Intel® Atom™ E6xx Processor With Intel EG20T Controller Hub Development Kit (Crown Bay – noemgd)
Clone with Git (preferred)
git://git.yoctoproject.org/meta-intel -b daisy
The Crown Bay platform consists of the Intel Atom E6xx processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
It also supports the E6xx embedded on-chip graphics via the Intel Embedded Media and Graphics Driver (EMGD) 1.18 Driver.
Further information on the platforms supported by this BSP can be found here:
And information on all Intel® embedded platforms can be found here:
Yocto Project Compatible
This BSP is compatible with the Yocto Project as per the requirements listed here:
This layer depends on:
URI: git://git.openembedded.org/bitbake branch: daisy
URI: git://git.openembedded.org/openembedded-core layers: meta branch: daisy
URI: git://git.yoctoproject.org/meta-intel layers: intel branch: daisy
Please submit any patches against this BSP to the meta-intel mailing list (email@example.com) and cc: the maintainer:
Maintainer: Nitin A Kamble firstname.lastname@example.org
Please see the meta-intel/MAINTAINERS file for more details.
Table of Contents
I. Building the meta-crownbay BSP layer II. Booting the images in /binary
I. Building the meta-crownbay BSP layer
In order to build an image with BSP support for a given release, you need to download the corresponding BSP tarball from the ‘Board Support Package (BSP) Downloads’ page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents at the top-level of your yocto build tree, you can build a crownbay image by adding the location of the meta-crownbay layer to bblayers.conf, along with the meta-intel layer itself (to access common metadata shared between BSPs) e.g.:
yocto/meta-intel \ yocto/meta-intel/meta-crownbay \
The meta-crownbay layer contains support for two different machine configurations. These configurations are identical except for the fact that the one prefixed with ‘crownbay’ makes use of the Intel-proprietary EMGD 1.18 graphics driver, while the one prefixed with ‘crownbay-noemgd’ does not.
If you want to enable the layer that supports EMGD graphics add the following to the local.conf file:
MACHINE ?= “crownbay”
The ‘crownbay’ machine includes the emgd-driver-bin package, which has a proprietary license that must be whitelisted by adding the string “license_emgd-driver-bin_1.18” to the LICENSE_FLAGS_WHITELIST variable in your local.conf. For example:
LICENSE_FLAGS_WHITELIST = “license_emgd-driver-bin”
The emgd recipe depends on Xorg’s dri and glx modules, which are built only when ‘opengl’ is listed in DISTRO_FEATURES. So if the distro doesn’t list ‘opengl’ in the DISTRO_FEATURES you would need this additional line to your local.conf:
DISTRO_FEATURES_append = ” opengl”
If you want to enable the layer that does not support EMGD graphics add the following to the local.conf file:
MACHINE ?= “crownbay-noemgd”
You should then be able to build a crownbay image as such:
$ source oe-init-build-env $ bitbake core-image-sato
At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section ‘Booting the images from /binary’).
NOTE: The ‘crownbay’ machine will include support for hardware video acceleration via gstreamer if and only if the “commercial” string is added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
LICENSE_FLAGS_WHITELIST = “license_emgd-driver-bin commercial”
The reason this is needed is to prevent the image from including anything that might violate the license terms of the packages used to implement the the video acceleration feature, such as gst-ffmpeg and ffmpeg. As always, please consult the licenses included in the specific packages for details if you use packages that require particular LICENSE_FLAGS.
As an alternative to downloading the BSP tarball, you can also work directly from the meta-intel git repository. For each BSP in the ‘meta-intel’ repository, there are multiple branches, one corresponding to each major release starting with ‘laverne’ (0.90), in addition to the latest code which tracks the current master (note that not all BSPs are present in every release). Instead of extracting a BSP tarball at the top level of your yocto build tree, you can equivalently check out the appropriate branch from the meta-intel repository at the same location.
II. Booting the images in /binary
This BSP contains bootable live images, which can be used to directly boot Yocto off of a USB flash drive.
Under Linux, insert a USB flash drive. Assuming the USB flash drive takes device /dev/sdf, use dd to copy the live image to it. For example:
dd if=core-image-sato-crownbay.hddimg of=/dev/sdf
This should give you a bootable USB flash device. Insert the device into a bootable USB socket on the target, and power on. This should result in a system booted to the Sato graphical desktop.
If you want a terminal, use the arrows at the top of the UI to move to different pages of available applications, one of which is named ‘Terminal’. Clicking that should give you a root terminal.
If you want to ssh into the system, you can use the root terminal to ifconfig the IP address and use that to ssh in. The root password is empty, so to log in type ‘root’ for the user name and hit ‘Enter’ at the Password prompt: and you should be in.
If you find you’re getting corrupt images on the USB (it doesn’t show the syslinux boot: prompt, or the boot: prompt contains strange characters), try doing this first: