diff --git a/docs/avrdude.html b/docs/avrdude.html index 0e069a81..812a4dd9 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

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

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

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

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