From 92a5ae20a69d535fe0c1b410c71f71e9d41d1307 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 00:09:47 +0100 Subject: [PATCH 01/25] Test for Github pages --- docs/avrdude.html | 351 ++++++++++++++ docs/avrdude_1.html | 109 +++++ docs/avrdude_10.html | 111 +++++ docs/avrdude_11.html | 174 +++++++ docs/avrdude_12.html | 296 ++++++++++++ docs/avrdude_13.html | 137 ++++++ docs/avrdude_14.html | 96 ++++ docs/avrdude_15.html | 172 +++++++ docs/avrdude_16.html | 109 +++++ docs/avrdude_17.html | 181 ++++++++ docs/avrdude_18.html | 94 ++++ docs/avrdude_19.html | 373 +++++++++++++++ docs/avrdude_2.html | 97 ++++ docs/avrdude_20.html | 378 ++++++++++++++++ docs/avrdude_21.html | 395 ++++++++++++++++ docs/avrdude_3.html | 1003 +++++++++++++++++++++++++++++++++++++++++ docs/avrdude_4.html | 346 ++++++++++++++ docs/avrdude_5.html | 242 ++++++++++ docs/avrdude_6.html | 103 +++++ docs/avrdude_7.html | 208 +++++++++ docs/avrdude_8.html | 183 ++++++++ docs/avrdude_9.html | 118 +++++ docs/avrdude_abt.html | 176 ++++++++ docs/avrdude_toc.html | 148 ++++++ 24 files changed, 5600 insertions(+) create mode 100644 docs/avrdude.html create mode 100644 docs/avrdude_1.html create mode 100644 docs/avrdude_10.html create mode 100644 docs/avrdude_11.html create mode 100644 docs/avrdude_12.html create mode 100644 docs/avrdude_13.html create mode 100644 docs/avrdude_14.html create mode 100644 docs/avrdude_15.html create mode 100644 docs/avrdude_16.html create mode 100644 docs/avrdude_17.html create mode 100644 docs/avrdude_18.html create mode 100644 docs/avrdude_19.html create mode 100644 docs/avrdude_2.html create mode 100644 docs/avrdude_20.html create mode 100644 docs/avrdude_21.html create mode 100644 docs/avrdude_3.html create mode 100644 docs/avrdude_4.html create mode 100644 docs/avrdude_5.html create mode 100644 docs/avrdude_6.html create mode 100644 docs/avrdude_7.html create mode 100644 docs/avrdude_8.html create mode 100644 docs/avrdude_9.html create mode 100644 docs/avrdude_abt.html create mode 100644 docs/avrdude_toc.html diff --git a/docs/avrdude.html b/docs/avrdude.html new file mode 100644 index 00000000..53e42783 --- /dev/null +++ b/docs/avrdude.html @@ -0,0 +1,351 @@ + + + + +AVRDUDE: 1 Introduction + + + + + + + + + + + + + + +

AVRDUDE

+

A program for download/uploading AVR microcontroller flash and eeprom.

+

For AVRDUDE, Version 6.99-20211218, 3 March 2022.

+by Brian S. Dean
+ + +

Send comments on AVRDUDE to avrdude-dev@nongnu.org">avrdude-dev@nongnu.org. +

+

Use http://savannah.nongnu.org/bugs/?group=avrdude to report bugs. +

+

Copyright © 2003,2005 Brian S. Dean +

+

Copyright © 2006 - 2013 Jörg Wunsch +


+
+ +

Permission is granted to make and distribute verbatim copies of +this manual provided the copyright notice and this permission notice +are preserved on all copies. +

+

Permission is granted to copy and distribute modified versions of this +manual under the conditions for verbatim copying, provided that the entire +resulting derived work is distributed under the terms of a permission +notice identical to this one. +

+

Permission is granted to copy and distribute translations of this manual +into another language, under the above conditions for modified versions, +except that this permission notice may be stated in a translation approved +by the Free Software Foundation. +

+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ + + + + + + + + + +
1 Introduction   +
2 Command Line Options   +
3 Terminal Mode Operation   +
4 Configuration File   +
5 Programmer Specific Information   +
Appendix A Platform Dependent Information   +
Appendix B Troubleshooting   +
+ + + +

1 Introduction

+ + +

AVRDUDE - AVR Downloader Uploader - is a program for downloading and +uploading the on-chip memories of Atmel’s AVR microcontrollers. It can +program the Flash and EEPROM, and where supported by the serial +programming protocol, it can program fuse and lock bits. AVRDUDE also +supplies a direct instruction mode allowing one to issue any programming +instruction to the AVR chip regardless of whether AVRDUDE implements +that specific feature of a particular chip. +

+

AVRDUDE can be used effectively via the command line to read or write +all chip memory types (eeprom, flash, fuse bits, lock bits, signature +bytes) or via an interactive (terminal) mode. Using AVRDUDE from the +command line works well for programming the entire memory of the chip +from the contents of a file, while interactive mode is useful for +exploring memory contents, modifying individual bytes of eeprom, +programming fuse/lock bits, etc. +

+

AVRDUDE supports the following basic programmer types: Atmel’s STK500, +Atmel’s AVRISP and AVRISP mkII devices, +Atmel’s STK600, +Atmel’s JTAG ICE (the original one, mkII, and 3, the latter two also in ISP mode), appnote +avr910, appnote avr109 (including the AVR Butterfly), +serial bit-bang adapters, +and the PPI (parallel port interface). PPI represents a class +of simple programmers where the programming lines are directly +connected to the PC parallel port. Several pin configurations exist +for several variations of the PPI programmers, and AVRDUDE can be +configured to work with them by either specifying the appropriate +programmer on the command line or by creating a new entry in its +configuration file. All that’s usually required for a new entry is to +tell AVRDUDE which pins to use for each programming function. +

+

A number of equally simple bit-bang programming adapters that connect +to a serial port are supported as well, among them the popular +Ponyprog serial adapter, and the DASA and DASA3 adapters that used to +be supported by uisp(1). Note that these adapters are meant to be +attached to a physical serial port. Connecting to a serial port +emulated on top of USB is likely to not work at all, or to work +abysmally slow. +

+

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 +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 +overcurrent situations in some way. The simplest would be to just put +some resistors in series or better yet use a 3-state buffer driver like +the 74HC244. Have a look at http://kolev.info/blog/2013/01/06/avrdude-linuxgpio/ for a more +detailed tutorial about using this programmer type. +

+

Under a Linux installation with direct access to the SPI bus and GPIO +pins, such as would be found on a Raspberry Pi, the “linuxspi” +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 +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’s SPI controller in the +event that the chip is running at 5V and the SPI runs at 3.3V. The +GPIO chosen for reset can be configured in the avrdude configuration +file using the reset entry under the linuxspi programmer, or +directly in the port specification. An external pull-up resistor +should be connected between the AVR’s reset pin and Vcc. If Vcc is not +the same as the SPI voltage, this should be done on the AVR side of +the level translator to protect the hardware from damage. +

+

On a Raspberry Pi, header J8 provides access to the SPI and GPIO +lines. +

+

Typically, pins 19, 21, and 23 are SPI MOSI, MISO, 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. +

+

A typical programming cable would then look like: +

+ + + + + + + + +
J8 pinISP pinName
211MISO
-2Vcc - leave open
233SCK
194MOSI
225/RESET
256GND
+ +

(Mind the 3.3 V voltage level of the Raspberry Pi!) +

+

The -P portname option defaults to +/dev/spidev0.0:/dev/gpiochip0 for this programmer. +

+

The STK500, JTAG ICE, avr910, and avr109/butterfly use the serial port to communicate with the PC. +The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivatives), and USBtinyISP +programmers communicate through the USB, using libusb 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 +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 +device. +The avr109 bootloader implements a protocol similar to avr910, but is +actually implemented in the boot area of the target’s flash ROM, as +opposed to being an external device. +The fundamental difference between the two types lies in the +protocol used to control the programmer. The avr910 protocol is very +simplistic and can easily be used as the basis for a simple, home made +programmer since the firmware is available online. On the other hand, +the STK500 protocol is more robust and complicated and the firmware is +not openly available. +The JTAG ICE also uses a serial communication protocol which is similar +to the STK500 firmware version 2 one. However, as the JTAG ICE is +intended to allow on-chip debugging as well as memory programming, the +protocol is more sophisticated. +(The JTAG ICE mkII protocol can also be run on top of USB.) +Only the memory programming functionality of the JTAG ICE is supported +by AVRDUDE. +For the JTAG ICE mkII/3, JTAG, debugWire and ISP mode are supported, provided +it has a firmware revision of at least 4.14 (decimal). +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). +

+

The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP modes). +

+

Atmel’s XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are +supported by the “jtag3” programmer type. +

+

Atmel’s XplainedMini boards, using mEDBG protocol, are also +supported by the “jtag3” programmer type. +

+

The AVR Dragon is supported in all modes (ISP, JTAG, PDI, HVSP, PP, debugWire). +When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a +JTAG ICE mkII, so all device-specific comments for that device +will apply as well. +When used in ISP and PDI mode, the AVR Dragon behaves similar to an +AVRISP mkII (or JTAG ICE mkII in ISP mode), so all device-specific +comments will apply there. +In particular, the Dragon starts out with a rather fast ISP clock +frequency, so the -B bitclock +option might be required to achieve a stable ISP communication. +For ATxmega devices, the AVR Dragon is supported in PDI mode, provided it +has a firmware version of at least 6.11 (decimal). +

+

Wiring boards (e.g. Arduino Mega 2560 Rev3) are supported, utilizing +STK500 V2.x protocol, but a simple DTR/RTS toggle to set the boards +into programming mode. The programmer type is “wiring”. Note that +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. +

+

The Arduino (which is very similar to the STK500 1.x) is supported via +its own programmer type specification “arduino”. 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 +extended parameters +below for details. +

+

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 +extended parameters +below for details. +

+

The USBasp ISP and USBtinyISP adapters are also supported, provided AVRDUDE +has been compiled with libusb support. +They both feature simple firmware-only USB implementations, running on +an ATmega8 (or ATmega88), or ATtiny2313, respectively. +

+

The Atmel DFU bootloader is supported in both, FLIP protocol version 1 +(AT90USB* and ATmega*U* devices), as well as version 2 (Xmega devices). +See below for some hints about FLIP version 1 protocol behaviour. +

+

The MPLAB(R) PICkit 4 and MPLAB(R) SNAP are supported in ISP, PDI and UPDI mode. +The Curiosity Nano board is supported in UPDI mode. It is dubbed “PICkit on +Board”, thus the name pkobn_updi. +

+

SerialUPDI programmer implementation is based on Microchip’s +pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) +utility, but it also contains some performance improvements included in +Spence Konde’s DxCore Arduino core (https://github.com/SpenceKonde/DxCore). +In a nutshell, this programmer consists of simple USB->UART adapter, diode +and couple of resistors. It uses serial connection to provide UPDI interface. +See section SerialUPDI programmer for more details and known issues. +

+

The jtag2updi programmer is supported, +and can program AVRs with a UPDI interface. +Jtag2updi is just a firmware that can be uploaded to an AVR, +which enables it to interface with avrdude using the jtagice mkii protocol +via a serial link (https://github.com/ElTangas/jtag2updi). +

+

The Micronucleus bootloader is supported for both protocol version V1 +and V2. As the bootloader does not support reading from flash memory, +use the -V option to prevent AVRDUDE from verifing the flash memory. +See the section on extended parameters +below for Micronucleus specific options. +

+

The Teensy bootloader is supported for all AVR boards. +As the bootloader does not support reading from flash memory, +use the -V option to prevent AVRDUDE from verifing the flash memory. +See the section on extended parameters +below for Teensy specific options. +

+ + +
1.1 History and Credits   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_1.html b/docs/avrdude_1.html new file mode 100644 index 00000000..77840526 --- /dev/null +++ b/docs/avrdude_1.html @@ -0,0 +1,109 @@ + + + + +AVRDUDE: 1.1 History and Credits + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

1.1 History and Credits

+ +

AVRDUDE was written by Brian S. Dean under the name of AVRPROG to run on +the FreeBSD Operating System. Brian renamed the software to be called +AVRDUDE when interest grew in a Windows port of the software so that the +name did not conflict with AVRPROG.EXE which is the name of Atmel’s +Windows programming software. +

+

The AVRDUDE source now resides in the public CVS repository on +savannah.gnu.org (http://savannah.gnu.org/projects/avrdude/), +where it continues to be enhanced and ported to other systems. In +addition to FreeBSD, AVRDUDE now runs on Linux and Windows. The +developers behind the porting effort primarily were Ted Roth, Eric +Weddington, and Joerg Wunsch. +

+

And in the spirit of many open source projects, this manual also draws +on the work of others. The initial revision was composed of parts of +the original Unix manual page written by Joerg Wunsch, the original web +site documentation by Brian Dean, and from the comments describing the +fields in the AVRDUDE configuration file by Brian Dean. The texi +formatting was modeled after that of the Simulavr documentation by Ted +Roth. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_10.html b/docs/avrdude_10.html new file mode 100644 index 00000000..e52e8e33 --- /dev/null +++ b/docs/avrdude_10.html @@ -0,0 +1,111 @@ + + + + +AVRDUDE: 4.1 AVRDUDE Defaults + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.1 AVRDUDE Defaults

+ +
+
default_parallel = "default-parallel-device";
+

Assign the default parallel port device. Can be overridden using the +‘-P’ option. +

+
+
default_serial = "default-serial-device";
+

Assign the default serial port device. Can be overridden using the +‘-P’ option. +

+
+
default_programmer = "default-programmer-id";
+

Assign the default programmer id. Can be overridden using the ‘-c’ +option. +

+
+
default_bitclock = "default-bitclock";
+

Assign the default bitclock value. Can be overridden using the ‘-B’ +option. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_11.html b/docs/avrdude_11.html new file mode 100644 index 00000000..5196f853 --- /dev/null +++ b/docs/avrdude_11.html @@ -0,0 +1,174 @@ + + + + +AVRDUDE: 4.2 Programmer Definitions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.2 Programmer Definitions

+ +

The format of the programmer definition is as follows: +

+
+
programmer
+    parent <id>                                 # <id> is a quoted string
+    id       = <id1> [, <id2> [, <id3>] ...] ;  # <idN> are quoted strings
+    desc     = <description> ;                  # quoted string
+    type     = "par" | "stk500" | ... ;         # programmer type (see below for a list)
+    baudrate = <num> ;                          # baudrate for serial ports
+    vcc      = <num1> [, <num2> ... ] ;         # pin number(s)
+    buff     = <num1> [, <num2> ... ] ;         # pin number(s)
+    reset    = <num> ;                          # pin number
+    sck      = <num> ;                          # pin number
+    mosi     = <num> ;                          # pin number
+    miso     = <num> ;                          # pin number
+    errled   = <num> ;                          # pin number
+    rdyled   = <num> ;                          # pin number
+    pgmled   = <num> ;                          # pin number
+    vfyled   = <num> ;                          # pin number
+    usbvid   = <hexnum>;                        # USB VID (Vendor ID)
+    usbpid   = <hexnum> [, <hexnum> ...];       # USB PID (Product ID)
+    usbdev   = <interface>;                     # USB interface or other device info 
+    usbvendor = <vendorname>;                   # USB Vendor Name
+    usbproduct = <productname>;                 # USB Product Name
+    usbsn    = <serialno>;                      # USB Serial Number
+  ;
+
+ +

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. +

+

To invert a bit in the pin definitions, use = ~ <num>. +

+

Not all programmer types can handle a list of USB PIDs. +

+

Following programmer types are currently implemented: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
arduinoArduino programmer
avr910Serial programmers using protocol described in application note AVR910
avrftdiInterface to the MPSSE Engine of FTDI Chips using libftdi.
buspirateUsing the Bus Pirate’s SPI interface for programming
buspirate_bbUsing the Bus Pirate’s bitbang interface for programming
butterflyAtmel Butterfly evaluation board; Atmel AppNotes AVR109, AVR911
butterfly_mkMikrokopter.de Butterfly
dragon_dwAtmel AVR Dragon in debugWire mode
dragon_hvspAtmel AVR Dragon in HVSP mode
dragon_ispAtmel AVR Dragon in ISP mode
dragon_jtagAtmel AVR Dragon in JTAG mode
dragon_pdiAtmel AVR Dragon in PDI mode
dragon_ppAtmel AVR Dragon in PP mode
flip1FLIP USB DFU protocol version 1 (doc7618)
flip2FLIP USB DFU protocol version 2 (AVR4023)
ftdi_syncbbFT245R/FT232R Synchronous BitBangMode Programmer
jtagmkiAtmel JTAG ICE mkI
jtagmkiiAtmel JTAG ICE mkII
jtagmkii_avr32Atmel JTAG ICE mkII in AVR32 mode
jtagmkii_dwAtmel JTAG ICE mkII in debugWire mode
jtagmkii_ispAtmel JTAG ICE mkII in ISP mode
jtagmkii_pdiAtmel JTAG ICE mkII in PDI mode
jtagice3Atmel JTAGICE3
jtagice3_pdiAtmel JTAGICE3 in PDI mode
jtagice3_updiAtmel JTAGICE3 in UPDI mode
jtagice3_dwAtmel JTAGICE3 in debugWire mode
jtagice3_ispAtmel JTAGICE3 in ISP mode
linuxgpioGPIO bitbanging using the Linux sysfs interface (not available)
linuxspiSPI using Linux spidev driver (not available)
micronucleusMicronucleus Bootloader
parParallel port bitbanging
pickit2Microchip’s PICkit2 Programmer
serbbSerial port bitbanging
serialupdiDriver for SerialUPDI programmers
stk500Atmel STK500 Version 1.x firmware
stk500genericAtmel STK500, autodetect firmware version
stk500v2Atmel STK500 Version 2.x firmware
stk500hvspAtmel STK500 V2 in high-voltage serial programming mode
stk500ppAtmel STK500 V2 in parallel programming mode
stk600Atmel STK600
stk600hvspAtmel STK600 in high-voltage serial programming mode
stk600ppAtmel STK600 in parallel programming mode
teensyTeensy Bootloader
usbaspUSBasp programmer, see http://www.fischl.de/usbasp/
usbtinyDriver for "usbtiny"-type programmers
wiringhttp://wiring.org.co/, Basically STK500v2 protocol, with some glue to trigger the bootloader.
xbeeXBee Series 2 Over-The-Air (XBeeBoot)
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_12.html b/docs/avrdude_12.html new file mode 100644 index 00000000..e80e6d34 --- /dev/null +++ b/docs/avrdude_12.html @@ -0,0 +1,296 @@ + + + + +AVRDUDE: 4.3 Part Definitions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.3 Part Definitions

+ +
+
part
+    id               = <id> ;                 # quoted string
+    desc             = <description> ;        # quoted string
+    family_id        = <description> ;        # quoted string
+    has_jtag         = <yes/no> ;             # part has JTAG i/f
+    has_debugwire    = <yes/no> ;             # part has debugWire i/f
+    has_pdi          = <yes/no> ;             # part has PDI i/f
+    has_updi         = <yes/no> ;             # part has UPDI i/f
+    has_tpi          = <yes/no> ;             # part has TPI i/f
+    devicecode       = <num> ;                # numeric
+    stk500_devcode   = <num> ;                # numeric
+    avr910_devcode   = <num> ;                # numeric
+    signature        = <num> <num> <num> ;    # signature bytes
+    usbpid           = <num> ;                # DFU USB PID
+    reset            = dedicated | io;
+    retry_pulse      = reset | sck;
+    pgm_enable       = <instruction format> ;
+    chip_erase       = <instruction format> ;
+    chip_erase_delay = <num> ;                # micro-seconds
+    # STK500 parameters (parallel programming IO lines)
+    pagel            = <num> ;                # pin name in hex, i.e., 0xD7
+    bs2              = <num> ;                # pin name in hex, i.e., 0xA0
+    serial           = <yes/no> ;             # can use serial downloading
+    parallel         = <yes/no/pseudo>;       # can use par. programming
+    # STK500v2 parameters, to be taken from Atmel's XML files
+    timeout          = <num> ;
+    stabdelay        = <num> ;
+    cmdexedelay      = <num> ;
+    synchloops       = <num> ;
+    bytedelay        = <num> ;
+    pollvalue        = <num> ;
+    pollindex        = <num> ;
+    predelay         = <num> ;
+    postdelay        = <num> ;
+    pollmethod       = <num> ;
+    mode             = <num> ;
+    delay            = <num> ;
+    blocksize        = <num> ;
+    readsize         = <num> ;
+    hvspcmdexedelay  = <num> ;
+    # STK500v2 HV programming parameters, from XML
+    pp_controlstack  = <num>, <num>, ...;     # PP only
+    hvsp_controlstack = <num>, <num>, ...;    # HVSP only
+    hventerstabdelay = <num>;
+    progmodedelay    = <num>;                 # PP only
+    latchcycles      = <num>;
+    togglevtg        = <num>;
+    poweroffdelay    = <num>;
+    resetdelayms     = <num>;
+    resetdelayus     = <num>;
+    hvleavestabdelay = <num>;
+    resetdelay       = <num>;
+    synchcycles      = <num>;                 # HVSP only
+    chiperasepulsewidth = <num>;              # PP only
+    chiperasepolltimeout = <num>;
+    chiperasetime    = <num>;                 # HVSP only
+    programfusepulsewidth = <num>;            # PP only
+    programfusepolltimeout = <num>;
+    programlockpulsewidth = <num>;            # PP only
+    programlockpolltimeout = <num>;
+    # JTAG ICE mkII parameters, also from XML files
+    allowfullpagebitstream = <yes/no> ;
+    enablepageprogramming = <yes/no> ;
+    idr              = <num> ;                # IO addr of IDR (OCD) reg.
+    rampz            = <num> ;                # IO addr of RAMPZ reg.
+    spmcr            = <num> ;                # mem addr of SPMC[S]R reg.
+    eecr             = <num> ;                # mem addr of EECR reg.
+                                              # (only when != 0x3c)
+    is_at90s1200     = <yes/no> ;             # AT90S1200 part
+    is_avr32         = <yes/no> ;             # AVR32 part
+
+    memory <memtype>
+        paged           = <yes/no> ;          # yes / no
+        size            = <num> ;             # bytes
+        page_size       = <num> ;             # bytes
+        num_pages       = <num> ;             # numeric
+        min_write_delay = <num> ;             # micro-seconds
+        max_write_delay = <num> ;             # micro-seconds
+        readback_p1     = <num> ;             # byte value
+        readback_p2     = <num> ;             # byte value
+        pwroff_after_write = <yes/no> ;       # yes / no
+        read            = <instruction format> ;
+        write           = <instruction format> ;
+        read_lo         = <instruction format> ;
+        read_hi         = <instruction format> ;
+        write_lo        = <instruction format> ;
+        write_hi        = <instruction format> ;
+        loadpage_lo     = <instruction format> ;
+        loadpage_hi     = <instruction format> ;
+        writepage       = <instruction format> ;
+      ;
+  ;
+
+ + + + +
4.3.1 Parent Part   +
4.3.2 Instruction Format   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.3.1 Parent Part

+ +

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. +

+
+
   part parent <id>                              # quoted string
+       id               = <id> ;                 # quoted string
+       <any set of other parameters from the list above>
+     ;
+
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.3.2 Instruction Format

+ +

Instruction formats are specified as a comma separated list of string +values containing information (bit specifiers) about each of the 32 bits +of the instruction. Bit specifiers may be one of the following formats: +

+
+
1
+

The bit is always set on input as well as output +

+
+
0
+

the bit is always clear on input as well as output +

+
+
x
+

the bit is ignored on input and output +

+
+
a
+

the bit is an address bit, the bit-number matches this bit specifier’s +position within the current instruction byte +

+
+
aN
+

the bit is the Nth address bit, bit-number = N, i.e., a12 +is address bit 12 on input, a0 is address bit 0. +

+
+
i
+

the bit is an input data bit +

+
+
o
+

the bit is an output data bit +

+
+
+ +

Each instruction must be composed of 32 bit specifiers. The instruction +specification closely follows the instruction data provided in Atmel’s +data sheets for their parts. For example, the EEPROM read and write +instruction for an AT90S2313 AVR part could be encoded as: +

+
+
+read  = "1  0  1  0   0  0  0  0   x x x x  x x x x",
+        "x a6 a5 a4  a3 a2 a1 a0   o o o o  o o o o";
+
+write = "1  1  0  0   0  0  0  0   x x x x  x x x x",
+        "x a6 a5 a4  a3 a2 a1 a0   i i i i  i i i i";
+
+
+ + + +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_13.html b/docs/avrdude_13.html new file mode 100644 index 00000000..3e20194c --- /dev/null +++ b/docs/avrdude_13.html @@ -0,0 +1,137 @@ + + + + +AVRDUDE: 4.4 Other Notes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4.4 Other Notes

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_14.html b/docs/avrdude_14.html new file mode 100644 index 00000000..fd28bc68 --- /dev/null +++ b/docs/avrdude_14.html @@ -0,0 +1,96 @@ + + + + +AVRDUDE: 5 Programmer Specific Information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

5 Programmer Specific Information

+ + + + + +
5.1 Atmel STK600   +
5.2 Atmel DFU bootloader using FLIP version 1   +
5.3 SerialUPDI programmer   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_15.html b/docs/avrdude_15.html new file mode 100644 index 00000000..b96b1c36 --- /dev/null +++ b/docs/avrdude_15.html @@ -0,0 +1,172 @@ + + + + +AVRDUDE: 5.1 Atmel STK600 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

5.1 Atmel STK600

+ +

The following devices are supported by the respective STK600 routing +and socket card: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Routing cardSocket cardDevices
STK600-ATTINY10ATtiny4 ATtiny5 ATtiny9 ATtiny10
STK600-RC008T-2STK600-DIPATtiny11 ATtiny12 ATtiny13 ATtiny13A ATtiny25 ATtiny45 ATtiny85
STK600-RC008T-7STK600-DIPATtiny15
STK600-RC014T-42STK600-SOICATtiny20
STK600-RC020T-1STK600-DIPATtiny2313 ATtiny2313A ATtiny4313
STK600-TinyX3UATtiny43U
STK600-RC014T-12STK600-DIPATtiny24 ATtiny44 ATtiny84 ATtiny24A ATtiny44A
STK600-RC020T-8STK600-DIPATtiny26 ATtiny261 ATtiny261A ATtiny461 ATtiny861 ATtiny861A
STK600-RC020T-43STK600-SOICATtiny261 ATtiny261A ATtiny461 ATtiny461A ATtiny861 ATtiny861A
STK600-RC020T-23STK600-SOICATtiny87 ATtiny167
STK600-RC028T-3STK600-DIPATtiny28
STK600-RC028M-6STK600-DIPATtiny48 ATtiny88 ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
QT600-ATTINY88-QT8ATtiny88
STK600-RC040M-4STK600-DIPATmega8515 ATmega162
STK600-RC044M-30STK600-TQFP44ATmega8515 ATmega162
STK600-RC040M-5STK600-DIPATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
STK600-RC044M-31STK600-TQFP44ATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
QT600-ATMEGA324-QM64ATmega324PA
STK600-RC032M-29STK600-TQFP32ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
STK600-RC064M-9STK600-TQFP64ATmega64 ATmega64A ATmega128 ATmega128A ATmega1281 ATmega2561 AT90CAN32 AT90CAN64 AT90CAN128
STK600-RC064M-10STK600-TQFP64ATmega165 ATmega165P ATmega169 ATmega169P ATmega169PA ATmega325 ATmega325P ATmega329 ATmega329P ATmega645 ATmega649 ATmega649P
STK600-RC100M-11STK600-TQFP100ATmega640 ATmega1280 ATmega2560
STK600-ATMEGA2560ATmega2560
STK600-RC100M-18STK600-TQFP100ATmega3250 ATmega3250P ATmega3290 ATmega3290P ATmega6450 ATmega6490
STK600-RC032U-20STK600-TQFP32AT90USB82 AT90USB162 ATmega8U2 ATmega16U2 ATmega32U2
STK600-RC044U-25STK600-TQFP44ATmega16U4 ATmega32U4
STK600-RC064U-17STK600-TQFP64ATmega32U6 AT90USB646 AT90USB1286 AT90USB647 AT90USB1287
STK600-RCPWM-22STK600-TQFP32ATmega32C1 ATmega64C1 ATmega16M1 ATmega32M1 ATmega64M1
STK600-RCPWM-19STK600-SOICAT90PWM2 AT90PWM3 AT90PWM2B AT90PWM3B AT90PWM216 AT90PWM316
STK600-RCPWM-26STK600-SOICAT90PWM81
STK600-RC044M-24STK600-TSSOP44ATmega16HVB ATmega32HVB
STK600-HVE2ATmega64HVE
STK600-ATMEGA128RFA1ATmega128RFA1
STK600-RC100X-13STK600-TQFP100ATxmega64A1 ATxmega128A1 ATxmega128A1_revD ATxmega128A1U
STK600-ATXMEGA1281A1ATxmega128A1
QT600-ATXMEGA128A1-QT16ATxmega128A1
STK600-RC064X-14STK600-TQFP64ATxmega64A3 ATxmega128A3 ATxmega256A3 ATxmega64D3 ATxmega128D3 ATxmega192D3 ATxmega256D3
STK600-RC064X-14STK600-MLF64ATxmega256A3B
STK600-RC044X-15STK600-TQFP44ATxmega32A4 ATxmega16A4 ATxmega16D4 ATxmega32D4
STK600-ATXMEGAT0ATxmega32T0
STK600-uC3-144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCUC3A144-33STK600-TQFP144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCuC3A100-28STK600-TQFP100AT32UC3A1512 AT32UC3A1256 AT32UC3A1128
STK600-RCuC3B0-21STK600-TQFP64-2AT32UC3B0256 AT32UC3B0512RevC AT32UC3B0512 AT32UC3B0128 AT32UC3B064 AT32UC3D1128
STK600-RCuC3B48-27STK600-TQFP48AT32UC3B1256 AT32UC3B164
STK600-RCUC3A144-32STK600-TQFP144AT32UC3A3512 AT32UC3A3256 AT32UC3A3128 AT32UC3A364 AT32UC3A3256S AT32UC3A3128S AT32UC3A364S
STK600-RCUC3C0-36STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-38STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-40STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3C0-37STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-39STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-41STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3L0-34STK600-TQFP48AT32UC3L064 AT32UC3L032 AT32UC3L016
QT600-AT32UC3L-QM64AT32UC3L064
+ +

Ensure the correct socket and routing card are mounted before +powering on the STK600. While the STK600 firmware ensures the socket +and routing card mounted match each other (using a table stored +internally in nonvolatile memory), it cannot handle the case where a +wrong routing card is used, e. g. the routing card +STK600-RC040M-5 (which is meant for 40-pin DIP AVRs that have +an ADC, with the power supply pins in the center of the package) was +used but an ATmega8515 inserted (which uses the “industry standard” +pinout with Vcc and GND at opposite corners). +

+

Note that for devices that use the routing card STK600-RC008T-2, +in order to use ISP mode, the jumper for AREF0 must be removed +as it would otherwise block one of the ISP signals. High-voltage +serial programming can be used even with that jumper installed. +

+

The ISP system of the STK600 contains a detection against shortcuts +and other wiring errors. AVRDUDE initiates a connection check before +trying to enter ISP programming mode, and display the result if the +target is not found ready to be ISP programmed. +

+

High-voltage programming requires the target voltage to be set to at +least 4.5 V in order to work. This can be done using +Terminal Mode, see Terminal Mode Operation. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_16.html b/docs/avrdude_16.html new file mode 100644 index 00000000..5dd0cca1 --- /dev/null +++ b/docs/avrdude_16.html @@ -0,0 +1,109 @@ + + + + +AVRDUDE: 5.2 Atmel DFU bootloader using FLIP version 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

5.2 Atmel DFU bootloader using FLIP version 1

+ +

Bootloaders using the FLIP protocol version 1 experience some very +specific behaviour. +

+

These bootloaders have no option to access memory areas other than +Flash and EEPROM. +

+

When the bootloader is started, it enters a security mode where +the only acceptable access is to query the device configuration +parameters (which are used for the signature on AVR devices). The +only way to leave this mode is a chip erase. As a chip erase +is normally implied by the ‘-U’ option when reprogramming the +flash, this peculiarity might not be very obvious immediately. +

+

Sometimes, a bootloader with security mode already disabled seems to +no longer respond with sensible configuration data, but only 0xFF for +all queries. As these queries are used to obtain the equivalent of a +signature, AVRDUDE can only continue in that situation by forcing the +signature check to be overridden with the ‘-F’ option. +

+

A chip erase might leave the EEPROM unerased, at least on some +versions of the bootloader. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_17.html b/docs/avrdude_17.html new file mode 100644 index 00000000..d8eeae8e --- /dev/null +++ b/docs/avrdude_17.html @@ -0,0 +1,181 @@ + + + + +AVRDUDE: 5.3 SerialUPDI programmer + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

5.3 SerialUPDI programmer

+ +

SerialUPDI programmer can be used for programming UPDI-only devices +using very simple serial connection. +You can read more about the details here +https://github.com/SpenceKonde/AVR-Guidance/blob/master/UPDI/jtag2updi.md +

+

SerialUPDI programmer has been tested using FT232RL USB->UART interface +with the following connection layout (copied from Spence Kohde’s page linked +above): +

+
+
--------------------                                 To Target device
+                DTR|                                  __________________
+                Rx |--------------,------------------| UPDI---\/\/---------->
+  Tx---/\/\/\---Tx |-------|<|---'          .--------| Gnd    470 ohm 
+    resistor    Vcc|---------------------------------| Vcc
+        1k      CTS|                     .`          |__________________
+                Gnd|--------------------' 
+--------------------
+
+ +

There are several limitations in current SerialUPDI/AVRDUDE integration, +listed below. +

+

At the end of each run there are fuse values being presented to the user. +For most of the UPDI-enabled devices these definitions (low fuse, high +fuse, extended fuse) have no meaning whatsoever, as they have been +simply replaced by array of fuses: fuse0..9. Therefore you can simply +ignore this particular line of AVRDUDE output. +

+

Currently available devices support only UPDI NVM programming model 0 +and 2, but there is also experimental implementation of model 3 - not +yet tested. +

+

One of the core AVRDUDE features is verification of the connection by +reading device signature prior to any operation, but this operation +is not possible on UPDI locked devices. Therefore, to be able to +connect to such a device, you have to provide ‘-F’ to override +this check. +

+

Please note: using ‘-F’ during write operation to locked device +will force chip erase. Use carefully. +

+

Another issue you might notice is slow performance of EEPROM writing +using SerialUPDI for AVR Dx devices. This can be addressed by changing +avrdude.conf section for this device - changing EEPROM page +size to 0x20 (instead of default 1), like so: +

+
+
#------------------------------------------------------------
+# AVR128DB28
+#------------------------------------------------------------
+
+part parent    ".avrdx"
+    id        = "avr128db28";
+    desc      = "AVR128DB28";
+    signature = 0x1E 0x97 0x0E;
+
+    memory "flash"
+        size      = 0x20000;
+        offset    = 0x800000;
+        page_size = 0x200;
+        readsize  = 0x100;
+    ;
+
+    memory "eeprom"
+        size      = 0x200;
+        offset    = 0x1400;
+        page_size = 0x1;
+        readsize  = 0x100;
+    ;
+;
+
+ +

USERROW memory has not been defined for new devices except for +experimental addition for AVR128DB28. The point of USERROW is to +provide ability to write configuration details to already locked +device and currently SerialUPDI interface supports this feature, +but it hasn’t been tested on wide variety of chips. Treat this as +something experimental at this point. Please note: on locked devices +it’s not possible to read back USERROW contents when written, so +the automatic verification will most likely fail and to prevent +error messages, use ‘-V’. +

+

Please note that SerialUPDI interface is pretty new and some +issues are to be expected. In case you run into them, please +make sure to run the intended command with debug output enabled +(‘-v -v -v’) and provide this verbose output with your +bug report. You can also try to perform the same action using +pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) +utility with ‘-v debug’ and provide its output too. +You will notice that both outputs are pretty similar, and this +was implemented like that on purpose - it was supposed to make +analysis of UPDI protocol quirks easier. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_18.html b/docs/avrdude_18.html new file mode 100644 index 00000000..b4a86203 --- /dev/null +++ b/docs/avrdude_18.html @@ -0,0 +1,94 @@ + + + + +AVRDUDE: Appendix A Platform Dependent Information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

Appendix A Platform Dependent Information

+ + + + +
A.1 Unix   +
A.2 Windows   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_19.html b/docs/avrdude_19.html new file mode 100644 index 00000000..085353f2 --- /dev/null +++ b/docs/avrdude_19.html @@ -0,0 +1,373 @@ + + + + +AVRDUDE: A.1 Unix + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.1 Unix

+ + + + + + +
A.1.1 Unix Installation   +
A.1.2 Unix Configuration Files   +
A.1.3 Unix Port Names   +
A.1.4 Unix Documentation   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.1.1 Unix Installation

+ +

To build and install from the source tarball on Unix like systems: +

+
+
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure
+$ make
+$ su root -c 'make install'
+
+ +

The default location of the install is into /usr/local so you +will need to be sure that /usr/local/bin is in your PATH +environment variable. +

+

If you do not have root access to your system, you can do the +following instead: +

+
+
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure --prefix=$HOME/local
+$ make
+$ make install
+
+ + + + +
A.1.1.1 FreeBSD Installation   +
A.1.1.2 Linux Installation   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.1.1.1 FreeBSD Installation

+ +

AVRDUDE is installed via the FreeBSD Ports Tree as follows: +

+
+
% su - root
+# cd /usr/ports/devel/avrdude
+# make install
+
+ +

If you wish to install from a pre-built package instead of the source, +you can use the following instead: +

+
+
% su - root
+# pkg_add -r avrdude
+
+ +

Of course, you must be connected to the Internet for these methods to +work, since that is where the source as well as the pre-built package is +obtained. +

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

A.1.1.2 Linux Installation

+ +

On rpm based Linux systems (such as RedHat, SUSE, Mandrake, etc.), you +can build and install the rpm binaries directly from the tarball: +

+
+
$ su - root
+# rpmbuild -tb avrdude-6.99-20211218.tar.gz
+# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-6.99-20211218-1.i386.rpm
+
+ +

Note that the path to the resulting rpm package, differs from system +to system. The above example is specific to RedHat. +

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

A.1.2 Unix Configuration Files

+ +

When AVRDUDE is build using the default ‘--prefix’ configure +option, the default configuration file for a Unix system is located at +/usr/local/etc/avrdude.conf. This can be overridden by using the +‘-C’ command line option. Additionally, the user’s home directory +is searched for a file named .avrduderc, and if found, is used to +augment the system default configuration file. +

+ + + +
A.1.2.1 FreeBSD Configuration Files   +
A.1.2.2 Linux Configuration Files   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.1.2.1 FreeBSD Configuration Files

+ +

When AVRDUDE is installed using the FreeBSD ports system, the system +configuration file is always /usr/local/etc/avrdude.conf. +

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

A.1.2.2 Linux Configuration Files

+ +

When AVRDUDE is installed using from an rpm package, the system +configuration file will be always be /etc/avrdude.conf. +

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

A.1.3 Unix Port Names

+ +

The parallel and serial port device file names are system specific. +The following table lists the default names for a given system. +

+ + + + + +
SystemDefault Parallel PortDefault Serial Port
FreeBSD/dev/ppi0/dev/cuad0
Linux/dev/parport0/dev/ttyS0
Solaris/dev/printers/0/dev/term/a
+ +

On FreeBSD systems, AVRDUDE uses the ppi(4) interface for +accessing the parallel port and the sio(4) driver for serial port +access. +

+

On Linux systems, AVRDUDE uses the ppdev interface for +accessing the parallel port and the tty driver for serial port +access. +

+

On Solaris systems, AVRDUDE uses the ecpp(7D) driver for +accessing the parallel port and the asy(7D) driver for serial port +access. +

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

A.1.4 Unix Documentation

+ +

AVRDUDE installs a manual page as well as info, HTML and PDF +documentation. The manual page is installed in +/usr/local/man/man1 area, while the HTML and PDF documentation +is installed in /usr/local/share/doc/avrdude directory. The +info manual is installed in /usr/local/info/avrdude.info. +

+

Note that these locations can be altered by various configure options +such as ‘--prefix’. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_2.html b/docs/avrdude_2.html new file mode 100644 index 00000000..074de75e --- /dev/null +++ b/docs/avrdude_2.html @@ -0,0 +1,97 @@ + + + + +AVRDUDE: 2 Command Line Options + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

2 Command Line Options

+ + + + + + +
2.1 Option Descriptions   +
2.2 Programmers accepting extended parameters   +
2.3 Example Command Line Invocations   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_20.html b/docs/avrdude_20.html new file mode 100644 index 00000000..d36ceac1 --- /dev/null +++ b/docs/avrdude_20.html @@ -0,0 +1,378 @@ + + + + +AVRDUDE: A.2 Windows + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.2 Windows

+ + + + + + +
A.2.1 Installation   +
A.2.2 Configuration Files   +
A.2.3 Port Names   +
A.2.4 Documentation   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.2.1 Installation

+ +

A Windows executable of avrdude is included in WinAVR which can be found at +http://sourceforge.net/projects/winavr. WinAVR is a suite of executable, +open source software development tools for the AVR for the Windows platform. +

+

There are two options to build avrdude from source under Windows. +The first one is to use Cygwin (http://www.cygwin.com/). +

+

To build and install from the source tarball for Windows (using Cygwin): +

+
+
$ set PREFIX=<your install directory path>
+$ export PREFIX
+$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure LDFLAGS="-static" --prefix=$PREFIX --datadir=$PREFIX 
+--sysconfdir=$PREFIX/bin --enable-versioned-doc=no
+$ make
+$ make install
+
+ +

Note that recent versions of Cygwin (starting with 1.7) removed the +MinGW support from the compiler that is needed in order to build a +native Win32 API binary that does not require to install the Cygwin +library cygwin1.dll at run-time. Either try using an older +compiler version that still supports MinGW builds, or use MinGW +(http://www.mingw.org/) directly. +

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

A.2.2 Configuration Files

+ + + + +
A.2.2.1 Configuration file names   +
A.2.2.2 How AVRDUDE finds the configuration files.   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.2.2.1 Configuration file names

+ +

AVRDUDE on Windows looks for a system configuration file name of +avrdude.conf and looks for a user override configuration file of +avrdude.rc. +

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

A.2.2.2 How AVRDUDE finds the configuration files.

+ +

AVRDUDE on Windows has a different way of searching for the system and +user configuration files. Below is the search method for locating the +configuration files: +

+
    +
  1. +Only for the system configuration file: +<directory from which application loaded>/../etc/avrdude.conf + +
  2. +The directory from which the application loaded. + +
  3. +The current directory. + +
  4. +The Windows system directory. On Windows NT, the name of this directory +is SYSTEM32. + +
  5. +Windows NT: The 16-bit Windows system directory. The name of this +directory is SYSTEM. + +
  6. +The Windows directory. + +
  7. +The directories that are listed in the PATH environment variable. + +
+ + +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.2.3 Port Names

+ + + + +
A.2.3.1 Serial Ports   +
A.2.3.2 Parallel Ports   +
+ +
+ + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

A.2.3.1 Serial Ports

+ +

When you select a serial port (i.e. when using an STK500) use the +Windows serial port device names such as: com1, com2, etc. +

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

A.2.3.2 Parallel Ports

+ +

AVRDUDE will accept 3 Windows parallel port names: lpt1, lpt2, or +lpt3. Each of these names corresponds to a fixed parallel port base +address: +

+
+
lpt1
+

0x378 +

+
+
lpt2
+

0x278 +

+
+
lpt3
+

0x3BC +

+
+
+ +

On your desktop PC, lpt1 will be the most common choice. If you are +using a laptop, you might have to use lpt3 instead of lpt1. Select the +name of the port the corresponds to the base address of the parallel +port that you want. +

+

If the parallel port can be accessed through a different +address, this address can be specified directly, using the common C +language notation (i. e., hexadecimal values are prefixed by 0x). +

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

A.2.4 Documentation

+ +

AVRDUDE installs a manual page as well as info, HTML and PDF +documentation. The manual page is installed in +/usr/local/man/man1 area, while the HTML and PDF documentation +is installed in /usr/local/share/doc/avrdude directory. The +info manual is installed in /usr/local/info/avrdude.info. +

+

Note that these locations can be altered by various configure options +such as ‘--prefix’ and ‘--datadir’. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_21.html b/docs/avrdude_21.html new file mode 100644 index 00000000..baaaec80 --- /dev/null +++ b/docs/avrdude_21.html @@ -0,0 +1,395 @@ + + + + +AVRDUDE: Appendix B Troubleshooting + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

Appendix B Troubleshooting

+ +

In general, please report any bugs encountered via +
+http://savannah.nongnu.org/bugs/?group=avrdude. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_3.html b/docs/avrdude_3.html new file mode 100644 index 00000000..5cca66b3 --- /dev/null +++ b/docs/avrdude_3.html @@ -0,0 +1,1003 @@ + + + + +AVRDUDE: 2.1 Option Descriptions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

2.1 Option Descriptions

+ +

AVRDUDE is a command line tool, used as follows: +

+
+
avrdude -p partno options …
+
+ +

Command line options are used to control AVRDUDE’s behaviour. The +following options are recognized: +

+
+
-p partno
+

This is the only mandatory option and it tells AVRDUDE what type of part +(MCU) that is connected to the programmer. The partno parameter +is the part’s id listed in the configuration file. Specify -p ? to list +all parts in the configuration file. If a part is unknown +to AVRDUDE, it means that there is no config file entry for that part, +but it can be added to the configuration file if you have the Atmel +datasheet so that you can enter the programming specifications. +Currently, the following MCU types are understood: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
uc3a0512AT32UC3A0512
c128AT90CAN128
c32AT90CAN32
c64AT90CAN64
pwm2AT90PWM2
pwm216AT90PWM216
pwm2bAT90PWM2B
pwm3AT90PWM3
pwm316AT90PWM316
pwm3bAT90PWM3B
1200AT90S1200 (****)
2313AT90S2313
2333AT90S2333
2343AT90S2343 (*)
4414AT90S4414
4433AT90S4433
4434AT90S4434
8515AT90S8515
8535AT90S8535
usb1286AT90USB1286
usb1287AT90USB1287
usb162AT90USB162
usb646AT90USB646
usb647AT90USB647
usb82AT90USB82
m103ATmega103
m128ATmega128
m1280ATmega1280
m1281ATmega1281
m1284ATmega1284
m1284pATmega1284P
m1284rfr2ATmega1284RFR2
m128aATmega128A
m128rfa1ATmega128RFA1
m128rfr2ATmega128RFR2
m16ATmega16
m1608ATmega1608
m1609ATmega1609
m161ATmega161
m162ATmega162
m163ATmega163
m164aATmega164A
m164pATmega164P
m164paATmega164PA
m165ATmega165
m165aATmega165A
m165pATmega165P
m165paATmega165PA
m168ATmega168
m168aATmega168A
m168pATmega168P
m168paATmega168PA
m168pbATmega168PB
m169ATmega169
m169aATmega169A
m169pATmega169P
m169paATmega169PA
m16aATmega16A
m16u2ATmega16U2
m2560ATmega2560 (**)
m2561ATmega2561 (**)
m2564rfr2ATmega2564RFR2
m256rfr2ATmega256RFR2
m32ATmega32
m3208ATmega3208
m3209ATmega3209
m324aATmega324A
m324pATmega324P
m324paATmega324PA
m324pbATmega324PB
m325ATmega325
m3250ATmega3250
m3250aATmega3250A
m3250pATmega3250P
m3250paATmega3250PA
m325aATmega325A
m325pATmega325P
m325paATmega325PA
m328ATmega328
m328pATmega328P
m328pbATmega328PB
m329ATmega329
m3290ATmega3290
m3290aATmega3290A
m3290pATmega3290P
m3290paATmega3290PA
m329aATmega329a
m329pATmega329P
m329paATmega329PA
m32aATmega32A
m32m1ATmega32M1
m32u2ATmega32U2
m32u4ATmega32U4
m406ATMEGA406
m48ATmega48
m4808ATmega4808
m4809ATmega4809
m48aATmega48A
m48pATmega48P
m48paATmega48PA
m48pbATmega48PB
m64ATmega64
m640ATmega640
m644ATmega644
m644aATmega644A
m644pATmega644P
m644paATmega644PA
m644rfr2ATmega644RFR2
m645ATmega645
m6450ATmega6450
m6450aATmega6450A
m6450pATmega6450P
m645aATmega645A
m645pATmega645P
m649ATmega649
m6490ATmega6490
m6490aATmega6490A
m6490pATmega6490P
m649aATmega649A
m649pATmega649P
m64aATmega64A
m64m1ATmega64M1
m64rfr2ATmega64RFR2
m8ATmega8
m808ATmega808
m809ATmega809
m8515ATmega8515
m8535ATmega8535
m88ATmega88
m88aATmega88A
m88pATmega88P
m88paATmega88PA
m88pbATmega88PB
m8aATmega8A
m8u2ATmega8U2
t10ATtiny10
t102ATtiny102
t104ATtiny104
t11ATtiny11 (***)
t12ATtiny12
t13ATtiny13
t13aATtiny13A
t15ATtiny15
t1604ATtiny1604
t1606ATtiny1606
t1607ATtiny1607
t1614ATtiny1614
t1616ATtiny1616
t1617ATtiny1617
t1624ATtiny1624
t1626ATtiny1626
t1627ATtiny1627
t1634ATtiny1634
t1634rATtiny1634R
t167ATtiny167
t20ATtiny20
t202ATtiny202
t204ATtiny204
t212ATtiny212
t214ATtiny214
t2313ATtiny2313
t2313aATtiny2313A
t24ATtiny24
t24aATtiny24A
t25ATtiny25
t26ATtiny26
t261ATtiny261
t261aATtiny261A
t28ATtiny28
t3216ATtiny3216
t3217ATtiny3217
t3224ATtiny3224
t3226ATtiny3226
t3227ATtiny3227
t4ATtiny4
t40ATtiny40
t402ATtiny402
t404ATtiny404
t406ATtiny406
t412ATtiny412
t414ATtiny414
t416ATtiny416
t417ATtiny417
t424ATtiny424
t426ATtiny426
t427ATtiny427
t4313ATtiny4313
t43uATtiny43u
t44ATtiny44
t441ATtiny441
t44aATtiny44A
t45ATtiny45
t461ATtiny461
t461aATtiny461A
t48ATtiny48
t5ATtiny5
t804ATtiny804
t806ATtiny806
t807ATtiny807
t814ATtiny814
t816ATtiny816
t817ATtiny817
t824ATtiny824
t826ATtiny826
t827ATtiny827
t828ATtiny828
t828rATtiny828R
t84ATtiny84
t841ATtiny841
t84aATtiny84A
t85ATtiny85
t861ATtiny861
t861aATtiny861A
t87ATtiny87
t88ATtiny88
t9ATtiny9
x128a1ATxmega128A1
x128a1dATxmega128A1revD
x128a1uATxmega128A1U
x128a3ATxmega128A3
x128a3uATxmega128A3U
x128a4ATxmega128A4
x128a4uATxmega128A4U
x128b1ATxmega128B1
x128b3ATxmega128B3
x128c3ATxmega128C3
x128d3ATxmega128D3
x128d4ATxmega128D4
x16a4ATxmega16A4
x16a4uATxmega16A4U
x16c4ATxmega16C4
x16d4ATxmega16D4
x16e5ATxmega16E5
x192a1ATxmega192A1
x192a3ATxmega192A3
x192a3uATxmega192A3U
x192c3ATxmega192C3
x192d3ATxmega192D3
x256a1ATxmega256A1
x256a3ATxmega256A3
x256a3bATxmega256A3B
x256a3buATxmega256A3BU
x256a3uATxmega256A3U
x256c3ATxmega256C3
x256d3ATxmega256D3
x32a4ATxmega32A4
x32a4uATxmega32A4U
x32c4ATxmega32C4
x32d4ATxmega32D4
x32e5ATxmega32E5
x384c3ATxmega384C3
x384d3ATxmega384D3
x64a1ATxmega64A1
x64a1uATxmega64A1U
x64a3ATxmega64A3
x64a3uATxmega64A3U
x64a4ATxmega64A4
x64a4uATxmega64A4U
x64b1ATxmega64B1
x64b3ATxmega64B3
x64c3ATxmega64C3
x64d3ATxmega64D3
x64d4ATxmega64D4
x8e5ATxmega8E5
avr128da28AVR128DA28
avr128da32AVR128DA32
avr128da48AVR128DA48
avr128da64AVR128DA64
avr128db28AVR128DB28
avr128db32AVR128DB32
avr128db48AVR128DB48
avr128db64AVR128DB64
avr16dd14AVR16DD14
avr16dd20AVR16DD20
avr16dd28AVR16DD28
avr16dd32AVR16DD32
avr16ea28AVR16EA28
avr16ea32AVR16EA32
avr16ea48AVR16EA48
avr32da28AVR32DA28
avr32da32AVR32DA32
avr32da48AVR32DA48
avr32db28AVR32DB28
avr32db32AVR32DB32
avr32db48AVR32DB48
avr32dd14AVR32DD14
avr32dd20AVR32DD20
avr32dd28AVR32DD28
avr32dd32AVR32DD32
avr32ea28AVR32EA28
avr32ea32AVR32EA32
avr32ea48AVR32EA48
avr64da28AVR64DA28
avr64da32AVR64DA32
avr64da48AVR64DA48
avr64da64AVR64DA64
avr64db28AVR64DB28
avr64db32AVR64DB32
avr64db48AVR64DB48
avr64db64AVR64DB64
avr64dd14AVR64DD14
avr64dd20AVR64DD20
avr64dd28AVR64DD28
avr64dd32AVR64DD32
avr64ea28AVR64EA28
avr64ea32AVR64EA32
avr64ea48AVR64EA48
avr8ea28AVR8EA28
avr8ea32AVR8EA32
ucr2deprecated,
lgt8f168pLGT8F168P
lgt8f328pLGT8F328P
lgt8f88pLGT8F88P
+ +

(*) The AT90S2323 and ATtiny22 use the same algorithm. +

+

(**) Flash addressing above 128 KB is not supported by all +programming hardware. Known to work are jtag2, stk500v2, +and bit-bang programmers. +

+

(***) +The ATtiny11 can only be +programmed in high-voltage serial mode. +

+

(****) +The ISP programming protocol of the AT90S1200 differs in subtle ways +from that of other AVRs. Thus, not all programmers support this +device. Known to work are all direct bitbang programmers, and all +programmers talking the STK500v2 protocol. +

+
+
-b baudrate
+

Override the RS-232 connection baud rate specified in the respective +programmer’s entry of the configuration file. +

+
+
-B bitclock
+

Specify the bit clock period for the JTAG interface or the ISP clock (JTAG ICE only). +The value is a floating-point number in microseconds. +Alternatively, the value might be suffixed with "Hz", "kHz", or "MHz", +in order to specify the bit clock frequency, rather than a period. +The default value of the JTAG ICE results in about 1 microsecond bit +clock period, suitable for target MCUs running at 4 MHz clock and +above. +Unlike certain parameters in the STK500, the JTAG ICE resets all its +parameters to default values when the programming software signs +off from the ICE, so for MCUs running at lower clock speeds, this +parameter must be specified on the command-line. +It can also be set in the configuration file by using the ’default_bitclock’ +keyword. +

+
+
-c programmer-id
+

Specify the programmer to be used. AVRDUDE knows about several common +programmers. Use this option to specify which one to use. The +programmer-id parameter is the programmer’s id listed in the +configuration file. Specify -c ? to list all programmers in the +configuration file. If you have a programmer that is unknown to +AVRDUDE, and the programmer is controlled via the PC parallel port, +there’s a good chance that it can be easily added to the configuration +file without any code changes to AVRDUDE. Simply copy an existing entry +and change the pin definitions to match that of the unknown programmer. +Currently, the following programmer ids are understood and supported: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
2232HIOFT2232H based generic programmer
4232hFT4232H based generic programmer
arduinoArduino
arduino-ft232rArduino: FT232R connected to ISP
arduinoispArduino ISP Programmer
arduinoisporgArduino ISP Programmer
atmeliceAtmel-ICE (ARM/AVR) in JTAG mode
atmelice_dwAtmel-ICE (ARM/AVR) in debugWIRE mode
atmelice_ispAtmel-ICE (ARM/AVR) in ISP mode
atmelice_pdiAtmel-ICE (ARM/AVR) in PDI mode
atmelice_updiAtmel-ICE (ARM/AVR) in UPDI mode
avr109Atmel AppNote AVR109 Boot Loader
avr910Atmel Low Cost Serial Programmer
avr911Atmel AppNote AVR911 AVROSP
avrftdiFT2232D based generic programmer
avrispAtmel AVR ISP
avrisp2Atmel AVR ISP mkII
avrispmkIIAtmel AVR ISP mkII
avrispv2Atmel AVR ISP V2
buspirateThe Bus Pirate
buspirate_bbThe Bus Pirate (bitbang interface, supports TPI)
butterflyAtmel Butterfly Development Board
butterfly_mkMikrokopter.de Butterfly
bwmegaBitWizard ftdi_atmega builtin programmer
c232hmC232HM cable from FTDI
c2n232iserial port banging, reset=dtr sck=!rts mosi=!txd miso=!cts
dasaserial port banging, reset=rts sck=dtr mosi=txd miso=cts
dasa3serial port banging, reset=!dtr sck=rts mosi=txd miso=cts
diecimilaalias for arduino-ft232r
dragon_dwAtmel AVR Dragon in debugWire mode
dragon_hvspAtmel AVR Dragon in HVSP mode
dragon_ispAtmel AVR Dragon in ISP mode
dragon_jtagAtmel AVR Dragon in JTAG mode
dragon_pdiAtmel AVR Dragon in PDI mode
dragon_ppAtmel AVR Dragon in PP mode
ehajo-ispavr-isp-programmer from eHaJo, http://www.eHaJo.de
flip1FLIP USB DFU protocol version 1 (doc7618)
flip2FLIP USB DFU protocol version 2 (AVR4023)
ft232hFT232H in MPSSE mode
ft232rFT232R Synchronous BitBang
ft245rFT245R Synchronous BitBang
iseavrprogUSBtiny-based USB programmer, https://github.com/IowaScaledEngineering/ckt-avrp
jtag1Atmel JTAG ICE (mkI)
jtag1slowAtmel JTAG ICE (mkI)
jtag2Atmel JTAG ICE mkII
jtag2avr32Atmel JTAG ICE mkII im AVR32 mode
jtag2dwAtmel JTAG ICE mkII in debugWire mode
jtag2fastAtmel JTAG ICE mkII
jtag2ispAtmel JTAG ICE mkII in ISP mode
jtag2pdiAtmel JTAG ICE mkII PDI mode
jtag2slowAtmel JTAG ICE mkII
jtag2updiJTAGv2 to UPDI bridge
jtag3Atmel AVR JTAGICE3 in JTAG mode
jtag3dwAtmel AVR JTAGICE3 in debugWIRE mode
jtag3ispAtmel AVR JTAGICE3 in ISP mode
jtag3pdiAtmel AVR JTAGICE3 in PDI mode
jtag3updiAtmel AVR JTAGICE3 in UPDI mode
jtagkeyAmontec JTAGKey, JTAGKey-Tiny and JTAGKey2
jtagmkIAtmel JTAG ICE (mkI)
jtagmkIIAtmel JTAG ICE mkII
jtagmkII_avr32Atmel JTAG ICE mkII im AVR32 mode
lm3s811Luminary Micro LM3S811 Eval Board (Rev. A)
mib510Crossbow MIB510 programming board
micronucleusMicronucleus Bootloader
mkbutterflyMikrokopter.de Butterfly
nibobeeNIBObee
o-linkO-Link, OpenJTAG from www.100ask.net
openmokoOpenmoko debug board (v3)
pavrJason Kyle’s pAVR Serial Programmer
pickit2MicroChip’s PICkit2 Programmer
pickit4_ispMPLAB(R) PICkit 4 in ISP mode
pickit4_pdiMPLAB(R) PICkit 4 in PDI mode
pickit4_updiMPLAB(R) PICkit 4 in UPDI mode
pkobn_updiCuriosity nano (nEDBG) in UPDI mode
ponyserdesign ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts
powerdebuggerAtmel PowerDebugger (ARM/AVR) in JTAG mode
powerdebugger_dwAtmel PowerDebugger (ARM/AVR) in debugWire mode
powerdebugger_ispAtmel PowerDebugger (ARM/AVR) in ISP mode
powerdebugger_pdiAtmel PowerDebugger (ARM/AVR) in PDI mode
powerdebugger_updiAtmel PowerDebugger (ARM/AVR) in UPDI mode
serialupdiSerialUPDI
siprogLancos SI-Prog <http://www.lancos.com/siprogsch.html>
snap_ispMPLAB(R) SNAP in ISP mode
snap_pdiMPLAB(R) SNAP in PDI mode
snap_updiMPLAB(R) SNAP in UPDI mode
stk500Atmel STK500
stk500hvspAtmel STK500 V2 in high-voltage serial programming mode
stk500ppAtmel STK500 V2 in parallel programming mode
stk500v1Atmel STK500 Version 1.x firmware
stk500v2Atmel STK500 Version 2.x firmware
stk600Atmel STK600
stk600hvspAtmel STK600 in high-voltage serial programming mode
stk600ppAtmel STK600 in parallel programming mode
tc2030Tag-Connect TC2030
teensyTeensy Bootloader
ttl232rFTDI TTL232R-5V with ICSP adapter
tumpaTIAO USB Multi-Protocol Adapter
um232hUM232H module from FTDI
uncompatinouncompatino with all pairs of pins shorted
usbaspUSBasp, http://www.fischl.de/usbasp/
usbasp-cloneAny usbasp clone with correct VID/PID
usbtinyUSBtiny simple USB programmer, https://learn.adafruit.com/usbtinyisp
wiringWiring
xbeeXBee Series 2 Over-The-Air (XBeeBoot)
xplainedminiAtmel AVR XplainedMini in ISP mode
xplainedmini_dwAtmel AVR XplainedMini in debugWIRE mode
xplainedmini_updiAtmel AVR XplainedMini in UPDI mode
xplainedproAtmel AVR XplainedPro in JTAG mode
xplainedpro_updiAtmel AVR XplainedPro in UPDI mode
+ + + +
+
-C config-file
+

Use the specified config file for configuration data. This file +contains all programmer and part definitions that AVRDUDE knows about. +If not specified, AVRDUDE looks for the configuration file in the following +two locations: +

+
    +
  1. +<directory from which application loaded>/../etc/avrdude.conf + +
  2. +<directory from which application loaded>/avrdude.conf + +
+ +

If not found there, the lookup procedure becomes platform dependent. On FreeBSD +and Linux, AVRDUDE looks at /usr/local/etc/avrdude.conf. See Appendix A +for the method of searching on Windows. +

+

If config-file is written as +filename +then this file is read after the system wide and user configuration +files. This can be used to add entries to the configuration +without patching your system wide configuration file. It can be used +several times, the files are read in same order as given on the command +line. +

+ +
+
-D
+

Disable auto erase for flash. When the -U option with flash memory is +specified, avrdude will perform a chip erase before starting any of the +programming operations, since it generally is a mistake to program the flash +without performing an erase first. This option disables that. +Auto erase is not used for ATxmega devices as these devices can +use page erase before writing each page so no explicit chip erase +is required. +Note however that any page not affected by the current operation +will retain its previous contents. +

+
+
-e
+

Causes a chip erase to be executed. This will reset the contents of the +flash ROM and EEPROM to the value ‘0xff’, and clear all lock bits. +Except for ATxmega devices which can use page erase, +it is basically a +prerequisite command before the flash ROM can be reprogrammed again. +The only exception would be if the new contents would exclusively cause +bits to be programmed from the value ‘1’ to ‘0’. Note that in order +to reprogram EERPOM cells, no explicit prior chip erase is required +since the MCU provides an auto-erase cycle in that case before +programming the cell. +

+ +
+
-E exitspec[,…]
+

By default, AVRDUDE leaves the parallel port in the same state at exit +as it has been found at startup. This option modifies the state of the +‘/RESET’ and ‘Vcc’ lines the parallel port is left at, according to +the exitspec arguments provided, as follows: +

+
+
reset
+

The ‘/RESET’ signal will be left activated at program exit, that is it +will be held low, in order to keep the MCU in reset state afterwards. +Note in particular that the programming algorithm for the AT90S1200 +device mandates that the ‘/RESET’ signal is active before powering up +the MCU, so in case an external power supply is used for this MCU type, +a previous invocation of AVRDUDE with this option specified is one of +the possible ways to guarantee this condition. +

+
+
noreset
+

The ‘/RESET’ line will be deactivated at program exit, thus allowing the +MCU target program to run while the programming hardware remains +connected. +

+
+
vcc
+

This option will leave those parallel port pins active (i. e. high) that +can be used to supply ‘Vcc’ power to the MCU. +

+
+
novcc
+

This option will pull the ‘Vcc’ pins of the parallel port down at +program exit. +

+
+
d_high
+

This option will leave the 8 data pins on the parallel port active +(i. e. high). +

+
+
d_low
+

This option will leave the 8 data pins on the parallel port inactive +(i. e. low). +

+
+
+ +

Multiple exitspec arguments can be separated with commas. +

+ +
+
-F
+

Normally, AVRDUDE tries to verify that the device signature read from +the part is reasonable before continuing. Since it can happen from time +to time that a device has a broken (erased or overwritten) device +signature but is otherwise operating normally, this options is provided +to override the check. +Also, for programmers like the Atmel STK500 and STK600 which can +adjust parameters local to the programming tool (independent of an +actual connection to a target controller), this option can be used +together with ‘-t’ to continue in terminal mode. +

+
+
-i delay
+

For bitbang-type programmers, delay for approximately +delay +microseconds between each bit state change. +If the host system is very fast, or the target runs off a slow clock +(like a 32 kHz crystal, or the 128 kHz internal RC oscillator), this +can become necessary to satisfy the requirement that the ISP clock +frequency must not be higher than 1/4 of the CPU clock frequency. +This is implemented as a spin-loop delay to allow even for very +short delays. +On Unix-style operating systems, the spin loop is initially calibrated +against a system timer, so the number of microseconds might be rather +realistic, assuming a constant system load while AVRDUDE is running. +On Win32 operating systems, a preconfigured number of cycles per +microsecond is assumed that might be off a bit for very fast or very +slow machines. +

+
+
-l logfile
+

Use logfile rather than stderr for diagnostics output. +Note that initial diagnostic messages (during option parsing) are still +written to stderr anyway. +

+
+
-n
+

No-write - disables actually writing data to the MCU (useful for +debugging AVRDUDE). +

+
+
-O
+

Perform a RC oscillator run-time calibration according to Atmel +application note AVR053. +This is only supported on the STK500v2, AVRISP mkII, and JTAG ICE mkII +hardware. +Note that the result will be stored in the EEPROM cell at address 0. +

+
+
-P port
+

Use port to identify the device to which the programmer is attached. +Normally, the default parallel port is used, but if the programmer type +normally connects to the serial port, the default serial port will be +used. See Appendix A, Platform Dependent Information, to find out the +default port names for your platform. If you need to use a different +parallel or serial port, use this option to specify the alternate port name. +

+

On Win32 operating systems, the parallel ports are referred to as lpt1 +through lpt3, referring to the addresses 0x378, 0x278, and 0x3BC, +respectively. If the parallel port can be accessed through a different +address, this address can be specified directly, using the common C +language notation (i. e., hexadecimal values are prefixed by 0x). +

+

For the JTAG ICE mkII, if AVRDUDE has been built with libusb support, +port may alternatively be specified as +usb[:serialno]. In that case, the JTAG ICE mkII will be +looked up on USB. If serialno is also specified, it will be +matched against the serial number read from any JTAG ICE mkII found on +USB. The match is done after stripping any existing colons from the +given serial number, and right-to-left, so only the least significant +bytes from the serial number need to be given. +For a trick how to find out the serial numbers of all JTAG ICEs +attached to USB, see Example Command Line Invocations. +

+

As the AVRISP mkII device can only be talked to over USB, the very +same method of specifying the port is required there. +

+

For the USB programmer "AVR-Doper" running in HID mode, the port must +be specified as avrdoper. Libhidapi support is required on Unix +and Mac OS but not on Windows. For more information about AVR-Doper see +http://www.obdev.at/avrusb/avrdoper.html. +

+

For the USBtinyISP, which is a simplistic device not implementing +serial numbers, multiple devices can be distinguished by their +location in the USB hierarchy. +See the respective +See section Troubleshooting entry for examples. +

+

For the XBee programmer the target MCU is to be programmed wirelessly +over a ZigBee mesh using the XBeeBoot bootloader. The ZigBee 64-bit +address for the target MCU’s own XBee device must be supplied as a +16-character hexadecimal value as a port prefix, followed by the +@ character, and the serial device to connect to a second +directly contactable XBee device associated with the same mesh (with +a default baud rate of 9600). This may look similar to: +0013a20000000001dev/tty.serial. +

+

For diagnostic purposes, if the target MCU with an XBeeBoot +bootloader is connected directly to the serial port, the +64-bit address field can be omitted. In this mode the +default baud rate will be 19200. +

+

For programmers that attach to a serial port using some kind of +higher level protocol (as opposed to bit-bang style programmers), +port can be specified as net:host:port. +In this case, instead of trying to open a local device, a TCP +network connection to (TCP) port on host +is established. +Square brackets may be placed around host to improve +readability for numeric IPv6 addresses (e.g. +net:[2001:db8::42]:1337). +The remote endpoint is assumed to be a terminal or console server +that connects the network stream to a local serial port where the +actual programmer has been attached to. +The port is assumed to be properly configured, for example using a +transparent 8-bit data connection without parity at 115200 Baud +for a STK500. +

+

Note: The ability to handle IPv6 hostnames and addresses is limited to +Posix systems (by now). +

+
+
-q
+

Disable (or quell) output of the progress bar while reading or writing +to the device. Specify it a second time for even quieter operation. +

+
+
-t
+

Tells AVRDUDE to enter the interactive “terminal” mode instead of up- +or downloading files. See below for a detailed description of the +terminal mode. +

+
+
-U memtype:op:filename[:format]
+

Perform a memory operation. +Multiple ‘-U’ options can be specified in order to operate on +multiple memories on the same command-line invocation. The +memtype field specifies the memory type to operate on. Use +the ‘-v’ option on the command line or the part command from +terminal mode to display all the memory types supported by a particular +device. +Typically, a device’s memory configuration at least contains +the memory types +flash +and +eeprom. +All memory types currently known are: +

+
calibration
+

One or more bytes of RC oscillator calibration data. +

+
eeprom
+

The EEPROM of the device. +

+
efuse
+

The extended fuse byte. +

+
flash
+

The flash ROM of the device. +

+
fuse
+

The fuse byte in devices that have only a single fuse byte. +

+
hfuse
+

The high fuse byte. +

+
lfuse
+

The low fuse byte. +

+
lock
+

The lock byte. +

+
signature
+

The three device signature bytes (device ID). +

+
fuseN
+

The fuse bytes of ATxmega devices, N is an integer number +for each fuse supported by the device. +

+
application
+

The application flash area of ATxmega devices. +

+
apptable
+

The application table flash area of ATxmega devices. +

+
boot
+

The boot flash area of ATxmega devices. +

+
prodsig
+

The production signature (calibration) area of ATxmega devices. +

+
usersig
+

The user signature area of ATxmega devices. +

+
+ +

The op field specifies what operation to perform: +

+
+
r
+

read the specified device memory and write to the specified file +

+
+
w
+

read the specified file and write it to the specified device memory +

+
+
v
+

read the specified device memory and the specified file and perform a verify operation +

+
+
+ +

The filename field indicates the name of the file to read or +write. The format field is optional and contains the format of +the file to read or write. Possible values are: +

+
+
i
+

Intel Hex +

+
+
s
+

Motorola S-record +

+
+
r
+

raw binary; little-endian byte order, in the case of the flash ROM data +

+
+
e
+

ELF (Executable and Linkable Format), the final output file from the +linker; currently only accepted as an input file +

+
+
m
+

immediate mode; actual byte values specified on the command line, +separated by commas or spaces in place of the filename field of +the ‘-U’ option. This is useful +for programming fuse bytes without having to create a single-byte file +or enter terminal mode. If the number specified begins with 0x, +it is treated as a hex value. If the number otherwise begins with a +leading zero (0) it is treated as octal. Otherwise, the value is +treated as decimal. +

+
+
a
+

auto detect; valid for input only, and only if the input is not provided +at stdin. +

+
+
d
+

decimal; this and the following formats are only valid on output. +They generate one line of output for the respective memory section, +forming a comma-separated list of the values. +This can be particularly useful for subsequent processing, like for +fuse bit settings. +

+
+
h
+

hexadecimal; each value will get the string 0x prepended. +

+
+
o
+

octal; each value will get a 0 +prepended unless it is less than 8 in which case it gets no prefix. +

+
+
b
+

binary; each value will get the string 0b prepended. +

+
+
+ +

The default is to use auto detection for input files, and raw binary +format for output files. +

+

Note that if filename contains a colon, the format field is +no longer optional since the filename part following the colon would +otherwise be misinterpreted as format. +

+

When reading any kind of flash memory area (including the various sub-areas +in Xmega devices), the resulting output file will be truncated to not contain +trailing 0xFF bytes which indicate unprogrammed (erased) memory. +Thus, if the entire memory is unprogrammed, this will result in an output +file that has no contents at all. +

+

As an abbreviation, the form -U filename +is equivalent to specifying +-U flash:w:filename:a. +This will only work if filename does not have a colon in it. +

+
+
-v
+

Enable verbose output. +More -v options increase verbosity level. +

+
+
-V
+

Disable automatic verify check when uploading data. +

+
+
-x extended_param
+

Pass extended_param to the chosen programmer implementation as +an extended parameter. The interpretation of the extended parameter +depends on the programmer itself. See below for a list of programmers +accepting extended parameters. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_4.html b/docs/avrdude_4.html new file mode 100644 index 00000000..d76b9872 --- /dev/null +++ b/docs/avrdude_4.html @@ -0,0 +1,346 @@ + + + + +AVRDUDE: 2.2 Programmers accepting extended parameters + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

2.2 Programmers accepting extended parameters

+ +
+
JTAG ICE mkII/3
+
AVR Dragon
+
+

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

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

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

+
+ +
+
AVR910
+
+

The AVR910 programmer type accepts the following extended parameter: +

+
‘devcode=VALUE’
+

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

+
‘no_blockmode’
+

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

+
+ +
+
Arduino
+
+

The Arduino programmer type accepts the following extended parameter: +

+
‘attemps=VALUE’
+

Overide the default number of connection retry attempt by using VALUE. +

+
+ +
+
BusPirate
+
+

The BusPirate programmer type accepts the following extended parameters: +

+
‘reset=cs,aux,aux2’
+

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

+

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

+
+
‘spifreq=0..7’
+
+ + + + + + + + +
030 kHz (default)
1125 kHz
2250 kHz
31 MHz
42 MHz
52.6 MHz
64 MHz
78 MHz
+ +
+
‘rawfreq=0..3’
+

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

+ + + + + +
05 kHz
150 kHz
2100 kHz (Firmware v4.2+ only)
3400 kHz (v4.2+)
+ +

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

+
+
‘ascii’
+

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

+
+
‘nopagedwrite’
+

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

+
+
‘nopagedread’
+

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

+
+
‘cpufreq=125..4000’
+

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

+
+
‘serial_recv_timeout=1...’
+

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

+
+
+ +
+
Micronucleus bootloader
+
+

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

+
‘wait=timeout’
+

If the device is not connected, wait for the device to be plugged in. +The optional timeout specifies the connection time-out in seconds. +If no time-out is specified, AVRDUDE will wait indefinitely until the +device is plugged in. +

+
+ +
+
Teensy bootloader
+
+

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

+
‘wait=timeout’
+

If the device is not connected, wait for the device to be plugged in. +The optional timeout specifies the connection time-out in seconds. +If no time-out is specified, AVRDUDE will wait indefinitely until the +device is plugged in. +

+
+ +
+
Wiring
+
+

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

+
‘snooze=0..32767’
+

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

+
+ +
+
PICkit2
+

Connection to the PICkit2 programmer: +

+ + + + + + + +
(AVR)(PICkit2)
RSTVPP/MCLR (1)
VDDVDD Target (2) -- possibly optional if AVR self powered
GNDGND (3)
MISOPGD (4)
SCLKPDC (5)
OSIAUX (6)
+ +

Extended command line parameters: +

+
‘clockrate=rate’
+

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

+
‘timeout=usb-transaction-timeout’
+

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

+
+ +
+
USBasp
+

Extended parameters: +

+
‘section_config’
+

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

+
+ +
+
xbee
+

Extended parameters: +

+
‘xbeeresetpin=1..7’
+

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

+

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

+
+ +
+
serialupdi
+

Extended parameters: +

+
‘rtsdtr=low|high’
+

Forces RTS/DTR lines to assume low or high state during the whole +programming session. Some programmers might use this signal to +indicate UPDI programming state, but this is strictly hardware +specific. +

+

When not provided, driver/OS default value will be used. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_5.html b/docs/avrdude_5.html new file mode 100644 index 00000000..a01947d0 --- /dev/null +++ b/docs/avrdude_5.html @@ -0,0 +1,242 @@ + + + + +AVRDUDE: 2.3 Example Command Line Invocations + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

2.3 Example Command Line Invocations

+ +

Download the file diag.hex to the ATmega128 chip using the +STK500 programmer connected to the default serial port: +

+
+
+
% avrdude -p m128 -c stk500 -e -U flash:w:diag.hex 
+
+avrdude: AVR device initialized and ready to accept instructions
+
+Reading | ################################################## | 100% 0.03s
+
+avrdude: Device signature = 0x1e9702
+avrdude: erasing chip
+avrdude: done.
+avrdude: performing op: 1, flash, 0, diag.hex
+avrdude: reading input file "diag.hex"
+avrdude: input file diag.hex auto detected as Intel Hex
+avrdude: writing flash (19278 bytes):
+
+Writing | ################################################## | 100% 7.60s
+
+avrdude: 19456 bytes of flash written
+avrdude: verifying flash memory against diag.hex:
+avrdude: load data flash data from input file diag.hex:
+avrdude: input file diag.hex auto detected as Intel Hex
+avrdude: input file diag.hex contains 19278 bytes
+avrdude: reading on-chip flash data:
+
+Reading | ################################################## | 100% 6.83s
+
+avrdude: verifying ...
+avrdude: 19278 bytes of flash verified
+
+avrdude done.  Thank you.
+
+%
+
+
+ + +

Upload the flash memory from the ATmega128 connected to the STK500 +programmer and save it in raw binary format in the file named +c:/diag flash.bin: +

+
+
+
% avrdude -p m128 -c stk500 -U flash:r:"c:/diag flash.bin":r 
+
+avrdude: AVR device initialized and ready to accept instructions
+
+Reading | ################################################## | 100% 0.03s
+
+avrdude: Device signature = 0x1e9702
+avrdude: reading flash memory:
+
+Reading | ################################################## | 100% 46.10s
+
+avrdude: writing output file "c:/diag flash.bin"
+
+avrdude done.  Thank you.
+
+% 
+
+
+ + +

Using the default programmer, download the file diag.hex to +flash, eeprom.hex to EEPROM, and set the Extended, High, and Low +fuse bytes to 0xff, 0x89, and 0x2e respectively: +

+
+
+
+% avrdude -p m128 -u -U flash:w:diag.hex \
+>                 -U eeprom:w:eeprom.hex \
+>                 -U efuse:w:0xff:m      \
+>                 -U hfuse:w:0x89:m      \
+>                 -U lfuse:w:0x2e:m
+
+avrdude: AVR device initialized and ready to accept instructions
+
+Reading | ################################################## | 100% 0.03s
+
+avrdude: Device signature = 0x1e9702
+avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
+         To disable this feature, specify the -D option.
+avrdude: erasing chip
+avrdude: reading input file "diag.hex"
+avrdude: input file diag.hex auto detected as Intel Hex
+avrdude: writing flash (19278 bytes):
+
+Writing | ################################################## | 100% 7.60s
+
+avrdude: 19456 bytes of flash written
+avrdude: verifying flash memory against diag.hex:
+avrdude: load data flash data from input file diag.hex:
+avrdude: input file diag.hex auto detected as Intel Hex
+avrdude: input file diag.hex contains 19278 bytes
+avrdude: reading on-chip flash data:
+
+Reading | ################################################## | 100% 6.84s
+
+avrdude: verifying ...
+avrdude: 19278 bytes of flash verified
+
+[ ... other memory status output skipped for brevity ... ]
+
+avrdude done.  Thank you.
+
+% 
+
+
+ + +

Connect to the JTAG ICE mkII which serial number ends up in 1C37 via +USB, and enter terminal mode: +

+
+
+
+% avrdude -c jtag2 -p m649 -P usb:1c:37 -t
+
+avrdude: AVR device initialized and ready to accept instructions
+
+Reading | ################################################## | 100% 0.03s
+
+avrdude: Device signature = 0x1e9603
+
+[ ... terminal mode output skipped for brevity ... ]
+
+avrdude done.  Thank you.
+
+
+
+ +

List the serial numbers of all JTAG ICEs attached to USB. This is +done by specifying an invalid serial number, and increasing the +verbosity level. +

+
+
+
+% avrdude -c jtag2 -p m128 -P usb:xx -v
+[...]
+         Using Port            : usb:xxx
+         Using Programmer      : jtag2
+avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C6B
+avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C3A
+avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C30
+avrdude: usbdev_open(): did not find any (matching) USB device "usb:xxx"
+
+
+
+ + +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_6.html b/docs/avrdude_6.html new file mode 100644 index 00000000..0d315cc4 --- /dev/null +++ b/docs/avrdude_6.html @@ -0,0 +1,103 @@ + + + + +AVRDUDE: 3 Terminal Mode Operation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

3 Terminal Mode Operation

+ +

AVRDUDE has an interactive mode called terminal mode that is +enabled by the ‘-t’ option. This mode allows one to enter +interactive commands to display and modify the various device memories, +perform a chip erase, display the device signature bytes and part +parameters, and to send raw programming commands. Commands and +parameters may be abbreviated to their shortest unambiguous form. +Terminal mode also supports a command history so that previously entered +commands can be recalled and edited. +

+ + + +
3.1 Terminal Mode Commands   +
3.2 Terminal Mode Examples   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_7.html b/docs/avrdude_7.html new file mode 100644 index 00000000..dfe86057 --- /dev/null +++ b/docs/avrdude_7.html @@ -0,0 +1,208 @@ + + + + +AVRDUDE: 3.1 Terminal Mode Commands + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

3.1 Terminal Mode Commands

+ +

The following commands are implemented: +

+
+
dump memtype addr nbytes
+

Read nbytes from the specified memory area, and display them in +the usual hexadecimal and ASCII form. +

+
+
dump
+

Continue dumping the memory contents for another nbytes where the +previous dump command left off. +

+
+
write memtype addr byte1 … byteN
+

Manually program the respective memory cells, starting at address addr, +using the values byte1 through byteN. This feature is not +implemented for bank-addressed memories such as the flash memory of +ATMega devices. +

+
+
erase
+

Perform a chip erase. +

+
+
send b1 b2 b3 b4
+

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. +

+
+
sig
+

Display the device signature bytes. +

+
+
spi
+

Enter direct SPI mode. The pgmled pin acts as slave select. +Only supported on parallel bitbang programmers, and partially by USBtiny. +Slave Select must be externally held low for direct SPI when +using USBtinyISP, and send must be a multiple of four bytes. +

+
+
part
+

Display the current part settings and parameters. Includes chip +specific information including all memory types supported by the +device, read/write timing, etc. +

+
+
pgm
+

Return to programming mode (from direct SPI mode). +

+
+
verbose [level]
+

Change (when level is provided), or display the verbosity +level. +The initial verbosity level is controlled by the number of -v options +given on the command line. +

+
+
?
+
help
+

Give a short on-line summary of the available commands. +

+
+
quit
+

Leave terminal mode and thus AVRDUDE. +

+
+
+ +

In addition, the following commands are supported on the STK500 +and STK600 programmer: +

+
+
vtarg voltage
+

Set the target’s supply voltage to voltage Volts. +

+
+
varef [channel] voltage
+

Set the adjustable voltage source to voltage Volts. +This voltage is normally used to drive the target’s +Aref input on the STK500 and STK600. +The STK600 offers two reference voltages, which can be +selected by the optional parameter channel (either +0 or 1). +

+
+
fosc freq[M|k]
+

Set the master oscillator to freq Hz. +An optional trailing letter M +multiplies by 1E6, a trailing letter k by 1E3. +

+
+
fosc off
+

Turn the master oscillator off. +

+
+
sck period
+

STK500 and STK600 only: +Set the SCK clock period to period microseconds. +

+

JTAG ICE only: +Set the JTAG ICE bit clock period to period microseconds. +Note that unlike STK500 settings, this setting will be reverted to +its default value (approximately 1 microsecond) when the programming +software signs off from the JTAG ICE. +This parameter can also be used on the JTAG ICE mkII/3 to specify the +ISP clock period when operating the ICE in ISP mode. +

+
+
parms
+

STK500 and STK600 only: +Display the current voltage and master oscillator parameters. +

+

JTAG ICE only: +Display the current target supply voltage and JTAG bit clock rate/period. +

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

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_8.html b/docs/avrdude_8.html new file mode 100644 index 00000000..d3fba8c2 --- /dev/null +++ b/docs/avrdude_8.html @@ -0,0 +1,183 @@ + + + + +AVRDUDE: 3.2 Terminal Mode Examples + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

3.2 Terminal Mode Examples

+ +

Display part parameters, modify eeprom cells, perform a chip erase: +

+
+
+
% avrdude -p m128 -c stk500 -t
+
+avrdude: AVR device initialized and ready to accept instructions
+avrdude: Device signature = 0x1e9702
+avrdude: current erase-rewrite cycle count is 52 (if being tracked)
+avrdude> part
+>>> part 
+
+AVR Part              : ATMEGA128
+Chip Erase delay      : 9000 us
+PAGEL                 : PD7
+BS2                   : PA0
+RESET disposition     : dedicated
+RETRY pulse           : SCK
+serial program mode   : yes
+parallel program mode : yes
+Memory Detail         :
+
+                            Page                       Polled
+  Memory Type Paged  Size   Size #Pages MinW  MaxW   ReadBack
+  ----------- ------ ------ ---- ------ ----- ----- ---------
+  eeprom      no       4096    8     0  9000  9000 0xff 0xff
+  flash       yes    131072  256   512  4500  9000 0xff 0x00
+  lfuse       no          1    0     0     0     0 0x00 0x00
+  hfuse       no          1    0     0     0     0 0x00 0x00
+  efuse       no          1    0     0     0     0 0x00 0x00
+  lock        no          1    0     0     0     0 0x00 0x00
+  calibration no          1    0     0     0     0 0x00 0x00
+  signature   no          3    0     0     0     0 0x00 0x00
+
+avrdude> dump eeprom 0 16
+>>> dump eeprom 0 16 
+0000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
+
+avrdude> write eeprom 0 1 2 3 4
+>>> write eeprom 0 1 2 3 4 
+
+avrdude> dump eeprom 0 16
+>>> dump eeprom 0 16 
+0000  01 02 03 04 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
+
+avrdude> erase
+>>> erase 
+avrdude: erasing chip
+avrdude> dump eeprom 0 16
+>>> dump eeprom 0 16 
+0000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
+
+avrdude> 
+
+
+ + +

Program the fuse bits of an ATmega128 (disable M103 compatibility, +enable high speed external crystal, enable brown-out detection, slowly +rising power). Note since we are working with fuse bits the -u (unsafe) +option is specified, which allows you to modify the fuse bits. First +display the factory defaults, then reprogram: +

+
+
+
% avrdude -p m128 -u -c stk500 -t
+
+avrdude: AVR device initialized and ready to accept instructions
+avrdude: Device signature = 0x1e9702
+avrdude: current erase-rewrite cycle count is 52 (if being tracked)
+avrdude> d efuse
+>>> d efuse 
+0000  fd                                                |.               |
+
+avrdude> d hfuse
+>>> d hfuse 
+0000  99                                                |.               |
+
+avrdude> d lfuse
+>>> d lfuse 
+0000  e1                                                |.               |
+
+avrdude> w efuse 0 0xff
+>>> w efuse 0 0xff 
+
+avrdude> w hfuse 0 0x89
+>>> w hfuse 0 0x89 
+
+avrdude> w lfuse 0 0x2f
+>>> w lfuse 0 0x2f 
+
+avrdude> 
+
+
+ + +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_9.html b/docs/avrdude_9.html new file mode 100644 index 00000000..52f4f7a9 --- /dev/null +++ b/docs/avrdude_9.html @@ -0,0 +1,118 @@ + + + + +AVRDUDE: 4 Configuration File + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+ +

4 Configuration File

+ +

AVRDUDE reads a configuration file upon startup which describes all of +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. +

+

AVRDUDE first looks for a system wide configuration file in a platform +dependent location. On Unix, this is usually +/usr/local/etc/avrdude.conf, while on Windows it is usually in the +same location as the executable file. The name of this file can be +changed using the ‘-C’ command line option. After the system wide +configuration file is parsed, AVRDUDE looks for a per-user configuration +file to augment or override the system wide defaults. On Unix, the +per-user file is .avrduderc within the user’s home directory. On +Windows, this file is the avrdude.rc file located in the same +directory as the executable. +

+ + + + + +
4.1 AVRDUDE Defaults   +
4.2 Programmer Definitions   +
4.3 Part Definitions   +
4.4 Other Notes   +
+ +
+ + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_abt.html b/docs/avrdude_abt.html new file mode 100644 index 00000000..a2679cb6 --- /dev/null +++ b/docs/avrdude_abt.html @@ -0,0 +1,176 @@ + + + + +AVRDUDE: About This Document + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

About This Document

+ +

+ This document was generated on March 3, 2022 using texi2html 5.0. +

+

+ The buttons in the navigation panels have the following meaning: +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Button Name Go to From 1.2.3 go to
[ << ] FastBackBeginning of this chapter or previous chapter1
[ < ] BackPrevious section in reading order1.2.2
[ Up ] UpUp section1.2
[ > ] ForwardNext section in reading order1.2.4
[ >> ] FastForwardNext chapter2
[Top] TopCover (top) of document  
[Contents] ContentsTable of contents  
[Index] IndexIndex  
[ ? ] AboutAbout (help)  
+ +

+ where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: +

+ + + +
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_toc.html b/docs/avrdude_toc.html new file mode 100644 index 00000000..b46cc80d --- /dev/null +++ b/docs/avrdude_toc.html @@ -0,0 +1,148 @@ + + + + +AVRDUDE: Table of Contents + + + + + + + + + + + + + + + + + + + + +
[Top][Contents][Index][ ? ]
+

Table of Contents

+ +
+ + +
+
+ + + + + +
[Top][Contents][Index][ ? ]
+

+ + This document was generated on March 3, 2022 using texi2html 5.0. + +
+ +

+ + From d62f309a00f1b003f10c068bc1c5ab157f80158d Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 00:18:04 +0100 Subject: [PATCH 02/25] Add symlink for index.html --- docs/index.html | 1 + 1 file changed, 1 insertion(+) create mode 120000 docs/index.html diff --git a/docs/index.html b/docs/index.html new file mode 120000 index 00000000..946880a3 --- /dev/null +++ b/docs/index.html @@ -0,0 +1 @@ +avrdude.html \ No newline at end of file From 00ea962abeba0424e0f62f67d348046c1c217a84 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 00:22:59 +0100 Subject: [PATCH 03/25] Add link to docs --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 5c0c05ff..e6484a05 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,10 @@ with the help of [various contributors](./AUTHORS). The latest version of AVRDUDE is always available here:\ +## Documentation + +Documentation is [here](https://dl8dtl.github.io/avrdude/). + ## Getting AVRDUDE for Windows To get AVRDUDE for Windows, install the latest version from the [Releases](http://download.savannah.gnu.org/releases/avrdude/) page. From 65618ed655c908c5d43552086e8bcf6dd2470686 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 21:38:17 +0100 Subject: [PATCH 04/25] Fix a one-bit error in the signature read command for ATmega165* --- NEWS | 1 + src/avrdude.conf.in | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 3ede3e9f..c3022765 100644 --- a/NEWS +++ b/NEWS @@ -72,6 +72,7 @@ Changes since version 6.4: - Rework HID support for Windows #881 - List of signing keys? #884 - Pickit4 UPDI is writing at offset 0x4000 into flash instead of 0x0000. #892 + - Signature read command for ATmega165* was wrong (no-id) * Pull requests: diff --git a/src/avrdude.conf.in b/src/avrdude.conf.in index b362154f..ba512efd 100644 --- a/src/avrdude.conf.in +++ b/src/avrdude.conf.in @@ -14437,7 +14437,7 @@ part memory "signature" size = 3; - read = "0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0", + read = "0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0", "x x x x x x a1 a0 o o o o o o o o"; ; From c746c9bc9eeeaf1585d3c144e61cd1d782c2c4f9 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 22:49:46 +0100 Subject: [PATCH 05/25] Fix a one-bit error in ATmega165* signature read command. --- NEWS | 1 + src/avrdude.conf.in | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 3ede3e9f..c3022765 100644 --- a/NEWS +++ b/NEWS @@ -72,6 +72,7 @@ Changes since version 6.4: - Rework HID support for Windows #881 - List of signing keys? #884 - Pickit4 UPDI is writing at offset 0x4000 into flash instead of 0x0000. #892 + - Signature read command for ATmega165* was wrong (no-id) * Pull requests: diff --git a/src/avrdude.conf.in b/src/avrdude.conf.in index b362154f..ba512efd 100644 --- a/src/avrdude.conf.in +++ b/src/avrdude.conf.in @@ -14437,7 +14437,7 @@ part memory "signature" size = 3; - read = "0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0", + read = "0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0", "x x x x x x a1 a0 o o o o o o o o"; ; From da315d73239998afe11bb0b8d5aace06124244c8 Mon Sep 17 00:00:00 2001 From: MCUdude Date: Mon, 28 Feb 2022 19:46:47 +0100 Subject: [PATCH 06/25] Support both userrow and usersig names --- src/avrdude.conf.in | 12 ++++++------ src/jtag3.c | 29 ++++++++++++++++++----------- src/jtagmkII.c | 34 ++++++++++++++++++++-------------- src/stk500v2.c | 15 ++++++++++----- 4 files changed, 54 insertions(+), 36 deletions(-) diff --git a/src/avrdude.conf.in b/src/avrdude.conf.in index ba512efd..6366de5c 100644 --- a/src/avrdude.conf.in +++ b/src/avrdude.conf.in @@ -16748,15 +16748,15 @@ part parent ".avr8x" desc = "AVR8X tiny family common values"; family_id = "tinyAVR"; - memory "usersig" + memory "userrow" size = 0x20; offset = 0x1300; page_size = 0x20; readsize = 0x100; ; - memory "userrow" - alias "usersig"; + memory "usersig" + alias "userrow"; ; ; @@ -16769,15 +16769,15 @@ part parent ".avr8x" desc = "AVR8X mega family common values"; family_id = "megaAVR"; - memory "usersig" + memory "userrow" size = 0x40; offset = 0x1300; page_size = 0x40; readsize = 0x100; ; - memory "userrow" - alias "usersig"; + memory "usersig" + alias "userrow"; ; ; diff --git a/src/jtag3.c b/src/jtag3.c index 5b341a1e..6d358dfa 100644 --- a/src/jtag3.c +++ b/src/jtag3.c @@ -1174,7 +1174,8 @@ static int jtag3_initialize(PROGRAMMER * pgm, AVRPART * p) u32_to_b4(xd.nvm_fuse_offset, m->offset & ~7); } else if (matches(m->desc, "lock")) { u32_to_b4(xd.nvm_lock_offset, m->offset); - } else if (strcmp(m->desc, "usersig") == 0) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { u32_to_b4(xd.nvm_user_sig_offset, m->offset); } else if (strcmp(m->desc, "prodsig") == 0) { u32_to_b4(xd.nvm_prod_sig_offset, m->offset); @@ -1225,7 +1226,8 @@ static int jtag3_initialize(PROGRAMMER * pgm, AVRPART * p) u16_to_b2(xd.eeprom_bytes, m->size); u16_to_b2(xd.eeprom_base, m->offset); } - else if (strcmp(m->desc, "usersig") == 0) + else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { u16_to_b2(xd.user_sig_bytes, m->size); u16_to_b2(xd.user_sig_base, m->offset); @@ -1686,9 +1688,10 @@ static int jtag3_page_erase(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, cmd[3] = XMEGA_ERASE_BOOT_PAGE; } else if (strcmp(m->desc, "eeprom") == 0) { cmd[3] = XMEGA_ERASE_EEPROM_PAGE; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[3] = XMEGA_ERASE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[3] = XMEGA_ERASE_BOOT_PAGE; } else { cmd[3] = XMEGA_ERASE_APP_PAGE; @@ -1760,9 +1763,10 @@ static int jtag3_paged_write(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, } cmd[3] = ( p->flags & AVRPART_HAS_PDI ) ? MTYPE_EEPROM_XMEGA : MTYPE_EEPROM_PAGE; PDATA(pgm)->eeprom_pageaddr = (unsigned long)-1L; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[3] = MTYPE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[3] = MTYPE_BOOT_FLASH; } else if ( p->flags & AVRPART_HAS_PDI || p->flags & AVRPART_HAS_UPDI ) { cmd[3] = MTYPE_FLASH; @@ -1849,11 +1853,12 @@ static int jtag3_paged_load(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, cmd[3] = ( p->flags & AVRPART_HAS_PDI || p->flags & AVRPART_HAS_UPDI ) ? MTYPE_EEPROM : MTYPE_EEPROM_PAGE; if (pgm->flag & PGM_FL_IS_DW) return -1; - } else if ( ( strcmp(m->desc, "prodsig") == 0 ) ) { + } else if (strcmp(m->desc, "prodsig") == 0) { cmd[3] = MTYPE_PRODSIG; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[3] = MTYPE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[3] = MTYPE_BOOT_FLASH; } else if ( p->flags & AVRPART_HAS_PDI ) { cmd[3] = MTYPE_FLASH; @@ -1965,7 +1970,8 @@ static int jtag3_read_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, cmd[3] = MTYPE_FUSE_BITS; if (!(p->flags & AVRPART_HAS_UPDI)) addr = mem->offset & 7; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { cmd[3] = MTYPE_USERSIG; } else if (strcmp(mem->desc, "prodsig") == 0) { cmd[3] = MTYPE_PRODSIG; @@ -2126,7 +2132,8 @@ static int jtag3_write_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, cmd[3] = MTYPE_FUSE_BITS; if (!(p->flags & AVRPART_HAS_UPDI)) addr = mem->offset & 7; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { cmd[3] = MTYPE_USERSIG; } else if (strcmp(mem->desc, "prodsig") == 0) { cmd[3] = MTYPE_PRODSIG; diff --git a/src/jtagmkII.c b/src/jtagmkII.c index eeab8e92..fc06301c 100644 --- a/src/jtagmkII.c +++ b/src/jtagmkII.c @@ -1056,7 +1056,8 @@ static void jtagmkII_set_xmega_params(PROGRAMMER * pgm, AVRPART * p) u32_to_b4(sendbuf.dd.nvm_fuse_offset, m->offset & ~7); } else if (strncmp(m->desc, "lock", 4) == 0) { u32_to_b4(sendbuf.dd.nvm_lock_offset, m->offset); - } else if (strcmp(m->desc, "usersig") == 0) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { u32_to_b4(sendbuf.dd.nvm_user_sig_offset, m->offset); } else if (strcmp(m->desc, "prodsig") == 0) { u32_to_b4(sendbuf.dd.nvm_prod_sig_offset, m->offset); @@ -1933,9 +1934,10 @@ static int jtagmkII_page_erase(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, cmd[1] = XMEGA_ERASE_BOOT_PAGE; } else if (strcmp(m->desc, "eeprom") == 0) { cmd[1] = XMEGA_ERASE_EEPROM_PAGE; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[1] = XMEGA_ERASE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[1] = XMEGA_ERASE_BOOT_PAGE; } else { cmd[1] = XMEGA_ERASE_APP_PAGE; @@ -2044,13 +2046,14 @@ static int jtagmkII_paged_write(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, free(cmd); return n_bytes; } - cmd[1] = ( p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI) ) ? MTYPE_EEPROM : MTYPE_EEPROM_PAGE; + cmd[1] = (p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI)) ? MTYPE_EEPROM : MTYPE_EEPROM_PAGE; PDATA(pgm)->eeprom_pageaddr = (unsigned long)-1L; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[1] = MTYPE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[1] = MTYPE_BOOT_FLASH; - } else if ( p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI) ) { + } else if (p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI)) { cmd[1] = MTYPE_FLASH; } else { cmd[1] = MTYPE_SPM; @@ -2156,16 +2159,17 @@ static int jtagmkII_paged_load(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, /* dynamically decide between flash/boot memtype */ dynamic_memtype = 1; } else if (strcmp(m->desc, "eeprom") == 0) { - cmd[1] = ( p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI) ) ? MTYPE_EEPROM : MTYPE_EEPROM_PAGE; + cmd[1] = (p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI)) ? MTYPE_EEPROM : MTYPE_EEPROM_PAGE; if (pgm->flag & PGM_FL_IS_DW) return -1; - } else if ( ( strcmp(m->desc, "prodsig") == 0 ) ) { + } else if (strcmp(m->desc, "prodsig") == 0) { cmd[1] = MTYPE_PRODSIG; - } else if ( ( strcmp(m->desc, "usersig") == 0 ) ) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { cmd[1] = MTYPE_USERSIG; - } else if ( ( strcmp(m->desc, "boot") == 0 ) ) { + } else if (strcmp(m->desc, "boot") == 0) { cmd[1] = MTYPE_BOOT_FLASH; - } else if ( p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI) ) { + } else if (p->flags & (AVRPART_HAS_PDI | AVRPART_HAS_UPDI)) { cmd[1] = MTYPE_FLASH; } else { cmd[1] = MTYPE_SPM; @@ -2291,7 +2295,8 @@ static int jtagmkII_read_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, unsupp = 1; } else if (strncmp(mem->desc, "fuse", strlen("fuse")) == 0) { cmd[1] = MTYPE_FUSE_BITS; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { cmd[1] = MTYPE_USERSIG; } else if (strcmp(mem->desc, "prodsig") == 0) { cmd[1] = MTYPE_PRODSIG; @@ -2460,7 +2465,8 @@ static int jtagmkII_write_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, unsupp = 1; } else if (strncmp(mem->desc, "fuse", strlen("fuse")) == 0) { cmd[1] = MTYPE_FUSE_BITS; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { cmd[1] = MTYPE_USERSIG; } else if (strcmp(mem->desc, "prodsig") == 0) { cmd[1] = MTYPE_PRODSIG; diff --git a/src/stk500v2.c b/src/stk500v2.c index 92e59516..523d6539 100644 --- a/src/stk500v2.c +++ b/src/stk500v2.c @@ -3869,7 +3869,8 @@ static int stk600_xprog_write_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, * fuses. */ need_erase = 1; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { memcode = XPRG_MEM_TYPE_USERSIG; } else { avrdude_message(MSG_INFO, "%s: stk600_xprog_write_byte(): unknown memory \"%s\"\n", @@ -3944,7 +3945,8 @@ static int stk600_xprog_read_byte(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, } else if (strcmp(mem->desc, "calibration") == 0 || strcmp(mem->desc, "prodsig") == 0) { b[1] = XPRG_MEM_TYPE_FACTORY_CALIBRATION; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { b[1] = XPRG_MEM_TYPE_USERSIG; } else { avrdude_message(MSG_INFO, "%s: stk600_xprog_read_byte(): unknown memory \"%s\"\n", @@ -4019,7 +4021,8 @@ static int stk600_xprog_paged_load(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, } else if (strcmp(mem->desc, "calibration") == 0 || strcmp(mem->desc, "prodsig") == 0) { memtype = XPRG_MEM_TYPE_FACTORY_CALIBRATION; - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { memtype = XPRG_MEM_TYPE_USERSIG; } else { avrdude_message(MSG_INFO, "%s: stk600_xprog_paged_load(): unknown paged memory \"%s\"\n", @@ -4132,7 +4135,8 @@ static int stk600_xprog_paged_write(PROGRAMMER * pgm, AVRPART * p, AVRMEM * mem, } else if (strcmp(mem->desc, "calibration") == 0) { memtype = XPRG_MEM_TYPE_FACTORY_CALIBRATION; writemode = (1 << XPRG_MEM_WRITE_WRITE); - } else if (strcmp(mem->desc, "usersig") == 0) { + } else if (strcmp(mem->desc, "usersig") == 0 || + strcmp(mem->desc, "userrow") == 0) { memtype = XPRG_MEM_TYPE_USERSIG; writemode = (1 << XPRG_MEM_WRITE_WRITE); } else { @@ -4290,7 +4294,8 @@ static int stk600_xprog_page_erase(PROGRAMMER * pgm, AVRPART * p, AVRMEM * m, b[1] = XPRG_ERASE_BOOT_PAGE; } else if (strcmp(m->desc, "eeprom") == 0) { b[1] = XPRG_ERASE_EEPROM_PAGE; - } else if (strcmp(m->desc, "usersig") == 0) { + } else if (strcmp(m->desc, "usersig") == 0 || + strcmp(m->desc, "userrow") == 0) { b[1] = XPRG_ERASE_USERSIG; } else { avrdude_message(MSG_INFO, "%s: stk600_xprog_page_erase(): unknown paged memory \"%s\"\n", From 1299d6b8bd880a387fab7fa69fb25dff168a4db4 Mon Sep 17 00:00:00 2001 From: MCUdude Date: Wed, 2 Mar 2022 20:09:59 +0100 Subject: [PATCH 07/25] Fix terminal write bug Wouldn't write data properly after an integer >= 2 bytes was written --- src/term.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/term.c b/src/term.c index 7051503a..281a1f70 100644 --- a/src/term.c +++ b/src/term.c @@ -410,7 +410,7 @@ static int cmd_write(PROGRAMMER * pgm, struct avrpart * p, }; } data = {.bytes_grown = 0, .size = 0, .is_float = false, .ll = 0, .is_signed = false}; - for (i = start_offset; i < len + start_offset - data.bytes_grown; i++) { + for (i = start_offset; i < len + start_offset; i++) { data.is_float = false; data.size = 0; From 4e05a8fa41c6d5c10bcdb08d602d667758ca6efa Mon Sep 17 00:00:00 2001 From: MCUdude Date: Wed, 2 Mar 2022 20:24:51 +0100 Subject: [PATCH 08/25] Update description --- src/term.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/term.c b/src/term.c index 281a1f70..fc1b1069 100644 --- a/src/term.c +++ b/src/term.c @@ -334,7 +334,7 @@ static int cmd_write(PROGRAMMER * pgm, struct avrpart * p, "Usage: write \n" " write <...>\n\n" " Add a suffix to manually specify the size for each field:\n" - " H/h/S/s: 16-bit, L/l: 32-bit, LL/ll: 6-bit, F/f: 32-bit float\n"); + " HH/hh: 8-bit, H/h/S/s: 16-bit, L/l: 32-bit, LL/ll: 64-bit, F/f: 32-bit float\n"); return -1; } From dca5fc92bf70b4ffd4dbccaa1229a8a28ea66c78 Mon Sep 17 00:00:00 2001 From: MCUdude Date: Thu, 3 Mar 2022 19:37:42 +0100 Subject: [PATCH 09/25] Restructure "write mode" code --- src/term.c | 26 +++++++++----------------- 1 file changed, 9 insertions(+), 17 deletions(-) diff --git a/src/term.c b/src/term.c index fc1b1069..d98f0207 100644 --- a/src/term.c +++ b/src/term.c @@ -365,9 +365,16 @@ static int cmd_write(PROGRAMMER * pgm, struct avrpart * p, return -1; } - // Figure out how many bytes there is to write to memory + uint8_t * buf = malloc(mem->size); + if (buf == NULL) { + avrdude_message(MSG_INFO, "%s (write): out of memory\n", progname); + return -1; + } + + // Find the first argument to write to flash and how many arguments to parse and write if (strcmp(argv[argc - 1], "...") == 0) { write_mode = WRITE_MODE_FILL; + start_offset = 4; len = strtoul(argv[3], &end_ptr, 0); if (*end_ptr || (end_ptr == argv[3])) { avrdude_message(MSG_INFO, "%s (write ...): can't parse address \"%s\"\n", @@ -376,23 +383,8 @@ static int cmd_write(PROGRAMMER * pgm, struct avrpart * p, } } else { write_mode = WRITE_MODE_STANDARD; - } - - uint8_t * buf = malloc(mem->size); - if (buf == NULL) { - avrdude_message(MSG_INFO, "%s (write): out of memory\n", progname); - return -1; - } - - if (write_mode == WRITE_MODE_STANDARD) { - start_offset = 3; // Argument number where data to write starts + start_offset = 3; len = argc - start_offset; - } else if (write_mode == WRITE_MODE_FILL) - start_offset = 4; - else { - avrdude_message(MSG_INFO, "%s (write): invalid write mode %d\n", - progname, write_mode); - return -1; } // Structure related to data that is being written to memory From 40e3aa17906144cc71f1481f6bde38e8acb26819 Mon Sep 17 00:00:00 2001 From: MCUdude Date: Mon, 28 Feb 2022 20:39:55 +0100 Subject: [PATCH 10/25] Incread default read size to 256 bytes --- src/term.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/term.c b/src/term.c index d98f0207..11e22918 100644 --- a/src/term.c +++ b/src/term.c @@ -250,7 +250,7 @@ static int cmd_dump(PROGRAMMER * pgm, struct avrpart * p, if (strncmp(prevmem, memtype, strlen(memtype)) != 0) { addr = 0; - len = 64; + len = 256; strncpy(prevmem, memtype, sizeof(prevmem)-1); prevmem[sizeof(prevmem)-1] = 0; } From 248b554e8d7bd584a47dc3cc326aa638edf687e4 Mon Sep 17 00:00:00 2001 From: MCUdude Date: Mon, 28 Feb 2022 22:40:17 +0100 Subject: [PATCH 11/25] Add support for read with ... "operator" This means that you can use ... to read the "rest" of the memory. $ read eeprom ... will dump the entire memory $ read eeorm 0x80 ... will dump the memory from address 0x80 to the end address --- src/term.c | 125 ++++++++++++++++++++++++++--------------------------- 1 file changed, 62 insertions(+), 63 deletions(-) diff --git a/src/term.c b/src/term.c index 11e22918..ba0cf5cf 100644 --- a/src/term.c +++ b/src/term.c @@ -149,12 +149,10 @@ static int nexttok(char * buf, char ** tok, char ** next) static int hexdump_line(char * buffer, unsigned char * p, int n, int pad) { char * hexdata = "0123456789abcdef"; - char * b; - int i, j; + char * b = buffer; + int32_t i = 0; + int32_t j = 0; - b = buffer; - - j = 0; for (i=0; i len) n = len; hexdump_line(dst1, p, n, 48); @@ -230,83 +225,88 @@ static int hexdump_buf(FILE * f, int startaddr, unsigned char * buf, int len) static int cmd_dump(PROGRAMMER * pgm, struct avrpart * p, int argc, char * argv[]) { - static char prevmem[128] = {0}; - char * e; - unsigned char * buf; - int maxsize; - unsigned long i; - static unsigned long addr=0; - static int len=64; - AVRMEM * mem; - char * memtype = NULL; - int rc; - - if (!((argc == 2) || (argc == 4))) { - avrdude_message(MSG_INFO, "Usage: dump [ ]\n"); - return -1; + if (argc < 2) { + avrdude_message(MSG_INFO, "Usage: %s [ ]\n" + " %s [ <...>]\n" + " %s <...>\n" + " %s \n", + argv[0], argv[0], argv[0], argv[0]); + return -1; } - memtype = argv[1]; - - if (strncmp(prevmem, memtype, strlen(memtype)) != 0) { - addr = 0; - len = 256; - strncpy(prevmem, memtype, sizeof(prevmem)-1); - prevmem[sizeof(prevmem)-1] = 0; - } - - mem = avr_locate_mem(p, memtype); + enum { read_size = 256 }; + static char prevmem[128] = {0x00}; + char * memtype = argv[1]; + AVRMEM * mem = avr_locate_mem(p, memtype); if (mem == NULL) { avrdude_message(MSG_INFO, "\"%s\" memory type not defined for part \"%s\"\n", memtype, p->desc); return -1; } + uint32_t maxsize = mem->size; + // Get start address if present + char * end_ptr; + static uint32_t addr = 0; if (argc == 4) { - addr = strtoul(argv[2], &e, 0); - if (*e || (e == argv[2])) { - avrdude_message(MSG_INFO, "%s (dump): can't parse address \"%s\"\n", - progname, argv[2]); + addr = strtoul(argv[2], &end_ptr, 0); + if (*end_ptr || (end_ptr == argv[2])) { + avrdude_message(MSG_INFO, "%s (%s): can't parse address \"%s\"\n", + progname, argv[0], argv[2]); return -1; - } - - len = strtol(argv[3], &e, 0); - if (*e || (e == argv[3])) { - avrdude_message(MSG_INFO, "%s (dump): can't parse length \"%s\"\n", - progname, argv[3]); + } else if (addr >= maxsize) { + avrdude_message(MSG_INFO, "%s (%s): address 0x%05lx is out of range for %s memory\n", + progname, argv[0], addr, mem->desc); return -1; } } - maxsize = mem->size; - - if (addr >= maxsize) { - if (argc == 2) { - /* wrap around */ + // Get no. bytes to read if present + static int32_t len = read_size; + if (argc >= 3) { + memset(prevmem, 0x00, sizeof(prevmem)); + if (strcmp(argv[argc - 1], "...") == 0) { + if (argc == 3) + addr = 0; + len = maxsize - addr; + } else if (argc == 4) { + len = strtol(argv[3], &end_ptr, 0); + if (*end_ptr || (end_ptr == argv[3])) { + avrdude_message(MSG_INFO, "%s (%s): can't parse length \"%s\"\n", + progname, argv[0], argv[3]); + return -1; + } + } else { + len = read_size; + } + } + // No address or length specified + else if (argc == 2) { + if (strncmp(prevmem, memtype, strlen(memtype)) != 0) { addr = 0; + len = read_size; + strncpy(prevmem, memtype, sizeof(prevmem) - 1); + prevmem[sizeof(prevmem) - 1] = 0; } - else { - avrdude_message(MSG_INFO, "%s (dump): address 0x%05lx is out of range for %s memory\n", - progname, addr, mem->desc); - return -1; - } + if (addr >= maxsize) + addr = 0; // Wrap around } - /* trim len if nessary to not read past the end of memory */ + // Trim len if nessary to not read past the end of memory if ((addr + len) > maxsize) len = maxsize - addr; - buf = malloc(len); + uint8_t * buf = malloc(len); if (buf == NULL) { avrdude_message(MSG_INFO, "%s (dump): out of memory\n", progname); return -1; } - for (i=0; iread_byte(pgm, p, mem, addr+i, &buf[i]); + for (uint32_t i = 0; i < len; i++) { + int32_t rc = pgm->read_byte(pgm, p, mem, addr + i, &buf[i]); if (rc != 0) { avrdude_message(MSG_INFO, "error reading %s address 0x%05lx of part %s\n", - mem->desc, addr+i, p->desc); + mem->desc, addr + i, p->desc); if (rc == -1) avrdude_message(MSG_INFO, "read operation not supported on memory type \"%s\"\n", mem->desc); @@ -315,7 +315,6 @@ static int cmd_dump(PROGRAMMER * pgm, struct avrpart * p, } hexdump_buf(stdout, addr, buf, len); - fprintf(stdout, "\n"); free(buf); From 631f671fe873d27fe64f2e8414de45a0290fbc88 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Sun, 13 Mar 2022 00:21:20 +0100 Subject: [PATCH 12/25] Mention PRs #893, #894, #896, bug #889 --- NEWS | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/NEWS b/NEWS index c3022765..81179c5e 100644 --- a/NEWS +++ b/NEWS @@ -73,6 +73,7 @@ Changes since version 6.4: - List of signing keys? #884 - Pickit4 UPDI is writing at offset 0x4000 into flash instead of 0x0000. #892 - Signature read command for ATmega165* was wrong (no-id) + - SerialUPDI programmer can't write to usersig/userrow in terminal mode #889 * Pull requests: @@ -145,6 +146,9 @@ Changes since version 6.4: - Avrdude terminal write improvements #880 - Add userrow and usersig aliases #888 - For UPDI devices do not add offset when accessing flash. #895 + - Support both userrow and usersig names #893 + - Fix ugly terminal write bug #896 + - Improve terminal read functionality #894 * Internals: From 67ab74cd6a1534e548b10f496cd24a62532c8d31 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Mon, 7 Mar 2022 22:52:14 +0100 Subject: [PATCH 13/25] Fix a one-bit error in ATmega165* signature read command. --- NEWS | 1 + 1 file changed, 1 insertion(+) diff --git a/NEWS b/NEWS index 81179c5e..5befbb8a 100644 --- a/NEWS +++ b/NEWS @@ -74,6 +74,7 @@ Changes since version 6.4: - Pickit4 UPDI is writing at offset 0x4000 into flash instead of 0x0000. #892 - Signature read command for ATmega165* was wrong (no-id) - SerialUPDI programmer can't write to usersig/userrow in terminal mode #889 + - Signature read command for ATmega165* was wrong (no-id) * Pull requests: From 7391e569b3a25206e81c46f7bd375eb63f3eb44f Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Sun, 13 Mar 2022 00:13:29 +0100 Subject: [PATCH 14/25] Bring the texinfo doc up to date * remove copyright years; they are not meaningful anyway * reflect the project move from Savannah to Github --- src/doc/avrdude.texi | 26 +++++++++++--------------- 1 file changed, 11 insertions(+), 15 deletions(-) diff --git a/src/doc/avrdude.texi b/src/doc/avrdude.texi index 0364a296..68769ec6 100644 --- a/src/doc/avrdude.texi +++ b/src/doc/avrdude.texi @@ -28,9 +28,7 @@ This file documents the avrdude program. For avrdude version @value{VERSION}, @value{UPDATED}. -Copyright @copyright{} 2003, 2005 Brian Dean - -Copyright @copyright{} 2006 - 2021 J@"org Wunsch +Copyright @copyright{} Brian Dean, J@"org Wunsch Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice @@ -66,11 +64,9 @@ the terms of the GNU Free Documentation License (FDL), version 1.3. @page Send comments on AVRDUDE to @w{@email{avrdude-dev@@nongnu.org}}. -Use @uref{http://savannah.nongnu.org/bugs/?group=avrdude} to report bugs. +Use @uref{https://github.com/avrdudes/avrdude/issues} to report bugs. -Copyright @copyright{} 2003,2005 Brian S. Dean - -Copyright @copyright{} 2006 - 2013 J@"org Wunsch +Copyright @copyright{} Brian S. Dean, J@"org Wunsch @sp 2 Permission is granted to make and distribute verbatim copies of @@ -104,11 +100,9 @@ For avrdude version @value{VERSION}, @value{UPDATED}. Send comments on AVRDUDE to @w{@email{avrdude-dev@@nongnu.org}}. -Use @uref{http://savannah.nongnu.org/bugs/?group=avrdude} to report bugs. +Use @uref{https://github.com/avrdudes/avrdude/issues} to report bugs. -Copyright @copyright{} 2003,2005 Brian S. Dean - -Copyright @copyright{} 2006 J@"org Wunsch +Copyright @copyright{} Brian S. Dean, J@"org Wunsch @end ifinfo @menu @@ -353,13 +347,15 @@ AVRDUDE when interest grew in a Windows port of the software so that the name did not conflict with AVRPROG.EXE which is the name of Atmel's Windows programming software. -The AVRDUDE source now resides in the public CVS repository on -savannah.gnu.org (@url{http://savannah.gnu.org/projects/avrdude/}), -where it continues to be enhanced and ported to other systems. In +For many years, the AVRDUDE source resided in public repositories on +savannah.nongnu.org, +where it continued to be enhanced and ported to other systems. In addition to FreeBSD, AVRDUDE now runs on Linux and Windows. The developers behind the porting effort primarily were Ted Roth, Eric Weddington, and Joerg Wunsch. +In 2022, the project moved to Github (@url{https://github.com/avrdudes/avrdude/}). + And in the spirit of many open source projects, this manual also draws on the work of others. The initial revision was composed of parts of the original Unix manual page written by Joerg Wunsch, the original web @@ -2446,7 +2442,7 @@ such as @option{--prefix} and @option{--datadir}. @noindent In general, please report any bugs encountered via @* -@url{http://savannah.nongnu.org/bugs/?group=avrdude}. +@url{https://github.com/avrdudes/avrdude/issues}. @itemize @bullet From 0e441013e9807e994a5fb0676377a0e8633c872c Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Sun, 13 Mar 2022 00:31:27 +0100 Subject: [PATCH 15/25] Update docs --- docs/avrdude.html | 12 +++++------- docs/avrdude_1.html | 12 +++++++----- docs/avrdude_10.html | 4 ++-- docs/avrdude_11.html | 4 ++-- docs/avrdude_12.html | 4 ++-- docs/avrdude_13.html | 4 ++-- docs/avrdude_14.html | 4 ++-- docs/avrdude_15.html | 4 ++-- docs/avrdude_16.html | 4 ++-- docs/avrdude_17.html | 4 ++-- docs/avrdude_18.html | 4 ++-- docs/avrdude_19.html | 4 ++-- docs/avrdude_2.html | 4 ++-- docs/avrdude_20.html | 4 ++-- docs/avrdude_21.html | 6 +++--- docs/avrdude_3.html | 4 ++-- docs/avrdude_4.html | 4 ++-- docs/avrdude_5.html | 4 ++-- docs/avrdude_6.html | 4 ++-- docs/avrdude_7.html | 4 ++-- docs/avrdude_8.html | 4 ++-- docs/avrdude_9.html | 4 ++-- docs/avrdude_abt.html | 6 +++--- docs/avrdude_toc.html | 4 ++-- 24 files changed, 58 insertions(+), 58 deletions(-) diff --git a/docs/avrdude.html b/docs/avrdude.html index 53e42783..6859b71f 100644 --- a/docs/avrdude.html +++ b/docs/avrdude.html @@ -1,6 +1,6 @@ - @@ -92,6 +109,7 @@ by the Free Software Foundation. [Index] [ ? ] +
@@ -103,11 +121,11 @@ by the Free Software Foundation. - - -
4 Configuration File  
5 Programmer Specific Information   +
5 Programmer Specific Information  
Appendix A Platform Dependent Information   +
Appendix A Platform Dependent Information  
Appendix B Troubleshooting   +
Appendix B Troubleshooting  
@@ -304,7 +322,7 @@ utility, but it also contains some performance improvements included in Spence Konde’s DxCore Arduino core (https://github.com/SpenceKonde/DxCore). In a nutshell, this programmer consists of simple USB->UART adapter, diode and couple of resistors. It uses serial connection to provide UPDI interface. -See section SerialUPDI programmer for more details and known issues. +See section SerialUPDI programmer for more details and known issues.

The jtag2updi programmer is supported, and can program AVRs with a UPDI interface. @@ -336,10 +354,18 @@ below for Teensy specific options. [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_1.html b/docs/avrdude_1.html index 0e592464..ee104d84 100644 --- a/docs/avrdude_1.html +++ b/docs/avrdude_1.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

1.1 History and Credits

@@ -99,10 +117,18 @@ Roth. [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_10.html b/docs/avrdude_10.html index 141b143c..e32942ed 100644 --- a/docs/avrdude_10.html +++ b/docs/avrdude_10.html @@ -1,6 +1,6 @@ - @@ -55,7 +72,7 @@ ul.no-bullet {list-style: none} [ < ] [ Up ] [ > ] -[ >> ] +[ >> ]       @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

4.1 AVRDUDE Defaults

@@ -93,16 +111,9 @@ option.
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_11.html b/docs/avrdude_11.html index 35ba4254..4ce8a7f8 100644 --- a/docs/avrdude_11.html +++ b/docs/avrdude_11.html @@ -1,6 +1,6 @@ - @@ -55,7 +72,7 @@ ul.no-bullet {list-style: none} [ < ] [ Up ] [ > ] -[ >> ] +[ >> ]       @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

4.2 Programmer Definitions

@@ -161,11 +179,19 @@ programmer. These values can be changed by new setting them for the new programm [ < ] [ Up ] [ > ] -[ >> ] +[ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_12.html b/docs/avrdude_12.html index b79fbe3e..b500b781 100644 --- a/docs/avrdude_12.html +++ b/docs/avrdude_12.html @@ -1,6 +1,6 @@ - @@ -54,8 +71,8 @@ ul.no-bullet {list-style: none} [ << ] [ < ] [ Up ] -[ > ] -[ >> ] +[ > ] +[ >> ]       @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

4.3 Part Definitions

@@ -164,20 +182,19 @@ ul.no-bullet {list-style: none} - -
4.3.1 Parent Part   +
4.3.1 Parent Part  
4.3.2 Instruction Format   +
4.3.2 Instruction Format  
- - - - - + + + + @@ -187,107 +204,9 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

4.3.1 Parent Part

- -

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. -

-
-
   part parent <id>                              # quoted string
-       id               = <id> ;                 # quoted string
-       <any set of other parameters from the list above>
-     ;
-
- -
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

4.3.2 Instruction Format

- -

Instruction formats are specified as a comma separated list of string -values containing information (bit specifiers) about each of the 32 bits -of the instruction. Bit specifiers may be one of the following formats: -

-
-
1
-

The bit is always set on input as well as output -

-
-
0
-

the bit is always clear on input as well as output -

-
-
x
-

the bit is ignored on input and output -

-
-
a
-

the bit is an address bit, the bit-number matches this bit specifier’s -position within the current instruction byte -

-
-
aN
-

the bit is the Nth address bit, bit-number = N, i.e., a12 -is address bit 12 on input, a0 is address bit 0. -

-
-
i
-

the bit is an input data bit -

-
-
o
-

the bit is an output data bit -

-
-
- -

Each instruction must be composed of 32 bit specifiers. The instruction -specification closely follows the instruction data provided in Atmel’s -data sheets for their parts. For example, the EEPROM read and write -instruction for an AT90S2313 AVR part could be encoded as: -

-
-
-read  = "1  0  1  0   0  0  0  0   x x x x  x x x x",
-        "x a6 a5 a4  a3 a2 a1 a0   o o o o  o o o o";
-
-write = "1  1  0  0   0  0  0  0   x x x x  x x x x",
-        "x a6 a5 a4  a3 a2 a1 a0   i i i i  i i i i";
-
-
- - - -
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_13.html b/docs/avrdude_13.html index 1d4c75ea..e3232ce3 100644 --- a/docs/avrdude_13.html +++ b/docs/avrdude_13.html @@ -1,6 +1,6 @@ - -AVRDUDE: 4.4 Other Notes +AVRDUDE: 4.3.1 Parent Part - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - + + + + @@ -65,70 +82,27 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

4.4 Other Notes

+
+ +

4.3.1 Parent Part

- -
    -
  • -The devicecode parameter is the device code used by the STK500 -and is obtained from the software section (avr061.zip) of -Atmel’s AVR061 application note available from -http://www.atmel.com/dyn/resources/prod_documents/doc2525.pdf. - -
  • -Not all memory types will implement all instructions. - -
  • -AVR Fuse bits and Lock bits are implemented as a type of memory. - -
  • -Example memory types are: flash, eeprom, fuse, -lfuse (low fuse), hfuse (high fuse), efuse -(extended fuse), signature, calibration, lock. - -
  • -The memory type specified on the AVRDUDE command line must match one of -the memory types defined for the specified chip. - -
  • -The pwroff_after_write flag causes AVRDUDE to attempt to power -the device off and back on after an unsuccessful write to the affected -memory area if VCC programmer pins are defined. If VCC pins are not -defined for the programmer, a message indicating that the device needs a -power-cycle is printed out. This flag was added to work around a -problem with the at90s4433/2333’s; see the at90s4433 errata at: - -

    http://www.atmel.com/dyn/resources/prod_documents/doc1280.pdf +

    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.

    -
  • -The boot loader from application note AVR109 (and thus also the AVR -Butterfly) does not support writing of fuse bits. Writing lock bits -is supported, but is restricted to the boot lock bits (BLBxx). These -are restrictions imposed by the underlying SPM instruction that is used -to program the device from inside the boot loader. Note that programming -the boot lock bits can result in a “shoot-into-your-foot” scenario as -the only way to unprogram these bits is a chip erase, which will also -erase the boot loader code. - -

    The boot loader implements the “chip erase” function by erasing the -flash pages of the application section. -

    -

    Reading fuse and lock bits is fully supported. -

    -
+
+
   part parent <id>                              # quoted string
+       id               = <id> ;                 # quoted string
+       <any set of other parameters from the list above>
+     ;
+
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_14.html b/docs/avrdude_14.html index df085ed8..02b7cba8 100644 --- a/docs/avrdude_14.html +++ b/docs/avrdude_14.html @@ -1,6 +1,6 @@ - -AVRDUDE: 5 Programmer Specific Information +AVRDUDE: 4.3.2 Instruction Format - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - + + + + @@ -65,29 +82,83 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

5 Programmer Specific Information

+
+ +

4.3.2 Instruction Format

+ +

Instruction formats are specified as a comma separated list of string +values containing information (bit specifiers) about each of the 32 bits +of the instruction. Bit specifiers may be one of the following formats: +

+
+
1
+

The bit is always set on input as well as output +

+
+
0
+

the bit is always clear on input as well as output +

+
+
x
+

the bit is ignored on input and output +

+
+
a
+

the bit is an address bit, the bit-number matches this bit specifier’s +position within the current instruction byte +

+
+
aN
+

the bit is the Nth address bit, bit-number = N, i.e., a12 +is address bit 12 on input, a0 is address bit 0. +

+
+
i
+

the bit is an input data bit +

+
+
o
+

the bit is an output data bit +

+
+
+ +

Each instruction must be composed of 32 bit specifiers. The instruction +specification closely follows the instruction data provided in Atmel’s +data sheets for their parts. For example, the EEPROM read and write +instruction for an AT90S2313 AVR part could be encoded as: +

+
+
+read  = "1  0  1  0   0  0  0  0   x x x x  x x x x",
+        "x a6 a5 a4  a3 a2 a1 a0   o o o o  o o o o";
+
+write = "1  1  0  0   0  0  0  0   x x x x  x x x x",
+        "x a6 a5 a4  a3 a2 a1 a0   i i i i  i i i i";
+
+
+ - - - - -
5.1 Atmel STK600   -
5.2 Atmel DFU bootloader using FLIP version 1   -
5.3 SerialUPDI programmer   -
- - - - + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_15.html b/docs/avrdude_15.html index c4f0c0ac..5c6e9d49 100644 --- a/docs/avrdude_15.html +++ b/docs/avrdude_15.html @@ -1,6 +1,6 @@ - -AVRDUDE: 5.1 Atmel STK600 +AVRDUDE: 4.4 Other Notes - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,105 +82,79 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

5.1 Atmel STK600

+
+ +

4.4 Other Notes

-

The following devices are supported by the respective STK600 routing -and socket card: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Routing cardSocket cardDevices
STK600-ATTINY10ATtiny4 ATtiny5 ATtiny9 ATtiny10
STK600-RC008T-2STK600-DIPATtiny11 ATtiny12 ATtiny13 ATtiny13A ATtiny25 ATtiny45 ATtiny85
STK600-RC008T-7STK600-DIPATtiny15
STK600-RC014T-42STK600-SOICATtiny20
STK600-RC020T-1STK600-DIPATtiny2313 ATtiny2313A ATtiny4313
STK600-TinyX3UATtiny43U
STK600-RC014T-12STK600-DIPATtiny24 ATtiny44 ATtiny84 ATtiny24A ATtiny44A
STK600-RC020T-8STK600-DIPATtiny26 ATtiny261 ATtiny261A ATtiny461 ATtiny861 ATtiny861A
STK600-RC020T-43STK600-SOICATtiny261 ATtiny261A ATtiny461 ATtiny461A ATtiny861 ATtiny861A
STK600-RC020T-23STK600-SOICATtiny87 ATtiny167
STK600-RC028T-3STK600-DIPATtiny28
STK600-RC028M-6STK600-DIPATtiny48 ATtiny88 ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
QT600-ATTINY88-QT8ATtiny88
STK600-RC040M-4STK600-DIPATmega8515 ATmega162
STK600-RC044M-30STK600-TQFP44ATmega8515 ATmega162
STK600-RC040M-5STK600-DIPATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
STK600-RC044M-31STK600-TQFP44ATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
QT600-ATMEGA324-QM64ATmega324PA
STK600-RC032M-29STK600-TQFP32ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
STK600-RC064M-9STK600-TQFP64ATmega64 ATmega64A ATmega128 ATmega128A ATmega1281 ATmega2561 AT90CAN32 AT90CAN64 AT90CAN128
STK600-RC064M-10STK600-TQFP64ATmega165 ATmega165P ATmega169 ATmega169P ATmega169PA ATmega325 ATmega325P ATmega329 ATmega329P ATmega645 ATmega649 ATmega649P
STK600-RC100M-11STK600-TQFP100ATmega640 ATmega1280 ATmega2560
STK600-ATMEGA2560ATmega2560
STK600-RC100M-18STK600-TQFP100ATmega3250 ATmega3250P ATmega3290 ATmega3290P ATmega6450 ATmega6490
STK600-RC032U-20STK600-TQFP32AT90USB82 AT90USB162 ATmega8U2 ATmega16U2 ATmega32U2
STK600-RC044U-25STK600-TQFP44ATmega16U4 ATmega32U4
STK600-RC064U-17STK600-TQFP64ATmega32U6 AT90USB646 AT90USB1286 AT90USB647 AT90USB1287
STK600-RCPWM-22STK600-TQFP32ATmega32C1 ATmega64C1 ATmega16M1 ATmega32M1 ATmega64M1
STK600-RCPWM-19STK600-SOICAT90PWM2 AT90PWM3 AT90PWM2B AT90PWM3B AT90PWM216 AT90PWM316
STK600-RCPWM-26STK600-SOICAT90PWM81
STK600-RC044M-24STK600-TSSOP44ATmega16HVB ATmega32HVB
STK600-HVE2ATmega64HVE
STK600-ATMEGA128RFA1ATmega128RFA1
STK600-RC100X-13STK600-TQFP100ATxmega64A1 ATxmega128A1 ATxmega128A1_revD ATxmega128A1U
STK600-ATXMEGA1281A1ATxmega128A1
QT600-ATXMEGA128A1-QT16ATxmega128A1
STK600-RC064X-14STK600-TQFP64ATxmega64A3 ATxmega128A3 ATxmega256A3 ATxmega64D3 ATxmega128D3 ATxmega192D3 ATxmega256D3
STK600-RC064X-14STK600-MLF64ATxmega256A3B
STK600-RC044X-15STK600-TQFP44ATxmega32A4 ATxmega16A4 ATxmega16D4 ATxmega32D4
STK600-ATXMEGAT0ATxmega32T0
STK600-uC3-144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCUC3A144-33STK600-TQFP144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCuC3A100-28STK600-TQFP100AT32UC3A1512 AT32UC3A1256 AT32UC3A1128
STK600-RCuC3B0-21STK600-TQFP64-2AT32UC3B0256 AT32UC3B0512RevC AT32UC3B0512 AT32UC3B0128 AT32UC3B064 AT32UC3D1128
STK600-RCuC3B48-27STK600-TQFP48AT32UC3B1256 AT32UC3B164
STK600-RCUC3A144-32STK600-TQFP144AT32UC3A3512 AT32UC3A3256 AT32UC3A3128 AT32UC3A364 AT32UC3A3256S AT32UC3A3128S AT32UC3A364S
STK600-RCUC3C0-36STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-38STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-40STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3C0-37STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-39STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-41STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3L0-34STK600-TQFP48AT32UC3L064 AT32UC3L032 AT32UC3L016
QT600-AT32UC3L-QM64AT32UC3L064
-

Ensure the correct socket and routing card are mounted before -powering on the STK600. While the STK600 firmware ensures the socket -and routing card mounted match each other (using a table stored -internally in nonvolatile memory), it cannot handle the case where a -wrong routing card is used, e. g. the routing card -STK600-RC040M-5 (which is meant for 40-pin DIP AVRs that have -an ADC, with the power supply pins in the center of the package) was -used but an ATmega8515 inserted (which uses the “industry standard” -pinout with Vcc and GND at opposite corners). +

    +
  • +The devicecode parameter is the device code used by the STK500 +and is obtained from the software section (avr061.zip) of +Atmel’s AVR061 application note available from +http://www.atmel.com/dyn/resources/prod_documents/doc2525.pdf. + +
  • +Not all memory types will implement all instructions. + +
  • +AVR Fuse bits and Lock bits are implemented as a type of memory. + +
  • +Example memory types are: flash, eeprom, fuse, +lfuse (low fuse), hfuse (high fuse), efuse +(extended fuse), signature, calibration, lock. + +
  • +The memory type specified on the AVRDUDE command line must match one of +the memory types defined for the specified chip. + +
  • +The pwroff_after_write flag causes AVRDUDE to attempt to power +the device off and back on after an unsuccessful write to the affected +memory area if VCC programmer pins are defined. If VCC pins are not +defined for the programmer, a message indicating that the device needs a +power-cycle is printed out. This flag was added to work around a +problem with the at90s4433/2333’s; see the at90s4433 errata at: + +

    http://www.atmel.com/dyn/resources/prod_documents/doc1280.pdf

    -

    Note that for devices that use the routing card STK600-RC008T-2, -in order to use ISP mode, the jumper for AREF0 must be removed -as it would otherwise block one of the ISP signals. High-voltage -serial programming can be used even with that jumper installed. +

  • +The boot loader from application note AVR109 (and thus also the AVR +Butterfly) does not support writing of fuse bits. Writing lock bits +is supported, but is restricted to the boot lock bits (BLBxx). These +are restrictions imposed by the underlying SPM instruction that is used +to program the device from inside the boot loader. Note that programming +the boot lock bits can result in a “shoot-into-your-foot” scenario as +the only way to unprogram these bits is a chip erase, which will also +erase the boot loader code. + +

    The boot loader implements the “chip erase” function by erasing the +flash pages of the application section.

    -

    The ISP system of the STK600 contains a detection against shortcuts -and other wiring errors. AVRDUDE initiates a connection check before -trying to enter ISP programming mode, and display the result if the -target is not found ready to be ISP programmed. -

    -

    High-voltage programming requires the target voltage to be set to at -least 4.5 V in order to work. This can be done using -Terminal Mode, see Terminal Mode Operation. +

    Reading fuse and lock bits is fully supported.

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

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_16.html b/docs/avrdude_16.html index 2b3a353e..c6989b35 100644 --- a/docs/avrdude_16.html +++ b/docs/avrdude_16.html @@ -1,6 +1,6 @@ - -AVRDUDE: 5.2 Atmel DFU bootloader using FLIP version 1 +AVRDUDE: 5 Programmer Specific Information - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,42 +82,23 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

5.2 Atmel DFU bootloader using FLIP version 1

- -

Bootloaders using the FLIP protocol version 1 experience some very -specific behaviour. -

-

These bootloaders have no option to access memory areas other than -Flash and EEPROM. -

-

When the bootloader is started, it enters a security mode where -the only acceptable access is to query the device configuration -parameters (which are used for the signature on AVR devices). The -only way to leave this mode is a chip erase. As a chip erase -is normally implied by the ‘-U’ option when reprogramming the -flash, this peculiarity might not be very obvious immediately. -

-

Sometimes, a bootloader with security mode already disabled seems to -no longer respond with sensible configuration data, but only 0xFF for -all queries. As these queries are used to obtain the equivalent of a -signature, AVRDUDE can only continue in that situation by forcing the -signature check to be overridden with the ‘-F’ option. -

-

A chip erase might leave the EEPROM unerased, at least on some -versions of the bootloader. -

- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]
+ +

5 Programmer Specific Information

+ + + + + +
5.1 Atmel STK600   +
5.2 Atmel DFU bootloader using FLIP version 1   +
5.3 SerialUPDI programmer   +
+ +

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_17.html b/docs/avrdude_17.html index 5eebbc1b..4f5d9d71 100644 --- a/docs/avrdude_17.html +++ b/docs/avrdude_17.html @@ -1,6 +1,6 @@ - -AVRDUDE: 5.3 SerialUPDI programmer +AVRDUDE: 5.1 Atmel STK600 - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,114 +82,114 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

5.3 SerialUPDI programmer

+
+ +

5.1 Atmel STK600

-

SerialUPDI programmer can be used for programming UPDI-only devices -using very simple serial connection. -You can read more about the details here -https://github.com/SpenceKonde/AVR-Guidance/blob/master/UPDI/jtag2updi.md +

The following devices are supported by the respective STK600 routing +and socket card:

-

SerialUPDI programmer has been tested using FT232RL USB->UART interface -with the following connection layout (copied from Spence Kohde’s page linked -above): -

-
-
--------------------                                 To Target device
-                DTR|                                  __________________
-                Rx |--------------,------------------| UPDI---\/\/---------->
-  Tx---/\/\/\---Tx |-------|<|---'          .--------| Gnd    470 ohm 
-    resistor    Vcc|---------------------------------| Vcc
-        1k      CTS|                     .`          |__________________
-                Gnd|--------------------' 
---------------------
-
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Routing cardSocket cardDevices
STK600-ATTINY10ATtiny4 ATtiny5 ATtiny9 ATtiny10
STK600-RC008T-2STK600-DIPATtiny11 ATtiny12 ATtiny13 ATtiny13A ATtiny25 ATtiny45 ATtiny85
STK600-RC008T-7STK600-DIPATtiny15
STK600-RC014T-42STK600-SOICATtiny20
STK600-RC020T-1STK600-DIPATtiny2313 ATtiny2313A ATtiny4313
STK600-TinyX3UATtiny43U
STK600-RC014T-12STK600-DIPATtiny24 ATtiny44 ATtiny84 ATtiny24A ATtiny44A
STK600-RC020T-8STK600-DIPATtiny26 ATtiny261 ATtiny261A ATtiny461 ATtiny861 ATtiny861A
STK600-RC020T-43STK600-SOICATtiny261 ATtiny261A ATtiny461 ATtiny461A ATtiny861 ATtiny861A
STK600-RC020T-23STK600-SOICATtiny87 ATtiny167
STK600-RC028T-3STK600-DIPATtiny28
STK600-RC028M-6STK600-DIPATtiny48 ATtiny88 ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
QT600-ATTINY88-QT8ATtiny88
STK600-RC040M-4STK600-DIPATmega8515 ATmega162
STK600-RC044M-30STK600-TQFP44ATmega8515 ATmega162
STK600-RC040M-5STK600-DIPATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
STK600-RC044M-31STK600-TQFP44ATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
QT600-ATMEGA324-QM64ATmega324PA
STK600-RC032M-29STK600-TQFP32ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
STK600-RC064M-9STK600-TQFP64ATmega64 ATmega64A ATmega128 ATmega128A ATmega1281 ATmega2561 AT90CAN32 AT90CAN64 AT90CAN128
STK600-RC064M-10STK600-TQFP64ATmega165 ATmega165P ATmega169 ATmega169P ATmega169PA ATmega325 ATmega325P ATmega329 ATmega329P ATmega645 ATmega649 ATmega649P
STK600-RC100M-11STK600-TQFP100ATmega640 ATmega1280 ATmega2560
STK600-ATMEGA2560ATmega2560
STK600-RC100M-18STK600-TQFP100ATmega3250 ATmega3250P ATmega3290 ATmega3290P ATmega6450 ATmega6490
STK600-RC032U-20STK600-TQFP32AT90USB82 AT90USB162 ATmega8U2 ATmega16U2 ATmega32U2
STK600-RC044U-25STK600-TQFP44ATmega16U4 ATmega32U4
STK600-RC064U-17STK600-TQFP64ATmega32U6 AT90USB646 AT90USB1286 AT90USB647 AT90USB1287
STK600-RCPWM-22STK600-TQFP32ATmega32C1 ATmega64C1 ATmega16M1 ATmega32M1 ATmega64M1
STK600-RCPWM-19STK600-SOICAT90PWM2 AT90PWM3 AT90PWM2B AT90PWM3B AT90PWM216 AT90PWM316
STK600-RCPWM-26STK600-SOICAT90PWM81
STK600-RC044M-24STK600-TSSOP44ATmega16HVB ATmega32HVB
STK600-HVE2ATmega64HVE
STK600-ATMEGA128RFA1ATmega128RFA1
STK600-RC100X-13STK600-TQFP100ATxmega64A1 ATxmega128A1 ATxmega128A1_revD ATxmega128A1U
STK600-ATXMEGA1281A1ATxmega128A1
QT600-ATXMEGA128A1-QT16ATxmega128A1
STK600-RC064X-14STK600-TQFP64ATxmega64A3 ATxmega128A3 ATxmega256A3 ATxmega64D3 ATxmega128D3 ATxmega192D3 ATxmega256D3
STK600-RC064X-14STK600-MLF64ATxmega256A3B
STK600-RC044X-15STK600-TQFP44ATxmega32A4 ATxmega16A4 ATxmega16D4 ATxmega32D4
STK600-ATXMEGAT0ATxmega32T0
STK600-uC3-144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCUC3A144-33STK600-TQFP144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
STK600-RCuC3A100-28STK600-TQFP100AT32UC3A1512 AT32UC3A1256 AT32UC3A1128
STK600-RCuC3B0-21STK600-TQFP64-2AT32UC3B0256 AT32UC3B0512RevC AT32UC3B0512 AT32UC3B0128 AT32UC3B064 AT32UC3D1128
STK600-RCuC3B48-27STK600-TQFP48AT32UC3B1256 AT32UC3B164
STK600-RCUC3A144-32STK600-TQFP144AT32UC3A3512 AT32UC3A3256 AT32UC3A3128 AT32UC3A364 AT32UC3A3256S AT32UC3A3128S AT32UC3A364S
STK600-RCUC3C0-36STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-38STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-40STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3C0-37STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
STK600-RCUC3C1-39STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
STK600-RCUC3C2-41STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
STK600-RCUC3L0-34STK600-TQFP48AT32UC3L064 AT32UC3L032 AT32UC3L016
QT600-AT32UC3L-QM64AT32UC3L064
-

There are several limitations in current SerialUPDI/AVRDUDE integration, -listed below. +

Ensure the correct socket and routing card are mounted before +powering on the STK600. While the STK600 firmware ensures the socket +and routing card mounted match each other (using a table stored +internally in nonvolatile memory), it cannot handle the case where a +wrong routing card is used, e. g. the routing card +STK600-RC040M-5 (which is meant for 40-pin DIP AVRs that have +an ADC, with the power supply pins in the center of the package) was +used but an ATmega8515 inserted (which uses the “industry standard” +pinout with Vcc and GND at opposite corners).

-

At the end of each run there are fuse values being presented to the user. -For most of the UPDI-enabled devices these definitions (low fuse, high -fuse, extended fuse) have no meaning whatsoever, as they have been -simply replaced by array of fuses: fuse0..9. Therefore you can simply -ignore this particular line of AVRDUDE output. +

Note that for devices that use the routing card STK600-RC008T-2, +in order to use ISP mode, the jumper for AREF0 must be removed +as it would otherwise block one of the ISP signals. High-voltage +serial programming can be used even with that jumper installed.

-

Currently available devices support only UPDI NVM programming model 0 -and 2, but there is also experimental implementation of model 3 - not -yet tested. +

The ISP system of the STK600 contains a detection against shortcuts +and other wiring errors. AVRDUDE initiates a connection check before +trying to enter ISP programming mode, and display the result if the +target is not found ready to be ISP programmed.

-

One of the core AVRDUDE features is verification of the connection by -reading device signature prior to any operation, but this operation -is not possible on UPDI locked devices. Therefore, to be able to -connect to such a device, you have to provide ‘-F’ to override -this check. -

-

Please note: using ‘-F’ during write operation to locked device -will force chip erase. Use carefully. -

-

Another issue you might notice is slow performance of EEPROM writing -using SerialUPDI for AVR Dx devices. This can be addressed by changing -avrdude.conf section for this device - changing EEPROM page -size to 0x20 (instead of default 1), like so: -

-
-
#------------------------------------------------------------
-# AVR128DB28
-#------------------------------------------------------------
-
-part parent    ".avrdx"
-    id        = "avr128db28";
-    desc      = "AVR128DB28";
-    signature = 0x1E 0x97 0x0E;
-
-    memory "flash"
-        size      = 0x20000;
-        offset    = 0x800000;
-        page_size = 0x200;
-        readsize  = 0x100;
-    ;
-
-    memory "eeprom"
-        size      = 0x200;
-        offset    = 0x1400;
-        page_size = 0x1;
-        readsize  = 0x100;
-    ;
-;
-
- -

USERROW memory has not been defined for new devices except for -experimental addition for AVR128DB28. The point of USERROW is to -provide ability to write configuration details to already locked -device and currently SerialUPDI interface supports this feature, -but it hasn’t been tested on wide variety of chips. Treat this as -something experimental at this point. Please note: on locked devices -it’s not possible to read back USERROW contents when written, so -the automatic verification will most likely fail and to prevent -error messages, use ‘-V’. -

-

Please note that SerialUPDI interface is pretty new and some -issues are to be expected. In case you run into them, please -make sure to run the intended command with debug output enabled -(‘-v -v -v’) and provide this verbose output with your -bug report. You can also try to perform the same action using -pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) -utility with ‘-v debug’ and provide its output too. -You will notice that both outputs are pretty similar, and this -was implemented like that on purpose - it was supposed to make -analysis of UPDI protocol quirks easier. +

High-voltage programming requires the target voltage to be set to at +least 4.5 V in order to work. This can be done using +Terminal Mode, see Terminal Mode Operation.

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

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_18.html b/docs/avrdude_18.html index 9b97acf5..807ca22d 100644 --- a/docs/avrdude_18.html +++ b/docs/avrdude_18.html @@ -1,6 +1,6 @@ - -AVRDUDE: Appendix A Platform Dependent Information +AVRDUDE: 5.2 Atmel DFU bootloader using FLIP version 1 - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,27 +82,36 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

Appendix A Platform Dependent Information

- - - - -
A.1 Unix   -
A.2 Windows   -
-
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]
+ +

5.2 Atmel DFU bootloader using FLIP version 1

+ +

Bootloaders using the FLIP protocol version 1 experience some very +specific behaviour. +

+

These bootloaders have no option to access memory areas other than +Flash and EEPROM. +

+

When the bootloader is started, it enters a security mode where +the only acceptable access is to query the device configuration +parameters (which are used for the signature on AVR devices). The +only way to leave this mode is a chip erase. As a chip erase +is normally implied by the ‘-U’ option when reprogramming the +flash, this peculiarity might not be very obvious immediately. +

+

Sometimes, a bootloader with security mode already disabled seems to +no longer respond with sensible configuration data, but only 0xFF for +all queries. As these queries are used to obtain the equivalent of a +signature, AVRDUDE can only continue in that situation by forcing the +signature check to be overridden with the ‘-F’ option. +

+

A chip erase might leave the EEPROM unerased, at least on some +versions of the bootloader. +

+

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_19.html b/docs/avrdude_19.html index 47712fc3..f4c348f8 100644 --- a/docs/avrdude_19.html +++ b/docs/avrdude_19.html @@ -1,6 +1,6 @@ - -AVRDUDE: A.1 Unix +AVRDUDE: 5.3 SerialUPDI programmer - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,80 +82,111 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

A.1 Unix

- - - - - - -
A.1.1 Unix Installation   -
A.1.2 Unix Configuration Files   -
A.1.3 Unix Port Names   -
A.1.4 Unix Documentation   -
-
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.1.1 Unix Installation

+ +

5.3 SerialUPDI programmer

-

To build and install from the source tarball on Unix like systems: +

SerialUPDI programmer can be used for programming UPDI-only devices +using very simple serial connection. +You can read more about the details here +https://github.com/SpenceKonde/AVR-Guidance/blob/master/UPDI/jtag2updi.md +

+

SerialUPDI programmer has been tested using FT232RL USB->UART interface +with the following connection layout (copied from Spence Kohde’s page linked +above):

-
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure
-$ make
-$ su root -c 'make install'
+
--------------------                                 To Target device
+                DTR|                                  __________________
+                Rx |--------------,------------------| UPDI---\/\/---------->
+  Tx---/\/\/\---Tx |-------|<|---'          .--------| Gnd    470 ohm 
+    resistor    Vcc|---------------------------------| Vcc
+        1k      CTS|                     .`          |__________________
+                Gnd|--------------------' 
+--------------------
-

The default location of the install is into /usr/local so you -will need to be sure that /usr/local/bin is in your PATH -environment variable. +

There are several limitations in current SerialUPDI/AVRDUDE integration, +listed below.

-

If you do not have root access to your system, you can do the -following instead: +

At the end of each run there are fuse values being presented to the user. +For most of the UPDI-enabled devices these definitions (low fuse, high +fuse, extended fuse) have no meaning whatsoever, as they have been +simply replaced by array of fuses: fuse0..9. Therefore you can simply +ignore this particular line of AVRDUDE output. +

+

Currently available devices support only UPDI NVM programming model 0 +and 2, but there is also experimental implementation of model 3 - not +yet tested. +

+

One of the core AVRDUDE features is verification of the connection by +reading device signature prior to any operation, but this operation +is not possible on UPDI locked devices. Therefore, to be able to +connect to such a device, you have to provide ‘-F’ to override +this check. +

+

Please note: using ‘-F’ during write operation to locked device +will force chip erase. Use carefully. +

+

Another issue you might notice is slow performance of EEPROM writing +using SerialUPDI for AVR Dx devices. This can be addressed by changing +avrdude.conf section for this device - changing EEPROM page +size to 0x20 (instead of default 1), like so:

-
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure --prefix=$HOME/local
-$ make
-$ make install
+
#------------------------------------------------------------
+# AVR128DB28
+#------------------------------------------------------------
+
+part parent    ".avrdx"
+    id        = "avr128db28";
+    desc      = "AVR128DB28";
+    signature = 0x1E 0x97 0x0E;
+
+    memory "flash"
+        size      = 0x20000;
+        offset    = 0x800000;
+        page_size = 0x200;
+        readsize  = 0x100;
+    ;
+
+    memory "eeprom"
+        size      = 0x200;
+        offset    = 0x1400;
+        page_size = 0x1;
+        readsize  = 0x100;
+    ;
+;
- - - -
A.1.1.1 FreeBSD Installation   -
A.1.1.2 Linux Installation   -
- +

USERROW memory has not been defined for new devices except for +experimental addition for AVR128DB28. The point of USERROW is to +provide ability to write configuration details to already locked +device and currently SerialUPDI interface supports this feature, +but it hasn’t been tested on wide variety of chips. Treat this as +something experimental at this point. Please note: on locked devices +it’s not possible to read back USERROW contents when written, so +the automatic verification will most likely fail and to prevent +error messages, use ‘-V’. +

+

Please note that SerialUPDI interface is pretty new and some +issues are to be expected. In case you run into them, please +make sure to run the intended command with debug output enabled +(‘-v -v -v’) and provide this verbose output with your +bug report. You can also try to perform the same action using +pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) +utility with ‘-v debug’ and provide its output too. +You will notice that both outputs are pretty similar, and this +was implemented like that on purpose - it was supposed to make +analysis of UPDI protocol quirks easier. +

- - - - - - + + + + + @@ -148,223 +196,9 @@ $ make install
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

A.1.1.1 FreeBSD Installation

- -

AVRDUDE is installed via the FreeBSD Ports Tree as follows: -

-
-
% su - root
-# cd /usr/ports/devel/avrdude
-# make install
-
- -

If you wish to install from a pre-built package instead of the source, -you can use the following instead: -

-
-
% su - root
-# pkg_add -r avrdude
-
- -

Of course, you must be connected to the Internet for these methods to -work, since that is where the source as well as the pre-built package is -obtained. -

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

A.1.1.2 Linux Installation

- -

On rpm based Linux systems (such as RedHat, SUSE, Mandrake, etc.), you -can build and install the rpm binaries directly from the tarball: -

-
-
$ su - root
-# rpmbuild -tb avrdude-6.99-20211218.tar.gz
-# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-6.99-20211218-1.i386.rpm
-
- -

Note that the path to the resulting rpm package, differs from system -to system. The above example is specific to RedHat. -

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

A.1.2 Unix Configuration Files

- -

When AVRDUDE is build using the default ‘--prefix’ configure -option, the default configuration file for a Unix system is located at -/usr/local/etc/avrdude.conf. This can be overridden by using the -‘-C’ command line option. Additionally, the user’s home directory -is searched for a file named .avrduderc, and if found, is used to -augment the system default configuration file. -

- - - -
A.1.2.1 FreeBSD Configuration Files   -
A.1.2.2 Linux Configuration Files   -
- -
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.1.2.1 FreeBSD Configuration Files

- -

When AVRDUDE is installed using the FreeBSD ports system, the system -configuration file is always /usr/local/etc/avrdude.conf. -

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

A.1.2.2 Linux Configuration Files

- -

When AVRDUDE is installed using from an rpm package, the system -configuration file will be always be /etc/avrdude.conf. -

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

A.1.3 Unix Port Names

- -

The parallel and serial port device file names are system specific. -The following table lists the default names for a given system. -

- - - - - -
SystemDefault Parallel PortDefault Serial Port
FreeBSD/dev/ppi0/dev/cuad0
Linux/dev/parport0/dev/ttyS0
Solaris/dev/printers/0/dev/term/a
- -

On FreeBSD systems, AVRDUDE uses the ppi(4) interface for -accessing the parallel port and the sio(4) driver for serial port -access. -

-

On Linux systems, AVRDUDE uses the ppdev interface for -accessing the parallel port and the tty driver for serial port -access. -

-

On Solaris systems, AVRDUDE uses the ecpp(7D) driver for -accessing the parallel port and the asy(7D) driver for serial port -access. -

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

A.1.4 Unix Documentation

- -

AVRDUDE installs a manual page as well as info, HTML and PDF -documentation. The manual page is installed in -/usr/local/man/man1 area, while the HTML and PDF documentation -is installed in /usr/local/share/doc/avrdude directory. The -info manual is installed in /usr/local/info/avrdude.info. -

-

Note that these locations can be altered by various configure options -such as ‘--prefix’. -

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

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_2.html b/docs/avrdude_2.html index 7f9bf837..ac327979 100644 --- a/docs/avrdude_2.html +++ b/docs/avrdude_2.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

2 Command Line Options

@@ -79,16 +97,9 @@ ul.no-bullet {list-style: none}
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_20.html b/docs/avrdude_20.html index 0f704262..6404c70c 100644 --- a/docs/avrdude_20.html +++ b/docs/avrdude_20.html @@ -1,6 +1,6 @@ - -AVRDUDE: A.2 Windows +AVRDUDE: Appendix A Platform Dependent Information - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,311 +82,21 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

A.2 Windows

+
+ +

Appendix A Platform Dependent Information

- - - -
A.2.1 Installation   +
A.1 Unix  
A.2.2 Configuration Files   -
A.2.3 Port Names   -
A.2.4 Documentation   +
A.2 Windows  
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.2.1 Installation

- -

A Windows executable of avrdude is included in WinAVR which can be found at -http://sourceforge.net/projects/winavr. WinAVR is a suite of executable, -open source software development tools for the AVR for the Windows platform. -

-

There are two options to build avrdude from source under Windows. -The first one is to use Cygwin (http://www.cygwin.com/). -

-

To build and install from the source tarball for Windows (using Cygwin): -

-
-
$ set PREFIX=<your install directory path>
-$ export PREFIX
-$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure LDFLAGS="-static" --prefix=$PREFIX --datadir=$PREFIX 
---sysconfdir=$PREFIX/bin --enable-versioned-doc=no
-$ make
-$ make install
-
- -

Note that recent versions of Cygwin (starting with 1.7) removed the -MinGW support from the compiler that is needed in order to build a -native Win32 API binary that does not require to install the Cygwin -library cygwin1.dll at run-time. Either try using an older -compiler version that still supports MinGW builds, or use MinGW -(http://www.mingw.org/) directly. -

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

A.2.2 Configuration Files

- - - - -
A.2.2.1 Configuration file names   -
A.2.2.2 How AVRDUDE finds the configuration files.   -
- -
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.2.2.1 Configuration file names

- -

AVRDUDE on Windows looks for a system configuration file name of -avrdude.conf and looks for a user override configuration file of -avrdude.rc. -

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

A.2.2.2 How AVRDUDE finds the configuration files.

- -

AVRDUDE on Windows has a different way of searching for the system and -user configuration files. Below is the search method for locating the -configuration files: -

-
    -
  1. -Only for the system configuration file: -<directory from which application loaded>/../etc/avrdude.conf - -
  2. -The directory from which the application loaded. - -
  3. -The current directory. - -
  4. -The Windows system directory. On Windows NT, the name of this directory -is SYSTEM32. - -
  5. -Windows NT: The 16-bit Windows system directory. The name of this -directory is SYSTEM. - -
  6. -The Windows directory. - -
  7. -The directories that are listed in the PATH environment variable. - -
- - -
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.2.3 Port Names

- - - - -
A.2.3.1 Serial Ports   -
A.2.3.2 Parallel Ports   -
- -
- - - - - - - - - - - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
- -

A.2.3.1 Serial Ports

- -

When you select a serial port (i.e. when using an STK500) use the -Windows serial port device names such as: com1, com2, etc. -

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

A.2.3.2 Parallel Ports

- -

AVRDUDE will accept 3 Windows parallel port names: lpt1, lpt2, or -lpt3. Each of these names corresponds to a fixed parallel port base -address: -

-
-
lpt1
-

0x378 -

-
-
lpt2
-

0x278 -

-
-
lpt3
-

0x3BC -

-
-
- -

On your desktop PC, lpt1 will be the most common choice. If you are -using a laptop, you might have to use lpt3 instead of lpt1. Select the -name of the port the corresponds to the base address of the parallel -port that you want. -

-

If the parallel port can be accessed through a different -address, this address can be specified directly, using the common C -language notation (i. e., hexadecimal values are prefixed by 0x). -

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

A.2.4 Documentation

- -

AVRDUDE installs a manual page as well as info, HTML and PDF -documentation. The manual page is installed in -/usr/local/man/man1 area, while the HTML and PDF documentation -is installed in /usr/local/share/doc/avrdude directory. The -info manual is installed in /usr/local/info/avrdude.info. -

-

Note that these locations can be altered by various configure options -such as ‘--prefix’ and ‘--datadir’. -

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

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_21.html b/docs/avrdude_21.html index 85572e55..6711637b 100644 --- a/docs/avrdude_21.html +++ b/docs/avrdude_21.html @@ -1,6 +1,6 @@ - -AVRDUDE: Appendix B Troubleshooting +AVRDUDE: A.1 Unix - - + + @@ -41,6 +41,23 @@ span.nolinebreak {white-space:pre} span.roman {font-family:serif; font-weight:normal} span.sansserif {font-family:sans-serif; font-weight:normal} ul.no-bullet {list-style: none} +body { background-color: #ffd; } +h1 { text-shadow: .05em .05em #ccc; } +table { + border: 3px solid #ccf; + background-color: white; +} +div.example { + background-color: #dfd; + border: 3px solid #cfc; +} +samp { + color: blue; +} +code { + color: green; +} + --> @@ -49,13 +66,13 @@ ul.no-bullet {list-style: none} - + - - - - - + + + + + @@ -65,328 +82,25 @@ ul.no-bullet {list-style: none}
[ << ][ < ][ Up ][ > ][ >> ]
[ << ][ < ][ Up ][ > ][ >> ]       [Index] [ ? ]
- -

Appendix B Troubleshooting

+
+ +

A.1 Unix

-

In general, please report any bugs encountered via -
-https://github.com/avrdudes/avrdude/issues. -

- -
    -
  • -Problem: I’m using a serial programmer under Windows and get the following -error: - -

    avrdude: serial_open(): can't set attributes for device "com1", -

    -

    Solution: This problem seems to appear with certain versions of Cygwin. Specifying -"/dev/com1" instead of "com1" should help. -

    - -
  • -Problem: I’m using Linux and my AVR910 programmer is really slow. - -

    Solution (short): setserial port low_latency -

    -

    Solution (long): -There are two problems here. First, the system may wait some time before it -passes data from the serial port to the program. Under Linux the following -command works around this (you may need root privileges for this). -

    -

    setserial port low_latency -

    -

    Secondly, the serial interface chip may delay the interrupt for some time. -This behaviour can be changed by setting the FIFO-threshold to one. Under Linux this -can only be done by changing the kernel source in drivers/char/serial.c. -Search the file for UART_FCR_TRIGGER_8 and replace it with UART_FCR_TRIGGER_1. Note that overall performance might suffer if there -is high throughput on serial lines. Also note that you are modifying the kernel at -your own risk. -

    - -
  • -Problem: I’m not using Linux and my AVR910 programmer is really slow. - -

    Solutions: The reasons for this are the same as above. -If you know how to work around this on your OS, please let us know. -

    -
  • -Problem: Updating the flash ROM from terminal mode does not work with the -JTAG ICEs. - -

    Solution: None at this time. Currently, the JTAG ICE code cannot -write to the flash ROM one byte at a time. -

    -
  • -Problem: Page-mode programming the EEPROM (using the -U option) does -not erase EEPROM cells before writing, and thus cannot overwrite any -previous value != 0xff. - -

    Solution: None. This is an inherent feature of the way JTAG EEPROM -programming works, and is documented that way in the Atmel AVR -datasheets. -In order to successfully program the EEPROM that way, a prior chip -erase (with the EESAVE fuse unprogrammed) is required. -This also applies to the STK500 and STK600 in high-voltage programming mode. -

    -
  • -Problem: How do I turn off the DWEN fuse? - -

    Solution: If the DWEN (debugWire enable) fuse is activated, -the /RESET pin is not functional anymore, so normal ISP -communication cannot be established. -There are two options to deactivate that fuse again: high-voltage -programming, or getting the JTAG ICE mkII talk debugWire, and -prepare the target AVR to accept normal ISP communication again. -

    -

    The first option requires a programmer that is capable of high-voltage -programming (either serial or parallel, depending on the AVR device), -for example the STK500. In high-voltage programming mode, the -/RESET pin is activated initially using a 12 V pulse (thus the -name high voltage), so the target AVR can subsequently be -reprogrammed, and the DWEN fuse can be cleared. Typically, this -operation cannot be performed while the AVR is located in the target -circuit though. -

    -

    The second option requires a JTAG ICE mkII that can talk the debugWire -protocol. The ICE needs to be connected to the target using the -JTAG-to-ISP adapter, so the JTAG ICE mkII can be used as a debugWire -initiator as well as an ISP programmer. AVRDUDE will then be activated -using the jtag2isp programmer type. The initial ISP -communication attempt will fail, but AVRDUDE then tries to initiate a -debugWire reset. When successful, this will leave the target AVR in a -state where it can accept standard ISP communication. The ICE is then -signed off (which will make it signing off from the USB as well), so -AVRDUDE has to be called again afterwards. This time, standard ISP -communication can work, so the DWEN fuse can be cleared. -

    -

    The pin mapping for the JTAG-to-ISP adapter is: -

    - - - - - - - - +
    JTAG pinISP pin
    13
    26
    31
    42
    65
    94
    + + + +
    A.1.1 Unix Installation   +
    A.1.2 Unix Configuration Files   +
    A.1.3 Unix Port Names   +
    A.1.4 Unix Documentation   +
    -
  • -Problem: Multiple USBasp or USBtinyISP programmers connected simultaneously are not -found. - -

    Solution: The USBtinyISP code supports distinguishing multiple -programmers based on their bus:device connection tuple that describes -their place in the USB hierarchy on a specific host. This tuple can -be added to the -P usb option, similar to adding a serial number -on other USB-based programmers. -

    -

    The actual naming convention for the bus and device names is -operating-system dependent; AVRDUDE will print out what it found -on the bus when running it with (at least) one -v option. -By specifying a string that cannot match any existing device -(for example, -P usb:xxx), the scan will list all possible -candidate devices found on the bus. -

    -

    Examples: -

    -
    avrdude -c usbtiny -p atmega8 -P usb:003:025 (Linux)
-avrdude -c usbtiny -p atmega8 -P usb:/dev/usb:/dev/ugen1.3 (FreeBSD 8+)
-avrdude -c usbtiny -p atmega8 \
-  -P usb:bus-0:\\.\libusb0-0001--0x1781-0x0c9f (Windows)
-
    - -
  • -Problem: I cannot do … when the target is in debugWire mode. - -

    Solution: debugWire mode imposes several limitations. -

    -

    The debugWire protocol is Atmel’s proprietary one-wire (plus ground) -protocol to allow an in-circuit emulation of the smaller AVR devices, -using the /RESET line. -DebugWire mode is initiated by activating the DWEN -fuse, and then power-cycling the target. -While this mode is mainly intended for debugging/emulation, it -also offers limited programming capabilities. -Effectively, the only memory areas that can be read or programmed -in this mode are flash ROM and EEPROM. -It is also possible to read out the signature. -All other memory areas cannot be accessed. -There is no -chip erase -functionality in debugWire mode; instead, while reprogramming the -flash ROM, each flash ROM page is erased right before updating it. -This is done transparently by the JTAG ICE mkII (or AVR Dragon). -The only way back from debugWire mode is to initiate a special -sequence of commands to the JTAG ICE mkII (or AVR Dragon), so the -debugWire mode will be temporarily disabled, and the target can -be accessed using normal ISP programming. -This sequence is automatically initiated by using the JTAG ICE mkII -or AVR Dragon in ISP mode, when they detect that ISP mode cannot be -entered. -

    -
  • -Problem: I want to use my JTAG ICE mkII to program an -Xmega device through PDI. The documentation tells me to use the -XMEGA PDI adapter for JTAGICE mkII that is supposed to ship -with the kit, yet I don’t have it. - -

    Solution: Use the following pin mapping: -

    - - - - - - - - - - - - - -
    JTAGICETargetSquid cab-PDI
    mkII probepinsle colorsheader
    1 (TCK)Black
    2 (GND)GNDWhite6
    3 (TDO)Grey
    4 (VTref)VTrefPurple2
    5 (TMS)Blue
    6 (nSRST)PDI_CLKGreen5
    7 (N.C.)Yellow
    8 (nTRST)Orange
    9 (TDI)PDI_DATARed1
    10 (GND)Brown
    - -
  • -Problem: I want to use my AVR Dragon to program an -Xmega device through PDI. - -

    Solution: Use the 6 pin ISP header on the Dragon and the following pin mapping: -

    - - - - - - - - - -
    DragonTarget
    ISP Headerpins
    1 (MISO)PDI_DATA
    2 (VCC)VCC
    3 (SCK)
    4 (MOSI)
    5 (RESET)PDI_CLK / RST
    6 (GND)GND
    - -
  • -Problem: I want to use my AVRISP mkII to program an -ATtiny4/5/9/10 device through TPI. How to connect the pins? - -

    Solution: Use the following pin mapping: -

    - - - - - - - - - -
    AVRISPTargetATtiny
    connectorpinspin #
    1 (MISO)TPIDATA1
    2 (VTref)Vcc5
    3 (SCK)TPICLK3
    4 (MOSI)
    5 (RESET)/RESET6
    6 (GND)GND2
    - -
  • -Problem: I want to program an ATtiny4/5/9/10 device using a serial/parallel -bitbang programmer. How to connect the pins? - -

    Solution: Since TPI has only 1 pin for bi-directional data transfer, both -MISO and MOSI pins should be connected to the TPIDATA pin -on the ATtiny device. -However, a 1K resistor should be placed between the MOSI and TPIDATA. -The MISO pin connects to TPIDATA directly. -The SCK pin is connected to TPICLK. -

    -

    In addition, the Vcc, /RESET and GND pins should -be connected to their respective ports on the ATtiny device. -

    -
  • -Problem: How can I use a FTDI FT232R USB-to-Serial device for bitbang programming? - -

    Solution: When connecting the FT232 directly to the pins of the target Atmel device, -the polarity of the pins defined in the programmer definition should be -inverted by prefixing a tilde. For example, the dasa programmer would -look like this when connected via a FT232R device (notice the tildes in -front of pins 7, 4, 3 and 8): -

    -
    -
    programmer
-  id    = "dasa_ftdi";
-  desc  = "serial port banging, reset=rts sck=dtr mosi=txd miso=cts";
-  type  = serbb;
-  reset = ~7;
-  sck   = ~4;
-  mosi  = ~3;
-  miso  = ~8;
-;
-
    - -

    Note that this uses the FT232 device as a normal serial port, not using the -FTDI drivers in the special bitbang mode. -

    -
  • -Problem: My ATtiny4/5/9/10 reads out fine, but any attempt to program -it (through TPI) fails. Instead, the memory retains the old contents. - -

    Solution: Mind the limited programming supply voltage range of these -devices. -

    -

    In-circuit programming through TPI is only guaranteed by the datasheet -at Vcc = 5 V. -

    -
  • -Problem: My ATxmega…A1/A2/A3 cannot be programmed through PDI with -my AVR Dragon. Programming through a JTAG ICE mkII works though, as does -programming through JTAG. - -

    Solution: None by this time (2010 Q1). -

    -

    It is said that the AVR Dragon can only program devices from the A4 -Xmega sub-family. -

    -
  • -Problem: when programming with an AVRISPmkII or STK600, AVRDUDE hangs -when programming files of a certain size (e.g. 246 bytes). Other -(larger or smaller) sizes work though. - -

    Solution: This is a bug caused by an incorrect handling of zero-length -packets (ZLPs) in some versions of the libusb 0.1 API wrapper that ships -with libusb 1.x in certain Linux distributions. All Linux systems with -kernel versions < 2.6.31 and libusb >= 1.0.0 < 1.0.3 are reported to be -affected by this. -

    -

    See also: http://www.libusb.org/ticket/6 -

    -
  • -Problem: after flashing a firmware that reduces the target’s clock -speed (e.g. through the CLKPR register), further ISP connection -attempts fail. - -

    Solution: Even though ISP starts with pulling /RESET 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. -

    -

    As that slows down the entire subsequent ISP session, it might make -sense to just issue a chip erase using the slow ISP clock -(option -e), and then start a new session at higher speed. -Option -D might be used there, to prevent another unneeded -erase cycle. -

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

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_22.html b/docs/avrdude_22.html new file mode 100644 index 00000000..e30c6e96 --- /dev/null +++ b/docs/avrdude_22.html @@ -0,0 +1,130 @@ + + + + +AVRDUDE: A.1.1 Unix Installation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+

+ +

A.1.1 Unix Installation

+ +

To build and install from the source tarball on Unix like systems: +

+
+
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure
+$ make
+$ su root -c 'make install'
+
+ +

The default location of the install is into /usr/local so you +will need to be sure that /usr/local/bin is in your PATH +environment variable. +

+

If you do not have root access to your system, you can do the +following instead: +

+
+
$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure --prefix=$HOME/local
+$ make
+$ make install
+
+ + + + +
A.1.1.1 FreeBSD Installation   +
A.1.1.2 Linux Installation   +
+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_23.html b/docs/avrdude_23.html new file mode 100644 index 00000000..51117d9a --- /dev/null +++ b/docs/avrdude_23.html @@ -0,0 +1,118 @@ + + + + +AVRDUDE: A.1.1.1 FreeBSD Installation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.1.1 FreeBSD Installation

+ +

AVRDUDE is installed via the FreeBSD Ports Tree as follows: +

+
+
% su - root
+# cd /usr/ports/devel/avrdude
+# make install
+
+ +

If you wish to install from a pre-built package instead of the source, +you can use the following instead: +

+
+
% su - root
+# pkg_add -r avrdude
+
+ +

Of course, you must be connected to the Internet for these methods to +work, since that is where the source as well as the pre-built package is +obtained. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_24.html b/docs/avrdude_24.html new file mode 100644 index 00000000..ad7ad238 --- /dev/null +++ b/docs/avrdude_24.html @@ -0,0 +1,110 @@ + + + + +AVRDUDE: A.1.1.2 Linux Installation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.1.2 Linux Installation

+ +

On rpm based Linux systems (such as RedHat, SUSE, Mandrake, etc.), you +can build and install the rpm binaries directly from the tarball: +

+
+
$ su - root
+# rpmbuild -tb avrdude-6.99-20211218.tar.gz
+# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-6.99-20211218-1.i386.rpm
+
+ +

Note that the path to the resulting rpm package, differs from system +to system. The above example is specific to RedHat. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_25.html b/docs/avrdude_25.html new file mode 100644 index 00000000..88baa79d --- /dev/null +++ b/docs/avrdude_25.html @@ -0,0 +1,112 @@ + + + + +AVRDUDE: A.1.2 Unix Configuration Files + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.2 Unix Configuration Files

+ +

When AVRDUDE is build using the default ‘--prefix’ configure +option, the default configuration file for a Unix system is located at +/usr/local/etc/avrdude.conf. This can be overridden by using the +‘-C’ command line option. Additionally, the user’s home directory +is searched for a file named .avrduderc, and if found, is used to +augment the system default configuration file. +

+ + + +
A.1.2.1 FreeBSD Configuration Files   +
A.1.2.2 Linux Configuration Files   +
+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_26.html b/docs/avrdude_26.html new file mode 100644 index 00000000..25350c4d --- /dev/null +++ b/docs/avrdude_26.html @@ -0,0 +1,101 @@ + + + + +AVRDUDE: A.1.2.1 FreeBSD Configuration Files + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.2.1 FreeBSD Configuration Files

+ +

When AVRDUDE is installed using the FreeBSD ports system, the system +configuration file is always /usr/local/etc/avrdude.conf. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_27.html b/docs/avrdude_27.html new file mode 100644 index 00000000..a7a707bf --- /dev/null +++ b/docs/avrdude_27.html @@ -0,0 +1,101 @@ + + + + +AVRDUDE: A.1.2.2 Linux Configuration Files + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.2.2 Linux Configuration Files

+ +

When AVRDUDE is installed using from an rpm package, the system +configuration file will be always be /etc/avrdude.conf. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_28.html b/docs/avrdude_28.html new file mode 100644 index 00000000..afa30540 --- /dev/null +++ b/docs/avrdude_28.html @@ -0,0 +1,120 @@ + + + + +AVRDUDE: A.1.3 Unix Port Names + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.3 Unix Port Names

+ +

The parallel and serial port device file names are system specific. +The following table lists the default names for a given system. +

+ + + + + +
SystemDefault Parallel PortDefault Serial Port
FreeBSD/dev/ppi0/dev/cuad0
Linux/dev/parport0/dev/ttyS0
Solaris/dev/printers/0/dev/term/a
+ +

On FreeBSD systems, AVRDUDE uses the ppi(4) interface for +accessing the parallel port and the sio(4) driver for serial port +access. +

+

On Linux systems, AVRDUDE uses the ppdev interface for +accessing the parallel port and the tty driver for serial port +access. +

+

On Solaris systems, AVRDUDE uses the ecpp(7D) driver for +accessing the parallel port and the asy(7D) driver for serial port +access. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_29.html b/docs/avrdude_29.html new file mode 100644 index 00000000..d7dc927c --- /dev/null +++ b/docs/avrdude_29.html @@ -0,0 +1,107 @@ + + + + +AVRDUDE: A.1.4 Unix Documentation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.1.4 Unix Documentation

+ +

AVRDUDE installs a manual page as well as info, HTML and PDF +documentation. The manual page is installed in +/usr/local/man/man1 area, while the HTML and PDF documentation +is installed in /usr/local/share/doc/avrdude directory. The +info manual is installed in /usr/local/info/avrdude.info. +

+

Note that these locations can be altered by various configure options +such as ‘--prefix’. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_3.html b/docs/avrdude_3.html index 8733476f..8a05752d 100644 --- a/docs/avrdude_3.html +++ b/docs/avrdude_3.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

2.1 Option Descriptions

@@ -758,7 +776,7 @@ and Mac OS but not on Windows. For more information about AVR-Doper see serial numbers, multiple devices can be distinguished by their location in the USB hierarchy. See the respective -See section Troubleshooting entry for examples. +See section Troubleshooting entry for examples.

For the XBee programmer the target MCU is to be programmed wirelessly over a ZigBee mesh using the XBeeBoot bootloader. The ZigBee 64-bit @@ -991,10 +1009,18 @@ accepting extended parameters. [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_30.html b/docs/avrdude_30.html new file mode 100644 index 00000000..f148a03a --- /dev/null +++ b/docs/avrdude_30.html @@ -0,0 +1,109 @@ + + + + +AVRDUDE: A.2 Windows + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+

+ +

A.2 Windows

+ + + + + + +
A.2.1 Installation   +
A.2.2 Configuration Files   +
A.2.3 Port Names   +
A.2.4 Documentation   +
+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_31.html b/docs/avrdude_31.html new file mode 100644 index 00000000..4a1f623a --- /dev/null +++ b/docs/avrdude_31.html @@ -0,0 +1,127 @@ + + + + +AVRDUDE: A.2.1 Installation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.1 Installation

+ +

A Windows executable of avrdude is included in WinAVR which can be found at +http://sourceforge.net/projects/winavr. WinAVR is a suite of executable, +open source software development tools for the AVR for the Windows platform. +

+

There are two options to build avrdude from source under Windows. +The first one is to use Cygwin (http://www.cygwin.com/). +

+

To build and install from the source tarball for Windows (using Cygwin): +

+
+
$ set PREFIX=<your install directory path>
+$ export PREFIX
+$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
+$ cd avrdude-6.99-20211218
+$ ./configure LDFLAGS="-static" --prefix=$PREFIX --datadir=$PREFIX 
+--sysconfdir=$PREFIX/bin --enable-versioned-doc=no
+$ make
+$ make install
+
+ +

Note that recent versions of Cygwin (starting with 1.7) removed the +MinGW support from the compiler that is needed in order to build a +native Win32 API binary that does not require to install the Cygwin +library cygwin1.dll at run-time. Either try using an older +compiler version that still supports MinGW builds, or use MinGW +(http://www.mingw.org/) directly. +

+ + +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_32.html b/docs/avrdude_32.html new file mode 100644 index 00000000..6218dd68 --- /dev/null +++ b/docs/avrdude_32.html @@ -0,0 +1,105 @@ + + + + +AVRDUDE: A.2.2 Configuration Files + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.2 Configuration Files

+ + + + +
A.2.2.1 Configuration file names   +
A.2.2.2 How AVRDUDE finds the configuration files.   +
+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_33.html b/docs/avrdude_33.html new file mode 100644 index 00000000..5e33d98f --- /dev/null +++ b/docs/avrdude_33.html @@ -0,0 +1,102 @@ + + + + +AVRDUDE: A.2.2.1 Configuration file names + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.2.1 Configuration file names

+ +

AVRDUDE on Windows looks for a system configuration file name of +avrdude.conf and looks for a user override configuration file of +avrdude.rc. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_34.html b/docs/avrdude_34.html new file mode 100644 index 00000000..e0f26f4b --- /dev/null +++ b/docs/avrdude_34.html @@ -0,0 +1,130 @@ + + + + +AVRDUDE: A.2.2.2 How AVRDUDE finds the configuration files. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.2.2 How AVRDUDE finds the configuration files.

+ +

AVRDUDE on Windows has a different way of searching for the system and +user configuration files. Below is the search method for locating the +configuration files: +

+
    +
  1. +Only for the system configuration file: +<directory from which application loaded>/../etc/avrdude.conf + +
  2. +The directory from which the application loaded. + +
  3. +The current directory. + +
  4. +The Windows system directory. On Windows NT, the name of this directory +is SYSTEM32. + +
  5. +Windows NT: The 16-bit Windows system directory. The name of this +directory is SYSTEM. + +
  6. +The Windows directory. + +
  7. +The directories that are listed in the PATH environment variable. + +
+ + +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_35.html b/docs/avrdude_35.html new file mode 100644 index 00000000..abe209a8 --- /dev/null +++ b/docs/avrdude_35.html @@ -0,0 +1,105 @@ + + + + +AVRDUDE: A.2.3 Port Names + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.3 Port Names

+ + + + +
A.2.3.1 Serial Ports   +
A.2.3.2 Parallel Ports   +
+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_36.html b/docs/avrdude_36.html new file mode 100644 index 00000000..4202abcf --- /dev/null +++ b/docs/avrdude_36.html @@ -0,0 +1,101 @@ + + + + +AVRDUDE: A.2.3.1 Serial Ports + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.3.1 Serial Ports

+ +

When you select a serial port (i.e. when using an STK500) use the +Windows serial port device names such as: com1, com2, etc. +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_37.html b/docs/avrdude_37.html new file mode 100644 index 00000000..1e939eb2 --- /dev/null +++ b/docs/avrdude_37.html @@ -0,0 +1,126 @@ + + + + +AVRDUDE: A.2.3.2 Parallel Ports + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.3.2 Parallel Ports

+ +

AVRDUDE will accept 3 Windows parallel port names: lpt1, lpt2, or +lpt3. Each of these names corresponds to a fixed parallel port base +address: +

+
+
lpt1
+

0x378 +

+
+
lpt2
+

0x278 +

+
+
lpt3
+

0x3BC +

+
+
+ +

On your desktop PC, lpt1 will be the most common choice. If you are +using a laptop, you might have to use lpt3 instead of lpt1. Select the +name of the port the corresponds to the base address of the parallel +port that you want. +

+

If the parallel port can be accessed through a different +address, this address can be specified directly, using the common C +language notation (i. e., hexadecimal values are prefixed by 0x). +

+
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_38.html b/docs/avrdude_38.html new file mode 100644 index 00000000..151c4935 --- /dev/null +++ b/docs/avrdude_38.html @@ -0,0 +1,108 @@ + + + + +AVRDUDE: A.2.4 Documentation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

A.2.4 Documentation

+ +

AVRDUDE installs a manual page as well as info, HTML and PDF +documentation. The manual page is installed in +/usr/local/man/man1 area, while the HTML and PDF documentation +is installed in /usr/local/share/doc/avrdude directory. The +info manual is installed in /usr/local/info/avrdude.info. +

+

Note that these locations can be altered by various configure options +such as ‘--prefix’ and ‘--datadir’. +

+ +
+

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_39.html b/docs/avrdude_39.html new file mode 100644 index 00000000..496ccd43 --- /dev/null +++ b/docs/avrdude_39.html @@ -0,0 +1,421 @@ + + + + +AVRDUDE: Appendix B Troubleshooting + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
[ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
+
+ +

Appendix B Troubleshooting

+ +

In general, please report any bugs encountered via +
+https://github.com/avrdudes/avrdude/issues. +

+ +
    +
  • +Problem: I’m using a serial programmer under Windows and get the following +error: + +

    avrdude: serial_open(): can't set attributes for device "com1", +

    +

    Solution: This problem seems to appear with certain versions of Cygwin. Specifying +"/dev/com1" instead of "com1" should help. +

    + +
  • +Problem: I’m using Linux and my AVR910 programmer is really slow. + +

    Solution (short): setserial port low_latency +

    +

    Solution (long): +There are two problems here. First, the system may wait some time before it +passes data from the serial port to the program. Under Linux the following +command works around this (you may need root privileges for this). +

    +

    setserial port low_latency +

    +

    Secondly, the serial interface chip may delay the interrupt for some time. +This behaviour can be changed by setting the FIFO-threshold to one. Under Linux this +can only be done by changing the kernel source in drivers/char/serial.c. +Search the file for UART_FCR_TRIGGER_8 and replace it with UART_FCR_TRIGGER_1. Note that overall performance might suffer if there +is high throughput on serial lines. Also note that you are modifying the kernel at +your own risk. +

    + +
  • +Problem: I’m not using Linux and my AVR910 programmer is really slow. + +

    Solutions: The reasons for this are the same as above. +If you know how to work around this on your OS, please let us know. +

    +
  • +Problem: Updating the flash ROM from terminal mode does not work with the +JTAG ICEs. + +

    Solution: None at this time. Currently, the JTAG ICE code cannot +write to the flash ROM one byte at a time. +

    +
  • +Problem: Page-mode programming the EEPROM (using the -U option) does +not erase EEPROM cells before writing, and thus cannot overwrite any +previous value != 0xff. + +

    Solution: None. This is an inherent feature of the way JTAG EEPROM +programming works, and is documented that way in the Atmel AVR +datasheets. +In order to successfully program the EEPROM that way, a prior chip +erase (with the EESAVE fuse unprogrammed) is required. +This also applies to the STK500 and STK600 in high-voltage programming mode. +

    +
  • +Problem: How do I turn off the DWEN fuse? + +

    Solution: If the DWEN (debugWire enable) fuse is activated, +the /RESET pin is not functional anymore, so normal ISP +communication cannot be established. +There are two options to deactivate that fuse again: high-voltage +programming, or getting the JTAG ICE mkII talk debugWire, and +prepare the target AVR to accept normal ISP communication again. +

    +

    The first option requires a programmer that is capable of high-voltage +programming (either serial or parallel, depending on the AVR device), +for example the STK500. In high-voltage programming mode, the +/RESET pin is activated initially using a 12 V pulse (thus the +name high voltage), so the target AVR can subsequently be +reprogrammed, and the DWEN fuse can be cleared. Typically, this +operation cannot be performed while the AVR is located in the target +circuit though. +

    +

    The second option requires a JTAG ICE mkII that can talk the debugWire +protocol. The ICE needs to be connected to the target using the +JTAG-to-ISP adapter, so the JTAG ICE mkII can be used as a debugWire +initiator as well as an ISP programmer. AVRDUDE will then be activated +using the jtag2isp programmer type. The initial ISP +communication attempt will fail, but AVRDUDE then tries to initiate a +debugWire reset. When successful, this will leave the target AVR in a +state where it can accept standard ISP communication. The ICE is then +signed off (which will make it signing off from the USB as well), so +AVRDUDE has to be called again afterwards. This time, standard ISP +communication can work, so the DWEN fuse can be cleared. +

    +

    The pin mapping for the JTAG-to-ISP adapter is: +

    + + + + + + + + +
    JTAG pinISP pin
    13
    26
    31
    42
    65
    94
    + +
  • +Problem: Multiple USBasp or USBtinyISP programmers connected simultaneously are not +found. + +

    Solution: The USBtinyISP code supports distinguishing multiple +programmers based on their bus:device connection tuple that describes +their place in the USB hierarchy on a specific host. This tuple can +be added to the -P usb option, similar to adding a serial number +on other USB-based programmers. +

    +

    The actual naming convention for the bus and device names is +operating-system dependent; AVRDUDE will print out what it found +on the bus when running it with (at least) one -v option. +By specifying a string that cannot match any existing device +(for example, -P usb:xxx), the scan will list all possible +candidate devices found on the bus. +

    +

    Examples: +

    +
    avrdude -c usbtiny -p atmega8 -P usb:003:025 (Linux)
+avrdude -c usbtiny -p atmega8 -P usb:/dev/usb:/dev/ugen1.3 (FreeBSD 8+)
+avrdude -c usbtiny -p atmega8 \
+  -P usb:bus-0:\\.\libusb0-0001--0x1781-0x0c9f (Windows)
+
    + +
  • +Problem: I cannot do … when the target is in debugWire mode. + +

    Solution: debugWire mode imposes several limitations. +

    +

    The debugWire protocol is Atmel’s proprietary one-wire (plus ground) +protocol to allow an in-circuit emulation of the smaller AVR devices, +using the /RESET line. +DebugWire mode is initiated by activating the DWEN +fuse, and then power-cycling the target. +While this mode is mainly intended for debugging/emulation, it +also offers limited programming capabilities. +Effectively, the only memory areas that can be read or programmed +in this mode are flash ROM and EEPROM. +It is also possible to read out the signature. +All other memory areas cannot be accessed. +There is no +chip erase +functionality in debugWire mode; instead, while reprogramming the +flash ROM, each flash ROM page is erased right before updating it. +This is done transparently by the JTAG ICE mkII (or AVR Dragon). +The only way back from debugWire mode is to initiate a special +sequence of commands to the JTAG ICE mkII (or AVR Dragon), so the +debugWire mode will be temporarily disabled, and the target can +be accessed using normal ISP programming. +This sequence is automatically initiated by using the JTAG ICE mkII +or AVR Dragon in ISP mode, when they detect that ISP mode cannot be +entered. +

    +
  • +Problem: I want to use my JTAG ICE mkII to program an +Xmega device through PDI. The documentation tells me to use the +XMEGA PDI adapter for JTAGICE mkII that is supposed to ship +with the kit, yet I don’t have it. + +

    Solution: Use the following pin mapping: +

    + + + + + + + + + + + + + +
    JTAGICETargetSquid cab-PDI
    mkII probepinsle colorsheader
    1 (TCK)Black
    2 (GND)GNDWhite6
    3 (TDO)Grey
    4 (VTref)VTrefPurple2
    5 (TMS)Blue
    6 (nSRST)PDI_CLKGreen5
    7 (N.C.)Yellow
    8 (nTRST)Orange
    9 (TDI)PDI_DATARed1
    10 (GND)Brown
    + +
  • +Problem: I want to use my AVR Dragon to program an +Xmega device through PDI. + +

    Solution: Use the 6 pin ISP header on the Dragon and the following pin mapping: +

    + + + + + + + + + +
    DragonTarget
    ISP Headerpins
    1 (MISO)PDI_DATA
    2 (VCC)VCC
    3 (SCK)
    4 (MOSI)
    5 (RESET)PDI_CLK / RST
    6 (GND)GND
    + +
  • +Problem: I want to use my AVRISP mkII to program an +ATtiny4/5/9/10 device through TPI. How to connect the pins? + +

    Solution: Use the following pin mapping: +

    + + + + + + + + + +
    AVRISPTargetATtiny
    connectorpinspin #
    1 (MISO)TPIDATA1
    2 (VTref)Vcc5
    3 (SCK)TPICLK3
    4 (MOSI)
    5 (RESET)/RESET6
    6 (GND)GND2
    + +
  • +Problem: I want to program an ATtiny4/5/9/10 device using a serial/parallel +bitbang programmer. How to connect the pins? + +

    Solution: Since TPI has only 1 pin for bi-directional data transfer, both +MISO and MOSI pins should be connected to the TPIDATA pin +on the ATtiny device. +However, a 1K resistor should be placed between the MOSI and TPIDATA. +The MISO pin connects to TPIDATA directly. +The SCK pin is connected to TPICLK. +

    +

    In addition, the Vcc, /RESET and GND pins should +be connected to their respective ports on the ATtiny device. +

    +
  • +Problem: How can I use a FTDI FT232R USB-to-Serial device for bitbang programming? + +

    Solution: When connecting the FT232 directly to the pins of the target Atmel device, +the polarity of the pins defined in the programmer definition should be +inverted by prefixing a tilde. For example, the dasa programmer would +look like this when connected via a FT232R device (notice the tildes in +front of pins 7, 4, 3 and 8): +

    +
    +
    programmer
+  id    = "dasa_ftdi";
+  desc  = "serial port banging, reset=rts sck=dtr mosi=txd miso=cts";
+  type  = serbb;
+  reset = ~7;
+  sck   = ~4;
+  mosi  = ~3;
+  miso  = ~8;
+;
+
    + +

    Note that this uses the FT232 device as a normal serial port, not using the +FTDI drivers in the special bitbang mode. +

    +
  • +Problem: My ATtiny4/5/9/10 reads out fine, but any attempt to program +it (through TPI) fails. Instead, the memory retains the old contents. + +

    Solution: Mind the limited programming supply voltage range of these +devices. +

    +

    In-circuit programming through TPI is only guaranteed by the datasheet +at Vcc = 5 V. +

    +
  • +Problem: My ATxmega…A1/A2/A3 cannot be programmed through PDI with +my AVR Dragon. Programming through a JTAG ICE mkII works though, as does +programming through JTAG. + +

    Solution: None by this time (2010 Q1). +

    +

    It is said that the AVR Dragon can only program devices from the A4 +Xmega sub-family. +

    +
  • +Problem: when programming with an AVRISPmkII or STK600, AVRDUDE hangs +when programming files of a certain size (e.g. 246 bytes). Other +(larger or smaller) sizes work though. + +

    Solution: This is a bug caused by an incorrect handling of zero-length +packets (ZLPs) in some versions of the libusb 0.1 API wrapper that ships +with libusb 1.x in certain Linux distributions. All Linux systems with +kernel versions < 2.6.31 and libusb >= 1.0.0 < 1.0.3 are reported to be +affected by this. +

    +

    See also: http://www.libusb.org/ticket/6 +

    +
  • +Problem: after flashing a firmware that reduces the target’s clock +speed (e.g. through the CLKPR register), further ISP connection +attempts fail. + +

    Solution: Even though ISP starts with pulling /RESET 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. +

    +

    As that slows down the entire subsequent ISP session, it might make +sense to just issue a chip erase using the slow ISP clock +(option -e), and then start a new session at higher speed. +Option -D might be used there, to prevent another unneeded +erase cycle. +

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

+ + This document was generated on March 16, 2022 using texi2html 5.0. + +
+ +

+ + diff --git a/docs/avrdude_4.html b/docs/avrdude_4.html index f6ce2057..7ba31249 100644 --- a/docs/avrdude_4.html +++ b/docs/avrdude_4.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

2.2 Programmers accepting extended parameters

@@ -334,10 +352,18 @@ specific. [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_5.html b/docs/avrdude_5.html index d8ebc355..d31e9fa6 100644 --- a/docs/avrdude_5.html +++ b/docs/avrdude_5.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

2.3 Example Command Line Invocations

@@ -230,10 +248,18 @@ avrdude: usbdev_open(): did not find any (matching) USB device "usb:xxx&quo [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_6.html b/docs/avrdude_6.html index 9de6d20f..8034fe4f 100644 --- a/docs/avrdude_6.html +++ b/docs/avrdude_6.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

3 Terminal Mode Operation

@@ -85,16 +103,9 @@ commands can be recalled and edited.
- - - - - - -
[ << ][ < ][ Up ][ > ][ >> ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_7.html b/docs/avrdude_7.html index 4b2f681f..530b35e6 100644 --- a/docs/avrdude_7.html +++ b/docs/avrdude_7.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

3.1 Terminal Mode Commands

@@ -196,10 +214,18 @@ Display the current target supply voltage and JTAG bit clock rate/period. [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_8.html b/docs/avrdude_8.html index 89a282bb..1fea3296 100644 --- a/docs/avrdude_8.html +++ b/docs/avrdude_8.html @@ -1,6 +1,6 @@ - @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

3.2 Terminal Mode Examples

@@ -171,10 +189,18 @@ avrdude> [ Up ] [ > ] [ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_9.html b/docs/avrdude_9.html index 23536848..c4c436cd 100644 --- a/docs/avrdude_9.html +++ b/docs/avrdude_9.html @@ -1,6 +1,6 @@ - @@ -55,7 +72,7 @@ ul.no-bullet {list-style: none} [ < ] [ Up ] [ > ] -[ >> ] +[ >> ]       @@ -65,6 +82,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

4 Configuration File

@@ -95,7 +113,7 @@ directory as the executable. 4.3 Part Definitions   -4.4 Other Notes   +4.4 Other Notes   @@ -105,11 +123,19 @@ directory as the executable. [ < ] [ Up ] [ > ] -[ >> ] +[ >> ] +   +   +   +   +[Top] +[Contents] +[Index] +[ ? ]

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_abt.html b/docs/avrdude_abt.html index a1e23c9b..652b534b 100644 --- a/docs/avrdude_abt.html +++ b/docs/avrdude_abt.html @@ -1,6 +1,6 @@ - @@ -56,10 +73,11 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

About This Document

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.

The buttons in the navigation panels have the following meaning: @@ -167,7 +185,7 @@ ul.no-bullet {list-style: none}

- This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
diff --git a/docs/avrdude_toc.html b/docs/avrdude_toc.html index 18149e9d..3fc6b389 100644 --- a/docs/avrdude_toc.html +++ b/docs/avrdude_toc.html @@ -1,6 +1,6 @@ - @@ -56,6 +73,7 @@ ul.no-bullet {list-style: none} [Index] [ ? ] +

Table of Contents

@@ -82,52 +100,52 @@ ul.no-bullet {list-style: none}
  • 4.2 Programmer Definitions
  • 4.3 Part Definitions
    • -
  • 4.4 Other Notes
    • +
  • 4.4 Other Notes
    • -
  • 5 Programmer Specific Information +
  • 5 Programmer Specific Information
    • -
  • Appendix A Platform Dependent Information +
  • Appendix A Platform Dependent Information
    • -
  • Appendix B Troubleshooting
    • +
  • Appendix B Troubleshooting
    • @@ -139,7 +157,7 @@ ul.no-bullet {list-style: none}

    - This document was generated on March 13, 2022 using texi2html 5.0. + This document was generated on March 16, 2022 using texi2html 5.0.
    From 27d201acb106b7daf4a75d5647f3c241f1bdc0e2 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Thu, 17 Mar 2022 07:21:33 +0100 Subject: [PATCH 19/25] Also tweak smallexample --- docs/avrdude.html | 8 ++++++-- docs/avrdude_1.html | 8 ++++++-- docs/avrdude_10.html | 8 ++++++-- docs/avrdude_11.html | 8 ++++++-- docs/avrdude_12.html | 8 ++++++-- docs/avrdude_13.html | 8 ++++++-- docs/avrdude_14.html | 8 ++++++-- docs/avrdude_15.html | 8 ++++++-- docs/avrdude_16.html | 8 ++++++-- docs/avrdude_17.html | 8 ++++++-- docs/avrdude_18.html | 8 ++++++-- docs/avrdude_19.html | 8 ++++++-- docs/avrdude_2.html | 8 ++++++-- docs/avrdude_20.html | 8 ++++++-- docs/avrdude_21.html | 8 ++++++-- docs/avrdude_22.html | 8 ++++++-- docs/avrdude_23.html | 8 ++++++-- docs/avrdude_24.html | 8 ++++++-- docs/avrdude_25.html | 8 ++++++-- docs/avrdude_26.html | 8 ++++++-- docs/avrdude_27.html | 8 ++++++-- docs/avrdude_28.html | 8 ++++++-- docs/avrdude_29.html | 8 ++++++-- docs/avrdude_3.html | 8 ++++++-- docs/avrdude_30.html | 8 ++++++-- docs/avrdude_31.html | 8 ++++++-- docs/avrdude_32.html | 8 ++++++-- docs/avrdude_33.html | 8 ++++++-- docs/avrdude_34.html | 8 ++++++-- docs/avrdude_35.html | 8 ++++++-- docs/avrdude_36.html | 8 ++++++-- docs/avrdude_37.html | 8 ++++++-- docs/avrdude_38.html | 8 ++++++-- docs/avrdude_39.html | 8 ++++++-- docs/avrdude_4.html | 8 ++++++-- docs/avrdude_5.html | 8 ++++++-- docs/avrdude_6.html | 8 ++++++-- docs/avrdude_7.html | 8 ++++++-- docs/avrdude_8.html | 8 ++++++-- docs/avrdude_9.html | 8 ++++++-- docs/avrdude_abt.html | 10 +++++++--- docs/avrdude_toc.html | 8 ++++++-- src/doc/avrdude.css | 4 ++++ 43 files changed, 257 insertions(+), 85 deletions(-) diff --git a/docs/avrdude.html b/docs/avrdude.html index 812a4dd9..1cdc6f1e 100644 --- a/docs/avrdude.html +++ b/docs/avrdude.html @@ -1,6 +1,6 @@ - - -AVRDUDE: 1 Introduction - - - - - - - - - - - - - - -

    AVRDUDE

    -

    A program for download/uploading AVR microcontroller flash and eeprom.

    -

    For AVRDUDE, Version 6.99-20211218, 13 March 2022.

    -by Brian S. Dean
    - - - -

    Use https://github.com/avrdudes/avrdude/issues to report bugs and ask questions. -

    -

    Copyright © Brian S. Dean, Jörg Wunsch -


    -
    - -

    Permission is granted to make and distribute verbatim copies of -this manual provided the copyright notice and this permission notice -are preserved on all copies. -

    -

    Permission is granted to copy and distribute modified versions of this -manual under the conditions for verbatim copying, provided that the entire -resulting derived work is distributed under the terms of a permission -notice identical to this one. -

    -

    Permission is granted to copy and distribute translations of this manual -into another language, under the above conditions for modified versions, -except that this permission notice may be stated in a translation approved -by the Free Software Foundation. -

    - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - - - - - - - - - - -
    1 Introduction   -
    2 Command Line Options   -
    3 Terminal Mode Operation   -
    4 Configuration File   -
    5 Programmer Specific Information   -
    Appendix A Platform Dependent Information   -
    Appendix B Troubleshooting   -
    - - - -

    1 Introduction

    - - -

    AVRDUDE - AVR Downloader Uploader - is a program for downloading and -uploading the on-chip memories of Atmel’s AVR microcontrollers. It can -program the Flash and EEPROM, and where supported by the serial -programming protocol, it can program fuse and lock bits. AVRDUDE also -supplies a direct instruction mode allowing one to issue any programming -instruction to the AVR chip regardless of whether AVRDUDE implements -that specific feature of a particular chip. -

    -

    AVRDUDE can be used effectively via the command line to read or write -all chip memory types (eeprom, flash, fuse bits, lock bits, signature -bytes) or via an interactive (terminal) mode. Using AVRDUDE from the -command line works well for programming the entire memory of the chip -from the contents of a file, while interactive mode is useful for -exploring memory contents, modifying individual bytes of eeprom, -programming fuse/lock bits, etc. -

    -

    AVRDUDE supports the following basic programmer types: Atmel’s STK500, -Atmel’s AVRISP and AVRISP mkII devices, -Atmel’s STK600, -Atmel’s JTAG ICE (the original one, mkII, and 3, the latter two also in ISP mode), appnote -avr910, appnote avr109 (including the AVR Butterfly), -serial bit-bang adapters, -and the PPI (parallel port interface). PPI represents a class -of simple programmers where the programming lines are directly -connected to the PC parallel port. Several pin configurations exist -for several variations of the PPI programmers, and AVRDUDE can be -configured to work with them by either specifying the appropriate -programmer on the command line or by creating a new entry in its -configuration file. All that’s usually required for a new entry is to -tell AVRDUDE which pins to use for each programming function. -

    -

    A number of equally simple bit-bang programming adapters that connect -to a serial port are supported as well, among them the popular -Ponyprog serial adapter, and the DASA and DASA3 adapters that used to -be supported by uisp(1). Note that these adapters are meant to be -attached to a physical serial port. Connecting to a serial port -emulated on top of USB is likely to not work at all, or to work -abysmally slow. -

    -

    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 -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 -overcurrent situations in some way. The simplest would be to just put -some resistors in series or better yet use a 3-state buffer driver like -the 74HC244. Have a look at http://kolev.info/blog/2013/01/06/avrdude-linuxgpio/ for a more -detailed tutorial about using this programmer type. -

    -

    Under a Linux installation with direct access to the SPI bus and GPIO -pins, such as would be found on a Raspberry Pi, the “linuxspi” -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 -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’s SPI controller in the -event that the chip is running at 5V and the SPI runs at 3.3V. The -GPIO chosen for reset can be configured in the avrdude configuration -file using the reset entry under the linuxspi programmer, or -directly in the port specification. An external pull-up resistor -should be connected between the AVR’s reset pin and Vcc. If Vcc is not -the same as the SPI voltage, this should be done on the AVR side of -the level translator to protect the hardware from damage. -

    -

    On a Raspberry Pi, header J8 provides access to the SPI and GPIO -lines. -

    -

    Typically, pins 19, 21, and 23 are SPI MOSI, MISO, 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. -

    -

    A typical programming cable would then look like: -

    - - - - - - - - -
    J8 pinISP pinName
    211MISO
    -2Vcc - leave open
    233SCK
    194MOSI
    225/RESET
    256GND
    - -

    (Mind the 3.3 V voltage level of the Raspberry Pi!) -

    -

    The -P portname option defaults to -/dev/spidev0.0:/dev/gpiochip0 for this programmer. -

    -

    The STK500, JTAG ICE, avr910, and avr109/butterfly use the serial port to communicate with the PC. -The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivatives), and USBtinyISP -programmers communicate through the USB, using libusb 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 -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 -device. -The avr109 bootloader implements a protocol similar to avr910, but is -actually implemented in the boot area of the target’s flash ROM, as -opposed to being an external device. -The fundamental difference between the two types lies in the -protocol used to control the programmer. The avr910 protocol is very -simplistic and can easily be used as the basis for a simple, home made -programmer since the firmware is available online. On the other hand, -the STK500 protocol is more robust and complicated and the firmware is -not openly available. -The JTAG ICE also uses a serial communication protocol which is similar -to the STK500 firmware version 2 one. However, as the JTAG ICE is -intended to allow on-chip debugging as well as memory programming, the -protocol is more sophisticated. -(The JTAG ICE mkII protocol can also be run on top of USB.) -Only the memory programming functionality of the JTAG ICE is supported -by AVRDUDE. -For the JTAG ICE mkII/3, JTAG, debugWire and ISP mode are supported, provided -it has a firmware revision of at least 4.14 (decimal). -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). -

    -

    The Atmel-ICE (ARM/AVR) is supported (JTAG, PDI for Xmega, debugWIRE, ISP modes). -

    -

    Atmel’s XplainedPro boards, using EDBG protocol (CMSIS-DAP compliant), are -supported by the “jtag3” programmer type. -

    -

    Atmel’s XplainedMini boards, using mEDBG protocol, are also -supported by the “jtag3” programmer type. -

    -

    The AVR Dragon is supported in all modes (ISP, JTAG, PDI, HVSP, PP, debugWire). -When used in JTAG and debugWire mode, the AVR Dragon behaves similar to a -JTAG ICE mkII, so all device-specific comments for that device -will apply as well. -When used in ISP and PDI mode, the AVR Dragon behaves similar to an -AVRISP mkII (or JTAG ICE mkII in ISP mode), so all device-specific -comments will apply there. -In particular, the Dragon starts out with a rather fast ISP clock -frequency, so the -B bitclock -option might be required to achieve a stable ISP communication. -For ATxmega devices, the AVR Dragon is supported in PDI mode, provided it -has a firmware version of at least 6.11 (decimal). -

    -

    Wiring boards (e.g. Arduino Mega 2560 Rev3) are supported, utilizing -STK500 V2.x protocol, but a simple DTR/RTS toggle to set the boards -into programming mode. The programmer type is “wiring”. Note that -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. -

    -

    The Arduino (which is very similar to the STK500 1.x) is supported via -its own programmer type specification “arduino”. 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 -extended parameters -below for details. -

    -

    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 -extended parameters -below for details. -

    -

    The USBasp ISP and USBtinyISP adapters are also supported, provided AVRDUDE -has been compiled with libusb support. -They both feature simple firmware-only USB implementations, running on -an ATmega8 (or ATmega88), or ATtiny2313, respectively. -

    -

    The Atmel DFU bootloader is supported in both, FLIP protocol version 1 -(AT90USB* and ATmega*U* devices), as well as version 2 (Xmega devices). -See below for some hints about FLIP version 1 protocol behaviour. -

    -

    The MPLAB(R) PICkit 4 and MPLAB(R) SNAP are supported in ISP, PDI and UPDI mode. -The Curiosity Nano board is supported in UPDI mode. It is dubbed “PICkit on -Board”, thus the name pkobn_updi. -

    -

    SerialUPDI programmer implementation is based on Microchip’s -pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) -utility, but it also contains some performance improvements included in -Spence Konde’s DxCore Arduino core (https://github.com/SpenceKonde/DxCore). -In a nutshell, this programmer consists of simple USB->UART adapter, diode -and couple of resistors. It uses serial connection to provide UPDI interface. -See section SerialUPDI programmer for more details and known issues. -

    -

    The jtag2updi programmer is supported, -and can program AVRs with a UPDI interface. -Jtag2updi is just a firmware that can be uploaded to an AVR, -which enables it to interface with avrdude using the jtagice mkii protocol -via a serial link (https://github.com/ElTangas/jtag2updi). -

    -

    The Micronucleus bootloader is supported for both protocol version V1 -and V2. As the bootloader does not support reading from flash memory, -use the -V option to prevent AVRDUDE from verifing the flash memory. -See the section on extended parameters -below for Micronucleus specific options. -

    -

    The Teensy bootloader is supported for all AVR boards. -As the bootloader does not support reading from flash memory, -use the -V option to prevent AVRDUDE from verifing the flash memory. -See the section on extended parameters -below for Teensy specific options. -

    - - -
    1.1 History and Credits   -
    - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_1.html b/docs/avrdude_1.html deleted file mode 100644 index be610b57..00000000 --- a/docs/avrdude_1.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - -AVRDUDE: 1.1 History and Credits - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    1.1 History and Credits

    - -

    AVRDUDE was written by Brian S. Dean under the name of AVRPROG to run on -the FreeBSD Operating System. Brian renamed the software to be called -AVRDUDE when interest grew in a Windows port of the software so that the -name did not conflict with AVRPROG.EXE which is the name of Atmel’s -Windows programming software. -

    -

    For many years, the AVRDUDE source resided in public repositories on -savannah.nongnu.org, -where it continued to be enhanced and ported to other systems. In -addition to FreeBSD, AVRDUDE now runs on Linux and Windows. The -developers behind the porting effort primarily were Ted Roth, Eric -Weddington, and Joerg Wunsch. -

    -

    In 2022, the project moved to Github (https://github.com/avrdudes/avrdude/). -

    -

    And in the spirit of many open source projects, this manual also draws -on the work of others. The initial revision was composed of parts of -the original Unix manual page written by Joerg Wunsch, the original web -site documentation by Brian Dean, and from the comments describing the -fields in the AVRDUDE configuration file by Brian Dean. The texi -formatting was modeled after that of the Simulavr documentation by Ted -Roth. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_10.html b/docs/avrdude_10.html deleted file mode 100644 index e0aa8c3c..00000000 --- a/docs/avrdude_10.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - -AVRDUDE: 4.1 AVRDUDE Defaults - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.1 AVRDUDE Defaults

    - -
    -
    default_parallel = "default-parallel-device";
    -

    Assign the default parallel port device. Can be overridden using the -‘-P’ option. -

    -
    -
    default_serial = "default-serial-device";
    -

    Assign the default serial port device. Can be overridden using the -‘-P’ option. -

    -
    -
    default_programmer = "default-programmer-id";
    -

    Assign the default programmer id. Can be overridden using the ‘-c’ -option. -

    -
    -
    default_bitclock = "default-bitclock";
    -

    Assign the default bitclock value. Can be overridden using the ‘-B’ -option. -

    -
    -
    - - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_11.html b/docs/avrdude_11.html deleted file mode 100644 index 2be52a23..00000000 --- a/docs/avrdude_11.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - -AVRDUDE: 4.2 Programmer Definitions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.2 Programmer Definitions

    - -

    The format of the programmer definition is as follows: -

    -
    -
    programmer
-    parent <id>                                 # <id> is a quoted string
-    id       = <id1> [, <id2> [, <id3>] ...] ;  # <idN> are quoted strings
-    desc     = <description> ;                  # quoted string
-    type     = "par" | "stk500" | ... ;         # programmer type (see below for a list)
-    baudrate = <num> ;                          # baudrate for serial ports
-    vcc      = <num1> [, <num2> ... ] ;         # pin number(s)
-    buff     = <num1> [, <num2> ... ] ;         # pin number(s)
-    reset    = <num> ;                          # pin number
-    sck      = <num> ;                          # pin number
-    mosi     = <num> ;                          # pin number
-    miso     = <num> ;                          # pin number
-    errled   = <num> ;                          # pin number
-    rdyled   = <num> ;                          # pin number
-    pgmled   = <num> ;                          # pin number
-    vfyled   = <num> ;                          # pin number
-    usbvid   = <hexnum>;                        # USB VID (Vendor ID)
-    usbpid   = <hexnum> [, <hexnum> ...];       # USB PID (Product ID)
-    usbdev   = <interface>;                     # USB interface or other device info 
-    usbvendor = <vendorname>;                   # USB Vendor Name
-    usbproduct = <productname>;                 # USB Product Name
-    usbsn    = <serialno>;                      # USB Serial Number
-  ;
-
    - -

    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. -

    -

    To invert a bit in the pin definitions, use = ~ <num>. -

    -

    Not all programmer types can handle a list of USB PIDs. -

    -

    Following programmer types are currently implemented: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    arduinoArduino programmer
    avr910Serial programmers using protocol described in application note AVR910
    avrftdiInterface to the MPSSE Engine of FTDI Chips using libftdi.
    buspirateUsing the Bus Pirate’s SPI interface for programming
    buspirate_bbUsing the Bus Pirate’s bitbang interface for programming
    butterflyAtmel Butterfly evaluation board; Atmel AppNotes AVR109, AVR911
    butterfly_mkMikrokopter.de Butterfly
    dragon_dwAtmel AVR Dragon in debugWire mode
    dragon_hvspAtmel AVR Dragon in HVSP mode
    dragon_ispAtmel AVR Dragon in ISP mode
    dragon_jtagAtmel AVR Dragon in JTAG mode
    dragon_pdiAtmel AVR Dragon in PDI mode
    dragon_ppAtmel AVR Dragon in PP mode
    flip1FLIP USB DFU protocol version 1 (doc7618)
    flip2FLIP USB DFU protocol version 2 (AVR4023)
    ftdi_syncbbFT245R/FT232R Synchronous BitBangMode Programmer
    jtagmkiAtmel JTAG ICE mkI
    jtagmkiiAtmel JTAG ICE mkII
    jtagmkii_avr32Atmel JTAG ICE mkII in AVR32 mode
    jtagmkii_dwAtmel JTAG ICE mkII in debugWire mode
    jtagmkii_ispAtmel JTAG ICE mkII in ISP mode
    jtagmkii_pdiAtmel JTAG ICE mkII in PDI mode
    jtagice3Atmel JTAGICE3
    jtagice3_pdiAtmel JTAGICE3 in PDI mode
    jtagice3_updiAtmel JTAGICE3 in UPDI mode
    jtagice3_dwAtmel JTAGICE3 in debugWire mode
    jtagice3_ispAtmel JTAGICE3 in ISP mode
    linuxgpioGPIO bitbanging using the Linux sysfs interface (not available)
    linuxspiSPI using Linux spidev driver (not available)
    micronucleusMicronucleus Bootloader
    parParallel port bitbanging
    pickit2Microchip’s PICkit2 Programmer
    serbbSerial port bitbanging
    serialupdiDriver for SerialUPDI programmers
    stk500Atmel STK500 Version 1.x firmware
    stk500genericAtmel STK500, autodetect firmware version
    stk500v2Atmel STK500 Version 2.x firmware
    stk500hvspAtmel STK500 V2 in high-voltage serial programming mode
    stk500ppAtmel STK500 V2 in parallel programming mode
    stk600Atmel STK600
    stk600hvspAtmel STK600 in high-voltage serial programming mode
    stk600ppAtmel STK600 in parallel programming mode
    teensyTeensy Bootloader
    usbaspUSBasp programmer, see http://www.fischl.de/usbasp/
    usbtinyDriver for "usbtiny"-type programmers
    wiringhttp://wiring.org.co/, Basically STK500v2 protocol, with some glue to trigger the bootloader.
    xbeeXBee Series 2 Over-The-Air (XBeeBoot)
    - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_12.html b/docs/avrdude_12.html deleted file mode 100644 index 4ea8fd33..00000000 --- a/docs/avrdude_12.html +++ /dev/null @@ -1,219 +0,0 @@ - - - - -AVRDUDE: 4.3 Part Definitions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.3 Part Definitions

    - -
    -
    part
-    id               = <id> ;                 # quoted string
-    desc             = <description> ;        # quoted string
-    family_id        = <description> ;        # quoted string
-    has_jtag         = <yes/no> ;             # part has JTAG i/f
-    has_debugwire    = <yes/no> ;             # part has debugWire i/f
-    has_pdi          = <yes/no> ;             # part has PDI i/f
-    has_updi         = <yes/no> ;             # part has UPDI i/f
-    has_tpi          = <yes/no> ;             # part has TPI i/f
-    devicecode       = <num> ;                # numeric
-    stk500_devcode   = <num> ;                # numeric
-    avr910_devcode   = <num> ;                # numeric
-    signature        = <num> <num> <num> ;    # signature bytes
-    usbpid           = <num> ;                # DFU USB PID
-    reset            = dedicated | io;
-    retry_pulse      = reset | sck;
-    pgm_enable       = <instruction format> ;
-    chip_erase       = <instruction format> ;
-    chip_erase_delay = <num> ;                # micro-seconds
-    # STK500 parameters (parallel programming IO lines)
-    pagel            = <num> ;                # pin name in hex, i.e., 0xD7
-    bs2              = <num> ;                # pin name in hex, i.e., 0xA0
-    serial           = <yes/no> ;             # can use serial downloading
-    parallel         = <yes/no/pseudo>;       # can use par. programming
-    # STK500v2 parameters, to be taken from Atmel's XML files
-    timeout          = <num> ;
-    stabdelay        = <num> ;
-    cmdexedelay      = <num> ;
-    synchloops       = <num> ;
-    bytedelay        = <num> ;
-    pollvalue        = <num> ;
-    pollindex        = <num> ;
-    predelay         = <num> ;
-    postdelay        = <num> ;
-    pollmethod       = <num> ;
-    mode             = <num> ;
-    delay            = <num> ;
-    blocksize        = <num> ;
-    readsize         = <num> ;
-    hvspcmdexedelay  = <num> ;
-    # STK500v2 HV programming parameters, from XML
-    pp_controlstack  = <num>, <num>, ...;     # PP only
-    hvsp_controlstack = <num>, <num>, ...;    # HVSP only
-    hventerstabdelay = <num>;
-    progmodedelay    = <num>;                 # PP only
-    latchcycles      = <num>;
-    togglevtg        = <num>;
-    poweroffdelay    = <num>;
-    resetdelayms     = <num>;
-    resetdelayus     = <num>;
-    hvleavestabdelay = <num>;
-    resetdelay       = <num>;
-    synchcycles      = <num>;                 # HVSP only
-    chiperasepulsewidth = <num>;              # PP only
-    chiperasepolltimeout = <num>;
-    chiperasetime    = <num>;                 # HVSP only
-    programfusepulsewidth = <num>;            # PP only
-    programfusepolltimeout = <num>;
-    programlockpulsewidth = <num>;            # PP only
-    programlockpolltimeout = <num>;
-    # JTAG ICE mkII parameters, also from XML files
-    allowfullpagebitstream = <yes/no> ;
-    enablepageprogramming = <yes/no> ;
-    idr              = <num> ;                # IO addr of IDR (OCD) reg.
-    rampz            = <num> ;                # IO addr of RAMPZ reg.
-    spmcr            = <num> ;                # mem addr of SPMC[S]R reg.
-    eecr             = <num> ;                # mem addr of EECR reg.
-                                              # (only when != 0x3c)
-    is_at90s1200     = <yes/no> ;             # AT90S1200 part
-    is_avr32         = <yes/no> ;             # AVR32 part
-
-    memory <memtype>
-        paged           = <yes/no> ;          # yes / no
-        size            = <num> ;             # bytes
-        page_size       = <num> ;             # bytes
-        num_pages       = <num> ;             # numeric
-        min_write_delay = <num> ;             # micro-seconds
-        max_write_delay = <num> ;             # micro-seconds
-        readback_p1     = <num> ;             # byte value
-        readback_p2     = <num> ;             # byte value
-        pwroff_after_write = <yes/no> ;       # yes / no
-        read            = <instruction format> ;
-        write           = <instruction format> ;
-        read_lo         = <instruction format> ;
-        read_hi         = <instruction format> ;
-        write_lo        = <instruction format> ;
-        write_hi        = <instruction format> ;
-        loadpage_lo     = <instruction format> ;
-        loadpage_hi     = <instruction format> ;
-        writepage       = <instruction format> ;
-      ;
-  ;
-
    - - - - -
    4.3.1 Parent Part   -
    4.3.2 Instruction Format   -
    - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_13.html b/docs/avrdude_13.html deleted file mode 100644 index 210ffe04..00000000 --- a/docs/avrdude_13.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - -AVRDUDE: 4.3.1 Parent Part - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.3.1 Parent Part

    - -

    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. -

    -
    -
       part parent <id>                              # quoted string
-       id               = <id> ;                 # quoted string
-       <any set of other parameters from the list above>
-     ;
-
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_14.html b/docs/avrdude_14.html deleted file mode 100644 index 25af1dcf..00000000 --- a/docs/avrdude_14.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - -AVRDUDE: 4.3.2 Instruction Format - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.3.2 Instruction Format

    - -

    Instruction formats are specified as a comma separated list of string -values containing information (bit specifiers) about each of the 32 bits -of the instruction. Bit specifiers may be one of the following formats: -

    -
    -
    1
    -

    The bit is always set on input as well as output -

    -
    -
    0
    -

    the bit is always clear on input as well as output -

    -
    -
    x
    -

    the bit is ignored on input and output -

    -
    -
    a
    -

    the bit is an address bit, the bit-number matches this bit specifier’s -position within the current instruction byte -

    -
    -
    aN
    -

    the bit is the Nth address bit, bit-number = N, i.e., a12 -is address bit 12 on input, a0 is address bit 0. -

    -
    -
    i
    -

    the bit is an input data bit -

    -
    -
    o
    -

    the bit is an output data bit -

    -
    -
    - -

    Each instruction must be composed of 32 bit specifiers. The instruction -specification closely follows the instruction data provided in Atmel’s -data sheets for their parts. For example, the EEPROM read and write -instruction for an AT90S2313 AVR part could be encoded as: -

    -
    -
    -read  = "1  0  1  0   0  0  0  0   x x x x  x x x x",
-        "x a6 a5 a4  a3 a2 a1 a0   o o o o  o o o o";
-
-write = "1  1  0  0   0  0  0  0   x x x x  x x x x",
-        "x a6 a5 a4  a3 a2 a1 a0   i i i i  i i i i";
-
-
    - - - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_15.html b/docs/avrdude_15.html deleted file mode 100644 index 9d8b02f3..00000000 --- a/docs/avrdude_15.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - -AVRDUDE: 4.4 Other Notes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4.4 Other Notes

    - - -
      -
    • -The devicecode parameter is the device code used by the STK500 -and is obtained from the software section (avr061.zip) of -Atmel’s AVR061 application note available from -http://www.atmel.com/dyn/resources/prod_documents/doc2525.pdf. - -
    • -Not all memory types will implement all instructions. - -
    • -AVR Fuse bits and Lock bits are implemented as a type of memory. - -
    • -Example memory types are: flash, eeprom, fuse, -lfuse (low fuse), hfuse (high fuse), efuse -(extended fuse), signature, calibration, lock. - -
    • -The memory type specified on the AVRDUDE command line must match one of -the memory types defined for the specified chip. - -
    • -The pwroff_after_write flag causes AVRDUDE to attempt to power -the device off and back on after an unsuccessful write to the affected -memory area if VCC programmer pins are defined. If VCC pins are not -defined for the programmer, a message indicating that the device needs a -power-cycle is printed out. This flag was added to work around a -problem with the at90s4433/2333’s; see the at90s4433 errata at: - -

      http://www.atmel.com/dyn/resources/prod_documents/doc1280.pdf -

      -
    • -The boot loader from application note AVR109 (and thus also the AVR -Butterfly) does not support writing of fuse bits. Writing lock bits -is supported, but is restricted to the boot lock bits (BLBxx). These -are restrictions imposed by the underlying SPM instruction that is used -to program the device from inside the boot loader. Note that programming -the boot lock bits can result in a “shoot-into-your-foot” scenario as -the only way to unprogram these bits is a chip erase, which will also -erase the boot loader code. - -

      The boot loader implements the “chip erase” function by erasing the -flash pages of the application section. -

      -

      Reading fuse and lock bits is fully supported. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_16.html b/docs/avrdude_16.html deleted file mode 100644 index 5b8885c1..00000000 --- a/docs/avrdude_16.html +++ /dev/null @@ -1,111 +0,0 @@ - - - - -AVRDUDE: 5 Programmer Specific Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    5 Programmer Specific Information

    - - - - - -
    5.1 Atmel STK600   -
    5.2 Atmel DFU bootloader using FLIP version 1   -
    5.3 SerialUPDI programmer   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_17.html b/docs/avrdude_17.html deleted file mode 100644 index e90856ce..00000000 --- a/docs/avrdude_17.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - -AVRDUDE: 5.1 Atmel STK600 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    5.1 Atmel STK600

    - -

    The following devices are supported by the respective STK600 routing -and socket card: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Routing cardSocket cardDevices
    STK600-ATTINY10ATtiny4 ATtiny5 ATtiny9 ATtiny10
    STK600-RC008T-2STK600-DIPATtiny11 ATtiny12 ATtiny13 ATtiny13A ATtiny25 ATtiny45 ATtiny85
    STK600-RC008T-7STK600-DIPATtiny15
    STK600-RC014T-42STK600-SOICATtiny20
    STK600-RC020T-1STK600-DIPATtiny2313 ATtiny2313A ATtiny4313
    STK600-TinyX3UATtiny43U
    STK600-RC014T-12STK600-DIPATtiny24 ATtiny44 ATtiny84 ATtiny24A ATtiny44A
    STK600-RC020T-8STK600-DIPATtiny26 ATtiny261 ATtiny261A ATtiny461 ATtiny861 ATtiny861A
    STK600-RC020T-43STK600-SOICATtiny261 ATtiny261A ATtiny461 ATtiny461A ATtiny861 ATtiny861A
    STK600-RC020T-23STK600-SOICATtiny87 ATtiny167
    STK600-RC028T-3STK600-DIPATtiny28
    STK600-RC028M-6STK600-DIPATtiny48 ATtiny88 ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
    QT600-ATTINY88-QT8ATtiny88
    STK600-RC040M-4STK600-DIPATmega8515 ATmega162
    STK600-RC044M-30STK600-TQFP44ATmega8515 ATmega162
    STK600-RC040M-5STK600-DIPATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
    STK600-RC044M-31STK600-TQFP44ATmega8535 ATmega16 ATmega16A ATmega32 ATmega32A ATmega164P ATmega164PA ATmega324P ATmega324PA ATmega644 ATmega644P ATmega644PA ATmega1284P
    QT600-ATMEGA324-QM64ATmega324PA
    STK600-RC032M-29STK600-TQFP32ATmega8 ATmega8A ATmega48 ATmega88 ATmega168 ATmega48P ATmega48PA ATmega88P ATmega88PA ATmega168P ATmega168PA ATmega328P
    STK600-RC064M-9STK600-TQFP64ATmega64 ATmega64A ATmega128 ATmega128A ATmega1281 ATmega2561 AT90CAN32 AT90CAN64 AT90CAN128
    STK600-RC064M-10STK600-TQFP64ATmega165 ATmega165P ATmega169 ATmega169P ATmega169PA ATmega325 ATmega325P ATmega329 ATmega329P ATmega645 ATmega649 ATmega649P
    STK600-RC100M-11STK600-TQFP100ATmega640 ATmega1280 ATmega2560
    STK600-ATMEGA2560ATmega2560
    STK600-RC100M-18STK600-TQFP100ATmega3250 ATmega3250P ATmega3290 ATmega3290P ATmega6450 ATmega6490
    STK600-RC032U-20STK600-TQFP32AT90USB82 AT90USB162 ATmega8U2 ATmega16U2 ATmega32U2
    STK600-RC044U-25STK600-TQFP44ATmega16U4 ATmega32U4
    STK600-RC064U-17STK600-TQFP64ATmega32U6 AT90USB646 AT90USB1286 AT90USB647 AT90USB1287
    STK600-RCPWM-22STK600-TQFP32ATmega32C1 ATmega64C1 ATmega16M1 ATmega32M1 ATmega64M1
    STK600-RCPWM-19STK600-SOICAT90PWM2 AT90PWM3 AT90PWM2B AT90PWM3B AT90PWM216 AT90PWM316
    STK600-RCPWM-26STK600-SOICAT90PWM81
    STK600-RC044M-24STK600-TSSOP44ATmega16HVB ATmega32HVB
    STK600-HVE2ATmega64HVE
    STK600-ATMEGA128RFA1ATmega128RFA1
    STK600-RC100X-13STK600-TQFP100ATxmega64A1 ATxmega128A1 ATxmega128A1_revD ATxmega128A1U
    STK600-ATXMEGA1281A1ATxmega128A1
    QT600-ATXMEGA128A1-QT16ATxmega128A1
    STK600-RC064X-14STK600-TQFP64ATxmega64A3 ATxmega128A3 ATxmega256A3 ATxmega64D3 ATxmega128D3 ATxmega192D3 ATxmega256D3
    STK600-RC064X-14STK600-MLF64ATxmega256A3B
    STK600-RC044X-15STK600-TQFP44ATxmega32A4 ATxmega16A4 ATxmega16D4 ATxmega32D4
    STK600-ATXMEGAT0ATxmega32T0
    STK600-uC3-144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
    STK600-RCUC3A144-33STK600-TQFP144AT32UC3A0512 AT32UC3A0256 AT32UC3A0128
    STK600-RCuC3A100-28STK600-TQFP100AT32UC3A1512 AT32UC3A1256 AT32UC3A1128
    STK600-RCuC3B0-21STK600-TQFP64-2AT32UC3B0256 AT32UC3B0512RevC AT32UC3B0512 AT32UC3B0128 AT32UC3B064 AT32UC3D1128
    STK600-RCuC3B48-27STK600-TQFP48AT32UC3B1256 AT32UC3B164
    STK600-RCUC3A144-32STK600-TQFP144AT32UC3A3512 AT32UC3A3256 AT32UC3A3128 AT32UC3A364 AT32UC3A3256S AT32UC3A3128S AT32UC3A364S
    STK600-RCUC3C0-36STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
    STK600-RCUC3C1-38STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
    STK600-RCUC3C2-40STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
    STK600-RCUC3C0-37STK600-TQFP144AT32UC3C0512 AT32UC3C0256 AT32UC3C0128 AT32UC3C064
    STK600-RCUC3C1-39STK600-TQFP100AT32UC3C1512 AT32UC3C1256 AT32UC3C1128 AT32UC3C164
    STK600-RCUC3C2-41STK600-TQFP64-2AT32UC3C2512 AT32UC3C2256 AT32UC3C2128 AT32UC3C264
    STK600-RCUC3L0-34STK600-TQFP48AT32UC3L064 AT32UC3L032 AT32UC3L016
    QT600-AT32UC3L-QM64AT32UC3L064
    - -

    Ensure the correct socket and routing card are mounted before -powering on the STK600. While the STK600 firmware ensures the socket -and routing card mounted match each other (using a table stored -internally in nonvolatile memory), it cannot handle the case where a -wrong routing card is used, e. g. the routing card -STK600-RC040M-5 (which is meant for 40-pin DIP AVRs that have -an ADC, with the power supply pins in the center of the package) was -used but an ATmega8515 inserted (which uses the “industry standard” -pinout with Vcc and GND at opposite corners). -

    -

    Note that for devices that use the routing card STK600-RC008T-2, -in order to use ISP mode, the jumper for AREF0 must be removed -as it would otherwise block one of the ISP signals. High-voltage -serial programming can be used even with that jumper installed. -

    -

    The ISP system of the STK600 contains a detection against shortcuts -and other wiring errors. AVRDUDE initiates a connection check before -trying to enter ISP programming mode, and display the result if the -target is not found ready to be ISP programmed. -

    -

    High-voltage programming requires the target voltage to be set to at -least 4.5 V in order to work. This can be done using -Terminal Mode, see Terminal Mode Operation. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_18.html b/docs/avrdude_18.html deleted file mode 100644 index 5414d7b7..00000000 --- a/docs/avrdude_18.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - -AVRDUDE: 5.2 Atmel DFU bootloader using FLIP version 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    5.2 Atmel DFU bootloader using FLIP version 1

    - -

    Bootloaders using the FLIP protocol version 1 experience some very -specific behaviour. -

    -

    These bootloaders have no option to access memory areas other than -Flash and EEPROM. -

    -

    When the bootloader is started, it enters a security mode where -the only acceptable access is to query the device configuration -parameters (which are used for the signature on AVR devices). The -only way to leave this mode is a chip erase. As a chip erase -is normally implied by the ‘-U’ option when reprogramming the -flash, this peculiarity might not be very obvious immediately. -

    -

    Sometimes, a bootloader with security mode already disabled seems to -no longer respond with sensible configuration data, but only 0xFF for -all queries. As these queries are used to obtain the equivalent of a -signature, AVRDUDE can only continue in that situation by forcing the -signature check to be overridden with the ‘-F’ option. -

    -

    A chip erase might leave the EEPROM unerased, at least on some -versions of the bootloader. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_19.html b/docs/avrdude_19.html deleted file mode 100644 index 023f8329..00000000 --- a/docs/avrdude_19.html +++ /dev/null @@ -1,211 +0,0 @@ - - - - -AVRDUDE: 5.3 SerialUPDI programmer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    5.3 SerialUPDI programmer

    - -

    SerialUPDI programmer can be used for programming UPDI-only devices -using very simple serial connection. -You can read more about the details here -https://github.com/SpenceKonde/AVR-Guidance/blob/master/UPDI/jtag2updi.md -

    -

    SerialUPDI programmer has been tested using FT232RL USB->UART interface -with the following connection layout (copied from Spence Kohde’s page linked -above): -

    -
    -
    --------------------                                 To Target device
-                DTR|                                  __________________
-                Rx |--------------,------------------| UPDI---\/\/---------->
-  Tx---/\/\/\---Tx |-------|<|---'          .--------| Gnd    470 ohm 
-    resistor    Vcc|---------------------------------| Vcc
-        1k      CTS|                     .`          |__________________
-                Gnd|--------------------' 
---------------------
-
    - -

    There are several limitations in current SerialUPDI/AVRDUDE integration, -listed below. -

    -

    At the end of each run there are fuse values being presented to the user. -For most of the UPDI-enabled devices these definitions (low fuse, high -fuse, extended fuse) have no meaning whatsoever, as they have been -simply replaced by array of fuses: fuse0..9. Therefore you can simply -ignore this particular line of AVRDUDE output. -

    -

    Currently available devices support only UPDI NVM programming model 0 -and 2, but there is also experimental implementation of model 3 - not -yet tested. -

    -

    One of the core AVRDUDE features is verification of the connection by -reading device signature prior to any operation, but this operation -is not possible on UPDI locked devices. Therefore, to be able to -connect to such a device, you have to provide ‘-F’ to override -this check. -

    -

    Please note: using ‘-F’ during write operation to locked device -will force chip erase. Use carefully. -

    -

    Another issue you might notice is slow performance of EEPROM writing -using SerialUPDI for AVR Dx devices. This can be addressed by changing -avrdude.conf section for this device - changing EEPROM page -size to 0x20 (instead of default 1), like so: -

    -
    -
    #------------------------------------------------------------
-# AVR128DB28
-#------------------------------------------------------------
-
-part parent    ".avrdx"
-    id        = "avr128db28";
-    desc      = "AVR128DB28";
-    signature = 0x1E 0x97 0x0E;
-
-    memory "flash"
-        size      = 0x20000;
-        offset    = 0x800000;
-        page_size = 0x200;
-        readsize  = 0x100;
-    ;
-
-    memory "eeprom"
-        size      = 0x200;
-        offset    = 0x1400;
-        page_size = 0x1;
-        readsize  = 0x100;
-    ;
-;
-
    - -

    USERROW memory has not been defined for new devices except for -experimental addition for AVR128DB28. The point of USERROW is to -provide ability to write configuration details to already locked -device and currently SerialUPDI interface supports this feature, -but it hasn’t been tested on wide variety of chips. Treat this as -something experimental at this point. Please note: on locked devices -it’s not possible to read back USERROW contents when written, so -the automatic verification will most likely fail and to prevent -error messages, use ‘-V’. -

    -

    Please note that SerialUPDI interface is pretty new and some -issues are to be expected. In case you run into them, please -make sure to run the intended command with debug output enabled -(‘-v -v -v’) and provide this verbose output with your -bug report. You can also try to perform the same action using -pymcuprog (https://github.com/microchip-pic-avr-tools/pymcuprog) -utility with ‘-v debug’ and provide its output too. -You will notice that both outputs are pretty similar, and this -was implemented like that on purpose - it was supposed to make -analysis of UPDI protocol quirks easier. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_2.html b/docs/avrdude_2.html deleted file mode 100644 index 5ccc1cec..00000000 --- a/docs/avrdude_2.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - -AVRDUDE: 2 Command Line Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    2 Command Line Options

    - - - - - - -
    2.1 Option Descriptions   -
    2.2 Programmers accepting extended parameters   -
    2.3 Example Command Line Invocations   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_20.html b/docs/avrdude_20.html deleted file mode 100644 index 63b07f6b..00000000 --- a/docs/avrdude_20.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - -AVRDUDE: Appendix A Platform Dependent Information - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    Appendix A Platform Dependent Information

    - - - - -
    A.1 Unix   -
    A.2 Windows   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_21.html b/docs/avrdude_21.html deleted file mode 100644 index a21997a4..00000000 --- a/docs/avrdude_21.html +++ /dev/null @@ -1,113 +0,0 @@ - - - - -AVRDUDE: A.1 Unix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1 Unix

    - - - - - - -
    A.1.1 Unix Installation   -
    A.1.2 Unix Configuration Files   -
    A.1.3 Unix Port Names   -
    A.1.4 Unix Documentation   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_22.html b/docs/avrdude_22.html deleted file mode 100644 index 00b19ddf..00000000 --- a/docs/avrdude_22.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - -AVRDUDE: A.1.1 Unix Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.1 Unix Installation

    - -

    To build and install from the source tarball on Unix like systems: -

    -
    -
    $ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure
-$ make
-$ su root -c 'make install'
-
    - -

    The default location of the install is into /usr/local so you -will need to be sure that /usr/local/bin is in your PATH -environment variable. -

    -

    If you do not have root access to your system, you can do the -following instead: -

    -
    -
    $ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure --prefix=$HOME/local
-$ make
-$ make install
-
    - - - - -
    A.1.1.1 FreeBSD Installation   -
    A.1.1.2 Linux Installation   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_23.html b/docs/avrdude_23.html deleted file mode 100644 index bb532118..00000000 --- a/docs/avrdude_23.html +++ /dev/null @@ -1,122 +0,0 @@ - - - - -AVRDUDE: A.1.1.1 FreeBSD Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.1.1 FreeBSD Installation

    - -

    AVRDUDE is installed via the FreeBSD Ports Tree as follows: -

    -
    -
    % su - root
-# cd /usr/ports/devel/avrdude
-# make install
-
    - -

    If you wish to install from a pre-built package instead of the source, -you can use the following instead: -

    -
    -
    % su - root
-# pkg_add -r avrdude
-
    - -

    Of course, you must be connected to the Internet for these methods to -work, since that is where the source as well as the pre-built package is -obtained. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_24.html b/docs/avrdude_24.html deleted file mode 100644 index c1ae1a81..00000000 --- a/docs/avrdude_24.html +++ /dev/null @@ -1,114 +0,0 @@ - - - - -AVRDUDE: A.1.1.2 Linux Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.1.2 Linux Installation

    - -

    On rpm based Linux systems (such as RedHat, SUSE, Mandrake, etc.), you -can build and install the rpm binaries directly from the tarball: -

    -
    -
    $ su - root
-# rpmbuild -tb avrdude-6.99-20211218.tar.gz
-# rpm -Uvh /usr/src/redhat/RPMS/i386/avrdude-6.99-20211218-1.i386.rpm
-
    - -

    Note that the path to the resulting rpm package, differs from system -to system. The above example is specific to RedHat. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_25.html b/docs/avrdude_25.html deleted file mode 100644 index 2d93f2a9..00000000 --- a/docs/avrdude_25.html +++ /dev/null @@ -1,116 +0,0 @@ - - - - -AVRDUDE: A.1.2 Unix Configuration Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.2 Unix Configuration Files

    - -

    When AVRDUDE is build using the default ‘--prefix’ configure -option, the default configuration file for a Unix system is located at -/usr/local/etc/avrdude.conf. This can be overridden by using the -‘-C’ command line option. Additionally, the user’s home directory -is searched for a file named .avrduderc, and if found, is used to -augment the system default configuration file. -

    - - - -
    A.1.2.1 FreeBSD Configuration Files   -
    A.1.2.2 Linux Configuration Files   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_26.html b/docs/avrdude_26.html deleted file mode 100644 index c00014ed..00000000 --- a/docs/avrdude_26.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - -AVRDUDE: A.1.2.1 FreeBSD Configuration Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.2.1 FreeBSD Configuration Files

    - -

    When AVRDUDE is installed using the FreeBSD ports system, the system -configuration file is always /usr/local/etc/avrdude.conf. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_27.html b/docs/avrdude_27.html deleted file mode 100644 index 3c1297d9..00000000 --- a/docs/avrdude_27.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - -AVRDUDE: A.1.2.2 Linux Configuration Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.2.2 Linux Configuration Files

    - -

    When AVRDUDE is installed using from an rpm package, the system -configuration file will be always be /etc/avrdude.conf. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_28.html b/docs/avrdude_28.html deleted file mode 100644 index c7ea1d12..00000000 --- a/docs/avrdude_28.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - -AVRDUDE: A.1.3 Unix Port Names - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.3 Unix Port Names

    - -

    The parallel and serial port device file names are system specific. -The following table lists the default names for a given system. -

    - - - - - -
    SystemDefault Parallel PortDefault Serial Port
    FreeBSD/dev/ppi0/dev/cuad0
    Linux/dev/parport0/dev/ttyS0
    Solaris/dev/printers/0/dev/term/a
    - -

    On FreeBSD systems, AVRDUDE uses the ppi(4) interface for -accessing the parallel port and the sio(4) driver for serial port -access. -

    -

    On Linux systems, AVRDUDE uses the ppdev interface for -accessing the parallel port and the tty driver for serial port -access. -

    -

    On Solaris systems, AVRDUDE uses the ecpp(7D) driver for -accessing the parallel port and the asy(7D) driver for serial port -access. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_29.html b/docs/avrdude_29.html deleted file mode 100644 index 3b387ae6..00000000 --- a/docs/avrdude_29.html +++ /dev/null @@ -1,111 +0,0 @@ - - - - -AVRDUDE: A.1.4 Unix Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.1.4 Unix Documentation

    - -

    AVRDUDE installs a manual page as well as info, HTML and PDF -documentation. The manual page is installed in -/usr/local/man/man1 area, while the HTML and PDF documentation -is installed in /usr/local/share/doc/avrdude directory. The -info manual is installed in /usr/local/info/avrdude.info. -

    -

    Note that these locations can be altered by various configure options -such as ‘--prefix’. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_3.html b/docs/avrdude_3.html deleted file mode 100644 index eac2ea9d..00000000 --- a/docs/avrdude_3.html +++ /dev/null @@ -1,1033 +0,0 @@ - - - - -AVRDUDE: 2.1 Option Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    2.1 Option Descriptions

    - -

    AVRDUDE is a command line tool, used as follows: -

    -
    -
    avrdude -p partno options …
-
    - -

    Command line options are used to control AVRDUDE’s behaviour. The -following options are recognized: -

    -
    -
    -p partno
    -

    This is the only mandatory option and it tells AVRDUDE what type of part -(MCU) that is connected to the programmer. The partno parameter -is the part’s id listed in the configuration file. Specify -p ? to list -all parts in the configuration file. If a part is unknown -to AVRDUDE, it means that there is no config file entry for that part, -but it can be added to the configuration file if you have the Atmel -datasheet so that you can enter the programming specifications. -Currently, the following MCU types are understood: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    uc3a0512AT32UC3A0512
    c128AT90CAN128
    c32AT90CAN32
    c64AT90CAN64
    pwm2AT90PWM2
    pwm216AT90PWM216
    pwm2bAT90PWM2B
    pwm3AT90PWM3
    pwm316AT90PWM316
    pwm3bAT90PWM3B
    1200AT90S1200 (****)
    2313AT90S2313
    2333AT90S2333
    2343AT90S2343 (*)
    4414AT90S4414
    4433AT90S4433
    4434AT90S4434
    8515AT90S8515
    8535AT90S8535
    usb1286AT90USB1286
    usb1287AT90USB1287
    usb162AT90USB162
    usb646AT90USB646
    usb647AT90USB647
    usb82AT90USB82
    m103ATmega103
    m128ATmega128
    m1280ATmega1280
    m1281ATmega1281
    m1284ATmega1284
    m1284pATmega1284P
    m1284rfr2ATmega1284RFR2
    m128aATmega128A
    m128rfa1ATmega128RFA1
    m128rfr2ATmega128RFR2
    m16ATmega16
    m1608ATmega1608
    m1609ATmega1609
    m161ATmega161
    m162ATmega162
    m163ATmega163
    m164aATmega164A
    m164pATmega164P
    m164paATmega164PA
    m165ATmega165
    m165aATmega165A
    m165pATmega165P
    m165paATmega165PA
    m168ATmega168
    m168aATmega168A
    m168pATmega168P
    m168paATmega168PA
    m168pbATmega168PB
    m169ATmega169
    m169aATmega169A
    m169pATmega169P
    m169paATmega169PA
    m16aATmega16A
    m16u2ATmega16U2
    m2560ATmega2560 (**)
    m2561ATmega2561 (**)
    m2564rfr2ATmega2564RFR2
    m256rfr2ATmega256RFR2
    m32ATmega32
    m3208ATmega3208
    m3209ATmega3209
    m324aATmega324A
    m324pATmega324P
    m324paATmega324PA
    m324pbATmega324PB
    m325ATmega325
    m3250ATmega3250
    m3250aATmega3250A
    m3250pATmega3250P
    m3250paATmega3250PA
    m325aATmega325A
    m325pATmega325P
    m325paATmega325PA
    m328ATmega328
    m328pATmega328P
    m328pbATmega328PB
    m329ATmega329
    m3290ATmega3290
    m3290aATmega3290A
    m3290pATmega3290P
    m3290paATmega3290PA
    m329aATmega329a
    m329pATmega329P
    m329paATmega329PA
    m32aATmega32A
    m32m1ATmega32M1
    m32u2ATmega32U2
    m32u4ATmega32U4
    m406ATMEGA406
    m48ATmega48
    m4808ATmega4808
    m4809ATmega4809
    m48aATmega48A
    m48pATmega48P
    m48paATmega48PA
    m48pbATmega48PB
    m64ATmega64
    m640ATmega640
    m644ATmega644
    m644aATmega644A
    m644pATmega644P
    m644paATmega644PA
    m644rfr2ATmega644RFR2
    m645ATmega645
    m6450ATmega6450
    m6450aATmega6450A
    m6450pATmega6450P
    m645aATmega645A
    m645pATmega645P
    m649ATmega649
    m6490ATmega6490
    m6490aATmega6490A
    m6490pATmega6490P
    m649aATmega649A
    m649pATmega649P
    m64aATmega64A
    m64m1ATmega64M1
    m64rfr2ATmega64RFR2
    m8ATmega8
    m808ATmega808
    m809ATmega809
    m8515ATmega8515
    m8535ATmega8535
    m88ATmega88
    m88aATmega88A
    m88pATmega88P
    m88paATmega88PA
    m88pbATmega88PB
    m8aATmega8A
    m8u2ATmega8U2
    t10ATtiny10
    t102ATtiny102
    t104ATtiny104
    t11ATtiny11 (***)
    t12ATtiny12
    t13ATtiny13
    t13aATtiny13A
    t15ATtiny15
    t1604ATtiny1604
    t1606ATtiny1606
    t1607ATtiny1607
    t1614ATtiny1614
    t1616ATtiny1616
    t1617ATtiny1617
    t1624ATtiny1624
    t1626ATtiny1626
    t1627ATtiny1627
    t1634ATtiny1634
    t1634rATtiny1634R
    t167ATtiny167
    t20ATtiny20
    t202ATtiny202
    t204ATtiny204
    t212ATtiny212
    t214ATtiny214
    t2313ATtiny2313
    t2313aATtiny2313A
    t24ATtiny24
    t24aATtiny24A
    t25ATtiny25
    t26ATtiny26
    t261ATtiny261
    t261aATtiny261A
    t28ATtiny28
    t3216ATtiny3216
    t3217ATtiny3217
    t3224ATtiny3224
    t3226ATtiny3226
    t3227ATtiny3227
    t4ATtiny4
    t40ATtiny40
    t402ATtiny402
    t404ATtiny404
    t406ATtiny406
    t412ATtiny412
    t414ATtiny414
    t416ATtiny416
    t417ATtiny417
    t424ATtiny424
    t426ATtiny426
    t427ATtiny427
    t4313ATtiny4313
    t43uATtiny43u
    t44ATtiny44
    t441ATtiny441
    t44aATtiny44A
    t45ATtiny45
    t461ATtiny461
    t461aATtiny461A
    t48ATtiny48
    t5ATtiny5
    t804ATtiny804
    t806ATtiny806
    t807ATtiny807
    t814ATtiny814
    t816ATtiny816
    t817ATtiny817
    t824ATtiny824
    t826ATtiny826
    t827ATtiny827
    t828ATtiny828
    t828rATtiny828R
    t84ATtiny84
    t841ATtiny841
    t84aATtiny84A
    t85ATtiny85
    t861ATtiny861
    t861aATtiny861A
    t87ATtiny87
    t88ATtiny88
    t9ATtiny9
    x128a1ATxmega128A1
    x128a1dATxmega128A1revD
    x128a1uATxmega128A1U
    x128a3ATxmega128A3
    x128a3uATxmega128A3U
    x128a4ATxmega128A4
    x128a4uATxmega128A4U
    x128b1ATxmega128B1
    x128b3ATxmega128B3
    x128c3ATxmega128C3
    x128d3ATxmega128D3
    x128d4ATxmega128D4
    x16a4ATxmega16A4
    x16a4uATxmega16A4U
    x16c4ATxmega16C4
    x16d4ATxmega16D4
    x16e5ATxmega16E5
    x192a1ATxmega192A1
    x192a3ATxmega192A3
    x192a3uATxmega192A3U
    x192c3ATxmega192C3
    x192d3ATxmega192D3
    x256a1ATxmega256A1
    x256a3ATxmega256A3
    x256a3bATxmega256A3B
    x256a3buATxmega256A3BU
    x256a3uATxmega256A3U
    x256c3ATxmega256C3
    x256d3ATxmega256D3
    x32a4ATxmega32A4
    x32a4uATxmega32A4U
    x32c4ATxmega32C4
    x32d4ATxmega32D4
    x32e5ATxmega32E5
    x384c3ATxmega384C3
    x384d3ATxmega384D3
    x64a1ATxmega64A1
    x64a1uATxmega64A1U
    x64a3ATxmega64A3
    x64a3uATxmega64A3U
    x64a4ATxmega64A4
    x64a4uATxmega64A4U
    x64b1ATxmega64B1
    x64b3ATxmega64B3
    x64c3ATxmega64C3
    x64d3ATxmega64D3
    x64d4ATxmega64D4
    x8e5ATxmega8E5
    avr128da28AVR128DA28
    avr128da32AVR128DA32
    avr128da48AVR128DA48
    avr128da64AVR128DA64
    avr128db28AVR128DB28
    avr128db32AVR128DB32
    avr128db48AVR128DB48
    avr128db64AVR128DB64
    avr16dd14AVR16DD14
    avr16dd20AVR16DD20
    avr16dd28AVR16DD28
    avr16dd32AVR16DD32
    avr16ea28AVR16EA28
    avr16ea32AVR16EA32
    avr16ea48AVR16EA48
    avr32da28AVR32DA28
    avr32da32AVR32DA32
    avr32da48AVR32DA48
    avr32db28AVR32DB28
    avr32db32AVR32DB32
    avr32db48AVR32DB48
    avr32dd14AVR32DD14
    avr32dd20AVR32DD20
    avr32dd28AVR32DD28
    avr32dd32AVR32DD32
    avr32ea28AVR32EA28
    avr32ea32AVR32EA32
    avr32ea48AVR32EA48
    avr64da28AVR64DA28
    avr64da32AVR64DA32
    avr64da48AVR64DA48
    avr64da64AVR64DA64
    avr64db28AVR64DB28
    avr64db32AVR64DB32
    avr64db48AVR64DB48
    avr64db64AVR64DB64
    avr64dd14AVR64DD14
    avr64dd20AVR64DD20
    avr64dd28AVR64DD28
    avr64dd32AVR64DD32
    avr64ea28AVR64EA28
    avr64ea32AVR64EA32
    avr64ea48AVR64EA48
    avr8ea28AVR8EA28
    avr8ea32AVR8EA32
    ucr2deprecated,
    lgt8f168pLGT8F168P
    lgt8f328pLGT8F328P
    lgt8f88pLGT8F88P
    - -

    (*) The AT90S2323 and ATtiny22 use the same algorithm. -

    -

    (**) Flash addressing above 128 KB is not supported by all -programming hardware. Known to work are jtag2, stk500v2, -and bit-bang programmers. -

    -

    (***) -The ATtiny11 can only be -programmed in high-voltage serial mode. -

    -

    (****) -The ISP programming protocol of the AT90S1200 differs in subtle ways -from that of other AVRs. Thus, not all programmers support this -device. Known to work are all direct bitbang programmers, and all -programmers talking the STK500v2 protocol. -

    -
    -
    -b baudrate
    -

    Override the RS-232 connection baud rate specified in the respective -programmer’s entry of the configuration file. -

    -
    -
    -B bitclock
    -

    Specify the bit clock period for the JTAG interface or the ISP clock (JTAG ICE only). -The value is a floating-point number in microseconds. -Alternatively, the value might be suffixed with "Hz", "kHz", or "MHz", -in order to specify the bit clock frequency, rather than a period. -The default value of the JTAG ICE results in about 1 microsecond bit -clock period, suitable for target MCUs running at 4 MHz clock and -above. -Unlike certain parameters in the STK500, the JTAG ICE resets all its -parameters to default values when the programming software signs -off from the ICE, so for MCUs running at lower clock speeds, this -parameter must be specified on the command-line. -It can also be set in the configuration file by using the ’default_bitclock’ -keyword. -

    -
    -
    -c programmer-id
    -

    Specify the programmer to be used. AVRDUDE knows about several common -programmers. Use this option to specify which one to use. The -programmer-id parameter is the programmer’s id listed in the -configuration file. Specify -c ? to list all programmers in the -configuration file. If you have a programmer that is unknown to -AVRDUDE, and the programmer is controlled via the PC parallel port, -there’s a good chance that it can be easily added to the configuration -file without any code changes to AVRDUDE. Simply copy an existing entry -and change the pin definitions to match that of the unknown programmer. -Currently, the following programmer ids are understood and supported: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    2232HIOFT2232H based generic programmer
    4232hFT4232H based generic programmer
    arduinoArduino
    arduino-ft232rArduino: FT232R connected to ISP
    arduinoispArduino ISP Programmer
    arduinoisporgArduino ISP Programmer
    atmeliceAtmel-ICE (ARM/AVR) in JTAG mode
    atmelice_dwAtmel-ICE (ARM/AVR) in debugWIRE mode
    atmelice_ispAtmel-ICE (ARM/AVR) in ISP mode
    atmelice_pdiAtmel-ICE (ARM/AVR) in PDI mode
    atmelice_updiAtmel-ICE (ARM/AVR) in UPDI mode
    avr109Atmel AppNote AVR109 Boot Loader
    avr910Atmel Low Cost Serial Programmer
    avr911Atmel AppNote AVR911 AVROSP
    avrftdiFT2232D based generic programmer
    avrispAtmel AVR ISP
    avrisp2Atmel AVR ISP mkII
    avrispmkIIAtmel AVR ISP mkII
    avrispv2Atmel AVR ISP V2
    buspirateThe Bus Pirate
    buspirate_bbThe Bus Pirate (bitbang interface, supports TPI)
    butterflyAtmel Butterfly Development Board
    butterfly_mkMikrokopter.de Butterfly
    bwmegaBitWizard ftdi_atmega builtin programmer
    c232hmC232HM cable from FTDI
    c2n232iserial port banging, reset=dtr sck=!rts mosi=!txd miso=!cts
    dasaserial port banging, reset=rts sck=dtr mosi=txd miso=cts
    dasa3serial port banging, reset=!dtr sck=rts mosi=txd miso=cts
    diecimilaalias for arduino-ft232r
    dragon_dwAtmel AVR Dragon in debugWire mode
    dragon_hvspAtmel AVR Dragon in HVSP mode
    dragon_ispAtmel AVR Dragon in ISP mode
    dragon_jtagAtmel AVR Dragon in JTAG mode
    dragon_pdiAtmel AVR Dragon in PDI mode
    dragon_ppAtmel AVR Dragon in PP mode
    ehajo-ispavr-isp-programmer from eHaJo, http://www.eHaJo.de
    flip1FLIP USB DFU protocol version 1 (doc7618)
    flip2FLIP USB DFU protocol version 2 (AVR4023)
    ft232hFT232H in MPSSE mode
    ft232rFT232R Synchronous BitBang
    ft245rFT245R Synchronous BitBang
    iseavrprogUSBtiny-based USB programmer, https://github.com/IowaScaledEngineering/ckt-avrp
    jtag1Atmel JTAG ICE (mkI)
    jtag1slowAtmel JTAG ICE (mkI)
    jtag2Atmel JTAG ICE mkII
    jtag2avr32Atmel JTAG ICE mkII im AVR32 mode
    jtag2dwAtmel JTAG ICE mkII in debugWire mode
    jtag2fastAtmel JTAG ICE mkII
    jtag2ispAtmel JTAG ICE mkII in ISP mode
    jtag2pdiAtmel JTAG ICE mkII PDI mode
    jtag2slowAtmel JTAG ICE mkII
    jtag2updiJTAGv2 to UPDI bridge
    jtag3Atmel AVR JTAGICE3 in JTAG mode
    jtag3dwAtmel AVR JTAGICE3 in debugWIRE mode
    jtag3ispAtmel AVR JTAGICE3 in ISP mode
    jtag3pdiAtmel AVR JTAGICE3 in PDI mode
    jtag3updiAtmel AVR JTAGICE3 in UPDI mode
    jtagkeyAmontec JTAGKey, JTAGKey-Tiny and JTAGKey2
    jtagmkIAtmel JTAG ICE (mkI)
    jtagmkIIAtmel JTAG ICE mkII
    jtagmkII_avr32Atmel JTAG ICE mkII im AVR32 mode
    lm3s811Luminary Micro LM3S811 Eval Board (Rev. A)
    mib510Crossbow MIB510 programming board
    micronucleusMicronucleus Bootloader
    mkbutterflyMikrokopter.de Butterfly
    nibobeeNIBObee
    o-linkO-Link, OpenJTAG from www.100ask.net
    openmokoOpenmoko debug board (v3)
    pavrJason Kyle’s pAVR Serial Programmer
    pickit2MicroChip’s PICkit2 Programmer
    pickit4_ispMPLAB(R) PICkit 4 in ISP mode
    pickit4_pdiMPLAB(R) PICkit 4 in PDI mode
    pickit4_updiMPLAB(R) PICkit 4 in UPDI mode
    pkobn_updiCuriosity nano (nEDBG) in UPDI mode
    ponyserdesign ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts
    powerdebuggerAtmel PowerDebugger (ARM/AVR) in JTAG mode
    powerdebugger_dwAtmel PowerDebugger (ARM/AVR) in debugWire mode
    powerdebugger_ispAtmel PowerDebugger (ARM/AVR) in ISP mode
    powerdebugger_pdiAtmel PowerDebugger (ARM/AVR) in PDI mode
    powerdebugger_updiAtmel PowerDebugger (ARM/AVR) in UPDI mode
    serialupdiSerialUPDI
    siprogLancos SI-Prog <http://www.lancos.com/siprogsch.html>
    snap_ispMPLAB(R) SNAP in ISP mode
    snap_pdiMPLAB(R) SNAP in PDI mode
    snap_updiMPLAB(R) SNAP in UPDI mode
    stk500Atmel STK500
    stk500hvspAtmel STK500 V2 in high-voltage serial programming mode
    stk500ppAtmel STK500 V2 in parallel programming mode
    stk500v1Atmel STK500 Version 1.x firmware
    stk500v2Atmel STK500 Version 2.x firmware
    stk600Atmel STK600
    stk600hvspAtmel STK600 in high-voltage serial programming mode
    stk600ppAtmel STK600 in parallel programming mode
    tc2030Tag-Connect TC2030
    teensyTeensy Bootloader
    ttl232rFTDI TTL232R-5V with ICSP adapter
    tumpaTIAO USB Multi-Protocol Adapter
    um232hUM232H module from FTDI
    uncompatinouncompatino with all pairs of pins shorted
    usbaspUSBasp, http://www.fischl.de/usbasp/
    usbasp-cloneAny usbasp clone with correct VID/PID
    usbtinyUSBtiny simple USB programmer, https://learn.adafruit.com/usbtinyisp
    wiringWiring
    xbeeXBee Series 2 Over-The-Air (XBeeBoot)
    xplainedminiAtmel AVR XplainedMini in ISP mode
    xplainedmini_dwAtmel AVR XplainedMini in debugWIRE mode
    xplainedmini_updiAtmel AVR XplainedMini in UPDI mode
    xplainedproAtmel AVR XplainedPro in JTAG mode
    xplainedpro_updiAtmel AVR XplainedPro in UPDI mode
    - - - -
    -
    -C config-file
    -

    Use the specified config file for configuration data. This file -contains all programmer and part definitions that AVRDUDE knows about. -If not specified, AVRDUDE looks for the configuration file in the following -two locations: -

    -
      -
    1. -<directory from which application loaded>/../etc/avrdude.conf - -
    2. -<directory from which application loaded>/avrdude.conf - -
    - -

    If not found there, the lookup procedure becomes platform dependent. On FreeBSD -and Linux, AVRDUDE looks at /usr/local/etc/avrdude.conf. See Appendix A -for the method of searching on Windows. -

    -

    If config-file is written as +filename -then this file is read after the system wide and user configuration -files. This can be used to add entries to the configuration -without patching your system wide configuration file. It can be used -several times, the files are read in same order as given on the command -line. -

    - -
    -
    -D
    -

    Disable auto erase for flash. When the -U option with flash memory is -specified, avrdude will perform a chip erase before starting any of the -programming operations, since it generally is a mistake to program the flash -without performing an erase first. This option disables that. -Auto erase is not used for ATxmega devices as these devices can -use page erase before writing each page so no explicit chip erase -is required. -Note however that any page not affected by the current operation -will retain its previous contents. -

    -
    -
    -e
    -

    Causes a chip erase to be executed. This will reset the contents of the -flash ROM and EEPROM to the value ‘0xff’, and clear all lock bits. -Except for ATxmega devices which can use page erase, -it is basically a -prerequisite command before the flash ROM can be reprogrammed again. -The only exception would be if the new contents would exclusively cause -bits to be programmed from the value ‘1’ to ‘0’. Note that in order -to reprogram EERPOM cells, no explicit prior chip erase is required -since the MCU provides an auto-erase cycle in that case before -programming the cell. -

    - -
    -
    -E exitspec[,…]
    -

    By default, AVRDUDE leaves the parallel port in the same state at exit -as it has been found at startup. This option modifies the state of the -‘/RESET’ and ‘Vcc’ lines the parallel port is left at, according to -the exitspec arguments provided, as follows: -

    -
    -
    reset
    -

    The ‘/RESET’ signal will be left activated at program exit, that is it -will be held low, in order to keep the MCU in reset state afterwards. -Note in particular that the programming algorithm for the AT90S1200 -device mandates that the ‘/RESET’ signal is active before powering up -the MCU, so in case an external power supply is used for this MCU type, -a previous invocation of AVRDUDE with this option specified is one of -the possible ways to guarantee this condition. -

    -
    -
    noreset
    -

    The ‘/RESET’ line will be deactivated at program exit, thus allowing the -MCU target program to run while the programming hardware remains -connected. -

    -
    -
    vcc
    -

    This option will leave those parallel port pins active (i. e. high) that -can be used to supply ‘Vcc’ power to the MCU. -

    -
    -
    novcc
    -

    This option will pull the ‘Vcc’ pins of the parallel port down at -program exit. -

    -
    -
    d_high
    -

    This option will leave the 8 data pins on the parallel port active -(i. e. high). -

    -
    -
    d_low
    -

    This option will leave the 8 data pins on the parallel port inactive -(i. e. low). -

    -
    -
    - -

    Multiple exitspec arguments can be separated with commas. -

    - -
    -
    -F
    -

    Normally, AVRDUDE tries to verify that the device signature read from -the part is reasonable before continuing. Since it can happen from time -to time that a device has a broken (erased or overwritten) device -signature but is otherwise operating normally, this options is provided -to override the check. -Also, for programmers like the Atmel STK500 and STK600 which can -adjust parameters local to the programming tool (independent of an -actual connection to a target controller), this option can be used -together with ‘-t’ to continue in terminal mode. -

    -
    -
    -i delay
    -

    For bitbang-type programmers, delay for approximately -delay -microseconds between each bit state change. -If the host system is very fast, or the target runs off a slow clock -(like a 32 kHz crystal, or the 128 kHz internal RC oscillator), this -can become necessary to satisfy the requirement that the ISP clock -frequency must not be higher than 1/4 of the CPU clock frequency. -This is implemented as a spin-loop delay to allow even for very -short delays. -On Unix-style operating systems, the spin loop is initially calibrated -against a system timer, so the number of microseconds might be rather -realistic, assuming a constant system load while AVRDUDE is running. -On Win32 operating systems, a preconfigured number of cycles per -microsecond is assumed that might be off a bit for very fast or very -slow machines. -

    -
    -
    -l logfile
    -

    Use logfile rather than stderr for diagnostics output. -Note that initial diagnostic messages (during option parsing) are still -written to stderr anyway. -

    -
    -
    -n
    -

    No-write - disables actually writing data to the MCU (useful for -debugging AVRDUDE). -

    -
    -
    -O
    -

    Perform a RC oscillator run-time calibration according to Atmel -application note AVR053. -This is only supported on the STK500v2, AVRISP mkII, and JTAG ICE mkII -hardware. -Note that the result will be stored in the EEPROM cell at address 0. -

    -
    -
    -P port
    -

    Use port to identify the device to which the programmer is attached. -Normally, the default parallel port is used, but if the programmer type -normally connects to the serial port, the default serial port will be -used. See Appendix A, Platform Dependent Information, to find out the -default port names for your platform. If you need to use a different -parallel or serial port, use this option to specify the alternate port name. -

    -

    On Win32 operating systems, the parallel ports are referred to as lpt1 -through lpt3, referring to the addresses 0x378, 0x278, and 0x3BC, -respectively. If the parallel port can be accessed through a different -address, this address can be specified directly, using the common C -language notation (i. e., hexadecimal values are prefixed by 0x). -

    -

    For the JTAG ICE mkII, if AVRDUDE has been built with libusb support, -port may alternatively be specified as -usb[:serialno]. In that case, the JTAG ICE mkII will be -looked up on USB. If serialno is also specified, it will be -matched against the serial number read from any JTAG ICE mkII found on -USB. The match is done after stripping any existing colons from the -given serial number, and right-to-left, so only the least significant -bytes from the serial number need to be given. -For a trick how to find out the serial numbers of all JTAG ICEs -attached to USB, see Example Command Line Invocations. -

    -

    As the AVRISP mkII device can only be talked to over USB, the very -same method of specifying the port is required there. -

    -

    For the USB programmer "AVR-Doper" running in HID mode, the port must -be specified as avrdoper. Libhidapi support is required on Unix -and Mac OS but not on Windows. For more information about AVR-Doper see -http://www.obdev.at/avrusb/avrdoper.html. -

    -

    For the USBtinyISP, which is a simplistic device not implementing -serial numbers, multiple devices can be distinguished by their -location in the USB hierarchy. -See the respective -See section Troubleshooting entry for examples. -

    -

    For the XBee programmer the target MCU is to be programmed wirelessly -over a ZigBee mesh using the XBeeBoot bootloader. The ZigBee 64-bit -address for the target MCU’s own XBee device must be supplied as a -16-character hexadecimal value as a port prefix, followed by the -@ character, and the serial device to connect to a second -directly contactable XBee device associated with the same mesh (with -a default baud rate of 9600). This may look similar to: -0013a20000000001dev/tty.serial. -

    -

    For diagnostic purposes, if the target MCU with an XBeeBoot -bootloader is connected directly to the serial port, the -64-bit address field can be omitted. In this mode the -default baud rate will be 19200. -

    -

    For programmers that attach to a serial port using some kind of -higher level protocol (as opposed to bit-bang style programmers), -port can be specified as net:host:port. -In this case, instead of trying to open a local device, a TCP -network connection to (TCP) port on host -is established. -Square brackets may be placed around host to improve -readability for numeric IPv6 addresses (e.g. -net:[2001:db8::42]:1337). -The remote endpoint is assumed to be a terminal or console server -that connects the network stream to a local serial port where the -actual programmer has been attached to. -The port is assumed to be properly configured, for example using a -transparent 8-bit data connection without parity at 115200 Baud -for a STK500. -

    -

    Note: The ability to handle IPv6 hostnames and addresses is limited to -Posix systems (by now). -

    -
    -
    -q
    -

    Disable (or quell) output of the progress bar while reading or writing -to the device. Specify it a second time for even quieter operation. -

    -
    -
    -t
    -

    Tells AVRDUDE to enter the interactive “terminal” mode instead of up- -or downloading files. See below for a detailed description of the -terminal mode. -

    -
    -
    -U memtype:op:filename[:format]
    -

    Perform a memory operation. -Multiple ‘-U’ options can be specified in order to operate on -multiple memories on the same command-line invocation. The -memtype field specifies the memory type to operate on. Use -the ‘-v’ option on the command line or the part command from -terminal mode to display all the memory types supported by a particular -device. -Typically, a device’s memory configuration at least contains -the memory types -flash -and -eeprom. -All memory types currently known are: -

    -
    calibration
    -

    One or more bytes of RC oscillator calibration data. -

    -
    eeprom
    -

    The EEPROM of the device. -

    -
    efuse
    -

    The extended fuse byte. -

    -
    flash
    -

    The flash ROM of the device. -

    -
    fuse
    -

    The fuse byte in devices that have only a single fuse byte. -

    -
    hfuse
    -

    The high fuse byte. -

    -
    lfuse
    -

    The low fuse byte. -

    -
    lock
    -

    The lock byte. -

    -
    signature
    -

    The three device signature bytes (device ID). -

    -
    fuseN
    -

    The fuse bytes of ATxmega devices, N is an integer number -for each fuse supported by the device. -

    -
    application
    -

    The application flash area of ATxmega devices. -

    -
    apptable
    -

    The application table flash area of ATxmega devices. -

    -
    boot
    -

    The boot flash area of ATxmega devices. -

    -
    prodsig
    -

    The production signature (calibration) area of ATxmega devices. -

    -
    usersig
    -

    The user signature area of ATxmega devices. -

    -
    - -

    The op field specifies what operation to perform: -

    -
    -
    r
    -

    read the specified device memory and write to the specified file -

    -
    -
    w
    -

    read the specified file and write it to the specified device memory -

    -
    -
    v
    -

    read the specified device memory and the specified file and perform a verify operation -

    -
    -
    - -

    The filename field indicates the name of the file to read or -write. The format field is optional and contains the format of -the file to read or write. Possible values are: -

    -
    -
    i
    -

    Intel Hex -

    -
    -
    s
    -

    Motorola S-record -

    -
    -
    r
    -

    raw binary; little-endian byte order, in the case of the flash ROM data -

    -
    -
    e
    -

    ELF (Executable and Linkable Format), the final output file from the -linker; currently only accepted as an input file -

    -
    -
    m
    -

    immediate mode; actual byte values specified on the command line, -separated by commas or spaces in place of the filename field of -the ‘-U’ option. This is useful -for programming fuse bytes without having to create a single-byte file -or enter terminal mode. If the number specified begins with 0x, -it is treated as a hex value. If the number otherwise begins with a -leading zero (0) it is treated as octal. Otherwise, the value is -treated as decimal. -

    -
    -
    a
    -

    auto detect; valid for input only, and only if the input is not provided -at stdin. -

    -
    -
    d
    -

    decimal; this and the following formats are only valid on output. -They generate one line of output for the respective memory section, -forming a comma-separated list of the values. -This can be particularly useful for subsequent processing, like for -fuse bit settings. -

    -
    -
    h
    -

    hexadecimal; each value will get the string 0x prepended. -

    -
    -
    o
    -

    octal; each value will get a 0 -prepended unless it is less than 8 in which case it gets no prefix. -

    -
    -
    b
    -

    binary; each value will get the string 0b prepended. -

    -
    -
    - -

    The default is to use auto detection for input files, and raw binary -format for output files. -

    -

    Note that if filename contains a colon, the format field is -no longer optional since the filename part following the colon would -otherwise be misinterpreted as format. -

    -

    When reading any kind of flash memory area (including the various sub-areas -in Xmega devices), the resulting output file will be truncated to not contain -trailing 0xFF bytes which indicate unprogrammed (erased) memory. -Thus, if the entire memory is unprogrammed, this will result in an output -file that has no contents at all. -

    -

    As an abbreviation, the form -U filename -is equivalent to specifying --U flash:w:filename:a. -This will only work if filename does not have a colon in it. -

    -
    -
    -v
    -

    Enable verbose output. -More -v options increase verbosity level. -

    -
    -
    -V
    -

    Disable automatic verify check when uploading data. -

    -
    -
    -x extended_param
    -

    Pass extended_param to the chosen programmer implementation as -an extended parameter. The interpretation of the extended parameter -depends on the programmer itself. See below for a list of programmers -accepting extended parameters. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_30.html b/docs/avrdude_30.html deleted file mode 100644 index 89b9c128..00000000 --- a/docs/avrdude_30.html +++ /dev/null @@ -1,113 +0,0 @@ - - - - -AVRDUDE: A.2 Windows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2 Windows

    - - - - - - -
    A.2.1 Installation   -
    A.2.2 Configuration Files   -
    A.2.3 Port Names   -
    A.2.4 Documentation   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_31.html b/docs/avrdude_31.html deleted file mode 100644 index 9a314ed7..00000000 --- a/docs/avrdude_31.html +++ /dev/null @@ -1,131 +0,0 @@ - - - - -AVRDUDE: A.2.1 Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.1 Installation

    - -

    A Windows executable of avrdude is included in WinAVR which can be found at -http://sourceforge.net/projects/winavr. WinAVR is a suite of executable, -open source software development tools for the AVR for the Windows platform. -

    -

    There are two options to build avrdude from source under Windows. -The first one is to use Cygwin (http://www.cygwin.com/). -

    -

    To build and install from the source tarball for Windows (using Cygwin): -

    -
    -
    $ set PREFIX=<your install directory path>
-$ export PREFIX
-$ gunzip -c avrdude-6.99-20211218.tar.gz | tar xf -
-$ cd avrdude-6.99-20211218
-$ ./configure LDFLAGS="-static" --prefix=$PREFIX --datadir=$PREFIX 
---sysconfdir=$PREFIX/bin --enable-versioned-doc=no
-$ make
-$ make install
-
    - -

    Note that recent versions of Cygwin (starting with 1.7) removed the -MinGW support from the compiler that is needed in order to build a -native Win32 API binary that does not require to install the Cygwin -library cygwin1.dll at run-time. Either try using an older -compiler version that still supports MinGW builds, or use MinGW -(http://www.mingw.org/) directly. -

    - - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_32.html b/docs/avrdude_32.html deleted file mode 100644 index 0ca29042..00000000 --- a/docs/avrdude_32.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - -AVRDUDE: A.2.2 Configuration Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.2 Configuration Files

    - - - - -
    A.2.2.1 Configuration file names   -
    A.2.2.2 How AVRDUDE finds the configuration files.   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_33.html b/docs/avrdude_33.html deleted file mode 100644 index 91197406..00000000 --- a/docs/avrdude_33.html +++ /dev/null @@ -1,106 +0,0 @@ - - - - -AVRDUDE: A.2.2.1 Configuration file names - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.2.1 Configuration file names

    - -

    AVRDUDE on Windows looks for a system configuration file name of -avrdude.conf and looks for a user override configuration file of -avrdude.rc. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_34.html b/docs/avrdude_34.html deleted file mode 100644 index 85dc94b2..00000000 --- a/docs/avrdude_34.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - -AVRDUDE: A.2.2.2 How AVRDUDE finds the configuration files. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.2.2 How AVRDUDE finds the configuration files.

    - -

    AVRDUDE on Windows has a different way of searching for the system and -user configuration files. Below is the search method for locating the -configuration files: -

    -
      -
    1. -Only for the system configuration file: -<directory from which application loaded>/../etc/avrdude.conf - -
    2. -The directory from which the application loaded. - -
    3. -The current directory. - -
    4. -The Windows system directory. On Windows NT, the name of this directory -is SYSTEM32. - -
    5. -Windows NT: The 16-bit Windows system directory. The name of this -directory is SYSTEM. - -
    6. -The Windows directory. - -
    7. -The directories that are listed in the PATH environment variable. - -
    - - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_35.html b/docs/avrdude_35.html deleted file mode 100644 index 2a1bbcbc..00000000 --- a/docs/avrdude_35.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - -AVRDUDE: A.2.3 Port Names - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.3 Port Names

    - - - - -
    A.2.3.1 Serial Ports   -
    A.2.3.2 Parallel Ports   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_36.html b/docs/avrdude_36.html deleted file mode 100644 index b681fbd9..00000000 --- a/docs/avrdude_36.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - -AVRDUDE: A.2.3.1 Serial Ports - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.3.1 Serial Ports

    - -

    When you select a serial port (i.e. when using an STK500) use the -Windows serial port device names such as: com1, com2, etc. -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_37.html b/docs/avrdude_37.html deleted file mode 100644 index f543a6f7..00000000 --- a/docs/avrdude_37.html +++ /dev/null @@ -1,130 +0,0 @@ - - - - -AVRDUDE: A.2.3.2 Parallel Ports - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.3.2 Parallel Ports

    - -

    AVRDUDE will accept 3 Windows parallel port names: lpt1, lpt2, or -lpt3. Each of these names corresponds to a fixed parallel port base -address: -

    -
    -
    lpt1
    -

    0x378 -

    -
    -
    lpt2
    -

    0x278 -

    -
    -
    lpt3
    -

    0x3BC -

    -
    -
    - -

    On your desktop PC, lpt1 will be the most common choice. If you are -using a laptop, you might have to use lpt3 instead of lpt1. Select the -name of the port the corresponds to the base address of the parallel -port that you want. -

    -

    If the parallel port can be accessed through a different -address, this address can be specified directly, using the common C -language notation (i. e., hexadecimal values are prefixed by 0x). -

    -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_38.html b/docs/avrdude_38.html deleted file mode 100644 index 1b637812..00000000 --- a/docs/avrdude_38.html +++ /dev/null @@ -1,112 +0,0 @@ - - - - -AVRDUDE: A.2.4 Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    A.2.4 Documentation

    - -

    AVRDUDE installs a manual page as well as info, HTML and PDF -documentation. The manual page is installed in -/usr/local/man/man1 area, while the HTML and PDF documentation -is installed in /usr/local/share/doc/avrdude directory. The -info manual is installed in /usr/local/info/avrdude.info. -

    -

    Note that these locations can be altered by various configure options -such as ‘--prefix’ and ‘--datadir’. -

    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_39.html b/docs/avrdude_39.html deleted file mode 100644 index 101e8d2e..00000000 --- a/docs/avrdude_39.html +++ /dev/null @@ -1,425 +0,0 @@ - - - - -AVRDUDE: Appendix B Troubleshooting - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    Appendix B Troubleshooting

    - -

    In general, please report any bugs encountered via -
    -https://github.com/avrdudes/avrdude/issues. -

    - -
      -
    • -Problem: I’m using a serial programmer under Windows and get the following -error: - -

      avrdude: serial_open(): can't set attributes for device "com1", -

      -

      Solution: This problem seems to appear with certain versions of Cygwin. Specifying -"/dev/com1" instead of "com1" should help. -

      - -
    • -Problem: I’m using Linux and my AVR910 programmer is really slow. - -

      Solution (short): setserial port low_latency -

      -

      Solution (long): -There are two problems here. First, the system may wait some time before it -passes data from the serial port to the program. Under Linux the following -command works around this (you may need root privileges for this). -

      -

      setserial port low_latency -

      -

      Secondly, the serial interface chip may delay the interrupt for some time. -This behaviour can be changed by setting the FIFO-threshold to one. Under Linux this -can only be done by changing the kernel source in drivers/char/serial.c. -Search the file for UART_FCR_TRIGGER_8 and replace it with UART_FCR_TRIGGER_1. Note that overall performance might suffer if there -is high throughput on serial lines. Also note that you are modifying the kernel at -your own risk. -

      - -
    • -Problem: I’m not using Linux and my AVR910 programmer is really slow. - -

      Solutions: The reasons for this are the same as above. -If you know how to work around this on your OS, please let us know. -

      -
    • -Problem: Updating the flash ROM from terminal mode does not work with the -JTAG ICEs. - -

      Solution: None at this time. Currently, the JTAG ICE code cannot -write to the flash ROM one byte at a time. -

      -
    • -Problem: Page-mode programming the EEPROM (using the -U option) does -not erase EEPROM cells before writing, and thus cannot overwrite any -previous value != 0xff. - -

      Solution: None. This is an inherent feature of the way JTAG EEPROM -programming works, and is documented that way in the Atmel AVR -datasheets. -In order to successfully program the EEPROM that way, a prior chip -erase (with the EESAVE fuse unprogrammed) is required. -This also applies to the STK500 and STK600 in high-voltage programming mode. -

      -
    • -Problem: How do I turn off the DWEN fuse? - -

      Solution: If the DWEN (debugWire enable) fuse is activated, -the /RESET pin is not functional anymore, so normal ISP -communication cannot be established. -There are two options to deactivate that fuse again: high-voltage -programming, or getting the JTAG ICE mkII talk debugWire, and -prepare the target AVR to accept normal ISP communication again. -

      -

      The first option requires a programmer that is capable of high-voltage -programming (either serial or parallel, depending on the AVR device), -for example the STK500. In high-voltage programming mode, the -/RESET pin is activated initially using a 12 V pulse (thus the -name high voltage), so the target AVR can subsequently be -reprogrammed, and the DWEN fuse can be cleared. Typically, this -operation cannot be performed while the AVR is located in the target -circuit though. -

      -

      The second option requires a JTAG ICE mkII that can talk the debugWire -protocol. The ICE needs to be connected to the target using the -JTAG-to-ISP adapter, so the JTAG ICE mkII can be used as a debugWire -initiator as well as an ISP programmer. AVRDUDE will then be activated -using the jtag2isp programmer type. The initial ISP -communication attempt will fail, but AVRDUDE then tries to initiate a -debugWire reset. When successful, this will leave the target AVR in a -state where it can accept standard ISP communication. The ICE is then -signed off (which will make it signing off from the USB as well), so -AVRDUDE has to be called again afterwards. This time, standard ISP -communication can work, so the DWEN fuse can be cleared. -

      -

      The pin mapping for the JTAG-to-ISP adapter is: -

      - - - - - - - - -
      JTAG pinISP pin
      13
      26
      31
      42
      65
      94
      - -
    • -Problem: Multiple USBasp or USBtinyISP programmers connected simultaneously are not -found. - -

      Solution: The USBtinyISP code supports distinguishing multiple -programmers based on their bus:device connection tuple that describes -their place in the USB hierarchy on a specific host. This tuple can -be added to the -P usb option, similar to adding a serial number -on other USB-based programmers. -

      -

      The actual naming convention for the bus and device names is -operating-system dependent; AVRDUDE will print out what it found -on the bus when running it with (at least) one -v option. -By specifying a string that cannot match any existing device -(for example, -P usb:xxx), the scan will list all possible -candidate devices found on the bus. -

      -

      Examples: -

      -
      avrdude -c usbtiny -p atmega8 -P usb:003:025 (Linux)
-avrdude -c usbtiny -p atmega8 -P usb:/dev/usb:/dev/ugen1.3 (FreeBSD 8+)
-avrdude -c usbtiny -p atmega8 \
-  -P usb:bus-0:\\.\libusb0-0001--0x1781-0x0c9f (Windows)
-
      - -
    • -Problem: I cannot do … when the target is in debugWire mode. - -

      Solution: debugWire mode imposes several limitations. -

      -

      The debugWire protocol is Atmel’s proprietary one-wire (plus ground) -protocol to allow an in-circuit emulation of the smaller AVR devices, -using the /RESET line. -DebugWire mode is initiated by activating the DWEN -fuse, and then power-cycling the target. -While this mode is mainly intended for debugging/emulation, it -also offers limited programming capabilities. -Effectively, the only memory areas that can be read or programmed -in this mode are flash ROM and EEPROM. -It is also possible to read out the signature. -All other memory areas cannot be accessed. -There is no -chip erase -functionality in debugWire mode; instead, while reprogramming the -flash ROM, each flash ROM page is erased right before updating it. -This is done transparently by the JTAG ICE mkII (or AVR Dragon). -The only way back from debugWire mode is to initiate a special -sequence of commands to the JTAG ICE mkII (or AVR Dragon), so the -debugWire mode will be temporarily disabled, and the target can -be accessed using normal ISP programming. -This sequence is automatically initiated by using the JTAG ICE mkII -or AVR Dragon in ISP mode, when they detect that ISP mode cannot be -entered. -

      -
    • -Problem: I want to use my JTAG ICE mkII to program an -Xmega device through PDI. The documentation tells me to use the -XMEGA PDI adapter for JTAGICE mkII that is supposed to ship -with the kit, yet I don’t have it. - -

      Solution: Use the following pin mapping: -

      - - - - - - - - - - - - - -
      JTAGICETargetSquid cab-PDI
      mkII probepinsle colorsheader
      1 (TCK)Black
      2 (GND)GNDWhite6
      3 (TDO)Grey
      4 (VTref)VTrefPurple2
      5 (TMS)Blue
      6 (nSRST)PDI_CLKGreen5
      7 (N.C.)Yellow
      8 (nTRST)Orange
      9 (TDI)PDI_DATARed1
      10 (GND)Brown
      - -
    • -Problem: I want to use my AVR Dragon to program an -Xmega device through PDI. - -

      Solution: Use the 6 pin ISP header on the Dragon and the following pin mapping: -

      - - - - - - - - - -
      DragonTarget
      ISP Headerpins
      1 (MISO)PDI_DATA
      2 (VCC)VCC
      3 (SCK)
      4 (MOSI)
      5 (RESET)PDI_CLK / RST
      6 (GND)GND
      - -
    • -Problem: I want to use my AVRISP mkII to program an -ATtiny4/5/9/10 device through TPI. How to connect the pins? - -

      Solution: Use the following pin mapping: -

      - - - - - - - - - -
      AVRISPTargetATtiny
      connectorpinspin #
      1 (MISO)TPIDATA1
      2 (VTref)Vcc5
      3 (SCK)TPICLK3
      4 (MOSI)
      5 (RESET)/RESET6
      6 (GND)GND2
      - -
    • -Problem: I want to program an ATtiny4/5/9/10 device using a serial/parallel -bitbang programmer. How to connect the pins? - -

      Solution: Since TPI has only 1 pin for bi-directional data transfer, both -MISO and MOSI pins should be connected to the TPIDATA pin -on the ATtiny device. -However, a 1K resistor should be placed between the MOSI and TPIDATA. -The MISO pin connects to TPIDATA directly. -The SCK pin is connected to TPICLK. -

      -

      In addition, the Vcc, /RESET and GND pins should -be connected to their respective ports on the ATtiny device. -

      -
    • -Problem: How can I use a FTDI FT232R USB-to-Serial device for bitbang programming? - -

      Solution: When connecting the FT232 directly to the pins of the target Atmel device, -the polarity of the pins defined in the programmer definition should be -inverted by prefixing a tilde. For example, the dasa programmer would -look like this when connected via a FT232R device (notice the tildes in -front of pins 7, 4, 3 and 8): -

      -
      -
      programmer
-  id    = "dasa_ftdi";
-  desc  = "serial port banging, reset=rts sck=dtr mosi=txd miso=cts";
-  type  = serbb;
-  reset = ~7;
-  sck   = ~4;
-  mosi  = ~3;
-  miso  = ~8;
-;
-
      - -

      Note that this uses the FT232 device as a normal serial port, not using the -FTDI drivers in the special bitbang mode. -

      -
    • -Problem: My ATtiny4/5/9/10 reads out fine, but any attempt to program -it (through TPI) fails. Instead, the memory retains the old contents. - -

      Solution: Mind the limited programming supply voltage range of these -devices. -

      -

      In-circuit programming through TPI is only guaranteed by the datasheet -at Vcc = 5 V. -

      -
    • -Problem: My ATxmega…A1/A2/A3 cannot be programmed through PDI with -my AVR Dragon. Programming through a JTAG ICE mkII works though, as does -programming through JTAG. - -

      Solution: None by this time (2010 Q1). -

      -

      It is said that the AVR Dragon can only program devices from the A4 -Xmega sub-family. -

      -
    • -Problem: when programming with an AVRISPmkII or STK600, AVRDUDE hangs -when programming files of a certain size (e.g. 246 bytes). Other -(larger or smaller) sizes work though. - -

      Solution: This is a bug caused by an incorrect handling of zero-length -packets (ZLPs) in some versions of the libusb 0.1 API wrapper that ships -with libusb 1.x in certain Linux distributions. All Linux systems with -kernel versions < 2.6.31 and libusb >= 1.0.0 < 1.0.3 are reported to be -affected by this. -

      -

      See also: http://www.libusb.org/ticket/6 -

      -
    • -Problem: after flashing a firmware that reduces the target’s clock -speed (e.g. through the CLKPR register), further ISP connection -attempts fail. - -

      Solution: Even though ISP starts with pulling /RESET 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. -

      -

      As that slows down the entire subsequent ISP session, it might make -sense to just issue a chip erase using the slow ISP clock -(option -e), and then start a new session at higher speed. -Option -D might be used there, to prevent another unneeded -erase cycle. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_4.html b/docs/avrdude_4.html deleted file mode 100644 index f874350c..00000000 --- a/docs/avrdude_4.html +++ /dev/null @@ -1,376 +0,0 @@ - - - - -AVRDUDE: 2.2 Programmers accepting extended parameters - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    2.2 Programmers accepting extended parameters

    - -
    -
    JTAG ICE mkII/3
    -
    AVR Dragon
    -
    -

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

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

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

    -
    - -
    -
    AVR910
    -
    -

    The AVR910 programmer type accepts the following extended parameter: -

    -
    ‘devcode=VALUE’
    -

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

    -
    ‘no_blockmode’
    -

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

    -
    - -
    -
    Arduino
    -
    -

    The Arduino programmer type accepts the following extended parameter: -

    -
    ‘attemps=VALUE’
    -

    Overide the default number of connection retry attempt by using VALUE. -

    -
    - -
    -
    BusPirate
    -
    -

    The BusPirate programmer type accepts the following extended parameters: -

    -
    ‘reset=cs,aux,aux2’
    -

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

    -

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

    -
    -
    ‘spifreq=0..7’
    -
    - - - - - - - - -
    030 kHz (default)
    1125 kHz
    2250 kHz
    31 MHz
    42 MHz
    52.6 MHz
    64 MHz
    78 MHz
    - -
    -
    ‘rawfreq=0..3’
    -

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

    - - - - - -
    05 kHz
    150 kHz
    2100 kHz (Firmware v4.2+ only)
    3400 kHz (v4.2+)
    - -

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

    -
    -
    ‘ascii’
    -

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

    -
    -
    ‘nopagedwrite’
    -

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

    -
    -
    ‘nopagedread’
    -

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

    -
    -
    ‘cpufreq=125..4000’
    -

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

    -
    -
    ‘serial_recv_timeout=1...’
    -

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

    -
    -
    - -
    -
    Micronucleus bootloader
    -
    -

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

    -
    ‘wait=timeout’
    -

    If the device is not connected, wait for the device to be plugged in. -The optional timeout specifies the connection time-out in seconds. -If no time-out is specified, AVRDUDE will wait indefinitely until the -device is plugged in. -

    -
    - -
    -
    Teensy bootloader
    -
    -

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

    -
    ‘wait=timeout’
    -

    If the device is not connected, wait for the device to be plugged in. -The optional timeout specifies the connection time-out in seconds. -If no time-out is specified, AVRDUDE will wait indefinitely until the -device is plugged in. -

    -
    - -
    -
    Wiring
    -
    -

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

    -
    ‘snooze=0..32767’
    -

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

    -
    - -
    -
    PICkit2
    -

    Connection to the PICkit2 programmer: -

    - - - - - - - -
    (AVR)(PICkit2)
    RSTVPP/MCLR (1)
    VDDVDD Target (2) -- possibly optional if AVR self powered
    GNDGND (3)
    MISOPGD (4)
    SCLKPDC (5)
    OSIAUX (6)
    - -

    Extended command line parameters: -

    -
    ‘clockrate=rate’
    -

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

    -
    ‘timeout=usb-transaction-timeout’
    -

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

    -
    - -
    -
    USBasp
    -

    Extended parameters: -

    -
    ‘section_config’
    -

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

    -
    - -
    -
    xbee
    -

    Extended parameters: -

    -
    ‘xbeeresetpin=1..7’
    -

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

    -

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

    -
    - -
    -
    serialupdi
    -

    Extended parameters: -

    -
    ‘rtsdtr=low|high’
    -

    Forces RTS/DTR lines to assume low or high state during the whole -programming session. Some programmers might use this signal to -indicate UPDI programming state, but this is strictly hardware -specific. -

    -

    When not provided, driver/OS default value will be used. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_5.html b/docs/avrdude_5.html deleted file mode 100644 index e20d4a21..00000000 --- a/docs/avrdude_5.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - -AVRDUDE: 2.3 Example Command Line Invocations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    2.3 Example Command Line Invocations

    - -

    Download the file diag.hex to the ATmega128 chip using the -STK500 programmer connected to the default serial port: -

    -
    -
    -
    % avrdude -p m128 -c stk500 -e -U flash:w:diag.hex 
-
-avrdude: AVR device initialized and ready to accept instructions
-
-Reading | ################################################## | 100% 0.03s
-
-avrdude: Device signature = 0x1e9702
-avrdude: erasing chip
-avrdude: done.
-avrdude: performing op: 1, flash, 0, diag.hex
-avrdude: reading input file "diag.hex"
-avrdude: input file diag.hex auto detected as Intel Hex
-avrdude: writing flash (19278 bytes):
-
-Writing | ################################################## | 100% 7.60s
-
-avrdude: 19456 bytes of flash written
-avrdude: verifying flash memory against diag.hex:
-avrdude: load data flash data from input file diag.hex:
-avrdude: input file diag.hex auto detected as Intel Hex
-avrdude: input file diag.hex contains 19278 bytes
-avrdude: reading on-chip flash data:
-
-Reading | ################################################## | 100% 6.83s
-
-avrdude: verifying ...
-avrdude: 19278 bytes of flash verified
-
-avrdude done.  Thank you.
-
-%
-
    -
    - - -

    Upload the flash memory from the ATmega128 connected to the STK500 -programmer and save it in raw binary format in the file named -c:/diag flash.bin: -

    -
    -
    -
    % avrdude -p m128 -c stk500 -U flash:r:"c:/diag flash.bin":r 
-
-avrdude: AVR device initialized and ready to accept instructions
-
-Reading | ################################################## | 100% 0.03s
-
-avrdude: Device signature = 0x1e9702
-avrdude: reading flash memory:
-
-Reading | ################################################## | 100% 46.10s
-
-avrdude: writing output file "c:/diag flash.bin"
-
-avrdude done.  Thank you.
-
-% 
-
    -
    - - -

    Using the default programmer, download the file diag.hex to -flash, eeprom.hex to EEPROM, and set the Extended, High, and Low -fuse bytes to 0xff, 0x89, and 0x2e respectively: -

    -
    -
    -
    -% avrdude -p m128 -u -U flash:w:diag.hex \
->                 -U eeprom:w:eeprom.hex \
->                 -U efuse:w:0xff:m      \
->                 -U hfuse:w:0x89:m      \
->                 -U lfuse:w:0x2e:m
-
-avrdude: AVR device initialized and ready to accept instructions
-
-Reading | ################################################## | 100% 0.03s
-
-avrdude: Device signature = 0x1e9702
-avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
-         To disable this feature, specify the -D option.
-avrdude: erasing chip
-avrdude: reading input file "diag.hex"
-avrdude: input file diag.hex auto detected as Intel Hex
-avrdude: writing flash (19278 bytes):
-
-Writing | ################################################## | 100% 7.60s
-
-avrdude: 19456 bytes of flash written
-avrdude: verifying flash memory against diag.hex:
-avrdude: load data flash data from input file diag.hex:
-avrdude: input file diag.hex auto detected as Intel Hex
-avrdude: input file diag.hex contains 19278 bytes
-avrdude: reading on-chip flash data:
-
-Reading | ################################################## | 100% 6.84s
-
-avrdude: verifying ...
-avrdude: 19278 bytes of flash verified
-
-[ ... other memory status output skipped for brevity ... ]
-
-avrdude done.  Thank you.
-
-% 
-
    -
    - - -

    Connect to the JTAG ICE mkII which serial number ends up in 1C37 via -USB, and enter terminal mode: -

    -
    -
    -
    -% avrdude -c jtag2 -p m649 -P usb:1c:37 -t
-
-avrdude: AVR device initialized and ready to accept instructions
-
-Reading | ################################################## | 100% 0.03s
-
-avrdude: Device signature = 0x1e9603
-
-[ ... terminal mode output skipped for brevity ... ]
-
-avrdude done.  Thank you.
-
-
    -
    - -

    List the serial numbers of all JTAG ICEs attached to USB. This is -done by specifying an invalid serial number, and increasing the -verbosity level. -

    -
    -
    -
    -% avrdude -c jtag2 -p m128 -P usb:xx -v
-[...]
-         Using Port            : usb:xxx
-         Using Programmer      : jtag2
-avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C6B
-avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C3A
-avrdude: usbdev_open(): Found JTAG ICE, serno: 00A000001C30
-avrdude: usbdev_open(): did not find any (matching) USB device "usb:xxx"
-
-
    -
    - - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_6.html b/docs/avrdude_6.html deleted file mode 100644 index af4e8ce8..00000000 --- a/docs/avrdude_6.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - -AVRDUDE: 3 Terminal Mode Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    3 Terminal Mode Operation

    - -

    AVRDUDE has an interactive mode called terminal mode that is -enabled by the ‘-t’ option. This mode allows one to enter -interactive commands to display and modify the various device memories, -perform a chip erase, display the device signature bytes and part -parameters, and to send raw programming commands. Commands and -parameters may be abbreviated to their shortest unambiguous form. -Terminal mode also supports a command history so that previously entered -commands can be recalled and edited. -

    - - - -
    3.1 Terminal Mode Commands   -
    3.2 Terminal Mode Examples   -
    - -
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_7.html b/docs/avrdude_7.html deleted file mode 100644 index 5ad163f7..00000000 --- a/docs/avrdude_7.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - -AVRDUDE: 3.1 Terminal Mode Commands - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    3.1 Terminal Mode Commands

    - -

    The following commands are implemented: -

    -
    -
    dump memtype addr nbytes
    -

    Read nbytes from the specified memory area, and display them in -the usual hexadecimal and ASCII form. -

    -
    -
    dump
    -

    Continue dumping the memory contents for another nbytes where the -previous dump command left off. -

    -
    -
    write memtype addr byte1 … byteN
    -

    Manually program the respective memory cells, starting at address addr, -using the values byte1 through byteN. This feature is not -implemented for bank-addressed memories such as the flash memory of -ATMega devices. -

    -
    -
    erase
    -

    Perform a chip erase. -

    -
    -
    send b1 b2 b3 b4
    -

    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. -

    -
    -
    sig
    -

    Display the device signature bytes. -

    -
    -
    spi
    -

    Enter direct SPI mode. The pgmled pin acts as slave select. -Only supported on parallel bitbang programmers, and partially by USBtiny. -Slave Select must be externally held low for direct SPI when -using USBtinyISP, and send must be a multiple of four bytes. -

    -
    -
    part
    -

    Display the current part settings and parameters. Includes chip -specific information including all memory types supported by the -device, read/write timing, etc. -

    -
    -
    pgm
    -

    Return to programming mode (from direct SPI mode). -

    -
    -
    verbose [level]
    -

    Change (when level is provided), or display the verbosity -level. -The initial verbosity level is controlled by the number of -v options -given on the command line. -

    -
    -
    ?
    -
    help
    -

    Give a short on-line summary of the available commands. -

    -
    -
    quit
    -

    Leave terminal mode and thus AVRDUDE. -

    -
    -
    - -

    In addition, the following commands are supported on the STK500 -and STK600 programmer: -

    -
    -
    vtarg voltage
    -

    Set the target’s supply voltage to voltage Volts. -

    -
    -
    varef [channel] voltage
    -

    Set the adjustable voltage source to voltage Volts. -This voltage is normally used to drive the target’s -Aref input on the STK500 and STK600. -The STK600 offers two reference voltages, which can be -selected by the optional parameter channel (either -0 or 1). -

    -
    -
    fosc freq[M|k]
    -

    Set the master oscillator to freq Hz. -An optional trailing letter M -multiplies by 1E6, a trailing letter k by 1E3. -

    -
    -
    fosc off
    -

    Turn the master oscillator off. -

    -
    -
    sck period
    -

    STK500 and STK600 only: -Set the SCK clock period to period microseconds. -

    -

    JTAG ICE only: -Set the JTAG ICE bit clock period to period microseconds. -Note that unlike STK500 settings, this setting will be reverted to -its default value (approximately 1 microsecond) when the programming -software signs off from the JTAG ICE. -This parameter can also be used on the JTAG ICE mkII/3 to specify the -ISP clock period when operating the ICE in ISP mode. -

    -
    -
    parms
    -

    STK500 and STK600 only: -Display the current voltage and master oscillator parameters. -

    -

    JTAG ICE only: -Display the current target supply voltage and JTAG bit clock rate/period. -

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

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_8.html b/docs/avrdude_8.html deleted file mode 100644 index 30fc7fad..00000000 --- a/docs/avrdude_8.html +++ /dev/null @@ -1,213 +0,0 @@ - - - - -AVRDUDE: 3.2 Terminal Mode Examples - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    3.2 Terminal Mode Examples

    - -

    Display part parameters, modify eeprom cells, perform a chip erase: -

    -
    -
    -
    % avrdude -p m128 -c stk500 -t
-
-avrdude: AVR device initialized and ready to accept instructions
-avrdude: Device signature = 0x1e9702
-avrdude: current erase-rewrite cycle count is 52 (if being tracked)
-avrdude> part
->>> part 
-
-AVR Part              : ATMEGA128
-Chip Erase delay      : 9000 us
-PAGEL                 : PD7
-BS2                   : PA0
-RESET disposition     : dedicated
-RETRY pulse           : SCK
-serial program mode   : yes
-parallel program mode : yes
-Memory Detail         :
-
-                            Page                       Polled
-  Memory Type Paged  Size   Size #Pages MinW  MaxW   ReadBack
-  ----------- ------ ------ ---- ------ ----- ----- ---------
-  eeprom      no       4096    8     0  9000  9000 0xff 0xff
-  flash       yes    131072  256   512  4500  9000 0xff 0x00
-  lfuse       no          1    0     0     0     0 0x00 0x00
-  hfuse       no          1    0     0     0     0 0x00 0x00
-  efuse       no          1    0     0     0     0 0x00 0x00
-  lock        no          1    0     0     0     0 0x00 0x00
-  calibration no          1    0     0     0     0 0x00 0x00
-  signature   no          3    0     0     0     0 0x00 0x00
-
-avrdude> dump eeprom 0 16
->>> dump eeprom 0 16 
-0000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
-
-avrdude> write eeprom 0 1 2 3 4
->>> write eeprom 0 1 2 3 4 
-
-avrdude> dump eeprom 0 16
->>> dump eeprom 0 16 
-0000  01 02 03 04 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
-
-avrdude> erase
->>> erase 
-avrdude: erasing chip
-avrdude> dump eeprom 0 16
->>> dump eeprom 0 16 
-0000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
-
-avrdude> 
-
    -
    - - -

    Program the fuse bits of an ATmega128 (disable M103 compatibility, -enable high speed external crystal, enable brown-out detection, slowly -rising power). Note since we are working with fuse bits the -u (unsafe) -option is specified, which allows you to modify the fuse bits. First -display the factory defaults, then reprogram: -

    -
    -
    -
    % avrdude -p m128 -u -c stk500 -t
-
-avrdude: AVR device initialized and ready to accept instructions
-avrdude: Device signature = 0x1e9702
-avrdude: current erase-rewrite cycle count is 52 (if being tracked)
-avrdude> d efuse
->>> d efuse 
-0000  fd                                                |.               |
-
-avrdude> d hfuse
->>> d hfuse 
-0000  99                                                |.               |
-
-avrdude> d lfuse
->>> d lfuse 
-0000  e1                                                |.               |
-
-avrdude> w efuse 0 0xff
->>> w efuse 0 0xff 
-
-avrdude> w hfuse 0 0x89
->>> w hfuse 0 0x89 
-
-avrdude> w lfuse 0 0x2f
->>> w lfuse 0 0x2f 
-
-avrdude> 
-
    -
    - - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_9.html b/docs/avrdude_9.html deleted file mode 100644 index 731b204d..00000000 --- a/docs/avrdude_9.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - -AVRDUDE: 4 Configuration File - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -
    - -

    4 Configuration File

    - -

    AVRDUDE reads a configuration file upon startup which describes all of -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. -

    -

    AVRDUDE first looks for a system wide configuration file in a platform -dependent location. On Unix, this is usually -/usr/local/etc/avrdude.conf, while on Windows it is usually in the -same location as the executable file. The name of this file can be -changed using the ‘-C’ command line option. After the system wide -configuration file is parsed, AVRDUDE looks for a per-user configuration -file to augment or override the system wide defaults. On Unix, the -per-user file is .avrduderc within the user’s home directory. On -Windows, this file is the avrdude.rc file located in the same -directory as the executable. -

    - - - - - -
    4.1 AVRDUDE Defaults   -
    4.2 Programmer Definitions   -
    4.3 Part Definitions   -
    4.4 Other Notes   -
    - -
    - - - - - - - - - - - - - - -
    [ << ][ < ][ Up ][ > ][ >> ]         [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_abt.html b/docs/avrdude_abt.html deleted file mode 100644 index 155c589d..00000000 --- a/docs/avrdude_abt.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - -AVRDUDE: About This Document - - - - - - - - - - - - - - - - - - - - -
    [Top][Contents][Index][ ? ]
    -
    -

    About This Document

    - -

    - This document was generated on March 17, 2022 using texi2html 5.0. -

    -

    - The buttons in the navigation panels have the following meaning: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Button Name Go to From 1.2.3 go to
    [ << ] FastBackBeginning of this chapter or previous chapter1
    [ < ] BackPrevious section in reading order1.2.2
    [ Up ] UpUp section1.2
    [ > ] ForwardNext section in reading order1.2.4
    [ >> ] FastForwardNext chapter2
    [Top] TopCover (top) of document  
    [Contents] ContentsTable of contents  
    [Index] IndexIndex  
    [ ? ] AboutAbout (help)  
    - -

    - where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure: -

    - -
      -
    • 1. Section One -
        -
      • 1.1 Subsection One-One -
          -
        • ...
          • -
        -
        • -
      • 1.2 Subsection One-Two -
          -
        • 1.2.1 Subsubsection One-Two-One
          • -
        • 1.2.2 Subsubsection One-Two-Two
          • -
        • 1.2.3 Subsubsection One-Two-Three     - <== Current Position
          • -
        • 1.2.4 Subsubsection One-Two-Four
          • -
        -
        • -
      • 1.3 Subsection One-Three -
          -
        • ...
          • -
        -
        • -
      • 1.4 Subsection One-Four
        • -
      -
      • -
    - -
    - - - - - -
    [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/avrdude_toc.html b/docs/avrdude_toc.html deleted file mode 100644 index bd7b72fb..00000000 --- a/docs/avrdude_toc.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - -AVRDUDE: Table of Contents - - - - - - - - - - - - - - - - - - - - -
    [Top][Contents][Index][ ? ]
    -
    -

    Table of Contents

    - -
    - - -
    -
    - - - - - -
    [Top][Contents][Index][ ? ]
    -

    - - This document was generated on March 17, 2022 using texi2html 5.0. - -
    - -

    - - diff --git a/docs/index.html b/docs/index.html deleted file mode 120000 index 946880a3..00000000 --- a/docs/index.html +++ /dev/null @@ -1 +0,0 @@ -avrdude.html \ No newline at end of file diff --git a/src/doc/avrdude.texi b/src/doc/avrdude.texi index 06693f8e..1daee82f 100644 --- a/src/doc/avrdude.texi +++ b/src/doc/avrdude.texi @@ -119,7 +119,7 @@ Copyright @copyright{} Brian S. Dean, J@"org Wunsch @node Introduction, Command Line Options, Top, Top @comment node-name, next, previous, up @chapter Introduction -@cindex introduction +@cindex Introduction AVRDUDE - AVR Downloader Uploader - is a program for downloading and uploading the on-chip memories of Atmel's AVR microcontrollers. It can @@ -137,6 +137,8 @@ from the contents of a file, while interactive mode is useful for exploring memory contents, modifying individual bytes of eeprom, programming fuse/lock bits, etc. +@cindex Programmers supported + AVRDUDE supports the following basic programmer types: Atmel's STK500, Atmel's AVRISP and AVRISP mkII devices, Atmel's STK600, @@ -337,6 +339,7 @@ below for Teensy specific options. @c Node @c @node History, , Introduction, Introduction +@cindex History @section History and Credits AVRDUDE was written by Brian S. Dean under the name of AVRPROG to run on @@ -368,7 +371,6 @@ Roth. @c @node Command Line Options, Terminal Mode Operation, Introduction, Top @chapter Command Line Options -@cindex options @menu * Option Descriptions:: @@ -380,6 +382,7 @@ Roth. @c Node @c @node Option Descriptions, Programmers accepting extended parameters, Command Line Options, Command Line Options +@cindex Options (command-line) @section Option Descriptions @noindent @@ -404,6 +407,8 @@ but it can be added to the configuration file if you have the Atmel datasheet so that you can enter the programming specifications. Currently, the following MCU types are understood: +@cindex Device support + @multitable @columnfractions .15 .3 @include parts.texi @end multitable @@ -455,6 +460,8 @@ file without any code changes to AVRDUDE. Simply copy an existing entry and change the pin definitions to match that of the unknown programmer. Currently, the following programmer ids are understood and supported: +@cindex Programmer support + @multitable @columnfractions .2 .6 @include programmers.texi @end multitable @@ -832,7 +839,7 @@ accepting extended parameters. @c @node Programmers accepting extended parameters, Example Command Line Invocations, Option Descriptions, Command Line Options @section Programmers accepting extended parameters - +@cindex @code{-x} AVR Dragon @table @code @item JTAG ICE mkII/3 @@ -849,6 +856,7 @@ Each AVR unit within the chain shifts by 4 bits. Other JTAG units might require a different bit shift count. @end table +@cindex @code{-x} AVR910 @item AVR910 The AVR910 programmer type accepts the following extended parameter: @@ -869,6 +877,7 @@ Use programmer creates errors during initial sequence. @end table +@cindex @code{-x} Arduino @item Arduino The Arduino programmer type accepts the following extended parameter: @@ -877,6 +886,7 @@ The Arduino programmer type accepts the following extended parameter: Overide the default number of connection retry attempt by using @var{VALUE}. @end table +@cindex @code{-x} Buspirate @item BusPirate The BusPirate programmer type accepts the following extended parameters: @@ -966,6 +976,7 @@ The default value is 100ms. Using 10ms might work in most cases. @end table +@cindex @code{-x} Micronucleus bootloader @item Micronucleus bootloader When using the Micronucleus programmer type, the @@ -978,6 +989,7 @@ If no time-out is specified, AVRDUDE will wait indefinitely until the device is plugged in. @end table +@cindex @code{-x} Teensy bootloader @item Teensy bootloader When using the Teensy programmer type, the @@ -990,6 +1002,7 @@ If no time-out is specified, AVRDUDE will wait indefinitely until the device is plugged in. @end table +@cindex @code{-x} Wiring @item Wiring When using the Wiring programmer type, the @@ -1001,6 +1014,7 @@ After performing the port open phase, AVRDUDE will wait/snooze for No toggling of DTR/RTS is performed if @var{snooze} > 0. @end table +@cindex @code{-x} PICkit2 @item PICkit2 Connection to the PICkit2 programmer: @multitable @columnfractions .05 .3 @@ -1021,6 +1035,7 @@ Sets the SPI clocking rate in Hz (default is 100kHz). Alternately the -B or -i o Sets the timeout for USB reads and writes in milliseconds (default is 1500 ms). @end table +@cindex @code{-x} USBasp @item USBasp Extended parameters: @table @code @@ -1031,6 +1046,7 @@ rather than entire chip. Only applicable to TPI devices (ATtiny 4/5/9/10/20/40). @end table +@cindex @code{-x} xbee @item xbee Extended parameters: @table @code @@ -1047,6 +1063,7 @@ The remaining two necessary XBee-to-MCU connections are not selectable the MCU's ‘TXD’ line. @end table +@cindex @code{-x} serialupdi @item serialupdi Extended parameters: @table @code @@ -1249,6 +1266,7 @@ commands can be recalled and edited. @end menu @node Terminal Mode Commands, Terminal Mode Examples, Terminal Mode Operation, Terminal Mode Operation +@cindex Terminal Mode @section Terminal Mode Commands @noindent @@ -1554,6 +1572,8 @@ avrdude> q @c Node @c @node Configuration File, Programmer Specific Information, Terminal Mode Operation, Top +@cindex Configuration File +@cindex @code{avrdude.conf} @chapter Configuration File @noindent @@ -1916,6 +1936,7 @@ Reading fuse and lock bits is fully supported. @c Node @c @node Atmel STK600, Atmel DFU bootloader using FLIP version 1, Programmer Specific Information, Programmer Specific Information +@cindex STK600 @section Atmel STK600 @c @@ -2012,6 +2033,7 @@ least 4.5 V in order to work. This can be done using @c Node @c @node Atmel DFU bootloader using FLIP version 1, SerialUPDI programmer , Atmel STK600, Programmer Specific Information +@cindex DFU bootloader @section Atmel DFU bootloader using FLIP version 1 Bootloaders using the FLIP protocol version 1 experience some very @@ -2040,6 +2062,7 @@ versions of the bootloader. @c Node @c @node SerialUPDI programmer, , Atmel DFU bootloader using FLIP version 1, Programmer Specific Information +@cindex SerialUPDI @section SerialUPDI programmer SerialUPDI programmer can be used for programming UPDI-only devices From 33bace0ceee9db5929262d1a0346abc670f2aa06 Mon Sep 17 00:00:00 2001 From: Joerg Wunsch Date: Sat, 19 Mar 2022 17:30:55 +0100 Subject: [PATCH 25/25] Provide an example for the second form of the "write" command In terminal mode, there are two forms of "write", one that explicitly mentions all data values, and a second one that instead specifies a total range to write, where the last data value given is replicated as needed. --- src/doc/avrdude.texi | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/src/doc/avrdude.texi b/src/doc/avrdude.texi index 1daee82f..cdf040a7 100644 --- a/src/doc/avrdude.texi +++ b/src/doc/avrdude.texi @@ -1443,6 +1443,7 @@ Display the current target supply voltage and JTAG bit clock rate/period. @c Node @c @node Terminal Mode Examples, , Terminal Mode Commands, Terminal Mode Operation +@cindex Terminal Mode @section Terminal Mode Examples @noindent @@ -1567,6 +1568,22 @@ avrdude> q @end cartouche @end smallexample +The following example demonstrates the second form of the @code{write} +command where the last data value provided is used to fill up the +indicated memory range. + +@smallexample +@cartouche +avrdude> write eeprom 0x00 0x20 'a' 'b' 'c' 0x11 0xcafe 0x55 ... +>>> write eeprom 0x00 0x20 'a' 'b' 'c' 0x11 0xcafe 0x55 ... + +avrdude> dump eeprom 0 0x30 +>>> dump eeprom 0 0x30 +0000 61 62 63 11 fe ca 55 55 55 55 55 55 55 55 55 55 |abc...UUUUUUUUUU| +0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 |UUUUUUUUUUUUUUUU| +0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| +@end cartouche +@end smallexample @c @c Node