summaryrefslogtreecommitdiffstats
path: root/meta-fri2/README
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-07-12 09:38:17 -0500
committerTom Zanussi <tom.zanussi@intel.com>2011-08-03 12:11:00 -0500
commitea897ce72602c7b8f1f11aafe8baf6cbe5887c4c (patch)
tree70b17505ae2e4a27a5c22616ebf5f95f1da4c60a /meta-fri2/README
parent724b13a74e068b7cd018cd8b2e18c2a762881d1d (diff)
downloadmeta-intel-ea897ce72602c7b8f1f11aafe8baf6cbe5887c4c.tar.gz
meta-fri2: new layer for Fish River Island II (E6XX/EG20T) systems
This layer provides support for E6XX + EG20T Intel systems. Currently it supports only vesa graphics, which will be upgraded shortly. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-fri2/README')
-rw-r--r--meta-fri2/README83
1 files changed, 83 insertions, 0 deletions
diff --git a/meta-fri2/README b/meta-fri2/README
new file mode 100644
index 00000000..7957a7fe
--- /dev/null
+++ b/meta-fri2/README
@@ -0,0 +1,83 @@
1This README file contains information on building the meta-fri2 BSP
2layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5
6Table of Contents
7=================
8
9 I. Special notes on the meta-fri2 BSP layer
10 II. Building the meta-fri2 BSP layer
11III. Booting the images in /binary
12
13
14II. Building the meta-fri2 BSP layer
15=========================================
16
17In order to build an image with BSP support for a given release, you
18need to download the corresponding BSP tarball from the 'Board Support
19Package (BSP) Downloads' page of the Yocto Project website.
20
21Having done that, and assuming you extracted the BSP tarball contents
22at the top-level of your yocto build tree, you can build a fri2 image
23by adding the location of the meta-fri2 layer to bblayers.conf e.g.:
24
25 yocto/meta-intel/meta-fri2 \
26
27To enable the fri2 layer, add the fri2 MACHINE to local.conf:
28
29 MACHINE ?= "fri2"
30
31You should then be able to build a fri2 image as such:
32
33 $ source poky-init-build-env
34 $ bitbake poky-image-sato-live
35
36At the end of a successful build, you should have a live image that
37you can boot from a USB flash drive (see instructions on how to do
38that below, in the section 'Booting the images from /binary').
39
40As an alternative to downloading the BSP tarball, you can also work
41directly from the meta-intel git repository. For each BSP in the
42'meta-intel' repository, there are multiple branches, one
43corresponding to each major release starting with 'laverne' (0.90), in
44addition to the latest code which tracks the current master. Instead
45of extracting a BSP tarball at the top level of your yocto build tree,
46you can equivalently check out the appropriate branch from the
47meta-intel repository at the same location.
48
49
50III. Booting the images in /binary
51==================================
52
53This BSP contains bootable live images, which can be used to directly
54boot Yocto off of a USB flash drive.
55
56Under Linux, insert a USB flash drive. Assuming the USB flash drive
57takes device /dev/sdf, use dd to copy the live image to it. For
58example:
59
60# dd if=poky-image-sato-live-fri2-20101207053738.hddimg of=/dev/sdf
61# sync
62# eject /dev/sdf
63
64This should give you a bootable USB flash device. Insert the device
65into a bootable USB socket on the target, and power on. This should
66result in a system booted to the Sato graphical desktop.
67
68If you want a terminal, use the arrows at the top of the UI to move to
69different pages of available applications, one of which is named
70'Terminal'. Clicking that should give you a root terminal.
71
72If you want to ssh into the system, you can use the root terminal to
73ifconfig the IP address and use that to ssh in. The root password is
74empty, so to log in type 'root' for the user name and hit 'Enter' at
75the Password prompt: and you should be in.
76
77----
78
79If you find you're getting corrupt images on the USB (it doesn't show
80the syslinux boot: prompt, or the boot: prompt contains strange
81characters), try doing this first:
82
83# dd if=/dev/zero of=/dev/sdf bs=1M count=512