Introducing AVR Dragon: Device Support
Introducing AVR Dragon: Device Support
'
With the AVR Dragon, Atmel has set a new standard for low cost development tools.
AVR Dragon supports all programming modes for the Atmel AVR device family. It also
include full emulation support for devices with 32kB or less Flash memory.
At a fraction of the price traditionally associated with this kind of featured tool, the AVR
Dragon will fulfill all your programming and emulation needs. The flexible and secure
firmware upgrade feature allows AVR Studio to easily upgrade the AVR Dragon to
support new devices.
To see which devices are currently supported please read the Device Support page.
(New devices will be added through AVR Studio updates or Service Packs on a regular
basis)
Supported Protocols
Programming Interfaces:
In System Programming ( ISP )
High Voltage Serial Programming ( HVSP )
Parallel Programming ( PP )
JTAG Programming ( JTAG Prog)
Emulation Interfaces: (Only available for devices with 32kB Flash or less)
JTAG ( JTAG )
debugWIRE ( dW )
AVR Dragon can be used with an external target board. However, the onboard prototype
area, allow simple programming and debugging without any additional hardware besides
strapping cables. Please see the Using the AVR Prototype Area section for a description
on how to use this.
AVR Dragon is powered by the USB cable, and can also source an external target with
up to 300mA (from the VCC connector, 5V) when programming or debugging. For more
information on technical details, please read the AVR Dragon Requirements section. If
the target is already powered by an external power source, the AVR Dragon will adapt
and level convert all signals between the target and the AVR Dragon.
Note: If the target board is powered by external power source, no connection should be
made betwwen the VCC connector and the external board.
AVR Dragon if fully supported by AVR Studio. This allows the AVR Dragon firmware to
be easily updated to support new devices and protocols. When connecting the AVR
Dragon, AVR Studio will automatically check the firmware and prompt the user if an
updated firmware is available.
Device Support
The following devices are currently supported by AVR Dragon.
Programming Debugging
Device ISP HVSP* PP* JTAG JTAG dW Connection Remarks
sheet
Tiny parts
ATtiny11 x SCKT3400D1
ATtiny12 x x SCKT3400D1
ATtiny13 x x x SCKT3400D1
ATtiny15 x x SCKT3600A1
ATtiny2313 x x x SCKT3300D3
ATtiny24 x x x SCKT244484 ATtiny84 HVSP
ATtiny44 programming issue
ATtiny84
ATtiny25 x x x SCKT3400D1
ATtiny45
ATtiny85
ATtiny26 x x SCKT3700A1 ATtiny26 PP
programming issue
ATtiny261 x x x SCKT3700A1
ATtiny461
ATtiny861
ATtiny28 x SCKT3500D-
ATtiny43U x x x Off Board Target
ATtiny48 x x x SCKT3200A2
Mega parts
ATmega8515 x x SCKT3000D3
ATmega8535 x x SCKT3100A3
ATmega48(P) x x x SCKT3200A2
ATmega88(P)
ATmega168(P)
ATmega328P
ATmega8 x x SCKT3200A2
ATmega16 x x x x SCKT3100A3
ATmega164P x x x x SCKT3100A3
ATmega324P
ATmega644(P) x x x SCKT3100A3
ATmega1284P
ATmega162 x x x x SCKT3000D3
ATmega32 x x x x SCKT3100A3
ATmega64 x x x Off Board Target
ATmega128 x x x Off Board Target
ATmega640 x x x Off Board Target
ATmega1280 x x x Off Board Target
ATmega1281 x x x Off Board Target
ATmega2560 x x x Off Board Target
ATmega2561 x x x Off Board Target
ATmega165(P) x x x x Off Board Target
ATmega169(P)
ATmega325(P) x x x x Off Board Target
ATmega329(P)
ATmega3250
(P)
ATmega3290
(P)
ATmega645 x x x Off Board Target
ATmega649
ATmega6450
ATmega6490
ATmega406 x x Off Board Target Note: Supports only
debugging up to
32kB
Note that the PP/HVSP interfaces (Parallel and High Voltage Serial Programming) are
not level converted, but runs at 5V. I.e. extreme care should be taken if using these
interfaces off board.
Abbreviations:
ISP: In System Programming
HVSP: High Voltage Serial Programming
PP: Parallel Programming (high voltage)
dW: debugWire
New devices will be supported through updates of AVR Studio. Please visit
www.atmel.com to download the latest version.
What's New
November 21st, 2007 - Sw: 0x0101 0x0200 (released with AVR Studio 4.13 SP2)
Added programming support for support for ATmega1284P
Added full part support for ATtiny43U, ATtiny48 and ATmega32HVB
July 5th, 2007 - Sw: 0x0101 0x010A (released with AVR Studio 4.13 SP1)
Added part support for AT90USB82, AT90USB162,AT90PWM216, AT90PWM316
and ATmega16HVA
Fixed in FW troubles with enabling debugWIRE mode in debug-projects
February 26th, 2007 - Sw: 0x0101 0x0109 (released with AVR Studio 4.13)
Added part support for ATmega88P and ATmega168P
June 29, 2006 - AVR Studio 4.12 SP3: Sw: 0x0100 0x0102
Fixed bug causing slow ISP programming
June 12, 2006 - AVR Studio 4.12 SP3: Sw: 0x0100 0x0101
Full Support for: ATmega48/88/168, ATmega8, ATmega32, ATmega128,
ATtiny13, ATtiny25/45/85 and ATtiny2313
Getting Started
Please read this section before connecting the AVR Dragon to the computer or target.
Important ! Please install AVR Studio and the USB driver before connecting AVR
Dragon to your PC
Follow these simple steps to get started using the AVR Dragon:
1. Download AVR Studio 4.12 SP3 or later from http://www.atmel.com/avrdragon
2. Install AVR Studio and the USB driver
3. Connect AVR Dragon to the computer, and auto-install new hardware (AVR
Dragon) on the computer
4. Start AVR Studio and the AVR Dragon Programming Dialog
5. Connect AVR Dragon to the target
USB Setup
In order to use the AVR Dragon it is required to install the AVR Studio and USB driver
first. Please do not connect the AVR Dragon to the computer before running the USB
Setup in order to follow this procedure described in Software and USB Setup.
There is no CD shipped with the AVR Dragon. The only way of getting the software is by
downloading it directly from the Internet.
System Requirements
Note: Windows 95 and Windows NT does not support USB, hence cannot be used with
AVR Dragon
Hints
• Always power up the AVR Dragon first before connecting to or powering up the target
• AVR Dragon needs to sense the target voltage at pin 2 on the ISP header or pin 4 on
the JTAG header.
-This also applies when using High Voltage interface.
• The High Voltage interface are set to 5V. Make sure the target board are running at 5V
before using this interface off board.
• VCC header are set to 5V, and can source max 300mA.
• If AVR Dragon is used for programming/debugging targets on the STK500, the RESET
jumper on the STK500 must be removed.
In order to use the AVR Dragon it is required to install the USB driver. Please do not
connect the AVR Dragon to the computer before running the USB Setup. USB driver
installation is done during the AVR Studio installation.
Note: AVR Dragon requires AVR Studio 4.12 with Service Pack 3 or later. Latest version
of the AVR Studio can be found at: www.atmel.com/products/AVR/
Start the AVR Studio installation. During this installation the dialog box in the figure
below will be presented to the user.
To install the USB driver, check the Install/Upgrade USB Driver checkbox, and the USB
Driver will automatically be installed.
When AVR Studio and USB driver installation is finished, please attach the USB cable to
both PC and AVR Dragon. (The AVR Dragon is powered from the USB). If it is the first
time the AVR Dragon is connected to the computer, the box below will appear:
If running Windows XP you need to click "Next" a couple of times. Please wait until the
installation process completes by itself. It may take from a few seconds up to a few
minutes depending on the computer and operating system.
If the USB driver is correctly installed and AVR Dragon is connect to the PC, the green
LED inside the encasing next to the USB connector will be lit.
If the AVR Studio for some reason can't detect the AVR Dragon after the USB setup, try
to restart the computer in order to get the driver properly loaded.
The USB driver can be installed even after AVR Studio have been installed by following
these steps:
1. Open "Control Panel" on the PC (Windows 95 and Windows NT does not support
USB)
2. Select "Add or Remove Programs"
3. Select "AVRStudio4" in the list of programs
4. Click on the "Change" button
5. Select "Modify"
6. Select "Install/upgrade USB Driver"
Note: The AVR Dragon requires a USB port that can deliver 500mA (self-powered USB
hub).
Headers:
Out of the box, the AVR Dragon has the following 3 header connectors mounted:
ISP Header - Used for ISP programming and debugWIRE OCD
JTAG Header - Used for JTAG programming and JTAG OCD.
VCC Header - Used for powering Devices placed in the prototype area, or to power
external target boards (max 300mA). Set to fixed 5V
This 6-pin header uses the standard AVR ISP pinout for easy connection to external
targets. The signals are level-converted to allow communication with targets running at
any voltage between 1.8 and 5.5V
Note that the target voltage must be applied to pin 2 on the ISP header for the AVR
Dragons level converters.
JTAG Header(mounted):
The 10-pin JTAG header is a standard pinout JTAG connector. When connecting the
AVR Dragon JTAG header to an external target, the signals are level converted to match
the target board voltage. This is done automatically. Please note that the AVR Dragon
will not power the target through the JTAG interface. The target needs to be powered
through a dedicated powersupply. (or by powering it using the VCC connector (5.0V max
300mA). AVR Dragon needs to sense the target voltage on pin 4 on the JTAG
connector.
The figure above shows the general pinout of the HV_PROG header. The High Voltage
programming pin mapping are not the same for all parts. See the HVSP Description or
PP Description chapters for more information on the pinout of this header.
The VCC Header contains 5.0 Volt VCC and GND that must be used to power the target
device placed in the prototype area of the AVR Dragon board. The voltage can also be
used to power an external target board, but it is important that the current consumption
is less than 300mA. Please note that the AVR Dragon current sourcing capabilities are
also limited by the amount of current the Host USB controller can deliver.
The expand connector is directly mapped to the 28 and 40-pin DIP sockets. Pin 1 on the
connector - is pin one on both the 28 and the 40pin DIP socket. When doing either
programming or emulation on-board, the appropriate signals should be routed from the
ISP, JTAG, VCC and HV_PROG headers to the correct pins on the EXPAND connector.
Please read the "Using the AVR Dragon Prototype Area" section for more information on
how to use this function.
Status LEDs
Two LEDs show the status of the AVR Dragon. Check the Troubleshooting Guide to
check for solutions if there are any errors.
In System Programming
In System Programming is well suited for programming devices soldered onto external
target boards. This section explains how to connect the AVR Dragon to ISP program an
external target. The ISP lines are equipped with level converters that automatically will
level shift the AVR Dragon to the target board voltage.
It is recommended that a 6-pin header connector with 2.54mm (100 MIL) spacing is
placed on the target board to allow easy access to the ISP programming interface. The
following pinout should be used.
Note: When connecting the AVR Dragon to the target, connect MISO to MISO pin on
the target device, MOSI to MOSI and so on.
Note: AVR Dragon must sense the target voltage at pin 2 on the ISP header in order to
set up the level-converter. For on-board targets, the voltage must be supplied from pin
2,4,6 on the VCC header (5V) into pin 2 (VTG) on the ISP header. When using off-board
targets there should be no connection between VCC header and pin 2 of the ISP
header.
Connect the 6pin cable from the AVR Dragon to the external target as shown in these
pictures:
See the AVR Studio user guide for information about using the Programming Dialog to
program the target device.
Low pin count AVR devices do not have enough IO pins to support the full Parallel
Programming interface. These devices instead use HVSP programming, which is a
serial version of the Parallel Programming interface.
Important!
Extreme care should be taken if using HVSP mode to program a AVR device on an
external target. The HVSP lines do not have level converters, so it is important that the
target board is powered by the AVR Dragon VCC header, and not using another power
supply. In addition the AVR Dragon will apply 12V to the reset pin, so it is important that
the target board is designed to handle 12V on this line.
Note that the target voltage, i.e. the 5V from the VCC header must be applied to either
pin 2 on the ISP header or pin 4 on the JTAG header. This because the AVR Dragon
must read the target voltage.
To avoid damaging the Target Board, the AVR Dragon or both, it is recommended to
only use HVSP mode on devices placed in the 28/40 pin DIP socket on the AVR
Prototyp area on the AVR Dragon.
The High Voltage Serial Programming (HVSP) interface is found on the HV_PROG
header. Figure below shows the pinout of the HV_PROG header when used for HVSP
for all parts except ATtiny24/44/84 :
The ATtiny24/44/84 uses separate pins for entering programming mode. See the pinout
of the HV_PROG header when used for these parts below:
Please see the "Device Connection Sheet" section for information on how to connect
AVR Dragon for HVSP programming for the different supported devices.
See the AVR Studio user guide for information about using the Programming Dialog to
program the target device.
Important!
Extreme care should be taken if using PP mode to program a AVR device on an external
target. The PP lines do not have level converters, so it is important that the target board
then is powered by the AVR Dragon VCC header, and not using its own power supply. In
addition the AVR Dragon will apply 12V to the reset pin, so it is important that the target
board is designed to handle 12V on this line.
Note that the target voltage, i.e. the 5V from the VCC header must be applied to either
pin 2 on the ISP header or pin 4 on the JTAG header. This because the AVR Dragon
must read the target voltage.
To avoid damaging the Target Board, the AVR Dragon or both, it is recommended to
only use PP mode on devices placed in the 28/40 pin DIP socket on the AVR Prototyp
area on the AVR Dragon.
The HV_PROG header pinout is listed below. This is the standard pinout for about all
AVR parts. However the pinout on the HV_PROG header are slightly different for some
parts, these exceptions are listed further down in this page.
Please see the "Device Connection Sheet" section for information on how to connect
AVR Dragon for PP programming.
See the AVR Studio user guide for information about using the Programming Dialog to
program the target device.
See the AVR Studio user guide for information about using the Programming Dialog to
program the target device.
Typing "avrdragon -h" will display all the commands, options and the parts currently
supported by the AVR Dragon.
Commands:
-h, -? Print this help.
-he Print exit codes.
-e Erase device.
-f <fusebytes> Write high/low fuse bytes. The LSB of fusebytes will be
written to the low fuse byte, and the MSB will be written
to the high fuse byte.
-j <ID> Read JTAG ID string. If an optional ID is specified, the
program will terminate if the read ID differs.
-l <lockbyte> Set the lock byte to the specified value.
-p[f|e|b] Program FLASH (-pf), EEPROM (-pe) or both (-pb) memories.
Requires input files specified with the -if (FLASH)
and/or -ie (EEPROM) options.
-q Read fuse bytes. If the selected device has extended fuse,
it will be also be read.
-r[f|e|b] Read FLASH (-rf), EEPROM (-re) or both (-rb) memories.
Requires output files specified with the -of (FLASH) and/or
-oe (EEPROM) options.
-s Read signature bytes.
-v[f|e|b] Verify FLASH (-vf), EEPROM (-ve) or both (vb) memories.
Requires input files specified with the -if (FLASH) and/or
-ie (EEPROM) options.
-y Read lock byte.
Optional line is the nSRST. The nTRST signal is not used, and is reserved for
compatibility with other equipment.
nSRST is used to control and monitor the target reset line. This is however not
necessary for correct emulation. But if the application code sets the JTD bit in the
MCUCSR, the JTAG Interface will be disabled. For the AVR Dragon to reprogram the
target AVR, it will need to have control of the Reset Pin.
The figure below shows which JTAG lines should be connected to the target AVR to
ensure correct operation. To avoid drive contention on the lines it is recommended that
series resistors are placed between the JTAG lines and external circuitry. The value of
the resistor should be chosen so that the external circuitry and the AVR do not exceed
their maximum ratings (i.e. sinks or sources to much current).
AVR Dragon support emulation of devices placed in a JTAG Chain. When connecting N
devices in a JTAG scan chain all devices should connect to TMS and TCK in parallel.
The first device should connects it's TDI to the emulator while the TDO should be wired
to TDI of the next device up to device N. The last device should connects it's TDO to the
emulator.
STK500 does not have a dedicated JTAG interface connector. To connect the AVR
Dragon to the STK500 board, the JTAG Probe must be strapped to the appropriate
JTAG Port Pins of the target device using a squid cable. Check the target device
datasheet for the location of the JTAG pins on the appropriate device. Figure below
shows an example on how the pins should be connected for an ATmega32 on the
STK500. Remember to remove the reset jumper on the STK500 if the reset pin is going
to be controlled from the AVR Dragon.
Note: Add-on cards for the STK500 like e.g. STK501/502 may have a dedicated
JTAG connector.
The STK500 JTAG Adapter, that comes with the JTAGICE mkII, can be used to
simplify the connection to the STK500 for AVR devices with JTAG that mates with
socket SCKT3100A3 and SCKT3000D3 on the STK500.
If the JTAGEN fuse (JTAG Enable) in the target device is un-programmed, the
JTAG Interface will be disabled. This fuse cannot be programmed through the
JTAG Interface and must therefore be programmed through the ISP Interface or
High Voltage Serial or Parallel Interface.
Important!
This interface uses only 1 pin, (RESET pin) for communication with the target. To enable
the debugWIRE interface on an AVR Device, the debugWIRE Enable fuse (DWEN)
must be programmed, (DWEN=0). AVR devices with debugWIRE interface are shipped
with the DWEN fuse un-programmed from the factory. The debugWIRE interface itself
cannot enable this fuse. The DWEN fuse can be programmed through ISP mode, which
requires connection to a 6-pin header. For this reason it is recommended to place the
full 6-pin ISP connector on your target board to simplify emulation and programming.
NOTE: When the DWEN fuse is set, the ISP Interface normal functionality is disabled.
This because the debugWIRE must have control over the RESET pin. When DWEN is
set it is no longer possible to use ISP. Use debugWIRE or High Voltage programming to
disable the DWEN fuse.
Note
If using this connection from AVR Dragon on a STK500, be sure to de-attach the
RESET jumper on the STK500. And connect to the correct ISP header for the actual
AVR device, guided by the colour code in the STK500 silk-print.
When DWEN fuse is programmed, there is only need for GND, VTref and RESET line
for using the debugWIRE interface. However to ease the task of changing between ISP
mode and debugWIRE mode, it is recommended to do debugWIRE with all six lines
connected. The AVR Dragon will automatically tristate all unused ISP pins when running
debugWIRE.
1. Connect the AVR Dragon to the target with ISP (6-pin connection) as described
above.
2. Load a project and Start a debug session using the "Start Debugging" command
(found under the Debug pulldown-menu in AVR Studio)
3. Open "AVR Dragon Options" (found under the Debug pulldown-menu in AVR
Studio) and select the "Connections" tab.
4. Click on the button "disable DebugWIRE" as shown in the figure below. And click
"Yes" in the next message box.
Note: Some precautions regarding the RESET line must be taken to ensure proper
communication over the debugWIRE interface. If there is a pull-up on the RESET line,
this resistor must be larger than 10Kohm, and there should be no capacitive load. The
pull-up resistor is not required for debugWIRE functionality. Other logic connected to the
RESET line should be removed.
Note
It's not possible to use the debugWIRE Interface if the lockbits on the target AVR are
programmed. Always be sure that the lockbits are cleared before programming the
DWEN fuse and never set the lockbits while the DWEN fuse is programmed. If both the
debugWIRE enable fuse (DWEN) and lockbits are set, one can use High Voltage
Programming to do a chip erase, hence clear the lockbits. When the lockbits are cleared
Note
The ISP Interface is only capable of reading fuses, signature and do a chip erase when
the DWEN fuse is unprogrammed.
The AVR Dragon has layout for a 40-pin and a 28-pin PDIP socket. The DIP socket pins
are connected directly to the 40-pin Header connector. By strapping the ISP, JTAG,
HV_PROG and VCC header signals to the 40-pin header connector programming or
emulation can be preformed without the need for an external target board.
This section shows how to strap the AVR Dragon for different operation modes. Each
supported AVR device has its own Device Connection Sheet containing all information
required.
There is a number of ways to utilize the prototype area. If only one device type /
programming mode is to be used, the easiest and cheapest way is to just solder wires
directly from the HV_PROG, ISP, JTAG and VCC headers to the EXPAND header.
Howerver, to make the board more flexible header connectors can be soldered in to
allow using cables to be connected without soldering.
Here is a suggestion how to modify the AVR Dragon board to make it flexible and able to
use all DIP socket AVR devices.
In this picture one 20-pin header connector, a 40-pin header connector and a 40-pin DIP
socket has been soldered onto the AVR Dragon.
To make it even more flexible and allow for narrow DIP packages, a ZIF (Zero Insertion
Force) DIP socket has been added in the picture above. Additional sockets can be
bought from third party vendors to support MLF/QFN, TQFP, SOIC etc packages. (Link:
http://www.atmel.com/products/AVR/thirdparty.asp#adapters )
- And finally the complete setup for debugWIRE and ISP programming of the ATtiny45.
For details on how this is connected please have a look at the ATtiny45 Device
connection sheet
Devicesheet: SCKT3000D3
Supported Programming Modes: ISP, Parallel Programming, JTAG Prog
Supported Emulation Modes: JTAG for devices with less than 64kB Flash
Applicable for the following devices :
ATmega8515 Note: JTAG programming and emulation not supported by
ATmega8515
ATmega162
In System Programming:
HV_PROG DEVICE
20 nc nc 19 nc F 20
21
18 nc nc 17 22 nc nc 19
16 nc nc 15 23 nc nc 18
14 nc nc 13 24 nc nc 17
12 nc nc 11 25 nc nc 16
10 nc nc 9 26 nc nc 15
8 nc nc 7 27 nc nc 14
6 nc nc 5 28 nc nc 13
4 nc nc 3 29 nc nc 12
2 nc nc 1 30 nc nc 11
ISP 31 nc nc 10
6F E 5 32 nc E 9
4D C 3 33 nc C 8
2B A 1 34 nc A 7
JTAG 35 nc D 6
10 nc nc 9 36 nc nc 5
VCC 8 nc nc 7 37 nc nc 4
6 B nc 5 6 nc nc 5 38 nc nc 3
4 G nc 3 4 nc nc 3 39 nc nc 2
2 nc nc 1 2 nc nc 1 40 G nc 1
HV_PROG DEVICE
20 nc nc 19 nc B 20
21
18 nc nc 17 22 nc nc 19
16 nc nc 15 23 nc nc 18
14 nc nc 13 24 nc nc 17
12 nc nc 11 25 A nc 16
10 nc nc 9 26 E nc 15
8 nc nc 7 27 C nc 14
6 nc nc 5 28 G nc 13
4 nc nc 3 29 nc nc 12
2 nc nc 1 30 nc nc 11
2 nc nc 1 30 nc nc 11
ISP 31 nc nc 10
6 nc nc 5 32 nc F 9
4 nc nc 3 33 nc nc 8
2 nc nc 1 34 nc nc 7
JTAG 35 nc nc 6
10 H G 9 36 nc nc 5
VCC 8 nc nc 7 37 nc nc 4
6 D H 5 6F E 5 38 nc nc 3
4 I nc 3 4D C 3 39 nc nc 2
2 nc nc 1 2B A 1 40 I nc 1
Parallel Programming
HV_PROG DEVICE
nc
20 T S 19 21 T 20
nc
18 R Q 17 22 Q 19
nc nc
16 P O 15 23 18
24 nc P 17
14 N M 13
nc
12 L K 11 25 O 16
nc
10 J I 9 26 N 15
nc
8H G 7 27 M 14
nc
6F E 5 28 L 13
29 nc K 12
4D C 3
nc
2B A 1 30 J 11
31 nc nc 10
ISP
nc
6 nc nc 5 32 R 9
nc
4 nc nc 3 33 H 8
nc 34 nc G 7
2U 1
35 nc F 6
JTAG
nc
10 nc nc 9 36 E 5
nc
VCC 8 nc nc 7 37 D 4
nc
6 U nc 5 6 nc nc 5 38 C 3
4 nc nc 3 4 nc nc 3 39 I B 2
2 nc nc 1 2 nc nc 1 40 S A 1
Devicesheet: SCKT3100A3
Supported Programming Modes: ISP, Parallel Programming, JTAG Prog
Supported Emulation Modes: JTAG for devices with less than 64kB Flash
Applicable for the following devices :
ATmega16
ATmega32
ATmega164P
ATmega324P
ATmega644
ATmega644P
ATmega1284P
In System Programming:
HV_PROG DEVICE
20 nc nc 19 21 nc nc 20
18 nc nc 17 22 nc nc 19
16 nc nc 15 23 nc nc 18
14 nc nc 13 24 nc nc 17
12 nc nc 11 25 nc nc 16
10 nc nc 9 26 nc nc 15
8 nc nc 7 27 nc nc 14
6 nc nc 5 28 nc nc 13
4 nc nc 3 29 nc nc 12
2 nc nc 1 30 nc F 11
ISP 31 nc G 10
6 F E 5 32 nc E 9
4 D C 3 33 nc C 8
2 B A 1 34 nc A 7
JTAG 35 nc D 6
10 nc nc 9 36 nc nc 5
VCC 8 nc nc 7 37 nc nc 4
6 B nc 5 6 nc nc 5 38 nc nc 3
4 G nc 3 4 nc nc 3 39 nc nc 2
2 nc nc 1 2 nc nc 1 40 nc nc 1
HV_PROG DEVICE
20 nc nc 19 21 nc nc 20
18 nc nc 17 22 nc nc 19
16 nc nc 15 23 nc nc 18
14 nc nc 13 24 A nc 17
12 nc nc 11 25 E nc 16
10 nc nc 9 26 C nc 15
8 nc nc 7 27 G nc 14
6 nc nc 5 28 nc nc 13
4 nc nc 3 29 nc nc 12
2 nc nc 1 30 nc B 11
ISP 31 nc I 10
6 nc nc 5 32 nc F 9
4 nc nc 3 33 nc nc 8
2 nc nc 1 34 nc nc 7
JTAG 35 nc nc 6
10 H G 9 36 nc nc 5
VCC 8 nc nc 7 37 nc nc 4
6 D H 5 6 F E 5 38 nc nc 3
4 I nc 3 4 D C 3 39 nc nc 2
2 nc nc 1 2 B A 1 40 nc nc 1
Parallel Programming
HV_PROG DEVICE
20 T S 19 21 P O 20
18 R Q 17 22 nc N 19
16 P O 15 23 nc M 18
14 N M 13 24 nc L 17
12 L K 11 25 nc K 16
10 J I 9 26 nc J 15
8 H G 7 27 nc nc 14
6 F E 5 28 nc Q 13
4 D C 3 29 nc nc 12
2 B A 1 30 nc T 11
ISP 31 nc S 10
6 nc nc 5 32 nc R 9
4 nc nc 3 33 nc H 8
2 U nc 1 34 nc G 7
JTAG 35 nc F 6
10 nc nc 9 36 nc E 5
VCC 8 nc nc 7 37 nc D 4
6 U nc 5 6 nc nc 5 38 nc C 3
4 nc nc 3 4 nc nc 3 39 nc B 2
2 nc nc 1 2 nc nc 1 40 I A 1
Devicesheet: SCKT3200A2
Supported Programming Modes: ISP, Parallel Programming
Supported Emulation modes: debugWIRE
Applicable for the following devices :
ATmega8 - Note: debugWIRE not supported by ATmega8
ATmega48
ATmega48P
ATmega88
ATmega168
ATtiny48
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 15 nc nc 14
6 nc nc 5 16 nc nc 13
4 nc nc 3 17 D nc 12
2 nc nc 1 18 A nc 11
ISP 19 C nc 10
6 F E 5 20 nc nc 9
4 D C 3 21 nc F 8
2 B A 1 22 nc G 7
JTAG 23 nc nc 6
10 nc nc 9 24 nc nc 5
VCC 8 nc nc 7 25 nc nc 4
6 B nc 5 6 nc nc 5 26 nc nc 3
4 G nc 3 4 nc nc 3 27 nc nc 2
2 nc nc 1 2 nc nc 1 28 nc E 1
Parallel Programming
HV_PROG DEVICE
20 T S 19 nc nc
18 R Q 17 nc nc
16 P O 15 nc nc
14 N M 13 nc nc
12 L K 11 nc nc
10 J I 9 nc nc
8 H G 7 15 B A 14
6 F E 5 16 C P 13
4 D C 3 17 D O 12
2 B A 1 18 E N 11
ISP 19 F nc 10
6 nc nc 5 20 nc Q 9
4 nc nc 3 21 nc T 8
2 U nc 1 22 nc S 7
JTAG 23 G M 6
10 nc nc 9 24 H L 5
VCC 8 nc nc 7 25 I K 4
6 U nc 5 6 nc nc 5 26 nc J 3
4 nc nc 3 4 nc nc 3 27 nc nc 2
2 nc nc 1 2 nc nc 1 28 nc R 1
Devicesheet: SCKT3300D3
Supported Programming Modes: ISP, Parallel Programming
Supported Emulation Modes: debugWIRE
Applicable for the following devices :
ATtiny2313
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 nc nc 1 nc nc
ISP 11 nc F 10
6 F E 5 12 nc nc 9
4 D C 3 13 nc nc 8
2 B A 1 14 nc nc 7
JTAG 15 nc nc 6
10 nc nc 9 16 nc nc 5
VCC 8 nc nc 7 17 D nc 4
6 B nc 5 6 nc nc 5 18 A nc 3
4 G nc 3 4 nc nc 3 19 C nc 2
2 nc nc 1 2 nc nc 1 20 G E 1
Parallel Programming
HV_PROG DEVICE
20 T S 19 nc nc
18 R Q 17 nc nc
16 nc O 15 nc nc
14 N M 13 nc nc
12 L K 11 nc nc
10 J nc 9 nc nc
8 H G 7 nc nc
6 F E 5 nc nc
4 D C 3 nc nc
2 B A 1 nc nc
ISP 11 O T 10
6 nc nc 5 12 A N 9
4 nc nc 3 13 B M 8
2 U nc 1 14 C L 7
JTAG 15 D K 6
10 nc nc 9 16 E Q 5
VCC 8 nc nc 7 17 F nc 4
6 U nc 5 6 nc nc 5 18 G J 3
4 nc nc 3 4 nc nc 3 19 H nc 2
2 nc nc 1 2 nc nc 1 20 S R 1
Devicesheet: SCKT3400D1
Supported programming modes: ISP, High Voltage Serial Programming
Supported emulation modes: debugWIRE
Applicable for the following devices :
ATtiny11 - Note: ISP and debugWIRE not supported by ATtiny11
ATtiny12 - Note: debugWIRE not supoported by ATtiny12
ATtiny13
ATtiny25
ATtiny45
ATtiny85
HV_PROG DEVICE
20 H G 19 nc nc
18 F E 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc D 3 nc nc
4 nc D 3 nc nc
2 C B 1 nc nc
ISP nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 A nc 1 nc nc
JTAG nc nc
10 nc nc 9 nc nc
VCC 8 nc nc 7 5 B H 4
6 A nc 5 6 nc nc 5 6 C nc 3
4 nc nc 3 4 nc nc 3 7 D E 2
2 nc nc 1 2 nc nc 1 8 G F 1
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 nc nc 1 nc nc
ISP nc nc
6 E F 5 nc nc
4 B D 3 nc nc
2 A C 1 nc nc
JTAG nc nc
10 nc nc 9 nc nc
VCC 8 nc nc 7 5 B E 4
6 A nc 5 6 nc nc 5 6 C nc 3
4 G nc 3 4 nc nc 3 7 D nc 2
2 nc nc 1 2 nc nc 1 8 G F 1
Devicesheet: SCKT3500D-
Supported Programming Modes:Parallel Programming
Supported Emulation modes: none
Applicable for the following devices :
ATtiny28 Note: Only High Voltage Programming available for ATtiny28
Parallel Programming
HV_PROG DEVICE
20 T S 19 nc nc
18 R Q 17 nc nc
nc nc
16 nc O 15 nc nc
14 N M 13 nc nc
12 L K 11 nc nc
10 J nc 9 15 B A 14
8H G 7 16 C nc 13
6F E 5 17 D O 12
4D C 3 18 E N 11
2B A 1 19 F nc 10
ISP 20 nc Q 9
6 nc nc 5 21 nc nc 8
4 nc nc 3 22 T S 7
2U nc 1 23 G M 6
JTAG 24 H L 5
10 nc nc 9 25 nc K 4
VCC 8 nc nc 7 26 nc J 3
6 U nc 5 6 nc nc 5 27 nc nc 2
4 nc nc 3 4 nc nc 3 28 nc R 1
2 nc nc 1 2 nc nc 1
Devicesheet: SCKT3600A1
Supported Programming Modes: ISP, High Voltage Serial Programming
Supported Emulation modes: None
Applicable for the following devices :
ATtiny15 Note: Emulation not supported by ATtiny15
In System Programming
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 nc nc 1 nc nc
ISP nc nc
6 F E 5 nc nc
4 D C 3 nc nc
2 B A 1 nc nc
JTAG nc nc
10 nc nc 9 nc nc
VCC 8 nc nc 7 5 D F 4
6 B nc 5 6 nc nc 5 6 A nc 3
4 G nc 3 4 nc nc 3 7 C nc 2
2 nc nc 1 2 nc nc 1 8 G E 1
HV_PROG DEVICE
20 G F 19 nc nc
18 E 17 nc nc
D
nc nc nc nc
16 15
nc nc
14 nc nc 13
nc nc nc nc
12 11
nc nc nc nc
10 9
nc nc nc nc
8 7
nc nc
6 nc nc 5
nc nc nc
4 C 3
nc nc
2B A 1
nc nc
ISP
nc nc
6 nc nc 5
nc nc nc nc
4 3
nc nc nc
2H 1
nc nc
JTAG
nc nc
10 nc nc 9
VCC 8 nc nc 7 5 A G 4
6 H nc 5 6 nc nc 5 6 B D 3
nc
4 nc nc 3 4 nc nc 3 7 C 2
2 nc nc 1 2 nc nc 1 8 F E 1
Devicesheet: SCKT3700A1
Supported Programming Modes: ISP, Parallel Programming
Supported Emulation modes: debugWIRE
Applicable for the following devices :
ATtiny26 - Note: debugWIRE not supported by ATtiny26, PP - prog issue, see
known issues section
ATtiny261
ATtiny461
ATtiny861
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
nc nc
6 nc nc 5
nc nc
4 nc nc 3 nc
2 nc nc 1 11 nc E
nc
10
ISP 12 9
nc nc
6F E 5 13 nc nc
8
4D C 3 14 nc 7
15 F 6
2B A 1
16 nc G 5
JTAG
17 nc nc 4
10 nc nc 9
18 nc C 3
VCC 8 nc nc 7 nc
6 B nc 5 6 nc nc 5 19 nc A 2
4 G nc 3 4 nc nc 3 20 D 1
2 nc nc 1 2 nc nc 1
Parallel Programming
HV_PROG DEVICE
20 R Q 19 nc nc
18 P O 17 nc nc
nc nc
16 N M 15 nc nc
14 L K 13 nc nc
12 J I 11 nc nc
10 nc nc 9 nc nc
nc nc
8H G 7
nc nc
6F E 5 nc nc
4D C 3
11 H P 10
2B A 1
12 G M 9
ISP
13 F N 8
6 nc nc 5
14 E O 7
4 nc nc 3
15 nc R 6
2S nc 1
16 nc Q 5
JTAG
17 D L 4
10 nc nc 9
18 C K 3
VCC 8 nc nc 7
19 B J 2
6 S nc 5 6 nc nc 5
20 A I 1
4 nc nc 3 4 nc nc 3
2 nc nc 1 2 nc nc 1
Devicesheet: SCKT244484
Supported Programming Modes: ISP, High Voltage Serial Programming
Supported Emulation modes: debugWIRE
Applicable for the following devices :
ATtiny24
ATtiny44
ATtiny84
HV_PROG DEVICE
20 nc nc 19 nc nc
18 nc nc 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc nc 11 nc nc
10 nc nc 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 nc nc 1 nc nc
ISP nc nc
6 F E 5 nc nc
4 D C 3 nc nc
2 B A 1 8 A D 7
JTAG 9 C nc 6
10 nc nc 9 10 nc nc 5
VCC 8 nc nc 7 11 nc E 4
6 B nc 5 6 nc nc 5 12 nc nc 3
4 G nc 3 4 nc nc 3 13 nc nc 2
2 nc nc 1 2 nc nc 1 14 F G 1
HV_PROG DEVICE
20 J I 19 nc nc
18 H G 17 nc nc
16 nc nc 15 nc nc
14 nc nc 13 nc nc
12 nc F 11 nc nc
10 E D 9 nc nc
8 nc nc 7 nc nc
6 nc nc 5 nc nc
4 nc C 3 nc nc
2B A 1 nc nc
ISP nc nc
6 nc nc 5 nc nc
4 nc nc 3 nc nc
2 U nc 1 8 B A 7
JTAG 9 C nc 6
10 nc nc 9 10 nc nc 5
VCC 8 nc nc 7 11 F H 4
6 U nc 5 6 nc nc 5 12 E nc 3
4 nc nc 3 4 nc nc 3 13 D G 2
2 nc nc 1 2 nc nc 1 14 J I 1
This Device is not available in PDIP package and can therefor not directly be connected
to the AVR Dragon Prototype area. See the applicable datasheet for information on how
to connect for ISP, PP and JTAG
Troubleshooting
Problem Reason Solution
Signature Bytes read as ISP Frequency is to high. Lower ISP freq under the
0x00 0x00 0x00 board settings
Not able to communicate RESET pullup resistor to Remove or increase the pull-
with device through small up value to 10K ohm or
debugWIRE more.
Not able to communicate Decoupling Capasitor Remove Decoupling
with device through destroys communication on capasitor on reset line during
debugWIRE RESET line debugWIRE emulation
debugWIRE communication RESET line strongly tied to Remove RESET jumper on
fails when using STK500 VCC STK500 to allow AVR
Dragon to control the line.
After successfully enabling RESET line strongly tied to Remove RESET jumper on
the DWEN fuse, AVR VCC STK500 to allow AVR
Dragon is not able to enter Dragon to control the line.
debug mode
Target voltage is read as 0V AVR Dragon get no In order to get reference
for on-board targets reference voltage to the voltage to the level
target voltage sensing. converters of AVR Dragon,
Target voltage is sensed connect Pin 2 or 4 or 6 on
from either pin 2 on ISP the VCC header to pin 2 on
header or pin 4 on the JTAG ISP header or pin 4 on the
header. JTAG header.
Note that VCC pins on AVR
Dragon are set to 5V and
this procedure should
Known issues
JTAG communication with packages in PDIP which have the CKOUT fuse enabled
and running above 3.5V may be unstable if there is long wiring from the AVR Dragon
to the PDIP AVR.
• An error message will be triggered when entering the Board tab in the programming
dialog, if there is no target voltage present.
• In order to set ISP frequency, AVR Dragon needs to sense target voltage. See trouble
shooting guide
Operation
Target Voltage Range.......................................1.8 - 5.5 V
I/O Pins
Maximum Pull-up on ISP/JTAG header........... 1K
Maximum Pull-down on ISP/JTAG header...... 10K
Note that the AVR Dragon requires a USB port that can deliver up to 500mA. (self-
powered USB hub)
Technical Support
Before requesting techical support make sure you have the latest available AVR Studio,
tool firmware installed. The latest AVR Studio version can be downloaded from
www.atmel.com/avrstudio, and contains the latest firmware version for all Atmel AVR
tools. When connecting your tool, AVR Studio will automatically check the firmware
version and request an update if needed.
Programming speed
A detailed description of the problem, and how to recreate it.
Any error or waring information generated by AVR Studio when the error occurred.