ATNGW100

ATNGW100

[Justin Seitz]

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

Hey all,

I am pretty new to OE, and having followed some scattered instructions on building the ATNGW100 I have been unsuccessful with the new OE core. My local.conf includes the directives:

TARGET_OS = “linux-uclibc”
MACHINE = “atngw100″
DISTRO = “angstrom-2008.1″
ANGSTROMLIBC = “uclibc”

Which it complains that angstrom-2008.1 cannot be found as a distro. Is this a case that I can just pull the configs from the OE-classic repo over or is there a guide somewhere that I can't find in YOCTO that describes how I can move the ATNGW100 build over to the new OE-core?

Thanks in advance,

JMS

Re: ATNGW100

[Takeshi Hamasaki]

Hi Justin,

according to the DISTRO name,
you have to specify something exists in
source/meta-angstrom/conf/distro/ directory.

I guess you can find angstrom-v2012.05.conf or something there.
Thus
DISTRO="angstrom-v2012.05"
helps you to walk one step forward.
-- 
Takeshi Hamasaki

2013/3/25 Justin Seitz <jms@bughunter.ca>:
> Hey all,
>
> I am pretty new to OE, and having followed some scattered instructions on building the ATNGW100 I have been unsuccessful with the new OE core. My local.conf includes the directives:
>
> TARGET_OS = “linux-uclibc”
> MACHINE = “atngw100&#8243;
> DISTRO = “angstrom-2008.1&#8243;
> ANGSTROMLIBC = “uclibc”
>
> Which it complains that angstrom-2008.1 cannot be found as a distro. Is this a case that I can just pull the configs from the OE-classic repo over or is there a guide somewhere that I can't find in YOCTO that describes how I can move the ATNGW100 build over to the new OE-core?
>
> Thanks in advance,
>
> JMS
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: ATNGW100

[Khem Raj]

On Mar 24, 2013, at 11:42 AM, Justin Seitz <jms@bughunter.ca> wrote:

> Hey all,
> 
> I am pretty new to OE, and having followed some scattered instructions on building the ATNGW100 I have been unsuccessful with the new OE core. My local.conf includes the directives:
> 
> TARGET_OS = “linux-uclibc”
> MACHINE = “atngw100&#8243;
> DISTRO = “angstrom-2008.1&#8243;
> ANGSTROMLIBC = “uclibc”
> 
> Which it complains that angstrom-2008.1 cannot be found as a distro. Is this a case that I can just pull the configs from the OE-classic repo over or is there a guide somewhere that I can't find in YOCTO that describes how I can move the ATNGW100 build over to the new OE-core?

this question belongs to angstrom distro ml. I will answer is here however. You should be able to checkout
2011.03 maintenance branch of oe.classic and use that one for the above machine and distro policies. No
one has yet forward ported the avr32 support into latest angstrom.

> 
> Thanks in advance,
> 
> JMS
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

ATNGW100

[Justin Seitz]

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Hey guys and gals,

I posted a similar question to the OE mailing list, so hopefully I am not spamming some folks. I have copied over the atngw100.conf file and its required include/tune-at32ap7000.inc file.

When I attempt to bitbike I get the following error:

TUNE_ARCH is unset. Please ensure your MACHINE configuration includes a valid tune configuration file which will set this correctly.
Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (None).

When I update them to be "avr32", those checks pass but I get an error of:

Toolchain tunings invalid:
No tuning found for default multilib.

I have looked through the example MACHINE files that are provided, and I don't see a reference to TUNE_ARCH or PACKAGE_ARCHS from the Yocto project. I'm a bit stumped to be honest. Has anyone successfully built the ATNGW100 using Yocto and could lend me some love?

JMS