summaryrefslogtreecommitdiffstats
path: root/meta-cedartrail/README
diff options
context:
space:
mode:
Diffstat (limited to 'meta-cedartrail/README')
-rwxr-xr-xmeta-cedartrail/README111
1 files changed, 111 insertions, 0 deletions
diff --git a/meta-cedartrail/README b/meta-cedartrail/README
new file mode 100755
index 00000000..295e9ff7
--- /dev/null
+++ b/meta-cedartrail/README
@@ -0,0 +1,111 @@
1This README file contains information on building the meta-cedartrail
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5Dependencies
6============
7
8This layer depends on:
9
10 URI: git://git.openembedded.org/bitbake
11 branch: master
12
13 URI: git://git.openembedded.org/openembedded-core
14 layers: meta
15 branch: master
16
17 URI: git://git.yoctoproject.org/meta-intel
18 layers: intel
19 branch: master
20
21
22Patches
23=======
24
25Please submit any patches against this BSP to the Yocto mailing list
26(yocto@yoctoproject.org) and cc: the maintainer:
27
28Maintainer: Kishore Bodke <kishore.k.bodke@intel.com>
29
30Please see the meta-intel/MAINTAINERS file for more details.
31
32Table of Contents
33=================
34
35 I. Building the meta-cedartrail BSP layer
36II. Booting the images in /binary
37
38
39I. Building the meta-cedartrail BSP layer
40=========================================
41
42In order to build an image with BSP support for a given release, you
43need to download the corresponding BSP tarball from the 'Board Support
44Package (BSP) Downloads' page of the Yocto Project website.
45
46Having done that, and assuming you extracted the BSP tarball contents
47at the top-level of your yocto build tree, you can build a cedartrail
48image by adding the location of the meta-cedartrail layer to
49bblayers.conf, along with the meta-intel layer itself (to access
50common metadata shared between BSPs) e.g.:
51
52 yocto/meta-intel \
53 yocto/meta-intel/meta-cedartrail \
54
55To enable the cedartrail layer, add the cedartrail MACHINE to local.conf:
56
57 MACHINE ?= "cedartrail"
58
59You should then be able to build a cedartrail image as such:
60
61 $ source oe-init-build-env
62 $ bitbake core-image-sato
63
64At the end of a successful build, you should have a live image that
65you can boot from a USB flash drive (see instructions on how to do
66that below, in the section 'Booting the images from /binary').
67
68As an alternative to downloading the BSP tarball, you can also work
69directly from the meta-intel git repository. For each BSP in the
70'meta-intel' repository, there are multiple branches, one
71corresponding to each major release starting with 'laverne' (0.90), in
72addition to the latest code which tracks the current master. Instead
73of extracting a BSP tarball at the top level of your yocto build tree,
74you can equivalently check out the appropriate branch from the
75meta-intel repository at the same location.
76
77
78II. Booting the images in /binary
79==================================
80
81This BSP contains bootable live images, which can be used to directly
82boot Yocto off of a USB flash drive.
83
84Under Linux, insert a USB flash drive. Assuming the USB flash drive
85takes device /dev/sdf, use dd to copy the live image to it. For
86example:
87
88# dd if=core-image-sato-cedartrail-20120105232035.hddimg of=/dev/sdf
89# sync
90# eject /dev/sdf
91
92This should give you a bootable USB flash device. Insert the device
93into a bootable USB socket on the target, and power on. This should
94result in a system booted to the Sato graphical desktop.
95
96If you want a terminal, use the arrows at the top of the UI to move to
97different pages of available applications, one of which is named
98'Terminal'. Clicking that should give you a root terminal.
99
100If you want to ssh into the system, you can use the root terminal to
101ifconfig the IP address and use that to ssh in. The root password is
102empty, so to log in type 'root' for the user name and hit 'Enter' at
103the Password prompt: and you should be in.
104
105----
106
107If you find you're getting corrupt images on the USB (it doesn't show
108the syslinux boot: prompt, or the boot: prompt contains strange
109characters), try doing this first:
110
111# dd if=/dev/zero of=/dev/sdf bs=1M count=512