summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--README.hardware42
1 files changed, 32 insertions, 10 deletions
diff --git a/README.hardware b/README.hardware
index 11877367f4..d48c9533e7 100644
--- a/README.hardware
+++ b/README.hardware
@@ -96,8 +96,9 @@ USB Device:
96 96
97 # dd if=core-image-minimal-atom-pc.hddimg of=/dev/sdb 97 # dd if=core-image-minimal-atom-pc.hddimg of=/dev/sdb
98 98
99 If the device fails to boot with "Boot error" displayed, it is likely the BIOS 99 If the device fails to boot with "Boot error" displayed, or apparently
100 cannot understand the physical layout of the disk (or rather it expects a 100 stops just after the SYSLINUX version banner, it is likely the BIOS cannot
101 understand the physical layout of the disk (or rather it expects a
101 particular layout and cannot handle anything else). There are two possible 102 particular layout and cannot handle anything else). There are two possible
102 solutions to this problem: 103 solutions to this problem:
103 104
@@ -106,26 +107,47 @@ USB Device:
106 geometry from the device. 107 geometry from the device.
107 108
108 2. Without such an option, the BIOS generally boots the device in USB-ZIP 109 2. Without such an option, the BIOS generally boots the device in USB-ZIP
109 mode. 110 mode. To write an image to a USB device that will be bootable in
111 USB-ZIP mode, carry out the following actions:
110 112
111 a. Configure the USB device for USB-ZIP mode: 113 a. Determine the geometry of your USB device using fdisk:
114
115 # fdisk /dev/sdb
116 Command (m for help): p
117
118 Disk /dev/sdb: 4011 MB, 4011491328 bytes
119 124 heads, 62 sectors/track, 1019 cylinders, total 7834944 sectors
120 ...
121
122 Command (m for help): q
123
124 b. Configure the USB device for USB-ZIP mode:
112 125
113 # mkdiskimage -4 /dev/sdb 0 63 62 126 # mkdiskimage -4 /dev/sdb 1019 124 62
114 127
115 Where 63 and 62 are the head and sector count as reported by fdisk. 128 Where 1019, 124 and 62 are the cylinder, head and sectors/track counts
116 Remove and reinsert the device to allow the kernel to detect the new 129 as reported by fdisk (substitute the values reported for your device).
117 partition layout. 130 When the operation has finished and the access LED (if any) on the
131 device stops flashing, remove and reinsert the device to allow the
132 kernel to detect the new partition layout.
118 133
119 b. Copy the contents of the poky image to the USB-ZIP mode device: 134 c. Copy the contents of the poky image to the USB-ZIP mode device:
120 135
136 # mkdir /tmp/image
137 # mkdir /tmp/usbkey
121 # mount -o loop core-image-minimal-atom-pc.hddimg /tmp/image 138 # mount -o loop core-image-minimal-atom-pc.hddimg /tmp/image
122 # mount /dev/sdb4 /tmp/usbkey 139 # mount /dev/sdb4 /tmp/usbkey
123 # cp -rf /tmp/image/* /tmp/usbkey 140 # cp -rf /tmp/image/* /tmp/usbkey
124 141
125 c. Install the syslinux boot loader: 142 d. Install the syslinux boot loader:
126 143
127 # syslinux /dev/sdb4 144 # syslinux /dev/sdb4
128 145
146 e. Unmount everything:
147
148 # umount /tmp/image
149 # umount /tmp/usbkey
150
129 Install the boot device in the target board and configure the BIOS to boot 151 Install the boot device in the target board and configure the BIOS to boot
130 from it. 152 from it.
131 153