[meta-xilinx] Assembling Yocto build outputs
Eric Wong
ekw1 at yahoo.com
Thu Nov 6 15:44:46 PST 2014
I have used Yocto and meta-xilinx layer to build a core-minimal-image for zc702-zynq7 using the daisy branch. (Prior to this, I successfully built and ran the default qemux86 target as well as the qemuzynq target on QEMU.) I now want to load and run the resulting zc702-zynq7 build from the Zedboard's QSPI flash.
In Xilinx SDK, I tried to build an image (MCS file) for QSPI flash using the following files:zynq_fsbl_0.elf (FSBL from Xilinx SDK)system hardware bitstream (from Xilinx SDK)u-boot.elf (Uboot created from Yocto build)uImage-zc702-zynq7.bin (Kernel created from Yocto build)uImage-zc702-zynq7.dtb (Device tree created from Yocto build)core-image-minimal-zc702-zynq7.ext2.gz.u-boot (Ramdisk image created from Yocto build) But I get messages about overlapping regions and when programmed to flash (knowing it won’t work), I get “Wrong Image Format for bootm command, can’t get kernel image” errors:
U-Boot 2014.01 (Nov 06 2014 - 14:02:33)I2C: ready
Memory: ECC disabled
DRAM: 1 GiB
MMC: zynq_sdhci: 0
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environmentIn: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Copying Linux from QSPI flash to RAM...
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
SF: 5242880 bytes @ 0x100000 Read: OK
SF: 131072 bytes @ 0x600000 Read: OK
Copying ramdisk...
SF: 6160384 bytes @ 0x620000 Read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image! I did not specify offsets when building the MCS file and suspect this could be the problem (or one of them anyway). I went ahead and took the 3 hex addresses that uboot looks like it's reading from above (0x100000, 0x600000, 0x620000) and put the kernel, device tree and ramdisk images at these offsets, respectively, but get the same uboot output and error.
My questions at this point are:1) Am I using the Yocto produced images correctly in Xilinx SDK to create the MCS file used to program the Zedboard's QSPI flash? Or do I need to do some more post-processing before the Yocto output can be used in Xilinx SDK?2) Does my problem have to do with using the wrong offsets to make the MCS file? How would I find the right offsets to use?
Thanks for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20141106/8230f47a/attachment.html>
More information about the meta-xilinx
mailing list