Getting started

Yocto on the UDOO Boards

This ASCII Cinema displays the basic set-up and layer configuration. For the complete guide scroll down.

Install the repo utility:

If not already done you have to install the repo utility

$ mkdir ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ PATH=${PATH}:~/bin

Clone the BSP sources

This will download all required layers needed to build Yocto for the UDOO boards

$ mkdir udoo-community-bsp
$ cd udoo-community-bsp
$ repo init -u https://github.com/graugans/fsl-community-bsp-platform -b krogoth
$ repo sync

Prepare the build environment

To form a warm and cosy build environment you have to decide which board to start with.

For UDOO Quad and Dual development

$ MACHINE=udooqdl source ./setup-environment build

For UDOO Neo development

$ MACHINE=udooneo source ./setup-environment build

Fix the layer set-up

Three layers have to be added to the conf/bblayers.conffile

--- fsl-udoo-community-bsp.orig/build/conf/bblayers.conf
+++ fsl-udoo-community-bsp/build/conf/bblayers.conf
@@ -9,6 +9,8 @@ BBLAYERS = " \
${BSPDIR}/sources/poky/meta-yocto \
\
${BSPDIR}/sources/meta-openembedded/meta-oe \
+ ${BSPDIR}/sources/meta-openembedded/meta-python \
+ ${BSPDIR}/sources/meta-openembedded/meta-networking \
${BSPDIR}/sources/meta-openembedded/meta-multimedia \
\
${BSPDIR}/sources/meta-fsl-arm \
+ ${BSPDIR}/sources/meta-udoo \

X11 or commandline with EGLFS?

At this point you have to decide weather to build an X11 image which is default or a commandline image with EGLFS support.

EGLFS

A image without X11and Wayland. This will build a commandline image without X11 but with an accelerated framebuffer. To achieve this you have to tweak the conf/local.conf

DISTRO_FEATURES_remove = "x11 wayland"
PACKAGE_CLASSES ?= "package_ipk"

X11 / Wayland

A image with X11 or Wayland. This will build a image with X11. This may breaks EGLFS support.

PACKAGE_CLASSES ?= "package_ipk"

Building the command line image

When everything was set-up right the image will start to build. This may take some hours depending on the CPU power your build host does provide.

MACHINE=udooneo bitbake udoo-image-full-cmdline

To build for another machine you have to provide another MACHINE export, or edit the conf/local.conf