ATMEGA169 ATMEL [ATMEL Corporation], ATMEGA169 Datasheet - Page 229

no-image

ATMEGA169

Manufacturer Part Number
ATMEGA169
Description
8-bit Microcontroller with 16K Bytes In-System Programmable Flash
Manufacturer
ATMEL [ATMEL Corporation]
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
ATMEGA169-16AI
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATMEGA169-16AI SL709
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATMEGA169-16AI SL710
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATMEGA169-16AU
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATMEGA169A-AU
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATMEGA169P-15AT
Manufacturer:
PANASONIC
Quantity:
301
Part Number:
ATMEGA169P-15AT
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Part Number:
ATMEGA169P-16AU
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Part Number:
ATMEGA169PA-MU
Manufacturer:
ATMEL
Quantity:
31
Part Number:
ATMEGA169PAAU
Manufacturer:
INF
Quantity:
4 275
Using the Boundary-
scan Chain
Using the On-chip Debug
System
2514P–AVR–07/06
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:
For detailed information on the JTAG specification, refer to the literature listed in “Bibli-
ography” on page 231.
A complete description of the Boundary-scan capabilities are given in the section “IEEE
1149.1 (JTAG) Boundary-scan” on page 232.
As shown in Figure 105, the hardware support for On-chip Debugging consists mainly of
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 Break Point Unit implements Break on Change of Program Flow, Single Step
Break, two Program Memory Break Points, and two combined Break Points. Together,
the four Break Points can be configured as either:
A debugger, like the AVR Studio, may however use one or more of these resources for
its internal purpose, leaving less flexibility to the end-user.
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 in this state, 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. In order to remain in the Shift-DR state,
the TMS input must be held low during input of all bits except the MSB. The MSB of
the data is shifted in when this state is left by setting TMS high. While the Data
Register is shifted in from the TDI pin, the parallel inputs to the Data Register
captured in the Capture-DR state is shifted 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.
A scan chain on the interface between the internal AVR CPU and the internal
peripheral units.
Break Point unit.
Communication interface between the CPU and JTAG system.
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”).
Independent of the initial state of the TAP Controller, the Test-Logic-Reset state can
always be entered by holding TMS high for five TCK clock periods.
ATmega169/V
229

Related parts for ATMEGA169