– 210 DMIPS throughput at 150 MHz
– 16 KB instruction cache and 16 KB data caches
– Memory Management Unit enabling use of operating systems
– Single-cycle RISC instruction set including SIMD and DSP instructions
– Java Hardware Acceleration
• Multimedia Co-Processor
– Vector Multiplication Unit for video acceleration through color-space conversion
(YUV<->RGB), image scaling and filtering, quarter pixel motion compensation
• Multi-hierarchy bus system
– High-performance data transfers on separate buses for increased performance
• Data Memories
– 32KBytes SRAM
• External Memory Interface
– SDRAM, DataFlash™, SRAM, Multi Media Card (MMC), Secure Digital (SD),
– Compact Flash, Smart Media, NAND Flash
• Direct Memory Access Controller
– External Memory access without CPU intervention
• Interrupt Controller
– Individually maskable Interrupts
– Each interrupt request has a programmable priority and autovector address
• System Functions
– Power and Clock Manager
– Crystal Oscillator with Phase-Lock-Loop (PLL)
– Watchdog Timer
– Real-time Clock
• 6 Multifunction timer/counters
– Three external clock inputs, I/O pins, PWM, capture and various counting
• Universal Serial Bus (USB) 2.0 High Speed (480 Mbps) Device
– On-chip Transceivers with physical interface
• 16-bit stereo audio DAC
– Sample rates up to 50 kHz
• On-Chip Debug System
– Nexus Class 3
– Full speed, non-intrusive data and program trace
– Runtime control and JTAG interface
• Package/Pins
– AT32AP7002: 196-ball CTBGA
• Power supplies
– 1.65V to1.95V VDDCORE
– 3.0V to 3.6V VDDIO
®
32 32-Bit Microcontroller
AVR®32 32-bit
Microcontroller
AT32AP7002
Preliminary
Summary
32054AS-AVR32-02/07
1.Part Description
The AT32AP7002 is a complete System-on-chip application processor with an AVR32 RISC
processor achieving 210 DMIPS running 150 MHz. AVR32 is a high-performance 32-bit RISC
microprocessor core, designed for cost-sensitive embedded applications, with particular emphasis on low power consumption, high code density and high application performance.
AT32AP7002 implements a Memory Management Unit (MMU) and a flexible interrupt controller
supporting modern operating systems and real-time operating systems. The processor also
includes a rich set of DSP and SIMD instructions, specially designed for multimedia and telecom
applications.
AT32AP7002 incorporates SRAM memories on-chip for fast and secure access. For applications requiring additional memory, external 16-bit SRAM is accessible. Additionally, an SDRAM
controller provides off-chip volatile memory access as well as controllers for all industry standard
off-chip non-volatile memories, like Compact Flash, Multi Media Card (MMC), Secure Digital
(SD)-card, SmartCard, NAND Flash and Atmel DataFlash™.
The Direct Memory Access controller for all the serial peripherals enables data transfer between
memories without processor intervention. This reduces the processor overhead when transferring continuous and large data streams between modules in the MCU.
The Timer/Counters includes three identical 16-bit timer/counter channels. Each channel can be
independently programmed to perform a wide range of functions including frequency measurement, event counting, interval measurement, pulse generation, delay timing and pulse width
modulation.
AT32AP7002
AT32AP7002 also features an onboard LCD Controller, supporting single and double scan
monochrome and color passive STN LCD modules and single scan active TFT LCD modules.
On monochrome STN displays, up to 16 gray shades are supported using a time-based dithering algorithm and Frame Rate Control (FRC) method. This method is also used in color STN
displays to generate up to 4096 colors.
The LCD Controller is programmable for supporting resolutions up to 2048 x 2048 with a pixel
depth from 1 to 24 bits per pixel.
A pixel co-processor provides color space conversions for images and video, in addition to a
wide variety of hardware filter support
The media-independent interface (MII) and reduced MII (RMII) 10/100 Ethernet MAC modules
provides on-chip solutions for network-connected devices.
The Java hardware acceleration implementation in AVR32 allows for a very high-speed Java
byte-code execution. AVR32 implements Java instructions in hardware, reusing the existing
RISC data path, which allows for a near-zero hardware overhead and cost with a very high
performance.
The Image Sensor Interface supports cameras with up to 12-bit data buses and connects
directly to the LCD interface through a separate bus.
32054AS-AVR32-02/07
PS2 connectivity is provided for standard input devices like mice and keyboards.
2
AT32AP7002
AT32AP7002 integrates a class 3 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.
The C-compiler is closely linked to the architecture and is able to utilize code optimization features, both for size and speed.
32054AS-AVR32-02/07
3
2.Blockdiagram
Figure 2-1.Blockdiagram
TRST_N
TCK
TDO
TDI
TMS
EVTI_N
D+
D-
DATA[11..0]
HSYNC
VSYNC
PCLK
PA
PB
PC
PD
PE
XIN32
XOUT32
XIN0
XOUT0
XIN1
XOUT1
PLL0
PLL1
OSCEN_N
Parallel Input/Output Controllers
RESET_N
A
D
D
A
A
D
T
D
T
A
C
CMD
DATA[7..0]
C
S
S
S
S
S
32 KHz
OSC
OSC0
OSC1
PLL0
PLL1
G
K
L
C
INTERFACE
MCKO
MDO[5..0]
MSEO[1..0]
EVTO_N
INTERFACE
SENSOR
INTERFACE
INTRAM0
INTRAM1
0
T
A
1
A
T
N
0
A
A
N
1
L
K
K
L
D
I
C
N
Y
O
D
3
[
]
0
.
.
JTAG
USB
DMA
IMAGE
PB
DMA CONTROLLER
AUDIO BITSTREAM
DAC
MULTIMEDIA CARD
INTERFACE
AC97 CONTROLLER
POWER
MANAGER
CLOCK
GENERATOR
CLOCK
CONTROLLER
SLEEP
CONTROLLER
RESET
CONTROLLER
NEXUS
CLASS 3
PBB
S
M
M
S
HSB
HSB-PB
BRIDGE
B
OCD
MEMORY MANAGEMENT UNIT
INSTR
CACHE
M
M
HIGH SPEED
BUS MATRIX
S
SMM
CONFIGURATION REGISTERS BUS
S
HSB
HSB-PB
BRIDGE A
PB
PBA
DMA
DMA
DMA
AP CPU
DATA
CACHE
HSB-HSB BRIDGE
PERIPHERAL
CONTROLLER
PDC
PERIPHERAL
PDC
INTERFACE 0/1
SYNCHRONOUS
PDC
CONTROLLER 0/1/2
TWO-WIRE
INTERFACE
PS2 INTERFACE
REAL TIME
COUNTER
WATCHDOG
M
M
DMA
USART0
USART1
USART2
USART3
SERIAL
SERIAL
TIMER
AT32AP7002
PIXEL COPROCESSOR
VSYNC,
HSYNC,
DATA[22..0],
NANDOE,
NANDWE,
SDCKE,
NCS[3,1,0],
ADDR[22..0]
NCS[5,4,2]
CFRNW,
CFCE1,
CONTROLLER & ECC)
CFCE2,
ADDR[23..25]
DATA[31..16]
RXD
TXD
CLK
RTS, CTS
SCK
MISO, MOSI
NPCS0
NPCS[3..1]
TX_DATA
RX_DATA
SCL
SDA
CLOCK[1..0]
DATA[1..0]
PWR,
PCLK,
MODE,
DVAL,
CC,
GPL[7..0]
RAS,
CAS,
SDWE,
SDCK,
NWE3,
NWE1,
NWE0,
NRD,
NWAIT
SDCS,
DATA[15..0]
PA
PB
PC
PD
PE
Parallel Input/Output Controllers
LCD
CONTRO
LLER
S
M
DMA
S
(SDRAM & STATIC MEMORY
EXTERNAL BUS INTERFACE
TX_CLOCK, TX_FRAME_SYNC
RX_CLOCK, RX_FRAME_SYNC
32054AS–AVR32–02/07
A
B
CLK[2..0]
X
E
T
K
P
NMI_N
.
.
0
]
[
2
2
[
0
]
.
.
T
I
N
S
[
7
TIMER/COUNTER 0/1
.
0
]
.
[
7
.
0
.
]
EXTERNAL
INTERRUPT
CONTROLLER
INTERRUPT
CONTROLLER
PULSE WIDTH
MODULATION
CONTROLLER
PWM0
PWM1
PWM2
PWM3
4
2.1Processor and architecture
2.1.1AVR32AP CPU
•
32-bit load/store AVR32B RISC architecture.
– Up to 15 general-purpose 32-bit registers.
– 32-bit Stack Pointer, 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 instructions.
– SIMD extention for media applications.
• 7 stage pipeline allows one instruction per clock cycle for most instructions.
– Java Hardware Acceleration.
– Byte, half-word, word and double word memory access.
– Unaligned memory access.
– Shadowed interrupt context for INT3 and multiple interrupt priority levels.
– Dynamic branch prediction and return address stack for fast change-of-flow.
– Coprocessor interface.
• Full MMU allows for operating systems with memory protection.
Coprocessor coupled to the AVR32 CPU Core through the TCB Bus.
•
• Three parallel Vector Multiplication Units (VMU) where each unit can:
– Multiply three pixel components with three coefficients.
– Add the products from the multiplications together.
– Accumulate the result or add an offset to the sum of the products.
• Can be used for accelerating:
– Image Color Space Conversion.
•Configurable Conversion Coefficients.
• Supports packed and planar input and output formats.
• Supports subsampled input color spaces (i.e 4:2:2, 4:2:0).
– Image filtering/scaling.
• Configurable Filter Coefficients.
• Throughput of one sample per cycle for a 9-tap FIR filter.
• Can use the built-in accumulator to extend the FIR filter to more than 9-taps.
• Can be used for bilinear/bicubic interpolations.
– MPEG-4/H.264 Quarter Pixel Motion Compensation.
• Flexible input Pixel Selector.
– Can operate on numerous different image storage formats.
• Flexible Output Pixel Inserter.
– Scales and saturates the results back to 8-bit pixel values.
32054AS–AVR32–02/07
5
– Supports packed and planar output formats.
• Configurable coefficients with flexible fixed-point representation.
2.1.3Debug 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 3
• 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, Ownership, and Watchpoint trace supported
2.1.4DMA controller
2 HSB Master Interfaces
•
• 3 Channels
• Software and Hardware Handshaking Interfaces
– 11 Hardware Handshaking Interfaces
• Memory/Non-Memory Peripherals to Memory/Non-Memory Peripherals Transfer
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.
• Eighteen channels
– Two for each USART
– Two for each Serial Synchronous Controller
– Two for each Serial Peripheral Interface
2.1.6Bus system
HSB bus matrix with 10 Masters and 8 Slaves handled
•
– Handles Requests from the CPU Icache, CPU Dcache, HSB bridge, HISI, USB 2.0 Controller,
LCD Controller, DMA Controller 0, DMA Controller 1, and to internal SRAM 0, internal SRAM 1,
PB A, PB B, EBI and, USB.
32054AS–AVR32–02/07
6
AT32AP7002
– Round-Robin Arbitration (three modes supported: no default master, last accessed default
master, fixed default master)
– Burst Breaking with Slot Cycle Limit
– One Address Decoder Provided per Master
• 2 Peripheral buses allowing each bus to run on different bus speeds.
– PB A intended to run on low clock speeds, with peripherals connected to the PDC.
– PB B intended to run on higher clock speeds, with peripherals connected to the DMAC.
• HSB-HSB Bridge providing a low-speed HSB bus running at the same speed as PBA
– Allows PDC transfers between a low-speed PB bus and a bus matrix of higher clock speeds
An overview of the bus system is given in Figure 2-1 on page 4. 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 Manager. The figure identifies the number of master and slave interfaces of each module
connected to the HSB bus, and which DMA controller is connected to which peripheral.
32054AS–AVR32–02/07
7
2.2Package and PinoutAVR32AP7002
Figure 2-2.196 CTBGA Pinout
TOP VIEWBOTTOM VIEW
Ball A1
14131211109876543211413121110 9 8 7 6 5 4 3 2 1
AT32AP7002
A
B
C
D
E
F
G
H
J
K
L
M
N
P
AVR32
A
B
C
D
E
F
G
H
J
K
L
M
N
P
Table 2-1.CTBGA196 Package Pinout A1..T8
12345678
PX49PX48PX47AVDDPLLPC28PC23PC20PB22
A
PX50GNDVDDIOPLL0PLL1XIN32PC22PB23
B
PX51PD01PX05GNDAGNDPLLXOUT32PC29PC21
C
PX32PD00VDDIOPX02XIN0XOUT0AGNDOSCPC30
D
PX33PX00PX04GNDPD07AVDDOSCOSCEN_NPC31
E
PX01PX03VDDCOREPD04PD09TDIRESET_NVDDCORE
F
PD05PD08PD06TDOPA04PA02PA08PX22
G
TMSTRST_NTCKEVTI_NPB24PA10PA14PX38
H
PA 01PA0 3PA 0 0V D D IOG NDPA 0 9PA 1 8G N D
J
PA 05PA1 1PA 1 2PA 1 6G NDG N DPA 2 6WA K E _N
K
PB25PA21PA19GNDVDDIOVDDIOPA25PA29
L
PA13PA22PA23PD17AVDDUSBVDDCOREVBGPA30
M
PA15PA20PD12PD15PD16AGNDUSBFSDPHSDP
N
PA17PA24PD13PD14XIN1XOUT1FSDMHSDM
P
32054AS–AVR32–02/07
8
AT32AP7002
Table 2-2.CTBGA196 Package Pinout A9..T16
9 1011121314
PB18PB16PB11PB08PB05PB04
A
PB21PB17PB12PB09PB06PB03
B
PA06PB19PB14PB10PB07PB02
C
VDDIOPB20PB15PB13GNDPB01
D
PA07GNDPB00PX44VDDIOPX45
E
PX42GNDGNDPX43PX46PX40
F
PX30PX25PX31VDDIOVDDCOREPX39
G
PA28PX20PX28PX29VDDCOREPX26
H
PB27PX37PX23PX27PX21PX24
J
PB28PX15PX36PX19PX34PX18
K
PX41GNDPX07VDDIOGNDPX35
L
PX53PX06PX11PX12PX17PX14
M
PB26VDDIOPX09PB29PX16PX13
N
PA27PA31PX52PX08PX10PB30
P
32054AS–AVR32–02/07
9
AT32AP7002
3.Signals Description
The following table gives details on the signal name classified by peripheral. The pinout multiplexing of these signals is given in the Peripheral Muxing table in the Peripherals chapter.
Connected to a 6810 Ohm ± 0.5%
resistor to gound and a 10 pF
capacitor to ground.
32054AS-AVR32-02/07
14
4.Power Considerations
4.1Power Supplies
The AT32AP7002 has several types of power supply pins:
•
VDDCORE pins: Power the core, memories, and peripherals. Voltage is 1.8V nominal.
• VDDIO pins: Power I/O lines. Voltage is 3.3V nominal.
• VDDPLL pin: Powers the PLL. Voltage is 1.8V nominal.
• VDDUSB pin: Powers the USB. Voltage is 1.8V nominal.
• VDDOSC pin: Powers the oscillators. Voltage is 1.8V nominal.
The ground pins GND are common to VDDCORE and VDDIO. The ground pin for VDDPLL is
GNDPLL, and the GND pin for VDDOSC is GNDOSC.
See ”Electrical Characteristics” on page 928 for power consumption on the various supply pins.
4.2Power Supply Connections
Special considerations should be made when connecting the power and ground pins on a PCB.
Figure 4-1 shows how this should be done.
Figure 4-1.Connecting analog power supplies
AT32AP7002
AVDDUSB
AVDDPLL
AVDDOSC
AGNDUSB
AGNDPLL
AGNDOSC
VDDCORE
3.3uH
C54
0.10u
VCC_1V8
C56
0.10u
C55
0.10u
32054AS–AVR32–02/07
15
5.I/O Line Considerations
5.1JTAG pins
The TMS, TDI and TCK pins have pull-up resistors. TDO is an output, driven at up to VDDIO,
and have no pull-up resistor. The TRST_N pin is used to initialize the embedded JTAG TAP
Controller when asserted at a low level. It is a schmitt input and integrates permanent pull-up
resistor to VDDIO, so that it can be left unconnected for normal operations.
5.2WAKE_N pin
The WAKE_N pin is a schmitt trigger input integrating a permanent pull-up resistor to VDDIO.
5.3RESET_N pin
The RESET_N pin is a schmitt input and integrates a permanent 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.
5.4EVTI_N pin
The EVTI_N pin is a schmitt input and integrates a non-programmable pull-up resistor to VDDIO.
AT32AP7002
5.5TWI pins
5.6PIO 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 other peripherals, the
pins have the same characteristics as PIO pins.
All the I/O lines integrate a programmable pull-up resistor. Programming of this pull-up resistor is
performed independently for each I/O line through the PIO Controllers. After reset, I/O lines
default as inputs with pull-up resistors enabled, except when indicated otherwise in the column
“Reset State” of the PIO Controller multiplexing tables.
32054AS–AVR32–02/07
16
6.Memories
6.1Embedded Memories
• 32 Kbyte SRAM
– Implemented as two 16Kbyte blocks
– Single cycle access at full bus speed
6.2Physical Memory Map
The system bus is implemented as an HSB bus matrix. All system bus addresses are fixed, and
they are never remapped in any way, not even in boot. Note that AT32AP7002 by default uses
segment translation, as described in the AVR32 Architecture Manual. The 32 bit physical
address space is mapped as follows:
Table 6-1.AT32AP7002 Physical Memory Map
Start AddressSizeDevice
0x0000_000064 MbyteEBI SRAM CS0
0x0400_000064 MbyteEBI SRAM CS4
AT32AP7002
0x0800_000064 MbyteEBI SRAM CS2
0x0C00_000064 MbyteEBI SRAM CS3
0x1000_0000256 MbyteEBI SRAM/SDRAM CS1
0x2000_000064 MbyteEBI SRAM CS5
0x2400_000016 KbyteInternal SRAM 0
0x2400_400016 KbyteInternal SRAM1
0xFF00_00004 KbyteLCDC configuration
0xFF20_00001 KByteDMAC configuration
0xFF30_00001 MByteUSB Data
0xFFE0_00001 MBytePBA
0xFFF0_00001 MBytePBB
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, MCFG2 is associated
with the HSB-HSB bridge.
32054AS–AVR32–02/07
17
AT32AP7002
Table 6-2.HSB masters
Master 0CPU Dcache
Master 1CPU Icache
Master 2HSB-HSB Bridge
Master 3ISI DMA
Master 4USB DMA
Master 5LCD Controller DMA
Master 6Ethernet MAC0 DMA
Master 7Ethernet MAC1 DMA
Master 8DMAC Master Interface 0
Master 9DMAC Master Interface 1
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 PBB.
The various modules may output interrupt request signals. These signals are routed to the Interrupt Controller (INTC). The Interrupt Controller supports up to 64 groups of interrupt requests.
Each group can have up to 32 interrupt request signals. 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 semantic of the different interrupt requests.
32054AS–AVR32–02/07
20
AT32AP7002
The interrupt request signals in AT32AP7002 are connected to the INTC as follows:
Table 7-2.Interrupt Request Signal Map
GroupLineSignal
00COUNT-COMPARE match
1Performance Counter Overflow
10LCDC EOF
1LCDC LN
2LCDC LSTLN
3LCDC MER
4LCDC OWR
5LCDC UFLW
20DMAC BLOCK
1DMAC DSTT
2DMAC ERR
3DMAC SRCT
4DMAC TFR
30SPI 0
40SPI 1
50TWI
60USART0
70USART1
80USART2
90USART3
100SSC0
110SSC1
120SSC2
130PIOA
140PIOB
150PIOC
160PIOD
170PIOE
180PSIF
190EIM0
1EIM1
2EIM2
3EIM3
200PM
32054AS–AVR32–02/07
210RTC
21
Table 7-2.Interrupt Request Signal Map
GroupLineSignal
220TC00
1TC01
2TC02
230TC10
1TC11
2TC12
240PWM
270DAC
280MCI
290AC97C
300ISI
310USB
320EBI
AT32AP7002
7.3DMAC Handshake Interface Map
The following table details the hardware handshake map between the DMAC and the peripherals attached to it: :
Table 7-3.Hardware Handshaking Connection
RequestHardware Handshaking Interface
MCI RX0
MCI TX1
DAC TX2
AC97C CHANNEL A RX3
AC97C CHANNEL A TX4
AC97C CHANNEL B RX5
AC97C CHANNEL B TX6
EXTERNAL DMA REQUEST 07
EXTERNAL DMA REQUEST 18
EXTERNAL DMA REQUEST 29
EXTERNAL DMA REQUEST 310
32054AS–AVR32–02/07
22
7.4Clock Connections
7.4.1Timer/Counters
Each Timer/Counter channel can independently select an internal or external clock source for its
counter:
Table 7-4.Timer/Counter clock connections
Timer/CounterSourceNameConnection
0InternalTIMER_CLOCK1clk_slow
1InternalTIMER_CLOCK1clk_slow
AT32AP7002
TIMER_CLOCK2clk_pbb / 4
TIMER_CLOCK3clk_pbb / 8
TIMER_CLOCK4clk_pbb / 16
TIMER_CLOCK5clk_pbb / 32
ExternalXC0See Section 7.7
XC1
XC2
TIMER_CLOCK2clk_pbb / 4
TIMER_CLOCK3clk_pbb / 8
7.4.2USARTs
TIMER_CLOCK4clk_pbb / 16
TIMER_CLOCK5clk_pbb / 32
ExternalXC0See Section 7.7
XC1
XC2
Each USART can be connected to an internally divided clock:
Table 7-5.USART clock connections
USARTSourceNameConnection
0InternalCLK_DIVclk_pba / 8
1
2
3
32054AS–AVR32–02/07
23
7.4.3SPIs
Each SPI can be connected to an internally divided clock:
Table 7-6.SPI clock connections
SPISourceNameConnection
0InternalCLK_DIVclk_pba / 32
1
7.5External Interrupt Pin Mapping
External interrupt requests are connected to the following pins::
Table 7-7.External Interrupt Pin Mapping
SourceConnection
NMI_NPB24
EXTINT0PB25
EXTINT1PB26
EXTINT2PB27
AT32AP7002
EXTINT3PB28
7.6Nexus 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 AP Techni-
cal Reference Manual.
Table 7-8.Nexus OCD AUX port connections
PinAXS=0AXS=1
EVTI_NEVTI_NEVTI_N
MDO[5]PB09PC18
MDO[4]PB08PC14
MDO[3]PB07PC12
MDO[2]PB06PC11
MDO[1]PB05PC06
MDO[0]PB04PC05
EVTO_NPB03PB28
MCKOPB02PC02
MSEO[1]PB01PC01
32054AS–AVR32–02/07
MSEO[0]PB00PC00
24
7.7Peripheral Multiplexing on IO lines
The AT32AP7002 features five PIO controllers, PIOA to PIOE, that multiplex the I/O lines of the
peripheral set. Each PIO Controller controls up to thirty-two lines.
Each line can be assigned to one of two peripheral functions, A or B. The tables in the following
pages define how the I/O lines of the peripherals A and B are multiplexed on the PIO
Controllers.
Note that some output only peripheral functions might be duplicated within the tables.
7.7.1PIO Controller A Multiplexing
Table 7-9.PIO Controller A Multiplexing
I/O LinePeripheral APeripheral B
PA00SPI0 - MISOSSC1 - RX_FRAME_SYNC
PA01SPI0 - MOSISSC1 - TX_FRAME_SYNC
PA02SPI0 - SCKSSC1 - TX_CLOCK
PA03SPI0 - NPCS[0]SSC1 - RX_CLOCK
PA04SPI0 - NPCS[1]SSC1 - TX_DATA
PA05SPI0 - NPCS[2]SSC1 - RX_DATA
PA06TWI - SDAUSART0 - RTS
PA07TWI - SCLUSART0 - CTS
PA08PSIF - CLOCKUSART0 - RXD
PA09PSIF - DATAUSART0 - TXD
PA10MCI - CLKUSART0 - CLK
PA11MCI - CMDTC0 - CLK0
PA12MCI - DATA[0]TC0 - A0
PA13MCI - DATA[1]TC0 - A1
PA14MCI - DATA[2]TC0 - A2
PA15MCI - DATA[3]TC0 - B0
PA16USART1 - CLKTC0 - B1
PA17USART1 - RXDTC0 - B2
PA18USART1 - TXDTC0 - CLK2
PA19USART1 - RTSTC0 - CLK1
PA20USART1 - CTSSPI0 - NPCS[3]
PA21SSC0 - RX_FRAME_SYNCPWM - PWM[2]
PA22SSC0 - RX_CLOCKPWM - PWM[3]
PA23SSC0 - TX_CLOCKTC1 - A0
PA24SSC0 - TX_FRAME_SYNCTC1 - A1
PA25SSC0 - TX_DATATC1 - B0
PA26SSC0 - RX_DATATC1 - B1
PA27SPI1 - NPCS[3]TC1 - CLK0
PA28PWM - PWM[0]TC1 - A2
AT32AP7002
32054AS–AVR32–02/07
25
Table 7-9.PIO Controller A Multiplexing
PA29PWM - PWM[1]TC1 - B2
PA30SM - GCLK[0]TC1 - CLK1
PA31SM - GCLK[1]TC1 - CLK2
7.7.2PIO Controller B Multiplexing
Table 7-10.PIO Controller B Multiplexing
I/O LinePeripheral APeripheral B
PB00ISI - DATA[0]SPI1 - MISO
PB01ISI - DATA[1]SPI1 - MOSI
PB02ISI - DATA[2]SPI1 - NPCS[0]
PB03ISI - DATA[3]SPI1 - NPCS[1]
PB04ISI - DATA[4]SPI1 - NPCS[2]
PB05ISI - DATA[5]SPI1 - SCK
PB06ISI - DATA[6]MCI - CMD[1]
PB07ISI - DATA[7]MCI - DATA[4]
PB08ISI - HSYNCMCI - DATA[5]
PB09ISI - VSYNCMCI - DATA[6]
PB10ISI - PCLKMCI - DATA[7]
PB11PSIF - CLOCK[1]ISI - DATA[8]
PB12PSIF - DATA[1]ISI - DATA[9]
PB13SSC2 - TX_DATAISI - DATA[10]
PB14SSC2 - RX_DATAISI - DATA[11]
PB15SSC2 - TX_CLOCKUSART3 - CTS
PB16SSC2 - TX_FRAME_SYNCUSART3 - RTS
PB17SSC2 - RX_FRAME_SYNCUSART3 - TXD
PB18SSC2 - RX_CLOCKUSART3 - RXD
PB19SM - GCLK[2]USART3 - CLK
PB20DAC - DATA[1]AC97C - SDO
PB21DAC - DATA[0]AC97C - SYNC
PB22DAC - DATAN[1]AC97C - SCLK
PB23DAC - DATAN[0]AC97C - SDI
PB24NMI_NDMAC - DMARQ[0]
PB25EXTINT0DMAC - DMARQ[1]
PB26EXTINT1USART2 - RXD
PB27EXTINT2USART2 - TXD
PB28EXTINT3USART2 - CLK
PB29SM - GCLK[3]USART2 - CTS
PB30SM - GCLK[4]USART2 - RTS
AT32AP7002
32054AS–AVR32–02/07
26
7.7.3PIO Controller C Multiplexing
Table 7-11.PIO Controller C Multiplexing
I/O LinePeripheral APeripheral B
PC20LCDC - HSYNC
PC21LCDC - PCLK
PC22LCDC - VSYNC
PC23LCDC - DVAL
PC28LCDC - DATA[2]
PC29LCDC - DATA[3]
PC30LCDC - DATA[4]
PC31LCDC - DATA[5]
AT32AP7002
7.7.4PIO Controller D Multiplexing
PIO Controller D Multiplexing
Table 7-12.PIO Controller D Multiplexing
I/O LinePeripheral APeripheral B
PD00LCDC - DATA[6]
PD01LCDC - DATA[7]
PD04LCDC - DATA[10]
PD05LCDC - DATA[11]
PD06LCDC - DATA[12]
PD07LCDC - DATA[13]
PD08LCDC - DATA[14]
PD09LCDC - DATA[15]
PD12LCDC - DATA[18]
PD13LCDC - DATA[19]
PD14LCDC - DATA[20]
PD15LCDC - DATA[21]
PD16LCDC - DATA[22]
PD17LCDC - DATA[23]
32054AS–AVR32–02/07
27
AT32AP7002
7.7.5IO Pins Without Multiplexing
Many of the external EBI pins are not controlled by the PIO modules, but directly driven by the
EBI. These pins have programmable pullup resistors. These resistors are controlled by Special
Function Register 4 (SFR4) in the HMATRIX. The pullup on the lines multiplexed with PIO is
controlled by the appropriate PIO control register.
This SFR can also control CompactFlash, SmartMedia or NandFlash Support, see the EBI chapter for details
7.7.5.1HMatrix SFR4 EBI Control Register
Name:HMATRIX_SFR4
Access Type:Read/Write
3130292827262524
––––––––
2322212019181716
––––––––
15141312111098
–––––––EBI_DBPUC
76543210
––EBI_CS5AEBI_CS4AEBI_CS3A–EBI_CS1A-
• CS1A: Chip Select 1 Assignment
0 = Chip Select 1 is assigned to the Static Memory Controller.
1 = Chip Select 1 is assigned to the SDRAM Controller.
• CS3A: Chip Select 3 Assignment
0 = Chip Select 3 is only assigned to the Static Memory Controller and NCS3 behaves as
defined by the SMC.
1 = Chip Select 3 is assigned to the Static Memory Controller and the NAND Flash/SmartMedia
Logic is activated.
• CS4A: Chip Select 4 Assignment
0 = Chip Select 4 is assigned to the Static Memory Controller and NCS4, NCS5 and NCS6
behave as defined by the SMC.
1 = Chip Select 4 is assigned to the Static Memory Controller and the CompactFlash Logic is
activated.
• CS5A: Chip Select 5 Assignment
0 = Chip Select 5 is assigned to the Static Memory Controller and NCS4, NCS5 and NCS6
behave as defined by the SMC.
32054AS–AVR32–02/07
1 = Chip Select 5 is assigned to the Static Memory Controller and the CompactFlash Logic is
activated.
28
AT32AP7002
Accessing the address space reserved to NCS5 and NCS6 may lead to an unpredictable
outcome.
• EBI_DBPUC: EBI Data Bus Pull-up Control
0: EBI D[15:0] are internally pulled up to the VDDIO power supply.
enabled after reset.
1: EBI D[15:0] are not internally pulled up.
Table 7-13.IO Pins without multiplexing
I/O LineFunction
PX00EBI - DATA[0]
PX01EBI - DATA[1]
PX02EBI - DATA[2]
PX03EBI - DATA[3]
PX04EBI - DATA[4]
PX05EBI - DATA[5]
PX06EBI - DATA[6]
PX07EBI - DATA[7]
PX08EBI - DATA[8]
PX09EBI - DATA[9]
PX10EBI - DATA[10]
PX11EBI - DATA[11]
PX12EBI - DATA[12]
PX13EBI - DATA[13]
PX14EBI - DATA[14]
PX15EBI - DATA[15]
PX16EBI - ADDR[0]
PX17EBI - ADDR[1]
PX18EBI - ADDR[2]
PX19EBI - ADDR[3]
PX20EBI - ADDR[4]
PX21EBI - ADDR[5]
PX22EBI - ADDR[6]
PX23EBI - ADDR[7]
PX24EBI - ADDR[8]
PX25EBI - ADDR[9]
PX26EBI - ADDR[10]
PX27EBI - ADDR[11]
PX28EBI - ADDR[12]
PX29EBI - ADDR[13]
PX30EBI - ADDR[14]
PX31EBI - ADDR[15]
The pull-up resistors are
32054AS–AVR32–02/07
29
Table 7-13.IO Pins without multiplexing (Continued)
– SmartMedia support: 8-bit as well as 16-bit devices are supported
– CompactFlash support: all modes (Attribute Memory, Common Memory, I/O, True IDE) are
supported but the signals _IOIS16 (I/O and True IDE modes) and _ATA SEL (True IDE mode)
are not handled.
• Optimized External Bus:
– 16- or 32-bit Data Bus
– Up to 26-bit Address Bus, Up to 64-Mbytes Addressable
– Optimized pin multiplexing to reduce latencies on External Memories
• Up to 6 Chip Selects, Configurable Assignment:
– Static Memory Controller on NCS0
– SDRAM Controller or Static Memory Controller on NCS1
– Static Memory Controller on NCS2
– Static Memory Controller on NCS3, Optional NAND Flash/SmartMedia
– Static Memory Controller on NCS4 - NCS5, Optional CompactFlash
7.8.2Static Memory Controller
TM
and CompactFlashTM Support
TM
AT32AP7002
TM
Support
Support
•
• 64-Mbyte Address Space per Chip Select
• 8-, 16- or 32-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
7.8.3SDRAM Controller
•
• Programming Facilities
6 Chip Selects Available
Numerous Configurations Supported
– 2K, 4K, 8K Row Address Memory Parts
– SDRAM with Two or Four Internal Banks
– SDRAM with 16- or 32-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
32054AS–AVR32–02/07
31
• Energy-saving Capabilities
– Self-refresh, Power-down and Deep Power Modes Supported
– 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
7.8.4Error Corrected Code Controller
Hardware Error Corrected Code (ECC) Generation
•
– Detection and Correction by Software
• Supports NAND Flash and SmartMedia
• Supports NAND Flash/SmartMedia with Page Sizes of 528, 1056, 2112 and 4224 Bytes, Specified
by Software
7.8.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 MCK
– The chip select line may be left active to speed up transfers on the same device
7.8.6Two-wire Interface
™
Devices with 8- or 16-bit Data Path.
AT32AP7002
32054AS–AVR32–02/07
Compatibility with standard two-wire serial memory
•
• One, two or three bytes for slave address
• Sequential read/write operations
32
7.8.7USART
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 timeguard
– Optional Multi-drop Mode with address generation and detection
– Optional Manchester Encoding
• RS485 with driver control signal
• ISO7816, T = 0 or T = 1 Protocols for interfacing with smart cards
– NACK handling, error counter with repetition and iteration limit
• IrDA modulation and demodulation
– Communication at up to 115.2 Kbps
• Test Modes 46
– Remote Loopback, Local Loopback, Automatic Echo
7.8.8Serial Synchronous Controller
AT32AP7002
•
• 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
• Receiver and transmitter include a data signal, a clock signal and a frame synchronization signal
7.8.9AC97 Controller
•
• Capable to Interface with a Single Analog Front end
• Three independent RX Channels and three independent TX Channels
• Time Slot Assigner allowing to assign up to 12 time slots to a channel
• Channels support mono or stereo up to 20 bit sample length - Variable sampling rate AC97 Codec
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.)
event on the frame sync signal
Compatible with AC97 Component Specification V2.2
– One RX and one TX channel dedicated to the AC97 Analog Front end control
– One RX and one TX channel for data transfers, connected to the DMAC
– One RX and one TX channel for data transfers, connected to the DMAC
Interface (48KHz and below)
32054AS–AVR32–02/07
33
7.8.10Audio 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 DMA Controller for background transfer without CPU intervention
– Three external clock inputs
– Five internal clock inputs
– Two multi-purpose input/output signals
• Two global registers that act on all three TC Channels
7.8.12Pulse Width Modulation Controller
AT32AP7002
4 channels, one 16-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
Single and Dual scan color and monochrome passive STN LCD panels supported
•
• Single scan active TFT LCD panels supported
• 4-bit single scan, 8-bit single or dual scan, 16-bit dual scan STN interfaces supported
• Up to 24-bit single scan TFT interfaces supported
• Up to 16 gray levels for mono STN and up to 4096 colors for color STN displays
• 1, 2 bits per pixel (palletized), 4 bits per pixel (non-palletized) for mono STN
• 1, 2, 4, 8 bits per pixel (palletized), 16 bits per pixel (non-palletized) for color STN
• 1, 2, 4, 8 bits per pixel (palletized), 16, 24 bits per pixel (non-palletized) for TFT
• Single clock domain architecture
• Resolution supported up to 2048x2048
• 2D-DMA Controller for management of virtual Frame Buffer
– Allows management of frame buffer larger than the screen size and moving the view over this
virtual frame buffer
• Automatic resynchronization of the frame buffer pointer to prevent flickering
• Configurable coefficients with flexible fixed-point representation.
32054AS–AVR32–02/07
35
•
7.8.17Image Sensor Interface
•
ITU-R BT. 601/656 8-bit mode external interface support
• Support for ITU-R BT.656-4 SAV and EAV synchronization
• Vertical and horizontal resolutions up to 2048 x 2048
• Preview Path up to 640*480
• Support for packed data formatting for YCbCr 4:2:2 formats
• Preview scaler to generate smaller size image 50
• Programmable frame capture rate
AT32AP7002
32054AS–AVR32–02/07
36
8.Boot Sequence
This chapter summarizes the boot sequence of the AT32AP7002. The behaviour after power-up
is controlled by the Power Manager.
8.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 the power has stabilized, the device will use
the XIN0 pin as clock source. XIN0 can be connected either to an external clock, or a crystal.
The OSCEN_N pin is connected either to VDD or GND to inform the Power Manager on how the
XIN0 pin is connected. If XIN0 receives a signal from a crystal, dedicated circuitry in the Power
Manager keeps the part in a reset state until the oscillator connected to XIN0 has settled. If XIN0
receives an external clock, no such settling delay is applied.
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
XIN0 clock.
8.2Fetching of initial instructions
After reset has been released, the AVR32AP CPU starts fetching instructions from the reset
address, which is 0xA000_0000. This address lies in the P2 segment, which is non-translated,
non-cacheable, and permanently mapped to the physical address range 0x0000_0000 to
0x2000_0000. This means that the instruction being fetched from virtual address 0xA000_0000
is being fetched from physical address 0x0000_0000. Physical address 0x0000_0000 is
mapped to EBI SRAM CS0. This is the external memory the device boots from.
AT32AP7002
The code read from the SRAM CS0 memory 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.
32054AS–AVR32–02/07
37
AT32AP7002
9.Ordering Information
Figure 9-1.Ordering Information
Temperature
Ordering CodePackagePackage TypePacking
AT32AP7002-CTURCTBGA196GreenReelIndustrial (-40°C to 85°C)
AT32AP7002-CTUTCTBGA196GreenTrayIndustrial (-40°C to 85°C)
Operating Range
32054AS–AVR32–02/07
38
10. Errata
10.1Rev. C
AT32AP7002
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 Chip Select 0 BITS field overrides other Chip Selects
The BITS field for Chip Select 0 overrides BITS fields for other Chip selects.
Fix/Workaround
Update Chip Select 0 BITS field to the relevant settings before transmitting with Chip Selects
other than 0.
3. SPI LASTXFER may be overwritten
When Peripheral Select (PS) = 0, the LASTXFER-bit in the Transmit Data Register (TDR)
should be internally discared. This fails and may cause problems during DMA transfers.
Transmitting data using the PDC when PS=0, the size of the transferred data is 8- or 16-bits.
The upper 16 bits of the TDR will be written to a random value. If Chip Select Active After
Transfer (CSAAT) = 1, the behavior of the Chip Select will be unpredictable.
Fix/Workaround
- Do not use CSAAT = 1 if PS = 0
- Use GPIO to control Chip Select lines
- Select PS=1 and store data for PCS and LASTXFER for each data in transmit buffer.
4. SPI LASTXFER overrides Chip Select
The LASTXFER bit overrides Chip Select input when PS = 0 and CSAAT is used.
Fix/Workaround
- Do not use the CSAAT
- Use GPIO as Chip Select input
- Select PS = 1. Transfer 32-bit with correct LASTXFER settings.
5. MMC data drite operation with less than 12 bytes is impossible.
The Data Write operation with a number of bytes less than 12 is impossible
Fix/Workaround
The PDC counters must always be equal to 12 bytes for data transfers lower than 12 bytes.
The BLKLEN or BCNT field are used to specify the real count number.
6. MMC SDIO interrupt only works for slot A
If 1-bit data bus width and on other slots than slot A, the SDIO interrupt can not be captured.
32054AS–AVR32–02/07
Fix/Workaround
Use slot A.
39
AT32AP7002
7. PSIF TXEN/RXEN may disable the transmitter/receiver
Writing a '0' to RXEN will disable the receiver. Writing '0' to TXEN will disable the transmitter.
Fix/Workaround
When accessing the PS/2 Control Register always write '1' to RXEN to keep the receiver
enabled, and write '1' to TXEN to keep the transmitter enabled.
8. PSIF TXRDY interrupt corrupts transfers
When writing to the Transmit Holding Register (THR), the data will be transferred to the data
shift register immediately, regardless of the state of the data shift register. If a transfer is
ongoing, it will be interrupted and a new transfer will be started with the new data written to
THR.
Fix/Workaround
Use the TXEMPTY-interrupt instead of the TXRDY-interrupt to update the THR. This
ensures that a transfer is completed.
9. LCD memory error interupt does not work
Writing to the MERIT-bit in the LCD Interrupt Test Register (ITR) does not cause an interrupt
as intended. The MERIC-bit in the LCD Interrupt Clear Register (ICR) cannot be written.
This means that if the MERIS-bit in ISR is set, it cannot be cleared.
Fix/Workaround
Memory error interrupt should not be used.
10. PWN counter restarts at 0x0001
The PWN 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, ..., period
- Consecutive periods are 0x0001, 0x0002, ..., period
11. 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.
12. 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.
32054AS–AVR32–02/07
13. 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.
40
10.2Rev. B
10.3Rev. A
AT32AP7002
Fix/Workaround
Reading the PWM channel status of a disabled channel is only correct after a PWM period
14. TWI transfer error without ACK
If the TWI does not receive an ACK from a slave during the address+R/W phase, no bits in
the status register will be set to indicate this. Hence, the transfer will never complete.
Fix/Workaround
To prevent errors due to missing ACK, the software should use a timeout mechanism to terminate the transfer if this happens.
Not sampled.
Not sampled.
32054AS–AVR32–02/07
41
11. 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.
1150 East Cheyenne Mtn. Blvd.
Colorado Springs, CO 80906, USA
Tel: 1(719) 576-3300
Fax: 1(719) 540-1759
Biometrics/Imaging/Hi-Rel MPU/
High Speed Converters/RF Datacom
Avenue de Rochepleine
BP 123
38521 Saint-Egreve Cedex, France
Tel: (33) 4-76-58-30-00
Fax: (33) 4-76-58-34-80
Literature Requests
www.atmel.com/literature
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 connection 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 INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES 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 herein. 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 support or sustain life.