* Kernel load address issue
@ 2011-07-26 21:51 Bernard Mentink
2011-07-26 22:03 ` Martin Jansa
0 siblings, 1 reply; 10+ messages in thread
From: Bernard Mentink @ 2011-07-26 21:51 UTC (permalink / raw)
To: openembedded-devel
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
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 21:51 Kernel load address issue Bernard Mentink
@ 2011-07-26 22:03 ` Martin Jansa
2011-07-26 22:14 ` Bernard Mentink
0 siblings, 1 reply; 10+ messages in thread
From: Martin Jansa @ 2011-07-26 22:03 UTC (permalink / raw)
To: openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 22:03 ` Martin Jansa
@ 2011-07-26 22:14 ` Bernard Mentink
2011-07-26 22:20 ` Gary Thomas
2011-07-26 22:26 ` Martin Jansa
0 siblings, 2 replies; 10+ messages in thread
From: Bernard Mentink @ 2011-07-26 22:14 UTC (permalink / raw)
To: openembedded-devel
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@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:03 a.m.
To: openembedded-devel@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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 22:14 ` Bernard Mentink
@ 2011-07-26 22:20 ` Gary Thomas
2011-07-26 22:26 ` Martin Jansa
1 sibling, 0 replies; 10+ messages in thread
From: Gary Thomas @ 2011-07-26 22:20 UTC (permalink / raw)
To: openembedded-devel
On 2011-07-26 16:14, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
It's ${MACHINE}.conf - fill in the name of your machine
> ------------------------------------------------------------------------
> ------------------
> 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@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@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@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 22:14 ` Bernard Mentink
2011-07-26 22:20 ` Gary Thomas
@ 2011-07-26 22:26 ` Martin Jansa
2011-07-26 22:31 ` Bernard Mentink
1 sibling, 1 reply; 10+ messages in thread
From: Martin Jansa @ 2011-07-26 22:26 UTC (permalink / raw)
To: openembedded-devel
[-- Attachment #1: Type: text/plain, Size: 3234 bytes --]
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> 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@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@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@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 22:26 ` Martin Jansa
@ 2011-07-26 22:31 ` Bernard Mentink
2011-07-27 2:48 ` Bernard Mentink
0 siblings, 1 reply; 10+ messages in thread
From: Bernard Mentink @ 2011-07-26 22:31 UTC (permalink / raw)
To: openembedded-devel
Hi Martin,
Thanks for that (and to Gary for the same answer) ..
By the way, where do I find this sort of information out? I especially
would like to know how to configure the kernel, modify source code etc,
Within the openembedded system ..
Are there some good "howto's" out there?
Thanks,
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@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:27 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> 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@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf
> Of Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@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@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-26 22:31 ` Bernard Mentink
@ 2011-07-27 2:48 ` Bernard Mentink
2011-07-27 6:00 ` Mats Kärrman
0 siblings, 1 reply; 10+ messages in thread
From: Bernard Mentink @ 2011-07-27 2:48 UTC (permalink / raw)
To: openembedded-devel
I have got a bit further now, I get:
-----------------------------------------------------
uboot> bootm 80400000
## Booting kernel from Legacy Image at 80400000 ...
Image Name: Angstrom/2.6.36/mx31ads
Created: 2011-07-26 22:30:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1765848 Bytes = 1.7 MiB
Load Address: 80400000
Entry Point: 80400000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
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?
(I am using: " dhcp 0x80400000 IP:file" followed by the above bootm .. )
Thanks,
Bernie
-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Bernard Mentink
Sent: Wednesday, 27 July 2011 10:32 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
Hi Martin,
Thanks for that (and to Gary for the same answer) ..
By the way, where do I find this sort of information out? I especially
would like to know how to configure the kernel, modify source code etc,
Within the openembedded system ..
Are there some good "howto's" out there?
Thanks,
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@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:27 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> 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@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf
> Of Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@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@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-27 2:48 ` Bernard Mentink
@ 2011-07-27 6:00 ` Mats Kärrman
[not found] ` <20110727141213.GA8582@cverges-dev-lnx>
0 siblings, 1 reply; 10+ messages in thread
From: Mats Kärrman @ 2011-07-27 6:00 UTC (permalink / raw)
To: openembedded-devel
Hi Bernard,
U-Boot prints "Starting kernel" (in your case probably from "lib_arm/bootm.c").
Setting boot arguments from U-Boot before bootm: setenv bootargs "...your args..."
// Mats
________________________________________
From: openembedded-devel-bounces@lists.openembedded.org [openembedded-devel-bounces@lists.openembedded.org] on behalf of Bernard Mentink [Bernard_Mentink@trimble.com]
Sent: Wednesday, July 27, 2011 4:48 AM
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
I have got a bit further now, I get:
-----------------------------------------------------
uboot> bootm 80400000
## Booting kernel from Legacy Image at 80400000 ...
Image Name: Angstrom/2.6.36/mx31ads
Created: 2011-07-26 22:30:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1765848 Bytes = 1.7 MiB
Load Address: 80400000
Entry Point: 80400000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
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?
(I am using: " dhcp 0x80400000 IP:file" followed by the above bootm .. )
Thanks,
Bernie
-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Bernard Mentink
Sent: Wednesday, 27 July 2011 10:32 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
Hi Martin,
Thanks for that (and to Gary for the same answer) ..
By the way, where do I find this sort of information out? I especially
would like to know how to configure the kernel, modify source code etc,
Within the openembedded system ..
Are there some good "howto's" out there?
Thanks,
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@lists.openembedded.org
[mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:27 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> 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@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf
> Of Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@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@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
[not found] ` <20110727141213.GA8582@cverges-dev-lnx>
@ 2011-07-27 19:22 ` Bernard Mentink
2011-07-28 17:59 ` Chris Verges
0 siblings, 1 reply; 10+ messages in thread
From: Bernard Mentink @ 2011-07-27 19:22 UTC (permalink / raw)
To: openembedded-devel
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@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Chris Verges
Sent: Thursday, 28 July 2011 2:12 a.m.
To: openembedded-devel@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@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Kernel load address issue
2011-07-27 19:22 ` Bernard Mentink
@ 2011-07-28 17:59 ` Chris Verges
0 siblings, 0 replies; 10+ messages in thread
From: Chris Verges @ 2011-07-28 17:59 UTC (permalink / raw)
To: openembedded-devel
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@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@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Chris Verges
> Sent: Thursday, 28 July 2011 2:12 a.m.
> To: openembedded-devel@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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-07-28 18:05 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-26 21:51 Kernel load address issue Bernard Mentink
2011-07-26 22:03 ` Martin Jansa
2011-07-26 22:14 ` Bernard Mentink
2011-07-26 22:20 ` Gary Thomas
2011-07-26 22:26 ` Martin Jansa
2011-07-26 22:31 ` Bernard Mentink
2011-07-27 2:48 ` Bernard Mentink
2011-07-27 6:00 ` Mats Kärrman
[not found] ` <20110727141213.GA8582@cverges-dev-lnx>
2011-07-27 19:22 ` Bernard Mentink
2011-07-28 17:59 ` Chris Verges
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.