[meta-xilinx] Wrong Image Format for bootm command
Oleg K Dzhimiev
oleg at elphel.com
Fri Jan 31 11:58:00 PST 2014
Hi,
> fatload mmc 0 0x00008000 uImage
> fatload mmc 0 0x2A00000 devicetree.dtb
> fatload mmc 0 0x2000000 uramdisk.image.gz
> bootm 0x00008000 0x2000000 0x2A00000
Check your fsbl/u-boot memory map - you might be overwriting it with
uImage.. which causes to load the ramdisk to 0x0
Try something like (allows to load a ramdisk of up to 65MB):
> fatload mmc 0 0x3F00000 uImage
> fatload mmc 0 0x3E00000 devicetree.dtb
> fatload mmc 0 0x2000000 uramdisk.image.gz
> bootm 0x3F00000 0x2000000 0x3E00000
>
Oleg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140131/bb5b876e/attachment.html>
More information about the meta-xilinx
mailing list