meta-intel/meta-cedartrail
Rahul Saxena 814d612aed meta-cedartrail: rename ogg-CC-BY-3.0-music-samples_0.1.bb to ogg-cc-by-3.0-music-samples_0.1.bb
Capital letters in receipe name generate error when ipk package types are used for build

Signed-off-by: Rahul Saxena <rahul.saxena@.intel.com>
2012-07-11 16:12:55 -05:00
..
binary meta-cedartrail: new layer for Cedar Trail Systems 2011-12-16 17:03:47 -06:00
conf meta-cedartrail: update BBFILES to include meta-intel/common path 2012-03-26 17:40:43 -05:00
recipes-bsp meta-cedartrail: update formfactor recipe for pvr and no-pvr case 2012-03-26 17:42:14 -05:00
recipes-core/tasks meta-cedartrail: new layer for Cedar Trail Systems 2011-12-16 17:03:47 -06:00
recipes-graphics meta-cedartrail: add Cedar Trail PVR driver 2012-03-26 17:41:28 -05:00
recipes-kernel/linux meta-cedartrail: add SRCREV of yocto/pvr kernel branch 2012-05-04 15:26:26 -05:00
recipes-mediasamples meta-cedartrail: rename ogg-CC-BY-3.0-music-samples_0.1.bb to ogg-cc-by-3.0-music-samples_0.1.bb 2012-07-11 16:12:55 -05:00
recipes-multimedia/libva meta-cedartrail: change libva license to MIT 2012-03-26 17:42:56 -05:00
recipes-sato/images meta-cedartrail: rename ogg-CC-BY-3.0-music-samples_0.1.bb to ogg-cc-by-3.0-music-samples_0.1.bb 2012-07-11 16:12:55 -05:00
COPYING.MIT meta-cedartrail: new layer for Cedar Trail Systems 2011-12-16 17:03:47 -06:00
README meta-cedartrail: fix README to state tools-testapps needed for Glxgears 2012-04-16 16:34:31 -05:00
README.sources meta-cedartrail: new layer for Cedar Trail Systems 2011-12-16 17:03:47 -06:00

This README file contains information on building the meta-cedartrail
BSP layer, and booting the images contained in the /binary directory.
Please see the corresponding sections below for details.

The 'Cedar Trail' platform consists of the Cedarview (Intel® Atom™
N2600, N2800 and D2700) processor, plus the Tiger Point
(Intel® NM10 Express) Chipset. 


Table of Contents
=================

 I. Building the meta-cedartrail BSP layer
II. Booting the images in /binary
III. Miscellaneous Notes 

I. Building the meta-cedartrail 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 cedartrail 
image by adding the location of the meta-cedartrail layer to
bblayers.conf e.g.:

  yocto/meta-intel/meta-cedartrail \

The meta-cedartrail layer contains support for two different machine
configurations. These configurations are identical except for the fact
that the one prefixed with 'cedartrail' makes use of Intel' proprietary
PowerVR Graphics/Media drivers to enable Graphics and Media acceleration
in the processor, while the one prefixed with 'cedartrail-nonopvr' uses
non-accelerated graphics driver (VESA).

If you want to enable the layer that supports Power VR graphics add the
following to the local.conf file:

  MACHINE ?= "cedartrail"

Power VR Graphics user-space driver binaries are covered by a
"Intel Free Distribution Binary License". The build of this driver
can be enabled by adding the following line to the local.conf file:
 PVR_LICENSE = "yes"

If you want to enable the layer that does not support Power VR graphics
add the following to the local.conf file:

 MACHINE ?= "cedartrail-nopvr"

You should then be able to build a cedartrail 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.  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-cedartrail-20111209003350.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

Miscellaneous Notes
====================

Video and Music Samples
-----------------------
This BSP includes recipes to download Ogg format video and
music files that can be played-back with the Video and music players
included in the sato images.  The sample files are installed in
/home/Music and /home/Videos directories.  


Adding Glxgears to image
-------------------------
Glxgears can be added to the generated image by adding "tools-testapps"
option to the extra image features variable in the default local.conf
before building the BSP.

e.g. to add Glxgears, locate the following line in local.conf
EXTRA_IMAGE_FEATURES = "debug-tweaks"

and change above line to..

EXTRA_IMAGE_FEATURES = "debug-tweaks tools-testapps"