summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2011-03-18 16:42:52 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-18 17:22:25 (GMT)
commitd2658c81017e5445e592a7c90222aaf37686486f (patch)
tree4783b8e8d73336963525dccd9ab30bc5cb9441d5 /README.hardware
parentcb5e5139d4ea471e0bb374ee09c62d860c5ac2b7 (diff)
downloadpoky-d2658c81017e5445e592a7c90222aaf37686486f.tar.gz
README.hardware: update for 1.0 release
* Update to refer to Yocto documentation * Change title as suggested by Scott Rifenbark * List all qemu* machine targets * Remove machines no longer in core layer * Add instructions for routerstationpro (originally based on an email from Mark Hatle) (From OE-Core rev: f8e9b15aa694b0f6d3373c2b6bf8904fdb0c7b86) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README.hardware')
-rw-r--r--README.hardware573
1 files changed, 170 insertions, 403 deletions
diff --git a/README.hardware b/README.hardware
index c0df01b..c68ad43 100644
--- a/README.hardware
+++ b/README.hardware
@@ -1,429 +1,66 @@
1 Poky Hardware Reference Guide 1 Poky Hardware README
2 ============================= 2 ====================
3 3
4This file gives details about using Poky with different hardware reference 4This file gives details about using Poky with different hardware reference
5boards and consumer devices. A full list of target machines can be found by 5boards and consumer devices. A full list of target machines can be found by
6looking in the meta/conf/machine/ directory. If in doubt about using Poky with 6looking in the meta/conf/machine/ directory. If in doubt about using Poky with
7your hardware, consult the documentation for your board/device. To discuss 7your hardware, consult the documentation for your board/device.
8support for further hardware reference boards/devices please contact OpenedHand.
9 8
10QEMU Emulation Images (qemuarm and qemux86) 9Support for additional devices is normally added by creating BSP layers - for
11=========================================== 10more information please see the Yocto Board Support Package (BSP) Developer's
12 11Guide - documentation source is in documentation/bspguide or download the PDF
13To simplify development Poky supports building images to work with the QEMU 12from:
14emulator in system emulation mode. Two architectures are currently supported,
15ARM (via qemuarm) and x86 (via qemux86). Use of the QEMU images is covered
16in the Poky Handbook.
17
18Hardware Reference Boards
19=========================
20
21The following boards are supported by Poky:
22
23 * Compulab CM-X270 (cm-x270)
24 * Compulab EM-X270 (em-x270)
25 * FreeScale iMX31ADS (mx31ads)
26 * Marvell PXA3xx Zylonite (zylonite)
27 * Logic iMX31 Lite Kit (mx31litekit)
28 * Phytec phyCORE-iMX31 (mx31phy)
29 * Texas Instruments Beagleboard (beagleboard)
30
31For more information see board's section below. The Poky MACHINE setting
32corresponding to the board is given in brackets.
33
34Consumer Devices
35================
36
37The following consumer devices are supported by Poky:
38
39 * FIC Neo1973 GTA01 smartphone (fic-gta01)
40 * HTC Universal (htcuniversal)
41 * Nokia 770/N800/N810 Internet Tablets (nokia770 and nokia800)
42 * Sharp Zaurus SL-C7x0 series (c7x0)
43 * Sharp Zaurus SL-C1000 (akita)
44 * Sharp Zaurus SL-C3x00 series (spitz)
45
46For more information see board's section below. The Poky MACHINE setting
47corresponding to the board is given in brackets.
48
49
50 Hardware Reference Boards
51 =========================
52
53Compulab CM-X270 (cm-x270)
54==========================
55
56The bootloader on this board doesn't support writing jffs2 images directly to
57NAND and normally uses a proprietary kernel flash driver. To allow the use of
58jffs2 images, a two stage updating procedure is needed. Firstly, an initramfs
59is booted which contains mtd utilities and this is then used to write the main
60filesystem.
61
62It is assumed the board is connected to a network where a TFTP server is
63available and that a serial terminal is available to communicate with the
64bootloader (38400, 8N1). If a DHCP server is available the device will use it
65to obtain an IP address. If not, run:
66
67 ARMmon > setip dhcp off
68 ARMmon > setip ip 192.168.1.203
69 ARMmon > setip mask 255.255.255.0
70
71To reflash the kernel:
72
73 ARMmon > download kernel tftp zimage 192.168.1.202
74 ARMmon > flash kernel
75
76where zimage is the name of the kernel on the TFTP server and its IP address is
77192.168.1.202. The names of the files must be all lowercase.
78
79To reflash the initrd/initramfs:
80
81 ARMmon > download ramdisk tftp diskimage 192.168.1.202
82 ARMmon > flash ramdisk
83
84where diskimage is the name of the initramfs image (a cpio.gz file).
85
86To boot the initramfs:
87
88 ARMmon > ramdisk on
89 ARMmon > bootos "console=ttyS0,38400 rdinit=/sbin/init"
90
91To reflash the main image login to the system as user "root", then run:
92
93 # ifconfig eth0 192.168.1.203
94 # tftp -g -r mainimage 192.168.1.202
95 # flash_eraseall /dev/mtd1
96 # nandwrite /dev/mtd1 mainimage
97
98which configures the network interface with the IP address 192.168.1.203,
99downloads the "mainimage" file from the TFTP server at 192.168.1.202, erases
100the flash and then writes the new image to the flash.
101
102The main image can then be booted with:
103
104 ARMmon > bootos "console=ttyS0,38400 root=/dev/mtdblock1 rootfstype=jffs2"
105
106Note that the initramfs image is built by poky in a slightly different mode to
107normal since it uses uclibc. To generate this use a command like:
108
109IMAGE_FSTYPES=cpio.gz MACHINE=cm-x270 POKYLIBC=uclibc bitbake poky-image-minimal-mtdutils
110
111
112Compulab EM-X270 (em-x270)
113==========================
114
115Fetch the "Linux - kernel and run-time image (Angstrom)" ZIP file from the
116Compulab website. Inside the images directory of this ZIP file is another ZIP
117file called 'LiveDisk.zip'. Extract this over a cleanly formatted vfat USB flash
118drive. Replace the 'em_x270.img' file with the 'updater-em-x270.ext2' file.
119
120Insert this USB disk into the supplied adapter and connect this to the
121board. Whilst holding down the the suspend button press the reset button. The
122board will now boot off the USB key and into a version of Angstrom. On the
123desktop is an icon labelled "Updater". Run this program to launch the updater
124that will flash the Poky kernel and rootfs to the board.
125
126
127FreeScale iMX31ADS (mx31ads)
128===========================
129
130The correct serial port is the top-most female connector to the right of the
131ethernet socket.
132
133For uploading data to RedBoot we are going to use tftp. In this example we
134assume that the tftpserver is on 192.168.9.1 and the board is on192.168.9.2.
135
136To set the IP address, run:
137
138 ip_address -l 192.168.9.2/24 -h 192.168.9.1
139
140To download a kernel called "zimage" from the TFTP server, run:
141
142 load -r -b 0x100000 zimage
143
144To write the kernel to flash run:
145
146 fis create kernel
147
148To download a rootfs jffs2 image "rootfs" from the TFTP server, run:
149
150 load -r -b 0x100000 rootfs
151
152To write the root filesystem to flash run:
153
154 fis create root
155
156To load and boot a kernel and rootfs from flash:
157
158 fis load kernel
159 exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock2 rootfstype=jffs2 init=linuxrc ip=none"
160
161To load and boot a kernel from a TFTP server with the rootfs over NFS:
162
163 load -r -b 0x100000 zimage
164 exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.9.1:/mnt/nfsmx31 rw ip=192.168.9.2::192.168.9.1:255.255.255.0"
165
166The instructions above are for using the (default) NOR flash on the board,
167there is also 128M of NAND flash. It is possible to install Poky to the NAND
168flash which gives more space for the rootfs and instructions for using this are
169given below. To switch to the NAND flash:
170
171 factive NAND
172
173This will then restart RedBoot using the NAND rather than the NOR. If you
174have not used the NAND before then it is unlikely that there will be a
175partition table yet. You can get the list of partitions with 'fis list'.
176
177If this shows no partitions then you can create them with:
178
179 fis init
180
181The output of 'fis list' should now show:
182
183Name FLASH addr Mem addr Length Entry point
184RedBoot 0xE0000000 0xE0000000 0x00040000 0x00000000
185FIS directory 0xE7FF4000 0xE7FF4000 0x00003000 0x00000000
186RedBoot config 0xE7FF7000 0xE7FF7000 0x00001000 0x00000000
187
188Partitions for the kernel and rootfs need to be created:
189
190fis create -l 0x1A0000 -e 0x00100000 kernel
191fis create -l 0x5000000 -e 0x00100000 root
192
193You may now use the instructions above for flashing. However it is important
194to note that the erase block size for the NAND is different to the NOR so the
195JFFS erase size will need to be changed to 0x4000. Stardard images are built
196for NOR and you will need to build custom images for NAND.
197
198You will also need to update the kernel command line to use the correct root
199filesystem. This should be '/dev/mtdblock7' if you adhere to the partitioning
200scheme shown above. If this fails then you can doublecheck against the output
201from the kernel when it evaluates the available mtd partitions.
202
203
204Marvell PXA3xx Zylonite (zylonite)
205==================================
206
207These instructions assume the Zylonite is connected to a machine running a TFTP
208server at address 192.168.123.5 and that a serial link (38400 8N1) is available
209to access the blob bootloader. The kernel is on the TFTP server as
210"zylonite-kernel" and the root filesystem jffs2 file is "zylonite-rootfs" and
211the images are to be saved in NAND flash.
212
213The following commands setup blob:
214
215 blob> setip client 192.168.123.4
216 blob> setip server 192.168.123.5
217
218To flash the kernel:
219
220 blob> tftp zylonite-kernel
221 blob> nandwrite -j 0x80800000 0x60000 0x200000
222
223To flash the rootfs:
224
225 blob> tftp zylonite-rootfs
226 blob> nanderase -j 0x260000 0x5000000
227 blob> nandwrite -j 0x80800000 0x260000 <length>
228
229(where <length> is the rootfs size which will be printed by the tftp step)
230
231To boot the board:
232
233 blob> nkernel
234 blob> boot
235
236
237Logic iMX31 Lite Kit (mx31litekit)
238===============================
239 13
240The easiest method to boot this board is to take an MMC/SD card and format 14 http://yoctoproject.org/community/documentation
241the first partition as ext2, then extract the poky image onto this as root.
242Assuming the board is network connected, a TFTP server is available at
243192.168.1.33 and a serial terminal is available (115200 8N1), the following
244commands will boot a kernel called "mx31kern" from the TFTP server:
245 15
246 losh> ifconfig sm0 192.168.1.203 255.255.255.0 192.168.1.33 16Support for machines other than QEMU may be moved out to separate BSP layers in
247 losh> load raw 0x80100000 0x200000 /tftp/192.168.1.33:mx31kern 17future versions.
248 losh> exec 0x80100000 -
249 18
250 19
251Phytec phyCORE-iMX31 (mx31phy) 20QEMU Emulation Targets
252============================== 21======================
253 22
254Support for this board is currently being developed. Experimental jffs2 23To simplify development Poky supports building images to work with the QEMU
255images and a suitable kernel are available and are known to work with the 24emulator in system emulation mode. Several architectures are currently
256board. 25supported:
257
258
259 Consumer Devices
260 ================
261
262FIC Neo1973 GTA01 smartphone (fic-gta01)
263========================================
264
265To install Poky on a GTA01 smartphone you will need "dfu-util" tool
266which you can build with "bitbake dfu-util-native" command.
267
268Flashing requires these steps:
269
270 1. Power down the device.
271 2. Connect the device to the host machine via USB.
272 3. Hold AUX key and press Power key. There should be a bootmenu
273 on screen.
274 4. Run "dfu-util -l" to check if the phone is visible on the USB bus.
275 The output should look like this:
276
277 dfu-util - (C) 2007 by OpenMoko Inc.
278 This program is Free Software and has ABSOLUTELY NO WARRANTY
279
280 Found Runtime: [0x1457:0x5119] devnum=19, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"
281
282 5. Flash the kernel with "dfu-util -a kernel -D uImage-2.6.21.6-moko11-r2-fic-gta01.bin"
283 6. Flash rootfs with "dfu-util -a rootfs -D <image>", where <image> is the
284 jffs2 image file to use as the root filesystem
285 (e.g. ./tmp/deploy/images/poky-image-sato-fic-gta01.jffs2)
286
287
288HTC Universal (htcuniversal)
289============================
290
291Note: HTC Universal support is highly experimental.
292
293On the HTC Universal, entirely replacing the Windows installation is not
294supported, instead Poky is booted from an MMC/SD card from Windows. Once Poky
295has booted, Windows is no longer in memory or active but when power is removed,
296the user will be returned to windows and will need to return to Linux from
297there.
298
299Once an MMC/SD card is available it is suggested its split into two partitions,
300one for a program called HaRET which lets you boot Linux from within Windows
301and the second for the rootfs. The HaRET partition should be the first partition
302on the card and be vfat formatted. It doesn't need to be large, just enough for
303HaRET and a kernel (say 5MB max). The rootfs should be ext2 and is usually the
304second partition. The first partition should be vfat so Windows recognises it
305as if it doesn't, it has been known to reformat cards.
306
307On the first partition you need three files:
308
309 * a HaRET binary (version 0.5.1 works well and a working version
310 should be part of the last Poky release)
311 * a kernel renamed to "zImage"
312 * a default.txt which contains:
313
314set kernel "zImage"
315set mtype "855"
316set cmdline "root=/dev/mmcblk0p2 rw console=ttyS0,115200n8 console=tty0 rootdelay=5 fbcon=rotate:1"
317boot2
318
319On the second parition the root file system is extracted as root. A different
320partition layout or other kernel options can be changed in the default.txt file.
321
322When inserted into the device, Windows should see the card and let you browse
323its contents using File Explorer. Running the HaRET binary will present a dialog
324box (maybe after messages warning about running unsigned binaries) where you
325select OK and you should then see Poky boot. Kernel messages can be seen by
326adding psplash=false to the kernel commandline.
327
328
329Nokia 770/N800/N810 Internet Tablets (nokia770 and nokia800)
330============================================================
331
332Note: Nokia tablet support is highly experimental.
333
334The Nokia internet tablet devices are OMAP based tablet formfactor devices
335with large screens (800x480), wifi and touchscreen.
336
337To flash images to these devices you need the "flasher" utility which can be
338downloaded from the http://tablets-dev.nokia.com/d3.php?f=flasher-3.0. This
339utility needs to be run as root and the usb filesystem needs to be mounted
340although most distributions will have done this for you. Once you have this
341follow these steps:
342
343 1. Power down the device.
344 2. Connect the device to the host machine via USB
345 (connecting power to the device doesn't hurt either).
346 3. Run "flasher -i"
347 4. Power on the device.
348 5. The program should give an indication it's found
349 a tablet device. If not, recheck the cables, make sure you're
350 root and usbfs/usbdevfs is mounted.
351 6. Run "flasher -r <image> -k <kernel> -f", where <image> is the
352 jffs2 image file to use as the root filesystem
353 (e.g. ./tmp/deploy/images/poky-image-sato-nokia800.jffs2)
354 and <kernel> is the kernel to use
355 (e.g. ./tmp/deploy/images/zImage-nokia800.bin).
356 7. Run "flasher -R" to reboot the device.
357 8. The device should boot into Poky.
358
359The nokia800 images and kernel will run on both the N800 and N810.
360
361
362Sharp Zaurus SL-C7x0 series (c7x0)
363==================================
364
365The Sharp Zaurus c7x0 series (SL-C700, SL-C750, SL-C760, SL-C860, SL-7500)
366are PXA25x based handheld PDAs with VGA screens. To install Poky images on
367these devices follow these steps:
368
369 1. Obtain an SD/MMC or CF card with a vfat or ext2 filesystem.
370 2. Copy a jffs2 image file (e.g. poky-image-sato-c7x0.jffs2) onto the
371 card as "initrd.bin":
372
373 $ cp ./tmp/deploy/images/poky-image-sato-c7x0.jffs2 /path/to/my-cf-card/initrd.bin
374
375 3. Copy an Linux kernel file (zImage-c7x0.bin) onto the card as
376 "zImage.bin":
377 26
378 $ cp ./tmp/deploy/images/zImage-c7x0.bin /path/to/my-cf-card/zImage.bin 27 * ARM (qemuarm)
28 * x86 (qemux86)
29 * x86-64 (qemux86-64)
30 * PowerPC (qemuppc)
31 * MIPS (qemumips)
379 32
380 4. Copy an updater script (updater.sh.c7x0) onto the card 33Use of the QEMU images is covered in the Poky Reference Manual. The Poky
381 as "updater.sh": 34MACHINE setting corresponding to the target is given in brackets.
382 35
383 $ cp ./tmp/deploy/images/updater.sh.c7x0 /path/to/my-cf-card/updater.sh
384 36
385 5. Power down the Zaurus. 37Hardware Reference Boards
386 6. Hold "OK" key and power on the device. An update menu should appear 38=========================
387 (in Japanese).
388 7. Choose "Update" (item 4).
389 8. The next screen will ask for the source, choose the appropriate
390 card (CF or SD).
391 9. Make sure AC power is connected.
392 10. The next screen asks for confirmation, choose "Yes" (the left button).
393 11. The update process will start, flash the files on the card onto
394 the device and the device will then reboot into Poky.
395 39
40The following boards are supported by Poky's core layer:
396 41
397Sharp Zaurus SL-C1000 (akita) 42 * Texas Instruments Beagleboard (beagleboard)
398============================= 43 * Freescale MPC8315E-RDB (mpc8315e-rdb)
44 * Ubiquiti Networks RouterStation Pro (routerstationpro)
399 45
400The Sharp Zaurus SL-C1000 is a PXA270 based device otherwise similar to the 46For more information see the board's section below. The Poky MACHINE setting
401c7x0. To install Poky images on this device follow the instructions for 47corresponding to the board is given in brackets.
402the c7x0 but replace "c7x0" with "akita" where appropriate.
403 48
404 49
405Sharp Zaurus SL-C3x00 series (spitz) 50Consumer Devices
406==================================== 51================
407 52
408The Sharp Zaurus SL-C3x00 devices are PXA270 based devices similar 53The following consumer devices are supported by Poky's core layer:
409to akita but with an internal microdrive. The installation procedure
410assumes a standard microdrive based device where the root (first)
411partition has been enlarged to fit the image (at least 100MB,
412400MB for the SDK).
413 54
414The procedure is the same as for the c7x0 and akita models with the 55 * Intel Atom based PCs and devices (atom-pc)
415following differences:
416 56
417 1. Instead of a jffs2 image you need to copy a compressed tarball of the 57For more information see the device's section below. The Poky MACHINE setting
418 root fileystem (e.g. poky-image-sato-spitz.tar.gz) onto the 58corresponding to the device is given in brackets.
419 card as "hdimage1.tgz":
420 59
421 $ cp ./tmp/deploy/images/poky-image-sato-spitz.tar.gz /path/to/my-cf-card/hdimage1.tgz
422 60
423 2. You additionally need to copy a special tar utility (gnu-tar) onto
424 the card as "gnu-tar":
425 61
426 $ cp ./tmp/deploy/images/gnu-tar /path/to/my-cf-card/gnu-tar 62 Specific Hardware Documentation
63 ===============================
427 64
428 65
429Intel Atom based PCs and devices (atom-pc) 66Intel Atom based PCs and devices (atom-pc)
@@ -580,3 +217,133 @@ Note: As of the 2.6.37 linux-yocto kernel recipe, the Beagleboard uses the
580 order to setup the getty on the serial line: 217 order to setup the getty on the serial line:
581 218
582 SERIAL_CONSOLE_beagleboard = "115200 ttyS2" 219 SERIAL_CONSOLE_beagleboard = "115200 ttyS2"
220
221
222Ubiquiti Networks RouterStation Pro (routerstationpro)
223======================================================
224
225You will need the following:
226* A serial cable - female to female (or female to male + gender changer)
227 NOTE: cable must be straight through, *not* a null modem cable.
228* USB flash drive or hard disk that is able to be powered from the
229 board's USB port.
230* tftp server installed on your workstation
231
232NOTE: in the following instructions it is assumed that /dev/sdb corresponds
233to the USB disk when it is plugged into your workstation. If this is not the
234case in your setup then please be careful to substitute the correct device
235name in all commands where appropriate.
236
237--- Preparation ---
238
2391) Build an image (e.g. poky-image-minimal) using "routerstationpro" as the
240MACHINE
241
2422) Partition the USB drive so that primary partition 1 is type Linux (83).
243Minimum size depends on your root image size - poky-image-minimal probably
244only needs 8-16MB, other images will need more.
245
246 # fdisk /dev/sdb
247 Command (m for help): p
248
249 Disk /dev/sdb: 4011 MB, 4011491328 bytes
250 124 heads, 62 sectors/track, 1019 cylinders, total 7834944 sectors
251 Units = sectors of 1 * 512 = 512 bytes
252 Sector size (logical/physical): 512 bytes / 512 bytes
253 I/O size (minimum/optimal): 512 bytes / 512 bytes
254 Disk identifier: 0x0009e87d
255
256 Device Boot Start End Blocks Id System
257 /dev/sdb1 62 1952751 976345 83 Linux
258
2593) Format partition 1 on the USB as ext3
260
261 # mke2fs -j /dev/sdb1
262
2634) Mount partition 1 and then extract the contents of
264tmp/deploy/images/poky-image-XXXX.tar.bz2 into it (preserving permissions).
265
266 # mount /dev/sdb1 /media/sdb1
267 # cd /media/sdb1
268 # tar -xvjpf tmp/deploy/images/poky-image-XXXX.tar.bz2
269
2705) Unmount the USB drive and then plug it into the board's USB port
271
2726) Connect the board's serial port to your workstation and then start up
273your favourite serial terminal so that you will be able to interact with
274the serial console. (If you don't have a favourite, picocom is suggested.)
275
2767) Connect the network into eth0 (the one that is NOT the 3 port switch). If
277you are using power-over-ethernet then the board will power up at this point.
278
2798) Start up the board, watch the serial console. Hit Ctrl+C to abort the
280autostart if the board is configured that way (it is by default). The
281bootloader's fconfig command can be used to disable autostart and configure
282the IP settings if you need to change them (default IP is 192.168.1.20).
283
2849) Make the kernel (tmp/deploy/images/vmlinux-routerstationpro.bin) available
285on the tftp server.
286
28710) If you are going to write the kernel to flash (optional - see "Booting a
288kernel directly" below for the alternative), remove the current kernel and
289rootfs flash partitions. You can list the partitions using the following
290bootloader command:
291
292 RedBoot> fis list
293
294You can delete the existing kernel and rootfs with these commands:
295
296 RedBoot> fis delete kernel
297 RedBoot> fis delete rootfs
298
299--- Booting a kernel directly ---
300
3011) Load the kernel using the following bootloader command:
302
303 RedBoot> load -m tftp -h <ip of tftp server> vmlinux-routerstationpro.bin
304
305You should see a message on it being successfully loaded.
306
3072) Execute the kernel:
308
309 RedBoot> exec -c "console=ttyS0,115200 root=/dev/sda1 rw rootdelay=2 board=UBNT-RSPRO"
310
311Note that specifying the command line with -c is important as linux-yocto does
312not provide a default command line.
313
314--- Writing a kernel to flash ---
315
3161) Go to your tftp server and gzip the kernel you want in flash. It should
317halve the size.
318
3192) Load the kernel using the following bootloader command:
320
321 RedBoot> load -r -b 0x80600000 -m tftp -h <ip of tftp server> vmlinux-routerstationpro.bin.gz
322
323This should output something similar to the following:
324
325 Raw file loaded 0x80600000-0x8087c537, assumed entry at 0x80600000
326
327Calculate the length by subtracting the first number from the second number
328and then rounding the result up to the nearest 0x1000.
329
3303) Using the length calculated above, create a flash partition for the kernel:
331
332 RedBoot> fis create -b 0x80600000 -l 0x240000 kernel
333
334(change 0x240000 to your rounded length -- change "kernel" to whatever
335you want to name your kernel)
336
337--- Booting a kernel from flash ---
338
339To boot the flashed kernel perform the following steps.
340
3411) At the bootloader prompt, load the kernel:
342
343 RedBoot> fis load -d -e kernel
344
345(Change the name "kernel" above if you chose something different earlier)
346
347(-e means 'elf', -d 'decompress')
348
3492) Execute the kernel using the exec command as above.