OLPC Firmware q3a34: Difference between revisions
Edmcnierney (talk | contribs) No edit summary |
(Proper name for Open Firmware) |
||
Line 10: | Line 10: | ||
== Changes since q3a30 == |
== Changes since q3a30 == |
||
=== |
=== Open Firmware is [http://openbios.org/viewvc/?root=OpenFirmware svn 1763] === |
||
* OLPC trac 10053 - XO-1.5 - Flaky audio selftest. Fixed buffer overflow with debugging routine for plotting impulse response. Doesn't affect normal testing. |
* OLPC trac 10053 - XO-1.5 - Flaky audio selftest. Fixed buffer overflow with debugging routine for plotting impulse response. Doesn't affect normal testing. |
Latest revision as of 23:46, 6 October 2012
OLPC Firmware Release q3a34
Works on XO-1.5 A1, A2, B1, B2, B3, and C1 systems, but does not work on any XO-1 machines.
Download: q3a34.rom
Changes since q3a30
Open Firmware is svn 1763
- OLPC trac 10053 - XO-1.5 - Flaky audio selftest. Fixed buffer overflow with debugging routine for plotting impulse response. Doesn't affect normal testing.
- OLPC trac 10053 - XO-1.5 - Flaky audio selftest. Use hardware synchronization between the output and input audio streams to make the test insensitive to CPU speed variations that can be caused by thermal throttling or interrupt vagaries.
- OLPC trac 10047 - XO-1.5 - Conexant chip needs ID in node 1. This revision also fixes a problem where the CODEC init table was not being processed properly, due to a table address relocation error.
- OLPC trac 10022 - Power wait must happen before turning off the EC, otherwise you can't read the AC and battery state.
- OLPC trac 10043 - Fix USB keyboard operation for XO-1.
- OLPC trac 10022 - XO 1.0 Keyjector - power state check before bootfw2.zip
- OLPC trac 10029 - but XO-1 firmware with real keys, not test keys.
- OLPC trac 10026 - menu test leaves current device set to last-executed test.
- OLPC trac 10025 - sound-recording plays back in doubletime.
- OLPC trac 10028 - OFW reprompts on glob copy.
- OLPC XO-1.5 - testinstructions.fth - tweaked the scanner drawing to make the tangents match better.
- OLPC XO-1.5 - renamed drawboardtop.fth to testinstructions.fth
- OLPC XO-1.5 - graphical instructions for factory selftest steps.
- OLPC trac 10024 - restored progress icons for internal NAND/SD and external SD storage (XO-1.5 build)
- OLPC trac 10024 - restored progress icons for internal NAND/SD and external SD storage.
- Memory selftest - Changed suspend/resume sub-test to do only one pass.
- OLPC XO-1.5 - Graphical instructions for manufacturing tests.
- OLPC trac 10024 - Improved SD card detection procedure so it works well for both the CaFe SDHCI controller and the Via SDHCI controller.
- OLPC XO-1.0 build - added some definitions to support new features added to the XO-1.5 build.
- USB mass storage driver - fixed a potential coherence problem that could result from having multiple deblocker instances open on the same device.
- SDHCI - added support for erase-blocks and predeclaring the write size, and fixed a potential coherence problem with duplicate deblocker instances.
- OLPC trac 9972 - ext2 filesystem package - fixed a bug in the calculation of backup group descriptor block numbers when the block size is not 1K.
- disk-label package - support unpartitioned disk layout where an ext2/3 filesystem occupies the entire device.
- sprintf - fixed egregious bug in the handling of backslash escapes.
- OLPC XO-1.0 - fixed regression in wireless open routine - new USB set-config scheme was improperly applied to the wireless driver.
- OLPC XO-1.0 - fixed regression in wireless firmware download result checking.
- Added adhoc-start to Libertas wireless driver.
- OLPC XO 1.5 - Removed unused icons from dropin list.
- OLPC XO 1.5 - Fixed bug in enable-serial - wrong number base caused wrong value to be written to wrong register.
- Removed unused definitions in OLPC GUI - for obsolete boot progress reporting mechanism.
- Last commit was to fix trac 10017, not 10009.
- OLPC trac 10009 - Fixed secure fs-update regression.
EC code is version 1.9.24
- Fix lost ps2 bytes on suspend/resume
- Large ammount of kbc/mouse flow debug
- trac 9675. Fix KBC hang from no cmd response.
- Add minimum off time on soft reboots
WLAN firmware is 9.70.7.p0
<same as in q3a14>
Which Firmware Do You Have?
If your machine is not in secure mode, the firmware version is displayed in the startup banner, as in:
OLPC XO 1.5, 1 GiB memory installed, S/N SHF7250024D OpenFirmware CL1 Q3A04 Q3A ^^^^^
If your machine is in secure mode, you can go to the Terminal activity and type
cat /ofw/openprom/model
If your machine is in secure mode but the OS will not start, just go ahead and try to upgrade the firmware anyway. The procedure is safe and will not do anything if you already have up-to-date firmware.
You can see the firmware version in secure mode by powering up with the "check" game button held down.
You can also go to the main Sugar screen, click on the little man and select "about this XO"
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/q3a34/q3a34.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:\q3a34.rom
- if the downloaded file is on an external SD card:
flash sd:\boot\q3a34.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/q3a34/q3a34.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\q3a34.rom
- if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q3a34.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\q3a34\q3a34.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.