[U-Boot-Users] Booting Multi Image FIle
Alemao
xcarandiru at gmail.com
Fri Jun 27 19:52:06 CEST 2008
Solved with:
bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr}
But, is there a way of getting this values instead of searching with a
hexeditor through the image??
On Thu, Jun 26, 2008 at 2:26 PM, Alemao <xcarandiru at gmail.com> wrote:
> Hi all,
>
> I have a board here that was fully working when booting using the tree
> files separated. Now im trying
> using a multi image file:
>
> # mkimage -A ppc -O Linux -T multi -C gzip -n 'Linux PowerPC' -d
> vmlinux.bin.gz:ramdisk:board.dtb kernel.img
>
> Loading to ram:
>
> # tftpboot 0x01000000 kernel.img
>
> Booting:
>
> # bootm 0x01000000
>
> ## Booting image at 01000000 ...
> Image Name: Linux PowerPC
> Image Type: PowerPC Linux Multi-File Image (gzip compressed)
> Data Size: 2627156 Bytes = 2.5 MB
> Load Address: 00000000
> Entry Point: 00000000
> Contents:
> Image 0: 916112 Bytes = 894.6 kB
> Image 1: 1698738 Bytes = 1.6 MB
> Image 2: 12288 Bytes = 12 kB
> Verifying Checksum ... OK
> Uncompressing Multi-File Image ... OK
> Loading Ramdisk to 07de2000, end 07f80bb2 ... OK
> Loading Device Tree to 007fc000, end 007fefff ... OK
> .
> .
> .
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> No filesystem could mount root, tried: ext2
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)
>
>
> Im missing something? Do i have to pass the addr of ramdisk at bootm ?
>
>
> Thanks in advance,
>
> --
> Alemao
>
--
Alemao
More information about the U-Boot
mailing list