H1940 Boot Issues -> Executable Build Problems?
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
From [email protected] Wed Jan 05 21:09:11 2011
Received: from lo.gmane.org ([80.91.229.12])
by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <[email protected]>) id 1PaZfT-0000sz-Nl for [email protected]; Wed, 05 Jan 2011 21:09:11 +0100 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from <[email protected]>) id 1PaZf5-00071c-KC for [email protected]; Wed, 05 Jan 2011 21:08:47 +0100 Received: from ip545070eb.adsl-surfen.hetnet.nl ([84.80.112.235]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <[email protected]>; Wed, 05 Jan 2011 21:08:47 +0100 Received: from k.kooi by ip545070eb.adsl-surfen.hetnet.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <[email protected]>; Wed, 05 Jan 2011 21:08:47 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: [email protected]
From: Koen Kooi <[email protected]>
Date: Wed, 05 Jan 2011 21:08:33 +0100
Lines: 24
Message-ID: <[email protected]>
References: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset
Quoted 9 lines · Russell Morris
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
OK thats bad. Now can you recompile the kernel with user debugging enabled ? and reboot then it will dump lot more info on console on error you need to turn on CONFIG_DEBUG_USER in .config
Quoted 6 lines
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
thats EABI version it has nothing to do with ARM architecture versions
Quoted 3 lines
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
OK good so it seems there is still some intructions generated which are not supported in armv4t
Quoted 1 line
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
Yes it wont change I think.
Quoted 4 lines
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of
pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */
thats just a gcc dejaGNU regression testcase it does not mean anything for compiling the root file system
Quoted 7 lines
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
as koen suggested try it with angstrom-2008 and see if that helps too.
Quoted 51 lines
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Hi,
A few answers / thoughts, below (marked with RMo).
Thanks for all the help and suggestions!
... Russell
Quoted 1 line · Khem Raj
On Wed, Jan 5, 2011 at 10:49 AM, Russell Morris
Quoted 9 lines
Quoted 8 lines · <[email protected]> wrote:
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
Quoted 5 lines
Quoted 1 line
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
OK thats bad. Now can you recompile the kernel with user debugging enabled ? and reboot then it will dump lot more info on console on error you need to turn on
CONFIG_DEBUG_USERin .config
[RMo] Sorry, a dumb question here - but how do I do this? I can see .config in the temp directory - is this where you want me to modify it?
Quoted 9 lines
Quoted 7 lines
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
thats EABI version it has nothing to do with ARM architecture versions
[RMo] OK, thanks!
Quoted 7 lines
Quoted 4 lines
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
OK good so it seems there is still some intructions generated which are not supported in armv4t
[RMo] That's what it seems like. To confirm - what is the best way to test this ... with qemu-arm, and/or on the target? Just trying to make sure I test it in a way that makes sense!
Quoted 4 lines
Quoted 2 lines
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
Yes it wont change I think.
[RMo] Definitely agreed.
Quoted 9 lines
Quoted 5 lines
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of
pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */thats just a gcc dejaGNU regression testcase it does not mean anything for compiling the root file system
[RMo] Ok, thanks!
Quoted 9 lines
Quoted 7 lines
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
as koen suggested try it with angstrom-2008 and see if that helps too.
[RMo] Absolutely - started already. I thought you were looking for the minimal distro, but I may have misunderstood. In any case, trying this now ... :-).
Quoted 53 lines
Quoted 47 lines
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
From [email protected] Thu Jan 06 05:38:34 2011
Received: from vms173005pub.verizon.net ([206.46.173.5])
by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <[email protected]>) id 1PahcQ-0007mo-86 for [email protected]; Thu, 06 Jan 2011 05:38:34 +0100 Received: from server ([unknown] [71.164.183.134]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <[email protected]> for [email protected]; Wed, 05 Jan 2011 22:37:52 -0600 (CST) Received: from server (127.0.0.1) by server (Axigen) with ESMTPSA id 105A1C; Wed, 05 Jan 2011 22:37:43 -0600 Received: from [192.168.1.10] by rkmorris.us with HTTP; Wed, 05 Jan 2011 22:37:41 -0600
From: Russell Morris <[email protected]>
Date: Wed, 05 Jan 2011 22:37:41 -0600
X-Mailer: Axigen WebMail
To: [email protected]
Message-id: <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]>
<[email protected]> <[email protected]>
Importance: Normal
MIME-version: 1.0
X-AxigenVirus-Level: 1
X-AxigenSpam-Level: 5
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.11
Subject: Re: [oe] H1940 Boot Issues -> Executable Build Problems?
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.11
Precedence: list
Reply-To: [email protected]
List-Id: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel.lists.openembedded.org>
List-Unsubscribe: <http://lists.linuxtogo.org/cgi-bin/mailman/options/openembedded-devel>,
<mailto:[email protected]?subject
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Russell Morris
Hi,
OK, a few more updates ...
- I built using the angstrom-2008.1 distro, but I have the same issue. I also ran the helloworld application on the target as well, getting the error message "Illegal instruction" (the same as qemu, which I guess is good).
If you can reproduce the issue on target then I would suggest that run the helloworld under gdb or gdbserver on target and see where its happening.
Quoted 164 lines
- I found the .config file that you are referring to, and made this change. I built and ran the debug kernel, but no more information is provided (other than "Illegal instruction").
- as a side note, I have to editsumversion.cto fix a "known" issue (http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-05/msg08279.html). You may want to update this in the master branch.Any other ideas?
Thanks,
... RussellQuoted 142 lines · Russell Morris
Hi,
A few answers / thoughts, below (marked with RMo).
Thanks for all the help and suggestions!
... Russell
Quoted 1 line · Khem Raj
On Wed, Jan 5, 2011 at 10:49 AM, Russell Morris
Quoted 9 lines
Quoted 8 lines · <[email protected]> wrote:
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
Quoted 5 lines
Quoted 1 line
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
OK thats bad. Now can you recompile the kernel with user debugging enabled ? and reboot then it will dump lot more info on console on error you need to turn on
CONFIG_DEBUG_USERin .config[RMo] Sorry, a dumb question here - but how do I do this? I can see .config in the temp directory - is this where you want me to modify it?
Quoted 9 lines
Quoted 7 lines
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
thats EABI version it has nothing to do with ARM architecture versions
[RMo] OK, thanks!
Quoted 7 lines
Quoted 4 lines
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
OK good so it seems there is still some intructions generated which are not supported in armv4t
[RMo] That's what it seems like. To confirm - what is the best way to test this ... with qemu-arm, and/or on the target? Just trying to make sure I test it in a way that makes sense!
Quoted 4 lines
Quoted 2 lines
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
Yes it wont change I think.
[RMo] Definitely agreed.
Quoted 9 lines
Quoted 5 lines
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of
pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */thats just a gcc dejaGNU regression testcase it does not mean anything for compiling the root file system
[RMo] Ok, thanks!
Quoted 9 lines
Quoted 7 lines
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
as koen suggested try it with angstrom-2008 and see if that helps too.
[RMo] Absolutely - started already. I thought you were looking for the minimal distro, but I may have misunderstood. In any case, trying this now ... :-).
Quoted 53 lines
Quoted 47 lines
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Hi,
Unfortunately I can't really do much on the target - as I can't get to the point where I can log in (no ssh connection, no local keyboard, etc.) ... :-(. I may be able to try to debug it when run through qemu-arm ... have you ever tried that?
I'll do some poking around to see if this is possible.
Thanks,
... Russell
Quoted 1 line · Khem Raj
Quoted 175 lines · Russell Morris
Quoted 4 lines
Hi,
OK, a few more updates ...
- I built using the angstrom-2008.1 distro, but I have the same issue. I also ran the helloworld application on the target as well, getting the error message "Illegal instruction" (the same as qemu, which I guess is good).If you can reproduce the issue on target then I would suggest that run the helloworld under gdb or gdbserver on target and see where its happening.
Quoted 159 lines
- I found the .config file that you are referring to, and made this change. I built and ran the debug kernel, but no more information is provided (other than "Illegal instruction").
- as a side note, I have to editsumversion.cto fix a "known" issue (http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-05/msg08279.html). You may want to update this in the master branch.Any other ideas?
Thanks,
... RussellQuoted 142 lines · Russell Morris
Hi,
A few answers / thoughts, below (marked with RMo).
Thanks for all the help and suggestions!
... Russell
Quoted 1 line · Khem Raj
On Wed, Jan 5, 2011 at 10:49 AM, Russell Morris
Quoted 9 lines
Quoted 8 lines · <[email protected]> wrote:
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
Quoted 5 lines
Quoted 1 line
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
OK thats bad. Now can you recompile the kernel with user debugging enabled ? and reboot then it will dump lot more info on console on error you need to turn on
CONFIG_DEBUG_USERin .config[RMo] Sorry, a dumb question here - but how do I do this? I can see .config in the temp directory - is this where you want me to modify it?
Quoted 9 lines
Quoted 7 lines
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
thats EABI version it has nothing to do with ARM architecture versions
[RMo] OK, thanks!
Quoted 7 lines
Quoted 4 lines
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
OK good so it seems there is still some intructions generated which are not supported in armv4t
[RMo] That's what it seems like. To confirm - what is the best way to test this ... with qemu-arm, and/or on the target? Just trying to make sure I test it in a way that makes sense!
Quoted 4 lines
Quoted 2 lines
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
Yes it wont change I think.
[RMo] Definitely agreed.
Quoted 9 lines
Quoted 5 lines
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of
pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */thats just a gcc dejaGNU regression testcase it does not mean anything for compiling the root file system
[RMo] Ok, thanks!
Quoted 9 lines
Quoted 7 lines
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
as koen suggested try it with angstrom-2008 and see if that helps too.
[RMo] Absolutely - started already. I thought you were looking for the minimal distro, but I may have misunderstood. In any case, trying this now ... :-).
Quoted 53 lines
Quoted 47 lines
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
From [email protected] Thu Jan 06 15:38:29 2011
Received: from vms173009pub.verizon.net ([206.46.173.9])
by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <[email protected]>) id 1Paqyz-00080R-46 for [email protected]; Thu, 06 Jan 2011 15:38:29 +0100 Received: from server ([unknown] [71.164.183.134]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <[email protected]> for [email protected]; Thu, 06 Jan 2011 08:37:58 -0600 (CST) Received: from server (127.0.0.1) by server (Axigen) with ESMTPSA id 1BE82C; Thu, 06 Jan 2011 08:37:51 -0600 Received: from [192.168.1.12] by rkmorris.us with HTTP; Thu, 06 Jan 2011 08:37:48 -0600
From: Russell Morris <[email protected]>
Date: Thu, 06 Jan 2011 08:37:48 -0600
X-Mailer: Axigen WebMail
To: [email protected]
Message-id: <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]>
<[email protected]> <[email protected]> <[email protected]> <[email protected]>
Importance: Normal
MIME-version: 1.0
X-AxigenVirus-Level: 1
X-AxigenSpam-Level: 5
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.11
Subject: Re: [oe] H1940 Boot Issues -> Executable Build Problems?
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.11
Precedence: list
Reply-To: [email protected]
List-Id: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel.lists.openembedded.org>
List-Unsubscribe: <http://lists.linuxtogo.org/cgi-bin/mailman/options/openembedded-devel>,
<mailto:[email protected]?subject
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 6 lines · Russell Morris
Hi,
OK, a few more updates ...
- I built using the angstrom-2008.1 distro, but I have the same issue. I also ran the helloworld application on the target as well, getting the error message "Illegal instruction" (the same as qemu, which I guess is good).
- I found the .config file that you are referring to, and made this change. I built and ran the debug kernel, but no more information is provided (other than "Illegal instruction").
- as a side note, I have to editsumversion.cto fix a "known" issue (http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-05/msg08279.html). You may want to update this in the master branch.
Does your kernel have EABI turned on? If it's built using linux.inc in OE it will, but if it isn't using linux.inc, double check. Or add 'require linux.inc' to the recipe, that usually helps a lot. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNJXVPMkyGM64RGpERAn1YAJ0ZDBCI50yTboMvzrKs6l5Upb3kGACgiN9J XlKDkdcTtrk74k7QmIhVlQs=
=pSaG
-----END PGP SIGNATURE-----
A message that is not in the archive (sent off-list or not yet received): [email protected]
You bet - attached!
Also, just to make it clear - I'm not booting in to this executable. Rather, I'm using the (old, Familiar Linux) rootfs that I have found seems to work (together with my OE kernel), and trying to run this once I get to runlevel 5 (i.e. via a script in rc5.d that calls this). I could be wrong, but I don't think this is the problem though - as I get the same issue when running the executable using qemu-arm (with an armv4t as the target ... it works fine for armv5te).
Does the attached work for you? This could definitely still be operator error (i.e. me)!
Thanks,
... Russell
Quoted 1 line · Khem Raj
Quoted 178 lines · Russell Morris
Quoted 8 lines
Hi,
OK, a few more updates ...
- I built using the angstrom-2008.1 distro, but I have the same issue. I also ran the helloworld application on the target as well, getting the error message "Illegal instruction" (the same as qemu, which I guess is good).
- I found the .config file that you are referring to, and made this change. I built and ran the debug kernel, but no more information is provided (other than "Illegal instruction").
- as a side note, I have to editsumversion.cto fix a "known" issue (http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-05/msg08279.html). You may want to update this in the master branch.Any other ideas?
Please post the helloworld binary which you are booting into. I think the seems to be some other issue
Quoted 155 lines
Thanks,
... RussellQuoted 142 lines · Russell Morris
Hi,
A few answers / thoughts, below (marked with RMo).
Thanks for all the help and suggestions!
... Russell
Quoted 1 line · Khem Raj
On Wed, Jan 5, 2011 at 10:49 AM, Russell Morris
Quoted 9 lines
Quoted 8 lines · <[email protected]> wrote:
Hi,
Let me try to answer a few questions in one email ... :-). First of all, I tried the patch - unfortunately no joy. It does the same thing as earlier builds - let me try to explain, which will hopefully also answer the questions below.
Quoted 5 lines
Quoted 1 line
I applied the patch, and rebuilt from scratch with the minimal distro (deleted the TMPDIR completely before building). I built the helloworld-image, to get a statically linked executable, and also because it's a pretty small (=faster) build.
OK thats bad. Now can you recompile the kernel with user debugging enabled ? and reboot then it will dump lot more info on console on error you need to turn on
CONFIG_DEBUG_USERin .config[RMo] Sorry, a dumb question here - but how do I do this? I can see .config in the temp directory - is this where you want me to modify it?
Quoted 9 lines
Quoted 7 lines
I then looked at the helloworld executable, and a few interesting notes,
- if I readelf -h helloworld, it reports "Version5 EABI" ... so I assume arm5te still?
thats EABI version it has nothing to do with ARM architecture versions
[RMo] OK, thanks!
Quoted 7 lines
Quoted 4 lines
- if I try to run helloworld using qemu-arm, it runs fine ... with no cpu selected (but I did some checking, and the default cpu for qemu-arm is the arm5te). If I try to run with a -cpu arm920t option I get the error message "qemu: uncaught target signal 4 (Illegal instruction) - core dumped"
OK good so it seems there is still some intructions generated which are not supported in armv4t
[RMo] That's what it seems like. To confirm - what is the best way to test this ... with qemu-arm, and/or on the target? Just trying to make sure I test it in a way that makes sense!
Quoted 4 lines
Quoted 2 lines
- I was not able to run this on the target right now, as I'm not near it ... but when I did before I either got a core dump (illegal instruction), or it said basically that the file was not found (depending on the executable I tried to run).
Yes it wont change I think.
[RMo] Definitely agreed.
Quoted 9 lines
Quoted 5 lines
One more interesting fact - if I go inside TMPDIR, and then inside work/armv4t-oe-linux-gnueabi/gcc-cross-4.5-r28.0+svnr167948/gcc-4_5-branch/testsuite/gcc.target/arm, there is some sort of test file, with a filename of
pr42235.c. Oddly enough the first line in this file says ... /* { dg-options "-mthumb -O2 -march=armv5te" } */thats just a gcc dejaGNU regression testcase it does not mean anything for compiling the root file system
[RMo] Ok, thanks!
Quoted 9 lines
Quoted 7 lines
Hopefully this all makes sense. I think this says that the executable is still targeting an armv5te ... but I could be wrong! Unfortunately it wouldn't be the first time I was off base, and certaintly it won't be the last ... :-(.
Thanks for all your help!
as koen suggested try it with angstrom-2008 and see if that helps too.
[RMo] Absolutely - started already. I thought you were looking for the minimal distro, but I may have misunderstood. In any case, trying this now ... :-).
Quoted 53 lines
Quoted 47 lines
... Russell
Quoted 1 line · Khem Raj
Quoted 26 lines · Phil Blundell
Quoted 10 lines · Russell Morris
Quoted 1 line
Just to confirm - have you run these on an armv4t target? Only asking because my build completes fine, but the executables don't seem to run on the target.
What exactly happens when you try to run those executables? Have you inspected them to see if they look like the right kind of thing, and/or compared them to working ones?
p.
yes as Phil asked you should try to localize the offending code in the faulty binary. So try to enable
kernel debugging messages so it tells you where its faulting. Secondly if you can take a working system
and see if the new binary faults in same way ? if not then link the binary statically and run it again on working
system and see if it faults again. If it does then you can debug itQuoted 6 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develQuoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · On Thursday 06 January 2011 18:14:08 Russell Morris wrote:
Hi Vasily,
Absolutely! I'm very glad to hear that you have it working on an h1940. I think I'm likely the problem ... :-(.
The file is attached. Do you have any suggestions? If you don't mind, could you share your local.conf file for me to try also?
Thanks!!!
Here it is, however it's not for minimal distro, and machine is rx1950 (seems I lost one for rx1950, but I'm sure that it differs only in machine name)
What kernel do you use on your h1940? One built via OE?
Regards
Vasily
P.S. Your mailer inserts too much empty lines in message, could you fix it somehow please? :)
#
# OpenEmbedded local configuration file (sample)
#
# Please visit the Wiki at http://openembedded.org/ for more info. #
#
# Be SURE to read this file in its entirety and the GettingStarted page on the
# wiki before proceeding.
#
# Once you have done that, remove the line at the end of this
# file and build away.
#
# WARNING: lines starting with a space (' ') will result in parse failures.
# Remove '# ' from commented lines to activate them.
#
# NOTE: Do NOT use $HOME in your paths, BitBake does NOT expand ~ for you. If you
# must have paths relative to your homedir use ${HOME} (note the {}'s there
# you MUST have them for the variable expansion to be done by BitBake). Your
# paths should all be absolute paths (They should all start with a / after
# expansion. Stuff like starting with ${HOME} or ${TOPDIR} is ok).# Use this to specify where BitBake should place the downloaded sources into DL_DIR = "/home/distfiles"
# Delete the line below. Then specify which .bb files to consider for
# your build. Typically this will be something like BBFILES = "/path/to/openembedded/recipes/*/*.bb" BBFILES = "/home/anarsoul/work/openembedded/openembedded/recipes/*/*.bb"
# Use the BBMASK below to instruct BitBake to _NOT_ consider some .bb files # This is a regulary expression, so be sure to get your parenthesis balanced. BBMASK = ""
# Uncomment this if your host distribution has recent enough Linux # Kernel header files. Utilities we use to generate certain types of
# target filesystems need somewhat recent header files. # ASSUME_PROVIDED += "linux-libc-headers-native"
# Uncomment this if you want to use a prebuilt toolchain. You will need to
# provide packages for toolchain and additional libraries yourself. You also
# have to set PATH in your environment to make sure BitBake finds additional binaries.
# ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc virtual/libc"# Uncomment this if you are building Linux 2.4 Embedix kernels.
# i.e. openzaurus-sa-2.4.18 and openzaurus-pxa-2.4.18 - and don't forget # to rename the binaries as instructed in the Wiki. # Most users do not need this anymore thankfully! # ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95"
# Select between multiple alternative providers, if more than one is eligible. PREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie" PREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11"PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-intermediate:gcc-cross-intermediate" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross" PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross" PREFERRED_VERSION_mupdf = "0.6"
# Uncomment this to specify where BitBake should create its temporary files. # Note that a full build of everything in OpenEmbedded will take GigaBytes of hard
# disk space, so make sure to free enough space. The default TMPDIR is # <build directory>/tmp # Don't use symlinks in in the path to avoid problems # TMPDIR = /usr/local/projects/oetmp
# Uncomment this to specify a machine to build for. See the conf directory
# for machines currently known to OpenEmbedded. This will automatically take care # of TARGET_ARCH MACHINE = "rx1950"
# Use this to specify the target architecture. Note that this is only
# needed when building for a machine not known to OpenEmbedded. Better use # the MACHINE attribute (see above) # TARGET_ARCH = "arm"
# Use this to specify the target operating system. The default is "linux",
# for a normal linux system with glibc. Set this to "linux-uclibc" if you want # to build a uclibc based system. # Normally the DISTRO of your choosing will take care of this # TARGET_OS = "linux" # TARGET_OS = "linux-uclibc"
# Uncomment this to select a distribution policy. See the conf directory
# for distributions currently known to OpenEmbedded. # Although it no longer contain version number in the (file-)name # openzaurus-unstable is a so called "versioned" distro, i.e. they # explicitely select specific versions of various packages. # Stay away from unversioned distros unless you really know what you are doing DISTRO = "jlime-2010.1"
# So far, angstrom.conf sets ENABLE_BINARY_LOCALE_GENERATION
# to generate binary locale packages at build time using qemu-native and # thereby guarantee i18n support on all devices. If your build breaks on # qemu-native consider disabling ENABLE_BINARY_LOCALE_GENERATION (note that # this breaks i18n on devices with less than 128MB RAM) or installing # a working third-party qemu (e.g. provided by your distribution) and # adding qemu-native to ASSUME_PROVIDED. Caveat emptor, since third-party # qemus lack patches needed to work with various OE targets. # ENABLE_BINARY_LOCALE_GENERATION = "0" # ASSUME_PROVIDED += "qemu-native"
# If ENABLE_BINARY_LOCALE_GENERATION is set to "1", you can limit locales
# generated to the list provided by GLIBC_GENERATE_LOCALES. This is huge # time-savior for developmental builds. Format: list of locale.encoding pairs # with spaces as separators. GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 ru_RU.UTF-8"
# Uncomment this to select a particular major kernel version if the MACHINE setting
# supports more than one major kernel version. Currently this is suported by the # following MACHINE types: poodle, tosa and simpad. # MACHINE_KERNEL_VERSION = "2.6"
# Uncomment one of these to build packages during the build process. # This is done automatically if you set DISTRO (see above) # INHERIT = "package_ipk"
# INHERIT = "package_tar"
#INHERIT += "rm_work"
INHERIT += "shr-mirrors"
# Add the required image file system types below. Valid are # jffs2, tar(.gz|bz2), cpio(.gz), cramfs, ext2(.gz), ext3(.gz) # squashfs, squashfs-lzmaIMAGE_FSTYPES = "tar"
# Uncomment this if you want to keep the temporary rootfs # diretory, this can be useful during development. # (Note that this rootfs is NOT usuable as NFS export.) # IMAGE_KEEPROOTFS = "1"
# Uncomment this to enable the use of ccache when building. Due to
# the nature of our builds this is only helpful in cases when one
# is rebuilding a recipe or set of recipes, repeatedly.
# CCACHE = "${@bb.which(bb.data.getVar('PATH', d, 1), 'ccache') and 'ccache '}"# Uncomment this to disable the parse cache (not recommended). # CACHE = ""
# Uncomment this if you want BitBake to emit debugging output # BBDEBUG = "yes"
# Use DEBUG_BUILD to build packages with DEBUG_OPTIMIZATION instead of # FULL_OPTIMIZATION.
#
# DEBUG_BUILD = "1"
# If you want to have unstripped ready-to-debug binaries, set this to "no",
# although for debugging you can use automatically produced -dbg packages. # If you need to have completely undebuggable builds, set this to "full", # by default gnu.debuglink section is left in the binaries after stripping, so # this might be useful if you want to have checksum-level binary consistency # across successive builds. # PACKAGE_STRIP = "no"
# Uncomment these to build a package such that you can use gprof to profile it. # NOTE: This will only work with 'linux' targets, not
# 'linux-uclibc', as uClibc doesn't provide the necessary
# object files. Also, don't build glibc itself with these
# flags, or it'll fail to build.
#
# PROFILE_OPTIMIZATION = "-pg"
# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"
# LDFLAGS =+ "-pg"# Uncomment this to enable parallel make.
# This allows make to spawn mutliple processes to take advantage of multiple
# processors. Useful on SMP machines. This may break some packages - we're # in the process of marking these so let us know if you find any. PARALLEL_MAKE = "-j4"
# Uncomment to run multiple bitbake threads in parallel.
# Bitbake can do multiple jobs in parallel: Its a good idea make use of
# all available resources: e.g. to download sources while some other # piece of software is compiled. # BB_NUMBER_THREADS = "2"
# Uncomment this if you want BitBake to emit the log if a build fails. BBINCLUDELOGS = "yes"
# Specifies a location to search for pre-generated tarballs when fetching
# a cvs:// URI. Outcomment this, if you always want to pull directly from CVS. #CVS_TARBALL_STASH = ""
# Uncomment this if you want to install shared libraries directly under their SONAME,
# rather than installing as the full version and symlinking to the SONAME. # PACKAGE_SNAP_LIB_SYMLINKS = "1"
Hi,
Well, let me try this. The only real difference that I see is the distro - agreed? I'll give that a shot though!
The kernel I used is from OE (targeting the h1940).
Thanks,
... Russell
PS: Sorry, not sure what the mailer is doing ... :-(.
Quoted 1 line · Vasily Khoruzhick
Quoted 13 lines · On Thursday 06 January 2011 18:14:08 Russell Morris wrote:
Quoted 9 lines
Hi Vasily,
Absolutely! I'm very glad to hear that you have it working on an h1940. I think I'm likely the problem ... :-(.
The file is attached. Do you have any suggestions? If you don't mind, could you share your local.conf file for me to try also?
Thanks!!!
Here it is, however it's not for minimal distro, and machine is rx1950 (seems I lost one for rx1950, but I'm sure that it differs only in machine name)
Quoted 8 lines
What kernel do you use on your h1940? One built via OE?
Regards
Vasily
P.S. Your mailer inserts too much empty lines in message, could you fix it somehow please? :)
From [email protected] Thu Jan 06 19:42:03 2011
Received: from mail-ey0-f175.google.com ([209.85.215.175])
by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <[email protected]>) id 1Paumh-0006Xm-1J for [email protected]; Thu, 06 Jan 2011 19:42:03 +0100 Received: by eya28 with SMTP id 28so7301262eya.6 for <[email protected]>; Thu, 06 Jan 2011 10:41:38 -0800 (PST)
DKIM-Signature: v
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Vasily Khoruzhick
Quoted 1 line · On Thursday 06 January 2011 18:50:28 Russell Morris wrote:
The kernel I used is from OE (targeting the h1940).
AFAIK it's pretty old. I'm using self-built kernel, linux-next tree with some extra patches. I can share it, so you can test if kernel is guilty :)
yeah that would be nice. May be the way aux vectors are passed to application could mean
that libc tried to use wrong AT_HWCAPS which could mean that it tries to access cp15 which is absent on this
processor can result in illegal instrs or it enables things like VFP which again is absent so many things
can cause this problem. So I think finding if auxiliary vector is passed correctly is important.
Quoted 8 lines
Regards
Vasily_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel