flashrom.8.tmpl 40.3 KB
Newer Older
1
.TH FLASHROM 8 "" ""
2
.SH NAME
3
flashrom \- detect, read, write, verify and erase flash chips
4
.SH SYNOPSIS
5 6 7 8 9 10
.B flashrom \fR[\fB\-h\fR|\fB\-R\fR|\fB\-L\fR|\fB\-z\fR|\
\fB\-p\fR <programmername>[:<parameters>]
               [\fB\-E\fR|\fB\-r\fR <file>|\fB\-w\fR <file>|\fB\-v\fR <file>] \
[\fB\-c\fR <chipname>]
               [\fB\-l\fR <file> [\fB\-i\fR <image>]] [\fB\-n\fR] [\fB\-f\fR]]
         [\fB\-V\fR[\fBV\fR[\fBV\fR]]] [\fB-o\fR <logfile>]
11 12
.SH DESCRIPTION
.B flashrom
13
is a utility for detecting, reading, writing, verifying and erasing flash
14
chips. It's often used to flash BIOS/EFI/coreboot/firmware images in-system
15 16 17
using a supported mainboard. However, it also supports various external
PCI/USB/parallel-port/serial-port based devices which can program flash chips,
including some network cards (NICs), SATA/IDE controller cards, graphics cards,
18
the Bus Pirate device, various FTDI FT2232/FT4232H/FT232H based USB devices, and more.
Uwe Hermann's avatar
Uwe Hermann committed
19
.PP
20
It supports a wide range of DIP32, PLCC32, DIP8, SO8/SOIC8, TSOP32, TSOP40,
21 22
TSOP48, and BGA chips, which use various protocols such as LPC, FWH,
parallel flash, or SPI.
23
.SH OPTIONS
24
.B IMPORTANT:
25 26
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
27
checking that your flashrom version won't interpret options in a different way.
28
.PP
29 30 31
You can specify one of
.BR \-h ", " \-R ", " \-L ", " \-z ", " \-E ", " \-r ", " \-w ", " \-v
or no operation.
32
If no operation is specified, flashrom will only probe for flash chips. It is
33
recommended that if you try flashrom the first time on a system, you run it
34
in probe-only mode and check the output. Also you are advised to make a
35 36
backup of your current ROM contents with
.B \-r
37 38 39
before you try to write a new image. All operations involving any chip access (probe/read/write/...) require the
.B -p/--programmer
option to be used (please see below).
40
.TP
Uwe Hermann's avatar
Uwe Hermann committed
41 42 43
.B "\-r, \-\-read <file>"
Read flash ROM contents and save them into the given
.BR <file> .
44
If the file already exists, it will be overwritten.
45
.TP
Uwe Hermann's avatar
Uwe Hermann committed
46
.B "\-w, \-\-write <file>"
47 48
Write
.B <file>
49 50 51
into flash ROM. This will first automatically
.B erase
the chip, then write to it.
52 53 54 55 56 57 58
.sp
In the process the chip is also read several times. First an in-memory backup
is made for disaster recovery and to be able to skip regions that are
already equal to the image file. This copy is updated along with the write
operation. In case of erase errors it is even re-read completely. After
writing has finished and if verification is enabled, the whole flash chip is
read out and compared with the input image.
59
.TP
60
.B "\-n, \-\-noverify"
61
Skip the automatic verification of flash ROM contents after writing. Using this
62 63
option is
.B not
64
recommended, you should only use it if you know what you are doing and if you
65 66 67
feel that the time for verification takes too long.
.sp
Typical usage is:
68
.B "flashrom \-p prog \-n \-w <file>"
69 70 71 72
.sp
This option is only useful in combination with
.BR \-\-write .
.TP
Uwe Hermann's avatar
Uwe Hermann committed
73 74 75
.B "\-v, \-\-verify <file>"
Verify the flash ROM contents against the given
.BR <file> .
76
.TP
77
.B "\-E, \-\-erase"
Uwe Hermann's avatar
Uwe Hermann committed
78
Erase the flash ROM chip.
79
.TP
80
.B "\-V, \-\-verbose"
81
More verbose output. This option can be supplied multiple times
Stefan Tauner's avatar
Stefan Tauner committed
82 83
(max. 3 times, i.e.
.BR \-VVV )
84
for even more debug output.
85
.TP
86
.B "\-c, \-\-chip" <chipname>
87
Probe only for the specified flash ROM chip. This option takes the chip name as
88 89
printed by
.B "flashrom \-L"
90 91
without the vendor name as parameter. Please note that the chip name is
case sensitive.
92 93
.TP
.B "\-f, \-\-force"
94
Force one or more of the following actions:
95
.sp
96 97
* Force chip read and pretend the chip is there.
.sp
98
* Force chip access even if the chip is bigger than the maximum supported \
99
size for the flash bus.
100 101 102 103
.sp
* Force erase even if erase is known bad.
.sp
* Force write even if write is known bad.
104 105 106 107
.TP
.B "\-l, \-\-layout <file>"
Read ROM layout from
.BR <file> .
108 109
.sp
flashrom supports ROM layouts. This allows you to flash certain parts of
110 111 112 113 114 115 116 117 118 119 120 121 122
the flash chip only. A ROM layout file contains multiple lines with the
following syntax:
.sp
.B "  startaddr:endaddr imagename"
.sp
.BR "startaddr " "and " "endaddr "
are hexadecimal addresses within the ROM file and do not refer to any
physical address. Please note that using a 0x prefix for those hexadecimal
numbers is not necessary, but you can't specify decimal/octal numbers.
.BR "imagename " "is an arbitrary name for the region/image from"
.BR " startaddr " "to " "endaddr " "(both addresses included)."
.sp
Example:
123 124 125 126 127
.sp
  00000000:00008fff gfxrom
  00009000:0003ffff normal
  00040000:0007ffff fallback
