diff options
Diffstat (limited to 'meta-romley/README')
-rw-r--r-- | meta-romley/README | 199 |
1 files changed, 0 insertions, 199 deletions
diff --git a/meta-romley/README b/meta-romley/README deleted file mode 100644 index acdcb99d..00000000 --- a/meta-romley/README +++ /dev/null | |||
@@ -1,199 +0,0 @@ | |||
1 | This README file contains information on building the meta-romley | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The romley platform consists of two versions: | ||
6 | 1. romley - Sandy Bridge | ||
7 | 2. romley - Ivy Bridge | ||
8 | |||
9 | The romley - Sandy Bridge platform consists of the Intel Xeon E5-2600 | ||
10 | and E5-2400 Series processors, plus the Intel C604/C602-J chipset | ||
11 | (Sandy Bridge-EP/EN + Patsburg). | ||
12 | |||
13 | The romley - Ivy Bridge platform consists of the Intel Xeon E5-2600 | ||
14 | and E5-2400 v2 Series processors with the Intel C604/C602-J chipset | ||
15 | (Ivy Bridge-EP/EN + Patsburg). | ||
16 | |||
17 | This BSP assumes Matrox graphics is being used. | ||
18 | |||
19 | Further information about the platforms supported by this BSP can be | ||
20 | found here: | ||
21 | |||
22 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-c604/overview | ||
23 | |||
24 | Information on all IntelĀ® embedded platforms can be found here: | ||
25 | |||
26 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
27 | |||
28 | |||
29 | Yocto Project Compatible | ||
30 | ======================== | ||
31 | |||
32 | This BSP is compatible with the Yocto Project as per the requirements | ||
33 | listed here: | ||
34 | |||
35 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
36 | |||
37 | |||
38 | Dependencies | ||
39 | ============ | ||
40 | |||
41 | This layer depends on: | ||
42 | |||
43 | URI: git://git.openembedded.org/bitbake | ||
44 | branch: master | ||
45 | |||
46 | URI: git://git.openembedded.org/openembedded-core | ||
47 | layers: meta | ||
48 | branch: master | ||
49 | |||
50 | URI: git://git.yoctoproject.org/meta-intel | ||
51 | layers: intel | ||
52 | branch: master | ||
53 | |||
54 | |||
55 | Patches | ||
56 | ======= | ||
57 | |||
58 | Please submit any patches against this BSP to the meta-intel mailing | ||
59 | list (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
60 | |||
61 | Maintainer: Chan Wei Sern <wei.sern.chan@intel.com> | ||
62 | |||
63 | Please see the meta-intel/MAINTAINERS file for more details. | ||
64 | |||
65 | |||
66 | Table of Contents | ||
67 | ================= | ||
68 | |||
69 | I. Building the meta-romley BSP layer | ||
70 | II. Booting the images in /binary | ||
71 | III. Device Notes | ||
72 | a. Boot Loader | ||
73 | b. I/O drivers | ||
74 | IV. Enabling Intel DPDK Technology | ||
75 | |||
76 | I. Building the meta-romley BSP layer | ||
77 | ======================================= | ||
78 | |||
79 | In order to build an image with BSP support for a given release, you | ||
80 | need to download the corresponding BSP tarball from the 'Board Support | ||
81 | Package (BSP) Downloads' page of the Yocto Project website. | ||
82 | |||
83 | Having done that, and assuming you extracted the BSP tarball contents | ||
84 | at the top-level of your yocto build tree, you can build a romley | ||
85 | image by adding the location of the meta-romley layer to | ||
86 | bblayers.conf, along with the meta-intel layer itself (to access | ||
87 | common metadata shared between BSPs) e.g.: | ||
88 | |||
89 | yocto/meta-intel \ | ||
90 | yocto/meta-intel/meta-romley \ | ||
91 | |||
92 | To enable the romley Sandy Bridge layer, add the romley MACHINE to local.conf: | ||
93 | |||
94 | MACHINE ?= "romley" | ||
95 | |||
96 | To enable the romley Ivy Bridge layer, add the romley-ivb MACHINE to local.conf: | ||
97 | |||
98 | MACHINE ?= "romley-ivb" | ||
99 | |||
100 | You should then be able to build a romley image as such: | ||
101 | |||
102 | $ source oe-init-build-env | ||
103 | $ bitbake core-image-sato | ||
104 | |||
105 | At the end of a successful build, you should have a live image that | ||
106 | you can boot from a USB flash drive (see instructions on how to do | ||
107 | that below, in the section 'Booting the images from /binary'). | ||
108 | |||
109 | As an alternative to downloading the BSP tarball, you can also work | ||
110 | directly from the meta-intel git repository. For each BSP in the | ||
111 | 'meta-intel' repository, there are multiple branches, one | ||
112 | corresponding to each major release starting with 'laverne' (0.90), in | ||
113 | addition to the latest code which tracks the current master (note that | ||
114 | not all BSPs are present in every release). Instead of extracting a | ||
115 | BSP tarball at the top level of your yocto build tree, you can | ||
116 | equivalently check out the appropriate branch from the meta-intel | ||
117 | repository at the same location. | ||
118 | |||
119 | |||
120 | II. Booting the images in /binary | ||
121 | ================================= | ||
122 | |||
123 | This BSP contains bootable live images, which can be used to directly | ||
124 | boot Yocto off of a USB flash drive. | ||
125 | |||
126 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
127 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
128 | example: | ||
129 | |||
130 | # dd if=core-image-sato-romley.hddimg of=/dev/sdf | ||
131 | # sync | ||
132 | # eject /dev/sdf | ||
133 | |||
134 | This should give you a bootable USB flash device. Insert the device | ||
135 | into a bootable USB socket on the target, and power on. This should | ||
136 | result in a system booted to the Sato graphical desktop. | ||
137 | |||
138 | If you want a terminal, use the arrows at the top of the UI to move to | ||
139 | different pages of available applications, one of which is named | ||
140 | 'Terminal'. Clicking that should give you a root terminal. | ||
141 | |||
142 | If you want to ssh into the system, you can use the root terminal to | ||
143 | ifconfig the IP address and use that to ssh in. The root password is | ||
144 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
145 | the Password prompt: and you should be in. | ||
146 | |||
147 | If you're using Rose City and does not have ME firmware and struggling with | ||
148 | rebooting the machine. This is because broken ME firmware can contribute to long wait of | ||
149 | reboot. We have to changing the kernel command line to blacklist MEI driver to be loaded: | ||
150 | |||
151 | 1. Open your syslinux in VI editor eg: | ||
152 | # vi /media/sda/syslinux.cfg | ||
153 | |||
154 | 2. Look for the line that has kernel command line which has certain similiarity | ||
155 | as below: | ||
156 | |||
157 | "APPEND initrd=/initrd LABEL=boot root=/dev/ram0 ....." | ||
158 | |||
159 | or | ||
160 | |||
161 | "APPEND initrd=/initrd LABEL=install root=/dev/ram0 ...." | ||
162 | |||
163 | 3. Add "mei_me.blacklist=yes"at the end of that line and it will be like below: | ||
164 | "APPEND inird=/initRD LABEL=boot root=/dev/ram0 .... mei_me.blacklist=yes" | ||
165 | |||
166 | 4. Save this syslinux.cfg | ||
167 | |||
168 | 5. Boot up the Romley with this new changed. | ||
169 | |||
170 | |||
171 | III. Device Notes | ||
172 | ================= | ||
173 | |||
174 | a. Boot Loader | ||
175 | -------------- | ||
176 | - Support BIOS version at RoseCity board :RMLCRB.86J.R0.45.D018 | ||
177 | |||
178 | b. I/O drivers | ||
179 | -------------- | ||
180 | -Support Matrox graphic card. | ||
181 | -Support SATA, USB Host v2.0 | ||
182 | -Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801, | ||
183 | WDT, and HPET) | ||
184 | |||
185 | IV. Enabling Intel DPDK Technology | ||
186 | =================================== | ||
187 | |||
188 | There are recipes available for the 'Intel Data Plane Development Kit | ||
189 | Technology components for use with this BSP. Please contact your | ||
190 | Intel Field Sales Representative or visit Intel Embedded Design | ||
191 | Center (www.intel.com/p/en_US/embedded/designcenter) for instructions on how | ||
192 | to locate and use these recipes. | ||
193 | ---- | ||
194 | |||
195 | If you find you're getting corrupt images on the USB (it doesn't show | ||
196 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
197 | characters), try doing this first: | ||
198 | |||
199 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||