Changeset 922
- Timestamp:
- Mar 7, 2010 1:11:08 PM (3 years ago)
- File:
-
- 1 edited
-
trunk/flashrom.8 (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/flashrom.8
r908 r922 132 132 easily pasted into the wiki page at http://www.flashrom.org/. 133 133 .TP 134 .B "\-p, \-\-programmer <name> "134 .B "\-p, \-\-programmer <name>[:parameters]" 135 135 Specify the programmer device. Currently supported are: 136 136 .sp … … 157 157 .BR "* buspiratespi" " (for flash ROMs attached to a Bus Pirate)" 158 158 .sp 159 The dummy programmer has an optional parameter specifying the bus types it 159 Some programmers have optional or mandatory parameters which are described 160 in detail in the 161 .B PROGRAMMER SPECIFIC INFO 162 section. Support for some programmers can be disabled at compile time. 163 .B "flashrom -h" 164 lists all supported programmers. 165 .TP 166 .B "\-h, \-\-help" 167 Show a help text and exit. 168 .TP 169 .B "\-R, \-\-version" 170 Show version information and exit. 171 .SH PROGRAMMER SPECIFIC INFO 172 Some programmer drivers accept further parameters to set programmer-specific 173 parameters. These parameters are seperated from the programmer name by a 174 colon. While some programmers take arguments at fixed positions, other 175 programmers use a key/value interface in which the key and value is separated 176 by an equal sign and different pairs are separated by a comma or a colon. 177 .TP 178 .BR "dummy " programmer 179 An optional parameter specifies the bus types it 160 180 should support. For that you have to use the 161 181 .B "flashrom -p dummy:type" … … 168 188 Example: 169 189 .B "flashrom -p dummy:lpc,fwh" 170 .sp 171 If you have multiple supported PCI cards which can program flash chips 172 (NICs, SATA/IDE controllers, etc.) in your system, you must use the 190 .TP 191 .BR "nic3com" , " gfxnvidia" , " satasii" and " atahpt " programmers 192 These programmers have an option to specify the PCI address of the card 193 your want to use, which must be specified if more than one card supported 194 by the selected programmer is installed in your system. The syntax is 173 195 .B "flashrom -p xxxx:bb:dd.f" 174 syntax to explicitly select one of them, where196 , where 175 197 .B xxxx 176 198 is the name of the programmer … … 184 206 Example: 185 207 .B "flashrom -p nic3com:05:04.0" 186 .sp 187 Currently the following programmers support this mechanism: 188 .BR nic3com , 189 .BR gfxnvidia , 190 .BR satasii , 191 .BR atahpt . 192 .sp 193 The it87spi programmer has an optional parameter which will set the I/O base 194 port of the IT87* SPI controller interface to the port specified in the 195 parameter. For that you have to use the 208 .TP 209 .BR "it87spi " programmer 210 An optional parameter sets the I/O base port of the IT87* SPI controller 211 interface to the port specified in the parameter instead of using the port 212 address set by the BIOS. For that you have to use the 196 213 .B "flashrom -p it87spi:port=portnum" 197 214 syntax where 198 215 .B portnum 199 216 is an I/O port number which must be a multiple of 8. 200 .sp 201 The ft2232spi programmer has an optional parameter specifying the controller 217 .TP 218 .BR "ft2232spi " programmer 219 An optional parameter species the controller 202 220 type and interface/port it should support. For that you have to use the 203 221 .B "flashrom -p ft2232spi:model,port=interface" … … 209 227 .B interface 210 228 can be any of 211 .B A 212 .BR B . 229 .BR "A B" . 213 230 The default model is 214 231 .B 4232H 215 232 and the default interface is 216 233 .BR B . 217 .sp 218 The serprog programmer has an optional parameter specifying either a serial 234 .TP 235 .BR "serprog " programmer 236 A mandatory parameter specifies either a serial 219 237 device/baud combination or an IP/port combination for communication with the 220 programmer. For serial, you have to use the 238 programmer. In the device/baud combination, the device has to start with a 239 slash. For serial, you have to use the 221 240 .B "flashrom -p serprog:/dev/device:baud" 222 241 syntax and for IP, you have to use … … 224 243 instead. More information about serprog is available in serprog-protocol.txt in 225 244 the source distribution. 226 .sp 227 The buspiratespi programmer has a required dev parameter specifying the Bus 228 Pirate device node and an optional spispeed parameter specifying the frequency 229 of the SPI bus. The parameter delimiter is a comma. Syntax is 245 .TP 246 .BR "buspiratespi " programmer 247 A required dev parameter specifyies the Bus Pirate device node and an optional 248 spispeed parameter specifyies the frequency of the SPI bus. The parameter 249 delimiter is a comma. Syntax is 250 .sp 230 251 .B "flashrom -p buspiratespi:dev=/dev/device,spispeed=frequency" 252 .sp 231 253 where 232 254 .B frequency 233 255 can be any of 234 256 .B 30k 125k 250k 1M 2M 2.6M 4M 8M 235 (in Hz). 236 .sp 237 Support for some programmers can be disabled at compile time. 238 .B "flashrom -h" 239 lists all supported programmers. 240 .TP 241 .B "\-h, \-\-help" 242 Show a help text and exit. 243 .TP 244 .B "\-R, \-\-version" 245 Show version information and exit. 257 (in Hz). The default is the maximum frequency of 8 MHz. 246 258 .SH EXIT STATUS 247 259 flashrom exits with 0 on success, 1 on most failures but with 2 if /dev/mem
Note: See TracChangeset
for help on using the changeset viewer.
