OLPC Firmware q3b14
Contents
OLPC Firmware Release q3b14
Works on XO-1.5 C1-C8 systems, but does not work on any XO-1 machines.
| Download | q3b14.rom |
| Build date time | 2011-07-23 00:00:42 |
| Source revision | 2395 |
| EC version | 2.2.7 |
| Wireless firmware version | Libertas thinfirm 9.0.7.p2 |
Changes
Open Firmware
- svn 2394 OLPC XO-1.5 - new EC firmware from Richard #11021
- svn 2388 USB hub - added 100 ms delay between detecting insertion and probing the device in hopes of keeping devices like scanners happy.
- svn 2380 Added some commentary about standard VESA modes to c32vesa.fth
- svn 2379 OLPC XO-1.5 - better value for turning off PCIe clock generator outputs.
- svn 2378 OLPC XO-1.5 - better value for turning off PCIe clock generator outputs.
- svn 2374 OLPC XO-1.75 (and 1.5) - Fixed the vector test instructions display to use the right colors when the display is in RGB565 mode, and modified the XO-1.5 and XO-1.75 drivers to support the necessary color conversion function.
- svn 2360 OLPC manufacturing tests - fixed a stack bug in an error path in smt.fth; perhaps that error path had never been executed.
- svn 2359 OLPC manufacturing tests - fixed mfg-test-dev to correctly pass in device-specifier arguments, thus fixing a bug that caused "test int:0" to fail when the SD card did not have a partition table.
- svn 2357 OLPC NANDblaster build script - Added "+ssh" to git URL for the "test" target, so changes can be pushed.
- svn 2356 Use latest NANDblaster source for 1.5 and 1.75 to pick up the move of memcmp() to the library.
- svn 2353 memcmp version from multicast-nand moved into library, Mitch identified it as better than the one that was there.
- svn 2342 Guard the attribute specification with #ifndef __llvm__ cos it slays LLVM-based compilers. Should be a no-op for everyone else in the universe. (Borland?)
- svn 2341 Can't suppress warnings in hdaudio/test.fth because it's loaded from FCode in some builds.
- svn 2340 Fixed bug in ofpong introduced by recent commit.
- svn 2331 GUI - interact with mouse in stream mode instead of remote-polling mode to decrease command traffic over the PS/2 bus.
- svn 2320 This goes with the last checkin - added locking around kbd-reset so it will work when the alarm handler is enabled.
- svn 2319 OLPC - added touchpad and keyboard tests to /ap-sp (SP-mediated) keyboard and touchpad drivers. Also auto-created keyboard and mouse aliases depending on which interface has an attached keyboard on XO-1.75.
EC
- fix for <trac>11021</trac>
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 q3b14 ... 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 q3b14 ... 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/q3b14/q3b14.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:\q3b14.rom
- if the downloaded file is on an external SD card:
flash sd:\boot\q3b14.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/q3b14/q3b14.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\q3b14.rom
- if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q3b14.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\q3b14\q3b14.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.
