summaryrefslogtreecommitdiffstats
path: root/meta-jasperforest/README
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-02-14 04:33:13 (GMT)
committerTom Zanussi <tom.zanussi@intel.com>2011-02-14 04:33:13 (GMT)
commit829f0b2db3015c145b89bf85cf9ac3d8e6827e30 (patch)
treedae0bb6e0c7e0eb88b376d2d5ffdee64f995e1df /meta-jasperforest/README
parent92c64651fe7d91f81d4eb7d48fbf854a4dad97d0 (diff)
downloadmeta-intel-829f0b2db3015c145b89bf85cf9ac3d8e6827e30.tar.gz
meta-jasperforest: new layer for Xeon C5500/C3500 + Intel 3420
This layer provides support for Jasper Forest + Ibex Peak Intel systems. 'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which combined with the Intel 3420 PCH chipset (Ibex Peak) make up the 'Picket Post' CRB this BSP was developed on. This BSP also makes use of the grub2 and associated live-install changes in meta-intel/common. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-jasperforest/README')
-rw-r--r--meta-jasperforest/README85
1 files changed, 85 insertions, 0 deletions
diff --git a/meta-jasperforest/README b/meta-jasperforest/README
new file mode 100644
index 0000000..ab7246d
--- /dev/null
+++ b/meta-jasperforest/README
@@ -0,0 +1,85 @@
1This README file contains information on building the
2meta-jasperforest BSP layer, and booting the images contained in the
3/binary directory. Please see the corresponding sections below for
4details.
5
6'Jasper Forest' refers to the Intel Xeon C5500/C3500 processors, which
7combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
8'Picket Post' CRB this BSP was developed on.
9
10
11Table of Contents
12=================
13
14 I. Building the meta-jasperforest BSP layer
15 II. Booting the images in /binary
16
17
18I. Building the meta-jasperforest BSP layer
19=======================================
20
21For each BSP in the 'meta-intel' repository, there are multiple
22branches, one corresponding to each major release starting with
23'laverne' (0.90), in addition to the latest code which tracks the
24current master.
25
26In order to build an image with BSP support for a given release, you
27need to check out the 'meta-intel' branch corresponding to the release
28you're building against e.g. to build for laverne (0.90), check out
29the 'laverne' branch of both poky and 'meta-intel'.
30
31Having done that, and assuming you cloned the 'meta-intel' repository
32at the top-level of your yocto build tree, you can build a jasperforest
33image by adding the location of the meta-jasperforest layer to
34bblayers.conf e.g.:
35
36 yocto/meta-intel/meta-jasperforest \
37
38To enable the jasperforest layer, add the jasperforest MACHINE to local.conf:
39
40 MACHINE ?= "jasperforest"
41
42You should then be able to build a jasperforest image as such:
43
44 $ source poky-init-build-env
45 $ bitbake poky-image-sato-live
46
47At the end of a successful build, you should have a live image that
48you can boot from a USB flash drive (see instructions on how to do
49that below, in the section 'Booting the images from /binary').
50
51
52II. Booting the images in /binary
53=================================
54
55This BSP contains bootable live images, which can be used to directly
56boot Yocto off of a USB flash drive.
57
58Under Linux, insert a USB flash drive. Assuming the USB flash drive
59takes device /dev/sdf, use dd to copy the live image to it. For
60example:
61
62# dd if=poky-image-sato-live-jasperforest-20101207053738.hddimg of=/dev/sdf
63# sync
64# eject /dev/sdf
65
66This should give you a bootable USB flash device. Insert the device
67into a bootable USB socket on the target, and power on. This should
68result in a system booted to the Sato graphical desktop.
69
70If you want a terminal, use the arrows at the top of the UI to move to
71different pages of available applications, one of which is named
72'Terminal'. Clicking that should give you a root terminal.
73
74If you want to ssh into the system, you can use the root terminal to
75ifconfig the IP address and use that to ssh in. The root password is
76empty, so to log in type 'root' for the user name and hit 'Enter' at
77the Password prompt: and you should be in.
78
79----
80
81If you find you're getting corrupt images on the USB (it doesn't show
82the syslinux boot: prompt, or the boot: prompt contains strange
83characters), try doing this first:
84
85# dd if=/dev/zero of=/dev/sdf bs=1M count=512