It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, TSOP40, and TSOP48 chips, which use various protocols such as LPC, FWH, parallel flash, or SPI.
You can specify one of -h, -R, -L, -z, -E, -r, -w, -v or no operation. If no operation is specified, flashrom will only probe for flash chips. It is recommended that if you try flashrom the first time on a system, you run it in probe only mode and check the output. Also you are advised to make a backup of your current ROM contents with -r before you try to write a new image.
Typical usage is: flashrom -n -w <file>
This option is only useful in combination with --write.
flashrom reads the coreboot table to determine the current mainboard. If no coreboot table could be read or if you want to override these values, you can specify -m, e.g.:
flashrom --mainboard AGAMI:ARUMA -w agami_aruma.rom
See the 'Known boards' or 'Known laptops' section in the output of 'flashrom -L' for a list of boards which require the specification of the board name, if no coreboot table is found.
* Force chip read and pretend the chip is there.
* Force chip access even if the chip is bigger than the maximum supportedsize for the flash bus.
* Force erase even if erase is known bad.
* Force write even if write is known bad.
flashrom supports ROM layouts. This allows you to flash certain parts of the flash chip only. A ROM layout file looks like follows:
All addresses are offsets within the file, not absolute addresses! If you only want to update the normal image in a ROM you can say:
flashrom --layout rom.layout --image normal -w agami_aruma.rom
To update normal and fallback but leave the VGA BIOS alone, say:
flashrom -l rom.layout -i normal
-i fallback -w agami_aruma.rom
Currently overlapping sections are not supported.
There are many unlisted boards which will work out of the box, without special support in flashrom. Please let us know if you can verify that other boards work or do not work out of the box.
IMPORTANT: For verification you have to test an ERASE and/or WRITE operation, so make sure you only do that if you have proper means to recover from failure!
* internal (default, for in-system flashing in the mainboard)
* dummy (just prints all operations and accesses)
* nic3com (for flash ROMs on 3COM network cards)
* nicrealtek (for flash ROMs on Realtek network cards)
* nicsmc1211 (for flash ROMs on RTL8139-compatible SMC2 network cards)
* gfxnvidia (for flash ROMs on NVIDIA graphics cards)
* drkaiser (for flash ROMs on Dr. Kaiser PC-Waechter PCI cards)
* satasii (for flash ROMs on Silicon Image SATA/IDE controllers)
* atahpt (for flash ROMs on Highpoint ATA/RAID controllers)
* it87spi (for flash ROMs behind an ITE IT87xx Super I/O LPC/SPI translation unit)
* ft2232_spi (for SPI flash ROMs attached to a FT2232H/FT4232H/JTAGkey based USB SPI programmer)
* serprog (for flash ROMs attached to a programmer speaking serprog)
* buspirate_spi (for SPI flash ROMs attached to a Bus Pirate)
* rayer_spi (for SPI flash ROMs attached to a RayeR parport based programmer)
Some programmers have optional or mandatory parameters which are described in detail in the PROGRAMMER SPECIFIC INFO section. Support for some programmers can be disabled at compile time. flashrom -h lists all supported programmers.
Some of these board-specific flash enabling functions (called board enables) in flashrom have not yet been tested. If your mainboard is detected needing an untested board enable function, a warning message is printed and the board enable is not executed, because a wrong board enable function might cause the system to behave erratically, as board enable functions touch the low-level internals of a mainboard. Not executing a board enable function (if one is needed) might cause detection or erasing failure. If your board protects only part of the flash (commonly the top end, called boot block), flashrom might encounter an error only after erasing the unprotected part, so running without the board-enable function might be dangerous for erase and write (which includes erase).
The suggested procedure for a mainboard with untested board specific code is to first try to probe the ROM (just invoke flashrom and check that it detects your flash chip type) without running the board enable code (i.e. without any parameters). If it finds your chip, fine. Otherwise, retry probing your chip with the board-enable code running, using
flashrom -p internal:boardenable=force
If your chip is still not detected, the board enable code seems to be broken or the flash chip unsupported. Otherwise, make a backup of your current ROM contents (using -r) and store it to a medium outside of your computer, like a USB drive or a network share. If you needed to run the board enable code already for probing, use it for reading too. Now you can try to write the new image. You should enable the board enable code in any case now, as it has been written because it is known that writing/erasing without the board enable is going to fail. In any case (success or failure), please report to the flashrom mailing list, see below.
On systems running coreboot, flashrom checks whether the desired image matches your mainboard. This needs some special board ID to be present in the image. If flashrom detects that the image you want to write and the current board do not match, it will refuse to write the image unless you specify
flashrom -p internal:boardmismatch=force
If your mainboard uses an ITE IT87 series Super I/O for LPC<->SPI flash bus translation, flashrom should autodetect that configuration. You can use the
flashrom -p internal:it87spiport=portnum
syntax as explained in the it87spi programmer section to use a non-default port for controlling the IT87 series Super I/O. In the unlikely case flashrom doesn't detect an active IT87 LPC<->SPI bridge, you can try to force recognition by using the it87spi programmer.
Using flashrom on laptops is dangerous and may easily make your hardware unusable (see also the BUGS section). The embedded controller (EC) in these machines often interacts badly with flashing. http://www.flashrom.org/Laptops has more information. If flash is shared with the EC, erase is guaranteed to brick your laptop and write is very likely to brick your laptop. Chip read and probe may irritate your EC and cause fan failure, backlight failure, sudden poweroff, and other nasty effects. flashrom will attempt to detect laptops and abort immediately for safety reasons. If you want to proceed anyway at your own risk, use
flashrom -p internal:laptop=force_I_want_a_brick
You have been warned.
We will not help you if you force flashing on a laptop because this is a really dumb idea.
Example: flashrom -p dummy:bus=lpc+fwh
Example: flashrom -p nic3com:pci=05:04.0
flashrom -p it87spi:it87spiport=portnum
syntax where portnum is an I/O port number which must be a multiple of 8.
flashrom -p ft2232_spi:type=model,port=interface
syntax where model can be any of 2232H, JTAGkey, or 4232H and interface can be any of A, or B. The default model is 4232H and the default interface is B.
flashrom -p serprog:dev=/dev/device:baud
syntax and for IP, you have to use
flashrom -p serprog:ip=ipaddr:port
instead. More information about serprog is available in serprog-protocol.txt in the source distribution.
flashrom -p buspirate_spi:dev=/dev/device,spispeed=frequency
where frequency can be any of 30k, 125k, 250k, 1M, 2M, 2.6M, 4M, 8M (in Hz). The default is the maximum frequency of 8 MHz.
internal needs raw memory access, PCI configuration space access, raw I/O port access (x86) and MSR access (x86).
it87spi needs raw I/O port access (x86).
nic3com, nicrealtek, nicsmc1211 and nicnatsemi need PCI configuration space read access and raw I/O port access.
atahpt needs PCI configuration space access and raw I/O port access.
gfxnvidia and drkaiser need PCI configuration space access and raw memory access.
rayer_spi needs raw I/O port access.
satasii needs PCI configuration space read access and raw memory access.
serprog needs TCP access to the network or userspace access to a serial port.
buspirate_spi needs userspace access to a serial port.
dediprog and ft2232_spi need access to the USB device via libusb.
dummy needs no access permissions at all.
internal, it87spi, nic3com, nicrealtek, nicsmc1211, nicnatsemi, gfxnvidia, drkaiser, satasii and atahpt have to be run as superuser/root, and need additional raw access permission.
serprog, buspirate_spi, dediprog and ft2232_spi can be run as normal user on most operating systems if appropriate device permissions are set.
On OpenBSD, you can obtain raw access permission by setting securelevel=-1 in /etc/rc.securelevel and rebooting, or rebooting into single user mode.
or on the flashrom mailing list at
Using flashrom on laptops is dangerous and may easily make your hardware unusable unless you can desolder the flash chip and have a full flash chip backup. This is caused by the embedded controller (EC) present in many laptops, which interacts badly with any flash attempts. This is a hardware limitation and flashrom will attempt to detect it and abort immediately for safety reasons.
This manual page was written by Uwe Hermann <email@example.com> and Carl-Daniel Hailfinger. It is licensed under the terms of the GNU GPL (version 2 or later).