OLPC Firmware Q2A53: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
=== Installation Caveats === |
=== Installation Caveats === |
||
* If you use olpcflash to write this image, you must use the --brick option. |
|||
* After you reflash, you must power cycle by physically removing power from the system. A warm-start or button-induced restart is not sufficient. Please remove both the battery pack and wall adapter for 10 seconds. |
* After you reflash, you must power cycle by physically removing power from the system. A warm-start or button-induced restart is not sufficient. Please remove both the battery pack and wall adapter for 10 seconds. |
||
''ATest users only:'' If you use olpcflash to write this image, you must use the --brick option.<br> Example: <code>olpcflash --brick -w image.rom</code><br> This will update your EC code. |
|||
BTest-1 users should '''NOT''' use olpcflash to write new firmware images. Doing so will erase the manufacturing data that was added at the factory. |
|||
=== Known issues === |
=== Known issues === |
||
Revision as of 22:25, 1 December 2006
This page is monitored by the OLPC team.
OLPC Firmware Production Release Q2A53 - 2006-12-1
This is the update release for the B-test build.
MD5 a1af762465a6b2a0a8939d51d6e31f9e olpc-Q2A53.rom
Changes since Q2A52
- OFW: Some nand write fixes for spurious errrors
- OFW: Fix a build error on ATest due nand fixes.
Installation Caveats
- After you reflash, you must power cycle by physically removing power from the system. A warm-start or button-induced restart is not sufficient. Please remove both the battery pack and wall adapter for 10 seconds.
ATest users only: If you use olpcflash to write this image, you must use the --brick option.
Example: olpcflash --brick -w image.rom
This will update your EC code.
BTest-1 users should NOT use olpcflash to write new firmware images. Doing so will erase the manufacturing data that was added at the factory.
Known issues
- Auto-repeat is slow on some USB keyboards
- NVRAM storage for configuration variables is not yet implemented.
- JFFS2 does not pay attention to the bad block table.
- JFFS2 does not handle ECC
- The boot menu is incomplete
- Dirctory symlinks have a problem.