public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] U-boot multi-file format
@ 2017-03-19 22:14 Diego
  2017-03-30 10:13 ` Diego
  0 siblings, 1 reply; 3+ messages in thread
From: Diego @ 2017-03-19 22:14 UTC (permalink / raw)
  To: u-boot

Hi all,

I'm trying to use the multi-file format mentioned in pages 12-13 of "U-Boot – Multi image booting scenarios" PDF slides.

I'd like to use FIT format, but I already have units in the field without CONFIG_FIT.

So I'd like to use the legacy U-Boot multi-file format, but I don't understand the format that should be used for the ramdisk. I already have a multi-file image that boots the kernel with the dtb, but it crashes when the ramdisk is needed (looking for an address outside of physical memory limits).

Which format should be used for the ramdisk? ext3.gz initrd? cpio.gz initramfs?

Thanks for any help!

Bests,
Diego

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] U-boot multi-file format
  2017-03-19 22:14 [U-Boot] U-boot multi-file format Diego
@ 2017-03-30 10:13 ` Diego
  2017-03-30 14:19   ` Wolfgang Denk
  0 siblings, 1 reply; 3+ messages in thread
From: Diego @ 2017-03-30 10:13 UTC (permalink / raw)
  To: u-boot

In data domenica 19 marzo 2017 23:14:14 CEST, Diego ha scritto:
> Hi all,
> 
> I'm trying to use the multi-file format mentioned in pages 12-13 of "U-Boot
> – Multi image booting scenarios" PDF slides.
> 
> I'd like to use FIT format, but I already have units in the field without
> CONFIG_FIT.
> 
> So I'd like to use the legacy U-Boot multi-file format, but I don't
> understand the format that should be used for the ramdisk. I already have a
> multi-file image that boots the kernel with the dtb, but it crashes when
> the ramdisk is needed (looking for an address outside of physical memory
> limits).
> 
> Which format should be used for the ramdisk? ext3.gz initrd? cpio.gz
> initramfs?
> 

Hi all,

as I've found the solution, I'll reply myself in the hope it might help 
somebody in the future.

The format can be both ext3.gz initrd, or cpio.gz, as I've seen a working 
example of ext3.gz initrd here:
https://alteraforum.com/forum/showthread.php?t=51423&p=212064#post212064
And I've been able to make a cpio.gz initramfs by specifying an initrd_high 
address below the location of the multi-file address. Leaving the 
initrd_high=0xffffffff was causing the kernel to not find the ramdisk image, 
thus crashing.

Hope it helps,
Diego

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] U-boot multi-file format
  2017-03-30 10:13 ` Diego
@ 2017-03-30 14:19   ` Wolfgang Denk
  0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2017-03-30 14:19 UTC (permalink / raw)
  To: u-boot

Dear Diego,

In message <3013204.RF8YVXT0ez@localhost.localdomain> you wrote:
>
> > Which format should be used for the ramdisk? ext3.gz initrd? cpio.gz
> > initramfs?

Actually this is independent of U-Boot.

> as I've found the solution, I'll reply myself in the hope it might help 
> somebody in the future.
> 
> The format can be both ext3.gz initrd, or cpio.gz, as I've seen a working 
> example of ext3.gz initrd here:

It can be anything that is understood by the Linux kernel you are
trying to boot.  U-Boot is just the tool that puts the image into
memory - all the rest is the responsibility of Linux.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"The greatest warriors are the ones who fight for peace."
- Holly Near

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-30 14:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-19 22:14 [U-Boot] U-boot multi-file format Diego
2017-03-30 10:13 ` Diego
2017-03-30 14:19   ` Wolfgang Denk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox