AT32UC3A464S Atmel Corporation, AT32UC3A464S Datasheet - Page 113

• Manufacturer Part Number: AT32UC3A464S
• Manufacturer: Atmel Corporation

Specifications of AT32UC3A464S

• Flash (kbytes): 64 Kbytes
• Pin Count: 100
• Max. Operating Frequency: 66 MHz
• Cpu: 32-bit AVR
• Hardware Qtouch Acquisition: No
• Usb Transceiver: 1
• Usb Speed: Hi-Speed
• Usb Interface: Device + OTG
• Spi: 6
• Twi (i2c): 2
• Uart: 4
• Ssc: 1
• Sd / Emmc: 2
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 8
• Adc Resolution (bits): 10
• Resistive Touch Screen: No
• Temp. Sensor: No
• Crypto Engine: AES
• Sram (kbytes): 128
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: Yes
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 3.0 to 3.6
• Operating Voltage (vcc): 3.0 to 3.6
• Fpu: No
• Mpu / Mmu: Yes / No
• Timers: 6
• Output Compare Channels: 6
• Input Capture Channels: 6
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

9.3.3.1
9.3.3.2
32002F–03/2010
Reset configuration
Message protocol
To be able to use AUX-based debug tools for AVR32, a circuit design using an AVR32 device
should use a Mictor38 connector (AMP P/N 767054-1) as defined in the Nexus standard, with
the pinout shown in Table 9-19.
Table 9-19.
The Nexus standard specifies that the AUX port can be enabled by keeping EVTI low while puls-
ing TRST (or exiting Test-Logic-Reset). The OCD system in AVR32 has removed this feature. In
order to enable the AUX port, the debugger has to write the AXC:AXE (Auxiliary Enable) bit.
The OCD System implements the Auxiliary Port Message Protocol defined in the Nexus stan-
dard. The following section is merely a summary of this protocol. For details, please see the
Nexus standard.
Messages are composed of a Start-of-Message (SOM) token, followed by one or more packets
of information, each of fixed or variable length, and ended by an End-of-Message (EOM) token.
SOM/EOM and End-of-Variable-Length-Packets (EVLP) are signalled by MSEO for transmitted
messages. Packet information is carried by the MDO pins. The number of MDO pins available is
known as the port boundary. The information carried by the MDO and MSEO pins each cycle is
known as a frame.
Signal
MSEO0
MSEO1
MCKO
EVTO_N
MDO0
MDO1
MDO2
MDO3
MDO4
MDO5
VREF
EVTI_N
AVR32 standard Nexus connector pinout. All directions relative to processor
Dir
Out
Out
Out
Out
Out
Out
Out
Out
Out
Out
N/C
N/C
N/C
Out
In
N/C
N/C
N/C
N/C
38
36
34
32
30
28
26
24
14
12
8
6
4
2
Pin
22
20
18
16
10
Pin
37
35
33
31
29
27
25
23
21
19
17
15
13
11
9
7
5
3
1
Dir
In
In
In
In
Out
In
Signal
N/C
N/C
N/C
N/C
N/C
N/C
N/C
N/C
TRST_N
TDI
TMS
TCK
N/C
TDO
RESET_N
N/C
N/C
N/C
N/C
AVR32
113