[meta-xilinx] ramdisk format for booti command in u-boot

[Sandeep Gundlupet Raju]

Hi Giordon,

Thanks,
Sandeep

From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-bounces at yoctoproject.org] On Behalf Of Giordon Stark
Sent: Wednesday, January 10, 2018 9:48 AM
To: meta-xilinx at yoctoproject.org
Subject: [meta-xilinx] ramdisk format for booti command in u-boot

Hi all,

Initially, I tried the bootm command, and found the Image format to be incorrect.. so then I switched to the booti command, and I get this:

> booti 0x200000 0x7000000 0x1000000
Bad Linux ARM64 Image magic!

I do something like the following to set things up:

> setenv ip no
> setenv autoload no
> setenv serverip 192.168.1.100
> dhcp
> tftpboot 0x200000 Image
> tftpboot 0x7000000 zynq-base-gfex-prototype3.tar.gz
> tftpboot 0x1000000 gfex-prototype3.dtb

Three questions:

1) Is there a different image format I should be using? If so, what is it?
2) are the addresses here arbitrary?
3) if I run without the initrd (passing '-' as the second parameter instead), it gets to a point where it cannot open a root device (we have no working SD card): https://gist.github.com/kratsg/b5630a23aa3b71161da833fcad07eaaf - how to fix this? Having `bootargs=boot=ram0` or something similar did not work.

Try similar to this command.
# mmc dev 0 && mmcinfo && load mmc 0:1 0x80000 Image.bin && load mmc 0:1 0x4000000 system.dtb && load mmc 0:1 0x6000000 rootfs.cpio.gz && booti 0x80000 - 0x4000000

Thanks,

Giordon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180112/26887c33/attachment-0001.html>