OLPC Firmware q3a65: Difference between revisions
(Proper name for Open Firmware) |
|||
Line 56: | Line 56: | ||
== Changes since q3a64 == |
== Changes since q3a64 == |
||
=== |
=== Open Firmware [http://openbios.org/viewvc/?root=OpenFirmware svn 2194] Built 2011-04-29 21:08:00 === |
||
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2193 svn 2193] OLPC XO-1.5 - fs-update, remove erase support because it broke NANDblaster. The microSD card is used to hold the received .zd file, and erasing the card erases the file, causing fs-update to see a zero filled file beyond a certain point. This revision tested with sparse .zd files on NANDblaster and fs-update from USB. |
* [http://tracker.coreboot.org/trac/openfirmware/changeset/2193 svn 2193] OLPC XO-1.5 - fs-update, remove erase support because it broke NANDblaster. The microSD card is used to hold the received .zd file, and erasing the card erases the file, causing fs-update to see a zero filled file beyond a certain point. This revision tested with sparse .zd files on NANDblaster and fs-update from USB. |
Latest revision as of 00:18, 7 October 2012
OLPC Firmware Release q3a65
Works on XO-1.5 A1, A2, B1, B2, B3, C1, C2 and C3 systems, but does not work on any XO-1 machines.
Download: q3a65.rom
Change summary:
- add support for sparse .zd files, decreasing fs-update time, <trac>10844</trac>,
- disable fs-update erase step, <trac>10825</trac>,
- revised help display,
fs-update sparse .zd files
Sparse .zd files do not include unused filesystem blocks. As a result, installation time for 10.1.3 falls from 14 minutes to 7 minutes ... if the .zd file is processed. Patches to olpc-os-builder are available for future builds.
(There is now an installation time advantage to smaller operating system builds).
fs-update disable erase
In Q3A64 and earlier, fs-update used to erase one 256th of the microSD card before starting to write to the card. This was removed, because it was unnecessary, because some cards did not behave well, and if extended to the whole card it broke NANDblaster.
help
A revised help output:
UPDATES: fs-update u:\os1.zd4 Rewrite the OS on internal SD from USB drive flash u:\q3a64.rom Rewrite the firmware from USB drive flash ext:\q3a64.rom Rewrite the firmware from external SD file DIRECTORY LISTING: dir u:\ List USB drive root directory dir u:\boot\ List USB drive /boot directory dir int:\boot\*.zip List .zip files in internal SD /boot directory BOOTING: boot Start the OS from list of default locations printenv boot-device Show the list of default locations used by boot boot u:\test.fth Start the OS from a specific location CONFIGURATION VARIABLES FOR BOOTING: boot-device Kernel or boot script paths. Example: ext:\boot\olpc.fth boot-file Default kernel command line. Example: console=ttyS0,115200 ramdisk Initial RAMDISK path. Example: int:\boot\initrd.img MANAGING CONFIGURATION VARIABLES: printenv [ <name> ] Show configuration variables setenv <name> <value> Set configuration variable editenv <name> Edit configuration variable DIAGNOSTICS: test <device-name> Test device. Example: test mouse test-all Test all devices that have test routines menu Graphical interface to selftests More information: http://wiki.laptop.org/go/OFW_FAQ
Changes since q3a64
Open Firmware svn 2194 Built 2011-04-29 21:08:00
- svn 2193 OLPC XO-1.5 - fs-update, remove erase support because it broke NANDblaster. The microSD card is used to hold the received .zd file, and erasing the card erases the file, causing fs-update to see a zero filled file beyond a certain point. This revision tested with sparse .zd files on NANDblaster and fs-update from USB.
- svn 2192 OLPC XO-1.5 - fs-update, add support for sparse .zd files, undo -r2186 meaning of zblocks: parameter, split card erasure to avoid card lockup, and show progress during erasure. SDHCI - erase blocks, wait for card to leave programming state, and ignore spurious data timeout.
- svn 2191 OLPC - fs-update, -r2190, make radix explicit.
- svn 2190 OLPC - fs-update was not erasing the whole part, because the image block count, typically a number of 131072-byte blocks, was used as a 512-byte block count in invokation of erase-blocks.
- svn 2189 OLPC XO-1.5 - "help" output review; avoid mentioning q2c series, use .zd4 file in example, change USB key to USB drive, vertically align comments, drop "boot u:\boot\vmlinuz" as it is unlikely to be used, explain "printenv boot-device" as a new line, expand configuration variable meanings, change "initrd.imz" to "initrd.img", indent URL of OFW_FAQ.
- svn 2188 stack effect comment for $case example of use.
EC code is version 2.1.0
- no change
WLAN firmware is Libertas thinfirm 9.0.7.p2
- 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 q3a65 ... 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 q3a65 ... 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
- download the firmware from http://dev.laptop.org/pub/firmware/q3a65/q3a65.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:\q3a65.rom
- if the downloaded file is on an external SD card:
flash sd:\boot\q3a65.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/q3a65/q3a65.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\q3a65.rom
- if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q3a65.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\q3a65\q3a65.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.