ATmega64A
• 2 Single Program Memory Break Points + 1 Program Memory Break Point with mask (“range
Break Point”).
• 2 Single Program Memory Break Points + 1 Data Memory Break Point with mask (“range
Break Point”).
A debugger, like the AVR Studio®, may however use one or more of these resources for its inter-
nal purpose, leaving less flexibility to the end-user.
A list of the On-chip Debug specific JTAG instructions is given in “On-chip Debug Specific JTAG
Instructions” on page 257.
The JTAGEN Fuse must be programmed to enable the JTAG Test Access Port. In addition, the
OCDEN Fuse must be programmed and no Lock bits must be set for the On-chip Debug system
to work. As a security feature, the On-chip Debug system is disabled when any Lock bits are set.
Otherwise, the On-chip Debug system would have provided a back-door into a secured device.
The AVR Studio enables the user to fully control execution of programs on an AVR device with
On-chip Debug capability, AVR In-Circuit Emulator, or the built-in AVR Instruction Set Simulator.
AVR Studio supports source level execution of Assembly programs assembled with Atmel AVR
Assembler and C programs compiled with third party vendors’ compilers.
AVR Studio runs under Microsoft® Windows® 95/98/2000/XP/NT®.
For a full description of the AVR Studio, please refer to the AVR Studio User Guide. Only high-
lights are presented in this document.
All necessary execution commands are available in AVR Studio, both on source level and on
disassembly level. The user can execute the program, single step through the code either by
tracing into or stepping over functions, step out of functions, place the cursor on a statement and
execute until the statement is reached, stop the execution, and reset the execution target. In
addition, the user can have an unlimited number of code Break Points (using the BREAK
instruction) and up to two data memory Break Points, alternatively combined as a mask (range)
Break Point.
24.7 On-chip Debug Specific JTAG Instructions
The On-chip debug support is considered being private JTAG instructions, and distributed within
ATMEL and to selected third party vendors only. Instruction opcodes are listed for reference.
24.7.1
24.7.2
24.7.3
24.7.4
PRIVATE0; 0x8
PRIVATE1; 0x9
PRIVATE2; 0xA
PRIVATE3; 0xB
Private JTAG instruction for accessing On-chip Debug system.
Private JTAG instruction for accessing On-chip Debug system.
Private JTAG instruction for accessing On-chip Debug system.
Private JTAG instruction for accessing On-chip Debug system.
257
8160C–AVR–07/09
ATMEL [ ATMEL ]
