OLPC Firmware q4b10

From OLPC

Jump to: navigation, search
  This page is monitored by the OLPC team.

Contents

OLPC Firmware Release q4b10

For A2 and later boards ONLY! Do not install on A1 boards.

  • new EC version,
  • working suspend and resume (Open Firmware only),
  • improved audio,
  • fix pingd,
  • hold EC in reset during reflash of Open Firmware,
  • thermal sensor watchdog reset,
  • enforce SPI FLASH write protect during security startup,
  • move camera reset pin.

To test suspend and resume:

ok test1
ok test2
ok test3
ok test4
Download q4b10.rom
Build date time 2011-09-23 03:51:07 (second cut)
Source revision 2532
EC version 0.2.04
CForth version 0cab8377
Wireless firmware version Libertas thinfirm 9.0.7.p2

Changes since q4b09

Open Firmware

  • svn 2531 - OLPC XO-1.75 - EC version 0.2.04
  • svn 2530 - OLPC XO-1.75 - different IP address for convenience function "newrom".
  • svn 2529 - OLPC security - added require-signatures? value for unsigned booting.
  • svn 2528 - Wifi - improved user interface for WPA authentication.
  • svn 2527 - OLPC XO-1.75 - Stabilizing suspend/resume.
  • svn 2526 - pingd no longer needs an argument; it implicitly uses "net//obp-tftp:last". If you need to change the target device, change the "net" devalias.
  • svn 2525 - Fixed pingd, which has been broken for a long time.
  • svn 2524 - ARM - >resolve broken; should be mask-op-and-or-offset, not simple add.
  • svn 2523 - OLPC XO-1.75 - hold EC in reset while flashing Open Firmware SPI FLASH, so that power button does not interrupt write. #11215.
  • svn 2522 - Forth core - added "dump-audio" command.
  • svn 2521 - OLPC XO-1.75 - audio selftest - fixed problem with intermittent channel reversal failures.
  • svn 2520 - OLPC XO-1.75 - Fixed problem with automatic audio selftest - the channel assignment now works correctly, with no need to flip the sync polarity.
  • svn 2519 - OLPC XO-1.75 - Goes with last checkin - (Improvements to suspend code for better DCON handling.)
  • svn 2518 - OLPC XO-1.75 - Improvements to suspend code for better DCON handling.
  • svn 2517 - OLPC XO-1.75 - Checkpoint of suspend code - seems to be working for the most part.
  • svn 2516 - OLPC XO-1.75 - Better management of ACK line to EC when not ready to receive events - part 2.
  • svn 2515 - OLPC XO-1.75 - Cleaned up some old cruft in the build script for nandblaster.
  • svn 2514 - OLPC XO-1.75 - Better management of ACK line to EC when not ready to receive events.
  • svn 2513 - ARM - ARM version of argb>565-pixel was badly broken.
  • svn 2512 - OLPC XO-1.75 - checkpoint of revised audio code. May still have rough edges.
  • svn 2511 - OLPC XO-1.75 - add thermal sensor watch mode
  • svn 2510 - OLPC XO-1.75 - enforce SPI FLASH write protect during security startup, #11228
  • svn 2509 - OLPC XO-1.75 - avoid turning off thermal sensor watchdog reset during watchdog configuration, add thermal sensor watchdog test script
  • svn 2508 - OLPC XO-1.75 - fix stack imbalance in fs-verify
  • svn 2507 - OLPC XO-1.75 - use correct timing commencement word, because secure fs-update, and normal fs-verify, displayed incorrect elapsed time because different timers are used for different resolutions on XO-1.75
  • svn 2506 - OLPC XO - fix stack imbalance when bad firmware image file detected, image length left behind.
  • svn 2505 - OLPC XO-1.75 B1 - move CAM_RST from GPIO 73 to GPIO 102, silently breaks camera test validity on A3, restores camera test validity on B1, fixes "EDI byte in timeout" failure reported by " flash-ec " after " test /camera " on B1 with R92 removed, requires cforth 17efd8f, see #11227
  • svn 2504 - OLPC XO-1.75 - automatically pull and build cforth in a subdirectory of the OFW build directory.

