flashrom.8 8.01 KB
Newer Older
1
.TH FLASHROM 8 "May 21, 2009"
2
.SH NAME
3
flashrom \- detect, read, write, verify and erase flash chips
4
.SH SYNOPSIS
5 6
.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]
         [\fB\-m\fR [vendor:]part] [\fB\-l\fR file] [\fB\-i\fR image] [\fB\-p\fR programmer]
7 8
.SH DESCRIPTION
.B flashrom
9
is a utility for detecting, reading, writing, verifying and erasing flash
10 11 12 13
chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system
using a supported mainboard, but it also supports flashing of network cards
(NICs), SATA controller cards, and other external devices which can program
flash chips.
Uwe Hermann's avatar
Uwe Hermann committed
14
.PP
15 16 17
It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, and
TSOP40 chips, which use various protocols such as LPC, FWH, parallel flash,
or SPI.
Uwe Hermann's avatar
Uwe Hermann committed
18
.PP
19 20 21
(see
.B http://coreboot.org
for details on coreboot)
22
.SH OPTIONS
23 24
Please note that the command line interface for flashrom will change before
flashrom 1.0. Do not use flashrom in scripts or other automated tools without
25
checking that your flashrom version won't interpret options in a different way.
26
.PP
Uwe Hermann's avatar
Uwe Hermann committed
27
You can specify one of \-E, \-r, \-w, \-v or no operation.
28
If no operation is specified, then all that happens
29
is that flash info is dumped and the flash chip is set to writable.
30
.TP
Uwe Hermann's avatar
Uwe Hermann committed
31 32 33
.B "\-r, \-\-read <file>"
Read flash ROM contents and save them into the given
.BR <file> .
34
.TP
Uwe Hermann's avatar
Uwe Hermann committed
35
.B "\-w, \-\-write <file>"
Uwe Hermann's avatar
Uwe Hermann committed
36
Write file into flash ROM.
37
.TP
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
.B "\-n, \-\-noverify"
Do
.B not
verify the flash ROM contents after writing them to the chip. Using this
option is
.B not
recommended, you should only use it if you know what you are doing and you
feel that the time for verification takes too long.
.sp
Typical usage is:
.B "flashrom -wn file"
.sp
This option is only useful in combination with
.BR \-\-write .
.TP
Uwe Hermann's avatar
Uwe Hermann committed
53 54 55
.B "\-v, \-\-verify <file>"
Verify the flash ROM contents against the given
.BR <file> .
56
.TP
57
.B "\-E, \-\-erase"
Uwe Hermann's avatar
Uwe Hermann committed
58
Erase the flash ROM chip.
59
.TP
60 61
.B "\-V, \-\-verbose"
More verbose output.
62
.TP
63
.B "\-c, \-\-chip" <chipname>
64
Probe only for specified flash ROM chip.
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88
.sp
flashrom supports ROM layouts. This allows you to flash certain parts of
the flash chip only. A ROM layout file looks like follows:
.sp
  00000000:00008fff gfxrom
  00009000:0003ffff normal
  00040000:0007ffff fallback
.sp
  i.e.:
  startaddr:endaddr name
