[oe] Kernel load address issue

[Chris Verges]

Apologies for the top posting on this one ...

You can easily generate a zImage.  If you have devshell enabled, type
"bitbake linux -c devshell" and browse under arch/*/boot/... to find
your vmlinux image.

Try bootm 0x840000A0.  This works on my system.

Chris

On Wed, Jul 27, 2011 at 12:22 PM, Bernard Mentink
<Bernard_Mentink at trimble.com> wrote:
> Hi Chris,
>
> Many thanks for that. However I only have a uImage in my build, no zImage so can't do a diff to find the offset, is there another way to find that out?
> Maybe you or someone else knows what script in openembedded calls the mkimage utility so I can find what parameters are passed ..
>
> By the way, I set UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT to be the same (0x80400000, a bit past u-boot and the environment) in my config file, I am not sure if the entry point should be the same as the load address.
>
> Cheers,
> Bernie
>
> ------------------------------------------------------------------------------------------
> I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car.
>
> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of Chris Verges
> Sent: Thursday, 28 July 2011 2:12 a.m.
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] Kernel load address issue
>
> On Wed, Jul 27, 2011 at 06:00:07AM +0000, Mats Kärrman wrote:
>> Starting kernel ...
>>
>> And there it hangs ... I don't know who printed out the "Starting
>> kernel" was it uboot or the kernel?  If uboot, how do I pass kernel
>> arguments (i.e the console serial params) with this method of booting?
>
> Hi Bernie,
>
> I've experienced this before when the UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT values in the machine config file for OpenEmbedded aren't properly set to the correct value.  You may want to double check those values.
>
> Also, try setting your bootm address just a tag higher in memory than the actual UBOOT_ENTRYPOINT.  I forgot what the exact uboot-mkimage header put on the uImage is, but you can do a hex diff between the zImage and uImage files to figure it out.  That offset can sometimes cause some odd booting problems.
>
> So if your ENTRYPOINT is 0x8300000 and the uboot-mkimage offset is 0xC0, for example, you'd need to bootm 0x83000C0.  (Again, double check the uboot-mkimage offset.)
>
> Good luck,
> Chris
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>