Ångström never ending battle

Found out where the f*** meta-toolchain recipes are stored. Hoorrah!!  /Projects/angstrom/setup-scripts/sources/openembedded-core/meta/recipes-core

Ångström  distribution build environment set following infos at : http://www.angstrom-distribution.org/building-angstrom

I must say, the fragmentation of the embedded linux software development tools is horrific. I’ll try to make my notices publique to contribute a small piece to open source community.

There is a difference between “setup-script method” and Narcissus building – the latter one uses ancient stable 2.6.32 kernel, the first one the 3.0.14 branch.


General remark: never ever use Ralink WLAN adapters (rt73usb) on Linux! After years spent on chasing sloooow SSH logins and dripping SSH-Session bytes I discovered ath9k_htc driven TP-LINK device (TL-WN722NC) – it works like a charm. 


Why am I using Ångström? It is coherent (sic!! in comparison to Ubuntu rootfs/kernel splitted maintanance). My goal is to create a BeagleBoard based low-latency gateway system for connecting CAN bus with WLAN device on the other side. It needs PEAKCAN driver, stable WLAN driver, and hostapd based Access Point. That’s all. It took a lot of time to build separate working software chunks. Ubuntu Natty rootfs with Robert C Nelson kernel 3.1 + hostapd + PeakCan driver works allright (but slow!). One has to remember aligning gdb and gdbserver when working remotely from Ubuntu Oneiric + linaro toolchain (GDB version mismatch).


Angstrom “setup-script” compilation this morning:

  • meta-toolchain -> OK
  • meta-toolchain-sdk -> NOK, fails while trying to change something in my host /etc and so on. Why? Where is the description of this bb file? What does it do? Questions over questions…
  • console-image -> OK


Next problem will be compiling PeakCAN driver with Angstrom kernel, since the driver needs kernel headers. Compilation of Ubuntu RCN kernel aganist them was a piece of cake.


Next, I’ll try Yocto/Poky. How do they differ form OpenEmbedded? How often do they cross-contribute if ever? I think without analyzing Angstrom setup-scripts which are somehow easier to understand I’ll stay stupid…


This link let me understanding what to do to be able to cross-compile stuff using local built native ipk packages:


Hopefully, this will work fo bare-bone Angstrom/OE, not Poky only.


Bought a new Linux SBC today.

The NanosG20 SBC comes from http://www.ledato.de and seems to be better than Olimex SBC’s, being built with a newer AT91SAM9G20 microcontroller and offering a already patched kernel ver. 2.6.35 together with Debian distro for a price of of merely 99 EUR (+VAT)!

There is an alternative SBC coming from taskit – PortuxG20, but it is more expensive (179 EUR).

SAM9-L9260 or SAM9-L9261 from Olimex are quite expensive (resp. 139.95 and 299.95). The latter offers an TFT display interface, and both do not reach the performance of taskit or ledato SBC’s.

All considered SBC’s have robust 2.54 mm pinheaders and DB9 connectors for heavy-duty HW interfaces (the rest are standard mini-USB and RJ45).