.sp
All addresses are offsets within the file, not absolute addresses!
If you only want to update the normal image in a ROM you can say:
.sp
.B "  flashrom -w --layout rom.layout --image normal agami_aruma.rom"
.sp
To update normal and fallback but leave the VGA BIOS alone, say:
.sp
.B "  flashrom -w -l rom.layout -i normal \"
.br
.B "           -i fallback agami_aruma.rom"
.sp
Currently overlapping sections are not supported.
.sp
89
ROM layouts should replace the \-s and \-e option since they are more
90 91
flexible and they should lead to a ROM update file format with the
ROM layout and the ROM image in one file (cpio, zip or something?).
92
.TP
93
.B "\-m, \-\-mainboard" <[vendor:]part>
94 95 96 97
Override mainboard settings.
.sp
flashrom reads the coreboot table to determine the current mainboard. If no
coreboot table could be read or if you want to override these values, you can
98
specify \-m, e.g.:
99 100 101
.sp
.B "  flashrom -w --mainboard AGAMI:ARUMA agami_aruma.rom"
.sp
102
See the 'Supported mainboards' section in the output of 'flashrom \-L' for
103 104
a list of boards which require the specification of the board name, if no
coreboot table is found.
105
.TP
106
.B "\-f, \-\-force"
Uwe Hermann's avatar
Uwe Hermann committed
107 108 109
Force write without checking whether the ROM image file is really meant
to be used on this board.
.sp
Stefan Reinauer's avatar
Stefan Reinauer committed
110 111
Note: This check only works while coreboot is running, and only for those
boards where the coreboot code supports it.
112
.TP
Uwe Hermann's avatar
Uwe Hermann committed
113 114 115
.B "\-l, \-\-layout <file>"
Read ROM layout from
.BR <file> .
116
.TP
Uwe Hermann's avatar
Uwe Hermann committed
117
.B "\-i, \-\-image <name>"
Uwe Hermann's avatar
Uwe Hermann committed
118 119 120
Only flash image
.B <name>
from flash layout.
121
.TP
122
.B "\-L, \-\-list\-supported"
123 124 125 126 127 128 129 130
List the flash chips, chipsets, mainboards, and PCI card "programmers"
supported by flashrom.
.sp
There are many unlisted boards which will work out of the box, without
special support in flashrom. Please let us know if you can verify that
other boards work or do not work out of the box. For verification you have
to test an ERASE and/or WRITE operation, so make sure you only do that
if you have proper means to recover from failure!
131
.TP
132 133 134 135 136 137
.B "\-z, \-\-list\-supported-wiki"
Same as
.BR \-\-list\-supported ,
but outputs the supported hardware in MediaWiki syntax, so that it can be
easily pasted into the wiki page at http://coreboot.org/Flashrom.
.TP
138 139 140
.B "\-p, \-\-programmer <name>"
Specify the programmer device. Currently supported are:
.sp
141 142
.BR "* internal" " (default, for in-system flashing in the mainboard)"
.sp
143 144
.BR "* dummy" " (just prints all operations and accesses)"
.sp
145 146
.BR "* nic3com" " (for flash ROMs on 3COM network cards)"
.sp
147 148
.BR "* satasii" " (for flash ROMs on Silicon Image SATA/IDE controllers)"
.sp
149
.BR "* it87spi" " (for flash ROMs behind an ITE IT87xx Super I/O LPC/SPI translation unit)"
150
.sp
151 152
.BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)"
.sp
153 154 155 156 157 158 159 160 161 162 163 164
The dummy programmer has an optional parameter specifying the bus types it
should support. For that you have to use the
.B "flashrom -p dummy=type"
syntax where
.B type
can be any comma-separated combination of
.B parallel lpc fwh spi all
in any order.
.sp
Example:
.B "flashrom -p dummy=lpc,fwh"
.sp
165 166 167 168 169 170
If you have multiple supported PCI cards which can program flash chips
(NICs, SATA/IDE controllers, etc.) in your system, you must use the
.B "flashrom -p xxxx=bb:dd.f"
syntax to explicitly select one of them, where
.B xxxx
is the name of the programmer
171 172 173 174 175 176 177 178 179 180
.B bb
is the PCI bus number,
.B dd
is the PCI device number, and
.B f
is the PCI function number of the desired NIC.
.sp
Example:
.B "flashrom -p nic3com=05:04.0"
.sp
181 182 183
Currently the following programmers support this mechanism:
.BR nic3com ,
.BR satasii .
184
.sp
185 186 187 188 189 190 191 192
The it87spi has an optional parameter which will set the I/O base port of the
IT87* SPI controller interface to the port specified in the parameter.
For that you have to use the
.B "flashrom -p it87spi=port=portnum"
syntax where
.B portnum
is an I/O port number which must be a multiple of 8.
.sp
193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208
The ft2232spi has an optional parameter specifying the controller type and
interface/port it should support. For that you have to use the
.B "flashrom -p ft2232spi=model,port=interface"
syntax where
.B model
can be any of
.B 2232H 4232H
and
.B interface
can be any of
.B A
.BR B .
The default model is
.B 4232H
and the default interface is
.BR B .
209
.TP
210 211
.B "\-h, \-\-help"
Show a help text and exit.
212 213 214
.TP
.B "\-R, \-\-version"
Show version information and exit.
215 216 217
.SH EXIT STATUS
flashrom exits with 0 on success, 1 on most failures but with 2 if /dev/mem
(/dev/xsvc on Solaris) can not be opened and with 3 if a call to mmap() fails.
218
.SH BUGS
219 220 221 222
Please report any bugs at
.BR http://tracker.coreboot.org/trac/coreboot/newticket ","
or on the coreboot mailing list
.RB "(" http://coreboot.org/Mailinglist ")."
223 224
.SH LICENCE
.B flashrom
225 226
is covered by the GNU General Public License (GPL), version 2. Some files are
additionally available under the GPL (version 2, or any later version).
227 228
.SH COPYRIGHT
.br
229 230 231
Please see the individual files.
.SH AUTHORS
Carl-Daniel Hailfinger
232
.br
233
Claus Gindhart <claus.gindhart@kontron.com>
234
.br
235 236 237 238 239 240 241 242 243 244
Dominik Geyer <dominik.geyer@kontron.com>
.br
Eric Biederman <ebiederman@lnxi.com>
.br
Giampiero Giancipoli <gianci@email.it>
.br
Joe Bao <Zheng.Bao@amd.com>
.br
Luc Verhaegen <libv@skynet.be>
.br
245 246
Li-Ta Lo
.br
247 248 249 250 251 252 253 254 255 256 257
Markus Boas <ryven@ryven.de>
.br
Nikolay Petukhov <nikolay.petukhov@gmail.com>
.br
Peter Stuge <peter@stuge.se>
.br
Reinder E.N. de Haan <lb_reha@mveas.com>
.br
Ronald G. Minnich <rminnich@gmail.com>
.br
Ronald Hoogenboom <ronald@zonnet.nl>
258 259 260
.br
Stefan Reinauer <stepan@coresystems.de>
.br
261 262 263 264 265 266 267 268 269
Stefan Wildemann <stefan.wildemann@kontron.com>
.br
Steven James <pyro@linuxlabs.com>
.br
Uwe Hermann <uwe@hermann-uwe.de>
.br
Wang Qingpei <Qingpei.Wang@amd.com>
.br
Yinghai Lu <yinghai.lu@amd.com>
270 271
.br
some others 
272
.PP
273
This manual page was written by Uwe Hermann <uwe@hermann-uwe.de>.
274
It is licensed under the terms of the GNU GPL (version 2 or later).