.sp
128 129
If you only want to update the image named
.BR "normal " "in a ROM based on the layout above, run"
130
.sp
131
.B "  flashrom \-p prog \-\-layout rom.layout \-\-image normal \-w some.rom"
132
.sp
133
To update only the images named
134
.BR "normal " "and " "fallback" ", run:"
135
.sp
136
.B "  flashrom \-p prog \-l rom.layout \-i normal -i fallback \-w some.rom"
137
.sp
138
Overlapping sections are not supported.
139
.TP
140 141 142
.B "\-i, \-\-image <imagename>"
Only flash region/image
.B <imagename>
Uwe Hermann's avatar
Uwe Hermann committed
143
from flash layout.
144
.TP
145
.B "\-L, \-\-list\-supported"
146 147
List the flash chips, chipsets, mainboards, and external programmers
(including PCI, USB, parallel port, and serial port based devices)
148 149 150 151
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
152 153 154 155
other boards work or do not work out of the box.
.sp
.B IMPORTANT:
For verification you have
156 157
to test an ERASE and/or WRITE operation, so make sure you only do that
if you have proper means to recover from failure!
158
.TP
159 160 161 162
.B "\-z, \-\-list\-supported-wiki"
Same as
.BR \-\-list\-supported ,
but outputs the supported hardware in MediaWiki syntax, so that it can be
163
easily pasted into the wiki page at
164
.nh
165 166
.BR http://www.flashrom.org/ .
Please note that MediaWiki output is not compiled in by default.
167
.TP
168
.B "\-p, \-\-programmer <name>[:parameter[,parameter[,parameter]]]"
169 170
Specify the programmer device. This is mandatory for all operations
involving any chip access (probe/read/write/...). Currently supported are:
171
.sp
172 173
.BR "* internal" " (default, for in-system flashing in the mainboard)"
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
174
.BR "* dummy" " (virtual programmer for testing flashrom)"
175
.sp
176 177
.BR "* nic3com" " (for flash ROMs on 3COM network cards)"
.sp
178
.BR "* nicrealtek" " (for flash ROMs on Realtek and SMC 1211 network cards)"
Uwe Hermann's avatar
Uwe Hermann committed
179
.sp
180 181 182
.BR "* nicnatsemi" " (for flash ROMs on National Semiconductor DP838* network \
cards)"
.sp
183
.BR "* nicintel" " (for parallel flash ROMs on Intel 10/100Mbit network cards)
Uwe Hermann's avatar
Uwe Hermann committed
184
.sp
185 186
.BR "* gfxnvidia" " (for flash ROMs on NVIDIA graphics cards)"
.sp
187 188
.BR "* drkaiser" " (for flash ROMs on Dr. Kaiser PC-Waechter PCI cards)"
.sp
189 190
.BR "* satasii" " (for flash ROMs on Silicon Image SATA/IDE controllers)"
.sp
Uwe Hermann's avatar
Uwe Hermann committed
191 192
.BR "* satamv" " (for flash ROMs on Marvell SATA controllers)"
.sp
193 194
.BR "* atahpt" " (for flash ROMs on Highpoint ATA/RAID controllers)"
.sp
195
.BR "* atavia" " (for flash ROMs on VIA VT6421A SATA controllers)"
196
.sp
Kyösti Mälkki's avatar
Kyösti Mälkki committed
197 198
.BR "* it8212" " (for flash ROMs on ITE IT8212F ATA/RAID controller)"
.sp
199
.BR "* ft2232_spi" " (for SPI flash ROMs attached to an FT2232/FT4232H/FT232H family \
200 201
based USB SPI programmer), including the DLP Design DLP-USB1232H, \
FTDI FT2232H Mini-Module, FTDI FT4232H Mini-Module, openbiosprog-spi, Amontec \
202
JTAGkey/JTAGkey-tiny/JTAGkey-2, Dangerous Prototypes Bus Blaster, \
203
Olimex ARM-USB-TINY/-H, Olimex ARM-USB-OCD/-H, TIAO/DIYGADGET USB
204
Multi-Protocol Adapter (TUMPA), TUMPA Lite, and GOEPEL PicoTAP.
205
.sp
206 207 208 209
.BR "* serprog" " (for flash ROMs attached to a programmer speaking serprog), \
including AVR flasher by Urja Rannikko, AVR flasher by eightdot, \
Arduino Mega flasher by fritz, InSystemFlasher by Juhana Helovuo, and \
atmegaXXu2-flasher by Stefan Tauner."
210
.sp
211
.BR "* buspirate_spi" " (for SPI flash ROMs attached to a Bus Pirate)"
212
.sp
213 214
.BR "* dediprog" " (for SPI flash ROMs attached to a Dediprog SF100)"
.sp
215
.BR "* rayer_spi" " (for SPI flash ROMs attached to a parallel port by one of various cable types)"
216
.sp
217 218 219
.BR "* pony_spi" " (for SPI flash ROMs attached to a SI-Prog serial port "
bitbanging adapter)
.sp
220
.BR "* nicintel_spi" " (for SPI flash ROMs on Intel Gigabit network cards)"
221
.sp
222
.BR "* ogp_spi" " (for SPI flash ROMs on Open Graphics Project graphics card)"
223
.sp
224 225
.BR "* linux_spi" " (for SPI flash ROMs accessible via /dev/spidevX.Y on Linux)"
.sp
226 227
.BR "* usbblaster_spi" " (for SPI flash ROMs attached to an Altera USB-Blaster compatible cable)"
.sp
228 229
.BR "* nicintel_eeprom" " (for SPI EEPROMs on Intel Gigabit network cards)"
.sp
230 231
.BR "* mstarddc_spi" " (for SPI flash ROMs accessible through DDC in MSTAR-equipped displays)"
.sp
232 233
.BR "* pickit2_spi" " (for SPI flash ROMs accessible via Microchip PICkit2)"
.sp
Michael Karcher's avatar
Michael Karcher committed
234 235
Some programmers have optional or mandatory parameters which are described
in detail in the
236
.B PROGRAMMER-SPECIFIC INFORMATION
Michael Karcher's avatar
Michael Karcher committed
237
section. Support for some programmers can be disabled at compile time.
238
.B "flashrom \-h"
Michael Karcher's avatar
Michael Karcher committed
239 240 241 242 243
lists all supported programmers.
.TP
.B "\-h, \-\-help"
Show a help text and exit.
.TP
244 245 246 247 248
.B "\-o, \-\-output <logfile>"
Save the full debug log to
.BR <logfile> .
If the file already exists, it will be overwritten. This is the recommended
way to gather logs from flashrom because they will be verbose even if the
249
on-screen messages are not verbose and don't require output redirection.
250
.TP
Michael Karcher's avatar
Michael Karcher committed
251 252
.B "\-R, \-\-version"
Show version information and exit.
253
.SH PROGRAMMER-SPECIFIC INFORMATION
Michael Karcher's avatar
Michael Karcher committed
254
Some programmer drivers accept further parameters to set programmer-specific
255
parameters. These parameters are separated from the programmer name by a
Michael Karcher's avatar
Michael Karcher committed
256 257 258
colon. While some programmers take arguments at fixed positions, other
programmers use a key/value interface in which the key and value is separated
by an equal sign and different pairs are separated by a comma or a colon.
Stefan Tauner's avatar
Stefan Tauner committed
259
.SS
260
.BR "internal " programmer
Stefan Tauner's avatar
Stefan Tauner committed
261 262 263
.TP
.B Board Enables
.sp
264 265 266 267
Some mainboards require to run mainboard specific code to enable flash erase
and write support (and probe support on old systems with parallel flash).
The mainboard brand and model (if it requires specific code) is usually
autodetected using one of the following mechanisms: If your system is
268 269
running coreboot, the mainboard type is determined from the coreboot table.
Otherwise, the mainboard is detected by examining the onboard PCI devices
270
and possibly DMI info. If PCI and DMI do not contain information to uniquely
271 272 273
identify the mainboard (which is the exception), or if you want to override
the detected mainboard model, you can specify the mainboard using the
.sp
274
.B "  flashrom \-p internal:mainboard=<vendor>:<board>"
275 276 277 278 279
syntax.
.sp
See the 'Known boards' or 'Known laptops' section in the output
of 'flashrom \-L' for a list of boards which require the specification of
the board name, if no coreboot table is found.
280
.sp
281 282
Some of these board-specific flash enabling functions (called
.BR "board enables" )
283 284 285 286 287 288 289 290 291 292 293 294 295 296
in flashrom have not yet been tested. If your mainboard is detected needing
an untested board enable function, a warning message is printed and the
board enable is not executed, because a wrong board enable function might
cause the system to behave erratically, as board enable functions touch the
low-level internals of a mainboard. Not executing a board enable function
(if one is needed) might cause detection or erasing failure. If your board
protects only part of the flash (commonly the top end, called boot block),
flashrom might encounter an error only after erasing the unprotected part,
so running without the board-enable function might be dangerous for erase
and write (which includes erase).
.sp
The suggested procedure for a mainboard with untested board specific code is
to first try to probe the ROM (just invoke flashrom and check that it
detects your flash chip type) without running the board enable code (i.e.
297
without any parameters). If it finds your chip, fine. Otherwise, retry
298 299
probing your chip with the board-enable code running, using
.sp
300
.B "  flashrom \-p internal:boardenable=force"
301 302 303
.sp
If your chip is still not detected, the board enable code seems to be broken
or the flash chip unsupported. Otherwise, make a backup of your current ROM
304 305 306 307
contents (using
.BR \-r )
and store it to a medium outside of your computer, like
a USB drive or a network share. If you needed to run the board enable code
308 309 310
already for probing, use it for reading too.
If reading succeeds and the contens of the read file look legit you can try to write the new image.
You should enable the board enable code in any case now, as it
311 312 313 314
has been written because it is known that writing/erasing without the board
enable is going to fail. In any case (success or failure), please report to
the flashrom mailing list, see below.
.sp
Stefan Tauner's avatar
Stefan Tauner committed
315 316 317
.TP
.B Coreboot
.sp
318 319 320 321 322
On systems running coreboot, flashrom checks whether the desired image matches
your mainboard. This needs some special board ID to be present in the image.
If flashrom detects that the image you want to write and the current board
do not match, it will refuse to write the image unless you specify
.sp
323
.B "  flashrom \-p internal:boardmismatch=force"
Stefan Tauner's avatar
Stefan Tauner committed
324 325
.TP
.B ITE IT87 Super I/O
326
.sp
327 328 329 330 331 332 333 334 335 336 337 338 339
If your mainboard is manufactured by GIGABYTE and supports DualBIOS it is very likely that it uses an
ITE IT87 series Super I/O to switch between the two flash chips. Only one of them can be accessed at a time
and you can manually select which one to use with the
.sp
.B "  flashrom \-p internal:dualbiosindex=chip"
.sp
syntax where
.B chip
is the index of the chip to use (0 = main, 1 = backup). You can check which one is currently selected by
leaving out the
.B chip
parameter.
.sp
340
If your mainboard uses an ITE IT87 series Super I/O for LPC<->SPI flash bus
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
341 342
translation, flashrom should autodetect that configuration. If you want to
set the I/O base port of the IT87 series SPI controller manually instead of
Stefan Tauner's avatar
Stefan Tauner committed
343
using the value provided by the BIOS, use the
344 345
.sp
.B "  flashrom \-p internal:it87spiport=portnum"
346
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
347 348 349 350 351
syntax where
.B portnum
is the I/O port number (must be a multiple of 8). In the unlikely case
flashrom doesn't detect an active IT87 LPC<->SPI bridge, please send a bug
report so we can diagnose the problem.
352
.sp
Stefan Tauner's avatar
Stefan Tauner committed
353
.TP
354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369
.B AMD chipsets
.sp
Beginning with the SB700 chipset there is an integrated microcontroller (IMC) based on the 8051 embedded in
every AMD southbridge. Its firmware resides in the same flash chip as the host's which makes writing to the
flash risky if the IMC is active. Flashrom tries to temporarily disable the IMC but even then changing the
contents of the flash can have unwanted effects: when the IMC continues (at the latest after a reboot) it will
continue executing code from the flash. If the code was removed or changed in an unfortunate way it is
unpredictable what the IMC will do. Therefore, if flashrom detects an active IMC it will disable write support
unless the user forces it with the
.sp
.B "  flashrom \-p internal:amd_imc_force=yes"
.sp
syntax. The user is responsible for supplying a suitable image or leaving out the IMC region with the help of
a layout file. This limitation might be removed in the future when we understand the details better and have
received enough feedback from users. Please report the outcome if you had to use this option to write a chip.
.sp
Stefan Tauner's avatar
Stefan Tauner committed
370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390
An optional
.B spispeed
parameter specifies the frequency of the SPI bus where applicable (i.e.\& SB600 or later with an SPI flash chip
directly attached to the chipset).
Syntax is
.sp
.B "  flashrom \-p internal:spispeed=frequency"
.sp
where
.B frequency
can be
.BR "'16.5\ MHz'" ", " "'22\ MHz'" ", " "'33\ MHz'" ", " "'66\ MHz'" ", " "'100\ MHZ'" ", or " "'800\ kHz'" "."
Support of individual frequencies depends on the generation of the chipset:
.sp
* SB6xx, SB7xx, SP5xxx: from 16.5 MHz up to and including 33 MHz
.sp
* SB8xx, SB9xx, Hudson: from 16.5 MHz up to and including 66 MHz
.sp
* Yangtze (with SPI 100 engine as found in Kabini and Tamesh): all of them
.sp
The default is to use 16.5 MHz and disable Fast Reads.
391
.TP
Stefan Tauner's avatar
Stefan Tauner committed
392 393
.B Intel chipsets
.sp
394
If you have an Intel chipset with an ICH8 or later southbridge with SPI flash
395
attached, and if a valid descriptor was written to it (e.g.\& by the vendor), the
396 397 398 399 400 401 402 403 404
chipset provides an alternative way to access the flash chip(s) named
.BR "Hardware Sequencing" .
It is much simpler than the normal access method (called
.BR "Software Sequencing" "),"
but does not allow the software to choose the SPI commands to be sent.
You can use the
.sp
.B "  flashrom \-p internal:ich_spi_mode=value"
.sp
405 406
syntax where
.BR "value " "can be"
407 408 409
.BR auto ", " swseq " or " hwseq .
By default
.RB "(or when setting " ich_spi_mode=auto )
410
the module tries to use swseq and only activates hwseq if need be (e.g.\& if
411 412 413 414
important opcodes are inaccessible due to lockdown; or if more than one flash
chip is attached). The other options (swseq, hwseq) select the respective mode
(if possible).
.sp
415 416 417 418 419 420 421 422 423 424 425 426 427 428 429
ICH8 and later southbridges may also have locked address ranges of different
kinds if a valid descriptor was written to it. The flash address space is then
partitioned in multiple so called "Flash Regions" containing the host firmware,
the ME firmware and so on respectively. The flash descriptor can also specify up
to 5 so called "Protected Regions", which are freely chosen address ranges
independent from the aforementioned "Flash Regions". All of them can be write
and/or read protected individually. If flashrom detects such a lock it will
disable write support unless the user forces it with the
.sp
.B "  flashrom \-p internal:ich_spi_force=yes"
.sp
syntax. If this leads to erase or write accesses to the flash it would most
probably bring it into an inconsistent and unbootable state and we will not
provide any support in such a case.
.sp
430
If you have an Intel chipset with an ICH2 or later southbridge and if you want
431 432 433 434 435
to set specific IDSEL values for a non-default flash chip or an embedded
controller (EC), you can use the
.sp
.B "  flashrom \-p internal:fwh_idsel=value"
.sp
436 437 438
syntax where
.B value
is the 48-bit hexadecimal raw value to be written in the
439 440 441 442 443 444 445 446 447
IDSEL registers of the Intel southbridge. The upper 32 bits use one hex digit
each per 512 kB range between 0xffc00000 and 0xffffffff, and the lower 16 bits
use one hex digit each per 1024 kB range between 0xff400000 and 0xff7fffff.
The rightmost hex digit corresponds with the lowest address range. All address
ranges have a corresponding sister range 4 MB below with identical IDSEL
settings. The default value for ICH7 is given in the example below.
.sp
Example:
.B "flashrom \-p internal:fwh_idsel=0x001122334567"
Stefan Tauner's avatar
Stefan Tauner committed
448 449
.TP
.B Laptops
450
.sp
451
Using flashrom on laptops is dangerous and may easily make your hardware
452 453 454 455
unusable (see also the
.B BUGS
section). The embedded controller (EC) in these
machines often interacts badly with flashing.
456
.nh
457
.B http://www.flashrom.org/Laptops
Stefan Tauner's avatar
Stefan Tauner committed
458 459 460 461 462 463 464 465
has more information. For example the EC firmware sometimes resides on the same
flash chip as the host firmware. While flashrom tries to change the contents of
that memory the EC might need to fetch new instructions or data from it and
could stop working correctly. Probing for and reading from the chip may also
irritate your EC and cause fan failure, backlight failure, sudden poweroff, and
other nasty effects. flashrom will attempt to detect if it is running on a
laptop and abort immediately for safety reasons if it clearly identifies the
host computer as one. If you want to proceed anyway at your own risk, use
466
.sp
467
.B "  flashrom \-p internal:laptop=force_I_want_a_brick"
468 469 470
.sp
We will not help you if you force flashing on a laptop because this is a really
dumb idea.
Stefan Tauner's avatar
Stefan Tauner committed
471 472 473 474 475 476 477 478 479 480
.sp
You have been warned.
.sp
Currently we rely on the chassis type encoded in the DMI/SMBIOS data to detect
laptops. Some vendors did not implement those bits correctly or set them to
generic and/or dummy values. flashrom will then issue a warning and bail out
like above. In this case you can use
.sp
.B "  flashrom \-p internal:laptop=this_is_not_a_laptop"
.sp
481
to tell flashrom (at your own risk) that it is not running on a laptop.
Stefan Tauner's avatar
Stefan Tauner committed
482
.SS
Michael Karcher's avatar
Michael Karcher committed
483
.BR "dummy " programmer
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
484 485 486 487 488 489 490
The dummy programmer operates on a buffer in memory only. It provides a safe
and fast way to test various aspects of flashrom and is mainly used in
development and while debugging.
.sp
It is able to emulate some chips to a certain degree (basic
identify/read/erase/write operations work).
.sp
Michael Karcher's avatar
Michael Karcher committed
491
An optional parameter specifies the bus types it
492
should support. For that you have to use the
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
493 494 495
.sp
.B "  flashrom \-p dummy:bus=[type[+type[+type]]]"
.sp
496 497
syntax where
.B type
Uwe Hermann's avatar
Uwe Hermann committed
498
can be
499 500 501
.BR parallel ", " lpc ", " fwh ", " spi
in any order. If you specify bus without type, all buses will be disabled.
If you do not specify bus, all buses will be enabled.
502 503
.sp
Example:
504
.B "flashrom \-p dummy:bus=lpc+fwh"
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521
.sp
The dummy programmer supports flash chip emulation for automated self-tests
without hardware access. If you want to emulate a flash chip, use the
.sp
.B "  flashrom \-p dummy:emulate=chip"
.sp
syntax where
.B chip
is one of the following chips (please specify only the chip name, not the
vendor):
.sp
.RB "* ST " M25P10.RES " SPI flash chip (RES, page write)"
.sp
.RB "* SST " SST25VF040.REMS " SPI flash chip (REMS, byte write)"
.sp
.RB "* SST " SST25VF032B " SPI flash chip (RDID, AAI write)"
.sp
522 523
.RB "* Macronix " MX25L6436 " SPI flash chip (RDID, SFDP)"
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
524 525
Example:
.B "flashrom -p dummy:emulate=SST25VF040.REMS"
Stefan Tauner's avatar
Stefan Tauner committed
526 527
.TP
.B Persistent images
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
528 529 530 531 532 533 534 535 536 537 538 539 540
.sp
If you use flash chip emulation, flash image persistence is available as well
by using the
.sp
.B "  flashrom \-p dummy:emulate=chip,image=image.rom"
.sp
syntax where
.B image.rom
is the file where the simulated chip contents are read on flashrom startup and
where the chip contents on flashrom shutdown are written to.
.sp
Example:
.B "flashrom -p dummy:emulate=M25P10.RES,image=dummy.bin"
Stefan Tauner's avatar
Stefan Tauner committed
541 542
.TP
.B SPI write chunk size
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
543 544 545 546 547 548 549 550 551
.sp
If you use SPI flash chip emulation for a chip which supports SPI page write
with the default opcode, you can set the maximum allowed write chunk size with
the
.sp
.B "  flashrom \-p dummy:emulate=chip,spi_write_256_chunksize=size"
.sp
syntax where
.B size
552
is the number of bytes (min.\& 1, max.\& 256).
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
553 554 555 556
.sp
Example:
.sp
.B "  flashrom -p dummy:emulate=M25P10.RES,spi_write_256_chunksize=5"
Stefan Tauner's avatar
Stefan Tauner committed
557 558
.TP
.B SPI blacklist
559 560 561 562 563 564
.sp
To simulate a programmer which refuses to send certain SPI commands to the
flash chip, you can specify a blacklist of SPI commands with the
.sp
.B "  flashrom -p dummy:spi_blacklist=commandlist"
.sp
565 566 567
syntax where
.B commandlist
is a list of two-digit hexadecimal representations of
568
SPI commands. If commandlist is e.g.\& 0302, flashrom will behave as if the SPI
569 570 571 572
controller refuses to run command 0x03 (READ) and command 0x02 (WRITE).
commandlist may be up to 512 characters (256 commands) long.
Implementation note: flashrom will detect an error during command execution.
.sp
Stefan Tauner's avatar
Stefan Tauner committed
573 574 575
.TP
.B SPI ignorelist
.sp
576 577 578 579 580
To simulate a flash chip which ignores (doesn't support) certain SPI commands,
you can specify an ignorelist of SPI commands with the
.sp
.B "  flashrom -p dummy:spi_ignorelist=commandlist"
.sp
581 582 583
syntax where
.B commandlist
is a list of two-digit hexadecimal representations of
584
SPI commands. If commandlist is e.g.\& 0302, the emulated flash chip will ignore
585 586 587
command 0x03 (READ) and command 0x02 (WRITE).  commandlist may be up to 512
characters (256 commands) long.
Implementation note: flashrom won't detect an error during command execution.
588 589 590 591 592 593 594 595
.sp
.TP
.B SPI status register
.sp
You can specify the initial content of the chip's status register with the
.sp
.B "  flashrom -p dummy:spi_status=content"
.sp
596 597 598
syntax where
.B content
is an 8-bit hexadecimal value.
Stefan Tauner's avatar
Stefan Tauner committed
599
.SS
600
.BR "nic3com" , " nicrealtek" , " nicnatsemi" , " nicintel", " nicintel_eeprom"\
601
, " nicintel_spi" , " gfxnvidia" , " ogp_spi" , " drkaiser" , " satasii"\
602
, " satamv" , " atahpt", " atavia " and " it8212 " programmers
Michael Karcher's avatar
Michael Karcher committed
603 604 605
These programmers have an option to specify the PCI address of the card
your want to use, which must be specified if more than one card supported
by the selected programmer is installed in your system. The syntax is
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
606 607 608
.sp
.BR "  flashrom \-p xxxx:pci=bb:dd.f" ,
.sp
609
where
610
.B xxxx
611
is the name of the programmer,
612 613 614 615 616
.B bb
is the PCI bus number,
.B dd
is the PCI device number, and
.B f
617
is the PCI function number of the desired device.
618 619
.sp
Example:
620
.B "flashrom \-p nic3com:pci=05:04.0"
Stefan Tauner's avatar
Stefan Tauner committed
621
.SS
622 623 624 625 626 627 628 629 630 631 632 633
.BR "atavia " programmer
Due to the mysterious address handling of the VIA VT6421A controller the user can specify an offset with the
.sp
.B "  flashrom \-p atavia:offset=addr"
.sp
syntax where
.B addr
will be interpreted as usual (leading 0x (0) for hexadecimal (octal) values, or else decimal).
For more information please see
.nh
.B http://flashrom.org/VT6421A
.SS
634 635 636 637 638 639 640 641
.BR "nicintel_eeprom " programmer
This is the first programmer module in flashrom that does not provide access to NOR flash chips but EEPROMs
mounted on gigabit Ethernet cards based on Intel's 82580 NIC. Because EEPROMs normally do not announce their
size nor allow to be identified, the controller relies on correct size values written to predefined addresses
within the chip. Flashrom follows this scheme but assumes the minimum size of 16 kB (128 kb) if an unprogrammed
EEPROM/card is detected. Intel specifies following EEPROMs to be compatible: Atmel AT25128, AT25256, Micron (ST)
M95128, M95256 and OnSemi (Catalyst) CAT25CS128.
.SS
642
.BR "ft2232_spi " programmer
643
An optional parameter specifies the controller
644
type and channel/interface/port it should support. For that you have to use the
645
.sp
646
.B "  flashrom \-p ft2232_spi:type=model,port=interface"
647
.sp
648 649
syntax where
.B model
Uwe Hermann's avatar
Uwe Hermann committed
650
can be
651
.BR 2232H ", " 4232H ", " 232H ", " jtagkey ", " busblaster ", " openmoko ", " \
652
arm-usb-tiny ", " arm-usb-tiny-h ", " arm-usb-ocd ", " arm-usb-ocd-h \
653
", " tumpa ", " tumpalite ", or " picotap
654 655
and
.B interface
Uwe Hermann's avatar
Uwe Hermann committed
656
can be
657
.BR A ", " B ", " C ", or " D .
658 659 660
The default model is
.B 4232H
and the default interface is
661
.BR A .
662
.sp
663 664 665 666 667 668 669 670 671
If there is more than one ft2232_spi-compatible device connected, you can select which one should be used by
specifying its serial number with the
.sp
.B "  flashrom \-p ft2232_spi:serial=number"
.sp
syntax where
.B number
is the serial number of the device (which can be found for example in the output of lsusb -v).
.sp
672
All models supported by the ft2232_spi driver can configure the SPI clock rate by setting a divisor. The
673 674 675
expressible divisors are all
.B even
numbers between 2 and 2^17 (=131072) resulting in SPI clock frequencies of
676 677 678 679 680 681 682 683
6 MHz down to about 92 Hz for 12 MHz inputs. The default divisor is set to 2, but you can use another one by
specifying the optional
.B divisor
parameter with the
.sp
.B "  flashrom \-p ft2232_spi:divisor=div"
.sp
syntax.
Stefan Tauner's avatar
Stefan Tauner committed
684
.SS
Michael Karcher's avatar
Michael Karcher committed
685 686
.BR "serprog " programmer
A mandatory parameter specifies either a serial
687
device/baud combination or an IP/port combination for communication with the
Michael Karcher's avatar
Michael Karcher committed
688 689
programmer. In the device/baud combination, the device has to start with a
slash. For serial, you have to use the
690
.sp
691
.B "  flashrom \-p serprog:dev=/dev/device:baud"
692
.sp
693
syntax and for IP, you have to use
694
.sp
695
.B "  flashrom \-p serprog:ip=ipaddr:port"
696
.sp
697 698 699
instead. In case the device supports it, you can set the SPI clock frequency
with the optional
.B spispeed
700
parameter. The frequency is parsed as hertz, unless an
701 702 703 704
.BR M ", or " k
suffix is given, then megahertz or kilohertz are used respectively.
Example that sets the frequency to 2 MHz:
.sp
705
.B "  flashrom \-p serprog:dev=/dev/device:baud,spispeed=2M"
706 707
.sp
More information about serprog is available in
708 709
.B serprog-protocol.txt
in the source distribution.
Stefan Tauner's avatar
Stefan Tauner committed
710
.SS
711
.BR "buspirate_spi " programmer
712 713 714 715 716
A required
.B dev
parameter specifies the Bus Pirate device node and an optional
.B spispeed
parameter specifies the frequency of the SPI bus. The parameter
Michael Karcher's avatar
Michael Karcher committed
717
delimiter is a comma. Syntax is
718
.sp
Uwe Hermann's avatar
Uwe Hermann committed
719
.B "  flashrom \-p buspirate_spi:dev=/dev/device,spispeed=frequency"
Michael Karcher's avatar
Michael Karcher committed
720
.sp
721 722
where
.B frequency
Uwe Hermann's avatar
Uwe Hermann committed
723 724
can be
.BR 30k ", " 125k ", " 250k ", " 1M ", " 2M ", " 2.6M ", " 4M " or " 8M
Michael Karcher's avatar
Michael Karcher committed
725
(in Hz). The default is the maximum frequency of 8 MHz.
726 727 728 729 730 731 732 733 734 735 736 737 738 739
.sp
An optional pullups parameter specifies the use of the Bus Pirate internal pull-up resistors. This may be
needed if you are working with a flash ROM chip that you have physically removed from the board. Syntax is
.sp
.B "  flashrom -p buspirate_spi:pullups=state"
.sp
where
.B state
can be
.BR on " or " off .
More information about the Bus Pirate pull-up resistors and their purpose is available at
.nh
.BR "http://dangerousprototypes.com/docs/Practical_guide_to_Bus_Pirate_pull-up_resistors " .
Only the external supply voltage (Vpu) is supported as of this writing.
Stefan Tauner's avatar
Stefan Tauner committed
740
.SS
741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768
.BR "pickit2_spi " programmer
An optional
.B voltage
parameter specifies the voltage the PICkit2 should use. The default unit is Volt if no unit is specified.
You can use
.BR mV ", " millivolt ", " V " or " Volt
as unit specifier. Syntax is
.sp
.B "  flashrom \-p pickit2_spi:voltage=value"
.sp
where
.B value
can be
.BR 0V ", " 1.8V ", " 2.5V ", " 3.5V
or the equivalent in mV.
.sp
An optional
.B spispeed
parameter specifies the frequency of the SPI bus. Syntax is
.sp
.B "  flashrom \-p pickit2_spi:spispeed=frequency"
.sp
where
.B frequency
can be
.BR 250k ", " 333k ", " 500k " or " 1M "
(in Hz). The default is a frequency of 1 MHz.
.SS
769
.BR "dediprog " programmer
770 771 772 773 774 775 776
An optional
.B voltage
parameter specifies the voltage the Dediprog should use. The default unit is
Volt if no unit is specified. You can use
.BR mV ", " milliVolt ", " V " or " Volt
as unit specifier. Syntax is
.sp
Uwe Hermann's avatar
Uwe Hermann committed
777
.B "  flashrom \-p dediprog:voltage=value"
778 779 780
.sp
where
.B value
Uwe Hermann's avatar
Uwe Hermann committed
781
can be
782 783
.BR 0V ", " 1.8V ", " 2.5V ", " 3.5V
or the equivalent in mV.
784 785 786 787 788 789 790 791 792
.sp
An optional
.B device
parameter specifies which of multiple connected Dediprog devices should be used.
Please be aware that the order depends on libusb's usb_get_busses() function and that the numbering starts
at 0.
Usage example to select the second device:
.sp
.B "  flashrom \-p dediprog:device=1"
793 794 795
.sp
An optional
.B spispeed
796 797
parameter specifies the frequency of the SPI bus. The firmware on the device needs to be 5.0.0 or newer.
Syntax is
798 799 800 801 802 803 804 805
.sp
.B "  flashrom \-p dediprog:spispeed=frequency"
.sp
where
.B frequency
can be
.BR 375k ", " 750k ", " 1.5M ", " 2.18M ", " 3M ", " 8M ", " 12M " or " 24M
(in Hz). The default is a frequency of 12 MHz.
806 807 808 809 810 811 812 813 814 815 816
.sp
An optional
.B target
parameter specifies which target chip should be used. Syntax is
.sp
.B "  flashrom \-p dediprog:target=value"
.sp
where
.B value
can be
.BR 1 " or " 2
817
to select target chip 1 or 2 respectively. The default is target chip 1.
Stefan Tauner's avatar
Stefan Tauner committed
818
.SS
819
.BR "rayer_spi " programmer
820 821 822 823 824 825 826 827 828 829 830 831
The default I/O base address used for the parallel port is 0x378 and you can use
the optional
.B iobase
parameter to specify an alternate base I/O address with the
.sp
.B "  flashrom \-p rayer_spi:iobase=baseaddr"
.sp
syntax where
.B baseaddr
is base I/O port address of the parallel port, which must be a multiple of
four. Make sure to not forget the "0x" prefix for hexadecimal port addresses.
.sp
832 833 834 835 836 837 838 839 840
The default cable type is the RayeR cable. You can use the optional
.B type
parameter to specify the cable type with the
.sp
.B "  flashrom \-p rayer_spi:type=model"
.sp
syntax where
.B model
can be
841
.BR rayer " for the RayeR cable, " byteblastermv " for the Altera ByteBlasterMV, " stk200 " for the Atmel \
842
STK200/300, " wiggler " for the Macraigor Wiggler, or " xilinx " for the Xilinx Parallel Cable III (DLC 5)."
843 844
.sp
More information about the RayeR hardware is available at
845
.nh
846
.BR "http://rayer.ic.cz/elektro/spipgm.htm " .
847 848 849
The Altera ByteBlasterMV datasheet can be obtained from
.nh
.BR "http://www.altera.co.jp/literature/ds/dsbytemv.pdf " .
850 851 852
For more information about the Macraigor Wiggler see
.nh
.BR "http://www.macraigor.com/wiggler.htm " .
853
The schematic of the Xilinx DLC 5 was published in
854
.nh
855
.BR "http://www.xilinx.com/support/documentation/user_guides/xtp029.pdf " .
Stefan Tauner's avatar
Stefan Tauner committed
856
.SS
857 858 859
.BR "pony_spi " programmer
The serial port (like /dev/ttyS0, /dev/ttyUSB0 on Linux or COM3 on windows) is
specified using the mandatory
860
.B dev
861 862 863
parameter. The adapter type is selectable between SI-Prog (used for
SPI devices with PonyProg 2000) or a custom made serial bitbanging programmer
named "serbang". The optional
864
.B type
865 866 867
parameter accepts the values "si_prog" (default) or "serbang".
.sp
Information about the SI-Prog adapter can be found at
868
.nh
869 870 871 872 873 874 875 876 877
.BR "http://www.lancos.com/siprogsch.html " .
.sp
An example call to flashrom is
.sp
.B "  flashrom \-p pony_spi:dev=/dev/ttyS0,type=serbang"
.sp
Please note that while USB-to-serial adapters work under certain circumstances,
this slows down operation considerably.
.SS
878
.BR "ogp_spi " programmer
Stefan Tauner's avatar
Stefan Tauner committed
879
The flash ROM chip to access must be specified with the
880 881 882 883 884 885 886 887 888 889 890
.B rom
parameter.
.sp
.B "  flashrom \-p ogp_spi:rom=name"
.sp
Where
.B name
is either
.B cprom
or
.B s3
891
for the configuration ROM and
892 893 894
.B bprom
or
.B bios
Uwe Hermann's avatar
Uwe Hermann committed
895
for the BIOS ROM. If more than one card supported by the ogp_spi programmer
896 897 898 899
is installed in your system, you have to specify the PCI address of the card
you want to use with the
.B pci=
parameter as explained in the
900
.B nic3com et al.\&
901 902 903
section above.
.sp
More information about the hardware is available at
904
.nh
905
.BR http://wiki.opengraphics.org .
906 907 908 909 910 911 912 913 914 915
.SS
.BR "linux_spi " programmer
You have to specify the SPI controller to use with the
.sp
.B "  flashrom \-p linux_spi:dev=/dev/spidevX.Y"
.sp
syntax where
.B /dev/spidevX.Y
is the Linux device node for your SPI controller.
.sp
916 917 918 919 920 921 922
In case the device supports it, you can set the SPI clock frequency with the optional
.B spispeed
parameter. The frequency is parsed as kilohertz.
Example that sets the frequency to 8 MHz:
.sp
.B "  flashrom \-p linux_spi:dev=/dev/spidevX.Y,spispeed=8000"
.sp
923
Please note that the linux_spi driver only works on Linux.
924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968
.SS
.BR "mstarddc_spi " programmer
The Display Data Channel (DDC) is an I2C bus present on VGA and DVI connectors, that allows exchanging
informations between a computer and attached displays. Its most common uses are getting display capabilities
through EDID (at I2C address 0x50) and sending commands to the display using the DDC/CI protocol (at address
0x37). On displays driven by MSTAR SoCs, it is also possible to access the SoC firmware flash (connected to
the Soc through another SPI bus) using an In-System Programming (ISP) port, usually at address 0x49.
This flashrom module allows the latter via Linux's I2C driver.
.sp
.B IMPORTANT:
Before using this programmer, the display
.B MUST
be in standby mode, and only connected to the computer that will run flashrom using a VGA cable, to an
inactive VGA output. It absolutely
.B MUST NOT
be used as a display during the procedure!
.sp
You have to specify the DDC/I2C controller and I2C address to use with the
.sp
.B "  flashrom \-p mstarddc_spi:dev=/dev/i2c-X:YY"
.sp
syntax where
.B /dev/i2c-X
is the Linux device node for your I2C controller connected to the display's DDC channel, and
.B YY
is the (hexadecimal) address of the MSTAR ISP port (address 0x49 is usually used).
Example that uses I2C controller /dev/i2c-1 and address 0x49:
.sp
.B "  flashrom \-p mstarddc_spi:dev=/dev/i2c-1:49
.sp
It is also possible to inhibit the reset command that is normally sent to the display once the flashrom
operation is completed using the optional
.B noreset
parameter. A value of 1 prevents flashrom from sending the reset command.
Example that does not reset the display at the end of the operation:
.sp
.B "  flashrom \-p mstarddc_spi:dev=/dev/i2c-1:49,noreset=1
.sp
Please note that sending the reset command is also inhibited in the event an error occured during the operation.
To send the reset command afterwards, you can simply run flashrom once more, in chip probe mode (not specifying
an operation), without the
.B noreset
parameter, once the flash read/write operation you intended to perform has completed successfully.
.sp
Please also note that the mstarddc_spi driver only works on Linux.
969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987
.SH EXAMPLES
To back up and update your BIOS, run
.sp
.B flashrom -p internal -r backup.rom -o backuplog.txt
.br
.B flashrom -p internal -w newbios.rom -o writelog.txt
.sp
Please make sure to copy backup.rom to some external media before you try
to write. That makes offline recovery easier.
.br
If writing fails and flashrom complains about the chip being in an unknown
state, you can try to restore the backup by running
.sp
.B flashrom -p internal -w backup.rom -o restorelog.txt
.sp
If you encounter any problems, please contact us and supply
backuplog.txt, writelog.txt and restorelog.txt. See section
.B BUGS
for contact info.
988
.SH EXIT STATUS
989
flashrom exits with 0 on success, 1 on most failures but with 3 if a call to mmap() fails.
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
990 991 992 993 994 995 996
.SH REQUIREMENTS
flashrom needs different access permissions for different programmers.
.sp
.B internal
needs raw memory access, PCI configuration space access, raw I/O port
access (x86) and MSR access (x86).
.sp
997 998 999
.B atavia
needs PCI configuration space access.
.sp
1000
.BR nic3com ", " nicrealtek " and " nicnatsemi "
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1001 1002 1003 1004 1005
need PCI configuration space read access and raw I/O port access.
.sp
.B atahpt
needs PCI configuration space access and raw I/O port access.
.sp
Kyösti Mälkki's avatar
Kyösti Mälkki committed
1006
.BR gfxnvidia ", " drkaiser " and " it8212
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1007 1008
need PCI configuration space access and raw memory access.
.sp
1009 1010 1011
.B rayer_spi
needs raw I/O port access.
.sp
1012 1013
.BR satasii ", " nicintel ", " nicintel_eeprom " and " nicintel_spi
need PCI configuration space read access and raw memory access.
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1014
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1015 1016 1017 1018
.B satamv
needs PCI configuration space read access, raw I/O port access and raw memory
access.
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1019 1020 1021 1022 1023 1024
.B serprog
needs TCP access to the network or userspace access to a serial port.
.sp
.B buspirate_spi
needs userspace access to a serial port.
.sp
1025
.BR dediprog ", " ft2232_spi " and " usbblaster_spi and " pickit2_spi
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1026 1027 1028 1029 1030
need access to the USB device via libusb.
.sp
.B dummy
needs no access permissions at all.
.sp
1031
.BR internal ", " nic3com ", " nicrealtek ", " nicnatsemi ", "
1032
.BR gfxnvidia ", " drkaiser ", " satasii ", " satamv ", " atahpt" and " atavia
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1033 1034
have to be run as superuser/root, and need additional raw access permission.
.sp
1035
.BR serprog ", " buspirate_spi ", " dediprog ", " usbblaster_spi " and " ft2232_spi and " pickit2_spi
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1036 1037 1038
can be run as normal user on most operating systems if appropriate device
permissions are set.
.sp
1039 1040 1041
.B ogp
needs PCI configuration space read access and raw memory access.
.sp
Carl-Daniel Hailfinger's avatar
Carl-Daniel Hailfinger committed
1042
On OpenBSD, you can obtain raw access permission by setting
1043 1044 1045 1046
.B "securelevel=-1"
in
.B "/etc/rc.securelevel"
and rebooting, or rebooting into single user mode.
1047
.SH BUGS
Stefan Tauner's avatar
Stefan Tauner committed
1048
Please report any bugs to the flashrom mailing list at
1049 1050 1051
.B "<flashrom@flashrom.org>"
.sp
We recommend to subscribe first at
1052 1053
.sp
.B "  http://www.flashrom.org/mailman/listinfo/flashrom"
1054
.sp
Stefan Tauner's avatar
Stefan Tauner committed
1055 1056 1057 1058 1059
Many of the developers communicate via the
.B "#flashrom"
IRC channel on
.BR chat.freenode.net .
You are welcome to join and ask questions, send us bug and success reports there
1060
too. Please provide a way to contact you later (e.g.\& a mail address) and be
Stefan Tauner's avatar
Stefan Tauner committed
1061 1062
patient if there is no immediate reaction. Also, we provide a pastebin service
at
1063
.nh
Stefan Tauner's avatar
Stefan Tauner committed
1064
.B http://paste.flashrom.org
1065
that is very useful when you want to share logs etc.\& without spamming the
Stefan Tauner's avatar
Stefan Tauner committed
1066 1067 1068
channel.
.SS
.B Laptops
1069
.sp
Stefan Tauner's avatar
Stefan Tauner committed
1070 1071 1072 1073 1074 1075 1076 1077
Using flashrom on laptops is dangerous and may easily make your hardware
unusable. flashrom will attempt to detect if it is running on a laptop and abort
immediately for safety reasons. Please see the detailed discussion of this topic
and associated flashrom options in the
.B Laptops
paragraph in the
.B internal programmer
subsection of the
1078
.B PROGRAMMER-SPECIFIC INFORMATION
1079 1080
section and the information in our wiki at
.BR "http://www.flashrom.org/Laptops " .
1081 1082 1083 1084 1085
.SS
One-time programmable (OTP) memory and unique IDs
.sp
Some flash chips contain OTP memory often denoted as "security registers".
They usually have a capacity in the range of some bytes to a few hundred
1086
bytes and can be used to give devices unique IDs etc.  flashrom is not able
1087 1088 1089 1090 1091 1092
to read or write these memories and may therefore not be able to duplicate a
chip completely. For chip types known to include OTP memories a warning is
printed when they are detected.
.sp
Similar to OTP memories are unique, factory programmed, unforgeable IDs.
They are not modifiable by the user at all.
1093
.SH LICENSE
1094
.B flashrom
1095 1096
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).
1097 1098
.SH COPYRIGHT
.br
1099 1100
Please see the individual files.
.SH AUTHORS
1101
Andrew Morgan
1102
.br
1103
Carl-Daniel Hailfinger
1104
.br
1105
Claus Gindhart
1106
.br
1107
David Borg
1108
.br
1109
David Hendricks
1110
.br
1111
Dominik Geyer
1112
.br
1113
Eric Biederman
1114
.br
1115
Giampiero Giancipoli
1116
.br
1117
Helge Wagner
1118
.br
1119
Idwer Vollering
1120
.br
1121
Joe Bao
1122
.br
1123
Joerg Fischer
1124
.br
1125
Joshua Roys
1126
.br
1127 1128
Ky\[:o]sti M\[:a]lkki
.br
1129
Luc Verhaegen
1130
.br
1131 1132
Li-Ta Lo
.br
1133 1134
Mark Marshall
.br
1135
Markus Boas
1136
.br
1137
Mattias Mattsson
1138
.br
1139
Michael Karcher
1140
.br
1141
Nikolay Petukhov
1142
.br
1143
Patrick Georgi
1144
.br
1145
Peter Lemenkov
1146
.br
1147
Peter Stuge
1148
.br
1149
Reinder E.N. de Haan
1150
.br
1151
Ronald G. Minnich
1152
.br
1153
Ronald Hoogenboom
1154
.br
1155
Sean Nelson
1156
.br
1157
Stefan Reinauer
1158
.br
Uwe Hermann's avatar
Uwe Hermann committed
1159 1160
Stefan Tauner
.br
1161
Stefan Wildemann
1162
.br
1163
Stephan Guilloux
1164
.br
1165
Steven James
1166
.br
1167
Uwe Hermann
1168
.br
1169
Wang Qingpei
1170
.br
1171
Yinghai Lu
1172
.br
1173 1174
some others, please see the flashrom svn changelog for details.
.br
1175
All still active authors can be reached via email at <flashrom@flashrom.org>.
1176
.PP
1177 1178
This manual page was written by Uwe Hermann <uwe@hermann-uwe.de>,
Carl-Daniel Hailfinger and others.
1179
It is licensed under the terms of the GNU GPL (version 2 or later).