Intel® Atom™ E6xx Processor With Intel EG20T Controller Hub Development Kit (Crown Bay – noemgd)

Board Info

Crown Bay
Processor Family: Intel x86
Organization: Intel Corporation


Built with: Yocto Project 1.7 – Dizzy
Compatible with: Dizzy 1.7.x
Release Date: 12/01/2014
MD5 sum: 8f3f4b2b50d0fe440a0f1738a8a87d2f

Clone with Git (preferred)

git:// -b dizzy

Release Notes

The Crown Bay platform consists of the Intel Atom E6xx processor,
plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).

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://
branch: 1.24

URI: git://
layers: meta
branch: dizzy

URI: git://
layers: intel
branch: dizzy


Please submit any patches against this BSP to the meta-intel mailing list
( and cc: the maintainer:

Maintainer: Nitin A Kamble

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 the crownbay-noemgd machine
configuration. The previously supported crownbay machine with the
proprietary EMGD graphics driver has been retired. The ‘crownbay-noemgd’
machine configuration uses the open source ‘vesa’ kernel driver.

To enable the layer 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’).

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

# dd if=core-image-sato-crownbay-noemgd.hddimg of=/dev/sdf
# sync
# eject /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:

# dd if=/dev/zero of=/dev/sdf bs=1M count=512