[U-Boot] u-boot: OpenRD Ultimate fails to build

Tom Rini
2015-04-07T00:39:31Z

On Sat, Apr 04, 2015 at 06:13:18PM +0200, drEagle wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Le 03/04/2015 23:46, Vagrant Cascadian a ?crit :
> > On 2015-03-25, drEagle wrote:
> >> Le 21/03/2015 15:53, Vagrant Cascadian a ?crit :
> >>> It seems that OpenRD Ultimate with u-boot 2015.04-rc3 and newer no
> >>> longer builds from source, both in Debian and with mainline git. It
> >>> appears to have overgrown the size limits set for it:
> >>
> >> Looks like the NAND partition map had to be changed to give more space for u-boot.
> >
> > The following patch gets it to build by moving the env addr and offset
> > later. This might cause problems with new or existing u-boot
> > installations on openrd if the environment needs to be at a specific
> > location. I have no hardware to test, so no way of confirming this
> > directly:
> >
> > diff --git a/include/configs/openrd.h b/include/configs/openrd.h
> > index b6f80af..2f1e174 100644
> > --- a/include/configs/openrd.h
> > +++ b/include/configs/openrd.h
> > @@ -72,12 +72,12 @@
> > /*
> > * max 4k env size is enough, but in case of nand
> > * it has to be rounded to sector size
> > */
> > #define CONFIG_ENV_SIZE 0x20000 /* 128k */
> > -#define CONFIG_ENV_ADDR 0x60000
> > -#define CONFIG_ENV_OFFSET 0x60000 /* env starts here */
> > +#define CONFIG_ENV_ADDR 0x80000
> > +#define CONFIG_ENV_OFFSET 0x80000 /* env starts here */
> > /*
> > * Environment is right behind U-Boot in flash. Make sure U-Boot
> > * doesn't grow into the environment area.
> > */
> > #define CONFIG_BOARD_SIZE_LIMIT CONFIG_ENV_OFFSET
> >
> >
> > I'll likely remove openrd_ultimate from future uploads to Debian if I
> > can't get confirmation about how to fix this properly.
>
> The same may be a problem for SHEEVAPLUG and GURUPLUG, may be also all KIRKWOOD derivatives.
> We need to get a more robust and compatible way to define the NAND PARTS, the BOOTLOAD and the NAND UPGRADE.
> Each distribution has differents needs.
>
> It's a discution needed upstream because it ill impact all distribution and users.

It's possible that by removing some CONFIG options things can fit under
the size limit and not require env to be moved.

--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150406/f7c080da/attachment.sig>