Datasheet

156
ATmega323(L)
1457E–11/01
• Apply the TMS sequence 1, 1, 0 to re-enter the Run-Test/Idle state. The instruction
is latched onto the parallel output from the shift register path in the Update-IR state.
The Exit-IR, Pause-IR, and Exit2-IR states are only used for navigating the state
machine.
• At the TMS input, apply the sequence 1, 0, 0 at the rising edges of TCK to enter the
Shift Data Register - Shift-DR state. While TMS is low, upload the selected Data
Register (selected by the present JTAG instruction in the JTAG Instruction Register)
from the TDI input at the rising edge of TCK. At the same time, the parallel inputs to
the Data Register captured in the Capture-DR state shifts out on the TDO pin.
• Apply the TMS sequence 1, 1, 0 to re-enter the Run-Test/Idle state. If the selected
Data Register has a latched parallel-output, the latching takes place in the Update-
DR state. The Exit-DR, Pause-DR, and Exit2-DR states are only used for navigating
the state machine.
As shown in the state diagram, the Run-Test/Idle state need not be entered between
selecting JTAG instruction and using Data Registers, and some JTAG instructions may
select certain functions to be performed in the Run-Test/Idle, making it unsuitable as an
Idle state.
Note: Independent of the initial state of the TAP Controller, the Test-Logic-Reset state can
always be entered by holding TMS high for 5 TCK clock periods.
For detailed information on the JTAG specification, refer to the literature listed in “Bibli-
ography” on page 158.
Using the Boundary-
scan Chain
A complete description of the Boundary-Scan capabilities are given in the section “IEEE
1149.1 (JTAG) Boundary-scan” on page 159.
Using the On-chip Debug
System
As shown in Figure 85, the hardware support for On-Chip Debugging consists mainly of
• A scan chain on the interface between the internal AVR CPU and the internal
peripheral units
• Breakpoint unit
• Communication interface between the CPU and JTAG system
All read or modify/write operations needed for implementing the Debugger are done by
applying AVR instructions via the internal AVR CPU Scan Chain. The CPU sends the
result to an I/O memory mapped location which is part of the communication interface
between the CPU and the JTAG system.
The Breakpoint Unit implements Break on Change of Program Flow, Single Step Break,
2 Program Memory Breakpoints, and 2 combined break points. Together, the 4 break-
points can be configured as either:
• 4 single Program Memory break-points
• 3 Single Program Memory break point + 1 single Data Memory break point
• 2 single Program Memory break-points + 2 single Data Memory break points
• 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 list of the On-Chip Debug specific JTAG instructions is given in “On-chip Debug Spe-
cific JTAG Instructions” on page 157. Note that Atmel supports the On-Chip Debug
system with the AVR Studio front-end software for PCs. The details on hardware imple-