Skip to contentSkip to conversation

H1940 Boot Issues -> Executable Build Problems?

DISCUSSION Russell Morris 4 participants 9 messages Jan 5, 2011 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

Thanks,

... Russell

Quoted 1 line · On Sun, Jan 2, 2011 06:34 AM, <[email protected]> wrote:

My sincere apologies - as I never got that earlier email (but was having issues with Norton filtering my email, so I'm sure it was on my side .. :-().

Quoted 167 lines

To answer your question though - the MACHINE is h1940, and I have tried two different DISTRO's ... minimal and angstrom-2008.1. I am using the master branch of OpenEmbedded, and last updated it ~ 30 days ago.

Thoughts?

Thanks!

... Russell

Quoted 151 lines · Khem Raj
Quoted 9 lines · On Sat, Jan 1, 2011 at 10:34 AM, <[email protected]> wrote:

Hi,

As I have been debugging this it's looking more like a build issue - so let me try the developer group, in case someone here has seen this before.

Copying over the key point from below ... I (successfully) built the helloworld-image,

what was MACHINE and DISTRO and OpenEmbedded revision you used ? I think I asked same qestion when you posted this to oe-users ml. If you are not going to provide information then I am afraid not many can help you here

but cannot run the resulting helloworld binary on the target machine - it does execute under QEMU, which doesn't provide support this CPU (arm920t - armv4t). However, a functioning binary from the target (armv4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

Quoted 119 lines

Any thoughts on this? It seems that OpenEmbedded / bitbake may be using QEMU to create the binary for the target ... is that right (as it's what I have seen in a bit of poking around)? This would be a problem, as QEMU doesn't support the arm920t processor. Perhaps I have to apply the QEMU patch that adds this support to QEMU, or change my config to somehow create the executable in a different way?

Any suggestions would be greatly appreciated - as my current built (actually, rootfs) is not functioning on the target machine.

Thanks!

... Russell

Subject: Re: [Openembedded-users] H1940 Boot Issues
From: <[email protected]>
Date: Thu, Dec 30, 2010 11:36 PM
To: [email protected]

Hi,

OK, I haven't given up on this - and now it gets more interesting ... :-). It seems that OpenEmbedded is not properly building a binary for the ARM920T CPU (arm4t) - has anyone else seen this?

I built the helloworld-image, and cannot run the resulting helloworld binary on the target machine - but can run it under QEMU, which doesn't even support this CPU. However, a functioning binary from the target (arm4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

The config files seem to be set up for the right target machine, but the binary is not being built right for some reason. Does anyone have any ideas?

Thanks!

... Russell

Quoted 1 line · On Fri, Dec 24, 2010 09:20 AM, <[email protected]> wrote:

Hi,

I have tried quite a few more things here, still with no luck. It really does seem that OpenEmbedded does not properly / fully build an image that works on (real?) embedded systems ... :-(. I am out of things to try, but let me pass this info along in the hope that it will save others some time / grief if they try to do similar things.

I have tried several different formats / approaches to the rootfs, none of which work (except for the legacy Familiar Linux file system that I found). I cannot load the OpenEmbedded rootfs as an initrd, or when extracted to an SD card (as a "normal" file system, either copied from the ext2 file, or extracted from tar.gz). While this seems to be a rootfs issue, it still could be the build of init, as replacing the Familiar Linux init.sysvinit with the one generated by OpenEmbedded does in fact break the working file system. I tried reducing the size of generated rootfs (by setting IMAGE_ROOTFS_SIZE), but that doesn't seem to be working either (so I cannot use the OpenEmbedded rootfs as an initrd, as it is 64 MB, which seems to cause problems on the target system). BTW, the OpenEmbedded generated linuxrc file is just a link to /bin/busybox, which seems a bit strange - so perhaps this is the issue?

Hopefully this helps other folks - by not trying these same things.

... Russell

Quoted 5 lines · On Wed, Dec 22, 2010 11:28 PM, <[email protected]> wrote:

Hi,

Quoted 13 lines

I have been strugging with this for quite some now, and really am stuck - so I really would appreciate any thoughts or pointers anyone has! Let me try to explain my problem.

I have been able to build OpenEmbedded on my machine, with a target of either h1940 or qemuarm - and for the console-image both build just fine. I can use the kernel for both of these (on the appropriate target), but my issue is with the rootfs. If I use the OpenEmbedded built rootfs in qemuarm, targeted for either qemuarm or the h1940 (but always using the qemuarm kernel) everything works just fine.

My issue arises when trying to use the rootfs on the h1940 - I cannot get my system to boot, and actually INIT is never launched (but the kernel seems fine). If I take an old file system that I was able to find (from Familiar Linux, ~ 2004-2005 vintage), it works fine on my h1940 (with the kernel from OpenEmbedded!) ... so the issue seems to be the rootfs. If I just replace /sbin/init.sysvinit in the Familiar Linux file system with the one from OpenEmbedded - then I get kernel panic (and no init found it says ... :-(). Oddly enough, if I use the Familiar LInux file system with qemuarm - it doesn't work, I have file system errors (and kernel panic), but the OpenEmbedded built file system (even for the h1940) works just great).

So it seems that I have some sort of filesystem incompatibility ... or am I wrong? BTW, I can load the above mentioned filesystems as ext2 or ext3 in (OpenSUSE) Linux, no issues there.

Again, any suggestions of how to fix this would be greatly appreciated!

Thanks!

Quoted 8 lines

... Russell

_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________

Quoted 8 lines

Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________
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

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 07:47:18 2011
Received: from mail-yx0-f175.google.com ([209.85.213.175])

	by linuxtogo.org with esmtp (Exim 4.72)
	(envelope-from <[email protected]>) id 1PaN9S-0005ew-GI
	for [email protected];
	Wed, 05 Jan 2011 07:47:18 +0100
Received: by yxd5 with SMTP id 5so6229548yxd.6
	for <[email protected]>;
	Tue, 04 Jan 2011 22:46:54 -0800 (PST)

DKIM-Signature: v

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

here is updated patch

Quoted 17 lines · Khem Raj
Quoted 8 lines · Russell Morris

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

Quoted 7 lines

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

Quoted 9 lines

OK you seem to be one patient guy :) Here is totally untested patch for gcc. Please apply it on top of your openembedded. Then use DISTRO=minimal
or any other distro that uses gcc 4.5 and build OE from scratch again and see if that helps and report back.

Thanks
-Khem

recipes/gcc/gcc-4.5.inc +1 -0
index bac15ef..3e6fb75 100644
@@ -32,6 +32,7 @@ SRC_URI = "svn://gcc.gnu.org/svn/gcc/branches;module=${BRANCH} \
 	   file://arm-bswapsi2.patch \
 	   file://Makefile.in.patch \
 	   file://gcc-armv4-pass-fix-v4bx-to-ld.patch \
+	   file://arm-default-to-armv4t.patch \
 	   file://linaro/gcc-4.5-linaro-r99297.patch \
 	   file://linaro/gcc-4.5-linaro-r99298.patch \
 	   file://linaro/gcc-4.5-linaro-r99299.patch \
recipes/gcc/gcc-4.5/arm-default-to-armv4t.patch new file +13 -0
new file mode 100644
index 0000000..580fccb
@@ -0,0 +1,13 @@
+Index: gcc-4_5-branch/gcc/config/arm/linux-eabi.h
+===================================================================
+--- gcc-4_5-branch.orig/gcc/config/arm/linux-eabi.h
++++ gcc-4_5-branch/gcc/config/arm/linux-eabi.h
+@@ -44,7 +44,7 @@
+    The ARM10TDMI core is the default for armv5t, so set
+    SUBTARGET_CPU_DEFAULT to achieve this.  */
+ #undef  SUBTARGET_CPU_DEFAULT
+-#define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm10tdmi
++#define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm9tdmi
+ 
+ /* TARGET_BIG_ENDIAN_DEFAULT is set in
+    config.gcc for big endian configurations.  */
#3 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That looks suspiciously like
http://www.flickr.com/photos/quimgil/478715643/ :)

Quoted 4 lines · Khem Raj

here is updated patch

Quoted 33 lines
Quoted 32 lines · Khem Raj
Quoted 8 lines · Russell Morris

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

Quoted 7 lines

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

OK you seem to be one patient guy :) Here is totally untested patch for gcc. Please apply it on top of your openembedded. Then use DISTRO=minimal
or any other distro that uses gcc 4.5 and build OE from scratch again and see if that helps and report back.

Thanks
-Khem

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNJCzCMkyGM64RGpERAvW/AKCTiQztYmWbEMLOvxHWtP0TrfGSwgCgnIdQ Df+XY7rjrMPTZKaMxfAXwRg=
=JXQ8
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 6 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That looks suspiciously like
http://www.flickr.com/photos/quimgil/478715643/ :)

heh yes indeed no suspicion. I am just making sure that he is not getting bitten by potential clz instructions from libgcc because now it defaults to armv5te. If thats the case then we have to use --with-arch=${BASE_PACKAGE_ARCH} while configuring gcc and then it will compile the gcc runtime libraries with proper options for an arch.

Quoted 53 lines · Khem Raj
Quoted 4 lines

here is updated patch

Quoted 33 lines
Quoted 32 lines · Khem Raj
Quoted 8 lines · Russell Morris

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

Quoted 7 lines

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

OK you seem to be one patient guy :) Here is totally untested patch for gcc. Please apply it on top of your openembedded. Then use DISTRO=minimal
or any other distro that uses gcc 4.5 and build OE from scratch again and see if that helps and report back.

Thanks
-Khem

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNJCzCMkyGM64RGpERAvW/AKCTiQztYmWbEMLOvxHWtP0TrfGSwgCgnIdQ Df+XY7rjrMPTZKaMxfAXwRg=
=JXQ8
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#5 lore raw
In reply to Khem Raj

Hi,

As I don't know you that well, not sure if you're joking or not - but in any case my apologies if I seem impatient ... that's not my intention at least! Just trying to debug here, and keeping folks in the loop as I progress. If the armv4t builds don't really work I'm likely not the only person impacted, so I'd like to help others avoid the issue if possible.

I have applied the patch, and have started the build from scratch. Fingers crossed ... :-).

