summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2017-09-14 12:00:35 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-09-14 13:36:22 +0100
commitabea8ec5063998e0e2b822be7704c0d14569df0e (patch)
treee77ce68754687a179c878a744caf5a71721c955c /README.hardware
parent145c245a56ff26f098ced26ee3c5c7bc45b0ead7 (diff)
downloadpoky-abea8ec5063998e0e2b822be7704c0d14569df0e.tar.gz
meta-yocto: Restructure and tidy up READMEs
The YP Compat v2 standard requres a more specific README structure. Bring meta-yocto to the required standard and clean up some of the data in the READMEs whilst in there. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README.hardware')
l---------[-rw-r--r--]README.hardware425
1 files changed, 1 insertions, 424 deletions
diff --git a/README.hardware b/README.hardware
index dc6a08dea7..8b6258d49d 100644..120000
--- a/README.hardware
+++ b/README.hardware
@@ -1,424 +1 @@
1 Poky Hardware README meta-yocto-bsp/README.hardware \ No newline at end of file
2 ====================
3
4This file gives details about using Poky with the reference machines
5supported out of the box. A full list of supported reference target machines
6can be found by looking in the following directories:
7
8 meta/conf/machine/
9 meta-yocto-bsp/conf/machine/
10
11If you are in doubt about using Poky/OpenEmbedded with your hardware, consult
12the documentation for your board/device.
13
14Support for additional devices is normally added by creating BSP layers - for
15more information please see the Yocto Board Support Package (BSP) Developer's
16Guide - documentation source is in documentation/bspguide or download the PDF
17from:
18
19 http://yoctoproject.org/documentation
20
21Support for physical reference hardware has now been split out into a
22meta-yocto-bsp layer which can be removed separately from other layers if not
23needed.
24
25
26QEMU Emulation Targets
27======================
28
29To simplify development, the build system supports building images to
30work with the QEMU emulator in system emulation mode. Several architectures
31are currently supported:
32
33 * ARM (qemuarm)
34 * x86 (qemux86)
35 * x86-64 (qemux86-64)
36 * PowerPC (qemuppc)
37 * MIPS (qemumips)
38
39Use of the QEMU images is covered in the Yocto Project Reference Manual.
40The appropriate MACHINE variable value corresponding to the target is given
41in brackets.
42
43
44Hardware Reference Boards
45=========================
46
47The following boards are supported by the meta-yocto-bsp layer:
48
49 * Texas Instruments Beaglebone (beaglebone)
50 * Freescale MPC8315E-RDB (mpc8315e-rdb)
51
52For more information see the board's section below. The appropriate MACHINE
53variable value corresponding to the board is given in brackets.
54
55Reference Board Maintenance
56===========================
57
58Send pull requests, patches, comments or questions about meta-yocto-bsps to poky@yoctoproject.org
59
60Maintainers: Kevin Hao <kexin.hao@windriver.com>
61 Bruce Ashfield <bruce.ashfield@windriver.com>
62
63Consumer Devices
64================
65
66The following consumer devices are supported by the meta-yocto-bsp layer:
67
68 * Intel x86 based PCs and devices (genericx86)
69 * Ubiquiti Networks EdgeRouter Lite (edgerouter)
70
71For more information see the device's section below. The appropriate MACHINE
72variable value corresponding to the device is given in brackets.
73
74
75
76 Specific Hardware Documentation
77 ===============================
78
79
80Intel x86 based PCs and devices (genericx86*)
81=============================================
82
83The genericx86 and genericx86-64 MACHINE are tested on the following platforms:
84
85Intel Xeon/Core i-Series:
86 + Intel NUC5 Series - ix-52xx Series SOC (Broadwell)
87 + Intel NUC6 Series - ix-62xx Series SOC (Skylake)
88 + Intel Shumway Xeon Server
89
90Intel Atom platforms:
91 + MinnowBoard MAX - E3825 SOC (Bay Trail)
92 + MinnowBoard MAX - Turbot (ADI Engineering) - E3826 SOC (Bay Trail)
93 - These boards can be either 32bot or 64bit modes depending on firmware
94 - See minnowboard.org for details
95 + Intel Braswell SOC
96
97and is likely to work on many unlisted Atom/Core/Xeon based devices. The MACHINE
98type supports ethernet, wifi, sound, and Intel/vesa graphics by default in
99addition to common PC input devices, busses, and so on.
100
101Depending on the device, it can boot from a traditional hard-disk, a USB device,
102or over the network. Writing generated images to physical media is
103straightforward with a caveat for USB devices. The following examples assume the
104target boot device is /dev/sdb, be sure to verify this and use the correct
105device as the following commands are run as root and are not reversable.
106
107USB Device:
108 1. Build a live image. This image type consists of a simple filesystem
109 without a partition table, which is suitable for USB keys, and with the
110 default setup for the genericx86 machine, this image type is built
111 automatically for any image you build. For example:
112
113 $ bitbake core-image-minimal
114
115 2. Use the "dd" utility to write the image to the raw block device. For
116 example:
117
118 # dd if=core-image-minimal-genericx86.hddimg of=/dev/sdb
119
120 If the device fails to boot with "Boot error" displayed, or apparently
121 stops just after the SYSLINUX version banner, it is likely the BIOS cannot
122 understand the physical layout of the disk (or rather it expects a
123 particular layout and cannot handle anything else). There are two possible
124 solutions to this problem:
125
126 1. Change the BIOS USB Device setting to HDD mode. The label will vary by
127 device, but the idea is to force BIOS to read the Cylinder/Head/Sector
128 geometry from the device.
129
130 2. Use a ".wic" image with an EFI partition
131
132 a) With a default grub-efi bootloader:
133 # dd if=core-image-minimal-genericx86-64.wic of=/dev/sdb
134
135 b) Use systemd-boot instead
136 - Build an image with EFI_PROVIDER="systemd-boot" then use the above
137 dd command to write the image to a USB stick.
138
139
140Texas Instruments Beaglebone (beaglebone)
141=========================================
142
143The Beaglebone is an ARM Cortex-A8 development board with USB, Ethernet, 2D/3D
144accelerated graphics, audio, serial, JTAG, and SD/MMC. The Black adds a faster
145CPU, more RAM, eMMC flash and a micro HDMI port. The beaglebone MACHINE is
146tested on the following platforms:
147
148 o Beaglebone Black A6
149 o Beaglebone A6 (the original "White" model)
150
151The Beaglebone Black has eMMC, while the White does not. Pressing the USER/BOOT
152button when powering on will temporarily change the boot order. But for the sake
153of simplicity, these instructions assume you have erased the eMMC on the Black,
154so its boot behavior matches that of the White and boots off of SD card. To do
155this, issue the following commands from the u-boot prompt:
156
157 # mmc dev 1
158 # mmc erase 0 512
159
160To further tailor these instructions for your board, please refer to the
161documentation at http://www.beagleboard.org/bone and http://www.beagleboard.org/black
162
163From a Linux system with access to the image files perform the following steps:
164
165 1. Build an image. For example:
166
167 $ bitbake core-image-minimal
168
169 2. Use the "dd" utility to write the image to the SD card. For example:
170
171 # dd core-image-minimal-beaglebone.wic of=/dev/sdb
172
173 3. Insert the SD card into the Beaglebone and boot the board.
174
175Freescale MPC8315E-RDB (mpc8315e-rdb)
176=====================================
177
178The MPC8315 PowerPC reference platform (MPC8315E-RDB) is aimed at hardware and
179software development of network attached storage (NAS) and digital media server
180applications. The MPC8315E-RDB features the PowerQUICC II Pro processor, which
181includes a built-in security accelerator.
182
183(Note: you may find it easier to order MPC8315E-RDBA; this appears to be the
184same board in an enclosure with accessories. In any case it is fully
185compatible with the instructions given here.)
186
187Setup instructions
188------------------
189
190You will need the following:
191* NFS root setup on your workstation
192* TFTP server installed on your workstation
193* Straight-thru 9-conductor serial cable (DB9, M/F) connected from your
194 PC to UART1
195* Ethernet connected to the first ethernet port on the board
196
197--- Preparation ---
198
199Note: if you have altered your board's ethernet MAC address(es) from the
200defaults, or you need to do so because you want multiple boards on the same
201network, then you will need to change the values in the dts file (patch
202linux/arch/powerpc/boot/dts/mpc8315erdb.dts within the kernel source). If
203you have left them at the factory default then you shouldn't need to do
204anything here.
205
206Note: To boot from USB disk you need u-boot that supports 'ext2load usb'
207command. You need to setup TFTP server, load u-boot from there and
208flash it to NOR flash.
209
210Beware! Flashing bootloader is potentially dangerous operation that can
211brick your device if done incorrectly. Please, make sure you understand
212what below commands mean before executing them.
213
214Load the new u-boot.bin from TFTP server to memory address 200000
215=> tftp 200000 u-boot.bin
216
217Disable flash protection
218=> protect off all
219
220Erase the old u-boot from fe000000 to fe06ffff in NOR flash.
221The size is 0x70000 (458752 bytes)
222=> erase fe000000 fe06ffff
223
224Copy the new u-boot from address 200000 to fe000000
225the size is 0x70000. It has to be greater or equal to u-boot.bin size
226=> cp.b 200000 fe000000 70000
227
228Enable flash protection again
229=> protect on all
230
231Reset the board
232=> reset
233
234--- Booting from USB disk ---
235
236 1. Flash partitioned image to the USB disk
237
238 # dd if=core-image-minimal-mpc8315e-rdb.wic of=/dev/sdb
239
240 2. Plug USB disk into the MPC8315 board
241
242 3. Connect the board's first serial port to your workstation and then start up
243 your favourite serial terminal so that you will be able to interact with
244 the serial console. If you don't have a favourite, picocom is suggested:
245
246 $ picocom /dev/ttyUSB0 -b 115200
247
248 4. Power up or reset the board and press a key on the terminal when prompted
249 to get to the U-Boot command line
250
251 5. Optional. Load the u-boot.bin from the USB disk:
252
253 => usb start
254 => ext2load usb 0:1 200000 u-boot.bin
255
256 and flash it to NOR flash as described above.
257
258 6. Load the kernel and dtb from the first partition of the USB disk:
259
260 => usb start
261 => ext2load usb 0:1 1000000 uImage
262 => ext2load usb 0:1 2000000 dtb
263
264 7. Set bootargs and boot up the device
265
266 => setenv bootargs root=/dev/sdb2 rw rootwait console=ttyS0,115200
267 => bootm 1000000 - 2000000
268
269
270--- Booting from NFS root ---
271
272Load the kernel and dtb (device tree blob), and boot the system as follows:
273
274 1. Get the kernel (uImage-mpc8315e-rdb.bin) and dtb (uImage-mpc8315e-rdb.dtb)
275 files from the tmp/deploy directory, and make them available on your TFTP
276 server.
277
278 2. Connect the board's first serial port to your workstation and then start up
279 your favourite serial terminal so that you will be able to interact with
280 the serial console. If you don't have a favourite, picocom is suggested:
281
282 $ picocom /dev/ttyUSB0 -b 115200
283
284 3. Power up or reset the board and press a key on the terminal when prompted
285 to get to the U-Boot command line
286
287 4. Set up the environment in U-Boot:
288
289 => setenv ipaddr <board ip>
290 => setenv serverip <tftp server ip>
291 => setenv bootargs root=/dev/nfs rw nfsroot=<nfsroot ip>:<rootfs path> ip=<board ip>:<server ip>:<gateway ip>:255.255.255.0:mpc8315e:eth0:off console=ttyS0,115200
292
293 5. Download the kernel and dtb, and boot:
294
295 => tftp 1000000 uImage-mpc8315e-rdb.bin
296 => tftp 2000000 uImage-mpc8315e-rdb.dtb
297 => bootm 1000000 - 2000000
298
299--- Booting from JFFS2 root ---
300
301 1. First boot the board with NFS root.
302
303 2. Erase the MTD partition which will be used as root:
304
305 $ flash_eraseall /dev/mtd3
306
307 3. Copy the JFFS2 image to the MTD partition:
308
309 $ flashcp core-image-minimal-mpc8315e-rdb.jffs2 /dev/mtd3
310
311 4. Then reboot the board and set up the environment in U-Boot:
312
313 => setenv bootargs root=/dev/mtdblock3 rootfstype=jffs2 console=ttyS0,115200
314
315
316Ubiquiti Networks EdgeRouter Lite (edgerouter)
317==============================================
318
319The EdgeRouter Lite is part of the EdgeMax series. It is a MIPS64 router
320(based on the Cavium Octeon processor) with 512MB of RAM, which uses an
321internal USB pendrive for storage.
322
323Setup instructions
324------------------
325
326You will need the following:
327* RJ45 -> serial ("rollover") cable connected from your PC to the CONSOLE
328 port on the device
329* Ethernet connected to the first ethernet port on the board
330
331If using NFS as part of the setup process, you will also need:
332* NFS root setup on your workstation
333* TFTP server installed on your workstation (if fetching the kernel from
334 TFTP, see below).
335
336--- Preparation ---
337
338Build an image (e.g. core-image-minimal) using "edgerouter" as the MACHINE.
339In the following instruction it is based on core-image-minimal. Another target
340may be similiar with it.
341
342--- Booting from NFS root / kernel via TFTP ---
343
344Load the kernel, and boot the system as follows:
345
346 1. Get the kernel (vmlinux) file from the tmp/deploy/images/edgerouter
347 directory, and make them available on your TFTP server.
348
349 2. Connect the board's first serial port to your workstation and then start up
350 your favourite serial terminal so that you will be able to interact with
351 the serial console. If you don't have a favourite, picocom is suggested:
352
353 $ picocom /dev/ttyS0 -b 115200
354
355 3. Power up or reset the board and press a key on the terminal when prompted
356 to get to the U-Boot command line
357
358 4. Set up the environment in U-Boot:
359
360 => setenv ipaddr <board ip>
361 => setenv serverip <tftp server ip>
362
363 5. Download the kernel and boot:
364
365 => tftp tftp $loadaddr vmlinux
366 => bootoctlinux $loadaddr coremask=0x3 root=/dev/nfs rw nfsroot=<nfsroot ip>:<rootfs path> ip=<board ip>:<server ip>:<gateway ip>:<netmask>:edgerouter:eth0:off mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)
367
368--- Booting from USB disk ---
369
370To boot from the USB disk, you either need to remove it from the edgerouter
371box and populate it from another computer, or use a previously booted NFS
372image and populate from the edgerouter itself.
373
374Type 1: Use partitioned image
375-----------------------------
376
377Steps:
378
379 1. Remove the USB disk from the edgerouter and insert it into a computer
380 that has access to your build artifacts.
381
382 2. Flash the image.
383
384 # dd if=core-image-minimal-edgerouter.wic of=/dev/sdb
385
386 3. Insert USB disk into the edgerouter and boot it.
387
388Type 2: NFS
389-----------
390
391Note: If you place the kernel on the ext3 partition, you must re-create the
392 ext3 filesystem, since the factory u-boot can only handle 128 byte inodes and
393 cannot read the partition otherwise.
394
395 These boot instructions assume that you have recreated the ext3 filesystem with
396 128 byte inodes, you have an updated uboot or you are running and image capable
397 of making the filesystem on the board itself.
398
399
400 1. Boot from NFS root
401
402 2. Mount the USB disk partition 2 and then extract the contents of
403 tmp/deploy/core-image-XXXX.tar.bz2 into it.
404
405 Before starting, copy core-image-minimal-xxx.tar.bz2 and vmlinux into
406 rootfs path on your workstation.
407
408 and then,
409
410 # mount /dev/sda2 /media/sda2
411 # tar -xvjpf core-image-minimal-XXX.tar.bz2 -C /media/sda2
412 # cp vmlinux /media/sda2/boot/vmlinux
413 # umount /media/sda2
414 # reboot
415
416 3. Reboot the board and press a key on the terminal when prompted to get to the U-Boot
417 command line:
418
419 # reboot
420
421 4. Load the kernel and boot:
422
423 => ext2load usb 0:2 $loadaddr boot/vmlinux
424 => bootoctlinux $loadaddr coremask=0x3 root=/dev/sda2 rw rootwait mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)