Poky Project Discussions
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Yocto Project Discussions <yocto@linux.intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [Yocto] RFC: README.hardware: Intel Atom device documentation
Date: Wed, 15 Dec 2010 19:31:04 -0600	[thread overview]
Message-ID: <1292463064.2104.40.camel@elmorro> (raw)
In-Reply-To: <4D095AB5.6060805@linux.intel.com>

On Wed, 2010-12-15 at 16:17 -0800, Darren Hart wrote:
> I ran across some issues working with USB keys while booting a couple
> different Intel Atom based devices. I drafted the following documenting
> what I learned from the process. I'd like to add this (or something
> similar) to README.hardware.
> 
> Thoughts/Comments?
> 

Hey, thanks for this - it solved the same problem I was having with the
sdk image :-)  One small correction below...

> 
> Intel Atom based PCs and devices (atom-pc)
> ==========================================
> 
> The atom-pc MACHINE is tested on the following platforms:
> 
>   o Asus eee901
>   o Acer Aspire One
>   o Toshiba NB305
>   o Intel BlackSand development board (FIXME: correct name)
> 
> and is likely to work on many unlisted atom based devices. The MACHINE
> type supports ethernet, wifi, sound, and i915 graphics by default in
> addition to common PC input devices, busses, and so on.
> 
> Depending on the device, it can boot from a traditional hard-disk, a USB
> device, or over the network. Writing poky generated images to physical
> is straightforward with a caveat for USB devices. The following examples
> assume the target boot device is /dev/sdb, be sure to verify this and
> use the correct device as the following commands are run as root and are
> not reversable.
> 
> Hard Disk:
>   1. Build a directdisk image format. This will generate proper
>      partition tables that will in turn be written to the physical media.
>   
>   2. Use the "dd" utility to write the image to the raw block device.
>      For example:
> 
>      $ dd if=poky-image-minimal-live-atom-pc-20101214120906.ddimg of=/dev/sdb
>      FIXME: verify image name and extension
> 
> USB Device:
>   1. Build an hddimg image format. This is a simple filesystem without
>      partition tables and is suitable for USB keys.
> 
>   2. Use the "dd" utility to write the image to the raw block device.
>      For example:
> 
>      $ dd if=poky-image-minimal-live-atom-pc-20101214120906.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 it to be a particular layout and can't handle anything
>   else). There are two possible solutions to this problem:
> 
>   1. Change the BIOS USB Device setting to HDD mode. The label will vary
>      my device, but the idea is to force BIOS to read the
>      Cylinder/Head/Sector geometry from the device.
> 
>   2. Without such an option, the BIOS generally boots the device in
>      USB-ZIP mode.
> 
>      a. Configure the USB device for USB-ZIP mode:
>      
>      # mkdiskimage -4 /dev/sdb 0 63 62
> 
>      Where 63 and 62 are the cylinder and head count as reported by

should be: head and sector rather than cylinder and
head.                               

Thanks,

Tom

>      fdisk.  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:
> 
>      # mount -o loop poky-image-minimal-live-atom-pc-20101214120906.hddimg  /tmp/image
>      # mount /dev/sdb4 /tmp/usbkey
>      # cp -rf /tmp/image/* /tmp/usbkey
> 
>      c. Install the syslinux boot loader:
> 
>      # syslinux /dev/sdb4
> 
>   Install the boot device in the target board and configure the BIOS to
>   boot from it.
> 
>   For more details on the USB-ZIP scenario, see the syslinux documentation:
>   http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob_plain;f=doc/usbkey.txt;hb=HEAD
> 




  reply	other threads:[~2010-12-16  1:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  0:17 RFC: README.hardware: Intel Atom device documentation Darren Hart
2010-12-16  1:31 ` Tom Zanussi [this message]
2010-12-16 16:25   ` [Yocto] " Darren Hart
2010-12-16 16:29     ` Tom Zanussi
2010-12-16 15:44 ` Richard Purdie
2010-12-16 16:40   ` Darren Hart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1292463064.2104.40.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=yocto@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox