AVRDUDE: 2.2 Programmers accepting extended parameters

[ << ] | [ < ] | [] | [ > ] | [ >> ] |  |  |  |  | [] | [] | [] | [ ? ]

## 2.2 Programmers accepting extended parameters

`JTAG ICE mkII/3`
`AVR Dragon`

  When using the JTAG ICE mkII/3 or AVR Dragon in JTAG mode, the following extended parameter is accepted:

  `‘`jtagchain=UB,UA,BB,BA`’`

    Setup the JTAG scan chain for UB units before, UA units after, BB bits before, and BA bits after the target AVR, respectively. Each AVR unit within the chain shifts by 4 bits. Other JTAG units might require a different bit shift count.

`AVR910`

  The AVR910 programmer type accepts the following extended parameter:

  `‘`devcode=VALUE`’`

    Override the device code selection by using VALUE as the device code. The programmer is not queried for the list of supported device codes, and the specified VALUE is not verified but used directly within the `T` command sent to the programmer. VALUE can be specified using the conventional number notation of the C programming language.

  `‘`no_blockmode`’`

    Disables the default checking for block transfer capability. Use ‘`no_blockmode`’ only if your ‘`AVR910`’ programmer creates errors during initial sequence.

`BusPirate`

  The BusPirate programmer type accepts the following extended parameters:

  `‘`reset=cs,aux,aux2`’`

    The default setup assumes the BusPirate’s CS output pin connected to the RESET pin on AVR side. It is however possible to have multiple AVRs connected to the same BP with MISO, MOSI and SCK lines common for all of them. In such a case one AVR should have its RESET connected to BusPirate’s CS pin, second AVR’s RESET connected to BusPirate’s AUX pin and if your BusPirate has an AUX2 pin (only available on BusPirate version v1a with firmware 3.0 or newer) use that to activate RESET on the third AVR.

    It may be a good idea to decouple the BusPirate and the AVR’s SPI buses from each other using a 3-state bus buffer. For example 74HC125 or 74HC244 are some good candidates with the latches driven by the appropriate reset pin (cs, aux or aux2). Otherwise the SPI traffic in one active circuit may interfere with programming the AVR in the other design.

  `‘`spifreq=0..7`’`

    `0` | 30 kHz (default)
    `1` | 125 kHz
    `2` | 250 kHz
    `3` | 1 MHz
    `4` | 2 MHz
    `5` | 2.6 MHz
    `6` | 4 MHz
    `7` | 8 MHz

  `‘`rawfreq=0..3`’`

    Sets the SPI speed and uses the Bus Pirate’s binary “raw-wire” mode instead of the default binary SPI mode:

    `0` | 5 kHz
    `1` | 50 kHz
    `2` | 100 kHz (Firmware v4.2+ only)
    `3` | 400 kHz (v4.2+)

    The only advantage of the “raw-wire” mode is that different SPI frequencies are available. Paged writing is not implemented in this mode.

  `‘`ascii`’`

    Attempt to use ASCII mode even when the firmware supports BinMode (binary mode). BinMode is supported in firmware 2.7 and newer, older FW’s either don’t have BinMode or their BinMode is buggy. ASCII mode is slower and makes the above ‘`reset=`’, ‘`spifreq=`’ and ‘`rawfreq=`’ parameters unavailable. Be aware that ASCII mode is not guaranteed to work with newer firmware versions, and is retained only to maintain compatibility with older firmware versions.

  `‘`nopagedwrite`’`

    Firmware versions 5.10 and newer support a binary mode SPI command that enables whole pages to be written to AVR flash memory at once, resulting in a significant write speed increase. If use of this mode is not desirable for some reason, this option disables it.

  `‘`nopagedread`’`

    Newer firmware versions support in binary mode SPI command some AVR Extended Commands. Using the “Bulk Memory Read from Flash” results in a significant read speed increase. If use of this mode is not desirable for some reason, this option disables it.

  `‘`cpufreq=125..4000`’`

    This sets the AUX pin to output a frequency of n kHz. Connecting the AUX pin to the XTAL1 pin of your MCU, you can provide it a clock, for example when it needs an external clock because of wrong fuses settings. Make sure the CPU frequency is at least four times the SPI frequency.

  `‘`serial_recv_timeout=1...`’`

    This sets the serial receive timeout to the given value. The timeout happens every time avrdude waits for the BusPirate prompt. Especially in ascii mode this happens very often, so setting a smaller value can speed up programming a lot. The default value is 100ms. Using 10ms might work in most cases.

`Wiring`

  When using the Wiring programmer type, the following optional extended parameter is accepted:

  `‘`snooze=0..32767`’`

    After performing the port open phase, AVRDUDE will wait/snooze for snooze milliseconds before continuing to the protocol sync phase. No toggling of DTR/RTS is performed if snooze > 0.

`PICkit2`

  Connection to the PICkit2 programmer:

  `(AVR)` | `(PICkit2)`
  `RST` | `VPP/MCLR (1)`
  `VDD` | `VDD Target (2) -- possibly optional if AVR self powered`
  `GND` | `GND (3)`
  `MISO` | `PGD (4)`
  `SCLK` | `PDC (5)`
  `OSI` | `AUX (6)`

  Extended command line parameters:

  `‘`clockrate=rate`’`

    Sets the SPI clocking rate in Hz (default is 100kHz). Alternately the -B or -i options can be used to set the period.

  `‘`timeout=usb-transaction-timeout`’`

    Sets the timeout for USB reads and writes in milliseconds (default is 1500 ms).

`USBasp`

  Extended parameters:

  `‘`section_config`’`

    Programmer will erase configuration section with option ’-e’ (chip erase), rather than entire chip. Only applicable to TPI devices (ATtiny 4/5/9/10/20/40).

`xbee`

  Extended parameters:

  `‘`xbeeresetpin=1..7`’`

    Select the XBee pin `DIO<1..7>` that is connected to the MCU’s ‘/RESET’ line. The programmer needs to know which DIO pin to use to reset into the bootloader. The default (3) is the `DIO3` pin (XBee pin 17), but some commercial products use a different XBee pin.

    The remaining two necessary XBee-to-MCU connections are not selectable - the XBee `DOUT` pin (pin 2) must be connected to the MCU’s ‘RXD’ line, and the XBee `DIN` pin (pin 3) must be connected to the MCU’s ‘TXD’ line.

[ << ] | [ < ] | [] | [ > ] | [ >> ]