blob: 81eceaa7db4b819ce3d9d8dc8c0a74939a1f3323 [file] [log] [blame]
Joerg Mayera93d9dc2013-08-29 00:38:19 +00001.TH FLASHROM 8 "" ""
Stefan Reinauer261144c2006-07-27 23:29:02 +00002.SH NAME
Uwe Hermann530cb2d2009-05-14 22:58:21 +00003flashrom \- detect, read, write, verify and erase flash chips
Stefan Reinauer261144c2006-07-27 23:29:02 +00004.SH SYNOPSIS
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +00005.B flashrom \fR[\fB\-h\fR|\fB\-R\fR|\fB\-L\fR|\fB\-z\fR|\
6\fB\-p\fR <programmername>[:<parameters>]
7 [\fB\-E\fR|\fB\-r\fR <file>|\fB\-w\fR <file>|\fB\-v\fR <file>] \
8[\fB\-c\fR <chipname>]
9 [\fB\-l\fR <file> [\fB\-i\fR <image>]] [\fB\-n\fR] [\fB\-f\fR]]
10 [\fB\-V\fR[\fBV\fR[\fBV\fR]]] [\fB-o\fR <logfile>]
Stefan Reinauer261144c2006-07-27 23:29:02 +000011.SH DESCRIPTION
12.B flashrom
Uwe Hermanne8ba5382009-05-22 11:37:27 +000013is a utility for detecting, reading, writing, verifying and erasing flash
Uwe Hermann530cb2d2009-05-14 22:58:21 +000014chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system
Uwe Hermann941a2732011-07-25 21:12:57 +000015using a supported mainboard. However, it also supports various external
16PCI/USB/parallel-port/serial-port based devices which can program flash chips,
17including some network cards (NICs), SATA/IDE controller cards, graphics cards,
Ilya A. Volynets-Evenbakh2c714ab2012-09-26 00:47:09 +000018the Bus Pirate device, various FTDI FT2232/FT4232H/FT232H based USB devices, and more.
Uwe Hermanne74b9f82009-04-10 14:41:29 +000019.PP
Uwe Hermann9ff514d2010-06-07 19:41:25 +000020It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, TSOP40,
Uwe Hermann941a2732011-07-25 21:12:57 +000021TSOP48, and BGA chips, which use various protocols such as LPC, FWH,
22parallel flash, or SPI.
Stefan Reinauer261144c2006-07-27 23:29:02 +000023.SH OPTIONS
Uwe Hermann9ff514d2010-06-07 19:41:25 +000024.B IMPORTANT:
Carl-Daniel Hailfinger5de93412009-05-01 10:53:49 +000025Please note that the command line interface for flashrom will change before
26flashrom 1.0. Do not use flashrom in scripts or other automated tools without
Uwe Hermanne8ba5382009-05-22 11:37:27 +000027checking that your flashrom version won't interpret options in a different way.
Carl-Daniel Hailfinger5de93412009-05-01 10:53:49 +000028.PP
Uwe Hermann9ff514d2010-06-07 19:41:25 +000029You can specify one of
30.BR \-h ", " \-R ", " \-L ", " \-z ", " \-E ", " \-r ", " \-w ", " \-v
31or no operation.
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +000032If no operation is specified, flashrom will only probe for flash chips. It is
Michael Karcher31fd8252010-03-12 06:41:39 +000033recommended that if you try flashrom the first time on a system, you run it
Uwe Hermann941a2732011-07-25 21:12:57 +000034in probe-only mode and check the output. Also you are advised to make a
Uwe Hermann9ff514d2010-06-07 19:41:25 +000035backup of your current ROM contents with
36.B \-r
Stefan Taunere34e3e82013-01-01 00:06:51 +000037before you try to write a new image. All operations involving any chip access (probe/read/write/...) require the
38.B -p/--programmer
39option to be used (please see below).
Stefan Reinauerde063bf2006-09-21 13:09:22 +000040.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000041.B "\-r, \-\-read <file>"
42Read flash ROM contents and save them into the given
43.BR <file> .
Uwe Hermann941a2732011-07-25 21:12:57 +000044If the file already exists, it will be overwritten.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000045.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000046.B "\-w, \-\-write <file>"
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +000047Write
48.B <file>
Uwe Hermann9ff514d2010-06-07 19:41:25 +000049into flash ROM. This will first automatically
50.B erase
51the chip, then write to it.
Stefan Taunerac54fbe2011-07-21 19:52:00 +000052.sp
53In the process the chip is also read several times. First an in-memory backup
54is made for disaster recovery and to be able to skip regions that are
55already equal to the image file. This copy is updated along with the write
56operation. In case of erase errors it is even re-read completely. After
57writing has finished and if verification is enabled, the whole flash chip is
58read out and compared with the input image.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000059.TP
Uwe Hermannea07f622009-06-24 17:31:08 +000060.B "\-n, \-\-noverify"
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +000061Skip the automatic verification of flash ROM contents after writing. Using this
Uwe Hermannea07f622009-06-24 17:31:08 +000062option is
63.B not
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +000064recommended, you should only use it if you know what you are doing and if you
Uwe Hermannea07f622009-06-24 17:31:08 +000065feel that the time for verification takes too long.
66.sp
67Typical usage is:
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +000068.B "flashrom \-p prog \-n \-w <file>"
Uwe Hermannea07f622009-06-24 17:31:08 +000069.sp
70This option is only useful in combination with
71.BR \-\-write .
72.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000073.B "\-v, \-\-verify <file>"
74Verify the flash ROM contents against the given
75.BR <file> .
Stefan Reinauerde063bf2006-09-21 13:09:22 +000076.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000077.B "\-E, \-\-erase"
Uwe Hermanne74b9f82009-04-10 14:41:29 +000078Erase the flash ROM chip.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000079.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000080.B "\-V, \-\-verbose"
Uwe Hermann9ff514d2010-06-07 19:41:25 +000081More verbose output. This option can be supplied multiple times
Stefan Taunereebeb532011-08-04 17:40:25 +000082(max. 3 times, i.e.
83.BR \-VVV )
Uwe Hermann9ff514d2010-06-07 19:41:25 +000084for even more debug output.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000085.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000086.B "\-c, \-\-chip" <chipname>
Uwe Hermann9ff514d2010-06-07 19:41:25 +000087Probe only for the specified flash ROM chip. This option takes the chip name as
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +000088printed by
89.B "flashrom \-L"
Uwe Hermann9ff514d2010-06-07 19:41:25 +000090without the vendor name as parameter. Please note that the chip name is
91case sensitive.
Joerg Mayer645c6df2010-03-13 14:47:48 +000092.TP
Joerg Mayer645c6df2010-03-13 14:47:48 +000093.B "\-f, \-\-force"
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +000094Force one or more of the following actions:
Joerg Mayer645c6df2010-03-13 14:47:48 +000095.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +000096* Force chip read and pretend the chip is there.
97.sp
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +000098* Force chip access even if the chip is bigger than the maximum supported \
Uwe Hermann9ff514d2010-06-07 19:41:25 +000099size for the flash bus.
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000100.sp
101* Force erase even if erase is known bad.
102.sp
103* Force write even if write is known bad.
Joerg Mayer645c6df2010-03-13 14:47:48 +0000104.TP
105.B "\-l, \-\-layout <file>"
106Read ROM layout from
107.BR <file> .
Uwe Hermann87c07932009-05-05 16:15:46 +0000108.sp
109flashrom supports ROM layouts. This allows you to flash certain parts of
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000110the flash chip only. A ROM layout file contains multiple lines with the
111following syntax:
112.sp
113.B " startaddr:endaddr imagename"
114.sp
115.BR "startaddr " "and " "endaddr "
116are hexadecimal addresses within the ROM file and do not refer to any
117physical address. Please note that using a 0x prefix for those hexadecimal
118numbers is not necessary, but you can't specify decimal/octal numbers.
119.BR "imagename " "is an arbitrary name for the region/image from"
120.BR " startaddr " "to " "endaddr " "(both addresses included)."
121.sp
122Example:
Uwe Hermann87c07932009-05-05 16:15:46 +0000123.sp
124 00000000:00008fff gfxrom
125 00009000:0003ffff normal
126 00040000:0007ffff fallback
127.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000128If you only want to update the image named
129.BR "normal " "in a ROM based on the layout above, run"
Uwe Hermann87c07932009-05-05 16:15:46 +0000130.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000131.B " flashrom \-p prog \-\-layout rom.layout \-\-image normal \-w some.rom"
Uwe Hermann87c07932009-05-05 16:15:46 +0000132.sp
Stefan Taunere34e3e82013-01-01 00:06:51 +0000133To update only the images named
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000134.BR "normal " "and " "fallback" ", run:"
Uwe Hermann87c07932009-05-05 16:15:46 +0000135.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000136.B " flashrom \-p prog \-l rom.layout \-i normal -i fallback \-w some.rom"
Uwe Hermann87c07932009-05-05 16:15:46 +0000137.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000138Overlapping sections are not supported.
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000139.TP
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000140.B "\-i, \-\-image <imagename>"
141Only flash region/image
142.B <imagename>
Uwe Hermann67808fe2007-10-18 00:29:05 +0000143from flash layout.
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000144.TP
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000145.B "\-L, \-\-list\-supported"
Uwe Hermann941a2732011-07-25 21:12:57 +0000146List the flash chips, chipsets, mainboards, and external programmers
147(including PCI, USB, parallel port, and serial port based devices)
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000148supported by flashrom.
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000149.sp
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000150There are many unlisted boards which will work out of the box, without
151special support in flashrom. Please let us know if you can verify that
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000152other boards work or do not work out of the box.
153.sp
154.B IMPORTANT:
155For verification you have
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000156to test an ERASE and/or WRITE operation, so make sure you only do that
157if you have proper means to recover from failure!
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000158.TP
Uwe Hermann20a293f2009-06-19 10:42:43 +0000159.B "\-z, \-\-list\-supported-wiki"
160Same as
161.BR \-\-list\-supported ,
162but outputs the supported hardware in MediaWiki syntax, so that it can be
Uwe Hermann941a2732011-07-25 21:12:57 +0000163easily pasted into the wiki page at
Stefan Tauner352e50b2013-02-22 15:58:45 +0000164.nh
Uwe Hermann941a2732011-07-25 21:12:57 +0000165.BR http://www.flashrom.org/ .
166Please note that MediaWiki output is not compiled in by default.
Uwe Hermann20a293f2009-06-19 10:42:43 +0000167.TP
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000168.B "\-p, \-\-programmer <name>[:parameter[,parameter[,parameter]]]"
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000169Specify the programmer device. This is mandatory for all operations
170involving any chip access (probe/read/write/...). Currently supported are:
Carl-Daniel Hailfingerce986772009-05-09 00:27:07 +0000171.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000172.BR "* internal" " (default, for in-system flashing in the mainboard)"
173.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000174.BR "* dummy" " (virtual programmer for testing flashrom)"
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000175.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000176.BR "* nic3com" " (for flash ROMs on 3COM network cards)"
177.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000178.BR "* nicrealtek" " (for flash ROMs on Realtek and SMC 1211 network cards)"
Uwe Hermann829ed842010-05-24 17:39:14 +0000179.sp
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000180.BR "* nicnatsemi" " (for flash ROMs on National Semiconductor DP838* network \
181cards)"
182.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000183.BR "* nicintel" " (for parallel flash ROMs on Intel 10/100Mbit network cards)
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000184.sp
Uwe Hermann2bc98f62009-09-30 18:29:55 +0000185.BR "* gfxnvidia" " (for flash ROMs on NVIDIA graphics cards)"
186.sp
TURBO Jb0912c02009-09-02 23:00:46 +0000187.BR "* drkaiser" " (for flash ROMs on Dr. Kaiser PC-Waechter PCI cards)"
188.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000189.BR "* satasii" " (for flash ROMs on Silicon Image SATA/IDE controllers)"
190.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000191.BR "* satamv" " (for flash ROMs on Marvell SATA controllers)"
192.sp
Uwe Hermannddd5c9e2010-02-21 21:17:00 +0000193.BR "* atahpt" " (for flash ROMs on Highpoint ATA/RAID controllers)"
194.sp
Stefan Tauner4f094752014-06-01 22:36:30 +0000195.BR "* atavia" " (for flash ROMs on VIA VT6421A SATA controllers)"
Jonathan Kollasch7f0f3fa2014-06-01 10:26:23 +0000196.sp
Kyösti Mälkki72d42f82014-06-01 23:48:31 +0000197.BR "* it8212" " (for flash ROMs on ITE IT8212F ATA/RAID controller)"
198.sp
Ilya A. Volynets-Evenbakh2c714ab2012-09-26 00:47:09 +0000199.BR "* ft2232_spi" " (for SPI flash ROMs attached to an FT2232/FT4232H/FT232H family \
Uwe Hermann314cfba2011-07-28 19:23:09 +0000200based USB SPI programmer), including the DLP Design DLP-USB1232H, \
201FTDI FT2232H Mini-Module, FTDI FT4232H Mini-Module, openbiosprog-spi, Amontec \
Steve Markgraf0528b7f2011-08-12 01:19:32 +0000202JTAGkey/JTAGkey-tiny/JTAGkey-2, Dangerous Prototypes Bus Blaster, \
Samir Ibradžić7189a5f2011-10-20 23:14:10 +0000203Olimex ARM-USB-TINY/-H, Olimex ARM-USB-OCD/-H, TIAO/DIYGADGET USB
Stefan Taunerb66ed842014-04-27 05:07:35 +0000204Multi-Protocol Adapter (TUMPA), TUMPA Lite, and GOEPEL PicoTAP.
Paul Fox05dfbe62009-06-16 21:08:06 +0000205.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000206.BR "* serprog" " (for flash ROMs attached to a programmer speaking serprog), \
207including AVR flasher by Urja Rannikko, AVR flasher by eightdot, \
208Arduino Mega flasher by fritz, InSystemFlasher by Juhana Helovuo, and \
209atmegaXXu2-flasher by Stefan Tauner."
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000210.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000211.BR "* buspirate_spi" " (for SPI flash ROMs attached to a Bus Pirate)"
Carl-Daniel Hailfingerd5b28fa2009-11-24 18:27:10 +0000212.sp
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000213.BR "* dediprog" " (for SPI flash ROMs attached to a Dediprog SF100)"
214.sp
Kyösti Mälkki8b1bdf12013-10-02 01:21:45 +0000215.BR "* rayer_spi" " (for SPI flash ROMs attached to a parallel port by one of various cable types)"
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000216.sp
Michael Karchere5449392012-05-05 20:53:59 +0000217.BR "* pony_spi" " (for SPI flash ROMs attached to a SI-Prog serial port "
218bitbanging adapter)
219.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000220.BR "* nicintel_spi" " (for SPI flash ROMs on Intel Gigabit network cards)"
Idwer Vollering004f4b72010-09-03 18:21:21 +0000221.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000222.BR "* ogp_spi" " (for SPI flash ROMs on Open Graphics Project graphics card)"
Mark Marshall90021f22010-12-03 14:48:11 +0000223.sp
Carl-Daniel Hailfinger8541d232012-02-16 21:00:27 +0000224.BR "* linux_spi" " (for SPI flash ROMs accessible via /dev/spidevX.Y on Linux)"
225.sp
James Lairdc60de0e2013-03-27 13:00:23 +0000226.BR "* usbblaster_spi" " (for SPI flash ROMs attached to an Altera USB-Blaster compatible cable)"
227.sp
Ricardo Ribalda Delgado2a41f0a2014-07-28 20:35:21 +0000228.BR "* nicintel_eeprom" " (for SPI EEPROMs on Intel Gigabit network cards)"
229.sp
Michael Karchere5eafb22010-03-07 12:11:08 +0000230Some programmers have optional or mandatory parameters which are described
231in detail in the
Stefan Tauner6697f712014-08-06 15:09:15 +0000232.B PROGRAMMER-SPECIFIC INFORMATION
Michael Karchere5eafb22010-03-07 12:11:08 +0000233section. Support for some programmers can be disabled at compile time.
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000234.B "flashrom \-h"
Michael Karchere5eafb22010-03-07 12:11:08 +0000235lists all supported programmers.
236.TP
237.B "\-h, \-\-help"
238Show a help text and exit.
239.TP
Carl-Daniel Hailfinger0b9af362012-07-21 16:56:04 +0000240.B "\-o, \-\-output <logfile>"
241Save the full debug log to
242.BR <logfile> .
243If the file already exists, it will be overwritten. This is the recommended
244way to gather logs from flashrom because they will be verbose even if the
Stefan Tauner6697f712014-08-06 15:09:15 +0000245on-screen messages are not verbose and don't require output redirection.
Carl-Daniel Hailfinger0b9af362012-07-21 16:56:04 +0000246.TP
Michael Karchere5eafb22010-03-07 12:11:08 +0000247.B "\-R, \-\-version"
248Show version information and exit.
Stefan Tauner6697f712014-08-06 15:09:15 +0000249.SH PROGRAMMER-SPECIFIC INFORMATION
Michael Karchere5eafb22010-03-07 12:11:08 +0000250Some programmer drivers accept further parameters to set programmer-specific
Uwe Hermann4e3d0b32010-03-25 23:18:41 +0000251parameters. These parameters are separated from the programmer name by a
Michael Karchere5eafb22010-03-07 12:11:08 +0000252colon. While some programmers take arguments at fixed positions, other
253programmers use a key/value interface in which the key and value is separated
254by an equal sign and different pairs are separated by a comma or a colon.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000255.SS
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000256.BR "internal " programmer
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000257.TP
258.B Board Enables
259.sp
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000260Some mainboards require to run mainboard specific code to enable flash erase
261and write support (and probe support on old systems with parallel flash).
262The mainboard brand and model (if it requires specific code) is usually
263autodetected using one of the following mechanisms: If your system is
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000264running coreboot, the mainboard type is determined from the coreboot table.
265Otherwise, the mainboard is detected by examining the onboard PCI devices
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000266and possibly DMI info. If PCI and DMI do not contain information to uniquely
Carl-Daniel Hailfinger2d927fb2012-01-04 00:48:27 +0000267identify the mainboard (which is the exception), or if you want to override
268the detected mainboard model, you can specify the mainboard using the
269.sp
Stefan Taunerb4e06bd2012-08-20 00:24:22 +0000270.B " flashrom \-p internal:mainboard=<vendor>:<board>"
Carl-Daniel Hailfinger2d927fb2012-01-04 00:48:27 +0000271syntax.
272.sp
273See the 'Known boards' or 'Known laptops' section in the output
274of 'flashrom \-L' for a list of boards which require the specification of
275the board name, if no coreboot table is found.
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000276.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000277Some of these board-specific flash enabling functions (called
278.BR "board enables" )
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000279in flashrom have not yet been tested. If your mainboard is detected needing
280an untested board enable function, a warning message is printed and the
281board enable is not executed, because a wrong board enable function might
282cause the system to behave erratically, as board enable functions touch the
283low-level internals of a mainboard. Not executing a board enable function
284(if one is needed) might cause detection or erasing failure. If your board
285protects only part of the flash (commonly the top end, called boot block),
286flashrom might encounter an error only after erasing the unprotected part,
287so running without the board-enable function might be dangerous for erase
288and write (which includes erase).
289.sp
290The suggested procedure for a mainboard with untested board specific code is
291to first try to probe the ROM (just invoke flashrom and check that it
292detects your flash chip type) without running the board enable code (i.e.
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000293without any parameters). If it finds your chip, fine. Otherwise, retry
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000294probing your chip with the board-enable code running, using
295.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000296.B " flashrom \-p internal:boardenable=force"
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000297.sp
298If your chip is still not detected, the board enable code seems to be broken
299or the flash chip unsupported. Otherwise, make a backup of your current ROM
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000300contents (using
301.BR \-r )
302and store it to a medium outside of your computer, like
303a USB drive or a network share. If you needed to run the board enable code
Stefan Taunereb582572012-09-21 12:52:50 +0000304already for probing, use it for reading too.
305If reading succeeds and the contens of the read file look legit you can try to write the new image.
306You should enable the board enable code in any case now, as it
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000307has been written because it is known that writing/erasing without the board
308enable is going to fail. In any case (success or failure), please report to
309the flashrom mailing list, see below.
310.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000311.TP
312.B Coreboot
313.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000314On systems running coreboot, flashrom checks whether the desired image matches
315your mainboard. This needs some special board ID to be present in the image.
316If flashrom detects that the image you want to write and the current board
317do not match, it will refuse to write the image unless you specify
318.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000319.B " flashrom \-p internal:boardmismatch=force"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000320.TP
321.B ITE IT87 Super I/O
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000322.sp
Vadim Girlin4dd0f902013-08-24 12:18:17 +0000323If your mainboard is manufactured by GIGABYTE and supports DualBIOS it is very likely that it uses an
324ITE IT87 series Super I/O to switch between the two flash chips. Only one of them can be accessed at a time
325and you can manually select which one to use with the
326.sp
327.B " flashrom \-p internal:dualbiosindex=chip"
328.sp
329syntax where
330.B chip
331is the index of the chip to use (0 = main, 1 = backup). You can check which one is currently selected by
332leaving out the
333.B chip
334parameter.
335.sp
Carl-Daniel Hailfinger01f3ef42010-03-25 02:50:40 +0000336If your mainboard uses an ITE IT87 series Super I/O for LPC<->SPI flash bus
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000337translation, flashrom should autodetect that configuration. If you want to
338set the I/O base port of the IT87 series SPI controller manually instead of
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000339using the value provided by the BIOS, use the
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +0000340.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000341.B " flashrom \-p internal:it87spiport=portnum"
342.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000343syntax where
344.B portnum
345is the I/O port number (must be a multiple of 8). In the unlikely case
346flashrom doesn't detect an active IT87 LPC<->SPI bridge, please send a bug
347report so we can diagnose the problem.
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000348.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000349.TP
Rudolf Marek70e14592013-07-25 22:58:56 +0000350.B AMD chipsets
351.sp
352Beginning with the SB700 chipset there is an integrated microcontroller (IMC) based on the 8051 embedded in
353every AMD southbridge. Its firmware resides in the same flash chip as the host's which makes writing to the
354flash risky if the IMC is active. Flashrom tries to temporarily disable the IMC but even then changing the
355contents of the flash can have unwanted effects: when the IMC continues (at the latest after a reboot) it will
356continue executing code from the flash. If the code was removed or changed in an unfortunate way it is
357unpredictable what the IMC will do. Therefore, if flashrom detects an active IMC it will disable write support
358unless the user forces it with the
359.sp
360.B " flashrom \-p internal:amd_imc_force=yes"
361.sp
362syntax. The user is responsible for supplying a suitable image or leaving out the IMC region with the help of
363a layout file. This limitation might be removed in the future when we understand the details better and have
364received enough feedback from users. Please report the outcome if you had to use this option to write a chip.
365.sp
Stefan Tauner21071b02014-05-16 21:39:48 +0000366An optional
367.B spispeed
368parameter specifies the frequency of the SPI bus where applicable (i.e.\& SB600 or later with an SPI flash chip
369directly attached to the chipset).
370Syntax is
371.sp
372.B " flashrom \-p internal:spispeed=frequency"
373.sp
374where
375.B frequency
376can be
377.BR "'16.5\ MHz'" ", " "'22\ MHz'" ", " "'33\ MHz'" ", " "'66\ MHz'" ", " "'100\ MHZ'" ", or " "'800\ kHz'" "."
378Support of individual frequencies depends on the generation of the chipset:
379.sp
380* SB6xx, SB7xx, SP5xxx: from 16.5 MHz up to and including 33 MHz
381.sp
382* SB8xx, SB9xx, Hudson: from 16.5 MHz up to and including 66 MHz
383.sp
384* Yangtze (with SPI 100 engine as found in Kabini and Tamesh): all of them
385.sp
386The default is to use 16.5 MHz and disable Fast Reads.
Rudolf Marek70e14592013-07-25 22:58:56 +0000387.TP
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000388.B Intel chipsets
389.sp
Stefan Tauner50e7c602011-11-08 10:55:54 +0000390If you have an Intel chipset with an ICH8 or later southbridge with SPI flash
Stefan Taunereb582572012-09-21 12:52:50 +0000391attached, and if a valid descriptor was written to it (e.g.\& by the vendor), the
Stefan Tauner50e7c602011-11-08 10:55:54 +0000392chipset provides an alternative way to access the flash chip(s) named
393.BR "Hardware Sequencing" .
394It is much simpler than the normal access method (called
395.BR "Software Sequencing" "),"
396but does not allow the software to choose the SPI commands to be sent.
397You can use the
398.sp
399.B " flashrom \-p internal:ich_spi_mode=value"
400.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000401syntax where
402.BR "value " "can be"
Stefan Tauner50e7c602011-11-08 10:55:54 +0000403.BR auto ", " swseq " or " hwseq .
404By default
405.RB "(or when setting " ich_spi_mode=auto )
Stefan Taunereb582572012-09-21 12:52:50 +0000406the module tries to use swseq and only activates hwseq if need be (e.g.\& if
Stefan Tauner50e7c602011-11-08 10:55:54 +0000407important opcodes are inaccessible due to lockdown; or if more than one flash
408chip is attached). The other options (swseq, hwseq) select the respective mode
409(if possible).
410.sp
Stefan Tauner5210e722012-02-16 01:13:00 +0000411ICH8 and later southbridges may also have locked address ranges of different
412kinds if a valid descriptor was written to it. The flash address space is then
413partitioned in multiple so called "Flash Regions" containing the host firmware,
414the ME firmware and so on respectively. The flash descriptor can also specify up
415to 5 so called "Protected Regions", which are freely chosen address ranges
416independent from the aforementioned "Flash Regions". All of them can be write
417and/or read protected individually. If flashrom detects such a lock it will
418disable write support unless the user forces it with the
419.sp
420.B " flashrom \-p internal:ich_spi_force=yes"
421.sp
422syntax. If this leads to erase or write accesses to the flash it would most
423probably bring it into an inconsistent and unbootable state and we will not
424provide any support in such a case.
425.sp
Kyösti Mälkki88ee0402013-09-14 23:37:01 +0000426If you have an Intel chipset with an ICH2 or later southbridge and if you want
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000427to set specific IDSEL values for a non-default flash chip or an embedded
428controller (EC), you can use the
429.sp
430.B " flashrom \-p internal:fwh_idsel=value"
431.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000432syntax where
433.B value
434is the 48-bit hexadecimal raw value to be written in the
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000435IDSEL registers of the Intel southbridge. The upper 32 bits use one hex digit
436each per 512 kB range between 0xffc00000 and 0xffffffff, and the lower 16 bits
437use one hex digit each per 1024 kB range between 0xff400000 and 0xff7fffff.
438The rightmost hex digit corresponds with the lowest address range. All address
439ranges have a corresponding sister range 4 MB below with identical IDSEL
440settings. The default value for ICH7 is given in the example below.
441.sp
442Example:
443.B "flashrom \-p internal:fwh_idsel=0x001122334567"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000444.TP
445.B Laptops
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000446.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000447Using flashrom on laptops is dangerous and may easily make your hardware
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000448unusable (see also the
449.B BUGS
450section). The embedded controller (EC) in these
451machines often interacts badly with flashing.
Stefan Tauner352e50b2013-02-22 15:58:45 +0000452.nh
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000453.B http://www.flashrom.org/Laptops
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000454has more information. For example the EC firmware sometimes resides on the same
455flash chip as the host firmware. While flashrom tries to change the contents of
456that memory the EC might need to fetch new instructions or data from it and
457could stop working correctly. Probing for and reading from the chip may also
458irritate your EC and cause fan failure, backlight failure, sudden poweroff, and
459other nasty effects. flashrom will attempt to detect if it is running on a
460laptop and abort immediately for safety reasons if it clearly identifies the
461host computer as one. If you want to proceed anyway at your own risk, use
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000462.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000463.B " flashrom \-p internal:laptop=force_I_want_a_brick"
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000464.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000465We will not help you if you force flashing on a laptop because this is a really
466dumb idea.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000467.sp
468You have been warned.
469.sp
470Currently we rely on the chassis type encoded in the DMI/SMBIOS data to detect
471laptops. Some vendors did not implement those bits correctly or set them to
472generic and/or dummy values. flashrom will then issue a warning and bail out
473like above. In this case you can use
474.sp
475.B " flashrom \-p internal:laptop=this_is_not_a_laptop"
476.sp
Stefan Tauner6697f712014-08-06 15:09:15 +0000477to tell flashrom (at your own risk) that it is not running on a laptop.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000478.SS
Michael Karchere5eafb22010-03-07 12:11:08 +0000479.BR "dummy " programmer
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000480The dummy programmer operates on a buffer in memory only. It provides a safe
481and fast way to test various aspects of flashrom and is mainly used in
482development and while debugging.
483.sp
484It is able to emulate some chips to a certain degree (basic
485identify/read/erase/write operations work).
486.sp
Michael Karchere5eafb22010-03-07 12:11:08 +0000487An optional parameter specifies the bus types it
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000488should support. For that you have to use the
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000489.sp
490.B " flashrom \-p dummy:bus=[type[+type[+type]]]"
491.sp
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000492syntax where
493.B type
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000494can be
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000495.BR parallel ", " lpc ", " fwh ", " spi
496in any order. If you specify bus without type, all buses will be disabled.
497If you do not specify bus, all buses will be enabled.
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000498.sp
499Example:
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000500.B "flashrom \-p dummy:bus=lpc+fwh"
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000501.sp
502The dummy programmer supports flash chip emulation for automated self-tests
503without hardware access. If you want to emulate a flash chip, use the
504.sp
505.B " flashrom \-p dummy:emulate=chip"
506.sp
507syntax where
508.B chip
509is one of the following chips (please specify only the chip name, not the
510vendor):
511.sp
512.RB "* ST " M25P10.RES " SPI flash chip (RES, page write)"
513.sp
514.RB "* SST " SST25VF040.REMS " SPI flash chip (REMS, byte write)"
515.sp
516.RB "* SST " SST25VF032B " SPI flash chip (RDID, AAI write)"
517.sp
Stefan Tauner0b9df972012-05-07 22:12:16 +0000518.RB "* Macronix " MX25L6436 " SPI flash chip (RDID, SFDP)"
519.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000520Example:
521.B "flashrom -p dummy:emulate=SST25VF040.REMS"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000522.TP
523.B Persistent images
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000524.sp
525If you use flash chip emulation, flash image persistence is available as well
526by using the
527.sp
528.B " flashrom \-p dummy:emulate=chip,image=image.rom"
529.sp
530syntax where
531.B image.rom
532is the file where the simulated chip contents are read on flashrom startup and
533where the chip contents on flashrom shutdown are written to.
534.sp
535Example:
536.B "flashrom -p dummy:emulate=M25P10.RES,image=dummy.bin"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000537.TP
538.B SPI write chunk size
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000539.sp
540If you use SPI flash chip emulation for a chip which supports SPI page write
541with the default opcode, you can set the maximum allowed write chunk size with
542the
543.sp
544.B " flashrom \-p dummy:emulate=chip,spi_write_256_chunksize=size"
545.sp
546syntax where
547.B size
Stefan Taunereb582572012-09-21 12:52:50 +0000548is the number of bytes (min.\& 1, max.\& 256).
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000549.sp
550Example:
551.sp
552.B " flashrom -p dummy:emulate=M25P10.RES,spi_write_256_chunksize=5"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000553.TP
554.B SPI blacklist
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000555.sp
556To simulate a programmer which refuses to send certain SPI commands to the
557flash chip, you can specify a blacklist of SPI commands with the
558.sp
559.B " flashrom -p dummy:spi_blacklist=commandlist"
560.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000561syntax where
562.B commandlist
563is a list of two-digit hexadecimal representations of
Stefan Taunereb582572012-09-21 12:52:50 +0000564SPI commands. If commandlist is e.g.\& 0302, flashrom will behave as if the SPI
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000565controller refuses to run command 0x03 (READ) and command 0x02 (WRITE).
566commandlist may be up to 512 characters (256 commands) long.
567Implementation note: flashrom will detect an error during command execution.
568.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000569.TP
570.B SPI ignorelist
571.sp
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000572To simulate a flash chip which ignores (doesn't support) certain SPI commands,
573you can specify an ignorelist of SPI commands with the
574.sp
575.B " flashrom -p dummy:spi_ignorelist=commandlist"
576.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000577syntax where
578.B commandlist
579is a list of two-digit hexadecimal representations of
Stefan Taunereb582572012-09-21 12:52:50 +0000580SPI commands. If commandlist is e.g.\& 0302, the emulated flash chip will ignore
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000581command 0x03 (READ) and command 0x02 (WRITE). commandlist may be up to 512
582characters (256 commands) long.
583Implementation note: flashrom won't detect an error during command execution.
Stefan Tauner5e695ab2012-05-06 17:03:40 +0000584.sp
585.TP
586.B SPI status register
587.sp
588You can specify the initial content of the chip's status register with the
589.sp
590.B " flashrom -p dummy:spi_status=content"
591.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000592syntax where
593.B content
594is an 8-bit hexadecimal value.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000595.SS
Ricardo Ribalda Delgado2a41f0a2014-07-28 20:35:21 +0000596.BR "nic3com" , " nicrealtek" , " nicnatsemi" , " nicintel", " nicintel_eeprom"\
Jonathan Kollasch7f0f3fa2014-06-01 10:26:23 +0000597, " nicintel_spi" , " gfxnvidia" , " ogp_spi" , " drkaiser" , " satasii"\
Stefan Tauner6697f712014-08-06 15:09:15 +0000598, " satamv" , " atahpt", " atavia " and " it8212 " programmers
Michael Karchere5eafb22010-03-07 12:11:08 +0000599These programmers have an option to specify the PCI address of the card
600your want to use, which must be specified if more than one card supported
601by the selected programmer is installed in your system. The syntax is
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000602.sp
603.BR " flashrom \-p xxxx:pci=bb:dd.f" ,
604.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000605where
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000606.B xxxx
Stefan Taunerc2eec2c2014-05-03 21:33:01 +0000607is the name of the programmer,
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000608.B bb
609is the PCI bus number,
610.B dd
611is the PCI device number, and
612.B f
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000613is the PCI function number of the desired device.
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000614.sp
615Example:
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000616.B "flashrom \-p nic3com:pci=05:04.0"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000617.SS
Jonathan Kollasch7f0f3fa2014-06-01 10:26:23 +0000618.BR "atavia " programmer
619Due to the mysterious address handling of the VIA VT6421A controller the user can specify an offset with the
620.sp
621.B " flashrom \-p atavia:offset=addr"
622.sp
623syntax where
624.B addr
625will be interpreted as usual (leading 0x (0) for hexadecimal (octal) values, or else decimal).
626For more information please see
627.nh
628.B http://flashrom.org/VT6421A
629.SS
Ricardo Ribalda Delgado2a41f0a2014-07-28 20:35:21 +0000630.BR "nicintel_eeprom " programmer
631This is the first programmer module in flashrom that does not provide access to NOR flash chips but EEPROMs
632mounted on gigabit Ethernet cards based on Intel's 82580 NIC. Because EEPROMs normally do not announce their
633size nor allow to be identified, the controller relies on correct size values written to predefined addresses
634within the chip. Flashrom follows this scheme but assumes the minimum size of 16 kB (128 kb) if an unprogrammed
635EEPROM/card is detected. Intel specifies following EEPROMs to be compatible: Atmel AT25128, AT25256, Micron (ST)
636M95128, M95256 and OnSemi (Catalyst) CAT25CS128.
637.SS
Carl-Daniel Hailfinger71127722010-05-31 15:27:27 +0000638.BR "ft2232_spi " programmer
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000639An optional parameter specifies the controller
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000640type and channel/interface/port it should support. For that you have to use the
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000641.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000642.B " flashrom \-p ft2232_spi:type=model,port=interface"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000643.sp
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000644syntax where
645.B model
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000646can be
Ilya A. Volynets-Evenbakh2c714ab2012-09-26 00:47:09 +0000647.BR 2232H ", " 4232H ", " 232H ", " jtagkey ", " busblaster ", " openmoko ", " \
Uwe Hermann836b26a2011-10-14 20:33:14 +0000648arm-usb-tiny ", " arm-usb-tiny-h ", " arm-usb-ocd ", " arm-usb-ocd-h \
Stefan Taunerb66ed842014-04-27 05:07:35 +0000649", " tumpa ", " tumpalite ", or " picotap
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000650and
651.B interface
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000652can be
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000653.BR A ", " B ", " C ", or " D .
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000654The default model is
655.B 4232H
656and the default interface is
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000657.BR A .
Samir Ibradžićb482c6d2012-05-15 22:58:19 +0000658.sp
Shik Chen14fbc4b2012-09-17 00:40:54 +0000659If there is more than one ft2232_spi-compatible device connected, you can select which one should be used by
660specifying its serial number with the
661.sp
662.B " flashrom \-p ft2232_spi:serial=number"
663.sp
664syntax where
665.B number
666is the serial number of the device (which can be found for example in the output of lsusb -v).
667.sp
Samir Ibradžićb482c6d2012-05-15 22:58:19 +0000668All models supported by the ft2232_spi driver can configure the SPI clock rate by setting a divisor. The
Stefan Tauner0554ca52013-07-25 22:54:25 +0000669expressible divisors are all
670.B even
671numbers between 2 and 2^17 (=131072) resulting in SPI clock frequencies of
Samir Ibradžićb482c6d2012-05-15 22:58:19 +00006726 MHz down to about 92 Hz for 12 MHz inputs. The default divisor is set to 2, but you can use another one by
673specifying the optional
674.B divisor
675parameter with the
676.sp
677.B " flashrom \-p ft2232_spi:divisor=div"
678.sp
679syntax.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000680.SS
Michael Karchere5eafb22010-03-07 12:11:08 +0000681.BR "serprog " programmer
682A mandatory parameter specifies either a serial
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000683device/baud combination or an IP/port combination for communication with the
Michael Karchere5eafb22010-03-07 12:11:08 +0000684programmer. In the device/baud combination, the device has to start with a
685slash. For serial, you have to use the
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000686.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000687.B " flashrom \-p serprog:dev=/dev/device:baud"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000688.sp
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000689syntax and for IP, you have to use
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000690.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000691.B " flashrom \-p serprog:ip=ipaddr:port"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000692.sp
Stefan Taunerb98f6eb2012-08-13 16:33:04 +0000693instead. In case the device supports it, you can set the SPI clock frequency
694with the optional
695.B spispeed
Stefan Tauner0554ca52013-07-25 22:54:25 +0000696parameter. The frequency is parsed as hertz, unless an
Stefan Taunerb98f6eb2012-08-13 16:33:04 +0000697.BR M ", or " k
698suffix is given, then megahertz or kilohertz are used respectively.
699Example that sets the frequency to 2 MHz:
700.sp
Stefan Tauner0554ca52013-07-25 22:54:25 +0000701.B " flashrom \-p serprog:dev=/dev/device:baud,spispeed=2M"
Stefan Taunerb98f6eb2012-08-13 16:33:04 +0000702.sp
703More information about serprog is available in
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000704.B serprog-protocol.txt
705in the source distribution.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000706.SS
Carl-Daniel Hailfinger71127722010-05-31 15:27:27 +0000707.BR "buspirate_spi " programmer
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000708A required
709.B dev
710parameter specifies the Bus Pirate device node and an optional
711.B spispeed
712parameter specifies the frequency of the SPI bus. The parameter
Michael Karchere5eafb22010-03-07 12:11:08 +0000713delimiter is a comma. Syntax is
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000714.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000715.B " flashrom \-p buspirate_spi:dev=/dev/device,spispeed=frequency"
Michael Karchere5eafb22010-03-07 12:11:08 +0000716.sp
Carl-Daniel Hailfingerd5b28fa2009-11-24 18:27:10 +0000717where
718.B frequency
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000719can be
720.BR 30k ", " 125k ", " 250k ", " 1M ", " 2M ", " 2.6M ", " 4M " or " 8M
Michael Karchere5eafb22010-03-07 12:11:08 +0000721(in Hz). The default is the maximum frequency of 8 MHz.
Brian Salcedo30dfdba2013-01-03 20:44:30 +0000722.sp
723An optional pullups parameter specifies the use of the Bus Pirate internal pull-up resistors. This may be
724needed if you are working with a flash ROM chip that you have physically removed from the board. Syntax is
725.sp
726.B " flashrom -p buspirate_spi:pullups=state"
727.sp
728where
729.B state
730can be
731.BR on " or " off .
732More information about the Bus Pirate pull-up resistors and their purpose is available at
733.nh
734.BR "http://dangerousprototypes.com/docs/Practical_guide_to_Bus_Pirate_pull-up_resistors " .
735Only the external supply voltage (Vpu) is supported as of this writing.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000736.SS
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000737.BR "dediprog " programmer
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000738An optional
739.B voltage
740parameter specifies the voltage the Dediprog should use. The default unit is
741Volt if no unit is specified. You can use
742.BR mV ", " milliVolt ", " V " or " Volt
743as unit specifier. Syntax is
744.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000745.B " flashrom \-p dediprog:voltage=value"
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000746.sp
747where
748.B value
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000749can be
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000750.BR 0V ", " 1.8V ", " 2.5V ", " 3.5V
751or the equivalent in mV.
Nathan Laredo21541a62012-12-24 22:07:36 +0000752.sp
753An optional
754.B device
755parameter specifies which of multiple connected Dediprog devices should be used.
756Please be aware that the order depends on libusb's usb_get_busses() function and that the numbering starts
757at 0.
758Usage example to select the second device:
759.sp
760.B " flashrom \-p dediprog:device=1"
Nico Huber77fa67d2013-02-20 18:03:36 +0000761.sp
762An optional
763.B spispeed
Patrick Georgiefe2d432013-05-23 21:47:46 +0000764parameter specifies the frequency of the SPI bus. The firmware on the device needs to be 5.0.0 or newer.
765Syntax is
Nico Huber77fa67d2013-02-20 18:03:36 +0000766.sp
767.B " flashrom \-p dediprog:spispeed=frequency"
768.sp
769where
770.B frequency
771can be
772.BR 375k ", " 750k ", " 1.5M ", " 2.18M ", " 3M ", " 8M ", " 12M " or " 24M
773(in Hz). The default is a frequency of 12 MHz.
Stefan Taunere659d2d2013-05-03 21:58:28 +0000774.sp
775An optional
776.B target
777parameter specifies which target chip should be used. Syntax is
778.sp
779.B " flashrom \-p dediprog:target=value"
780.sp
781where
782.B value
783can be
784.BR 1 " or " 2
Stefan Tauner6697f712014-08-06 15:09:15 +0000785to select target chip 1 or 2 respectively. The default is target chip 1.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000786.SS
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000787.BR "rayer_spi " programmer
Carl-Daniel Hailfinger37c42522010-10-05 19:19:48 +0000788The default I/O base address used for the parallel port is 0x378 and you can use
789the optional
790.B iobase
791parameter to specify an alternate base I/O address with the
792.sp
793.B " flashrom \-p rayer_spi:iobase=baseaddr"
794.sp
795syntax where
796.B baseaddr
797is base I/O port address of the parallel port, which must be a multiple of
798four. Make sure to not forget the "0x" prefix for hexadecimal port addresses.
799.sp
Carl-Daniel Hailfingerae418d82011-09-12 06:17:06 +0000800The default cable type is the RayeR cable. You can use the optional
801.B type
802parameter to specify the cable type with the
803.sp
804.B " flashrom \-p rayer_spi:type=model"
805.sp
806syntax where
807.B model
808can be
Maksim Kuleshov4dab5c12013-10-02 01:22:02 +0000809.BR rayer " for the RayeR cable, " byteblastermv " for the Altera ByteBlasterMV, " stk200 " for the Atmel \
Maksim Kuleshovacba2ac2013-10-02 01:22:11 +0000810STK200/300, " wiggler " for the Macraigor Wiggler, or " xilinx " for the Xilinx Parallel Cable III (DLC 5)."
Carl-Daniel Hailfingerae418d82011-09-12 06:17:06 +0000811.sp
812More information about the RayeR hardware is available at
Stefan Tauner352e50b2013-02-22 15:58:45 +0000813.nh
Carl-Daniel Hailfingerae418d82011-09-12 06:17:06 +0000814.BR "http://rayer.ic.cz/elektro/spipgm.htm " .
Maksim Kuleshov3647b2d2013-10-02 01:21:57 +0000815The Altera ByteBlasterMV datasheet can be obtained from
816.nh
817.BR "http://www.altera.co.jp/literature/ds/dsbytemv.pdf " .
Maksim Kuleshovacba2ac2013-10-02 01:22:11 +0000818For more information about the Macraigor Wiggler see
819.nh
820.BR "http://www.macraigor.com/wiggler.htm " .
Kyösti Mälkki8b1bdf12013-10-02 01:21:45 +0000821The schematic of the Xilinx DLC 5 was published in
Stefan Tauner352e50b2013-02-22 15:58:45 +0000822.nh
Kyösti Mälkki8b1bdf12013-10-02 01:21:45 +0000823.BR "http://www.xilinx.com/support/documentation/user_guides/xtp029.pdf " .
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000824.SS
Michael Karchere5449392012-05-05 20:53:59 +0000825.BR "pony_spi " programmer
826The serial port (like /dev/ttyS0, /dev/ttyUSB0 on Linux or COM3 on windows) is
827specified using the mandatory
Stefan Taunere34e3e82013-01-01 00:06:51 +0000828.B dev
Michael Karchere5449392012-05-05 20:53:59 +0000829parameter. The adapter type is selectable between SI-Prog (used for
830SPI devices with PonyProg 2000) or a custom made serial bitbanging programmer
831named "serbang". The optional
Stefan Taunere34e3e82013-01-01 00:06:51 +0000832.B type
Michael Karchere5449392012-05-05 20:53:59 +0000833parameter accepts the values "si_prog" (default) or "serbang".
834.sp
835Information about the SI-Prog adapter can be found at
Stefan Tauner352e50b2013-02-22 15:58:45 +0000836.nh
Michael Karchere5449392012-05-05 20:53:59 +0000837.BR "http://www.lancos.com/siprogsch.html " .
838.sp
839An example call to flashrom is
840.sp
841.B " flashrom \-p pony_spi:dev=/dev/ttyS0,type=serbang"
842.sp
843Please note that while USB-to-serial adapters work under certain circumstances,
844this slows down operation considerably.
845.SS
Mark Marshall90021f22010-12-03 14:48:11 +0000846.BR "ogp_spi " programmer
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000847The flash ROM chip to access must be specified with the
Mark Marshall90021f22010-12-03 14:48:11 +0000848.B rom
849parameter.
850.sp
851.B " flashrom \-p ogp_spi:rom=name"
852.sp
853Where
854.B name
855is either
856.B cprom
857or
858.B s3
Stefan Taunere34e3e82013-01-01 00:06:51 +0000859for the configuration ROM and
Mark Marshall90021f22010-12-03 14:48:11 +0000860.B bprom
861or
862.B bios
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000863for the BIOS ROM. If more than one card supported by the ogp_spi programmer
Mark Marshall90021f22010-12-03 14:48:11 +0000864is installed in your system, you have to specify the PCI address of the card
865you want to use with the
866.B pci=
867parameter as explained in the
Stefan Taunere34e3e82013-01-01 00:06:51 +0000868.B nic3com et al.\&
Mark Marshall90021f22010-12-03 14:48:11 +0000869section above.
870.sp
871More information about the hardware is available at
Stefan Tauner352e50b2013-02-22 15:58:45 +0000872.nh
Uwe Hermann941a2732011-07-25 21:12:57 +0000873.BR http://wiki.opengraphics.org .
Carl-Daniel Hailfinger8541d232012-02-16 21:00:27 +0000874.SS
875.BR "linux_spi " programmer
876You have to specify the SPI controller to use with the
877.sp
878.B " flashrom \-p linux_spi:dev=/dev/spidevX.Y"
879.sp
880syntax where
881.B /dev/spidevX.Y
882is the Linux device node for your SPI controller.
883.sp
Stefan Tauner0554ca52013-07-25 22:54:25 +0000884In case the device supports it, you can set the SPI clock frequency with the optional
885.B spispeed
886parameter. The frequency is parsed as kilohertz.
887Example that sets the frequency to 8 MHz:
888.sp
889.B " flashrom \-p linux_spi:dev=/dev/spidevX.Y,spispeed=8000"
890.sp
Carl-Daniel Hailfinger8541d232012-02-16 21:00:27 +0000891Please note that the linux_spi driver only works on Linux.
Carl-Daniel Hailfinger0b9af362012-07-21 16:56:04 +0000892.SH EXAMPLES
893To back up and update your BIOS, run
894.sp
895.B flashrom -p internal -r backup.rom -o backuplog.txt
896.br
897.B flashrom -p internal -w newbios.rom -o writelog.txt
898.sp
899Please make sure to copy backup.rom to some external media before you try
900to write. That makes offline recovery easier.
901.br
902If writing fails and flashrom complains about the chip being in an unknown
903state, you can try to restore the backup by running
904.sp
905.B flashrom -p internal -w backup.rom -o restorelog.txt
906.sp
907If you encounter any problems, please contact us and supply
908backuplog.txt, writelog.txt and restorelog.txt. See section
909.B BUGS
910for contact info.
Peter Stuge42688e52009-01-26 02:20:56 +0000911.SH EXIT STATUS
Niklas Söderlund2d8b7ef2013-09-13 19:19:25 +0000912flashrom exits with 0 on success, 1 on most failures but with 3 if a call to mmap() fails.
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000913.SH REQUIREMENTS
914flashrom needs different access permissions for different programmers.
915.sp
916.B internal
917needs raw memory access, PCI configuration space access, raw I/O port
918access (x86) and MSR access (x86).
919.sp
Jonathan Kollasch7f0f3fa2014-06-01 10:26:23 +0000920.B atavia
921needs PCI configuration space access.
922.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000923.BR nic3com ", " nicrealtek " and " nicnatsemi "
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000924need PCI configuration space read access and raw I/O port access.
925.sp
926.B atahpt
927needs PCI configuration space access and raw I/O port access.
928.sp
Kyösti Mälkki72d42f82014-06-01 23:48:31 +0000929.BR gfxnvidia ", " drkaiser " and " it8212
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000930need PCI configuration space access and raw memory access.
931.sp
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000932.B rayer_spi
933needs raw I/O port access.
934.sp
Ricardo Ribalda Delgado2a41f0a2014-07-28 20:35:21 +0000935.BR satasii ", " nicintel ", " nicintel_eeprom " and " nicintel_spi
936need PCI configuration space read access and raw memory access.
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000937.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000938.B satamv
939needs PCI configuration space read access, raw I/O port access and raw memory
940access.
941.sp
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000942.B serprog
943needs TCP access to the network or userspace access to a serial port.
944.sp
945.B buspirate_spi
946needs userspace access to a serial port.
947.sp
James Lairdc60de0e2013-03-27 13:00:23 +0000948.BR dediprog ", " ft2232_spi " and " usbblaster_spi
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000949need access to the USB device via libusb.
950.sp
951.B dummy
952needs no access permissions at all.
953.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000954.BR internal ", " nic3com ", " nicrealtek ", " nicnatsemi ", "
Jonathan Kollasch7f0f3fa2014-06-01 10:26:23 +0000955.BR gfxnvidia ", " drkaiser ", " satasii ", " satamv ", " atahpt" and " atavia
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000956have to be run as superuser/root, and need additional raw access permission.
957.sp
James Lairdc60de0e2013-03-27 13:00:23 +0000958.BR serprog ", " buspirate_spi ", " dediprog ", " usbblaster_spi " and " ft2232_spi
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000959can be run as normal user on most operating systems if appropriate device
960permissions are set.
961.sp
Mark Marshall90021f22010-12-03 14:48:11 +0000962.B ogp
963needs PCI configuration space read access and raw memory access.
964.sp
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000965On OpenBSD, you can obtain raw access permission by setting
Uwe Hermann941a2732011-07-25 21:12:57 +0000966.B "securelevel=-1"
967in
968.B "/etc/rc.securelevel"
969and rebooting, or rebooting into single user mode.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000970.SH BUGS
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000971Please report any bugs to the flashrom mailing list at
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000972.B "<flashrom@flashrom.org>"
973.sp
974We recommend to subscribe first at
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000975.sp
976.B " http://www.flashrom.org/mailman/listinfo/flashrom"
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000977.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000978Many of the developers communicate via the
979.B "#flashrom"
980IRC channel on
981.BR chat.freenode.net .
982You are welcome to join and ask questions, send us bug and success reports there
Stefan Taunereb582572012-09-21 12:52:50 +0000983too. Please provide a way to contact you later (e.g.\& a mail address) and be
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000984patient if there is no immediate reaction. Also, we provide a pastebin service
985at
Stefan Tauner352e50b2013-02-22 15:58:45 +0000986.nh
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000987.B http://paste.flashrom.org
Stefan Taunereb582572012-09-21 12:52:50 +0000988that is very useful when you want to share logs etc.\& without spamming the
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000989channel.
990.SS
991.B Laptops
992.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000993Using flashrom on laptops is dangerous and may easily make your hardware
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000994unusable. flashrom will attempt to detect if it is running on a laptop and abort
995immediately for safety reasons. Please see the detailed discussion of this topic
996and associated flashrom options in the
997.B Laptops
998paragraph in the
999.B internal programmer
1000subsection of the
Stefan Tauner6697f712014-08-06 15:09:15 +00001001.B PROGRAMMER-SPECIFIC INFORMATION
Stefan Tauner352e50b2013-02-22 15:58:45 +00001002section and the information in our wiki at
1003.BR "http://www.flashrom.org/Laptops " .
Daniel Lenski65922a32012-02-15 23:40:23 +00001004.SS
1005One-time programmable (OTP) memory and unique IDs
1006.sp
1007Some flash chips contain OTP memory often denoted as "security registers".
1008They usually have a capacity in the range of some bytes to a few hundred
Stefan Taunereb582572012-09-21 12:52:50 +00001009bytes and can be used to give devices unique IDs etc. flashrom is not able
Daniel Lenski65922a32012-02-15 23:40:23 +00001010to read or write these memories and may therefore not be able to duplicate a
1011chip completely. For chip types known to include OTP memories a warning is
1012printed when they are detected.
1013.sp
1014Similar to OTP memories are unique, factory programmed, unforgeable IDs.
1015They are not modifiable by the user at all.
Stefan Taunerac54fbe2011-07-21 19:52:00 +00001016.SH LICENSE
Stefan Reinauer261144c2006-07-27 23:29:02 +00001017.B flashrom
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001018is covered by the GNU General Public License (GPL), version 2. Some files are
1019additionally available under the GPL (version 2, or any later version).
Stefan Reinauer261144c2006-07-27 23:29:02 +00001020.SH COPYRIGHT
Stefan Reinauer261144c2006-07-27 23:29:02 +00001021.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001022Please see the individual files.
Stefan Reinauer261144c2006-07-27 23:29:02 +00001023.SH AUTHORS
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001024Andrew Morgan
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001025.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001026Carl-Daniel Hailfinger
1027.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001028Claus Gindhart
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001029.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001030David Borg
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001031.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001032David Hendricks
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001033.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001034Dominik Geyer
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001035.br
Stefan Reinaueredc61882010-01-03 14:40:30 +00001036Eric Biederman
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001037.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001038Giampiero Giancipoli
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001039.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001040Helge Wagner
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001041.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001042Idwer Vollering
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001043.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001044Joe Bao
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001045.br
Stefan Taunerc0aaf952011-05-19 02:58:17 +00001046Joerg Fischer
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001047.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001048Joshua Roys
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001049.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001050Luc Verhaegen
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001051.br
Carl-Daniel Hailfinger451dc802009-05-01 11:00:39 +00001052Li-Ta Lo
1053.br
Mark Marshall90021f22010-12-03 14:48:11 +00001054Mark Marshall
1055.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001056Markus Boas
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001057.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001058Mattias Mattsson
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001059.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001060Michael Karcher
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +00001061.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001062Nikolay Petukhov
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001063.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001064Patrick Georgi
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001065.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001066Peter Lemenkov
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001067.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001068Peter Stuge
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001069.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001070Reinder E.N. de Haan
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001071.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001072Ronald G. Minnich
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001073.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001074Ronald Hoogenboom
Stefan Reinauer261144c2006-07-27 23:29:02 +00001075.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001076Sean Nelson
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +00001077.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001078Stefan Reinauer
Stefan Reinauer261144c2006-07-27 23:29:02 +00001079.br
Uwe Hermann68b9cca2011-06-15 23:44:52 +00001080Stefan Tauner
1081.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001082Stefan Wildemann
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001083.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001084Stephan Guilloux
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +00001085.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001086Steven James
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001087.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001088Uwe Hermann
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001089.br
Stefan Reinaueredc61882010-01-03 14:40:30 +00001090Wang Qingpei
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +00001091.br
Stefan Reinaueredc61882010-01-03 14:40:30 +00001092Yinghai Lu
Stefan Reinauerf8337dd2006-08-03 10:49:09 +00001093.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +00001094some others, please see the flashrom svn changelog for details.
1095.br
Uwe Hermann68b9cca2011-06-15 23:44:52 +00001096All authors can be reached via email at <flashrom@flashrom.org>.
Stefan Reinauer261144c2006-07-27 23:29:02 +00001097.PP
Stefan Taunerac54fbe2011-07-21 19:52:00 +00001098This manual page was written by Uwe Hermann <uwe@hermann-uwe.de>,
1099Carl-Daniel Hailfinger and others.
Uwe Hermann42eb17f2008-01-18 17:48:51 +00001100It is licensed under the terms of the GNU GPL (version 2 or later).