ATxmega64A3 Atmel Corporation, ATxmega64A3 Datasheet - Page 353

• Manufacturer Part Number: ATxmega64A3
• Manufacturer: Atmel Corporation

Specifications of ATxmega64A3

• Flash (kbytes): 64 Kbytes
• Pin Count: 64
• Max. Operating Frequency: 32 MHz
• Cpu: 8-bit AVR
• # Of Touch Channels: 16
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 50
• Ext Interrupts: 50
• Usb Speed: No
• Usb Interface: No
• Spi: 10
• Twi (i2c): 2
• Uart: 7
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 16
• Adc Resolution (bits): 12
• Adc Speed (ksps): 2000
• Analog Comparators: 4
• Resistive Touch Screen: No
• Dac Channels: 2
• Dac Resolution (bits): 12
• Temp. Sensor: Yes
• Crypto Engine: AES/DES
• Sram (kbytes): 4
• Eeprom (bytes): 2048
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: Yes
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 1.6 to 3.6
• Operating Voltage (vcc): 1.6 to 3.6
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 7
• Output Compare Channels: 22
• Input Capture Channels: 22
• Pwm Channels: 22
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

29.4.7
29.4.7.1
29.4.7.2
29.5
29.5.1
29.5.2
8077H–AVR–12/09
PDI Controller
Serial reception
Switching between PDI- and JTAG-mode
Accessing Internal Interfaces
Parity checker
BREAK detector
During reception, the receiver collects the eight data bits and the Parity bit from TDI and shifts
them into the shift register. Every time a valid frame is received, the data is latched in a parallel
way in the Update-DR state.
The Parity Checker calculates the parity (even mode) of the data bits in incoming frames and
compares the result with the parity bit from the serial frame. In case of a parity error, the PDI
Controller is signalized.
The Parity checker is active in both TX- and RX-mode. If a parity error is detected, the received
data byte is evaluated and compared with the BREAK character (which always will generate a
parity error). In case the BREAK character is recognized, the PDI Controller is signalized.
The PDI Controller includes data transmission/reception on a byte level, command decoding,
high-level direction control, control and status register access, exception handling, and clock
switching (PDI_CLK or TCK). The interaction between a programmer and the PDI Controller is
based on a scheme where the programmer transmits various types of requests to the PDI Con-
troller, which in turn responds in a way according to the specific request. A programmer request
comes in the form of an instruction, which may be followed by one or more byte operands. The
PDI Controller response may be silent (e.g. a data byte is stored to a location within the target),
or it may involve data to be returned back to the programmer (e.g. a data byte is read from a
location within the target).
The PDI Controller uses either the JTAG - or the PDI physical layer for establishing a connection
to the programmer. Based on this, the PDI is said to be in either JTAG or PDI mode. When one
of the modes are entered, the PDI Controller registers will be initialized, and the correct clock
source is selected by the clock system. It should be noted that the PDI mode has higher priority
than the JTAG mode. Hence, if the PDI mode is enabled while the PDI Controller is already in
JTAG mode, the access layer will automatically switch over to PDI mode. Still, if by some reason
a user wants to switch physical layer without power on/off the device, the active layer should be
disabled (to trigger a reset of the PDI) before the alternative physical layer is enabled.
After an external programmer has established communication with the PDI, the internal inter-
faces are not accessible by default. To get access to the NVM Controller and the NVM
memories for programming, a unique key must be signalized by using the KEY instruction. The
internal interfaces is accessed as one linear address space using a dedicated bus (PDIBUS)
between the PDI and the internal interfaces. The PDIBUS address space is the one shown in
Figure 30-4 on page
access to the NVMs. The PDI controller can only access the NVM and NVM controller in pro-
gramming mode. The PDI controller does not ever need to access the NVM controller's data or
address registers when reading or writing NVM.
380. The NVM controller must be enabled for the PDI controller to have any
XMEGA A
353