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