[U-Boot-Users] Re: Booting Multi Image FIle
Actually i havent read, cause im using u-boot 1.1.14
What im trying to do is using a multi-image file with this version.
If i do: bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} everything is OK, the problem for me is getting this addresses, i had to browse the image with a hex editor.
If i do: bootm ${kernel_addr} the kernel doesnt find ramdisk
So i have to find a way for getting it works using just the command above.
Move to u-boot 1.3.3 is not a good idea right now.
Cheers,
-- Alemao
On Mon, Jun 30, 2008 at 8:43 AM, Detlev Zundel dzu@denx.de wrote:
Hi Alemao,
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??
So you read doc/uImage.FIT/command_syntax_extension.txt containing this example at the end:
- boot "kernel@2" from a new uImage at 200000, with initrd "ramdisk@1"
and FDT "fdt@1", both stored in some other new uImage located at 800000: bootm 200000:kernel@1 800000:ramdisk@1 800000:fdt@1
And you still have questions? ;)
Cheers Detlev
-- The proprietary-Unix players proved so ponderous, so blind, and so inept at marketing that Microsoft was able to grab away a large part of their market with the shockingly inferior technology of its Windows operating system. -- "A Brief History of Hackerdom" by Eric Steven Raymond -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
My apologies, i was using ramdisk image with some headers... thats why kernel couldnt find it.
Cheers,
-- Alemao
On Wed, Jul 2, 2008 at 10:04 AM, Alemao xcarandiru@gmail.com wrote:
Actually i havent read, cause im using u-boot 1.1.14
What im trying to do is using a multi-image file with this version.
If i do: bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} everything is OK, the problem for me is getting this addresses, i had to browse the image with a hex editor.
If i do: bootm ${kernel_addr} the kernel doesnt find ramdisk
So i have to find a way for getting it works using just the command above.
Move to u-boot 1.3.3 is not a good idea right now.
Cheers,
-- Alemao
On Mon, Jun 30, 2008 at 8:43 AM, Detlev Zundel dzu@denx.de wrote:
Hi Alemao,
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??
So you read doc/uImage.FIT/command_syntax_extension.txt containing this example at the end:
- boot "kernel@2" from a new uImage at 200000, with initrd "ramdisk@1"
and FDT "fdt@1", both stored in some other new uImage located at 800000: bootm 200000:kernel@1 800000:ramdisk@1 800000:fdt@1
And you still have questions? ;)
Cheers Detlev
-- The proprietary-Unix players proved so ponderous, so blind, and so inept at marketing that Microsoft was able to grab away a large part of their market with the shockingly inferior technology of its Windows operating system. -- "A Brief History of Hackerdom" by Eric Steven Raymond -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
participants (1)
-
Alemao