Actions
Forum Thread Details
  • State Not Answered
  • Replies 10 replies
  • Subscribers 342 subscribers
  • Views 801 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, 

    It was just confirmed to me that you are most likely running Petalinux due to Pulsar Linux never booting up with a prompt of "zynq>". If you enter "uname -a" at your linux prompt you should be able to discern which kernel version you are running. 

    Now moving on to getting the u-boot.elf file you are requesting. U-boot.elf is somthing that is typically generated for your specific hardware. In your case it involves the MicroZed 7010 or 7020. So it is not a one u-boot.elf fits all kind of file. Here are the steps you will need to follow to generate your u-boot.elf file

    1. Download the PetaLinux BSP for your specific MicroZed at http://zedboard.org/support/design/1519/10

    2.Then go to http://zedboard.org/support/design/13076/106 and download the Application Not on Booting PicoZed Using QSPI and eMMC "Booting PicoZed Using QSPI and eMMC v2.1"

    3. Go through that tutorial, but remember that you are targeting your MicroZed not PicoZed so alter material accordingly. 

    4. By the end you should be able to boot from QSPI

    --Josh

  • 0 in reply to jafoste4

    Hello,

    The application note specifies requirements to be

    The software requirements for this reference design are:
    • 64-bit Linux (can be Linux installed in a virtual machine on a 64-bit Windows host)

    I am using Vivado and SDK on a Windows platform and getting a Linux box is problematic. How can SDK on Windows get access to the correct BSP or .elf so that a build of my custom PL gets booted from the QSPI as well as keeping the Pulsar Linux that came with the board so that the Microzed board boots to the "Zync" prompt ?    

Reply
  • 0 in reply to jafoste4

    Hello,

    The application note specifies requirements to be

    The software requirements for this reference design are:
    • 64-bit Linux (can be Linux installed in a virtual machine on a 64-bit Windows host)

    I am using Vivado and SDK on a Windows platform and getting a Linux box is problematic. How can SDK on Windows get access to the correct BSP or .elf so that a build of my custom PL gets booted from the QSPI as well as keeping the Pulsar Linux that came with the board so that the Microzed board boots to the "Zync" prompt ?    

Children
No Data