From 37dee2e3ea78746be32057074ead9f9de5124670 Mon Sep 17 00:00:00 2001 From: Tom Zanussi Date: Thu, 17 May 2012 22:17:42 -0500 Subject: meta-chiefriver: new layer for Chief River (Ivy Bridge/Panther Point) systems This layer provides support for Ivy Bridge + Panther Point Intel systems. Signed-off-by: Tom Zanussi --- meta-chiefriver/README | 107 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 107 insertions(+) create mode 100644 meta-chiefriver/README (limited to 'meta-chiefriver/README') diff --git a/meta-chiefriver/README b/meta-chiefriver/README new file mode 100644 index 00000000..49e44613 --- /dev/null +++ b/meta-chiefriver/README @@ -0,0 +1,107 @@ +This README file contains information on building the meta-chiefriver +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + +The 'Chief River' platform consists of the Intel Ivy Bridge processor, +plus the Panther Point PCH. This BSP assumes that the Ivy 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 + + +Table of Contents +================= + + I. Building the meta-chiefriver BSP layer + II. Booting the images in /binary + + +I. Building the meta-chiefriver 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 chiefriver +image by adding the location of the meta-chiefriver 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-chiefriver \ + +To enable the chiefriver layer, add the chiefriver MACHINE to local.conf: + + MACHINE ?= "chiefriver" + +You should then be able to build a chiefriver 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-chiefriver-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: + +# dd if=/dev/zero of=/dev/sdf bs=1M count=512 -- cgit v1.2.3-54-g00ecf