Difference between revisions of "Flashrom"
(→Supported mainboards: ASUS P2B-D works fine, detect, read, write, and erase tested by me.)
(Update URL for checkout.)
|Line 1,442:||Line 1,442:|
$ svn co svn://coreboot.org/
$ svn co svn://coreboot.org//trunk flashrom
$ cd flashrom
$ cd flashrom
Revision as of 19:08, 26 April 2009
Flashrom is a utility which can be used to detect, read, erase, or write BIOS chips (DIP, PLCC, SPI).
- 1 Supported devices
- 2 Supported chipsets
- 3 Supported mainboards
- 4 Installation
- 5 Usage
- 6 Fully testing flashrom chip/southbridge/mainboard support
- 7 Flashrom Live CD
- 8 ROM chip overview
Note: There are probably some flash ROM chips which are compatible to the ones listed below.
1 This includes the ICH, ICH0, ICH2, ICH2-M, ICH3-S, ICH3-M, ICH4/ICH4-L, ICH4-M, ICH5/ICH5R, ICH6/ICH6R, ICH6-M, ICH7DH, ICH7/ICH7R, ICH7M, ICH7MDH, ICH8/ICH8R, ICH8M-E, ICH8DH, ICH8DO, ICH8M, ICH9DH, ICH9DO, ICH9R, ICH9M-E, ICH9, ICH9M, ICH10DO, ICH10R, ICH10, ICH10D chipsets.
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 southbridge and ROM 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 or add them here directly.
Known-good (but special setup required)
1 Used in the IGEL WinNET III thin client.
2 Might also work for other CLE266 based EPIAs.
3 Interestingly flashrom does not work when the vendor BIOS is booted, but it does work flawlessly when the machine is booted with coreboot.
4 See http://www.coreboot.org/pipermail/coreboot/2007-September/025281.html.
5 Used in the IGEL-316 thin client.
6 See http://www.coreboot.org/pipermail/coreboot/2007-October/026496.html.
Flashrom requires the pciutils and zlib and the respective development packages in order to be built. In addition, the subversion package is required to download it.
In Debian unstable these development packages are called pciutils-dev/libpci-dev, zlib1g-dev, and subversion. Most other distributions call them pciutils-devel, zlib-devel, and subversion.
$ svn co svn://coreboot.org/flashrom/trunk flashrom $ cd flashrom $ make $ sudo make install
$ sudo aptitude install flashrom
$ sudo yum install flashrom
$ urpmi flashrom
$ yast -i coreboot-utils
For distributions older than openSUSE Factory (11.0) you find "backports" in the openSUSE Build Service.
There is a Windows port of the flashrom utility. Download the latest version at http://google-summer-of-code-2007-coresystems.googlecode.com/files/DarmawanMappatutu_Salihun.tar.gz
Detect whether flashrom knows about your chipset/mainboard/BIOS chip:
Read the current BIOS image into a file:
$ flashrom -r backup.bin
Depening on the chip driver, you may have to erase the chip before writing:
$ flashrom -E
Write a BIOS image (proprietary or coreboot) on the ROM chip:
$ flashrom -wv newbios.bin
For more documentation please see the flashrom README or the man page.
Fully testing flashrom chip/southbridge/mainboard support
See this page for instructions on how to test flashrom properly (this may be risky, make sure you have a working backup ROM chip).
Flashrom Live CD
ROM chip overview
Modern mainboards store the BIOS in a reprogrammable flash ROM chip. There are hundreds of different flash ROMs, with variables such as memory size, speed, communication bus (LPC vs. ISA/PCI) and packaging to name just a few. The three most common packages are called DIP, PLCC and TSOP. The BIOS copyright holders often place a fancy sticker on the BIOS chip showing a name or logotype, BIOS version, serial number and copyright notice.
DIP32: Dual In-line Package, 32 pins
A rectangular black plastic block with lots of pins along the two longer sides of the package. DIP ROMs can be socketed which means they are detachable from the mainboard using physical force. Since they haven't been moved in and out of the socket very much (yet, hehe) they can appear to be quite difficult to release from the socket. One way to remove a DIP from a socket is by prying a thin screwdriver in between the plastic package and the socket, along the shorter sides where there are no pins, and then gently bending the screwdriver to push the DIP upwards, away from the mainboard. Alternate between the two sides to avoid bending the pins, and don't touch any of the pins with the screwdriver, see FAQ about ESD, electro-static discharge. If the DIP is soldered directly to the mainboard, it has to be desoldered in order to be reprogrammed outside the mainboard. If you do this, it's a good idea to solder a socket to the mainboard instead, to ease any future experiments.
PLCC32: Plastic Leaded Chip Carrier, 32 pins
Black plastic block again, but this one is much more square. PLCC is becoming the standard for mainboards because of it's smaller physical size. PLCC can also be socketed or soldered directly to the mainboard. Socketed PLCC chips can be removed using a special PLCC removal tool, or using a piece of nylon line tied in a loop around the chip and pulled swiftly straight up, or bending/prying using small screwdrivers if one is careful. PLCC sockets are often fragile so the screwdriver approach is not recommended. While the nylon line method sounds onorthodox it works well. Desoldering PLCC can be painful without specialized desoldering equipment particularly because PLCC chips have leads on all four sides of the package.
DIP8: Dual In-line Package, 8 pins
TSOP: Thin Small-Outline Package
TSOPs are often used in embedded systems where size is important and there is no need for replacement in the field. It is possible to (de)solder TSOPs by hand, but it comes close to wizardry.