Next: Programmers accepting extended parameters, Previous: Command Line Options, Up: Command Line Options
AVRDUDE is a command line tool, used as follows:
avrdude -p partno options ...
Command line options are used to control AVRDUDE's behaviour. The following options are recognized:
-p
partnoc128 | AT90CAN128
|
pwm2 | AT90PWM2
|
pwm3 | AT90PWM3
|
1200 | AT90S1200
|
2313 | AT90S2313
|
2333 | AT90S2333
|
2343 | AT90S2343 (*)
|
4414 | AT90S4414
|
4433 | AT90S4433
|
4434 | AT90S4434
|
8515 | AT90S8515
|
8535 | AT90S8535
|
m103 | ATmega103
|
m128 | ATmega128
|
m1280 | ATmega1280
|
m1281 | ATmega1281
|
m1284p | ATmega1284P
|
m128rfa1 | ATmega128RFA1
|
m16 | ATmega16
|
m161 | ATmega161
|
m162 | ATmega162
|
m163 | ATmega163
|
m164 | ATmega164
|
m169 | ATmega169
|
m2560 | ATmega2560 (**)
|
m2561 | ATmega2561 (**)
|
m32 | ATmega32
|
m324 | ATmega324
|
m329 | ATmega329
|
m3290 | ATmega3290
|
m48 | ATmega48
|
m64 | ATmega64
|
m640 | ATmega640
|
m644 | ATmega644
|
m649 | ATmega649
|
m6490 | ATmega6490
|
m8 | ATmega8
|
m8515 | ATmega8515
|
m8535 | ATmega8535
|
m88 | ATmega88
|
t12 | ATtiny12
|
t13 | ATtiny13
|
t15 | ATtiny15
|
t2313 | ATtiny2313
|
t25 | ATtiny25
|
t26 | ATtiny26
|
t45 | ATtiny45
|
t85 | ATtiny85
|
x128a1 | ATxmega128A1
|
x128a1d | ATxmega128A1revD
|
(*) The AT90S2323 and ATtiny22 use the same algorithm.
(**) Flash addressing above 128 KB is not supported by all
programming hardware. Known to work are jtag2, stk500v2,
and bit-bang programmers.
-b
baudrate-B
bitclock-c
programmer-idabcmini |
ABCmini Board, aka Dick Smith HOTCHIP
|
alf |
Nightshade ALF-PgmAVR, http://nightshade.homeip.net/ |
arduino
Arduino board, protocol similar to STK500 1.x
| |
atisp |
AT-ISP V1.1 programming cable for AVR-SDK1 from, http://micro-research.co.th/ |
avr109 |
Atmel AppNote AVR109 Boot Loader
|
avr910 |
Atmel Low Cost Serial Programmer
|
avr911 |
Atmel AppNote AVR911 AVROSP (an alias for avr109)
|
avrisp |
Atmel AVR ISP (an alias for stk500)
|
avrisp2 |
Atmel AVR ISP mkII (alias for stk500v2)
|
avrispmkII |
Atmel AVR ISP mkII (alias for stk500v2)
|
avrispv2 |
Atmel AVR ISP, running a version 2.x firmware (an alias for stk500v2)
|
bascom |
Bascom SAMPLE programming cable
|
blaster |
Altera ByteBlaster
|
bsd |
Brian Dean's Programmer, http://www.bsdhome.com/avrdude/ |
butterfly |
Atmel Butterfly Development Board
|
c2n232i |
C2N232I, reset=dtr sck=!rts mosi=!txd miso=!cts, http://www.ktverkko.fi/~msmakela/8bit/c2n232/hardware/index.en.html |
dapa |
Direct AVR Parallel Access cable
|
dasa |
serial port banging, reset=rts sck=dtr mosi=txd miso=cts
|
dasa3 |
serial port banging, reset=!dtr sck=rts mosi=txd miso=cts
|
dragon_dw |
AVR Dragon in debugWire mode
|
dragon_hvsp |
AVR Dragon in high-voltage serial programming mode
|
dragon_isp |
AVR Dragon in ISP mode
|
dragon_jtag |
AVR Dragon in JTAG mode
|
dragon_pp |
AVR Dragon in (high-voltage) parallel programming mode
|
dt006 |
Dontronics DT006
|
ere-isp-avr |
ERE ISP-AVR, http://www.ere.co.th/download/sch050713.pdf |
frank-stk200 |
Frank's STK200 clone, http://electropol.free.fr/spip/spip.php?article15 |
futurlec |
Futurlec.com programming cable
|
jtag1 |
Atmel JTAG ICE mkI, running at 115200 Bd
|
jtag1slow |
Atmel JTAG ICE mkI, running at 19200 Bd
|
jtag2slow |
Atmel JTAG ICE mkII (default speed 19200 Bd)
|
jtag2 |
Atmel JTAG ICE mkII, running at 115200 Bd
|
jtag2fast |
Atmel JTAG ICE mkII, running at 115200 Bd
|
jtag2isp |
Atmel JTAG ICE mkII in ISP mode.
|
jtag2dw |
Atmel JTAG ICE mkII in debugWire mode.
|
jtagmkI |
Atmel JTAG ICE mkI, running at 115200 Bd
|
jtagmkII |
Atmel JTAG ICE mkII (default speed 19200 Bd)
|
mib510 |
Crossbow MIB510 programming board
|
pavr |
Jason Kyle's pAVR Serial Programmer
|
picoweb |
Picoweb Programming Cable, http://www.picoweb.net/ |
pony-stk200 |
Pony Prog STK200
|
ponyser |
design ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts
|
siprog |
Lancos SI-Prog, http://www.lancos.com/siprogsch.html |
sp12 |
Steve Bolt's Programmer
|
stk200 |
STK200
|
stk500 |
Atmel STK500, probing for either version 1.x or 2.x firmware
|
stk500hvsp |
Atmel STK500 in high-voltage serial programming mode(version 2.x firmware only)
|
stk500pp |
Atmel STK500 in parallel programming mode (version 2.xfirmware only)
|
stk500v1 |
Atmel STK500, running a version 1.x firmware
|
stk500v2 |
Atmel STK500, running a version 2.x firmware
|
stk600 |
Atmel STK600 in ISP mode, or in PDI mode for ATxmega devices
|
stk600hvsp |
Atmel STK600 in high-voltage serial programming mode
|
stk600pp |
Atmel STK600 in parallel programming mode
|
usbasp |
USBasp, http://www.fischl.de/usbasp/ |
usbtiny |
USBtiny simple USB programmer, http://www.ladyada.net/make/usbtinyisp/ |
xil |
Xilinx JTAG cable
|
-C
config-file-D
-e
-E
exitspec[,...]
reset
noreset
vcc
novcc
Multiple exitspec arguments can be separated with commas.
-F
-i
delay-n
-O
-P
portOn Win32 operating systems, the parallel ports are referred to as lpt1 through lpt3, referring to the addresses 0x378, 0x278, and 0x3BC, respectively. If the parallel port can be accessed through a different address, this address can be specified directly, using the common C language notation (i. e., hexadecimal values are prefixed by 0x).
For the JTAG ICE mkII, if AVRDUDE has been built with libusb support,
port may alternatively be specified as
usb
[:serialno]. In that case, the JTAG ICE mkII will be
looked up on USB. If serialno is also specified, it will be
matched against the serial number read from any JTAG ICE mkII found on
USB. The match is done after stripping any existing colons from the
given serial number, and right-to-left, so only the least significant
bytes from the serial number need to be given.
For a trick how to find out the serial numbers of all JTAG ICEs
attached to USB, see Example Command Line Invocations.
As the AVRISP mkII device can only be talked to over USB, the very same method of specifying the port is required there.
For the USB programmer "AVR-Doper" running in HID mode, the port must be specified as avrdoper. Libusb support is required on Unix but not on Windows. For more information about AVR-Doper see http://www.obdev.at/avrusb/avrdoper.html.
For programmers that attach to a serial port using some kind of
higher level protocol (as opposed to bit-bang style programmers),
port can be specified as net
:host:port.
In this case, instead of trying to open a local device, a TCP
network connection to (TCP) port on host
is established.
The remote endpoint is assumed to be a terminal or console server
that connects the network stream to a local serial port where the
actual programmer has been attached to.
The port is assumed to be properly configured, for example using a
transparent 8-bit data connection without parity at 115200 Baud
for a STK500.
This feature is currently not implemented for Win32 systems.
-q
-u
-t
-U
memtype:
op:
filename[:
format]
part
command from
terminal mode to display all the memory types supported by a particular
device.
Typically, a device's memory configuration at least contains
the memory types
flash
and
eeprom
.
All memory types currently known are:
calibration
eeprom
efuse
flash
fuse
hfuse
lfuse
lock
signature
The op field specifies what operation to perform:
r
w
v
The filename field indicates the name of the file to read or write. The format field is optional and contains the format of the file to read or write. Possible values are:
i
s
r
m
0x
,
it is treated as a hex value. If the number otherwise begins with a
leading zero (0
) it is treated as octal. Otherwise, the value is
treated as decimal.
a
d
h
o
b
The default is to use auto detection for input files, and raw binary format for output files.
Note that if filename contains a colon, the format field is no longer optional since the filename part following the colon would otherwise be misinterpreted as format.
As an abbreviation, the form -U
filename
is equivalent to specifying
-U
flash:w:filename:a.
This will only work if filename does not have a colon in it.
-v
-V
-x
extended_param-y
-Y
cycles