[oe] Kernel load address issue
Bernard Mentink
Bernard_Mentink at trimble.com
Tue Jul 26 22:14:50 UTC 2011
Many thanks for the reply,
By the way where is the machine.conf file, I can't seem to find it
anywhere ..
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
Martin Jansa
Sent: Wednesday, 27 July 2011 10:03 a.m.
To: openembedded-devel at lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 09:51:28AM +1200, Bernard Mentink wrote:
>
> Hi Guys,
>
> I am new to OE, but have managed to get u-boot working on my target,
> got TFTP working so I can transfer a kernel to RAM.
> I have modified my conf/local.conf file so that when a kernel is built
> a uImage binary is created that u-boot can use. (added line
> KERNEL_IMAGETYPE = "uImage")
>
> However When I try to boot the image in the bootloader, I get this:
>
> uboot> bootm 0x80300000
> ## Booting kernel from Legacy Image at 80300000 ...
> Image Name: Angstrom/2.6.36/mx31ads
> Created: 2011-07-26 19:55:31 UTC
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1765856 Bytes = 1.7 MiB
> Load Address: 20008000
> Entry Point: 20008000
machine.conf can define
UBOOT_ENTRYPOINT = "0x80008000"
UBOOT_LOADADDRESS = "0x80008000"
both used in kernel.bbclass
/OE/dev/classes/kernel.bbclass:UBOOT_ENTRYPOINT ?= "20008000"
/OE/dev/classes/kernel.bbclass:UBOOT_LOADADDRESS ?=
"${UBOOT_ENTRYPOINT}"
/OE/dev/classes/kernel.bbclass: uboot-mkimage -A
${UBOOT_ARCH} -O linux -T kernel -C none -a ${UBOOT_LOADADDRESS} -e
$ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin
arch/${ARCH}/boot/uImage
Cheers,
> Verifying Checksum ... OK
> Loading Kernel Image ... <-- gets stuck here! ...
>
> The Load Address is wrong, my ram starts at 0x80000000 ... can someone
> tell me how to change this? I presume mkimage is responsible for this
> as the kernel is configured as relocatable ..
>
> Many Thanks,
> Bernie
>
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa at gmail.com
More information about the Openembedded-devel
mailing list