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