This page provides information on obtaining the Board Support Package (BSP) and building and running images for systems based on the Intel® Atomtm Processor E660 with Intel® Platform Controller Hub EG20T Development Kit.
This BSP, also known as "Crown Bay", ships as an open system and allows maximum flexibility for changing hardware configuration and peripherals.
You can find information about this kit by downloading the PDF document from http://edc.intel.com/Link.aspx?id=3878. For information on the Intel® Atomtm Processor E660 see http://edc.intel.com/Platforms/Atom-E6xx/. For general information about Board Support Packages, see the Board Support Package (BSP) Developer's Guide
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
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.5 graphics driver, while the one prefixed with 'crownbay-noemgd' does not.
Follow these steps to build either or both images:
- Ensure you have the Yocto Project Bernard 5.0 version. You can get this version from http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.tar.bz2. You can also get it through the Poky/Bernard git tree.
- Expand the BSP tarball inside of the top-level Poky directory. For example, assuming the top-level directory of the Poky tree is /home/trz/yocto, you would expand the tarball into the meta-crownbay layer at /home/trz/yocto/meta-crownbay.
- Add the location of the meta-crownbay layer to the bblayers.conf file using the following statement:
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:
$ source poky-init-build-env
$ bitbake poky-image-sato-live
At the end of a successful build, you should have a live image you can boot from a USB flash drive. See the following instructions in Booting the Images from /binary 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=poky-image-sato-live-crownbay-20101207053738.hddimg \
$ 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 you are getting 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