Flashrom: Difference between revisions
(Change ROM chip to flash chip everywhere for less user confusion.) |
(→Installation: FreeBSD install.) |
||
Line 2,162: | Line 2,162: | ||
'''Manual Installation''' | '''Manual Installation''' | ||
$ svn co svn://coreboot.org/flashrom/trunk flashrom | $ '''svn co svn://coreboot.org/flashrom/trunk flashrom''' | ||
$ cd flashrom | $ '''cd flashrom''' | ||
$ make | $ '''make''' | ||
$ sudo make install | $ '''sudo make install''' | ||
'''Debian''' | '''Debian''' | ||
$ sudo aptitude install flashrom | $ '''sudo aptitude install flashrom''' | ||
'''Fedora''' | '''Fedora''' | ||
$ sudo yum install flashrom | $ '''sudo yum install flashrom''' | ||
'''Gentoo''' | '''Gentoo''' | ||
$ emerge flashrom | $ '''emerge flashrom''' | ||
'''Mandriva''' | '''Mandriva''' | ||
$ urpmi flashrom | $ '''urpmi flashrom''' | ||
'''openSUSE''' | '''openSUSE''' | ||
$ yast -i coreboot-utils | $ '''yast -i coreboot-utils''' | ||
For distributions older than openSUSE Factory (11.0) you find "backports" in the [http://packages.opensuse-community.org/index.jsp?searchTerm=coreboot-utils openSUSE Build Service]. | For distributions older than openSUSE Factory (11.0) you find "backports" in the [http://packages.opensuse-community.org/index.jsp?searchTerm=coreboot-utils openSUSE Build Service]. | ||
Line 2,192: | Line 2,192: | ||
Installation from source: | Installation from source: | ||
$ Emerge-Pkg flashrom | $ '''Emerge-Pkg flashrom''' | ||
Installation of binaries: | Installation of binaries: | ||
$ mine -i flashrom-0.9.0.tar.bz2 | $ '''mine -i flashrom-0.9.0.tar.bz2''' | ||
'''FreeBSD''' | |||
$ '''cd /usr/ports/sysutils/flashrom && make install clean''' | |||
'''Windows''' | '''Windows''' | ||
There is a Windows port of the flashrom utility. Download the latest version | There is a Windows port of the flashrom utility. Download the latest version: [http://google-summer-of-code-2007-coresystems.googlecode.com/files/DarmawanMappatutu_Salihun.tar.gz DarmawanMappatutu_Salihun.tar.gz] | ||
= Usage = | = Usage = |
Revision as of 18:21, 22 May 2009
flashrom is a utility for identifying, reading, writing, verifying and erasing flash chips. It's often used to flash BIOS/EFI/coreboot/firmware images.
Highlights of flashrom include:
- Supports parallel, LPC, FWH and SPI flash interfaces.
- Supports more than 150 flash chip families and half a dozen variants of each family.
- Flash chip package agnostic. DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, TSOP40 and more have all been verified to work.
- Supports more than 75 different chipsets, some with multiple flash controllers.
- Features special mainboard enabling code for dozens of nonstandard mainboards.
- No physical access needed, root access is sufficient.
- No bootable floppy disk, bootable CD-ROM or other media needed.
- No keyboard or monitor needed. Simply reflash remotely via SSH.
- No instant reboot needed. Reflash your chip in a running system, verify it, be happy. The new firmware will be present next time you boot.
- Crossflashing and hotflashing is possible as long as the flash chips are electrically and logically compatible (same protocol). Great for recovery.
- Scriptability. Reflash a whole pool of identical machines at the same time from the command line. It is recommended to check flashrom output and error codes.
- Speed. flashrom is often much faster than most vendor flash tools.
- Supports Linux, FreeBSD, DragonFly BSD, Solaris, Mac OS X, and other Unix-like OSes.
Supported devices
Supported chips
|
|
|
Supported chipsets
|
|
|
Supported mainboards
In general, it is very likely that flashrom works out of the box even if your mainboard is not listed below.
This is a list of mainboards where we have verified that they either do or do not need any special initialization to make flashrom work (given flashrom supports the respective chipset and flash chip), or that they do not yet work at all. If they do not work, support may or may not be added later.
Mainboards which don't appear in the list may or may not work (we don't know, someone has to give it a try). Please report any further verified mainboards on the mailing list.
Known good (worked out of the box)
|
|
|
Known good (with write-enable code in flashrom)
|
|
Not supported (yet)
|
Board notes
- ASI MB-5BLMP: Used in the IGEL WinNET III thin client.
- MSI MS-7260 (K9N Neo): Interestingly flashrom does not work when the vendor BIOS is booted, but it does work flawlessly when the machine is booted with coreboot.
- ASUS M2A-VM: See http://www.coreboot.org/pipermail/coreboot/2007-September/025281.html.
- BCOM WinNET100: Used in the IGEL-316 thin client.
- ASUS A8V-E SE: See http://www.coreboot.org/pipermail/coreboot/2007-October/026496.html.
Supported laptops/notebooks
In general, flashing laptops is more difficult because
- Laptops often use the flash chip for stuff besides the BIOS.
- Laptops often have special protection stuff which has to be handled by flashrom.
- Laptops often use flash translation circuits which need extra drivers in flashrom.
At this point we recommend to not use flashrom on untested laptops unless you have a means to recover from a flashing that goes wrong (a working backup flash chip and/or good soldering skills).
Known-good
|