FYI - I did look in the old TMPDIR, and found that inside gcc-cross-initial (and intermediate), the test directory seemed to call out an armv5te, so I'm hopeful that this is the issue.

Thanks for all your help!

... Russell

Quoted 1 line · Khem Raj

here is updated patch

Quoted 27 lines · Khem Raj
Quoted 23 lines · Russell Morris
Quoted 8 lines

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

Quoted 7 lines

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

OK you seem to be one patient guy :) Here is totally untested patch for gcc. Please apply it on top of your openembedded. Then use DISTRO=minimal
or any other distro that uses gcc 4.5 and build OE from scratch again and see if that helps and report back.

Quoted 8 lines
Quoted 3 lines

Thanks
-Khem

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

From [email protected] Wed Jan 05 15:49:08 2011
Received: from vms173011pub.verizon.net ([206.46.173.11])

	by linuxtogo.org with esmtp (Exim 4.72)
	(envelope-from <[email protected]>) id 1PaUfk-0005d1-F0
	for [email protected];
	Wed, 05 Jan 2011 15:49:08 +0100
Received: from server ([unknown] [71.164.183.134]) by vms173011.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 08:48:44 -0600 (CST)
Received: from server (127.0.0.1) by server (Axigen)
	with ESMTPSA id 393506; Wed, 05 Jan 2011 08:48:38 -0600
