blob: b64ae6d00eea5bc08ac40cd9d90c264d42d5c980 [file] [log] [blame]
Uwe Hermanne8ba5382009-05-22 11:37:27 +00001.TH FLASHROM 8 "May 21, 2009"
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
Uwe Hermannea07f622009-06-24 17:31:08 +00005.B flashrom \fR[\fB\-VfLzhRn\fR] [\fB\-E\fR|\fB\-r\fR file|\fB\-w\fR file|\fB\-v\fR file] [\fB\-c\fR chipname]
6 [\fB\-m\fR [vendor:]part] [\fB\-l\fR file] [\fB\-i\fR image] [\fB\-p\fR programmer]
Stefan Reinauer261144c2006-07-27 23:29:02 +00007.SH DESCRIPTION
8.B flashrom
Uwe Hermanne8ba5382009-05-22 11:37:27 +00009is a utility for detecting, reading, writing, verifying and erasing flash
Uwe Hermann530cb2d2009-05-14 22:58:21 +000010chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system
11using a supported mainboard, but it also supports flashing of network cards
12(NICs), SATA controller cards, and other external devices which can program
13flash chips.
Uwe Hermanne74b9f82009-04-10 14:41:29 +000014.PP
Uwe Hermannd42009c2009-04-11 13:59:00 +000015It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and
16TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash,
17or SPI.
Uwe Hermanne74b9f82009-04-10 14:41:29 +000018.PP
Uwe Hermann42eb17f2008-01-18 17:48:51 +000019(see
20.B http://coreboot.org
21for details on coreboot)
Stefan Reinauer261144c2006-07-27 23:29:02 +000022.SH OPTIONS
Carl-Daniel Hailfinger5de93412009-05-01 10:53:49 +000023Please note that the command line interface for flashrom will change before
24flashrom 1.0. Do not use flashrom in scripts or other automated tools without
Uwe Hermanne8ba5382009-05-22 11:37:27 +000025checking that your flashrom version won't interpret options in a different way.
Carl-Daniel Hailfinger5de93412009-05-01 10:53:49 +000026.PP
Uwe Hermann1432a602009-06-28 23:26:37 +000027You can specify one of \-E, \-r, \-w, \-v or no operation.
Carl-Daniel Hailfinger01d6aba2009-06-12 14:02:07 +000028If no operation is specified, then all that happens
Stefan Reinauer261144c2006-07-27 23:29:02 +000029is that flash info is dumped and the flash chip is set to writable.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000030.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000031.B "\-r, \-\-read <file>"
32Read flash ROM contents and save them into the given
33.BR <file> .
Stefan Reinauerde063bf2006-09-21 13:09:22 +000034.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000035.B "\-w, \-\-write <file>"
Uwe Hermann9d680802009-07-11 22:17:28 +000036Write file into flash ROM.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000037.TP
Uwe Hermannea07f622009-06-24 17:31:08 +000038.B "\-n, \-\-noverify"
39Do
40.B not
41verify the flash ROM contents after writing them to the chip. Using this
42option is
43.B not
44recommended, you should only use it if you know what you are doing and you
45feel that the time for verification takes too long.
46.sp
47Typical usage is:
48.B "flashrom -wn file"
49.sp
50This option is only useful in combination with
51.BR \-\-write .
52.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +000053.B "\-v, \-\-verify <file>"
54Verify the flash ROM contents against the given
55.BR <file> .
Stefan Reinauerde063bf2006-09-21 13:09:22 +000056.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000057.B "\-E, \-\-erase"
Uwe Hermanne74b9f82009-04-10 14:41:29 +000058Erase the flash ROM chip.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000059.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000060.B "\-V, \-\-verbose"
61More verbose output.
Stefan Reinauerde063bf2006-09-21 13:09:22 +000062.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +000063.B "\-c, \-\-chip" <chipname>
Uwe Hermann42eb17f2008-01-18 17:48:51 +000064Probe only for specified flash ROM chip.
Uwe Hermann87c07932009-05-05 16:15:46 +000065.sp
66flashrom supports ROM layouts. This allows you to flash certain parts of
67the flash chip only. A ROM layout file looks like follows:
68.sp
69 00000000:00008fff gfxrom
70 00009000:0003ffff normal
71 00040000:0007ffff fallback
72.sp
73 i.e.:
74 startaddr:endaddr name
75.sp
76All addresses are offsets within the file, not absolute addresses!
77If you only want to update the normal image in a ROM you can say:
78.sp
79.B " flashrom -w --layout rom.layout --image normal agami_aruma.rom"
80.sp
81To update normal and fallback but leave the VGA BIOS alone, say:
82.sp
83.B " flashrom -w -l rom.layout -i normal \"
84.br
85.B " -i fallback agami_aruma.rom"
86.sp
87Currently overlapping sections are not supported.
88.sp
Uwe Hermanne8ba5382009-05-22 11:37:27 +000089ROM layouts should replace the \-s and \-e option since they are more
Uwe Hermann87c07932009-05-05 16:15:46 +000090flexible and they should lead to a ROM update file format with the
91ROM layout and the ROM image in one file (cpio, zip or something?).
Stefan Reinauerde063bf2006-09-21 13:09:22 +000092.TP
Peter Stuge6b53fed2008-01-27 16:21:21 +000093.B "\-m, \-\-mainboard" <[vendor:]part>
Uwe Hermann87c07932009-05-05 16:15:46 +000094Override mainboard settings.
95.sp
96flashrom reads the coreboot table to determine the current mainboard. If no
97coreboot table could be read or if you want to override these values, you can
Uwe Hermanne8ba5382009-05-22 11:37:27 +000098specify \-m, e.g.:
Uwe Hermann87c07932009-05-05 16:15:46 +000099.sp
100.B " flashrom -w --mainboard AGAMI:ARUMA agami_aruma.rom"
101.sp
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000102See the 'Supported mainboards' section in the output of 'flashrom \-L' for
Uwe Hermann87c07932009-05-05 16:15:46 +0000103a list of boards which require the specification of the board name, if no
104coreboot table is found.
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000105.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +0000106.B "\-f, \-\-force"
Uwe Hermann67808fe2007-10-18 00:29:05 +0000107Force write without checking whether the ROM image file is really meant
108to be used on this board.
109.sp
Stefan Reinauere3f3e2e2008-01-18 15:33:10 +0000110Note: This check only works while coreboot is running, and only for those
111boards where the coreboot code supports it.
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000112.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +0000113.B "\-l, \-\-layout <file>"
114Read ROM layout from
115.BR <file> .
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000116.TP
Uwe Hermanne74b9f82009-04-10 14:41:29 +0000117.B "\-i, \-\-image <name>"
Uwe Hermann67808fe2007-10-18 00:29:05 +0000118Only flash image
119.B <name>
120from flash layout.
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000121.TP
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000122.B "\-L, \-\-list\-supported"
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000123List the flash chips, chipsets, mainboards, and PCI card "programmers"
124supported by flashrom.
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000125.sp
Uwe Hermanne8ba5382009-05-22 11:37:27 +0000126There are many unlisted boards which will work out of the box, without
127special support in flashrom. Please let us know if you can verify that
128other boards work or do not work out of the box. For verification you have
129to test an ERASE and/or WRITE operation, so make sure you only do that
130if you have proper means to recover from failure!
Uwe Hermanne5ac1642008-03-12 11:54:51 +0000131.TP
Uwe Hermann20a293f2009-06-19 10:42:43 +0000132.B "\-z, \-\-list\-supported-wiki"
133Same as
134.BR \-\-list\-supported ,
135but outputs the supported hardware in MediaWiki syntax, so that it can be
136easily pasted into the wiki page at http://coreboot.org/Flashrom.
137.TP
Carl-Daniel Hailfingerce986772009-05-09 00:27:07 +0000138.B "\-p, \-\-programmer <name>"
139Specify the programmer device. Currently supported are:
140.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000141.BR "* internal" " (default, for in-system flashing in the mainboard)"
142.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000143.BR "* dummy" " (just prints all operations and accesses)"
144.sp
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000145.BR "* nic3com" " (for flash ROMs on 3COM network cards)"
146.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000147.BR "* satasii" " (for flash ROMs on Silicon Image SATA/IDE controllers)"
148.sp
Uwe Hermanne9d04d42009-06-02 19:54:22 +0000149.BR "* it87spi" " (for flash ROMs behind an ITE IT87xx Super I/O LPC/SPI translation unit)"
Carl-Daniel Hailfingerb8afecd2009-05-31 18:00:57 +0000150.sp
Paul Fox05dfbe62009-06-16 21:08:06 +0000151.BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)"
152.sp
Carl-Daniel Hailfinger3504b532009-06-01 00:02:11 +0000153The dummy programmer has an optional parameter specifying the bus types it
154should support. For that you have to use the
155.B "flashrom -p dummy=type"
156syntax where
157.B type
158can be any comma-separated combination of
159.B parallel lpc fwh spi all
160in any order.
161.sp
162Example:
163.B "flashrom -p dummy=lpc,fwh"
164.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000165If you have multiple supported PCI cards which can program flash chips
166(NICs, SATA/IDE controllers, etc.) in your system, you must use the
167.B "flashrom -p xxxx=bb:dd.f"
168syntax to explicitly select one of them, where
169.B xxxx
170is the name of the programmer
Uwe Hermann530cb2d2009-05-14 22:58:21 +0000171.B bb
172is the PCI bus number,
173.B dd
174is the PCI device number, and
175.B f
176is the PCI function number of the desired NIC.
177.sp
178Example:
179.B "flashrom -p nic3com=05:04.0"
180.sp
Uwe Hermannc7e8a0c2009-05-19 14:14:21 +0000181Currently the following programmers support this mechanism:
182.BR nic3com ,
183.BR satasii .
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000184.sp
Carl-Daniel Hailfingerbb297f72009-07-11 18:05:42 +0000185The it87spi has an optional parameter which will set the I/O base port of the
186IT87* SPI controller interface to the port specified in the parameter.
187For that you have to use the
188.B "flashrom -p it87spi=port=portnum"
189syntax where
190.B portnum
191is an I/O port number which must be a multiple of 8.
192.sp
Carl-Daniel Hailfingerfeea2722009-07-01 00:02:23 +0000193The ft2232spi has an optional parameter specifying the controller type and
194interface/port it should support. For that you have to use the
195.B "flashrom -p ft2232spi=model,port=interface"
196syntax where
197.B model
198can be any of
199.B 2232H 4232H
200and
201.B interface
202can be any of
203.B A
204.BR B .
205The default model is
206.B 4232H
207and the default interface is
208.BR B .
Carl-Daniel Hailfingerce986772009-05-09 00:27:07 +0000209.TP
Stefan Reinauer261144c2006-07-27 23:29:02 +0000210.B "\-h, \-\-help"
211Show a help text and exit.
Bernhard Walle201bde32008-01-21 15:24:22 +0000212.TP
213.B "\-R, \-\-version"
214Show version information and exit.
Peter Stuge42688e52009-01-26 02:20:56 +0000215.SH EXIT STATUS
216flashrom exits with 0 on success, 1 on most failures but with 2 if /dev/mem
217(/dev/xsvc on Solaris) can not be opened and with 3 if a call to mmap() fails.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000218.SH BUGS
Uwe Hermann42eb17f2008-01-18 17:48:51 +0000219Please report any bugs at
220.BR http://tracker.coreboot.org/trac/coreboot/newticket ","
221or on the coreboot mailing list
222.RB "(" http://coreboot.org/Mailinglist ")."
Stefan Reinauer261144c2006-07-27 23:29:02 +0000223.SH LICENCE
224.B flashrom
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000225is covered by the GNU General Public License (GPL), version 2. Some files are
226additionally available under the GPL (version 2, or any later version).
Stefan Reinauer261144c2006-07-27 23:29:02 +0000227.SH COPYRIGHT
Stefan Reinauer261144c2006-07-27 23:29:02 +0000228.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000229Please see the individual files.
Stefan Reinauer261144c2006-07-27 23:29:02 +0000230.SH AUTHORS
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000231Carl-Daniel Hailfinger
232.br
233Claus Gindhart <claus.gindhart@kontron.com>
234.br
235Dominik Geyer <dominik.geyer@kontron.com>
236.br
237Eric Biederman <ebiederman@lnxi.com>
238.br
239Giampiero Giancipoli <gianci@email.it>
240.br
241Joe Bao <Zheng.Bao@amd.com>
242.br
243Luc Verhaegen <libv@skynet.be>
244.br
Carl-Daniel Hailfinger451dc802009-05-01 11:00:39 +0000245Li-Ta Lo
246.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000247Markus Boas <ryven@ryven.de>
248.br
249Nikolay Petukhov <nikolay.petukhov@gmail.com>
250.br
251Peter Stuge <peter@stuge.se>
252.br
253Reinder E.N. de Haan <lb_reha@mveas.com>
254.br
255Ronald G. Minnich <rminnich@gmail.com>
256.br
257Ronald Hoogenboom <ronald@zonnet.nl>
Stefan Reinauer261144c2006-07-27 23:29:02 +0000258.br
259Stefan Reinauer <stepan@coresystems.de>
260.br
Carl-Daniel Hailfinger851ecf22009-01-08 04:56:59 +0000261Stefan Wildemann <stefan.wildemann@kontron.com>
262.br
263Steven James <pyro@linuxlabs.com>
264.br
265Uwe Hermann <uwe@hermann-uwe.de>
266.br
267Wang Qingpei <Qingpei.Wang@amd.com>
268.br
269Yinghai Lu <yinghai.lu@amd.com>
Stefan Reinauerf8337dd2006-08-03 10:49:09 +0000270.br
271some others
Stefan Reinauer261144c2006-07-27 23:29:02 +0000272.PP
Stefan Reinauerde063bf2006-09-21 13:09:22 +0000273This manual page was written by Uwe Hermann <uwe@hermann-uwe.de>.
Uwe Hermann42eb17f2008-01-18 17:48:51 +0000274It is licensed under the terms of the GNU GPL (version 2 or later).