Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 336 subscribers
  • Views 602 views
  • Users 0 members are here
Related

MicroZED Does not boot Wind River Pulsar Linux

sbillings1

I have a new MicroZED board with Wind River Pulsar Linux provided on an SD card.  I have followed the quick start instructions to install USB-to-UART driver, insert the SD card, connect ENET, and boot the MicroZED.  However, the MicroZED does not appear to boot Wind River Pulsar Linux.

I noticed that the SD card does get mounted to "/mnt" though.  What can I do to boot Wind River Pulsar Linux?

Update:  I discovered the MicroZED Evaluation Kit Hardware Guide specifiers that jumpers JP2 and JP3 control the boot device to be used, and that the default boot device is QSPI flash memory. The serial output during bootup confirms that the MicroZED is booting from QSPI flash.  However, changing jumpers JP2 and JP3 to the SD Card boot device setting has no effect.  These are the jumper settings stated in the hardware guide:

QSPI Setting:  JP3 = 2-3 (1),  JP2 = 1-2 (0)

SD Card Setting:  JP3 = 2-3 (1),  JP2 = 2-3 (1)

  • 0

    Following instructions in the Wind River Pulsar Linux Quick Start for Avnet Zynq Version 7.0 I was able to boot the Wind River Pulsar Linux kernel from SD Card.  Booting requires pressing a key immediately after reset to stop the autoboot process and then issuing several commands to boot from the SD Card.  (These commands can be stored as the defaults using a few more commands).

    If anyone from Avnet is listening, it would be really helpful to include this information in the Quick Start cards that ship with the development kit, or at least include a statement saying to refer to the quick start guide that I've noted above.  The Quick Start cards that shipped with my kit only say to put in the SD card and wait for Wind River Pulsar Linux to boot.  There is no mention about jumper settings, stopping the autoboot process, or the cryptic commands that are required.

  • 0

    Hi sbillings1,

    Sounds very strange, as I have not had any problems booting Pulsar Linux on my MicroZed.  Sorry to hear you are having this type of frustration with our kit.

    I think hockeyman1972 ran into a similar issue a while back where he saved some U-Boot environment parameters down to NV memory using the 'saveenv' command.  Once this happens, subsequent loads of U-Boot will also use any stored environment parameters found in that same u-boot environment variable NV memory partition space.

    A few weeks might go by and he would load a Pulsar build onto that board and forget that "custom" U-Boot environment parameters had been stored and were being recalled into memory and used for booting.  Unfortunately, if you had parameters in there for booting some other version of Linux, like PetaLinux, then perhaps

    Thanks to some research from hockeyman1972, it turns out there is a way to wipe out any saved u-boot environment settings so that default settings built into U-Boot can take over:

    https://stackoverflow.com/questions/20621937/how-do-i-clear-environment-variables-previously-saved-with-u-boot

    Is it possible that something similar was happening in your situation?

    Best Regards,

    -Kevin