Upgrading the firmware: Difference between revisions
Jump to navigation
Jump to search
(To avoid rewriting your OS, just use manual upgrade below. +typos, broken links) |
(Redirected page to Upgrading firmware) |
||
| (30 intermediate revisions by 18 users not shown) | |||
| Line 1: | Line 1: | ||
#REDIRECT [[Upgrading firmware]] |
|||
How you update the firmware depends on what method you can use and what board type you have. |
|||
== Finding your current firmware version == |
|||
If you are curious, you can find out your current version. The version of the firmware is displayed by OpenFirmware when the laptop boots and prior to loading the kernel. The version number is a series of 5 digits after the text |
|||
<code>OpenFirmware CL1</code> |
|||
An example would be 'Q2B74'. The last 3 digits of this string (B74) are the most important. The 'B' stands for BTest and indicates the target board for the firmware. We try hard to keep backwards compability so it will (with a few exceptions) run on an ATest board. |
|||
The 2 digits are the revision number of that firmware. Higher numbers equal more recent firmware versions. |
|||
== BTest Laptop Upgrades == |
|||
This is the procedure to upgrade B1 and B2 laptops. The ATest procedure is [[Upgrading_the_firmware#ATest|here]] |
|||
=== Via Auto Updater === |
|||
If your current firmware version is earlier than the firmware in the [[Autoreinstallation_image]] then you can just use that procedure for the update. Note: that this procedure will also upgrade the image in your nand flash, which contains the entire Linux operating system and all your user and system files. '''This means it will ERASE what is in your nand and re-write it.''' You will lose any data you have stored on the filesystem unless you '''first''' back it up. If you do not want your nand erased, then please do the manual upgrade (below) instead. |
|||
=== Manual upgrade === |
|||
Before you manually upgrade your firmware you should first ensure that your battery is charged and that you have good AC power. If the firmware upgrade is interrupted by a power loss the result will most likely be a laptop that will not power up anymore (a "brick"). The only recovery method from a failed flash requires disassembling the laptop and using special equipment to reprogram the hardware. |
|||
* Upgrade steps |
|||
# Download the latest firmware image from the [[Firmware]] page. See above for decoding the version numbers. You can also just pick the firmware released on the latest date. |
|||
# Copy this image to a USB disk, "key" or "stick". The filesystem can be ext2, ext3, or FAT. If you choose FAT, then you will need to rename the .rom file to adhere to FAT 8.3 filename conventions. OpenFirmware does not support long filenames on FAT. |
|||
# Insert this key into a laptop that is turned off. |
|||
# Plug the laptop into AC power, and make sure it has a good battery |
|||
# Turn on the laptop |
|||
# When you see the prompt "Type any key to interrupt automatic startup", press the enter key a few times. |
|||
# You should now be at a prompt that says 'ok' |
|||
# At the 'ok' prompt type <code>flash disk:\<path_to_rom> </code> where <code><path_to_rom></code> is the path to the firmware rom file. An example would be <code>flash disk:\olpc-Q2B74.rom</code> |
|||
# When the upgrade is complete, the laptop will power off. |
|||
== ATest Upgrade == |
|||
Check with a member of the OLPC firmware or hardware staff if you have an ATest board. |
|||
[[Category:Developers]] |
|||
[[Category:Firmware]] |
|||
[[Category:HowTo]] |
|||
Latest revision as of 06:20, 30 August 2013
Redirect to: