Re: [oe] Kernel load address issue
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 0x84A0. This works on my system. Chris On Wed, Jul 27, 2011 at 12:22 PM, Bernard Mentink bernard_ment...@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 (0x8040, 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-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@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 +, 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 0x830 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 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
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-boun...@lists.openembedded.org
[openembedded-devel-boun...@lists.openembedded.org] on behalf of Bernard
Mentink [bernard_ment...@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 8040
## Booting kernel from Legacy Image at 8040 ...
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: 8040
Entry Point: 8040
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 0x8040 IP:file followed by the above bootm .. )
Thanks,
Bernie
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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
Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 06:00:07AM +, 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 0x830 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
Re: [oe] Kernel load address issue
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 (0x8040, 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-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@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 +, 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 0x830 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
[oe] Kernel load address issue
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 0x8030 ## Booting kernel from Legacy Image at 8030 ... 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 0x8000 ... 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
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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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.ja...@gmail.com
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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.ja...@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.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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.ja...@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.ja...@gmail.com
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
I have got a bit further now, I get:
-
uboot bootm 8040
## Booting kernel from Legacy Image at 8040 ...
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: 8040
Entry Point: 8040
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 0x8040 IP:file followed by the above bootm .. )
Thanks,
Bernie
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@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 0x8030
## Booting kernel from Legacy Image at 8030 ...
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 0x8000 ... 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.ja...@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.ja...@gmail.com
