[U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command

[Kumar Gala]

On Feb 19, 2007, at 5:51 PM, Timur Tabi wrote:

> Kumar Gala wrote:
>
>>> I've never heard of multi image before.  How do I make one?  The  
>>> README doesn't explain it.
>> mkimage  -A ppc -O Linux -T multi -C gzip -n 'Linux Multiboot- 
>> Image' -e 0 -a 0 -d vmlinux.gz:rootfs.ext2.gz:oftree.dtb  kern+fs 
>> +dtb.bin
>
> I need some more help getting the multi-image to work.  I have the  
> following files:
>
> vmlinux.bin.gz (built myself)
> rootfs.ext2.gz.uboot (from the BSP, because I don't know how to  
> build a root file system.  I don't know what the ".uboot" is for.)
> mpc8349emitx.dtb (built myself)
>
> I create the multi image per you instructions, tftp them to  
> $loadaddr (200000), and do "bootm $loadaddr".  I get this output:
>
> bootm $loadaddr
> ## Booting image at 00200000 ...
>    Image Name:   Linux Multiboot-Image
>    Created:      2007-02-19  23:46:03 UTC
>    Image Type:   PowerPC Linux Multi-File Image (gzip compressed)
>    Data Size:    20407814 Bytes = 19.5 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Contents:
>    Image 0:  1416615 Bytes =  1.4 MB
>    Image 1: 18987128 Bytes = 18.1 MB
>    Image 2:     4054 Bytes =  4 kB
>    Verifying Checksum ... OK
>    Uncompressing Multi-File Image ... OK
>
>
> U-Boot 1.2.0-g2e892316-dirty (Feb  9 2007 - 15:56:37) MPC83XX
>
>
> So the image appears to be okay, but it doesn't boot at all.  Is  
> there something obvious I'm doing wrong, or will I have to debug this?

Sounds right, I'd double check that your rootfs.ext2.gz.uboot isn't  
already a uImage, but the actual ext2 image gziped.

Also, can you boot these three files if you keep them separate?  If  
so that makes me think a bug in the bootm changes.

- k