From: Mateusz Nowaczyk <mateusz.nowaczyk@wisene.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Newbie question: Angstrom on at91sam9g20
Date: Thu, 30 Aug 2012 16:22:55 +0200 [thread overview]
Message-ID: <503F773F.6020409@wisene.pl> (raw)
In-Reply-To: <k1n6oh$8ve$1@ger.gmane.org>
On 30.08.2012 10:03, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 29-08-12 19:25, Mateusz Nowaczyk schreef:
>> Hi, I've been using Angstrom 2011.03 (oe-classic) on a modified
>> at91sam9g20ek board. Unfortunately, it seems that it is no longer updated
>> - it contains obsolete version of dropbear (0.52) ect. I tried switching
>> to the new oe-core based version, but it lacks adequate bsp layer. I also
>> tried manually changing the opkg.conf and installing packages from
>> http://www.angstrom-distribution.org/feeds/v2012.05/ipk/eglibc/armv5te/base/
>>
>>
> but it only caused more problems (can't login at all).
>> How can i get an up-to-date Angstrom for this architecture? Should I
>> stick to the classic OE and manually update recipies, or rather create a
>> bsp layer?
>
> Create a bsp layer
OK, I found the meta-atmel layer here:
https://github.com/rascalmicro/meta-atmel
I got the following error:
~/angstrom/setup-scripts$ MACHINE=at91sam9g20ek bitbake console-image
Pseudo is not present but is required, building this first before the
main build
ERROR: ParseError at
/home/mn/angstrom/setup-scripts/sources/meta-atmel/recipes-bsp/u-boot/u-boot.inc:62:
unparsed line: 'INSANE_SKIP_${PN} = True': --:--:--
ERROR: Command execution failed: Exited with 1
Is there any way to fix it?
next prev parent reply other threads:[~2012-08-30 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 17:25 Newbie question: Angstrom on at91sam9g20 Mateusz Nowaczyk
2012-08-30 8:03 ` Koen Kooi
2012-08-30 14:22 ` Mateusz Nowaczyk [this message]
2012-08-30 14:29 ` Paul Eggleton
2012-08-30 14:45 ` Mateusz Nowaczyk
2012-08-30 17:47 ` Mateusz Nowaczyk
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=503F773F.6020409@wisene.pl \
--to=mateusz.nowaczyk@wisene.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox