I am using bitbake to build on top of a custom machine [eg: using my
devicetree] and then generating the following files which I renamed into a
format appropriate for meta-xilinx

-rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
-rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
-rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
-rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
-rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf

The machine is defined here:

The image I make (bitbake zynq-base) is defined here:

So i'm hoping this is relatively straightforward. *Now I get a little
confused about actually booting this on the board using the SD Card.* According
to the docs (
https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard) it
seems that I need to only use four files generated from bitbake:
devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then use the
Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
create a boot image (BOOT.BIN). Why isn't this able to be done using
bitbake? When I try everything without using the Xilinx SDK, I see the
error message [1].

My second (*less important*) question is how to get bitbake to generate the
filesystem in the right format? Right now, I have to run

mkimage -A arm -T ramdisk -C gzip -d
zynq-base-gfex-prototype2.cpio.gz.u-boot uramdisk.image.gz

in order to get the correct uramdisk.image.gz . Is there a way to make
bitbake generate the right image so I don't need to run this command so
that u-boot understands my image when booting?


U-Boot SPL 2015.04 (Oct 05 2016 - 13:12:31)
mmc boot
reading fpga.bin
spl_load_image_fat: error reading image fpga.bin, err - -1
spl: error reading image fpga.bin, err - 1
reading system.dtb
spl_load_image_fat_os: error reading image system.dtb, err - -1
reading u-boot-dtb.img
spl_load_image_fat: error reading image u-boot-dtb.img, err - -1
### ERROR ### Please RESET the board ###
meta-xilinx mailing list

Reply via email to