ATxmega64B3 Atmel Corporation, ATxmega64B3 Datasheet - Page 371

• Manufacturer Part Number: ATxmega64B3
• Manufacturer: Atmel Corporation

Specifications of ATxmega64B3

• 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: 36
• Ext Interrupts: 36
• Usb Transceiver: 1
• Usb Speed: Full Speed
• Usb Interface: Device
• Spi: 2
• Twi (i2c): 1
• Uart: 1
• Segment Lcd: 100
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 8
• Adc Resolution (bits): 12
• Adc Speed (ksps): 2000
• Analog Comparators: 2
• Resistive Touch Screen: No
• 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: 2
• Output Compare Channels: 6
• Input Capture Channels: 6
• Pwm Channels: 6
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

28.3.6
28.3.7
Figure 28-7. PDI direction change by inserting IDLE bits.
28.3.8
8291A–AVR–10/11
t S
Serial Reception
Direction Change
Drive Contention and Collision Detection
PDI DATA Receive (RX)
When a start bit is detected, the receiver starts to collect the eight data bits. If the parity bit does
not correspond to the parity of the data bits, a parity error has occurred. If one or both of the stop
bits are low, a frame error has occurred. If the parity bit is correct, and no frame error is detected,
the received data bits are available for the PDI controller.
When the PDI is in TX mode, a BREAK character signaled by the programmer will not be inter-
preted as a BREAK, but will instead cause a generic data collision. When the PDI is in RX mode,
a BREAK character will be recognized as a BREAK. By transmitting two successive BREAK
characters (which must be separated by one or more high bits), the last BREAK character will
always be recognized as a BREAK, regardless of whether the PDI was in TX or RX mode ini-
tially. This is because in TX mode the first BREAK is seen as a collision. The PDI then shifts to
RX mode and sees the second BREAK as break.
In order to ensure correct timing for half-duplex operation, a guard time mechanism is used.
When the PDI changes from RX mode to TX mode, a configurable number of IDLE bits are
inserted before the start bit is transmitted. The minimum transition time between RX and TX
mode is two IDLE cycles, and these are always inserted. The default guard time value is 128
bits.
1 DATA character
The external programmer will loose control of the PDI_DATA line at the point where the PDI
changes from RX to TX mode. The guard time relaxes this critical phase of the communication.
When the programmer changes from RX mode to TX mode, a single IDLE bit, at minimum,
should be inserted before the start bit is transmitted.
In order to reduce the effect of drive contention (the PDI and the programmer driving the
PDI_DATA line at the same time), a mechanism for collision detection is used. The mechanism
is based on the way the PDI drives data out on the PDI_DATA line. As shown in
page
Hence, if two or more successive bit values are the same, the value is actively driven only on the
first clock cycle. After this point, the PDI output driver is automatically tri-stated, and the
PDI_DATA pin has a bus keeper responsible for keeping the pin value unchanged until the out-
put driver is reenabled due to a change in the bit value.
Programmer to
PDI interface
Data from
372, the PDI output driver is active only when the output value changes (from 0-1 or 1-0).
P
Sp1
Sp2
Dir. change
IDLE bits
Guard time
# IDLE bits
inserted
t S
Atmel AVR XMEGA B
PDI DATA Transmit (TX)
1 DATA character
to Programmer
PDI interface
Data from
P
Figure 28-8 on
Sp1 Sp2
371