summaryrefslogtreecommitdiffstats
path: root/meta-sys940x/README
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2012-01-23 23:46:07 (GMT)
committerDarren Hart <dvhart@linux.intel.com>2012-02-03 17:25:17 (GMT)
commit6aad7407464ec9cc807916b71068fdae323bfcd1 (patch)
treeb2c72e5be10717494a98a9e6d59a64debf8f429b /meta-sys940x/README
parentc6d991cf83b3047419cc0076ea4ab1297b9cfb6d (diff)
downloadmeta-intel-6aad7407464ec9cc807916b71068fdae323bfcd1.tar.gz
meta-intel: Add Inforce SYS940x BSP
The Inforce SYS940x-ECX Developer-Ready Reference Platform features: o Intel Atom E6xx (0.6-1.6 GHz) o Up to 1GB on-board DDR2 o Intel Platform Controller Hub EG20T o VGA,LVDS o HD Audio o SD Card o Dual SATA o Mini-PCIe http://www.inforcecomputing.com/SYS940X_ECX.html Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta-sys940x/README')
-rw-r--r--meta-sys940x/README140
1 files changed, 140 insertions, 0 deletions
diff --git a/meta-sys940x/README b/meta-sys940x/README
new file mode 100644
index 0000000..e349008
--- /dev/null
+++ b/meta-sys940x/README
@@ -0,0 +1,140 @@
1This README file contains information on building the meta-sys940x BSP
2layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5The Inforce SYS940x platform consists of the Intel Atom E6xx
6processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek
7+ Topcliff).
8
9It also supports the E6xx embedded on-chip graphics via the Intel
10Embedded Media and Graphics Driver (EMGD) 1.10 Driver.
11
12
13Dependencies
14============
15
16This layer depends on:
17
18 URI: git://git.openembedded.org/bitbake
19 branch: master
20
21 URI: git://git.openembedded.org/openembedded-core
22 layers: meta
23 branch: master
24
25 URI: git://git.yoctoproject.org/meta-intel
26 layers: intel
27 branch: master
28
29
30Patches
31=======
32
33Please submit any patches against this BSP to the Yocto mailing list
34(yocto@yoctoproject.org) and cc: the maintainer:
35
36Maintainer: Darren Hart <dvhart@linux.intel.com>
37
38Please see the meta-intel/MAINTAINERS file for more details.
39
40
41Table of Contents
42=================
43
44 I. Building the meta-sys940x BSP layer
45 II. Booting the images in /binary
46
47
48I. Building the meta-sys940x BSP layer
49===================================
50
51In order to build an image with BSP support for a given release, you
52need to download the corresponding BSP tarball from the 'Board Support
53Package (BSP) Downloads' page of the Yocto Project website.
54
55Having done that, and assuming you extracted the BSP tarball contents
56at the top-level of your yocto build tree, you can build an sys940x image
57by adding the location of the meta-sys940x layer to bblayers.conf, along
58with the meta-intel layer itself (to access common metadata shared
59between BSPs) e.g.:
60
61 yocto/meta-intel \
62 yocto/meta-intel/meta-sys940x \
63
64The meta-sys940x layer contains support for two different machine
65configurations. These configurations are identical except for the fact
66that the one prefixed with 'sys940x' makes use of the Intel-proprietary
67EMGD 1.10 graphics driver, while the one prefixed with 'sys940x-noemgd'
68does not.
69
70If you want to enable the layer that supports EMGD graphics add the
71following to the local.conf file:
72
73 MACHINE ?= "sys940x"
74
75The 'sys940x' machine includes the emgd-driver-bin package, which has a
76proprietary license that must be whitelisted by adding the string
77"license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable
78in your local.conf. For example:
79
80 LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10"
81
82If you want to enable the layer that does not support EMGD graphics
83add the following to the local.conf file:
84
85 MACHINE ?= "sys940x-noemgd"
86
87You should then be able to build an sys940x image as such:
88
89 $ source oe-init-build-env
90 $ bitbake core-image-sato
91
92At the end of a successful build, you should have a live image that
93you can boot from a USB flash drive (see instructions on how to do
94that below, in the section 'Booting the images from /binary').
95
96As an alternative to downloading the BSP tarball, you can also work
97directly from the meta-intel git repository. For each BSP in the
98'meta-intel' repository, there are multiple branches, one
99corresponding to each major release starting with 'laverne' (0.90), in
100addition to the latest code which tracks the current master (note that
101not all BSPs are present in every release). Instead of extracting a
102BSP tarball at the top level of your yocto build tree, you can
103equivalently check out the appropriate branch from the meta-intel
104repository at the same location.
105
106
107II. Booting the images in /binary
108=================================
109
110This BSP contains bootable live images, which can be used to directly
111boot Yocto off of a USB flash drive.
112
113Under Linux, insert a USB flash drive. Assuming the USB flash drive
114takes device /dev/sdf, use dd to copy the live image to it. For
115example:
116
117# dd if=core-image-sato-sys940x-20101207053738.hddimg of=/dev/sdf
118# sync
119# eject /dev/sdf
120
121This should give you a bootable USB flash device. Insert the device
122into a bootable USB socket on the target, and power on. This should
123result in a system booted to the Sato graphical desktop.
124
125If you want a terminal, use the arrows at the top of the UI to move to
126different pages of available applications, one of which is named
127'Terminal'. Clicking that should give you a root terminal.
128
129If you want to ssh into the system, you can use the root terminal to
130ifconfig the IP address and use that to ssh in. The root password is
131empty, so to log in type 'root' for the user name and hit 'Enter' at
132the Password prompt: and you should be in.
133
134----
135
136If you find you're getting corrupt images on the USB (it doesn't show
137the syslinux boot: prompt, or the boot: prompt contains strange
138characters), try doing this first:
139
140# dd if=/dev/zero of=/dev/sdf bs=1M count=512