These release notes provide information for building the meta-crownbay Board Support Package (BSP) layer and booting the images contained in the /binary directory. The Crown Bay platform consists of an Intel® Atom™ Z6xx processor with the Intel® Platform Controller Hub EG20T Development Kit. Crown Bay ships as an open system and allows maximum flexibility for changing hardware configuration and peripherals.
Without modification, the pre-built images contain a 10-day timer. If you boot the pre-built images on target hardware, the hardware will automatically reboot after 10 days at which time the timer will reset itself to another 10-day period. To disable this timer, you must rebuild the BSP image using the Yocto Project.
The Crown Bay platform also supports the Intel® Atom™ E6xx embedded on-chip graphics through the Intel® Embedded Media and Graphics Driver (EMGD) 1.8 Driver.
You can find information about this kit by downloading the PDF document from
For information on the Intel® Atomtm Processor E660 see
For general information about Board Support Packages, see the Board Support Package (BSP) Developer's Guide.
The release notes here represent the latest information for the Crown Bay BSP as compared to the README file packaged as part of the BSP tarball. Please refer to the notes on this website (i.e. the ones you are now reading) for the latest information on how to use the meta-crownbay BSP.
The BSP Tarballs
You can download two versions of the Crown Bay BSP tarball from this page. Each tarball contains the meta-crownbay Yocto BSP layer. Bootable images specific to the version you downloaded can be found in the BSP layer's /binary directory. The BSP versions available for the Crown Bay are:
- Crown Bay - This tarball is prefixed with the string 'crownbay'. It contains proprietary graphics binaries and requires you to agree to a click-through end-user license before you can download the tarball.
- Crown Bay no EMGD - This tarball is prefixed with the string 'crownbay-noemgd'. It does not contain any proprietary information. You can download the tarball directly without signing a licence. The BSP uses fully open source generic VESA support. As such, the drivers are not optimized to take full advantage of the hardware as compared to the other BSP tarball.
For source files used to create the Crown Bay BSP images see http://autobuilder.yoctoproject.org/sources
Special Notes for Building the meta-crownbay BSP Layer
The meta-crownbay layer makes use of the proprietary Intel EMGD userspace drivers when building the "crownbay" machine (but not when building the "crownbay-noemgd" machine). If you get the BSP from the 'BSP Downloads' section of the Yocto website, the EMGD binaries needed to perform the build will already be present in the BSP, located in
the meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 directory, and you can ignore the rest of these special notes. Simply go to the Building the meta-crownbay BSP Layer section below.
If you did not get the BSP from the 'BSP Downloads' section of the Yocto website, you can download a tarball containing an rpm that contains the binaries and extract the binaries from that, and copy them to the proper location in the meta-crownbay layer. Then next section, Downloading and Extracting the Binaries Using the EMGD Linux Tarball, describes the steps you need to take.
Downloading and Extracting the Binaries Using the EMGD Linux Tarball
- Download the EMGD 1.8 Driver: Here is the current link to the URL from which you can download the driver: http://edc.intel.com/Software/Downloads/EMGD/
- Select the following in the "Download Now" tab:
Intel® architecture-based product: Linux Tar Ball
Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9)
Doing so gives you the large tarball file Lin_EMGD_1_8_RC_2032.tgz
- Extract the files in the tar file, which will in turn give you a directory named IEMGD_HEAD_Linux. The binaries are contained in an rpm file.
- Extract the binaries from the from the rpm file using rpm2cpio and cpio:
$ cd IEMGD_HEAD_Linux/MeeGo1.2
$ rpm2cpio emgd-bin-2032-1.6.i586.rpm > emgd-bin-2032-1.6.i586.cpio
$ mkdir extracted; cd extracted
$ cpio -idv < ../emgd-bin-2032-1.6.i586.cpio
- Copy the xorg-xserver binaries to the emgd-driver-bin-1.8 directory in meta-intel/common:
$ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
- Copy the IEMGD License.txt file to the same directory:
$ cp IEMGD_HEAD_Linux/License/License.txt \
- Remove the following unused file from the emgd binaries in order to avoid a packaging error at build-time:
$ rm meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8/lib/dri/emgd_drv_video.so
At this point, you should be able to build meta-crownbay images as usual.
Building the Meta-crownbay BSP Layer
If you're interested in building Crown Bay images, you'll find that 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.8 graphics driver, while the one prefixed with 'crownbay-noemgd' does not.
Follow these steps to build either or both images:
- Download the corresponding BSP tarball from the Board Support Package (BSP) Downloads page of the Yocto Project website. Note, you can also clone the meta-intel Git repository from the Yocto Project 1.1 Release.
- Assuming you have extracted the BSP tarball contents into the top-level of your Yocto Project source directory, you can build a Crown Bay image by adding the location of the meta-crownbay layer to the bblayers.conf file:
- If you want to enable the layer that supports EMGD graphics, add the following to the local.conf file:
MACHINE ?= "crownbay"
- If you want to enable the layer that does not support EMGD graphics, add the following to the local.conf file:
MACHINE ?= "crownbay-noemgd"
- Build the image using the following two commands:
$ bitbake core-image-sato
At the end of a successful build, you should have a live image you can boot from a USB flash drive. See the instructions in the section Booting the Images in /binary that follows for information on how to boot the image from a USB flash drive.
Booting the Images in /binary
The Crown Bay BSP contains bootable live images, which you can use to directly boot Yocto from a USB flash drive. The bootable images for either BSP (normal or -noemgd) exist in the /binary directory of the downloaded and expanded tarball.
Follow these steps to create a bootable USB flash drive and boot the image:
- Under Linux, insert a USB flash drive.
- Assuming the USB flash drive takes device /dev/sdf, copy the live image to the drive as follows:
# dd if=core-image-sato-crownbay-20101207053738.hddimg of=/dev/sdf
# eject /dev/sdf
You now should have a bootable USB flash device.
- Insert the flash drive into a bootable USB socket on the target.
- Power the target machine on to boot 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', and click it to get 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. Log in as 'root' with no password (hit 'Enter' for the password) to log in.
If you find corrupt images on the USB (e.g. it does not show the syslinux boot: prompt, or the boot: prompt contains strange characters), try making sure the USB device is cleared out before you copy the image to it during step 2. So, try the following between steps 1 and 2 above:
# dd if=/dev/zero of=/dev/sdf bs=1M count=512