OLPC Firmware q4c06: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Proper name for Open Firmware)
 
Line 8: Line 8:
This is a test candidate for the C2 build:
This is a test candidate for the C2 build:
* a change to the architecture device-tree tag,
* a change to the architecture device-tree tag,
* during automatic OpenFirmware reflash, show progress bar,
* during automatic Open Firmware reflash, show progress bar,
* during automatic EC reflash, prevent keyboard interrupt, show progress bar,
* during automatic EC reflash, prevent keyboard interrupt, show progress bar,
* show battery icon with sad face if not enough power sources present for automatic reflash,
* show battery icon with sad face if not enough power sources present for automatic reflash,
Line 37: Line 37:
== Changes since q4c05 ==
== Changes since q4c05 ==


=== OpenFirmware ===
=== Open Firmware ===


* [http://tracker.coreboot.org/trac/openfirmware/changeset/2715 2715] OLPC XO-1.75 - reset-usb-hub wasn't actually driving the RESET# line low.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2715 2715] OLPC XO-1.75 - reset-usb-hub wasn't actually driving the RESET# line low.
Line 45: Line 45:
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2706 2706] OLPC XO-1.75 - synchronise EC flags flash page when reprogramming manufacturing tags <trac>11493</trac> (thanks to Mitch for initial design on 22nd August), and fix flash-ec which was failing if any flags were set.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2706 2706] OLPC XO-1.75 - synchronise EC flags flash page when reprogramming manufacturing tags <trac>11493</trac> (thanks to Mitch for initial design on 22nd August), and fix flash-ec which was failing if any flags were set.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2705 2705] OLPC - avoid a gap in the reflash progress display, and show one more dot after the verify pass.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2705 2705] OLPC - avoid a gap in the reflash progress display, and show one more dot after the verify pass.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2703 2703] OLPC XO-1 XO-1.5 XO-1.75 - show progress bar during automatic OpenFirmware reflashing, two dots per flash block, show not enough power icon ... on XO-1 only the dots are shown because of a smaller icon collection. Tested on XO-1, XO-1.5, XO-1.75.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2703 2703] OLPC XO-1 XO-1.5 XO-1.75 - show progress bar during automatic Open Firmware reflashing, two dots per flash block, show not enough power icon ... on XO-1 only the dots are shown because of a smaller icon collection. Tested on XO-1, XO-1.5, XO-1.75.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2702 2702] OLPC XO-1.75 - automatic EC reflash, use chip icon, show progress bar, show battery icon with sad face if not enough power
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2702 2702] OLPC XO-1.75 - automatic EC reflash, use chip icon, show progress bar, show battery icon with sad face if not enough power
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2701 2701] OLPC XO-1.75 - prevent keyboard interrupt during flash or flash-ec, <trac>11488</trac>
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2701 2701] OLPC XO-1.75 - prevent keyboard interrupt during flash or flash-ec, <trac>11488</trac>

Latest revision as of 01:30, 7 October 2012

  This page is monitored by the OLPC team.

OLPC Firmware Release q4c06

Works on XO-1.75 B1 and C1 only. Do not use on A2 or A3.

This is a test candidate for the C2 build:

  • a change to the architecture device-tree tag,
  • during automatic Open Firmware reflash, show progress bar,
  • during automatic EC reflash, prevent keyboard interrupt, show progress bar,
  • show battery icon with sad face if not enough power sources present for automatic reflash,
  • add support for AP and CP manufacturing tags, add-tag AP.
Download q4c06.rom
Build date time 2011-11-29 23:54:33
Source revision 2717
EC version 0.3.05
CForth version 89de5064
Wireless firmware version Libertas thinfirm 9.0.7.p2

Changes since q4c05

Open Firmware

  • 2715 OLPC XO-1.75 - reset-usb-hub wasn't actually driving the RESET# line low.
  • 2714 USB UHCI - begin-intr-in stack balance was wrong if already started
  • 2710 Manufacturing test infrastructure - fixed a stack order bug in the automatic layout code.
  • 2709 Added USB mouse class driver and included it in most active builds.
  • 2706 OLPC XO-1.75 - synchronise EC flags flash page when reprogramming manufacturing tags <trac>11493</trac> (thanks to Mitch for initial design on 22nd August), and fix flash-ec which was failing if any flags were set.
  • 2705 OLPC - avoid a gap in the reflash progress display, and show one more dot after the verify pass.
  • 2703 OLPC XO-1 XO-1.5 XO-1.75 - show progress bar during automatic Open Firmware reflashing, two dots per flash block, show not enough power icon ... on XO-1 only the dots are shown because of a smaller icon collection. Tested on XO-1, XO-1.5, XO-1.75.
  • 2702 OLPC XO-1.75 - automatic EC reflash, use chip icon, show progress bar, show battery icon with sad face if not enough power
  • 2701 OLPC XO-1.75 - prevent keyboard interrupt during flash or flash-ec, <trac>11488</trac>
  • 2700 OLPC XO-1.75 - change architecture device-tree tag.
  • 2699 fix hang on " u:f" r/w create-file caused by stack imbalance after handling UFS partition letter.

CForth

  • none

EC

  • none

WLAN

  • none


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  q4c06 ...   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 mark) game button held down. You will be asked to Release the game keys to continue. Release the ✓ (check mark) game button and watch carefully. For a short time the startup banner will be displayed, like this:

 OLPC ..., ... memory installed, ..., S/N SHF7250024D
 OpenFirmware  q4c06 ...   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:\q4c06.rom
  • if the downloaded file is on an external SD card:
 flash sd:\boot\q4c06.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/q4c06/q4c06.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\q4c06.rom
  • if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q4c06.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\q4c06\q4c06.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.