diff options
Diffstat (limited to 'meta-emenlow/README')
-rw-r--r-- | meta-emenlow/README | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/meta-emenlow/README b/meta-emenlow/README new file mode 100644 index 0000000000..862af5481b --- /dev/null +++ b/meta-emenlow/README | |||
@@ -0,0 +1,78 @@ | |||
1 | This README file contains information on building the meta-emenlow | ||
2 | BSP layer using any of the supported machine configurations, and | ||
3 | booting the images contained in the /binary directory. | ||
4 | |||
5 | If you're only interested in booting the images in the /binary | ||
6 | directory of a BSP tarball you've downloaded, there's nothing special | ||
7 | to do - the appropriate images are already in the /binary directory | ||
8 | depending on which BSP tarball you downloaded. | ||
9 | |||
10 | Please see the corresponding sections below for details. | ||
11 | |||
12 | |||
13 | Table of Contents | ||
14 | ================= | ||
15 | |||
16 | I. Building the meta-emenlow BSP layer | ||
17 | II. Booting the images in /binary | ||
18 | |||
19 | |||
20 | I. Building the meta-emenlow BSP layer | ||
21 | ======================================= | ||
22 | |||
23 | In order to build an image with BSP support for emenlow, you just need | ||
24 | to check out the poky master branch. | ||
25 | |||
26 | Having done that, you can build an emenlow image by adding the | ||
27 | location of the meta-emenlow layer to bblayers.conf e.g.: | ||
28 | |||
29 | yocto/meta-emenlow \ | ||
30 | |||
31 | To enable the emenlow layer, add the emenlow MACHINE to local.conf: | ||
32 | |||
33 | MACHINE ?= "emenlow" | ||
34 | |||
35 | You should then be able to build an emenlow image as such: | ||
36 | |||
37 | $ source poky-init-build-env | ||
38 | $ bitbake poky-image-sato-live | ||
39 | |||
40 | At the end of a successful build, you should have a live image that | ||
41 | you can boot from a USB flash drive (see instructions on how to do | ||
42 | that below, in the section 'Booting the images from /binary'). | ||
43 | |||
44 | |||
45 | II. Booting the images in /binary | ||
46 | ================================= | ||
47 | |||
48 | This BSP contains bootable live images, which can be used to directly | ||
49 | boot Yocto off of a USB flash drive. | ||
50 | |||
51 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
52 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
53 | example: | ||
54 | |||
55 | # dd if=poky-image-sato-live-emenlow-20101207053738.hddimg of=/dev/sdf | ||
56 | # sync | ||
57 | # eject /dev/sdf | ||
58 | |||
59 | This should give you a bootable USB flash device. Insert the device | ||
60 | into a bootable USB socket on the target, and power on. This should | ||
61 | result in a system booted to the Sato graphical desktop. | ||
62 | |||
63 | If you want a terminal, use the arrows at the top of the UI to move to | ||
64 | different pages of available applications, one of which is named | ||
65 | 'Terminal'. Clicking that should give you a root terminal. | ||
66 | |||
67 | If you want to ssh into the system, you can use the root terminal to | ||
68 | ifconfig the IP address and use that to ssh in. The root password is | ||
69 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
70 | the Password prompt: and you should be in. | ||
71 | |||
72 | ---- | ||
73 | |||
74 | If you find you're getting corrupt images on the USB (it doesn't show | ||
75 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
76 | characters), try doing this first: | ||
77 | |||
78 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||