OpenEmbedded

= Building your system with OpenEmbedded and Angstrom scripts =

A "meta layer" is the OpenEmbedded repository (layer) of recipes, needed to build machine-specific stuff (u-boot, Linux kernel, script.bin), and dd'able SD-Card image.

The official repository is:

https://github.com/linux-sunxi/meta-sunxi

To make damn thing work you will need:

1. A new fresh directory. 2. Angstrom scripts. 3. Luck and patience.

The repository supports the following boards ("machines" in OE terminology):
 * cubieboard
 * cubieboard2
 * olinuxino-a13
 * olinuxino-a10

More will be added as contributions occur.

So, what you really need is set up angstrom scripts:

git clone git@github.com:Angstrom-distribution/setup-scripts.git cd setup-scripts git checkout -b next origin/next echo "meta-sunxi,git://github.com/linux-sunxi/meta-sunxi.git,master,HEAD" >>sources/layers.txt

then edit conf/bblayers.conf e.g with vi

add the following BEFORE comment BSPLAYERS = "${TOPDIR}/sources/meta-sunxi"
 * 1) Add your overlay location to EXTRALAYERS

for cubieboard, do MACHINE=cubieboard ./oebb.sh config cubieboard for any other board replace cubieboard with your machine name

then you import the configured environment to start working: . environment-angstrom-next

Thn you can start build: MACHINE=cubieboard bitbake console-image And then stuff depends on your computer speed. As build finishes, you can dd the resulting image to your SD card (for USB mass storage card reader, /dev/sdd is your card) dd if=deploy/eglibc/images/cubieboard/console-image-cubieboard.a10-sdimg of=/dev/sdd sync eject /dev/sdd

For directly attached mmc controller (/dev/mmcblk0 is your card): dd if=deploy/eglibc/images/cubieboard/console-image-cubieboard.a10-sdimg of=/dev/mmcblk0 If your card gets maounted during insertion, unmount it before doing any dd. And yes, as usual, check that your device name is correct BEFORE doing dd. You will not be able to undo this operation.

So you now have bootable SD card image you can play with. Enjoy!