From mboxrd@z Thu Jan  1 00:00:00 1970
From: Diego <diego.ml@zoho.com>
Date: Thu, 30 Mar 2017 12:13:16 +0200
Subject: [U-Boot] U-boot multi-file format
In-Reply-To: <3AEBA8D2-9065-4811-8212-4B2E0F714633@zoho.com>
References: <3AEBA8D2-9065-4811-8212-4B2E0F714633@zoho.com>
Message-ID: <3013204.RF8YVXT0ez@localhost.localdomain>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
To: u-boot@lists.denx.de

In data domenica 19 marzo 2017 23:14:14 CEST, Diego ha scritto:
> Hi all,
>=20
> I'm trying to use the multi-file format mentioned in pages 12-13 of "U-Bo=
ot
> =E2=80=93 Multi image booting scenarios" PDF slides.
>=20
> I'd like to use FIT format, but I already have units in the field without
> CONFIG_FIT.
>=20
> 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).
>=20
> Which format should be used for the ramdisk? ext3.gz initrd? cpio.gz
> initramfs?
>=20

Hi all,

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

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

Hope it helps,
Diego