OLPC Firmware q4d16: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:


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

* support for 1 GHz processors,
* warn if TS tag is not SHIP,
* show menu after left-rocker automatic tests completed.


{| border="1" cellspacing="0" cellpadding="2" class="wikitable"
{| border="1" cellspacing="0" cellpadding="2" class="wikitable"
Line 13: Line 17:
|-
|-
| Build date time <!-- .built -->
| Build date time <!-- .built -->
| 2012-06-06 20:05:25
|
|-
|-
| Source revision <!-- more rom:sourceurl -->
| Source revision <!-- more rom:sourceurl -->
| [http://tracker.coreboot.org/trac/openfirmware/changeset/3002 3002]
| [http://tracker.coreboot.org/trac/openfirmware/changeset/3003 3003]
|-
|-
| EC version <!-- banner -->
| EC version <!-- banner -->
Line 33: Line 37:
=== OpenFirmware ===
=== OpenFirmware ===


* [http://tracker.coreboot.org/trac/openfirmware/changeset/3000 3000] OLPC XO-1.75 - warn on boot if TS tag is not SHIP, for boards such as spares that do not pass through final testing at factory, #11848
* [http://tracker.coreboot.org/trac/openfirmware/changeset/3000 3000] OLPC XO-1.75 - warn on boot if TS tag is not SHIP, for boards such as spares that do not pass through final testing at factory, <trac>11848</trac>
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2999 2999] OLPC - keep menu active and display results after all tests completed. #11847
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2999 2999] OLPC - keep menu active and display results after all tests completed. <trac>11847</trac>
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2998 2998] OLPC - test menu, automatic tests; maintain an overall failure state and report it at the end, handle any escape request from the hold message, make the quit item the default afterwards, and provide the timed menu again. #11847.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2998 2998] OLPC - test menu, automatic tests; maintain an overall failure state and report it at the end, handle any escape request from the hold message, make the quit item the default afterwards, and provide the timed menu again. <trac>11847</trac>.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2996 2996] FCode tokenizer - removed the macro versions of */ and */mod, which do not work correctly (the intermediate result can overflow). If you need to use these functions in an FCode driver, use um* and um/mod to perform the calculations.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2996 2996] FCode tokenizer - removed the macro versions of */ and */mod, which do not work correctly (the intermediate result can overflow). If you need to use these functions in an FCode driver, use um* and um/mod to perform the calculations.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2995 2995] isin.fth - before svn 2994, the calculation in set-period was using */, which is supposed to use a double-precision intermediate value to avoid overflow. However, */ is not a primitive FCode, so the FCode tokenizer was synthesizing it (incorrectly) using (overflowing) * and /. The correct fix, to retain precision, is to implement "u*/" using (double-precision) um* and um/mod .
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2995 2995] isin.fth - before svn 2994, the calculation in set-period was using */, which is supposed to use a double-precision intermediate value to avoid overflow. However, */ is not a primitive FCode, so the FCode tokenizer was synthesizing it (incorrectly) using (overflowing) * and /. The correct fix, to retain precision, is to implement "u*/" using (double-precision) um* and um/mod .
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2993 2993] OLPC XO-1.75 - Added support for 910 MHz and 1 GHz (actually 988 MHz) operating points.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2993 2993] OLPC XO-1.75 - Added support for 910 MHz and 1 GHz (actually 988 MHz) operating points.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2992 2992] OLPC XO-1.75 - If PLL2 is in use, leave it connected to the CPU cores when suspending.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2992 2992] OLPC XO-1.75 - If PLL2 is in use, leave it connected to the CPU cores when suspending.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2991 2991] OLPC - lid close consistent across models, made into common code, #11095
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2991 2991] OLPC - lid close consistent across models, made into common code, <trac>11095</trac>
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2989 2989] OLPC trac #11902 - ALPS touchpad driver - use mouse emulation mode on initial open so the menu works, switching to ALPS mode only during selftest.
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2989 2989] OLPC <trac>11902</trac> - ALPS touchpad driver - use mouse emulation mode on initial open so the menu works, switching to ALPS mode only during selftest.


=== CForth ===
=== CForth ===

Revision as of 00:12, 7 June 2012

  This page is monitored by the OLPC team.


Pencil.png NOTE: The contents of this page are not set in stone, and are subject to change!

This page is a draft in active flux ...
Please leave suggestions on the talk page.

Pencil.png

OLPC Firmware Release q4d16

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

  • support for 1 GHz processors,
  • warn if TS tag is not SHIP,
  • show menu after left-rocker automatic tests completed.
Download q4d16.rom
Build date time 2012-06-06 20:05:25
Source revision 3003
EC version 0.4.03
CForth version f4db9ccf
Wireless firmware version Libertas thinfirm 9.0.7.p2

Changes

OpenFirmware

  • 3000 OLPC XO-1.75 - warn on boot if TS tag is not SHIP, for boards such as spares that do not pass through final testing at factory, <trac>11848</trac>
  • 2999 OLPC - keep menu active and display results after all tests completed. <trac>11847</trac>
  • 2998 OLPC - test menu, automatic tests; maintain an overall failure state and report it at the end, handle any escape request from the hold message, make the quit item the default afterwards, and provide the timed menu again. <trac>11847</trac>.
  • 2996 FCode tokenizer - removed the macro versions of */ and */mod, which do not work correctly (the intermediate result can overflow). If you need to use these functions in an FCode driver, use um* and um/mod to perform the calculations.
  • 2995 isin.fth - before svn 2994, the calculation in set-period was using */, which is supposed to use a double-precision intermediate value to avoid overflow. However, */ is not a primitive FCode, so the FCode tokenizer was synthesizing it (incorrectly) using (overflowing) * and /. The correct fix, to retain precision, is to implement "u*/" using (double-precision) um* and um/mod .
  • 2993 OLPC XO-1.75 - Added support for 910 MHz and 1 GHz (actually 988 MHz) operating points.
  • 2992 OLPC XO-1.75 - If PLL2 is in use, leave it connected to the CPU cores when suspending.
  • 2991 OLPC - lid close consistent across models, made into common code, <trac>11095</trac>
  • 2989 OLPC <trac>11902</trac> - ALPS touchpad driver - use mouse emulation mode on initial open so the menu works, switching to ALPS mode only during selftest.

CForth

  • support for 1 GHz processors. See the git log for the changes.

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  q4d16 ...   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  q4d16 ...   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:\q4d16.rom
  • if the downloaded file is on an external SD card:
 flash sd:\boot\q4d16.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/q4d16/q4d16.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\q4d16.rom
  • if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q4d16.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\q4d16\q4d16.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.