[U-Boot-Users] Booting multi-file images with a FDT but no initrd
Simon Kagstrom
simon.kagstrom at ericsson.com
Tue Dec 4 15:04:16 CET 2007
Hello U-boot list!
I'm using U-boot 1.3.0 to boot Linux on a Freescale MPC8349E-mITX, and
I have a small issue with multi-file images. I use a device tree but no
initrd, and I'm not quite sure how to boot the image in a good way. The
image is created in this way:
mkimage -A ppc -O Linux -T multi -d vmlinux.bin.gz:cmxb.dtb /tftpboot/vmlinux+fdt.img
I can boot it with (in U-boot)
setenv loadaddr 600000
tftp $loadaddr /tftpboot/vmlinux+fdt.img
bootm $loadaddr - 7a9634
and it starts just fine. My issue is with the address of the FDT - I'd
like to avoid having to hardcode this address since the kernel size can
change. If I just do 'bootm' or 'bootm $loadaddr -' it will end with
Verifying Checksum ... OK
Uncompressing Multi-File Image ... OK
Loading Ramdisk to 0ff6c000, end 0ff6f000 ... OK
and just lock there. So to the question: Is it possible to boot a
multifile image in this way without having an initrd and without the
hardcoded address, or must I modify the U-boot code to get such
functionality?
// Simon
More information about the U-Boot
mailing list