[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

2.2 Programmers accepting extended parameters

JTAG ICE mkII
AVR Dragon

When using the JTAG ICE mkII 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.

speed=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

ascii

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=’ and ‘speed=’ parameters unavailable.

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.


[ < ] [ > ]   [ << ] [ Up ] [ >> ]

This document was generated on August 22, 2013 using texi2html 1.82.