CForth

  • enable thermal protection watchdog reset,
  • power off if last reset was due to thermal protection watchdog,
  • support build within Open Firmware,
  • move camera reset pin,
  • fix usage of ACK line in EC communication.

EC

WLAN

  • no change


Which Firmware Do You Have?

The best method for finding out what firmware version you have on a laptop depends on whether the laptop is secured or not, and what operating state it is in.

Unsecured Laptop

Obtain the Ok prompt, the firmware version is displayed in the startup banner, thus:

 OLPC ..., ... memory installed, ..., S/N SHF7250024D
 OpenFirmware  q4b10 ...   EC Firmware Ver:...
               ^^^^^

You can also obtain the built date:

 ok .built

This is the date and time that this image of the firmware was built by the release engineer.

Secured Laptop

Power up the laptop with the "check" game button held down. You will be asked to Release the game keys to continue. Release the "check" game button and watch carefully. For a short time the startup banner will be displayed, like this:

 OLPC ..., ... memory installed, ..., S/N SHF7250024D
 OpenFirmware  q4b10 ...   EC Firmware Ver:...
               ^^^^^

Alternatively, if the laptop is already booted, go to the Sugar home view, click on the icon at the centre of the screen and select "My Settings" then "About my Computer." The firmware version is displayed there.

Alternatively, in the Terminal activity or a text console, type:

 cat /proc/device-tree/openprom/model

or

 cat /ofw/openprom/model

With certain older firmware versions, if the operating system will not start, and the laptop is secured, you will not be able to obtain the firmware version using the above methods, so our recommendation is to go ahead and upgrade anyway. The procedure is safe and will not do anything if you already have up-to-date firmware.


Installation

When installing new firmware, you must have a well-charged battery and the AC adapter plugged in. The firmware update code will not proceed otherwise. Possible error messages are:

error message how to fix
AC not present plug in the power cord, check the battery LED is on, then try again.
No external power plug in the power cord, check the battery LED is on, then try again,
No battery plug in the battery, check the latches, then try again, or try another battery,
Battery low allow more time for the battery to charge, then try again, or try another battery.

Unsecured Laptop

This section is for unsecured laptops. Most XO-1.5 and XO-1.75 laptops are unsecured. Most developer XO laptops are unsecured. To unsecure your laptop, follow the instructions at Activation and Developer Keys.

You may install using either:

  • a USB drive or SD card,
  • the laptop's internal drive,
  • a network.

Choose one.

Using a USB drive or SD card

  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • insert the USB drive or SD card,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if the downloaded file is on a USB drive, type:
 flash u:\q4b10.rom
  • if the downloaded file is on an external SD card:
 flash sd:\boot\q4b10.rom
  • wait for the laptop to reboot itself,
  • remove the USB drive or SD card.

(Expert users may remove the USB drive after the message "Got firmware" ... at this stage the file has been read and closed.)

Using the laptop internal drive

An alternate method is to download the firmware file to the laptop internal drive and then install from the internal drive.

  • start the laptop,
  • connect to a wireless or wired network,
su
cd /versions/boot/current/boot/
wget http://dev.laptop.org/pub/firmware/q4b10/q4b10.rom
  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if the downloaded file is on an XO-1, type:
flash n:\boot\q4b10.rom
  • if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q4b10.rom

Using a network

You will need a compatible USB to ethernet adapter, or an open or WEP wireless access point, connected to the internet.

  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if using wireless, type the essid of the wireless network:
essid mynetwork
  • if using a WPA wireless access point, type the WPA key for the network:
wpa passphrase
  • type the flash command using the download link above, but change all slash characters so they are backwards, for example:
flash http:\\dev.laptop.org\pub\firmware\q4b10\q4b10.rom

Secured Laptop

Secured laptops can only use flash firmware that has been signed. All mass-production machines had the latest firmware at the time of manufacture.

Upgrading firmware describes how to upgrade to a newer signed firmware release.

See also

  • Cheat codes for information about how game buttons control startup options.
Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox