OLPC Firmware q4b11

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

OLPC Firmware Release q4b11

For B1 and later boards ONLY! Do not install on A2 boards. Use on A3 boards requires a hardware mod to connect the touchpad and keyboard to the SP instead of the EC - see XO_1.75_A3_ECOs#Keyboard_Touchpad_Routing

This is a test candidate for the C1 build. Suspend/resume is stable and the selftest suite works after a resume.

Download q4b11.rom
Build date time 2011-10-05 16:45:27
Source revision 2584
EC version 0.3.00
CForth version 95375c42
Wireless firmware version Libertas thinfirm 9.0.7.p2

Changes since q4b10

Open Firmware

  • svn 2583 - trac #11300 - WLAN now works after suspend/resume
  • svn 2581 - trac #11299 - Trackpad (mouse) now work after suspend/resume
  • svn 2579 - trac #11292 - touchscreen absence - the usual case - is not reported as a selftest error.
  • svn 2578 - trac #11298 - reinit USB hardware as necessary after suspend/resume.
  • svn 2576 - trac #11124 - added fuse display commands .fuses and .fuses-all .
  • svn 2575 - enable-security now works for XO-1.75
  • svn 2574 - trac #11292 - OFW no longer supports routing the keyboard and mouse through the EC.
  • svn 2573 - trac #11095 - implemented lid switch power-off.
  • svn 2572 - WLAN and LED selftest no longer have unnecessary console output
  • svn 2567 - Added suspend/resume test to "test /memory"
  • svn 2556 - trac #11236 - Added YCrCb (YUV) support to the XO-1.75 camera test
  • svn 2555 - fix RTC test for units that do not hold their date, by checking only the year, #11229
  • svn 2554 - change LED testing order, flash the OLS LED flash slower for better discrimination
  • svn 2553 - trac #11230 - WLAN selftest - added association test that runs if there is an OLPCOFW access point.
  • svn 2551 - Changed disable-irq and enable-irq to affect only the routing for IRQ1
  • svn 2550 - Added gpio-clr-mask as a complement to gpio-set-mask, and fixed gpio-set-mask not to clobber other bits in the mask.
  • svn 2549 - add thermal watchdog disable used in testing
  • svn 2548 - trac #11229 - Display date and time in RTC selftest. Also check date for reasonablness - later than the date when this test was added.
  • svn 2547 - adopt EC 0.3.00
  • svn 2546 - trac #11279 - fix autorun-mfg-tests
  • svn 2544 - suspend/resume test4 improvements - slightly longer cycle time to ensure at least one whole clock tick, display power info.
  • svn 2542 - Changed audio driver to use audio PLL instead of I2SCLOCK at Marvell's recommendation.
  • svn 2541 - Eliminated noise at the end of the jingle when OFW boots Linux
  • svn 2540 - retry DCON init 5 times for more reliable resume
  • svn 2539 - suspend/resume is now stable
  • svn 2537 - DNS - use source port 53 which works better with dnscache than the previously-used port 1022.
  • svn 2534 - Added EC commands ec-rst-pwr, ec-min-pwr, ec-max-pwr , used for power measurement during suspend.
  • svn 2533 - WiFi - 13-byte keys now work.

CForth

  • better keyboard handling when keys are depressed at startup
  • MFPR pin setting changes for better behavior when asleep

EC

See EC_1.75_Firmware#Ver:_0.3.00

  • Fully implement suspend power blinking
  • rename *_SLEEP_IND functions to *_VCXO_EN, and invert level
  • Rework SDI host (ACK state) handling
  • Enable touchpad by default for < 0x1B1
  • Introduce workaround for ljmp bug
  • Fully init the gpwu on every reboot

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