AT32UC3A1128 Atmel Corporation, AT32UC3A1128 Datasheet - Page 326

no-image

AT32UC3A1128

Manufacturer Part Number
AT32UC3A1128
Description
Manufacturer
Atmel Corporation

Specifications of AT32UC3A1128

Flash (kbytes)
128 Kbytes
Pin Count
100
Max. Operating Frequency
66 MHz
Cpu
32-bit AVR
# Of Touch Channels
32
Hardware Qtouch Acquisition
No
Max I/o Pins
69
Ext Interrupts
69
Usb Transceiver
1
Usb Speed
Full Speed
Usb Interface
Device + OTG
Spi
6
Twi (i2c)
1
Uart
4
Ssc
1
Ethernet
1
Graphic Lcd
No
Video Decoder
No
Camera Interface
No
Adc Channels
8
Adc Resolution (bits)
10
Adc Speed (ksps)
384
Resistive Touch Screen
No
Dac Channels
2
Dac Resolution (bits)
16
Temp. Sensor
No
Crypto Engine
No
Sram (kbytes)
32
Self Program Memory
YES
Dram Memory
No
Nand Interface
No
Picopower
No
Temp. Range (deg C)
-40 to 85
I/o Supply Class
3.0-3.6 or (1.65-1.95+3.0-3.6)
Operating Voltage (vcc)
3.0-3.6 or (1.65-1.95+3.0-3.6)
Fpu
No
Mpu / Mmu
Yes / No
Timers
10
Output Compare Channels
16
Input Capture Channels
6
Pwm Channels
13
32khz Rtc
Yes
Calibrated Rc Oscillator
Yes

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
AT32UC3A1128-AUR
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
AT32UC3A1128-AUT
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
AT32UC3A1128-U
Manufacturer:
ATMEL
Quantity:
13
32058K AVR32-01/12
Figure 26-28. Receiver Behavior when Operating with Hardware Handshaking
26.7.5
26.7.5.1
RXBUFF
US_CR
Write
RXD
RTS
ISO7816 Mode
RXEN = 1
ISO7816 Mode Overview
Setting the USART to operate with hardware handshaking is performed by writing the MODE
field in the Mode Register (MR) to the value 0x2.
The USART behavior when hardware handshaking is enabled is the same as the behavior in
standard synchronous or asynchronous mode, except that the receiver drives the RTS pin as
described below and the level on the CTS pin modifies the behavior of the transmitter as
described below. Using this mode requires using the PDC channel for reception. The transmitter
can handle hardware handshaking in any case.
Figure 26-28 on page 326
The RTS pin is driven high if the receiver is disabled and if the status RXBUFF (Receive Buffer
Full) coming from the PDC channel is high. Normally, the remote device does not start transmit-
ting while its CTS pin (driven by RTS) is high. As soon as the Receiver is enabled, the RTS falls,
indicating to the remote device that it can start transmitting. Defining a new buffer to the PDC
clears the status bit RXBUFF and, as a result, asserts the pin RTS low.
Figure 26-29 on page 326
enabled. The CTS pin disables the transmitter. If a character is being processing, the transmitter
is disabled only after the completion of the current character and transmission of the next char-
acter happens as soon as the pin CTS falls.
Figure 26-29. Transmitter Behavior when Operating with Hardware Handshaking
The USART features an ISO7816-compatible operating mode. This mode permits interfacing
with smart cards and Security Access Modules (SAM) communicating through an ISO7816 link.
Both T = 0 and T = 1 protocols defined by the ISO7816 specification are supported.
Setting the USART in ISO7816 mode is performed by writing the MODE field in the Mode Regis-
ter (MR) to the value 0x4 for protocol T = 0 and to the value 0x5 for protocol T = 1.
The ISO7816 is a half duplex communication on only one bidirectional line. The baud rate is
determined by a division of the clock provided to the remote device (see
on page
The USART connects to a smart card as shown in
becomes bidirectional and the Baud Rate Generator feeds the ISO7816 clock on the CLK pin.
305).
CTS
TXD
shows how the receiver operates if hardware handshaking is enabled.
shows how the transmitter operates if hardware handshaking is
Figure 26-30 on page
RXDIS = 1
”Baud Rate Generator”
AT32UC3A
327. The TXD line
326

Related parts for AT32UC3A1128