diff options
author | Nitin A Kamble <nitin.a.kamble@intel.com> | 2012-12-11 10:29:48 -0800 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2012-12-14 10:37:39 -0600 |
commit | ea0075af9339839ec91a4075e4e016fd807c9868 (patch) | |
tree | f62122babc394ced4647a0b372dc103643065e78 /meta-nuc/README | |
parent | 3b4e4b952d9149b595cdee00b7d558b4b2dd88f5 (diff) | |
download | meta-intel-ea0075af9339839ec91a4075e4e016fd807c9868.tar.gz |
meta-nuc: new BSP layer for Intel NUC systems
This layer provides support for Intel NUC (Next Unit of Computing)
systems.
This BSP specifically targets the "Next Unit of Computing Kit
DC3217IYE" containing the 3rd generation Intel® Core™ i3- 3217U (Ivy
Bridge) processor and Intel Centrino Advanced-N 6235 Wireless mini PCI
Express card.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-nuc/README')
-rw-r--r-- | meta-nuc/README | 149 |
1 files changed, 149 insertions, 0 deletions
diff --git a/meta-nuc/README b/meta-nuc/README new file mode 100644 index 00000000..3b68609f --- /dev/null +++ b/meta-nuc/README | |||
@@ -0,0 +1,149 @@ | |||
1 | This README file contains information on building the meta-nuc | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | This BSP is made specifically for "Next Unit of Computing Kit DC3217IYE" | ||
6 | with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card. | ||
7 | |||
8 | Further information on this NUC platform can be found here: | ||
9 | |||
10 | http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-boards-d33217gke-dc3217iye.html | ||
11 | |||
12 | Information on all Intel® embedded platforms can be found here: | ||
13 | |||
14 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
15 | |||
16 | |||
17 | Compliance | ||
18 | ========== | ||
19 | |||
20 | This BSP is compliant with the Yocto Project as per the requirements | ||
21 | listed here: | ||
22 | |||
23 | http://www.yoctoproject.org/yocto-project-compatible-registration | ||
24 | |||
25 | |||
26 | Dependencies | ||
27 | ============ | ||
28 | |||
29 | This layer depends on: | ||
30 | |||
31 | URI: git://git.openembedded.org/bitbake | ||
32 | branch: master | ||
33 | |||
34 | URI: git://git.openembedded.org/openembedded-core | ||
35 | layers: meta | ||
36 | branch: master | ||
37 | |||
38 | URI: git://git.yoctoproject.org/meta-intel | ||
39 | layers: intel | ||
40 | branch: master | ||
41 | |||
42 | |||
43 | Patches | ||
44 | ======= | ||
45 | |||
46 | Please submit any patches against this BSP to the Yocto mailing list | ||
47 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
48 | |||
49 | Maintainer: Nitin A Kamble <nitin.a.kamble@intel.com> | ||
50 | |||
51 | Please see the meta-intel/MAINTAINERS file for more details. | ||
52 | |||
53 | |||
54 | Table of Contents | ||
55 | ================= | ||
56 | |||
57 | I. Building the meta-nuc BSP layer | ||
58 | II. Booting the images in /binary | ||
59 | |||
60 | |||
61 | I. Building the meta-nuc BSP layer | ||
62 | ========================================= | ||
63 | |||
64 | In order to build an image with BSP support for a given release, you | ||
65 | need to download the corresponding BSP tarball from the 'Board Support | ||
66 | Package (BSP) Downloads' page of the Yocto Project website. | ||
67 | |||
68 | Having done that, and assuming you extracted the BSP tarball contents | ||
69 | at the top-level of your yocto build tree, you can build a nuc | ||
70 | image by adding the location of the meta-nuc layer to | ||
71 | bblayers.conf, along with the meta-intel layer itself (to access | ||
72 | common metadata shared between BSPs) e.g.: | ||
73 | |||
74 | yocto/meta-intel \ | ||
75 | yocto/meta-intel/meta-nuc \ | ||
76 | |||
77 | To enable the nuc layer, add the nuc MACHINE to local.conf: | ||
78 | |||
79 | MACHINE ?= "nuc" | ||
80 | |||
81 | You should then be able to build a nuc image as such: | ||
82 | |||
83 | $ source oe-init-build-env | ||
84 | $ bitbake core-image-sato | ||
85 | |||
86 | At the end of a successful build, you should have a live image that | ||
87 | you can boot from a USB flash drive (see instructions on how to do | ||
88 | that below, in the section 'Booting the images from /binary'). | ||
89 | |||
90 | NOTE: The 'nuc' machine will include support for hardware video | ||
91 | acceleration via gstreamer if and only if the "commercial" string is | ||
92 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
93 | |||
94 | For example: | ||
95 | |||
96 | LICENSE_FLAGS_WHITELIST = "commercial" | ||
97 | |||
98 | The reason this is needed is to prevent the image from including | ||
99 | anything that might violate the license terms of the packages used to | ||
100 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
101 | ffmpeg. As always, please consult the licenses included in the | ||
102 | specific packages for details if you use packages that require | ||
103 | particular LICENSE_FLAGS. | ||
104 | |||
105 | As an alternative to downloading the BSP tarball, you can also work | ||
106 | directly from the meta-intel git repository. For each BSP in the | ||
107 | 'meta-intel' repository, there are multiple branches, one | ||
108 | corresponding to each major release starting with 'laverne' (0.90), in | ||
109 | addition to the latest code which tracks the current master (note that | ||
110 | not all BSPs are present in every release). Instead of extracting a | ||
111 | BSP tarball at the top level of your yocto build tree, you can | ||
112 | equivalently check out the appropriate branch from the meta-intel | ||
113 | repository at the same location. | ||
114 | |||
115 | |||
116 | II. Booting the images in /binary | ||
117 | ================================= | ||
118 | |||
119 | This BSP contains bootable live images, which can be used to directly | ||
120 | boot Yocto off of a USB flash drive. | ||
121 | |||
122 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
123 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
124 | example: | ||
125 | |||
126 | # dd if=core-image-sato-nuc-20101207053738.hddimg of=/dev/sdf | ||
127 | # sync | ||
128 | # eject /dev/sdf | ||
129 | |||
130 | This should give you a bootable USB flash device. Insert the device | ||
131 | into a bootable USB socket on the target, and power on. This should | ||
132 | result in a system booted to the Sato graphical desktop. | ||
133 | |||
134 | If you want a terminal, use the arrows at the top of the UI to move to | ||
135 | different pages of available applications, one of which is named | ||
136 | 'Terminal'. Clicking that should give you a root terminal. | ||
137 | |||
138 | If you want to ssh into the system, you can use the root terminal to | ||
139 | ifconfig the IP address and use that to ssh in. The root password is | ||
140 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
141 | the Password prompt: and you should be in. | ||
142 | |||
143 | ---- | ||
144 | |||
145 | If you find you're getting corrupt images on the USB (it doesn't show | ||
146 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
147 | characters), try doing this first: | ||
148 | |||
149 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||