summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2012-03-30 16:53:26 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-04-01 12:52:03 +0100
commit6a11c787571230e104699ea83aa50484ec1d8a86 (patch)
treecc40fff552e411cd32ca32fc1ad7c12f8728bca5
parent501f0da47fce7e8382910e03e2eb7861467d5fcb (diff)
downloadpoky-6a11c787571230e104699ea83aa50484ec1d8a86.tar.gz
poky-6a11c787571230e104699ea83aa50484ec1d8a86.tar.bz2
poky-6a11c787571230e104699ea83aa50484ec1d8a86.zip
README.hardware: extend USB-ZIP instructions
* Note that on some machines booting just stops after the SYSLINUX version banner is displayed * Add an instruction to show how to get the geometry information for the disk * Specify the number of cylinders when running mkdiskimage as it is sometimes unable to detect it automatically * Create the temporary mountpoints before attempting to use them * Add an instruction to unmount the disk before removing it Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-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:
# dd if=core-image-minimal-atom-pc.hddimg of=/dev/sdb
- If the device fails to boot with "Boot error" displayed, it is likely the BIOS
- cannot understand the physical layout of the disk (or rather it expects a
+ If the device fails to boot with "Boot error" displayed, or apparently
+ stops just after the SYSLINUX version banner, it is likely the BIOS cannot
+ understand the physical layout of the disk (or rather it expects a
particular layout and cannot handle anything else). There are two possible
solutions to this problem:
@@ -106,26 +107,47 @@ USB Device:
geometry from the device.
2. Without such an option, the BIOS generally boots the device in USB-ZIP
- mode.
+ mode. To write an image to a USB device that will be bootable in
+ USB-ZIP mode, carry out the following actions:
- a. Configure the USB device for USB-ZIP mode:
+ a. Determine the geometry of your USB device using fdisk:
+
+ # fdisk /dev/sdb
+ Command (m for help): p
+
+ Disk /dev/sdb: 4011 MB, 4011491328 bytes
+ 124 heads, 62 sectors/track, 1019 cylinders, total 7834944 sectors
+ ...
+
+ Command (m for help): q
+
+ b. Configure the USB device for USB-ZIP mode:
- # mkdiskimage -4 /dev/sdb 0 63 62
+ # mkdiskimage -4 /dev/sdb 1019 124 62
- Where 63 and 62 are the head and sector count as reported by fdisk.
- Remove and reinsert the device to allow the kernel to detect the new
- partition layout.
+ Where 1019, 124 and 62 are the cylinder, head and sectors/track counts
+ as reported by fdisk (substitute the values reported for your device).
+ When the operation has finished and the access LED (if any) on the
+ device stops flashing, remove and reinsert the device to allow the
+ kernel to detect the new partition layout.
- b. Copy the contents of the poky image to the USB-ZIP mode device:
+ c. Copy the contents of the poky image to the USB-ZIP mode device:
+ # mkdir /tmp/image
+ # mkdir /tmp/usbkey
# mount -o loop core-image-minimal-atom-pc.hddimg /tmp/image
# mount /dev/sdb4 /tmp/usbkey
# cp -rf /tmp/image/* /tmp/usbkey
- c. Install the syslinux boot loader:
+ d. Install the syslinux boot loader:
# syslinux /dev/sdb4
+ e. Unmount everything:
+
+ # umount /tmp/image
+ # umount /tmp/usbkey
+
Install the boot device in the target board and configure the BIOS to boot
from it.