Actions
Forum Thread Details
  • State Not Answered
  • Replies 11 replies
  • Subscribers 263 subscribers
  • Views 1442 views
  • Users 0 members are here
Related

PetaLinux SD boot

Former Member

I'm having trouble figuring out how to get the image I've created for the microZed 7020 to boot on it. It runs nicely in the qemu emulator but I can't get a valid system.bit.bin file. I've found some not quiet for microZed instructions to make a .bit.bin file, but I try using any of those files the boot process ends with a timeout on DMA when trying to load the FMGA.

For reference I'm using the Avnet-MicroZed-z7020-v2014.2.bsp file with the petalinux-create command, that appears to be the most correct one to use.

SD Boot without system.bit.bin:
Copying Linux from SD to RAM...
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Loading bitstream from SD/MMC/eMMC to RAM..
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
reading system.bit.bin
** Unable to read file system.bit.bin **
zynq-uboot>
]


With a system.bit.bin that I made using "bootgen -image test.bif -split bin -o i BOOT.BIN" but none of the .bit files I could find to convert with that matched the instructions so I think I'm doing something wrong there. But the boot attempts with that system.bit.bin all failed with:

Copying Linux from SD to RAM...
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Loading bitstream from SD/MMC/eMMC to RAM..
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
reading system.bit.bin
4045568 bytes read in 550 ms (7 MiB/s)
Error: Timeout waiting for DMA to complete.
fpga - loadable FPGA image support

Usage:
fpga [operation type] [device number] [image address] [image size]
fpga operations:
  dump  [dev]                   Load device to memory buffer
  info  [dev]                   list known device information
  load  [dev] [address] [size]  Load device from memory buffer
  loadb [dev] [address] [size]  Load device from bitstream buffer (Xilinx only)
  loadmk [dev] [address]        Load device generated with mkimage
        For loadmk operating on FIT format uImage address must include
        subimage unit name in the form of addr:<subimg_uname>
zynq-uboot>



Really I'm hoping someone just points me to the correct instructions for this.

  • 0

    You can try reading this chapter "Booting Linux from QSPI" in the "Booting PicoZed using QSPI and eMMC" found here: http://zedboard.org/content/booting-picozed-using-qspi-and-emmc-v21 

    It tells you how to get the files into the qspi flash in detail, but the 'power up with the switches set to qpsi' step is a bit vague.  I am not sure if our board had the uboot env overwritten or corrupted, but there was no command that told it to boot from qspi, so I did it by hand, something like: echo Running QSPI Boot && sf probe 0 && sf read ${clobstart} 0x520000 0x880000 && bootm ${clobstart}

    The 0x520000 could be different in your system, you'd want to check the output of your 'cat /proc/mtd' command to see where the kernel partition starts.