blob: 90afced623db0ee604658de0ff049cf1496550b4 [file] [log] [blame]
Nathan Laredo21541a62012-12-24 22:07:36 +00001.TH FLASHROM 8 "Dec, 2012"
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
164.BR http://www.flashrom.org/ .
165Please note that MediaWiki output is not compiled in by default.
Uwe Hermann20a293f2009-06-19 10:42:43 +0000166.TP
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000167.B "\-p, \-\-programmer <name>[:parameter[,parameter[,parameter]]]"
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000168Specify the programmer device. This is mandatory for all operations
169involving any chip access (probe/read/write/...). Currently supported are:
Carl-Daniel Hailfingerce986772009-05-09 00:27:07 +0000170.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000171.BR "* internal" " (default, for in-system flashing in the mainboard)"
172.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000173.BR "* dummy" " (virtual programmer for testing flashrom)"
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000174.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000175.BR "* nic3com" " (for flash ROMs on 3COM network cards)"
176.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000177.BR "* nicrealtek" " (for flash ROMs on Realtek and SMC 1211 network cards)"
Uwe Hermann829ed842010-05-24 17:39:14 +0000178.sp
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000179.BR "* nicnatsemi" " (for flash ROMs on National Semiconductor DP838* network \
180cards)"
181.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000182.BR "* nicintel" " (for parallel flash ROMs on Intel 10/100Mbit network cards)
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000183.sp
Uwe Hermann2bc98f62009-09-30 18:29:55 +0000184.BR "* gfxnvidia" " (for flash ROMs on NVIDIA graphics cards)"
185.sp
TURBO Jb0912c02009-09-02 23:00:46 +0000186.BR "* drkaiser" " (for flash ROMs on Dr. Kaiser PC-Waechter PCI cards)"
187.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000188.BR "* satasii" " (for flash ROMs on Silicon Image SATA/IDE controllers)"
189.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000190.BR "* satamv" " (for flash ROMs on Marvell SATA controllers)"
191.sp
Uwe Hermannddd5c9e2010-02-21 21:17:00 +0000192.BR "* atahpt" " (for flash ROMs on Highpoint ATA/RAID controllers)"
193.sp
Ilya A. Volynets-Evenbakh2c714ab2012-09-26 00:47:09 +0000194.BR "* ft2232_spi" " (for SPI flash ROMs attached to an FT2232/FT4232H/FT232H family \
Uwe Hermann314cfba2011-07-28 19:23:09 +0000195based USB SPI programmer), including the DLP Design DLP-USB1232H, \
196FTDI FT2232H Mini-Module, FTDI FT4232H Mini-Module, openbiosprog-spi, Amontec \
Steve Markgraf0528b7f2011-08-12 01:19:32 +0000197JTAGkey/JTAGkey-tiny/JTAGkey-2, Dangerous Prototypes Bus Blaster, \
Samir Ibradžić7189a5f2011-10-20 23:14:10 +0000198Olimex ARM-USB-TINY/-H, Olimex ARM-USB-OCD/-H, TIAO/DIYGADGET USB
199Multi-Protocol Adapter (TUMPA), and GOEPEL PicoTAP.
Paul Fox05dfbe62009-06-16 21:08:06 +0000200.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000201.BR "* serprog" " (for flash ROMs attached to a programmer speaking serprog), \
202including AVR flasher by Urja Rannikko, AVR flasher by eightdot, \
203Arduino Mega flasher by fritz, InSystemFlasher by Juhana Helovuo, and \
204atmegaXXu2-flasher by Stefan Tauner."
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000205.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000206.BR "* buspirate_spi" " (for SPI flash ROMs attached to a Bus Pirate)"
Carl-Daniel Hailfingerd5b28fa2009-11-24 18:27:10 +0000207.sp
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000208.BR "* dediprog" " (for SPI flash ROMs attached to a Dediprog SF100)"
209.sp
Carl-Daniel Hailfingerae418d82011-09-12 06:17:06 +0000210.BR "* rayer_spi" " (for SPI flash ROMs attached to a RayeR parport "
211or Xilinx DLC5 compatible cable)
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000212.sp
Michael Karchere5449392012-05-05 20:53:59 +0000213.BR "* pony_spi" " (for SPI flash ROMs attached to a SI-Prog serial port "
214bitbanging adapter)
215.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000216.BR "* nicintel_spi" " (for SPI flash ROMs on Intel Gigabit network cards)"
Idwer Vollering004f4b72010-09-03 18:21:21 +0000217.sp
Uwe Hermann314cfba2011-07-28 19:23:09 +0000218.BR "* ogp_spi" " (for SPI flash ROMs on Open Graphics Project graphics card)"
Mark Marshall90021f22010-12-03 14:48:11 +0000219.sp
Carl-Daniel Hailfinger8541d232012-02-16 21:00:27 +0000220.BR "* linux_spi" " (for SPI flash ROMs accessible via /dev/spidevX.Y on Linux)"
221.sp
Michael Karchere5eafb22010-03-07 12:11:08 +0000222Some programmers have optional or mandatory parameters which are described
223in detail in the
224.B PROGRAMMER SPECIFIC INFO
225section. Support for some programmers can be disabled at compile time.
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000226.B "flashrom \-h"
Michael Karchere5eafb22010-03-07 12:11:08 +0000227lists all supported programmers.
228.TP
229.B "\-h, \-\-help"
230Show a help text and exit.
231.TP
Carl-Daniel Hailfinger0b9af362012-07-21 16:56:04 +0000232.B "\-o, \-\-output <logfile>"
233Save the full debug log to
234.BR <logfile> .
235If the file already exists, it will be overwritten. This is the recommended
236way to gather logs from flashrom because they will be verbose even if the
237on-screen messages are not verbose.
238.TP
Michael Karchere5eafb22010-03-07 12:11:08 +0000239.B "\-R, \-\-version"
240Show version information and exit.
241.SH PROGRAMMER SPECIFIC INFO
242Some programmer drivers accept further parameters to set programmer-specific
Uwe Hermann4e3d0b32010-03-25 23:18:41 +0000243parameters. These parameters are separated from the programmer name by a
Michael Karchere5eafb22010-03-07 12:11:08 +0000244colon. While some programmers take arguments at fixed positions, other
245programmers use a key/value interface in which the key and value is separated
246by an equal sign and different pairs are separated by a comma or a colon.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000247.SS
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000248.BR "internal " programmer
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000249.TP
250.B Board Enables
251.sp
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000252Some mainboards require to run mainboard specific code to enable flash erase
253and write support (and probe support on old systems with parallel flash).
254The mainboard brand and model (if it requires specific code) is usually
255autodetected using one of the following mechanisms: If your system is
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000256running coreboot, the mainboard type is determined from the coreboot table.
257Otherwise, the mainboard is detected by examining the onboard PCI devices
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000258and possibly DMI info. If PCI and DMI do not contain information to uniquely
Carl-Daniel Hailfinger2d927fb2012-01-04 00:48:27 +0000259identify the mainboard (which is the exception), or if you want to override
260the detected mainboard model, you can specify the mainboard using the
261.sp
Stefan Taunerb4e06bd2012-08-20 00:24:22 +0000262.B " flashrom \-p internal:mainboard=<vendor>:<board>"
Carl-Daniel Hailfinger2d927fb2012-01-04 00:48:27 +0000263syntax.
264.sp
265See the 'Known boards' or 'Known laptops' section in the output
266of 'flashrom \-L' for a list of boards which require the specification of
267the board name, if no coreboot table is found.
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000268.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000269Some of these board-specific flash enabling functions (called
270.BR "board enables" )
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000271in flashrom have not yet been tested. If your mainboard is detected needing
272an untested board enable function, a warning message is printed and the
273board enable is not executed, because a wrong board enable function might
274cause the system to behave erratically, as board enable functions touch the
275low-level internals of a mainboard. Not executing a board enable function
276(if one is needed) might cause detection or erasing failure. If your board
277protects only part of the flash (commonly the top end, called boot block),
278flashrom might encounter an error only after erasing the unprotected part,
279so running without the board-enable function might be dangerous for erase
280and write (which includes erase).
281.sp
282The suggested procedure for a mainboard with untested board specific code is
283to first try to probe the ROM (just invoke flashrom and check that it
284detects your flash chip type) without running the board enable code (i.e.
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000285without any parameters). If it finds your chip, fine. Otherwise, retry
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000286probing your chip with the board-enable code running, using
287.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000288.B " flashrom \-p internal:boardenable=force"
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000289.sp
290If your chip is still not detected, the board enable code seems to be broken
291or the flash chip unsupported. Otherwise, make a backup of your current ROM
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000292contents (using
293.BR \-r )
294and store it to a medium outside of your computer, like
295a USB drive or a network share. If you needed to run the board enable code
Stefan Taunereb582572012-09-21 12:52:50 +0000296already for probing, use it for reading too.
297If reading succeeds and the contens of the read file look legit you can try to write the new image.
298You should enable the board enable code in any case now, as it
Michael Karcher7f0c3ec2010-03-07 22:29:28 +0000299has been written because it is known that writing/erasing without the board
300enable is going to fail. In any case (success or failure), please report to
301the flashrom mailing list, see below.
302.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000303.TP
304.B Coreboot
305.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000306On systems running coreboot, flashrom checks whether the desired image matches
307your mainboard. This needs some special board ID to be present in the image.
308If flashrom detects that the image you want to write and the current board
309do not match, it will refuse to write the image unless you specify
310.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000311.B " flashrom \-p internal:boardmismatch=force"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000312.TP
313.B ITE IT87 Super I/O
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000314.sp
Carl-Daniel Hailfinger01f3ef42010-03-25 02:50:40 +0000315If your mainboard uses an ITE IT87 series Super I/O for LPC<->SPI flash bus
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000316translation, flashrom should autodetect that configuration. If you want to
317set the I/O base port of the IT87 series SPI controller manually instead of
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000318using the value provided by the BIOS, use the
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +0000319.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000320.B " flashrom \-p internal:it87spiport=portnum"
321.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000322syntax where
323.B portnum
324is the I/O port number (must be a multiple of 8). In the unlikely case
325flashrom doesn't detect an active IT87 LPC<->SPI bridge, please send a bug
326report so we can diagnose the problem.
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000327.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000328.TP
329.B Intel chipsets
330.sp
Stefan Tauner50e7c602011-11-08 10:55:54 +0000331If you have an Intel chipset with an ICH8 or later southbridge with SPI flash
Stefan Taunereb582572012-09-21 12:52:50 +0000332attached, and if a valid descriptor was written to it (e.g.\& by the vendor), the
Stefan Tauner50e7c602011-11-08 10:55:54 +0000333chipset provides an alternative way to access the flash chip(s) named
334.BR "Hardware Sequencing" .
335It is much simpler than the normal access method (called
336.BR "Software Sequencing" "),"
337but does not allow the software to choose the SPI commands to be sent.
338You can use the
339.sp
340.B " flashrom \-p internal:ich_spi_mode=value"
341.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000342syntax where
343.BR "value " "can be"
Stefan Tauner50e7c602011-11-08 10:55:54 +0000344.BR auto ", " swseq " or " hwseq .
345By default
346.RB "(or when setting " ich_spi_mode=auto )
Stefan Taunereb582572012-09-21 12:52:50 +0000347the module tries to use swseq and only activates hwseq if need be (e.g.\& if
Stefan Tauner50e7c602011-11-08 10:55:54 +0000348important opcodes are inaccessible due to lockdown; or if more than one flash
349chip is attached). The other options (swseq, hwseq) select the respective mode
350(if possible).
351.sp
Stefan Tauner5210e722012-02-16 01:13:00 +0000352ICH8 and later southbridges may also have locked address ranges of different
353kinds if a valid descriptor was written to it. The flash address space is then
354partitioned in multiple so called "Flash Regions" containing the host firmware,
355the ME firmware and so on respectively. The flash descriptor can also specify up
356to 5 so called "Protected Regions", which are freely chosen address ranges
357independent from the aforementioned "Flash Regions". All of them can be write
358and/or read protected individually. If flashrom detects such a lock it will
359disable write support unless the user forces it with the
360.sp
361.B " flashrom \-p internal:ich_spi_force=yes"
362.sp
363syntax. If this leads to erase or write accesses to the flash it would most
364probably bring it into an inconsistent and unbootable state and we will not
365provide any support in such a case.
366.sp
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000367If you have an Intel chipset with an ICH6 or later southbridge and if you want
368to set specific IDSEL values for a non-default flash chip or an embedded
369controller (EC), you can use the
370.sp
371.B " flashrom \-p internal:fwh_idsel=value"
372.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000373syntax where
374.B value
375is the 48-bit hexadecimal raw value to be written in the
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000376IDSEL registers of the Intel southbridge. The upper 32 bits use one hex digit
377each per 512 kB range between 0xffc00000 and 0xffffffff, and the lower 16 bits
378use one hex digit each per 1024 kB range between 0xff400000 and 0xff7fffff.
379The rightmost hex digit corresponds with the lowest address range. All address
380ranges have a corresponding sister range 4 MB below with identical IDSEL
381settings. The default value for ICH7 is given in the example below.
382.sp
383Example:
384.B "flashrom \-p internal:fwh_idsel=0x001122334567"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000385.TP
386.B Laptops
Carl-Daniel Hailfinger46fa0682011-07-25 22:44:09 +0000387.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000388Using flashrom on laptops is dangerous and may easily make your hardware
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000389unusable (see also the
390.B BUGS
391section). The embedded controller (EC) in these
392machines often interacts badly with flashing.
393.B http://www.flashrom.org/Laptops
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000394has more information. For example the EC firmware sometimes resides on the same
395flash chip as the host firmware. While flashrom tries to change the contents of
396that memory the EC might need to fetch new instructions or data from it and
397could stop working correctly. Probing for and reading from the chip may also
398irritate your EC and cause fan failure, backlight failure, sudden poweroff, and
399other nasty effects. flashrom will attempt to detect if it is running on a
400laptop and abort immediately for safety reasons if it clearly identifies the
401host computer as one. If you want to proceed anyway at your own risk, use
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000402.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000403.B " flashrom \-p internal:laptop=force_I_want_a_brick"
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000404.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000405We will not help you if you force flashing on a laptop because this is a really
406dumb idea.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000407.sp
408You have been warned.
409.sp
410Currently we rely on the chassis type encoded in the DMI/SMBIOS data to detect
411laptops. Some vendors did not implement those bits correctly or set them to
412generic and/or dummy values. flashrom will then issue a warning and bail out
413like above. In this case you can use
414.sp
415.B " flashrom \-p internal:laptop=this_is_not_a_laptop"
416.sp
417to tell flashrom (at your own risk) that it does not running on a laptop.
418.SS
Michael Karchere5eafb22010-03-07 12:11:08 +0000419.BR "dummy " programmer
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000420The dummy programmer operates on a buffer in memory only. It provides a safe
421and fast way to test various aspects of flashrom and is mainly used in
422development and while debugging.
423.sp
424It is able to emulate some chips to a certain degree (basic
425identify/read/erase/write operations work).
426.sp
Michael Karchere5eafb22010-03-07 12:11:08 +0000427An optional parameter specifies the bus types it
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000428should support. For that you have to use the
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000429.sp
430.B " flashrom \-p dummy:bus=[type[+type[+type]]]"
431.sp
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000432syntax where
433.B type
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000434can be
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000435.BR parallel ", " lpc ", " fwh ", " spi
436in any order. If you specify bus without type, all buses will be disabled.
437If you do not specify bus, all buses will be enabled.
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000438.sp
439Example:
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000440.B "flashrom \-p dummy:bus=lpc+fwh"
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000441.sp
442The dummy programmer supports flash chip emulation for automated self-tests
443without hardware access. If you want to emulate a flash chip, use the
444.sp
445.B " flashrom \-p dummy:emulate=chip"
446.sp
447syntax where
448.B chip
449is one of the following chips (please specify only the chip name, not the
450vendor):
451.sp
452.RB "* ST " M25P10.RES " SPI flash chip (RES, page write)"
453.sp
454.RB "* SST " SST25VF040.REMS " SPI flash chip (REMS, byte write)"
455.sp
456.RB "* SST " SST25VF032B " SPI flash chip (RDID, AAI write)"
457.sp
Stefan Tauner0b9df972012-05-07 22:12:16 +0000458.RB "* Macronix " MX25L6436 " SPI flash chip (RDID, SFDP)"
459.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000460Example:
461.B "flashrom -p dummy:emulate=SST25VF040.REMS"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000462.TP
463.B Persistent images
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000464.sp
465If you use flash chip emulation, flash image persistence is available as well
466by using the
467.sp
468.B " flashrom \-p dummy:emulate=chip,image=image.rom"
469.sp
470syntax where
471.B image.rom
472is the file where the simulated chip contents are read on flashrom startup and
473where the chip contents on flashrom shutdown are written to.
474.sp
475Example:
476.B "flashrom -p dummy:emulate=M25P10.RES,image=dummy.bin"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000477.TP
478.B SPI write chunk size
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000479.sp
480If you use SPI flash chip emulation for a chip which supports SPI page write
481with the default opcode, you can set the maximum allowed write chunk size with
482the
483.sp
484.B " flashrom \-p dummy:emulate=chip,spi_write_256_chunksize=size"
485.sp
486syntax where
487.B size
Stefan Taunereb582572012-09-21 12:52:50 +0000488is the number of bytes (min.\& 1, max.\& 256).
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000489.sp
490Example:
491.sp
492.B " flashrom -p dummy:emulate=M25P10.RES,spi_write_256_chunksize=5"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000493.TP
494.B SPI blacklist
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000495.sp
496To simulate a programmer which refuses to send certain SPI commands to the
497flash chip, you can specify a blacklist of SPI commands with the
498.sp
499.B " flashrom -p dummy:spi_blacklist=commandlist"
500.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000501syntax where
502.B commandlist
503is a list of two-digit hexadecimal representations of
Stefan Taunereb582572012-09-21 12:52:50 +0000504SPI commands. If commandlist is e.g.\& 0302, flashrom will behave as if the SPI
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000505controller refuses to run command 0x03 (READ) and command 0x02 (WRITE).
506commandlist may be up to 512 characters (256 commands) long.
507Implementation note: flashrom will detect an error during command execution.
508.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000509.TP
510.B SPI ignorelist
511.sp
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000512To simulate a flash chip which ignores (doesn't support) certain SPI commands,
513you can specify an ignorelist of SPI commands with the
514.sp
515.B " flashrom -p dummy:spi_ignorelist=commandlist"
516.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000517syntax where
518.B commandlist
519is a list of two-digit hexadecimal representations of
Stefan Taunereb582572012-09-21 12:52:50 +0000520SPI commands. If commandlist is e.g.\& 0302, the emulated flash chip will ignore
Carl-Daniel Hailfinger1b83be52012-02-08 23:28:54 +0000521command 0x03 (READ) and command 0x02 (WRITE). commandlist may be up to 512
522characters (256 commands) long.
523Implementation note: flashrom won't detect an error during command execution.
Stefan Tauner5e695ab2012-05-06 17:03:40 +0000524.sp
525.TP
526.B SPI status register
527.sp
528You can specify the initial content of the chip's status register with the
529.sp
530.B " flashrom -p dummy:spi_status=content"
531.sp
Carl-Daniel Hailfinger4e3391f2012-07-22 12:01:43 +0000532syntax where
533.B content
534is an 8-bit hexadecimal value.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000535.SS
Sergey Lichack98f47102012-08-27 01:24:15 +0000536.BR "nic3com" , " nicrealtek" , " nicnatsemi" , " nicintel\
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000537" , " nicintel_spi" , " gfxnvidia" , " ogp_spi" , " drkaiser" , " satasii\
538" , " satamv" ", and " atahpt " programmers
Michael Karchere5eafb22010-03-07 12:11:08 +0000539These programmers have an option to specify the PCI address of the card
540your want to use, which must be specified if more than one card supported
541by the selected programmer is installed in your system. The syntax is
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000542.sp
543.BR " flashrom \-p xxxx:pci=bb:dd.f" ,
544.sp
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000545where
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000546.B xxxx
547is the name of the programmer
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000548.B bb
549is the PCI bus number,
550.B dd
551is the PCI device number, and
552.B f
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000553is the PCI function number of the desired device.
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000554.sp
555Example:
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000556.B "flashrom \-p nic3com:pci=05:04.0"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000557.SS
Carl-Daniel Hailfinger71127722010-05-31 15:27:27 +0000558.BR "ft2232_spi " programmer
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000559An optional parameter specifies the controller
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000560type and channel/interface/port it should support. For that you have to use the
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000561.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000562.B " flashrom \-p ft2232_spi:type=model,port=interface"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000563.sp
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000564syntax where
565.B model
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000566can be
Ilya A. Volynets-Evenbakh2c714ab2012-09-26 00:47:09 +0000567.BR 2232H ", " 4232H ", " 232H ", " jtagkey ", " busblaster ", " openmoko ", " \
Uwe Hermann836b26a2011-10-14 20:33:14 +0000568arm-usb-tiny ", " arm-usb-tiny-h ", " arm-usb-ocd ", " arm-usb-ocd-h \
Samir Ibradžić7189a5f2011-10-20 23:14:10 +0000569", " tumpa ", or " picotap
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000570and
571.B interface
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000572can be
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000573.BR A ", " B ", " C ", or " D .
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000574The default model is
575.B 4232H
576and the default interface is
Stefan Taunerfbc71ac2012-09-26 00:46:02 +0000577.BR A .
Samir Ibradžićb482c6d2012-05-15 22:58:19 +0000578.sp
Shik Chen14fbc4b2012-09-17 00:40:54 +0000579If there is more than one ft2232_spi-compatible device connected, you can select which one should be used by
580specifying its serial number with the
581.sp
582.B " flashrom \-p ft2232_spi:serial=number"
583.sp
584syntax where
585.B number
586is the serial number of the device (which can be found for example in the output of lsusb -v).
587.sp
Samir Ibradžićb482c6d2012-05-15 22:58:19 +0000588All models supported by the ft2232_spi driver can configure the SPI clock rate by setting a divisor. The
589expressible divisors are all even numbers between 2 and 2^17 (=131072) resulting in SPI clock frequencies of
5906 MHz down to about 92 Hz for 12 MHz inputs. The default divisor is set to 2, but you can use another one by
591specifying the optional
592.B divisor
593parameter with the
594.sp
595.B " flashrom \-p ft2232_spi:divisor=div"
596.sp
597syntax.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000598.SS
Michael Karchere5eafb22010-03-07 12:11:08 +0000599.BR "serprog " programmer
600A mandatory parameter specifies either a serial
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000601device/baud combination or an IP/port combination for communication with the
Michael Karchere5eafb22010-03-07 12:11:08 +0000602programmer. In the device/baud combination, the device has to start with a
603slash. For serial, you have to use the
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000604.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000605.B " flashrom \-p serprog:dev=/dev/device:baud"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000606.sp
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000607syntax and for IP, you have to use
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000608.sp
Carl-Daniel Hailfinger744132a2010-07-06 09:55:48 +0000609.B " flashrom \-p serprog:ip=ipaddr:port"
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000610.sp
Stefan Taunerb98f6eb2012-08-13 16:33:04 +0000611instead. In case the device supports it, you can set the SPI clock frequency
612with the optional
613.B spispeed
614parameter. The frequency is parsed as Hertz, unless an
615.BR M ", or " k
616suffix is given, then megahertz or kilohertz are used respectively.
617Example that sets the frequency to 2 MHz:
618.sp
619.B "flashrom \-p serprog:dev=/dev/device:baud,spispeed=2M"
620.sp
621More information about serprog is available in
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000622.B serprog-protocol.txt
623in the source distribution.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000624.SS
Carl-Daniel Hailfinger71127722010-05-31 15:27:27 +0000625.BR "buspirate_spi " programmer
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000626A required
627.B dev
628parameter specifies the Bus Pirate device node and an optional
629.B spispeed
630parameter specifies the frequency of the SPI bus. The parameter
Michael Karchere5eafb22010-03-07 12:11:08 +0000631delimiter is a comma. Syntax is
Carl-Daniel Hailfingerdfade102009-08-18 23:51:22 +0000632.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000633.B " flashrom \-p buspirate_spi:dev=/dev/device,spispeed=frequency"
Michael Karchere5eafb22010-03-07 12:11:08 +0000634.sp
Carl-Daniel Hailfingerd5b28fa2009-11-24 18:27:10 +0000635where
636.B frequency
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000637can be
638.BR 30k ", " 125k ", " 250k ", " 1M ", " 2M ", " 2.6M ", " 4M " or " 8M
Michael Karchere5eafb22010-03-07 12:11:08 +0000639(in Hz). The default is the maximum frequency of 8 MHz.
Brian Salcedo30dfdba2013-01-03 20:44:30 +0000640.sp
641An optional pullups parameter specifies the use of the Bus Pirate internal pull-up resistors. This may be
642needed if you are working with a flash ROM chip that you have physically removed from the board. Syntax is
643.sp
644.B " flashrom -p buspirate_spi:pullups=state"
645.sp
646where
647.B state
648can be
649.BR on " or " off .
650More information about the Bus Pirate pull-up resistors and their purpose is available at
651.nh
652.BR "http://dangerousprototypes.com/docs/Practical_guide_to_Bus_Pirate_pull-up_resistors " .
653Only the external supply voltage (Vpu) is supported as of this writing.
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000654.SS
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000655.BR "dediprog " programmer
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000656An optional
657.B voltage
658parameter specifies the voltage the Dediprog should use. The default unit is
659Volt if no unit is specified. You can use
660.BR mV ", " milliVolt ", " V " or " Volt
661as unit specifier. Syntax is
662.sp
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000663.B " flashrom \-p dediprog:voltage=value"
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000664.sp
665where
666.B value
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000667can be
Carl-Daniel Hailfingerc2441382010-11-09 22:00:31 +0000668.BR 0V ", " 1.8V ", " 2.5V ", " 3.5V
669or the equivalent in mV.
Nathan Laredo21541a62012-12-24 22:07:36 +0000670.sp
671An optional
672.B device
673parameter specifies which of multiple connected Dediprog devices should be used.
674Please be aware that the order depends on libusb's usb_get_busses() function and that the numbering starts
675at 0.
676Usage example to select the second device:
677.sp
678.B " flashrom \-p dediprog:device=1"
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000679.SS
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000680.BR "rayer_spi " programmer
Carl-Daniel Hailfinger37c42522010-10-05 19:19:48 +0000681The default I/O base address used for the parallel port is 0x378 and you can use
682the optional
683.B iobase
684parameter to specify an alternate base I/O address with the
685.sp
686.B " flashrom \-p rayer_spi:iobase=baseaddr"
687.sp
688syntax where
689.B baseaddr
690is base I/O port address of the parallel port, which must be a multiple of
691four. Make sure to not forget the "0x" prefix for hexadecimal port addresses.
692.sp
Carl-Daniel Hailfingerae418d82011-09-12 06:17:06 +0000693The default cable type is the RayeR cable. You can use the optional
694.B type
695parameter to specify the cable type with the
696.sp
697.B " flashrom \-p rayer_spi:type=model"
698.sp
699syntax where
700.B model
701can be
702.BR rayer " for the RayeR cable or " xilinx " for the Xilinx Parallel Cable III
703(DLC 5).
704.sp
705More information about the RayeR hardware is available at
706.BR "http://rayer.ic.cz/elektro/spipgm.htm " .
707The schematic of the Xilinx DLC 5 was published at
708.BR "http://www.xilinx.com/itp/xilinx4/data/docs/pac/appendixb.html " .
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000709.SS
Michael Karchere5449392012-05-05 20:53:59 +0000710.BR "pony_spi " programmer
711The serial port (like /dev/ttyS0, /dev/ttyUSB0 on Linux or COM3 on windows) is
712specified using the mandatory
Stefan Taunere34e3e82013-01-01 00:06:51 +0000713.B dev
Michael Karchere5449392012-05-05 20:53:59 +0000714parameter. The adapter type is selectable between SI-Prog (used for
715SPI devices with PonyProg 2000) or a custom made serial bitbanging programmer
716named "serbang". The optional
Stefan Taunere34e3e82013-01-01 00:06:51 +0000717.B type
Michael Karchere5449392012-05-05 20:53:59 +0000718parameter accepts the values "si_prog" (default) or "serbang".
719.sp
720Information about the SI-Prog adapter can be found at
721.BR "http://www.lancos.com/siprogsch.html " .
722.sp
723An example call to flashrom is
724.sp
725.B " flashrom \-p pony_spi:dev=/dev/ttyS0,type=serbang"
726.sp
727Please note that while USB-to-serial adapters work under certain circumstances,
728this slows down operation considerably.
729.SS
Mark Marshall90021f22010-12-03 14:48:11 +0000730.BR "ogp_spi " programmer
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000731The flash ROM chip to access must be specified with the
Mark Marshall90021f22010-12-03 14:48:11 +0000732.B rom
733parameter.
734.sp
735.B " flashrom \-p ogp_spi:rom=name"
736.sp
737Where
738.B name
739is either
740.B cprom
741or
742.B s3
Stefan Taunere34e3e82013-01-01 00:06:51 +0000743for the configuration ROM and
Mark Marshall90021f22010-12-03 14:48:11 +0000744.B bprom
745or
746.B bios
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000747for the BIOS ROM. If more than one card supported by the ogp_spi programmer
Mark Marshall90021f22010-12-03 14:48:11 +0000748is installed in your system, you have to specify the PCI address of the card
749you want to use with the
750.B pci=
751parameter as explained in the
Stefan Taunere34e3e82013-01-01 00:06:51 +0000752.B nic3com et al.\&
Mark Marshall90021f22010-12-03 14:48:11 +0000753section above.
754.sp
755More information about the hardware is available at
Uwe Hermann941a2732011-07-25 21:12:57 +0000756.BR http://wiki.opengraphics.org .
Carl-Daniel Hailfinger8541d232012-02-16 21:00:27 +0000757.SS
758.BR "linux_spi " programmer
759You have to specify the SPI controller to use with the
760.sp
761.B " flashrom \-p linux_spi:dev=/dev/spidevX.Y"
762.sp
763syntax where
764.B /dev/spidevX.Y
765is the Linux device node for your SPI controller.
766.sp
767Please note that the linux_spi driver only works on Linux.
Carl-Daniel Hailfinger0b9af362012-07-21 16:56:04 +0000768.SH EXAMPLES
769To back up and update your BIOS, run
770.sp
771.B flashrom -p internal -r backup.rom -o backuplog.txt
772.br
773.B flashrom -p internal -w newbios.rom -o writelog.txt
774.sp
775Please make sure to copy backup.rom to some external media before you try
776to write. That makes offline recovery easier.
777.br
778If writing fails and flashrom complains about the chip being in an unknown
779state, you can try to restore the backup by running
780.sp
781.B flashrom -p internal -w backup.rom -o restorelog.txt
782.sp
783If you encounter any problems, please contact us and supply
784backuplog.txt, writelog.txt and restorelog.txt. See section
785.B BUGS
786for contact info.
Peter Stuge42688e52009-01-26 02:20:56 +0000787.SH EXIT STATUS
788flashrom exits with 0 on success, 1 on most failures but with 2 if /dev/mem
789(/dev/xsvc on Solaris) can not be opened and with 3 if a call to mmap() fails.
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000790.SH REQUIREMENTS
791flashrom needs different access permissions for different programmers.
792.sp
793.B internal
794needs raw memory access, PCI configuration space access, raw I/O port
795access (x86) and MSR access (x86).
796.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000797.BR nic3com ", " nicrealtek " and " nicnatsemi "
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000798need PCI configuration space read access and raw I/O port access.
799.sp
800.B atahpt
801needs PCI configuration space access and raw I/O port access.
802.sp
803.BR gfxnvidia " and " drkaiser
804need PCI configuration space access and raw memory access.
805.sp
Carl-Daniel Hailfingere7fdd6e2010-07-21 10:26:01 +0000806.B rayer_spi
807needs raw I/O port access.
808.sp
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000809.B satasii
810needs PCI configuration space read access and raw memory access.
811.sp
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000812.B satamv
813needs PCI configuration space read access, raw I/O port access and raw memory
814access.
815.sp
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000816.B serprog
817needs TCP access to the network or userspace access to a serial port.
818.sp
819.B buspirate_spi
820needs userspace access to a serial port.
821.sp
822.BR dediprog " and " ft2232_spi
823need access to the USB device via libusb.
824.sp
825.B dummy
826needs no access permissions at all.
827.sp
Sergey Lichack98f47102012-08-27 01:24:15 +0000828.BR internal ", " nic3com ", " nicrealtek ", " nicnatsemi ", "
Carl-Daniel Hailfinger9321f062011-07-24 18:41:13 +0000829.BR gfxnvidia ", " drkaiser ", " satasii ", " satamv " and " atahpt
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000830have to be run as superuser/root, and need additional raw access permission.
831.sp
832.BR serprog ", " buspirate_spi ", " dediprog " and " ft2232_spi
833can be run as normal user on most operating systems if appropriate device
834permissions are set.
835.sp
Mark Marshall90021f22010-12-03 14:48:11 +0000836.B ogp
837needs PCI configuration space read access and raw memory access.
838.sp
Carl-Daniel Hailfingerb63b0672010-07-02 17:12:50 +0000839On OpenBSD, you can obtain raw access permission by setting
Uwe Hermann941a2732011-07-25 21:12:57 +0000840.B "securelevel=-1"
841in
842.B "/etc/rc.securelevel"
843and rebooting, or rebooting into single user mode.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000844.SH BUGS
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000845Please report any bugs to the flashrom mailing list at
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000846.B "<flashrom@flashrom.org>"
847.sp
848We recommend to subscribe first at
Uwe Hermann9ff514d2010-06-07 19:41:25 +0000849.sp
850.B " http://www.flashrom.org/mailman/listinfo/flashrom"
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000851.sp
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000852Many of the developers communicate via the
853.B "#flashrom"
854IRC channel on
855.BR chat.freenode.net .
856You are welcome to join and ask questions, send us bug and success reports there
Stefan Taunereb582572012-09-21 12:52:50 +0000857too. Please provide a way to contact you later (e.g.\& a mail address) and be
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000858patient if there is no immediate reaction. Also, we provide a pastebin service
859at
860.B http://paste.flashrom.org
Stefan Taunereb582572012-09-21 12:52:50 +0000861that is very useful when you want to share logs etc.\& without spamming the
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000862channel.
863.SS
864.B Laptops
865.sp
Carl-Daniel Hailfinger27023762010-04-28 15:22:14 +0000866Using flashrom on laptops is dangerous and may easily make your hardware
Stefan Tauner9e9f6842012-02-16 20:55:27 +0000867unusable. flashrom will attempt to detect if it is running on a laptop and abort
868immediately for safety reasons. Please see the detailed discussion of this topic
869and associated flashrom options in the
870.B Laptops
871paragraph in the
872.B internal programmer
873subsection of the
874.B PROGRAMMER SPECIFIC INFO
875section.
Uwe Hermann941a2732011-07-25 21:12:57 +0000876.B " http://www.flashrom.org/Laptops"
Daniel Lenski65922a32012-02-15 23:40:23 +0000877.SS
878One-time programmable (OTP) memory and unique IDs
879.sp
880Some flash chips contain OTP memory often denoted as "security registers".
881They usually have a capacity in the range of some bytes to a few hundred
Stefan Taunereb582572012-09-21 12:52:50 +0000882bytes and can be used to give devices unique IDs etc. flashrom is not able
Daniel Lenski65922a32012-02-15 23:40:23 +0000883to read or write these memories and may therefore not be able to duplicate a
884chip completely. For chip types known to include OTP memories a warning is
885printed when they are detected.
886.sp
887Similar to OTP memories are unique, factory programmed, unforgeable IDs.
888They are not modifiable by the user at all.
Stefan Taunerac54fbe2011-07-21 19:52:00 +0000889.SH LICENSE
Stefan Reinauer261144c2006-07-27 23:29:02 +0000890.B flashrom
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000891is covered by the GNU General Public License (GPL), version 2. Some files are
892additionally available under the GPL (version 2, or any later version).
Stefan Reinauer261144c2006-07-27 23:29:02 +0000893.SH COPYRIGHT
Stefan Reinauer261144c2006-07-27 23:29:02 +0000894.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000895Please see the individual files.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000896.SH AUTHORS
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000897Andrew Morgan
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000898.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000899Carl-Daniel Hailfinger
900.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000901Claus Gindhart
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000902.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000903David Borg
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000904.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000905David Hendricks
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000906.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000907Dominik Geyer
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000908.br
Stefan Reinaueredc61882010-01-03 14:40:30 +0000909Eric Biederman
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000910.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000911Giampiero Giancipoli
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000912.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000913Helge Wagner
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000914.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000915Idwer Vollering
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000916.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000917Joe Bao
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000918.br
Stefan Taunerc0aaf952011-05-19 02:58:17 +0000919Joerg Fischer
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000920.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000921Joshua Roys
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000922.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000923Luc Verhaegen
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000924.br
Carl-Daniel Hailfinger451dc802009-05-01 11:00:39 +0000925Li-Ta Lo
926.br
Mark Marshall90021f22010-12-03 14:48:11 +0000927Mark Marshall
928.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000929Markus Boas
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000930.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000931Mattias Mattsson
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000932.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000933Michael Karcher
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +0000934.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000935Nikolay Petukhov
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000936.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000937Patrick Georgi
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000938.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000939Peter Lemenkov
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000940.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000941Peter Stuge
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000942.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000943Reinder E.N. de Haan
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000944.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000945Ronald G. Minnich
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000946.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000947Ronald Hoogenboom
Stefan Reinauer261144c2006-07-27 23:29:02 +0000948.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000949Sean Nelson
Carl-Daniel Hailfinger8841d3e2010-05-15 15:04:37 +0000950.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000951Stefan Reinauer
Stefan Reinauer261144c2006-07-27 23:29:02 +0000952.br
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000953Stefan Tauner
954.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000955Stefan Wildemann
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000956.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000957Stephan Guilloux
Carl-Daniel Hailfinger3e854422010-10-06 23:03:21 +0000958.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000959Steven James
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000960.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000961Uwe Hermann
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000962.br
Stefan Reinaueredc61882010-01-03 14:40:30 +0000963Wang Qingpei
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000964.br
Stefan Reinaueredc61882010-01-03 14:40:30 +0000965Yinghai Lu
Stefan Reinauerf8337dd2006-08-03 10:49:09 +0000966.br
Carl-Daniel Hailfingeref697832010-10-07 22:21:45 +0000967some others, please see the flashrom svn changelog for details.
968.br
Uwe Hermann68b9cca2011-06-15 23:44:52 +0000969All authors can be reached via email at <flashrom@flashrom.org>.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000970.PP
Stefan Taunerac54fbe2011-07-21 19:52:00 +0000971This manual page was written by Uwe Hermann <uwe@hermann-uwe.de>,
972Carl-Daniel Hailfinger and others.
Uwe Hermann42eb17f2008-01-18 17:48:51 +0000973It is licensed under the terms of the GNU GPL (version 2 or later).