From: Russell Morris <openembedded@rkmorris.us>
To: openembedded-devel@lists.openembedded.org
Subject: Re: H1940 Boot Issues -> Executable Build Problems?
Date: Wed, 05 Jan 2011 12:49:34 -0600 [thread overview]
Message-ID: <1294253374472299500@rkmorris.us> (raw)
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
On Wed, Jan 5, 2011 11:45 AM, Khem Raj <raj.khem@gmail.com> wrote:
>
On Wed, Jan 5, 2011 at 7:11 AM, Phil Blundell <philb@gnu.org> wrote:
> > On Wed, 2011-01-05 at 08:48 -0600, Russell Morris wrote:
> >> 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 it
> >
> > _______________________________________________
> > 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
>
From gcho-openembedded-devel@m.gmane.org 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 <gcho-openembedded-devel@m.gmane.org>)
id 1PaZfT-0000sz-Nl for openembedded-devel@lists.openembedded.org;
Wed, 05 Jan 2011 21:09:11 +0100
Received: from list by lo.gmane.org with local (Exim 4.69)
(envelope-from <gcho-openembedded-devel@m.gmane.org>)
id 1PaZf5-00071c-KC for openembedded-devel@lists.openembedded.org;
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 <openembedded-devel@lists.openembedded.org>;
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 <openembedded-devel@lists.openembedded.org>;
Wed, 05 Jan 2011 21:08:47 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: openembedded-devel@lists.openembedded.org
From: Koen Kooi <k.kooi@student.utwente.nl>
Date: Wed, 05 Jan 2011 21:08:33 +0100
Lines: 24
Message-ID: <ig2j41$65t$1@dough.gmane.org>
References: <1294253374472299500@rkmorris.us>
Mime-Version: 1.0
Content-Type: text/plain; charset
next reply other threads:[~2011-01-05 19:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 18:49 Russell Morris [this message]
2011-01-05 20:23 ` H1940 Boot Issues -> Executable Build Problems? Khem Raj
2011-01-05 23:07 ` Russell Morris
[not found] ` <1294288661406628500@rkmorris.us>
2011-01-06 6:15 ` Khem Raj
2011-01-06 14:30 ` Russell Morris
2011-01-06 7:54 ` Koen Kooi
[not found] ` <AANLkTimaX4kPer1-+UFRq-80PBFrcT8oxorC=SHwHWFU@mail.gmail.com>
2011-01-06 14:28 ` Russell Morris
[not found] ` <201101061721.30643.anarsoul@gmail.com>
[not found] ` <1294330448552193500@rkmorris.us>
2011-01-06 16:32 ` Vasily Khoruzhick
2011-01-06 16:50 ` Russell Morris
[not found] ` <201101062040.16993.anarsoul@gmail.com>
2011-01-06 23:41 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-01-08 14:52 Russell Morris
2011-01-05 3:32 Russell Morris
[not found] ` <AANLkTim22AbOed09n1Ez6A2gtJhnjUDm3Ksv+tRDnn=8@mail.gmail.com>
2011-01-05 7:42 ` Khem Raj
2011-01-05 8:33 ` Koen Kooi
2011-01-05 8:49 ` Khem Raj
2011-01-05 14:47 ` Russell Morris
2011-01-05 8:47 ` Koen Kooi
[not found] ` <1294238916100625500@rkmorris.us>
2011-01-05 15:11 ` Phil Blundell
2011-01-05 17:45 ` Khem Raj
2011-01-05 17:20 ` Khem Raj
2011-01-01 18:34 openembedded
2011-01-02 6:44 ` Khem Raj
2011-01-02 12:34 ` openembedded
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1294253374472299500@rkmorris.us \
--to=openembedded@rkmorris.us \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.