df18b721f8
These layers all contain machine configuration that depends on having the meta-intel common layer enabled as well, so use LAYERDEPENDS in the layer configuration for each one to make this explicit. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> |
||
|---|---|---|
| .. | ||
| binary | ||
| conf | ||
| recipes-bsp/formfactor | ||
| recipes-core/tasks | ||
| recipes-graphics/xorg-xserver | ||
| recipes-kernel/linux | ||
| COPYING.MIT | ||
| README | ||
| README.sources | ||
This README file contains information on building the meta-sugarbay BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details.
The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor, plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This BSP assumes that the Sandy Bridge integrated graphics are being used.
Dependencies
This layer depends on:
URI: git://git.openembedded.org/bitbake branch: master
URI: git://git.openembedded.org/openembedded-core layers: meta branch: master
URI: git://git.yoctoproject.org/meta-intel layers: intel branch: master
Patches
Please submit any patches against this BSP to the Yocto mailing list (yocto@yoctoproject.org) and cc: the maintainer:
Maintainer: Tom Zanussi tom.zanussi@intel.com
Please see the meta-intel/MAINTAINERS file for more details.
Table of Contents
I. Building the meta-sugarbay BSP layer II. Booting the images in /binary
I. Building the meta-sugarbay 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 sugarbay image by adding the location of the meta-sugarbay 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-sugarbay \
To enable the sugarbay layer, add the sugarbay MACHINE to local.conf:
MACHINE ?= "sugarbay"
You should then be able to build a sugarbay 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 example:
dd if=core-image-sato-sugarbay-20101207053738.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: