Skip to contentSkip to conversation

Machine Configuration

DISCUSSION Russell Morris 3 participants 5 messages Oct 20, 2011 – Oct 21, 2011 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

I am trying to do some builds for an am3517-evm ... but the machine configuration doesn't seem to be working (or I'm doing it wrong, more likely ... :-().

I have successfully built console-image for qemuarm, and then use oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh update) - but then when I try to build for this machine I see the following ...

OE Build Configuration:

BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2011.10-core"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"

So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone else having this issue? Any suggestions of how to fix this?

Thanks!

... Russell

#1 lore raw
Quoted 16 lines · Russell Morris

Hi,

I am trying to do some builds for an am3517-evm ... but the machine configuration doesn't seem to be working (or I'm doing it wrong, more likely ... :-().

I have successfully built console-image for qemuarm, and then use oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh update) - but then when I try to build for this machine I see the following ...

OE Build Configuration:

BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2011.10-core"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"
Quoted 1 line

So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone else having this issue? Any suggestions of how to fix this?

You need to always specify MACHINE="am3517-evm" on your command line, e.g.
% MACHINE="am3517-evm" bitbake systemd-image

Alternatively, you can add just a single line to conf/local.conf and then it will be "sticky"

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#2 lore raw

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

Op 20-10-11 21:17, Gary Thomas schreef:

Quoted 18 lines · Russell Morris
Quoted 17 lines

Hi,

I am trying to do some builds for an am3517-evm ... but the machine configuration doesn't seem to be working (or I'm doing it wrong, more likely ... :-().

I have successfully built console-image for qemuarm, and then use oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh update) - but then when I try to build for this machine I see the following ...

OE Build Configuration: BB_VERSION = "1.13.3" TARGET_ARCH
= "arm" TARGET_OS = "linux-gnueabi" MACHINE =
"qemuarm" DISTRO = "angstrom" DISTRO_VERSION =
"v2011.10-core" TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"

Quoted 8 lines
Quoted 2 lines

So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone else having this issue? Any suggestions of how to fix this?

You need to always specify MACHINE="am3517-evm" on your command line, e.g. % MACHINE="am3517-evm" bitbake systemd-image

Alternatively, you can add just a single line to conf/local.conf and then it will be "sticky"

not local.conf, auto.conf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOoJY1MkyGM64RGpERAliKAKCfu0E2K3Qn+lsTx5YzNRgkxrA+QwCgqJjT 0ZsSMZCZArrGVc54VNa4dDA=
=zm3i
-----END PGP SIGNATURE-----

#3 lore raw

Makes sense - thanks!
But I do have to ask ... why does "oebb.sh config am3517-evm" not set this? I would have thought it does, but could be wrong of course. Thanks again,... Russell

Quoted 44 lines · Koen Kooi

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

Op 20-10-11 21:17, Gary Thomas schreef:

Quoted 18 lines · Russell Morris
Quoted 17 lines

Hi,

I am trying to do some builds for an am3517-evm ... but the machine configuration doesn't seem to be working (or I'm doing it wrong, more likely ... :-().

I have successfully built console-image for qemuarm, and then use oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh update) - but then when I try to build for this machine I see the following ...

OE Build Configuration: BB_VERSION = "1.13.3" TARGET_ARCH
= "arm" TARGET_OS = "linux-gnueabi" MACHINE =
"qemuarm" DISTRO = "angstrom" DISTRO_VERSION =
"v2011.10-core" TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"

Quoted 8 lines
Quoted 2 lines

So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone else having this issue? Any suggestions of how to fix this?

You need to always specify MACHINE="am3517-evm" on your command line, e.g. % MACHINE="am3517-evm" bitbake systemd-image

Alternatively, you can add just a single line to conf/local.conf and then it will be "sticky"

not local.conf, auto.conf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOoJY1MkyGM64RGpERAliKAKCfu0E2K3Qn+lsTx5YzNRgkxrA+QwCgqJjT 0ZsSMZCZArrGVc54VNa4dDA=
=zm3i
-----END PGP SIGNATURE-----

