/usr/share/doc/avrdude/avrdude-html/Programmers-accepting-extended-parameters.html is in avrdude-doc 6.3-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.4.90, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Programmers accepting extended parameters (AVRDUDE)</title>
<meta name="description" content="Programmers accepting extended parameters (AVRDUDE)">
<meta name="keywords" content="Programmers accepting extended parameters (AVRDUDE)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Command-Line-Options.html#Command-Line-Options" rel="up" title="Command Line Options">
<link href="Example-Command-Line-Invocations.html#Example-Command-Line-Invocations" rel="next" title="Example Command Line Invocations">
<link href="Option-Descriptions.html#Option-Descriptions" rel="prev" title="Option Descriptions">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Programmers-accepting-extended-parameters"></a>
<div class="header">
<p>
Next: <a href="Example-Command-Line-Invocations.html#Example-Command-Line-Invocations" accesskey="n" rel="next">Example Command Line Invocations</a>, Previous: <a href="Option-Descriptions.html#Option-Descriptions" accesskey="p" rel="prev">Option Descriptions</a>, Up: <a href="Command-Line-Options.html#Command-Line-Options" accesskey="u" rel="up">Command Line Options</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Programmers-accepting-extended-parameters-1"></a>
<h3 class="section">2.2 Programmers accepting extended parameters</h3>
<dl compact="compact">
<dt><code>JTAG ICE mkII/3</code></dt>
<dt><code>AVR Dragon</code></dt>
<dd>
<p>When using the JTAG ICE mkII/3 or AVR Dragon in JTAG mode, the
following extended parameter is accepted:
</p><dl compact="compact">
<dt><code>‘<samp>jtagchain=UB,UA,BB,BA</samp>’</code></dt>
<dd><p>Setup the JTAG scan chain for <var>UB</var> units before, <var>UA</var> units
after, <var>BB</var> bits before, and <var>BA</var> 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.
</p></dd>
</dl>
</dd>
<dt><code>AVR910</code></dt>
<dd>
<p>The AVR910 programmer type accepts the following extended parameter:
</p><dl compact="compact">
<dt><code>‘<samp>devcode=VALUE</samp>’</code></dt>
<dd><p>Override the device code selection by using <var>VALUE</var>
as the device code.
The programmer is not queried for the list of supported
device codes, and the specified <var>VALUE</var>
is not verified but used directly within the
<code>T</code> command sent to the programmer.
<var>VALUE</var> can be specified using the conventional number notation of the
C programming language.
</p></dd>
<dt><code>‘<samp>no_blockmode</samp>’</code></dt>
<dd><p>Disables the default checking for block transfer capability.
Use
‘<samp>no_blockmode</samp>’ only if your ‘<samp>AVR910</samp>’
programmer creates errors during initial sequence.
</p></dd>
</dl>
</dd>
<dt><code>BusPirate</code></dt>
<dd>
<p>The BusPirate programmer type accepts the following extended parameters:
</p><dl compact="compact">
<dt><code>‘<samp>reset=cs,aux,aux2</samp>’</code></dt>
<dd><p>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
<em>CS</em>
pin, second AVR’s RESET connected to BusPirate’s
<em>AUX</em>
pin and if your BusPirate has an
<em>AUX2</em>
pin (only available on BusPirate version v1a with firmware 3.0 or newer)
use that to activate RESET on the third AVR.
</p>
<p>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.
</p>
</dd>
<dt><code>‘<samp>spifreq=<var>0..7</var></samp>’</code></dt>
<dd><table>
<tr><td width="5%"><code>0</code></td><td width="30%">30 kHz (default)</td></tr>
<tr><td width="5%"><code>1</code></td><td width="30%">125 kHz</td></tr>
<tr><td width="5%"><code>2</code></td><td width="30%">250 kHz</td></tr>
<tr><td width="5%"><code>3</code></td><td width="30%">1 MHz</td></tr>
<tr><td width="5%"><code>4</code></td><td width="30%">2 MHz</td></tr>
<tr><td width="5%"><code>5</code></td><td width="30%">2.6 MHz</td></tr>
<tr><td width="5%"><code>6</code></td><td width="30%">4 MHz</td></tr>
<tr><td width="5%"><code>7</code></td><td width="30%">8 MHz</td></tr>
</table>
</dd>
<dt><code>‘<samp>rawfreq=0..3</samp>’</code></dt>
<dd><p>Sets the SPI speed and uses the Bus Pirate’s binary “raw-wire” mode instead
of the default binary SPI mode:
</p>
<table>
<tr><td width="5%"><code>0</code></td><td width="30%">5 kHz</td></tr>
<tr><td width="5%"><code>1</code></td><td width="30%">50 kHz</td></tr>
<tr><td width="5%"><code>2</code></td><td width="30%">100 kHz (Firmware v4.2+ only)</td></tr>
<tr><td width="5%"><code>3</code></td><td width="30%">400 kHz (v4.2+)</td></tr>
</table>
<p>The only advantage of the “raw-wire” mode is that different SPI frequencies
are available. Paged writing is not implemented in this mode.
</p>
</dd>
<dt><code>‘<samp>ascii</samp>’</code></dt>
<dd><p>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
‘<samp>reset=</samp>’, ‘<samp>spifreq=</samp>’
and
‘<samp>rawfreq=</samp>’
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.
</p>
</dd>
<dt><code>‘<samp>nopagedwrite</samp>’</code></dt>
<dd><p>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.
</p>
</dd>
<dt><code>‘<samp>nopagedread</samp>’</code></dt>
<dd><p>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.
</p>
</dd>
<dt><code>‘<samp>cpufreq=<var>125..4000</var></samp>’</code></dt>
<dd><p>This sets the <em>AUX</em> pin to output a frequency of <var>n</var> kHz. Connecting
the <em>AUX</em> 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.
</p>
</dd>
<dt><code>‘<samp>serial_recv_timeout=<var>1...</var></samp>’</code></dt>
<dd><p>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.
</p>
</dd>
</dl>
</dd>
<dt><code>Wiring</code></dt>
<dd>
<p>When using the Wiring programmer type, the
following optional extended parameter is accepted:
</p><dl compact="compact">
<dt><code>‘<samp>snooze=<var>0..32767</var></samp>’</code></dt>
<dd><p>After performing the port open phase, AVRDUDE will wait/snooze for
<var>snooze</var> milliseconds before continuing to the protocol sync phase.
No toggling of DTR/RTS is performed if <var>snooze</var> > 0.
</p></dd>
</dl>
</dd>
<dt><code>PICkit2</code></dt>
<dd><p>Connection to the PICkit2 programmer:
</p><table>
<tr><td width="5%"><code>(AVR)</code></td><td width="30%"><code>(PICkit2)</code></td></tr>
<tr><td width="5%"><code>RST</code></td><td width="30%"><code>VPP/MCLR (1) </code></td></tr>
<tr><td width="5%"><code>VDD</code></td><td width="30%"><code>VDD Target (2) -- possibly optional if AVR self powered </code></td></tr>
<tr><td width="5%"><code>GND</code></td><td width="30%"><code>GND (3) </code></td></tr>
<tr><td width="5%"><code>MISO</code></td><td width="30%"><code>PGD (4) </code></td></tr>
<tr><td width="5%"><code>SCLK</code></td><td width="30%"><code>PDC (5) </code></td></tr>
<tr><td width="5%"><code>OSI</code></td><td width="30%"><code>AUX (6) </code></td></tr>
</table>
<p>Extended command line parameters:
</p><dl compact="compact">
<dt><code>‘<samp>clockrate=<var>rate</var></samp>’</code></dt>
<dd><p>Sets the SPI clocking rate in Hz (default is 100kHz). Alternately the -B or -i options can be used to set the period.
</p></dd>
<dt><code>‘<samp>timeout=<var>usb-transaction-timeout</var></samp>’</code></dt>
<dd><p>Sets the timeout for USB reads and writes in milliseconds (default is 1500 ms).
</p></dd>
</dl>
</dd>
</dl>
<hr>
<div class="header">
<p>
Next: <a href="Example-Command-Line-Invocations.html#Example-Command-Line-Invocations" accesskey="n" rel="next">Example Command Line Invocations</a>, Previous: <a href="Option-Descriptions.html#Option-Descriptions" accesskey="p" rel="prev">Option Descriptions</a>, Up: <a href="Command-Line-Options.html#Command-Line-Options" accesskey="u" rel="up">Command Line Options</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
</body>
</html>
|