Nandblaster for XO-1.5: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(rewrite instructions)
Line 5: Line 5:
How to install to multiple XO-1.5 using NANDblaster:
How to install to multiple XO-1.5 using NANDblaster:


The build is installed to the internal microSD device. You will need a USB memory stick of at least 1Gb capacity, but only for the duration of the installation.
* ensure receiver XO-1.5 have firmware q3a45 or later,

* ensure sender XO-1.5 has firmware q3a50 <!-- for nb-update --> or later,
* copy the os*.zd file to /fs.zd on a USB stick
* Prepare the USB memory stick:
* select one XO-1.5 to be the sender, (there is no change to what is installed on it),
** download the os*.zd file for the build you wish to install,
* insert the USB stick in the sender laptop,
** copy the file to the USB stick,
** rename the file to fs.zd,
* power up to the [[Ok]] prompt,
** check that the USB stick contains the file fs.zd,
* type <tt>nb-update</tt> and press enter,

* wait for nb-update to get going, when it says "pass 1" and counts up the blocks it is ready - it usually takes about 15 seconds,
* Prepare the sender laptop:
* power up the receiver laptops using the four game keys down sequence,
** choose a laptop, it must be an XO-1.5, it need not have anything installed on it, and if there is a build installed on it won't be changed by the process,
* if a receiver laptop does not start, try again,
** check that the laptop has firmware q3a50 <!-- for nb-update --> or later, upgrade the firmware if needed,
* wait for each laptop to finish and turn off (or reboot?),
** unlock the laptop if it is locked,
* when all have finished, type ESC on the sender laptop, then power it off and remove the USB stick.

* Start the sender laptop:
** insert the USB stick in the laptop,
** power up to the [[Ok]] prompt,
** type <tt>nb-update</tt> and press ''enter'',
** wait for it to get going, it is ready when you see "pass 1" and a slowly increasing block count ... it usually takes about 15 seconds,

* Start the receiver laptops, one by one or at will if you have many people helping:
** hold down the four game keys while turning on each laptop,
** watch the display until the coloured boxes begin to appear,

* If a receiver laptop does not properly start:
** ensure they have firmware q3a45 or later, upgrade the firmware if needed,
** try once more, wireless contention may have prevented association,
** move it closer to the sender, try once more, radiofrequency noise may have prevented association,

* Wait for all receiver laptops to finish

* Stop the sender laptop:
** press [[File:Esc.png]] ''Escape'' key on the sender laptop,
** power it off,
** remove the USB stick.


== Starting the Sender ==
== Starting the Sender ==

Revision as of 01:04, 5 August 2010

Quick Start

XO-1.5

How to install to multiple XO-1.5 using NANDblaster:

The build is installed to the internal microSD device. You will need a USB memory stick of at least 1Gb capacity, but only for the duration of the installation.

  • Prepare the USB memory stick:
    • download the os*.zd file for the build you wish to install,
    • copy the file to the USB stick,
    • rename the file to fs.zd,
    • check that the USB stick contains the file fs.zd,
  • Prepare the sender laptop:
    • choose a laptop, it must be an XO-1.5, it need not have anything installed on it, and if there is a build installed on it won't be changed by the process,
    • check that the laptop has firmware q3a50 or later, upgrade the firmware if needed,
    • unlock the laptop if it is locked,
  • Start the sender laptop:
    • insert the USB stick in the laptop,
    • power up to the Ok prompt,
    • type nb-update and press enter,
    • wait for it to get going, it is ready when you see "pass 1" and a slowly increasing block count ... it usually takes about 15 seconds,
  • Start the receiver laptops, one by one or at will if you have many people helping:
    • hold down the four game keys while turning on each laptop,
    • watch the display until the coloured boxes begin to appear,
  • If a receiver laptop does not properly start:
    • ensure they have firmware q3a45 or later, upgrade the firmware if needed,
    • try once more, wireless contention may have prevented association,
    • move it closer to the sender, try once more, radiofrequency noise may have prevented association,
  • Wait for all receiver laptops to finish
  • Stop the sender laptop:
    • press Esc.png Escape key on the sender laptop,
    • power it off,
    • remove the USB stick.

Starting the Sender

NANDblasting an Unsigned Filesystem Image File

To send an unsigned filesystem image, put the filesystem image file (*.zd) on a USB key as "/fs.zd". Insert the USB key into the sending XO and type:

 ok nb-update

NANDblasting a Signed Filesystem Image File

To send a signed filesystem image, put the filesystem image file (*.zd) on a USB key as "/fs.zd". Put the corresponding signature bundle (the .zip that contains a control file and a signature file) on the USB key as "/fs.zip". Insert the USB key into the sending XO and type:

 ok nb-secure

Stopping

You can stop the sender by typing the ESC key or by powering off. If you type any other key, the sender will pause and ask you if you want to stop. If you then type 'y', it will stop; other keys will resume the sending.

"No quiet channels" - Forcing the Channel

The sender chooses a wireless channel automatically by scanning to find the least-busy channel. If they are all busy, i.e. they all have received signal strength values exceeding some threshold, the sender tell you which one has the least signal strength and ask for confirmation before proceeding on that channel.

You can force it to use a specific channel by appending either "1", "6", or "11" to one of the commands above, for example:

 ok nb-update6

or

 ok nb-secure11

If you force the channel, the sender won't check if the channel is busy, it will just start sending.

Changing the Redundancy

You can change the redundancy percentage before you execute one of the send commands. For example, to set the sender redundancy to 12% (the default is 20%), type:

 ok d# 12 to redundancy

The redundancy controls the number of extra error correction packets that the sender sends for each erase block worth of source data.

Design Notes

Nandblaster_for_XO-1.5_Design_Discussion