Sorry, you need to enable JavaScript to visit this website.

programming qspi images

Zedboard forums is currently read-only while it under goes maintenance.

Unsolved
3 posts / 0 new
lguser
Junior(0)
programming qspi images

Do I have to name the QSPI image BOOT_QSPI.bin, if I use the flashcp linux utility to program the image to QSPI flash?
We will need to load more than one image on the QSPI flash on the picoZed SOM (FMC v2 7015).  Can I copy two image files with different names to QSPI flash via flashcp?  
Do I need multiple boot partitions on the QSPI flash in this case?
How does the FSBL handle or select from two or more images?

lguser
Junior(0)
Are there picoZed documents

Are there picoZed documents that discuss multi-boot?
Ae there Linux utilities that allow user to specify the qspi flash location (offset) to which the bin file is copied?   
Does the Linux flashcp utility program the BOOT_QSPI.bin file at 0 offset?

lguser
Junior(0)
BOOT.mcs image size

Based on the tutorials from AVNET site, QSPI boot requires a MCS image (BOOT.mcs).  It turns out that my generated BOOT.mcs image (FSBL, bitstream and u-boot) is of 11.3M in size, whereas its BOOT.bin counterpart is only 3.9M in size. The MCS format itself takes up an extra 7M bytes.   Why is BOOT.mcs doubled in size?   
For upgrade and backup purposes, we would like to store at least two images on QSPI flash.  Would BOOT.bin work on the QSPI flash?