Actions
Forum Thread Details
  • State Not Answered
  • Replies 10 replies
  • Subscribers 342 subscribers
  • Views 800 views
  • Users 0 members are here
Related

Keep Linux and custom hardware in PL at power on

Former Member

MicroZED with IO Carrier. My custom hardware PL application does not need the PS at all. My TOP design does however instantiate both the Base PS_module wrapper as well as my custom PL_module. And a bit file for this TOP design can be generated in Vivado.

Powering up the MicroZED and Carrier, boots Linux from QSPI and responds to serial Terminal commands. From the Vivado GUI with JTAG connected I can "Program Device" with the TOP bit file. After programming is done both Linux and my custom hardware in the PL are operating as expected. Also as expected, when power off then on, my custom hardware in the PL is no longer operational, and the device must be programmed again.

What do I do to program this TOP bit file into the QSPI so that the system boots to the Linux and my custom hardware in the PL is running and available at power up.

Thank you

Parents
  • 0

    Hello Warrenh,

    I am going to refer you to our Zynq Software Speedways. Spefically lab 6 and lab 7.

    http://zedboard.org/course/developing-zynq%C2%AE-7000-all-programmable-soc-software-vivado-20133-201441-20152-and-20162

    In those two labs, first we creat a First stage bootloader, then we create the .mcs files image that will program the QSPI, and finally we program the flash(QSPI). In this example it is a baremetal design, however you are working on a Linux design. The process is almost nearly the same. When creating your linux .mcs image, instead of using the SDK boot image generator to add a baremetal application as the last partition in the boot image, the u-boot.elf executable is used instead. So the order of files would look like this:

    zynq.fsbl.elf

    system.bit

    uboot.elf

    U-boot is the Second Stage Bootloader (SSBL) which, in-turn, should know how to lead Linux using image.ub or ulmage depending on which flavor of Linux you are using.

    --Josh

  • 0 in reply to jafoste4

    Hello,

    Adding the u-boot.elf executable as the last object in "Create Boot Image" programs my system.bit file into the PL while an OS boots as observed via a Terminal window. The issue that I have is that I can not find a uboot.elf that installs the desired OS. The board out of the box booted with a terminal prompt "zynq>" and recognized commands like "ls" and "pwd". The only u-boot.elf's that I can find for Creating Boot Image boot with a terminal prompt of U-Boot-PetaLinux>" or "zynq-uboot>" and do not recognize the "ls" or "pwd" commands. How can I get an .elf to include as the last object for "Create Boot Image" that will boot to the "zync" prompt as the original did?

    Thank you,

Reply
  • 0 in reply to jafoste4

    Hello,

    Adding the u-boot.elf executable as the last object in "Create Boot Image" programs my system.bit file into the PL while an OS boots as observed via a Terminal window. The issue that I have is that I can not find a uboot.elf that installs the desired OS. The board out of the box booted with a terminal prompt "zynq>" and recognized commands like "ls" and "pwd". The only u-boot.elf's that I can find for Creating Boot Image boot with a terminal prompt of U-Boot-PetaLinux>" or "zynq-uboot>" and do not recognize the "ls" or "pwd" commands. How can I get an .elf to include as the last object for "Create Boot Image" that will boot to the "zync" prompt as the original did?

    Thank you,

Children
No Data