AT32UC3A0512

Features • High Performance, Low Power AVR®32 UC 32-Bit Microcontroller – Compact Single-cycle RISC Instruction Set Including DSP Instruction Set – Read-Modify-Write Instructions and Atomic Bit Manipulation – Performing 1.49 DMIPS / MHz Up to 91 DMIPS Running at 66 MHz from Flash (1 Wait-State) Up to 49 DMIPS Running at 33MHz from Flash (0 Wait-State) – Memory Protection Unit Multi-hierarchy Bus System – High-Performance Data Transfers on Separate Buses for Increased Performance – 15 Peripheral DMA Channels Improves Speed for Peripheral Communication Internal High-Speed Flash – 512K Bytes, 256K Bytes, 128K Bytes Versions – Single Cycle Access up to 33 MHz – Prefetch Buffer Optimizing Instruction Execution at Maximum Speed – 4ms Page Programming Time and 8ms Full-Chip Erase Time – 100,000 Write Cycles, 15-year Data Retention Capability – Flash Security Locks and User Defined Configuration Area Internal High-Speed SRAM, Single-Cycle Access at Full Speed – 64K Bytes (512KB and 256KB Flash), 32K Bytes (128KB Flash) External Memory Interface on AT32UC3A0 Derivatives – SDRAM / SRAM Compatible Memory Bus (16-bit Data and 24-bit Address Buses) Interrupt Controller – Autovectored Low Latency Interrupt Service with Programmable Priority System Functions – Power and Clock Manager Including Internal RC Clock and One 32KHz Oscillator – Two Multipurpose Oscillators and Two Phase-Lock-Loop (PLL) allowing Independant CPU Frequency from USB Frequency – Watchdog Timer, Real-Time Clock Timer Universal Serial Bus (USB) – Device 2.0 Full Speed and On-The-Go (OTG) Low Speed and Full Speed – Flexible End-Point Configuration and Management with Dedicated DMA Channels – On-chip Transceivers Including Pull-Ups Ethernet MAC 10/100 Mbps interface – 802.3 Ethernet Media Access Controller – Supports Media Independent Interface (MII) and Reduced MII (RMII) One Three-Channel 16-bit Timer/Counter (TC) – Three External Clock Inputs, PWM, Capture and Various Counting Capabilities One 7-Channel 16-bit Pulse Width Modulation Controller (PWM) Four Universal Synchronous/Asynchronous Receiver/Transmitters (USART) – Independant Baudrate Generator, Support for SPI, IrDA and ISO7816 interfaces – Support for Hardware Handshaking, RS485 Interfaces and Modem Line Two Master/Slave Serial Peripheral Interfaces (SPI) with Chip Select Signals One Synchronous Serial Protocol Controller – Supports I2S and Generic Frame-Based Protocols One Master/Slave Two-Wire Interface (TWI), 400kbit/s I2C-compatible One 8-channel 10-bit Analog-To-Digital Converter 16-bit Stereo Audio Bitstream – Sample Rate Up to 50 KHz • • AVR®32 32-Bit Microcontroller AT32UC3A0512 AT32UC3A0256 AT32UC3A0128 AT32UC3A1512 AT32UC3A1256 AT32UC3A1128 Preliminary • • • • • • • • • • • • • • 32058H–AVR32–03/09 AT32UC3A • On-Chip Debug System (JTAG interface) – Nexus Class 2+, Runtime Control, Non-Intrusive Data and Program Trace • 100-pin TQFP (69 GPIO pins), 144-pin LQFP (109 GPIO pins) , 144 BGA (109 GPIO pins) • 5V Input Tolerant I/Os • Single 3.3V Power Supply or Dual 1.8V-3.3V Power Supply 2 32058H–AVR32–03/09 AT32UC3A 1. Description The AT32UC3A is a complete System-On-Chip microcontroller based on the AVR32 UC RISC processor running at frequencies up to 66 MHz. AVR32 UC is a high-performance 32-bit RISC microprocessor core, designed for cost-sensitive embedded applications, with particular emphasis on low power consumption, high code density and high performance. The processor implements a Memory Protection Unit (MPU) and a fast and flexible interrupt controller for supporting modern operating systems and real-time operating systems. Higher computation capabilities are achievable using a rich set of DSP instructions. The AT32UC3A incorporates on-chip Flash and SRAM memories for secure and fast access. For applications requiring additional memory, an external memory interface is provided on AT32UC3A0 derivatives. The Peripheral Direct Memory Access controller (PDCA) enables data transfers between peripherals and memories without processor involvement. PDCA drastically reduces processing overhead when transferring continuous and large data streams between modules within the MCU. The PowerManager improves design flexibility and security: the on-chip Brown-Out Detector monitors the power supply, the CPU runs from the on-chip RC oscillator or from one of external oscillator sources, a Real-Time Clock and its associated timer keeps track of the time. The Timer/Counter includes three identical 16-bit timer/counter channels. Each channel can be independently programmed to perform frequency measurement, event counting, interval measurement, pulse generation, delay timing and pulse width modulation. The PWM modules provides seven independent channels with many configuration options including polarity, edge alignment and waveform non overlap control. One PWM channel can trigger ADC conversions for more accurate close loop control implementations. The AT32UC3A also features many communication interfaces for communication intensive applications. In addition to standard serial interfaces like UART, SPI or TWI, other interfaces like flexible Synchronous Serial Controller, USB and Ethernet MAC are available. The Synchronous Serial Controller provides easy access to serial communication protocols and audio standards like I2S. The Full-Speed USB 2.0 Device interface supports several USB Classes at the same time thanks to the rich End-Point configuration. The On-The-GO (OTG) Host interface allows device like a USB Flash disk or a USB printer to be directly connected to the processor. The media-independent interface (MII) and reduced MII (RMII) 10/100 Ethernet MAC module provides on-chip solutions for network-connected devices. AT32UC3A integrates a class 2+ Nexus 2.0 On-Chip Debug (OCD) System, with non-intrusive real-time trace, full-speed read/write memory access in addition to basic runtime control. 3 32058H–AVR32–03/09 AT32UC3A 2. Configuration Summary The table below lists all AT32UC3A memory and package configurations: Ethernet MAC yes yes yes yes yes yes Device AT32UC3A0512 AT32UC3A0256 AT32UC3A0128 AT32UC3A1512 AT32UC3A1256 AT32UC3A1128 Flash 512 Kbytes 256 Kbytes 128 Kbytes 512 Kbytes 256 Kbytes 128 Kbytes SRAM 64 Kbytes 64 Kbytes 32 Kbytes 64 Kbytes 64 Kbytes 32 Kbytes Ext. Bus Interface yes yes yes no no no Package 144 pin LQFP 144 pin BGA 144 pin LQFP 144 pin BGA 144 pin LQFP 144 pin BGA 100 pin TQFP 100 pin TQFP 100 pin TQFP 3. Abbreviations • GCLK: Power Manager Generic Clock • GPIO: General Purpose Input/Output • HSB: High Speed Bus • MPU: Memory Protection Unit • OCD: On Chip Debug • PB: Peripheral Bus • PDCA: Peripheral Direct Memory Access Controller (PDC) version A • USBB: USB On-The-GO Controller version B 4 32058H–AVR32–03/09 AT32UC3A 4. Blockdiagram Figure 4-1. Blockdiagram TC K TDO TD I TM S M C KO M D O[5..0] M SEO[1..0] EVTI_N EVTO_N VBU S D+ DID VBO F NEXUS CLASS 2+ O CD UC CPU M EM O RY PRO TEC TIO N U NIT MEMORY INTERFACE JTAG INTERFACE LOC AL BU S INTERFACE FAST G PIO INSTR INTERFACE PBB DATA INTERFACE 64 KB SRAM FLASH CONTROLLER USB INTERFACE DM A S M M M M M S S 512 KB FLASH S ETHERNET M AC PB GENERAL PURPOSE IOs M DC , TXD [3..0], TX_C LK, TX_EN , TX_ER , SPEED M D IO S C ON FIGU RATIO N HS B S REG ISTER S BUS M EXTERNAL BUS INTERFACE (SDRAM & STATIC MEMORY CONTROLLER) CO L, CR S, R XD[3..0], R X_CLK, R X_DV, RX_ER DM A HIG H SPEED BUS M ATRIX D ATA[15..0] ADD R[23..0] NC S[3..0] N RD NW AIT N W E0 N W E1 N W E3 RAS CAS SD A10 SD CK SDC KE SD CS0 SD W E H SB HSB-PB BRIDG E B HSB-PB BRIDG E A PB PBA PERIPHERAL DM A CO NTRO LLER INTERRUPT CO NTRO LLER EXTIN T[7..0] KPS[7..0] N M I_N EXTERNAL INTERRUPT CO NTRO LLER USART1 GENERAL PURPOSE IOs PA PB PC PX R XD TXD CLK R TS, C TS D SR, DTR, D CD , RI R XD TXD CLK R TS, C TS PDC PA PB PC PX REAL TIM E CO UNTER USART0 USART2 USART3 PDC W ATCHDO G TIM ER 115 kHz RCO SC XIN 32 XO UT32 XIN0 XO U T0 XIN1 XO U T1 SERIAL PERIPHERAL INTERFACE 0/1 SYNCHRO NO US SERIAL CO NTRO LLER SC K M ISO , M O SI NPC S0 NPC S[3..1] TX _C LO C K, TX_FRA ME _SYN C TX_D ATA RX _C LO C K, R X_FRA ME _SYN C R X_D ATA PO W ER M ANAG ER CLO CK G ENERATO R CLO CK CO NTRO LLER SLEEP CO NTRO LLER RESET CO NTRO LLER 32 KHz O SC O SC0 O SC1 PLL0 PLL1 PDC PDC TW O -W IRE INTERFACE PDC SC L SD A PULSE W IDTH M O DULATIO N CO NTRO LLER ANALO G TO DIG ITAL CO NVERTER AUDIO BITSTREAM DAC PDC PW M [6..0] PDC RESET_N G CLK[3..0] AD[7..0] AD VREF PDC A[2..0] B[2..0] CLK[2..0] TIM ER /CO UNTER DATA[1..0] D ATAN [1..0] 5 32058H–AVR32–03/09 AT32UC3A 4.1 4.1.1 Processor and architecture AVR32 UC CPU • 32-bit load/store AVR32A RISC architecture. 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. • 3 stage pipeline allows one instruction per clock cycle for most instructions. – Byte, half-word, word and double word memory access. – Multiple interrupt priority levels. • MPU allows for operating systems with memory protection. – – – – – 4.1.2 Debug and Test system • IEEE1149.1 compliant JTAG and boundary scan • Direct memory access and programming capabilities through JTAG interface • Extensive On-Chip Debug features in compliance with IEEE-ISTO 5001-2003 (Nexus 2.0) Class 2+ • • • • – Low-cost NanoTrace supported. Auxiliary port for high-speed trace information Hardware support for 6 Program and 2 data breakpoints Unlimited number of software breakpoints supported Advanced Program, Data, Ownership, and Watchpoint trace supported 4.1.3 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. • Fifteen channels – – – – – Two for each USART Two for each Serial Synchronous Controller Two for each Serial Peripheral Interface One for each ADC Two for each TWI Interface 4.1.4 Bus system • High Speed Bus (HSB) matrix with 6 Masters and 6 Slaves handled – Handles Requests from the CPU Data Fetch, CPU Instruction Fetch, PDCA, USBB, Ethernet Controller, CPU SAB, and to internal Flash, internal SRAM, Peripheral Bus A, Peripheral Bus B, EBI. – Round-Robin Arbitration (three modes supported: no default master, last accessed default master, fixed default master) – Burst Breaking with Slot Cycle Limit – One Address Decoder Provided per Master 6 32058H–AVR32–03/09 AT32UC3A • Peripheral Bus A able to run on at divided bus speeds compared to the High Speed Bus Figure 4-1 gives an overview of the bus system. All modules connected to the same bus use the same clock, but the clock to each module can be individually shut off by the Power Manager. The figure identifies the number of master and slave interfaces of each module connected to the High Speed Bus, and which DMA controller is connected to which peripheral. 7 32058H–AVR32–03/09 AT32UC3A 5. Signals Description The following table gives details on the signal name classified by peripheral The signals are multiplexed with GPIO pins as described in ”Peripheral Multiplexing on I/O lines” on page 45. Table 5-1. Signal Name Signal Description List Function Power Type Active Level Comments VDDPLL Power supply for PLL Power Input Power Input Power Input Power Input Power Input Power Output Ground Ground Clocks, Oscillators, and PLL’s 1.65V to 1.95 V VDDCORE Core Power Supply 1.65V to 1.95 V VDDIO I/O Power Supply 3.0V to 3.6V VDDANA Analog Power Supply 3.0V to 3.6V VDDIN Voltage Regulator Input Supply 3.0V to 3.6V VDDOUT GNDANA GND Voltage Regulator Output Analog Ground Ground 1.65V to 1.95 V XIN0, XIN1, XIN32 XOUT0, XOUT1, XOUT32 Crystal 0, 1, 32 Input Crystal 0, 1, 32 Output JTAG Analog Analog TCK TDI TDO TMS Test Clock Test Data In Test Data Out Test Mode Select Input Input Output Input Auxiliary Port - AUX MCKO MDO0 - MDO5 Trace Data Output Clock Trace Data Output Output Output 8 32058H–AVR32–03/09 AT32UC3A Table 5-1. Signal Name MSEO0 - MSEO1 EVTI_N EVTO_N Signal Description List Function Trace Frame Control Event In Event Out Type Output Output Output Power Manager - PM Low Low Active Level Comments GCLK0 - GCLK3 RESET_N Generic Clock Pins Reset Pin Output Input Real Time Counter - RTC Low RTC_CLOCK RTC clock Output Watchdog Timer - WDT WDTEXT External Watchdog Pin Output External Interrupt Controller - EIC EXTINT0 - EXTINT7 KPS0 - KPS7 NMI_N External Interrupt Pins Keypad Scan Pins Non-Maskable Interrupt Pin Input Output Input Ethernet MAC - MACB Low COL CRS MDC MDIO RXD0 - RXD3 RX_CLK RX_DV RX_ER SPEED TXD0 - TXD3 TX_CLK TX_EN TX_ER Collision Detect Carrier Sense and Data Valid Management Data Clock Management Data Input/Output Receive Data Receive Clock Receive Data Valid Receive Coding Error Speed Transmit Data Transmit Clock or Reference Clock Transmit Enable Transmit Coding Error Input Input Output I/O Input Input Input Input Output Output Output Output 9 32058H–AVR32–03/09 AT32UC3A Table 5-1. Signal Name Signal Description List Function Type External Bus Interface - HEBI Active Level Comments ADDR0 - ADDR23 CAS DATA0 - DATA15 NCS0 - NCS3 NRD NWAIT NWE0 NWE1 NWE3 RAS SDA10 SDCK SDCKE SDCS0 SDWE Address Bus Column Signal Data Bus Chip Select Read Signal External Wait Signal Write Enable 0 Write Enable 1 Write Enable 3 Row Signal SDRAM Address 10 Line SDRAM Clock SDRAM Clock Enable SDRAM Chip Select SDRAM Write Enable Output Output I/O Output Output Input Output Output Output Output Output Output Output Output Output Low Low Low Low Low Low Low Low Low Low General Purpose Input/Output 2 - GPIOA, GPIOB, GPIOC P0 - P31 P0 - P31 P0 - P5 P0 - P31 Parallel I/O Controller GPIOA Parallel I/O Controller GPIOB Parallel I/O Controller GPIOC Parallel I/O Controller GPIOX I/O I/O I/O I/O Serial Peripheral Interface - SPI0, SPI1 MISO MOSI NPCS0 - NPCS3 SCK Master In Slave Out Master Out Slave In SPI Peripheral Chip Select Clock I/O I/O I/O Output Synchronous Serial Controller - SSC RX_CLOCK SSC Receive Clock I/O Low 10 32058H–AVR32–03/09 AT32UC3A Table 5-1. Signal Name RX_DATA RX_FRAME_SYNC TX_CLOCK TX_DATA TX_FRAME_SYNC Signal Description List Function SSC Receive Data SSC Receive Frame Sync SSC Transmit Clock SSC Transmit Data SSC Transmit Frame Sync Type Input I/O I/O Output I/O Timer/Counter - TIMER Active Level Comments A0 A1 A2 B0 B1 B2 CLK0 CLK1 CLK2 Channel 0 Line A Channel 1 Line A Channel 2 Line A Channel 0 Line B Channel 1 Line B Channel 2 Line B Channel 0 External Clock Input Channel 1 External Clock Input Channel 2 External Clock Input I/O I/O I/O I/O I/O I/O Input Input Input Two-wire Interface - TWI SCL SDA Serial Clock Serial Data I/O I/O Universal Synchronous Asynchronous Receiver Transmitter - USART0, USART1, USART2, USART3 CLK CTS DCD DSR DTR RI RTS RXD TXD Clock Clear To Send Data Carrier Detect Data Set Ready Data Terminal Ready Ring Indicator Request To Send Receive Data Transmit Data Output Input Output I/O Input Only USART1 Only USART1 Only USART1 Only USART1 11 32058H–AVR32–03/09 AT32UC3A Table 5-1. Signal Name Signal Description List Function Type Analog to Digital Converter - ADC Active Level Comments AD0 - AD7 Analog input pins Analog input Analog input 2.6 to 3.6V ADVREF Analog positive reference voltage input Pulse Width Modulator - PWM PWM0 - PWM6 PWM Output Pins Output Universal Serial Bus Device - USB DDM DDP VBUS USBID USB_VBOF USB Device Port Data USB Device Port Data + USB VBUS Monitor and OTG Negociation ID Pin of the USB Bus USB VBUS On/off: bus power control port Analog Analog Analog Input Input output Audio Bitstream DAC (ABDAC) DATA0-DATA1 DATAN0-DATAN1 D/A Data out D/A Data inverted out Outpu Outpu 12 32058H–AVR32–03/09 AT32UC3A 6. Power Considerations 6.1 Power Supplies The AT32UC3A has several types of power supply pins: • • • • • VDDIO: Powers I/O lines. Voltage is 3.3V nominal. VDDANA: Powers the ADC Voltage is 3.3V nominal. VDDIN: Input voltage for the voltage regulator. Voltage is 3.3V nominal. VDDCORE: Powers the core, memories, and peripherals. Voltage is 1.8V nominal. VDDPLL: Powers the PLL. Voltage is 1.8V nominal. The ground pins GND are common to VDDCORE, VDDIO, VDDPLL. The ground pin for VDDANA is GNDANA. Refer to ”Power Consumption” on page 767 for power consumption on the various supply pins. Dual Power Supply Single Power Supply 3.3V VDDANA 3.3V VDDANA VDDIO VDDIO ADVREF ADVREF VDDIN 1.8V Regulator VDDIN 1.8V Regulator VDDOUT VDDOUT VDDCORE 1.8V VDDCORE VDDPLL VDDPLL 13 32058H–AVR32–03/09 AT32UC3A 6.2 6.2.1 Voltage Regulator Single Power Supply The AT32UC3A embeds a voltage regulator that converts from 3.3V to 1.8V. The regulator takes its input voltage from VDDIN, and supplies the output voltage on VDDOUT. VDDOUT should be externally connected to the 1.8V domains. Adequate input supply decoupling is mandatory for VDDIN in order to improve startup stability and reduce source voltage drop. Two input decoupling capacitors must be placed close to the chip. Adequate output supply decoupling is mandatory for VDDOUT to reduce ripple and avoid oscillations. The best way to achieve this is to use two capacitors in parallel between VDDOUT and GND as close to the chip as possible 3.3V CIN2 CIN1 VDDIN 1.8V Regulator VDDOUT 1.8V COUT2 COUT1 Refer to Section 38.3 on page 765 for decoupling capacitors values and regulator characteristics 6.2.2 Dual Power Supply In case of dual power supply, VDDIN and VDDOUT should be connected to ground to prevent from leakage current. VDDIN VDDOUT 14 32058H–AVR32–03/09 AT32UC3A 6.3 Analog-to-Digital Converter (A.D.C) reference. The ADC reference (ADVREF) must be provided from an external source. Two decoupling capacitors must be used to insure proper decoupling. 3.3V C VREF2 ADVREF C VREF1 Refer to Section 38.4 on page 765 for decoupling capacitors values and electrical characteristics. In case ADC is not used, the ADVREF pin should be connected to GND to avoid extra consumption. 15 32058H–AVR32–03/09 AT32UC3A 7. Package and Pinout The device pins are multiplexed with peripheral functions as described in ”Peripheral Multiplexing on I/O lines” on page 45. Figure 7-1. TQFP100 Pinout 75 76 51 50 100 1 25 26 Table 7-1. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 TQFP100 Package Pinout PB20 PB21 PB22 VDDIO GND PB23 PB24 PB25 PB26 PB27 VDDOUT VDDIN GND PB28 PB29 PB30 PB31 RESET_N PA00 PA01 GND VDDCORE 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 PA05 PA06 PA07 PA08 PA09 PA10 N/C PA11 VDDCORE GND PA12 PA13 VDDCORE PA14 PA15 PA16 PA17 PA18 PA19 PA20 VBUS VDDIO 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 PA21 PA22 PA23 PA24 PA25 PA26 PA27 PA28 VDDANA ADVREF GNDANA VDDPLL PC00 PC01 PB00 PB01 VDDIO VDDIO GND PB02 PB03 PB04 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 PB08 PB09 PB10 VDDIO GND PB11 PB12 PA29 PA30 PC02 PC03 PB13 PB14 TMS TCK TDO TDI PC04 PC05 PB15 PB16 VDDCORE 16 32058H–AVR32–03/09 AT32UC3A Table 7-1. 23 24 25 TQFP100 Package Pinout PA02 PA03 PA04 48 49 50 DM DP GND 73 74 75 PB05 PB06 PB07 98 99 100 PB17 PB18 PB19 Figure 7-2. LQFP144 Pinout 108 109 73 72 144 1 36 37 Table 7-2. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 VQFP144 Package Pinout PX00 PX01 PB20 PX02 PB21 PB22 VDDIO GND PB23 PX03 PB24 PX04 PB25 PB26 PB27 VDDOUT VDDIN GND PB28 PB29 PB30 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 GND PX10 PA05 PX11 PA06 PX12 PA07 PX13 PA08 PX14 PA09 PA10 N/C PA11 VDDCORE GND PA12 PA13 VDDCORE PA14 PA15 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 PA21 PA22 PA23 PA24 PA25 PA26 PA27 PA28 VDDANA ADVREF GNDANA VDDPLL PC00 PC01 PX20 PB00 PX21 PB01 PX22 VDDIO VDDIO 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 GND PX30 PB08 PX31 PB09 PX32 PB10 VDDIO GND PX33 PB11 PX34 PB12 PA29 PA30 PC02 PC03 PB13 PB14 TMS TCK 17 32058H–AVR32–03/09 AT32UC3A Table 7-2. 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 VQFP144 Package Pinout PB31 RESET_N PX05 PA00 PX06 PA01 GND VDDCORE PA02 PX07 PA03 PX08 PA04 PX09 VDDIO 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 PA16 PX15 PA17 PX16 PA18 PX17 PA19 PX18 PA20 PX19 VBUS VDDIO DM DP GND 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 GND PX23 PB02 PX24 PB03 PX25 PB04 PX26 PB05 PX27 PB06 PX28 PB07 PX29 VDDIO 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 TDO TDI PC04 PC05 PB15 PX35 PB16 PX36 VDDCORE PB17 PX37 PB18 PX38 PB19 PX39 Figure 7-3. BGA144 Pinout 18 32058H–AVR32–03/09 AT32UC3A Table 7-3. 1 A B C D E F G H J K L M VDDIO PB08 PB09 PB11 PB10 PA30 TMS TDO TDI PC05 PB21 PB22 BGA144 Package Pinout A1..M8 2 PB07 GND PX33 PB13 VDDIO PB14 PC03 VDDCORE PB17 PC04 GND PB23 3 PB05 PB06 PA29 PB12 PX32 PX34 PX36 PX38 PB15 PB19 PB18 PB25 4 PB02 PB04 PC02 PX30 PX31 PB16 PX35 PX39 PX00 PB20 PB24 PB26 5 PB03 VDDIO PX28 PX29 VDDIO TCK PX37 VDDIO PX01 PX02 VDDOUT PX03 6 PB01 PB00 PX26 PX25 PX27 GND GND PA01 PA00 PB29 PX04 PB27 7 PC00 PC01 PX22 PX24 PX23 GND GND PA10 PA03 PB30 PB31 PB28 8 PA28 VDDPLL PX21 PX20 VDDANA PX16 PA16 VDDCORE PA04 PA02 VDDIN RESET_N Table 7-4. 9 A B C D E F G H J K L M Note: PA26 PA27 ADVREF PA18 PX18 PA17 PA13 PX11 PX14 PX08 PX06 PX05 BGA144 Package Pinout A9..M12 10 PA25 PA21 GNDANA PA20 PX17 PX15 PA12 PA08 PA07 GND PX10 PX07 11 PA24 GND PX19 DP VDDIO PA15 PA11 VDDCORE PX13 PA05 GND PX09 12 PA23 PA22 PA19 DM VBUS PA14 NC VDDCORE PA09 PX12 PA06 VDDIO NC is not connected. 19 32058H–AVR32–03/09 AT32UC3A 8. I/O Line Considerations 8.1 JTAG pins TMS, TDI and TCK have pull-up resistors. TDO is an output, driven at up to VDDIO, and has no pull-up resistor. 8.2 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. 8.3 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. 8.4 GPIO 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 GPIO Controllers. After reset, I/O lines default as inputs with pull-up resistors disabled, except when indicated otherwise in the column “Reset State” of the GPIO Controller multiplexing tables. 20 32058H–AVR32–03/09 AT32UC3A 9. Processor and Architecture This chapter gives an overview of the AVR32UC CPU. AVR32UC is an implementation of the AVR32 architecture. A summary of the programming model, instruction set and MPU is presented. For further details, see the AVR32 Architecture Manual and the AVR32UC Technical Reference Manual. 9.1 AVR32 Architecture AVR32 is a new, high-performance 32-bit RISC microprocessor architecture, designed for costsensitive embedded applications, with particular emphasis on low power consumption and high code density. In addition, the instruction set architecture has been tuned to allow a variety of microarchitectures, enabling the AVR32 to be implemented as low-, mid- or high-performance processors. AVR32 extends the AVR family into the world of 32- and 64-bit applications. Through a quantitative approach, a large set of industry recognized benchmarks has been compiled and analyzed to achieve the best code density in its class. In addition to lowering the memory requirements, a compact code size also contributes to the core’s low power characteristics. The processor supports byte and half-word data types without penalty in code size and performance. Memory load and store operations are provided for byte, half-word, word and double word data with automatic sign- or zero extension of half-word and byte data. The C-compiler is closely linked to the architecture and is able to exploit code optimization features, both for size and speed. In order to reduce code size to a minimum, some instructions have multiple addressing modes. As an example, instructions with immediates often have a compact format with a smaller immediate, and an extended format with a larger immediate. In this way, the compiler is able to use the format giving the smallest code size. Another feature of the instruction set is that frequently used instructions, like add, have a compact format with two operands as well as an extended format with three operands. The larger format increases performance, allowing an addition and a data move in the same instruction in a single cycle. Load and store instructions have several different formats in order to reduce code size and speed up execution. The register file is organized as sixteen 32-bit registers and includes the Program Counter, the Link Register, and the Stack Pointer. In addition, register R12 is designed to hold return values from function calls and is used implicitly by some instructions. 9.2 The AVR32UC CPU The AVR32 UC CPU targets low- and medium-performance applications, and provides an advanced OCD system, no caches, and a Memory Protection Unit (MPU). Java acceleration hardware is not implemented. AVR32 UC provides three memory interfaces, one High Speed Bus master for instruction fetch, one High Speed Bus master for data access, and one High Speed Bus slave interface allowing other bus masters to access data RAMs internal to the CPU. Keeping data RAMs internal to the CPU allows fast access to the RAMs, reduces latency and guarantees deterministic timing. Also, power consumption is reduced by not needing a full High Speed Bus access for memory accesses. A dedicated data RAM interface is provided for communicating with the internal data RAMs. 21 32058H–AVR32–03/09 AT32UC3A A local bus interface is provided for connecting the CPU to device-specific high-speed systems, such as floating-point units and fast GPIO ports. This local bus has to be enabled by writing the LOCEN bit in the CPUCR system register. The local bus is able to transfer data between the CPU and the local bus slave in a single clock cycle. The local bus has a dedicated memory range allocated to it, and data transfers are performed using regular load and store instructions. Details on which devices that are mapped into the local bus space is given in the device-specific “Peripherals” chapter of this data sheet. Figure 9-1 on page 22 displays the contents of AVR32UC. Figure 9-1. Interrupt controller interface Overview of the AVR32UC CPU Reset interface OCD interface OCD system Power/ Reset control AVR32UC CPU pipeline MPU Instruction memory controller High Speed Bus master High Speed Bus Data memory controller High Speed Bus slave High Speed Bus High Speed Bus master High Speed Bus 9.2.1 Pipeline Overview AVR32 UC is a pipelined processor with three pipeline stages. There are three pipeline stages, Instruction Fetch (IF), Instruction Decode (ID) and Instruction Execute (EX). The EX stage is split into three parallel subsections, one arithmetic/logic (ALU) section, one multiply (MUL) section and one load/store (LS) section. Instructions are issued and complete in order. Certain operations require several clock cycles to complete, and in this case, the instruction resides in the ID and EX stages for the required number of clock cycles. Since there is only three pipeline stages, no internal data forwarding is required, and no data dependencies can arise in the pipeline. Figure 9-2 on page 23 shows an overview of the AVR32 UC pipeline stages. CPU Local Bus Data RAM interface CPU Local Bus master 22 32058H–AVR32–03/09 AT32UC3A Figure 9-2. The AVR32UC Pipeline MUL Multiply unit IF ID Regf ile Read A LU Regf ile w rite A LU unit Pref etch unit Decode unit Load-store unit LS 9.2.2 AVR32A Microarchitecture Compliance AVR32UC implements an AVR32A microarchitecture. The AVR32A microarchitecture is targeted at cost-sensitive, lower-end applications like smaller microcontrollers. This microarchitecture does not provide dedicated hardware registers for shadowing of register file registers in interrupt contexts. Additionally, it does not provide hardware registers for the return address registers and return status registers. Instead, all this information is stored on the system stack. This saves chip area at the expense of slower interrupt handling. Upon interrupt initiation, registers R8-R12 are automatically pushed to the system stack. These registers are pushed regardless of the priority level of the pending interrupt. The return address and status register are also automatically pushed to stack. The interrupt handler can therefore use R8-R12 freely. Upon interrupt completion, the old R8-R12 registers and status register are restored, and execution continues at the return address stored popped from stack. The stack is also used to store the status register and return address for exceptions and scall. Executing the rete or rets instruction at the completion of an exception or system call will pop this status register and continue execution at the popped return address. 9.2.3 Java Support AVR32UC does not provide Java hardware acceleration. 9.2.4 Memory protection The MPU allows the user to check all memory accesses for privilege violations. If an access is attempted to an illegal memory address, the access is aborted and an exception is taken. The MPU in AVR32UC is specified in the AVR32UC Technical Reference manual. Unaligned reference handling AVR32UC does not support unaligned accesses, except for doubleword accesses. AVR32UC is able to perform word-aligned st.d and ld.d. Any other unaligned memory access will cause an address exception. Doubleword-sized accesses with word-aligned pointers will automatically be performed as two word-sized accesses. 9.2.5 23 32058H–AVR32–03/09 AT32UC3A The following table shows the instructions with support for unaligned addresses. All other instructions require aligned addresses. Table 9-1. Instruction ld.d st.d Instructions with unaligned reference support Supported alignment Word Word 9.2.6 Unimplemented instructions The following instructions are unimplemented in AVR32UC, and will cause an Unimplemented Instruction Exception if executed: • All SIMD instructions • All coprocessor instructions • retj, incjosp, popjc, pushjc • tlbr, tlbs, tlbw • cache 9.2.7 CPU and Architecture revision Two major revisions of the AVR32UC CPU currently exist. The device described in this datasheet uses CPU revision 2. The Architecture Revision field in the CONFIG0 system register identifies which architecture revision is implemented in a specific device. AVR32UC CPU revision 2 is fully backward-compatible with revision 1, ie. code compiled for revision 1 is binary-compatible with revision 2 CPUs. 24 32058H–AVR32–03/09 AT32UC3A 9.3 9.3.1 Programming Model Register file configuration The AVR32UC register file is shown below. Figure 9-3. Application Bit 31 Bit 0 The AVR32UC Register File Supe rv isor Bit 31 Bit 0 INT0 Bit 31 Bit 0 INT1 Bit 31 Bit 0 INT2 Bit 31 Bit 0 INT3 Bit 31 Bit 0 Exce ption Bit 31 Bit 0 NMI Bit 31 Bit 0 PC LR SP_APP R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR PC LR SP_SYS R12 R11 R10 R9 R8 INT0PC R7 INT1PC R6 FINTPC R5 SM PC R4 R3 R2 R1 R0 SR 9.3.2 Status register configuration The Status Register (SR) is split into two halfwords, one upper and one lower, see Figure 9-4 on page 25 and Figure 9-5 on page 26. The lower word contains the C, Z, N, V and Q condition code flags and the R, T and L bits, while the upper halfword contains information about the mode and state the processor executes in. Refer to the AVR32 Architecture Manual for details. Figure 9-4. Bit 31 The Status Register High Halfword Bit 16 - LC 1 0 - - DM D - M2 M1 M0 E M I3M I2M FE I1M I0M GM Bit name Initial value Global Interrupt Mask Interrupt Level 0 Mask Interrupt Level 1 Mask Interrupt Level 2 Mask Interrupt Level 3 Mask Exception Mask Mode Bit 0 Mode Bit 1 Mode Bit 2 Reserved Debug State Debug State Mask Reserved 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 25 32058H–AVR32–03/09 AT32UC3A Figure 9-5. Bit 15 The Status Register Low Halfword Bit 0 R 0 T 0 0 0 0 0 0 0 0 0 L 0 Q 0 V 0 N 0 Z 0 C 0 Bit name Initial value Carry Zero Sign Overflow Saturation Lock Reserved Scratch Register Remap Enable 9.3.3 9.3.3.1 Processor States Normal RISC State The AVR32 processor supports several different execution contexts as shown in Table 9-2 on page 26. Table 9-2. Priority 1 2 3 4 5 6 N/A N/A Overview of execution modes, their priorities and privilege levels. Mode Non Maskable Interrupt Exception Interrupt 3 Interrupt 2 Interrupt 1 Interrupt 0 Supervisor Application Security Privileged Privileged Privileged Privileged Privileged Privileged Privileged Unprivileged Description Non Maskable high priority interrupt mode Execute exceptions General purpose interrupt mode General purpose interrupt mode General purpose interrupt mode General purpose interrupt mode Runs supervisor calls Normal program execution mode Mode changes can be made under software control, or can be caused by external interrupts or exception processing. A mode can be interrupted by a higher priority mode, but never by one with lower priority. Nested exceptions can be supported with a minimal software overhead. When running an operating system on the AVR32, user processes will typically execute in the application mode. The programs executed in this mode are restricted from executing certain instructions. Furthermore, most system registers together with the upper halfword of the status register cannot be accessed. Protected memory areas are also not available. All other operating modes are privileged and are collectively called System Modes. They have full access to all privileged and unprivileged resources. After a reset, the processor will be in supervisor mode. 9.3.3.2 Debug State The AVR32 can be set in a debug state, which allows implementation of software monitor routines that can read out and alter system information for use during application development. This implies that all system and application registers, including the status registers and program counters, are accessible in debug state. The privileged instructions are also available. 26 32058H–AVR32–03/09 AT32UC3A All interrupt levels are by default disabled when debug state is entered, but they can individually be switched on by the monitor routine by clearing the respective mask bit in the status register. Debug state can be entered as described in the AVR32UC Technical Reference Manual. Debug state is exited by the retd instruction. 9.3.4 System registers The system registers are placed outside of the virtual memory space, and are only accessible using the privileged mfsr and mtsr instructions. The table below lists the system registers specified in the AVR32 architecture, some of which are unused in AVR32UC. The programmer is responsible for maintaining correct sequencing of any instructions following a mtsr instruction. For detail on the system registers, refer to the AVR32UC Technical Reference Manual. Table 9-3. Reg # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 System Registers Address 0 4 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96 100 Name SR EVBA ACBA CPUCR ECR RSR_SUP RSR_INT0 RSR_INT1 RSR_INT2 RSR_INT3 RSR_EX RSR_NMI RSR_DBG RAR_SUP RAR_INT0 RAR_INT1 RAR_INT2 RAR_INT3 RAR_EX RAR_NMI RAR_DBG JECR JOSP JAVA_LV0 JAVA_LV1 JAVA_LV2 Function Status Register Exception Vector Base Address Application Call Base Address CPU Control Register Exception Cause Register Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Return Status Register for Debug Mode Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Return Address Register for Debug Mode Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC 27 32058H–AVR32–03/09 AT32UC3A Table 9-3. Reg # 26 27 28 29 30 31 32 33-63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 System Registers (Continued) Address 104 108 112 116 120 124 128 132-252 256 260 264 268 272 276 280 284 288 292 296 300 304 308 312 316 320 324 328 332 336 340 344 348 352 356 360 364 Name JAVA_LV3 JAVA_LV4 JAVA_LV5 JAVA_LV6 JAVA_LV7 JTBA JBCR Reserved CONFIG0 CONFIG1 COUNT COMPARE TLBEHI TLBELO PTBR TLBEAR MMUCR TLBARLO TLBARHI PCCNT PCNT0 PCNT1 PCCR BEAR MPUAR0 MPUAR1 MPUAR2 MPUAR3 MPUAR4 MPUAR5 MPUAR6 MPUAR7 MPUPSR0 MPUPSR1 MPUPSR2 MPUPSR3 Function Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Reserved for future use Configuration register 0 Configuration register 1 Cycle Counter register Compare register Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Unused in AVR32UC Bus Error Address Register MPU Address Register region 0 MPU Address Register region 1 MPU Address Register region 2 MPU Address Register region 3 MPU Address Register region 4 MPU Address Register region 5 MPU Address Register region 6 MPU Address Register region 7 MPU Privilege Select Register region 0 MPU Privilege Select Register region 1 MPU Privilege Select Register region 2 MPU Privilege Select Register region 3 28 32058H–AVR32–03/09 AT32UC3A Table 9-3. Reg # 92 93 94 95 96 97 98 99 100 101 102 103-191 192-255 System Registers (Continued) Address 368 372 376 380 384 388 392 396 400 404 408 412-764 768-1020 Name MPUPSR4 MPUPSR5 MPUPSR6 MPUPSR7 MPUCRA MPUCRB MPUBRA MPUBRB MPUAPRA MPUAPRB MPUCR Reserved IMPL Function MPU Privilege Select Register region 4 MPU Privilege Select Register region 5 MPU Privilege Select Register region 6 MPU Privilege Select Register region 7 Unused in this version of AVR32UC Unused in this version of AVR32UC Unused in this version of AVR32UC Unused in this version of AVR32UC MPU Access Permission Register A MPU Access Permission Register B MPU Control Register Reserved for future use IMPLEMENTATION DEFINED 9.4 Exceptions and Interrupts AVR32UC incorporates a powerful exception handling scheme. The different exception sources, like Illegal Op-code and external interrupt requests, have different priority levels, ensuring a welldefined behavior when multiple exceptions are received simultaneously. Additionally, pending exceptions of a higher priority class may preempt handling of ongoing exceptions of a lower priority class. When an event occurs, the execution of the instruction stream is halted, and execution control is passed to an event handler at an address specified in Table 9-4 on page 32. Most of the handlers are placed sequentially in the code space starting at the address specified by EVBA, with four bytes between each handler. This gives ample space for a jump instruction to be placed there, jumping to the event routine itself. A few critical handlers have larger spacing between them, allowing the entire event routine to be placed directly at the address specified by the EVBA-relative offset generated by hardware. All external interrupt sources have autovectored interrupt service routine (ISR) addresses. This allows the interrupt controller to directly specify the ISR address as an address relative to EVBA. The autovector offset has 14 address bits, giving an offset of maximum 16384 bytes. The target address of the event handler is calculated as (EVBA | event_handler_offset), not (EVBA + event_handler_offset), so EVBA and exception code segments must be set up appropriately. The same mechanisms are used to service all different types of events, including external interrupt requests, yielding a uniform event handling scheme. An interrupt controller does the priority handling of the external interrupts and provides the autovector offset to the CPU. 9.4.1 System stack issues Event handling in AVR32 UC uses the system stack pointed to by the system stack pointer, SP_SYS, for pushing and popping R8-R12, LR, status register and return address. Since event code may be timing-critical, SP_SYS should point to memory addresses in the IRAM section, since the timing of accesses to this memory section is both fast and deterministic. 29 32058H–AVR32–03/09 AT32UC3A The user must also make sure that the system stack is large enough so that any event is able to push the required registers to stack. If the system stack is full, and an event occurs, the system will enter an UNDEFINED state. 9.4.2 Exceptions and interrupt requests When an event other than scall or debug request is received by the core, the following actions are performed atomically: 1. The pending event will not be accepted if it is masked. The I3M, I2M, I1M, I0M, EM and GM bits in the Status Register are used to mask different events. Not all events can be masked. A few critical events (NMI, Unrecoverable Exception, TLB Multiple Hit and Bus Error) can not be masked. When an event is accepted, hardware automatically sets the mask bits corresponding to all sources with equal or lower priority. This inhibits acceptance of other events of the same or lower priority, except for the critical events listed above. Software may choose to clear some or all of these bits after saving the necessary state if other priority schemes are desired. It is the event source’s responsability to ensure that their events are left pending until accepted by the CPU. 2. When a request is accepted, the Status Register and Program Counter of the current context is stored to the system stack. If the event is an INT0, INT1, INT2 or INT3, registers R8-R12 and LR are also automatically stored to stack. Storing the Status Register ensures that the core is returned to the previous execution mode when the current event handling is completed. When exceptions occur, both the EM and GM bits are set, and the application may manually enable nested exceptions if desired by clearing the appropriate bit. Each exception handler has a dedicated handler address, and this address uniquely identifies the exception source. 3. The Mode bits are set to reflect the priority of the accepted event, and the correct register file bank is selected. The address of the event handler, as shown in Table 9-4, is loaded into the Program Counter. The execution of the event handler routine then continues from the effective address calculated. The rete instruction signals the end of the event. When encountered, the Return Status Register and Return Address Register are popped from the system stack and restored to the Status Register and Program Counter. If the r ete i nstruction returns from INT0, INT1, INT2 or INT3, registers R8-R12 and LR are also popped from the system stack. The restored Status Register contains information allowing the core to resume operation in the previous execution mode. This concludes the event handling. 9.4.3 Supervisor calls The AVR32 instruction set provides a supervisor mode call instruction. The scall instruction is designed so that privileged routines can be called from any context. This facilitates sharing of code between different execution modes. The scall mechanism is designed so that a minimal execution cycle overhead is experienced when performing supervisor routine calls from timecritical event handlers. The scall instruction behaves differently depending on which mode it is called from. The behaviour is detailed in the instruction set reference. In order to allow the scall routine to return to the correct context, a return from supervisor call instruction, rets, is implemented. In the AVR32UC CPU, scall and rets uses the system stack to store the return address and the status register. 9.4.4 Debug requests The AVR32 architecture defines a dedicated debug mode. When a debug request is received by the core, Debug mode is entered. Entry into Debug mode can be masked by the DM bit in the 30 32058H–AVR32–03/09 AT32UC3A status register. Upon entry into Debug mode, hardware sets the SR[D] bit and jumps to the Debug Exception handler. By default, debug mode executes in the exception context, but with dedicated Return Address Register and Return Status Register. These dedicated registers remove the need for storing this data to the system stack, thereby improving debuggability. The mode bits in the status register can freely be manipulated in Debug mode, to observe registers in all contexts, while retaining full privileges. Debug mode is exited by executing the retd instruction. This returns to the previous context. 9.4.5 Entry points for events Several different event handler entry points exists. In AVR32 UC, the reset address is 0x8000_0000. This places the reset address in the boot flash memory area. TLB miss exceptions and scall have a dedicated space relative to EVBA where their event handler can be placed. This speeds up execution by removing the need for a jump instruction placed at the program address jumped to by the event hardware. All other exceptions have a dedicated event routine entry point located relative to EVBA. The handler routine address identifies the exception source directly. AVR32UC uses the ITLB and DTLB protection exceptions to signal a MPU protection violation. ITLB and DTLB miss exceptions are used to signal that an access address did not map to any of the entries in the MPU. TLB multiple hit exception indicates that an access address did map to multiple TLB entries, signalling an error. All external interrupt requests have entry points located at an offset relative to EVBA. This autovector offset is specified by an external Interrupt Controller. The programmer must make sure that none of the autovector offsets interfere with the placement of other code. The autovector offset has 14 address bits, giving an offset of maximum 16384 bytes. Special considerations should be made when loading EVBA with a pointer. Due to security considerations, the event handlers should be located in non-writeable flash memory, or optionally in a privileged memory protection region if an MPU is present. If several events occur on the same instruction, they are handled in a prioritized way. The priority ordering is presented in Table 9-4. If events occur on several instructions at different locations in the pipeline, the events on the oldest instruction are always handled before any events on any younger instruction, even if the younger instruction has events of higher priority than the oldest instruction. An instruction B is younger than an instruction A if it was sent down the pipeline later than A. The addresses and priority of simultaneous events are shown in Table 9-4. Some of the exceptions are unused in AVR32 UC since it has no MMU, coprocessor interface or floating-point unit. 31 32058H–AVR32–03/09 AT32UC3A Table 9-4. Priority 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Priority and handler addresses for events Handler Address 0x8000_0000 Provided by OCD system EVBA+0x00 EVBA+0x04 EVBA+0x08 EVBA+0x0C EVBA+0x10 Autovectored Autovectored Autovectored Autovectored EVBA+0x14 EVBA+0x50 EVBA+0x18 EVBA+0x1C EVBA+0x20 EVBA+0x24 EVBA+0x28 EVBA+0x2C EVBA+0x30 EVBA+0x100 EVBA+0x34 EVBA+0x38 EVBA+0x60 EVBA+0x70 EVBA+0x3C EVBA+0x40 EVBA+0x44 Name Reset OCD Stop CPU Unrecoverable exception TLB multiple hit Bus error data fetch Bus error instruction fetch NMI Interrupt 3 request Interrupt 2 request Interrupt 1 request Interrupt 0 request Instruction Address ITLB Miss ITLB Protection Breakpoint Illegal Opcode Unimplemented instruction Privilege violation Floating-point Coprocessor absent Supervisor call Data Address (Read) Data Address (Write) DTLB Miss (Read) DTLB Miss (Write) DTLB Protection (Read) DTLB Protection (Write) DTLB Modified Event source External input OCD system Internal MPU Data bus Data bus External input External input External input External input External input CPU MPU MPU OCD system Instruction Instruction Instruction UNUSED UNUSED Instruction CPU CPU MPU MPU MPU MPU UNUSED PC of offending instruction PC of offending instruction PC(Supervisor Call) +2 PC of offending instruction PC of offending instruction PC of offending instruction First non-completed instruction PC of offending instruction PC of offending instruction PC of offending instruction First non-completed instruction First non-completed instruction First non-completed instruction First non-completed instruction First non-completed instruction First non-completed instruction First non-completed instruction PC of offending instruction Stored Return Address Undefined First non-completed instruction PC of offending instruction 32 32058H–AVR32–03/09 AT32UC3A 10. Memories 10.1 Embedded Memories • Internal High-Speed Flash – 512 KBytes (AT32UC3A0512, AT32UC3A1512) – 256 KBytes (AT32UC3A0256, AT32UC3A1256) – 128 KBytes (AT32UC3A1128, AT32UC3A2128) - 0 Wait State Access at up to 33 MHz in Worst Case Conditions - 1 Wait State Access at up to 66 MHz in Worst Case Conditions - Pipelined Flash Architecture, allowing burst reads from sequential Flash locations, hiding penalty of 1 wait state access - Pipelined Flash Architecture typically reduces the cycle penalty of 1 wait state operation to only 15% compared to 0 wait state operation - 100 000 Write Cycles, 15-year Data Retention Capability - 4 ms Page Programming Time, 8 ms Chip Erase Time - Sector Lock Capabilities, Bootloader Protection, Security Bit - 32 Fuses, Erased During Chip Erase - User Page For Data To Be Preserved During Chip Erase • Internal High-Speed SRAM, Single-cycle access at full speed – 64 KBytes (AT32UC3A0512, AT32UC3A0256, AT32UC3A1512, AT32UC3A1256) – 32KBytes (AT32UC3A1128) 10.2 Physical Memory Map The system bus is implemented as a bus matrix. All system bus addresses are fixed, and they are never remapped in any way, not even in boot. Note that AVR32 UC CPU uses unsegmented translation, as described in the AVR32 Architecture Manual. The 32-bit physical address space is mapped as follows: Table 10-1. Device AT32UC3A Physical Memory Map Start Address 0x0000_0000 0x8000_0000 0xC000_0000 0xC800_0000 0xCC00_0000 0xD000_0000 0xE000_0000 0xFFFE_0000 0xFFFF_0000 Size AT32UC3A0512 AT32UC3A1512 AT32UC3A0256 AT32UC3A1256 AT32UC3A0128 AT32UC3A1128 Embedded SRAM Embedded Flash EBI SRAM CS0 EBI SRAM CS2 EBI SRAM CS3 EBI SRAM CS1 /SDRAM CS0 USB Configuration HSB-PB Bridge A HSB-PB Bridge B 64 Kbyte 512 Kbyte 16 Mbyte 16 Mbyte 16 Mbyte 128 Mbyte 64 Kbyte 64 Kbyte 64 Kbyte 64 Kbyte 512 Kbyte 64 Kbyte 64 Kbyte 64 Kbyte 64 Kbyte 256 Kbyte 16 Mbyte 16 Mbyte 16 Mbyte 128 Mbyte 64 Kbyte 64 Kbyte 64 kByte 64 Kbyte 256 Kbyte 64 Kbyte 64 Kbyte 64 kByte 32 Kbyte 128 Kbyte 16 Mbyte 16 Mbyte 16 Mbyte 128 Mbyte 64 Kbyte 64 Kbyte 64 Kbyte 32 Kbyte 128 Kbyte 64 Kbyte 64 Kbyte 64 Kbyte 33 32058H–AVR32–03/09 AT32UC3A Table 10-2. Flash Memory Parameters Flash Size (FLASH_PW) 512 Kbytes 512 Kbytes 256 Kbytes 256 Kbytes 128 Kbytes 128 Kbytes Number of pages (FLASH_P) 1024 1024 512 512 256 256 Page size (FLASH_W) 128 words 128 words 128 words 128 words 128 words 128 words General Purpose Fuse bits (FLASH_F) 32 fuses 32 fuses 32 fuses 32 fuses 32 fuses 32 fuses Part Number AT32UC3A0512 AT32UC3A1512 AT32UC3A0256 AT32UC3A1256 AT32UC3A1128 AT32UC3A0128 10.3 Bus Matrix Connections Accesses to unused areas returns an error result to the master requesting such an access. The bus matrix has the several masters and slaves. Each master has its own bus and its own decoder, thus allowing a different memory mapping per master. The master number in the table below can be used to index the HMATRIX control registers. For example, MCFG0 is associated with the CPU Data master interface. Table 10-3. Master 0 Master 1 Master 2 Master 3 Master 4 Master 5 High Speed Bus masters CPU Data CPU Instruction CPU SAB PDCA MACB DMA USBB DMA Each slave has its own arbiter, thus allowing a different arbitration per slave. The slave number in the table below can be used to index the HMATRIX control registers. For example, SCFG3 is associated with the Internal SRAM Slave Interface. Table 10-4. Slave 0 Slave 1 Slave 2 Slave 3 Slave 4 Slave 5 High Speed Bus slaves Internal Flash HSB-PB Bridge 0 HSB-PB Bridge 1 Internal SRAM USBB DPRAM EBI 34 32058H–AVR32–03/09 AT32UC3A Figure 10-1. HMatrix Master / Slave Connections HMATRIX SLAVES Internal SRAM Slave Internal Flash USBB Slave HSB-PB Bridge 0 HSB-PB Bridge 1 0 1 2 3 4 CPU Data 0 CPU Instruction HMATRIX MASTERS 1 CPU SAB 2 PDCA 3 MACB 4 USBB DMA 5 EBI 5 35 32058H–AVR32–03/09 AT32UC3A 11. Fuses Settings The flash block contains a number of general purpose fuses. Some of these fuses have defined meanings outside the flash controller and are described in this section. The general purpose fuses are erase by a JTAG chip erase. 11.1 Flash General Purpose Fuse Register (FGPFRLO) FGPFR Register Description 30 GPF30 29 GPF29 28 BODEN 27 26 BODHYST 25 24 Table 11-1. 31 GPF31 BODLEVEL[5:4] 23 22 21 20 19 18 BOOTPROT 17 16 EPFL BODLEVEL[3:0] 15 14 13 12 LOCK[15:8] 11 10 9 8 7 6 5 4 LOCK[7:0] 3 2 1 0 BODEN: Brown Out Detector Enable Table 11-2. BODEN 0x0 0x1 0x2 0x3 BODEN Field Description Description BOD disabled BOD enabled, BOD reset enabled BOD enabled, BOD reset disabled BOD disabled BODHYST: Brown Out Detector Hysteresis Table 11-3. BODHYST 0b 1b BODEN Field Description Description The Brown out detector hysteresis is disabled he Brown out detector hysteresis is enabled. BODLEVEL: Brown Out Detector Trigger Level This controls the voltage trigger level for the Brown out detector. Refer to sectionTable 38-6 on page 765 for values description. If the BODLEVEL is set higher than VDDCORE and enabled by fuses, the part will be in constant reset. To recover from this situation, apply an external voltage on VDDCORE that is higher than the BOD level and disable the BOD. 36 32058H–AVR32–03/09 AT32UC3A LOCK, EPFL, BOOTPROT These are Flash controller fuses and are described in the FLASHC section. 11.2 Default Fuse Value The devices are shipped with the FGPFRLO register value: 0xFC07FFFF: • GPF31 fuse set to 1b. This fuse is used by the pre-programmed USB bootloader. • GPF30 fuse set to 1b. This fuse is used by the pre-programmed USB bootloader. • GPF29 fuse set to 1b. This fuse is used by the pre-programmed USB bootloader. • BODEN fuses set to 11b. BOD is disabled. • BODHYST fuse set to 1b. The BOD hysteresis is enabled. • BODLEVEL fuses set to 000000b. This is the minimum voltage trigger level for BOD. • BOOTPROT fuses set to 011b. The bootloader protected size is 8 Ko. • EPFL fuse set to 1b. External privileged fetch is not locked. • LOCK fuses set to 1111111111111111b. No region locked. See also the AT32UC3A Bootloader user guide document. After the JTAG chip erase command, the FGPFRLO register value is 0xFFFFFFFF. 37 32058H–AVR32–03/09 AT32UC3A 12. Peripherals 12.1 Peripheral address map Peripheral Address Mapping Address Peripheral Name Bus Table 12-1. 0xE0000000 USBB USBB Slave Interface - USBB HSB 0xFFFE0000 USBB USBB Configuration Interface - USBB PBB 0xFFFE1000 HMATRIX HMATRIX Configuration Interface - HMATRIX PBB 0xFFFE1400 FLASHC Flash Controller - FLASHC PBB 0xFFFE1800 MACB MACB Configuration Interface - MACB Static Memory Controller Configuration Interface SMC SDRAM Controller Configuration Interface SDRAMC Peripheral DMA Interface - PDCA PBB 0xFFFE1C00 SMC PBB 0xFFFE2000 SDRAMC PBB 0xFFFF0000 PDCA PBA 0xFFFF0800 INTC Interrupt Controller Interface - INTC PBA 0xFFFF0C00 PM Power Manager - PM PBA 0xFFFF0D00 RTC Real Time Clock - RTC PBA 0xFFFF0D30 WDT WatchDog Timer - WDT PBA 0xFFFF0D80 EIC External Interrupt Controller - EIC PBA 0xFFFF1000 GPIO General Purpose IO Controller - GPIO Universal Synchronous Asynchronous Receiver Transmitter - USART0 Universal Synchronous Asynchronous Receiver Transmitter - USART1 PBA 0xFFFF1400 USART0 PBA 0xFFFF1800 USART1 PBA 38 32058H–AVR32–03/09 AT32UC3A Table 12-1. Peripheral Address Mapping (Continued) Address Peripheral Name Bus 0xFFFF1C00 USART2 Universal Synchronous Asynchronous Receiver Transmitter - USART2 Universal Synchronous Asynchronous Receiver Transmitter - USART3 Serial Peripheral Interface - SPI0 PBA 0xFFFF2000 USART3 PBA 0xFFFF2400 SPI0 PBA 0xFFFF2800 SPI1 Serial Peripheral Interface - SPI1 PBA 0xFFFF2C00 TWI Two Wire Interface - TWI PBA 0xFFFF3000 PWM Pulse Width Modulation Controller - PWM PBA 0xFFFF3400 SSC Synchronous Serial Controller - SSC PBA 0xFFFF3800 TC Timer/Counter - TC PBA 0xFFFF3C00 ADC Analog To Digital Converter - ADC PBA 12.2 CPU Local Bus Mapping Some of the registers in the GPIO module are mapped onto the CPU local bus, in addition to being mapped on the Peripheral Bus. These registers can therefore be reached both by accesses on the Peripheral Bus, and by accesses on the local bus. Mapping these registers on the local bus allows cycle-deterministic toggling of GPIO pins since the CPU and GPIO are the only modules connected to this bus. Also, since the local bus runs at CPU speed, one write or read operation can be performed per clock cycle to the local busmapped GPIO registers. 39 32058H–AVR32–03/09 AT32UC3A The following GPIO registers are mapped on the local bus: Table 12-2. Port 0 Local bus mapped GPIO registers Mode WRITE SET CLEAR TOGGLE Local Bus Address 0x4000_0040 0x4000_0044 0x4000_0048 0x4000_004C 0x4000_0050 0x4000_0054 0x4000_0058 0x4000_005C 0x4000_0060 0x4000_0140 0x4000_0144 0x4000_0148 0x4000_014C 0x4000_0150 0x4000_0154 0x4000_0158 0x4000_015C 0x4000_0160 0x4000_0240 0x4000_0244 0x4000_0248 0x4000_024C 0x4000_0250 0x4000_0254 0x4000_0258 0x4000_025C 0x4000_0260 Access Write-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Read-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Read-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Read-only Register Output Driver Enable Register (ODER) Output Value Register (OVR) WRITE SET CLEAR TOGGLE Pin Value Register (PVR) 1 Output Driver Enable Register (ODER) WRITE SET CLEAR TOGGLE Output Value Register (OVR) WRITE SET CLEAR TOGGLE Pin Value Register (PVR) 2 Output Driver Enable Register (ODER) WRITE SET CLEAR TOGGLE Output Value Register (OVR) WRITE SET CLEAR TOGGLE Pin Value Register (PVR) - 40 32058H–AVR32–03/09 AT32UC3A Table 12-2. Port 3 Local bus mapped GPIO registers Mode WRITE SET CLEAR TOGGLE Local Bus Address 0x4000_0340 0x4000_0344 0x4000_0348 0x4000_034C 0x4000_0350 0x4000_0354 0x4000_0358 0x4000_035C 0x4000_0360 Access Write-only Write-only Write-only Write-only Write-only Write-only Write-only Write-only Read-only Register Output Driver Enable Register (ODER) Output Value Register (OVR) WRITE SET CLEAR TOGGLE Pin Value Register (PVR) - 12.3 Interrupt Request Signal Map The various modules may output Interrupt request signals. These signals are routed to the Interrupt Controller (INTC), described in a later chapter. 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 semantics of the different interrupt requests. The interrupt request signals are connected to the INTC as follows. Table 12-3. Group 0 Interrupt Request Signal Map Line 0 0 1 2 3 4 Module AVR32 UC CPU with optional MPU and optional OCD External Interrupt Controller External Interrupt Controller External Interrupt Controller External Interrupt Controller External Interrupt Controller External Interrupt Controller External Interrupt Controller External Interrupt Controller Real Time Counter Power Manager Frequency Meter Signal SYSBLOCK COMPARE EIC 0 EIC 1 EIC 2 EIC 3 EIC 4 EIC 5 EIC 6 EIC 7 RTC PM FREQM 1 5 6 7 8 9 10 41 32058H–AVR32–03/09 AT32UC3A Table 12-3. Interrupt Request Signal Map 0 1 2 3 4 5 6 2 7 8 9 10 11 12 13 0 1 2 3 4 5 6 3 7 8 9 10 11 12 13 14 4 5 6 7 8 0 0 0 0 0 General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Peripheral DMA Controller Flash Controller Universal Synchronous/Asynchronous Receiver/Transmitter Universal Synchronous/Asynchronous Receiver/Transmitter Universal Synchronous/Asynchronous Receiver/Transmitter Universal Synchronous/Asynchronous Receiver/Transmitter GPIO 7 GPIO 8 GPIO 9 GPIO 10 GPIO 11 GPIO 12 GPIO 13 PDCA 0 PDCA 1 PDCA 2 PDCA 3 PDCA 4 PDCA 5 PDCA 6 PDCA 7 PDCA 8 PDCA 9 PDCA 10 PDCA 11 PDCA 12 PDCA 13 PDCA 14 FLASHC USART0 USART1 USART2 USART3 General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output General Purpose Input/Output GPIO 0 GPIO 1 GPIO 2 GPIO 3 GPIO 4 GPIO 5 GPIO 6 42 32058H–AVR32–03/09 AT32UC3A Table 12-3. 9 10 11 12 13 Interrupt Request Signal Map 0 0 0 0 0 0 Serial Peripheral Interface Serial Peripheral Interface Two-wire Interface Pulse Width Modulation Controller Synchronous Serial Controller Timer/Counter Timer/Counter Timer/Counter Analog to Digital Converter Ethernet MAC USB 2.0 OTG Interface SDRAM Controller Audio Bitstream DAC SPI0 SPI1 TWI PWM SSC TC0 TC1 TC2 ADC MACB USBB SDRAMC DAC 14 1 2 15 16 17 18 19 0 0 0 0 0 12.4 12.4.1 Clock Connections Timer/Counters Each Timer/Counter channel can independently select an internal or external clock source for its counter: Table 12-4. Source Internal Timer/Counter clock connections Name TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 TIMER_CLOCK5 Connection 32 KHz Oscillator PBA clock / 2 PBA clock / 8 PBA clock / 32 PBA clock / 128 See Section 12.7 External XC0 XC1 XC2 12.4.2 USARTs Each USART can be connected to an internally divided clock: Table 12-5. USART 0 1 2 3 USART clock connections Source Internal Name CLK_DIV Connection PBA clock / 8 43 32058H–AVR32–03/09 AT32UC3A 12.4.3 SPIs Each SPI can be connected to an internally divided clock: Table 12-6. SPI 0 1 SPI clock connections Source Internal Name CLK_DIV Connection PBA clock or PBA clock / 32 12.5 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 UC Technical Reference Manual. Table 12-7. Pin EVTI_N MDO[5] MDO[4] MDO[3] MDO[2] MDO[1] MDO[0] EVTO_N MCKO MSEO[1] MSEO[0] Nexus OCD AUX port connections AXS=0 PB19 PB16 PB14 PB13 PB12 PB11 PB10 PB20 PB21 PB04 PB17 AXS=1 PA08 PA27 PA26 PA25 PA24 PA23 PA22 PB20 PA21 PA07 PA28 12.6 PDC handshake signals The PDC and the peripheral modules communicate through a set of handshake signals. The following table defines the valid settings for the Peripheral Identifier (PID) in the PDC Peripheral Select Register (PSR). Table 12-8. PID Value 0 1 2 3 PDC Handshake Signals Peripheral module & direction ADC SSC - RX USART0 - RX USART1 - RX 44 32058H–AVR32–03/09 AT32UC3A Table 12-8. PID Value 4 5 6 7 8 9 10 11 12 13 14 15 16 17 PDC Handshake Signals Peripheral module & direction USART2 - RX USART3 - RX TWI - RX SPI0 - RX SPI1 - RX SSC - TX USART0 - TX USART1 - TX USART2 - TX USART3 - TX TWI - TX SPI0 - TX SPI1 - TX ABDAC 12.7 Peripheral Multiplexing on I/O lines Each GPIO line can be assigned to one of 3 peripheral functions; A, B or C. The following table define how the I/O lines on the peripherals A, B and C are multiplexed by the GPIO. Table 12-9. TQFP100 19 20 23 24 25 26 27 28 29 30 31 33 36 37 39 40 GPIO Controller Function Multiplexing VQFP144 25 27 30 32 34 39 41 43 45 47 48 50 53 54 56 57 PIN PA00 PA01 PA02 PA03 PA04 PA05 PA06 PA07 PA08 PA09 PA10 PA11 PA12 PA13 PA14 PA15 GPIO Pin GPIO 0 GPIO 1 GPIO 2 GPIO 3 GPIO 4 GPIO 5 GPIO 6 GPIO 7 GPIO 8 GPIO 9 GPIO 10 GPIO 11 GPIO 12 GPIO 13 GPIO 14 GPIO 15 Function A USART0 - RXD USART0 - TXD USART0 - CLK USART0 - RTS USART0 - CTS USART1 - RXD USART1 - TXD USART1 - CLK USART1 - RTS USART1 - CTS SPI0 - NPCS[0] SPI0 - MISO SPI0 - MOSI SPI0 - SCK SSC TX_FRAME_SYNC SSC - TX_CLOCK SPI1 - NPCS[0] SPI1 - SCK EBI - NCS[0] EBI - ADDR[20] Function B TC - CLK0 TC - CLK1 TC - CLK2 EIM - EXTINT[4] EIM - EXTINT[5] PWM - PWM[4] PWM - PWM[5] PM - GCLK[0] SPI0 - NPCS[1] SPI0 - NPCS[2] EIM - EXTINT[6] USB - USB_ID USB - USB_VBOF SPI0 - NPCS[3] EIM - EXTINT[7] MACB - WOL DAC - DATA[0] DAC - DATAN[0] Function C 45 32058H–AVR32–03/09 AT32UC3A Table 12-9. 41 42 43 44 45 51 52 53 54 55 56 57 58 83 84 65 66 70 71 72 73 74 75 76 77 78 81 82 87 88 95 96 98 99 100 1 2 3 6 GPIO Controller Function Multiplexing 58 60 62 64 66 73 74 75 76 77 78 79 80 122 123 88 90 96 98 100 102 104 106 111 113 115 119 121 126 127 134 136 139 141 143 3 5 6 9 PA16 PA17 PA18 PA19 PA20 PA21 PA22 PA23 PA24 PA25 PA26 PA27 PA28 PA29 PA30 PB00 PB01 PB02 PB03 PB04 PB05 PB06 PB07 PB08 PB09 PB10 PB11 PB12 PB13 PB14 PB15 PB16 PB17 PB18 PB19 PB20 PB21 PB22 PB23 GPIO 16 GPIO 17 GPIO 18 GPIO 19 GPIO 20 GPIO 21 GPIO 22 GPIO 23 GPIO 24 GPIO 25 GPIO 26 GPIO 27 GPIO 28 GPIO 29 GPIO 30 GPIO 32 GPIO 33 GPIO 34 GPIO 35 GPIO 36 GPIO 37 GPIO 38 GPIO 39 GPIO 40 GPIO 41 GPIO 42 GPIO 43 GPIO 44 GPIO 45 GPIO 46 GPIO 47 GPIO 48 GPIO 49 GPIO 50 GPIO 51 GPIO 52 GPIO 53 GPIO 54 GPIO 55 SSC - TX_DATA SSC - RX_DATA SSC - RX_CLOCK SSC RX_FRAME_SYNC EIM - EXTINT[8] ADC - AD[0] ADC - AD[1] ADC - AD[2] ADC - AD[3] ADC - AD[4] ADC - AD[5] ADC - AD[6] ADC - AD[7] TWI - SDA TWI - SCL MACB - TX_CLK MACB - TX_EN MACB - TXD[0] MACB - TXD[1] MACB - CRS MACB - RXD[0] MACB - RXD[1] MACB - RX_ER MACB - MDC MACB - MDIO MACB - TXD[2] MACB - TXD[3] MACB - TX_ER MACB - RXD[2] MACB - RXD[3] MACB - RX_DV MACB - COL MACB - RX_CLK MACB - SPEED PWM - PWM[0] PWM - PWM[1] PWM - PWM[2] PWM - PWM[3] TC - A0 USB - USB_ID USB - USB_VBOF ADC - TRIGGER PM - GCLK[0] PM - GCLK[1] PM - GCLK[2] PM - GCLK[3] USART1 - DCD EBI - SDA10 EBI - ADDR[23] PWM - PWM[6] EIM - SCAN[4] EIM - SCAN[5] EIM - SCAN[6] EIM - SCAN[7] USART3 - RXD USART3 - TXD TC - CLK0 TC - CLK1 TC - CLK2 EBI - SDCK EBI - SDCKE EBI - RAS EBI - CAS EBI - SDWE SPI1 - MOSI SPI1 - MISO SPI1 - NPCS[1] SPI1 - NPCS[2] SPI1 - NPCS[3] EIM - EXTINT[0] EIM - EXTINT[1] EIM - EXTINT[2] EIM - EXTINT[3] EIM - SCAN[0] EIM - SCAN[1] EIM - SCAN[2] EIM - SCAN[3] USART2 - RTS USART2 - CTS USART2 - RTS USART2 - CTS DAC - DATA[0] DAC - DATAN[0] USART3 - CLK DAC - DATA[1] DAC - DATAN[1] EBI - NCS[3] USART3 - RTS USART3 - CTS USB - USB_ID USB - USB_VBOF DAC - DATA[1] DAC - DATAN[1] EBI - NCS[0] EBI - ADDR[20] EBI - ADDR[21] EBI - ADDR[22] EBI - ADDR[21] EBI - ADDR[22] MACB - WOL 46 32058H–AVR32–03/09 AT32UC3A Table 12-9. 7 8 9 10 14 15 16 17 63 64 85 86 93 94 GPIO Controller Function Multiplexing 11 13 14 15 19 20 21 22 85 86 124 125 132 133 1 2 4 10 12 24 26 31 33 35 38 40 42 44 46 59 61 63 65 67 87 89 91 95 97 PB24 PB25 PB26 PB27 PB28 PB29 PB30 PB31 PC00 PC01 PC02 PC03 PC04 PC05 PX00 PX01 PX02 PX03 PX04 PX05 PX06 PX07 PX08 PX09 PX10 PX11 PX12 PX13 PX14 PX15 PX16 PX17 PX18 PX19 PX20 PX21 PX22 PX23 PX24 GPIO 56 GPIO 57 GPIO 58 GPIO 59 GPIO 60 GPIO 61 GPIO 62 GPIO 63 GPIO 64 GPIO 65 GPIO 66 GPIO 67 GPIO 68 GPIO 69 GPIO 100 GPIO 99 GPIO 98 GPIO 97 GPIO 96 GPIO 95 GPIO 94 GPIO 93 GPIO 92 GPIO 91 GPIO 90 GPIO 109 GPIO 108 GPIO 107 GPIO 106 GPIO 89 GPIO 88 GPIO 87 GPIO 86 GPIO 85 GPIO 84 GPIO 83 GPIO 82 GPIO 81 GPIO 80 EBI - DATA[10] EBI - DATA[9] EBI - DATA[8] EBI - DATA[7] EBI - DATA[6] EBI - DATA[5] EBI - DATA[4] EBI - DATA[3] EBI - DATA[2] EBI - DATA[1] EBI - DATA[0] EBI - NWE1 EBI - NWE0 EBI - NRD EBI - NCS[1] EBI - ADDR[19] EBI - ADDR[18] EBI - ADDR[17] EBI - ADDR[16] EBI - ADDR[15] EBI - ADDR[14] EBI - ADDR[13] EBI - ADDR[12] EBI - ADDR[11] EBI - ADDR[10] EIM - SCAN[0] EIM - SCAN[1] EIM - SCAN[2] EIM - SCAN[3] EIM - SCAN[4] EIM - SCAN[5] USART3 - RTS USART3 - CTS USART0 - RXD USART0 - TXD USART0 - CTS USART0 - RTS USART1 - RXD USART1 - TXD USART1 - CTS USART1 - RTS USART3 - RXD USART3 - TXD USART2 - RXD USART2 - TXD USART2 - CTS USART2 - RTS TC - A0 TC - B0 TC - A1 TC - B1 TC - A2 TC - B2 TC - CLK0 TC - CLK1 TC - CLK2 TC - B0 TC - A1 TC - B1 TC - A2 TC - B2 USART2 - RXD USART2 - TXD USART2 - CLK USART1 - DSR USART1 - DTR USART1 - RI PWM - PWM[4] PWM - PWM[5] PM - GCLK[1] PM - GCLK[2] PM - GCLK[3] EBI - NCS[2] EBI - SDCS EBI - NWAIT 47 32058H–AVR32–03/09 AT32UC3A Table 12-9. GPIO Controller Function Multiplexing 99 101 103 105 107 110 112 114 118 120 135 137 140 142 144 PX25 PX26 PX27 PX28 PX29 PX30 PX31 PX32 PX33 PX34 PX35 PX36 PX37 PX38 PX39 GPIO 79 GPIO 78 GPIO 77 GPIO 76 GPIO 75 GPIO 74 GPIO 73 GPIO 72 GPIO 71 GPIO 70 GPIO 105 GPIO 104 GPIO 103 GPIO 102 GPIO 101 EBI - ADDR[9] EBI - ADDR[8] EBI - ADDR[7] EBI - ADDR[6] EBI - ADDR[5] EBI - ADDR[4] EBI - ADDR[3] EBI - ADDR[2] EBI - ADDR[1] EBI - ADDR[0] EBI - DATA[15] EBI - DATA[14] EBI - DATA[13] EBI - DATA[12] EBI - DATA[11] EIM - SCAN[6] EIM - SCAN[7] SPI0 - MISO SPI0 - MOSI SPI0 - SCK SPI0 - NPCS[0] SPI0 - NPCS[1] SPI0 - NPCS[2] SPI0 - NPCS[3] SPI1 - MISO SPI1 - MOSI SPI1 - SCK SPI1 - NPCS[0] SPI1 - NPCS[1] SPI1 - NPCS[2] 12.8 Oscillator Pinout The oscillators are not mapped to the normal A,B or C functions and their muxings are controlled by registers in the Power Manager (PM). Please refer to the power manager chapter for more information about this. Table 12-10. Oscillator pinout TQFP100 pin 85 93 63 86 94 64 VQFP144 pin 124 132 85 125 133 86 Pad PC02 PC04 PC00 PC03 PC05 PC01 Oscillator pin xin0 xin1 xin32 xout0 xout1 xout32 12.9 USART Configuration Table 12-11. USART Supported Mode SPI USART0 USART1 USART2 USART3 Yes Yes Yes Yes RS485 No Yes No No ISO7816 No Yes No No IrDA No Yes No No Modem No Yes No No Manchester Encoding No Yes No No 48 32058H–AVR32–03/09 AT32UC3A 12.10 GPIO The GPIO open drain feature (GPIO ODMER register (Open Drain Mode Enable Register)) is not available for this device. 12.11 Peripheral overview 12.11.1 External Bus Interface • Optimized for Application Memory Space support • Integrates Two External Memory Controllers: – Static Memory Controller – SDRAM Controller • Optimized External Bus: – 16-bit Data Bus – 24-bit Address Bus, Up to 16-Mbytes Addressable – Optimized pin multiplexing to reduce latencies on External Memories • 4 SRAM Chip Selects, 1SDRAM Chip Select: – Static Memory Controller on NCS0 – SDRAM Controller or Static Memory Controller on NCS1 – Static Memory Controller on NCS2 – Static Memory Controller on NCS3 12.11.2 Static Memory Controller • 4 Chip Selects Available • 64-Mbyte Address Space per Chip Select • 8-, 16-bit Data Bus • Word, Halfword, Byte Transfers • Byte Write or Byte Select Lines • Programmable Setup, Pulse And Hold Time for Read Signals per Chip Select • Programmable Setup, Pulse And Hold Time for Write Signals per Chip Select • Programmable Data Float Time per Chip Select • Compliant with LCD Module • External Wait Request • Automatic Switch to Slow Clock Mode • Asynchronous Read in Page Mode Supported: Page Size Ranges from 4 to 32 Bytes SDRAM Controller • Numerous Configurations Supported – 2K, 4K, 8K Row Address Memory Parts – SDRAM with Two or Four Internal Banks – SDRAM with 16-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 • Energy-saving Capabilities – Self-refresh, Power-down and Deep Power Modes Supported 12.11.3 49 32058H–AVR32–03/09 AT32UC3A – 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 12.11.4 USB Controller • USB 2.0 Compliant, Full-/Low-Speed (FS/LS) and On-The-Go (OTG), 12 Mbit/s • 7 Pipes/Endpoints • 960 bytes of Embedded Dual-Port RAM (DPRAM) for Pipes/Endpoints • Up to 2 Memory Banks per Pipe/Endpoint (Not for Control Pipe/Endpoint) • Flexible Pipe/Endpoint Configuration and Management with Dedicated DMA Channels • On-Chip Transceivers Including Pull-Ups 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 Peripheral Bus A (PBA) max frequency – The chip select line may be left active to speed up transfers on the same device 12.11.5 12.11.6 Two-wire Interface • • • • High speed up to 400kbit/s Compatibility with standard two-wire serial memory One, two or three bytes for slave address Sequential read/write operations 12.11.7 USART • Programmable Baud Rate Generator • 5- to 9-bit full-duplex synchronous or asynchronous serial communications – – – – – – – – – 1, 1.5 or 2 stop bits in Asynchronous Mode or 1 or 2 stop bits in Synchronous Mode Parity generation and error detection Framing error detection, overrun error detection MSB- or LSB-first Optional break generation and detection By 8 or by-16 over-sampling receiver frequency Hardware handshaking RTS-CTS Receiver time-out and transmitter timeguard Optional Multi-drop Mode with address generation and detection 50 32058H–AVR32–03/09 AT32UC3A – 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 – Remote Loopback, Local Loopback, Automatic Echo • SPI Mode – Master or Slave – Serial Clock Programmable Phase and Polarity – SPI Serial Clock (SCK) Frequency up to Internal Clock Frequency PBA/4 • Supports Connection of Two Peripheral DMA Controller Channels (PDC) – Offers Buffer Transfer without Processor Intervention 12.11.8 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 • Receiver and transmitter include a data signal, a clock signal and a frame synchronization signal 12.11.9 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 12.11.10 Pulse Width Modulation Controller • 7 channels, one 20-bit counter per channel • Common clock generator, providing Thirteen Different Clocks – A Modulo n counter providing eleven clocks – Two independent Linear Dividers working on modulo n counter outputs • Independent channel programming – Independent Enable Disable Commands – Independent Clock – Independent Period and Duty Cycle, with Double Bufferization – Programmable selection of the output waveform polarity – Programmable center or left aligned output waveform 51 32058H–AVR32–03/09 AT32UC3A 12.11.11 Ethernet 10/100 MAC • • • • • • • • • • • • Compatibility with IEEE Standard 802.3 10 and 100 Mbits per second data throughput capability Full- and half-duplex operations MII or RMII interface to the physical layer Register Interface to address, data, status and control registers DMA Interface, operating as a master on the Memory Controller Interrupt generation to signal receive and transmit completion 28-byte transmit and 28-byte receive FIFOs Automatic pad and CRC generation on transmitted frames Address checking logic to recognize four 48-bit addresses Support promiscuous mode where all valid frames are copied to memory Support physical layer management through MDIO interface control of alarm and update time/calendar data 12.11.12 Audio Bitstream DAC • Digital Stereo DAC • Oversampled D/A conversion architecture – Oversampling ratio fixed 128x – FIR equalization filter – Digital interpolation filter: Comb4 – 3rd Order Sigma-Delta D/A converters • Digital bitstream outputs • Parallel interface • Connected to Peripheral DMA Controller for background transfer without CPU intervention 52 32058H–AVR32–03/09 AT32UC3A 13. Power Manager (PM) Rev: 2.0.0.1 13.1 Features • • • • • • • • • • • • • Controls integrated oscillators and PLLs Generates clocks and resets for digital logic Supports 2 crystal oscillators 450 kHz-16 MHz Supports 2 PLLs 80-240 MHz Supports 32 KHz ultra-low power oscillator Integrated low-power RC oscillator On-the fly frequency change of CPU, HSB, PBA, and PBB clocks Sleep modes allow simple disabling of logic clocks, PLLs, and oscillators Module-level clock gating through maskable peripheral clocks Wake-up from internal or external interrupts Generic clocks with wide frequency range provided Automatic identification of reset sources Controls brownout detector (BOD), RC oscillator, and bandgap voltage reference through control and calibration registers 13.2 Description The Power Manager (PM) controls the oscillators and PLLs, and generates the clocks and resets in the device. The PM controls two fast crystal oscillators, as well as two PLLs, which can multiply the clock from either oscillator to provide higher frequencies. Additionally, a low-power 32 KHz oscillator is used to generate the real-time counter clock for high accuracy real-time measurements. The PM also contains a low-power RC oscillator with fast start-up time, which can be used to clock the digital logic. The provided clocks are divided into synchronous and generic clocks. The synchronous clocks are used to clock the main digital logic in the device, namely the CPU, and the modules and peripherals connected to the HSB, PBA, and PBB buses. The generic clocks are asynchronous clocks, which can be tuned precisely within a wide frequency range, which makes them suitable for peripherals that require specific frequencies, such as timers and communication modules. The PM also contains advanced power-saving features, allowing the user to optimize the power consumption for an application. The synchronous clocks are divided into three clock domains, one for the CPU and HSB, one for modules on the PBA bus, and one for modules on the PBB bus.The three clocks can run at different speeds, so the user can save power by running peripherals at a relatively low clock, while maintaining a high CPU performance. Additionally, the clocks can be independently changed on-the-fly, without halting any peripherals. This enables the user to adjust the speed of the CPU and memories to the dynamic load of the application, without disturbing or re-configuring active peripherals. Each module also has a separate clock, enabling the user to switch off the clock for inactive modules, to save further power. Additionally, clocks and oscillators can be automatically switched off during idle periods by using the sleep instruction on the CPU. The system will return to normal on occurrence of interrupts. The Power Manager also contains a Reset Controller, which collects all possible reset sources, generates hard and soft resets, and allows the reset source to be identified by software. 53 32058H–AVR32–03/09 AT32UC3A 13.3 Block Diagram RCOSC Synchronous Clock Generator PLL0 Synchronous clocks CPU, HSB, PBA, PBB Oscillator 0 Oscillator 1 PLL1 G eneric Clock Generator Generic clocks 32 KHz Oscillator OSC/PLL Control signals 32 KHz clock for RTC RC Oscillator Slow clock Oscillator and PLL Control Voltage Regulator Startup Counter Interrupts Sleep Controller Sleep instruction fuses Calibration Registers Brown-Out Detector Power-O n Detector Other reset sources External Reset Pad Reset Controller resets Figure 13-1. Power Manager block diagram 54 32058H–AVR32–03/09 AT32UC3A 13.4 13.4.1 Product Dependencies I/O Lines The PM provides a number of generic clock outputs, which can be connected to output pins, multiplexed with GPIO lines. The programmer must first program the GPIO controller to assign these pins to their peripheral function. If the I/O pins of the PM are not used by the application, they can be used for other purposes by the GPIO controller. 13.4.2 Interrupt The PM interrupt line is connected to one of the internal sources of the interrupt controller. Using the PM interrupt requires the interrupt controller to be programmed first. 13.4.3 Clock implementation In AT32UC3A, the HSB shares the source clock with the CPU. This means that writing to the HSBDIV and HSBSEL bits in CKSEL has no effect. These bits will always read the same as CPUDIV and CPUSEL. 13.5 13.5.1 Functional Description Slow clock The slow clock is generated from an internal RC oscillator which is always running, except in Static mode. The slow clock can be used for the main clock in the device, as described in ”Synchronous clocks” on page 58. The slow clock is also used for the Watchdog Timer and measuring various delays in the Power Manager. The RC oscillator has a 3 cycles startup time, and is always available when the CPU is running. The RC oscillator operates at approximately 115 kHz, and can be calibrated to a narrow range by the RCOSCCAL fuses. Software can also change RC oscillator calibration through the use of the RCCR register. Please see the Electrical Characteristics section for details. RC oscillator can also be used as the RTC clock when crystal accuracy is not required. 13.5.2 Oscillator 0 and 1 operation The two main oscillators are designed to be used with an external 450 kHz to 16 MHz crystal and two biasing capacitors, as shown in Figure 13-2. Oscillator 0 can be used for the main clock in the device, as described in ”Synchronous clocks” on page 58. Both oscillators can be used as source for the generic clocks, as described in ”Generic clocks” on page 61. The oscillators are disabled by default after reset. When the oscillators are disabled, the XIN and XOUT pins can be used as general purpose I/Os. When the oscillators are configured to use an external clock, the clock must be applied to the XIN pin while the XOUT pin can be used as a general purpose I/O. The oscillators can be enabled by writing to the OSCnEN bits in MCCTRL. Operation mode (external clock or crystal) is chosen by writing to the MODE field in OSCCTRLn. Oscillators are automatically switched off in certain sleep modes to reduce power consumption, as described in Section 13.5.7 on page 60. After a hard reset, or when waking up from a sleep mode that disabled the oscillators, the oscillators may need a certain amount of time to stabilize on the correct frequency. This start-up time can be set in the OSCCTRLn register. 55 32058H–AVR32–03/09 AT32UC3A The PM masks the oscillator outputs during the start-up time, to ensure that no unstable clocks propagate to the digital logic. The OSCnRDY bits in POSCSR are automatically set and cleared according to the status of the oscillators. A zero to one transition on these bits can also be configured to generate an interrupt, as described in ”Interrupt Enable/Disable/Mask/Status/Clear” on page 76. C2 XO U T XIN C1 Figure 13-2. Oscillator connections 13.5.3 32 KHz oscillator operation The 32 KHz oscillator operates as described for Oscillator 0 and 1 above. The 32 KHz oscillator is used as source clock for the Real-Time Counter. The oscillator is disabled by default, but can be enabled by writing OSC32EN in OSCCTRL32. The oscillator is an ultra-low power design and remains enabled in all sleep modes except Static mode. While the 32 KHz oscillator is disabled, the XIN32 and XOUT32 pins are available as general purpose I/Os. When the oscillator is configured to work with an external clock (MODE field in OSCCTRL32 register), the external clock must be connected to XIN32 while the XOUT32 pin can be used as a general purpose I/O. The startup time of the 32 KHz oscillator can be set in the OSCCTRL32, after which OSC32RDY in POSCSR is set. An interrupt can be generated on a zero to one transition of OSC32RDY. As a crystal oscillator usually requires a very long startup time (up to 1 second), the 32 KHz oscillator will keep running across resets, except Power-On-Reset. 13.5.4 PLL operation The device contains two PLLs, PLL0 and PLL1. These are disabled by default, but can be enabled to provide high frequency source clocks for synchronous or generic clocks. The PLLs can take either Oscillator 0 or 1 as reference clock. The PLL output is divided by a multiplication factor, and the PLL compares the resulting clock to the reference clock. The PLL will adjust its output frequency until the two compared clocks are equal, thus locking the output frequency to a multiple of the reference clock frequency. The Voltage Controlled Oscillator inside the PLL can generate frequencies from 80 to 240 MHz. To make the PLL output frequencies under 80 MHz the OTP[1] bitfield could be set. This will 56 32058H–AVR32–03/09 AT32UC3A divide the output of the PLL by two and bring the clock in range of the max frequency of the CPU. When the PLL is switched on, or when changing the clock source or multiplication factor for the PLL, the PLL is unlocked and the output frequency is undefined. The PLL clock for the digital logic is automatically masked when the PLL is unlocked, to prevent connected digital logic from receiving a too high frequency and thus become unstable. PLLM UL P L L O P T [1 ] O u tp u t D iv id e r fvco 0 fP LL M ask P L L c lo c k 1 /2 O sc0 c lo c k O sc1 c lo c k P hase D e te c to r Lock D e te c to r 1 0 1 In p u t D iv id e r P L L D IV VCO L o c k b it PLLO SC PLLO PT Figure 13-3. PLL with control logic and filters 13.5.4.1 Enabling the PLL PLLn is enabled by writing the PLLEN bit in the PLLn register. PLLOSC selects Oscillator 0 or 1 as clock source. The PLLMUL and PLLDIV bitfields must be written with the multiplication and division factors, respectively, creating the voltage controlled ocillator frequency fVCO and the PLL frequency fPLL : fVCO = (PLLMUL+1)/(PLLDIV) • fOSC if PLLDIV > 0. fVCO = 2*(PLLMUL+1) • fOSC if PLLDIV = 0. If PLLOPT[1] field is set to 0: fPLL = fVCO. If PLLOPT[1] field is set to 1: fPLL = fVCO / 2. The PLLn:PLLOPT field should be set to proper values according to the PLL operating frequency. The PLLOPT field can also be set to divide the output frequency of the PLLs by 2. The lock signal for each PLL is available as a LOCKn flag in POSCSR. An interrupt can be generated on a 0 to 1 transition of these bits. 57 32058H–AVR32–03/09 AT32UC3A 13.5.5 Synchronous clocks The slow clock (default), Oscillator 0, or PLL0 provide the source for the main clock, which is the common root for the synchronous clocks for the CPU/HSB, PBA, and PBB modules. The main clock is divided by an 8-bit prescaler, and each of these four synchronous clocks can run from any tapping of this prescaler, or the undivided main clock, as long as fCPU fPBA,B,. The synchronous clock source can be changed on-the fly, responding to varying load in the application. The clock domains can be shut down in sleep mode, as described in ”Sleep modes” on page 60. Additionally, the clocks for each module in the four domains can be individually masked, to avoid power consumption in inactive modules. Sleep instruction Sleep Controller 0 Slow clock Osc0 clock PLL0 clock Main clock Mask CPUMASK CPU clocks HSB clocks PBAclocks PBB clocks Prescaler 1 CPUDIV MCSEL CPUSEL Figure 13-4. Synchronous clock generation 13.5.5.1 Selecting PLL or oscillator for the main clock The common main clock can be connected to the slow clock, Oscillator 0, or PLL0. By default, the main clock will be connected to the slow clock. The user can connect the main clock to Oscillator 0 or PLL0 by writing the MCSEL bitfield in the Main Clock Control Register (MCCTRL). This must only be done after that unit has been enabled, otherwise a deadlock will occur. Care should also be taken that the new frequency of the synchronous clocks does not exceed the maximum frequency for each clock domain. 13.5.5.2 Selecting synchronous clock division ratio The main clock feeds an 8-bit prescaler, which can be used to generate the synchronous clocks. By default, the synchronous clocks run on the undivided main clock. The user can select a pres- 58 32058H–AVR32–03/09 AT32UC3A caler division for the CPU clock by writing CKSEL:CPUDIV to 1 and CPUSEL to the prescaling value, resulting in a CPU clock frequency: fCPU = fmain / 2(CPUSEL+1) Similarly, the clock for the PBA, and PBB can be divided by writing their respective bitfields. To ensure correct operation, frequencies must be selected so that fCPU fPBA,B. Also, frequencies must never exceed the specified maximum frequency for each clock domain. CKSEL can be written without halting or disabling peripheral modules. Writing CKSEL allows a new clock setting to be written to all synchronous clocks at the same time. It is possible to keep one or more clocks unchanged by writing the same value a before to the xxxDIV and xxxSEL bitfields. This way, it is possible to e.g. scale CPU and HSB speed according to the required performance, while keeping the PBA and PBB frequency constant. 13.5.5.3 Clock Ready flag There is a slight delay from CKSEL is written and the new clock setting becomes effective. During this interval, the Clock Ready (CKRDY) flag in ISR will read as 0. If IER:CKRDY is written to 1, the Power Manager interrupt can be triggered when the new clock setting is effective. CKSEL must not be re-written while CKRDY is 0, or the system may become unstable or hang. 13.5.6 Peripheral clock masking By default, the clock for all modules are enabled, regardless of which modules are actually being used. It is possible to disable the clock for a module in the CPU, HSB, PBA, or PBB clock domain by writing the corresponding bit in the Clock Mask register (CPU/HSB/PBA/PBB) to 0. When a module is not clocked, it will cease operation, and its registers cannot be read or written. The module can be re-enabled later by writing the corresponding mask bit to 1. A module may be connected to several clock domains, in which case it will have several mask bits. Table 13-5 contains a list of implemented maskable clocks. 13.5.6.1 Cautionary note Note that clocks should only be switched off if it is certain that the module will not be used. Switching off the clock for the internal RAM will cause a problem if the stack is mapped there. Switching off the clock to the Power Manager (PM), which contains the mask registers, or the corresponding PBx bridge, will make it impossible to write the mask registers again. In this case, they can only be re-enabled by a system reset. 13.5.6.2 Mask Ready flag Due to synchronization in the clock generator, there is a slight delay from a mask register is written until the new mask setting goes into effect. When clearing mask bits, this delay can usually be ignored. However, when setting mask bits, the registers in the corresponding module must not be written until the clock has actually be re-enabled. The status flag MSKRDY in ISR provides the required mask status information. When writing either mask register with any value, this bit is cleared. The bit is set when the clocks have been enabled and disabled according to the new mask setting. Optionally, the Power Manager interrupt can be enabled by writing the MSKRDY bit in IER. 59 32058H–AVR32–03/09 AT32UC3A 13.5.7 Sleep modes In normal operation, all clock domains are active, allowing software execution and peripheral operation. When the CPU is idle, it is possible to switch off the CPU clock and optionally other clock domains to save power. This is activated by the sleep instruction, which takes the sleep mode index number as argument. 13.5.7.1 Entering and exiting sleep modes The sleep instruction will halt the CPU and all modules belonging to the stopped clock domains. The modules will be halted regardless of the bit settings of the mask registers. Oscillators and PLLs can also be switched off to save power. Some of these modules have a relatively long start-up time, and are only switched off when very low power consumption is required. The CPU and affected modules are restarted when the sleep mode is exited. This occurs when an interrupt triggers. Note that even if an interrupt is enabled in sleep mode, it may not trigger if the source module is not clocked. 13.5.7.2 Supported sleep modes The following sleep modes are supported. These are detailed in Table 13-1. •Idle: The CPU is stopped, the rest of the chip is operating. Wake-up sources are any interrupt. •Frozen: The CPU and HSB modules are stopped, peripherals are operating. Wake-up sources are any interrupt from PB modules. •Standby: All synchronous clocks are stopped, but oscillators and PLLs are running, allowing quick wake-up to normal mode. Wake-up sources are RTC or external interrupt (EIC). •Stop: As Standby, but Oscillator 0 and 1, and the PLLs are stopped. 32 KHz (if enabled) and RC oscillators and RTC/WDT still operate. Wake-up sources are RTC, external interrupt (EIC), or external reset pin. •DeepStop: All synchronous clocks, Oscillator 0 and 1 and PLL 0 and 1 are stopped. 32 KHz oscillator can run if enabled. RC oscillator still operates. Bandgap voltage reference and BOD is turned off. Wake-up sources are RTC, external interrupt (EIC) or external reset pin. •Static: All oscillators, including 32 KHz and RC oscillator are stopped. Bandgap voltage reference BOD detector is turned off. Wake-up sources are external interrupt (EIC) in asynchronous mode only or external reset pin. Table 13-1. Index 0 1 2 3 4 5 Sleep modes Sleep Mode Idle Frozen Standby Stop DeepStop Static CPU Stop Stop Stop Stop Stop Stop HSB Run Stop Stop Stop Stop Stop PBA,B GCLK Run Run Stop Stop Stop Stop Osc0,1 PLL0,1 Run Run Run Stop Stop Stop Osc32 Run Run Run Run Run Stop RCOsc Run Run Run Run Run Stop BOD & Bandgap On On On On Off Off Voltage Regulator Full power Full power Full power Low power Low power Low power 60 32058H–AVR32–03/09 AT32UC3A The power level of the internal voltage regulator is also adjusted according to the sleep mode to reduce the internal regulator power consumption. 13.5.7.3 Precautions when entering sleep mode Modules communicating with external circuits should normally be disabled before entering a sleep mode that will stop the module operation. This prevents erratic behavior when entering or exiting sleep mode. Please refer to the relevant module documentation for recommended actions. Communication between the synchronous clock domains is disturbed when entering and exiting sleep modes. This means that bus transactions are not allowed between clock domains affected by the sleep mode. The system may hang if the bus clocks are stopped in the middle of a bus transaction. The CPU is automatically stopped in a safe state to ensure that all CPU bus operations are complete when the sleep mode goes into effect. Thus, when entering Idle mode, no further action is necessary. When entering a sleep mode (except Idle mode), all HSB masters must be stopped before entering the sleep mode. Also, if there is a chance that any PB write operations are incomplete, the CPU should perform a read operation from any register on the PB bus before executing the sleep instruction. This will stall the CPU while waiting for any pending PB operations to complete. 13.5.7.4 Wake up The USB can be used to wake up the part from sleep modes through register PM_AWEN of the Power Manager. 13.5.8 Generic clocks Timers, communication modules, and other modules connected to external circuitry may require specific clock frequencies to operate correctly. The Power Manager contains an implementation defined number of generic clocks that can provide a wide range of accurate clock frequencies. Each generic clock module runs from either Oscillator 0 or 1, or PLL0 or 1. The selected source can optionally be divided by any even integer up to 512. Each clock can be independently enabled and disabled, and is also automatically disabled along with peripheral clocks by the Sleep Controller. 61 32058H–AVR32–03/09 AT32UC3A Sleep Controller 0 Osc0 clock Osc1 clock PLL0 clock PLL1 clock 0 Mask Divider 1 Generic Clock 1 PLLSEL OSCSEL DIVEN DIV CEN Figure 13-5. Generic clock generation 13.5.8.1 Enabling a generic clock A generic clock is enabled by writing the CEN bit in GCCTRL to 1. Each generic clock can use either Oscillator 0 or 1 or PLL0 or 1 as source, as selected by the PLLSEL and OSCSEL bits. The source clock can optionally be divided by writing DIVEN to 1 and the division factor to DIV, resulting in the output frequency: fGCLK = fSRC / (2*(DIV+1)) 13.5.8.2 Disabling a generic clock The generic clock can be disabled by writing CEN to 0 or entering a sleep mode that disables the PB clocks. In either case, the generic clock will be switched off on the first falling edge after the disabling event, to ensure that no glitches occur. If CEN is written to 0, the bit will still read as 1 until the next falling edge occurs, and the clock is actually switched off. When writing CEN to 0, the other bits in GCCTRL should not be changed until CEN reads as 0, to avoid glitches on the generic clock. When the clock is disabled, both the prescaler and output are reset. 13.5.8.3 Changing clock frequency When changing generic clock frequency by writing GCCTRL, the clock should be switched off by the procedure above, before being re-enabled with the new clock source or division setting. This prevents glitches during the transition. 62 32058H–AVR32–03/09 AT32UC3A 13.5.8.4 Generic clock implementation In AT32UC3A, there are 6 generic clocks. These are allocated to different functions as shown in Table 13-2. Table 13-2. Generic clock allocation Function GCLK0 pin GCLK1 pin GCLK2 pin GCLK3 pin USBB ABDAC Clock number 0 1 2 3 4 5 13.5.9 Divided PB clocks The clock generator in the Power Manager provides divided PBA and PBB clocks for use by peripherals that require a prescaled PBx clock. This is described in the documentation for the relevant modules. The divided clocks are not directly maskable, but are stopped in sleep modes where the PBx clocks are stopped. 13.5.10 Debug operation During a debug session, the user may need to halt the system to inspect memory and CPU registers. The clocks normally keep running during this debug operation, but some peripherals may require the clocks to be stopped, e.g. to prevent timer overflow, which would cause the program to fail. For this reason, peripherals on the PBA and PBB buses may use “debug qualified” PBx clocks. This is described in the documentation for the relevant modules. The divided PBx clocks are always debug qualified clocks. Debug qualified PB clocks are stopped during debug operation. The debug system can optionally keep these clocks running during the debug operation. This is described in the documentation for the On-Chip Debug system. 13.5.11 Reset Controller The Reset Controller collects the various reset sources in the system and generates hard and soft resets for the digital logic. The device contains a Power-On Detector, which keeps the system reset until power is stable. This eliminates the need for external reset circuitry to guarantee stable operation when powering up the device. 63 32058H–AVR32–03/09 AT32UC3A It is also possible to reset the device by asserting the RESET_N pin. This pin has an internal pullup, and does not need to be driven externally when negated. Table 13-4 lists these and other reset sources supported by the Reset Controller. RC _RCAUSE RESET_N P o w e r-O n D e te c to r R eset C o n tro lle r CPU, HSB, PBA, PBB O C D , R T C /W D T C lo c k G e n e ra to B ro w n o u t D e te c to r JT A G OCD W a tc h d o g R e s e t Figure 13-6. Reset Controller block diagram In addition to the listed reset types, the JTAG can keep parts of the device statically reset through the JTAG Reset Register. See JTAG documentation for details. Table 13-3. Reset source Reset description Description Supply voltage below the power-on reset detector threshold voltage RESET_N pin asserted Supply voltage below the brownout reset detector threshold voltage Caused by an illegal CPU access to external memory while in Supervisor mode See watchdog timer documentation. See On-Chip Debug documentation Power-on Reset External Reset Brownout Reset CPU Error Watchdog Timer OCD When a Reset occurs, some parts of the chip are not necessarily reset, depending on the reset source. Only the Power On Reset (POR) will force a reset of the whole chip. 64 32058H–AVR32–03/09 AT32UC3A Table 13-4 lists parts of the device that are reset, depending on the reset source. Table 13-4. Effect of the different reset events Power-On Reset CPU/HSB/PBA/PBB (excluding Power Manager) 32 KHz oscillator RTC control register GPLP registers Watchdog control register Y Y Y Y Y Y Y Y Y Y Y Y Y External Reset Y N N N Y N N Y Y Y Y Y Y Watchdog Reset Y N N N N N N N N Y Y Y N BOD Reset Y N N N Y N N N N Y Y Y Y CPU Error Reset Y N N N Y N N N N Y Y Y Y OCD Reset Y N N N Y N N N N Y Y Y N Voltage Calibration register RC Oscillator Calibration register BOD control register Bandgap control register Clock control registers Osc0/Osc1 and control registers PLL0/PLL1 and control registers OCD system and OCD registers The cause of the last reset can be read from the RCAUSE register. This register contains one bit for each reset source, and can be read during the boot sequence of an application to determine the proper action to be taken. 13.5.11.1 Power-On Detector The Power-On Detector monitors the VDDCORE supply pin and generates a reset when the device is powered on. The reset is active until the supply voltage from the linear regulator is above the power-on threshold level. The reset will be re-activated if the voltage drops below the power-on threshold level. See Electrical Characteristics for parametric details. 13.5.11.2 Brown-Out Detector The Brown-Out Detector (BOD) monitors the VDDCORE supply pin and compares the supply voltage to the brown-out detection level, as set in BOD:LEVEL. The BOD is disabled by default, but can be enabled either by software or by flash fuses. The Brown-Out Detector can either generate an interrupt or a reset when the supply voltage is below the brown-out detection level. In any case, the BOD output is available in bit POSCR:BODET bit. Note that any change to the BOD:LEVEL field of the BOD register should be done with the BOD deactivated to avoid spurious reset or interrupt. See Electrical Characteristics for parametric details. 65 32058H–AVR32–03/09 AT32UC3A 13.5.11.3 External Reset The external reset detector monitors the state of the RESET_N pin. By default, a low level on this pin will generate a reset. 13.5.12 Calibration registers The Power Manager controls the calibration of the RC oscillator, voltage regulator, bandgap voltage reference through several calibrations registers. Those calibration registers are loaded after a Power On Reset with default values stored in factory-programmed flash fuses. Although it is not recommended to override default factory settings, it is still possible to override these default values by writing to those registers. To prevent unexpected writes due to software bugs, write access to these registers is protected by a “key”. First, a write to the register must be made with the field “KEY” equal to 0x55 then a second write must be issued with the “KEY” field equal to 0xAA 13.6 User Interface Offset 0x0000 0x0004 0x0008 0x000C 0x0010 0x0014 0x0018 - 0x001C 0x0020 0x0024 0x0028 0x002C 0x0030 0x0034 0x0038 0x003C 0x0040 0x0044 0x0048 0x004C 0x0050 0x0054 0x0058 - 0x005C Register Main Clock Control Clock Select CPU Mask HSB Mask PBA Mask PBB Mask Reserved PLL0 Control PLL1 Control Oscillator 0 Control Register Oscillator 1 Control Register Oscillator 32 Control Register Reserved Reserved Reserved PM Interrupt Enable Register PM Interrupt Disable Register PM Interrupt Mask Register PM Interrupt Status Register PM Interrupt Clear Register Power and Oscillators Status Register Reserved IER IDR IMR ISR ICR PLL0 PLL1 Name MCCTRL CKSEL CPUMASK HSBMASK PBAMASK PBBMASK Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Reset State 0x00000000 0x00000000 0x00000003 0x0000007F 0x0000FFFF 0x0000003F Read/Write Read/Write Read/Write Read/Write Read/Write 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 OSCCTRL0 OSCCTRL1 OSCCTRL32 Write Only Write Only Read Only Read Only Write Only Read/Write 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 POSCSR 66 32058H–AVR32–03/09 AT32UC3A 0x0060 0x0064 - 0x00BC 0x00C0 0x00C4 0x00C8 0x00CC 0x00D0 0x00D4 - 0x013C 0x0140 0x0144 - 0x01FC 0x0200 0x0204 Generic Clock Control Reserved RC Oscillator Calibration Register Bandgap Calibration Register Linear Regulator Calibration Register Reserved BOD Level Register Reserved Reset Cause Register Reserved General Purpose Low-Power register 0 General Purpose Low-Power register 1 GPLP0 GPLP1 Read/Write Read/Write 0x00000000 0x00000000 RCAUSE Read Only Latest Reset Source BOD Read/Write BOD fuses in Flash RCCR BGCR VREGCR Read/Write Read/Write Read/Write Factory settings Factory settings Factory settings GCCTRL Read/Write 0x00000000 67 32058H–AVR32–03/09 AT32UC3A 13.6.1 Name: Access Type: Main Clock Control MCCTRL Read/Write 31 23 15 7 - 30 22 14 6 - 29 21 13 5 28 20 12 4 27 19 11 3 OSC1EN 26 18 10 2 OSC0EN 25 17 9 1 MCSEL 24 16 8 0 • MCSEL: Main Clock Select 0: The slow clock is the source for the main clock 1: Oscillator 0 is source for the main clock 2: PLL0 is source for the main clock 3: Reserved • OSC0EN: Oscillator 0 Enable 0: Oscillator 0 is disabled 1: Oscillator 0 is enabled • OSC1EN: Oscillator 1 Enable 0: Oscillator 1is disabled 1: Oscillator 1is enabled 68 32058H–AVR32–03/09 AT32UC3A 13.6.2 Name: Access Type: Clock Select CKSEL Read/Write 31 PBBDIV 23 PBADIV 15 HSBDIV 7 CPUDIV 30 22 14 6 - 29 21 13 5 - 28 20 12 4 - 27 19 11 3 - 26 25 PBBSEL 24 18 17 PBASEL 16 10 9 HSBSEL 8 2 1 CPUSEL 0 • PBBDIV, PBBSEL: PBB Division and Clock Select PBBDIV = 0: PBB clock equals main clock. PBBDIV = 1: PBB clock equals main clock divided by 2(PBBSEL+1). • PBADIV, PBASEL: PBA Division and Clock Select PBADIV = 0: PBA clock equals main clock. PBADIV = 1: PBA clock equals main clock divided by 2(PBASEL+1). • HSBDIV, HSBSEL: HSB Division and Clock Select For the AT32UC3A, HSBDIV always equals CPUDIV, and HSBSEL always equals CPUSEL, as the HSB clock is always equal to the CPU clock. • CPUDIV, CPUSEL: CPU Division and Clock Select CPUDIV = 0: CPU clock equals main clock. CPUDIV = 1: CPU clock equals main clock divided by 2(CPUSEL+1). Note that if xxxDIV is written to 0, xxxSEL should also be written to 0 to ensure correct operation. Also note that writing this register clears POSCSR:CKRDY. The register must not be re-written until CKRDY goes high. 69 32058H–AVR32–03/09 AT32UC3A 13.6.3 Name: Access Type: Clock Mask CPU/HSB/PBA/PBBMASK Read/Write 31 30 29 28 MASK[31:24] 27 26 25 24 23 22 21 20 MASK[23:16] 19 18 17 16 15 14 13 12 MASK[15:8] 11 10 9 8 7 6 5 4 MASK[7:0] 3 2 1 0 • MASK: Clock Mask If bit n is cleared, the clock for module n is stopped. If bit n is set, the clock for module n is enabled according to the current power mode. The number of implemented bits in each mask register, as well as which module clock is controlled by each bit, is shown in Table 13-5. Table 13-5. Bit 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Maskable module clocks in AT32UC3A. CPUMASK OCD HSBMASK FLASHC PBA bridge PBB bridge USBB MACB PDCA EBI PBAMASK INTC GPIO PDCA PM/RTC/EIC ADC SPI0 SPI1 TWI USART0 USART1 USART2 USART3 PWM SSC PBBMASK HMATRIX USBB FLASHC MACB SMC SDRAMC - 70 32058H–AVR32–03/09 AT32UC3A Table 13-5. Bit 14 15 16 Maskable module clocks in AT32UC3A. CPUMASK HSBMASK PBAMASK TC ABDAC PBBMASK - SYSTIMER (COMPARE/COUNT REGISTERS CLK) - 31: 17 - - - 71 32058H–AVR32–03/09 AT32UC3A 13.6.4 Name: Access Type: PLL Control PLL0,1 Read/Write 31 RESERVED 23 30 29 28 27 PLLCOUNT 26 25 24 22 RESERVED 21 20 19 18 PLLMUL 17 16 15 14 RESERVED 13 12 11 10 PLLDIV 9 8 7 - 6 - 5 - 4 3 PLLOPT 2 1 PLLOSC 0 PLLEN • RESERVED: Reserved bitfields Reserved for internal use. Always write to 0. • PLLCOUNT: PLL Count Specifies the number of slow clock cycles before ISR:LOCKn will be set after PLLn has been written, or after PLLn has been automatically re-enabled after exiting a sleep mode. • PLLMUL: PLL Multiply Factor • PLLDIV: PLL Division Factor These bitfields determine the ratio of the PLL output frequency (voltage controlled oscillator frequency fVCO) to the source oscillator frequency: fVCO = (PLLMUL+1)/(PLLDIV) • fOSC if PLLDIV > 0. fVCO = 2*(PLLMUL+1) • fOSC if PLLDIV = 0. If PLLOPT[1] field is set to 0: fPLL = fVCO. If PLLOPT[1] field is set to 1: fPLL = fVCO / 2. Note that the MUL field cannot be equal to 0 or 1, or the behavior of the PLL will be undefined. • PLLOPT: PLL Option Select the operating range for the PLL. PLLOPT[0]: Select the VCO frequency range. PLLOPT[1]: Enable the extra output divider. PLLOPT[2]: Disable the Wide-Bandwidth mode (Wide-Bandwidth mode allows a faster startup time and out-of-lock time). 72 32058H–AVR32–03/09 AT32UC3A Table 13-6. PLLOPT Fields Description in AT32UC3A Description PLLOPT[0]: VCO frequency 0 1 PLLOPT[1]: Output divider 0 1 PLLOPT[2] 0 1 Wide Bandwidth Mode enabled Wide Bandwidth Mode disabled fPLL = fvco fPLL = fvco/2 160MHz bit MREAD = 1 Start the transfer TWI_CR = START | STOP Read status register RXRDY = 1? Yes Read Receive Holding Register No Read Status register No TXCOMP = 1? Yes END 232 32058H–AVR32–03/09 AT32UC3A Figure 24-17. TWI Read Operation with Single Data Byte and Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: - Master enable TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (IADRSZ) - Transfer direction bit Read ==> bit MREAD = 1 Set the internal address TWI_IADR = address Start the transfer TWI_CR = START | STOP Read Status register No RXRDY = 1? Yes Read Receive Holding register Read Status register No TXCOMP = 1? Yes END 233 32058H–AVR32–03/09 AT32UC3A Figure 24-18. TWI Read Operation with Multiple Data Bytes with or without Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: - Master enable TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Read ==> bit MREAD = 1 Internal address size = 0? Set the internal address TWI_IADR = address Yes Start the transfer TWI_CR = START Read Status register RXRDY = 1? Yes Read Receive Holding register (TWI_RHR) No No Last data to read but one? Yes Stop the transfer TWI_CR = STOP Read Status register No RXRDY = 1? Yes Read Receive Holding register (TWI_RHR) Read status register TXCOMP = 1? Yes END No 234 32058H–AVR32–03/09 AT32UC3A 24.12 Multi-master Mode 24.12.1 Definition More than one master may handle the bus at the same time without data corruption by using arbitration. Arbitration starts as soon as two or more masters place information on the bus at the same time, and stops (arbitration is lost) for the master that intends to send a logical one while the other master sends a logical zero. As soon as arbitration is lost by a master, it stops sending data and listens to the bus in order to detect a stop. When the stop is detected, the master who has lost arbitration may put its data on the bus by respecting arbitration. Arbitration is illustrated in Figure 24-20 on page 236. 24.12.2 Different Multi-master Modes Two multi-master modes may be distinguished: 1. TWI is considered as a Master only and will never be addressed. 2. TWI may be either a Master or a Slave and may be addressed. Note: Arbitration is supported in both Multi-master modes. 24.12.2.1 TWI as Master Only In this mode, TWI is considered as a Master only (MSEN is always at one) and must be driven like a Master with the ARBLST (ARBitration Lost) flag in addition. If arbitration is lost (ARBLST = 1), the programmer must reinitiate the data transfer. If the user starts a transfer (ex.: DADR + START + W + Write in THR) and if the bus is busy, the TWI automatically waits for a STOP condition on the bus to initiate the transfer (see Figure 2419 on page 236). Note: The state of the bus (busy or free) is not indicated in the user interface. 24.12.2.2 TWI as Master or Slave The automatic reversal from Master to Slave is not supported in case of a lost arbitration. Then, in the case where TWI may be either a Master or a Slave, the programmer must manage the pseudo Multi-master mode described in the steps below. 1. Program TWI in Slave mode (SADR + MSDIS + SVEN) and perform Slave Access (if TWI is addressed). 2. If TWI has to be set in Master mode, wait until TXCOMP flag is at 1. 3. Program Master mode (DADR + SVDIS + MSEN) and start the transfer (ex: START + Write in THR). 4. As soon as the Master mode is enabled, TWI scans the bus in order to detect if it is busy or free. When the bus is considered as free, TWI initiates the transfer. 5. As soon as the transfer is initiated and until a STOP condition is sent, the arbitration becomes relevant and the user must monitor the ARBLST flag. 6. If the arbitration is lost (ARBLST is set to 1), the user must program the TWI in Slave mode in the case where the Master that won the arbitration wanted to access the TWI. 235 32058H–AVR32–03/09 AT32UC3A 7. If TWI has to be set in Slave mode, wait until TXCOMP flag is at 1 and then program the Slave mode. Note: In the case where the arbitration is lost and TWI is addressed, TWI will not acknowledge even if it is programmed in Slave mode as soon as ARBLST is set to 1. Then, the Master must repeat SADR. Figure 24-19. Programmer Sends Data While the Bus is Busy TWCK STOP sent by the master TWD DATA sent by a master Bus is busy Bus is free TWI DATA transfer Transfer is kept START sent by the TWI DATA sent by the TWI A transfer is programmed (DADR + W + START + Write THR) Bus is considered as free Transfer is initiated Figure 24-20. Arbitration Cases TWCK TWD TWCK Data from a Master Data from TWI TWD S S S 1 1 1 0 0 11 0 1 Arbitration is lost TWI stops sending data P S S 1 1 1 0 1 Arbitration is lost The master stops sending data 0 01 0 01 1 1 Data from the TWI 00 11 Data from the master P S ARBLST Bus is busy Bus is free TWI DATA transfer A transfer is programmed (DADR + W + START + Write THR) Transfer is stopped Transfer is kept Transfer is programmed again (DADR + W + START + Write THR) Bus is considered as free Transfer is initiated The flowchart shown in Figure 24-21 on page 237 gives an example of read and write operations in Multi-master mode. 236 32058H–AVR32–03/09 AT32UC3A Figure 24-21. Multi-master Flowchart START Programm the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? Yes GACC = 1 ? SVREAD = 0 ? EOSACC = 1 ? Yes TXCOMP = 1 ? Yes Yes TXRDY= 1 ? Yes Write in TWI_THR RXRDY= 0 ? Yes Read TWI_RHR GENERAL CALL TREATMENT Need to perform a master access ? Yes Decoding of the programming sequence Prog seq OK ? Change SADR Program the Master mode DADR + SVDIS + MSEN + CLK + R / W Read Status Register Yes ARBLST = 1 ? Yes Yes RXRDY= 0 ? MREAD = 1 ? TXRDY= 0 ? Yes Read TWI_RHR Yes Data to read? Data to send ? Yes Write in TWI_THR Stop transfer Read Status Register Yes TXCOMP = 0 ? 237 32058H–AVR32–03/09 AT32UC3A 24.13 Slave Mode 24.13.1 Definition The Slave Mode is defined as a mode where the device receives the clock and the address from another device called the master. In this mode, the device never initiates and never completes the transmission (START, REPEATED_START and STOP conditions are always provided by the master). 24.13.2 Application Block Diagram Figure 24-22. Slave Mode Typical Application Block Diagram VDD R TWD TWCK R Master Host with TWI Interface Host with TWI Interface Slave 1 Host with TWI Interface Slave 2 LCD Controller Slave 3 24.13.3 Programming Slave Mode The following fields must be programmed before entering Slave mode: 1. SADR (SMR): The slave device address is used in order to be accessed by master devices in read or write mode. 2. MSDIS (CR): Disable the master mode. 3. SVEN (CR): Enable the slave mode. As the device receives the clock, values written in CWGR are not taken into account. 24.13.4 Receiving Data After a Start or Repeated Start condition is detected and if the address sent by the Master matches with the Slave address programmed in the SADR (Slave ADdress) field, SVACC (Slave ACCess) flag is set and SVREAD (Slave READ) indicates the direction of the transfer. SVACC remains high until a STOP condition or a repeated START is detected. When such a condition is detected, EOSACC (End Of Slave ACCess) flag is set. 24.13.4.1 Read Sequence In the case of a Read sequence (SVREAD is high), TWI transfers data written in the THR (TWI Transmit Holding Register) until a STOP condition or a REPEATED_START + an address different from SADR is detected. Note that at the end of the read sequence TXCOMP (Transmission Complete) flag is set and SVACC reset. 238 32058H–AVR32–03/09 AT32UC3A As soon as data is written in the THR, TXRDY (Transmit Holding Register Ready) flag is reset, and it is set when the shift register is empty and the sent data acknowledged or not. If the data is not acknowledged, the NACK flag is set. Note that a STOP or a repeated START always follows a NACK. See Figure 24-23 on page 240. 24.13.4.2 Write Sequence In the case of a Write sequence (SVREAD is low), the RXRDY (Receive Holding Register Ready) flag is set as soon as a character has been received in the RHR (TWI Receive Holding Register). RXRDY is reset when reading the RHR. TWI continues receiving data until a STOP condition or a REPEATED_START + an address different from SADR is detected. Note that at the end of the write sequence TXCOMP flag is set and SVACC reset. See Figure 24-24 on page 241. 24.13.4.3 Clock Synchronization Sequence In the case where THR or RHR is not written/read in time, TWI performs a clock synchronization. Clock stretching information is given by the SCLWS (Clock Wait state) bit. See Figure 24-26 on page 242 and Figure 24-27 on page 243. 24.13.4.4 General Call In the case where a GENERAL CALL is performed, GACC (General Call ACCess) flag is set. After GACC is set, it is up to the programmer to interpret the meaning of the GENERAL CALL and to decode the new address programming sequence. See Figure 24-25 on page 241. 24.13.4.5 PDC As it is impossible to know the exact number of data to receive/send, the use of PDC is NOT recommended in SLAVE mode. 239 32058H–AVR32–03/09 AT32UC3A As it is impossible to know the exact number of data to receive/send, the use of PDC is NOT recommended in SLAVE mode. 24.13.5 24.13.5.1 Data Transfer Read Operation The read mode is defined as a data requirement from the master. After a START or a REPEATED START condition is detected, the decoding of the address starts. If the slave address (SADR) is decoded, SVACC is set and SVREAD indicates the direction of the transfer. Until a STOP or REPEATED START condition is detected, TWI continues sending data loaded in the THR register. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 24-23 on page 240 describes the write operation. Figure 24-23. Read Access Ordered by a MASTER SADR does not match, TWI answers with a NACK SADR matches, TWI answers with an ACK ACK/NACK from the Master A DATA NA S/Sr TWD TXRDY NACK SVACC SVREAD EOSVACC S ADR R NA DATA NA P/S/Sr SADR R A DATA A Write THR Read RHR SVREAD has to be taken into account only while SVACC is active Notes: 1. When SVACC is low, the state of SVREAD becomes irrelevant. 2. TXRDY is reset when data has been transmitted from THR to the shift register and set when this data has been acknowledged or non acknowledged. 24.13.5.2 Write Operation The write mode is defined as a data transmission from the master. After a START or a REPEATED START, the decoding of the address starts. If the slave address is decoded, SVACC is set and SVREAD indicates the direction of the transfer (SVREAD is low in this case). Until a STOP or REPEATED START condition is detected, TWI stores the received data in the RHR register. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 24-24 on page 241 describes the Write operation. 240 32058H–AVR32–03/09 AT32UC3A Figure 24-24. Write Access Ordered by a Master SADR does not match, TWI answers with a NACK SADR matches, TWI answers with an ACK Read RHR TWD RXRDY SVACC SVREAD EOSVACC S ADR W NA DATA NA P/S/Sr SADR W A DATA A A DATA NA S/Sr SVREAD has to be taken into account only while SVACC is active Notes: 1. When SVACC is low, the state of SVREAD becomes irrelevant. 2. RXRDY is set when data has been transmitted from the shift register to the RHR and reset when this data is read. 24.13.5.3 General Call The general call is performed in order to change the address of the slave. If a GENERAL CALL is detected, GACC is set. After the detection of General Call, it is up to the programmer to decode the commands which come afterwards. In case of a WRITE command, the programmer has to decode the programming sequence and program a new SADR if the programming sequence matches. Figure 24-25 on page 241 describes the General Call access. Figure 24-25. Master Performs a General Call 0000000 + W RESET command = 00000110X WRITE command = 00000100X TXD S GENERAL CALL A Reset or write DADD A DATA1 A DATA2 A New SADR A P New SADR Programming sequence GCACC Reset after read SVACC Note: 1. This method allows the user to create an own programming sequence by choosing the programming bytes and the number of them. The programming sequence has to be provided to the master. 241 32058H–AVR32–03/09 AT32UC3A 24.13.6 Clock Synchronization In both read and write modes, it may happen that THR/RHR buffer is not filled /emptied before the emission/reception of a new character. In this case, to avoid sending/receiving undesired data, a clock stretching mechanism is implemented. 24.13.6.1 Clock Synchronization in Read Mode The clock is tied low if the shift register is empty and if a STOP or REPEATED START condition was not detected. It is tied low until the shift register is loaded. Figure 24-26 on page 242 describes the clock synchronization in Read mode. Figure 24-26. Clock Synchronization in Read Mode TWI_THR DATA0 1 DATA1 DATA2 S SADR R A DATA0 A DATA1 A XXXXXXX 2 DATA2 NA S TWCK Write THR CLOCK is tied low by the TWI as long as THR is empty SCLWS TXRDY SVACC SVREAD TXCOMP As soon as a START is detected TWI_THR is transmitted to the shift register 1 2 The data is memorized in TWI_THR until a new value is written Ack or Nack from the master The clock is stretched after the ACK, the state of TWD is undefined during clock stretching Notes: 1. TXRDY is reset when data has been written in the TH to the shift register and set when this data has been acknowledged or non acknowledged. 2. At the end of the read sequence, TXCOMP is set after a STOP or after a REPEATED_START + an address different from SADR. 3. SCLWS is automatically set when the clock synchronization mechanism is started. 242 32058H–AVR32–03/09 AT32UC3A 24.13.6.2 Clock Synchronization in Write Mode The clock is tied low if the shift register and the RHR is full. If a STOP or REPEATED_START condition was not detected, it is tied low until RHR is read. Figure 24-27 on page 243 describes the clock synchronization in Read mode. Figure 24-27. Clock Synchronization in Write Mode TWCK CLOCK is tied low by the TWI as long as RHR is full TWD S SADR W A DATA0 A DATA1 A DATA2 NA S ADR TWI_RHR SCLWS DATA0 is not read in the RHR DATA1 DATA2 SCL is stretched on the last bit of DATA1 RXRDY Rd DATA0 SVACC SVREAD TXCOMP As soon as a START is detected Rd DATA1 Rd DATA2 Notes: 1. At the end of the read sequence, TXCOMP is set after a STOP or after a REPEATED_START + an address different from SADR. 2. SCLWS is automatically set when the clock synchronization mechanism is started and automatically reset when the mechanism is finished. 243 32058H–AVR32–03/09 AT32UC3A 24.13.7 24.13.7.1 Reversal after a Repeated Start Reversal of Read to Write The master initiates the communication by a read command and finishes it by a write command. Figure 24-28 on page 244 describes the repeated start + reversal from Read to Write mode. Figure 24-28. Repeated Start + Reversal from Read to Write Mode TWI_THR DATA0 DATA1 TWD S SADR R A DATA0 A DATA1 NA Sr SADR W A DATA2 A DATA3 A DATA3 P TWI_RHR SVACC SVREAD TXRDY RXRDY EOSACC TXCOMP As soon as a START is detected DATA2 Cleared after read 1. TXCOMP is only set at the end of the transmission because after the repeated start, SADR is detected again. 24.13.7.2 Reversal of Write to Read The master initiates the communication by a write command and finishes it by a read command.Figure 24-29 on page 244 describes the repeated start + reversal from Write to Read mode. Figure 24-29. Repeated Start + Reversal from Write to Read Mode TWI_THR DATA2 DATA3 TWD TWI_RHR SVACC SVREAD TXRDY RXRDY EOSACC TXCOMP S SADR W A DATA0 A DATA1 A Sr SADR R A DATA2 A DATA3 NA P DATA0 DATA1 Read TWI_RHR As soon as a START is detected Cleared after read Notes: 1. In this case, if THR has not been written at the end of the read command, the clock is automatically stretched before the ACK. 2. TXCOMP is only set at the end of the transmission because after the repeated start, SADR is detected again. 244 32058H–AVR32–03/09 AT32UC3A 24.13.8 Read Write Flowcharts The flowchart shown in Figure 24-30 on page 245 gives an example of read and write operations in Slave mode. A polling or interrupt method can be used to check the status bits. The interrupt method requires that the interrupt enable register (IER) be configured first. Figure 24-30. Read Write Flowchart in Slave Mode Set the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? GACC = 1 ? SVREAD = 0 ? EOSACC = 1 ? TXRDY= 1 ? Write in TWI_THR TXCOMP = 1 ? RXRDY= 0 ? END Read TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? Change SADR 245 32058H–AVR32–03/09 AT32UC3A 24.14 Two-wire Interface (TWI) User Interface 24.14.1 Register Mapping TWI User Interface Register Control Register Master Mode Register Slave Mode Register Internal Address Register Clock Waveform Generator Register Status Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register Receive Holding Register Transmit Holding Register Reserved Version Register Reserved Name CR MMR SMR IADR CWGR SR IER IDR IMR RHR THR – TWI_VER – Access Write-only Read-write Read-write Read-write Read-write Read-only Write-only Write-only Read-only Read-only Write-only – Read-only – Reset N/A 0x00000000 0x00000000 0x00000000 0x00000000 0x0000F009 N/A N/A 0x00000000 0x00000000 0x00000000 – 0x00000000(1) – Table 24-4. Offset 0x00 0x04 0x08 0x0C 0x10 0x20 0x24 0x28 0x2C 0x30 0x34 0x38 - 0xF8 0xFC 0x38 - 0xFC Note: 1. Values in the Version Register vary with the version of the IP block implementation. 24.14.2 Name: Access: TWI Control Register CR Write-only Reset Value: 0x00000000 31 – 23 – 15 – 7 SWRST 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 SVDIS 28 – 20 – 12 – 4 SVEN 27 – 19 – 11 – 3 MSDIS 26 – 18 – 10 – 2 MSEN 25 – 17 – 9 – 1 STOP 24 – 16 – 8 – 0 START • START: Send a START Condition 0 = No effect. 1 = A frame beginning with a START bit is transmitted according to the features defined in the mode register. 246 32058H–AVR32–03/09 AT32UC3A This action is necessary when the TWI peripheral wants to read data from a slave. When configured in Master Mode with a write operation, a frame is sent as soon as the user writes a character in the Transmit Holding Register (THR). • STOP: Send a STOP Condition 0 = No effect. 1 = STOP Condition is sent just after completing the current byte transmission in master read mode. - In single data byte master read, the START and STOP must both be set. - In multiple data bytes master read, the STOP must be set after the last data received but one. - In master read mode, if a NACK bit is received, the STOP is automatically performed. - In multiple data write operation, when both THR and shift register are empty, a STOP condition is automatically sent. • MSEN: TWI Master Mode Enabled 0 = No effect. 1 = If MSDIS = 0, the master mode is enabled. Note: Switching from Slave to Master mode is only permitted when TXCOMP = 1. • MSDIS: TWI Master Mode Disabled 0 = No effect. 1 = The master mode is disabled, all pending data is transmitted. The shifter and holding characters (if it contains data) are transmitted in case of write operation. In read operation, the character being transferred must be completely received before disabling. • SVEN: TWI Slave Mode Enabled 0 = No effect. 1 = If SVDIS = 0, the slave mode is enabled. Note: Switching from Master to Slave mode is only permitted when TXCOMP = 1. • SVDIS: TWI Slave Mode Disabled 0 = No effect. 1 = The slave mode is disabled. The shifter and holding characters (if it contains data) are transmitted in case of read operation. In write operation, the character being transferred must be completely received before disabling. • SWRST: Software Reset 0 = No effect. 1 = Equivalent to a system reset. 247 32058H–AVR32–03/09 AT32UC3A 24.14.3 Name: Access: TWI Master Mode Register MMR Read-write Reset Value: 0x00000000 31 – 23 – 15 – 7 – 30 – 22 29 – 21 28 – 20 27 – 19 DADR 11 – 3 – 26 – 18 25 – 17 24 – 16 14 – 6 – 13 – 5 – 12 MREAD 4 – 10 – 2 – 9 IADRSZ 1 – 8 0 – • IADRSZ: Internal Device Address Size IADRSZ[9:8] 0 0 1 1 0 1 0 1 Description No internal device address One-byte internal device address Two-byte internal device address Three-byte internal device address • MREAD: Master Read Direction 0 = Master write direction. 1 = Master read direction. • DADR: Device Address The device address is used to access slave devices in read or write mode. Those bits are only used in Master mode. 248 32058H–AVR32–03/09 AT32UC3A 24.14.4 Name: Access: TWI Slave Mode Register SMR Read-write Reset Value: 0x00000000 31 – 23 – 15 – 7 – 30 – 22 29 – 21 28 – 20 27 – 19 SADR 11 – 3 – 26 – 18 25 – 17 24 – 16 14 – 6 – 13 – 5 – 12 – 4 – 10 – 2 – 9 8 1 – 0 – • SADR: Slave Address The slave device address is used in Slave mode in order to be accessed by master devices in read or write mode. SADR must be programmed before enabling the Slave mode or after a general call. Writes at other times have no effect. 249 32058H–AVR32–03/09 AT32UC3A 24.14.5 Name: Access: TWI Internal Address Register IADR Read-write Reset Value: 0x00000000 31 – 23 30 – 22 29 – 21 28 – 20 IADR 15 14 13 12 IADR 7 6 5 4 IADR 3 2 1 0 11 10 9 8 27 – 19 26 – 18 25 – 17 24 – 16 • IADR: Internal Address 0, 1, 2 or 3 bytes depending on IADRSZ. 250 32058H–AVR32–03/09 AT32UC3A 24.14.6 Name: Access: TWI Clock Waveform Generator Register CWGR Read-write Reset Value: 0x00000000 31 – 23 30 – 22 29 – 21 28 – 20 27 – 19 26 – 18 25 – 17 CKDIV 9 24 – 16 15 14 13 12 CHDIV 11 10 8 7 6 5 4 CLDIV 3 2 1 0 CWGR is only used in Master mode. • CLDIV: Clock Low Divider The SCL low period is defined as follows: T low = ( ( CLDIV × 2 CKDIV ) + 4 ) × T MCK • CHDIV: Clock High Divider The SCL high period is defined as follows: T high = ( ( CHDIV × 2 CKDIV ) + 4 ) × T MCK • CKDIV: Clock Divider The CKDIV is used to increase both SCL high and low periods. 251 32058H–AVR32–03/09 AT32UC3A 24.14.7 Name: Access: TWI Status Register SR Read-only Reset Value: 0x0000F009 31 – 23 – 15 TXBUFE 7 – 30 – 22 – 14 RXBUFF 6 OVRE 29 – 21 – 13 ENDTX 5 GACC 28 – 20 – 12 ENDRX 4 SVACC 27 – 19 – 11 EOSACC 3 SVREAD 26 – 18 – 10 SCLWS 2 TXRDY 25 – 17 – 9 ARBLST 1 RXRDY 24 – 16 – 8 NACK 0 TXCOMP • TXCOMP: Transmission Completed (automatically set / reset) TXCOMP used in Master mode: 0 = During the length of the current frame. 1 = When both holding and shifter registers are empty and STOP condition has been sent. TXCOMP behavior in Master mode can be seen in Figure 24-8 on page 225 and in Figure 24-10 on page 226. TXCOMP used in Slave mode: 0 = As soon as a Start is detected. 1 = After a Stop or a Repeated Start + an address different from SADR is detected. TXCOMP behavior in Slave mode can be seen in Figure 24-26 on page 242, Figure 24-27 on page 243, Figure 24-28 on page 244 and Figure 24-29 on page 244. • RXRDY: Receive Holding Register Ready (automatically set / reset) 0 = No character has been received since the last RHR read operation. 1 = A byte has been received in the RHR since the last read. RXRDY behavior in Master mode can be seen in Figure 24-10 on page 226. RXRDY behavior in Slave mode can be seen in Figure 24-24 on page 241, Figure 24-27 on page 243, Figure 24-28 on page 244 and Figure 24-29 on page 244. • TXRDY: Transmit Holding Register Ready (automatically set / reset) TXRDY used in Master mode: 0 = The transmit holding register has not been transferred into shift register. Set to 0 when writing into THR register. 1 = As soon as a data byte is transferred from THR to internal shifter or if a NACK error is detected, TXRDY is set at the same time as TXCOMP and NACK. TXRDY is also set when MSEN is set (enable TWI). TXRDY behavior in Master mode can be seen in Figure 24-8 on page 225. 252 32058H–AVR32–03/09 AT32UC3A TXRDY used in Slave mode: 0 = As soon as data is written in the THR, until this data has been transmitted and acknowledged (ACK or NACK). 1 = It indicates that the THR is empty and that data has been transmitted and acknowledged. If TXRDY is high and if a NACK has been detected, the transmission will be stopped. Thus when TRDY = NACK = 1, the programmer must not fill THR to avoid losing it. TXRDY behavior in Slave mode can be seen in Figure 24-23 on page 240, Figure 24-26 on page 242, Figure 24-28 on page 244 and Figure 24-29 on page 244. • SVREAD: Slave Read (automatically set / reset) This bit is only used in Slave mode. When SVACC is low (no Slave access has been detected) SVREAD is irrelevant. 0 = Indicates that a write access is performed by a Master. 1 = Indicates that a read access is performed by a Master. SVREAD behavior can be seen in Figure 24-23 on page 240, Figure 24-24 on page 241, Figure 24-28 on page 244 and Figure 24-29 on page 244. • SVACC: Slave Access (automatically set / reset) This bit is only used in Slave mode. 0 = TWI is not addressed. SVACC is automatically cleared after a NACK or a STOP condition is detected. 1 = Indicates that the address decoding sequence has matched (A Master has sent SADR). SVACC remains high until a NACK or a STOP condition is detected. SVACC behavior can be seen in Figure 24-23 on page 240, Figure 24-24 on page 241, Figure 24-28 on page 244 and Figure 24-29 on page 244. • GACC: General Call Access (clear on read) This bit is only used in Slave mode. 0 = No General Call has been detected. 1 = A General Call has been detected. After the detection of General Call, the programmer decoded the commands that follow and the programming sequence. GACC behavior can be seen in Figure 24-25 on page 241. • OVRE: Overrun Error (clear on read) This bit is only used in Master mode. 0 = RHR has not been loaded while RXRDY was set 1 = RHR has been loaded while RXRDY was set. Reset by read in SR when TXCOMP is set. • NACK: Not Acknowledged (clear on read) NACK used in Master mode: 0 = Each data byte has been correctly received by the far-end side TWI slave component. 1 = A data byte has not been acknowledged by the slave component. Set at the same time as TXCOMP. 253 32058H–AVR32–03/09 AT32UC3A NACK used in Slave Read mode: 0 = Each data byte has been correctly received by the Master. 1 = In read mode, a data byte has not been acknowledged by the Master. When NACK is set the programmer must not fill THR even if TXRDY is set, because it means that the Master will stop the data transfer or re initiate it. Note that in Slave Write mode all data are acknowledged by the TWI. • ARBLST: Arbitration Lost (clear on read) This bit is only used in Master mode. 0 = Arbitration won. 1 = Arbitration lost. Another master of the TWI bus has won the multi-master arbitration. TXCOMP is set at the same time. • SCLWS: Clock Wait State (automatically set / reset) This bit is only used in Slave mode. 0 = The clock is not stretched. 1 = The clock is stretched. THR / RHR buffer is not filled / emptied before the emission / reception of a new character. SCLWS behavior can be seen in Figure 24-26 on page 242 and Figure 24-27 on page 243. • EOSACC: End Of Slave Access (clear on read) This bit is only used in Slave mode. 0 = A slave access is being performing. 1 = The Slave Access is finished. End Of Slave Access is automatically set as soon as SVACC is reset. EOSACC behavior can be seen in Figure 24-28 on page 244 and Figure 24-29 on page 244 • ENDRX: End of RX buffer This bit is only used in Master mode. 0 = The Receive Counter Register has not reached 0 since the last write in RCR or RNCR. 1 = The Receive Counter Register has reached 0 since the last write in RCR or RNCR. • ENDTX: End of TX buffer This bit is only used in Master mode. 0 = The Transmit Counter Register has not reached 0 since the last write in TCR or TNCR. 1 = The Transmit Counter Register has reached 0 since the last write in TCR or TNCR. • RXBUFF: RX Buffer Full This bit is only used in Master mode. 0 = RCR or RNCR have a value other than 0. 1 = Both RCR and RNCR have a value of 0. • TXBUFE: TX Buffer Empty This bit is only used in Master mode. 0 = TCR or TNCR have a value other than 0. 254 32058H–AVR32–03/09 AT32UC3A 1 = Both TCR and TNCR have a value of 0. 24.14.8 Name: Access: TWI Interrupt Enable Register IER Write-only Reset Value: 0x00000000 31 – 23 – 15 TXBUFE 7 – 30 – 22 – 14 RXBUFF 6 OVRE 29 – 21 – 13 ENDTX 5 GACC 28 – 20 – 12 ENDRX 4 SVACC 27 – 19 – 11 EOSACC 3 – 26 – 18 – 10 SCL_WS 2 TXRDY 25 – 17 – 9 ARBLST 1 RXRDY 24 – 16 – 8 NACK 0 TXCOMP • TXCOMP: Transmission Completed Interrupt Enable • RXRDY: Receive Holding Register Ready Interrupt Enable • TXRDY: Transmit Holding Register Ready Interrupt Enable • SVACC: Slave Access Interrupt Enable • GACC: General Call Access Interrupt Enable • OVRE: Overrun Error Interrupt Enable • NACK: Not Acknowledge Interrupt Enable • ARBLST: Arbitration Lost Interrupt Enable • SCL_WS: Clock Wait State Interrupt Enable • EOSACC: End Of Slave Access Interrupt Enable • ENDRX: End of Receive Buffer Interrupt Enable • ENDTX: End of Transmit Buffer Interrupt Enable • RXBUFF: Receive Buffer Full Interrupt Enable • TXBUFE: Transmit Buffer Empty Interrupt Enable 0 = No effect. 255 32058H–AVR32–03/09 AT32UC3A 1 = Enables the corresponding interrupt. 24.14.9 Name: Access: TWI Interrupt Disable Register IDR Write-only Reset Value: 0x00000000 31 – 23 – 15 TXBUFE 7 – 30 – 22 – 14 RXBUFF 6 OVRE 29 – 21 – 13 ENDTX 5 GACC 28 – 20 – 12 ENDRX 4 SVACC 27 – 19 – 11 EOSACC 3 – 26 – 18 – 10 SCL_WS 2 TXRDY 25 – 17 – 9 ARBLST 1 RXRDY 24 – 16 – 8 NACK 0 TXCOMP • TXCOMP: Transmission Completed Interrupt Disable • RXRDY: Receive Holding Register Ready Interrupt Disable • TXRDY: Transmit Holding Register Ready Interrupt Disable • SVACC: Slave Access Interrupt Disable • GACC: General Call Access Interrupt Disable • OVRE: Overrun Error Interrupt Disable • NACK: Not Acknowledge Interrupt Disable • ARBLST: Arbitration Lost Interrupt Disable • SCL_WS: Clock Wait State Interrupt Disable • EOSACC: End Of Slave Access Interrupt Disable • ENDRX: End of Receive Buffer Interrupt Disable • ENDTX: End of Transmit Buffer Interrupt Disable • RXBUFF: Receive Buffer Full Interrupt Disable • TXBUFE: Transmit Buffer Empty Interrupt Disable 0 = No effect. 1 = Disables the corresponding interrupt. 256 32058H–AVR32–03/09 AT32UC3A 24.14.10 TWI Interrupt Mask Register Name: Access: IMR Read-only Reset Value: 0x00000000 31 – 23 – 15 TXBUFE 7 – 30 – 22 – 14 RXBUFF 6 OVRE 29 – 21 – 13 ENDTX 5 GACC 28 – 20 – 12 ENDRX 4 SVACC 27 – 19 – 11 EOSACC 3 – 26 – 18 – 10 SCL_WS 2 TXRDY 25 – 17 – 9 ARBLST 1 RXRDY 24 – 16 – 8 NACK 0 TXCOMP • TXCOMP: Transmission Completed Interrupt Mask • RXRDY: Receive Holding Register Ready Interrupt Mask • TXRDY: Transmit Holding Register Ready Interrupt Mask • SVACC: Slave Access Interrupt Mask • GACC: General Call Access Interrupt Mask • OVRE: Overrun Error Interrupt Mask • NACK: Not Acknowledge Interrupt Mask • ARBLST: Arbitration Lost Interrupt Mask • SCL_WS: Clock Wait State Interrupt Mask • EOSACC: End Of Slave Access Interrupt Mask • ENDRX: End of Receive Buffer Interrupt Mask • ENDTX: End of Transmit Buffer Interrupt Mask • RXBUFF: Receive Buffer Full Interrupt Mask • TXBUFE: Transmit Buffer Empty Interrupt Mask 0 = The corresponding interrupt is disabled. 1 = The corresponding interrupt is enabled. 24.14.11 TWI Receive Holding Register Name: RHR 257 32058H–AVR32–03/09 AT32UC3A Access: Read-only Reset Value: 0x00000000 31 – 23 – 15 – 7 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 RXDATA 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • RXDATA: Master or Slave Receive Holding Data 24.14.12 TWI Transmit Holding Register Name: Access: THR Read-write Reset Value: 0x00000000 31 – 23 – 15 – 7 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 TXDATA 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • TXDATA: Master or Slave Transmit Holding Data 258 32058H–AVR32–03/09 AT32UC3A 25. Synchronous Serial Controller (SSC) Rev: 3.0.0.2 25.1 Features • • • • • Provides Serial Synchronous Communication Links Used in Audio and Telecom Applications Contains an Independent Receiver and Transmitter and a Common Clock Divider Interfaced with Two PDCA Channels (DMA Access) to Reduce Processor Overhead Offers a Configurable Frame Sync and Data Length Receiver and Transmitter Can be Programmed to Start Automatically or on Detection of Different Events on the Frame Sync Signal • Receiver and Transmitter Include a Data Signal, a Clock Signal and a Frame Synchronization Signal 25.2 Overview The Atmel Synchronous Serial Controller (SSC) provides a synchronous communication link with external devices. It supports many serial synchronous communication protocols generally used in audio and telecom applications such as I2S, Short Frame Sync, Long Frame Sync, etc. The SSC contains an independent receiver and transmitter and a common clock divider. The receiver and the transmitter each interface with three signals: the TX_DATA/RX_DATA signal for data, the TX_CLOCK/RX_CLOCK signal for the clock and the TX_FRAME_SYNC/RX_FRAME_SYNC signal for the Frame Sync. The transfers can be programmed to start automatically or on different events detected on the Frame Sync signal. The SSC’s high-level of programmability and its two dedicated PDCA channels of up to 32 bits permit a continuous high bit rate data transfer without processor intervention. Featuring connection to two PDCA channels, the SSC permits interfacing with low processor overhead to the following: • CODEC’s in master or slave mode • DAC through dedicated serial interface, particularly I2S • Magnetic card reader 259 32058H–AVR32–03/09 AT32UC3A 25.3 Block Diagram Figure 25-1. Block Diagram High Speed Bus Peripheral Bus Bridge PDCA Peripheral Bus TX_FRAME_SYNC TX_CLOCK Power CLK_SSC Manager TX_DATA SSC Interface PIO RX_FRAME_SYNC RX_CLOCK Interrupt Control RX_DATA SSC Interrupt 25.4 Application Block Diagram Figure 25-2. Application Block Diagram Power Management SSC Serial AUDIO Codec Time Slot Frame Management Management Line Interface Interrupt Management Test Management OS or RTOS Driver 260 32058H–AVR32–03/09 AT32UC3A 25.5 I/O Lines Description I/O Lines Description Pin Description Receiver Frame Synchro Receiver Clock Receiver Data Transmitter Frame Synchro Transmitter Clock Transmitter Data Type Input/Output Input/Output Input Input/Output Input/Output Output Table 25-1. Pin Name RX_FRAME_SYNC RX_CLOCK RX_DATA TX_FRAME_SYNC TX_CLOCK TX_DATA 25.6 25.6.1 Product Dependencies I/O Lines The pins used for interfacing the compliant external devices may be multiplexed with PIO lines. Before using the SSC receiver, the PIO controller must be configured to dedicate the SSC receiver I/O lines to the SSC peripheral mode. Before using the SSC transmitter, the PIO controller must be configured to dedicate the SSC transmitter I/O lines to the SSC peripheral mode. 25.6.2 Power Management The SSC clock is generated by the power manager. Before using the SSC, the programmer must ensure that the SSC clock is enabled in the power manager. In the SSC description, Master Clock (CLK_SSC) is the bus clock of the peripheral bus to which the SSC is connected. 25.6.3 Interrupt The SSC interface has an interrupt line connected to the interrupt controller. Handling interrupts requires programming the interrupt controller before configuring the SSC. All SSC interrupts can be enabled/disabled configuring the SSC Interrupt mask register. Each pending and unmasked SSC interrupt will assert the SSC interrupt line. The SSC interrupt service routine can get the interrupt origin by reading the SSC interrupt status register. 25.7 Functional Description This chapter contains the functional description of the following: SSC Functional Block, Clock Management, Data format, Start, Transmitter, Receiver and Frame Sync. The receiver and transmitter operate separately. However, they can work synchronously by programming the receiver to use the transmit clock and/or to start a data transfer when transmission starts. Alternatively, this can be done by programming the transmitter to use the receive clock and/or to start a data transfer when reception starts. The transmitter and the receiver can be programmed to operate with the clock signals provided on either the TX_CLOCK or RX_CLOCK pins. This allows the SSC to support many slave-mode data transfers. The maximum clock speed allowed on the TX_CLOCK and RX_CLOCK pins is the master clock divided by 2. 261 32058H–AVR32–03/09 AT32UC3A Figure 25-3. SSC Functional Block Diagram Transmitter Clock Output Controller TX_CLOCK TX_CLOCK Input CLK_SSC Clock Divider RX clock TX_FRAME_SYNC RX_FRAME_SYNC Transmit Clock TX clock Controller Frame Sync Controller TX_FRAME_SYNC Start Selector TX_PDCA Transmit Shift Register Transmit Holding Register Transmit Sync Holding Register TX_DATA Peripheral Bus User Interface Load Shift Receiver Clock Output Controller RX_CLOCK RX_CLOCK Input TX clock TX_FRAME_SYNC RX_FRAME_SYNC Receive Clock RX clock Controller Frame Sync Controller RX_FRAME_SYNC Start Selector RX_PDCA Receive Shift Register Receive Holding Register Receive Sync Holding Register RX_DATA PDCA Interrupt Control Load Shift Interrupt Controller 25.7.1 Clock Management The transmitter clock can be generated by: • an external clock received on the TX_CLOCK I/O pad • the receiver clock • the internal clock divider The receiver clock can be generated by: • an external clock received on the RX_CLOCK I/O pad • the transmitter clock • the internal clock divider Furthermore, the transmitter block can generate an external clock on the TX_CLOCK I/O pad, and the receiver block can generate an external clock on the RX_CLOCK I/O pad. This allows the SSC to support many Master and Slave Mode data transfers. 262 32058H–AVR32–03/09 AT32UC3A 25.7.1.1 Clock Divider Figure 25-4. Divided Clock Block Diagram Clock Divider CMR CLK_SSC Divided Clock /2 12-bit Counter The Master Clock divider is determined by the 12-bit field DIV counter and comparator (so its maximal value is 4095) in the Clock Mode Register CMR, allowing a Master Clock division by up to 8190. The Divided Clock is provided to both the Receiver and Transmitter. When this field is programmed to 0, the Clock Divider is not used and remains inactive. When DIV is set to a value equal to or greater than 1, the Divided Clock has a frequency of Master Clock divided by 2 times DIV. Each level of the Divided Clock has a duration of the Master Clock multiplied by DIV. This ensures a 50% duty cycle for the Divided Clock regardless of whether the DIV value is even or odd. Figure 25-5. Divided Clock Generation Master Clock Divided Clock DIV = 1 Divided Clock Frequency = CLK_SSC/2 Master Clock Divided Clock DIV = 3 Divided Clock Frequency = CLK_SSC/6 Table 25-2. Maximum CLK_SSC / 2 Minimum CLK_SSC / 8190 25.7.1.2 Transmitter Clock Management The transmitter clock is generated from the receiver clock or the divider clock or an external clock scanned on the TX_CLOCK I/O pad. The transmitter clock is selected by the CKS field in TCMR (Transmit Clock Mode Register). Transmit Clock can be inverted independently by the CKI bits in TCMR. 263 32058H–AVR32–03/09 AT32UC3A The transmitter can also drive the TX_CLOCK I/O pad continuously or be limited to the actual data transfer. The clock output is configured by the TCMR register. The Transmit Clock Inversion (CKI) bits have no effect on the clock outputs. Programming the TCMR register to select TX_CLOCK pin (CKS field) and at the same time Continuous Transmit Clock (CKO field) might lead to unpredictable results. Figure 25-6. Transmitter Clock Management TX_CLOCK(pin) Clock Output MUX Receiver Clock Tri-state Controller Divider Clock CKO Data Transfer CKS INV MUX Tri-state Controller Transmitter Clock CKI CKG 25.7.1.3 Receiver Clock Management The receiver clock is generated from the transmitter clock or the divider clock or an external clock scanned on the RX_CLOCK I/O pad. The Receive Clock is selected by the CKS field in RCMR (Receive Clock Mode Register). Receive Clocks can be inverted independently by the CKI bits in RCMR. The receiver can also drive the RX_CLOCK I/O pad continuously or be limited to the actual data transfer. The clock output is configured by the RCMR register. The Receive Clock Inversion (CKI) bits have no effect on the clock outputs. Programming the RCMR register to select RX_CLOCK pin (CKS field) and at the same time Continuous Receive Clock (CKO field) can lead to unpredictable results. 264 32058H–AVR32–03/09 AT32UC3A Figure 25-7. Receiver Clock Management RX_CLOCK (pin) MUX Transmitter Clock Tri-state Controller Clock Output Divider Clock CKO Data Transfer CKS INV MUX Tri-state Controller Receiver Clock CKI CKG 25.7.1.4 Serial Clock Ratio Considerations The Transmitter and the Receiver can be programmed to operate with the clock signals provided on either the TX_CLOCK or RX_CLOCK pins. This allows the SSC to support many slave-mode data transfers. In this case, the maximum clock speed allowed on the RX_CLOCK pin is: – Master Clock divided by 2 if Receiver Frame Synchro is input – Master Clock divided by 3 if Receiver Frame Synchro is output In addition, the maximum clock speed allowed on the TX_CLOCK pin is: – Master Clock divided by 6 if Transmit Frame Synchro is input – Master Clock divided by 2 if Transmit Frame Synchro is output 25.7.2 Transmitter Operations A transmitted frame is triggered by a start event and can be followed by synchronization data before data transmission. The start event is configured by setting the Transmit Clock Mode Register (TCMR). See Section “25.7.4” on page 267. The frame synchronization is configured setting the Transmit Frame Mode Register (TFMR). See Section “25.7.5” on page 269. To transmit data, the transmitter uses a shift register clocked by the transmitter clock signal and the start mode selected in the TCMR. Data is written by the application to the THR register then transferred to the shift register according to the data format selected. When both the THR and the transmit shift register are empty, the status flag TXEMPTY is set in SR. When the Transmit Holding register is transferred in the Transmit shift register, the status flag TXRDY is set in SR and additional data can be loaded in the holding register. 265 32058H–AVR32–03/09 AT32UC3A Figure 25-8. Transmitter Block Diagram CR.TXEN SR.TXEN CR.TXDIS TFMR.DATDEF TCMR.STTDLY TFMR.FSDEN TFMR.DATNB 1 0 TX_DATA TX_FRAME_SYNC RX_FRAME_SYNC Transmitter Clock Start Selector TFMR.MSBF Transmit Shift Register TFMR.FSDEN TCMR.STTDLY TFMR.DATLEN THR 0 1 TSHR TFMR.FSLEN 25.7.3 Receiver Operations A received frame is triggered by a start event and can be followed by synchronization data before data transmission. The start event is configured setting the Receive Clock Mode Register (RCMR). See Section “25.7.4” on page 267. The frame synchronization is configured setting the Receive Frame Mode Register (RFMR). See Section “25.7.5” on page 269. The receiver uses a shift register clocked by the receiver clock signal and the start mode selected in the RCMR. The data is transferred from the shift register depending on the data format selected. When the receiver shift register is full, the SSC transfers this data in the holding register, the status flag RXRDY is set in SR and the data can be read in the receiver holding register. If another transfer occurs before read of the RHR register, the status flag OVERUN is set in SR and the receiver shift register is transferred in the RHR register. 266 32058H–AVR32–03/09 AT32UC3A Figure 25-9. Receiver Block Diagram R X _ C L O C K (p in ) MUX T ra n sm itte r C lo ck T ri-sta te C o n tro lle r C lo ck O u tp u t D ivid e r C lo ck CKO D a ta T ra n sfe r CKS IN V MUX T ri-sta te C o n tro lle r R e ce ive r C lo ck CKI CKG 25.7.4 Start The transmitter and receiver can both be programmed to start their operations when an event occurs, respectively in the Transmit Start Selection (START) field of TCMR and in the Receive Start Selection (START) field of RCMR. Under the following conditions the start event is independently programmable: • Continuous. In this case, the transmission starts as soon as a word is written in THR and the reception starts as soon as the Receiver is enabled. • Synchronously with the transmitter/receiver • On detection of a falling/rising edge on TX_FRAME_SYNC/RX_FRAME_SYNC • On detection of a low level/high level on TX_FRAME_SYNC/RX_FRAME_SYNC • On detection of a level change or an edge on TX_FRAME_SYNC/RX_FRAME_SYNC A start can be programmed in the same manner on either side of the Transmit/Receive Clock Register (RCMR/TCMR). Thus, the start could be on TX_FRAME_SYNC (Transmit) or RX_FRAME_SYNC (Receive). Moreover, the Receiver can start when data is detected in the bit stream with the Compare Functions. Detection on TX_FRAME_SYNC/RX_FRAME_SYNC input/output is done by the field FSOS of the Transmit/Receive Frame Mode Register (TFMR/RFMR). 267 32058H–AVR32–03/09 AT32UC3A Figure 25-10. Transmit Start Mode TX_CLOCK (Input) TX_FRAME_SYNC (Input) TX_DATA (Output) Start= Low Level on TX_FRAME_SYNC TX_DATA (Output) Start= Falling Edge on TX_FRAME_SYNC TX_DATA (Output) Start= High Level on TX_FRAME_SYNC TX_DATA (Output) Start= Rising Edge on TX_FRAME_SYNC TX_DATA (Output) Start= Level Change on TX_FRAME_SYNC TX_DATA (Output) Start= Any Edge on TX_FRAME_SYNC X B0 B1 STTDLY X B0 B1 STTDLY X B0 B1 STTDLY X B0 B1 STTDLY X B0 B1 B0 B1 STTDLY X B0 B1 B0 B1 STTDLY Figure 25-11. Receive Pulse/Edge Start Modes RX_CLOCK RX_FRAME_SYNC (Input) RX_DATA (Input) Start = Low Level on RX_FRAME_SYNC RX_DATA (Input) Start = Falling Edge on RX_FRAME_SYNC RX_DATA (Input) Start = High Level on RX_FRAME_SYNC RX_DATA (Input) Start = Rising Edge on RX_FRAME_SYNC RX_DATA (Input) Start = Level Change on RX_FRAME_SYNC RX_DATA (Input) Start = Any Edge on RX_FRAME_SYNC X B0 B1 B0 B1 STTDLY X X X STTDLY X B0 B1 STTDLY B0 B1 STTDLY B0 B1 STTDLY X B0 B1 B0 B1 STTDLY 268 32058H–AVR32–03/09 AT32UC3A 25.7.5 Frame Sync The Transmitter and Receiver Frame Sync pins, TX_FRAME_SYNC and RX_FRAME_SYNC, can be programmed to generate different kinds of frame synchronization signals. The Frame Sync Output Selection (FSOS) field in the Receive Frame Mode Register (RFMR) and in the Transmit Frame Mode Register (TFMR) are used to select the required waveform. • Programmable low or high levels during data transfer are supported. • Programmable high levels before the start of data transfers or toggling are also supported. If a pulse waveform is selected, the Frame Sync Length (FSLEN) field in RFMR and TFMR programs the length of the pulse, from 1 bit time up to 16 bit time. The periodicity of the Receive and Transmit Frame Sync pulse output can be programmed through the Period Divider Selection (PERIOD) field in RCMR and TCMR. 25.7.5.1 Frame Sync Data Frame Sync Data transmits or receives a specific tag during the Frame Sync signal. During the Frame Sync signal, the Receiver can sample the RX_DATA line and store the data in the Receive Sync Holding Register and the transmitter can transfer Transmit Sync Holding Register in the Shifter Register. The data length to be sampled/shifted out during the Frame Sync signal is programmed by the FSLEN field in RFMR/TFMR. Concerning the Receive Frame Sync Data operation, if the Frame Sync Length is equal to or lower than the delay between the start event and the actual data reception, the data sampling operation is performed in the Receive Sync Holding Register through the Receive Shift Register. The Transmit Frame Sync Operation is performed by the transmitter only if the bit Frame Sync Data Enable (FSDEN) in TFMR is set. If the Frame Sync length is equal to or lower than the delay between the start event and the actual data transmission, the normal transmission has priority and the data contained in the Transmit Sync Holding Register is transferred in the Transmit Register, then shifted out. 25.7.5.2 Frame Sync Edge Detection The Frame Sync Edge detection is programmed by the FSEDGE field in RFMR/TFMR. This sets the corresponding flags RXSYN/TXSYN in the SSC Status Register (SR) on frame synchro edge detection (signals RX_FRAME_SYNC/TX_FRAME_SYNC). 269 32058H–AVR32–03/09 AT32UC3A 25.7.6 Receive Compare Modes Figure 25-12. Receive Compare Modes RX_CLOCK RX_DATA (Input) CMP0 CMP1 CMP2 CMP3 Start Ignored B0 B1 B2 FSLEN Up to 16 Bits (4 in This Example) STTDLY DATLEN 25.7.6.1 Compare Functions Compare 0 can be one start event of the Receiver. In this case, the receiver compares at each new sample the last FSLEN bits received at the FSLEN lower bit of the data contained in the Compare 0 Register (RC0R). When this start event is selected, the user can program the Receiver to start a new data transfer either by writing a new Compare 0, or by receiving continuously until Compare 1 occurs. This selection is done with the bit (STOP) in RCMR. Data Format The data framing format of both the transmitter and the receiver are programmable through the Transmitter Frame Mode Register (TFMR) and the Receiver Frame Mode Register (RFMR). In either case, the user can independently select: • the event that starts the data transfer (START) • the delay in number of bit periods between the start event and the first data bit (STTDLY) • the length of the data (DATLEN) • the number of data to be transferred for each start event (DATNB). • the length of synchronization transferred for each start event (FSLEN) • the bit sense: most or lowest significant bit first (MSBF). Additionally, the transmitter can be used to transfer synchronization and select the level driven on the TX_DATA pin while not in data transfer operation. This is done respectively by the Frame Sync Data Enable (FSDEN) and by the Data Default Value (DATDEF) bits in TFMR. 25.7.7 270 32058H–AVR32–03/09 AT32UC3A Table 25-3. Transmitter TFMR TFMR TFMR TFMR TFMR TFMR TCMR TCMR Data Frame Registers Receiver RFMR RFMR RFMR RFMR Field DATLEN DATNB MSBF FSLEN DATDEF FSDEN RCMR RCMR PERIOD STTDLY Up to 512 Up to 255 Up to 16 0 or 1 Length Up to 32 Up to 16 Comment Size of word Number of words transmitted in frame Most significant bit first Size of Synchro data register Data default value ended Enable send TSHR Frame size Size of transmit start delay Figure 25-13. Transmit and Receive Frame Format in Edge/Pulse Start Modes Start PERIOD TX_FRAME_SYNC / (1) RX_FRAME_SYNC FSLEN TX_DATA (If FSDEN = 1) TX_DATA (If FSDEN = 0) Sync Data From TSHR Default From DATDEF Data From THR Data From THR Data To RHR DATLEN Data From THR Data From THR Data To RHR DATLEN Default From DATDEF Default From DATDEF Ignored Sync Data Sync Data Start Default From DATDEF RX_DATA Sync Data To RSHR Ignored STTDLY DATNB Note: 1. Example of input on falling edge of TX_FRAME_SYNC/RX_FRAME_SYNC. 271 32058H–AVR32–03/09 AT32UC3A Figure 25-14. Transmit Frame Format in Continuous Mode Start TX_DATA Data From THR DATLEN Data From THR DATLEN Default Start: 1. TXEMPTY set to 1 2. Write into the THR Note: 1. STTDLY is set to 0. In this example, THR is loaded twice. FSDEN value has no effect on the transmission. SyncData cannot be output in continuous mode. Figure 25-15. Receive Frame Format in Continuous Mode Start = Enable Receiver RX_DATA Data To RHR DATLEN Data To RHR DATLEN Note: 1. STTDLY is set to 0. 25.7.8 Loop Mode The receiver can be programmed to receive transmissions from the transmitter. This is done by setting the Loop Mode (LOOP) bit in RFMR. In this case, RX_DATA is connected to TX_DATA, RX_FRAME_SYNC is connected to TX_FRAME_SYNC and RX_CLOCK is connected to TX_CLOCK. 25.7.9 Interrupt Most bits in SR have a corresponding bit in interrupt management registers. The SSC can be programmed to generate an interrupt when it detects an event. The interrupt is controlled by writing IER (Interrupt Enable Register) and IDR (Interrupt Disable Register) These registers enable and disable, respectively, the corresponding interrupt by setting and clearing the corresponding bit in IMR (Interrupt Mask Register), which controls the generation of interrupts by asserting the SSC interrupt line connected to the interrupt controller. 272 32058H–AVR32–03/09 AT32UC3A Figure 25-16. Interrupt Block Diagram IMR IER PDCA TXBUFE ENDTX Transmitter TXRDY TXEMPTY TXSYNC RXBUFF ENDRX Receiver RXRDY OVRUN RXSYNC Interrupt Control Set IDR Clear SSC Interrupt 25.8 SSC Application Examples The SSC can support several serial communication modes used in audio or high speed serial links. Some standard applications are shown in the following figures. All serial link applications supported by the SSC are not listed here. Figure 25-17. Audio Application Block Diagram Clock SCK TX_CLOCK Word Select WS TX_FRAME_SYNC Data SD TX_DATA SSC RX_DATA RX_FRAME_SYNC RX_CLOCK Clock SCK Word Select WS I2S RECEIVER Data SD MSB Left Channel LSB MSB Right Channel 273 32058H–AVR32–03/09 AT32UC3A Figure 25-18. Codec Application Block Diagram Serial Data Clock (SCLK) TX_CLOCK Frame sync (FSYNC) TX_FRAME_SYNC Serial Data Out TX_DATA SSC Serial Data In RX_DATA RX_FRAME_SYNC RX_CLOCK CODEC Serial Data Clock (SCLK) Frame sync (FSYNC) First Time Slot Dstart Serial Data Out Dend Serial Data In Figure 25-19. Time Slot Application Block Diagram SCLK TX_CLOCK FSYNC TX_FRAME_SYNC Data Out TX_DATA SSC RX_DATA RX_FRAME_SYNC RX_CLOCK Data in CODEC First Time Slot CODEC Second Time Slot Serial Data Clock (SCLK) Frame sync (FSYNC) Serial Data Out Serial Data In First Time Slot Dstart Second Time Slot Dend 274 32058H–AVR32–03/09 AT32UC3A 25.9 User Interface Register Mapping Register Control Register Clock Mode Register Reserved Reserved Receive Clock Mode Register Receive Frame Mode Register Transmit Clock Mode Register Transmit Frame Mode Register Receive Holding Register Transmit Holding Register Reserved Reserved Receive Sync. Holding Register Transmit Sync. Holding Register Receive Compare 0 Register Receive Compare 1 Register Status Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register Reserved Register Name CR CMR – – RCMR RFMR TCMR TFMR RHR THR – – RSHR TSHR RC0R RC1R SR IER IDR IMR – Access Write Read/Write – – Read/Write Read/Write Read/Write Read/Write Read Write – – Read Read/Write Read/Write Read/Write Read Write Write Read – Reset – 0x0 – – 0x0 0x0 0x0 0x0 0x0 – – – 0x0 0x0 0x0 0x0 0x000000CC – – 0x0 – Table 25-4. Offset 0x0 0x4 0x8 0xC 0x10 0x14 0x18 0x1C 0x20 0x24 0x28 0x2C 0x30 0x34 0x38 0x3C 0x40 0x44 0x48 0x4C 0x50-0xFC 275 32058H–AVR32–03/09 AT32UC3A 25.9.1 Name: Control Register CR Write-only 0x00 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 TXDIS 1 RXDIS 24 – 16 – 8 TXEN 0 RXEN Access Type: Offset: Reset value: 31 – 23 – 15 SWRST 7 – • SWRST: Software Reset 0: No effect. 1: Performs a software reset. Has priority on any other bit in CR. • TXDIS: Transmit Disable 0: No effect. 1: Disables Transmit. If a character is currently being transmitted, disables at end of current character transmission. • TXEN: Transmit Enable 0: No effect. 1: Enables Transmit if TXDIS is not set. • RXDIS: Receive Disable 0: No effect. 1: Disables Receive. If a character is currently being received, disables at end of current character reception. • RXEN: Receive Enable 0: No effect. 1: Enables Receive if RXDIS is not set. 276 32058H–AVR32–03/09 AT32UC3A 25.9.2 Name: Clock Mode Register CMR Read/Write 0x04 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 DIV 27 – 19 – 11 26 – 18 – 10 DIV 3 2 1 0 25 – 17 – 9 24 – 16 – 8 Access Type: Offset: Reset value: 31 – 23 – 15 – 7 • DIV: Clock Divider 0: The Clock Divider is not active. Any Other Value: The Divided Clock equals the Master Clock divided by 2 times DIV. The maximum bit rate is CLK_SSC/2. The minimum bit rate is CLK_SSC/2 x 4095 = CLK_SSC/8190. 277 32058H–AVR32–03/09 AT32UC3A 25.9.3 Name: Receive Clock Mode Register RCMR Read/Write 0x10 0x00000000 30 29 28 PERIOD 23 22 21 20 STTDLY 15 – 7 CKG 14 – 6 13 – 5 CKI 12 STOP 4 11 10 START 3 CKO 2 1 CKS 0 9 8 19 18 17 16 27 26 25 24 Access Type: Offset: Reset value: 31 • PERIOD: Receive Period Divider Selection This field selects the divider to apply to the selected Receive Clock in order to generate a new Frame Sync Signal. If 0, no PERIOD signal is generated. If not 0, a PERIOD signal is generated each 2 x (PERIOD+1) Receive Clock. • STTDLY: Receive Start Delay If STTDLY is not 0, a delay of STTDLY clock cycles is inserted between the start event and the actual start of reception. When the Receiver is programmed to start synchronously with the Transmitter, the delay is also applied. Note: It is very important that STTDLY be set carefully. If STTDLY must be set, it should be done in relation to TAG (Receive Sync Data) reception. • STOP: Receive Stop Selection 0: After completion of a data transfer when starting with a Compare 0, the receiver stops the data transfer and waits for a new compare 0. 1: After starting a receive with a Compare 0, the receiver operates in a continuous mode until a Compare 1 is detected. • START: Receive Start Selection START 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9-0xF Receive Start Continuous, as soon as the receiver is enabled, and immediately after the end of transfer of the previous data. Transmit start Detection of a low level on RX_FRAME_SYNC signal Detection of a high level on RX_FRAME_SYNC signal Detection of a falling edge on RX_FRAME_SYNC signal Detection of a rising edge on RX_FRAME_SYNC signal Detection of any level change on RX_FRAME_SYNC signal Detection of any edge on RX_FRAME_SYNC signal Compare 0 Reserved 278 32058H–AVR32–03/09 AT32UC3A • CKG: Receive Clock Gating Selection CKG 0x0 0x1 0x2 0x3 Receive Clock Gating None, continuous clock Receive Clock enabled only if RX_FRAME_SYNC Low Receive Clock enabled only if RX_FRAME_SYNC High Reserved • CKI: Receive Clock Inversion 0: The data inputs (Data and Frame Sync signals) are sampled on Receive Clock falling edge. The Frame Sync signal output is shifted out on Receive Clock rising edge. 1: The data inputs (Data and Frame Sync signals) are sampled on Receive Clock rising edge. The Frame Sync signal output is shifted out on Receive Clock falling edge. CKI affects only the Receive Clock and not the output clock signal. • CKO: Receive Clock Output Mode Selection CKO 0x0 0x1 0x2 0x3-0x7 Receive Clock Output Mode None Continuous Receive Clock Receive Clock only during data transfers Reserved RX_CLOCK pin Input-only Output Output • CKS: Receive Clock Selection CKS 0x0 0x1 0x2 0x3 Selected Receive Clock Divided Clock TX_CLOCK Clock signal RX_CLOCK pin Reserved 279 32058H–AVR32–03/09 AT32UC3A 25.9.4 Name: Receive Frame Mode Register RFMR Read/Write 0x14 0x00000000 30 FSLENHI 23 – 15 – 7 MSBF 22 21 FSOS 13 – 5 LOOP 20 29 28 27 – 19 26 – 18 FSLEN 12 – 4 11 10 DATNB 3 2 DATLEN 1 0 9 8 25 – 17 24 FSEDGE 16 Access Type: Offset: Reset value: 31 14 – 6 – • FSLENHI: Receive Frame Sync Length High part The four MSB of the FSLEN bitfield. • FSEDGE: Frame Sync Edge Detection Determines which edge on Frame Sync will generate the interrupt RXSYN in the SSC Status Register. FSEDGE 0x0 0x1 Frame Sync Edge Detection Positive Edge Detection Negative Edge Detection • FSOS: Receive Frame Sync Output Selection FSOS 0x0 0x1 0x2 0x3 0x4 0x5 0x6-0x7 Selected Receive Frame Sync Signal None Negative Pulse Positive Pulse Driven Low during data transfer Driven High during data transfer Toggling at each start of data transfer Reserved RX_FRAME_SYNC Pin Input-only Output Output Output Output Output Undefined • FSLEN: Receive Frame Sync Length This field defines the length of the Receive Frame Sync Signal and the number of bits sampled and stored in the Receive Sync Data Register. When this mode is selected by the START field in the Receive Clock Mode Register, it also determines the length of the sampled data to be compared to the Compare 0 or Compare 1 register. Note: The four most significant bits fo this bitfield are in the FSLENHI bitfield. Pulse length is equal to ({FSLENHI,FSLEN} + 1) Receive Clock periods. Thus, if {FSLENHI,FSLEN} is 0, the Receive Frame Sync signal is generated during one Receive Clock period. • DATNB: Data Number per Frame 280 32058H–AVR32–03/09 AT32UC3A This field defines the number of data words to be received after each transfer start, which is equal to (DATNB + 1). • MSBF: Most Significant Bit First 0: The lowest significant bit of the data register is sampled first in the bit stream. 1: The most significant bit of the data register is sampled first in the bit stream. • LOOP: Loop Mode 0: Normal operating mode. 1: RX_DATA is driven by TX_DATA, RX_FRAME_SYNC is driven by TX_FRAME_SYNC and TX_CLOCK drives RX_CLOCK. • DATLEN: Data Length 0: Forbidden value (1-bit data length not supported). Any other value: The bit stream contains DATLEN + 1 data bits. Moreover, it defines the transfer size performed by the PDCA assigned to the Receiver. If DATLEN is lower or equal to 7, data transfers are in bytes. If DATLEN is between 8 and 15 (included), half-words are transferred, and for any other value, 32-bit words are transferred. 281 32058H–AVR32–03/09 AT32UC3A 25.9.5 Name: Transmit Clock Mode Register TCMR Read/Write 0x18 0x00000000 30 29 28 PERIOD 23 22 21 20 STTDLY 15 – 7 CKG 14 – 6 13 – 5 CKI 12 – 4 11 10 START 3 CKO 2 1 CKS 0 9 8 19 18 17 16 27 26 25 24 Access Type: Offset: Reset value: 31 • PERIOD: Transmit Period Divider Selection This field selects the divider to apply to the selected Transmit Clock to generate a new Frame Sync Signal. If 0, no period signal is generated. If not 0, a period signal is generated at each 2 x (PERIOD+1) Transmit Clock. • STTDLY: Transmit Start Delay If STTDLY is not 0, a delay of STTDLY clock cycles is inserted between the start event and the actual start of transmission of data. When the Transmitter is programmed to start synchronously with the Receiver, the delay is also applied. Note: STTDLY must be set carefully. If STTDLY is too short in respect to TAG (Transmit Sync Data) emission, data is emitted instead of the end of TAG. • START: Transmit Start Selection START 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 - 0xF Transmit Start Continuous, as soon as a word is written in the THR Register (if Transmit is enabled), and immediately after the end of transfer of the previous data. Receive start Detection of a low level on TX_FRAME_SYNC signal Detection of a high level on TX_FRAME_SYNC signal Detection of a falling edge on TX_FRAME_SYNC signal Detection of a rising edge on TX_FRAME_SYNC signal Detection of any level change on TX_FRAME_SYNC signal Detection of any edge on TX_FRAME_SYNC signal Reserved 282 32058H–AVR32–03/09 AT32UC3A • CKG: Transmit Clock Gating Selection CKG 0x0 0x1 0x2 0x3 Transmit Clock Gating None, continuous clock Transmit Clock enabled only if TX_FRAME_SYNC Low Transmit Clock enabled only if TX_FRAME_SYNC High Reserved • CKI: Transmit Clock Inversion 0: The data outputs (Data and Frame Sync signals) are shifted out on Transmit Clock falling edge. The Frame sync signal input is sampled on Transmit clock rising edge. 1: The data outputs (Data and Frame Sync signals) are shifted out on Transmit Clock rising edge. The Frame sync signal input is sampled on Transmit clock falling edge. CKI affects only the Transmit Clock and not the output clock signal. • CKO: Transmit Clock Output Mode Selection CKO 0x0 0x1 0x2 0x3-0x7 Transmit Clock Output Mode None Continuous Transmit Clock Transmit Clock only during data transfers Reserved TX_CLOCK pin Input-only Output Output • CKS: Transmit Clock Selection CKS 0x0 0x1 0x2 0x3 Selected Transmit Clock Divided Clock RX_CLOCK Clock signal TX_CLOCK Pin Reserved 283 32058H–AVR32–03/09 AT32UC3A 25.9.6 Name: Transmit Frame Mode Register TFMR Read/Write 0x1C 0x00000000 30 FSLENHI 23 FSDEN 15 – 7 MSBF 22 21 FSOS 13 – 5 DATDEF 20 29 28 27 – 19 26 – 18 FSLEN 12 – 4 11 10 DATNB 3 2 DATLEN 1 0 9 8 25 – 17 24 FSEDGE 16 Access Type: Offset: Reset value: 31 14 – 6 – • FSLENHI: Transmit Frame Sync Length High part The four MSB of the FSLEN bitfield. • FSEDGE: Frame Sync Edge Detection Determines which edge on frame sync will generate the interrupt TXSYN (Status Register). FSEDGE 0x0 0x1 Frame Sync Edge Detection Positive Edge Detection Negative Edge Detection • FSDEN: Frame Sync Data Enable 0: The TX_DATA line is driven with the default value during the Transmit Frame Sync signal. 1: TSHR value is shifted out during the transmission of the Transmit Frame Sync signal. • FSOS: Transmit Frame Sync Output Selection FSOS 0x0 0x1 0x2 0x3 0x4 0x5 0x6-0x7 Selected Transmit Frame Sync Signal None Negative Pulse Positive Pulse Driven Low during data transfer Driven High during data transfer Toggling at each start of data transfer Reserved TX_FRAME_SYNC Pin Input-only Output Output Output Output Output Undefined • FSLEN: Transmit Frame Sync Length This field defines the length of the Transmit Frame Sync signal and the number of bits shifted out from the Transmit Sync Data Register if FSDEN is 1. Note: The four most significant bits fo this bitfield are in the FSLENHI bitfield. 284 32058H–AVR32–03/09 AT32UC3A Pulse length is equal to ({FSLENHI,FSLEN} + 1) Transmit Clock periods, i.e., the pulse length can range from 1 to 16 Transmit Clock periods. If {FSLENHI,FSLEN} is 0, the Transmit Frame Sync signal is generated during one Transmit Clock period. • DATNB: Data Number per frame This field defines the number of data words to be transferred after each transfer start, which is equal to (DATNB +1). • MSBF: Most Significant Bit First 0: The lowest significant bit of the data register is shifted out first in the bit stream. 1: The most significant bit of the data register is shifted out first in the bit stream. • DATDEF: Data Default Value This bit defines the level driven on the TX_DATA pin while out of transmission. Note that if the pin is defined as multi-drive by the PIO Controller, the pin is enabled only if the SCC TX_DATA output is 1. • DATLEN: Data Length 0: Forbidden value (1-bit data length not supported). Any other value: The bit stream contains DATLEN + 1 data bits. Moreover, it defines the transfer size performed by the PDCA assigned to the Transmit. If DATLEN is lower or equal to 7, data transfers are bytes, if DATLEN is between 8 and 15 (included), half-words are transferred, and for any other value, 32-bit words are transferred. 285 32058H–AVR32–03/09 AT32UC3A 25.9.7 Name: SSC Receive Holding Register RHR Read-only 0x20 0x00000000 30 29 28 RDAT 23 22 21 20 RDAT 15 14 13 12 RDAT 7 6 5 4 RDAT 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Access Type: Offset: Reset value: 31 • RDAT: Receive Data Right aligned regardless of the number of data bits defined by DATLEN in RFMR. 286 32058H–AVR32–03/09 AT32UC3A 25.9.8 Name: Transmit Holding Register THR Write-only 0x24 30 29 28 TDAT 23 22 21 20 TDAT 15 14 13 12 TDAT 7 6 5 4 TDAT 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Access Type: Offset: Reset value: 31 • TDAT: Transmit Data Right aligned regardless of the number of data bits defined by DATLEN in TFMR. 287 32058H–AVR32–03/09 AT32UC3A 25.9.9 Name: Receive Synchronization Holding Register RSHR Read-only 0x30 0x00000000 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 RSDAT 7 6 5 4 RSDAT 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Access Type: Offset: Reset value: 31 – 23 – 15 • RSDAT: Receive Synchronization Data 288 32058H–AVR32–03/09 AT32UC3A 25.9.10 Name: Transmit Synchronization Holding Register TSHR Read/Write 0x34 0x00000000 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 TSDAT 7 6 5 4 TSDAT 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Access Type: Offset: Reset value: 31 – 23 – 15 • TSDAT: Transmit Synchronization Data 289 32058H–AVR32–03/09 AT32UC3A 25.9.11 Name: Receive Compare 0 Register RC0R Read/Write 0x38 0x00000000 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 CP0 7 6 5 4 CP0 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Access Type: Offset: Reset value: 31 – 23 – 15 • CP0: Receive Compare Data 0 290 32058H–AVR32–03/09 AT32UC3A 25.9.12 Name: Receive Compare 1 Register RC1R Read/Write 0x3C 0x00000000 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 CP1 7 6 5 4 CP1 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Access Type: Offset: Reset value: 31 – 23 – 15 • CP1: Receive Compare Data 1 291 32058H–AVR32–03/09 AT32UC3A 25.9.13 Name: Status Register SR Read-only 0x40 0x000000CC 30 – 22 – 14 – 6 ENDRX 29 – 21 – 13 – 5 OVRUN 28 – 20 – 12 – 4 RXRDY 27 – 19 – 11 RXSYN 3 TXBUFE 26 – 18 – 10 TXSYN 2 ENDTX 25 – 17 RXEN 9 CP1 1 TXEMPTY 24 – 16 TXEN 8 CP0 0 TXRDY Access Type: Offset: Reset value: 31 – 23 – 15 – 7 RXBUFF • RXEN: Receive Enable 0: Receive is disabled. 1: Receive is enabled. • TXEN: Transmit Enable 0: Transmit is disabled. 1: Transmit is enabled. • RXSYN: Receive Sync 0: An Rx Sync has not occurred since the last read of the Status Register. 1: An Rx Sync has occurred since the last read of the Status Register. • TXSYN: Transmit Sync 0: A Tx Sync has not occurred since the last read of the Status Register. 1: A Tx Sync has occurred since the last read of the Status Register. • CP1: Compare 1 0: A compare 1 has not occurred since the last read of the Status Register. 1: A compare 1 has occurred since the last read of the Status Register. • CP0: Compare 0 0: A compare 0 has not occurred since the last read of the Status Register. 1: A compare 0 has occurred since the last read of the Status Register. • RXBUFF: Receive Buffer Full 0: RCR or RNCR have a value other than 0. 1: Both RCR and RNCR have a value of 0. • ENDRX: End of Reception 0: Data is written on the Receive Counter Register or Receive Next Counter Register. 292 32058H–AVR32–03/09 AT32UC3A 1: End of PDCA transfer when Receive Counter Register has arrived at zero. • OVRUN: Receive Overrun 0: No data has been loaded in RHR while previous data has not been read since the last read of the Status Register. 1: Data has been loaded in RHR while previous data has not yet been read since the last read of the Status Register. • RXRDY: Receive Ready 0: RHR is empty. 1: Data has been received and loaded in RHR. • TXBUFE: Transmit Buffer Empty 0: TCR or TNCR have a value other than 0. 1: Both TCR and TNCR have a value of 0. • ENDTX: End of Transmission 0: The register TCR has not reached 0 since the last write in TCR or TNCR. 1: The register TCR has reached 0 since the last write in TCR or TNCR. • TXEMPTY: Transmit Empty 0: Data remains in THR or is currently transmitted from TSR. 1: Last data written in THR has been loaded in TSR and last data loaded in TSR has been transmitted. • TXRDY: Transmit Ready 0: Data has been loaded in THR and is waiting to be loaded in the Transmit Shift Register (TSR). 1: THR is empty. 293 32058H–AVR32–03/09 AT32UC3A 25.9.14 Name: Interrupt Enable Register IER Write-only 0x44 30 – 22 – 14 – 6 ENDRX 29 – 21 – 13 – 5 OVRUN 28 – 20 – 12 – 4 RXRDY 27 – 19 – 11 RXSYN 3 TXBUFE 26 – 18 – 10 TXSYN 2 ENDTX 25 – 17 – 9 CP1 1 TXEMPTY 24 – 16 – 8 CP0 0 TXRDY Access Type: Offset: Reset value: 31 – 23 – 15 – 7 RXBUFF • RXSYN: Rx Sync Interrupt Enable 0: No effect. 1: Enables the Rx Sync Interrupt. • TXSYN: Tx Sync Interrupt Enable 0: No effect. 1: Enables the Tx Sync Interrupt. • CP1: Compare 1 Interrupt Enable 0: No effect. 1: Enables the Compare 1 Interrupt. • CP0: Compare 0 Interrupt Enable 0: No effect. 1: Enables the Compare 0 Interrupt. • RXBUFF: Receive Buffer Full Interrupt Enable 0: No effect. 1: Enables the Receive Buffer Full Interrupt. • ENDRX: End of Reception Interrupt Enable 0: No effect. 1: Enables the End of Reception Interrupt. • OVRUN: Receive Overrun Interrupt Enable 0: No effect. 1: Enables the Receive Overrun Interrupt. • RXRDY: Receive Ready Interrupt Enable 0: No effect. 294 32058H–AVR32–03/09 AT32UC3A 1: Enables the Receive Ready Interrupt. • TXBUFE: Transmit Buffer Empty Interrupt Enable 0: No effect. 1: Enables the Transmit Buffer Empty Interrupt • ENDTX: End of Transmission Interrupt Enable 0: No effect. 1: Enables the End of Transmission Interrupt. • TXEMPTY: Transmit Empty Interrupt Enable 0: No effect. 1: Enables the Transmit Empty Interrupt. • TXRDY: Transmit Ready Interrupt Enable 0: No effect. 1: Enables the Transmit Ready Interrupt. 295 32058H–AVR32–03/09 AT32UC3A 25.9.15 Name: Interrupt Disable Register IDR Write-only 0x48 30 – 22 – 14 – 6 ENDRX 29 – 21 – 13 – 5 OVRUN 28 – 20 – 12 – 4 RXRDY 27 – 19 – 11 RXSYN 3 TXBUFE 26 – 18 – 10 TXSYN 2 ENDTX 25 – 17 – 9 CP1 1 TXEMPTY 24 – 16 – 8 CP0 0 TXRDY Access Type: Offset: Reset value: 31 – 23 – 15 – 7 RXBUFF • RXSYN: Rx Sync Interrupt Enable 0: No effect. 1: Disables the Rx Sync Interrupt. • TXSYN: Tx Sync Interrupt Enable 0: No effect. 1: Disables the Tx Sync Interrupt. • CP1: Compare 1 Interrupt Disable 0: No effect. 1: Disables the Compare 1 Interrupt. • CP0: Compare 0 Interrupt Disable 0: No effect. 1: Disables the Compare 0 Interrupt. • RXBUFF: Receive Buffer Full Interrupt Disable 0: No effect. 1: Disables the Receive Buffer Full Interrupt. • ENDRX: End of Reception Interrupt Disable 0: No effect. 1: Disables the End of Reception Interrupt. • OVRUN: Receive Overrun Interrupt Disable 0: No effect. 1: Disables the Receive Overrun Interrupt. • RXRDY: Receive Ready Interrupt Disable 0: No effect. 296 32058H–AVR32–03/09 AT32UC3A 1: Disables the Receive Ready Interrupt. • TXBUFE: Transmit Buffer Empty Interrupt Disable 0: No effect. 1: Disables the Transmit Buffer Empty Interrupt. • ENDTX: End of Transmission Interrupt Disable 0: No effect. 1: Disables the End of Transmission Interrupt. • TXEMPTY: Transmit Empty Interrupt Disable 0: No effect. 1: Disables the Transmit Empty Interrupt. • TXRDY: Transmit Ready Interrupt Disable 0: No effect. 1: Disables the Transmit Ready Interrupt. 297 32058H–AVR32–03/09 AT32UC3A 25.9.16 Name: Interrupt Mask Register IMR Read-only 0x4C 0x00000000 30 – 22 – 14 – 6 ENDRX 29 – 21 – 13 – 5 OVRUN 28 – 20 – 12 – 4 RXRDY 27 – 19 – 11 RXSYN 3 TXBUFE 26 – 18 – 10 TXSYN 2 ENDTX 25 – 17 – 9 CP1 1 TXEMPTY 24 – 16 – 8 CP0 0 TXRDY Access Type: Offset: Reset value: 31 – 23 – 15 – 7 RXBUFF • RXSYN: Rx Sync Interrupt Mask 0: The Rx Sync Interrupt is disabled. 1: The Rx Sync Interrupt is enabled. • TXSYN: Tx Sync Interrupt Mask 0: The Tx Sync Interrupt is disabled. 1: The Tx Sync Interrupt is enabled. • CP1: Compare 1 Interrupt Mask 0: The Compare 1 Interrupt is disabled. 1: The Compare 1 Interrupt is enabled. • CP0: Compare 0 Interrupt Mask 0: The Compare 0 Interrupt is disabled. 1: The Compare 0 Interrupt is enabled. • RXBUFF: Receive Buffer Full Interrupt Mask 0: The Receive Buffer Full Interrupt is disabled. 1: The Receive Buffer Full Interrupt is enabled. • ENDRX: End of Reception Interrupt Mask 0: The End of Reception Interrupt is disabled. 1: The End of Reception Interrupt is enabled. • OVRUN: Receive Overrun Interrupt Mask 0: The Receive Overrun Interrupt is disabled. 1: The Receive Overrun Interrupt is enabled. • RXRDY: Receive Ready Interrupt Mask 0: The Receive Ready Interrupt is disabled. 298 32058H–AVR32–03/09 AT32UC3A 26. Universal Synchronous/Asynchronous Receiver/Transmitter (USART) Rev. 4.0.0.2 26.1 Features • Programmable Baud Rate Generator • 5- to 9-bit Full-duplex Synchronous or Asynchronous Serial Communications – 1, 1.5 or 2 Stop Bits in Asynchronous Mode or 1 or 2 Stop Bits in Synchronous Mode – Parity Generation and Error Detection – Framing Error Detection, Overrun Error Detection – MSB- or LSB-first – Optional Break Generation and Detection – By 8 or by 16 Over-sampling Receiver Frequency – Optional Hardware Handshaking RTS-CTS – Receiver Time-out and Transmitter Timeguard – Optional Multidrop Mode with Address Generation and Detection 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 SPI Mode – Master or Slave – Serial Clock Programmable Phase and Polarity – SPI Serial Clock (CLK) Frequency up to Internal Clock Frequency CLK_USART/4 Test Modes – Remote Loopback, Local Loopback, Automatic Echo Supports Connection of Two Peripheral DMA Controller Channels (PDC) – Offers Buffer Transfer without Processor Intervention • • • • • • 26.2 Overview The Universal Synchronous Asynchronous Receiver Transceiver (USART) provides one full duplex universal synchronous asynchronous serial link. Data frame format is widely programmable (data length, parity, number of stop bits) to support a maximum of standards. The receiver implements parity error, framing error and overrun error detection. The receiver time-out enables handling variable-length frames and the transmitter timeguard facilitates communications with slow remote devices. Multidrop communications are also supported through address bit handling in reception and transmission. The USART features three test modes: remote loopback, local loopback and automatic echo. The USART supports specific operating modes providing interfaces on RS485 and SPI buses, with ISO7816 T = 0 or T = 1 smart card slots and infrared transceivers. The hardware handshaking feature enables an out-of-band flow control by automatic management of the pins RTS and CTS. The USART supports the connection to the Peripheral DMA Controller, which enables data transfers to the transmitter and from the receiver. The PDC provides chained buffer management without any intervention of the processor. 299 32058H–AVR32–03/09 AT32UC3A 26.3 Block Diagram Figure 26-1. USART Block Diagram Peripheral DMA Controller Channel Channel USART PIO Controller RXD Receiver RTS INTC USART Interrupt TXD Transmitter CTS CLK_USART CLK_USART/DIV BaudRate Generator CLK Power Manager DIV User Interface Peripheral bus 300 32058H–AVR32–03/09 AT32UC3A 26.4 Application Block Diagram Figure 26-2. Application Block Diagram PPP Modem Driver Serial Driver Field Bus Driver EMV Driver IrLAP IrDA Driver SPI Driver USART RS232 Drivers Modem PSTN RS232 Drivers RS485 Drivers Smart Card Slot IrDA Transceivers SPI Transceiver Serial Port Differential Bus 301 32058H–AVR32–03/09 AT32UC3A 26.5 I/O Lines Description I/O Line Description Description Serial Clock Transmit Serial Data or Master Out Slave In (MOSI) in SPI Master Mode or Master In Slave Out (MISO) in SPI Slave Mode Receive Serial Data or Master In Slave Out (MISO) in SPI Master Mode or Master Out Slave In (MOSI) in SPI Slave Mode Clear to Send or Slave Select (NSS) in SPI Slave Mode Request to Send or Slave Select (NSS) in SPI Master Mode Type I/O I/O Active Level Table 26-1. Name CLK TXD RXD Input CTS RTS Input Output Low Low 302 32058H–AVR32–03/09 AT32UC3A 26.6 26.6.1 Product Dependencies I/O Lines The pins used for interfacing the USART may be multiplexed with the PIO lines. The programmer must first program the PIO controller to assign the desired USART pins to their peripheral function. If I/O lines of the USART are not used by the application, they can be used for other purposes by the PIO Controller. To prevent the TXD line from falling when the USART is disabled, the use of an internal pull up is mandatory. If the hardware handshaking feature or Modem mode is used, the internal pull up on TXD must also be enabled. 26.6.2 Power Manager (PM) The USART is not continuously clocked. The programmer must first enable the USART Clock in the Power Manager (PM) before using the USART. However, if the application does not require USART operations, the USART clock can be stopped when not needed and be restarted later. In this case, the USART will resume its operations where it left off. Configuring the USART does not require the USART clock to be enabled. 26.6.3 Interrupt The USART interrupt line is connected on one of the internal sources of the Advanced Interrupt Controller. Using the USART interrupt requires the INTC to be programmed first. Note that it is not recommended to use the USART interrupt line in edge sensitive mode. 303 32058H–AVR32–03/09 AT32UC3A 26.7 Functional Description The USART is capable of managing several types of serial synchronous or asynchronous communications. It supports the following communication modes: •5- to 9-bit full-duplex asynchronous serial communication –MSB- or LSB-first –1, 1.5 or 2 stop bits –Parity even, odd, marked, space or none –By 8 or by 16 over-sampling receiver frequency –Optional hardware handshaking –Optional break management –Optional multidrop serial communication •High-speed 5- to 9-bit full-duplex synchronous serial communication –MSB- or LSB-first –1 or 2 stop bits –Parity even, odd, marked, space or none –By 8 or by 16 over-sampling frequency –Optional hardware handshaking –Optional break management –Optional multidrop serial communication •RS485 with driver control signal •ISO7816, T0 or T1 protocols for interfacing with smart cards –NACK handling, error counter with repetition and iteration limit •InfraRed IrDA Modulation and Demodulation • SPI Mode – Master or Slave – Serial Clock Programmable Phase and Polarity – SPI Serial Clock (CLK) Frequency up to Internal Clock Frequency CLK_USART/4 •Test modes –Remote loopback, local loopback, automatic echo 304 32058H–AVR32–03/09 AT32UC3A 26.7.1 Baud Rate Generator The Baud Rate Generator provides the bit period clock named the Baud Rate Clock to both the receiver and the transmitter. The Baud Rate Generator clock source can be selected by setting the USCLKS field in the Mode Register (MR) between: •the CLK_USART •a division of the CLK_USART, the divider being product dependent, but generally set to 8 •the external clock, available on the CLK pin The Baud Rate Generator is based upon a 16-bit divider, which is programmed with the CD field of the Baud Rate Generator Register (BRGR). If CD is programmed at 0, the Baud Rate Generator does not generate any clock. If CD is programmed at 1, the divider is bypassed and becomes inactive. If the external CLK clock is selected, the duration of the low and high levels of the signal provided on the CLK pin must be longer than a CLK_USART period. The frequency of the signal provided on CLK must be at least 4.5 times lower than CLK_USART. Figure 26-3. Baud Rate Generator USCLKS CD CD 0 1 2 3 0 CLK_USART CLK_USART/DIV CLK Reserved CLK 16-bit Counter >1 1 0 1 1 SYNC USCLKS= 3 Sampling Clock OVER 0 Sampling Divider 0 BaudRate Clock FIDI SYNC 26.7.1.1 Baud Rate in Asynchronous Mode If the USART is programmed to operate in asynchronous mode, the selected clock is first divided by CD, which is field programmed in the Baud Rate Generator Register (BRGR). The resulting clock is provided to the receiver as a sampling clock and then divided by 16 or 8, depending on the programming of the OVER bit in MR. If OVER is set to 1, the receiver sampling is 8 times higher than the baud rate clock. If OVER is cleared, the sampling is performed at 16 times the baud rate clock. The following formula performs the calculation of the Baud Rate. SelectedClock Baudrate = -------------------------------------------( 8 ( 2 – Over ) CD ) 305 32058H–AVR32–03/09 AT32UC3A This gives a maximum baud rate of CLK_USART divided by 8, assuming that CLK_USART is the highest possible clock and that OVER is programmed at 1. 26.7.1.2 Baud Rate Calculation Example Table 26-2 on page 306 shows calculations of CD to obtain a baud rate at 38400 bauds for different source clock frequencies. This table also shows the actual resulting baud rate and the error. Baud Rate Example (OVER = 0) Expected Baud Rate Bit/s 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 38 400 6.00 8.00 8.14 12.00 13.02 19.53 20.00 23.30 24.00 30.00 39.06 40.00 40.69 52.08 53.33 53.71 65.10 81.38 97.66 113.93 6 8 8 12 13 20 20 23 24 30 39 40 40 52 53 54 65 81 98 114 Calculation Result CD Actual Baud Rate Bit/s 38 400.00 38 400.00 39 062.50 38 400.00 38 461.54 37 500.00 38 400.00 38 908.10 38 400.00 38 400.00 38 461.54 38 400.00 38 109.76 38 461.54 38 641.51 38 194.44 38 461.54 38 580.25 38 265.31 38 377.19 0.00% 0.00% 1.70% 0.00% 0.16% 2.40% 0.00% 1.31% 0.00% 0.00% 0.16% 0.00% 0.76% 0.16% 0.63% 0.54% 0.16% 0.47% 0.35% 0.06% Error Table 26-2. Source Clock MHz 3 686 400 4 915 200 5 000 000 7 372 800 8 000 000 12 000 000 12 288 000 14 318 180 14 745 600 18 432 000 24 000 000 24 576 000 25 000 000 32 000 000 32 768 000 33 000 000 40 000 000 50 000 000 60 000 000 70 000 000 The baud rate is calculated with the following formula: BaudRate = ( CLKUSART ) ⁄ CD × 16 The baud rate error is calculated with the following formula. It is not recommended to work with an error higher than 5%. ExpectedBaudRate Error = 1 – ⎛ --------------------------------------------------⎞ ⎝ ActualBaudRate ⎠ 306 32058H–AVR32–03/09 AT32UC3A 26.7.1.3 Fractional Baud Rate in Asynchronous Mode The Baud Rate generator previously defined is subject to the following limitation: the output frequency changes by only integer multiples of the reference frequency. An approach to this problem is to integrate a fractional N clock generator that has a high resolution. The generator architecture is modified to obtain Baud Rate changes by a fraction of the reference source clock. This fractional part is programmed with the FP field in the Baud Rate Generator Register (BRGR). If FP is not 0, the fractional part is activated. The resolution is one eighth of the clock divider. This feature is only available when using USART normal mode. The fractional Baud Rate is calculated using the following formula: SelectedClock Baudrate = ---------------------------------------------------------------⎛ 8 ( 2 – Over ) ⎛ CD + FP⎞ ⎞ -----⎝ ⎝ 8 ⎠⎠ The modified architecture is presented below: Figure 26-4. Fractional Baud Rate Generator FP USCLKS CD Modulus Control FP CD CLK FIDI >1 1 0 0 1 1 SYNC USCLKS = 3 Sampling Clock 0 Sampling Divider 0 BaudRate Clock OVER SYNC CLK_USART CLK_USART/DIV CLK Reserved 0 1 16-bit Counter 2 3 glitch-free logic 26.7.1.4 Baud Rate in Synchronous Mode or SPI Mode If the USART is programmed to operate in synchronous mode, the selected clock is simply divided by the field CD in BRGR. BaudRate = SelectedClock ------------------------------------CD In synchronous mode, if the external clock is selected (USCLKS = 3), the clock is provided directly by the signal on the USART CLK pin. No division is active. The value written in BRGR 307 32058H–AVR32–03/09 AT32UC3A has no effect. The external clock frequency must be at least 4.5 times lower than the system clock. When either the external clock CLK or the internal clock divided (CLK_USART/DIV) is selected, the value programmed in CD must be even if the user has to ensure a 50:50 mark/space ratio on the CLK pin. If the internal clock CLK_USART is selected, the Baud Rate Generator ensures a 50:50 duty cycle on the CLK pin, even if the value programmed in CD is odd. 26.7.1.5 Baud Rate in ISO 7816 Mode The ISO7816 specification defines the bit rate with the following formula: Di B = ----- × f Fi where: •B is the bit rate •Di is the bit-rate adjustment factor •Fi is the clock frequency division factor •f is the ISO7816 clock frequency (Hz) Di is a binary value encoded on a 4-bit field, named DI, as represented in Table 26-3 on page 308. Table 26-3. DI field Di (decimal) Binary and Decimal Values for Di 0001 1 0010 2 0011 4 0100 8 0101 16 0110 32 1000 12 1001 20 Fi is a binary value encoded on a 4-bit field, named FI, as represented in Table 26-4 on page 308. Table 26-4. FI field Fi (decimal Binary and Decimal Values for Fi 0000 372 0001 372 0010 558 0011 744 0100 1116 0101 1488 0110 1860 1001 512 1010 768 1011 1024 1100 1536 1101 2048 Table 26-5 on page 308 shows the resulting Fi/Di Ratio, which is the ratio between the ISO7816 clock and the baud rate clock. Table 26-5. Fi/Di 1 2 4 8 16 32 12 20 Possible Values for the Fi/Di Ratio 372 372 186 93 46.5 23.25 11.62 31 18.6 558 558 279 139.5 69.75 34.87 17.43 46.5 27.9 774 744 372 186 93 46.5 23.25 62 37.2 1116 1116 558 279 139.5 69.75 34.87 93 55.8 1488 1488 744 372 186 93 46.5 124 74.4 1806 1860 930 465 232.5 116.2 58.13 155 93 512 512 256 128 64 32 16 42.66 25.6 768 768 384 192 96 48 24 64 38.4 1024 1024 512 256 128 64 32 85.33 51.2 1536 1536 768 384 192 96 48 128 76.8 2048 2048 1024 512 256 128 64 170.6 102.4 If the USART is configured in ISO7816 Mode, the clock selected by the USCLKS field in the Mode Register (MR) is first divided by the value programmed in the field CD in the Baud Rate 308 32058H–AVR32–03/09 AT32UC3A Generator Register (BRGR). The resulting clock can be provided to the CLK pin to feed the smart card clock inputs. This means that the CLKO bit can be set in MR. This clock is then divided by the value programmed in the FI_DI_RATIO field in the FI_DI_Ratio register (FIDI). This is performed by the Sampling Divider, which performs a division by up to 2047 in ISO7816 Mode. The non-integer values of the Fi/Di Ratio are not supported and the user must program the FI_DI_RATIO field to a value as close as possible to the expected value. The FI_DI_RATIO field resets to the value 0x174 (372 in decimal) and is the most common divider between the ISO7816 clock and the bit rate (Fi = 372, Di = 1). Figure 26-5 on page 309 shows the relation between the Elementary Time Unit, corresponding to a bit time, and the ISO 7816 clock. Figure 26-5. Elementary Time Unit (ETU) FI_DI_RATIO ISO7816 Clock Cycles ISO7816 Clock on CLK ISO7816 I/O Line on TXD 1 ETU 26.7.2 Receiver and Transmitter Control After reset, the receiver is disabled. The user must enable the receiver by setting the RXEN bit in the Control Register (CR). However, the receiver registers can be programmed before the receiver clock is enabled. After reset, the transmitter is disabled. The user must enable it by setting the TXEN bit in the Control Register (CR). However, the transmitter registers can be programmed before being enabled. The Receiver and the Transmitter can be enabled together or independently. At any time, the software can perform a reset on the receiver or the transmitter of the USART by setting the corresponding bit, RSTRX and RSTTX respectively, in the Control Register (CR). The software resets clear the status flag and reset internal state machines but the user interface configuration registers hold the value configured prior to software reset. Regardless of what the receiver or the transmitter is performing, the communication is immediately stopped. The user can also independently disable the receiver or the transmitter by setting RXDIS and TXDIS respectively in CR. If the receiver is disabled during a character reception, the USART waits until the end of reception of the current character, then the reception is stopped. If the transmitter is disabled while it is operating, the USART waits the end of transmission of both the current character and character being stored in the Transmit Holding Register (THR). If a timeguard is programmed, it is handled normally. 309 32058H–AVR32–03/09 AT32UC3A 26.7.3 26.7.3.1 Synchronous and Asynchronous Modes Transmitter Operations The transmitter performs the same in both synchronous and asynchronous operating modes (SYNC = 0 or SYNC = 1). One start bit, up to 9 data bits, one optional parity bit and up to two stop bits are successively shifted out on the TXD pin at each falling edge of the programmed serial clock. The number of data bits is selected by the CHRL field and the MODE 9 bit in the Mode Register (MR). Nine bits are selected by setting the MODE 9 bit regardless of the CHRL field. The parity bit is set according to the PAR field in MR. The even, odd, space, marked or none parity bit can be configured. The MSBF field in MR configures which data bit is sent first. If written at 1, the most significant bit is sent first. At 0, the less significant bit is sent first. The number of stop bits is selected by the NBSTOP field in MR. The 1.5 stop bit is supported in asynchronous mode only. Figure 26-6. Character Transmit Example: 8-bit, Parity Enabled One Stop Baud Rate Clock TXD Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Parity Bit Stop Bit The characters are sent by writing in the Transmit Holding Register (THR). The transmitter reports two status bits in the Channel Status Register (CSR): TXRDY (Transmitter Ready), which indicates that THR is empty and TXEMPTY, which indicates that all the characters written in THR have been processed. When the current character processing is completed, the last character written in THR is transferred into the Shift Register of the transmitter and THR becomes empty, thus TXRDY rises. Both TXRDY and TXEMPTY bits are low when the transmitter is disabled. Writing a character in THR while TXRDY is low has no effect and the written character is lost. Figure 26-7. Transmitter Status Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Start D0 Bit Bit Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit Write US_THR TXRDY TXEMPTY 310 32058H–AVR32–03/09 AT32UC3A 26.7.3.2 Manchester Encoder When the Manchester encoder is in use, characters transmitted through the USART are encoded based on biphase Manchester II format. To enable this mode, set the MAN field in the MR register to 1. Depending on polarity configuration, a logic level (zero or one), is transmitted as a coded signal one-to-zero or zero-to-one. Thus, a transition always occurs at the midpoint of each bit time. It consumes more bandwidth than the original NRZ signal (2x) but the receiver has more error control since the expected input must show a change at the center of a bit cell. An example of Manchester encoded sequence is: the byte 0xB1 or 10110001 encodes to 10 01 10 10 01 01 01 10, assuming the default polarity of the encoder. Figure 26-8 on page 311 illustrates this coding scheme. Figure 26-8. NRZ to Manchester Encoding NRZ encoded data Manchester encoded data 1 0 1 1 0 0 0 1 Txd The Manchester encoded character can also be encapsulated by adding both a configurable preamble and a start frame delimiter pattern. Depending on the configuration, the preamble is a training sequence, composed of a pre-defined pattern with a programmable length from 1 to 15 bit times. If the preamble length is set to 0, the preamble waveform is not generated prior to any character. The preamble pattern is chosen among the following sequences: ALL_ONE, ALL_ZERO, ONE_ZERO or ZERO_ONE, writing the field TX_PP in the MAN register, the field TX_PL is used to configure the preamble length. Figure 26-9 on page 312 illustrates and defines the valid patterns. To improve flexibility, the encoding scheme can be configured using the TX_MPOL field in the MAN register. If the TX_MPOL field is set to zero (default), a logic zero is encoded with a zero-to-one transition and a logic one is encoded with a one-to-zero transition. If the TX_MPOL field is set to one, a logic one is encoded with a one-to-zero transition and a logic zero is encoded with a zero-to-one transition. 311 32058H–AVR32–03/09 AT32UC3A Figure 26-9. Preamble Patterns, Default Polarity Assumed Manchester encoded data Txd SFD DATA 8 bit width "ALL_ONE" Preamble Manchester encoded data Txd SFD DATA 8 bit width "ALL_ZERO" Preamble Manchester encoded data Txd SFD DATA 8 bit width "ZERO_ONE" Preamble Manchester encoded data Txd SFD DATA 8 bit width "ONE_ZERO" Preamble A start frame delimiter is to be configured using the ONEBIT field in the MR register. It consists of a user-defined pattern that indicates the beginning of a valid data. Figure 26-10 on page 313 illustrates these patterns. If the start frame delimiter, also known as start bit, is one bit, (ONEBIT at 1), a logic zero is Manchester encoded and indicates that a new character is being sent serially on the line. If the start frame delimiter is a synchronization pattern also referred to as sync (ONEBIT at 0), a sequence of 3 bit times is sent serially on the line to indicate the start of a new character. The sync waveform is in itself an invalid Manchester waveform as the transition occurs at the middle of the second bit time. Two distinct sync patterns are used: the command sync and the data sync. The command sync has a logic one level for one and a half bit times, then a transition to logic zero for the second one and a half bit times. If the MODSYNC field in the MR register is set to 1, the next character is a command. If it is set to 0, the next character is a data. When direct memory access is used, the MODSYNC field can be immediately updated with a modified character located in memory. To enable this mode, VAR_SYNC field in MR register must be set to 1. In this case, the MODSYNC field in MR is bypassed and the sync configuration is held in the TXSYNH in the THR register. The USART character format is modified and includes sync information. 312 32058H–AVR32–03/09 AT32UC3A Figure 26-10. Start Frame Delimiter Preamble Length is set to 0 SFD Manchester encoded data Txd DATA One bit start frame delimiter SFD Manchester encoded data Txd DATA SFD Manchester encoded data Txd Command Sync start frame delimiter DATA Data Sync start frame delimiter 26.7.3.3 Drift Compensation Drift compensation is available only in 16X oversampling mode. An hardware recovery system allows a larger clock drift. To enable the hardware system, the bit in the MAN register must be set. If the RXD edge is one 16X clock cycle from the expected edge, this is considered as normal jitter and no corrective actions is taken. If the RXD event is between 4 and 2 clock cycles before the expected edge, then the current period is shortened by one clock cycle. If the RXD event is between 2 and 3 clock cycles after the expected edge, then the current period is lengthened by one clock cycle. These intervals are considered to be drift and so corrective actions are automatically taken. Figure 26-11. Bit Resynchronization Oversampling 16x Clock RXD Sampling point Expected edge Synchro. Error Synchro. Jump Tolerance Sync Jump Synchro. Error 26.7.3.4 Asynchronous Receiver If the USART is programmed in asynchronous operating mode (SYNC = 0), the receiver oversamples the RXD input line. The oversampling is either 16 or 8 times the Baud Rate clock, depending on the OVER bit in the Mode Register (MR). 313 32058H–AVR32–03/09 AT32UC3A The receiver samples the RXD line. If the line is sampled during one half of a bit time at 0, a start bit is detected and data, parity and stop bits are successively sampled on the bit rate clock. If the oversampling is 16, (OVER at 0), a start is detected at the eighth sample at 0. Then, data bits, parity bit and stop bit are sampled on each 16 sampling clock cycle. If the oversampling is 8 (OVER at 1), a start bit is detected at the fourth sample at 0. Then, data bits, parity bit and stop bit are sampled on each 8 sampling clock cycle. The number of data bits, first bit sent and parity mode are selected by the same fields and bits as the transmitter, i.e. respectively CHRL, MODE9, MSBF and PAR. For the synchronization mechanism only, the number of stop bits has no effect on the receiver as it considers only one stop bit, regardless of the field NBSTOP, so that resynchronization between the receiver and the transmitter can occur. Moreover, as soon as the stop bit is sampled, the receiver starts looking for a new start bit so that resynchronization can also be accomplished when the transmitter is operating with one stop bit. Figure 26-12 on page 314 and Figure 26-13 on page 314 illustrate start detection and character reception when USART operates in asynchronous mode. Figure 26-12. Asynchronous Start Detection Baud Rate Clock Sampling Clock (x16) RXD Sampling 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 D0 Sampling Start Detection RXD Sampling 1 2 3 4 5 6 01 Start Rejection 7 2 3 4 Figure 26-13. Asynchronous Character Reception Example: 8-bit, Parity Enabled Baud Rate Clock RXD Start Detection 16 16 16 16 16 16 16 16 16 16 samples samples samples samples samples samples samples samples samples samples D0 D1 D2 D3 D4 D5 D6 D7 Parity Bit Stop Bit 314 32058H–AVR32–03/09 AT32UC3A 26.7.3.5 Manchester Decoder When the MAN field in MR register is set to 1, the Manchester decoder is enabled. The decoder performs both preamble and start frame delimiter detection. One input line is dedicated to Manchester encoded input data. An optional preamble sequence can be defined, its length is user-defined and totally independent of the emitter side. Use RX_PL in MAN register to configure the length of the preamble sequence. If the length is set to 0, no preamble is detected and the function is disabled. In addition, the polarity of the input stream is programmable with RX_MPOL field in MAN register. Depending on the desired application the preamble pattern matching is to be defined via the RX_PP field in MAN. See Figure 26-9 on page 312 for available preamble patterns. Unlike preamble, the start frame delimiter is shared between Manchester Encoder and Decoder. So, if ONEBIT field is set to 1, only a zero encoded Manchester can be detected as a valid start frame delimiter. If ONEBIT is set to 0, only a sync pattern is detected as a valid start frame delimiter. Decoder operates by detecting transition on incoming stream. If RXD is sampled during one quarter of a bit time at zero, a start bit is detected. See Figure 26-14 on page 315.. The sample pulse rejection mechanism applies. Figure 26-14. Asynchronous Start Bit Detection Sampling Clock (16 x) Manchester encoded data Txd Start Detection 1 2 3 4 The receiver is activated and starts Preamble and Frame Delimiter detection, sampling the data at one quarter and then three quarters. If a valid preamble pattern or start frame delimiter is detected, the receiver continues decoding with the same synchronization. If the stream does not match a valid pattern or a valid start frame delimiter, the receiver re-synchronizes on the next valid edge.The minimum time threshold to estimate the bit value is three quarters of a bit time. If a valid preamble (if used) followed with a valid start frame delimiter is detected, the incoming stream is decoded into NRZ data and passed to USART for processing. Figure 26-15 on page 316 illustrates Manchester pattern mismatch. When incoming data stream is passed to the USART, the receiver is also able to detect Manchester code violation. A code violation is a lack of transition in the middle of a bit cell. In this case, MANE flag in CSR register is raised. It is cleared by writing the Control Register (CR) with the RSTSTA bit at 1. See Figure 26-16 on page 316 for an example of Manchester error detection during data phase. 315 32058H–AVR32–03/09 AT32UC3A Figure 26-15. Preamble Pattern Mismatch Preamble Mismatch Manchester coding error Preamble Mismatch invalid pattern Manchester encoded data Txd SFD DATA Preamble Length is set to 8 Figure 26-16. Manchester Error Flag Preamble Length is set to 4 Elementary character bit time SFD Manchester encoded data Txd Entering USART character area sampling points Preamble subpacket and Start Frame Delimiter were successfully decoded Manchester Coding Error detected When the start frame delimiter is a sync pattern (ONEBIT field at 0), both command and data delimiter are supported. If a valid sync is detected, the received character is written as RXCHR field in the RHR register and the RXSYNH is updated. RXCHR is set to 1 when the received character is a command, and it is set to 0 if the received character is a data. This mechanism alleviates and simplifies the direct memory access as the character contains its own sync field in the same register. As the decoder is setup to be used in unipolar mode, the first bit of the frame has to be a zero-toone transition. 26.7.3.6 Radio Interface: Manchester Encoded USART Application This section describes low data rate RF transmission systems and their integration with a Manchester encoded USART. These systems are based on transmitter and receiver ICs that support ASK and FSK modulation schemes. The goal is to perform full duplex radio transmission of characters using two different frequency carriers. See the configuration in Figure 26-17 on page 317. 316 32058H–AVR32–03/09 AT32UC3A Figure 26-17. Manchester Encoded Characters RF Transmission Fup frequency Carrier ASK/FSK Upstream Receiver Upstream Emitter LNA VCO RF filter Demod Serial Configuration Interface control Fdown frequency Carrier bi-dir line ASK/FSK downstream transmitter Manchester decoder USART Receiver Downstream Receiver Manchester encoder PA RF filter Mod VCO USART Emitter control The USART module is configured as a Manchester encoder/decoder. Looking at the downstream communication channel, Manchester encoded characters are serially sent to the RF emitter. This may also include a user defined preamble and a start frame delimiter. Mostly, preamble is used in the RF receiver to distinguish between a valid data from a transmitter and signals due to noise. The Manchester stream is then modulated. See Figure 26-18 on page 317 for an example of ASK modulation scheme. When a logic one is sent to the ASK modulator, the power amplifier, referred to as PA, is enabled and transmits an RF signal at downstream frequency. When a logic zero is transmitted, the RF signal is turned off. If the FSK modulator is activated, two different frequencies are used to transmit data. When a logic 1 is sent, the modulator outputs an RF signal at frequency F0 and switches to F1 if the data sent is a 0. See Figure 26-19 on page 318. From the receiver side, another carrier frequency is used. The RF receiver performs a bit check operation examining demodulated data stream. If a valid pattern is detected, the receiver switches to receiving mode. The demodulated stream is sent to the Manchester decoder. Because of bit checking inside RF IC, the data transferred to the microcontroller is reduced by a user-defined number of bits. The Manchester preamble length is to be defined in accordance with the RF IC configuration. Figure 26-18. ASK Modulator Output 1 NRZ stream Manchester encoded data default polarity unipolar output ASK Modulator Output Uptstream Frequency F0 0 0 1 Txd 317 32058H–AVR32–03/09 AT32UC3A Figure 26-19. FSK Modulator Output 1 NRZ stream Manchester encoded data default polarity unipolar output FSK Modulator Output Uptstream Frequencies [F0, F0+offset] 0 0 1 Txd 26.7.4 Synchronous Receiver In synchronous mode (SYNC = 1), the receiver samples the RXD signal on each rising edge of the Baud Rate Clock. If a low level is detected, it is considered as a start. All data bits, the parity bit and the stop bits are sampled and the receiver waits for the next start bit. Synchronous mode operations provide a high speed transfer capability. Configuration fields and bits are the same as in asynchronous mode. Figure 26-20 on page 318 illustrates a character reception in synchronous mode. Figure 26-20. Synchronous Mode Character Reception Example: 8-bit, Parity Enabled 1 Stop Baud Rate Clock RXD Sampling Start D0 D1 D2 D3 D4 D5 D6 D7 Parity Bit Stop Bit 26.7.4.1 Receiver Operations When a character reception is completed, it is transferred to the Receive Holding Register (RHR) and the RXRDY bit in the Status Register (CSR) rises. If a character is completed while the RXRDY is set, the OVRE (Overrun Error) bit is set. The last character is transferred into RHR and overwrites the previous one. The OVRE bit is cleared by writing the Control Register (CR) with the RSTSTA (Reset Status) bit at 1. 318 32058H–AVR32–03/09 AT32UC3A Figure 26-21. Receiver Status Baud Rate Clock RXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Start D0 Bit Bit Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit RSTSTA = 1 Write US_CR Read US_RHR RXRDY OVRE 319 32058H–AVR32–03/09 AT32UC3A 26.7.4.2 Parity The USART supports five parity modes selected by programming the PAR field in the Mode Register (MR). The PAR field also enables the Multidrop mode, see ”Multidrop Mode” on page 321. Even and odd parity bit generation and error detection are supported. If even parity is selected, the parity generator of the transmitter drives the parity bit at 0 if a number of 1s in the character data bit is even, and at 1 if the number of 1s is odd. Accordingly, the receiver parity checker counts the number of received 1s and reports a parity error if the sampled parity bit does not correspond. If odd parity is selected, the parity generator of the transmitter drives the parity bit at 1 if a number of 1s in the character data bit is even, and at 0 if the number of 1s is odd. Accordingly, the receiver parity checker counts the number of received 1s and reports a parity error if the sampled parity bit does not correspond. If the mark parity is used, the parity generator of the transmitter drives the parity bit at 1 for all characters. The receiver parity checker reports an error if the parity bit is sampled at 0. If the space parity is used, the parity generator of the transmitter drives the parity bit at 0 for all characters. The receiver parity checker reports an error if the parity bit is sampled at 1. If parity is disabled, the transmitter does not generate any parity bit and the receiver does not report any parity error. Table 26-6 on page 320 shows an example of the parity bit for the character 0x41 (character ASCII “A”) depending on the configuration of the USART. Because there are two bits at 1, 1 bit is added when a parity is odd, or 0 is added when a parity is even. Table 26-6. Character A A A A A Parity Bit Examples Hexa 0x41 0x41 0x41 0x41 0x41 Binary 0100 0001 0100 0001 0100 0001 0100 0001 0100 0001 Parity Bit 1 0 1 0 None Parity Mode Odd Even Mark Space None When the receiver detects a parity error, it sets the PARE (Parity Error) bit in the Channel Status Register (CSR). The PARE bit can be cleared by writing the Control Register (CR) with the RSTSTA bit at 1. Figure 26-22 on page 321 illustrates the parity bit status setting and clearing. 320 32058H–AVR32–03/09 AT32UC3A Figure 26-22. Parity Error Baud Rate Clock RXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Bad Stop Parity Bit Bit RSTSTA = 1 Write US_CR PARE RXRDY 26.7.4.3 Multidrop Mode If the PAR field in the Mode Register (MR) is programmed to the value 0x6 or 0x07, the USART runs in Multidrop Mode. This mode differentiates the data characters and the address characters. Data is transmitted with the parity bit at 0 and addresses are transmitted with the parity bit at 1. If the USART is configured in multidrop mode, the receiver sets the PARE parity error bit when the parity bit is high and the transmitter is able to send a character with the parity bit high when the Control Register is written with the SENDA bit at 1. To handle parity error, the PARE bit is cleared when the Control Register is written with the bit RSTSTA at 1. The transmitter sends an address byte (parity bit set) when SENDA is written to CR. In this case, the next byte written to THR is transmitted as an address. Any character written in THR without having written the command SENDA is transmitted normally with the parity at 0. 26.7.4.4 Transmitter Timeguard The timeguard feature enables the USART interface with slow remote devices. The timeguard function enables the transmitter to insert an idle state on the TXD line between two characters. This idle state actually acts as a long stop bit. The duration of the idle state is programmed in the TG field of the Transmitter Timeguard Register (TTGR). When this field is programmed at zero no timeguard is generated. Otherwise, the transmitter holds a high level on TXD after each transmitted byte during the number of bit periods programmed in TG in addition to the number of stop bits. As illustrated in Figure 26-23 on page 322, the behavior of TXRDY and TXEMPTY status bits is modified by the programming of a timeguard. TXRDY rises only when the start bit of the next character is sent, and thus remains at 0 during the timeguard transmission if a character has been written in THR. TXEMPTY remains low until the timeguard transmission is completed as the timeguard is part of the current character being transmitted. 321 32058H–AVR32–03/09 AT32UC3A Figure 26-23. Timeguard Operations TG = 4 Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit TG = 4 Write US_THR TXRDY TXEMPTY Table 26-7 on page 322 indicates the maximum length of a timeguard period that the transmitter can handle in relation to the function of the Baud Rate. Table 26-7. Maximum Timeguard Length Depending on Baud Rate Bit time µs 833 104 69.4 52.1 34.7 29.9 17.9 17.4 8.7 Timeguard ms 212.50 26.56 17.71 13.28 8.85 7.63 4.55 4.43 2.21 Baud Rate Bit/sec 1 200 9 600 14400 19200 28800 33400 56000 57600 115200 26.7.4.5 Receiver Time-out The Receiver Time-out provides support in handling variable-length frames. This feature detects an idle condition on the RXD line. When a time-out is detected, the bit TIMEOUT in the Channel Status Register (CSR) rises and can generate an interrupt, thus indicating to the driver an end of frame. The time-out delay period (during which the receiver waits for a new character) is programmed in the TO field of the Receiver Time-out Register (RTOR). If the TO field is programmed at 0, the Receiver Time-out is disabled and no time-out is detected. The TIMEOUT bit in CSR remains at 0. Otherwise, the receiver loads a 16-bit counter with the value programmed in TO. This counter is decremented at each bit period and reloaded each time a new character is received. If the counter reaches 0, the TIMEOUT bit in the Status Register rises. Then, the user can either: • Stop the counter clock until a new character is received. This is performed by writing the Control Register (CR) with the STTTO (Start Time-out) bit at 1. In this case, the idle state on RXD before a new character is received will not provide a time-out. This prevents having to 322 32058H–AVR32–03/09 AT32UC3A handle an interrupt before a character is received and allows waiting for the next idle state on RXD after a frame is received. • Obtain an interrupt while no character is received. This is performed by writing CR with the RETTO (Reload and Start Time-out) bit at 1. If RETTO is performed, the counter starts counting down immediately from the value TO. This enables generation of a periodic interrupt so that a user time-out can be handled, for example when no key is pressed on a keyboard. If STTTO is performed, the counter clock is stopped until a first character is received. The idle state on RXD before the start of the frame does not provide a time-out. This prevents having to obtain a periodic interrupt and enables a wait of the end of frame when the idle state on RXD is detected. If RETTO is performed, the counter starts counting down immediately from the value TO. This enables generation of a periodic interrupt so that a user time-out can be handled, for example when no key is pressed on a keyboard. Figure 26-24 on page 323 shows the block diagram of the Receiver Time-out feature. Figure 26-24. Receiver Time-out Block Diagram Baud Rate Clock TO 1 STTTO D Q Clock 16-bit Time-out Counter Load 16-bit Value = TIMEOUT Character Received RETTO Clear 0 Table 26-8 on page 323 gives the maximum time-out period for some standard baud rates. Table 26-8. Maximum Time-out Period Bit Time µs 1 667 833 417 208 104 69 52 35 30 18 17 5 Time-out ms 109 225 54 613 27 306 13 653 6 827 4 551 3 413 2 276 1 962 1 170 1 138 328 Baud Rate bit/sec 600 1 200 2 400 4 800 9 600 14400 19200 28800 33400 56000 57600 200000 323 32058H–AVR32–03/09 AT32UC3A 26.7.4.6 Framing Error The receiver is capable of detecting framing errors. A framing error happens when the stop bit of a received character is detected at level 0. This can occur if the receiver and the transmitter are fully desynchronized. A framing error is reported on the FRAME bit of the Channel Status Register (CSR). The FRAME bit is asserted in the middle of the stop bit as soon as the framing error is detected. It is cleared by writing the Control Register (CR) with the RSTSTA bit at 1. Figure 26-25. Framing Error Status Baud Rate Clock RXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit RSTSTA = 1 Write US_CR FRAME RXRDY 26.7.4.7 Transmit Break The user can request the transmitter to generate a break condition on the TXD line. A break condition drives the TXD line low during at least one complete character. It appears the same as a 0x00 character sent with the parity and the stop bits at 0. However, the transmitter holds the TXD line at least during one character until the user requests the break condition to be removed. A break is transmitted by writing the Control Register (CR) with the STTBRK bit at 1. This can be performed at any time, either while the transmitter is empty (no character in either the Shift Register or in THR) or when a character is being transmitted. If a break is requested while a character is being shifted out, the character is first completed before the TXD line is held low. Once STTBRK command is requested further STTBRK commands are ignored until the end of the break is completed. The break condition is removed by writing CR with the STPBRK bit at 1. If the STPBRK is requested before the end of the minimum break duration (one character, including start, data, parity and stop bits), the transmitter ensures that the break condition completes. The transmitter considers the break as though it is a character, i.e. the STTBRK and STPBRK commands are taken into account only if the TXRDY bit in CSR is at 1 and the start of the break condition clears the TXRDY and TXEMPTY bits as if a character is processed. Writing CR with the both STTBRK and STPBRK bits at 1 can lead to an unpredictable result. All STPBRK commands requested without a previous STTBRK command are ignored. A byte written into the Transmit Holding Register while a break is pending, but not started, is ignored. 324 32058H–AVR32–03/09 AT32UC3A After the break condition, the transmitter returns the TXD line to 1 for a minimum of 12 bit times. Thus, the transmitter ensures that the remote receiver detects correctly the end of break and the start of the next character. If the timeguard is programmed with a value higher than 12, the TXD line is held high for the timeguard period. After holding the TXD line for this period, the transmitter resumes normal operations. Figure 26-26 on page 325 illustrates the effect of both the Start Break (STTBRK) and Stop Break (STPBRK) commands on the TXD line. Figure 26-26. Break Transmission Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit Break Transmission STPBRK = 1 End of Break STTBRK = 1 Write US_CR TXRDY TXEMPTY 26.7.4.8 Receive Break The receiver detects a break condition when all data, parity and stop bits are low. This corresponds to detecting a framing error with data at 0x00, but FRAME remains low. When the low stop bit is detected, the receiver asserts the RXBRK bit in CSR. This bit may be cleared by writing the Control Register (CR) with the bit RSTSTA at 1. An end of receive break is detected by a high level for at least 2/16 of a bit period in asynchronous operating mode or one sample at high level in synchronous operating mode. The end of break detection also asserts the RXBRK bit. 26.7.4.9 Hardware Handshaking The USART features a hardware handshaking out-of-band flow control. The RTS and CTS pins are used to connect with the remote device, as shown in Figure 26-27 on page 325. Figure 26-27. Connection with a Remote Device for Hardware Handshaking USART TXD RXD CTS RTS Remote Device RXD TXD RTS CTS 325 32058H–AVR32–03/09 AT32UC3A Setting the USART to operate with hardware handshaking is performed by writing the MODE field in the Mode Register (MR) to the value 0x2. The USART behavior when hardware handshaking is enabled is the same as the behavior in standard synchronous or asynchronous mode, except that the receiver drives the RTS pin as described below and the level on the CTS pin modifies the behavior of the transmitter as described below. Using this mode requires using the PDC channel for reception. The transmitter can handle hardware handshaking in any case. Figure 26-28 on page 326 shows how the receiver operates if hardware handshaking is enabled. The RTS pin is driven high if the receiver is disabled and if the status RXBUFF (Receive Buffer Full) coming from the PDC channel is high. Normally, the remote device does not start transmitting while its CTS pin (driven by RTS) is high. As soon as the Receiver is enabled, the RTS falls, indicating to the remote device that it can start transmitting. Defining a new buffer to the PDC clears the status bit RXBUFF and, as a result, asserts the pin RTS low. Figure 26-28. Receiver Behavior when Operating with Hardware Handshaking RXD RXEN = 1 Write US_CR RTS RXBUFF RXDIS = 1 Figure 26-29 on page 326 shows how the transmitter operates if hardware handshaking is enabled. The CTS pin disables the transmitter. If a character is being processing, the transmitter is disabled only after the completion of the current character and transmission of the next character happens as soon as the pin CTS falls. Figure 26-29. Transmitter Behavior when Operating with Hardware Handshaking CTS TXD 26.7.5 ISO7816 Mode The USART features an ISO7816-compatible operating mode. This mode permits interfacing with smart cards and Security Access Modules (SAM) communicating through an ISO7816 link. Both T = 0 and T = 1 protocols defined by the ISO7816 specification are supported. Setting the USART in ISO7816 mode is performed by writing the MODE field in the Mode Register (MR) to the value 0x4 for protocol T = 0 and to the value 0x5 for protocol T = 1. 26.7.5.1 ISO7816 Mode Overview The ISO7816 is a half duplex communication on only one bidirectional line. The baud rate is determined by a division of the clock provided to the remote device (see ”Baud Rate Generator” on page 305). The USART connects to a smart card as shown in Figure 26-30 on page 327. The TXD line becomes bidirectional and the Baud Rate Generator feeds the ISO7816 clock on the CLK pin. 326 32058H–AVR32–03/09 AT32UC3A As the TXD pin becomes bidirectional, its output remains driven by the output of the transmitter but only when the transmitter is active while its input is directed to the input of the receiver. The USART is considered as the master of the communication as it generates the clock. Figure 26-30. Connection of a Smart Card to the USART USART CLK CLK Smart Card TXD I/O When operating in ISO7816, either in T = 0 or T = 1 modes, the character format is fixed. The configuration is 8 data bits, even parity and 1 or 2 stop bits, regardless of the values programmed in the CHRL, MODE9, PAR and CHMODE fields. MSBF can be used to transmit LSB or MSB first. Parity Bit (PAR) can be used to transmit in normal or inverse mode. Refer to ”USART Mode Register” on page 343 and ”PAR: Parity Type” on page 345. The USART cannot operate concurrently in both receiver and transmitter modes as the communication is unidirectional at a time. It has to be configured according to the required mode by enabling or disabling either the receiver or the transmitter as desired. Enabling both the receiver and the transmitter at the same time in ISO7816 mode may lead to unpredictable results. The ISO7816 specification defines an inverse transmission format. Data bits of the character must be transmitted on the I/O line at their negative value. The USART does not support this format and the user has to perform an exclusive OR on the data before writing it in the Transmit Holding Register (THR) or after reading it in the Receive Holding Register (RHR). 26.7.5.2 Protocol T = 0 In T = 0 protocol, a character is made up of one start bit, eight data bits, one parity bit and one guard time, which lasts two bit times. The transmitter shifts out the bits and does not drive the I/O line during the guard time. If no parity error is detected, the I/O line remains at 1 during the guard time and the transmitter can continue with the transmission of the next character, as shown in Figure 26-31 on page 328. If a parity error is detected by the receiver, it drives the I/O line at 0 during the guard time, as shown in Figure 26-32 on page 328. This error bit is also named NACK, for Non Acknowledge. In this case, the character lasts 1 bit time more, as the guard time length is the same and is added to the error bit time which lasts 1 bit time. When the USART is the receiver and it detects an error, it does not load the erroneous character in the Receive Holding Register (RHR). It appropriately sets the PARE bit in the Status Register (SR) so that the software can handle the error. 327 32058H–AVR32–03/09 AT32UC3A Figure 26-31. T = 0 Protocol without Parity Error Baud Rate Clock RXD Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Parity Guard Guard Next Bit Time 1 Time 2 Start Bit Figure 26-32. T = 0 Protocol with Parity Error Baud Rate Clock I/O Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Error Parity Guard Bit Time 1 Guard Start Time 2 Bit D0 D1 Repetition 26.7.5.3 Receive Error Counter The USART receiver also records the total number of errors. This can be read in the Number of Error (NER) register. The NB_ERRORS field can record up to 255 errors. Reading NER automatically clears the NB_ERRORS field. Receive NACK Inhibit The USART can also be configured to inhibit an error. This can be achieved by setting the INACK bit in the Mode Register (MR). If INACK is at 1, no error signal is driven on the I/O line even if a parity bit is detected, but the INACK bit is set in the Status Register (SR). The INACK bit can be cleared by writing the Control Register (CR) with the RSTNACK bit at 1. Moreover, if INACK is set, the erroneous received character is stored in the Receive Holding Register, as if no error occurred. However, the RXRDY bit does not raise. 26.7.5.4 26.7.5.5 Transmit Character Repetition When the USART is transmitting a character and gets a NACK, it can automatically repeat the character before moving on to the next one. Repetition is enabled by writing the MAX_ITERATION field in the Mode Register (MR) at a value higher than 0. Each character can be transmitted up to eight times; the first transmission plus seven repetitions. If MAX_ITERATION does not equal zero, the USART repeats the character as many times as the value loaded in MAX_ITERATION. When the USART repetition number reaches MAX_ITERATION, the ITERATION bit is set in the Channel Status Register (CSR). If the repetition of the character is acknowledged by the receiver, the repetitions are stopped and the iteration counter is cleared. The ITERATION bit in CSR can be cleared by writing the Control Register with the RSIT bit at 1. 26.7.5.6 Disable Successive Receive NACK The receiver can limit the number of successive NACKs sent back to the remote transmitter. This is programmed by setting the bit DSNACK in the Mode Register (MR). The maximum number of NACK transmitted is programmed in the MAX_ITERATION field. As soon as 328 32058H–AVR32–03/09 AT32UC3A MAX_ITERATION is reached, the character is considered as correct, an acknowledge is sent on the line and the ITERATION bit in the Channel Status Register is set. 26.7.5.7 Protocol T = 1 When operating in ISO7816 protocol T = 1, the transmission is similar to an asynchronous format with only one stop bit. The parity is generated when transmitting and checked when receiving. Parity error detection sets the PARE bit in the Channel Status Register (CSR). 26.7.6 IrDA Mode The USART features an IrDA mode supplying half-duplex point-to-point wireless communication. It embeds the modulator and demodulator which allows a glueless connection to the infrared transceivers, as shown in Figure 26-33 on page 329. The modulator and demodulator are compliant with the IrDA specification version 1.1 and support data transfer speeds ranging from 2.4 Kb/s to 115.2 Kb/s. The USART IrDA mode is enabled by setting the MODE field in the Mode Register (MR) to the value 0x8. The IrDA Filter Register (IFR) allows configuring the demodulator filter. The USART transmitter and receiver operate in a normal asynchronous mode and all parameters are accessible. Note that the modulator and the demodulator are activated. Figure 26-33. Connection to IrDA Transceivers USART Receiver Demodulator RXD RX TX Transmitter Modulator TXD IrDA Transceivers The receiver and the transmitter must be enabled or disabled according to the direction of the transmission to be managed. 26.7.6.1 IrDA Modulation For baud rates up to and including 115.2 Kbits/sec, the RZI modulation scheme is used. “0” is represented by a light pulse of 3/16th of a bit time. Some examples of signal pulse duration are shown in Table 26-9 on page 329. Table 26-9. Baud Rate 2.4 Kb/s 9.6 Kb/s 19.2 Kb/s IrDA Pulse Duration Pulse Duration (3/16) 78.13 µs 19.53 µs 9.77 µs 329 32058H–AVR32–03/09 AT32UC3A Table 26-9. Baud Rate 38.4 Kb/s 57.6 Kb/s 115.2 Kb/s IrDA Pulse Duration Pulse Duration (3/16) 4.88 µs 3.26 µs 1.63 µs Figure 26-34 on page 330 shows an example of character transmission. Figure 26-34. IrDA Modulation Start Bit Transmitter Output 0 1 0 1 Data Bits 0 0 1 1 0 Stop Bit 1 TXD Bit Period 3 16 Bit Period 26.7.6.2 IrDA Baud Rate Table 26-10 on page 330 gives some examples of CD values, baud rate error and pulse duration. Note that the requirement on the maximum acceptable error of ±1.87% must be met. Table 26-10. IrDA Baud Rate Error Peripheral Clock 3 686 400 20 000 000 32 768 000 40 000 000 3 686 400 20 000 000 32 768 000 40 000 000 3 686 400 20 000 000 32 768 000 40 000 000 3 686 400 20 000 000 32 768 000 40 000 000 Baud Rate 115 200 115 200 115 200 115 200 57 600 57 600 57 600 57 600 38 400 38 400 38 400 38 400 19 200 19 200 19 200 19 200 CD 2 11 18 22 4 22 36 43 6 33 53 65 12 65 107 130 Baud Rate Error 0.00% 1.38% 1.25% 1.38% 0.00% 1.38% 1.25% 0.93% 0.00% 1.38% 0.63% 0.16% 0.00% 0.16% 0.31% 0.16% Pulse Time 1.63 1.63 1.63 1.63 3.26 3.26 3.26 3.26 4.88 4.88 4.88 4.88 9.77 9.77 9.77 9.77 330 32058H–AVR32–03/09 AT32UC3A Table 26-10. IrDA Baud Rate Error (Continued) Peripheral Clock 3 686 400 20 000 000 32 768 000 40 000 000 3 686 400 20 000 000 32 768 000 Baud Rate 9 600 9 600 9 600 9 600 2 400 2 400 2 400 CD 24 130 213 260 96 521 853 Baud Rate Error 0.00% 0.16% 0.16% 0.16% 0.00% 0.03% 0.04% Pulse Time 19.53 19.53 19.53 19.53 78.13 78.13 78.13 26.7.6.3 IrDA Demodulator The demodulator is based on the IrDA Receive filter comprised of an 8-bit down counter which is loaded with the value programmed in IFR. When a falling edge is detected on the RXD pin, the Filter Counter starts counting down at the CLK_USART speed. If a rising edge is detected on the RXD pin, the counter stops and is reloaded with IFR. If no rising edge is detected when the counter reaches 0, the input of the receiver is driven low during one bit time. Figure 26-35 on page 331 illustrates the operations of the IrDA demodulator. Figure 26-35. IrDA Demodulator Operations CLK_USART RXD Counter Value 6 5 4 3 2 6 6 5 4 3 2 1 0 Pulse Accepted Receiver Input Pulse Rejected Driven Low During 16 Baud Rate Clock Cycles As the IrDA mode uses the same logic as the ISO7816, note that the FI_DI_RATIO field in FIDI must be set to a value higher than 0 in order to assure IrDA communications operate correctly. 331 32058H–AVR32–03/09 AT32UC3A 26.7.7 RS485 Mode The USART features the RS485 mode to enable line driver control. While operating in RS485 mode, the USART behaves as though in asynchronous or synchronous mode and configuration of all the parameters is possible. The difference is that the RTS pin is driven high when the transmitter is operating. The behavior of the RTS pin is controlled by the TXEMPTY bit. A typical connection of the USART to a RS485 bus is shown in Figure 26-36 on page 332. Figure 26-36. Typical Connection to a RS485 Bus USART RXD TXD RTS Differential Bus The USART is set in RS485 mode by programming the MODE field in the Mode Register (MR) to the value 0x1. The RTS pin is at a level inverse to the TXEMPTY bit. Significantly, the RTS pin remains high when a timeguard is programmed so that the line can remain driven after the last character completion. Figure 26-37 on page 332 gives an example of the RTS waveform during a character transmission when the timeguard is enabled. Figure 26-37. Example of RTS Drive with Timeguard TG = 4 Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit Write US_THR TXRDY TXEMPTY RTS 332 32058H–AVR32–03/09 AT32UC3A 26.7.8 SPI Mode The Serial Peripheral Interface (SPI) Mode is a synchronous serial data link that provides communication with external devices in Master or Slave Mode. It also enables communication between processors if an external processor is connected to the system. The Serial Peripheral Interface is essentially a shift register that serially transmits data bits to other SPIs. During a data transfer, one SPI system acts as the “master” which controls the data flow, while the other devices act as “slaves'' which have data shifted into and out by the master. Different CPUs can take turns being masters and one master may simultaneously shift data into multiple slaves. (Multiple Master Protocol is the opposite of Single Master Protocol, where one CPU is always the master while all of the others are always slaves.) However, only one slave may drive its output to write data back to the master at any given time. A slave device is selected when its NSS signal is asserted by the master. The USART in SPI Master mode can address only one SPI Slave because it can generate only one NSS signal. The SPI system consists of two data lines and two control lines: • Master Out Slave In (MOSI): This data line supplies the output data from the master shifted into the input of the slave. • Master In Slave Out (MISO): This data line supplies the output data from a slave to the input of the master. • Serial Clock (CLK): This control line is driven by the master and regulates the flow of the data bits. The master may transmit data at a variety of baud rates. The CLK line cycles once for each bit that is transmitted. • Slave Select (NSS): This control line allows the master to select or deselect the slave. 26.7.8.1 Modes of Operation The USART can operate in Master Mode or in Slave Mode. Operation in SPI Master Mode is programmed by writing at 0xE the MODE field in the Mode Register. In this case the SPI lines must be connected as described below: • the MOSI line is driven by the output pin TXD • the MISO line drives the input pin RXD • the CLK line is driven by the output pin CLK • the NSS line is driven by the output pin RTS Operation in SPI Slave Mode is programmed by writing at 0xF the MODE field in the Mode Register. In this case the SPI lines must be connected as described below: • the MOSI line drives the input pin RXD • the MISO line is driven by the output pin TXD • the CLK line drives the input pin CLK • the NSS line drives the input pin CTS In order to avoid unpredicted behavior, any change of the SPI Mode must be followed by a software reset of the transmitter and of the receiver (except the initial configuration after a hardware reset). 333 32058H–AVR32–03/09 AT32UC3A 26.7.8.2 Baud Rate In SPI Mode, the baudrate generator operates in the same way as in USART synchronous mode: See Section “26.7.1.4” on page 307. However, there are some restrictions: In SPI Master Mode: • the external clock CLK must not be selected (USCLKS … 0x3), and the bit CLKO must be set to “1” in the Mode Register (MR), in order to generate correctly the serial clock on the CLK pin. • to obtain correct behavior of the receiver and the transmitter, the value programmed in CD of must be superior or equal to 4. • if the internal clock divided (CLK_USART/DIV) is selected, the value programmed in CD must be even to ensure a 50:50 mark/space ratio on the CLK pin, this value can be odd if the internal clock is selected (CLK_USART). In SPI Slave Mode: • the external clock (CLK) selection is forced regardless of the value of the USCLKS field in the Mode Register (MR). Likewise, the value written in BRGR has no effect, because the clock is provided directly by the signal on the USART CLK pin. • to obtain correct behavior of the receiver and the transmitter, the external clock (CLK) frequency must be at least 4 times lower than the system clock. 26.7.8.3 Data Transfer Up to 9 data bits are successively shifted out on the TXD pin at each rising or falling edge (depending of CPOL and CPHA) of the programmed serial clock. There is no Start bit, no Parity bit and no Stop bit. The number of data bits is selected by the CHRL field and the MODE 9 bit in the Mode Register (MR). The 9 bits are selected by setting the MODE 9 bit regardless of the CHRL field. The MSB data bit is always sent first in SPI Mode (Master or Slave). Four combinations of polarity and phase are available for data transfers. The clock polarity is programmed with the CPOL bit in the Mode Register. The clock phase is programmed with the CPHA bit. These two parameters determine the edges of the clock signal upon which data is driven and sampled. Each of the two parameters has two possible states, resulting in four possible combinations that are incompatible with one another. Thus, a master/slave pair must use the same parameter pair values to communicate. If multiple slaves are used and fixed in different configurations, the master must reconfigure itself each time it needs to communicate with a different slave. Table 26-11. SPI Bus Protocol Mode SPI Bus Protocol Mode 0 1 2 3 CPOL 0 0 1 1 CPHA 1 0 1 0 334 32058H–AVR32–03/09 AT32UC3A Figure 26-38. SPI Transfer Format (CPHA=1, 8 bits per transfer) CLK cycle (for reference) CLK (CPOL= 0) 1 2 3 4 5 6 7 8 CLK (CPOL= 1) MOSI SPI Master ->TXD SPI Slave ->RXD MSB 6 5 4 3 2 1 LSB MISO SPI Master ->RXD SPI Slave ->TXD MSB 6 5 4 3 2 1 LSB NSS SPI Master ->RTS SPI Slave ->CTS Figure 26-39. SPI Transfer Format (CPHA=0, 8 bits per transfer) CLK cycle (for reference) CLK (CPOL= 0) 1 2 3 4 5 6 7 8 CLK (CPOL= 1) MOSI SPI Master -> TXD SPI Slave -> RXD MSB 6 5 4 3 2 1 LSB MISO SPI Master -> RXD SPI Slave -> TXD MSB 6 5 4 3 2 1 LSB NSS SPI Master -> RTS SPI Slave -> CTS 26.7.8.4 Receiver and Transmitter Control See Section “26.7.2” on page 309. 335 32058H–AVR32–03/09 AT32UC3A 26.7.8.5 Character Transmission The characters are sent by writing in the Transmit Holding Register (THR). The transmitter reports two status bits in the Channel Status Register (CSR): TXRDY (Transmitter Ready), which indicates that THR is empty and TXEMPTY, which indicates that all the characters written in THR have been processed. When the current character processing is completed, the last character written in THR is transferred into the Shift Register of the transmitter and THR becomes empty, thus TXRDY rises. Both TXRDY and TXEMPTY bits are low when the transmitter is disabled. Writing a character in THR while TXRDY is low has no effect and the written character is lost. If the USART is in SPI Slave Mode and if a character must be sent while the Transmit Holding Register (THR) is empty, the UNRE (Underrun Error) bit is set. The TXD transmission line stays at high level during all this time. The UNRE bit is cleared by writing the Control Register (CR) with the RSTSTA (Reset Status) bit at 1. In SPI Master Mode, the slave select line (NSS) is asserted at low level 1 Tbit before the transmission of the MSB bit and released at high level 1 Tbit after the transmission of the LSB bit. So, the slave select line (NSS) is always released between each character transmission and a minimum delay of 3 Tbits always inserted. However, in order to address slave devices supporting the CSAAT mode (Chip Select Active After Transfer), the slave select line (NSS) can be forced at low level by writing the Control Register (CR) with the RTSEN bit at 1. The slave select line (NSS) can be released at high level only by writing the Control Register (CR) with the RTSDIS bit at 1 (for example, when all data have been transferred to the slave device). In SPI Slave Mode, the transmitter does not require a falling edge of the slave select line (NSS) to initiate a character transmission but only a low level. However, this low level must be present on the slave select line (NSS) at least 1 Tbit before the first serial clock cycle corresponding to the MSB bit. 26.7.8.6 Character Reception When a character reception is completed, it is transferred to the Receive Holding Register (RHR) and the RXRDY bit in the Status Register (CSR) rises. If a character is completed while RXRDY is set, the OVRE (Overrun Error) bit is set. The last character is transferred into RHR and overwrites the previous one. The OVRE bit is cleared by writing the Control Register (CR) with the RSTSTA (Reset Status) bit at 1. To ensure correct behavior of the receiver in SPI Slave Mode, the master device sending the frame must ensure a minimum delay of 1 Tbit between each character transmission. The receiver does not require a falling edge of the slave select line (NSS) to initiate a character reception but only a low level. However, this low level must be present on the slave select line (NSS) at least 1 Tbit before the first serial clock cycle corresponding to the MSB bit. 26.7.8.7 Receiver Timeout Because the receiver baudrate clock is active only during data transfers in SPI Mode, a receiver timeout is impossible in this mode, whatever the Time-out value is (field TO) in the Time-out Register (RTOR). 336 32058H–AVR32–03/09 AT32UC3A 26.7.9 Test Modes The USART can be programmed to operate in three different test modes. The internal loopback capability allows on-board diagnostics. In the loopback mode the USART interface pins are disconnected or not and reconfigured for loopback internally or externally. 26.7.9.1 Normal Mode Normal mode connects the RXD pin on the receiver input and the transmitter output on the TXD pin. Figure 26-40. Normal Mode Configuration RXD Receiver TXD Transmitter 26.7.9.2 Automatic Echo Mode Automatic echo mode allows bit-by-bit retransmission. When a bit is received on the RXD pin, it is sent to the TXD pin, as shown in Figure 26-41 on page 337. Programming the transmitter has no effect on the TXD pin. The RXD pin is still connected to the receiver input, thus the receiver remains active. Figure 26-41. Automatic Echo Mode Configuration RXD Receiver TXD Transmitter 26.7.9.3 Local Loopback Mode Local loopback mode connects the output of the transmitter directly to the input of the receiver, as shown in Figure 26-42 on page 337. The TXD and RXD pins are not used. The RXD pin has no effect on the receiver and the TXD pin is continuously driven high, as in idle state. Figure 26-42. Local Loopback Mode Configuration RXD Receiver Transmitter 1 TXD 337 32058H–AVR32–03/09 AT32UC3A 26.7.9.4 Remote Loopback Mode Remote loopback mode directly connects the RXD pin to the TXD pin, as shown in Figure 26-43 on page 338. The transmitter and the receiver are disabled and have no effect. This mode allows bit-by-bit retransmission. Figure 26-43. Remote Loopback Mode Configuration Receiver 1 RXD TXD Transmitter 338 32058H–AVR32–03/09 AT32UC3A 26.8 26.8.1 Universal Synchronous/Asynchronous Receiver/Transmitter (USART) User Interface Register Mapping Register Mapping Register Control Register Mode Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register Channel Status Register Receiver Holding Register Transmitter Holding Register Baud Rate Generator Register Receiver Time-out Register Transmitter Timeguard Register Reserved FI DI Ratio Register Number of Errors Register Reserved IrDA Filter Register Manchester Encoder Decoder Register Reserved Version Register Reserved Name CR MR IER IDR IMR CSR RHR THR BRGR RTOR TTGR – FIDI NER – IFR MAN – VERSION – Access Write-only Read-write Write-only Write-only Read-only Read-only Read-only Write-only Read-write Read-write Read-write – Read-write Read-only – Read-write Read-write – Read-only – Reset – – – – 0x0 – 0x0 – 0x0 0x0 0x0 – 0x174 – – 0x0 0x30011004 – 0x–(3) – Table 26-12. Offset 0x0000 0x0004 0x0008 0x000C 0x0010 0x0014 0x0018 0x001C 0x0020 0x0024 0x0028 0x2C - 0x3C 0x0040 0x0044 0x0048 0x004C 0x0050 0x5C - 0xF8 0xFC 0x5C - 0xFC 3. Values in the Version Register vary with the version of the IP block implementation. 339 32058H–AVR32–03/09 AT32UC3A 26.8.2 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 RETTO 7 TXDIS USART Control Register CR Write-only 0x0 30 – 22 – 14 RSTNACK 6 TXEN 29 – 21 – 13 RSTIT 5 RXDIS 28 – 20 – 12 SENDA 4 RXEN 27 – 19 RTSDIS/RCS 11 STTTO 3 RSTTX 26 – 18 RTSEN/FCS 10 STPBRK 2 RSTRX 25 – 17 – 9 STTBRK 1 – 24 – 16 – 8 RSTSTA 0 – • RTSDIS/RCS: Request to Send Disable/Release SPI Chip Select – If USART does not operate in SPI Master Mode (MODE … 0xE): 0: No effect. 1: Drives the pin RTS to 1. – If USART operates in SPI Master Mode (MODE = 0xE): RCS = 0: No effect. RCS = 1: Releases the Slave Select Line NSS (RTS pin). • RTSEN/FCS: Request to Send Enable/Force SPI Chip Select – If USART does not operate in SPI Master Mode (MODE … 0xE): 0: No effect. 1: Drives the pin RTS to 0. – If USART operates in SPI Master Mode (MODE = 0xE): FCS = 0: No effect. FCS = 1: Forces the Slave Select Line NSS (RTS pin) to 0, even if USART is no transmitting, in order to address SPI slave devices supporting the CSAAT Mode (Chip Select Active After Transfer). • RETTO: Rearm Time-out 0: No effect 1: Restart Time-out • RSTNACK: Reset Non Acknowledge 0: No effect 1: Resets NACK in CSR. 340 32058H–AVR32–03/09 AT32UC3A • RSTIT: Reset Iterations 0: No effect. 1: Resets ITERATION in CSR. No effect if the ISO7816 is not enabled. • SENDA: Send Address 0: No effect. 1: In Multidrop Mode only, the next character written to the THR is sent with the address bit set. • STTTO: Start Time-out 0: No effect. 1: Starts waiting for a character before clocking the time-out counter. Resets the status bit TIMEOUT in CSR. • STPBRK: Stop Break 0: No effect. 1: Stops transmission of the break after a minimum of one character length and transmits a high level during 12-bit periods. No effect if no break is being transmitted. • STTBRK: Start Break 0: No effect. 1: Starts transmission of a break after the characters present in THR and the Transmit Shift Register have been transmitted. No effect if a break is already being transmitted. • RSTSTA: Reset Status Bits 0: No effect. 1: Resets the status bits PARE, FRAME, OVRE, MANERR and RXBRK in CSR. • TXDIS: Transmitter Disable 0: No effect. 1: Disables the transmitter. • TXEN: Transmitter Enable 0: No effect. 1: Enables the transmitter if TXDIS is 0. • RXDIS: Receiver Disable 0: No effect. 1: Disables the receiver. • RXEN: Receiver Enable 0: No effect. 1: Enables the receiver, if RXDIS is 0. • RSTTX: Reset Transmitter 0: No effect. 341 32058H–AVR32–03/09 AT32UC3A 1: Resets the transmitter. • RSTRX: Reset Receiver 0: No effect. 1: Resets the receiver. 342 32058H–AVR32–03/09 AT32UC3A 26.8.3 Name: Access Type: Offset: Reset Value: USART Mode Register MR Read-write 0x4 - 31 ONEBIT 23 – 15 30 MODSYNC 22 VAR_SYNC 14 29 MAN 21 DSNACK 13 NBSTOP 28 FILTER 20 INACK 12 27 – 19 OVER 11 26 25 MAX_ITERATION 17 MODE9 9 24 18 CLKO 10 PAR 2 MODE 16 MSBF/CPOL 8 SYNC/CPHA 0 CHMODE 7 CHRL 6 5 4 USCLKS 3 1 • ONEBIT: Start Frame Delimiter Selector 0: Start Frame delimiter is COMMAND or DATA SYNC. 1: Start Frame delimiter is One Bit. • MODSYNC: Manchester Synchronization Mode 0:The Manchester Start bit is a 0 to 1 transition 1: The Manchester Start bit is a 1 to 0 transition. • MAN: Manchester Encoder/Decoder Enable 0: Manchester Encoder/Decoder are disabled. 1: Manchester Encoder/Decoder are enabled. • FILTER: Infrared Receive Line Filter 0: The USART does not filter the receive line. 1: The USART filters the receive line using a three-sample filter (1/16-bit clock) (2 over 3 majority). • MAX_ITERATION Defines the maximum number of iterations in mode ISO7816, protocol T= 0. • VAR_SYNC: Variable Synchronization of Command/Data Sync Start Frame Delimiter 0: User defined configuration of command or data sync field depending on SYNC value. 1: The sync field is updated when a character is written into THR register. • DSNACK: Disable Successive NACK 0: NACK is sent on the ISO line as soon as a parity error occurs in the received character (unless INACK is set). 343 32058H–AVR32–03/09 AT32UC3A 1: Successive parity errors are counted up to the value specified in the MAX_ITERATION field. These parity errors generate a NACK on the ISO line. As soon as this value is reached, no additional NACK is sent on the ISO line. The flag ITERATION is asserted. • INACK: Inhibit Non Acknowledge 0: The NACK is generated. 1: The NACK is not generated. • OVER: Oversampling Mode 0: 16x Oversampling. 1: 8x Oversampling. • CLKO: Clock Output Select 0: The USART does not drive the CLK pin. 1: The USART drives the CLK pin if USCLKS does not select the external clock CLK. • MODE9: 9-bit Character Length 0: CHRL defines character length. 1: 9-bit character length. • MSBF/CPOL: Bit Order or SPI Clock Polarity – If USART does not operate in SPI Mode (MODE … 0xE and 0xF): MSBF = 0: Least Significant Bit is sent/received first. MSBF = 1: Most Significant Bit is sent/received first. – If USART operates in SPI Mode (Slave or Master, MODE = 0xE or 0xF): CPOL = 0: The inactive state value of SPCK is logic level zero. CPOL = 1: The inactive state value of SPCK is logic level one. CPOL is used to determine the inactive state value of the serial clock (SPCK). It is used with CPHA to produce the required clock/data relationship between master and slave devices. • CHMODE: Channel Mode CHMODE 0 0 1 1 0 1 0 1 Mode Description Normal Mode Automatic Echo. Receiver input is connected to the TXD pin. Local Loopback. Transmitter output is connected to the Receiver Input.. Remote Loopback. RXD pin is internally connected to the TXD pin. • NBSTOP: Number of Stop Bits NBSTOP 0 0 Asynchronous (SYNC = 0) 1 stop bit Synchronous (SYNC = 1) 1 stop bit 344 32058H–AVR32–03/09 AT32UC3A 0 1 1 1 0 1 1.5 stop bits 2 stop bits Reserved Reserved 2 stop bits Reserved • PAR: Parity Type PAR 0 0 0 0 1 1 0 0 1 1 0 1 0 1 0 1 x x Parity Type Even parity Odd parity Parity forced to 0 (Space) Parity forced to 1 (Mark) No parity Multidrop mode • SYNC/CPHA: Synchronous Mode Select or SPI Clock Phase – If USART does not operate in SPI Mode (MODE is … 0xE and 0xF): SYNC = 0: USART operates in Asynchronous Mode. SYNC = 1: USART operates in Synchronous Mode. – If USART operates in SPI Mode (MODE = 0xE or 0xF): CPHA = 0: Data is changed on the leading edge of SPCK and captured on the following edge of SPCK. CPHA = 1: Data is captured on the leading edge of SPCK and changed on the following edge of SPCK. CPHA determines which edge of SPCK causes data to change and which edge causes data to be captured. CPHA is used with CPOL to produce the required clock/data relationship between master and slave devices. • CHRL: Character Length. CHRL 0 0 1 1 0 1 0 1 Character Length 5 bits 6 bits 7 bits 8 bits • USCLKS: Clock Selection USCLKS 0 0 1 1 0 1 0 1 Selected Clock CLK_USART CLK_USART/DIV (DIV = xx) Reserved CLK 345 32058H–AVR32–03/09 AT32UC3A • MODE MODE 0 0 0 0 0 1 1 1 0 0 0 1 1 0 1 1 Others 0 0 1 0 1 0 1 1 0 1 0 0 0 0 0 1 Mode of the USART Normal RS485 Hardware Handshaking IS07816 Protocol: T = 0 IS07816 Protocol: T = 1 IrDA SPI Master SPI Slave Reserved 346 32058H–AVR32–03/09 AT32UC3A 26.8.4 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 USART Interrupt Enable Register IER Write-only 0x8 30 – 22 – 14 29 – 21 – 13 NACK 5 OVRE 28 – 20 MANE 12 RXBUFF 4 ENDTX 27 – 19 CTSIC 11 TXBUFE 3 ENDRX 26 25 24 MANEA 16 – 8 TIMEOUT 0 RXRDY 18 – 10 ITER/UNRE 2 RXBRK 17 – 9 TXEMPTY 1 TXRDY 7 PARE 6 FRAME • MANEA: Manchester Error Interrupt Enable • MANE: Manchester Error Interrupt Enable • CTSIC: Clear to Send Input Change Interrupt Enable • NACK: Non Acknowledge Interrupt Enable • RXBUFF: Buffer Full Interrupt Enable • TXBUFE: Buffer Empty Interrupt Enable • ITER/UNRE: Iteration or SPI Underrun Error Interrupt Enable • TXEMPTY: TXEMPTY Interrupt Enable • TIMEOUT: Time-out Interrupt Enable • PARE: Parity Error Interrupt Enable • FRAME: Framing Error Interrupt Enable • OVRE: Overrun Error Interrupt Enable • ENDTX: End of Transmit Interrupt Enable • ENDRX: End of Receive Transfer Interrupt Enable • RXBRK: Receiver Break Interrupt Enable • TXRDY: TXRDY Interrupt Enable • RXRDY: RXRDY Interrupt Enable 347 32058H–AVR32–03/09 AT32UC3A 26.8.5 Name: USART Interrupt Disable Register IDR 348 32058H–AVR32–03/09 AT32UC3A Access Type: Offset: Reset Value: 31 – 23 – 15 Write-only 0xC 30 – 22 – 14 29 28 27 26 25 24 MANEA 16 – 8 TIMEOUT 0 RXRDY 21 – 13 NACK 5 OVRE 20 MANE 12 RXBUFF 4 ENDTX 19 CTSIC 11 TXBUFE 3 ENDRX 18 – 10 ITER/UNRE 2 RXBRK 17 – 9 TXEMPTY 1 TXRDY 7 PARE 6 FRAME • MANEA: Manchester Error Interrupt Disable • MANE: Manchester Error Interrupt Disable • CTSIC: Clear to Send Input Change Interrupt Disable • NACK: Non Acknowledge Interrupt Disable • RXBUFF: Buffer Full Interrupt Disable • TXBUFE: Buffer Empty Interrupt Disable • ITER/UNRE: Iteration or SPI Underrun Error Interrupt Enable • TXEMPTY: TXEMPTY Interrupt Disable • TIMEOUT: Time-out Interrupt Disable • PARE: Parity Error Interrupt Disable • FRAME: Framing Error Interrupt Disable • OVRE: Overrun Error Interrupt Disable • ENDTX: End of Transmit Interrupt Disable • ENDRX: End of Receive Transfer Interrupt Disable • RXBRK: Receiver Break Interrupt Disable • TXRDY: TXRDY Interrupt Disable • RXRDY: RXRDY Interrupt Disable 349 32058H–AVR32–03/09 AT32UC3A 26.8.6 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 USART Interrupt Mask Register IMR Read-only 0x10 0x00000000 30 – 22 – 14 29 28 27 26 25 24 MANEA 16 – 8 TIMEOUT 0 RXRDY 21 – 13 NACK 5 OVRE 20 MANE 12 RXBUFF 4 ENDTX 19 CTSIC 11 TXBUFE 3 ENDRX 18 – 10 ITER/UNRE 2 RXBRK 17 – 9 TXEMPTY 1 TXRDY 7 PARE 6 FRAME • MANEA: Manchester Error Interrupt Mask • MANE: Manchester Error Interrupt Mask • CTSIC: Clear to Send Input Change Interrupt Mask • NACK: Non Acknowledge Interrupt Mask • RXBUFF: Buffer Full Interrupt Mask • TXBUFE: Buffer Empty Interrupt Mask • ITER/UNRE: Iteration or SPI Underrun Error Interrupt Enable • TXEMPTY: TXEMPTY Interrupt Mask • TIMEOUT: Time-out Interrupt Mask • PARE: Parity Error Interrupt Mask • FRAME: Framing Error Interrupt Mask • OVRE: Overrun Error Interrupt Mask • ENDTX: End of Transmit Interrupt Mask • ENDRX: End of Receive Transfer Interrupt Mask • RXBRK: Receiver Break Interrupt Mask • TXRDY: TXRDY Interrupt Mask • RXRDY: RXRDY Interrupt Mask 350 32058H–AVR32–03/09 AT32UC3A 26.8.7 Name: USART Channel Status Register CSR 351 32058H–AVR32–03/09 AT32UC3A Access Type: Offset: Reset Value: 31 – 23 CTS 15 Read-only 0x14 30 – 22 – 14 29 28 27 26 25 24 MANERR 16 – 8 TIMEOUT 0 RXRDY 21 – 13 NACK 5 OVRE 20 – 12 RXBUFF 4 ENDTX 19 CTSIC 11 TXBUFE 3 ENDRX 18 – 10 ITER/UNRE 2 RXBRK 17 – 9 TXEMPTY 1 TXRDY 7 PARE 6 FRAME • MANERR: Manchester Error 0: No Manchester error has been detected since the last RSTSTA. 1: At least one Manchester error has been detected since the last RSTSTA. • CTS: Image of CTS Input 0: CTS is at 0. 1: CTS is at 1. • CTSIC: Clear to Send Input Change Flag 0: No input change has been detected on the CTS pin since the last read of CSR. 1: At least one input change has been detected on the CTS pin since the last read of CSR. • NACK: Non Acknowledge 0: No Non Acknowledge has not been detected since the last RSTNACK. 1: At least one Non Acknowledge has been detected since the last RSTNACK. • RXBUFF: Reception Buffer Full 0: The signal Buffer Full from the Receive PDC channel is inactive. 1: The signal Buffer Full from the Receive PDC channel is active. • TXBUFE: Transmission Buffer Empty 0: The signal Buffer Empty from the Transmit PDC channel is inactive. 1: The signal Buffer Empty from the Transmit PDC channel is active. • ITER/UNRE: Max number of Repetitions Reached or SPI Underrun Error – If USART does not operate in SPI Slave Mode (MODE … 0xF): ITER = 0: Maximum number of repetitions has not been reached since the last RSTSTA. ITER = 1: Maximum number of repetitions has been reached since the last RSTSTA. 352 32058H–AVR32–03/09 AT32UC3A – If USART operates in SPI Slave Mode (MODE = 0xF): UNRE = 0: No SPI underrun error has occurred since the last RSTSTA. UNRE = 1: At least one SPI underrun error has occurred since the last RSTSTA. • TXEMPTY: Transmitter Empty 0: There are characters in either THR or the Transmit Shift Register, or the transmitter is disabled. TXEMPTY == 1: Means that the Transmit Shift Register is empty and that there is no data in THR. • TIMEOUT: Receiver Time-out 0: There has not been a time-out since the last Start Time-out command (STTTO in CR) or the Time-out Register is 0. 1: There has been a time-out since the last Start Time-out command (STTTO in CR). • PARE: Parity Error 0: No parity error has been detected since the last RSTSTA. 1: At least one parity error has been detected since the last RSTSTA. • FRAME: Framing Error 0: No stop bit has been detected low since the last RSTSTA. 1: At least one stop bit has been detected low since the last RSTSTA. • OVRE: Overrun Error 0: No overrun error has occurred since the last RSTSTA. 1: At least one overrun error has occurred since the last RSTSTA. • ENDTX: End of Transmitter Transfer 0: The End of Transfer signal from the Transmit PDC channel is inactive. 1: The End of Transfer signal from the Transmit PDC channel is active. • ENDRX: End of Receiver Transfer 0: The End of Transfer signal from the Receive PDC channel is inactive. 1: The End of Transfer signal from the Receive PDC channel is active. • RXBRK: Break Received/End of Break 0: No Break received or End of Break detected since the last RSTSTA. 1: Break Received or End of Break detected since the last RSTSTA. • TXRDY: Transmitter Ready 0: A character is in the THR waiting to be transferred to the Transmit Shift Register, or an STTBRK command has been requested, or the transmitter is disabled. As soon as the transmitter is enabled, TXRDY becomes 1. 1: There is no character in the THR. • RXRDY: Receiver Ready 0: No complete character has been received since the last read of RHR or the receiver is disabled. If characters were being received when the receiver was disabled, RXRDY changes to 1 when the receiver is enabled. 353 32058H–AVR32–03/09 AT32UC3A 1: At least one complete character has been received and RHR has not yet been read. 354 32058H–AVR32–03/09 AT32UC3A 26.8.8 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 RXSYNH 7 USART Receive Holding Register RHR Read-only 0x18 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 RXCHR 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 RXCHR 0 • RXSYNH: Received Sync 0: Last Character received is a Data. 1: Last Character received is a Command. • RXCHR: Received Character Last character received if RXRDY is set. 355 32058H–AVR32–03/09 AT32UC3A 26.8.9 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 TXSYNH 7 USART Transmit Holding Register THR Write-only 0x1C 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 TXCHR 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 TXCHR 0 • TXSYNH: Sync Field to be transmitted 0: The next character sent is encoded as a data. Start Frame Delimiter is DATA SYNC. 1: The next character sent is encoded as a command. Start Frame Delimiter is COMMAND SYNC. • TXCHR: Character to be Transmitted Next character to be transmitted after the current character if TXRDY is not set. 356 32058H–AVR32–03/09 AT32UC3A 26.8.10 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 USART Baud Rate Generator Register BRGR Read-write 0x20 0x00000000 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 CD 27 – 19 – 11 26 – 18 25 – 17 FP– 9 24 – 16 10 8 7 6 5 4 CD 3 2 1 0 • FP: Fractional Part 0: Fractional divider is disabled. 1 - 7: Baudrate resolution, defined by FP x 1/8. • CD: Clock Divider MODE ≠ ISO7816 SYNC = 1 or MODE = SPI (Master or Slave) OVER = 1 Baud Rate Clock Disabled Baud Rate = Selected Clock/16/CD Baud Rate = Selected Clock/8/CD Baud Rate = Selected Clock /CD Baud Rate = Selected Clock/CD/FI_DI_RATIO MODE = ISO7816 SYNC = 0 CD 0 1 to 65535 OVER = 0 357 32058H–AVR32–03/09 AT32UC3A 26.8.11 Name: Access Type: Offset: Reset Value: 31 USART Receiver Time-out Register RTOR Read-write 0x24 0x00000000 30 29 28 27 26 25 24 – 23 – 15 – 22 – 14 – 21 – 13 – 20 – 12 TO – 19 – 11 – 18 – 10 – 17 – 9 – 16 – 8 7 6 5 4 TO 3 2 1 0 • TO: Time-out Value 0: The Receiver Time-out is disabled. 1 - 65535: The Receiver Time-out is enabled and the Time-out delay is TO x Bit Period. 358 32058H–AVR32–03/09 AT32UC3A 26.8.12 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 USART Transmitter Timeguard Register TTGR Read-write 0x28 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 TG 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • TG: Timeguard Value 0: The Transmitter Timeguard is disabled. 1 - 255: The Transmitter timeguard is enabled and the timeguard delay is TG x Bit Period. 359 32058H–AVR32–03/09 AT32UC3A 26.8.13 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 USART FI DI RATIO Register FIDI Read-write 0x40 0x00000174 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 FI_DI_RATIO 27 – 19 – 11 – 3 26 – 18 – 10 25 – 17 – 9 FI_DI_RATIO 1 24 – 16 – 8 2 0 • FI_DI_RATIO: FI Over DI Ratio Value 0: If ISO7816 mode is selected, the Baud Rate Generator generates no signal. 1 - 2047: If ISO7816 mode is selected, the Baud Rate is the clock provided on CLK divided by FI_DI_RATIO. 360 32058H–AVR32–03/09 AT32UC3A 26.8.14 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 USART Number of Errors Register NER Read-only 0x44 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 NB_ERRORS 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • NB_ERRORS: Number of Errors Total number of errors that occurred during an ISO7816 transfer. This register automatically clears when read. 361 32058H–AVR32–03/09 AT32UC3A 26.8.15 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 USART IrDA FILTER Register IFR Read-write 0x4C 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 IRDA_FILTER 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • IRDA_FILTER: IrDA Filter Sets the filter of the IrDA demodulator. 362 32058H–AVR32–03/09 AT32UC3A 26.8.16 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 – USART Manchester Configuration Register MAN Read-write 0x50 0x30011004 30 DRIFT 22 – 14 – 6 – 29 1 21 – 13 – 5 – 28 RX_MPOL 20 – 12 TX_MPOL 4 – 27 – 19 26 – 18 RX_PL 11 – 3 10 – 2 TX_PL 9 TX_PP 1 0 8 25 RX_PP 17 16 24 • DRIFT: Drift compensation 0: The USART can not recover from an important clock drift 1: The USART can recover from clock drift. The 16X clock mode must be enabled. • RX_MPOL: Receiver Manchester Polarity 0: Logic Zero is coded as a zero-to-one transition, Logic One is coded as a one-to-zero transition. 1: Logic Zero is coded as a one-to-zero transition, Logic One is coded as a zero-to-one transition. • RX_PP: Receiver Preamble Pattern detected RX_PP 0 0 1 1 0 1 0 1 Preamble Pattern default polarity assumed (RX_MPOL field not set) ALL_ONE ALL_ZERO ZERO_ONE ONE_ZERO • RX_PL: Receiver Preamble Length 0: The receiver preamble pattern detection is disabled 1 - 15: The detected preamble length is RX_PL x Bit Period • TX_MPOL: Transmitter Manchester Polarity 0: Logic Zero is coded as a zero-to-one transition, Logic One is coded as a one-to-zero transition. 1: Logic Zero is coded as a one-to-zero transition, Logic One is coded as a zero-to-one transition. 363 32058H–AVR32–03/09 AT32UC3A • TX_PP: Transmitter Preamble Pattern TX_PP 0 0 1 1 0 1 0 1 Preamble Pattern default polarity assumed (TX_MPOL field not set) ALL_ONE ALL_ZERO ZERO_ONE ONE_ZERO • TX_PL: Transmitter Preamble Length 0: The Transmitter Preamble pattern generation is disabled 1 - 15: The Preamble Length is TX_PL x Bit Period 364 32058H–AVR32–03/09 AT32UC3A 26.8.17 Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 USART Version Register VERSION Read-only 0xFC 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 VERSION 27 – 19 – 11 26 – 18 25 – 17 VARIANT 9 VERSION 3 2 1 0 24 – 16 10 8 • VARIANT Reserved. No functionality associated. • VERSION Version of the module. No functionality associated. 365 32058H–AVR32–03/09 AT32UC3A 27. Static Memory Controller (SMC) Rev. 1.0.0.0 27.1 Features • • • • • • • • • • • • 4 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 27.2 Overview The Static Memory Controller (SMC) generates the signals that control the access to the external memory devices or peripheral devices. It has 4 Chip Selects and a 26-bit address bus. The 32-bit data bus can be configured to interface with 8-, or16-, or 32-bit external devices. Separate read and write control signals allow for direct memory and peripheral interfacing. Read and write signal waveforms are fully parametrizable. The SMC can manage wait requests from external devices to extend the current access. The SMC is provided with an automatic slow clock mode. In slow clock mode, it switches from userprogrammed waveforms to slow-rate specific waveforms on read and write signals. The SMC supports asynchronous burst read in page mode access for page size up to 32 bytes. 366 32058H–AVR32–03/09 AT32UC3A 27.3 Block Diagram Figure 27-1. Block Diagram GPIO Controller NCS[5:0] NCS[5:0] Bus Matrix SMC Chip Select NRD NWR0/NWE A0/NBS0 A0/NBS0 SMC NWR1/NBS1 A1/NWR2/NBS2 PM CLK_SMC NWR3/NBS3 A[25:2] A[25:2] D[31:0] D[31:0] NWAIT NWAIT NWR1/NBS1 A1/NWR2/NBS2 NWR3/NBS3 NRD NWR0/NWE User Interface Peripheral Bus 27.4 I/O Lines Description I/O Line Description Description Static Memory Controller Chip Select Lines Read Signal Write 0/Write Enable Signal Address Bit 0/Byte 0 Select Signal Write 1/Byte 1 Select Signal Address Bit 1/Write 2/Byte 2 Select Signal Write 3/Byte 3 Select Signal Address Bus Data Bus External Wait Signal Type Output Output Output Output Output Output Output Output I/O Input Low Active Level Low Low Low Low Low Low Low Table 27-1. Name NCS[3:0] NRD NWR0/NWE A0/NBS0 NWR1/NBS1 A1/NWR2/NBS2 NWR3/NBS3 A[25:2] D[31:0] NWAIT 367 32058H–AVR32–03/09 AT32UC3A 27.5 27.5.1 Product Dependencies EBI I/O Lines The Static Memory Controller signals pass througth the EBI module where they are multiplexed. The programmer must first configure the GPIO controller to assign the EBI pins corresponding to SMC signals to their peripheral function. If I/O lines of the EBI corresponding to SMC signals are not used by the application, they can be used for other purposes by the GPIO Controller. 27.6 27.6.1 Functionnal Description Application Example Hardware Interface 27.6.1.1 Figure 27-2. SMC Connections to Static Memory Devices D0-D31 A0/NBS0 NWR0/NWE NWR1/NBS1 A1/NWR2/NBS2 NWR3/NBS3 D0-D7 128K x 8 SRAM D0-D7 CS A0-A16 A2-A18 D8-D15 128K x 8 SRAM D0-D7 CS A0-A16 A2-A18 NRD NCS0 NCS1 NCS2 NCS3 NCS4 NCS5 NWR0/NWE OE WE NRD NWR1/NBS1 OE WE A2-A25 D16-D23 128K x 8 SRAM D0-D7 CS A0-A16 A2-A18 D24-D31 128K x 8 SRAM D0-D7 CS A0-A16 A2-A18 NRD A1/NWR2/NBS2 OE WE Static Memory Controller NRD OE NWR3/NBS3 WE 27.6.2 External Memory Mapping The SMC provides up to 26 address lines, A[25:0]. This allows each chip select line to address up to 64 Mbytes of memory. 368 32058H–AVR32–03/09 AT32UC3A If the physical memory device connected on one chip select is smaller than 64 Mbytes, it wraps around and appears to be repeated within this space. The SMC correctly handles any valid access to the memory device within the page (see Figure 27-3). A[25:0] is only significant for 8-bit memory, A[25:1] is used for 16-bit memory, A[25:2] is used for 32-bit memory. Figure 27-3. Memory Connections for 6 External Devices NCS[0] - NCS[5] NRD SMC NWE A[25:0] D[31:0] NCS5 NCS4 NCS3 NCS2 NCS1 NCS0 Memory Enable Memory Enable Memory Enable Memory Enable Memory Enable Memory Enable Output Enable Write Enable A[25:0] 8 or 16 or 32 D[31:0] or D[15:0] or D[7:0] 27.6.3 27.6.3.1 Connection to External Devices Data Bus Width A data bus width of 8, 16 or 32 bits can be selected for each chip select. This option is controlled by the field DBW in MODE (Mode Register) for the corresponding chip select. Figure 27-4 shows how to connect a 512K x 8-bit memory on NCS2. Figure 27-5 shows how to connect a 512K x 16-bit memory on NCS2. Figure 27-6 shows two 16-bit memories connected as a single 32-bit memory. 27.6.3.2 Byte Write or Byte Select Access Each chip select with a 16-bit or 32-bit data bus can operate with one of two different types of write access: byte write or byte select access. This is controlled by the BAT field of the MODE register for the corresponding chip select. 369 32058H–AVR32–03/09 AT32UC3A Figure 27-4. Memory Connection for an 8-bit Data Bus D[7:0] A[18:2] A0 SMC A1 NWE NRD NCS[2] D[7:0] A[18:2] A0 A1 Write Enable Output Enable Memory Enable Figure 27-5. Memory Connection for a 16-bit Data Bus D[15:0] A[19:2] A1 SMC NBS0 NBS1 NWE NRD NCS[2] D[15:0] A[18:1] A[0] Low Byte Enable High Byte Enable Write Enable Output Enable Memory Enable Figure 27-6. Memory Connection for a 32-bit Data Bus D[31:16] D[15:0] A[20:2] D[31:16] D[15:0] A[18:0] Byte 0 Enable Byte 1 Enable Byte 2 Enable Byte 3 Enable Write Enable Output Enable Memory Enable SMC NBS0 NBS1 NBS2 NBS3 NWE NRD NCS[2] 370 32058H–AVR32–03/09 AT32UC3A – Byte Write Access Byte write access supports one byte write signal per byte of the data bus and a single read signal. Note that the SMC does not allow boot in Byte Write Access mode. • For 16-bit devices: the SMC provides NWR0 and NWR1 write signals for respectively byte0 (lower byte) and byte1 (upper byte) of a 16-bit bus. One single read signal (NRD) is provided. Byte Write Access is used to connect 2 x 8-bit devices as a 16-bit memory. • For 32-bit devices: NWR0, NWR1, NWR2 and NWR3, are the write signals of byte0 (lower byte), byte1, byte2 and byte 3 (upper byte) respectively. One single read signal (NRD) is provided. Byte Write Access is used to connect 4 x 8-bit devices as a 32-bit memory. Byte Write option is illustrated on Figure 27-7. – Byte Select Access In this mode, read/write operations can be enabled/disabled at a byte level. One byte-select line per byte of the data bus is provided. One NRD and one NWE signal control read and write. • For 16-bit devices: the SMC provides NBS0 and NBS1 selection signals for respectively byte0 (lower byte) and byte1 (upper byte) of a 16-bit bus. Byte Select Access is used to connect one 16-bit device. • For 32-bit devices: NBS0, NBS1, NBS2 and NBS3, are the selection signals of byte0 (lower byte), byte1, byte2 and byte 3 (upper byte) respectively. Byte Select Access is used to connect two 16-bit devices. Figure 27-8 shows how to connect two 16-bit devices on a 32-bit data bus in Byte Select Access mode, on NCS3 (BAT = Byte Select Access). 371 32058H–AVR32–03/09 AT32UC3A Figure 27-7. Connection of 2 x 8-bit Devices on a 16-bit Bus: Byte Write Option D[7:0] D[15:8] A[24:2] A[23:1] A[0] Write Enable Read Enable Memory Enable D[7:0] SMC A1 NWR0 NWR1 NRD NCS[3] D[15:8] A[23:1] A[0] Write Enable Read Enable Memory Enable – Signal Multiplexing Depending on the BAT, only the write signals or the byte select signals are used. To save IOs at the external bus interface, control signals at the SMC interface are multiplexed. For 32-bit devices, bits A0 and A1 are unused. For 16-bit devices, bit A0 of address is unused. When Byte Select Option is selected, NWR1 to NWR3 are unused. When Byte Write option is selected, NBS0 to NBS3 are unused. 372 32058H–AVR32–03/09 AT32UC3A Figure 27-8. Connection of 2x16-bit Data Bus on a 32-bit Data Bus (Byte Select Option) D[15:0] D[31:16] A[25:2] NWE NBS0 NBS1 A[23:0] Write Enable Low Byte Enable High Byte Enable D[15:0] SMC NBS2 NBS3 NRD NCS[3] Read Enable Memory Enable D[31:16] A[23:0] Write Enable Low Byte Enable High Byte Enable Read Enable Memory Enable Table 27-2. Signal Name Device Type SMC Multiplexed Signal Translation 32-bit Bus 1x32-bit Byte Select NBS0 NWE NBS1 NBS2 NBS3 2x16-bit Byte Select NBS0 NWE NBS1 NBS2 NBS3 NWR0 NWR1 NWR2 NWR3 4 x 8-bit Byte Write 16-bit Bus 1x16-bit Byte Select NBS0 NWE NBS1 A1 NWR0 NWR1 A1 A1 2 x 8-bit Byte Write A0 NWE 8-bit Bus 1 x 8-bit Byte Access Type (BAT) NBS0_A0 NWE_NWR0 NBS1_NWR1 NBS2_NWR2_A1 NBS3_NWR3 27.6.4 Standard Read and Write Protocols In the following sections, the byte access type is not considered. Byte select lines (NBS0 to NBS3) always have the same timing as the A address bus. NWE represents either the NWE signal in byte select access type or one of the byte write lines (NWR0 to NWR3) in byte write access type. NWR0 to NWR3 have the same timings and protocol as NWE. In the same way, NCS represents one of the NCS[0..3] chip select lines. 373 32058H–AVR32–03/09 AT32UC3A 27.6.4.1 Read Waveforms The read cycle is shown on Figure 27-9. The read cycle starts with the address setting on the memory address bus, i.e.: {A[25:2], A1, A0} for 8-bit devices {A[25:2], A1} for 16-bit devices A[25:2] for 32-bit devices. Figure 27-9. Standard Read Cycle CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS D[15:0] NRD_SETUP NRD_PULSE NRD_HOLD NCS_RD_SETUP NCS_RD_PULSE NRD_CYCLE NCS_RD_HOLD – NRD Waveform The NRD signal is characterized by a setup timing, a pulse width and a hold timing. 1. NRD_SETUP: the NRD setup time is defined as the setup of address before the NRD falling edge; 2. NRD_PULSE: the NRD pulse length is the time between NRD falling edge and NRD rising edge; 3. NRD_HOLD: the NRD hold time is defined as the hold time of address after the NRD rising edge. 374 32058H–AVR32–03/09 AT32UC3A – NCS Waveform Similarly, the NCS signal can be divided into a setup time, pulse length and hold time: 1. NCS_RD_SETUP: the NCS setup time is defined as the setup time of address before the NCS falling edge. 2. NCS_RD_PULSE: the NCS pulse length is the time between NCS falling edge and NCS rising edge; 3. NCS_RD_HOLD: the NCS hold time is defined as the hold time of address after the NCS rising edge. – Read Cycle The NRD_CYCLE time is defined as the total duration of the read cycle, i.e., from the time where address is set on the address bus to the point where address may change. The total read cycle time is equal to: NRD_CYCLE = NRD_SETUP + NRD_PULSE + NRD_HOLD = NCS_RD_SETUP + NCS_RD_PULSE + NCS_RD_HOLD All NRD and NCS timings are defined separately for each chip select as an integer number of Master Clock cycles. To ensure that the NRD and NCS timings are coherent, user must define the total read cycle instead of the hold timing. NRD_CYCLE implicitly defines the NRD hold time and NCS hold time as: NRD_HOLD = NRD_CYCLE - NRD SETUP - NRD PULSE NCS_RD_HOLD = NRD_CYCLE - NCS_RD_SETUP - NCS_RD_PULSE – Null Delay Setup and Hold If null setup and hold parameters are programmed for NRD and/or NCS, NRD and NCS remain active continuously in case of consecutive read cycles in the same memory (see Figure 27-10). 375 32058H–AVR32–03/09 AT32UC3A Figure 27-10. No Setup, No Hold On NRD and NCS Read Signals CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS D[15:0] NRD_SETUP NRD_PULSE NRD_PULSE NCS_RD_PULSE NCS_RD_PULSE NCS_RD_PULSE NRD_CYCLE NRD_CYCLE NRD_CYCLE – Null Pulse Programming null pulse is not permitted. Pulse must be at least set to 1. A null value leads to unpredictable behavior. 27.6.4.2 Read Mode As NCS and NRD waveforms are defined independently of one other, the SMC needs to know when the read data is available on the data bus. The SMC does not compare NCS and NRD timings to know which signal rises first. The READ_MODE parameter in the MODE register of the corresponding chip select indicates which signal of NRD and NCS controls the read operation. – Read is Controlled by NRD (READ_MODE = 1): Figure 27-11 shows the waveforms of a read operation of a typical asynchronous RAM. The read data is available tPACC after the falling edge of NRD, and turns to ‘Z’ after the rising edge of NRD. In this case, the READ_MODE must be set to 1 (read is controlled by NRD), to indicate that data is available with the rising edge of NRD. The SMC samples the read data internally on the rising edge of Master Clock that generates the rising edge of NRD, whatever the programmed waveform of NCS may be. 376 32058H–AVR32–03/09 AT32UC3A Figure 27-11. READ_MODE = 1: Data is sampled by SMC before the rising edge of NRD CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS tPACC D[15:0] Data Sampling – Read is Controlled by NCS (READ_MODE = 0) Figure 27-12 shows the typical read cycle of an LCD module. The read data is valid tPACC after the falling edge of the NCS signal and remains valid until the rising edge of NCS. Data must be sampled when NCS is raised. In that case, the READ_MODE must be set to 0 (read is controlled by NCS): the SMC internally samples the data on the rising edge of Master Clock that generates the rising edge of NCS, whatever the programmed waveform of NRD may be. 377 32058H–AVR32–03/09 AT32UC3A Figure 27-12. READ_MODE = 0: Data is sampled by SMC before the rising edge of NCS CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS tPACC D[15:0] Data Sampling 27.6.4.3 Write Waveforms The write protocol is similar to the read protocol. It is depicted in Figure 27-13. The write cycle starts with the address setting on the memory address bus. – NWE Waveforms The NWE signal is characterized by a setup timing, a pulse width and a hold timing. 1. NWE_SETUP: the NWE setup time is defined as the setup of address and data before the NWE falling edge; 2. NWE_PULSE: The NWE pulse length is the time between NWE falling edge and NWE rising edge; 3. NWE_HOLD: The NWE hold time is defined as the hold time of address and data after the NWE rising edge. The NWE waveforms apply to all byte-write lines in Byte Write access mode: NWR0 to NWR3. 27.6.4.4 NCS Waveforms The NCS signal waveforms in write operation are not the same that those applied in read operations, but are separately defined: 1. NCS_WR_SETUP: the NCS setup time is defined as the setup time of address before the NCS falling edge. 2. NCS_WR_PULSE: the NCS pulse length is the time between NCS falling edge and NCS rising edge; 3. NCS_WR_HOLD: the NCS hold time is defined as the hold time of address after the NCS rising edge. 378 32058H–AVR32–03/09 AT32UC3A Figure 27-13. Write Cycle CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE NCS NWE_SETUP NCS_WR_SETUP NWE_PULSE NWE_HOLD NCS_WR_PULSE NWE_CYCLE NCS_WR_HOLD – Write Cycle The write_cycle time is defined as the total duration of the write cycle, that is, from the time where address is set on the address bus to the point where address may change. The total write cycle time is equal to: NWE_CYCLE = NWE_SETUP + NWE_PULSE + NWE_HOLD = NCS_WR_SETUP + NCS_WR_PULSE + NCS_WR_HOLD All NWE and NCS (write) timings are defined separately for each chip select as an integer number of Master Clock cycles. To ensure that the NWE and NCS timings are coherent, the user must define the total write cycle instead of the hold timing. This implicitly defines the NWE hold time and NCS (write) hold times as: NWE_HOLD = NWE_CYCLE - NWE_SETUP - NWE_PULSE NCS_WR_HOLD = NWE_CYCLE - NCS_WR_SETUP - NCS_WR_PULSE – Null Delay Setup and Hold If null setup parameters are programmed for NWE and/or NCS, NWE and/or NCS remain active continuously in case of consecutive write cycles in the same memory (see Figure 27-14). However, for devices that perform write operations on the rising edge of NWE or NCS, such as SRAM, either a setup or a hold must be programmed. 379 32058H–AVR32–03/09 AT32UC3A Figure 27-14. Null Setup and Hold Values of NCS and NWE in Write Cycle CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE, NWE0, NWE1 NCS D[15:0] NWE_SETUP NWE_PULSE NWE_PULSE NCS_WR_SETUP NCS_WR_PULSE NCS_WR_PULSE NWE_CYCLE NWE_CYCLE NWE_CYCLE – Null Pulse Programming null pulse is not permitted. Pulse must be at least set to 1. A null value leads to unpredictable behavior. 27.6.4.5 Write Mode The WRITE_MODE parameter in the MODE register of the corresponding chip select indicates which signal controls the write operation. – Write is Controlled by NWE (WRITE_MODE = 1): Figure 27-15 shows the waveforms of a write operation with WRITE_MODE set to 1. The data is put on the bus during the pulse and hold steps of the NWE signal. The internal data buffers are turned out after the NWE_SETUP time, and until the end of the write cycle, regardless of the programmed waveform on NCS. 380 32058H–AVR32–03/09 AT32UC3A Figure 27-15. WRITE_MODE = 1. The write operation is controlled by NWE CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE, NWR0, NWR1 NCS D[15:0] – Write is Controlled by NCS (WRITE_MODE = 0) Figure 27-16 shows the waveforms of a write operation with WRITE_MODE set to 0. The data is put on the bus during the pulse and hold steps of the NCS signal. The internal data buffers are turned out after the NCS_WR_SETUP time, and until the end of the write cycle, regardless of the programmed waveform on NWE. Figure 27-16. WRITE_MODE = 0. The write operation is controlled by NCS CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE, NWR0, NWR1 NCS D[15:0] 27.6.4.6 Coding Timing Parameters All timing parameters are defined for one chip select and are grouped together in one REGISTER according to their type. 381 32058H–AVR32–03/09 AT32UC3A The SETUP register groups the definition of all setup parameters: • NRD_SETUP, NCS_RD_SETUP, NWE_SETUP, NCS_WR_SETUP The PULSE register groups the definition of all pulse parameters: • NRD_PULSE, ncs_rd_pULSE, nwe_pULSE, ncs_wr_pULSE The CYCLE register groups the definition of all cycle parameters: • NRD_CYCLE, NWE_CYCLEe Table 27-3 shows how the timing parameters are coded and their permitted range. Table 27-3. Coding and Range of Timing Parameters Permitted Range Coded Value setup [5:0] pulse [6:0] cycle [8:0] Number of Bits 6 7 9 Effective Value 128 x setup[5] + setup[4:0] 256 x pulse[6] + pulse[5:0] 256 x cycle[8:7] + cycle[6:0] Coded Value 0 ≤ ≤ 31 0 ≤ ≤ 63 0 ≤ ≤ 127 Effective Value 128 ≤ ≤ 128+31 256 ≤ ≤ 256+63 256 ≤ ≤ 256+127 512 ≤ ≤ 512+127 768 ≤ ≤ 768+127 27.6.4.7 Usage Restriction The SMC does not check the validity of the user-programmed parameters. If the sum of SETUP and PULSE parameters is larger than the corresponding CYCLE parameter, this leads to unpredictable behavior of the SMC. For read operations: Null but positive setup and hold of address and NRD and/or NCS can not be guaranteed at the memory interface because of the propagation delay of theses signals through external logic and pads. If positive setup and hold values must be verified, then it is strictly recommended to program non-null values so as to cover possible skews between address, NCS and NRD signals. For write operations: If a null hold value is programmed on NWE, the SMC can guarantee a positive hold of address, byte select lines, and NCS signal after the rising edge of NWE. This is true for WRITE_MODE = 1 only. See ”Early Read Wait State” on page 385. For read and write operations: a null value for pulse parameters is forbidden and may lead to unpredictable behavior. In read and write cycles, the setup and hold time parameters are defined in reference to the address bus. For external devices that require setup and hold time between NCS and NRD signals (read), or between NCS and NWE signals (write), these setup and hold times must be converted into setup and hold times in reference to the address bus. 27.6.5 Automatic Wait States Under certain circumstances, the SMC automatically inserts idle cycles between accesses to avoid bus contention or operation conflict. 382 32058H–AVR32–03/09 AT32UC3A 27.6.5.1 Chip Select Wait States The SMC always inserts an idle cycle between 2 transfers on separate chip selects. This idle cycle ensures that there is no bus contention between the de-activation of one device and the activation of the next one. During chip select wait state, all control lines are turned inactive: NBS0 to NBS3, NWR0 to NWR3, NCS[0..5], NRD lines are all set to 1. Figure 27-17 illustrates a chip select wait state between access on Chip Select 0 and Chip Select 2. 383 32058H–AVR32–03/09 AT32UC3A Figure 27-17. Chip Select Wait State between a Read Access on NCS0 and a Write Access on NCS2 CLK_SMC A[25:2] S0, NBS1, A0, A1 NRD NWE NCS0 NCS2 NRD_CYCLE D[15:0] NWE_CYCLE Read to Write Wait State Chip Select Wait State 384 32058H–AVR32–03/09 AT32UC3A 27.6.5.2 Early Read Wait State In some cases, the SMC inserts a wait state cycle between a write access and a read access to allow time for the write cycle to end before the subsequent read cycle begins. This wait state is not generated in addition to a chip select wait state. The early read cycle thus only occurs between a write and read access to the same memory device (same chip select). • An early read wait state is automatically inserted if at least one of the following conditions is valid: • if the write controlling signal has no hold time and the read controlling signal has no setup time (Figure 27-18). • in NCS write controlled mode (WRITE_MODE = 0), if there is no hold timing on the NCS signal and the NCS_RD_SETUP parameter is set to 0, regardless of the read mode (Figure 27-19). The write operation must end with a NCS rising edge. Without an Early Read Wait State, the write operation could not complete properly. • in NWE controlled mode (WRITE_MODE = 1) and if there is no hold timing (NWE_HOLD = 0), the feedback of the write control signal is used to control address, data, chip select and byte select lines. If the external write control signal is not inactivated as expected due to load capacitances, an Early Read Wait State is inserted and address, data and control signals are maintained one more cycle. See Figure 27-20. Figure 27-18. Early Read Wait State: Write with No Hold Followed by Read with No Setup. CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE NRD No hold No setup D[15:0] Write cycle Early Read Wait state Read cycle 385 32058H–AVR32–03/09 AT32UC3A Figure 27-19. Early Read Wait State: NCS Controlled Write with No Hold Followed by a Read with No Setup. CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE NRD No hold D[15:0] No setup Write cycle (WRITE_MODE=0) Read cycle Early Read Wait state (READ_MODE=0 or READ_MODE=1) 386 32058H–AVR32–03/09 AT32UC3A Figure 27-20. Early Read Wait State: NWE-controlled Write with No Hold Followed by a Read with one Set-up Cycle. CLK_SMC A[25:2] NBS0, NBS1, A0, A1 Internal write controlling signal external write controlling signal(NWE) No hold NRD Read setup=1 D[15:0] Write cycle (WRITE_MODE = 1) Early Read Wait state Read cycle (READ_MODE=0 or READ_MODE=1) 27.6.5.3 Reload User Configuration Wait State The user may change any of the configuration parameters by writing the SMC user interface. When detecting that a new user configuration has been written in the user interface, the SMC inserts a wait state before starting the next access. The so called “Reload User Configuration Wait State” is used by the SMC to load the new set of parameters to apply to next accesses. The Reload Configuration Wait State is not applied in addition to the Chip Select Wait State. If accesses before and after re-programming the user interface are made to different devices (Chip Selects), then one single Chip Select Wait State is applied. On the other hand, if accesses before and after writing the user interface are made to the same device, a Reload Configuration Wait State is inserted, even if the change does not concern the current Chip Select. – User Procedure To insert a Reload Configuration Wait State, the SMC detects a write access to any MODE register of the user interface. If the user only modifies timing registers (SETUP, PULSE, CYCLE registers) in the user interface, he must validate the modification by writing the MODE, even if no change was made on the mode parameters. – Slow Clock Mode Transition A Reload Configuration Wait State is also inserted when the Slow Clock Mode is entered or exited, after the end of the current transfer (see ”Slow Clock Mode” on page 398). 387 32058H–AVR32–03/09 AT32UC3A 27.6.5.4 Read to Write Wait State Due to an internal mechanism, a wait cycle is always inserted between consecutive read and write SMC accesses. This wait cycle is referred to as a read to write wait state in this document. This wait cycle is applied in addition to chip select and reload user configuration wait states when they are to be inserted. See Figure 27-17 on page 384. 27.6.6 Data Float Wait States Some memory devices are slow to release the external bus. For such devices, it is necessary to add wait states (data float wait states) after a read access: • before starting a read access to a different external memory • before starting a write access to the same device or to a different external one. The Data Float Output Time (t DF ) for each external memory device is programmed in the TDF_CYCLES field of the MODE register for the corresponding chip select. The value of TDF_CYCLES indicates the number of data float wait cycles (between 0 and 15) before the external device releases the bus, and represents the time allowed for the data output to go to high impedance after the memory is disabled. Data float wait states do not delay internal memory accesses. Hence, a single access to an external memory with long t DF w ill not slow down the execution of a program from internal memory. The data float wait states management depends on the READ_MODE and the TDF_MODE fields of the MODE register for the corresponding chip select. 27.6.6.1 READ_MODE Setting the READ_MODE to 1 indicates to the SMC that the NRD signal is responsible for turning off the tri-state buffers of the external memory device. The Data Float Period then begins after the rising edge of the NRD signal and lasts TDF_CYCLES MCK cycles. When the read operation is controlled by the NCS signal (READ_MODE = 0), the TDF field gives the number of MCK cycles during which the data bus remains busy after the rising edge of NCS. Figure 27-21 illustrates the Data Float Period in NRD-controlled mode (READ_MODE =1), assuming a data float period of 2 cycles (TDF_CYCLES = 2). Figure 27-22 shows the read operation when controlled by NCS (READ_MODE = 0) and the TDF_CYCLES parameter equals 3. 388 32058H–AVR32–03/09 AT32UC3A Figure 27-21. TDF Period in NRD Controlled Read Access (TDF = 2) CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS tPACC D[15:0] TDF = 2 clock cycles NRD controlled read operation Figure 27-22. TDF Period in NCS Controlled Read Operation (TDF = 3) CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NRD NCS tPACC D[15:0] TDF = 3 clock cycles NCS controlled read operation 389 32058H–AVR32–03/09 AT32UC3A 27.6.6.2 TDF Optimization Enabled (TDF_MODE = 1) When the TDF_MODE of the MODE register is set to 1 (TDF optimization is enabled), the SMC takes advantage of the setup period of the next access to optimize the number of wait states cycle to insert. Figure 27-23 shows a read access controlled by NRD, followed by a write access controlled by NWE, on Chip Select 0. Chip Select 0 has been programmed with: NRD_HOLD = 4; READ_MODE = 1 (NRD controlled) NWE_SETUP = 3; WRITE_MODE = 1 (NWE controlled) TDF_CYCLES = 6; TDF_MODE = 1 (optimization enabled). Figure 27-23. TDF Optimization: No TDF wait states are inserted if the TDF period is over when the next access begins CLK_SMC A[25:2] NRD NRD_HOLD = 4 NWE NWE_SETUP = 3 NCS0 TDF_CYCLES = 6 D[15:0] Read access on NCS0 (NRD controlled) Read to Write Wait State write access on NCS0 (NWE controlled) 27.6.6.3 TDF Optimization Disabled (TDF_MODE = 0) When optimization is disabled, tdf wait states are inserted at the end of the read transfer, so that the data float period is ended when the second access begins. If the hold period of the read1 controlling signal overlaps the data float period, no additional tdf wait states will be inserted. Figure 27-24, Figure 27-25 and Figure 27-26 illustrate the cases: • read access followed by a read access on another chip select, • read access followed by a write access on another chip select, 390 32058H–AVR32–03/09 AT32UC3A • read access followed by a write access on the same chip select, with no TDF optimization. Figure 27-24. TDF Optimization Disabled (TDF Mode = 0). TDF wait states between 2 read accesses on different chip selects. C LK_SMC A[25:2] NBS0, NBS1, A0, A1 Read1 controlling signal(NRD) Read2 controlling signal(NRD) D[15:0] Read1 hold = 1 Read2 setup = 1 TDF_CYCLES = 6 5 TDF WAIT STATES Read1 cycle TDF_CYCLES = 6 Chip Select Wait State Read 2 cycle TDF_MODE=0 (optimization disabled) Figure 27-25. TDF Mode = 0: TDF wait states between a read and a write access on different chip selects. CLK_SMC A[25:2] NBS0, NBS1, A0, A1 Read1 controlling signal(NRD) Read1 hold = 1 Write2 setup = 1 Write2 controlling signal(NWE) TDF_CYCLES = 4 D[15:0] Read1 cycle TDF_CYCLES = 4 Read to Write Chip Select Wait State Wait State 2 TDF WAIT STATES Write 2 cycle TDF_MODE=0 (optimization disabled) 391 32058H–AVR32–03/09 AT32UC3A Figure 27-26. TDF Mode = 0: TDF wait states between read and write accesses on the same chip select. CLK_SMC A[25:2] NBS0, NBS1, A0, A1 Read1 controlling signal(NRD) Read1 hold = 1 Write2 setup = 1 Write2 controlling signal(NWE) TDF_CYCLES = 5 D[15:0] 4 TDF WAIT STATES Read1 cycle TDF_CYCLES = 5 Read to Write Wait State Write 2 cycle TDF_MODE=0 (optimization disabled) 27.6.7 External Wait Any access can be extended by an external device using the NWAIT input signal of the SMC. The EXNW_MODE field of the MODE register on the corresponding chip select must be set to either to “10” (frozen mode) or “11” (ready mode). When the EXNW_MODE is set to “00” (disabled), the NWAIT signal is simply ignored on the corresponding chip select. The NWAIT signal delays the read or write operation in regards to the read or write controlling signal, depending on the read and write modes of the corresponding chip select. 27.6.7.1 Restriction When one of the EXNW_MODE is enabled, it is mandatory to program at least one hold cycle for the read/write controlling signal. For that reason, the NWAIT signal cannot be used in Page Mode (”Asynchronous Page Mode” on page 400), or in Slow Clock Mode (”Slow Clock Mode” on page 398). The NWAIT signal is assumed to be a response of the external device to the read/write request of the SMC. Then NWAIT is examined by the SMC only in the pulse state of the read or write controlling signal. The assertion of the NWAIT signal outside the expected period has no impact on SMC behavior. 392 32058H–AVR32–03/09 AT32UC3A 27.6.7.2 Frozen Mode When the external device asserts the NWAIT signal (active low), and after internal synchronization of this signal, the SMC state is frozen, i.e., SMC internal counters are frozen, and all control signals remain unchanged. When the resynchronized NWAIT signal is deasserted, the SMC completes the access, resuming the access from the point where it was stopped. See Figure 2727. This mode must be selected when the external device uses the NWAIT signal to delay the access and to freeze the SMC. The assertion of the NWAIT signal outside the expected period is ignored as illustrated in Figure 27-28. Figure 27-27. Write Access with NWAIT Assertion in Frozen Mode (EXNW_MODE = 10). CLK_SMC A[25:2] NBS0, NBS1, A0, A1 FROZEN STATE 4 NWE 6 NCS 5 4 3 2 2 2 2 0 3 2 1 1 1 1 0 D[15:0] NWAIT Internally synchronized NWAIT signal Write cycle EXNW_MODE = 10 (Frozen) WRITE_MODE = 1 (NWE_controlled) NWE_PULSE = 5 NCS_WR_PULSE = 7 393 32058H–AVR32–03/09 AT32UC3A Figure 27-28. Read Access with NWAIT Assertion in Frozen Mode (EXNW_MODE = 10). CLK_SMC A[25:2] NBS0, NBS1, A0, A1 FROZEN STATE NCS 4 3 2 2 2 1 0 2 1 NRD 0 5 5 5 4 3 2 1 0 1 0 NWAIT Internally synchronized NWAIT signal Read cycle EXNW_MODE = 10 (Frozen) READ_MODE = 0 (NCS_controlled) NRD_PULSE = 2, NRD_HOLD = 6 NCS_RD_PULSE = 5, NCS_RD_HOLD = 3 Assertion is ignored 394 32058H–AVR32–03/09 AT32UC3A 27.6.7.3 Ready Mode In Ready mode (EXNW_MODE = 11), the SMC behaves differently. Normally, the SMC begins the access by down counting the setup and pulse counters of the read/write controlling signal. In the last cycle of the pulse phase, the resynchronized NWAIT signal is examined. If asserted, the SMC suspends the access as shown in Figure 27-29 and Figure 27-30. After deassertion, the access is completed: the hold step of the access is performed. This mode must be selected when the external device uses deassertion of the NWAIT signal to indicate its ability to complete the read or write operation. If the NWAIT signal is deasserted before the end of the pulse, or asserted after the end of the pulse of the controlling read/write signal, it has no impact on the access length as shown in Figure 27-30. Figure 27-29. NWAIT Assertion in Write Access: Ready Mode (EXNW_MODE = 11). CLK _SM C A [2 5 :2 ] NBS0, NBS1, A0, A1 FRO ZEN STATE 4 NW E 6 NCS 5 4 3 2 1 1 1 0 3 2 1 0 0 0 D [1 5 :0 ] N W A IT In te rn a lly s y n c h ro n iz e d N W A IT s ig n a l W rite c y c le E X N W _ M O D E = 1 1 (R e a d y m o d e ) W R IT E _ M O D E = 1 (N W E _ c o n tro lle d ) N W E_PU LSE = 5 N CS _W R_PU LSE = 7 395 32058H–AVR32–03/09 AT32UC3A Figure 27-30. NWAIT Assertion in Read Access: Ready Mode (EXNW_MODE = 11). CLK_SMC A[25:2] NBS0, NBS1, A0, A1 Wait STATE NCS 6 5 4 3 2 1 0 0 NRD 6 5 4 3 2 1 1 0 NWAIT Internally synchronized NWAIT signal Read cycle EXNW_MODE = 11 (Ready mode) READ_MODE = 0 (NCS_controlled) NRD_PULSE = 7 NCS_RD_PULSE = 7 Assertion is ignored Assertion is ignored 396 32058H–AVR32–03/09 AT32UC3A 27.6.7.4 NWAIT Latency and Read/write Timings There may be a latency between the assertion of the read/write controlling signal and the assertion of the NWAIT signal by the device. The programmed pulse length of the read/write controlling signal must be at least equal to this latency plus the 2 cycles of resynchronization + 1 cycle. Otherwise, the SMC may enter the hold state of the access without detecting the NWAIT signal assertion. This is true in frozen mode as well as in ready mode. This is illustrated on Figure 27-31. When EXNW_MODE is enabled (ready or frozen), the user must program a pulse length of the read and write controlling signal of at least: minimal pulse length = NWAIT latency + 2 resynchronization cycles + 1 cycle Figure 27-31. NWAIT Latency CLK_SMC A[25:2] NBS0, NBS1, A0, A1 Wait STATE 4 NRD Minimal pulse length 3 2 1 0 0 0 NWAIT nternally synchronized NWAIT signal NWAIT latency 2 cycle resynchronization Read cycle EXNW_MODE = 10 or 11 READ_MODE = 1 (NRD_controlled) NRD_PULSE = 5 397 32058H–AVR32–03/09 AT32UC3A 27.6.8 Slow Clock Mode The SMC is able to automatically apply a set of “slow clock mode” read/write waveforms when an internal signal driven by the Power Management Controller is asserted because CLK_SMC has been turned to a very slow clock rate (typically 32kHz clock rate). In this mode, the user-programmed waveforms are ignored and the slow clock mode waveforms are applied. This mode is provided so as to avoid reprogramming the User Interface with appropriate waveforms at very slow clock rate. When activated, the slow mode is active on all chip selects. 27.6.8.1 Slow Clock Mode Waveforms Figure 27-32 illustrates the read and write operations in slow clock mode. They are valid on all chip selects. indicates the value of read and write parameters in slow clock mode. Figure 27-32. Read/write Cycles in Slow Clock Mode CLK_SMC CLK_SMC A[25:2] A[25:2] NBS0, NBS1, A0, A1 NBS0, NBS1, A0, A1 NWE 1 1 1 NRD 1 1 NCS NRD_CYCLES = 2 SLOW CLOCK MODE READ NCS NWE_CYCLES = 3 SLOW CLOCK MODE WRITE Table 27-4. Read and Write Timing Parameters in Slow Clock Mode Duration (cycles) 1 1 0 2 2 Write Parameters NWE_SETUP NWE_PULSE NCS_WR_SETUP NCS_WR_PULSE NWE_CYCLE Duration (cycles) 1 1 0 3 3 Read Parameters NRD_SETUP NRD_PULSE NCS_RD_SETUP NCS_RD_PULSE NRD_CYCLE 398 32058H–AVR32–03/09 AT32UC3A 27.6.8.2 Switching from (to) Slow Clock Mode to (from) Normal Mode When switching from slow clock mode to the normal mode, the current slow clock mode transfer is completed at high clock rate, with the set of slow clock mode parameters.See Figure 27-33 on page 399. The external device may not be fast enough to support such timings. Figure 27-34 illustrates the recommended procedure to properly switch from one mode to the other. Figure 27-33. Clock Rate Transition Occurs while the SMC is Performing a Write Operation Slow Clock Mode Internal signal from PM CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE 1 1 1 1 1 1 2 3 2 NCS NWE_CYCLE = 3 SLOW CLOCK MODE WRITE SLOW CLOCK MODE WRITE NWE_CYCLE = 7 NORMAL MODE WRITE This write cycle finishes with the slow clock mode set Of parameters after the clock rate transition Slow clock mode transition is detected: Reload Configuration Wait State 399 32058H–AVR32–03/09 AT32UC3A Figure 27-34. Recommended Procedure to Switch from Slow Clock Mode to Normal Mode or from Normal Mode to Slow Clock Mode Slow Clock Mode Internal signal from PM CLK_SMC A[25:2] NBS0, NBS1, A0, A1 NWE 1 NCS 1 1 2 3 2 SLOW CLOCK MODE WRITE IDLE STATE NORMAL MODE WRITE Reload Configuration Wait State 27.6.9 Asynchronous Page Mode The SMC supports asynchronous burst reads in page mode, providing that the page mode is enabled in the MODE register (PMEN field). The page size must be configured in the MODE register (PS field) to 4, 8, 16 or 32 bytes. The page defines a set of consecutive bytes into memory. A 4-byte page (resp. 8-, 16-, 32-byte page) is always aligned to 4-byte boundaries (resp. 8-, 16-, 32-byte boundaries) of memory. The MSB of data address defines the address of the page in memory, the LSB of address define the address of the data in the page as detailed in Table 27-5. With page mode memory devices, the first access to one page (tpa) takes longer than the subsequent accesses to the page (tsa ) as shown in Figure 27-35. When in page mode, the SMC enables the user to define different read timings for the first access within one page, and next accesses within the page. Table 27-5. Page Size 4 bytes 8 bytes 16 bytes 32 bytes Notes: Page Address and Data Address within a Page Page Address(1) A[25:2] A[25:3] A[25:4] A[25:5] Data Address in the Page(2) A[1:0] A[2:0] A[3:0] A[4:0] 1. A denotes the address bus of the memory device 2. For 16-bit devices, the bit 0 of address is ignored. For 32-bit devices, bits [1:0] are ignored. 27.6.9.1 Protocol and Timings in Page Mode Figure 27-35 shows the NRD and NCS timings in page mode access. 400 32058H–AVR32–03/09 AT32UC3A Figure 27-35. Page Mode Read Protocol (Address MSB and LSB are defined in Table 27-5) CLK_SMC A[MSB] A[LSB] NRD tpa NCS tsa tsa D[15:0] NCS_RD_PULSE NRD_PULSE NRD_PULSE The NRD and NCS signals are held low during all read transfers, whatever the programmed values of the setup and hold timings in the User Interface may be. Moreover, the NRD and NCS timings are identical. The pulse length of the first access to the page is defined with the NCS_RD_PULSE field of the PULSE register. The pulse length of subsequent accesses within the page are defined using the NRD_PULSE parameter. In page mode, the programming of the read timings is described in Table 27-6: Table 27-6. Parameter READ_MODE NCS_RD_SETUP NCS_RD_PULSE NRD_SETUP NRD_PULSE NRD_CYCLE Programming of Read Timings in Page Mode Value ‘x’ ‘x’ tpa ‘x’ tsa ‘x’ Definition No impact No impact Access time of first access to the page No impact Access time of subsequent accesses in the page No impact The SMC does not check the coherency of timings. It will always apply the NCS_RD_PULSE timings as page access timing (tpa) and the NRD_PULSE for accesses to the page (tsa), even if the programmed value for tpa is shorter than the programmed value for tsa. 27.6.9.2 Byte Access Type in Page Mode The Byte Access Type configuration remains active in page mode. For 16-bit or 32-bit page mode devices that require byte selection signals, configure the BAT field of the REGISTER to 0 (byte select access type). 401 32058H–AVR32–03/09 AT32UC3A 27.6.9.3 Page Mode Restriction The page mode is not compatible with the use of the NWAIT signal. Using the page mode and the NWAIT signal may lead to unpredictable behavior. 27.6.9.4 Sequential and Non-sequential Accesses If the chip select and the MSB of addresses as defined in Table 27-5 are identical, then the current access lies in the same page as the previous one, and no page break occurs. Using this information, all data within the same page, sequential or not sequential, are accessed with a minimum access time (tsa). Figure 27-36 illustrates access to an 8-bit memory device in page mode, with 8-byte pages. Access to D1 causes a page access with a long access time (tpa). Accesses to D3 and D7, though they are not sequential accesses, only require a short access time (tsa). If the MSB of addresses are different, the SMC performs the access of a new page. In the same way, if the chip select is different from the previous access, a page break occurs. If two sequential accesses are made to the page mode memory, but separated by an other internal or external peripheral access, a page break occurs on the second access because the chip select of the device was deasserted between both accesses. Figure 27-36. Access to Non-sequential Data within the Same Page CLK_SMC A[25:3] Page address A[2], A1, A0 A1 A3 A7 NRD NCS D[7:0] NCS_RD_PULSE D1 NRD_PULSE D3 NRD_PULSE D7 402 32058H–AVR32–03/09 AT32UC3A 27.7 User Interface The SMC is programmed using the registers listed in Table 27-7. For each chip select, a set of 4 registers is used to program the parameters of the external device connected on it. In Table 27-7, “CS_number” denotes the chip select number. 16 bytes (0x10) are required per chip select. The user must complete writing the configuration by writing any one of the MODE registers. Table 27-7. SMC Register Mapping Offset 0x10 x CS_number + 0x00 0x10 x CS_number + 0x04 0x10 x CS_number + 0x08 0x10 x CS_number + 0x0C Register SMC Setup Register SMC Pulse Register SMC Cycle Register SMC Mode Register Name SETUP PULSE CYCLE MODE Access Read/Write Read/Write Read/Write Read/Write Reset State – – – – 403 32058H–AVR32–03/09 AT32UC3A 27.7.1 Setup Register SETUP[0 ..3] Read/Write 0x10 x CS_number + 0x00 – 30 – 22 – 14 – 6 – 5 4 13 12 11 21 20 29 28 27 26 25 24 NCS_RD_SETUP 19 NRD_SETUP 10 9 8 18 17 16 Register Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 – NCS_WR_SETUP 3 NWE_SETUP 2 1 0 • NCS_RD_SETUP: NCS Setup Length in READ Access In read access, the NCS signal setup length is defined as: NCS setup length = (128* NCS_RD_SETUP[5] + NCS_RD_SETUP[4:0]) clock cycles • NRD_SETUP: NRD Setup Length The NRD signal setup length is defined in clock cycles as: NRD setup length = (128* NRD_SETUP[5] + NRD_SETUP[4:0]) clock cycles • NCS_WR_SETUP: NCS Setup Length in WRITE Access In write access, the NCS signal setup length is defined as: NCS setup length = (128* NCS_WR_SETUP[5] + NCS_WR_SETUP[4:0]) clock cycles • NWE_SETUP: NWE Setup Length The NWE signal setup length is defined as: NWE setup length = (128* NWE_SETUP[5] + NWE_SETUP[4:0]) clock cycles 404 32058H–AVR32–03/09 AT32UC3A 27.7.2 Pulse Register PULSE[0..3] Read/Write 0x10 x CS_number + 0x04 – 30 29 28 27 NCS_RD_PULSE 22 21 20 19 NRD_PULSE 14 13 12 11 NCS_WR_PULSE 6 5 4 3 NWE_PULSE 2 1 0 10 9 8 18 17 16 26 25 24 Register Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 – • NCS_RD_PULSE: NCS Pulse Length in READ Access In standard read access, the NCS signal pulse length is defined as: NCS pulse length = (256* NCS_RD_PULSE[6] + NCS_RD_PULSE[5:0]) clock cycles The NCS pulse length must be at least 1 clock cycle. In page mode read access, the NCS_RD_PULSE parameter defines the duration of the first access to one page. • NRD_PULSE: NRD Pulse Length In standard read access, the NRD signal pulse length is defined in clock cycles as: NRD pulse length = (256* NRD_PULSE[6] + NRD_PULSE[5:0]) clock cycles The NRD pulse length must be at least 1 clock cycle. In page mode read access, the NRD_PULSE parameter defines the duration of the subsequent accesses in the page. • NCS_WR_PULSE: NCS Pulse Length in WRITE Access In write access, the NCS signal pulse length is defined as: NCS pulse length = (256* NCS_WR_PULSE[6] + NCS_WR_PULSE[5:0]) clock cycles The NCS pulse length must be at least 1 clock cycle. • NWE_PULSE: NWE Pulse Length The NWE signal pulse length is defined as: NWE pulse length = (256* NWE_PULSE[6] + NWE_PULSE[5:0]) clock cycles The NWE pulse length must be at least 1 clock cycle. 405 32058H–AVR32–03/09 AT32UC3A 27.7.3 Cycle Register CYCLE[0..3] Read/Write 0x10 x CS_number + 0x08 – 30 – 22 29 – 21 28 – 20 NRD_CYCLE 15 – 7 14 – 6 13 – 5 12 – 4 NWE_CYCLE 11 – 3 10 – 2 9 – 1 8 NWE_CYCLE 0 27 – 19 26 – 18 25 – 17 24 NRD_CYCLE 16 Register Name: Access Type: Offset: Reset Value: 31 – 23 • NRD_CYCLE: Total Read Cycle Length The total read cycle length is the total duration in clock cycles of the read cycle. It is equal to the sum of the setup, pulse and hold steps of the NRD and NCS signals. It is defined as: Read cycle length = (NRD_CYCLE[8:7]*256 + NRD_CYCLE[6:0]) clock cycles • NWE_CYCLE: Total Write Cycle Length The total write cycle length is the total duration in clock cycles of the write cycle. It is equal to the sum of the setup, pulse and hold steps of the NWE and NCS signals. It is defined as: Write cycle length = (NWE_CYCLE[8:7]*256 + NWE_CYCLE[6:0]) clock cycles 406 32058H–AVR32–03/09 AT32UC3A 27.7.4 MODE Register MODE[0..3] Read/Write 0x10 x CS_number + 0x0C – 30 – 22 – 14 – 6 – 5 EXNW_MODE 21 – 13 DBW 4 29 PS 20 TDF_MODE 12 11 – 3 – 10 – 2 – 28 27 – 19 26 – 18 TDF_CYCLES 9 – 1 WRITE_MOD E 8 BAT 0 READ_MODE 25 – 17 24 PMEN 16 Register Name: Access Type: Offset: Reset Value: 31 – 23 – 15 – 7 – • PS: Page Size If page mode is enabled, this field indicates the size of the page in bytes. Table 27-8. Page size settings. PS 0 0 1 1 0 1 0 1 Page Size 4-byte page 8-byte page 16-byte page 32-byte page • PMEN: Page Mode Enabled 1: Asynchronous burst read in page mode is applied on the corresponding chip select. 0: Standard read is applied. • TDF_MODE: TDF Optimization 1: TDF optimization is enabled. – The number of TDF wait states is optimized using the setup period of the next read/write access. 0: TDF optimization is disabled. – The number of TDF wait states is inserted before the next access begins. • TDF_CYCLES: Data Float Time This field gives the integer number of clock cycles required by the external device to release the data after the rising edge of the read controlling signal. The SMC always provide one full cycle of bus turnaround after the TDF_CYCLES period. The 407 32058H–AVR32–03/09 AT32UC3A external bus cannot be used by another chip select during TDF_CYCLES + 1 cycles. From 0 up to 15 TDF_CYCLES can be set. • Data Bus Width (DBW) DBW 0 0 1 1 0 1 0 1 Data Bus Width 8-bit bus 16-bit bus 32-bit bus Reserved • BAT: Byte Access Type This field is used only if DBW defines a 16- or 32-bit data bus. 1: Byte write access type: – Write operation is controlled using NCS, NWR0, NWR1, NWR2, NWR3. – Read operation is controlled using NCS and NRD. 0: Byte select access type: – Write operation is controlled using NCS, NWE, NBS0, NBS1, NBS2 and NBS3 – Read operation is controlled using NCS, NRD, NBS0, NBS1, NBS2 and NBS3 • EXNW_MODE: NWAIT Mode The NWAIT signal is used to extend the current read or write signal. It is only taken into account during the pulse phase of the read and write controlling signal. When the use of NWAIT is enabled, at least one cycle hold duration must be programmed for the read and write controlling signal. Table 27-9. EXNW_MODE EXNW_MODE 0 0 1 1 0 1 0 1 NWAIT Mode Disabled Reserved Frozen Mode Ready Mode • Disabled Mode: The NWAIT input signal is ignored on the corresponding Chip Select. • Frozen Mode: If asserted, the NWAIT signal freezes the current read or write cycle. After deassertion, the read/write cycle is resumed from the point where it was stopped. • Ready Mode: The NWAIT signal indicates the availability of the external device at the end of the pulse of the controlling read or write signal, to complete the access. If high, the access normally completes. If low, the access is extended until NWAIT returns high. • WRITE_MODE 1: The write operation is controlled by the NWE signal. – If TDF optimization is enabled (TDF_MODE =1), TDF wait states will be inserted after the setup of NWE. 0: The write operation is controlled by the NCS signal. – If TDF optimization is enabled (TDF_MODE =1), TDF wait states will be inserted after the setup of NCS. • READ_MODE: 1: The read operation is controlled by the NRD signal. 408 32058H–AVR32–03/09 AT32UC3A – If TDF cycles are programmed, the external bus is marked busy after the rising edge of NRD. – If TDF optimization is enabled (TDF_MODE =1), TDF wait states are inserted after the setup of NRD. 0: The read operation is controlled by the NCS signal. – If TDF cycles are programmed, the external bus is marked busy after the rising edge of NCS. – If TDF optimization is enabled (TDF_MODE =1), TDF wait states are inserted after the setup of NCS. 409 32058H–AVR32–03/09 AT32UC3A 28. SDRAM Controller (SDRAMC) Rev: 2.0.1.1 28.1 Features • 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 – Automatic Update of DS, TCR and PASR Parameters (Mobile SDRAM Devices) Energy-saving Capabilities – Self-refresh, Power-down and Deep Power Modes Supported – Supports Mobile SDRAM Devices Error Detection – Refresh Error Interrupt SDRAM Power-up Initialization by Software CAS Latency of 1, 2, 3 Supported Auto Precharge Command Not Used • • • • • • 28.2 Description The SDRAM Controller (SDRAMC) extends the memory capabilities of a chip by providing the interface to an external 16-bit or 32-bit SDRAM device. The page size supports ranges from 2048 to 8192 and the number of columns from 256 to 2048. It supports byte (8-bit), half-word (16-bit) and word (32-bit) accesses. The SDRAM Controller supports a read or write burst length of one location. It keeps track of the active row in each bank, thus maximizing SDRAM performance, e.g., the application may be placed in one bank and data in the other banks. So as to optimize performance, it is advisable to avoid accessing different rows in the same bank. The SDRAM controller supports a CAS latency of 1, 2 or 3 and optimizes the read access depending on the frequency. The different modes available - self-refresh, power-down and deep power-down modes - minimize power consumption on the SDRAM device. 410 32058H–AVR32–03/09 AT32UC3A 28.3 Block Diagram Figure 28-1. SDRAM Controller Block Diagram PIO Controller SDRAMC Chip Select Memory Controller SDRAMC Interrupt SDCK SDCKE SDCS BA[1:0] RAS PMC MCK SDRAMC CAS SDWE NBS[3:0] SDRAMC_A[12:0] D[31:0] User Interface Peripheral Bus 28.4 I/O Lines Description Table 28-1. Name SDCK SDCKE SDCS BA[1:0] RAS CAS SDWE NBS[3:0] I/O Line Description Description SDRAM Clock SDRAM Clock Enable SDRAM Controller Chip Select Bank Select Signals Row Signal Column Signal SDRAM Write Enable Data Mask Enable Signals Address Bus Data Bus Type Output Output Output Output Output Output Output Output Output I/O Low Low Low Low High Low Active Level SDRAMC_A[12:0] D[31:0] 411 32058H–AVR32–03/09 AT32UC3A 28.5 28.5.1 Application Example Hardware Interface Figure 28-2 shows an example of SDRAM device connection to the SDRAM Controller using a 32-bit data bus width. Figure 28-3 shows an example of SDRAM device connection using a 16bit data bus width. It is important to note that these examples are given for a direct connection of the devices to the SDRAM Controller, without External Bus Interface or PIO Controller multiplexing. Figure 28-2. SDRAM Controller Connections to SDRAM Devices: 32-bit Data Bus Width D0-D31 RAS CAS SDCK SDCKE SDWE NBS0 NBS1 NBS2 NBS3 D0-D7 2M x 8 SDRAM D0-D7 SDRAMC_A[0-9], SDRAMC_A11 SDRAMC_A10 BA0 BA1 D8-D15 2M x 8 SDRAM D0-D7 CS CLK CKE SDWE WE RAS CAS DQM NBS0 A0-A9, A11 A10 BA0 BA1 CS CLK CKE SDWE WE RAS CAS DQM NBS1 A0-A9, A11 A10 BA0 BA1 SDRAMC_A[0-9], SDRAMC_A11 SDRAMC_A10 BA0 BA1 SDRAMC_A[0-12] BA0 BA1 D16-D23 SDCS D0-D7 2M x 8 SDRAM D24-D31 2M x 8 SDRAM D0-D7 SDRAMC_A[0-9], SDRAMC_A11 A0-A9, A11 SDRAMC_A10 A10 BA0 BA0 BA1 BA1 SDRAM Controller CS CLK CKE SDWE WE RAS CAS DQM NBS2 A0-A9, A11 A10 BA0 BA1 SDRAMC_A[0-9], SDRAMC_ A11 SDRAMC_A10 BA0 BA1 CS CLK CKE SDWE WE RAS CAS DQM NBS3 Figure 28-3. SDRAM Controller Connections to SDRAM Devices: 16-bit Data Bus Width D0-D31 RAS CAS SDCK SDCKE SDWE NBS0 NBS1 D0-D7 2M x 8 SDRAM D0-D7 D8-D15 2M x 8 SDRAM D0-D7 CS CLK CKE SDWE WE RAS CAS DQM NBS0 A0-A9, A11 A10 BA0 BA1 SDRAMC_A[0-9], SDRAMC_A11 SDRAMC_A10 BA0 BA1 CS CLK CKE SDWE WE RAS CAS DQM NBS1 A0-A9, A11 A10 BA0 BA1 SDRAMC_A[0-9], SDRAMC_A11 SDRAMC_A10 BA0 BA1 SDRAMC_A[0-12] BA0 BA1 SDRAM Controller SDCS 412 32058H–AVR32–03/09 AT32UC3A 28.5.2 Software Interface The SDRAM address space is organized into banks, rows, and columns. The SDRAM controller allows mapping different memory types according to the values set in the SDRAMC configuration register. The SDRAM Controller’s function is to make the SDRAM device access protocol transparent to the user. Table 28-2 to Table 28-7 illustrate the SDRAM device memory mapping seen by the user in correlation with the device structure. Various configurations are illustrated. 28.5.2.1 Table 28-2. 2 7 2 6 2 5 32-bit Memory Data Bus Width SDRAM Configuration Mapping: 2K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 1 5 Row[10:0] Row[10:0] Row[10:0] Row[10:0] 1 4 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Bk[1:0] Bk[1:0] Bk[1:0] Column[7:0] Column[8:0] Column[9:0] Column[10:0] M[1:0] M[1:0] M[1:0] M[1:0] Table 28-3. 2 7 2 6 2 5 SDRAM Configuration Mapping: 4K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 1 5 1 4 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Bk[1:0] Bk[1:0] Bk[1:0] Row[11:0] Row[11:0] Row[11:0] Row[11:0] Column[7:0] Column[8:0] Column[9:0] Column[10:0] M[1:0] M[1:0] M[1:0] M[1:0] Table 28-4. 2 7 2 6 2 5 SDRAM Configuration Mapping: 8K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 Row[12:0] Row[12:0] Row[12:0] Row[12:0] 1 5 1 4 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Bk[1:0] Bk[1:0] Bk[1:0] Column[7:0] Column[8:0] Column[9:0] Column[10:0] M[1:0] M[1:0] M[1:0] M[1:0] Notes: 1. M[1:0] is the byte address inside a 32-bit word. 2. Bk[1] = BA1, Bk[0] = BA0. 413 32058H–AVR32–03/09 AT32UC3A 28.5.2.2 Table 28-5. 2 7 2 6 2 5 16-bit Memory Data Bus Width SDRAM Configuration Mapping: 2K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 1 5 1 4 Row[10:0] 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Column[7:0] M 0 M 0 M 0 M 0 Bk[1:0] Row[10:0] Column[8:0] Bk[1:0] Row[10:0] Column[9:0] Bk[1:0] Row[10:0] Column[10:0] Table 28-6. 2 7 2 6 2 5 SDRAM Configuration Mapping: 4K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 1 5 1 4 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Row[11:0] Column[7:0] M 0 M 0 M 0 M 0 Bk[1:0] Row[11:0] Column[8:0] Bk[1:0] Row[11:0] Column[9:0] Bk[1:0] Row[11:0] Column[10:0] Table 28-7. 2 7 2 6 2 5 SDRAM Configuration Mapping: 8K Rows, 256/512/1024/2048 Columns CPU Address Line 2 4 2 3 2 2 2 1 2 0 1 9 1 8 1 7 1 6 1 5 Row[12:0] 1 4 1 3 1 2 1 1 1 0 9 8 7 6 5 4 3 2 1 0 Bk[1:0] Column[7:0] M 0 M 0 M 0 M 0 Bk[1:0] Row[12:0] Column[8:0] Bk[1:0] Row[12:0] Column[9:0] Bk[1:0] Row[12:0] Column[10:0] Notes: 1. M0 is the byte address inside a 16-bit half-word. 2. Bk[1] = BA1, Bk[0] = BA0. 414 32058H–AVR32–03/09 AT32UC3A 28.6 28.6.1 Product Dependencies SDRAM Device Initialization The initialization sequence is generated by software. The SDRAM devices are initialized by the following sequence: 1. SDRAM features must be set in the configuration register: asynchronous timings (TRC, TRAS, ...), number of column, rows, CAS latency, and the data bus width. 2. For mobile SDRAM, temperature-compensated self refresh (TCSR), drive strength (DS) and partial array self refresh (PASR) must be set in the Low Power Register. 3. The SDRAM memory type must be set in the Memory Device Register. 4. An No Operation (NOP)command must be issued to the SDRAM devices to start the SDRAM clock. The application must set Mode to 1 in the and perform a write access to any SDRAM address. 5. A minimum pause of 200 µs is provided to precede any signal toggle. 6. An All Banks Precharge command must be issued to the SDRAM devices. The application must set Mode to 2 in the Mode Register and perform a write access to any SDRAM address. 7. Eight auto-refresh (CBR) cycles are provided. The application must set the Mode to 4 in the Mode Register and performs a write access to any SDRAM location eight times. 8. A Mode Register set (MRS) cycle must be issued to program the parameters of the SDRAM devices, in particular CAS latency and burst length. The application must set Mode to 3 in the Mode Register and perform a write access to the SDRAM. The write address must be chosen so that BA[1:0] are set to 0. For example, with a 16-bit 128 MB SDRAM (12 rows, 9 columns, 4 banks) bank address, the SDRAM write access should be done at the address 0x20000000. 9. For mobile SDRAM initialization, an Extended Mode Register set (EMRS) cycle must be issued to program the SDRAM parameters (TCSR, PASR, DS). The application must set Mode to 5 in the Mode Register and perform a write access to the SDRAM. The write address must be chosen so that BA[1] or BA[0] are set to 1. For example, with a 16-bit 128 MB SDRAM, (12 rows, 9 columns, 4 banks) bank address the SDRAM write access should be done at the address 0x20800000 or 0x20400000. 10. The application must go into Normal Mode, setting Mode to 0 in the Mode Register and performing a write access at any location in the SDRAM. 11. Write the refresh rate into the count field in the SDRAMC Refresh Timer register. (Refresh rate = delay between refresh cycles). The SDRAM device requires a refresh every 15.625 us or 7.81 us. With a 100 MHz frequency, the Refresh Timer Counter Register must be set with the value 1562 (15.625 µs x 100 MHz) or 781 (7.81 µs x 100 MHz). After initialization, the SDRAM devices are fully functional. 415 32058H–AVR32–03/09 AT32UC3A Figure 28-4. SDRAM Device Initialization Sequence SDCKE tRP tRC tMRD SDCK SDRAMC_A[9:0] A10 SDRAMC_A[12:11] SDCS RAS CAS SDWE NBS Inputs Stable for 200 μsec Precharge All Banks 1st Auto-refresh 8th Auto-refresh MRS Command Valid Command 28.6.2 I/O Lines The pins used for interfacing the SDRAM Controller may be multiplexed with the PIO lines. The programmer must first program the PIO controller to assign the SDRAM Controller pins to their peripheral function. If I/O lines of the SDRAM Controller are not used by the application, they can be used for other purposes by the PIO Controller. 28.6.3 Interrupt The SDRAM Controller has an interrupt line connected to the interrupt controller. In order to handle interrupts, the interrupt controller must be programmed before configuring the SDRAM Controller. Using the SDRAM Controller interrupt requires the IC to be programmed first.) 416 32058H–AVR32–03/09 AT32UC3A 28.7 28.7.1 Functional Description SDRAM Controller Write Cycle The SDRAM Controller allows burst access or single access. In both cases, the SDRAM controller keeps track of the active row in each bank, thus maximizing performance. To initiate a burst access, the SDRAM Controller uses the transfer type signal provided by the master requesting the access. If the next access is a sequential write access, writing to the SDRAM device is carried out. If the next access is a write-sequential access, but the current access is to a boundary page, or if the next access is in another row, then the SDRAM Controller generates a precharge command, activates the new row and initiates a write command. To comply with SDRAM timing parameters, additional clock cycles are inserted between precharge/active (tRP) commands and active/write (tRCD) commands. For definition of these timing parameters, refer to the ”SDRAMC Configuration Register” on page 427. This is described in Figure 28-5 below. Figure 28-5. Write Burst, 32-bit SDRAM Access tRCD = 3 SDCS SDCK SDRAMC_A[12:0] Row n col a col b col c col d col e col f col g col h col i col j col k col l RAS CAS SDWE D[31:0] D na Dnb Dnc Dnd Dne Dnf Dng Dnh Dni Dnj Dnk Dnl 28.7.2 SDRAM Controller Read Cycle The SDRAM Controller allows burst access, incremental burst of unspecified length or single access. In all cases, the SDRAM Controller keeps track of the active row in each bank, thus maximizing performance of the SDRAM. If row and bank addresses do not match the previous row/bank address, then the SDRAM controller automatically generates a precharge command, activates the new row and starts the read command. To comply with the SDRAM timing parameters, additional clock cycles on SDCK are inserted between precharge and active commands (tRP) and between active and read command (tRCD). These two parameters are set in the configuration register of the SDRAM Controller. After a read command, additional wait states are generated to comply with the CAS latency (1, 2 or 3 clock delays specified in the configuration register). 417 32058H–AVR32–03/09 AT32UC3A For a single access or an incremented burst of unspecified length, the SDRAM Controller anticipates the next access. While the last value of the column is returned by the SDRAM Controller on the bus, the SDRAM Controller anticipates the read to the next column and thus anticipates the CAS latency. This reduces the effect of the CAS latency on the internal bus. For burst access of specified length (4, 8, 16 words), access is not anticipated. This case leads to the best performance. If the burst is broken (border, busy mode, etc.), the next access is handled as an incrementing burst of unspecified length. Figure 28-6. Read Burst, 32-bit SDRAM Access tRCD = 3 SDCS CAS = 2 SDCK SDRAMC_A[12:0] Row n col a col b col c col d col e col f RAS CAS SDWE D[31:0] (Input) D na Dnb Dnc Dnd Dne Dnf 28.7.3 Border Management When the memory row boundary has been reached, an automatic page break is inserted. In this case, the SDRAM controller generates a precharge command, activates the new row and initiates a read or write command. To comply with SDRAM timing parameters, an additional clock cycle is inserted between the precharge/active (tRP) command and the active/read (tRCD) command. This is described in Figure 28-7 below. 418 32058H–AVR32–03/09 AT32UC3A Figure 28-7. Read Burst with Boundary Row Access TRP = 3 SDCS TRCD = 3 CAS = 2 SDCK Row n SDRAMC_A[12:0] col a c ol b col c col d Row m col a col b col c col d col e RAS CAS SDWE D[31:0] Dna Dnb Dnc Dnd Dma Dmb Dmc Dmd Dme 28.7.4 SDRAM Controller Refresh Cycles An auto-refresh command is used to refresh the SDRAM device. Refresh addresses are generated internally by the SDRAM device and incremented after each auto-refresh automatically. The SDRAM Controller generates these auto-refresh commands periodically. An internal timer is loaded with the value in the register TR that indicates the number of clock cycles between refresh cycles. A refresh error interrupt is generated when the previous auto-refresh command did not perform. It is acknowledged by reading the Interrupt Status Register (ISR). When the SDRAM Controller initiates a refresh of the SDRAM device, internal memory accesses are not delayed. However, if the CPU tries to access the SDRAM, the slave indicates that the device is busy and the master is held by a wait signal. See Figure 28-8. 419 32058H–AVR32–03/09 AT32UC3A Figure 28-8. Refresh Cycle Followed by a Read Access tRP = 3 SDCS tRC = 8 tRCD = 3 CAS = 2 SDCK Row n SDRAMC_A[12:0] col c col d R ow m col a RAS CAS SDWE D[31:0] (input) Dnb Dnc Dnd D ma 28.7.5 Power Management Three low-power modes are available: • Self-refresh Mode: The SDRAM executes its own Auto-refresh cycle without control of the SDRAM Controller. Current drained by the SDRAM is very low. • Power-down Mode: Auto-refresh cycles are controlled by the SDRAM Controller. Between auto-refresh cycles, the SDRAM is in power-down. Current drained in Power-down mode is higher than in Self-refresh Mode. • Deep Power-down Mode: (Only available with Mobile SDRAM) The SDRAM contents are lost, but the SDRAM does not drain any current. The SDRAM Controller activates one low-power mode as soon as the SDRAM device is not selected. It is possible to delay the entry in self-refresh and power-down mode after the last access by programming a timeout value in the Low Power Register. 28.7.5.1 Self-refresh Mode This mode is selected by programming the LPCB field to 1 in the SDRAMC Low Power Register. In self-refresh mode, the SDRAM device retains data without external clocking and provides its own internal clocking, thus performing its own auto-refresh cycles. All the inputs to the SDRAM device become “don’t care” except SDCKE, which remains low. As soon as the SDRAM device is selected, the SDRAM Controller provides a sequence of commands and exits self-refresh mode. Some low-power SDRAMs (e.g., mobile SDRAM) can refresh only one quarter or a half quarter or all banks of the SDRAM array. This feature reduces the self-refresh current. To configure this feature, Temperature Compensated Self Refresh (TCSR), Partial Array Self Refresh (PASR) and Drive Strength (DS) parameters must be set in the Low Power Register and transmitted to the low-power SDRAM during initialization. 420 32058H–AVR32–03/09 AT32UC3A After initialization, as soon as PASR/DS/TCSR fields are modified and self-refresh mode is activated, the Extended Mode Register is accessed automatically and PASR/DS/TCSR bits are updated before entry into self-refresh mode. The SDRAM device must remain in self-refresh mode for a minimum period of tRAS and may remain in self-refresh mode for an indefinite period. This is described in Figure 28-9. Figure 28-9. Self-refresh Mode Behavior Self Refresh Mode SRCB = 1 Write SDRAMC_SRR SDRAMC_A[12:0] Row TXSR = 3 SDCK SDCKE SDCS RAS CAS SDWE Access Request to the SDRAM Controller 28.7.5.2 Low-power Mode This mode is selected by programming the LPCB field to 2 in the SDRAMC Low Power Register. Power consumption is greater than in self-refresh mode. All the input and output buffers of the SDRAM device are deactivated except SDCKE, which remains low. In contrast to self-refresh mode, the SDRAM device cannot remain in low-power mode longer than the refresh period (64 ms for a whole device refresh operation). As no auto-refresh operations are performed by the SDRAM itself, the SDRAM Controller carries out the refresh operation. The exit procedure is faster than in self-refresh mode. This is described in Figure 28-10. 421 32058H–AVR32–03/09 AT32UC3A Figure 28-10. Low-power Mode Behavior TRCD = 3 SDCS CAS = 2 Low Power Mode SDCK SDRAMC_A[12:0] Row n col a col b col c col d col e col f RAS CAS SDCKE D[31:0] (input) D na Dnb Dnc Dnd Dne Dnf 28.7.5.3 Deep Power-down Mode This mode is selected by programming the LPCB field to 3 in the SDRAMC Low Power Register. When this mode is activated, all internal voltage generators inside the SDRAM are stopped and all data is lost. When this mode is enabled, the application must not access to the SDRAM until a new initialization sequence is done (See ”SDRAM Device Initialization” on page 415). This is described in Figure 28-11. 422 32058H–AVR32–03/09 AT32UC3A Figure 28-11. Deep Power-down Mode Behavior tRP = 3 SDCS SDCK Row n SDRAMC_A[12:0] col c col d RAS CAS SDWE CKE D[31:0] (input) Dnb Dnc Dnd 423 32058H–AVR32–03/09 AT32UC3A 28.8 SDRAM Controller User Interface SDRAM Controller Memory Map Register SDRAMC Mode Register SDRAMC Refresh Timer Register SDRAMC Configuration Register SDRAMC High Speed Register SDRAMC Low Power Register SDRAMC Interrupt Enable Register SDRAMC Interrupt Disable Register SDRAMC Interrupt Mask Register SDRAMC Interrupt Status Register SDRAMC Memory Device Register Reserved Name MR TR CR HSR LPR IER IDR IMR ISR MDR – Access Read/Write Read/Write Read/Write Read/Write Read/Write Write-only Write-only Read-only Read-only Read/Write – Reset State 0x00000000 0x00000000 0x852372C0 0x00 0x0 – – 0x0 0x0 0x0 – Table 28-8. Offset 0x00 0x04 0x08 0x0C 0x10 0x14 0x18 0x1C 0x20 0x24 0x28 - 0xFC 424 32058H–AVR32–03/09 AT32UC3A 28.8.1 SDRAMC Mode Register MR Read/Write 0x00000000 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 25 – 17 – 9 – 1 MODE 24 – 16 – 8 – 0 Register Name: Access Type: Reset Value: 31 – 23 – 15 – 7 – • MODE: SDRAMC Command Mode This field defines the command issued by the SDRAM Controller when the SDRAM device is accessed. Table 28-9. MODE 0 0 0 0 0 1 0 1 0 Description Normal mode. Any access to the SDRAM is decoded normally. The SDRAM Controller issues a NOP command when the SDRAM device is accessed regardless of the cycle. The SDRAM Controller issues an “All Banks Precharge” command when the SDRAM device is accessed regardless of the cycle. The SDRAM Controller issues a “Load Mode Register” command when the SDRAM device is accessed regardless of the cycle. The command will load the CAS latency from the Configuration Register and every other value set to 0 into the Mode Register. The SDRAM Controller issues an “Auto-Refresh” Command when the SDRAM device is accessed regardless of the cycle. Previously, an “All Banks Precharge” command must be issued. The SDRAM Controller issues an extended load mode register command when the SDRAM device is accessed regardless of the cycle. The command will load the PASR, DS and TCR from the Low Power Register and every other value set to 0 into the Extended Mode Register. Deep power-down mode. Enters deep power-down mode. 0 1 1 1 0 0 1 1 0 1 1 0 425 32058H–AVR32–03/09 AT32UC3A 28.8.2 SDRAMC Refresh Timer Register TR Read/Write 0x00000000 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 COUNT 27 – 19 – 11 26 – 18 – 10 COUNT 3 2 1 0 25 – 17 – 9 24 – 16 – 8 Register Name: Access Type: Reset Value: 31 – 23 – 15 – 7 • COUNT: SDRAMC Refresh Timer Count This 12-bit field is loaded into a timer that generates the refresh pulse. Each time the refresh pulse is generated, a refresh burst is initiated. The value to be loaded depends on the SDRAMC clock frequency (MCK: Master Clock), the refresh rate of the SDRAM device and the refresh burst length where 15.6 µs per row is a typical value for a burst of length one. To refresh the SDRAM device, this 12-bit field must be written. If this condition is not satisfied, no refresh command is issued and no refresh of the SDRAM device is carried out. 426 32058H–AVR32–03/09 AT32UC3A 28.8.3 SDRAMC Configuration Register CR Read/Write 0x852372C0 30 TXSR 23 22 TRCD 15 14 TRC 7 DBW 6 CAS 5 4 NB 3 NR 2 13 12 11 10 TWR 1 NC 0 21 20 19 18 TRP 9 8 29 28 27 26 TRAS 17 16 25 24 Register Name: Access Type: Reset Value: 31 • NC: Number of Column Bits Reset value is 8 column bits. NC 0 0 1 1 0 1 0 1 Column Bits 8 9 10 11 • NR: Number of Row Bits Reset value is 11 row bits. NR 0 0 1 1 0 1 0 1 Row Bits 11 12 13 Reserved • NB: Number of Banks Reset value is two banks. NB 0 1 Number of Banks 2 4 427 32058H–AVR32–03/09 AT32UC3A • CAS: CAS Latency Reset value is two cycles. In the SDRAMC, only a CAS latency of one, two and three cycles is managed. CAS 0 0 1 1 0 1 0 1 CAS Latency (Cycles) Reserved 1 2 3 • DBW: Data Bus Width Reset value is 16 bits 0: Data bus width is 32 bits. 1: Data bus width is 16 bits. • TWR: Write Recovery Delay Reset value is two cycles. This field defines the Write Recovery Time in number of cycles. Number of cycles is between 0 and 15. • TRC: Row Cycle Delay Reset value is seven cycles. This field defines the delay between a Refresh and an Activate Command in number of cycles. Number of cycles is between 0 and 15. • TRP: Row Precharge Delay Reset value is three cycles. This field defines the delay between a Precharge Command and another Command in number of cycles. Number of cycles is between 0 and 15. • TRCD: Row to Column Delay Reset value is two cycles. This field defines the delay between an Activate Command and a Read/Write Command in number of cycles. Number of cycles is between 0 and 15. • TRAS: Active to Precharge Delay Reset value is five cycles. This field defines the delay between an Activate Command and a Precharge Command in number of cycles. Number of cycles is between 0 and 15. • TXSR: Exit Self Refresh to Active Delay Reset value is height cycles. This field defines the delay between SCKE set high and an Activate Command in number of cycles. Number of cycles is between 0 and 15. 428 32058H–AVR32–03/09 AT32UC3A 28.8.4 SDRAMC High Speed Register HSR Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 DA Register Name: Access Type: 31 – 23 – 15 – 7 – • DA: Decode Cycle Enable A decode cycle can be added on the addresses as soon as a non-sequential access is performed on the HSB bus. The addition of the decode cycle allows the SDRAMC to gain time to access the SDRAM memory. 0: Decode cycle is disabled. 1: Decode cycle is enabled. 429 32058H–AVR32–03/09 AT32UC3A 28.8.5 SDRAMC Low Power Register LPR Read/Write 0x0 30 – 22 – 14 – 6 29 – 21 – 13 TIMEOUT 5 PASR 4 3 – 28 – 20 – 12 27 – 19 – 11 DS 2 – 1 LPCB 26 – 18 – 10 25 – 17 – 9 TCSR 0 24 – 16 – 8 Register Name: Access Type: Reset Value: 31 – 23 – 15 – 7 – • LPCB: Low-power Configuration Bits 00 Low Power Feature is inhibited: no Power-down, Self-refresh or Deep Power-down command is issued to the SDRAM device. The SDRAM Controller issues a Self-refresh command to the SDRAM device, the SDCLK clock is deactivated and the SDCKE signal is set low. The SDRAM device leaves the Self Refresh Mode when accessed and enters it after the access. The SDRAM Controller issues a Power-down Command to the SDRAM device after each access, the SDCKE signal is set to low. The SDRAM device leaves the Power-down Mode when accessed and enters it after the access. The SDRAM Controller issues a Deep Power-down command to the SDRAM device. This mode is unique to low-power SDRAM. 01 10 11 • PASR: Partial Array Self-refresh (only for low-power SDRAM) PASR parameter is transmitted to the SDRAM during initialization to specify whether only one quarter, one half or all banks of the SDRAM array are enabled. Disabled banks are not refreshed in self-refresh mode. This parameter must be set according to the SDRAM device specification. After initialization, as soon as PASR field is modified and self-refresh mode is activated, the Extended Mode Register is accessed automatically and PASR bits are updated before entry in self-refresh mode. • TCSR: Temperature Compensated Self-Refresh (only for low-power SDRAM) TCSR parameter is transmitted to the SDRAM during initialization to set the refresh interval during self-refresh mode depending on the temperature of the low-power SDRAM. This parameter must be set according to the SDRAM device specification. After initialization, as soon as TCSR field is modified and self-refresh mode is activated, the Extended Mode Register is accessed automatically and TCSR bits are updated before entry in self-refresh mode. • DS: Drive Strength (only for low-power SDRAM) DS parameter is transmitted to the SDRAM during initialization to select the SDRAM strength of data output. This parameter must be set according to the SDRAM device specification. 430 32058H–AVR32–03/09 AT32UC3A After initialization, as soon as DS field is modified and self-refresh mode is activated, the Extended Mode Register is accessed automatically and DS bits are updated before entry in self-refresh mode. • TIMEOUT: Time to define when low-power mode is enabled 00 01 10 11 The SDRAM controller activates the SDRAM low-power mode immediately after the end of the last transfer. The SDRAM controller activates the SDRAM low-power mode 64 clock cycles after the end of the last transfer. The SDRAM controller activates the SDRAM low-power mode 128 clock cycles after the end of the last transfer. Reserved. 431 32058H–AVR32–03/09 AT32UC3A 28.8.6 SDRAMC Interrupt Enable Register IER Write-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 RES Register Name: Access Type: 31 – 23 – 15 – 7 – • RES: Refresh Error Status 0: No effect. 1: Enables the refresh error interrupt. 432 32058H–AVR32–03/09 AT32UC3A 28.8.7 SDRAMC Interrupt Disable Register IDR Write-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 RES Register Name: Access Type: 31 – 23 – 15 – 7 – • RES: Refresh Error Status 0: No effect. 1: Disables the refresh error interrupt. 433 32058H–AVR32–03/09 AT32UC3A 28.8.8 SDRAMC Interrupt Mask Register IMR Read-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 RES Register Name: Access Type: 31 – 23 – 15 – 7 – • RES: Refresh Error Status 0: The refresh error interrupt is disabled. 1: The refresh error interrupt is enabled. 434 32058H–AVR32–03/09 AT32UC3A 28.8.9 SDRAMC Interrupt Status Register ISR Read-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 RES Register Name: Access Type: 31 – 23 – 15 – 7 – • RES: Refresh Error Status 0: No refresh error has been detected since the register was last read. 1: A refresh error has been detected since the register was last read. 435 32058H–AVR32–03/09 AT32UC3A 28.8.10 SDRAMC Memory Device Register MDR Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 MD 24 – 16 – 8 – 0 Register Name: Access Type: 31 – 23 – 15 – 7 – • MD: Memory Device Type 00 01 10 11 SDRAM Low-power SDRAM Reserved Reserved. 436 32058H–AVR32–03/09 AT32UC3A 29. Ethernet MAC (MACB) Rev: 1.1.2.5 29.1 Features • • • • • • • • • • • • • • • • • • • • • Compatible with IEEE Standard 802.3 10 and 100 Mbit/s Operation Full- and Half-duplex Operation Statistics Counter Registers MII/RMII Interface to the Physical Layer Interrupt Generation to Signal Receive and Transmit Completion DMA Master on Receive and Transmit Channels Transmit and Receive FIFOs Automatic Pad and CRC Generation on Transmitted Frames Automatic Discard of Frames Received with Errors Address Checking Logic Supports Up to Four Specific 48-bit Addresses Supports Promiscuous Mode Where All Valid Received Frames are Copied to Memory Hash Matching of Unicast and Multicast Destination Addresses External Address Matching of Received Frames Physical Layer Management through MDIO Interface Half-duplex Flow Control by Forcing Collisions on Incoming Frames Full-duplex Flow Control with Recognition of Incoming Pause Frames and Hardware Generation of Transmitted Pause Frames Support for 802.1Q VLAN Tagging with Recognition of Incoming VLAN and Priority Tagged Frames Multiple Buffers per Receive and Transmit Frame Wake-on-LAN Support Jumbo Frames Up to 10240 bytes Supported 29.2 Description The MACB module implements a 10/100 Ethernet MAC compatible with the IEEE 802.3 standard using an address checker, statistics and control registers, receive and transmit blocks, and a DMA interface. The address checker recognizes four specific 48-bit addresses and contains a 64-bit hash register for matching multicast and unicast addresses. It can recognize the broadcast address of all ones, copy all frames, and act on an external address match signal. The statistics register block contains registers for counting various types of events associated with transmit and receive operations. These registers, along with the status words stored in the receive buffer list, enable software to generate network management statistics compatible with IEEE 802.3. 437 32058H–AVR32–03/09 AT32UC3A 29.3 Block Diagram Figure 29-1. MACB Block Diagram Address Checker Peripheral Bus Slave Register Interface Statistics Registers MDIO Control Registers DMA Interface RX FIFO TX FIFO Ethernet Receive High Speed Bus Master MII/RMII Ethernet Transmit 29.4 29.4.1 Product Dependencies I/O Lines The pins used for interfacing the compliant external devices may be multiplexed with PIO lines. The programmer must first program the PIO controllers to assign the MACB pins to their peripheral functions. 29.4.2 Power Management The MACB clock is generated by the Power Manager. Before using the MACB, the programmer must ensure that the MACB clock is enabled in the Power Manager. In the MACB description, Master Clock (MCK) is the clock of the peripheral bus to which the MACB is connected. The synchronization module in the MACB requires that the bus clock (hclk) runs on at least the speed of the macb_tx/rx_clk, which is 25MHz in 100Mbps, and 2.5MHZ in 10Mbps in MII mode and 50MHz in 100Mbps, and 5MHZ in 10Mbps in RMII mode. To prevent bus errors the MACB operation must be terminated before entering sleep mode. 438 32058H–AVR32–03/09 AT32UC3A 29.4.3 Interrupt The MACB interface has an interrupt line connected to the Interrupt Controller. Handling the MACB interrupt requires programming the interrupt controller before configuring the MACB. 29.5 Functional Description Figure 29-1 on page 438 illustrates the different blocks of the MACB module. The control registers drive the MDIO interface, setup DMA activity, start frame transmission and select modes of operation such as full- or half-duplex. The receive block checks for valid preamble, FCS, alignment and length, and presents received frames to the address checking block and DMA interface. The transmit block takes data from the DMA interface, adds preamble and, if necessary, pad and FCS, and transmits data according to the CSMA/CD (carrier sense multiple access with collision detect) protocol. The start of transmission is deferred if CRS (carrier sense) is active. If COL (collision) becomes active during transmission, a jam sequence is asserted and the transmission is retried after a random back off. CRS and COL have no effect in full duplex mode. The DMA block connects to external memory through its high speed bus (HSB) interface. It contains receive and transmit FIFOs for buffering frame data. It loads the transmit FIFO and empties the receive FIFO using HSB bus master operations. Receive data is not sent to memory until the address checking logic has determined that the frame should be copied. Receive or transmit frames are stored in one or more buffers. Receive buffers have a fixed length of 128 bytes. Transmit buffers range in length between 0 and 2047 bytes, and up to 128 buffers are permitted per frame. The DMA block manages the transmit and receive framebuffer queues. These queues can hold multiple frames. 29.5.1 Memory Interface Frame data is transferred to and from the MACB through the DMA interface. All transfers are 32bit words and may be single accesses or bursts of 2, 3 or 4 words. Burst accesses do not cross sixteen-byte boundaries. Bursts of 4 words are the default data transfer; single accesses or bursts of less than four words may be used to transfer data at the beginning or the end of a buffer. The DMA controller performs six types of operation on the bus. In order of priority, these are: 1. Receive buffer manager write 2. Receive buffer manager read 3. Transmit data DMA read 4. Receive data DMA write 5. Transmit buffer manager read 6. Transmit buffer manager write 29.5.1.1 FIFO The FIFO depths are 124 bytes. Data is typically transferred into and out of the FIFOs in bursts of four words. For receive, a bus request is asserted when the FIFO contains four words and has space for three more. For transmit, a bus request is generated when there is space for four words, or when there is space for two words if the next transfer is to be only one or two words. 439 32058H–AVR32–03/09 AT32UC3A Thus the bus latency must be less than the time it takes to load the FIFO and transmit or receive three words (12 bytes) of data. At 100 Mbit/s, it takes 960 ns to transmit or receive 12 bytes of data. In addition, six master clock cycles should be allowed for data to be loaded from the bus and to propagate through the FIFOs. For a 60 MHz master clock this takes 100 ns, making the bus latency requirement 860 ns. 29.5.1.2 Receive Buffers Received frames, optionally including CRC/FCS, are written to receive buffers stored in memory. Each receive buffer is 128 bytes long. The start location for each receive buffer is stored in memory in a list of receive buffer descriptors at a location pointed to by the receive buffer queue pointer register. The receive buffer start location is a word address. For the first buffer of a frame, the start location can be offset by up to three bytes depending on the value written to bits 14 and 15 of the network configuration register. If the start location of the buffer is offset the available length of the first buffer of a frame is reduced by the corresponding number of bytes. Each list entry consists of two words, the first being the address of the receive buffer and the second being the receive status. If the length of a receive frame exceeds the buffer length, the status word for the used buffer is written with zeroes except for the “start of frame” bit and the offset bits, if appropriate. Bit zero of the address field is written to one to show the buffer has been used. The receive buffer manager then reads the location of the next receive buffer and fills that with receive frame data. The final buffer descriptor status word contains the complete frame status. Refer to Table 29-1 for details of the receive buffer descriptor list. Table 29-1. Bit Receive Buffer Descriptor Entry Function Word 0 31:2 1 0 Address of beginning of buffer Wrap - marks last descriptor in receive buffer descriptor list. Ownership - needs to be zero for the MACB to write data to the receive buffer. The MACB sets this to one once it has successfully written a frame to memory. Software has to clear this bit before the buffer can be used again. Word 1 31 30 29 28 27 26 25 24 23 22 21 Global all ones broadcast address detected Multicast hash match Unicast hash match External address match Reserved for future use Specific address register 1 match Specific address register 2 match Specific address register 3 match Specific address register 4 match Type ID match VLAN tag detected (i.e., type id of 0x8100) 440 32058H–AVR32–03/09 AT32UC3A Table 29-1. Bit 20 19:17 16 15 14 Receive Buffer Descriptor Entry (Continued) Function Priority tag detected (i.e., type id of 0x8100 and null VLAN identifier) VLAN priority (only valid if bit 21 is set) Concatenation format indicator (CFI) bit (only valid if bit 21 is set) End of frame - when set the buffer contains the end of a frame. If end of frame is not set, then the only other valid status are bits 12, 13 and 14. Start of frame - when set the buffer contains the start of a frame. If both bits 15 and 14 are set, then the buffer contains a whole frame. Receive buffer offset - indicates the number of bytes by which the data in the first buffer is offset from the word address. Updated with the current values of the network configuration register. If jumbo frame mode is enabled through bit 3 of the network configuration register, then bits 13:12 of the receive buffer descriptor entry are used to indicate bits 13:12 of the frame length. Length of frame including FCS (if selected). Bits 13:12 are also used if jumbo frame mode is selected. 13:12 11:0 To receive frames, the buffer descriptors must be initialized by writing an appropriate address to bits 31 to 2 in the first word of each list entry. Bit zero must be written with zero. Bit one is the wrap bit and indicates the last entry in the list. The start location of the receive buffer descriptor list must be written to the receive buffer queue pointer register before setting the receive enable bit in the network control register to enable receive. As soon as the receive block starts writing received frame data to the receive FIFO, the receive buffer manager reads the first receive buffer location pointed to by the receive buffer queue pointer register. If the filter block then indicates that the frame should be copied to memory, the receive data DMA operation starts writing data into the receive buffer. If an error occurs, the buffer is recovered. If the current buffer pointer has its wrap bit set or is the 1024th descriptor, the next receive buffer location is read from the beginning of the receive descriptor list. Otherwise, the next receive buffer location is read from the next word in memory. There is an 11-bit counter to count out the 2048 word locations of a maximum length, receive buffer descriptor list. This is added with the value originally written to the receive buffer queue pointer register to produce a pointer into the list. A read of the receive buffer queue pointer register returns the pointer value, which is the queue entry currently being accessed. The counter is reset after receive status is written to a descriptor that has its wrap bit set or rolls over to zero after 1024 descriptors have been accessed. The value written to the receive buffer pointer register may be any word-aligned address, provided that there are at least 2048 word locations available between the pointer and the top of the memory. The System Bus specification states that bursts should not cross 1K boundaries. As receive buffer manager writes are bursts of two words, to ensure that this does not occur, it is best to write the pointer register with the least three significant bits set to zero. As receive buffers are used, the receive buffer manager sets bit zero of the first word of the descriptor to indicate used. If a receive error is detected the receive buffer currently being written is recovered. Previous buffers are not recovered. Software should search through the used bits in the buffer descriptors to find out how many frames have been received. It should be checking the start-of-frame and end-offrame bits, and not rely on the value returned by the receive buffer queue pointer register which changes continuously as more buffers are used. 441 32058H–AVR32–03/09 AT32UC3A For CRC errored frames, excessive length frames or length field mismatched frames, all of which are counted in the statistics registers, it is possible that a frame fragment might be stored in a sequence of receive buffers. Software can detect this by looking for start of frame bit set in a buffer following a buffer with no end of frame bit set. For a properly working Ethernet system, there should be no excessively long frames or frames greater than 128 bytes with CRC/FCS errors. Collision fragments are less than 128 bytes long. Therefore, it is a rare occurrence to find a frame fragment in a receive buffer. If bit zero is set when the receive buffer manager reads the location of the receive buffer, then the buffer has already been used and cannot be used again until software has processed the frame and cleared bit zero. In this case, the DMA block sets the buffer not available bit in the receive status register and triggers an interrupt. If bit zero is set when the receive buffer manager reads the location of the receive buffer and a frame is being received, the frame is discarded and the receive resource error statistics register is incremented. A receive overrun condition occurs when bus was not granted in time or because HRESP was not OK (bus error). In a receive overrun condition, the receive overrun interrupt is asserted and the buffer currently being written is recovered. The next frame received with an address that is recognized reuses the buffer. If bit 17 of the network configuration register is set, the FCS of received frames shall not be copied to memory. The frame length indicated in the receive status field shall be reduced by four bytes in this case. 29.5.1.3 Transmit Buffer Frames to be transmitted are stored in one or more transmit buffers. Transmit buffers can be between 0 and 2047 bytes long, so it is possible to transmit frames longer than the maximum length specified in IEEE Standard 802.3. Zero length buffers are allowed. The maximum number of buffers permitted for each transmit frame is 128. The start location for each transmit buffer is stored in memory in a list of transmit buffer descriptors at a location pointed to by the transmit buffer queue pointer register. Each list entry consists of two words, the first being the byte address of the transmit buffer and the second containing the transmit control and status. Frames can be transmitted with or without automatic CRC generation. If CRC is automatically generated, padding is also automatically generated to take frames to a minimum length of 64 bytes. Table 29-2 on page 443 defines an entry in the transmit buffer descriptor list. To transmit frames, the buffer descriptors must be initialized by writing an appropriate byte address to bits 31 to 0 in the first word of each list entry. The second transmit buffer descriptor is initialized with control information that indicates the length of the buffer, whether or not it is to be transmitted with CRC and whether the buffer is the last buffer in the frame. After transmission, the control bits are written back to the second word of the first buffer along with the “used” bit and other status information. Before a transmission, bit 31 is the “used” bit which must be zero when the control word is read. It is written to one when a frame has been transmitted. Bits 27, 28 and 29 indicate various transmit error conditions. Bit 30 is the “wrap” bit which can be set for any buffer within a frame. If no wrap bit is encountered after 1024 descriptors, the queue pointer rolls over to the start. The transmit buffer queue pointer register must not be written while transmit is active. If a new value is written to the transmit buffer queue pointer register, the queue pointer resets itself to 442 32058H–AVR32–03/09 AT32UC3A point to the beginning of the new queue. If transmit is disabled by writing to bit 3 of the network control, the transmit buffer queue pointer register resets to point to the beginning of the transmit queue. Note that disabling receive does not have the same effect on the receive queue pointer. Once the transmit queue is initialized, transmit is activated by writing to bit 9, the Transmit Start bit of the network control register. Transmit is halted when a buffer descriptor with its used bit set is read, or if a transmit error occurs, or by writing to the transmit halt bit of the network control register. (Transmission is suspended if a pause frame is received while the pause enable bit is set in the network configuration register.) Rewriting the start bit while transmission is active is allowed. Transmission control is implemented with a Tx_go variable which is readable in the transmit status register at bit location 3. The Tx_go variable is reset when: – transmit is disabled – a buffer descriptor with its ownership bit set is read – a new value is written to the transmit buffer queue pointer register – bit 10, tx_halt, of the network control register is written – there is a transmit error such as too many retries or a transmit underrun. To set tx_go, write to bit 9, tx_start, of the network control register. Transmit halt does not take effect until any ongoing transmit finishes. If a collision occurs during transmission of a multi-buffer frame, transmission automatically restarts from the first buffer of the frame. If a “used” bit is read midway through transmission of a multi-buffer frame, this is treated as a transmit error. Transmission stops, tx_er is asserted and the FCS is bad. If transmission stops due to a transmit error, the transmit queue pointer resets to point to the beginning of the transmit queue. Software needs to re-initialize the transmit queue after a transmit error. If transmission stops due to a “used” bit being read at the start of the frame, the transmission queue pointer is not reset and transmit starts from the same transmit buffer descriptor when the transmit start bit is written Table 29-2. Bit Transmit Buffer Descriptor Entry Function Word 0 31:0 Byte Address of buffer Word 1 Used. Needs to be zero for the MACB to read data from the transmit buffer. The MACB sets this to one for the first buffer of a frame once it has been successfully transmitted. Software has to clear this bit before the buffer can be used again. Note: This bit is only set for the first buffer in a frame unlike receive where all buffers have the Used bit set once used. 31 30 29 28 27 26:17 Wrap. Marks last descriptor in transmit buffer descriptor list. Retry limit exceeded, transmit error detected Transmit underrun, occurs either when hresp is not OK (bus error) or the transmit data could not be fetched in time or when buffers are exhausted in mid frame. Buffers exhausted in mid frame Reserved 443 32058H–AVR32–03/09 AT32UC3A Table 29-2. Bit 16 15 14:11 10:0 Transmit Buffer Descriptor Entry (Continued) Function No CRC. When set, no CRC is appended to the current frame. This bit only needs to be set for the last buffer of a frame. Last buffer. When set, this bit indicates the last buffer in the current frame has been reached. Reserved Length of buffer 29.5.2 Transmit Block This block transmits frames in accordance with the Ethernet IEEE 802.3 CSMA/CD protocol. Frame assembly starts by adding preamble and the start frame delimiter. Data is taken from the transmit FIFO a word at a time. Data is transmitted least significant nibble first. If necessary, padding is added to increase the frame length to 60 bytes. CRC is calculated as a 32-bit polynomial. This is inverted and appended to the end of the frame, taking the frame length to a minimum of 64 bytes. If the No CRC bit is set in the second word of the last buffer descriptor of a transmit frame, neither pad nor CRC are appended. In full-duplex mode, frames are transmitted immediately. Back-to-back frames are transmitted at least 96 bit times apart to guarantee the interframe gap. In half-duplex mode, the transmitter checks carrier sense. If asserted, it waits for it to de-assert and then starts transmission after the interframe gap of 96 bit times. If the collision signal is asserted during transmission, the transmitter transmits a jam sequence of 32 bits taken from the data register and retries transmission after the back off time has elapsed. The back-off time is based on an XOR of the 10 least significant bits of the data coming from the transmit FIFO and a 10-bit pseudo random number. The number of bits used depends on the number of collisions seen. After the first collision, 1 bit is used, after the second 2, and so on up to 10. Above 10, all 10 bits are used. An error is indicated and no further attempts are made if 16 attempts cause collisions. If transmit DMA underruns, bad CRC is automatically appended using the same mechanism as jam insertion and the TX_ER signal is asserted. In a properly configured system, this should never happen. If the back pressure bit is set in the network control register in half duplex mode, the transmit block transmits 64 bits of data, which can consist of 16 nibbles of 1011 or in bit-rate mode 64 1s, whenever it sees an incoming frame to force a collision. This provides a way of implementing flow control in half-duplex mode. 29.5.3 Pause Frame Support The start of an 802.3 pause frame is as follows: Table 29-3. Start of an 802.3 Pause Frame Source Address 6 bytes Type (Mac Control Frame) 0x8808 Pause Opcode 0x0001 Pause Time 2 bytes Destination Address 0x0180C2000001 The network configuration register contains a receive pause enable bit (13). If a valid pause frame is received, the pause time register is updated with the frame’s pause time, regardless of 444 32058H–AVR32–03/09 AT32UC3A its current contents and regardless of the state of the configuration register bit 13. An interrupt (12) is triggered when a pause frame is received, assuming it is enabled in the interrupt mask register. If bit 13 is set in the network configuration register and the value of the pause time register is non-zero, no new frame is transmitted until the pause time register has decremented to zero. The loading of a new pause time, and hence the pausing of transmission, only occurs when the MACB is configured for full-duplex operation. If the MACB is configured for half-duplex, there is no transmission pause, but the pause frame received interrupt is still triggered. A valid pause frame is defined as having a destination address that matches either the address stored in specific address register 1 or matches 0x0180C2000001 and has the MAC control frame type ID of 0x8808 and the pause opcode of 0x0001. Pause frames that have FCS or other errors are treated as invalid and are discarded. Valid pause frames received increment the Pause Frame Received statistic register. The pause time register decrements every 512 bit times (i.e., 128 rx_clks in nibble mode) once transmission has stopped. For test purposes, the register decrements every rx_clk cycle once transmission has stopped if bit 12 (retry test) is set in the network configuration register. If the pause enable bit (13) is not set in the network configuration register, then the decrementing occurs regardless of whether transmission has stopped or not. An interrupt (13) is asserted whenever the pause time register decrements to zero (assuming it is enabled in the interrupt mask register). Automatic transmission of pause frames is supported through the transmit pause frame bits of the network control register and the tx_pause and tx_pause_zero inputs. If either bit 11 or bit 12 of the network control register is written to with a 1, or if the input signal tx_pause is toggled, a pause frame is transmitted only if full duplex is selected in the network configuration register and transmit is enabled in the network control register. Pause frame transmission occurs immediately if transmit is inactive or if transmit is active between the current frame and the next frame due to be transmitted. The transmitted pause frame is comprised of the items in the following list: • a destination address of 01-80-C2-00-00-01 • a source address taken from the specific address 1 register • a type ID of 88-08 (MAC control frame) • a pause opcode of 00-01 • a pause quantum • fill of 00 to take the frame to minimum frame length • valid FCS The pause quantum used in the generated frame depends on the trigger source for the frame as follows: 1. If bit 11 is written with a one, the pause quantum comes from the transmit pause quantum register. The Transmit Pause Quantum register resets to a value of 0xFFFF giving a maximum pause quantum as a default. 2. If bit 12 is written with a one, the pause quantum is zero. 3. If the tx_pause input is toggled and the tx_pause_zero input is held low until the next toggle, the pause quantum comes from the transmit pause quantum register. 4. If the tx_pause input is toggled and the tx_pause_zero input is held high until the next toggle, the pause quantum is zero. 445 32058H–AVR32–03/09 AT32UC3A After transmission, no interrupts are generated and the only statistics register that is incremented is the pause frames transmitted register. 29.5.4 Receive Block The receive block checks for valid preamble, FCS, alignment and length, presents received frames to the DMA block and stores the frames destination address for use by the address checking block. If, during frame reception, the frame is found to be too long or rx_er is asserted, a bad frame indication is sent to the DMA block. The DMA block then ceases sending data to memory. At the end of frame reception, the receive block indicates to the DMA block whether the frame is good or bad. The DMA block recovers the current receive buffer if the frame was bad. The receive block signals the register block to increment the alignment error, the CRC (FCS) error, the short frame, long frame, jabber error, the receive symbol error statistics and the length field mismatch statistics. The enable bit for jumbo frames in the network configuration register allows the MACB to receive jumbo frames of up to 10240 bytes in size. This operation does not form part of the IEEE802.3 specification and is disabled by default. When jumbo frames are enabled, frames received with a frame size greater than 10240 bytes are discarded. 29.5.5 Address Checking Block The address checking (or filter) block indicates to the DMA block which receive frames should be copied to memory. Whether a frame is copied depends on what is enabled in the network configuration register, the state of the external match pin, the contents of the specific address and hash registers and the frame’s destination address. In this implementation of the MACB, the frame’s source address is not checked. Provided that bit 18 of the Network Configuration register is not set, a frame is not copied to memory if the MACB is transmitting in half duplex mode at the time a destination address is received. If bit 18 of the Network Configuration register is set, frames can be received while transmitting in half-duplex mode. Ethernet frames are transmitted a byte at a time, least significant bit first. The first six bytes (48 bits) of an Ethernet frame make up the destination address. The first bit of the destination address, the LSB of the first byte of the frame, is the group/individual bit: this is One for multicast addresses and Zero for unicast. The All Ones address is the broadcast address, and a special case of multicast. The MACB supports recognition of four specific addresses. Each specific address requires two registers, specific address register bottom and specific address register top. Specific address register bottom stores the first four bytes of the destination address and specific address register top contains the last two bytes. The addresses stored can be specific, group, local or universal. The destination address of received frames is compared against the data stored in the specific address registers once they have been activated. The addresses are deactivated at reset or when their corresponding specific address register bottom is written. They are activated when specific address register top is written. If a receive frame address matches an active address, the frame is copied to memory. 446 32058H–AVR32–03/09 AT32UC3A The following example illustrates the use of the address match registers for a MAC address of 21:43:65:87:A9:CB. Preamble 55 SFD D5 DA (Octet0 - LSB) 21 DA(Octet 1) 43 DA(Octet 2) 65 DA(Octet 3) 87 DA(Octet 4) A9 DA (Octet5 - MSB) CB SA (LSB) 00 SA 00 SA 00 SA 00 SA 00 SA (MSB) 43 SA (LSB) 21 The sequence above shows the beginning of an Ethernet frame. Byte order of transmission is from top to bottom as shown. For a successful match to specific address 1, the following address matching registers must be set up: • Base address + 0x98 0x87654321 (Bottom) • Base address + 0x9C 0x0000CBA9 (Top) And for a successful match to the Type ID register, the following should be set up: • Base address + 0xB8 0x00004321 29.5.6 Broadcast Address The broadcast address of 0xFFFFFFFFFFFF is recognized unless the ‘no broadcast’ bit in the network configuration register is set. Hash Addressing The hash address register is 64 bits long and takes up two locations in the memory map. The least significant bits are stored in hash register bottom and the most significant bits in hash register top. The unicast hash enable and the multicast hash enable bits in the network configuration register enable the reception of hash matched frames. The destination address is reduced to a 6-bit index into the 64-bit hash register using the following hash function. The hash function is an exclusive or of every sixth bit of the destination address. 29.5.7 447 32058H–AVR32–03/09 AT32UC3A hash_index[5] = da[5] ^ da[11] ^ da[17] ^ da[23] ^ da[29] ^ da[35] ^ da[41] ^ da[47] hash_index[4] = da[4] ^ da[10] ^ da[16] ^ da[22] ^ da[28] ^ da[34] ^ da[40] ^ da[46] hash_index[3] = da[3] ^ da[09] ^ da[15] ^ da[21] ^ da[27] ^ da[33] ^ da[39] ^ da[45] hash_index[2] = da[2] ^ da[08] ^ da[14] ^ da[20] ^ da[26] ^ da[32] ^ da[38] ^ da[44] hash_index[1] = da[1] ^ da[07] ^ da[13] ^ da[19] ^ da[25] ^ da[31] ^ da[37] ^ da[43] hash_index[0] = da[0] ^ da[06] ^ da[12] ^ da[18] ^ da[24] ^ da[30] ^ da[36] ^ da[42] da[0] represents the least significant bit of the first byte received, that is, the multicast/unicast indicator, and da[47] represents the most significant bit of the last byte received. If the hash index points to a bit that is set in the hash register, then the frame is matched according to whether the frame is multicast or unicast. A multicast match is signalled if the multicast hash enable bit is set. da[0] is 1 and the hash index points to a bit set in the hash register. A unicast match is signalled if the unicast hash enable bit is set. da[0] is 0 and the hash index points to a bit set in the hash register. To receive all multicast frames, the hash register should be set with all ones and the multicast hash enable bit should be set in the network configuration register. 29.5.8 External Address Matching The external address signal (eam) is enabled by bit 9 in the network configuration register. When enabled, the filter block sends the store frame and the external address match status signal to the DMA block if the external address match signal is asserted (from a source external to the MACB) and the destination address has been received and the frame has not completed. For the DMA block to be able to copy the frame to memory, the external address signal must be asserted before four words have been loaded into the receive FIFO. 29.5.9 Copy All Frames (or Promiscuous Mode) If the copy all frames bit is set in the network configuration register, then all non-errored frames are copied to memory. For example, frames that are too long, too short, or have FCS errors or rx_er asserted during reception are discarded and all others are received. Frames with FCS errors are copied to memory if bit 19 in the network configuration register is set. Type ID Checking The contents of the type_id register are compared against the length/type ID of received frames (i.e., bytes 13 and 14). Bit 22 in the receive buffer descriptor status is set if there is a match. The reset state of this register is zero which is unlikely to match the length/type ID of any valid Ethernet frame. Note: A type ID match does not affect whether a frame is copied to memory. 29.5.10 448 32058H–AVR32–03/09 AT32UC3A 29.5.11 VLAN Support An Ethernet encoded 802.1Q VLAN tag looks like this: Table 29-4. 802.1Q VLAN Tag TCI (Tag Control Information) 16 bits First 3 bits priority, then CFI bit, last 12 bits VID TPID (Tag Protocol Identifier) 16 bits 0x8100 The VLAN tag is inserted at the 13th byte of the frame, adding an extra four bytes to the frame. If the VID (VLAN identifier) is null (0x000), this indicates a priority-tagged frame. The MAC can support frame lengths up to 1536 bytes, 18 bytes more than the original Ethernet maximum frame length of 1518 bytes. This is achieved by setting bit 8 in the network configuration register. The following bits in the receive buffer descriptor status word give information about VLAN tagged frames: • Bit 21 set if receive frame is VLAN tagged (i.e. type id of 0x8100) • Bit 20 set if receive frame is priority tagged (i.e. type id of 0x8100 and null VID). (If bit 20 is set bit 21 is set also.) • Bit 19, 18 and 17 set to priority if bit 21 is set • Bit 16 set to CFI if bit 21 is set 29.5.12 PHY Maintenance The register MAN enables the MACB to communicate with a PHY by means of the MDIO interface. It is used during auto-negotiation to ensure that the MACB and the PHY are configured for the same speed and duplex configuration. The PHY maintenance register is implemented as a shift register. Writing to the register starts a shift operation which is signalled as complete when bit two is set in the network status register (about 2000 MCK cycles later when bit ten is set to zero, and bit eleven is set to one in the network configuration register). An interrupt is generated as this bit is set. During this time, the MSB of the register is output on the MDIO pin and the LSB updated from the MDIO pin with each MDC cycle. This causes transmission of a PHY management frame on MDIO. Reading during the shift operation returns the current contents of the shift register. At the end of management operation, the bits have shifted back to their original locations. For a read operation, the data bits are updated with data read from the PHY. It is important to write the correct values to the register to ensure a valid PHY management frame is produced. The MDIO interface can read IEEE 802.3 clause 45 PHYs as well as clause 22 PHYs. To read clause 45 PHYs, bits[31:28] should be written as 0x0011. For a description of MDC generation, see the network configuration register in the ”Network Control Register” on page 456. 29.5.13 Media Independent Interface The Ethernet MAC is capable of interfacing to both RMII and MII Interfaces. The RMII bit in the USRIO register controls the interface that is selected. When this bit is set, the RMII interface is selected, else the MII interface is selected. 449 32058H–AVR32–03/09 AT32UC3A The MII and RMII interface are capable of both 10Mb/s and 100Mb/s data rates as described in the IEEE 802.3u standard. The signals used by the MII and RMII interfaces are described in Table 29-5. Table 29-5. Pin Name ETXCK_EREFCK ECRS ECOL ERXDV ERX0 - ERX3 ERXER ERXCK ETXEN ETX0-ETX3 ETXER ETXCK: Transmit Clock ECRS: Carrier Sense ECOL: Collision Detect ERXDV: Data Valid ERX0 - ERX3: 4-bit Receive Data ERXER: Receive Error ERXCK: Receive Clock ETXEN: Transmit Enable ETX0 - ETX3: 4-bit Transmit Data ETXER: Transmit Error ETXEN: Transmit Enable ETX0 - ETX1: 2-bit Transmit Data ECRSDV: Carrier Sense/Data Valid ERX0 - ERX1: 2-bit Receive Data ERXER: Receive Error Pin Configuration MII RMII EREFCK: Reference Clock The intent of the RMII is to provide a reduced pin count alternative to the IEEE 802.3u MII. It uses 2 bits for transmit (ETX0 and ETX1) and two bits for receive (ERX0 and ERX1). There is a Transmit Enable (ETXEN), a Receive Error (ERXER), a Carrier Sense (ECRS_DV), and a 50 MHz Reference Clock (ETXCK_EREFCK) for 100Mb/s data rate. 29.5.13.1 RMII Transmit and Receive Operation The same signals are used internally for both the RMII and the MII operations. The RMII maps these signals in a more pin-efficient manner. The transmit and receive bits are converted from a 4-bit parallel format to a 2-bit parallel scheme that is clocked at twice the rate. The carrier sense and data valid signals are combined into the ECRSDV signal. This signal contains information on carrier sense, FIFO status, and validity of the data. Transmit error bit (ETXER) and collision detect (ECOL) are not used in RMII mode. 450 32058H–AVR32–03/09 AT32UC3A 29.6 29.6.1 29.6.1.1 Programming Interface Initialization Configuration Initialization of the MACB configuration (e.g. frequency ratios) must be done while the transmit and receive circuits are disabled. See the description of the network control register and network configuration register later in this document. Receive Buffer List Receive data is written to areas of data (i.e., buffers) in system memory. These buffers are listed in another data structure that also resides in main memory. This data structure (receive buffer queue) is a sequence of descriptor entries as defined in ”Receive Buffer Descriptor Entry” on page 440. It points to this data structure. 29.6.1.2 Figure 29-2. Receive Buffer List Receive Buffer 0 Receive Buffer Queue Pointer (MAC Register) Receive Buffer 1 Receive Buffer N Receive Buffer Descriptor List (In memory) (In memory) To create the list of buffers: 1. Allocate a number (n) of buffers of 128 bytes in system memory. 2. Allocate an area 2n words for the receive buffer descriptor entry in system memory and create n entries in this list. Mark all entries in this list as owned by MACB, i.e., bit 0 of word 0 set to 0. 3. If less than 1024 buffers are defined, the last descriptor must be marked with the wrap bit (bit 1 in word 0 set to 1). 4. Write address of receive buffer descriptor entry to MACB register receive_buffer queue pointer. 5. The receive circuits can then be enabled by writing to the address recognition registers and then to the network control register. 451 32058H–AVR32–03/09 AT32UC3A 29.6.1.3 Transmit Buffer List Transmit data is read from the system memory These buffers are listed in another data structure that also resides in main memory. This data structure (Transmit Buffer Queue) is a sequence of descriptor entries (as defined in Table 29-2 on page 443) that points to this data structure. To create this list of buffers: 1. Allocate a number (n) of buffers of between 1 and 2047 bytes of data to be transmitted in system memory. Up to 128 buffers per frame are allowed. 2. Allocate an area 2n words for the transmit buffer descriptor entry in system memory and create N entries in this list. Mark all entries in this list as owned by MACB, i.e. bit 31 of word 1 set to 0. 3. If fewer than 1024 buffers are defined, the last descriptor must be marked with the wrap bit — bit 30 in word 1 set to 1. 4. Write address of transmit buffer descriptor entry to MACB register transmit_buffer queue pointer. 5. The transmit circuits can then be enabled by writing to the network control register. 29.6.1.4 Address Matching The MACB register-pair hash address and the four specific address register-pairs must be written with the required values. Each register-pair comprises a bottom register and top register, with the bottom register being written first. The address matching is disabled for a particular register-pair after the bottom-register has been written and re-enabled when the top register is written. See Section “29.5.5” on page 446. for details of address matching. Each register-pair may be written at any time, regardless of whether the receive circuits are enabled or disabled. Interrupts There are 14 interrupt conditions that are detected within the MACB. These are ORed to make a single interrupt. This interrupt is passed to the interrupt controller. On receipt of the interrupt signal, the CPU enters the interrupt handler. To ascertain which interrupt has been generated, read the interrupt status register. Note that this register clears itself when read. At reset, all interrupts are disabled. To enable an interrupt, write to interrupt enable register with the pertinent interrupt bit set to 1. To disable an interrupt, write to interrupt disable register with the pertinent interrupt bit set to 1. To check whether an interrupt is enabled or disabled, read interrupt mask register: if the bit is set to 1, the interrupt is disabled. 29.6.1.6 Transmitting Frames To set up a frame for transmission: 1. Enable transmit in the network control register. 2. Allocate an area of system memory for transmit data. This does not have to be contiguous, varying byte lengths can be used as long as they conclude on byte borders. 3. Set-up the transmit buffer list. 4. Set the network control register to enable transmission and enable interrupts. 5. Write data for transmission into these buffers. 6. Write the address to transmit buffer descriptor queue pointer. 7. Write control and length to word one of the transmit buffer descriptor entry. 8. Write to the transmit start bit in the network control register. 29.6.1.5 452 32058H–AVR32–03/09 AT32UC3A 29.6.1.7 Receiving Frames When a frame is received and the receive circuits are enabled, the MACB checks the address and, in the following cases, the frame is written to system memory: • if it matches one of the four specific address registers. • if it matches the hash address function. • if it is a broadcast address (0xFFFFFFFFFFFF) and broadcasts are allowed. • if the MACB is configured to copy all frames. • if the EAM is asserted before four words have been loaded into the receive FIFO. The register receive buffer queue pointer points to the next entry (see Table 29-1 on page 440) and the MACB uses this as the address in system memory to write the frame to. Once the frame has been completely and successfully received and written to system memory, the MACB then updates the receive buffer descriptor entry with the reason for the address match and marks the area as being owned by software. Once this is complete an interrupt receive complete is set. Software is then responsible for handling the data in the buffer and then releasing the buffer by writing the ownership bit back to 0. If the MACB is unable to write the data at a rate to match the incoming frame, then an interrupt receive overrun is set. If there is no receive buffer available, i.e., the next buffer is still owned by software, the interrupt receive buffer not available is set. If the frame is not successfully received, a statistic register is incremented and the frame is discarded without informing software. 453 32058H–AVR32–03/09 AT32UC3A 29.7 Ethernet MAC (MACB) User Interface Ethernet MAC (MACB) Register Mapping Register Network Control Register Network Configuration Register Network Status Register Reserved Reserved Transmit Status Register Receive Buffer Queue Pointer Register Transmit Buffer Queue Pointer Register Receive Status Register Interrupt Status Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register Phy Maintenance Register Pause Time Register Pause Frames Received Register Frames Transmitted Ok Register Single Collision Frames Register Multiple Collision Frames Register Frames Received Ok Register Frame Check Sequence Errors Register Alignment Errors Register Deferred Transmission Frames Register Late Collisions Register Excessive Collisions Register Transmit Underrun Errors Register Carrier Sense Errors Register Receive Resource Errors Register Receive Overrun Errors Register Receive Symbol Errors Register Excessive Length Errors Register Receive Jabbers Register Undersize Frames Register SQE Test Errors Register Received Length Field Mismatch Register TSR RBQP TBQP RSR ISR IER IDR IMR MAN PTR PFR FTO SCF MCF FRO FCSE ALE DTF LCOL EXCOL TUND CSE RRE ROV RSE ELE RJA USF STE RLE Read/Write Read/Write Read/Write Read/Write Read/Write Write-only Write-only Read-only Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_3FFF 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 Name NCR NCFG NSR Access Read/Write Read/Write Read-only Reset Value 0 0x800 - Table 29-6. Offset 0x00 0x04 0x08 0x0C 0x10 0x14 0x18 0x1C 0x20 0x24 0x28 0x2C 0x30 0x34 0x38 0x3C 0x40 0x44 0x48 0x4C 0x50 0x54 0x58 0x5C 0x60 0x64 0x68 0x6C 0x70 0x74 0x78 0x7C 0x80 0x84 0x88 454 32058H–AVR32–03/09 AT32UC3A Table 29-6. Offset 0x8C 0x90 0x94 0x98 0x9C 0xA0 0xA4 0xA8 0xAC 0xB0 0xB4 0xB8 0xBC 0xC0 0xC4 0xC8 - 0xFC Ethernet MAC (MACB) Register Mapping (Continued) Register Transmitted Pause Frames Register Hash Register Bottom [31:0] Register Hash Register Top [63:32] Register Specific Address 1 Bottom Register Specific Address 1 Top Register Specific Address 2 Bottom Register Specific Address 2 Top Register Specific Address 3 Bottom Register Specific Address 3 Top Register Specific Address 4 Bottom Register Specific Address 4 Top Register Type ID Checking Register Transmit Pause Quantum Register User Input/output Register Wake on LAN Register Reserved Name TPF HRB HRT SA1B SA1T SA2B SA2T SA3B SA3T SA4B SA4T TID TPQ USRIO WOL – Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Reset Value 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_0000 0x0000_FFFF 0x0000_0000 0x0000_0000 – 455 32058H–AVR32–03/09 AT32UC3A 29.7.1 Network Control Register Register Name: NCR Access Type: 31 – 23 – 15 – 7 WESTAT Read/Write 30 – 22 – 14 – 6 INCSTAT 29 – 21 – 13 – 5 CLRSTAT 28 – 20 – 12 TZQ 4 MPE 27 – 19 – 11 TPF 3 TE 26 – 18 – 10 THALT 2 RE 25 – 17 – 9 TSTART 1 LLB 24 – 16 – 8 BP 0 LB • LB: LoopBack Asserts the loopback signal to the PHY. • LLB: LoopBack Local connects txd to rxd, tx_en to rx_dv, forces full duplex and drives rx_clk and tx_clk with pclk divided by 4. rx_clk and tx_clk may glitch as the MACB is switched into and out of internal loop back. It is important that receive and transmit circuits have already been disabled when making the switch into and out of internal loop back. This function may not be supported by some instantiations of the MACB. • RE: Receive enable When set, enables the MACB to receive data. When reset, frame reception stops immediately and the receive FIFO is cleared. The receive queue pointer register is unaffected. • TE: Transmit enable When set, enables the Ethernet transmitter to send data. When reset, transmission stops immediately, the transmit FIFO and control registers are cleared and the transmit queue pointer register resets to point to the start of the transmit descriptor list. • MPE: Management port enable Set to one to enable the management port. When zero, forces MDIO to high impedance state and MDC low. • CLRSTAT: Clear statistics registers This bit is write only. Writing a one clears the statistics registers. • INCSTAT: Increment statistics registers This bit is write only. Writing a one increments all the statistics registers by one for test purposes. • WESTAT: Write enable for statistics registers Setting this bit to one makes the statistics registers writable for functional test purposes. • BP: Back pressure If set in half duplex mode, forces collisions on all received frames. 456 32058H–AVR32–03/09 AT32UC3A • TSTART: Start transmission Writing one to this bit starts transmission. • THALT: Transmit halt Writing one to this bit halts transmission as soon as any ongoing frame transmission ends. • TPF: Transmit pause frame Writing one to this bit transmits a pause frame with the pause quantum from the transmit pause quantum register at the next available transmitter idle time. • TZQ: Transmit zero quantum pause frame Writing a one to this bit transmits a pause frame with zero pause quantum at the next available transmitter idle time. 457 32058H–AVR32–03/09 AT32UC3A 29.7.2 Network Configuration Register Register Name: NCFGR Access Type: 31 – 23 – 15 RBOF 7 UNI 6 MTI Read/Write 30 – 22 – 14 29 – 21 – 13 PAE 5 NBC 28 – 20 – 12 RTY 4 CAF 27 – 19 IRXFCS 11 CLK 3 JFRAME 2 Bit rate 26 – 18 EFRHD 10 25 – 17 DRFCS 9 EAE 1 FD 24 – 16 RLCE 8 BIG 0 SPD • SPD: Speed Set to 1 to indicate 100 Mbit/s operation, 0 for 10 Mbit/s. The value of this pin is reflected on the speed pin. • FD: Full Duplex If set to 1, the transmit block ignores the state of collision and carrier sense and allows receive while transmitting. Also controls the half_duplex pin. • Bit rate: If set to 1 to configure the interface for serial operation. Must be set before receive and transmit enable in the network control register. If set a serial interface is configured with transmit and receive data being driven out on txd[0] and received on rxd[0] serially. Also the crs and rx_dv are logically ORed together so either may be used as the data valid signal. • CAF: Copy All Frames When set to 1, all valid frames are received. • JFRAME: Jumbo Frames Set to one to enable jumbo frames of up to 10240 bytes to be accepted. • NBC: No Broadcast When set to 1, frames addressed to the broadcast address of all ones are not received. • MTI: Multicast Hash Enable When set, multicast frames are received when the 6-bit hash function of the destination address points to a bit that is set in the hash register. • UNI: Unicast Hash Enable When set, unicast frames are received when the 6-bit hash function of the destination address points to a bit that is set in the hash register. • BIG: Receive 1536 bytes frames Setting this bit means the MACB receives frames up to 1536 bytes in length. Normally, the MACB would reject any frame above 1518 bytes. • EAE: External address match enable When set, the eam pin can be used to copy frames to memory. 458 32058H–AVR32–03/09 AT32UC3A • CLK: MDC clock divider Set according to system clock speed. This determines by what number system clock is divided to generate MDC. For conformance with 802.3, MDC must not exceed 2.5MHz (MDC is only active during MDIO read and write operations). CLK 00 01 10 11 MDC MCK divided by 8 (MCK up to 20 MHz) MCK divided by 16 (MCK up to 40 MHz) MCK divided by 32 (MCK up to 80 MHz) MCK divided by 64 (MCK up to 160 MHz) • RTY: Retry test Must be set to zero for normal operation. If set to one, the back off between collisions is always one slot time. Setting this bit to one helps testing the too many retries condition. Also used in the pause frame tests to reduce the pause counters decrement time from 512 bit times, to every rx_clk cycle. • PAE: Pause Enable When set, transmission pauses when a valid pause frame is received. • RBOF: Receive Buffer Offset Indicates the number of bytes by which the received data is offset from the start of the first receive buffer. RBOF 00 01 10 11 Offset No offset from start of receive buffer One-byte offset from start of receive buffer Two-byte offset from start of receive buffer Three-byte offset from start of receive buffer • RLCE: Receive Length field Checking Enable When set, frames with measured lengths shorter than their length fields are discarded. Frames containing a type ID in bytes 13 and 14 — length/type ID = 0600 — are not be counted as length errors. • DRFCS: Discard Receive FCS When set, the FCS field of received frames will not be copied to memory. • EFRHD: Enable Frames to be received in half-duplex mode while transmitting. • IRXFCS: Ignore RX FCS When set, frames with FCS/CRC errors are not rejected and no FCS error statistics are counted. For normal operation, this bit must be set to 0. 459 32058H–AVR32–03/09 AT32UC3A 29.7.3 Network Status Register Register Name: NSR Access Type: 31 – 23 – 15 – 7 – Read-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 IDLE 25 – 17 – 9 – 1 MDIO 24 – 16 – 8 – 0 - • MDIO Returns status of the mdio_in pin. Use the PHY maintenance register for reading managed frames rather than this bit. • IDLE 0 = The PHY logic is running. 1 = The PHY management logic is idle (i.e., has completed). 460 32058H–AVR32–03/09 AT32UC3A 29.7.4 Transmit Status Register Register Name: TSR Access Type: 31 – 23 – 15 – 7 – Read/Write 30 – 22 – 14 – 6 UND 29 – 21 – 13 – 5 COMP 28 – 20 – 12 – 4 BEX 27 – 19 – 11 – 3 TGO 26 – 18 – 10 – 2 RLE 25 – 17 – 9 – 1 COL 24 – 16 – 8 – 0 UBR This register, when read, provides details of the status of a transmit. Once read, individual bits may be cleared by writing 1 to them. It is not possible to set a bit to 1 by writing to the register. • UBR: Used Bit Read Set when a transmit buffer descriptor is read with its used bit set. Cleared by writing a one to this bit. • COL: Collision Occurred Set by the assertion of collision. Cleared by writing a one to this bit. • RLE: Retry Limit exceeded Cleared by writing a one to this bit. • TGO: Transmit Go If high transmit is active. • BEX: Buffers exhausted mid frame If the buffers run out during transmission of a frame, then transmission stops, FCS shall be bad and tx_er asserted. Cleared by writing a one to this bit. • COMP: Transmit Complete Set when a frame has been transmitted. Cleared by writing a one to this bit. • UND: Transmit Underrun Set when transmit DMA was not able to read data from memory, either because the bus was not granted in time, because a not OK hresp(bus error) was returned or because a used bit was read midway through frame transmission. If this occurs, the transmitter forces bad CRC. Cleared by writing a one to this bit. 461 32058H–AVR32–03/09 AT32UC3A 29.7.5 Receive Buffer Queue Pointer Register Register Name: RBQP Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 ADDR 4 3 2 1 – 0 – This register points to the entry in the receive buffer queue (descriptor list) currently being used. It is written with the start location of the receive buffer descriptor list. The lower order bits increment as buffers are used up and wrap to their original values after either 1024 buffers or when the wrap bit of the entry is set. Reading this register returns the location of the descriptor currently being accessed. This value increments as buffers are used. Software should not use this register for determining where to remove received frames from the queue as it constantly changes as new frames are received. Software should instead work its way through the buffer descriptor queue checking the used bits. Receive buffer writes also comprise bursts of two words and, as with transmit buffer reads, it is recommended that bit 2 is always written with zero to prevent a burst crossing a 1K boundary, in violation of the System Bus specification. • ADDR: Receive buffer queue pointer address Written with the address of the start of the receive queue, reads as a pointer to the current buffer being used. 462 32058H–AVR32–03/09 AT32UC3A 29.7.6 Transmit Buffer Queue Pointer Register Register Name: TBQP Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 ADDR 4 3 2 1 – 0 – This register points to the entry in the transmit buffer queue (descriptor list) currently being used. It is written with the start location of the transmit buffer descriptor list. The lower order bits increment as buffers are used up and wrap to their original values after either 1024 buffers or when the wrap bit of the entry is set. This register can only be written when bit 3 in the transmit status register is low. As transmit buffer reads consist of bursts of two words, it is recommended that bit 2 is always written with zero to prevent a burst crossing a 1K boundary, in violation of the System Bus specification. • ADDR: Transmit buffer queue pointer address Written with the address of the start of the transmit queue, reads as a pointer to the first buffer of the frame being transmitted or about to be transmitted. 463 32058H–AVR32–03/09 AT32UC3A 29.7.7 Receive Status Register Register Name: RSR Access Type: 31 – 23 – 15 – 7 – Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 OVR 25 – 17 – 9 – 1 REC 24 – 16 – 8 – 0 BNA This register, when read, provides details of the status of a receive. Once read, individual bits may be cleared by writing 1 to them. It is not possible to set a bit to 1 by writing to the register. • BNA: Buffer Not Available An attempt was made to get a new buffer and the pointer indicated that it was owned by the processor. The DMA rereads the pointer each time a new frame starts until a valid pointer is found. This bit is set at each attempt that fails even if it has not had a successful pointer read since it has been cleared. Cleared by writing a one to this bit. • REC: Frame Received One or more frames have been received and placed in memory. Cleared by writing a one to this bit. • OVR: Receive Overrun The DMA block was unable to store the receive frame to memory, either because the bus was not granted in time or because a not OK hresp(bus error) was returned. The buffer is recovered if this happens. Cleared by writing a one to this bit. 464 32058H–AVR32–03/09 AT32UC3A 29.7.8 Interrupt Status Register Register Name: ISR Access Type: 31 – 23 – 15 – 7 TCOMP Read/Write 30 – 22 – 14 – 6 TXERR 29 – 21 – 13 PTZ 5 RLE 28 – 20 – 12 PFR 4 TUND 27 – 19 – 11 HRESP 3 TXUBR 26 – 18 – 10 ROVR 2 RXUBR 25 – 17 – 9 1 RCOMP 24 – 16 – 8 – 0 MFD • MFD: Management Frame Done The PHY maintenance register has completed its operation. Cleared on read. • RCOMP: Receive Complete A frame has been stored in memory. Cleared on read. • RXUBR: Receive Used Bit Read Set when a receive buffer descriptor is read with its used bit set. Cleared on read. • TXUBR: Transmit Used Bit Read Set when a transmit buffer descriptor is read with its used bit set. Cleared on read. • TUND: Ethernet Transmit Buffer Underrun The transmit DMA did not fetch frame data in time for it to be transmitted or hresp returned not OK. Also set if a used bit is read mid-frame or when a new transmit queue pointer is written. Cleared on read. • RLE: Retry Limit Exceeded Cleared on read. • TXERR: Transmit Error Transmit buffers exhausted in mid-frame - transmit error. Cleared on read. • TCOMP: Transmit Complete Set when a frame has been transmitted. Cleared on read. • ROVR: Receive Overrun Set when the receive overrun status bit gets set. Cleared on read. • HRESP: Hresp not OK Set when the DMA block sees a bus error. Cleared on read. • PFR: Pause Frame Received Indicates a valid pause has been received. Cleared on a read. • PTZ: Pause Time Zero Set when the pause time register, 0x38 decrements to zero. Cleared on a read. 465 32058H–AVR32–03/09 AT32UC3A 29.7.9 Interrupt Enable Register Register Name: IER 466 32058H–AVR32–03/09 AT32UC3A Access Type: 31 – 23 – 15 – 7 TCOMP Write-only 30 – 22 – 14 – 6 TXERR 29 – 21 – 13 PTZ 5 RLE 28 – 20 – 12 PFR 4 TUND 27 – 19 – 11 HRESP 3 TXUBR 26 – 18 – 10 ROVR 2 RXUBR 25 – 17 – 9 24 – 16 – 8 – 0 MFD 1 RCOMP • MFD: Management Frame sent Enable management done interrupt. • RCOMP: Receive Complete Enable receive complete interrupt. • RXUBR: Receive Used Bit Read Enable receive used bit read interrupt. • TXUBR: Transmit Used Bit Read Enable transmit used bit read interrupt. • TUND: Ethernet Transmit Buffer Underrun Enable transmit underrun interrupt. • RLE: Retry Limit Exceeded Enable retry limit exceeded interrupt. • TXERR: Transmit Error Enable transmit buffers exhausted in mid-frame interrupt. • TCOMP: Transmit Complete Enable transmit complete interrupt. • ROVR: Receive Overrun Enable receive overrun interrupt. • HRESP: Hresp not OK Enable Hresp not OK interrupt. • PFR: Pause Frame Received Enable pause frame received interrupt. • PTZ: Pause Time Zero Enable pause time zero interrupt. 467 32058H–AVR32–03/09 AT32UC3A 29.7.10 Interrupt Disable Register Register Name: IDR Access Type: 31 – 23 – 15 – 7 TCOMP Write-only 30 – 22 – 14 – 6 TXERR 29 – 21 – 13 PTZ 5 RLE 28 – 20 – 12 PFR 4 TUND 27 – 19 – 11 HRESP 3 TXUBR 26 – 18 – 10 ROVR 2 RXUBR 25 – 17 – 9 1 RCOMP 24 – 16 – 8 – 0 MFD • MFD: Management Frame sent Disable management done interrupt. • RCOMP: Receive Complete Disable receive complete interrupt. • RXUBR: Receive Used Bit Read Disable receive used bit read interrupt. • TXUBR: Transmit Used Bit Read Disable transmit used bit read interrupt. • TUND: Ethernet Transmit Buffer Underrun Disable transmit underrun interrupt. • RLE: Retry Limit Exceeded Disable retry limit exceeded interrupt. • TXERR: Transmit Error Disable transmit buffers exhausted in mid-frame interrupt. • TCOMP: Transmit Complete Disable transmit complete interrupt. • ROVR: Receive Overrun Disable receive overrun interrupt. • HRESP: Hresp not OK Disable Hresp not OK interrupt. • PFR: Pause Frame Received Disable pause frame received interrupt. • PTZ: Pause Time Zero Disable pause time zero interrupt. 468 32058H–AVR32–03/09 AT32UC3A 29.7.11 Interrupt Mask Register Register Name: IMR Access Type: 31 – 23 – 15 – 7 TCOMP Write-only 30 – 22 – 14 – 6 TXERR 29 – 21 – 13 PTZ 5 RLE 28 – 20 – 12 PFR 4 TUND 27 – 19 – 11 HRESP 3 TXUBR 26 – 18 – 10 ROVR 2 RXUBR 25 – 17 – 9 1 RCOMP 24 – 16 – 8 – 0 MFD • MFD: Management Frame sent Management done interrupt masked. • RCOMP: Receive Complete Receive complete interrupt masked. • RXUBR: Receive Used Bit Read Receive used bit read interrupt masked. • TXUBR: Transmit Used Bit Read Transmit used bit read interrupt masked. • TUND: Ethernet Transmit Buffer Underrun Transmit underrun interrupt masked. • RLE: Retry Limit Exceeded Retry limit exceeded interrupt masked. • TXERR: Transmit Error Transmit buffers exhausted in mid-frame interrupt masked. • TCOMP: Transmit Complete Transmit complete interrupt masked. • ROVR: Receive Overrun Receive overrun interrupt masked. • HRESP: Hresp not OK Hresp not OK interrupt masked. • PFR: Pause Frame Received Pause frame received interrupt masked. • PTZ: Pause Time Zero Pause time zero interrupt masked. 469 32058H–AVR32–03/09 AT32UC3A 29.7.12 PHY Maintenance Register Register Name: MAN Access Type: 31 SOF 23 PHYA 15 22 21 Read/Write 30 29 RW 20 REGA 12 DATA 19 18 28 27 26 PHYA 17 CODE 11 10 9 8 16 25 24 14 13 7 6 5 4 DATA 3 2 1 0 • DATA For a write operation this is written with the data to be written to the PHY. After a read operation this contains the data read from the PHY. • CODE: Must be written to 10. Reads as written. • REGA: Register Address Specifies the register in the PHY to access. • PHYA: PHY Address • RW: Read/Write 10 is read; 01 is write. Any other value is an invalid PHY management frame • SOF: Start of frame Must be written 01 for a valid frame. 470 32058H–AVR32–03/09 AT32UC3A 29.7.13 Pause Time Register Register Name: PTR Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 PTIME 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 PTIME 3 2 1 0 • PTIME: Pause Time Stores the current value of the pause time register which is decremented every 512 bit times. 471 32058H–AVR32–03/09 AT32UC3A 29.7.14 Hash Register Bottom Register Name: HRB Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR: Bits 31:0 of the hash address register. See ”Hash Addressing” on page 447. 472 32058H–AVR32–03/09 AT32UC3A 29.7.15 Hash Register Top Register Name: HRT Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR: Bits 63:32 of the hash address register. See ”Hash Addressing” on page 447. 473 32058H–AVR32–03/09 AT32UC3A 29.7.16 Specific Address 1 Bottom Register Register Name: SA1B Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR Least significant bits of the destination address. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received. 474 32058H–AVR32–03/09 AT32UC3A 29.7.17 Specific Address 1 Top Register Register Name: SA1T Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 ADDR 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 ADDR 3 2 1 0 • ADDR The most significant bits of the destination address, that is bits 47 to 32. 475 32058H–AVR32–03/09 AT32UC3A 29.7.18 Specific Address 2 Bottom Register Register Name: SA2B Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR Least significant bits of the destination address. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received. 476 32058H–AVR32–03/09 AT32UC3A 29.7.19 Specific Address 2 Top Register Register Name: SA2T Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 ADDR 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 ADDR 3 2 1 0 • ADDR The most significant bits of the destination address, that is bits 47 to 32. 477 32058H–AVR32–03/09 AT32UC3A 29.7.20 Specific Address 3 Bottom Register Register Name: SA3B Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR Least significant bits of the destination address. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received. 478 32058H–AVR32–03/09 AT32UC3A 29.7.21 Specific Address 3 Top Register Register Name: SA3T Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 ADDR 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 ADDR 3 2 1 0 • ADDR The most significant bits of the destination address, that is bits 47 to 32. 479 32058H–AVR32–03/09 AT32UC3A 29.7.22 Specific Address 4 Bottom Register Register Name: SA4B Access Type: 31 Read/Write 30 29 28 ADDR 27 26 25 24 23 22 21 20 ADDR 19 18 17 16 15 14 13 12 ADDR 11 10 9 8 7 6 5 4 ADDR 3 2 1 0 • ADDR Least significant bits of the destination address. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received. 480 32058H–AVR32–03/09 AT32UC3A 29.7.23 Specific Address 4 Top Register Register Name: SA4T Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 ADDR 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 ADDR 3 2 1 0 • ADDR The most significant bits of the destination address, that is bits 47 to 32. 481 32058H–AVR32–03/09 AT32UC3A 29.7.24 Type ID Checking Register Register Name: TID Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 TID 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 TID 3 2 1 0 • TID: Type ID checking For use in comparisons with received frames TypeID/Length field. 482 32058H–AVR32–03/09 AT32UC3A 29.7.25 Transmit Pause Quantum Register Register Name: TPQ Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 TPQ 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 TPQ 3 2 1 0 • TPQ: Transmit Pause Quantum Used in hardware generation of transmitted pause frames as value for pause quantum. 483 32058H–AVR32–03/09 AT32UC3A 29.7.26 User Input/Output Register Register Name: USRIO Access Type: 31 – 23 – 15 – 7 – Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 TX_PAUSE_ ZERO 26 – 18 – 10 – 2 TX_PAUSE 25 – 17 – 9 – 1 EAM 24 – 16 – 8 – 0 RMII • RMII When set, this bit enables the MII operation mode. When reset, it selects the RMII mode. • EAM When set, this bit causes a frame to be copied to memory, if this feature is enabled by the EAE bit in NCFGR. Otherwise, no frame is copied. • TX_PAUSE Toggling this bit causes a PAUSE frame to be transmitted. • TX_PAUSE_ZERO Selects either zero or the transmit quantum register as the transmitted pause frame quantum. 484 32058H–AVR32–03/09 AT32UC3A 29.7.27 Wake-on-LAN Register Register Name: WOL Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 IP 27 – 19 MTI 11 26 – 18 SA1 10 25 – 17 ARP 9 24 – 16 MAG 8 7 6 5 4 IP 3 2 1 0 • IP: ARP request IP address Written to define the least significant 16 bits of the target IP address that is matched to generate a Wake-on-LAN event. A value of zero does not generate an event, even if this is matched by the received frame. • MAG: Magic packet event enable When set, magic packet events causes the wol output to be asserted. • ARP: ARP request event enable When set, ARP request events causes the wol output to be asserted. • SA1: Specific address register 1 event enable When set, specific address 1 events causes the wol output to be asserted. • MTI: Multicast hash event enable When set, multicast hash events causes the wol output to be asserted. 485 32058H–AVR32–03/09 AT32UC3A 29.7.28 MACB Statistic Registers These registers reset to zero on a read and stick at all ones when they count to their maximum value. They should be read frequently enough to prevent loss of data. The receive statistics registers are only incremented when the receive enable bit is set in the network control register. To write to these registers, bit 7, WESTAT, in the network control register, NCR, must be set. The statistics register block contains the following registers. 29.7.28.1 Pause Frames Received Register Register Name: PFR Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 FROK 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 FROK 3 2 1 0 • FROK: Pause Frames received OK A 16-bit register counting the number of good pause frames received. A good frame has a length of 64 to 1518 (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set) and has no FCS, alignment or receive symbol errors. 29.7.28.2 Frames Transmitted OK Register Register Name: FTO Access Type: 31 – 23 Read/Write 30 – 22 29 – 21 28 – 20 FTOK 27 – 19 26 – 18 25 – 17 24 – 16 15 14 13 12 FTOK 11 10 9 8 7 6 5 4 FTOK 3 2 1 0 • FTOK: Frames Transmitted OK A 24-bit register counting the number of frames successfully transmitted, i.e., no underrun and not too many retries. 486 32058H–AVR32–03/09 AT32UC3A 29.7.28.3 Single Collision Frames Register Register Name: SCF Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 SCF 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 SCF 3 2 1 0 • SCF: Single Collision Frames A 16-bit register counting the number of frames experiencing a single collision before being successfully transmitted, i.e., no underrun. 29.7.28.4 Multicollision Frames Register Register Name: MCF Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 MCF 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 MCF 3 2 1 0 • MCF: Multicollision Frames A 16-bit register counting the number of frames experiencing between two and fifteen collisions prior to being successfully transmitted, i.e., no underrun and not too many retries. 487 32058H–AVR32–03/09 AT32UC3A 29.7.28.5 Frames Received OK Register Register Name: FRO Access Type: 31 – 23 Read/Write 30 – 22 29 – 21 28 – 20 FROK 27 – 19 26 – 18 25 – 17 24 – 16 15 14 13 12 FROK 11 10 9 8 7 6 5 4 FROK 3 2 1 0 • FROK: Frames Received OK A 24-bit register counting the number of good frames received, i.e., address recognized and successfully copied to memory. A good frame is of length 64 to 1518 bytes (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set) and has no FCS, alignment or receive symbol errors. 29.7.28.6 Frames Check Sequence Errors Register Register Name: FCSE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 FCSE 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • FCSE: Frame Check Sequence Errors An 8-bit register counting frames that are an integral number of bytes, have bad CRC and are between 64 and 1518 bytes in length (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set). This register is also incremented if a symbol error is detected and the frame is of valid length and has an integral number of bytes. 488 32058H–AVR32–03/09 AT32UC3A 29.7.28.7 Alignment Errors Register Register Name: ALE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 ALE 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • ALE: Alignment Errors An 8-bit register counting frames that are not an integral number of bytes long and have bad CRC when their length is truncated to an integral number of bytes and are between 64 and 1518 bytes in length (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set). This register is also incremented if a symbol error is detected and the frame is of valid length and does not have an integral number of bytes. 29.7.28.8 Deferred Transmission Frames Register Register Name: DTF Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 DTF 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 DTF 3 2 1 0 • DTF: Deferred Transmission Frames A 16-bit register counting the number of frames experiencing deferral due to carrier sense being active on their first attempt at transmission. Frames involved in any collision are not counted nor are frames that experienced a transmit underrun. 489 32058H–AVR32–03/09 AT32UC3A 29.7.28.9 Late Collisions Register Register Name: LCOL Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 LCOL 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • LCOL: Late Collisions An 8-bit register counting the number of frames that experience a collision after the slot time (512 bits) has expired. A late collision is counted twice; i.e., both as a collision and a late collision. 29.7.28.10 Excessive Collisions Register Register Name: EXCOL Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 EXCOL 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • EXCOL: Excessive Collisions An 8-bit register counting the number of frames that failed to be transmitted because they experienced 16 collisions. 490 32058H–AVR32–03/09 AT32UC3A 29.7.28.11 Transmit Underrun Errors Register Register Name: TUND Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 TUND 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • TUND: Transmit Underruns An 8-bit register counting the number of frames not transmitted due to a transmit DMA underrun. If this register is incremented, then no other statistics register is incremented. 29.7.28.12 Carrier Sense Errors Register Register Name: CSE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 CSE 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • CSE: Carrier Sense Errors An 8-bit register counting the number of frames transmitted where carrier sense was not seen during transmission or where carrier sense was deasserted after being asserted in a transmit frame without collision (no underrun). Only incremented in half-duplex mode. The only effect of a carrier sense error is to increment this register. The behavior of the other statistics registers is unaffected by the detection of a carrier sense error. 491 32058H–AVR32–03/09 AT32UC3A 29.7.28.13 Receive Resource Errors Register Register Name: RRE Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 RRE 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 RRE 3 2 1 0 • RRE: Receive Resource Errors A 16-bit register counting the number of frames that were address matched but could not be copied to memory because no receive buffer was available. 29.7.28.14 Receive Overrun Errors Register Register Name: ROVR Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 ROVR 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • ROVR: Receive Overrun An 8-bit register counting the number of frames that are address recognized but were not copied to memory due to a receive DMA overrun. 492 32058H–AVR32–03/09 AT32UC3A 29.7.28.15 Receive Symbol Errors Register Register Name: RSE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 RSE 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • RSE: Receive Symbol Errors An 8-bit register counting the number of frames that had rx_er asserted during reception. Receive symbol errors are also counted as an FCS or alignment error if the frame is between 64 and 1518 bytes in length (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set). If the frame is larger, it is recorded as a jabber error. 29.7.28.16 Excessive Length Errors Register Register Name: ELE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 EXL 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • EXL: Excessive Length Errors An 8-bit register counting the number of frames received exceeding 1518 bytes (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set) in length but do not have either a CRC error, an alignment error nor a receive symbol error. 493 32058H–AVR32–03/09 AT32UC3A 29.7.28.17 Receive Jabbers Register Register Name: RJA Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 RJB 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • RJB: Receive Jabbers An 8-bit register counting the number of frames received exceeding 1518 bytes (1536 if bit 8, BIG, in network configuration register, NCFGR, is set, 10240 if bit 3, JFRAME in network configuration register, NCFGR, is set) in length and have either a CRC error, an alignment error or a receive symbol error. 29.7.28.18 Undersize Frames Register Register Name: USF Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 USF 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • USF: Undersize frames An 8-bit register counting the number of frames received less than 64 bytes in length but do not have either a CRC error, an alignment error or a receive symbol error. 494 32058H–AVR32–03/09 AT32UC3A 29.7.28.19 SQE Test Errors Register Register Name: STE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 SQER 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • SQER: SQE test errors An 8-bit register counting the number of frames where col was not asserted within 96 bit times (an interframe gap) of tx_en being deasserted in half duplex mode. 29.7.28.20 Received Length Field Mismatch Register Register Name: RLE Access Type: 31 – 23 – 15 – 7 Read/Write 30 – 22 – 14 – 6 29 – 21 – 13 – 5 28 – 20 – 12 – 4 RLFM 27 – 19 – 11 – 3 26 – 18 – 10 – 2 25 – 17 – 9 – 1 24 – 16 – 8 – 0 • RLFM: Receive Length Field Mismatch An 8-bit register counting the number of frames received that have a measured length shorter than that extracted from its length field. Checking is enabled through bit 16 of the network configuration register. Frames containing a type ID in bytes 13 and 14 (i.e., length/type ID 0x0600) are not counted as length field errors, neither are excessive length frames. 495 32058H–AVR32–03/09 AT32UC3A 29.7.28.21 Transmitted Pause Frames Register Register Name: TPF Access Type: 31 – 23 – 15 Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 TPF 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 7 6 5 4 TPF 3 2 1 0 • TPF: Transmitted Pause Frames A 16-bit register counting the number of pause frames transmitted. 496 32058H–AVR32–03/09 AT32UC3A 30. USB On-The-Go Interface (USBB) Rev: 3.1.1.1 30.1 Features • • • • • • • USB 2.0 Compliant, Full-/Low-Speed (FS/LS) and On-The-Go (OTG), 12 Mbit/s 7 Pipes/Endpoints 960 bytes of Embedded Dual-Port RAM (DPRAM) for Pipes/Endpoints Up to 2 Memory Banks per Pipe/Endpoint (Not for Control Pipe/Endpoint) Flexible Pipe/Endpoint Configuration and Management with Dedicated DMA Channels On-Chip Transceivers Including Pull-Ups/Pull-downs. On-Chip OTG pad including VBUS analog comparator 30.2 Description The Universal Serial Bus (USB) MCU device complies with the Universal Serial Bus (USB) 2.0 specification, but it does NOT feature high-speed USB (480 Mbit/s). Each pipe/endpoint can be configured in one of several transfer types. It can be associated with one or more banks of a dual-port RAM used to store the current data payload. If several banks are used (“ping-pong” mode), then one DPRAM bank is read or written by the CPU or the DMA while the other is read or written by the USB macro core. This feature is mandatory for isochronous pipes/endpoints. Table 30-1 describes the hardware configuration of the USB MCU device. Table 30-1. Description of USB Pipes/Endpoints Mnemonic PEP0 PEP1 PEP2 PEP3 PEP4 PEP5 PEP6 Max. Size 64 bytes bytes bytes 64 bytes 64 bytes bytes bytes Max. Nb. Banks 1 DMA N Y Y Y Y Y Y Type Control Isochronous/Bulk/Interrupt Isochronous/Bulk/Interrupt Bulk/Interrupt Bulk/Interrupt Isochronous/Bulk/Interrupt Isochronous/Bulk/Interrupt Pipe/Endpoint 0 1 2 3 4 5 6 The theoretical maximal pipe/endpoint configuration (1600 bytes) exceeds the real DPRAM size (960 bytes). The user needs to be aware of this when configuring pipes/endpoints. To fully use the 960 bytes of DPRAM, the user could for example use the configuration described in Table 30-2. Table 30-2. Example of Configuration of Pipes/Endpoints Using the Whole DPRAM Mnemonic PEP0 PEP1 PEP2 PEP3 Size 64 bytes 64 bytes 64 bytes 64 bytes Nb. Banks 1 2 2 1 Pipe/Endpoint 0 1 2 3 497 32058H–AVR32–03/09 AT32UC3A Table 30-2. Example of Configuration of Pipes/Endpoints Using the Whole DPRAM Mnemonic PEP4 PEP5 PEP6 Size 64 bytes 256 bytes 256 bytes Nb. Banks 1 1 1 Pipe/Endpoint 4 5 6 498 32058H–AVR32–03/09 AT32UC3A 30.3 Block Diagram The USB controller provides a hardware device to interface a USB link to a data flow stored in a dual-port RAM (DPRAM). The USB controller requires a 48 MHz ± 0.25% reference clock, which is the USB generic clock generated from one of the power manager oscillators, optionally through one of the power manager PLLs. The 48 MHz clock is used to generate a 12 MHz full-speed (or 1.5 MHz low-speed) bit clock from the received USB differential data and to transmit data according to full- or low-speed USB device tolerance. Clock recovery is achieved by a digital phase-locked loop (a DPLL, not represented), which complies with the USB jitter specifications. Figure 30-1. Block Diagram USB 32 bits DPRAM Local HSB Slave Interface Slave HSB MUX HSB Master HSB0 DMA HSB1 PEP Allocation VBUS DUSB 2.0 Core D+ USB_ID GPIO Controller PB User Interface Interrupt Controller USB Interrupts USB_VBOF Power Manager USB GCLK @ 48 MHz System Clock Domain USB Clock Domain 499 32058H–AVR32–03/09 AT32UC3A 30.4 Application Block Diagram Depending on the USB operating mode (device-only, reduced-host or OTG mode) and the power source (bus-powered or self-powered), there are different typical hardware implementations. 30.4.1 30.4.1.1 Device Mode Bus-Powered Device Figure 30-2. Bus-Powered Device Application Block Diagram VDD 3.3 V Regulator USB USB Connector VBUS DD+ ID GND USB_VBOF VBUS DD+ USB_ID 39 Ω ± 1% 39 Ω ± 1% 30.4.1.2 Self-Powered Device Figure 30-3. Self-Powered Device Application Block Diagram USB USB Connector VBUS DD+ ID GND USB_VBOF VBUS DD+ USB_ID 39 Ω ± 1% 39 Ω ± 1% 500 32058H–AVR32–03/09 AT32UC3A 30.4.2 Host and OTG Modes Figure 30-4. Host and OTG Application Block Diagram VDD 5 V DC/DC Generator USB USB Connector VBUS DD+ ID GND USB_VBOF VBUS DD+ USB_ID 39 Ω ± 1% 39 Ω ± 1% 30.5 I/O Lines Description I/O Lines Description Description USB VBus On/Off: Bus Power Control Port VBus: Bus Power Measurement Port Data -: Differential Data Line - Port Data +: Differential Data Line + Port USB Identification: Mini Connector Identification Port Type Output Input Input/Output Input/Output Input Active Level VBUSPO High N/A N/A Low: Mini-A plug High Z: Mini-B plug Table 30-3. Name USB_VBOF VBUS DD+ USB_ID 501 32058H–AVR32–03/09 AT32UC3A 30.6 30.6.1 Product Dependencies I/O Lines The USB_VBOF and USB_ID pins are multiplexed with GPIO lines and may also be multiplexed with lines of other peripherals. In order to use them with the USB, the programmer must first program the GPIO controller to assign them to their USB peripheral functions. Moreover, if USB_ID is used, the GPIO controller must be configured to enable the internal pull-up resistor of its pin. If USB_VBOF or USB_ID is not used by the application, the corresponding pin can be used for other purposes by the GPIO controller or by other peripherals. 30.6.2 Power Management The 48 MHz USB clock is generated by a dedicated generic clock from the power manager. Before using the USB, the programmer must ensure that the USB generic clock (USB GCLK) is enabled at 48 MHz in the power manager. 30.6.3 Interrupts The USB interface has an interrupt line connected to the interrupt controller. In order to handle USB interrupts, the interrupt controller must be programmed first. 502 32058H–AVR32–03/09 AT32UC3A 30.7 30.7.1 30.7.1.1 Functional Description USB General Operation Introduction After a hardware reset, the USB controller is disabled. When enabled, the USB controller runs either in device mode or in host mode according to the ID detection. If the USB_ID pin is not connected to ground, the ID bit is set by hardware (the internal pull-up resistor of the USB_ID pin must be enabled by the GPIO controller) and device mode is engaged. The ID bit is cleared by hardware when a low level has been detected on the USB_ID pin. Host mode is then engaged. 30.7.1.2 Power-On and Reset Figure 30-5 describes the USB controller main states. Figure 30-5. General States Macrooff: USBE = 0 Clock stopped: FRZCLK = 1 Reset USBE = 0 HW RESET USBE = 1 ID = 1 USBE = 0 USBE = 1 ID = 0 USBE = 0 Device Host After a hardware reset, the USB controller is in the Reset state. In this state: •the macro is disabled (USBE = 0); •the macro clock is stopped in order to minimize power consumption (FRZCLK = 1); •the pad is in suspend mode; •the internal states and registers of the device and host modes are reset; •the DPRAM is not cleared and is accessible; •the ID and VBUS read-only bits reflect the states of the USB_ID and VBUS input pins; •the OTGPADE, VBUSPO, FRZCLK, USBE, UIDE, UIMOD and LS bits can be written by software, so that the user can program pads and speed before enabling the macro, but their value is only taken into account once the macro is enabled and unfrozen. After setting USBE, the USB controller enters the Device or the Host mode (according to the ID detection) in idle state. The USB controller can be disabled at any time by clearing USBE. In fact, clearing USBE acts as a hardware reset, except that the OTGPADE, VBUSPO, FRZCLK, UIDE, UIMOD and LS bits are not reset. 503 32058H–AVR32–03/09 AT32UC3A 30.7.1.3 Interrupts One interrupt vector is assigned to the USB interface. Figure 30-6 shows the structure of the USB interrupt system. Figure 30-6. Interrupt System USBSTA.IDTI USBCON.IDTE USBSTA.VBUSTI USBCON.VBUSTE USBSTA.SRPI USBCON.SRPE USBSTA.VBERRI USBCON.VBERRE USBSTA.BCERRI USBCON.BCERRE USBSTA.ROLEEXI USBCON.ROLEEXE USBSTA.HNPERRI USBCON.HNPERRE USBSTA.STOI USBCON.STOE USB General Interrupt UESTAX.TXINI UECONX.TXINE UESTAX.RXOUTI UECONX.RXOUTE UESTAX.RXSTPI UECONX.RXSTPE UESTAX.UNDERFI UECONX.UNDERFE UESTAX.NAKOUTI UECONX.NAKOUTE UESTAX.NAKINI UECONX.NAKINE UESTAX.OVERFI UECONX.OVERFE UESTAX.STALLEDI UECONX.STALLEDE UESTAX.CRCERRI UECONX.CRCERRE UESTAX.SHORTPACKET UECONX.SHORTPACKETE UESTAX.NBUSYBK UECONX.NBUSYBKE UDDMAX_STATUS.EOT_STA UDDMAX_CONTROL.EOT_IRQ_EN UDDMAX_STATUS.EOCH_BUFF_STA UDDMAX_CONTROL.EOBUFF_IRQ_EN UDDMAX_STATUS.DESC_LD_STA UDDMAX_CONTROL.DESC_LD_IRQ_EN UPSTAX.RXINI UPCONX.RXINE UPSTAX.TXOUTI UPCONX.TXOUTE UPSTAX.TXSTPI UPCONX.TXSTPE UPSTAX.UNDERFI UPCONX.UNDERFIE UPSTAX.PERRI UPCONX.PERRE UPSTAX.NAKEDI UPCONX.NAKEDE UPSTAX.OVERFI UPCONX.OVERFIE UPSTAX.RXSTALLDI UPCONX.RXSTALLDE UPSTAX.CRCERRI UPCONX.CRCERRE UPSTAX.SHORTPACKETI UPCONX.SHORTPACKETIE UPSTAX.NBUSYBK UPCONX.NBUSYBKE UHDMAX_STATUS.EOT_STA UHDMAX_CONTROL.EOT_IRQ_EN UHDMAX_STATUS.EOCH_BUFF_STA UHDMAX_CONTROL.EOBUFF_IRQ_EN UHDMAX_STATUS.DESC_LD_STA UHDMAX_CONTROL.DESC_LD_IRQ_EN USB Host DMA Channel X Interrupt UHINT.DMAXINT UHINTE.DMAXINTE UHINT.HWUPI UHINTE.HWUPIE UHINT.PXINT UHINTE.PXINTE USB Host Pipe X Interrupt UHINT.RSMEDI UHINTE.RSMEDIE UHINT.RXRSMI UHINTE.RXRSMIE UHINT.HSOFI UHINTE.HSOFIE USB Host Interrupt UHINT.RSTI UHINTE.RSTIE UHINT.DDISCI UHINTE.DDISCIE UHINT.DCONNI UHINTE.DCONNIE USB Device DMA Channel X Interrupt UDINT.DMAXINT UDINTE.DMAXINTE UDINT.UPRSM UDINTE.UPRSME UDINT.EPXINT UDINTE.EPXINTE USB Device Endpoint X Interrupt UDINT.EORST UDINTE.EORSTE UDINT.WAKEUP UDINTE.WAKEUPE UDINT.EORSM UDINTE.EORSME USB Device Interrupt USB Interrupt UDINT.SOF UDINTE.SOFE UDINT.SUSP UDINTE.SUSPE Asynchronous interrupt source 504 32058H–AVR32–03/09 AT32UC3A See Section 30.7.2.17 on page 520 and Section 30.7.3.13 on page 528 for further details about device and host interrupts. There are two kinds of general interrupts: processing, i.e. their generation is part of the normal processing, and exception, i.e. errors (not related to CPU exceptions). The processing general interrupts are: •the ID Transition interrupt (IDTI); •the VBus Transition interrupt (VBUSTI); •the SRP interrupt (SRPI); •the Role Exchange interrupt (ROLEEXI). The exception general interrupts are: •the VBus Error interrupt (VBERRI); •the B-Connection Error interrupt (BCERRI); •the HNP Error interrupt (HNPERRI); •the Suspend Time-Out interrupt (STOI). 30.7.1.4 30.7.1.4.1 MCU Power Modes Run Mode In this mode, all MCU clocks can run, including the USB clock. 30.7.1.4.2 Idle Mode In this mode, the CPU is halted, i.e. the CPU clock is stopped. The Idle mode is entered whatever the state of the USB macro. The MCU wakes up on any USB interrupt. 30.7.1.4.3 Frozen Mode Same as the Idle mode, except that the HSB module is stopped, so the USB DMA, which is an HSB master, can not be used. Moreover, the USB DMA must be stopped before entering this sleep mode in order to avoid erratic behavior. The MCU wakes up on any USB interrupt. 30.7.1.4.4 Standby, Stop, DeepStop and Static Modes Same as the Frozen mode, except that the USB generic clock and other clocks are stopped, so the USB macro is frozen. 30.7.1.4.5 USB Clock Frozen In the Run, Idle and Frozen MCU modes, the USB macro can be frozen when the usb line is in the suspend mode, by setting the FRZCLK bit, what reduces power consumption. In this case, it is still possible to access the following elements, but only in Run mode: •the OTGPADE, VBUSPO, FRZCLK, USBE, UIDE, UIMOD and LS bits; •the DPRAM (through the USB_FIFOX_DATA registers, but not through USB bus transfers which are frozen). Moreover, when FRZCLK is set, only the asynchronous interrupt sources may trigger the USB interrupt: •the ID Transition interrupt (IDTI); 505 32058H–AVR32–03/09 AT32UC3A •the VBus Transition interrupt (VBUSTI); •the Wake-Up interrupt (WAKEUP); •the Host Wake-Up interrupt (HWUPI). 30.7.1.4.6 USB Suspend mode : In peripheral mode, the UDINT.SUSP bit indicates that the usb line is in the suspend mode. In this case, the USB Data transceiver is automatically set in suspend mode to reduce the consumption. 30.7.1.5 30.7.1.5.1 Speed Control Device Mode When the USB interface is in device mode, the speed selection (full-/low-speed) depends on which of D+ and D- is pulled up. The LS bit allows to connect an internal pull-up resistor either on D+ (full-speed mode) or on D- (low-speed mode). The LS bit should be configured before attaching the device, what can be done by clearing the DETACH bit. Figure 30-7. Speed Selection in Device Mode VBUS RPU UDCON.DETACH UDCON.LS D+ D- 30.7.1.5.2 Host Mode When the USB interface is in host mode, internal pull-down resistors are connected on both D+ and D- and the interface detects the speed of the connected device, which is reflected by the SPEED bit-field. 30.7.1.6 DPRAM Management Pipes and endpoints can only be allocated in ascending order (from the pipe/endpoint 0 to the last pipe/endpoint to be allocated). The firmware shall therefore configure them in the same order. The allocation of a pipe/endpoint ki starts when its ALLOC bit is set. Then, the hardware allocates a memory area in the DPRAM and inserts it between the ki-1 and ki+1 pipes/endpoints. The ki+1 pipe/endpoint memory window slides up and its data is lost. Note that the following pipe/endpoint memory windows (from ki+2) do not slide. 506 32058H–AVR32–03/09 AT32UC3A Disabling a pipe (PENX = 0) or an endpoint (EPENX = 0) resets neither its ALLOC bit nor its configuration (PBK/EPBK, PSIZE/EPSIZE, PTOKEN/EPDIR, PTYPE/EPTYPE, PEPNUM, INTFRQ). To free its memory, the firmware should clear its ALLOC bit. The ki+1 pipe/endpoint memory window then slides down and its data is lost. Note that the following pipe/endpoint memory windows (from ki+2) do not slide. Figure 30-8 illustrates the allocation and reorganization of the DPRAM in a typical example. Figure 30-8. Allocation and Reorganization of the DPRAM Free Memory Free Memory Free Memory Free Memory PEP5 PEP5 PEP5 PEP5 PEP4 Conflict PEP4 PEP3 PEP4 PEP3 (ALLOC stays at 1) PEP2 PEP4 Lost Memory PEP4 PEP3 (larger size) PEP2 PEP2 PEP2 PEP1 PEP1 PEP1 PEP1 PEP0 PEP0 PEP0 PEP0 U(P/E)RST.(E)PENX = 1 U(P/E)CFGX.ALLOC = 1 U(P/E)RST.(E)PEN3 = 0 U(P/E)CFG3.ALLOC = 0 U(P/E)RST.(E)PEN3 = 1 U(P/E)CFG3.ALLOC = 1 Pipes/Endpoints 0..5 Activated Pipe/Endpoint 3 Disabled Pipe/Endpoint 3 Memory Freed Pipe/Endpoint 3 Activated • First, the pipes/endpoints 0 to 5 are enabled, configured and allocated in ascending order. Each pipe/endpoint then owns a memory area in the DPRAM. • Then, the pipe/endpoint 3 is disabled, but its memory is kept allocated by the controller. • In order to free its memory, its ALLOC bit is then cleared by the firmware. The pipe/endpoint 4 memory window slides down, but the pipe/endpoint 5 does not move. • Finally, if the firmware chooses to reconfigure the pipe/endpoint 3 with a larger size, the controller allocates a memory area after the pipe/endpoint 2 memory area and automatically slides up the pipe/endpoint 4 memory window. The pipe/endpoint 5 does not move and a memory conflict appears as the memory windows of the pipes/endpoints 4 and 5 overlap. The data of these pipes/endpoints is potentially lost. Note that: •there is no way the data of the pipe/endpoint 0 can be lost (except if it is de-allocated) as memory allocation and de-allocation may affect only higher pipes/endpoints; •deactivating then reactivating a same pipe/endpoint with the same configuration only modifies temporarily the controller DPRAM pointer and size for this pipe/endpoint, but nothing changes in the DPRAM, so higher endpoints seem to not have been moved and their data is preserved as far as nothing has been written or received into them while changing the allocation state of the first pipe/endpoint; •when the firmware sets the ALLOC bit, the CFGOK bit is set by hardware only if the configured size and number of banks are correct compared to their maximal allowed values for the endpoint and to the maximal FIFO size (i.e. the DPRAM size), so the value of CFGOK does not consider memory allocation conflicts. 507 32058H–AVR32–03/09 AT32UC3A 30.7.1.7 Pad Suspend Figure 30-9 shows the pad behavior. Figure 30-9. Pad Behavior Idle USBE = 1 & DETACH = 0 & Suspend USBE = 0 | DETACH = 1 | Suspend Active • In the Idle state, the pad is put in low power consumption mode. • In the Active state, the pad is working. Figure 30-10 illustrates the pad events leading to a PAD state change. Figure 30-10. Pad Events SUSP Suspend detected Cleared by hardware on wake-up WAKEUP Wake-up detected Cleared by software to acknowledge the interrupt PAD State Active Idle Active The Suspend interrupt flag (SUSP) is set and the Wake-Up interrupt flag (WAKEUP) is cleared when a USB “Suspend” state has been detected on the USB bus. This event automatically puts the USB pad in the Idle state. The detection of a non-idle event sets WAKEUP, clears SUSP and wakes up the USB pad. Moreover, the pad goes to the Idle state if the macro is disabled or if the DETACH bit is set. It returns to the Active state when USBE = 1 and DETACH = 0. 508 32058H–AVR32–03/09 AT32UC3A 30.7.1.8 Customizing of OTG Timers It is possible to refine some OTG timers thanks to the TIMPAGE and TIMVALUE bit-fields, as shown by Figure 30-4. Table 30-4. Customizing of OTG Timers TIMPAGE 00b: AWaitVrise Time-Out ([OTG] Chapter 6.6.5.1) TIMVALUE 00b 01b 10b 11b 20 ms 50 ms 70 ms 100 ms 01b: VbBusPulsing Time-Out ([OTG] Chapter 5.3.4) 15 ms 23 ms 31 ms 40 ms 10b: PdTmOutCnt Time-Out ([OTG] Chapter 5.3.2) 93 ms 105 ms 118 ms 131 ms 11b: SRPDetTmOut Time-Out ([OTG] Chapter 5.3.3) 10 µs 100 µs 1 ms 11 ms TIMPAGE is used to select the OTG timer to access while TIMVALUE indicates the time-out value of the selected timer. TIMPAGE and TIMVALUE can be read or written. Before writing them, the firmware should unlock write accesses by setting the UNLOCK bit. This is not required for read accesses, except before accessing TIMPAGE if it has to be written in order to read the TIMVALUE bit-field of another OTG timer. 30.7.1.9 Plug-In Detection The USB connection is detected from the VBUS pad. Figure 30-11 shows the architecture of the plug-in detector. Figure 30-11. Plug-In Detection Input Block Diagram VDD VBus_pulsing RPU Session_valid Logic VBUS RPD Va_Vbus_valid VBUS USBSTA VBUSTI USBSTA VBus_discharge GND Pad Logic The control logic of the VBUS pad outputs two signals: •the Session_valid signal is high when the voltage on the VBUS pad is higher than or equal to 1.4 V; •the Va_Vbus_valid signal is high when the voltage on the VBUS pad is higher than or equal to 4.4 V. In device mode, the VBUS bit follows the Session_valid comparator output: •it is set when the voltage on the VBUS pad is higher than or equal to 1.4 V; 509 32058H–AVR32–03/09 AT32UC3A •it is cleared when the voltage on the VBUS pad is lower than 1.4 V. In host mode, the VBUS bit follows an hysteresis based on Session_valid and Va_Vbus_valid: •it is set when the voltage on the VBUS pad is higher than or equal to 4.4 V; •it is cleared when the voltage on the VBUS pad is lower than 1.4 V. The VBus Transition interrupt (VBUSTI) is raised on each transition of the VBUS bit. The VBUS bit is effective whether the USB macro is enabled or not. 30.7.1.10 ID Detection Figure 30-12 shows how the ID transitions are detected. Figure 30-12. ID Detection Input Block Diagram VDD RPU 1 USB_ID 0 ID USBSTA IDTI USBSTA UIMOD USBCON UIDE USBCON GPIO Controller The USB mode (device or host) can be either detected from the USB_ID pin or software selected from the UIMOD bit, according to the UIDE bit. This allows the USB_ID pin to be used as a general purpose I/O pin even when the USB interface is enabled. By default, the USB_ID pin is selected (UIDE = 1) and the USB macro is in device mode (ID = 1), what corresponds to the case where no Mini-A plug is connected, i.e. no plug or a Mini-B plug is connected and the USB_ID pin is kept high by the internal pull-up resistor from the GPIO controller (which must be enabled if USB_ID is used). The ID Transition interrupt (IDTI) is raised on each transition of the ID bit, i.e. when a Mini-A plug (host mode) is connected or disconnected. This does not occur when a Mini-B plug (device mode) is connected or disconnected. The ID bit is effective whether the USB macro is enabled or not. 510 32058H–AVR32–03/09 AT32UC3A 30.7.2 30.7.2.1 USB Device Operation Introduction In device mode, the USB controller supports full- and low-speed data transfers. In addition to the default control endpoint, six endpoints are provided, which can be configured with the types isochronous, bulk or interrupt, as described in Table 30-1 on page 497. The device mode starts in the Idle state, so the pad consumption is reduced to the minimum. 30.7.2.2 Power-On and Reset Figure 30-13 describes the USB controller device mode main states. Figure 30-13. Device Mode States USBE = 0 | ID = 0 USBE = 0 | ID = 0 Reset HW RESET USBE = 1 & ID = 1 Idle After a hardware reset, the USB controller device mode is in the Reset state. In this state: •the macro clock is stopped in order to minimize power consumption (FRZCLK = 1); •the internal registers of the device mode are reset; •the endpoint banks are de-allocated; •neither D+ nor D- is pulled up (DETACH = 1). D+ or D- will be pulled up according to the selected speed as soon as the DETACH bit is cleared and VBus is present. See Section 30.7.1.5.1 on page 506 for further details. When the USB macro is enabled (USBE = 1) in device mode (ID = 1), its device mode state goes to the Idle state with minimal power consumption. This does not require the USB clock to be activated. The USB controller device mode can be disabled and reset at any time by disabling the USB macro (USBE = 0) or when host mode is engaged (ID = 0). 30.7.2.3 USB Reset The USB bus reset is managed by hardware. It is initiated by a connected host. When a USB reset is detected on the USB line, the following operations are performed by the controller: •all the endpoints are disabled, except the default control endpoint; •the default control endpoint is reset (see Section 30.7.2.4 on page 512 for more details); •the data toggle sequence of the default control endpoint is cleared; •at the end of the reset process, the End of Reset interrupt (EORST) is raised. 511 32058H–AVR32–03/09 AT32UC3A 30.7.2.4 Endpoint Reset An endpoint can be reset at any time by setting its EPRSTX bit in the UERST register. This is recommended before using an endpoint upon hardware reset or when a USB bus reset has been received. This resets: •the internal state machine of this endpoint; •the receive and transmit bank FIFO counters; •all the registers of this endpoint (UECFGX, UESTAX, UECONX), except its configuration (ALLOC, EPBK, EPSIZE, EPDIR, EPTYPE) and its Data Toggle Sequence bit-field (DTSEQ). Note that the interrupt sources located in the UESTAX register are not cleared when a USB bus reset has been received. The endpoint configuration remains active and the endpoint is still enabled. The endpoint reset may be associated with a clear of the data toggle sequence as an answer to the CLEAR_FEATURE USB request. This can be achieved by setting the RSTDT bit (by setting the RSTDTS bit). In the end, the firmware has to clear the EPRSTX bit to complete the reset operation and to start using the FIFO. 30.7.2.5 Endpoint Activation The endpoint is maintained inactive and reset (see Section 30.7.2.4 on page 512 for more details) as long as it is disabled (EPENX = 0). The Data Toggle Sequence bit-field (DTSEQ) is also reset. The algorithm represented on Figure 30-14 must be followed in order to activate an endpoint. Figure 30-14. Endpoint Activation Algorithm Endpoint Activation EPENX = 1 Enable the endpoint. UECFGX EPTYPE EPDIR EPSIZE EPBK ALLOC Configure the endpoint: - type; - direction; - size; - number of banks. Allocate the configured DPRAM banks. CFGOK == 1? Yes Endpoint Activated No Test if the endpoint configuration is correct. ERROR As long as the endpoint is not correctly configured (CFGOK = 0), the controller does not acknowledge the packets sent by the host to this endpoint. The CFGOK bit is set by hardware only if the configured size and number of banks are correct compared to their maximal allowed values for the endpoint (see Table 30-1 on page 497) and to the maximal FIFO size (i.e. the DPRAM size). 512 32058H–AVR32–03/09 AT32UC3A See Section 30.7.1.6 on page 506 for more details about DPRAM management. 30.7.2.6 Address Setup The USB device address is set up according to the USB protocol: •after all kinds of resets, the USB device address is 0; •the host starts a SETUP transaction with a SET_ADDRESS(addr) request; •the firmware records this address into the UADD bit-field, leaving the ADDEN bit cleared, so the actual address is still 0; •the firmware sends a zero-length IN packet from the control endpoint; •the firmware enables the recorded USB device address by setting ADDEN. Once the USB device address is configured, the controller filters the packets to only accept those targeting the address stored in UADD. UADD and ADDEN shall not be written all at once. UADD and ADDEN are cleared by hardware: •on a hardware reset; •when the USB macro is disabled (USBE = 0); •when a USB reset is detected. When UADD or ADDEN is cleared, the default device address 0 is used. 30.7.2.7 Suspend and Wake-Up When an idle USB bus state has been detected for 3 ms, the controller raises the Suspend interrupt (SUSP). The firmware may then set the FRZCLK bit to reduce power consumption. The MCU can also enter the Idle or Frozen sleep mode to lower again power consumption. To recover from the Suspend mode, the firmware should wait for the Wake-Up interrupt (WAKEUP), which is raised when a non-idle event is detected, then clear FRZCLK. As the WAKEUP interrupt is raised when a non-idle event is detected, it can occur whether the controller is in the Suspend mode or not. The SUSP and WAKEUP interrupts are thus independent of each other except that one’s flag is cleared by hardware when the other is raised. 30.7.2.8 Detach The reset value of the DETACH bit is 1. It is possible to initiate a device re-enumeration simply by setting then clearing DETACH. DETACH acts on the pull-up connections of the D+ and D- pads. See Section 30.7.1.5.1 on page 506 for further details. 30.7.2.9 Remote Wake-Up The Remote Wake-Up request (also known as Upstream Resume) is the only one the device may send on its own initiative, but the device should have beforehand been allowed to by a DEVICE_REMOTE_WAKEUP request from the host. • First, the USB controller must have detected a “Suspend” state on the bus, i.e. the Remote Wake-Up request can only be sent after a SUSP interrupt has been raised. 513 32058H–AVR32–03/09 AT32UC3A • The firmware may then set the RMWKUP bit to send an upstream resume to the host for a remote wake-up. This will automatically be done by the controller after 5 ms of inactivity on the USB bus. • When the controller sends the upstream resume, the Upstream Resume interrupt (UPRSM) is raised and SUSP is cleared by hardware. • RMWKUP is cleared by hardware at the end of the upstream resume. • If the controller detects a valid “End of Resume” signal from the host, the End of Resume interrupt (EORSM) is raised. 30.7.2.10 STALL Request For each endpoint, the STALL management is performed using: •the STALL Request bit (STALLRQ) to initiate a STALL request; •the STALLed interrupt (STALLEDI) raised when a STALL handshake has been sent. To answer the next request with a STALL handshake, STALLRQ has to be set by setting the STALLRQS bit. All following requests will be discarded (RXOUTI, etc. will not be set) and handshaked with a STALL until the STALLRQ bit is cleared, what is done by hardware when a new SETUP packet is received (for control endpoints) or when the STALLRQC bit is set. Each time a STALL handshake is sent, the STALLEDI flag is set by the USB controller and the EPXINT interrupt is raised. 30.7.2.10.1 Special Considerations for Control Endpoints If a SETUP packet is received into a control endpoint for which a STALL is requested, the Received SETUP interrupt (RXSTPI) is raised and STALLRQ and STALLEDI are cleared by hardware. The SETUP has to be ACKed. This management simplifies the enumeration process management. If a command is not supported or contains an error, the firmware requests a STALL and can return to the main task, waiting for the next SETUP request. 30.7.2.10.2 STALL Handshake and Retry Mechanism The retry mechanism has priority over the STALL handshake. A STALL handshake is sent if the STALLRQ bit is set and if there is no retry required. 30.7.2.11 Management of Control Endpoints 30.7.2.11.1 Overview A SETUP request is always ACKed. When a new SETUP packet is received, the Received SETUP interrupt (RXSTPI) is raised, but not the Received OUT Data interrupt (RXOUTI). The FIFOCON and RWALL bits are irrelevant for control endpoints. The firmware shall therefore never use them on these endpoints. When read, their value is always 0. Control endpoints are managed using: •the Received SETUP interrupt (RXSTPI) which is raised when a new SETUP packet is received and which shall be cleared by firmware to acknowledge the packet and to free the bank; 514 32058H–AVR32–03/09 AT32UC3A •the Received OUT Data interrupt (RXOUTI) which is raised when a new OUT packet is received and which shall be cleared by firmware to acknowledge the packet and to free the bank; •the Transmitted IN Data interrupt (TXINI) which is raised when the current bank is ready to accept a new IN packet and which shall be cleared by firmware to send the packet. 30.7.2.11.2 Control Write Figure 30-15 shows a control write transaction. During the status stage, the controller will not necessarily send a NAK on the first IN token: •if the firmware knows the exact number of descriptor bytes that must be read, it can then anticipate the status stage and send a zero-length packet after the next IN token; •or it can read the bytes and wait for the NAKed IN interrupt (NAKINI) which tells that all the bytes have been sent by the host and that the transaction is now in the status stage. Figure 30-15. Control Write SETUP USB Bus RXSTPI RXOUTI TXINI SETUP HW SW DATA OUT OUT IN NAK STATUS IN HW SW HW SW SW 30.7.2.11.3 Control Read Figure 30-16 shows a control read transaction. The USB controller has to manage the simultaneous write requests from the CPU and the USB host. Figure 30-16. Control Read SETUP USB Bus RXSTPI RXOUTI TXINI Wr Enable HOST Wr Enable CPU SW HW DATA IN SW STATUS IN OUT NAK OUT SETUP HW HW SW SW A NAK handshake is always generated on the first status stage command. When the controller detects the status stage, all the data written by the CPU is lost and clearing TXINI has no effect. The firmware checks if the transmission or the reception is complete. 515 32058H–AVR32–03/09 AT32UC3A The OUT retry is always ACKed. This reception sets RXOUTI and TXINI. Handle this with the following software algorithm: set TXINI wait for RXOUTI OR TXINI if RXOUTI, then clear flag and return if TXINI, then continue Once the OUT status stage has been received, the USB controller waits for a SETUP request. The SETUP request has priority over any other request and has to be ACKed. This means that any other flag should be cleared and the FIFO reset when a SETUP is received. The firmware has to take care of the fact that the byte counter is reset when a zero-length OUT packet is received. 30.7.2.12 Management of IN Endpoints 30.7.2.12.1 Overview IN packets are sent by the USB device controller upon IN requests from the host. All the data can be written by the firmware which acknowledges or not the bank when it is full. The endpoint must be configured first. The TXINI bit is set by hardware at the same time as FIFOCON when the current bank is free. This triggers an EPXINT interrupt if TXINE = 1. TXINI shall be cleared by software (by setting the TXINIC bit) to acknowledge the interrupt, what has no effect on the endpoint FIFO. The firmware then writes into the FIFO and clears the FIFOCON bit to allow the USB controller to send the data. If the IN endpoint is composed of multiple banks, this also switches to the next bank. The TXINI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. TXINI shall always be cleared before clearing FIFOCON. The RWALL bit is set by hardware when the current bank is not full, i.e. the software can write further data into the FIFO. Figure 30-17. Example of an IN Endpoint with 1 Data Bank NAK IN DATA (bank 0) ACK IN HW TXINI SW SW FIFOCON write data to CPU BANK 0 SW write data to CPU BANK 0 SW 516 32058H–AVR32–03/09 AT32UC3A Figure 30-18. Example of an IN Endpoint with 2 Data Banks IN DATA (bank 0) ACK IN DATA (bank 1) ACK HW TXINI SW SW SW FIFOCON write data to CPU BANK 0 SW write data to CPU BANK 1 SW write data to CPU BANK0 30.7.2.12.2 Detailed Description The data is written by the firmware, following the next flow: •when the bank is empty, TXINI and FIFOCON are set, what triggers an EPXINT interrupt if TXINE = 1; •the firmware acknowledges the interrupt by clearing TXINI; •the firmware writes the data into the current bank by using the USB Pipe/Endpoint X FIFO Data register (USB_FIFOX_DATA), until all the data frame is written or the bank is full (in which case RWALL is cleared by hardware and BYCT reaches the endpoint size); •the firmware allows the controller to send the bank and switches to the next bank (if any) by clearing FIFOCON. If the endpoint uses several banks, the current one can be written by the firmware while the previous one is being read by the host. Then, when the firmware clears FIFOCON, the following bank may already be free and TXINI is set immediately. An “Abort” stage can be produced when a zero-length OUT packet is received during an IN stage of a control or isochronous IN transaction. The KILLBK bit is used to kill the last written bank. The best way to manage this abort is to apply the algorithm represented on Figure 30-19. 517 32058H–AVR32–03/09 AT32UC3A Figure 30-19. Abort Algorithm Endpoint Abort Disable the TXINI interrupt. TXINEC = 1 NBUSYBK == 0? Yes EPRSTX = 1 No Abort is based on the fact that no bank is busy, i.e. that nothing has to be sent. KILLBKS = 1 Kill the last written bank. Yes KILLBK == 1? No Wait for the end of the procedure. Abort Done 30.7.2.13 Management of OUT Endpoints 30.7.2.13.1 Overview OUT packets are sent by the host. All the data can be read by the firmware which acknowledges or not the bank when it is empty. The endpoint must be configured first. The RXOUTI bit is set by hardware at the same time as FIFOCON when the current bank is full. This triggers an EPXINT interrupt if RXOUTE = 1. RXOUTI shall be cleared by software (by setting the RXOUTIC bit) to acknowledge the interrupt, what has no effect on the endpoint FIFO. The firmware then reads from the FIFO and clears the FIFOCON bit to free the bank. If the OUT endpoint is composed of multiple banks, this also switches to the next bank. The RXOUTI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. RXOUTI shall always be cleared before clearing FIFOCON. The RWALL bit is set by hardware when the current bank is not empty, i.e. the software can read further data from the FIFO. 518 32058H–AVR32–03/09 AT32UC3A Figure 30-20. Example of an OUT Endpoint with 1 Data Bank OUT DATA (bank 0) ACK NAK OUT DATA (bank 0) ACK HW RXOUTI SW HW SW FIFOCON read data from CPU BANK 0 SW read data from CPU BANK 0 Figure 30-21. Example of an OUT Endpoint with 2 Data Banks OUT DATA (bank 0) ACK OUT DATA (bank 1) ACK HW RXOUTI SW HW SW FIFOCON read data from CPU BANK 0 SW read data from CPU BANK 1 30.7.2.13.2 Detailed Description The data is read by the firmware, following the next flow: •when the bank is full, RXOUTI and FIFOCON are set, what triggers an EPXINT interrupt if RXOUTE = 1; •the firmware acknowledges the interrupt by clearing RXOUTI; •the firmware can read the byte count of the current bank from BYCT to know how many bytes to read, rather than polling RWALL; •the firmware reads the data from the current bank by using the USB Pipe/Endpoint X FIFO Data register (USB_FIFOX_DATA), until all the expected data frame is read or the bank is empty (in which case RWALL is cleared by hardware and BYCT reaches 0); •the firmware frees the bank and switches to the next bank (if any) by clearing FIFOCON. If the endpoint uses several banks, the current one can be read by the firmware while the following one is being written by the host. Then, when the firmware clears FIFOCON, the following bank may already be ready and RXOUTI is set immediately. 30.7.2.14 Underflow This error exists only for isochronous IN/OUT endpoints. It raises the Underflow interrupt (UNDERFI), what triggers an EPXINT interrupt if UNDERFE = 1. An underflow can occur during IN stage if the host attempts to read from an empty bank. A zerolength packet is then automatically sent by the USB controller. 519 32058H–AVR32–03/09 AT32UC3A An underflow can not occur during OUT stage on a CPU action, since the firmware may read only if the bank is not empty (RXOUTI = 1 or RWALL = 1). An underflow can also occur during OUT stage if the host sends a packet while the bank is already full. Typically, the CPU is not fast enough. The packet is lost. An underflow can not occur during IN stage on a CPU action, since the firmware may write only if the bank is not full (TXINI = 1 or RWALL = 1). 30.7.2.15 Overflow This error exists for all endpoint types. It raises the Overflow interrupt (OVERFI), what triggers an EPXINT interrupt if OVERFE = 1. An overflow can occur during OUT stage if the host attempts to write into a bank that is too small for the packet. The packet is acknowledged and the Received OUT Data interrupt (RXOUTI) is raised as if no overflow had occurred. The bank is filled with all the first bytes of the packet that fit in. An overflow can not occur during IN stage on a CPU action, since the firmware may write only if the bank is not full (TXINI = 1 or RWALL = 1). 30.7.2.16 CRC Error This error exists only for isochronous OUT endpoints. It raises the CRC Error interrupt (CRCERRI), what triggers an EPXINT interrupt if CRCERRE = 1. A CRC error can occur during OUT stage if the USB controller detects a corrupted received packet. The OUT packet is stored in the bank as if no CRC error had occurred (RXOUTI is raised). 30.7.2.17 Interrupts See the structure of the USB device interrupt system on Figure 30-6 on page 504. There are two kinds of device interrupts: processing, i.e. their generation is part of the normal processing, and exception, i.e. errors (not related to CPU exceptions). 30.7.2.17.1 Global Interrupts The processing device global interrupts are: •the Suspend interrupt (SUSP); •the Start of Frame interrupt (SOF) with no frame number CRC error (FNCERR = 0); •the End of Reset interrupt (EORST); •the Wake-Up interrupt (WAKEUP); •the End of Resume interrupt (EORSM); •the Upstream Resume interrupt (UPRSM); •the Endpoint X interrupt (EPXINT); •the DMA Channel X interrupt (DMAXINT). The exception device global interrupts are: •the Start of Frame interrupt (SOF) with a frame number CRC error (FNCERR = 1). 520 32058H–AVR32–03/09 AT32UC3A 30.7.2.17.2 Endpoint Interrupts The processing device endpoint interrupts are: •the Transmitted IN Data interrupt (TXINI); •the Received OUT Data interrupt (RXOUTI); •the Received SETUP interrupt (RXSTPI); •the Short Packet interrupt (SHORTPACKET); •the Number of Busy Banks interrupt (NBUSYBK). The exception device endpoint interrupts are: •the Underflow interrupt (UNDERFI); •the NAKed OUT interrupt (NAKOUTI); •the NAKed IN interrupt (NAKINI); •the Overflow interrupt (OVERFI); •the STALLed interrupt (STALLEDI); •the CRC Error interrupt (CRCERRI); 30.7.2.17.3 DMA Interrupts The processing device DMA interrupts are: •the End of USB Transfer Status interrupt (EOT_STA); •the End of Channel Buffer Status interrupt (EOCH_BUFF_STA); •the Descriptor Loaded Status interrupt (DESC_LD_STA). There is no exception device DMA interrupt. 521 32058H–AVR32–03/09 AT32UC3A 30.7.3 30.7.3.1 USB Host Operation Description of Pipes For the USB controller in host mode, the term “pipe” is used instead of “endpoint” (used in device mode). A host pipe corresponds to a device endpoint, as described by the Figure 30-22 from the USB specification. Figure 30-22. USB Communication Flow In host mode, the USB controller associates a pipe to a device endpoint, considering the device configuration descriptors. 30.7.3.2 Power-On and Reset Figure 30-23 describes the USB controller host mode main states. Figure 30-23. Host Mode States Macrooff Clock stopped Idle Device Disconnection Device Connection Device Disconnection Ready SOFE = 0 SOFE = 1 Suspend After a hardware reset, the USB controller host mode is in the Reset state. When the USB macro is enabled (USBE = 1) in host mode (ID = 0), its host mode state goes to the Idle state. In this state, the controller waits for device connection with minimal power consumption. The USB pad should be in the Idle state. Once a device is connected, the macro enters the Ready state, what does not require the USB clock to be activated. 522 32058H–AVR32–03/09 AT32UC3A The controller enters the Suspend state when the USB bus is in a “Suspend” state, i.e. when the host mode does not generate the “Start of Frame”. In this state, the USB consumption is minimal. The host mode exits the Suspend state when starting to generate the SOF over the USB line. 30.7.3.3 Device Detection A device is detected by the USB controller host mode when D+ or D- is no longer tied low, i.e. when the device D+ or D- pull-up resistor is connected. To enable this detection, the host controller has to provide the VBus power supply to the device by setting the VBUSRQ bit (by setting the VBUSRQS bit). The device disconnection is detected by the host controller when both D+ and D- are pulled down. 30.7.3.4 USB Reset The USB controller sends a USB bus reset when the firmware sets the RESET bit. The USB Reset Sent interrupt (RSTI) is raised when the USB reset has been sent. In this case, all the pipes are disabled and de-allocated. If the bus was previously in a “Suspend” state (SOFE = 0), the USB controller automatically switches it to the “Resume” state, the Host Wake-Up interrupt (HWUPI) is raised and the SOFE bit is set by hardware in order to generate SOFs immediately after the USB reset. 30.7.3.5 Pipe Reset A pipe can be reset at any time by setting its PRSTX bit in the UPRST register. This is recommended before using a pipe upon hardware reset or when a USB bus reset has been sent. This resets: •the internal state machine of this pipe; •the receive and transmit bank FIFO counters; •all the registers of this pipe (UPCFGX, UPSTAX, UPCONX), except its configuration (ALLOC, PBK, PSIZE, PTOKEN, PTYPE, PEPNUM, INTFRQ) and its Data Toggle Sequence bit-field (DTSEQ). The pipe configuration remains active and the pipe is still enabled. The pipe reset may be associated with a clear of the data toggle sequence. This can be achieved by setting the RSTDT bit (by setting the RSTDTS bit). In the end, the firmware has to clear the PRSTX bit to complete the reset operation and to start using the FIFO. 30.7.3.6 Pipe Activation The pipe is maintained inactive and reset (see Section 30.7.3.5 on page 523 for more details) as long as it is disabled (PENX = 0). The Data Toggle Sequence bit-field (DTSEQ) is also reset. The algorithm represented on Figure 30-24 must be followed in order to activate a pipe. 523 32058H–AVR32–03/09 AT32UC3A Figure 30-24. Pipe Activation Algorithm Pipe Activation PENX = 1 Enable the pipe. UPCFGX INTFRQ PEPNUM PTYPE PTOKEN PSIZE PBK ALLOC Configure the pipe: - interrupt request frequency; - endpoint number; - type; - token; - size; - number of banks. Allocate the configured DPRAM banks. CFGOK == 1? Yes Pipe Activated No Test if the pipe configuration is correct. ERROR As long as the pipe is not correctly configured (CFGOK = 0), the controller can not send packets to the device through this pipe. The CFGOK bit is set by hardware only if the configured size and number of banks are correct compared to their maximal allowed values for the pipe (see Table 30-1 on page 497) and to the maximal FIFO size (i.e. the DPRAM size). See Section 30.7.1.6 on page 506 for more details about DPRAM management. Once the pipe is correctly configured (CFGOK = 1), only the PTOKEN and INTFRQ bit-fields can be modified by software. INTFRQ is meaningless for non-interrupt pipes. When starting an enumeration, the firmware gets the device descriptor by sending a GET_DESCRIPTOR USB request. This descriptor contains the maximal packet size of the device default control endpoint (bMaxPacketSize0) and the firmware re-configures the size of the default control pipe with this size parameter. 30.7.3.7 Address Setup Once the device has answered the first host requests with the default device address 0, the host assigns a new address to the device. The host controller has to send a USB reset to the device and to send a SET_ADDRESS(addr) SETUP request with the new address to be used by the device. Once this SETUP transaction is over, the firmware writes the new address into the HADDR bit-field. All following requests, on all pipes, will be performed using this new address. When the host controller sends a USB reset, the HADDR bit-field is reset by hardware and the following host requests will be performed using the default device address 0. 30.7.3.8 Remote Wake-Up The controller host mode enters the Suspend state when the SOFE bit is cleared. No more “Start of Frame” is sent on the USB bus and the USB device enters the Suspend state 3 ms later. The device awakes the host by sending an Upstream Resume (Remote Wake-Up feature). When the host controller detects a non-idle state on the USB bus, it raises the Host Wake-Up 524 32058H–AVR32–03/09 AT32UC3A interrupt (HWUPI). If the non-idle bus state corresponds to an Upstream Resume (K state), the Upstream Resume Received interrupt (RXRSMI) is raised. The firmware has to generate a Downstream Resume within 1 ms and for at least 20 ms by setting the RESUME bit. It is mandatory to set SOFE before setting RESUME to enter the Ready state, else RESUME will have no effect. 30.7.3.9 Management of Control Pipes A control transaction is composed of three stages: •SETUP; •Data (IN or OUT); •Status (OUT or IN). The firmware has to change the pipe token according to each stage. For the control pipe, and only for it, each token is assigned a specific initial data toggle sequence: •SETUP: Data0; •IN: Data1; •OUT: Data1. 30.7.3.10 Management of IN Pipes IN packets are sent by the USB device controller upon IN requests from the host. All the data can be read by the firmware which acknowledges or not the bank when it is empty. The pipe must be configured first. When the host requires data from the device, the firmware has to select beforehand the IN request mode with the INMODE bit: •when INMODE is cleared, the USB controller will perform (INRQ + 1) IN requests before freezing the pipe; •when INMODE is set, the USB controller will perform IN requests endlessly when the pipe is not frozen by the firmware. The generation of IN requests starts when the pipe is unfrozen (PFREEZE = 0). The RXINI bit is set by hardware at the same time as FIFOCON when the current bank is full. This triggers a PXINT interrupt if RXINE = 1. RXINI shall be cleared by software (by setting the RXINIC bit) to acknowledge the interrupt, what has no effect on the pipe FIFO. The firmware then reads from the FIFO and clears the FIFOCON bit to free the bank. If the IN pipe is composed of multiple banks, this also switches to the next bank. The RXINI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. RXINI shall always be cleared before clearing FIFOCON. The RWALL bit is set by hardware when the current bank is not empty, i.e. the software can read further data from the FIFO. 525 32058H–AVR32–03/09 AT32UC3A Figure 30-25. Example of an IN Pipe with 1 Data Bank IN DATA (bank 0) ACK IN DATA (bank 0) ACK HW RXINI SW HW SW FIFOCON read data from CPU BANK 0 SW read data from CPU BANK 0 Figure 30-26. Example of an IN Pipe with 2 Data Banks IN DATA (bank 0) ACK IN DATA (bank 1) ACK HW RXINI SW HW SW FIFOCON read data from CPU BANK 0 SW read data from CPU BANK 1 30.7.3.11 Management of OUT Pipes OUT packets are sent by the host. All the data can be written by the firmware which acknowledges or not the bank when it is full. The pipe must be configured and unfrozen first. The TXOUTI bit is set by hardware at the same time as FIFOCON when the current bank is free. This triggers a PXINT interrupt if TXOUTE = 1. TXOUTI shall be cleared by software (by setting the TXOUTIC bit) to acknowledge the interrupt, what has no effect on the pipe FIFO. The firmware then writes into the FIFO and clears the FIFOCON bit to allow the USB controller to send the data. If the OUT pipe is composed of multiple banks, this also switches to the next bank. The TXOUTI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. TXOUTI shall always be cleared before clearing FIFOCON. The RWALL bit is set by hardware when the current bank is not full, i.e. the software can write further data into the FIFO. Note that if the firmware decides to switch to the Suspend state (by clearing the SOFE bit) while a bank is ready to be sent, the USB controller automatically exits this state and the bank is sent. 526 32058H–AVR32–03/09 AT32UC3A Figure 30-27. Example of an OUT Pipe with 1 Data Bank OUT DATA (bank 0) ACK OUT HW TXOUTI SW SW FIFOCON write data to CPU BANK 0 SW write data to CPU BANK 0 SW Figure 30-28. Example of an OUT Pipe with 2 Data Banks and no Bank Switching Delay OUT DATA (bank 0) ACK OUT DATA (bank 1) ACK HW TXOUTI SW SW SW FIFOCON write data to CPU BANK 0 SW write data to CPU BANK 1 SW write data to CPU BANK0 Figure 30-29. Example of an OUT Pipe with 2 Data Banks and a Bank Switching Delay OUT DATA (bank 0) ACK OUT DATA (bank 1) ACK HW TXOUTI SW SW SW FIFOCON write data to CPU BANK 0 SW write data to CPU BANK 1 SW write data to CPU BANK0 30.7.3.12 CRC Error This error exists only for isochronous IN pipes. It raises the CRC Error interrupt (CRCERRI), what triggers a PXINT interrupt if CRCERRE = 1. A CRC error can occur during IN stage if the USB controller detects a corrupted received packet. The IN packet is stored in the bank as if no CRC error had occurred (RXINI is raised). 527 32058H–AVR32–03/09 AT32UC3A 30.7.3.13 Interrupts See the structure of the USB host interrupt system on Figure 30-6 on page 504. There are two kinds of host interrupts: processing, i.e. their generation is part of the normal processing, and exception, i.e. errors (not related to CPU exceptions). 30.7.3.13.1 Global Interrupts The processing host global interrupts are: •the Device Connection interrupt (DCONNI); •the Device Disconnection interrupt (DDISCI); •the USB Reset Sent interrupt (RSTI); •the Downstream Resume Sent interrupt (RSMEDI); •the Upstream Resume Received interrupt (RXRSMI); •the Host Start of Frame interrupt (HSOFI); •the Host Wake-Up interrupt (HWUPI); •the Pipe X interrupt (PXINT); •the DMA Channel X interrupt (DMAXINT). There is no exception host global interrupt. 30.7.3.13.2 Pipe Interrupts The processing host pipe interrupts are: •the Received IN Data interrupt (RXINI); •the Transmitted OUT Data interrupt (TXOUTI); •the Transmitted SETUP interrupt (TXSTPI); •the Short Packet interrupt (SHORTPACKETI); •the Number of Busy Banks interrupt (NBUSYBK). The exception host pipe interrupts are: •the Underflow interrupt (UNDERFI); •the Pipe Error interrupt (PERRI); •the NAKed interrupt (NAKEDI); •the Overflow interrupt (OVERFI); •the Received STALLed interrupt (RXSTALLDI); •the CRC Error interrupt (CRCERRI). 30.7.3.13.3 DMA Interrupts The processing host DMA interrupts are: •the End of USB Transfer Status interrupt (EOT_STA); •the End of Channel Buffer Status interrupt (EOCH_BUFF_STA); •the Descriptor Loaded Status interrupt (DESC_LD_STA). There is no exception host DMA interrupt. 528 32058H–AVR32–03/09 AT32UC3A 30.7.4 USB DMA Operation USB packets of any length may be transferred when required by the USB controller. These transfers always feature sequential addressing. These two characteristics mean that in case of high USB controller throughput, both HSB ports will benefit from “incrementing burst of unspecified length” since the average access latency of HSB slaves can then be reduced. The DMA uses word “incrementing burst of unspecified length” of up to 256 beats for both data transfers and channel descriptor loading. A burst may last on the HSB busses for the duration of a whole USB packet transfer, unless otherwise broken by the HSB arbitration or the HSB 1 kbyte boundary crossing. Packet data HSB bursts may be locked on a DMA buffer basis for drastic overall HSB bus bandwidth performance boost with paged memories. This is because these memories row (or bank) changes, which are very clock-cycle consuming, will then likely not occur or occur once instead of dozens of times during a single big USB packet DMA transfer in case other HSB masters address the memory. This means up to 128 words single cycle unbroken HSB bursts for bulk pipes/endpoints and 256 words single cycle unbroken bursts for isochronous pipes/endpoints. This maximal burst length is then controlled by the lowest programmed USB pipe/endpoint size (PSIZE/EPSIZE) and DMA channel byte length (CH_BYTE_LENGTH). The USB controller average throughput may be up to nearly 1.5 Mbyte/s. Its average access latency decreases as burst length increases due to the 0 wait-state side effect of unchanged pipe/endpoint. Word access allows reducing the HSB bandwidth required for the USB by 4 compared to native byte access. If at least 0 wait-state word burst capability is also provided by the other DMA HSB bus slaves, each of both DMA HSB busses need less than 1.1% bandwidth allocation for full USB bandwidth usage at 33 MHz, and less than 0.6% at 66 MHz. Figure 30-30. Example of DMA Chained List Transfer Descriptor USB DMA Channel X Registers (Current Transfer Descriptor) Next Descriptor Address Next Descriptor Address HSB Address Control HSB Address Control Status Transfer Descriptor Next Descriptor Address HSB Address Control Transfer Descriptor Next Descriptor Address HSB Address Control NULL Memory Area Data Buffer 1 Data Buffer 2 Data Buffer 3 529 32058H–AVR32–03/09 AT32UC3A 30.8 USB User Interface USB PB Memory Map Register Device General Control Register Device Global Interrupt Register Device Global Interrupt Clear Register Device Global Interrupt Set Register Device Global Interrupt Enable Register Device Global Interrupt Enable Clear Register Device Global Interrupt Enable Set Register Endpoint Enable/Reset Register Device Frame Number Register Reserved Endpoint 0 Configuration Register Endpoint 1 Configuration Register Endpoint 2 Configuration Register Endpoint 3 Configuration Register Endpoint 4 Configuration Register Endpoint 5 Configuration Register Endpoint 6 Configuration Register Reserved Endpoint 0 Status Register Endpoint 1 Status Register Endpoint 2 Status Register Endpoint 3 Status Register Endpoint 4 Status Register Endpoint 5 Status Register Endpoint 6 Status Register Reserved Endpoint 0 Status Clear Register Endpoint 1 Status Clear Register Endpoint 2 Status Clear Register Endpoint 3 Status Clear Register Endpoint 4 Status Clear Register Endpoint 5 Status Clear Register Endpoint 6 Status Clear Register Reserved Endpoint 0 Status Set Register Name UDCON UDINT UDINTCLR UDINTSET UDINTE UDINTECLR UDINTESET UERST UDFNUM – UECFG0 UECFG1 UECFG2 UECFG3 UECFG4 UECFG5 UECFG6 – UESTA0 UESTA1 UESTA2 UESTA3 UESTA4 UESTA5 UESTA6 – UESTA0CLR UESTA1CLR UESTA2CLR UESTA3CLR UESTA4CLR UESTA5CLR UESTA6CLR – UESTA0SET Access Read/Write Read-Only Write-Only Write-Only Read-Only Write-Only Write-Only Read/Write Read-Only – Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Write-Only Reset Value 0x00000100 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000100 0x00000100 0x00000100 0x00000100 0x00000100 0x00000100 0x00000100 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 Table 30-5. Offset 0x0000 0x0004 0x0008 0x000C 0x0010 0x0014 0x0018 0x001C 0x0020 0x0024 - 0x00FC 0x0100 0x0104 0x0108 0x010C 0x0110 0x0114 0x0118 +0x004 - 0x012C 0x0130 0x0134 0x0138 0x013C 0x0140 0x0144 0x0148 +0x004 - 0x015C 0x0160 0x0164 0x0168 0x016C 0x0170 0x0174 0x0178 +0x04 - 0x018C 0x0190 530 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x0194 0x0198 0x019C 0x01A0 0x01A4 0x01A8 +0x04 - 0x01BC 0x01C0 0x01C4 0x01C8 0x01CC 0x01D0 0x01D4 0x01D8 +0x04 - 0x01EC 0x01F0 0x01F4 0x01F8 0x01FC 0x0200 0x0204 0x0208 +0x04 - 0x021C 0x0220 0x0224 0x0228 0x022C 0x0230 0x0234 0x0238 +0x04 - 0x030C 0x0310 0x0314 0x0318 USB PB Memory Map Register Endpoint 1 Status Set Register Endpoint 2 Status Set Register Endpoint 3 Status Set Register Endpoint 4 Status Set Register Endpoint 5 Status Set Register Endpoint 6 Status Set Register Reserved Endpoint 0 Control Register Endpoint 1 Control Register Endpoint 2 Control Register Endpoint 3 Control Register Endpoint 4 Control Register Endpoint 5 Control Register Endpoint 6 Control Register Reserved Endpoint 0 Control Set Register Endpoint 1 Control Set Register Endpoint 2 Control Set Register Endpoint 3 Control Set Register Endpoint 4 Control Set Register Endpoint 5 Control Set Register Endpoint 6 Control Set Register Reserved Endpoint 0 Control Clear Register Endpoint 1 Control Clear Register Endpoint 2 Control Clear Register Endpoint 3 Control Clear Register Endpoint 4 Control Clear Register Endpoint 5 Control Clear Register Endpoint 6 Control Clear Register Reserved Device DMA Channel 1 Next Descriptor Address Register Device DMA Channel 1 HSB Address Register Device DMA Channel 1 Control Register Name UESTA1SET UESTA2SET UESTA3SET UESTA4SET UESTA5SET UESTA6SET – UECON0 UECON1 UECON2 UECON3 UECON4 UECON5 UECON6 – UECON0SET UECON1SET UECON2SET UECON3SET UECON4SET UECON5SET UECON6SET – UECON0CLR UECON1CLR UECON2CLR UECON3CLR UECON4CLR UECON5CLR UECON6CLR – UDDMA1_ NEXTDESC UDDMA1_ ADDR UDDMA1_ CONTROL Access Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Read/Write Read/Write Read/Write Reset Value 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 531 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x031C 0x0320 0x0324 0x0328 0x032C 0x0330 0x0334 0x0338 0x033C 0x0340 0x0344 0x0348 0x034C 0x0350 0x0354 0x0358 0x035C 0x0360 0x0364 0x0368 0x036C 0x0370 - 0x03FC USB PB Memory Map Register Device DMA Channel 1 Status Register Device DMA Channel 2 Next Descriptor Address Register Device DMA Channel 2 HSB Address Register Device DMA Channel 2 Control Register Device DMA Channel 2 Status Register Device DMA Channel 3 Next Descriptor Address Register Device DMA Channel 3 HSB Address Register Device DMA Channel 3 Control Register Device DMA Channel 3 Status Register Device DMA Channel 4 Next Descriptor Address Register Device DMA Channel 4 HSB Address Register Device DMA Channel 4 Control Register Device DMA Channel 4 Status Register Device DMA Channel 5 Next Descriptor Address Register Device DMA Channel 5 HSB Address Register Device DMA Channel 5 Control Register Device DMA Channel 5 Status Register Device DMA Channel 6 Next Descriptor Address Register Device DMA Channel 6 HSB Address Register Device DMA Channel 6 Control Register Device DMA Channel 6 Status Register Reserved Name UDDMA1_ STATUS UDDMA2_ NEXTDESC UDDMA2_ ADDR UDDMA2_ CONTROL UDDMA2_ STATUS UDDMA3_ NEXTDESC UDDMA3_ ADDR UDDMA3_ CONTROL UDDMA3_ STATUS UDDMA4_ NEXTDESC UDDMA4_ ADDR UDDMA4_ CONTROL UDDMA4_ STATUS UDDMA5_ NEXTDESC UDDMA5_ ADDR UDDMA5_ CONTROL UDDMA5_ STATUS UDDMA6_ NEXTDESC UDDMA6_ ADDR UDDMA6_ CONTROL UDDMA6_ STATUS – Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Reset Value 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 532 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x0400 0x0404 0x0408 0x040C 0x0410 0x0414 0x0418 0x0041C 0x0420 0x0424 0x0428 +0x04 - 0x04FC 0x0500 0x0504 0x0508 0x050C 0x0510 0x0514 0x0518 +0x04 - 0x052C 0x0530 0x0534 0x0538 0x053C 0x0540 0x0544 0x0548 +0x04 - 0x055C 0x0560 0x0564 0x0568 0x056C 0x0570 0x0574 0x0578 +0x04 - 0x058C USB PB Memory Map Register Host General Control Register Host Global Interrupt Register Host Global Interrupt Clear Register Host Global Interrupt Set Register Host Global Interrupt Enable Register Host Global Interrupt Enable Clear Register Host Global Interrupt Enable Set Register Pipe Enable/Reset Register Host Frame Number Register Host Address 1 Register Host Address 2 Register Reserved Pipe 0 Configuration Register Pipe 1 Configuration Register Pipe 2 Configuration Register Pipe 3 Configuration Register Pipe 4 Configuration Register Pipe 5 Configuration Register Pipe 6 Configuration Register Reserved Pipe 0 Status Register Pipe 1 Status Register Pipe 2 Status Register Pipe 3 Status Register Pipe 4 Status Register Pipe 5 Status Register Pipe 6 Status Register Reserved Pipe 0 Status Clear Register Pipe 1 Status Clear Register Pipe 2 Status Clear Register Pipe 3 Status Clear Register Pipe 4 Status Clear Register Pipe 5 Status Clear Register Pipe 6 Status Clear Register Reserved Name UHCON UHINT UHINTCLR UHINTSET UHINTE UHINTECLR UHINTESET UPRST UHFNUM UHADDR1 UHADDR2 – UPCFG0 UPCFG1 UPCFG2 UPCFG3 UPCFG4 UPCFG5 UPCFG6 – UPSTA0 UPSTA1 UPSTA2 UPSTA3 UPSTA4 UPSTA5 UPSTA6 – UPSTA0CLR UPSTA1CLR UPSTA2CLR UPSTA3CLR UPSTA4CLR UPSTA5CLR UPSTA6CLR – Access Read/Write Read-Only Write-Only Write-Only Read-Only Write-Only Write-Only Read/Write Read/Write Read/Write Read/Write – Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Reset Value 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 533 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x0590 0x0594 0x0598 0x059C 0x05A0 0x05A4 0x05A8 +0x04 - 0x05BC 0x05C0 0x05C4 0x05C8 0x05CC 0x05D0 0x05D4 0x05D8 +0x04 - 0x05EC 0x05F0 0x05F4 0x05F8 0x05FC 0x0600 0x0604 0x0608 +0x04 - 0x061C 0x0620 0x0624 0x0628 0x062C 0x0630 0x0634 0x0638 +0x04 - 0x064C 0x0650 0x0654 0x0658 0x065C USB PB Memory Map Register Pipe 0 Status Set Register Pipe 1 Status Set Register Pipe 2 Status Set Register Pipe 3 Status Set Register Pipe 4 Status Set Register Pipe 5 Status Set Register Pipe 6 Status Set Register Reserved Pipe 0 Control Register Pipe 1 Control Register Pipe 2 Control Register Pipe 3 Control Register Pipe 4 Control Register Pipe 5 Control Register Pipe 6 Control Register Reserved Pipe 0 Control Set Register Pipe 1 Control Set Register Pipe 2 Control Set Register Pipe 3 Control Set Register Pipe 4 Control Set Register Pipe 5 Control Set Register Pipe 6 Control Set Register Reserved Pipe 0 Control Clear Register Pipe 1 Control Clear Register Pipe 2 Control Clear Register Pipe 3 Control Clear Register Pipe 4 Control Clear Register Pipe 5 Control Clear Register Pipe 6 Control Clear Register Reserved Pipe 0 IN Request Register Pipe 1 IN Request Register Pipe 2 IN Request Register Pipe 3 IN Request Register Name UPSTA0SET UPSTA1SET UPSTA2SET UPSTA3SET UPSTA4SET UPSTA5SET UPSTA6SET – UPCON0 UPCON1 UPCON2 UPCON3 UPCON4 UPCON5 UPCON6 – UPCON0SET UPCON1SET UPCON2SET UPCON3SET UPCON4SET UPCON5SET UPCON6SET – UPCON0CLR UPCON1CLR UPCON2CLR UPCON3CLR UPCON4CLR UPCON5CLR UPCON6CLR – UPINRQ0 UPINRQ1 UPINRQ2 UPINRQ3 Access Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only Write-Only – Read/Write Read/Write Read/Write Read/Write Reset Value 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 534 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x0660 0x0664 0x0668 0x066C - 0x067C 0x0680 0x0684 0x0688 0x068C 0x0690 0x0694 0x0698 +0x04 - 0x070C 0x0710 0x0714 0x0718 0x071C 0x0720 0x0724 0x0728 0x072C 0x0730 0x0734 0x0738 0x073C 0x0740 0x0744 USB PB Memory Map Register Pipe 4 IN Request Register Pipe 5 IN Request Register Pipe 6 IN Request Register Reserved Pipe 0 Error Register Pipe 1 Error Register Pipe 2 Error Register Pipe 3 Error Register Pipe 4 Error Register Pipe 5 Error Register Pipe 6 Error Register Reserved Host DMA Channel 1 Next Descriptor Address Register Host DMA Channel 1 HSB Address Register Host DMA Channel 1 Control Register Host DMA Channel 1 Status Register Host DMA Channel 2 Next Descriptor Address Register Host DMA Channel 2 HSB Address Register Host DMA Channel 2 Control Register Host DMA Channel 2 Status Register Host DMA Channel 3 Next Descriptor Address Register Host DMA Channel 3 HSB Address Register Host DMA Channel 3 Control Register Host DMA Channel 3Status Register Host DMA Channel 4 Next Descriptor Address Register Host DMA Channel 4 HSB Address Register Name UPINRQ4 UPINRQ5 UPINRQ6 – UPERR0 UPERR1 UPERR2 UPERR3 UPERR4 UPERR5 UPERR6 – UHDMA1_ NEXTDESC UHDMA1_ ADDR UHDMA1_ CONTROL UHDMA1_ STATUS UHDMA2_ NEXTDESC UHDMA2_ ADDR UHDMA2_ CONTROL UHDMA2_ STATUS UHDMA3_ NEXTDESC UHDMA3_ ADDR UHDMA3_ CONTROL UHDMA3_ STATUS UHDMA4_ NEXTDESC UHDMA4_ ADDR Access Read/Write Read/Write Read/Write – Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Reset Value 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 535 32058H–AVR32–03/09 AT32UC3A Table 30-5. Offset 0x0748 0x074C 0x0750 0x0754 0x0758 0x075C 0x0760 0x0764 0x0768 0x076C 0x0770 - 0x07FC 0x0800 0x0804 0x0808 0x080C 0x0810-0x0814 0x0818 0x081C 0x0820 0x0824 0x0828 0x082C 0x0830 - 0x0BFC USB PB Memory Map Register Host DMA Channel 4 Control Register Host DMA Channel 4 Status Register Host DMA Channel 5 Next Descriptor Address Register Host DMA Channel 5 HSB Address Register Host DMA Channel 5 Control Register Host DMA Channel 5 Status Register Host DMA Channel 6 Next Descriptor Address Register Host DMA Channel 6 HSB Address Register Host DMA Channel 6 Control Register Host DMA Channel 6 Status Register Reserved General Control Register General Status Register General Status Clear Register General Status Set Register Reserved IP Version Register IP Features Register IP PB Address Size Register IP Name Register 1 IP Name Register 2 USB Finite State Machine Status Register Reserved Name UHDMA4_ CONTROL UHDMA4_ STATUS UHDMA5_ NEXTDESC UHDMA5_ ADDR UHDMA5_ CONTROL UHDMA5_ STATUS UHDMA6_ NEXTDESC UHDMA6_ ADDR UHDMA6_ CONTROL UHDMA6_ STATUS – USBCON USBSTA USBSTACLR USBSTASET – UVERS UFEATURES UADDRSIZE UNAME1 UNAME2 USBFSM – Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Read/Write Read-Only Write-Only Write-Only – Read-Only Read-Only Read-Only Read-Only Read-Only Read-Only – Reset Value 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 – 0x03004000 0x00000400 0x00000000 0x00000000 – 0x00000311 0x00012467 0x00001000 0x48555342 (“HUSB”) 0x004F5447 (“\0OTG“) 0x00000009 – 536 32058H–AVR32–03/09 AT32UC3A Table 30-6. Offset 0x00000 0x0FFFC 0x10000 0x1FFFC 0x20000 0x2FFFC 0x30000 0x3FFFC 0x40000 0x4FFFC 0x50000 0x5FFFC 0x60000 0x6FFFC +0x00004 0xFFFFC USB HSB Memory Map Register Pipe/Endpoint 0 FIFO Data Register Pipe/Endpoint 1 FIFO Data Register Pipe/Endpoint 2 FIFO Data Register Pipe/Endpoint 3 FIFO Data Register Pipe/Endpoint 4 FIFO Data Register Pipe/Endpoint 5 FIFO Data Register Pipe/Endpoint 6 FIFO Data Register Reserved Name USB_ FIFO0_DATA USB_ FIFO1_DATA USB_ FIFO2_DATA USB_ FIFO3_DATA USB_ FIFO4_DATA USB_ FIFO5_DATA USB_ FIFO6_DATA – Access Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write Read/Write – Reset Value Undefined Undefined Undefined Undefined Undefined Undefined Undefined – In the following subsections, the bit and bit-field access types use the following flags: •“r”: readable; •“w”: writable; •“u”: may be updated by hardware. 537 32058H–AVR32–03/09 AT32UC3A 30.8.1 30.8.1.1 USB General Registers USB General Control Register (USBCON) 0x0800 USBCON Read/Write 0x03004000 30 – 29 – 28 – 27 – 26 – 25 UIMOD rw 1 17 TIMVALUE rw 0 11 HNPREQ rwu 0 3 VBERRE rw 0 10 SRPREQ rwu 0 2 SRPE rw 0 9 SRPSEL rw 0 1 VBUSTE rw 0 0 8 VBUSHWC rw 0 0 IDTE rw 0 24 UIDE rw 1 16 Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 UNLOCK rw 0 14 FRZCLK rw 1 6 HNPERRE rw 0 21 TIMPAGE rw 0 13 VBUSPO rw 0 5 ROLEEXE rw 0 20 19 – 18 – 0 12 OTGPADE rw 0 4 BCERRE rw 0 15 USBE rw 0 7 STOE rw 0 • IDTE: ID Transition Interrupt Enable Set to enable the ID Transition interrupt (IDTI). Clear to disable the ID Transition interrupt (IDTI). • VBUSTE: VBus Transition Interrupt Enable Set to enable the VBus Transition interrupt (VBUSTI). Clear to disable the VBus Transition interrupt (VBUSTI). • SRPE: SRP Interrupt Enable Set to enable the SRP interrupt (SRPI). Clear to disable the SRP interrupt (SRPI). • VBERRE: VBus Error Interrupt Enable Set to enable the VBus Error interrupt (VBERRI). Clear to disable the VBus Error interrupt (VBERRI). • BCERRE: B-Connection Error Interrupt Enable Set to enable the B-Connection Error interrupt (BCERRI). Clear to disable the B-Connection Error interrupt (BCERRI). • ROLEEXE: Role Exchange Interrupt Enable Set to enable the Role Exchange interrupt (ROLEEXI). 538 32058H–AVR32–03/09 AT32UC3A Clear to disable the Role Exchange interrupt (ROLEEXI). • HNPERRE: HNP Error Interrupt Enable Set to enable the HNP Error interrupt (HNPERRI). Clear to disable the HNP Error interrupt (HNPERRI). • STOE: Suspend Time-Out Interrupt Enable Set to enable the Suspend Time-Out interrupt (STOI). Clear to disable the Suspend Time-Out interrupt (STOI). • VBUSHWC: VBus Hardware Control Set to disable the hardware control over the USB_VBOF output pin. Clear to enable the hardware control over the USB_VBOF output pin. If cleared, then the USB macro considers VBus problems and resets the USB_VBOF output pin in that event. • SRPSEL: SRP Selection Set to choose VBus pulsing as SRP method. Clear to choose data line pulsing as SRP method. • SRPREQ: SRP Request Set to initiate an SRP when the controller is in device mode. Cleared by hardware when the controller is initiating an SRP. • HNPREQ: HNP Request When the controller is in device mode: Set to initiate an HNP. Cleared by hardware when the controller is initiating an HNP. When the controller is in host mode: Set to accept an HNP. Clear otherwise. • OTGPADE: OTG Pad Enable Set to enable the OTG pad. Clear to disable the OTG pad. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit. • VBUSPO: VBus Polarity When 0, the USB_VBOF output signal is in its default mode (active high). When 1, the USB_VBOF output signal is inverted (active low). To be generic. May be useful to control an external VBus power module. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit. 539 32058H–AVR32–03/09 AT32UC3A • FRZCLK: Freeze USB Clock Set to disable the clock inputs (the resume detection is still active). This reduces power consumption. Unless explicitly stated, all registers then become read-only. Clear to enable the clock inputs. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit, but this freezes the clock inputs whatever its value. • USBE: USB Macro Enable Set to enable the USB controller. Clear to disable and reset the USB controller, to disable the USB transceiver and to disable the USB controller clock inputs. Unless explicitly stated, all registers then become read-only and are reset. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. • TIMVALUE: Timer Value Set to initialize the new value of the special timer register selected by TIMPAGE. • TIMPAGE: Timer Page Write the page value to access a special timer register. • UNLOCK: Timer Access Unlock Set to unlock the TIMPAGE and TIMVALUE fields before writing them. Reset to lock the TIMPAGE and TIMVALUE fields. Note that the TIMPAGE and TIMVALUE fields can always be read, whatever the value of UNLOCK. • UIDE: USB_ID Pin Enable Set to select the USB mode (device/host) from the USB_ID input pin. Clear to select the USB mode (device/host) with the UIMOD bit. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit. • UIMOD: USB Macro Mode This bit has no effect when UIDE = 1 (USB_ID input pin activated). Set to select the USB device mode. Clear to select the USB host mode. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit. 540 32058H–AVR32–03/09 AT32UC3A 30.8.1.2 USB General Status Register (USBSTA) 0x0804 USBSTA Read-Only 0x00000400 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 SPEED ru 0 12 0 4 BCERRI ru 0 11 VBUS ru 0 3 VBERRI ru 0 10 ID ru 1 2 SRPI ru 0 9 VBUSRQ ru 0 1 VBUSTI ru 0 8 – 7 STOI ru 0 6 HNPERRI ru 0 5 ROLEEXI ru 0 0 IDTI ru 0 • IDTI: ID Transition Interrupt Flag Asynchronous interrupt. Set by hardware when a transition (high to low, low to high) has been detected on the USB_ID input pin. This triggers a USB interrupt if IDTE = 1. Shall be cleared by software (by setting the IDTIC bit) to acknowledge the interrupt (USB clock inputs must be enabled before). Note that this interrupt is generated even if the clock is frozen by the FRZCLK bit. • VBUSTI: VBus Transition Interrupt Flag Asynchronous interrupt. Set by hardware when a transition (high to low, low to high) has been detected on the VBUS pad. This triggers a USB interrupt if VBUSTE = 1. Shall be cleared by software (by setting the VBUSTIC bit) to acknowledge the interrupt (USB clock inputs must be enabled before). Note that this interrupt is generated even if the clock is frozen by the FRZCLK bit. • SRPI: SRP Interrupt Flag Shall only be used in host mode. Set by hardware when an SRP has been detected. This triggers a USB interrupt if SRPE = 1. Shall be cleared by software (by setting the SRPIC bit) to acknowledge the interrupt. 541 32058H–AVR32–03/09 AT32UC3A • VBERRI: VBus Error Interrupt Flag In host mode, set by hardware when a VBus drop has been detected. This triggers a USB interrupt if VBERRE = 1. Shall be cleared by software (by setting the VBERRIC bit) to acknowledge the interrupt. Note that if a VBus problem occurs, then the VBERRI interrupt is generated even if the USB macro does not go to an error state because of VBUSHWC = 1. • BCERRI: B-Connection Error Interrupt Flag In host mode, set by hardware when an error occurs during the B-connection. This triggers a USB interrupt if BCERRE = 1. Shall be cleared by software (by setting the BCERRIC bit) to acknowledge the interrupt. • ROLEEXI: Role Exchange Interrupt Flag Set by hardware when the USB controller has successfully switched its mode because of an HNP negotiation (host to device or device to host). This triggers a USB interrupt if ROLEEXE = 1. Shall be cleared by software (by setting the ROLEEXIC bit) to acknowledge the interrupt. • HNPERRI: HNP Error Interrupt Flag In device mode, set by hardware when an error has been detected during an HNP negotiation. This triggers a USB interrupt if HNPERRE = 1. Shall be cleared by software (by setting the HNPERRIC bit) to acknowledge the interrupt. • STOI: Suspend Time-Out Interrupt Flag In host mode, set by hardware when a time-out error (more than 200ms) has been detected after a suspend. This triggers a USB interrupt if STOE = 1. Shall be cleared by software (by setting the STOIC bit) to acknowledge the interrupt. • VBUSRQ: VBus Request In host mode, set by software (by setting the VBUSRQS bit) to assert the USB_VBOF output pin in order to enable the VBus power supply generation. Cleared by software by setting the VBUSRQC bit. Cleared by hardware when a VBus error occurs when VBUSHWC = 0. • ID: USB_ID Pin State Set/cleared by hardware and reflects the state of the USB_ID input pin, even if USBE = 0. • VBUS: VBus Level Set/cleared by hardware and reflects the level of the VBus line, even if USBE = 0. This bit can be used in device mode to monitor the USB bus connection state of the application. • SPEED: Speed Status Set by hardware according to the controller speed mode: SPEED 0 1 X 0 0 1 Speed Status FULL-SPEED mode LOW-SPEED mode Reserved Shall only be used in host mode. 542 32058H–AVR32–03/09 AT32UC3A 30.8.1.3 USB General Status Clear Register (USBSTACLR) 0x0808 USBSTACLR Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 VBUSRQC w 0 1 VBUSTIC w 0 8 – 7 STOIC w 0 6 HNPERRIC w 0 5 ROLEEXIC w 0 4 BCERRIC w 0 3 VBERRIC w 0 2 SRPIC w 0 0 IDTIC w 0 • IDTIC: ID Transition Interrupt Flag Clear Set to clear IDTI. Clearing has no effect. Always read as 0. • VBUSTIC: VBus Transition Interrupt Flag Clear Set to clear VBUSTI. Clearing has no effect. Always read as 0. • SRPIC: SRP Interrupt Flag Clear Set to clear SRPI. Clearing has no effect. Always read as 0. • VBERRIC: VBus Error Interrupt Flag Clear Set to clear VBERRI. Clearing has no effect. Always read as 0. • BCERRIC: B-Connection Error Interrupt Flag Clear Set to clear BCERRI. 543 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • ROLEEXIC: Role Exchange Interrupt Flag Clear Set to clear ROLEEXI. Clearing has no effect. Always read as 0. • HNPERRIC: HNP Error Interrupt Flag Clear Set to clear HNPERRI. Clearing has no effect. Always read as 0. • STOIC: Suspend Time-Out Interrupt Flag Clear Set to clear STOI. Clearing has no effect. Always read as 0. • VBUSRQC: VBus Request Clear Set to clear VBUSRQ. Clearing has no effect. Always read as 0. 544 32058H–AVR32–03/09 AT32UC3A 30.8.1.4 USB General Status Set Register (USBSTASET) 0x080C USBSTASET Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 VBUSRQS w 0 1 VBUSTIS w 0 8 – 7 STOIS w 0 6 HNPERRIS w 0 5 ROLEEXIS w 0 4 BCERRIS w 0 3 VBERRIS w 0 2 SRPIS w 0 0 IDTIS w 0 • IDTIS: ID Transition Interrupt Flag Set Set to set IDTI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • VBUSTIS: VBus Transition Interrupt Flag Set Set to set VBUSTI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • SRPIS: SRP Interrupt Flag Set Set to set SRPI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • VBERRIS: VBus Error Interrupt Flag Set Set to set VBERRI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • BCERRIS: B-Connection Error Interrupt Flag Set Set to set BCERRI, what may be useful for test or debug purposes. 545 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • ROLEEXIS: Role Exchange Interrupt Flag Set Set to set ROLEEXI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • HNPERRIS: HNP Error Interrupt Flag Set Set to set HNPERRI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • STOIS: Suspend Time-Out Interrupt Flag Set Set to set STOI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • VBUSRQS: VBus Request Set Set to set VBUSRQ. Clearing has no effect. Always read as 0. 546 32058H–AVR32–03/09 AT32UC3A 30.8.1.5 USB IP Version Register (UVERS) 0x0818 UVERS Read-Only 0x00000260 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 0 15 14 13 12 11 VERSION_NUM r 10 17 METAL_FIX_NUM r 0 9 16 0 8 0 7 6 5 4 VERSION_NUM r 6 3 2 2 1 0 0 • VERSION_NUM: IP Version Number This field indicates the version number of the USB macro IP, encoded with 1 version digit per nibble, e.g. 0x0260 for version 2.6.0. • METAL_FIX_NUM: Number of Metal Fixes This field indicates the number of metal fixes of the USB macro IP. 547 32058H–AVR32–03/09 AT32UC3A 30.8.1.6 USB IP Features Register (UFEATURES) 0x081C UFEATURES Read-Only 0x00012467 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 BYTE_WRITE _DPRAM r 0 7 DMA_BUFFER _SIZE r 0 14 13 FIFO_MAX_SIZE 12 11 10 9 8 DMA_FIFO_WORD_DEPTH r 0 4 0 3 1 2 EPT_NBR_MAX r 0 0 1 1 1 0 1 0 0 0 6 r 1 5 DMA_CHANNEL_NBR 1 r 1 • EPT_NBR_MAX: Maximal Number of Pipes/Endpoints This field indicates the number of hardware-implemented pipes/endpoints: EPT_NBR_MAX 0 0 0 0 0 0 0 0 1 0 1 0 Maximal Number of Pipes/Endpoints 16 1 2 ... 1 1 1 1 15 • DMA_CHANNEL_NBR: Number of DMA Channels This field indicates the number of hardware-implemented DMA channels: DMA_CHANNEL_NBR 0 0 0 0 0 1 0 1 0 Number of DMA Channels Reserved 1 2 ... 1 1 1 7 548 32058H–AVR32–03/09 AT32UC3A • DMA_BUFFER_SIZE: DMA Buffer Size This field indicates the size of the DMA buffer: DMA_BUFFER_SIZE 0 1 DMA Buffer Size 16 bits 24 bits • DMA_FIFO_WORD_DEPTH: DMA FIFO Depth in Words This field indicates the DMA FIFO depth controller in words: DMA_FIFO_WORD_DEPTH 0 0 0 0 0 0 0 0 1 0 1 0 DMA FIFO Depth in Words 16 1 2 ... 1 1 1 1 15 • FIFO_MAX_SIZE: Maximal FIFO Size This field indicates the maximal FIFO size, i.e. the DPRAM size: FIFO_MAX_SIZE 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Maximal FIFO Size < 256 bytes < 512 bytes < 1024 bytes < 2048 bytes < 4096 bytes < 8192 bytes < 16384 bytes >= 16384 bytes • BYTE_WRITE_DPRAM: DPRAM Byte-Write Capability This field indicates whether the DPRAM is byte-write capable: BYTE_WRITE_DPRAM 0 1 DPRAM Byte-Write Capability DPRAM byte write lanes have shadow logic implemented in the USB macro IP interface. DPRAM is natively byte-write capable. 549 32058H–AVR32–03/09 AT32UC3A 30.8.1.7 USB IP PB Address Size Register (UADDRSIZE) 0x0820 UADDRSIZE Read-Only 0x00001000 30 29 28 UADDRSIZE r 0 23 0 22 0 21 0 20 UADDRSIZE r 0 15 0 14 0 13 0 12 UADDRSIZE r 0 7 0 6 0 5 1 4 UADDRSIZE r 0 0 0 0 0 0 0 0 0 3 0 2 0 1 0 0 0 11 0 10 0 9 0 8 0 19 0 18 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Read Value: 31 • UADDRSIZE: IP PB Address Size This field indicates the size of the PB address space reserved for the USB macro IP interface (2 at the power of the number of bits reserved to encode the PB addresses of the USB macro IP interface relatively to its base address). 550 32058H–AVR32–03/09 AT32UC3A 30.8.1.8 USB IP Name Register 1 (UNAME1) 0x0824 UNAME1 Read-Only 0x48555342 (“HUSB”) 30 29 28 UNAME1 r “H” 23 22 21 20 UNAME1 r “U” 15 14 13 12 UNAME1 r “S” 7 6 5 4 UNAME1 r “B” 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Offset: Register Name: Access Type: Read Value: 31 • UNAME1: IP Name Part 1 This field indicates the 1st part of the ASCII-encoded name of the USB macro IP. 551 32058H–AVR32–03/09 AT32UC3A 30.8.1.9 USB IP Name Register 2 (UNAME2) 0x0828 UNAME2 Read-Only 0x004F5447 (“\0OTG“) 30 29 28 UNAME2 r “\0“ 23 22 21 20 UNAME2 r “O“ 15 14 13 12 UNAME2 r “T“ 7 6 5 4 UNAME2 r “G“ 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Offset: Register Name: Access Type: Read Value: 31 • UNAME2: IP Name Part 2 This field indicates the 2nd part of the ASCII-encoded name of the USB macro IP. 552 32058H–AVR32–03/09 AT32UC3A 30.8.1.10 USB Finite State Machine Status Register (USBFSM) 0x082C USBFSM Read-Only 0x00000009 30 0 22 0 14 0 6 0 29 0 21 0 13 0 5 0 28 0 20 0 12 0 4 0 27 0 19 0 11 0 3 26 0 18 0 10 0 2 DRDSTATE r 1 0 0 1 25 0 17 0 9 0 1 24 0 16 0 8 0 0 Offset: Register Name: Access Type: Read Value: 31 0 23 0 15 0 7 0 • DRDSTATE This field indicates the state of the USB controller. Refer to the OTG specification for more details. USBFSM 0 1 2 3 4 5 6 7 8 9 10 Description a_idle state : this is the start state for A-devices (when the ID pin is 0) a_wait_vrise : In this state, the A-device waits for the voltage on VBus to rise above the Adevice VBus Valid threshold (4.4 V). a_wait_bcon : In this state, the A-device waits for the B-device to signal a connection. a_host : In this state, the A-device that operates in Host mode is operational. a_suspend : The A-device operating as a host is in the suspend mode. a_peripheral : The A-device operates as a peripheral. a_wait_vfall : In this state, the A-device waits for the voltage on VBus to drop below the Adevice Session Valid threshold (1.4 V). a_vbus_err : In this state, the A-device waits for recovery of the overcurrent condition that caused it to enter this state. a_wait_discharge : In this state, the A-device waits for the data usb line to discharge (100 us). b_idle : this is the start state for B-device (when the ID pin is 1). b_peripheral : In this state, the B-device acts as the peripheral. 553 32058H–AVR32–03/09 AT32UC3A USBFSM 11 12 13 14 15 Description b_wait_begin_hnp : In this state, the B-device is in suspend mode and waits until 3 ms before initiating the HNP protocol if requested. b_wait_discharge : In this state, the B-device waits for the data usb line to discharge (100 us) before becoming Host. b_wait_acon : In this state, the B-device waits for the A-device to signal a connect before becoming B-Host. b_host : In this state, the B-device acts as the Host. b_srp_init : In this state, the B-device attempts to start a session using the SRP protocol. 554 32058H–AVR32–03/09 AT32UC3A 30.8.2 30.8.2.1 USB Device Registers USB Device General Control Register (UDCON) 0x0000 UDCON Read/Write 0x00000100 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 LS rw 0 11 – 10 – 9 RMWKUP rwu 0 8 DETACH rw 1 0 7 ADDEN rwu 0 6 5 4 0 0 0 3 UADD rwu 0 2 1 0 0 0 • UADD: USB Address Set to configure the device address. Cleared by hardware upon receiving a USB reset. • ADDEN: Address Enable Set to activate the UADD field (USB address). Cleared by hardware upon receiving a USB reset. Clearing by software has no effect. • DETACH: Detach Set to physically detach the device (disconnect internal pull-up resistor from D+ and D-). Clear to reconnect the device. • RMWKUP: Remote Wake-Up Set to send an upstream resume to the host for a remote wake-up. Cleared by hardware upon receiving a USB reset or once the upstream resume has been sent. Clearing by software has no effect. • LS: Low-Speed Mode Force Set to force the low-speed mode. 555 32058H–AVR32–03/09 AT32UC3A Clear to unforce the low-speed mode. Then, the full-speed mode is active. Note that this bit can be set/cleared even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset this bit. 556 32058H–AVR32–03/09 AT32UC3A 30.8.2.2 USB Device Global Interrupt Register (UDINT) 0x0004 UDINT Read-Only 0x00000000 30 DMA6INT ru 0 22 – 29 DMA5INT ru 0 21 – 28 DMA4INT ru 0 20 27 DMA3INT ru 0 19 26 DMA2INT ru 0 18 EP6INT ru 0 10 – 25 DMA1INT ru 0 17 EP5INT ru 0 9 – 24 – Offset: Register Name: Access Type: Reset Value: 31 23 – 16 EP4INT ru 0 8 – 15 EP3INT ru 0 7 – 14 EP2INT ru 0 6 UPRSM ru 0 13 EP1INT ru 0 5 EORSM ru 0 12 EP0INT ru 0 4 WAKEUP ru 0 11 – 3 EORST ru 0 2 SOF ru 0 1 – 0 SUSP ru 0 • SUSP: Suspend Interrupt Flag Set by hardware when a USB “Suspend” idle bus state has been detected for 3 frame periods (J state for 3 ms). This triggers a USB interrupt if SUSPE = 1. Shall be cleared by software (by setting the SUSPC bit) to acknowledge the interrupt. Cleared by hardware when a Wake-Up interrupt (WAKEUP) is raised. • SOF: Start of Frame Interrupt Flag Set by hardware when a USB “Start of Frame” PID (SOF) has been detected (every 1 ms). This triggers a USB interrupt if SOFE = 1. The FNUM field is updated. Shall be cleared by software (by setting the SOFC bit) to acknowledge the interrupt. • EORST: End of Reset Interrupt Flag Set by hardware when a USB “End of Reset” has been detected. This triggers a USB interrupt if EORSTE = 1. Shall be cleared by software (by setting the EORSTC bit) to acknowledge the interrupt. • WAKEUP: Wake-Up Interrupt Flag Asynchronous interrupt. Set by hardware when the USB controller is reactivated by a filtered non-idle signal from the lines (not by an upstream resume). This triggers an interrupt if WAKEUPE = 1. Shall be cleared by software (by setting the WAKEUPC bit) to acknowledge the interrupt (USB clock inputs must be enabled before). Cleared by hardware when a Suspend interrupt (SUSP) is raised. 557 32058H–AVR32–03/09 AT32UC3A Note that this interrupt is generated even if the clock is frozen by the FRZCLK bit. • EORSM: End of Resume Interrupt Flag Set by hardware when the USB controller detects a valid “End of Resume” signal initiated by the host. This triggers a USB interrupt if EORSME = 1. Shall be cleared by software (by setting the EORSMC bit) to acknowledge the interrupt. • UPRSM: Upstream Resume Interrupt Flag Set by hardware when the USB controller sends a resume signal called “Upstream Resume”. This triggers a USB interrupt if UPRSME = 1. Shall be cleared by software (by setting the UPRSMC bit) to acknowledge the interrupt (USB clock inputs must be enabled before). • EPXINT, X in [0..6]: Endpoint X Interrupt Flag Set by hardware when an interrupt is triggered by the endpoint X (UESTAX, UECONX). This triggers a USB interrupt if EPXINTE = 1. Cleared by hardware when the interrupt source is serviced. • DMAXINT, X in [1..6]: DMA Channel X Interrupt Flag Set by hardware when an interrupt is triggered by the DMA channel X. This triggers a USB interrupt if DMAXINTE = 1. Cleared by hardware when the UDDMAX_STATUS interrupt source is cleared. 558 32058H–AVR32–03/09 AT32UC3A 30.8.2.3 USB Device Global Interrupt Clear Register (UDINTCLR) 0x0008 UDINTCLR Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 UPRSMC w 0 5 EORSMC w 0 4 WAKEUPC w 0 3 EORSTC w 0 2 SOFC w 0 1 – 0 SUSPC w 0 • SUSPC: Suspend Interrupt Flag Clear Set to clear SUSP. Clearing has no effect. Always read as 0. • SOFC: Start of Frame Interrupt Flag Clear Set to clear SOF. Clearing has no effect. Always read as 0. • EORSTC: End of Reset Interrupt Flag Clear Set to clear EORST. Clearing has no effect. Always read as 0. • WAKEUPC: Wake-Up Interrupt Flag Clear Set to clear WAKEUP. Clearing has no effect. Always read as 0. • EORSMC: End of Resume Interrupt Flag Clear Set to clear EORSM. 559 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • UPRSMC: Upstream Resume Interrupt Flag Clear Set to clear UPRSM. Clearing has no effect. Always read as 0. 560 32058H–AVR32–03/09 AT32UC3A 30.8.2.4 USB Device Global Interrupt Set Register (UDINTSET) 0x000C UDINTSET Write-Only 0x00000000 30 DMA7INTS w 0 22 – 29 DMA5INTS w 0 21 – 28 DMA4INTS w 0 20 – 27 DMA3INTS w 0 19 – 26 DMA2INTS w 0 18 – 25 DMA1INTS w 0 17 – 24 – Offset: Register Name: Access Type: Read Value: 31 23 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 UPRSMS w 0 5 EORSMS w 0 4 WAKEUPS w 0 3 EORSTS w 0 2 SOFS w 0 1 – 0 SUSPS w 0 • SUSPS: Suspend Interrupt Flag Set Set to set SUSP, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • SOFS: Start of Frame Interrupt Flag Set Set to set SOF, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • EORSTS: End of Reset Interrupt Flag Set Set to set EORST, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • WAKEUPS: Wake-Up Interrupt Flag Set Set to set WAKEUP, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • EORSMS: End of Resume Interrupt Flag Set Set to set EORSM, what may be useful for test or debug purposes. 561 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • UPRSMS: Upstream Resume Interrupt Flag Set Set to set UPRSM, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • DMAXINTS, X in [1..6]: DMA Channel X Interrupt Flag Set Set to set DMAXINT, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. 562 32058H–AVR32–03/09 AT32UC3A 30.8.2.5 USB Device Global Interrupt Enable Register (UDINTE) 0x0010 UDINTE Read-Only 0x00000000 30 DMA6INTE r 0 22 – 29 DMA5INTE r 0 21 – 28 DMA4INTE r 0 20 27 DMA3INTE r 0 19 26 DMA2INTE r 0 18 EP6INTE r 0 10 – 25 DMA1INTE r 0 17 EP5INTE r 0 9 – 24 – Offset: Register Name: Access Type: Reset Value: 31 23 – 16 EP4INTE r 0 8 – 15 EP3INTE r 0 7 – 14 EP2INTE r 0 6 UPRSME r 0 13 EP1INTE r 0 5 EORSME r 0 12 EP0INTE r 0 4 WAKEUPE r 0 11 – 3 EORSTE r 0 2 SOFE r 0 1 – 0 SUSPE r 0 • SUSPE: Suspend Interrupt Enable Set by software (by setting the SUSPES bit) to enable the Suspend interrupt (SUSP). Clear by software (by setting the SUSPEC bit) to disable the Suspend interrupt (SUSP). • SOFE: Start of Frame Interrupt Enable Set by software (by setting the SOFES bit) to enable the Start of Frame interrupt (SOF). Clear by software (by setting the SOFEC bit) to disable the Start of Frame interrupt (SOF). • EORSTE: End of Reset Interrupt Enable Set by software (by setting the EORSTES bit) to enable the End of Reset interrupt (EORST). Clear by software (by setting the EORSTEC bit) to disable the End of Reset interrupt (EORST). • WAKEUPE: Wake-Up Interrupt Enable Set by software (by setting the WAKEUPES bit) to enable the Wake-Up interrupt (WAKEUP). Clear by software (by setting the WAKEUPEC bit) to disable the Wake-Up interrupt (WAKEUP). • EORSME: End of Resume Interrupt Enable Set by software (by setting the EORSMES bit) to enable the End of Resume interrupt (EORSM). Clear by software (by setting the EORSMEC bit) to disable the End of Resume interrupt (EORSM). • UPRSME: Upstream Resume Interrupt Enable Set by software (by setting the UPRSMES bit) to enable the Upstream Resume interrupt (UPRSM). Clear by software (by setting the UPRSMEC bit) to disable the Upstream Resume interrupt (UPRSM). 563 32058H–AVR32–03/09 AT32UC3A • EPXINTE, X in [0..6]: Endpoint X Interrupt Enable Set by software (by setting the EPXINTES bit) to enable the Endpoint X interrupt (EPXINT). Clear by software (by setting the EPXINTEC bit) to disable the Endpoint X interrupt (EPXINT). • DMAXINTE, X in [1..6]: DMA Channel X Interrupt Enable Set by software (by setting the DMAXINTES bit) to enable the DMA Channel X interrupt (DMAXINT). Clear by software (by setting the DMAXINTEC bit) to disable the DMA Channel X interrupt (DMAXINT). 564 32058H–AVR32–03/09 AT32UC3A 30.8.2.6 USB Device Global Interrupt Enable Clear Register (UDINTECLR) 0x0014 UDINTECLR Write-Only 0x00000000 30 DMA6INTEC w 0 22 – 29 DMA5INTEC w 0 21 – 28 DMA4INTEC w 0 20 – 27 DMA3INTEC w 0 19 – 26 DMA2INTEC w 0 18 EP6INTEC w 0 10 – 25 DMA1INTEC w 0 17 EP5INTEC w 0 9 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 16 EP4INTEC w 0 8 – 15 EP3INTEC w 0 7 – 14 EP2INTEC w 0 6 UPRSMEC w 0 13 EP1INTEC w 0 5 EORSMEC w 0 12 EP0INTEC w 0 4 WAKEUPEC w 0 11 – 3 EORSTEC w 0 2 SOFEC w 0 1 – 0 SUSPEC w 0 • SUSPEC: Suspend Interrupt Enable Clear Set to clear SUSPE. Clearing has no effect. Always read as 0. • SOFEC: Start of Frame Interrupt Enable Clear Set to clear SOFE. Clearing has no effect. Always read as 0. • EORSTEC: End of Reset Interrupt Enable Clear Set to clear EORSTE. Clearing has no effect. Always read as 0. • WAKEUPEC: Wake-Up Interrupt Enable Clear Set to clear WAKEUPE. Clearing has no effect. Always read as 0. • EORSMEC: End of Resume Interrupt Enable Clear Set to clear EORSME. 565 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • UPRSMEC: Upstream Resume Interrupt Enable Clear Set to clear UPRSME. Clearing has no effect. Always read as 0. • EPXINTEC, X in [0..6]: Endpoint X Interrupt Enable Clear Set to clear EPXINTE. Clearing has no effect. Always read as 0. • DMAXINTEC, X in [1..6]: DMA Channel X Interrupt Enable Clear Set to clear DMAXINTE. Clearing has no effect. Always read as 0. 566 32058H–AVR32–03/09 AT32UC3A 30.8.2.7 USB Device Global Interrupt Enable Set Register (UDINTESET) 0x0018 UDINTESET Write-Only 0x00000000 30 DMA6INTES w 0 22 – 29 DMA5INTES w 0 21 – 28 DMA4INTES w 0 20 – 27 DMA3INTES w 0 19 – 26 DMA2INTES w 0 18 EP6INTES w 0 10 – 25 DMA1INTES w 0 17 EP5INTES w 0 9 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 16 EP4INTES w 0 8 – 15 EP3INTES w 0 7 – 14 EP2INTES w 0 6 UPRSMES w 0 13 EP1INTES w 0 5 EORSMES w 0 12 EP0INTES w 0 4 WAKEUPES w 0 11 – 3 EORSTES w 0 2 SOFES w 0 1 – 0 SUSPES w 0 • SUSPES: Suspend Interrupt Enable Set Set to set SUSPE. Clearing has no effect. Always read as 0. • SOFES: Start of Frame Interrupt Enable Set Set to set SOFE. Clearing has no effect. Always read as 0. • EORSTES: End of Reset Interrupt Enable Set Set to set EORSTE. Clearing has no effect. Always read as 0. • WAKEUPES: Wake-Up Interrupt Enable Set Set to set WAKEUPE. Clearing has no effect. Always read as 0. • EORSMES: End of Resume Interrupt Enable Set Set to set EORSME. 567 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • UPRSMES: Upstream Resume Interrupt Enable Set Set to set UPRSME. Clearing has no effect. Always read as 0. • EPXINTES, X in [0..6]: Endpoint X Interrupt Enable Set Set to set EPXINTE. Clearing has no effect. Always read as 0. • DMAXINTES, X in [1..6]: DMA Channel X Interrupt Enable Set Set to set DMAXINTE. Clearing has no effect. Always read as 0. 568 32058H–AVR32–03/09 AT32UC3A 30.8.2.8 USB Device Frame Number Register (UDFNUM) 0x0020 UDFNUM Read-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 FNCERR ru 0 7 14 – 13 12 11 FNUM ru 10 9 8 0 6 5 FNUM ru 0 0 4 0 3 0 2 – 0 1 – 0 0 – 0 0 0 0 • FNUM: Frame Number Set by hardware. These bits are the 11-bit frame number information. They are provided in the last received SOF packet. Cleared by hardware upon receiving a USB reset. Note that FNUM is updated even if a corrupted SOF is received. • FNCERR: Frame Number CRC Error Set by hardware when a corrupted frame number is received. This bit and the SOF interrupt flag are updated at the same time. Cleared by hardware upon receiving a USB reset. 569 32058H–AVR32–03/09 AT32UC3A 30.8.2.9 USB Endpoint Enable/Reset Register (UERST) 0x001C UERST Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 EPRST6 rwu 0 14 – 21 EPRST5 rwu 0 13 – 20 EPRST4 rwu 0 12 – 19 EPRST3 rwu 0 11 – 18 EPRST2 rwu 0 10 – 17 EPRST1 rwu 0 9 – 16 EPRST0 rwu 0 8 – 15 – 7 – 6 EPEN6 rw 0 5 EPEN5 rw 0 4 EPEN4 rw 0 3 EPEN3 rw 0 2 EPEN2 rw 0 1 EPEN1 rw 0 0 EPEN0 rw 0 • EPENX, X in [0..6]: Endpoint X Enable Set to enable the endpoint X. Clear to disable the endpoint X, what forces the endpoint X state to inactive (no answer to USB requests) and resets the endpoint X registers (UECFGX, UESTAX, UECONX) but not the endpoint configuration (ALLOC, EPBK, EPSIZE, EPDIR, EPTYPE). • EPRSTX, X in [0..6]: Endpoint X Reset Set by software to reset the endpoint X FIFO prior to any other operation, upon hardware reset or when a USB bus reset has been received. This resets the endpoint X registers (UECFGX, UESTAX, UECONX) but not the endpoint configuration (ALLOC, EPBK, EPSIZE, EPDIR, EPTYPE). All the endpoint mechanism (FIFO counter, reception, transmission, etc.) is reset apart from the Data Toggle Sequence field (DTSEQ) which can be cleared by setting the RSTDT bit (by setting the RSTDTS bit). The endpoint configuration remains active and the endpoint is still enabled. Then, clear by software to complete the reset operation and to start using the FIFO. Cleared by hardware upon receiving a USB reset. 570 32058H–AVR32–03/09 AT32UC3A 30.8.2.10 USB Endpoint X Configuration Register (UECFGX) 0x0100 + X . 0x04 UECFGX, X in [0..6] Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 EPTYPE rwu 0 11 10 – 0 3 EPBK rwu 2 9 AUTOSW rwu 0 1 ALLOC rwu 0 8 EPDIR rwu 0 0 – 7 – 6 0 5 EPSIZE rwu 0 4 0 0 0 • ALLOC: Endpoint Memory Allocate Set to allocate the endpoint memory. Clear to free the endpoint memory. Cleared by hardware upon receiving a USB reset (except for the endpoint 0). Note that after setting this bit, the user should check the CFGOK bit to know whether the allocation of this endpoint is correct. • EPBK: Endpoint Banks Set to select the number of banks for the endpoint: EPBK 0 0 1 1 0 1 0 1 Endpoint Banks 1 (single-bank endpoint) 2 (double-bank endpoint) 3 (triple-bank endpoint) Reserved For control endpoints, a single-bank endpoint (00b) should be selected. Cleared by hardware upon receiving a USB reset (except for the endpoint 0). 571 32058H–AVR32–03/09 AT32UC3A • EPSIZE: Endpoint Size Set to select the size of each endpoint bank: EPSIZE 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Endpoint Size 8 bytes 16 bytes 32 bytes 64 bytes 128 bytes 256 bytes 512 bytes 1024 bytes Cleared by hardware upon receiving a USB reset (except for the endpoint 0). • EPDIR: Endpoint Direction Set to select the endpoint direction: EPDIR 0 1 Endpoint Direction OUT IN (not for control endpoints) Cleared by hardware upon receiving a USB reset. • AUTOSW: Automatic Switch Set to automatically switch bank when it is ready. Clear to disable the automatic bank switching. Cleared by hardware upon receiving a USB reset. • EPTYPE: Endpoint Type Set to select the endpoint type: EPTYPE 0 0 1 1 0 1 0 1 Endpoint Type Control Isochronous Bulk Interrupt Cleared by hardware upon receiving a USB reset. 572 32058H–AVR32–03/09 AT32UC3A 30.8.2.11 USB Endpoint X Status Register (UESTAX) 0x0130 + X . 0x04 UESTAX, X in [0..6] Read-Only 0x00000100 30 29 28 27 BYCT ru 0 19 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 – 0 23 22 BYCT ru 0 15 CURRBK ru 0 7 SHORT PACKET ru 0 0 6 STALLEDI/ CRCERRI ru 0 0 14 0 21 0 20 0 18 CFGOK ru 0 10 – 0 17 CTRLDIR ru 0 9 DTSEQ ru 0 0 16 RWALL ru 0 8 0 13 NBUSYBK ru 0 5 OVERFI ru 0 0 12 11 – 0 4 NAKINI ru 0 3 NAKOUTI ru 0 2 RXSTPI/ UNDERFI ru 0 1 0 TXINI ru 0 1 RXOUTI ru 0 • TXINI: Transmitted IN Data Interrupt Flag For control endpoints: Set by hardware when the current bank is ready to accept a new IN packet. This triggers an EPXINT interrupt if TXINE = 1. Shall be cleared by software (by setting the TXINIC bit) to acknowledge the interrupt and to send the packet. For isochronous, bulk and interrupt IN endpoints: Set by hardware at the same time as FIFOCON when the current bank is free. This triggers an EPXINT interrupt if TXINE = 1. Shall be cleared by software (by setting the TXINIC bit) to acknowledge the interrupt, what has no effect on the endpoint FIFO. The software then writes into the FIFO and clears the FIFOCON bit to allow the USB controller to send the data. If the IN endpoint is composed of multiple banks, this also switches to the next bank. The TXINI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. TXINI shall always be cleared before clearing FIFOCON. This bit is inactive (cleared) for isochronous, bulk and interrupt OUT endpoints. • RXOUTI: Received OUT Data Interrupt Flag For control endpoints: Set by hardware when the current bank contains a bulk OUT packet (data or status stage). This triggers an EPXINT interrupt if RXOUTE = 1. 573 32058H–AVR32–03/09 AT32UC3A Shall be cleared by software (by setting the RXOUTIC bit) to acknowledge the interrupt and to free the bank. For isochronous, bulk and interrupt OUT endpoints: Set by hardware at the same time as FIFOCON when the current bank is full. This triggers an EPXINT interrupt if RXOUTE = 1. Shall be cleared by software (by setting the RXOUTIC bit) to acknowledge the interrupt, what has no effect on the endpoint FIFO. The software then reads from the FIFO and clears the FIFOCON bit to free the bank. If the OUT endpoint is composed of multiple banks, this also switches to the next bank. The RXOUTI and FIFOCON bits are updated by hardware in accordance with the status of the next bank. RXOUTI shall always be cleared before clearing FIFOCON. This bit is inactive (cleared) for isochronous, bulk and interrupt IN endpoints. • RXSTPI: Received SETUP Interrupt Flag For control endpoints, set by hardware to signal that the current bank contains a new valid SETUP packet. This triggers an EPXINT interrupt if RXSTPE = 1. Shall be cleared by software (by setting the RXSTPIC bit) to acknowledge the interrupt and to free the bank. This bit is inactive (cleared) for bulk and interrupt IN/OUT endpoints and it means UNDERFI for isochronous IN/OUT endpoints. • UNDERFI: Underflow Interrupt Flag For isochronous IN/OUT endpoints, set by hardware when an underflow error occurs. This triggers an EPXINT interrupt if UNDERFE = 1. An underflow can occur during IN stage if the host attempts to read from an empty bank. A zero-length packet is then automatically sent by the USB controller. An underflow can also occur during OUT stage if the host sends a packet while the bank is already full. Typically, the CPU is not fast enough. The packet is lost. Shall be cleared by software (by setting the UNDERFIC bit) to acknowledge the interrupt. This bit is inactive (cleared) for bulk and interrupt IN/OUT endpoints and it means RXSTPI for control endpoints. • NAKOUTI: NAKed OUT Interrupt Flag Set by hardware when a NAK handshake has been sent in response to an OUT request from the host. This triggers an EPXINT interrupt if NAKOUTE = 1. Shall be cleared by software (by setting the NAKOUTIC bit) to acknowledge the interrupt. • NAKINI: NAKed IN Interrupt Flag Set by hardware when a NAK handshake has been sent in response to an IN request from the host. This triggers an EPXINT interrupt if NAKINE = 1. Shall be cleared by software (by setting the NAKINIC bit) to acknowledge the interrupt. • OVERFI: Overflow Interrupt Flag Set by hardware when an overflow error occurs. This triggers an EPXINT interrupt if OVERFE = 1. For all endpoint types, an overflow can occur during OUT stage if the host attempts to write into a bank that is too small for the packet. The packet is acknowledged and the Received OUT Data interrupt (RXOUTI) is raised as if no overflow had occurred. The bank is filled with all the first bytes of the packet that fit in. 574 32058H–AVR32–03/09 AT32UC3A Shall be cleared by software (by setting the OVERFIC bit) to acknowledge the interrupt. • STALLEDI: STALLed Interrupt Flag Set by hardware to signal that a STALL handshake has been sent. To do that, the software has to set the STALLRQ bit (by setting the STALLRQS bit). This triggers an EPXINT interrupt if STALLEDE = 1. Shall be cleared by software (by setting the STALLEDIC bit) to acknowledge the interrupt. • CRCERRI: CRC Error Interrupt Flag Set by hardware to signal that a CRC error has been detected in an isochronous OUT endpoint. The OUT packet is stored in the bank as if no CRC error had occurred. This triggers an EPXINT interrupt if CRCERRE = 1. Shall be cleared by software (by setting the CRCERRIC bit) to acknowledge the interrupt. • SHORTPACKET: Short Packet Interrupt Flag For non-control OUT endpoints, set by hardware when a short packet has been received. For non-control IN endpoints, set by hardware when a short packet is transmitted upon ending a DMA transfer, thus signaling an end of isochronous frame or a bulk or interrupt end of transfer, this only if the End of DMA Buffer Output Enable bit (DMAEND_EN) and the Automatic Switch bit (AUTOSW) are set. This triggers an EPXINT interrupt if SHORTPACKETE = 1. Shall be cleared by software (by setting the SHORTPACKETC bit) to acknowledge the interrupt. • DTSEQ: Data Toggle Sequence Set by hardware to indicate the PID of the current bank: DTSEQ 0 0 1 0 1 X Data Toggle Sequence Data0 Data1 Reserved For IN transfers, it indicates the data toggle sequence that will be used for the next packet to be sent. This is not relative to the current bank. For OUT transfers, this value indicates the last data toggle sequence received on the current bank. Note that by default DTSEQ = 01b, as if the last data toggle sequence was Data1, so the next sent or expected data toggle sequence should be Data0. • NBUSYBK: Number of Busy Banks Set by hardware to indicate the number of busy banks: NBUSYBK 0 0 1 1 0 1 0 1 Number of Busy Banks 0 (all banks free) 1 2 3 For IN endpoints, it indicates the number of banks filled by the user and ready for IN transfer. When all banks are free, this triggers an EPXINT interrupt if NBUSYBKE = 1. 575 32058H–AVR32–03/09 AT32UC3A For OUT endpoints, it indicates the number of banks filled by OUT transactions from the host. When all banks are busy, this triggers an EPXINT interrupt if NBUSYBKE = 1. Note that when the FIFOCON bit is cleared (by setting the FIFOCONC bit) to validate a new bank, this field is updated 2 or 3 clock cycles later to calculate the address of the next bank. An EPXINT interrupt is triggered if : - for IN endpoint, NBUSYBKE=1 and all the banks are free. - for OUT endpoint, NBUSYBKE=1 and all the banks are busy. • CURRBK: Current Bank For non-control endpoints, set by hardware to indicate the current bank: CURRBK 0 0 1 1 0 1 0 1 Current Bank Bank0 Bank1 Bank2 Reserved Note that this field may be updated 1 clock cycle after the RWALL bit changes, so the user should not poll this field as an interrupt flag. • RWALL: Read/Write Allowed For IN endpoints, set by hardware when the current bank is not full, i.e. the software can write further data into the FIFO. For OUT endpoints, set by hardware when the current bank is not empty, i.e. the software can read further data from the FIFO. Never set if STALLRQ = 1 or in case of error. Cleared by hardware otherwise. This bit shall not be used for control endpoints. • CTRLDIR: Control Direction Set by hardware after a SETUP packet to indicate the direction of the following packet: CTRLDIR 0 1 Control Direction OUT IN Can not be set or cleared by software. • CFGOK: Configuration OK Status This bit is updated when the ALLOC bit is set. Set by hardware if the endpoint X number of banks (EPBK) and size (EPSIZE) are correct compared to the maximal allowed number of banks and size for this endpoint and to the maximal FIFO size (i.e. the DPRAM size). If this bit is cleared by hardware, the user should reprogram the UECFGX register with correct EPBK and EPSIZE values. • BYCT: Byte Count Set by the hardware to indicate the byte count of the FIFO. 576 32058H–AVR32–03/09 AT32UC3A For IN endpoints, incremented after each byte written by the software into the endpoint and decremented after each byte sent to the host. For OUT endpoints, incremented after each byte received from the host and decremented after each byte read by the software from the endpoint. Note that this field may be updated 1 clock cycle after the RWALL bit changes, so the user should not poll this field as an interrupt flag. 577 32058H–AVR32–03/09 AT32UC3A 30.8.2.12 USB Endpoint X Status Clear Register (UESTAXCLR) 0x0160 + X . 0x04 UESTAXCLR, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 SHORT PACKETC w 0 6 STALLEDIC/ CRCERRIC w 0 5 OVERFIC w 0 4 NAKINIC w 0 3 NAKOUTIC w 0 2 RXSTPIC/ UNDERFIC w 0 1 RXOUTIC w 0 0 TXINIC w 0 • TXINIC: Transmitted IN Data Interrupt Flag Clear Set to clear TXINI. Clearing has no effect. Always read as 0. • RXOUTIC: Received OUT Data Interrupt Flag Clear Set to clear RXOUTI. Clearing has no effect. Always read as 0. • RXSTPIC: Received SETUP Interrupt Flag Clear Set to clear RXSTPI. Clearing has no effect. Always read as 0. • UNDERFIC: Underflow Interrupt Flag Clear Set to clear UNDERFI. Clearing has no effect. Always read as 0. • NAKOUTIC: NAKed OUT Interrupt Flag Clear Set to clear NAKOUTI. 578 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKINIC: NAKed IN Interrupt Flag Clear Set to clear NAKINI. Clearing has no effect. Always read as 0. • OVERFIC: Overflow Interrupt Flag Clear Set to clear OVERFI. Clearing has no effect. Always read as 0. • STALLEDIC: STALLed Interrupt Flag Clear Set to clear STALLEDI. Clearing has no effect. Always read as 0. • CRCERRIC: CRC Error Interrupt Flag Clear Set to clear CRCERRI. Clearing has no effect. Always read as 0. • SHORTPACKETC: Short Packet Interrupt Flag Clear Set to clear SHORTPACKET. Clearing has no effect. Always read as 0. 579 32058H–AVR32–03/09 AT32UC3A 30.8.2.13 USB Endpoint X Status Set Register (UESTAXSET) 0x0190 + X . 0x04 UESTAXSET, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 NBUSYBKS w 0 4 NAKINIS w 0 11 – 10 – 9 8 – 7 SHORT PACKETS w 0 6 STALLEDIS/ CRCERRIS w 0 5 OVERFIS w 0 3 NAKOUTIS w 0 2 RXSTPIS/ UNDERFIS w 0 1 RXOUTIS w 0 0 TXINIS w 0 • TXINIS: Transmitted IN Data Interrupt Flag Set Set to set TXINI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RXOUTIS: Received OUT Data Interrupt Flag Set Set to set RXOUTI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RXSTPIS: Received SETUP Interrupt Flag Set Set to set RXSTPI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • UNDERFIS: Underflow Interrupt Flag Set Set to set UNDERFI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • NAKOUTIS: NAKed OUT Interrupt Flag Set Set to set NAKOUTI, what may be useful for test or debug purposes. 580 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKINIS: NAKed IN Interrupt Flag Set Set to set NAKINI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • OVERFIS: Overflow Interrupt Flag Set Set to set OVERFI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • STALLEDIS: STALLed Interrupt Flag Set Set to set STALLEDI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • CRCERRIS: CRC Error Interrupt Flag Set Set to set CRCERRI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • SHORTPACKETS: Short Packet Interrupt Flag Set Set to set SHORTPACKET, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • NBUSYBKS: Number of Busy Banks Interrupt Flag Set Set to force the Number of Busy Banks interrupt flag (NBUSYBK), what may be useful for test or debug purposes. Set again to unforce the Number of Busy Banks interrupt flag (NBUSYBK). Clearing has no effect. Always read as 0. 581 32058H–AVR32–03/09 AT32UC3A 30.8.2.14 USB Endpoint X Control Register (UECONX) 0x01C0 + X . 0x04 UECONX, X in [0..6] Read-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 STALLRQ ru 0 11 – 18 RSTDT ru 0 10 – 17 – 16 EPDISHDMA r 0 8 – 15 – 14 FIFOCON ru 0 6 STALLEDE/ CRCERRE r 0 13 KILLBK ru 0 5 OVERFE r 0 12 NBUSYBKE r 0 4 NAKINE r 0 9 – 7 SHORT PACKETE r 0 3 NAKOUTE r 0 2 RXSTPE/ UNDERFE r 0 1 RXOUTE r 0 0 TXINE r 0 • TXINE: Transmitted IN Data Interrupt Enable Set by software (by setting the TXINES bit) to enable the Transmitted IN Data interrupt (TXINI). Clear by software (by setting the TXINEC bit) to disable the Transmitted IN Data interrupt (TXINI). • RXOUTE: Received OUT Data Interrupt Enable Set by software (by setting the RXOUTES bit) to enable the Received OUT Data interrupt (RXOUT). Clear by software (by setting the RXOUTEC bit) to disable the Received OUT Data interrupt (RXOUT). • RXSTPE: Received SETUP Interrupt Enable Set by software (by setting the RXSTPES bit) to enable the Received SETUP interrupt (RXSTPI). Clear by software (by setting the RXSTPEC bit) to disable the Received SETUP interrupt (RXSTPI). • UNDERFE: Underflow Interrupt Enable Set by software (by setting the UNDERFES bit) to enable the Underflow interrupt (UNDERFI). Clear by software (by setting the UNDERFEC bit) to disable the Underflow interrupt (UNDERFI). • NAKOUTE: NAKed OUT Interrupt Enable Set by software (by setting the NAKOUTES bit) to enable the NAKed OUT interrupt (NAKOUTI). Clear by software (by setting the NAKOUTEC bit) to disable the NAKed OUT interrupt (NAKOUTI). • NAKINE: NAKed IN Interrupt Enable Set by software (by setting the NAKINES bit) to enable the NAKed IN interrupt (NAKINI). Clear by software (by setting the NAKINEC bit) to disable the NAKed IN interrupt (NAKINI). 582 32058H–AVR32–03/09 AT32UC3A • OVERFE: Overflow Interrupt Enable Set by software (by setting the OVERFES bit) to enable the Overflow interrupt (OVERFI). Clear by software (by setting the OVERFEC bit) to disable the Overflow interrupt (OVERFI). • STALLEDE: STALLed Interrupt Enable Set by software (by setting the STALLEDES bit) to enable the STALLed interrupt (STALLEDI). Clear by software (by setting the STALLEDEC bit) to disable the STALLed interrupt (STALLEDI). • CRCERRE: CRC Error Interrupt Enable Set by software (by setting the CRCERRES bit) to enable the CRC Error interrupt (CRCERRI). Clear by software (by setting the CRCERREC bit) to disable the CRC Error interrupt (CRCERRI). • SHORTPACKETE: Short Packet Interrupt Enable Set by software (by setting the SHORTPACKETES bit) to enable the Short Packet interrupt (SHORTPACKET). Clear by software (by setting the SHORTPACKETEC bit) to disable the Short Packet interrupt (SHORTPACKET). • NBUSYBKE: Number of Busy Banks Interrupt Enable Set by software (by setting the NBUSYBKES bit) to enable the Number of Busy Banks interrupt (NBUSYBK). Clear by software (by setting the NBUSYBKEC bit) to disable the Number of Busy Banks interrupt (NBUSYBK). • KILLBK: Kill IN Bank Set by software (by setting the KILLBKS bit) to kill the last written bank. Cleared by hardware when the bank is killed. Caution: The bank is really cleared when the “kill packet” procedure is accepted by the USB macro core. This bit is automatically cleared after the end of the procedure: – The bank is really cleared or the bank is sent (IN transfer): NBUSYBK is decremented. – The bank is not cleared but sent (IN transfer): NBUSYBK is decremented. – The bank is not cleared because it was empty. The software shall wait for this bit to be cleared before trying to kill another packet. Note that this kill request is refused if at the same time an IN token is coming and the last bank is the current one being sent on the USB line. If at least 2 banks are ready to be sent, there is no problem to kill a packet even if an IN token is coming. Indeed, in this case, the current bank is sent (IN transfer) while the last bank is killed. • FIFOCON: FIFO Control For control endpoints: The FIFOCON and RWALL bits are irrelevant. The software shall therefore never use them on these endpoints. When read, their value is always 0. For IN endpoints: Set by hardware when the current bank is free, at the same time as TXINI. Clear by software (by setting the FIFOCONC bit) to send the FIFO data and to switch to the next bank. For OUT endpoints: Set by hardware when the current bank is full, at the same time as RXOUTI. 583 32058H–AVR32–03/09 AT32UC3A Clear by software (by setting the FIFOCONC bit) to free the current bank and to switch to the next bank. • EPDISHDMA: Endpoint Interrupts Disable HDMA Request Enable Set by software (by setting the EPDISHDMAS bit) to pause the on-going DMA channel X transfer on any Endpoint X interrupt (EPXINT), whatever the state of the Endpoint X Interrupt Enable bit (EPXINTE). The software then has to acknowledge or to disable the interrupt source (e.g. RXOUTI) or to clear the EPDISHDMA bit (by setting the EPDISHDMAC bit) in order to complete the DMA transfer. In ping-pong mode, if the interrupt is associated to a new system-bank packet (e.g. Bank1) and the current DMA transfer is running on the previous packet (Bank0), then the previous-packet DMA transfer completes normally, but the new-packet DMA transfer will not start (not requested). If the interrupt is not associated to a new system-bank packet (NAKINI, NAKOUTI, etc.), then the request cancellation may occur at any time and may immediately pause the current DMA transfer. This may be used for example to identify erroneous packets, to prevent them from being transferred into a buffer, to complete a DMA transfer by software after reception of a short packet, etc. • RSTDT: Reset Data Toggle Set by software (by setting the RSTDTS bit) to clear the data toggle sequence, i.e. to set to Data0 the data toggle sequence of the next sent (IN endpoints) or received (OUT endpoints) packet. Cleared by hardware instantaneously. The software does not have to wait for this bit to be cleared. • STALLRQ: STALL Request Set by software (by setting the STALLRQS bit) to request to send a STALL handshake to the host. Cleared by hardware when a new SETUP packet is received. Can also be cleared by software by setting the STALLRQC bit. 584 32058H–AVR32–03/09 AT32UC3A 30.8.2.15 USB Endpoint X Control Clear Register (UECONXCLR) 0x0220 + X . 0x04 UECONXCLR, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 STALLRQC w 0 11 – 18 – 17 – 16 EPDISHDMAC w 0 8 – 15 – 14 FIFOCONC w 0 6 STALLEDEC/ CRCERREC w 0 13 – 12 NBUSYBKEC w 0 4 NAKINEC w 0 10 – 9 – 7 SHORT PACKETEC w 0 5 OVERFEC w 0 3 NAKOUTEC w 0 2 RXSTPEC/ UNDERFEC w 0 1 RXOUTEC w 0 0 TXINEC w 0 • TXINEC: Transmitted IN Data Interrupt Enable Clear Set to clear TXINE. Clearing has no effect. Always read as 0. • RXOUTEC: Received OUT Data Interrupt Enable Clear Set to clear RXOUTE. Clearing has no effect. Always read as 0. • RXSTPEC: Received SETUP Interrupt Enable Clear Set to clear RXSTPE. Clearing has no effect. Always read as 0. • UNDERFEC: Underflow Interrupt Enable Clear Set to clear UNDERFE. Clearing has no effect. Always read as 0. • NAKOUTEC: NAKed OUT Interrupt Enable Clear Set to clear NAKOUTE. 585 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKINEC: NAKed IN Interrupt Enable Clear Set to clear NAKINE. Clearing has no effect. Always read as 0. • OVERFEC: Overflow Interrupt Enable Clear Set to clear OVERFE. Clearing has no effect. Always read as 0. • STALLEDEC: STALLed Interrupt Enable Clear Set to clear STALLEDE. Clearing has no effect. Always read as 0. • CRCERREC: CRC Error Interrupt Enable Clear Set to clear CRCERRE. Clearing has no effect. Always read as 0. • SHORTPACKETEC: Short Packet Interrupt Enable Clear Set to clear SHORTPACKETE. Clearing has no effect. Always read as 0. • NBUSYBKEC: Number of Busy Banks Interrupt Enable Clear Set to clear NBUSYBKE. Clearing has no effect. Always read as 0. • FIFOCONC: FIFO Control Clear Set to clear FIFOCON. Clearing has no effect. Always read as 0. • EPDISHDMAC: Endpoint Interrupts Disable HDMA Request Enable Clear Set to clear EPDISHDMA. Clearing has no effect. Always read as 0. 586 32058H–AVR32–03/09 AT32UC3A • STALLRQC: STALL Request Clear Set to clear STALLRQ. Clearing has no effect. Always read as 0. 587 32058H–AVR32–03/09 AT32UC3A 30.8.2.16 USB Endpoint X Control Set Register (UECONXSET) 0x01F0 + X . 0x04 UECONXSET, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 STALLRQS w 0 11 – 18 RSTDTS 17 – 16 EPDISHDMAS w 0 8 – 15 – 14 – w 0 6 STALLEDES/ CRCERRES w 0 13 KILLBKS 12 NBUSYBKES w 0 4 NAKINES w 0 10 – 9 – 7 SHORT PACKETES w 0 5 OVERFES w 0 3 NAKOUTES w 0 2 RXSTPES/ UNDERFES w 0 1 RXOUTES w 0 0 TXINES w 0 • TXINES: Transmitted IN Data Interrupt Enable Set Set to set TXINE. Clearing has no effect. Always read as 0. • RXOUTES: Received OUT Data Interrupt Enable Set Set to set RXOUTE. Clearing has no effect. Always read as 0. • RXSTPES: Received SETUP Interrupt Enable Set Set to set RXSTPE. Clearing has no effect. Always read as 0. • UNDERFES: Underflow Interrupt Enable Set Set to set UNDERFE. Clearing has no effect. Always read as 0. • NAKOUTES: NAKed OUT Interrupt Enable Set Set to set NAKOUTE. 588 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKINES: NAKed IN Interrupt Enable Set Set to set NAKINE. Clearing has no effect. Always read as 0. • OVERFES: Overflow Interrupt Enable Set Set to set OVERFE. Clearing has no effect. Always read as 0. • STALLEDES: STALLed Interrupt Enable Set Set to set STALLEDE. Clearing has no effect. Always read as 0. • CRCERRES: CRC Error Interrupt Enable Set Set to set CRCERRE. Clearing has no effect. Always read as 0. • SHORTPACKETES: Short Packet Interrupt Enable Set Set to set SHORTPACKETE. Clearing has no effect. Always read as 0. • NBUSYBKES: Number of Busy Banks Interrupt Enable Set Set to set NBUSYBKE. Clearing has no effect. Always read as 0. • KILLBKS: Kill IN Bank Set Set to set KILLBK. Clearing has no effect. Always read as 0. • EPDISHDMAS: Endpoint Interrupts Disable HDMA Request Enable Set Set to set EPDISHDMA. Clearing has no effect. 589 32058H–AVR32–03/09 AT32UC3A Always read as 0. • RSTDTS: Reset Data Toggle Set Set to set RSTDT. Clearing has no effect. Always read as 0. • STALLRQS: STALL Request Set Set to set STALLRQ. Clearing has no effect. Always read as 0. 590 32058H–AVR32–03/09 AT32UC3A 30.8.2.17 USB Device DMA Channel X Next Descriptor Address Register (UDDMAX_NEXTDESC) 0x0310 + (X - 1) . 0x10 UDDMAX_NEXTDESC, X in [1..6] Read/Write 0x00000000 30 29 28 27 NXT_DESC_ADDR rwu 0 0 20 19 NXT_DESC_ADDR rwu 0 0 12 11 NXT_DESC_ADDR rwu 0 0 4 3 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 0 23 0 22 0 21 0 18 0 17 0 16 0 15 0 14 0 13 0 10 0 9 0 8 0 7 0 0 0 2 – 0 1 – 0 0 – 0 6 5 NXT_DESC_ADDR rwu 0 0 0 • NXT_DESC_ADDR: Next Descriptor Address This field contains the bits 31:4 of the 16-byte aligned address of the next channel descriptor to be processed. Note that this field is written either by software or by descriptor loading. 591 32058H–AVR32–03/09 AT32UC3A 30.8.2.18 USB Device DMA Channel X HSB Address Register (UDDMAX_ADDR) 0x0314 + (X - 1) . 0x10 UDDMAX_ADDR, X in [1..6] Read/Write 0x00000000 30 29 28 HSB_ADDR rwu 0 23 0 22 0 21 0 20 HSB_ADDR rwu 0 15 0 14 0 13 0 12 HSB_ADDR rwu 0 7 0 6 0 5 0 4 HSB_ADDR rwu 0 0 0 0 0 0 0 0 0 3 0 2 0 1 0 0 0 11 0 10 0 9 0 8 0 19 0 18 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 • HSB_ADDR: HSB Address This field determines the HSB bus current address of a channel transfer. The address set on the HSB address bus is HSB_ADDR rounded down to the nearest word-aligned address, i.e. HSB_ADDR[1:0] is considered as 00b since only word accesses are performed. Channel HSB start and end addresses may be aligned on any byte boundary. The software may write this field only when the Channel Enabled bit (CH_EN) of the UDDMAX_STATUS register is clear. This field is updated at the end of the address phase of the current access to the HSB bus. It is incremented of the HSB access byte-width. The HSB access width is 4 bytes, or less at packet start or end if the start or end address is not aligned on a word boundary. The packet start address is either the channel start address or the next channel address to be accessed in the channel buffer. The packet end address is either the channel end address or the latest channel address accessed in the channel buffer. The channel start address is written by software or loaded from the descriptor, whereas the channel end address is either determined by the end of buffer or the end of USB transfer if the Buffer Close Input Enable bit (BUFF_CLOSE_IN_EN) is set. 592 32058H–AVR32–03/09 AT32UC3A 30.8.2.19 USB Device DMA Channel X Control Register (UDDMAX_CONTROL) 0x0318 + (X - 1) . 0x10 UDDMAX_CONTROL, X in [1..6] Read/Write 0x00000000 30 29 28 27 CH_BYTE_LENGTH rwu 0 0 20 19 CH_BYTE_LENGTH rwu 0 0 12 – 11 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 0 23 0 22 0 21 0 18 0 17 0 16 0 15 – 0 14 – 0 13 – 0 10 – 0 9 – 0 8 – 7 BURST_LOCK _EN rwu 0 6 DESC_LD_ IRQ_EN rwu 0 5 EOBUFF_ IRQ_EN rwu 0 4 EOT_IRQ_EN rwu 0 3 DMAEND_EN rwu 0 2 BUFF_CLOSE _IN_EN rwu 0 1 LD_NXT_CH_ DESC_EN rwu 0 0 CH_EN rwu 0 • CH_EN: Channel Enable Set this bit to enable this channel data transfer. Clear this bit to disable the channel data transfer. This may be used to start or resume any requested transfer. This bit is cleared by hardware when the HSB source channel is disabled at end of dma buffer. • LD_NXT_CH_DESC_EN: Load Next Channel Descriptor Enable Set this bit to allow automatic next descriptor loading at the end of the channel transfer. Clear this bit to disable this feature. If set, the dma channel controller loads the next descriptor when the UDDMAX_STATUS.CH_EN bit is reset due to software of hardware event (for example at the end of the current transfer). • BUFF_CLOSE_IN_EN: Buffer Close Input Enable Set this bit to automatically closed the current dma transfer at the end of the usb OUT data transfer (received short packet). Clear this bit to disable this feature. • DMAEND_EN: End of DMA Buffer Output Enable Set this bit to properly complete the usb transfer at the end of the dma transfer. For IN endpoint, it means that a short packet (or a Zero Length Packet) will be sent to the usb line to properly closed the usb transfer at the end of the dma transfer. For OUT endpoint, it means that all the banks will be properly released. (NBUSYBK=0) at the end of the dma transfer. 593 32058H–AVR32–03/09 AT32UC3A • EOT_IRQ_EN: End of USB Transfer Interrupt Enable Set this bit to enable the end of usb OUT data transfer interrupt. This interrupt is generated only if the BUFF_CLOSE_IN_EN bit is set. Clear this bit to disable this interrupt. • EOBUFF_IRQ_EN: End of Buffer Interrupt Enable Set this bit to enable the end of buffer interrupt. This interrupt is generated when the channel byte count reaches zero. Clear this bit to disable this interrupt. • DESC_LD_IRQ_EN: Descriptor Loaded Interrupt Enable Set this bit to enable the Descripor Loaded interrupt. This interrupt is generated when a Descriptor has been loaded from the system bus. Clear this bit to disable this interrupt. • BURST_LOCK_EN: Burst Lock Enable Set this bit to lock the HSB data burst for maximum optimization of HSB busses bandwidth usage and maximization of flyby duration. If clear, the DMA never locks HSB access. • CH_BYTE_LENGTH: Channel Byte Length This field determines the total number of bytes to be transferred for this buffer. The maximum channel transfer size 64 kB is reached when this field is 0 (default value). If the transfer size is unknown, the transfer end is controlled by the peripheral and this field should be set to 0. This field can be written by software or descriptor loading only after the UDDMAX_STATUS.CH_EN bit has been cleared, otherwise this field is ignored. 594 32058H–AVR32–03/09 AT32UC3A 30.8.2.20 USB Device DMA Channel X Status Register (UDDMAX_STATUS) 0x031C + (X - 1) . 0x10 UDDMAX_STATUS, X in [1..6] Read/Write 0x00000000 30 29 28 CH_BYTE_CNT ru 0 23 0 22 0 21 0 20 CH_BYTE_CNT ru 0 15 – 0 14 – 0 13 – 0 12 – 0 11 – 0 10 – 0 9 – 0 8 – 0 19 0 18 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 7 – 6 DESC_LD_ STA ru 0 5 EOCH_BUFF_ STA ru 0 4 EOT_STA ru 0 3 – 2 – 1 CH_ACTIVE rwu 0 0 CH_EN rwu 0 • CH_EN: Channel Enabled If set, the DMA channel is currently enabled. If cleared, the DMA channel does no longer transfer data. • CH_ACTIVE: Channel Active If set, the DMA channel is currently trying to source USB data. If cleared, the DMA channel is no longer trying to source USB data. When a USB data transfer is completed, this bit is automatically reset. • EOT_STA: End of USB Transfer Status Set by hardware when the completion of the usb data transfer has closed the dma transfer. It is valid only if BUFF_CLOSE_EN=1. This bit is automatically cleared when read by software. • EOCH_BUFF_STA: End of Channel Buffer Status Set by hardware when the Channel Byte Count downcounts to zero. This bit is automatically cleared when read by software. • DESC_LD_STA: Descriptor Loaded Status Set by hardware when a Descriptor has been loaded from the HSB bus. This bit is automatically cleared when read by software. 595 32058H–AVR32–03/09 AT32UC3A • CH_BYTE_CNT: Channel Byte Count This field gives the current number of bytes still to be transferred for this buffer. This field is decremented at each dma access. This field is reliable (stable) only if the CH_EN flag is 0. 596 32058H–AVR32–03/09 AT32UC3A 30.8.3 30.8.3.1 USB Host Registers USB Host General Control Register (UHCON) 0x0400 UHCON Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 RESUME rwu 0 9 RESET rwu 0 1 – 8 SOFE rwu 0 0 – 7 – 6 – 5 – 4 – 3 – 2 – • SOFE: Start of Frame Generation Enable Set this bit to generate SOF on the USB bus in full speed mode and keep alive in low speed mode. Clear this bit to disable the SOF generation and to leave the USB bus in idle state. This bit is set by hardware when a USB reset is requested or an upstream resume interrupt is detected (UHINT.TXRSMI). • RESET: Send USB Reset Set this bit to generate a USB Reset on the USB bus. Cleared by hardware when the USB Reset has been sent. It may be useful to clear this bit by software when a device disconnection is detected (UHINT.DDISCI is set) whereas a USB Reset is being sent. • RESUME: Send USB Resume Set this bit to generate a USB Resume on the USB bus. Cleared by hardware when the USB Resume has been sent or when a USB reset is requested. Clearing by software has no effect. This bit should be set only when the start of frame generation is enable. (SOFE bit set). 597 32058H–AVR32–03/09 AT32UC3A 30.8.3.2 USB Host Global Interrupt Register (UHINT) 0x0404 UHINT Read-Only 0x00000000 30 DMA6INT r 0 22 – 29 DMA5INT r 0 21 – 28 DMA4INT r 0 20 – 27 DMA3INT r 0 19 – 26 DMA2INT r 0 18 – 25 DMA1INT r 0 17 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 16 – 15 – 14 P6INT r 0 6 HWUPI r 0 13 P5INT r 0 5 HSOFI r 0 12 P4INT r 0 4 RXRSMI r 0 11 P3INT r 0 3 RSMEDI r 0 10 P2INT r 0 2 RSTI r 0 9 P1INT r 0 1 DDISCI r 0 8 P0INT r 0 0 DCONNI r 0 7 – • DCONNI: Device Connection Interrupt Flag Set by hardware when a new device has been connected to the USB bus. Shall be cleared by software (by setting the DCONNIC bit). • DDISCI: Device Disconnection Interrupt Flag Set by hardware when the device has been removed from the USB bus. Shall be cleared by software (by setting the DDISCIC bit). • RSTI: USB Reset Sent Interrupt Flag Set by hardware when a USB Reset has been sent to the device. Shall be cleared by software (by setting the RSTIC bit). • RSMEDI: Downstream Resume Sent Interrupt Flag Set by hardware when a Downstream Resume has been sent to the Device. Shall be cleared by software (by setting the RSMEDIC bit). • RXRSMI: Upstream Resume Received Interrupt Flag Set by hardware when an Upstream Resume has been received from the Device. Shall be cleared by software (by setting the RXRSMIC bit). • HSOFI: Host Start of Frame Interrupt Flag Set by hardware when a SOF is issued by the Host controller. This triggers a USB interrupt when HSOFE is set. When using the host controller in low speed mode, this bit is also set when a keep-alive is sent. Shall be cleared by software (by setting the HSOFIC bit). 598 32058H–AVR32–03/09 AT32UC3A • HWUPI: Host Wake-Up Interrupt Flag Asynchronous interrupt. Set by hardware in the following cases : – The Host controller is in the suspend mode (SOFE=0) and an upstream resume from the Peripheral is detected. – The Host controller is in the suspend mode (SOFE=0) and a Peripheral disconnection is detected. – The Host controller is in the Idle state (VBUSRQ=0, no VBus is generated), and an OTG SRP event initiated by the Peripheral is detected. Note that this interrupt is generated even if the clock is frozen by the FRZCLK bit. • PXINT, X in [0..6]: Pipe X Interrupt Flag Set by hardware when an interrupt is triggered by the endpoint X (UPSTAX). This triggers a USB interrupt if the corresponding pipe interrupt enable bit is set (UHINTE register). Cleared by hardware when the interrupt source is served. • DMAXINT, X in [1..6]: DMA Channel X Interrupt Flag Set by hardware when an interrupt is triggered by the DMA channel X. This triggers a USB interrupt if the corresponding DMAXINTE is set (UHINTE register). Cleared by hardware when the UHDMAX_STATUS interrupt source is cleared. 599 32058H–AVR32–03/09 AT32UC3A 30.8.3.3 USB Host Global Interrupt Clear Register (UHINTCLR) 0x0408 UHINTCLR Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 HWUPIC w 0 5 HSOFIC w 0 4 RXRSMIC w 0 3 RSMEDIC w 0 2 RSTIC w 0 1 DDISCIC w 0 0 DCONNIC w 0 • DCONNIC: Device Connection Interrupt Flag Clear Set to clear DCONNI. Clearing has no effect. Always read as 0. • DDISCIC: Device Disconnection Interrupt Flag Clear Set to clear DDISCI. Clearing has no effect. Always read as 0. • RSTIC: USB Reset Sent Interrupt Flag Clear Set to clear RSTI. Clearing has no effect. Always read as 0. • RSMEDIC: Downstream Resume Sent Interrupt Flag Clear Set to clear RSMEDI. Clearing has no effect. Always read as 0. • RXRSMIC: Upstream Resume Received Interrupt Flag Clear Set to clear RXRSMI. 600 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • HSOFIC: Host Start of Frame Interrupt Flag Clear Set to clear HSOFI. Clearing has no effect. Always read as 0. • HWUPIC: Host Wake-Up Interrupt Flag Clear Set to clear HWUPI. Clearing has no effect. Always read as 0. 601 32058H–AVR32–03/09 AT32UC3A 30.8.3.4 USB Host Global Interrupt Set Register (UHINTSET) 0x040C UHINTSET Write-Only 0x00000000 30 DMA6INTS w 0 22 – 29 DMA5INTS w 0 21 – 28 DMA4INTS w 0 20 – 27 DMA3INTS w 0 19 – 26 DMA2INTS w 0 18 – 25 DMA1INTS w 0 17 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 HWUPIS w 0 5 HSOFIS w 0 4 RXRSMIS w 0 3 RSMEDIS w 0 2 RSTIS w 0 1 DDISCIS w 0 0 DCONNIS w 0 • DCONNIS: Device Connection Interrupt Flag Set Set to set DCONNI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • DDISCIS: Device Disconnection Interrupt Flag Set Set to set DDISCI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RSTIS: USB Reset Sent Interrupt Flag Set Set to set RSTI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RSMEDIS: Downstream Resume Sent Interrupt Flag Set Set to set RSMEDI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RXRSMIS: Upstream Resume Received Interrupt Flag Set Set to set RXRSMI, what may be useful for test or debug purposes. 602 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • HSOFIS: Host Start of Frame Interrupt Flag Set Set to set HSOFI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • HWUPIS: Host Wake-Up Interrupt Flag Set Set to set HWUPI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • DMAXINTS, X in [1..6]: DMA Channel X Interrupt Flag Set Set to set DMAXINT, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. 603 32058H–AVR32–03/09 AT32UC3A 30.8.3.5 USB Host Global Interrupt Enable Register (UHINTE) 0x0410 UHINTE Read-Only 0x00000000 30 DMA6INTE r 0 22 – 29 DMA5INTE r 0 21 – 28 DMA4INTE r 0 20 – 27 DMA3INTE r 0 19 – 26 DMA2INTE r 0 18 – 25 DMA1INTE r 0 17 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 16 – 15 – 14 P6INTE r 0 6 HWUPIE r 0 13 P5INTE r 0 5 HSOFIE r 0 12 P4INTE r 0 4 RXRSMIE r 0 11 P3INTE r 0 3 RSMEDIE r 0 10 P2INTE r 0 2 RSTIE r 0 9 P1INTE r 0 1 DDISCIE r 0 8 P0INTE r 0 0 DCONNIE r 0 7 – • DCONNIE: Device Connection Interrupt Enable Set by software (by setting the DCONNIES bit) to enable the Device Connection interrupt (DCONNI). Clear by software (by setting the DCONNIEC bit) to disable the Device Connection interrupt (DCONNI). • DDISCIE: Device Disconnection Interrupt Enable Set by software (by setting the DDISCIES bit) to enable the Device Disconnection interrupt (DDISCI). Clear by software (by setting the DDISCIEC bit) to disable the Device Disconnection interrupt (DDISCI). • RSTIE: USB Reset Sent Interrupt Enable Set by software (by setting the RSTIES bit) to enable the USB Reset Sent interrupt (RSTI). Clear by software (by setting the RSTIEC bit) to disable the USB Reset Sent interrupt (RSTI). • RSMEDIE: Downstream Resume Sent Interrupt Enable Set by software (by setting the RSMEDIES bit) to enable the Downstream Resume interrupt (RSMEDI). Clear by software (by setting the RSMEDIEC bit) to disable the Downstream Resume interrupt (RSMEDI). • RXRSMIE: Upstream Resume Received Interrupt Enable Set by software (by setting the RXRSMIES bit) to enable the Upstream Resume Received interrupt (RXRSMI). Clear by software (by setting the RXRSMIEC bit) to disable the Downstream Resume interrupt (RXRSMI). • HSOFIE: Host Start of Frame Interrupt Enable Set by software (by setting the HSOFIES bit) to enable the Host Start of Frame interrupt (HSOFI). Clear by software (by setting the HSOFIEC bit) to disable the Host Start of Frame interrupt (HSOFI). 604 32058H–AVR32–03/09 AT32UC3A • HWUPIE: Host Wake-Up Interrupt Enable Set by software (by setting the HWUPIES bit) to enable the Host Wake-up Interrupt (HWUPI). Clear by software (by setting the HWUPIEC bit) to disable the Host Wake-up Interrupt (HWUPI). • PXINTE, X in [0..6]: Pipe X Interrupt Enable Set by software (by setting the PXINTES bit) to enable the Pipe X Interrupt (PXINT). Clear by software (by setting the PXINTEC bit) to disable the Pipe X Interrupt (PXINT). • DMAXINTE, X in [1..6]: DMA Channel X Interrupt Enable Set by software (by setting the DMAXINTES bit) to enable the DMA Channel X Interrupt (DMAXINT). Clear by software (by setting the DMAXINTEC bit) to disable the DMA Channel X Interrupt (DMAXINT). 605 32058H–AVR32–03/09 AT32UC3A 30.8.3.6 USB Host Global Interrupt Enable Clear Register (UHINTECLR) 0x0414 UHINTECLR Write-Only 0x00000000 30 DMA6INTEC w 0 22 – 29 DMA5INTEC w 0 21 – 28 DMA4INTEC w 0 20 – 27 DMA3INTEC w 0 19 – 26 DMA2INTEC w 0 18 – 25 DMA1INTEC w 0 17 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 16 – 15 – 14 P6INTEC w 0 6 HWUPIEC w 0 13 P5INTEC w 0 5 HSOFIEC w 0 12 P4INTEC w 0 4 RXRSMIEC w 0 11 P3INTEC w 0 3 RSMEDIEC w 0 10 P2INTEC w 0 2 RSTIEC w 0 9 P1INTEC w 0 1 DDISCIEC w 0 8 P0INTEC w 0 0 DCONNIEC w 0 7 – • DCONNIEC: Device Connection Interrupt Enable Clear Set to clear DCONNIE. Clearing has no effect. Always read as 0. • DDISCIEC: Device Disconnection Interrupt Enable Clear Set to clear DDISCIEC. Clearing has no effect. Always read as 0. • RSTIEC: USB Reset Sent Interrupt Enable Clear Set to clear RSTIEC. Clearing has no effect. Always read as 0. • RSMEDIEC: Downstream Resume Sent Interrupt Enable Clear Set to clear RSMEDIEC. Clearing has no effect. Always read as 0. • RXRSMIEC: Upstream Resume Received Interrupt Enable Clear Set to clear RSTIEC. 606 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • HSOFIEC: Host Start of Frame Interrupt Enable Clear Set to clear HSOFIEC. Clearing has no effect. Always read as 0. • HWUPIEC: Host Wake-Up Interrupt Enable Clear Set to clear HWUPIEC. Clearing has no effect. Always read as 0. • PXINTEC, X in [0..6]: Pipe X Interrupt Enable Clear Set to clear PXINTEC. Clearing has no effect. Always read as 0. • DMAXINTEC, X in [1..6]: DMA Channel X Interrupt Enable Clear Set to clear DMAXINTEC. Clearing has no effect. Always read as 0. 607 32058H–AVR32–03/09 AT32UC3A 30.8.3.7 USB Host Global Interrupt Enable Set Register (UHINTESET) 0x0418 UHINTESET Write-Only 0x00000000 30 DMA6INTES w 0 22 – 29 DMA5INTES w 0 21 – 28 DMA4INTES w 0 20 – 27 DMA3INTES w 0 19 – 26 DMA2INTES w 0 18 – 25 DMA1INTES w 0 17 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 16 – 15 – 14 P6INTES w 0 6 HWUPIES w 0 13 P5INTES w 0 5 HSOFIES w 0 12 P4INTES w 0 4 RXRSMIES w 0 11 P3INTES w 0 3 RSMEDIES w 0 10 P2INTES w 0 2 RSTIES w 0 9 P1INTES w 0 1 DDISCIES w 0 8 P0INTES w 0 0 DCONNIES w 0 7 – • DCONNIES: Device Connection Interrupt Enable Set Set to set DCONNIE. Clearing has no effect. Always read as 0. • DDISCIES: Device Disconnection Interrupt Enable Set Set to set DDISCIE. Clearing has no effect. Always read as 0. • RSTIES: USB Reset Sent Interrupt Enable Set Set to set RSTIE. Clearing has no effect. Always read as 0. • RSMEDIES: Downstream Resume Sent Interrupt Enable Set Set to set RSMEDIE. Clearing has no effect. Always read as 0. • RXRSMIES: Upstream Resume Received Interrupt Enable Set Set to set RXRSMIE. 608 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • HSOFIES: Host Start of Frame Interrupt Enable Set Set to set HSOFIE. Clearing has no effect. Always read as 0. • HWUPIES: Host Wake-Up Interrupt Enable Set Set to set HWUPIE. Clearing has no effect. Always read as 0. • PXINTES, X in [0..6]: Pipe X Interrupt Enable Set Set to set PXINTE. Clearing has no effect. Always read as 0. • DMAXINTES, X in [1..6]: DMA Channel X Interrupt Enable Set Set to set DMAXINTE. Clearing has no effect. Always read as 0. 609 32058H–AVR32–03/09 AT32UC3A 30.8.3.8 USB Host Frame Number Register (UHFNUM) 0x0420 UHFNUM Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 22 21 20 FLENHIGH ru 19 18 17 16 0 15 – 0 14 – 0 13 0 12 0 11 FNUM rwu 0 10 0 9 0 8 0 7 6 5 FNUM rwu 0 0 4 0 3 0 2 – 0 1 – 0 0 – 0 0 0 0 • FNUM: Frame Number The value contained in this register is the current SOF number. This value can be modified by software. • FLENHIGH: Frame Length This register gives the 8 high-order bits of the 14-bits internal frame counter (frame counter at 12 Mhz, counter length is 12000 to ensure a SOF generation every 1 ms). 610 32058H–AVR32–03/09 AT32UC3A 30.8.3.9 USB Host Frame Number Register (UHADDR1) 0x0424 UHADDR1 Read/Write 0x00000000 30 29 28 27 UHADDR_P3 rwu 0 19 UHADDR_P2 rwu 0 11 UHADDR_P1 rwu 0 3 UHADDR_P0 rwu 0 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 – – 23 – – 15 – – 7 – – 0 22 0 21 0 20 0 18 0 17 0 16 0 14 0 13 0 12 0 10 0 9 0 8 0 6 0 5 0 4 0 2 0 1 0 0 0 0 0 • UHADDR_P0 : USB Host Address These bits should contain the address of the Pipe0 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P1 : USB Host Address These bits should contain the address of the Pipe1 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P2 : USB Host Address These bits should contain the address of the Pipe2 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P3 : USB Host Address These bits should contain the address of the Pipe3 of the USB Device. Cleared by hardware when a USB reset is requested. 611 32058H–AVR32–03/09 AT32UC3A 30.8.3.10 USB Host Frame Number Register (UHADDR2) 0x0428 UHADDR2 Read/Write 0x00000000 30 – 0 22 29 – 0 21 28 – 0 20 27 – rwu 0 19 UHADDR_P6 rwu 0 11 UHADDR_P5 rwu 0 3 UHADDR_P4 rwu 0 26 – 0 18 25 – 0 17 24 – 0 16 Offset: Register Name: Access Type: Reset Value: 31 – – 23 – – 15 – – 7 – – 0 14 0 13 0 12 0 10 0 9 0 8 0 6 0 5 0 4 0 2 0 1 0 0 0 0 0 • UHADDR_P4 : USB Host Address These bits should contain the address of the Pipe4 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P5 : USB Host Address These bits should contain the address of the Pipe5 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P6 : USB Host Address These bits should contain the address of the Pipe6 of the USB Device. Cleared by hardware when a USB reset is requested. • UHADDR_P7 : USB Host Address These bits should contain the address of the Pipe7 of the USB Device. Cleared by hardware when a USB reset is requested. 612 32058H–AVR32–03/09 AT32UC3A 30.8.3.11 USB Pipe Enable/Reset Register (UPRST) 0x0041C UPRST Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 PRST6 rwu 0 14 – 21 PRST5 rwu 0 13 – 20 PRST4 rwu 0 12 – 19 PRST3 rwu 0 11 – 18 PRST2 rwu 0 10 – 17 PRST1 rwu 0 9 – 16 PRST0 rwu 0 8 – 15 – 7 – 6 PEN6 rw 0 5 PEN5 rw 0 4 PEN4 rw 0 3 PEN3 rw 0 2 PEN2 rw 0 1 PEN1 rw 0 0 PEN0 rw 0 • PENX, X in [0..6]: Pipe X Enable Set to enable the Pipe X. Clear to disable the Pipe X, what forces the Pipe X state to inactive and resets the pipe X registers (UPCFGX, UPSTAX, UPCONX) but not the pipe configuration (ALLOC, PBK, PSIZE). • PRSTX, X in [0..6]: Pipe X Reset Set by software to reset the Pipe X FIFO. This resets the endpoint X registers (UPCFGX, UPSTAX, UPCONX) but not the endpoint configuration (ALLOC, PBK, PSIZE, PTOKEN, PTYPE, PEPNUM, INTFRQ). All the endpoint mechanism (FIFO counter, reception, transmission, etc.) is reset apart from the Data Toggle management . The endpoint configuration remains active and the endpoint is still enabled. Then, clear by software to complete the reset operation and to start using the FIFO. 613 32058H–AVR32–03/09 AT32UC3A 30.8.3.12 USB Pipe X Configuration Register (UPCFGX) 0x0500 + X . 0x04 UPCFGX, X in [0..6] Read/Write 0x00000000 30 29 28 INTFRQ rwu 0 23 – 0 22 – 0 21 – 0 20 – 0 19 0 18 PEPNUM rwu 0 15 – 14 – 13 PTYPE rwu 0 7 – 6 5 PSIZE rwu 0 0 4 3 PBK rwu 0 0 0 12 11 – 0 10 AUTOSW rwu 0 2 0 9 PTOKEN rwu 0 1 ALLOC rwu 0 0 0 – 0 8 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 0 • ALLOC: Pipe Memory Allocate Set to configure the pipe memory with the characteristics. Clear to update the memory allocation. This bit is cleared by hardware when a USB Reset is requested. Refer to the DPRAM Management chapter for more details. • PBK: Pipe Banks Set to select the number of banks for the pipe: PBK 0 0 1 1 0 1 0 1 Endpoint Banks 1 (single-bank pipe) 2 (double-bank pipe) 3 (triple-bank pipe) Reserved For control endpoints, a single-bank pipe (00b) should be selected. Cleared by hardware upon sending a USB reset. 614 32058H–AVR32–03/09 AT32UC3A • PSIZE: Pipe Size Set to select the size of each pipe bank: PSIZE 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Endpoint Size 8 bytes 16 bytes 32 bytes 64 bytes 128 bytes 256 bytes 512 bytes 1024 bytes Cleared by hardware upon sending a USB reset. • PTOKEN: Pipe Token Set to select the endpoint token: PTOKEN 00 01 10 11 Endpoint Direction SETUP IN OUT reserved • AUTOSW: Automatic Switch Set to automatically switch bank when it is ready. Clear to disable the automatic bank switching. Cleared by hardware upon sending a USB reset. • PTYPE: Pipe Type Set to select the pipe type: PTYPE 0 0 1 1 0 1 0 1 Pipe Type Control Isochronous Bulk Interrupt Cleared by hardware upon sending a USB reset. • PEPNUM: Pipe Endpoint Number Set this field according to the Pipe configuration. Set the number of the endpoint targeted by the pipe. This value is from 0 to 15. Cleared by hardware upon sending a USB reset. 615 32058H–AVR32–03/09 AT32UC3A • INTFRQ: Pipe Interrupt Request Frequency These bits are the maximum value in millisecond of the polling period for an Interrupt Pipe. This value has no effect for a non-Interrupt Pipe. Cleared by hardware upon sending a USB reset. 616 32058H–AVR32–03/09 AT32UC3A 30.8.3.13 USB Pipe X Status Register (UPSTAX) 0x0530 + X . 0x04 UPSTAX, X in [0..6] Read-Only 0x00000000 30 29 28 27 PBYCT r 0 19 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 – 0 23 22 PBYCT r 0 15 CURRBK r 0 7 SHORT PACKETI r 0 0 6 RXSTALLDI/ CRCERRI r 0 0 14 0 21 0 20 0 18 CFGOK r 0 10 – 0 17 – 0 16 RWALL r 0 8 DTSEQ r 0 13 NBUSYBK r 0 5 OVERFI r 0 0 12 11 – 9 0 4 NAKEDI r 0 3 PERRI r 0 2 TXSTPI/ UNDERFI r 0 0 1 TXOUTI r 0 0 0 RXINI r 0 • RXINI: Received IN Data Interrupt Flag Set by hardware when a new USB message is stored in the current bank of the Pipe. This triggers an interrupt if the RXINE bit is set. Shall be cleared by software (by setting the RXINIC bit). • TXOUTI: Transmitted OUT Data Interrupt Flag Set by hardware when the current OUT bank is free and can be filled. This triggers an interrupt if the TXOUTE bit is set. Shall be cleared by software (by setting the TXOUTIC bit). • TXSTPI: Transmitted SETUP Interrupt Flag For Control endpoints. Set by hardware when the current SETUP bank is free and can be filled. This triggers an interrupt if the TXSTPE bit is set. Shall be cleared by software (by setting the TXSTPIC bit). • UNDERFI: Underflow Interrupt Flag Set by hardware when a transaction underflow occurs in the current isochronous or interrupt pipe. (the pipe can’t send the OUT data packet in time because the current bank is not ready). A zero-length-packet (ZLP) will be send instead of. This triggers an interrupt if the UNDERFLE bit is set. Shall be cleared by software (by setting the UNDERFIC bit). • PERRI: Pipe Error Interrupt Flag Set by hardware when an error occurs on the current bank of the Pipe. This triggers an interrupt if the PERRE bit is set. Refers to the UPERRX register to determine the source of the error. Automatically cleared by hardware when the error source bit is cleared. • NAKEDI: NAKed Interrupt Flag Set by hardware when a NAK has been received on the current bank of the Pipe. This triggers an interrupt if the NAKEDE bit is set. Shall be cleared by software (by setting the NAKEDIC bit). 617 32058H–AVR32–03/09 AT32UC3A • OVERFI: Overflow Interrupt Flag Set by hardware when the current Pipe has received more data than the maximum length of the current Pipe. An interrupt is triggered if the OVERFIE bit is set. Shall be cleared by software (by setting the OVERFIC bit). • RXSTALLDI: Received STALLed Interrupt Flag For all endpoints but isochronous. Set by hardware when a STALL handshake has been received on the current bank of the Pipe. The Pipe is automatically frozen. This triggers an interrupt if the RXSTALLE bit is set. Shall be cleared to handshake the interrupt (by setting the RXSTALLDIC bit). • CRCERRI: CRC Error Interrupt Flag For isochronous endpoint, set by hardware when a CRC error occurs on the current bank of the Pipe. This triggers an interrupt if the TXSTPE bit is set. Shall be cleared to handshake the interrupt (by setting the CRCERRIC bit). • SHORTPACKETI: Short Packet Interrupt Flag Set by hardware when a short packet is received by the host controller (packet length inferior to the PSIZE programmed field). Shall be cleared to handshake the interrupt (by setting the SHORTPACKETIC bit). • DTSEQ: Data Toggle Sequence Set by hardware to indicate the data PID of the current bank. DTSEQ 0 0 1 1 0 1 0 1 Data toggle sequence Data0 Data1 reserved reserved For OUT pipe, this field indicates the data toggle of the next packet that will be sent. For IN pipe, this field indicates the data toggle of the received packet stored in the current bank. • NBUSYBK: Number of Busy Banks Set by hardware to indicate the number of busy bank. For OUT Pipe, it indicates the number of busy bank(s), filled by the user, ready for OUT transfer. When all banks are busy, this triggers an PXINT interrupt if UPCONX.NBUSYBKE = 1. For IN Pipe, it indicates the number of busy bank(s) filled by IN transaction from the Device. When all banks are free, this triggers an PXINT interrupt if UPCONX.NBUSYBKE = 1.. NBUSYBK 0 0 1 1 0 1 0 1 Number of busy bank All banks are free. 1 busy bank 2 busy banks reserved 618 32058H–AVR32–03/09 AT32UC3A • CURRBK: Current Bank For non-control pipe, set by hardware to indicate the number of the current bank. CURRBK 0 0 1 1 0 1 0 1 Current Bank Bank0 Bank1 Bank2 Reserved Note that this field may be updated 1 clock cycle after the RWALL bit changes, so the user should not poll this field as an interrupt flag. • RWALL: Read/Write Allowed For OUT pipe, set by hardware when the current bank is not full, i.e. the software can write further data into the FIFO. For IN pipe, set by hardware when the current bank is not empty, i.e. the software can read further data from the FIFO. Cleared by hardware otherwise. This bit is also cleared by hardware when the RXSTALL or the PERR bit is set. • CFGOK: Configuration OK Status This bit is updated when the ALLOC bit is set. Set by hardware if the pipe X number of banks (PBK) and size (PSIZE) are correct compared to the maximal allowed number of banks and size for this pipe and to the maximal FIFO size (i.e. the DPRAM size). If this bit is cleared by hardware, the user should reprogram the UPCFGX register with correct PBK and PSIZE values. • PBYCT: Pipe Byte Count Set by the hardware to indicate the byte count of the FIFO. For OUT pipe, incremented after each byte written by the software into the pipe and decremented after each byte sent to the peripheral. For In pipe, incremented after each byte received from the peripheral and decremented after each byte read by the software from the pipe. Note that this field may be updated 1 clock cycle after the RWALL bit changes, so the user should not poll this field as an interrupt flag. 619 32058H–AVR32–03/09 AT32UC3A 30.8.3.14 USB Pipe X Status Clear Register (UPSTAXCLR) 0x0560 + X . 0x04 UPSTAXCLR, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 SHORT PACKETIC w 0 6 RXSTALLDIC/ CRCERRIC w 0 5 OVERFIC w 0 4 NAKEDIC w 0 3 – 2 TXSTPIC/ UNDERFIC w 0 1 TXOUTIC w 0 0 RXINIC w 0 • RXINIC: Received IN Data Interrupt Flag Clear Set to clear RXINI. Clearing has no effect. Always read as 0. • TXOUTIC: Transmitted OUT Data Interrupt Flag Clear Set to clear TXOUTI. Clearing has no effect. Always read as 0. • TXSTPIC: Transmitted SETUP Interrupt Flag Clear Set to clear TXSTPI. Clearing has no effect. Always read as 0. • UNDERFIC: Underflow Interrupt Flag Clear Set to clear UNDERFI. Clearing has no effect. Always read as 0. • NAKEDIC: NAKed Interrupt Flag Clear Set to clear NAKEDI. 620 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • OVERFIC: Overflow Interrupt Flag Clear Set to clear OVERFI. Clearing has no effect. Always read as 0. • RXSTALLDIC: Received STALLed Interrupt Flag Clear Set to clear RXSTALLDI. Clearing has no effect. Always read as 0. • CRCERRIC: CRC Error Interrupt Flag Clear Set to clear CRCERRI. Clearing has no effect. Always read as 0. • SHORTPACKETIC: Short Packet Interrupt Flag Clear Set to clear SHORTPACKETI. Clearing has no effect. Always read as 0. 621 32058H–AVR32–03/09 AT32UC3A 30.8.3.15 USB Pipe X Status Set Register (UPSTAXSET) 0x0590 + X . 0x04 UPSTAXSET, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 NBUSYBKS w 0 4 NAKEDIS w 0 11 – 10 – 9 – 8 – 7 SHORT PACKETIS w 0 6 RXSTALLDIS/ CRCERRIS w 0 5 OVERFIS w 0 3 PERRIS w 0 2 TXSTPIS/ UNDERFIS w 0 1 TXOUTIS w 0 0 RXINIS w 0 • RXINIS: Received IN Data Interrupt Flag Set Set to set RXINI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • TXOUTIS: Transmitted OUT Data Interrupt Flag Set Set to set TXOUTI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • TXSTPIS: Transmitted SETUP Interrupt Flag Set Set to set TXSTPI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • UNDERFIS: Underflow Interrupt Flag Set Set to set UNDERFI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • PERRIS: Pipe Error Interrupt Flag Set Set to set PERRI, what may be useful for test or debug purposes. 622 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKEDIS: NAKed Interrupt Flag Set Set to set NAKEDI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • OVERFIS: Overflow Interrupt Flag Set Set to set OVERFI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • RXSTALLDIS: Received STALLed Interrupt Flag Set Set to set RXSTALLDI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • CRCERRIS: CRC Error Interrupt Flag Set Set to set CRCERRI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • SHORTPACKETIS: Short Packet Interrupt Flag Set Set to set SHORTPACKETI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. • NBUSYBKS: Number of Busy Banks Interrupt Flag Set Set to set NBUSYBKI, what may be useful for test or debug purposes. Clearing has no effect. Always read as 0. 623 32058H–AVR32–03/09 AT32UC3A 30.8.3.16 USB Pipe X Control Register (UPCONX) 0x05C0 + X . 0x04 UPCONX, X in [0..6] Read-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 RSTDT ru 0 10 – 17 PFREEZE ru 0 9 – 16 PDISHDMA ru 0 8 – 15 – 14 FIFOCON ru 0 6 RXSTALLDE/ CRCERRE ru 0 13 – 12 NBUSYBKE ru 0 4 NAKEDE ru 0 11 – 7 SHORT PACKETIE ru 0 5 OVERFIE ru 0 3 PERRE ru 0 2 TXSTPE/ UNDERFIE ru 0 1 TXOUTE ru 0 0 RXINE ru 0 • RXINE: Received IN Data Interrupt Enable Set by software (by setting the RXINES bit) to enable the Received IN Data interrupt (RXINE). Clear by software (by setting the RXINEC bit) to disable the Received IN Data interrupt (RXINE). • TXOUTE: Transmitted OUT Data Interrupt Enable Set by software (by setting the TXOUTES bit) to enable the Transmitted OUT Data interrupt (TXOUTE). Clear by software (by setting the TXOUTECbit) to disable the Transmitted OUT Data interrupt (TXOUTE). • TXSTPE: Transmitted SETUP Interrupt Enable Set by software (by setting the TXSTPES bit) to enable the Transmitted SETUP interrupt (TXSTPE). Clear by software (by setting the TXSTPEC bit) to disable the Transmitted SETUP interrupt (TXSTPE). • UNDERFIE: Underflow Interrupt Enable Set by software (by setting the UNDERFIES bit) to enable the Underflow interrupt (UNDERFIE). Clear by software (by setting the UNDERFIEC bit) to disable the Underflow interrupt (UNDERFIE). • PERRE: Pipe Error Interrupt Enable Set by software (by setting the PERRES bit) to enable the Pipe Error interrupt (PERRE). Clear by software (by setting the PERREC bit) to disable the Pipe Error interrupt (PERRE). • NAKEDE: NAKed Interrupt Enable Set by software (by setting the NAKEDES bit) to enable the NAKed interrupt (NAKEDE). Clear by software (by setting the NAKEDEC bit) to disable the NAKed interrupt (NAKEDE). 624 32058H–AVR32–03/09 AT32UC3A • OVERFIE: Overflow Interrupt Enable Set by software (by setting the OVERFIES bit) to enable the Overflow interrupt (OVERFIE). Clear by software (by setting the OVERFIEC bit) to disable the Overflow interrupt (OVERFIE). • RXSTALLDE: Received STALLed Interrupt Enable Set by software (by setting the RXSTALLDES bit) to enable the Received STALLed interrupt (RXSTALLDE). Clear by software (by setting the RXSTALLDEC bit) to disable the Received STALLed interrupt (RXSTALLDE). • CRCERRE: CRC Error Interrupt Enable Set by software (by setting the CRCERRES bit) to enable the CRC Error interrupt (CRCERRE). Clear by software (by setting the CRCERREC bit) to disable the CRC Error interrupt (CRCERRE). • SHORTPACKETIE: Short Packet Interrupt Enable Set by software (by setting the SHORTPACKETES bit) to enable the Short Packet interrupt (SHORTPACKETIE). Clear by software (by setting the SHORTPACKETEC bit) to disable the Short Packet interrupt (SHORTPACKETE). • NBUSYBKE: Number of Busy Banks Interrupt Enable Set by software (by setting the NBUSYBKES bit) to enable the Number of Busy Banks interrupt (NBUSYBKE). Clear by software (by setting the NBUSYBKEC bit) to disable the Number of Busy Banks interrupt (NBUSYBKE). • FIFOCON: FIFO Control For OUT and SETUP Pipe : Set by hardware when the current bank is free, at the same time than TXOUTI or TXSTPI. Clear by software (by setting the FIFOCONC bit) to send the FIFO data and to switch the bank. For IN Pipe: Set by hardware when a new IN message is stored in the current bank, at the same time than RXINI. Clear by software (by setting the FIFOCONC bit) to free the current bank and to switch to the next bank. • PDISHDMA: Pipe Interrupts Disable HDMA Request Enable See EPDISHDMA (UECONX register). • PFREEZE: Pipe Freeze Set by software (by setting the PFREEZES bit) to Freeze the Pipe requests generation. Clear by software (by setting the PFREEZEC bit) to enable the Pipe request generation. This bit is set by hardware when: - the pipe is not configured - a STALL handshake has been received on this Pipe - An error occurs on the Pipe (PERR = 1) - (INRQ+1) In requests have been processed This bit is set at 1 by hardware after a Pipe reset or a Pipe enable. • RSTDT: Reset Data Toggle Set by software (by setting the RSTDTS bit) to reset the Data Toggle to its initial value for the current Pipe. Cleared by hardware when proceed. 625 32058H–AVR32–03/09 AT32UC3A 30.8.3.17 USB Pipe X Control Clear Register (UPCONXCLR) 0x0620 + X . 0x04 UPCONXCLR, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 PFREEZEC w 0 9 – 16 PDISHDMAC w 0 8 – 15 – 14 FIFOCONC w 0 6 RXSTALLDEC/ CRCERREC w 0 13 – 12 NBUSYBKEC w 0 4 NAKEDEC w 0 11 – 10 – 7 SHORT PACKETIEC w 0 5 OVERFIEC w 0 3 PERREC w 0 2 TXSTPEC/ UNDERFIEC w 0 1 TXOUTEC w 0 0 RXINEC w 0 • RXINEC: Received IN Data Interrupt Enable Clear Set to clear RXINE. Clearing has no effect. Always read as 0. • TXOUTEC: Transmitted OUT Data Interrupt Enable Clear Set to clear TXOUTE. Clearing has no effect. Always read as 0. • TXSTPEC: Transmitted SETUP Interrupt Enable Clear Set to clear TXSTPE. Clearing has no effect. Always read as 0. • UNDERFIEC: Underflow Interrupt Enable Clear Set to clear UNDERFIE. Clearing has no effect. Always read as 0. • PERREC: Pipe Error Interrupt Enable Clear Set to clear PERRE. 626 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKEDEC: NAKed Interrupt Enable Clear Set to clear NAKEDE. Clearing has no effect. Always read as 0. • OVERFIEC: Overflow Interrupt Enable Clear Set to clear OVERFIE. Clearing has no effect. Always read as 0. • RXSTALLDEC: Received STALLed Interrupt Enable Clear Set to clear RXSTALLDE. Clearing has no effect. Always read as 0. • CRCERREC: CRC Error Interrupt Enable Clear Set to clear CRCERRE. Clearing has no effect. Always read as 0. • SHORTPACKETIEC: Short Packet Interrupt Enable Clear Set to clear SHORTPACKETIE. Clearing has no effect. Always read as 0. • NBUSYBKEC: Number of Busy Banks Interrupt Enable Clear Set to clear NBUSYBKE. Clearing has no effect. Always read as 0. • FIFOCONC: FIFO Control Clear Set to clear FIFOCON. Clearing has no effect. Always read as 0. • PDISHDMAC: Pipe Interrupts Disable HDMA Request Enable Clear Set to clear PDISHDMA. Clearing has no effect. Always read as 0. • PFREEZEC: Pipe Freeze Clear Set to clear PFREEZE. 627 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. 628 32058H–AVR32–03/09 AT32UC3A 30.8.3.18 USB Pipe X Control Set Register (UPCONXSET) 0x05F0 + X . 0x04 UPCONXSET, X in [0..6] Write-Only 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Read Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 RSTDTS w 0 10 – 17 PFREEZES w 0 9 – 16 PDISHDMAS w 0 8 – 15 – 14 – 13 – 12 NBUSYBKES w 0 4 NAKEDES w 0 11 – 7 SHORT PACKETIES w 0 6 RXSTALLDES/ CRCERRES w 0 5 OVERFIES w 0 3 PERRES w 0 2 TXSTPES/ UNDERFIES w 0 1 TXOUTES w 0 0 RXINES w 0 • RXINES: Received IN Data Interrupt Enable Set Set to set RXINE. Clearing has no effect. Always read as 0. • TXOUTE: Transmitted OUT Data Interrupt Enable Set Set to set RXINE. Clearing has no effect. Always read as 0. • TXSTPES: Transmitted SETUP Interrupt Enable Set Set to set TXSTPE. Clearing has no effect. Always read as 0. • UNDERFIES: Underflow Interrupt Enable Set Set to set UNDERFIE. Clearing has no effect. Always read as 0. • PERRES: Pipe Error Interrupt Enable Set Set to set PERRE. 629 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. • NAKEDES: NAKed Interrupt Enable Set Set to set NAKEDE. Clearing has no effect. Always read as 0. • OVERFIES: Overflow Interrupt Enable Set Set to set OVERFIE. Clearing has no effect. Always read as 0. • RXSTALLDES: Received STALLed Interrupt Enable Set Set to set RXSTALLDE. Clearing has no effect. Always read as 0. • CRCERRES: CRC Error Interrupt Enable Set Set to set CRCERRE. Clearing has no effect. Always read as 0. • SHORTPACKETIES: Short Packet Interrupt Enable Set Set to set SHORTPACKETIE. Clearing has no effect. Always read as 0. • NBUSYBKES: Number of Busy Banks Interrupt Enable Set Set to set NBUSYBKE. Clearing has no effect. Always read as 0. • PDISHDMAS: Pipe Interrupts Disable HDMA Request Enable Set Set to set PDISHDMA. Clearing has no effect. Always read as 0. • PFREEZES: Pipe Freeze Set Set to set PFREEZE. Clearing has no effect. Always read as 0. • RSTDTS: Reset Data Toggle Set Set to set RSTDT. 630 32058H–AVR32–03/09 AT32UC3A Clearing has no effect. Always read as 0. 631 32058H–AVR32–03/09 AT32UC3A 30.8.3.19 USB Pipe X IN Request Register (UPINRQX) 0x0650 + X . 0x04 UPINRQX, X in [0..6] Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 INMODE rw 0 0 7 6 5 4 INRQ rwu 3 2 1 0 0 0 0 0 0 0 0 • INRQ: IN Request Number before Freeze Enter the number of IN transactions before the USB controller freezes the pipe. The USB controller will perform (INRQ+1) IN requests before to freeze the Pipe. This counter is automatically decreased by 1 each time a IN request has been successfully performed. This register has no effect when the INMODE bit is set (infinite IN requests generation till the pipe is not frozen). • INMODE: IN Request Mode Set this bit to allow the USB controller to perform infinite IN requests when the Pipe is not frozen. Clear this bit to perform a pre-defined number of IN requests. This number is the INRQ field. 632 32058H–AVR32–03/09 AT32UC3A 30.8.3.20 USB Pipe X Error Register (UPERRX) 0x0680 + X . 0x04 UPERRX, X in [0..6] Read/Write 0x00000000 30 – 29 – 28 – 27 – 26 – 25 – 24 – Offset: Register Name: Access Type: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 COUNTER rwu 0 5 0 4 CRC16 rwu 0 3 TIMEOUT rwu 0 2 PID rwu 0 1 DATAPID rwu 0 0 DATATGL rwu 0 • DATATGL: Data Toggle Error Set by hardware when a data toggle error has been detected. Shall be cleared by software. Setting by software has no effect. • DATAPID: Data PID Error Set by hardware when a data PID error has been detected. Shall be cleared by software. Setting by software has no effect. • PID: PID Error Set by hardware when a PID error has been detected. Shall be cleared by software. Setting by software has no effect. • TIMEOUT: Time-Out Error Set by hardware when a Timeout error has been detected. Shall be cleared by software. Setting by software has no effect. • CRC16: CRC16 Error Set by hardware when a CRC16 error has been detected. Shall be cleared by software. Setting by software has no effect. • COUNTER: Error Counter Set by hardware when a CRC16 error has been detected. Shall be cleared by software. Setting by software has no effect. 633 32058H–AVR32–03/09 AT32UC3A 30.8.3.21 USB Host DMA Channel X Next Descriptor Address Register (UHDMAX_NEXTDESC) 0x0710 + (X - 1) . 0x10 UHDMAX_NEXTDESC, X in [1..6] Read/Write 0x00000000 30 29 28 27 NXT_DESC_ADDR rwu 0 0 20 19 NXT_DESC_ADDR rwu 0 0 12 11 NXT_DESC_ADDR rwu 0 0 4 3 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 0 23 0 22 0 21 0 18 0 17 0 16 0 15 0 14 0 13 0 10 0 9 0 8 0 7 0 0 0 2 – 0 1 – 0 0 – 0 6 5 NXT_DESC_ADDR rwu 0 0 0 Same as ”USB Device DMA Channel X Next Descriptor Address Register (UDDMAX_NEXTDESC)” on page 591. 634 32058H–AVR32–03/09 AT32UC3A 30.8.3.22 USB Host DMA Channel X HSB Address Register (UHDMAX_ADDR) 0x0714 + (X - 1) . 0x10 UHDMAX_ADDR, X in [1..6] Read/Write 0x00000000 30 29 28 HSB_ADDR rwu 0 23 0 22 0 21 0 20 HSB_ADDR rwu 0 15 0 14 0 13 0 12 HSB_ADDR rwu 0 7 0 6 0 5 0 4 HSB_ADDR rwu 0 0 0 0 0 0 0 0 0 3 0 2 0 1 0 0 0 11 0 10 0 9 0 8 0 19 0 18 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 Same as ”USB Device DMA Channel X HSB Address Register (UDDMAX_ADDR)” on page 592. 635 32058H–AVR32–03/09 AT32UC3A 30.8.3.23 USB Host DMA Channel X Control Register (UHDMAX_CONTROL) 0x0718 + (X - 1) . 0x10 UHDMAX_CONTROL, X in [1..6] Read/Write 0x00000000 30 29 28 27 CH_BYTE_LENGTH rwu 0 0 20 19 CH_BYTE_LENGTH rwu 0 0 12 – 11 – 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 0 23 0 22 0 21 0 18 0 17 0 16 0 15 – 0 14 – 0 13 – 0 10 – 0 9 – 0 8 – 7 BURST_LOCK _EN rwu 0 6 DESC_LD_ IRQ_EN rwu 0 5 EOBUFF_ IRQ_EN rwu 0 4 EOT_IRQ_EN rwu 0 3 DMAEND_EN rwu 0 2 BUFF_CLOSE _IN_EN rwu 0 1 LD_NXT_CH_ DESC_EN rwu 0 0 CH_EN rwu 0 Same as ”USB Device DMA Channel X Control Register (UDDMAX_CONTROL)” on page 593. (just replace the IN endpoint term by OUT endpoint, and vice-versa) 636 32058H–AVR32–03/09 AT32UC3A 30.8.3.24 USB Host DMA Channel X Status Register (UHDMAX_STATUS) 0x071C + (X - 1) . 0x10 UHDMAX_STATUS, X in [1..6] Read/Write 0x00000000 30 29 28 CH_BYTE_CNT ru 0 23 0 22 0 21 0 20 CH_BYTE_CNT ru 0 15 – 0 14 – 0 13 – 0 12 – 0 11 – 0 10 – 0 9 – 0 8 – 0 19 0 18 0 17 0 16 27 26 25 24 Offset: Register Name: Access Type: Reset Value: 31 7 – 6 DESC_LD_ STA ru 0 5 EOCH_BUFF_ STA ru 0 4 EOT_STA ru 0 3 – 2 – 1 CH_ACTIVE rwu 0 0 CH_EN rwu 0 Same as ”USB Device DMA Channel X Status Register (UDDMAX_STATUS)” on page 595. 637 32058H–AVR32–03/09 AT32UC3A 30.8.4 USB Pipe/Endpoint X FIFO Data Register (USB_FIFOX_DATA) Note that this register can be accessed even if USBE = 0 or FRZCLK = 1. Disabling the USB controller (by clearing the USBE bit) does not reset the DPRAM. 638 32058H–AVR32–03/09 AT32UC3A 31. Timer/Counter (TC) Rev: 2.2.2.1 31.1 Features • Three 16-bit Timer Counter Channels • A 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 • Internal Interrupt Signal • Two Global Registers that Act on All Three TC Channels 31.2 Description The Timer Counter (TC) 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. Each channel has three external clock inputs, five internal clock inputs and two multi-purpose input/output signals which can be configured by the user. Each channel drives an internal interrupt signal which can be programmed to generate processor interrupts. The Timer Counter block has two global registers which act upon all three TC channels. The Block Control Register allows the three channels to be started simultaneously with the same instruction. The Block Mode Register defines the external clock inputs for each channel, allowing them to be chained. 639 32058H–AVR32–03/09 AT32UC3A 31.3 Block Diagram Figure 31-1. Timer Counter Block Diagram Parallel I/O Controller TCLK0 TIMER_CLOCK2 TIMER_CLOCK1 TIOA1 TIMER_CLOCK3 TCLK0 TCLK1 TCLK2 TIOA0 TIOB0 TIOA2 TCLK1 XC0 XC1 XC2 TC0XC0S Timer/Counter Channel 0 TIOA TIOA0 TIOB TIMER_CLOCK4 TIMER_CLOCK5 TCLK2 TIOB0 SYNC INT0 TCLK0 TCLK1 TIOA0 TIOA2 TCLK2 XC0 XC1 XC2 TC1XC1S SYNC Timer/Counter Channel 1 TIOA TIOA1 TIOB TIOB1 INT1 TIOA1 TIOB1 TCLK0 TCLK1 TCLK2 TIOA0 TIOA1 XC0 XC1 XC2 TC2XC2S Timer/Counter Channel 2 TIOA TIOA2 TIOB TIOB2 SYNC TIOA2 TIOB2 INT2 Timer Counter Interrupt Controller Table 31-1. Signal Name Description Signal Name XC0, XC1, XC2 TIOA Description External Clock Inputs Capture Mode: Timer Counter Input Waveform Mode: Timer Counter Output Capture Mode: Timer Counter Input Waveform Mode: Timer Counter Input/Output Interrupt Signal Output Synchronization Input Signal Block/Channel Channel Signal TIOB INT SYNC 640 32058H–AVR32–03/09 AT32UC3A 31.4 Pin Name List Table 31-2. Pin Name TC pin list Description External Clock Input I/O Line A I/O Line B Type Input I/O I/O TCLK0-TCLK2 TIOA0-TIOA2 TIOB0-TIOB2 31.5 31.5.1 Product Dependencies I/O Lines The pins used for interfacing the compliant external devices may be multiplexed with PIO lines. The programmer must first program the PIO controllers to assign the TC pins to their peripheral functions. 31.5.2 Debug operation The Timer Counter clocks are frozen during debug operation, unless the OCD system keeps peripherals running in debug operation. 31.5.3 Power Management The Timer Counter clock is generated by the power manager. Before using the TC, the programmer must ensure that the TC clock is enabled in the power manager. 31.5.4 Interrupt The TC has an interrupt line connected to the interrupt controller. Handling the TC interrupt requires programming the interrupt controller before configuring the TC. 31.6 31.6.1 Functional Description TC Description The three channels of the Timer Counter are independent and identical in operation. The registers for channel programming are listed in Table 31-4 on page 654. 31.6.1.1 16-bit Counter Each channel is organized around a 16-bit counter. The value of the counter is incremented at each positive edge of the selected clock. When the counter has reached the value 0xFFFF and passes to 0x0000, an overflow occurs and the COVFS bit in SR (Status Register) is set. The current value of the counter is accessible in real time by reading the Counter Value Register, CV. The counter can be reset by a trigger. In this case, the counter value passes to 0x0000 on the next valid edge of the selected clock. 31.6.1.2 Clock Selection At block level, input clock signals of each channel can either be connected to the external inputs TCLK0, TCLK1 or TCLK2, or be connected to the configurable I/O signals TIOA0, TIOA1 or TIOA2 for chaining by programming the BMR (Block Mode). See Figure 31-2. 641 32058H–AVR32–03/09 AT32UC3A Each channel can independently select an internal or external clock source for its counter: • Internal clock signals: TIMER_CLOCK1, TIMER_CLOCK2, TIMER_CLOCK3, TIMER_CLOCK4, TIMER_CLOCK5. The Peripherals Chapter details the connection of these clock sources. • External clock signals: XC0, XC1 or XC2. The Peripherals Chapter details the connection of these clock sources. This selection is made by the TCCLKS bits in the TC Channel Mode Register . The selected clock can be inverted with the CLKI bit in CMR. This allows counting on the opposite edges of the clock. The burst function allows the clock to be validated when an external signal is high. The BURST parameter in the Mode Register defines this signal (none, XC0, XC1, XC2). Note: In all cases, if an external clock is used, the duration of each of its levels must be longer than the master clock period. The external clock frequency must be at least 2.5 times lower than the master clock Figure 31-2. Clock Selection TCCLKS TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 TIMER_CLOCK5 XC0 XC1 XC2 CLKI Selected Clock BURST 1 31.6.1.3 Clock Control The clock of each counter can be controlled in two different ways: it can be enabled/disabled and started/stopped. See Figure 31-3. • The clock can be enabled or disabled by the user with the CLKEN and the CLKDIS commands in the Control Register. In Capture Mode it can be disabled by an RB load event if LDBDIS is set to 1 in CMR. In Waveform Mode, it can be disabled by an RC Compare event if CPCDIS is set to 1 in CMR. When disabled, the start or the stop actions have no effect: only a CLKEN command in the Control Register can re-enable the clock. When the clock is enabled, the CLKSTA bit is set in the Status Register. • The clock can also be started or stopped: a trigger (software, synchro, external or compare) always starts the clock. The clock can be stopped by an RB load event in Capture Mode 642 32058H–AVR32–03/09 AT32UC3A (LDBSTOP = 1 in CMR) or a RC compare event in Waveform Mode (CPCSTOP = 1 in CMR). The start and the stop commands have effect only if the clock is enabled. Figure 31-3. Clock Control Selected Clock Trigger CLKSTA CLKEN CLKDIS Q Q S R S R Counter Clock Stop Event Disable Event 31.6.1.4 TC Operating Modes Each channel can independently operate in two different modes: • Capture Mode provides measurement on signals. • Waveform Mode provides wave generation. The TC Operating Mode is programmed with the WAVE bit in the TC Channel Mode Register. In Capture Mode, TIOA and TIOB are configured as inputs. In Waveform Mode, TIOA is always configured to be an output and TIOB is an output if it is not selected to be the external trigger. 31.6.1.5 Trigger A trigger resets the counter and starts the counter clock. Three types of triggers are common to both modes, and a fourth external trigger is available to each mode. The following triggers are common to both modes: • Software Trigger: Each channel has a software trigger, available by setting SWTRG in CCR. • SYNC: Each channel has a synchronization signal SYNC. When asserted, this signal has the same effect as a software trigger. The SYNC signals of all channels are asserted simultaneously by writing BCR (Block Control) with SYNC set. • Compare RC Trigger: RC is implemented in each channel and can provide a trigger when the counter value matches the RC value if CPCTRG is set in CMR. The channel can also be configured to have an external trigger. In Capture Mode, the external trigger signal can be selected between TIOA and TIOB. In Waveform Mode, an external event can be programmed on one of the following signals: TIOB, XC0, XC1 or XC2. This external event can then be programmed to perform a trigger by setting ENETRG in CMR. 643 32058H–AVR32–03/09 AT32UC3A If an external trigger is used, the duration of the pulses must be longer than the master clock period in order to be detected. Regardless of the trigger used, it will be taken into account at the following active edge of the selected clock. This means that the counter value can be read differently from zero just after a trigger, especially when a low frequency signal is selected as the clock. 31.6.2 Capture Operating Mode This mode is entered by clearing the WAVE parameter in CMR (Channel Mode Register). Capture Mode allows the TC channel to perform measurements such as pulse timing, frequency, period, duty cycle and phase on TIOA and TIOB signals which are considered as inputs. Figure 31-4 shows the configuration of the TC channel when programmed in Capture Mode. 31.6.2.1 Capture Registers A and B Registers A and B (RA and RB) are used as capture registers. This means that they can be loaded with the counter value when a programmable event occurs on the signal TIOA. The LDRA parameter in CMR defines the TIOA edge for the loading of register A, and the LDRB parameter defines the TIOA edge for the loading of Register B. RA is loaded only if it has not been loaded since the last trigger or if RB has been loaded since the last loading of RA. RB is loaded only if RA has been loaded since the last trigger or the last loading of RB. Loading RA or RB before the read of the last value loaded sets the Overrun Error Flag (LOVRS) in SR (Status Register). In this case, the old value is overwritten. 31.6.2.2 Trigger Conditions In addition to the SYNC signal, the software trigger and the RC compare trigger, an external trigger can be defined. The ABETRG bit in CMR selects TIOA or TIOB input signal as an external trigger. The ETRGEDG parameter defines the edge (rising, falling or both) detected to generate an external trigger. If ETRGEDG = 0 (none), the external trigger is disabled. 644 32058H–AVR32–03/09 TCCLKS CLKI CLKSTA CLKEN CLKDIS 32058H–AVR32–03/09 TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 Q Q R S R S Figure 31-4. Capture Mode TIMER_CLOCK5 XC0 XC1 LDBSTOP BURST LDBDIS XC2 Register C 1 16-bit Counter CLK OVF RESET Trig ABETRG ETRGEDG Edge Detector LDRA LDRB CPCTRG Capture Register A SWTRG Capture Register B Compare RC = SYNC MTIOB TIOB CPCS LOVRS LDRAS LDRBS ETRGS COVFS TC1_SR MTIOA If RA is not loaded or RB is Loaded Edge Detector If RA is Loaded Edge Detector TC1_IMR TIOA Timer/Counter Channel INT AT32UC3A 645 AT32UC3A 31.6.3 Waveform Operating Mode Waveform operating mode is entered by setting the WAVE parameter in CMR (Channel Mode Register). In Waveform Operating Mode the TC channel generates 1 or 2 PWM signals with the same frequency and independently programmable duty cycles, or generates different types of one-shot or repetitive pulses. In this mode, TIOA is configured as an output and TIOB is defined as an output if it is not used as an external event (EEVT parameter in CMR). Figure 31-5 shows the configuration of the TC channel when programmed in Waveform Operating Mode. 31.6.3.1 Waveform Selection Depending on the WAVSEL parameter in CMR (Channel Mode Register), the behavior of CV varies. With any selection, RA, RB and RC can all be used as compare registers. RA Compare is used to control the TIOA output, RB Compare is used to control the TIOB output (if correctly configured) and RC Compare is used to control TIOA and/or TIOB outputs. 646 32058H–AVR32–03/09 BURST Register A WAVSEL Register B Register C ASWTRG 1 16-bit Counter CLK RESET OVF Compare RA = Compare RB = Compare RC = SWTRG BCPC Trig BCPB WAVSEL EEVT BEEVT EEVTEDG ENETRG Edge Detector CPCS CPAS CPBS ETRGS COVFS TC1_SR MTIOB SYNC Output Controller TIOB TC1_IMR BSWTRG Timer/Counter Channel INT Output Controller 32058H–AVR32–03/09 TCCLKS CLKSTA CLKI CLKEN CLKDIS ACPC TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 CPCDIS Q Q R CPCSTOP S R ACPA MTIOA TIMER_CLOCK5 S XC0 XC1 Figure 31-5. Waveform Mode XC2 AEEVT TIOA TIOB AT32UC3A 647 AT32UC3A 31.6.3.2 WAVSEL = 00 When WAVSEL = 00, the value of CV is incremented from 0 to 0xFFFF. Once 0xFFFF has been reached, the value of CV is reset. Incrementation of CV starts again and the cycle continues. See Figure 31-6. An external event trigger or a software trigger can reset the value of CV. It is important to note that the trigger may occur at any time. See Figure 31-7. RC Compare cannot be programmed to generate a trigger in this configuration. At the same time, RC Compare can stop the counter clock (CPCSTOP = 1 in CMR) and/or disable the counter clock (CPCDIS = 1 in CMR). Figure 31-6. WAVSEL= 00 without trigger Counter Value 0xFFFF Counter cleared by compare match with 0xFFFF RC RB RA Waveform Examples TIOB Time TIOA 648 32058H–AVR32–03/09 AT32UC3A Figure 31-7. WAVSEL= 00 with trigger Counter Value 0xFFFF Counter cleared by trigger Counter cleared by compare match with 0xFFFF RC RB RA Waveform Examples TIOB Time TIOA 31.6.3.3 WAVSEL = 10 When WAVSEL = 10, the value of CV is incremented from 0 to the value of RC, then automatically reset on a RC Compare. Once the value of CV has been reset, it is then incremented and so on. See Figure 31-8. It is important to note that CV can be reset at any time by an external event or a software trigger if both are programmed correctly. See Figure 31-9. In addition, RC Compare can stop the counter clock (CPCSTOP = 1 in CMR) and/or disable the counter clock (CPCDIS = 1 in CMR). Figure 31-8. WAVSEL = 10 Without Trigger Counter Value 0xFFFF Counter cleared by compare match with RC RC RB RA Waveform Examples TIOB Time TIOA 649 32058H–AVR32–03/09 AT32UC3A Figure 31-9. WAVSEL = 10 With Trigger Counter Value 0xFFFF Counter cleared by compare match with RC RC RB Counter cleared by trigger RA Waveform Examples TIOB Time TIOA 31.6.3.4 WAVSEL = 01 When WAVSEL = 01, the value of CV is incremented from 0 to 0xFFFF. Once 0xFFFF is reached, the value of CV is decremented to 0, then re-incremented to 0xFFFF and so on. See Figure 31-10. A trigger such as an external event or a software trigger can modify CV at any time. If a trigger occurs while CV is incrementing, CV then decrements. If a trigger is received while CV is decrementing, CV then increments. See Figure 31-11. RC Compare cannot be programmed to generate a trigger in this configuration. At the same time, RC Compare can stop the counter clock (CPCSTOP = 1) and/or disable the counter clock (CPCDIS = 1). 650 32058H–AVR32–03/09 AT32UC3A Figure 31-10. WAVSEL = 01 Without Trigger Counter Value 0xFFFF Counter decremented by compare match with 0xFFFF RC RB RA Waveform Examples TIOB Time TIOA Figure 31-11. WAVSEL = 01 With Trigger Counter Value 0xFFFF Counter decremented by trigger RC RB Counter decremented by compare match with 0xFFFF Counter incremented by trigger RA Waveform Examples TIOB Time TIOA 31.6.3.5 WAVSEL = 11 When WAVSEL = 11, the value of CV is incremented from 0 to RC. Once RC is reached, the value of CV is decremented to 0, then re-incremented to RC and so on. See Figure 31-12. A trigger such as an external event or a software trigger can modify CV at any time. If a trigger occurs while CV is incrementing, CV then decrements. If a trigger is received while CV is decrementing, CV then increments. See Figure 31-13. RC Compare can stop the counter clock (CPCSTOP = 1) and/or disable the counter clock (CPCDIS = 1). 651 32058H–AVR32–03/09 AT32UC3A Figure 31-12. WAVSEL = 11 Without Trigger Counter Value 0xFFFF Counter decremented by compare match with RC RC RB RA Waveform Examples TIOB Time TIOA Figure 31-13. WAVSEL = 11 With Trigger Counter Value 0xFFFF Counter decremented by compare match with RC RC RB Counter decremented by trigger Counter incremented by trigger RA Waveform Examples TIOB Time TIOA 31.6.3.6 External Event/Trigger Conditions An external event can be programmed to be detected on one of the clock sources (XC0, XC1, XC2) or TIOB. The external event selected can then be used as a trigger. The EEVT parameter in CMR selects the external trigger. The EEVTEDG parameter defines the trigger edge for each of the possible external triggers (rising, falling or both). If EEVTEDG is cleared (none), no external event is defined. 652 32058H–AVR32–03/09 AT32UC3A If TIOB is defined as an external event signal (EEVT = 0), TIOB is no longer used as an output and the compare register B is not used to generate waveforms and subsequently no IRQs. In this case the TC channel can only generate a waveform on TIOA. When an external event is defined, it can be used as a trigger by setting bit ENETRG in CMR. As in Capture Mode, the SYNC signal and the software trigger are also available as triggers. RC Compare can also be used as a trigger depending on the parameter WAVSEL. 31.6.3.7 Output Controller The output controller defines the output level changes on TIOA and TIOB following an event. TIOB control is used only if TIOB is defined as output (not as an external event). The following events control TIOA and TIOB: software trigger, external event and RC compare. RA compare controls TIOA and RB compare controls TIOB. Each of these events can be programmed to set, clear or toggle the output as defined in the corresponding parameter in CMR. 653 32058H–AVR32–03/09 AT32UC3A 31.7 Timer Counter (TC) User Interface Table 31-3. Offset 0x00 0x40 0x80 0xC0 0xC4 TC Global Memory Map Name Access See Table 31-4 See Table 31-4 See Table 31-4 BCR BMR Write-only Read/Write – 0 Reset Value Channel/Register TC Channel 0 TC Channel 1 TC Channel 2 TC Block Control Register TC Block Mode Register BCR (Block Control Register) and BMR (Block Mode Register) control the whole TC block. TC channels are controlled by the registers listed in Table 31-4. The offset of each of the channel registers in Table 31-4 is in relation to the offset of the corresponding channel as mentioned in Table 31-4. Table 31-4. Offset 0x00 0x04 0x08 0x0C 0x10 0x14 0x18 0x1C 0x20 0x24 0x28 0x2C Notes: TC Channel Memory Map Register Channel Control Register Channel Mode Register Reserved Reserved Counter Value Register A Register B Register C Status Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register CV RA RB RC SR IER IDR IMR Read-only Read/Write(1) Read/Write (1) Name CCR CMR Access Write-only Read/Write Reset Value – 0 – – 0 0 0 0 0 – – 0 Read/Write Read-only Write-only Write-only Read-only 1. Read-only if WAVE = 0 654 32058H–AVR32–03/09 AT32UC3A 31.7.1 TC Block Control Register BCR Write-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 – 25 – 17 – 9 – 1 – 24 – 16 – 8 – 0 SYNC Register Name: Access Type: 31 – 23 – 15 – 7 – • SYNC: Synchro Command 0 = No effect. 1 = Asserts the SYNC signal which generates a software trigger simultaneously for each of the channels. 655 32058H–AVR32–03/09 AT32UC3A 31.7.2 TC Block Mode Register BMR Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 TC2XC2S 28 – 20 – 12 – 4 27 – 19 – 11 – 3 TC1XC1S 26 – 18 – 10 – 2 25 – 17 – 9 – 1 TC0XC0S 24 – 16 – 8 – 0 Register Name: Access Type: 31 – 23 – 15 – 7 – • TC0XC0S: External Clock Signal 0 Selection TC0XC0S 0 0 1 1 0 1 0 1 Signal Connected to XC0 TCLK0 none TIOA1 TIOA2 • TC1XC1S: External Clock Signal 1 Selection TC1XC1S 0 0 1 1 0 1 0 1 Signal Connected to XC1 TCLK1 none TIOA0 TIOA2 • TC2XC2S: External Clock Signal 2 Selection TC2XC2S 0 0 1 1 0 1 0 1 Signal Connected to XC2 TCLK2 none TIOA0 TIOA1 656 32058H–AVR32–03/09 AT32UC3A 31.7.3 TC Channel Control Register CCR Write-only 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 SWTRG 25 – 17 – 9 – 1 CLKDIS 24 – 16 – 8 – 0 CLKEN Register Name: Access Type: 31 – 23 – 15 – 7 – • CLKEN: Counter Clock Enable Command 0 = No effect. 1 = Enables the clock if CLKDIS is not 1. • CLKDIS: Counter Clock Disable Command 0 = No effect. 1 = Disables the clock. • SWTRG: Software Trigger Command 0 = No effect. 1 = A software trigger is performed: the counter is reset and the clock is started. 657 32058H–AVR32–03/09 AT32UC3A 31.7.4 TC Channel Mode Register: Capture Mode CMR Read/Write 30 – 22 – 14 CPCTRG 6 LDBSTOP 29 – 21 – 13 – 5 BURST 28 – 20 – 12 – 4 27 – 19 LDRB 11 – 3 CLKI 10 ABETRG 2 9 ETRGEDG 1 TCCLKS 0 26 – 18 25 – 17 LDRA 8 24 – 16 Register Name: Access Type: 31 – 23 – 15 WAVE = 0 7 LDBDIS • TCCLKS: Clock Selection TCCLKS 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Clock Selected TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 TIMER_CLOCK5 XC0 XC1 XC2 • CLKI: Clock Invert 0 = Counter is incremented on rising edge of the clock. 1 = Counter is incremented on falling edge of the clock. • BURST: Burst Signal Selection BURST 0 0 1 1 0 1 0 1 The clock is not gated by an external signal. XC0 is ANDed with the selected clock. XC1 is ANDed with the selected clock. XC2 is ANDed with the selected clock. • LDBSTOP: Counter Clock Stopped with RB Loading 0 = Counter clock is not stopped when RB loading occurs. 1 = Counter clock is stopped when RB loading occurs. • LDBDIS: Counter Clock Disable with RB Loading 658 32058H–AVR32–03/09 AT32UC3A 0 = Counter clock is not disabled when RB loading occurs. 1 = Counter clock is disabled when RB loading occurs. • ETRGEDG: External Trigger Edge Selection ETRGEDG 0 0 1 1 0 1 0 1 Edge none rising edge falling edge each edge • ABETRG: TIOA or TIOB External Trigger Selection 0 = TIOB is used as an external trigger. 1 = TIOA is used as an external trigger. • CPCTRG: RC Compare Trigger Enable 0 = RC Compare has no effect on the counter and its clock. 1 = RC Compare resets the counter and starts the counter clock. • WAVE 0 = Capture Mode is enabled. 1 = Capture Mode is disabled (Waveform Mode is enabled). • LDRA: RA Loading Selection LDRA 0 0 1 1 0 1 0 1 Edge none rising edge of TIOA falling edge of TIOA each edge of TIOA • LDRB: RB Loading Selection LDRB 0 0 1 1 0 1 0 1 Edge none rising edge of TIOA falling edge of TIOA each edge of TIOA 659 32058H–AVR32–03/09 AT32UC3A 31.7.5 TC Channel Mode Register: Waveform Mode CMR Read/Write 30 BSWTRG 23 ASWTRG 15 WAVE = 1 7 CPCDIS 14 WAVSEL 6 CPCSTOP 5 BURST 13 22 21 AEEVT 12 ENETRG 4 11 EEVT 3 CLKI 2 29 BEEVT 20 19 ACPC 10 9 EEVTEDG 1 TCCLKS 0 28 27 BCPC 18 17 ACPA 8 26 25 BCPB 16 24 Register Name: Access Type: 31 • TCCLKS: Clock Selection TCCLKS 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Clock Selected TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 TIMER_CLOCK5 XC0 XC1 XC2 • CLKI: Clock Invert 0 = Counter is incremented on rising edge of the clock. 1 = Counter is incremented on falling edge of the clock. • BURST: Burst Signal Selection BURST 0 0 1 1 0 1 0 1 The clock is not gated by an external signal. XC0 is ANDed with the selected clock. XC1 is ANDed with the selected clock. XC2 is ANDed with the selected clock. • CPCSTOP: Counter Clock Stopped with RC Compare 0 = Counter clock is not stopped when counter reaches RC. 1 = Counter clock is stopped when counter reaches RC. • CPCDIS: Counter Clock Disable with RC Compare 660 32058H–AVR32–03/09 AT32UC3A 0 = Counter clock is not disabled when counter reaches RC. 1 = Counter clock is disabled when counter reaches RC. • EEVTEDG: External Event Edge Selection EEVTEDG 0 0 1 1 0 1 0 1 Edge none rising edge falling edge each edge • EEVT: External Event Selection EEVT 0 0 1 1 Note: 0 1 0 1 Signal selected as external event TIOB XC0 XC1 XC2 TIOB Direction input(1) output output output 1. If TIOB is chosen as the external event signal, it is configured as an input and no longer generates waveforms and subsequently no IRQs. • ENETRG: External Event Trigger Enable 0 = The external event has no effect on the counter and its clock. In this case, the selected external event only controls the TIOA output. 1 = The external event resets the counter and starts the counter clock. • WAVSEL: Waveform Selection WAVSEL 0 1 0 1 0 0 1 1 Effect UP mode without automatic trigger on RC Compare UP mode with automatic trigger on RC Compare UPDOWN mode without automatic trigger on RC Compare UPDOWN mode with automatic trigger on RC Compare • WAVE = 1 0 = Waveform Mode is disabled (Capture Mode is enabled). 1 = Waveform Mode is enabled. 661 32058H–AVR32–03/09 AT32UC3A • ACPA: RA Compare Effect on TIOA ACPA 0 0 1 1 0 1 0 1 Effect none set clear toggle • ACPC: RC Compare Effect on TIOA ACPC 0 0 1 1 0 1 0 1 Effect none set clear toggle • AEEVT: External Event Effect on TIOA AEEVT 0 0 1 1 0 1 0 1 Effect none set clear toggle • ASWTRG: Software Trigger Effect on TIOA ASWTRG 0 0 1 1 0 1 0 1 Effect none set clear toggle • BCPB: RB Compare Effect on TIOB BCPB 0 0 Effect none 662 32058H–AVR32–03/09 AT32UC3A BCPB 0 1 1 1 0 1 Effect set clear toggle • BCPC: RC Compare Effect on TIOB BCPC 0 0 1 1 0 1 0 1 Effect none set clear toggle • BEEVT: External Event Effect on TIOB BEEVT 0 0 1 1 0 1 0 1 Effect none set clear toggle • BSWTRG: Software Trigger Effect on TIOB BSWTRG 0 0 1 1 0 1 0 1 Effect none set clear toggle 663 32058H–AVR32–03/09 AT32UC3A 31.7.6 TC Counter Value Register CV Read-only 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 CV 7 6 5 4 CV 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Register Name: Access Type: 31 – 23 – 15 • CV: Counter Value CV contains the counter value in real time. 664 32058H–AVR32–03/09 AT32UC3A 31.7.7 TC Register A RA Read-only if WAVE = 0, Read/Write if WAVE = 1 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 RA 7 6 5 4 RA 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Register Name: Access Type: 31 – 23 – 15 • RA: Register A RA contains the Register A value in real time. 665 32058H–AVR32–03/09 AT32UC3A 31.7.8 TC Register B RB Read-only if WAVE = 0, Read/Write if WAVE = 1 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 RB 7 6 5 4 RB 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Register Name: Access Type: 31 – 23 – 15 • RB: Register B RB contains the Register B value in real time. 666 32058H–AVR32–03/09 AT32UC3A 31.7.9 TC Register C RC Read/Write 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 RC 7 6 5 4 RC 3 2 1 0 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 Register Name: Access Type: 31 – 23 – 15 • RC: Register C RC contains the Register C value in real time. 667 32058H–AVR32–03/09 AT32UC3A 31.7.10 TC Status Register SR Read-only 30 – 22 – 14 – 6 LDRBS 29 – 21 – 13 – 5 LDRAS 28 – 20 – 12 – 4 CPCS 27 – 19 – 11 – 3 CPBS 26 – 18 MTIOB 10 – 2 CPAS 25 – 17 MTIOA 9 – 1 LOVRS 24 – 16 CLKSTA 8 – 0 COVFS Register Name: Access Type: 31 – 23 – 15 – 7 ETRGS Note: Reading the Status Register will also clear the interrupt flag for the corresponding interrupts. • COVFS: Counter Overflow Status 0 = No counter overflow has occurred since the last read of the Status Register. 1 = A counter overflow has occurred since the last read of the Status Register. • LOVRS: Load Overrun Status 0 = Load overrun has not occurred since the last read of the Status Register or WAVE = 1. 1 = RA or RB have been loaded at least twice without any read of the corresponding register since the last read of the Status Register, if WAVE = 0. • CPAS: RA Compare Status 0 = RA Compare has not occurred since the last read of the Status Register or WAVE = 0. 1 = RA Compare has occurred since the last read of the Status Register, if WAVE = 1. • CPBS: RB Compare Status 0 = RB Compare has not occurred since the last read of the Status Register or WAVE = 0. 1 = RB Compare has occurred since the last read of the Status Register, if WAVE = 1. • CPCS: RC Compare Status 0 = RC Compare has not occurred since the last read of the Status Register. 1 = RC Compare has occurred since the last read of the Status Register. • LDRAS: RA Loading Status 0 = RA Load has not occurred since the last read of the Status Register or WAVE = 1. 1 = RA Load has occurred since the last read of the Status Register, if WAVE = 0. • LDRBS: RB Loading Status 0 = RB Load has not occurred since the last read of the Status Register or WAVE = 1. 1 = RB Load has occurred since the last read of the Status Register, if WAVE = 0. • ETRGS: External Trigger Status 0 = External trigger has not occurred since the last read of the Status Register. 1 = External trigger has occurred since the last read of the Status Register. 668 32058H–AVR32–03/09 AT32UC3A • CLKSTA: Clock Enabling Status 0 = Clock is disabled. 1 = Clock is enabled. • MTIOA: TIOA Mirror 0 = TIOA is low. If WAVE = 0, this means that TIOA pin is low. If WAVE = 1, this means that TIOA is driven low. 1 = TIOA is high. If WAVE = 0, this means that TIOA pin is high. If WAVE = 1, this means that TIOA is driven high. • MTIOB: TIOB Mirror 0 = TIOB is low. If WAVE = 0, this means that TIOB pin is low. If WAVE = 1, this means that TIOB is driven low. 1 = TIOB is high. If WAVE = 0, this means that TIOB pin is high. If WAVE = 1, this means that TIOB is driven high. 669 32058H–AVR32–03/09 AT32UC3A 31.7.11 TC Interrupt Enable Register IER Write-only 30 – 22 – 14 – 6 LDRBS 29 – 21 – 13 – 5 LDRAS 28 – 20 – 12 – 4 CPCS 27 – 19 – 11 – 3 CPBS 26 – 18 – 10 – 2 CPAS 25 – 17 – 9 – 1 LOVRS 24 – 16 – 8 – 0 COVFS Register Name: Access Type: 31 – 23 – 15 – 7 ETRGS Note: Reading the Status Register will also clear the interrupt flag for the corresponding interrupts. • COVFS: Counter Overflow 0 = No effect. 1 = Enables the Counter Overflow Interrupt. • LOVRS: Load Overrun 0 = No effect. 1 = Enables the Load Overrun Interrupt. • CPAS: RA Compare 0 = No effect. 1 = Enables the RA Compare Interrupt. • CPBS: RB Compare 0 = No effect. 1 = Enables the RB Compare Interrupt. • CPCS: RC Compare 0 = No effect. 1 = Enables the RC Compare Interrupt. • LDRAS: RA Loading 0 = No effect. 1 = Enables the RA Load Interrupt. • LDRBS: RB Loading 0 = No effect. 1 = Enables the RB Load Interrupt. • ETRGS: External Trigger 0 = No effect. 1 = Enables the External Trigger Interrupt. 670 32058H–AVR32–03/09 AT32UC3A 31.7.12 TC Interrupt Disable Register IDR Write-only 30 – 22 – 14 – 6 LDRBS 29 – 21 – 13 – 5 LDRAS 28 – 20 – 12 – 4 CPCS 27 – 19 – 11 – 3 CPBS 26 – 18 – 10 – 2 CPAS 25 – 17 – 9 – 1 LOVRS 24 – 16 – 8 – 0 COVFS Register Name: Access Type: 31 – 23 – 15 – 7 ETRGS Note: Reading the Status Register will also clear the interrupt flag for the corresponding interrupts. • COVFS: Counter Overflow 0 = No effect. 1 = Disables the Counter Overflow Interrupt. • LOVRS: Load Overrun 0 = No effect. 1 = Disables the Load Overrun Interrupt (if WAVE = 0). • CPAS: RA Compare 0 = No effect. 1 = Disables the RA Compare Interrupt (if WAVE = 1). • CPBS: RB Compare 0 = No effect. 1 = Disables the RB Compare Interrupt (if WAVE = 1). • CPCS: RC Compare 0 = No effect. 1 = Disables the RC Compare Interrupt. • LDRAS: RA Loading 0 = No effect. 1 = Disables the RA Load Interrupt (if WAVE = 0). • LDRBS: RB Loading 0 = No effect. 1 = Disables the RB Load Interrupt (if WAVE = 0). • ETRGS: External Trigger 0 = No effect. 1 = Disables the External Trigger Interrupt. 671 32058H–AVR32–03/09 AT32UC3A 31.7.13 TC Interrupt Mask Register IMR Read-only 30 – 22 – 14 – 6 LDRBS 29 – 21 – 13 – 5 LDRAS 28 – 20 – 12 – 4 CPCS 27 – 19 – 11 – 3 CPBS 26 – 18 – 10 – 2 CPAS 25 – 17 – 9 – 1 LOVRS 24 – 16 – 8 – 0 COVFS Register Name: Access Type: 31 – 23 – 15 – 7 ETRGS Note: Reading the Status Register will also clear the interrupt flag for the corresponding interrupts. • COVFS: Counter Overflow 0 = The Counter Overflow Interrupt is disabled. 1 = The Counter Overflow Interrupt is enabled. • LOVRS: Load Overrun 0 = The Load Overrun Interrupt is disabled. 1 = The Load Overrun Interrupt is enabled. • CPAS: RA Compare 0 = The RA Compare Interrupt is disabled. 1 = The RA Compare Interrupt is enabled. • CPBS: RB Compare 0 = The RB Compare Interrupt is disabled. 1 = The RB Compare Interrupt is enabled. • CPCS: RC Compare 0 = The RC Compare Interrupt is disabled. 1 = The RC Compare Interrupt is enabled. • LDRAS: RA Loading 0 = The Load RA Interrupt is disabled. 1 = The Load RA Interrupt is enabled. • LDRBS: RB Loading 0 = The Load RB Interrupt is disabled. 1 = The Load RB Interrupt is enabled. • ETRGS: External Trigger 0 = The External Trigger Interrupt is disabled. 1 = The External Trigger Interrupt is enabled. 672 32058H–AVR32–03/09 AT32UC3A 32. Pulse Width Modulation Controller (PWM) Rev: 1.3.0.1 32.1 Features • 7 Channels • One 20-bit Counter Per Channel • Common Clock Generator Providing Thirteen Different Clocks – A Modulo n Counter Providing Eleven Clocks – Two Independent Linear Dividers Working on Modulo n Counter Outputs • Independent Channels – Independent Enable Disable Command for Each Channel – Independent Clock Selection for Each Channel – Independent Period and Duty Cycle for Each Channel – Double Buffering of Period or Duty Cycle for Each Channel – Programmable Selection of The Output Waveform Polarity for Each Channel – Programmable Center or Left Aligned Output Waveform for Each Channel 32.2 Description The PWM macrocell controls several channels independently. Each channel controls one square output waveform. Characteristics of the output waveform such as period, duty-cycle and polarity are configurable through the user interface. Each channel selects and uses one of the clocks provided by the clock generator. The clock generator provides several clocks resulting from the division of the PWM macrocell master clock. All PWM macrocell accesses are made through registers mapped on the peripheral bus. Channels can be synchronized, to generate non overlapped waveforms. All channels integrate a double buffering system in order to prevent an unexpected output waveform while modifying the period or the duty-cycle. 673 32058H–AVR32–03/09 AT32UC3A 32.3 Block Diagram Figure 32-1. Pulse Width Modulation Controller Block Diagram PWM Controller PWMx Channel Period Update Duty Cycle Comparator PWMx PWMx Clock Selector Counter PIO PWM0 Channel Period Update Duty Cycle Comparator PWM0 PWM0 Clock Selector Power Manager MCK Counter Interrupt Controller Clock Generator PB Interface Interrupt Generator Peripheral Bus 32.4 I/O Lines Description Each channel outputs one waveform on one external I/O line. Table 32-1. Name PWMx I/O Line Description Description PWM Waveform Output for channel x Type Output 674 32058H–AVR32–03/09 AT32UC3A 32.5 32.5.1 Product Dependencies I/O Lines The pins used for interfacing the PWM may be multiplexed with PIO lines. The programmer must first program the PIO controller to assign the desired PWM pins to their peripheral function. If I/O lines of the PWM are not used by the application, they can be used for other purposes by the PIO controller. Not all PWM outputs may be enabled. If an application requires only four channels, then only four PIO lines will be assigned to PWM outputs. 32.5.2 Debug operation The PWM clock is running during debug operation. 32.5.3 Power Management The PWM clock is generated by the Power Manager. Before using the PWM, the programmer must ensure that the PWM clock is enabled in the Power Manager. However, if the application does not require PWM operations, the PWM clock can be stopped when not needed and be restarted later. In this case, the PWM will resume its operations where it left off. In the PWM description, Master Clock (MCK) is the clock of the peripheral bus to which the PWM is connected. 32.5.4 Interrupt Sources The PWM interrupt line is connected to the interrupt controller. Using the PWM interrupt requires the interrupt controller to be programmed first. 675 32058H–AVR32–03/09 AT32UC3A 32.6 Functional Description The PWM macrocell is primarily composed of a clock generator module and 7 channels. – Clocked by the system clock, MCK, the clock generator module provides 13 clocks. – Each channel can independently choose one of the clock generator outputs. – Each channel generates an output waveform with attributes that can be defined independently for each channel through the user interface registers. 32.6.1 PWM Clock Generator Figure 32-2. Functional View of the Clock Generator Block Diagram MCK modulo n counter MCK MCK/2 MCK/4 MCK/8 MCK/16 MCK/32 MCK/64 MCK/128 MCK/256 MCK/512 MCK/1024 Divider A clkA PREA DIVA PWM_MR Divider B clkB PREB DIVB PWM_MR Caution: Before using the PWM macrocell, the programmer must ensure that the PWM clock in the Power Manager is enabled. The PWM macrocell master clock, MCK, is divided in the clock generator module to provide different clocks available for all channels. Each channel can independently select one of the divided clocks. 676 32058H–AVR32–03/09 AT32UC3A The clock generator is divided in three blocks: – a modulo n counter which provides 11 clocks: FMCK, FMCK/2, FMCK/4, FMCK/8, FMCK/16, FMCK/32, FMCK/64, FMCK/128, FMCK/256, FMCK/512, FMCK/1024 – two linear dividers (1, 1/2, 1/3, ... 1/255) that provide two separate clocks: clkA and clkB Each linear divider can independently divide one of the clocks of the modulo n counter. The selection of the clock to be divided is made according to the PREA (PREB) field of the PWM Mode register (MR). The resulting clock clkA (clkB) is the clock selected divided by DIVA (DIVB) field value in the PWM Mode register (MR). After a reset of the PWM controller, DIVA (DIVB) and PREA (PREB) in the PWM Mode register are set to 0. This implies that after reset clkA (clkB) are turned off. At reset, all clocks provided by the modulo n counter are turned off except clock “clk”. This situation is also true when the PWM master clock is turned off through the Power Management Controller. 32.6.2 32.6.2.1 PWM Channel Block Diagram Figure 32-3. Functional View of the Channel Block Diagram inputs from clock generator Channel Clock Selector Internal Counter Comparator PWMx output waveform inputs from Peripheral Bus Each of the 7 channels is composed of three blocks: • A clock selector which selects one of the clocks provided by the clock generator described in Section 32.6.1 ”PWM Clock Generator” on page 676. • An internal counter clocked by the output of the clock selector. This internal counter is incremented or decremented according to the channel configuration and comparators events. The size of the internal counter is 20 bits. • A comparator used to generate events according to the internal counter value. It also computes the PWMx output waveform according to the configuration. 32.6.2.2 Waveform Properties The different properties of output waveforms are: • the internal clock selection. The internal channel counter is clocked by one of the clocks provided by the clock generator described in the previous section. This channel parameter is defined in the CPRE field of the CMRx register. This field is reset at 0. • the waveform period. This channel parameter is defined in the CPRD field of the CPRDx register. 677 32058H–AVR32–03/09 AT32UC3A - If the waveform is left aligned, then the output waveform period depends on the counter source clock and can be calculated: By using the Master Clock (MCK) divided by an X given prescaler value (with X being 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024), the resulting period formula will be: ( X × CPRD ) -----------------------------MCK By using a Master Clock divided by one of both DIVA or DIVB divider, the formula becomes, respectively: ( CRPD × DIVA ) ----------------------------------------- or ( CRPD × DIVAB ) --------------------------------------------MCK MCK If the waveform is center aligned then the output waveform period depends on the counter source clock and can be calculated: By using the Master Clock (MCK) divided by an X given prescaler value (with X being 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula will be: ( 2 × X × CPRD ) ---------------------------------------MCK By using a Master Clock divided by one of both DIVA or DIVB divider, the formula becomes, respectively: ( 2 × CPRD × DIVA ) --------------------------------------------------- or ( 2 × CPRD × DIVB ) --------------------------------------------------MCK MCK • the waveform duty cycle. This channel parameter is defined in the CDTY field of the CDTYx register. If the waveform is left aligned then: duty cycle = ( period – 1 ⁄ fchannel_x_clock × CDTY ) ------------------------------------------------------------------------------------------------------period If the waveform is center aligned, then: ( ( period ⁄ 2 ) – 1 ⁄ fchannel_x_clock × CDTY ) ) duty cycle = ---------------------------------------------------------------------------------------------------------------------( period ⁄ 2 ) • the waveform polarity. At the beginning of the period, the signal can be at high or low level. This property is defined in the CPOL field of the CMRx register. By default the signal starts by a low level. • the waveform alignment. The output waveform can be left or center aligned. Center aligned waveforms can be used to generate non overlapped waveforms. This property is defined in the CALG field of the CMRx register. The default mode is left aligned. 678 32058H–AVR32–03/09 AT32UC3A Figure 32-4. Non Overlapped Center Aligned Waveforms No overlap PWM0 PWM1 Period Note: 1. See Figure 32-5 on page 680 for a detailed description of center aligned waveforms. When center aligned, the internal channel counter increases up to CPRD and.decreases down to 0. This ends the period. When left aligned, the internal channel counter increases up to CPRD and is reset. This ends the period. Thus, for the same CPRD value, the period for a center aligned channel is twice the period for a left aligned channel. Waveforms are fixed at 0 when: • CDTY = CPRD and CPOL = 0 • CDTY = 0 and CPOL = 1 Waveforms are fixed at 1 (once the channel is enabled) when: • CDTY = 0 and CPOL = 0 • CDTY = CPRD and CPOL = 1 The waveform polarity must be set before enabling the channel. This immediately affects the channel output level. Changes on channel polarity are not taken into account while the channel is enabled. 679 32058H–AVR32–03/09 AT32UC3A Figure 32-5. Waveform Properties PWM_MCKx CHIDx(PWM_SR) CHIDx(PWM_ENA) CHIDx(PWM_DIS) Center Aligned CALG(PWM_CMRx) = 1 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Period Output Waveform PWMx CPOL(PWM_CMRx) = 0 Output Waveform PWMx CPOL(PWM_CMRx) = 1 CHIDx(PWM_ISR) PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Left Aligned CALG(PWM_CMRx) = 0 Period Output Waveform PWMx CPOL(PWM_CMRx) = 0 Output Waveform PWMx CPOL(PWM_CMRx) = 1 CHIDx(PWM_ISR) 680 32058H–AVR32–03/09 AT32UC3A 32.6.3 32.6.3.1 PWM Controller Operations Initialization Before enabling the output channel, this channel must have been configured by the software application: • Configuration of the clock generator if DIVA and DIVB are required • Selection of the clock for each channel (CPRE field in the CMRx register) • Configuration of the waveform alignment for each channel (CALG field in the CMRx register) • Configuration of the period for each channel (CPRD in the CPRDx register). Writing in CPRDx Register is possible while the channel is disabled. After validation of the channel, the user must use CUPDx Register to update CPRDx as explained below. • Configuration of the duty cycle for each channel (CDTY in the CDTYx register). Writing in CDTYx Register is possible while the channel is disabled. After validation of the channel, the user must use CUPDx Register to update CDTYx as explained below. • Configuration of the output waveform polarity for each channel (CPOL in the CMRx register) • Enable Interrupts (Writing CHIDx in the IER register) • Enable the PWM channel (Writing CHIDx in the ENA register) It is possible to synchronize different channels by enabling them at the same time by means of writing simultaneously several CHIDx bits in the ENA register. In such a situation, all channels may have the same clock selector configuration and the same period specified. 32.6.3.2 Source Clock Selection Criteria The large number of source clocks can make selection difficult. The relationship between the value in the Period Register (CPRDx) and the Duty Cycle Register (CDTYx) can help the user in choosing. The event number written in the Period Register gives the PWM accuracy. The Duty Cycle quantum cannot be lower than 1 /CPRDx value. The higher the value of CPRDx, the greater the PWM accuracy. For example, if the user sets 15 (in decimal) in CPRDx, the user is able to set a value between 1 up to 14 in CDTYx Register. The resulting duty cycle quantum cannot be lower than 1/15 of the PWM period. 32.6.3.3 Changing the Duty Cycle or the Period It is possible to modulate the output waveform duty cycle or period. To prevent unexpected output waveform, the user must use the update register (PWM_CUPDx) to change waveform parameters while the channel is still enabled. The user can write a new period value or duty cycle value in the update register (CUPDx). This register holds the new value until the end of the current cycle and updates the value for the next cycle. Depending on the CPD field in the CMRx register, CUPDx either updates CPRDx or CDTYx. Note that even if the update register is used, the period must not be smaller than the duty cycle. 681 32058H–AVR32–03/09 AT32UC3A Figure 32-6. Synchronized Period or Duty Cycle Update User's Writing PWM_CUPDx Value 1 0 PWM_CMRx. CPD PWM_CPRDx PWM_CDTYx End of Cycle To prevent overwriting the CUPDx by software, the user can use status events in order to synchronize his software. Two methods are possible. In both, the user must enable the dedicated interrupt in IER at PWM Controller level. The first method (polling method) consists of reading the relevant status bit in ISR Register according to the enabled channel(s). See Figure 32-7. The second method uses an Interrupt Service Routine associated with the PWM channel. Note: Reading the ISR register automatically clears CHIDx flags. Figure 32-7. Polling Method PWM_ISR Read Acknowledgement and clear previous register state Writing in CPD field Update of the Period or Duty Cycle CHIDx = 1 YES Writing in PWM_CUPDx The last write has been taken into account Note: Polarity and alignment can be modified only when the channel is disabled. 682 32058H–AVR32–03/09 AT32UC3A 32.6.3.4 Interrupts Depending on the interrupt mask in the IMR register, an interrupt is generated at the end of the corresponding channel period. The interrupt remains active until a read operation in the ISR register occurs. A channel interrupt is enabled by setting the corresponding bit in the IER register. A channel interrupt is disabled by setting the corresponding bit in the IDR register. 683 32058H–AVR32–03/09 AT32UC3A 32.7 32.7.1 Pulse Width Modulation (PWM) Controller User Interface Register Mapping PWM Controller Registers Register PWM Mode Register PWM Enable Register PWM Disable Register PWM Status Register PWM Interrupt Enable Register PWM Interrupt Disable Register PWM Interrupt Mask Register PWM Interrupt Status Register Reserved Reserved Reserved Channel 0 Mode Register Channel 0 Duty Cycle Register Channel 0 Period Register Channel 0 Counter Register Channel 0 Update Register Reserved Channel 1 Mode Register Channel 1 Duty Cycle Register Channel 1 Period Register Channel 1 Counter Register Channel 1 Update Register ... CMR1 CDTY1 CPRD1 CCNT1 CUPD1 ... Read/Write Read/Write Read/Write Read-only Write-only ... 0x0 0x0 0x0 0x0 ... CMR0 CDTY0 CPRD0 CCNT0 CUPD0 Read/Write Read/Write Read/Write Read-only Write-only 0x0 0x0 0x0 0x0 Name MR ENA DIS SR IER IDR IMR ISR – – Access Read/Write Write-only Write-only Read-only Write-only Write-only Read-only Read-only – – Peripheral Reset Value 0 0 0 0 – – Table 32-2. Offset 0x00 0x04 0x08 0x0C 0x10 0x14 0x18 0x1C 0x4C - 0xF8 0x4C - 0xFC 0x100 - 0x1FC 0x200 0x204 0x208 0x20C 0x210 ... 0x220 0x224 0x228 0x22C 0x230 ... 684 32058H–AVR32–03/09 AT32UC3A 32.7.2 PWM Mode Register MR Read/Write 30 – 22 29 – 21 28 – 20 DIVB 15 – 7 14 – 6 13 – 5 12 – 4 DIVA 11 10 PREA 3 2 1 0 9 8 27 26 PREB 19 18 17 16 25 24 Register Name: Access Type: 31 – 23 • DIVA, DIVB: CLKA, CLKB Divide Factor DIVA, DIVB 0 1 2-255 CLKA, CLKB CLKA, CLKB clock is turned off CLKA, CLKB clock is clock selected by PREA, PREB CLKA, CLKB clock is clock selected by PREA, PREB divided by DIVA, DIVB factor. • PREA, PREB PREA, PREB 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 1 1 1 1 0 0 0 Other 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 MCK. MCK/2 MCK/4 MCK/8 MCK/16 MCK/32 MCK/64 MCK/128 MCK/256 MCK/512 MCK/1024 Reserved Divider Input Clock 685 32058H–AVR32–03/09 AT32UC3A 32.7.3 PWM Enable Register ENA Write-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID 0 = No effect. 1 = Enable PWM output for channel x. 686 32058H–AVR32–03/09 AT32UC3A 32.7.4 PWM Disable Register DIS Write-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID 0 = No effect. 1 = Disable PWM output for channel x. 687 32058H–AVR32–03/09 AT32UC3A 32.7.5 PWM Status Register SR Read-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID 0 = PWM output for channel x is disabled. 1 = PWM output for channel x is enabled. 688 32058H–AVR32–03/09 AT32UC3A 32.7.6 PWM Interrupt Enable Register IER Write-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID. 0 = No effect. 1 = Enable interrupt for PWM channel x. 689 32058H–AVR32–03/09 AT32UC3A 32.7.7 PWM Interrupt Disable Register IDR Write-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID. 0 = No effect. 1 = Disable interrupt for PWM channel x. 690 32058H–AVR32–03/09 AT32UC3A 32.7.8 PWM Interrupt Mask Register IMR Read-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID. 0 = Interrupt for PWM channel x is disabled. 1 = Interrupt for PWM channel x is enabled. 691 32058H–AVR32–03/09 AT32UC3A 32.7.9 PWM Interrupt Status Register ISR Read-only 30 – 22 – 14 – 6 CHID6 29 – 21 – 13 – 5 CHID5 28 – 20 – 12 – 4 CHID4 27 – 19 – 11 – 3 CHID3 26 – 18 – 10 – 2 CHID2 25 – 17 – 9 – 1 CHID1 24 – 16 – 8 – 0 CHID0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CHIDx: Channel ID 0 = No new channel period since the last read of the ISR register. 1 = At least one new channel period since the last read of the ISR register. Note: Reading ISR automatically clears CHIDx flags. 692 32058H–AVR32–03/09 AT32UC3A 32.7.10 PWM Channel Mode Register CMRx Read/Write 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 26 – 18 – 10 CPD 2 CPRE 25 – 17 – 9 CPOL 1 24 – 16 – 8 CALG 0 Register Name: Access Type: 31 – 23 – 15 – 7 – • CPRE: Channel Pre-scaler CPRE 0 0 0 0 0 0 0 0 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 Other 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 MCK MCK/2 MCK/4 MCK/8 MCK/16 MCK/32 MCK/64 MCK/128 MCK/256 MCK/512 MCK/1024 CLKA CLKB Reserved Channel Pre-scaler • CALG: Channel Alignment 0 = The period is left aligned. 1 = The period is center aligned. • CPOL: Channel Polarity 0 = The output waveform starts at a low level. 1 = The output waveform starts at a high level. 693 32058H–AVR32–03/09 AT32UC3A • CPD: Channel Update Period 0 = Writing to the CUPDx will modify the duty cycle at the next period start event. 1 = Writing to the CUPDx will modify the period at the next period start event. 694 32058H–AVR32–03/09 AT32UC3A 32.7.11 PWM Channel Duty Cycle Register CDTYx Register Name: Access Type: 31 30 Read/Write 29 28 CDTY 27 26 25 24 23 22 21 20 CDTY 19 18 17 16 15 14 13 12 CDTY 11 10 9 8 7 6 5 4 CDTY 3 2 1 0 Only the first 20 bits (internal channel counter size) are significant. • CDTY: Channel Duty Cycle Defines the waveform duty cycle. This value must be defined between 0 and CPRD (CPRx). 695 32058H–AVR32–03/09 AT32UC3A 32.7.12 PWM Channel Period Register CPRDx Read/Write 30 29 28 CPRD 23 22 21 20 CPRD 15 14 13 12 CPRD 7 6 5 4 CPRD 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Register Name: Access Type: 31 Only the first 20 bits (internal channel counter size) are significant. • CPRD: Channel Period I f the waveform is left-aligned, then the output waveform period depends on the counter source clock and can be calculated: – By using the Master Clock (MCK) divided by an X given prescaler value (with X being 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula will be: ( X × CPRD ) -----------------------------MCK – By using a Master Clock divided by one of both DIVA or DIVB divider, the formula becomes, respectively: ( CRPD × DIVA ) ----------------------------------------- or ( CRPD × DIVAB ) --------------------------------------------MCK MCK If the waveform is center-aligned, then the output waveform period depends on the counter source clock and can be calculated: – By using the Master Clock (MCK) divided by an X given prescaler value (with X being 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula will be: ( 2 × X × CPRD ) ---------------------------------------MCK – By using a Master Clock divided by one of both DIVA or DIVB divider, the formula becomes, respectively: ( 2 × CPRD × DIVA ) --------------------------------------------------- or ( 2 × CPRD × DIVB ) --------------------------------------------------MCK MCK 696 32058H–AVR32–03/09 AT32UC3A 32.7.13 PWM Channel Counter Register CCNTx Read-only 30 29 28 CNT 23 22 21 20 CNT 15 14 13 12 CNT 7 6 5 4 CNT 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Register Name: Access Type: 31 • CNT: Channel Counter Register Internal counter value. This register is reset when: • the channel is enabled (writing CHIDx in the ENA register). • the counter reaches CPRD value defined in the CPRDx register if the waveform is left aligned. 697 32058H–AVR32–03/09 AT32UC3A 32.7.14 PWM Channel Update Register CUPDx Write-only 30 29 28 CUPD 23 22 21 20 CUPD 15 14 13 12 CUPD 7 6 5 4 CUPD 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 Register Name: Access Type: 31 This register acts as a double buffer for the period or the duty cycle. This prevents an unexpected waveform when modifying the waveform period or duty-cycle. Only the first 20 bits (internal channel counter size) are significant. CPD (CMRx Register) 0 1 The duty-cycle (CDTY in the CDTYx register) is updated with the CUPD value at the beginning of the next period. The period (CPRD in the CPRDx register) is updated with the CUPD value at the beginning of the next period. 698 32058H–AVR32–03/09 AT32UC3A 33. Analog-to-Digital Converter (ADC) Rev: 1.0.0.3 33.1 Features • Integrated Multiplexer Offering Up to Eight Independent Analog Inputs • Individual Enable and Disable of Each Channel • Hardware or Software Trigger – External Trigger Pin – Timer Counter Outputs (Corresponding TIOA Trigger) • PDC Support • Possibility of ADC Timings Configuration • Sleep Mode and Conversion Sequencer – Automatic Wakeup on Trigger and Back to Sleep Mode after Conversions of all Enabled Channels 33.2 Overview The ADC is based on a Successive Approximation Register (SAR) 10-bit Analog-to-Digital Converter (ADC). It also integrates an ADC_NB_CHANNELS-to-1 analog multiplexer, making possible the analog-to-digital conversions of ADC_NB_CHANNELS analog lines. The conversions extend from 0V to ADVREF. The ADC supports an 8-bit or 10-bit resolution mode, and conversion results are reported in a common register for all channels, as well as in a channel-dedicated register. Software trigger, external trigger on rising edge of the TRIGGER pin or internal triggers from Timer Counter output(s) are configurable. The ADC also integrates a Sleep Mode and a conversion sequencer and connects with a PDC channel. These features reduce both power consumption and processor intervention. Finally, the user can configure ADC timings, such as Startup Time and Sample & Hold Time. 699 32058H–AVR32–03/09 AT32UC3A 33.3 Block Diagram Figure 33-1. Analog-to-Digital Converter Block Diagram Timer Counter Channels ADC Trigger Selection TRIGGER Control Logic ADC Interrupt INTC VDDANA ADVREF HSB ADDedicated Analog Inputs ADUser Interface ADSuccessive Approximation Register Analog-to-Digital Converter Peripheral Bridge PDC Analog Inputs Multiplexed With I/O lines ADAD- PIO PB AD- GND 33.4 I/O Lines Description ADC Pins Description Description Analog power supply Reference voltage Analog input channels External trigger Table 33-1. Pin Name VDDANA ADVREF AD0 - AD[ADC_NB_CHANNELS-1] TRIGGER 33.5 33.5.1 Product Dependencies GPIO The pin TRIGGER may be shared with other peripheral functions through the PIO Controller. In this case, the PIO Controller should be set accordingly to assign the pin TRIGGER to the ADC function. 700 32058H–AVR32–03/09 AT32UC3A 33.5.2 Analog Inputs The analog input pins can be multiplexed with PIO lines. In this case, the assignment of the ADC input is automatically done as soon as the corresponding channel is enabled by writing the CHER register . By default, after reset, the PIO line is configured as input with its pull-up enabled and the ADC input is connected to the GND. 33.5.3 Power Manager The ADC is automatically clocked after the first conversion in Normal Mode. In Sleep Mode, the ADC clock is automatically stopped after each conversion. As the logic is small and the ADC cell can be put into Sleep Mode, the Power Manager(PM) has no effect on the ADC behavior. Interrupt Controller The ADC interrupt line is connected on one of the internal sources of the Interrupt Controller. Using the ADC interrupt requires the INTC to be programmed first. Timer Triggers Timer Counters may or may not be used as hardware triggers depending on user requirements. Thus, some or all of the timer counters may be non-connected. 33.5.4 33.5.5 33.5.6 Conversion Performances For performance and electrical characteristics of the ADC, see the DC Characteristics section. 701 32058H–AVR32–03/09 AT32UC3A 33.6 33.6.1 Functional Description Analog-to-digital Conversion The ADC uses the ADC Clock to perform conversions. Converting a single analog value to a 10bit digital data requires Sample and Hold Clock cycles as defined in the field SHTIM of the MR register and 10 ADC Clock cycles. The ADC Clock frequency is selected in the PRESCAL field of the MR register. The ADC clock range is between CLK_ADC/2, if PRESCAL is 0, and CLK_ADC/128, if PRESCAL is set to 63 (0x3F). PRESCAL must be programmed in order to provide an ADC clock frequency according to the parameters given in the Product definition section. 33.6.2 Conversion Reference The conversion is performed on a full range between 0V and the reference voltage pin ADVREF. Analog inputs between these voltages convert to values based on a linear conversion. Conversion Resolution The ADC supports 8-bit or 10-bit resolutions. The 8-bit selection is performed by setting the bit LOWRES in the ADC Mode Register (MR). By default, after a reset, the resolution is the highest and the DATA field in the data registers is fully used. By setting the bit LOWRES, the ADC switches in the lowest resolution and the conversion results can be read in the eight lowest significant bits of the data registers. The two highest bits of the DATA field in the corresponding CDR register and of the LDATA field in the LCDR register read 0. Moreover, when a PDC channel is connected to the ADC, 10-bit resolution sets the transfer request sizes to 16-bit. Setting the bit LOWRES automatically switches to 8-bit data transfers. In this case, the destination buffers are optimized. 33.6.3 702 32058H–AVR32–03/09 AT32UC3A 33.6.4 Conversion Results When a conversion is completed, the resulting 10-bit digital value is stored in the Channel Data Register (CDR) of the current channel and in the ADC Last Converted Data Register (LCDR). The channel EOC bit in the Status Register (SR) is set and the DRDY is set. In the case of a connected PDC channel, DRDY rising triggers a data transfer request. In any case, either EOC and DRDY can trigger an interrupt. Reading one of the CDR registers clears the corresponding EOC bit. Reading LCDR clears the DRDY bit and the EOC bit corresponding to the last converted channel. Figure 33-2. EOCx and DRDY Flag Behavior Write CR With START=1 Read CDRx Write CR With START=1 Read LCDR CHx(CHSR) EOCx(SR) Conversion Time Conversion Time DRDY(SR) 703 32058H–AVR32–03/09 AT32UC3A If the CDR is not read before further incoming data is converted, the corresponding Overrun Error (OVRE) flag is set in the Status Register (SR). In the same way, new data converted when DRDY is high sets the bit GOVRE (General Overrun Error) in SR. The OVRE and GOVRE flags are automatically cleared when SR is read. Figure 33-3. GOVRE and OVREx Flag Behavior Read SR TRIGGER CH0(CHSR) CH1(CHSR) LCDR CRD0 Undefined Data Undefined Data Undefined Data Data A Data A Data B Data C Data C CRD1 Data B EOC0(SR) Conversion Conversion Read CDR0 EOC1(SR) Conversion Read CDR1 GOVRE(SR) DRDY(ASR) OVRE0(SR) Warning: If the corresponding channel is disabled during a conversion or if it is disabled and then reenabled during a conversion, its associated data and its corresponding EOC and OVRE flags in SR are unpredictable. 704 32058H–AVR32–03/09 AT32UC3A 33.6.5 Conversion Triggers Conversions of the active analog channels are started with a software or a hardware trigger. The software trigger is provided by writing the Control Register (CR) with the bit START at 1. The hardware trigger can be one of the TIOA outputs of the Timer Counter channels, or the external trigger input of the ADC (TRIGGER). The hardware trigger is selected with the field TRGSEL in the Mode Register (MR). The selected hardware trigger is enabled with the bit TRGEN in the Mode Register (MR). If a hardware trigger is selected, the start of a conversion is detected at each rising edge of the selected signal. If one of the TIOA outputs is selected, the corresponding Timer Counter channel must be programmed in Waveform Mode. Only one start command is necessary to initiate a conversion sequence on all the channels. The ADC hardware logic automatically performs the conversions on the active channels, then waits for a new request. The Channel Enable (CHER) and Channel Disable (CHDR) Registers enable the analog channels to be enabled or disabled independently. If the ADC is used with a PDC, only the transfers of converted data from enabled channels are performed and the resulting data buffers should be interpreted accordingly. Warning: Enabling hardware triggers does not disable the software trigger functionality. Thus, if a hardware trigger is selected, the start of a conversion can be initiated either by the hardware or the software trigger. 33.6.6 Sleep Mode and Conversion Sequencer The ADC Sleep Mode maximizes power saving by automatically deactivating the ADC when it is not being used for conversions. Sleep Mode is selected by setting the bit SLEEP in the Mode Register MR. The SLEEP mode is automatically managed by a conversion sequencer, which can automatically process the conversions of all channels at lowest power consumption. When a start conversion request occurs, the ADC is automatically activated. As the analog cell requires a start-up time, the logic waits during this time and starts the conversion on the enabled channels. When all conversions are complete, the ADC is deactivated until the next trigger. Triggers occurring during the sequence are not taken into account. The conversion sequencer allows automatic processing with minimum processor intervention and optimized power consumption. Conversion sequences can be performed periodically using a Timer/Counter output. The periodic acquisition of several samples can be processed automatically without any intervention of the processor thanks to the PDC. Note: The reference voltage pins always remain connected in normal mode as in sleep mode. 705 32058H–AVR32–03/09 AT32UC3A 33.6.7 ADC Timings Each ADC has its own minimal Startup Time that is programmed through the field STARTUP in the Mode Register MR. In the same way, a minimal Sample and Hold Time is necessary for the ADC to guarantee the best converted final value between two channels selection. This time has to be programmed through the bitfield SHTIM in the Mode Register MR. Warning: No input buffer amplifier to isolate the source is included in the ADC. This must be taken into consideration to program a precise value in the SHTIM field. See the section, ADC Characteristics in the product datasheet. 706 32058H–AVR32–03/09 AT32UC3A 33.7 User Interface ADC Register Mapping Register Control Register Mode Register Channel Enable Register Channel Disable Register Channel Status Register Status Register Last Converted Data Register Interrupt Enable Register Interrupt Disable Register Interrupt Mask Register Channel Data Register 0 ...(if implemented) Channel Data Register 7(if implemented) Version Register Name CR MR CHER CHDR CHSR SR LCDR IER IDR IMR CDR0 ... CDR7 VERSION Access Write-only Read/Write Write-only Write-only Read-only Read-only Read-only Write-only Write-only Read-only Read-only ... Read-only Read-only Reset State – 0x00000000 – – 0x00000000 0x000C0000 0x00000000 – – 0x00000000 0x00000000 ... 0x00000000 – Table 33-2. Offset 0x00 0x04 0x10 0x14 0x18 0x1C 0x20 0x24 0x28 0x2C 0x30 ... 0x4C 0xFC 707 32058H–AVR32–03/09 AT32UC3A 33.7.1 Name: Control Register CR Write-only 0x00 – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – – – – – – START SWRST • START: Start Conversion 0 = No effect. 1 = Begins analog-to-digital conversion. • SWRST: Software Reset 0 = No effect. 1 = Resets the ADC simulating a hardware reset. 708 32058H–AVR32–03/09 AT32UC3A 33.7.2 Name: Mode Register MR Read/Write 0x04 0x00000000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 19 18 SHTIM 17 16 – 15 – 14 – 13 12 11 STARTUP 10 9 8 – 7 – 6 5 4 3 PRESCAL 2 1 0 – – SLEEP LOWRES TRGSEL TRGEN • SHTIM: Sample & Hold Time Sample & Hold Time = (SHTIM+1) / ADCClock • STARTUP: Start Up Time Startup Time = (STARTUP+1) * 8 / ADCClock • PRESCAL: Prescaler Rate Selection ADCClock = CLK_ADC / ( (PRESCAL+1) * 2 ) • SLEEP: Sleep Mode SLEEP 0 1 Selected Mode Normal Mode Sleep Mode • LOWRES: Resolution LOWRES 0 1 Selected Resolution 10-bit resolution 8-bit resolution • TRGSEL: Trigger Selection TRGSEL 0 0 0 0 1 0 0 1 1 0 0 1 0 1 0 Selected TRGSEL Internal Trigger 0, depending of chip integration Internal Trigger 1, depending of chip integration Internal Trigger 2, depending of chip integration Internal Trigger 3, depending of chip integration Internal Trigger 4, depending of chip integration 709 32058H–AVR32–03/09 AT32UC3A TRGSEL 1 1 1 0 1 1 1 0 1 Selected TRGSEL Internal Trigger 5, depending of chip integration External trigger Reserved • TRGEN: Trigger Enable TRGEN 0 1 Selected TRGEN Hardware triggers are disabled. Starting a conversion is only possible by software. Hardware trigger selected by TRGSEL field is enabled. 710 32058H–AVR32–03/09 AT32UC3A 33.7.3 Name: Channel Enable Register CHER Write-only 0x10 – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CH2 CH6 CH5 CH4 CH3 CH2 CH1 CH0 • CHx: Channel x Enable 0 = No effect. 1 = Enables the corresponding channel(if implemented). 711 32058H–AVR32–03/09 AT32UC3A 33.7.4 Name: Channel Disable Register CHDR Write-only 0x14 – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CH7 CH6 CH5 CH4 CH3 CH2 CH1 CH0 • CHx: Channel x Disable 0 = No effect. 1 = Disables the corresponding channel(if implemented). Warning: If the corresponding channel is disabled during a conversion or if it is disabled then reenabled during a conversion, its associated data and its corresponding EOC and OVRE flags in SR are unpredictable. 712 32058H–AVR32–03/09 AT32UC3A 33.7.5 Name: Channel Status Register CHSR Read-only 0x18 0x00000000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CH7 CH6 CH5 CH4 CH3 CH2 CH1 CH0 • CHx: Channel x Status 0 = Corresponding channel is disabled(if implemented). 1 = Corresponding channel is enabled(if implemented). 713 32058H–AVR32–03/09 AT32UC3A 33.7.6 Name: Status Register SR Read-only 0x1C 0x000C0000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 RXBUFF 11 ENDRX 10 GOVRE 9 DRDY 8 OVRE7 7 OVRE6 6 OVRE5 5 OVRE4 4 OVRE3 3 OVRE2 2 OVRE1 1 OVRE0 0 EOC7 EOC6 EOC5 EOC4 EOC3 EOC2 EOC1 EOC0 • RXBUFF: RX Buffer Full 0 = RCR or RNCR have a value other than 0. 1 = Both RCR and RNCR have a value of 0. • ENDRX: End of RX Buffer 0 = The Receive Counter Register has not reached 0 since the last write in RCR or RNCR. 1 = The Receive Counter Register has reached 0 since the last write in RCR or RNCR. • GOVRE: General Overrun Error 0 = No General Overrun Error occurred since the last read of SR. 1 = At least one General Overrun Error has occurred since the last read of SR. • DRDY: Data Ready 0 = No data has been converted since the last read of LCDR. 1 = At least one data has been converted and is available in LCDR. • OVREx: Overrun Error x 0 = No overrun error on the corresponding channel(if implemented) since the last read of SR. 1 = There has been an overrun error on the corresponding channel (if implemented) since the last read of SR. • EOCx: End of Conversion x 0 = Corresponding analog channel (if implemented) is disabled, or the conversion is not finished. 1 = Corresponding analog channel (if implemented) is enabled and conversion is complete. 714 32058H–AVR32–03/09 AT32UC3A 33.7.7 Name: Last Converted Data Register LCDR Read-only 0x20 0x00000000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 1 LDATA 0 LDATA • LDATA: Last Data Converted The analog-to-digital conversion data is placed into this register at the end of a conversion and remains until a new conversion is completed. 715 32058H–AVR32–03/09 AT32UC3A 33.7.8 Name: Interrupt Enable Register IER Write-only 0x24 – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 RXBUFF 11 ENDRX 10 GOVRE 9 DRDY 8 OVRE7 7 OVRE6 6 OVRE5 5 OVRE4 4 OVRE3 3 OVRE2 2 OVRE1 1 OVRE0 0 EOC7 EOC6 EOC5 EOC4 EOC3 EOC2 EOC1 EOC0 • RXBUFF: Receive Buffer Full Interrupt Enable 0 = No effect. 1 = Enables the corresponding interrupt. ENDRX: End of Receive Buffer Interrupt Enable • GOVRE: General Overrun Error Interrupt Enable • DRDY: Data Ready Interrupt Enable • OVREx: Overrun Error Interrupt Enable x • EOCx: End of Conversion Interrupt Enable x 716 32058H–AVR32–03/09 AT32UC3A 33.7.9 Name: Interrupt Disable Register IDR Write-only 0x28 – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 RXBUFF 11 ENDRX 10 GOVRE 9 DRDY 8 OVRE7 7 OVRE6 6 OVRE5 5 OVRE4 4 OVRE3 3 OVRE2 2 OVRE1 1 OVRE0 0 EOC7 EOC6 EOC5 EOC4 EOC3 EOC2 EOC1 EOC0 • RXBUFF: Receive Buffer Full Interrupt Disable 0 = No effect. 1 = Disables the corresponding interrupt. • ENDRX: End of Receive Buffer Interrupt Disable • GOVRE: General Overrun Error Interrupt Disable • DRDY: Data Ready Interrupt Disable • OVREx: Overrun Error Interrupt Disable x • EOCx: End of Conversion Interrupt Disable x 717 32058H–AVR32–03/09 AT32UC3A 33.7.10 Name: Interrupt Mask Register IMR Read-only 0x2C 0x00000000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 RXBUFF 11 ENDRX 10 GOVRE 9 DRDY 8 OVRE7 7 OVRE6 6 OVRE5 5 OVRE4 4 OVRE3 3 OVRE2 2 OVRE1 1 OVRE0 0 EOC7 EOC6 EOC5 EOC4 EOC3 EOC2 EOC1 EOC0 • RXBUFF: Receive Buffer Full Interrupt Mask 0 = The corresponding interrupt is disabled. 1 = The corresponding interrupt is enabled. • ENDRX: End of Receive Buffer Interrupt Mask • GOVRE: General Overrun Error Interrupt Mask • DRDY: Data Ready Interrupt Mask • OVREx: Overrun Error Interrupt Mask x • EOCx: End of Conversion Interrupt Mask x 718 32058H–AVR32–03/09 AT32UC3A 33.7.11 Name: Channel Data Register CDRx Read-only 0x2C-0x4C 0x00000000 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 1 DATA 0 DATA • DATA: Converted Data The analog-to-digital conversion data is placed into this register at the end of a conversion and remains until a new conversion is completed. The Convert Data Register (CDR) is only loaded if the corresponding analog channel is enabled. 719 32058H–AVR32–03/09 AT32UC3A 33.7.12 Name: Version Register VERSION Read-only 0xFC – 30 29 28 27 26 25 24 Access Type: Offset: Reset Value: 31 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 11 10 VARIANT 9 8 – 7 – 6 – 5 – 4 3 2 VERSION[11:8] 1 0 VERSION[7:0] • VARIANT: Variant Number Reserved. No functionality associated. • VERSION: Version Number Version number of the module. No functionality associated. 720 32058H–AVR32–03/09 AT32UC3A 34. Audio Bitstream DAC (ABDAC) Rev: 1.0.1.1 34.1 Features • 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 34.2 Description The Audio Bitstream DAC converts a 16-bit sample value to a digital bitstream with an average value proportional to the sample value. Two channels are supported, making the Audio Bitstream DAC particularly suitable for stereo audio. Each channel has a pair of complementary digital outputs, DACn and DACn_N, which can be connected to an external high input impedance amplifier. The Audio Bitstream DAC is compromised of two 3rd order Sigma Delta D/A converter with an oversampling ratio of 128. The samples are upsampled with a 4th order Sinc interpolation filter (Comb4) before being input to the Sigmal Delta Modulator. In order to compensate for the pass band frequency response of the interpolation filter and flatten the overall frequency response, the input to the interpolation filter is first filtered with a simple 3-tap FIR filter.The total frequency response of the Equalization FIR filter and the interpolation filter is given in Figure 34-2 on page 733. The digital output bitstreams from the Sigma Delta Modulators should be low-pass filtered to remove high frequency noise inserted by the Modulation process. The output DACn and DACn_N should be as ideal as possible before filtering, to achieve the best SNR quality. The output can be connected to a class D amplifier output stage, or it can be low pass filtered and connected to a high input impedance amplifier. A simple 1st order or higher low pass filter that filters all the frequencies above 50 kHz should be adequate. 721 32058H–AVR32–03/09 AT32UC3A 34.3 Block Diagram Figure 34-1. Functional Block Diagram Audio Bitstream DAC clk Clock Generator sample_clk bit_clk din1[15:0] Equalization FIR COMB (INT=128) Sigma-Delta DA-MOD bit_out1 din2[15:0] Equalization FIR COMB (INT=128) Sigma-Delta DA-MOD bit_out2 34.4 Pin Name List I/O Lines Description Pin Description Output from Audio Bitstream DAC Channel 0 Output from Audio Bitstream DAC Channel 1 Inverted output from Audio Bitstream DAC Channel 0 Inverted output from Audio Bitstream DAC Channel 1 Type Output Output Output Output Table 34-1. Pin Name DATA0 DATA1 DATAN0 DATAN1 34.5 34.5.1 Product Dependencies I/O Lines The output pins used for the output bitstream from the Audio Bitstream DAC may be multiplexed with PIO lines. Before using the Audio Bitstream DAC, the PIO controller must be configured in order for the Audio Bitstream DAC I/O lines to be in Audio Bitstream DAC peripheral mode. 34.5.2 Power Management The PB-bus clock to the Audio Bitstream DAC is generated by the power manager. Before using the Audio Bitstream DAC, the programmer must ensure that the Audio Bitstream DAC clock is enabled in the power manager. 722 32058H–AVR32–03/09 AT32UC3A 34.5.3 Clock Management The Audio Bitstream DAC needs a separate clock for the D/A conversion operation. This clock should be set up in the generic clock register in the power manager. The frequency of this clock must be 256 times the frequency of the desired samplerate (fs). For fs=48kHz this means that the clock must have a frequency of 12.288MHz. 34.5.4 Interrupts The Audio Bitstream DAC interface has an interrupt line connected to the interrupt controller. In order to handle interrupts, the interrupt controller must be programmed before configuring the Audio Bitstream DAC. All Audio Bitstream DAC interrupts can be enabled/disabled by writing to the Audio Bitstream DAC Interrupt Enable/Disable Registers. Each pending and unmasked Audio Bitstream DAC interrupt will assert the interrupt line. The Audio Bitstream DAC interrupt service routine can get the interrupt source by reading the Interrupt Status Register. 34.5.5 DMA The Audio Bitstream DAC is connected to the DMA controller. The DMA controller can be programmed to automatically transfer samples to the Audio Bitstream DAC Sample Data Register (SDR) when the Audio Bitstream DAC is ready for new samples. This enables the Audio Bitstream DAC to operate without any CPU intervention such as polling the Interrupt Status Register (ISR) or using interrupts. See the DMA controller documentation for details on how to setup DMA transfers. 34.6 Functional Description In order to use the Audio Bitstream DAC the product dependencies given in Section 34.5 on page 722 must be resolved. Particular attention should be given to the configuration of clocks and I/O lines in order to ensure correct operation of the Audio Bitstream DAC. The Audio Bitstream DAC is enabled by writing the ENABLE bit in the Audio Bitstream DAC Control Register (CR). The two 16-bit sample values for channel 0 and 1 can then be written to the least and most significant halfword of the Sample Data Register (SDR), respectively. The TX_READY bit in the Interrupt Status Register (ISR) will be set whenever the DAC is ready to receive a new sample. A new sample value should be written to SDR before 256 DAC clock cycles, or an underrun will occur, as indicated by the UNDERRUN status flags in ISR. ISR is cleared when read, or when writing one to the corresponding bits in the Interrupt Clear Register (ICR). For interrupt-based operation, the relevant interrupts must be enabled by writing one to the corresponding bits in the Interrupt Enable Register (IER). Interrupts can be disabled by the Interrupt Disable Register (IDR), and active interrupts are indicated in the read-only Interrupt Mask Register (IMR). The Audio Bitstream DAC can also be configured for peripheral DMA access, in which case only the enable bit in the control register needs to be set in the Audio Bitstream DAC module. 34.6.1 Equalization Filter The equalization filter is a simple 3-tap FIR filter. The purpose of this filter is to compensate for the pass band frequency response of the sinc interpolation filter. The equalization filter makes the pass band response more flat and moves the -3dB corner a little higher. 723 32058H–AVR32–03/09 AT32UC3A 34.6.2 Interpolation filter The interpolation filter interpolates from fs to 128fs. This filter is a 4th order Cascaded IntegratorComb filter, and the basic building blocks of this filter is a comb part and an integrator part. 34.6.3 Sigma Delta Modulator This part is a 3rd order Sigma Delta Modulator consisting of three differentiators (delta blocks), three integrators (sigma blocks) and a one bit quantizer. The purpose of the integrators is to shape the noise, so that the noise is reduces in the band of interest and increased at the higher frequencies, where it can be filtered. 34.6.4 Data Format Input data is on two’s complement format. 724 32058H–AVR32–03/09 AT32UC3A 34.7 Audio Bitstream DAC User Interface Table 34-2. Offset 0x0 0x4 0x8 0xc 0x10 0x14 0x18 0x1C Sample Data Register Reserved Control Register Interrupt Mask Register Interrupt Enable Register Interrupt Disable Register Interrupt Clear Register Interrupt Status Register Register Mapping Register Register Name SDR CR IMR IER IDR ICR ISR Access Read/Write Read/Write Read Write Write Write Read Reset 0x0 0x0 0x0 0x0 725 32058H–AVR32–03/09 AT32UC3A 34.7.1 Name: Access Type: 31 23 15 7 Audio Bitstream DAC Sample Data Register SDR Read-Write 30 22 14 6 29 21 13 5 28 CHANNEL1 20 CHANNEL1 12 CHANNEL0 4 CHANNEL0 3 2 1 0 11 10 9 8 19 18 17 16 27 26 25 24 • CHANNEL0: Sample Data for Channel 0 Signed 16-bit Sample Data for channel 0. When the SWAP bit in the DAC Control Register (CR) is set writing to the Sample Data Register (SDR) will cause the values written to CHANNEL0 and CHANNEL1 to be swapped. • CHANNEL1: Sample Data for Channel 1 Signed 16-bit Sample Data for channel 1. When the SWAP bit in the DAC Control Register (CR) is set writing to the Sample Data Register (SDR) will cause the values written to CHANNEL0 and CHANNEL1 to be swapped. 726 32058H–AVR32–03/09 AT32UC3A 34.7.2 Name: Access Type: 31 EN 23 15 7 - Audio Bitstream DAC Control Register CR Read-Write 30 SWAP 22 14 6 29 21 13 5 28 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • SWAP: Swap Channels 0: The CHANNEL0 and CHANNEL1 samples will not be swapped when writing the Audio Bitstream DAC Sample Data Register (SDR). 1: The CHANNEL0 and CHANNEL1 samples will be swapped when writing the Audio Bitstream DAC Sample Data Register (SDR). • EN: Enable Audio Bitstream DAC 0: Audio Bitstream DAC is disabled. 1: Audio Bitstream DAC is enabled. 727 32058H–AVR32–03/09 AT32UC3A 34.7.3 Name: Access Type: 31 23 15 7 - Audio Bitstream DAC Interrupt Mask Register IMR Read-only 30 22 14 6 29 TX_READY 21 13 5 28 UNDERRUN 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • UNDERRUN: Underrun Interrupt Mask 0: The Audio Bitstream DAC Underrun interrupt is disabled. 1: The Audio Bitstream DAC Underrun interrupt is enabled. • TX_READY: TX Ready Interrupt Mask 0: The Audio Bitstream DAC TX Ready interrupt is disabled. 1: The Audio Bitstream DAC TX Ready interrupt is enabled. 728 32058H–AVR32–03/09 AT32UC3A 34.7.4 Name: Access Type: 31 23 15 7 - Audio Bitstream DAC Interrupt Enable Register IER Write-only 30 22 14 6 29 TX_READY 21 13 5 28 UNDERRUN 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • UNDERRUN: Underrun Interrupt Enable 0: No effect. 1: Enables the Audio Bitstream DAC Underrun interrupt. • TX_READY: TX Ready Interrupt Enable 0: No effect. 1: Enables the Audio Bitstream DAC TX Ready interrupt. 729 32058H–AVR32–03/09 AT32UC3A 34.7.5 Name: Access Type: 31 23 15 7 - Audio Bitstream DAC Interrupt Disable Register IDR Write-only 30 22 14 6 29 TX_READY 21 13 5 28 UNDERRUN 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • UNDERRUN: Underrun Interrupt Disable 0: No effect. 1: Disable the Audio Bitstream DAC Underrun interrupt. • TX_READY: TX Ready Interrupt Disable 0: No effect. 1: Disable the Audio Bitstream DAC TX Ready interrupt. 730 32058H–AVR32–03/09 AT32UC3A 34.7.6 Name: Access Type: 31 23 15 7 - Audio Bitstream DAC Interrupt Clear Register ICR Write-only 30 22 14 6 29 TX_READY 21 13 5 28 UNDERRUN 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • UNDERRUN: Underrun Interrupt Clear 0: No effect. 1: Clear the Audio Bitstream DAC Underrun interrupt. • TX_READY: TX Ready Interrupt Clear 0: No effect. 1: Clear the Audio Bitstream DAC TX Ready interrupt. 731 32058H–AVR32–03/09 AT32UC3A 34.7.7 Name: Access Type: 31 23 15 7 - Audio Bitstream DAC Interrupt Status Register ISR Read-only 30 22 14 6 29 TX_READY 21 13 5 28 UNDERRUN 20 12 4 27 19 11 3 26 18 10 2 25 17 9 1 24 16 8 0 - • UNDERRUN: Underrun Interrupt Status 0: No Audio Bitstream DAC Underrun has occured since the last time ISR was read or since reset. 1: At least one Audio Bitstream DAC Underrun has occured since the last time ISR was read or since reset. • TX_READY: TX Ready Interrupt Status 0: No Audio Bitstream DAC TX Ready has occuredt since the last time ISR was read. 1: At least one Audio Bitstream DAC TX Ready has occuredt since the last time ISR was read. 732 32058H–AVR32–03/09 AT32UC3A 34.8 Frequency Response Figure 34-2. Frequecy response, EQ-FIR+COMB4 10 0 -1 0 -2 0 -3 0 -4 0 -5 0 -6 0 0 1 2 3 4 5 6 7 8 9 x 10 10 4 733 32058H–AVR32–03/09 AT32UC3A 35. On-Chip Debug Rev: 1.3.0.0 35.1 Features • • • • • • • • Debug interface in compliance with IEEE-ISTO 5001-2003 (Nexus 2.0) Class 2+ JTAG access to all on-chip debug functions Advanced Program, Data, Ownership, and Watchpoint trace supported NanoTrace JTAG-based trace access Auxiliary port for high-speed trace information Hardware support for 6 Program and 2 Data breakpoints Unlimited number of software breakpoints supported Automatic CRC check of memory regions 35.2 Overview Debugging on the AT32UC3A is facilitated by a powerful On-Chip Debug (OCD) system. The user accesses this through an external debug tool which connects to the JTAG port and the Auxiliary (AUX) port. The AUX port is primarily used for trace functions, and a JTAG-based debugger is sufficient for basic debugging. The debug system is based on the Nexus 2.0 standard, class 2+, which includes: • Basic run-time control • Program breakpoints • Data breakpoints • Program trace • Ownership trace • Data trace In addition to the mandatory Nexus debug features, the AT32UC3A implements several useful OCD features, such as: • Debug Communication Channel between CPU and JTAG • Run-time PC monitoring • CRC checking • NanoTrace • Software Quality Assurance (SQA) support The OCD features are controlled by OCD registers, which can be accessed by JTAG when the NEXUS_ACCESS JTAG instruction is loaded. The CPU can also access OCD registers directly using mtdr/mfdr instructions in any privileged mode. The OCD registers are implemented based on the recommendations in the Nexus 2.0 standard, and are detailed in the AVR32UC Technical Reference Manual. 734 32058H–AVR32–03/09 AT32UC3A 35.3 Block diagram Figure 35-1. On-Chip Debug block diagram JTAG JTAG AUX On-Chip Debug Service Access Bus Memory Service Unit Transmit Queue Watchpoints Debug PC Debug Instruction Program Trace Data Trace Ownership Trace Breakpoints CPU Internal SRAM HSB Bus Matrix Memories and peripherals 35.4 35.4.1 Functional description JTAG-based debug features A debugger can control all OCD features by writing OCD registers over the JTAG interface. Many of these do not depend on output on the AUX port, allowing a JTAG-based debugger to be used. A JTAG-based debugger should connect to the device through a standard 10-pin IDC connector as described in the AVR32UC Technical Reference Manual. 735 32058H–AVR32–03/09 AT32UC3A Figure 35-2. JTAG-based debugger PC JTAG-based debug tool 10-pin IDC JTAG AVR32 35.4.1.1 Debug Communication Channel The Debug Communication Channel (DCC) consists of a pair OCD registers with associated handshake logic, accessible to both CPU and JTAG. The registers can be used to exchange data between the CPU and the JTAG master, both runtime as well as in debug mode. Breakpoints One of the most fundamental debug features is the ability to halt the CPU, to examine registers and the state of the system. This is accomplished by breakpoints, of which many types are available: • Unconditional breakpoints are set by writing OCD registers by JTAG, halting the CPU immediately. • Program breakpoints halt the CPU when a specific address in the program is executed. • Data breakpoints halt the CPU when a specific memory address is read or written, allowing variables to be watched. • Software breakpoints halt the CPU when the breakpoint instruction is executed. When a breakpoint triggers, the CPU enters debug mode, and the D bit in the status register is set. This is a privileged mode with dedicated return address and return status registers. All privileged instructions are permitted. Debug mode can be entered as either OCD Mode, running instructions from JTAG, or Monitor Mode, running instructions from program memory. 35.4.1.2 736 32058H–AVR32–03/09 AT32UC3A 35.4.1.3 OCD Mode When a breakpoint triggers, the CPU enters OCD mode, and instructions are fetched from the Debug Instruction OCD register. Each time this register is written by JTAG, the instruction is executed, allowing the JTAG to execute CPU instructions directly. The JTAG master can e.g. read out the register file by issuing mtdr instructions to the CPU, writing each register to the Debug Communication Channel OCD registers. 35.4.1.4 Monitor Mode Since the OCD registers are directly accessible by the CPU, it is possible to build a softwarebased debugger that runs on the CPU itself. Setting the Monitor Mode bit in the Development Control register causes the CPU to enter Monitor Mode instead of OCD mode when a breakpoint triggers. Monitor Mode is similar to OCD mode, except that instructions are fetched from the debug exception vector in regular program memory, instead of issued by JTAG. Program Counter monitoring Normally, the CPU would need to be halted for a JTAG-based debugger to examine the current PC value. However, the AT32UC3A also proves a Debug Program Counter OCD register, where the debugger can continuously read the current PC without affecting the CPU. This allows the debugger to generate a simple statistic of the time spent in various areas of the code, easing code optimization. 35.4.1.5 35.4.2 Memory Service Unit The Memory Service Unit (MSU) is a block dedicated to test and debug functionality. It is controlled through a dedicated set of registers addressed through the MEMORY_SERVICE JTAG command. Cyclic Redundancy Check (CRC) The MSU can be used to automatically calculate the CRC of a block of data in memory. The OCD will then read out each word in the specified memory block and report the CRC32-value in an OCD register. NanoTrace The MSU additionally supports NanoTrace. This is an AVR32-specific feature, in which trace data is output to memory instead of the AUX port. This allows the trace data to be extracted by JTAG MEMORY_ACCESS, enabling trace features for JTAG-based debuggers. The user must write MSU registers to configure the address and size of the memory block to be used for NanoTrace. The NanoTrace buffer can be anywhere in the physical address range, including internal and external RAM, through an EBI, if present. This area may not be used by the application running on the CPU. 35.4.2.1 35.4.2.2 35.4.3 AUX-based debug features Utilizing the Auxiliary (AUX) port gives access to a wide range of advanced debug features. Of prime importance are the trace features, which allow an external debugger to receive continuous information on the program execution in the CPU. Additionally, Event In and Event Out pins allow external events to be correlated with the program flow. The AUX port contains a number of pins, as shown in Table 35-1 on page 738. These are multiplexed with PIO lines, and must explicitly be enabled by writing OCD registers before the debug session starts. The AUX port is mapped to two different locations, selectable by OCD Registers, minimizing the chance that the AUX port will need to be shared with an application. 737 32058H–AVR32–03/09 AT32UC3A Debug tools utilizing the AUX port should connect to the device through a Nexus-compliant Mictor-38 connector, as described in the AVR32UC Technical Reference manual. This connector includes the JTAG signals and the RESET_N pin, giving full access to the programming and debug features in the device. Table 35-1. Signal MCKO MDO[5:0] MSEO[1:0] EVTI_N EVTO_N Auxiliary port signals Direction Output Output Output Input Output Description Trace data output clock Trace data output Trace frame control Event In Event Out Figure 35-3. AUX+JTAG based debugger PC T ra c e b u ffe r AU X+JTA G d e b u g to o l M ic to r 3 8 AUX h ig h s p e e d JTA G AVR 32 35.4.3.1 Trace operation Trace features are enabled by writing OCD registers by JTAG. The OCD extracts the trace information from the CPU, compresses this information and formats it into variable-length messages according to the Nexus standard. The messages are buffered in a 16-frame transmit queue, and are output on the AUX port one frame at a time. 738 32058H–AVR32–03/09 AT32UC3A The trace features can be configured to be very selective, to reduce the bandwidth on the AUX port. In case the transmit queue overflows, error messages are produced to indicate loss of data. The transmit queue module can optionally be configured to halt the CPU when an overflow occurs, to prevent the loss of messages, at the expense of longer run-time for the program. 35.4.3.2 Program Trace Program trace allows the debugger to continuously monitor the program execution in the CPU. Program trace messages are generated for every branch in the program, and contains compressed information, which allows the debugger to correlate the message with the source code to identify the branch instruction and target address. Data Trace Data trace outputs a message every time a specific location is read or written. The message contains information about the type (read/write) and size of the access, as well as the address and data of the accessed location. The AT32UC3A contains two data trace channels, each of which are controlled by a pair of OCD registers which determine the range of addresses (or single address) which should produce data trace messages. 35.4.3.4 Ownership Trace Program and data trace operate on virtual addresses. In cases where an operating system runs several processes in overlapping virtual memory segments, the Ownership Trace feature can be used to identify the process switch. When the O/S activates a process, it will write the process ID number to an OCD register, which produces an Ownership Trace Message, allowing the debugger to switch context for the subsequent program and data trace messages. As the use of this feature depends on the software running on the CPU, it can also be used to extract other types of information from the system. Watchpoint messages The breakpoint modules normally used to generate program and data breakpoints can also be used to generate Watchpoint messages, allowing a debugger to monitor program and data events without halting the CPU. Watchpoints can be enabled independently of breakpoints, so a breakpoint module can optionally halt the CPU when the trigger condition occurs. Data trace modules can also be configured to produce watchpoint messages instead of regular data trace messages. Event In and Event Out pins The AUX port also contains an Event In pin (EVTI_N) and an Event Out pin (EVTO_N). EVTI_N can be used to trigger a breakpoint when an external event occurs. It can also be used to trigger specific program and data trace synchronization messages, allowing an external event to be correlated to the program flow. When the CPU enters debug mode, a Debug Status message is transmitted on the trace port. All trace messages can be timestamped when they are received by the debug tool. However, due to the latency of the transmit queue buffering, the timestamp will not be 100% accurate. To improve this, EVTO_N can toggle every time a message is inserted into the transmit queue, allowing trace messages to be timestamped precisely. EVTO_N can also toggle when a breakpoint module triggers, or when the CPU enters debug mode, for any reason. This can be used to measure precisely when the respective internal event occurs. 35.4.3.3 35.4.3.5 35.4.3.6 739 32058H–AVR32–03/09 AT32UC3A 35.4.3.7 Software Quality Analysis (SQA) Software Quality Analysis (SQA) deals with two important issues regarding embedded software development. Code coverage involves identifying untested parts of the embedded code, to improve test procedures and thus the quality of the released software. Performance analysis allows the developer to precisely quantify the time spent in various parts of the code, allowing bottlenecks to be identified and optimized. Program trace must be used to accomplish these tasks without instrumenting (altering) the code to be examined. However, traditional program trace cannot reconstruct the current PC value without correlating the trace information with the source code, which cannot be done on-the-fly. This limits program trace to a relatively short time segment, determined by the size of the trace buffer in the debug tool. The OCD system in AT32UC3A extends program trace with SQA capabilities, allowing the debug tool to reconstruct the PC value on-the-fly. Code coverage and performance analysis can thus be reported for an unlimited execution sequence. 740 32058H–AVR32–03/09 AT32UC3A 36. JTAG and Boundary Scan Rev.: 2.0.0.2 36.1 Features • • • • IEEE1149.1 compliant JTAG Interface Boundary-Scan Chain for board-level testing Direct memory access and programming capabilities through JTAG interface On-Chip Debug access in compliance with IEEE-ISTO 5001-2003 (Nexus 2.0) 36.2 Overview Figure 36-1 on page 742 shows how the JTAG is connected in an AVR32 device. The TAP Controller is a state machine controlled by the TCK and TMS signals. The TAP Controller selects either the JTAG Instruction Register or one of several Data Registers as the scan chain (shift register) between the TDI-input and TDO-output. The Instruction Register holds JTAG instructions controlling the behavior of a Data Register. The ID Register, Bypass Register, and the Boundary-Scan Chain are the Data Registers used for board-level testing. The Reset Register can be used to keep the device reset during test or programming. The Service Access Bus (SAB) interface contains address and data registers for the Service Access Bus, which gives access to on-chip debug, programming, and other functions in the device. The SAB offers several modes of access to the address and data registers, as discussed in Section 36.6.4. Section 36.7 lists the supported JTAG instructions, with references to the description in this document. 741 32058H–AVR32–03/09 AT32UC3A 36.3 Block diagram Figure 36-1. JTAG and Boundary Scan access AVR32 device JTAG master TCK TMS TDI TDO TAP Controller Instruction Register Scan enable Boundary scan enable JTAG TAP Data register scan enable Instruction Register TMS TCK TDO TDI JTAG data registers JTAG device Bypass ID Register Reset Register ... Service Access Bus interface OCD Registers CPU RAM Service Access Bus Memory Service Unit Memories and peripherals Pins and analog blocks Boundary Scan Chain High Speed Bus 742 32058H–AVR32–03/09 AT32UC3A 36.4 I/O Lines Description I/O Lines Description Description Test Clock Input. Fully asynchronous to system clock frequency. Test Mode Select, sampled on rising TCK Test Data In, sampled on rising TCK. Test Data Out, driven on falling TCK. Type Input Input Input Output Table 36-1. Name TCK TMS TDI TDO 36.5 Product Dependencies In order to use this module, other parts of the system must be configured correctly, as described below. 36.5.1 I/O Lines The JTAG interface pins are multiplexed with IO lines. When the JTAG is used the associated pins must be enabled. To enable the JTAG pins TCK must be zero while RESET_N has a zero to one transition. To disable the JTAG pins TCK must be one while RESET_N has a zero to one transition. While using the JTAG lines all normal peripheral activity on these lines are disabled. The user must make sure that no external peripheral is blocking the JTAG lines while debugging. 36.6 36.6.1 Functional description JTAG interface The JTAG interface is accessed through the dedicated JTAG pins shown in Table 36-1 on page 743. The TMS control line navigates the TAP controller, as shown in Figure 36-2 on page 744. The TAP controller manages the serial access to the JTAG Instruction and Data registers. Data is scanned into the selected instruction or data register on TDI, and out of the register on TDO, in the Shift-IR and Shift-DR states, respectively. The LSB is shifted in and out first. TDO is highZ in other states than Shift-IR and Shift-DR. Independent of the initial state of the TAP Controller, the Test-Logic-Reset state can always be entered by holding TMS high for 5 TCK clock periods. This sequence should always be applied at the start of a JTAG session to bring the TAP Controller into a defined state before applying JTAG commands. Applying a 0 on TMS for 1 TCK period brings the TAP Controller to the RunTest/Idle state, which is the starting point for JTAG operations. The device implements a 5-bit Instruction Register (IR). A number of public JTAG instructions defined by the JTAG standard are supported, as described in Section 36.8, as well as a number of AVR32-specific private JTAG instructions described in Section 36.9. Each instruction selects a specific data register for the Shift-DR path, as described for each instruction. 743 32058H–AVR32–03/09 AT32UC3A Figure 36-2. TAP Controller State Diagram 1 Test-LogicReset 0 0 Run-Test/ Idle 1 Select-DR Scan 0 Capture-DR 0 Shift-DR 1 Exit1-DR 0 Pause-DR 1 0 Exit2-DR 1 1 Update-DR 0 1 0 1 0 0 1 Select-IR Scan 0 Capture-IR 0 Shift-IR 1 Exit1-IR 0 Pause-IR 1 Exit2-IR 1 Update-IR 0 0 1 0 1 1 1 36.6.2 Typical sequence Assuming Run-Test/Idle is the present state, a typical scenario for using the JTAG interface is: Scanning in JTAG instruction At the TMS input, apply the sequence 1, 1, 0, 0 at the rising edges of TCK to enter the Shift Instruction Register - Shift-IR state. While in this state, shift the 5 bits of the JTAG instructions into the JTAG instruction register from the TDI input at the rising edge of TCK. The TMS input must be held low during input of the 4 LSBs in order to remain in the Shift-IR state. The JTAG Instruction selects a particular Data Register as path between TDI and TDO and controls the circuitry surrounding the selected Data Register. Apply the TMS sequence 1, 1, 0 to re-enter the Run-Test/Idle state. The instruction is latched onto the parallel output from the shift register path in the Update-IR state. The Exit-IR, Pause-IR, and Exit2-IR states are only used for navigating the state machine. 36.6.2.1 744 32058H–AVR32–03/09 AT32UC3A Figure 36-3. Scanning in JTAG instruction TCK TAP State TMS TDI TDO Instruction ImplDefined TLR RTI SelDR SelIR CapIR ShIR Ex1IR UpdIR RTI 36.6.2.2 Scanning in/out data At the TMS input, apply the sequence 1, 0, 0 at the rising edges of TCK to enter the Shift Data Register - Shift-DR state. While in this state, upload the selected Data Register (selected by the present JTAG instruction in the JTAG Instruction Register) from the TDI input at the rising edge of TCK. In order to remain in the Shift-DR state, the TMS input must be held low. While the Data Register is shifted in from the TDI pin, the parallel inputs to the Data Register captured in the Capture-DR state is shifted out on the TDO pin. Apply the TMS sequence 1, 1, 0 to re-enter the Run-Test/Idle state. If the selected Data Register has a latched parallel-output, the latching takes place in the Update-DR state. The Exit-DR, Pause-DR, and Exit2-DR states are only used for navigating the state machine. As shown in the state diagram, the Run-Test/Idle state need not be entered between selecting JTAG instruction and using Data Registers. 36.6.3 Boundary-Scan The Boundary-Scan chain has the capability of driving and observing the logic levels on the digital I/O pins, as well as the boundary between digital and analog logic for analog circuitry having off-chip connections. At system level, all ICs having JTAG capabilities are connected serially by the TDI/TDO signals to form a long shift register. An external controller sets up the devices to drive values at their output pins, and observe the input values received from other devices. The controller compares the received data with the expected result. In this way, Boundary-Scan provides a mechanism for testing interconnections and integrity of components on Printed Circuits Boards by using the 4 TAP signals only. The four IEEE 1149.1 defined mandatory JTAG instructions IDCODE, BYPASS, SAMPLE/PRELOAD, and EXTEST can be used for testing the Printed Circuit Board. Initial scanning of the data register path will show the ID-code of the device, since IDCODE is the default JTAG instruction. It may be desirable to have the AVR32 device in reset during test mode. If not reset, inputs to the device may be determined by the scan operations, and the internal software may be in an undetermined state when exiting the test mode. Entering reset, the outputs of any Port Pin will instantly enter the high impedance state, making the HIGHZ instruction redundant. If needed, the BYPASS instruction can be issued to make the shortest possible scan chain through the device. The device can be set in the reset state either by pulling the external RESETn pin low, or issuing the AVR_RESET instruction with appropriate setting of the Reset Data Register. The EXTEST instruction is used for sampling external pins and loading output pins with data. The data from the output latch will be driven out on the pins as soon as the EXTEST instruction is loaded into the JTAG IR-register. Therefore, the SAMPLE/PRELOAD should also be used for setting initial values to the scan ring, to avoid damaging the board when issuing the EXTEST 745 32058H–AVR32–03/09 AT32UC3A instruction for the first time. SAMPLE/PRELOAD can also be used for taking a snapshot of the external pins during normal operation of the part. When using the JTAG interface for Boundary-Scan, the JTAG TCK clock is independent of the internal chip clock, which is not required to run. 36.6.4 Service Access Bus A number of private instructions are used to access Service Access Bus (SAB) resources. Each of these are described in detail in SAB address map in the Service Access Bus chapter. The MEMORY_SIZED_ACCESS instruction allows a sized read or write to any 36-bit address on the bus. MEMORY_WORD_ACCESS is a shorthand instruction for 32-bit accesses to any 36-bit address, while the NEXUS_ACCESS instruction is a Nexus-compliant shorthand instruction for accessing the 32-bit OCD registers in the 7-bit address space reserved for these. These instructions require two passes through the Shift-DR TAP state: one for the address and control information, and one for data. To increase the transfer rate, consecutive memory accesses can be accomplished by the MEMORY_BLOCK_ACCESS instruction, which only requires a single pass through Shift-DR for data transfer only. The address is automatically incremented according to the size of the last SAB transfer. The access time to SAB resources depends on the type of resource being accessed. It is possible to read external memory through the EBI, in which case the latency may be very long. It is possible to abort an ongoing SAB access by the CANCEL_ACCESS instruction, to avoid hanging the bus due to an extremely slow slave. "The access time to SAB resources depends on the type of resource being accessed. It is possible to abort an ongoing SAB access by the CANCEL_ACCESS instruction, to avoid hanging the bus due to an extremely slow slave." 36.6.4.1 Busy reporting As the time taken to perform an access may vary depending on system activity and current chip frequency, all the SAB access JTAG instructions can return a busy indicator. This indicates whether a delay needs to be inserted, or an operation needs to be repeated in order to be successful. If a new access is requested while the SAB is busy, the request is ignored. The SAB becomes busy when: • Entering Update-DR in the address phase of any read operation, e.g. after scanning in a NEXUS_ACCESS address with the read bit set. • Entering Update-DR in the data phase of any write operation, e.g. after scanning in data for a NEXUS_ACCESS write. • Entering Update-DR during a MEMORY_BLOCK_ACCESS. • Entering Update-DR after scanning in a counter value for SYNC. • Entering Update-IR after scanning in a MEMORY_BLOCK_ACCESS if the previous access was a read and data was scanned after scanning the address. The SAB becomes ready again when: • A read or write operation completes. 746 32058H–AVR32–03/09 AT32UC3A • A SYNC countdown completed. • A operation is cancelled by the CANCEL_ACCESS instruction. What to do if the busy bit is set: • During Shift-IR: The new instruction is selected, but the previous operation has not yet completed and will continue (unless the new instruction is CANCEL_ACCESS). You may continue shifting the same instruction until the busy bit clears, or start shifting data. If shifting data, you must be prepared that the data shift may also report busy. • During Shift-DR of an address: The new address is ignored. The SAB stays in address mode, so no data must be shifted. Repeat the address until the busy bit clears. • During Shift-DR of read data: The read data are invalid. The SAB stays in data mode. Repeat scanning until the busy bit clears. • During Shift-DR of write data: The write data are ignored. The SAB stays in data mode. Repeat scanning until the busy bit clears. 36.6.4.2 Error reporting The Service access port may not be able to complete all accesses as requested. This may be because the address is invalid, the addressed area is read-only or cannot handle byte/halfword accesses, or because the chip is set in a protected mode where only limited accesses are allowed. The error bit is updated when an access completes, and is cleared when a new access starts. What to do if the error bit is set: • During Shift-IR: The new instruction is selected. The last operation performed using the old instruction did not complete successfully. • During Shift-DR of an address: The previous operation failed. The new address is accepted. If the read bit is set, a read operation is started. • During Shift-DR of read data: The read operation failed, and the read data are invalid. • During Shift-DR of write data: The previous write operation failed. The new data are accepted and a write operation started. This should only occur during block writes or stream writes. No error can occur between scanning a write address and the following write data. • While polling with CANCEL_ACCESS: The previous access was cancelled. It may or may not have actually completed. 36.6.5 Memory programming The High-Speed Bus (HSB) in the device is mapped as a slave on the SAB. This enables all HSB-mapped memories to be read or written through the SAB using JTAG instructions, as described in Section 36.6.4. Internal SRAM can always be directly accessed. External static memory or SDRAM can be accessed if the EBI has been correctly configured to access this memory. It is also possible to access the configuration registers for these modules to set up the correct configuration. Similarly, external parallel flash can be programmed by accessing the registers for the flash device through the EBI. The internal flash and fuses can likewise be programmed by accessing the registers in the Flash Controller. When the security fuse is set, access to internal memory is blocked, and the CHIP_ERASE instruction must be used to erase the fuse and flash contents. For detail see the SAB address map section. 747 32058H–AVR32–03/09 AT32UC3A Memory can be written while the CPU is executing, which can be utilized for debug purposes. When downloading a new program, the JTAG HALT instruction should be used to freeze the CPU, to prevent partially downloaded code from being executed. 36.7 JTAG Instruction Summary The implemented JTAG instructions in the AVR32 are shown in the table below. JTAG Instruction Summary Instruction IDCODE SAMPLE_PRELOAD EXTEST INTEST CLAMP AVR_RESET CHIP_ERASE NEXUS_ACCESS MEMORY_WORD_ACCESS MEMORY_BLOCK_ACCESS CANCEL_ACCESS MEMORY_SERVICE MEMORY_SIZED_ACCESS SYNC HALT BYPASS N/A Description Select the 32-bit ID register as data register. Take a snapshot of external pin values without affecting system operation. Select boundary scan chain as data register for testing circuitry external to the device. Select boundary scan chain for internal testing of the device. Bypass device through Bypass register, while driving outputs from boundary scan register. Apply or remove a static reset to the device Erase the device Select the SAB Address and Data registers as data register for the TAP. The registers are accessed in Nexus mode. Select the SAB Address and Data registers as data register for the TAP. Select the SAB Data register as data register for the TAP. The address is auto-incremented. Cancel an ongoing Nexus or Memory access. Select the SAB Address and Data registers as data register for the TAP. The registers are accessed in Memory Service mode. Select the SAB Address and Data registers as data register for the TAP. Synchronization counter Halt the CPU for safe programming. Bypass this device through the bypass register. Acts as BYPASS Page 749 749 749 749 750 757 757 751 754 755 756 752 753 757 758 750 Table 36-2. Instruction OPCODE 0x01 0x02 0x03 0x04 0x06 0x0C 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x17 0x1C 0x1F Others 36.7.1 Security restrictions When the security fuse in the Flash is programmed, the following JTAG instructions are restricted: • NEXUS_ACCESS • MEMORY_WORD_ACCESS • MEMORY_BLOCK_ACCESS • MEMORY_SIZED_ACCESS 748 32058H–AVR32–03/09 AT32UC3A For description of what memory locations remain accessible, please refer to the SAB address map. Full access to these instructions is re-enabled when the security fuse is erased by the CHIP_ERASE JTAG instruction. Note that the security bit will read as programmed and block these instructions also if the Flash Controller is statically reset. Other security mechanisms can also restrict these functions. If such mechanisms are present they are listed in the SAB address map section. 36.8 36.8.1 Public JTAG instructions IDCODE This instruction selects the 32 bit ID register as Data Register. The ID register consists of a version number, a device number and the manufacturer code chosen by JEDEC. This is the default instruction after power-up. The active states are: • Capture-DR: The static IDCODE value is latched into the shift register. • Shift-DR: The IDCODE scan chain is shifted by the TCK input. 36.8.2 SAMPLE_PRELOAD JTAG instruction for taking a snap-shot of the input/output pins without affecting the system operation, and pre-loading the scan chain without updating the DR-latch. The Boundary-Scan Chain is selected as Data Register. The active states are: • Capture-DR: Data on the external pins are sampled into the Boundary-Scan Chain. • Shift-DR: The Boundary-Scan Chain is shifted by the TCK input. 36.8.3 EXTEST JTAG instruction for selecting the Boundary-Scan Chain as Data Register for testing circuitry external to the AVR32 package. The contents of the latched outputs of the Boundary-Scan chain is driven out as soon as the JTAG IR-register is loaded with the EXTEST instruction. The active states are: • Capture-DR: Data on the external pins is sampled into the Boundary-Scan Chain. • Shift-DR: The Internal Scan Chain is shifted by the TCK input. • Update-DR: Data from the scan chain is applied to output pins. 36.8.4 INTEST This instruction selects the Boundary-Scan Chain as Data Register for testing internal logic in the device. The logic inputs are determined by the Boundary-Scan Chain, and the logic outputs are captured by the Boundary-Scan chain. The device output pins are driven from the BoundaryScan Chain. The active states are: • Capture-DR: Data from the internal logic is sampled into the Boundary-Scan Chain. 749 32058H–AVR32–03/09 AT32UC3A • Shift-DR: The Internal Scan Chain is shifted by the TCK input. • Update-DR: Data from the scan chain is applied to internal logic inputs. 36.8.5 CLAMP This instruction selects the Bypass register as Data Register. The device output pins are driven from the Boundary-Scan Chain. The active states are: • Capture-DR: Loads a logic ‘0’ into the Bypass Register. • Shift-DR: Data is scanned from TDI to TDO through the Bypass register. 36.8.6 BYPASS JTAG instruction selecting the 1-bit Bypass Register for Data Register. The active states are: • Capture-DR: Loads a logic ‘0’ into the Bypass Register. • Shift-DR: Data is scanned from TDI to TDO through the Bypass register. 36.9 36.9.1 Private JTAG Instructions Notation The AVR32 defines a number of private JTAG instructions. Each instruction is briefly described in text, with details following in table form. Table 36-4 on page 751 shows bit patterns to be shifted in a format like "peb01". Each character corresponds to one bit, and eight bits are grouped together for readability. The rightmost bit is always shifted first, and the leftmost bit shifted last. The symbols used are shown in Table 36-3. Table 36-3. Symbol 0 1 a b d e Symbol description Description Constant low value - always reads as zero. Constant high value - always reads as one. An address bit - always scanned with the least significant bit first A busy bit. Reads as one if the SAB was busy, or zero if it was not. See Section 36.6.4.1 for details on how the busy reporting works. A data bit - always scanned with the least significant bit first. An error bit. Reads as one if an error occurred, or zero if not. See Section 36.6.4.2 for details on how the error reporting works. The chip protected bit. Some devices may be set in a protected state where access to chip internals are severely restricted. See the documentation for the specific device for details. On devices without this possibility, this bit always reads as zero. A direction bit. Set to one to request a read, set to zero to request a write. A size bit. The size encoding is described where used. A don’t care bit. Any value can be shifted in, and output data should be ignored. p r s x In many cases, it is not required to shift all bits through the data register. Bit patterns are shown using the full width of the shift register, but the suggested or required bits are emphasized using 750 32058H–AVR32–03/09 AT32UC3A bold text. I.e. given the pattern "aaaaaaar xxxxxxxx xxxxxxxx xxxxxxxx xx", the shift register is 34 bits, but the test or debug unit may choose to shift only 8 bits "aaaaaaar". The following describes how to interpret the fields in the instruction description tables: Table 36-4. Instruction Instruction description Description Shows the bit pattern to shift into IR in the Shift-IR state in order to select this instruction. The pattern is show both in binary and in hexadecimal form for convenience. Example: 10000 (0x10) Shows the bit pattern shifted out of IR in the Shift-IR state when this instruction is active. Example: peb01 Shows the number of bits in the data register chain when this instruction is active. Example: 34 bits Shows which bit pattern to shift into the data register in the Shift-DR state when this instruction is active. Multiple such lines may exist, e.g. to distinguish between reads and writes. Example: aaaaaaar xxxxxxxx xxxxxxxx xxxxxxxx xx Shows the bit pattern shifted out of the data register in the Shift-DR state when this instruction is active. Multiple such lines may exist, e.g. to distinguish between reads and writes. Example: xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb IR input value IR output value DR Size DR input value DR output value 36.9.2 NEXUS_ACCESS This instruction allows Nexus-compliant access to on-chip debug registers through the SAB. OCD registers are addressed by their register index, as listed in the AVR32 Technical Reference Manual. The 7-bit register index and a read/write control bit, and the 32-bit data is accessed through the JTAG port. The data register is alternately interpreted by the SAB as an address register and a data register. The SAB starts in address mode after the NEXUS_ACCESS instruction is selected, and toggles between address and data mode each time a data scan completes with the busy bit cleared. Starting in Run-Test/Idle, OCD registers are accessed in the following way: 1. Select the DR Scan path. 2. Scan in the 7-bit address for the OCD register and a direction bit (1=read, 0=write). 3. Go to Update-DR and re-enter Select-DR Scan. 4. For a read operation, scan out the contents of the addressed register. For a write operation, scan in the new contents of the register. 5. Return to Run-Test/Idle. 751 32058H–AVR32–03/09 AT32UC3A For any operation, the full 7 bits of the address must be provided. For write operations, 32 data bits must be provided, or the result will be undefined. For read operations, shifting may be terminated once the required number of bits have been acquired. Table 36-5. Instructions IR input value NEXUS_ACCESS details Details 10000 (0x10) peb01 34 bits aaaaaaar xxxxxxxx xxxxxxxx xxxxxxxx xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xx dddddddd dddddddd dddddddd dddddddd xx xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb eb dddddddd dddddddd dddddddd dddddddd xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb IR output value DR Size DR input value (Address phase) DR input value (Data read phase) DR input value (Data write phase) DR output value (Address phase) DR output value (Data read phase) DR output value (Data write phase) 36.9.3 MEMORY_SERVICE This instruction allows access to registers in an optional Memory Service unit. Memory Service registers are addressed by their register index, as listed in the Memory Service documentation. The 7-bit register index and a read/write control bit, and the 32-bit data is accessed through the JTAG port. The Memory Service unit may offer features such as CRC calculation of memory, debug trace support, and test features. Please refer to the Memory Service Unit documentation and the part specific documentation for details. The data register is alternately interpreted by the SAB as an address register and a data register. The SAB starts in address mode after the MEMORY_SERVICE instruction is selected, and toggles between address and data mode each time a data scan completes with the busy bit cleared. Starting in Run-Test/Idle, Memory Service registers are accessed in the following way: 1. Select the DR Scan path. 2. Scan in the 7-bit address for the Memory Service register and a direction bit (1=read, 0=write). 3. Go to Update-DR and re-enter Select-DR Scan. 4. For a read operation, scan out the contents of the addressed register. For a write operation, scan in the new contents of the register. 5. Return to Run-Test/Idle. 752 32058H–AVR32–03/09 AT32UC3A For any operation, the full 7 bits of the address must be provided. For write operations, 32 data bits must be provided, or the result will be undefined. For read operations, shifting may be terminated once the required number of bits have been acquired. Table 36-6. Instructions IR input value MEMORY_SERVICE details Details 10100 (0x14) peb01 34 bits aaaaaaar xxxxxxxx xxxxxxxx xxxxxxxx xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xx dddddddd dddddddd dddddddd dddddddd xx xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb eb dddddddd dddddddd dddddddd dddddddd xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb IR output value DR Size DR input value (Address phase) DR input value (Data read phase) DR input value (Data write phase) DR output value (Address phase) DR output value (Data read phase) DR output value (Data write phase) 36.9.4 MEMORY_SIZED_ACCESS This instruction allows access to the entire Service Access Bus data area. Data are accessed through a 36-bit byte index, a 2-bit size, a direction bit, and 8, 16, or 32 bits of data. Not all units mapped on the SAB bus may support all sizes of accesses, e.g. some may only support word accesses. The data register is alternately interpreted by the SAB as an address register and a data register. The SAB starts in address mode after the MEMORY_SIZED_ACCESS instruction is selected, and toggles between address and data mode each time a data scan completes with the busy bit cleared. The size field is encoded as i Table 36-7. Table 36-7. Size Field Semantics Access size Data alignment Address modulo 4 : data alignment 0: dddddddd xxxxxxxx xxxxxxxx xxxxxxxx 1: xxxxxxxx dddddddd xxxxxxxx xxxxxxxx 2: xxxxxxxx xxxxxxxx dddddddd xxxxxxxx 3: xxxxxxxx xxxxxxxx xxxxxxxx dddddddd Size field value 00 Byte (8 bits) 753 32058H–AVR32–03/09 AT32UC3A Table 36-7. Size Field Semantics Access size Data alignment Address modulo 4 : data alignment 0: dddddddd dddddddd xxxxxxxx xxxxxxxx 1: Not allowed 2: xxxxxxxx xxxxxxxx dddddddd dddddddd 3: Not allowed Address modulo 4 : data alignment 0: dddddddd dddddddd dddddddd dddddddd 1: Not allowed 2: Not allowed 3: Not allowed N/A Size field value 01 Halfword (16 bits) 10 Word (32 bits) 11 Reserved Starting in Run-Test/Idle, SAB data are accessed in the following way: 1. Select the DR Scan path. 2. Scan in the 36-bit address of the data to access, a 2-bit access size, and a direction bit (1=read, 0=write). 3. Go to Update-DR and re-enter Select-DR Scan. 4. For a read operation, scan out the contents of the addressed area. For a write operation, scan in the new contents of the area. 5. Return to Run-Test/Idle. For any operation, the full 36 bits of the address must be provided. For write operations, 32 data bits must be provided, or the result will be undefined. For read operations, shifting may be terminated once the required number of bits have been acquired. Table 36-8. Instructions IR input value MEMORY_SIZED_ACCESS details Details 10101 (0x15) peb01 39 bits aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aaaassr xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxx dddddddd dddddddd dddddddd dddddddd xxxxxxx xxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb xxxxxeb dddddddd dddddddd dddddddd dddddddd xxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb IR output value DR Size DR input value (Address phase) DR input value (Data read phase) DR input value (Data write phase) DR output value (Address phase) DR output value (Data read phase) DR output value (Data write phase) 36.9.5 MEMORY_WORD_ACCESS This instruction allows access to the entire Service Access Bus data area. Data are accessed through a 34-bit word index, a direction bit, and 32 bits of data. This instruction is identical to MEMORY_SIZED_ACCESS except that it always does word sized accesses. The size field is implied, and the two lowest address bits are removed. 754 32058H–AVR32–03/09 AT32UC3A Note: This instruction was previously known as MEMORY_ACCESS, and is provided for backwards compatibility. The data register is alternately interpreted by the SAB as an address register and a data register. The SAB starts in address mode after the MEMORY_WORD_ACCESS instruction is selected, and toggles between address and data mode each time a data scan completes with the busy bit cleared. Starting in Run-Test/Idle, SAB data are accessed in the following way: 1. Select the DR Scan path. 2. Scan in the 34-bit address of the data to access, and a direction bit (1=read, 0=write). 3. Go to Update-DR and re-enter Select-DR Scan. 4. For a read operation, scan out the contents of the addressed area. For a write operation, scan in the new contents of the area. 5. Return to Run-Test/Idle. For any operation, the full 34 bits of the address must be provided. For write operations, 32 data bits must be provided, or the result will be undefined. For read operations, shifting may be terminated once the required number of bits have been acquired. Table 36-9. Instructions IR input value MEMORY_WORD_ACCESS details Details 10001 (0x11) peb01 35 bits aaaaaaaa aaaaaaaa aaaaaaaa aaaaaaaa aar xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxx dddddddd dddddddd dddddddd dddddddd xxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xeb xeb dddddddd dddddddd dddddddd dddddddd xxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb IR output value DR Size DR input value (Address phase) DR input value (Data read phase) DR input value (Data write phase) DR output value (Address phase) DR output value (Data read phase) DR output value (Data write phase) 36.9.6 MEMORY_BLOCK_ACCESS This instruction allows access to the entire SAB data area. Up to 32 bits of data are accessed at a time, while the address is sequentially incremented from the previously used address. In this mode, the SAB address, size, and access direction is not provided with each access. Instead, the previous address is auto-incremented depending on the specified size and the previous operation repeated. The address must be set up in advance with MEMORY_SIZE_ACCESS or MEMORY_WORD_ACCESS. It is allowed, but not required, to shift data after shifting the address. This instruction is primarily intended to speed up large quantities of sequential word accesses. It is possible to use it also for byte and halfword accesses, but the overhead in this is case much larger as 32 bits must still be shifted for each access. The following sequence should be used: 755 32058H–AVR32–03/09 AT32UC3A 1. Use the MEMORY_SIZE_ACCESS or MEMORY_WORD_ACCESS to read or write the first location. 2. Apply MEMORY_BLOCK_ACCESS in the IR Scan path. 3. Select the DR Scan path. The address will now have incremented by 1, 2, or 4 (corresponding to the next byte, halfword, or word location). 4. For a read operation, scan out the contents of the next addressed location. For a write operation, scan in the new contents of the next addressed location. 5. Go to Update-DR. 6. If the block access is not complete, return to Select-DR Scan and repeat the access. 7. If the block access is complete, return to Run-Test/Idle. For write operations, 32 data bits must be provided, or the result will be undefined. For read operations, shifting may be terminated once the required number of bits have been acquired. Table 36-10. MEMORY_BLOCK_ACCESS details Instructions IR input value IR output value DR Size DR input value (Data read phase) DR input value (Data write phase) DR output value (Data read phase) DR output value (Data write phase) Details 10010 (0x12) peb01 34 bits xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xx dddddddd dddddddd dddddddd dddddddd xx eb dddddddd dddddddd dddddddd dddddddd xx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxeb The overhead using block word access is 4 cycles per 32 bits of data, resulting in an 88% transfer efficiency, or 2.1 MBytes per second with a 20 MHz TCK frequency. 36.9.7 CANCEL_ACCESS If a very slow memory location is accessed during a SAB memory access, it could take a very long time until the busy bit is cleared, and the SAB becomes ready for the next operation. The CANCEL_ACCESS instruction provides a possibility to abort an ongoing transfer and report a timeout to the user. When the CANCEL_ACCESS instruction is selected, the current access will be terminated as soon as possible. There are no guarantees about how long this will take, as the hardware may not always be able to cancel the access immediately. The SAB is ready to respond to a new command when the busy bit clears. Table 36-11. CANCEL_ACCESS details Instructions IR input value IR output value DR Size DR input value DR output value Details 10011 (0x13) peb01 1 x 0 756 32058H–AVR32–03/09 AT32UC3A 36.9.8 SYNC This instruction allows external debuggers and testers to measure the ratio between the external JTAG clock and the internal system clock. The SYNC data register is a 16-bit counter that counts down to zero using the internal system clock. The busy bit stays high until the counter reaches zero. Starting in Run-Test/Idle, SYNC instruction is used in the following way: 1. Select the DR Scan path. 2. Scan in an 16-bit counter value. 3. Go to Update-DR and re-enter Select-DR Scan. 4. Scan out the busy bit, and retry until the busy bit clears. 5. Calculate an approximation to the internal clock speed using the elapsed time and the counter value. 6. Return to Run-Test/Idle. The full 16-bit counter value must be provided when starting the synch operation, or the result will be undefined. When reading status, shifting may be terminated once the required number of bits have been acquired. Table 36-12. SYNC_ACCESS details Instructions IR input value IR output value DR Size DR input value DR output value Details 10111 (0x17) peb01 16 bits dddddddd dddddddd xxxxxxxx xxxxxxeb 36.9.9 AVR_RESET This instruction allows a debugger or tester to directly control separate reset domains inside the chip. The shift register contains one bit for each controllable reset domain. Setting a bit to one resets that domain and holds it in reset. Setting a bit to zero releases the reset for that domain. See the device specific documentation for the number of reset domains, and what these domains are. For any operation, all bits must be provided or the result will be undefined. Table 36-13. AVR_RESET details Instructions IR input value IR output value DR Size DR input value DR output value Details 01100 (0x0C) p0001 Device specific. Device specific. Device specific. 36.9.10 CHIP_ERASE This instruction allows a programmer to completely erase all nonvolatile memories in a chip. This will also clear any security bits that are set, so the device can be accessed normally. In 757 32058H–AVR32–03/09 AT32UC3A devices without non-volatile memories this instruction does nothing, and appears to complete immediately. The erasing of non-volatile memories starts as soon as the CHIP_ERASE instruction is selected. The CHIP_ERASE instruction selects a 1 bit bypass data register. A chip erase operation should be performed as: 1. Scan in the HALT instruction 2. Scan in the value 1 to halt the CPU 3. Stay in Run-Test/Idle for 10 TCK cycles to let the halt command propagate properly 4. Scan in the CHIP_ERASE instruction 5. Keep scanning the CHIP_ERASE instruction until the busy bit is cleared and the protection bit is cleared. 6. Scan in the HALT instruction 7. Scan in the value 0 to release the CPU 8. Return to Run-Test/Idle 9. Stay in Run-Test/Idle for 10 TCK cycles to let the halt command propagate properly. Table 36-14. CHIP_ERASE details Instructions IR input value IR output value DR Size DR input value DR output value Details 01111 (0x0F) p0b01 Where b is the busy bit. 1 bit x 0 36.9.11 HALT This instruction allows a programmer to easily stop the CPU to ensure that it does not execute invalid code during programming. This instruction selects a 1-bit halt register. Setting this bit to one halts the CPU. Setting this bit to zero releases the CPU to run normally. The value shifted out from the data register is one if the CPU is halted. The HALT instruction can be used in the following way: 10. Scan in the value 1 to halt the CPU 11. Stay in Run-Test/Idle for 10 TCK cycles to let the command propagate properly 12. Use any MEMORY_* instructions to program the device 13. Scan in the HALT instruction 14. Scan in the value 0 to release the CPU 15. Return to Run-Test/Idle 758 32058H–AVR32–03/09 AT32UC3A 16. Stay in Run-Test/Idle for 10 TCK cycles to let the command propagate properly - the device now runs with the new code. Table 36-15. HALT details Instructions IR input value IR output value DR Size DR input value DR output value Details 11100 (0x1C) p0001 1 bit d d 759 32058H–AVR32–03/09 AT32UC3A 36.10 JTAG Data Registers The following device specific registers can be selected as JTAG scan chain depending on the instruction loaded in the JTAG Instruction Register. Additional registers exist, but are implicitly described in the functional description of the relevant instructions. 36.10.1 Device Identification Register The Device Identification Register contains a unique identifier for each product. The register is selected by the IDCODE instruction, which is the default instruction after a JTAG reset. MS B Bit Device ID 31 28 27 Part Number LSB 12 11 Manufacturer ID 1 0 1 Revision 4 bits 16 bits 11 bits 1 bit Revision Part Number Manufacturer ID This is a 4 bit number identifying the revision of the component. Rev A = 0x0, B = 0x1, etc. The part number is a 16 bit code identifying the component. The Manufacturer ID is a 11 bit code identifying the manufacturer. The JTAG manufacturer ID for ATMEL is 0x01F. 36.10.1.1 Device specific ID codes The different device configurations have different JTAG ID codes, as shown in Table 36-16. Note that if the flash controller is statically reset, the ID code will be undefined. Table 36-16. Device and JTAG ID Device name AT32UC3A0512 AT32UC3A0256 AT32UC3A0128 AT32UC3A1512 AT32UC3A1256 AT32UC3A1128 JTAG ID code (r is the revision number) 0xr1EDC03F 0xr1EDF03F 0xr1EE203F 0xr1EDD03F 0xr1EE003F 0xr1EE303F 36.10.2 Reset register The reset register is selected by the AVR_RESET instruction and contains one bit for each reset domain in the device. Setting each bit to one will keep that domain reset until the bit is cleared. LSB Bit Device ID 4 OCD 3 APP 2 RESERVED 1 RESERVED 0 CPU 760 32058H–AVR32–03/09 AT32UC3A CPU APP OCD RSERVED CPU HSB and PB buses On-Chip Debug logic and registers No effect Note: This register is primarily intended for compatibility with other AVR32 devices. Certain operations may not function correctly when parts of the system are reset. It is generally recommended to only write 0x11111 or 0x00000 to these bits to ensure no unintended side effects occur. 36.10.3 Boundary-Scan Chain The Boundary-Scan Chain has the capability of driving and observing the logic levels on the digital I/O pins, as well as driving and observing the logic levels between the digital I/O pins and the internal logic. Typically, output value, output enable, and input data are all available in the boundary scan chain. The boundary scan chain is described in the BDSL (Boundary Scan Description Language) file available at the Atmel web site. 36.11 SAB address map The Service Access Bus (SAB) gives the user access to the internal address space and other features through a 36 bits address space. The 4 MSBs identify the slave number, while the 32 LSBs are decoded within the slave’s address space. The SAB slaves are shown in Table 36-17. Table 36-17. SAB Slaves, addresses and descriptions. Slave Unallocated OCD HSB HSB Memory Service Unit Reserved Address [35:32] 0x0 0x1 0x4 0x5 0x6 Other Description Intentionally unallocated OCD registers HSB memory space, as seen by the CPU Alternative mapping for HSB space, for compatibility with other AVR32 devices. Memory Service Unit registers Unused 761 32058H–AVR32–03/09 AT32UC3A 37. Boot Sequence This chapter summarizes the boot sequence of the AT32UC3A. The behaviour after power-up is controlled by the Power Manager. For specific details, refer to Section 13. ”Power Manager (PM)” on page 53. 37.1 Starting of clocks After power-up, the device will be held in a reset state by the Power-On Reset circuitry, until the power has stabilized throughout the device. Once the power has stabilized, the device will use the internal RC Oscillator as clock source. On system start-up, the PLLs are disabled. All clocks to all modules are running. No clocks have a divided frequency, all parts of the system recieves a clock with the same frequency as the internal RC Oscillator. 37.2 Fetching of initial instructions After reset has been released, the AVR32 UC CPU starts fetching instructions from the reset address, which is 0x8000_0000. This address points to the first address in the internal Flash. The code read from the internal Flash is free to configure the system to use for example the PLLs, to divide the frequency of the clock routed to some of the peripherals, and to gate the clocks to unused peripherals. 762 32058H–AVR32–03/09 AT32UC3A 38. Electrical Characteristics 38.1 Absolute Maximum Ratings* *NOTICE: Stresses beyond those listed under “Absolute Maximum Ratings” may cause permanent damage to the device. This is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational sections of this specification is not implied. Exposure to absolute maximum rating conditions for extended periods may affect device reliability. Operating Temperature......................................-40⋅C to +85⋅C Storage Temperature ..................................... -60°C to +150°C Voltage on Input Pin with respect to Ground except for PC00, PC01, PC02, PC03, PC04, PC05..........................................................-0.3V to 5.5V Voltage on Input Pin with respect to Ground for PC00, PC01, PC02, PC03, PC04, PC05.....................................................................-0.3V to 3.6V Maximum Operating Voltage (VDDCORE, VDDPLL) ..... 1.95V Maximum Operating Voltage (VDDIO, VDDIN, VDDANA).3.6V Total DC Output Current on all I/O Pin for TQFP100 package ................................................. 370 mA for LQGP144 package ................................................. 470 mA 763 32058H–AVR32–03/09 AT32UC3A 38.2 DC Characteristics The following characteristics are applicable to the operating temperature range: TA = -40°C to 85°C, unless otherwise specified and are certified for a junction temperature up to TJ = 100°C. Table 38-1. Symbol VVDDCOR E DC Characteristics Parameter DC Supply Core DC Supply PLL DC Supply Peripheral I/Os Analog reference voltage Input Low-level Voltage All GPIOS except for PC00, PC01, PC02, PC03, PC04, PC05. PC00, PC01, PC02, PC03, PC04, PC05. IOL=-4mA for PA0-PA20, PB0, PB4-PB9, PB11-PB18, PB24-PB26, PB29-PB31, PX0-PX39 Condition Min. 1.65 1.65 3.0 2.6 -0.3 2.0 2.0 Typ. Max 1.95 1.95 3.6 3.6 +0.8 5.5V 3.6V 0.4 Units V V V V V V V V VVDDPLL VVDDIO VREF VIL VIH Input High-level Voltage VOL Output Low-level Voltage IOL=-8mA for PA21-PA30, PB1-PB3, PB10, PB19-PB23, PB27-PB28, PC0PC5 IOH=4mA for PA0-PA20, PB0, PB4-PB9, PB11-PB18, PB24-PB26, PB29-PB31, PX0-PX39 VVDDIO0.4 0.4 V V VOH Output High-level Voltage IOH=8mA for PA21-PA30, PB1-PB3, PB10, PB19-PB23, PB27-PB28, PC0PC5 VVDDIO0.4 -4 -8 4 8 1 7 7 10K 15K V IOL PA0-PA20, PB0, PB4-PB9, PB11-PB18, PB24-PB26, PB29-PB31, PX0-PX39 Output Low-level Current PA21-PA30, PB1-PB3, PB10, PB19PB23, PB27-PB28, PC0-PC5 mA mA mA mA µA pF pF Ohm IOH PA0-PA20, PB0, PB4-PB9, PB11-PB18, PB24-PB26, PB29-PB31, PX0-PX39 Output HIgh-level Current PA21-PA30, PB1-PB3, PB10, PB19PB23, PB27-PB28, PC0-PC5 ILEAK Input Leakage Current Pullup resistors disabled TQFP100 Package LQFP144 Package All GPIO and RESET_N pin. CIN Input Capacitance RPULLUP Pull-up Resistance 764 32058H–AVR32–03/09 AT32UC3A 38.3 Regulator characteristics Table 38-2. Symbol VVDDIN VVDDOUT IOUT ISCR Parameter Supply voltage (input) Supply voltage (output) Maximum DC output current with VVDDIN = 3.3V Maximum DC output current with VVDDIN = 2.7V Static Current of internal regulator Low Power mode (stop, deep stop or static) at TA =25°C 10 Electrical characteristics Condition Min. 3 1.81 Typ. 3.3 1.85 Max. 3.6 1.89 100 90 Units V V mA mA µA Table 38-3. Symbol CIN1 CIN2 COUT1 COUT2 Parameter Input Regulator Capacitor 1 Input Regulator Capacitor 2 Output Regulator Capacitor 1 Output Regulator Capacitor 2 Decoupling requirements Condition Typ. 1 4.7 470 2.2 Techno. NPO X7R NPO X7R Units nF uF pF uF 38.4 Analog characteristics Table 38-4. Electrical characteristics Condition Min. 2.6 Typ. Max. 3.6 Units V Symbol VADVREF Parameter Analog voltage reference (input) Table 38-5. Symbol CVREF1 CVREF2 Parameter Voltage reference Capacitor 1 Voltage reference Capacitor 2 Decoupling requirements Condition Typ. 10 1 Techno . Units nF uF 38.4.1 BOD Table 38-6. BODLEVEL Values Typ. Typ. Typ. Units. BODLEVEL Value 00 0000b 01 0111b 01 1111b 10 0111b 1.40 1.45 1.55 1.65 1.47 1.52 1.6 1.69 1.55 1.6 1.65 1.75 V V V V The values in Table 38-6 describes the values of the BODLEVEL in the flash FGPFR register. 765 32058H–AVR32–03/09 AT32UC3A Table 38-7. Symbol TBOD BOD Timing Parameter Test Conditions Typ. Max. Units. Minimum time with VDDCORE < VBOD to detect power failure Falling VDDCORE from 1.8V to 1.1V 300 800 ns 38.4.2 POR Table 38-8. Electrical Characteristic Test Conditions Min. Typ. Max. Units. Symbol VDDRR VSSFR VPOR+ Parameter VDDCORE rise rate to ensure power-on-reset VDDCORE fall rate to ensure power-on-reset Rising threshold voltage: voltage up to which device is kept under reset by POR on rising VDDCORE Falling threshold voltage: voltage when POR resets device on falling VDDCORE On falling VDDCORE, voltage must go down to this value before supply can rise again to ensure reset signal is released at VPOR+ Minimum time with VDDCORE < VPORTime for reset signal to be propagated to system Rising VDDCORE: VRESTART -> VPOR+ Falling VDDCORE: 1.8V -> VPOR+ Falling VDDCORE: 1.8V -> VRESTART Falling VDDCORE: 1.8V -> 1.1V 0.01 0.01 1.35 1.5 400 1.6 V/ms V/ms V VPOR- 1.25 1.3 1.4 V VRESTART -0.1 0.5 V TPOR TRST 15 200 400 us us 766 32058H–AVR32–03/09 AT32UC3A 38.5 Power Consumption The values in Table 38-9 and Table 38-10 on page 769 are measured values of power consumption with operating conditions as follows: •VDDIO = 3.3V •VDDCORE = VDDPLL = 1.8V •TA = 25°C, TA = 85°C •I/Os are configured in input, pull-up enabled. Figure 38-1. Measurement setup VDDANA VDDIO Amp0 VDDIN Internal Voltage Regulator VDDOUT Amp1 VDDCORE VDDPLL 767 32058H–AVR32–03/09 AT32UC3A These figures represent the power consumption measured on the power supplies. Table 38-9. Mode Power Consumption for Different Modes Conditions Typ : Ta =25 °C CPU running from flash (1). VDDIN=3.3 V. VDDCORE =1.8V. CPU clocked from PLL0 at f MHz Voltage regulator is on. XIN0 : external clock. (1) XIN1 stopped. XIN32 stopped PLL0 running All peripheral clocks activated. GPIOs on internal pull-up. JTAG unconnected with ext pull-up. Typ : Ta = 25 °C CPU running from flash (1). VDDIN=3.3 V. VDDCORE =1.8V. CPU clocked from PLL0 at f MHz Voltage regulator is on. XIN0 : external clock. XIN1 stopped. XIN32 stopped PLL0 running All peripheral clocks activated. GPIOs on internal pull-up. JTAG unconnected with ext pull-up. Typ : Ta = 25 °C CPU running from flash (1). CPU clocked from PLL0 at f MHz Voltage regulator is on. XIN0 : external clock. XIN1 stopped. XIN32 stopped PLL0 running All peripheral clocks activated. GPIOs on internal pull-up. JTAG unconnected with ext pull-up. Typ : Ta = 25 °C CPU running from flash (1). CPU clocked from PLL0 at f MHz Voltage regulator is on. XIN0 : external clock. XIN1 stopped. XIN32 stopped PLL0 running All peripheral clocks activated. GPIOs on internal pull-up. JTAG unconnected with ext pull-up. f = 12 MHz f = 24 MHz f = 36MHz f = 50 MHz Typ. 9 15 20 28 Unit mA mA mA mA Active f = 66 MHz 36.3 mA f = 12 MHz f = 24 MHz f = 36MHz f = 50 MHz 5 10 14 19 mA mA mA mA Idle f = 66 MHz 25.5 mA f = 12 MHz f = 24 MHz f = 36MHz f = 50 MHz 3 6 9 13 mA mA mA mA Frozen f = 66 MHz 16.8 mA f = 12 MHz f = 24 MHz f = 36MHz f = 50 MHz 1 2 3 4 mA mA mA mA Standby f = 66 MHz 4.8 mA 768 32058H–AVR32–03/09 AT32UC3A Table 38-9. Mode Power Consumption for Different Modes Conditions Typ : Ta = 25 °C. CPU is in stop mode GPIOs on internal pull-up. All peripheral clocks de-activated. DM and DP pins connected to ground. XIN0,Xin1 and XIN2 are stopped Typ : Ta = 25 °C.CPU is in deepstop mode GPIOs on internal pull-up. All peripheral clocks de-activated. DM and DP pins connected to ground. XIN0,Xin1 and XIN2 are stopped Typ : Ta = 25 °C. CPU is in static mode GPIOs on internal pull-up. All peripheral clocks de-activated. DM and DP pins connected to ground. XIN0,Xin1 and XIN2 are stopped on Amp0 Typ. 47 Unit uA Stop on Amp1 40 uA on Amp0 36 uA Deepstop on Amp1 28 uA on Amp0 25 uA Static on Amp1 14 uA 1. Core frequency is generated from XIN0 using the PLL so that 140 MHz < fpll0 < 160 MHz and 10 MHz < fxin0 < 12MHz Table 38-10. Power Consumption by Peripheral in Active Mode Peripheral GPIO SMC SDRAMC ADC EBI INTC TWI MACB PDCA PWM RTC SPI SSC TC USART USB Typ. 37 10 4 18 31 25 14 45 µA/MHz 30 36 7 13 13 10 35 45 Unit 38.6 Clock Characteristics These parameters are given in the following conditions: 769 32058H–AVR32–03/09 AT32UC3A • VDDCORE = 1.8V • Ambient Temperature = 25°C 38.6.1 CPU/HSB Clock Characteristics Table 38-11. Core Clock Waveform Parameters Symbol 1/(tCPCPU) tCPCPU Parameter CPU Clock Frequency CPU Clock Period 15,15 Conditions Min Max 66 Units MHz ns 38.6.2 PBA Clock Characteristics Table 38-12. PBA Clock Waveform Parameters Symbol 1/(tCPPBA) tCPPBA Parameter PBA Clock Frequency PBA Clock Period 15,15 Conditions Min Max 66 Units MHz ns 38.6.3 PBB Clock Characteristics Table 38-13. PBB Clock Waveform Parameters Symbol 1/(tCPPBB) tCPPBB Parameter PBB Clock Frequency PBB Clock Period 15,15 Conditions Min Max 66 Units MHz ns 38.7 Crystal Oscillator Characteristis The following characteristics are applicable to the operating temperature range: TA = -40°C to 85°C and worst case of power supply, unless otherwise specified. 38.7.1 32 KHz Oscillator Characteristics Table 38-14. 32 KHz Oscillator Characteristics Symbol 1/(tCP32KHz) CL tST IOSC Parameter Crystal Oscillator Frequency Equivalent Load Capacitance Startup Time CL = 6pF CL = 12.5pF(1) Active mode Current Consumption Standby mode 1. CL is the equivalent load capacitance. 0.1 µA (1) Conditions Min Typ Max 32 768 Unit Hz pF ms µA 6 12.5 600 1200 1.8 Note: 770 32058H–AVR32–03/09 AT32UC3A 38.7.2 Main Oscillators Characteristics Table 38-15. Main Oscillator Characteristics Symbol 1/(tCPMAIN) CL1, CL2 Parameter Crystal Oscillator Frequency Internal Load Capacitance (CL1 = CL2) Duty Cycle tST 1/(tCPXIN) Startup Time External clock XIN Clock Frequency Crystal XIN Clock High Half-period 0.45 0.4 x tCPXIN 0.4 x tCPXIN 16 0.6 x tCPXIN 0.6 x tCPXIN TBD pF MHz 40 Conditions Min 0.45 12 50 60 TBD 50 Typ Max 16 Unit MHz pF % ms MHz tCHXIN tCLXIN CIN XIN Clock Low Half-period XIN Input Capacitance 38.7.3 PLL Characteristics Table 38-16. Phase Lock Loop Characteristics Symbol FOUT FIN IPLL Parameter Output Frequency Input Frequency active mode Current Consumption standby mode TBD µA Conditions Min 80 TBD Typ Max 240 TBD TBD Unit MHz MHz mA 771 32058H–AVR32–03/09 AT32UC3A 38.8 ADC Characteristics Conditions 10-bit resolution mode 8-bit resolution mode Return from Idle Mode 600 ADC Clock = 5 MHz ADC Clock = 8 MHz ADC Clock = 5 MHz ADC Clock = 8 MHz 2 1.25 384(1) 533(2) Min Typ Max 5 8 20 Units MHz MHz µs ns µs µs kSPS kSPS Table 38-17. Channel Conversion Time and ADC Clock Parameter ADC Clock Frequency ADC Clock Frequency Startup Time Track and Hold Acquisition Time Conversion Time Conversion Time Throughput Rate Throughput Rate Notes: 1. Corresponds to 13 clock cycles at 5 MHz: 3 clock cycles for track and hold acquisition time and 10 clock cycles for conversion. 2. Corresponds to 15 clock cycles at 8 MHz: 5 clock cycles for track and hold acquisition time and 10 clock cycles for conversion. Table 38-18. External Voltage Reference Input Parameter ADVREF Input Voltage Range ADVREF Average Current Current Consumption on VDDANA Note: On 13 samples with ADC Clock = 5 MHz Conditions Min 2.6 200 Typ Max VDDANA 250 TBD Units V µA mA ADVREF should be connected to GND to avoid extra consumption in case ADC is not used. Table 38-19. Analog Inputs Parameter Input Voltage Range Input Leakage Current Input Capacitance Min 0 TBD 17 Typ Max VADVREF µA pF Units Table 38-20. Transfer Characteristics in 8-bit mode Parameter Resolution Absolute Accuracy Integral Non-linearity Differential Non-linearity Offset Error Gain Error f=5MHz f=8MHz f=5MHz f=8MHz f=5MHz f=8MHz f=5MHz f=5MHz -0.5 -0.5 0.35 0.5 0.3 0.5 Conditions Min Typ 8 0.8 1.5 0.5 1.0 0.5 1.0 0.5 0.5 Max Units Bit LSB LSB LSB LSB LSB LSB LSB LSB 772 32058H–AVR32–03/09 AT32UC3A Table 38-21. Transfer Characteristics in 10-bit mode Parameter Resolution Absolute Accuracy Integral Non-linearity Differential Non-linearity Offset Error Gain Error f=5MHz f=5MHz f=5MHz f=2.5MHz f=5MHz f=5MHz -2 -2 1.5 1 0.6 Conditions Min Typ 10 3 2 2 1 2 2 Max Units Bit LSB LSB LSB LSB LSB LSB 773 32058H–AVR32–03/09 AT32UC3A 38.9 EBI Timings These timings are given for worst case process, T = 85⋅C, VDDCORE = 1.65V, VDDIO = 3V and 40 pF load capacitance. Table 38-22. SMC Clock Signal. Symbol 1/(tCPSMC) Note: Parameter SMC Controller Clock Frequency Max(1) 1/(tcpcpu) Units MHz 1. The maximum frequency of the SMC interface is the same as the max frequency for the HSB. Table 38-23. SMC Read Signals with Hold Settings Symbol Parameter NRD Controlled (READ_MODE = 1) SMC1 SMC2 SMC3 SMC4 SMC5 SMC6 SMC7 SMC8 SMC9 Min Units Data Setup before NRD High Data Hold after NRD High NRD High to NBS0/A0 Change NRD High to NBS1 Change(1) NRD High to NBS2/A1 Change NRD High to NBS3 Change(1) NRD High to A2 - A25 Change NRD High to NCS Inactive(1) NRD Pulse Width (1) (1) (1) 12 0 nrd hold length * tCPSMC - 1.3 nrd hold length * tCPSMC - 1.3 nrd hold length * tCPSMC - 1.3 nrd hold length * tCPSMC - 1.3 nrd hold length * tCPSMC - 1.3 (nrd hold length - ncs rd hold length) * tCPSMC - 2.3 nrd pulse length * tCPSMC - 1.4 ns NRD Controlled (READ_MODE = 0) SMC10 SMC11 SMC12 SMC13 SMC14 SMC15 SMC16 SMC17 SMC18 Note: Data Setup before NCS High Data Hold after NCS High NCS High to NBS0/A0 Change (1) 11.5 0 ncs rd hold length * tCPSMC - 2.3 ncs rd hold length * tCPSMC - 2.3 ncs rd hold length * tCPSMC - 2.3 ncs rd hold length * tCPSMC - 2.3 ncs rd hold length * tCPSMC - 4 ncs rd hold length - nrd hold length)* tCPSMC - 1.3 ncs rd pulse length * tCPSMC - 3.6 ns NCS High to NBS0/A0 Change(1) NCS High to NBS2/A1 Change NCS High to NBS3 Change(1) NCS High to A2 - A25 Change NCS High to NRD Inactive(1) NCS Pulse Width (1) (1) 1. hold length = total cycle duration - setup duration - pulse duration. “hold length” is for “ncs rd hold length” or “nrd hold length”. 774 32058H–AVR32–03/09 AT32UC3A Table 38-24. SMC Read Signals with no Hold Settings Symbol Parameter NRD Controlled (READ_MODE = 1) SMC19 SMC20 Min Units Data Setup before NRD High Data Hold after NRD High NRD Controlled (READ_MODE = 0) 13.7 ns 1 SMC21 SMC22 Data Setup before NCS High Data Hold after NCS High 13.3 ns 0 Table 38-25. SMC Write Signals with Hold Settings Symbol Parameter NRD Controlled (READ_MODE = 1) SMC23 SMC24 SMC25 SMC26 SMC29 SMC30 SMC31 SMC32 SMC33 Min Units Data Out Valid before NWE High Data Out Valid after NWE High(1) NWE High to NBS0/A0 Change NWE High to NBS1 Change(1) NWE High to NBS2/A1 Change NWE High to NBS3 Change(1) NWE High to A2 - A25 Change NWE High to NCS Inactive(1) NWE Pulse Width (1) (1) (1) (nwe pulse length - 1) * tCPSMC - 0.9 nwe hold length * tCPSMC - 6 nwe hold length * tCPSMC - 1.9 nwe hold length * tCPSMC - 1.9 nwe hold length * tCPSMC - 1.9 nwe hold length * tCPSMC - 1.9 nwe hold length * tCPSMC - 1.7 (nwe hold length - ncs wr hold length)* tCPSMC - 2.9 nwe pulse length * tCPSMC - 0.9 ns NRD Controlled (READ_MODE = 0) SMC34 SMC35 SMC36 Note: Data Out Valid before NCS High Data Out Valid after NCS High(1) NCS High to NWE Inactive (1) (ncs wr pulse length - 1)* tCPSMC - 4.6 ncs wr hold length * tCPSMC - 5.8 (ncs wr hold length - nwe hold length)* tCPSMC - 0.6 ns 1. hold length = total cycle duration - setup duration - pulse duration. “hold length” is for “ncs wr hold length” or “nwe hold length" 775 32058H–AVR32–03/09 AT32UC3A Table 38-26. SMC Write Signals with No Hold Settings (NWE Controlled only). Symbol SMC37 SMC38 SMC39 SMC40 SMC41 SMC42 SMC43 SMC44 SMC45 Parameter Min Units NWE Rising to A2-A25 Valid NWE Rising to NBS0/A0 Valid NWE Rising to NBS1 Change NWE Rising to A1/NBS2 Change NWE Rising to NBS3 Change NWE Rising to NCS Rising Data Out Valid before NWE Rising Data Out Valid after NWE Rising NWE Pulse Width 5.4 5 5 5 5 5.1 (nwe pulse length - 1) * tCPSMC - 1.2 5 nwe pulse length * tCPSMC - 0.9 ns Figure 38-2. SMC Signals for NCS Controlled Accesses. SMC16 SMC16 SMC16 A2-A25 SMC12 SMC13 SMC14 SMC15 SMC12 SMC13 SMC14 SMC15 SMC12 SMC13 SMC14 SMC15 A0/A1/NBS[3:0] NRD SMC17 SMC17 NCS SMC18 SMC22 SMC18 SMC18 SMC21 SMC10 SMC11 SMC34 SMC35 D0 - D15 SMC36 NWE 776 32058H–AVR32–03/09 AT32UC3A Figure 38-3. SMC Signals for NRD and NRW Controlled Accesses. SMC7 SMC37 SMC7 SMC31 A2-A25 SMC3 SMC4 SMC5 SMC6 SMC38 SMC39 SMC40 SMC41 SMC3 SMC4 SMC5 SMC6 SMC25 SMC26 SMC29 SMC30 A0/A1/NBS[3:0] SMC42 SMC8 SMC32 NCS SMC8 NRD SMC9 SMC9 SMC19 SMC20 SMC43 SMC44 SMC1 SMC2 SMC23 SMC24 D0 - D15 SMC45 SMC33 NWE 38.9.1 SDRAM Signals These timings are given for 10 pF load on SDCK and 40 pF on other signals. Table 38-27. SDRAM Clock Signal. Symbol 1/(tCPSDCK) Note: Parameter SDRAM Controller Clock Frequency Max(1) 1/(tcpcpu) Units MHz 1. The maximum frequency of the SDRAMC interface is the same as the max frequency for the HSB. Table 38-28. SDRAM Clock Signal. Symbol SDRAMC1 SDRAMC2 SDRAMC3 SDRAMC4 SDRAMC5 SDRAMC6 SDRAMC7 SDRAMC8 SDRAMC9 SDRAMC10 Parameter Min 7.4 3.2 7 2.9 7.5 1.6 7.2 2.3 7.6 1.9 Units ns SDCKE High before SDCK Rising Edge SDCKE Low after SDCK Rising Edge SDCKE Low before SDCK Rising Edge SDCKE High after SDCK Rising Edge SDCS Low before SDCK Rising Edge SDCS High after SDCK Rising Edge RAS Low before SDCK Rising Edge RAS High after SDCK Rising Edge SDA10 Change before SDCK Rising Edge SDA10 Change after SDCK Rising Edge 777 32058H–AVR32–03/09 AT32UC3A Table 38-28. SDRAM Clock Signal. Symbol SDRAMC11 SDRAMC12 SDRAMC13 SDRAMC14 SDRAMC15 SDRAMC16 SDRAMC17 SDRAMC18 SDRAMC19 SDRAMC20 SDRAMC23 SDRAMC24 SDRAMC25 SDRAMC26 Parameter Min 6.2 2.2 6.3 2.4 7.4 1.9 6.4 ns 2.2 9 0 7.6 1.8 7.1 1.5 Units Address Change before SDCK Rising Edge Address Change after SDCK Rising Edge Bank Change before SDCK Rising Edge Bank Change after SDCK Rising Edge CAS Low before SDCK Rising Edge CAS High after SDCK Rising Edge DQM Change before SDCK Rising Edge DQM Change after SDCK Rising Edge D0-D15 in Setup before SDCK Rising Edge D0-D15 in Hold after SDCK Rising Edge SDWE Low before SDCK Rising Edge SDWE High after SDCK Rising Edge D0-D15 Out Valid before SDCK Rising Edge D0-D15 Out Valid after SDCK Rising Edge 778 32058H–AVR32–03/09 AT32UC3A Figure 38-4. SDRAMC Signals relative to SDCK. SDCK SDRAMC1 SDRAMC2 SDRAMC3 SDRAMC4 SDCKE SDRAMC5 SDRAMC6 SDRAMC5 SDRAMC6 SDRAMC5 SDRAMC6 SDCS SDRAMC7 SDRAMC8 RAS SDRAMC15 SDRAMC16 SDRAMC15 SDRAMC16 CAS SDRAMC23 SDRAMC24 SDWE SDRAMC9 SDRAMC10 SDRAMC9 SDRAMC10 SDRAMC9 SDRAMC10 SDA10 SDRAMC11 SDRAMC12 SDRAMC11 SDRAMC12 SDRAMC11 SDRAMC12 A0 - A9, A11 - A13 SDRAMC13 SDRAMC14 SDRAMC13 SDRAMC14 SDRAMC13 SDRAMC14 BA0/BA1 SDRAMC17 SDRAMC18 SDRAMC17 SDRAMC18 DQM0 DQM3 SDRAMC19 SDRAMC20 D0 - D15 Read SDRAMC25 SDRAMC26 D0 - D15 to Write 779 32058H–AVR32–03/09 AT32UC3A 38.10 JTAG Timings 38.10.1 JTAG Interface Signals Table 38-29. JTAG Interface Timing specification Symbol JTAG0 JTAG1 JTAG2 JTAG3 JTAG4 JTAG5 JTAG6 JTAG7 JTAG8 JTAG9 JTAG10 Note: Parameter TCK Low Half-period TCK High Half-period TCK Period TDI, TMS Setup before TCK High TDI, TMS Hold after TCK High TDO Hold Time TCK Low to TDO Valid Device Inputs Setup Time Device Inputs Hold Time Device Outputs Hold Time TCK to Device Outputs Valid 1. VVDDIO from 3.0V to 3.6V, maximum external capacitor = 40pF Conditions (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) Min 6 3 9 1 0 4 Max Units ns ns ns ns ns ns 6 ns ns ns ns ns 780 32058H–AVR32–03/09 AT32UC3A Figure 38-5. JTAG Interface Signals JTAG2 TCK JTAG JTAG1 0 TMS/TDI JTAG3 JTAG4 TDO JTAG5 JTAG6 Device Inputs JTAG7 JTAG8 Device Outputs JTAG9 JTAG10 38.11 SPI Characteristics Figure 38-6. SPI Master mode with (CPOL = NCPHA = 0) or (CPOL= NCPHA= 1) SPCK SPI0 MISO SPI1 SPI2 MOSI 781 32058H–AVR32–03/09 AT32UC3A Figure 38-7. SPI Master mode with (CPOL=0 and NCPHA=1) or (CPOL=1 and NCPHA=0) SPCK SPI3 MISO SPI4 SPI5 MOSI Figure 38-8. SPI Slave mode with (CPOL=0 and NCPHA=1) or (CPOL=1 and NCPHA=0) SPCK SPI6 MISO SPI7 MOSI SPI8 Figure 38-9. SPI Slave mode with (CPOL = NCPHA = 0) or (CPOL= NCPHA= 1) SPCK SPI9 MISO SPI10 MOSI SPI11 782 32058H–AVR32–03/09 AT32UC3A Table 38-30. SPI Timings Symbol SPI0 SPI1 SPI2 SPI3 SPI4 SPI5 SPI6 SPI7 SPI8 SPI9 SPI10 SPI11 Notes: Parameter MISO Setup time before SPCK rises (master) MISO Hold time after SPCK rises (master) SPCK rising to MOSI Delay (master) MISO Setup time before SPCK falls (master) MISO Hold time after SPCK falls (master) SPCK falling to MOSI Delay (master) SPCK falling to MISO Delay (slave) MOSI Setup time before SPCK rises (slave) MOSI Hold time after SPCK rises (slave) SPCK rising to MISO Delay (slave) MOSI Setup time before SPCK falls (slave) MOSI Hold time after SPCK falls (slave) Conditions 3.3V domain 3.3V domain 3.3V domain 3.3V domain (1) (1) (1) (1) Min 22 + (tCPMCK)/2 0 (2) Max Units ns ns 7 22 + (tCPMCK)/2 0 7 26.5 0 1.5 27 0 1 (2) ns ns ns ns ns ns ns ns ns ns 3.3V domain (1) 3.3V domain (1) 3.3V domain 3.3V domain 3.3V domain 3.3V domain 3.3V domain 3.3V domain (1) (1) (1) (1) (1) (1) 1. 3.3V domain: VVDDIO from 3.0V to 3.6V, maximum external capacitor = 40 pF. 2. tCPMCK: Master Clock period in ns. 38.12 MACB Characteristics Table 38-31. Ethernet MAC Signals Symbol EMAC1 EMAC2 EMAC3 Notes: Parameter Setup for EMDIO from EMDC rising Hold for EMDIO from EMDC rising EMDIO toggling from EMDC falling 1. f: MCK frequency (MHz) 2. VVDDIO from 3.0V to 3.6V, maximum external capacitor = 20 pF Conditions Load: 20pF (2) Min (ns) Max (ns) Load: 20pF(2) Load: 20pF(2) Table 38-32. Ethernet MAC MII Specific Signals Symbol EMAC4 EMAC5 EMAC6 EMAC7 EMAC8 EMAC9 EMAC10 EMAC11 Parameter Setup for ECOL from ETXCK rising Hold for ECOL from ETXCK rising Setup for ECRS from ETXCK rising Hold for ECRS from ETXCK rising ETXER toggling from ETXCK rising ETXEN toggling from ETXCK rising ETX toggling from ETXCK rising Setup for ERX from ERXCK Conditions Load: 20pF Load: 20pF Load: 20pF (1) (1) (1) Min (ns) 3 0 3 0 Max (ns) Load: 20pF (1) Load: 20pF Load: 20pF Load: 20pF (1) (1) (1) 15 15 15 1 Load: 20pF (1) 783 32058H–AVR32–03/09 AT32UC3A Table 38-32. Ethernet MAC MII Specific Signals Symbol EMAC12 EMAC13 EMAC14 EMAC15 EMAC16 Note: Parameter Hold for ERX from ERXCK Setup for ERXER from ERXCK Hold for ERXER from ERXCK Setup for ERXDV from ERXCK Hold for ERXDV from ERXCK Conditions Load: 20pF Load: 20pF Load: 20pF (1) (1) (1) Min (ns) 1.5 1 0.5 1.5 1 Max (ns) Load: 20pF (1) Load: 20pF (1) 1. VVDDIO from 3.0V to 3.6V, maximum external capacitor = 20 pF Figure 38-10. Ethernet MAC MII Mode EMDC EMAC1 EMDIO EMAC4 ECOL EMAC6 ECRS EMAC7 EMAC5 EMAC2 EMAC3 ETXCK EMAC8 ETXER EMAC9 ETXEN EMAC10 ETX[3:0] ERXCK EMAC11 ERX[3:0] EMAC13 ERXER EMAC15 ERXDV EMAC16 EMAC14 EMAC12 784 32058H–AVR32–03/09 AT32UC3A Table 38-33. Ethernet MAC RMII Specific Signals Symbol EMAC21 EMAC22 EMAC23 EMAC24 EMAC25 EMAC26 EMAC27 EMAC28 Parameter ETXEN toggling from EREFCK rising ETX toggling from EREFCK rising Setup for ERX from EREFCK Hold for ERX from EREFCK Setup for ERXER from EREFCK Hold for ERXER from EREFCK Setup for ECRSDV from EREFCK Hold for ECRSDV from EREFCK Min (ns) 7 7 1.5 0 1.5 0 1.5 0 Max (ns) 14.5 14.7 Figure 38-11. Ethernet MAC RMII Mode EREFCK EMAC21 ETXEN EMAC22 ETX[1:0] EMAC23 ERX[1:0] EMAC25 ERXER EMAC27 ECRSDV EMAC28 EMAC26 EMAC24 38.13 Flash Characteristics The following table gives the device maximum operating frequency depending on the field FWS of the Flash FSR register. This field defines the number of wait states required to access the Flash Memory. Table 38-34. Flash Wait States FWS 0 1 Read Operations 1 cycle 2 cycles Maximum Operating Frequency (MHz) 33 66 785 32058H–AVR32–03/09 AT32UC3A Table 38-35. Programming Time Page Programming Time (ms) 4 16 Chip Erase Time (ms) 4 16 Temperature Operating Range Part Industrial Automotive 786 32058H–AVR32–03/09 AT32UC3A 39. Mechanical Characteristics 39.1 39.1.1 Thermal Considerations Thermal Data Table 39-1 summarizes the thermal resistance data depending on the package. Table 39-1. Symbol θJA θJC θJA θJC Thermal Resistance Data Parameter Junction-to-ambient thermal resistance Junction-to-case thermal resistance Junction-to-ambient thermal resistance Junction-to-case thermal resistance Still Air Condition Still Air Package TQFP100 TQFP100 LQFP144 LQFP144 Typ 43.4 5.5 39.8 8.9 ⋅C/W Unit ⋅C/W 39.1.2 Junction Temperature The average chip-junction temperature, TJ, in °C can be obtained from the following: 1. 2. T J = T A + ( P D × θ JA ) T J = T A + ( P D × ( θ HEATSINK + θ JC ) ) where: • θJA = package thermal resistance, Junction-to-ambient (°C/W), provided in Table 39-1 on page 787. • θJC = package thermal resistance, Junction-to-case thermal resistance (°C/W), provided in Table 39-1 on page 787. • θHEAT SINK = cooling device thermal resistance (°C/W), provided in the device datasheet. • PD = device power consumption (W) estimated from data provided in the section ”Power Consumption” on page 767. • TA = ambient temperature (°C). From the first equation, the user can derive the estimated lifetime of the chip and decide if a cooling device is necessary or not. If a cooling device is to be fitted on the chip, the second equation should be used to compute the resulting average chip-junction temperature TJ in °C. 787 32058H–AVR32–03/09 AT32UC3A 39.2 Package Drawings Figure 39-1. TQFP-100 package drawing Table 39-2. 500 Device and Package Maximum Weight mg Table 39-3. Package Characteristics Jdec J-STD0-20D - MSL 3 Moisture Sensitivity Level Table 39-4. Package Reference MS-026 E3 JEDEC Drawing Reference JESD97 Classification 788 32058H–AVR32–03/09 AT32UC3A Figure 39-2. LQFP-144 package drawing Table 39-5. 1300 Device and Package Maximum Weight mg Table 39-6. Package Characteristics Jdec J-STD0-20D - MSL 3 Moisture Sensitivity Level Table 39-7. Package Reference MS-026 E3 JEDEC Drawing Reference JESD97 Classification 789 32058H–AVR32–03/09 AT32UC3A Figure 39-3. FFBGA-144 package drawing Table 39-8. TBD Device and Package Maximum Weight mg Table 39-9. Package Characteristics TBD Moisture Sensitivity Level Table 39-10. Package Reference JEDEC Drawing Reference JESD97 Classification MS-026 E3 790 32058H–AVR32–03/09 AT32UC3A 39.3 Soldering Profile Table 39-11 gives the recommended soldering profile from J-STD-20. Table 39-11. Soldering Profile Profile Feature Average Ramp-up Rate (217°C to Peak) Preheat Temperature 175°C ±25°C Time Maintained Above 217°C Time within 5⋅C of Actual Peak Temperature Peak Temperature Range Ramp-down Rate Time 25⋅C to Peak Temperature Note: Green Package 3°C/sec Min. 150 °C, Max. 200 °C 60-150 sec 30 sec 260 °C 6 °C/sec Max. 8 minutes It is recommended to apply a soldering temperature higher than 250°C. A maximum of three reflow passes is allowed per component. 791 32058H–AVR32–03/09 AT32UC3A 40. Ordering Information Table 40-1. Device AT32UC3A0512 Ordering Information Ordering Code AT32UC3A0512-ALUT AT32UC3A0512-ALUR AT32UC3A0512-ALTR AT32UC3A0512-ALTT AT32UC3A0512-ALTES AT32UC3A0512-CTUT AT32UC3A0512-CTUR Package 144 LQFP 144 LQFP 144 LQFP 144 LQFP 144 LQFP 144 FFBGA 144 FFBGA 144 LQFP 144 LQFP 144 FFBGA 144 FFBGA 144 LQFP 144 LQFP 144 FFBGA 144 FFBGA 100 TQFP 100 TQFP 100 TQFP 100 TQFP 100 TQFP 100 TQFP Conditioning Tray Reel Reel Tray Tray Tray Reel Tray Reel Tray Reel Tray Reel Tray Reel Tray Reel Tray Reel Tray Reel Temperature Operating Range Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Automotive (-40⋅C to 85⋅C) Automotive (-40⋅C to 85⋅C) Automotive (-40⋅C to 85⋅C) samples Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) Industrial (-40⋅C to 85⋅C) AT32UC3A0256 AT32UC3A0256-ALUT AT32UC3A0256-ALUR AT32UC3A0256-CTUT AT32UC3A0256-CTUR AT32UC3A0128 AT32UC3A0128-ALUT AT32UC3A0128-ALUR AT32UC3A0128-CTUT AT32UC3A0128-CTUR AT32UC3A1512 AT32UC3A1256 AT32UC3A1128 AT32UC3A1512-AUT AT32UC3A1512-AUR AT32UC3A1256-AUT AT32UC3A1256-AUR AT32UC3A1128-AUT AT32UC3A1128-AUR 40.1 Automotive Quality Grade The AT32UC3A have been developed and manufactured according to the most stringent requirements of the international standard ISO-TS-16949. This data sheet will contain limit values extracted from the results of extensive characterization (Temperature and Voltage). The quality and reliability of the AT32UC3A is verified during regular product qualification as per AEC-Q100 grade 3. As indicated in the ordering information paragraph, the product is available in only one temperature grade T: -40°C / + 85°C. 792 32058H–AVR32–03/09 AT32UC3A 41. Errata All industrial parts labelled with -UES (engineering samples) are revision E parts. 41.1 41.1.1 Rev. K PWM 1. PWM channel interrupt enabling triggers an interrupt When enabling a PWM channel that is configured with center aligned period (CALG=1), an interrupt is signalled. Fix/Workaround When using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 2. PWM counter restarts at 0x0001 The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first PWM period has one more clock cycle. Fix/Workaround - The first period is 0x0000, 0x0001, ..., period - Consecutive periods are 0x0001, 0x0002, ..., period 3. PWM update period to a 0 value does not work It is impossible to update a period equal to 0 by the using the PWM update register (PWM_CUPD). Fix/Workaround Do not update the PWM_CUPD register with a value equal to 0. 41.1.2 ADC 1. Sleep Mode activation needs additional A to D conversion If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode before after the next AD conversion. Fix/Workaround Activate the sleep mode in the mode register and then perform an AD conversion. 41.1.3 SPI 1. SPI Slave / PDCA transfer: no TX UNDERRUN flag There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to be informed of a character lost in transmission. Fix/Workaround For PDCA transfer: none. 2. SPI FDIV option does not work Selecting clock signal using FDIV = 1 does not work as specified. Fix/Workaround Do not set FDIV = 1. 793 32058H–AVR32–03/09 AT32UC3A 3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and NCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn't equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK. Fix/workaround When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if CPOL=1 and CPHA=0. 4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first transfer In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or during the first transfer. Fix/Workaround 1. Set slave mode, set required CPOL/CPHA. 2. Enable SPI. 3. Set the polarity CPOL of the line in the opposite value of the required one. 4. Set the polarity CPOL to the required one. 5. Read the RXHOLDING register. Transfers can now befin and RXREADY will now behave as expected. 5. SPI Disable does not work in Slave mode Fix/workaround Read the last received data then perform a Software reset. 41.1.4 Power Manager 1. If the BOD level is higher than VDDCORE, the part is constantly under reset If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will be in constant reset. Fix/Workaround Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than VDDCORE max and disable the BOD. 41.1.5 PDCA 1. Wrong PDCA behavior when using two PDCA channels with the same PID. Fix/Workaround The same PID should not be assigned to more than one channel. 41.1.6 TWI 1. The TWI RXRDY flag in SR register is not reset when a software reset is performed. Fix/Workaround After a Software Reset, the register TWI RHR must be read. 41.1.7 USART 1. ISO7816 info register US_NER cannot be read The NER register always returns zero. Fix/Workaround None Processor and Architecture 1. LDM instruction with PC in the register list and without ++ increments Rp 41.1.8 794 32058H–AVR32–03/09 AT32UC3A For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the increment of the pointer is done in parallel with the testing of R12. Fix/Workaround None. 795 32058H–AVR32–03/09 AT32UC3A 41.2 41.2.1 Rev. J PWM 1. PWM channel interrupt enabling triggers an interrupt When enabling a PWM channel that is configured with center aligned period (CALG=1), an interrupt is signalled. Fix/Workaround When using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 2. PWM counter restarts at 0x0001 The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first PWM period has one more clock cycle. Fix/Workaround - The first period is 0x0000, 0x0001, ..., period - Consecutive periods are 0x0001, 0x0002, ..., period 3. PWM update period to a 0 value does not work It is impossible to update a period equal to 0 by the using the PWM update register (PWM_CUPD). Fix/Workaround Do not update the PWM_CUPD register with a value equal to 0. 41.2.2 ADC 1. Sleep Mode activation needs additional A to D conversion If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode before after the next AD conversion. Fix/Workaround Activate the sleep mode in the mode register and then perform an AD conversion. 41.2.3 SPI 1. SPI Slave / PDCA transfer: no TX UNDERRUN flag There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to be informed of a character lost in transmission. Fix/Workaround For PDCA transfer: none. 2. SPI FDIV option does not work Selecting clock signal using FDIV = 1 does not work as specified. Fix/Workaround Do not set FDIV = 1. 3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and NCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn't equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK. Fix/workaround 796 32058H–AVR32–03/09 AT32UC3A When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if CPOL=1 and CPHA=0. 4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first transfer In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or during the first transfer. Fix/Workaround 1. Set slave mode, set required CPOL/CPHA. 2. Enable SPI. 3. Set the polarity CPOL of the line in the opposite value of the required one. 4. Set the polarity CPOL to the required one. 5. Read the RXHOLDING register. Transfers can now befin and RXREADY will now behave as expected. 5. SPI Disable does not work in Slave mode Fix/workaround Read the last received data then perform a Software reset. 41.2.4 Power Manager 1. If the BOD level is higher than VDDCORE, the part is constantly under reset If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will be in constant reset. Fix/Workaround Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than VDDCORE max and disable the BOD. 41.2.5 PDCA 1. Wrong PDCA behavior when using two PDCA channels with the same PID. Fix/Workaround The same PID should not be assigned to more than one channel. 41.2.6 TWI 1. The TWI RXRDY flag in SR register is not reset when a software reset is performed. Fix/Workaround After a Software Reset, the register TWI RHR must be read. 41.2.7 SDRAMC 1. Code execution from external SDRAM does not work Code execution from SDRAM does not work. Fix/Workaround Do not run code from SDRAM. 41.2.8 GPIO 1. PA29 (TWI SDA) and PA30 (TWI SCL) GPIO VIH (input high voltage) is 3.6V max instead of 5V tolerant The following GPIOs are not 5V tolerant : PA29 and PA30. Fix/Workaround 797 32058H–AVR32–03/09 AT32UC3A None. 41.2.9 USART 1. ISO7816 info register US_NER cannot be read The NER register always returns zero. Fix/Workaround None Processor and Architecture 1. LDM instruction with PC in the register list and without ++ increments Rp For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the increment of the pointer is done in parallel with the testing of R12. Fix/Workaround None. 41.2.10 2. RETE instruction does not clear SREG[L] from interrupts. The RETE instruction clears SREG[L] as expected from exceptions. Fix/Workaround When using the STCOND instruction, clear SREG[L] in the stacked value of SR before returning from interrupts with RETE. 3. Exceptions when system stack is protected by MPU RETS behaves incorrectly when MPU is enabled and MPU is configured so that system stack is not readable in unprivileged mode. Fix/Woraround Workaround 1: Make system stack readable in unprivileged mode, or Workaround 2: Return from supervisor mode using rete instead of rets. This requires : 1. Changing the mode bits from 001b to 110b before issuing the instruction. Updating the mode bits to the desired value must be done using a single mtsr instruction so it is done atomically. Even if this step is described in general as not safe in the UC technical reference guide, it is safe in this very specific case. 2. Execute the RETE instruction. 798 32058H–AVR32–03/09 AT32UC3A 41.3 41.3.1 Rev. I PWM 1. PWM channel interrupt enabling triggers an interrupt When enabling a PWM channel that is configured with center aligned period (CALG=1), an interrupt is signalled. Fix/Workaround When using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 2. PWM counter restarts at 0x0001 The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first PWM period has one more clock cycle. Fix/Workaround - The first period is 0x0000, 0x0001, ..., period - Consecutive periods are 0x0001, 0x0002, ..., period 3. PWM update period to a 0 value does not work It is impossible to update a period equal to 0 by the using the PWM update register (PWM_CUPD). Fix/Workaround Do not update the PWM_CUPD register with a value equal to 0. 41.3.2 ADC 1. Sleep Mode activation needs additional A to D conversion If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode before after the next AD conversion. Fix/Workaround Activate the sleep mode in the mode register and then perform an AD conversion. 41.3.3 SPI 1. SPI Slave / PDCA transfer: no TX UNDERRUN flag There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to be informed of a character lost in transmission. Fix/Workaround For PDCA transfer: none. 2. SPI FDIV option does not work Selecting clock signal using FDIV = 1 does not work as specified. Fix/Workaround Do not set FDIV = 1. 3. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and NCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn't equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK. Fix/workaround 799 32058H–AVR32–03/09 AT32UC3A When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if CPOL=1 and CPHA=0. 4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first transfer In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or during the first transfer. Fix/Workaround 1. Set slave mode, set required CPOL/CPHA. 2. Enable SPI. 3. Set the polarity CPOL of the line in the opposite value of the required one. 4. Set the polarity CPOL to the required one. 5. Read the RXHOLDING register. Transfers can now befin and RXREADY will now behave as expected. 5. SPI Disable does not work in Slave mode Fix/workaround Read the last received data then perform a Software reset. 41.3.4 Power Manager 1. If the BOD level is higher than VDDCORE, the part is constantly under reset If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will be in constant reset. Fix/Workaround Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than VDDCORE max and disable the BOD. 41.3.5 Flashc 1. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP, EP, EA, WUP, EUP commands may happen - After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the other half of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, reading (data read or code fetch) the second half (last 256 kB) of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. Fix/Workaround Flashc WP, EP, EA, WUP, EUP commands: these commands must be issued from RAM or through the EBI. After these commands, read twice one flash page initialized to 00h in each half part of the flash. 41.3.6 PDCA 1. Wrong PDCA behavior when using two PDCA channels with the same PID. 800 32058H–AVR32–03/09 AT32UC3A Workaround/fix The same PID should not be assigned to more than one channel. 41.3.7 GPIO 1. Some GPIO VIH (input high voltage) are 3.6V max instead of 5V tolerant Only 11 GPIOs remain 5V tolerant (VIHmax=5V):PB01, PB02, PB03, PB10, PB19, PB20, PB21, PB22, PB23, PB27, PB28. Workaround/fix None. 41.3.8 USART 1. ISO7816 info register US_NER cannot be read The NER register always returns zero. Fix/Workaround None. 41.3.9 TWI 1. The TWI RXRDY flag in SR register is not reset when a software reset is performed. Fix/Workaround After a Software Reset, the register TWI RHR must be read. 41.3.10 SDRAMC 1. Code execution from external SDRAM does not work Code execution from SDRAM does not work. 41.3.11 Fix/Workaround Do not run code from SDRAM. Processor and Architecture 1. LDM instruction with PC in the register list and without ++ increments Rp For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the increment of the pointer is done in parallel with the testing of R12. Fix/Workaround None. 2. RETE instruction does not clear SREG[L] from interrupts. The RETE instruction clears SREG[L] as expected from exceptions. Fix/Workaround When using the STCOND instruction, clear SREG[L] in the stacked value of SR before returning from interrupts with RETE. 3. Exceptions when system stack is protected by MPU RETS behaves incorrectly when MPU is enabled and MPU is configured so that system stack is not readable in unprivileged mode. Fix/Woraround Workaround 1: Make system stack readable in unprivileged mode, or Workaround 2: Return from supervisor mode using rete instead of rets. This requires : 1. Changing the mode bits from 001b to 110b before issuing the instruction. Updating the mode bits to the desired value must be done using a single mtsr instruction so it is done atomically. Even if this step is described in general as not safe in the UC technical reference guide, it is safe in this very 801 32058H–AVR32–03/09 AT32UC3A specific case. 2. Execute the RETE instruction. 802 32058H–AVR32–03/09 AT32UC3A 41.4 41.4.1 Rev. H PWM 1. PWM channel interrupt enabling triggers an interrupt When enabling a PWM channel that is configured with center aligned period (CALG=1), an interrupt is signalled. Fix/Workaround When using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 2. PWM counter restarts at 0x0001 The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first PWM period has one more clock cycle. Fix/Workaround - The first period is 0x0000, 0x0001, ..., period - Consecutive periods are 0x0001, 0x0002, ..., period 3. PWM update period to a 0 value does not work It is impossible to update a period equal to 0 by the using the PWM update register (PWM_CUPD). Fix/Workaround Do not update the PWM_CUPD register with a value equal to 0. 41.4.2 ADC 1. Sleep Mode activation needs additional A to D conversion If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode before after the next AD conversion. Fix/Workaround Activate the sleep mode in the mode register and then perform an AD conversion. 41.4.3 SPI 1. SPI Slave / PDCA transfer: no TX UNDERRUN flag There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to be informed of a character lost in transmission. Fix/Workaround For PDCA transfer: none. 2. SPI FDIV option does not work Selecting clock signal using FDIV = 1 does not work as specified. Fix/Workaround Do not set FDIV = 1 3. SPI disable does not work in SLAVE mode. Fix/Workaround Read the last received data, then perform a Software Reset. 803 32058H–AVR32–03/09 AT32UC3A 4. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and NCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn't equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK. Fix/workaround When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if CPOL=1 and CPHA=0. 5. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first transfer In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or during the first transfer. Fix/Workaround 1. Set slave mode, set required CPOL/CPHA. 2. Enable SPI. 3. Set the polarity CPOL of the line in the opposite value of the required one. 4. Set the polarity CPOL to the required one. 5. Read the RXHOLDING register. Transfers can now befin and RXREADY will now behave as expected. 6. SPI Disable does not work in Slave mode Fix/workaround Read the last received data then perform a Software reset. Power Manager 1. Wrong reset causes when BOD is activated Setting the BOD enable fuse will cause the Reset Cause Register to list BOD reset as the reset source even though the part was reset by another source. Fix/Workaround Do not set the BOD enable fuse, but activate the BOD as soon as your program starts. 2. If the BOD level is higher than VDDCORE, the part is constantly under reset If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will be in constant reset. Fix/Workaround Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than VDDCORE max and disable the BOD. 41.4.5 FLASHC 1. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP, EP, EA, WUP, EUP commands may happen - After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the other half of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, reading 41.4.4 804 32058H–AVR32–03/09 AT32UC3A (data read or code fetch) the second half (last 256 kB) of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. Fix/Workaround Flashc WP, EP, EA, WUP, EUP commands: these commands must be issued from RAM or through the EBI. After these commands, read twice one flash page initialized to 00h in each half part of the flash. 41.4.6 PDCA 1. Wrong PDCA behavior when using two PDCA channels with the same PID. Workaround/fix The same PID should not be assigned to more than one channel. 41.4.7 TWI 1. The TWI RXRDY flag in SR register is not reset when a software reset is performed. Fix/Workaround After a Software Reset, the register TWI RHR must be read. 41.4.8 SDRAMC 1. Code execution from external SDRAM does not work Code execution from SDRAM does not work. Fix/Workaround Do not run code from SDRAM. 41.4.9 GPIO 1. Some GPIO VIH (input high voltage) are 3.6V max instead of 5V tolerant Only 11 GPIOs remain 5V tolerant (VIHmax=5V):PB01, PB02, PB03, PB10, PB19, PB20, PB21, PB22, PB23, PB27, PB28. Workaround/fix None. 41.4.10 USART 1. ISO7816 info register US_NER cannot be read The NER register always returns zero. Fix/Workaround None. Processor and Architecture 1. LDM instruction with PC in the register list and without ++ increments Rp For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the increment of the pointer is done in parallel with the testing of R12. Fix/Workaround None. 41.4.11 2. RETE instruction does not clear SREG[L] from interrupts. The RETE instruction clears SREG[L] as expected from exceptions. Fix/Workaround When using the STCOND instruction, clear SREG[L] in the stacked value of SR before returning from interrupts with RETE. 3. Exceptions when system stack is protected by MPU 805 32058H–AVR32–03/09 AT32UC3A RETS behaves incorrectly when MPU is enabled and MPU is configured so that system stack is not readable in unprivileged mode. Fix/Woraround Workaround 1: Make system stack readable in unprivileged mode, or Workaround 2: Return from supervisor mode using rete instead of rets. This requires : 1. Changing the mode bits from 001b to 110b before issuing the instruction. Updating the mode bits to the desired value must be done using a single mtsr instruction so it is done atomically. Even if this step is described in general as not safe in the UC technical reference guide, it is safe in this very specific case. 2. Execute the RETE instruction. 806 32058H–AVR32–03/09 AT32UC3A 41.5 41.5.1 Rev. E SPI 1. SPI FDIV option does not work Selecting clock signal using FDIV = 1 does not work as specified. Fix/Workaround Do not set FDIV = 1. 2. SPI Slave / PDCA transfer: no TX UNDERRUN flag There is no TX UNDERRUN flag available, therefore in SPI slave mode, there is no way to be informed of a character lost in transmission. Fix/Workaround For PDCA transfer: none. 3. SPI Bad serial clock generation on 2nd chip select when SCBR=1, CPOL=1 and CNCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn’t equal to 1, and CPOL=1 and CPHA=0, then an additional pulse will be generated on SCK. Fix/Workaround When multiple CS are in use, if one of the baudrate equals to 1, the other must also equal 1 if CPOL=1 and CPHA=0. 4. SPI Glitch on RXREADY flag in slave mode when enabling the SPI or during the first transfer In slave mode, the SPI can generate a false RXREADY signal during enabling of the SPI or during the first transfer. Fix/Workaround 1. Set slave mode, set required CPOL/CPHA. 2. Enable SPI. 3. Set the polarity CPOL of the line in the opposite value of the required one. 4. Set the polarity CPOL to the required one. 5. Read the RXHOLDING register. Transfers can now befin and RXREADY will now behave as expected. 5. SPI CSNAAT bit 2 in register CSR0...CSR3 is not available. Fix/Workaround Do not use this bit. 6. SPI disable does not work in SLAVE mode. Fix/Workaround Read the last received data, then perform a Software Reset. 7. SPI Bad Serial Clock Generation on 2nd chip_select when SCBR = 1, CPOL=1 and NCPHA=0 When multiple CS are in use, if one of the baudrate equals to 1 and one of the others doesn't equal to 1, and CPOL=1 and CPHA=0, then an aditional pulse will be generated on SCK. 807 32058H–AVR32–03/09 AT32UC3A Fix/workaround When multiple CS are in use, if one of the baudrate equals 1, the other must also equal 1 if CPOL=1 and CPHA=0. 41.5.2 PWM 1. PWM counter restarts at 0x0001 The PWM counter restarts at 0x0001 and not 0x0000 as specified. Because of this the first PWM period has one more clock cycle. Fix/Workaround - The first period is 0x0000, 0x0001, ..., period - Consecutive periods are 0x0001, 0x0002, ..., period 2. PWM channel interrupt enabling triggers an interrupt When enabling a PWM channel that is configured with center aligned period (CALG=1), an interrupt is signalled. Fix/Workaround When using center aligned mode, enable the channel and read the status before channel interrupt is enabled. 3. PWM update period to a 0 value does not work It is impossible to update a period equal to 0 by the using the PWM update register (PWM_CUPD). Fix/Workaround Do not update the PWM_CUPD register with a value equal to 0. 4. PWM channel status may be wrong if disabled before a period has elapsed Before a PWM period has elapsed, the read channel status may be wrong. The CHIDx-bit for a PWM channel in the PWM Enable Register will read '1' for one full PWM period even if the channel was disabled before the period elapsed. It will then read '0' as expected. Fix/Workaround Reading the PWM channel status of a disabled channel is only correct after a PWM period has elapsed. 41.5.3 SSC 1. SSC does not trigger RF when data is low The SSC cannot transmit or receive data when CKS = CKDIV and CKO = none, in TCMR or RCMR respectively. Fix/Workaround Set CKO to a value that is not "none" and bypass the output of the TK/RK pin with the PIO. 2. SSC Data is not sent unless clock is set as output The SSC cannot transmit or receive data when CKS = CKDIV and CKO = none, in TCMR or RCMR respectively. Fix/Workaround Set CKO to a value that is not "none" and bypass the output of the TK/RK pin with the PIO. 808 32058H–AVR32–03/09 AT32UC3A 41.5.4 USB 1. USB No end of host reset signaled upon disconnection In host mode, in case of an unexpected device disconnection whereas a usb reset is being sent by the usb controller, the UHCON.RESET bit may not been cleared by the hardware at the end of the reset. Fix/Workaround A software workaround consists in testing (by polling or interrupt) the disconnection (UHINT.DDISCI == 1) while waiting for the end of reset (UHCON.RESET == 0) to avoid being stuck. 2. USBFSM and UHADDR1/2/3 registers are not available. Do not use USBFSM register. Fix/Workaround Do not use USBFSM register and use HCON[6:0] field instead for all the pipes. 41.5.5 Processor and Architecture 1. Incorrect Processor ID The processor ID reads 0x01 and not 0x02 as it should. Fix/Workaround None. 2. Bus error should be masked in Debug mode If a bus error occurs during debug mode, the processor will not respond to debug commands through the DINST register. Fix/Workaround A reset of the device will make the CPU respond to debug commands again. 3. Read Modify Write (RMW) instructions on data outside the internal RAM does not work. Read Modify Write (RMW) instructions on data outside the internal RAM does not work. Fix/Workaround Do not perform RMW instructions on data outside the internal RAM. 4. CRC calculation of a locked device will calculate CRC for 512 kB of flash memory, even though the part has less flash. Fix/Workaround The flash address space is wrapping, so it is possible to use the CRC value by calculating CRC of the flash content concatenated with itself N times. Where N is 512 kB/flash size. Need two NOPs instruction after instructions masking interrupts The instructions following in the pipeline the instruction masking the interrupt through SR may behave abnormally. Fix/Workaround Place two NOPs instructions after each SSRF or MTSR instruction setting IxM or GM in SR. 5. 809 32058H–AVR32–03/09 AT32UC3A 6. CPU Cycle Counter does not reset the COUNT system register on COMPARE match. The device revision E does not reset the COUNT system register on COMPARE match. In this revision, the COUNT register is clocked by the CPU clock, so when the CPU clock stops, so does incrementing of COUNT. Fix/Workaround None. 7. Memory Protection Unit (MPU) is non functional. Fix/Workaround Do not use the MPU. 8. The following alternate GPIO function C are not available in revE MACB-WOL on GPIO9 (PA09), MACB-WOL on GPIO18 (PA18), USB-USB_ID on GPIO21 (PA21), USB-USB_VBOF on GPIO22 (PA22), and all function B and C on GPIO70 to GPIO101 (PX00 to PX39). Fix/Workaround Do not use these alternate B and C functions on the listed GPIO pins. 9. Clock connection table on Rev E Here is the table of Rev E Figure 41-1. Timer/Counter clock connections on RevE Source Internal Name TIMER_CLOCK1 TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 TIMER_CLOCK5 External XC0 XC1 XC2 Connection 32 KHz Oscillator PBA Clock / 4 PBA Clock / 8 PBA Clock / 16 PBA Clock / 32 10. Local Bus fast GPIO not available in RevE. Fix/Workaround Do not use on this silicon revision. 11. Spurious interrupt may corrupt core SR mode to exception If the rules listed in the chapter `Masking interrupt requests in peripheral modules' of the AVR32UC Technical Reference Manual are not followed, a spurious interrupt may occur. An interrupt context will be pushed onto the stack while the core SR mode will indicate an exception. A RETE instruction would then corrupt the stack.. Fix/Workaround Follow the rules of the AVR32UC Technical Reference Manual. To increase software robustness, if an exception mode is detected at the beginning of an interrupt handler, change the stack interrupt context to an exception context and issue a RETE instruction. 810 32058H–AVR32–03/09 AT32UC3A 12. CPU cannot operate on a divided slow clock (internal RC oscillator) Fix/Workaround Do not run the CPU on a divided slow clock. 13. LDM instruction with PC in the register list and without ++ increments Rp For LDM with PC in the register list: the instruction behaves as if the ++ field is always set, ie the pointer is always updated. This happens even if the ++ field is cleared. Specifically, the increment of the pointer is done in parallel with the testing of R12. Fix/Workaround None. 14. RETE instruction does not clear SREG[L] from interrupts. The RETE instruction clears SREG[L] as expected from exceptions. Fix/Workaround When using the STCOND instruction, clear SREG[L] in the stacked value of SR before returning from interrupts with RETE. 15. Exceptions when system stack is protected by MPU RETS behaves incorrectly when MPU is enabled and MPU is configured so that system stack is not readable in unprivileged mode. Fix/Woraround Workaround 1: Make system stack readable in unprivileged mode, or Workaround 2: Return from supervisor mode using rete instead of rets. This requires : 1. Changing the mode bits from 001b to 110b before issuing the instruction. Updating the mode bits to the desired value must be done using a single mtsr instruction so it is done atomically. Even if this step is described in general as not safe in the UC technical reference guide, it is safe in this very specific case. 2. Execute the RETE instruction. 41.5.6 SDRAMC 1. Code execution from external SDRAM does not work Code execution from SDRAM does not work. Fix/Workaround Do not run code from SDRAM. 2. SDRAM SDCKE rise at the same time as SDCK while exiting self-refresh mode SDCKE rise at the same time as SDCK while exiting self-refresh mode. Fix/Workaround None. 41.5.7 USART 1. USART Manchester Encoder Not Working Manchester encoding/decoding is not working. Fix/Workaround Do not use manchester encoding. 811 32058H–AVR32–03/09 AT32UC3A 2. USART RXBREAK problem when no timeguard In asynchronous mode the RXBREAK flag is not correctly handled when the timeguard is 0 and the break character is located just after the stop bit. Fix/Workaround If the NBSTOP is 1, timeguard should be different from 0. 3. USART Handshaking: 2 characters sent / CTS rises when TX If CTS switches from 0 to 1 during the TX of a character, if the Holding register is not empty, the TXHOLDING is also transmitted. Fix/Workaround None. 4. USART PDC and TIMEGUARD not supported in MANCHESTER Manchester encoding/decoding is not working. Fix/Workaround Do not use manchester encoding. 5. USART SPI mode is non functional on this revision. Fix/Workaround Do not use the USART SPI mode. 6. DCD is active High instead of Low. In modem mode the DCD signal is assumed to be active high by the USART, butshould have been active low. Fix/Workaround Add an external inverter to the DCD line. 7. ISO7816 info register US_NER cannot be read The NER register always returns zero. Fix/Workaround None. Power Manager 1. Voltage regulator input and output is connected to VDDIO and VDDCORE inside the device The voltage regulator input and output is connected to VDDIO and VDDCORE respectively inside the device. Fix/Workaround Do not supply VDDCORE externally, as this supply will work in paralell with the regulator. 2. Wrong reset causes when BOD is activated Setting the BOD enable fuse will cause the Reset Cause Register to list BOD reset as the reset source even though the part was reset by another source. Fix/Workaround Do not set the BOD enable fuse, but activate the BOD as soon as your program starts. 3. PLL0/1 Lock control does not work Lock Control does not work for PLL0 and PLL1. 812 32058H–AVR32–03/09 41.5.8 AT32UC3A Fix/Workaround In PLL0/1 Control register, the bit 7 should be set in order to prevent unexpected behaviour. 4. Peripheral Bus A maximum frequency is 33MHz instead of 66MHz. Fix/Workaround Do not set PBA frequency higher than 33 MHz. 5. PCx pins go low in stop mode In sleep mode stop all PCx pins will be controlled by GPIO module instead of oscillators. This can cause drive contention on the XINx in worst case. Fix/Workaround Before entering stop mode set all PCx pins to input and GPIO controlled. 6. On some rare parts, the maximum HSB and CPU speed is 50MHz instead of 66MHz. Fix/Workaround Do not set the HSB/CPU speed higher than 50MHz when the firmware generate exceptions. 7. If the BOD level is higher than VDDCORE, the part is constantly under reset If the BOD level is set to a value higher than VDDCORE and enabled by fuses, the part will be in constant reset. Fix/Workaround Apply an external voltage on VDDCORE that is higher than the BOD level and is lower than VDDCORE max and disable the BOD. 8. System Timer mask (Bit 16) of the PM CPUMASK register is not available. Fix/Workaround Do not use this bit. 41.5.9 HMatrix 1. HMatrix fixed priority arbitration does not work Fixed priority arbitration does not work. Fix/Workaround Use Round-Robin arbitration instead. 41.5.10 ADC 1. ADC possible miss on DRDY when disabling a channel The ADC does not work properly when more than one channel is enabled. Fix/Workaround Do not use the ADC with more than one channel enabled at a time. 2. ADC OVRE flag sometimes not reset on Status Register read The OVRE flag does not clear properly if read simultaneously to an end of conversion. Fix/Workaround None. 3. Sleep Mode activation needs additional A to D conversion 813 32058H–AVR32–03/09 AT32UC3A If the ADC sleep mode is activated when the ADC is idle the ADC will not enter sleep mode before after the next AD conversion. Fix/Workaround Activate the sleep mode in the mode register and then perform an AD conversion. 41.5.11 ABDAC 1. Audio Bitstream DAC is not functional. Fix/Workaround Do not use the ABDAC on revE. 41.5.12 FLASHC 1. The address of Flash General Purpose Fuse Register Low (FGPFRLO) is 0xFFFE140C on revE instead of 0xFFFE1410. Fix/Workaround None. 2. The command Quick Page Read User Page(QPRUP) is not functional. Fix/Workaround None. 3. PAGEN Semantic Field for Program GP Fuse Byte is WriteData[7:0], ByteAddress[1:0] on revision E instead of WriteData[7:0], ByteAddress[2:0]. Fix/Workaround None. 4. On AT32UC3A0512 and AT32UC3A1512, corrupted read in flash after FLASHC WP, EP, EA, WUP, EUP commands may happen - After a FLASHC Write Page (WP) or Erase Page (EP) command applied to a page in a given half of the flash (first or last 256 kB of flash), reading (data read or code fetch) the other half of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Erase All (EA) command, reading (data read or code fetch) the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. - After a FLASHC Write User Page (WUP) or Erase User Page (EUP) command, reading (data read or code fetch) the second half (last 256 kB) of the flash may fail. This may lead to an exception or to other errors derived from this corrupted read access. Fix/Workaround Flashc WP, EP, EA, WUP, EUP commands: these commands must be issued from RAM or through the EBI. After these commands, read twice one flash page initialized to 00h in each half part of the flash. 41.5.13 RTC 1. Writes to control (CTRL), top (TOP) and value (VAL) in the RTC are discarded if the RTC peripheral bus clock (PBA) is divided by a factor of four or more relative to the HSB clock. Fix/Workaround Do not write to the RTC registers using the peripheral bus clock (PBA) divided by a factor of four or more relative to the HSB clock. 814 32058H–AVR32–03/09 AT32UC3A 2. The RTC CLKEN bit (bit number 16) of CTRL register is not available. Fix/Workaround Do not use the CLKEN bit of the RTC on Rev E. 41.5.14 OCD 1. Stalled memory access instruction writeback fails if followed by a HW breakpoint. Consider the following assembly code sequence: A B If a hardware breakpoint is placed on instruction B, and instruction A is a memory access instruction, register file updates from instruction A can be discarded. Fix/Workaround Do not place hardware breakpoints, use software breakpoints instead. Alternatively, place a hardware breakpoint on the instruction before the memory access instruction and then single step over the memory access instruction. 41.5.15 PDCA 1. Wrong PDCA behavior when using two PDCA channels with the same PID. Workaround/fix The same PID should not be assigned to more than one channel. 41.5.16 TWI 1. The TWI RXRDY flag in SR register is not reset when a software reset is performed. Fix/Workaround After a Software Reset, the register TWI RHR must be read. 815 32058H–AVR32–03/09 AT32UC3A 42. 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. 42.1 Rev. H – 03/09 1. 2. 2. Update ”Errata” on page 793. Update eletrical characteristic in ”DC Characteristics” on page 764. Add BGA144 package information. 42.2 Rev. G – 01/09 1. 2. Update ”Errata” on page 793. Update GPIO eletrical characteristic in ”DC Characteristics” on page 764. 42.3 Rev. F – 08/08 1. 2. Add revision J to ”Errata” on page 793. Update DMIPS number in ”Features” on page 1. 42.4 Rev. E – 04/08 1. Open Drain Mode removed from ”General-Purpose Input/Output Controller (GPIO)” on page 151. 42.5 Rev. D – 04/08 1. 2. Updated ”Signal Description List” on page 8. Removed RXDN and TXDN from USART section. Updated ”Errata” on page 793. Rev G replaced by rev H. 816 32058H–AVR32–03/09 AT32UC3A 42.6 Rev. C – 10/07 1. 2. Updated ”Signal Description List” on page 8. Removed RXDN and TXDN from USART section. Updated ”Errata” on page 793. Rev G replaced by rev H. 42.7 Rev. B – 10/07 1. 2. 3. 4. 5. 6. 7. Updated ”Features” on page 1. Update ”Blockdiagram” on page 4 with local bus. Updated ”Peripherals” on page 34 with local bus. Add SPI feature in ”Universial Synchronous/Asynchronous Receiver/Transmitter (USART)” on page 315. Updated ”USB On-The-Go Interface (USBB)” on page 517. Updated ”JTAG and Boundary Scan” on page 750 with programming procedure . Add description for silicon Rev G. 42.8 Rev. A – 03/07 1. Initial revision. 817 32058H–AVR32–03/09 AT32UC3A Table of Contents 1 2 3 4 Description ............................................................................................... 3 Configuration Summary .......................................................................... 4 Abbreviations ........................................................................................... 4 Blockdiagram ........................................................................................... 5 4.1Processor and architecture ........................................................................................6 5 6 Signals Description .................................................................................. 8 Power Considerations ........................................................................... 13 6.1Power Supplies ........................................................................................................13 6.2Voltage Regulator ....................................................................................................14 6.3Analog-to-Digital Converter (A.D.C) reference. .......................................................15 7 8 Package and Pinout ............................................................................... 16 I/O Line Considerations ......................................................................... 20 8.1JTAG pins ................................................................................................................20 8.2RESET_N pin ..........................................................................................................20 8.3TWI pins ..................................................................................................................20 8.4GPIO pins ................................................................................................................20 9 Processor and Architecture .................................................................. 21 9.1AVR32 Architecture .................................................................................................21 9.2The AVR32UC CPU ................................................................................................21 9.3Programming Model ................................................................................................25 9.4Exceptions and Interrupts ........................................................................................29 10 Memories ................................................................................................ 33 10.1Embedded Memories ............................................................................................33 10.2Physical Memory Map ...........................................................................................33 10.3Bus Matrix Connections .........................................................................................34 11 Fuses Settings ........................................................................................ 36 11.1Flash General Purpose Fuse Register (FGPFRLO) ..............................................36 11.2Default Fuse Value ................................................................................................37 12 Peripherals .............................................................................................. 38 12.1Peripheral address map ........................................................................................38 12.2CPU Local Bus Mapping .......................................................................................39 i 32058H–AVR32–03/09 AT32UC3A 12.3Interrupt Request Signal Map ................................................................................41 12.4Clock Connections .................................................................................................43 12.5Nexus OCD AUX port connections ........................................................................44 12.6PDC handshake signals ........................................................................................44 12.7Peripheral Multiplexing on I/O lines .......................................................................45 12.8Oscillator Pinout ....................................................................................................48 12.9USART Configuration ............................................................................................48 12.10GPIO ....................................................................................................................49 12.11Peripheral overview .............................................................................................49 13 Power Manager (PM) .............................................................................. 53 13.1Features ................................................................................................................53 13.2Description .............................................................................................................53 13.3Block Diagram .......................................................................................................54 13.4Product Dependencies ..........................................................................................55 13.5Functional Description ...........................................................................................55 13.6User Interface ........................................................................................................66 14 Real Time Counter (RTC) ....................................................................... 86 14.1Features ................................................................................................................86 14.2Description .............................................................................................................86 14.3Block Diagram .......................................................................................................87 14.4Product Dependencies ..........................................................................................87 14.5Functional Description ...........................................................................................87 14.6User Interface ........................................................................................................89 15 Watchdog Timer (WDT) ......................................................................... 94 15.1Features ................................................................................................................94 15.2Description .............................................................................................................94 15.3Block Diagram .......................................................................................................94 15.4Product Dependencies ..........................................................................................94 15.5Functional Description ...........................................................................................95 15.6User Interface ........................................................................................................96 16 Interrupt Controller (INTC) .................................................................... 99 16.1Description .............................................................................................................99 16.2Block Diagram .......................................................................................................99 16.3Operation ...............................................................................................................99 16.4User Interface ......................................................................................................101 ii 32058H–AVR32–03/09 AT32UC3A 17 External Interrupts Controller (EIC) .................................................... 105 17.1Features ..............................................................................................................105 17.2Description ...........................................................................................................105 17.3Block Diagram .....................................................................................................106 17.4Product Dependencies ........................................................................................106 17.5Functional Description .........................................................................................107 17.6User Interface ......................................................................................................109 18 Flash Controller (FLASHC) .................................................................. 115 18.1Features ..............................................................................................................115 18.2Description ...........................................................................................................115 18.3Product dependencies .........................................................................................115 18.4Functional description ..........................................................................................116 18.5Flash commands .................................................................................................118 18.6General-purpose fuse bits ...................................................................................120 18.7Security bit ...........................................................................................................122 18.8User interface ......................................................................................................123 19 HSB Bus Matrix (HMATRIX) ................................................................ 132 19.1Features ..............................................................................................................132 19.2Description ...........................................................................................................132 19.3Memory Mapping .................................................................................................132 19.4Special Bus Granting Mechanism .......................................................................132 19.5Arbitration ............................................................................................................133 19.6Slave and Master assignation .............................................................................135 19.7User Interface ......................................................................................................136 20 External Bus Interface (EBI) ................................................................ 145 20.1Features ..............................................................................................................145 20.2Description ...........................................................................................................145 20.3Block Diagram .....................................................................................................146 20.4I/O Lines Description ...........................................................................................147 20.5Application Example ............................................................................................148 20.6Product Dependencies ........................................................................................151 20.7Functional Description .........................................................................................151 21 Peripheral DMA Controller (PDCA) ..................................................... 153 21.1Features ..............................................................................................................153 21.2Overview ..............................................................................................................153 iii 32058H–AVR32–03/09 AT32UC3A 21.3Block Diagram .....................................................................................................154 21.4Functional Description .........................................................................................154 21.5User Interface ......................................................................................................156 22 General-Purpose Input/Output Controller (GPIO) ............................. 170 22.1Features ..............................................................................................................170 22.2Overview ..............................................................................................................170 22.3Product dependencies .........................................................................................170 22.4Functional Description .........................................................................................171 22.5General Purpose Input/Output (GPIO) User Interface .........................................175 22.6Programming Examples ......................................................................................189 23 Serial Peripheral Interface (SPI) .......................................................... 191 23.1Features ..............................................................................................................191 23.2Description ...........................................................................................................191 23.3Block Diagram .....................................................................................................192 23.4Application Block Diagram ...................................................................................193 23.5Signal Description ................................................................................................194 23.6Product Dependencies ........................................................................................195 23.7Functional Description .........................................................................................196 23.8Serial Peripheral Interface (SPI) User Interface ..................................................206 24 Two-Wire Interface (TWI) ..................................................................... 220 24.1Features ..............................................................................................................220 24.2Overview ..............................................................................................................220 24.3List of Abbreviations ............................................................................................221 24.4Block Diagram .....................................................................................................221 24.5Application Block Diagram ...................................................................................222 24.6I/O Lines Description ...........................................................................................222 24.7Product Dependencies ........................................................................................222 24.8Functional Description .........................................................................................223 24.9Modes of Operation .............................................................................................223 24.10Master Mode ......................................................................................................224 24.11 Internal Address Usage Using the Peripheral DMA Controller (PDC) ..............228 24.12Multi-master Mode .............................................................................................235 24.13Slave Mode ........................................................................................................238 24.14Two-wire Interface (TWI) User Interface ...........................................................246 25 Synchronous Serial Controller (SSC) ................................................ 259 iv 32058H–AVR32–03/09 AT32UC3A 25.1Features ..............................................................................................................259 25.2Overview ..............................................................................................................259 25.3Block Diagram .....................................................................................................260 25.4Application Block Diagram ...................................................................................260 25.5I/O Lines Description ...........................................................................................261 25.6Product Dependencies ........................................................................................261 25.7Functional Description .........................................................................................261 25.8SSC Application Examples ..................................................................................273 25.9User Interface ......................................................................................................275 26 Universal Synchronous/Asynchronous Receiver/Transmitter (USART) 299 26.1Features ..............................................................................................................299 26.2Overview ..............................................................................................................299 26.3Block Diagram .....................................................................................................300 26.4Application Block Diagram ...................................................................................301 26.5I/O Lines Description ..........................................................................................302 26.6Product Dependencies ........................................................................................303 26.7Functional Description .........................................................................................304 26.8Universal Synchronous/Asynchronous Receiver/Transmitter (USART) User Interface 339 27 Static Memory Controller (SMC) ......................................................... 366 27.1Features ..............................................................................................................366 27.2Overview ..............................................................................................................366 27.3Block Diagram .....................................................................................................367 27.4I/O Lines Description ...........................................................................................367 27.5Product Dependencies ........................................................................................368 27.6Functionnal Description .......................................................................................368 27.7User Interface ......................................................................................................403 28 SDRAM Controller (SDRAMC) ............................................................. 410 28.1Features ..............................................................................................................410 28.2Description ...........................................................................................................410 28.3Block Diagram .....................................................................................................411 28.4I/O Lines Description ...........................................................................................411 28.5Application Example ............................................................................................412 28.6Product Dependencies ........................................................................................415 28.7Functional Description .........................................................................................417 28.8SDRAM Controller User Interface .......................................................................424 v 32058H–AVR32–03/09 AT32UC3A 29 Ethernet MAC (MACB) ......................................................................... 437 29.1Features ..............................................................................................................437 29.2Description ...........................................................................................................437 29.3Block Diagram .....................................................................................................438 29.4Product Dependencies ........................................................................................438 29.5Functional Description .........................................................................................439 29.6Programming Interface ........................................................................................451 29.7Ethernet MAC (MACB) User Interface .................................................................454 30 USB On-The-Go Interface (USBB) ...................................................... 497 30.1Features ..............................................................................................................497 30.2Description ...........................................................................................................497 30.3Block Diagram .....................................................................................................499 30.4Application Block Diagram ...................................................................................500 30.5I/O Lines Description ...........................................................................................501 30.6Product Dependencies ........................................................................................502 30.7Functional Description .........................................................................................503 30.8USB User Interface ..............................................................................................530 31 Timer/Counter (TC) .............................................................................. 639 31.1Features ..............................................................................................................639 31.2Description ...........................................................................................................639 31.3Block Diagram .....................................................................................................640 31.4Pin Name List ......................................................................................................641 31.5Product Dependencies ........................................................................................641 31.6Functional Description .........................................................................................641 31.7Timer Counter (TC) User Interface ......................................................................654 32 Pulse Width Modulation Controller (PWM) ........................................ 673 32.1Features ..............................................................................................................673 32.2Description ...........................................................................................................673 32.3Block Diagram .....................................................................................................674 32.4I/O Lines Description ...........................................................................................674 32.5Product Dependencies ........................................................................................675 32.6Functional Description .........................................................................................676 32.7Pulse Width Modulation (PWM) Controller User Interface ..................................684 33 Analog-to-Digital Converter (ADC) ..................................................... 699 33.1Features ..............................................................................................................699 vi 32058H–AVR32–03/09 AT32UC3A 33.2Overview ..............................................................................................................699 33.3Block Diagram .....................................................................................................700 33.4I/O Lines Description ...........................................................................................700 33.5Product Dependencies ........................................................................................700 33.6Functional Description .........................................................................................702 33.7User Interface ......................................................................................................707 34 Audio Bitstream DAC (ABDAC) .......................................................... 721 34.1Features ..............................................................................................................721 34.2Description ...........................................................................................................721 34.3Block Diagram .....................................................................................................722 34.4Pin Name List ......................................................................................................722 34.5Product Dependencies ........................................................................................722 34.6Functional Description .........................................................................................723 34.7Audio Bitstream DAC User Interface ...................................................................725 34.8Frequency Response ..........................................................................................733 35 On-Chip Debug ..................................................................................... 734 35.1Features ..............................................................................................................734 35.2Overview ..............................................................................................................734 35.3Block diagram ......................................................................................................735 35.4Functional description ..........................................................................................735 36 JTAG and Boundary Scan ................................................................... 741 36.1Features ..............................................................................................................741 36.2Overview ..............................................................................................................741 36.3Block diagram ......................................................................................................742 36.4I/O Lines Description ...........................................................................................743 36.5Product Dependencies ........................................................................................743 36.6Functional description ..........................................................................................743 36.7JTAG Instruction Summary .................................................................................748 36.8Public JTAG instructions .....................................................................................749 36.9Private JTAG Instructions ....................................................................................750 36.10JTAG Data Registers .........................................................................................760 36.11SAB address map ..............................................................................................761 37 Boot Sequence ..................................................................................... 762 37.1Starting of clocks .................................................................................................762 37.2Fetching of initial instructions ..............................................................................762 vii 32058H–AVR32–03/09 AT32UC3A 38 Electrical Characteristics .................................................................... 763 38.1Absolute Maximum Ratings* ...............................................................................763 38.2DC Characteristics ...............................................................................................764 38.3Regulator characteristics .....................................................................................765 38.4Analog characteristics .........................................................................................765 38.5Power Consumption ............................................................................................767 38.6Clock Characteristics ...........................................................................................769 38.7Crystal Oscillator Characteristis ..........................................................................770 38.8ADC Characteristics ............................................................................................772 38.9EBI Timings .........................................................................................................774 38.10JTAG Timings ....................................................................................................780 38.11SPI Characteristics ............................................................................................781 38.12MACB Characteristics .......................................................................................783 38.13Flash Characteristics .........................................................................................785 39 Mechanical Characteristics ................................................................. 787 39.1Thermal Considerations ......................................................................................787 39.2Package Drawings ...............................................................................................788 39.3Soldering Profile ..................................................................................................791 40 Ordering Information ........................................................................... 792 40.1Automotive Quality Grade ...................................................................................792 41 Errata ..................................................................................................... 793 41.1Rev. K ..................................................................................................................793 41.2Rev. J ..................................................................................................................796 41.3Rev. I ...................................................................................................................799 41.4Rev. H ..................................................................................................................803 41.5Rev. E ..................................................................................................................807 42 Datasheet Revision History ................................................................. 816 42.1Rev. H – 03/09 .....................................................................................................816 42.2Rev. G – 01/09 ....................................................................................................816 42.3Rev. F – 08/08 .....................................................................................................816 42.4Rev. E – 04/08 .....................................................................................................816 42.5Rev. D – 04/08 .....................................................................................................816 42.6Rev. C – 10/07 .....................................................................................................817 42.7Rev. B – 10/07 .....................................................................................................817 42.8Rev. A – 03/07 .....................................................................................................817 viii 32058H–AVR32–03/09 Headquarters Atmel Corporation 2325 Orchard Parkway San Jose, CA 95131 USA Tel: 1(408) 441-0311 Fax: 1(408) 487-2600 International 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 Product Contact Web Site www.atmel.com Technical Support avr32@atmel.com Sales Contact www.atmel.com/contacts Literature Requests www.atmel.com/literature Disclaimer: T he 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 ®, logo and combinations thereof, AVR® and others are registered trademarks or trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others. 32058H–AVR32–03/09