Mirrors/avrdude
1
0
Fork 0
mirror of https://github.com/avrdudes/avrdude.git synced 2026-06-02 09:46:34 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update "current" documentation

Browse Source
This commit is contained in:
Joerg Wunsch
2023-01-09 20:43:22 +01:00
parent 9a1d96276d
commit c970e8d79c
44 changed files with 1126 additions and 732 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
docs/current/avrdude.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -72,7 +72,7 @@ code {
<h1>AVRDUDE</h1>
<h3 align="right">A program for download/uploading AVR microcontroller flash and eeprom.</h3>
<h3 align="right">For AVRDUDE, Version 6.99-20211218, 26 April 2022.</h3>
<h3 align="right">For AVRDUDE, Version 7.1, 3 January 2023.</h3>
<strong>by Brian S. Dean</strong><br>
@@ -182,9 +182,10 @@ emulated on top of USB is likely to not work at all, or to work
abysmally slow.
</p>
<p>If you happen to have a Linux system with at least 4 hardware GPIOs
available (like almost all embedded Linux boards) you can do without
any additional hardware - just connect them to the MOSI, MISO, RESET
and SCK pins on the AVR and use the linuxgpio programmer type. It bitbangs
available (like almost all embedded Linux boards) you can do without any
additional hardware - just connect them to the SDO, SDI, RESET and SCK
pins of the AVR&rsquo;s SPI interface and use the linuxgpio programmer
type. Older boards might use the labels MOSI for SDO and MISO for SDI. It bitbangs
the lines using the Linux sysfs GPIO interface. Of course, care should
be taken about voltage level compatibility. Also, although not strictly
required, it is strongly advisable to protect the GPIO pins from
@@ -199,7 +200,7 @@ programmer type can be used to directly connect to and program a chip
using the built in interfaces on the computer. The requirements to use
this type are that an SPI interface is exposed along with one GPIO
pin. The GPIO serves as the reset output since the Linux SPI drivers
do not hold slave select down when a transfer is not occuring and thus
do not hold chip select down when a transfer is not occuring and thus
it cannot be used as the reset pin. A readily available level
translator should be used between the SPI bus/reset GPIO and the chip
to avoid potentially damaging the computer&rsquo;s SPI controller in the
@@ -214,7 +215,7 @@ the level translator to protect the hardware from damage.
<p>On a Raspberry Pi, header J8 provides access to the SPI and GPIO
lines.
</p>
<p>Typically, pins 19, 21, and 23 are SPI MOSI, MISO, and SCK, while
<p>Typically, pins 19, 21, and 23 are SPI SDO, SDI, and SCK, while
pins 24 and 26 would serve as CE outputs. So, close to these pins
is pin 22 as GPIO25 which can be used as /RESET, and pin 25 can
be used as GND.
@@ -223,10 +224,10 @@ be used as GND.
</p>
<table>
<tr><td width="15%"><code>J8 pin</code></td><td width="15%"><code>ISP pin</code></td><td width="30%"><code>Name</code></td></tr>
<tr><td width="15%"><code>21</code></td><td width="15%"><code>1</code></td><td width="30%"><code>MISO</code></td></tr>
<tr><td width="15%"><code>21</code></td><td width="15%"><code>1</code></td><td width="30%"><code>SDI</code></td></tr>
<tr><td width="15%"><code>-</code></td><td width="15%"><code>2</code></td><td width="30%"><code>Vcc - leave open</code></td></tr>
<tr><td width="15%"><code>23</code></td><td width="15%"><code>3</code></td><td width="30%"><code>SCK</code></td></tr>
<tr><td width="15%"><code>19</code></td><td width="15%"><code>4</code></td><td width="30%"><code>MOSI</code></td></tr>
<tr><td width="15%"><code>19</code></td><td width="15%"><code>4</code></td><td width="30%"><code>SDO</code></td></tr>
<tr><td width="15%"><code>22</code></td><td width="15%"><code>5</code></td><td width="30%"><code>/RESET</code></td></tr>
<tr><td width="15%"><code>25</code></td><td width="15%"><code>6</code></td><td width="30%"><code>GND</code></td></tr>
</table>
@@ -242,7 +243,7 @@ programmers communicate through the USB, using <code>libusb</code> as a
platform abstraction layer.
The avrftdi adds support for the FT2232C/D, FT2232H, and FT4232H devices. These all use
the MPSSE mode, which has a specific pin mapping. Bit 1 (the lsb of the byte in the config
file) is SCK. Bit 2 is MOSI, and Bit 3 is MISO. Bit 4 usually reset. The 2232C/D parts
file) is SCK. Bit 2 is SDO, and Bit 3 is SDI. Bit 4 usually reset. The 2232C/D parts
are only supported on interface A, but the H parts can be either A or B (specified by the
usbdev config parameter).
The STK500, STK600, JTAG ICE, and avr910 contain on-board logic to control the programming of the target
@@ -269,7 +270,8 @@ See below for the limitations of debugWire.
For ATxmega devices, the JTAG ICE mkII/3 is supported in PDI mode, provided it
has a revision 1 hardware and firmware version of at least 5.37 (decimal).
</p>
<p>The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP modes).
<p>The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP,
UPDI).
</p>
<p>Atmel&rsquo;s XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are
supported by the &ldquo;jtag3&rdquo; programmer type.
@@ -297,14 +299,27 @@ the -D option will likely be required in this case, because the
bootloader will rewrite the program memory, but no true chip erase can
be performed.
</p>
<p>The Arduino (which is very similar to the STK500 1.x) is supported via
its own programmer type specification &ldquo;arduino&rdquo;. This programmer works for
<p>Serial bootloaders that run a skeleton of the STK500 1.x protocol are supported via
their own programmer type specification &ldquo;arduino&rdquo;. This programmer works for
the Arduino Uno Rev3 or any AVR that runs the Optiboot bootloader.
The number of connection retry attempts can be specified as an
extended parameter. See the section on
<em>extended parameters</em>
below for details.
</p>
<p>Urprotocol is a leaner version of the STK500 1.x protocol that is designed
to be backwards compatible with STK500 v1.x; it allows bootloaders to be
much smaller, e.g., as implemented in the urboot project
<a href="https://github.com/stefanrueger/urboot">https://github.com/stefanrueger/urboot</a>. The programmer type &ldquo;urclock&rdquo;
caters for these urboot bootloaders. Owing to its backward compatibility,
bootloaders that can be served by the arduino programmer can normally also
be served by the urclock programmer. This may require specifying the size
of (to AVRDUDE) <em>unknown</em> bootloaders in bytes using the <code>-x
bootsize=&lt;n&gt;</code> option, which is necessary for the urclock programmer to
enable it to protect the bootloader from being overwritten. If an unknown
bootloader has EEPROM read/write capability then the option <code>-x eepromrw</code>
informs <code>avrdude -c urclock</code> of that capability.
</p>
<p>The BusPirate is a versatile tool that can also be used as an AVR programmer.
A single BusPirate can be connected to up to 3 independent AVRs. See
the section on
@@ -320,7 +335,7 @@ an ATmega8 (or ATmega88), or ATtiny2313, respectively.
(AT90USB* and ATmega*U* devices), as well as version 2 (Xmega devices).
See below for some hints about FLIP version 1 protocol behaviour.
</p>
<p>The MPLAB(R) PICkit 4 and MPLAB(R) SNAP are supported in ISP, PDI and UPDI mode.
<p>The MPLAB(R) PICkit 4 and MPLAB(R) SNAP are supported in JTAG, TPI, ISP, PDI and UPDI mode.
The Curiosity Nano board is supported in UPDI mode. It is dubbed &ldquo;PICkit on
Board&rdquo;, thus the name <code>pkobn_updi</code>.
</p>
@@ -340,13 +355,13 @@ via a serial link (<a href="https://github.com/ElTangas/jtag2updi">https://githu
</p>
<p>The Micronucleus bootloader is supported for both protocol version V1
and V2. As the bootloader does not support reading from flash memory,
use the <code>-V</code> option to prevent AVRDUDE from verifing the flash memory.
use the <code>-V</code> option to prevent AVRDUDE from verifying the flash memory.
See the section on <em>extended parameters</em>
below for Micronucleus specific options.
</p>
<p>The Teensy bootloader is supported for all AVR boards.
As the bootloader does not support reading from flash memory,
use the <code>-V</code> option to prevent AVRDUDE from verifing the flash memory.
use the <code>-V</code> option to prevent AVRDUDE from verifying the flash memory.
See the section on <em>extended parameters</em>
below for Teensy specific options.
</p>
@@ -373,7 +388,7 @@ below for Teensy specific options.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

BIN
docs/current/avrdude.pdf
View File

Binary file not shown.

4
docs/current/avrdude_1.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -133,7 +133,7 @@ Roth.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_10.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -117,7 +117,7 @@ option.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

77
docs/current/avrdude_11.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -94,38 +94,60 @@ code {
</p>
<div class="smallexample">
<pre class="smallexample">programmer
parent &lt;id&gt; # &lt;id&gt; is a quoted string
id = &lt;id1&gt; [, &lt;id2&gt; [, &lt;id3&gt;] ...] ; # &lt;idN&gt; are quoted strings
desc = &lt;description&gt; ; # quoted string
type = &quot;par&quot; | &quot;stk500&quot; | ... ; # programmer type (see below for a list)
baudrate = &lt;num&gt; ; # baudrate for serial ports
vcc = &lt;num1&gt; [, &lt;num2&gt; ... ] ; # pin number(s)
buff = &lt;num1&gt; [, &lt;num2&gt; ... ] ; # pin number(s)
reset = &lt;num&gt; ; # pin number
sck = &lt;num&gt; ; # pin number
mosi = &lt;num&gt; ; # pin number
miso = &lt;num&gt; ; # pin number
errled = &lt;num&gt; ; # pin number
rdyled = &lt;num&gt; ; # pin number
pgmled = &lt;num&gt; ; # pin number
vfyled = &lt;num&gt; ; # pin number
usbvid = &lt;hexnum&gt;; # USB VID (Vendor ID)
usbpid = &lt;hexnum&gt; [, &lt;hexnum&gt; ...]; # USB PID (Product ID)
usbdev = &lt;interface&gt;; # USB interface or other device info
usbvendor = &lt;vendorname&gt;; # USB Vendor Name
usbproduct = &lt;productname&gt;; # USB Product Name
usbsn = &lt;serialno&gt;; # USB Serial Number
;
parent &lt;id&gt; # optional parent
id = &lt;id1&gt; [, &lt;id2&gt; ... ] ; # &lt;idN&gt; are quoted strings
desc = &lt;description&gt; ; # quoted string
type = &lt;type&gt;; # programmer type, quoted string
# supported types can be listed by &quot;-c ?type&quot;
prog_modes = PM_&lt;i/f&gt; { | PM_&lt;i/f&gt; } # interfaces, e.g., PM_SPM|PM_PDI
connection_type = parallel | serial | usb | spi
baudrate = &lt;num&gt; ; # baudrate for avr910-programmer
vcc = &lt;pin1&gt; [, &lt;pin2&gt; ... ] ; # pin number(s)
buff = &lt;pin1&gt; [, &lt;pin2&gt; ... ] ; # pin number(s)
reset = &lt;pin&gt; ; # pin number
sck = &lt;pin&gt; ; # pin number
sdo = &lt;pin&gt; ; # pin number
sdi = &lt;pin&gt; ; # pin number
errled = &lt;pin&gt; ; # pin number
rdyled = &lt;pin&gt; ; # pin number
pgmled = &lt;pin&gt; ; # pin number
vfyled = &lt;pin&gt; ; # pin number
usbvid = &lt;hexnum&gt; ; # USB VID (Vendor ID)
usbpid = &lt;hexnum&gt; [, &lt;hexnum&gt; ...] ; # USB PID (Product ID)
usbdev = &lt;interface&gt; ; # USB interface or other device info
usbvendor = &lt;vendorname&gt; ; # USB Vendor Name
usbproduct = &lt;productname&gt; ; # USB Product Name
usbsn = &lt;serialno&gt; ; # USB Serial Number
hvupdi_support = &lt;num&gt; [, &lt;num&gt;, ... ] ; # UPDI HV Variants Support
;
</pre></div>
<p>If a parent is specified, all settings of it (except its ids) are used for the new
programmer. These values can be changed by new setting them for the new programmer.
</p>
<p>To invert a bit in the pin definitions, use <code>= ~ &lt;num&gt;</code>.
<p>Known programming modes are
</p><ul>
<li> <code>PM_SPM</code>: Bootloaders, self-programming with SPM opcodes or NVM Controllers
</li><li> <code>PM_TPI</code>: Tiny Programming Interface (t4, t5, t9, t10, t20, t40, t102, t104)
</li><li> <code>PM_ISP</code>: SPI programming for In-System Programming (almost all classic parts)
</li><li> <code>PM_PDI</code>: Program and Debug Interface (xmega parts)
</li><li> <code>PM_UPDI</code>: Unified Program and Debug Interface
</li><li> <code>PM_HVSP</code>: High Voltage Serial Programming (some classic parts)
</li><li> <code>PM_HVPP</code>: High Voltage Parallel Programming (most non-HVSP classic parts)
</li><li> <code>PM_debugWIRE</code>: Simpler alternative to JTAG (a subset of HVPP/HVSP parts)
</li><li> <code>PM_JTAG</code>: Joint Test Action Group standard (some classic parts)
</li><li> <code>PM_JTAGmkI</code>: Subset of <code>PM_JTAG</code>, older parts, Atmel ICE mkI
</li><li> <code>PM_XMEGAJTAG</code>: JTAG, some XMEGA parts
</li><li> <code>PM_AVR32JTAG</code>: JTAG for 32-bit AVRs
</li><li> <code>PM_aWire</code>: AVR32 parts
</li></ul>
<p>To invert a bit in the pin definitions, use <code>= ~ &lt;num&gt;</code>. To invert a pin list
(all pins get inverted) use <code>~ ( &lt;num1&gt; [, &lt;num2&gt; ... ] )</code>.
</p>
<p>Not all programmer types can handle a list of USB PIDs.
</p>
<p>Following programmer types are currently implemented:
<p>The following programmer types are currently implemented:
</p>
<table>
<tr><td width="25%"><code>arduino</code></td><td width="60%">Arduino programmer</td></tr>
@@ -150,11 +172,13 @@ programmer. These values can be changed by new setting them for the new programm
<tr><td width="25%"><code>jtagmkii_dw</code></td><td width="60%">Atmel JTAG ICE mkII in debugWire mode</td></tr>
<tr><td width="25%"><code>jtagmkii_isp</code></td><td width="60%">Atmel JTAG ICE mkII in ISP mode</td></tr>
<tr><td width="25%"><code>jtagmkii_pdi</code></td><td width="60%">Atmel JTAG ICE mkII in PDI mode</td></tr>
<tr><td width="25%"><code>jtagmkii_updi</code></td><td width="60%">Atmel JTAG ICE mkII in UPDI mode</td></tr>
<tr><td width="25%"><code>jtagice3</code></td><td width="60%">Atmel JTAGICE3</td></tr>
<tr><td width="25%"><code>jtagice3_pdi</code></td><td width="60%">Atmel JTAGICE3 in PDI mode</td></tr>
<tr><td width="25%"><code>jtagice3_updi</code></td><td width="60%">Atmel JTAGICE3 in UPDI mode</td></tr>
<tr><td width="25%"><code>jtagice3_dw</code></td><td width="60%">Atmel JTAGICE3 in debugWire mode</td></tr>
<tr><td width="25%"><code>jtagice3_isp</code></td><td width="60%">Atmel JTAGICE3 in ISP mode</td></tr>
<tr><td width="25%"><code>jtagice3_tpi</code></td><td width="60%">Atmel JTAGICE3 in TPI mode</td></tr>
<tr><td width="25%"><code>linuxgpio</code></td><td width="60%">GPIO bitbanging using the Linux sysfs interface (not available)</td></tr>
<tr><td width="25%"><code>linuxspi</code></td><td width="60%">SPI using Linux spidev driver (not available)</td></tr>
<tr><td width="25%"><code>micronucleus</code></td><td width="60%">Micronucleus Bootloader</td></tr>
@@ -171,6 +195,7 @@ programmer. These values can be changed by new setting them for the new programm
<tr><td width="25%"><code>stk600hvsp</code></td><td width="60%">Atmel STK600 in high-voltage serial programming mode</td></tr>
<tr><td width="25%"><code>stk600pp</code></td><td width="60%">Atmel STK600 in parallel programming mode</td></tr>
<tr><td width="25%"><code>teensy</code></td><td width="60%">Teensy Bootloader</td></tr>
<tr><td width="25%"><code>urclock</code></td><td width="60%">Urclock programmer for urboot bootloaders (arduino compatible)</td></tr>
<tr><td width="25%"><code>usbasp</code></td><td width="60%">USBasp programmer, see http://www.fischl.de/usbasp/</td></tr>
<tr><td width="25%"><code>usbtiny</code></td><td width="60%">Driver for &quot;usbtiny&quot;-type programmers</td></tr>
<tr><td width="25%"><code>wiring</code></td><td width="60%">http://wiring.org.co/, Basically STK500v2 protocol, with some glue to trigger the bootloader.</td></tr>
@@ -195,7 +220,7 @@ programmer. These values can be changed by new setting them for the new programm
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

136
docs/current/avrdude_12.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -92,30 +92,38 @@ code {
<div class="smallexample">
<pre class="smallexample">part
id = &lt;id&gt; ; # quoted string
desc = &lt;description&gt; ; # quoted string
family_id = &lt;description&gt; ; # quoted string
has_jtag = &lt;yes/no&gt; ; # part has JTAG i/f
has_debugwire = &lt;yes/no&gt; ; # part has debugWire i/f
has_pdi = &lt;yes/no&gt; ; # part has PDI i/f
has_updi = &lt;yes/no&gt; ; # part has UPDI i/f
has_tpi = &lt;yes/no&gt; ; # part has TPI i/f
devicecode = &lt;num&gt; ; # numeric
id = &lt;id&gt; ; # quoted string
family_id = &lt;id&gt; ; # quoted string, e.g., &quot;megaAVR&quot; or &quot;tinyAVR&quot;
prog_modes = PM_&lt;i/f&gt; {| PM_&lt;i/f&gt;} # interfaces, e.g., PM_SPM|PM_ISP|PM_HVPP|PM_debugWIRE
mcuid = &lt;num&gt;; # unique id in 0..2039 for 8-bit AVRs
n_interrupts = &lt;num&gt;; # number of interrupts, used for vector bootloaders
n_page_erase = &lt;num&gt;; # if set, number of pages erased during SPM erase
n_boot_sections = &lt;num&gt;; # Number of boot sections
boot_section_size = &lt;num&gt;; # Size of (smallest) boot section, if any
hvupdi_variant = &lt;num&gt; ; # numeric -1 (n/a) or 0..2
devicecode = &lt;num&gt; ; # deprecated, use stk500_devcode
stk500_devcode = &lt;num&gt; ; # numeric
avr910_devcode = &lt;num&gt; ; # numeric
has_jtag = &lt;yes/no&gt; ; # part has JTAG i/f (deprecated, use prog_modes)
has_debugwire = &lt;yes/no&gt; ; # part has debugWire i/f (deprecated, use prog_modes)
has_pdi = &lt;yes/no&gt; ; # part has PDI i/f (deprecated, use prog_modes)
has_updi = &lt;yes/no&gt; ; # part has UPDI i/f (deprecated, use prog_modes)
has_tpi = &lt;yes/no&gt; ; # part has TPI i/f (deprecated, use prog_modes)
is_avr32 = &lt;yes/no&gt; ; # AVR32 part (deprecated, use prog_modes)
is_at90s1200 = &lt;yes/no&gt; ; # AT90S1200 part
signature = &lt;num&gt; &lt;num&gt; &lt;num&gt; ; # signature bytes
usbpid = &lt;num&gt; ; # DFU USB PID
reset = dedicated | io;
retry_pulse = reset | sck;
pgm_enable = &lt;instruction format&gt; ;
chip_erase = &lt;instruction format&gt; ;
chip_erase_delay = &lt;num&gt; ; # micro-seconds
reset = dedicated | io ;
retry_pulse = reset | sck ;
chip_erase_delay = &lt;num&gt; ; # chip erase delay (us)
# STK500 parameters (parallel programming IO lines)
pagel = &lt;num&gt; ; # pin name in hex, i.e., 0xD7
bs2 = &lt;num&gt; ; # pin name in hex, i.e., 0xA0
serial = &lt;yes/no&gt; ; # can use serial downloading
parallel = &lt;yes/no/pseudo&gt;; # can use par. programming
# STK500v2 parameters, to be taken from Atmel's XML files
parallel = &lt;yes/no/pseudo&gt; ; # can use par. programming
# STK500v2 parameters, to be taken from Atmel's ATDF files
timeout = &lt;num&gt; ;
stabdelay = &lt;num&gt; ;
cmdexedelay = &lt;num&gt; ;
@@ -126,52 +134,63 @@ code {
predelay = &lt;num&gt; ;
postdelay = &lt;num&gt; ;
pollmethod = &lt;num&gt; ;
mode = &lt;num&gt; ;
delay = &lt;num&gt; ;
blocksize = &lt;num&gt; ;
readsize = &lt;num&gt; ;
hvspcmdexedelay = &lt;num&gt; ;
# STK500v2 HV programming parameters, from XML
pp_controlstack = &lt;num&gt;, &lt;num&gt;, ...; # PP only
hvsp_controlstack = &lt;num&gt;, &lt;num&gt;, ...; # HVSP only
hventerstabdelay = &lt;num&gt;;
progmodedelay = &lt;num&gt;; # PP only
latchcycles = &lt;num&gt;;
togglevtg = &lt;num&gt;;
poweroffdelay = &lt;num&gt;;
resetdelayms = &lt;num&gt;;
resetdelayus = &lt;num&gt;;
hvleavestabdelay = &lt;num&gt;;
resetdelay = &lt;num&gt;;
synchcycles = &lt;num&gt;; # HVSP only
chiperasepulsewidth = &lt;num&gt;; # PP only
chiperasepolltimeout = &lt;num&gt;;
chiperasetime = &lt;num&gt;; # HVSP only
programfusepulsewidth = &lt;num&gt;; # PP only
programfusepolltimeout = &lt;num&gt;;
programlockpulsewidth = &lt;num&gt;; # PP only
programlockpolltimeout = &lt;num&gt;;
# JTAG ICE mkII parameters, also from XML files
# STK500v2 HV programming parameters, from ATDFs
pp_controlstack = &lt;num&gt;, &lt;num&gt;, ... ; # PP only
hvsp_controlstack = &lt;num&gt;, &lt;num&gt;, ... ; # HVSP only
flash_instr = &lt;num&gt;, &lt;num&gt;, &lt;num&gt; ;
eeprom_instr = &lt;num&gt;, &lt;num&gt;, ... ;
hventerstabdelay = &lt;num&gt; ;
progmodedelay = &lt;num&gt; ; # PP only
latchcycles = &lt;num&gt; ;
togglevtg = &lt;num&gt; ;
poweroffdelay = &lt;num&gt; ;
resetdelayms = &lt;num&gt; ;
resetdelayus = &lt;num&gt; ;
hvleavestabdelay = &lt;num&gt; ;
resetdelay = &lt;num&gt; ;
synchcycles = &lt;num&gt; ; # HVSP only
chiperasepulsewidth = &lt;num&gt; ; # PP only
chiperasepolltimeout = &lt;num&gt; ;
chiperasetime = &lt;num&gt; ; # HVSP only
programfusepulsewidth = &lt;num&gt; ; # PP only
programfusepolltimeout = &lt;num&gt; ;
programlockpulsewidth = &lt;num&gt; ; # PP only
programlockpolltimeout = &lt;num&gt; ;
# debugWIRE and/or JTAG ICE mkII parameters, also from ATDF files
allowfullpagebitstream = &lt;yes/no&gt; ;
enablepageprogramming = &lt;yes/no&gt; ;
idr = &lt;num&gt; ; # IO addr of IDR (OCD) reg.
rampz = &lt;num&gt; ; # IO addr of RAMPZ reg.
spmcr = &lt;num&gt; ; # mem addr of SPMC[S]R reg.
eecr = &lt;num&gt; ; # mem addr of EECR reg.
# (only when != 0x3c)
is_at90s1200 = &lt;yes/no&gt; ; # AT90S1200 part
is_avr32 = &lt;yes/no&gt; ; # AVR32 part
idr = &lt;num&gt; ; # IO addr of IDR (OCD) reg
rampz = &lt;num&gt; ; # IO addr of RAMPZ reg
spmcr = &lt;num&gt; ; # mem addr of SPMC[S]R reg
eecr = &lt;num&gt; ; # mem addr of EECR reg only when != 0x3f
eind = &lt;num&gt; ; # mem addr of EIND reg
mcu_base = &lt;num&gt; ;
nvm_base = &lt;num&gt; ;
ocd_base = &lt;num&gt; ;
ocdrev = &lt;num&gt; ;
pgm_enable = &lt;instruction format&gt; ;
chip_erase = &lt;instruction format&gt; ;
# parameters for bootloaders
autobaud_sync = &lt;num&gt; ; # autobaud detection byte, default 0x30
memory &lt;memtype&gt;
paged = &lt;yes/no&gt; ; # yes / no
paged = &lt;yes/no&gt; ; # yes/no (flash only, do not use for EEPROM)
offset = &lt;num&gt; ; # memory offset
size = &lt;num&gt; ; # bytes
page_size = &lt;num&gt; ; # bytes
num_pages = &lt;num&gt; ; # numeric
n_word_writes = &lt;num&gt; ; # TPI only: if set, number of words to write
min_write_delay = &lt;num&gt; ; # micro-seconds
max_write_delay = &lt;num&gt; ; # micro-seconds
readback_p1 = &lt;num&gt; ; # byte value
readback_p2 = &lt;num&gt; ; # byte value
pwroff_after_write = &lt;yes/no&gt; ; # yes / no
readback = &lt;num&gt; &lt;num&gt; ; # pair of byte values
readback_p1 = &lt;num&gt; ; # byte value (first component)
readback_p2 = &lt;num&gt; ; # byte value (second component)
pwroff_after_write = &lt;yes/no&gt; ; # yes/no
mode = &lt;num&gt; ; # STK500 v2 file parameter from ATDF files
delay = &lt;num&gt; ; # &quot;
blocksize = &lt;num&gt; ; # &quot;
readsize = &lt;num&gt; ; # &quot;
read = &lt;instruction format&gt; ;
write = &lt;instruction format&gt; ;
read_lo = &lt;instruction format&gt; ;
@@ -181,10 +200,19 @@ code {
loadpage_lo = &lt;instruction format&gt; ;
loadpage_hi = &lt;instruction format&gt; ;
writepage = &lt;instruction format&gt; ;
;
;
;
;
</pre></div>
<p>If any of the above parameters are not specified, the default value of 0
is used for numerics (except for <code>mcuid</code>, <code>hvupdi_variant</code> and
<code>ocdrev</code>, where the default value is -1, and for <code>autobaud_sync</code>
which defaults to 0x30) or the empty string <code>&quot;&quot;</code> for string values.
If a required parameter is left empty, AVRDUDE will complain. Almost all
occurrences of numbers (with the exception of pin numbers and where they
are separated by space, e.g., in signature and readback) can also be given
as simple expressions involving arithemtic and bitwise operators.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="avrdude_13.html#Parent-Part">4.3.1 Parent Part</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
</td></tr>
@@ -210,7 +238,7 @@ code {
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

21
docs/current/avrdude_13.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -90,11 +90,18 @@ code {
<a name="Parent-Part-1"></a>
<h3 class="subsection">4.3.1 Parent Part</h3>
<p>Parts can also inherit parameters from previously defined parts
using the following syntax. In this case specified integer and
string values override parameter values from the parent part. New
memory definitions are added to the definitions inherited from the
parent.
<p>Parts can also inherit parameters from previously defined parts using
the following syntax. In this case specified integer and string values
override parameter values from the parent part. New memory definitions
are added to the definitions inherited from the parent. If, however, a
new memory definition refers to an existing one of the same name for
that part then, from v7.1, the existing memory definition is extended,
and components overwritten with new values. Assigning <code>NULL</code>
removes an inherited SPI instruction format, memory definition, control
stack, eeprom or flash instruction, e.g., as in <code>memory &quot;efuse&quot; =
NULL;</code>
</p>
<p>Example format for part inheritance:
</p>
<div class="smallexample">
<pre class="smallexample"> part parent &lt;id&gt; # quoted string
@@ -106,7 +113,7 @@ parent.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

19
docs/current/avrdude_14.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -142,7 +142,22 @@ write = &quot;1 1 0 0 0 0 0 0 x x x x x x x x&quot;,
</pre></div>
<p>As the address bit numbers in the SPI opcodes are highly systematic, they
don&rsquo;t really need to be specified. A compact version of the format
specification neither uses bit-numbers for address lines nor spaces. If such
a string is longer than 7 characters, then the characters <code>0</code>, <code>1</code>,
<code>x</code>, <code>a</code>, <code>i</code> and <code>o</code> will be recognised as the
corresponding bit, whilst any of the characters <code>.</code>, <code>-</code>, <code>_</code>
or <code>/</code> can act as arbitrary visual separators, which are ignored.
Examples:
</p>
<div class="smallexample">
<pre class="smallexample">
loadpage_lo = &quot;0100.0000--000x.xxxx--xxaa.aaaa--iiii.iiii&quot;;
loadpage_lo = &quot;0100.0000&quot;, &quot;000x.xxxx&quot;, &quot;xxaa.aaaa&quot;, &quot;iiii.iiii&quot;;
</pre></div>
<hr>
<table class="header" cellpadding="1" cellspacing="1" border="0">
@@ -162,7 +177,7 @@ write = &quot;1 1 0 0 0 0 0 0 x x x x x x x x&quot;,
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_15.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -158,7 +158,7 @@ flash pages of the application section.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_16.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -102,7 +102,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_17.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -194,7 +194,7 @@ least 4.5 V in order to work. This can be done using
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_18.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -116,7 +116,7 @@ versions of the bootloader.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_19.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -203,7 +203,7 @@ analysis of UPDI protocol quirks easier.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_2.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -102,7 +102,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_20.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -100,7 +100,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_21.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -104,7 +104,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

12
docs/current/avrdude_22.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -93,8 +93,8 @@ code {
<p>To build and install from the source tarball on Unix like systems:
</p>
<div class="example">
<pre class="example">$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
$ cd avrdude-6.99-20211218
<pre class="example">$ gunzip -c avrdude-7.1.tar.gz | tar xf -
$ cd avrdude-7.1
$ ./configure
$ make
$ su root -c 'make install'
@@ -108,8 +108,8 @@ environment variable.
following instead:
</p>
<div class="example">
<pre class="example">$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
$ cd avrdude-6.99-20211218
<pre class="example">$ gunzip -c avrdude-7.1.tar.gz | tar xf -
$ cd avrdude-7.1
$ ./configure --prefix=$HOME/local
$ make
$ make install
@@ -125,7 +125,7 @@ $ make install
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_23.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -113,7 +113,7 @@ obtained.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

8
docs/current/avrdude_24.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -95,8 +95,8 @@ can build and install the rpm binaries directly from the tarball:
</p>
<div class="example">
<pre class="example">$ su - root
# rpmbuild -tb avrdude-6.99-20211218.tar.gz
# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-6.99-20211218-1.i386.rpm
# rpmbuild -tb avrdude-7.1.tar.gz
# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-7.1-1.i386.rpm
</pre></div>
<p>Note that the path to the resulting rpm package, differs from system
@@ -105,7 +105,7 @@ to system. The above example is specific to RedHat.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_25.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -107,7 +107,7 @@ augment the system default configuration file.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_26.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -96,7 +96,7 @@ configuration file is always <code>/usr/local/etc/avrdude.conf</code>.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_27.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -96,7 +96,7 @@ configuration file will be always be <code>/etc/avrdude.conf</code>.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_28.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -117,7 +117,7 @@ access.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_29.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -102,7 +102,7 @@ such as &lsquo;<samp>--prefix</samp>&rsquo;.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

972
docs/current/avrdude_3.html
View File

File diff suppressed because it is too large Load Diff

4
docs/current/avrdude_30.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -104,7 +104,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

8
docs/current/avrdude_31.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -102,8 +102,8 @@ The first one is to use Cygwin (<a href="http://www.cygwin.com/">http://www.cygw
<div class="example">
<pre class="example">$ set PREFIX=&lt;your install directory path&gt;
$ export PREFIX
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
$ cd avrdude-6.99-20211218
$ gunzip -c avrdude-7.1.tar.gz | tar xf -
$ cd avrdude-7.1
$ ./configure LDFLAGS=&quot;-static&quot; --prefix=$PREFIX --datadir=$PREFIX
--sysconfdir=$PREFIX/bin --enable-versioned-doc=no
$ make
@@ -122,7 +122,7 @@ compiler version that still supports MinGW builds, or use MinGW
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_32.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -100,7 +100,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_33.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -97,7 +97,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_34.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -125,7 +125,7 @@ The directories that are listed in the PATH environment variable.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_35.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -100,7 +100,7 @@ code {
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_36.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -96,7 +96,7 @@ Windows serial port device names such as: com1, com2, etc.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_37.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -121,7 +121,7 @@ language notation (i. e., hexadecimal values are prefixed by <code>0x</code>).
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_38.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -103,7 +103,7 @@ such as &lsquo;<samp>--prefix</samp>&rsquo; and &lsquo;<samp>--datadir</samp>&rs
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

37
docs/current/avrdude_39.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -280,10 +280,10 @@ Xmega device through PDI.
<table>
<tr><td width="20%"><strong>Dragon</strong></td><td width="20%"><strong>Target</strong></td></tr>
<tr><td width="20%"><strong>ISP Header</strong></td><td width="20%"><strong>pins</strong></td></tr>
<tr><td width="20%">1 (MISO)</td><td width="20%">PDI_DATA</td></tr>
<tr><td width="20%">1 (SDI)</td><td width="20%">PDI_DATA</td></tr>
<tr><td width="20%">2 (VCC)</td><td width="20%">VCC</td></tr>
<tr><td width="20%">3 (SCK)</td><td width="20%"></td></tr>
<tr><td width="20%">4 (MOSI)</td><td width="20%"></td></tr>
<tr><td width="20%">4 (SDO)</td><td width="20%"></td></tr>
<tr><td width="20%">5 (RESET)</td><td width="20%">PDI_CLK / RST</td></tr>
<tr><td width="20%">6 (GND)</td><td width="20%">GND</td></tr>
</table>
@@ -297,10 +297,10 @@ ATtiny4/5/9/10 device through TPI. How to connect the pins?
<table>
<tr><td width="20%"><strong>AVRISP</strong></td><td width="20%"><strong>Target</strong></td><td width="20%"><strong>ATtiny</strong></td></tr>
<tr><td width="20%"><strong>connector</strong></td><td width="20%"><strong>pins</strong></td><td width="20%"><strong>pin #</strong></td></tr>
<tr><td width="20%">1 (MISO)</td><td width="20%">TPIDATA</td><td width="20%">1</td></tr>
<tr><td width="20%">1 (SDI)</td><td width="20%">TPIDATA</td><td width="20%">1</td></tr>
<tr><td width="20%">2 (VTref)</td><td width="20%">Vcc</td><td width="20%">5</td></tr>
<tr><td width="20%">3 (SCK)</td><td width="20%">TPICLK</td><td width="20%">3</td></tr>
<tr><td width="20%">4 (MOSI)</td><td width="20%"></td><td width="20%"></td></tr>
<tr><td width="20%">4 (SDO)</td><td width="20%"></td><td width="20%"></td></tr>
<tr><td width="20%">5 (RESET)</td><td width="20%">/RESET</td><td width="20%">6</td></tr>
<tr><td width="20%">6 (GND)</td><td width="20%">GND</td><td width="20%">2</td></tr>
</table>
@@ -310,10 +310,10 @@ Problem: I want to program an ATtiny4/5/9/10 device using a serial/parallel
bitbang programmer. How to connect the pins?
<p>Solution: Since TPI has only 1 pin for bi-directional data transfer, both
<var>MISO</var> and <var>MOSI</var> pins should be connected to the <var>TPIDATA</var> pin
<var>SDI</var> and <var>SDO</var> pins should be connected to the <var>TPIDATA</var> pin
on the ATtiny device.
However, a 1K resistor should be placed between the <var>MOSI</var> and <var>TPIDATA</var>.
The <var>MISO</var> pin connects to <var>TPIDATA</var> directly.
However, a 1K resistor should be placed between the <var>SDO</var> and <var>TPIDATA</var>.
The <var>SDI</var> pin connects to <var>TPIDATA</var> directly.
The <var>SCK</var> pin is connected to <var>TPICLK</var>.
</p>
<p>In addition, the <var>Vcc</var>, <var>/RESET</var> and <var>GND</var> pins should
@@ -331,12 +331,12 @@ front of pins 7, 4, 3 and 8):
<div class="example">
<pre class="example">programmer
id = &quot;dasa_ftdi&quot;;
desc = &quot;serial port banging, reset=rts sck=dtr mosi=txd miso=cts&quot;;
desc = &quot;serial port banging, reset=rts sck=dtr sdo=txd sdi=cts&quot;;
type = serbb;
reset = ~7;
sck = ~4;
mosi = ~3;
miso = ~8;
sdo = ~3;
sdi = ~8;
;
</pre></div>
@@ -379,14 +379,15 @@ affected by this.
</li><li>
Problem: after flashing a firmware that reduces the target&rsquo;s clock
speed (e.g. through the <code>CLKPR</code> register), further ISP connection
attempts fail.
attempts fail. Or a programmer cannot initialize communication with
a brand new chip.
<p>Solution: Even though ISP starts with pulling <var>/RESET</var> low, the
target continues to run at the internal clock speed as defined by the
firmware running before. Therefore, the ISP clock speed must be
reduced appropriately (to less than 1/4 of the internal clock speed)
using the -B option before the ISP initialization sequence will
succeed.
target continues to run at the internal clock speed either as defined by
the firmware running before or as set by the factory. Therefore, the
ISP clock speed must be reduced appropriately (to less than 1/4 of the
internal clock speed) using the -B option before the ISP initialization
sequence will succeed.
</p>
<p>As that slows down the entire subsequent ISP session, it might make
sense to just issue a <em>chip erase</em> using the slow ISP clock
@@ -414,7 +415,7 @@ erase cycle.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

175
docs/current/avrdude_4.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -92,10 +92,15 @@ code {
<a name="index-_002dx-AVR-Dragon"></a>
<dl compact="compact">
<dt><code>JTAG ICE mkII/3</code></dt>
<dt><code>Atmel-ICE</code></dt>
<dt><code>PICkit 4</code></dt>
<dt><code>MPLAB SNAP</code></dt>
<dt><code>Power Debugger</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>When using the JTAG ICE mkII, JTAGICE3, Atmel-ICE, PICkit 4, MPLAB SNAP,
Power Debugger or AVR Dragon in JTAG mode, the following extended parameter
is accepted:
</p><dl compact="compact">
<dt><code>&lsquo;<samp>jtagchain=UB,UA,BB,BA</samp>&rsquo;</code></dt>
<dd><p>Setup the JTAG scan chain for <var>UB</var> units before, <var>UA</var> units
@@ -106,6 +111,15 @@ Other JTAG units might require a different bit shift count.
</p></dd>
</dl>
<p>The PICkit 4 and the Power Debugger also supports high-voltage UPDI programming.
This is used to enable a UPDI pin that has previously been set to RESET or
GPIO mode. High-voltage UPDI can be utilized by using an extended parameter:
</p><dl compact="compact">
<dt><code>&lsquo;<samp>hvupdi</samp>&rsquo;</code></dt>
<dd><p>Enable high-voltage UPDI initialization for targets that supports this.
</p></dd>
</dl>
<a name="index-_002dx-AVR910"></a>
</dd>
<dt><code>AVR910</code></dt>
@@ -141,6 +155,143 @@ programmer creates errors during initial sequence.
</p></dd>
</dl>
<a name="index-_002dx-Urclock"></a>
</dd>
<dt><code>Urclock</code></dt>
<dd>
<p>The urclock programmer type accepts the following extended parameters:
</p><dl compact="compact">
<dt><code>&lsquo;<samp>showall</samp>&rsquo;</code></dt>
<dd><p>Show all info for the connected part, then exit. The <code>-xshow...</code> options
below can be used to assemble a bespoke response consisting of a subset
(or only one item) of all available relevant information about the
connected part and bootloader.
</p></dd>
<dt><code>&lsquo;<samp>showid</samp>&rsquo;</code></dt>
<dd><p>Show a unique Urclock ID stored in either flash or EEPROM of the MCU, then exit.
</p></dd>
<dt><code>&lsquo;<samp>id=&lt;E|F&gt;.&lt;addr&gt;.&lt;len&gt;</samp>&rsquo;</code></dt>
<dd><p>Historically, the Urclock ID was a six-byte unique little-endian number
stored in Urclock boards at EEPROM address 257. The location of this
number can be set by the <code>-xid=&lt;E|F&gt;.&lt;addr&gt;.&lt;len&gt;</code> extended parameter. <code>E</code>
stands for EEPROM and <code>F</code> stands for flash. A negative address addr counts
from the end of EEPROM and flash, respectively. The length len of the
Urclock ID can be between 1 and 8 bytes.
</p></dd>
<dt><code>&lsquo;<samp>showdate</samp>&rsquo;</code></dt>
<dd><p>Show the last-modified date of the input file for the flash application,
then exit. If the input file was stdin, the date will be that of the
programming. Date and filename are part of the metadata that the urclock
programmer stores by default in high flash just under the bootloader; see also
<code>-xnometadata</code>.
</p></dd>
<dt><code>&lsquo;<samp>showfilename</samp>&rsquo;</code></dt>
<dd><p>Show the input filename (or title) of the last flash writing session, then exit.
</p></dd>
<dt><code>&lsquo;<samp>title=&lt;string&gt;</samp>&rsquo;</code></dt>
<dd><p>When set, &lt;string&gt; will be used in lieu of the input filename. The maximum
string length for the title/filename field is 254 bytes including
terminating nul.
</p></dd>
<dt><code>&lsquo;<samp>showapp</samp>&rsquo;</code></dt>
<dd><p>Show the size of the programmed application, then exit.
</p></dd>
<dt><code>&lsquo;<samp>showstore</samp>&rsquo;</code></dt>
<dd><p>Show the size of the unused flash between the application and metadata, then exit.
</p></dd>
<dt><code>&lsquo;<samp>showmeta</samp>&rsquo;</code></dt>
<dd><p>Show the size of the metadata just below the bootloader, then exit.
</p></dd>
<dt><code>&lsquo;<samp>showboot</samp>&rsquo;</code></dt>
<dd><p>Show the size of the bootloader, then exit.
</p></dd>
<dt><code>&lsquo;<samp>showversion</samp>&rsquo;</code></dt>
<dd><p>Show bootloader version and capabilities, then exit.
</p></dd>
<dt><code>&lsquo;<samp>showvector</samp>&rsquo;</code></dt>
<dd><p>Show the vector number and name of the interrupt table vector used by the
bootloader for starting the application, then exit. For hardware-supported
bootloaders this will be vector 0 (Reset), and for vector bootloaders this
will be any other vector number of the interrupt vector table or the slot
just behind the vector table with the name <code>VBL_ADDITIONAL_VECTOR</code>.
</p></dd>
<dt><code>&lsquo;<samp>showpart</samp>&rsquo;</code></dt>
<dd><p>Show the part for which the bootloader was compiled, then exit.
</p></dd>
<dt><code>&lsquo;<samp>bootsize=&lt;size&gt;</samp>&rsquo;</code></dt>
<dd><p>Manual override for bootloader size. Urboot bootloaders put the number of
used bootloader pages into a table at the top of the bootloader section,
ie, typically top of flash, so the urclock programmer can look up the
bootloader size itself. In backward-compatibility mode, when programming
via other bootloaders, this option can be used to tell the programmer the
size, and therefore the location, of the bootloader.
</p></dd>
<dt><code>&lsquo;<samp>vectornum=&lt;arg&gt;</samp>&rsquo;</code></dt>
<dd><p>Manual override for vector number. Urboot bootloaders put the vector
number used by a vector bootloader into a table at the top of flash, so
this option is normally not needed for urboot bootloaders. However, it is
useful in backward-compatibility mode (or when the urboot bootloader does
not offer flash read). Specifying a vector number in these circumstances
implies a vector bootloader whilst the default assumption would be a
hardware-supported bootloader.
</p></dd>
<dt><code>&lsquo;<samp>eepromrw</samp>&rsquo;</code></dt>
<dd><p>Manual override for asserting EEPROM read/write capability. Not normally
needed for urboot bootloaders, but useful for in backward-compatibility
mode if the bootloader offers EEPROM read/write.
</p></dd>
<dt><code>&lsquo;<samp>emulate_ce</samp>&rsquo;</code></dt>
<dd><p>If an urboot bootloader does not offer a chip erase command it will tell
the urclock programmer so during handshake. In this case the urclock
programmer emulates a chip erase, if warranted by user command line
options, by filling the remainder of unused flash below the bootloader
with 0xff. If this option is specified, the urclock programmer will assume
that the bootloader cannot erase the chip itself. The option is useful
for backwards-compatible bootloaders that do not implement chip erase.
</p></dd>
<dt><code>&lsquo;<samp>restore</samp>&rsquo;</code></dt>
<dd><p>Upload unchanged flash input files and trim below the bootloader if
needed. This is most useful when one has a backup of the full flash and
wants to play that back onto the device. No metadata are written in this
case and no vector patching happens either if it is a vector bootloader.
However, for vector bootloaders, even under the option <code>-xrestore</code> an
input file will not be uploaded for which the reset vector does not point
to the vector bootloader. This is to avoid writing an input file to the
device that would render the vector bootloader not functional as it would
not be reached after reset.
</p></dd>
<dt><code>&lsquo;<samp>initstore</samp>&rsquo;</code></dt>
<dd><p>On writing to flash fill the store space between the flash application and
the metadata section with 0xff.
</p></dd>
<dt><code>&lsquo;<samp>nofilename</samp>&rsquo;</code></dt>
<dd><p>On writing to flash do not store the application input filename (nor a title).
</p></dd>
<dt><code>&lsquo;<samp>nodate</samp>&rsquo;</code></dt>
<dd><p>On writing to flash do not store the application input filename (nor a
title) and no date either.
</p></dd>
<dt><code>&lsquo;<samp>nometadata</samp>&rsquo;</code></dt>
<dd><p>On writing to flash do not store any metadata. The full flash below the
bootloader is available for the application. In particular, no data store
frame is programmed.
</p></dd>
<dt><code>&lsquo;<samp>delay=&lt;n&gt;</samp>&rsquo;</code></dt>
<dd><p>Add a &lt;n&gt; ms delay after reset. This can be useful if a board takes a
particularly long time to exit from external reset. &lt;n&gt; can be negative,
in which case the default 120 ms delay after issuing reset will be
shortened accordingly.
</p></dd>
<dt><code>&lsquo;<samp>strict</samp>&rsquo;</code></dt>
<dd><p>Urclock has a faster, but slightly different strategy than -c arduino to
synchronise with the bootloader; some stk500v1 bootloaders cannot cope
with this, and they need the <code>-xstrict</code> option.
</p></dd>
<dt><code>&lsquo;<samp>help</samp>&rsquo;</code></dt>
<dd><p>Show this help menu and exit
</p></dd>
</dl>
<a name="index-_002dx-Buspirate"></a>
</dd>
<dt><code>BusPirate</code></dt>
@@ -150,7 +301,7 @@ programmer creates errors during initial sequence.
<dt><code>&lsquo;<samp>reset=cs,aux,aux2</samp>&rsquo;</code></dt>
<dd><p>The default setup assumes the BusPirate&rsquo;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.
connected to the same BP with SDI, SDO and SCK lines common for all of them.
In such a case one AVR should have its RESET connected to BusPirate&rsquo;s
<em>CS</em>
pin, second AVR&rsquo;s RESET connected to BusPirate&rsquo;s
@@ -293,7 +444,7 @@ No toggling of DTR/RTS is performed if <var>snooze</var> &gt; 0.
<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>SDI</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>
@@ -355,6 +506,18 @@ specific.
</p></dd>
</dl>
<a name="index-_002dx-linuxspi"></a>
</dd>
<dt><code>linuxspi</code></dt>
<dd><p>Extended parameter:
</p><dl compact="compact">
<dt><code>&lsquo;<samp>disable_no_cs</samp>&rsquo;</code></dt>
<dd><p>Ensures the programmer does not use the SPI_NO_CS bit for the SPI
driver. This parameter is useful for kernels that do not support
the CS line being managed outside the application.
</p></dd>
</dl>
</dd>
</dl>
@@ -377,7 +540,7 @@ specific.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

6
docs/current/avrdude_40.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -121,10 +121,12 @@ code {
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-AVR-Dragon"><code>-x</code> AVR Dragon</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-AVR910"><code>-x</code> AVR910</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-Buspirate"><code>-x</code> Buspirate</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-linuxspi"><code>-x</code> linuxspi</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-Micronucleus-bootloader"><code>-x</code> Micronucleus bootloader</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-PICkit2"><code>-x</code> PICkit2</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-serialupdi"><code>-x</code> serialupdi</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-Teensy-bootloader"><code>-x</code> Teensy bootloader</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-Urclock"><code>-x</code> Urclock</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-USBasp"><code>-x</code> USBasp</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-Wiring"><code>-x</code> Wiring</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
<tr><td></td><td valign="top"><a href="avrdude_4.html#index-_002dx-xbee"><code>-x</code> xbee</a></td><td>&nbsp;</td><td valign="top"><a href="avrdude_4.html#Programmers-accepting-extended-parameters">2.2 Programmers accepting extended parameters</a></td></tr>
@@ -202,7 +204,7 @@ code {
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_5.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -263,7 +263,7 @@ avrdude: usbdev_open(): did not find any (matching) USB device &quot;usb:xxx&quo
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_6.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -109,7 +109,7 @@ commands can be recalled and edited.
<hr>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

191
docs/current/avrdude_7.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -91,16 +91,24 @@ code {
<a name="Terminal-Mode-Commands-1"></a>
<h2 class="section">3.1 Terminal Mode Commands</h2>
<p>The following commands are implemented:
<p>The following commands are implemented for all programmers:
</p>
<dl compact="compact">
<dt><code>dump <var>memtype</var> [<var>start_addr</var> [<var>nbytes</var>]]</code></dt>
<dt><code>dump <var>memtype</var> <var>addr</var> <var>nbytes</var></code></dt>
<dd><p>Read <var>nbytes</var> from the specified memory area, and display them in
the usual hexadecimal and ASCII form.
</p>
</dd>
<dt><code>dump <var>memtype</var> [<var>start_addr</var>] &hellip;</code></dt>
<dd><p>Start reading from <var>start_addr</var>, all the way to the last memory address.
<dt><code>dump <var>memtype</var> <var>addr</var> &hellip;</code></dt>
<dd><p>Start reading from <var>addr</var>, all the way to the last memory address.
</p>
</dd>
<dt><code>dump <var>memtype</var> <var>addr</var></code></dt>
<dd><p>Read 256 bytes from the specified memory area, and display them.
</p>
</dd>
<dt><code>dump <var>memtype</var> &hellip;</code></dt>
<dd><p>Read all bytes from the specified memory, and display them.
</p>
</dd>
<dt><code>dump <var>memtype</var></code></dt>
@@ -108,93 +116,121 @@ the usual hexadecimal and ASCII form.
previous dump command left off.
</p>
</dd>
<dt><code>write <var>memtype</var> <var>start_addr</var> <var>data1</var> <var>data2</var> &hellip; <var>dataN</var></code></dt>
<dd><p>Manually program the respective memory cells, starting at address <var>start_addr</var>,
using the values <var>data1</var> through <var>dataN</var>. This feature is not
implemented for bank-addressed memories such as the flash memory of
ATMega devices.
<dt><code>read</code></dt>
<dd><p>Can be used as an alias for dump.
</p>
<p>Items <var>dataN</var> can have the following formats:
</dd>
<dt><code>write <var>memtype</var> <var>addr</var> <var>data[,]</var> {<var>data[,]</var>}</code></dt>
<dd><p>Manually program the respective memory cells, starting at address
<var>addr</var>, using the data items provided. The terminal implements
reading from and writing to flash and EEPROM type memories normally
through a cache and paged access functions. All other memories are
directly written to without use of a cache. Some older parts without paged
access will also have flash and EEPROM directly accessed without cache.
</p>
<p>Items <var>data</var> can have the following formats:
</p>
<table>
<tr><td width="30%"><strong>Type</strong></td><td width="40%"><strong>Example</strong></td><td width="30%"><strong>Size (bytes)</strong></td></tr>
<tr><td width="30%">String</td><td width="40%"><code>&quot;Hello, world\n&quot;</code></td><td width="30%">varying</td></tr>
<tr><td width="30%">Character</td><td width="40%"><code>'A'</code></td><td width="30%">1</td></tr>
<tr><td width="30%">Decimal integer</td><td width="40%">12345</td><td width="30%">1, 2, 4, or 8 (see below)</td></tr>
<tr><td width="30%">Octal integer</td><td width="40%">012345</td><td width="30%">1, 2, 4, or 8 (see below)</td></tr>
<tr><td width="30%">Hexadecimal integer</td><td width="40%">0x12345</td><td width="30%">1, 2, 4, or 8 (see below)</td></tr>
<tr><td width="30%">Decimal integer</td><td width="40%">12345</td><td width="30%">1, 2, 4, or 8</td></tr>
<tr><td width="30%">Octal integer</td><td width="40%">012345</td><td width="30%">1, 2, 4, or 8</td></tr>
<tr><td width="30%">Hexadecimal integer</td><td width="40%">0x12345</td><td width="30%">1, 2, 4, or 8</td></tr>
<tr><td width="30%">Float</td><td width="40%">3.1415926</td><td width="30%">4</td></tr>
<tr><td width="30%">Double</td><td width="40%">3.141592653589793D</td><td width="30%">8</td></tr>
</table>
<p>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:
</p>
<dl compact="compact">
<p><var>data</var>
can be hexadecimal, octal or decimal integers, floating point numbers
or C-style strings and characters. For integers, an optional case-insensitive
suffix specifies the data size as in the table below:
</p><dl compact="compact">
<dt><code>LL</code></dt>
<dt><code>ll</code></dt>
<dd><p>8 bytes / 64 bits
</p></dd>
<dt><code>L</code></dt>
<dt><code>l</code></dt>
<dd><p>4 bytes / 32 bits
</p></dd>
<dt><code>H</code></dt>
<dt><code>h</code></dt>
<dt><code>S</code></dt>
<dt><code>s</code></dt>
<dt><code>H or S</code></dt>
<dd><p>2 bytes / 16 bits
</p></dd>
<dt><code>HH</code></dt>
<dt><code>hh</code></dt>
<dd><p>1 byte / 8 bits
</p></dd>
</dl>
<p>Similarly, floating-point constants can have an <code>F</code> or <code>f</code>
appended, but only 32-bit floating-point values are supported.
<p>Suffix <code>D</code> indicates a 64-bit double, <code>F</code> a 32-bit float, whilst a
floating point number without suffix defaults to 32-bit float. Hexadecimal
floating point notation is supported. An ambiguous trailing suffix, e.g.,
<code>0x1.8D</code>, is read as no-suffix float where <code>D</code> is part of the
mantissa; use a zero exponent <code>0x1.8p0D</code> to clarify.
</p>
<p>An optional <code>U</code> suffix makes integers unsigned. Ordinary <code>0x</code> hex
integers are always treated as unsigned. <code>+0x</code> or <code>-0x</code> hex
numbers are treated as signed unless they have a <code>U</code> suffix. Unsigned
integers cannot be larger than 2^64-1. If <var>n</var> is an unsigned integer then <var>-n</var>
is also a valid unsigned integer as in C. Signed integers must fall into
the [-2^63, 2^63-1] range or a correspondingly smaller range when a suffix
specifies a smaller type.
</p>
<p>Ordinary <code>0x</code> hex integers with <var>n</var> hex digits (counting leading
zeros) use the smallest size of one, two, four and eight bytes that can
accommodate any n-digit hex integer. If an integer suffix specifies a size
explicitly the corresponding number of least significant bytes are
written, and a warning shown if the number does not fit into the desired
representation. Otherwise, unsigned integers occupy the smallest of one,
two, four or eight bytes needed. Signed numbers are allowed to fit into
the smallest signed or smallest unsigned representation: For example,
<code>255</code> is stored as one byte as <code>255U</code> would fit in one byte,
though as a signed number it would not fit into a one-byte interval [-128,
127]. The number <code>-1</code> is stored in one byte whilst <code>-1U</code> needs
eight bytes as it is the same as <code>0xFFFFffffFFFFffffU</code>.
</p>
<p>One trailing comma at the end of data items is ignored to facilitate copy
and paste of lists.
</p>
</dd>
<dt><code>write <var>memtype</var> <var>start_addr</var> <var>length</var> <var>data1</var> <var>data2</var> <var>dataN</var> &hellip;</code></dt>
<dd>
<p>Similar to the above, but <var>length</var> byte of the memory are written.
For that purpose, after writing the initial items, <var>dataN</var> is
replicated as many times as needed.
<dt><code>write <var>memtype</var> <var>addr</var> <var>length</var> <var>data[,]</var> {<var>data[,]</var>} &hellip;</code></dt>
<dd><p>The ellipses form &hellip; of write is similar to above, but <var>length</var>
byte of the memory are written. For that purpose, after writing the
initial items, the last <var>data</var> item is replicated as many times as
needed.
</p>
</dd>
<dt><code>flush</code></dt>
<dd><p>Synchronise with the device all pending cached writes to EEPROM or flash.
With some programmer and part combinations, flash (and sometimes EEPROM,
too) looks like a NOR memory, ie, one can only write 0 bits, not 1 bits.
When this is detected, either page erase is deployed (e.g., with parts that
have PDI/UPDI interfaces), or if that is not available, both EEPROM and
flash caches are fully read in, a chip erase command is issued and both
EEPROM and flash are written back to the device. Hence, it can take
minutes to ensure that a single previously cleared bit is set and,
therefore, this command should be used sparingly.
</p>
</dd>
<dt><code>abort</code></dt>
<dd><p>Normally, caches are only ever actually written to the device when using
<code>flush</code>, at the end of the terminal session after typing <code>quit</code>,
or after EOF on input is encountered. The <code>abort</code> command resets the
cache discarding all previous writes to the flash and EEPROM cache.
</p>
</dd>
<dt><code>erase</code></dt>
<dd><p>Perform a chip erase.
</p>
</dd>
<dt><code>send <var>b1</var> <var>b2</var> <var>b3</var> <var>b4</var></code></dt>
<dd><p>Send 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.
<dd><p>Perform a chip erase and discard all pending writes to EEPROM and flash.
</p>
</dd>
<dt><code>sig</code></dt>
<dd><p>Display the device signature bytes.
</p>
</dd>
<dt><code>spi</code></dt>
<dd><p>Enter direct SPI mode. The <em>pgmled</em> pin acts as slave select.
<em>Only supported on parallel bitbang programmers, and partially by USBtiny.</em>
Slave Select must be externally held low for direct SPI when
using USBtinyISP, and send must be a multiple of four bytes.
</p>
</dd>
<dt><code>part</code></dt>
<dd><p>Display the current part settings and parameters. Includes chip
specific information including all memory types supported by the
device, read/write timing, etc.
</p>
</dd>
<dt><code>pgm</code></dt>
<dd><p>Return to programming mode (from direct SPI mode).
</p>
</dd>
<dt><code>verbose [<var>level</var>]</code></dt>
<dd><p>Change (when <var>level</var> is provided), or display the verbosity
level.
@@ -202,6 +238,13 @@ The initial verbosity level is controlled by the number of <code>-v</code> optio
given on the command line.
</p>
</dd>
<dt><code>quell [<var>level</var>]</code></dt>
<dd><p>Change (when <var>level</var> is provided), or display the quell
level. 1 is used to suppress progress reports. 2 or higher yields
progressively quieter operations. The initial quell level is controlled
by the number of <code>-q</code> options given on the command line.
</p>
</dd>
<dt><code>?</code></dt>
<dt><code>help</code></dt>
<dd><p>Give a short on-line summary of the available commands.
@@ -213,10 +256,32 @@ given on the command line.
</dd>
</dl>
<p>In addition, the following commands are supported on the STK500
and STK600 programmer:
<p>In addition, the following commands are supported on some programmers:
</p>
<dl compact="compact">
<dt><code>pgerase <var>memory</var> <var>addr</var></code></dt>
<dd><p>Erase one page of the memory specified.
</p>
</dd>
<dt><code>send <var>b1</var> <var>b2</var> <var>b3</var> <var>b4</var></code></dt>
<dd><p>Send 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.
</p>
</dd>
<dt><code>spi</code></dt>
<dd><p>Enter direct SPI mode. The <em>pgmled</em> pin acts as chip select.
<em>Only supported on parallel bitbang programmers, and partially by USBtiny.</em>
Chip Select must be externally held low for direct SPI when
using USBtinyISP, and send must be a multiple of four bytes.
</p>
</dd>
<dt><code>pgm</code></dt>
<dd><p>Return to programming mode (from direct SPI mode).
</p>
</dd>
<dt><code>vtarg <var>voltage</var></code></dt>
<dd><p>Set the target&rsquo;s supply voltage to <var>voltage</var> Volts.
</p>
@@ -231,20 +296,19 @@ selected by the optional parameter <var>channel</var> (either
</p>
</dd>
<dt><code>fosc <var>freq</var>[<code>M</code>|<code>k</code>]</code></dt>
<dd><p>Set the master oscillator to <var>freq</var> Hz.
<dd><p>Set the programming oscillator to <var>freq</var> Hz.
An optional trailing letter <code>M</code>
multiplies by 1E6, a trailing letter <code>k</code> by 1E3.
</p>
</dd>
<dt><code>fosc off</code></dt>
<dd><p>Turn the master oscillator off.
<dd><p>Turn the programming oscillator off.
</p>
</dd>
<dt><code>sck <var>period</var></code></dt>
<dd><p><em>STK500 and STK600 only:</em>
Set the SCK clock period to <var>period</var> microseconds.
</p>
<p><em>JTAG ICE only:</em>
<em>JTAG ICE only:</em>
Set the JTAG ICE bit clock period to <var>period</var> microseconds.
Note that unlike STK500 settings, this setting will be reverted to
its default value (approximately 1 microsecond) when the programming
@@ -255,9 +319,8 @@ ISP clock period when operating the ICE in ISP mode.
</dd>
<dt><code>parms</code></dt>
<dd><p><em>STK500 and STK600 only:</em>
Display the current voltage and master oscillator parameters.
</p>
<p><em>JTAG ICE only:</em>
Display the current voltage and programming oscillator parameters.
<em>JTAG ICE only:</em>
Display the current target supply voltage and JTAG bit clock rate/period.
</p>
</dd>
@@ -281,7 +344,7 @@ Display the current target supply voltage and JTAG bit clock rate/period.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_8.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -246,7 +246,7 @@ avrdude&gt; dump eeprom 0 0x30
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

29
docs/current/avrdude_9.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -96,21 +96,24 @@ code {
the parts and programmers that it knows about. The advantage of this is
that if you have a chip that is not currently supported by AVRDUDE, you
can add it to the configuration file without waiting for a new release
of AVRDUDE. Likewise, if you have a parallel port programmer that is
not supported by AVRDUDE, chances are good that you can copy and
existing programmer definition, and with only a few changes, make your
programmer work with AVRDUDE.
of AVRDUDE. Likewise, if you have a parallel port programmer that is
not supported, chances are that you can copy an
existing programmer definition and, with only a few changes, make your
programmer work.
</p>
<p>AVRDUDE first looks for a system wide configuration file in a platform
dependent location. On Unix, this is usually
<code>/usr/local/etc/avrdude.conf</code>, while on Windows it is usually in the
same location as the executable file. The name of this file can be
changed using the &lsquo;<samp>-C</samp>&rsquo; command line option. After the system wide
configuration file is parsed, AVRDUDE looks for a per-user configuration
<code>/usr/local/etc/avrdude.conf</code>, whilst on Windows it is usually in the
same location as the executable file. The full name of this file can be
specified using the &lsquo;<samp>-C</samp>&rsquo; command line option. After parsing the system wide
configuration file, AVRDUDE looks for a per-user configuration
file to augment or override the system wide defaults. On Unix, the
per-user file is <code>.avrduderc</code> within the user&rsquo;s home directory. On
Windows, this file is the <code>avrdude.rc</code> file located in the same
directory as the executable.
per-user file is <code>${XDG_CONFIG_HOME}/avrdude/avrdude.rc</code>, whereas
if <code>${XDG_CONFIG_HOME}</code> is either not set or empty,
<code>${HOME}/.config/</code> is used instead. If that does not exists
<code>.avrduderc</code> within the user&rsquo;s home directory is used. On Windows,
this file is the <code>avrdude.rc</code> file located in the same directory as
the executable.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="avrdude_10.html#AVRDUDE-Defaults">4.1 AVRDUDE Defaults</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
@@ -141,7 +144,7 @@ directory as the executable.
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

6
docs/current/avrdude_abt.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -81,7 +81,7 @@ code {
<h1>About This Document</h1>
<p>
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</p>
<p>
The buttons in the navigation panels have the following meaning:
@@ -189,7 +189,7 @@ code {
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>

4
docs/current/avrdude_toc.html
View File

@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created on April 26, 2022 by texi2html 5.0
<!-- Created on January 8, 2023 by texi2html 5.0
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
@@ -162,7 +162,7 @@ code {
</tr></table>
<p>
<font size="-1">
This document was generated on <i>April 26, 2022</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
This document was generated on <i>January 8, 2023</i> using <a href="http://www.nongnu.org/texi2html/"><i>texi2html 5.0</i></a>.
</font>
<br>