AT32AP7000 Summary - Mature

Features
• High Performance, Low Power AVR®32 32-Bit Microcontroller
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
– 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
Pixel Co-Processor
– Pixel Co-Processor 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
capabilities
4 Universal Synchronous/Asynchronous Receiver/Transmitters (USART)
– 115.2 kbps IrDA Modulation and Demodulation
– Hardware and software handshaking
3 Synchronous Serial Protocol controllers
– Supports I2S, SPI and generic frame-based protocols
Two-Wire Interface
– Sequential Read/Write Operations, Philips’ I2C© compliant
Liquid Crystal Display (LCD) interface
– Supports TFT displays
– Configurable pixel resolution supporting QCIF/QVGA/VGA/SVGA configurations.
Image Sensor Interface
– 12-bit Data Interface for CMOS cameras
Universal Serial Bus (USB) 2.0 High Speed (480 Mbps) Device
– On-chip Transceivers with physical interface
2 Ethernet MAC 10/100 Mbps interfaces
– 802.3 Ethernet Media Access Controller
– Supports Media Independent Interface (MII) and Reduced MII (RMII)
16-bit stereo audio bitstream 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
– AT32AP7000: 256-ball CTBGA 1.0 mm pitch/160 GPIO pins
Power supplies
– 1.65V to1.95V VDDCORE
– 3.0V to 3.6V VDDIO
AVR®32 32-bit
Microcontroller
AT32AP7000
Preliminary
Summary
32003MS-AVR32-09/09
AT32AP7000
1. Part Description
The AT32AP7000 is a complete System-on-chip application processor with an AVR32 RISC
processor achieving 210 DMIPS running at 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.
AT32AP7000 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.
AT32AP7000 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, MultiMedia 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.
AT32AP7000 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.
Synchronous Serial Controllers provide easy access to serial communication protocols, audio
standards like I2S and frame-based protocols.
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.
PS2 connectivity is provided for standard input devices like mice and keyboards.
2
32003MS–AVR32–09/09
AT32AP7000
AT32AP7000 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.
3
32003MS–AVR32–09/09
AT32AP7000
2. Blockdiagram
Blockdiagram
JTAG
INTERFACE
NEXUS
CLASS 3
OCD
DMA
DMA
S
M
S
CLK
CMD
DATA[7..0]
SCLK
SDI
SSYNC
SDO
CONFIGURATION
PB
HS
B
MULTIMEDIA CARD
INTERFACE
AC97 CONTROLLER
32 KHz
OSC
XIN0
XIN1
OSC1
XOUT1
PLL0
PLL0
PLL1
PLL1
GCLK[3..0]
OSCEN_N
RESET_N
HSB-HSB BRIDGE
PERIPHERAL
DMA
CONTROLLER
PBA
PB
RAS,
CAS,
SDWE,
NANDOE,
NANDWE,
SDCK,
SDCKE,
NWE3,
NWE1,
NWE0,
NRD,
NCS[3,1,0],
ADDR[22..0]
DATA[15..0]
NWAIT
NCS[5,4,2]
CFRNW,
CFCE1,
CFCE2,
ADDR[23..25]
DATA[31..16]
USART0
USART1
USART2
USART3
SERIAL
PERIPHERAL
INTERFACE 0/1
SYNCHRONOUS
SERIAL
CONTROLLER 0/1/2
TWO-WIRE
INTERFACE
RXD
TXD
CLK
RTS, CTS
SCK
MISO, MOSI
NPCS0
NPCS[3..1]
TX_CLOCK, TX_FRAME_SYNC
TX_DATA
RX_CLOCK, RX_FRAME_SYNC
PA
PB
PC
PD
PE
RX_DATA
SCL
SDA
CLOCK
GENERATOR
OSC0
XOUT0
REGISTERS BUS
HSB-PB
BRIDGE A
DMA
AUDIO BITSTREAM
DAC
M
HSB
HSB-PB
BRIDGE
B
POWER
MANAGER
XIN32
XOUT32
S
S MM S
DMA
DATA0N
DATA1N
DMA
EXTERNAL BUS INTERFACE
(SDRAM & STATIC MEMORY
CONTROLLER & ECC)
S
DMA CONTROLLER
DATA0
DATA1
S
M
HIGH SPEED
BUS MATRIX
INTRAM0
INTRAM1
MACB0
MACB1
M
M
M
VSYNC,
HSYNC,
PWR,
PCLK,
MODE,
DVAL,
CC,
DATA[22..0],
GPL[7..0]
M
DMA
Parallel Input/Output Controllers
MDC,
TXD[3..0],
TX_CLK,
TX_EN,
TX_ER,
SPEED
MDIO
PA
PB
PC
PD
PE
S
M
IMAGE
SENSOR
INTERFACE
COL,
CRS,
RXD[3..0],
RX_CLK,
RX_DV,
RX_ER
LCD
CONTRO
LLER
PDC
USB
INTERFACE
PBB
EVTO_N
DATA[11..0]
HSYNC
VSYNC
PCLK
DATA
CACHE
INSTR
CACHE
EVTI_N
D+
D-
MEMORY MANAGEMENT UNIT
Parallel Input/Output Controllers
MCKO
MDO[5..0]
MSEO[1..0]
PIXEL COPROCESSOR
AP CPU
PDC
TRST_N
TCK
TDO
TDI
TMS
PDC
Figure 2-1.
CLOCK[1..0]
CLOCK
CONTROLLER
SLEEP
CONTROLLER
RESET
CONTROLLER
PS2 INTERFACE
DATA[1..0]
REAL TIME
COUNTER
WATCHDOG
TIMER
A[2..0]
B[2..0]
CLK[2..0]
TIMER/COUNTER 0/1
INTERRUPT
CONTROLLER
EXTINT[7..0]
KPS[7..0]
NMI_N
EXTERNAL
INTERRUPT
CONTROLLER
PULSE WIDTH
MODULATION
CONTROLLER
PWM0
PWM1
PWM2
PWM3
4
32003MS–AVR32–09/09
AT32AP7000
2.0.1
AVR32AP CPU
• 32-bit load/store AVR32B RISC architecture.
–
–
–
–
–
•
•
•
•
2.0.2
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.
16Kbyte Instruction and 16Kbyte data caches.
– Virtually indexed, physically tagged.
– 4-way associative.
– Write-through or write-back.
Nexus Class 3 On-Chip Debug system.
– Low-cost NanoTrace supported.
Pixel Coprocessor (PICO)
• Coprocessor coupled to the AVR32 CPU Core through the TCB Bus.
•
•
•
•
– Coprocessor number one on 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.
– Supports packed and planar output formats.
5
32003MS–AVR32–09/09
AT32AP7000
• Configurable coefficients with flexible fixed-point representation.
2.0.3
Debug and Test system
•
•
•
•
•
•
•
2.0.4
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
DMA 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
• Single-block DMA Transfer
• Multi-block DMA Transfer
– Linked Lists
– Auto-Reloading
– Contiguous Blocks
• DMA Controller is Always the Flow Controller
• Additional Features
– Scatter and Gather Operations
– Channel Locking
– Bus Locking
– FIFO Mode
– Pseudo Fly-by Operation
2.0.5
Peripheral 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.
• Eighteen channels
– Two for each USART
– Two for each Serial Synchronous Controller
– Two for each Serial Peripheral Interface
2.0.6
Bus 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, Ethernet Controller 0, Ethernet Controller 1, DMA Controller 0, DMA
Controller 1, and to internal SRAM 0, internal SRAM 1, PB A, PB B, EBI and, USB.
6
32003MS–AVR32–09/09
AT32AP7000
– 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 DMACA.
• 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.
7
32003MS–AVR32–09/09
AT32AP7000
Package and PinoutAVR32AP7000
2.1
Figure 2-2.
256 CTBGA Pinout
TOP VIEW
BOTTOM VIEW
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Ball A1
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
T
Table 2-1.
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
T
AVR32
CTBGA256 Package Pinout A1..T8
1
2
3
4
5
6
7
8
A VDDIO
PE15
PE13
PE11
PE07
PE02
AGNDPLL
OSCEN_N
B GNDIO
PE16
PE12
PE09
PE04
PLL0
AVDDOSC
PC30
C PD01
PD00
PE14
PE10
PE06
PE00
PLL1
PC31
D PE17
PE18
PD02
PE08
PE03
GND
AGNDOSC
PC29
E PX48
PX50
PX49
PX47
PE05
PE01
XOUT32
PC28
F PX32
PX00
PX33
VDDIO
PX51
AVDDPLL
XIN0
PC27
G PX04
VDDCORE
PX05
PX03
PX02
PX01
XOUT0
PC26
H PD06
VDDIO
PD07
PD05
PD04
PD03
GND
XIN32
J TRST_N
TMS
TDI
TCK
TDO
PD09
PD08
EVTI_N
K PA05
PA01
PA02
PA00
RESET_N
PA03
PA04
HSDP
L PA09
PB25
VDDIO
PA08
GND
PB24
AGNDUSB
VDDCORE
M PA14
PA11
PA13
PA10
PA12
VDDIO
VDDIO
GND
N PA18
PA16
PA17
PA15
PD14
GND
FSDM
VBG
P PA20
PA19
PA21
PD11
PD16
XOUT1
GND
PA25
R PA22
PD10
PA23
PD13
PD17
AVDDUSB
HSDM
PA26
T VDDIO
GND
PA24
PD12
PD15
XIN1
FSDP
VDDIO
8
32003MS–AVR32–09/09
AT32AP7000
Table 2-2.
CTBGA256 Package Pinout A9..T16
9
10
11
12
13
14
15
16
A PC23
PA06
PB21
PB16
PB13
PB11
GND
VDDIO
B PC25
PC19
PB23
PB18
PB14
PB10
PC17
PC16
C PC24
PA07
PB22
PB17
PB12
PB09
PB07
PB08
D PC22
PC18
PB20
PB15
PB03
PB05
PB04
PB06
E VDDIO
GND
PB19
PB00
PX46
PB01
VDDIO
PB02
F PC21
VDDCORE
GND
PX44
PX42
PX43
PX40
PX45
G PC20
PC15
PC14
PC10
PC11
PC13
PC12
VDDCORE
H PC09
PC05
PC06
PE26
VDDIO
PC07
PX39
PC08
J PB27
PX27
PX28
PX29
PX30
VDDCORE
GND
PX31
K PA27
GND
PX22
PX23
PX24
PX26
VDDIO
PX25
L PA28
VDDIO
PE24
PX38
PX18
PX20
PX21
PX19
M PA29
PB28
PE20
PX08
PX34
PX36
PX37
PX35
N PA30
PX53
PE22
PX06
PX11
PX15
PX17
PX16
P WAKE_N
PX41
PE21
PX09
PB30
PC02
PX13
PX14
R PA31
PX52
PE23
PX07
PB29
PC00
PC04
GND
T PB26
PE25
PE19
PX10
PX12
PC01
PC03
VDDIO
9
32003MS–AVR32–09/09
AT32AP7000
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.
Table 3-1.
Signal Description List
Signal Name
Function
Type
Active
Level
Comments
Power
AVDDPLL
PLL Power Supply
Power
1.65 to 1.95 V
AVDDUSB
USB Power Supply
Power
1.65 to 1.95 V
AVDDOSC
Oscillator Power Supply
Power
1.65 to 1.95 V
VDDCORE
Core Power Supply
Power
1.65 to 1.95 V
VDDIO
I/O Power Supply
Power
3.0 to 3.6V
AGNDPLL
PLL Ground
Ground
AGNDUSB
USB Ground
Ground
AGNDOSC
Oscillator Ground
Ground
GND
Ground
Ground
Clocks, Oscillators, and PLL’s
XIN0, XIN1, XIN32
Crystal 0, 1, 32 Input
Analog
XOUT0, XOUT1,
XOUT32
Crystal 0, 1, 32 Output
Analog
PLL0, PLL1
PLL 0,1 Filter Pin
Analog
JTAG
TCK
Test Clock
Input
TDI
Test Data In
Input
TDO
Test Data Out
TMS
Test Mode Select
Input
TRST_N
Test Reset
Input
Output
Low
Auxiliary Port - AUX
MCKO
Trace Data Output Clock
Output
MDO0 - MDO5
Trace Data Output
Output
MSEO0 - MSEO1
Trace Frame Control
Output
EVTI_N
Event In
Input
Low
10
32003MS–AVR32–09/09
AT32AP7000
Table 3-1.
Signal Description List
Signal Name
Function
Type
Active
Level
EVTO_N
Event Out
Output
Low
Comments
Power Manager - PM
GCLK0 - GCLK4
Generic Clock Pins
Output
OSCEN_N
Oscillator Enable
Input
Low
RESET_N
Reset Pin
Input
Low
WAKE_N
Wake Pin
Input
Low
External Interrupt Controller - EIC
EXTINT0 - EXTINT3
External Interrupt Pins
Input
NMI_N
Non-Maskable Interrupt Pin
Input
Low
AC97 Controller - AC97C
SCLK
AC97 Clock Signal
Input
SDI
AC97 Receive Signal
Output
SDO
AC97 Transmit Signal
Output
SYNC
AC97 Frame Synchronization Signal
Input
Audio Bitstream DAC - ABDAC
DATA0 - DATA1
D/A Data Out
Output
DATAN0 - DATAN1
D/A Inverted Data Out
Output
Ethernet MAC - MACB0, MACB1
COL
Collision Detect
Input
CRS
Carrier Sense and Data Valid
Input
MDC
Management Data Clock
MDIO
Management Data Input/Output
RXD0 - RXD3
Receive Data
Input
RX_CLK
Receive Clock
Input
RX_DV
Receive Data Valid
Input
RX_ER
Receive Coding Error
Input
SPEED
Speed
Output
TXD0 - TXD3
Transmit Data
Output
Output
I/O
11
32003MS–AVR32–09/09
AT32AP7000
Table 3-1.
Signal Description List
Signal Name
Function
Type
TX_CLK
Transmit Clock or Reference Clock
Input
TX_EN
Transmit Enable
Output
TX_ER
Transmit Coding Error
Output
Active
Level
Comments
External Bus Interface - EBI
PX0 - PX53
I/O Controlled by EBI
I/O
ADDR0 - ADDR25
Address Bus
Output
CAS
Column Signal
Output
Low
CFCE1
Compact Flash 1 Chip Enable
Output
Low
CFCE2
Compact Flash 2 Chip Enable
Output
Low
CFRNW
Compact Flash Read Not Write
Output
DATA0 - DATA31
Data Bus
NANDOE
NAND Flash Output Enable
Output
Low
NANDWE
NAND Flash Write Enable
Output
Low
NCS0 - NCS5
Chip Select
Output
Low
NRD
Read Signal
Output
Low
NWAIT
External Wait Signal
Input
Low
NWE0
Write Enable 0
Output
Low
NWE1
Write Enable 1
Output
Low
NWE3
Write Enable 3
Output
Low
RAS
Row Signal
Output
Low
SDA10
SDRAM Address 10 Line
Output
SDCK
SDRAM Clock
Output
SDCKE
SDRAM Clock Enable
Output
SDWE
SDRAM Write Enable
Output
I/O
Low
Image Sensor Interface - ISI
DATA0 - DATA11
Image Sensor Data
Input
HSYNC
Horizontal Synchronization
Input
PCLK
Image Sensor Data Clock
Input
12
32003MS–AVR32–09/09
AT32AP7000
Table 3-1.
Signal Description List
Signal Name
Function
Type
VSYNC
Vertical Synchronization
Input
Active
Level
Comments
LCD Controller - LCDC
CC
LCD Contrast Control
Output
DATA0 - DATA23
LCD Data Bus
Input
DVAL
LCD Data Valid
Output
GPL0 - GPL7
LCD General Purpose Lines
Output
HSYNC
LCD Horizontal Synchronization
Output
MODE
LCD Mode
Output
PCLK
LCD Clock
Output
PWR
LCD Power
Output
VSYNC
LCD Vertical Synchronization
Output
MultiMedia Card Interface - MCI
CLK
Multimedia Card Clock
Output
CMD0 - CMD1
Multimedia Card Command
I/O
DATA0 - DATA7
Multimedia Card Data
I/O
Parallel Input/Output - PIOA, PIOB, PIOC, PIOD, PIOE
PA0 - PA31
Parallel I/O Controller PIOA
I/O
PB0 - PB30
Parallel I/O Controller PIOB
I/O
PC0 - PC31
Parallel I/O Controller PIOC
I/O
PD0 - PD17
Parallel I/O Controller PIOD
I/O
PE0 - PE26
Parallel I/O Controller PIOE
I/O
PS2 Interface - PSIF
CLOCK0 - CLOCK1
PS2 Clock
Input
DATA0 - DATA1
PS2 Data
I/O
Serial Peripheral Interface - SPI0, SPI1
MISO
Master In Slave Out
I/O
MOSI
Master Out Slave In
I/O
NPCS0 - NPCS3
SPI Peripheral Chip Select
I/O
Low
13
32003MS–AVR32–09/09
AT32AP7000
Table 3-1.
Signal Description List
Signal Name
Function
SCK
Clock
Type
Active
Level
Comments
Output
Synchronous Serial Controller - SSC0, SSC1, SSC2
RX_CLOCK
SSC Receive Clock
I/O
RX_DATA
SSC Receive Data
Input
RX_FRAME_SYNC
SSC Receive Frame Sync
I/O
TX_CLOCK
SSC Transmit Clock
I/O
TX_DATA
SSC Transmit Data
Output
TX_FRAME_SYNC
SSC Transmit Frame Sync
I/O
DMA Controller - DMACA
DMARQ0 - DMARQ3
DMA Requests
Input
Timer/Counter - TIMER0, TIMER1
A0
Channel 0 Line A
I/O
A1
Channel 1 Line A
I/O
A2
Channel 2 Line A
I/O
B0
Channel 0 Line B
I/O
B1
Channel 1 Line B
I/O
B2
Channel 2 Line B
I/O
CLK0
Channel 0 External Clock Input
Input
CLK1
Channel 1 External Clock Input
Input
CLK2
Channel 2 External Clock Input
Input
Two-wire Interface - TWI
SCL
Serial Clock
I/O
SDA
Serial Data
I/O
Universal Synchronous Asynchronous Receiver Transmitter - USART0, USART1, USART2, USART3
CLK
Clock
CTS
Clear To Send
RTS
Request To Send
RXD
Receive Data
I/O
Input
Output
Input
14
32003MS–AVR32–09/09
AT32AP7000
Table 3-1.
Signal Description List
Signal Name
Function
TXD
Transmit Data
Type
Active
Level
Comments
Output
Pulse Width Modulator - PWM
PWM0 - PWM3
PWM Output Pins
Output
USB Interface - USBA
HSDM
High Speed USB Interface Data -
Analog
FSDM
Full Speed USB Interface Data -
Analog
HSDP
High Speed USB Interface Data +
Analog
FSDP
Full Speed USB Interface Data +
Analog
VBG
USB bandgap
Analog
Connected to a 6810 Ohm ± 0.5%
resistor to gound and a 10 pF
capacitor to ground.
15
32003MS–AVR32–09/09
AT32AP7000
4. Power Considerations
4.1
Power Supplies
The AT32AP7000 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.2
Power 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
C54
0.10u
AVDDUSB
AVDDPLL
AVDDOSC
AGNDUSB
AGNDPLL
AGNDOSC
C56
0.10u
C55
0.10u
3.3uH
VDDCORE
VCC_1V8
16
32003MS–AVR32–09/09
AT32AP7000
5. I/O Line Considerations
5.1
JTAG 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.2
WAKE_N pin
The WAKE_N pin is a schmitt trigger input integrating a permanent pull-up resistor to VDDIO.
5.3
RESET_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.4
EVTI_N pin
The EVTI_N pin is a schmitt input and integrates a non-programmable pull-up resistor to VDDIO.
5.5
TWI 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.
5.6
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.
17
32003MS–AVR32–09/09
AT32AP7000
6. Memories
6.1
Embedded Memories
• 32 Kbyte SRAM
– Implemented as two 16Kbyte blocks
– Single cycle access at full bus speed
6.2
Physical 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 AT32AP7000 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.
AT32AP7000 Physical Memory Map
Start Address
Size
Device
0x0000_0000
64 Mbyte
EBI SRAM CS0
0x0400_0000
64 Mbyte
EBI SRAM CS4
0x0800_0000
64 Mbyte
EBI SRAM CS2
0x0C00_0000
64 Mbyte
EBI SRAM CS3
0x1000_0000
256 Mbyte
EBI SRAM/SDRAM CS1
0x2000_0000
64 Mbyte
EBI SRAM CS5
0x2400_0000
16 Kbyte
Internal SRAM 0
0x2400_4000
16 Kbyte
Internal SRAM1
0xFF00_0000
4 Kbyte
LCDC configuration
0xFF20_0000
1 KByte
DMACA configuration
0xFF30_0000
1 MByte
USBA Data
0xFFE0_0000
1 MByte
PBA
0xFFF0_0000
1 MByte
PBB
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.
18
32003MS–AVR32–09/09
AT32AP7000
Table 6-2.
HSB masters
Master 0
CPU Dcache
Master 1
CPU Icache
Master 2
HSB-HSB Bridge
Master 3
ISI DMA
Master 4
USBA DMA
Master 5
LCD Controller DMA
Master 6
Ethernet MAC0 DMA
Master 7
Ethernet MAC1 DMA
Master 8
DMAC Master Interface 0
Master 9
DMAC 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.
Table 6-3.
HSB slaves
Slave 0
Internal SRAM 0
Slave 1
Internal SRAM1
Slave 2
PBA
Slave 3
PBB
Slave 4
EBI
Slave 5
USBA data
Slave 6
LCDC configuration
Slave 7
DMACA configuration
19
32003MS–AVR32–09/09
AT32AP7000
7. Peripherals
7.1
Peripheral address map
Table 7-1.
Peripheral Address Mapping
Address
0xFF000000
0xFF200000
0xFF300000
0xFFE00000
0xFFE00400
0xFFE00800
0xFFE00C00
0xFFE01000
0xFFE01400
0xFFE01800
0xFFE01C00
0xFFE02000
0xFFE02400
0xFFE02800
0xFFE02C00
0xFFE03000
0xFFE03400
Peripheral Name
Bus
LCD Controller Slave Interface - LCDC
HSB
DMA Controller Slave Interface- DMACA
HSB
USBA
USB Slave Interface - USBA
HSB
SPI0
Serial Peripheral Interface - SPI0
PB A
SPI1
Serial Peripheral Interface - SPI1
PB A
TWI
Two-wire Interface - TWI
PB A
USART0
Universal Synchronous Asynchronous Receiver
Transmitter - USART0
PB A
USART1
Universal Synchronous Asynchronous Receiver
Transmitter - USART1
PB A
USART2
Universal Synchronous Asynchronous Receiver
Transmitter - USART2
PB A
USART3
Universal Synchronous Asynchronous Receiver
Transmitter - USART3
PB A
SSC0
Synchronous Serial Controller - SSC0
PB A
SSC1
Synchronous Serial Controller - SSC1
PB A
SSC2
Synchronous Serial Controller - SSC2
PB A
PIOA
Parallel Input/Output 2 - PIOA
PB A
PIOB
Parallel Input/Output 2 - PIOB
PB A
PIOC
Parallel Input/Output 2 - PIOC
PB A
PIOD
Parallel Input/Output 2 - PIOD
PB A
LCDC
DMACA
20
32003MS–AVR32–09/09
AT32AP7000
Table 7-1.
Peripheral Address Mapping (Continued)
Address
0xFFE03800
0xFFE03C00
0xFFF00000
0xFFF00080
0xFFF000B0
0xFFF00100
0xFFF00400
0xFFF00800
0xFFF00C00
0xFFF01000
0xFFF01400
0xFFF01800
0xFFF01C00
0xFFF02000
0xFFF02400
0xFFF02800
0xFFF02C00
0xFFF03000
0xFFF03400
Peripheral Name
Bus
PIOE
Parallel Input/Output 2 - PIOE
PB A
PSIF
PS2 Interface - PSIF
PB A
PM
Power Manager - PM
PB B
RTC
Real Time Counter- RTC
PB B
WDT
WatchDog Timer- WDT
PB B
External Interrupt Controller - EIC
PB B
Interrupt Controller - INTC
PB B
HSB Matrix - HMATRIX
PB B
TC0
Timer/Counter - TC0
PB B
TC1
Timer/Counter - TC1
PB B
PWM
Pulse Width Modulation Controller - PWM
PB B
MACB0
Ethernet MAC - MACB0
PB B
MACB1
Ethernet MAC - MACB1
PB B
ABDAC
Audio Bitstream DAC - ABDAC
PB B
MCI
MultiMedia Card Interface - MCI
PB B
AC97 Controller - AC97C
PB B
Image Sensor Interface - ISI
PB B
USBA
USB Configuration Interface - USBA
PB B
SMC
Static Memory Controller - SMC
PB B
EIC
INTC
HMATRIX
AC97C
ISI
21
32003MS–AVR32–09/09
AT32AP7000
Table 7-1.
Peripheral Address Mapping (Continued)
Address
0xFFF03800
0xFFF03C00
7.2
SDRAMC
ECC
Peripheral Name
Bus
SDRAM Controller - SDRAMC
PB B
Error Correcting Code Controller - ECC
PB B
Interrupt Request Signal Map
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.
The interrupt request signals in AT32AP7000 are connected to the INTC as follows:
Table 7-2.
Interrupt Request Signal Map
Group
Line
Signal
0
0
COUNT-COMPARE match
1
Performance Counter Overflow
0
LCDC EOF
1
LCDC LN
2
LCDC LSTLN
3
LCDC MER
4
LCDC OWR
5
LCDC UFLW
0
DMACA BLOCK
1
DMACA DSTT
2
DMACA ERR
3
DMACA SRCT
4
DMACA TFR
3
0
SPI 0
4
0
SPI 1
5
0
TWI
6
0
USART0
7
0
USART1
8
0
USART2
9
0
USART3
10
0
SSC0
11
0
SSC1
1
2
22
32003MS–AVR32–09/09
AT32AP7000
Table 7-2.
Interrupt Request Signal Map
Group
Line
Signal
12
0
SSC2
13
0
PIOA
14
0
PIOB
15
0
PIOC
16
0
PIOD
17
0
PIOE
18
0
PSIF
19
0
EIC0
1
EIC1
2
EIC2
3
EIC3
20
0
PM
21
0
RTC
22
0
TC00
1
TC01
2
TC02
0
TC10
1
TC11
2
TC12
24
0
PWM
25
0
MACB0
26
0
MACB1
27
0
ABDAC
28
0
MCI
29
0
AC97C
30
0
ISI
31
0
USBA
32
0
EBI
23
23
32003MS–AVR32–09/09
AT32AP7000
7.3
DMACA Handshake Interface Map
The following table details the hardware handshake map between the DMACA and the peripherals attached to it: :
Table 7-3.
Hardware Handshaking Connection
Request
Hardware Handshaking Interface
MCI RX
0
MCI TX
1
ABDAC TX
2
AC97C CHANNEL A RX
3
AC97C CHANNEL A TX
4
AC97C CHANNEL B RX
5
AC97C CHANNEL B TX
6
EXTERNAL DMA REQUEST 0
7
EXTERNAL DMA REQUEST 1
8
EXTERNAL DMA REQUEST 2
9
EXTERNAL DMA REQUEST 3
10
24
32003MS–AVR32–09/09
AT32AP7000
7.4
7.4.1
Clock Connections
Timer/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/Counter
Source
Name
Connection
0
Internal
TIMER_CLOCK1
clk_osc32
TIMER_CLOCK2
clk_pbb / 4
TIMER_CLOCK3
clk_pbb / 8
TIMER_CLOCK4
clk_pbb / 16
TIMER_CLOCK5
clk_pbb / 32
XC0
See Section 7.7
External
XC1
XC2
1
Internal
External
TIMER_CLOCK1
clk_osc32
TIMER_CLOCK2
clk_pbb / 4
TIMER_CLOCK3
clk_pbb / 8
TIMER_CLOCK4
clk_pbb / 16
TIMER_CLOCK5
clk_pbb / 32
XC0
See Section 7.7
XC1
XC2
7.4.2
USARTs
Each USART can be connected to an internally divided clock:
Table 7-5.
USART clock connections
USART
Source
Name
Connection
0
Internal
CLK_DIV
clk_pba / 8
1
2
3
25
32003MS–AVR32–09/09
AT32AP7000
7.4.3
SPIs
Each SPI can be connected to an internally divided clock:
Table 7-6.
SPI clock connections
SPI
Source
Name
Connection
0
Internal
CLK_DIV
clk_pba / 32
1
7.4.4
USBA
OSC1 is connected to the USB HS Phy and must be 12 MHz when using the USBA.
7.5
External Interrupt Pin Mapping
External interrupt requests are connected to the following pins::
Table 7-7.
7.6
External Interrupt Pin Mapping
Source
Connection
NMI_N
PB24
EXTINT0
PB25
EXTINT1
PB26
EXTINT2
PB27
EXTINT3
PB28
Nexus 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 Technical Reference Manual.
Table 7-8.
Nexus OCD AUX port connections
Pin
AXS=0
AXS=1
EVTI_N
EVTI_N
EVTI_N
MDO[5]
PB09
PC18
MDO[4]
PB08
PC14
MDO[3]
PB07
PC12
MDO[2]
PB06
PC11
MDO[1]
PB05
PC06
MDO[0]
PB04
PC05
EVTO_N
PB03
PB28
MCKO
PB02
PC02
MSEO[1]
PB01
PC01
MSEO[0]
PB00
PC00
26
32003MS–AVR32–09/09
AT32AP7000
7.7
Peripheral Multiplexing on IO lines
The AT32AP7000 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.1
PIO Controller A Multiplexing
Table 7-9.
PIO Controller A Multiplexing
CTBGA256
I/O Line
Peripheral A
Peripheral B
K4
PA00
SPI0 - MISO
SSC1 - RX_FRAME_SYNC
K2
PA01
SPI0 - MOSI
SSC1 - TX_FRAME_SYNC
K3
PA02
SPI0 - SCK
SSC1 - TX_CLOCK
K6
PA03
SPI0 - NPCS[0]
SSC1 - RX_CLOCK
K7
PA04
SPI0 - NPCS[1]
SSC1 - TX_DATA
K1
PA05
SPI0 - NPCS[2]
SSC1 - RX_DATA
A10
PA06
TWI - SDA
USART0 - RTS
C10
PA07
TWI - SCL
USART0 - CTS
L4
PA08
PSIF - CLOCK
USART0 - RXD
L1
PA09
PSIF - DATA
USART0 - TXD
M4
PA10
MCI - CLK
USART0 - CLK
M2
PA11
MCI - CMD
TC0 - CLK0
M5
PA12
MCI - DATA[0]
TC0 - A0
M3
PA13
MCI - DATA[1]
TC0 - A1
M1
PA14
MCI - DATA[2]
TC0 - A2
N4
PA15
MCI - DATA[3]
TC0 - B0
N2
PA16
USART1 - CLK
TC0 - B1
N3
PA17
USART1 - RXD
TC0 - B2
N1
PA18
USART1 - TXD
TC0 - CLK2
P2
PA19
USART1 - RTS
TC0 - CLK1
P1
PA20
USART1 - CTS
SPI0 - NPCS[3]
P3
PA21
SSC0 - RX_FRAME_SYNC
PWM - PWM[2]
R1
PA22
SSC0 - RX_CLOCK
PWM - PWM[3]
R3
PA23
SSC0 - TX_CLOCK
TC1 - A0
T3
PA24
SSC0 - TX_FRAME_SYNC
TC1 - A1
P8
PA25
SSC0 - TX_DATA
TC1 - B0
R8
PA26
SSC0 - RX_DATA
TC1 - B1
K9
PA27
SPI1 - NPCS[3]
TC1 - CLK0
L9
PA28
PWM - PWM[0]
TC1 - A2
27
32003MS–AVR32–09/09
AT32AP7000
Table 7-9.
7.7.2
PIO Controller A Multiplexing
M9
PA29
PWM - PWM[1]
TC1 - B2
N9
PA30
PM - GCLK[0]
TC1 - CLK1
R9
PA31
PM - GCLK[1]
TC1 - CLK2
PIO Controller B Multiplexing
Table 7-10.
PIO Controller B Multiplexing
CTBGA256
I/O Line
Peripheral A
Peripheral B
E12
PB00
ISI - DATA[0]
SPI1 - MISO
E14
PB01
ISI - DATA[1]
SPI1 - MOSI
E16
PB02
ISI - DATA[2]
SPI1 - NPCS[0]
D13
PB03
ISI - DATA[3]
SPI1 - NPCS[1]
D15
PB04
ISI - DATA[4]
SPI1 - NPCS[2]
D14
PB05
ISI - DATA[5]
SPI1 - SCK
D16
PB06
ISI - DATA[6]
MCI - CMD[1]
C15
PB07
ISI - DATA[7]
MCI - DATA[4]
C16
PB08
ISI - HSYNC
MCI - DATA[5]
C14
PB09
ISI - VSYNC
MCI - DATA[6]
B14
PB10
ISI - PCLK
MCI - DATA[7]
A14
PB11
PSIF - CLOCK[1]
ISI - DATA[8]
C13
PB12
PSIF - DATA[1]
ISI - DATA[9]
A13
PB13
SSC2 - TX_DATA
ISI - DATA[10]
B13
PB14
SSC2 - RX_DATA
ISI - DATA[11]
D12
PB15
SSC2 - TX_CLOCK
USART3 - CTS
A12
PB16
SSC2 - TX_FRAME_SYNC
USART3 - RTS
C12
PB17
SSC2 - RX_FRAME_SYNC
USART3 - TXD
B12
PB18
SSC2 - RX_CLOCK
USART3 - RXD
E11
PB19
PM - GCLK[2]
USART3 - CLK
D11
PB20
ABDAC - DATA[1]
AC97C - SDO
A11
PB21
ABDAC - DATA[0]
AC97C - SYNC
C11
PB22
ABDAC - DATAN[1]
AC97C - SCLK
B11
PB23
ABDAC - DATAN[0]
AC97C - SDI
L6
PB24
NMI_N
DMACA - DMARQ[0]
L2
PB25
EXTINT0
DMACA - DMARQ[1]
T9
PB26
EXTINT1
USART2 - RXD
J9
PB27
EXTINT2
USART2 - TXD
M10
PB28
EXTINT3
USART2 - CLK
R13
PB29
PM - GCLK[3]
USART2 - CTS
P13
PB30
PM - GCLK[4]
USART2 - RTS
28
32003MS–AVR32–09/09
AT32AP7000
7.7.3
PIO Controller C Multiplexing
Table 7-11.
PIO Controller C Multiplexing
CTBGA256
I/O Line
Peripheral A
Peripheral B
R14
PC00
MACB0 - COL
T14
PC01
MACB0 - CRS
P14
PC02
MACB0 - TX_ER
T15
PC03
MACB0 - TXD[0]
R15
PC04
MACB0 - TXD[1]
H10
PC05
MACB0 - TXD[2]
DMACA - DMARQ[2]
H11
PC06
MACB0 - TXD[3]
DMACA - DMARQ[3]
H14
PC07
MACB0 - TX_EN
H16
PC08
MACB0 - TX_CLK
H9
PC09
MACB0 - RXD[0]
G12
PC10
MACB0 - RXD[1]
G13
PC11
MACB0 - RXD[2]
G15
PC12
MACB0 - RXD[3]
G14
PC13
MACB0 - RX_ER
G11
PC14
MACB0 - RX_CLK
G10
PC15
MACB0 - RX_DV
B16
PC16
MACB0 - MDC
B15
PC17
MACB0 - MDIO
D10
PC18
MACB0 - SPEED
B10
PC19
LCDC - CC
G9
PC20
LCDC - HSYNC
F9
PC21
LCDC - PCLK
D9
PC22
LCDC - VSYNC
A9
PC23
LCDC - DVAL
MACB1 - CRS
C9
PC24
LCDC - MODE
MACB1 - RX_CLK
B9
PC25
LCDC - PWR
G8
PC26
LCDC - DATA[0]
MACB1 - TX_ER
F8
PC27
LCDC - DATA[1]
MACB1 - TXD[2]
E8
PC28
LCDC - DATA[2]
MACB1 - TXD[3]
D8
PC29
LCDC - DATA[3]
MACB1 - RXD[2]
B8
PC30
LCDC - DATA[4]
MACB1 - RXD[3]
C8
PC31
LCDC - DATA[5]
MACB1 - COL
29
32003MS–AVR32–09/09
AT32AP7000
7.7.4
PIO Controller D Multiplexing
Table 7-12.
7.7.5
PIO Controller D Multiplexing
CTBGA256
I/O Line
Peripheral A
Peripheral B
C2
PD00
LCDC - DATA[6]
C1
PD01
LCDC - DATA[7]
D3
PD02
LCDC - DATA[8]
MACB1 - MDIO
H6
PD03
LCDC - DATA[9]
MACB1 - MDC
H5
PD04
LCDC - DATA[10]
MACB1 - RX_DV
H4
PD05
LCDC - DATA[11]
MACB1 - RX_ER
H1
PD06
LCDC - DATA[12]
MACB1 - RXD[1]
H3
PD07
LCDC - DATA[13]
J7
PD08
LCDC - DATA[14]
J6
PD09
LCDC - DATA[15]
R2
PD10
LCDC - DATA[16]
MACB1 - RXD[0]
P4
PD11
LCDC - DATA[17]
MACB1 - TX_EN
T4
PD12
LCDC - DATA[18]
MACB1 - TX_CLK
R4
PD13
LCDC - DATA[19]
MACB1 - TXD[0]
N5
PD14
LCDC - DATA[20]
MACB1 - TXD[1]
T5
PD15
LCDC - DATA[21]
MACB1 - SPEED
P5
PD16
LCDC - DATA[22]
R5
PD17
LCDC - DATA[23]
PIO Controller E Multiplexing
Table 7-13.
PIO Controller E Multiplexing
CTBGA256
I/O Line
Peripheral A
Peripheral B
C6
PE00
EBI - DATA[16]
LCDC - CC
E6
PE01
EBI - DATA[17]
LCDC - DVAL
A6
PE02
EBI - DATA[18]
LCDC - MODE
D5
PE03
EBI - DATA[19]
LCDC - DATA[0]
B5
PE04
EBI - DATA[20]
LCDC - DATA[1]
E5
PE05
EBI - DATA[21]
LCDC - DATA[2]
C5
PE06
EBI - DATA[22]
LCDC - DATA[3]
A5
PE07
EBI - DATA[23]
LCDC - DATA[4]
D4
PE08
EBI - DATA[24]
LCDC - DATA[8]
B4
PE09
EBI - DATA[25]
LCDC - DATA[9]
C4
PE10
EBI - DATA[26]
LCDC - DATA[10]
A4
PE11
EBI - DATA[27]
LCDC - DATA[11]
30
32003MS–AVR32–09/09
AT32AP7000
Table 7-13.
PIO Controller E Multiplexing
B3
PE12
EBI - DATA[28]
LCDC - DATA[12]
A3
PE13
EBI - DATA[29]
LCDC - DATA[16]
C3
PE14
EBI - DATA[30]
LCDC - DATA[17]
A2
PE15
EBI - DATA[31]
LCDC - DATA[18]
B2
PE16
EBI - ADDR[23]
LCDC - DATA[19]
D1
PE17
EBI - ADDR[24]
LCDC - DATA[20]
D2
PE18
EBI - ADDR[25]
LCDC - DATA[21]
T11
PE19
EBI - CFCE1
M11
PE20
EBI - CFCE2
P11
PE21
EBI - NCS[4]
N11
PE22
EBI - NCS[5]
R11
PE23
EBI - CFRNW
L11
PE24
EBI - NWAIT
T10
PE25
EBI - NCS[2]
31
32003MS–AVR32–09/09
AT32AP7000
7.7.6
IO 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.6.1
HMatrix SFR4 EBI Control Register
Name:
HMATRIX_SFR4
Access Type:
Read/Write
31
–
30
–
29
–
28
–
27
–
26
–
25
–
24
–
23
–
22
–
21
–
20
–
19
–
18
–
17
–
16
–
15
–
14
–
13
–
12
–
11
–
10
–
9
–
8
EBI_DBPUC
7
–
6
–
5
EBI_CS5A
4
EBI_CS4A
3
EBI_CS3A
2
–
1
EBI_CS1A
0
-
• 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.
1 = Chip Select 5 is assigned to the Static Memory Controller and the CompactFlash Logic is
activated.
32
32003MS–AVR32–09/09
AT32AP7000
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.
The pull-up resistors are
1: EBI D[15:0] are not internally pulled up.
Table 7-14.
IO Pins without multiplexing
I/O Line
Function
PX00
EBI - DATA[0]
PX01
EBI - DATA[1]
PX02
EBI - DATA[2]
PX03
EBI - DATA[3]
PX04
EBI - DATA[4]
PX05
EBI - DATA[5]
PX06
EBI - DATA[6]
PX07
EBI - DATA[7]
PX08
EBI - DATA[8]
PX09
EBI - DATA[9]
PX10
EBI - DATA[10]
PX11
EBI - DATA[11]
PX12
EBI - DATA[12]
PX13
EBI - DATA[13]
PX14
EBI - DATA[14]
PX15
EBI - DATA[15]
PX16
EBI - ADDR[0]
PX17
EBI - ADDR[1]
PX18
EBI - ADDR[2]
PX19
EBI - ADDR[3]
PX20
EBI - ADDR[4]
PX21
EBI - ADDR[5]
PX22
EBI - ADDR[6]
PX23
EBI - ADDR[7]
PX24
EBI - ADDR[8]
PX25
EBI - ADDR[9]
PX26
EBI - ADDR[10]
PX27
EBI - ADDR[11]
PX28
EBI - ADDR[12]
PX29
EBI - ADDR[13]
PX30
EBI - ADDR[14]
PX31
EBI - ADDR[15]
33
32003MS–AVR32–09/09
AT32AP7000
Table 7-14.
IO Pins without multiplexing (Continued)
PX32
EBI - ADDR[16]
PX33
EBI - ADDR[17]
PX34
EBI - ADDR[18]
PX35
EBI - ADDR[19]
PX36
EBI - ADDR[20]
PX37
EBI - ADDR[21]
PX38
EBI - ADDR[22]
PX39
EBI - NCS[0]
PX40
EBI - NCS[1]
PX41
EBI - NCS[3]
PX42
EBI - NRD
PX43
EBI - NWE0
PX44
EBI - NWE1
PX45
EBI - NWE3
PX46
EBI - SDCK
PX47
EBI - SDCKE
PX48
EBI - RAS
PX49
EBI - CAS
PX50
EBI - SDWE
PX51
EBI - SDA10
PX52
EBI - NANDOE
PX53
EBI - NANDWE
34
32003MS–AVR32–09/09
AT32AP7000
7.8
7.8.1
Peripheral overview
External Bus Interface
• Optimized for Application Memory Space support
• Integrates Three External Memory Controllers:
– Static Memory Controller
– SDRAM Controller
– ECC Controller
• Additional Logic for NAND Flash/SmartMediaTM and CompactFlashTM Support
– 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/SmartMediaTM Support
– Static Memory Controller on NCS4 - NCS5, Optional CompactFlashTM Support
7.8.2
Static Memory Controller
7.8.3
• 6 Chip Selects Available
• 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
SDRAM Controller
• 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
• Programming Facilities
– 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
35
32003MS–AVR32–09/09
AT32AP7000
• Energy-saving Capabilities
•
7.8.4
– 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
•
•
•
Error Corrected Code Controller
• Hardware Error Corrected Code (ECC) Generation
– Detection and Correction by Software
• Supports NAND Flash and SmartMedia™ Devices with 8- or 16-bit Data Path.
• Supports NAND Flash/SmartMedia with Page Sizes of 528, 1056, 2112 and 4224 Bytes, Specified
by Software
7.8.5
Serial 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.6
Two-wire Interface
• Compatibility with standard two-wire serial memory
• One, two or three bytes for slave address
• Sequential read/write operations
36
32003MS–AVR32–09/09
AT32AP7000
7.8.7
USART
• Programmable Baud Rate Generator
• 5- to 9-bit full-duplex synchronous or asynchronous serial communications
•
•
•
•
7.8.8
– 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
Serial 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
7.8.9
• Receiver and transmitter include a data signal, a clock signal and a frame synchronization signal
AC97 Controller
• Compatible with AC97 Component Specification V2.2
• Capable to Interface with a Single Analog Front end
• Three independent RX Channels and three independent TX Channels
– 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 DMACA
– One RX and one TX channel for data transfers, connected to the DMACA
• 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
Interface (48KHz and below)
37
32003MS–AVR32–09/09
AT32AP7000
7.8.10
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 DMA Controller for background transfer without CPU intervention
7.8.11
Timer Counter
• Three 16-bit Timer Counter Channels
• Wide range of functions including:
– Frequency Measurement
– Event Counting
– Interval Measurement
– Pulse Generation
– Delay Timing
– Pulse Width Modulation
– Up/down Capabilities
• Each channel is user-configurable and contains:
– 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.12
Pulse Width Modulation Controller
• 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
38
32003MS–AVR32–09/09
AT32AP7000
7.8.13
MultiMedia Card Interface
•
•
•
•
•
•
•
2 double-channel MultiMedia Card Interface, allowing concurrent transfers with 2 cards
Compatibility with MultiMedia Card Specification Version 2.2
Compatibility with SD Memory Card Specification Version 1.0
Compatibility with SDIO Specification Version V1.0.
Cards clock rate up to Master Clock divided by 2
Embedded power management to slow down clock rate when not used
Each MCI has two slot, each supporting
– One slot for one MultiMediaCard bus (up to 30 cards) or
– One SD Memory Card
• Support for stream, block and multi-block data read and write
7.8.14
PS/2 Interface
•
•
•
•
•
7.8.15
USB Interface
7.8.16
•
•
•
•
•
•
•
•
LCD Controller
Peripheral Bus slave
PS/2 Host
Receive and transmit capability
Parity generation and error detection
Overrun error detection
Supports Hi (480Mbps) and Full (12Mbps) speed communication
Compatible with the USB 2.0 specification
UTMI Compliant
7 Endpoints
Embedded Dual-port RAM for Endpoints
Suspend/Resume Logic (Command of UTMI)
Up to Three Memory Banks for Endpoints (Not for Control Endpoint)
4 KBytes of DPRAM
•
•
•
•
•
•
•
•
•
•
•
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.
39
32003MS–AVR32–09/09
AT32AP7000
7.8.17
Ethernet MAC
•
•
•
•
•
•
•
•
•
•
•
•
7.8.18
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 in
Image 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
40
32003MS–AVR32–09/09
AT32AP7000
8. Boot Sequence
This chapter summarizes the boot sequence of the AT32AP7000. The behaviour after power-up
is controlled by the Power Manager.
8.1
Starting of clocks
After power-up, the device will be held in a reset state by the Power-On Reset (POR) circuitry
until the voltage has reached the power-on reset rising threshold value (see Electrical Characteristics for details). This ensures that all critical parts of the device are properly reset.
Once the power-on reset is complete, 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.
Note that the power-on reset will release reset at a lower voltage threshold than the minimum
specified operating voltage. If the voltage is not guaranteed to be stable by the time the device
starts executing, an external brown-out reset circuit should be used.
8.2
Fetching 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.
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.
41
32003MS–AVR32–09/09
AT32AP7000
9. Ordering Information
Table 9-1.
Ordering Information
Ordering Code
Package
Package Type
Packing
Temperature
Operating Range
AT32AP7000-CTUR
CTBGA256
Green
Reel
Industrial (-40°C to 85°C)
AT32AP7000-CTUT
CTBGA256
Green
Tray
Industrial (-40°C to 85°C)
42
32003MS–AVR32–09/09
AT32AP7000
10. Errata
10.1
Rev. C
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 write operation with less than 12 bytes is impossible.
MCI data write operation with less than 12 bytes is impossible. The Data Write operation
with a number of bytes less than 12 leaves the internal MCI FIFO in an inconsistent state.
Subsequent reads and writes will not function properly.
Fix/Workaround
Always transfer 12 or more bytes at a time. If less than 12 bytes are transferred, the only
recovery mechanism is to perform a software reset of the MCI.
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.
43
32003MS–AVR32–09/09
AT32AP7000
Fix/Workaround
Use slot A.
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. 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, ..., 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.
13. PWM channel status may be wrong if disabled before a period has elapsed
44
32003MS–AVR32–09/09
AT32AP7000
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
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.
15. SSC can not transmit or receive data
The SSC can not 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 enable the PIO with output driver disabled on the
TK/RK pin.
16. USART - RXBREAK flag is not correctly handled
The FRAME_ERROR is set instead of the RXBREAK when the break character is located
just after the STOP BIT(S) in ASYNCHRONOUS mode.
Fix/Workaround
The transmitting UART must set timeguard greater than 0.
17. USART - Manchester encoding/decoding is not working.
Manchester encoding/decoding is not working.
Fix/Workaround
Do not use manchester encoding.
18. SPI - Disabling SPI has no effect on TDRE flag.
Disabling SPI has no effect on TDRE whereas the write data command is filtered when SPI
is disabled. This means that as soon as the SPI is disabled it becomes impossible to reset
the TDRE flag by writing in the SPI_TDR. So if the SPI is disabled during a PDC transfer, the
PDC will continue to write data in the SPI_TDR (as TDRE keeps High) till its buffer is empty,
and all data written after the disable command is lost.
Fix/Workaround
Disable PDC, 2 NOP (minimum), Disable SPI. When you want to continue the transfer:
Enable SPI, Enable PDC.
19. SPI disable does not work in SLAVE mode.
SPI disable does not work in SLAVE mode.
Fix/Workaround
Read the last received data, then perform a Software Reset.
45
32003MS–AVR32–09/09
AT32AP7000
20. SCC - First Data transmitted after reset is not DATDEF.
In the first frame transmitted, the first transmitted data that follows the frame synchro is 0,
not DATDEF. This happens when:
1. PDC is disabled
2. Reset the SSC
3. Configure the SSC with a transmit START condition different from CONTINUOUS
(START = 0)
4. DATDEF = 1
5. Enable the SSC in transmission.
This trouble only appears after a reset and it is only the first frame is affected.
Fix/Workaround
Use the PDC to fill the THR after the enable of the SSC and before the start of the frame.
21. MCI - False data timeout error DTOE may occur.
If a small block (5 bytes) is read through the READ_SINGLE_BLOCK command (CMD17),
the flag NOTBUSY will be set and a false data timeout error DTOE occurs.
Fix/Workaround
None.
22. SDRAM - Self-refresh mode
If Entry in Self-refresh mode is followed by SDRAM access and auto-refresh event, TRC timing is not checked for AUTO_REFRESH sequence.
Fix/Workaround
Set the value of TRAS field in user interface with TRC+1.
23. SPI - No TX UNDERRUN flag available
There is no TX UNDERRUN flag available, therefore in slave mode there is no way to be
informed of a character lost in transmission.
Fix/Workaround
PDC/PDCA transfers: None.
Manual transfers (no PDC and TX slave only): Read the RHR every time the THR is written.
The OVRS flag of the status register will track any UNDERRUN on the TX side.
24. HMATRIX - Fixed priority arbitration does not work
Fixed priority arbitration does not work.
Fix/Workaround
Use Round-robin arbitration instead.
25. OSC32 is not available for RTC, WDT, TIMERs and USARTs at startup
Right after startup the osc32 clock to internal modules is not valid. The osc32 clock will be
valid for use approximately 128 osc32 cycles after the the first instruction is executed. This
has consequences if you are planning to use the RTC, WDT, going into sleep mode and
USARTs with SCK and TCs with TIMER_CLOCK0.
46
32003MS–AVR32–09/09
AT32AP7000
Fix/Workaround
Before executing any code the user should enable the RTC with the smallest prescaler and
poll that the RTC is counting before doing anything in your program. Another way to ensure
that the osc32 is valid is to use interrupts with TOP=1.
Example:
//reset the counter register
AVR32_RTC.val = 0x0;
//enable the RTC with the smallest prescaler
AVR32_RTC.ctrl = 0x1;
//wait until the value increases
while(AVR32_RTC.val == 0);
26. SPI can generate a false RXREADY signal in SLAVE mode
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 begin and RXREADY will now behave as expected.
27. EBI address lines 23, 24, and 25 are pulled up when booting up
After reset the EBI address lines 23, 24 and 25 are tristated with pullups. Booting from a
flash larger than 8 MB using these lines will fail, as the flash will be accessed with these
address bits set.
Fix/Workaround
Add external pulldown resistors (5 kΩ) on these lines if booting from a flash larger than 8 MB
using these address lines.
28. SSC - Additional delay on TD output
A delay from 2 to 3 system clock cycles is added to TD output when:
TCMR.START = Receive Start,
TCMR.STTDLY = more than ZERO,
RCMR.START = Start on falling edge / Start on Rising edge / Start on any edge
RFMR.FSOS = None (input)
Fix/Workaround
None.
29. SSC - TF output is not correct
TF output is not correct (at least emitted one serial clock cycle later than expected) when:
TFMR.FSOS = Driven Low during data transfer/ Driven High during data transfer
47
32003MS–AVR32–09/09
AT32AP7000
TCMR.START = Receive start
RFMR.FSOS = None (Input)
RCMR.START = any on RF (edge/level)
Fix/Workaround
None.
30. USART - TXD signal is floating in Modem and Hardware Handshaking mode
The TXD signal is floating in Modem and Hardware Handshaking mode, but should be
pulled up.
Fix/Workaround
Enable pullup on this line in the PIO.
31. PWM - Impossible to update a period equal to 0 by using the CUPD register
It is impossible to UPDATE a period equal to 0 by the using of the UPDATE register
(CUPD).
Fix/Workaround
To update a period equal to 0, write directly to the CPRD register.
32. WDT Clear is blocked after WDT Reset
A watchdog timer event will, after reset, block writes to the WDT_CLEAR register, preventing the program to clear the next Watchdog Timer Reset.
Fix/Workaround
If the RTC is not used a write to AVR32_RTC.ctrl.pclr = 1, instead of writing to
AVR32_WDT.clr, will reset the prescaler and thus prevent the watchdog event from happening. This will render the RTC useless, but prevents WDT reset because the RTC and WDT
share the same prescaler. Another sideeffect of this is that the watchdog timeout period will
be half the expected timeout period.
If the RTC is used one can disable the Watchdog Timer (WDT) after a WDT reset has
occured. This will prevent the WDT resetting the system. To make the WDT functional again
a hard reset (power on reset or RESET_N) must be applied. If you still want to use the WDT
a f t e r a W D T r e s e t a s m a l l c o d e c a n b e i n s e r te d a t t h e s ta r tu p c h e c k i n g t h e
AVR32_PM.rcause register for WDT reset and use a GPIO pin to reset the system. This
method requires that one of the GPIO pins are available and connected externally to the
RESET_N pin. After the GPIO pin has pulled down the reset line the GPIO will be reset and
leave the pin tristated with pullup.
33. USART - The DCD Signal is active high from the USART, but should be active low
The DCD signal is active high from the USART, but should be active low.
Fix/Workaround
An inverter should be added on this line on the PCB.
34. MCI Transmit Data Register (TDR) FIFO corruption
If the number of bytes to be transmitted by the MCI is not a multiple of 4, the Transmit Data
Register (TDR) First In First Out data buffer control logic will become corrupted when transmit data is written to the TDR as 32-bit values.
Fix/Workaround
48
32003MS–AVR32–09/09
AT32AP7000
Configure the MCI Mode Register (MR) to accept 8-bit data input by writing a 1 to bit 13
(FBYTE), and transfer each byte of the transmit data to TDR by right aligning the useful
value. This allows the number of bytes transferred into the TDR to match the number set up
in the BCNT field of the MCI Block Register (BLKR).
35. Unreliable branch folding
In certain situations, branch folding does not work as expected.
Fix/Workaround
Write 0 to CPUCR.FE before executing any branch instructions after reset.
36. USB PLL jitter may cause packet loss during USB hi-speed transmission
The USB Hi-speed PLL accuracy is not sufficient for Isochronous USB hi-speed transmission and may cause packet loss. The observed bit-loss is typically < 125 ppm.
Fix/Workaround
Do not use isochronous mode if absolute data accuracy is critical.
10.2
Rev. B
Not sampled.
10.3
Rev. A
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. MMC data write operation with less than 12 bytes is impossible.
49
32003MS–AVR32–09/09
AT32AP7000
MCI data write operation with less than 12 bytes is impossible. The Data Write operation
with a number of bytes less than 12 leaves the internal MCI FIFO in an inconsistent state.
Subsequent reads and writes will not function properly.
Fix/Workaround
Always transfer 12 or more bytes at a time. If less than 12 bytes are transferred, the only
recovery mechanism is to perform a software reset of the MCI.
5. 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.
Fix/Workaround
Use slot A.
6. 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.
7. 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.
8. PSIF Status Register bits return 0
The PARITY, NACK and OVRUN bits in the PSIF Status Register cannot be read. Reading
these bits will always return zero.
Fix/Workaround
None
9. PSIF Transmit does not work as intended
While PSIF receiving works, transmitting using the PSIF does not work.
Fix/Workaround
Do not transmit using the PSIF.
10. 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.
50
32003MS–AVR32–09/09
AT32AP7000
11. 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, ..., period
- Consecutive periods are 0x0001, 0x0002, ..., period
12. 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.
13. 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.
14. 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.
15. Power Manager DIVEN-bit cannot be read
The DIVEN-bit in the Generic Clock Control Register in the Power Manager cannot be read.
Reading the register will give a wrong value for DIVEN. Writing to DIVEN works as intended.
Fix/Workaround
Do not read DIVEN. If needed, the written value must be store elsewhere.
16. Watchdog Timer cannot wake the part from sleep
When the CPU has entered sleep mode, the watchdog timer will not be able to reset the system if a watchdog reset occurs. The problem is valid for all sleep modes.
Fix/Workaround
None.
17. Peripherals connected to wrong clock signal
The frequency of the divided clocks for the SPI and the USART is set by the clock configuration for peripheral bus B (PBB) and not by peripheral bus A.
Fix/Workaround
Use clock settings for PBB for the SPI and USART.
51
32003MS–AVR32–09/09
AT32AP7000
18. JTAG CLAMP instruction does not work as intended
During the CLAMP instruction, the Boundary Scan register should be stable and only the
BYPASS register selected. Instead, the bscan register will capture and shift as if it was
selected, reducing the usefulness of the CLAMP instruction.
Fix/Workaround
None.
19. High current consumption in reset with no clocks enabled
In connection with the datacache RAM access, a higher current consumption than expected
can be observed during reset. The error is non-functional and does not affect reliability of the
device.
Fix/Workaround
Via software, access the datacache RAM every 100 µs. This prevents the increased current
consumption. Example code:
mov
r11, lo(0x24002000)
orh
r11, hi(0x24002000)
ld.w
r11, r11[0]
mov
r10, lo(0x24000000)
orh
r10, hi(0x24000000)
ld.w
r10, r10[0]
//access first RAM
//access second RAM
20. 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.
21. SSC can not transmit or receive data
The SSC can not 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 enable the PIO with output driver disabled on the
TK/RK pin.
22. USART - RXBREAK flag is not correctly handled
The FRAME_ERROR is set instead of the RXBREAK when the break character is located
just after the STOP BIT(S) in ASYNCHRONOUS mode.
Fix/Workaround
The transmitting UART must set timeguard greater than 0.
23. USART - Manchester encoding/decoding is not working.
Manchester encoding/decoding is not working.
Fix/Workaround
Do not use manchester encoding.
52
32003MS–AVR32–09/09
AT32AP7000
24. SPI - Disabling SPI has no effect on TDRE flag.
Disabling SPI has no effect on TDRE whereas the write data command is filtered when SPI
is disabled. This means that as soon as the SPI is disabled it becomes impossible to reset
the TDRE flag by writing in the SPI_TDR. So if the SPI is disabled during a PDC transfer, the
PDC will continue to write data in the SPI_TDR (as TDRE keeps High) till its buffer is empty,
and all data written after the disable command is lost.
Fix/Workaround
Disable PDC, 2 NOP (minimum), Disable SPI. When you want to continue the transfer:
Enable SPI, Enable PDC.
25. SPI disable does not work in SLAVE mode.
SPI disable does not work in SLAVE mode.
Fix/Workaround
Read the last received data, then perform a Software Reset.
26. SCC - First Data transmitted after reset is not DATDEF.
In the first frame transmitted, the first transmitted data that follows the frame synchro is 0,
not DATDEF. This happens when:
1. PDC is disabled
2. Reset the SSC
3. Configure the SSC with a transmit START condition different from CONTINUOUS
(START = 0)
4. DATDEF = 1
5. Enable the SSC in transmission.
This trouble only appears after a reset and it is only the first frame is affected.
Fix/Workaround
Use the PDC to fill the THR after the enable of the SSC and before the start of the frame.
27. MCI - False data timeout error DTOE may occur.
If a small block (5 bytes) is read through the READ_SINGLE_BLOCK command (CMD17),
the flag NOTBUSY will be set and a false data timeout error DTOE occurs.
Fix/Workaround
None.
28. SDRAM - Self-refresh mode
If Entry in Self-refresh mode is followed by SDRAM access and auto-refresh event, TRC timing is not checked for AUTO_REFRESH sequence.
Fix/Workaround
Set the value of TRAS field in user interface with TRC+1.
29. SPI - No TX UNDERRUN flag available
There is no TX UNDERRUN flag available, therefore in slave mode there is no way to be
informed of a character lost in transmission.
Fix/Workaround
53
32003MS–AVR32–09/09
AT32AP7000
PDC/PDCA transfers: None.
Manual transfers (no PDC and TX slave only): Read the RHR every time the THR is written.
The OVRS flag of the status register will track any UNDERRUN on the TX side.
30. HMATRIX - Fixed priority arbitration does not work
Fixed priority arbitration does not work.
Fix/Workaround
Use Round-robin arbitration instead.
31. OSC32 is not available for RTC, WDT, TIMERs and USARTs at startup
Right after startup the osc32 clock to internal modules is not valid. The osc32 clock will be
valid for use approximately 128 osc32 cycles after the the first instruction is executed. This
has consequences if you are planning to use the RTC, WDT, going into sleep mode and
USARTs with SCK and TCs with TIMER_CLOCK0.
Fix/Workaround
Before executing any code the user should enable the RTC with the smallest prescaler and
poll that the RTC is counting before doing anything in your program. Another way to ensure
that the osc32 is valid is to use interrupts with TOP=1.
Example:
//reset the counter register
AVR32_RTC.val = 0x0;
//enable the RTC with the smallest prescaler
AVR32_RTC.ctrl = 0x1;
//wait until the value increases
while(AVR32_RTC.val == 0);
32. SPI can generate a false RXREADY signal in SLAVE mode
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 begin and RXREADY will now behave as expected.
33. EBI address lines 23, 24, and 25 are pulled up when booting up
After reset the EBI address lines 23, 24 and 25 are tristated with pullups. Booting from a
flash larger than 8 MB using these lines will fail, as the flash will be accessed with these
address bits set.
Fix/Workaround
Add external pulldown resistors (5 kΩ) on these lines if booting from a flash larger than 8 MB
using these address lines.
54
32003MS–AVR32–09/09
AT32AP7000
34. SSC - Additional delay on TD output
A delay from 2 to 3 system clock cycles is added to TD output when:
TCMR.START = Receive Start,
TCMR.STTDLY = more than ZERO,
RCMR.START = Start on falling edge / Start on Rising edge / Start on any edge
RFMR.FSOS = None (input)
Fix/Workaround
None.
35. SSC - TF output is not correct
TF output is not correct (at least emitted one serial clock cycle later than expected) when:
TFMR.FSOS = Driven Low during data transfer/ Driven High during data transfer
TCMR.START = Receive start
RFMR.FSOS = None (Input)
RCMR.START = any on RF (edge/level)
Fix/Workaround
None.
36. USART - TXD signal is floating in Modem and Hardware Handshaking mode
The TXD signal is floating in Modem and Hardware Handshaking mode, but should be
pulled up.
Fix/Workaround
Enable pullup on this line in the PIO.
37. PWM - Impossible to update a period equal to 0 by using the CUPD register
It is impossible to UPDATE a period equal to 0 by the using of the UPDATE register
(CUPD).
Fix/Workaround
To update a period equal to 0, write directly to the CPRD register.
38. WDT Clear is blocked after WDT Reset
A watchdog timer event will, after reset, block writes to the WDT_CLEAR register, preventing the program to clear the next Watchdog Timer Reset.
Fix/Workaround
If the RTC is not used a write to AVR32_RTC.ctrl.pclr = 1, instead of writing to
AVR32_WDT.clr, will reset the prescaler and thus prevent the watchdog event from happening. This will render the RTC useless, but prevents WDT reset because the RTC and WDT
share the same prescaler. Another sideeffect of this is that the watchdog timeout period will
be half the expected timeout period.
If the RTC is used one can disable the Watchdog Timer (WDT) after a WDT reset has
occured. This will prevent the WDT resetting the system. To make the WDT functional again
a hard reset (power on reset or RESET_N) must be applied. If you still want to use the WDT
a f t e r a W D T r e s e t a s m a l l c o d e c a n b e i n s e r te d a t t h e s ta r tu p c h e c k i n g t h e
AVR32_PM.rcause register for WDT reset and use a GPIO pin to reset the system. This
method requires that one of the GPIO pins are available and connected externally to the
55
32003MS–AVR32–09/09
AT32AP7000
RESET_N pin. After the GPIO pin has pulled down the reset line the GPIO will be reset and
leave the pin tristated with pullup.
39. USART - The DCD Signal is active high from the USART, but should be active low
The DCD signal is active high from the USART, but should be active low.
Fix/Workaround
An inverter should be added on this line on the PCB.
40. MCI Transmit Data Register (TDR) FIFO corruption
If the number of bytes to be transmitted by the MCI is not a multiple of 4, the Transmit Data
Register (TDR) First In First Out data buffer control logic will become corrupted when transmit data is written to the TDR as 32-bit values.
Fix/Workaround
Configure the MCI Mode Register (MR) to accept 8-bit data input by writing a 1 to bit 13
(FBYTE), and transfer each byte of the transmit data to TDR by right aligning the useful
value. This allows the number of bytes transferred into the TDR to match the number set up
in the BCNT field of the MCI Block Register (BLKR).
41. Unreliable branch folding
In certain situations, branch folding does not work as expected.
Fix/Workaround
Write 0 to CPUCR.FE before executing any branch instructions after reset.
42. USB PLL jitter may cause packet loss during USB hi-speed transmission
The USB Hi-speed PLL accuracy is not sufficient for Isochronous USB hi-speed transmission and may cause packet loss. The observed bit-loss is typically < 125 ppm.
Fix/Workaround
Do not use isochronous mode if absolute data accuracy is critical.
56
32003MS–AVR32–09/09
AT32AP7000
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.
11.1
11.2
11.3
Rev. M 09/09
1.
Updated ”Errata” on page 43.
1.
Updated ”Errata” on page 43.
1.
PIO Controller C Multiplexing table updated in ”Peripherals” on page 75“.
2.
Added section ”USBA” on page 81 in Clock Connections in ”Peripherals” on page 75.
3.
USBA feature list updated in ”Peripherals” on page 75.
4.
Renamed clk_slow to clk_osc32 in Table 9-4 on page 80.
5.
Updated organisation of User Interface in ”HSB Bus Matrix (HMATRIX)” on page 144.
6.
Updated special bus granting mechanism in ”HSB Bus Matrix (HMATRIX)” on page 144.
7
Added product dependencies in ”DMA Controller (DMACA)” on page 174.
8.
Added product dependencies in ”Peripheral DMA Controller (PDC)” on page 237.
9.
Added description of multi-drive in ”Parallel Input/Output Controller (PIO)” on page 253.
10.
Added MDER/MDDR/MDSR to pin logic diagram in ”Parallel Input/Output Controller (PIO)” on
page 253.
11.
SPI pins must be enabled to use local loopback.
12.
Updated description of the OVRES bit in ”Serial Peripheral Interface (SPI)” on page 293.
13.
Updated bit description of TXEMPTY in the ”USART Channel Status Register” on page 435.
14.
Number of chip select lines updatedin figures and tables, changed from 8 to 6 in ”Static
Memory Controller (SMC)” on page 492.
15.
Made the MDR register Read/Write instead of Read in ”SDRAM Controller (SDRAMC)” on
page 534.
16.
Removed the PWSEN and PWSDIS bits from the ”Control Register” on page 588.
17.
Added PDCFBYTE and removed the PWSDIV bits from the ”Control Register” on page 588
18.
Added note about terminating the transfers in sleep modes in product dependencies in
”Ethernet MAC (MACB)” on page 606.
19.
Added note about reading the Status Register clears the interrupt flag in ”Timer/Counter (TC)”
on page 740.
20.
Added debug operation to product dependencies in ”Timer/Counter (TC)” on page 740.
21.
Added debug operation to product dependencies in ”Pulse Width Modulation Controller
(PWM)” on page 777.
Rev. L 09/09
Rev. K 09/07
57
32003MS–AVR32–09/09
AT32AP7000
11.4
11.5
11.6
22.
Consistently used the term LCDC Core Clock through the document when referring to the
generic clock that drives the LCD Core and is used to generate PCLK and the other LCD
synchronization signals.
23.
Updated typos in ”LCD Controller (LCDC)” on page 803.
24.
Rewritten the Register Configuration Guide and renamed it “Register Configuration Example“
in ”LCD Controller (LCDC)” on page 803.
25.
Updated formula for pixel clock in ”LCD Control Register 1” on page 846.
26.
Updated HOZVAL description in ”LCD Frame Configuration Register” on page 851.
27.
Updated ”PLL Characteristics” on page 935.
28.
Updated ”Errata” on page 43.
1.
USB Signals updated in ”Signals Description” on page 4.
2.
The PX0 - PX53 Signals added in ”Signals Description” on page 4.
3.
SDCS signals removed from PIO Controller Multiplexing tables in ”Peripherals” on page 75.
4.
SDCS1 signal removed from figures and tables, and SDCS0 renamed to SDCS in ”External
Bus Interface (EBI)” on page 147.
Rev. J 07/07
5
SmartMedia renamed to NAND Flash in some description to avoid confusion in ”External Bus
Interface (EBI)” on page 147.
6.
Updated the reset state of the SMC Mode register in Table 27-9 on page 523.
7.
Updated ”Mechanical Characteristics” on page 927.
8.
Updated pad parameters in ”DC Characteristics” on page 928.
9
Updated pad parameters in ”Clock Characteristics” on page 931.
10.
Updated ”USB Transceiver Characteristics” on page 934.
11.
Updated ”EBI Timings” on page 938.
1.
Updated ”Features” on page 1.
2.
Updated tables in ”Signals Description” on page 4.
3.
Updated Table 9-2 on page 77, Table 9-9 on page 82, and Table 9-9 on page 82 in the
”Peripherals” on page 75.
4.
Updated module names and abbreviations through the datasheet.
1.
Updated ”Features” on page 1.
2.
Updated ”Part Description” on page 2.
3.
Added VBG pin in ”Signals Description” on page 4.
3.
Changed direction in the EVTI_N signal in ”Signals Description” on page 4.
4.
Updated ”Blockdiagram” on page 4.
5.
Updated Registers in ”Power Manager (PM)” on page 48.
Rev. I 04/07
Rev. H 02/07
58
32003MS–AVR32–09/09
AT32AP7000
11.7
11.8
11.9
6.
“Pulling OSCEN_N low” replaced by “Pulling OSCEN_N high” in ”32 KHz oscillator operation”
on page 98.
7.
Added note in ”32 KHz oscillator operation” on page 98.
8.
Updated register names in ”Real Time Counter (RTC)” on page 119.
9.
Updated register names in ”Watchdog Timer (WDT)” on page 125.
10.
Updated register descriptions in ”HSB Bus Matrix (HMATRIX)” on page 144.
11.
Updated CFRNW to a separate signal in ”External Bus Interface (EBI)” on page 147.
12.
Updated register descriptions in ”DMA Controller (DMACA)” on page 174.
13.
Added registers and updated register descriptions in ”Parallel Input/Output Controller (PIO)” on
page 253.
14.
Updated bit names in ”Serial Peripheral Interface (SPI)” on page 293.
15.
Updated flow charts in ”Two-wire Interface (TWI)” on page 322.
16.
Updated bit name in the PSR register in ”PS/2 Module (PSIF)” on page 340.
17.
Added second instance of ps2 interface in ”PS/2 Module (PSIF)” on page 340.
18.
Updated register descriptions in ”Synchronous Serial Controller (SSC)” on page 352.
19.
Updated register names in ”Static Memory Controller (SMC)” on page 492.
20.
Updated register names in ”Error Corrected Code (ECC) Controller” on page 562.
21.
Updated register descriptions in ”Ethernet MAC (MACB)” on page 606.
22.
Updated register descriptions in ”LCD Controller (LCDC)” on page 803.
23.
Updated register descriptions in ”Image Sensor Interface (ISI)” on page 873.
24.
Removed JTAG specification references in ”Debug and Test” on page 909.
25.
Updated ”Electrical Characteristics” on page 928.
26.
Updated memory locations.
1.
Package text changed from CABGA to CTBGA.
2.
Occurrences of APB and AHB changed to Peripheral Bus (PB) and High Speed Bus (HSB)
respectively.
3.
Updated ”Hi-Speed USB Interface (USBA)” on page 584.
4.
Added ”Errata” on page 43.
1.
Removed 150CGU from ”Ordering Information” on page 97.
1.
Added ”USB Device - High Speed (480 Mbits/s)” on page 665.
Rev. G 10/06
Rev. F 07/06
Rev. E 05/06
59
32003MS–AVR32–09/09
AT32AP7000
11.10 Rev. D 04/06
1.
Some occurences of AP7000 renamed to AT32AP7000.
2.
Updated ”Real Time Counter” on page 117.
3.
Updated ”Audio DAC - (DAC)” on page 480
4.
Updated ”DC Characteristics” on page 89.
5.
Updated ”Ordering Information” on page 97.
1.
Initial revision.
11.11 Rev. C 04/06
60
32003MS–AVR32–09/09
AT32AP7000
Table of Contents
Features ..................................................................................................... 1
1
Part Description ....................................................................................... 2
2
Blockdiagram ........................................................................................... 4
2.1Package and PinoutAVR32AP7000 ..........................................................................8
3
Signals Description ............................................................................... 10
4
Power Considerations ........................................................................... 16
4.1Power Supplies .......................................................................................................16
4.2Power Supply Connections .....................................................................................16
5
I/O Line Considerations ......................................................................... 17
5.1JTAG pins ................................................................................................................17
5.2WAKE_N pin ...........................................................................................................17
5.3RESET_N pin ..........................................................................................................17
5.4EVTI_N pin ..............................................................................................................17
5.5TWI pins ..................................................................................................................17
5.6PIO pins ...................................................................................................................17
6
Memories ................................................................................................ 18
6.1Embedded Memories ..............................................................................................18
6.2Physical Memory Map .............................................................................................18
7
Peripherals ............................................................................................. 20
7.1Peripheral address map ..........................................................................................20
7.2Interrupt Request Signal Map ..................................................................................22
7.3DMACA Handshake Interface Map .........................................................................24
7.4Clock Connections ..................................................................................................25
7.5External Interrupt Pin Mapping ................................................................................26
7.6Nexus OCD AUX port connections .........................................................................26
7.7Peripheral Multiplexing on IO lines ..........................................................................27
7.8Peripheral overview .................................................................................................35
8
Boot Sequence ....................................................................................... 41
8.1Starting of clocks .....................................................................................................41
8.2Fetching of initial instructions ..................................................................................41
9
Ordering Information ............................................................................. 42
i
32003MS–AVR32–09/09
AT32AP7000
10 Errata ....................................................................................................... 43
10.1Rev. C ...................................................................................................................43
10.2Rev. B ....................................................................................................................49
10.3Rev. A ....................................................................................................................49
11 Datasheet Revision History .................................................................. 57
11.1Rev. M 09/09 .........................................................................................................57
11.2Rev. L 09/09 ..........................................................................................................57
11.3Rev. K 09/07 ..........................................................................................................57
11.4Rev. J 07/07 ..........................................................................................................58
11.5Rev. I 04/07 ...........................................................................................................58
11.6Rev. H 02/07 .........................................................................................................58
11.7Rev. G 10/06 .........................................................................................................59
11.8Rev. F 07/06 ..........................................................................................................59
11.9Rev. E 05/06 ..........................................................................................................59
11.10Rev. D 04/06 .......................................................................................................60
11.11Rev. C 04/06 .......................................................................................................60
Table of Contents....................................................................................... i
ii
32003MS–AVR32–09/09
Headquarters
International
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
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
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
Technical Support
[email protected]
Sales Contact
www.atmel.com/contacts
Product Contact
Web Site
www.atmel.com
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 CONDITIONS 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.
© 2009 Atmel Corporation. All rights reserved. Atmel ®, Atmel logo and combinations thereof, AVR®, AVR® logo and others are registered trademarks or trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others.
32003MS–AVR32–09/09
Similar pages