[yocto] [SOLVED] Wrong ENTRYPOINT and LOADADDRESS in uImage

[Markus Hubig]

On Thu, Aug 23, 2012 at 11:32:02AM +0200, Martin Jansa wrote:
> On Thu, Aug 23, 2012 at 11:24:20AM +0200, Markus Hubig wrote:
> > 
> > I have a customized Yocto-Linux Recipe in my BSP, and now I'm seeing that
> > the UBOOT_ENTRYPOINT and UBOOT_LOADADDRESS settings in my ${MACHINE}.conf
> > is not honored in the resulting uImage.
> 
> You need newer oe-core with this commit and KEEPUIMAGE set to "no"
> 
> commit 72a7049526ee107005bd39c7bdd814ed71345829
> Author: Koen Kooi <koen at dominion.thruhere.net>
> Date:   Mon Jul 23 13:45:30 2012 -0700
> 
>     kernel bbclass: Recreate uImage only when KEEPUIMAGE != "yes"
> 
>     The intent of the uImage code in this class includes the following
> 
>     1) be able to specify custom load addresses without needing to patch the
>        kernel
>     2) add better information to the uImage description field
> 
>     The current state is a NOP anyway, the kernel will always build a uImage
>     when you tell it to 'make uImage'.
> 
>     weakly Set KEEPUIMAGE to 'yes' in default-distrovars.inc which preserve
>     the current OE-Core behavior. Machines which are being ported from oe.dev
>     and need to regenerate uImage can set this to be empty
> 
>     Signed-off-by: Koen Kooi <koen at dominion.thruhere.net>
>     Signed-off-by: Khem Raj <raj.khem at gmail.com>
>     Signed-off-by: Saul Wold <sgw at linux.intel.com>

Thanks that fixed it ...

Cheers, Markus

-- 
Human beings were created by water to transport it uphill.