[U-Boot-Users] Booting Multi Image FIle

[U-Boot-Users] Booting Multi Image FIle

[Alemao]

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

[U-Boot-Users] Booting Multi Image FIle

[Alemao]

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@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

[U-Boot-Users] Booting Multi Image FIle

[Detlev Zundel]

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 at 2" from a new uImage at 200000, with initrd "ramdisk at 1"
  and FDT
  "fdt at 1", both stored in some other new uImage located at 800000:
bootm 200000:kernel at 1 800000:ramdisk at 1 800000:fdt at 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 at denx.de

[U-Boot-Users] Re: Booting Multi Image FIle

[Alemao]

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 at 2" from a new uImage at 200000, with initrd "ramdisk at 1"
>  and FDT
>  "fdt at 1", both stored in some other new uImage located at 800000:
> bootm 200000:kernel at 1 800000:ramdisk at 1 800000:fdt at 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 at denx.de
>

[U-Boot-Users] Booting Multi Image FIle

[Alemao]

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 at 2" from a new uImage at 200000, with initrd "ramdisk at 1"
>>  and FDT
>>  "fdt at 1", both stored in some other new uImage located at 800000:
>> bootm 200000:kernel at 1 800000:ramdisk at 1 800000:fdt at 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 at denx.de
>>
>