Quoted 5 lines

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

From [email protected] Fri Oct 21 01:56:20 2011
Received: from mail-gx0-f175.google.com ([209.85.161.175])

	by linuxtogo.org with esmtp (Exim 4.72)
	(envelope-from <[email protected]>) id 1RH2TE-0005qh-Hj
	for [email protected];
	Fri, 21 Oct 2011 01:56:20 +0200
Received: by ggnj1 with SMTP id j1so1811276ggn.6
	for <[email protected]>;
	Thu, 20 Oct 2011 16:50:27 -0700 (PDT)

DKIM-Signature: v

#5 lore raw
In reply to a message not in the archive

Yep, that works - thanks!

... Russell

Quoted 73 lines · Khem Raj
Quoted 2 lines · Russell Morris

Makes sense - thanks!
But I do have to ask ... why does "oebb.sh config am3517-evm" not set this? I would have thought it does, but could be wrong of course.

I think it should update the MACHINE entry in auto.conf but it only does that if auto.conf does not exist.
Can you try this patch

http://paste.ubuntu.com/714716/

and see if it works for you

Quoted 53 lines

Thanks again,... Russell

Quoted 44 lines · Koen Kooi

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

Op 20-10-11 21:17, Gary Thomas schreef:

Quoted 18 lines · Russell Morris
Quoted 17 lines

Hi,

I am trying to do some builds for an am3517-evm ... but the machine configuration doesn't seem to be working (or I'm doing it wrong, more likely ... :-().

I have successfully built console-image for qemuarm, and then use oebb.sh to set the machine (to am3517-evm, followed bu ./oebb.sh update) - but then when I try to build for this machine I see the following ...

OE Build Configuration: BB_VERSION = "1.13.3" TARGET_ARCH
= "arm" TARGET_OS = "linux-gnueabi" MACHINE =
"qemuarm" DISTRO = "angstrom" DISTRO_VERSION =
"v2011.10-core" TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"

Quoted 8 lines
Quoted 2 lines

So it's still building for qemuarm, not am3517-evm ... :-(. Is anyone else having this issue? Any suggestions of how to fix this?

You need to always specify MACHINE="am3517-evm" on your command line, e.g. % MACHINE="am3517-evm" bitbake systemd-image

Alternatively, you can add just a single line to conf/local.conf and then it will be "sticky"

not local.conf, auto.conf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOoJY1MkyGM64RGpERAliKAKCfu0E2K3Qn+lsTx5YzNRgkxrA+QwCgqJjT 0ZsSMZCZArrGVc54VNa4dDA=
=zm3i
-----END PGP SIGNATURE-----

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

Quoted 5 lines

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

From [email protected] Fri Oct 21 08:01:45 2011
Received: from lo.gmane.org ([80.91.229.12])

	by linuxtogo.org with esmtp (Exim 4.72)
	(envelope-from <[email protected]>)
	id 1RH8Ar-0005uj-LH for [email protected];
	Fri, 21 Oct 2011 08:01:45 +0200
Received: from list by lo.gmane.org with local (Exim 4.69)
	(envelope-from <[email protected]>)
	id 1RH85C-0005cy-6T for [email protected];
	Fri, 21 Oct 2011 07:55:54 +0200
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]>;
	Fri, 21 Oct 2011 07:55:54 +0200
Received: from koen by ip545070eb.adsl-surfen.hetnet.nl with local (Gmexim 0.1
	(Debian)) id 1AlnuQ-0007hv-00
	for <[email protected]>;
	Fri, 21 Oct 2011 07:55:54 +0200

X-Injected-Via-Gmane: http://gmane.org/
To: [email protected]
From: Koen Kooi <[email protected]>
Date: Fri, 21 Oct 2011 07:55:41 +0200
Lines: 20
Message-ID: <[email protected]>
References: <[email protected]>

	<1d63385213ee2d6741906cf2e61ccfb6fee58270.1319168013.git.otavio@ossystems.com.br>

Mime-Version: 1.0
Content-Type: text/plain; charset