Received: from [192.168.1.12] by rkmorris.us with HTTP; Wed,
	05 Jan 2011 08:48:36 -0600

From: Russell Morris <[email protected]>
Date: Wed, 05 Jan 2011 08:48:36 -0600
X-Mailer: Axigen WebMail
To: [email protected]
Message-id: <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]>
Importance: Normal
MIME-version: 1.0
X-AxigenVirus-Level: 1
X-AxigenSpam-Level: 6
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

#6 lore raw
In reply to Russell Morris

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 9 lines · Russell Morris

Hi,

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

DISTRO=angstrom-2008.1 generates armv4t binaries just fine over here.

regards,

Koen

Quoted 124 lines

Thanks,

... Russell

Quoted 1 line · On Sun, Jan 2, 2011 06:34 AM, <[email protected]> wrote:

My sincere apologies - as I never got that earlier email (but was having issues with Norton filtering my email, so I'm sure it was on my side .. :-().

Quoted 108 lines

To answer your question though - the MACHINE is h1940, and I have tried two different DISTRO's ... minimal and angstrom-2008.1. I am using the master branch of OpenEmbedded, and last updated it ~ 30 days ago.

Thoughts?

Thanks!

... Russell

Quoted 97 lines · Khem Raj
Quoted 9 lines · On Sat, Jan 1, 2011 at 10:34 AM, <[email protected]> wrote:

Hi,

As I have been debugging this it's looking more like a build issue - so let me try the developer group, in case someone here has seen this before.

Copying over the key point from below ... I (successfully) built the helloworld-image,

what was MACHINE and DISTRO and OpenEmbedded revision you used ? I think I asked same qestion when you posted this to oe-users ml. If you are not going to provide information then I am afraid not many can help you here

but cannot run the resulting helloworld binary on the target machine - it does execute under QEMU, which doesn't provide support this CPU (arm920t - armv4t). However, a functioning binary from the target (armv4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

Quoted 74 lines

Any thoughts on this? It seems that OpenEmbedded / bitbake may be using QEMU to create the binary for the target ... is that right (as it's what I have seen in a bit of poking around)? This would be a problem, as QEMU doesn't support the arm920t processor. Perhaps I have to apply the QEMU patch that adds this support to QEMU, or change my config to somehow create the executable in a different way?

Any suggestions would be greatly appreciated - as my current built (actually, rootfs) is not functioning on the target machine.

Thanks!

... Russell

Subject: Re: [Openembedded-users] H1940 Boot Issues
From: <[email protected]>
Date: Thu, Dec 30, 2010 11:36 PM
To: [email protected]

Hi,

OK, I haven't given up on this - and now it gets more interesting ... :-). It seems that OpenEmbedded is not properly building a binary for the ARM920T CPU (arm4t) - has anyone else seen this?

I built the helloworld-image, and cannot run the resulting helloworld binary on the target machine - but can run it under QEMU, which doesn't even support this CPU. However, a functioning binary from the target (arm4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

The config files seem to be set up for the right target machine, but the binary is not being built right for some reason. Does anyone have any ideas?

Thanks!

... Russell

Quoted 1 line · On Fri, Dec 24, 2010 09:20 AM, <[email protected]> wrote:

Hi,

Quoted 65 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

I have tried quite a few more things here, still with no luck. It really does seem that OpenEmbedded does not properly / fully build an image that works on (real?) embedded systems ... :-(. I am out of things to try, but let me pass this info along in the hope that it will save others some time / grief if they try to do similar things.

I have tried several different formats / approaches to the rootfs, none of which work (except for the legacy Familiar Linux file system that I found). I cannot load the OpenEmbedded rootfs as an initrd, or when extracted to an SD card (as a "normal" file system, either copied from the ext2 file, or extracted from tar.gz). While this seems to be a rootfs issue, it still could be the build of init, as replacing the Familiar Linux init.sysvinit with the one generated by OpenEmbedded does in fact break the working file system. I tried reducing the size of generated rootfs (by setting IMAGE_ROOTFS_SIZE), but that doesn't seem to be working either (so I cannot use the OpenEmbedded rootfs as an initrd, as it is 64 MB, which seems to cause problems on the target system). BTW, the OpenEmbedde

d generated linuxrc file is just a link to /bin/busybox, which seems a bit strange - so perhaps this is the issue?

Quoted 59 lines
Quoted 49 lines
Quoted 40 lines

Hopefully this helps other folks - by not trying these same things.

... Russell

Quoted 5 lines · On Wed, Dec 22, 2010 11:28 PM, <[email protected]> wrote:

Hi,

Quoted 13 lines

I have been strugging with this for quite some now, and really am stuck - so I really would appreciate any thoughts or pointers anyone has! Let me try to explain my problem.

I have been able to build OpenEmbedded on my machine, with a target of either h1940 or qemuarm - and for the console-image both build just fine. I can use the kernel for both of these (on the appropriate target), but my issue is with the rootfs. If I use the OpenEmbedded built rootfs in qemuarm, targeted for either qemuarm or the h1940 (but always using the qemuarm kernel) everything works just fine.

My issue arises when trying to use the rootfs on the h1940 - I cannot get my system to boot, and actually INIT is never launched (but the kernel seems fine). If I take an old file system that I was able to find (from Familiar Linux, ~ 2004-2005 vintage), it works fine on my h1940 (with the kernel from OpenEmbedded!) ... so the issue seems to be the rootfs. If I just replace /sbin/init.sysvinit in the Familiar Linux file system with the one from OpenEmbedded - then I get kernel panic (and no init found it says ... :-(). Oddly enough, if I use the Familiar LInux file system with qemuarm - it doesn't work, I have file system errors (and kernel panic), but the OpenEmbedded built file system (even for the h1940) works just great).

So it seems that I have some sort of filesystem incompatibility ... or am I wrong? BTW, I can load the above mentioned filesystems as ext2 or ext3 in (OpenSUSE) Linux, no issues there.

Again, any suggestions of how to fix this would be greatly appreciated!

Thanks!

Quoted 8 lines

... Russell

_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________

Quoted 8 lines

Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________
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

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNJDAsMkyGM64RGpERAnXbAJ4nw3gu1JA47X0xUMOHFJ1sA31aTACdFw1K mJcYeEnaLSmo0XaY0eXokUU=
=HU+c
-----END PGP SIGNATURE-----

A message that is not in the archive (sent off-list or not yet received): [email protected]

#8 lore raw
Quoted 1 line · Russell Morris

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.

#9 lore raw
Quoted 10 lines · Phil Blundell
Quoted 1 line · Russell Morris

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

Quoted 6 lines

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#10 lore raw
In reply to Koen Kooi
Quoted 8 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 4 lines · Russell Morris

Hi,

Quoted 7 lines
Quoted 5 lines

A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).

It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.

Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?

DISTRO=angstrom-2008.1 generates armv4t binaries just fine over here.

hmmm one of distro he tried was angstrom-2008.1. so this ay not be the issue then

Quoted 210 lines

regards,

Koen

Quoted 124 lines

Thanks,

... Russell

Quoted 1 line · On Sun, Jan 2, 2011 06:34  AM, <[email protected]> wrote:

My sincere apologies - as I never got that earlier email (but was having issues with Norton filtering my email, so I'm sure it was on my side .. :-().

Quoted 108 lines

To answer your question though - the MACHINE is h1940, and I have tried two different DISTRO's ... minimal and angstrom-2008.1. I am using the master branch of OpenEmbedded, and last updated it ~ 30 days ago.

Thoughts?

Thanks!

... Russell

Quoted 97 lines · Khem Raj
Quoted 9 lines · On Sat, Jan 1, 2011 at 10:34 AM, <[email protected]> wrote:

Hi,

As I have been debugging this it's looking more like a build issue - so let me try the developer group, in case someone here has seen this before.

Copying over the key point from below ... I (successfully) built the helloworld-image,

what was MACHINE and DISTRO and OpenEmbedded revision you used ? I think I asked same qestion when you posted this to oe-users ml. If you are not going to provide information then I am afraid not many can help you here

but cannot run the resulting helloworld binary on the target machine - it does execute under QEMU, which doesn't provide support this CPU (arm920t - armv4t). However, a functioning binary from the target (armv4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

Quoted 74 lines

Any thoughts on this? It seems that OpenEmbedded / bitbake may be using QEMU to create the binary for the target ... is that right (as it's what I have seen in a bit of poking around)? This would be a problem, as QEMU doesn't support the arm920t processor. Perhaps I have to apply the QEMU patch that adds this support to QEMU, or change my config to somehow create the executable in a different way?

Any suggestions would be greatly appreciated - as my current built (actually, rootfs) is not functioning on the target machine.

Thanks!

... Russell

Subject: Re: [Openembedded-users] H1940 Boot Issues
From: <[email protected]>
Date: Thu, Dec 30, 2010 11:36 PM
To: [email protected]

Hi,

OK, I haven't given up on this - and now it gets more interesting ... :-). It seems that OpenEmbedded is not properly building a binary for the ARM920T CPU (arm4t) - has anyone else seen this?

I built the helloworld-image, and cannot run the resulting helloworld binary on the target machine - but can run it under QEMU, which doesn't even support this CPU. However, a functioning binary from the target (arm4t) machine runs on the target, but not on QEMU (as expected). So it seems that OpenEmbedded is not building for the right machine (which is strange, as the OpenEmbedded built kernel works!).

The config files seem to be set up for the right target machine, but the binary is not being built right for some reason. Does anyone have any ideas?

Thanks!

... Russell

Quoted 1 line · On Fri, Dec 24, 2010 09:20 AM, <[email protected]> wrote:

Hi,

Quoted 65 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

I have tried quite a few more things here, still with no luck. It really does seem that OpenEmbedded does not properly / fully build an image that works on (real?) embedded systems ... :-(. I am out of things to try, but let me pass this info along in the hope that it will save others some time / grief if they try to do similar things.

I have tried several different formats / approaches to the rootfs, none of which work (except for the legacy Familiar Linux file system that I found). I cannot load the OpenEmbedded rootfs as an initrd, or when extracted to an SD card (as a "normal" file system, either copied from the ext2 file, or extracted from tar.gz). While this seems to be a rootfs issue, it still could be the build of init, as replacing the Familiar Linux init.sysvinit with the one generated by OpenEmbedded does in fact break the working file system. I tried reducing the size of generated rootfs (by setting IMAGE_ROOTFS_SIZE), but that doesn't seem to be working either (so I cannot use the OpenEmbedded rootfs as an initrd, as it is 64 MB, which seems to cause problems on the target system). BTW, the OpenEmbedde

 d generated linuxrc file is just a link to /bin/busybox, which seems a bit strange - so perhaps this is the issue?

Quoted 59 lines
Quoted 49 lines
Quoted 40 lines

Hopefully this helps other folks - by not trying these same things.

... Russell

Quoted 5 lines · On Wed, Dec 22, 2010 11:28 PM, <[email protected]> wrote:

Hi,

Quoted 13 lines

I have been strugging with this for quite some now, and really am stuck - so I really would appreciate any thoughts or pointers anyone has! Let me try to explain my problem.

I have been able to build OpenEmbedded on my machine, with a target of either h1940 or qemuarm - and for the console-image both build just fine. I can use the kernel for both of these (on the appropriate target), but my issue is with the rootfs. If I use the OpenEmbedded built rootfs in qemuarm, targeted for either qemuarm or the h1940 (but always using the qemuarm kernel) everything works just fine.

My issue arises when trying to use the rootfs on the h1940 - I cannot get my system to boot, and actually INIT is never launched (but the kernel seems fine). If I take an old file system that I was able to find (from Familiar Linux, ~ 2004-2005 vintage), it works fine on my h1940 (with the kernel from OpenEmbedded!) ... so the issue seems to be the rootfs. If I just replace /sbin/init.sysvinit in the Familiar Linux file system with the one from OpenEmbedded - then I get kernel panic (and no init found it says ... :-(). Oddly enough, if I use the Familiar LInux file system with qemuarm - it doesn't work, I have file system errors (and kernel panic), but the OpenEmbedded built file system (even for the h1940) works just great).

So it seems that I have some sort of filesystem incompatibility ... or am I wrong? BTW, I can load the above mentioned filesystems as ext2 or ext3 in (OpenSUSE) Linux, no issues there.

Again, any suggestions of how to fix this would be greatly appreciated!

Thanks!

Quoted 8 lines

... Russell

_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________

Quoted 8 lines

Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________
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

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNJDAsMkyGM64RGpERAnXbAJ4nw3gu1JA47X0xUMOHFJ1sA31aTACdFw1K mJcYeEnaLSmo0XaY0eXokUU=
=HU+c
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel