– Compact Single-cycle RISC Instruction Set Including DSP Instruction Set
– Read-Modify-Write Instructions and Atomic Bit Manipulation
– Performing 1.49 DMIPS / MHz
Up to 91 DMIPS Running at 66 MHz from Flash (1 Wait-State)
Up to 49 DMIPS Running at 33MHz from Flash (0 Wait-State)
– Memory Protection Unit
• Multi-hierarchy Bus System
– High-Performance Data Transfers on Separate Buses for Increased Performance
– 15 Peripheral DMA Channels Improves Speed f or Peripheral Communication
• Internal High-Speed Flash
– 512K Bytes, 256K Bytes, 128K Bytes Versions
– Single Cycle Access up to 33 MHz
– Prefetch Buffer Optimizing Instruction Execution at Maximum Speed
– 4ms Page Programming Time and 8ms Full-Chip Erase Time
– 100,000 Write Cycles, 15-year Data Retention Capability
– Flash Security Locks and User Defined Configuration Area
• Internal High-Speed SRAM, Single-Cycle Access at Full Speed
• External Memory Interface on AT32UC3A0 Derivatives
– SDRAM / SRAM Compatible Memory Bus (16-bit Data and 24-bit Address Buses)
• Interrupt Controller
– Autovectored Lo w Latency Interrupt Service with Programmable Priority
• System Functions
– Power and Clock Manager Including Internal RC Clock and One 32KHz Oscillator
– Two Multipurpose Oscillators and Two Phase-Lock-Loop (PLL) allowing
Independant CPU Frequency from USB Frequency
– Watchdog Timer, Real-Time Clock Timer
• Universal Serial Bus (USB)
– Device 2.0 Full Speed and On-The-Go (OTG) Low Speed and Full Speed
– Flexible End-Point Configuration and Management with Dedicated DMA Channels
– On-chip Transceivers Including Pull-Ups
• Ethernet MAC 10/100 Mbps interface
– 802.3 Ethernet Media Access Controller
– Supports Media Independent Interface (MII) and Reduced MII (RMII)
• One Three-Channel 16-bit Timer/Counter (TC)
– Three External Clock Inputs, PWM, Capture and Various Counting Capabilities
• One 7-Channel 16-bit Pulse Width Modulation Controller (PWM)
• Four Universal Synchronous/Asynchronous Receiver/Transmitters (USART)
– Independant Baudrate Generator, Support for SPI, IrDA and ISO7816 interfaces
– Support for Hardware Handshaking, RS485 Interfaces and Modem Line
• Two Master/Slave Serial Peripheral Interfaces (SPI) with Chip Select Signals
• One Synchronous Serial Protocol Controller
– Supports I2S and Generic Frame-Based Protocols
• One Master/Slave Two-Wire Interface (TWI), 400kbit/s I2C-compatible
• One 8-channel 10-bit Analog-To-Digital Converter
• Single 3.3V Power Supply or Dual 1.8V-3.3V Power Supply
AT32UC3A
32058HS–AVR32–03/09
2
1.Description
AT32UC3A
The AT32UC3A is a complete System-On-Chip microcontroller based on the AVR32 UC RISC
processor running at frequencies up to 66 MHz. AVR32 UC is a high-performance 32-bit RISC
microprocessor core, designed for cost- sensit ive embed ded applicat ion s, with p ar ticular emph asis on low power consumption, high code density and high performance.
The processor implements a Memory Protection Unit (MPU) and a fast and flexible int errupt controller for supporting modern operating systems and real-time operating systems. Higher
computation capabilities are achievable using a rich set of DSP instructions.
The AT32UC3A incorporates on-chip Flash and SRAM memories for secure and fast access.
For applications requiring additional memory, an external memory interface is provided on
AT32UC3A0 derivatives.
The Peripheral Direct Memory Access cont roller (PDCA) enables data transfers between peripherals and memories without processor involvement. PDCA drastically reduces processing
overhead when transferring continuous and large data streams between modules within the
MCU.
The PowerManager improves design flexibility and security: the on-chip Brown-Out Detector
monitors the power supply, the CPU runs from the on-chip RC oscillator or from one of external
oscillator sources, a Real-Time Clock and its associated timer keeps track of the time.
The Timer/Counter includes three identical 16-bit timer/counter channels. Each channel can be
independently programmed to perform frequency measurement, event counting, interval measurement, pulse generation, delay timing and pulse width modulation.
The PWM modules provides seven independent channels with many configuration options
including polarity, edge alignment and waveform non overlap control. O ne PWM channel can
trigger ADC conversions for more accurate close loop control implementations.
The AT32UC3A also features many communication interfaces for communication intensive
applications. In addition to standard serial int erfa ces like UART, SPI or TWI , ot he r int erface s like
flexible Synchronous Serial Controller, USB and Ethernet MAC are available.
The Synchronous Serial Controller provides easy access to serial communication protocols and
audio standards like I2S.
The Full-Speed USB 2.0 Device interface supports several USB Classes at the same time
thanks to the rich End-Point configuration. The On-The-GO (OTG) Host interface allows device
like a USB Flash disk or a USB printer to be directly connected to the processor.
The media-independent interface (MII) and reduced MII (RMII) 10/100 Ethernet MAC module
provides on-chip solutions for network-connecte d devices.
AT32UC3A integrates a class 2+ Nexus 2.0 On-Chip Debug (OCD) System, with non-intrusive
real-time trace, full-speed read/write memory access in addition to basic runtime control.
32058HS–AVR32–03/09
3
2.Configuration Summary
The table below lists all AT32UC3A memory and package configurations:
DeviceFlashSRAMExt. Bus Interface
AT32UC3A0512512 Kbytes64 Kbytesyesyes144 pin LQFP
• PDCA: Peripheral Direct Memory Access Controller (PDC) version A
• USBB: USB On-The-GO Controller version B
32058HS–AVR32–03/09
4
4.Blockdiagram
UC CPU
NEXUS
CLASS 2+
OCD
INS T R
INTERFACE
DATA
INTERFACE
TIMER/COUNTER
INTERRUPT
CONTROLLER
REAL TIME
COUNTER
PERIPHERAL
DMA
CONTROLLER
512 KB
FLASH
HSB-PB
BR IDGE B
HSB-PB
BRIDGE A
MEMORY INTERFACE
S
MM M
M
M
S
S
S
S
S
M
EXTERNAL
INTERRUPT
CONTROLLER
HIGH SPEED
BUS MATRIX
FAST GPIO
GENERAL PURPOSE IOs
64 KB
SRAM
GENERAL PURPOSE IOs
PA
PB
PC
PX
A[2..0]
B[2..0]
CLK[2..0]
EXTINT[7..0]
KPS [7 ..0 ]
NMI_N
GCLK[3..0]
XIN32
XOUT32
XIN0
XOUT0
PA
PB
PC
PX
RESET_N
EXTERNAL BUS INTERFACE
(SDRAM & STATIC MEMORY
CONTROLLER)
CAS
RAS
SDA10
SDCK
SDCKE
SDCS0
SDWE
NCS [3 ..0 ]
NRD
NWAIT
NWE0
DATA[15..0]
USB
INT E RFA CE
DMA
ID
VBOF
VBUS
D-
D+
ETHERNET
MAC
DMA
32 KHz
OSC
115 kHz
RCOSC
OSC0
PLL0
PULSE WIDTH
MODULATION
CONTROLLER
SERIAL
PERIPHERAL
INTERFACE 0/1
TWO-WIRE
INTERFACE
PDCPDCPDC
MISO, MOSI
NPC S[3..1]
PW M[6..0]
SCL
SDA
USART1
PDC
RXD
TXD
CLK
RTS, CTS
DSR, DTR, DCD, RI
USART0
USART2
USART3
PDC
RXD
TXD
CLK
RTS, CTS
SYNCHRONOUS
SERIAL
CONTROLLER
PDC
TX_CLOCK , TX_FR A ME _S Y NC
RX_DATA
TX_DATA
RX_CLOCK , RX_F RA M E _SY N C
ANALOG TO
DIGITAL
CONVERTER
PDC
AD[7 ..0 ]
ADVREF
WATCHDOG
TIMER
XIN1
XOUT1
OSC1
PLL1
SCK
JTAG
INT E RFA CE
MCKO
MDO[5..0]
MSE O[1..0]
EVTI_N
EVTO_N
TCK
TDO
TDI
TMS
POWER
MANAGER
RESET
CONTROLLER
ADD R [23..0]
SLEEP
CONTROLLER
CLOCK
CONTROLLER
CLOCK
GENERATOR
COL,
CRS,
RXD[3..0],
RX_CLK,
RX_DV,
RX_ER
MDC,
TXD [3..0 ],
TX_CLK,
TX_EN,
TX_ER,
SPEED
MDIO
FLASH
CONTROLLER
CONFIGURATION REGISTERS BUS
MEMORY PROTECTION UNIT
PB
PB
HSB
HS
B
NWE1
NWE3
PBA
PBB
NPCS0
LOCAL BUS
INTE R F ACE
AUDIO
BITSTREAM
DAC
PDC
DAT A [1 ..0 ]
DATAN[1..0]
Figure 4-1.Blockdiagram
AT32UC3A
32058HS–AVR32–03/09
5
4.1Processor and architecture
4.1.1AVR32 UC CPU
•
32-bit load/store AVR32A RISC architecture.
– 15 general-purpose 32-bit registers.
– 32-bit Stack Poin ter, Program Counter and Link Register reside in register file.
– Fully orthogonal instruction set.
– Privileged and unprivileged modes enabling efficient and secure Operating Systems.
– Innovative instruction set together with variable instruction length ensuring industry leading
code density.
– DSP extention with saturating arithmetic, and a wide variety of multiply instru ctio ns.
• 3 stage pipeline allows one instruction per clock cycle for most instructions.
– Byte, half-word, word and double word memory access.
– Multiple interrupt priority levels.
• MPU allows for operating systems with memory protection.
4.1.2Debug and Test system
IEEE1149.1 compliant JTAG and boundary scan
•
• Direct memory access and programming capabilities through JTAG interface
• Extensive On-Chip Debug features in compliance with IEEE-ISTO 5001-2003 (Nexus 2.0) Class 2+
– Low-cost NanoTrace supported.
• Auxiliary port for high-speed trace information
• Hardware support for 6 Program and 2 data breakpoints
• Unlimited number of software breakpoints supported
• Advanced Program, Data, Ownersh ip , and Watchpoint trace supported
AT32UC3A
4.1.3Peripheral DMA Controller
Transfers from/to peripheral to/from any memory space without intervention of the processor.
•
• Next Pointer Support, forbids strong real-time constraints on buffer management.
• Fifteen channels
– Two for each USART
– Two for each Serial Synchronous Controller
– Two for each Serial Peripheral Interface
– One for each ADC
– Two for each TWI Interface
4.1.4Bus system
High Speed Bus (HSB) matrix with 6 Masters and 6 Slaves handled
•
– Handles Requests from the CPU Data Fetch, CPU Instruction Fetch, PDCA, USBB, Ethernet
Controller, CPU SAB, and to internal Flash, internal SRAM, Peripheral Bus A, Peripheral Bus
B, EBI.
– Round-Robin Arbitration (three modes supported: no default master, last
master, fixed default master)
– Burst Breaking with Slot Cycle Limit
– One Address Decoder Provided per Master
accessed default
32058HS–AVR32–03/09
6
AT32UC3A
• Peripheral Bus A able to run on at divided bus speeds compared to the High Speed Bus
Figure 4-1 gives an overview of the bus system. All modules connected to the same bus use the
same clock, but the clock to each module can be individually shut off by the Power Manage r.
The figure identifies the number o f mast er and slave int er faces of each mo du le con nected t o the
High Speed Bus, and which DMA controller is connected to which peripheral.
32058HS–AVR32–03/09
7
5.Signals Description
The following table gives details on the signal name classified by peripheral
The signals are multiplexed with GPIO pins as described in ”Peripheral Multiplexing on I/O lines”
The AT32UC3A has several types of power supply pins:
•
VDDIO: Powers I/O lines. Voltage is 3.3V nominal.
• VDDANA: P owers the ADC Voltage is 3.3V nominal.
• VDDIN: Input voltage for the voltage regulator. Voltage is 3.3V nomin al.
• VDDCORE: Powers the core, memories, and peripherals. Voltage is 1.8V nominal.
• VDDPLL: Powers the PLL. Voltage is 1.8V nominal.
The ground pins GND are common to VDDCORE, VDDIO, VDDPLL. The ground pin for
VDDANA is GNDANA.
Refer to ”Power Consumption” on page 44 for power consumption on the va rious supply pins.
AT32UC3A
32058HS–AVR32–03/09
17
7.2Voltage Regulator
3.3V
1.8V
VDDIN
VDDOUT
1.8V
Regulator
C
IN1
C
OUT1
C
OUT2
C
IN2
VDDIN
VDDOUT
7.2.1Single Power Supply
The AT32UC3A embeds a voltage regulator tha t converts from 3.3V to 1.8V. The r egulator takes
its input voltage from VDDIN, and supplies the output voltage on VDDOUT. VDDOUT should be
externally connected to the 1.8V domains.
Adequate input supply decoupling is mandatory for VDDIN in order to improve startup stability
and reduce source voltage drop. Two input decoupling capacitors must be placed close to the
chip.
Adequate output supply decoupling is mandatory for VDDOUT to reduce ripple and avoid oscillations. The best way to achieve this is to use two capacitors in parallel between VDDOUT and
GND as close to the chip as possible
AT32UC3A
Refer to Section 12.3 on page 42 for decoupling capacitors values and regulator characteristics
7.2.2Dual Power Supply
In case of dual power supply, VDDIN and VDDOUT should be connected to ground to prevent
from leakage current.
32058HS–AVR32–03/09
18
7.3Analog-to-Digital Converter (A.D.C) reference.
A DVREF
CC
VREF1VREF2
3.3V
The ADC reference (ADVREF) must be provided from an external source. Two decoupling
capacitors must be used to insure proper decoupling.
Refer to Section 12.4 on page 42 for decoupling capacitors values and electrical characteristics.
In case ADC is not used, the ADVREF pin should be connected to GND to avoid extra
consumption.
AT32UC3A
32058HS–AVR32–03/09
19
8.I/O Line Considerations
8.1JTAG pins
TMS, TDI and TCK have pull-up resistors. TDO is an output, driven at up to VDDIO, and has no
pull-up resistor.
8.2RESET_N pin
The RESET_N pin is a schmitt input and integrates a perm anent pull-up resistor to VDDIO. As
the product integrates a power-on reset cell, the RESET_N pin can be left unconnected in case
no reset from the system needs to be applied to the product.
8.3TWI pins
When these pins are used for TWI, the pins are open-drain outputs with slew-rate limitation and
inputs with inputs with spike-filtering. When used as GPIO-pins or used for ot her peripher als, the
pins have the same characteristics as PIO pins.
8.4GPIO pins
All the I/O lines integrate a programmable pull-up re sistor. Programming of this pull-up resistor is
performed independently for each I/O line through the GPIO Controllers. After reset, I/O lines
default as inputs with pull-up resistors disabled, except when indicated otherwise in the column
“Reset State” of the GPIO Controller multiplexing table s.
The system bus is implemented as a bus matrix. All system bus addresses are fixed, and they
are never remapped in any way, not even in boot. Note that AVR32 UC CPU uses unsegment ed
translation, as described in the AVR32 Architecture Manual. The 32-bit physical address space
is mapped as follows:
Accesses to unused areas returns an error result to the master requesting such an access.
The bus matrix has the several masters and slaves. Each master has its own bus and its own
decoder, thus allowing a different memory mapping per master. The master number in the table
below can be used to index the HMATRIX control registers. For example, MCFG0 is associated
with the CPU Data master interface.
AT32UC3A
Fuse bits
(FLASH_F)
Table 9-3.High Speed Bus masters
Master 0CPU Data
Master 1CPU Instruction
Master 2CPU SAB
Master 3PDCA
Master 4MACB DMA
Master 5USBB DMA
Each slave has its own arbiter, thus allowing a different arbitration per slave. The slave number
in the table below can be used to index the HMATRIX control registers. For example, SCFG3 is
associated with the Internal SRAM Slave Interface.
Some of the registers in the GPIO module are mapped onto the CPU local bus, in addition to
being mapped on the Peripheral Bus. These registers can therefore be reached both by
accesses on the Peripheral Bus, and by accesses on the local bus.
Mapping these registers on the local bus allows cycle-deterministic toggling of GPIO pins since
the CPU and GPIO are the only modules connected to this bus. Also, since the local bus runs at
CPU speed, one write or read operation can be performed per clock cycle to the local busmapped GPIO registers.
32058HS–AVR32–03/09
25
AT32UC3A
The following GPIO registers are mapped on the local bus:
Output Value Register (OVR)WRITE0x4000_0 350Write-only
Pin Value Register (PVR)-0x4000_0360Read-only
10.3Interrupt Request Signal Map
The various modules may output Interrupt request signals. These signals are routed to th e Inte rrupt Controller (INTC), described in a later chapter. The Interrupt Controller supports up to 64
groups of interrupt requests. Each group can ha ve up to 32 inte rrupt request sign als. All interrupt
signals in the same group share the same autovector address and priority level. Refer to the
documentation for the individual submodules for a description of the semantics of the different
interrupt requests.
Each USART can be connected to an internally divided clock:
Table 10-5.USART clock connections
32058HS–AVR32–03/09
USARTSourceNameConnection
0InternalCLK_DIVPBA clock / 8
1
2
3
29
10.4.3SPIs
Each SPI can be connected to an internally divided clock:
Table 10-6.SPI clock connections
SPISourceNameConnection
0InternalCLK_DIVPBA clock or
1
10.5Nexus OCD AUX port connections
If the OCD trace system is enabled, the trace system will take control over a number of pins, irrespectively of the PIO configuration. Two different OCD trace pin mappings are possible,
depending on the configuration of the OCD AXS register. For details, see the AVR32 UC Technical Reference Manual.
The PDC and the peripheral modules communicate t hro ugh a set of han dshake sign als. The f ollowing table defines the valid settings for the Peripheral Identifier (PID) in the PDC Peripheral
Select Register (PSR).
Each GPIO line can be assigned to one of 3 peripheral functions; A, B or C. The following table
define how the I/O lines on the peripherals A, B and C are multiplexed by the GPIO.
Table 10-9.GPIO Controller Function Multiplexing
TQFP100VQFP144PINGPIO PinFunction AFunction BFunction C
The oscillators are not mapped to the normal A,B or C functions and their muxings are controlled
by registers in the Power Manager (PM). Please refer to the power manager chapter for more
information about this.
The GPIO open drain feature (GPIO ODMER register (Open Drain Mode Enable Register)) is
not available for this device.
10.11 Peripheral overview
10.11.1External Bus Interface
Optimized for Application Memory Space support
•
• Integrates Two External Memory Controllers:
– Static Memory Controller
– SDRAM Controller
• Optimized External Bus:
–16-bit Data Bus
– 24-bit Address Bus, Up to 16-M bytes Addressable
– Optimized pin multiplexing to reduce latencies on External Memories
• 4 SRAM Chip Selects, 1SDRAM Chip Select:
– Static Memory Controller on NCS0
– SDRAM Controller or Static Memory Controller on NCS1
– Static Memory Controller on NCS2
– Static Memory Controller on NCS3
10.11.2Static Memory Controller
AT32UC3A
•
• 64-Mbyte Address Space per Chip Select
• 8-, 16-bit Data Bus
• Word, Halfword, Byte Transfers
• Byte Write or Byte Select Lines
• Programmable Setup, Pulse And Hold Time for Read Signals per Chip Select
• Programmable Setup, Pulse And Hold Time for Write Signals per Chip Select
• Programmable Data Float Time per Chip Select
• Compliant with LCD Module
• External Wait Request
• Automatic Switch to Slow Clock Mode
• Asynchronous Read in Page Mode Supported: Page Size Ranges from 4 to 32 Bytes
10.11.3SDRAM Controller
•
• Programming Facilities
• Energy-saving Capabilities
4 Chip Selects Available
Numerous Configurations Supported
– 2K, 4K, 8K Row Address Memory Parts
– SDRAM with Two or Four Internal Banks
– SDRAM with 16-bit Data Path
– Word, Half-word, Byte Access
– Automatic Page Break When Memory Boundary Has Been Reached
– Multibank Ping-pong Access
– Timing Parameters Specified by Software
– Automatic Refresh Operation, Refresh Rate is Programmable
– Self-refresh, Power-down and Deep Power Modes Supported
32058HS–AVR32–03/09
35
– Supports Mobile SDRAM Devices
• Error Detection
– Refresh Error Interrupt
• SDRAM Power-up Initialization by Software
• CAS Latency of 1, 2, 3 Supported
• Auto Precharge Command Not Used
10.11.4USB Controller
USB 2.0 Compliant, Full-/Low-Speed (FS/LS) and On-The-Go (OTG), 12 Mbit/s
•
• 7 Pipes/Endpoints
• 960 bytes of Embedded Dual-Port RAM (DPRAM) for Pipes/Endpoints
• Up to 2 Memory Banks per Pipe/Endpoint (Not for Control Pipe/Endpoint)
• Flexible Pipe/Endpoint Configuration and Management with D edicated DMA Channels
• On-Chip Transceivers Including Pull-Ups
10.11.5Serial Peripheral Interface
Supports communication with serial external devices
•
– Four chip selects with external decoder support allow communication with up to 15
peripherals
– Serial memories, such as DataFlash and 3-wire EEPROMs
– Serial peripherals, such as ADCs, DACs, LCD Controllers, CAN Controllers and Sensors
– External co-processors
• Master or slave serial peripheral bus interface
– 8- to 16-bit programmable data length per chip select
– Programmable phase and polarity per chip select
– Programmable transfer delays between consecutive transfers and between clock and data
per chip select
– Programmable delay between consecutive transfers
– Selectable mode fault detection
• Very fast transfers supported
– Transfers with baud rates up to Peripheral Bus A (PBA) max frequency
– The chip select line may be left active to speed up transfers on the same device
10.11.6Two-wire Interface
AT32UC3A
10.11.7USART
32058HS–AVR32–03/09
High speed up to 400kbit/s
•
• Compatibility with standard two-wire serial memory
• One, two or three bytes for slave address
• Sequential read/write operations
Programmable Baud Rate Generator
•
• 5- to 9-bit full-duplex synchronous or asynchronous serial communications
– 1, 1.5 or 2 stop bits in Asynchronous Mode or 1 or 2 stop bits in Synchronous Mode
– Parity generation and error detection
– Framing error detection, overrun error detection
– MSB- or LSB-first
– Optional break generation and detection
– By 8 or by-16 over-sampling receiver frequency
– Hardware handshaking RTS-CTS
– Receiver time-out and transmitter timegu ard
– Optional Multi-drop Mode with address generation and detection
36
– Optional Manchester Encoding
• RS485 with driver control signal
• ISO7816, T = 0 or T = 1 Protocols for interfacing with smart cards
– NACK handling, err o r counter with repet itio n an d iterati on limit
• IrDA modulation and demodulation
– Communication at up to 115.2 Kbps
• Test Modes
– Remote Loopback, Local Loopback, Automatic Echo
• SPI Mode
– Master or Slave
– Serial Clock Programmable Phase and Polarity
– SPI Serial Clock (SCK) Frequency up to Internal Clock Frequency PBA/4
• Supports Connection of Two Peripheral DMA Controller Channels (PDC)
– Offers Buffer Transfer without Processor Intervention
10.11.8Serial Synchronous Controller
Provides serial synchronous communication links used in audio and telecom applications (with
•
CODECs in Master or Slave Modes, I2S, TDM Buses, Magnetic Card Reader, etc.)
• Contains an independent receiver and transmitter and a common clock divider
• Offers a configurable frame sync and data length
• Receiver and transmitter can be programmed to start automatically or on detection of different
event on the frame sync signal
• Receiver and transmitter include a data signal, a clock signal and a frame synchronization signal
– Three external clock inputs
– Five internal clock inputs
– Two multi-purpose input/output signals
• Two global registers that act on all three TC Channels
10.11.10 Pulse Width Modulation Controller
7 channels, one 20-bit counter per channel
•
• Common clock generator, providing Thirteen Different Clocks
– A Modulo n counter providing eleven clocks
– Two independent Linear Dividers working on modulo n counter outputs
• Independent channel programming
– Independent Enable Disable Commands
– Independent Clock
– Independent Period and Duty Cycle, with Double Bufferization
– Programmable selection of the output waveform polarity
– Programmable center or left aligned output waveform
32058HS–AVR32–03/09
37
10.11.11 Ethernet 10/100 MAC
Compatibility with IEEE Standard 802.3
•
• 10 and 100 Mbits per second data throughput capability
• Full- and half-duplex operations
• MII or RMII interface to the physical layer
• Register Interface to address, data, status and control registers
• DMA Interface, operating as a master on the Memory Controller
• Interrupt generation to signal receive and transmit completion
• 28-byte transmit and 28-byte receive FIFOs
• Automatic pad and CRC generation on transmitted frames
• Address checking logic to recognize four 48-bit addresses
• Support promiscuous mode where all valid frames are copied to memory
• Support physical layer management through MDIO interface control of alarm and update
time/calendar data
10.11.12 Audio Bitstream DAC
Digital Stereo DAC
•
• Oversampled D/A conversion architecture
– Oversampling ratio fixed 128x
– FIR equalization filter
– Digital interpolation filter: Comb4
– 3rd Order Sigma-Delta D/A converters
• Digital bitstream outputs
• Parallel interface
• Connected to Peripheral DMA Controller for background transfer without CPU intervention
AT32UC3A
32058HS–AVR32–03/09
38
11. Boot Sequence
This chapter summarizes the boot sequence of the AT32UC3A. The behaviou r afte r power- up is
controlled by the Power Manager. For specific details, refer to Section 13. ”Power Manager
(PM)” on page 53.
11.1Starting of clocks
After power-up, the device will be held in a reset state by the Power-On Reset circuitry, until the
power has stabilized throughout the device. Once th e power has stabilized, the device will use
the internal RC Oscillator as clock source.
On system start-up, the PLLs are disabled. All clocks to all modules are running. No clocks have
a divided frequency, all parts of the system recieves a clock with the same frequency as the
internal RC Oscillator.
11.2Fetching of initial instructions
After reset has been released, the AVR32 UC CPU starts fetching instructions from the reset
address, which is 0x8000_0000. This address points to the first address in the internal Flash.
The code read from the internal Flash is free to configure the system to use for example the
PLLs, to divide the frequency of the clock routed to some of the peripherals, and to gate the
clocks to unused peripherals.
AT32UC3A
32058HS–AVR32–03/09
39
12. Electrical Characteristics
12.1Absolute Maximum Ratings*
Operating Temperature......................................-40⋅C to +85⋅C
Storage Temperature..................................... -60°C to +150°C
Voltage on Input Pin
with respect to Ground except for PC00, PC01, PC02, PC03,
PC04, PC05..........................................................-0.3V to 5.5V
Voltage on Input Pin
with respect to Ground for PC00, PC01, PC02, PC03, PC04,
PC05.....................................................................-0.3V to 3.6V
Maximum Operating Voltage (VDDCORE, VDDPLL)..... 1.95V
Maximum Operating Voltage (VDDIO, VDDIN, VDDANA).3.6V
Total DC Output Current on all I/O Pin
for TQFP100 package.................................................370 mA
for LQGP144 package................................................. 470 mA
AT32UC3A
*NOTICE:Stresses beyond those listed under “Absolute
Maximum Ratings” may cause permanent damage to the device. This is a stress rating only and
functional operation of the device at these or
other conditions beyond those indicated in the
operational sections of this specification is not
implied. Exposure to absolute maximum rating
conditions for extended periods may affect
device reliability.
32058HS–AVR32–03/09
40
AT32UC3A
12.2DC Characteristics
The following characteristics are applicable to t he operating temp erature rang e: TA = -40°C to 85°C, unless otherwise specified and are certified for a junction temperature up to T
Table 12-1.DC Characteristics
SymbolParameterConditionMin.Typ.MaxUnits
V
VDDCOR
E
V
VDDPLL
V
VDDIO
V
REF
V
IL
V
IH
V
OL
V
OH
I
OL
I
OH
DC Supply Core1.651.95V
DC Supply PLL1.651.95V
DC Supply Peripheral I/Os3.03.6V
Analog reference voltage2.63.6V
Input Low-level Voltage-0.3+0.8V
Voltage reference Capacitor 110-nF
Voltage reference Capacitor 21-uF
Table 12-6.BODLEVEL Values
BODLEVEL Value
00 0000b
01 0111b
01 1111b
Typ.Typ.Typ.Units.
1.401.471.55V
1.451.521.6V
1.551.61.65V
32058HS–AVR32–03/09
10 0111b
1.651.691.75V
The values in Table 12-6 describes the values of the BODLEVEL in the flash FGPFR register.
42
AT32UC3A
Table 12-7.BOD Timing
SymbolParameterTest ConditionsTyp.Max.Units.
Minimum time with
T
BOD
VDDCORE < VBOD to
detect power failure
Falling VDDCORE
from 1.8V to 1.1V
300800ns
12.4.2POR
Table 12-8.Electrical Characteristic
SymbolParameterTest ConditionsMin.Typ.Max.Units.
V
DDRR
V
SSFR
V
POR+
V
POR-
V
RESTART
T
POR
VDDCORE rise rate to ensure power-on-reset0.01V/ms
VDDCORE fall rate to ensure power-on-reset0.01400V/ms
Rising threshold voltage: voltage up to which
device is kept under reset by POR on rising
VDDCORE
Falling threshold voltage: voltage when POR
resets device on falling VDDCORE
On falling VDDCORE, voltage must go down to
this value before supply can rise again to ensure
reset signal is released at
Minimum time with VDDCORE < V
V
POR+
POR-
Rising VDDCORE:
V
RESTART
-> V
POR+
Falling VDDCORE:
1.8V -> V
POR+
Falling VDDCORE:
1.8V -> V
RESTART
Falling VDDCORE:
1.8V -> 1.1V
1.351.51.6V
1.251.31.4V
-0.10.5V
15us
T
RST
Time for reset signal to be propagated to system200400us
32058HS–AVR32–03/09
43
12.5Po wer Consumption
Internal
Voltage
Regulator
Amp0
Amp1
VDDANA
VDDIO
VDDIN
VDDOUT
VDDCORE
VDDPLL
The values in Table 12-9 and Table 12-10 on page 46 are measured values of power consumption with operating conditions as follows:
•V
DDIO
•V
DDCORE
•T
A = 25°C, TA = 85°C
•I/Os are configured in input, pull-up enabled.
Figure 12-1. Measurement setup
= 3.3V
= V
DDPLL
AT32UC3A
= 1.8V
32058HS–AVR32–03/09
44
These figures represent the power consumption me asured on the power supplies.
Table 12-9.Power Consumption for Different Modes
ModeConditionsTyp.Unit
AT32UC3A
Active
Idle
Frozen
Typ : Ta =25 °C
(1)
CPU running from flash
.
VDDIN=3.3 V. VDDCORE =1.8V.
CPU clocked from PLL0 at f MHz
V o ltage regulator is on.
XIN0 : external clock.
(1)
XIN1 stopped. XIN32 stopped
PLL0 running
All peripheral clocks activated.
GPIOs on internal pull-up.
JTAG unconnected with ext pull-up.
Typ : Ta = 25 °C
(1)
CPU running from flash
.
VDDIN=3.3 V. VDDCORE =1.8V.
CPU clocked from PLL0 at f MHz
V o ltage regulator is on.
XIN0 : external clock.
XIN1 stopped. XIN32 stopped
PLL0 running
All peripheral clocks activated.
GPIOs on internal pull-up.
JTAG unconnected with ext pull-up.
Typ : Ta = 25 °C
(1)
CPU running from flash
.
CPU clocked from PLL0 at f MHz
V o ltage regulator is on.
XIN0 : external clock.
XIN1 stopped. XIN32 stopped
PLL0 running
All peripheral clocks activated.
GPIOs on internal pull-up.
JTAG unconnected with ext pull-up.
f = 12 MHz9mA
f = 24 MHz15mA
f = 36MHz20mA
f = 50 MHz28mA
f = 66 MHz36.3mA
f = 12 MHz5mA
f = 24 MHz10mA
f = 36MHz14mA
f = 50 MHz19mA
f = 66 MHz25.5mA
f = 12 MHz3mA
f = 24 MHz6mA
f = 36MHz9mA
f = 50 MHz13mA
f = 66 MHz16.8mA
Typ : Ta = 25 °C
CPU running from flash
CPU clocked from PLL0 at f MHz
V o ltage regulator is on.
Standby
XIN0 : external clock.
XIN1 stopped. XIN32 stopped
PLL0 running
All peripheral clocks activated.
GPIOs on internal pull-up.
JTAG unconnected with ext pull-up.
32058HS–AVR32–03/09
(1)
.
f = 24 MHz2mA
f = 36MHz3mA
f = 50 MHz4mA
f = 66 MHz4.8mA
45
f = 12 MHz1mA
Table 12-9.Power Consumption for Different Modes
ModeConditionsTyp.Unit
Stop
Deepstop
Static
Typ : Ta = 25 °C.
CPU is in stop mode
GPIOs on internal pull-up.
All peripheral clocks de-activated.
DM and DP pins connected to ground.
XIN0,Xin1 and XIN2 are stopped
Typ : Ta = 25 °C.CPU is in deepstop mode
GPIOs on internal pull-up.
All peripheral clocks de-activated.
DM and DP pins connected to ground.
XIN0,Xin1 and XIN2 are stopped
Typ : Ta = 25 °C. CPU is in static mode
GPIOs on internal pull-up.
All peripheral clocks de-activated.
DM and DP pins connected to ground.
XIN0,Xin1 and XIN2 are stopped
on Amp047uA
on Amp140uA
on Amp036uA
on Amp128uA
on Amp025uA
on Amp114uA
AT32UC3A
1.Core frequency is generated from XIN0 using the PLL so that 140 MHz < fpll0 < 160 MHz and 10 MHz < fxin0
< 12MHz
Table 12-10. Power Consumption by Peripheral in Active Mode
These parameters are given in the following conditions:
32058HS–AVR32–03/09
46
AT32UC3A
•V
DDCORE
= 1.8V
• Ambient Temperature = 25°C
12.6.1CPU/HSB Clock Characteristics
Table 12-11. Core Clock Waveform Parameters
SymbolParameterConditionsMinMaxUnits
1/(t
t
CPCPU
)CPU Clock Frequency66MHz
CPCPU
CPU Clock Period15,15ns
12.6.2PBA Clock Characteristics
Table 12-12. PBA Clock Waveform Parameters
SymbolParameterConditionsMinMaxUnits
1/(t
t
CPPBA
)PBA Clock Frequency66MHz
CPPBA
PBA Clock Period15,15ns
12.6.3PBB Clock Characteristics
Table 12-13. PBB Clock Waveform Parameters
SymbolParameterConditionsMinMaxUnits
1/(t
t
CPPBB
)PBB Clock Frequency66MHz
CPPBB
PBB Clock Period15,15ns
12.7Crystal Oscillator Characteristis
The following characteristics are applicable to the operating temperature range: TA = -40°C to 85°C and worst case of
power supply, unless otherwise specified.
12.7.132 KHz Oscillator Characteristics
Table 12-14. 32 KHz Oscillator Characteristics
SymbolParameterConditionsMinTypMaxUnit
1/(t
C
L
t
ST
I
OSC
Note:1. CL is the equivalent load capacitance.
)Crystal Oscillator Frequency32 768Hz
CP32KHz
Equivalent Load Capacitance612.5pF
Startup Time
C
CL = 12.5pF
= 6pF
L
(1)
(1)
600
1200
ms
Active mode1.8µA
Current Consumption
Standby mode0.1µA
32058HS–AVR32–03/09
47
AT32UC3A
12.7.2Main Oscillators Characteristic s
Table 12-15. Main Oscillator Characteristics
SymbolParameterConditionsMinTypMaxUnit
1/(t
C
L1
)Crystal Oscillator Frequency0.4516MHz
CPMAIN
, C
L2
Internal Load Capacitance
= CL2)
(C
L1
12pF
Duty Cycle405060%
t
ST
Startup TimeTBDms
External clock50MHz
1/(t
t
t
C
)XIN Clock Frequency
CPXIN
CHXIN
CLXIN
IN
XIN Clock High Half-period
XIN Clock Low Half-period
XIN Input CapacitanceTBDpF
Crystal0.4516MHz
0.4 x
t
CPXIN
0.4 x
t
CPXIN
0.6 x
t
CPXIN
0.6 x
t
CPXIN
12.7.3PLL Characteristics
Table 12-16. Phase Lock Loop Characteristics
SymbolParameterConditionsMinTypMaxUnit
F
F
I
OUT
IN
PLL
Output Frequency80240MHz
Input FrequencyTBDTBDMHz
active modeTBDmA
Current Consumption
standby modeTBDµA
32058HS–AVR32–03/09
48
AT32UC3A
12.8ADC Characteristics
Table 12-17. Channel Conversion Time and ADC Clock
SDCKE High before SDCK Rising Edge
SDCKE Low after SDCK Rising Edge
SDCKE Low before SDCK Rising Edge
SDCKE High after SDCK Rising Edge
SDCS Low before SDCK Rising Edge
SDCS High after SDCK Rising Edge
RAS Low before SDCK Rising Edge
RAS High after SDCK Rising Edge
SDA10 Change before SDCK Rising Edge
SDA10 Change after SDCK Rising Edge
Address Change before SDCK Rising Edge
Address Change after SDCK Rising Edge
Bank Change before SDCK Rising Edge
Bank Change after SDCK Rising Edge
CAS Low before SDCK Rising Edge
CAS High after SDCK Rising Edge
DQM Change before SDCK Rising Edge
DQM Change after SDCK Rising Edge
D0-D15 in Setup before SDCK Rising Edge
D0-D15 in Hold after SDCK Rising Edge
SDWE Low before SDCK Rising Edge
SDWE High after SDCK Rising Edge
D0-D15 Out Valid before SDCK Rising Edge
D0-D15 Out Valid after SDCK Rising Edge
TCK Low Half-period
TCK High Half-period
TCK Period
TDI, TMS Setup before TCK High
TDI, TMS Hold after TCK High
TDO Hold Time
TCK Low to TDO Valid
Device Inputs Setup Time
Device Inputs Hold Time
Device Outputs Hold Time
TCK to Device Outputs Valid
(1)
6ns
(1)
3ns
(1)
9ns
(1)
1ns
(1)
0ns
(1)
4ns
(1)
6ns
(1)
ns
(1)
ns
(1)
ns
(1)
ns
Note:1. V
from 3.0V to 3.6V, maximum external capacitor = 40pF
VDDIO
32058HS–AVR32–03/09
57
Figure 12-5. JTAG Interface Signals
TCK
JTAG
9
TMS/TDI
TDO
Device
Outputs
JTAG
5
JTAG
4
JTAG
3
JTAG
0
JTAG
1
JTAG
2
JTAG
10
Device
Inputs
JTAG
8
JTAG
7
JTAG
6
SPCK
MISO
MOSI
SPI
2
SPI
0
SPI
1
AT32UC3A
12.11 SPI Characteristics
Figure 12-6. SPI Master mode with (CPOL = NCPHA = 0) or (CPOL= NCPHA= 1)
32058HS–AVR32–03/09
58
AT32UC3A
SPCK
MISO
MOSI
SPI
5
SPI
3
SPI
4
SPCK
MISO
MOSI
SPI
6
SPI
7
SPI
8
SPCK
MISO
MOSI
SPI
9
SPI
10
SPI
11
Figure 12-7. SPI Master mode with (CPOL=0 and NCPHA=1) or (CPOL=1 and NCPHA=0)
Figure 12-8. SPI Slave mode with (CPOL=0 and NCPHA=1) or (CPOL=1 and NCPHA=0)
32058HS–AVR32–03/09
Figure 12-9. SPI Slave mode with (CPOL = NCPHA = 0) or (CPOL= NCPHA= 1)
59
AT32UC3A
Table 12-30. SPI Timings
SymbolParameterConditionsMinMaxUnits
SPI
SPI
SPI
SPI
SPI
SPI
SPI
SPI
SPI
SPI
SPI
SPI
0
1
2
3
4
5
6
7
8
9
10
11
MISO Setup time before SPCK rises (master)3.3V domain
MISO Hold time after SPCK rises (master)3.3V domain
SPCK rising to MOSI Delay (master)3.3V domain
MISO Setup time before SPCK falls (master)3.3V domain
MISO Hold time after SPCK falls (master)3.3V domain
SPCK falling to MOSI Delay (master)3.3V domain
SPCK falling to MISO Delay (slave)3.3V domain
MOSI Setup time before SPCK rises (slave)3.3V domain
MOSI Hold time after SPCK rises (slave)3.3V domain
SPCK rising to MISO Delay (slave)3.3V domain
MOSI Setup time before SPCK falls (slave)3.3V domain
MOSI Hold time after SPCK falls (slave)3.3V domain
(1)
22 + (t
CPMCK
(1)
(1)
(1)
22 + (t
CPMCK
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
1.5ns
(2)
)/2
0ns
7ns
(2)
)/2
0ns
7ns
26.5ns
0ns
27ns
0ns
1ns
ns
ns
Notes: 1. 3.3V domain: V
2. t
: Master Clock period in ns.
CPMCK
from 3.0V to 3.6V, maximum external capacitor = 40 pF.
VDDIO
12.12 MACB Characteristics
Table 12-31. Ethernet MAC Signals
SymbolParameterConditionsMin (ns)Max (ns)
EMAC
EMAC
EMAC
1
2
3
Setup for EMDIO from EMDC risingLoad: 20pF
Hold for EMDIO from EMDC risingLoad: 20pF
EMDIO toggling from EMDC fallingLoad: 20pF
Notes: 1. f: MCK frequency (MHz)
2. V
from 3.0V to 3.6V, maximum external capacitor = 20 pF
VDDIO
Table 12-32. Ethernet MAC MII Specific Signals
SymbolParameterConditionsMin (ns)Max (ns)
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
4
5
6
7
8
9
10
11
Setup for ECOL from ETXCK risingLoad: 20pF
Hold for ECOL from ETXCK risingLoad: 20pF
Setup for ECRS from ETXCK risingLoad: 20pF
Hold for ECRS from ETXCK risingLoad: 20pF
ETXER toggling from ETXCK risingLoad: 20pF
ETXEN toggling from ETXCK risingLoad: 20pF
ETX toggling from ETXCK risingLoad: 20pF
Setup for ERX from ERXCKLoad: 20pF
(2)
(2)
(2)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
3
0
3
0
15
15
15
1
32058HS–AVR32–03/09
60
AT32UC3A
EMDC
EMDIO
ECOL
ECRS
ETXCK
ETXER
ETXEN
ETX[3:0]
ERXCK
ERX[3:0]
ERXER
ERXDV
EMAC
3
EMAC
1
EMAC
2
EMAC
4
EMAC
5
EMAC
6
EMAC
7
EMAC
8
EMAC
9
EMAC
10
EMAC
11
EMAC
12
EMAC
13
EMAC
14
EMAC
15
EMAC
16
Table 12-32. Ethernet MAC MII Specific Signals
SymbolParameterConditionsMin (ns)Max (ns)
EMAC
EMAC
EMAC
EMAC
EMAC
12
13
14
15
16
Hold for ERX from ERXCKLoad: 20pF
Setup for ERXER from ERXCKLoad: 20pF
Hold for ERXER from ERXCKLoad: 20pF
Setup for ERXDV from ERXCKLoad: 20pF
Hold for ERXDV from ERXCKLoad: 20pF
(1)
(1)
(1)
(1)
(1)
1.5
1
0.5
1.5
1
Note:1. V
from 3.0V to 3.6V, maximum external capacitor = 20 pF
VDDIO
Figure 12-10. Ethernet MAC MII Mode
32058HS–AVR32–03/09
61
AT32UC3A
EREFCK
ETXEN
ETX[1:0]
ERX[1:0]
ERXER
ECRSDV
EMAC
21
EMAC
22
EMAC
23
EMAC
24
EMAC
25
EMAC
26
EMAC
27
EMAC
28
Table 12-33. Ethernet MAC RMII Specific Signals
SymbolParameterMin (ns)Max (ns)
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
EMAC
ETXEN toggling from EREFCK rising714.5
21
ETX toggling from EREFCK rising714.7
22
Setup for ERX from EREFCK1.5
23
Hold for ERX from EREFCK0
24
Setup for ERXER from EREFCK1.5
25
Hold for ERXER from EREFCK0
26
Setup for ECRSDV from EREFCK1.5
27
Hold for ECRSDV from EREFCK0
28
Figure 12-11. Ethernet MAC RMII Mode
12.13 Flash Characteristics
The following table gives the device maximum operating frequency depending on the field FWS
of the Flash FSR register. This field defines the number of wait states required to access the
Flash Memory.
Table 12-34. Flash Wait States
FWSRead OperationsMaximum Operating Frequency (MHz)
01 cycle33
32058HS–AVR32–03/09
12 cycles66
62
Table 12-35. Programming Time
Temperature Operating Range
PartPage Programming Time (ms)Chip Erase Time (ms)
Industrial44
Automotive1616
AT32UC3A
32058HS–AVR32–03/09
63
13. Mechanical Characteristics
TJTAP
DθJA
×()+=
TJTAP(
Dθ(HEATSINK
×θ
JC
))++=
13.1Thermal Considerations
13.1.1Thermal Data
Table 13-1 summarizes the thermal resistance data depending on the package.
Table 13-1.Thermal Resistance Data
SymbolParameterConditionPackageTypUnit
AT32UC3A
θ
JA
θ
JC
θ
JA
θ
JC
13.1.2Junction Temperature
The average chip-junction temperature, T
1.
2.
where:
• θ
= package thermal resistance, J unction -to-ambien t (°C/W), pr o vided in Table 13-1 on p age
JA
64.
• θ
= package thermal resistance, Junction-to-case thermal resistance (°C/W), provided in
JC
Table 13-1 on page 64.
• θ
HEAT SINK
•P
= device power consumption (W) estimated from data provided in the section ”Power
D
Consumption” on page 44.
•T
= ambient temperature (°C).
A
From the first equation, the user can derive the estimated lifetime of the chip and decide if a
cooling device is necessary or not. If a cooling device is to be fitted on the chip, the second
equation should be used to compute the resulting average chip-junction temperature T
Table 13-11 gives the recommended soldering profile from J-STD-20.
Table 13-11. Soldering Profile
Profile FeatureGreen Package
Average Ramp-up Rate (217°C to Peak)3°C/sec
Preheat Temperature 175°C ±25°CMin. 150 °C, Max. 200 °C
Time Maintained Above 217°C60-150 sec
Time within 5⋅C of Actual Peak Temperature30 sec
Peak Temperature Range260 °C
Ramp-down Rate6 °C/sec
Time 25⋅C to Peak TemperatureMax. 8 minutes
Note:It is recommended to apply a soldering temperature higher than 250°C.
A maximum of three reflow passes is allowed per component.
AT32UC3A
32058HS–AVR32–03/09
68
AT32UC3A
14. Ordering Information
Table 14-1.Ordering Information
DeviceOrdering CodePackageConditioningTemperature Operatin g Ran ge
AT32UC3A0512AT32UC3A0512-ALUT144 LQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0512-ALU R144 LQFPReelIndustrial (-40⋅C to 85⋅C)
AT32UC3A0512-ALTR144 LQFPReelAutomotive (-40⋅C to 85⋅C)
AT32UC3A0512-ALTT144 LQFPTrayAutomotive (-40⋅C to 85⋅C)
AT32UC3A0512-ALTES144 LQFPTrayAutomotive (-40⋅C to 85⋅C) samples
AT32UC3A0512-CTUT144 FFBGATrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0512-CTUR144 FFBGAReelIndustrial (-40 ⋅C to 85⋅C)
AT32UC3A0256AT32UC3A0256-ALUT144 LQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0256-ALU R144 LQFPReelIndustrial (-40⋅C to 85⋅C)
AT32UC3A0256-CTUT144 FFBGATrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0256-CTUR144 FFBGAReelIndustrial (-40 ⋅C to 85⋅C)
AT32UC3A0128AT32UC3A0128-ALUT144 LQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0128-ALU R144 LQFPReelIndustrial (-40⋅C to 85⋅C)
AT32UC3A0128-CTUT144 FFBGATrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A0128-CTUR144 FFBGAReelIndustrial (-40 ⋅C to 85⋅C)
AT32UC3A1512AT32UC3A1512-AUT100 TQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A1512-AUR100 TQFPReelIndustrial (-40⋅C to 85⋅C)
AT32UC3A1256AT32UC3A1256-AUT100 TQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A1256-AUR100 TQFPReelIndustrial (-40⋅C to 85⋅C)
AT32UC3A1128AT32UC3A1128-AUT100 TQFPTrayIndustrial (-40⋅C to 85⋅C)
AT32UC3A1128-AUR100 TQFPReelIndustrial (-40⋅C to 85⋅C)
14.1Automotive Quality Grade
The AT32UC3A have been developed and manufactured according to the most stringent
requirements of the international standard ISO-TS-16949. This data sheet will contain limit values extracted from the results of extensive characterization (Temperature and Voltage). The
quality and reliability of the AT32UC3A is verified during regular product qualification as per
AEC-Q100 grade 3.
As indicated in the ordering information paragraph, the product is available in only one temperature grade T: -40°C / + 85°C.
32058HS–AVR32–03/09
69
15. Errata
15.1Rev. K
15.1.1PWM
AT32UC3A
All industrial parts labelled with -UES (engineering samples) are revision E parts.
1. PWM channel interrupt enabling triggers an interrupt
When enabling a PWM channel that is configured with center aligned period (CALG=1), an
interrupt is signalled.
Fix/Workaround
When using center aligned mode, enable the channel and read the status before channel
interrupt is enabled.
2. PWM counter restarts at 0x0001
The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first
PWM period has one more clock cycle.
Fix/Workaround
- The first period is 0x0000, 0x0001, ..., per iod
- Consecutive periods are 0x0001, 0x0002, ..., period
15.1.2ADC
15.1.3SPI
3. PWM update period to a 0 value does not work
It is impossible to update a period equal to 0 by the using the PWM update register
(PWM_CUPD).
Fix/Workaround
Do not update the PWM_CUPD register with a value equal to 0.
1. Sleep Mode activation needs additional A to D conversion
If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode
before after the next AD conversion.
Fix/Workaround
Activate the sleep mode in the mode register and then perform an AD conversion.
1. SPI Slave / PDCA transfer: no TX UNDERRUN flag
There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to
be informed of a character lost in transmission.
Fix/Workaround
For PDCA transfer: none.
2. SPI FDIV option does not work
Selecting clock signal using FDIV = 1 does not work as specified.
32058HS–AVR32–03/09
Fix/Workaround
Do not set FDIV = 1.
70
AT32UC3A
3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and
NCPHA=0
When multiple CS are in use, if one of the baudrate equ als to 1 and one of the o thers doesn't
equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK.
Fix/workaround
When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if
CPOL=1 and CPHA=0.
4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first
transfer
In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or
during the first transfer.
Fix/Workaround
1. Set slave mode, set required CPOL/CPHA.
2. Enable SPI.
3. Set the polarity CPOL of the line in the opposite value of the required one.
4. Set the polarity CPOL to the required one.
5. Read the RXHOLDING register.
Transfers can now befin and RXREADY will now behave as expected.
15.1.4Power Manager
15.1.5PDCA
15.1.6TWI
15.1.7USART
5. SPI Disable does not work in Slave mode
Fix/workaround
Read the last received data then perform a Software reset.
1. If the BOD level is higher than VDDCORE, the part is constantly under reset
If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will
be in constant reset.
Fix/Workaround
Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than
VDDCORE max and disable the BOD.
1. Wrong PDCA behavior when using two PDCA channels with the same PID.
Fix/Workaround
The same PID should not be assigned to more than one channel.
1. The TWI RXRDY flag in SR register is not reset when a software reset is performed.
Fix/Workaround
After a Software Reset, the register TWI RHR must be read.
1. ISO7816 info register US_NER cannot be read
The NER register always returns zero.
Fix/Workaround
None
15.1.8Processor and Architecture
1. LDM instruction with PC in the register list and without ++ increments Rp
32058HS–AVR32–03/09
71
AT32UC3A
For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie
the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the
increment of the pointer is done in parallel with the testing of R12.
Fix/Workaround
None.
32058HS–AVR32–03/09
72
15.2Rev. J
15.2.1PWM
AT32UC3A
1. PWM channel interrupt enabling triggers an interrupt
When enabling a PWM channel that is configured with center aligned period (CALG=1), an
interrupt is signalled.
Fix/Workaround
When using center aligned mode, enable the channel and read the status before channel
interrupt is enabled.
2. PWM counter restarts at 0x0001
The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first
PWM period has one more clock cycle.
Fix/Workaround
- The first period is 0x0000, 0x0001, ..., per iod
- Consecutive periods are 0x0001, 0x0002, ..., period
3. PWM update period to a 0 value does not work
It is impossible to update a period equal to 0 by the using the PWM update register
(PWM_CUPD).
15.2.2ADC
15.2.3SPI
Fix/Workaround
Do not update the PWM_CUPD register with a value equal to 0.
1. Sleep Mode activation needs additional A to D conversion
If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode
before after the next AD conversion.
Fix/Workaround
Activate the sleep mode in the mode register and then perform an AD conversion.
1. SPI Slave / PDCA transfer: no TX UNDERRUN flag
There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to
be informed of a character lost in transmission.
Fix/Workaround
For PDCA transfer: none.
2. SPI FDIV option does not work
Selecting clock signal using FDIV = 1 does not work as specified.
Fix/Workaround
Do not set FDIV = 1.
32058HS–AVR32–03/09
3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and
NCPHA=0
When multiple CS are in use, if one of the baudrate equ als to 1 and one of the o thers doesn't
equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK.
Fix/workaround
73
AT32UC3A
When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if
CPOL=1 and CPHA=0.
4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first
transfer
In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or
during the first transfer.
Fix/Workaround
1. Set slave mode, set required CPOL/CPHA.
2. Enable SPI.
3. Set the polarity CPOL of the line in the opposite value of the required one.
4. Set the polarity CPOL to the required one.
5. Read the RXHOLDING register.
Transfers can now befin and RXREADY will now behave as expected.
5. SPI Disable does not work in Slave mode
Fix/workaround
Read the last received data then perform a Software reset.
15.2.4Power Manager
15.2.5PDCA
15.2.6TWI
15.2.7SDRAMC
1. If the BOD level is higher than VDDCORE, the part is constantly under reset
If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will
be in constant reset.
Fix/Workaround
Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than
VDDCORE max and disable the BOD.
1. Wrong PDCA behavior when using two PDCA channels with the same PID.
Fix/Workaround
The same PID should not be assigned to more than one channel.
1. The TWI RXRDY flag in SR register is not reset when a software reset is performed.
Fix/Workaround
After a Software Reset, the register TWI RHR must be read.
1. Code execution from external SDRAM does not work
Code execution from SDRAM does not work.
15.2.8GPIO
32058HS–AVR32–03/09
Fix/Workaround
Do not run code from SDRAM.
1. PA29 (TWI SDA) and PA30 (TWI SCL) GPIO VIH (input high voltage) is 3.6V max
instead of 5V tolerant
The following GPIOs are not 5V tolerant : PA29 and PA30.
Fix/Workaround
74
None.
15.2.9USART
1. ISO7816 info register US_NER cannot be read
The NER register always returns zero.
Fix/Workaround
None
15.2.10Processor and Architecture
1. LDM instruction with PC in the register list and without ++ increments Rp
For LDM with PC in the register list:
the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the
increment of the pointer is done in parallel with the testing of R12.
Fix/Workaround
None.
2. RETE instruction does not clear SREG[L] from interrupts.
The RETE instruction clears SREG[L] as expected from exceptions.
Fix/Workaround
When using the STCOND instruction, clear SREG[L] in the stacked value of SR before
returning from interrupts with RETE.
AT32UC3A
the instruction behaves as if the ++ field is always set, ie
3. Exceptions when system stack is protected by MPU
RETS behaves incorrectly when MPU is enabled and MPU is configured so that
system stack is not readable in unprivileged mode.
Fix/Woraround
Workaround 1: Make system stack readable in unprivileged mode,
or
Workaround 2: Return from supervisor mode using rete instead of rets. This
requires :
1. Changing the mode bits from 001b to 110b before issuing the instruction.
Updating the mode bits to the desired value must be done using a single mtsr
instruction so it is done atomically. Even if this step is described in general
as not safe in the UC technical reference guide, it is safe in this very
specific case.
2. Execute the RETE instruction.
32058HS–AVR32–03/09
75
15.3Rev. I
15.3.1PWM
AT32UC3A
1. PWM channel interrupt enabling triggers an interrupt
When enabling a PWM channel that is configured with center aligned period (CALG=1), an
interrupt is signalled.
Fix/Workaround
When using center aligned mode, enable the channel and read the status before channel
interrupt is enabled.
2. PWM counter restarts at 0x0001
The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first
PWM period has one more clock cycle.
Fix/Workaround
- The first period is 0x0000, 0x0001, ..., per iod
- Consecutive periods are 0x0001, 0x0002, ..., period
3. PWM update period to a 0 value does not work
It is impossible to update a period equal to 0 by the using the PWM update register
(PWM_CUPD).
15.3.2ADC
15.3.3SPI
Fix/Workaround
Do not update the PWM_CUPD register with a value equal to 0.
1. Sleep Mode activation needs additional A to D conversion
If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode
before after the next AD conversion.
Fix/Workaround
Activate the sleep mode in the mode register and then perform an AD conversion.
1. SPI Slave / PDCA transfer: no TX UNDERRUN flag
There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to
be informed of a character lost in transmission.
Fix/Workaround
For PDCA transfer: none.
2. SPI FDIV option does not work
Selecting clock signal using FDIV = 1 does not work as specified.
Fix/Workaround
Do not set FDIV = 1.
32058HS–AVR32–03/09
3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and
NCPHA=0
When multiple CS are in use, if one of the baudrate equ als to 1 and one of the o thers doesn't
equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK.
Fix/workaround
76
AT32UC3A
When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if
CPOL=1 and CPHA=0.
4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first
transfer
In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or
during the first transfer.
Fix/Workaround
1. Set slave mode, set required CPOL/CPHA.
2. Enable SPI.
3. Set the polarity CPOL of the line in the opposite value of the required one.
4. Set the polarity CPOL to the required one.
5. Read the RXHOLDING register.
Transfers can now befin and RXREADY will now behave as expected.
5. SPI Disable does not work in Slave mode
Fix/workaround
Read the last received data then perform a Software reset.
15.3.4Power Manager
15.3.5Flashc
1. If the BOD level is higher than VDDCORE, the part is constantly under reset
If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will
be in constant reset.
Fix/Workaround
Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than
VDDCORE max and disable the BOD.
1. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP,
EP, EA, WUP, EUP commands may happen
- After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a
given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the
other half of the flash may fail. This may lead to an exception or to other errors derived from
this corrupted read access.
- After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may
fail. This may lead to an exception or to othe r errors der ived from this corrup ted read ac cess.
- After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, readin g
(data read or code fetch) the second half ( l ast 256 kB) of t he fla sh ma y fa il. This ma y le ad to
an exception or to other errors derived from this corrupted read access.
Fix/Workaround
Flashc WP, EP, EA, WUP, EUP commands: thes e com mands must b e issued from RAM or
through the EBI. After these commands, read twice one flash page initialized to 00h in each
half part of the flash.
15.3.6PDCA
32058HS–AVR32–03/09
1. Wrong PDCA behavior when using two PDCA channels with the same PID.
77
15.3.7GPIO
15.3.8USART
15.3.9TWI
15.3.10SDRAMC
AT32UC3A
Workaround/fix
The same PID should not be assigned to more than one channel.
1. Some GPIO VIH (input high voltage) are 3.6V max instead of 5V tolerant
1. The TWI RXRDY flag in SR register is not reset when a software reset is performed.
Fix/Workaround
After a Software Reset, the register TWI RHR must be read.
1. Code execution from external SDRAM does not work
Code execution from SDRAM does not work.
Fix/Workaround
Do not run code from SDRAM.
15.3.11Processor and Architecture
1. LDM instruction with PC in the register list and without ++ increments Rp
For LDM with PC in the register list:
the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the
increment of the pointer is done in parallel with the testing of R12.
Fix/Workaround
None.
2. RETE instruction does not clear SREG[L] from interrupts.
The RETE instruction clears SREG[L] as expected from exceptions.
Fix/Workaround
When using the STCOND instruction, clear SREG[L] in the stacked value of SR before
returning from interrupts with RETE.
3. Exceptions when system stack is protected by MPU
RETS behaves incorrectly when MPU is enabled and MPU is configured so that
system stack is not readable in unprivileged mode.
Fix/Woraround
Workaround 1: Make system stack readable in unprivileged mode,
or
Workaround 2: Return from supervisor mode using rete instead of rets. This
requires :
1. Changing the mode bits from 001b to 110b before issuing the instruction.
Updating the mode bits to the desired value must be done using a single mtsr
instruction so it is done atomically. Even if this step is described in general
as not safe in the UC technical reference guide, it is safe in this very
the instruction behaves as if the ++ field is always set, ie
32058HS–AVR32–03/09
78
specific case.
2. Execute the RETE instruction.
AT32UC3A
32058HS–AVR32–03/09
79
15.4Rev. H
15.4.1PWM
AT32UC3A
1. PWM channel interrupt enabling triggers an interrupt
When enabling a PWM channel that is configured with center aligned period (CALG=1), an
interrupt is signalled.
Fix/Workaround
When using center aligned mode, enable the channel and read the status before channel
interrupt is enabled.
2. PWM counter restarts at 0x0001
The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first
PWM period has one more clock cycle.
Fix/Workaround
- The first period is 0x0000, 0x0001, ..., per iod
- Consecutive periods are 0x0001, 0x0002, ..., period
3. PWM update period to a 0 value does not work
It is impossible to update a period equal to 0 by the using the PWM update register
(PWM_CUPD).
15.4.2ADC
15.4.3SPI
Fix/Workaround
Do not update the PWM_CUPD register with a value equal to 0.
1. Sleep Mode activation needs additional A to D conversion
If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode
before after the next AD conversion.
Fix/Workaround
Activate the sleep mode in the mode register and then perform an AD conversion.
1. SPI Slave / PDCA transfer: no TX UNDERRUN flag
There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to
be informed of a character lost in transmission.
Fix/Workaround
For PDCA transfer: none.
2. SPI FDIV option does not work
Selecting clock signal using FDIV = 1 does not work as specified.
Fix/Workaround
Do not set FDIV = 1
32058HS–AVR32–03/09
3. SPI disable does not work in SLAVE mode.
Fix/Workaround
Read the last received data, then perform a Software Reset.
80
AT32UC3A
4. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and
NCPHA=0
When multiple CS are in use, if one of the baudrate equ als to 1 and one of the o thers doesn't
equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK.
Fix/workaround
When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if
CPOL=1 and CPHA=0.
5. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first
transfer
In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or
during the first transfer.
Fix/Workaround
1. Set slave mode, set required CPOL/CPHA.
2. Enable SPI.
3. Set the polarity CPOL of the line in the opposite value of the required one.
4. Set the polarity CPOL to the required one.
5. Read the RXHOLDING register.
Transfers can now befin and RXREADY will now behave as expected.
15.4.4Power Manager
15.4.5FLASHC
6. SPI Disable does not work in Slave mode
Fix/workaround
Read the last received data then perform a Software reset.
1. Wrong reset causes when BOD is activated
Setting the BOD enable fuse will cause the Reset Cause Register to list BOD reset as the
reset source even though the part was reset by another source.
Fix/Workaround
Do not set the BOD enable fuse, but activate the BOD as soon as your program starts.
2. If the BOD level is higher than VDDCORE, the part is constantly under reset
If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will
be in constant reset.
Fix/Workaround
Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than
VDDCORE max and disable the BOD.
1. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP,
EP, EA, WUP, EUP commands may happen
- After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a
given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the
other half of the flash may fail. This may lead to an exception or to other errors derived from
this corrupted read access.
- After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may
fail. This may lead to an exception or to othe r errors der ived from this corrup ted read ac cess.
- After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, readin g
32058HS–AVR32–03/09
81
15.4.6PDCA
15.4.7TWI
15.4.8SDRAMC
AT32UC3A
(data read or code fetch) the second half ( l ast 256 kB) of t he fla sh ma y fa il. This ma y le ad to
an exception or to other errors derived from this corrupted read access.
Fix/Workaround
Flashc WP, EP, EA, WUP, EUP commands: thes e com mands must b e issued from RAM or
through the EBI. After these commands, read twice one flash page initialized to 00h in each
half part of the flash.
1. Wrong PDCA behavior when using two PDCA channels with the same PID.
Workaround/fix
The same PID should not be assigned to more than one channel.
1. The TWI RXRDY flag in SR register is not reset when a software reset is performed.
Fix/Workaround
After a Software Reset, the register TWI RHR must be read.
1. Code execution from external SDRAM does not work
Code execution from SDRAM does not work.
Fix/Workaround
Do not run code from SDRAM.
15.4.9GPIO
1. Some GPIO VIH (input high voltage) are 3.6V max instead of 5V tolerant
1. LDM instruction with PC in the register list and without ++ increments Rp
For LDM with PC in the register list:
the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the
increment of the pointer is done in parallel with the testing of R12.
Fix/Workaround
None.
2. RETE instruction does not clear SREG[L] from interrupts.
The RETE instruction clears SREG[L] as expected from exceptions.
Fix/Workaround
When using the STCOND instruction, clear SREG[L] in the stacked value of SR before
returning from interrupts with RETE.
the instruction behaves as if the ++ field is always set, ie
32058HS–AVR32–03/09
3. Exceptions when system stack is protected by MPU
82
AT32UC3A
RETS behaves incorrectly when MPU is enabled and MPU is configured so that
system stack is not readable in unprivileged mode.
Fix/Woraround
Workaround 1: Make system stack readable in unprivileged mode,
or
Workaround 2: Return from supervisor mode using rete instead of rets. This
requires :
1. Changing the mode bits from 001b to 110b before issuing the instruction.
Updating the mode bits to the desired value must be done using a single mtsr
instruction so it is done atomically. Even if this step is described in general
as not safe in the UC technical reference guide, it is safe in this very
specific case.
2. Execute the RETE instruction.
32058HS–AVR32–03/09
83
15.5Rev. E
15.5.1SPI
AT32UC3A
1. SPI FDIV option does not work
Selecting clock signal using FDIV = 1 does not work as specified.
Fix/Workaround
Do not set FDIV = 1.
2. SPI Slave / PDCA transfer: no TX UNDERRUN flag
There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to
be informed of a character lost in transmission.
Fix/Workaround
For PDCA transfer: none.
3. SPI Bad serial clock generation on 2nd chip select when SCBR=1, CPOL=1 and
CNCPHA=0
When multiple CS are in use, if one of the baudrate e quals to 1 and one of the others
doesn’t equal to 1, and CPOL=1 and CPHA=0, then an additional pulse will be generated on
SCK.
Fix/Workaround
When multiple CS are in use, if one of the baudrate equals to 1, the other must also equal 1
if CPOL=1 and CPHA=0.
4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first
transfer
In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or
during the first transfer.
Fix/Workaround
1. Set slave mode, set required CPOL/CPHA.
2. Enable SPI.
3. Set the polarity CPOL of the line in the opposite value of the required one.
4. Set the polarity CPOL to the required one.
5. Read the RXHOLDING register.
Transfers can now befin and RXREADY will now behave as expected.
5. SPI CSNAAT bit 2 in register CSR0...CSR3 is not available.
Fix/Workaround
Do not use this bit.
6. SPI disable does not work in SLAVE mode.
Fix/Workaround
Read the last received data, then perform a Software Reset.
32058HS–AVR32–03/09
7. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and
NCPHA=0
When multiple CS are in use, if one of the baudrate equ als to 1 and one of the o thers doesn't
equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK.
84
15.5.2PWM
AT32UC3A
Fix/workaround
When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if
CPOL=1 and CPHA=0.
1. PWM counter restarts at 0x0001
The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first
PWM period has one more clock cycle.
Fix/Workaround
- The first period is 0x0000, 0x0001, ..., per iod
- Consecutive periods are 0x0001, 0x0002, ..., period
2. PWM channel interrupt enabling triggers an interrupt
When enabling a PWM channel that is configured with center aligned period (CALG=1), an
interrupt is signalled.
Fix/Workaround
When using center aligned mode, enable the channel and read the status before channel
interrupt is enabled.
15.5.3SSC
3. PWM update period to a 0 value does not work
It is impossible to update a period equal to 0 by the using the PWM update register
(PWM_CUPD).
Fix/Workaround
Do not update the PWM_CUPD register with a value equal to 0.
4. PWM channel status may be wrong if disabled before a period has elapsed
Before a PWM period has elapsed, the read channel status may be wrong. The CHIDx-bit
for a PWM channel in the PWM Enable Register will read '1' for one full PWM period even if
the channel was disabled before the period elapsed. It will then read '0' as expected.
Fix/Workaround
Reading the PWM channel status of a disabled channel is only correct after a PWM period
has elapsed.
1. SSC does not trigger RF when data is low
The SSC cannot transmit or receive data when CKS = CKDIV and CKO = none, in TCMR or
RCMR respectively.
Fix/Workaround
Set CKO to a value that is not "none" and bypass the output of the TK/RK pin with the PIO.
32058HS–AVR32–03/09
2. SSC Data is not sent unless clock is set as output
The SSC cannot transmit or receive data when CKS = CKDIV and CKO = none, in TCMR or
RCMR respectively.
Fix/Workaround
Set CKO to a value that is not "none" and bypass the output of the TK/RK pin with the PIO.
85
15.5.4USB
1. USB No end of host reset signaled upon disconnection
In host mode, in case of an unexpected device disconnection whereas a usb reset is being
sent by the usb controller, the UHCON.RESET bit may not been cleared by the hardware at
the end of the reset.
Fix/Workaround
A software workaround consists in testing (by polling or interrupt) the disconnection
(UHINT.DDISCI == 1) while waiting for the end of reset (UHCON.RESET == 0) to avoid
being stuck.
2. USBFSM and UHADDR1/2/3 registers are not available.
Do not use USBFSM register.
Fix/Workaround
Do not use USBFSM register and use HCON[6:0] field instead for all the pipes.
15.5.5Processor and Architecture
1. Incorrect Processor ID
The processor ID reads 0x01 and not 0x02 as it should.
AT32UC3A
Fix/Workaround
None.
2. Bus error should be masked in Debug mode
If a bus error occurs during debug mode, the processor will not respond to debug commands through the DINST register.
Fix/Workaround
A reset of the device will make the CPU respond to debug commands again.
3. Read Modify Write (RMW) instructions on data outside the internal RAM does not
work.
Read Modify Write (RMW) instructions on data outside t he internal RAM does not work.
Fix/Workaround
Do not perform RMW instructions on data outside the internal RAM.
4. CRC calculation of a locked device will calculate CRC for 512 kB of flash memory,
even though the part has less flash.
Fix/Workaround
The flash address space is wrapping, so it is possible to use the CRC value by calculating
CRC of the flash content concatenated with itself N times. Where N is 512 kB/flash size.
5. Need two NOPs instruction after instructions masking interrupts
The instructions following in the pipeline the instruction masking the interrupt through SR
may behave abnormally.
32058HS–AVR32–03/09
Fix/Workaround
Place two NOPs instructions after each SSRF or MTSR instruction setting IxM or GM in SR.
86
AT32UC3A
6. CPU Cycle Counter does not reset the COUNT system register on COMPARE match.
The device revision E does not reset the COUNT system register on COMPARE match. In
this revision, the COUNT register is clocked by the CPU clock, so when the CPU clock
stops, so does incrementing of COUNT.
Fix/Workaround
None.
7. Memory Protection Unit (MPU) is non functional.
Fix/Workaround
Do not use the MPU.
8. The following alternate GPIO function C are not available in revE
MACB-WOL on GPIO9 (PA09), MACB-WOL on GPIO18 (PA18), USB-USB_ID on GPIO21
(PA21), USB-USB_VBOF on GPIO22 (PA22), and all function B and C on GPIO70 to
GPIO101 (PX00 to PX39).
Fix/Workaround
Do not use these alternate B and C functions on the listed GPIO pins.
9.Clock connection table on Rev E
Here is the table of Rev E
Figure 15-1. Timer/Counter clock connections on RevE
10. Local Bus fast GPIO not available in RevE.
Fix/Workaround
Do not use on this silicon revision.
11. Spurious interrupt may corrupt core SR mode to exception
If the rules listed in the chapter `Masking interrupt requests in peripheral modules' of the
AVR32UC Technical Reference Manual are not followed, a spurious interrupt may occur. An
interrupt context will be pushed onto the stack while the core SR mode will indicate an
exception. A RETE instruction would then corrupt the stack..
32058HS–AVR32–03/09
Fix/Workaround
Follow the rules of the AVR32UC Technical Reference Manual. To increase software
robustness, if an exception mode is detected at the beginning of an interrupt handler,
change the stack interrupt context to an exception context and issue a RETE instruction.
87
AT32UC3A
12. CPU cannot operate on a divided slow clock (internal RC oscillator)
Fix/Workaround
Do not run the CPU on a divided slow clock.
13. LDM instruction with PC in the register list and without ++ increments Rp
For LDM with PC in the register list:
the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the
increment of the pointer is done in parallel with the testing of R12.
Fix/Workaround
None.
14. RETE instruction does not clear SREG[L] from interrupts.
The RETE instruction clears SREG[L] as expected from exceptions.
Fix/Workaround
When using the STCOND instruction, clear SREG[L] in the stacked value of SR before
returning from interrupts with RETE.
15. Exceptions when system stack is protected by MPU
RETS behaves incorrectly when MPU is enabled and MPU is configured so that
system stack is not readable in unprivileged mode.
Fix/Woraround
Workaround 1: Make system stack readable in unprivileged mode,
or
Workaround 2: Return from supervisor mode using rete instead of rets. This
requires :
1. Changing the mode bits from 001b to 110b before issuing the instruction.
Updating the mode bits to the desired value must be done using a single mtsr
instruction so it is done atomically. Even if this step is described in general
as not safe in the UC technical reference guide, it is safe in this very
specific case.
2. Execute the RETE instruction.
the instruction behaves as if the ++ field is always set, ie
15.5.6SDRAMC
15.5.7USART
32058HS–AVR32–03/09
1. Code execution from external SDRAM does not work
Code execution from SDRAM does not work.
Fix/Workaround
Do not run code from SDRAM.
2. SDRAM SDCKE rise at the same time as SDCK while exiting self-refresh mode
SDCKE rise at the same time as SDCK while exiting self-refresh mode.
Fix/Workaround
None.
1. USART Manchester Encoder Not Working
Manchester encoding/decoding is not wor kin g.
Fix/Workaround
Do not use manchester encoding.
88
AT32UC3A
2. USART RXBREAK problem when no timeguard
In asynchronous mode the RXBREAK flag is not correctly handled when the timeguard is 0
and the break character is located just after the stop bit.
Fix/Workaround
If the NBSTOP is 1, timeguard should be different from 0.
3. USART Handshaking: 2 characters sent / CTS rises when TX
If CTS switches from 0 to 1 during the TX of a character, if the Holding register is not emp ty,
the TXHOLDING is also transmitted.
Fix/Workaround
None.
4. USART PDC and TIMEGUARD not supported in MANCHESTER
Manchester encoding/decoding is not wor kin g.
Fix/Workaround
Do not use manchester encoding.
5. USART SPI mode is non functional on this revision.
Fix/Workaround
Do not use the USART SPI mode.
15.5.8Power Manager
6. DCD is active High instead of Low.
In modem mode the DCD signal is assumed to be active high by the USART, butshould
have been active low.
Fix/Workaround
Add an external inverter to the DCD line.
7. ISO7816 info register US_NER cannot be read
The NER register always returns zero.
Fix/Workaround
None.
1. Voltage regulator input and output is connected to VDDIO and VDDCORE inside the
device
The voltage regulator input and output is connected to VDDIO and VDDCORE respectively
inside the device.
Fix/Workaround
Do not supply VDDCORE externally, as this supply will work in paralell with the regulator.
2. Wrong reset causes when BOD is activated
Setting the BOD enable fuse will cause the Reset Cause Register to list BOD reset as the
reset source even though the part was reset by another source.
32058HS–AVR32–03/09
Fix/Workaround
Do not set the BOD enable fuse, but activate the BOD as soon as your program starts.
3. PLL0/1 Lock control does not work
Lock Control does not work for PLL0 and PLL1.
89
AT32UC3A
Fix/Workaround
In PLL0/1 Control register, the bit 7 should be set in order to prevent unexpected behaviour.
4. Peripheral Bus A maximum frequency is 33MHz instead of 66MHz.
Fix/Workaround
Do not set PBA frequency higher than 33 MHz.
5. PCx pins go low in stop mode
In sleep mode stop all PCx pins will be controlled by GPIO module instead of oscillators.
This can cause drive contention on the XINx in worst case.
Fix/Workaround
Before entering stop mode set all PCx pins to input and GPIO controlled.
6. On some rare parts, the maximum HSB and CPU speed is 50MHz instead of 66MHz.
Fix/Workaround
Do not set the HSB/CPU speed higher than 50MHz when the fir mware ge nerate exceptions.
7. If the BOD level is higher than VDDCORE, the part is constantly under reset
If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will
be in constant reset.
15.5.9HMatrix
15.5.10ADC
Fix/Workaround
Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than
VDDCORE max and disable the BOD.
8. System Timer mask (Bit 16) of the PM CPUMASK register is not available.
Fix/Workaround
Do not use this bit.
1. HMatrix fixed priority arbitration does not work
Fixed priority arbitration does not work.
Fix/Workaround
Use Round-Robin arbitration instead.
1. ADC possible miss on DRDY when disabling a channel
The ADC does not work properly when more than one channel is enabled.
Fix/Workaround
Do not use the ADC with more than one channel enabled at a time.
2. ADC OVRE flag sometimes not reset on Status Register read
The OVRE flag does not clear properly if read simultaneously to an end of conversion.
32058HS–AVR32–03/09
Fix/Workaround
None.
3. Sleep Mode activation needs additional A to D conversion
90
15.5.11ABDAC
15.5.12FLASHC
AT32UC3A
If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode
before after the next AD conversion.
Fix/Workaround
Activate the sleep mode in the mode register and then perform an AD conversion.
1. Audio Bitstream DAC is not functional.
Fix/Workaround
Do not use the ABDAC on revE.
1. The address of Flash General Purpose Fuse Register Low (FGPFRLO) is 0xFFFE140C
on revE instead of 0xFFFE1410.
Fix/Workaround
None.
2. The command Quick Page Read User Page(QPRUP) is not functional.
Fix/Workaround
None.
15.5.13RTC
3. PAGEN Semantic Field for Program GP Fuse Byte is WriteData[7:0], ByteAddress[ 1:0]
on revision E instead of WriteData[7:0], ByteAddress[2:0].
Fix/Workaround
None.
4. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP,
EP, EA, WUP, EUP commands may happen
- After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a
given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the
other half of the flash may fail. This may lead to an exception or to other errors derived from
this corrupted read access.
- After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may
fail. This may lead to an exception or to othe r errors der ived from this corrup ted read ac cess.
- After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, readin g
(data read or code fetch) the second half ( l ast 256 kB) of t he fla sh ma y fa il. This ma y le ad to
an exception or to other errors derived from this corrupted read access.
Fix/Workaround
Flashc WP, EP, EA, WUP, EUP commands: thes e com mands must b e issued from RAM or
through the EBI. After these commands, read twice one flash page initialized to 00h in each
half part of the flash.
32058HS–AVR32–03/09
1. Writes to control (CTR L), top (TOP) and value (VAL) in the RTC are discarded if the
RTC peripheral bus clock (PBA) is divided by a factor of four or more relative to the
HSB clock.
Fix/Workaround
Do not write to the RTC registers using the peripheral bus clock (PBA) divided by a factor of
four or more relative to the HSB clock.
91
15.5.14OCD
15.5.15PDCA
15.5.16TWI
AT32UC3A
2. The RTC CLKEN bit (bit number 16) of CTRL register is not available.
Fix/Workaround
Do not use the CLKEN bit of the RTC on Rev E.
1. Stalled memory access instruction writeback fails if followed by a HW breakpoint.
Consider the following assembly code sequence:
A
B
If a hardware breakpoint is placed on instruction B, and instruction A is a memory access
instruction, register file updates from instruc tio n A can be disc ar de d.
Fix/Workaround
Do not place hardware breakpoints, use software breakpoints instead.
Alternatively, place a hardware breakpoint on the instruction before the memory
access instruction and then single step over the memory access instruction.
1. Wrong PDCA behavior when using two PDCA channels with the same PID.
Workaround/fix
The same PID should not be assigned to more than one channel.
1. The TWI RXRDY flag in SR register is not reset when a software reset is performed.
Fix/Workaround
After a Software Reset, the register TWI RHR must be read.
32058HS–AVR32–03/09
92
16. Datasheet Revision History
Please note that the referring page numbers in this section are referred to this document. The
referring revision in this section are referring to the document revision.
16.1Rev. H – 03/09
AT32UC3A
16.2Rev. G – 01/09
16.3Rev. F – 08/08
1.
2.
2.
1.
2.
1.
2.Update DMIPS number in ”Features” on page 1.
Update ”Errata” on page 70.
Update eletrical characteristic in ”DC Characteristics” on page 41.
Add BGA144 package information.
Update ”Errata” on page 70.
Update GPIO eletrical characteristic in ”DC Characteristics” on page 41.
Add revision J to ”Errata” on page 70.
16.4Rev. E – 04/08
16.5Rev. D – 04/08
32058HS–AVR32–03/09
1.Open Drain Mode removed from ”General-Purpose Input/Output Controller (G PIO)”
on page 151.
1.Updated ”Signal Description List” on page 8. Removed RXDN and TXDN from
USART section.
2.Updated ”Errata” on page 70. Rev G replaced by rev H.
93
16.6Rev. C – 10/07
16.7Rev. B – 10/07
AT32UC3A
1.Updated ”Signal Description List” on page 8. Removed RXDN and TXDN from
USART section.
2.Updated ”Errata” on page 70. Rev G replaced by rev H.
1.Updated ”Features” on page 1.
2.Update ”Blockdiagram” on page 4 with local bus.
3.Updated ”Peripherals” on page 34 with local bus.
4.Add SPI feature in ”Universial Synchronous/Asynchronous Receiver/Transmitter
(USART)” on page 315.
5.Updated ”USB On-The-Go Interface (USBB)” on page 517.
6.Updated ”JTAG and Boundary Scan” on page 750 with programming procedure .
15.3Rev. I .....................................................................................................................76
15.4Rev. H ...................................................................................................................80
15.5Rev. E ....................................................................................................................84
16Datasheet Revision History ..................................................................93
16.1Rev. H – 03/09 ......................................................................................................93
16.2Rev. G – 01/09 ......................................................................................................93
16.3Rev. F – 08/08 .......................................................................................................93
AT32UC3A
16.4Rev. E – 04/08 .......................................................................................................93
16.5Rev. D – 04/08 ......................................................................................................93
16.6Rev. C – 10/07 ......................................................................................................94
16.7Rev. B – 10/07 .......................................................................................................94
16.8Rev. A – 03/07 .......................................................................................................94
32058HS–AVR32–03/09
III
HeadquartersInternation al
Atmel Corporation
2325 Orchard Parkway
San Jose, CA 95131
USA
Tel: 1(408) 441-0311
Fax: 1(408) 487-2600
Atmel Asia
Unit 1-5 & 16, 19/F
BEA Tower, Millennium City 5
418 Kwun Tong Road
Kwun Tong, Kowloon
Hong Kong
Tel: (852) 2245-6100
Fax: (852) 2722-1369
Product Contact
Web Site
www.atmel.com
Literature Requests
www.atmel.com/literature
Atmel Europe
Le Krebs
8, Rue Jean-Pierre Timbaud
BP 309
78054 Saint-Quentin-enYvelines Cedex
France
Tel: (33) 1-30-60-70-00
Fax: (33) 1-30-60-71-11
Technical Support
avr32@atmel.com
Atmel Japan
9F, Tonetsu Shinkawa Bldg.
1-24-8 Shinkawa
Chuo-ku, Tokyo 104-0033
Japan
Tel: (81) 3-3523-3551
Fax: (81) 3-3523-7581
Sales Contact
www.atmel.com/contacts
Disclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any
intellectual property right is granted by this document or in conne ction with the sale of Atmel products. EXCEPT AS SET FORTH IN ATMEL’S TERMS AND CONDI-
TIONS OF SALE LOCATED ON ATMEL’S WEB SITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY
WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENT AL DAMAGES (INCLUDING, WITHOUT LIMITATION, D AMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF
THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no
representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications
and product descriptions at any time without notice. Atmel does not make any commitment to update the information contained here in. Unless specifically provided
otherwise, Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel’s products are not intended, authorized, or warranted for use
as components in applications intended to suppor t or sustain life.