| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] | 
The following commands are implemented:
dump memtype [start_addr [nbytes]]Read nbytes from the specified memory area, and display them in the usual hexadecimal and ASCII form.
dump memtype [start_addr] …Start reading from start_addr, all the way to the last memory address.
dump memtypeContinue dumping the memory contents for another nbytes where the previous dump command left off.
write memtype start_addr data1 data2 … dataNManually program the respective memory cells, starting at address start_addr, using the values data1 through dataN. This feature is not implemented for bank-addressed memories such as the flash memory of ATMega devices.
Items dataN can have the following formats:
| Type | Example | Size (bytes) | 
| Character | 'A' | 1 | 
| Decimal integer | 12345 | 1, 2, 4, or 8 (see below) | 
| Octal integer | 012345 | 1, 2, 4, or 8 (see below) | 
| Hexadecimal integer | 0x12345 | 1, 2, 4, or 8 (see below) | 
| Float | 3.1415926 | 4 | 
Integer constants can be 1, 2, 4, or 8 bytes long. By default, the smallest possible size will be used where the specified number just fits into. A specific size can be denoted by appending one of these suffixes:
LLll8 bytes / 64 bits
Ll4 bytes / 32 bits
HhSs2 bytes / 16 bits
HHhh1 byte / 8 bits
Similarly, floating-point constants can have an F or f
appended, but only 32-bit floating-point values are supported.
write memtype start_addr length data1 data2 dataN …Similar to the above, but length byte of the memory are written. For that purpose, after writing the initial items, dataN is replicated as many times as needed.
erasePerform a chip erase.
send b1 b2 b3 b4Send raw instruction codes to the AVR device. If you need access to a feature of an AVR part that is not directly supported by AVRDUDE, this command allows you to use it, even though AVRDUDE does not implement the command. When using direct SPI mode, up to 3 bytes can be omitted.
sigDisplay the device signature bytes.
spiEnter direct SPI mode. The pgmled pin acts as slave select. Only supported on parallel bitbang programmers, and partially by USBtiny. Slave Select must be externally held low for direct SPI when using USBtinyISP, and send must be a multiple of four bytes.
partDisplay the current part settings and parameters. Includes chip specific information including all memory types supported by the device, read/write timing, etc.
pgmReturn to programming mode (from direct SPI mode).
verbose [level]Change (when level is provided), or display the verbosity
level.
The initial verbosity level is controlled by the number of -v options
given on the command line.
?helpGive a short on-line summary of the available commands.
quitLeave terminal mode and thus AVRDUDE.
In addition, the following commands are supported on the STK500 and STK600 programmer:
vtarg voltageSet the target’s supply voltage to voltage Volts.
varef [channel] voltageSet the adjustable voltage source to voltage Volts. This voltage is normally used to drive the target’s Aref input on the STK500 and STK600. The STK600 offers two reference voltages, which can be selected by the optional parameter channel (either 0 or 1).
fosc freq[M|k]Set the master oscillator to freq Hz.
An optional trailing letter M
multiplies by 1E6, a trailing letter k by 1E3.
fosc offTurn the master oscillator off.
sck periodSTK500 and STK600 only: Set the SCK clock period to period microseconds.
JTAG ICE only: Set the JTAG ICE bit clock period to period microseconds. Note that unlike STK500 settings, this setting will be reverted to its default value (approximately 1 microsecond) when the programming software signs off from the JTAG ICE. This parameter can also be used on the JTAG ICE mkII/3 to specify the ISP clock period when operating the ICE in ISP mode.
parmsSTK500 and STK600 only: Display the current voltage and master oscillator parameters.
JTAG ICE only: Display the current target supply voltage and JTAG bit clock rate/period.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] | 
 
  This document was generated on May 7, 2022 using texi2html 5.0.