OLPC Firmware q2f09
OLPC Firmware Release q2f09
Works on XO-1 systems.
- fix NANDblaster receive bug, <trac>11696</trac>,
- fix black-boxes regression in autorun-mfg-tests graphical test menu, <trac>11688</trac>,
- common NANDblaster source update, <trac>11696</trac>,
- consistent help across platforms,
- full screen debugger,
- decompiler syntax highlighting,
| Download | q2f09.rom |
| Build date time | 2012-03-03 20:42:57 |
| Source revision | 2935. |
| EC version | 1.2.1 |
| Wireless firmware version | 5.110.22.p23 |
Changes
- 2933 start.s removed in favor of start.S
- 2930 GUI - Fixed bug introduced by recent mouse/touchscreen/pointer revamp. menu was broken on systems without a touchscreen.
- 2926 Kernel - removed obsolete and unused definition c" to fix compilation warning about compile-pstring .
- 2923 Fix nandblaster build errors introduced by recent client library declaration changes.
- 2922 Client library - fixed residual problem from recent cleanup.
- 2920 Graphical menu - rearranged the mouse and touchscreen handling code so the multiplexing is done in one place, using the name "pointer" to mean the collection of positional input devices. That should make it easier to support additional devices. Ideally, there would be a multiplexor node to which devices could be attached, akin to the input and output mux nodes, but that improvement is left to a later date.
- 2919 Client library - big checkin to (a) Support cell-sized stdin and stdout properties and (b) Clean up data typing to satisfy XCode compilers
- 2917 Core - Converted config-int, chosen-int, chosen-value, and chosen-variable to cell size intead of explicit 32-bit. Those values often contain pointers that need the full width of the processors native cell size, and represent dynamically-determined information that does not need portability across processor types. Property values in the device description portion of the device tree remain as explicit 32-bit chunks. The OFW client library code needs to be changed accordingly, but has not yet been changed.
- 2914 Debugger - improved the "down" command so it will skip past the method call machinery to find the callee that the user cares about. You can now use 'd' on $call-method, $call-parent, etc.
- 2913 Debugger - improved the "up" command so it will skip past the method call machinery to find the caller that the user cares about.
- 2912 Decompiler - fixed oops in last checkin (indentation for "loop")
- 2911 rstrace - set the default value for boring? so the debugger works before OFW is loaded.
- 2910 Debugger - factored (trace so it's not so crazy long, and cleaned up a few minor glitches.
- 2909 Decompiler - fixed the indentation logic (it sometimes messed up on repeated conditionals or loops) and added h#/d# number prefixes.
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 q2f09 ... 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 q2f09 ... 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
- download the firmware from http://dev.laptop.org/pub/firmware/q2f09/q2f09.rom and save it to a USB drive or SD card,
- shutdown the laptop,
- 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:\q2f09.rom
- if the downloaded file is on an external SD card:
flash sd:\boot\q2f09.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,
- start the Terminal Activity and type:
su cd /versions/boot/current/boot/ wget http://dev.laptop.org/pub/firmware/q2f09/q2f09.rom
- shutdown the laptop,
- 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\q2f09.rom
- if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q2f09.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.
- shutdown the laptop,
- 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\q2f09\q2f09.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.