summaryrefslogtreecommitdiffstats
path: root/meta-emenlow/README
diff options
context:
space:
mode:
Diffstat (limited to 'meta-emenlow/README')
-rw-r--r--meta-emenlow/README148
1 files changed, 0 insertions, 148 deletions
diff --git a/meta-emenlow/README b/meta-emenlow/README
deleted file mode 100644
index eccc9f33..00000000
--- a/meta-emenlow/README
+++ /dev/null
@@ -1,148 +0,0 @@
1This README file contains information on building the meta-emenlow
2BSP layer using any of the supported machine configurations, and
3booting the images contained in the /binary directory.
4
5The 'eMenlow' platform consists of the Intel Atom Z5xx processor,
6plus the Intel US15W System Controller Hub.
7
8Further information on the platform supported by this BSP can be
9found here:
10
11 http://www.portwell.com/products/detail.asp?CUSTCHAR1=WEBS-2120
12
13Information on all IntelĀ® embedded platforms can be found here:
14
15 http://www.intel.com/p/en_US/embedded/hwsw/hardware
16
17If you're only interested in booting the images in the /binary
18directory of a BSP tarball you've downloaded, there's nothing special
19to do - the appropriate images are already in the /binary directory
20depending on which BSP tarball you downloaded.
21
22Please see the corresponding sections below for details.
23
24
25Yocto Project Compatible
26========================
27
28This BSP is compatible with the Yocto Project as per the requirements
29listed here:
30
31 https://www.yoctoproject.org/webform/yocto-project-compatible-registration
32
33
34Dependencies
35============
36
37This layer depends on:
38
39 URI: git://git.openembedded.org/bitbake
40 branch: master
41
42 URI: git://git.openembedded.org/openembedded-core
43 layers: meta
44 branch: master
45
46 URI: git://git.yoctoproject.org/meta-intel
47 layers: intel
48 branch: master
49
50
51Patches
52=======
53
54Please submit any patches against this BSP to the meta-intel mailing list
55(meta-intel@yoctoproject.org) and cc: the maintainer:
56
57Maintainer: Saul Wold <sgw@linux.intel.com>
58
59Please see the meta-intel/MAINTAINERS file for more details.
60
61
62Table of Contents
63=================
64
65 I. Building the meta-emenlow BSP layer
66II. Booting the images in /binary
67
68
69I. Building the meta-emenlow BSP layer
70=======================================
71
72In order to build an image with BSP support for a given release, you
73need to download the corresponding BSP tarball from the 'Board Support
74Package (BSP) Downloads' page of the Yocto Project website.
75
76Having done that, and assuming you extracted the BSP tarball contents
77at the top-level of your yocto build tree, you can build an emenlow
78image by adding the location of the meta-emenlow layer to
79bblayers.conf, along with the meta-intel layer itself (to access
80common metadata shared between BSPs) e.g.:
81
82 yocto/meta-intel \
83 yocto/meta-intel/meta-emenlow \
84
85The meta-emenlow layer contains support for emenlow-noemgd machine
86configuration. The previously supported emenlow machine with the
87proprietary EMGD graphics driver has been retired. The 'emenlow-noemgd'
88machine configuration uses the open source 'gma500' kernel DRM driver
89along with the 'modesetting' X driver.
90
91To enable the layer add the following to the local.conf file:
92
93 MACHINE ?= "emenlow-noemgd"
94
95You should then be able to build an emenlow image as such:
96
97 $ source oe-init-build-env
98 $ bitbake core-image-sato
99
100At the end of a successful build, you should have a live image that
101you can boot from a USB flash drive (see instructions on how to do
102that below, in the section 'Booting the images from /binary').
103
104As an alternative to downloading the BSP tarball, you can also work
105directly from the meta-intel git repository. For each BSP in the
106'meta-intel' repository, there are multiple branches, one
107corresponding to each major release starting with 'laverne' (0.90), in
108addition to the latest code which tracks the current master (note that
109not all BSPs are present in every release). Instead of extracting a
110BSP tarball at the top level of your yocto build tree, you can
111equivalently check out the appropriate branch from the meta-intel
112repository at the same location.
113
114
115II. Booting the images in /binary
116=================================
117
118This BSP contains bootable live images, which can be used to directly
119boot Yocto off of a USB flash drive.
120
121Under Linux, insert a USB flash drive. Assuming the USB flash drive
122takes device /dev/sdf, use dd to copy the live image to it. For
123example:
124
125# dd if=core-image-sato-emenlow-noemgd.hddimg of=/dev/sdf
126# sync
127# eject /dev/sdf
128
129This should give you a bootable USB flash device. Insert the device
130into a bootable USB socket on the target, and power on. This should
131result in a system booted to the Sato graphical desktop.
132
133If you want a terminal, use the arrows at the top of the UI to move to
134different pages of available applications, one of which is named
135'Terminal'. Clicking that should give you a root terminal.
136
137If you want to ssh into the system, you can use the root terminal to
138ifconfig the IP address and use that to ssh in. The root password is
139empty, so to log in type 'root' for the user name and hit 'Enter' at
140the Password prompt: and you should be in.
141
142----
143
144If you find you're getting corrupt images on the USB (it doesn't show
145the syslinux boot: prompt, or the boot: prompt contains strange
146characters), try doing this first:
147
148# dd if=/dev/zero of=/dev/sdf bs=1M count=512