OLPC Firmware q2d07: Difference between revisions
(→OLPC Firmware Release q2d07 - 2007-12-07: Add link to detailed procedures for getting a developer key.) |
|||
| Line 5: | Line 5: | ||
<font color=red>If your system currently has Q2D06 and the screen lights up after power on, there is no urgency to upgrade to Q2D07.</font> You can wait and let the firmware upgrade happen automatically when a later OS build includes Q2D07. The critical bug that is mentioned above is only triggered if the Real Time Clock device loses its dedicated battery power. That is unlikely to occur in the field, unless you explicitly disassemble the machine and remove the "coin cell" battery that provides backup power for the Real Time Clock chip. |
<font color=red>If your system currently has Q2D06 and the screen lights up after power on, there is no urgency to upgrade to Q2D07.</font> You can wait and let the firmware upgrade happen automatically when a later OS build includes Q2D07. The critical bug that is mentioned above is only triggered if the Real Time Clock device loses its dedicated battery power. That is unlikely to occur in the field, unless you explicitly disassemble the machine and remove the "coin cell" battery that provides backup power for the Real Time Clock chip. |
||
<font color=red>If your system won't boot and it says "The Clock is not set properly. Invalid system date. Stopping." then powers off, you are being bit by this bug.</font> In that case, you need a "developer key" from OLPC. See [[Activation and Developer Keys#Getting a Developer Key if the Machine Won't Boot]]. |
<font color=red>If your system won't boot and it says "The Clock is not set properly. Invalid system date. Stopping." then powers off, you are being bit by this bug.</font> In that case, you need a "developer key" from OLPC. See [[Activation and Developer Keys#Getting a Developer Key if the Machine Won't Boot]]. On the other hand, it is reasonably safe to upgrade to Q2D07, so if you want to do so, there is no compelling reason not to proceed with the upgrade. |
||
On the other hand, it is reasonably safe to upgrade to Q2D07, so if you want to do so, there is no compelling reason not to proceed with the upgrade. |
|||
---- |
|||
==Installation== |
==Installation== |
||
Revision as of 05:10, 28 December 2007
OLPC Firmware Release q2d07 - 2007-12-07
This firmware is for the Ship.2 software release set, fixing a critical bug that was found in q2d06. The bug caused the system not to start at all on systems where the Real Time Clock in not initialized - i.e. in the manufacturing environment. It is supported on B3 and later systems. In addition, it has been tested to be safe (does not brick) on B1, B2-1, and preB3. Do not use it on pre-B1 boards - it will brick them because of the EC microcode. It does not work on Atest because support for Atest has been eliminated from the EC microcode.
If your system currently has Q2D06 and the screen lights up after power on, there is no urgency to upgrade to Q2D07. You can wait and let the firmware upgrade happen automatically when a later OS build includes Q2D07. The critical bug that is mentioned above is only triggered if the Real Time Clock device loses its dedicated battery power. That is unlikely to occur in the field, unless you explicitly disassemble the machine and remove the "coin cell" battery that provides backup power for the Real Time Clock chip.
If your system won't boot and it says "The Clock is not set properly. Invalid system date. Stopping." then powers off, you are being bit by this bug. In that case, you need a "developer key" from OLPC. See Activation and Developer Keys#Getting a Developer Key if the Machine Won't Boot. On the other hand, it is reasonably safe to upgrade to Q2D07, so if you want to do so, there is no compelling reason not to proceed with the upgrade.
Installation
When installing new firmware, you need a well-charged battery and the AC adapter must be plugged in. The firmware update code will not proceed otherwise.
Secure Machines
Download: Signed q2d07 bootfw.zip
Put the bootfw.zip file on the XO NAND FLASH filesystem in /versions/boot/current/boot/bootfw.zip, or on a USB key as /boot/bootfw.zip. Do not unpack the zip file - it must be present on the media in .zip form. Then power cycle the system. OFW should reload the firmware from the bootfw.zip automatically.
Unsecure Machines
Download: q2d07.rom
Put the q2d07.rom file on the XO NAND FLASH filesystem in /versions/boot/current/boot/q2d07.rom, or on a USB key as /boot/q2d07.rom . Power cycle the system and get to the ok prompt. Then type either:
ok flash u:\boot\q2d07.rom ( if the file is on a USB key )
or
ok flash n:\boot\q2d07.rom ( if the file is on the NAND FLASH filesystem )
See Cheat codes for information about how game buttons control startup options.
Changes since OLPC Firmware q2d06
OpenFirmware is svn 741, plus cherry-picked 749 and 750
- OLPC Trac 5391 - Fixed a problem that bricks systems that have 0 (an invalid value) in the RTC month register.
WLAN firmware is 5.110.20.p42.bin
<Same as in Q2D06>
EC code is test4e
<same as in q2d06>