ATSAMA5D28B-CU

32-BIT ARM-BASED MICROPROCESSORS SAMA5D2 Series SAMA5D21 /22 /23 /24 /26 /27 /28 Introduction The SAMA5D2 series is a high-performance, ultra-low-power ARM® Cortex®-A5 processor-based MPU running up to 500 MHz, with support for multiple memories such as DDR2, DDR3, DDR3L, LPDDR1, LPDDR2, LPDDR3, and QSPI Flash. The devices integrate powerful peripherals for connectivity and user interface applications, and offer advanced security functions (ARM TrustZone®, tamper detection, secure data storage, etc.), as well as high-performance cryptoprocessors AES, SHA and TRNG. The SAMA5D2 series is delivered with a free Linux distribution and bare metal C examples. Features • ARM Cortex-A5 core - ARMv7-A architecture - ARM TrustZone - NEON™ Media Processing Engine - Up to 500 MHz - ETM/ETB 8 Kbytes • Memory Architecture - Memory Management Unit - 32-Kbyte L1 data cache, 32-Kbyte L1 instruction cache - 128-Kbyte L2 cache configurable to be used as an internal SRAM - One 128-Kbyte scrambled internal SRAM - One 160-Kbyte internal ROM  64-Kbyte scrambled and maskable ROM embedding boot loader/ Secure boot loader  96-Kbyte unscrambled, unmaskable ROM for NAND Flash BCH ECC table - High-bandwidth scramblable 16-bit or 32-bit Double Data Rate (DDR) multiport dynamic RAM controller supporting up to 512 Mbyte 8-bank DDR2/DDR3 (DLL off only) / DDR3L (DLL off only) / LPDDR1/LPDDR2/ LPDDR3, including “on-the-fly” encryption/decryption path - 8-bit SLC/MLC NAND controller, with up to 32-bit Error Correcting Code (PMECC) • System running up to 166 MHz in typical conditions - Reset controller, shutdown controller, periodic interval timer, independent watchdog timer and secure Real-Time Clock (RTC) with clock calibration - One 600 to 1200 MHz PLL for the system and one 480 MHz PLL optimized for USB high speed - Digital fractional PLL for audio (11.2896 MHz and 12.288 MHz) - Internal low-power 12 MHz RC and 32 KHz typical RC - Selectable 32.768-Hz low-power oscillator and 8 to 24 MHz oscillator - 51 DMA Channels including two 16-channel 64-bit Central DMA Controllers - 64-bit Advanced Interrupt Controller (AIC) - 64-bit Secure Advanced Interrupt Controller (SAIC) - Three programmable external clock signals • Low-Power Modes - Ultra Low-power mode with fast wakeup capability - Low-power Backup mode with 5-Kbyte SRAM and SleepWalking™ features  Wakeup from up to nine wakeup pins, UART reception, analog comparison  Fast wakeup capability  2017 Microchip Technology Inc. DS60001476B-page 1 SAMA5D2 SERIES  Extended Backup mode with DDR in Self-Refresh mode • Peripherals - LCD TFT controller up to 1024x768, with four overlays, rotation, post-processing and alpha blending, 24-bit parallel RGB - ITU-R BT. 601/656/1120 Image Sensor Controller (ISC) supporting up to 5 M-pixel sensors with a parallel 12-bit interface for Raw Bayer, YCbCr, Monochrome and JPEG-compressed sensor interface - Two Synchronous Serial Controllers (SSC), two Inter-IC Sound Controllers (I2SC), and one Stereo Class D amplifier - One Peripheral Touch Controller (PTC) with up to 8 X-lines and 8 Y-lines (64-channel capacitive touch) - One Pulse Density Modulation Interface Controller (PDMIC) - One USB high-speed device port (UDPHS) and one USB high-speed host port or two USB high-speed host ports (UHPHS) - One USB high-speed host port with a High-Speed Inter-Chip (HSIC) interface - One 10/100 Ethernet MAC (GMAC)  Energy efficiency support (IEEE 802.3az standard)  Ethernet AVB support with IEEE802.1AS time stamping  IEEE802.1Qav credit-based traffic-shaping hardware support  IEEE1588 Precision Time Protocol (PTP) - Two high-speed memory card hosts:  SDMMC0: SD 3.0, eMMC 4.51, 8 bits  SDMMC1: SD 2.0, eMMC 4.41, 4 bits only - Two master/slave Serial Peripheral Interfaces (SPI) - Two Quad Serial Peripheral Interfaces (QSPI) - Five FLEXCOMs (USART, SPI and TWI) - Five UARTs - Two master CAN-FD (MCAN) controllers with SRAM-based mailboxes, and time- and event-triggered transmission - One Rx only UART in backup area (RXLP) - One analog comparator (ACC) in backup area - Two 2-wire interfaces (TWIHS) up to 400 Kbits/s supporting the I2C protocol and SMBUS (TWIHS) - Two 3-channel 32-bit Timer/Counters (TC), supporting basic PWM modes - One full-featured 4-channel 16-bit Pulse Width Modulation (PWM) controller - One 12-channel, 12-bit, Analog-to-Digital Converter (ADC) with Resistive TouchScreen capability • Safety - Zero-power Power-On Reset (POR) cells - Main crystal clock failure detector - Write-protected registers - Integrity Check Monitor (ICM) based on SHA256 - Memory Management Unit - Independent watchdog • Security - 5 Kbytes of internal scrambled SRAM:  1 Kbyte non-erasable on tamper detection  4 Kbytes erasable on tamper detection - 256 bits of scrambled and erasable registers - Up to eight tamper pins for static or dynamic intrusion detections - Environmental monitors on specific versions: temperature, voltage, frequency and active die shield(1) - Secure Boot Loader(2) - On-the-fly AES encryption/decryption on DDR and QSPI memories (AESB) - RTC including time-stamping on security intrusions - Programmable fuse box with 544 fuse bits (including JTAG protection and BMS) Note 1: For environmental monitors, refer to the document “SAMA5D23 and SAMA5D28 Environmental Monitors” (document no. 44036), available under Non-Disclosure Agreement (NDA). Contact a Microchip Sales Representative for details. 2: For secure boot strategies, refer to the document “SAMA5D2 Series Secure Boot Strategy” (document no. 44040), available under Non-Disclosure Agreement (NDA). Contact a Microchip Sales Representative for details. • Hardware cryptography - SHA (SHA1, SHA224, SHA256, SHA384, SHA512): compliant with FIPS PUB 180-2 - AES: 256-, 192-, 128-bit key algorithm, compliant with FIPS PUB 197 DS60001476B-page 2  2017 Microchip Technology Inc. SAMA5D2 SERIES - TDES: two-key or three-key algorithms, compliant with FIPS PUB 46-3 - True Random Number Generator (TRNG) compliant with NIST Special Publication 800-22 Test Suite and FIPS PUBs 140-2 and 140-3 • Up to 128 I/Os - Fully programmable through set/clear registers - Multiplexing of up to eight peripheral functions per I/O line - Each I/O line can be assigned to a peripheral or used as a general purpose I/O - The PIO controller features a synchronous output providing up to 32 bits of data output in one write operation • Packages - 289-ball LFBGA, 14 x 14 mm body, 0.8 mm pitch - 256-ball TFBGA, 8 x 8 mm body, 0.4 mm pitch - 196-ball TFBGA, 11 x 11 mm body, 0.75 mm pitch  2017 Microchip Technology Inc. DS60001476B-page 3 SAMA5D2 SERIES 1. Description The SAMA5D2 Series is a high-performance, power-efficient embedded MPU based on the ARM Cortex-A5 processor. It integrates the ARM NEON SIMD engine for accelerated multimedia and signal processing, a configurable 128-Kbyte L2 cache, a floating point unit for high-precision computing and reliable performance, as well as high data bandwidth architecture. The device features an advanced user interface and connectivity peripherals. Advanced security is provided by powerful cryptographic accelerators, by the ARM TrustZone technology securing access to memories and sensitive peripherals, and by several hardware features that safeguard memory content, authenticate software reliability, detect physical attacks and prevent information leakage during code execution. The SAMA5D2 features an internal multilayer bus architecture associated with 2 x 16 DMA channels and dedicated DMAs for the communication and interface peripherals required to ensure uninterrupted data transfers with minimal processor overhead. The device supports DDR2, DDR3, DDR3L, LPDDR1, LPDDR2, LPDDR3, and SLC/MLC NAND Flash memory up to 32-bit ECC. The comprehensive peripheral set includes an LCD TFT controller with overlays for hardware-accelerated image composition, an image sensor controller, audio support through I2S, SSC, a stereo Class D amplifier and a digital microphone. Connectivity peripherals include a 10/100 EMAC, USBs, CAN-FDs, FLEXCOMs, UARTs, SPIs and two QSPIs, SDIO/SD/e.MMCs, and TWIs/I2C. Protection of code and data is provided by automatic scrambling of memories and an Integrity Check Monitor (ICM) to detect any modification of the memory contents. The SAMA5D2 also supports execution of encrypted code (QSPI or one portion of the DDR) with an “onthe-fly” encryption-decryption process. With its secure design architecture, cryptographic acceleration engines, and secure boot loader, the SAMA5D2 is the ideal solution for point-of-sale (POS), IoT and industrial applications requiring anti-cloning, data protection and secure communication transfer. SAMA5D2 devices feature three software-selectable low-power modes: Idle, Ultra-low-power and Backup. In Idle mode, the processor is stopped while all other functions can be kept running. In Ultra-low-power-mode 0, the processor is stopped while all other functions are clocked at 512 Hz and interrupts or peripherals can be configured to wake up the system based on events, including partial asynchronous wakeup (SleepWalking). In Ultra-low-power mode 1, all clocks and functions are stopped but some peripherals can be configured to wake up the system based on events, including partial asynchronous wakeup (SleepWalking). In Backup mode, RTC and wakeup logic are active. The Backup mode can be extended to feature DDR in Self-refresh mode. SAMA5D2 devices also include an Event System that allows peripherals to receive, react to and send events in Active and Idle modes without processor intervention. DS60001476B-page 4  2017 Microchip Technology Inc. SAMA5D2 SERIES 2. Configuration Summary Table 2-1: SAMA5D2 Configuration Summary Feature SAMA5D21 SAMA5D22 SAMA5D23 SAMA5D24 SAMA5D26 SAMA5D27 Package TFBGA196 TFBGA256 LFBGA289 PIOs 72 105 128 DDR Bus 16-bit 16/32-bit SMC Up to 16-bit SRAM 128 Kbytes QSPI 2 LCD 24-bit RGB Camera Interface (ISC) 1 EMAC 1 PTC – 4 X-lines x 8 Y-lines CAN – 1 8 X-lines x 8 Y-lines – 8 X-lines x 8 Y-lines – 3 (2 Hosts/ 1 HSIC, or 1 Host/ 1 Device/ 1 HSIC) 2 2 (2 Hosts or 1 Host/ 1 Device) USB 2 (2 Hosts or 1 Host/1 Device) UART/SPI/I2C 9/6/6 10 / 7 / 7 SDIO/SD/MMC 1 2 I2S/SSC/ 3 (2 Hosts/1 HSIC or 1 Host/1 Device/1 HSIC) 2/2/1/1 Class D/PDM ADC Inputs 5 12 Timers 5 6 PWM 4 (PWM) + 5 (TC) 4 (PWM) + 6 (TC) Tamper Pins 6 AESB SAMA5D28 – Environmental Monitors, Die Shield – 2 8 Yes – Yes – Yes Yes For information on device pin compatibility, see Section 6.2 “Pinouts”.  2017 Microchip Technology Inc. DS60001476B-page 5 SAMA5D2 SERIES 3. Block Diagram Figure 3-1: SAMA5D2 Series Block Diagram PIO JTAG / SWD Key Digital In-Circuit Emulator Analog Memories, bridges L1 32-KB ICache Master Slave NEON FPU EBI L1 32-KB DCache MMU L2 Cache I/D 128 KB SRAM SHA 1/256/512 M S 160 KB ROM S S S 16-ch DMA0 AES 128/192/256 M AESB (Bridge to memory) M 16-ch DMA1 Scrambling M S S S S TWI0 2 x FLEXCOM (USART, SPI, TWI) PIO 3x UART HS Trans HS Trans HS USB Device TDES TRNG M CAN1 TWI1 3 x FLEXCOM (USART, SPI, TWI) 2x UART SPI1 SPI0 H32MX Peripheral Bridge 0 S S H32MX Peripheral Bridge 1 SSC0 PIO CAN0 DMA H64MX Peripheral Bridge M DMA M M HS Trans PC PB PA DMA M HS EHCI USB HOST HS HSIC S TrustZone Secured Multilayer Matrix DMA DMA ISC M DMA 4-layer LCDC NANDFlash Controller PMECC M 2x SDMMC Reduced Static Memory Controller (9 KB SRAM) DMA 2 x QSPI Scrambling S Scrambling 128 KB L2 or SRAM DDR2 DDR3 DDR3L LPDDR1 LPDDR2 LPDDR3 Controller PIO Cryptoprocessor Cortex-A5 Processor PIO ETM CoreSight ETB Security Module M S Trust Zone Scrambling PIO Backup Area SSC1 SHA1/256 ICM DMA PIO I2SC1 I2SC0 M Stereo CLASS D 6 x 32-bit Timers + PWM (TC) 12-ch 12-bit ADC (+ Resistive Touchscreen) 4-ch PWM S PTC EMAC 10/100 DMA PDMIC Audio PLL M PLL UTMI Crystal Oscillator (or external Clock in Bypass mode) PLLA Fuse Box (SFC) 12 MHz RC Osc. WDT Clock Control (PMC) System Controller Backup Area Shutdown and Wakeup Control (SHDWC) 32K Crystal Osc. (or external clock in Bypass mode) Reset Control (RSTC) PIO Note: POR RTC 64 kHz RC Osc. POR ACC Security Module 8 PIOBU 256-bit Backup Register Environmental Sensors Secure RAM RX UART Wakeup (RXLP) Refer to Section 38. “DMA Controller (XDMAC)” for peripheral connections to DMA. DS60001476B-page 6  2017 Microchip Technology Inc. SAMA5D2 SERIES 4. Signal Description Table 4-1 gives details on signal names classified by peripheral. Table 4-1: Signal Name Signal Description List Function Active Level Type Comments Input – – Output – – Input – – Clocks, Oscillators and PLLs XIN Main Oscillator Input XOUT Main Oscillator Output XIN32 Slow Clock Oscillator Input XOUT32 Slow Clock Oscillator Output Output – – CLK_AUDIO Audio Clock Output – – VBG Bias Voltage Reference for USB Analog – – Reset State: PCK 0–2 Programmable Clock Output Output - PIO Input - Internal Pull-up enabled – - Schmitt Trigger enabled Shutdown, Wakeup Logic SHDN Shutdown Control Output – – PIOBU 0–7 Tamper or Wakeup Inputs Input – – WKUP Wakeup Input Input – – TCK/SWCLK Test Clock/Serial Wire Clock Input – – TDI Test Data In Input – – TDO Test Data Out Output – – TMS/SWDIO Test Mode Select/Serial Wire Input/Output I/O – – JTAGSEL JTAG Selection Input – – NRST Microprocessor Reset Input – Low TST Test Mode Select Input – – NTRST Test Reset Signal Input – – Input – – Input – – ICE and JTAG Reset/Test Advanced Interrupt Controller - AIC IRQ External Interrupt Input Secured Advanced Interrupt Controller - SAIC FIQ Fast Interrupt Input PIO Controller PA0–PAxx Parallel IO Controller I/O – – PB0–PBxx Parallel IO Controller I/O – – PC0–PCxx Parallel IO Controller I/O – – PD0–PDxx Parallel IO Controller I/O – –  2017 Microchip Technology Inc. DS60001476B-page 7 SAMA5D2 SERIES Table 4-1: Signal Description List (Continued) Signal Name Function Type Active Level Comments External Bus Interface - EBI D[15:0] Data Bus A[25:0] Address Bus NWAIT External Wait Signal I/O – – Output – – Input – Low Static Memory Controller - HSMC NCS0–NCS3 Chip Select Lines Output – Low NWR0–NWR1 Write Signal Output – Low NRD Read Signal Output – Low NWE Write Enable Output – Low NBS0–NBS1 Byte Mask Signal Output – Low NANDOE NAND Flash Output Enable Output – Low NANDWE NAND Flash Write Enable Output – Low – DDR2/DDR3/LPDDR1/LPDDR2/LPDDR3 Controller DDR_CK, DDR_CLKN DDR Differential Clock Output – DDR_CKE DDR Clock Enable Output When Backup Self-refresh mode is used, should be tied to GND using 100 KΩ pull-down High DDR_CS DDR Controller Chip Select Output – Low DDR_BA[2:0] Bank Select Output – Low DDR_WE DDR Write Enable Output – Low DDR_RAS, DDR_CAS Row and Column Signal Output – Low DDR_A[13:0] DDR Address Bus Output – – DDR_D[31:0] DDR Data Bus I/O/-PD – – Differential Data Strobe I/O- PD – – DDR_DQM[3:0] Write Data Mask Output – – DDR_CAL DDR/LPDDR Calibration Input – – DDR_VREF DDR/LPDDR Reference Input – – DDR_RESETN DDR3 Active Low Asynchronous Reset When Backup Self-refresh mode is used, should be tied to VDDIODDR using 100 KΩ pull-up – Input – – I/O – – Input – – DDR_DQS[3:0], DDR_DQSN[3:0] Output Secure Data Memory Card - SDMMCx [1:0] SDMMCx_CD SDcard / e.MMC Card Detect SDMMCx_CMD SDcard / e.MMC Command line SDMMCx_WP SDcard Connector Write Protect Signal SDMMCx_RSTN e.MMC Reset Signal Output – – SDMMCx_1V8SEL SDcard Signal Voltage Selection Output – – DS60001476B-page 8  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 4-1: Signal Description List (Continued) Signal Name Function SDMMCx_CK SDcard / e.MMC Clock Signal SDMMCx_DAT[7:0] SDcard / e.MMC Data Lines Type Comments Active Level Output – – I/O – – Flexible Serial Communication Controller - FLEXCOMx [4:0] FLEXCOMx_IO0 FLEXCOMx Transmit Data I/O – – FLEXCOMx_IO1 FLEXCOMx Receive Data I/O – – FLEXCOMx_IO2 FLEXCOMx Serial Clock I/O – – FLEXCOMx_IO3 FLEXCOMx Clear To Send / Peripheral Chip Select I/O – – FLEXCOMx_IO4 FLEXCOMx Request To Send / Peripheral Chip Select Output – – Universal Asynchronous Receiver Transmitter - UARTx [4..0] UTXDx UARTx Transmit Data Output – – URXDx UARTx Receive Data Input – – Inter-IC Sound Controller - I2SCx [1..0] I2SCx_MCK Master Clock Output – – I2SCx_CK Serial Clock I/O – – 2 I2SCx_WS I S Word Select I/O – – I2SCx_DI0 Serial Data Input Input – – I2SCx_DO0 Serial Data Output Output – – Synchronous Serial Controller - SSCx [1..0] TDx SSC Transmit Data Output – – RDx SSC Receive Data Input – – TKx SSC Transmit Clock I/O – – RKx SSC Receive Clock I/O – – TFx SSC Transmit Frame Sync I/O – – RFx SSC Receive Frame Sync I/O – – Input – – Timer/Counter - TCx [1..0] TCLK[5..0] TC Channel y External Clock Input TIOA[5..0] TC Channel y I/O Line A I/O – – TIOB[5..0] TC Channel y I/O Line B I/O – – Quad IO SPI - QSPIx [1..0] QSPIx_SCK QSPI Serial Clock Output – – QSPIx_CS QSPI Chip Select Output – – QSPIx_IO[0..3] QSPI I/O QIO0 is QMOSI Master Out - Slave In QIO1 is QMISO Master In - Slave Out I/O – –  2017 Microchip Technology Inc. DS60001476B-page 9 SAMA5D2 SERIES Table 4-1: Signal Description List (Continued) Signal Name Function Type Comments Active Level Serial Peripheral Interface - SPIx [1..0] SPIx_MISO Master In Slave Out I/O – – SPIx_MOSI Master Out Slave In I/O – – SPIx_SPCK SPI Serial Clock I/O – – SPIx_NPCS0 SPI Peripheral Chip Select 0 I/O – Low SPIx_NPCS[3..1] SPI Peripheral Chip Select Output – Low Two-wire Interface - TWIx [1..0] TWDx Two-wire Serial Data I/O – – TWCKx Two-wire Serial Clock I/O – – Pulse Width Modulation Controller - PWM PWMH0–3 PWM Waveform Output High Output – – PWML0–3 PWM Waveform Output Low Output – – PWMFI0–1 PWM Fault Inputs Input – – PWMEXTRG1–2 PWM External Trigger Input – – USB Host High Speed Port - UHPHS HHSDPA USB Host Port A High Speed Data + Analog – – HHSDMA USB Host Port A High Speed Data - Analog – – HHSDPB USB Host Port B High Speed Data + Analog – – HHSDMB USB Host Port B High Speed Data - Analog – – USB Device High Speed Port - UDPHS DHSDP USB Device High Speed Data + Analog – – DHSDM USB Device High Speed Data - Analog – – USB High-Speed Inter-Chip Port - HSIC HHSTROBE USB High-Speed Inter-Chip Strobe I/O – – HHDATA USB High-Speed Inter-Chip Data I/O – – Ethernet 10/100 - GMAC GREFCK Reference Clock Input – – GTXCK Transmit Clock Input – – GRXCK Receive Clock Input – – GTXEN Transmit Enable Output – – GTX0–GTX3 Transmit Data Output – – GTXER Transmit Coding Error Output – – GRXDV Receive Data Valid Input – – GRX0–GRX3 Receive Data Input – – GRXER Receive Error Input – – GCRS Carrier Sense Input – – DS60001476B-page 10  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 4-1: Signal Description List (Continued) Active Level Signal Name Function Type Comments GCOL Collision Detected Input – – GMDC Management Data Clock Output – – GMDIO Management Data Input/Output I/O – – GTSUCOMP TSU timer comparison valid Output – – LCDDAT[23:0] LCD Data Bus Output – – LCDVSYNC LCD Vertical Synchronization Output – – LCDHSYNC LCD Horizontal Synchronization Output – – LCDPCK LCD Pixel Clock Output – – LCDDEN LCD Data Enable Output – – LCDPWM LCDPWM for Contrast Control Output – – LCDDISP LCD Display ON/OFF Output – – Analog – – Input – – Analog – – I/O – – LCD Controller - LCDC Touchscreen Analog-to-Digital Converter - ADC AD0–11 12 Analog Inputs ADTRG ADC Trigger ADVREF ADC Reference Secure Box Module - SBM PIOBU0–7 Tamper I/Os Image Sensor Controller - ISC ISC_D0–ISC_D11 Image Sensor Data Input – – ISC_HSYNC Image Sensor Horizontal Synchro Input – – ISC_VSYNC Image Sensor Vertical Synchro Input – – ISC_PCK Image Sensor Pixel clock Input – – ISC_MCK Image Sensor Main clock Output – – ISC_FIELD Field identification signal Input – – Audio Class Amplifier - CLASSD CLASSD_L0 CLASSD Left Output L0 Output – – CLASSD_L1 CLASSD Left Output L1 Output – – CLASSD_L2 CLASSD Left Output L2 Output – – CLASSD_L3 CLASSD Left Output L3 Output – – CLASSD_R0 CLASSD Right Output R0 Output – – CLASSD_R1 CLASSD Right Output R1 Output – – CLASSD_R2 CLASSD Right Output R2 Output – – CLASSD_R3 CLASSD Right Output R3 Output – –  2017 Microchip Technology Inc. DS60001476B-page 11 SAMA5D2 SERIES Table 4-1: Signal Description List (Continued) Signal Name Function Type Comments Active Level Control Area Network - CAN CANRXx CAN Receive Input – – CANTXx CAN Transmit Output – – Peripheral Touch Controller (PTC) PTC_X[7..0] X-lines I/O – – PTC_Y[7..0] Y-lines I – – Pulse Density Modulation Interface Controller - PDMIC PDMIC_DAT PDM Data Input – – PDMIC_CLK PDM Clock Output – – DS60001476B-page 12  2017 Microchip Technology Inc. SAMA5D2 SERIES 5. Safety and Security Features 5.1 Design for Safety and IEC60730 Class B Certification 5.1.1 Background Information The IEC 60730 standard encompasses all aspects of appliance design. Annex H of the standard covers the aspects most relevant to microcontrollers. It details the tests and diagnostics which are intended to ensure safe operation of embedded control hardware and software. IEC 60730 defines three classifications for electronic control functions: • Class A - Control functions which are not intended to be relied upon for safety of the equipment • Class B - Control functions intended to prevent unsafe operation of the controlled equipment • Class C - Control functions intended to prevent special hazards such as explosions Specific design techniques have been used in the SAMA5D2 to ease compliance with the IEC 60730 Class B Certification and to resolve general-purpose safety concerns. This allows reduced software development and code size as well as savings on external hardware circuitry, since built-in self-tests are already embedded in the MPU. Table 5-1 gives the list of peripherals which incorporate these techniques, and details whether these features are applicable for the IEC 60730 Class B Certification or for general-purpose safety considerations. 5.2 Design for Security The SAMA5D2 embeds peripherals with security features to prevent counterfeiting, to secure external communication, and to authenticate the system. Table 5-2 provides the list of peripherals and an overview of their security function. For more information, see the sections on each peripheral.  2017 Microchip Technology Inc. DS60001476B-page 13 SAMA5D2 SERIES 5.3 Safety and IEC 60730 Features Table 5-1: Safety and IEC 60730 Features List Peripheral Requirements for Class B IEC 60730(1) General Safety – X X X X X – X X – X – X – – X – X X X – X Watchdog overflow generates a system reset X X Cortex-A5 Memory Management Unit – X – X Component Fault/Error/Feature CPU clock monitoring - Overclocking detection PMC Clock 32.768 kHz crystal oscillator frequency monitoring - Abnormal frequency deviation Main crystal oscillator - Crystal failure detection Programmable configuration lock (active until next VDDCORE reset) to protect against further software modifications (intentional or unintentional) PIOC I/O Periphery Digital I/O - Plausibility check Analog I/O and ADC converter ADCC ICM (SHA) NAND Flash Controller ECC - Plausibility check Memory and Internal Data Path All internal and external memories such as QSPI, DDR, and all memories on SMC Non-volatile memory - Mutiple error detection (2 to 32) Power supplies System Controller Supply Monitor - VDDCORE, VDDIO, VDDANA, VDDBU abnormal levels Watchdog can be fed by an internal always ON clock - Program counter stuck at faults. WDT, RSTC Cortex MMU MATRIX, AIC, RTC, SYSC, RXLP, ACC, PMC, PIO, MPDDRC, SMC, CLASSD, SSC, TWI, UART, SPI, FLEXCOM, QSPI, TC, PDMIC, ADC DS60001476B-page 14 Watchdog Watchdog configuration can be locked (writeprotected) - Errant writes (Programming errors, errors introduced by system or hardware failures) Memory Management Unit Peripherals Configuration, Interrupt Enable/Disable, Control registers can be independently write-protected - Errant writes (Programming errors, errors introduced by system or hardware failures)  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 5-1: Safety and IEC 60730 Features List (Continued) Peripheral Component Fault/Error/Feature Fault inputs can be configured to put the PWM outputs in Safe mode - Programming errors, errors introduced by system or hardware failures PWM, PIO General Safety – X – X – X PIO controller can lock the PWM I/O PWM - Programming errors, errors introduced by system or hardware failures Fault inputs can be external (IO) or internal (ADC, TIMER, ACC, etc.) - Programming errors, errors introduced by system or hardware failures Note 1: Class B IEC 60730 Requirements. Annex H - Table H.1 (H.11.12.7 of edition 3).  2017 Microchip Technology Inc. Requirements for Class B IEC 60730(1) DS60001476B-page 15 SAMA5D2 SERIES 5.4 Security Features Table 5-2: Security Features Peripheral Function TrustZone Security Enclave Cortex MMU Memory Management Unit I/O Control/ Peripheral Access Description Comments Partition secure/non-secure world ARM technology Cortex-A5 Memory Management Unit – When a peripheral is not selected (PIO-controlled), I/ O lines have no access to the peripheral. – Capability to freeze either the functional part or the physical part of the configuration. Once the freeze command is issued, no modifications to the current configuration are possible. Only a hardware reset allows a change to the configuration. PIO Freeze Software ECC (Asymmetric key algorithm, elliptic curves) Classical Atmel Software Crypto LIbrary (CASCL) TDES, TRNG Software library(1) Software RSA (Asymmetric key algorithm) Cryptography Hardware-accelerated Triple DES True Random Number Generator FIPS-compliant(3) Hardware-accelerated AES up to 256 bits SHA up to 512 and HMAC-SHA AES, SHA Secure Boot AESB AES on-the-fly Memories Scrambling ICM Memory Integrity Check Monitoring DS60001476B-page 16 Code encrypted/decrypted, Trusted Code Authentication Hardware SHA (HMAC) + Software RSA or AES Hardware (CMAC) On-the-fly encryption/decryption for DDR and QSPI memories AES128 On-the-fly scrambling/unscrambling for memories All internal and external memories such as QSPI, DDR, and all memories on SMC More robust than CRC. Uses a hardware Secure Hash Algorithm (up to SHA256) All internal and external memories such as QSPI, DDR, and all memories on SMC can be monitored  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 5-2: Peripheral Security Features (Continued) Function JTAG Test Active Shield(2) Voltage Monitoring(2) Temperature Monitoring(2) SECUMOD Frequency Monitoring(2) RTC Description Comments JTAG entry monitor Test entry monitor Die Active Shield VDDBU monitoring VDDCORE monitoring Temperature monitoring 32.768 kHz crystal oscillator monitoring These tamper pins (JTAG, test, PIOBUs, monitors, etc.) can be configured to immediately erase Backup memories (BUSRAM4KB and BUREG256b), or generate an interrupt or a wakeup signal. CPU clock monitoring IO Tamper Pin 8 tamper detection pins. Active and Dynamic modes supported. Secure Backup SRAM 5 Kbytes scrambled and non-imprinting avoiding data persistance 4 Kbytes erasable on tamper detection Secure Backup Registers 256-bit register bank, scrambled Erasable on tamper detection Timestamping of tamper events. Protection against bad configuration (invalid entry for date and time are impossible) All events are logged in the RTC. Timestamping gives the source of the reset/erase memory/interruption RTC robustness against glitch attack on 32 kHz crystal oscillator – Disable JTAG access by fuse bit – RTC JTAG Access Control Secure Fuse Secure Debug JTAG debug allowed in Normal mode only, not in Disable Secure mode Note 1: A PCI-certified Atmel Software Crypto Library (ASCL) is available under NDA. TrustZone 2: Available on SAMA5D23 and SAMA5D28 only. For environmental monitors, refer to the document “SAMA5D23 and SAMA5D28 Environmental Monitors” (document no. 44036), available under Non-Disclosure Agreement (NDA). Contact a Microchip sales representative for details. 3: Refer to the sections on each peripheral for details on FIPS compliancy.  2017 Microchip Technology Inc. DS60001476B-page 17 SAMA5D2 SERIES 6. Package and Pinout 6.1 Packages The SAMA5D2 is available in the packages listed in Table 6-1. Table 6-1: SAMA5D2 Packages Package Name Pin Count Ball Pitch LFBGA289 289 0.8 mm TFBGA256 256 0.4 mm TFBGA196 196 0.75 mm The package mechanical characteristics are described in Section 67. “Mechanical Characteristics”. 6.2 Pinouts Pinouts are provided in - Table 6-2 “Pin Description” - Table 6-3 “Pin Description (SAMA5D23 pins different from those in Table 6-2 “Pin Description”)” - Table 6-4 “Pin Description (SAMA5D28B/C pins different from those in Table 6-2 “Pin Description”)”. Note: I/Os for each peripheral are grouped into IO sets, listed in the column ‘IO Set’ in the pinout tables below. For all peripherals, it is mandatory to use I/Os that belong to the same IO set. The timings are not guaranteed when IOs from different IO sets are mixed. Table 6-2: Pin Description 289- 256- 196pin pin pin BGA BGA BGA U11 P10 T11 R10 U12 T12 R10 R9 U11 P10 P11 V11 – – – – – – Primary Power Rail VDDSDMMC VDDSDMMC VDDSDMMC VDDSDMMC VDDSDMMC VDDSDMMC DS60001476B-page 18 I/O Type GPIO_EMMC GPIO_EMMC GPIO_EMMC GPIO_EMMC GPIO_EMMC GGPIO_EMMC Signal PA0 PA1 PA2 PA3 PA4 PA5 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func – – – – – – Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A SDMMC0_CK I/O 1 B QSPI0_SCK F D0 I/O 2 A SDMMC0_CMD I/O 1 B QSPI0_CS F D1 I/O 2 A SDMMC0_DAT0 I/O 1 B QSPI0_IO0 I/O 1 F D2 I/O 2 A SDMMC0_DAT1 I/O 1 B QSPI0_IO1 I/O 1 F D3 I/O 2 A SDMMC0_DAT2 I/O 1 B QSPI0_IO2 I/O 1 F D4 I/O 2 A SDMMC0_DAT3 I/O 1 B QSPI0_IO3 I/O 1 F D5 I/O 2 O O 1 1 PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA R12 T13 N10 N11 U13 P15 N15 P16 U12 V12 N11 P12 U13 R14 N13 P14 – – – – – – – – Primary Power Rail VDDSDMMC VDDSDMMC VDDSDMMC VDDSDMMC VDDSDMMC VDDIOP1 VDDIOP1 VDDIOP1  2017 Microchip Technology Inc. I/O Type GPIO_EMMC GPIO_EMMC GPIO_EMMC GPIO_EMMC GPIO_EMMC GPIO GPIO GPIO Signal PA6 PA7 PA8 PA9 PA10 PA11 PA12 PA13 Alternate Dir I/O I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – – PIO peripheral Dir Func – – – – – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A SDMMC0_DAT4 I/O 1 B QSPI1_SCK D TIOA5 I/O 1 E FLEXCOM2_IO0 I/O 1 F D6 I/O 2 A SDMMC0_DAT5 I/O 1 B QSPI1_IO0 I/O 1 D TIOB5 I/O 1 E FLEXCOM2_IO1 I/O 1 F D7 I/O 2 A SDMMC0_DAT6 I/O 1 B QSPI1_IO1 I/O 1 D TCLK5 E FLEXCOM2_IO2 I/O 1 F NWE/NANDWE O A SDMMC0_DAT7 I/O 1 B QSPI1_IO2 I/O 1 D TIOA4 I/O 1 E FLEXCOM2_IO3 O 1 F NCS3 O 2 A SDMMC0_RSTN O 1 B QSPI1_IO3 I/O 1 D TIOB4 I/O 1 E FLEXCOM2_IO4 O 1 F A21/NANDALE O 2 A SDMMC0_1V8SEL O 1 B QSPI1_CS O 1 D TCLK4 I 1 F A22/NANDCLE O 2 A SDMMC0_WP I 1 B IRQ I 1 F NRD/NANDOE O 2 A SDMMC0_CD I 1 E FLEXCOM3_IO1 I/O 1 F D8 I/O 2 O I 1 1 – PIO, I, PU, ST PIO, I, PU, ST 2 – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST DS60001476B-page 19 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA M14 N16 P17 R18 M10 N15 N17 U14 T14 P18 M9 V13 – – – – L9 N9 Primary Power Rail VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 DS60001476B-page 20 I/O Type GPIO_QSPI GPIO GPIO_IO GPIO_IO GPIO_IO GPIO_IO Signal PA14 PA15 PA16 PA17 PA18 PA19 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A SPI0_SPCK I/O 1 B TK1 I/O 1 C QSPI0_SCK O 2 D I2SC1_MCK O 2 E FLEXCOM3_IO2 I/O 1 F D9 I/O 2 A SPI0_MOSI I/O 1 B TF1 I/O 1 C QSPI0_CS O D I2SC1_CK I/O 2 E FLEXCOM3_IO0 I/O 1 F D10 I/O 2 A SPI0_MISO I/O 1 B TD1 C QSPI0_IO0 I/O 2 D I2SC1_WS I/O 2 E FLEXCOM3_IO3 F D11 I/O 2 A SPI0_NPCS0 I/O 1 B RD1 C QSPI0_IO1 D I2SC1_DI0 I 2 E FLEXCOM3_IO4 O 1 F D12 A SPI0_NPCS1 B RK1 I/O 1 C QSPI0_IO2 I/O 2 D I2SC1_DO0 O E SDMMC1_DAT0 I/O 1 F D13 I/O 2 A SPI0_NPCS2 B RF1 I/O 1 C QSPI0_IO3 I/O 2 D TIOA0 I/O 1 E SDMMC1_DAT1 I/O 1 F D14 I/O 2 – PIO, I, PU, ST 2 – PIO, I, PU, ST O 1 – PIO, I, PU, ST O I 1 1 I/O 2 – PIO, I, PU, ST I/O 2 O 1 – PIO, I, PU, ST O 2 1 – PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA P12 L9 M9 R13 M10 M10 U15 U16 T15 U17 P13 V14 U14 R13 U15 L10 P9 P10 N10 L10 P11 Primary Power Rail VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1  2017 Microchip Technology Inc. I/O Type GPIO_IO GPIO_IO GPIO_QSPI GPIO GPIO_IO GPIO_IO GPIO_IO Signal PA20 PA21 PA22 PA23 PA24 PA25 PA26 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – PIO peripheral Dir Func Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A SPI0_NPCS3 O 1 D TIOB0 I/O 1 E SDMMC1_DAT2 I/O 1 F D15 I/O 2 A IRQ I 2 B PCK2 O 3 D TCLK0 I 1 E SDMMC1_DAT3 F NANDRDY A FLEXCOM1_IO2 I/O 1 B D0 I/O 1 C TCK D SPI1_SPCK I/O 2 E SDMMC1_CK I/O 1 F QSPI0_SCK A FLEXCOM1_IO1 I/O 1 B D1 I/O 1 C TDI D SPI1_MOSI I/O 2 F QSPI0_CS O A FLEXCOM1_IO0 I/O 1 B D2 I/O 1 C TDO D SPI1_MISO I/O 2 F QSPI0_IO0 I/O 3 A FLEXCOM1_IO3 B D3 C TMS D SPI1_NPCS0 I/O 2 F QSPI0_IO1 I/O 3 A FLEXCOM1_IO4 B D4 C NTRST I 4 D SPI1_NPCS1 O 2 F QSPI0_IO2 – – PIO, I, PU, ST I/O 1 I I 2 4 – – – – – PIO, I, PU, ST PIO, I, PU, ST O I O O 3 4 PIO, I, PU, ST 3 4 PIO, I, PU, ST 1 I/O 1 I O 4 PIO, I, PU, ST 1 I/O 1 PIO, I, PU, ST I/O 3 DS60001476B-page 21 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA T16 R16 T17 R15 R17 J8 A8 A7 V17 U16 U17 V18 P12 M11 N11 N12 U18 M12 G9 A7 B7 A6 A5 B6 Primary Power Rail VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP0 VDDIOP0 VDDIOP0 DS60001476B-page 22 I/O Type GPIO_IO GPIO GPIO GPIO GPIO GPIO GPIO GPIO Signal PA27 PA28 PA29 PA30 PA31 PB0 PB1 PB2 Alternate Dir I/O I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – – PIO peripheral Reset State Signal IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A TIOA1 I/O 2 B D5 I/O 1 C SPI0_NPCS2 O 2 D SPI1_NPCS2 O 2 E SDMMC1_RSTN O 1 F QSPI0_IO3 I/O 3 A TIOB1 I/O 2 B D6 I/O 1 C SPI0_NPCS3 O 2 D SPI1_NPCS3 O 2 E SDMMC1_CMD F CLASSD_L0 O 1 A TCLK1 I 2 B D7 C SPI0_NPCS1 O 2 E SDMMC1_WP I 1 F CLASSD_L1 O 1 B NWE/NANDWE O 1 C SPI0_NPCS0 D PWMH0 O 1 E SDMMC1_CD I 1 F CLASSD_L2 O 1 B NCS3 O 1 C SPI0_MISO D PWML0 O 1 F CLASSD_L3 O 1 B A21/NANDALE O 1 C SPI0_MOSI D PWMH1 O 1 B A22/NANDCLE O 1 C SPI0_SPCK D PWML1 O 1 F CLASSD_R0 O 1 B NRD/NANDOE O 1 D PWMFI0 I 1 F CLASSD_R1 O 1 Dir Func – PIO, I, PU, ST – – – PIO, I, PU, ST I/O 1 I/O 1 I/O 2 PIO, I, PU, ST I/O 2 PIO, I, PU, ST I/O 2 – – PIO, I, PU, ST I/O 2 – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA A6 B6 B7 C7 C6 A5 A4 B6 A6 D7 B5 A5 E7 F6 B5 A4 D6 A3 B4 A2 B3 Primary Power Rail VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0  2017 Microchip Technology Inc. I/O Type GPIO GPIO GPIO_QSPI GPIO GPIO_IO GPIO_IO GPIO_IO Signal PB3 PB4 PB5 PB6 PB7 PB8 PB9 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – PIO peripheral Dir Func – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A URXD4 I 1 B D8 C IRQ I 3 D PWMEXTRG1 I 1 F CLASSD_R2 O 1 A UTXD4 O 1 B D9 C FIQ I 4 F CLASSD_R3 O 1 A TCLK2 I 1 B D10 C PWMH2 O 1 D QSPI1_SCK O 2 F GTSUCOMP O 3 A TIOA2 I/O 1 B D11 I/O 1 C PWML2 O 1 D QSPI1_CS O 2 F GTXER O 3 A TIOB2 I/O 1 B D12 I/O 1 C PWMH3 D QSPI1_IO0 F GRXCK I 3 A TCLK3 I 1 B D13 C PWML3 D QSPI1_IO1 F GCRS A TIOA3 I/O 1 B D14 I/O 1 C PWMFI1 D QSPI1_IO2 F GCOL I/O 1 I/O 1 – – – – – – PIO, I, PU, ST PIO, I, PU, ST I/O 1 O 1 PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST I/O 2 I/O 1 O 1 PIO, I, PU, ST I/O 2 I I 3 1 PIO, I, PU, ST I/O 2 I 3 DS60001476B-page 23 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA H8 B5 D6 B4 C5 H7 D5 D6 A4 B3 A3 B4 G8 E5 A1 B1 B2 C1 D5 E5 C5 Primary Power Rail VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 DS60001476B-page 24 I/O Type GPIO_IO GPIO GPIO GPIO GPIO_QSPI GPIO GPIO_IO Signal PB10 PB11 PB12 PB13 PB14 PB15 PB16 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – PIO peripheral Signal A TIOB3 I/O 1 B D15 I/O 1 C PWMEXTRG2 D QSPI1_IO3 F GRX2 I 3 A LCDDAT0 O 1 B A0/NBS0 O 1 C URXD3 I 3 D PDMIC_DAT F GRX3 I 3 A LCDDAT1 O 1 B A1 O 1 C UTXD3 O 3 D PDMIC_CLK F GTX2 O 3 A LCDDAT2 O 1 B A2 O 1 C PCK1 O 3 F GTX3 O 3 A LCDDAT3 O 1 B A3 O 1 C TK1 D I2SC1_MCK O 1 E QSPI1_SCK O 3 F GTXCK A LCDDAT4 O 1 B A4 O 1 C TF1 I/O 2 D I2SC1_CK I/O 1 E QSPI1_CS O 3 F GTXEN O 3 A LCDDAT5 O 1 B A5 O 1 C TD1 O 2 D I2SC1_WS I/O 1 E QSPI1_IO0 I/O 3 F GRXDV Dir Func – – – Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) I 1 PIO, I, PU, ST I/O 2 PIO, I, PU, ST 2 PIO, I, PU, ST 2 – PIO, I, PU, ST I/O 2 – PIO, I, PU, ST I/O 3 – PIO, I, PU, ST – PIO, I, PU, ST I 3  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA C4 A3 D4 B3 A2 C3 G7 A2 H7 A1 D2 G5 C2 D4 C4 C3 D1 D2 Primary Power Rail VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0  2017 Microchip Technology Inc. I/O Type GPIO_IO GPIO_IO GPIO_IO GPIO GPIO GPIO Signal PB17 PB18 PB19 PB20 PB21 PB22 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A LCDDAT6 O 1 B A6 O 1 C RD1 I 2 D I2SC1_DI0 I 1 E QSPI1_IO1 F GRXER I 3 A LCDDAT7 O 1 B A7 O 1 C RK1 D I2SC1_DO0 O E QSPI1_IO2 I/O 3 F GRX0 I 3 A LCDDAT8 O 1 B A8 O 1 C RF1 I/O 2 D TIOA3 I/O 2 E QSPI1_IO3 I/O 3 F GRX1 I 3 A LCDDAT9 O 1 B A9 O 1 C TK0 I/O 1 D TIOB3 I/O 2 E PCK1 O 4 F GTX0 O 3 A LCDDAT10 O 1 B A10 O 1 C TF0 I/O 1 D TCLK3 E FLEXCOM3_IO2 F GTX1 O 3 A LCDDAT11 O 1 B A11 O 1 C TD0 O 1 D TIOA2 I/O 2 E FLEXCOM3_IO1 I/O 3 F GMDC – PIO, I, PU, ST I/O 3 I/O 2 – PIO, I, PU, ST 1 – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST I 2 I/O 3 – PIO, I, PU, ST O 3 DS60001476B-page 25 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA A1 E5 B2 E4 B1 C2 D3 C2 F4 C1 E4 F1 D1 F2 E1 D3 E3 E2 E6 F1 F6 Primary Power Rail VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 DS60001476B-page 26 I/O Type GPIO GPIO GPIO GPIO GPIO GPIO GPIO Signal PB23 PB24 PB25 PB26 PB27 PB28 PB29 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – PIO peripheral Dir Func Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A LCDDAT12 O 1 B A12 O 1 C RD0 I 1 D TIOB2 I/O 2 E FLEXCOM3_IO0 I/O 3 F GMDIO I/O 3 A LCDDAT13 O 1 B A13 O 1 C RK0 I/O 1 D TCLK2 I 2 E FLEXCOM3_IO3 O 3 F ISC_D10 I 3 A LCDDAT14 O 1 B A14 O 1 C RF0 I/O 1 E FLEXCOM3_IO4 O 3 F ISC_D11 I 3 A LCDDAT15 O 1 B A15 O 1 C URXD0 I 1 D PDMIC_DAT F ISC_D0 I 3 A LCDDAT16 O 1 B A16 O 1 C UTXD0 O 1 D PDMIC_CLK F ISC_D1 I 3 A LCDDAT17 O 1 B A17 O 1 C FLEXCOM0_IO0 I/O 1 D TIOA5 I/O 2 F ISC_D2 I 3 A LCDDAT18 O 1 B A18 O 1 C FLEXCOM0_IO1 I/O 1 D TIOB5 I/O 2 F ISC_D3 – PIO, I, PU, ST – – – – – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST 1 PIO, I, PU, ST 1 I PIO, I, PU, ST PIO, I, PU, ST 3  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA D2 C1 P17 N12 N14 M15 E2 E1 F2 F7 R15 M13 M11 P15 K9 P13 N13 K10 Primary Power Rail VDDIOP0 VDDIOP0 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1  2017 Microchip Technology Inc. I/O Type GPIO GPIO GPIO GPIO GPIO GPIO Signal PB30 PB31 PC0 PC1 PC2 PC3 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func – – – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A LCDDAT19 O 1 B A19 O 1 C FLEXCOM0_IO2 D TCLK5 I 2 F ISC_D4 I 3 A LCDDAT20 O 1 B A20 O 1 C FLEXCOM0_IO3 O 1 D TWD0 F ISC_D5 I 3 A LCDDAT21 O 1 B A23 O 1 C FLEXCOM0_IO4 O 1 D TWCK0 F ISC_D6 I 3 A LCDDAT22 O 1 B A24 O 1 C CANTX0 O 1 D SPI1_SPCK I/O 1 E I2SC0_CK I/O 1 F ISC_D7 I 3 A LCDDAT23 O 1 B A25 O 1 C CANRX0 I 1 D SPI1_MOSI I/O 1 E I2SC0_MCK O 1 F ISC_D8 I 3 A LCDPWM O 1 B NWAIT I 1 C TIOA1 I/O 1 D SPI1_MISO I/O 1 E I2SC0_WS I/O 1 F ISC_D9 I/O 1 PIO, I, PU, ST PIO, I, PU, ST I/O 1 PIO, I, PU, ST I/O 1 – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST I 3 DS60001476B-page 27 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA M11 L10 K10 K10 L11 L12 P14 J8 N14 M16 M12 M14 J10 D1 K11 – J9 – Primary Power Rail VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDIOP1 VDDISC DS60001476B-page 28 I/O Type GPIO GPIO GPIO GPIO_CLK GPIO GPIO Signal PC4 PC5 PC6 PC7 PC8 PC9 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A LCDDISP O 1 B NWR1/NBS1 O 1 C TIOB1 I/O 1 D SPI1_NPCS0 I/O 1 E I2SC0_DI0 I 1 F ISC_PCK I 3 A LCDVSYNC O 1 B NCS0 O 1 C TCLK1 I 1 D SPI1_NPCS1 O 1 E I2SC0_DO0 O 1 F ISC_VSYNC I 3 A LCDHSYNC O 1 B NCS1 O 1 C TWD1 I/O 1 D SPI1_NPCS2 O 1 F ISC_HSYNC I 3 A LCDPCK O 1 B NCS2 O 1 C TWCK1 D SPI1_NPCS3 O 1 E URXD1 I 2 F ISC_MCK O 3 A LCDDEN O 1 B NANDRDY I 1 C FIQ I 1 D PCK0 O 3 E UTXD1 O 2 F ISC_FIELD I 3 A FIQ I 3 B GTSUCOMP O 1 C ISC_D0 I 1 D TIOA4 – PIO, I, PU, ST – – PIO, I, PU, ST PIO, I, PU, ST I/O 1 – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST I/O 2  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA E3 E2 E1 F3 F5 F2 – – – – – – – – – – – – Primary Power Rail VDDISC VDDISC VDDISC VDDISC VDDISC VDDISC  2017 Microchip Technology Inc. I/O Type GPIO GPIO GPIO GPIO GPIO GPIO Signal PC10 PC11 PC12 PC13 PC14 PC15 Alternate Dir I/O I/O I/O I/O I/O I/O Signal – – – – – – PIO peripheral Dir Func – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A LCDDAT2 O 2 B GTXCK C ISC_D1 D TIOB4 E CANTX0 O 2 A LCDDAT3 O 2 B GTXEN O 1 C ISC_D2 I 1 D TCLK4 I 2 E CANRX0 I 2 F A0/NBS0 O 2 A LCDDAT4 O 2 B GRXDV I 1 C ISC_D3 I 1 D URXD3 I 1 E TK0 F A1 O 2 A LCDDAT5 O 2 B GRXER I 1 C ISC_D4 I 1 D UTXD3 O 1 E TF0 I/O 2 F A2 O 2 A LCDDAT6 O 2 B GRX0 I 1 C ISC_D5 I 1 E TD0 O 2 F A3 O 2 A LCDDAT7 O 2 B GRX1 I 1 C ISC_D6 I 1 E RD0 I 2 F A4 O 2 I/O 1 I 1 I/O 2 – PIO, I, PU, ST – PIO, I, PU, ST I/O 2 – – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST DS60001476B-page 29 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA G6 F1 H6 G2 G3 G1 H2 – – – – – – – – – – – – – – Primary Power Rail VDDISC VDDISC VDDISC VDDISC VDDISC VDDISC VDDISC DS60001476B-page 30 I/O Type GPIO GPIO GPIO GPIO GPIO GPIO GPIO Signal PC16 PC17 PC18 PC19 PC20 PC21 PC22 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – PIO peripheral Dir Func – – – – – – – Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A LCDDAT10 O 2 B GTX0 O 1 C ISC_D7 I 1 E RK0 F A5 O 2 A LCDDAT11 O 2 B GTX1 O 1 C ISC_D8 I 1 E RF0 F A6 O 2 A LCDDAT12 O 2 B GMDC O 1 C ISC_D9 I 1 E FLEXCOM3_IO2 F A7 O 2 A LCDDAT13 O 2 B GMDIO C ISC_D10 E FLEXCOM3_IO1 F A8 O 2 A LCDDAT14 O 2 B GRXCK I 1 C ISC_D11 I 1 E FLEXCOM3_IO0 F A9 O 2 A LCDDAT15 O 2 B GTXER O 1 C ISC_PCK I 1 E FLEXCOM3_IO3 O 2 F A10 O 2 A LCDDAT18 O 2 B GCRS I 1 C ISC_VSYNC I 1 E FLEXCOM3_IO4 O 2 F A11 O 2 PIO, I, PU, ST I/O 2 PIO, I, PU, ST I/O 2 PIO, I, PU, ST I/O 2 I/O 1 I 1 PIO, I, PU, ST I/O 2 PIO, I, PU, ST I/O 2 PIO, I, PU, ST PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA G5 H1 H5 J9 H9 E8 G8 F8 D8 – – – – – – – – – – – – – – – – – – Primary Power Rail VDDISC VDDISC VDDISC VDDIOP2 VDDIOP2 VDDIOP2 VDDIOP2 VDDIOP2 VDDIOP2  2017 Microchip Technology Inc. I/O Type GPIO GPIO_CLK GPIO GPIO GPIO GPIO GPIO GPIO GPIO Signal PC23 PC24 PC25 PC26 PC27 PC28 PC29 PC30 PC31 Alternate Dir I/O I/O I/O I/O I/O I/O I/O I/O I/O Signal – – – – – – – – – PIO peripheral Dir Func Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A LCDDAT19 O 2 B GCOL I 1 C ISC_HSYNC I 1 F A12 O 2 A LCDDAT20 O 2 B GRX2 I 1 C ISC_MCK O 1 F A13 O 2 A LCDDAT21 O 2 B GRX3 I 1 C ISC_FIELD I 1 F A14 O 2 A LCDDAT22 O 2 B GTX2 O 1 D CANTX1 O 1 F A15 O 2 A LCDDAT23 O 2 B GTX3 O 1 C PCK1 O 2 D CANRX1 I 1 E TWD0 F A16 O 2 A LCDPWM O 2 B FLEXCOM4_IO0 C PCK2 E TWCK0 F A17 O 2 A LCDDISP O 2 B FLEXCOM4_IO1 F A18 O 2 A LCDVSYNC O 2 B FLEXCOM4_IO2 F A19 O 2 A LCDHSYNC O 2 B FLEXCOM4_IO3 O 1 C URXD3 I 2 F A20 O 2 – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST – – – – PIO, I, PU, ST I/O 2 I/O 1 O 1 PIO, I, PU, ST I/O 2 I/O 1 I/O 1 – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST DS60001476B-page 31 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA G10 E10 G9 K1 J6 J4 J2 J7 E9 F8 F9 J4 H6 H1 G4 H5 – – – – – – – F5 Primary Power Rail VDDIOP2 VDDIOP2 VDDIOP2 VDDANA VDDANA VDDANA VDDANA VDDANA DS60001476B-page 32 I/O Type GPIO_CLK GPIO GPIO_CLK GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD Signal PD0 PD1 PD2 PD3 PD4 PD5 PD6 PD7 Alternate Dir I/O I/O I/O I/O I/O I/O I/O I/O Signal – – – PTC_X0 PTC_X1 PTC_X2 PTC_X3 PTC_X4 PIO peripheral Dir Func – – Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A LCDPCK O 2 B FLEXCOM4_IO4 O 1 C UTXD3 O 2 D GTSUCOMP O 2 F A23 O 2 A LCDDEN O 2 D GRXCK I 2 F A24 O 2 A URXD1 I 1 D GTXER O 2 E ISC_MCK O 2 F A25 O 2 A UTXD1 O 1 B FIQ I 2 D GCRS I 2 E ISC_D11 I 2 F NWAIT I 2 A TWD1 B URXD2 I 1 D GCOL I 2 E ISC_D10 I 2 F NCS0 O 2 A TWCK1 I/O 2 B UTXD2 O 1 D GRX2 I 2 E ISC_D9 I 2 F NCS1 O 2 A TCK I 2 B PCK1 O 1 D GRX3 I 2 E ISC_D8 I 2 F NCS2 O 2 A TDI I 2 C UTMI_RXVAL O 1 D GTX2 O 2 E ISC_D0 I 2 F NWR1/NBS1 O 2 – – – – – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST I/O 2 PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA J1 K9 J3 M1 K8 L2 K4 G1 H4 G2 H2 K5 J5 K6 F3 G5 G4 H1 H6 H3 G6 Primary Power Rail VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA  2017 Microchip Technology Inc. I/O Type GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD Signal PD8 PD9 PD10 PD11 PD12 PD13 PD14 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal PTC_X5 PTC_X6 PTC_X7 PTC_Y0 PTC_Y1 PTC_Y2 PTC_Y3 PIO peripheral Dir Func – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A TDO O 2 C UTMI_RXERR O 1 D GTX3 O 2 E ISC_D1 I 2 F NANDRDY I 2 A TMS I 2 C UTMI_RXACT O 1 D GTXCK E ISC_D2 I 2 A NTRST I 2 C UTMI_HDIS O 1 D GTXEN O 2 E ISC_D3 I 2 A TIOA1 I/O 3 B PCK2 O 2 C UTMI_LS0 O 1 D GRXDV I 2 E ISC_D4 I 2 F ISC_MCK O 4 A TIOB1 I/O 3 B FLEXCOM4_IO0 I/O 2 C UTMI_LS1 O 1 D GRXER I 2 E ISC_D5 I 2 F ISC_D4 I 4 A TCLK1 I 3 B FLEXCOM4_IO1 C UTMI_CDRCPSEL0 I 1 D GRX0 I 2 E ISC_D6 I 2 F ISC_D5 I 4 A TCK I 1 B FLEXCOM4_IO2 C UTMI_CDRCPSEL1 I 1 D GRX1 I 2 E ISC_D7 I 2 F ISC_D6 I 4 – PIO, I, PU, ST PIO, I, PU, ST I/O 2 – PIO, I, PU, ST – PIO, I, PU, ST – PIO, I, PU, ST I/O 2 – PIO, I, PU, ST I/O 2 – A, PU, ST DS60001476B-page 33 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA K7 L1 K2 J5 K6 M2 N1 K4 K1 K2 L5 L4 M1 M2 H5 G1 G2 G3 H4 J1 K1 Primary Power Rail VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA DS60001476B-page 34 I/O Type GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD Signal PD15 PD16 PD17 PD18 PD19 PD20 PD21 Alternate Dir I/O I/O I/O I/O I/O I/O I/O Signal PTC_Y4 PTC_Y5 PTC_Y6 PTC_Y7 AD0 AD1 AD2 PIO peripheral Dir Func Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal A TDI I 1 B FLEXCOM4_IO3 O 2 C UTMI_CDRCPDIVEN I 1 D GTX0 O 2 E ISC_PCK I 2 F ISC_D7 I 4 A TDO O 1 B FLEXCOM4_IO4 O 2 C UTMI_CDRBISTEN I 1 D GTX1 O 2 E ISC_VSYNC I 2 F ISC_D8 I 4 A TMS I 1 C UTMI_CDRCPSELDIV O 1 D GMDC O 2 E ISC_HSYNC I 2 F ISC_D9 I 4 A NTRST I 1 D GMDIO E ISC_FIELD I 2 F ISC_D10 I 4 A PCK0 O 1 B TWD1 I/O 3 C URXD2 E I2SC0_CK F ISC_D11 A TIOA2 I/O 3 B TWCK1 I/O 3 C UTXD2 O 3 E I2SC0_MCK O 2 F ISC_PCK I 4 A TIOB2 I/O 3 B TWD0 I/O 4 C FLEXCOM4_IO0 I/O 3 E I2SC0_WS I/O 2 F ISC_VSYNC – PIO, I, PU, ST – – PIO, I, PU, ST I/O 2 – – – – A, PU, ST PIO, I, PU, ST I 3 PIO, I, PU, ST I/O 2 I I 4 PIO, I, PU, ST PIO, I, PU, ST 4  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA L4 M3 L7 L6 N2 L8 M4 N3 L9 M7 L5 M4 P1 L6 M5 N1 N2 P2 R1 N4 T1 L1 J3 K2 – – – – – – – – K3 Primary Power Rail VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA VDDANA  2017 Microchip Technology Inc. I/O Type GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO_AD GPIO power Signal PD22 PD23 PD24 PD25 PD26 PD27 PD28 PD29 PD30 PD31 VDDANA Alternate Dir I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I Signal AD3 AD4 AD5 AD6 AD7 AD8 AD9 AD10 AD11 – – PIO peripheral Dir Func – Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) A TCLK2 I 3 B TWCK0 I/O 4 C FLEXCOM4_IO1 I/O 3 E I2SC0_DI0 I 2 F ISC_HSYNC I 4 A URXD2 I 2 C FLEXCOM4_IO2 E I2SC0_DO0 O 2 F ISC_FIELD I 4 A UTXD2 O 2 C FLEXCOM4_IO3 O 3 A SPI1_SPCK C FLEXCOM4_IO4 A SPI1_MOSI I/O 3 C FLEXCOM2_IO0 I/O 2 A SPI1_MISO I/O 3 B TCK C FLEXCOM2_IO1 I/O 2 A SPI1_NPCS0 I/O 3 B TDI C FLEXCOM2_IO2 A SPI1_NPCS1 O 3 B TDO O 3 C FLEXCOM2_IO3 O 2 D TIOA3 I/O 3 E TWD0 I/O 3 A SPI1_NPCS2 O 3 B TMS I 3 C FLEXCOM2_IO4 O 2 D TIOB3 I/O 3 E TWCK0 I/O 3 A ADTRG I 1 B NTRST I 3 C IRQ I 4 D TCLK3 I 3 E PCK0 O 2 – – – – I/O 3 – PIO, I, PU, ST – PIO, I, PU, ST I/O 3 – PIO, I, PU, ST O 3 – – – – – – – PIO, I, PU, ST PIO, I, PU, ST I I 3 3 PIO, I, PU, ST PIO, I, PU, ST I/O 2 PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST – DS60001476B-page 35 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA Primary Alternate Power Rail I/O Type Signal Dir Signal PIO peripheral Dir Func Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) K5 L2 K4 GNDANA ground GNDANA I – – – – – – – M6 P5 L2 VDDANA – ADVREF I – – – – – – – K3 J1 H2 VDDANA power VDDANA I – – – – – – – L3 J2 J2 GNDANA ground GNDANA I – – – – – – – H16, J17, H12, D16 D12 C12 VDDIODDR DDR DDR_VREF – – – – – – – – B12 B12 B7 VDDIODDR DDR DDR_D0 – – – – – – – – A12 B13 A7 VDDIODDR DDR DDR_D1 – – – – – – – – C12 D13 C8 VDDIODDR DDR DDR_D2 – – – – – – – – A13 A13 B9 VDDIODDR DDR DDR_D3 – – – – – – – – A14 A15 A9 VDDIODDR DDR DDR_D4 – – – – – – – – C13 D14 C9 VDDIODDR DDR DDR_D5 – – – – – – – – A15 B15 A10 VDDIODDR DDR DDR_D6 – – – – – – – – B15 B16 B10 VDDIODDR DDR DDR_D7 – – – – – – – – G17 G18 H13 VDDIODDR DDR DDR_D8 – – – – – – – – G16 K17 H14 VDDIODDR DDR DDR_D9 – – – – – – – – H17 J13 J13 VDDIODDR DDR DDR_D10 – – – – – – – – K17 H15 J14 VDDIODDR DDR DDR_D11 – – – – – – – – K16 J15 L13 VDDIODDR DDR DDR_D12 – – – – – – – – J13 J14 L14 VDDIODDR DDR DDR_D13 – – – – – – – – K14 K13 J12 VDDIODDR DDR DDR_D14 – – – – – – – – K15 K18 K12 VDDIODDR DDR DDR_D15 – – – – – – – – B8 A8 – VDDIODDR DDR DDR_D16 – – – – – – – – B9 B9 – VDDIODDR DDR DDR_D17 – – – – – – – – C9 D9 – VDDIODDR DDR DDR_D18 – – – – – – – – A9 A9 – VDDIODDR DDR DDR_D19 – – – – – – – – A10 B11 – VDDIODDR DDR DDR_D20 – – – – – – – – D10 D10 – VDDIODDR DDR DDR_D21 – – – – – – – – B11 A11 – VDDIODDR DDR DDR_D22 – – – – – – – – A11 A12 – VDDIODDR DDR DDR_D23 – – – – – – – – J12 L18 – VDDIODDR DDR DDR_D24 – – – – – – – – H10 K15 – VDDIODDR DDR DDR_D25 – – – – – – – – J11 K14 – VDDIODDR DDR DDR_D26 – – – – – – – – K11 M18 – VDDIODDR DDR DDR_D27 – – – – – – – – L13 N17 – VDDIODDR DDR DDR_D28 – – – – – – – – L11 M14 – VDDIODDR DDR DDR_D29 – – – – – – – – L12 M15 – VDDIODDR DDR DDR_D30 – – – – – – – – M17 N18 – VDDIODDR DDR DDR_D31 – – – – – – – – DS60001476B-page 36  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) Primary Alternate PIO peripheral Reset State 289- 256- 196pin pin pin BGA BGA BGA Power Rail I/O Type Signal Dir Signal F12 D17 E11 VDDIODDR DDR DDR_A0 – – – – – – – – C17 A17 C11 VDDIODDR DDR DDR_A1 – – – – – – – – B17 A18 B12 VDDIODDR DDR DDR_A2 – – – – – – – – B16 F15 A12 VDDIODDR DDR DDR_A3 – – – – – – – – C16 G12 D11 VDDIODDR DDR DDR_A4 – – – – – – – – G14 H12 D14 VDDIODDR DDR DDR_A5 – – – – – – – – F14 F13 B14 VDDIODDR DDR DDR_A6 – – – – – – – – F11 H10 D9 VDDIODDR DDR DDR_A7 – – – – – – – – C14 A16 C10 VDDIODDR DDR DDR_A8 – – – – – – – – D13 E12 D10 VDDIODDR DDR DDR_A9 – – – – – – – – C15 H11 F9 VDDIODDR DDR DDR_A10 – – – – – – – – A16 J10 A11 VDDIODDR DDR DDR_A11 – – – – – – – – A17 D15 B11 VDDIODDR DDR DDR_A12 – – – – – – – – G11 J11 E13 VDDIODDR DDR DDR_A13 – – – – – – – – E17 C18 A13 VDDIODDR DDR DDR_CLK – – – – – – – – D17 C17 B13 VDDIODDR DDR DDR_CLKN – – – – – – – – F16 F18 E14 VDDIODDR DDR DDR_CKE – – – – – – – – E16 F17 D13 VDDIODDR DDR DDR_RESETN – – – – – – – – G13 J12 F11 VDDIODDR DDR DDR_CS – – – – – – – – F15 D18 A14 VDDIODDR DDR DDR_WE – – – – – – – – F13 E18 C14 VDDIODDR DDR DDR_RAS – – – – – – – – G12 E17 C13 VDDIODDR DDR DDR_CAS – – – – – – – – C11 D11 D8 VDDIODDR DDR DDR_DQM0 – – – – – – – – G15 H14 G14 VDDIODDR DDR DDR_DQM1 – – – – – – – – C8 B8 – VDDIODDR DDR DDR_DQM2 – – – – – – – – H11 L13 – VDDIODDR DDR DDR_DQM3 – – – – – – – – B13 A14 B8 VDDIODDR DDR DDR_DQS0 – – – – – – – – J17 H18 K14 VDDIODDR DDR DDR_DQS1 – – – – – – – – C10 A10 – VDDIODDR DDR DDR_DQS2 – – – – – – – – L17 M17 – VDDIODDR DDR DDR_DQS3 – – – – – – – – B14 B14 A8 VDDIODDR DDR DDR_DQSN0 – – – – – – – – J16 J18 K13 VDDIODDR DDR DDR_DQSN1 – – – – – – – – B10 B10 – VDDIODDR DDR DDR_DQSN2 – – – – – – – – L16 L17 – VDDIODDR DDR DDR_DQSN3 – – – – – – – – H12 H13 F13 VDDIODDR DDR DDR_BA0 – – – – – – – – H13 K12 G13 VDDIODDR DDR DDR_BA1 – – – – – – – – F17 H17 F14 VDDIODDR DDR DDR_BA2 – – – – – – – –  2017 Microchip Technology Inc. Dir Func Signal IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) DS60001476B-page 37 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) Primary Alternate PIO peripheral Reset State 289- 256- 196pin pin pin BGA BGA BGA Power Rail I/O Type Signal Dir Signal E13 G17 F10 VDDIODDR DDR DDR_CAL – – – – – – – – L15, J15, H15, E15, D15, D12, D11 B17, E11, E14, F10, G11, G15, L14 C6, E10, E12, G10, G12, H11, J10 VDDIODDR power VDDIODDR I – – – – – – – L14, J14, H14, E14, D14, E12, E11 B18, E10, E15, F11, G10, G14, L15 C7, D12, E9, F12, G11, H10, J11 GNDIODDR power GNDIODDR I – – – – – – – H3, N5, N9, K13, D9, D7 H8, J6, J9, K8, L8 E8, G8, H8, H9, J5 VDDCORE power VDDCORE I – – – – – – – H4, M5, M9, K12, E9, E7 H9, J7, J8, K7, L7 F8, G7, G9, H7, J4 GNDCORE ground GNDCORE I – – – – – – – E6, F7 B1, D5 D7, F4 VDDIOP0 power VDDIOP0 I – – – – – – – F6, G7 B2, D4 E4, E7 GNDIOP0 ground GNDIOP0 I – – – – – – – R14, T18, N13 V16 K8, L11 VDDIOP1 power VDDIOP1 I – – – – – – – M13, T17, P14 V15 K9, L12 GNDIOP1 ground GNDIOP1 I – – – – – – – Dir Func Signal IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) F10 D8 – VDDIOP2 power VDDIOP2 I – – – – – – – F9 E8 – GNDIOP2 ground GNDIOP2 I – – – – – – – P11 R11 – VDDSDMMC power VDDSDMMC I – – – – – – – R11 R12 – GNDSDMMC ground GNDSDMMC I – – – – – – – F4 – – VDDISC power VDDISC I – – – – – – – G4 – – GNDISC ground GNDISC I – – – – – – – K11 VDDFUSE power VDDFUSE I – – – – – – – M12 R17 U4 V5 P3 VDDPLLA power VDDPLLA I – – – – – – – U5 U6 P4 GNDPLLA ground GNDPLLA I – – – – – – – T3 M7 K6 VDDAUDIOPLL power VDDAUDIOPLL I – – – – – – – T5 P7 L6 GNDDPLL ground I – – – – – – – T4 N6 J6 GNDAUDIOPLL ground GNDAUDIOPLL I – – – – – – – DS60001476B-page 38 GNDDPLL  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA Primary Alternate Power Rail I/O Type Signal Dir Signal PIO peripheral Dir Func Signal Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) U3 M8 J7 VDDAUDIOPLL – CLK_AUDIO – – – – – – – – U7 V7 P5 VDDOSC – XIN – – – – – – – – U6 V6 P6 VDDOSC – XOUT – – – – – – – – T7 R8 N5 VDDOSC – VDDOSC – – – – – – – – T6 U5 N6 GNDOSC power GNDOSC I – – – – – – – P8 N8 K7 VDDUTMII power VDDUTMII I – – – – – – – R9 P9 – VDDHSIC power VDDHSIC I – – – – – – – P9 N9 L8 GNDUTMII power GNDUTMII I – – – – – – – T8 U8 N7 VDDUTMII – HHSDPA I – – – – – – – R8 V8 P7 VDDUTMII – HHSDMA – – – – – – – – U8 U9 N8 VDDUTMII – HHSDPB – – – – – – – – U9 V9 P8 VDDUTMII – HHSDMB – – – – – – – – T9 U10 – VDDHSIC – HHSDPDATC – – – – – – – – U10 V10 – VDDHSIC – HHSDMSTRC – – – – – – – P7 P8 M7 VDDUTMIC power VDDUTMIC I – – – – – – – R7 U7 M8 GNDUTMIC power GNDUTMIC I – – – – – – – T10 N10 – VDDSDMMC – SDCAL – – – – – – – – R6 R7 L7 VDDUTMIC – VBG – – – – – – – – P3 P4 M2 VDDBU – TST – – – – – – – – – – – – – – – – (3) U2 V1 N3 VDDBU – T2 V2 L4 VDDBU – JTAGSEL – – – – – – – – P4 R5 P1 VDDBU – WKUP – – – – – – – – N4 U2 – VDDBU – RXD – – – – – – – – R1 U1 N1 VDDBU – SHDN – – – – – – – – R3 R6 K5 VDDBU – PIOBU0 – – – – – – – – N8 R4 L3 VDDBU – PIOBU1 – – – – – – – – R2 – M3 VDDBU – PIOBU2 – – – – – – – – R5 – N4 VDDBU – PIOBU3 – – – – – – – – R4 – L5 VDDBU – PIOBU4 – – – – – – – – P5 – M6 VDDBU – PIOBU5 – – – – – – – – P6 – – VDDBU – PIOBU6 – – – – – – – – M8 – – VDDBU – PIOBU7 – – – – – – – – N7 U3 M4 VDDBU power VDDBU I – – – – – – – N6 U4 M5 GNDBU ground GNDBU I – – – – – – – P1 T2 M1 VDDBU – XIN32 – – – – – – – – P2 R2 L1 VDDBU – XOUT32 – – – – – – – – T1 V3 N2 VDDBU – COMPP I – – – – – – –  2017 Microchip Technology Inc. NRST DS60001476B-page 39 SAMA5D2 SERIES Table 6-2: Pin Description (Continued) 289- 256- 196pin pin pin BGA BGA BGA U1 V4 Primary Alternate Power Rail I/O Type Signal Dir Signal VDDBU – COMPN I – P2 PIO peripheral Dir Func – – Reset State IO (Signal, Dir, PU, Dir Set PD, HiZ, ST)(1)(2) Signal – – – – Note 1: Signal = ‘PIO’ if GPIO; Dir = Direction; PU = Pull-up; PD = Pull-down; HiZ = High impedance; ST = Schmitt Trigger 2: The GPIOs’ reset state is not guaranteed during the powerup phase. During this phase, the GPIOs are in input pullup mode and they take their reset value only after VDDCORE POR reset has been released. If a GPIO must be at level zero at powerup, it is recommended to connect an external pulldown to guarantee this state. 3: For NRST usage, refer to Section 68.5 “Reset and Test”. The SAMA5D23 is not pin-to-pin compatible with SAMA5D21/SAMA5D22. Table 6-3 provides the differences in pinout. Table 6-3: Pin Description (SAMA5D23 pins different from those in Table 6-2 “Pin Description”) Primary Alternate PIO peripheral Dir (Signal, Dir, PU, PD, HiZ, ST)(1)(2) – – – – – – – – – – – – – – B NCS3 O 1 C SPI0_MISO I/O 2 D PWML0 O 1 F CLASSD_L3 O 1 B A21/NANDALE O 1 C SPI0_MOSI I/O 2 D PWMH1 O 1 B NRD/NANDOE O 1 D PWMFI0 I 1 F CLASSD_R1 O 1 A URXD4 I 1 B D8 I/O 1 C IRQ I 3 D PWMEXTRG1 I 1 F CLASSD_R2 O 1 A TCLK2 I 1 B D10 I/O 1 C PWMH2 O 1 D QSPI1_SCK O 2 F GTSUCOMP O 3 Power Rail I/O Type Signal Dir Signal Dir Func Signal N4 GNDBU ground GNDBU I – – – M6 GNDDPLL ground GNDDPLL I – – M3 JTAGSEL – JTAGSEL – – – K11 D6 A6 B6 B5 VDDIOP1 VDDIOP0 VDDIOP0 VDDIOP0 VDDIOP0 DS60001476B-page 40 GPIO GPIO GPIO GPIO GPIO_QSPI PA31 PB0 PB2 PB3 PB5 I/O I/O I/O I/O I/O – – – – – Reset State IO Set 196-pin BGA – – – – – PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST PIO, I, PU, ST  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 6-3: Pin Description (SAMA5D23 pins different from those in Table 6-2 “Pin Description”) Primary 196-pin BGA M12 Power Rail VDDIOP1 M13 VDDIOP1 I/O Type GPIO GPIO Signal PC0 PC1 Alternate Dir I/O I/O Signal – – PIO peripheral Dir – Reset State Func Signal Dir IO Set A LCDDAT21 O 1 B A23 O 1 FLEXCOM0_IO4 O 1 C D TWCK0 I/O 1 F ISC_D6 I 3 A LCDDAT22 O 1 B A24 O 1 C CANTX0 O 1 D SPI1_SPCK I/O 1 E I2SC0_CK I/O 1 F ISC_D7 I 3 – (Signal, Dir, PU, PD, HiZ, ST)(1)(2) PIO, I, PU, ST PIO, I, PU, ST L4 VDDBU – PIOBU1 – – – – – – – – L3 VDDBU – PIOBU2 – – – – – – – – M5 VDDBU – PIOBU3 – – – – – – – – L6 VDDBU – PIOBU5 – – – – – – – – P13 VDDFUSE power VDDFUSE I – – – – – – – Note 1: Signal = ‘PIO’ if GPIO; Dir = Direction; PB/CU = Pull-up; PD = Pull-down; HiZ = High impedance; ST = Schmitt Trigger 2: The GPIOs’ reset state is not guaranteed during the powerup phase. During this phase, the GPIOs are in input pullup mode and they take their reset value only after VDDCORE POR reset has been released. If a GPIO must be at level zero at powerup, it is recommended to connect an external pulldown to guarantee this state. The SAMA5D28B/C are not pin-to-pin compatible with SAMA5D28A, SAMA5D26A/B/C and SAMA5D27A/B/C. Table 6-4 provides the differences in pinout. Table 6-4: Pin Description (SAMA5D28B/C pins different from those in Table 6-2 “Pin Description”) Primary Alternate PIO peripheral Reset State Dir IO Set (Signal, Dir, PU, PD, HiZ, ST)(1)(2) – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – PIOBU3 – – – – – – – – – PIOBU4 – – – – – – – – VDDBU – PIOBU5 – – – – – – – – N7 VDDBU – PIOBU6 – – – – – – – – M5 VDDBU – PIOBU7 – – – – – – – – R3 VDDBU power VDDBU I – – – – – – – R4 GNDBU ground GNDBU I – – – – – – – 289-pin BGA Power Rail I/O Type Signal Dir Signal Dir Func Signal P4 VDDCORE power VDDCORE I – – – N5 GNDCORE ground GNDCORE I – – R2 VDDBU – WKUP – – N6 VDDBU – PIOBU0 – M8 VDDBU – PIOBU2 P6 VDDBU – P5 VDDBU R5  2017 Microchip Technology Inc. DS60001476B-page 41 SAMA5D2 SERIES Note 1: Signal = ‘PIO’ if GPIO; Dir = Direction; PU = Pull-up; PD = Pull-down; HiZ = High impedance; ST = Schmitt Trigger 2: The GPIOs’ reset state is not guaranteed during the powerup phase. During this phase, the GPIOs are in input pullup mode and they take their reset value only after VDDCORE POR reset has been released. If a GPIO must be at level zero at powerup, it is recommended to connect an external pulldown to guarantee this state. DS60001476B-page 42  2017 Microchip Technology Inc. SAMA5D2 SERIES 7. Power Considerations 7.1 Power Supplies Table 7-1: SAMA5D2 Power Supplies Name Voltage Range, Nominal Associated Ground VDDCORE 1.10V – 1.32V, 1.20V GNDCORE Core, including the processor, the embedded memories and the peripherals VDDPLLA 1.10V – 1.32V, 1.20V GNDPLLA PLLA Cell VDDUTMIC 1.10V – 1.32V, 1.20V GNDUTMII USB device and host UTMI+ core VDDHSIC 1.10V – 1.30V, 1.20V GNDUTMII USB High-Speed Inter-Chip 1.70V – 1.90V, 1.80V VDDIODDR 1.14V – 1.30V, 1.20V 1.29V – 1.45V, 1.35V Powers LPDDR1 / DDR2 Interface I/O lines GNDIODDR 1.43V – 1.57V, 1.50V LPDDR2 / LPDDR3 Interface I/O lines DDR3L Interface I/O lines DDR3 Interface I/O lines VDDIOP0 1.65V – 3.60V GNDIOP0 Peripheral I/O lines VDDIOP1 1.65V – 3.60V GNDIOP1 Peripheral I/O lines VDDIOP2 1.65V – 3.60V GNDIOP2 Peripheral I/O lines VDDISC 1.65V – 3.60V GNDISC Image Sensor I/O lines VDDSDMMC 1.65V – 3.60V GNDSDMMC SDMMC I/O lines VDDUTMII 3.00V – 3.60V, 3.30V GNDUTMII USB device and host UTMI+ interface VDDOSC 1.65V – 3.60V GNDOSC Main Oscillator Cell and PLL UTMI. If PLL UTMI or USB is used, the range is restricted to 3.00V–3.60V VDDAUDIOPLL 3.00V – 3.60V, 3.30V VDDANA 1.65V – 3.60V, 3.30V GNDANA VDD Analog VDDFUSE 2.25V – 2.75V, 2.50V GNDFUSE Fuse box for programming. It can be tied to ground with a 100 Ω resistor for fuse reading only. It must be powered for fuse programming and to switch to Secure Mode. VDDBU 1.65V – 3.60V GNDBU Slow Clock Oscillator, the internal 64-kHz RC Oscillator and a part of the System Controller 7.2 GNDAUDIOPLL GNDDPLL Audio PLL Powerup Considerations At powerup, from a supply sequencing perspective, the SAMA5D2 power supply inputs are categorized into two groups: • Group 1 (core group) contains VDDCORE, VDDUTMIC, VDDHSIC and VDDPLLA. • Group 2 (periphery group) contains all other power supply inputs except VDDFUSE. Figure 7-1 shows the recommended powerup sequence. Note that: • VDDBU, when supplied from a battery, is an always-on supply input and is therefore not part of the power supply sequencing. When no backup battery is present in the application, VDDBU is part of Group 2. • VDDFUSE is the only power supply that may be left unpowered during operation. This is possible if and only if the application does not access the Customer Fuse Matrix in Write mode. It is good practice to turn on VDDFUSE only when the Customer Fuse Matrix is accessed in Write mode, and to turn off VDDFUSE otherwise. • VDDIODDR may be nominally supplied at 1.2V when the SAMA5D2 device is equipped with an LPDDR2 or LPDDR3 memory. In this case, VDDIODDR can be considered as part of Group 1.  2017 Microchip Technology Inc. DS60001476B-page 43 SAMA5D2 SERIES Figure 7-1: Recommended Powerup Sequence Group 2 No specific order and no specific timing required among these channels VDDBU VDDANA VDDOSC VDDUTMII VDDAUDIOPLL VDDIOP0 VDDIOP1 VDDIOP2 VDDISC VDDSDMMC VDDIODDR VDDFUSE VDDCORE t3 Group 1 t1 VDDPLLA VDDHSIC VDDUTMIC t2 NRST tRSTPU time Table 7-2: Symbol Powerup Timing Specification Parameter Conditions (1) supply to the Min Max 0 – t1 Group 2 to Group 1 delay Delay from the last Group 2 established first Group1 supply turn-on t2 Group 1 delay(2) Delay from the first group 1 established supply to the last Group 1 established supply – 1 t3 VDDFUSE to VDDBU delay Delay from VDDBU established to VDDFUSE turn-on 1 – Reset delay at powerup From the last established supply to NRST high 1 – tRSTPU Unit ms Note 1: An “established” supply refers to a power supply established at 90% of its final value. 2: Also applies to VDDIODDR when considered as part of Group 1. DS60001476B-page 44  2017 Microchip Technology Inc. SAMA5D2 SERIES 7.3 Powerdown Considerations Figure 7-2 shows the SAMA5D2 powerdown sequence that starts by asserting the NRST line to 0. Once NRST is asserted, the supply inputs can be immediately shutdown without any specific timing or order. VDDBU may not be shutdown if the application uses a backup battery on this supply input. In applications where VDDFUSE is powered, it is mandatory to shutdown VDDFUSE prior to removing any other supply. VDDFUSE can be removed before or after asserting the NRST signal. Figure 7-2: Recommended Powerdown Sequence tRSTPD NRST No specific order and no specific timing required among the channels VDDBU VDDANA VDDOSC VDDUTMII VDDAUDIOPLL VDDIOP0 VDDIOP1 VDDIOP2 VDDISC VDDSDMMC VDDIODDR t1 VDDFUSE VDDCORE VDDPLLA VDDHSIC VDDUTMIC time Table 7-3: Symbol tRSTPD t1 7.4 7.4.1 Powerdown Timing Specification Parameter Conditions Min Max Reset delay at powerdown From NRST low to the first supply turn-off 0 – VDDFUSE delay at shutdown From VDDFUSE < 1V to the first supply turn-off 0 – Unit ms Power Supply Sequencing at Backup Mode Entry and Exit VDDBU Power Architecture The backup power switch aims at optimizing the power consumption on VDDBU source by switching the supply of the backup digital part (BUREG memories + 64-kHz RC oscillator) to VDDANA. When enabled, the backup power source can be automatically switched to VDDANA, which reduces power consumption on VDDBU. Then, VDDBU powers the pads, VDDBU POR, 32-kHz crystal and, on secure products SAMA5D23 and SAMA5D28, the temperature sensor and the backup supply monitor. The power source (VDDANA or VDDBU) can be selected manually or can be set to work automatically by programming an SFRBU register (refer to SFRBU_PSWBUCTRL in Section 20. “Special Function Registers Backup (SFRBU)”).  2017 Microchip Technology Inc. DS60001476B-page 45 SAMA5D2 SERIES 7.4.2 Backup Mode Entry Figure 7-3 shows the recommended power down sequence to place the SAMA5D2 either in Backup mode or in Backup mode with its DDR in self-refresh. The SHDN signal, output of Shutdown Controller (SHDWC), signals the shutdown request to the power supply. This output is supplied by VDDBU that is present in Backup mode. Placing the external DDR memory in self-refresh while in Backup mode, requires to maintain also VDDIODDR. One possible way to signal this additional need to the power supply is to position one of the general purpose I/Os supplied by VDDBU (PIOBUx) in a predefined state. Figure 7-3: Recommended Backup Mode Entry Shutdown Request in SHDWC tRSTPD SHDN PIOBUx NRST VDDBU VDDANA PIOBUx signals to maintain or shutdown VDDIODDR VDDOSC No specific order and no specific timing required among the channels VDDUTMII VDDAUDIOPLL VDDIOP0 VDDIOP1 VDDIOP2 VDDISC VDDSDMMC VDDFUSE VDDIODDR VDDCORE VDDPLLA VDDHSIC VDDUTMIC time Table 7-4: Powerdown Timing Specification Symbol Parameter Conditions tRSTPD Reset delay at powerdown From NRST low to the first supply turn-off DS60001476B-page 46 Min Max Unit 0 – ms  2017 Microchip Technology Inc. SAMA5D2 SERIES 7.4.3 Backup Mode Exit (Wakeup) Figure 7-4 shows the recommended powerup sequence to wake up SAMA5D2 from Backup mode. Upon a wakeup event, the Shutdown Controller toggles its SHDN output back to VDDBU to request the power supply to restart. Except VDDIODDR which may already be present if the external DDR memory was placed in Self-refresh mode, this powerup sequence is the same as the one of Figure 7-1. In particular, the definitions of Group 1 and Group 2 are the same. Figure 7-4: Recommended Power Supply Sequencing at Wakeup SHDN VDDBU VDDANA VDDOSC Group 2 No specific order and no specific timing required among these channels VDDUTMII VDDAUDIOPLL VDDIOP0 VDDIOP1 VDDIOP2 VDDISC VDDSDMMC VDDFUSE VDDIODDR Group 1 VDDCORE t1 VDDPLLA VDDHSIC VDDUTMIC t2 NRST tRSTPU time Table 7-5: Symbol Powerup Timing Specification Parameter Conditions established(1) Min Max 1 – t1 Group 2 to Group 1 delay Delay from the last Group 2 first Group1 supply turn-on t2 Group 1 delay(2) Delay from the first group 1 established supply to the last Group 1 established supply – 1 tRSTPU Reset delay at powerup From the last established supply to NRST high. 1 – supply to the Unit ms Note 1: An “established” supply refers to a power supply established at 90% of its final value. 2: Also applies to VDDIODDR when considered as part of Group 1.  2017 Microchip Technology Inc. DS60001476B-page 47 SAMA5D2 SERIES 8. Memories Figure 8-1: 0x00000000 Memory Mapping Address memory space 0x00000000 Internal memories 0xF0000000 Internal memories 0x00200000 ICM 63 SYSC 9 0xF8000000 SYSC 33 0xF8004000 43 0xF8008000 0xF800C000 35 +0x80 36 +0x80 TDES 76 0xFC048000 75 0xFC04C000 CLASSD 54 0xFC058000 56;64 0xFC05C000 34 0xFC060000 RESERVED CAN0 SFRBU SPI1 QSPI0 MEM 0xFC004000 44 0xFC008000 0xFC00C000 27 0xFC068000 28 0xFC069000 RESERVED UART4 0xF0000000 58 0xFC064000 RESERVED UART3 QSPI1 MEM 77 PTC SSC1 0xD8000000 57;65 0xFC054000 UTMI I2SC0 0xFC000000 55 CAN1 50 0xF8054000 24 59 0xFC050000 SFC 48 11 I2SC1 0xF8050000 0xF801C000 16 0xFC044000 RESERVED 17 0xF8018000 14 0xFC040000 SECUMOD 0xF804C000 UART0 0xD0000000 +74 0xF804B000 0xF8014000 18 H32MX RTC ACC PDMIC NFC command Register PIOA 0xF804A000 HSMC 32;72 0xFC038000 0xFC03C000 RXLP TC1_CH5 0xC0000000 WDT SCKC SYSCWP TC1_CH4 SDMMC1 RESERVED 0xF8049000 +0x40 40 0xFC034000 SYSC TC1_CH3 31;71 PIT +0xE4 0xF8010000 42 ADC +0xb0 SYSC 30 0xFC030000 4 SYSC TC0_CH2 0xB0000000 SHDWC 3 SYSC TC0_CH1 SDMMC0 0xFC02C000 UDPHS +0x50 +0x40 0xA0000000 +74 TWIHS1 +0x40 GMAC 5;66;67 TC0_CH0 QSPI1 AESB MEM 0xFC028000 +0x30 SYSC 49;62 0xFC024000 51 RSTC +0x10 SPI0 47 0xFC020000 RESERVED SECURAM 0xF8048000 SSC0 0x98000000 8 12 AES 23 0xFC01C000 AIC 0xF8044000 0xF002C000 0x00A00000 Undefined (Abort) QSPI0 AESB MEM 0;61 53 22 0xFC018000 TRNG SAIC SHA L2CC 0x90000000 20 0xF8040000 0xF0028000 PTC 0x0FFFFFFF FLEXCOM1 52 21 FLEXCOM4 0xF803C000 QSPI1 0x00800000 EBI Chip Select 3 19 10 0xF0024000 DAP 0xFC014000 FLEXCOM3 0xF8038000 QSPI0 0x00700000 60 FLEXCOM0 15 0xF0020000 0xFC010000 FLEXCOM2 0xF8034000 AESB UHPHS (EHCI) 0x00C00000 +74 0xF001C000 0x00500000 38 SFR H64MX AXIMX 0x80000000 0xF8030000 0xF0018000 0x00600000 EBI Chip Select 2 PWM 6 PMC UHPHS (OHCI) 0x70000000 29 0xF802C000 XDMAC0 0x00400000 EBI Chip Select 1 TWIHS0 13 0xF0014000 0x00300000 UDPHS (RAM) 0x60000000 26 0xF8028000 MPDDRC 0xF0010000 SRAM1 DDR AESB Chip Select UART2 46 0xF000C000 0x00220000 0x40000000 25 0xF8024000 ISC SRAM0 DDR Chip Select UART1 7 0xF0008000 NFC (SRAM) 0x20000000 0xF8020000 XDMAC1 0x00100000 EBI Chip Select 0 45 0xF0004000 0x00040000 ECC ROM 0x10000000 Internal peripherals LCDC ROM CHIPID Internal peripherals 78 0xFC06A000 RESERVED 0xFFFFFFFF offset block peripheral ID (+ : wired-or) DS60001476B-page 48  2017 Microchip Technology Inc. SAMA5D2 SERIES 8.1 8.1.1 Embedded Memories Internal SRAM The SAMA5D2 embeds a total of 128 Kbytes of high-speed SRAM. After reset, and until the Remap command is performed, the SRAM is accessible at address 0x0020 0000. When the AXI Bus Matrix is remapped, the SRAM is also available at address 0x0. The device features a second 128-Kbyte SRAM that can be allocated either to the L2 cache controller or used as an internal SRAM. After reset, this block is connected to the system SRAM, making the two 128-Kbyte RAMs contiguous. The SRAM_SEL bit, located in the SFR_L2CC_HRAMC register, is used to reassign this memory as a L2 cache memory. 8.1.2 Internal ROM The product embeds one 160-Kbyte secured internal ROM mapped at address 0 after reset. The ROM contains a standard and secure bootloader as well as the BCH (Bose, Chaudhuri and Hocquenghem) code tables for NAND Flash ECC correction. The memory area containing the secure boot is automatically hidden after the execution of the secure boot while the one containing the code tables for ECC remains visible. 8.1.3 Boot Strategies For standard boot strategies, refer to Section 16. “Standard Boot Strategies” of this datasheet. For secure boot strategies, refer to the document “SAMA5D2x Secure Boot Strategy”, document no. 44040 (Non-Disclosure Agreement required). 8.2 External Memory The SAMA5D2 offers connections to a wide range of external memories or to parallel peripherals. 8.2.1 External Bus Interface The External Bus Interface (EBI) is a 16-bit wide interface working at MCK/2. The EBI supports: • Static memories • 8-bit NAND Flash with 32-bit BCH ECC • 16-bit NAND Flash EBI I/Os accept three drive levels (Low, Medium, High) to avoid overshoots and provide the best performances according to the bus load and external memories voltage. The drive levels are configured with the DRVSTR field in the PIO Configuration Register (PIO_CFGRx) if the corresponding line is nonsecure or the Secure PIO Configuration Register (S_PIO_CFGRx) if the I/O line is secure. At reset, the selected drive is low. The user must make sure to program the correct drive according to the device load. The I/O embeds serial resistors for impedance matching. 8.2.2 Supported Memories on DDR2/DDR3/LPDDR1/LPDDR2/LPDDR3 Interface • • • • • • • • 16-bit or 32-bit external interface 512 Mbytes of address space on DDR CS and DDR/AES CS in 32-bit mode 256 Mbytes of address space on DDR CS and DDR/AES CS in 16-bit mode Supports 16-bit or 32-bit 8-bank DDR2, DDR3, LPDDR1, LPDDR2 and LPDDR3 memories Automatic drive level control Multiport Scramblable data path Port 0 of this interface has an embedded automatic AES encryption and decryption mechanism (refer to Section 59. “Advanced Encryption Standard Bridge (AESB)”). Writing to or reading from the address 0x40000000 may trigger the encryption and decryption mechanism depending on the AESB on External Memories configuration. • TrustZone: The multiport feature of this interface implies TrustZone configuration constraints. Refer to Section 18.12 “TrustZone Extension to AHB and APB” for more details. 8.2.3 Supported Memories on Static Memories and NAND Flash Interfaces The Static Memory Controller is dedicated to interfacing external memory devices: • Asynchronous SRAM-like memories and parallel peripherals  2017 Microchip Technology Inc. DS60001476B-page 49 SAMA5D2 SERIES • NAND Flash (MLC and SLC) 8-bit datapath The Static Memory Controller is able to drive up to four chip select. NCS3 is dedicated to the NAND Flash control. The HSMC embeds a NAND Flash Controller (NFC). The NFC can handle automatic transfers, sending the commands and address cycles to the NAND Flash and transferring the contents of the page (for read and write) to the NFC SRAM. It minimizes the processor overhead. In order to improve overall system performance, the DATA phase of the transfer can be DMA-assisted. The static memory embeds the NAND Flash Error Correcting Code controller with the following features: • Algorithm based on BCH codes • Supports also SLC 1-bit (BCH 2-bit), SLC 4-bit (BCH 4-bit) • Programmable Error Correcting Capability - 2-bit, 4-bit, 8-bit and 16-bit errors for 512 bytes/sector (4-Kbyte page) - 24-bit error for 1024 bytes/sector (8-Kbyte page) • Programmable sector size: 512 bytes or 1024 bytes • Programmable number of sectors per page: 1, 2, 4 or 8 blocks of data per page • Programmable spare area size • Supports spare area ECC protection • Supports 8-Kbyte page size using 1024 bytes/sector and 4-Kbyte page size using 512 bytes/sector • Error detection is interrupt-driven • Provides hardware acceleration for error location • Finds roots of error-locator polynomial • Programmable number of roots 8.2.4 DDR and SDMMC I/Os Calibration 8.2.4.1 DDR I/O Calibration The DDR2/DDR3/LPDDR1/LPDDR2/LPDDR3/DDR3L I/Os embed an automatic impedance matching control to avoid overshoots and reach the best performance levels depending on the bus load and external memories. A serial termination connection scheme, where the driver has an output impedance matched to the characteristic impedance of the line, is used to improve signal quality and reduce EMI. One specific analog input, DDR_CAL, is used to calibrate all DDR / IOs. The MPDDRC supports the ZQ calibration procedure used to calibrate the SAMA5D2 DDR I/O drive strength and the commands to setup the external DDR device drive strength (refer to Section 36. “Multiport DDR-SDRAM Controller (MPDDRC)”). The calibration cell supports all the memory types listed above. Figure 8-2: DDR Calibration Cell CAL_CTRL DDR_CAL CALCODEN/CALCODEP Calibration Cell RZQ MPDDRC CZQ cal_nmos cal_pmos drive DDR I/O PCB Trace DDR Memory DDR I/O PCB Trace The calibration cell provides an input pin, DDR_CAL, loaded with one of the following resistor RZQ values: DS60001476B-page 50  2017 Microchip Technology Inc. SAMA5D2 SERIES - 24 KΩ for LPDDR2/LPDDR3 23 KΩ for DDR3L 22 KΩ for DDR3 21 KΩ for DDR2/LPDDR1 The typical value for CZQ is 22 pF. • LPDDR2 Power Fail Management The DDR controller (MPDDRC) is used to manage the LPDDR memory when an uncontrolled power off occurs. The DDR power rail must be monitored externally and generate an interrupt when a power fail condition is triggered. The interrupt handler must apply the sequence defined in the MPDDRC Low-power register (MPDDRC_LPR) by setting bit LPDDR2_PWOFF (LPDDR2 Power Off bit). 8.2.4.2 SDMMC I/O Calibration The SAMA5D2 also embeds an SDMMC I/O calibration cell. The purpose of this block is to provide to e.MMC/SD I/Os an output impedance reference to limit the impact of process, voltage and temperature on the drivers output impedance. The impedance control is required at high frequency in order to improve signal quality. The control and procedure to setup the SDMMC calibration cell is described in Section 51. “Secure Digital MultiMedia Card Controller (SDMMC)”. Figure 8-3: SDMMC I/O Calibration Cell SDCAL CAL_CTRL Calibration Cell RZQ SDMMC CZQ cal_nmos cal_pmos drive SDMMC I/O PCB Trace SD/MMC Memory SDMMC I/O PCB Trace The calibration cell provides an input pin SDCAL loaded with a 20 KΩ resistor for 1.8V memories and a 16.9 KΩ resistor for 3.3V memories. According to the e.MMC specification, the output impedance calibration is mandatory for HS200 mode (1.8V) when it is not for other modes (3.3V). In addition, according to the SD specification, the output impedance calibration is mandatory for 1.8V signaling when it is not for 3.3V signaling. Thus, the calibration cell design is oriented to get the highest accuracy under 1.8V. In case of interfacing which would need to operate under both 1.8V and 3.3V, external devices RZQ and CZQ must get values related to the 1.8V mode. The typical value for CZQ is 22 pF.  2017 Microchip Technology Inc. DS60001476B-page 51 SAMA5D2 SERIES 9. Event System The events generated by peripherals are designed to be directly routed to peripherals managing/using these events without processor intervention. Peripherals receiving events contain logic by which to select the one required. 9.1 Real-time Event List • Timers, PWM, IO peripherals generate event triggers which are directly routed to event managers such as ADC, for example, to start measurement/conversion without processor intervention. • ADC is connected to nine trigger inputs defined as two groups: - One group of eight elements for Timer Counter (TC0 to TC4), ADTRIG and PMW0 event0, PWM0 event1 - One group of one element for low-rate trigger, RTC • UART, USART, SPI, TWI, PWM, CLASSD, AES, SHA, ADC, PIO, TIMER (Capture mode) generate event triggers directly connected to DMA controllers (XDMAC) for data transfer without processor intervention. • PWM safety events (faults) are in combinational form and directly routed from event generators (ADC, ACC, PMC, TIMER) to the PWM module. • PWM receives external triggers to provide PFC, DC/DC functions. • PWM output comparators generate events directly connected to TIMER. • PMC safety event (clock failure detection) can be programmed to switch the MCK on a reliable main RC internal clock without processor intervention. DS60001476B-page 52  2017 Microchip Technology Inc. SAMA5D2 SERIES 9.2 Real-time Event Mapping Table 9-1: Function Safety Real-time Event Mapping List Application Description General-purpose Automatic switch to reliable main RC oscillator in case of main crystal clock failure(1) General-purpose, motor control, power factor correction (PFC) Puts the PWM outputs in Safe mode (main crystal clock failure detection)(1)(2) Motor control, PFC Puts the PWM outputs in Safe mode (overspeed, overcurrent detection, etc.)(2)(3) Motor control Puts the PWM outputs in Safe mode (overspeed detection through TIMER quadrature decoder)(2)(4) General-purpose Puts the PWM outputs in Safe mode (general-purpose fault inputs)(2) General-purpose Programmable delay in PWM(7) Event Source Event Destination PMC Power Management Controller (PMC) ADC PWM Timer Counter Block (TC 0, 1, 2) Timer Counter Block (TC 3, 4, 5) 2 IOs (PWM_Flx) PWM Event Line 0 PWM Event Line 1 IO (ADC_ADTRG) TC Output 0 Measurement trigger General-purpose ADC TC Output 1 Trigger source selection in ADC(5) TC Output 2 TC Output 3 General-purpose GTSUCOMP synchronous clock generation trigger Delay measurement Audio Motor control Low-speed TC Output 4 RTCOUT0 RTC RTCOUT1 GMAC GTSUCOMP Line TC5 PWM Compare Line 0 TC Input (A/B) 0 PWM Compare Line 1 TC Input (A/B) 1 PWM Compare Line 2 TC Input (A/B) 2 measurement(6) Trigger source selection in TC Delay measurement between PWM outputs and TC inputs externally connected to power transistor bridge driver.(8)(9) Note 1: Refer to Section 33.17 “Main Crystal Oscillator Failure Detection”. 2: Refer to Section 56.5.4 “Fault Inputs” and Section 56.6.2.7 “Fault Protection”. 3: Refer to Section 65.5.5 “Fault Output”. 4: Refer to Section 54.6.18 “Fault Mode”. 5: Refer to Section 65.7.25 “ADC Trigger Register”. 6: Refer to Section 26.5.8 “Waveform Generation”. 7: Refer to Section 56.6.3 “PWM Comparison Units” and Section 56.6.4 “PWM Event Lines”. 8: Refer to Section 54.6.14 “Synchronization with PWM”. 9: Refer to Section 56.6.2.2 “Comparator”.  2017 Microchip Technology Inc. DS60001476B-page 53 SAMA5D2 SERIES 10. System Controller The system controller is a set of peripherals handling key elements of the system, such as power, resets, clocks, time, interrupts, watchdog, etc. The system controller’s peripherals are all mapped between addresses 0xF8049000 and 0xF8048000. Figure 10-1 shows the system controller block diagram. DS60001476B-page 54  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 10-1: System Controller Block Diagram FIQ VDDCORE Powered Secured Advanced Interrupt Controller secure_peripheral_irq[] irq[23] nfiq CA5_wakeup pmc_irq nirq IRQ Cortex-A5 Advanced Interrupt Controller nonsecure_peripheral_irq[] pit_irq wdt_irq ntrst proc_nreset PCK VDDCORE MCK debug periph_nreset SLCK debug idle proc_nreset Periodic Interval Timer pit_irq Watchdog Timer wdt_irq debug jtag_nreset Boundary Scan TAP Controller MCK wdt_fault Bus Matrix periph_nreset NRST por_ntrst jtag_nreset VDDCORE POR Reset Controller periph_nreset proc_nreset backup_nreset UPLLCK VDDBU Powered VDDBU POR SLCK UHP48M UHP12M SLCK Real-time Clock backup_nreset rtc_irq rtc_alarm periph_nreset USB High Speed Host Port periph_irq[41] VDDBU Security Module ntrst Tamper Detection PIOBU[7..0] irq[16] UPLLCK debug MCK Protection Manager 12 MHz RC 64 kHz RC wkup (to PMC) Secure Memories periph_nreset USB High Speed Device Port periph_irq[42] RXD COMPP COMPN RXLP RXLP_wkup (to PMC) ACC ACC_wkup (to PMC) SLCK SHDN WKUP Shutdown Controller DDR_BUMEN backup_nreset DDR sysclk rtc_alarm XIN32 XOUT32 32.768 kHz Crystal Oscillator MPDDRC periph_clk[13] 64 kHz RC Oscillator SFRBU DDR_BUMEN SCKC_CR SLCK XIN XOUT periph_clk[id] 8–24 MHz Main Oscillator MAINCK 12 MHz RC Oscillator PLLACK PLLA Power Management Controller UPLLCK UPLL pck[0–2] UHP48M UHP12M UPLLCK GCLK PCK MCK DDR sysclk LCD Pixel clock pmc_irq idle CA5_wakeup int periph_nreset RXLP, ACC, SBM wkup PA0–PA31 PB0–PB31 PC0–PC31 PD0–PD31  2017 Microchip Technology Inc. periph_clk[id] periph_nreset periph_nreset periph_irq[70, 69, 68, 18] periph_clk[id] irq PIO Controllers Embedded Peripherals periph_irq[id] fiq in out enable DS60001476B-page 55 SAMA5D2 SERIES 10.1 Power-On Reset The SAMA5D2 embeds several Power-On Resets (PORs) to ensure the power supply is established when the reset is released. These PORs are dedicated to monitoring VDDBU, VDDIOP and VDDCORE respectively. DS60001476B-page 56  2017 Microchip Technology Inc. SAMA5D2 SERIES 11. Peripherals 11.1 Peripheral Mapping As shown in Figure 8-1. Memory Mapping, the peripherals are mapped in the upper 256 Mbytes of the address space, between addresses 0xF000 0000 and 0xFFFC 0000. 11.2 Peripheral Identifiers Table 11-1: Peripheral Identifiers PMC Internal Clock Interrupt Control Instance Description Instance ID Instance Name Clock Type Security(2) In Matrix 0 SAIC FIQ – FIQ Interrupt ID SYS_CLK_LS AS – 1 – – – – – – – 2 ARM PMU X Performance Monitor Unit (PMU) PROC_CLK PS H64MX 3 PIT X – Periodic Interval Timer Interrupt SYS_CLK_LS PS H32MX 4 WDT X – Watchdog Timer Interrupt SYS_CLK_LS PS H32MX 5 GMAC X X Ethernet MAC HCLOCK_LS PCLOCK_LS PS H32MX 6 XDMAC0 X X DMA Controller 0 HCLOCK_HS PS H64MX 7 XDMAC1 X X DMA Controller 1 HCLOCK_HS PS H64MX 8 ICM X X Integrity Check Monitor HCLOCK_LS PS H32MX 9 AES X X Advanced Encryption Standard PCLK_HS PS H64MX 10 AESB X X AES Bridge HCLOCK_HS PS H64MX 11 TDES X X Triple Data Encryption Standard PCLOCK_LS PS H32MX 12 SHA X X SHA Signature PCLK_HS PS H64MX 13 MPDDRC X X MPDDR Controller HCLOCK_HS PS H64MX 14 H32MX X X 32-bit AHB Matrix SYS_CLK_LS AS – 15 H64MX X X 64-bit AHB Matrix SYS_CLOCK AS – 16 SECUMOD X X Security Module SLOW_CLOCK AS H32MX 17 HSMC X X Multibit ECC Interrupt HCLOCK_LS PS H32MX 18 PIOA X X Parallel I/O Controller PCLOCK_LS AS H32MX 19 FLEXCOM0 X X FLEXCOM 0 PCLOCK_LS PS H32MX 20 FLEXCOM1 X X FLEXCOM 1 PCLOCK_LS PS H32MX 21 FLEXCOM2 X X FLEXCOM 2 PCLOCK_LS PS H32MX 22 FLEXCOM3 X X FLEXCOM 3 PCLOCK_LS PS H32MX 23 FLEXCOM4 X X FLEXCOM 4 PCLOCK_LS PS H32MX 24 UART0 X X Universal Asynchronous Receiver Transmitter 0 PCLOCK_LS PS H32MX 25 UART1 X X Universal Asynchronous Receiver Transmitter 1 PCLOCK_LS PS H32MX  2017 Microchip Technology Inc. DS60001476B-page 57 SAMA5D2 SERIES Table 11-1: Peripheral Identifiers (Continued) PMC Internal Clock Interrupt Control Instance Description Instance ID Instance Name Clock Type Security(2) In Matrix 26 UART2 X X Universal Asynchronous Receiver Transmitter 2 PCLOCK_LS PS H32MX 27 UART3 X X Universal Asynchronous Receiver Transmitter 3 PCLOCK_LS PS H32MX 28 UART4 X X Universal Asynchronous Receiver Transmitter 4 PCLOCK_LS PS H32MX 29 TWIHS0 X X Two-Wire Interface 0 PCLOCK_LS PS H32MX 30 TWIHS1 X X Two-Wire Interface 1 PCLOCK_LS PS H32MX 31 SDMMC0 X X Secure Digital MultiMedia Card Controller 0 HCLOCK_HS PS H64MX 32 SDMMC1 X X Secure Digital MultiMedia Card Controller 1 HCLOCK_HS PS H64MX 33 SPI0 X X Serial Peripheral Interface 0 PCLOCK_LS PS H32MX 34 SPI1 X X Serial Peripheral Interface 1 PCLOCK_LS PS H32MX 35 TC0 X X Timer Counter 0 (ch. 0, 1, 2) PCLOCK_LS PS H32MX 36 TC1 X X Timer Counter 1 (ch. 3, 4, 5) PCLOCK_LS PS H32MX 37 – – – – – – – 38 PWM X X Pulse Width Modulation Controller 0 (ch. 0, 1, 2, 3) PCLOCK_LS PS H32MX 39 – – – – – – – 40 ADC X X Touchscreen ADC Controller PCLOCK_LS PS H32MX 41 UHPHS X X USB Host High-Speed HCLOCK_LS PS H32MX 42 UDPHS X X USB Device High-Speed HCLOCK_LS PS H32MX 43 SSC0 X X Synchronous Serial Controller 0 PCLOCK_LS PS H32MX 44 SSC1 X X Synchronous Serial Controller 1 PCLOCK_LS PS H32MX 45 LCDC X X LCD Controller HCLOCK_HS PS H64MX 46 ISC X X Image Sensor Controller HCLOCK_HS PS H64MX 47 TRNG X X True Random Number Generator PCLOCK_LS PS H32MX 48 PDMIC X X Pulse Density Modulation Interface Controller PCLOCK_LS PS H32MX 49 AIC IRQ – IRQ Interrupt ID SYS_CLK_LS NS H32MX 50 SFC X X Secure Fuse Controller PCLOCK_LS PS H32MX 51 SECURAM X X Secured RAM PCLOCK_LS AS H32MX 52 QSPI0 X X Quad SPI Interface 0 HCLOCK_HS PS H64MX 53 QSPI1 X X Quad SPI Interface 1 HCLOCK_HS PS H64MX 54 I2SC0 X X Inter-IC Sound Controller 0 PCLOCK_LS PS H32MX 55 I2SC1 X X Inter-IC Sound Controller 1 PCLOCK_LS PS H32MX 56 MCAN0 INT0 X MCAN 0 Interrupt0 HCLOCK_LS PS H32MX 57 MCAN1 INT0 X MCAN 1 Interrupt0 HCLOCK_LS PS H32MX DS60001476B-page 58  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 11-1: Peripheral Identifiers (Continued) PMC Internal Clock Interrupt Control Instance Description Instance ID Instance Name 58 PTC X X 59 CLASSD X X 60 61 SFR SAIC – – – – Clock Type Security(2) In Matrix Peripheral Touch Controller PCLOCK_LS PS H32MX Audio Class D Amplifier PCLOCK_LS PS H32MX SYS_CLK_LS PS H32MX SYS_CLK_LS AS H32MX SYS_CLK_LS NS H32MX Special Function Register (2) Secured Advanced Interrupt Controller (2) (2) 62 AIC – – Advanced Interrupt Controller 63 L2CC X – L2 Cache Controller – PS H64MX 64 MCAN0 INT1 – MCAN 0 Interrupt1 – PS H32MX 65 MCAN1 INT1 – MCAN 1 Interrupt1 – PS H32MX 66 GMAC Q1 – GMAC Queue 1 Interrupt – PS H32MX 67 GMAC Q2 – GMAC Queue 2 Interrupt – PS H32MX 68 PIOB X – – – AS H32MX 69 PIOC X – – – AS H32MX 70 PIOD X – – – AS H32MX 71 SDMMC0 TIMER – – – PS H32MX 72 SDMMC1 TIMER – – – PS H32MX 73 – – – – – – – 74 PMC, RTC, RSTC X – System Controller Interrupt SYS_CLK_LS PS H32MX 75 ACC X – Analog Comparator SYS_CLK_LS PS H32MX 76 RXLP X – UART Low-Power SYS_CLK_LS PS H32MX – PS H32MX – PS H32MX 77 SFRBU – – Special Function Register Backup 78 CHIPID – – Chip ID (2) Note 1: AS = Always Secure; PS = Programmable Secure; NS = Never Secure 2: For security purposes, there is no matching clock but a peripheral ID only. 11.3 Peripheral Signal Multiplexing on I/O Lines The SAMA5D2 features several PIO Controllers that multiplex the I/O lines of the peripheral set. Table 6-2 “Pin Description” defines how the I/O lines are multiplexed on the different PIO Controllers. Several I/O sets are available for each peripheral. However, selecting I/Os from different I/O sets for one peripheral is prohibited. The column “Reset State” shows whether the PIO line resets in I/O mode or in Peripheral mode. If I/O is shown, the PIO line resets in input with the pull-up enabled, so that the device is maintained in a static state as soon as the reset is released. As a result, the bit corresponding to the PIO line in register PIO_CFGR (PIO Configuration Register) resets low. If a signal name is shown in the “Reset State” column, the PIO line is assigned to this function and the corresponding bit in PIO_CFGR resets high. That is the case for pins controlling memories, in particular address lines, which require the pin to be driven as soon as the reset is released. The PIO state can be retained when the system enters in Backup mode.  2017 Microchip Technology Inc. DS60001476B-page 59 SAMA5D2 SERIES 11.4 Peripheral Clock Types Table 11-2 lists the clock types available on embedded peripherals in SAMA5D2. Clock type suffixes HS and LS refer to Matrix (H64MX) and Matrix (H32MX), respectively. See Table 11-1 “Peripheral Identifiers” for details on embedded peripherals. Table 11-2: Peripheral Clock Types Clock Type HCLOCK_HS HCLOCK_LS PCLOCK_HS Description AHB Clock. Managed with the PMC_PCER, PMC_PCDR, PMC_PCSR and PMC_PCR registers of Peripheral Clock.(1) APB Clock. PCLOCK_LS Managed with the PMC_PCER, PMC_PCDR, PMC_PCSR and PMC_PCR registers of Peripheral Clock. (1) SYS_CLK_LS This clock cannot be disabled. (2) SYS_CLOCK This clock cannot be disabled. (2) PROC_CLK The clock related to Processor Clock (PCK) and managed with the PMC_SCDR and PMC_SCSR registers of PMC System Clock SLOW_CLOCK The clock related to the backup area and the RTC and managed with the SCKC_CR. This clock can be generated either by an external 32.768 kHz crystal oscillator or by the on-chip 64 kHz RC oscillator. Note 1: Refer to Figure 33-1. General Clock Block Diagram in Section 33. “Power Management Controller (PMC)”. 2: Refer to the MC2 clock in Figure 33-1. General Clock Block Diagram. DS60001476B-page 60  2017 Microchip Technology Inc. SAMA5D2 SERIES 12. Chip Identifier (CHIPID) 12.1 Description Chip Identifier (CHIPID) registers are used to recognize the device and its revision. These registers provide the sizes and types of the onchip memories, as well as the set of embedded peripherals. Two CHIPID registers are embedded: Chip ID Register (CHIPID_CIDR) and Chip ID Extension Register (CHIPID_EXID). Both registers contain a hard-wired value that is read-only. The CHIPID_CIDR register contains the following fields: • • • • • • VERSION: Identifies the revision of the silicon EPROC: Indicates the embedded ARM processor NVPTYP and NVPSIZ: Identify the type of embedded non-volatile memory and the size SRAMSIZ: Indicates the size of the embedded SRAM ARCH: Identifies the set of embedded peripherals EXT: Shows the use of the extension identifier register The CHIPID_EXID register is device-dependent and reads 0 if CHIPID_CIDR.EXT = 0. 12.2 Embedded Characteristics • Chip ID Registers - Identification of the Device Revision, Sizes of the Embedded Memories, Set of Peripherals, Embedded Processor Table 12-1: SAMA5D2 Chip ID Registers Chip Name CHIPID_CIDR CHIPID_EXID ATSAMA5D22A-CU 0x8A5C08C0 0x00000059 ATSAMA5D24A-CU 0x8A5C08C0 0x00000014 ATSAMA5D27A-CU 0x8A5C08C0 0x00000011 ATSAMA5D28A-CU 0x8A5C08C0 0x00000010 ATSAMA5D21B-CU 0x8A5C08C1 0x0000005A ATSAMA5D22B-CN 0x8A5C08C1 0x00000069 ATSAMA5D22B-CU 0x8A5C08C1 0x00000059 ATSAMA5D23B-CN 0x8A5C08C1 0x00000068 ATSAMA5D23B-CU 0x8A5C08C1 0x00000058 ATSAMA5D24B-CU 0x8A5C08C1 0x00000014 ATSAMA5D26B-CN 0x8A5C08C1 0x00000022 ATSAMA5D26B-CU 0x8A5C08C1 0x00000012 ATSAMA5D27B-CN 0x8A5C08C1 0x00000021 ATSAMA5D27B-CU 0x8A5C08C1 0x00000011 ATSAMA5D28B-CN 0x8A5C08C1 0x00000020 ATSAMA5D28B-CU 0x8A5C08C1 0x00000010 ATSAMA5D21C-CU 0x8A5C08C2 0x0000005A ATSAMA5D22C-CN 0x8A5C08C2 0x00000069 ATSAMA5D22C-CU 0x8A5C08C2 0x00000059 ATSAMA5D23C-CN 0x8A5C08C2 0x00000068  2017 Microchip Technology Inc. DS60001476B-page 61 SAMA5D2 SERIES Table 12-1: SAMA5D2 Chip ID Registers (Continued) Chip Name CHIPID_CIDR CHIPID_EXID ATSAMA5D23C-CU 0x8A5C08C2 0x00000058 ATSAMA5D24C-CU 0x8A5C08C2 0x00000014 ATSAMA5D26C-CN 0x8A5C08C2 0x00000022 ATSAMA5D26C-CU 0x8A5C08C2 0x00000012 ATSAMA5D27C-CN 0x8A5C08C2 0x00000021 ATSAMA5D27C-CU 0x8A5C08C2 0x00000011 ATSAMA5D28C-CN 0x8A5C08C2 0x00000020 ATSAMA5D28C-CU 0x8A5C08C2 0x00000010 DS60001476B-page 62  2017 Microchip Technology Inc. SAMA5D2 SERIES 12.3 Chip Identifier (CHIPID) User Interface Table 12-2: Offset Register Mapping Register Name 0x0 Chip ID Register 0x4 Chip ID Extension Register  2017 Microchip Technology Inc. Access Reset CHIPID_CIDR Read-only – CHIPID_EXID Read-only – DS60001476B-page 63 SAMA5D2 SERIES 12.3.1 Chip ID Register Name: CHIPID_CIDR Address: 0xFC069000 Access: Read-only 31 EXT 30 23 22 29 NVPTYP 28 21 20 27 26 19 18 ARCH 15 14 13 6 EPROC 24 17 16 9 8 1 0 SRAMSIZ 12 11 NVPSIZ2 7 25 ARCH 10 NVPSIZ 5 4 3 2 VERSION VERSION: Version of the Device Current version of the device. EPROC: Embedded Processor Value Name Description 0 SAM x7 Cortex-M7 1 ARM946ES ARM946ES 2 ARM7TDMI ARM7TDMI 3 CM3 Cortex-M3 4 ARM920T ARM920T 5 ARM926EJS ARM926EJS 6 CA5 Cortex-A5 7 CM4 Cortex-M4 NVPSIZ: Nonvolatile Program Memory Size Value Name Description 0 NONE None 1 8K 8 Kbytes 2 16K 16 Kbytes 3 32K 32 Kbytes 4 – Reserved 5 64K 64 Kbytes 6 – Reserved 7 128K 128 Kbytes 8 160K 160 Kbytes 9 256K 256 Kbytes 10 512K 512 Kbytes DS60001476B-page 64  2017 Microchip Technology Inc. SAMA5D2 SERIES Value Name Description 11 – Reserved 12 1024K 1024 Kbytes 13 – Reserved 14 2048K 2048 Kbytes 15 – Reserved NVPSIZ2: Second Nonvolatile Program Memory Size Value Name Description 0 NONE None 1 8K 8 Kbytes 2 16K 16 Kbytes 3 32K 32 Kbytes 4 – Reserved 5 64K 64 Kbytes 6 – Reserved 7 128K 128 Kbytes 8 – Reserved 9 256K 256 Kbytes 10 512K 512 Kbytes 11 – Reserved 12 1024K 1024 Kbytes 13 – Reserved 14 2048K 2048 Kbytes 15 – Reserved SRAMSIZ: Internal SRAM Size Value Name Description 0 48K 48 Kbytes 1 192K 192 Kbytes 2 384K 384 Kbytes 3 6K 6 Kbytes 4 24K 24 Kbytes 5 4K 4 Kbytes 6 80K 80 Kbytes 7 160K 160 Kbytes 8 8K 8 Kbytes 9 16K 16 Kbytes 10 32K 32 Kbytes  2017 Microchip Technology Inc. DS60001476B-page 65 SAMA5D2 SERIES Value Name Description 11 64K 64 Kbytes 12 128K 128 Kbytes 13 256K 256 Kbytes 14 96K 96 Kbytes 15 512K 512 Kbytes ARCH: Architecture Identifier Value Name Description 0xA5 SAMA5 SAMA5 NVPTYP: Nonvolatile Program Memory Type Value Name Description 0 ROM ROM 1 ROMLESS ROMless or on-chip Flash 2 FLASH Embedded Flash Memory 3 ROM_FLASH ROM and Embedded Flash Memory  NVPSIZ is ROM size  NVPSIZ2 is Flash size 4 SRAM SRAM emulating ROM EXT: Extension Flag 0: Chip ID has a single register definition without extension. 1: An extended Chip ID exists. DS60001476B-page 66  2017 Microchip Technology Inc. SAMA5D2 SERIES 12.3.2 Chip ID Extension Register Name: CHIPID_EXID Address: 0xFC069004 Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 EXID 23 22 21 20 EXID 15 14 13 12 EXID 7 6 5 4 EXID EXID: Chip ID Extension This field is cleared if CHIPID_CIDR.EXT = 0.  2017 Microchip Technology Inc. DS60001476B-page 67 SAMA5D2 SERIES 13. ARM Cortex-A5 13.1 Description The ARM Cortex-A5 processor is a high-performance, low-power, ARM macrocell with an L1 cache subsystem that provides full virtual memory capabilities. The Cortex-A5 processor implements the ARMv7 architecture and runs 32-bit ARM instructions, 16-bit and 32-bit Thumb instructions, and 8-bit Java™ byte codes in Jazelle® state. The Cortex-A5 NEON Media Processing Engine (MPE) extends the Cortex-A5 functionality to provide support for the ARM v7 Advanced SIMD v2 and Vector Floating-Point v4 (VFPv4) instruction sets. The Cortex-A5 NEON MPE provides flexible and powerful acceleration for signal processing algorithms including multimedia such as image processing, video decode/encode, 2D/3D graphics, and audio. See the Cortex-A5 NEON Media Processing Engine Technical Reference Manual. The Cortex-A5 processor includes TrustZone® technology to enhance security by partitioning the SoC’s hardware and software resources in a Secure world for the security subsystem and a Normal world for the rest, enabling a strong security perimeter to be built between the two. See Security Extensions overview in the Cortex-A5 Technical Reference Manual. See the ARM Architecture Reference Manual for details on how TrustZone works in the architecture. Note: 13.1.1 All ARM publications referenced in this datasheet can be found at www.arm.com. Power Management The Cortex-A5 design supports the following main levels of power management: • Run Mode • Standby Mode 13.1.1.1 Run Mode Run mode is the normal mode of operation where all of the processor functionality is available. Everything, including core logic and embedded RAM arrays, is clocked and powered up. 13.1.1.2 Standby Mode Standby mode disables most of the clocks of the processor, while keeping it powered up. This reduces the power drawn to the static leakage current, plus a small clock power overhead required to enable the processor to wake up from Standby mode. The transition from Standby mode to Run mode is caused by one of the following: • • • • the arrival of an interrupt, either masked or unmasked the arrival of an event, if standby mode was initiated by a Wait for Event (WFE) instruction a debug request, when either debug is enabled or disabled a reset. DS60001476B-page 68  2017 Microchip Technology Inc. SAMA5D2 SERIES 13.2 • • • • • • • • • • • Embedded Characteristics In-order pipeline with dynamic branch prediction ARM, Thumb, and ThumbEE instruction set support TrustZone security extensions Harvard level 1 memory system with a Memory Management Unit (MMU) 32 Kbytes Data Cache 32 Kbytes Instruction Cache 64-bit AXI master interface ARM v7 debug architecture Trace support through an Embedded Trace Macrocell (ETM) interface Media Processing Engine (MPE) with NEON technology Jazelle hardware acceleration 13.3 Block Diagram Figure 13-1: Cortex-A5 Processor Top-level Diagram *'   '   *    #$%&   %                  ' $!           "   ' $!       ! "        " :&     " %+"    2017 Microchip Technology Inc. DS60001476B-page 69 SAMA5D2 SERIES 13.4 Programmer Model 13.4.1 Processor Operating Modes The following operation modes are present in all states: • • • • • • • • User mode (USR) is the usual ARM program execution state. It is used for executing most application programs. Fast Interrupt (FIQ) mode is used for handling fast interrupts. It is suitable for high-speed data transfer or channel process. Interrupt (IRQ) mode is used for general-purpose interrupt handling. Supervisor mode (SVC) is a protected mode for the operating system. Abort mode (ABT) is entered after a data or instruction prefetch abort. System mode (SYS) is a privileged user mode for the operating system. Undefined mode (UND) is entered when an undefined instruction exception occurs. Monitor mode (MON) is secure mode that enables change between Secure and Non-secure states, and can also be used to handle any of FIQs, IRQs and external aborts. Entered on execution of a Secure Monitor Call (SMC) instruction. Mode changes may be made under software control, or may be brought about by external interrupts or exception processing. Most application programs execute in User Mode. The non-user modes, known as privileged modes, are entered in order to service interrupts or exceptions or to access protected resources. 13.4.2 Processor Operating States The processor has the following instruction set states controlled by the T bit and J bit in the CPSR. • ARM state: The processor executes 32-bit, word-aligned ARM instructions. • Thumb state: The processor executes 16-bit and 32-bit, halfword-aligned Thumb instructions. • ThumbEE state: The processor executes a variant of the Thumb instruction set designed as a target for dynamically generated code. This is code compiled on the device either shortly before or during execution from a portable bytecode or other intermediate or native representation. • Jazelle state: The processor executes variable length, byte-aligned Java bytecodes. The J bit and the T bit determine the instruction set used by the processor. Table 13-1 shows the encoding of these bits. Table 13-1: CPSR J and T Bit Encoding J T Instruction Set State 0 0 ARM 0 1 Thumb 1 0 Jazelle 1 1 ThumbEE Changing between ARM and Thumb states does not affect the processor mode or the register contents. See the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition for information on entering and exiting ThumbEE state. 13.4.2.1 Switching State It is possible to change the instruction set state of the processor between: • • • • ARM state and Thumb state using the BX and BLX instructions. Thumb state and ThumbEE state using the ENTERX and LEAVEX instructions. ARM and Jazelle state using the BXJ instruction. Thumb and Jazelle state using the BXJ instruction. See the ARM Architecture Reference Manual for more information about changing instruction set state. DS60001476B-page 70  2017 Microchip Technology Inc. SAMA5D2 SERIES 13.4.3 Cortex-A5 Registers This view provides 16 ARM core registers, R0 to R15, that include the Stack Pointer (SP), Link Register (LR), and Program Counter (PC). These registers are selected from a total set of either 31 or 33 registers, depending on whether or not the Security Extensions are implemented. The current execution mode determines the selected set of registers, as shown in Table 13-2. This shows that the arrangement of the registers provides duplicate copies of some registers, with the current register selected by the execution mode. This arrangement is described as banking of the registers, and the duplicated copies of registers are referred to as banked registers. Table 13-2: Cortex-A5 Modes and Registers Layout User and System Monitor Supervisor Abort Undefined Interrupt Fast Interrupt R0 R0 R0 R0 R0 R0 R0 R1 R1 R1 R1 R1 R1 R1 R2 R2 R2 R2 R2 R2 R2 R3 R3 R3 R3 R3 R3 R3 R4 R4 R4 R4 R4 R4 R4 R5 R5 R5 R5 R5 R5 R5 R6 R6 R6 R6 R6 R6 R6 R7 R7 R7 R7 R7 R7 R7 R8 R8 R8 R8 R8 R8 R8_FIQ R9 R9 R9 R9 R9 R9 R9_FIQ R10 R10 R10 R10 R10 R10 R10_FIQ R11 R11 R11 R11 R11 R11 R11_FIQ R12 R12 R12 R12 R12 R12 R12_FIQ R13 R13_MON R13_SVC R13_ABT R13_UND R13_IRQ R13_FIQ R14 R14_MON R14_SVC R14_ABT R14_UND R14_IRQ R14_FIQ PC PC PC PC PC PC PC CPSR CPSR CPSR CPSR CPSR CPSR CPSR SPSR_MON SPSR_SVC SPSR_ABT SPSR_UND SPSR_IRQ SPSR_FIQ Mode-specific banked registers  2017 Microchip Technology Inc. DS60001476B-page 71 SAMA5D2 SERIES The core contains one CPSR, and six SPSRs for exception handlers to use. The program status registers: • hold information about the most recently performed ALU operation • control the enabling and disabling of interrupts • set the processor operating mode Figure 13-2: Status Register Format 31 30 29 28 27 N Z C V Q • • • • • • • • • • • 24 23 2019 IT J Reserved [1:0] 16 15 GE[3:0] 10 9 8 7 6 5 4 IT[7:2] E A I F T 0 Mode N: Negative, Z: Zero, C: Carry, and V: Overflow are the four ALU flags Q: cumulative saturation flag IT: If-Then execution state bits for the Thumb IT (If-Then) instruction J: Jazelle bit, see the description of the T bit GE: Greater than or Equal flags, for SIMD instructions E: Endianness execution state bit. Controls the load and store endianness for data accesses. This bit is ignored by instruction fetches. - E = 0: Little endian operation - E = 1: Big endian operation A: Asynchronous abort disable bit. Used to mask asynchronous aborts. I: Interrupt disable bit. Used to mask IRQ interrupts. F: Fast interrupt disable bit. Used to mask FIQ interrupts. T: Thumb execution state bit. This bit and the J execution state bit, bit [24], determine the instruction set state of the processor, ARM, Thumb, Jazelle, or ThumbEE. Mode: five bits to encode the current processor mode. The effect of setting M[4:0] to a reserved value is UNPREDICTABLE. Table 13-3: Processor Mode vs. Mode Field DS60001476B-page 72 Mode M[4:0] USR 10000 FIQ 10001 IRQ 10010 SVC 10011 MON 10110 ABT 10111 UND 11011 SYS 11111 Reserved Other  2017 Microchip Technology Inc. SAMA5D2 SERIES 13.4.3.1 CP15 Coprocessor Coprocessor 15, or System Control Coprocessor CP15, is used to configure and control all the items in the list below: • • • • • Cortex A5 Caches (ICache, DCache and write buffer) MMU Security Other system options To control these features, CP15 provides 16 additional registers. See Table 13-4. Table 13-4: Register 0 CP15 Registers Name ID Read/Write Code(1) Read/Unpredictable (1) Read/Unpredictable 0 Cache type 1 Control(1) Read/Write 1 Security(1) Read/Write 2 Translation Table Base Read/Write 3 Domain Access Control Read/Write 4 Reserved None (1) Read/Write 5 Data fault Status 5 Instruction fault status Read/Write 6 Fault Address Read/Write 7 Cache and MMU Operations(1) Read/Write 8 TLB operations Unpredictable/Write lockdown(1) 9 Cache 10 TLB lockdown Read/Write 11 Reserved None 12 Interrupts management Read/Write 12 Monitor vectors Read-only Read/Write 13 (1) FCSE PID Read/Write 13 Context ID(1) Read/Write 14 Reserved None 15 Test configuration Read/Write Note 1: This register provides access to more than one register. The register accessed depends on the value of the CRm field or Opcode_2 field.  2017 Microchip Technology Inc. DS60001476B-page 73 SAMA5D2 SERIES 13.4.4 CP 15 Register Access CP15 registers can only be accessed in privileged mode by: • MCR (Move to Coprocessor from ARM Register) instruction is used to write an ARM register to CP15. • MRC (Move to ARM Register from Coprocessor) instruction is used to read the value of CP15 to an ARM register. Other instructions such as CDP, LDC, STC can cause an undefined instruction exception. The assembler code for these instructions is: MCR/MRC{cond} p15, opcode_1, Rd, CRn, CRm, opcode_2. The MCR/MRC instructions bit pattern is shown below: 31 30 29 28 27 1 26 1 21 20 L 19 18 13 12 11 1 10 1 5 4 1 3 2 cond 23 22 opcode_1 15 14 Rd 7 6 opcode_2 25 1 24 0 17 16 9 1 8 1 1 0 CRn CRm CRm[3:0]: Specified Coprocessor Action Determines specific coprocessor action. Its value is dependent on the CP15 register used. For details, see CP15 specific register behavior. opcode_2[7:5] Determines specific coprocessor operation code. By default, set to 0. Rd[15:12]: ARM Register Defines the ARM register whose value is transferred to the coprocessor. If R15 is chosen, the result is unpredictable. CRn[19:16]: Coprocessor Register Determines the destination coprocessor register. L: Instruction Bit 0: MCR instruction 1: MRC instruction opcode_1[23:20]: Coprocessor Code Defines the coprocessor specific code. Value is c15 for CP15. cond [31:28]: Condition 13.4.5 Addresses in the Cortex-A5 processor The Cortex-A5 processor operates using virtual addresses (VAs). The Memory Management Unit (MMU) translates these VAs into the physical addresses (PAs) used to access the memory system. Translation tables hold the mappings between VAs and PAs. See the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition for more information. When the Cortex-A5 processor is executing in Non-secure state, the processor performs translation table look-ups using the Non-secure versions of the Translation Table Base Registers. In this situation, any VA can only translate into a Non-secure PA. When it is in Secure state, the Cortex-A5 processor performs translation table look-ups using the Secure versions of the Translation Table Base Registers. In this situation, the security state of any VA is determined by the NS bit of the translation table descriptors for that address. Following is an example of the address manipulation that occurs when the Cortex-A5 processor requests an instruction: DS60001476B-page 74  2017 Microchip Technology Inc. SAMA5D2 SERIES 1. 2. 3. 4. The Cortex-A5 processor issues the VA of the instruction as Secure or Non-secure VA accesses according to the state the processor is in. The instruction cache is indexed by the bits of the VA. The MMU performs the translation table look-up in parallel with the cache access. If the processor is in the Secure state it uses the Secure translation tables, otherwise it uses the Non-secure translation tables. If the protection check carried out by the MMU on the VA does not abort and the PA tag is in the instruction cache, the instruction data is returned to the processor. If there is a cache miss, the MMU passes the PA to the AXI bus interface to perform an external access. The external access is always Non-secure when the core is in the Non-secure state. In the Secure state, the external access is Secure or Non-secure according to the NS attribute value in the selected translation table entry. In Secure state, both L1 and L2 translation table walk accesses are marked as Secure, even if the first level descriptor is marked as NS. 13.4.6 Security Extensions Overview The purpose of the Security Extensions is to enable the construction of a secure software environment. See the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition for details of the Security Extensions. 13.4.6.1 System Boot Sequence CAUTION: The Security Extensions enable the construction of an isolated software environment for more secure execution, depending on a suitable system design around the processor. The technology does not protect the processor from hardware attacks, and care must be taken to be sure that the hardware containing the reset handling code is appropriately secure. The processor always boots in the privileged Supervisor mode in the Secure state, with the NS bit set to 0. This means that code that does not attempt to use the Security Extensions always runs in the Secure state. If the software uses both Secure and Non-secure states, the less trusted software, such as a complex operating system and application code running under that operating system, executes in Nonsecure state, and the most trusted software executes in the Secure state. The following sequence is expected to be typical use of the Security Extensions: 1. 2. 3. 4. 5. 6. 7. Exit from reset in Secure state. Configure the security state of memory and peripherals. Some memory and peripherals are accessible only to the software running in Secure state. Initialize the secure operating system. The required operations depend on the operating system, and include initialization of caches, MMU, exception vectors, and stacks. Initialize Secure Monitor software to handle exceptions that switch execution between the Secure and Non-secure operating systems. Optionally lock aspects of the secure state environment against further configuration. Pass control through the Secure Monitor software to the non-secure OS with an SMC instruction. Enable the Non-secure operating system to initialize. The required operations depend on the operating system, and typically include initialization of caches, MMU, exception vectors, and stacks. The overall security of the secure software depends on the system design, and on the secure software itself.  2017 Microchip Technology Inc. DS60001476B-page 75 SAMA5D2 SERIES 13.4.7 13.4.7.1 TrustZone Hardware TrustZone enables a single physical processor core to execute code safely and efficiently from both the Normal world and the Secure world. This removes the need for a dedicated security processor core, saving silicon area and power, and allowing high performance security software to run alongside the Normal world operating environment. The two virtual processors context switch via a new processor mode called monitor mode when changing the currently running virtual processor. Figure 13-3: 13.4.7.2 TrustZone Hardware Implementation Software The mechanisms by which the physical processor can enter monitor mode from the Normal world are tightly controlled, and are all viewed as exceptions to the monitor mode software. Software executing a dedicated instruction can trigger entry to monitor, the Secure Monitor Call (SMC) instruction, or by a subset of the hardware exception mechanisms. Configuration of the IRQ, FIQ, external Data Abort, and external Prefetch Abort exceptions can cause the processor to switch into monitor mode. The software that executes within monitor mode is implementation defined, but it generally saves the state of the current world and restores the state of the world at the location to which it switches. It then performs a return-from-exception to restart processing in the restored world. DS60001476B-page 76  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 13-4: 13.4.7.3 TrustZone Software Implementation in a Trusted Execution Environment (TEE) Debug TrustZone hardware architecture is a security-aware debug infrastructure that can enable control over access to secure world debug, without impairing debug visibility of the Normal world. This is controlled with bits in the Secure Fuse Controller. Note: 13.5 13.5.1 Secure debug modes are described in the document SAMA5D2 External Tamper Protections, document no. 44095. Contact a Microchip sales representative for further details. Memory Management Unit About the MMU The MMU works with the L1 and L2 memory system to translate virtual addresses to physical addresses. It also controls accesses to and from external memory. The ARM v7 Virtual Memory System Architecture (VMSA) features include the following: • Page table entries that support: - 16 Mbyte supersections. The processor supports supersections that consist of 16 Mbyte blocks of memory. - 1 Mbyte sections - 64 Kbyte large pages - 4 Kbyte small pages • 16 access domains • Global and application-specific identifiers to remove the requirement for context switch TLB flushes. • Extended permissions checking capability. TLB maintenance and configuration operations are controlled through a dedicated coprocessor, CP15, integrated with the core. This coprocessor provides a standard mechanism for configuring the L1 memory system. See the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition for a full architectural description of the ARMv7 VMSA.  2017 Microchip Technology Inc. DS60001476B-page 77 SAMA5D2 SERIES 13.5.2 Memory Management System The Cortex-A5 processor supports the ARM v7 VMSA including the TrustZone security extension. The translation of a Virtual Address (VA) used by the instruction set architecture to a Physical Address (PA) used in the memory system and the management of the associated attributes and permissions is carried out using a two-level MMU. The first level MMU uses a Harvard design with separate micro TLB structures in the PFU for instruction fetches (IuTLB) and in the DPU for data read and write requests (DuTLB). A miss in the micro TLB results in a request to the main unified TLB shared between the data and instruction sides of the memory system. The TLB consists of a 128-entry two-way set-associative RAM based structure. The TLB page-walk mechanism supports page descriptors held in the L1 data cache. The caching of page descriptors is configured globally for each translation table base register, TTBRx, in the system coprocessor, CP15. The TLB contains a hitmap cache of the page types which have already been stored in the TLB. 13.5.2.1 Memory types Although various different memory types can be specified in the page tables, the Cortex-A5 processor does not implement all possible combinations: • Write-through caches are not supported. Any memory marked as write-through is treated as Non-cacheable. • The outer shareable attribute is not supported. Anything marked as outer shareable is treated in the same way as inner shareable. • Write-back no write-allocate is not supported. It is treated as write-back write-allocate. Table 13-5 shows the treatment of each different memory type in the Cortex-A5 processor in addition to the architectural requirements. Table 13-5: Treatment of Memory Attributes Memory Type Attribute Strongly Ordered Shareability Other Attributes Notes — — — Non-shareable — — Shareable — — Non-cacheable Does not access L1 caches Write-through cacheable Treated as non-cacheable Write-back cacheable, write allocate Can dynamically switch to no write allocate, if more than three full cache lines are written in succession Write-back cacheable, no write allocate Treated as non-shareable write-back cacheable, write allocate Non-cacheable — Write-through cacheable Treated as inner shareable non-cacheable Write-back cacheable, write allocate Treated as inner shareable non-cacheable unless the SMP bit in the Auxiliary Control Register is set (ACTLR[6] = b1). If this bit is set the area is treated as write-back cacheable write allocate. Device Non-shareable Normal Inner shareable Write-back cacheable, no write allocate Non-cacheable Treated as inner shareable non-cacheable Write-through cacheable Outer shareable Write-back cacheable, write allocate Write-back cacheable, no write allocate DS60001476B-page 78 Treated as inner shareable non-cacheable unless the SMP bit in the Auxiliary Control Register is set (ACTLR[6] = b1). If this bit is set the area is treated as write-back cacheable write allocate.  2017 Microchip Technology Inc. SAMA5D2 SERIES 13.5.3 TLB Organization TLB Organization is described in the sections that follow: • Micro TLB • Main TLB 13.5.3.1 Micro TLB The first level of caching for the page table information is a micro TLB of 10 entries that is implemented on each of the instruction and data sides. These blocks provide a lookup of the virtual addresses in a single cycle. The micro TLB returns the physical address to the cache for the address comparison, and also checks the access permissions to signal either a Prefetch Abort or a Data Abort. All main TLB related maintenance operations affect both the instruction and data micro TLBs, causing them to be flushed. In the same way, any change of the following registers causes the micro TLBs to be flushed: • • • • • Context ID Register (CONTEXTIDR) Domain Access Control Register (DACR) Primary Region Remap Register (PRRR) Normal Memory Remap Register (NMRR) Translation Table Base Registers (TTBR0 and TTBR1)  2017 Microchip Technology Inc. DS60001476B-page 79 SAMA5D2 SERIES 13.5.3.2 Main TLB Misses from the instruction and data micro TLBs are handled by a unified main TLB. Accesses to the main TLB take a variable number of cycles, according to competing requests from each of the micro TLBs and other implementation-dependent factors. The main TLB is 128-entry two-way set-associative. TLB match process Each TLB entry contains a virtual address, a page size, a physical address, and a set of memory properties. Each is marked as being associated with a particular application space (ASID), or as global for all application spaces. The CONTEXTIDR determines the currently selected application space. A TLB entry matches when these conditions are true: • Its virtual address matches that of the requested address. • Its Non-secure TLB ID (NSTID) matches the Secure or Non-secure state of the MMU request. • Its ASID matches the current ASID in the CONTEXTIDR or is global. The operating system must ensure that, at most, one TLB entry matches at any time. The TLB can store entries based on the following block sizes: Supersections Describe 16 Mbyte blocks of memory Sections Describe 1 Mbyte blocks of memory Large pages Describe 64 Kbyte blocks of memory Small pages Describe 4 Kbyte blocks of memory Supersections, sections and large pages are supported to permit mapping of a large region of memory while using only a single entry in the TLB. If no mapping for an address is found within the TLB, then the translation table is automatically read by hardware and a mapping is placed in the TLB. 13.5.4 Memory Access Sequence When the processor generates a memory access, the MMU: 1. 2. 3. Performs a lookup for the requested virtual address and current ASID and security state in the relevant instruction or data micro TLB. If there is a miss in the micro TLB, performs a lookup for the requested virtual address and current ASID and security state in the main TLB. If there is a miss in main TLB, performs a hardware translation table walk. The MMU can be configured to perform hardware translation table walks in cacheable regions by setting the IRGN bits in Translation Table Base Register 0 and Translation Table Base Register 1. If the encoding of the IRGN bits is write-back, an L1 data cache lookup is performed and data is read from the data cache. If the encoding of the IRGN bits is write-through or non-cacheable, an access to external memory is performed. For more information, see Cortex-A5 Technical Reference Manual. The MMU might not find a global mapping, or a mapping for the currently selected ASID, with a matching Non-secure TLB ID (NSTID) for the virtual address in the TLB. In this case, the hardware does a translation table walk if the translation table walk is enabled by the PD0 or PD1 bit in the Translation Table Base Control Register. If translation table walks are disabled, the processor returns a Section Translation fault. For more information, see Cortex-A5 Technical Reference Manual. If the TLB finds a matching entry, it uses the information in the entry as follows: 1. The access permission bits and the domain determine if the access is enabled. If the matching entry does not pass the permission checks, the MMU signals a memory abort. See the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition for a description of access permission bits, abort types and priorities, and for a description of the Instruction Fault Status Register (IFSR) and Data Fault Status Register (DFSR). 2. The memory region attributes specified in both the TLB entry and the CP15 c10 remap registers determine if the access is - Secure or Non-secure - Shared or not - Normal memory, Device, or Strongly-ordered For more information, see Cortex-A5 Technical Reference Manual, Memory region remap. 3. The TLB translates the virtual address to a physical address for the memory access. DS60001476B-page 80  2017 Microchip Technology Inc. SAMA5D2 SERIES 13.5.5 Interaction with Memory System The MMU can be enabled or disabled as described in the ARM Architecture Reference Manual, ARMv7-A and ARMv7-R edition. 13.5.6 External Aborts External memory errors are defined as those that occur in the memory system rather than those that are detected by the MMU. External memory errors are expected to be extremely rare. External aborts are caused by errors flagged by the AXI interfaces when the request goes external to the Cortex-A5 processor. External aborts can be configured to trap to Monitor mode by setting the EA bit in the Secure Configuration Register. For more information, see Cortex-A5 Technical Reference Manual. 13.5.6.1 External Aborts on Data Write Externally generated errors during a data write can be asynchronous. This means that the r14_abt on entry into the abort handler on such an abort might not hold the address of the instruction that caused the exception. The DFAR is Unpredictable when an asynchronous abort occurs. Externally generated errors during data read are always synchronous. The address captured in the DFAR matches the address which generated the external abort. 13.5.6.2 Synchronous and Asynchronous Aborts Chapter 4, System Control in the Cortex-A5 Technical Reference Manual describes synchronous and asynchronous aborts, their priorities, and the IFSR and DFSR. To determine a fault type, read the DFSR for a data abort or the IFSR for an instruction abort. The processor supports an Auxiliary Fault Status Register for software compatibility reasons only. The processor does not modify this register because of any generated abort. 13.5.7 MMU Software Accessible Registers The system control coprocessor registers, CP15, in conjunction with page table descriptors stored in memory, control the MMU. Access all the registers with instructions of the form: MRC p15, 0, , , , MCR p15, 0, , , , CRn is the system control coprocessor register. Unless specified otherwise, CRm and Opcode_2 Should Be Zero.  2017 Microchip Technology Inc. DS60001476B-page 81 SAMA5D2 SERIES 14. L2 Cache Controller (L2CC) 14.1 Description The L2 Cache Controller (L2CC) is based on the L2CC-PL310 ARM multiway cache macrocell, version r3p2. The addition of an on-chip secondary cache, also referred to as a Level 2 or L2 cache, is a method of improving the system performance when significant memory traffic is generated by the processor. 14.2 • • • • • • Embedded Characteristics 8-way set associative cache architecture Data banking is not supported No parity bit embedded Lockdown by master is not supported Lockdown by line is not supported TrustZone architecture for enhanced OS security 14.3 14.3.1 Product Dependencies Power Management The L2 Cache Controller is continuously clocked by the Processor Clock. The Power Management Controller has no effect on the behavior of the L2 Cache Controller. 14.4 Functional Description The addition of an on-chip secondary cache, also referred to as a Level 2 or L2 cache, is a recognized method of improving the performance of ARM-based systems when significant memory traffic is generated by the processor. By definition a secondary cache assumes the presence of a Level 1 or primary cache, closely coupled or internal to the processor. Memory access is fastest to L1 cache, followed closely by L2 cache. Memory access is typically significantly slower with L3 main memory. The cache controller is a unified, physically addressed, physically tagged cache with up to 8 ways. The user can lock the replacement algorithm on a way basis, enabling the associativity to be reduced from 8-way down to 1-way (directly mapped). The cache controller does not have snooping hardware to maintain coherency between caches, so the user has to maintain coherency by software. 14.4.1 Double Linefill Issuing The L2CC cache line length is 32-byte. Therefore, by default, on each L2 cache miss, L2CC issues 32-byte linefills, 4 x 64-bit read bursts, to the L3 memory system. L2CC can issue 64-byte linefills, 8 x 64-bit read bursts, on an L2 cache miss. When the L2CC is waiting for the data from L3, it performs a lookup on the second cache line targeted by the 64-byte linefill. If it misses, data corresponding to the second cache line are allocated to the L2 cache. If it hits, data corresponding to the second cache line are discarded. The user can control this feature using the DLEN, DLFWRDIS and DLEN bits of the L2CC Prefetch Control Register. The IDLEN and DLFWRDIS bits are only used if you set the DLEN bit HIGH. Table 14-1 shows the behavior of the L2CC master ports, depending on the configuration chosen by the user. Table 14-1: L2CC Master Port Behavior Bit 30 DLEN Bit 27 DLFWRDIS Bit 23 IDLEN Original Read Address from L1 Read Address to L3 AXI Burst Type AXI Burst Length Targeted Cache Lines 0 0 or 1 0 or 1 0x00 0x00 WRAP 0x3, 4x64-bit 0x00 0 0 or 1 0 or 1 0x20 0x20 WRAP 0x3, 4x64-bit 0x20 1 0 or 1 0 0x00 0x00 WRAP 0x7, 8x64-bit 0x00 and 0x20 1 1 0 0x08 or 0x10 or 0x18 0x08 WRAP 0x3, 4x64-bit 0x00 1 0 0 0x08 or 0x10 or 0x18 0x00 WRAP 0x7, 8x64-bit 0x00 and 0x20 DS60001476B-page 82  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 14-1: L2CC Master Port Behavior (Continued) Bit 30 DLEN Bit 27 DLFWRDIS Bit 23 IDLEN Original Read Address from L1 Read Address to L3 AXI Burst Type AXI Burst Length Targeted Cache Lines 1 0 or 1 0 0x20 0x20 WRAP 0x7, 8x64-bit 0x00 and 0x20 1 1 0 0x28 or 0x30 or 0x38 0x28 WRAP 0x3, 4x64-bit 0x20 1 0 0 0x28 or 0x30 or 0x38 0x20 WRAP 0x7, 8x64-bit 0x00 and 0x20 1 0 or 1 1 0x00 0x00 INCR or WRAP 0x7, 8x64-bit 0x00 and 0x20 1 1 1 0x08 or 0x10 or 0x18 0x08 WRAP 0x3, 4x64-bit 0x00 1 0 1 0x08 or 0x10 or 0x18 0x00 INCR or WRAP 0x7, 8x64-bit 0x00 and 0x20 1 0 or 1 1 0x20 0x20 INCR 0x7, 8x64-bit 0x20 and 0x40 1 1 1 0x28 or 0x30 or 0x38 0x28 WRAP 0x3, 4x64-bit 0x20 1 0 1 0x28 or 0x30 or 0x38 0x20 INCR 0x7, 8x64-bit 0x20 and 0x40 Note 1: Double linefills are not issued for prefetch reads if you enable exclusive cache configuration. 2: Double linefills are not launched when crossing a 4-Kbyte boundary. 3: Double linefills only occur if a WRAP4 or an INCR4 64-bit transaction is received on the slave ports. This transaction is most commonly seen as a result of a cache linefill in a master, but can be produced by a master when accessing memory marked as inner non-cacheable.  2017 Microchip Technology Inc. DS60001476B-page 83 SAMA5D2 SERIES 14.5 L2 Cache Controller (L2CC) User Interface Table 14-2: Register Mapping Offset Register Name 0x000 Cache ID Register 0x004 Cache Type Register 0x100 Control Register Access Reset L2CC_IDR Read-only 0x4100_00C9 L2CC_TYPR Read-only L2CC_CR 0x0010_0100 (1) 0x0000_0000 Read-only(1) 0x0202_0000 Read/Write, Read-only 0x104 Auxiliary Control Register L2CC_ACR Read/Write, 0x108 Tag RAM Control Register L2CC_TRCR Read/Write, Read-only(1) 0x0000_0111 (1) 0x0000_0111 0x10C Data RAM Control Register L2CC_DRCR 0x110–0x1FC Reserved – 0x200 Event Counter Control Register 0x204 Read/Write, Read-only – – L2CC_ECR Read/Write 0x0000_0000 Event Counter 1 Configuration Register L2CC_ECFGR1 Read/Write 0x0202_0000 0x208 Event Counter 0 Configuration Register L2CC_ECFGR0 Read/Write 0x0000_0000 0x20C Event Counter 1 Value Register L2CC_EVR1 Read/Write 0x0000_0000 0x210 Event Counter 0 Value Register L2CC_EVR0 Read/Write 0x0000_0000 0x214 Interrupt Mask Register L2CC_IMR Programmable(2) 0x0000_0000 0x218 Masked Interrupt Status Register L2CC_MISR Read-only 0x0000_0000 0x21C Raw Interrupt Status Register L2CC_RISR Read-only 0x220 Interrupt Clear Register L2CC_ICR 0x224–0x72C Reserved – 0x730 Cache Synchronization Register L2CC_CSR 0x734–0x76C Reserved – 0x770 Invalidate Physical Address Line Register L2CC_IPALR 0x774–0x778 Reserved – 0x77C Invalidate Way Register L2CC_IWR 0x780–0x7AF Reserved – 0x7B0 Clean Physical Address Line Register L2CC_CPALR 0x7B4 Reserved – 0x7B8 Clean Index Register 0x7BC Programmable 0x0000_0000 (2) 0x0000_0000 – – Read/Write 0x0000_0000 – – Read/Write 0x0000_0000 – – Read/Write 0x0000_0000 – – Read/Write 0x0000_0000 – – L2CC_CIR Read/Write 0x0000_0000 Clean Way Register L2CC_CWR Read/Write 0x0000_0000 0x7C0–0x7EC Reserved – – – 0x7F0 Clean Invalidate Physical Address Line Register L2CC_CIPALR Read/Write 0x0000_0000 0x7F4 Reserved – – – 0x7F8 Clean Invalidate Index Register L2CC_CIIR Read/Write 0x0000_0000 0x7FC Clean Invalidate Way Register L2CC_CIWR Read/Write 0x0000_0000 0x800–0x8FC Reserved – 0x900 0x904 Data Lockdown Register Instruction Lockdown Register DS60001476B-page 84 L2CC_DLKR L2CC_ILKR – – Programmable (2) 0x0000_0000 Programmable (2) 0x0000_0000  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 14-2: Register Mapping (Continued) Offset Register Name 0x908–0xF3C Reserved – 0xF40 Debug Control Register L2CC_DCR 0xF44–0xF5C Reserved – 0xF60 Prefetch Control Register L2CC_PCR 0xF64–0xF7C Reserved – 0xF80 Power Control Register L2CC_POWCR Access Reset – Read/Write, Read-only – (1) 0x0000_0000 – – Read/Write, Read-only(1) 0x0000_0000 – – (1) Read/Write, Read-only 0x0000_0000 Note 1: Read/Write in Secure mode, Read-only in Non-secure mode. 2: Programmable in Auxiliary Control Register.  2017 Microchip Technology Inc. DS60001476B-page 85 SAMA5D2 SERIES 14.5.1 L2CC Cache ID Register Name: L2CC_IDR Address: 0x00A00000 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ID 23 22 21 20 ID 15 14 13 12 ID 7 6 5 4 ID ID: Cache Controller ID The cache ID is 0x410000C9. DS60001476B-page 86  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.2 L2CC Type Register Name: L2CC_TYPR Address: 0x00A00004 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 21 DL2WSIZE 20 19 – 18 DL2ASS 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 9 IL2WSIZE 8 7 – 6 IL2ASS 5 – 4 – 3 – 2 – 1 – 0 – IL2ASS: Instruction L2 Cache Associativity The value is read from the field ASS in Auxiliary Control Register, should be 0. IL2WSIZE: Instruction L2 Cache Way Size The value is read from the field WAYSIZE in Auxiliary Control Register, should be 0x1. DL2ASS: Data L2 Cache Associativity The value is read from the field ASS in Auxiliary Control Register, should be 0. DL2WSIZE: Data L2 Cache Way Size The value is read from the field WAYSIZE in Auxiliary Control Register, should be 0x1.  2017 Microchip Technology Inc. DS60001476B-page 87 SAMA5D2 SERIES 14.5.3 L2CC Control Register Name: L2CC_CR Address: 0x00A00100 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 L2CEN L2CEN: L2 Cache Enable 0: L2 Cache is disabled. This is the default value. 1: L2 Cache is enabled. DS60001476B-page 88  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.4 L2CC Auxiliary Control Register Name: L2CC_ACR Address: 0x00A00104 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 IPEN 28 DPEN 27 NSIAC 26 NSLEN 25 CRPOL 24 FWA 23 FWA 22 SAOEN 21 PEN 20 EMBEN 19 18 WAYSIZE 17 16 ASS 15 – 14 – 13 SAIE 12 EXCC 11 SBDLE 10 HPSO 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – Note: The L2 Cache Controller (L2CC) must be disabled in the L2CC Control Register prior to any write access to this register. HPSO: High Priority for SO and Dev Reads Enable 0: Strongly Ordered and Device reads have lower priority than cacheable accesses when arbitrated in the L2CC master ports. This is the default value. 1: Strongly Ordered and Device reads get the highest priority when arbitrated in the L2CC master ports. SBDLE: Store Buffer Device Limitation Enable 0: Store buffer device limitation is disabled. Device writes can take all slots in the store buffer. This is the default value. 1: Store buffer device limitation is enabled. EXCC: Exclusive Cache Configuration 0: Disabled. This is the default value. 1: Enabled. SAIE: Shared Attribute Invalidate Enable 0: Shared invalidate behavior is disabled. This is the default value. 1: Shared invalidate behavior is enabled if the Shared Attribute Override Enable bit is not set. Shared invalidate behavior is enabled if both: • Shareable Attribute Invalidate Enable bit is set in the Auxiliary Control Register, bit[13] • Shared Attribute Override Enable bit is not set in the Auxiliary Control Register, bit[22] ASS: Associativity 0: 8-way.This is the default value. 1: Reserved. WAYSIZE: Way Size Value Name Description 0x0 RESERVED Reserved 0x1 16KB_WAY 16-Kbyte way set associative 0x2 RESERVED Reserved 0x3 RESERVED Reserved  2017 Microchip Technology Inc. DS60001476B-page 89 SAMA5D2 SERIES Value Name Description 0x4 RESERVED Reserved 0x5 RESERVED Reserved 0x6 RESERVED Reserved 0x7 RESERVED Reserved EMBEN: Event Monitor Bus Enable 0: Disabled. This is the default value. 1: Enabled. PEN: Parity Enable 0: Disabled. This is the default value. 1: Enabled. SAOEN: Shared Attribute Override Enable 0: Treats shared accesses. This is the default value. 1: Shared attribute is internally ignored. FWA: Force Write Allocate 0: The L2 Cache controller uses AWCACHE attributes for WA. This is the default value. 1: User forces no allocate, WA bit must be set to 0. 2: User overrides AWCACHE attributes, WA bit must be set to 1. All cacheable write misses become write allocated. 3: The write allocation is internally mapped to 00. CRPOL: Cache Replacement Policy 0: Pseudo-random replacement using the LFSR algorithm. 1: Round-robin replacement. This is always the default value. NSLEN: Non-Secure Lockdown Enable 0: Lockdown registers cannot be modified using non-secure accesses. This is the default value. 1: Non-secure accesses can write to the lockdown registers. NSIAC: Non-Secure Interrupt Access Control 0: Interrupt Clear Register and Interrupt Mask Register can only be modified or read with secure accesses. This is the default value. 1: Interrupt Clear Register and Interrupt Mask Register can be modified or read with secure or non-secure accesses. DPEN: Data Prefetch Enable 0: Data prefetching is disabled. This is the default value. 1: Data prefetching is enabled. IPEN: Instruction Prefetch Enable 0: Instruction prefetching is disabled. This is the default value. 1: Instruction prefetching is enabled. DS60001476B-page 90  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.5 L2CC Tag RAM Latency Control Register Name: L2CC_TRCR Address: 0x00A00108 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 9 TWRLAT 8 7 – 6 5 TRDLAT 4 3 – 2 1 TSETLAT 0 Note: The L2 Cache Controller (L2CC) must be disabled in the L2CC Control Register prior to any write access to this register. TSETLAT: Setup Latency TRDLAT: Read Access Latency TWRLAT: Write Access Latency Latency to Tag RAM is the programmed value + 1. Default value is 0.  2017 Microchip Technology Inc. DS60001476B-page 91 SAMA5D2 SERIES 14.5.6 L2CC Data RAM Latency Control Register Name: L2CC_DRCR Address: 0x00A0010C Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 9 DWRLAT 8 7 – 6 5 DRDLAT 4 3 – 2 1 DSETLAT 0 Note: The L2 Cache Controller (L2CC) must be disabled in the L2CC Control Register prior to any write access to this register. DSETLAT: Setup Latency DRDLAT: Read Access Latency DWRLAT: Write Access Latency Latency to Data RAM is the programmed value + 1. Default value is 0. DS60001476B-page 92  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.7 L2CC Event Counter Control Register Name: L2CC_ECR Address: 0x00A00200 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 EVC1RST 1 EVC0RST 0 EVCEN EVCEN: Event Counter Enable 0: Disables Event Counter. This is the default value. 1: Enables Event Counter. EVC0RST: Event Counter 0 Reset 0: No effect, always read as zero. 1: Resets Counter 0. EVC1RST: Event Counter 1 Reset 0: No effect, always read as zero. 1: Resets Counter 1.  2017 Microchip Technology Inc. DS60001476B-page 93 SAMA5D2 SERIES 14.5.8 L2CC Event Counter 1 Configuration Register Name: L2CC_ECFGR1 Address: 0x00A00204 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 4 3 2 1 ESRC 0 EIGEN EIGEN: Event Counter Interrupt Generation Value Name Description 0x0 INT_DIS Disables (default) 0x1 INT_EN_INCR Enables with Increment condition 0x2 INT_EN_OVER Enables with Overflow condition 0x3 INT_GEN_DIS Disables Interrupt generation ESRC: Event Counter Source Value Name Description 0x0 CNT_DIS Counter Disabled 0x1 SRC_CO Source is CO 0x2 SRC_DRHIT Source is DRHIT 0x3 SRC_DRREQ Source is DRREQ 0x4 SRC_DWHIT Source is DWHIT 0x5 SRC_DWREQ Source is DWREQ 0x6 SRC_DWTREQ Source is DWTREQ 0x7 SRC_IRHIT Source is IRHIT 0x8 SRC_IRREQ Source is IRREQ 0x9 SRC_WA Source is WA 0xa SRC_IPFALLOC Source is IPFALLOC 0xb SRC_EPFHIT Source is EPFHIT 0xc SRC_EPFALLOC Source is EPFALLOC 0xd SRC_SRRCVD Source is SRRCVD 0xe SRC_SRCONF Source is SRCONF 0xf SRC_EPFRCVD Source is EPFRCVD DS60001476B-page 94  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.9 L2CC Event Counter 0 Configuration Register Name: L2CC_ECFGR0 Address: 0x00A00208 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 4 3 2 1 ESRC 0 EIGEN EIGEN: Event Counter Interrupt Generation Value Name Description 0x0 INT_DIS Disables (default) 0x1 INT_EN_INCR Enables with Increment condition 0x2 INT_EN_OVER Enables with Overflow condition 0x3 INT_GEN_DIS Disables Interrupt generation ESRC: Event Counter Source Value Name Description 0x0 CNT_DIS Counter Disabled 0x1 SRC_CO Source is CO 0x2 SRC_DRHIT Source is DRHIT 0x3 SRC_DRREQ Source is DRREQ 0x4 SRC_DWHIT Source is DWHIT 0x5 SRC_DWREQ Source is DWREQ 0x6 SRC_DWTREQ Source is DWTREQ 0x7 SRC_IRHIT Source is IRHIT 0x8 SRC_IRREQ Source is IRREQ 0x9 SRC_WA Source is WA 0xa SRC_IPFALLOC Source is IPFALLOC 0xb SRC_EPFHIT Source is EPFHIT 0xc SRC_EPFALLOC Source is EPFALLOC 0xd SRC_SRRCVD Source is SRRCVD 0xe SRC_SRCONF Source is SRCONF 0xf SRC_EPFRCVD Source is EPFRCVD  2017 Microchip Technology Inc. DS60001476B-page 95 SAMA5D2 SERIES 14.5.10 L2CC Event Counter 1 Value Register Name: L2CC_EVR1 Address: 0x00A0020C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VALUE 23 22 21 20 VALUE 15 14 13 12 VALUE 7 6 5 4 VALUE Note: Counter 1 must be disabled in the L2CC Event Counter 1 Configuration Register prior to any write access to this register. VALUE: Event Counter Value Value returns the number of instance of the selected event. If a counter reaches its maximum value, it remains saturated at that value until it is reset. DS60001476B-page 96  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.11 L2CC Event Counter 0 Value Register Name: L2CC_EVR0 Address: 0x00A00210 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VALUE 23 22 21 20 VALUE 15 14 13 12 VALUE 7 6 5 4 VALUE Note: Counter 0 must be disabled in the L2CC Event Counter 0 Configuration Register prior to any write access to this register. VALUE: Event Counter Value Value returns the number of instance of the selected event. If a counter reaches its maximum value, it remains saturated at that value until it is reset.  2017 Microchip Technology Inc. DS60001476B-page 97 SAMA5D2 SERIES 14.5.12 L2CC Interrupt Mask Register Name: L2CC_IMR Address: 0x00A00214 Access: Programmable in Auxiliary Control Register 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DECERR 7 SLVERR 6 ERRRD 5 ERRRT 4 ERRWD 3 ERRWT 2 PARRD 1 PARRT 0 ECNTR ECNTR: Event Counter 1/0 Overflow Increment PARRT: Parity Error on L2 Tag RAM, Read PARRD: Parity Error on L2 Data RAM, Read ERRWT: Error on L2 Tag RAM, Write ERRWD: Error on L2 Data RAM, Write ERRRT: Error on L2 Tag RAM, Read ERRRD: Error on L2 Data RAM, Read SLVERR: SLVERR from L3 Memory DECERR: DECERR from L3 Memory 0: Masked. This is the default value. 1: Enabled. DS60001476B-page 98  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.13 L2CC Masked Interrupt Status Register Name: L2CC_MISR Address: 0x00A00218 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DECERR 7 SLVERR 6 ERRRD 5 ERRRT 4 ERRWD 3 ERRWT 2 PARRD 1 PARRT 0 ECNTR ECNTR: Event Counter 1/0 Overflow Increment PARRT: Parity Error on L2 Tag RAM, Read PARRD: Parity Error on L2 Data RAM, Read ERRWT: Error on L2 Tag RAM, Write ERRWD: Error on L2 Data RAM, Write ERRRT: Error on L2 Tag RAM, Read ERRRD: Error on L2 Data RAM, Read SLVERR: SLVERR from L3 memory DECERR: DECERR from L3 memory 0: No interrupt has been generated or the interrupt is masked. 1: The input lines have triggered an interrupt.  2017 Microchip Technology Inc. DS60001476B-page 99 SAMA5D2 SERIES 14.5.14 L2CC Raw Interrupt Status Register Name: L2CC_RISR Address: 0x00A0021C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DECERR 7 SLVERR 6 ERRRD 5 ERRRT 4 ERRWD 3 ERRWT 2 PARRD 1 PARRT 0 ECNTR ECNTR: Event Counter 1/0 Overflow Increment PARRT: Parity Error on L2 Tag RAM, Read PARRD: Parity Error on L2 Data RAM, Read ERRWT: Error on L2 Tag RAM, Write ERRWD: Error on L2 Data RAM, Write ERRRT: Error on L2 Tag RAM, Read ERRRD: Error on L2 Data RAM, Read SLVERR: SLVERR from L3 memory DECERR: DECERR from L3 memory 0: No interrupt has been generated. 1: The input lines have triggered an interrupt. DS60001476B-page 100  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.15 L2CC Interrupt Clear Register Name: L2CC_ICR Address: 0x00A00220 Access: Programmable in Auxiliary Control Register 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DECERR 7 SLVERR 6 ERRRD 5 ERRRT 4 ERRWD 3 ERRWT 2 PARRD 1 PARRT 0 ECNTR ECNTR: Event Counter 1/0 Overflow Increment PARRT: Parity Error on L2 Tag RAM, Read PARRD: Parity Error on L2 Data RAM, Read ERRWT: Error on L2 Tag RAM, Write ERRWD: Error on L2 Data RAM, Write ERRRT: Error on L2 Tag RAM, Read ERRRD: Error on L2 Data RAM, Read SLVERR: SLVERR from L3 memory DECERR: DECERR from L3 memory 0: No effect. Read returns zero. 1: Clears the corresponding bit in the Raw Interrupt Status Register.  2017 Microchip Technology Inc. DS60001476B-page 101 SAMA5D2 SERIES 14.5.16 L2CC Cache Synchronization Register Name: L2CC_CSR Address: 0x00A00730 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 C C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. DS60001476B-page 102  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.17 L2CC Invalidate Physical Address Line Register Name: L2CC_IPALR Address: 0x00A00770 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 2 – 1 – 0 C TAG 23 22 21 20 TAG 15 14 13 12 TAG 7 IDX 6 IDX 5 4 – 3 – C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. IDX: Index Number TAG: Tag Number  2017 Microchip Technology Inc. DS60001476B-page 103 SAMA5D2 SERIES 14.5.18 L2CC Invalidate Way Register Name: L2CC_IWR Address: 0x00A0077C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 WAY7 6 WAY6 5 WAY5 4 WAY4 3 WAY3 2 WAY2 1 WAY1 0 WAY0 WAYx: Invalidate Way Number x 0: The corresponding way is totally invalidated. 1: Invalidates the way. This bit is read as ‘1’ as long as invalidation of the way is in progress. DS60001476B-page 104  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.19 L2CC Clean Physical Address Line Register Name: L2CC_CPALR Address: 0x00A007B0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 2 – 1 – 0 C TAG 23 22 21 20 TAG 15 14 13 12 TAG 7 IDX 6 IDX 5 4 – 3 – C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. IDX: Index number TAG: Tag number  2017 Microchip Technology Inc. DS60001476B-page 105 SAMA5D2 SERIES 14.5.20 L2CC Clean Index Register Name: L2CC_CIR Address: 0x00A007B8 Access: Read/Write 31 – 30 29 WAY 28 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 12 11 10 9 8 7 6 IDX 5 2 – 1 – 0 C IDX 4 – 3 – C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. IDX: Index number WAY: Way number DS60001476B-page 106  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.21 L2CC Clean Way Register Name: L2CC_CWR Address: 0x00A007BC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 WAY7 6 WAY6 5 WAY5 4 WAY4 3 WAY3 2 WAY2 1 WAY1 0 WAY0 WAYx: Clean Way Number x 0: The corresponding way is totally cleaned. 1: Cleans the way. This bit is read as ‘1’ as long as cleaning of the way is in progress.  2017 Microchip Technology Inc. DS60001476B-page 107 SAMA5D2 SERIES 14.5.22 L2CC Clean Invalidate Physical Address Line Register Name: L2CC_CIPALR Address: 0x00A007F0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 2 – 1 – 0 C TAG 23 22 21 20 TAG 15 14 13 12 TAG 7 IDX 6 IDX 5 4 – 3 – C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. IDX: Index Number TAG: Tag Number DS60001476B-page 108  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.23 L2CC Clean Invalidate Index Register Name: L2CC_CIIR Address: 0x00A007F8 Access: Read/Write 31 – 30 29 WAY 28 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 12 11 10 9 8 7 6 IDX 5 2 – 1 – 0 C IDX 4 – 3 – C: Cache Synchronization Status 0: No background operation is in progress. When written, must be zero. 1: A background operation is in progress. IDX: Index Number WAY: Way Number  2017 Microchip Technology Inc. DS60001476B-page 109 SAMA5D2 SERIES 14.5.24 L2CC Clean Invalidate Way Register Name: L2CC_CIWR Address: 0x00A007FC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 WAY7 6 WAY6 5 WAY5 4 WAY4 3 WAY3 2 WAY2 1 WAY1 0 WAY0 WAYx: Clean Invalidate Way Number x 0: The corresponding way is totally invalidated and cleaned. 1: Invalidates and cleans the way. This bit is read as ‘1’ as long as invalidation and cleaning of the way is in progress. DS60001476B-page 110  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.25 L2CC Data Lockdown Register Name: L2CC_DLKR Address: 0x00A00900 Access: Programmable in Auxiliary Control Register 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 DLK7 6 DLK6 5 DLK5 4 DLK4 3 DLK3 2 DLK2 1 DLK1 0 DLK0 DLKx: Data Lockdown in Way Number x 0: Allocation can occur in the corresponding way. 1: There is no allocation in the corresponding way.  2017 Microchip Technology Inc. DS60001476B-page 111 SAMA5D2 SERIES 14.5.26 L2CC Instruction Lockdown Register Name: L2CC_ILKR Address: 0x00A00904 Access: Programmable in Auxiliary Control Register 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 ILK7 6 ILK6 5 ILK5 4 ILK4 3 ILK3 2 ILK2 1 ILK1 0 ILK0 ILKx: Instruction Lockdown in Way Number x 0: Allocation can occur in the corresponding way. 1: There is no allocation in the corresponding way. DS60001476B-page 112  2017 Microchip Technology Inc. SAMA5D2 SERIES 14.5.27 L2CC Debug Control Register Name: L2CC_DCR Address: 0x00A00F40 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 SPNIDEN 1 DWB 0 DCL DCL: Disable Cache Linefill 0: Enables cache linefills. This is the default value. 1: Disables cache linefills. DWB: Disable Write-back, Force Write-through 0: Enables write-back behavior. This is the default value. 1: Forces write-through behavior. SPNIDEN: SPNIDEN Value Reads value of the SPNIDEN input.  2017 Microchip Technology Inc. DS60001476B-page 113 SAMA5D2 SERIES 14.5.28 L2CC Prefetch Control Register Name: L2CC_PCR Address: 0x00A00F60 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 DLEN 29 INSPEN 28 DATPEN 27 DLFWRDIS 26 – 25 – 24 PDEN 23 IDLEN 22 – 21 NSIDEN 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 3 2 OFFSET 1 0 OFFSET: Prefetch Offset You must only use the Prefetch offset values of 0-7, 15, 23, and 31 for these bits. The L2CC does not support the other values. NSIDEN: Not Same ID on Exclusive Sequence Enable 0: Read and write portions of a non-cacheable exclusive sequence have the same AXI ID when issued to L3. This is the default value. 1: Read and write portions of a non-cacheable exclusive sequence do not have the same AXI ID when issued to L3. IDLEN: INCR Double Linefill Enable 0: The L2CC does not issue INCR 8x64-bit read bursts to L3 on reads that miss in the L2 cache. This is the default value. 1: The L2CC can issue INCR 8x64-bit read bursts to L3 on reads that miss in the L2 cache. Note: This bit can only be used if the DLEN bit is set HIGH. See Section 14.4.1 “Double Linefill Issuing” for details on double linefill functionality. PDEN: Prefetch Drop Enable 0: The L2CC does not discard prefetch reads issued to L3. This is the default value. 1: The L2CC discards prefetch reads issued to L3 when there is a resource conflict with explicit reads. DLFWRDIS: Double Linefill on WRAP Read Disable 0: Double linefill on WRAP read is enabled. This is the default value. 1: Double linefill on WRAP read is disabled. Note: This bit can only be used if the DLEN bit is set HIGH. See Section 14.4.1 “Double Linefill Issuing” for details on double linefill functionality. DATPEN: Data Prefetch Enable 0: Data prefetching is disabled. This is the default value. 1: Data prefetching is enabled. INSPEN: Instruction Prefetch Enable 0: Instruction prefetching is disabled. This is the default value. 1: Instruction prefetching is enabled. DLEN: Double Linefill Enable 0: The L2CC always issues 4x64-bit read bursts to L3 on reads that miss in the L2 cache. This is the default value. 1: The L2CC issues 8x64-bit read bursts to L3 on reads that miss in the L2 cache. DS60001476B-page 114  2017 Microchip Technology Inc. SAMA5D2 SERIES See Section 14.4.1 “Double Linefill Issuing” for details on double linefill functionality.  2017 Microchip Technology Inc. DS60001476B-page 115 SAMA5D2 SERIES 14.5.29 L2CC Power Control Register Name: L2CC_POWCR Address: 0x00A00F80 Access: Read/Write in Secure mode Read-only in Non-secure mode 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 DCKGATEN 0 STBYEN STBYEN: Standby Mode Enable 0: Disabled. This is the default value. 1: Enabled. DCKGATEN: Dynamic Clock Gating Enable 0: Disabled. This is the default value. 1: Enabled. DS60001476B-page 116  2017 Microchip Technology Inc. SAMA5D2 SERIES 15. Debug and Test Features 15.1 Description The device features a number of complementary debug and test capabilities. A common JTAG/ICE (In-Circuit Emulator) port is used for standard debugging functions, such as downloading code and single-stepping through programs. A 2-pin debug port Serial Wire Debug (SWD) replaces the 5-pin JTAG port and provides an easy and risk-free alternative to JTAG as the two signals, SWDIO and SWCLK, are overlaid on the TMS and TCK pins, allowing for bi-modal devices that provide the other JTAG signals. These extra JTAG pins can be switched to other uses when in SWD mode. A set of dedicated debug and test input/output pins gives direct access to these capabilities from a PC-based test environment. 15.2 Embedded Characteristics • Cortex-A5 In-circuit Emulator - Two Real-time Watchpoint Units - Two Independent Registers: Debug Control Register and Debug Status Register - Test Access Port Accessible through JTAG Protocol - Debug Communications Channel - Serial Wire Debug - Trace • Chip ID Register • IEEE1149.1 JTAG Boundary-scan on All Digital Pins • ETM, ETB: 8-Kbyte Embedded Trace Buffer  2017 Microchip Technology Inc. DS60001476B-page 117 SAMA5D2 SERIES 15.3 Debug and Test Block Diagrams Figure 15-1: DS60001476B-page 118 Debug and Test General Block Diagram  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 15-2: Debug and Test Interface Block Diagram TMS / SWDIO TCK / SWCLK TDI NTRST Boundary Port SWD/ICE/JTAG SELECT JTAGSEL TDO SWD DEBUG PORT ICE/JTAG DEBUG PORT Reset and Test POR TST Cortex-A5  2017 Microchip Technology Inc. DS60001476B-page 119 SAMA5D2 SERIES 15.4 15.4.1 Application Examples Debug Environment Figure 15-3 shows a complete debug environment example. The ICE/JTAG interface is used for standard debugging functions, such as downloading code and single-stepping through the program. A software debugger running on a personal computer provides the user interface for configuring a Trace Port interface utilizing the ICE/JTAG interface. Figure 15-3: Application Debug and Trace Environment Example Host Debugger PC ICE/JTAG Interface ICE/JTAG Connector RS232 Connector SAM device Terminal SAM-based Application Board 15.4.2 Test Environment Figure 15-4 shows a test environment example. Test vectors are sent and interpreted by the tester. In this example, the “board in test” is designed using a number of JTAG-compliant devices. These devices can be connected to form a single scan chain. Figure 15-4: Application Test Environment Example Test Adaptor Tester JTAG Interface ICE/JTAG Chip n SAM device Chip 2 Chip 1 SAM-based Application Board In Test DS60001476B-page 120  2017 Microchip Technology Inc. SAMA5D2 SERIES 15.5 Debug and Test Pin Description Table 15-1: Debug and Test Pin List Pin Name Function Type Active Level Reset/Test NRST Microprocessor Reset Input Low TST Test Mode Select Input – NTRST Test Reset Signal Input – ICE and JTAG TCK/SWCLK Test Clock/Serial Wire Clock Input – TDI Test Data In Input – TDO Test Data Out Output – TMS/SWDIO Test Mode Select/Serial Wire Input/Output I/O – JTAGSEL JTAG Selection Input – 15.6 15.6.1 Functional Description Test Pin One dedicated pin, TST, is used to define the device operating mode. The user must make sure that this pin is tied at low level to ensure normal operating conditions. Other values associated with this pin are reserved for manufacturing test. 15.6.2 EmbeddedICE The Cortex-A5 EmbeddedICE-RT is supported via the ICE/JTAG port. It is connected to a host computer via an ICE interface.The internal state of the Cortex-A5 is examined through an ICE/JTAG port which allows instructions to be serially inserted into the pipeline of the core without using the external data bus. Therefore, when in debug state, a store-multiple (STM) can be inserted into the instruction pipeline. This exports the contents of the Cortex-A5 registers. This data can be serially shifted out without affecting the rest of the system. There are two scan chains inside the Cortex-A5 processor which support testing, debugging, and programming of the EmbeddedICE-RT. The scan chains are controlled by the ICE/JTAG port. EmbeddedICE mode is selected when JTAGSEL is low. It is not possible to switch directly between ICE and JTAG operations. A chip reset must be performed after JTAGSEL is changed. For further details on the EmbeddedICE-RT, see the ARM document: ARM IHI 0031A_ARM_debug_interface_v5.pdf 15.6.3 JTAG Signal Description TMS is the Test Mode Select input which controls the transitions of the test interface state machine. TDI is the Test Data Input line which supplies the data to the JTAG registers (Boundary Scan Register, Instruction Register, or other data registers). TDO is the Test Data Output line which is used to serially output the data from the JTAG registers to the equipment controlling the test. It carries the sampled values from the boundary scan chain (or other JTAG registers) and propagates them to the next chip in the serial test circuit. NTRST (optional in IEEE Standard 1149.1) is a Test-ReSeT input which is mandatory in ARM cores and used to reset the debug logic. On Cortex-A5-based cores, NTRST is a Power On Reset output. It is asserted on power on. If necessary, the user can also reset the debug logic with the NTRST pin assertion during 2.5 MCK periods. TCK is the Test ClocK input which enables the test interface. TCK is pulsed by the equipment controlling the test and not by the tested device. It can be pulsed at any frequency.  2017 Microchip Technology Inc. DS60001476B-page 121 SAMA5D2 SERIES 15.6.4 Chip Access Using JTAG Connection The JTAG connection is not enabled by default on this chip at delivery due to the secure ROM code implementation. By default, the SAMA5D2 devices boot in Standard mode and not in Secure mode. When the secure ROM code starts, it disables the JTAG access for the entire boot sequence. If the secure ROM code does not find any program in the external memory, it enables the USB connection and the serial port and waits for a dedicated command to switch the chip into Secure mode. If any other character is received, the secure ROM code starts the standard SAM-BA® monitor, locks access to the ROM memory, and enables the JTAG. The chip can then be accessed using the JTAG connection. If the secure ROM code finds a bootable program, it automatically disables ROM access and enables the JTAG connection just before launching the program. The procedure to enable JTAG access is as follows: • Connect your computer to the board with JTAG and USB (J20 USB-A) • Power on the chip • Open a terminal console (TeraTerm or HyperTerminal, etc.) on your computer and connect to the USB CDC Serial COM port related to the J14 connector on the board • Send the '#' character. You will see then the prompt '>' character sent by the device (indicating that the Standard SAM-BA Monitor is running) • Use the Standard SAM-BA Monitor to connect to the chip with JTAG Note that you don't need to follow this sequence in order to connect the Standard SAM-BA Monitor with USB. 15.6.5 IEEE 1149.1 JTAG Boundary Scan IEEE 1149.1 JTAG Boundary Scan allows pin-level access independent of the device packaging technology. IEEE 1149.1 JTAG Boundary Scan is enabled when JTAGSEL is high. The SAMPLE, EXTEST and BYPASS functions are implemented. In ICE debug mode, the ARM processor responds with a non-JTAG chip ID that identifies the processor to the ICE system. This is not IEEE 1149.1 JTAG-compliant. It is not possible to switch directly between JTAG and ICE operations. A chip reset must be performed after JTAGSEL is changed. A Boundary-scan Descriptor Language (BSDL) file is provided to set up test. DS60001476B-page 122  2017 Microchip Technology Inc. SAMA5D2 SERIES 15.7 Boundary JTAG ID Register Access: Read-only 31 30 29 28 27 VERSION 23 22 26 25 24 PART NUMBER 21 20 19 18 17 16 10 9 8 PART NUMBER 15 14 13 12 11 PART NUMBER 7 6 MANUFACTURER IDENTITY 5 4 MANUFACTURER IDENTITY 3 2 1 0 1 VERSION[31:28]: Product Version Number Set to 0x0. PART NUMBER[27:12]: Product Part Number Product part number is 0x5B39. MANUFACTURER IDENTITY[11:1] Set to 0x01F. Bit[0] required by IEEE Std. 1149.1. Set to 0x1. JTAG ID Code value is 0x05B3903F.  2017 Microchip Technology Inc. DS60001476B-page 123 SAMA5D2 SERIES 15.8 Cortex-A5 DP Identification Code Register IDCODE The Identification Code Register is always present on all DP implementations. It provides identification information about the ARM Debug Interface. 15.8.1 JTAG Debug Port (JTAG-DP) It is accessed using its own scan chain, the JTAG-DP Device ID Code Register. Access: Read-only 31 30 29 28 27 VERSION 23 22 26 25 24 PART NUMBER 21 20 19 18 17 16 10 9 8 PART NUMBER 15 14 13 12 11 PART NUMBER 7 6 5 DESIGNER 4 DESIGNER 3 2 1 0 1 VERSION[31:28]: Product Version Number Set to 0x0. PART NUMBER[27:12]: Product Part Number Product part Number is 0xBA00 DESIGNER[11:1] Set to 0x23B. Bit[0] required by IEEE Std. 1149.1. Set to 0x1. Debug Port JTAG IDCODE value is 0x4BA00477. DS60001476B-page 124  2017 Microchip Technology Inc. SAMA5D2 SERIES 15.8.2 Serial Wire Debug Port (SW-DP) It is at address 0x0 on read operations when the APnDP bit = 0. Access to the Identification Code Register is not affected by the value of the CTRLSEL bit in the Select Register Access: Read-only 31 30 29 28 27 VERSION 23 22 26 25 24 PART NUMBER 21 20 19 18 17 16 9 8 1 0 PART NUMBER 15 14 13 12 11 10 PART NUMBER 7 6 5 DESIGNER 4 DESIGNER 3 2 1 VERSION[31:28]: Product Version Number Set to 0x0. PART NUMBER[27:12]: Product Part Number Product part Number is 0xBA01 DESIGNER[11:1] Set to 0x23B. Bit[0] required by IEEE Std. 1149.1. Set to 0x1. Debug Port Serial Wire IDCODE is 0x5ba02477.  2017 Microchip Technology Inc. DS60001476B-page 125 SAMA5D2 SERIES 16. Standard Boot Strategies 16.1 Description The system always boots from the ROM memory at address 0x0. The ROM code is a boot program contained in the embedded ROM. It is also called “First level boot loader”. This microcontroller can be configured to run a Standard Boot mode or a Secure Boot mode. More information on how the Secure Boot mode can be enabled, and how the chip operates in this mode, is provided in the document “SAMA5D2x Secure Boot Strategy”, document no. 44040. To obtain this application note and additional information about the secure boot and related tools, contact a Microchip sales representative. By default, the chip starts in Standard Boot mode. Note: 16.2 JTAG access is disabled during the execution of the ROM code sequence. It is re-enabled when jumping into SRAM when a valid code has been found on an external NVM, at the same time the ROM memory is hidden. If no valid boot has been found on an external NVM, the ROM code enables the USB connection and one UART serial port, the ROM code starts the standard SAM-BA monitor, locks access to the ROM memory and re-enables the JTAG connection. Flow Diagram The ROM code global flow is shown in Figure 16-1. Figure 16-1: ROM Code Flow Diagram Chip Setup Valid boot code found in one NVM Yes Copy and run it in internal SRAM No DISABLE_MONITOR Fuse bit set Yes while(1) No SAM-BA Monitor 16.3 Chip Setup When the chip is powered on, the processor clock (PCK) and the master clock (MCK) source is the 12 MHz fast RC oscillator. The ROM code performs a low-level initialization that follows the steps described below: 1. 2. 3. 4. Stack Setup for ARM supervisor mode. PLLA Initialization Master Clock Selection: when the PLLA is stabilized, the Master Clock source is switched from internal 12 MHz RC to PLLA. The PMC Status Register is polled to wait for MCK Ready. PCK and MCK are now the Main Clock. C Variable Initialization: non zero-initialized data is initialized in the RAM (copy from ROM to RAM). Zero-initialized data is set to 0 in the RAM. For clock frequencies, see Table 16-6. DS60001476B-page 126  2017 Microchip Technology Inc. SAMA5D2 SERIES Note: 16.4 No external crystal or clock is needed during the external boot memories sequence. An external clock source is checked before the launch of the SAM-BA monitor to get a more accurate clock signal for USB. Boot Configuration The boot sequence is controlled using a Boot Configuration Word in the Fuse area. 16.4.1 Boot Configuration Word The Boot Configuration Word allows several customizations of the Boot Sequence: • To configure the IO Set where the external memories used to boot are connected (see Section 16.4.8 “Hardware and Software Constraints” for a description of the IO sets) • To disable the boot on selected memories • To configure the UART port used as a terminal console • To configure the JTAG pins used for debug See “Section 16.4.4 “Boot Configuration Word” for a detailed description of all the bitfields in this word. By default, the value of this word is 0x0. For MRL A and B parts, the ROM code does not try to detect a valid bootable software in any external memory, and runs directly the SAMBA monitor. See Figure 16-3. For MRL C parts, the ROM code only tries to boot on SDMMC1 and SDMMC0 memory interfaces and then run the SAM-BA monitor. See Figure 16-4. During prototyping phases, the value of this fuse word can be overridden by the content of a backup register. The conditions to enable this feature are as follows: • The fuse bit DISABLE_BSCR must not be set (default value). • The Boot Sequence Controller Configuration Register (BSC_CR) must have the BUREG_VALID bit set and indicate in BUREG_INDEX which register has to be used. Using BUREG allows the user to test several boot configuration options, incuding Secure Boot Mode, without burning fuses. Note: VDDBU must be connected in order to benefit from this feature. However, in production, it is highly recommended to disable this feature and to write the boot configuration in fuses.  2017 Microchip Technology Inc. DS60001476B-page 127 SAMA5D2 SERIES Figure 16-2: Boot Configuration Loading Read Boot Configuration in Fuse Yes DISABLE_BSCR flag set Boot sequence uses fuse configuration No Read BSC_CR No BUREG_VALID bit set Boot sequence uses fuse configuration Yes Read the two BSCR LSB to know which BUREG to use Boot sequence uses BUREG configuration DS60001476B-page 128  2017 Microchip Technology Inc. SAMA5D2 SERIES 16.4.2 Boot Sequence Controller Configuration Register Name: BSC_CR Address:0xF8048054 Access: Read-write 31 30 29 28 27 26 25 24 19 18 17 16 9 – 8 – WPKEY 23 22 21 20 WPKEY 15 – 14 – 13 – 12 – 11 – 10 – 7 – 6 – 5 – 4 – 3 2 BUREG_VALID – 1 0 BUREG_INDEX WPKEY: Write Protect Key (Write-only) Value Name 0x6683 PASSWD Description Writing any other value in this field aborts the write operation of the BOOT field. Always reads as 0. BUREG_VALID: Validate the data in BUREG_INDEX field 0: No BUREG contains valid Boot Configuration data. 1: The BUREG indicated in BUREG_INDEX contains Boot Configuration data for use in configuring the boot sequence. BUREG_INDEX: Select the BUREG where the Boot Configuration data shall be read Value Name 0 BUREG_0 Use BUREG 0 value 1 BUREG_1 Use BUREG 1 value 2 BUREG_2 Use BUREG 2 value 3 BUREG_3 Use BUREG 3 value  2017 Microchip Technology Inc. Description DS60001476B-page 129 SAMA5D2 SERIES 16.4.3 Backup Registers (BUREG) The 4 BUREGs used to override the Boot Configuration Word in Fuse are at addresses: - 0xF8045400 0xF8045404 0xF8045408 0xF804540C 16.4.4 Boot Configuration Word Reset: 0x00000000 31 30 – – 23 22 DNU DISABLE_ BSCR 15 7 29 SECURE_ MODE 28 27 26 25 DNU DNU DNU DNU 21 20 19 17 QSPI_XIP_ MODE DNU DNU 18 EXT_MEM_ BOOT_ ENABLE 14 13 UART_CONSOLE 12 11 SDMMC_1 10 SDMMC_0 9 6 4 3 2 1 5 SPI_1 SPI_0 24 DISABLE_ MONITOR 16 JTAG_IO_SET 8 NFC QSPI_1 0 QSPI_0 The Boot Configuration Word comprises the 32 boot configuration bits (see Table 16-11 “Customer Fuse Matrix”). Note: To avoid any malfunctioning, the user must not write the “DO NOT USE (DNU)” fuse bits. SECURE_MODE: Enable Secure Boot Mode 0: Standard Boot Sequence 1: Secure Boot Sequence DISABLE_MONITOR: Disable SAM-BA Monitor 0: If no boot file found, launch SAM-BA Monitor. 1: SAM-BA Monitor never launched. DISABLE_BSCR: Disable Read of BSC_CR 0: If the BUREG index in the BSC_CR is valid, its data replace Fuse configuration bits. 1: Does not read BSC_CR content, so the Boot settings are those from the Fuse. QSPI_XIP_MODE: Enable XIP Mode on QSPI Flash 0: QSPI is accessed in QSPI mode and data copied into internal SRAM. 1: QSPI is accessed in XIP mode, and the bootstrap directly executed from it. EXT_MEM_BOOT_ENABLE: Enable Boot on External Memories 0: No external memory boot performed. 1: External memory boot enabled. JTAG_IO_SET: Select the pins used for JTAG access Value Name 0 JTAG_IOSET_1 DS60001476B-page 130 Description Use JTAG IO Set 1  2017 Microchip Technology Inc. SAMA5D2 SERIES Value Name Description 1 JTAG_IOSET_2 Use JTAG IO Set 2 2 JTAG_IOSET_3 Use JTAG IO Set 3 3 JTAG_IOSET_4 Use JTAG IO Set 4(1) 1: In Errata Section, see Section 71.1.19 “ROM Code: Using JTAG IOSET 4” (for SAMA5D2 MRL C Parts), Section 71.2.20 “ROM Code: Using JTAG IOSET 4” (for SAMA5D2 MRL B Parts) or Section 71.3.36 “ROM Code: Using JTAG IOSET 4” (for SAMA5D2 MRL A Parts). UART_CONSOLE: Select the Pins and UART Interface Used as a Console Terminal Value Name Description 0 UART_1_IOSET_1 Use UART1 IO Set 1 1 UART_0_IOSET_1 Use UART0 IO Set 1 2 UART_1_IOSET_2 Use UART1 IO Set 2 3 UART_2_IOSET_1 Use UART2 IO Set 1 4 UART_2_IOSET_2 Use UART2 IO Set 2 5 UART_2_IOSET_3 Use UART2 IO Set 3 6 UART_3_IOSET_1 Use UART3 IO Set 1 7 UART_3_IOSET_2 Use UART3 IO Set 2 8 UART_3_IOSET_3 Use UART3 IO Set 3 9 UART_4_IOSET_1 Use UART4 IO Set 1 10 DISABLED No console terminal 11 DISABLED No console terminal 12 DISABLED No console terminal 13 DISABLED No console terminal 14 DISABLED No console terminal 15 DISABLED No console terminal SDMMC_1: Disable SDCard/e.MMC Boot on SDMMC_1 0: Boots on SDMMC_1 using SDMMC_1 PIO Set 1. 1: Disables boot on SDMMC_1. Note: After the first boot, the boot on SDMMC_1 can be disabled by setting this bit. SDMMC_0: Disable SDCard/e.MMC Boot on SDMMC_0 0: Boots on SDMMC_0 using SDMMC_0 PIO Set 1. 1: Disables boot on SDMMC_0. Note: After the first boot, the boot on SDMMC_0 can be disabled by setting this bit. NFC: Select the PIO Set Used for NFC Boot Value Name 0 NFC_IOSET_1 Use NFC PIO Set 1 1 NFC_IOSET_2 Use NFC PIO Set 2 2 DISABLED NFC boot is disabled 3 DISABLED NFC boot is disabled  2017 Microchip Technology Inc. Description DS60001476B-page 131 SAMA5D2 SERIES SPI_1: Select the PIO Set Used for SPI_1 Boot Value Name Description 0 SPI_1_IOSET_1 Use SPI_1 PIO Set 1 1 SPI_1_IOSET_2 Use SPI_1 PIO Set 2 2 SPI_1_IOSET_3 Use SPI_1 PIO Set 3 3 DISABLED SPI_1 boot is disabled SPI_0: Select the PIO Set Used for SPI_0 Boot Value Name Description 0 SPI_0_IOSET_1 Use SPI_0 PIO Set 1 1 SPI_0_IOSET_2 Use SPI_0 PIO Set 2 2 DISABLED SPI_0 boot is disabled 3 DISABLED SPI_0 boot is disabled QSPI_1: Select the PIO Set Used for QSPI_1 Boot Value Name Description 0 QSPI_1_IOSET_1 Use QSPI_1 PIO Set 1 1 QSPI_1_IOSET_2 Use QSPI_1 PIO Set 2 2 QSPI_1_IOSET_3 Use QSPI_1 PIO Set 3 3 DISABLED QSPI_1 boot is disabled QSPI_0: Select the PIO Set Used for QSPI_0 Boot Value Name 0 QSPI_0_IOSET_1 Use QSPI_0 PIO Set 1 1 QSPI_0_IOSET_2 Use QSPI_0 PIO Set 2 2 QSPI_0_IOSET_3 Use QSPI_0 PIO Set 3 3 DISABLED QSPI_0 boot is disabled DS60001476B-page 132 Description  2017 Microchip Technology Inc. SAMA5D2 SERIES 16.4.5 NVM Boot Sequence The ROM code performs the initialization and valid code detection for the external memories as described below only if those memories are not disabled in the Boot Configuration word. Figure 16-3: NVM Bootloader Program Description for MRL A and MRL B Parts Device Setup No EXT_MEM_BOOT_ENABLE Fuse bit set Yes SDMMC_1 Boot Yes Copy from SD Card / e.MMC to SRAM Run SDMMC Bootloader Yes Copy from SD Card / e.MMC to SRAM Run SDMMC Bootloader Yes Copy from NAND Flash to SRAM Run NAND Bootloader Yes Copy from SPI Flash to SRAM Run SPI Bootloader Yes Copy from SPI Flash to SRAM Run SPI Bootloader Yes Copy from QSPI Flash to SRAM Run QSPI Bootloader Yes Copy from QSPI Flash to SRAM Run QSPI Bootloader No SDMMC_0 Boot No NFC Boot No SPI_0 Boot No SPI_1 Boot No QSPI_0 Boot No QSPI_1 Boot No DISABLE_MONITOR Fuse bit set Yes while(1) SAM-BA Monitor  2017 Microchip Technology Inc. DS60001476B-page 133 SAMA5D2 SERIES Figure 16-4: NVM Bootloader Program Description for MRL C Parts Device Setup SDMMC_1 Boot Yes Copy from SD Card / e.MMC to SRAM Run SDMMC Bootloader Yes Copy from SD Card / e.MMC to SRAM Run SDMMC Bootloader Yes Copy from NAND Flash to SRAM Run NAND Bootloader Yes Copy from SPI Flash to SRAM Run SPI Bootloader Yes Copy from SPI Flash to SRAM Run SPI Bootloader Yes Copy from QSPI Flash to SRAM Run QSPI Bootloader Yes Copy from QSPI Flash to SRAM Run QSPI Bootloader No SDMMC_0 Boot No No EXT_MEM_BOOT_ENABLE Fuse bit set Yes NFC Boot No SPI_0 Boot No SPI_1 Boot No QSPI_0 Boot No QSPI_1 Boot No DISABLE_MONITOR Fuse bit set Yes while(1) SAM-BA Monitor DS60001476B-page 134  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 16-5: NVM Boot Diagram Start Initialize NVM Initialization OK? No Restore the reset values for the peripherals and jump to the next boot solution Yes Valid code detection in NVM NVM contains valid code No Yes Copy the valid code from external NVM to internal SRAM Restore the reset values for the peripherals. Perform the REMAP and set the PC to 0 to jump to the downloaded application End  2017 Microchip Technology Inc. DS60001476B-page 135 SAMA5D2 SERIES The NVM bootloader program first initializes the PIOs related to the NVM device. Then it configures the right peripheral depending on the NVM and tries to access this memory. If the initialization fails, it restores the reset values for the PIO and the peripheral, and then tries to fulfill the same operations on the next NVM of the sequence. If the initialization is successful, the NVM bootloader program reads the beginning of the NVM and determines if the NVM contains a valid code. If the NVM does not contain a valid code, the NVM bootloader program restores the reset value for the peripherals and then tries to fulfill the same operations on the next NVM of the sequence. If a valid code is found, this code is loaded from the NVM into the internal SRAM and executed by branching at address 0x0000_0000 after remap. This code may be the application code or a second-level bootloader. All the calls to functions are PC-relative and do not use absolute addresses. Figure 16-6: Remap Action after Download Completion 0x0000_0000 0x0000_0000 Internal ROM Internal SRAM REMAP 0x0020_0000 0x0020_0000 Internal SRAM Internal SRAM 16.4.6 Valid Code Detection There are two kinds of valid code detection. 16.4.6.1 ARM Exception Vectors Check The NVM bootloader program reads and analyzes the first 28 bytes corresponding to the first seven ARM exception vectors. Except for the sixth vector, these bytes must implement the ARM instructions for either branch or load PC with PC-relative addressing. Figure 16-7: LDR Opcode 31 1 28 27 1 Figure 16-8: 1 0 0 24 23 1 I P U 20 19 1 W 0 16 15 Rn 12 11 Rd 0 Offset B Opcode 31 1 28 27 1 DS60001476B-page 136 1 0 1 24 23 0 1 0 0 Offset (24 bits)  2017 Microchip Technology Inc. SAMA5D2 SERIES Unconditional instruction: 0xE for bits 31 to 28. Load PC with the PC-relative addressing instruction: - Rn = Rd = PC = 0xF I==0 (12-bit immediate value) P==1 (pre-indexed) U offset added (U==1) or subtracted (U==0) W==1 The sixth vector, at the offset 0x14, contains the size of the image to download. The user must replace this vector with the user’s own vector. This procedure is described below. Figure 16-9: Arm Vector 6 Structure 31 0 Size of the code to download in bytes The value has to be smaller than 64 Kbytes. Example An example of valid vectors: 00 04 08 0c 10 14 18 ea000006 eafffffe ea00002f eafffffe eafffffe 00001234 eafffffe 16.4.6.2 boot.bin File Check B B B B B B B 0x20 0x04 _main 0x0c 0x10 0x14 ← 0x18 Code size = 4660 bytes This method is the one used on FAT-formatted SD Card and e.MMC. The boot program must be a file named “boot.bin” written in the root directory of the file system. Its size must not exceed the maximum size allowed: 64 Kbytes (0x10000). 16.4.7 16.4.7.1 Detailed Memory Boot Procedures NAND Flash Boot: NAND Flash Detection After the NAND Flash interface configuration, a reset command is sent to the memory. Hardware ECC detection and correction are provided by the PMECC peripheral. See Section 37.18 “PMECC Controller Functional Description” for more details. The Boot Program is able to retrieve NAND Flash parameters and ECC requirements using two methods as follows: • The detection of a specific header written at the beginning of the first page of the NAND Flash, or • Through the ONFI parameters for the ONFI-compliant memories However, it is highly recommended to use the NAND Flash Header method (first bullet above) since it indicates exactly how the PMECC has been configured to write the bootable program in the NAND Flash, and not to rely only on the NAND Flash capabilities. Note: Booting on 16-bit NAND Flash is not possible; only 8-bit NAND Flash memories are supported.  2017 Microchip Technology Inc. DS60001476B-page 137 SAMA5D2 SERIES Figure 16-10: Boot NAND Flash Download Start Initialize NAND Flash interface Send Reset command No First page contains valid header Yes NAND Flash is ONFI Compliant No Yes Read NAND Flash and PMECC parameters from the header Read NAND Flash and PMECC parameters from the ONFI Copy the valid code from external NVM to internal SRAM Restore the reset values for the peripherals. Perform the REMAP and set the PC to 0 to jump to the downloaded application End DS60001476B-page 138 Restore the reset values for the peripherals and jump to the next bootable memory  2017 Microchip Technology Inc. SAMA5D2 SERIES • NAND Flash Specific Header Detection (Recommended Solution) This is the first method used to determine NAND Flash parameters. After Initialization and Reset command, the Boot Program reads the first page without an ECC check, to determine whether the NAND parameter header is present. The header is made of 52 times the same 32-bit word (for redundancy reasons) which must contain NAND and PMECC parameters used to correctly perform the read of the rest of the data in the NAND. This 32-bit word is described below: 31 30 29 28 27 - 26 25 eccOffset 24 20 19 18 17 16 key 23 22 21 eccOffset sectorSize 15 14 eccBitReq 13 12 11 10 spareSize 9 8 7 6 5 4 3 2 nbSectorPerPage 1 0 usePmecc spareSize Note: Booting on 16-bit NAND Flash is not possible; only 8-bit NAND Flash memories are supported. usePmecc: Use PMECC 0: Do not use PMECC to detect and correct the data. 1: Use PMECC to detect and correct the data. nbSectorPerPage: Number of Sectors per Page spareSize: Size of the Spare Zone in Bytes eccBitReq: Number of ECC Bits Required 0: 2-bit ECC 1: 4-bit ECC 2: 8-bit ECC 3: 12-bit ECC 4: 24-bit ECC 5: 32-bit ECC sectorSize: Size of the ECC Sector 0: For 512 bytes 1: For 1024 bytes per sector Other value for future use. eccOffset: Offset of the First ECC Byte in the Spare Zone A value below 2 is not allowed and is considered as 2. key: Value 0xC Must be Written here to Validate the Content of the Whole Word. If the header is valid, the Boot Program continues with the detection of a valid code. • ONFI 2.2 Parameters (Not Recommended) In case no valid header is found, the Boot Program checks if the NAND Flash is ONFI-compliant, sending a Read Id command (0x90) with 0x20 as parameter for the address. If the NAND Flash is ONFI-compliant, the Boot Program retrieves the following parameters with the help of the Get Parameter Page command: • • • • Number of bytes per page (byte 80) Number of bytes in spare zone (byte 84) Number of ECC bit corrections required (byte 112) ECC sector size: by default, set to 512 bytes; or to 1024 bytes if the ECC bit capability above is 0xFF  2017 Microchip Technology Inc. DS60001476B-page 139 SAMA5D2 SERIES By default, the ONFI NAND Flash detection turns ON the usePmecc parameter, and the ECC correction algorithm is automatically activated. Once the Boot Program retrieves the parameter, using one of the two methods described above, it reads the first page again, with or without ECC, depending on the usePmecc parameter. Then it looks for a valid code programmed just after the header offset 0xD0. If the code is valid, the program is copied at the beginning of the internal SRAM. Note: 16.4.7.2 Booting on 16-bit NAND Flash is not possible; only 8-bit NAND Flash memories are supported. NAND Flash Boot: PMECC Error Detection and Correction NAND Flash boot procedure uses PMECC to detect and correct errors during NAND Flash read operations in two cases: • When the usePmecc flag is set in a specific NAND header. If the flag is not set, no ECC correction is performed during the NAND Flash page read. • When the NAND Flash has been detected using ONFI parameters. The ROM memory embeds the Galois field tables. The user does not need to embed them in his own software. The Galois field tables are mapped in the ROM just after the ROM code, as described in Figure 16-11. Figure 16-11: Galois Field Table Mapping 0x0000_0000 ROM Code 0x0004_0000 0x0004_8000 Galois field tables for 512-byte sectors correction Galois field tables for 1024-byte sectors correction For a full description and an example of how to use the PMECC detection and correction feature, see the software package dedicated to this device on our website. 16.4.7.3 SDCard / e.MMC Boot The SDCard/e.MMC boot requires the Card Detect pin to be connected. If the level on the Card Detect pin is low, SDCard/e.MMC access is initiated (IOs toggling). If not, no communication with SDCard/e.MMC is performed (no IOs toggling). The SDMMC0 and SDMMC1 pin card detect must be left unconnected if the interfaces are used with a non-removable and non-bootable device (wifi module, etc.). This prevents the ROM code from trying to boot out of these interfaces and avoids a bad behavior of the boot. In the case of non-removable devices (soldered on board), the card detect can be managed by software (refer to "Force Card Detect" bit) or by hardware by enabling the pulldown resistor on SDMMCx_CD PIO after the ROM Code execution. • Supported SDCard Devices SDCard Boot supports all SDCard memories compliant with the SD Memory Card Specification V3.0. This includes SDMMC cards. • e.MMC with Boot Partition DS60001476B-page 140  2017 Microchip Technology Inc. SAMA5D2 SERIES The ROM code first checks if the e.MMC Boot Partition is enabled. If enabled, the ROM code reads the first 64 Kbytes of the boot partition, and copy them into the internal SRAM. • FAT Filesystem boot If no boot partition is enabled on an e.MMC, the boot process continues with a Standard SDCard/e.MMC detection, and the ROM code looks for a “boot.bin” file in the root directory of a FAT12/16/32 file system. 16.4.7.4 SPI Flash Boot Two types of SPI Flash are supported: SPI Serial Flash and SPI DataFlash. The SPI Flash bootloader tries to boot on SPI0, first looking for SPI Serial Flash, and then for SPI DataFlash. It uses only one valid code detection: analysis of ARM exception vectors. The SPI Flash read is done by means of a Continuous Read command from the address 0x0. This command is 0xE8 for DataFlash and 0x0B for Serial Flash devices. • Supported DataFlash Devices The SPI Flash Boot program supports the DataFlash devices listed in Table 16-1. Table 16-1: DataFlash Devices Device Density Page Size (bytes) Number of Pages AT45DB011 1 Mbit 264 512 AT45DB021 2 Mbits 264 1024 AT45DB041 4 Mbits 264 2048 AT45DB081 8 Mbits 264 4096 AT45DB161 16 Mbits 528 4096 AT45DB321 32 Mbits 528 8192 AT45DB642 64 Mbits 1056 8192 AT45DB641 64 Mbits 264 37768 • Supported Serial Flash Devices The SPI Flash Boot program supports all SPI Serial Flash devices responding correctly to both Get Status and Continuous Read commands. 16.4.7.5 QSPI NOR Flash Boot for MRL A and MRL B Important: This section applies to the devices listed in the table below: Table 16-2: SAMA5D2 MRL A and MRL B Parts Device Name ATSAMA5D22A ATSAMA5D24A ATSAMA5D27A ATSAMA5D28A ATSAMA5D21B ATSAMA5D22B ATSAMA5D23B ATSAMA5D24B  2017 Microchip Technology Inc. DS60001476B-page 141 SAMA5D2 SERIES Table 16-2: SAMA5D2 MRL A and MRL B Parts (Continued) Device Name ATSAMA5D26B ATSAMA5D27B ATSAMA5D28B • Definitions (MRL A, MRL B) SPI x-y-z protocol: • Command opcode is sent on x I/O data line(s) with x in {1, 2, 4} • Address is sent on y I/O data line(s) with y in {1, 2, 4} • Data are sent or received on z I/O data lin(s) with z in {1, 2, 4} Relevant combinations are: SPI 1-1-1: legacy SPI protocol using MOSI/IO0 and MISO/IO1 lines SPI 1-1-2: SPI Dual Output using IO0 and IO1 lines SPI 1-2-2: SPI Dual I/O using IO0 and IO1 lines SPI 2-2-2: SPI Dual Command using IO0 and IO1 lines SPI 1-1-4: SPI Quad Output using IO0, IO1, IO2 and IO3 lines SPI 1-4-4: SPI Quad I/O using IO0, IO1, IO2 and IO3 lines SPI 4-4-4: SPI Quad Command using IO0, IO1, IO2 and IO3 lines • Supported QSPI Memory Manufacturers (MRL A, MRL B) The ROM code only supports the three following manufacturers (manufacturer ID): • Cypress (01h) • Micron (20h) • Macronix (C2h) Other manufacturer IDs are ignored: The ROM code jumps to the next Non-Volatile Memory in the Boot Sequence. • SPI Clock Frequency, Phase and Polarity (MRL A, MRL B) The peripheral clock of each QSPI controller is gated from the Master Clock (MCK). The ROM code configures MCK and the QSPI Serial Clock (QSCK). See Table 16-6. The QSPI controller is configured to use Clock Mode 0: Both CPHA and CPOL are cleared in QSPI_SCR. CPOL = 0: The inactive state value of QSCK is logic level zero. CPHA = 0: Data is captured on the leading edge of QSCK and changed on the following edge of QSCK. • QSPI Memory Detection (MRL A, MRL B) The ROM code probes the QSPI memory using JEDEC Read ID commands. However the opcode and the SPI protocol to be used to read the JEDEC ID of the QSPI memory depend on its Manufacturer and its current internal state. • Cypress Cypress memories do not support the SPI 4-4-4 protocol. The command opcode is always sent on the single MOSI/IO1 data line. Hence when writing the 9Fh opcode on MOSI during the first 8 cycles, Cypress memories should always reply on MISO with their JEDEC ID during the following cycles. • Micron Micron memories provide three modes of operation: - Extended SPI: standard SPI protocol upgraded with dual (SPI 1-1-2, SPI 1-2-2) and quad (SPI 1-1-4, SPI 1-4-4) operations - Dual I/O SPI: all commands use the SPI 2-2-2 protocol - Quad I/O SPI: all commands use the SPI 4-4-4 protocol The ROM code supports the Extended and Quad I/O SPI modes but not Dual I/O SPI. In Extended SPI mode, Micron memories replies to the regular Read JEDEC ID opcode using the protocol SPI 1-1-1: the 9Fh opcode is sent on MOSI using eight clock cycles then the JEDEC ID is read from MISO only. DS60001476B-page 142  2017 Microchip Technology Inc. SAMA5D2 SERIES In Quad I/O SPI mode, Micron memories no longer reply to the regular Read JEDEC ID (9Fh) but answer the new Read JEDEC ID Multiple I/O command instead: The AFh op code is sent on the 4 I/O lines using 2 clock cycles, then only the 3 first bytes (1 byte for the Manufacturer ID followed by 2 bytes for the Device ID) of the JEDEC ID are returned by the memory on the 4 I/O lines. The AFh opcode is not supported in Extended SPI mode. • Macronix Macronix memories provide two modes of operation: - SPI: standard SPI protocol upgraded with dual (SPI 1-1-2, SPI 1-2-2) and quad (SPI 1-1-4, SPI 1-4-4) operations. - QPI: all commands use the SPI 4-4-4 protocol The ROM code supports only the Macronix SPI mode. In SPI mode, Macronix memories reply to the regular Read JEDEC ID opcode using the protocol SPI 1-1-1: The 9Fh opcode is sent on MOSI using 8 clock cycles then the JEDEC ID is read from MISO only. Hence the ROM code uses the following sequence to read the JEDEC ID: Step SPI Protocol Opcode Support by Manufacturer Modes 1. 1-1-1 9Fh Cypress, Micron Extended SPI, Macronix SPI 2. 1-4-4 AFh (1) 3. 4-4-4 AFh Micron Quad I/O SPI Note 1: Step 2 is a wrong combination but should not change the internal state of any QSPI memory. Indeed, assuming pull-up resistors are used on the four I/O lines, sending the AFh op code with SPI 1-x-y protocols (the opcode is sent only to MOSI during eight clock cycles) to a memory in Quad I/O SPI or QPI mode should be harmless (FEh opcode decoded by the memory when in Quad I/O SPI or QPI mode: unknown opcode). See Figure 16-12. Figure 16-12: QSPI Transfer Format (CPHA = 0, 8 bits per opcode) QSCK cycle (for reference) 1 2 3 4 5 6 7 8 QSCK (CPOL = 0) NSS (to slave) MOSI (from master) AFh MISO (from slave) IO2 IO3 AFh send to MOSI in SPI 1-4-4 Decoded as FE in SPI 4-4-4 • Allowing Quad I/O Commands (MRL A, MRL B) On most QSPI memories, some pins are shared between legacy functions such as Write Protect (#WP), Hold (#HOLD) or Reset (#RST) and I/O data lines 2 and 3. Hence before sending any Quad I/O commands, the ROM code updates the relevant register to reassign those pins to function IO2 and IO3:  2017 Microchip Technology Inc. DS60001476B-page 143 SAMA5D2 SERIES • Cypress The ROM code sets the Quad Enable bit (bit1) in the Configuration Register (CR) / Status Register 2 (SR2). The bit is volatile or non-volatile depending on memory versions. This operation is performed using the Write Status command (01h), setting SR1 to 00h and SR2 to 02h. • Micron The ROM code updates the Enhanced Volatile Configuration Register (EVCR) to clear the Quad I/O protocol bit (bit7) hence enabling the Quad I/O protocol. From this point, all command must use the SPI 4-4-4 protocol. • Macronix The ROM code updates the Status Register (SR1) to set its Quad Enable non-volatile bit (bit6) using the Write Status command (01h). • Configuration of Fast Read Quad I/O (EBh) Operations (MRL A, MRL B) The ROM code performs all read operations using the Fast Read Quad I/O (EBh) opcode followed by a 3-byte address. Since we cannot afford to add an exhaustive table of Read JEDEC IDs and to provide support of future products of memory manufacturers, the ROM code only relies on the very first byte of the JEDEC ID, i.e., the Manufacturer ID, to configure read operations. The ROM code matches the Manufacturer ID as shown in the following table. Table 16-3: Fast Read Quad I/O (EBh) configuration by Manufacturer ID Manufacturer ID Mode Cycle Value Manufacturer 01h Cypress SPI Protocol SPI 1-4-4 # of Mode Cycles 2 (1) (2) 20h Micron SPI 4-4-4 1 C2h Macronix SPI 1-4-4 2 (3) # of Dummy Cycles (no XIP) (XIP) 4 (1) 00h A0h 9 (2) 1h 0h 00h F0h 4 (3) Note 1: The ROM code expects the Latency Control non-volatile bits of the Cypress Status Register 3 (SR3) / Control Register 1 (CR1) to be zero (LC = 0). The ROM code does not update this value. 2: The ROM code sets the number of mode/dummy cycles for Micron memories updating bits [7:4] of their Volatile Configuration Register (VCR) with the 81h opcode. During this update of the VCR: – ROM code v1.1 always clears bit3 to enable XIP. – ROM code v1.2 clears bit3 to enable XIP if and only if XIP bit is set in the Boot Config word, otherwise it sets bit3 to disable XIP. 3: The ROM code configures the number of mode/dummy cycles for Macronix memories by clearing the volatile DC0 and DC1 bits (bits [7:6]) in the Configuration Register (CR) / Status Register 2 (SR2). It also clears the 4-byte volatile bit (bit5), resulting in the memory going back to its 3-byte address mode. This register updated (read, modify, write) using a Write Status command (01h). • Miscellaneous Information (MRL A, MRL B) Pull-up Resistors The ROM code removes the internal pull-up resistors when it configures PIO controller to mux the QSPI controller I/O lines. Therefore the probing step may fail if the Quad I/O mode of the memory has not been enabled yet and if this memory does not embed an internal pull-up resistor on #HOLD or #RESET pin. This is why we recommend to add external pull-up resistors if needed on the four I/O data lines MOSI/IO0, MISO/IO1, #WP/IO2 and #HOLD/IO3. Another solution is to update the Quad Enable non-volatile bit in the relevant register to reassign #WP and #HOLD/#RESET pins to functions IO2 and IO3. 4-byte Address Mode (> 16 MB memories) Except for Macronix, the ROM code never sends any command to the memory to leave its 4-byte address mode or to select its first memory bank. The ROM code expects to read from the very beginning of the QSPI memory using the Fast Read Quad I/O (EBh) command with a 3-byte address. DS60001476B-page 144  2017 Microchip Technology Inc. SAMA5D2 SERIES Therefore we recommend that the customer application does not change the internal state of the QSPI memory but uses 4-byte opcodes when needed instead. Hence the ROM code can still read from the QSPI memory after a reset of the SoCs. 16.4.7.6 QSPI NOR Flash Boot for MRL C Important: This section applies to the devices listed in the table below: Table 16-4: SAMA5D2 MRL C Parts Device Name ATSAMA5D21C ATSAMA5D22C ATSAMA5D23C ATSAMA5D24C ATSAMA5D26C ATSAMA5D27C ATSAMA5D28C • Hardware Considerations The ROM code configures the hardware so that: - the QSPI controller uses SPI Mode 0 (CPOL = 0 and CPHA = 0), the QSPIx_SCK clock frequency is ≤ 50 MHz, QSPIx_SCK and QSPIx_CS do not use any internal pullup/pulldown resistor, each QSPIx_IO{0,1,2,3} uses the PIO controller’s internal pullup resistor. • Software Considerations Before reading any data, the ROM code sends a software reset to the QSPI NOR memory. Then the ROM code looks for the Serial Flash Discoverable Parameters (SFDP) of the QSPI NOR memory, if available, to learn the parameters (instruction op code, timing settings) required to read the user-programmed boot file. If SFDP tables are not available, the ROM code uses hard-coded values as fallback settings to read the boot file. The ROM code supports any QSPI NOR memory which can provide its Serial Flash Discoverable Parameters (SFDP) as defined in the JEDEC JESD216B standard. The supported revisions of this JEDEC standard are: - JESD216 (version 1.0) - JESD216 rev. A (version 1.5) - JESD216 rev. B (version 1.6) Refer to the datasheet of the QSPI NOR memory to check compliance with any of the above JEDEC JESD216 standard revisions/versions. 1. QSPI NOR memories with SFDP (JEDEC JESD216x compliant) The ROM code reads the memory SFDP tables to learn the factory settings (instruction op code, number of dummy cycles, etc.). The ROM code also reads bits[22:20] in DWORD15 from the Basic Flash Parameter Table (refer to JEDEC JESD216B specification) to select and then execute the relevant procedure, if any, to set the Quad Enable (QE) bit in some internal register of the QSPI NOR memory. For most memory manufacturers, this QE bit is nonvolatile and must be set before performing any Quad SPI command. This is the only persistent setting that the ROM code may change in the internal registers of the QSPI NOR memory. All other settings are kept unchanged. Note: Values 001b and 100b for bits[22:20] in DWORD15 are not correctly supported by ROM code rev. C. Consequently, booting from memories using one the above values in their SFDP tables is likely to fail. Almost all Winbond QSPI NOR memories suffer from this issue. Refer to the datasheet of the QSPI NOR memory to find which value was chosen by the memory manufacturer and written into the SFDP tables. Finally, the ROM code reads the boot file from the data area of the QSPI NOR memory, and then continues its boot procedure.  2017 Microchip Technology Inc. DS60001476B-page 145 SAMA5D2 SERIES 2. QSPI NOR memories without SFDP This section only applies when the ROM code fails to read the SFDP tables from the QSPI NOR memory. The ROM code reads the JEDEC ID of the QSPI NOR memory, and then selects the read settings based on the manufacturer ID (first byte of the JEDEC ID) from the following hard-coded values: Cypress (01h) Micron (20h) Macronix (C2h) Winbond (EFh) Others Fast Read protocol SPI 1-4-4 SPI 1-4-4 SPI 1-4-4 SPI 1-4-4 SPI 1-1-1 Fast Read op code EBh EBh EBh EBh 0Bh Address width 24 bits 24 bits 24 bits 24 bits 24 bits Number of mode clock cycles 2 1 2 2 0 Number of wait states 4 9 4 4 8 0Fh A5h N/A 0h The ROM code first sets XIP bit[3] in the Volatile Configuration Register (VCR) Value of mode cycles to enter the 0-4-4 mode (XIP) A0h Value of mode cycles to exit the 0-4-4 mode (normal read) 00h 1h 00h FFh N/A XIP supported yes yes yes yes no Those hard-coded parameters give a last chance to the ROM code to boot from a QSPI NOR memory in either normal mode or XIP (continuous read) mode. DS60001476B-page 146  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 16-5: QSPI NOR Memories Tested with and Supported by MRL C ROM Code (non exhaustive) Manufacturer Memories SST26VF016B Microchip (SST) SST26VF032B SST26VF032BA SST26VF064B N25Q128A N25Q128A13ESF Micron N25Q256A13ESF N25Q512A13 MT25QL01G MX25V4035FM2I MX25V8035FM2I MX25V1635FM2I MX25L3233FM2I-08G MX25L3273FM2I-08G MX25L6433FM2I-08G Macronix MX25L6473FM2I-08G MX25L12835FM2I-10G MX25L12845GMI-08G MX25L12873GM2I-08G MX25L25645G MX25L25673G MX25L51245GMI-10G MX66L1G45GMI-08G S25FL127 (normal boot only; XIP fails) Spansion S25FL164 S25FL512 Winbond  2017 Microchip Technology Inc. Limited support. Refer to Note. DS60001476B-page 147 SAMA5D2 SERIES 16.4.8 Hardware and Software Constraints The table below provides clock frequencies configured by the ROM code during boot. Table 16-6: Clock Frequencies during External Memory Boot Sequence Clock MRL A MRL B MRL C PLLA 792 MHz 792 MHz 756 MHz PCK 396 MHz 396 MHz 378 MHz MCK 132 MHz 132 MHz 126 MHz SDMMC (init/operational) 400 kHz / 25 MHz 400 kHz / 25 MHz 400 kHz / 25 MHz SPI 6 MHz 12 MHz 12 MHz QSPI 25 MHz 50 MHz 50 MHz The NVM drivers use several PIOs in Peripheral mode to communicate with external memory devices. Care must be taken when these PIOs are used by the application. The connected devices could be unintentionally driven at boot time, and thus electrical conflicts between the output pins used by the NVM drivers and the connected devices could occur. To ensure the correct functionality, it is recommended to plug in critical devices to other pins not used by the NVM. Table 16-7 contains a list of pins that are driven during the boot program execution. These pins are driven during the boot sequence for a period of less than 1 second if no correct boot program is found. For MRL C parts only, the drive strength of some I/O pins is set to 'medium' while the pins are used in peripheral mode by the ROM code. For MRL A and B, drive strength is always low. Before performing the jump to the application in the internal SRAM, all the PIOs and peripherals used in the boot program are set to their reset state. DS60001476B-page 148  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 16-7: PIO Driven during Boot Program Execution NVM Bootloader Peripheral SDMMC_0 IO Set PIO Line Drive Strength (MRL C only) SDMMC0_CK PIOA0 low SDMMC0_CMD PIOA1 medium SDMMC0_DAT0 PIOA2 medium SDMMC0_DAT1 PIOA3 medium SDMMC0_DAT2 PIOA4 medium SDMMC0_DAT3 PIOA5 medium SDMMC0_DAT4 PIOA6 low SDMMC0_DAT5 PIOA7 low SDMMC0_DAT6 PIOA8 low SDMMC0_DAT7 PIOA9 low SDMMC0_RSTN PIOA10 medium SDMMC0_1V8SEL PIOA11 low SDMMC0_WP PIOA12 medium SDMMC0_CD PIOA13 medium SDMMC1_DAT0 PIOA18 medium SDMMC1_DAT1 PIOA19 medium SDMMC1_DAT2 PIOA20 medium SDMMC1_DAT3 PIOA21 medium SDMMC1_CK PIOA22 low SDMMC1_RSTN PIOA27 medium SDMMC1_CMD PIOA28 medium SDMMC1_WP PIOA29 medium SDMMC1_CD PIOA30 medium D0–D7 PIOA22-PIOA29 low NANDWE PIOA30 low NANDCS3 PIOA31 low NAND ALE PIOB0 low NAND CLE PIOB1 low NANDOE PIOB2 low D0–D7 PIOA0–PIOA7 low NANDWE PIOA8 low NANDCS3 PIOA9 low NAND ALE PIOA10 low NAND CLE PIOA11 low NANDOE PIOA12 low 1 SD Card / e.MMC SDMMC_1 Pin 1 1 NAND Flash HSMC 2  2017 Microchip Technology Inc. DS60001476B-page 149 SAMA5D2 SERIES Table 16-7: PIO Driven during Boot Program Execution (Continued) NVM Bootloader Peripheral IO Set Pin PIO Line Drive Strength (MRL C only) SPCK PIOA14 low MOSI PIOA15 low MISO PIOA16 medium NPCS0 PIOA17 low NPCS0 PIOA30 low MISO PIOA31 medium MOSI PIOB0 low SPCK PIOB1 low SPCK PIOC1 low MOSI PIOC2 low MISO PIOC3 medium NPCS0 PIOC4 low SPCK PIOA22 low MOSI PIOA23 low MISO PIOA24 medium NPCS0 PIOA25 low SPCK PIOD25 low MOSI PIOD26 low MISO PIOD27 medium NPCS0 PIOD28 low 1 SPI_0 2 SPI Flash 1 SPI_1 2 3 DS60001476B-page 150  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 16-7: PIO Driven during Boot Program Execution (Continued) NVM Bootloader Peripheral QSPI_0 QSPI_0 QSPI_0 IO Set Pin PIO Line Drive Strength (MRL C only) SCK PIOA0 low CS PIOA1 low IO0 PIOA2 low IO1 PIOA3 low IO2 PIOA4 low IO3 PIOA5 low SCK PIOA14 low CS PIOA15 low IO0 PIOA16 medium IO1 PIOA17 medium IO2 PIOA18 medium IO3 PIOA19 medium SCK PIOA22 low CS PIOA23 low IO0 PIOA24 medium IO1 PIOA25 medium IO2 PIOA26 medium IO3 PIOA27 medium SCK PIOA6 low CS PIOA7 medium IO0 PIOA8 medium IO1 PIOA9 medium IO2 PIOA10 medium IO3 PIOA11 low SCK PIOB5 low CS PIOB6 low IO0 PIOB7 medium IO1 PIOB8 medium IO2 PIOB9 medium IO3 PIOB10 medium SCK PIOB14 low CS PIOB15 low IO0 PIOB16 medium IO1 PIOB17 medium IO2 PIOB18 medium IO3 PIOB19 medium 1 2 3 QSPI Flash QSPI_1 QSPI_1 QSPI_1  2017 Microchip Technology Inc. 1 2 3 DS60001476B-page 151 SAMA5D2 SERIES Table 16-7: PIO Driven during Boot Program Execution (Continued) NVM Bootloader Peripheral IO Set UART_0 1 Pin PIO Line Drive Strength (MRL C only) DRXD PIOB26 low DTXD PIOB27 low DRXD PIOD2 low DTXD PIOD3 low DRXD PIOC7 low DTXD PIOC8 low DRXD PIOD4 low DTXD PIOD5 low DRXD PIOD23 low DTXD PIOD24 low DRXD PIOD19 low DTXD PIOD20 low DRXD PIOC12 low DTXD PIOC13 low DRXD PIOC31 low DTXD PIOD0 low DRXD PIOB11 low DTXD PIOB12 low DRXD PIOB3 low DTXD PIOB4 low 1 UART_1 2 1 UART_2 2 Console Terminal and SAM-BA Monitor 3 1 UART_3 2 3 UART_4 DS60001476B-page 152 1  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 16-7: PIO Driven during Boot Program Execution (Continued) NVM Bootloader Peripheral IO Set 1 2 Debug Port PIO Line Drive Strength (MRL C only) TCK PIOD14 low TDI PIOD15 low TDO PIOD16 low TMS PIOD17 low NTRST PIOD18 low TCK PIOD6 low TDI PIOD7 low TDO PIOD8 low TMS PIOD9 low NTRST PIOD10 low TCK PIOD27 low TDI PIOD28 low TDO PIOD29 low TMS PIOD30 low NTRST PIOD31 low TCK PIOA22 low TDI PIOA23 low TDO PIOA24 low TMS PIOA25 low NTRST PIOA26 low JTAG 3 4  2017 Microchip Technology Inc. Pin DS60001476B-page 153 SAMA5D2 SERIES 16.5 SAM-BA Monitor This part of the ROM code is executed when no valid code is found in any NVM during the NVM boot sequence, and if the DISABLE_MONITOR Fuse bit is not set. The Main Oscillator is enabled and set in the bypass mode. If the MOSCSELS bit rises, an external clock is connected. If not, the Bypass mode is cleared to attempt external quartz detection. This detection is successful when the MOSCXTS and MOSCSELS bits rise, else the internal 12 MHz fast RC oscillator is used as the Main Clock. If an external clock or crystal frequency is found, then the PLLA is configured to allow communication on the USB link for the SAM-BA Monitor, else the Main Clock is switched back to the internal 12 MHz fast RC oscillator and USB is not activated. The SAM-BA Monitor steps are: • Initialize UART and USB. • Check if USB Device enumeration occurred. • Check if characters are received on the UART. Once the communication interface is identified, the application runs in an infinite loop waiting for different commands as listed in Table 16-8. Figure 16-13: SAM-BA Monitor Diagram No valid code in NVM External clock detection Init UART and USB No USB enumeration successful? Yes Run monitor Wait for command on the USB link DS60001476B-page 154 No Character(s) received on UART? Yes Run monitor Wait for command on the UART link  2017 Microchip Technology Inc. SAMA5D2 SERIES 16.5.1 Command List Table 16-8: Commands Available through the SAM-BA Monitor Command Action Argument(s) Example N Set Normal Mode No argument N# T Set Terminal Mode No argument T# O Write a byte Address, Value# O200001,CA# o Read a byte Address,# o200001,# H Write a half word Address, Value# H200002,CAFE# h Read a half word Address,# h200002,# W Write a word Address, Value# W200000,CAFEDECA# w Read a word Address,# w200000,# S Send a file Address,# S200000,# R Receive a file Address, NbOfBytes# R200000,1234# G Go Address# G200200# V Display version No argument V# • Mode commands: - Normal mode configures SAM-BA Monitor to send / receive data in binary format, - Terminal mode configures SAM-BA Monitor to send / receive data in ASCII format. • Write commands: Writes a byte (O), a halfword (H) or a word (W) to the target - Address: Address in hexadecimal - Value: Byte, halfword or word to write in hexadecimal - Output: ‘>’ • Read commands: Reads a byte (o), a halfword (h) or a word (w) from the target - Address: Address in hexadecimal - Output: The byte, halfword or word read in hexadecimal followed by ‘>’ • Send a file (S): Sends a file to a specified address - Address: Address in hexadecimal - Output: ‘>’ Note: There is a timeout on this command which is reached when the prompt ‘>’ appears before the end of the command execution. • Receive a file (R): Receives data into a file from a specified address - Address: Address in hexadecimal - NbOfBytes: Number of bytes in hexadecimal to receive - Output: ‘>’ • Go (G): Jumps to a specified address and executes the code - Address: Address to jump to in hexadecimal - Output: ‘>’ once returned from the program execution. If the executed program does not handle the link register at its entry and does not return, the prompt is not displayed. • Get Version (V): Returns the Boot Program version - Output: version, date and time of ROM code followed by ‘>’ 16.5.2 UART Port Communication is performed through the UART port initialized to 115,200 bauds, 8 bits of data, no parity, 1 stop bit. 16.5.2.1 Xmodem Protocol The Send and Receive File commands use the Xmodem protocol to communicate. Any terminal using this protocol can be used to send the application file to the target. The size of the binary file to send depends on the SRAM size embedded in the product. In all cases, the size of the binary file must be lower than the SRAM size because the Xmodem protocol requires some SRAM memory in order to work.  2017 Microchip Technology Inc. DS60001476B-page 155 SAMA5D2 SERIES The Xmodem protocol supported is the 128-byte length block. This protocol uses a two-character CRC16 to guarantee detection of maximum bit errors. Xmodem protocol with CRC is supported by successful transmission reports provided both by a sender and by a receiver. Each transfer block is as follows: in which: - = 01 hex = binary number, starts at 01, increments by 1, and wraps 0FFH to 00H (not to 01) = 1’s complement of the blk#. = 2 bytes CRC16 Figure 16-14 shows a transmission using this protocol. Figure 16-14: Xmodem Transfer Example Host Device C SOH 01 FE Data[128] CRC CRC ACK SOH 02 FD Data[128] CRC CRC ACK SOH 03 FC Data[100] CRC CRC ACK EOT ACK 16.5.3 16.5.3.1 USB Device Port Supported External Crystal / External Clocks The SAM-BA Monitor only supports an external crystal or external clock frequency at 12 MHz to allow USB communication. 16.5.3.2 USB Class The device uses the USB Communication Device Class (CDC) drivers to take advantage of the installed PC Serial Communication software to talk over the USB. The CDC is implemented in all releases of Windows®, starting from Windows 98SE®. The CDC document, available at www.usb.org, describes how to implement devices such as ISDN modems and virtual COM ports. Vendor ID is 0x03EB. The product ID is 0x6124. These references are used by the host operating system to mount the correct driver. On Windows systems, INF files contain the correspondence between vendor ID and product ID. 16.5.3.3 Enumeration Process The USB protocol is a master/slave protocol. The host starts the enumeration, sending requests to the device through the control endpoint. The device handles standard requests as defined in the USB Specification. DS60001476B-page 156  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 16-9: Handled Standard Requests Request Definition GET_DESCRIPTOR Returns the current device configuration value SET_ADDRESS Sets the device address for all future device access SET_CONFIGURATION Sets the device configuration GET_CONFIGURATION Returns the current device configuration value GET_STATUS Returns status for the specified recipient SET_FEATURE Used to set or enable a specific feature CLEAR_FEATURE Used to clear or disable a specific feature The device also handles some class requests defined in the CDC class. Table 16-10: Handled Class Requests Request Definition SET_LINE_CODING Configures DTE rate, stop bits, parity and number of character bits GET_LINE_CODING Requests current DTE rate, stop bits, parity and number of character bits SET_CONTROL_LINE_STATE RS-232 signal used to indicate to the DCE device that the DTE device is now present Unhandled requests are stalled. 16.5.3.4 Communication Endpoints Endpoint 0 is used for the enumeration process. Endpoint 1 (64-byte Bulk OUT) and endpoint 2 (64-byte Bulk IN) are used as communication endpoints. SAM-BA Boot commands are sent by the host through Endpoint 1. If required, the message is split into several data payloads by the host driver. If the command requires a response, the host sends IN transactions to pick up the response. 16.6 Fuse Box Controller Read/write access to the fuse bits requires that the internal 12 MHz RC oscillator is enabled. 16.6.1 Fuse Bit Mapping One 32-bit word is reserved for boot configuration. 512 fuse bits are available for customer needs. Writing a ‘1’ to SFR_SECURE.FUSE disables access to the Secure Fuse Controller (SFC). To avoid any malfunctioning, the user must not write the “DO NOT USE (DNU)” fuse bits in the Boot Configuration area.  2017 Microchip Technology Inc. DS60001476B-page 157 SAMA5D2 SERIES Table 16-11: SFC_DR Customer Fuse Matrix Bits Use 16 [543:512] JTAG_DIS[543] 15 [511:480] 14 [479:448] 13 [447:416] 12 [415:384] 11 [383:352] 10 [351:320] 9 [319:288] 8 [287:256] 7 [255:224] 6 [223:192] 5 [191:160] 4 [159:128] 3 [127:96] 2 [95:64] 1 [63:32] 0 [31:0] SEC_DEBUG_ DIS[542] Boot Configuration bits[541:512](1) USER_DATA[511:0] Note 1: See Section 16.4.4 “Boot Configuration Word” for details on the contents of these bits. Table 16-12: Special Function Bits JTAG Disable (Fuse bit 543) Secure Debug Disable (Fuse bit 542) 0 0 Full JTAG debug allowed in Secure and Normal modes 0 1 JTAG debug allowed in Normal mode only (not in Secure mode) 1 X JTAG debug disabled DS60001476B-page 158 Description  2017 Microchip Technology Inc. SAMA5D2 SERIES 17. AXI Matrix (AXIMX) 17.1 Description The AXI Matrix comprises the embedded Advanced Extensible Interface (AXI) bus protocol which supports separate address/control and data phases, unaligned data transfers using byte strobes, burst-based transactions with only start address issued, separate read and write data channels to enable low-cost DMA, ability to issue multiple outstanding addresses, out-of-order transaction completion, and easy addition of register stages to provide timing closure. 17.2 Embedded Characteristics • High performance AXI network interconnect • 1 Master: - Cortex-A5 Core • 2 Slaves: - ROM - AXI/AHB bridge to AHB Matrix • Single-cycle arbitration • Full pipelining to prevent master stalls • 1 remap state 17.3 17.3.1 Operation Remap Remap states are managed in the AXI Matrix Remap Register (AXIMX_REMAP): AXIMX_REMAP.REMAP0 (register bit 0) is used to remap RAM @ addr 0x00000000. See Section 17.4 “AXI Matrix (AXIMX) User Interface”. The number of remap states can be defined using eight bits of the AXIMX_REMAP register, and a bit in AXIMX_REMAP controls each remap state. Each remap state can be used to control the address decoding for one or more slave interfaces. If a slave interface is affected by two remap states that are both asserted, the remap state with the lowest remap bit number takes precedence. Each slave interface can be configured independently so that a remap state can perform different functions for different masters. A remap state can: • Alias a memory region into two different address ranges • Move an address region • Remove an address region Because of the nature of the distributed register subsystem, the masters receive the updated remap bit states in sequence, and not simultaneously. A slave interface does not update to the latest remap bit setting until: • The address completion handshake accepts any transaction that is pending • Any current lock sequence completes At powerup, ROM is seen at address 0. After powerup, the internal SRAM can be moved down to address 0 by means of the remap bits. 17.4 AXI Matrix (AXIMX) User Interface Table 17-1: Register Mapping Offset Register Name 0x00 AXI Matrix Remap Register AXIMX_REMAP 0x04–0x43108 Reserved –  2017 Microchip Technology Inc. Access Reset Write-only – – – DS60001476B-page 159 SAMA5D2 SERIES 17.4.1 AXI Matrix Remap Register Name: AXIMX_REMAP Address: 0x00600000 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 – – 1 – 0 REMAP0 – 23 22 21 20 – 15 14 13 12 – 7 – 6 – 5 – 4 – REMAP0: Remap State 0 SRAM is seen at address 0x00000000 (through AHB slave interface) instead of ROM. DS60001476B-page 160  2017 Microchip Technology Inc. SAMA5D2 SERIES 18. Matrix (H64MX/H32MX) 18.1 Description In order to reduce power consumption without loss in performance, the system embeds three matrixes: one based on the AXI protocol (AXIMX) and two based on the AHB protocol (H64MX and H32MX). This section describes the implementation of the 64-bit AHB Matrix (H64MX) and the 32-bit AHB Matrix (H32MX). For details on the matrix based on the AXI protocol, refer to Section 17. “AXI Matrix (AXIMX)”. Each AHB Matrix implements a multilayer AHB, based on the AHB-Lite protocol, which enables parallel access paths between multiple AHB masters and slaves in a system, thus increasing the overall bandwidth. The normal latency to connect a master to a slave is one cycle, except for the default master of the accessed slave which is connected directly (zero cycle latency). Note: 18.2 • • • • • • • • • • • • • When a master and a slave are on different bus matrixes (AXIMX, H64MX, or H32MX), both matrixes (H64MX and H32MX) and the bridge between the bus matrixes must be configured accordingly. Embedded Characteristics 32-bit or 64-bit Data Bus 64-bit AHB Matrix (H64MX) Providing 12 Masters and 15 Slaves 32-bit AHB Matrix (H32MX) Providing 8 Masters and 6 Slaves One Address Decoder for Each Master Support for Long Bursts of Length 32, 64, 128 and Up to the Limit of 256-bit Burst Beats of Words Enhanced Programmable Mixed Arbitration for Each Slave: - Round-robin - Fixed priority - Latency quality of service Programmable Default Master for Each Slave: - No default master - Last accessed default master - Fixed default master Deterministic Maximum Access Latency for Masters Zero or One Cycle Arbitration Latency for the First Access of a Burst Bus Lock Forwarding to Slaves One Special Function Register for Each Slave (not dedicated) Register Write Protection ARM TrustZone Technology Extension to AHB and APB  2017 Microchip Technology Inc. DS60001476B-page 161 SAMA5D2 SERIES 18.3 64-bit Matrix (H64MX) 18.3.1 Matrix Masters The H64MX manages 12 masters, which means that each master can perform an access, concurrently with others, to an available slave. This matrix operates at MCK. Each master has its own decoder, which is defined specifically for each master. In order to simplify the addressing, all the masters have the same decodings. Table 18-1: Master No. List of H64MX Masters Name Security Type Bridge from AXI Matrix (Core) Not applicable 1, 2 DMA Controller 0 Peripheral Securable 3, 4 DMA Controller 1 Peripheral Securable 5, 6 LCDC DMA Peripheral Securable 7 SDMMC0 Peripheral Securable 8 SDMMC1 Peripheral Securable 9 ISC DMA Peripheral Securable 10 AESB Not applicable(1) 11 Bridge from H32MX to H64MX Not applicable 0 Note 1: Master signals secure/not secure are propagated through the AES bridge. 18.3.2 Matrix Slaves The H64MX manages 15 slaves. Each slave has its own arbiter providing a dedicated arbitration per slave. Table 18-2: Slave No. List of H64MX Slaves Description TZ Access Management Bridge from H64MX to H32MX Not applicable H64MX Peripheral Bridge HSEL0: not applicable SDMMC0 HSEL1: Internal Securable to Peripheral: 1 region(1) SDMMC1 HSEL2: Internal Securable to Peripheral: 1 region(1) 2 DDR2 Port 0 - AESB Scalable Securable: 4 regions(2) 3 DDR2 Port 1 Scalable Securable: 4 regions(2) 4 DDR2 Port 2 Scalable Securable: 4 regions(2) 5 DDR2 Port 3 Scalable Securable: 4 regions(2) 6 DDR2 Port 4 Scalable Securable: 4 regions(2) 7 DDR2 Port 5 Scalable Securable: 4 regions(2) 8 DDR2 Port 6 Scalable Securable: 4 regions(2) 9 DDR2 Port 7 Scalable Securable: 4 regions(2) 10 Internal SRAM 128K Internal Securable: 1 region 11 Internal SRAM 128K (Cache L2) Internal Securable: 1 region 0 1 DS60001476B-page 162  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 18-2: Slave No. List of H64MX Slaves (Continued) Description TZ Access Management 12 QSPI0 Internal Securable: 1 region 13 QSPI1 Internal Securable: 1 region 14 AESB Not applicable Note 1: Particular case: see Section 18.12.4 “Security Types of AHB Slave Peripherals” for Internal Securable to Peripheral type configuration. For each SDMMCx, a coherent configuration must be done on - the AHB Slave, - MATRIX_SPSELSR for general interrupt and AHB Master, - MATRIX_SPSELSR for TIMER interrupt 2: For coherency, each DDR2 port shall have the same TZ access management configuration. 18.3.3 Master to Slave Access Table 18-3 shows how masters and slaves interconnect. Writing in a register or field not dedicated to a master or a slave has no effect. Table 18-3: Master to Slave Access on H64MX MASTER 0 SLAVE Bridge from AXIMX (Core) 1 2 XDMAC0 3 4 XDMAC1 5 6 LCDC DMA 7 8 SDMMC0 SDMMC1 DMA DMA 9 10 11 ISC DMA AESB Bridge from H32MX Bridge from H64MX to H32MX X X X X X — — — — — — — H64MX Peripheral Bridge X X X X X — — — — — — X SDMMC0–SDMMC1 X X X X X — — — — — — X 2 DDR2 Port 0 — — — — — — — — — — X — 3 DDR2 Port 1 X — — — — — — — — — — — 4 DDR2 Port 2 — — — — — X — — — — — — 5 DDR2 Port 3 — — — — — — X — — — — — 6 DDR2 Port 4 — — — — — — — X X X — — 7 DDR2 Port 5 — X — X — — — — — — — — 8 DDR2 Port 6 — — X — X — — — — — — — 9 DDR2 Port 7 — — — — — — — — — — — X 10 Internal SRAM X X X X X X X X X X — X 11 L2C SRAM X X X X X X X X X X — X 12 QSPI0 X X X X X — — — — — X X 13 QSPI1 X X X X X — — — — — X X 14 AESB X X X X X — — — — — — X 0 1  2017 Microchip Technology Inc. DS60001476B-page 163 SAMA5D2 SERIES 18.4 32-bit Matrix (H32MX) 18.4.1 Matrix Masters The H32MX manages eight masters, which means that each master can perform an access, concurrently with others, to an available slave. This matrix can operate at MCK if MCK is lower than 83 MHz, or at MCK/2 if MCK is higher than 83 MHz. Refer to Section 33. “Power Management Controller (PMC)” for more details. Each master has its own decoder, which is defined specifically for each master. In order to simplify the addressing, all the masters have the same decodings. Table 18-4: Master No. List of H32MX Masters Name Security Type 0 Bridge from H64MX to H32MX Not applicable 1 Integrity Check Monitor (ICM) Peripheral Securable 2 UHPHS EHCI DMA Peripheral Securable 3 UHPHS OHCI DMA Peripheral Securable 4 UDPHS DMA Peripheral Securable 5 GMAC DMA Peripheral Securable 6 CAN0 DMA Peripheral Securable 7 CAN1 DMA Peripheral Securable 18.4.2 Matrix Slaves The H32MX manages six slaves. Each slave has its own arbiter providing a dedicated arbitration per slave. Table 18-5: List of H32MX Slaves Slave No. Description TZ Access Management 0 Bridge from H32MX to H64MX Not applicable 1 H32MX Peripheral Bridge 0 Not applicable 2 H32MX Peripheral Bridge 1 Not applicable External Securable: 7 regions: HSEL0: 0x10000000 128 MB CS0 HSEL1: 0x18000000 128 MB CS0 External Bus Interface 3 HSEL2: 0x60000000 128 MB CS1 HSEL3: 0x68000000 128 MB CS1 HSEL4: 0x70000000 128 MB CS2 HSEL5: 0x78000000 128 MB CS2 HSEL6: 0x80000000 128 MB CS3 NFC Command Register 4 DS60001476B-page 164 NFC SRAM Internal Securable to Peripheral: 1 region HSEL7: 0xC0000000 256 MB NFCCMD Internal Securable: 1 region  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 18-5: List of H32MX Slaves (Continued) Slave No. 5 6 Description TZ Access Management USB Device High Speed (UDPHS) Dual Port RAM (DPR) HSEL0: Internal Securable: 1 region USB Host (UHPHS) OHCI registers HSEL1: Internal Securable to Peripheral: 1 region(1) USB Host (UHPHS) EHCI registers HSEL2: Internal Securable to Peripheral: 1 region(1) Peripheral Touch Controller (PTC) Internal Securable: 1 region Note 1: UHPHS: Coherent configuration must be done on: - AHB Slave UHPHS OHCI Internal Securable Peripheral - AHB Slave UHPHS EHCI Internal Securable Peripheral - MATRIX_SPSELSR for Interrupt and AHB Master 18.4.3 Master to Slave Access Table 18-6 shows how masters and slaves interconnect. Writing in a register or field not dedicated to a master or a slave has no effect. Table 18-6: Master to Slave Access on H32MX MASTER 0 (Through Bridge from H64MX) XDMAC0 1 2 3 4 5 6 UHPHS OHCI DMA UDPHS DMA GMAC DMA CAN0 DMA XDMAC1 SLAVE Core IF0 IF1 IF0 IF1 ICM UHPHS EHCI DMA 0 Bridge from H32MX to H64MX — — — — — X X X X X X 1 H32MX Peripheral Bridge 0 X — X — X X — — — — — 2 H32MX Peripheral Bridge 1 X — X — X X — — — — — EBI CS0..CS3 X X — X — X — — — — — NFC Command Register X X — X — — — — — — — NFC SRAM X X — X — — — — — — — UDPHS RAM X — — — X — — — — — — UHP OHCI Reg X — — — X — — — — — — UHP EHCI Reg X — — — X — — — — — — Peripheral Touch Controller (PTC) X — — — — — — — — — — 3 4 5 6 18.5 Memory Mapping The Bus Matrix provides one decoder for every AHB master interface. The decoder offers each AHB master several memory mappings. Each memory area may be assigned to several slaves. Booting at the same address while using different AHB slaves (i.e., external RAM, internal ROM or internal Flash, etc.) becomes possible. 18.6 Special Bus Granting Mechanism The Bus Matrix provides some speculative bus granting techniques in order to anticipate access requests from masters. This mechanism reduces latency at first access of a burst, or for a single transfer, as long as the slave is free from any other master access. It does not provide any benefit if the slave is continuously accessed by more than one master, since arbitration is pipelined and has no negative effect on the slave bandwidth or access latency. This bus granting mechanism sets a different default master for every slave. At the end of the current access, if no other request is pending, the slave remains connected to its associated default master. A slave can be associated with three kinds of default masters:  2017 Microchip Technology Inc. DS60001476B-page 165 SAMA5D2 SERIES • No default master • Last access master • Fixed default master To change from one type of default master to another, the Bus Matrix user interface provides Slave Configuration Registers, one for every slave, which set a default master for each slave. The Slave Configuration Register contains two fields to manage master selection: DEFMSTR_TYPE and FIXED_DEFMSTR. The 2-bit DEFMSTR_TYPE field selects the default master type (no default, last access master, fixed default master), whereas the 4-bit FIXED_DEFMSTR field selects a fixed default master provided that DEFMSTR_TYPE is set to fixed default master. See Section 18.13.2 “Bus Matrix Slave Configuration Registers”. 18.7 No Default Master After the end of the current access, if no other request is pending, the slave is disconnected from all masters. This configuration incurs one latency clock cycle for the first access of a burst after bus Idle. Arbitration without default master may be used for masters that perform significant bursts or several transfers with no Idle in between, or if the slave bus bandwidth is widely used by one or more masters. This configuration provides no benefit on access latency or bandwidth when reaching maximum slave bus throughput regardless of the number of requesting masters. 18.8 Last Access Master After the end of the current access, if no other request is pending, the slave remains connected to the last master that performed an access request. This allows the Bus Matrix to remove the one latency cycle for the last master that accessed the slave. Other nonprivileged masters still get one latency clock cycle if they need to access the same slave. This technique is used for masters that mainly perform single accesses or short bursts with some Idle cycles in between. This configuration provides no benefit on access latency or bandwidth when reaching maximum slave bus throughput whatever is the number of requesting masters. 18.9 Fixed Default Master After the end of the current access, if no other request is pending, the slave connects to its fixed default master. Unlike the last access master, the fixed default master does not change unless the user modifies it by software (FIXED_DEFMSTR field of the related MATRIX_SCFG). This allows the Bus Matrix arbiters to remove the one latency clock cycle for the fixed default master of the slave. All requests attempted by the fixed default master do not cause any arbitration latency, whereas other nonprivileged masters will get one latency cycle. This technique is used for a master that mainly performs single accesses or short bursts with Idle cycles in between. This configuration provides no benefit on access latency or bandwidth when reaching maximum slave bus throughput, regardless of the number of requesting masters. 18.10 Arbitration The Bus Matrix provides an arbitration mechanism that reduces latency when conflicts occur, i.e., when two or more masters try to access the same slave at the same time. One arbiter per AHB slave is provided, thus arbitrating each slave specifically. The Bus Matrix provides the user with the possibility of choosing between two arbitration types or mixing them for each slave: • Round-robin Arbitration (default) • Fixed Priority Arbitration The resulting algorithm may be complemented by selecting a default master configuration for each slave. When rearbitration must be done, specific conditions apply. See Section 18.10.1 “Arbitration Scheduling”. 18.10.1 Arbitration Scheduling Each arbiter has the ability to arbitrate between two or more master requests. In order to avoid burst breaking and also to provide the maximum throughput for slave interfaces, arbitration may only take place during the following cycles: • Idle Cycles: when a slave is not connected to any master or is connected to a master which is not currently accessing it. • Single Cycles: when a slave is currently performing a single access. • End of Burst Cycles: when the current cycle is the last cycle of a burst transfer. For defined burst length, predicted end of burst DS60001476B-page 166  2017 Microchip Technology Inc. SAMA5D2 SERIES matches the size of the transfer but is managed differently for undefined burst length. See Section 18.10.1.1 “Undefined Length Burst Arbitration”. • Slot Cycle Limit: when the slot cycle counter has reached the limit value indicating that the current master access is too long and must be broken. See Section 18.10.1.2 “Slot Cycle Limit Arbitration”. 18.10.1.1 Undefined Length Burst Arbitration In order to prevent long AHB burst lengths that can lock the access to the slave for an excessive period of time, the user can trigger the rearbitration before the end of the incremental bursts. The rearbitration period can be selected from the following Undefined Length Burst Type (ULBT) possibilities: • • • • • • • • Unlimited: no predetermined end of burst is generated. This value enables 1 Kbyte burst lengths. 1-beat bursts: predetermined end of burst is generated at each single transfer during the INCR transfer. 4-beat bursts: predetermined end of burst is generated at the end of each 4-beat boundary during INCR transfer. 8-beat bursts: predetermined end of burst is generated at the end of each 8-beat boundary during INCR transfer. 16-beat bursts: predetermined end of burst is generated at the end of each 16-beat boundary during INCR transfer. 32-beat bursts: predetermined end of burst is generated at the end of each 32-beat boundary during INCR transfer. 64-beat bursts: predetermined end of burst is generated at the end of each 64-beat boundary during INCR transfer. 128-beat bursts: predetermined end of burst is generated at the end of each 128-beat boundary during INCR transfer. The use of undefined length 8-beat bursts, or less, is discouraged since this may decrease the overall bus bandwidth due to arbitration and slave latencies at each first access of a burst. However, if the usual length of undefined length bursts is known for a master it is recommended to configure the ULBT accordingly. This selection can be done through the ULBT field of the Master Configuration Registers (MATRIX_MCFG). 18.10.1.2 Slot Cycle Limit Arbitration The Bus Matrix contains specific logic to break long accesses, such as very long bursts on a very slow slave (e.g., an external low speed memory). At each arbitration time, a counter is loaded with the value previously written in the SLOT_CYCLE field of the related Slave Configuration Register (MATRIX_SCFG) and decreased at each clock cycle. When the counter elapses, the arbiter has the ability to rearbitrate at the end of the current AHB access cycle. Unless a master has a very tight access latency constraint, which could lead to data overflow or underflow due to a badly undersized internal FIFO with respect to its throughput, the Slot Cycle Limit should be disabled (SLOT_CYCLE = 0) or set to its default maximum value in order not to inefficiently break long bursts performed by some masters. In most cases, this feature is not needed and should be disabled for power saving. Warning: This feature cannot prevent any slave from locking its access indefinitely. 18.10.2 Arbitration Priority Scheme The bus Matrix arbitration scheme is organized in priority pools, each corresponding to an access criticality class as shown in the “Latency Quality of Service” column in Table 18-7. Table 18-7: Arbitration Priority Pools Priority Pool Latency Quality of Service 3 Latency Critical 2 Latency Sensitive 1 Bandwidth Sensitive 0 Background Transfers Round-robin priority is used in the highest and lowest priority pools 3 and 0, whereas fixed level priority is used between priority pools and in the intermediate priority pools 2 and 1. See Section 18.10.2.2 “Round-robin Arbitration”. For each slave, each master is assigned to one of the slave priority pools through the priority registers for slaves (MxPR fields of MATRIX_PRAS and MATRIX_PRBS). When evaluating master requests, this priority pool level always takes precedence. After reset, most of the masters belong to the lowest priority pool (MxPR = 0, Background Transfer) and are therefore granted bus access in a true round-robin order.  2017 Microchip Technology Inc. DS60001476B-page 167 SAMA5D2 SERIES The highest priority pool must be specifically reserved for masters requiring very low access latency. If more than one master belongs to this pool, they will be granted bus access in a biased round-robin manner which allows tight and deterministic maximum access latency from AHB requests. In the worst case, any currently occurring high-priority master request will be granted after the current bus master access has ended and other high priority pool master requests, if any, have been granted once each. The lowest priority pool shares the remaining bus bandwidth between AHB masters. Intermediate priority pools allow fine priority tuning. Typically, a latency-sensitive master or a bandwidth-sensitive master will use such a priority level. The higher the priority level (MxPR value), the higher the master priority. For good CPU performance, it is recommended configure CPU priority with the default reset value 2 (Latency Sensitive). All combinations of MxPR values are allowed for all masters and slaves. For example, some masters might be assigned the highest priority pool (round-robin), and remaining masters the lowest priority pool (round-robin), with no master for intermediate fixed priority levels. 18.10.2.1 Fixed Priority Arbitration Fixed priority arbitration algorithm is the first and only arbitration algorithm applied between masters from distinct priority pools. It is also used in priority pools other than the highest and lowest priority pools (intermediate priority pools). Fixed priority arbitration allows the Bus Matrix arbiters to dispatch the requests from different masters to the same slave by using the fixed priority defined by the user in the MxPR field for each master in the Priority Registers, MATRIX_PRAS and MATRIX_PRBS. If two or more master requests are active at the same time, the master with the highest priority MxPR number is serviced first. In intermediate priority pools, if two or more master requests with the same priority are active at the same time, the master with the highest number is serviced first. 18.10.2.2 Round-robin Arbitration This algorithm is only used in the highest and lowest priority pools. It allows the Bus Matrix arbiters to properly dispatch requests from different masters to the same slave. If two or more master requests are active at the same time in the priority pool, they are serviced in a round-robin increasing master number order. 18.11 Register Write Protection To prevent any single software error from corrupting Bus Matrix behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the Write Protection Mode Register (MATRIX_WPMR). If a write access to a write-protected register is detected, the WPVS bit in the Write Protection Status Register (MATRIX_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS flag is reset by writing the Bus Matrix Write Protect Mode Register (MATRIX_WPMR) with the appropriate access key WPKEY. The following registers can be write-protected: • • • • • • • • • • Bus Matrix Master Configuration Registers Bus Matrix Slave Configuration Registers Bus Matrix Priority Registers A For Slaves Bus Matrix Priority Registers B For Slaves Master Error Interrupt Enable Register Master Error Interrupt Disable Register Security Slave Registers Security Areas Split Slave Registers Security Region Top Slave Registers Security Peripheral Select x Registers 18.12 TrustZone Extension to AHB and APB TrustZone secure software is supported through the filtering of each slave access with master security bit AMBA hprot[6] extension signals. The TrustZone extension adds the ability to manage the access rights for Secure and Non-secure accesses. The access rights are defined through the hardware and software configuration of the device. The operating mode is as follows: • With the TrustZone extension, the Bus Masters transmit requests with the Secure or Non-secure Security option. • The AHB Matrix, according to its configuration and the request, grants or denies the access. DS60001476B-page 168  2017 Microchip Technology Inc. SAMA5D2 SERIES The slave address space is divided into one or more slave regions. The slave regions are generally contiguous parts of the slave address space. The slave region is potentially split into an access denied area (upper part) and a security region which can be split (lower part), unless the slave security region occupies the whole slave region. The security region itself may or may not be split into one Secured area and one Non-secured area. The Secured area may be independently secured for read access and for write access. For one slave region, the following characteristics are configured by hardware or software: • • • • Base Address of the slave region Max Size of the slave region: the maximum size for the region’s physical content Top Size of the slave security region: the actually programmed or fixed size for the region’s physical content Split Size of the slave security region: the size of the lower security area of the region. Figure 18-1 shows how the terms defined here are implemented in an AHB slave address space. Figure 18-1: Generic Partitioning of the AHB Slave Address Space Securable Slave Address Space Generic Partitioning Slave Region n+1 Region n Max (Hardwired) Access Denied Area Region n Top Slave Region n Max Size Upper Security Area Configured as the Non-secured or the Securable Area Region n Top Size (Fixed or Programmable) Region n Split Lower Security Area Configured as the Non-secured or the Securable Area Region n Split Size (Fixed or Programmable) Region n Base Address (Fixed or Region n-1 Top) Slave Region n-1  2017 Microchip Technology Inc. DS60001476B-page 169 SAMA5D2 SERIES A set of Bus Matrix security registers allows to specify, for each AHB slave, slave security region or slave security area, the security mode required to access this slave, slave security region or slave security area. Additional Bus Matrix security registers allow to specify, for each APB slave, the security mode required to access this slave (see Section 18.13.15 “Security Peripheral Select x Registers”). See Section 18.13.12 “Security Slave Registers”. The Bus Matrix registers can only be accessed in Secure mode. The Bus Matrix propagates the AHB security bit down to the AHB slaves to let them perform additional security checks, and the Bus Matrix itself allows, or not, the access to the slaves by means of its TrustZone embedded controller. Access violations may be reported either by an AHB slave through the bus error response (example from the AHB/APB Bridge), or by the Bus Matrix embedded TrustZone controller. In both cases, a bus error response is sent to the offending master and the error is flagged in the Master Error Status Register. An interrupt can be sent to the Secure world, if it has been enabled for that master by writing into the Master Error Interrupt Enable Register. Thus, the offending master is identified. The offending address is registered in the Master Error Address Registers, so that the slave and the targeted security region are also known. Depending on the hardware parameters and software configuration, the address space of each AHB slave security region may or may not be split into two parts, one belonging to the Secure world and the other one to the Normal world. Five different security types of AHB slaves are supported. The number of security regions is set by design for each slave, independently, from 1 to 8, totalling from 1 up to 16 security areas for security configurable slaves. 18.12.1 18.12.1.1 Security Types of AHB Slaves Principles The Bus Matrix supports five different security types of AHB slaves: two fixed types and three configurable types. The security type of an AHB slave is set at hardware design among the following: • • • • • Always Non-secured Always Secured Internal Securable External Securable Scalable Securable The security type is set at hardware design on a per-master and a per-slave basis. Always Non-secured and Always Secured security types are not software configurable. The different security types have the following characteristics: • Always Non-secured slaves have no security mode access restriction. Their address space is precisely set by design. Any out-ofaddress range access is denied and reported. • Always Secured slaves can only be accessed by a secure master request. Their address space is precisely set by design. Any nonsecure or out-of-address range access is denied and reported. • Internal Securable is intended for internal memories such as RAM, ROM or embedded Flash. The Internal Securable slave has one slave region which has a hardware fixed base address and Security Region Top. This slave region may be split through software configuration into one Non-secured area plus one Secured area. Inside the slave security region, the split boundary is programmable in powers of 2 from 4 Kbytes up to the full slave security region address space. The security area located below the split boundary may be configured as the Non-secured or the Secured one. The Securable area may be independently configured as Read Secured and/or Write Secured. Any access with security or address range violation is denied and reported. • External Securable is intended for external memories on the EBI, such as DDR, SDRAM, external ROM or NAND Flash. The External Securable slave has identical features as the Internal Securable slave, plus the ability to configure each of its slave security region address space sizes according to the external memory parts used. This avoids mirroring Secured areas into Non-secured areas, and further restricts the overall accessible address range. Any access with security or configured address range violation is denied and reported. • Scalable Securable is intended for external memories with a dedicated slave, such as DDR. The Scalable Securable slave is divided into a fixed number of scalable, equally sized, and contiguous security regions. Each of them can be split in the same way as for Internal or External Securable slaves. The security region size must be configured by software, so that the equally-sized regions fill the actual available memory. This avoids mirroring Secured areas into Non-secured areas, and further restricts the overall accessible address range. Any access with security or configured address range violation is denied and reported. As the security type is set at hardware design on a per-master and per-slave basis, it is possible to set some slave access security as configurable from one or some particular masters, and to set the access as Always Secured from all the other masters. As the security type is set by design at the slave region level, different security region types can be mixed inside a single slave. DS60001476B-page 170  2017 Microchip Technology Inc. SAMA5D2 SERIES Likewise, the mapping base address and the accessible address range of each AHB slave or slave region may have been hardwarerestricted on a per-master basis from no access to full slave address space. 18.12.1.2 Examples Table 18-8 shows an example of Security Type settings. Table 18-8: Slave Slave0 Internal Memory Security Type Setting Example Master0 Always Non-secured Slave1 External Securable EBI 2 regions Master1 Master2 Internal Securable Internal Securable 1 region 1 region Always Secured External Securable 2 regions This example is constructed with the following characteristics: • Slave0 is an Internal Memory containing one region: - The Access from Master0 to Slave0 is Always Non-secured - The Access from Master1 and Master2 to Slave0 is Internal Securable with one region and with the same Software Configuration (Choice of SPLIT0 and the Security Configuration bits LANSECH, RDNSECH, WRNSECH). • Slave1 is an EBI containing two regions: - The Access from Master1 to Slave1 is Always Secured - The Access from Master0 and Master2 to Slave1 is External Securable with two regions and with the same Software Configuration (Choice of TOP0, TOP1, SPLIT0, SPLIT1 and the Security Configuration bits LANSECH, RDNSECH, WRNSECH). Figure 18-2 shows an Internal Securable slave example. This example is constructed with the following hypothesis: • The slave is an Internal Memory containing one region. The Slave region Max Size is 4 Mbytes. • The slave region 0 base address equals 0x10000000. Its Top Size is 512 Kbytes (hardware configuration). • The slave software configuration is: - SPLIT0 is set to 256 Kbytes - LANSECH0 is set to 0, the low area of region 0 is the securable one - RDNSECH0 is set to 0, region 0 Securable area is secured for reads - WRNSECH0 is set to 0, region 0 Securable area is secured for writes  2017 Microchip Technology Inc. DS60001476B-page 171 SAMA5D2 SERIES Figure 18-2: Partitioning Example of an Internal Securable Slave Featuring 1 Security Region of 512 Kbytes Split into 1 or 2 Security Areas of 4 Kbytes to 512 Kbytes 512 Kbyte space Internal Securable Slave 0x10400000 Access Denied Area Slave Region 0 0x10080000 Region 0 Top 256 Kbyte Non-secured Area Region 0 Split 256 Kbyte Read/Write Secured Area 0x10000000 Note: The slave security areas split inside the security region are configured by writing into the Security Areas Split Slave Registers. DS60001476B-page 172  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 18-3 shows an External Securable slave example. This example is constructed with the following hypothesis: • The slave is an interface with the external bus (EBI) containing two regions. The slave size is 2 × 256 Mbytes. Each slave region Max Size is 256 Mbytes. • The slave region 0 base address equals 0x10000000. It is connected to a 32 Mbyte memory, for example an external DDR. The slave region 0 Top Size must be set to 32 Mbytes. • The slave region 1 base address equals 0x20000000. It is connected to a 2 Mbyte memory, for example an external NAND Flash. The slave region 1 Top Size must be set to 2 Mbytes. • The slave software configuration is: - TOP0 is set to 32 Mbytes - TOP1 is set to 2 Mbytes - SPLIT0 is set to 4 Mbytes - SPLIT1 is set to 1 Mbyte - LANSECH0 is set to 1, the low area of region 0 is the non-securable one - RDNSECH0 is set to 0, region 0 Securable area is secured for reads - WRNSECH0 is set to 0, region 0 Securable area is secured for writes - LANSECH1 is set to 0, the low area of region 1 is the Securable one - RDNSECH1 is set to 1, region 1 Securable area is non-secured for reads - WRNSECH1 is set to 0, region 1 Securable area is secured for writes  2017 Microchip Technology Inc. DS60001476B-page 173 SAMA5D2 SERIES Figure 18-3: Partitioning Example of an External Securable Slave Featuring 2 Security Regions of 4 Kbytes to 128 Mbytes each and up to 4 Security Areas of 4 Kbytes to 128 Mbytes 2*256 Mbyte space External Securable Slave partitioning with a 32 Mbyte memory part and a 2 Mbyte memory part 0x30000000 254 Mbyte Access Denied Area Slave Region 1 Region 1 Top 1 Mbyte Non-secured Area 0x20100000 Region 1 Split 1 Mbyte Write Secured Area 0x20000000 224 Mbyte Access Denied Area Slave Region 0 0x12000000 Region 0 Top 28 Mbyte Read/Write Secured Area 0x10000000 Region 0 Split Read/Write Secured Area 0x10400000 4 Mbyte Non-secured Area Note: 0x10000000 The slave region sizes are configured by writing into the Security Region Top Slave Registers. The slave security area split inside each region is configured by writing into the Security Areas Split Slave Registers. DS60001476B-page 174  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 18-4 shows a Scalable Securable slave example. This example is constructed with the following hypothesis: • • • • The slave is an external memory with dedicated slave containing four regions, for example an external DDR. The slave size is 512 Mbytes. The slave base address equals 0x40000000. It is connected to a 256-Mbyte external memory. As the connected memory size is 256 Mbytes and there are four regions, the size of each region is 64 Mbytes. This gives the value of the slave region Max Size and Top Size. The slave region 0 Top Size must be configured to 64 Mbytes. • The slave software configuration is: - TOP0 is set to 64 Mbytes - SPLIT0 is set to 4 Kbytes - SPLIT1 is set to 64 Mbytes, so its low area occupies the whole region 1 - SPLIT2 is set to 4 Kbytes - SPLIT3 is set to 32 Mbytes - LANSECH0 is set to 0, the low area of region 0 is the Securable one - RDNSECH0 is set to 1, region 0 Securable area is non-secured for reads - WRNSECH0 is set to 0, region 0 Securable area is secured for writes - LANSECH1 is set to 1, the low area of region 1 is the non-securable one - RDNSECH1 is ‘don’t care’ since the low area occupies the whole region 1 - WRNSECH1 is ‘don’t care’ since the low area occupies the whole region 1 - LANSECH2 is set to 1, the low area of region 2 is the non-securable one - RDNSECH2 is set to 0, region 2 Securable area is secured for reads - WRNSECH2 is set to 0, region 2 Securable area is secured for writes - LANSECH3 is set to 0, the low area of region 3 is the Securable one - RDNSECH3 is set to 0, region 3 Securable area is secured for reads - WRNSECH3 is set to 0, region 3 Securable area is secured for writes  2017 Microchip Technology Inc. DS60001476B-page 175 SAMA5D2 SERIES Figure 18-4: Partitioning Example of a Scalable Securable Slave Featuring 4 Equally-sized Security Regions of 1 Mbytes to 128 Mbytes each and up to 8 Security Areas of 4 Kbytes to 128 Mbytes 512 Mbyte space Scalable Securable Slave partitioning with 256 Mbyte memory 0x60000000 256 Mbyte Access Denied Area 0x50000000 32 Mbyte Non-secured Area Security Region 3 0x4C000000 Read/Write Secured Area 95.996 Mbyte Region 3 Split Read/Write Secured Area Security Region 2 Read/Write Secured Area Region 2 Split Region 1 Split 0x48000000 0x48001000 Security Region 1 4 Kbyte Non-secured Area Non-secured Area 0x44000000 128 Mbyte 0x48000000 Generic Region Size => Region 0 Top = Region1 Base Non-secured Area Security Region 0 Region 0 Split Non-secured Area 0x40000000 0x40001000 4 Kbyte Write Secured Area Note: 0x40000000 The slaves’ generic security regions sizes are configured by writing into field SRTOP0 of the Security Region Top Slave Registers and the custom slave security areas splits inside each region is configured by writing into the Security Areas Split Slave Registers. DS60001476B-page 176  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.12.2 Security of APB Slaves The security type of an APB slave is set at hardware design among the following: • Peripheral Always Secured (PAS) • Peripheral Always Non-secured (PNS) • Peripheral Securable (PS) To configure the security mode required for accessing a particular APB slave connected to the AHB/APB Bridge, the Bus Matrix features three 32-bit Security Peripheral Select x Registers. Some of these bits may have been set to a Secured or a Non-secured value by design, whereas others are programmed by software (see Section 18.13.15 “Security Peripheral Select x Registers”). Peripheral security state, “Secure” or “Non-secure” is an AND operation between H32MX MATRIX_SPSELRx and H64MX MATRIX_SPSELRx for the bit corresponding to the peripheral. As a general rule: • The peripheral security state is applied to the corresponding peripheral interrupt line. Exceptions may occur on some peripherals (PIO Controller, etc.). In such case, refer to the peripheral description. • The peripheral security state is applied to the peripheral master part, if any. Exceptions may occur on some peripherals. In such case, refer to the peripheral description. See Section 18.12.3 “Security Types of AHB Master Peripherals”. MATRIX_SPSELRx bits in the H32MX or H64MX user interface are respectively read/write or read-only to ‘1’ depending on whether the peripheral is connected or not, on the Matrix. All bit values in Table 18-9 except those marked ‘UD’ (User Defined) are read-only and cannot be changed. Values marked ‘UD’ can be changed. Refer to the following examples. • Example for GMAC, Peripheral ID 5, which is connected to the H32MX Matrix - H64MX MATRIX_SPSELR1[5] = 1 (read-only); no influence on the security configuration - H32MX MATRIX_SPSELR1[5] can be written by user to program the security. • Example for LCDC, Peripheral ID 45, which is connected to the H64MX Matrix - H64MX MATRIX_SPSELR2[13] can be written by user to program the security. - H32MX MATRIX_SPSELR2[13] = 1 (read-only); no influence on the security configuration • Example for AIC, Peripheral ID 49, which is connected to the H32MX Matrix - H64MX MATRIX_SPSELR2[17] = 1 (read-only); sets the peripheral as Non-secure by hardware, also called “Peripheral Always Non-secured” - H32MX MATRIX_SPSELR2[17] = 1 (read-only); no influence on the security configuration • Example for SAIC, Peripheral ID 0, which is connected to the H32MX Matrix - H64MX MATRIX_SPSELR1[0] = 1 (read-only); no influence on the security configuration - H32MX MATRIX_SPSELR1[0] = 0 (read-only); sets the peripheral as Secure by hardware, also called “Peripheral Always Secured” Table 18-9: Peripheral Identifiers Bit Value in H32MX Bit Value in H64MX MATRIX_SPSELR1[0] 0 1 – – – H64MX MATRIX_SPSELR1[2] 1 UD PS H32MX MATRIX_SPSELR1[3] UD 1 WDT PS H32MX MATRIX_SPSELR1[4] UD 1 5 GMAC PS H32MX MATRIX_SPSELR1[5] UD 1 6 XDMAC0 PS H64MX MATRIX_SPSELR1[6] 1 UD 7 XDMAC1 PS H64MX MATRIX_SPSELR1[7] 1 UD 8 ICM PS H32MX MATRIX_SPSELR1[8] UD 1 9 AES PS H64MX MATRIX_SPSELR1[9] 1 UD 10 AESB PS H64MX MATRIX_SPSELR1[10] 1 UD ID Peripheral Security Type 0 SAIC Peripheral Always Secured (PAS) – 1 – – – 2 ARM Peripheral Securable (PS) 3 PIT 4  2017 Microchip Technology Inc. Matrix MATRIX_SPSELRx Bit DS60001476B-page 177 SAMA5D2 SERIES Table 18-9: Peripheral Identifiers (Continued) ID Peripheral Security Type Matrix MATRIX_SPSELRx Bit Bit Value in H32MX Bit Value in H64MX 11 TDES PS H32MX MATRIX_SPSELR1[11] UD 1 12 SHA PS H64MX MATRIX_SPSELR1[12] 1 UD 13 MPDDRC PS H64MX MATRIX_SPSELR1[13] 1 UD 14 H32MX config. PAS H32MX MATRIX_SPSELR1[14] 0 1 15 H64MX config. PAS H64MX MATRIX_SPSELR1[15] 1 0 16 SECUMOD PAS H32MX MATRIX_SPSELR1[16] 0 1 17 HSMC PS H32MX MATRIX_SPSELR1[17] UD 1 18 PIOA PAS H32MX MATRIX_SPSELR1[18] 0 1 19 FLEXCOM0 PS H32MX MATRIX_SPSELR1[19] UD 1 20 FLEXCOM1 PS H32MX MATRIX_SPSELR1[20] UD 1 21 FLEXCOM2 PS H32MX MATRIX_SPSELR1[21] UD 1 22 FLEXCOM3 PS H32MX MATRIX_SPSELR1[22] UD 1 23 FLEXCOM4 PS H32MX MATRIX_SPSELR1[23] UD 1 24 UART0 PS H32MX MATRIX_SPSELR1[24] UD 1 25 UART1 PS H32MX MATRIX_SPSELR1[25] UD 1 26 UART2 PS H32MX MATRIX_SPSELR1[26] UD 1 27 UART3 PS H32MX MATRIX_SPSELR1[27] UD 1 28 UART4 PS H32MX MATRIX_SPSELR1[28] UD 1 29 TWIHS0 PS H32MX MATRIX_SPSELR1[29] UD 1 30 TWIHS1 PS H32MX MATRIX_SPSELR1[30] UD 1 31 SDMMC0 PS H64MX MATRIX_SPSELR1[31] 1 UD 32 SDMMC1 PS H64MX MATRIX_SPSELR2[0] 1 UD 33 SPI0 PS H32MX MATRIX_SPSELR2[1] UD 1 34 SPI1 PS H32MX MATRIX_SPSELR2[2] UD 1 35 TC0 PS H32MX MATRIX_SPSELR2[3] UD 1 36 TC1 PS H32MX MATRIX_SPSELR2[4] UD 1 37 – – – – 38 PWM PS UD 1 39 – – – – 40 ADC PS H32MX MATRIX_SPSELR2[8] UD 1 41 UHPHS PS H32MX MATRIX_SPSELR2[9] UD 1 42 UDPHS PS H32MX MATRIX_SPSELR2[10] UD 1 43 SSC0 PS H32MX MATRIX_SPSELR2[11] UD 1 44 SSC1 PS H32MX MATRIX_SPSELR2[12] UD 1 45 LCDC PS H64MX MATRIX_SPSELR2[13] 1 UD 46 ISC PS H64MX MATRIX_SPSELR2[14] 1 UD DS60001476B-page 178 – H32MX – – MATRIX_SPSELR2[6] –  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 18-9: Peripheral Identifiers (Continued) ID Peripheral Security Type Matrix MATRIX_SPSELRx Bit Bit Value in H32MX Bit Value in H64MX 47 TRNG PS H32MX MATRIX_SPSELR2[15] UD 1 48 PDMIC PS H32MX MATRIX_SPSELR2[16] UD 1 49 AIC Peripheral Always Non-secured (PNS) H32MX MATRIX_SPSELR2[17] 1 1 50 SFC PS H32MX MATRIX_SPSELR2[18] UD 1 51 SECURAM PAS H32MX MATRIX_SPSELR2[19] 0 1 52 QSPI0 PS H64MX MATRIX_SPSELR2[20] 1 UD 53 QSPI1 PS H64MX MATRIX_SPSELR2[21] 1 UD 54 I2SC0 PS H32MX MATRIX_SPSELR2[22] UD 1 55 I2SC1 PS H32MX MATRIX_SPSELR2[23] UD 1 56 CAN0 PS H32MX MATRIX_SPSELR2[24] UD 1 57 CAN1 PS H32MX MATRIX_SPSELR2[25] UD 1 58 PTC PS H32MX MATRIX_SPSELR2[26] UD 1 59 CLASSD PS H32MX MATRIX_SPSELR2[27] UD 1 60 SFR PS H32MX MATRIX_SPSELR2[28] UD 1 61 SAIC PAS H32MX MATRIX_SPSELR2[29] 0 1 62 AIC PNS H32MX MATRIX_SPSELR2[30] 1 1 63 L2CC PS H64MX MATRIX_SPSELR2[31] 1 UD 64 CAN0 PS H32MX MATRIX_SPSELR3[0] UD 1 65 CAN1 PS H32MX MATRIX_SPSELR3[1] UD 1 66 GMAC PS H32MX MATRIX_SPSELR3[2] UD 1 67 GMAC PS H32MX MATRIX_SPSELR3[3] UD 1 68 PIOB PAS H32MX MATRIX_SPSELR3[4] 0 1 69 PIOC PAS H32MX MATRIX_SPSELR3[5] 0 1 70 PIOD PAS H32MX MATRIX_SPSELR3[6] 0 1 71 SDMMC0 PS H32MX MATRIX_SPSELR3[7] UD 1 72 SDMMC1 PS H32MX MATRIX_SPSELR3[8] UD 1 73 – – – – 74 RTC, RSTC, PMC PS H32MX MATRIX_SPSELR3[9] UD 1 75 ACC PS H32MX MATRIX_SPSELR3[10] UD 1 76 RXLP PS H32MX MATRIX_SPSELR3[11] UD 1 77 SFRBU PS H32MX MATRIX_SPSELR3[12] UD 1 78 CHIPID PS H32MX MATRIX_SPSELR3[13] UD 1 – – The AHB/APB Bridge compares the incoming master request security bit with the required security mode for the selected peripheral, and accepts or denies access. In the last case, its bus error response is internally flagged in the Bus Matrix Master Error Status Register; the offending address is registered in the Master Error Address Registers so that the slave and the targeted protected region are also known.  2017 Microchip Technology Inc. DS60001476B-page 179 SAMA5D2 SERIES 18.12.3 Security Types of AHB Master Peripherals Master AHB peripherals send requests on the AHB matrix with a security attribute that depends on: • The master security type: the master security type is identical to the security type of the IP peripheral slave user interface. • Possibly for some masters with one or more channels: it may be possible to choose the TrustZone security attribute for each channel. If this is the case, refer to the peripheral’s user interface description. When the peripheral security type is Peripheral Securable, the slave security configuration applies to the peripheral master AHB part. 18.12.4 Security Types of AHB Slave Peripherals In this particular case, the AHB interface is connected to one or more peripheral user interfaces. The type is Internal Securable to Peripheral (ISP). Important: In this case, each region in the “Internal Securable to Peripheral” AHB slave type must be programmed with the following characteristics: • The region must be programmed to be entirely secure or entirely non-secure. This is done with: - The split offset must be equal to the maximum size of 128 Mbytes so that the whole peripheral user interface is in the low area below the split. Code sample: MATRIX_SASSRx.SASPLITy = 0xF - The bits WRNSECH and RDNSECH must be set respectively to 0=”write secure” and 0=”read secure”. Code sample: MATRIX_SSRx.WRNSECHy = 0; MATRIX_SSRx.RDNSECHy = 0; - To set the peripheral to “secure”: the bit LANSECHy must be set to 0 (low area according to RDNSECH0 and WRNSECH0, hence secure). - To set the peripheral to “non-secure”: the bit LANSECHy must be set to 1 (low area is non-secure). Note: The MATRIX_SRTSRx register is not applicable for the “Internal Securable to Peripheral” type. • The Security Peripheral Select Registers must be set to the same security attributes for the corresponding Peripheral identifiers: MATRIX_SPSELRx.NSECPy. DS60001476B-page 180  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13 Matrix (H64MX/H32MX) User Interface The user interface below is constructed with the maximum numbers of masters, slaves and regions by slave that are possible on the two product matrixes. The exact number of these elements must be used to deduce the exact register description of the Matrix user interface. The exact numbers of these elements can be found in: • Section 18.3 “64-bit Matrix (H64MX)” • Section 18.4 “32-bit Matrix (H32MX)” Table 18-10: Register Mapping Offset Register Name Access Reset 0x0000 Master Configuration Register 0 MATRIX_MCFG0 Read/Write 0x00000004 0x0004 Master Configuration Register 1 MATRIX_MCFG1 Read/Write 0x00000004 0x0008 Master Configuration Register 2 MATRIX_MCFG2 Read/Write 0x00000004 0x000C Master Configuration Register 3 MATRIX_MCFG3 Read/Write 0x00000004 0x0010 Master Configuration Register 4 MATRIX_MCFG4 Read/Write 0x00000004 0x0014 Master Configuration Register 5 MATRIX_MCFG5 Read/Write 0x00000004 0x0018 Master Configuration Register 6 MATRIX_MCFG6 Read/Write 0x00000004 0x001C Master Configuration Register 7 MATRIX_MCFG7 Read/Write 0x00000004 0x0020 Master Configuration Register 8 MATRIX_MCFG8 Read/Write 0x00000004 0x0024 Master Configuration Register 9 MATRIX_MCFG9 Read/Write 0x00000004 0x0028 Master Configuration Register 10 MATRIX_MCFG10 Read/Write 0x00000004 0x002C Master Configuration Register 11 MATRIX_MCFG11 Read/Write 0x00000004 Reserved – – – 0x0040 Slave Configuration Register 0 MATRIX_SCFG0 Read/Write 0x000001FF 0x0044 Slave Configuration Register 1 MATRIX_SCFG1 Read/Write 0x000001FF 0x0048 Slave Configuration Register 2 MATRIX_SCFG2 Read/Write 0x000001FF 0x004C Slave Configuration Register 3 MATRIX_SCFG3 Read/Write 0x000001FF 0x0050 Slave Configuration Register 4 MATRIX_SCFG4 Read/Write 0x000001FF 0x0054 Slave Configuration Register 5 MATRIX_SCFG5 Read/Write 0x000001FF 0x0058 Slave Configuration Register 6 MATRIX_SCFG6 Read/Write 0x000001FF 0x005C Slave Configuration Register 7 MATRIX_SCFG7 Read/Write 0x000001FF 0x0060 Slave Configuration Register 8 MATRIX_SCFG8 Read/Write 0x000001FF 0x0064 Slave Configuration Register 9 MATRIX_SCFG9 Read/Write 0x000001FF 0x0068 Slave Configuration Register 10 MATRIX_SCFG10 Read/Write 0x000001FF 0x006C Slave Configuration Register 11 MATRIX_SCFG11 Read/Write 0x000001FF 0x0070 Slave Configuration Register 12 MATRIX_SCFG12 Read/Write 0x000001FF 0x0074 Slave Configuration Register 13 MATRIX_SCFG13 Read/Write 0x000001FF 0x0078 Slave Configuration Register 14 MATRIX_SCFG14 Read/Write 0x000001FF 0x007C Reserved – – – 0x0080 Priority Register A for Slave 0 MATRIX_PRAS0 Read/Write 0x00000000 0x0084 Priority Register B for Slave 0 MATRIX_PRBS0 Read/Write 0x00000000 0x0030–0x003C  2017 Microchip Technology Inc. DS60001476B-page 181 SAMA5D2 SERIES Table 18-10: Register Mapping (Continued) Offset Register Name Access Reset 0x0088 Priority Register A for Slave 1 MATRIX_PRAS1 Read/Write 0x00000000 0x008C Priority Register B for Slave 1 MATRIX_PRBS1 Read/Write 0x00000000 0x0090 Priority Register A for Slave 2 MATRIX_PRAS2 Read/Write 0x00000000 0x0094 Priority Register B for Slave 2 MATRIX_PRBS2 Read/Write 0x00000000 0x0098 Priority Register A for Slave 3 MATRIX_PRAS3 Read/Write 0x00000000 0x009C Priority Register B for Slave 3 MATRIX_PRBS3 Read/Write 0x00000000 0x00A0 Priority Register A for Slave 4 MATRIX_PRAS4 Read/Write 0x00000000 0x00A4 Priority Register B for Slave 4 MATRIX_PRBS4 Read/Write 0x00000000 0x00A8 Priority Register A for Slave 5 MATRIX_PRAS5 Read/Write 0x00000000 0x00AC Priority Register B for Slave 5 MATRIX_PRBS5 Read/Write 0x00000000 0x00B0 Priority Register A for Slave 6 MATRIX_PRAS6 Read/Write 0x00000000 0x00B4 Priority Register B for Slave 6 MATRIX_PRBS6 Read/Write 0x00000000 0x00B8 Priority Register A for Slave 7 MATRIX_PRAS7 Read/Write 0x00000000 0x00BC Priority Register B for Slave 7 MATRIX_PRBS7 Read/Write 0x00000000 0x00C0 Priority Register A for Slave 8 MATRIX_PRAS8 Read/Write 0x00000000 0x00C4 Priority Register B for Slave 8 MATRIX_PRBS8 Read/Write 0x00000000 0x00C8 Priority Register A for Slave 9 MATRIX_PRAS9 Read/Write 0x00000000 0x00CC Priority Register B for Slave 9 MATRIX_PRBS9 Read/Write 0x00000000 0x00D0 Priority Register A for Slave 10 MATRIX_PRAS10 Read/Write 0x00000000 0x00D4 Priority Register B for Slave 10 MATRIX_PRBS10 Read/Write 0x00000000 0x00D8 Priority Register A for Slave 11 MATRIX_PRAS11 Read/Write 0x00000000 0x00DC Priority Register B for Slave 11 MATRIX_PRBS11 Read/Write 0x00000000 0x00E0 Priority Register A for Slave 12 MATRIX_PRAS12 Read/Write 0x00000000 0x00E4 Priority Register B for Slave 12 MATRIX_PRBS12 Read/Write 0x00000000 0x00E8 Priority Register A for Slave 13 MATRIX_PRAS13 Read/Write 0x00000000 0x00EC Priority Register B for Slave 13 MATRIX_PRBS13 Read/Write 0x00000000 0x00F0 Priority Register A for Slave 14 MATRIX_PRAS14 Read/Write 0x00000000 0x00F4 Priority Register B for Slave 14 MATRIX_PRBS14 Read/Write 0x00000000 Reserved – – – 0x0150 Master Error Interrupt Enable Register MATRIX_MEIER Write-only – 0x0154 Master Error Interrupt Disable Register MATRIX_MEIDR Write-only – 0x0158 Master Error Interrupt Mask Register MATRIX_MEIMR Read-only 0x00000000 0x015C Master Error Status Register MATRIX_MESR Read-only 0x00000000 0x0160 Master 0 Error Address Register MATRIX_MEAR0 Read-only 0x00000000 0x0164 Master 1 Error Address Register MATRIX_MEAR1 Read-only 0x00000000 0x0168 Master 2 Error Address Register MATRIX_MEAR2 Read-only 0x00000000 0x00FC–0x014C DS60001476B-page 182  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 18-10: Register Mapping (Continued) Offset Register Name Access Reset 0x016C Master 3 Error Address Register MATRIX_MEAR3 Read-only 0x00000000 0x0170 Master 4 Error Address Register MATRIX_MEAR4 Read-only 0x00000000 0x0174 Master 5 Error Address Register MATRIX_MEAR5 Read-only 0x00000000 0x0178 Master 6 Error Address Register MATRIX_MEAR6 Read-only 0x00000000 0x017C Master 7 Error Address Register MATRIX_MEAR7 Read-only 0x00000000 0x0180 Master 8 Error Address Register MATRIX_MEAR8 Read-only 0x00000000 0x0184 Master 9 Error Address Register MATRIX_MEAR9 Read-only 0x00000000 0x0188 Master 10 Error Address Register MATRIX_MEAR10 Read-only 0x00000000 0x018C Master 11 Error Address Register MATRIX_MEAR11 Read-only 0x00000000 Reserved – – – 0x01E4 Write Protection Mode Register MATRIX_WPMR Read/Write 0x00000000 0x01E8 Write Protection Status Register MATRIX_WPSR Read-only 0x00000000 Reserved – – – 0x0200 Security Slave 0 Register MATRIX_SSR0 Read/Write 0x00000000 0x0204 Security Slave 1 Register MATRIX_SSR1 Read/Write 0x00000000 0x0208 Security Slave 2 Register MATRIX_SSR2 Read/Write 0x00000000 0x020C Security Slave 3 Register MATRIX_SSR3 Read/Write 0x00000000 0x0210 Security Slave 4 Register MATRIX_SSR4 Read/Write 0x00000000 0x0214 Security Slave 5 Register MATRIX_SSR5 Read/Write 0x00000000 0x0218 Security Slave 6 Register MATRIX_SSR6 Read/Write 0x00000000 0x021C Security Slave 7 Register MATRIX_SSR7 Read/Write 0x00000000 0x0220 Security Slave 8 Register MATRIX_SSR8 Read/Write 0x00000000 0x0224 Security Slave 9 Register MATRIX_SSR9 Read/Write 0x00000000 0x0228 Security Slave 10 Register MATRIX_SSR10 Read/Write 0x00000000 0x022C Security Slave 11 Register MATRIX_SSR11 Read/Write 0x00000000 0x0230 Security Slave 12 Register MATRIX_SSR12 Read/Write 0x00000000 0x0234 Security Slave 13 Register MATRIX_SSR13 Read/Write 0x00000000 0x0238 Security Slave 14 Register MATRIX_SSR14 Read/Write 0x00000000 0x023C Reserved – 0x0190–0x01E0 0x01EC–0x01FC – – 0x0240 Security Areas Split Slave 0 Register MATRIX_SASSR0 Read/Write (1) 0x0244 Security Areas Split Slave 1 Register MATRIX_SASSR1 Read/Write (1) 0x0248 Security Areas Split Slave 2 Register MATRIX_SASSR2 Read/Write (1) 0x024C Security Areas Split Slave 3 Register MATRIX_SASSR3 Read/Write (1) 0x0250 Security Areas Split Slave 4 Register MATRIX_SASSR4 Read/Write (1) 0x0254 Security Areas Split Slave 5 Register MATRIX_SASSR5 Read/Write (1) 0x0258 Security Areas Split Slave 6 Register MATRIX_SASSR6 Read/Write (1)  2017 Microchip Technology Inc. DS60001476B-page 183 SAMA5D2 SERIES Table 18-10: Register Mapping (Continued) Offset Register Name Access Reset 0x025C Security Areas Split Slave 7 Register MATRIX_SASSR7 Read/Write (1) 0x0260 Security Areas Split Slave 8 Register MATRIX_SASSR8 Read/Write (1) 0x0264 Security Areas Split Slave 9 Register MATRIX_SASSR9 Read/Write (1) 0x0268 Security Areas Split Slave 10 Register MATRIX_SASSR10 Read/Write (1) 0x026C Security Areas Split Slave 11 Register MATRIX_SASSR11 Read/Write (1) 0x0270 Security Areas Split Slave 12 Register MATRIX_SASSR12 Read/Write (1) 0x0274 Security Areas Split Slave 13 Register MATRIX_SASSR13 Read/Write (1) 0x0278 Security Areas Split Slave 14 Register MATRIX_SASSR14 Read/Write (1) Reserved – – – 0x0284 Security Region Top Slave 1 Register MATRIX_SRTSR1 Read/Write 0x00000000 0x0288 Security Region Top Slave 2 Register MATRIX_SRTSR2 Read/Write 0x00000000 0x028C Security Region Top Slave 3 Register MATRIX_SRTSR3 Read/Write 0x00000000 0x0290 Security Region Top Slave 4 Register MATRIX_SRTSR4 Read/Write 0x00000000 0x0294 Security Region Top Slave 5 Register MATRIX_SRTSR5 Read/Write 0x00000000 0x0298 Security Region Top Slave 6 Register MATRIX_SRTSR6 Read/Write 0x00000000 0x029C Security Region Top Slave 7 Register MATRIX_SRTSR7 Read/Write 0x00000000 0x02A0 Security Region Top Slave 8 Register MATRIX_SRTSR8 Read/Write 0x00000000 0x02A4 Security Region Top Slave 9 Register MATRIX_SRTSR9 Read/Write 0x00000000 0x02A8 Security Region Top Slave 10 Register MATRIX_SRTSR10 Read/Write 0x00000000 0x02AC Security Region Top Slave 11 Register MATRIX_SRTSR11 Read/Write 0x00000000 0x02B0 Security Region Top Slave 12 Register MATRIX_SRTSR12 Read/Write 0x00000000 0x02B4 Security Region Top Slave 13 Register MATRIX_SRTSR13 Read/Write 0x00000000 0x02B8 Security Region Top Slave 14 Register MATRIX_SRTSR14 Read/Write 0x00000000 0x02BC Reserved – – – 0x02C0 Security Peripheral Select 1 Register MATRIX_SPSELR1 Read/Write 0x00000000(2) 0x02C4 Security Peripheral Select 2 Register MATRIX_SPSELR2 Read/Write 0x00000000(3) 0x02C8 Security Peripheral Select 3 Register MATRIX_SPSELR3 Read/Write 0x00000000(4) 0x027C–0x0280 Note 1: When applicable to an AHB slave region, the initial value of MATRIX_SASSRx.SASPLITy is 0xF. When not applicable to an AHB slave region, the initial value of MATRIX_SASSRx.SASPLITy is 0x0. 2: This value is 0x000D2504 for H32MX and 0xFFF2DAFB for H64MX. 3: This value is 0x011C0000 for H32MX and 0xFFE7FFFF for H64MX. 4: This value is 0xFFFFFFFA for H32MX and 0xFFFFFFE7 for H64MX. DS60001476B-page 184  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.1 Bus Matrix Master Configuration Registers Name: MATRIX_MCFGx [x=0..11] Address: 0xF0018000 (0), 0xFC03C000 (1) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 2 1 0 7 6 5 4 3 – – – – – ULBT This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. ULBT: Undefined Length Burst Type Value 0 Name UNLIMITED Description Unlimited Length Burst—No predicted end of burst is generated, therefore INCR bursts coming from this master can only be broken if the Slave Slot Cycle Limit is reached. If the Slot Cycle Limit is not reached, the burst is normally completed by the master, at the latest, on the next AHB 1 Kbyte address boundary, allowing up to 256-beat word bursts or 128-beat double-word bursts. This value should not be used in the very particular case of a master capable of performing back-to-back undefined length bursts on a single slave, since this could indefinitely freeze the slave arbitration and thus prevent another master from accessing this slave. 1 SINGLE Single Access—The undefined length burst is treated as a succession of single accesses, allowing rearbitration at each beat of the INCR burst or bursts sequence. 2 4_BEAT 4-beat Burst—The undefined length burst or bursts sequence is split into 4-beat bursts or less, allowing rearbitration every 4 beats. 3 8_BEAT 8-beat Burst—The undefined length burst or bursts sequence is split into 8-beat bursts or less, allowing rearbitration every 8 beats. 4 16_BEAT 16-beat Burst—The undefined length burst or bursts sequence is split into 16-beat bursts or less, allowing rearbitration every 16 beats. 5 32_BEAT 32-beat Burst—The undefined length burst or bursts sequence is split into 32-beat bursts or less, allowing rearbitration every 32 beats. 6 64_BEAT 64-beat Burst—The undefined length burst or bursts sequence is split into 64-beat bursts or less, allowing rearbitration every 64 beats. 7 128_BEAT 128-beat Burst—The undefined length burst or bursts sequence is split into 128-beat bursts or less, allowing rearbitration every 128 beats. Unless duly needed, the ULBT should be left at its default 0 value for power saving.  2017 Microchip Technology Inc. DS60001476B-page 185 SAMA5D2 SERIES 18.13.2 Bus Matrix Slave Configuration Registers Name: MATRIX_SCFGx [x=0..14] Address: 0xF0018040 (0), 0xFC03C040 (1) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – 15 14 13 12 11 10 9 8 – – – – – – – SLOT_CYCLE 7 6 5 4 3 2 1 0 FIXED_DEFMSTR DEFMSTR_TYPE SLOT_CYCLE This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. SLOT_CYCLE: Maximum Bus Grant Duration for Masters When SLOT_CYCLE AHB clock cycles have elapsed since the last arbitration, a new arbitration takes place to let another master access this slave. If another master is requesting the slave bus, then the current master burst is broken. If SLOT_CYCLE = 0, the Slot Cycle Limit feature is disabled and bursts always complete unless broken according to the ULBT. This limit has been placed in order to enforce arbitration so as to meet potential latency constraints of masters waiting for slave access. This limit must not be too small. Unreasonably small values break every burst and the Bus Matrix arbitrates without performing any data transfer. The default maximum value is usually an optimal conservative choice. In most cases, this feature is not needed and should be disabled for power saving. See Section 18.10.1.2 “Slot Cycle Limit Arbitration” for details. DEFMSTR_TYPE: Default Master Type Value 0 Name Description NONE No Default Master—At the end of the current slave access, if no other master request is pending, the slave is disconnected from all masters. This results in a one clock cycle latency for the first access of a burst transfer or for a single access. 1 LAST Last Default Master—At the end of the current slave access, if no other master request is pending, the slave stays connected to the last master having accessed it. This results in not having one clock cycle latency when the last master tries to access the slave again. 2 FIXED Fixed Default Master—At the end of the current slave access, if no other master request is pending, the slave connects to the fixed master the number that has been written in the FIXED_DEFMSTR field. This results in not having one clock cycle latency when the fixed master tries to access the slave again. FIXED_DEFMSTR: Fixed Default Master This is the number of the Default Master for this slave. Only used if DEFMSTR_TYPE value = 2. Specifying the number of a master which is not connected to the selected slave is equivalent to clearing DEFMSTR_TYPE. DS60001476B-page 186  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.3 Bus Matrix Priority Registers A For Slaves Name: MATRIX_PRASx [x=0..14] Address: 0xF0018080 (0)[0], 0xF0018088 (0)[1], 0xF0018090 (0)[2], 0xF0018098 (0)[3], 0xF00180A0 (0)[4], 0xF00180A8 (0)[5], 0xF00180B0 (0)[6], 0xF00180B8 (0)[7], 0xF00180C0 (0)[8], 0xF00180C8 (0)[9], 0xF00180D0 (0)[10], 0xF00180D8 (0)[11], 0xF00180E0 (0)[12], 0xF00180E8 (0)[13], 0xF00180F0 (0)[14], 0xFC03C080 (1)[0], 0xFC03C088 (1)[1], 0xFC03C090 (1)[2], 0xFC03C098 (1)[3], 0xFC03C0A0 (1)[4], 0xFC03C0A8 (1)[5], 0xFC03C0B0 (1)[6], 0xFC03C0B8 (1)[7], 0xFC03C0C0 (1)[8], 0xFC03C0C8 (1)[9], 0xFC03C0D0 (1)[10], 0xFC03C0D8 (1)[11], 0xFC03C0E0 (1)[12], 0xFC03C0E8 (1)[13], 0xFC03C0F0 (1)[14] Access: Read/Write 31 30 – – 23 22 – – 15 14 – – 7 6 – – 29 28 M7PR 21 20 M5PR 13 12 M3PR 5 4 M1PR 27 26 – – 19 18 – – 11 10 – – 3 2 – – 25 24 M6PR 17 16 M4PR 9 8 M2PR 1 0 M0PR This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. MxPR: Master x Priority Fixed priority of Master x for accessing the selected slave. The higher the number, the higher the priority. All the masters programmed with the same MxPR value for the slave make up a priority pool. Round-robin arbitration is used in the lowest (MxPR = 0) and highest (MxPR = 3) priority pools. Fixed priority is used in intermediate priority pools (MxPR = 1) and (MxPR = 2). See Section 18.10.2 “Arbitration Priority Scheme” for details.  2017 Microchip Technology Inc. DS60001476B-page 187 SAMA5D2 SERIES 18.13.4 Bus Matrix Priority Registers B For Slaves Name: MATRIX_PRBSx [x=0..14] Address: 0xF0018084 (0)[0], 0xF001808C (0)[1], 0xF0018094 (0)[2], 0xF001809C (0)[3], 0xF00180A4 (0)[4], 0xF00180AC (0)[5], 0xF00180B4 (0)[6], 0xF00180BC (0)[7], 0xF00180C4 (0)[8], 0xF00180CC (0)[9], 0xF00180D4 (0)[10], 0xF00180DC (0)[11], 0xF00180E4 (0)[12], 0xF00180EC (0)[13], 0xF00180F4 (0)[14], 0xFC03C084 (1)[0], 0xFC03C08C (1)[1], 0xFC03C094 (1)[2], 0xFC03C09C (1)[3], 0xFC03C0A4 (1)[4], 0xFC03C0AC (1)[5], 0xFC03C0B4 (1)[6], 0xFC03C0BC (1)[7], 0xFC03C0C4 (1)[8], 0xFC03C0CC (1)[9], 0xFC03C0D4 (1)[10], 0xFC03C0DC (1)[11], 0xFC03C0E4 (1)[12], 0xFC03C0EC (1)[13], 0xFC03C0F4 (1)[14] Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 – – – – 7 6 – – M11PR 5 4 M9PR 3 2 – – 8 M10PR 1 0 M8PR This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. MxPR: Master x Priority Fixed priority of Master x for accessing the selected slave. The higher the number, the higher the priority. All the masters programmed with the same MxPR value for the slave make up a priority pool. Round-robin arbitration is used in the lowest (MxPR = 0) and highest (MxPR = 3) priority pools. Fixed priority is used in intermediate priority pools (MxPR = 1) and (MxPR = 2). See Section 18.10.2 “Arbitration Priority Scheme” for details. DS60001476B-page 188  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.5 Master Error Interrupt Enable Register Name: MATRIX_MEIER Address: 0xF0018150 (0), 0xFC03C150 (1) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – MERR11 MERR10 MERR9 MERR8 7 6 5 4 3 2 1 0 MERR7 MERR6 MERR5 MERR4 MERR3 MERR2 MERR1 MERR0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. MERRx: Master x Access Error 0: No effect. 1: Enables Master x Access Error interrupt source.  2017 Microchip Technology Inc. DS60001476B-page 189 SAMA5D2 SERIES 18.13.6 Master Error Interrupt Disable Register Name: MATRIX_MEIDR Address: 0xF0018154 (0), 0xFC03C154 (1) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – MERR11 MERR10 MERR9 MERR8 7 6 5 4 3 2 1 0 MERR7 MERR6 MERR5 MERR4 MERR3 MERR2 MERR1 MERR0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. MERRx: Master x Access Error 0: No effect. 1: Disables Master x Access Error interrupt source. DS60001476B-page 190  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.7 Master Error Interrupt Mask Register Name: MATRIX_MEIMR Address: 0xF0018158 (0), 0xFC03C158 (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – MERR11 MERR10 MERR9 MERR8 7 6 5 4 3 2 1 0 MERR7 MERR6 MERR5 MERR4 MERR3 MERR2 MERR1 MERR0 MERRx: Master x Access Error 0: Master x Access Error does not trigger any interrupt. 1: Master x Access Error triggers the Bus Matrix interrupt line.  2017 Microchip Technology Inc. DS60001476B-page 191 SAMA5D2 SERIES 18.13.8 Master Error Status Register Name: MATRIX_MESR Address: 0xF001815C (0), 0xFC03C15C (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – MERR11 MERR10 MERR9 MERR8 7 6 5 4 3 2 1 0 MERR7 MERR6 MERR5 MERR4 MERR3 MERR2 MERR1 MERR0 MERRx: Master x Access Error 0: No Master Access Error has occurred since the last read of the MATRIX_MESR. 1: At least one Master Access Error has occurred since the last read of the MATRIX_MESR. DS60001476B-page 192  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.9 Master Error Address Registers Name: MATRIX_MEARx [x=0..11] Address: 0xF0018160 (0), 0xFC03C160 (1) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ERRADD 23 22 21 20 ERRADD 15 14 13 12 ERRADD 7 6 5 4 ERRADD ERRADD: Master Error Address Master Last Access Error Address  2017 Microchip Technology Inc. DS60001476B-page 193 SAMA5D2 SERIES 18.13.10 Write Protection Mode Register Name: MATRIX_WPMR Address: 0xF00181E4 (0), 0xFC03C1E4 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the Write Protection if WPKEY corresponds to 0x4D4154 (“MAT” in ASCII). 1: Enables the Write Protection if WPKEY corresponds to 0x4D4154 (“MAT” in ASCII). See Section 18.11 “Register Write Protection” for list of registers that can be write-protected. WPKEY: Write Protection Key (Write-only) Value Name 0x4D4154 PASSWD DS60001476B-page 194 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.11 Write Protection Status Register Name: MATRIX_WPSR Address: 0xF00181E8 (0), 0xFC03C1E8 (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 11 10 9 8 WPVSRC 15 14 13 12 WPVSRC 7 6 5 4 3 2 1 0 – – – – – – – WPVS WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of MATRIX_WPSR. 1: A write protection violation has occurred since the last write of MATRIX_WPMR. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.  2017 Microchip Technology Inc. DS60001476B-page 195 SAMA5D2 SERIES 18.13.12 Security Slave Registers Name: MATRIX_SSRx [x=0..14] Address: 0xF0018200 (0), 0xFC03C200 (1) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 WRNSECH7 WRNSECH6 WRNSECH5 WRNSECH4 WRNSECH3 WRNSECH2 WRNSECH1 WRNSECH0 15 14 13 12 11 10 9 8 RDNSECH7 RDNSECH6 RDNSECH5 RDNSECH4 RDNSECH3 RDNSECH2 RDNSECH1 RDNSECH0 7 6 5 4 3 2 1 0 LANSECH7 LANSECH6 LANSECH5 LANSECH4 LANSECH3 LANSECH2 LANSECH1 LANSECH0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. LANSECHx: Low Area Non-secured in HSELx Security Region 0: The security of the HSELx AHB slave area lying below the corresponding MATRIX_SASSR.SASPLITx boundary is configured according to RDNSECHx and WRNSECHx. The entire remaining HSELx upper address space is configured as Non-secured access. 1: The HSELx AHB slave address area lying below the corresponding MATRIX_SASSR.SASPLITx boundary is configured as Nonsecured access, and the entire remaining upper address space according to RDNSECHx and WRNSECHx. RDNSECHx: Read Non-secured for HSELx Security Region 0: The HSELx AHB slave security region is split into one Read Secured and one Read Non-secured area, according to LANSECHx and MATRIX_SASSR.SASPLITx. That is, the so defined Securable High or Low Area is Secured for Read access. 1: The HSELx AHB slave security region is Non-secured for Read access. WRNSECHx: Write Non-secured for HSELx Security Region 0: The HSELx AHB slave security region is split into one Write Secured and one Write Non-secured area, according to LANSECHx and MATRIX_SASSR.SASPLITx. That is, the so defined Securable High or Low Area is Secured for Write access. 1: The HSELx AHB slave security region is Non-secured for Write access. Securable Area access rights: WRNSECHx / RDNSECHx Non-secure Access Secure Access 00 Denied Write - Read 01 Read Write - Read 10 Write Write - Read 11 Write - Read Write - Read DS60001476B-page 196  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.13 Security Areas Split Slave Registers Name: MATRIX_SASSRx [x=0..14] Address: 0xF0018240 (0), 0xFC03C240 (1) Access: 31 Read/Write 30 29 28 27 26 SASPLIT7 23 22 21 20 19 18 SASPLIT5 15 14 13 6 24 17 16 9 8 1 0 SASPLIT4 12 11 10 SASPLIT3 7 25 SASPLIT6 SASPLIT2 5 4 3 SASPLIT1 2 SASPLIT0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. SASPLITx: Security Areas Split for HSELx Security Region This field defines the boundary address offset where the HSELx AHB slave security region splits into two Security Areas whose access is controlled according to the corresponding MATRIX_SSR. It also defines the Security Low Area size inside the HSELx region. If this Low Area size is set at or above the HSELx Region Size, then the Security High Area is no longer available and the MATRIX_SSR settings for the Low Area apply to the entire HSELx Security Region. SASPLITx Split Offset Security Low Area Size 0000 0x00001000 4 Kbytes 0001 0x00002000 8 Kbytes 0010 0x00004000 16 Kbytes 0011 0x00008000 32 Kbytes 0100 0x00010000 64 Kbytes 0101 0x00020000 128 Kbytes 0110 0x00040000 256 Kbytes 0111 0x00080000 512 Kbytes 1000 0x00100000 1 Mbyte 1001 0x00200000 2 Mbytes 1010 0x00400000 4 Mbytes 1011 0x00800000 8 Mbytes 1100 0x01000000 16 Mbytes 1101 0x02000000 32 Mbytes 1110 0x04000000 64 Mbytes 1111 0x08000000 128 Mbytes  2017 Microchip Technology Inc. DS60001476B-page 197 SAMA5D2 SERIES 18.13.14 Security Region Top Slave Registers Name: MATRIX_SRTSRx [x=0..14] Address: 0xF0018284 (0), 0xFC03C284 (1) Access: Read/Write 31 30 29 28 27 26 SRTOP7 23 22 21 20 19 18 SRTOP5 15 14 13 6 24 17 16 9 8 1 0 SRTOP4 12 11 10 SRTOP3 7 25 SRTOP6 SRTOP2 5 4 3 2 SRTOP1 SRTOP0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. SRTOPx: HSELx Security Region Top This field defines the size of the HSELx security region address space. Invalid sizes for the slave region must never be programmed. Valid sizes and number of security regions are product-, slave- and slave-configuration dependent. Note: The slaves featuring multiple scalable contiguous security regions have a single SRTOP0 field for all the security regions. If this HSELx security region size is set at or below the HSELx low area size, then there is no Security High Area and the MATRIX_SSR settings for the Low Area apply to the whole HSELx security region. SRTOPx Top Offset Security Region Size 0000 0x00001000 4 Kbytes 0001 0x00002000 8 Kbytes 0010 0x00004000 16 Kbytes 0011 0x00008000 32 Kbytes 0100 0x00010000 64 Kbytes 0101 0x00020000 128 Kbytes 0110 0x00040000 256 Kbytes 0111 0x00080000 512 Kbytes 1000 0x00100000 1 Mbyte 1001 0x00200000 2 Mbytes 1010 0x00400000 4 Mbytes 1011 0x00800000 8 Mbytes 1100 0x01000000 16 Mbytes 1101 0x02000000 32 Mbytes 1110 0x04000000 64 Mbytes 1111 0x08000000 128 Mbytes DS60001476B-page 198  2017 Microchip Technology Inc. SAMA5D2 SERIES 18.13.15 Security Peripheral Select x Registers Name: MATRIX_SPSELRx [x=1..3] Address: 0xF00182C0 (0), 0xFC03C2C0 (1) Access: Read/Write 31 30 29 28 27 26 25 24 NSECP31 NSECP30 NSECP29 NSECP28 NSECP27 NSECP26 NSECP25 NSECP24 23 22 21 20 19 18 17 16 NSECP23 NSECP22 NSECP21 NSECP20 NSECP19 NSECP18 NSECP17 NSECP16 15 14 13 12 11 10 9 8 NSECP15 NSECP14 NSECP13 NSECP12 NSECP11 NSECP10 NSECP9 NSECP8 7 6 5 4 3 2 1 0 NSECP7 NSECP6 NSECP5 NSECP4 NSECP3 NSECP2 NSECP1 NSECP0 This register can only be written if the WPEN bit is cleared in the Write Protection Mode Register. Each MATRIX_SPSELR can configure the access security type for up to 32 peripherals: – MATRIX_SPSELR1 configures the access security type for peripheral identifiers 0–31 (bits NSECP0– NSECP31). – MATRIX_SPSELR2 configures the access security type for peripheral identifiers 32–63 (bits NSECP0– NSECP31). – MATRIX_SPSELR3 configures the access security type for peripheral identifiers 64–95 (bits NSECP0– NSECP31). Note: The actual number of peripherals implemented is device-specific; see Table 18-9 ”Peripheral Identifiers” for details. NSECPy: Non-secured Peripheral 0: The selected peripheral address space is configured as “Secured” access (value of ‘0’ has no effect if the peripheral security type is “Peripheral Always Non-secured”). 1: The selected peripheral address space is configured as “Non-secured” access (value of ‘1’ has no effect if the peripheral security type is “Peripheral Always Secured”).  2017 Microchip Technology Inc. DS60001476B-page 199 SAMA5D2 SERIES 19. Special Function Registers (SFR) 19.1 Description Special Function Registers (SFR) manage specific aspects of the integrated memory, bridge implementations, processor and other functionality not controlled elsewhere. 19.2 Embedded Characteristics • 32-bit Special Function Registers control specific behavior of the product DS60001476B-page 200  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3 Special Function Registers (SFR) User Interface Table 19-1: Offset (1) Register Mapping Register Name Access Reset 0x00 Reserved – – – 0x04 DDR Configuration Register SFR_DDRCFG Read/Write 0x01 Reserved – – – 0x10 OHCI Interrupt Configuration Register SFR_OHCIICR Read/Write 0x0 0x14 OHCI Interrupt Status Register SFR_OHCIISR Read-only – 0x18 Reserved – – – 0x1C Reserved – – – 0x20–0x24 Reserved – – – 0x28 Security Configuration Register SFR_SECURE Read/Write 0x0 0x2C Reserved – – – 0x30 UTMI Clock Trimming Register SFR_UTMICKTRIM Read/Write 0x00010000 0x34 UTMI High-Speed Trimming Register SFR_UTMIHSTRIM Read/Write 0x00044433 0x38 UTMI Full-Speed Trimming Register SFR_UTMIFSTRIM Read/Write 0x00430211 0x3C UTMI DP/DM Pin Swapping Register SFR_UTMISWAP Read/Write 0x0 0x40 Reserved – – – 0x44 Reserved – – – 0x48 CAN Memories Address-based Register SFR_CAN Read/Write 0x00200020 0x4C Serial Number 0 Register SFR_SN0 Read-only – 0x50 Serial Number 1 Register SFR_SN1 Read-only – 0x54 AIC Interrupt Redirection Register SFR_AICREDIR Read/Write 0x0 0x58 L2CC_HRAMC1 SFR_L2CC_HRAMC Read/Write 0x0 Reserved – – – 0x90 I2SC Register SFR_I2SCLKSEL Read/Write 0x0 0x94 QSPI Clock Pad Supply Select Register QSPICLK_REG Read/Write 0x1 Reserved – – – 0x08–0x0C 0x5C–0x8C 0x98–0x3FFC Note 1: If an offset is not listed in the table, it must be considered as reserved.  2017 Microchip Technology Inc. DS60001476B-page 201 SAMA5D2 SERIES 19.3.1 DDR Configuration Register Name: SFR_DDRCFG Address: 0xF8030004 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – FDQSIEN FDQIEN 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – – FDQIEN: Force DDR_DQ Input Buffer Always On 0: DDR_DQ input buffer controlled by DDR controller. 1: DDR_DQ input buffer always on. FDQSIEN: Force DDR_DQS Input Buffer Always On 0: DDR_DQS input buffer controlled by DDR controller. 1: DDR_DQS input buffer always on. Note: FDQIEN and FDQSIEN = 1 are used to force the selection of the analog comparator inside the IO. If those bits are cleared the DDR controller automatically manages the selection of the analog comparator. Forcing the bits to 0 reduces power consumption. DS60001476B-page 202  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.2 OHCI Interrupt Configuration Register Name: SFR_OHCIICR Address: 0xF8030010 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – HSIC_SEL – – – 23 22 21 20 19 18 17 16 UDPPUDIS – – – – – – – 15 14 13 12 11 10 9 8 – – – – – SUSPEND_C SUSPEND_B SUSPEND_A 7 6 5 4 3 2 1 0 – – APPSTART ARIE – RES2 RES1 RES0 RESx: USB PORTx RESET 0: Resets USB Port. 1: Usable USB Port. ARIE: OHCI Asynchronous Resume Interrupt Enable 0: Interrupt disabled. 1: Interrupt enabled. APPSTART: Reserved 0: Must write 0. SUSPEND_A: USB PORT A 0: Suspends controlled by EHCI-OCHO. 1: Forces the suspend for PORTA. SUSPEND_B: USB PORT B 0: Suspend controlled by EHCI-OCHO. 1: Forces the suspend for PORTB. SUSPEND_C: USB PORT C 0: Suspends controlled by EHCI-OCHO. 1: Forces the suspend for PORTC. UDPPUDIS: USB DEVICE PULLUP DISABLE 0: USB device pullup connection is enabled. 1: USB device pullup connection is disabled. HSIC_SEL: Reserved 0: Must write 0.  2017 Microchip Technology Inc. DS60001476B-page 203 SAMA5D2 SERIES 19.3.3 OHCI Interrupt Status Register Name: SFR_OHCIISR Address: 0xF8030014 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – RIS2 RIS1 RIS0 RISx: OHCI Resume Interrupt Status Port x 0: OHCI port resume not detected. 1: OHCI port resume detected. DS60001476B-page 204  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.4 Security Configuration Register Name: SFR_SECURE Address: 0xF8030028 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – FUSE 7 6 5 4 3 2 1 0 – – – – – – – ROM ROM: Disable Access to ROM Code This bit is writable once only. When the ROM is secured, only a reset signal can clear this bit. 0: ROM is enabled. 1: ROM is disabled. FUSE: Disable Access to Fuse Controller This bit is writable once only. When the Fuse Controller is secured, only a reset signal can clear this bit. 0: Fuse Controller is enabled. 1: Fuse Controller is disabled.  2017 Microchip Technology Inc. DS60001476B-page 205 SAMA5D2 SERIES 19.3.5 UTMI Clock Trimming Register Name: SFR_UTMICKTRIM Address: 0xF8030030 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 1 7 6 5 4 3 2 – – – – – – 16 VBG 0 FREQ FREQ: UTMI Reference Clock Frequency Value Name Description 0 12 12 MHz reference clock 1 16 16 MHz reference clock 2 24 24 MHz reference clock 3 12 12 MHz reference clock VBG: UTMI Band Gap Voltage Trimming DS60001476B-page 206  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.6 UTMI High-Speed Trimming Register Name: SFR_UTMIHSTRIM Address: 0xF8030034 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – 15 14 13 12 11 – 7 SLOPE2 10 SLOPE1 6 – 5 9 8 SLOPE0 4 DISC 3 – 2 1 0 SQUELCH SQUELCH: UTMI HS SQUELCH Voltage Trimming Calibration bits to adjust squelch threshold. DISC: UTMI Disconnect Voltage Trimming Calibration bits to adjust disconnect threshold. SLOPEx: UTMI HS PORTx Transceiver Slope Trimming Calibration bits to adjust HS Transceiver output slope for PORTx.  2017 Microchip Technology Inc. DS60001476B-page 207 SAMA5D2 SERIES 19.3.7 UTMI Full-Speed Trimming Register Name: SFR_UTMIFSTRIM Address: 0xF8030038 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – ZP – ZN 15 14 13 12 11 10 – – – – – – 7 6 5 4 3 2 – FALL – 9 8 XCVR 1 0 RISE RISE: FS Transceiver Output Rising Slope Trimming Calibration bits to adjust the FS transceiver output rising slope. FALL: FS Transceiver Output Falling Slope Trimming Calibration bits to adjust the FS transceiver output falling slope. XCVR: FS Transceiver Crossover Voltage Trimming Calibration bits to adjust the FS transceiver crossover voltage. ZN: FS Transceiver NMOS Impedance Trimming Calibration bits to adjust the FS transceiver NMOS output impedance. ZP: FS Transceiver PMOS Impedance Trimming Calibration bits to adjust the FS transceiver PMOS output impedance. DS60001476B-page 208  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.8 UMTI DP/DM Pin Swapping Register Name: SFR_UTMISWAP Address: 0xF803003C Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – PORT2 PORT1 PORT0 PORTx: PORT x DP/DM Pin Swapping 0 (NORMAL): DP/DM normal pinout. 1 (SWAPPED): DP/DM swapped pinout.  2017 Microchip Technology Inc. DS60001476B-page 209 SAMA5D2 SERIES 19.3.9 CAN Memories Address-based Register Name: SFR_CAN Address: 0xF8030048 Access: Read/Write 31 30 29 28 27 26 25 24 18 17 16 10 9 8 2 1 0 EXT_MEM_CAN1_ADDR 23 22 21 20 19 EXT_MEM_CAN1_ADDR 15 14 13 12 11 EXT_MEM_CAN0_ADDR 7 6 5 4 3 EXT_MEM_CAN0_ADDR EXT_MEM_CAN0_ADDR: MSB CAN0 DMA Base Address Gives the 16-bit MSB of the CAN0 DMA base address. The 16-bit LSB must be programmed in the CAN0 user interface. EXT_MEM_CAN1_ADDR: MSB CAN1 DMA Base Address Gives the 16-bit MSB of the CAN1 DMA base address. The 16-bit LSB must be programmed in the CAN1 user interface. DS60001476B-page 210  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.10 Serial Number 0 Register Name: SFR_SN0 Address: 0xF803004C Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 SN0 23 22 21 20 SN0 15 14 13 12 SN0 7 6 5 4 SN0 This register is used to read the first 32 bits of the 64-bit Serial Number (unique ID). SN0: Serial Number 0  2017 Microchip Technology Inc. DS60001476B-page 211 SAMA5D2 SERIES 19.3.11 Serial Number 1 Register Name: SFR_SN1 Address: 0xF8030050 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 SN1 23 22 21 20 SN1 15 14 13 12 SN1 7 6 5 4 SN1 This register is used to read the last 32 bits of the 64-bit Serial Number (unique ID). SN1: Serial Number 1 DS60001476B-page 212  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.12 AIC Interrupt Redirection Register Name: SFR_AICREDIR Address: 0xF8030054 Access: 31 Read/Write 30 29 28 27 26 25 24 18 17 16 10 9 8 2 1 AICREDIRKEY 23 22 21 20 19 AICREDIRKEY 15 14 13 12 11 AICREDIRKEY 7 6 5 4 3 0 AICREDIRKEY NSAIC NSAIC: Interrupt Redirection to Non-Secure AIC 0: Interrupts are managed by the AIC corresponding to the Secure State of the peripheral (secure AIC or non-secure AIC). 1: All interrupts are managed by the non-secure AIC. AICREDIRKEY: Unlock Key Value is a XOR between 0xb6d81c4d and SN1[31:0] but only field [31:1] of the result must be written in this field. In case of set in Secure mode by fuse configuration, this register is read_only 0 (it is not possible to redirect secure interrupts on non-secure AIC for products set in secure mode for security reasons). Note: After three tries, entering a wrong key results in locking the NSAIC bit. A reset is needed.  2017 Microchip Technology Inc. DS60001476B-page 213 SAMA5D2 SERIES 19.3.13 HRAMC L2CC Register Name: SFR_L2CC_HRAMC Address: 0xF8030058 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – SRAM_SEL This register is used to configure the L2 cache to be used as an internal SRAM. SRAM_SEL: SRAM Selector 0: Selects SRAM. 1: Selects L2CC. DS60001476B-page 214  2017 Microchip Technology Inc. SAMA5D2 SERIES 19.3.14 I2S Register Name: SFR_I2SCLKSEL Address: 0xF8030090 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – CLKSEL1 CLKSEL0 CLKSEL0: Clock Selection 0 0: Selects PCLK (peripheral clock). 1: Selects GCLK. CLKSEL1: Clock Selection 1 0: Selects PCLK (peripheral clock). 1: Selects GCLK.  2017 Microchip Technology Inc. DS60001476B-page 215 SAMA5D2 SERIES 19.3.15 QSPI Clock Pad Supply Select Register Name: QSPICLK_REG Address: 0xF8030094 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – SUP_SEL SUP_SEL: Supply Selection 0: 1.8V supply selected. 1: 3.3V supply selected. DS60001476B-page 216  2017 Microchip Technology Inc. SAMA5D2 SERIES 20. Special Function Registers Backup (SFRBU) 20.1 Description Special Function Registers Backup (SFRBU) manages specific aspects of the integrated memory, bridge implementations, processor and other functionality not controlled elsewhere. 20.2 Embedded Characteristics • 32-bit Special Function Registers Backup controls specific behavior of the product.  2017 Microchip Technology Inc. DS60001476B-page 217 SAMA5D2 SERIES 20.3 Special Function Registers Backup (SFRBU) User Interface Table 20-1: Register Mapping Offset Register Name Access Reset 0x00 Power Switch BU Control Register SFRBU_PSWBUCTRL Read/Write 0x09 0x04 TS Range Configuration Register SFRBU_TSRANGECFG Read/Write 0x00 0x08 Reserved – – – 0x0C Reserved – – – 0x10 DDR BU Mode Control Register SFRBU_DDRBUMCR Read/Write 0x00 0x14 RXLP Pull-Up Control Register SFRBU_RXLPPUCR Read/Write 0x01 0x18-0xFC Reserved – – – 0x100 Reserved – – – 0x104–0x3FFC Reserved – – – DS60001476B-page 218  2017 Microchip Technology Inc. SAMA5D2 SERIES 20.3.1 SFRBU Power Switch BU Control Register Name: SFRBU_PSWBUCTRL Address: 0xFC05C000 Access: 31 Read/Write 30 29 28 27 26 25 24 18 17 16 10 9 8 KEY PSW MODE 23 22 21 20 19 KEY PSW MODE 15 14 13 12 11 KEY PSW MODE 7 6 5 4 3 2 1 0 – – – – STATE SMCTRL SSWCTRL SCTRL SCTRL: Power Switch BU Software Control This bit is used to control the Power Switch BU state by software in addition to the SSWCTRL bit. 0: Power Switch BU is controlled by hardware (SSWCTRL bit has no action). 1 (Reset value): Power Switch BU is controlled by software (SSWCTRL bit has an action). SSWCTRL: Power Switch BU Source Selection This bit has an action only if SCTRL bit value is “1”. 0 (Reset value): LDO Supply source is VDDBU. 1: LDO Supply source is VDDANA. SMCTRL: Allow Power Switch BU Control by Security Module Autobackup (Hardware) Enables to select automatically the VDDBU source when the security module enters Backup mode. This automatic supply source switching is independent from the SCTRL and SSWCTRL bits. 0 (Reset value): No automatic supply source switching from security module. 1: Automatic supply source switching from security module activated. STATE: Power Switch BU state (Read-only) This bit reflects the power switch BU supply source selection in real time. After a switching request, the user must wait for the analog cell switching time to have an updated status (see Electrical Characteristics section). 0: LDO BU Supply source is VDDBU. 1: LDO BU Supply source is VDDANA. KEY_PSW_MODE: Specific value mandatory to allow writing of other register bits (Write-only) This field is a security key preventing power switch changes due to software error or malicious code. 0x4BD20C: SFRBU_PSWBUCTRL register write possible. Other values: SFRBU_PSWBUCTRL register write impossible.  2017 Microchip Technology Inc. DS60001476B-page 219 SAMA5D2 SERIES 20.3.2 SFRBU Temperature Sensor Range Configuration Register Name: SFRBU_TSRANGECFG Address: 0xFC05C004 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – TSHRSEL TSHRSEL: Temperature Sensor Range Selection 0 (Reset value): Temperature Sensor High Triggering level is +105°C (internal transistor junction temperature). 1: Temperature Sensor High Triggering level is +115°C (internal transistor junction temperature). DS60001476B-page 220  2017 Microchip Technology Inc. SAMA5D2 SERIES 20.3.3 SFRBU DDR BU Mode Control Register Name: SFRBU_DDRBUMCR Address: 0xFC05C010 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – BUMEN BUMEN: DDR BU Mode Enable This bit is used to isolate the DDR Pads from the CPU domain (VDDCORE). It has to be set after enabling the Self-refresh mode on the DDR memory and before doing power-down on VDDCORE.(1) 0 (Reset value): DDR Backup mode disabled. The DDR pads are not isolated from CPU domain. 1: DDR Backup mode enabled. The DDR pads are isolated from CPU domain (IOs are in memory state). Note 1: To enable Self-refresh mode, refer to MPDDRC Low-power Register (in Multi-port DDR-SDRAM Controller section) and to Self-refresh Backup mode (in Electrical Characteristics section).  2017 Microchip Technology Inc. DS60001476B-page 221 SAMA5D2 SERIES 20.3.4 SFRBU RXLP Pull-Up Control Register Name: SFRBU_RXLPPUCR Address: 0xFC05C014 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – RXDPUCTRL RXDPUCTRL: RXLP RXD Pull-Up Control 0 (Reset value): Pull-up enabled on RXD IO. 1: Pull-up disabled on RXD IO. Note: If the RXLP is not used, it is recommended to enable the pull-up to avoid power consumption on VDDBU rail. DS60001476B-page 222  2017 Microchip Technology Inc. SAMA5D2 SERIES 21. Advanced Interrupt Controller (AIC) 21.1 Description The Advanced Interrupt Controller (AIC) is an 8-level priority, individually maskable, vectored interrupt controller providing handling of up to one hundred and twenty-eight interrupt sources. It is designed to substantially reduce the software and real-time overhead in handling internal and external interrupts. The AIC drives the nFIQ (fast interrupt request) and the nIRQ (standard interrupt request) inputs of an ARM processor. Inputs of the AIC are either internal peripheral interrupts or external interrupts coming from the product's pins. The 8-level Priority Controller allows the user to define the priority for each interrupt source, thus permitting higher priority interrupts to be serviced even if a lower priority interrupt is being processed. Internal interrupt sources can be programmed to be level-sensitive or edge-triggered. External interrupt sources can be programmed to be rising-edge or falling-edge triggered or high-level or low-level sensitive. 21.2 Embedded Characteristics • Controls the Interrupt Lines (nIRQ and nFIQ) of an ARM Processor • 128 Individually Maskable and Vectored Interrupt Sources - Source 0 is reserved for the fast interrupt input (FIQ) - Source 74 is reserved for system peripheral interrupts - Sources 2 to 73 and Sources 75 to 127 control up to 125 embedded peripheral interrupts or external interrupts - Programmable edge-triggered or level-sensitive internal sources - Programmable rising/falling edge-triggered or high/low level-sensitive external sources • 8-level Priority Controller - Drives the normal interrupt of the processor - Handles priority of the interrupt sources 1 to 127 - Higher priority interrupts can be served during service of lower priority interrupt • Vectoring - Optimizes interrupt service routine branch and execution - One 32-bit vector register for all interrupt sources - Interrupt vector register reads the corresponding current interrupt vector • Protect Mode - Easy debugging by preventing automatic operations when protect models are enabled • General Interrupt Mask - Provides processor synchronization on events without triggering an interrupt • Register Write Protection • AIC0 is Non-Secure AIC, AIC1 is Secure AIC • AIC0 manages nIRQ line, AIC1 manages nFIQ line  2017 Microchip Technology Inc. DS60001476B-page 223 SAMA5D2 SERIES 21.3 Block Diagram Figure 21-1: Block Diagram FIQ Secure AIC ARM Processor Up to 128 Sources Secure Secure Secure Peripheral Embedded Peripheral nFIQ nIRQ nFIQ nIRQ APB Non-Secure AIC IRQ0-IRQn nFIQ Up to 128 Sources Embedded PeripheralEE Embedded nIRQ Peripheral Embedded Peripheral 21.4 Application Block Diagram Figure 21-2: Description of the Application Block OS-based Applications Standalone Applications OS Drivers RTOS Drivers Hard Real-Time Tasks General OS Interrupt Handler Advanced Interrupt Controller Embedded Peripherals DS60001476B-page 224 External Peripherals (External Interrupts)  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.5 AIC Detailed Block Diagram Figure 21-3: AIC Detailed Block Diagram IRQ NonSecured AIC Non-Secured Peripheral nIRQ FIQ Secured Peripheral Secured AIC Cortex-A5 nFIQ Secured MATRIX Master / Slave Always Secured Secured AIC 21.6 Programmable by Software Security Always NonSecured I/O Line Description Table 21-1: I/O Line Description Pin Name Pin Description Type FIQ Fast Interrupt Input IRQ0–IRQn Interrupt 0–Interrupt n Input  2017 Microchip Technology Inc. DS60001476B-page 225 SAMA5D2 SERIES 21.7 Product Dependencies 21.7.1 I/O Lines The interrupt signals FIQ and IRQ0 to IRQn are normally multiplexed through the PIO controllers. Depending on the features of the PIO controller used in the product, the pins must be programmed in accordance with their assigned interrupt functions. This is not applicable when the PIO controller used in the product is transparent on the input path. Table 21-2: I/O Lines Instance Signal I/O Line Peripheral AIC FIQ PB4 C AIC FIQ PC8 C AIC FIQ PC9 A AIC FIQ PD3 B AIC IRQ PA12 B AIC IRQ PA21 A AIC IRQ PB3 C AIC IRQ PD31 C 21.7.2 Power Management The Advanced Interrupt Controller is continuously clocked. The Power Management Controller has no effect on the Advanced Interrupt Controller behavior. The assertion of the Advanced Interrupt Controller outputs, either nIRQ or nFIQ, wakes up the ARM processor while it is in Idle mode. The General Interrupt Mask feature enables the AIC to wake up the processor without asserting the interrupt line of the processor, thus providing synchronization of the processor on an event. 21.7.3 Interrupt Sources Interrupt Source 0 is always located at FIQ. If the product does not feature any FIQ pin, Interrupt Source 0 cannot be used. Interrupt Source 1 is always located at System Interrupt. This is the result of the OR-wiring of the system peripheral interrupt lines. When a system interrupt occurs, the service routine must first distinguish the cause of the interrupt. This is performed by reading successively the status registers of the above-mentioned system peripherals. Interrupt sources 2 to 73 and 75 to 127 can either be connected to the interrupt outputs of an embedded user peripheral, or to external interrupt lines. The external interrupt lines can be connected either directly or through the PIO Controller. PIO controllers are considered as user peripherals in the scope of interrupt handling. Accordingly, the PIO controller interrupt lines are connected to interrupt sources 2 to 73 and 75 to 127. The peripheral identification defined at the product level corresponds to the interrupt source number (as well as the bit number controlling the clock of the peripheral). Consequently, to simplify the description of the functional operations and the user interface, the interrupt sources are named FIQ, SYS, and PID2 to PID73 and PID75 to PID127. AIC0 manages all Non-Secure Interrupts including IRQn; AIC1 manages all Secure Interrupts including FIQ. Each AIC has its own User Interface. The user should pay attention to use the relevant user interface for each source. DS60001476B-page 226  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.8 21.8.1 21.8.1.1 Functional Description Interrupt Source Control Interrupt Source Mode The Advanced Interrupt Controller independently programs each interrupt source. The SRCTYPE field of the Source Mode register (AIC_SMR) selects the interrupt condition of the interrupt source selected by the INTSEL field of the Source Select register (AIC_SSR). Note: Configuration registers such as AIC_SMR and AIC_SSR return the values corresponding to the interrupt source selected by INTSEL. The internal interrupt sources wired on the interrupt outputs of the embedded peripherals can be programmed either in Level-Sensitive mode or in Edge-Triggered mode. The active level of the internal interrupts is not important for the user. The external interrupt sources can be programmed either in High Level-Sensitive or Low Level-Sensitive modes, or in Rising Edge-Triggered or Negative Edge-Triggered modes. 21.8.1.2 Interrupt Source Enabling Each interrupt source, including the FIQ in source 0, can be enabled or disabled by using the command registers Interrupt Enable Command register (AIC_IECR) and Interrupt Disable Command register (AIC_IDCR). The interrupt mask of the selected interrupt source can be read in the Interrupt Mask register (AIC_IMR). A disabled interrupt does not affect servicing of other interrupts. 21.8.1.3 Interrupt Clearing and Setting All interrupt sources programmed to be edge-triggered (including the FIQ in source 0) can be individually set or cleared by writing respectively the Interrupt Set Command register (AIC_ISCR) and Interrupt Clear Command register (AIC_ICCR). Clearing or setting interrupt sources programmed in Level-Sensitive mode has no effect. The clear operation is perfunctory, as the software must perform an action to reset the “memorization” circuitry activated when the source is programmed in Edge-Triggered mode. However, the set operation is available for auto-test or software debug purposes. It can also be used to execute an AIC-implementation of a software interrupt. The AIC features an automatic clear of the current interrupt when AIC_IVR (Interrupt Vector register) is read. Only the interrupt source being detected by the AIC as the current interrupt is affected by this operation. (See Section 21.8.3.1 “Priority Controller”.) The automatic clear reduces the operations required by the interrupt service routine entry code to read AIC_IVR. The automatic clear of interrupt source 0 is performed when the FIQ Vector register (AIC_FVR) is read. 21.8.1.4 Interrupt Status Interrupt Pending registers (AIC_IPR) represent the state of the interrupt lines, whether they are masked or not. AIC_IMR can be used to define the mask of the interrupt lines. The Interrupt Status register (AIC_ISR) reads the number of the current interrupt (see Section 21.8.3.1 “Priority Controller”) and the Core Interrupt Status register (AIC_CISR) gives an image of the nIRQ and nFIQ signals driven on the processor. Each status referred to above can be used to optimize the interrupt handling of the systems.  2017 Microchip Technology Inc. DS60001476B-page 227 SAMA5D2 SERIES 21.8.1.5 Internal Interrupt Source Input Stage Figure 21-4: Internal Interrupt Source Input Stage AIC_SMRi (SRCTYPE) Level/ Edge Source i AIC_IPR AIC_IMR Fast Interrupt Controller or Priority Controller Edge Detector AIC_IECR Set Clear FF AIC_ISCR AIC_ICCR AIC_IDCR 21.8.1.6 External Interrupt Source Input Stage Figure 21-5: External Interrupt Source Input Stage High/Low AIC_SMRi (SRCTYPE) Level/ Edge AIC_IPR AIC_IMR Source i Fast Interrupt Controller or Priority Controller AIC_IECR Rising/Falling Edge Detector Set FF Clear AIC_ISCR AIC_IDCR AIC_ICCR 21.8.2 Interrupt Latencies Global interrupt latencies depend on several parameters, including: • • • • The time the software masks the interrupts Occurrence, either at the processor level or at the AIC level The execution time of the instruction in progress when the interrupt occurs The treatment of higher priority interrupts and the resynchronization of the hardware signals This section addresses hardware resynchronizations only. It gives details about the latency times between the events on an external interrupt leading to a valid interrupt (edge or level) or the assertion of an internal interrupt source and the assertion of the nIRQ or nFIQ line on the processor. The resynchronization time depends on the programming of the interrupt source and on its type (internal or external). For the standard interrupt, resynchronization times are given assuming there is no higher priority in progress. The PIO Controller multiplexing has no effect on the interrupt latencies of the external interrupt sources. DS60001476B-page 228  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.8.2.1 External Interrupt Edge Triggered Source Figure 21-6: External Interrupt Edge Triggered Source MCK IRQ or FIQ (rising edge) IRQ or FIQ (falling edge) nIRQ Maximum IRQ Latency = 4 cycles nFIQ Maximum FIQ Latency = 4 cycles 21.8.2.2 External Interrupt Level Sensitive Source Figure 21-7: External Interrupt Level Sensitive Source MCK IRQ or FIQ (high level) IRQ or FIQ (low level) nIRQ Maximum IRQ Latency = 3 cycles nFIQ Maximum FIQ Latency = 3 cycles  2017 Microchip Technology Inc. DS60001476B-page 229 SAMA5D2 SERIES 21.8.2.3 Internal Interrupt Edge Triggered Source Figure 21-8: Internal Interrupt Edge Triggered Source MCK IRQ or FIQ (high level) IRQ or FIQ (low level) nIRQ Maximum IRQ Latency = 3 cycles nFIQ Maximum FIQ Latency = 3 cycles 21.8.2.4 Internal Interrupt Level Sensitive Source Figure 21-9: Internal Interrupt Level Sensitive Source MCK nIRQ Maximum IRQ Latency = 3.5 cycles Peripheral Interrupt Becomes Active 21.8.3 21.8.3.1 Normal Interrupt Priority Controller An 8-level priority controller drives the nIRQ line of the processor, depending on the interrupt conditions occurring on the interrupt sources 1 to 127. Each interrupt source has a programmable priority level of 7 to 0, which is user-definable by writing AIC_SMR.PRIOR. Level 7 is the highest priority and level 0 the lowest. As soon as an interrupt condition occurs, as defined by AIC_SMR.SRCTYPE, the nIRQ line is asserted. As a new interrupt condition might have happened on other interrupt sources since the nIRQ has been asserted, the priority controller determines the current interrupt at the time AIC_IVR is read. The read of AIC_IVR is the entry point of the interrupt handling which allows the AIC to consider that the interrupt has been taken into account by the software. The current priority level is defined as the priority level of the current interrupt. If several interrupt sources of equal priority are pending and enabled when AIC_IVR is read, the interrupt with the lowest interrupt source number is serviced first. The nIRQ line can be asserted only if an interrupt condition occurs on an interrupt source with a higher priority. If an interrupt condition happens (or is pending) during the interrupt treatment in progress, it is delayed until the software indicates to the AIC the end of the current service by writing AIC_EOICR (End of Interrupt Command register). The write of AIC_EOICR is the exit point of the interrupt handling. 21.8.3.2 Interrupt Nesting The priority controller utilizes interrupt nesting in order for the high priority interrupt to be handled during the service of lower priority interrupts. This requires the interrupt service routines of the lower interrupts to re-enable the interrupt at the processor level. DS60001476B-page 230  2017 Microchip Technology Inc. SAMA5D2 SERIES When an interrupt of a higher priority happens during an already occurring interrupt service routine, the nIRQ line is re-asserted. If the interrupt is enabled at the core level, the current execution is interrupted and the new interrupt service routine should read AIC_IVR. At this time, the current interrupt number and its priority level are pushed into an embedded hardware stack, so that they are saved and restored when the higher priority interrupt servicing is finished and AIC_EOICR is written. The AIC is equipped with an 8-level wide hardware stack in order to support up to eight interrupt nestings to match the eight priority levels. 21.8.3.3 Interrupt Handlers This section gives an overview of the fast interrupt handling sequence when using the AIC. It is assumed that the programmer understands the architecture of the ARM processor, and especially the Processor Interrupt modes and the associated status bits. It is assumed that: 1. The Advanced Interrupt Controller has been programmed, AIC_SVR registers are loaded with corresponding interrupt service routine addresses and interrupts are enabled. The instruction at the ARM interrupt exception vector address is required to work with the vectoring. Load the PC with the absolute address of the interrupt handler. 2. When nIRQ is asserted, if the bit “I” of CPSR is 0, the sequence is as follows: 1. 2. 3. 4. 5. 6. The CPSR is stored in SPSR_irq, the current value of the Program Counter is loaded in the Interrupt link register (R14_irq) and the Program Counter (R15) is loaded with 0x18. In the following cycle during fetch at address 0x1C, the ARM core adjusts R14_irq, decrementing it by four. The ARM core enters Interrupt mode, if it has not already done so. When the instruction loaded at address 0x18 is executed, the program counter is loaded with the value read in AIC_IVR. Reading AIC_IVR has the following effects: Sets the current interrupt to be the pending and enabled interrupt with the highest priority. The current level is the priority level of the current interrupt. De-asserts the nIRQ line on the processor. Even if vectoring is not used, AIC_IVR must be read in order to de-assert nIRQ. Automatically clears the interrupt, if it has been programmed to be edge-triggered. Pushes the current level and the current interrupt number on to the stack. Returns the value written in AIC_SVR corresponding to the current interrupt. The previous step has the effect of branching to the corresponding interrupt service routine. This should start by saving the link register (R14_irq) and SPSR_IRQ. The link register must be decremented by four when it is saved if it is to be restored directly into the program counter at the end of the interrupt. For example, the instruction SUB PC, LR, #4 may be used. Further interrupts can then be unmasked by clearing the “I” bit in CPSR, allowing re-assertion of the nIRQ to be taken into account by the core. This can happen if an interrupt with a higher priority than the current interrupt occurs. The interrupt handler can then proceed as required, saving the registers that will be used and restoring them at the end. During this phase, an interrupt of higher priority than the current level will restart the sequence from step 1. Note: 7. 8. If the interrupt is programmed to be level-sensitive, the source of the interrupt must be cleared during this phase. The “I” bit in CPSR must be set in order to mask interrupts before exiting to ensure that the interrupt is completed in an orderly manner. AIC_EOICR must be written in order to indicate to the AIC that the current interrupt is finished. This causes the current level to be popped from the stack, restoring the previous current level if one exists on the stack. If another interrupt is pending, with lower or equal priority than the old current level but with higher priority than the new current level, the nIRQ line is re-asserted, but the interrupt sequence does not immediately start because the “I” bit is set in the core. SPSR_irq is restored. Finally, the saved value of the link register is restored directly into the PC. This has the effect of returning from the interrupt to whatever was being executed before, and of loading the CPSR with the stored SPSR, masking or unmasking the interrupts depending on the state saved in SPSR_irq. Note: 21.8.4 21.8.4.1 The “I” bit in SPSR is significant. If it is set, it indicates that the ARM core was on the verge of masking an interrupt when the mask instruction was interrupted. Hence, when SPSR is restored, the mask instruction is completed (interrupt is masked). Fast Interrupt Fast Interrupt Source Interrupt source 0 is the only source which can raise a fast interrupt request to the processor. Interrupt source 0 is generally connected to a FIQ pin of the product, either directly or through a PIO Controller.  2017 Microchip Technology Inc. DS60001476B-page 231 SAMA5D2 SERIES 21.8.4.2 Fast Interrupt Control The fast interrupt logic of the AIC has no priority controller. The mode of interrupt source 0 is programmed with AIC_SMR and INTSEL = 0; the PRIOR field of this register is not used even if it reads what has been written. AIC_SMR.SRCTYPE enables programming the fast interrupt source to be rising-edge triggered or falling-edge triggered or high-level sensitive or low-level sensitive. Writing 0x1 in AIC_IECR and AIC_IDCR respectively enables and disables the fast interrupt when INTSEL = 0. Bit 0 of AIC_IMR indicates whether the fast interrupt is enabled or disabled. 21.8.4.3 Fast Interrupt Handlers This section gives an overview of the fast interrupt handling sequence when using the AIC. It is assumed that the programmer understands the architecture of the ARM processor, and especially the Processor Interrupt modes and associated status bits. Assuming that: 1. 2. 3. The Advanced Interrupt Controller has been programmed, AIC_SVR is loaded with the fast interrupt service routine address, and interrupt source 0 is enabled. The Instruction at address 0x1C (FIQ exception vector address) is required to vector the fast interrupt. Load the PC with the absolute address of the interrupt handler. The user does not need nested fast interrupts. When nFIQ is asserted, if bit “F” of CPSR is 0, the sequence is: 1. 2. 3. The CPSR is stored in SPSR_fiq, the current value of the program counter is loaded in the FIQ link register (R14_FIQ) and the program counter (R15) is loaded with 0x1C. In the following cycle, during fetch at address 0x20, the ARM core adjusts R14_fiq, decrementing it by four. The ARM core enters FIQ mode. The routine must read AIC1_CISR to know if the interrupt is the FIQ or a Secure Internal interrupt. ldr ldr cmp beq r1, =REG_SAIC_CISR r1, [r1] r1, #AIC_CISR_NFIQ get_fiqvec_addr If FIQ is active, it is processed in priority, even if another interrupt is active. get_irqvec_addr ldr b get_fiqvec_addr ldr read_vec ldr r14, =REG_SAIC_IVR read_vec r14, =REG_SAIC_FVR r0, [r14] Now r0 contains the correct vector address, IVR for a Secure Internal interrupt or FVR for FIQ. The system can branch to the routine pointed to by r0. FIQ_Handler_Branch mov r14, pc bx r0 4. 5. The previous step enables branching to the corresponding interrupt service routine. It is not necessary to save the link register R14_fiq and SPSR_fiq if nested fast interrupts are not needed. The Interrupt Handler can then proceed as required. It is not necessary to save registers R8 to R13 because the FIQ mode has its own dedicated registers and registers R8 to R13 are banked. The other registers, R0 to R7, must be saved before being used, and restored at the end (before the next step). Note: 6. If the fast interrupt is programmed to be level-sensitive, the source of the interrupt must be cleared during this phase in order to de-assert interrupt source 0. Finally, Link register R14_fiq is restored into the PC after decrementing it by four (with instruction SUB PC, LR, #4 for example). This has the effect of returning from the interrupt to whatever was being executed before, loading the CPSR with the SPSR and masking or unmasking the fast interrupt depending on the state saved in the SPSR. Note: The “F” bit in SPSR is significant. If it is set, it indicates that the ARM core was just about to mask FIQ interrupts when the mask instruction was interrupted. Hence, when the SPSR is restored, the interrupted instruction is completed (FIQ is masked). Another way to handle the fast interrupt is to map the interrupt service routine at the address of the ARM vector 0x1C. This method does not use vectoring, so that reading AIC_FVR must be performed at the very beginning of the handler operation. However, this method saves the execution of a branch instruction. DS60001476B-page 232  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.8.5 Protect Mode The Protect mode is used to read the Interrupt Vector register without performing the associated automatic operations. This is necessary when working with a debug system. When a debugger, working either with a Debug Monitor or the ARM processor's ICE, stops the applications and updates the opened windows, it might read the AIC User Interface and thus the IVR. This has adverse consequences: • If an enabled interrupt with a higher priority than the current one is pending, it is stacked. • If there is no enabled pending interrupt, the spurious vector is returned. In either case, an End of Interrupt command is necessary to acknowledge and restore the context of the AIC. This operation is generally not performed by the debug system, as the debug system would become strongly intrusive and cause the application to enter an undesired state. This is avoided by using the Protect mode. Writing PROT in the Debug Control register (AIC_DCR) at 0x1 enables the Protect mode. When the Protect mode is enabled, the AIC performs interrupt stacking only when a write access is performed on AIC_IVR. Therefore, the Interrupt Service Routines must write (arbitrary data) to AIC_IVR just after reading it. The new context of the AIC, including the value of AIC_ISR, is updated with the current interrupt only when AIC_IVR is written. An AIC_IVR read on its own (e.g., by a debugger) modifies neither the AIC context nor AIC_ISR. Extra AIC_IVR reads perform the same operations. However, it is recommended to not stop the processor between the read and the write of AIC_IVR of the interrupt service routine to make sure the debugger does not modify the AIC context. To summarize, in normal operating mode, the read of AIC_IVR performs the following operations within the AIC: 1. 2. 3. 4. 5. Calculates active interrupt (higher than current or spurious). Determines and returns the vector of the active interrupt. Memorizes the interrupt. Pushes the current priority level onto the internal stack. Acknowledges the interrupt. However, while the Protect mode is activated, only operations 1 to 3 are performed when AIC_IVR is read. Operations 4 and 5 are only performed by the AIC when AIC_IVR is written. Software that has been written and debugged using the Protect mode runs correctly in normal mode without modification. However, in normal mode, the AIC_IVR write has no effect and can be removed to optimize the code. 21.8.6 Spurious Interrupt The Advanced Interrupt Controller features a protection against spurious interrupts. A spurious interrupt is defined as being the assertion of an interrupt source long enough for the AIC to assert the nIRQ, but no longer present when AIC_IVR is read. This is most prone to occur when: • An external interrupt source is programmed in Level-Sensitive mode and an active level occurs for only a short time. • An internal interrupt source is programmed in level-sensitive and the output signal of the corresponding embedded peripheral is activated for a short time (as is the case for the watchdog). • An interrupt occurs just a few cycles before the software begins to mask it, thus resulting in a pulse on the interrupt source. The AIC detects a spurious interrupt at the time AIC_IVR is read while no enabled interrupt source is pending. When this happens, the AIC returns the value stored by the programmer in the Spurious Vector register (AIC_SPU). The programmer must store the address of a spurious interrupt handler in AIC_SPU as part of the application, to enable an as fast as possible return to the normal execution flow. This handler writes in AIC_EOICR and performs a return from interrupt. 21.8.7 General Interrupt Mask The AIC features a General Interrupt Mask bit (AIC_DCR.GMSK) to prevent interrupts from reaching the processor. Both the nIRQ and the nFIQ lines are driven to their inactive state if AIC_DCR.GMSK is set. However, this mask does not prevent waking up the processor if it has entered Idle mode. This function facilitates synchronizing the processor on a next event and, as soon as the event occurs, performs subsequent operations without having to handle an interrupt. It is strongly recommended to use this mask with caution.  2017 Microchip Technology Inc. DS60001476B-page 233 SAMA5D2 SERIES 21.8.8 Register Write Protection To prevent any single software error from corrupting AIC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the AIC Write Protection Mode Register (AIC_WPMR). If a write access to a write-protected register is detected, the WPVS flag in the AIC Write Protection Status Register (AIC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading AIC_WPSR. The following registers can be write-protected: • • • • AIC Source Mode Register AIC Source Vector Register AIC Spurious Interrupt Vector Register AIC Debug Control Register DS60001476B-page 234  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9 Advanced Interrupt Controller (AIC) User Interface Table 21-3: Register Mapping Offset Register Name Access Reset 0x00 Source Select Register AIC_SSR Read/Write 0x0 0x04 Source Mode Register AIC_SMR Read/Write 0x0 0x08 Source Vector Register AIC_SVR Read/Write 0x0 0x0C Reserved – – – 0x10 Interrupt Vector Register AIC_IVR Read-only 0x0 0x14 FIQ Vector Register AIC_FVR Read-only 0x0 0x18 Interrupt Status Register AIC_ISR Read-only 0x0 0x1C Reserved – – – 0x20 (2) Interrupt Pending Register 0 AIC_IPR0 Read-only 0x0(1) 0x24 Interrupt Pending Register 1(2) AIC_IPR1 Read-only 0x0(1) 0x28 Interrupt Pending Register 2(2) AIC_IPR2 Read-only 0x0(1) 0x2C Interrupt Pending Register 3(2) AIC_IPR3 Read-only 0x0(1) 0x30 Interrupt Mask Register AIC_IMR Read-only 0x0 0x34 Core Interrupt Status Register AIC_CISR Read-only 0x0 0x38 End of Interrupt Command Register AIC_EOICR Write-only – 0x3C Spurious Interrupt Vector Register AIC_SPU Read/Write 0x0 0x40 Interrupt Enable Command Register AIC_IECR Write-only – 0x44 Interrupt Disable Command Register AIC_IDCR Write-only – 0x48 Interrupt Clear Command Register AIC_ICCR Write-only – 0x4C Interrupt Set Command Register AIC_ISCR Write-only – 0x50–0x5C Reserved – – – 0x60–0x68 Reserved – – – 0x6C Debug Control Register AIC_DCR Read/Write 0x0 0x70–0xE0 Reserved – – – 0xE4 Write Protection Mode Register AIC_WPMR Read/Write 0x0 0xE8 Write Protection Status Register AIC_WPSR Read-only 0x0 0xEC–0xFC Reserved – – – Note 1: The reset value of this register depends on the level of the external interrupt source. All other sources are cleared at reset, thus not pending. 2: PID2...PID127 bit fields refer to the identifiers as defined in Section 11.2 “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 235 SAMA5D2 SERIES 21.9.1 AIC Source Select Register Name: AIC_SSR Address: 0xFC020000 (AIC), 0xF803C000 (SAIC) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 5 4 3 INTSEL 2 1 0 INTSEL: Interrupt Line Selection 0–127 = Selects the interrupt line to handle. See Section 21.8.1.1 “Interrupt Source Mode”. DS60001476B-page 236  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.2 AIC Source Mode Register Name: AIC_SMR Address: 0xFC020004 (AIC), 0xF803C004 (SAIC) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 5 4 – 3 – 2 1 PRIOR 0 SRCTYPE This register can only be written if the WPEN bit is cleared in the AIC Write Protection Mode Register. PRIOR: Priority Level Programs the priority level of the source selected by INTSEL except FIQ source (source 0). The priority level can be between 0 (lowest) and 7 (highest). The priority level is not used for the FIQ. SRCTYPE: Interrupt Source Type The active level or edge is not programmable for the internal interrupt source selected by INTSEL. Value Name 0 INT_LEVEL_SENSITIVE 1 EXT_NEGATIVE_EDGE 2 EXT_HIGH_LEVEL 3 EXT_POSITIVE_EDGE  2017 Microchip Technology Inc. Description High-level sensitive for internal source Low-level sensitive for external source Negative-edge triggered for external source High-level sensitive for internal source High-level sensitive for external source Positive-edge triggered for external source DS60001476B-page 237 SAMA5D2 SERIES 21.9.3 AIC Source Vector Register Name: AIC_SVR Address: 0xFC020008 (AIC), 0xF803C008 (SAIC) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VECTOR 23 22 21 20 VECTOR 15 14 13 12 VECTOR 7 6 5 4 VECTOR This register can only be written if the WPEN bit is cleared in the AIC Write Protection Mode Register. VECTOR: Source Vector The user may store in this register the address of the corresponding handler for the interrupt source selected by INTSEL. DS60001476B-page 238  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.4 AIC Interrupt Vector Register Name: AIC_IVR Address: 0xFC020010 (AIC), 0xF803C010 (SAIC) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IRQV 23 22 21 20 IRQV 15 14 13 12 IRQV 7 6 5 4 IRQV IRQV: Interrupt Vector Register The Interrupt Vector Register contains the vector programmed by the user in the Source Vector Register corresponding to the current interrupt. The Source Vector Register is indexed using the current interrupt number when the Interrupt Vector Register is read. When there is no current interrupt, the Interrupt Vector Register reads the value stored in AIC_SPU.  2017 Microchip Technology Inc. DS60001476B-page 239 SAMA5D2 SERIES 21.9.5 AIC FIQ Vector Register Name: AIC_FVR Address: 0xFC020014 (AIC), 0xF803C014 (SAIC) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 FIQV 23 22 21 20 FIQV 15 14 13 12 FIQV 7 6 5 4 FIQV FIQV: FIQ Vector Register The FIQ Vector Register contains the vector programmed by the user in the Source Vector Register when INTSEL = 0. When there is no fast interrupt, the FIQ Vector Register reads the value stored in AIC_SPU. DS60001476B-page 240  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.6 AIC Interrupt Status Register Name: AIC_ISR Address: 0xFC020018 (AIC), 0xF803C018 (SAIC) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 5 4 3 IRQID 2 1 0 IRQID: Current Interrupt Identifier The Interrupt Status Register returns the current interrupt source number.  2017 Microchip Technology Inc. DS60001476B-page 241 SAMA5D2 SERIES 21.9.7 AIC Interrupt Pending Register 0 Name: AIC_IPR0 Address: 0xFC020020 (AIC), 0xF803C020 (SAIC) Access: Read-only 31 PID31 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 PID18 17 PID17 16 PID16 15 PID15 14 PID14 13 PID13 12 PID12 11 PID11 10 PID10 9 PID9 8 PID8 7 PID7 6 PID6 5 PID5 4 PID4 3 PID3 2 PID2 1 PID1 0 FIQ FIQ: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending. PIDx: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending. DS60001476B-page 242  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.8 AIC Interrupt Pending Register 1 Name: AIC_IPR1 Address: 0xFC020024 (AIC), 0xF803C024 (SAIC) Access: Read-only 31 PID63 30 PID62 29 PID61 28 PID60 27 PID59 26 PID58 25 PID57 24 PID56 23 PID55 22 PID54 21 PID53 20 PID52 19 PID51 18 PID50 17 PID49 16 PID48 15 PID47 14 PID46 13 PID45 12 PID44 11 PID43 10 PID42 9 PID41 8 PID40 7 PID39 6 PID38 5 PID37 4 PID36 3 PID35 2 PID34 1 PID33 0 PID32 PIDx: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending.  2017 Microchip Technology Inc. DS60001476B-page 243 SAMA5D2 SERIES 21.9.9 AIC Interrupt Pending Register 2 Name: AIC_IPR2 Address: 0xFC020028 (AIC), 0xF803C028 (SAIC) Access: Read-only 31 PID95 30 PID94 29 PID93 28 PID92 27 PID91 26 PID90 25 PID89 24 PID88 23 PID87 22 PID86 21 PID85 20 PID84 19 PID83 18 PID82 17 PID81 16 PID80 15 PID79 14 PID78 13 PID77 12 PID76 11 PID75 10 SYS 9 PID73 8 PID72 7 PID71 6 PID70 5 PID69 4 PID68 3 PID67 2 PID66 1 PID65 0 PID64 PIDx: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending. SYS: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending. DS60001476B-page 244  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.10 AIC Interrupt Pending Register 3 Name: AIC_IPR3 Address: 0xFC02002C (AIC), 0xF803C02C (SAIC) Access: Read-only 31 PID127 30 PID126 29 PID125 28 PID124 27 PID123 26 PID122 25 PID121 24 PID120 23 PID119 22 PID118 21 PID117 20 PID116 19 PID115 18 PID114 17 PID113 16 PID112 15 PID111 14 PID110 13 PID109 12 PID108 11 PID107 10 PID106 9 PID105 8 PID104 7 PID103 6 PID102 5 PID101 4 PID100 3 PID99 2 PID98 1 PID97 0 PID96 PIDx: Interrupt Pending 0: The corresponding interrupt is not pending. 1: The corresponding interrupt is pending.  2017 Microchip Technology Inc. DS60001476B-page 245 SAMA5D2 SERIES 21.9.11 AIC Interrupt Mask Register Name: AIC_IMR Address: 0xFC020030 (AIC), 0xF803C030 (SAIC) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 INTM INTM: Interrupt Mask 0: The interrupt source selected by INTSEL is disabled. 1: The interrupt source selected by INTSEL is enabled. DS60001476B-page 246  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.12 AIC Core Interrupt Status Register Name: AIC_CISR Address: 0xFC020034 (AIC), 0xF803C034 (SAIC) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 NIRQ 0 NFIQ NFIQ: NFIQ Status 0: nFIQ line is deactivated. 1: nFIQ line is active. NIRQ: NIRQ Status 0: nIRQ line is deactivated. 1: nIRQ line is active.  2017 Microchip Technology Inc. DS60001476B-page 247 SAMA5D2 SERIES 21.9.13 AIC End of Interrupt Command Register Name: AIC_EOICR Address: 0xFC020038 (AIC), 0xF803C038 (SAIC) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 ENDIT ENDIT: Interrupt Processing Complete Command The End of Interrupt Command Register is used by the interrupt routine to indicate that the interrupt treatment is complete. Any value can be written because it is only necessary to make a write to this register location to signal the end of interrupt treatment. DS60001476B-page 248  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.14 AIC Spurious Interrupt Vector Register Name: AIC_SPU Address: 0xFC02003C (AIC), 0xF803C03C (SAIC) Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 SIVR 23 22 21 20 SIVR 15 14 13 12 SIVR 7 6 5 4 SIVR This register can only be written if the WPEN bit is cleared in the AIC Write Protection Mode Register. SIVR: Spurious Interrupt Vector Register The user may store the address of a spurious interrupt handler in this register. The written value is returned in AIC_IVR in case of a spurious interrupt, or in AIC_FVR in case of a spurious fast interrupt.  2017 Microchip Technology Inc. DS60001476B-page 249 SAMA5D2 SERIES 21.9.15 AIC Interrupt Enable Command Register Name: AIC_IECR Address: 0xFC020040 (AIC), 0xF803C040 (SAIC) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 INTEN INTEN: Interrupt Enable 0: No effect. 1: Enables the interrupt source selected by INTSEL. DS60001476B-page 250  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.16 AIC Interrupt Disable Command Register Name: AIC_IDCR Address: 0xFC020044 (AIC), 0xF803C044 (SAIC) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 INTD INTD: Interrupt Disable 0: No effect. 1: Disables the interrupt source selected by INTSEL.  2017 Microchip Technology Inc. DS60001476B-page 251 SAMA5D2 SERIES 21.9.17 AIC Interrupt Clear Command Register Name: AIC_ICCR Address: 0xFC020048 (AIC), 0xF803C048 (SAIC) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 INTCLR INTCLR: Interrupt Clear Clears one the following depending on the setting of the INTSEL bit FIQ, SYS, PID2-PID73 and PID75-PID127 0: No effect. 1: Clears the interrupt source selected by INTSEL. DS60001476B-page 252  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.18 AIC Interrupt Set Command Register Name: AIC_ISCR Address: 0xFC02004C (AIC), 0xF803C04C (SAIC) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 INTSET INTSET: Interrupt Set 0: No effect. 1: Sets the interrupt source selected by INTSEL.  2017 Microchip Technology Inc. DS60001476B-page 253 SAMA5D2 SERIES 21.9.19 AIC Debug Control Register Name: AIC_DCR Address: 0xFC02006C (AIC), 0xF803C06C (SAIC) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 GMSK 0 PROT This register can only be written if the WPEN bit is cleared in the AIC Write Protection Mode Register. PROT: Protection Mode 0: The Protection mode is disabled. 1: The Protection mode is enabled. GMSK: General Interrupt Mask 0: The nIRQ and nFIQ lines are normally controlled by the AIC. 1: The nIRQ and nFIQ lines are tied to their inactive state. DS60001476B-page 254  2017 Microchip Technology Inc. SAMA5D2 SERIES 21.9.20 AIC Write Protection Mode Register Name: AIC_WPMR Address: 0xFC0200E4 (AIC), 0xF803C0E4 (SAIC) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x414943 (“AIC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x414943 (“AIC” in ASCII). See Section 21.8.8 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value 0x414943 Name PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0. DS60001476B-page 255 SAMA5D2 SERIES 21.9.21 AIC Write Protection Status Register Name: AIC_WPSR Address: 0xFC0200E8 (AIC), 0xF803C0E8 (SAIC) Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of AIC_WPSR. 1: A write protection violation has occurred since the last read of AIC_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 256  2017 Microchip Technology Inc. SAMA5D2 SERIES 22. Watchdog Timer (WDT) 22.1 Description The Watchdog Timer (WDT) is used to prevent system lock-up if the software becomes trapped in a deadlock. It features a 12-bit down counter that allows a watchdog period of up to 16 seconds (slow clock around 32 kHz). It can generate a general reset or a processor reset only. In addition, it can be stopped while the processor is in Debug mode or Sleep mode (Idle mode). 22.2 • • • • Embedded Characteristics 12-bit Key-protected Programmable Counter Watchdog Clock is Independent from Processor Clock Provides Reset or Interrupt Signals to the System Counter May Be Stopped while the Processor is in Debug State or in Idle Mode 22.3 Block Diagram Figure 22-1: Watchdog Timer Block Diagram write WDT_MR WDT_MR WDV WDT_CR WDRSTT reload 1 0 12-bit Down Counter WDT_MR WDD reload Current Value 1/128 SLCK 0 WKUPTx=0 Edge detect + debounce time PIOBUx Edge detect + debounce time VROFF=1 VROFF=1 System Active BACKUP Active BACKUP active runtime Active active runtime BACKUP check PIOBUx status check PIOBUx status DS60001476B-page 276  2017 Microchip Technology Inc. SAMA5D2 SERIES The Shutdown Controller can be programmed so as to activate the wakeup using the RTC alarm, RXLP event, ACC comparison event, security module event (detection of the rising edge event is synchronized with SLCK). This is done by writing the SHDW_MR using the RTCWKEN bit, RXLPWKEN bit and ACCWKEN bit. When enabled, the detection of RTC alarm, RXLP event, ACC comparison event, security module event is reported in the RTCWK bit, RXLPWK and ACCWK bits of SHDW_SR. They are cleared after reading SHDW_SR. When using the RTC alarm to wake up the system, the user must ensure that RTC alarm, RXLPWK and ACCWK status flags are cleared before shutting down the system. Otherwise, no rising edge of the status flags may be detected and the wakeup will fail.  2017 Microchip Technology Inc. DS60001476B-page 277 SAMA5D2 SERIES 24.7 Shutdown Controller (SHDWC) User Interface Table 24-2: Register Mapping Offset Register Name Access Reset 0x00 Shutdown Control Register SHDW_CR Write-only – 0x04 Shutdown Mode Register SHDW_MR Read/Write 0x0000_0000 0x08 Shutdown Status Register SHDW_SR Read-only 0x0000_0000 0x0C Shutdown Wakeup Inputs Register SHDW_WUIR Read/Write 0x0000_0000 DS60001476B-page 278  2017 Microchip Technology Inc. SAMA5D2 SERIES 24.7.1 Shutdown Control Register Name: SHDW_CR Address: 0xF8048010 Access: Write-only 31 30 29 28 27 26 25 24 KEY 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 SHDW SHDW: Shutdown Command 0: No effect. 1: If KEY value is correct, asserts the SHDN pin. KEY: Password Value Name Description 0xA5 PASSWD Writing any other value in this field aborts the write operation.  2017 Microchip Technology Inc. DS60001476B-page 279 SAMA5D2 SERIES 24.7.2 Shutdown Mode Register Name: SHDW_MR Address: 0xF8048014 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 25 WKUPDBC 24 23 – 22 – 21 – 20 – 19 RXLPWKEN 18 ACCWKEN 17 RTCWKEN 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – RTCWKEN: Real-time Clock Wakeup Enable 0: The RTC Alarm signal has no effect on the Shutdown Controller. 1: The RTC Alarm signal forces the deassertion of the SHDN pin. ACCWKEN: Analog Comparator Controller Wakeup Enable 0: The Analog comparator alarm signal has no effect on the Shutdown Controller. 1: The Analog comparator alarm signal forces the deassertion of the SHDN pin. RXLPWKEN: Debug Unit Wakeup Enable 0: The Backup RX UART Comparison event has no effect on the Shutdown Controller. 1: The Backup RX UART Comparison event forces the deassertion of the SHDN pin. WKUPDBC: Wakeup Inputs Debouncer Period Value Name Description 0 IMMEDIATE Immediate, no debouncing, detected active at least on one Slow Clock edge 1 3_SLCK PIOBUx shall be in its active state for at least 3 SLCK periods 2 32_SLCK PIOBUx shall be in its active state for at least 32 SLCK periods 3 512_SLCK PIOBUx shall be in its active state for at least 512 SLCK periods 4 4096_SLCK PIOBUx shall be in its active state for at least 4,096 SLCK periods 5 32768_SLCK PIOBUx shall be in its active state for at least 32,768 SLCK periods DS60001476B-page 280  2017 Microchip Technology Inc. SAMA5D2 SERIES 24.7.3 Shutdown Status Register Name: SHDW_SR Address: 0xF8048018 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 WKUPIS9 24 WKUPIS8 23 WKUPIS7 22 WKUPIS6 21 WKUPIS5 20 WKUPIS4 19 WKUPIS3 18 WKUPIS2 17 WKUPIS1 16 WKUPIS0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 RXLPWK 6 ACCWK 5 RTCWK 4 – 3 – 2 – 1 – 0 WKUPS WKUPS: PIOBU, WKUP Wakeup Status 0 (NO): No wakeup due to the assertion of the PIOBU, WKUP pins has occurred since the last read of SHDW_SR. 1 (PRESENT): At least one wakeup due to the assertion of the PIOBU, WKUP pins has occurred since the last read of SHDW_SR. Note: WKUPIS1 reports the status of the Security Module event. ACCWK: Analog Comparator Controller Wakeup 0: No wakeup alarm from the ACC occurred since the last read of SHDW_SR. 1: At least one wakeup alarm from the ACC occurred since the last read of SHDW_SR. RXLPWK: Debug Unit Wakeup 0: No wakeup alarm from the Backup RX UART Comparison unit (RXLP) occurred since the last read of SHDW_SR. 1: At least one wakeup alarm from the Backup RX UART Comparison unit (RXLP) occurred since the last read of SHDW_SR. WKUPIS0–WKUPIS9: Wakeup 0 to 9 Input Status 0 (DISABLE): The corresponding wakeup input is disabled, or was inactive at the time the debouncer triggered a wakeup event. 1 (ENABLE): The corresponding wakeup input was active at the time the debouncer triggered a wakeup event.  2017 Microchip Technology Inc. DS60001476B-page 281 SAMA5D2 SERIES 24.7.4 Shutdown Wakeup Inputs Register Name: SHDW_WUIR Address: 0xF804801C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 WKUPT9 24 WKUPT8 23 WKUPT7 22 WKUPT6 21 WKUPT5 20 WKUPT4 19 WKUPT3 18 WKUPT2 17 WKUPT1 16 WKUPT0 15 – 14 – 13 – 12 – 11 – 10 – 9 WKUPEN9 8 WKUPEN8 7 WKUPEN7 6 WKUPEN6 5 WKUPEN5 4 WKUPEN4 3 WKUPEN3 2 WKUPEN2 1 WKUPEN1 0 WKUPEN0 WKUPEN0–WKUPEN9: Wakeup 0 to 9 Input Enable 0 (DISABLE): The corresponding wakeup input has no wakeup effect. 1 (ENABLE): The corresponding wakeup input forces the wakeup of the core power supply. WKUPT0–WKUPT9: Wakeup 0 to 9 Input Type 0 (LOW): A falling edge followed by a low level, for a period defined by WKUPDBC, on the corresponding wakeup input forces the wakeup of the core power supply. 1 (HIGH): A rising edge followed by a high level, for a period defined by WKUPDBC, on the corresponding wakeup input forces the wakeup of the core power supply. DS60001476B-page 282  2017 Microchip Technology Inc. SAMA5D2 SERIES 25. Periodic Interval Timer (PIT) 25.1 Description The Periodic Interval Timer (PIT) provides the operating system’s scheduler interrupt. It is designed to offer maximum accuracy and efficient management, even for systems with long response time. 25.2 Embedded Characteristics • 20-bit Programmable Counter plus 12-bit Interval Counter • Reset-on-read Feature • Both Counters Work on Master Clock/16 25.3 Block Diagram Figure 25-1: Periodic Interval Timer PIT_MR PIV = PIT_MR PITIEN set 0 PIT_SR pit_irq PITS reset 0 MCK Prescaler 0 0 1 12-bit Adder 1 read PIT_PIVR 20-bit Counter MCK/16  2017 Microchip Technology Inc. CPIV PIT_PIVR CPIV PIT_PIIR PICNT PICNT DS60001476B-page 283 SAMA5D2 SERIES 25.4 Functional Description The Periodic Interval Timer aims at providing periodic interrupts for use by operating systems. The PIT provides a programmable overflow counter and a reset-on-read feature. It is built around two counters: a 20-bit CPIV counter and a 12-bit PICNT counter. Both counters work at Master Clock /16. The first 20-bit CPIV counter increments from 0 up to a programmable overflow value set in the field PIV of the Mode Register (PIT_MR). When the counter CPIV reaches this value, it resets to 0 and increments the Periodic Interval Counter, PICNT. The status bit PITS in the Status Register (PIT_SR) rises and triggers an interrupt, provided the interrupt is enabled (PITIEN in PIT_MR). Writing a new PIV value in PIT_MR does not reset/restart the counters. When CPIV and PICNT values are obtained by reading the Periodic Interval Value Register (PIT_PIVR), the overflow counter (PICNT) is reset and the PITS bit is cleared, thus acknowledging the interrupt. The value of PICNT gives the number of periodic intervals elapsed since the last read of PIT_PIVR. When CPIV and PICNT values are obtained by reading the Periodic Interval Image Register (PIT_PIIR), there is no effect on the counters CPIV and PICNT, nor on the bit PITS. For example, a profiler can read PIT_PIIR without clearing any pending interrupt, whereas a timer interrupt clears the interrupt by reading PIT_PIVR. The PIT may be enabled/disabled using the PITEN bit in the PIT_MR register (disabled on reset). The PITEN bit only becomes effective when the CPIV value is 0. Figure 25-2 illustrates the PIT counting. After the PIT Enable bit is reset (PITEN = 0), the CPIV goes on counting until the PIV value is reached, and is then reset. PIT restarts counting, only if the PITEN is set again. The PIT is stopped when the core enters debug state. Figure 25-2: Enabling/Disabling PIT with PITEN APB cycle APB cycle MCK 15 restarts MCK Prescaler MCK Prescaler 0 PITEN CPIV PICNT 0 1 PIV - 1 0 PIV 1 0 1 0 PITS (PIT_SR) APB Interface read PIT_PIVR DS60001476B-page 284  2017 Microchip Technology Inc. SAMA5D2 SERIES 25.5 Periodic Interval Timer (PIT) User Interface Table 25-1: Register Mapping Offset Register Name Access Reset 0x00 Mode Register PIT_MR Read/Write 0x000F_FFFF 0x04 Status Register PIT_SR Read-only 0x0000_0000 0x08 Periodic Interval Value Register PIT_PIVR Read-only 0x0000_0000 0x0C Periodic Interval Image Register PIT_PIIR Read-only 0x0000_0000  2017 Microchip Technology Inc. DS60001476B-page 285 SAMA5D2 SERIES 25.5.1 PIT Mode Register Name: PIT_MR Address: 0xF8048030 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 PITIEN 24 PITEN 23 – 22 – 21 – 20 – 19 18 17 16 15 14 13 12 11 10 9 8 3 2 1 0 PIV PIV 7 6 5 4 PIV PIV: Periodic Interval Value Defines the value compared with the primary 20-bit counter of the Periodic Interval Timer (CPIV). The period is equal to (PIV + 1). PITEN: Period Interval Timer Enabled 0: The Periodic Interval Timer is disabled when the PIV value is reached. 1: The Periodic Interval Timer is enabled. PITIEN: Periodic Interval Timer Interrupt Enable 0: The bit PITS in PIT_SR has no effect on interrupt. 1: The bit PITS in PIT_SR asserts interrupt. DS60001476B-page 286  2017 Microchip Technology Inc. SAMA5D2 SERIES 25.5.2 PIT Status Register Name: PIT_SR Address: 0xF8048034 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 PITS PITS: Periodic Interval Timer Status 0: The Periodic Interval timer has not reached PIV since the last read of PIT_PIVR. 1: The Periodic Interval timer has reached PIV since the last read of PIT_PIVR.  2017 Microchip Technology Inc. DS60001476B-page 287 SAMA5D2 SERIES 25.5.3 PIT Value Register Name: PIT_PIVR Address: 0xF8048038 Access: Read-only 31 30 29 28 27 26 19 18 25 24 17 16 PICNT 23 22 21 20 PICNT 15 14 CPIV 13 12 11 10 9 8 3 2 1 0 CPIV 7 6 5 4 CPIV Reading this register clears PITS in PIT_SR. CPIV: Current Periodic Interval Value Returns the current value of the periodic interval timer. PICNT: Periodic Interval Counter Returns the number of occurrences of periodic intervals since the last read of PIT_PIVR. DS60001476B-page 288  2017 Microchip Technology Inc. SAMA5D2 SERIES 25.5.4 PIT Image Register Name: PIT_PIIR Address: 0xF804803C Access: 31 Read-only 30 29 28 27 26 19 18 25 24 17 16 PICNT 23 22 21 20 PICNT 15 14 CPIV 13 12 11 10 9 8 3 2 1 0 CPIV 7 6 5 4 CPIV CPIV: Current Periodic Interval Value Returns the current value of the periodic interval timer. PICNT: Periodic Interval Counter Returns the number of occurrences of periodic intervals since the last read of PIT_PIVR.  2017 Microchip Technology Inc. DS60001476B-page 289 SAMA5D2 SERIES 26. Real-time Clock (RTC) 26.1 Description The Real-time Clock (RTC) peripheral is designed for very low power consumption. For optimal functionality, the RTC requires an accurate external 32.768 kHz clock, which can be provided by a crystal oscillator. It combines a complete time-of-day clock with alarm and a Gregorian or Persian calendar, complemented by a programmable periodic interrupt. The alarm and calendar registers are accessed by a 32-bit data bus. The RTC can also be configured for the UTC time format. The time and calendar values are coded in binary-coded decimal (BCD) format. The time format can be 24-hour mode or 12-hour mode with an AM/PM indicator. Updating time and calendar fields and configuring the alarm fields are performed by a parallel capture on the 32-bit data bus. An entry control is performed to avoid loading registers with incompatible BCD format data or with an incompatible date according to the current month/year/century. A clock divider calibration circuitry can be used to compensate for crystal oscillator frequency variations. Timestamping capability reports the first and last occurrences of tamper events. 26.2 • • • • • • • • Embedded Characteristics Full Asynchronous Design for Ultra Low Power Consumption Gregorian, UTC and Persian Modes Supported Programmable Periodic Interrupt Safety/security Features: - Valid Time and Date Programming Check - On-The-Fly Time and Date Validity Check Counters Calibration Circuitry to Compensate for Crystal Oscillator Variations Waveform Generation for Trigger Event Tamper Timestamping Registers Register Write Protection 26.3 Block Diagram Figure 26-1: Slow Clock SLCK Real-time Clock Block Diagram 32768 Divider Time Wave Generator Date Clock Calibration System Bus DS60001476B-page 290 User Interface Entry Control Alarm Interrupt Control RTCOUT0 (ADC AD[n:0] trigger) RTCOUT1 (ADC AD[n] trigger) Where n is the higher index available (last channel) RTC Interrupt  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.4 26.4.1 Product Dependencies Power Management The Real-time Clock is continuously clocked at 32.768 kHz. The Power Management Controller has no effect on RTC behavior. 26.4.2 Interrupt Within the System Controller, the RTC interrupt is OR-wired with all the other module interrupts. Only one System Controller interrupt line is connected on one of the internal sources of the interrupt controller. RTC interrupt requires the interrupt controller to be programmed first. When a System Controller interrupt occurs, the service routine must first determine the cause of the interrupt. This is done by reading each status register of the System Controller peripherals successively. 26.5 Functional Description The RTC provides a full binary-coded decimal (BCD) clock that includes century (19/20), year (with leap years), month, date, day, hours, minutes and seconds reported in RTC Time Register (RTC_TIMR) and RTC Time Register (UTC_MODE) (RTC_CALR). The RTC can operate in UTC mode, giving the number of seconds elapsed since a reference time defined by the user (the UTC standard— ISO 8601—reference time is the 30th of June 1972). In this mode, the timefield is 32-bit wide and coded in hexadecimal format. The valid year range is up to 2099 in Gregorian mode (or 1300 to 1499 in Persian mode). The RTC can operate in 24-hour mode or in 12-hour mode with an AM/PM indicator. Corrections for leap years are included (all years divisible by 4 being leap years except 1900). This is correct up to the year 2099. The RTC can generate events to trigger ADC measurements. 26.5.1 Reference Clock The reference clock is the Slow Clock (SLCK). It can be driven internally or by an external 32.768 kHz crystal. During low power modes of the processor, the oscillator runs and power consumption is critical. The crystal selection has to take into account the current consumption for power saving and the frequency drift due to temperature effect on the circuit for time accuracy. 26.5.2 Timing In Gregorian and Persian modes, the RTC is updated in real time at one-second intervals in Normal mode for the counters of seconds, at one-minute intervals for the counter of minutes and so on. In UTC mode, the RTC is updated in real time at one-second intervals (32-bit UTC counter default configuration). Due to the asynchronous operation of the RTC with respect to the rest of the chip, to be certain that the value read in the RTC registers (century, year, month, date, day, hours, minutes, seconds) are valid and stable, it is necessary to read these registers twice. If the data is the same both times, then it is valid. Therefore, a minimum of two and a maximum of three accesses are required. 26.5.3 Alarm In Gregorian and Persian modes, the RTC has five programmable fields: month, date, hours, minutes and seconds. Each of these fields can be enabled or disabled to match the alarm condition: • If all the fields are enabled, an alarm flag is generated (the corresponding flag is asserted and an interrupt generated if enabled) at a given month, date, hour/minute/second. • If only the “seconds” field is enabled, then an alarm is generated every minute. Depending on the combination of fields enabled, a large number of possibilities are available to the user ranging from minutes to 365/366 days. Hour, minute and second matching alarm (SECEN, MINEN, HOUREN) can be enabled independently of SEC, MIN, HOUR fields. Note: To change one of the SEC, MIN, HOUR, DATE, MONTH fields, it is recommended to disable the field before changing the value and then re-enable it after the change has been made. This requires up to three accesses to the RTC_TIMALR or RTC_CALALR. The first access clears the enable corresponding to the field to change (SECEN, MINEN, HOUREN, DATEEN, MTHEN). If the field is already cleared, this access is not required. The second access performs the change of the value (SEC, MIN, HOUR, DATE, MONTH). The third access is required to re-enable the field by writing 1 in SECEN, MINEN, HOUREn, DATEEN, MTHEN fields.  2017 Microchip Technology Inc. DS60001476B-page 291 SAMA5D2 SERIES In UTC mode, RTC_TIMALR must be configured to set the UTC alarm value and bit 0 in RTC_CALALR must be used to enable or disable the UTC alarm. If the UTC alarm is enabled, the alarm is generated once the UTC time matches the programmed UTC_TIME alarm field. To change the UTC_TIME alarm field, proceed as follows: 1. 2. 3. Disable the UTC alarm by clearing the UTCEN bit in RTC_CALALR if it is not already cleared. Change the UTC_TIME alarm value in RTC_TIMALR. Re-enable the UTC alarm by setting the UTCEN bit in RTC_CALALR. 26.5.4 Error Checking when Programming Verification on user interface data is performed when accessing the century, year, month, date, day, hours, minutes, seconds and alarms. A check is performed on illegal BCD entries such as illegal date of the month with regard to the year and century configured. If one of the time fields is not correct, the data is not loaded into the register/counter and a flag is set in the validity register. The user can not reset this flag. It is reset as soon as an acceptable value is programmed. This avoids any further side effects in the hardware. The same procedure is followed for the alarm. The following checks are performed: 1. 2. 3. 4. 5. 6. 7. 8. Century (check if it is in range 19–20 or 13–14 in Persian mode) Year (BCD entry check) Date (check range 01–31) Month (check if it is in BCD range 01–12, check validity regarding “date”) Day (check range 1–7) Hour (BCD checks: in 24-hour mode, check range 00–23 and check that AM/PM flag is not set if RTC is set in 24-hour mode; in 12-hour mode check range 01–12) Minute (check BCD and range 00–59) Second (check BCD and range 00–59) Note: If the 12-hour mode is selected by means of the RTC Mode Register (RTC_MR), a 12-hour value can be programmed and the returned value on RTC_TIMR will be the corresponding 24-hour value. The entry control checks the value of the AM/PM indicator (bit 22 of RTC_TIMR) to determine the range to be checked. Note: In UTC mode, no check is performed on the entries. The RTC does not report any failure. 26.5.5 RTC Internal Free Running Counter Error Checking To improve the reliability and security of the RTC, a permanent check is performed on the internal free running counters to report nonBCD or invalid date/time values. An error is reported by TDERR bit in the status register (RTC_SR) if an incorrect value has been detected. The flag can be cleared by setting the TDERRCLR bit in the Status Clear Command Register (RTC_SCCR). Anyway the TDERR error flag will be set again if the source of the error has not been cleared before clearing the TDERR flag. The clearing of the source of such error can be done by reprogramming a correct value on RTC_CALR and/or RTC_TIMR. The RTC internal free running counters may automatically clear the source of TDERR due to their roll-over (i.e., every 10 seconds for SECONDS[3:0] field in RTC_TIMR). In this case the TDERR is held high until a clear command is asserted by TDERRCLR bit in RTC_SCCR. 26.5.6 26.5.6.1 Updating Time/Calendar Gregorian and Persian Modes The update of the time/calendar must be synchronized on a second periodic event by either polling the RTC_SR.SEC status bit or by enabling the SECEN interrupt in the RTC_IER register. Once the second event occurs, the user must stop the RTC by setting the corresponding field in the Control Register (RTC_CR). Bit UPDTIM must be set to update time fields (hour, minute, second) and bit UPDCAL must be set to update calendar fields (century, year, month, date, day). The ACKUPD bit must then be read to 1 by either polling the RTC_SR or by enabling the ACKUPD interrupt in the RTC_IER. Once ACKUPD is read to 1, it is mandatory to clear this flag by writing the corresponding bit in the RTC_SCCR, after which the user can write to the Time Register, the Calendar Register, or both. Once the update is finished, the user must write UPDTIM and/or UPDCAL to 0 in the RTC_CR. The timing sequence of the time/calendar update is described in Figure 26-2 ”Time/Calendar Update Timing Diagram”. DS60001476B-page 292  2017 Microchip Technology Inc. SAMA5D2 SERIES When entering the Programming mode of the calendar fields, the time fields remain enabled. When entering the Programming mode of the time fields, both the time and the calendar fields are stopped. This is due to the location of the calendar logical circuity (downstream for low-power considerations). It is highly recommended to prepare all the fields to be updated before entering Programming mode. In successive update operations, the user must wait for at least one second after resetting the UPDTIM/UPDCAL bit in the RTC_CR before setting these bits again. This is done by waiting for the SEC flag in the RTC_SR before setting the UPDTIM/UPDCAL bit. After resetting UPDTIM/UPDCAL, the SEC flag must also be cleared. Figure 26-2: Time/Calendar Update Timing Diagram // 1Hz RTC Clock RTC_TIMR.SEC Software Time Line // 20 Update request from SW 1 Clear ACKUPD bit 2 // // // // 15 (counter stopped) 16 Clear UPDTIM bit 3 RTC BACK TO NORMAL MODE 4 Update RTC_TIMR.SEC to 15 RTC_CR.UPDTIM SEC Event Flag RTC_SR.ACKUPD  2017 Microchip Technology Inc. // // // // // // DS60001476B-page 293 SAMA5D2 SERIES Figure 26-3: Gregorian and Persian Modes Update Sequence Begin Prepare Time or Calendar Fields Wait for second periodic event Set RTC_CR.UPDTIM and/or RTC_CR.UPDCAL Read RTC_SR Polling or IRQ (if enabled) ACKUPD = 1? No Yes Clear RTC_SR.ACKUPD by writing a ‘1’ to RTC_SCCR.ACKCLR Update Time and/or Calendar values in RTC_TIMR/RTC_CALR Clear RTC_CR.UPDTIM and/or RTC_CR.UPDCAL End DS60001476B-page 294  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.5.6.2 UTC Mode The update of the UTC time field must be synchronized on a second periodic event by either polling the RTC_SR.SEC status bit or by enabling the SECEN interrupt in the RTC_IER. Once the second event occurs, the user must stop the RTC by setting the UPDTIM field in the Control Register (RTC_CR). The ACKUPD bit must then be read to 1 by either polling the RTC_SR or by enabling the ACKUPD interrupt in the RTC_IER. Once ACKUPD is read to 1, it is mandatory to clear this flag by writing the corresponding bit in the RTC_SCCR, after which the user can write to the Time Register. Once the update is finished, the user must write UPDTIM to 0 in the RTC_CR. The timing sequence of the UTC time update is described in Figure 26-4 ”UTC Time Update Timing Diagram”. In successive update operations, the user must wait for at least one second after resetting the UPDTIM bit in the RTC_CR before setting this bit again. This is done by waiting for the SEC flag in the RTC_SR before setting UPDTIM bit. After resetting UPDTIM, the SEC flag must also be cleared. Figure 26-4: UTC Time Update Timing Diagram General Time Update // 1Hz RTC Clock RTC_TIMR.UTC_TIME Software Time Line // 20 Update request from SW 1 Clear ACKUPD bit 2 // // // // 15 (counter stopped) 16 Clear UPDTIM bit 3 RTC BACK TO NORMAL MODE 4 Update RTC_TIMR.SEC to 15 RTC_CR.UPDTIM SEC Event Flag RTC_SR.ACKUPD  2017 Microchip Technology Inc. // // // // // // DS60001476B-page 295 SAMA5D2 SERIES Figure 26-5: UTC Mode Update Sequence Begin Prepare Time Field Wait for second periodic event Set RTC_CR.UPDTIM Read RTC_SR Polling or IRQ (if enabled) ACKUPD = 1? No Yes Clear RTC_SR.ACKUPD by writing a ‘1’ to RTC_SCCR.ACKCLR Update Time value in RTC_TIMR Clear RTC_CR.UPDTIM End DS60001476B-page 296  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.5.7 RTC Accurate Clock Calibration The crystal oscillator that drives the RTC may not be as accurate as expected mainly due to temperature variation. The RTC is equipped with circuitry able to correct slow clock crystal drift. To compensate for possible temperature variations over time, this accurate clock calibration circuitry can be programmed on-the-fly and also programmed during application manufacturing, in order to correct the crystal frequency accuracy at room temperature (20–25°C). The typical clock drift range at room temperature is ±20 ppm. In the device operating temperature range, the 32.768 kHz crystal oscillator clock inaccuracy can be up to -200 ppm. The RTC clock calibration circuitry allows positive or negative correction in a range of 1.5 ppm to 1950 ppm. The calibration circuitry is fully digital. Thus, the configured correction is independent of temperature, voltage, process, etc., and no additional measurement is required to check that the correction is effective. If the correction value configured in the calibration circuitry results from an accurate crystal frequency measure, the remaining accuracy is bounded by the values listed below: • Below 1 ppm, for an initial crystal drift between 1.5 ppm up to 20 ppm, and from 30 ppm to 90 ppm • Below 2 ppm, for an initial crystal drift between 20 ppm up to 30 ppm, and from 90 ppm to 130 ppm • Below 5 ppm, for an initial crystal drift between 130 ppm up to 200 ppm The calibration circuitry does not modify the 32.768 kHz crystal oscillator clock frequency but it acts by slightly modifying the 1 Hz clock period from time to time. The correction event occurs every 1 + [(20 - (19 x HIGHPPM)) x CORRECTION] seconds. When the period is modified, depending on the sign of the correction, the 1 Hz clock period increases or reduces by around 4 ms. Depending on the CORRECTION, NEGPPM and HIGHPPM values configured in RTC_MR, the period interval between two correction events differs. Figure 26-6: Calibration Circuitry RTC Divider by 32768 32.768 kHz Oscillator Add 32.768 kHz 1Hz Time/Calendar Suppress Integrator Comparator CORRECTION, HIGHPPM NEGPPM Other Logic  2017 Microchip Technology Inc. DS60001476B-page 297 SAMA5D2 SERIES Figure 26-7: Calibration Circuitry Waveforms Monotonic 1 Hz Counter value 32.768 kHz +50 ppm Phase adjustment (~4 ms) Nominal 32.768 kHz 32.768 kHz -50 ppm -25 ppm Crystal frequency remains unadjusted -50 ppm Internal 1 Hz clock is adjusted Time User configurable period (integer multiple of 1s or 20s) Time -50 ppm correction period -25 ppm correction period NEGATIVE CORRECTION Crystal clock Internally divided clock (256 Hz) Clock pulse periodically suppressed when correction period elapses Internally divided clock (128 Hz) 1.000 second 128 Hz clock edge delayed by 3.906 ms when correction period elapses POSITIVE CORRECTION 1.003906 second Internally divided clock (256 Hz) Internally divided clock (128 Hz) Clock edge periodically added when correction period elapses Internally divided clock (64 Hz) 0.996094 second 1.000 second 128 Hz clock edge delayed by 3.906 ms when correction period elapses dashed lines = no correction The inaccuracy of a crystal oscillator at typical room temperature (±20 ppm at 20–25 °C) can be compensated if a reference clock/signal is used to measure such inaccuracy. This kind of calibration operation can be set up during the final product manufacturing by means of measurement equipment embedding such a reference clock. The correction of value must be programmed into the (RTC_MR), and this value is kept as long as the circuitry is powered (backup area). Removing the backup power supply cancels this calibration. This room temperature calibration can be further processed by means of the networking capability of the target application. In any event, this adjustment does not take into account the temperature variation. DS60001476B-page 298  2017 Microchip Technology Inc. SAMA5D2 SERIES The frequency drift (up to -200 ppm) due to temperature variation can be compensated using a reference time if the application can access such a reference. If a reference time cannot be used, a temperature sensor can be placed close to the crystal oscillator in order to get the operating temperature of the crystal oscillator. Once obtained, the temperature may be converted using a lookup table (describing the accuracy/temperature curve of the crystal oscillator used) and RTC_MR configured accordingly. The calibration can be performed on-thefly. This adjustment method is not based on a measurement of the crystal frequency/drift and therefore can be improved by means of the networking capability of the target application. If no crystal frequency adjustment has been done during manufacturing, it is still possible to do it. In the case where a reference time of the day can be obtained through LAN/WAN network, it is possible to calculate the drift of the application crystal oscillator by comparing the values read on RTC Time Register (RTC_TIMR) and programming the HIGHPPM and CORRECTION fields on RTC_MR according to the difference measured between the reference time and those of RTC_TIMR. 26.5.8 Waveform Generation Waveforms can be generated by the RTC in order to take advantage of the RTC inherent prescalers while the RTC is the only powered circuitry (Low-power mode of operation, Backup mode) or in any active mode. Going into Backup or Low-power operating modes does not affect the waveform generation outputs. The RTC waveforms are internally routed to ADC trigger events and those events have a source driver selected among five possibilities. Two different triggers can be generated at a time, the first one is configurable through field OUT0 in RTC_MR while the second trigger is configurable through field OUT1 in RTC_MR. OUT0 field manages the trigger for channel AD[n:0] (where n is the higher index available (last channel)), while OUT1 manages the channel AD[n] only for specific modes. See the ADC section for selection of the measurement triggers and associated mode of operations. The first selection choice sticks the associated output at 0 (This is the reset value and it can be used at any time to disable the waveform generation). Selection choices 1 to 4 respectively select 1 Hz, 32 Hz, 64 Hz and 512 Hz. Selection choice 6 provides a copy of the alarm flag, so the associated output is set high (logical 1) when an alarm occurs and immediately cleared when software clears the alarm interrupt source.  2017 Microchip Technology Inc. DS60001476B-page 299 SAMA5D2 SERIES Figure 26-8: Waveform Generation for ADC Trigger Event ‘0’ 0 ‘0’ 0 1 Hz 1 1 Hz 1 32 Hz 2 32 Hz 2 64 Hz 3 64 Hz 3 512 Hz 4 512 Hz 4 toggle_alarm 5 toggle_alarm 5 flag_alarm 6 flag_alarm 6 pulse 7 pulse 7 To ADC trigger event for all channels RTC_MR.OUT0 To ADC trigger event for AD[n] n = higher index available RTC_MR.OUT1 alarm match event 2 alarm match event 1 flag_alarm RTC_SCCR.ALRCLR RTC_SCCR.ALRCLR toggle_alarm pulse Thigh Tperiod 26.5.9 Tperiod Tamper Timestamping As soon as a tamper is detected, the tamper counter is incremented and the RTC stores the time of the day, the date and the source of the tamper event in registers located in the backup area. Up to two tamper events can be stored. In UTC mode, only the UTC time is stored. The date information is not relevant. The tamper counter saturates at 15. Once this limit is reached, the exact number of tamper occurrences since the last read of stamping registers cannot be known. The first set of timestamping registers (RTC_TSTR0, RTC_TSDR0, RTC_TSSR0) cannot be overwritten, so once they have been written all data are stored until the registers are reset. Therefore these registers are storing the first tamper occurrence after a read. The second set of timestamping registers (RTC_TSTR1, RTC_TSDR1, RTC_TSSR1) are overwritten each time a tamper event is detected. Thus the date and the time data of the first and the second stamping registers may be equal. This occurs when the tamper counter value carried on field TEVCNT in RTC_TSTR0 equals 1. Thus this second set of registers stores the last occurrence of tamper before a read. Reading a set of timestamping registers requires three accesses, one for the time of the day, one for the date and one for the tamper source. Reading the third part (RTC_TSSR0/1) of a timestamping register set clears the whole content of the registers (time, date and tamper source) and makes the timestamping registers available to store a new event. DS60001476B-page 300  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6 Real-time Clock (RTC) User Interface Table 26-1: Offset Register Mapping Register Name Access Reset 0x00 Control Register RTC_CR Read/Write 0x00000000 0x04 Mode Register RTC_MR Read/Write 0x00000000 0x08 Time Register RTC_TIMR Read/Write 0x00000000 0x0C Calendar Register RTC_CALR Read/Write 0x01E11220 0x10 Time Alarm Register RTC_TIMALR Read/Write 0x00000000 0x14 Calendar Alarm Register RTC_CALALR Read/Write 0x01010000 0x18 Status Register RTC_SR Read-only 0x00000000 0x1C Status Clear Command Register RTC_SCCR Write-only – 0x20 Interrupt Enable Register RTC_IER Write-only – 0x24 Interrupt Disable Register RTC_IDR Write-only – 0x28 Interrupt Mask Register RTC_IMR Read-only 0x00000000 0x2C Valid Entry Register RTC_VER Read-only 0x00000000 0xB0 TimeStamp Time Register 0 RTC_TSTR0 Read-only 0x00000000 0xB4 TimeStamp Date Register 0 RTC_TSDR0 Read-only 0x00000000 0xB8 TimeStamp Source Register 0 RTC_TSSR0 Read-only 0x00000000 0xBC TimeStamp Time Register 1 RTC_TSTR1 Read-only 0x00000000 0xC0 TimeStamp Date Register 1 RTC_TSDR1 Read-only 0x00000000 0xC4 TimeStamp Source Register 1 RTC_TSSR1 Read-only 0x00000000 0xC8 Reserved – – – 0xCC Reserved – – – 0xD0 Reserved – – – 0xD4–0xF8 Reserved – – – 0xFC Reserved – – – Note: If an offset is not listed in the table it must be considered as reserved.  2017 Microchip Technology Inc. DS60001476B-page 301 SAMA5D2 SERIES 26.6.1 RTC Control Register Name: RTC_CR Address: 0xF80480B0 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 – – – – – – 15 14 13 12 11 10 – – – – – – 16 CALEVSEL 9 8 TIMEVSEL 7 6 5 4 3 2 1 0 – – – – – – UPDCAL UPDTIM This register can only be written if the WPEN bit is cleared in the System Controller Write Protection Mode Register (SYSC_WPMR). UPDTIM: Update Request Time Register 0: No effect or, if UPDTIM has been previously written to 1, stops the update procedure. 1: Stops the RTC time counting. Time counting consists of second, minute and hour counters. Time counters can be programmed once this bit is set and acknowledged by the bit ACKUPD of the RTC_SR. UPDCAL: Update Request Calendar Register 0: No effect or, if UPDCAL has been previously written to 1, stops the update procedure. 1: Stops the RTC calendar counting. Calendar counting consists of day, date, month, year and century counters. Calendar counters can be programmed once this bit is set and acknowledged by the bit ACKUPD of the RTC_SR. Note: In UTC mode, this bit has no effect on the RTC behavior. TIMEVSEL: Time Event Selection The event that generates the flag TIMEV in RTC_SR depends on the value of TIMEVSEL. Value Name Description 0 MINUTE Minute change 1 HOUR Hour change 2 MIDNIGHT Every day at midnight 3 NOON Every day at noon Note: In UTC mode, this field has no effect on the RTC_SR. DS60001476B-page 302  2017 Microchip Technology Inc. SAMA5D2 SERIES CALEVSEL: Calendar Event Selection The event that generates the flag CALEV in RTC_SR depends on the value of CALEVSEL Value Name Description 0 WEEK Week change (every Monday at time 00:00:00) 1 MONTH Month change (every 01 of each month at time 00:00:00) 2 YEAR Year change (every January 1 at time 00:00:00) 3 – Reserved Note: In UTC mode, this field has no effect on the RTC_SR.  2017 Microchip Technology Inc. DS60001476B-page 303 SAMA5D2 SERIES 26.6.2 RTC Mode Register Name: RTC_MR Address: 0xF80480B4 Access: Read/Write 31 30 – – 23 22 – 29 28 TPERIOD 21 14 26 – 20 OUT1 15 27 19 18 – 13 12 HIGHPPM 11 25 24 THIGH 17 16 OUT0 10 9 8 CORRECTION 7 6 5 4 3 2 1 0 – – – NEGPPM – UTC PERSIAN HRMOD This register can only be written if the WPEN bit is cleared in the System Controller Write Protection Mode Register (SYSC_WPMR). HRMOD: 12-/24-hour Mode 0: 24-hour mode is selected. 1: 12-hour mode is selected. PERSIAN: PERSIAN Calendar 0: Gregorian calendar. 1: Persian calendar. UTC: UTC Time Format 0: Gregorian or Persian calendar. 1: UTC format. It is forbidden to write a one to the UTC and PERSIAN bits at the same time. NEGPPM: NEGative PPM Correction 0: Positive correction (the divider will be slightly higher than 32768). 1: Negative correction (the divider will be slightly lower than 32768). Refer to CORRECTION and HIGHPPM field descriptions. Note: NEGPPM must be cleared to correct a crystal slower than 32.768 kHz. CORRECTION: Slow Clock Correction 0: No correction 1–127: The slow clock will be corrected according to the formula given in HIGHPPM description. HIGHPPM: HIGH PPM Correction 0: Lower range ppm correction with accurate correction. 1: Higher range ppm correction with accurate correction. If the absolute value of the correction to be applied is lower than 30 ppm, it is recommended to clear HIGHPPM. HIGHPPM set to 1 is recommended for 30 ppm correction and above. Formula: If HIGHPPM = 0, then the clock frequency correction range is from 1.5 ppm up to 98 ppm. The RTC accuracy is less than 1 ppm for a range correction from 1.5 ppm up to 30 ppm. The correction field must be programmed according to the required correction in ppm; the formula is as follows: 3906 CORRECTION = ------------------------- – 1 20 × ppm DS60001476B-page 304  2017 Microchip Technology Inc. SAMA5D2 SERIES The value obtained must be rounded to the nearest integer prior to being programmed into CORRECTION field. If HIGHPPM = 1, then the clock frequency correction range is from 30.5 ppm up to 1950 ppm. The RTC accuracy is less than 1 ppm for a range correction from 30.5 ppm up to 90 ppm. The correction field must be programmed according to the required correction in ppm; the formula is as follows: 3906 CORRECTION = ------------- – 1 ppm The value obtained must be rounded to the nearest integer prior to be programmed into CORRECTION field. If NEGPPM is set to 1, the ppm correction is negative (used to correct crystals that are faster than the nominal 32.768 kHz). OUT0: All ADC Channel Trigger Event Source Selection Value Name Description 0 NO_WAVE No waveform, stuck at ‘0’ 1 FREQ1HZ 1 Hz square wave 2 FREQ32HZ 32 Hz square wave 3 FREQ64HZ 64 Hz square wave 4 FREQ512HZ 512 Hz square wave 5 ALARM_TOGGLE Output toggles when alarm flag rises 6 ALARM_FLAG Output is a copy of the alarm flag 7 PROG_PULSE Duty cycle programmable pulse OUT1: ADC Last Channel Trigger Event Source Selection Value Name Description 0 NO_WAVE No waveform, stuck at ‘0’ 1 FREQ1HZ 1 Hz square wave 2 FREQ32HZ 32 Hz square wave 3 FREQ64HZ 64 Hz square wave 4 FREQ512HZ 512 Hz square wave 5 ALARM_TOGGLE Output toggles when alarm flag rises 6 ALARM_FLAG Output is a copy of the alarm flag 7 PROG_PULSE Duty cycle programmable pulse THIGH: High Duration of the Output Pulse Value Name Description 0 H_31MS 31.2 ms 1 H_16MS 15.6 ms 2 H_4MS 3.91 ms 3 H_976US 976 µs 4 H_488US 488 µs  2017 Microchip Technology Inc. DS60001476B-page 305 SAMA5D2 SERIES Value Name Description 5 H_122US 122 µs 6 H_30US 30.5 µs 7 H_15US 15.2 µs TPERIOD: Period of the Output Pulse Value Name Description 0 P_1S 1 second 1 P_500MS 500 ms 2 P_250MS 250 ms 3 P_125MS 125 ms DS60001476B-page 306  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.3 RTC Time Register Name: RTC_TIMR Address: 0xF80480B8 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – AMPM 15 14 10 9 8 2 1 0 HOUR 13 12 – 7 11 MIN 6 5 4 – 3 SEC SEC: Current Second The range that can be set is 0–59 (BCD). The lowest four bits encode the units. The higher bits encode the tens. MIN: Current Minute The range that can be set is 0–59 (BCD). The lowest four bits encode the units. The higher bits encode the tens. HOUR: Current Hour The range that can be set is 1–12 (BCD) in 12-hour mode or 0–23 (BCD) in 24-hour mode. AMPM: Ante Meridiem Post Meridiem Indicator This bit is the AM/PM indicator in 12-hour mode. 0: AM. 1: PM.  2017 Microchip Technology Inc. DS60001476B-page 307 SAMA5D2 SERIES 26.6.4 RTC Time Register (UTC_MODE) Name: RTC_TIMR (UTC_MODE) Address: 0xF80480B8 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UTC_TIME 23 22 21 20 UTC_TIME 15 14 13 12 UTC_TIME 7 6 5 4 UTC_TIME This configuration is relevant only if UTC = 1 in RTC_MR UTC_TIME: Current UTC Time Any value can be set. DS60001476B-page 308  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.5 RTC Calendar Register Name: RTC_CALR Address: 0xF80480BC Access: Read/Write 31 30 – – 23 22 29 28 27 21 20 19 DAY 15 14 26 25 24 18 17 16 DATE MONTH 13 12 11 10 9 8 3 2 1 0 YEAR 7 6 5 4 – Note: CENT In UTC mode, values read in this register are not relevant CENT: Current Century The range that can be set is 19–20 (Gregorian) or 13–14 (Persian) (BCD). The lowest four bits encode the units. The higher bits encode the tens. YEAR: Current Year The range that can be set is 00–99 (BCD). The lowest four bits encode the units. The higher bits encode the tens. MONTH: Current Month The range that can be set is 01–12 (BCD). The lowest four bits encode the units. The higher bits encode the tens. DAY: Current Day in Current Week The range that can be set is 1–7 (BCD). The coding of the number (which number represents which day) is user-defined as it has no effect on the date counter. DATE: Current Day in Current Month The range that can be set is 01–31 (BCD). The lowest four bits encode the units. The higher bits encode the tens.  2017 Microchip Technology Inc. DS60001476B-page 309 SAMA5D2 SERIES 26.6.6 RTC Time Alarm Register Name: RTC_TIMALR Address: 0xF80480C0 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 21 20 19 18 17 16 10 9 8 2 1 0 23 22 HOUREN AMPM 15 14 HOUR 13 12 MINEN 7 11 MIN 6 5 4 SECEN 3 SEC This register can only be written if the WPEN bit is cleared in the System Controller Write Protection Mode Register (SYSC_WPMR). Note: To change one of the SEC, MIN, HOUR fields, it is recommended to disable the field before changing the value and then reenable it after the change has been made. This requires up to three accesses to the RTC_TIMALR. The first access clears the enable corresponding to the field to change (SECEN, MINEN, HOUREN). If the field is already cleared, this access is not required. The second access performs the change of the value (SEC, MIN, HOUR). The third access is required to re-enable the field by writing 1 in SECEN, MINEN, HOUREN fields. SEC: Second Alarm This field is the alarm field corresponding to the BCD-coded second counter. SECEN: Second Alarm Enable 0: The second-matching alarm is disabled. 1: The second-matching alarm is enabled. MIN: Minute Alarm This field is the alarm field corresponding to the BCD-coded minute counter. MINEN: Minute Alarm Enable 0: The minute-matching alarm is disabled. 1: The minute-matching alarm is enabled. HOUR: Hour Alarm This field is the alarm field corresponding to the BCD-coded hour counter. AMPM: AM/PM Indicator This field is the alarm field corresponding to the BCD-coded hour counter. HOUREN: Hour Alarm Enable 0: The hour-matching alarm is disabled. 1: The hour-matching alarm is enabled. DS60001476B-page 310  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.7 RTC Time Alarm Register (UTC_MODE) Name: RTC_TIMALR (UTC_MODE) Address: 0xF80480C0 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UTC_TIME 23 22 21 20 UTC_TIME 15 14 13 12 UTC_TIME 7 6 5 4 UTC_TIME This configuration is relevant only if UTC = 1 in RTC_MR. UTC_TIME: UTC_TIME Alarm This field is the alarm field corresponding to the UTC time counter. To change it, proceed as follows: 1. 2. 3. Disable the UTC alarm by clearing the UTCEN bit in RTC_CALALR if it is not already cleared. Change the UTC_TIME alarm value. Enable the UTC alarm by setting the UTCEN bit in RTC_CALALR.  2017 Microchip Technology Inc. DS60001476B-page 311 SAMA5D2 SERIES 26.6.8 RTC Calendar Alarm Register Name: RTC_CALALR Address: 0xF80480C4 Access: Read/Write 31 30 DATEEN – 29 28 27 26 25 24 18 17 16 DATE 23 22 21 MTHEN – – 20 19 15 14 13 12 11 10 9 8 – – – – – – – – 0 MONTH 7 6 5 4 3 2 1 – – – – – – – This register can only be written if the WPEN bit is cleared in the System Controller Write Protection Mode Register (SYSC_WPMR). Note: To change one of the DATE, MONTH fields, it is recommended to disable the field before changing the value and then reenable it after the change has been made. This requires up to three accesses to the RTC_CALALR. The first access clears the enable corresponding to the field to change (DATEEN, MTHEN). If the field is already cleared, this access is not required. The second access performs the change of the value (DATE, MONTH). The third access is required to re-enable the field by writing 1 in DATEEN, MTHEN fields. MONTH: Month Alarm This field is the alarm field corresponding to the BCD-coded month counter. MTHEN: Month Alarm Enable 0: The month-matching alarm is disabled. 1: The month-matching alarm is enabled. DATE: Date Alarm This field is the alarm field corresponding to the BCD-coded date counter. DATEEN: Date Alarm Enable 0: The date-matching alarm is disabled. 1: The date-matching alarm is enabled. DS60001476B-page 312  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.9 RTC Calendar Alarm Register (UTC_MODE) Name: RTC_CALALR (UTC_MODE) Address: 0xF80480C4 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – UTCEN This register can only be written if the WPEN bit is cleared in the System Controller Write Protection Mode Register (SYSC_WPMR). UTCEN: UTC Alarm Enable 0: The UTC-matching alarm is disabled. 1: The UTC-matching alarm is enabled.  2017 Microchip Technology Inc. DS60001476B-page 313 SAMA5D2 SERIES 26.6.10 RTC Status Register Name: RTC_SR Address: 0xF80480C8 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – TDERR CALEV TIMEV SEC ALARM ACKUPD ACKUPD: Acknowledge for Update Value Name Description 0 FREERUN Time and calendar registers cannot be updated. 1 UPDATE Time and calendar registers can be updated. ALARM: Alarm Flag Value Name Description 0 NO_ALARMEVENT No alarm matching condition occurred. 1 ALARMEVENT An alarm matching condition has occurred. SEC: Second Event Value Name Description 0 NO_SECEVENT No second event has occurred since the last clear. 1 SECEVENT At least one second event has occurred since the last clear. TIMEV: Time Event Value Name Description 0 NO_TIMEVENT No time event has occurred since the last clear. 1 TIMEVENT At least one time event has occurred since the last clear. Note: The time event is selected in the TIMEVSEL field in the Control Register (RTC_CR) and can be any one of the following events: minute change, hour change, noon, midnight (day change). If the RTC is configured in UTC mode, the value returned by this field is not relevant. CALEV: Calendar Event Value Name Description 0 NO_CALEVENT No calendar event has occurred since the last clear. 1 CALEVENT At least one calendar event has occurred since the last clear. Note: The calendar event is selected in the CALEVSEL field in the Control Register (RTC_CR) and can be any one of the following events: week change, month change and year change. If the RTC is configured in UTC mode, the value returned by this field is not relevant. DS60001476B-page 314  2017 Microchip Technology Inc. SAMA5D2 SERIES TDERR: Time and/or Date Free Running Error Value Name Description 0 CORRECT The internal free running counters are carrying valid values since the last read of the Status Register (RTC_SR). 1 ERR_TIMEDATE The internal free running counters have been corrupted (invalid date or time, non-BCD values) since the last read and/or they are still invalid. Note: If the RTC is configured in UTC mode, the value returned by this field is not relevant.  2017 Microchip Technology Inc. DS60001476B-page 315 SAMA5D2 SERIES 26.6.11 RTC Status Clear Command Register Name: RTC_SCCR Address: 0xF80480CC Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – TDERRCLR CALCLR TIMCLR SECCLR ALRCLR ACKCLR ACKCLR: Acknowledge Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). ALRCLR: Alarm Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). SECCLR: Second Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). TIMCLR: Time Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). If the RTC is configured in UTC mode, this bit has no effect. CALCLR: Calendar Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). If the RTC is configured in UTC mode, this bit has no effect. TDERRCLR: Time and/or Date Free Running Error Clear 0: No effect. 1: Clears corresponding status flag in the Status Register (RTC_SR). If the RTC is configured in UTC mode, this bit has no effect. DS60001476B-page 316  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.12 RTC Interrupt Enable Register Name: RTC_IER Address: 0xF80480D0 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – TDERREN CALEN TIMEN SECEN ALREN ACKEN ACKEN: Acknowledge Update Interrupt Enable 0: No effect. 1: The acknowledge for update interrupt is enabled. ALREN: Alarm Interrupt Enable 0: No effect. 1: The alarm interrupt is enabled. SECEN: Second Event Interrupt Enable 0: No effect. 1: The second periodic interrupt is enabled. TIMEN: Time Event Interrupt Enable 0: No effect. 1: The selected time event interrupt is enabled. If the RTC is configured in UTC mode, this bit has no effect. CALEN: Calendar Event Interrupt Enable 0: No effect. 1: The selected calendar event interrupt is enabled. If the RTC is configured in UTC mode, this bit has no effect. TDERREN: Time and/or Date Error Interrupt Enable 0: No effect. 1: The time and date error interrupt is enabled. If the RTC is configured in UTC mode, this bit has no effect.  2017 Microchip Technology Inc. DS60001476B-page 317 SAMA5D2 SERIES 26.6.13 RTC Interrupt Disable Register Name: RTC_IDR Address: 0xF80480D4 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – TDERRDIS CALDIS TIMDIS SECDIS ALRDIS ACKDIS ACKDIS: Acknowledge Update Interrupt Disable 0: No effect. 1: The acknowledge for update interrupt is disabled. ALRDIS: Alarm Interrupt Disable 0: No effect. 1: The alarm interrupt is disabled. SECDIS: Second Event Interrupt Disable 0: No effect. 1: The second periodic interrupt is disabled. TIMDIS: Time Event Interrupt Disable 0: No effect. 1: The selected time event interrupt is disabled. If the RTC is configured in UTC mode, this bit has no effect. CALDIS: Calendar Event Interrupt Disable 0: No effect. 1: The selected calendar event interrupt is disabled. If the RTC is configured in UTC mode, this bit has no effect. TDERRDIS: Time and/or Date Error Interrupt Disable 0: No effect. 1: The time and date error interrupt is disabled. If the RTC is configured in UTC mode, this bit has no effect. DS60001476B-page 318  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.14 RTC Interrupt Mask Register Name: RTC_IMR Address: 0xF80480D8 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – TDERR CAL TIM SEC ALR ACK ACK: Acknowledge Update Interrupt Mask 0: The acknowledge for update interrupt is disabled. 1: The acknowledge for update interrupt is enabled. ALR: Alarm Interrupt Mask 0: The alarm interrupt is disabled. 1: The alarm interrupt is enabled. SEC: Second Event Interrupt Mask 0: The second periodic interrupt is disabled. 1: The second periodic interrupt is enabled. TIM: Time Event Interrupt Mask 0: The selected time event interrupt is disabled. 1: The selected time event interrupt is enabled. If the RTC is configured in UTC mode, this bit is not relevant. CAL: Calendar Event Interrupt Mask 0: The selected calendar event interrupt is disabled. 1: The selected calendar event interrupt is enabled. If the RTC is configured in UTC mode, this bit is not relevant. TDERR: Time and/or Date Error Mask 0: The time and/or date error event is disabled. 1: The time and/or date error event is enabled. If the RTC is configured in UTC mode, this bit has no effect.  2017 Microchip Technology Inc. DS60001476B-page 319 SAMA5D2 SERIES 26.6.15 RTC Valid Entry Register Name: RTC_VER Address: 0xF80480DC Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – NVCALALR NVTIMALR NVCAL NVTIM If the RTC is configured in UTC mode, the values returned by this register are not relevant. NVTIM: Non-valid Time 0: No invalid data has been detected in RTC_TIMR (Time Register). 1: RTC_TIMR has contained invalid data since it was last programmed. NVCAL: Non-valid Calendar 0: No invalid data has been detected in RTC_CALR (Calendar Register). 1: RTC_CALR has contained invalid data since it was last programmed. NVTIMALR: Non-valid Time Alarm 0: No invalid data has been detected in RTC_TIMALR (Time Alarm Register). 1: RTC_TIMALR has contained invalid data since it was last programmed. NVCALALR: Non-valid Calendar Alarm 0: No invalid data has been detected in RTC_CALALR (Calendar Alarm Register). 1: RTC_CALALR has contained invalid data since it was last programmed. DS60001476B-page 320  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.16 RTC TimeStamp Time Register 0 Name: RTC_TSTR0 Address: 0xF8048160 Access: Read-only 31 30 29 28 BACKUP – – – 23 22 21 20 – AMPM 15 14 26 25 24 18 17 16 10 9 8 2 1 0 TEVCNT 19 HOUR 13 12 – 7 27 11 MIN 6 5 4 – 3 SEC These fields are valid for non-UTC mode only. RTC_TSTR0 reports the timestamp of the first tamper event after reading RTC_TSSR0. This register is cleared by reading RTC_TSSR0. SEC: Seconds of the Tamper MIN: Minutes of the Tamper HOUR: Hours of the Tamper AMPM: AM/PM Indicator of the Tamper TEVCNT: Tamper Events Counter Each time a tamper event occurs, this counter is incremented. This counter saturates at 15. Once this value is reached, it is no more possible to know the exact number of tamper events. If this field is not null, this implies that at least one tamper event occurs since last register reset and that the values stored in timestamping registers are valid. BACKUP: System Mode of the Tamper 0: The state of the system is different from backup mode when the tamper event occurs. 1: The system is in backup mode when the tamper event occurs.  2017 Microchip Technology Inc. DS60001476B-page 321 SAMA5D2 SERIES 26.6.17 RTC TimeStamp Time Register 0 (UTC_MODE) Name: RTC_TSTR0 (UTC_MODE) Address: 0xF8048160 Access: Read-only 31 30 29 28 BACKUP – – – 27 26 25 24 23 22 21 20 19 – – – – – 18 17 16 – – – 15 14 13 12 11 10 9 8 – – – – – – – – TEVCNT 7 6 5 4 3 2 1 0 – – – – – – – – RTC_TSTR0 reports the timestamp of the first tamper event. TEVCNT: Tamper Events Counter (cleared by reading RTC_TSSR0) Each time a tamper event occurs, this counter is incremented. This counter saturates at 15. Once this value is reached, it is no more possible to know the exact number of tamper events. If this field is not null, this implies that at least one tamper event occurs since last register reset and that the values stored in timestamping registers are valid. BACKUP: System Mode of the Tamper (cleared by reading RTC_TSSR0) 0: The state of the system is different from Backup mode when the tamper event occurs. 1: The system is in Backup mode when the tamper event occurs. DS60001476B-page 322  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.18 RTC TimeStamp Time Register 1 Name: RTC_TSTR1 Address: 0xF804816C Access: Read-only 31 30 29 28 27 26 25 24 BACKUP – – – – – – – 23 22 21 20 19 18 17 16 – AMPM 15 14 10 9 8 2 1 0 HOUR 13 12 – 7 11 MIN 6 5 4 – 3 SEC These fields are valid for non-UTC mode only. RTC_TSTR1 reports the timestamp of the last tamper event. This register is cleared by reading RTC_TSSR1. SEC: Seconds of the Tamper MIN: Minutes of the Tamper HOUR: Hours of the Tamper AMPM: AM/PM Indicator of the Tamper BACKUP: System Mode of the Tamper 0: The state of the system is different from Backup mode when the tamper event occurs. 1: The system is in Backup mode when the tamper event occurs.  2017 Microchip Technology Inc. DS60001476B-page 323 SAMA5D2 SERIES 26.6.19 RTC TimeStamp Time Register 1 (UTC_MODE) Name: RTC_TSTR1 (UTC_MODE) Address: 0xF804816C Access: Read-only 31 30 29 28 27 26 25 24 BACKUP – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – – RTC_TSTR1 reports the timestamp of the last tamper event. BACKUP: System Mode of the Tamper 0: The state of the system is different from Backup mode when the tamper event occurs. 1: The system is in Backup mode when the tamper event occurs. DS60001476B-page 324  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.20 RTC TimeStamp Date Register Name: RTC_TSDRx Address: 0xF8048164 [0], 0xF8048170 [1] Access: Read-only 31 30 – – 23 22 29 28 27 21 20 19 DAY 15 14 26 25 24 18 17 16 DATE MONTH 13 12 11 10 9 8 3 2 1 0 YEAR 7 6 5 – 4 CENT These fields are relevant for non-UTC mode only. RTC_TSTR0 reports the timestamp of the first tamper event after reading RTC_TSSR0, and RTC_TSTR1 reports the timestamp of the last tamper event. This register is cleared by reading RTC_TSSR. CENT: Century of the Tamper YEAR: Year of the Tamper MONTH: Month of the Tamper DAY: Day of the Tamper DATE: Date of the Tamper The fields contain the date and the source of a tamper occurrence if the TEVCNT is not null.  2017 Microchip Technology Inc. DS60001476B-page 325 SAMA5D2 SERIES 26.6.21 RTC TimeStamp Date Register (UTC_MODE) Name: RTC_TSDRx (UTC_MODE) Address: 0xF8048164 [0], 0xF8048170 [1] Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UTC_TIME 23 22 21 20 UTC_TIME 15 14 13 12 UTC_TIME 7 6 5 4 UTC_TIME UTC_TIME: Time of the Tamper (UTC format) This configuration is relevant only if UTC = 1 in RTC_MR. DS60001476B-page 326  2017 Microchip Technology Inc. SAMA5D2 SERIES 26.6.22 RTC TimeStamp Source Register Name: RTC_TSSRx Address: 0xF8048168 [0], 0xF8048174 [1] Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 DET7 DET6 DET5 DET4 DET3 DET2 DET1 DET0 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – JTAG TST – – The following configuration values are valid for all listed bit names of this register: 0: No alarm generated since the last clear. 1: An alarm has been generated by the corresponding monitor since the last clear. TST: Test Pin Monitor JTAG: JTAG Pins Monitor DETx: PIOBU Intrusion Detector  2017 Microchip Technology Inc. DS60001476B-page 327 SAMA5D2 SERIES 27. System Controller Write Protection (SYSCWP) 27.1 Functional Description To prevent any single software error from corrupting System Controller (SYSC) behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the ”System Controller Write Protection Mode Register” (SYSC_WPMR). The following registers can be write-protected: • • • • • • • • • RSTC Mode Register RTC Control Register RTC Mode Register RTC Time Alarm Register RTC Calendar Alarm Register PIT Mode Register Shutdown Mode Register Shutdown Wakeup Inputs Register Slow Clock Controller Configuration Register DS60001476B-page 328  2017 Microchip Technology Inc. SAMA5D2 SERIES 27.2 System Controller Write Protect (SYSCWP) User Interface Table 27-1: Register Mapping Offset Register Name 0x00 Write Protection Mode Register SYSC_WPMR  2017 Microchip Technology Inc. Access Reset Read/Write 0x0000_0000 DS60001476B-page 329 SAMA5D2 SERIES 27.2.1 System Controller Write Protection Mode Register Name: SYSC_WPMR Address: 0xF80480E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x535943 (“SYC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x535943 (“SYC” in ASCII). See Section 27.1 ”Functional Description” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value Name 0x535943 PASSWD DS60001476B-page 330 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 28. Slow Clock Controller (SCKC) 28.1 Description The System Controller embeds a Slow Clock Controller (SCKC). The SCKC selects the slow clock from one of two sources: • External 32.768 kHz crystal oscillator • Embedded 64 kHz (typical) RC oscillator 28.2 Embedded Characteristics • 64 kHz (typical) RC Oscillator or 32.768 kHz Crystal Oscillator Selector • VDDBU Powered 28.3 Block Diagram Figure 28-1: Block Diagram Security Module Embedded 64 kHz RC Oscillator 32 kHz Slow Clock SLCK XIN32 XOUT32 28.4 32.768 kHz Crystal Oscillator OSCSEL Functional Description The OSCSEL bit is located in the Slow Clock Controller Configuration Register (SCKC_CR) located at the address 0xFC068650 in the backed-up part of the System Controller and, thus, it is preserved while VDDBU is present. The embedded 64 kHz (typical) RC oscillator and the 32.768 kHz crystal oscillator are always enabled as soon as VDDBU is established. The Slow Clock Selector command (OSCSEL bit) selects the slow clock source. After the VDDBU power-on reset, the default configuration is OSCSEL = 0, allowing the system to start on the embedded 64 kHz (typical) RC oscillator. The programmer controls the slow clock switching by software and so must take precautions during the switching phase. 28.4.1 Switching from Embedded 64 kHz RC Oscillator to 32.768 kHz Crystal Oscillator The sequence to switch from the embedded 64 kHz (typical) RC oscillator to the 32.768 kHz crystal oscillator is the following: 1. 2. 3. Switch the master clock to a source different from slow clock (PLL or Main Oscillator) through the Power Management Controller. Switch from the embedded 64 kHz (typical) RC oscillator to the 32.768 kHz crystal oscillator by writing a 1 to the OSCSEL bit. Wait 5 slow clock cycles for internal resynchronization. 28.4.2 Switching from 32.768 kHz Crystal Oscillator to Embedded 64 kHz RC Oscillator The sequence to switch from the 32.768 kHz crystal oscillator to the embedded 64 kHz (typical) RC oscillator is the following: 1. 2. 3. Switch the master clock to a source different from slow clock (PLL or Main Oscillator). Switch from the 32.768 kHz crystal oscillator to the embedded RC oscillator by writing a 0 to the OSCSEL bit. Wait 5 slow clock cycles for internal resynchronization.  2017 Microchip Technology Inc. DS60001476B-page 331 SAMA5D2 SERIES 28.5 Slow Clock Controller (SCKC) User Interface Table 28-1: Offset 0x0 Register Mapping Register Name Slow Clock Controller Configuration Register SCKC_CR DS60001476B-page 332 Access Reset Read/Write 0x0000_0001  2017 Microchip Technology Inc. SAMA5D2 SERIES 28.5.1 Slow Clock Controller Configuration Register Name: SCKC_CR Address: 0xF8048050 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSCSEL 2 – 1 – 0 – OSCSEL: Slow Clock Selector 0 (RC): Slow clock is the embedded 64 kHz (typical) RC oscillator. 1 (XTAL): Slow clock is the 32.768 kHz crystal oscillator.  2017 Microchip Technology Inc. DS60001476B-page 333 SAMA5D2 SERIES 29. Peripheral Touch Controller (PTC) 29.1 Description The QTouch Peripheral Touch Controller (PTC) subsystem offers built-in hardware for capacitive touch measurement on sensors that function as buttons, sliders and wheels. The PTC subsystem supports both mutual and self-capacitance measurement without the need for any external component. It offers sensitivity and noise tolerance, as well as self-calibration, and minimizes the sensitivity tuning effort by the user. The PTC subsystem is intended for autonomously performing capacitive touch sensor measurements. The external capacitive touch sensor is typically formed on a PCB, and the sensor electrodes are connected to the analog charge integrator of the PTC using the device I/ O pins. The PTC supports mutual capacitance sensors organized as capacitive touch matrices in different X-Y configurations. In Mutual Capacitance mode, the PTC requires one pin per X line (drive line) and one pin per Y line (sense line). In Self-capacitance mode, the PTC requires only one pin with a Y-line driver for each self-capacitance sensor. 29.2 Embedded Characteristics • Implements Low-power, High-sensitivity, Environmentally-robust Capacitive Touch Buttons, Sliders, and Wheels - One Pin per Electrode – No External Components - Zero Drift over Temperature and supply/reference ranges - No Need for Temperature or supply/reference compensation • “On demand” or “Timed” measurement • Supports Mutual Capacitance and Self-capacitance Sensing - Up to 8 Buttons in Self-capacitance Mode - Up to 64 Buttons in Mutual Capacitance Mode - Supports Lumped Mode Configuration(1) • Calibration - Load Compensating Charge Sensing - Parasitic capacitance compensation together with the electrode capacitance • Adjustable Gain for Higher Sensitivity - Analog Gain 1 to 16 - Digital Gain 1 to 32 • Noise Immunity - Hardware Noise Filtering by Accumulation 1 to 64 - Adjacent Key Suppression (AKS), Removal of False Detection(2) - Frequency Hopping: Noise Signal De-synchronization for High Conducted Immunity(3) - Noise Signal De-synchronization for High Conducted Immunity • Provided PTC Subsystem Firmware(4) • Acquisition Module (Node Definitions, pPP and PTC Management) is Product-dependent, which implements all Hardware-dependent Operations for Configuration and Measurement of Capacitive Touch or Proximity Sensors • Signal Conditioning Module (Frequency Hopping) applies Algorithmic and Feedback Control Methods to improve the Quality of Measurement Data captured by an Acquisition Module • Post-processing Modules (Key, Scroller) interpret Measurement Data in the Context of a Capacitive Touch or Proximity Sensor • Scroller Module defines Slider and Wheels Configuration and Data, based on Keys Module Setting Note 1: A lumped sensor is implemented as a combination of multiple sense lines (self-capacitance measurement) or multiple drive and sense lines (mutual capacitance measurement) to act as one single button sensor. This provides the application developer with greater flexibility in the touch sensor implementation. 2: The PTC incorporates the Adjacent Key Suppression (AKS) technology, which can be selected on a per-key basis. The AKS technology is used to suppress multiple key presses based on relative signal strength. This feature assists in solving the problem of surface moisture which can bridge a key touch to an adjacent key, causing multiple key presses. 3: This PTC subsystem supports frequency hopping, which tries to select a sampling frequency that does not clash with noise at specific frequencies elsewhere in products or product operating environments. Frequency Hopping tries to hop away from the noise. 4: It is necessary to use the firmware provided by Microchip in order to use the PTC subsystem. DS60001476B-page 334  2017 Microchip Technology Inc. SAMA5D2 SERIES 29.3 Block Diagram Figure 29-1: PTC Block Diagram Host Processor PTC Subsystem AHB Port PTC Subsystem Firmware ARM Cortex-A5 QTM API User Application Host Interface pPP API 8X SRAM AHB Port Mailbox pPP APB Port PTC Digital Controller PTC Analog Front End 8Y User Interface SCLK RC12MHZ_PTC PMC Clock Generator RC12MHZ_REQ Periph_CLK_PTC Periph_CLK_REQ AIC Interrupt Controller Note: 29.4 PTC_IRQ QTM is the QTouch Manager Firmware interface. Signal Description Table 29-1: Signal Description Name Type Description PTC_X[n..0] Input/Output 8 X-lines with n=7 Transmit lines in Mutual Capacitance mode. Receive lines in Self-capacitance mode. PTC_Y[m..0] Input 8 Y-lines with m=7 Receive lines in Mutual/Self-capacitance mode. SCLK Input Connection to the product system 32 kHz slow clock RC12MHZ_PTC Input Direct connection to the 12 MHz RC oscillator RC12MHZ_REQ Output Request to supply the RC12MHz PTC subsystem clock Periph_CLK_PTC Input Peripheral clock enabled by the PTC ID (max 83 MHz) Periph_CLK_REQ Output Request to supply the peripheral clock PTC_IRQ Output One PTC IRQ rises for host flag (28, 29, 30 or 31). 29.5 Product Dependencies The PTC subsystem needs to have some other peripherals of the ARM system configured correctly, as described in the following sections. Those peripherals are the PIO Controller (PIO), the Advanced Interrupt Controller (AIC) and the Power Management Controller (PMC).  2017 Microchip Technology Inc. DS60001476B-page 335 SAMA5D2 SERIES 29.5.1 Power Management The PTC Controller is not continuously clocked. The programmer must first enable the PTC Controller peripheral clock in the Power Management Controller (PMC) before using the PTC Controller. However, if the application does not require PTC operations, the PTC Controller clock can be stopped when not needed and restarted when necessary. Configuring the PTC Controller requires the PTC Controller clock to be enabled. Figure 29-2: PTC Subsystem Clock Sources Clock Generator Security Module Embedded 64 kHz RC Oscillator PTC Subsystem 1/2 XIN32 XOUT32 SCLK Slow Clock SCLK 32.768 kHz Crystal Oscillator RC12MHZ_PTC 12 MHz RC Oscillator 12 MHz RC Peripheral Control Register (PMC_PCR) RC12MHZ_REQ Periph_CLK_PTC Periph_CLK_REQ MCK MCK2 1/2 ON/OFF Periph_clk (ID=58) EN The PTC subsystem operates both from a peripheral clock synchronous to the master clock of the system and from an asynchronous clock source directly connected to the embedded 12 MHz RC oscillator. The selected clocks must be enabled in the PMC before they can be used by the PTC. By default, the 12 MHz RC oscillator is enabled at startup of the product. The various clock sources are as follows: • PERIPH_CLK_PTC This clock source is dedicated to the picoPower processor. It is located in the PMC as Periph_clk[PID]=PCLOCK_LS. This clock is synchronous with the AHB/APB matrix controlling the host interface and the mailbox. The clock frequency is between 12 MHz and 83 MHz. The same clock is used for the ARM interface connected as an APB slave via an AHB/APB bridge. It is also used to program the code/ data SRAM and to access the mailbox SRAM. • RC12MHZ A different clock is used for the PTC digital controller. This clock can be divided internally in the pPP before being used. There is also a small local prescaler in the PTC digital controller to allow lower clock rates. Thus, the PTC operates from an asynchronous clock source and the operation is independent from the main system clock and its derivative clocks, such as the peripheral bus clock (PERIPH_CLK_PTC). • SCLK For the timers, a 32 kHz clock is used and divided internally down to a 1 kHz clock for counting the timer interrupt. DS60001476B-page 336  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 29-3: PTC Subsystem Clock Schematic PTC Subsystem SCLK Timer AHB Port SRAM AHB Port Mailbox APB Port User Interface pPP System PTC_IRQ PTC Digital Controller IRQ0 IRQ1 IRQ2 IRQ3 PTC Periph_CLK_PTC RC12MHZ_PTC 1/3 4 MHz PTC_CLK Prescale 1/4 ADC_CLK Periph_CLK_REQ RC12MHZ_REQ Clock Controller Analog Front End Prescale = 1, 1/2, 1/4 or 1/8 The RC12HMZ clock is internally divided by 3 in the PTC subsystem, and so a 4 MHz clock is provided to the PTC digital controller. This controller can divide the clock further by 1, 2, 4 or 8 to slow down the PTC clock. • ADC_CLK The prescaled clock PTC_CLK is divided by 4 to supply an ADC_CLK to the PTC analog front end. The ADC data rate is defined by the controller. The typical value is about 33 kHz to 66 kHz depending on the timing configuration. 29.5.2 I/O Lines The pins used for interfacing the PTC may be multiplexed with GPIO lines. When the PTC subsystem is activated and the X-Y lines selected, the GPIO switches automatically to analog state. The ADC modules possibly hanging on the same PTC analog lines should not use the same GPIO for ADC conversion. Adjacent GPIO lines to PTC lines must not be used to output high speed signals to avoid crosstalk with PTC sensing. When a line is disabled, the corresponding I/O pin is not reserved for the PTC subsystem, and it can be used for some alternative I/O function. There is an individual selection bit for each Y or X line. In normal cases, just one line should be active at the same time. For more advanced uses, like proximity sensing, several lines may be selected in parallel. The input and output functionality, such as charging and sensing pulses of the selected line, is controlled automatically by the PTC digital controller sequencer in various operating modes. The I/O lines used for analog PTC_X lines and PTC_Y lines must be connected to external capacitive touch sensor electrodes. External components are not required for normal operation. 29.5.3 Interrupt Sources The PTC_IRQ interrupt line is connected on one of the internal sources of the host processor interrupt controller (AIC). Using the PTC_IRQ interrupt requires the interrupt controller to be programmed first. Four interrupts (IRQ0,1,2,3) can be generated in the host interface register. The PTC_IRQ line is a logical “OR” between the four IRQ0, IRQ1, IRQ2 and IRQ3. 29.6 Functional Description The PTC analog front end (AFE) and the digital controller are not managed directly by the Cortex-A5 processor. An intermediate processor (pPP) is introduced to manage all functionalities of the PTC. A pPP program, a “firmware”, is needed. This program is loaded by the ARM (host) in a shared SRAM area. The firmware embeds many software functionalities and algorithms to ensure an efficient touch detection.  2017 Microchip Technology Inc. DS60001476B-page 337 SAMA5D2 SERIES 29.6.1 picoPower Processor (pPP) The picoPower Processor (pPP) is a small processor dedicated to handling the PTC and to processing its data in order to offload the main host ARM processor. The pPP uses a unified memory architecture where instructions and data share the address space. The pPP embeds a 16 Kbytes SRAM block. When the processor is stopped, the 16 Kbytes SRAM block can be used by the ARM processor. The pPP has single-cycle access to instructions and data that reside in the SRAM. Loads and stores go to the local code/data SRAM, the shared mailbox SRAM or the local I/O space. Accesses to the mailbox enter a wait state for every other access cycle. Accesses to code/data SRAM and local I/O space never enter wait states. 29.6.2 Shared Memories The SRAM memory space contains context save, interrupt vectors and a unified instruction/data space that can be used for stacks and instructions. On top of the SRAM space is the shared mailbox SRAM. Figure 29-4: Memory Map Cortex-A5 System Memory Map 0x0080_5000 Topology & Parameters AHB Port AHB Port Mailbox (4 KB) PTC Subsystem pPP PTC X and Y Configuration Buttons, Wheels, Sliders Gain and Filtering Adjacent Key Suppression Frequency Hopping Timing and Parameters 0x0080_4000 pPP Code Firmware SRAM (16 KB) Data 0x0080_0000 Host Interface API 29.6.2.1 APB Port User Interface Registers Command Register: Stop, Reset, Run Host Flag (interrupt) Mailbox The mailbox (4 Kbytes) is used to indicate to the pPP the X and Y topoloy as well as the number of sensors implemented. The mailbox can also be used, for example, to pass the parameters required by an application to adjust the analog or digital gain, the filtering functions and some touch operation timing values. The mailbox is the main way to control the PTC digital and analog components. The pPP firmware reads the mailbox and performs the tasks requested. After execution, some data are fed back to the mailbox to be read by the main processor, such as touch button confirmation or touch position on the slider or wheel. 29.6.2.2 SRAM Data Area The pPP uses the SRAM data area for its own needs and to work with the firmware local variables. This SRAM section is not used to communicate with the ARM. DS60001476B-page 338  2017 Microchip Technology Inc. SAMA5D2 SERIES 29.6.2.3 Firmware in SRAM Code Area The firmware contains all PTC subsystem functionalities, allowing PTC measurement in the different conditions of parameters and configurations. The firmware is a binary file copied to the SRAM code area at the address defined by the memory map. The firmware makes the pPP work properly with some peripherals like the timer, a clock generator and obviously the PTC digital controller and the PTC analog front end. The firmware embeds all QTML (QTouch Modular Library) functionalities. Those modules are not modifiable by the application developer. The QTML functionalities configuration and data are controllable by the mailbox. The host has read and write accesses to the mailbox. 29.6.2.4 Host Interface The pPP can be controlled by the host processor through an APB interface and the user interface registers. This is referred to as the “host interface”. Some configurations are only accessible when the pPP is stopped. The host interface includes pPP flags, which are also called host flags on the firmware, for interprocessor communications. The user interface registers can run, stop and reset the pPP and read the IRQ host flags. Nevertheless, the mailbox remains the main means of communication. • Processor Command Registers The CMD field is part of the host interface and is used to start, stop and reset the pPP. Writing a valid command to this field changes the internal state of the pPP. After a number of cycles, this state change is reflected in the processor state register. When a START command is issued, the host is no longer able to write to host interface registers which are marked as run-time writelocked. The pPP RAM block is also locked by this command. The host interface registers and RAM block can be unlocked by using the STOP or RESET commands. The lock is released when the processor state register reflects this state. 29.6.3 PTC Digital Controller The PTC digital controller is a peripheral of the pPP. It is intended for acquiring capacitive touch sensor and capacitive proximity sensor signals under limited firmware control by the controlling processor. The PTC digital controller consists of an Analog Charge Integrator and a 10-bit ADC Controller, 16-bit Digital Accumulator for the ADC results and a State Machine taking care of sensor sampling and digital accumulation sequence. 29.6.3.1 PTC Digital Controller Operations • Sensing mode (mutual or self) • Control of the ADC 10-bit SAR state machine single ADC conversion or free run mode (comparator and ADC data/accumulator register) • Digital gain up to 32 and averaging up to 64 ADC codes • Selection of the filtering resistance (0, 20, 50 or 100 k?) • Adjustment of the compensation capacitor up to 30 pF • Adjustment of the integration capacitor up to 30 pF • Frequency hopping(1) implementation (modification of the sampling rate to avoid synchronous parasitic noise) • Channel Change Delay Selection CDS(2) (settling time) • Prescaling (1, 1/2, 1/4, 1/8), 4 MHz down to ADC_CLK Note 1: A programmable sampling delay can be used to choose (modify) the sampling frequency that is best suited in an application where other periodic noise sources may otherwise disturb the sampling. Frequency hopping can also be modified automatically from one sampling cycle to another, by setting the software driver parameters. 2: CDS bits define the delay when changing input channels. The delay allows the analog circuits to settle on a new (Y) channel or channel pair (X-Y). The delay is application-dependent, and therefore this option enables the user to select a suitable delay. The delay is expressed as a number of PTC clock cycles. 29.6.4 PTC Analog Front End (AFE) The analog front end consists of X-line drivers, a sensor capacitance compensation circuit and a parasitic capacitance insensitive analog Switched Capacitor Charge Integrator (SCCI). The integrator is connected to sensor Y-lines via an analog multiplexer. When the PTC digital controller is enabled, the SCCI output is automatically connected to the ADC input. The external capacitive touch sensor is typically formed on a PCB and the sensor electrodes are connected to the Analog Charge Integrator of the PTC AFE via MCU I/O port pins. The PTC AFE supports mutual capacitance sensors organized as capacitive touch matrices in different X-Y configurations (QTouch Surface). The PTC AFE requires one pin per X-line and one pin per Y-line. No external components are needed. The PTC AFE also supports “self-capacitance touch sensors” (QTouch). In Self-capacitance mode, the PTC AFE requires just one Y-line pin per self-capacitance sensor.  2017 Microchip Technology Inc. DS60001476B-page 339 SAMA5D2 SERIES Figure 29-5: PTC Analog Front End PTC Analog Front End Y0 Y1 Y2 Analog Filtering To PTC Digital Controller Analog Gain SCCI (Integrator) Y3 10-bit ADC Rs=100k Y4 Y5 Charge Compensation Circuit VREF=VDDANA Y6 Y7 X0 X1 X2 X3 VREF/GND X Line Driver X4 X5 X6 X7 29.6.5 Operations in Mutual Capacitance A mutual capacitance sensor is formed between two I/O lines, a PTC_X electrode for transmitting, and a PTC_Y electrode for receiving. The mutual capacitance between the PTC_X and PTC_Y electrodes is calibrated and measured by the PTC. It is not necessary to connect all X and Y lines; when unused, they can be left unconnected. DS60001476B-page 340  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 29-6: Mutual Capacitance Sensor Arrangement Sensor Capacitance Cx,y PTC_X0 PTC_X1 Cx0,y0 Cx0,y1 Cx0,ym Cx1,y0 Cx1,y1 Cx1,ym Cx2,y0 Cx2,y1 Cxn,y0 Cxn,y1 PTC_X2 ............. PTC_Xn PTC Cxn,ym PTC_Y0 PTC_Y1 PTC_Y2 ............. PTC_Ym 29.6.6 Operations in Self-capacitance The self-capacitance sensor is connected to a single pin on the PTC through the PTC_Ym electrodes to receive the signal. The sensor electrode capacitance is measured by the PTC. Figure 29-7: Self-capacitance Sensor Arrangement PTC_X0 PTC_X1 PTC_X2 ............. PTC_Xn PTC Sensor Capacitance Cy,gnd PTC_Y0 PTC_Y1 Cy0,gnd Cy1,gnd PTC_Y2 ............. Cy2,gnd PTC_Ym Cym,gnd  2017 Microchip Technology Inc. DS60001476B-page 341 SAMA5D2 SERIES 29.7 Peripheral Touch Controller (PTC) User Interface Table 29-2: Register Mapping Offset Register Name 0x28 PTC Command Register 0x30 0x35 DS60001476B-page 342 Access Reset PTC_CMD Write-only – PTC Interrupt Status Register PTC_ISR Read/Write 0x00 PTC Enable Register PTC_IED Write-only –  2017 Microchip Technology Inc. SAMA5D2 SERIES 29.7.1 PTC Command Register Name: PTC_CMD Access: Write-only 7 – 6 – 5 – 4 – 3 2 1 0 CMD CMD: Host Command Issues commands to the pPP. Value Name Description 0x0 NO_ACTION – 0x1 STOP Waits for ongoing execution to complete, then stops. 0x2 RESET Stops and resets. 0x3 Reserved – 0x4 ABORT Stops without waiting for ongoing execution to complete. 0x5 RUN Starts execution (from stopped state). 0x6–0xF Reserved –  2017 Microchip Technology Inc. DS60001476B-page 343 SAMA5D2 SERIES 29.7.2 PTC Interrupt Status Register Name: PTC_ISR Access: Read/Write 7 IRQ3 6 IRQ2 5 IRQ1 4 IRQ0 3 – 2 – 1 – 0 NOTIFY0 NOTIFY0: Notification to the Firmware Used for communications between the host processor and the pPP. The firmware is notified when a command is used. IRQx: Interrupt to the Host Used for communications between the host processor and the pPP. The firmware can set an IRQ event in fields IRQ0 to IRQ3. Any of the pPP IRQ0 to IRQ3 fields automatically rises the PTC_IRQ signal. DS60001476B-page 344  2017 Microchip Technology Inc. SAMA5D2 SERIES 29.7.3 PTC Enable Register Name: PTC_IED Access: Write-only 7 IER3 6 IER2 5 IER1 4 IER0 3 – 2 – 1 – 0 – IERx: Interrupt Enable Enables interrupt for device-to-host interrupt. Writing a zero to this field has no effect.  2017 Microchip Technology Inc. DS60001476B-page 345 SAMA5D2 SERIES 30. Low Power Asynchronous Receiver (RXLP) 30.1 Description The Low Power Asynchronous Receiver (RXLP) is a low-power UART with a slow clock. It works only in Receive mode. It features a Receive Data (RXD) pin that can be used to wake up the system. The wakeup occurs only on data matching—expected data can be a single value, two values, or a range of values. The RXLP operates on a slow clock domain to reduce power consumption. 30.2 - Embedded Characteristics Exit from Backup Mode on Comparison Match Programmable Baud Rate Generator Even, Odd, Mark or Space Parity Check Parity and Framing Error Detection Digital Filter on Receive Line Comparison Function on Received Character Register Write Protection 30.3 Block Diagram Figure 30-1: RXLP Functional Block Diagram RXLP (backup area) Baud Rate Generator Receiver RXD APB Exit Control Logic rxlp_wakeup (to Shutdown Controller) 32.768 kHz Clock Table 30-1: RXLP Pin Description Pin Name Description Type RXD RXLP Receive Data Input 30.4 30.4.1 Product Dependencies Power Management The peripheral clock is not managed by the PMC but rather automatically activated when the RXLP is enabled and receive line is active. The peripheral clock is automatically deactivated after transmission of the wakeup signal. 30.5 Functional Description The RXLP features an RS232 receive-only circuitry able to decode and compare data and parity while the system is in Backup mode. If a matching comparison occurs, the RXLP instructs the system to wake up (if enabled). The RXLP operates in Asynchronous mode only and supports only 8-bit character handling (with or without parity). The RXLP is made up of a receiver and a baud rate generator. Receiver timeout is not implemented and there is no interrupt line. DS60001476B-page 346  2017 Microchip Technology Inc. SAMA5D2 SERIES 30.5.1 Baud Rate Generator The baud rate generator provides the bit period clock named baud rate clock to the receiver. The baud rate clock is the 32.768 kHz clock from the crystal oscillator, divided by 16 times the value (CD) written in the Baud Rate Generator Register (RXLP_BRGR). If RXLP_BRGR is set to 0, the baud rate clock is disabled and the RXLP remains inactive. The maximum allowable baud rate is 32.768 kHz clock divided by 16. The minimum allowable baud rate is 32.768 kHz clock divided by (16 × 3). f 32.768 kHz clock Baud Rate = -------------------------------------16 × CD Figure 30-2: Baud Rate Generator CD CD 32.768 kHz Clock 16-bit Counter OUT >1 1 0 Divide by 16 Baud Rate Clock 0 Receiver Sampling Clock 30.5.2 30.5.2.1 Receiver Receiver Reset, Enable and Disable After device reset, the RXLP is disabled and must be enabled before being used. The receiver can be enabled by setting bit RXEN in the Control Register (RXLP_CR). At this command, the receiver starts looking for a start bit. The programmer can disable the receiver by setting bit RXLP_CR.RXDIS. If the receiver is waiting for a start bit, it is immediately stopped. However, if the receiver has already detected a start bit and is receiving the data, it waits for the stop bit before actually stopping its operation. The receiver can be put in reset state by setting bit RXLP_CR.RSTRX. In this case, the receiver immediately stops its current operations and is disabled, whatever its current state. If RSTRX is applied when data is being processed, this data is lost. After initiating a reset it is mandatory to clear bit RXLP_CR.RSTRX. 30.5.2.2 Start Detection and Data Sampling The RXLP only supports asynchronous operations, and this affects only its receiver. The RXLP detects the start of a received character by sampling the RXD signal until it detects a valid start bit. A low level (space) on RXD is interpreted as a valid start bit if it is detected for more than seven cycles of the sampling clock, which is 16 times the baud rate. Hence, a space that is longer than 7/16 of the bit period is detected as a valid start bit. A space which is 7/16 of a bit period or shorter is ignored and the receiver continues to wait for a valid start bit. When a valid start bit has been detected, the receiver samples the RXD at the theoretical midpoint of each bit. It is assumed that each bit lasts 16 cycles of the sampling clock (1-bit period) so the bit sampling point is eight cycles (0.5-bit period) after the start of the bit. The first sampling point is therefore 24 cycles (1.5-bit periods) after detecting the falling edge of the start bit. Each subsequent bit is sampled 16 cycles (1-bit period) after the previous one.  2017 Microchip Technology Inc. DS60001476B-page 347 SAMA5D2 SERIES Figure 30-3: Character Reception Example: 8-bit, parity enabled 1 stop 0.5 bit period 1 bit period RXD Sampling 30.5.2.3 D0 D1 True Start Detection D2 D3 D4 D5 D6 Stop Bit D7 Parity Bit Parity Error Each time a character is received, the receiver calculates the parity of the received data bits, in accordance with the field PAR in the Mode Register (RXLP_MR). It then compares the result with the received parity bit. If different, the received character is ignored and the receiver continues to wait for a new valid start bit. 30.5.2.4 Receiver Framing Error When a start bit is detected, it generates a character reception when all the data bits have been sampled. The stop bit is also sampled and when it is detected at 0, the received character is ignored and the receiver continues to wait for a new valid start bit. 30.5.2.5 Receiver Digital Filter The RXLP embeds a digital filter on the receive line. It is disabled by default and can be enabled by writing a logical 1 in the FILTER bit of RXLP_MR. When enabled, the receive line is sampled using the 16x bit clock and a three-sample filter (majority 2 over 3) determines the value of the line. 30.5.3 Comparison Function on Received Character Each time a valid character is received (without parity error and without frame error) it is compared to the wakeup trigger values. If the received character matches to the condition of wakeup, it is stored in the Receiver Holding Register (RXLP_RHR), a system wakeup is generated and the RXLP is automatically disabled. If the character received does not match, it is ignored and the receiver continues to wait for a new valid start bit. RXLP_CMPR (see Section 30.6.5 “RXLP Comparison Register”) can be programmed to provide three different comparison methods: • VAL1 equals VAL2—the comparison is performed on a single value and the wakeup request is generated if the received character equals VAL1. • VAL1 is strictly lower than VAL2—any value between VAL1 and VAL2 generates a wakeup request. • VAL1 is strictly higher than VAL2—the wakeup request is generated if either received character equals VAL1 or VAL2. DS60001476B-page 348  2017 Microchip Technology Inc. SAMA5D2 SERIES 30.5.4 Register Write Protection To prevent any single software error from corrupting RXLP behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the RXLP Write Protection Mode Register (RXLP_WPMR). The following registers can be write-protected: • RXLP Mode Register • RXLP Baud Rate Generator Register • RXLP Comparison Register  2017 Microchip Technology Inc. DS60001476B-page 349 SAMA5D2 SERIES 30.6 Low Power Asynchronous Receiver (RXLP) User Interface Table 30-2: Register Mapping Offset Register Name Access Reset 0x0000 Control Register RXLP_CR Write-only – 0x0004 Mode Register RXLP_MR Read/Write 0x0 Reserved – – – 0x0018 Receive Holding Register RXLP_RHR Read-only 0x0 0x001C Reserved – – – 0x0020 Baud Rate Generator Register RXLP_BRGR Read/Write 0x0 0x0024 Comparison Register RXLP_CMPR Read/Write 0x0 Reserved – – – Write Protection Mode Register RXLP_WPMR Read/Write 0x0 Reserved – – – 0x0008–0x0014 0x0028–0x00E0 0x00E4 0x00E8–0x00FC DS60001476B-page 350  2017 Microchip Technology Inc. SAMA5D2 SERIES 30.6.1 RXLP Control Register Name: RXLP_CR Address: 0xF8049000 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – RXDIS RXEN – RSTRX – – RSTRX: Reset Receiver 0: Deactivate the reset of the receiver logic. 1: The receiver logic is reset and disabled. If a character is being received, the reception is aborted. The receiver logic remains in reset state until RSTRX is written to 0. RXEN: Receiver Enable 0: No effect. 1: The receiver is enabled if RXDIS is 0. RXDIS: Receiver Disable 0: No effect. 1: The receiver is disabled. If a character is being processed and RSTRX is not set, the character is completed before the receiver is stopped.  2017 Microchip Technology Inc. DS60001476B-page 351 SAMA5D2 SERIES 30.6.2 RXLP Mode Register Name: RXLP_MR Address: 0xF8049004 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 – – – – PAR 8 – 7 6 5 4 3 2 1 0 – – – FILTER – – – – FILTER: Receiver Digital Filter Value Name Description 0 DISABLED RXLP does not filter the receive line. 1 ENABLED RXLP filters the receive line using a three-sample filter (16x-bit clock) (2 over 3 majority). PAR: Parity Type Value Name Description 0 EVEN Even Parity 1 ODD Odd Parity 2 SPACE Parity forced to 0 3 MARK Parity forced to 1 4 NO No parity DS60001476B-page 352  2017 Microchip Technology Inc. SAMA5D2 SERIES 30.6.3 RXLP Receiver Holding Register Name: RXLP_RHR Address: 0xF8049018 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXCHR RXCHR: Received Character Last received character  2017 Microchip Technology Inc. DS60001476B-page 353 SAMA5D2 SERIES 30.6.4 RXLP Baud Rate Generator Register Name: RXLP_BRGR Address: 0xF8049020 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 1 7 6 5 4 3 2 – – – – – – 0 CD CD: Clock Divisor 0: Baud rate clock is disabled 1 to 3: f32.768 kHz clock / (CD × 16) DS60001476B-page 354  2017 Microchip Technology Inc. SAMA5D2 SERIES 30.6.5 RXLP Comparison Register Name: RXLP_CMPR Address: 0xF8049024 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 VAL2 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 VAL1 VAL1: First Comparison Value for Received Character 0 to 255. The received character must be higher or equal to the value of VAL1 and lower or equal to VAL2 to request a system wakeup. VAL2: Second Comparison Value for Received Character 0 to 255. The received character must be lower or equal to the value of VAL2 and higher or equal to VAL1 to request a system wakeup.  2017 Microchip Technology Inc. DS60001476B-page 355 SAMA5D2 SERIES 30.6.6 RXLP Write Protection Mode Register Name: RXLP_WPMR Address: 0xF80490E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x52584C (RXL in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x52584C (RXL in ASCII). See Section 30.5.4 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value Name 0x52584C PASSWD DS60001476B-page 356 Description Writing any other value in this field aborts the write operation. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 31. Analog Comparator Controller (ACC) 31.1 Description The Analog Comparator Controller (ACC) controls the analog comparator in order to provide an additional source of wakeup when the system wakes up from Wait mode. 31.2 Embedded Characteristics • Source of Wakeup When System Wakes Up from Wait Mode and ULP1 Mode 31.3 Block Diagram Figure 31-1: Analog Comparator Controller Block Diagram VDDBU BIAS Analog Comparator COMPP + COMPN - on Digital Controller AND Wakeup Input for Shutdown Controller ACEN INV User Interface 31.4 Signal Description Table 31-1: ACC Signal Description Pin Name Description Type COMPP, COMPN External analog data inputs Input 31.5 31.5.1 Product Dependencies I/O Lines The analog input pins (COMPP and COMPN) are not multiplexed with digital functions (PIO) on the IO line. 31.5.2 Power Management By clearing the ACEN bit in the ACC Mode Register (ACC_MR), the analog comparator power consumption is reduced to current leakage only.  2017 Microchip Technology Inc. DS60001476B-page 357 SAMA5D2 SERIES 31.6 31.6.1 Functional Description Description The analog comparator is enabled by writing a one to the ACEN bit in the ACC Mode Register (ACC_MR) and the polarity of the comparator output can be configured with bit ACC_MR.INV. The ACC registers are listed in Table 31-2. 31.6.2 Register Write Protection To prevent any single software error from corrupting ACC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the ACC Write Protection Mode Register (ACC_WPMR). If a write access to a write-protected register is detected, the WPVS flag in the ACC Write Protection Status Register (ACC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading the ACC_WPSR register. The following registers can be write-protected: • ACC Mode Register DS60001476B-page 358  2017 Microchip Technology Inc. SAMA5D2 SERIES 31.7 Analog Comparator Controller (ACC) User Interface Table 31-2: Offset Register Mapping Register Name Access Reset 0x00 Control Register ACC_CR Write-only – 0x04 Mode Register ACC_MR Read/Write 0 – – – 0x08–0xE0 Reserved 0xE4 Write Protection Mode Register ACC_WPMR Read/Write 0 0xE8 Write Protection Status Register ACC_WPSR Read-only 0 – – – 0xEC–0xFC Reserved  2017 Microchip Technology Inc. DS60001476B-page 359 SAMA5D2 SERIES 31.7.1 ACC Control Register Name: ACC_CR Address: 0xF804A000 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 SWRST SWRST: Software Reset 0: No effect. 1: Resets the module. DS60001476B-page 360  2017 Microchip Technology Inc. SAMA5D2 SERIES 31.7.2 ACC Mode Register Name: ACC_MR Address: 0xF804A004 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 INV 11 – 10 – 9 – 8 ACEN 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register can only be written if the WPEN bit is cleared in the ACC Write Protection Mode Register. ACEN: Analog Comparator Enable 0 (DIS): Analog comparator disabled. 1 (EN): Analog comparator enabled. INV: Invert Comparator Output 0 (DIS): Analog comparator output is directly processed. 1 (EN): Analog comparator output is inverted prior to being processed.  2017 Microchip Technology Inc. DS60001476B-page 361 SAMA5D2 SERIES 31.7.3 ACC Write Protection Mode Register Name: ACC_WPMR Address: 0xF804A0E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x414343 (“ACC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x414343 (“ACC” in ASCII). Refer to Section 31.6.2 “Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x414343 Name PASSWD DS60001476B-page 362 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 31.7.4 ACC Write Protection Status Register Name: ACC_WPSR Address: 0xF804A0E8 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 WPVS WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of ACC_WPSR. 1: A write protection violation (WPEN = 1) has occurred since the last read of ACC_WPSR.  2017 Microchip Technology Inc. DS60001476B-page 363 SAMA5D2 SERIES 32. Clock Generator 32.1 Description The Clock Generator User Interface is embedded within the Power Management Controller and is described in Section 33.22 “Power Management Controller (PMC) User Interface”. However, the Clock Generator registers are named CKGR_. 32.2 Embedded Characteristics The Clock Generator is made up of: • • • • • • • A low-power 32.768 kHz crystal oscillator A low-power embedded 64 kHz (typical) RC oscillator generating the 32 kHz source clock A 8 to 24 MHz crystal oscillator or a 12 to 48 MHz XRCGB crystal resonator with Bypass mode A 12 MHz RC oscillator A 480 MHz UTMI PLL providing a clock for the USB High-speed Device Controller A 600 to 1200 MHz programmable PLL (input from 8 to 50 MHz), provides the clock to the processor and to the peripherals A 700 MHz fractional-N programmable audio PLL, with 22-bit frequency resolution and two independent programmable post dividers to drive the CLK_AUDIO output pin and the internal peripherals (AUDIOPLLCLK) The Clock Generator provides the following clocks: • • • • • • SLCK—Slow clock. The only permanent clock within the system. MAINCK—output of the Main clock oscillator selection: either 8 to 24 MHz crystal oscillator or 12 MHz RC oscillator PLLACK—output of the divider and the 600 to 1200 MHz programmable PLL (PLLA) AUDIOPLLCLK—output of the first Audio PLL post-divider, with a frequency range from 24 to 125 MHz AUDIOPINCLK—output of the second Audio PLL post-divider, with a frequency range from 8 to 30 MHz UPLLCK—output of the 480 MHz UTMI PLL (UPLL) The Power Management Controller also provides the following operations on clocks: • 8 to 24 MHz crystal oscillator clock failure detector • 32.768 kHz crystal oscillator frequency monitor • Frequency counter on Main clock and an on-the-fly adjustable 12 MHz RC oscillator frequency DS60001476B-page 364  2017 Microchip Technology Inc. SAMA5D2 SERIES 32.3 Block Diagram Figure 32-1: Clock Generator Block Diagram Security Module Embedded 64 kHz RC Oscillator Clock Generator 32 kHz Slow Clock (SLCK) XIN32 32.768 kHz Crystal Oscillator OSCSEL XOUT32 MOSCSEL Embedded 12 MHz RC Oscillator XIN Main Clock (MAINCK) 12 MHz Crystal Oscillator XOUT AUDIOPLLCK AUDIOPLL Audio Clock output pin UPLL UPLL Clock (UPLLCK) PLLA and Divider PLLA Clock (PLLACK) PLLADIV2 Status Control User Interface  2017 Microchip Technology Inc. DS60001476B-page 365 SAMA5D2 SERIES 32.4 Slow Clock The Slow Clock Controller embeds a Slow clock generator that is supplied with the VDDBU power supply. As soon as VDDBU is supplied, both the 32.768 kHz crystal oscillator and the embedded 64 kHz (typical) RC oscillator are powered, but only the RC oscillator is enabled. The Slow clock is generated either by the 32.768 kHz crystal oscillator or by the embedded 64 kHz (typical) RC oscillator divided by two. The selection of the Slow clock source is made via the OSCSEL bit in the Slow Clock Controller Configuration register (SCKC_CR). SCKC_CR.OSCSEL and PMC_SR.OSCSELS report which oscillator is selected as the Slow clock source. PMC_SR.OSCSELS informs when the switch sequence initiated by a new value written in SCKC_CR.OSCSEL is done. 32.4.1 Embedded 64 kHz (typical) RC Oscillator By default, the embedded 64 kHz (typical) RC oscillator is enabled and selected as a source of SLCK. The user has to take into account the possible drifts of this oscillator. Refer to Section 66.2 “DC Characteristics”. 32.4.2 32.768 kHz Crystal Oscillator The Clock Generator integrates a low-power 32.768 kHz crystal oscillator. To use this oscillator, the XIN32 and XOUT32 pins must be connected to a 32.768 kHz crystal. Refer to Section 66. “Electrical Characteristics” for appropriate loading capacitor selection on XIN32 and XOUT32. Note that the user is not obliged to use the 32.768 kHz crystal oscillator and can use the 64 kHz (typical) RC oscillator instead. The 32.768 kHz crystal oscillator provides a more accurate frequency than the 64 kHz (typical) RC oscillator. To select the 32.768 kHz crystal oscillator as the source of the Slow clock, the bit SCKC_CR.OSCSEL must be set. This results in a sequence which enables the 32.768 kHz crystal oscillator. The switch of the Slow clock source is glitch-free. DS60001476B-page 366  2017 Microchip Technology Inc. SAMA5D2 SERIES 32.5 Main Clock The Main clock has two sources: • a 12 MHz RC oscillator with a fast startup time and used at startup • a 8 to 24 MHz crystal oscillator with Bypass mode Figure 32-2: Main Clock Block Diagram MOSCRCEN MOSCRCS Embedded 12 MHz RC Oscillator MOSCSEL MOSCSELS 1 Main Clock (MAINCK) MOSCXTEN 0 XIN Main Crystal Oscillator XOUT MOSCXTST Slow Clock (SLCK) Main Crystal Oscillator Counter MOSCXTS MOSCRCEN MOSCXTEN MOSCSEL Main Clock Frequency Counter 32.5.1 MAINF MAINFRDY 12 MHz RC Oscillator After reset, the 12 MHz RC oscillator is enabled and selected as the source of MAINCK and MCK. MCK is the default clock selected to start up the system. Refer to Section 66.2 “DC Characteristics”. The software can disable or enable the 12 MHz RC oscillator with the MOSCRCEN bit in the Clock Generator Main Oscillator register (CKGR_MOR). When disabling the Main clock by clearing CKGR_MOR.MOSCRCEN, PMC_SR.MOSCRCS is automatically cleared, indicating the Main clock is OFF. Setting the MOSCRCS bit in the Power Management Controller Interrupt Enable register (PMC_IER) triggers an interrupt to the processor. 32.5.2 12 MHz RC Oscillator Clock Frequency Adjustment It is possible for the user to adjust the 12 MHz RC oscillator frequency through the PMC Oscillator Calibration Register (PMC_OCR). By default, PMC_OCR.SEL is low, so the RC oscillator is driven with fuse calibration bits which are programmed during the chip production. The user can adjust the trimming of the 12 MHz RC oscillator through PMC_OCR in order to obtain more accurate frequency (to compensate derating factors such as temperature and voltage).  2017 Microchip Technology Inc. DS60001476B-page 367 SAMA5D2 SERIES In order to calibrate the 12 MHz oscillator frequency, SEL must be set to 1 and a correct frequency value must be configured in the CAL field. It is possible to restart, at anytime, a measurement of the frequency of the selected clock by means of the RCMEAS bit in the Clock Generator Main Clock Frequency register (CKGR_MCFR). Thus, when MAINFRDY flag reads 1, another read access on CKGR_MCFR provides an image of the frequency of the Main clock on MAINF field. The software can calculate the error with an expected frequency and correct PMC_OCR.CAL accordingly. This may be used to compensate frequency drift due to derating factors such as temperature and/or voltage. 32.5.3 8 to 24 MHz Crystal Oscillator After reset, the 8 to 24 MHz crystal oscillator is disabled and is not selected as the source of MAINCK. As the source of MAINCK, the 8 to 24 MHz crystal oscillator provides an accurate frequency. The software enables or disables this oscillator in order to reduce power consumption via CKGR_MOR.MOSCXTEN. When disabling this oscillator by clearing the CKGR_MOR.MOSCXTEN bit, the PMC_SR.MOSCXTS bit is automatically cleared, indicating the 8 to 24 MHz crystal oscillator is off. When enabling this oscillator, the user must initiate the startup time counter. This startup time depends on the characteristics of the external device connected to this oscillator. Refer to Section 66. “Electrical Characteristics” for the startup time. When CKGR_MOR.MOSCXTEN and CKGR_MOR.MOSCXTST are written to enable this oscillator, the PMC_SR.MOSCXTS bit is cleared and the counter starts counting down on the Slow clock divided by 8 from the MOSCXTST value. When the counter reaches 0, the PMC_SR.MOSCXTS is set, indicating that the 8 to 24 MHz crystal oscillator is stabilized. Setting MOSCXTS in the PMC Interrupt Mask register (PMC_IMR) triggers an interrupt to the processor. 32.5.4 Main Clock Source Selection The source of the Main clock can be selected from the following: - embedded 12 MHz RC oscillator - 8 to 24 MHz crystal oscillator - an XRCGB crystal resonator The advantage of the Main RC oscillator is its fast startup time. By default, this oscillator is selected to start the system and it must be selected prior to entering Wait mode. The advantage of the Main crystal oscillator is its high level of accuracy. The selection is made by writing CKGR_MOR.MOSCSEL. The switch of the Main clock source is glitch-free, so there is no need to run out of SLCK or PLLACK in order to change the selection. PMC_SR.MOSCSELS indicates when the switch sequence is done. Setting PMC_IMR.MOSCSELS triggers an interrupt to the processor. The 8 to 24 MHz crystal oscillator can be bypassed by setting the CKGR_MOR.MOSCXTBY to accept an external Main clock on XIN (refer to Section 32.5.5 “Bypassing the 8 to 24 MHz Crystal Oscillator”). MOSCRCEN, MOSCSEL, MOSCXTEN and MOSCXTBY bits are located in the PMC Clock Generator Main Oscillator Register (CKGR_MOR). After a VDDBU power-on reset, the default configuration is MOSCRCEN = 1, MOSCXTEN = 0 and MOSCSEL = 0, allowing the 12 MHz RC oscillator to start as Main clock. DS60001476B-page 368  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 32-3: Main Clock Source Selection MOSCRCEN Embedded 12 MHz RC Oscillator Main Clock XIN XOUT Main Crystal Oscillator MOSCSEL MOSCXTEN MOSCXTBY 32.5.5 Bypassing the 8 to 24 MHz Crystal Oscillator Prior to bypassing the 8 to 24 MHz crystal oscillator, the external clock frequency provided on the XIN pin must be stable and within the values specified in the XIN clock characteristics. Refer to Section 66. “Electrical Characteristics”. The sequence to bypass the crystal oscillator is the following: 1. 2. 3. Ensure that an external clock is connected on XIN. Enable the bypass by setting CKGR_MOR.MOSCXTBY. Disable the 8 to 24 MHz crystal oscillator by clearing CKGR_MOR.MOSCXTEN. 32.5.6 Main Frequency Counter The main frequency counter measures the Main RC oscillator and the Main crystal oscillator against the SLCK and is managed by CKGR_MCFR. During the measurement period, the main frequency counter increments at the speed of the clock defined by the bit CKGR_MCFR.CCSS. A measurement is started in the following cases: • When CKGR_MCFR.RCMEAS is written to ‘1’. • When the 12 MHz RC oscillator is selected as the source of the Main clock and when this oscillator becomes stable (i.e., when the MOSCRCS bit is set) • When the 8 to 24 MHz crystal oscillator is selected as the source of the Main clock and when this oscillator becomes stable (i.e., when the MOSCXTS bit is set) • When the Main clock source selection is modified The measurement period ends at the 16th falling edge of the Slow clock, CKGR_MCFR.MAINFRDY is set and the counter stops counting. Its value can be read in the CKGR_MCFR.MAINF and gives the number of Main clock cycles during 16 periods of Slow clock, so that the frequency of the 12 MHz RC oscillator or the crystal oscillator can be determined.  2017 Microchip Technology Inc. DS60001476B-page 369 SAMA5D2 SERIES Figure 32-4: Main Frequency Counter Block Diagram MOSCXTST PMC_SR Main Crystal Oscillator Startup Counter SLCK MOSCXTS CKGR_MOR MOSCRCEN CKGR_MOR CKGR_MCFR MOSCXTEN RCMEAS CKGR_MOR MOSCSEL CKGR_MCFR Main RC Oscillator 0 Reference Clock MAINF Main Frequency Counter CKGR_MCFR MAINFRDY Main Crystal Oscillator 1 CCSS CKGR_MCFR 32.5.7 Switching Main Clock Between the RC Oscillator and the Crystal Oscillator When switching the source of the Main clock between the RC oscillator and the crystal oscillator, both oscillators must be enabled. After completion of the switch, the unused oscillator can be disabled. If switching to the crystal oscillator, a check must be carried out to ensure that the oscillator is present and that its frequency is valid. Follow the sequence below: 1. Enable the crystal oscillator by setting CKGR_MOR.MOSCXTEN. Configure the CKGR_MOR. MOSCXTST field with the crystal oscillator startup time as defined in Section 66. “Electrical Characteristics”. 2. Wait for PMC_SR.MOSCXTS flag to rise, indicating the end of a startup period of the crystal oscillator. 3. Select the crystal oscillator as the source clock of the frequency meter by setting CKGR_MCFR.CCSS 4. Initiate a frequency measurement by setting CKGR_MCFR.RCMEAS. 5. Read CKGR_MCFR.MAINFRDY until its value equals 1. 6. Read CKGR_MCFR.MAINF and compute the value of the crystal frequency. - If the MAINF value is valid, the Main clock can be switched to the crystal oscillator. DS60001476B-page 370  2017 Microchip Technology Inc. SAMA5D2 SERIES 32.6 Divider and PLLA Block The PLLA embeds an input divider to increase the accuracy of the resulting clock signals. However, the user must respect the PLLA minimum input frequency when programming the divider. Figure 32-5 shows the block diagram of the divider and PLLA block. Figure 32-5: Divider and PLLA Block Diagram DIVA MAINCK MULA Divider OUTA PLLADIV2 /1 or /2 Divider PLLA PLLACK PLLACOUNT SLCK 32.6.1 PLLA Counter LOCKA Divider and Phase Lock Loop Programming The PLLA allows multiplication of the divider’s outputs. The PLLA clock signal has a frequency that depends on the respective source signal frequency and on the parameters DIVA and MULA. The factor applied to the source signal frequency is (MULA + 1)/DIVA. When MULA is written to 0, the PLLA is disabled and its power consumption is saved. Re-enabling the PLLA can be performed by writing a value higher than 0 in the MUL field. Whenever the PLLA is re-enabled or one of its parameters is changed, PMC_SR.LOCKA is automatically cleared. The values written in the PLLACOUNT field in the Clock Generator PLLA register (CKGR_PLLAR) are loaded in the PLLA counter. The PLLA counter then decrements at the speed of the Slow clock until it reaches 0. At this time, PMC_SR.LOCKA is set and can trigger an interrupt to the processor. The user has to load the number of Slow clock cycles required to cover the PLLA transient time into CKGR_PLLACOUNT. The PLLA clock must be divided by 2 by writing PMC_MCKR.PLLADIV2, if the ratio between Processor clock (PCK) and MCK is 3 (MDIV = 3).  2017 Microchip Technology Inc. DS60001476B-page 371 SAMA5D2 SERIES 32.7 UTMI PLL Clock The source of the UTMI PLL (UPLL) is the Main clock (MAINCK). MAINCK must select the Main crystal oscillator to meet the frequency accuracy required by USB. The crystal frequency selection among 12, 16 or 24 MHz must be configured to the correct value in the field SFR_UTMICKTRIM.FREQ, in order to apply the correct multiplier, x40, x30 or x20, respectively. Figure 32-6: UTMI PLL Block Diagram UPLLEN MAINCK UPLLCK UTMI PLL UPLLCOUNT SLCK UTMI PLL Counter LOCKU Whenever the UTMI PLL is enabled by writing UPLLEN in the UTMI Clock register (CKGR_UCKR), PMC_SR.LOCKU is automatically cleared. The values written in CKGR_UCKR.UPLLCOUNT are loaded in the UTMI PLL counter. The UTMI PLL counter then decrements at the speed of the Slow clock divided by 8 until it reaches 0. At this time, the PMC_SR.LOCKU is set in and can trigger an interrupt to the processor. The user has to load the number of Slow clock cycles required to cover the UTMI PLL transient time into CKGR_UCKR.UPLLCOUNT. 32.8 Audio PLL The Audio PLL is a high-resolution fractional-N digital PLL specifically designed for low jitter operation. In audio applications, the CLK_AUDIO output pin typically serves as the Master clock frequency generator for external components such as Audio DAC, Audio ADCs, or Audio Codecs, thus saving one crystal on the board. The reference clock of the Audio PLL is the fast crystal oscillator. The PLL core operating frequency is defined as: FRACR f AUDIOCORECLK = f ref  ND + 1 + --------------------22   2 where fref is the frequency of the main crystal oscillator. Refer to Section 66.8 “PLL Characteristics” for the limits of fAUDIOCORECLK. The PLL core features two post-dividers enabling the generation of two output clock signals, AUDIOPLLCLK and AUDIOPINCLK. AUDIOPLLCLK is dedicated to the PMC and can be sent to the GCLK input of peripherals or to the Programmable clock outputs PCKx. AUDIOPINCLK is dedicated to driving the external audio pin CLK_AUDIO. The AUDIOPLLCLK frequency is defined by the following formula: f AUDIOCORECLK f AUDIOPLLCLK = ----------------------------------------------------( QDPMC + 1 ) The AUDIOPINCLK frequency is defined by the following formula: f AUDIOCORECLK f AUDIOPINCLK = ----------------------------------------------------( DIV × QDAUDIO ) The typical programming sequence of the audio PLL is the following: 1. 2. 3. 4. 5. Disable the PLL by writing ‘0’ in bits PLLEN and RESETN in the Audio PLL Control register 0 (PMC_AUDIO_PLL0). Release the reset of the PLL by writing ‘1’ in PMC_AUDIO_PLL0.RESETN. Configure the PLL frequency by writing QDPMC and ND in PMC_AUDIO_PLL0, QDAUDIO, DIV and FRACR in PMC_AUDIO_PLL1. ND and FRACR must be configured so as to set AUDIOCORECLK frequency in its authorized range. Refer to Section 66. “Electrical Characteristics”. Enable the PLL by writing ‘1’ in PMC_AUDIO_PLL0.PLLEN, PMC_AUDIO_PLL0.PADEN and PMC_AUDIO_PLL0.PMCEN. Wait for the startup time of this PLL. Refer to Section 66. “Electrical Characteristics”. DS60001476B-page 372  2017 Microchip Technology Inc. SAMA5D2 SERIES 6. If needed, ND or FRACR can be adjusted at any time. The typical frequency settling time of this PLL is indicated in Section 66. “Electrical Characteristics”. Figure 32-7: Audio PLL PMC_AUDIO_PLL0.RESETN CKGR_MOR.MOSCXTEN XIN XOUT PMC_AUDIO_PLL0.PLLEN Main Crystal Oscillator CKGR_MOR.MOSCXTBY PLL CORE AUDIOCORECLK ON/OFF /(QDPMC+1) PMC_AUDIO_PLL1.FRACR AUDIOPLLCLK PCKx PMC GCLK PMC_AUDIO_PLL0.QDPMC PMC_AUDIO_PLL0.PMCEN PMC_AUDIO_PLL0.ND ON/OFF /DIV /QDAUDIO PMC_AUDIO_PLL1.DIV PMC_AUDIO_PLL0.PADEN AUDIOPINCLK Audio Clock Output PMC_AUDIO_PLL1.QDAUDIO AUDIO PLL  2017 Microchip Technology Inc. DS60001476B-page 373 SAMA5D2 SERIES 33. Power Management Controller (PMC) 33.1 Description The Power Management Controller (PMC) optimizes power consumption by controlling all system and user peripheral clocks. The PMC enables/disables the clock inputs to many of the peripherals and the Core. 33.2 Embedded Characteristics The Power Management Controller provides the following clocks: • Master Clock (MCK)—programmable from a few hundred Hz to the maximum operating frequency of the device. It is available to the modules running permanently. • Processor Clock (PCK)—must be switched off when processor is entering Idle mode • HS USB Device Clock (UDPCK) • H64MX Matrix Clock (MCK) and H32MX Matrix Clock (MCK or MCK/2) • Peripheral Clocks—provided to the embedded peripherals and independently controllable • Programmable Clock outputs can be selected from the clocks provided by the clock generator and driven on the PCKx pins. • Generic Clock (GCLK) for peripherals that can accept a second clock source • Asynchronous partial wakeup (SleepWalking) for FLEXCOMx, SPIx, TWIx, UARTx and ADC DS60001476B-page 374  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.3 Block Diagram Example 33-1: General Clock Block Diagram PLLA /2 PLLADIV2 1 0 USBS PLLACK UHP48M USBDIV + 1 UHP12M /4 USB OHCI USB EHCI PCK Processor Clock Controller UPLLCK Master Clock Controller (PMC_MCKR) Any Peripheral Interrupt /2 DDRCK 2 x MCK MAINCK SLCK Prescaler /1, /2, /4,...,/64 Divider /1, /2, /3, /4 PRES MDIV CSS MCK Peripheral Clock Controller (PMC_PCR) Periph_clk[PID] PCLOCK_HS (to peripherals) MCK (AHB 64-bit MATRIX system) ON/OFF Periph_clk[PID] HCLOCK_HS (to peripherals) SLCK MAINCK EN Prescaler /1, /2, /3,... /256 UPLLCK MCK AUDIOPLLCK GCKCSS[PID] GCKDIV[PID] ON/OFF GCLK[PID] (to peripherals) GCKEN[PID] Peripheral Clock Controller (PMC_PCR) 0 MCK2 (AHB 32-bit MATRIX system) /2 1 Periph_clk[PID] PCLOCK_LS (to peripherals) ON/OFF Periph_clk[PID] HCLOCK_LS (to peripherals) H32MXDIV EN SLCK MAINCK UPLLCK MCK AUDIOPLLCK Programmable Clock Controller (PMC_PCKx) SLCK MAINCK Prescaler /1, /2, /3,... /256 UPLLCK MCK AUDIOPLLCK PMC_SCERx, PMC_SCDRx Prescaler /1, /2, /3,... /256 GCKCSS[PID] GCKDIV[PID] ON/OFF GCLK[PID] (to peripherals) GCKEN[PID] ON/OFF PCKx (to pads) PRES CSS  2017 Microchip Technology Inc. DS60001476B-page 375 SAMA5D2 SERIES 33.4 Master Clock Controller The Master Clock Controller provides selection and division of the Master clock (MCK). MCK is the source clock of the peripheral clocks. The Master clock is selected from one of the clocks provided by the Clock Generator. Selecting the Slow clock provides a Slow clock signal to the whole device. Selecting the Main clock saves power consumption of the PLLs. The Master Clock Controller is made up of a clock selector and a prescaler. It also contains a Master clock divider which allows the processor clock to be faster than the Master clock. The Master clock selection is made by writing the CSS (Clock Source Selection) field in the Master Clock register (PMC_MCKR). The prescaler supports the division by a power of 2 of the selected clock between 1 and 64, and the division by 6. PMC_MCKR.PRES programs the prescaler. Note: It is forbidden to modify MDIV and CSS at the same access. Each field must be modified separately with a wait for MCKRDY flag between the first field modification and the second field modification. Each time PMC_MCKR is written to define a new Master clock, PMC_SR.MCKRDY is cleared. It reads 0 until the Master clock is established. Then, the MCKRDY bit is set and can trigger an interrupt to the processor. This feature is useful when switching from a high-speed clock to a lower one to inform the software when the change is actually done. Figure 33-1: Master Clock Controller PMC_MCKR PMC_MCKR CSS PRES SLCK MAINCK PLLACK Master Clock Prescaler MCK UPLLCK To the Processor Clock Controller (PCK) 33.5 Processor Clock Controller The PMC features a Processor Clock (PCK) Controller that implements the processor Idle mode. The Processor clock can be disabled by executing the WFI (WaitForInterrupt) processor instruction or the WFE (WaitForEvent) processor instruction while the LPM bit is at 0 in the PMC Fast Startup Mode register (PMC_FSMR). The Processor clock can be disabled by writing the PMC System Clock Disable Register (PMC_SCDR). The status of this clock (at least for debug purposes) can be read in the PMC System Clock Status Register (PMC_SCSR). The Processor clock is enabled after a reset and is automatically re-enabled by any enabled interrupt. The processor Idle mode is entered by disabling the Processor clock, which is automatically re-enabled by any enabled fast or normal interrupt, or by the reset of the product. When processor Idle mode is entered, the current instruction is finished before the clock is stopped, but this does not prevent data transfers from other masters of the system bus. DS60001476B-page 376  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.6 Matrix Clock Controller The AXI Matrix and H64MX 64-bit Matrix clocks are MCK. The H32MX 32-bit matrix clock is to be configured as MCK if MCK does not exceed 83 MHz (refer to Section 66.6.2 “Master Clock Characteristics” in Section 66. “Electrical Characteristics”); otherwise, this clock is to be configured as MCK/2. Selection is done with the H32MXDIV bit in “PMC Master Clock Register” . Figure 33-2: H32MX 32-bit Matrix Clock Configuration PMC_MCKR.H32MXDIV MCK Divider by 2 1 H32MXCLK 0 33.7 Programmable Clock Controller The PMC controls three signals to be outputs on external pins PCKx. Each signal can be independently programmed via the Programmable Clock registers (PMC_PCKx). PCKx can be independently selected between the Slow clock (SLCK), the Master clock (MAINCK), the PLLACK, the UTMI PLL output, the Main clock and the AUDIO PLL (AUDIOPLLCLK) output by writing PMC_PCKx.CSS. Each output signal can also be divided by a factor between 1 and 256 by writing PMC_PCKx.PRES. Each output signal can be enabled and disabled by writing a ‘1’ in the corresponding bits, PMC_SCER.PCKx and PMC_SCDR.PCKx, respectively. The status of each active programmable output clocks is given in PMC_SCSR.PCKx. The status flag PMC_SR.PCKRDYx indicates that the Programmable clock programmed in PMC_PCKx is ready. As the Programmable Clock Controller does not implement glitch prevention when switching clocks, it is strongly recommended to disable the Programmable clock before any configuration change and to re-enable it after the change is performed. 33.8 Core and Bus Independent Clocks for Peripherals Table 33-1 lists the peripherals that can operate while the core, bus and peripheral clock frequencies are modified, thus providing communications at a bit rate which is independent for the core/bus/peripheral clock. This mode of operation is possible by using the internally generated independent clock sources. Table 33-1: Clock Assignments Peripheral Specific Clock Requirements LCDC GCLK GMAC – UDPHS – UHPHS – CLASSD GCLK I2SC GCLK FLEXCOM (USART, SPI, TWI) GCLK ISC PCK (pad clock) MCAN GCLK TC GCLK ADC GCLK  2017 Microchip Technology Inc. DS60001476B-page 377 SAMA5D2 SERIES 33.9 Peripheral and Generic Clock Controller The PMC controls the clocks of the embedded peripherals by means of the Peripheral Control register (PMC_PCR). With this register, the user can enable and disable the different clocks used by the peripherals: - Peripheral clocks (periph_clk[..]), routed to every peripheral and derived from the Master clock (MCK), and - Generic clocks (GCLK[PID]), routed to selected peripherals only (see the Peripheral Identifiers table in section Peripherals). These clocks are independent of the core and bus clocks (PCK, MCK and Periph_clk[PID]). They are generated by selection and division of the following sources: SLCK, MAINCK, UPLLCKDIV, PLLACK, AUDIOCKDIV and MCK. To configure a peripheral’s clocks, PMC_PCR.CMD must be written to ‘1’ and PMC_PCR.PID must be written with the index of the corresponding peripheral. All other configuration fields must be correctly set. To read the current clock configuration of a peripheral, PMC_PCR.CMD must be written to ‘0’ and PMC_PCR.PID must be written with the index of the corresponding peripheral regardless of the values of other fields. This write does not modify the configuration of the peripheral. The PMC_PCR can then be read to know the configuration status of the corresponding PID. The user can also enable and disable these clocks by configuring the Peripheral Clock Enable (PMC_PCERx) and Peripheral Clock Disable (PMC_PCDRx) registers. The status of the peripheral clock activity can be read in the Peripheral Clock Status registers (PMC_PCSRx). When a peripheral or a generic clock is disabled, it is immediately stopped. These clocks are disabled after a reset. To stop a peripheral clock, it is recommended that the system software wait until the peripheral has executed its last programmed operation before disabling the clock. This is to avoid data corruption or erroneous behavior of the system. The bit number in PMC_PCERx, PMC_PCDRx, and PMC_PCSRx is the Peripheral Identifier defined at the product level. The bit number corresponds to the interrupt source number assigned to the peripheral. 33.10 LCDC Clock Controller In order to have more flexibility on the pixel clock, the LCDC can use MCK, or MCKx2 if LCDCK is set in the PMC System Clock Enable Register (PMC_SCER). Figure 33-3: LCDCLK Clock Configuration PMC_SCER.LCDCK LCDC_LCDCCFG0.CLKSEL MCKx2 ON/OFF 1 MCK ON/OFF 0 Selected clock LCDC Pixel Clock Generator System Bus Interface PMC_PCER.PIDx 33.11 ISC Clock Controller In order to have more flexibility on the pixel clock, the ISC can use MCK, or MCKx2 if ISCCK is set in the PMC System Clock Enable Register (PMC_SCER). Figure 33-4: ISCCLK Clock Configuration PMC_SCER.ISCCK MCKx2 ON/OFF 1 MCK ON/OFF 0 PMC_PCERx.PIDx DS60001476B-page 378 ISC ISC_CLKCFG.ICSEL Selected clock Pixel Clock Generator System Bus Interface  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.12 USB Device and Host Clocks The USB Device and Host High Speed ports (UDPHS and UHPHS) clocks are enabled by the corresponding PIDx bits in the Peripheral Clock Enable register (PMC_PCERx). To save power on this peripheral when they are not used, the user can set these bits in the Peripheral Clock Disable register (PMC_PCDRx). Corresponding PIDx bits in the Peripheral Clock Status register (PMC_PCSRx) give the status of these clocks. The PMC also provides the clocks UHP48M and UHP12M to the USB Host OHCI. The USB Host OHCI clocks are controlled by PMC_SCER.UHP. To save power on this peripheral when they are not used, the user can set PMC_SCDR.UHP. PMC_SCSR.UHP gives the status of this clock. The USB host OHCI requires both the 12/48 MHz signal and the Master clock. The USBDIV field in the USB Clock register (PMC_USB) is to be programmed to 9 (division by 10) for normal operations. To further reduce power consumption the user can stop the UTMI PLL. In this case USB high-speed operations are not possible. Nevertheless, as the USB OHCI Input clock can be selected with PMC_USB.USBS (PLLA or UTMI PLL), OHCI full-speed operation remains possible. The user must program the USB OHCI Input clock and the USBDIV divider in the PMC_USB register to generate a 48 MHz and a 12 MHz signal with an accuracy of ±0.25%. The USB clock input is to be defined according to main oscillator via the FREQ field in the UTMI Clock Trimming register (SFR_UTMICKTRIM). Refer to Section 19. “Special Function Registers (SFR)”. This input clock can be 12, 16, or 24 MHz. 33.13 DDR2/LPDDR/LPDDR2 Clock Controller The PMC controls the clocks of the DDR memory. The DDR clock can be enabled and disabled with the DDRCK bit in PMC_SCER and PMC_SDER, respectively. At reset, the DDR clock is disabled to reduce power consumption. If PMC_MCKR.MDIV = 0 (PCK = MCK), the DDR clock is not available. To reduce PLLA power consumption, the user can choose UPLLCK as an input clock for the system. In this case, the DDR Controller can drive LPDDR or LPDDR2 at up to 120 MHz.  2017 Microchip Technology Inc. DS60001476B-page 379 SAMA5D2 SERIES 33.14 Fast Startup from Ultra Low-power (ULP) Mode 0 In Ultra Low-power (ULP) mode 0, the Main clock (MAINCK) must be running, thus either the 12 MHz crystal oscillator or the Fast RC oscillator must be enabled. The lowest power consumption that can be achieved in ULP Mode 0, can be obtained when dividing the selected oscillator frequency by 64 by writing PMC_MCKR.PRES to 6. Any interrupt exits the system from ULP Mode. The software must write PMC_MCKR.PRES to 1 to provide MCK with the fastest clock. If the PLL is used, the startup procedure must be done prior to writing PMC_MCKR.PRES to 1. Figure 33-5 illustrates an example of startup phase from ULP Mode 0 without use of PLL. Figure 33-5: Fast Startup from Ultra Low-Power Mode 0 MODE ULP 187 kHz ACTIVE 12 MHz ULP 187 kHz 12 MHz RC MCK Any interrupt Write PMC_MCKR.PRES = 0 (no division) Synchronization Period Synchronization Period Write PMC_SCDR.PCK = 1 Write PMC_MCKR.PRES = 6 (divided by 64) PMC_SR.MCKRDY Warning: The duration of the WKUPx pins active level must be greater than four MAINCK cycles. DS60001476B-page 380  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.15 Fast Startup from Ultra Low-Power (ULP) Mode 1 The device allows the processor to restart in less than 10 µs while the device exits Ultra Low-power (ULP) mode 1 only if the C-code function managing the ULP mode 1 entry and exit is linked to and executed from on-chip SRAM. Prior to instructing the device to enter ULP mode 1, the RC oscillator must be selected as the Master clock source (PMC_MCKR.CSS must be written to 1, wait for PMC_SR.MCKRDY to be set) and the internal sources of wakeup must be cleared. It must be verified that none of the enabled external wakeup inputs (WKUP) hold an active polarity. The system enters ULP mode 1 either by setting the CKGR_MOR.WAITMODE, or by executing the WaitForEvent (WFE) instruction of the processor while PMC_FSMR.LPM is at 1. Immediately after setting the WAITMODE bit or using the WFE instruction, wait for PMC_SR.MCKRDY to be set. Refer to Figure 33-6. Figure 33-6: Fast Startup from ULP Mode 1 MODE ACTIVE ULP1 ACTIVE 12 MHz RC = off 12 MHz RC 12 MHz RC startup period MCK Write PMC_MCKR.CSS = 1 (fast RC selected) Synchronization Period PMC_SR.MCKRDY Write CKGR_MOR.WAITMODE = 1 or WFE Wakeup Event (WKUP pins, RTC, etc.) few μs startup period A fast startup is enabled upon any of the following events: • • • • • • • detection of a programmed level on one of the nine wake-up inputs (WKUP, PIOBUx) an active alarm from the RTC a resume from the USB Controller SDMMC card detect backup UART (RXLP) received character comparison match an analog comparison (ACC) any SleepWalking event coming from TWI, FLEXCOMx, SPI, ADC The polarity of the nine wake-up inputs is programmable by writing the PMC Fast Startup Polarity register (PMC_FSPR). All the fast restart event sources except SleepWalking can be individually enabled/disabled by writing in PMC_FSMR. SleepWalking events can be individually enabled/disabled by writing in PMC_SLPWK_ERx/PMC_SLPWK_DRx (see Section 33.16 “Asynchronous Partial Wakeup (SleepWalking)”). The fast startup circuitry, as shown in Figure 33-7, is fully asynchronous and provides a fast startup signal to the PMC. As soon as the fast startup signal is asserted, the embedded 12 MHz RC oscillator restarts automatically.  2017 Microchip Technology Inc. DS60001476B-page 381 SAMA5D2 SERIES Figure 33-7: Fast Startup Circuitry FSTT0 WKUP FSTP0 FSTT1 SECUMOD FSTP1 FSTT2 PIOBU0 FSTP2 FSTT9 fast_restart PIOBU7 FSTP9 RTCAL RTC Alarm USBAL USB Alarm SDMMC_CD SDMMC Card Detect Event RXLP_MCE Backup UART Receive Match Event ACC_CE Analog Comparator Event The PMC user interface does not provide the source of the fast startup, but the user can recover this information by reading the PIO Controller and the status registers of the RTC, ACC, RXLP, and USB Controller. DS60001476B-page 382  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.16 Asynchronous Partial Wakeup (SleepWalking) 33.16.1 Description The asynchronous partial wakeup (SleepWalking) wakes up a peripheral in a fully asynchronous way when activity is detected on the communication line. Moreover, under some user configurable conditions, the asynchronous partial wakeup can trigger an exit of the system from ULP mode 1 (full system wakeup). The asynchronous partial wakeup function automatically manages the peripheral clock. It improves the overall power consumption of the system by clocking peripherals only when needed. Only the following peripherals can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. The peripheral selected for asynchronous partial wakeup must be first configured so that its clock is enabled by setting the appropriate PIDx bit in PMC_PCERx. When the system is in ULP mode 1, all clocks of the system (except SLCK) are stopped. When an asynchronous clock request from a peripheral occurs, the PMC partially wakes up the system to feed the clock only to this peripheral. The rest of the system is not fed with the clock, thus optimizing power consumption. Finally, depending on user-configurable conditions, the peripheral either wakes up the whole system if these conditions are met or stops the peripheral clock until the next clock request. If a wakeup request occurs, the Asynchronous Partial Wakeup mode is automatically disabled until the user instructs the PMC to enable asynchronous partial wakeup. This is done by setting PIDx in the PMC SleepWalking Enable register (PMC_SLPWK_ER). Figure 33-8: SleepWalking During Ultra Low-Power Mode 1 system_clock The system is in wait mode. No clock is fed to the system. peripheral_clock Peripheral clock request Peripheral wakeup request Peripheral SleepWalking status The wakeup request wakes up the system and resets the SleepWalking status of the peripheral. When the system is in Active mode, peripherals enabled for asynchronous partial wakeup have their respective clocks stopped until the peripherals request a clock. When a peripheral requests the clock, the PMC provides the clock without CPU intervention. The triggering of the peripheral clock request depends on conditions which can be configured for each peripheral. If these conditions are met, the peripheral asserts a request to the PMC. The PMC disables the Asynchronous Partial Wakeup mode of the peripheral and provides the clock to the peripheral until the user instructs the PMC to re-enable partial wakeup on the peripheral. This is done by setting PIDx in PMC_SLPWK_ER. If the conditions are not met, the peripheral clears the clock request and PMC stops the peripheral clock until the clock request is reasserted by the peripheral. Figure 33-9: SleepWalking During Active Mode system_clock peripheral_clock Peripheral clock request Peripheral wakeup request Peripheral SleepWalking status  2017 Microchip Technology Inc. The wakeup request resets the SleepWalking status of the peripheral. DS60001476B-page 383 SAMA5D2 SERIES 33.16.2 Configuration Procedure Before configuring the asynchronous partial wakeup (SleepWalking) function of a peripheral, check that the peripheral clock is enabled (the PIDx bit in the PMC Peripheral Clock Status register (PMC_PCSR) must be set). The procedure to enable the asynchronous partial wakeup (SleepWalking) function of a peripheral is the following: 1. 2. 3. 4. Check that the corresponding PIDx bit in the PMC SleepWalking Activity Status register (PMC_SLPWK_ASR) is cleared. This ensures that the peripheral has no activity in progress. Enable the asynchronous partial wakeup function of the peripheral by writing a one to the corresponding PIDx bit in PMC_SLPWK_ER. Check that the corresponding PIDx bit in PMC_SLPWK_ASR is cleared. This ensures that no activity has started during the enable phase. In PMC_SLPWK_ASR, if the corresponding PIDx bit is set, the asynchronous partial wakeup function must be immediately disabled by writing a one to the PIDx bit in the PMC SleepWalking Disable register (PMC_SLPWK_DR). Wait for the end of peripheral activity before reinitializing the procedure. If the corresponding PIDx bit is cleared, then the peripheral clock is disabled and the system can now be placed in ULP mode 1. Before entering ULP mode 1, check that the AIP bit in the PMC SleepWalking Activity In Progress register (PMC_SLPWK_AIPR) is cleared. This ensures that none of the peripherals has any activity in progress. Note: When asynchronous partial wakeup (SleepWalking) of a peripheral is enabled and the core is running (system not in ULP mode 1), the peripheral must not be accessed before a wakeup of the peripheral is performed. 33.17 Main Crystal Oscillator Failure Detection The Main crystal oscillator failure detector monitors the 8 to 24 MHz crystal oscillator or ceramic resonator-based oscillator to identify a possible failure of this oscillator. The clock failure detector can be enabled or disabled by configuring CKGR_MOR.CFDEN. The detector is also disabled in either of the following cases: - after a VDDCORE reset - when the oscillator is disabled (CKGR_MOR.MOSCXTEN = 0) A failure is detected by means of a counter incrementing on the main oscillator clock edge and detection logic is triggered by the 32 kHz generated by the 64 kHz (typical) RC oscillator. This oscillator is automatically enabled when CKGR_MOR.CFDEN = 1. The counter is cleared when the 32 kHz generated by the 64 kHz (typical) RC oscillator clock signal is low, and enabled when the signal is high. Thus, the failure detection time is one RC oscillator period. If, during the high level period of the 32 kHz generated by the 64 kHz (typical) RC oscillator clock signal, less than eight 8 to 24 MHz crystal oscillator clock periods have been counted, then a failure is reported. If a failure of the Main clock is detected, bit PMC_SR.CFDEV indicates a failure event and generates an interrupt if the corresponding interrupt source is enabled. The interrupt remains active until a read occurs in PMC_SR. The user can know the status of the clock failure detection at any time by reading bit PMC_SR.CFDS. Figure 33-10: Clock Failure Detection (Example) Main Crystal Oscillator Output SLCK CFDEV Read PMC_SR CFDS Note: Ratio of clock periods is for illustration purposes only. If the 8 to 24 MHz crystal oscillator or ceramic resonator-based oscillator is selected as the source clock of MAINCK (CKGR_MOR.MOSCSEL = 1), and if MCK source is PLLACK or UPLLCK (PMC_MCKR.CSS = 2 or 3), a clock failure detection automatically forces MAINCK to be the source clock for the Master clock (MCK). Then, regardless of the PMC configuration, a clock failure detection automatically forces the 12 MHz RC oscillator to be the source clock for MAINCK. If this oscillator is disabled when a clock failure detection occurs, it is automatically re-enabled by the clock failure detection mechanism. DS60001476B-page 384  2017 Microchip Technology Inc. SAMA5D2 SERIES It takes two 32 kHz (typical) clock cycles to detect and switch from the 8 to 24 MHz crystal oscillator to the 12 MHz RC oscillator if the source Master clock (MCK) is Main clock (MAINCK), or three 32 kHz (typical) cycles if the source of MCK is PLLACK or UPLLCK. A clock failure detection activates a fault output that is connected to the Pulse Width Modulator (PWM) Controller. With this connection, the PWM controller is able to force its outputs and to protect the driven device, if a clock failure is detected. The user can know the status of the clock failure detector at any time by reading bit PMC_SR.FOS. This fault output remains active until the defect is detected and until it is cleared by the bit FOCLR in the PMC Fault Output Clear register (PMC_FOCR). 33.18 32.768 kHz Crystal Oscillator Frequency Monitor The frequency of the 32.768 kHz crystal oscillator can be monitored by means of logic driven by the 12 MHz RC oscillator known as a reliable clock source. This function is enabled by configuring the XT32KFME bit of CKGR_MOR. The error flag XT32KERR in PMC_SR is asserted when the 32.768 kHz crystal oscillator frequency is out of the ±10% nominal frequency value (i.e., 32.768 kHz). The error flag can be cleared only if the Slow clock frequency monitoring is disabled. The monitored clock frequency is declared invalid if at least four consecutive clock period measurement results are over the nominal period ±10%. Due to the possible frequency variation of the embedded 12 MHz RC oscillator acting as reference clock for the monitor logic, any Slow clock crystal frequency deviation over ±10% of the nominal frequency is systematically reported as an error by means of PMC_SR.XT32KERR. Between -1% and -10% and +1% and +10%, the error is not systematically reported. Thus, only a crystal running at a 32.768 kHz frequency ensures that the error flag is not asserted. The permitted drift of the crystal is 10000 ppm (1%), which allows any standard crystal to be used. The error flag can be defined as an interrupt source of the PMC by setting PMC_IER.XT32KERR. 33.19 Programming Sequence Note 1: If the 8 to 24 MHz crystal oscillator is not required, PLL can be directly configured (begin with Step 9. or Step 10.) else this oscillator must be started (begin with Step 5.). 5. 6. 7. 8. Enable the 8 to 24 MHz crystal oscillator by setting CKGR_MOR.MOSCXTEN. The user can define a startup time. This can be achieved by writing a value in CKGR_MOR.MOSCXTST. Once this register has been correctly configured, the user must wait for PMC_SR.MOSCXTS to be set. This can be done either by polling MOSCXTS or by waiting for the interrupt line to be raised if the associated interrupt source (MOSCXTS) has been enabled in PMC_IER. Switch the MAINCK to the 8 to 24 MHz crystal oscillator by setting CKGR_MOR.MOSCSEL. Wait for PMC_SR.MOSCSELS to be set to ensure the switchover is complete. Check the Main clock frequency: The Main clock frequency can be measured via CKGR_MCFR. Read CKGR_MCFR until the MAINFRDY field is set, after which the user can read the field CKGR_MCFR.MAINF by performing an additional read. This provides the number of Main clock cycles that have been counted during a period of 16 Slow clock cycles. If MAINF = 0, switch the MAINCK to the 12 MHz RC oscillator by clearing CKGR_MOR.MOSCSEL. If MAINF ≠ 0, proceed to Step 9. 9. Set the PLLA and divider (if not required, proceed to Step 10.) All parameters needed to configure PLLA and the divider are located in CKGR_PLLAR. The MULA field is the PLLA multiplier factor. This parameter can be programmed between 0 and 127. If MULA is cleared, PLLA is turned off, otherwise the PLLA output frequency is PLLA input frequency multiplied by (MULA + 1). The PLLACOUNT field specifies the number of Slow clock cycles before LOCKA bit is set in PMC_SR after CKGR_PLLAR has been written. Once CKGR_PLLAR has been written, the user must wait for the LOCKA bit to be set in PMC_SR. This can be done either by polling LOCKA in PMC_SR or by waiting for the interrupt line to be raised if the associated interrupt source (LOCKA) has been enabled in PMC_IER. All parameters in CKGR_PLLAR can be programmed in a single write operation. If at some stage parameter MULA or DIVA is modified, LOCKA bit goes low to indicate that PLLA is not yet ready. When PLLA is locked, LOCKA is set again. The user must wait for the LOCKA bit to be set before using the PLLA output clock. 10. Set Bias and High-speed PLL (UPLL) for UTMI  2017 Microchip Technology Inc. DS60001476B-page 385 SAMA5D2 SERIES The UTMI PLL is enabled by setting CKGR_UCKR.UPLLEN. The UTMI Bias must be enabled by setting CKGR_UCKR.BIASEN at the same time. In some cases, it may be preferable to define a startup time. This can be achieved by writing a value in CKGR_UCKR.PLLCOUNT. Once this register has been correctly configured, the user must wait for PMC_SR.LOCKU to be set. This can be done either by polling LOCKU in PMC_SR or by waiting for the interrupt line to be raised if the associated interrupt source (LOCKU) has been enabled in PMC_IER. 11. Select Master Clock and Processor Clock The Master clock and the Processor clock are configurable via PMC_MCKR. The CSS field is used to select the clock source of the Master clock and Processor clock dividers. By default, the selected clock source is the Main clock. The PRES field is used to define the Processor clock and Master clock prescaler. The user can choose between different values from 1 to 256). Prescaler output is the selected clock source frequency divided by the PRES value. The MDIV field is used to define the Master clock divider. It is possible to choose between different values (0, 1, 2, 3). The Master clock output is Processor clock frequency divided by 1, 2, 3 or 4, depending on the value programmed in MDIV. The PMC PLLA clock input must be divided by 2 by writing the PLLADIV2 bit if MDIV is set to 3. By default, MDIV and PLLLADIV2 are cleared, which indicates that Processor clock is equal to the Master clock. Once PMC_MCKR has been written, the user must wait for the MCKRDY bit to be set in PMC_SR. This can be done either by polling MCKRDY in PMC_SR or by waiting for the interrupt line to be raised if the associated interrupt source (MCKRDY) has been enabled in PMC_IER. PMC_MCKR must not be programmed in a single write operation. The programming sequence for PMC_MCKR is the following: If a new value for CSS field corresponds to PLL clock, a) b) c) d) e) f) Program PMC_MCKR.PRES. Wait for PMC_SR.MCKRDY to be set. Program PMC_MCKR.MDIV. Wait for PMC_SR.MCKRDY to be set. Program PMC_MCKR.CSS. Wait for PMC_SR.MCKRDY to be set. If a new value for CSS field corresponds to Main clock or Slow clock, a) b) c) d) Program PMC_MCKR.CSS. Wait for PMC_SR.MCKRDY to be set. Program PMC_MCKR.PRES. Wait for PMC_SR.MCKRDY to be set. If CSS, MDIV or PRES are modified at some stage, the MCKRDY bit goes low to indicate that the Master clock and the Processor clock are not yet ready. The user must wait for the MCKRDY bit to be set again before using the Master and Processor clocks. If PLLA clock was selected as the Master clock and the user decides to modify it by writing in CKGR_PLLR, the MCKRDY flag goes low while PLL is unlocked. Once PLL is locked again, LOCKA goes high and MCKRDY is set. While PLL is unlocked, the Master clock selection is automatically changed to Slow clock. For further information, see Section 33.20.2 “Clock Switching Waveforms”. Code Example: write_register(PMC_MCKR,0x00000001) wait (MCKRDY=1) write_register(PMC_MCKR,0x00000011) wait (MCKRDY=1) The Master clock is Main clock divided by 2. The Processor clock is the Master clock. 12. Select Programmable Clocks Programmable clocks can be enabled and/or disabled via PMC_SCER and PMC_SCDR. 3 programmable clocks can be used. PMC_SCSR indicates which programmable clock is enabled. By default all programmable clocks are disabled. PMC_PCKx registers are used to configure programmable clocks. DS60001476B-page 386  2017 Microchip Technology Inc. SAMA5D2 SERIES The PMC_PCKx.CSS field selects the programmable clock divider source. Five clock options are available: Main clock, Slow clock, Master clock, PLLACK, UPLLCK. The Slow clock is the default clock source. The PRES field is used to control the programmable clock prescaler. It is possible to choose among different values (from 1 to 256). Programmable clock output is prescaler input divided by PRES parameter. By default, the PRES value is cleared which means that PCKx is equal to Slow clock. Once the PMC_PCKx register has been configured, The corresponding programmable clock must be enabled and the user is constrained to wait for the PCKRDYx bit to be set in PMC_SR. This can be done either by polling PCKRDYx in PMC_SR or by waiting for the interrupt line to be raised if the associated interrupt source (PCKRDYx) has been enabled in PMC_IER. All parameters in PMC_PCKx can be programmed in a single write operation. If the CSS and PRES parameters are to be modified, the corresponding programmable clock must be disabled first. The parameters can then be modified. Once this has been done, the user must re-enable the programmable clock and wait for the PCKRDYx bit to be set. 13. Enable Peripheral Clocks Once all of the previous steps have been completed, the peripheral clocks can be enabled and/or disabled via PMC_PCERx and PMC_PCDRx. 33.20 Clock Switching Details 33.20.1 Master Clock Switching Timings Table 33-2 and Table 33-3 give the worst case timings required for the Master clock to switch from one selected clock to another one. This is in the event that the prescaler is deactivated. When the prescaler is activated, an additional time of 64 clock cycles of the new selected clock has to be added. Table 33-2: Clock Switching Timings (Worst Case) From To Main Clock SLCK PLL Clock Main Clock – 4 × SLCK + 2.5 × Main Clock SLCK 0.5 × Main Clock + 4.5 × SLCK – 3 × PLL Clock + 5 × SLCK PLL Clock 0.5 × Main Clock + 4 × SLCK + PLLCOUNT × SLCK + 2.5 × PLL Clock 2.5 × PLL Clock + 5 × SLCK + PLLCOUNT × SLCK 2.5 × PLL Clock + 4 × SLCK + PLLCOUNT × SLCK 3 × PLL Clock + 4 × SLCK + 1 × Main Clock Note 1: PLL designates either the PLLA or the UPLL Clock. 2: PLLCOUNT designates either PLLACOUNT or UPLLCOUNT. Table 33-3: Clock Switching Timings Between Two PLLs (Worst Case) From To PLLA Clock UPLL Clock PLLA Clock 2.5 × PLLA Clock + 4 × SLCK + PLLACOUNT × SLCK 3 × PLLA Clock + 4 × SLCK + 1.5 × PLLA Clock UPLL Clock 3 × UPLL Clock + 4 × SLCK + 1.5 × UPLL Clock 2.5 × UPLL Clock + 4 × SLCK + UPLLCOUNT × SLCK  2017 Microchip Technology Inc. DS60001476B-page 387 SAMA5D2 SERIES 33.20.2 Clock Switching Waveforms Figure 33-11: Switch Master Clock from Slow Clock to PLL Clock Slow Clock PLL Clock LOCK MCKRDY Master Clock Write PMC_MCKR Figure 33-12: Switch Master Clock from Main Clock to Slow Clock Slow Clock Main Clock MCKRDY Master Clock Write PMC_MCKR DS60001476B-page 388  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 33-13: Change PLLA Programming Slow Clock PLLA Clock LOCKA MCKRDY Master Clock Slow Clock Write CKGR_PLLAR Figure 33-14: Programmable Clock Output Programming PLL Clock PCKRDY PCKx Output Write PMC_PCKx Write PMC_SCER Write PMC_SCDR  2017 Microchip Technology Inc. PLL Clock is selected PCKx is enabled PCKx is disabled DS60001476B-page 389 SAMA5D2 SERIES 33.21 Register Write Protection To prevent any single software error from corrupting PMC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the PMC Write Protection Mode Register (PMC_WPMR). If a write access to a write-protected register is detected, the WPVS bit in the PMC Write Protection Status Register (PMC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading PMC_WPSR. The following registers can be write-protected: • • • • • • • • • • • • • • • • • • • PMC System Clock Enable Register PMC System Clock Disable Register PMC Peripheral Clock Enable Register 0 PMC Peripheral Clock Disable Register 0 PMC Clock Generator Main Oscillator Register PMC Clock Generator Main Clock Frequency Register PMC Clock Generator PLLA Register PMC Master Clock Register PMC USB Clock Register PMC Programmable Clock Register PMC Fast Startup Polarity Register PMC Fast Startup Mode Register PLL Charge Pump Current Register PMC Oscillator Calibration Register PMC SleepWalking Enable Register 0 PMC SleepWalking Disable Register 1 PMC SleepWalking Enable Register 1 PMC SleepWalking Disable Register 1 PMC SleepWalking Control Register DS60001476B-page 390  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22 Power Management Controller (PMC) User Interface Table 33-4: Register Mapping Offset Register Name Access Reset 0x0000 System Clock Enable Register PMC_SCER Write-only – 0x0004 System Clock Disable Register PMC_SCDR Write-only – 0x0008 System Clock Status Register PMC_SCSR Read-only 0x0000_0005 0x000C Reserved – – – 0x0010 Peripheral Clock Enable Register 0 PMC_PCER0 Write-only – 0x0014 Peripheral Clock Disable Register 0 PMC_PCDR0 Write-only – 0x0018 Peripheral Clock Status Register 0 PMC_PCSR0 Read-only 0x0000_0000 0x001C UTMI Clock Register CKGR_UCKR Read/Write 0x1020_0000 0x0020 Main Oscillator Register CKGR_MOR Read/Write 0x0100_0021 0x0024 Main Clock Frequency Register CKGR_MCFR Read/Write 0x0000_0000 0x0028 PLLA Register CKGR_PLLAR Read/Write 0x0000_3F00 0x002C Reserved – – – 0x0030 Master Clock Register PMC_MCKR Read/Write 0x0000_0001 0x0034 Reserved – – – 0x0038 USB Clock Register PMC_USB Read/Write 0x0000_0000 0x003C Reserved – – – 0x0040 Programmable Clock 0 Register PMC_PCK0 Read/Write 0x0000_0000 0x0044 Programmable Clock 1 Register PMC_PCK1 Read/Write 0x0000_0000 0x0048 Programmable Clock 2 Register PMC_PCK2 Read/Write 0x0000_0000 Reserved – – – 0x0060 Interrupt Enable Register PMC_IER Write-only – 0x0064 Interrupt Disable Register PMC_IDR Write-only – 0x0068 Status Register PMC_SR Read-only 0x0001_0008 0x006C Interrupt Mask Register PMC_IMR Read-only 0x0000_0000 0x0070 Fast Startup Mode Register PMC_FSMR Read/Write 0x0000_0000 0x0074 Fast Startup Polarity Register PMC_FSPR Read/Write 0x0000_0000 0x0078 Fault Output Clear Register PMC_FOCR Write-only – 0x007C Reserved – – – 0x0080 PLL Charge Pump Current Register PMC_PLLICPR Read/Write 0x0000_0000 Reserved – – – 0x00E4 Write ProtectIon Mode Register PMC_WPMR Read/Write 0x0000_0000 0x00E8 Write Protection Status Register PMC_WPSR Read-only 0x0000_0000 Reserved – – – 0x0100 Peripheral Clock Enable Register 1 PMC_PCER1 Write-only – 0x0104 Peripheral Clock Disable Register 1 PMC_PCDR1 Write-only – 0x004C–0x005C 0x0084–0x00E0 0x00EC–0x00FC  2017 Microchip Technology Inc. DS60001476B-page 391 SAMA5D2 SERIES Table 33-4: Register Mapping (Continued) Offset Register Name Access Reset 0x0108 Peripheral Clock Status Register 1 PMC_PCSR1 Read-only 0x0000_0000 0x010C Peripheral Control Register PMC_PCR Read/Write 0x0000_0000 0x0110 Oscillator Calibration Register PMC_OCR Read/Write 0x0040_4040 0x0114 SleepWalking Enable Register 0 PMC_SLPWK_ER0 Write-only – 0x0118 SleepWalking Disable Register 0 PMC_SLPWK_DR0 Write-only – 0x011C SleepWalking Status Register 0 PMC_SLPWK_SR0 Read-only 0x0000_0000 0x0120 SleepWalking Activity Status Register 0 PMC_SLPWK_ASR0 Read-Only – Reserved – – – 0x0134 SleepWalking Enable Register 1 PMC_SLPWK_ER1 Write-only – 0x0138 SleepWalking Disable Register 1 PMC_SLPWK_DR1 Write-only – 0x013C SleepWalking Status Register 1 PMC_SLPWK_SR1 Read-only 0x0000_0000 0x0140 SleepWalking Activity Status Register 1 PMC_SLPWK_ASR1 Read-Only – 0x0144 SleepWalking Activity In Progress Register PMC_SLPWK_AIPR Read-Only – 0x0148 SleepWalking Control Register PMC_SLPWKCR Read/Write 0x0000_0000 0x014C Audio PLL Register 0 PMC_AUDIO_PLL0 Read/Write 0x0000_00D0 0x0150 Audio PLL Register 1 PMC_AUDIO_PLL1 Read/Write 0x0000_0000 0x0124–0x0130 DS60001476B-page 392  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.1 PMC System Clock Enable Register Name: PMC_SCER Address: 0xF0014000 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 ISCCK 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 PCK2 9 PCK1 8 PCK0 7 UDP 6 UHP 5 – 4 – 3 LCDCK 2 DDRCK 1 – 0 – This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. DDRCK: DDR Clock Enable 0: No effect. 1: Enables the DDR clock. LCDCK: MCK2x Clock Enable 0: No effect. 1: Enables the MCK2x clock. Note: MCK2x is selected as LCD Pixel source clock if LCDC_LCDCFG0.CLKSEL = 1. UHP: USB Host OHCI Clocks Enable 0: No effect. 1: Enables the UHP48M and UHP12M OHCI clocks. UDP: USB Device Clock Enable 0: No effect. 1: Enables the USB Device clock. PCKx: Programmable Clock x Output Enable 0: No effect. 1: Enables the corresponding Programmable Clock output. ISCCK: ISC Clock Enable 0: No effect. 1: Enables the ISC clock.  2017 Microchip Technology Inc. DS60001476B-page 393 SAMA5D2 SERIES 33.22.2 PMC System Clock Disable Register Name: PMC_SCDR Address: 0xF0014004 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 ISCCK 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 PCK2 9 PCK1 8 PCK0 7 UDP 6 UHP 5 – 4 – 3 LCDCK 2 DDRCK 1 – 0 PCK This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PCK: Processor Clock Disable 0: No effect. 1: Disables the Processor clock. This is used to enter the processor in Idle mode. DDRCK: DDR Clock Disable 0: No effect. 1: Disables the DDR clock. LCDCK: MCK2x Clock Disable 0: No effect. 1: Disables the MCK2x clock. UHP: USB Host OHCI Clock Disable 0: No effect. 1: Disables the UHP48M and UHP12M OHCI clocks. UDP: USB Device Clock Enable 0: No effect. 1: Disables the USB Device clock. PCKx: Programmable Clock x Output Disable 0: No effect. 1: Disables the corresponding Programmable Clock output. ISCCK: ISC Clock Disable 0: No effect. 1: Disables the ISC clock. DS60001476B-page 394  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.3 PMC System Clock Status Register Name: PMC_SCSR Address: 0xF0014008 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 ISCCK 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 PCK2 9 PCK1 8 PCK0 7 UDP 6 UHP 5 – 4 – 3 LCDCK 2 DDRCK 1 – 0 PCK PCK: Processor Clock Status 0: The Processor clock is disabled. 1: The Processor clock is enabled. DDRCK: DDR Clock Status 0: The DDR clock is disabled. 1: The DDR clock is enabled. LCDCK: MCK2x Clock Status 0: The MCK2x clock is disabled. 1: The MCK2x clock is enabled. Note: MCK2x is selected as LCD Pixel source clock if LCDC_LCDCFG0.CLKSEL = 1. UHP: USB Host Port Clock Status 0: The UHP48M and UHP12M OHCI clocks are disabled. 1: The UHP48M and UHP12M OHCI clocks are enabled. UDP: USB Device Port Clock Status 0: The USB Device clock is disabled. 1: The USB Device clock is enabled. PCKx: Programmable Clock x Output Status 0: The corresponding Programmable Clock output is disabled. 1: The corresponding Programmable Clock output is enabled. ISCCK: ISC Clock Status 0: The ISC clock is disabled. 1: The ISC clock is enabled.  2017 Microchip Technology Inc. DS60001476B-page 395 SAMA5D2 SERIES 33.22.4 PMC Peripheral Clock Enable Register 0 Name: PMC_PCER0 Address: 0xF0014010 Access: Write-only 31 PID31 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 PID18 17 PID17 16 PID16 15 PID15 14 PID14 13 PID13 12 PID12 11 PID11 10 PID10 9 PID9 8 PID8 7 PID7 6 PID6 5 PID5 4 PID4 3 PID3 2 PID2 1 – 0 – This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PIDx: Peripheral Clock x Enable 0: No effect. 1: Enables the corresponding peripheral clock. Note 1: PID2 to PID31 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”. Other peripherals can be enabled in PMC_PCER1. 2: Programming the control bits of the Peripheral ID that are not implemented has no effect on the behavior of the PMC. DS60001476B-page 396  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.5 PMC Peripheral Clock Disable Register 0 Name: PMC_PCDR0 Address: 0xF0014014 Access: Write-only 31 PID31 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 PID18 17 PID17 16 PID16 15 PID15 14 PID14 13 PID13 12 PID12 11 PID11 10 PID10 9 PID9 8 PID8 7 PID7 6 PID6 5 PID5 4 PID4 3 PID3 2 PID2 1 – 0 – This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PIDx: Peripheral Clock x Disable 0: No effect. 1: Disables the corresponding peripheral clock. Note: PID2 to PID31 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”. Other peripherals can be disabled in PMC_PCDR1.  2017 Microchip Technology Inc. DS60001476B-page 397 SAMA5D2 SERIES 33.22.6 PMC Peripheral Clock Status Register 0 Name: PMC_PCSR0 Address: 0xF0014018 Access: Read-only 31 PID31 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 PID18 17 PID17 16 PID16 15 PID15 14 PID14 13 PID13 12 PID12 11 PID11 10 PID10 9 PID9 8 PID8 7 PID7 6 PID6 5 PID5 4 PID4 3 PID3 2 PID2 1 – 0 – PIDx: Peripheral Clock x Status 0: The corresponding peripheral clock is disabled. 1: The corresponding peripheral clock is enabled. Note: PID2 to PID31 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”. Other peripherals status can be read in PMC_PCSR1. DS60001476B-page 398  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.7 PMC UTMI Clock Configuration Register Name: CKGR_UCKR Address: 0xF001401C Access: 31 Read/Write 30 29 28 27 – 26 – 25 – 24 BIASEN 21 20 19 – 18 – 17 – 16 UPLLEN BIASCOUNT 23 22 UPLLCOUNT 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – UPLLEN: UTMI PLL Enable 0: The UTMI PLL is disabled. 1: The UTMI PLL is enabled. When UPLLEN is set, the LOCKU flag is set once the UTMI PLL startup time is achieved. UPLLCOUNT: UTMI PLL Startup Time Specifies the number of Slow clock cycles multiplied by 8 for the UTMI PLL startup time. BIASEN: UTMI BIAS Enable 0: The UTMI BIAS is disabled. 1: The UTMI BIAS is enabled. BIASCOUNT: UTMI BIAS Startup Time Specifies the number of Slow clock cycles for the UTMI BIAS startup time.  2017 Microchip Technology Inc. DS60001476B-page 399 SAMA5D2 SERIES 33.22.8 PMC Clock Generator Main Oscillator Register Name: CKGR_MOR Address: 0xF0014020 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 CFDEN 24 MOSCSEL 19 18 17 16 11 10 9 8 3 MOSCRCEN 2 WAITMODE 1 MOSCXTBY 0 MOSCXTEN KEY 15 14 13 12 MOSCXTST 7 – 6 0 5 ONE 4 0 This register can only be written if the WCKGR_MOR_ONEPEN bit is cleared in the PMC Write Protection Mode Register. Warning: bits 6:4 must always be configured to 010 when programming CKGR_MOR. MOSCXTEN: 8 to 24 MHz Crystal Oscillator Enable A crystal must be connected between XIN and XOUT. 0: The 8 to 24 MHz crystal oscillator is disabled. 1: The 8 to 24 MHz crystal oscillator is enabled. MOSCXTBY must be cleared. When MOSCXTEN is set, the MOSCXTS flag is set once the crystal oscillator startup time is achieved. MOSCXTBY: 8 to 24 MHz Crystal Oscillator Bypass 0: No effect. 1: The 8 to 24 MHz crystal oscillator is bypassed. MOSCXTEN must be cleared. An external clock must be connected on XIN. When MOSCXTBY is set, the MOSCXTS flag in PMC_SR is automatically set. Clearing MOSCXTEN and MOSCXTBY bits allows resetting the MOSCXTS flag. Note: When Main Oscillator Bypass is disabled (MOSCXTBY = 0), the MOSCXTS flag must be read as 0 in PMC_SR prior to enabling the main crystal oscillator (MOSCXTEN = 1). WAITMODE: Wait Mode Command (Write-only) 0: No effect. 1: Puts the device in Wait mode. MOSCRCEN: 12 MHz RC Oscillator Enable 0: The 12 MHz RC oscillator is disabled. 1: The 12 MHz RC oscillator is enabled. When MOSCRCEN is set, the MOSCRCS flag is set once the RC oscillator startup time is achieved. ONE: Must Be Set to 1 When programming CKGR_MOR, bit 5 must always be set to 1; bits 6 and 4 must always be set to 0. MOSCXTST: 8 to 24 MHz Crystal Oscillator Startup Time Specifies the number of Slow clock cycles multiplied by 8 for the crystal oscillator startup time. DS60001476B-page 400  2017 Microchip Technology Inc. SAMA5D2 SERIES KEY: Password Value Name Description 0x37 PASSWD Writing any other value in this field aborts the write operation. MOSCSEL: Main Clock Oscillator Selection 0: The 12 MHz oscillator is selected. 1: The 8 to 24 MHz crystal oscillator is selected. CFDEN: Clock Failure Detector Enable 0: The clock failure detector is disabled. 1: The clock failure detector is enabled.  2017 Microchip Technology Inc. DS60001476B-page 401 SAMA5D2 SERIES 33.22.9 PMC Clock Generator Main Clock Frequency Register Name: CKGR_MCFR Address: 0xF0014024 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 CCSS 23 – 22 – 21 – 20 RCMEAS 19 – 18 – 17 – 16 MAINFRDY 15 14 13 12 11 10 9 8 3 2 1 0 MAINF 7 6 5 4 MAINF This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. MAINF: Main Clock Frequency Gives the number of cycles of the clock selected by the bit CCSS within 16 Slow clock periods. To calculate the frequency of the measured clock: fSELCK = (MAINF × fSLCK) / 16 where frequency is in MHz. MAINFRDY: Main Clock Frequency Measure Ready 0: MAINF value is not valid or the measured oscillator is disabled or a measure has just been started by means of RCMEAS. 1: The measured oscillator has been enabled previously and MAINF value is available. Note: To ensure that a correct value is read on the MAINF field, the MAINFRDY flag must be read at 1 then another read access must be performed on the register to get a stable value on the MAINF field. RCMEAS: RC Oscillator Frequency Measure (write-only) 0: No effect. 1: Restarts measuring of the frequency of the Main clock source. MAINF will carry the new frequency as soon as a low to high transition occurs on the MAINFRDY flag. The measure is performed on the main frequency (i.e., not limited to RC oscillator only), but if the Main clock frequency source is the 8 to 24 MHz crystal oscillator, the restart of measuring is not needed because of the well known stability of crystal oscillators. CCSS: Counter Clock Source Selection 0: The clock of the MAINF counter is the RC oscillator. 1: The clock of the MAINF counter is the crystal oscillator. DS60001476B-page 402  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.10 PMC Clock Generator PLLA Register Name: CKGR_PLLAR Address: 0xF0014028 Access: Read/Write 31 – 30 – 29 ONE 23 22 21 28 – 27 – 26 – 25 – 20 19 18 17 MULA 15 14 13 16 OUTA 12 11 OUTA 7 – 24 MULA 10 9 8 2 – 1 – 0 DIVA PLLACOUNT 6 – 5 – 4 – 3 – This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. Possible limitations on PLL input frequencies and multiplier factors should be checked before using the PMC. DIVA: Divider A 0: PLLA is disabled. 1: Divider is bypassed and the PLL input entry is Main clock (MAINCK). PLLACOUNT: PLLA Counter Specifies the number of Slow clock cycles before the LOCKA bit is set in PMC_SR after CKGR_PLLAR is written. OUTA: PLLA Clock Frequency Range To be programmed to 0. MULA: PLLA Multiplier 0: The PLLA is disabled. 1–127: The PLLA Clock frequency is the PLLA input frequency multiplied by MULA + 1. ONE: Must Be Set to 1 Bit 29 must always be set to 1 when programming CKGR_PLLAR.  2017 Microchip Technology Inc. DS60001476B-page 403 SAMA5D2 SERIES 33.22.11 PMC Master Clock Register Name: PMC_MCKR Address: 0xF0014030 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 H32MXDIV 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 PLLADIV2 11 – 10 – 9 8 7 – 6 5 PRES 4 3 – 2 – 1 MDIV 0 CSS This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. CSS: Master/Processor Clock Source Selection Value Name Description 0 SLOW_CLK Slow clock is selected 1 MAIN_CLK Main clock is selected 2 PLLA_CLK PLLACK is selected 3 UPLL_CLK UPLL Clock is selected PRES: Master/Processor Clock Prescaler Value Name Description 0 CLOCK Selected clock 1 CLOCK_DIV2 Selected clock divided by 2 2 CLOCK_DIV4 Selected clock divided by 4 3 CLOCK_DIV8 Selected clock divided by 8 4 CLOCK_DIV16 Selected clock divided by 16 5 CLOCK_DIV32 Selected clock divided by 32 6 CLOCK_DIV64 Selected clock divided by 64 7 – Reserved MDIV: Master Clock Division Value Name Description Master Clock is Prescaler Output Clock divided by 1. 0 EQ_PCK 1 PCK_DIV2 Master Clock is Prescaler Output Clock divided by 2. DDRCK is equal to MCK. 2 PCK_DIV4 Master Clock is Prescaler Output Clock divided by 4. DDRCK is equal to MCK. 3 PCK_DIV3 Master Clock is Prescaler Output Clock divided by 3. DDRCK is equal to MCK. DS60001476B-page 404 Warning: DDRCK is not available.  2017 Microchip Technology Inc. SAMA5D2 SERIES PLLADIV2: PLLA Divisor by 2 Bit PLLADIV2 must always be set to 1 when MDIV is set to 3. H32MXDIV: AHB 32-bit Matrix Divisor Value Name Description 0 H32MXDIV1 The AHB 32-bit Matrix frequency is equal to the AHB 64-bit Matrix frequency. It is possible only if the AHB 64-bit Matrix frequency does not exceed 83 MHz. 1 H32MXDIV2 The AHB 32-bit Matrix frequency is equal to the AHB 64-bit Matrix frequency divided by 2.  2017 Microchip Technology Inc. DS60001476B-page 405 SAMA5D2 SERIES 33.22.12 PMC USB Clock Register Name: PMC_USB Address: 0xF0014038 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 7 – 6 – 5 – 4 – 3 – 1 – 0 USBS USBDIV 2 – This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. USBS: USB OHCI Input Clock Selection 0: USB Clock Input is PLLA. 1: USB Clock Input is UPLL. USBDIV: Divider for USB OHCI Clock USB Clock is Input clock divided by USBDIV + 1. DS60001476B-page 406  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.13 PMC Programmable Clock Register Name: PMC_PCKx[x = 0..2] Address: 0xF0014040 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 7 6 5 4 3 – 1 CSS 0 PRES PRES 2 This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. CSS: Master Clock Source Selection Value Name Description 0 SLOW_CLK Slow clock is selected 1 MAIN_CLK Main clock is selected 2 PLLA_CLK PLLACK is selected 3 UPLL_CLK UPLL Clock is selected 4 MCK_CLK Master Clock is selected 5 AUDIO_CLK Audio PLL clock is selected PRES: Programmable Clock Prescaler Programmable Clock Frequency = Selected Clock Frequency / (PRES + 1)  2017 Microchip Technology Inc. DS60001476B-page 407 SAMA5D2 SERIES 33.22.14 PMC Interrupt Enable Register Name: PMC_IER Address: 0xF0014060 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 CFDEV 17 MOSCRCS 16 MOSCSELS 15 – 14 – 13 – 12 – 11 – 10 PCKRDY2 9 PCKRDY1 8 PCKRDY0 7 – 6 LOCKU 5 – 4 – 3 MCKRDY 2 – 1 LOCKA 0 MOSCXTS The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Enables the corresponding interrupt MOSCXTS: 8 to 24 MHz Crystal Oscillator Status Interrupt Enable LOCKA: PLLA Lock Interrupt Enable MCKRDY: Master Clock Ready Interrupt Enable LOCKU: UTMI PLL Lock Interrupt Enable PCKRDYx: Programmable Clock Ready x Interrupt Enable MOSCSELS: Main Clock Source Oscillator Selection Status Interrupt Enable MOSCRCS: 12 MHz RC Oscillator Status Interrupt Enable CFDEV: Clock Failure Detector Event Interrupt Enable DS60001476B-page 408  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.15 PMC Interrupt Disable Register Name: PMC_IDR Address: 0xF0014064 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 CFDEV 17 MOSCRCS 16 MOSCSELS 15 – 14 – 13 – 12 – 11 – 10 PCKRDY2 9 PCKRDY1 8 PCKRDY0 7 – 6 LOCKU 5 – 4 – 3 MCKRDY 2 – 1 LOCKA 0 MOSCXTS The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Disables the corresponding interrupt MOSCXTS: 8 to 24 MHz Crystal Oscillator Status Interrupt Disable LOCKA: PLLA Lock Interrupt Disable MCKRDY: Master Clock Ready Interrupt Disable LOCKU: UTMI PLL Lock Interrupt Enable PCKRDYx: Programmable Clock Ready x Interrupt Disable MOSCSELS: Main Oscillator Clock Source Selection Status Interrupt Disable MOSCRCS: 12 MHz RC Oscillator Status Interrupt Disable CFDEV: Clock Failure Detector Event Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 409 SAMA5D2 SERIES 33.22.16 PMC Status Register Name: PMC_SR Address: 0xF0014068 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 GCKRDY 23 – 22 – 21 – 20 FOS 19 CFDS 18 CFDEV 17 MOSCRCS 16 MOSCSELS 15 – 14 – 13 – 12 – 11 – 10 PCKRDY2 9 PCKRDY1 8 PCKRDY0 7 OSCSELS 6 LOCKU 5 – 4 – 3 MCKRDY 2 – 1 LOCKA 0 MOSCXTS MOSCXTS: 8 to 24 MHz Crystal Oscillator Status 0: 8 to 24 MHz crystal oscillator is not stabilized. 1: 8 to 24 MHz crystal oscillator is stabilized. LOCKA: PLLA Lock Status 0: PLLA is not locked. 1: PLLA is locked. MCKRDY: Master Clock Status 0: Master Clock is not ready. 1: Master Clock is ready. LOCKU: UPLL Clock Status 0: UPLL Clock is not ready. 1: UPLL Clock is ready. OSCSELS: Slow Clock Oscillator Selection 0: Embedded 64 kHz RC oscillator is selected. 1: 32.768 kHz crystal oscillator is selected. PCKRDYx: Programmable Clock Ready Status 0: Programmable Clock x is not ready. 1: Programmable Clock x is ready. MOSCSELS: Main Oscillator Selection Status 0: Selection is in progress. 1: Selection is done. MOSCRCS: 12 MHz RC Oscillator Status 0: 12 MHz RC oscillator is not stabilized. 1: 12 MHz RC oscillator is stabilized. CFDEV: Clock Failure Detector Event 0: No clock failure detection of the 8 to 24 MHz crystal oscillator has occurred since the last read of PMC_SR. 1: At least one clock failure detection of the 8 to 24 MHz crystal oscillator has occurred since the last read of PMC_SR. DS60001476B-page 410  2017 Microchip Technology Inc. SAMA5D2 SERIES CFDS: Clock Failure Detector Status 0: A clock failure of the 8 to 24 MHz crystal oscillator is not detected. 1: A clock failure of the 8 to 24 MHz crystal oscillator is detected. FOS: Clock Failure Detector Fault Output Status 0: The fault output of the clock failure detector is inactive. 1: The fault output of the clock failure detector is active. GCKRDY: Generic Clock Status 0: One of the generic clocks is not ready yet. 1: All generic clocks are ready.  2017 Microchip Technology Inc. DS60001476B-page 411 SAMA5D2 SERIES 33.22.17 PMC Interrupt Mask Register Name: PMC_IMR Address: 0xF001406C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 CFDEV 17 MOSCRCS 16 MOSCSELS 15 – 14 – 13 – 12 – 11 – 10 PCKRDY2 9 PCKRDY1 8 PCKRDY0 7 – 6 – 5 – 4 – 3 MCKRDY 2 – 1 LOCKA 0 MOSCXTS The following configuration values are valid for all listed bit names of this register: 0: Corresponding interrupt is not enabled. 1: Corresponding interrupt is enabled. MOSCXTS: 8 to 24 MHz Crystal Oscillator Status Interrupt Mask LOCKA: PLLA Lock Interrupt Mask MCKRDY: Master Clock Ready Interrupt Mask PCKRDYx: Programmable Clock Ready x Interrupt Mask MOSCSELS: Main Oscillator Clock Source Selection Status Interrupt Mask MOSCRCS: 12 MHz RC Oscillator Status Interrupt Mask CFDEV: Clock Failure Detector Event Interrupt Mask DS60001476B-page 412  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.18 PMC Fast Startup Polarity Register Name: PMC_FSPR Address: 0xF0014074 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 FSTP10 9 FSTP9 8 FSTP8 7 FSTP7 6 FSTP6 5 FSTP5 4 FSTP4 3 FSTP3 2 FSTP2 1 FSTP1 0 FSTP0 This register can only be written if the WPEN bit is cleared in PMC Write Protection Mode Register. FSTP0: WKUP Pin Polarity for Fast Startup Defines the active polarity of the wakeup input. If the wakeup input is enabled and at the FSTP level, it enables a fast restart signal. FSTP1: Security Module Polarity for Fast Startup If PMC_FSMR.FSTT1 = 1, FSTP1 must be written to 1. FSTP2–FSTP9: PIOBU0–7 Pin Polarity for Fast Startup Defines the active polarity of the corresponding PIOBUx input. If the corresponding wakeup input is enabled and at the FSTP level, it enables a fast restart signal. FSTP10: GMAC Wakeup On LAN Polarity for Fast Startup If PMC_FSMR.FSTT10 = 1, FSTP10 must be written to 1.  2017 Microchip Technology Inc. DS60001476B-page 413 SAMA5D2 SERIES 33.22.19 PMC Fast Startup Mode Register Name: PMC_FSMR Address: 0xF0014070 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 ACC_CE 24 RXLP_MCE 23 – 22 – 21 – 20 LPM 19 SDMMC_CD 18 USBAL 17 RTCAL 16 – 15 – 14 – 13 – 12 – 11 – 10 FSTT10 9 FSTT9 8 FSTT8 7 FSTT7 6 FSTT6 5 FSTT5 4 FSTT4 3 FSTT3 2 FSTT2 1 FSTT1 0 FSTT0 This register can only be written if the WPEN bit is cleared in PMC Write Protection Mode Register. FSTT0: Fast Startup from WKUP Pin Enable 0: The wakeup input (WKUP) has no effect on the PMC. 1: The wakeup input (WKUP) can trigger a fast restart signal to the PMC. FSTT1: Fast Startup from Security Module Enable 0: The SECUMOD has no effect on the PMC. 1: The SECUMOD can trigger a fast restart signal to the PMC. FSTT2–FSTT9: Fast Startup from PIOBU0–7 Input Enable 0: The corresponding PIOBUx input has no effect on the PMC. 1: The corresponding PIOBUx input can trigger a fast restart signal to the PMC. FSTT10: Fast Startup from GMAC Wakeup On LAN Enable 0: The GMAC_WOL input has no effect on the PMC. 1: The GMAC_WOL input can trigger a fast restart signal to the PMC. RTCAL: Fast Startup from RTC Alarm Enable 0: The RTC alarm has no effect on the PMC. 1: The RTC alarm can trigger a fast restart signal to the PMC. USBAL: Fast Startup from USB Resume Enable 0: The USB resume has no effect on the PMC. 1: The USB resume can trigger a fast restart signal to the PMC. SDMMC_CD: Fast Startup from SDMMC Card Detect Enable 0: The SDMMC card detect has no effect on the PMC. 1: The SDMMC card detect can trigger a fast restart signal to the PMC. LPM: Low-power Mode 0: The WaitForInterrupt (WFI) or the WaitForEvent (WFE) instruction of the processor instructs the processor to enter Idle mode. 1: The WaitForEvent (WFE) instruction of the processor instructs the system to enter ULP mode 1. RXLP_MCE: Fast Startup from Backup UART Receive Match Condition Enable 0: The matching condition on the RXLP has no effect on the PMC. DS60001476B-page 414  2017 Microchip Technology Inc. SAMA5D2 SERIES 1: The matching condition on the RXLP can trigger a fast restart signal to the PMC. ACC_CE: Fast Startup from Analog Comparator Controller Comparison Enable 0: The ACC (Analog Comparator Controller) comparison has no effect on the PMC. 1: The ACC (Analog Comparator Controller) comparison can trigger a fast restart signal to the PMC.  2017 Microchip Technology Inc. DS60001476B-page 415 SAMA5D2 SERIES 33.22.20 PMC Fault Output Clear Register Name: PMC_FOCR Address: 0xF0014078 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 FOCLR FOCLR: Fault Output Clear Clears the clock failure detector fault output. DS60001476B-page 416  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.21 PLL Charge Pump Current Register Name: PMC_PLLICPR Address: 0xF0014080 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 23 – 22 – 21 – 20 – 19 – 18 – 17 15 – 14 – 13 – 12 – 11 – 10 – 9 – 7 – 6 – 5 – 4 – 3 – 2 – 1 24 IVCO_PLLU 16 ICP_PLLU 8 – 0 ICP_PLLA This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. ICP_PLLA: Charge Pump Current To optimize clock performance, this field must be programmed as specified in “PLL A Characteristics” in the Electrical Characteristics section. ICP_PLLU: Charge Pump Current PLL UTMI Should be written to 0. IVCO_PLLU: Voltage Control Output Current PLL UTMI Should be written to 0.  2017 Microchip Technology Inc. DS60001476B-page 417 SAMA5D2 SERIES 33.22.22 PMC Write Protection Mode Register Name: PMC_WPMR Address: 0xF00140E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x504D43 (“PMC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x504D43 (“PMC” in ASCII). See Section 33.21 “Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x504D43 Name PASSWD DS60001476B-page 418 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.23 PMC Write Protection Status Register Name: PMC_WPSR Address: 0xF00140E8 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of PMC_WPSR. 1: A write protection violation has occurred since the last read of PMC_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.  2017 Microchip Technology Inc. DS60001476B-page 419 SAMA5D2 SERIES 33.22.24 PMC Peripheral Clock Enable Register 1 Name: PMC_PCER1 Address: 0xF0014100 Access: Write-only 31 PID63 30 PID62 29 PID61 28 PID60 27 PID59 26 PID58 25 PID57 24 PID56 23 PID55 22 PID54 21 PID53 20 PID52 19 PID51 18 PID50 17 PID49 16 PID48 15 PID47 14 PID46 13 PID45 12 PID44 11 PID43 10 PID42 9 PID41 8 PID40 7 PID39 6 PID38 5 PID37 4 PID36 3 PID35 2 PID34 1 PID33 0 PID32 This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PIDx: Peripheral Clock x Enable 0: No effect. 1: Enables the corresponding peripheral clock. Note 1: PID32 to PID63 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”. 2: Programming the control bits of the Peripheral ID that are not implemented has no effect on the behavior of the PMC. DS60001476B-page 420  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.25 PMC Peripheral Clock Disable Register 1 Name: PMC_PCDR1 Address: 0xF0014104 Access: Write-only 31 PID63 30 PID62 29 PID61 28 PID60 27 PID59 26 PID58 25 PID57 24 PID56 23 PID55 22 PID54 21 PID53 20 PID52 19 PID51 18 PID50 17 PID49 16 PID48 15 PID47 14 PID46 13 PID45 12 PID44 11 PID43 10 PID42 9 PID41 8 PID40 7 PID39 6 PID38 5 PID37 4 PID36 3 PID35 2 PID34 1 PID33 0 PID32 This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PIDx: Peripheral Clock x Disable 0: No effect. 1: Disables the corresponding peripheral clock. Note: PID32 to PID63 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 421 SAMA5D2 SERIES 33.22.26 PMC Peripheral Clock Status Register 1 Name: PMC_PCSR1 Address: 0xF0014108 Access: Read-only 31 PID63 30 PID62 29 PID61 28 PID60 27 PID59 26 PID58 25 PID57 24 PID56 23 PID55 22 PID54 21 PID53 20 PID52 19 PID51 18 PID50 17 PID49 16 PID48 15 PID47 14 PID46 13 PID45 12 PID44 11 PID43 10 PID42 9 PID41 8 PID40 7 PID39 6 PID38 5 PID37 4 PID36 3 PID35 2 PID34 1 PID33 0 PID32 PIDx: Peripheral Clock x Status 0: The corresponding peripheral clock is disabled. 1: The corresponding peripheral clock is enabled. Note: PID32 to PID63 refer to identifiers as defined in Section 11.2 “Peripheral Identifiers”. DS60001476B-page 422  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.27 PMC Peripheral Control Register Name: PMC_PCR Address: 0xF001410C Access: Read/Write 31 – 30 – 23 22 29 GCKEN 28 EN 27 21 20 19 – GCKDIV 26 25 24 18 – 17 – 16 – GCKDIV 15 – 14 – 13 – 12 CMD 11 – 10 9 GCKCSS 8 7 – 6 5 4 3 PID 2 1 0 PID: Peripheral ID Peripheral ID selection from PID2 to the maximum PID number. This refers to identifiers as defined in the section “Peripheral Identifiers”. GCKCSS: Generic Clock Source Selection Value Name Description 0 SLOW_CLK Slow clock is selected 1 MAIN_CLK Main clock is selected 2 PLLA_CLK PLLACK is selected 3 UPLL_CLK UPLL Clock is selected 4 MCK_CLK Master Clock is selected 5 AUDIO_CLK Audio PLL clock is selected CMD: Command 0: Read mode 1: Write mode GCKDIV: Generic Clock Division Ratio Generic clock is: selected clock period divided by GCKDIV + 1. GCKDIV must not be changed while the peripheral selects GCLK (e.g., bit rate, etc.). EN: Enable 0: The selected peripheral clock is disabled. 1: The selected peripheral clock is enabled. GCKEN: Generic Clock Enable 0: The selected generic clock is disabled. 1: The selected generic clock is enabled.  2017 Microchip Technology Inc. DS60001476B-page 423 SAMA5D2 SERIES 33.22.28 PMC Oscillator Calibration Register Name: PMC_OCR Address: 0xF0014110 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 SEL 6 5 4 3 CAL 2 1 0 This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. CAL: 12 MHz RC Oscillator Calibration Bits Calibration bits applied to the RC oscillator when SEL is set. SEL: Selection of RC Oscillator Calibration Bits 0: Factory determined value. 1: Value written by user in CAL field of this register. DS60001476B-page 424  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.29 PMC SleepWalking Enable Register 0 Name: PMC_SLPWK_ER0 Address: 0xF0014114 Access: Write-only 31 – 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register can only be written if the WPEN bit is cleared in the “PMC Write Protection Mode Register” . PIDx: Peripheral x SleepWalking Enable 0: No effect. 1: The asynchronous partial wakeup (SleepWalking) function of the corresponding peripheral is enabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. The clock of the peripheral must be enabled before using its asynchronous partial wakeup (SleepWalking) function (its associated PIDx field in “ISCCK: ISC Clock Status” or “PMC Peripheral Clock Status Register 1” is set to ‘1’). Note: The values for PIDx are defined in section “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 425 SAMA5D2 SERIES 33.22.30 PMC SleepWalking Disable Register 0 Name: PMC_SLPWK_DR0 Address: 0xF0014118 Access: Write-only 31 – 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register can only be written if the WPEN bit is cleared in the “PMC Write Protection Mode Register” . PIDx: Peripheral x SleepWalking Disable 0: No effect. 1: The asynchronous partial wakeup (SleepWalking) function of the corresponding peripheral is disabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. Note: The values for PIDx are defined in the section “Peripheral Identifiers”. DS60001476B-page 426  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.31 PMC SleepWalking Status Register 0 Name: PMC_SLPWK_SR0 Address: 0xF001411C Access: Read-only 31 – 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – PIDx: Peripheral x SleepWalking Status 0: The asynchronous partial wakeup (SleepWalking) function of the peripheral is currently disabled or the peripheral enabled for asynchronous partial wakeup (SleepWalking) cleared the PIDx bit upon detection of a wakeup condition. 1: The asynchronous partial wakeup (SleepWalking) function of the peripheral is currently enabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. Note: The values for PIDx are defined in the section “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 427 SAMA5D2 SERIES 33.22.32 PMC SleepWalking Activity Status Register 0 Name: PMC_SLPWK_ASR0 Address: 0xF0014120 Access: Read-only 31 – 30 PID30 29 PID29 28 PID28 27 PID27 26 PID26 25 PID25 24 PID24 23 PID23 22 PID22 21 PID21 20 PID20 19 PID19 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – PIDx: Peripheral x Activity Status 0: The peripheral x is not presently active. The asynchronous partial wakeup (SleepWalking) function can be activated. 1: The peripheral x is presently active. The asynchronous partial wakeup (SleepWalking) function must not be activated. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. All other PIDs are always read at 0. Note: The values for PIDx are defined in the section “Peripheral Identifiers”. DS60001476B-page 428  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.33 PMC SleepWalking Enable Register 1 Name: PMC_SLPWK_ER1 Address: 0xF0014134 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 PID40 7 – 6 – 5 – 4 – 3 – 2 PID34 1 PID33 0 – This register can only be written if the WPEN bit is cleared in the “PMC Write Protection Mode Register” . PIDx: Peripheral x SleepWalking Enable 0: No effect. 1: The asynchronous partial wakeup (SleepWalking) function of the corresponding peripheral is enabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. The clock of the peripheral must be enabled before using its asynchronous partial wakeup (SleepWalking) function (the associated PIDx field in “PMC Peripheral Clock Status Register 1” or “ISCCK: ISC Clock Status” is set to ‘1’). Note: The values for PIDx are defined in the section “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 429 SAMA5D2 SERIES 33.22.34 PMC SleepWalking Disable Register 1 Name: PMC_SLPWK_DR1 Address: 0xF0014138 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 PID40 7 – 6 – 5 – 4 – 3 – 2 PID34 1 PID33 0 – This register can only be written if the WPEN bit is cleared in the “PMC Write Protection Mode Register” . PIDx: Peripheral x SleepWalking Disable 0: No effect. 1: The asynchronous partial wakeup (SleepWalking) function of the corresponding peripheral is disabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. Note: The values for PIDx are defined in the section “Peripheral Identifiers”. DS60001476B-page 430  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.35 PMC SleepWalking Status Register 1 Name: PMC_SLPWK_SR1 Address: 0xF001413C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 PID40 7 – 6 – 5 – 4 – 3 – 2 PID34 1 PID33 0 – PIDx: Peripheral x SleepWalking Status 0: The asynchronous partial wakeup (SleepWalking) function of the peripheral is currently disabled or the peripheral enabled for asynchronous partial wakeup (SleepWalking) cleared the PIDx bit upon detection of a wakeup condition. 1: The asynchronous partial wakeup (SleepWalking) function of the peripheral is currently enabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. Note: The values for PIDx are defined in the section “Peripheral Identifiers”.  2017 Microchip Technology Inc. DS60001476B-page 431 SAMA5D2 SERIES 33.22.36 PMC SleepWalking Activity Status Register 1 Name: PMC_SLPWK_ASR1 Address: 0xF0014140 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 PID40 7 – 6 – 5 – 4 – 3 – 2 PID34 1 PID33 0 – PIDx: Peripheral x Activity Status 0: The peripheral x is not currently active; the asynchronous partial wakeup (SleepWalking) function can be activated. 1: The peripheral x is currently active; the asynchronous partial wakeup (SleepWalking) function must not be activated. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. All other PIDs are always read at 0. Note: The values for PIDx are defined in the section “Peripheral Identifiers”. DS60001476B-page 432  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.37 PMC SleepWalking Activity In Progress Register Name: PMC_SLPWK_AIPR Address: 0xF0014144 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 AIP AIP: Activity In Progress 0: There is no activity on peripherals. The asynchronous partial wakeup (SleepWalking) function can be activated on one or more peripherals. The device can enter ULP mode 1. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. 1: One or more peripherals are currently active. The device must not enter ULP mode 1 if the asynchronous partial wakeup is enabled for one of the following PIDs: FLEXCOMx, SPIx, TWIx, UARTx and ADC.  2017 Microchip Technology Inc. DS60001476B-page 433 SAMA5D2 SERIES 33.22.38 PMC SleepWalking Control Register Name: PMC_SLPWKCR Address: 0xF0014148 Access: Read/Write 31 – 30 – 29 – 28 SLPWKSR 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 ASR 15 – 14 – 13 – 12 CMD 11 – 10 – 9 – 8 – 7 – 6 5 4 3 PID 2 1 0 This register can only be written if the WPEN bit is cleared in the PMC Write Protection Mode Register. PID: Peripheral ID Peripheral ID selection from PID2 to the maximum PID number. This refers to identifiers as defined in the section “Peripheral Identifiers”. CMD: Command 0: Read mode 1: Write mode ASR: Activity Status Register 0: The peripheral x is not currently active; the asynchronous partial wakeup (SleepWalking) function can be activated. 1: The peripheral x is currently active; the asynchronous partial wakeup (SleepWalking) function must not be activated. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. SLPWKSR: SleepWalking Status Register 0: The asynchronous partial wakeup (SleepWalking) function of the peripheral is disabled. 1: The asynchronous partial wakeup (SleepWalking) function of the peripheral is enabled. Not all PIDs can be configured with asynchronous partial wakeup. Only the following PIDs can be configured with asynchronous partial wakeup: FLEXCOMx, SPIx, TWIx, UARTx and ADC. DS60001476B-page 434  2017 Microchip Technology Inc. SAMA5D2 SERIES 33.22.39 PMC Audio PLL Control Register 0 Name: PMC_AUDIO_PLL0 Address: 0xF001414C Access: Read/Write 31 – 30 – 29 28 27 23 – 22 21 20 19 QDPMC 15 – 14 13 12 7 6 5 4 26 25 24 18 17 16 11 ND 10 9 8 3 RESETN 2 PMCEN 1 PADEN 0 PLLEN DCO_GAIN DCO_FILTER PLLFLT PLLEN: PLL Enable 0: The Audio PLL is disabled. 1: The Audio PLL is enabled PADEN: Pad Clock Enable 0: The external audio pin CLK_AUDIO is driven low. 1: The external audio pin CLK_AUDIO is driven by AUDIOPINCLK. PMCEN: PMC Clock Enable 0: The output clock of the audio PLL is not sent to the PMC. 1: The output clock of the audio PLL is sent to the PMC. RESETN: Audio PLL Reset 0: The audio PLL is in reset state. 1: The audio PLL is in active state. PLLFLT: PLL Loop Filter Selection Default value should be 13 (0xD) ND: Loop Divider Ratio QDPMC: Output Divider Ratio for PMC Clock fpmc = fref × ((ND + 1) + FRACR ÷ 2^22) / (QDPMC + 1) DCO_FILTER: Digitally Controlled Oscillator Filter Selection For optimization, the value of this field must be configured to 0. DCO_GAIN: Digitally Controlled Oscillator Gain Selection For optimization, the value of this field must be configured to 0.  2017 Microchip Technology Inc. DS60001476B-page 435 SAMA5D2 SERIES 33.22.40 PMC Audio PLL Control Register 1 Name: PMC_AUDIO_PLL1 Address: 0xF0014150 Access: Read/Write 31 – 30 29 23 – 22 – 21 15 14 13 28 QDAUDIO 27 20 19 26 25 24 DIV 18 17 16 11 10 9 8 3 2 1 0 FRACR 12 FRACR 7 6 5 4 FRACR FRACR: Fractional Loop Divider Setting DIV: Divider Value Value Name Description 0 FORBIDDEN Reserved 1 FORBIDDEN Reserved 2 DIV2 Divide by 2 3 DIV3 Divide by 3 QDAUDIO: Output Divider Ratio for Pad Clock faudio = fref × ((ND + 1) + FRACR ÷ 2^22) / (DIV x QDAUDIO) DS60001476B-page 436  2017 Microchip Technology Inc. SAMA5D2 SERIES 34. Parallel Input/Output Controller (PIO) 34.1 Description The Parallel Input/Output Controller (PIO) manages up to 128 fully programmable input/output lines. Each I/O line may be dedicated as a general purpose I/O or be assigned to a function of an embedded peripheral. This ensures effective optimization of the pins of the product. Each I/O line of the PIO Controller features: • • • • • • • • An input change interrupt enabling level change detection on any I/O line Rising edge, falling edge, both edge, low-level or high-level detection on any I/O line A glitch filter providing rejection of glitches lower than one-half of PIO clock cycle A debouncing filter providing rejection of unwanted pulses from key or push button operations Multi-drive capability similar to an open drain I/O line Control of the pull-up and pull-down of the I/O line Input visibility and output control Secure or Non-Secure management of the I/O line The PIO Controller also features a synchronous output providing up to 32 bits of data output in a single write operation. 34.2 Embedded Characteristics • Up to 128 Programmable I/O Lines • Multiplexing of up to Seven Peripheral Functions per I/O Line • For each I/O Line (whether assigned to a peripheral or used as general purpose I/O) - Input Change Interrupt - Programmable Glitch Filter - Programmable Debouncing Filter - Multi-drive Option Enables Driving in Open Drain - Programmable Pull-Up/Pull-Down on Each I/O Line - Pin Data Status Register, Supplies Visibility of the Level on the Pin at Any Time - Programmable Event: Rising Edge, Falling Edge, Both edge, Low-Level or High-Level - Configuration Lock by the Connected Peripheral - Security management of each I/O line - Programmable Configuration Lock (Active Until Next VDDCORE Reset) to protect Against Further Software Modifications (intentional or unintentional) • Register Write Protection against unintentional software modifications: - One Configuration Bit to Enable or Disable Protection of I/O Line Settings - One Configuration Bit to Enable or Disable Protection of Interrupt Settings • Synchronous Output, possibility to set or clear simultaneously up to 32 I/O Lines in a Single Write • Programmable Schmitt Trigger Inputs • Programmable I/O Drive  2017 Microchip Technology Inc. DS60001476B-page 437 SAMA5D2 SERIES 34.3 Block Diagram Figure 34-1: Block Diagram APB PIO Controller PIOA Interrupt PIOB Interrupt Interrupts Management PIOC Interrupt Secure Secure Interrupt Controller Non-Secure Interrupt Controller PIOC Interrupt PIOx Interrupt Non-Secure PIOx Interrupt PIOA Interrupt PIOB Interrupt Pads Pads Configuration PMC PIO Clock gpio_inputs PIO Muxing I/O Group 0 PA0 mux _selection PA1 Priority Management PA31 I/O Group 1 PB0 n PB1 1 0 PB31 Input Muxing I/O Group 2 PC0 PC1 gpio_oen gpio_outputs PC31 7 input_data Embedded Peripheral 1 0 I/O Group x Px0 output_data output_enable 8-to-1 Px1 Output Muxing Px31 Note 1: x = 3 (the number of I/O groups is 4) 2: n depends on the number of I/O lines affected to the IP input DS60001476B-page 438  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.4 34.4.1 Product Dependencies Pin Multiplexing Each pin is configurable, depending on the product, as either a general purpose I/O line only, or as an I/O line multiplexed with up to 6 peripheral I/Os. As the multiplexing is hardware defined and thus product-dependent, the hardware designer and programmer must carefully determine the configuration of the PIO Controllers required by their application. When an I/O line is general purpose only, i.e., not multiplexed with any peripheral I/O, programming of the PIO Controller regarding the assignment to a peripheral has no effect and only the PIO Controller can control how the pin is driven by the product. 34.4.2 External Interrupt Lines The interrupt signals FIQ and IRQ0 to IRQn are multiplexed through the PIO Controllers. 34.4.3 Power Management The Power Management Controller (PMC) controls the PIO Controller clock in order to save power. Writing any of the registers of the user interface does not require the PIO Controller clock to be enabled. This means that the configuration of the I/O lines does not require the PIO Controller clock to be enabled. However, when the clock is disabled, not all of the features of the PIO Controller are available, including glitch filtering. Note that the input change interrupt, the interrupt modes on a programmable event and the read of the pin level require the clock to be validated. After a hardware reset, the PIO clock is disabled by default. The user must configure the PMC before any access to the input line information. 34.4.4 Interrupt Generation For interrupt handling, the PIO Controllers are considered as user peripherals. This means that the PIO Controller interrupt lines are connected among the interrupt sources. The PIO Controller supplies one interrupt signal per I/O group. Refer to Table 11-1 “Peripheral Identifiers” to identify the interrupt sources dedicated to the PIO Controller. The PIO Controller can target either the Secure or Non-Secure Interrupt Controller according to security level of the I/O line which triggers the interruption. Using the PIO Controller requires the Interrupt Controller to be programmed first. The PIO Controller interrupt can be generated only if the PIO Controller clock is enabled. 34.5 Functional Description The PIO Controller features up to 512 fully-programmable I/O lines. Most of the control logic associated to each I/O is represented in Figure 34-2 where the I/O line 3 of the PIOB (PB3) is described as an example. In this description each signal shown represents one of up to 512 possible indexes.  2017 Microchip Technology Inc. DS60001476B-page 439 SAMA5D2 SERIES Figure 34-2: I/O Line Control Logic Peripheral G output enable 7 PIO_CFGR1.PUEN Peripheral B output enable 2 Peripheral A output enable 1 PIO_CFGR1.DIR PUEN1_3 Integrated Pull-Up Resistor 0 DIR1_3 0 1 FUNC1_3 PIO_CFGR1.FUNC PIO_CFGR1.OPD OPD1_3 Peripheral G output 7 0 PB3 Peripheral B output 2 Peripheral A output 1 1 0 PIO_SODR1[3] PIO_ODSR1[3] PIO_CODR1[3] PIO_CFGR1.PDEN PDEN1_3 Integrated Pull-Down Resistor GND Pad Input to input muxing PIO_ISR1[0] Not Secure PIOB Interrupt PIO_PDSR1[3] 0 PIO Clock 0 Slow Clock PIO_SCDR Clock Divider PIO_CFGR1.IFSCEN 1 Programmable Glitch or Debouncing Filter D Q DFF EVENT DETECTOR 1 Resynchronization Stage PIO_ISR1[31] Secure Interrupt Management Secure PIOB Interrupt IFSCEN1_3 PIO_CFGR1.IFEN DS60001476B-page 440 PIO_ISR1[3] D Q DFF IFEN1_3  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.5.1 I/O Line Configuration Method The user interface of the PIO Controller provides several sets of registers. Each set of registers interfaces with one I/O group. Table 34-1: 34.5.1.1 I/O Group List I/O Group Number PIO 0 PIOA 1 PIOB ... ... 3 PIOD Security Management First of all, the user must defined the security level of the I/O line. Each I/O line of each I/O group can be defined as either secure or nonsecure lines. Each I/O line of the I/O group x can be set as non-secure I/O line by writing a 1 to the corresponding bit P0–P31 of the Secure PIO Set I/O Non-Secure Register (S_PIO_SIONRx) of the I/O group x. To define an I/O line of I/O group x as a secure I/O line, write a 1 to the corresponding bit P0–P31 of the “Secure PIO Set I/O Secure Register” (S_PIO_SIOSRx) of the I/O group x. Examples: Setting the I/O line PC4 as non-secure line: Write the value 16 (bit No. 4 at 1) at address 0x10B0 (S_PIO_SIONR2) Setting the I/O line PB3 as secure line: Write the value 8 (bit No. 3 at 1) at address 0x1074 (S_PIO_SIOSR1) The security level of each I/O line is reported by the Secure PIO I/O Security Status Register (S_PIO_IOSSRx) of the corresponding I/O group. Reading 0 at the corresponding bit P0–P31 means that the corresponding I/O line of the I/O group is defined as secure. Reading 1 means that this I/O line of the I/O group is non-secure. The PIO Controller user interface is divided into two register mapping areas: • The Non-Secure area, located from address 0x0 to 0x1000, can be accessed by any master (Secure or Non-Secure master). This area interfaces with all the I/O lines defined as non-secure. Trying to access to an I/O line defined as secure through this area will have no effect on I/O line and read values will be 0. • The Secure area, located above address 0x1000, can only be accessed by a Secure master (if the PIO Controller is defined as secure at the HMATRIX level). This area interfaces with all the I/O lines defined as secure. Trying to access to an I/O line defined as non-secure through this area will have no effect on I/O line and read values will be 0. 34.5.1.2 Programming I/O Line Configuration The user must first define which I/O line in the group will be targeted by writing a 1 to the corresponding bit in the PIO Mask Register (PIO_MSKRx). Several I/O lines in an I/O group can be configured at the same time by setting the corresponding bits in PIO_MSKRx. Then, writing the PIO Configuration Register (PIO_CFGRx) apply the configuration to the I/O line(s) defined in PIO_MSKRx. All the I/O lines defined as secure in the S_PIO_SIOSRx must be configured by writing the S_PIO_CFGRx and S_PIO_MSKRx registers. For more details concerning the I/O line configuration using PIO_MSKRx and PIO_CFGRx, see Section 34.6 “I/O Lines Programming Example”. 34.5.1.3 Reading I/O line configuration As for programming operation, reading configuration requires the user to first define which I/O line in the group x will be targeted by writing a 1 to the corresponding bit in the PIO Mask Register (PIO_MSKRx). The value of the targeted I/O line is read in PIO_CFGRx. If several bits are set in PIO_MSKRx, then the read configuration in PIO_CFGRx is the configuration of the I/O line with the lowest index. Note that S_PIO_MSKRx and S_PIO_CFGRx must be used to read the configuration of a secure I/O line. 34.5.2 Pull-up and Pull-down Resistor Control Each I/O line is designed with an embedded pull-up resistor and an embedded pull-down resistor. The pull-up resistor on the I/O line(s) defined in PIO_MSKRx can be enabled by setting the PUEN bit in PIO_CFGRx. Clearing the PUEN bit in PIO_CFGRx disables the pull-up resistor of I/O lines defined in PIO_MSKRx.  2017 Microchip Technology Inc. DS60001476B-page 441 SAMA5D2 SERIES The pull-down resistor on the I/O line(s) defined in PIO_MSKRx can be enabled by setting the PDEN bit in PIO_CFGRx. Clearing the PDEN bit in PIO_CFGRx disables the pull-down resistor of I/O lines defined in PIO_MSKRx. If both PUEN and PDEN bit are set in PIO_CFGRx, only the pull-up resistor is enabled for I/O line(s) defined in PIO_MSKRx and the PDEN bit is discarded. Control of the pull-up resistor is possible regardless of the configuration of the I/O line (Input, Output, Open-drain). Note that S_PIO_MSKRx and S_PIO_CFGRx must be used to program the pull-up or pull-down configuration of a secure I/O line. For more details concerning Pull-up and Pull-down configuration, see Section 34.7.2 “PIO Configuration Register” or Section 34.7.16 “Secure PIO Configuration Register” for secure I/O line configuration. The reset value of PUEN and PDEN bits of each I/O line is defined at the product level and depends on the multiplexing of the device. 34.5.3 General Purpose or Peripheral Function Selection The PIO Controller provides multiplexing of up to 6 peripheral functions on a single pin. The selection is performed by writing the FUNC field in PIO_CFGRx. The selected function is applied to the I/O line(s) defined in PIO_MSKRx. When FUNC is 0, no peripheral is selected and the General Purpose PIO (GPIO) mode is selected (in this mode, the I/O line is controlled by the PIO Controller). When FUNC is not 0, the peripheral selected to control the I/O line depends on the FUNC value. Note that S_PIO_MSKRx and S_PIO_CFGRx must be used to program the FUNC field of a secure I/O line. For more details, see Section 34.7.2 “PIO Configuration Register” or Section 34.7.16 “Secure PIO Configuration Register” for secure I/O line configuration. Note that multiplexing of peripheral lines affects both input and output peripheral lines. When a peripheral is not selected on any I/O line, its inputs are assigned with constant default values defined at the product level. The user must ensure that only one I/O line is affected to a peripheral input at a time. For more details concerning input muxing, see Section 34.5.4 “Output Control”. The reset value of the FUNC field of each I/O line is defined at the product level and depends on the multiplexing of the device. 34.5.4 Output Control When the I/O line is assigned to a peripheral function, i.e., the corresponding FUNC field of the line configuration is not 0, the drive of the I/O line is controlled by the peripheral. According to the FUNC value, the selected peripheral determines whether the pin is driven or not. When the FUNC field of a I/O line is 0, then the I/O line is set in General Purpose mode and the I/O line can be configured to be driven by the PIO Controller instead of the peripheral. If the DIR bit of the I/O line configuration (PIO_CFGRx) is set (OUTPUT) then the I/O line can be driven by the PIO Controller. The level driven on an I/O line can be determined by writing in the PIO Set Output Data Register (PIO_SODRx) and the PIO Clear Output Data Register (PIO_CODRx). These write operations, respectively, set and clear the PIO Output Data Status Register (PIO_ODSRx), which represents the data driven on the I/O lines. Writing PIO_ODSRx directly is possible and only affects the I/O line set to 1 in PIO_MSKRx (see Section 34.5.5 “Synchronous Data Output”). When the DIR bit of the I/O line configuration is at zero, the corresponding I/O line is used as an input only. The DIR bit has no effect if the corresponding line is assigned to a peripheral function, but writing the DIR bit is managed whether the pin is configured to be controlled by the PIO Controller or assigned to a peripheral function. This enables configuration of the I/O line prior to setting it to be managed by the PIO Controller. Similarly, writing in PIO_SODRx and PIO_CODRx affects PIO_ODSRx. This is important as it defines the first level driven on the I/O line. 34.5.5 Synchronous Data Output Clearing one or more PIO line(s) and setting another one or more PIO line(s) synchronously cannot be done by using PIO_SODRx and PIO_CODRx. It requires two successive write operations into two different registers. To overcome this, the PIO Controller offers a direct control of PIO outputs by single write access to PIO_ODSRx. Only I/O lines set to 1 in PIO_MSKRx are written. 34.5.6 Open-Drain Mode Each I/O can be independently programmed in Open-Drain mode. This feature permits several drivers to be connected on the I/O line which is driven low only by each device. An external pull-up resistor (or enabling of the internal one) is generally required to guarantee a high level on the line. The Open-Drain mode is controlled by the OPD bit in the I/O line configuration (PIO_CFGRx). An I/O line is switched in Open-Drain mode by setting the PIO_CFGRx.OPD bit. The Open-Drain mode can be selected if the I/O line is not controlled by a peripheral (the FUNC field must be cleared in PIO_CFGRx). DS60001476B-page 442  2017 Microchip Technology Inc. SAMA5D2 SERIES For more details concerning the Open-Drain mode, see Section 34.7.2 “PIO Configuration Register” or Section 34.7.16 “Secure PIO Configuration Register” for secure I/O line configuration. After reset, the OPD bit of each I/O line is defined at the product level and depends on the multiplexing of the device. 34.5.7 Output Line Timings Figure 34-3 shows how the outputs are driven either by writing PIO_SODRx or PIO_CODRx, or by directly writing PIO_ODSRx. This last case is valid only if the corresponding bit in PIO_MSKRx is set. Figure 34-3 also shows when the feedback in the Pin Data Status Register (PIO_PDSRx) is available. Figure 34-3: Output Line Timings MCK Write PIO_SODRx Write PIO_ODSRx at 1 APB Access Write PIO_CODRx Write PIO_ODSRx at 0 APB Access PIO_ODSRx 2 cycles 2 cycles PIO_PDSRx 34.5.8 Inputs The level on each I/O line of the I/O group x can be read through PIO_PDSRx. This register indicates the level of the I/O lines regardless of their configuration, whether uniquely as an input, or driven by the PIO Controller, or driven by a peripheral. Reading the I/O line levels requires the clock of the PIO Controller to be enabled, otherwise PIO_PDSRx reads the levels present on the I/O line at the time the clock was disabled. 34.5.9 Input Glitch and Debouncing Filters Optional input glitch and debouncing filters are independently programmable on each I/O line. The glitch filter can filter a glitch with a duration of less than 1/2 master clock (MCK) and the debouncing filter can filter a pulse of less than 1/2 period of a programmable divided slow clock. The selection between glitch filtering or debounce filtering is done by writing the bit IFSCEN in the PIO Configuration Register (PIO_CFGRx). The selected filtering mode is applied to the I/O line(s) defined in PIO_MSKRx. • If IFSCEN = 0: The glitch filter can filter a glitch with a duration of less than 1/2 master clock period. • If IFSCEN = 1: The debouncing filter can filter a pulse with a duration of less than 1/2 programmable divided slow clock period. For the debouncing filter, the period of the divided slow clock is performed by writing in the DIV field of the Secure PIO Slow Clock Divider Debouncing Register (S_PIO_SCDR): tdiv_slck = ((DIV + 1) × 2) × tslck. When the glitch or debouncing filter is enabled, a glitch or pulse with a duration of less than 1/2 selected clock cycle (selected clock represents MCK or divided slow clock depending on IFSCEN bit programming) is automatically rejected, while a pulse with a duration of one selected clock (MCK or divided slow clock) cycle or more is accepted. For pulse durations between 1/2 selected clock cycle and one selected clock cycle, the pulse may or may not be taken into account, depending on the precise timing of its occurrence. Thus for a pulse to be visible, it must exceed one selected clock cycle, whereas for a glitch to be reliably filtered out, its duration must not exceed 1/2 selected clock cycle. The filters also introduce some latencies, illustrated in Figure 34-4 and Figure 34-5. The glitch filter of each I/O lines is controlled by the IFEN bit of the PIO Configuration Register (PIO_CFGRx). Setting the PIO_CFGRx.IFEN bit enables the glitch filter of the I/O line(s) defined in PIO_MSKRx.  2017 Microchip Technology Inc. DS60001476B-page 443 SAMA5D2 SERIES When the glitch and/or debouncing filter is enabled, it does not modify the behavior of the inputs on the peripherals. It acts only on the value read in PIO_PDSRx and on the input change interrupt detection. The glitch and debouncing filters require that the PIO Controller clock is enabled. Figure 34-4: Input Glitch Filter Timing PIO_CFGRx.IFCSENy(1) = 0 MCK up to 1.5 cycles Pin Level 1 cycle 1 cycle 1 cycle 1 cycle PIO_PDSRx[y](2) if PIO_CFGRx.IFENy(3) = 0 2 cycles up to 2 cycles if PIO_CFGRx.IFENy(3) = 1 Figure 34-5: 1 cycle up to 2.5 cycles PIO_PDSRx[y](2) Input Debouncing Filter Timing PIO_CFGRx.IFSCENy(1) = 1 Divided Slow Clock Pin Level up to 2 cycles Tmck up to 2 cycles Tmck PIO_PDSRx[y](2) if PIO_CFGRx.IFENy(3) = 0 1 cycle Tdiv_slclk (2) PIO_PDSRx[y] 1 cycle Tdiv_slclk up to 1.5 cycles Tdiv_slclk if PIO_CFGRx.IFENy(3) = 1 up to 1.5 cycles Tdiv_slclk up to 2 cycles Tmck up to 2 cycles Tmck Note 1: Means IFCSEN bit of the I/O line y of the I/O group x 2: Means PIO Data Status value of the I/O line y of the I/O group x 3: Means IFEN bit of the I/O line y of the I/O group x 34.5.10 Input Edge/Level Interrupt Each I/O group can be programmed to generate an interrupt when it detects an edge or a level on an I/O line. The Input Edge/Level interrupts are controlled by writing the PIO Interrupt Enable Register (PIO_IERx) and the PIO Interrupt Disable Register (PIO_IDRx), which enable and disable the input change interrupt respectively by setting and clearing the corresponding bit in the PIO Interrupt Mask Register (PIO_IMRx). For the Secure I/O lines, the Input Edge/Level interrupts are controlled by writing S_PIO_IERx and S_PIO_IDRx, which enable and disable input change interrupts respectively by setting and clearing the corresponding bit in the S_PIO_IMRx. As input change detection is possible only by comparing two successive samplings of the input of the I/O line, the PIO Controller clock must be enabled. The Input Change interrupt is available regardless of the configuration of the I/O line, i.e., configured as an input only, controlled by the PIO Controller or assigned to a peripheral function. Each I/O group can generate a Non-Secure interrupt and a Secure interrupt according to the security level of the I/O line which triggers the interrupt. According to the EVTSEL field value in the PIO Configuration Register (PIO_CFGRx) or the Secure PIO Configuration Register (S_PIO_CFGRx) in case of a Secure I/O line, the interrupt signal of the I/O group x can be generated on the following occurrence: • (S_)PIO_CFGRx.EVTSELy = 0: The interrupt signal of the I/O group x is generated on the I/O line y falling edge detection (assuming that (S_)PIO_IMRx[y] = 1). DS60001476B-page 444  2017 Microchip Technology Inc. SAMA5D2 SERIES • (S_)PIO_CFGRx.EVTSELy = 1: The interrupt signal of the I/O group x is generated on the I/O line y rising edge detection (assuming that (S_)PIO_IMRx[y] = 1). • (S_)PIO_CFGRx.EVTSELy = 2: The interrupt signal of the I/O group x is generated on the I/O line y both rising and falling edge detection (assuming that (S_)PIO_IMRx[y] = 1). • (S_)PIO_CFGRx.EVTSELy = 3: The interrupt signal of the I/O group x is generated on the I/O line y low level detection (assuming that (S_)PIO_IMRx[y] = 1). • (S_)PIO_CFGRx.EVTSELy = 4: The interrupt signal of the I/O group x is generated on the I/O line y high level detection (assuming that (S_)PIO_IMRx[y] = 1). By default, the interrupt can be generated at any time a falling edge is detected on the input. When an input edge or level is detected on an I/O line, the corresponding bit in the PIO Interrupt Status Register (PIO_ISRx), or in the Secure PIO Interrupt Status Register (S_PIO_ISRx) if the I/O line is Secure, is set. For a Non-Secure I/O line, if the corresponding bit in PIO_IMRx is set, the PIO Controller Non-Secure interrupt line of the I/O group x is asserted. For a Secure I/O line, if the corresponding bit in S_PIO_IMRx is set, the PIO Controller Secure interrupt line of the I/O group x is asserted. When the software reads PIO_ISRx, all the Non-Secure interrupts of the I/O group x are automatically cleared. When the software reads S_PIO_ISRx, all the Secure interrupts of the I/O group x are automatically cleared. This signifies that all the interrupts that are pending when PIO_ISRx or S_PIO_ISRx is read must be handled. When an Interrupt is enabled on a “level”, the interrupt is generated as long as the interrupt source is not cleared, even if some read accesses in PIO_ISRx or S_PIO_ISRx are performed. Figure 34-6: Event Detector on Input Lines High Level Detector Low Level Detector Resynchronized input on line y of I/O group x 4 3 Both Edge Detector 2 Rising Edge Detector 0 Event detection on line y of the I/O group x 1 Falling Edge Detector PIO_CFGRx.EVTSELy Example of interrupt generation on following lines: • • • • • • • • • Rising edge on the Secure PIO line 0 of the I/O group 0 (PIOA) Low-level edge on the Secure PIO line 1of the I/O group 0 (PIOA) Rising edge on the Secure PIO line 2 of the I/O group 0 (PIOA) High-level on the Secure PIO line 3 of the I/O group 0 (PIOA) Low-level on the Non-Secure PIO line 4 of the I/O group 0 (PIOA) High-level on the Secure PIO line 0 of the I/O group 1 (PIOB) Falling edge on the Secure PIO line 1 of the I/O group 1 (PIOB) Rising edge on the Secure PIO line 2 of the I/O group 1 (PIOB) Any edge on the other Non-Secure lines of the I/O group 1 (PIOB) Table 34-2 details the required configuration for this example. Table 34-2: Configuration for Example Interrupt Generation Configuration PIOA: I/O line security level PIOA: Interrupt Mode Name Define the I/O lines 0 to 3 of the PIOA as Secure by writing 32’h0000_000F in the S_PIO_SIOSR0 (offset 0x1034) Define the I/O lines 4 of the PIOA as Non-Secure by writing 32’h0000_0010 in the S_PIO_SIONR0 (offset 0x1030) Enable interrupt sources for lines 0 to 3 of PIOA by writing 32’h0000_000F in S_PIO_IER0 (offset 0x1020) Enable interrupt source for the line 4 of PIOA by writing 32’h0000_0010 in PIO_IER0 (offset 0x20)  2017 Microchip Technology Inc. DS60001476B-page 445 SAMA5D2 SERIES Table 34-2: Configuration for Example Interrupt Generation (Continued) Configuration Name Configure Rising Edge detection for Secure lines 0 and 2: Write 32’h0000_0005 in S_PIO_MSKR0 (offset 0x1000) Write 32’h0100_0000 in S_PIO_CFGR0 (offset 0x1004) Configure Low Level detection for Secure line 1: Write 32’h0000_0002 in S_PIO_MSKR0 (offset 0x1000) Write 32’h0300_0000 in S_PIO_CFGR0 (offset 0x1004) PIOA: Event Selection Configure High Level detection for Secure line 3: Write 32’h0000_0008 in S_PIO_MSKR0 (offset 0x1000) Write 32’h0400_0000 in S_PIO_CFGR0 (offset 0x1004) Configure Low Level detection for Non-Secure line 4: Write 32’h0000_0010 in PIO_MSKR0 (offset 0x0) Write 32’h0300_0000 in PIO_CFGR0 (offset 0x4) PIOB: I/O line security level PIOB: Interrupt Mode Define the I/O lines 0 to 2 of the PIOB as Secure by writing 32’h0000_0007 in the S_PIO_SIOSR1 (offset 0x1074) Define the other I/O lines of the PIOB as Non-Secure by writing 32’hFFFF_FFF8 in the S_PIO_SIONR1 (offset 0x1070) Enable interrupt sources for lines 0 to 2 of PIOB by writing 32’h0000_0007 in S_PIO_IER1 (offset 0x1060) Enable interrupt sources for all other lines of PIOB by writing 32’hFFFF_FFF8 in PIO_IER1 (offset 0x60) Configure High Level detection for Secure line 0: Write 32’h0000_0001 in S_PIO_MSKR1 (offset 0x1040) Write 32’h0400_0000 in S_PIO_CFGR1 (offset 0x1044) Configure Falling Edge detection for Secure line 1: Write 32’h0000_0002 in S_PIO_MSKR1 (offset 0x1040) Write 32’h0000_0000 in S_PIO_CFGR1 (offset 0x1044) PIOB: Event Selection Configure Rising Edge detection for Secure line 2: Write 32’h0000_0004 in S_PIO_MSKR1 (offset 0x1040) Write 32’h0100_000 in S_PIO_CFGR1 (offset 0x1044) Configure Low Level detection for Non-Secure lines: Write 32’hFFFF_FFF8 in PIO_MSKR1 (offset 0x40) Write 32’h0200_000 in PIO_CFGR1 (offset 0x44) DS60001476B-page 446  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 34-7: Input Change Interrupt Timings When No Additional Interrupt Modes MCK Pin Level PIO_ISRx Read PIO_ISRx 34.5.11 APB Access APB Access Interrupt Management The PIO Controller can drive one secure interrupt signal and one non-secure interrupt signal per I/O group (see Figure 34-1). Secure interrupt signals are connected to the secure interrupt controller of the system. Non-secure interrupt signals are connected to the non-secure interrupt controller of the system. Figure 34-8: PIO Interrupt Management PIO_ISRx[0] PIO_IERx[0] PIO_IMRx[0] PIO_IDRx[0] (Up to 32 possible inputs) Non-Secure PIOx Interrupt PIO_ISRx[31] PIO_IERx[31] PIO_IMRx[31] PIO_IDRx[31] S_PIO_ISRx[0] S_PIO_IERx[0] S_PIO_IMRx[0] S_PIO_IDRx[0] (Up to 32 possible inputs) Secure PIOx Interrupt S_PIO_ISRx[31] S_PIO_IERx[31] S_PIO_IMRx[31] S_PIO_IDRx[31]  2017 Microchip Technology Inc. DS60001476B-page 447 SAMA5D2 SERIES 34.5.12 I/O Lines Lock When an I/O line is controlled by a peripheral (particularly the Pulse Width Modulation Controller PWM), it can become locked by the action of this peripheral via an input of the PIO Controller. When an I/O line is locked, the following fields in PIO_CFGRx are locked and cannot be modified: • • • • FUNC: Peripheral selection cannot be changed when the corresponding I/O line is locked. PUEN: Pull-Up configuration cannot be changed when the corresponding I/O line is locked. PDEN: Pull-Down configuration cannot be changed when the corresponding I/O line is locked. OPD: Open Drain configuration cannot be changed when the corresponding I/O line is locked. Writing to one of these fields while the corresponding I/O line is locked will have no effect. The user can know at anytime which I/O line is locked by reading the PIO Lock Status Register (PIO_LOCKSR) or Secure PIO Lock Status Register (S_PIO_LOCKSR) for locked Secure I/O lines. Once an I/O line is locked, the only way to unlock it is to apply a hardware reset to the PIO Controller. 34.5.13 Programmable I/O Drive It is possible to configure the I/O drive for pads PA0 to PD31. The I/O drive of the pad can be programmed by writing the DRVSTR field in the PIO Configuration Register (PIO_CFGRx) if the corresponding line is Non-Secure or the Secure PIO Configuration Register (S_PIO_CFGRx) if the I/O line is Secure. For details, refer to Section 66. “Electrical Characteristics”. 34.5.14 Programmable Schmitt Trigger It is possible to configure each input for the Schmitt trigger. The Schmitt trigger can be enabled by setting the SCHMITT bit of the PIO Configuration Register (PIO_CFGRx) if the corresponding line is Non-Secure or the Secure PIO Configuration Register (S_PIO_CFGRx) if the I/O line is Secure. By default the Schmitt trigger is active. Disabling the Schmitt trigger is requested when using the QTouch® Library. 34.5.15 34.5.15.1 I/O Line Configuration Freeze Software Freeze Once the I/O line configuration is done, it can be frozen by using the PIO I/O Freeze Configuration Register (PIO_IOFRx) of the corresponding group or the Secure PIO I/O Freeze Configuration Register (S_PIO_IOFRx) if the I/O line is Secure. • Physical Freeze Setting the FPHY bit of PIO_IOFRx freezes the following fields of the Non-Secure I/O lines defined in PIO_MSKRx: • • • • • • • FUNC: I/O Line Function DIR: Direction PUEN: Pull-Up Enable PDEN: Pull-Down Enable OPD: Open-Drain SCHMITT: Schmitt Trigger DRVSTR: Drive Strength For Secure I/O lines, use the FPHY bit of the S_PIO_IOFRx and the S_PIO_MSKRx to freeze the fields above. When the physical freeze is currently active on an I/O line, the PCFS flag is set when reading the PIO_CFGRx of the I/O line (or the S_PIO_CFGRx if the I/O line is Secure). Only a hardware reset can release fields listed above. • Interrupt Freeze Setting the FINT bit of the PIO_IOFRx will freeze the following fields of the Non-Secure I/O lines defined in the PIO_MSKRx: • IFEN: Input Filter Enable • IFSCEN: Input Filter Slow Clock Enable • EVTSEL: Event Selection For Secure I/O lines, use the FINT bit of the S_PIO_IOFRx and the S_PIO_MSKRx to freeze the fields above. When the “Interrupt Freeze” is currently active on an I/O line, the ICFS flag is set when reading the PIO_CFGRx of the I/O line (or the S_PIO_CFGRx if the I/O line is Secure). Only a hardware reset can release fields listed above. DS60001476B-page 448  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.5.16 Register Write Protection To prevent any single software error from corrupting PIO behavior, certain registers in the address space can be write-protected by setting bit WPEN in the PIO Write Protection Mode Register (PIO_WPMR) or the Secure PIO Write Protection Mode Register (S_PIO_WPMR). If a write access to a Non-Secure write-protected register is detected, the WPVS flag in the PIO Write Protection Status Register (PIO_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. If a write access to a Secure write-protected register is detected, the WPVS flag in the Secure PIO Write Protection Status Register (S_PIO_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The respective WPVS bit is automatically cleared after reading the PIO_WPSR or S_PIO_WPSR. The following registers are write-protected when WPEN is set in PIO_WPMR: • PIO Mask Register • PIO Configuration Register The following registers are write-protected when WPEN is set in S_PIO_WPMR: • Secure PIO Mask Register • Secure PIO Configuration Register • Secure PIO Slow Clock Divider Debouncing Register 34.6 I/O Lines Programming Example The programming example shown in Table 34-3 is used to obtain the following configurations: • PIOA Configuration: - 4-bit output port on Secure I/O lines 0 to 3, open-drain, with pull-up resistor - Four output signals on Non-Secure I/O lines 4 to 7 (to drive LEDs for example), driven high and low, no pull-up resistor, no pulldown resistor - Secure I/O lines 16 to 19 assigned to peripheral A functions with pull-up resistor - Non-Secure I/O lines 20 to 23 assigned to peripheral B functions with pull-down resistor • PIOB Configuration: - Four input signals on Secure I/O lines 0 to 3 (to read push-button states for example), with pull-up resistors, glitch filters and input change interrupts - Four input signals on Non-Secure I/O lines 12 to 15 to read an external device status (polled, thus no input change interrupt), no pull-up resistor, no glitch filter - Secure I/O lines 16 to 23 assigned to peripheral B functions with pull-down resistor - Non-Secure I/O lines 24 to 27 assigned to peripheral D with Input Change Interrupt, no pull-up resistor and no pull-down resistor Table 34-3: Programming Example Action PIOA: Set I/O lines 0 to 3 and 16 to 19 as Secure PIOA: Set I/O lines 4 to 7 and 20 to 23 as Non-Secure Register S_PIO_SIOSR0 (offset 0x1034) S_PIO_SIONR0 (offset 0x1030) S_PIO_MSKR0 (offset 0x1000) Value to be Written 0x000F_000F 0x00F0_00F0 0x0000_000F PIOA: 4-bit output port on Secure I/O lines 0 to 3, open-drain, with pull-up resistor S_PIO_CFGR0 (offset 0x1004) PIO_MSKR0 PIOA: Four output signals on Non-Secure I/O lines 4 to 7 (to drive LEDs for example), driven high and low, no pull-up resistor, no pull-down resistor (offset 0x0) PIO_CFGR0 (offset 0x4)  2017 Microchip Technology Inc. 0x0000_4300 0x0000_00F0 0x0000_0100 DS60001476B-page 449 SAMA5D2 SERIES Table 34-3: Programming Example (Continued) Action Register S_PIO_MSKR0 (offset 0x1000) Value to be Written 0x000F_0000 PIOA: Secure I/O lines 16 to 19 assigned to peripheral A functions with pull-up resistor S_PIO_CFGR0 (offset 0x1004) PIO_MSKR0 PIOA: Non-Secure I/O lines 20 to 23 assigned to peripheral B functions with pull-down resistor (offset 0x0) PIO_CFGR0 (offset 0x4) PIOB: Set I/O lines 0 to 3 and 16 to 23as Secure PIOB: Set I/O lines 12 to 15 and 24 to 27 as Non-Secure S_PIO_SIOSR1 (offset 0x1074) S_PIO_SIONR1 (offset 0x1070) S_PIO_MSKR1 PIOB: Four input signals on Secure I/O lines 0 to 3 (to read push-button states for example), with pull-up resistors, glitch filters and interrupts on rising edge (offset 0x1040) S_PIO_CFGR1 (offset 0x1044) PIO_MSKR1 PIOB: Four input signals on Non-Secure I/O line 12 to 15 to read an external device status (polled, thus no input change interrupt), no pull-up resistor, no glitch filter (offset 0x40) PIO_CFGR1 (offset 0x44) S_PIO_MSKR1 (offset 0x1040) 0x0000_0201 0x00F0_0000 0x0000_0402 0x00FF_000F 0x0F00_F000 0x0000_000F 0x0100_1200 0x0000_F000 0x0100_1200 0x00FF_0000 PIOB: Secure I/O lines 16 to 23 assigned to peripheral B functions with pull-down resistor S_PIO_CFGR1 (offset 0x1044) PIO_MSKR1 PIOB: Non-Secure I/O line 24 to 27 assigned to peripheral D with Input Interrupt on both edges, no pull-up resistor and no pull-down resistor (offset 0x40) PIO_CFGR1 (offset 0x44) S_PIO_IER1 (offset 0x1060) 0x0000_0402 0x0F00_0000 0x0200_0004 0x0000_000F PIOB: Enable interrupt PIO_IER1 (offset 0x60) DS60001476B-page 450 0x0F00_0000  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7 Parallel Input/Output Controller (PIO) User Interface Each I/O line controlled by the PIO Controller is associated with a bit in each of the PIO Controller User Interface registers. Each register is 32 bits wide. If a parallel I/O line is not defined, writing to the corresponding bits has no effect. Undefined bits read zero. Table 34-4: Register Mapping (3)(4) Offset Register Name Access Reset 0x000 + (io_group * 0x40) + 0x00 PIO Mask Register PIO_MSKR Read/Write 0x00000000 0x000 + (io_group * 0x40) + 0x04 PIO Configuration Register PIO_CFGR Read/Write 0x00000200 0x000 + (io_group * 0x40) + 0x08 PIO Pin Data Status Register PIO_PDSR Read-only (1) 0x000 + (io_group * 0x40) + 0x0C PIO Lock Status Register PIO_LOCKSR Read-only 0x00000000 0x000 + (io_group * 0x40) + 0x10 PIO Set Output Data Register PIO_SODR Write-only – 0x000 + (io_group * 0x40) + 0x14 PIO Clear Output Data Register PIO_CODR Write-only – 0x000 + (io_group * 0x40) + 0x18 PIO Output Data Status Register PIO_ODSR Read/Write 0x00000000 0x000 + (io_group * 0x40) + 0x1C Reserved – – – 0x000 + (io_group * 0x40) + 0x20 PIO Interrupt Enable Register PIO_IER Write-only – 0x000 + (io_group * 0x40) + 0x24 PIO Interrupt Disable Register PIO_IDR Write-only – 0x000 + (io_group * 0x40) + 0x28 PIO Interrupt Mask Register PIO_IMR Read-only 0x00000000 0x000 + (io_group * 0x40) + 0x2C PIO Interrupt Status Register(2) PIO_ISR Read-only 0x00000000 0x000 + (io_group * 0x40) + 0x30 Reserved – – – 0x000 + (io_group * 0x40) + 0x34 Reserved – – – 0x000 + (io_group * 0x40) + 0x38 Reserved – – – 0x000 + (io_group * 0x40) + 0x3C PIO I/O Freeze Configuration Register PIO_IOFR Write-only – 0x400–0x4FC Reserved – – – 0x500 Reserved – – – 0x5D0 Reserved – – – 0x5D4 Reserved – – – 0x5E0 PIO Write Protection Mode Register PIO_WPMR Read/Write 0x00000000 0x5E4 PIO Write Protection Status Register PIO_WPSR Read-only 0x00000000 0x5E8–0x5FC Reserved – – – 0x1000 + (io_group * 0x40) + 0x00 Secure PIO Mask Register S_PIO_MSKR Read/Write 0x00000000  2017 Microchip Technology Inc. DS60001476B-page 451 SAMA5D2 SERIES Table 34-4: Register Mapping (Continued) (3)(4) Offset Register Name Access Reset 0x1000 + (io_group * 0x40) + 0x04 Secure PIO Configuration Register S_PIO_CFGR Read/Write 0x00000200 0x1000 + (io_group * 0x40) + 0x08 Secure PIO Pin Data Status Register S_PIO_PDSR Read-only (1) 0x1000 + (io_group * 0x40) + 0x0C Secure PIO Lock Status Register S_PIO_LOCKSR Read-only 0x00000000 0x1000 + (io_group * 0x40) + 0x10 Secure PIO Set Output Data Register S_PIO_SODR Write-only – 0x1000 + (io_group * 0x40) + 0x14 Secure PIO Clear Output Data Register S_PIO_CODR Write-only – 0x1000 + (io_group * 0x40) +0x18 Secure PIO Output Data Status Register S_PIO_ODSR Read/Write 0x00000000 0x1000 + (io_group * 0x40) + 0x1C Reserved – – – 0x1000 + (io_group * 0x40) + 0x20 Secure PIO Interrupt Enable Register S_PIO_IER Write-only – 0x1000 + (io_group * 0x40) + 0x24 Secure PIO Interrupt Disable Register S_PIO_IDR Write-only – 0x1000 + (io_group * 0x40) + 0x28 Secure PIO Interrupt Mask Register S_PIO_IMR Read-only 0x00000000 0x1000 + (io_group * 0x40) + 0x2C Secure PIO Interrupt Status Register(2) S_PIO_ISR Read-only 0x00000000 0x1000 + (io_group * 0x40) + 0x30 Secure PIO Set I/O Non-Secure Register S_PIO_SIONR Write-only – 0x1000 + (io_group * 0x40) + 0x34 Secure PIO Set I/O Secure Register S_PIO_SIOSR Write-only – 0x1000 + (io_group * 0x40) + 0x38 Secure PIO I/O Security Status Register S_PIO_IOSSR Read-only 0x00000000 0x1000 + (io_group * 0x40) + 0x3C Secure PIO I/O Freeze Configuration Register S_PIO_IOFR Write-only – 0x1400–0x14FC Reserved – – – 0x1500 Secure PIO Slow Clock Divider Debouncing Register S_PIO_SCDR Read/Write 0x00000000 0x15D0 Reserved – – – 0x15D4 Reserved – – – 0x15E0 Secure PIO Write Protection Mode Register S_PIO_WPMR Read/Write 0x00000000 0x15E4 Secure PIO Write Protection Status Register S_PIO_WPSR Read-only 0x00000000 Note 1: Reset value of PIO_PDSR and S_PIO_PDSR depend on the level of the I/O lines. Reading the I/O line levels requires the clock of the PIO Controller to be enabled, otherwise PIO_PDSR reads the levels present on the I/O line at the time the clock was disabled. 2: PIO_ISR and S_PIO_ISR are reset at 0x0. However, the first read of the register may read a different value as input changes may have occurred. 3: If an offset is not listed in the table it must be considered as reserved. 4: Some registers are indexed with “io_group” index ranging from 0 to 3. DS60001476B-page 452  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.1 PIO Mask Register Name: PIO_MSKRx [x=0..3] Address: 0xFC038000 [0], 0xFC038040 [1], 0xFC038080 [2], 0xFC0380C0 [3] Access: Read/Write 31 30 29 28 27 26 25 24 MSK31 MSK30 MSK29 MSK28 MSK27 MSK26 MSK25 MSK24 23 22 21 20 19 18 17 16 MSK23 MSK22 MSK21 MSK20 MSK19 MSK18 MSK17 MSK16 15 14 13 12 11 10 9 8 MSK15 MSK14 MSK13 MSK12 MSK11 MSK10 MSK9 MSK8 7 6 5 4 3 2 1 0 MSK7 MSK6 MSK5 MSK4 MSK3 MSK2 MSK1 MSK0 This register can only be written if the WPEN bit is cleared in the PIO Write Protection Mode Register. MSKy: PIO Line y Mask These bits define the I/O lines to be configured when writing the PIO Configuration Register. 0 (DISABLED): Writing the PIO_CFGRx, PIO_ODSRx or PIO_IOFRx does not affect the corresponding I/O line configuration. 1 (ENABLED): Writing the PIO_CFGRx, PIO_ODSRx or PIO_IOFRx updates the corresponding I/O line configuration.  2017 Microchip Technology Inc. DS60001476B-page 453 SAMA5D2 SERIES 34.7.2 PIO Configuration Register Name: PIO_CFGRx [x=0..3] Address: 0xFC038004 [0], 0xFC038044 [1], 0xFC038084 [2], 0xFC0380C4 [3] Access: Read/Write 31 30 29 28 – ICFS PCFS – 27 26 23 22 21 20 19 18 – – – – – – 25 24 EVTSEL 17 16 DRVSTR 15 14 13 12 11 10 9 8 SCHMITT OPD IFSCEN IFEN – PDEN PUEN DIR 2 1 0 7 6 5 4 3 – – – – – FUNC This register can only be written if the WPEN bit is cleared in the PIO Write Protection Mode Register. Writing this register will only affect I/O lines enabled in the PIO_MSKRx. FUNC: I/O Line Function This field defines the function for I/O lines of the I/O group x according to the PIO Mask Register. Value Name Description 0 GPIO Select the PIO mode for the selected I/O lines. 1 PERIPH_A Select the peripheral A for the selected I/O lines. 2 PERIPH_B Select the peripheral B for the selected I/O lines. 3 PERIPH_C Select the peripheral C for the selected I/O lines. 4 PERIPH_D Select the peripheral D for the selected I/O lines. 5 PERIPH_E Select the peripheral E for the selected I/O lines. 6 PERIPH_F Select the peripheral F for the selected I/O lines. 7 PERIPH_G Select the peripheral G for the selected I/O lines. DIR: Direction This bit defines the direction of the I/O lines of the I/O group x according to the PIO Mask Register. 0 (INPUT): The selected I/O lines are pure inputs. 1 (OUTPUT): The selected I/O lines are enabled in output. PUEN: Pull-Up Enable This bit defines the pull-up configuration of the I/O lines of the I/O group x according to the PIO Mask Register. 0 (DISABLED): Pull-Up is disabled for the selected I/O lines. 1 (ENABLED): Pull-Up is enabled for the selected I/O lines. PDEN: Pull-Down Enable This bit defines the pull-down configuration of the I/O lines of the I/O group x according to the PIO Mask Register. 0 (DISABLED): Pull-Down is disabled for the selected I/O lines. 1 (ENABLED): Pull-Down is enabled for the selected I/O lines only if PUEN is 0(1). Note 1: PDEN can be written to 1 only if PUEN is written to 0. IFEN: Input Filter Enable This bit defines if the glitch filtering is used for the I/O lines of the I/O group x according to the PIO Mask Register. DS60001476B-page 454  2017 Microchip Technology Inc. SAMA5D2 SERIES 0 (DISABLED): The input filter is disabled for the selected I/O lines. 1 (ENABLED): The input filter is enabled for the selected I/O lines. IFSCEN: Input Filter Slow Clock Enable This bit defines the clock source of the glitch filtering for the I/O lines of the I/O group x according to the PIO Mask Register. 0 (DISABLED): The glitch filter is able to filter glitches with a duration < tmck/2 for the selected I/O lines. 1 (ENABLED): The debouncing filter is able to filter pulses with a duration < tdiv_slck/2 for the selected I/O lines. OPD: Open-Drain This bit defines the open drain configuration of the I/O lines of the I/O group x according to the PIO Mask Register. 0 (DISABLED): The open-drain is disabled for the selected I/O lines. I/O lines are driven at high- and low-level. 1 (ENABLED): The open-drain is enabled for the selected I/O lines. I/O lines are driven at low-level only. SCHMITT: Schmitt Trigger This bit defines the Schmitt trigger configuration of the I/O lines of the I/O group x according to the PIO Mask Register. 0 (ENABLED): Schmitt trigger is enabled for the selected I/O lines. 1 (DISABLED): Schmitt trigger is disabled for the selected I/O lines. DRVSTR: Drive Strength This field defines the drive strength of the I/O lines of the I/O group x according to the PIO Mask Register. Value Name Description 0 LO Low drive 1 LO Low drive 2 ME Medium drive 3 HI High drive EVTSEL: Event Selection This field defines the type of event to detect on the I/O lines of the I/O group x according to the PIO Mask Register. Value Name Description 0 FALLING Event detection on input falling edge 1 RISING Event detection on input rising edge 2 BOTH Event detection on input both edge 3 LOW Event detection on low level input 4 HIGH Event detection on high level input 5 – Reserved 6 – Reserved 7 – Reserved PCFS: Physical Configuration Freeze Status (read-only) This bit gives information about the freeze state of the following fields of the read I/O line configuration: • FUNC: I/O Line Function • DIR: Direction • PUEN: Pull-Up Enable • PDEN: Pull-Down Enable • OPD: Open-Drain  2017 Microchip Technology Inc. DS60001476B-page 455 SAMA5D2 SERIES • SCHMITT: Schmitt Trigger • DRVSTR: Drive Strength 0 (NOT_FROZEN): The fields are not frozen and can be written for this I/O line. 1 (FROZEN): The fields are frozen and cannot be written for this I/O line. Only a hardware reset can release these fields. ICFS: Interrupt Configuration Freeze Status (read-only) This bit gives information about the freeze state of the following fields of the read I/O line configuration: • IFEN: Input Filter Enable • IFSCEN: Input Filter Slow Clock Enable • EVTSEL: Event Selection 0 (NOT_FROZEN): The fields are not frozen and can be written for this I/O line. 1 (FROZEN): The fields are frozen and cannot be written for this I/O line. Only a hardware reset can release these fields. DS60001476B-page 456  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.3 PIO Pin Data Status Register Name: PIO_PDSRx [x=0..3] Address: 0xFC038008 [0], 0xFC038048 [1], 0xFC038088 [2], 0xFC0380C8 [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Data Status 0: The I/O line of the I/O group x is at level 0. 1: The I/O line of the I/O group x is at level 1.  2017 Microchip Technology Inc. DS60001476B-page 457 SAMA5D2 SERIES 34.7.4 PIO Lock Status Register Name: PIO_LOCKSRx [x=0..3] Address: 0xFC03800C [0], 0xFC03804C [1], 0xFC03808C [2], 0xFC0380CC [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Lock Status 0: The I/O line of the I/O group x is not locked. 1: The I/O line of the I/O group x is locked. DS60001476B-page 458  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.5 PIO Set Output Data Register Name: PIO_SODRx [x=0..3] Address: 0xFC038010 [0], 0xFC038050 [1], 0xFC038090 [2], 0xFC0380D0 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Set Output Data 0: No effect. 1: Sets the data to be driven on the I/O line of I/O group x.  2017 Microchip Technology Inc. DS60001476B-page 459 SAMA5D2 SERIES 34.7.6 PIO Clear Output Data Register Name: PIO_CODRx [x=0..3] Address: 0xFC038014 [0], 0xFC038054 [1], 0xFC038094 [2], 0xFC0380D4 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Clear Output Data 0: No effect. 1: Clears the data to be driven on the I/O line of the I/O group x. DS60001476B-page 460  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.7 PIO Output Data Status Register Name: PIO_ODSRx [x=0..3] Address: 0xFC038018 [0], 0xFC038058 [1], 0xFC038098 [2], 0xFC0380D8 [3] Access: Read/Write 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 Writing this register will only affect I/O lines enabled in the PIO_MSKRx. P0–P31: Output Data Status 0: The data to be driven on the I/O line of the I/O group x is 0. 1: The data to be driven on the I/O line of the I/O group x is 1.  2017 Microchip Technology Inc. DS60001476B-page 461 SAMA5D2 SERIES 34.7.8 PIO Interrupt Enable Register Name: PIO_IERx [x=0..3] Address: 0xFC038020 [0], 0xFC038060 [1], 0xFC0380A0 [2], 0xFC0380E0 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Enable 0: No effect. 1: Enables the Input Change interrupt on the I/O line of the I/O group x. DS60001476B-page 462  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.9 PIO Interrupt Disable Register Name: PIO_IDRx [x=0..3] Address: 0xFC038024 [0], 0xFC038064 [1], 0xFC0380A4 [2], 0xFC0380E4 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Disable 0: No effect. 1: Disables the Input Change interrupt on the I/O line of the I/O group x.  2017 Microchip Technology Inc. DS60001476B-page 463 SAMA5D2 SERIES 34.7.10 PIO Interrupt Mask Register Name: PIO_IMRx [x=0..3] Address: 0xFC038028 [0], 0xFC038068 [1], 0xFC0380A8 [2], 0xFC0380E8 [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Mask 0: Input Change interrupt is disabled on the I/O line of the I/O group x. 1: Input Change interrupt is enabled on the I/O line of the I/O group x. DS60001476B-page 464  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.11 PIO Interrupt Status Register Name: PIO_ISRx [x=0..3] Address: 0xFC03802C [0], 0xFC03806C [1], 0xFC0380AC [2], 0xFC0380EC [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Status 0: No Input Change has been detected on the I/O line of the I/O group x since PIO_ISRx was last read or since reset. 1: At least one Input Change has been detected on the I/O line of the I/O group since PIO_ISRx was last read or since reset.  2017 Microchip Technology Inc. DS60001476B-page 465 SAMA5D2 SERIES 34.7.12 PIO I/O Freeze Configuration Register Name: PIO_IOFRx [x=0..3] Address: 0xFC03803C [0], 0xFC03807C [1], 0xFC0380BC [2], 0xFC0380FC [3] Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 FRZKEY 23 22 21 20 FRZKEY 15 14 13 12 FRZKEY 7 6 5 4 3 2 1 0 – – – – – – FINT FPHY Writing this register will only affect I/O lines enabled in the PIO_MSKRx. FPHY: Freeze Physical Configuration 0: No effect. 1: Freezes the following configuration fields of Non-Secure I/O lines if FRZKEY corresponds to 0x494F46 (“IOF” in ASCII): • FUNC: I/O Line Function • DIR: Direction • PUEN: Pull-Up Enable • PDEN: Pull-Down Enable • OPD: Open-Drain • SCHMITT: Schmitt Trigger • DRVSTR: Drive Strength Only a hardware reset can reset the FPHY bit. FINT: Freeze Interrupt Configuration 0: No effect. 1: Freezes the following configuration fields of Non-Secure I/O lines if FRZKEY corresponds to 0x494F46 (“IOF” in ASCII): • IFEN: Input Filter Enable • IFSCEN: Input Filter Slow Clock Enable • EVTSEL: Event Selection Only a hardware reset can reset the FINT bit. FRZKEY: Freeze Key Value Name 0x494F46 PASSWD DS60001476B-page 466 Description Writing any other value in this field aborts the write operation of the WPEN bit.  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.13 PIO Write Protection Mode Register Name: PIO_WPMR Address: 0xFC0385E0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x50494F (“PIO” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x50494F (“PIO” in ASCII). See Section 34.5.16 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value Name 0x50494F PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0. DS60001476B-page 467 SAMA5D2 SERIES 34.7.14 PIO Write Protection Status Register Name: PIO_WPSR Address: 0xFC0385E4 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 11 10 9 8 WPVSRC 15 14 13 12 WPVSRC 7 6 5 4 3 2 1 0 – – – – – – – WPVS WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of the PIO_WPSR. 1: A write protection violation has occurred since the last read of the PIO_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 468  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.15 Secure PIO Mask Register Name: S_PIO_MSKRx [x=0..3] Address: 0xFC039000 [0], 0xFC039040 [1], 0xFC039080 [2], 0xFC0390C0 [3] Access: Read/Write 31 30 29 28 27 26 25 24 MSK31 MSK30 MSK29 MSK28 MSK27 MSK26 MSK25 MSK24 23 22 21 20 19 18 17 16 MSK23 MSK22 MSK21 MSK20 MSK19 MSK18 MSK17 MSK16 15 14 13 12 11 10 9 8 MSK15 MSK14 MSK13 MSK12 MSK11 MSK10 MSK9 MSK8 7 6 5 4 3 2 1 0 MSK7 MSK6 MSK5 MSK4 MSK3 MSK2 MSK1 MSK0 This register can only be written if the WPEN bit is cleared in the Secure PIO Write Protection Mode Register. MSKy: PIO Line y Mask These bits define the I/O lines to be configured when writing the Secure PIO Configuration Register. 0 (DISABLED): Writing the S_PIO_CFGRx, S_PIO_ODSRx or S_PIO_IOFRx does not affect the corresponding I/O line configuration. 1 (ENABLED): Writing the S_PIO_CFGRx, S_PIO_ODSRx or S_PIO_IOFRX updates the corresponding I/O line configuration.  2017 Microchip Technology Inc. DS60001476B-page 469 SAMA5D2 SERIES 34.7.16 Secure PIO Configuration Register Name: S_PIO_CFGRx [x=0..3] Address: 0xFC039004 [0], 0xFC039044 [1], 0xFC039084 [2], 0xFC0390C4 [3] Access: Read/Write 31 30 29 28 – ICFS PCFS – 27 26 23 22 21 20 19 18 – – – – – – 25 24 EVTSEL 17 16 DRVSTR 15 14 13 12 11 10 9 8 SCHMITT OPD IFSCEN IFEN – PDEN PUEN DIR 2 1 0 7 6 5 4 3 – – – – – FUNC This register can only be written if the WPEN bit is cleared in the Secure PIO Write Protection Mode Register. Writing this register will only affect I/O lines enabled in the S_PIO_MSKRx. FUNC: I/O Line Function This field defines the function for I/O lines of the I/O group x according to the Secure PIO Mask Register. Value Name Description 0 GPIO Select the PIO mode for the selected I/O lines. 1 PERIPH_A Select the peripheral A for the selected I/O lines. 2 PERIPH_B Select the peripheral B for the selected I/O lines. 3 PERIPH_C Select the peripheral C for the selected I/O lines. 4 PERIPH_D Select the peripheral D for the selected I/O lines. 5 PERIPH_E Select the peripheral E for the selected I/O lines. 6 PERIPH_F Select the peripheral F for the selected I/O lines. 7 PERIPH_G Select the peripheral G for the selected I/O lines. DIR: Direction This bit defines the direction of the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0 (INPUT): The selected I/O lines are pure inputs. 1 (OUTPUT): The selected I/O lines are enabled in output. PUEN: Pull-Up Enable This bit defines the pull-up configuration of the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0 (DISABLED): Pull-Up is disabled for the selected I/O lines. 1 (ENABLED): Pull-Up is enabled for the selected I/O lines. PDEN: Pull-Down Enable This bit defines the pull-down configuration of the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0 (DISABLED): Pull-Down is disabled for the selected I/O lines. 1 (ENABLED): Pull-Down is enabled for the selected I/O lines only if PUEN is 0(1). Note 1: PDEN can be written to 1 only if PUEN is written to 0. IFEN: Input Filter Enable This bit defines if the glitch filtering is used for the I/O lines of the I/O group x according to the Secure PIO Mask Register. DS60001476B-page 470  2017 Microchip Technology Inc. SAMA5D2 SERIES 0 (DISABLED): The input filter is disabled for the selected I/O lines. 1 (ENABLED): The input filter is enabled for the selected I/O lines. IFSCEN: Input Filter Slow Clock Enable This bit defines the clock source of the glitch filtering for the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0: The glitch filter is able to filter glitches with a duration < tmck/2 for the selected I/O lines. 1: The debouncing filter is able to filter pulses with a duration < tdiv_slck/2 for the selected I/O lines. OPD: Open-Drain This bit defines the open drain configuration of the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0 (DISABLED): The open-drain is disabled for the selected I/O lines. I/O lines are driven at high- and low-level. 1 (ENABLED): The open-drain is enabled for the selected I/O lines. I/O lines are driven at low-level only. SCHMITT: Schmitt Trigger This bit defines the Schmitt trigger configuration of the I/O lines of the I/O group x according to the Secure PIO Mask Register. 0 (ENABLED): Schmitt trigger is enabled for the selected I/O lines. 1 (DISABLED): Schmitt trigger is disabled for the selected I/O lines. DRVSTR: Drive Strength This field defines the drive strength of the I/O lines of the I/O group x according to the Secure PIO Mask Register. Value Name Description 0 LO Low drive 1 LO Low drive 2 ME Medium drive 3 HI High drive EVTSEL: Event Selection This field defines the type of event to detect on the I/O lines of the I/O group x according to the Secure PIO Mask Register. Value Name Description 0 FALLING Event detection on input falling edge 1 RISING Event detection on input rising edge 2 BOTH Event detection on input both edge 3 LOW Event detection on low level input 4 HIGH Event detection on high level input 5 – Reserved 6 – Reserved 7 – Reserved PCFS: Physical Configuration Freeze Status (read-only) This bit gives information about the freeze state of the following fields of the read I/O line configuration: • FUNC: I/O Line Function • DIR: Direction • PUEN: Pull-Up Enable • PDEN: Pull-Down Enable • OPD: Open-Drain  2017 Microchip Technology Inc. DS60001476B-page 471 SAMA5D2 SERIES • SCHMITT: Schmitt Trigger • DRVSTR: Drive Strength 0 (NOT_FROZEN): The fields are not frozen and can be written for this I/O line. 1 (FROZEN): The fields are frozen and cannot be written for this I/O line. Only a hardware reset can release these fields. ICFS: Interrupt Configuration Freeze Status (read-only) This bit gives information about the freeze state of the following fields of the read I/O line configuration: • IFEN: Input Filter Enable • IFSCEN: Input Filter Slow Clock Enable • EVTSEL: Event Selection 0 (NOT_FROZEN): The fields are not frozen and can be written for this I/O line. 1 (FROZEN): The fields are frozen and cannot be written for this I/O line. Only a hardware reset can release these fields. DS60001476B-page 472  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.17 Secure PIO Pin Data Status Register Name: S_PIO_PDSRx [x=0..3] Address: 0xFC039008 [0], 0xFC039048 [1], 0xFC039088 [2], 0xFC0390C8 [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Data Status 0: The I/O line of the I/O group x is at level 0. 1: The I/O line of the I/O group x is at level 1.  2017 Microchip Technology Inc. DS60001476B-page 473 SAMA5D2 SERIES 34.7.18 Secure PIO Lock Status Register Name: S_PIO_LOCKSRx [x=0..3] Address: 0xFC03900C [0], 0xFC03904C [1], 0xFC03908C [2], 0xFC0390CC [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Lock Status 0: The I/O line of the I/O group x is not locked. 1: The I/O line of the I/O group x is locked. DS60001476B-page 474  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.19 Secure PIO Set Output Data Register Name: S_PIO_SODRx [x=0..3] Address: 0xFC039010 [0], 0xFC039050 [1], 0xFC039090 [2], 0xFC0390D0 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Set Output Data 0: No effect. 1: Sets the data to be driven on the I/O line of I/O group x.  2017 Microchip Technology Inc. DS60001476B-page 475 SAMA5D2 SERIES 34.7.20 Secure PIO Clear Output Data Register Name: S_PIO_CODRx [x=0..3] Address: 0xFC039014 [0], 0xFC039054 [1], 0xFC039094 [2], 0xFC0390D4 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Clear Output Data 0: No effect. 1: Clears the data to be driven on the I/O line of the I/O group x. DS60001476B-page 476  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.21 Secure PIO Output Data Status Register Name: S_PIO_ODSRx [x=0..3] Address: 0xFC039018 [0], 0xFC039058 [1], 0xFC039098 [2], 0xFC0390D8 [3] Access: Read/Write 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 Writing this register will only affect I/O lines enabled in the S_PIO_MSKRx. P0–P31: Output Data Status 0: The data to be driven on the I/O line of the I/O group x is 0. 1: The data to be driven on the I/O line of the I/O group x is 1.  2017 Microchip Technology Inc. DS60001476B-page 477 SAMA5D2 SERIES 34.7.22 Secure PIO Interrupt Enable Register Name: S_PIO_IERx [x=0..3] Address: 0xFC039020 [0], 0xFC039060 [1], 0xFC0390A0 [2], 0xFC0390E0 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Enable 0: No effect. 1: Enables the Input Change interrupt on the I/O line of the I/O group x. DS60001476B-page 478  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.23 Secure PIO Interrupt Disable Register Name: S_PIO_IDRx [x=0..3] Address: 0xFC039024 [0], 0xFC039064 [1], 0xFC0390A4 [2], 0xFC0390E4 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Disable 0: No effect. 1: Disables the Input Change interrupt on the I/O line of the I/O group x.  2017 Microchip Technology Inc. DS60001476B-page 479 SAMA5D2 SERIES 34.7.24 Secure PIO Interrupt Mask Register Name: S_PIO_IMRx [x=0..3] Address: 0xFC039028 [0], 0xFC039068 [1], 0xFC0390A8 [2], 0xFC0390E8 [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Mask 0: Input Change interrupt is disabled on the I/O line of the I/O group x. 1: Input Change interrupt is enabled on the I/O line of the I/O group x. DS60001476B-page 480  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.25 Secure PIO Interrupt Status Register Name: S_PIO_ISRx [x=0..3] Address: 0xFC03902C [0], 0xFC03906C [1], 0xFC0390AC [2], 0xFC0390EC [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Input Change Interrupt Status 0: No Input Change has been detected on the I/O line of the I/O group x since S_PIO_ISRx was last read or since reset. 1: At least one Input Change has been detected on the I/O line of the I/O group since S_PIO_ISRx was last read or since reset.  2017 Microchip Technology Inc. DS60001476B-page 481 SAMA5D2 SERIES 34.7.26 Secure PIO Set I/O Non-Secure Register Name: S_PIO_SIONRx [x=0..3] Address: 0xFC039030 [0], 0xFC039070 [1], 0xFC0390B0 [2], 0xFC0390F0 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Set I/O Non-Secure 0: No effect. 1: Set the I/O line of the I/O group x in Non-Secure mode. DS60001476B-page 482  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.27 Secure PIO Set I/O Secure Register Name: S_PIO_SIOSRx [x=0..3] Address: 0xFC039034 [0], 0xFC039074 [1], 0xFC0390B4 [2], 0xFC0390F4 [3] Access: Write-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: Set I/O Secure 0: No effect. 1: Set the I/O line of the I/O group x in Secure mode.  2017 Microchip Technology Inc. DS60001476B-page 483 SAMA5D2 SERIES 34.7.28 Secure PIO I/O Security Status Register Name: S_PIO_IOSSRx [x=0..3] Address: 0xFC039038 [0], 0xFC039078 [1], 0xFC0390B8 [2], 0xFC0390F8 [3] Access: Read-only 31 30 29 28 27 26 25 24 P31 P30 P29 P28 P27 P26 P25 P24 23 22 21 20 19 18 17 16 P23 P22 P21 P20 P19 P18 P17 P16 15 14 13 12 11 10 9 8 P15 P14 P13 P12 P11 P10 P9 P8 7 6 5 4 3 2 1 0 P7 P6 P5 P4 P3 P2 P1 P0 P0–P31: I/O Security Status 0 (SECURE): The I/O line of the I/O group x is in Secure mode. 1 (NON_SECURE): The I/O line of the I/O group x is in Non-Secure mode. DS60001476B-page 484  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.29 Secure PIO I/O Freeze Configuration Register Name: S_PIO_IOFRx [x=0..3] Address: 0xFC03903C [0], 0xFC03907C [1], 0xFC0390BC [2], 0xFC0390FC [3] Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 FRZKEY 23 22 21 20 FRZKEY 15 14 13 12 FRZKEY 7 6 5 4 3 2 1 0 – – – – – – FINT FPHY Writing this register will only affect I/O lines enabled in the S_PIO_MSKRx. FPHY: Freeze Physical Configuration 0: No effect. 1: Freezes the following configuration fields of Secure I/O lines if FRZKEY corresponds to 0x494F46 (“IOF” in ASCII): • FUNC: I/O Line Function • DIR: Direction • PUEN: Pull-Up Enable • PDEN: Pull-Down Enable • OPD: Open-Drain • SCHMITT: Schmitt Trigger • DRVSTR: Drive Strength Only a hardware reset can reset the FPHY bit. FINT: Freeze Interrupt Configuration 0: No effect. 1: Freezes the following configuration fields of Secure I/O lines if FRZKEY corresponds to 0x494F46 (“IOF” in ASCII): • IFEN: Input Filter Enable • IFSCEN: Input Filter Slow Clock Enable • EVTSEL: Event Selection Only a hardware reset can reset the FINT bit. FRZKEY: Freeze Key Value Name 0x494F46 PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. DS60001476B-page 485 SAMA5D2 SERIES 34.7.30 Secure PIO Slow Clock Divider Debouncing Register Name: S_PIO_SCDR Address: 0xFC039500 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – 7 6 2 1 0 DIV 5 4 3 DIV This register can only be written if the WPEN bit is cleared in the Secure PIO Write Protection Mode Register. DIV: Slow Clock Divider Selection for Debouncing tdiv_slck = ((DIV + 1) × 2) × tslck DS60001476B-page 486  2017 Microchip Technology Inc. SAMA5D2 SERIES 34.7.31 Secure PIO Write Protection Mode Register Name: S_PIO_WPMR Address: 0xFC0395E0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x50494F (“PIO” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x50494F (“PIO” in ASCII). See Section 34.5.16 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value Name 0x50494F PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0. DS60001476B-page 487 SAMA5D2 SERIES 34.7.32 Secure PIO Write Protection Status Register Name: S_PIO_WPSR Address: 0xFC0395E4 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 11 10 9 8 WPVSRC 15 14 13 12 WPVSRC 7 6 5 4 3 2 1 0 – – – – – – – WPVS WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of the S_PIO_WPSR. 1: A write protection violation has occurred since the last read of the S_PIO_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 488  2017 Microchip Technology Inc. SAMA5D2 SERIES 35. External Memories The product features: • Multiport DDR-SDRAM Controller (MPDDRC) • External Bus Interface (EBI) that embeds a NAND Flash controller and a Static Memory Controller (HSMC) Figure 35-1: External Memory Controllers MPDDRC ... ... Port 7 TrustZone Secure Bus Matrix Scrambling Port 2 Port 1 AESB Port 0 DDR2 DDR3 DDR3L LPDDR1 LPDDR2-S4 LPDDR3 EBI NAND Flash Controller NAND Flash Device Static Memory Controller Static Memory Device • The MPDDRC is a multiport DDRSDR controller supporting DDR2, DDR3, DDR3L, LPDDR1, LPDDR2-S4 and LPDDR3 devices. The MPDDRC user interface is located at 0xF000C000. All the paths can be scrambled and Port 0 can be connected to an AES encryption/decryption engine. • The HSMC supports Static Memories and MLC/SLC NAND Flash. It embeds MultiBit ECC correction (PMECC). Its user interface is located at 0xF8014000. The HSMC buses can be scrambled. 35.1 35.1.1 Multiport DDR-SDRAM Controller (MPDDRC) Description The MPDDRC is an 8-port memory controller supporting DDR-SDRAM and low-power DDR devices. Data transfers are performed through a 16/32-bit data bus on one chip select. The controller operates with a 1.8V power supply for DDR2, DDR3, LPDDR1, 1.35V for DDR3L and 1.2V for LPDDR2, LPDDR3. For full details, refer to Section 36. “Multiport DDR-SDRAM Controller (MPDDRC)”.  2017 Microchip Technology Inc. DS60001476B-page 489 SAMA5D2 SERIES 35.1.2 MPDDR Controller Block Diagram Figure 35-2: MPDDRC Block Diagram MPDDRC DDR_A[13:0] DDR_D[31:0] DDR_CS Bus Matrix DDR_CKE DDR_RAS, DDR_CAS DDR2 DDR3 DDR3L LPDDR1 LPDDR2-S4 LPDDR3 Controller AHB DDR_CLK,DDR_CLKN DDR_DQS[3:0] DDR_DQSN[3:0] DDR_DQM[3:0] DDR_WE DDR_BA[2:0] Address Decoders DDR_CAL(1) DDR_RESETN DDR_VREF User Interface APB Note: For more details, refer to Section 8.2.4 ”DDR and SDMMC I/Os Calibration”. DS60001476B-page 490  2017 Microchip Technology Inc. SAMA5D2 SERIES 35.1.3 I/O Lines Description Table 35-1: DDR/LPDDR I/O Lines Description Name Function Type Active Level Power – DDR/LPDDR Controller VDDIODDR Power Supply of memory interface DDR_VREF Reference Voltage Input – DDR_CAL Calibration reference Input – DDR_D[31:0] Data Bus I/O – DDR_A[13:0] Address Bus Output – DDR_DQM[3:0] Data Mask Output – DDR_DQS[3:0] Data Strobe I/O – DDR_DQSN[3:0] Negative Data Strobe I/O – DDR_CS Chip Select Output Low DDR_RESETN DDR3 Active Low Asynchronous Reset Output Low DDR_CLK, DDR_CLKN Differential Clock Output – DDR_CKE Clock enable Output High DDR_RAS Row signal Output Low DDR_CAS Column signal Output Low DDR_WE Write enable Output Low DDR_BA[2:0] Bank Select Output –  2017 Microchip Technology Inc. DS60001476B-page 491 SAMA5D2 SERIES 35.1.4 Product Dependencies The pins used for interfacing the DDR/LPDDR memories are not multiplexed with the PIO lines. The table below gives the connections to the various memory types. Table 35-2: I/O Lines Usage vs Operating Modes Signal Name DDR2 DDR3 DDR3L LPDDR1 LPDDR2/LPDDR3 DDR_VREF VDDIODDR/2 VDDIODDR/2 VDDIODDR/2 VDDIODDR/2 VDDIODDR/2 DDR_CAL GND via 21KΩ GND via 22KΩ GND via 23KΩ GND via 21KΩ GND via 24ΚΩ DDR_CK, DDR_CLKN CLK, CLKN CLK, CLKN CLK, CLKN CLK, CLKN CLK, CLKN DDR_CKE CLKE CLKE CLKE CLKE CLKE DDR_CS CS CS CS CS CS DDR_RESETN Not connected DDR_RESETN DDR_RESETN Not connected Not connected DDR_BA[2:0] BA[2:0] BA[2:0] BA[2:0] BA[1:0] Not connected DDR_WE WE WE WE WE CA2 DDR_RAS, DDR_CAS RAS, CAS RAS, CAS RAS, CAS RAS, CAS CA0, CA1 DDR_A[13:0] A[13:0] A[13:0] A[13:0] A[13:0] CAx, with x > 2 DDR_D[31:0] D[31:0] D[31:0] D[31:0] D[31:0] D[31:0] DDR_DQS[3:0], DDR_DQSN[3:0] LDQS,UDQS DDR_VREF DQS[3:0] DQSN[3:0] DQS[3:0] DQSN[3:0] DQS[3:0], DDR_VREF DQS[3:0] DQSN[3:0] DDR_DQM[3:0] UDM, LDM DQM[3:0] DQM[3:0] DQM[3:0] DQM[3:0] DS60001476B-page 492  2017 Microchip Technology Inc. SAMA5D2 SERIES 35.1.5 Implementation Example The following hardware configurations are given for illustration only. The user should refer to the memory manufacturer website to check current device availability. 35.1.5.1 16-bit DDR2 Figure 35-3: 16-bit DDR2 Hardware Configuration DDR_CS DDR_RAS DDR_CAS DDR_WE L8 K7 L7 K3 DDR_CK DDR_C L KN DDR_CKE J8 K8 K2 0R K9 DDR_VREF VDDIODDR J2 J7 J1 A9 C1 C3 C7 C9 E9 G1 G3 G7 G9 VDDQ1 VDDQ2 VDDQ3 VDDQ4 VDDQ5 VDDQ6 VDDQ7 VDDQ8 VDDQ9 VDDQ10 L2 L3 L1 DQ0 DQ1 DQ2 DQ3 DQ4 DQ5 DQ6 DQ7 DQ8 DQ9 DQ10 DQ11 DQ12 DQ13 DQ14 DQ15 BA0 BA1 BA2 LDQS LDQS CS RAS CAS WE UDQS UDQS UDM LDM CK CK CKE ODT NC_A2 NC_E2 RFU_R3 RFU_R7 VREF VSSDL VDDL 100nF A3 E3 J3 N1 P9 100nF G8 G2 H7 H3 H1 H9 F1 F9 C8 C2 D7 D3 D1 D9 B1 B9 DDR_D0 DDR_D1 DDR_D2 DDR_D3 DDR_D4 DDR_D5 DDR_D6 DDR_D7 DDR_D8 DDR_D9 DDR_D10 DDR_D11 DDR_D12 DDR_D13 DDR_D14 DDR_D15 F7 E8 DDR_DQS0 DDR_DQSN0 B7 A8 DDR_DQS1 DDR_DQSN1 B3 F3 DDR_DQM1 DDR_DQM0 A2 E2 R3 R7 VSSQ1 VSSQ2 VSSQ3 VSSQ4 VSSQ5 VSSQ6 VSSQ7 VSSQ8 VSSQ9 VSSQ10 DDR_BA0 DDR_BA1 DDR_BA2 A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A12 A13 A7 B8 D2 D8 E7 F2 F8 H2 H8 B2 M8 M3 M7 N2 N8 N3 N7 P2 P8 P3 M2 P7 R2 R8 VSS1 VSS2 VSS3 VSS4 VSS5 DDR_A0 DDR_A1 DDR_A2 DDR_A3 DDR_A4 DDR_A5 DDR_A6 DDR_A7 DDR_A8 DDR_A9 DDR_A10 DDR_A11 DDR_A12 DDR_A13 VDD1 VDD2 VDD3 VDD4 VDD5 A1 E1 J9 M9 R1 VDDIODDR MT47H128M16RT-25E:C VDDIODDR 10uH_150mA DDR _CK+ 100nF 4.7uF 2.2K 1% 1R 1% DDR_VREF DNP(100R 1%) DDR _CK-  2017 Microchip Technology Inc. 4.7uF 2.2K 1% 100nF DS60001476B-page 493 SAMA5D2 SERIES 35.1.5.2 2x16-bit DDR2 Figure 35-4: 2x16-bit DDR2 Hardware Configuration ''5B'>@ ''5B$>@ 9'',2''5 ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ 0 0 0 1 1 1 1 3 3 3 0 3 5 5 ''5B%$ ''5B%$ ''5B%$ / / / '13. . 5 ''5B&.( ''5B&. ''5B&/.1 . - . ''5B&6 / ''5B&$6 ''5B5$6 / . ''5B:( . ''5B'46 . % $ ''5B'46 . ) ( ''5B'40 ''5B'40 % ) $ ( 5 5 $ ''56'5$0 '4 $ '4 $ 07+0+5 '4 '4 $ $ '4 $ '4 '4 $ $ '4 $ '4 $ '4 $ '4 '4 $ $ '4 $ '4 '4 %$ '4 %$ %$ 9'' 9'' 2'7 9'' 9'' 9'' &.( 9''/ &. &. 9''4 9''4 9''4 9''4 &6 9''4 9''4 &$6 9''4 5$6 9''4 9''4 :( 9''4 8'46 8'46 /'46 /'46 8'0 /'0 5)8 5)8 5)8 5)8 95() 966 966 966 966 966 9664 9664 9664 9664 9664 9664 9664 9664 9664 9664 966'/ * * + + + + ) ) & & ' ' ' ' % % ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' 9'',2''5 9'',2''5 $ ( - 0 5 - $ ( - 1 3 $ % % ' ' ( ) ) + + - ''5B%$ ''5B%$ ''5B%$ / / / . 5 Q) $ & & & & ( * * * * 0 0 0 1 1 1 1 3 3 3 0 3 5 5 '13. Q) Q) Q) Q) Q) - ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ Q) Q) Q) Q) Q) Q) Q) Q) Q) Q) ''5B95() & Q) ''5B&.( . ''5B&. ''5B&/.1 - . ''5B&6 / ''5B&$6 ''5B5$6 / . ''5B:( . ''5B'46 . % $ ''5B'46 . ) ( ''5B'40 ''5B'40 % ) $ ( 5 5 $ ''56'5$0 '4 '4 $ $ 07+0+5 '4 '4 $ $ '4 $ '4 '4 $ $ '4 '4 $ '4 $ $ '4 '4 $ $ '4 $ '4 '4 %$ '4 %$ %$ 9'' 2'7 9'' 9'' 9'' 9'' &.( 9''/ &. &. 9''4 9''4 9''4 9''4 &6 9''4 9''4 9''4 &$6 5$6 9''4 9''4 :( 9''4 95() 8'46 8'46 966 966 966 966 966 /'46 /'46 9664 9664 9664 9664 9664 9664 9664 9664 9664 9664 966'/ 8'0 /'0 5)8 5)8 5)8 5)8 9'',2''5 * * + + + + ) ) & & ' ' ' ' % % ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' 9'',2''5 $ ( - 0 5 Q) Q) Q) Q) Q) - Q) $ & & & & ( * * * * - $ ( - 1 3 Q) Q) Q) Q) Q) Q) Q) Q) Q) Q) ''5B95() Q) $ % % ' ' ( ) ) + + - X+ P$ X) 5 Q) . ''5B95() X) DS60001476B-page 494 Q) 5 .  2017 Microchip Technology Inc. SAMA5D2 SERIES 35.1.5.3 16-bit DDR3/DDR3L Figure 35-5: 16-bit DDR3/DDR3L Hardware Configuration ''5B&. '135 ''5B& / .1 ''5B5(6(71 7 ''5B&. ''5B& / .1 ''5B&.( ''5B&6 ''5B5$6 ''5B&$6 ''5B:( - . . / - . / ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ''5B' ( ) ) ) + + * + ' & & & $ $ % $ ''5B'46 & ''5B'461 % ''5B'46 ) ''5B'461 * ''5B'40 ' ''5B'40 ( 9''B9 9'',2''5 X+BP$ X) 5 X) Q) . - - / / ''5B95() Q) $ $ & & ' ( ) + + . ''5B95() Q) Q) 0 + 5(6(7 &. &. &.( &6 5$6 &$6 :( $ $ $ $ $ $ $ $ $ $ $$3 $ $%& $ $ $ %$ %$ %$ '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 '4 2'7 8'46 8'46 /'46 /'46 8'0 /'0 9''4 9''4 9''4 9''4 9''4 9''4 9''4 9''4 9''4 1& 1& 1& 1& 95()&$ 95()'4 9'' 9'' 9'' 9'' 9'' 9'' 9'' 9'' 9'' 966 966 966 966 966 966 966 966 966 966 966 966 9664 9664 9664 9664 9664 9664 9664 9664 9664 =4 1 3 3 1 3 3 5 5 7 5 / 5 1 7 7 0 0 1 0 . % * 5 . . 1 1 5 ' ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B%$ ''5B%$ ''5B%$ 9''B9 '13. 5 9''B9 $ % ( * - - 0 0 3 3 7 7 % % ' ' ( ( ) * * / 5 07.0-7.  2017 Microchip Technology Inc. DS60001476B-page 495 SAMA5D2 SERIES 35.1.5.4 2x16-bit DDR3/DDR3L Figure 35-6: 2x16-bit DDR3/DDR3L Hardware Configuration DDR_CK DNP(100R 1%) DDR_C LKN DDR_RESETN T2 DDR_CK DDR_C LKN DDR_CKE DDR_CS DDR_RAS DDR_CAS DDR_WE J7 K7 K9 L2 J3 K3 L3 DDR_D0 DDR_D1 DDR_D2 DDR_D3 DDR_D4 DDR_D5 DDR_D6 DDR_D7 DDR_D8 DDR_D9 DDR_D10 DDR_D11 DDR_D12 DDR_D13 DDR_D14 DDR_D15 E3 F7 F2 F8 H3 H8 G2 H7 D7 C3 C8 C2 A7 A2 B8 A3 DDR_DQS1 C7 DDR_DQSN1 B7 DDR_DQS0 F3 DDR_DQSN0 G3 DDR_DQM1 D3 DDR_DQM0 E7 VDD_1V35 VDDIODDR 10uH_150mA 4.7uF 100nF 6.8K 1% 1R 1% 4.7uF J1 J9 L1 L9 DDR_VREF 100nF A1 A8 C1 C9 D2 E9 F1 H2 H9 6.8K 1% DDR_VREF 100nF 100nF M8 H1 RESET# CK CK# CKE CS# RAS# CAS# WE# A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10/AP A11 A12/BC# A13 A14 A15 BA0 BA1 BA2 DQ0 DQ1 DQ2 DQ3 DQ4 DQ5 DQ6 DQ7 DQ8 DQ9 DQ10 DQ11 DQ12 DQ13 DQ14 DQ15 ODT UDQS UDQS# LDQS LDQS# UDM LDM VDDQ1 VDDQ2 VDDQ3 VDDQ4 VDDQ5 VDDQ6 VDDQ7 VDDQ8 VDDQ9 NC1 NC2 NC3 NC4 VREFCA VREFDQ VDD1 VDD2 VDD3 VDD4 VDD5 VDD6 VDD7 VDD8 VDD9 VSS1 VSS2 VSS3 VSS4 VSS5 VSS6 VSS7 VSS8 VSS9 VSS10 VSS11 VSS12 VSSQ1 VSSQ2 VSSQ3 VSSQ4 VSSQ5 VSSQ6 VSSQ7 VSSQ8 VSSQ9 ZQ N3 P7 P3 N2 P8 P2 R8 R2 T8 R3 L7 R7 N7 T3 T7 M7 M2 N8 M3 DDR_A0 DDR_A1 DDR_A2 DDR_A3 DDR_A4 DDR_A5 DDR_A6 DDR_A7 DDR_A8 DDR_A9 DDR_A10 DDR_A11 DDR_A12 DDR_A13 DDR_BA0 DDR_BA1 DDR_BA2 DDR_RESETN T2 DDR_CK DDR_C LKN DDR_CKE DDR_CS DDR_RAS DDR_CAS DDR_WE J7 K7 K9 L2 J3 K3 L3 DDR_D16 DDR_D17 DDR_D18 DDR_D19 DDR_D20 DDR_D21 DDR_D22 DDR_D23 DDR_D24 DDR_D25 DDR_D26 DDR_D27 DDR_D28 DDR_D29 DDR_D30 DDR_D31 E3 F7 F2 F8 H3 H8 G2 H7 D7 C3 C8 C2 A7 A2 B8 A3 VDD_1V35 DNP(1K) K1 0R B2 G7 R9 K2 K8 N1 N9 R1 D9 VDD_1V35 DDR_DQS3 C7 DDR_DQSN3 B7 DDR_DQS2 F3 DDR_DQSN2 G3 DDR_DQM3 D3 DDR_DQM2 E7 A9 B3 E1 G8 J2 J8 M1 M9 P1 P9 T1 T9 VDD_1V35 B1 B9 D1 D8 E2 E8 F9 G1 G9 A1 A8 C1 C9 D2 E9 F1 H2 H9 J1 J9 L1 L9 DDR_VREF L8 100nF 100nF M8 H1 RESET# CK CK# CKE CS# RAS# CAS# WE# A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10/AP A11 A12/BC# A13 A14 A15 BA0 BA1 BA2 DQ0 DQ1 DQ2 DQ3 DQ4 DQ5 DQ6 DQ7 DQ8 DQ9 DQ10 DQ11 DQ12 DQ13 DQ14 DQ15 ODT VDD1 VDD2 VDD3 VDD4 VDD5 VDD6 VDD7 VDD8 VDD9 UDQS UDQS# LDQS LDQS# UDM LDM VSS1 VSS2 VSS3 VSS4 VSS5 VSS6 VSS7 VSS8 VSS9 VSS10 VSS11 VSS12 VDDQ1 VDDQ2 VDDQ3 VDDQ4 VDDQ5 VDDQ6 VDDQ7 VDDQ8 VDDQ9 NC1 NC2 NC3 NC4 VSSQ1 VSSQ2 VSSQ3 VSSQ4 VSSQ5 VSSQ6 VSSQ7 VSSQ8 VSSQ9 VREFCA VREFDQ ZQ 240R 1% MT41K128M16JT-125:K DS60001476B-page 496 N3 P7 P3 N2 P8 P2 R8 R2 T8 R3 L7 R7 N7 T3 T7 M7 M2 N8 M3 DDR_A0 DDR_A1 DDR_A2 DDR_A3 DDR_A4 DDR_A5 DDR_A6 DDR_A7 DDR_A8 DDR_A9 DDR_A10 DDR_A11 DDR_A12 DDR_A13 DDR_BA0 DDR_BA1 DDR_BA2 VDD_1V35 DNP(1K) K1 0R B2 G7 R9 K2 K8 N1 N9 R1 D9 VDD_1V35 A9 B3 E1 G8 J2 J8 M1 M9 P1 P9 T1 T9 B1 B9 D1 D8 E2 E8 F9 G1 G9 L8 240R 1% MT41K128M16JT-125:K  2017 Microchip Technology Inc. SAMA5D2 SERIES 35.1.5.5 2x16-bit LPDDR2/LPDDR3 The schematic below is given for LPDDR2 but it is also valid for LPDDR3. Figure 35-7: 2x16-bit LPDDR2 Hardware Configuration ''5B'>@ ''5B5$6 ''5B&$6 ''5B:( ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ ''5B$ $& $% $& $% $% : 9 8 7 7 ''5B&.( $& $& 1; for (i=1; i XMEMSIZE ) otherwise Vertical Scaler The YMEMSIZE field of the LCDC_HEOCFG4 register indicates the vertical size minus one of the image in the system memory. The YSIZE field of the LCDC_HEOCFG3 register contains the vertical size minus one of the window. The SCALEN bit of the LCDC_HEOCFG13 register is set to one. The scaling factor is programmed in the YFACTOR field of the LCDC_HEOCFG13 register. 8 × 256 × YMEMSIZE – 256 × YPHIDEF YFACTOR 1st = floor  --------------------------------------------------------------------------------------------------------   YSIZE YFACTOR 1st = YFACTOR 1st + 1 YFACTOR 1st × YSIZE + 256 × YPHIDEF YMEMSIZE max = floor  ----------------------------------------------------------------------------------------------------------   2048  YFACTOR = YFACTOR 1st – 1  YFACTOR = YFACTOR 1st  39.6.10 39.6.10.1 when ( YMEMSIZE max > YMEMSIZE ) otherwise Color Combine Unit Window Overlay The LCD module provides hardware support for multiple “overlay plane” that can be used to display windows on top of the image without destroying the image located below. The overlay image can use any color depth. Using the overlay alleviates the need to re-render the occluded portion of the image. When pixels are combined together through the alpha blending unit, a new color is created. This new pixel is called an iterated pixel and is passed to the next blending stage. Then, this pixel may be combined again with another pixel. The VIDPRI bit located in the LCDC_HEOCFG12 register configures the video priority algorithm used to display the layers. When the VIDPRI bit is written to ‘0’, the OVR1 layer is located above the HEO layer. When the VIDPRI bit is written to ‘1’, OVR1 is located below the HEO layer. DS60001476B-page 752  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 39-9: Overlay Example with Two Different Video Prioritization Algorithms HEO width OVR1 width Base width Base height o0(x,y) HEO o1(x,y) HEO height Overlay1 OVR1 OVR1 height OVR2 Base Image Video Prioritization Algorithm 1 : OVR2 > OVR1 > HEO > BASE Base Image HEO OVR2 Overlay1 OVR1 Video Prioritization Algorithm 2 : OVR2 > HEO > OVR1 > BASE 39.6.10.2 Base Layer with Window Overlay Optimization When the base layer is combined with at least one active overlay, the whole base layer frame is retrieved from the memory though it is not visible. A set of registers is used to disable the Base DMA when this condition is met. These registers are the following: • LCDC_BASECFG5: - field DISCXPOS (Discard Area Horizontal Position) - field DISCYPOS (Discard Area Vertical Position) • LCDC_BASECFG6: - field DISCXSIZE (Discard Area Horizontal Size) - field DISCYSIZE (Discard Area Vertical Size)  2017 Microchip Technology Inc. DS60001476B-page 753 SAMA5D2 SERIES • LCDC_BASECFG4: bit DISCEN (Discard Area Enable) Figure 39-10: Base Layer Discard Area Base width Base height Base Image DISCXSIZE Base width Base height {DISCXPOS, DISCYPOS} Overlay1 DISCYSIZE Discarded Area Base Image HEO width Base width Base height HEO Video HEO height Base Image 39.6.10.3 Overlay Blending The blending function requires two pixels (one iterated from the previous blending stage and one from the current overlay color) and a set of blending configuration parameters. These parameters define the color operation. DS60001476B-page 754  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 39-11: Alpha Blender Function iter[n-1] GA OVR From LAEN Shadow REVALPHA Registers ITER ITER2BL CRKEY INV DMA GAEN RGBKEY RGBMASK OVRDEF Figure 39-12: la ovr Blending Function iter[n] Alpha Blender Database la ovr iter[n-1] OVR ITER OVRDEF GA "0" "0" GAEN 0 0 0 DMA LAEN "0" 0 0 Alpha * ovr + (1 - Alpha) * iter[n-1] REVALPHA ovr RGBKEY RGBMASK CRKEY ovr iter[n-1] 0 MATCH LOGIC 0 Inverted INV 0 iter[n]  2017 Microchip Technology Inc. DS60001476B-page 755 SAMA5D2 SERIES 39.6.10.4 Window Blending Figure 39-13: 256-level Alpha Blending Base Image OVR1 25 % HEO 75 % Video Prioritization Algorithm 1: OVR1 > HEO > BASE 39.6.10.5 Color Keying Color keying involves a method of bit-block image transfer (Blit). This entails blitting one image onto another where not all the pixels are copied. Blitting usually involves two bitmaps: a source bitmap and a destination bitmap. A raster operation (ROP) is performed to define whether the iterated color or the overlay color is to be visible or not. • Source Color Keying If the masked overlay color matches the color key, the iterated color is selected and Source Color Keying is activated using the following configuration sequence: 1. 2. 3. 4. 5. Select the overlay to blit. Write a ‘0’ to DSTKEY. Activate Color Keying by writing a ‘1’ to CRKEY. Configure the Color Key by writing RKEY, GKEY and BKEY fields. Configure the Color Mask by writing RKEY, GKEY and BKEY fields. When the field RMASK, GMASK, or BMASK is configured to ‘0’, the comparison is disabled and the raster operation is activated. • Destination Color Keying If the iterated masked color matches the color key then the overlay color is selected, Destination Color Keying is activated using the following configuration sequence: 1. 2. 3. 4. 5. Select the overlay to blit. Write a ‘1’ to DSTKEY. Activate Color Keying by writing a ‘1’ to CRKEY bit Configure the Color Key by writing RKEY, GKEY and BKEY fields. Configure the Color Mask by writing RKEY, GKEY and BKEY fields. When the field RMASK, GMASK, or BMASK is configured to ‘0’, the comparison is disabled and the raster operation is activated. 39.6.11 LCDC PWM Controller This block generates the LCD contrast control signal (LCDPWM) to make possible the control of the display's contrast by software. This is an 8-bit PWM (Pulse Width Modulation) signal that can be converted to an analog voltage with a simple passive filter. DS60001476B-page 756  2017 Microchip Technology Inc. SAMA5D2 SERIES The PWM module has a free-running counter whose value is compared against a compare register (PWMCVAL field of the LCDC_LCDCFG6 register). If the value in the counter is less than that in the register, the output brings the value of the signal polarity (PWMPOL) bit in the PWM control register: LCDC_LCDCFG6. Otherwise, the opposite value is output. Thus, a periodic waveform with a pulse width proportional to the value in the compare register is generated. Due to the comparison mechanism, the output pulse has a width between zero and 255 PWM counter cycles. Thus by adding a simple passive filter outside the chip, an analog voltage between 0 and (255/256) × VDD can be obtained (for the positive polarity case, or between (1/256) × VDD and VDD for the negative polarity case). Other voltage values can be obtained by adding active external circuitry. For PWM mode, the counter frequency can be adjusted to four different values using the PWMPS field of the LCDC_LCDCFG6 register. The PWM module can be fed with the slow clock or the system clock, depending on the CLKPWMSEL bit of the LCDC_CFG0 register. 39.6.12 Post Processing Controller The output stream of pixels can be either displayed on the screen or written to the memory using the Post Processing Controller (PPC). When the PPC is used, the screen display is disabled, but synchronization signals remain active (if enabled). The stream of pixel can be written in RGB mode or encoded in YCbCr 422 mode. A programmable color space conversion stage is available. ·· Y CSCYR CSCYG CSCYB R Yoff = • + U CSCUR CSCUG CSCUB G Uoff V CSCVR CSCVG CSCUB B Voff 39.6.13 LCD Overall Performance 39.6.13.1 Color Lookup Table (CLUT) Table 39-49: CLUT Pixel Performance CLUT Mode Pixels/Cycle Rotation Scaling 1 bpp 64 Not supported Supported 2 bpp 32 Not supported Supported 3 bpp 16 Not supported Supported 4 bpp 8 Not supported Supported  2017 Microchip Technology Inc. DS60001476B-page 757 SAMA5D2 SERIES 39.6.13.2 RGB Mode Fetch Performance Table 39-50: RGB Mode Performance RGB Mode Rotation Peak Random Memory Access (pixels/cycle) Pixels/Cycle Memory Burst Mode Rotation Optimization (see table footnote) Normal Mode Scaling Burst Mode or Rotation Optimization Available 12 bpp 4 1 0.2 Supported 16 bpp 4 1 0.2 Supported 18 bpp 2 1 0.2 Supported 18 bpp RGB PACKED 2.666 Not supported 0.2 Supported 19 bpp 2 1 0.2 Supported 19 bpp PACKED 2.666 Not Supported 0.2 Supported 24 bpp 2 1 0.2 Supported 24 bpp PACKED 2.666 Not Supported 0.2 Supported 25 bpp 2 1 0.2 Supported 32 bpp 2 1 0.2 Supported Note: Rotation optimization = AHB lock asserted on consecutive single access. 39.6.13.3 YUV Mode Fetch Performance Table 39-51: Single Stream for 0 Wait State Memory Rotation Peak Random Memory Access (pixels/cycle) YUV Mode Pixels/Cycle Memory Burst Mode Rotation Optimization (see table footnote) Normal Mode Scaling Burst Mode or Rotation Optimization Is Available 32 bpp AYUV 2 1 0.2 Supported 16 bpp 422 4 Not Supported Not Supported Supported Note 1: Rotation optimization = AHB lock asserted on consecutive single access Table 39-52: Multiple Stream for 0 Wait State Memory YUV Mode Comp/Cycle Rotation Peak Random Memory Access (pixels/cycle) Memory Burst Mode Rotation Optimization Normal Mode Scaling Burst Mode or Rotation Optimization Is Available 16 bpp 422 semiplanar 8 Y, 4 UV 1 Y, 1 UV (2 streams) 0.2 Y 0.2 UV (2 streams) Supported 16 bpp 422 planar 8 Y, 8 U, 8 V 1 Y, 1 U, 1 V (3 streams) 0.2 Y, 0.2 U, 0.2 V (3 streams) Supported 12 bpp 4:2:0 semiplanar 8 Y, 4 UV 1 Y, 1 UV (2 streams) 0.2 Y 0.2 UV (2 streams) 12 bpp 4:2:0 planar 1 Y, 1 U, 1 V (3 streams) 0.2 Y, 0.2 U, 0.2 V (3 streams) Supported Note: 8 Y, 8 U, 8 V Supported In order to provide more bandwidth when multiple streams are used to transfer Y, UV, U or V components, two AHB interfaces are recommended or multiple AXI IDs are required. DS60001476B-page 758  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 39-53: YUV Planar Overall Performance 1 AHB Interface for 0 Wait State Memory YUV Mode Pix/Cycle Rotation Peak Random Memory Access (pixels/cycle) Memory Burst Mode Rotation Optimization Normal Mode Scaling Burst Mode or Rotation Optimization Is Available 16 bpp 422 semiplanar 4 0.66 0.132 Supported 16 bpp 422 planar 4 0.5 0.1 Supported 12 bpp 4:2:0 semiplanar 5.32 0.8 0.16 Supported 12 bpp 4:2:0 planar 0.66 0.132 Supported Note: 39.6.14 5.32 In order to provide more bandwidth when multiple streams are used to transfer Y, UV, U or V components, two AHB interfaces are recommended or multiple AXI IDs are required. Input FIFO The LCD module includes one input FIFO per overlay. These input FIFOs are used to buffer the AHB burst and serialize the stream of pixels. 39.6.15 Output FIFO The LCD module includes one output FIFO that stores the blended pixel.  2017 Microchip Technology Inc. DS60001476B-page 759 SAMA5D2 SERIES 39.6.16 Output Timing Generation 39.6.16.1 Active Display Timing Mode Figure 39-14: Active Display Timing LCDPCLK LCDVSYNC LCDHSYNC LCDBIAS_DEN LCDDAT[23:0] HSW VSW VBP HBP LCDPCLK LCDVSYNC LCDHSYNC LCDBIASDEN LCDDAT[23:0] HSW HBP HFP PPL HSW HBP LCDPCLK LCDVSYNC LCDHSYNC LCDBIASDEN LCDDAT[23:0] PPL DS60001476B-page 760 HFP HSW VFP  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 39-15: VSPDLYS = 0 Vertical Synchronization Timing (part 1) VSPDLYE = 0 VSPSU = 0 VSPHO = 0 LCDPCLK LCDVSYNC LCDHSYNC HSW VSPDLYS = 1 VSPDLYE = 0 VSW VSPSU = 0 VBP HBP VBP HBP VBP HBP VBP HBP VBP HBP VSPHO = 0 LCDPCLK LCDVSYNC LCDHSYNC HSW VSPDLYS = 0 VSPDLYE = 1 VSW VSPSU = 0 VSPHO = 0 LCDPCLK LCDVSYNC LCDHSYNC HSW VSPDLYS = 1 VSPDLYE = 1 VSW VSPSU = 0 VSPHO = 0 LCDPCLK LCDVSYNC LCDHSYNC HSW VSPDLYS = 1 VSPDLYE = 0 VSW VSPSU = 1 VSPHO = 0 LCDPCLK LCDVSYNC LCDHSYNC HSW  2017 Microchip Technology Inc. VSW DS60001476B-page 761 SAMA5D2 SERIES Figure 39-16: VSPDLYS = 1 Vertical Synchronization Timing (part 2) VSPDLYE = 0 VSPSU = 0 VSPHO = 1 LCDPCLK LCDVSYNC LCDHSYNC HSW VSPDLYS = 1 VSPDLYE = 0 VSW VSPSU = 1 VBP HBP VBP HBP VSPHO = 1 LCDPCLK LCDVSYNC LCDHSYNC HSW DS60001476B-page 762 VSW  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 39-17: DISP Signal Timing Diagram VSPDLYE = 0 VSPHO = 0 DISPPOL = 0 DISPDLY = 0 LCDPCLK LCDVSYNC LCDHSYNC lcd display off LCDDISP lcd display on VSPDLYE = 0, VSPHO = 0, DISPPOL = 0, DISPDLY = 0 LCDPCLK LCDVSYNC LCDHSYNC LCDDISP lcd display off lcd display on VSPDLYE = 0, VSPHO = 0, DISPPOL = 0, DISPDLY = 1 LCDPCLK LCDVSYNC LCDHSYNC LCDDISP lcd display off lcd display on VSPDLYE = 0, VSPHO = 0, DISPPOL = 0, DISPDLY = 1 LCDPCLK LCDVSYNC LCDHSYNC LCDDISP  2017 Microchip Technology Inc. lcd display on lcd display off DS60001476B-page 763 SAMA5D2 SERIES 39.6.17 Output Format 39.6.17.1 Active Mode Output Pin Assignment Table 39-54: Active Mode Output with 24-bit Bus Interface Configuration Pin ID TFT 24 bits TFT 18 bits TFT 16 bits TFT 12 bits LCDDAT[23] R[7] R[5] R[4] R[3] LCDDAT[22] R[6] R[4] R[3] R[2] LCDDAT[21] R[5] R[3] R[2] R[1] LCDDAT[20] R[4] R[2] R[1] R[0] LCDDAT[19] R[3] R[1] R[0] – LCDDAT[18] R[2] R[0] – – LCDDAT[17] R[1] – – – LCDDAT[16] R[0] – – – LCDDAT[15] G[7] G[5] G[5] G[3] LCDDAT[14] G[6] G[4] G[4] G[2] LCDDAT[13] G[5] G[3] G[3] G[1] LCDDAT[12] G[4] G[2] G[2] G[0] LCDDAT[11] G[3] G[1] G[1] – LCDDAT[10] G[2] G[0] G[0] – LCDDAT[9] G[1] – – – LCDDAT[8] G[0] – – – LCDDAT[7] B[7] B[5] B[4] B[3] LCDDAT[6] B[6] B[4] B[3] B[2] LCDDAT[5] B[5] B[3] B[2] B[1] LCDDAT[4] B[4] B[2] B[1] B[0] LCDDAT[3] B[3] B[1] B[0] – LCDDAT[2] B[2] B[0] – – LCDDAT[1] B[1] – – – LCDDAT[0] B[0] – – – DS60001476B-page 764  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7 LCD Controller (LCDC) User Interface Table 39-55: Register Mapping Offset Register Name Access Reset 0x00000000 LCD Controller Configuration Register 0 LCDC_LCDCFG0 Read/ Write 0x00000000 0x00000004 LCD Controller Configuration Register 1 LCDC_LCDCFG1 Read/ Write 0x00000000 0x00000008 LCD Controller Configuration Register 2 LCDC_LCDCFG2 Read/ Write 0x00000000 0x0000000C LCD Controller Configuration Register 3 LCDC_LCDCFG3 Read/ Write 0x00000000 0x00000010 LCD Controller Configuration Register 4 LCDC_LCDCFG4 Read/ Write 0x00000000 0x00000014 LCD Controller Configuration Register 5 LCDC_LCDCFG5 Read/ Write 0x00000000 0x00000018 LCD Controller Configuration Register 6 LCDC_LCDCFG6 Read/ Write 0x00000000 0x0000001C Reserved – – – 0x00000020 LCD Controller Enable Register LCDC_LCDEN Write-only – 0x00000024 LCD Controller Disable Register LCDC_LCDDIS Write-only – 0x00000028 LCD Controller Status Register LCDC_LCDSR Read-only 0x00000000 0x0000002C LCD Controller Interrupt Enable Register LCDC_LCDIER Write-only – 0x00000030 LCD Controller Interrupt Disable Register LCDC_LCDIDR Write-only – 0x00000034 LCD Controller Interrupt Mask Register LCDC_LCDIMR Read-only 0x00000000 0x00000038 LCD Controller Interrupt Status Register LCDC_LCDISR Read-only 0x00000000 0x0000003C LCD Controller Attribute Register LCDC_ATTR Write-only – 0x00000040 Base Layer Channel Enable Register LCDC_BASECHER Write-only – 0x00000044 Base Layer Channel Disable Register LCDC_BASECHDR Write-only – 0x00000048 Base Layer Channel Status Register LCDC_BASECHSR Read-only 0x00000000 0x0000004C Base Layer Interrupt Enable Register LCDC_BASEIER Write-only – 0x00000050 Base Layer Interrupt Disabled Register LCDC_BASEIDR Write-only – 0x00000054 Base Layer Interrupt Mask Register LCDC_BASEIMR Read-only 0x00000000 0x00000058 Base Layer Interrupt Status Register LCDC_BASEISR Read-only 0x00000000 0x0000005C Base DMA Head Register LCDC_BASEHEAD Read/ Write 0x00000000 0x00000060 Base DMA Address Register LCDC_BASEADDR Read/ Write 0x00000000 0x00000064 Base DMA Control Register LCDC_BASECTRL Read/ Write 0x00000000 0x00000068 Base DMA Next Register LCDC_BASENEXT Read/ Write 0x00000000  2017 Microchip Technology Inc. DS60001476B-page 765 SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset 0x0000006C Base Layer Configuration Register 0 LCDC_BASECFG0 Read/ Write 0x00000000 0x00000070 Base Layer Configuration Register 1 LCDC_BASECFG1 Read/ Write 0x00000000 0x00000074 Base Layer Configuration Register 2 LCDC_BASECFG2 Read/ Write 0x00000000 0x00000078 Base Layer Configuration Register 3 LCDC_BASECFG3 Read/ Write 0x00000000 0x0000007C Base Layer Configuration Register 4 LCDC_BASECFG4 Read/ Write 0x00000000 0x00000080 Base Layer Configuration Register 5 LCDC_BASECFG5 Read/ Write 0x00000000 0x00000084 Base Layer Configuration Register 6 LCDC_BASECFG6 Read/ Write 0x00000000 Reserved – – – 0x00000140 Overlay 1 Channel Enable Register LCDC_OVR1CHER Write-only – 0x00000144 Overlay 1 Channel Disable Register LCDC_OVR1CHDR Write-only – 0x00000148 Overlay 1 Channel Status Register LCDC_OVR1CHSR Read-only 0x00000000 0x0000014C Overlay 1 Interrupt Enable Register LCDC_OVR1IER Write-only – 0x00000150 Overlay 1 Interrupt Disable Register LCDC_OVR1IDR Write-only – 0x00000154 Overlay 1 Interrupt Mask Register LCDC_OVR1IMR Read-only 0x00000000 0x00000158 Overlay 1 Interrupt Status Register LCDC_OVR1ISR Read-only 0x00000000 0x0000015C Overlay 1 DMA Head Register LCDC_OVR1HEAD Read/ Write 0x00000000 0x00000160 Overlay 1 DMA Address Register LCDC_OVR1ADDR Read/ Write 0x00000000 0x00000164 Overlay 1 DMA Control Register LCDC_OVR1CTRL Read/ Write 0x00000000 0x00000168 Overlay 1 DMA Next Register LCDC_OVR1NEXT Read/ Write 0x00000000 0x0000016C Overlay 1 Configuration Register 0 LCDC_OVR1CFG0 Read/ Write 0x00000000 0x00000170 Overlay 1 Configuration Register 1 LCDC_OVR1CFG1 Read/ Write 0x00000000 0x00000174 Overlay 1 Configuration Register 2 LCDC_OVR1CFG2 Read/ Write 0x00000000 0x00000178 Overlay 1 Configuration Register 3 LCDC_OVR1CFG3 Read/ Write 0x00000000 0x0000017C Overlay 1 Configuration Register 4 LCDC_OVR1CFG4 Read/ Write 0x00000000 0x00000180 Overlay 1 Configuration Register 5 LCDC_OVR1CFG5 Read/ Write 0x00000000 0x00000088–0x0000013C DS60001476B-page 766  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset 0x00000184 Overlay 1 Configuration Register 6 LCDC_OVR1CFG6 Read/ Write 0x00000000 0x00000188 Overlay 1 Configuration Register 7 LCDC_OVR1CFG7 Read/ Write 0x00000000 0x0000018C Overlay 1 Configuration Register 8 LCDC_OVR1CFG8 Read/ Write 0x00000000 0x00000190 Overlay 1 Configuration Register 9 LCDC_OVR1CFG9 Read/ Write 0x00000000 Reserved – – – 0x00000240 Overlay 2 Channel Enable Register LCDC_OVR2CHER Write-only – 0x00000244 Overlay 2 Channel Disable Register LCDC_OVR2CHDR Write-only – 0x00000248 Overlay 2 Channel Status Register LCDC_OVR2CHSR Read-only 0x00000000 0x0000024C Overlay 2 Interrupt Enable Register LCDC_OVR2IER Write-only – 0x00000250 Overlay 2 Interrupt Disable Register LCDC_OVR2IDR Write-only – 0x00000254 Overlay 2 Interrupt Mask Register LCDC_OVR2IMR Read-only 0x00000000 0x00000258 Overlay 2 Interrupt Status Register LCDC_OVR2ISR Read-only 0x00000000 0x0000025C Overlay 2 DMA Head Register LCDC_OVR2HEAD Read/ Write 0x00000000 0x00000260 Overlay 2 DMA Address Register LCDC_OVR2ADDR Read/ Write 0x00000000 0x00000264 Overlay 2 DMA Control Register LCDC_OVR2CTRL Read/ Write 0x00000000 0x00000268 Overlay 2 DMA Next Register LCDC_OVR2NEXT Read/ Write 0x00000000 0x0000026C Overlay 2 Configuration Register 0 LCDC_OVR2CFG0 Read/ Write 0x00000000 0x00000270 Overlay 2 Configuration Register 1 LCDC_OVR2CFG1 Read/ Write 0x00000000 0x00000274 Overlay 2 Configuration Register 2 LCDC_OVR2CFG2 Read/ Write 0x00000000 0x00000278 Overlay 2 Configuration Register 3 LCDC_OVR2CFG3 Read/ Write 0x00000000 0x0000027C Overlay 2 Configuration Register 4 LCDC_OVR2CFG4 Read/ Write 0x00000000 0x00000280 Overlay 2 Configuration Register 5 LCDC_OVR2CFG5 Read/ Write 0x00000000 0x00000284 Overlay 2 Configuration Register 6 LCDC_OVR2CFG6 Read/ Write 0x00000000 0x00000288 Overlay 2 Configuration Register 7 LCDC_OVR2CFG7 Read/ Write 0x00000000 0x0000028C Overlay 2 Configuration Register 8 LCDC_OVR2CFG8 Read/ Write 0x00000000 0x00000194–0x0000023C  2017 Microchip Technology Inc. DS60001476B-page 767 SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset Overlay 2 Configuration Register 9 LCDC_OVR2CFG9 Read/ Write 0x00000000 Reserved – – – 0x00000340 High-End Overlay Channel Enable Register LCDC_HEOCHER Write-only – 0x00000344 High-End Overlay Channel Disable Register LCDC_HEOCHDR Write-only – 0x00000348 High-End Overlay Channel Status Register LCDC_HEOCHSR Read-only 0x00000000 0x0000034C High-End Overlay Interrupt Enable Register LCDC_HEOIER Write-only – 0x00000350 High-End Overlay Interrupt Disable Register LCDC_HEOIDR Write-only – 0x00000354 High-End Overlay Interrupt Mask Register LCDC_HEOIMR Read-only 0x00000000 0x00000358 High-End Overlay Interrupt Status Register LCDC_HEOISR Read-only 0x00000000 0x0000035C High-End Overlay DMA Head Register LCDC_HEOHEAD Read/ Write 0x00000000 0x00000360 High-End Overlay DMA Address Register LCDC_HEOADDR Read/ Write 0x00000000 0x00000364 High-End Overlay DMA Control Register LCDC_HEOCTRL Read/ Write 0x00000000 0x00000368 High-End Overlay DMA Next Register LCDC_HEONEXT Read/ Write 0x00000000 0x0000036C High-End Overlay U-UV DMA Head Register LCDC_HEOUHEAD Read/ Write 0x00000000 0x00000370 High-End Overlay U-UV DMA Address Register LCDC_HEOUADDR Read/ Write 0x00000000 0x00000374 High-End Overlay U-UV DMA Control Register LCDC_HEOUCTRL Read/ Write 0x00000000 0x00000378 High-End Overlay U-UV DMA Next Register LCDC_HEOUNEXT Read/ Write 0x00000000 0x0000037C High-End Overlay V DMA Head Register LCDC_HEOVHEAD Read/ Write 0x00000000 0x00000380 High-End Overlay V DMA Address Register LCDC_HEOVADDR Read/ Write 0x00000000 0x00000384 High-End Overlay V DMA Control Register LCDC_HEOVCTRL Read/ Write 0x00000000 0x00000388 High-End Overlay V DMA Next Register LCDC_HEOVNEXT Read/ Write 0x00000000 0x0000038C High-End Overlay Configuration Register 0 LCDC_HEOCFG0 Read/ Write 0x00000000 0x00000390 High-End Overlay Configuration Register 1 LCDC_HEOCFG1 Read/ Write 0x00000000 0x00000394 High-End Overlay Configuration Register 2 LCDC_HEOCFG2 Read/ Write 0x00000000 0x00000398 High-End Overlay Configuration Register 3 LCDC_HEOCFG3 Read/ Write 0x00000000 0x00000290 0x00000294–0x0000033C DS60001476B-page 768  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset 0x0000039C High-End Overlay Configuration Register 4 LCDC_HEOCFG4 Read/ Write 0x00000000 0x000003A0 High-End Overlay Configuration Register 5 LCDC_HEOCFG5 Read/ Write 0x00000000 0x000003A4 High-End Overlay Configuration Register 6 LCDC_HEOCFG6 Read/ Write 0x00000000 0x000003A8 High-End Overlay Configuration Register 7 LCDC_HEOCFG7 Read/ Write 0x00000000 0x000003AC High-End Overlay Configuration Register 8 LCDC_HEOCFG8 Read/ Write 0x00000000 0x000003B0 High-End Overlay Configuration Register 9 LCDC_HEOCFG9 Read/ Write 0x00000000 0x000003B4 High-End Overlay Configuration Register 10 LCDC_HEOCFG10 Read/ Write 0x00000000 0x000003B8 High-End Overlay Configuration Register 11 LCDC_HEOCFG11 Read/ Write 0x00000000 0x000003BC High-End Overlay Configuration Register 12 LCDC_HEOCFG12 Read/ Write 0x00000000 0x000003C0 High-End Overlay Configuration Register 13 LCDC_HEOCFG13 Read/ Write 0x00000000 0x000003C4 High-End Overlay Configuration Register 14 LCDC_HEOCFG14 Read/ Write 0x00000000 0x000003C8 High-End Overlay Configuration Register 15 LCDC_HEOCFG15 Read/ Write 0x00000000 0x000003CC High-End Overlay Configuration Register 16 LCDC_HEOCFG16 Read/ Write 0x00000000 0x000003D0 High-End Overlay Configuration Register 17 LCDC_HEOCFG17 Read/ Write 0x00000000 0x000003D4 High-End Overlay Configuration Register 18 LCDC_HEOCFG18 Read/ Write 0x00000000 0x000003D8 High-End Overlay Configuration Register 19 LCDC_HEOCFG19 Read/ Write 0x00000000 0x000003DC High-End Overlay Configuration Register 20 LCDC_HEOCFG20 Read/ Write 0x00000000 0x000003E0 High-End Overlay Configuration Register 21 LCDC_HEOCFG21 Read/ Write 0x00000000 0x000003E4 High-End Overlay Configuration Register 22 LCDC_HEOCFG22 Read/ Write 0x00000000 0x000003E8 High-End Overlay Configuration Register 23 LCDC_HEOCFG23 Read/ Write 0x00000000 0x000003EC High-End Overlay Configuration Register 24 LCDC_HEOCFG24 Read/ Write 0x00000000 0x000003F0 High-End Overlay Configuration Register 25 LCDC_HEOCFG25 Read/ Write 0x00000000  2017 Microchip Technology Inc. DS60001476B-page 769 SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset 0x000003F4 High-End Overlay Configuration Register 26 LCDC_HEOCFG26 Read/ Write 0x00000000 0x000003F8 High-End Overlay Configuration Register 27 LCDC_HEOCFG27 Read/ Write 0x00000000 0x000003FC High-End Overlay Configuration Register 28 LCDC_HEOCFG28 Read/ Write 0x00000000 0x00000400 High-End Overlay Configuration Register 29 LCDC_HEOCFG29 Read/ Write 0x00000000 0x00000404 High-End Overlay Configuration Register 30 LCDC_HEOCFG30 Read/ Write 0x00000000 0x00000408 High-End Overlay Configuration Register 31 LCDC_HEOCFG31 Read/ Write 0x00000000 0x0000040C High-End Overlay Configuration Register 32 LCDC_HEOCFG32 Read/ Write 0x00000000 0x00000410 High-End Overlay Configuration Register 33 LCDC_HEOCFG33 Read/ Write 0x00000000 0x00000414 High-End Overlay Configuration Register 34 LCDC_HEOCFG34 Read/ Write 0x00000000 0x00000418 High-End Overlay Configuration Register 35 LCDC_HEOCFG35 Read/ Write 0x00000000 0x0000041C High-End Overlay Configuration Register 36 LCDC_HEOCFG36 Read/ Write 0x00000000 0x00000420 High-End Overlay Configuration Register 37 LCDC_HEOCFG37 Read/ Write 0x00000000 0x00000424 High-End Overlay Configuration Register 38 LCDC_HEOCFG38 Read/ Write 0x00000000 0x00000428 High-End Overlay Configuration Register 39 LCDC_HEOCFG39 Read/ Write 0x00000000 0x0000042C High-End Overlay Configuration Register 40 LCDC_HEOCFG40 Read/ Write 0x00000000 0x00000430 High-End Overlay Configuration Register 41 LCDC_HEOCFG41 Read/ Write 0x00000000 Reserved – – – 0x00000540 Post Processing Channel Enable Register LCDC_PPCHER Write-only – 0x00000544 Post Processing Channel Disable Register LCDC_PPCHDR Write-only – 0x00000548 Post Processing Channel Status Register LCDC_PPCHSR Read-only 0x00000000 0x0000054C Post Processing Interrupt Enable Register LCDC_PPIER Write-only – 0x00000550 Post Processing Interrupt Disable Register LCDC_PPIDR Write-only – 0x00000554 Post Processing Interrupt Mask Register LCDC_PPIMR Read-only 0x00000000 0x00000558 Post Processing Interrupt Status Register LCDC_PPISR Read-only 0x00000000 0x0000055C Post Processing Head Register LCDC_PPHEAD Read/ Write 0x00000000 0x00000434–0x0000053C DS60001476B-page 770  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 39-55: Register Mapping (Continued) Offset Register Name Access Reset 0x00000560 Post Processing Address Register LCDC_PPADDR Read/ Write 0x00000000 0x00000564 Post Processing Control Register LCDC_PPCTRL Read/ Write 0x00000000 0x00000568 Post Processing Next Register LCDC_PPNEXT Read/ Write 0x00000000 0x0000056C Post Processing Configuration Register 0 LCDC_PPCFG0 Read/ Write 0x00000000 0x00000570 Post Processing Configuration Register 1 LCDC_PPCFG1 Read/ Write 0x00000000 0x00000574 Post Processing Configuration Register 2 LCDC_PPCFG2 Read/ Write 0x00000000 0x00000578 Post Processing Configuration Register 3 LCDC_PPCFG3 Read/ Write 0x00000000 0x0000057C Post Processing Configuration Register 4 LCDC_PPCFG4 Read/ Write 0x00000000 0x00000580 Post Processing Configuration Register 5 LCDC_PPCFG5 Read/ Write 0x00000000 Reserved – – – Base CLUT Register 0 LCDC_BASECLUT0 Read/ Write 0x00000000 ... ... ... ... 0x000008FC Base CLUT Register 255 LCDC_BASECLUT255 Read/ Write 0x00000000 0x00000A00 Overlay 1 CLUT Register 0 LCDC_OVR1CLUT0 Read/ Write 0x00000000 ... ... ... ... 0x00000DFC Overlay 1 CLUT Register 255 LCDC_OVR1CLUT255 Read/ Write 0x00000000 0x00000E00 Overlay 2 CLUT Register 0 LCDC_OVR2CLUT0 Read/ Write 0x00000000 ... ... ... ... 0x000011FC Overlay 2 CLUT Register 255 LCDC_OVR2CLUT255 Read/ Write 0x00000000 0x00001200 High-End Overlay CLUT Register 0 LCDC_HEOCLUT0 Read/ Write 0x00000000 ... ... ... ... High-End Overlay CLUT Register 255 LCDC_HEOCLUT255 Read/ Write 0x00000000 Reserved – – – 0x00000584–0x000005FC 0x00000600 ... ... ... ... 0x000015FC 0x00001600–0x00001FFC Note 1: The CLUT registers are located in embedded RAM.  2017 Microchip Technology Inc. DS60001476B-page 771 SAMA5D2 SERIES 39.7.1 LCD Controller Configuration Register 0 Name: LCDC_LCDCFG0 Address: 0xF0000000 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 CLKDIV 15 – 14 – 13 CGDISPP 12 – 11 CGDISHEO 10 CGDISOVR2 9 CGDISOVR1 8 CGDISBASE 7 – 6 – 5 – 4 – 3 CLKPWMSEL 2 CLKSEL 1 – 0 CLKPOL CLKPOL: LCD Controller Clock Polarity 0: Data/Control signals are launched on the rising edge of the pixel clock. 1: Data/Control signals are launched on the falling edge of the pixel clock. CLKSEL: LCD Controller Clock Source Selection 0: The asynchronous output stage of the LCD controller is fed by the System Clock. 1: The asynchronous output state of the LCD controller is fed by the 2x System Clock. CLKPWMSEL: LCD Controller PWM Clock Source Selection 0: The slow clock is selected and feeds the PWM module. 1: The system clock is selected and feeds the PWM module. CGDISBASE: Clock Gating Disable Control for the Base Layer 0: Automatic Clock Gating is enabled for the Base Layer. 1: Clock is running continuously. CGDISOVR1: Clock Gating Disable Control for the Overlay 1 Layer 0: Automatic Clock Gating is enabled for the Overlay 1 Layer. 1: Clock is running continuously. CGDISOVR2: Clock Gating Disable Control for the Overlay 2 Layer 0: Automatic Clock Gating is enabled for the Overlay 2 Layer. 1: Clock is running continuously. CGDISHEO: Clock Gating Disable Control for the High-End Overlay 0: Automatic Clock Gating is enabled for the High-End Overlay Layer. 1: Clock is running continuously. CGDISPP: Clock Gating Disable Control for the Post Processing Layer 0: Automatic Clock Gating is enabled for the Post Processing Layer. 1: Clock is running continuously. DS60001476B-page 772  2017 Microchip Technology Inc. SAMA5D2 SERIES CLKDIV: LCD Controller Clock Divider 8-bit width clock divider for pixel clock (LCDPCLK). The pixel clock period formula is: LCDPCLK = source clock / (CLKDIV+2) where source clock is the system clock when CLKSEL is written to ‘0’, and 2x system_clock when CLKSEL is written to ‘1’.  2017 Microchip Technology Inc. DS60001476B-page 773 SAMA5D2 SERIES 39.7.2 LCD Controller Configuration Register 1 Name: LCDC_LCDCFG1 Address: 0xF0000004 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 24 19 18 17 16 11 – 10 – 9 8 3 2 1 VSPW VSPW 15 – 14 – 13 – 12 – 7 6 5 4 HSPW 0 HSPW HSPW: Horizontal Synchronization Pulse Width Width of the LCDHSYNC pulse, given in pixel clock cycles. Width is (HSPW+1) LCDPCLK cycles. VSPW: Vertical Synchronization Pulse Width Width of the LCDVSYNC pulse, given in number of lines. Width is (VSPW+1) lines. DS60001476B-page 774  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.3 LCD Controller Configuration Register 2 Name: LCDC_LCDCFG2 Address: 0xF0000008 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 24 19 18 17 16 11 – 10 – 9 8 3 2 1 VBPW VBPW 15 – 14 – 13 – 12 – 7 6 5 4 VFPW 0 VFPW VFPW: Vertical Front Porch Width This field indicates the number of lines at the end of the Frame. The blanking interval is equal to (VFPW+1) lines. VBPW: Vertical Back Porch Width This field indicates the number of lines at the beginning of the Frame. The blanking interval is equal to VBPW lines.  2017 Microchip Technology Inc. DS60001476B-page 775 SAMA5D2 SERIES 39.7.4 LCD Controller Configuration Register 3 Name: LCDC_LCDCFG3 Address: 0xF000000C Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 24 19 18 17 16 11 – 10 – 9 8 3 2 1 HBPW HBPW 15 – 14 – 13 – 12 – 7 6 5 4 HFPW 0 HFPW HFPW: Horizontal Front Porch Width Number of pixel clock cycles inserted at the end of the active line. The interval is equal to (HFPW+1) LCDPCLK cycles. HBPW: Horizontal Back Porch Width Number of pixel clock cycles inserted at the beginning of the line. The interval is equal to (HBPW+1) LCDPCLK cycles. DS60001476B-page 776  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.5 LCD Controller Configuration Register 4 Name: LCDC_LCDCFG4 Address: 0xF0000010 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 RPF 24 19 18 17 16 11 – 10 9 PPL 8 3 2 1 0 RPF 15 – 14 – 13 – 12 – 7 6 5 4 PPL RPF: Number of Active Row Per Frame Number of active lines in the frame. The frame height is equal to (RPF+1) lines. PPL: Number of Pixels Per Line Number of pixels in the frame. The number of active pixels in the frame is equal to (PPL+1) pixels.  2017 Microchip Technology Inc. DS60001476B-page 777 SAMA5D2 SERIES 39.7.6 LCD Controller Configuration Register 5 Name: LCDC_LCDCFG5 Address: 0xF0000014 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 8 GUARDTIME 15 – 14 – 13 VSPHO 12 VSPSU 11 – 10 PP 9 7 DISPDLY 6 DITHER 5 – 4 DISPPOL 3 VSPDLYE 2 VSPDLYS 1 VSPOL MODE 0 HSPOL HSPOL: Horizontal Synchronization Pulse Polarity 0: Active High 1: Active Low VSPOL: Vertical Synchronization Pulse Polarity 0: Active High 1: Active Low VSPDLYS: Vertical Synchronization Pulse Start 0: The first active edge of the Vertical synchronization pulse is synchronous with the second edge of the horizontal pulse. 1: The first active edge of the Vertical synchronization pulse is synchronous with the first edge of the horizontal pulse. VSPDLYE: Vertical Synchronization Pulse End 0: The second active edge of the Vertical synchronization pulse is synchronous with the second edge of the horizontal pulse. 1: The second active edge of the Vertical synchronization pulse is synchronous with the first edge of the horizontal pulse. DISPPOL: Display Signal Polarity 0: Active High 1: Active Low DITHER: LCD Controller Dithering 0: Dithering logical unit is disabled 1: Dithering logical unit is activated DISPDLY: LCD Controller Display Power Signal Synchronization 0: The LCDDISP signal is asserted synchronously with the second active edge of the horizontal pulse. 1: The LCDDISP signal is asserted asynchronously with both edges of the horizontal pulse. DS60001476B-page 778  2017 Microchip Technology Inc. SAMA5D2 SERIES MODE: LCD Controller Output Mode Value Name Description 0 OUTPUT_12BPP LCD Output mode is set to 12 bits per pixel 1 OUTPUT_16BPP LCD Output mode is set to 16 bits per pixel 2 OUTPUT_18BPP LCD Output mode is set to 18 bits per pixel 3 OUTPUT_24BPP LCD Output mode is set to 24 bits per pixel PP: Post Processing Enable 0: The blended pixel is pushed into the output FIFO. 1: The blended pixel is written back to memory, the post-processing stage is enabled. VSPSU: LCD Controller Vertical synchronization Pulse Setup Configuration 0: The vertical synchronization pulse is asserted synchronously with horizontal pulse edge. 1: The vertical synchronization pulse is asserted one pixel clock cycle before the horizontal pulse. VSPHO: LCD Controller Vertical synchronization Pulse Hold Configuration 0: The vertical synchronization pulse is asserted synchronously with horizontal pulse edge. 1: The vertical synchronization pulse is held active one pixel clock cycle after the horizontal pulse. GUARDTIME: LCD DISPLAY Guard Time Number of frames inserted during startup before LCDDISP assertion. Number of frames inserted after LCDDISP reset.  2017 Microchip Technology Inc. DS60001476B-page 779 SAMA5D2 SERIES 39.7.7 LCD Controller Configuration Register 6 Name: LCDC_LCDCFG6 Address: 0xF0000018 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 – 2 1 PWMPS 0 PWMCVAL 7 – 6 – 5 – 4 PWMPOL PWMPS: PWM Clock Prescaler Selects the configuration of the counter prescaler module. Value Name Description 000 DIV_1 The counter advances at a rate of fCOUNTER = fPWM_SELECTED_CLOCK 001 DIV_2 The counter advances at a rate of fCOUNTER = fPWM_SELECTED_CLOCK/2 010 DIV_4 The counter advances at a rate of fCOUNTER = fPWM_SELECTED_CLOCK/4 011 DIV_8 The counter advances at a rate of fCOUNTER = fPWM_SELECTED_CLOCK/8 100 DIV_16 The counter advances at a rate of fCOUNTER = fPWM_SELECTED_CLOCK/16 101 DIV_32 The counter advances at a of rate fCOUNTER = fPWM_SELECTED_CLOCK/32 110 DIV_64 The counter advances at a of rate fCOUNTER = fPWM_SELECTED_CLOCK/64 PWMPOL: LCD Controller PWM Signal Polarity This bit defines the polarity of the PWM output signal. 0: The output pulses are low level. 1: The output pulses are high level (the output is high whenever the value in the counter is less than value CVAL). PWMCVAL: LCD Controller PWM Compare Value PWM compare value. Used to adjust the analog value obtained after an external filter to control the contrast of the display. DS60001476B-page 780  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.8 LCD Controller Enable Register Name: LCDC_LCDEN Address: 0xF0000020 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 PWMEN 2 DISPEN 1 SYNCEN 0 CLKEN CLKEN: LCD Controller Pixel Clock Enable 0: No effect 1: Pixel clock logical unit is activated. SYNCEN: LCD Controller Horizontal and Vertical Synchronization Enable 0: No effect 1: Both horizontal and vertical synchronization (LCDVSYNC and LCDHSYNC) signals are generated. DISPEN: LCD Controller DISP Signal Enable 0: No effect 1: LCDDISP signal is generated. PWMEN: LCD Controller Pulse Width Modulation Enable 0: No effect 1: PWM is enabled.  2017 Microchip Technology Inc. DS60001476B-page 781 SAMA5D2 SERIES 39.7.9 LCD Controller Disable Register Name: LCDC_LCDDIS Address: 0xF0000024 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 PWMRST 10 DISPRST 9 SYNCRST 8 CLKRST 7 – 6 – 5 – 4 – 3 PWMDIS 2 DISPDIS 1 SYNCDIS 0 CLKDIS CLKDIS: LCD Controller Pixel Clock Disable 0: No effect. 1: Disables the pixel clock. SYNCDIS: LCD Controller Horizontal and Vertical Synchronization Disable 0: No effect. 1: Disables the synchronization signals after the end of the frame. DISPDIS: LCD Controller DISP Signal Disable 0: No effect. 1: Disables the DISP signal. PWMDIS: LCD Controller Pulse Width Modulation Disable 0: No effect. 1: Disables the pulse width modulation signal. CLKRST: LCD Controller Clock Reset 0: No effect. 1: Resets the pixel clock generator module. The pixel clock duty cycle may be violated. SYNCRST: LCD Controller Horizontal and Vertical Synchronization Reset 0: No effect. 1: Resets the timing engine. The horizontal and vertical pulse widths are both violated. DISPRST: LCD Controller DISP Signal Reset 0: No effect. 1: Resets the DISP signal. PWMRST: LCD Controller PWM Reset 0: No effect. 1: Resets the PWM module. The duty cycle may be violated. DS60001476B-page 782  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.10 LCD Controller Status Register Name: LCDC_LCDSR Address: 0xF0000028 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 SIPSTS 3 PWMSTS 2 DISPSTS 1 LCDSTS 0 CLKSTS CLKSTS: Clock Status 0: Pixel clock is disabled. 1: Pixel clock is running. LCDSTS: LCD Controller Synchronization status 0: Timing engine is disabled. 1: Timing engine is running. DISPSTS: LCD Controller DISP Signal Status 0: DISP is disabled. 1: DISP signal is activated. PWMSTS: LCD Controller PWM Signal Status 0: PWM is disabled. 1: PWM signal is activated. SIPSTS: Synchronization In Progress 0: Clock domain synchronization is terminated. 1: Synchronization is in progress. Access to the registers LCDC_LCDCCFG[0..6], LCDC_LCDEN and LCDC_LCDDIS has no effect.  2017 Microchip Technology Inc. DS60001476B-page 783 SAMA5D2 SERIES 39.7.11 LCD Controller Interrupt Enable Register Name: LCDC_LCDIER Address: 0xF000002C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 PPIE 12 – 11 HEOIE 10 OVR2IE 9 OVR1IE 8 BASEIE 7 – 6 – 5 – 4 FIFOERRIE 3 – 2 DISPIE 1 DISIE 0 SOFIE SOFIE: Start of Frame Interrupt Enable 0: No effect. 1: Enables the interrupt. DISIE: LCD Disable Interrupt Enable 0: No effect. 1: Enables the interrupt. DISPIE: Powerup/Powerdown Sequence Terminated Interrupt Enable 0: No effect. 1: Enables the interrupt. FIFOERRIE: Output FIFO Error Interrupt Enable 0: No effect. 1: Enables the interrupt. BASEIE: Base Layer Interrupt Enable 0: No effect. 1: Enables the interrupt. OVR1IE: Overlay 1 Interrupt Enable 0: No effect. 1: Enables the interrupt. OVR2IE: Overlay 2 Interrupt Enable 0: No effect. 1: Enables the interrupt. HEOIE: High-End Overlay Interrupt Enable 0: No effect. 1: Enables the interrupt. DS60001476B-page 784  2017 Microchip Technology Inc. SAMA5D2 SERIES PPIE: Post Processing Interrupt Enable 0: No effect. 1: Enables the interrupt.  2017 Microchip Technology Inc. DS60001476B-page 785 SAMA5D2 SERIES 39.7.12 LCD Controller Interrupt Disable Register Name: LCDC_LCDIDR Address: 0xF0000030 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 PPID 12 – 11 HEOID 10 OVR2ID 9 OVR1ID 8 BASEID 7 – 6 – 5 – 4 FIFOERRID 3 – 2 DISPID 1 DISID 0 SOFID SOFID: Start of Frame Interrupt Disable 0: No effect. 1: Disables the interrupt. DISID: LCD Disable Interrupt Disable 0: No effect. 1: Disables the interrupt. DISPID: Powerup/Powerdown Sequence Terminated Interrupt Disable 0: No effect. 1: Disables the interrupt. FIFOERRID: Output FIFO Error Interrupt Disable 0: No effect. 1: Disables the interrupt. BASEID: Base Layer Interrupt Disable 0: No effect. 1: Disables the interrupt. OVR1ID: Overlay 1 Interrupt Disable 0: No effect. 1: Disables the interrupt. OVR2ID: Overlay 2 Interrupt Disable 0: No effect. 1: Disables the interrupt. HEOID: High-End Overlay Interrupt Disable 0: No effect. 1: Disables the interrupt. DS60001476B-page 786  2017 Microchip Technology Inc. SAMA5D2 SERIES PPID: Post Processing Interrupt Disable 0: No effect 1: Disables the interrupt  2017 Microchip Technology Inc. DS60001476B-page 787 SAMA5D2 SERIES 39.7.13 LCD Controller Interrupt Mask Register Name: LCDC_LCDIMR Address: 0xF0000034 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 PPIM 12 – 11 HEOIM 10 OVR2IM 9 OVR1IM 8 BASEIM 7 – 6 – 5 – 4 FIFOERRIM 3 – 2 DISPIM 1 DISIM 0 SOFIM SOFIM: Start of Frame Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. DISIM: LCD Disable Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. DISPIM: Powerup/Powerdown Sequence Terminated Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. FIFOERRIM: Output FIFO Error Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. BASEIM: Base Layer Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. OVR1IM: Overlay 1 Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. OVR2IM: Overlay 2 Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. HEOIM: High-End Overlay Interrupt Mask 0: Interrupt source is disabled. 1: Interrupt source is enabled. PPIM: Post Processing Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DS60001476B-page 788  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.14 LCD Controller Interrupt Status Register Name: LCDC_LCDISR Address: 0xF0000038 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 PP 12 – 11 HEO 10 OVR2 9 OVR1 8 BASE 7 – 6 – 5 – 4 FIFOERR 3 – 2 DISP 1 DIS 0 SOF SOF: Start of Frame Interrupt Status 0: No detection since last read of LCDC_LCDISR. 1: Indicates that a start of frame event has been detected. This flag is reset after a read operation. DIS: LCD Disable Interrupt Status 0: Horizontal and vertical timing generator has not yet been disabled. 1: Indicates that the horizontal and vertical timing generator has been disabled. This flag is reset after a read operation. DISP: Powerup/Powerdown Sequence Terminated Interrupt Status 0: Powerup sequence or powerdown sequence has not yet terminated. 1: Indicates the powerup sequence or powerdown sequence has terminated. This flag is reset after a read operation. FIFOERR: Output FIFO Error 0: No underflow has occurred in the output FIFO since last read of LCDC_LCDISR. 1: Indicates that an underflow has occurred in the output FIFO. This flag is reset after a read operation. BASE: Base Layer Raw Interrupt Status 0: No base layer interrupt detected since last read of LCDC_BASEISR. 1: Indicates that a base layer interrupt is pending. This flag is reset as soon as the LCDC_BASEISR is read. OVR1: Overlay 1 Raw Interrupt Status 0: No Overlay 1 layer interrupt detected since last read of LCDC_OVR1ISR. 1: Indicates that an Overlay 1 layer interrupt is pending. This flag is reset as soon as the LCDC_OVR1ISR is read. OVR2: Overlay 2 Raw Interrupt Status 0: No Overlay 2 layer interrupt detected since last read of LCDC_OVR2ISR. 1: Indicates that an Overlay 2 layer interrupt is pending. This flag is reset as soon as the LCDC_OVR2ISR is read. HEO: High-End Overlay Raw Interrupt Status 0: No High-End layer interrupt detected since last read of LCDC_HEOISR. 1: Indicates that a High-End layer interrupt is pending. This flag is reset as soon as the LCDC_HEOISR is read. PP: Post Processing Raw Interrupt Status 0: No Post Processing interrupt detected since last read of LCDC_PPISR 1: Indicates that Post Processing interrupt is pending. This flag is reset as soon as the LCDC_PPISR is read.  2017 Microchip Technology Inc. DS60001476B-page 789 SAMA5D2 SERIES 39.7.15 LCD Controller Attribute Register Name: LCDC_ATTR Address: 0xF000003C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 PPA2Q 12 – 11 HEOA2Q 10 OVR2A2Q 9 OVR1A2Q 8 BASEA2Q 7 – 6 – 5 PP 4 – 3 HEO 2 OVR2 1 OVR1 0 BASE BASE: Base Layer Update Attribute 0: No effect. 1: Update the BASE window attributes. OVR1: Overlay 1 Update Attribute 0: No effect. 1: Update the OVR1 window attribute. OVR2: Overlay 2 Update Attribute 0: No effect. 1: Update the OVR2 window attribute. HEO: High-End Overlay Update Attribute 0: No effect. 1: Update the HEO window attribute. PP: Post-Processing Update Attribute 0: No effect. 1: Update the PP window attribute. BASEA2Q: Base Layer Update Add To Queue 0: No effect. 1: Add the descriptor pointed to by the LCDC_BASEHEAD register to the descriptor list. OVR1A2Q: Overlay 1 Update Add To Queue 0: No effect. 1: Add the descriptor pointed to by the LCDC_OVR1HEAD register to the descriptor list. OVR2A2Q: Overlay 2 Update Add to Queue 0: No effect. 1: Add the descriptor pointed to by the LCDC_OVR2HEAD register to the descriptor list. HEOA2Q: High-End Overlay Update Add To Queue 0: No effect. 1: Add the descriptor pointed to by the LCDC_HEOHEAD register to the descriptor list. DS60001476B-page 790  2017 Microchip Technology Inc. SAMA5D2 SERIES PPA2Q: Post-Processing Update Add To Queue 0: No effect. 1: Add the descriptor pointed to by the LCDC_PPHEAD register to the descriptor list.  2017 Microchip Technology Inc. DS60001476B-page 791 SAMA5D2 SERIES 39.7.16 Base Layer Channel Enable Register Name: LCDC_BASECHER Address: 0xF0000040 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QEN 1 UPDATEEN 0 CHEN CHEN: Channel Enable 0: No effect 1: Enables the DMA channel UPDATEEN: Update Overlay Attributes Enable 0: No effect 1: Updates windows attributes on the next start of frame. A2QEN: Add To Queue Enable 0: No effect 1: Indicates that a valid descriptor has been written to memory, its memory location should be written to the DMA head pointer. The A2QSR status bit is set to one, and it is reset by hardware as soon as the descriptor pointed to by the DMA head pointer is added to the list. DS60001476B-page 792  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.17 Base Layer Channel Disable Register Name: LCDC_BASECHDR Address: 0xF0000044 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CHRST 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CHDIS CHDIS: Channel Disable 0: No effect 1: Disables the layer at the end of the current frame. The frame is completed. CHRST: Channel Reset 0: No effect 1: Resets the layer immediately. The frame is aborted.  2017 Microchip Technology Inc. DS60001476B-page 793 SAMA5D2 SERIES 39.7.18 Base Layer Channel Status Register Name: LCDC_BASECHSR Address: 0xF0000048 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QSR 1 UPDATESR 0 CHSR CHSR: Channel Status 0: Layer disabled 1: Layer enabled UPDATESR: Update Overlay Attributes In Progress Status 0: No update pending 1: Overlay attributes will be updated on the next frame A2QSR: Add To Queue Status 0: Add to queue not pending 1: Add to queue pending DS60001476B-page 794  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.19 Base Layer Interrupt Enable Register Name: LCDC_BASEIER Address: 0xF000004C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled DONE: End of List Interrupt Enable 0: No effect 1: Interrupt source is enabled OVR: Overflow Interrupt Enable 0: No effect 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 795 SAMA5D2 SERIES 39.7.20 Base Layer Interrupt Disable Register Name: LCDC_BASEIDR Address: 0xF0000050 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Disable 0: No effect 1: Interrupt source is disabled DSCR: Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled ADD: Head Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled DONE: End of List Interrupt Disable 0: No effect 1: Interrupt source is disabled OVR: Overflow Interrupt Disable 0: No effect 1: Interrupt source is disabled DS60001476B-page 796  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.21 Base Layer Interrupt Mask Register Name: LCDC_BASEIMR Address: 0xF0000054 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DONE: End of List Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled OVR: Overflow Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 797 SAMA5D2 SERIES 39.7.22 Base Layer Interrupt Status Register Name: LCDC_BASEISR Address: 0xF0000058 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer 0: No end of DMA transfer has been detected since last read of LCDC_BASEISR 1: End of Transfer has been detected. This flag is reset after a read operation. DSCR: DMA Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_BASEISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. ADD: Head Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_BASEISR 1: The descriptor pointed to by the LCDC_BASEHEAD register has been loaded successfully. This flag is reset after a read operation. DONE: End of List Detected 0: No End of List condition occurred since last read of LCDC_BASEISR 1: End of List condition has occurred. This flag is reset after a read operation. OVR: Overflow Detected 0: No overflow occurred since last read of LCDC_BASEISR 1: An overflow occurred. This flag is reset after a read operation. DS60001476B-page 798  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.23 Base DMA Head Register Name: LCDC_BASEHEAD Address: 0xF000005C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – HEAD 23 22 21 20 HEAD 15 14 13 12 HEAD 7 6 5 4 HEAD HEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 799 SAMA5D2 SERIES 39.7.24 Base DMA Address Register Name: LCDC_BASEADDR Address: 0xF0000060 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: DMA Transfer Start Address Frame buffer base address DS60001476B-page 800  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.25 Base DMA Control Register Name: LCDC_BASECTRL Address: 0xF0000064 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONEIEN 4 ADDIEN 3 DSCRIEN 2 DMAIEN 1 LFETCH 0 DFETCH DFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled 1: Transfer Descriptor fetch is enabled LFETCH: Lookup Table Fetch Enable 0: Lookup Table DMA fetch is disabled 1: Lookup Table DMA fetch is enabled DMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled 1: DMA transfer completed interrupt is disabled DSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled 1: Transfer descriptor loaded interrupt is disabled ADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled 1: Transfer descriptor added to queue interrupt is enabled DONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled 1: End of list interrupt is enabled  2017 Microchip Technology Inc. DS60001476B-page 801 SAMA5D2 SERIES 39.7.26 Base DMA Next Register Name: LCDC_BASENEXT Address: 0xF0000068 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NEXT 23 22 21 20 NEXT 15 14 13 12 NEXT 7 6 5 4 NEXT NEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 802  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.27 Base Layer Configuration Register 0 Name: LCDC_BASECFG0 Address: 0xF000006C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DLBO 7 – 6 – 5 4 3 – 2 – 1 – 0 SIF BLEN SIF: Source Interface 0: Base Layer data is retrieved through AHB interface 0. 1: Base Layer data is retrieved through AHB interface 1. BLEN: AHB Burst Length Value Name Description 0 AHB_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. DLBO: Defined Length Burst Only For Channel Bus Transaction 0: Undefined length INCR burst is used for a burst of 2 and 3 beats. 1: Only Defined Length burst is used (SINGLE, INCR4, INCR8 and INCR16).  2017 Microchip Technology Inc. DS60001476B-page 803 SAMA5D2 SERIES 39.7.28 Base Layer Configuration Register 1 Name: LCDC_BASECFG1 Address: 0xF0000070 Access: Read/Write 31 – 30 – 29 – 28 - 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 – 10 – 9 8 3 – 2 – 1 – – 7 6 5 4 RGBMODE CLUTMODE 0 CLUTEN CLUTEN: Color Lookup Table Mode Enable 0: RGB mode is selected. 1: Color Lookup Table mode is selected. RGBMODE: RGB Mode Input Selection Value Name Description 0 12BPP_RGB_444 12 bpp RGB 444 1 16BPP_ARGB_4444 16 bpp ARGB 4444 2 16BPP_RGBA_4444 16 bpp RGBA 4444 3 16BPP_RGB_565 16 bpp RGB 565 4 16BPP_TRGB_1555 16 bpp TRGB 1555 5 18BPP_RGB_666 18 bpp RGB 666 6 18BPP_RGB_666PACKED 18 bpp RGB 666 PACKED 7 19BPP_TRGB_1666 19 bpp TRGB 1666 8 19BPP_TRGB_PACKED 19 bpp TRGB 1666 PACKED 9 24BPP_RGB_888 24 bpp RGB 888 10 24BPP_RGB_888_PACKED 24 bpp RGB 888 PACKED 11 25BPP_TRGB_1888 25 bpp TRGB 1888 12 32BPP_ARGB_8888 32 bpp ARGB 8888 13 32BPP_RGBA_8888 32 bpp RGBA 8888 CLUTMODE: Color Lookup Table Mode Input Selection Value Name Description 0 CLUT_1BPP Color Lookup Table mode set to 1 bit per pixel 1 CLUT_2BPP Color Lookup Table mode set to 2 bits per pixel 2 CLUT_4BPP Color Lookup Table mode set to 4 bits per pixel 3 CLUT_8BPP Color Lookup Table mode set to 8 bits per pixel DS60001476B-page 804  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.29 Base Layer Configuration Register 2 Name: LCDC_BASECFG2 Address: 0xF0000074 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 XSTRIDE 23 22 21 20 XSTRIDE 15 14 13 12 XSTRIDE 7 6 5 4 XSTRIDE XSTRIDE: Horizontal Stride XSTRIDE represents the memory offset, in bytes, between two rows of the image memory.  2017 Microchip Technology Inc. DS60001476B-page 805 SAMA5D2 SERIES 39.7.30 Base Layer Configuration Register 3 Name: LCDC_BASECFG3 Address: 0xF0000078 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RDEF 15 14 13 12 GDEF 7 6 5 4 BDEF RDEF: Red Default Default Red color when the Base DMA channel is disabled GDEF: Green Default Default Green color when the Base DMA channel is disabled BDEF: Blue Default Default Blue color when the Base DMA channel is disabled DS60001476B-page 806  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.31 Base Layer Configuration Register 4 Name: LCDC_BASECFG4 Address: 0xF000007C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 DISCEN 10 – 9 REP 8 DMA 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DMA: Use DMA Data Path 0: The default color is used on the Base Layer. 1: The DMA channel retrieves the pixels stream from the memory. REP: Use Replication logic to expand RGB color to 24 bits 0: When the selected pixel depth is less than 24 bpp the pixel is shifted and least significant bits are set to 0. 1: When the selected pixel depth is less than 24 bpp the pixel is shifted and the least significant bit replicates the msb. DISCEN: Discard Area Enable 0: The whole frame is retrieved from memory. 1: The DMA channel discards the area located at screen coordinate {DISCXPOS, DISCYPOS}.  2017 Microchip Technology Inc. DS60001476B-page 807 SAMA5D2 SERIES 39.7.32 Base Layer Configuration Register 5 Name: LCDC_BASECFG5 Address: 0xF0000080 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 DISCYPOS 24 19 18 17 16 11 10 9 DISCXPOS 8 3 2 1 0 DISCYPOS 15 – 14 – 13 – 12 – 7 6 5 4 DISCXPOS DISCXPOS: Discard Area Horizontal Coordinate Horizontal Position of the Discard Area DISCYPOS: Discard Area Vertical Coordinate Vertical Position of the Discard Area DS60001476B-page 808  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.33 Base Layer Configuration Register 6 Name: LCDC_BASECFG6 Address: 0xF0000084 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 DISCYSIZE 24 19 18 17 16 11 10 9 DISCXSIZE 8 3 2 1 0 DISCYSIZE 15 – 14 – 13 – 12 – 7 6 5 4 DISCXSIZE DISCXSIZE: Discard Area Horizontal Size Discard Horizontal size in pixels. The Discard size is set to (DISCXSIZE + 1) pixels horizontally. DISCYSIZE: Discard Area Vertical Size Discard Vertical size in pixels. The Discard size is set to (DISCYSIZE + 1) pixels vertically.  2017 Microchip Technology Inc. DS60001476B-page 809 SAMA5D2 SERIES 39.7.34 Overlay 1 Channel Enable Register Name: LCDC_OVR1CHER Address: 0xF0000140 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QEN 1 UPDATEEN 0 CHEN CHEN: Channel Enable 0: No effect 1: Enables the DMA channel UPDATEEN: Update Overlay Attributes Enable 0: No effect 1: Updates window attributes (size, alpha blending, etc.) on the next start of frame. A2QEN: Add To Queue Enable 0: No effect 1: Indicates that a valid descriptor has been written to memory, its memory location should be written to the DMA head pointer. The A2QSR status bit is set to one, and it is reset by hardware as soon as the descriptor pointed to by the DMA head pointer is added to the list. DS60001476B-page 810  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.35 Overlay 1 Channel Disable Register Name: LCDC_OVR1CHDR Address: 0xF0000144 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CHRST 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CHDIS CHDIS: Channel Disable 0: No effect 1: Disables the layer at the end of the current frame. The frame is completed. CHRST: Channel Reset 0: No effect 1: Resets the layer immediately. The frame is aborted.  2017 Microchip Technology Inc. DS60001476B-page 811 SAMA5D2 SERIES 39.7.36 Overlay 1 Channel Status Register Name: LCDC_OVR1CHSR Address: 0xF0000148 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QSR 1 UPDATESR 0 CHSR CHSR: Channel Status 0: Layer disabled 1: Layer enabled UPDATESR: Update Overlay Attributes In Progress Status 0: No update pending 1: Overlay attributes will be updated on the next frame A2QSR: Add To Queue Status 0: Add to queue not pending 1: Add to queue pending DS60001476B-page 812  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.37 Overlay 1 Interrupt Enable Register Name: LCDC_OVR1IER Address: 0xF000014C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled DONE: End of List Interrupt Enable 0: No effect 1: Interrupt source is enabled OVR: Overflow Interrupt Enable 0: No effect 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 813 SAMA5D2 SERIES 39.7.38 Overlay 1 Interrupt Disable Register Name: LCDC_OVR1IDR Address: 0xF0000150 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Disable 0: No effect 1: Interrupt source is disabled DSCR: Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled ADD: Head Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled DONE: End of List Interrupt Disable 0: No effect 1: Interrupt source is disabled OVR: Overflow Interrupt Disable 0: No effect 1: Interrupt source is disabled DS60001476B-page 814  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.39 Overlay 1 Interrupt Mask Register Name: LCDC_OVR1IMR Address: 0xF0000154 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DONE: End of List Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled OVR: Overflow Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 815 SAMA5D2 SERIES 39.7.40 Overlay 1 Interrupt Status Register Name: LCDC_OVR1ISR Address: 0xF0000158 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer 0: No End of Transfer has been detected since last read of LCDC_OVR1ISR 1: End of Transfer has been detected. This flag is reset after a read operation. DSCR: DMA Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_OVR1ISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. ADD: Head Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_OVR1ISR 1: The descriptor pointed to by the LCDC_OVR1HEAD register has been loaded successfully. This flag is reset after a read operation. DONE: End of List Detected 0: No End of List condition has occurred since last read of LCDC_OVR1ISR 1: End of List condition has occurred. This flag is reset after a read operation. OVR: Overflow Detected 0: No overflow occurred since last read of LCDC_OVR1ISR 1: An overflow occurred. This flag is reset after a read operation. DS60001476B-page 816  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.41 Overlay 1 Head Register Name: LCDC_OVR1HEAD Address: 0xF000015C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – HEAD 23 22 21 20 HEAD 15 14 13 12 HEAD 7 6 5 4 HEAD HEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 817 SAMA5D2 SERIES 39.7.42 Overlay 1 Address Register Name: LCDC_OVR1ADDR Address: 0xF0000160 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: DMA Transfer Overlay 1 Address Overlay 1 frame buffer base address DS60001476B-page 818  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.43 Overlay 1 Control Register Name: LCDC_OVR1CTRL Address: 0xF0000164 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONEIEN 4 ADDIEN 3 DSCRIEN 2 DMAIEN 1 LFETCH 0 DFETCH DFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled 1: Transfer Descriptor fetch is enabled LFETCH: Lookup Table Fetch Enable 0: Lookup Table DMA fetch is disabled 1: Lookup Table DMA fetch is enabled DMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled 1: DMA transfer completed interrupt is disabled DSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled 1: Transfer descriptor loaded interrupt is disabled ADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled 1: Transfer descriptor added to queue interrupt is enabled DONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled 1: End of list interrupt is enabled  2017 Microchip Technology Inc. DS60001476B-page 819 SAMA5D2 SERIES 39.7.44 Overlay 1 Next Register Name: LCDC_OVR1NEXT Address: 0xF0000168 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NEXT 23 22 21 20 NEXT 15 14 13 12 NEXT 7 6 5 4 NEXT NEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 820  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.45 Overlay 1 Configuration Register 0 Name: LCDC_OVR1CFG0 Address: 0xF000016C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 LOCKDIS 12 ROTDIS 11 – 10 – 9 – 8 DLBO 7 – 6 – 5 4 3 – 2 – 1 – 0 SIF BLEN SIF: Source Interface 0: Base Layer data is retrieved through AHB interface 0. 1: Base Layer data is retrieved through AHB interface 1. BLEN: AHB Burst Length Value Name Description 0 AHB_BLEN_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_BLEN_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_BLEN_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_BLEN_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. DLBO: Defined Length Burst Only for Channel Bus Transaction 0: Undefined length INCR burst is used for a burst of 2 and 3 beats. 1: Only Defined Length burst is used (SINGLE, INCR4, INCR8 and INCR16). ROTDIS: Hardware Rotation Optimization Disable 0: Rotation optimization is enabled. 1: Rotation optimization is disabled. LOCKDIS: Hardware Rotation Lock Disable 0: AHB lock signal is asserted when a rotation is performed. 1: AHB lock signal is cleared when a rotation is performed.  2017 Microchip Technology Inc. DS60001476B-page 821 SAMA5D2 SERIES 39.7.46 Overlay 1 Configuration Register 1 Name: LCDC_OVR1CFG1 Address: 0xF0000170 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 – 2 – 1 – RGBMODE CLUTMODE 0 CLUTEN CLUTEN: Color Lookup Table Mode Enable 0: RGB mode is selected. 1: Color Lookup Table mode is selected. RGBMODE: RGB Mode Input Selection Value Name Description 0 12BPP_RGB_444 12 bpp RGB 444 1 16BPP_ARGB_4444 16 bpp ARGB 4444 2 16BPP_RGBA_4444 16 bpp RGBA 4444 3 16BPP_RGB_565 16 bpp RGB 565 4 16BPP_TRGB_1555 16 bpp TRGB 1555 5 18BPP_RGB_666 18 bpp RGB 666 6 18BPP_RGB_666PACKED 18 bpp RGB 666 PACKED 7 19BPP_TRGB_1666 19 bpp TRGB 1666 8 19BPP_TRGB_PACKED 19 bpp TRGB 1666 PACKED 9 24BPP_RGB_888 24 bpp RGB 888 10 24BPP_RGB_888_PACKED 24 bpp RGB 888 PACKED 11 25BPP_TRGB_1888 25 bpp TRGB 1888 12 32BPP_ARGB_8888 32 bpp ARGB 8888 13 32BPP_RGBA_8888 32 bpp RGBA 8888 DS60001476B-page 822  2017 Microchip Technology Inc. SAMA5D2 SERIES CLUTMODE: Color Lookup Table Mode Input Selection Value Name Description 0 CLUT_1BPP Color Lookup Table mode set to 1 bit per pixel 1 CLUT_2BPP Color Lookup Table mode set to 2 bits per pixel 2 CLUT_4BPP Color Lookup Table mode set to 4 bits per pixel 3 CLUT_8BPP Color Lookup Table mode set to 8 bits per pixel  2017 Microchip Technology Inc. DS60001476B-page 823 SAMA5D2 SERIES 39.7.47 Overlay 1 Configuration Register 2 Name: LCDC_OVR1CFG2 Address: 0xF0000174 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YPOS 24 19 18 17 16 11 – 10 9 XPOS 8 3 2 1 0 YPOS 15 – 14 – 13 – 12 – 7 6 5 4 XPOS XPOS: Horizontal Window Position Overlay 1 Horizontal window position. YPOS: Vertical Window Position Overlay 1 Vertical window position. DS60001476B-page 824  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.48 Overlay 1 Configuration Register 3 Name: LCDC_OVR1CFG3 Address: 0xF0000178 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YSIZE 24 19 18 17 16 11 – 10 9 XSIZE 8 3 2 1 0 YSIZE 15 – 14 – 13 – 12 – 7 6 5 4 XSIZE XSIZE: Horizontal Window Size Overlay 1 window width in pixels. The window width is set to (XSIZE + 1). The following constraint must be met: XPOS + XSIZE ≤ PPL YSIZE: Vertical Window Size Overlay 1 window height in pixels. The window height is set to (YSIZE + 1). The following constraint must be met: YPOS + YSIZE ≤ RPF  2017 Microchip Technology Inc. DS60001476B-page 825 SAMA5D2 SERIES 39.7.49 Overlay 1 Configuration Register 4 Name: LCDC_OVR1CFG4 Address: 0xF000017C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 XSTRIDE 23 22 21 20 XSTRIDE 15 14 13 12 XSTRIDE 7 6 5 4 XSTRIDE XSTRIDE: Horizontal Stride XSTRIDE represents the memory offset, in bytes, between two rows of the image memory. DS60001476B-page 826  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.50 Overlay 1 Configuration Register 5 Name: LCDC_OVR1CFG5 Address: 0xF0000180 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 PSTRIDE 23 22 21 20 PSTRIDE 15 14 13 12 PSTRIDE 7 6 5 4 PSTRIDE PSTRIDE: Pixel Stride PSTRIDE represents the memory offset, in bytes, between two pixels of the image.  2017 Microchip Technology Inc. DS60001476B-page 827 SAMA5D2 SERIES 39.7.51 Overlay 1 Configuration Register 6 Name: LCDC_OVR1CFG6 Address: 0xF0000184 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RDEF 15 14 13 12 GDEF 7 6 5 4 BDEF RDEF: Red Default Default Red color when the Overlay 1 DMA channel is disabled. GDEF: Green Default Default Green color when the Overlay 1 DMA channel is disabled. BDEF: Blue Default Default Blue color when the Overlay 1 DMA channel is disabled. DS60001476B-page 828  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.52 Overlay 1 Configuration Register 7 Name: LCDC_OVR1CFG7 Address: 0xF0000188 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RKEY 15 14 13 12 GKEY 7 6 5 4 BKEY RKEY: Red Color Component Chroma Key Reference Red chroma key used to match the Red color of the current overlay. GKEY: Green Color Component Chroma Key Reference Green chroma key used to match the Green color of the current overlay. BKEY: Blue Color Component Chroma Key Reference Blue chroma key used to match the Blue color of the current overlay.  2017 Microchip Technology Inc. DS60001476B-page 829 SAMA5D2 SERIES 39.7.53 Overlay 1 Configuration Register 8 Name: LCDC_OVR1CFG8 Address: 0xF000018C Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RMASK 15 14 13 12 GMASK 7 6 5 4 BMASK RMASK: Red Color Component Chroma Key Mask Red Mask used when the compare function is used. If a bit is set then this bit is compared. GMASK: Green Color Component Chroma Key Mask Green Mask used when the compare function is used. If a bit is set then this bit is compared. BMASK: Blue Color Component Chroma Key Mask Blue Mask used when the compare function is used. If a bit is set then this bit is compared. DS60001476B-page 830  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.54 Overlay 1 Configuration Register 9 Name: LCDC_OVR1CFG9 Address: 0xF0000190 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 GA 15 – 14 – 13 – 12 – 11 – 10 DSTKEY 9 REP 8 DMA 7 OVR 6 LAEN 5 GAEN 4 REVALPHA 3 ITER 2 ITER2BL 1 INV 0 CRKEY CRKEY: Blender Chroma Key Enable 0: Chroma key matching is disabled. 1: Chroma key matching is enabled. INV: Blender Inverted Blender Output Enable 0: Iterated pixel is the blended pixel. 1: Iterated pixel is the inverted pixel. ITER2BL: Blender Iterated Color Enable 0: Final adder stage operand is set to 0. 1: Final adder stage operand is set to the iterated pixel value. ITER: Blender Use Iterated Color 0: Pixel difference is set to 0. 1: Pixel difference is set to the iterated pixel value. REVALPHA: Blender Reverse Alpha 0: Pixel difference is multiplied by alpha. 1: Pixel difference is multiplied by 1 - alpha. GAEN: Blender Global Alpha Enable 0: Global alpha blending coefficient is disabled. 1: Global alpha blending coefficient is enabled. LAEN: Blender Local Alpha Enable 0: Local alpha blending coefficient is disabled. 1: Local alpha blending coefficient is enabled. OVR: Blender Overlay Layer Enable 0: Overlay pixel color is set to the default overlay pixel color. 1: Overlay pixel color is set to the DMA channel pixel color. DMA: Blender DMA Layer Enable 0: The default color is used on the Overlay 1 Layer. 1: The DMA channel retrieves the pixels stream from the memory.  2017 Microchip Technology Inc. DS60001476B-page 831 SAMA5D2 SERIES REP: Use Replication logic to expand RGB color to 24 bits 0: When the selected pixel depth is less than 24 bpp the pixel is shifted and least significant bits are set to 0. 1: When the selected pixel depth is less than 24 bpp the pixel is shifted and the least significant bit replicates the msb. DSTKEY: Destination Chroma Keying 0: Source Chroma keying is enabled. 1: Destination Chroma keying is used. GA: Blender Global Alpha Global alpha blender for the current layer. DS60001476B-page 832  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.55 Overlay 2 Channel Enable Register Name: LCDC_OVR2CHER Address: 0xF0000240 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QEN 1 UPDATEEN 0 CHEN CHEN: Channel Enable 0: No effect 1: Enables the DMA channel UPDATEEN: Update Overlay Attributes Enable 0: No effect 1: Updates windows attributes on the next start of frame. A2QEN: Add To Queue Enable 0: No effect 1: Indicates that a valid descriptor has been written to memory, its memory location should be written to the DMA head pointer. The A2QSR status bit is set to one, and it is reset by hardware as soon as the descriptor pointed to by the DMA head pointer is added to the list.  2017 Microchip Technology Inc. DS60001476B-page 833 SAMA5D2 SERIES 39.7.56 Overlay 2 Channel Disable Register Name: LCDC_OVR2CHDR Address: 0xF0000244 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CHRST 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CHDIS CHDIS: Channel Disable 0: No effect 1: Disables the layer at the end of the current frame. The frame is completed. CHRST: Channel Reset 0: No effect 1: Resets the layer immediately. The frame is aborted. DS60001476B-page 834  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.57 Overlay 2 Channel Status Register Name: LCDC_OVR2CHSR Address: 0xF0000248 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QSR 1 UPDATESR 0 CHSR CHSR: Channel Status 0: Layer disabled 1: Layer enabled UPDATESR: Update Overlay Attributes In Progress Status 0: No update pending 1: Overlay attributes will be updated on the next frame A2QSR: Add To Queue Status 0: Add to queue not pending 1: Add to queue pending  2017 Microchip Technology Inc. DS60001476B-page 835 SAMA5D2 SERIES 39.7.58 Overlay 2 Interrupt Enable Register Name: LCDC_OVR2IER Address: 0xF000024C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled DONE: End of List Interrupt Enable 0: No effect 1: Interrupt source is enabled OVR: Overflow Interrupt Enable 0: No effect 1: Interrupt source is enabled DS60001476B-page 836  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.59 Overlay 2 Interrupt Disable Register Name: LCDC_OVR2IDR Address: 0xF0000250 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Disable 0: No effect 1: Interrupt source is disabled DSCR: Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled ADD: Head Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled DONE: End of List Interrupt Disable 0: No effect 1: Interrupt source is disabled OVR: Overflow Interrupt Disable 0: No effect 1: Interrupt source is disabled  2017 Microchip Technology Inc. DS60001476B-page 837 SAMA5D2 SERIES 39.7.60 Overlay 2 Interrupt Mask Register Name: LCDC_OVR2IMR Address: 0xF0000254 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DONE: End of List Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled OVR: Overflow Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DS60001476B-page 838  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.61 Overlay 2 Interrupt Status Register Name: LCDC_OVR2ISR Address: 0xF0000258 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer 0: No End of Transfer has been detected since last read of LCDC_OVR2ISR 1: End of Transfer has been detected. This flag is reset after a read operation. DSCR: DMA Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_OVR2ISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. ADD: Head Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_OVR2ISR 1: The descriptor pointed to by the LCDC_OVR2HEAD register has been loaded successfully. This flag is reset after a read operation. DONE: End of List Detected 0: No End of List condition occurred since last read of LCDC_OVR2ISR 1: End of List condition has occurred. This flag is reset after a read operation. OVR: Overflow Detected 0: No overflow occurred since last read of LCDC_OVR2ISR 1: An overflow occurred. This flag is reset after a read operation.  2017 Microchip Technology Inc. DS60001476B-page 839 SAMA5D2 SERIES 39.7.62 Overlay 2 Head Register Name: LCDC_OVR2HEAD Address: 0xF000025C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – HEAD 23 22 21 20 HEAD 15 14 13 12 HEAD 7 6 5 4 HEAD HEAD: DMA Head Pointer The Head Pointer points to a new descriptor. DS60001476B-page 840  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.63 Overlay 2 Address Register Name: LCDC_OVR2ADDR Address: 0xF0000260 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: DMA Transfer Overlay 2 Address Overlay 2 frame buffer base address.  2017 Microchip Technology Inc. DS60001476B-page 841 SAMA5D2 SERIES 39.7.64 Overlay 2 Control Register Name: LCDC_OVR2CTRL Address: 0xF0000264 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONEIEN 4 ADDIEN 3 DSCRIEN 2 DMAIEN 1 LFETCH 0 DFETCH DFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled. 1: Transfer Descriptor fetch is enabled. LFETCH: Lookup Table Fetch Enable 0: Lookup Table DMA fetch is disabled. 1: Lookup Table DMA fetch is enabled. DMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled. 1: DMA transfer completed interrupt is disabled. DSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled. 1: Transfer descriptor loaded interrupt is disabled. ADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled. 1: Transfer descriptor added to queue interrupt is enabled. DONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled. 1: End of list interrupt is enabled. DS60001476B-page 842  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.65 Overlay 2 Next Register Name: LCDC_OVR2NEXT Address: 0xF0000268 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NEXT 23 22 21 20 NEXT 15 14 13 12 NEXT 7 6 5 4 NEXT NEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary.  2017 Microchip Technology Inc. DS60001476B-page 843 SAMA5D2 SERIES 39.7.66 Overlay 2 Configuration Register 0 Name: LCDC_OVR2CFG0 Address: 0xF000026C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 LOCKDIS 12 ROTDIS 11 – 10 – 9 – 8 DLBO 7 – 6 – 5 4 3 – 2 – 1 – 0 – BLEN BLEN: AHB Burst Length Value Name Description 0 AHB_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. DLBO: Defined Length Burst Only For Channel Bus Transaction 0: Undefined length INCR burst is used for 2 and 3 beats burst. 1: Only Defined Length burst is used (SINGLE, INCR4, INCR8 and INCR16). ROTDIS: Hardware Rotation Optimization Disable 0: Rotation optimization is enabled. 1: Rotation optimization is disabled. LOCKDIS: Hardware Rotation Lock Disable 0: AHB lock signal is asserted when a rotation is performed. 1: AHB lock signal is cleared when a rotation is performed. DS60001476B-page 844  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.67 Overlay 2 Configuration Register 1 Name: LCDC_OVR2CFG1 Address: 0xF0000270 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 – 2 – 1 – RGBMODE CLUTMODE 0 CLUTEN CLUTEN: Color Lookup Table Mode Enable 0: RGB mode is selected. 1: Color Lookup Table mode is selected. RGBMODE: RGB Mode Input Selection Value Name Description 0 12BPP_RGB_444 12 bpp RGB 444 1 16BPP_ARGB_4444 16 bpp ARGB 4444 2 16BPP_RGBA_4444 16 bpp RGBA 4444 3 16BPP_RGB_565 16 bpp RGB 565 4 16BPP_TRGB_1555 16 bpp TRGB 1555 5 18BPP_RGB_666 18 bpp RGB 666 6 18BPP_RGB_666PACKED 18 bpp RGB 666 PACKED 7 19BPP_TRGB_1666 19 bpp TRGB 1666 8 19BPP_TRGB_PACKED 19 bpp TRGB 1666 PACKED 9 24BPP_RGB_888 24 bpp RGB 888 10 24BPP_RGB_888_PACKED 24 bpp RGB 888 PACKED 11 25BPP_TRGB_1888 25 bpp TRGB 1888 12 32BPP_ARGB_8888 32 bpp ARGB 8888 13 32BPP_RGBA_8888 32 bpp RGBA 8888  2017 Microchip Technology Inc. DS60001476B-page 845 SAMA5D2 SERIES CLUTMODE: Color Lookup Table Mode Input Selection Value Name Description 0 CLUT_1BPP Color Lookup Table mode set to 1 bit per pixel 1 CLUT_2BPP Color Lookup Table mode set to 2 bits per pixel 2 CLUT_4BPP Color Lookup Table mode set to 4 bits per pixel 3 CLUT_8BPP Color Lookup Table mode set to 8 bits per pixel DS60001476B-page 846  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.68 Overlay 2 Configuration Register 2 Name: LCDC_OVR2CFG2 Address: 0xF0000274 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YPOS 24 19 18 17 16 11 – 10 9 XPOS 8 3 2 1 0 YPOS 15 – 14 – 13 – 12 – 7 6 5 4 XPOS XPOS: Horizontal Window Position Overlay 2 Horizontal window position. YPOS: Vertical Window Position Overlay 2 Vertical window position.  2017 Microchip Technology Inc. DS60001476B-page 847 SAMA5D2 SERIES 39.7.69 Overlay 2 Configuration Register 3 Name: LCDC_OVR2CFG3 Address: 0xF0000278 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YSIZE 24 19 18 17 16 11 – 10 9 XSIZE 8 3 2 1 0 YSIZE 15 – 14 – 13 – 12 – 7 6 5 4 XSIZE XSIZE: Horizontal Window Size Overlay 2 window width in pixels. The window width is set to (XSIZE + 1). The following constraint must be met: XPOS + XSIZE ≤ PPL YSIZE: Vertical Window Size Overlay 2 window height in pixels. The window height is set to (YSIZE + 1). The following constraint must be met: YPOS + YSIZE ≤ RPF DS60001476B-page 848  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.70 Overlay 2 Configuration Register 4 Name: LCDC_OVR2CFG4 Address: 0xF000027C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 XSTRIDE 23 22 21 20 XSTRIDE 15 14 13 12 XSTRIDE 7 6 5 4 XSTRIDE XSTRIDE: Horizontal Stride XSTRIDE represents the memory offset, in bytes, between two rows of the image memory.  2017 Microchip Technology Inc. DS60001476B-page 849 SAMA5D2 SERIES 39.7.71 Overlay 2 Configuration Register 5 Name: LCDC_OVR2CFG5 Address: 0xF0000280 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 PSTRIDE 23 22 21 20 PSTRIDE 15 14 13 12 PSTRIDE 7 6 5 4 PSTRIDE PSTRIDE: Pixel Stride PSTRIDE represents the memory offset, in bytes, between two pixels of the image memory. DS60001476B-page 850  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.72 Overlay 2 Configuration Register 6 Name: LCDC_OVR2CFG6 Address: 0xF0000284 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RDEF 15 14 13 12 GDEF 7 6 5 4 BDEF RDEF: Red Default Default Red color when the Overlay 1 DMA channel is disabled. GDEF: Green Default Default Green color when the Overlay 1 DMA channel is disabled. BDEF: Blue Default Default Blue color when the Overlay 1 DMA channel is disabled.  2017 Microchip Technology Inc. DS60001476B-page 851 SAMA5D2 SERIES 39.7.73 Overlay 2 Configuration Register 7 Name: LCDC_OVR2CFG7 Address: 0xF0000288 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RKEY 15 14 13 12 GKEY 7 6 5 4 BKEY RKEY: Red Color Component Chroma Key Reference Red chroma key used to match the Red color of the current overlay. GKEY: Green Color Component Chroma Key Reference Green chroma key used to match the Green color of the current overlay. BKEY: Blue Color Component Chroma Key Reference Blue chroma key used to match the Blue color of the current overlay. DS60001476B-page 852  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.74 Overlay 2 Configuration Register 8 Name: LCDC_OVR2CFG8 Address: 0xF000028C Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RMASK 15 14 13 12 GMASK 7 6 5 4 BMASK RMASK: Red Color Component Chroma Key Mask Red Mask used when the compare function is used. If a bit is set then this bit is compared. GMASK: Green Color Component Chroma Key Mask Green Mask used when the compare function is used. If a bit is set then this bit is compared. BMASK: Blue Color Component Chroma Key Mask Blue Mask used when the compare function is used. If a bit is set then this bit is compared.  2017 Microchip Technology Inc. DS60001476B-page 853 SAMA5D2 SERIES 39.7.75 Overlay 2 Configuration Register 9 Name: LCDC_OVR2CFG9 Address: 0xF0000290 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 GA 15 – 14 – 13 – 12 – 11 – 10 DSTKEY 9 REP 8 DMA 7 OVR 6 LAEN 5 GAEN 4 REVALPHA 3 ITER 2 ITER2BL 1 INV 0 CRKEY CRKEY: Blender Chroma Key Enable 0: Chroma key matching is disabled. 1: Chroma key matching is enabled. INV: Blender Inverted Blender Output Enable 0: Iterated pixel is the blended pixel. 1: Iterated pixel is the inverted pixel. ITER2BL: Blender Iterated Color Enable 0: Final adder stage operand is set to 0. 1: Final adder stage operand is set to the iterated pixel value. ITER: Blender Use Iterated Color 0: Pixel difference is set to 0. 1: Pixel difference is set to the iterated pixel value. REVALPHA: Blender Reverse Alpha 0: Pixel difference is multiplied by alpha. 1: Pixel difference is multiplied by 1 - alpha. GAEN: Blender Global Alpha Enable 0: Global alpha blending coefficient is disabled. 1: Global alpha blending coefficient is enabled. LAEN: Blender Local Alpha Enable 0: Local alpha blending coefficient is disabled. 1: Local alpha blending coefficient is enabled. OVR: Blender Overlay Layer Enable 0: Overlay pixel color is set to the default overlay pixel color. 1: Overlay pixel color is set to the DMA channel pixel color. DMA: Blender DMA Layer Enable 0: The default color is used on the Overlay 1 Layer. 1: The DMA channel retrieves the pixels stream from the memory. DS60001476B-page 854  2017 Microchip Technology Inc. SAMA5D2 SERIES REP: Use Replication logic to expand RGB color to 24 bits 0: When the selected pixel depth is less than 24 bpp the pixel is shifted and least significant bits are set to 0. 1: When the selected pixel depth is less than 24 bpp the pixel is shifted and the least significant bit replicates the msb. DSTKEY: Destination Chroma Keying 0: Source Chroma keying is enabled. 1: Destination Chroma keying is used. GA: Blender Global Alpha Global alpha blender for the current layer.  2017 Microchip Technology Inc. DS60001476B-page 855 SAMA5D2 SERIES 39.7.76 High-End Overlay Channel Enable Register Name: LCDC_HEOCHER Address: 0xF0000340 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QEN 1 UPDATEEN 0 CHEN CHEN: Channel Enable 0: No effect 1: Enables the DMA channel UPDATEEN: Update Overlay Attributes Enable 0: No effect 1: Updates windows attributes on the next start of frame. A2QEN: Add To Queue Enable 0: No effect 1: Indicates that a valid descriptor has been written to memory, its memory location should be written to the DMA head pointer. The A2QSR status bit is set to one, and it is reset by hardware as soon as the descriptor pointed to by the DMA head pointer is added to the list. DS60001476B-page 856  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.77 High-End Overlay Channel Disable Register Name: LCDC_HEOCHDR Address: 0xF0000344 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CHRST 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CHDIS CHDIS: Channel Disable 0: No effect 1: Disables the layer at the end of the current frame. The frame is completed. CHRST: Channel Reset 0: No effect 1: Resets the layer immediately. The frame is aborted.  2017 Microchip Technology Inc. DS60001476B-page 857 SAMA5D2 SERIES 39.7.78 High-End Overlay Channel Status Register Name: LCDC_HEOCHSR Address: 0xF0000348 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QSR 1 UPDATESR 0 CHSR CHSR: Channel Status 0: Layer disabled 1: Layer enabled UPDATESR: Update Overlay Attributes In Progress Status 0: No update pending 1: Overlay attributes will be updated on the next frame A2QSR: Add To Queue Status 0: Add to queue not pending 1: Add to queue pending DS60001476B-page 858  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.79 High-End Overlay Interrupt Enable Register Name: LCDC_HEOIER Address: 0xF000034C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 VOVR 21 VDONE 20 VADD 19 VDSCR 18 VDMA 17 – 16 – 15 – 14 UOVR 13 UDONE 12 UADD 11 UDSCR 10 UDMA 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled DONE: End of List Interrupt Enable 0: No effect 1: Interrupt source is enabled OVR: Overflow Interrupt Enable 0: No effect 1: Interrupt source is enabled UDMA: End of DMA Transfer for U or UV Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled UDSCR: Descriptor Loaded for U or UV Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled UADD: Head Descriptor Loaded for U or UV Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled UDONE: End of List for U or UV Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 859 SAMA5D2 SERIES UOVR: Overflow for U or UV Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled VDMA: End of DMA for V Chrominance Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled VDSCR: Descriptor Loaded for V Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled VADD: Head Descriptor Loaded for V Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled VDONE: End of List for V Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled VOVR: Overflow for V Chrominance Interrupt Enable 0: No effect 1: Interrupt source is enabled DS60001476B-page 860  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.80 High-End Overlay Interrupt Disable Register Name: LCDC_HEOIDR Address: 0xF0000350 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 VOVR 21 VDONE 20 VADD 19 VDSCR 18 VDMA 17 – 16 – 15 – 14 UOVR 13 UDONE 12 UADD 11 UDSCR 10 UDMA 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Disable 0: No effect 1: Interrupt source is disabled DSCR: Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled ADD: Head Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled DONE: End of List Interrupt Disable 0: No effect 1: Interrupt source is disabled OVR: Overflow Interrupt Disable 0: No effect 1: Interrupt source is disabled UDMA: End of DMA Transfer for U or UV Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled UDSCR: Descriptor Loaded for U or UV Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled UADD: Head Descriptor Loaded for U or UV Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled UDONE: End of List Interrupt for U or UV Chrominance Component Disable 0: No effect 1: Interrupt source is disabled  2017 Microchip Technology Inc. DS60001476B-page 861 SAMA5D2 SERIES UOVR: Overflow Interrupt for U or UV Chrominance Component Disable 0: No effect 1: Interrupt source is disabled VDMA: End of DMA Transfer for V Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled VDSCR: Descriptor Loaded for V Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled VADD: Head Descriptor Loaded for V Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled VDONE: End of List for V Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled VOVR: Overflow for V Chrominance Component Interrupt Disable 0: No effect 1: Interrupt source is disabled DS60001476B-page 862  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.81 High-End Overlay Interrupt Mask Register Name: LCDC_HEOIMR Address: 0xF0000354 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 VOVR 21 VDONE 20 VADD 19 VDSCR 18 VDMA 17 – 16 – 15 – 14 UOVR 13 UDONE 12 UADD 11 UDSCR 10 UDMA 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DONE: End of List Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled OVR: Overflow Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled UDMA: End of DMA Transfer for U or UV Chrominance Component Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled UDSCR: Descriptor Loaded for U or UV Chrominance Component Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled UADD: Head Descriptor Loaded for U or UV Chrominance Component Mask 0: Interrupt source is disabled 1: Interrupt source is enabled UDONE: End of List for U or UV Chrominance Component Mask 0: Interrupt source is disabled 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 863 SAMA5D2 SERIES UOVR: Overflow for U Chrominance Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled VDMA: End of DMA Transfer for V Chrominance Component Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled VDSCR: Descriptor Loaded for V Chrominance Component Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled VADD: Head Descriptor Loaded for V Chrominance Component Mask 0: Interrupt source is disabled 1: Interrupt source is enabled VDONE: End of List for V Chrominance Component Mask 0: Interrupt source is disabled 1: Interrupt source is enabled VOVR: Overflow for V Chrominance Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DS60001476B-page 864  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.82 High-End Overlay Interrupt Status Register Name: LCDC_HEOISR Address: 0xF0000358 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 VOVR 21 VDONE 20 VADD 19 VDSCR 18 VDMA 17 – 16 – 15 – 14 UOVR 13 UDONE 12 UADD 11 UDSCR 10 UDMA 9 – 8 – 7 – 6 OVR 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer 0: No end of transfer has been detected since last read of LCDC_HEOISR 1: End of Transfer has been detected. This flag is reset after a read operation. DSCR: DMA Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. ADD: Head Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: The descriptor pointed to by the LCDC_HEOHEAD register has been loaded successfully. This flag is reset after a read operation. DONE: End of List Detected 0: No End of List condition occurred since last read of LCDC_HEOISR 1: End of List condition has occurred. This flag is reset after a read operation. OVR: Overflow Detected 0: No overflow occurred since last read of LCDC_HEOISR 1: An overflow occurred. This flag is reset after a read operation. UDMA: End of DMA Transfer for U Component 0: No End of Transfer has been detected since last read of LCDC_HEOISR 1: End of Transfer has been detected. This flag is reset after a read operation. UDSCR: DMA Descriptor Loaded for U Component 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. UADD: Head Descriptor Loaded for U Component 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: The descriptor pointed to by the LCDC_HEOUHEAD register has been loaded successfully. This flag is reset after a read operation. UDONE: End of List Detected for U Component 0: No End of List condition occurred since last read of LCDC_HEOISR 1: End of List condition has occurred. This flag is reset after a read operation.  2017 Microchip Technology Inc. DS60001476B-page 865 SAMA5D2 SERIES UOVR: Overflow Detected for U Component 0: No overflow occurred since last read of LCDC_HEOISR 1: An overflow occurred. This flag is reset after a read operation. VDMA: End of DMA Transfer for V Component 0: No End of Transfer has been detected since last read of LCDC_HEOISR 1: End of Transfer has been detected. This flag is reset after a read operation. VDSCR: DMA Descriptor Loaded for V Component 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. VADD: Head Descriptor Loaded for V Component 0: No descriptor has been loaded since last read of LCDC_HEOISR 1: The descriptor pointed to by the LCDC_HEOVHEAD register has been loaded successfully. This flag is reset after a read operation. VDONE: End of List Detected for V Component 0: No End of List condition occurred since last read of LCDC_HEOISR 1: End of List condition has occurred. This flag is reset after a read operation. VOVR: Overflow Detected for V Component 0: No overflow occurred since last read of LCDC_HEOISR 1: An overflow occurred. This flag is reset after a read operation. DS60001476B-page 866  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.83 High-End Overlay DMA Head Register Name: LCDC_HEOHEAD Address: 0xF000035C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – HEAD 23 22 21 20 HEAD 15 14 13 12 HEAD 7 6 5 4 HEAD HEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 867 SAMA5D2 SERIES 39.7.84 High-End Overlay DMA Address Register Name: LCDC_HEOADDR Address: 0xF0000360 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: DMA Transfer Start Address Frame Buffer Base Address. DS60001476B-page 868  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.85 High-End Overlay DMA Control Register Name: LCDC_HEOCTRL Address: 0xF0000364 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONEIEN 4 ADDIEN 3 DSCRIEN 2 DMAIEN 1 LFETCH 0 DFETCH DFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled. 1: Transfer Descriptor fetch is enabled. LFETCH: Lookup Table Fetch Enable 0: Lookup Table DMA fetch is disabled. 1: Lookup Table DMA fetch is enabled. DMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled. 1: DMA transfer completed interrupt is disabled. DSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled. 1: Transfer descriptor loaded interrupt is disabled. ADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled. 1: Transfer descriptor added to queue interrupt is enabled. DONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled. 1: End of list interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 869 SAMA5D2 SERIES 39.7.86 High-End Overlay DMA Next Register Name: LCDC_HEONEXT Address: 0xF0000368 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NEXT 23 22 21 20 NEXT 15 14 13 12 NEXT 7 6 5 4 NEXT NEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 870  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.87 High-End Overlay U-UV DMA Head Register Name: LCDC_HEOUHEAD Address: 0xF000036C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UHEAD 23 22 21 20 UHEAD 15 14 13 12 UHEAD 7 6 5 4 UHEAD UHEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 871 SAMA5D2 SERIES 39.7.88 High-End Overlay U-UV DMA Address Register Name: LCDC_HEOUADDR Address: 0xF0000370 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UADDR 23 22 21 20 UADDR 15 14 13 12 UADDR 7 6 5 4 UADDR UADDR: DMA Transfer Start Address for U or UV Chrominance U or UV frame buffer address. DS60001476B-page 872  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.89 High-End Overlay U-UV DMA Control Register Name: LCDC_HEOUCTRL Address: 0xF0000374 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 UDONEIEN 4 UADDIEN 3 UDSCRIEN 2 UDMAIEN 1 – 0 UDFETCH UDFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled. 1: Transfer Descriptor fetch is enabled. UDMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled. 1: DMA transfer completed interrupt is disabled. UDSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled. 1: Transfer descriptor loaded interrupt is disabled. UADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled. 1: Transfer descriptor added to queue interrupt is enabled. UDONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled. 1: End of list interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 873 SAMA5D2 SERIES 39.7.90 High-End Overlay U-UV DMA Next Register Name: LCDC_HEOUNEXT Address: 0xF0000378 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UNEXT 23 22 21 20 UNEXT 15 14 13 12 UNEXT 7 6 5 4 UNEXT UNEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 874  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.91 High-End Overlay V DMA Head Register Name: LCDC_HEOVHEAD Address: 0xF000037C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VHEAD 23 22 21 20 VHEAD 15 14 13 12 VHEAD 7 6 5 4 VHEAD VHEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 875 SAMA5D2 SERIES 39.7.92 High-End Overlay V DMA Address Register Name: LCDC_HEOVADDR Address: 0xF0000380 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VADDR 23 22 21 20 VADDR 15 14 13 12 VADDR 7 6 5 4 VADDR VADDR: DMA Transfer Start Address for V Chrominance Frame Buffer Base Address. DS60001476B-page 876  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.93 High-End Overlay V DMA Control Register Name: LCDC_HEOVCTRL Address: 0xF0000384 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 VDONEIEN 4 VADDIEN 3 VDSCRIEN 2 VDMAIEN 1 – 0 VDFETCH VDFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled. 1: Transfer Descriptor fetch is enabled. VDMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled. 1: DMA transfer completed interrupt is disabled. VDSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled. 1: Transfer descriptor loaded interrupt is disabled. VADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled. 1: Transfer descriptor added to queue interrupt is enabled. VDONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled. 1: End of list interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 877 SAMA5D2 SERIES 39.7.94 High-End Overlay V DMA Next Register Name: LCDC_HEOVNEXT Address: 0xF0000388 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VNEXT 23 22 21 20 VNEXT 15 14 13 12 VNEXT 7 6 5 4 VNEXT VNEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 878  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.95 High-End Overlay Configuration Register 0 Name: LCDC_HEOCFG0 Address: 0xF000038C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 LOCKDIS 12 ROTDIS 11 – 10 – 9 – 8 DLBO 6 5 4 3 – 2 – 1 – 0 SIF 7 BLENUV BLEN SIF: Source Interface 0: Base Layer data is retrieved through AHB interface 0. 1: Base Layer data is retrieved through AHB interface 1. BLEN: AHB Burst Length Value Name Description 0 AHB_BLEN_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_BLEN_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_BLEN_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_BLEN_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. BLENUV: AHB Burst Length for U-V Channel Value Name Description 0 AHB_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats.  2017 Microchip Technology Inc. DS60001476B-page 879 SAMA5D2 SERIES DLBO: Defined Length Burst Only For Channel Bus Transaction 0: Undefined length INCR burst is used for a burst of 2 and 3 beats. 1: Only Defined Length burst is used (SINGLE, INCR4, INCR8 and INCR16). ROTDIS: Hardware Rotation Optimization Disable 0: Rotation optimization is enabled. 1: Rotation optimization is disabled. LOCKDIS: Hardware Rotation Lock Disable 0: AHB lock signal is asserted when a rotation is performed. 1: AHB lock signal is cleared when a rotation is performed. DS60001476B-page 880  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.96 High-End Overlay Configuration Register 1 Name: LCDC_HEOCFG1 Address: 0xF0000390 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 DSCALEOPT 19 – 18 – 17 YUV422SWP 16 YUV422ROT 15 14 13 12 11 – 10 – 9 8 3 – 2 – 1 YUVEN YUVMODE 7 6 5 4 RGBMODE CLUTMODE 0 CLUTEN CLUTEN: Color Lookup Table Mode Enable 0: RGB mode is selected. 1: Color Lookup Table mode is selected. YUVEN: YUV Color Space Enable 0: Color space is RGB 1: Color Space is YUV RGBMODE: RGB Mode Input Selection Value Name Description 0 12BPP_RGB_444 12 bpp RGB 444 1 16BPP_ARGB_4444 16 bpp ARGB 4444 2 16BPP_RGBA_4444 16 bpp RGBA 4444 3 16BPP_RGB_565 16 bpp RGB 565 4 16BPP_TRGB_1555 16 bpp TRGB 1555 5 18BPP_RGB_666 18 bpp RGB 666 6 18BPP_RGB_666PACKED 18 bpp RGB 666 PACKED 7 19BPP_TRGB_1666 19 bpp TRGB 1666 8 19BPP_TRGB_PACKED 19 bpp TRGB 1666 PACKED 9 24BPP_RGB_888 24 bpp RGB 888 10 24BPP_RGB_888_PACKED 24 bpp RGB 888 PACKED 11 25BPP_TRGB_1888 25 bpp TRGB 1888 12 32BPP_ARGB_8888 32 bpp ARGB 8888 13 32BPP_RGBA_8888 32 bpp RGBA 8888  2017 Microchip Technology Inc. DS60001476B-page 881 SAMA5D2 SERIES CLUTMODE: Color Lookup Table Mode Input Selection Value Name Description 0 CLUT_1BPP Color Lookup Table mode set to 1 bit per pixel 1 CLUT_2BPP Color Lookup Table mode set to 2 bits per pixel 2 CLUT_4BPP Color Lookup Table mode set to 4 bits per pixel 3 CLUT_8BPP Color Lookup Table mode set to 8 bits per pixel YUVMODE: YUV Mode Input Selection Value Name Description 0 32BPP_AYCBCR 32 bpp AYCbCr 444 1 16BPP_YCBCR_MODE0 16 bpp Cr(n)Y(n+1)Cb(n)Y(n) 422 2 16BPP_YCBCR_MODE1 16 bpp Y(n+1)Cr(n)Y(n)Cb(n) 422 3 16BPP_YCBCR_MODE2 16 bpp Cb(n)Y(+1)Cr(n)Y(n) 422 4 16BPP_YCBCR_MODE3 16 bpp Y(n+1)Cb(n)Y(n)Cr(n) 422 5 16BPP_YCBCR_SEMIPLANAR 16 bpp Semiplanar 422 YCbCr 6 16BPP_YCBCR_PLANAR 16 bpp Planar 422 YCbCr 7 12BPP_YCBCR_SEMIPLANAR 12 bpp Semiplanar 420 YCbCr 8 12BPP_YCBCR_PLANAR 12 bpp Planar 420 YCbCr YUV422ROT: YUV 4:2:2 Rotation 0: Chroma Upsampling kernel is configured to use 0 and 180 degrees algorithm 1: Indicates that the Chroma Upsampling kernel is configured to use the 4:2:2 Rotation Algorithm. This bit is relevant only when a rotation angle of 90 degrees or 270 degrees is used. YUV422SWP: YUV 4:2:2 Swap 0: The two Y components of the YUV 4:2:2 packed data stream are not swapped 1: The two Y components of the YUV 4:2:2 packed data stream are swapped. DSCALEOPT: Down Scaling Bandwidth Optimization 0: Scaler Optimization is disabled. 1: Scaler Optimization is enabled, only relevant pixels are retrieved from memory to fill the scaler filter. DS60001476B-page 882  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.97 High-End Overlay Configuration Register 2 Name: LCDC_HEOCFG2 Address: 0xF0000394 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YPOS 24 19 18 17 16 11 – 10 9 XPOS 8 3 2 1 0 YPOS 15 – 14 – 13 – 12 – 7 6 5 4 XPOS XPOS: Horizontal Window Position High-End Overlay Horizontal window position. YPOS: Vertical Window Position High-End Overlay Vertical window position.  2017 Microchip Technology Inc. DS60001476B-page 883 SAMA5D2 SERIES 39.7.98 High-End Overlay Configuration Register 3 Name: LCDC_HEOCFG3 Address: 0xF0000398 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YSIZE 24 19 18 17 16 11 – 10 9 XSIZE 8 3 2 1 0 YSIZE 15 – 14 – 13 – 12 – 7 6 5 4 XSIZE XSIZE: Horizontal Window Size High-End Overlay window width in pixels. The window width is set to (XSIZE + 1). The following constraint must be met: XPOS + XSIZE ≤ PPL YSIZE: Vertical Window Size High-End Overlay window height in pixels. The window height is set to (YSIZE + 1). The following constraint must be met: YPOS + YSIZE ≤ RPF DS60001476B-page 884  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.99 High-End Overlay Configuration Register 4 Name: LCDC_HEOCFG4 Address: 0xF000039C Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 25 YMEMSIZE 24 19 18 17 16 11 – 10 9 XMEMSIZE 8 3 2 1 0 YMEMSIZE 15 – 14 – 13 – 12 – 7 6 5 4 XMEMSIZE XMEMSIZE: Horizontal image Size in Memory High-End Overlay image width in pixels. The image width is set to (XMEMSIZE + 1). YMEMSIZE: Vertical image Size in Memory High-End Overlay image height in pixels. The image height is set to (YMEMSIZE + 1).  2017 Microchip Technology Inc. DS60001476B-page 885 SAMA5D2 SERIES 39.7.100 High-End Overlay Configuration Register 5 Name: LCDC_HEOCFG5 Address: 0xF00003A0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 XSTRIDE 23 22 21 20 XSTRIDE 15 14 13 12 XSTRIDE 7 6 5 4 XSTRIDE XSTRIDE: Horizontal Stride XSTRIDE represents the memory offset, in bytes, between two rows of the image memory. DS60001476B-page 886  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.101 High-End Overlay Configuration Register 6 Name: LCDC_HEOCFG6 Address: 0xF00003A4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 PSTRIDE 23 22 21 20 PSTRIDE 15 14 13 12 PSTRIDE 7 6 5 4 PSTRIDE PSTRIDE: Pixel Stride PSTRIDE represents the memory offset, in bytes, between two pixels of the image memory.  2017 Microchip Technology Inc. DS60001476B-page 887 SAMA5D2 SERIES 39.7.102 High-End Overlay Configuration Register 7 Name: LCDC_HEOCFG7 Address: 0xF00003A8 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UVXSTRIDE 23 22 21 20 UVXSTRIDE 15 14 13 12 UVXSTRIDE 7 6 5 4 UVXSTRIDE UVXSTRIDE: UV Horizontal Stride UVXSTRIDE represents the memory offset, in bytes, between two rows of the image memory. DS60001476B-page 888  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.103 High-End Overlay Configuration Register 8 Name: LCDC_HEOCFG8 Address: 0xF00003AC Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 UVPSTRIDE 23 22 21 20 UVPSTRIDE 15 14 13 12 UVPSTRIDE 7 6 5 4 UVPSTRIDE UVPSTRIDE: UV Pixel Stride UVPSTRIDE represents the memory offset, in bytes, between two pixels of the image memory.  2017 Microchip Technology Inc. DS60001476B-page 889 SAMA5D2 SERIES 39.7.104 High-End Overlay Configuration Register 9 Name: LCDC_HEOCFG9 Address: 0xF00003B0 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RDEF 15 14 13 12 GDEF 7 6 5 4 BDEF RDEF: Red Default Default Red color when the High-End Overlay DMA channel is disabled. GDEF: Green Default Default Green color when the High-End Overlay DMA channel is disabled. BDEF: Blue Default Default Blue color when the High-End Overlay DMA channel is disabled. DS60001476B-page 890  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.105 High-End Overlay Configuration Register 10 Name: LCDC_HEOCFG10 Address: 0xF00003B4 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RKEY 15 14 13 12 GKEY 7 6 5 4 BKEY RKEY: Red Color Component Chroma Key Reference Red chroma key used to match the Red color of the current overlay. GKEY: Green Color Component Chroma Key Reference Green chroma key used to match the Green color of the current overlay. BKEY: Blue Color Component Chroma Key Reference Blue chroma key used to match the Blue color of the current overlay.  2017 Microchip Technology Inc. DS60001476B-page 891 SAMA5D2 SERIES 39.7.106 High-End Overlay Configuration Register 11 Name: LCDC_HEOCFG11 Address: 0xF00003B8 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RMASK 15 14 13 12 GMASK 7 6 5 4 BMASK RMASK: Red Color Component Chroma Key Mask Red Mask used when the compare function is used. If a bit is set then this bit is compared. GMASK: Green Color Component Chroma Key Mask Green Mask used when the compare function is used. If a bit is set then this bit is compared. BMASK: Blue Color Component Chroma Key Mask Blue Mask used when the compare function is used. If a bit is set then this bit is compared. DS60001476B-page 892  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.107 High-End Overlay Configuration Register 12 Name: LCDC_HEOCFG12 Address: 0xF00003BC Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 GA 15 – 14 – 13 – 12 VIDPRI 11 – 10 DSTKEY 9 REP 8 DMA 7 OVR 6 LAEN 5 GAEN 4 REVALPHA 3 ITER 2 ITER2BL 1 INV 0 CRKEY CRKEY: Blender Chroma Key Enable 0: Chroma key matching is disabled. 1: Chroma key matching is enabled. INV: Blender Inverted Blender Output Enable 0: Iterated pixel is the blended pixel. 1: Iterated pixel is the inverted pixel. ITER2BL: Blender Iterated Color Enable 0: Final adder stage operand is set to 0. 1: Final adder stage operand is set to the iterated pixel value. ITER: Blender Use Iterated Color 0: Pixel difference is set to 0. 1: Pixel difference is set to the iterated pixel value. REVALPHA: Blender Reverse Alpha 0: Pixel difference is multiplied by alpha. 1: Pixel difference is multiplied by 1 - alpha. GAEN: Blender Global Alpha Enable 0: Global alpha blending coefficient is disabled. 1: Global alpha blending coefficient is enabled. LAEN: Blender Local Alpha Enable 0: Local alpha blending coefficient is disabled. 1: Local alpha blending coefficient is enabled. OVR: Blender Overlay Layer Enable 0: Overlay pixel color is set to the default overlay pixel color. 1: Overlay pixel color is set to the DMA channel pixel color. DMA: Blender DMA Layer Enable 0: The default color is used on the Overlay 1 Layer. 1: The DMA channel retrieves the pixels stream from the memory.  2017 Microchip Technology Inc. DS60001476B-page 893 SAMA5D2 SERIES REP: Use Replication logic to expand RGB color to 24 bits 0: When the selected pixel depth is less than 24 bpp the pixel is shifted and least significant bits are set to 0. 1: When the selected pixel depth is less than 24 bpp the pixel is shifted and the least significant bit replicates the msb. DSTKEY: Destination Chroma Keying 0: Source Chroma keying is enabled. 1: Destination Chroma keying is used. VIDPRI: Video Priority 0: OVR1 layer is above HEO layer. 1: OVR1 layer is below HEO layer. GA: Blender Global Alpha Global alpha blender for the current layer. DS60001476B-page 894  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.108 High-End Overlay Configuration Register 13 Name: LCDC_HEOCFG13 Address: 0xF00003C0 Access: Read/Write 31 SCALEN 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 2 1 0 YFACTOR 20 YFACTOR 15 – 14 – 13 7 6 5 12 XFACTOR 4 3 XFACTOR SCALEN: Hardware Scaler Enable 0: Scaler is disabled 1: Scaler is enabled. YFACTOR: Vertical Scaling Factor Scaler Vertical Factor. XFACTOR: Horizontal Scaling Factor Scaler Horizontal Factor.  2017 Microchip Technology Inc. DS60001476B-page 895 SAMA5D2 SERIES 39.7.109 High-End Overlay Configuration Register 14 Name: LCDC_HEOCFG14 Address: 0xF00003C4 Access: Read/Write 31 – 30 CSCYOFF 29 23 22 21 28 27 26 20 19 18 CSCRV 15 14 25 24 17 16 9 8 CSCRV CSCRU 13 12 11 10 CSCRU 7 6 5 CSCRY 4 3 2 1 0 CSCRY CSCRY: Color Space Conversion Y coefficient for Red Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCRU: Color Space Conversion U coefficient for Red Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCRV: Color Space Conversion V coefficient for Red Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCYOFF: Color Space Conversion Offset 0: Offset is set to 0 1: Offset is set to 16 DS60001476B-page 896  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.110 High-End Overlay Configuration Register 15 Name: LCDC_HEOCFG15 Address: 0xF00003C8 Access: Read/Write 31 – 30 CSCUOFF 29 23 22 21 28 27 26 20 19 18 CSCGV 15 14 25 24 17 16 9 8 CSCGV CSCGU 13 12 11 10 CSCGU 7 6 5 CSCGY 4 3 2 1 0 CSCGY CSCGY: Color Space Conversion Y coefficient for Green Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCGU: Color Space Conversion U coefficient for Green Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCGV: Color Space Conversion V coefficient for Green Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCUOFF: Color Space Conversion Offset 0: Offset is set to 0 1: Offset is set to 128  2017 Microchip Technology Inc. DS60001476B-page 897 SAMA5D2 SERIES 39.7.111 High-End Overlay Configuration Register 16 Name: LCDC_HEOCFG16 Address: 0xF00003CC Access: Read/Write 31 – 30 CSCVOFF 29 23 22 21 28 27 26 20 19 18 CSCBV 15 14 25 24 17 16 9 8 CSCBV CSCBU 13 12 11 10 CSCBU 7 6 5 CSCBY 4 3 2 1 0 CSCBY CSCBY: Color Space Conversion Y coefficient for Blue Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCBU: Color Space Conversion U coefficient for Blue Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCBV: Color Space Conversion V coefficient for Blue Component 1:2:7 format Color Space Conversion coefficient format is 1 sign bit, 2 magnitude bits and 7 fractional bits. CSCVOFF: Color Space Conversion Offset 0: Offset is set to 0 1: Offset is set to 128 DS60001476B-page 898  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.112 High-End Overlay Configuration Register 17 Name: LCDC_HEOCFG17 Address: 0xF00003D0 Access: Read/Write 31 30 29 28 27 XPHI0COEFF3 26 25 24 23 22 21 20 19 XPHI0COEFF2 18 17 16 15 14 13 12 11 XPHI0COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI0COEFF0 XPHI0COEFF0: Horizontal Coefficient for phase 0 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI0COEFF1: Horizontal Coefficient for phase 0 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI0COEFF2: Horizontal Coefficient for phase 0 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI0COEFF3: Horizontal Coefficient for phase 0 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 899 SAMA5D2 SERIES 39.7.113 High-End Overlay Configuration Register 18 Name: LCDC_HEOCFG18 Address: 0xF00003D4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI0COEFF4 XPHI0COEFF4: Horizontal Coefficient for phase 0 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 900  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.114 High-End Overlay Configuration Register 19 Name: LCDC_HEOCFG19 Address: 0xF00003D8 Access: Read/Write 31 30 29 28 27 XPHI1COEFF3 26 25 24 23 22 21 20 19 XPHI1COEFF2 18 17 16 15 14 13 12 11 XPHI1COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI1COEFF0 XPHI1COEFF0: Horizontal Coefficient for phase 1 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI1COEFF1: Horizontal Coefficient for phase 1 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI1COEFF2: Horizontal Coefficient for phase 1 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI1COEFF3: Horizontal Coefficient for phase 1 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 901 SAMA5D2 SERIES 39.7.115 High-End Overlay Configuration Register 20 Name: LCDC_HEOCFG20 Address: 0xF00003DC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI1COEFF4 XPHI1COEFF4: Horizontal Coefficient for phase 1 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 902  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.116 High-End Overlay Configuration Register 21 Name: LCDC_HEOCFG21 Address: 0xF00003E0 Access: Read/Write 31 30 29 28 27 XPHI2COEFF3 26 25 24 23 22 21 20 19 XPHI2COEFF2 18 17 16 15 14 13 12 11 XPHI2COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI2COEFF0 XPHI2COEFF0: Horizontal Coefficient for phase 2 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI2COEFF1: Horizontal Coefficient for phase 2 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI2COEFF2: Horizontal Coefficient for phase 2 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI2COEFF3: Horizontal Coefficient for phase 2 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 903 SAMA5D2 SERIES 39.7.117 High-End Overlay Configuration Register 22 Name: LCDC_HEOCFG22 Address: 0xF00003E4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI2COEFF4 XPHI2COEFF4: Horizontal Coefficient for phase 2 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 904  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.118 High-End Overlay Configuration Register 23 Name: LCDC_HEOCFG23 Address: 0xF00003E8 Access: Read/Write 31 30 29 28 27 XPHI3COEFF3 26 25 24 23 22 21 20 19 XPHI3COEFF2 18 17 16 15 14 13 12 11 XPHI3COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI3COEFF0 XPHI3COEFF0: Horizontal Coefficient for phase 3 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI3COEFF1: Horizontal Coefficient for phase 3 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI3COEFF2: Horizontal Coefficient for phase 3 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI3COEFF3: Horizontal Coefficient for phase 3 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 905 SAMA5D2 SERIES 39.7.119 High-End Overlay Configuration Register 24 Name: LCDC_HEOCFG24 Address: 0xF00003EC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI3COEFF4 XPHI3COEFF4: Horizontal Coefficient for phase 3 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 906  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.120 High-End Overlay Configuration Register 25 Name: LCDC_HEOCFG25 Address: 0xF00003F0 Access: Read/Write 31 30 29 28 27 XPHI4COEFF3 26 25 24 23 22 21 20 19 XPHI4COEFF2 18 17 16 15 14 13 12 11 XPHI4COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI4COEFF0 XPHI4COEFF0: Horizontal Coefficient for phase 4 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI4COEFF1: Horizontal Coefficient for phase 4 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI4COEFF2: Horizontal Coefficient for phase 4 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI4COEFF3: Horizontal Coefficient for phase 4 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 907 SAMA5D2 SERIES 39.7.121 High-End Overlay Configuration Register 26 Name: LCDC_HEOCFG26 Address: 0xF00003F4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI4COEFF4 XPHI4COEFF4: Horizontal Coefficient for phase 4 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 908  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.122 High-End Overlay Configuration Register 27 Name: LCDC_HEOCFG27 Address: 0xF00003F8 Access: Read/Write 31 30 29 28 27 XPHI5COEFF3 26 25 24 23 22 21 20 19 XPHI5COEFF2 18 17 16 15 14 13 12 11 XPHI5COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI5COEFF0 XPHI5COEFF0: Horizontal Coefficient for phase 5 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI5COEFF1: Horizontal Coefficient for phase 5 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI5COEFF2: Horizontal Coefficient for phase 5 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI5COEFF3: Horizontal Coefficient for phase 5 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 909 SAMA5D2 SERIES 39.7.123 High-End Overlay Configuration Register 28 Name: LCDC_HEOCFG28 Address: 0xF00003FC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI5COEFF4 XPHI5COEFF4: Horizontal Coefficient for phase 5 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 910  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.124 High-End Overlay Configuration Register 29 Name: LCDC_HEOCFG29 Address: 0xF0000400 Access: Read/Write 31 30 29 28 27 XPHI6COEFF3 26 25 24 23 22 21 20 19 XPHI6COEFF2 18 17 16 15 14 13 12 11 XPHI6COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI6COEFF0 XPHI6COEFF0: Horizontal Coefficient for phase 6 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI6COEFF1: Horizontal Coefficient for phase 6 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI6COEFF2: Horizontal Coefficient for phase 6 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI6COEFF3: Horizontal Coefficient for phase 6 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 911 SAMA5D2 SERIES 39.7.125 High-End Overlay Configuration Register 30 Name: LCDC_HEOCFG30 Address: 0xF0000404 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI6COEFF4 XPHI6COEFF4: Horizontal Coefficient for phase 6 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 912  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.126 High-End Overlay Configuration Register 31 Name: LCDC_HEOCFG31 Address: 0xF0000408 Access: Read/Write 31 30 29 28 27 XPHI7COEFF3 26 25 24 23 22 21 20 19 XPHI7COEFF2 18 17 16 15 14 13 12 11 XPHI7COEFF1 10 9 8 7 6 5 4 2 1 0 3 XPHI7COEFF0 XPHI7COEFF0: Horizontal Coefficient for phase 7 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. XPHI7COEFF1: Horizontal Coefficient for phase 7 tap 1 Coefficient format is 1 sign bit and 7 fractional bits. XPHI7COEFF2: Horizontal Coefficient for phase 7 tap 2 Coefficient format is 1 magnitude bit and 7 fractional bits. XPHI7COEFF3: Horizontal Coefficient for phase 7 tap 3 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 913 SAMA5D2 SERIES 39.7.127 High-End Overlay Configuration Register 32 Name: LCDC_HEOCFG32 Address: 0xF000040C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 XPHI7COEFF4 XPHI7COEFF4: Horizontal Coefficient for phase 7 tap 4 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 914  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.128 High-End Overlay Configuration Register 33 Name: LCDC_HEOCFG33 Address: 0xF0000410 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI0COEFF2 18 17 16 15 14 13 12 11 YPHI0COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI0COEFF0 YPHI0COEFF0: Vertical Coefficient for phase 0 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI0COEFF1: Vertical Coefficient for phase 0 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI0COEFF2: Vertical Coefficient for phase 0 tap 2 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 915 SAMA5D2 SERIES 39.7.129 High-End Overlay Configuration Register 34 Name: LCDC_HEOCFG34 Address: 0xF0000414 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI1COEFF2 18 17 16 15 14 13 12 11 YPHI1COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI1COEFF0 YPHI1COEFF0: Vertical Coefficient for phase 1 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI1COEFF1: Vertical Coefficient for phase 1 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI1COEFF2: Vertical Coefficient for phase 1 tap 2 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 916  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.130 High-End Overlay Configuration Register 35 Name: LCDC_HEOCFG35 Address: 0xF0000418 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI2COEFF2 18 17 16 15 14 13 12 11 YPHI2COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI2COEFF0 YPHI2COEFF0: Vertical Coefficient for phase 2 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI2COEFF1: Vertical Coefficient for phase 2 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI2COEFF2: Vertical Coefficient for phase 2 tap 2 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 917 SAMA5D2 SERIES 39.7.131 High-End Overlay Configuration Register 36 Name: LCDC_HEOCFG36 Address: 0xF000041C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI3COEFF2 18 17 16 15 14 13 12 11 YPHI3COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI3COEFF0 YPHI3COEFF0: Vertical Coefficient for phase 3 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI3COEFF1: Vertical Coefficient for phase 3 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI3COEFF2: Vertical Coefficient for phase 3 tap 2 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 918  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.132 High-End Overlay Configuration Register 37 Name: LCDC_HEOCFG37 Address: 0xF0000420 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI4COEFF2 18 17 16 15 14 13 12 11 YPHI4COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI4COEFF0 YPHI4COEFF0: Vertical Coefficient for phase 4 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI4COEFF1: Vertical Coefficient for phase 4 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI4COEFF2: Vertical Coefficient for phase 4 tap 2 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 919 SAMA5D2 SERIES 39.7.133 High-End Overlay Configuration Register 38 Name: LCDC_HEOCFG38 Address: 0xF0000424 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI5COEFF2 18 17 16 15 14 13 12 11 YPHI5COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI5COEFF0 YPHI5COEFF0: Vertical Coefficient for phase 5 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI5COEFF1: Vertical Coefficient for phase 5 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI5COEFF2: Vertical Coefficient for phase 5 tap 2 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 920  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.134 High-End Overlay Configuration Register 39 Name: LCDC_HEOCFG39 Address: 0xF0000428 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI6COEFF2 18 17 16 15 14 13 12 11 YPHI6COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI6COEFF0 YPHI6COEFF0: Vertical Coefficient for phase 6 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI6COEFF1: Vertical Coefficient for phase 6 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI6COEFF2: Vertical Coefficient for phase 6 tap 2 Coefficient format is 1 sign bit and 7 fractional bits.  2017 Microchip Technology Inc. DS60001476B-page 921 SAMA5D2 SERIES 39.7.135 High-End Overlay Configuration Register 40 Name: LCDC_HEOCFG40 Address: 0xF000042C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 YPHI7COEFF2 18 17 16 15 14 13 12 11 YPHI7COEFF1 10 9 8 7 6 5 4 2 1 0 3 YPHI7COEFF0 YPHI7COEFF0: Vertical Coefficient for phase 7 tap 0 Coefficient format is 1 sign bit and 7 fractional bits. YPHI7COEFF1: Vertical Coefficient for phase 7 tap 1 Coefficient format is 1 magnitude bit and 7 fractional bits. YPHI7COEFF2: Vertical Coefficient for phase 7 tap 2 Coefficient format is 1 sign bit and 7 fractional bits. DS60001476B-page 922  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.136 High-End Overlay Configuration Register 41 Name: LCDC_HEOCFG41 Address: 0xF0000430 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 17 YPHIDEF 16 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 1 XPHIDEF 0 XPHIDEF: Horizontal Filter Phase Offset XPHIDEF defines the index of the first coefficient set used when the horizontal resampling operation is started. YPHIDEF: Vertical Filter Phase Offset XPHIDEF defines the index of the first coefficient set used when the vertical resampling operation is started.  2017 Microchip Technology Inc. DS60001476B-page 923 SAMA5D2 SERIES 39.7.137 Post Processing Channel Enable Register Name: LCDC_PPCHER Address: 0xF0000540 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QEN 1 UPDATEEN 0 CHEN CHEN: Channel Enable 0: No effect 1: Enables the DMA channel UPDATEEN: Update Overlay Attributes Enable 0: No effect 1: Updates windows attributes on the next start of frame. A2QEN: Add To Queue Enable 0: No effect 1: Indicates that a valid descriptor has been written to memory, its memory location should be written to the DMA head pointer. The A2QSR status bit is set to one, and it is reset by hardware as soon as the descriptor pointed to by the DMA head pointer is added to the list. DS60001476B-page 924  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.138 Post Processing Channel Disable Register Name: LCDC_PPCHDR Address: 0xF0000544 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CHRST 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 CHDIS CHDIS: Channel Disable 0: No effect 1: Disables the layer at the end of the current frame. The frame is completed. CHRST: Channel Reset 0: No effect 1: Resets the layer immediately. The frame is aborted.  2017 Microchip Technology Inc. DS60001476B-page 925 SAMA5D2 SERIES 39.7.139 Post Processing Channel Status Register Name: LCDC_PPCHSR Address: 0xF0000548 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 A2QSR 1 UPDATESR 0 CHSR CHSR: Channel Status 0: Layer disabled 1: Layer enabled UPDATESR: Update Overlay Attributes In Progress Status 0: No update pending 1: Overlay attributes will be updated on the next frame A2QSR: Add To Queue Status 0: Add to queue not pending 1: Add to queue pending DS60001476B-page 926  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.140 Post Processing Interrupt Enable Register Name: LCDC_PPIER Address: 0xF000054C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Enable 0: No effect 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Enable 0: No effect 1: Interrupt source is enabled DONE: End of List Interrupt Enable 0: No effect 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 927 SAMA5D2 SERIES 39.7.141 Post Processing Interrupt Disable Register Name: LCDC_PPIDR Address: 0xF0000550 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Disable 0: No effect 1: Interrupt source is disabled DSCR: Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled ADD: Head Descriptor Loaded Interrupt Disable 0: No effect 1: Interrupt source is disabled DONE: End of List Interrupt Disable 0: No effect 1: Interrupt source is disabled DS60001476B-page 928  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.142 Post Processing Interrupt Mask Register Name: LCDC_PPIMR Address: 0xF0000554 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DSCR: Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled ADD: Head Descriptor Loaded Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled DONE: End of List Interrupt Mask 0: Interrupt source is disabled 1: Interrupt source is enabled  2017 Microchip Technology Inc. DS60001476B-page 929 SAMA5D2 SERIES 39.7.143 Post Processing Interrupt Status Register Name: LCDC_PPISR Address: 0xF0000558 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONE 4 ADD 3 DSCR 2 DMA 1 – 0 – DMA: End of DMA Transfer 0: No End of Transfer has been detected since last read of LCDC_PPISR 1: End of Transfer has been detected. This flag is reset after a read operation. DSCR: DMA Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_PPISR 1: A descriptor has been loaded successfully. This flag is reset after a read operation. ADD: Head Descriptor Loaded 0: No descriptor has been loaded since last read of LCDC_PPISR 1: The descriptor pointed to by the LCDC_PPHEAD register has been loaded successfully. This flag is reset after a read operation. DONE: End of List Detected 0: No End of List condition has occurred since last read of LCDC_PPISR 1: End of List condition has occurred. This flag is reset after a read operation. DS60001476B-page 930  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.144 Post Processing Head Register Name: LCDC_PPHEAD Address: 0xF000055C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – HEAD 23 22 21 20 HEAD 15 14 13 12 HEAD 7 6 5 4 HEAD HEAD: DMA Head Pointer The Head Pointer points to a new descriptor.  2017 Microchip Technology Inc. DS60001476B-page 931 SAMA5D2 SERIES 39.7.145 Post Processing Address Register Name: LCDC_PPADDR Address: 0xF0000560 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: DMA Transfer Start Address Post Processing Destination frame buffer address. DS60001476B-page 932  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.146 Post Processing Control Register Name: LCDC_PPCTRL Address: 0xF0000564 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 DONEIEN 4 ADDIEN 3 DSCRIEN 2 DMAIEN 1 – 0 DFETCH DFETCH: Transfer Descriptor Fetch Enable 0: Transfer Descriptor fetch is disabled. 1: Transfer Descriptor fetch is enabled. DMAIEN: End of DMA Transfer Interrupt Enable 0: DMA transfer completed interrupt is enabled. 1: DMA transfer completed interrupt is disabled. DSCRIEN: Descriptor Loaded Interrupt Enable 0: Transfer descriptor loaded interrupt is enabled. 1: Transfer descriptor loaded interrupt is disabled. ADDIEN: Add Head Descriptor to Queue Interrupt Enable 0: Transfer descriptor added to queue interrupt is enabled. 1: Transfer descriptor added to queue interrupt is enabled. DONEIEN: End of List Interrupt Enable 0: End of list interrupt is disabled. 1: End of list interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 933 SAMA5D2 SERIES 39.7.147 Post Processing Next Register Name: LCDC_PPNEXT Address: 0xF0000568 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NEXT 23 22 21 20 NEXT 15 14 13 12 NEXT 7 6 5 4 NEXT NEXT: DMA Descriptor Next Address The transfer descriptor address must be aligned on a 64-bit boundary. DS60001476B-page 934  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.148 Post Processing Configuration Register 0 Name: LCDC_PPCFG0 Address: 0xF000056C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DLBO 7 – 6 – 5 4 3 – 2 – 1 – 0 SIF BLEN SIF: Source Interface 0: Base Layer data is retrieved through AHB interface 0. 1: Base Layer data is retrieved through AHB interface 1. BLEN: AHB Burst Length Value Name Description 0 AHB_BLEN_SINGLE AHB Access is started as soon as there is enough space in the FIFO to store one data. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. 1 AHB_BLEN_INCR4 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 4 data. An AHB INCR4 Burst is used. SINGLE, INCR and INCR4 bursts are used. INCR is used for a burst of 2 and 3 beats. 2 AHB_BLEN_INCR8 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 8 data. An AHB INCR8 Burst is used. SINGLE, INCR, INCR4 and INCR8 bursts are used. INCR is used for a burst of 2 and 3 beats. 3 AHB_BLEN_INCR16 AHB Access is started as soon as there is enough space in the FIFO to store a total amount of 16 data. An AHB INCR16 Burst is used. SINGLE, INCR, INCR4, INCR8 and INCR16 bursts are used. INCR is used for a burst of 2 and 3 beats. DLBO: Defined Length Burst Only For Channel Bus Transaction 0: Undefined length INCR burst is used for 2 and 3 beats burst. 1: Only Defined Length burst is used (SINGLE, INCR4, INCR8 and INCR16).  2017 Microchip Technology Inc. DS60001476B-page 935 SAMA5D2 SERIES 39.7.149 Post Processing Configuration Register 1 Name: LCDC_PPCFG1 Address: 0xF0000570 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 ITUBT601 3 – 2 1 PPMODE 0 PPMODE: Post Processing Output Format Selection Value Name Description 0 PPMODE_RGB_16BPP RGB 16 bpp 1 PPMODE_RGB_24BPP_PACKED RGB 24 bpp PACKED 2 PPMODE_RGB_24BPP_UNPACKED RGB 24 bpp UNPACKED 3 PPMODE_YCBCR_422_MODE0 YCbCr 422 16 bpp (Mode 0) 4 PPMODE_YCBCR_422_MODE1 YCbCr 422 16 bpp (Mode 1) 5 PPMODE_YCBCR_422_MODE2 YCbCr 422 16 bpp (Mode 2) 6 PPMODE_YCBCR_422_MODE3 YCbCr 422 16 bpp (Mode 3) ITUBT601: Color Space Conversion Luminance 0: Luminance and chrominance range is [0;255] 1: Luminance values are clamped to [16;235] range. Chrominance values are clamped to [16;240] range. DS60001476B-page 936  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.150 Post Processing Configuration Register 2 Name: LCDC_PPCFG2 Address: 0xF0000574 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 XSTRIDE 23 22 21 20 XSTRIDE 15 14 13 12 XSTRIDE 7 6 5 4 XSTRIDE XSTRIDE: Horizontal Stride XSTRIDE represents the memory offset, in bytes, between two rows of the image memory.  2017 Microchip Technology Inc. DS60001476B-page 937 SAMA5D2 SERIES 39.7.151 Post Processing Configuration Register 3 Name: LCDC_PPCFG3 Address: 0xF0000578 Access: Read/Write 31 – 30 CSCYOFF 29 23 22 21 28 27 26 20 19 18 CSCYB 15 14 25 24 17 16 9 8 CSCYB CSCYG 13 12 11 10 CSCYG 7 6 5 CSCYR 4 3 2 1 0 CSCYR CSCYR: Color Space Conversion R coefficient for Luminance component, signed format, step set to 1/1024 Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCYG: Color Space Conversion G coefficient for Luminance component, signed format, step set to 1/512 Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCYB: Color Space Conversion B coefficient for Luminance component, signed format, step set to 1/1024 Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCYOFF: Color Space Conversion Luminance Offset 0: The Yoff parameter value is set to 0. 1: The Yoff parameter value is set to 16. DS60001476B-page 938  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.152 Post Processing Configuration Register 4 Name: LCDC_PPCFG4 Address: 0xF000057C Access: Read/Write 31 – 30 CSCUOFF 29 23 22 21 28 27 26 20 19 18 CSCUB 15 14 25 24 17 16 9 8 CSCUB CSCUG 13 12 11 10 CSCUG 7 6 5 CSCUR 4 3 2 1 0 CSCUR CSCUR: Color Space Conversion R coefficient for Chrominance B component, signed format. (step 1/1024) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCUG: Color Space Conversion G coefficient for Chrominance B component, signed format. (step 1/512) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCUB: Color Space Conversion B coefficient for Chrominance B component, signed format. (step 1/512) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCUOFF: Color Space Conversion Chrominance B Offset 0: The Cboff parameter value is set to 0. 1: The Cboff parameter value is set to 128.  2017 Microchip Technology Inc. DS60001476B-page 939 SAMA5D2 SERIES 39.7.153 Post Processing Configuration Register 5 Name: LCDC_PPCFG5 Address: 0xF0000580 Access: Read/Write 31 – 30 CSCVOFF 29 23 22 21 28 27 26 20 19 18 CSCVB 15 14 25 24 17 16 9 8 CSCVB CSCVG 13 12 11 10 CSCVG 7 6 5 CSCVR 4 3 2 1 0 CSCVR CSCVR: Color Space Conversion R coefficient for Chrominance R component, signed format. (step 1/1024) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCVG: Color Space Conversion G coefficient for Chrominance R component, signed format. (step 1/512) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCVB: Color Space Conversion B coefficient for Chrominance R component, signed format. (step 1/1024) Color Space Conversion coefficient format is 1 sign bit, 9 fractional bits. CSCVOFF: Color Space Conversion Chrominance R Offset 0: The Croff parameter value is set to 0. 1: The Croff parameter value is set to 128. DS60001476B-page 940  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.154 Base CLUT Register x Name: LCDC_BASECLUTx [x=0..255] Address: 0xF0000600 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 RCLUT 15 14 13 12 GCLUT 7 6 5 4 BCLUT BCLUT: Blue Color Entry This field indicates the 8-bit width Blue color of the color lookup table. GCLUT: Green Color Entry This field indicates the 8-bit width Green color of the color lookup table. RCLUT: Red Color Entry This field indicates the 8-bit width Red color of the color lookup table.  2017 Microchip Technology Inc. DS60001476B-page 941 SAMA5D2 SERIES 39.7.155 Overlay 1 CLUT Register x Name: LCDC_OVR1CLUTx [x=0..255] Address: 0xF0000A00 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ACLUT 23 22 21 20 RCLUT 15 14 13 12 GCLUT 7 6 5 4 BCLUT BCLUT: Blue Color Entry This field indicates the 8-bit width Blue color of the color lookup table. GCLUT: Green Color Entry This field indicates the 8-bit width Green color of the color lookup table. RCLUT: Red Color Entry This field indicates the 8-bit width Red color of the color lookup table. ACLUT: Alpha Color Entry This field indicates the 8-bit width Alpha channel of the color lookup table. DS60001476B-page 942  2017 Microchip Technology Inc. SAMA5D2 SERIES 39.7.156 Overlay 2 CLUT Register x Name: LCDC_OVR2CLUTx [x=0..255] Address: 0xF0000E00 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ACLUT 23 22 21 20 RCLUT 15 14 13 12 GCLUT 7 6 5 4 BCLUT BCLUT: Blue Color Entry This field indicates the 8-bit width Blue color of the color lookup table. GCLUT: Green Color Entry This field indicates the 8-bit width Green color of the color lookup table. RCLUT: Red Color Entry This field indicates the 8-bit width Red color of the color lookup table. ACLUT: Alpha Color Entry This field indicates the 8-bit width Alpha channel of the color lookup table.  2017 Microchip Technology Inc. DS60001476B-page 943 SAMA5D2 SERIES 39.7.157 High-End Overlay CLUT Register x Name: LCDC_HEOCLUTx [x=0..255] Address: 0xF0001200 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ACLUT 23 22 21 20 RCLUT 15 14 13 12 GCLUT 7 6 5 4 BCLUT BCLUT: Blue Color Entry This field indicates the 8-bit width Blue color of the color lookup table. GCLUT: Green Color Entry This field indicates the 8-bit width Green color of the color lookup table. RCLUT: Red Color Entry This field indicates the 8-bit width Red color of the color lookup table. ACLUT: Alpha Color Entry This field indicates the 8-bit width Alpha channel of the color lookup table. DS60001476B-page 944  2017 Microchip Technology Inc. SAMA5D2 SERIES 40. Ethernet MAC (GMAC) 40.1 Description The Ethernet MAC (GMAC) module implements a 10/100 Mbps Ethernet MAC compatible with the IEEE 802.3 standard. The GMAC can operate in either half or full duplex mode at all supported speeds. The GMAC Network Configuration Register is used to select the speed, duplex mode and interface type (MII, RMII). 40.2 • • • • • • • • • • • • • • • • • • • • • • • • • • Embedded Characteristics Compatible with IEEE Standard 802.3 10, 100 Mbps Operation Full and Half Duplex Operation at all Supported Speeds of Operation Statistics Counter Registers for RMON/MIB MII/RMII Interface to the Physical Layer Integrated Physical Coding Direct Memory Access (DMA) Interface to External Memory Support for 3 Priority Queues 8 Kbytes Transmit RAM and 4 Kbytes Receive RAM (refer to Table 40-6 for queue-specific sizes) Programmable Burst Length and Endianism for DMA Interrupt Generation to Signal Receive and Transmit Completion, Errors or Other Events Automatic Pad and Cyclic Redundancy Check (CRC) Generation on Transmitted Frames Automatic Discard of Frames Received with Errors Receive and Transmit IP, TCP and UDP Checksum Offload. Both IPv4 and IPv6 Packet Types Supported Address Checking Logic for Four Specific 48-bit Addresses, Four Type IDs, Promiscuous Mode, Hash Matching of Unicast and Multicast Destination Addresses and Wake-on-LAN Management Data Input/Output (MDIO) Interface for Physical Layer Management Support for Jumbo Frames up to 10240Bytes Full Duplex Flow Control with Recognition of Incoming Pause Frames and Hardware Generation of Transmitted Pause Frames Half Duplex Flow Control by Forcing Collisions on Incoming Frames Support for 802.1Q VLAN Tagging with Recognition of Incoming VLAN and Priority Tagged Frames Support for 802.1Qbb Priority-based Flow Control Programmable Inter Packet Gap (IPG) Stretch Recognition of IEEE 1588 PTP Frames IEEE 1588 Timestamp Unit (TSU) Support for 802.1AS Timing and Synchronization Supports 802.1Qav Traffic Shaping on Two Highest Priority Queues  2017 Microchip Technology Inc. DS60001476B-page 945 SAMA5D2 SERIES 40.3 Block Diagram Figure 40-1: Block Diagram Status & Statistic Registers Register Interface APB MDIO Control Registers MAC Transmitter AHB DMA Interface AHB FIFO Interface Media Interface MAC Receiver Frame Filtering Packet Buffer Memories 40.4 Signal Interfaces The GMAC includes the following signal interfaces: • • • • • MII, RMII to an external PHY MDIO interface for external PHY management Slave APB interface for accessing GMAC registers Master AHB interface for memory access GTSUCOMP signal for TSU timer count value comparison Table 40-1: GMAC Connections in Different Modes Signal Name Function MII RMII GTXCK(1) Transmit Clock or Reference Clock TXCK REFCK GTXEN Transmit Enable TXEN TXEN GTX[3..0] Transmit Data TXD[3:0] TXD[1:0] GTXER Transmit Coding Error TXER Not Used GRXCK Receive Clock RXCK Not Used GRXDV Receive Data Valid RXDV CRSDV GRX[3..0] Receive Data RXD[3:0] RXD[1:0] GRXER Receive Error RXER RXER GCRS Carrier Sense and Data Valid CRS Not Used DS60001476B-page 946  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-1: GMAC Connections in Different Modes (Continued) Signal Name Function MII RMII GCOL Collision Detect COL Not Used GMDC Management Data Clock MDC MDC GMDIO Management Data Input/Output MDIO MDIO Note 1: Input only. GTXCK must be provided with a 25 MHz / 50 MHz external crystal oscillator for MII / RMII interfaces, respectively. 40.5 Product Dependencies 40.5.1 I/O Lines The pins used for interfacing the GMAC may be multiplexed with PIO lines. The programmer must first program the PIO Controller to assign the pins to their peripheral function. If I/O lines of the GMAC are not used by the application, they can be used for other purposes by the PIO Controller. Table 40-2: I/O Lines Instance Signal I/O Line Peripheral GMAC GCOL PB9 F GMAC GCOL PC23 B GMAC GCOL PD4 D GMAC GCRS PB8 F GMAC GCRS PC22 B GMAC GCRS PD3 D GMAC GMDC PB22 F GMAC GMDC PC18 B GMAC GMDC PD17 D GMAC GMDIO PB23 F GMAC GMDIO PC19 B GMAC GMDIO PD18 D GMAC GRXCK PB7 F GMAC GRXCK PC20 B GMAC GRXCK PD1 D GMAC GRXDV PB16 F GMAC GRXDV PC12 B GMAC GRXDV PD11 D GMAC GRXER PB17 F GMAC GRXER PC13 B GMAC GRXER PD12 D GMAC GRX0 PB18 F GMAC GRX0 PC14 B GMAC GRX0 PD13 D GMAC GRX1 PB19 F  2017 Microchip Technology Inc. DS60001476B-page 947 SAMA5D2 SERIES Table 40-2: 40.5.2 I/O Lines GMAC GRX1 PC15 B GMAC GRX1 PD14 D GMAC GRX2 PB10 F GMAC GRX2 PC24 B GMAC GRX2 PD5 D GMAC GRX3 PB11 F GMAC GRX3 PC25 B GMAC GRX3 PD6 D GMAC GTSUCOMP PB5 F GMAC GTSUCOMP PC9 B GMAC GTSUCOMP PD0 D GMAC GTXCK PB14 F GMAC GTXCK PC10 B GMAC GTXCK PD9 D GMAC GTXEN PB15 F GMAC GTXEN PC11 B GMAC GTXEN PD10 D GMAC GTXER PB6 F GMAC GTXER PC21 B GMAC GTXER PD2 D GMAC GTX0 PB20 F GMAC GTX0 PC16 B GMAC GTX0 PD15 D GMAC GTX1 PB21 F GMAC GTX1 PC17 B GMAC GTX1 PD16 D GMAC GTX2 PB12 F GMAC GTX2 PC26 B GMAC GTX2 PD7 D GMAC GTX3 PB13 F GMAC GTX3 PC27 B GMAC GTX3 PD8 D Power Management The GMAC is not continuously clocked. The user must first enable the GMAC clock in the Power Management Controller before using it. 40.5.3 Interrupt Sources The GMAC interrupt line is connected to one of the internal sources of the interrupt controller. Using the GMAC interrupt requires prior programming of the interrupt controller. DS60001476B-page 948  2017 Microchip Technology Inc. SAMA5D2 SERIES The GMAC features 3 interrupt sources. Refer to Table 11-1 "Peripheral Identifiers" for the interrupt numbers for GMAC priority queues. Table 40-3: Peripheral IDs Instance ID GMAC 5 40.6 40.6.1 Functional Description Media Access Controller The Media Access Controller (MAC) transmit block takes data from FIFO, adds preamble and, if necessary, pad and frame check sequence (FCS). Both half duplex and full duplex Ethernet modes of operation are supported. When operating in half duplex mode, the MAC transmit block generates data according to the carrier sense multiple access with collision detect (CSMA/CD) protocol. The start of transmission is deferred if carrier sense (CRS) is active. If collision (COL) becomes active during transmission, a jam sequence is asserted and the transmission is retried after a random backoff. The CRS and COL signals have no effect in full duplex mode. The MAC receive block checks for valid preamble, FCS, alignment and length, and presents received frames to the MAC address checking block and FIFO. Software can configure the GMAC to receive jumbo frames up to 10240bytes. It can optionally strip CRC from the received frame prior to transfer to FIFO. The address checker recognizes four specific 48-bit addresses, can recognize four different type ID values, and contains a 64-bit Hash register for matching multicast and unicast addresses as required. It can recognize the broadcast address of all ones and copy all frames. The MAC can also reject all frames that are not VLAN tagged and recognize Wake on LAN events. The MAC receive block supports offloading of IP, TCP and UDP checksum calculations (both IPv4 and IPv6 packet types supported), and can automatically discard bad checksum frames. 40.6.2 1588 Timestamp Unit The 1588 timestamp unit (TSU) is implemented as a 94-bit timer. The 48 upper bits [93:46] of the timer count seconds and are accessible in the “GMAC 1588 Timer Seconds High Register” (GMAC_TSH) and “GMAC 1588 Timer Seconds Low Register” (GMAC_TSL). The 30 lower bits [45:16] of the timer count nanoseconds and are accessible in the “GMAC 1588 Timer Nanoseconds Register” (GMAC_TN). The lowest 16 bits [15:0] of the timer count sub-nanoseconds. The 46 lower bits roll over when they have counted to one second. The timer increments by a programmable period (to approximately 15.2 femtoseconds resolution) with each MCK period and can also be adjusted in 1ns resolution (incremented or decremented) through APB register accesses. 40.6.3 AHB Direct Memory Access Interface The GMAC DMA controller is connected to the MAC FIFO interface and provides a scatter-gather type capability for packet data storage. The DMA implements packet buffering where dual-port memories are used to buffer multiple frames.  2017 Microchip Technology Inc. DS60001476B-page 949 SAMA5D2 SERIES 40.6.3.1 Packet Buffer DMA • Easier to guarantee maximum line rate due to the ability to store multiple frames in the packet buffer, where the number of frames is limited by the amount of packet buffer memory and Ethernet frame size • Full store and forward, or partial store and forward programmable options (partial store will cater for shorter latency requirements) • Support for Transmit TCP/IP checksum offload • Support for priority queueing • When a collision on the line occurs during transmission, the packet will be automatically replayed directly from the packet buffer memory rather than having to re-fetch through the AHB (full store and forward ONLY) • Received error packets are automatically dropped before any of the packet is presented to the AHB (full store and forward ONLY), thus reducing AHB activity • Supports manual RX packet flush capabilities • Optional RX packet flush when there is lack of AHB resource 40.6.3.2 Partial Store and Forward Using Packet Buffer DMA The DMA uses SRAM-based packet buffers, and can be programmed into a low latency mode, known as Partial Store and Forward. This allows for a reduced latency as the full packet is not buffered before forwarding. Note that this option is only available when the device is configured for full duplex operation. This feature is enabled via the programmable TX and RX Partial Store and Forward registers. When the transmit Partial Store and Forward mode is activated, the transmitter will only begin to forward the packet to the MAC when there is enough packet data stored in the packet buffer. Likewise, when the receive Partial Store and Forward mode is activated, the receiver will only begin to forward the packet to the AHB when enough packet data is stored in the packet buffer. The amount of packet data required to activate the forwarding process is programmable via watermark registers which are located at the same address as the partial store and forward enable bits. Note that the minimum operational value for the TX partial store and forward watermark is 20. There is no operational limit for the RX partial store and forward watermark. Enabling partial store and forward is a useful means to reduce latency, but there are performance implications. The GMAC DMA uses separate transmit and receive lists of buffer descriptors, with each descriptor describing a buffer area in memory. This allows Ethernet packets to be broken up and scattered around the AHB memory space. 40.6.3.3 Receive AHB Buffers Received frames, optionally including FCS, are written to receive AHB buffers stored in memory. The receive buffer depth is programmable in the range of 64 bytes to 16 Kbytes through the DMA Configuration register, with the default being 128 bytes. The start location for each receive AHB buffer is stored in memory in a list of receive buffer descriptors at an address location pointed to by the receive buffer queue pointer. The base address for the receive buffer queue pointer is configured in software using the Receive Buffer Queue Base Address register. Each list entry consists of two words. The first is the address of the receive AHB buffer and the second the receive status. If the length of a receive frame exceeds the AHB buffer length, the status word for the used buffer is written with zeroes except for the “start of frame” bit, which is always set for the first buffer in a frame. Bit zero of the address field is written to 1 to show the buffer has been used. The receive buffer manager then reads the location of the next receive AHB buffer and fills that with the next part of the received frame data. AHB buffers are filled until the frame is complete and the final buffer descriptor status word contains the complete frame status. Refer to Table 40-4 for details of the receive buffer descriptor list. Each receive AHB buffer start location is a word address. The start of the first AHB buffer in a frame 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 AHB buffer is offset, the available length of the first AHB buffer is reduced by the corresponding number of bytes. Table 40-4: Bit Receive Buffer Descriptor Entry Function Word 0 31:2 Address of beginning of buffer 1 Wrap—marks last descriptor in receive buffer descriptor list. 0 Ownership—needs to be zero for the GMAC to write data to the receive buffer. The GMAC 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 DS60001476B-page 950  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-4: Receive Buffer Descriptor Entry (Continued) Bit Function 31 Global all ones broadcast address detected 30 Multicast hash match 29 Unicast hash match 28 – 27 Specific Address Register match found, bit 25 and bit 26 indicate which Specific Address Register causes the match. Specific Address Register match. Encoded as follows: 00: Specific Address Register 1 match 26:25 01: Specific Address Register 2 match 10: Specific Address Register 3 match 11: Specific Address Register 4 match If more than one specific address is matched only one is indicated with priority 4 down to 1. This bit has a different meaning depending on whether RX checksum offloading is enabled. With RX checksum offloading disabled: (bit 24 clear in Network Configuration Register) 24 Type ID register match found, bit 22 and bit 23 indicate which type ID register causes the match. With RX checksum offloading enabled: (bit 24 set in Network Configuration Register) 0: The frame was not SNAP encoded and/or had a VLAN tag with the Canonical Format Indicator (CFI) bit set. 1: The frame was SNAP encoded and had either no VLAN tag or a VLAN tag with the CFI bit not set. This bit has a different meaning depending on whether RX checksum offloading is enabled. With RX checksum offloading disabled: (bit 24 clear in Network Configuration) Type ID register match. Encoded as follows: 00: Type ID register 1 match 01: Type ID register 2 match 10: Type ID register 3 match 23:22 11: Type ID register 4 match If more than one Type ID is matched only one is indicated with priority 4 down to 1. With RX checksum offloading enabled: (bit 24 set in Network Configuration Register) 00: Neither the IP header checksum nor the TCP/UDP checksum was checked. 01: The IP header checksum was checked and was correct. Neither the TCP nor UDP checksum was checked. 10: Both the IP header and TCP checksum were checked and were correct. 11: Both the IP header and UDP checksum were checked and were correct. 21 VLAN tag detected—type ID of 0x8100. For packets incorporating the stacked VLAN processing feature, this bit will be set if the second VLAN tag has a type ID of 0x8100 20 Priority tag detected—type ID of 0x8100 and null VLAN identifier. For packets incorporating the stacked VLAN processing feature, this bit will be set if the second VLAN tag has a type ID of 0x8100 and a null VLAN identifier. 19:17 VLAN priority—only valid if bit 21 is set. 16 Canonical format indicator (CFI) bit (only valid if bit 21 is set). 15 End of frame—when set the buffer contains the end of a frame. If end of frame is not set, then the only valid status bit is start of frame (bit 14). 14 Start of frame—when set the buffer contains the start of a frame. If both bits 15 and 14 are set, the buffer contains a whole frame.  2017 Microchip Technology Inc. DS60001476B-page 951 SAMA5D2 SERIES Table 40-4: Bit Receive Buffer Descriptor Entry (Continued) Function This bit has a different meaning depending on whether jumbo frames and ignore FCS modes are enabled. If neither mode is enabled this bit will be zero. With jumbo frame mode enabled: (bit 3 set in Network Configuration Register) Additional bit for length of frame (bit[13]), that is concatenated with bits[12:0] 13 With ignore FCS mode enabled and jumbo frames disabled: (bit 26 set in Network Configuration Register and bit 3 clear in Network Configuration Register) This indicates per frame FCS status as follows: 0: Frame had good FCS 1: Frame had bad FCS, but was copied to memory as ignore FCS enabled. These bits represent the length of the received frame which may or may not include FCS depending on whether FCS discard mode is enabled. With FCS discard mode disabled: (bit 17 clear in Network Configuration Register) 12:0 Least significant 12 bits for length of frame including FCS. If jumbo frames are enabled, these 12 bits are concatenated with bit[13] of the descriptor above. With FCS discard mode enabled: (bit 17 set in Network Configuration Register) Least significant 12 bits for length of frame excluding FCS. If jumbo frames are enabled, these 12 bits are concatenated with bit[13] of the descriptor above. To receive frames, the AHB buffer descriptors must be initialized by writing an appropriate address to bits 31:2 in the first word of each list entry. Bit 0 must be written with zero. Bit 1 is the wrap bit and indicates the last entry in the buffer descriptor list. The start location of the receive buffer descriptor list must be written with the receive buffer queue base address before reception is enabled (receive enable in the Network Control register). Once reception is enabled, any writes to the Receive Buffer Queue Base Address register are ignored. When read, it will return the current pointer position in the descriptor list, though this is only valid and stable when receive is disabled. If the filter block indicates that a 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. An internal counter within the GMAC represents the receive buffer queue pointer and it is not visible through the CPU interface. The receive buffer queue pointer increments by two words after each buffer has been used. It re-initializes to the receive buffer queue base address if any descriptor has its wrap bit set. As receive AHB buffers are used, the receive AHB buffer manager sets bit zero of the first word of the descriptor to logic one indicating the AHB buffer has been used. Software should search through the “used” bits in the AHB buffer descriptors to find out how many frames have been received, checking the start of frame and end of frame bits. When the DMA is configured in the packet buffer Partial Store And Forward mode, received frames are written out to the AHB buffers as soon as enough frame data exists in the packet buffer. For both cases, this may mean several full AHB buffers are used before some error conditions can be detected. If a receive error is detected the receive buffer currently being written will be recovered. Previous buffers will not be recovered. As an example, when receiving frames with cyclic redundancy check (CRC) errors or excessive length, it is possible that a frame fragment might be stored in a sequence of AHB 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. To function properly, a 10/100 Ethernet system should have no excessive length frames or frames greater than 128 bytes with CRC errors. Collision fragments will be less than 128 bytes long, therefore it will be a rare occurrence to find a frame fragment in a receive AHB buffer, when using the default value of 128 bytes for the receive buffers size. When in packet buffer full store and forward mode, only good received frames are written out of the DMA, so no fragments will exist in the AHB buffers due to MAC receiver errors. There is still the possibility of fragments due to DMA errors, for example used bit read on the second buffer of a multi-buffer frame. DS60001476B-page 952  2017 Microchip Technology Inc. SAMA5D2 SERIES If bit zero of the receive buffer descriptor is already set when the receive buffer manager reads the location of the receive AHB buffer, then the buffer has been already used and cannot be used again until software has processed the frame and cleared bit zero. In this case, the “buffer not available” bit in the Receive Status register is set and an interrupt triggered. The Receive Resource Error statistics register is also incremented. When the DMA is configured in the packet buffer full store and forward mode, the user can optionally select whether received frames should be automatically discarded when no AHB buffer resource is available. This feature is selected via bit 24 of the DMA Configuration register (by default, the received frames are not automatically discarded). If this feature is off, then received packets will remain to be stored in the SRAM-based packet buffer until AHB buffer resource next becomes available. This may lead to an eventual packet buffer overflow if packets continue to be received when bit zero (used bit) of the receive buffer descriptor remains set. Note that after a used bit has been read, the receive buffer manager will re-read the location of the receive buffer descriptor every time a new packet is received. When the DMA is not configured in the packet buffer full store and forward mode and a used bit is read, the frame currently being received will be automatically discarded. When the DMA is configured in the packet buffer full store and forward mode, a receive overrun condition occurs when the receive SRAMbased packet buffer is full, or because HRESP was not OK. In all other modes, a receive overrun condition occurs when either the AHB bus was not granted quickly enough, or because HRESP was not OK, or because a new frame has been detected by the receive block, but the status update or write back for the previous frame has not yet finished. For a receive overrun condition, the receive overrun interrupt is asserted and the buffer currently being written is recovered. The next frame that is received whose address is recognized reuses the buffer. In any packet buffer mode, a write to bit 18 of GMAC_NCR will force a packet from the external SRAM-based receive packet buffer to be flushed. This feature is only acted upon when the RX DMA is not currently writing packet data out to AHB, i.e., it is in an IDLE state. If the RX DMA is active, a write to this bit is ignored. 40.6.3.4 Transmit AHB Buffers Frames to transmit are stored in one or more transmit AHB buffers. Transmit frames can be between 1 and 16384 bytes long, so it is possible to transmit frames longer than the maximum length specified in the IEEE 802.3 standard. It should be noted that zero length AHB buffers are allowed and that the maximum number of buffers permitted for each transmit frame is 128. The start location for each transmit AHB buffer is stored in memory in a list of transmit buffer descriptors at a location pointed to by the transmit buffer queue pointer. The base address for this queue pointer is set in software using the Transmit Buffer Queue Base Address register. Each list entry consists of two words. The first is the byte address of the transmit buffer and the second containing the transmit control and status. For the packet buffer DMA, the start location for each AHB buffer is a byte address, the bottom bits of the address being used to offset the start of the data from the data-word boundary (i.e., bits 2,1 and 0 are used to offset the address for 64-bit datapaths). Frames can be transmitted with or without automatic CRC generation. If CRC is automatically generated, pad will also be automatically generated to take frames to a minimum length of 64 bytes. When CRC is not automatically generated (as defined in word 1 of the transmit buffer descriptor), the frame is assumed to be at least 64 bytes long and pad is not generated. An entry in the transmit buffer descriptor list is described in Table 40-5. To transmit frames, the buffer descriptors must be initialized by writing an appropriate byte address to bits [31:0] in the first word of each descriptor list entry. The second word of the transmit buffer descriptor is initialized with control information that indicates the length of the frame, whether or not the MAC is to append CRC and whether the buffer is the last buffer in the frame. After transmission the status bits are written back to the second word of the first buffer along with the used bit. Bit 31 is the used bit which must be zero when the control word is read if transmission is to take place. It is written to one once the frame has been transmitted. Bits[29:20] 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 the queue pointer continues to increment. The Transmit Buffer Queue Base Address register can only be updated while transmission is disabled or halted; otherwise any attempted write will be ignored. When transmission is halted the transmit buffer queue pointer will maintain its value. Therefore when transmission is restarted the next descriptor read from the queue will be from immediately after the last successfully transmitted frame. while transmit is disabled (bit 3 of the Network Control register set low), the transmit buffer queue pointer resets to point to the address indicated by the Transmit Buffer Queue Base Address register. Note that disabling receive does not have the same effect on the receive buffer queue pointer. Once the transmit queue is initialized, transmit is activated by writing to the transmit start bit (bit 9) of the Network Control register. Transmit is halted when a buffer descriptor with its used bit set is read, 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. This is implemented with TXGO variable which is readable in the Transmit Status register at bit location 3. The TXGO variable is reset when: • Transmit is disabled.  2017 Microchip Technology Inc. DS60001476B-page 953 SAMA5D2 SERIES • A buffer descriptor with its ownership bit set is read. • Bit 10, THALT, of the Network Control register is written. • There is a transmit error such as too many retries or a transmit underrun. To set TXGO, write TSTART to the bit 9 of the Network Control register. Transmit halt does not take effect until any ongoing transmit finishes. If the DMA is configured for packet buffer Partial Store and Forward mode and a collision occurs during transmission of a multi-buffer frame, transmission will automatically restart from the first buffer of the frame. For packet buffer mode, the entire contents of the frame are read into the transmit packet buffer memory, so the retry attempt will be replayed directly from the packet buffer memory rather than having to re-fetch through the AHB. If an used bit is read midway through transmission of a multi-buffer frame, this is treated as a transmit error. Transmission stops, GTXER is asserted and the FCS will be bad. If transmission stops due to a transmit error or a used bit being read, transmission restarts from the first buffer descriptor of the frame being transmitted when the transmit start bit is rewritten. Table 40-5: Bit Transmit Buffer Descriptor Entry Function Word 0 31:0 Byte address of buffer Word 1 31 Used—must be zero for the GMAC to read data to the transmit buffer. The GMAC sets this to one for the first buffer of a frame once it has been successfully transmitted. Software must clear this bit before the buffer can be used again. 30 Wrap—marks last descriptor in transmit buffer descriptor list. This can be set for any buffer within the frame. 29 Retry limit exceeded, transmit error detected 28 Reserved. 27 Transmit frame corruption due to AHB error—set if an error occurs while midway through reading transmit frame from the AHB, including HRESP errors and buffers exhausted mid frame (if the buffers run out during transmission of a frame then transmission stops, FCS shall be bad and GTXER asserted). Also set if single frame is too large for configured packet buffer memory size. 26 25:23 Late collision, transmit error detected. Reserved Transmit IP/TCP/UDP checksum generation offload errors: 000: No Error. 001: The Packet was identified as a VLAN type, but the header was not fully complete, or had an error in it. 010: The Packet was identified as a SNAP type, but the header was not fully complete, or had an error in it. 22:20 011: The Packet was not of an IP type, or the IP packet was invalidly short, or the IP was not of type IPv4/IPv6. 100: The Packet was not identified as VLAN, SNAP or IP. 101: Non supported packet fragmentation occurred. For IPv4 packets, the IP checksum was generated and inserted. 110: Packet type detected was not TCP or UDP. TCP/UDP checksum was therefore not generated. For IPv4 packets, the IP checksum was generated and inserted. 111: A premature end of packet was detected and the TCP/UDP checksum could not be generated. 19:17 Reserved No CRC to be appended by MAC. When set, this implies that the data in the buffers already contains a valid CRC, hence no CRC or padding is to be appended to the current frame by the MAC. 16 This control bit must be set for the first buffer in a frame and will be ignored for the subsequent buffers of a frame. Note that this bit must be clear when using the transmit IP/TCP/UDP checksum generation offload, otherwise checksum generation and substitution will not occur. DS60001476B-page 954  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-5: Transmit Buffer Descriptor Entry (Continued) Bit Function 15 Last buffer, when set this bit will indicate the last buffer in the current frame has been reached. 14 Reserved 13:0 Length of buffer  2017 Microchip Technology Inc. DS60001476B-page 955 SAMA5D2 SERIES 40.6.3.5 DMA Bursting on the AHB The DMA will always use SINGLE, or INCR type AHB accesses for buffer management operations. When performing data transfers, the AHB burst length used can be programmed using bits 4:0 of the DMA Configuration register so that either SINGLE, INCR or fixed length incrementing bursts (INCR4, INCR8 or INCR16) are used where possible. When there is enough space and enough data to be transferred, the programmed fixed length bursts will be used. If there is not enough data or space available, for example when at the beginning or the end of a buffer, SINGLE type accesses are used. Also SINGLE type accesses are used at 1024 byte boundaries, so that the 1 Kbyte boundaries are not burst over as per AHB requirements. The DMA will not terminate a fixed length burst early, unless an error condition occurs on the AHB or if receive or transmit are disabled in the Network Control register. 40.6.3.6 DMA Packet Buffer The DMA uses packet buffers for both transmit and receive paths. This mode allows multiple packets to be buffered in both transmit and receive directions. This allows the DMA to withstand far greater access latencies on the AHB and make more efficient use of the AHB bandwidth. There are two modes of operation—Full Store and Forward and Partial Store and Forward. As described above (Section 40.6.3.2 ”Partial Store and Forward Using Packet Buffer DMA”), the DMA can be programmed into a low latency mode, known as Partial Store and Forward. For further details of this mode, see Section 40.6.3.2 “Partial Store and Forward Using Packet Buffer DMA”. When the DMA is in full store and forward mode, full packets are buffered which provides the possibility to: • Discard packets with error on the receive path before they are partially written out of the DMA, thus saving AHB bus bandwidth and driver processing overhead, • Retry collided transmit frames from the buffer, thus saving AHB bus bandwidth, • Implement transmit IP/TCP/UDP checksum generation offload. With the packet buffers included, the structure of the GMAC data paths is shown in Figure 40-2. DS60001476B-page 956  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 40-2: Data Paths with Packet Buffers Included TX GMII MAC Transmitter TX Packet Buffer DPSRAM TX Packet Buffer TX DMA APB Register Interface Status and Statistic Registers AHB AHB DMA RX DMA MDIO Control Interface RX Packet Buffer DPSRAM RX Packet Buffer RX GMII MAC Receive Frame Filtering Ethernet MAC 40.6.3.7 Transmit Packet Buffer The transmitter packet buffer will continue attempting to fetch frame data from the AHB system memory until the packet buffer itself is full, at which point it will attempt to maintain its full level. To accommodate the status and statistics associated with each frame, three words per packet (or two if the GMAC is configured in 64-bit datapath mode) are reserved at the end of the packet data. If the packet is bad and requires to be dropped, the status and statistics are the only information held on that packet. Storing the status in the DPRAM is required in order to decouple the DMA interface of the buffer from the MAC interface, to update the MAC status/statistics and to generate interrupts in the order in which the packets that they represent were fetched from the AHB memory. If any errors occur on the AHB while reading the transmit frame, the fetching of packet data from AHB memory is halted. The MAC transmitter will continue to fetch packet data, thereby emptying the packet buffer and allowing any good non-errored frames to be transmitted successfully. Once these have been fully transmitted, the status/statistics for the errored frame will be updated and software will be informed via an interrupt that an AHB error occurred. This way, the error is reported in the correct packet order. The transmit packet buffer will only attempt to read more frame data from the AHB when space is available in the packet buffer memory. If space is not available it must wait until the a packet fetched by the MAC completes transmission and is subsequently removed from the packet buffer memory. Note that if full store and forward mode is active and if a single frame is fetched that is too large for the packet buffer  2017 Microchip Technology Inc. DS60001476B-page 957 SAMA5D2 SERIES memory, the frame is flushed and the DMA halted with an error status. This is because a complete frame must be written into the packet buffer before transmission can begin, and therefore the minimum packet buffer memory size should be chosen to satisfy the maximum frame to be transmitted in the application. In full store and forward mode, once the complete transmit frame is written into the packet buffer memory, a trigger is sent across to the MAC transmitter, which will then begin reading the frame from the packet buffer memory. Since the whole frame is present and stable in the packet buffer memory an underflow of the transmitter is not possible. The frame is kept in the packet buffer until notification is received from the MAC that the frame data has either been successfully transmitted or can no longer be retransmitted (too many retries in half duplex mode). When this notification is received the frame is flushed from memory to make room for a new frame to be fetched from AHB system memory. In Partial Store and Forward mode, a trigger is sent across to the MAC transmitter as soon as sufficient packet data is available, which will then begin fetching the frame from the packet buffer memory. If, after this point, the MAC transmitter is able to fetch data from the packet buffer faster than the AHB DMA can fill it, an underflow of the transmitter is possible. In this case, the transmission is terminated early, and the packet buffer is completely flushed. Transmission can only be restarted by writing to the transmit START bit. In half duplex mode, the frame is kept in the packet buffer until notification is received from the MAC that the frame data has either been successfully transmitted or can no longer be retransmitted (too many retries in half duplex mode). When this notification is received the frame is flushed from memory to make room for a new frame to be fetched from AHB system memory. In full duplex mode, the frame is removed from the packet buffer on the fly. Other than underflow, the only MAC related errors that can occur are due to collisions during half duplex transmissions. When a collision occurs the frame still exists in the packet buffer memory so can be retried directly from there. Only once the MAC transmitter has failed to transmit after sixteen attempts is the frame finally flushed from the packet buffer. 40.6.3.8 Receive Packet Buffer The receive packet buffer stores frames from the MAC receiver along with their status and statistics. Frames with errors are flushed from the packet buffer memory, while good frames are pushed onto the DMA AHB interface. The receiver packet buffer monitors the FIFO write interface from the MAC receiver and translates the FIFO pushes into packet buffer writes. At the end of the received frame the status and statistics are buffered so that the information can be used when the frame is read out. When programmed in full store and forward mode, if the frame has an error the frame data is immediately flushed from the packet buffer memory allowing subsequent frames to utilise the freed up space. The status and statistics for bad frames are still used to update the GMAC registers. To accommodate the status and statistics associated with each frame, three words per packet (or two if configured in 64-bit datapath mode) are reserved at the end of the packet data. If the packet is bad and requires to be dropped, the status and statistics are the only information held on that packet. The receiver packet buffer will also detect a full condition so that an overflow condition can be detected. If this occurs, subsequent packets are dropped and an RX overflow interrupt is raised. For full store and forward, the DMA only begins packet fetches once the status and statistics for a frame are available. If the frame has a bad status due to a frame error, the status and statistics are passed on to the GMAC registers. If the frame has a good status, the information is used to read the frame from the packet buffer memory and burst onto the AHB using the DMA buffer management protocol. Once the last frame data has been transferred to the packet buffer, the status and statistics are updated to the GMAC registers. If Partial Store and Forward mode is active, the DMA will begin fetching the packet data before the status is available. As soon as the status becomes available, the DMA will fetch this information as soon as possible before continuing to fetch the remainder of the frame. Once the last frame data has been transferred to the packet buffer, the status and statistics are updated to the GMAC registers. 40.6.3.9 Priority Queueing in the DMA The DMA by default uses a single transmit and receive queue. This means the list of transmit/receive buffer descriptors point to data buffers associated with a single transmit/receive data stream. The GMAC can select up to 3 priority queues. Each queue has an independent list of buffer descriptors pointing to separate data streams. The table below gives the DPRAM size associated with each queue: Table 40-6: Queue Size Queue Number Queue Size 2 4 KB 1 2 KB 0 (lowest priority) 2 KB DS60001476B-page 958  2017 Microchip Technology Inc. SAMA5D2 SERIES In the transmit direction, higher priority queues are always serviced before lower priority queues, with Q0 as lowest priority and Q2 as highest priority. This strict priority scheme requires the user to ensure that high priority traffic is constrained so that lower priority traffic will have required bandwidth. The GMAC DMA will determine the next queue to service by initiating a sequence of buffer descriptor reads interrogating the ownership bits of each. The buffer descriptor corresponding to the highest priority queue is read first. As an example, if the ownership bit of this descriptor is set, then the DMA will progress to reading the 2nd highest priority queue’s descriptor. If that ownership bit read of this lower priority queue is set, then the DMA will read the 3rd highest priority queue’s descriptor. If all the descriptors return an ownership bit set, then a resource error has occurred, an interrupt is generated and transmission is automatically halted. Transmission can only be restarted by setting the START bit in the Network Control register. The GMAC DMA will need to identify the highest available queue to transmit from when the START bit in the Network Control register is written to and the TX is in a halted state, or when the last word of any packet has been fetched from external AHB memory. The GMAC transmit DMA maximizes the effectiveness of priority queuing by ensuring that high priority traffic be transmitted as early as possible after being fetched from AHB. High priority traffic fetched from AHB will be pushed to the MAC layer, depending on traffic shaping being enabled and the associated credit value for that queue, before any lower priority traffic that may pre-exist in the transmit SRAMbased packet buffer. This is achieved by separating the transmit SRAM-based packet buffer into regions, one region per queue. The size of each region determines the amount of SRAM space allocated per queue. For each queue, there is an associated Transmit Buffer Queue Base Address register. For the lowest priority queue (or the only queue when only one queue is selected), the Transmit Buffer Queue Base Address is located at address 0x1C. For all other queues, the Transmit Buffer Queue Base Address registers are located at sequential addresses starting at address 0x440. In the receive direction each packet is written to AHB data buffers in the order that it is received. For each queue, there is an independent set of receive AHB buffers for each queue. There is therefore a separate Receive Buffer Queue Base Address register for each queue. For the lowest priority queue (or the only queue when only one queue is selected), the Receive Buffer Queue Base Address is located at address 0x18. For all other queues, the Receive Buffer Queue Base Address registers are located at sequential addresses starting at address 0x480. Every received packet will pass through a programmable screening algorithm which will allocate a particular queue to that frame. The user interface to the screeners is through two types of programmable registers: • Screening Type 1 registers—The module features 4 Screening Type 1 registers. Screening Type 1 registers hold values to match against specific IP and UDP fields of the received frames. The fields matched against are DS (Differentiated Services field of IPv4 frames), TC (Traffic class field of IPv6 frames) and/or the UDP destination port. • Screening Type 2 registers—The module features 8 Screening Type 2 registers GMAC_ST2RPQ. Screening Type 2 registers operate independently of Screening Type 1 registers and offer additional match capabilities. Screening Type 2 allows a screen to be configured that is the combination of all or any of the following comparisons: 1. An enable bit VLAN priority, VLANE. A VLAN priority match will be performed if the VLAN priority enable is set. The extracted priority field in the VLAN header is compared against VLANP in the GMAC_ST2RPQ register itself. 2. An enable bit EtherType, ETHE. The EtherType field I2ETH inside GMAC_ST2RPQ maps to one of 4 EtherType match registers, GMAC_ST2ER. The extracted EtherType is compared against GMAC_ST2ER designated by this EtherType field. 3. An enable bit Compare A, COMPAE. This bit is associated with a Screening Type 2 Compare Word 0/1 register x, GMAC_ST2CW0/ 1. 4. An enable bit Compare B, COMPBE. This bit is associated with a Screening Type 2 Compare Word 0/1 register x, GMAC_ST2CW0/ 1. 5. An enable bit Compare C, COMPCE. This bit is associated with a Screening Type 2 Compare Word 0/1 register x, GMAC_ST2CW0/1. Each screener type has an enable bit, a match pattern and a queue number. If a received frame matches on an enabled Screening register, then the frame will be tagged with the queue value in the associated Screening register, and forwarded onto the DMA and subsequently into the external memory associated with that queue. If two screeners are matched, then the one which resides at the lowest register address will take priority so care must be taken on the selection of the screener location. When the priority queuing feature is enabled, the number of interrupt outputs from the GMAC core is increased to match the number of supported queues. The number of Interrupt Status registers is increased by the same number. Only DMA related events are reported using the individual interrupt outputs, as the GMAC can relate these events to specific queues. All other events generated within the GMAC are reported in the interrupt associated with the lowest priority queue. For the lowest priority queue (or the only queue when only 1 queue is selected), the Interrupt Status register is located at address 0x24. For all other queues, the Interrupt Status register is located at sequential addresses starting at address 0x400. Note: The address matching is the first level of filtering. If there is a match, the screeners are the next level of filtering for routing the data to the appropriate queue. See Section 40.6.7 ”MAC Filtering Block” for more details. The additional screening done by the functions Compare A, B, and C each have an enable bit and compare register field. COMPA, COMPB and COMPC in GMAC_ST2RPQ are pointers to a configured offset (OFFSVAL), value (COMPVAL), and mask (MASKVAL). If enabled, the compare is true if the data at the offset into the frame, ANDed with MASKVAL, is equal to the value of COMPVAL ANDed with  2017 Microchip Technology Inc. DS60001476B-page 959 SAMA5D2 SERIES MASKVAL. A 16-bit word comparison is done. The byte at the offset number of bytes from the index start is compared to bits 7:0 of the configured COMPVAL and MASKVAL. The byte at the offset number of bytes + 1 from the index start is compared to bits 15:8 of the configured COMPVAL and MASKVAL. The offset value in bytes, OFFSVAL, ranges from 0 to 127 bytes from either the start of the frame, the byte after the EtherType field, the byte after the IP header (IPv4 or IPv6) or the byte after the TCP/UDP header. Note the logic to decode the IP header or the TCP/UDP header is reused from the TCP/UDP/IP checksum offload logic and therefore has the same restrictions on use (the main limitation is that IP fragmentation is not supported). Refer to the Checksum Offload for IP, TCP and UDP section of this documentation for further details. Compare A, B, and C use a common set of 24 GMAC_ST2CW0/1 registers, thus all COMPA, COMPB and COMPC fields in the registers GMAC_ST2RPQ point to a single pool of 24 GMAC_ST2CW0/1 registers. Note that Compare A, B and C together allow matching against an arbitrary 48 bits of data and so can be used to match against a MAC address. All enabled comparisons are ANDed together to form the overall type 2 screening match. 40.6.4 MAC Transmit Block The MAC transmitter can operate in either half duplex or full duplex mode and transmits frames in accordance with the Ethernet IEEE 802.3 standard. In half duplex mode, the CSMA/CD protocol of the IEEE 802.3 specification is followed. A small input buffer receives data through the FIFO interface which will extract data in 32-bit form. All subsequent processing prior to the final output is performed in bytes. Transmit data can be output using the MII interface. Frame assembly starts by adding preamble and the start frame delimiter. Data is taken from the transmit FIFO interface a word at a time. If necessary, padding is added to take the frame length to 60 bytes. CRC is calculated using an order 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. The no CRC bit can also be set through the FIFO interface. In full duplex mode (at all data rates), 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, the transmitter waits for the signal to become inactive, and then starts transmission after the interframe gap of 96 bit times. If the collision signal is asserted during transmission, the transmitter will transmit a jam sequence of 32 bits taken from the data register and then retry transmission after the backoff time has elapsed. If the collision occurs during either the preamble or Start Frame Delimiter (SFD), then these fields will be completed prior to generation of the jam sequence. The backoff time is based on an XOR of the 10 least significant bits of the data coming from the transmit FIFO interface and a 10-bit pseudo random number generator. The number of bits used depends on the number of collisions seen. After the first collision 1 bit is used, then the second 2 bits and so on up to the maximum of 10 bits. All 10 bits are used above ten collisions. An error will be indicated and no further attempts will be made if 16 consecutive attempts cause collision. This operation is compliant with the description in Clause 4.2.3.2.5 of the IEEE 802.3 standard which refers to the truncated binary exponential backoff algorithm. In 10/100 mode, both collisions and late collisions are treated identically, and backoff and retry will be performed up to 16 times. This condition is reported in the transmit buffer descriptor word 1 (late collision, bit 26) and also in the Transmit Status register (late collision, bit 7). An interrupt can also be generated (if enabled) when this exception occurs, and bit 5 in the Interrupt Status register will be set. In all modes of operation, if the transmit DMA underruns, a bad CRC is automatically appended using the same mechanism as jam insertion and the GTXER signal is asserted. For a properly configured system this should never happen and also it is impossible if configured to use the DMA with packet buffers, as the complete frame is buffered in local packet buffer memory. By setting when bit 28 is set in the Network Configuration register, the Inter Packet Gap (IPG) may be stretched beyond 96 bits depending on the length of the previously transmitted frame and the value written to the IPG Stretch register (GMAC_IPGS). The least significant 8 bits of the IPG Stretch register multiply the previous frame length (including preamble). The next significant 8 bits (+1 so as not to get a divide by zero) divide the frame length to generate the IPG. IPG stretch only works in full duplex mode and when bit 28 is set in the Network Configuration register. The IPG Stretch register cannot be used to shrink the IPG below 96 bits. If the back pressure bit is set in the Network Control register, or if the HDFC configuration bit is set in the GMAC_UR register (10M or 100M 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. 40.6.5 MAC Receive Block All processing within the MAC receive block is implemented using a 16-bit data path. The MAC receive block checks for valid preamble, FCS, alignment and length, presents received frames to the FIFO interface and stores the frame destination address for use by the address checking block. DS60001476B-page 960  2017 Microchip Technology Inc. SAMA5D2 SERIES If, during the frame reception, the frame is found to be too long, a bad frame indication is sent to the FIFO interface. The receiver logic ceases to send data to memory as soon as this condition occurs. At end of frame reception the receive block indicates to the DMA block whether the frame is good or bad. The DMA block will recover the current receive buffer if the frame was bad. Ethernet frames are normally stored in DMA memory complete with the FCS. Setting the FCS remove bit in the network configuration (bit 17) causes frames to be stored without their corresponding FCS. The reported frame length field is reduced by four bytes to reflect this operation. The receive block signals to the register block to increment the alignment, CRC (FCS), short frame, long frame, jabber or receive symbol errors when any of these exception conditions occur. If bit 26 is set in the network configuration, CRC errors will be ignored and CRC errored frames will not be discarded, though the Frame Check Sequence Errors statistic register will still be incremented. Additionally, if not enabled for jumbo frames mode, then bit[13] of the receiver descriptor word 1 will be updated to indicate the FCS validity for the particular frame. This is useful for applications such as EtherCAT whereby individual frames with FCS errors must be identified. Received frames can be checked for length field error by setting the length field error frame discard bit of the Network Configuration register (bit-16). When this bit is set, the receiver compares a frame's measured length with the length field (bytes 13 and 14) extracted from the frame. The frame is discarded if the measured length is shorter. This checking procedure is for received frames between 64 bytes and 1518 bytes in length. Each discarded frame is counted in the 10-bit Length Field Frame Error statistics register. Frames where the length field is greater than or equal to 0x0600 hex will not be checked. 40.6.6 Checksum Offload for IP, TCP and UDP The GMAC can be programmed to perform IP, TCP and UDP checksum offloading in both receive and transmit directions, which is enabled by setting bit 24 in the Network Configuration register for receive and bit 11 in the DMA Configuration register for transmit. IPv4 packets contain a 16-bit checksum field, which is the 16-bit 1’s complement of the 1’s complement sum of all 16-bit words in the header. TCP and UDP packets contain a 16-bit checksum field, which is the 16-bit 1’s complement of the 1’s complement sum of all 16bit words in the header, the data and a conceptual IP pseudo header. To calculate these checksums in software requires each byte of the packet to be processed. For TCP and UDP this can use a large amount of processing power. Offloading the checksum calculation to hardware can result in significant performance improvements. For IP, TCP or UDP checksum offload to be useful, the operating system containing the protocol stack must be aware that this offload is available so that it can make use of the fact that the hardware can either generate or verify the checksum. 40.6.6.1 Receiver Checksum Offload When receive checksum offloading is enabled in the GMAC, the IPv4 header checksum is checked as per RFC 791, where the packet meets the following criteria: • • • • If present, the VLAN header must be four octets long and the CFI bit must not be set. Encapsulation must be RFC 894 Ethernet Type Encoding or RFC 1042 SNAP Encoding. IPv4 packet IP header is of a valid length The GMAC also checks the TCP checksum as per RFC 793, or the UDP checksum as per RFC 768, if the following criteria are met: • • • • IPv4 or IPv6 packet Good IP header checksum (if IPv4) No IP fragmentation TCP or UDP packet When an IP, TCP or UDP frame is received, the receive buffer descriptor gives an indication if the GMAC was able to verify the checksums. There is also an indication if the frame had SNAP encapsulation. These indication bits will replace the type ID match indication bits when the receive checksum offload is enabled. For details of these indication bits refer to Table 40-4 “Receive Buffer Descriptor Entry”. If any of the checksums are verified as incorrect by the GMAC, the packet is discarded and the appropriate statistics counter incremented. 40.6.6.2 Transmitter Checksum Offload The transmitter checksum offload is only available if the full store and forward mode is enabled. This is because the complete frame to be transmitted must be read into the packet buffer memory before the checksum can be calculated and written back into the headers at the beginning of the frame.  2017 Microchip Technology Inc. DS60001476B-page 961 SAMA5D2 SERIES Transmitter checksum offload is enabled by setting bit [11] in the DMA Configuration register. When enabled, it will monitor the frame as it is written into the transmitter packet buffer memory to automatically detect the protocol of the frame. Protocol support is identical to the receiver checksum offload. For transmit checksum generation and substitution to occur, the protocol of the frame must be recognized and the frame must be provided without the FCS field, by making sure that bit [16] of the transmit descriptor word 1 is clear. If the frame data already had the FCS field, this would be corrupted by the substitution of the new checksum fields. If these conditions are met, the transmit checksum offload engine will calculate the IP, TCP and UDP checksums as appropriate. Once the full packet is completely written into packet buffer memory, the checksums will be valid and the relevant DPRAM locations will be updated for the new checksum fields as per standard IP/TCP and UDP packet structures. If the transmitter checksum engine is prevented from generating the relevant checksums, bits [22:20] of the transmitter DMA writeback status will be updated to identify the reason for the error. Note that the frame will still be transmitted but without the checksum substitution, as typically the reason that the substitution did not occur was that the protocol was not recognized. 40.6.7 MAC Filtering Block The filter block determines which frames should be written to the FIFO interface and on to the DMA. Whether a frame is passed depends on what is enabled in the Network Configuration register, the state of the external matching pins, the contents of the specific address, type and Hash registers and the frame's destination address and type field. If bit 25 of the Network Configuration register is not set, a frame will not be copied to memory if the GMAC is transmitting in half duplex mode at the time a destination address is received. 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, which is the LSB of the first byte of the frame, is the group or 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 GMAC supports recognition of four specific addresses. Each specific address requires two registers, Specific Address Bottom register and Specific Address Top register. Specific Address Bottom register stores the first four bytes of the destination address and Specific Address Top register 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 Bottom register is written. They are activated when Specific Address Top register is written. If a receive frame address matches an active address, the frame is written to the FIFO interface and on to DMA memory. Frames may be filtered using the type ID field for matching. Four type ID registers exist in the register address space and each can be enabled for matching by writing a one to the MSB (bit 31) of the respective register. When a frame is received, the matching is implemented as an OR function of the various types of match. The contents of each type ID register (when enabled) are compared against the length/type ID of the frame being received (e.g., bytes 13 and 14 in non-VLAN and non-SNAP encapsulated frames) and copied to memory if a match is found. The encoded type ID match bits (Word 0, Bit 22 and Bit 23) in the receive buffer descriptor status are set indicating which type ID register generated the match, if the receive checksum offload is disabled. The reset state of the type ID registers is zero, hence each is initially disabled. The following example illustrates the use of the address and type ID match registers for a MAC address of 21:43:65:87:A9:CB: Preamble 55 SFD D5 DA (Octet 0 - LSB) 21 DA (Octet 1) 43 DA (Octet 2) 65 DA (Octet 3) 87 DA (Octet 4) A9 DA (Octet 5 - MSB) CB SA (LSB) ) DS60001476B-page 962 00(1  2017 Microchip Technology Inc. SAMA5D2 SERIES 00(1 SA ) SA ) SA ) SA ) SA (MSB) ) Type ID (MSB) 43 Type ID (LSB) 21 00(1 00(1 00(1 00(1 Note 1: Contains the address of the transmitting device 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: Specific Address 1 Bottom register (GMAC_SAB1) (Address 0x088) 0x87654321 Specific Address 1 Top register (GMAC_SAT1) (Address 0x08C) 0x0000CBA9 For a successful match to the type ID, the following Type ID Match 1 register must be set up: Type ID Match 1 register (GMAC_TIDM1) (Address 0x0A8)  2017 Microchip Technology Inc. 0x80004321 DS60001476B-page 963 SAMA5D2 SERIES 40.6.8 Broadcast Address Frames with the broadcast address of 0xFFFFFFFFFFFF are stored to memory only if the 'no broadcast' bit in the Network Configuration register is set to zero. 40.6.9 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 XOR of every sixth bit of the destination address. hash_index[05] hash_index[04] hash_index[03] hash_index[02] hash_index[01] hash_index[00] = = = = = = da[05] da[04] da[03] da[02] da[01] da[00] ^ ^ ^ ^ ^ ^ da[11] da[10] da[09] da[08] da[07] da[06] ^ ^ ^ ^ ^ ^ da[17] da[16] da[15] da[14] da[13] da[12] ^ ^ ^ ^ ^ ^ da[23] da[22] da[21] da[20] da[19] da[18] ^ ^ ^ ^ ^ ^ da[29] da[28] da[27] da[26] da[25] da[24] ^ ^ ^ ^ ^ ^ da[35] da[34] da[33] da[32] da[31] da[30] ^ ^ ^ ^ ^ ^ da[41] da[40] da[39] da[38] da[37] da[36] ^ ^ ^ ^ ^ ^ da[47] da[46] da[45] da[44] da[43] 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 will be matched according to whether the frame is multicast or unicast. A multicast match will be signalled if the multicast hash enable bit is set, da[0] is logic 1 and the hash index points to a bit set in the Hash register. A unicast match will be signalled if the unicast hash enable bit is set, da[0] is logic 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. 40.6.10 Copy all Frames (Promiscuous Mode) If the Copy All Frames bit is set in the Network Configuration register then all frames (except those that are too long, too short, have FCS errors or have GRXER asserted during reception) will be copied to memory. Frames with FCS errors will be copied if bit 26 is set in the Network Configuration register. 40.6.11 Disable Copy of Pause Frames Pause frames can be prevented from being written to memory by setting the disable copying of pause frames control bit 23 in the Network Configuration register. When set, pause frames are not copied to memory regardless of the Copy All Frames bit, whether a hash match is found, a type ID match is identified or if a destination address match is found. 40.6.12 VLAN Support The following table describes an Ethernet encoded 802.1Q VLAN tag. Table 40-7: 802.1Q VLAN Tag TPID (Tag Protocol Identifier) 16 bits TCI (Tag Control Information) 16 bits 0x8100 First 3 bits priority, then CFI bit, last 12 bits VID The VLAN tag is inserted at the 13th byte of the frame adding an extra four bytes to the frame. To support these extra four bytes, the GMAC can accept frame lengths up to 1536 bytes by setting bit 8 in the Network Configuration register. If the VID (VLAN identifier) is null (0x000) this indicates a priority-tagged frame. 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 will be 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. DS60001476B-page 964  2017 Microchip Technology Inc. SAMA5D2 SERIES The GMAC can be configured to reject all frames except VLAN tagged frames by setting the discard non-VLAN frames bit in the Network Configuration register. 40.6.13 Wake on LAN Support The receive block supports Wake on LAN by detecting the following events on incoming receive frames: • • • • Magic packet Address Resolution Protocol (ARP) request to the device IP address Specific address 1 filter match Multicast hash filter match These events can be individually enabled through bits [19:16] of the Wake on LAN register. Also, for Wake on LAN detection to occur, receive enable must be set in the Network Control register, however a receive buffer does not have to be available. In case of an ARP request, specific address 1 or multicast filter events will occur even if the frame is errored. For magic packet events, the frame must be correctly formed and error free. A magic packet event is detected if all of the following are true: • • • • • Magic packet events are enabled through bit 16 of the Wake on LAN register The frame's destination address matches specific address 1 The frame is correctly formed with no errors The frame contains at least 6 bytes of 0xFF for synchronization There are 16 repetitions of the contents of Specific Address 1 register immediately following the synchronization An ARP request event is detected if all of the following are true: • • • • • • ARP request events are enabled through bit 17 of the Wake on LAN register Broadcasts are allowed by bit 5 in the Network Configuration register The frame has a broadcast destination address (bytes 1 to 6) The frame has a type ID field of 0x0806 (bytes 13 and 14) The frame has an ARP operation field of 0x0001 (bytes 21 and 22) The least significant 16 bits of the frame's ARP target protocol address (bytes 41 and 42) match the value programmed in bits[15:0] of the Wake on LAN register The decoding of the ARP fields adjusts automatically if a VLAN tag is detected within the frame. The reserved value of 0x0000 for the Wake on LAN target address value will not cause an ARP request event, even if matched by the frame. A specific address 1 filter match event will occur if all of the following are true: • Specific address 1 events are enabled through bit 18 of the Wake on LAN register • The frame's destination address matches the value programmed in the Specific Address 1 registers A multicast filter match event will occur if all of the following are true: • • • • Multicast hash events are enabled through bit 19 of the Wake on LAN register Multicast hash filtering is enabled through bit 6 of the Network Configuration register The frame destination address matches against the multicast hash filter The frame destination address is not a broadcast 40.6.14 IEEE 1588 Support IEEE 1588 is a standard for precision time synchronization in local area networks. It works with the exchange of special Precision Time Protocol (PTP) frames. The PTP messages can be transported over IEEE 802.3/Ethernet, over Internet Protocol Version 4 or over Internet Protocol Version 6 as described in the annex of IEEE P1588.D2.1. The GMAC indicates the message timestamp point (asserted on the start packet delimiter and de-asserted at end of frame) for all frames and the passage of PTP event frames (asserted when a PTP event frame is detected and de-asserted at end of frame). IEEE 802.1AS is a subset of IEEE 1588. One difference is that IEEE 802.1AS uses the Ethernet multicast address 0180C200000E for sync frame recognition whereas IEEE 1588 does not. GMAC is designed to recognize sync frames with both IEEE 802.1AS and IEEE 1588 addresses and so can support both 1588 and 802.1AS frame recognition simultaneously. Synchronization between master and slave clocks is a two stage process. First, the offset between the master and slave clocks is corrected by the master sending a sync frame to the slave with a follow up frame containing the exact time the sync frame was sent. Hardware assist modules at the master and slave side detect exactly when the sync frame was sent by the master and received by the slave. The slave then corrects its clock to match the master clock.  2017 Microchip Technology Inc. DS60001476B-page 965 SAMA5D2 SERIES Second, the transmission delay between the master and slave is corrected. The slave sends a delay request frame to the master which sends a delay response frame in reply. Hardware assist modules at the master and slave side detect exactly when the delay request frame was sent by the slave and received by the master. The slave will now have enough information to adjust its clock to account for delay. For example, if the slave was assuming zero delay, the actual delay will be half the difference between the transmit and receive time of the delay request frame (assuming equal transmit and receive times) because the slave clock will be lagging the master clock by the delay time already. The timestamp is taken when the message timestamp point passes the clock timestamp point. This can generate an interrupt if enabled (GMAC_IER). However, MAC Filtering configuration is needed to actually ‘copy’ the message to memory. For Ethernet, the message timestamp point is the SFD and the clock timestamp point is the MII interface. (The IEEE 1588 specification refers to sync and delay_req messages as event messages as these require timestamping. These events are captured in the registers GMAC_EFTx and GMAC_EFRx, respectively. Follow up, delay response and management messages do not require timestamping and are referred to as general messages.) 1588 version 2 defines two additional PTP event messages. These are the peer delay request (Pdelay_Req) and peer delay response (Pdelay_Resp) messages. These events are captured in the registers GMAC_PEFTx and GMAC_PEFRx, respectively. These messages are used to calculate the delay on a link. Nodes at both ends of a link send both types of frames (regardless of whether they contain a master or slave clock). The Pdelay_Resp message contains the time at which a Pdelay_Req was received and is itself an event message. The time at which a Pdelay_Resp message is received is returned in a Pdelay_Resp_Follow_Up message. 1588 version 2 introduces transparent clocks of which there are two kinds, peer-to-peer (P2P) and end-to-end (E2E). Transparent clocks measure the transit time of event messages through a bridge and amend a correction field within the message to allow for the transit time. P2P transparent clocks additionally correct for the delay in the receive path of the link using the information gathered from the peer delay frames. With P2P transparent clocks delay_req messages are not used to measure link delay. This simplifies the protocol and makes larger systems more stable. The GMAC recognizes four different encapsulations for PTP event messages: 1. 2. 3. 4. 1588 version 1 (UDP/IPv4 multicast) 1588 version 2 (UDP/IPv4 multicast) 1588 version 2 (UDP/IPv6 multicast) 1588 version 2 (Ethernet multicast) For 1588 version 1 messages, sync and delay request frames are indicated by the GMAC if the frame type field indicates TCP/IP, UDP protocol is indicated, the destination IP address is 224.0.1.129/130/131 or 132, the destination UDP port is 319 and the control field is correct. The control field is 0x00 for sync frames and 0x01 for delay request frames. Table 40-8: Example of Sync Frame in 1588 Version 1 Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 0800 IP stuff (Octets 14–22) — UDP (Octet 23) 11 IP stuff (Octets 24–29) — IP DA (Octets 30–32) E00001 IP DA (Octet 33) 81 or 82 or 83 or 84 Source IP port (Octets 34–35) — Dest IP port (Octets 36–37) 013F Other stuff (Octets 38–42) — Version PTP (Octet 43) 01 Other stuff (Octets 44–73) — DS60001476B-page 966  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-8: Example of Sync Frame in 1588 Version 1 Format (Continued) Frame Segment Value Control (Octet 74) 00 Other stuff (Octets 75–168) —  2017 Microchip Technology Inc. DS60001476B-page 967 SAMA5D2 SERIES Table 40-9: Example of Delay Request Frame in 1588 Version 1 Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 0800 IP stuff (Octets 14–22) — UDP (Octet 23) 11 IP stuff (Octets 24–29) — IP DA (Octets 30–32) E00001 IP DA (Octet 33) 81 or 82 or 83 or 84 Source IP port (Octets 34–35) — Dest IP port (Octets 36–37) 013F Other stuff (Octets 38–42) — Version PTP (Octet 43) 01 Other stuff (Octets 44–73) — Control (Octet 74) 01 Other stuff (Octets 75–168) — For 1588 version 2 messages, the type of frame is determined by looking at the message type field in the first byte of the PTP frame. Whether a frame is version 1 or version 2 can be determined by looking at the version PTP field in the second byte of both version 1 and version 2 PTP frames. In version 2 messages sync frames have a message type value of 0x0, delay_req have 0x1, Pdelay_Req have 0x2 and Pdelay_Resp have 0x3. Table 40-10: Example of Sync Frame in 1588 Version 2 (UDP/IPv4) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 0800 IP stuff (Octets 14–22) — UDP (Octet 23) 11 IP stuff (Octets 24–29) — IP DA (Octets 30–33) E0000181 Source IP port (Octets 34–35) — Dest IP port (Octets 36–37) 013F Other stuff (Octets 38–41) — Message type (Octet 42) 00 Version PTP (Octet 43) 02 DS60001476B-page 968  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-11: Example of Pdelay_Req Frame in 1588 Version 2 (UDP/IPv4) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 0800 IP stuff (Octets 14–22) — UDP (Octet 23) 11 IP stuff (Octets 24–29) — IP DA (Octets 30–33) E000006B Source IP port (Octets 34–35) — Dest IP port (Octets 36–37) 013F Other stuff (Octets 38–41) — Message type (Octet 42) 02 Version PTP (Octet 43) 02 Table 40-12: Example of Sync Frame in 1588 Version 2 (UDP/IPv6) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 86dd IP stuff (Octets 14–19) — UDP (Octet 20) 11 IP stuff (Octets 21–37) — IP DA (Octets 38–53) FF0X00000000018 Source IP port (Octets 54–55) — Dest IP port (Octets 56–57) 013F Other stuff (Octets 58–61) — Message type (Octet 62) 00 Other stuff (Octets 63–93) — Version PTP (Octet 94) 02  2017 Microchip Technology Inc. DS60001476B-page 969 SAMA5D2 SERIES Table 40-13: Example of Pdelay_Resp Frame in 1588 Version 2 (UDP/IPv6) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) — SA (Octets 6–11) — Type (Octets 12–13) 86dd IP stuff (Octets 14–19) — UDP (Octet 20) 11 IP stuff (Octets 21–37) — IP DA (Octets 38–53) FF0200000000006B Source IP port (Octets 54–55) — Dest IP port (Octets 56–57) 013F Other stuff (Octets 58–61) — Message type (Octet 62) 03 Other stuff (Octets 63–93) — Version PTP (Octet 94) 02 For the multicast address 011B19000000 sync and delay request frames are recognized depending on the message type field, 00 for sync and 01 for delay request. Table 40-14: Example of Sync Frame in 1588 Version 2 (Ethernet Multicast) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) 011B19000000 SA (Octets 6–11) — Type (Octets 12–13) 88F7 Message type (Octet 14) 00 Version PTP (Octet 15) 02 DS60001476B-page 970  2017 Microchip Technology Inc. SAMA5D2 SERIES Pdelay request frames need a special multicast address so they can pass through ports blocked by the spanning tree protocol. For the multicast address 0180C200000E sync, Pdelay_Req and Pdelay_Resp frames are recognized depending on the message type field, 00 for sync, 02 for pdelay request and 03 for pdelay response. Table 40-15: Example of Pdelay_Req Frame in 1588 Version 2 (Ethernet Multicast) Format Frame Segment Value Preamble/SFD 55555555555555D5 DA (Octets 0–5) 0180C200000E SA (Octets 6–11) — Type (Octets 12–13) 88F7 Message type (Octet 14) 00 Version PTP (Octet 15) 02 40.6.15 Timestamp Unit The TSU consists of a timer and registers to capture the time at which PTP event frames cross the message timestamp point. An interrupt is issued when a capture register is updated. The timer is implemented as a 94-bit register with the upper 48 bits counting seconds, the next 30 bits counting nanoseconds and the lowest 16 bits counting sub-nanoseconds. The lower 46 bits rolls over when they have counted to one second. An interrupt is generated when the seconds increment. The timer value can be read, written and adjusted through the APB interface. The timer is clocked by MCK. The amount by which the timer increments each clock cycle is controlled by the timer increment registers (GMAC_TI). Bits 7:0 are the default increment value in nanoseconds and an additional 16 bits of sub-nanosecond resolution are available using the Timer Increment Sub-nanoseconds register (GMAC_TISUBN). If the rest of the register is written with zero, the timer increments by the value in [7:0], plus the value of GMAC_TISUBN, each clock cycle. The GMAC_TISUBN register allows a resolution of approximately 15 femtoseconds. Bits 15:8 of the increment register are the alternative increment value in nanoseconds and bits 23:16 are the number of increments after which the alternative increment value is used. If 23:16 are zero then the alternative increment value will never be used. Taking the example of 10.2 MHz, there are 102 cycles every ten microseconds or 51 every five microseconds. So a timer with a 10.2 MHz clock source is constructed by incrementing by 98 ns for fifty cycles and then incrementing by 100 ns (98 × 50 + 100 = 5000). This is programmed by setting the 1588 Timer Increment register to 0x00326462. For a 49.8 MHz clock source it would be 20 ns for 248 cycles followed by an increment of 40 ns (20 × 248 + 40 = 5000) programmed as 0x00F82814. Having eight bits for the “number of increments” field allows frequencies up to 50 MHz to be supported with 200 kHz resolution. Without the alternative increment field the period of the clock would be limited to an integer number of nanoseconds, resulting in supported clock frequencies of 8, 10, 20, 25, 40, 50, 100, 125, 200 and 250 MHz. There are eight additional 80-bit registers that capture the time at which PTP event frames are transmitted and received. An interrupt is issued when these registers are updated. The TSU timer count value can be compared to a programmable comparison value. For the comparison, the 48 bits of the seconds value and the upper 22 bits of the nanoseconds value are used. A signal (GTSUCOMP) is provided to indicate when the TSU timer count value is equal to the comparison value stored in the TSU timer comparison value registers (0x0DC, 0x0E0, and 0x0E4). The GTSUCOMP signal can be routed to the Timer peripheral to automatically toggle pin TOIA11/PD21. This can be used as the reference clock for an external PLL to regenerate the audio clock in Ethernet AVB. An interrupt can also be generated (if enabled) when the TSU timer count value and comparison value are equal, mapped to bit 29 of the Interrupt Status register.  2017 Microchip Technology Inc. DS60001476B-page 971 SAMA5D2 SERIES 40.6.16 Note: MAC 802.3 Pause Frame Support See Clause 31, and Annex 31A and 31B of the IEEE standard 802.3 for a full description of MAC 802.3 pause operation. The following table shows the start of a MAC 802.3 pause frame. Table 40-16: Start of an 802.3 Pause Frame Address Destination Source Type (MAC Control Frame) 0x0180C2000001 6 bytes 0x8808 Pause Opcode Time 0x0001 2 bytes The GMAC supports both hardware controlled pause of the transmitter, upon reception of a pause frame, and hardware generated pause frame transmission. 40.6.16.1 802.3 Pause Frame Reception Bit 13 of the Network Configuration register is the pause enable control for reception. If this bit is set, transmission pauses if a non zero pause quantum frame is received. If a valid pause frame is received, then the Pause Time register is updated with the new frame's pause time, regardless of whether a previous pause frame is active or not. An interrupt (either bit 12 or bit 13 of the Interrupt Status register) is triggered when a pause frame is received, but only if the interrupt has been enabled (bit 12 and bit 13 of the Interrupt Mask register). Pause frames received with non zero quantum are indicated through the interrupt bit 12 of the Interrupt Status register. Pause frames received with zero quantum are indicated on bit 13 of the Interrupt Status register. Once the Pause Time register is loaded and the frame currently being transmitted has been sent, no new frames are transmitted until the pause time reaches zero. The loading of a new pause time, and hence the pausing of transmission, only occurs when the GMAC is configured for full duplex operation. If the GMAC is configured for half duplex there will be no transmission pause, but the pause frame received interrupt will still be triggered. A valid pause frame is defined as having a destination address that matches either the address stored in Specific Address 1 register or if it matches the reserved address of 0x0180C2000001. It must also have the MAC control frame type ID of 0x8808 and have the pause opcode of 0x0001. Pause frames that have frame check sequence (FCS) or other errors will be treated as invalid and will be discarded. 802.3 Pause frames that are received after Priority-based Flow Control (PFC) has been negotiated will also be discarded. Valid pause frames received will increment the Pause Frames Received statistic register. The Pause Time register decrements every 512 bit times once transmission has stopped. For test purposes, the retry test bit can be set (bit 12 in the Network Configuration register) which causes the Pause Time register to decrement every GTXCK cycle once transmission has stopped. The interrupt (bit 13 in the Interrupt Status register) is asserted whenever the Pause Time register decrements to zero (assuming it has been enabled by bit 13 in the Interrupt Mask register). This interrupt is also set when a zero quantum pause frame is received. 40.6.16.2 802.3 Pause Frame Transmission Automatic transmission of pause frames is supported through the transmit pause frame bits of the Network Control register. If either bit 11 or bit 12 of the Network Control register is written with logic 1, an 802.3 pause frame will be transmitted, providing full duplex is selected in the Network Configuration register and the transmit block is enabled in the Network Control register. Pause frame transmission will happen immediately if transmit is inactive or if transmit is active between the current frame and the next frame due to be transmitted. Transmitted pause frames comprise the following: • • • • • • • A destination address of 01-80-C2-00-00-01 A source address taken from Specific Address 1 register A type ID of 88-08 (MAC control frame) A pause opcode of 00-01 A Pause Quantum register Fill of 00 to take the frame to minimum frame length Valid FCS The pause quantum used in the generated frame will depend on the trigger source for the frame as follows: • If bit 11 is written with a one, the pause quantum will be taken from the Transmit Pause Quantum register. The Transmit Pause Quantum register resets to a value of 0xFFFF giving maximum pause quantum as default. DS60001476B-page 972  2017 Microchip Technology Inc. SAMA5D2 SERIES • If bit 12 is written with a one, the pause quantum will be zero. After transmission, a pause frame transmitted interrupt will be generated (bit 14 of the Interrupt Status register) and the only the statistics register Pause Frames Transmitted is incremented. Pause frames can also be transmitted by the MAC using normal frame transmission methods. 40.6.17 Note: MAC PFC Priority-based Pause Frame Support Refer to the 802.1Qbb standard for a full description of priority-based pause operation. The following table shows the start of a Priority-based Flow Control (PFC) pause frame. Table 40-17: Start of a PFC Pause Frame Address Destination Source Type (Mac Control Frame) Pause Opcode Priority Enable Vector Pause Time 0x0180C2000001 6 bytes 0x8808 0x1001 2 bytes 8 × 2 bytes The GMAC supports PFC priority-based pause transmission and reception. Before PFC pause frames can be received, bit 16 of the Network Control register must be set. 40.6.17.1 PFC Pause Frame Reception The ability to receive and decode priority-based pause frames is enabled by setting bit 16 of the Network Control register. When this bit is set, the GMAC will match either classic 802.3 pause frames or PFC priority-based pause frames. Once a priority-based pause frame has been received and matched, then from that moment on the GMAC will only match on priority-based pause frames (this is an 802.1Qbb requirement, known as PFC negotiation). Once priority-based pause has been negotiated, any received 802.3x format pause frames will not be acted upon. If a valid priority-based pause frame is received then the GMAC will decode the frame and determine which, if any, of the eight priorities require to be paused. Up to eight Pause Time registers are then updated with the eight pause times extracted from the frame regardless of whether a previous pause operation is active or not. An interrupt (either bit 12 or bit 13 of the Interrupt Status register) is triggered when a pause frame is received, but only if the interrupt has been enabled (bit 12 and bit 13 of the Interrupt Mask register). Pause frames received with non zero quantum are indicated through the interrupt bit 12 of the Interrupt Status register. Pause frames received with zero quantum are indicated on bit 13 of the Interrupt Status register. The loading of a new pause time only occurs when the GMAC is configured for full duplex operation. If the GMAC is configured for half duplex, the pause time counters will not be loaded, but the pause frame received interrupt will still be triggered. A valid pause frame is defined as having a destination address that matches either the address stored in Specific Address 1 register or if it matches the reserved address of 0x0180C2000001. It must also have the MAC control frame type ID of 0x8808 and have the pause opcode of 0x0101. Pause frames that have frame check sequence (FCS) or other errors will be treated as invalid and will be discarded. Valid pause frames received will increment the Pause Frames Received Statistic register. The Pause Time registers decrement every 512 bit times immediately following the PFC frame reception. For test purposes, the retry test bit can be set (bit 12 in the Network Configuration register) which causes the Pause Time register to decrement every GRXCK cycle once transmission has stopped. The interrupt (bit 13 in the Interrupt Status register) is asserted whenever the Pause Time register decrements to zero (assuming it has been enabled by bit 13 in the Interrupt Mask register). This interrupt is also set when a zero quantum pause frame is received. 40.6.17.2 PFC Pause Frame Transmission Automatic transmission of pause frames is supported through the transmit priority-based pause frame bit of the Network Control register. If bit 17 of the Network Control register is written with logic 1, a PFC pause frame will be transmitted providing full duplex is selected in the Network Configuration register and the transmit block is enabled in the Network Control register. When bit 17 of the Network Control register is set, the fields of the priority-based pause frame will be built using the values stored in the Transmit PFC Pause register. Pause frame transmission will happen immediately if transmit is inactive or if transmit is active between the current frame and the next frame due to be transmitted. Transmitted pause frames comprise the following: • • • • A destination address of 01-80-C2-00-00-01 A source address taken from Specific Address 1 register A type ID of 88-08 (MAC control frame) A pause opcode of 01-01  2017 Microchip Technology Inc. DS60001476B-page 973 SAMA5D2 SERIES • • • • A priority enable vector taken from Transmit PFC Pause register 8 Pause Quantum registers Fill of 00 to take the frame to minimum frame length Valid FCS The Pause Quantum registers used in the generated frame will depend on the trigger source for the frame as follows: • If bit 17 of the Network Control register is written with a one, then the priority enable vector of the priority-based pause frame will be set equal to the value stored in the Transmit PFC Pause register [7:0]. For each entry equal to zero in the Transmit PFC Pause register [15:8], the pause quantum field of the pause frame associated with that entry will be taken from the Transmit Pause Quantum register. For each entry equal to one in the Transmit PFC Pause register [15:8], the pause quantum associated with that entry will be zero. • The Transmit Pause Quantum register resets to a value of 0xFFFF giving maximum pause quantum as default. After transmission, a pause frame transmitted interrupt will be generated (bit 14 of the Interrupt Status register) and the only statistics register that will be incremented will be the Pause Frames Transmitted register. PFC Pause frames can also be transmitted by the MAC using normal frame transmission methods. DS60001476B-page 974  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.6.18 Energy-efficient Ethernet Support IEEE 802.3az adds support for energy efficiency to Ethernet. These are the key features of 802.3az: • Allows a system’s transmit path to enter a low power mode if there is nothing to transmit. • Allows a PHY to detect whether its link partner’s transmit path is in low power mode, therefore allowing the system’s receive path to enter low power mode. • Link remains up during lower power mode and no frames are dropped. • Asymmetric, one direction can be in low power mode while the other is transmitting normally. • LPI (Low Power Idle) signaling is used to control entry and exit to and from low power modes. • LPI signaling can only take place if both sides have indicated support for it through auto-negotiation. These are the key features of 802.3az operation: • Low power control is done at the MII (reconciliation sublayer). • As an architectural convenience in writing the 802.3az it is assumed that transmission is deferred by asserting carrier sense, in practice it will not be done this way. This system will know when it has nothing to transmit and only enter low power mode when it is not transmitting. • LPI should not be requested unless the link has been up for at least one second. • LPI is signaled on the transmit path by asserting 0x01 on txd with tx_en low and tx_er high. • A PHY on seeing LPI requested on the MII will send the sleep signal before going quiet. After going quiet it will periodically transmit refresh signals. • LPI mode ends by transmitting normal idle for the wake time. There is a default time for this but it can be adjusted in software using the Link Layer Discovery Protocol (LLDP) described in Clause 79 of 802.3az. • LPI is indicated at the receive side when sleep and refresh signaling has been detected. 40.6.19 802.1Qav Support - Credit-based Shaping A credit-based shaping algorithm is available on the two highest priority queues and is defined in the standard 802.1Qav: Forwarding and Queuing Enhancements for Time-Sensitive Streams. This allows traffic on these queues to be limited and to allow other queues to transmit. Traffic shaping is enabled via the CBS (Credit Based Shaping) Control register. This enables a counter which stores the amount of transmit 'credit', measured in bytes that a particular queue has. A queue may only transmit if it has non-negative credit. If a queue has data to send, but is held off from doing as another queue is transmitting, then credit will accumulate in the credit counter at the rate defined in the IdleSlope register (GMAC_CBSISQx) for that queue. portTransmitRate is the transmission rate, in bits per second, that the underlying MAC service that supports transmission through the Port provides. The value of this parameter is determined by the operation of the MAC. IdleSlope is the rate of change of increasing credit when waiting to transmit and must be less than the value of the portTransmitRate. The max value of IdleSlope (or sendSlope) is (portTransmitRate / bits_per_MII_Clock). In case of 100Mbps, maximum IdleSlope = (100Mbps / 4) = 0x17D7840. When this queue is transmitting, the credit counter is decremented at the rate of sendSlope, which is defined as (portTransmitRate IdleSlope). A queue can accumulate negative credit when transmitting which will hold off any other transfers from that queue until credit returns to a non-negative value. No transfers are halted when a queue's credit becomes negative; it will accumulate negative credit until the transfer completes. The highest priority queue always has priority regardless of which queue has the most credit. 40.6.20 LPI Operation in the GMAC It is best to use firmware to control LPI. LPI operation happens at the system level. Firmware gives maximum control and flexibility of operation. LPI operation is straightforward and firmware should be capable of responding within the required timeframes. Autonegotiation: 1. Indicate EEE capability using next page autonegotiation. For the transmit path: 1. 2. If the link has been up for 1 second and there is nothing being transmitted, write to the TXLPIEN bit in the Network Control register. Wake up by clearing the TXLPIEN bit in the Network Control register. For the receive path: 1. 2. Enable RXLPISBC bit in GMAC_IER. The bit RXLPIS is set in Network Status Register triggering an interrupt. Wait for an interrupt to indicate that LPI has been received.  2017 Microchip Technology Inc. DS60001476B-page 975 SAMA5D2 SERIES 3. 4. 5. Disable relevant parts of the receive path if desired. The RXLPIS bit in Network Status Register gets cleared to indicate that regular idle has been received. This triggers an interrupt. Re-enable the receive path. 40.6.21 PHY Interface Different PHY interfaces are supported by the Ethernet MAC: • MII • RMII The MII interface is provided for 10/100 operation and uses txd[3:0] and rxd[3:0]. The RMII interface is provided for 10/100 operation and uses txd[1:0] and rxd[1:0]. 40.6.22 10/100 Operation The 10/100Mbps speed bit in the Network Configuration register is used to select between 10Mbps and 100Mbps. 40.6.23 Jumbo Frames The jumbo frames enable bit in the Network Configuration register allows the GMAC, in its default configuration, to receive jumbo frames up to 10240 bytes in size. This operation does not form part of the IEEE 802.3 specification and is normally disabled. When jumbo frames are enabled, frames received with a frame size greater than 10240 bytes are discarded. DS60001476B-page 976  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.7 40.7.1 40.7.1.1 Programming Interface Initialization Configuration Initialization of the GMAC configuration (e.g., loop back mode, 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 earlier in this document. To change loop back mode, the following sequence of operations must be followed: 1. 2. 3. Write to Network Control register to disable transmit and receive circuits. Write to Network Control register to change loop back mode. Write to Network Control register to re-enable transmit or receive circuits. Note: 40.7.1.2 These writes to the Network Control register cannot be combined in any way. 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 Table 40-4 “Receive Buffer Descriptor Entry”. The Receive Buffer Queue Pointer register points to this data structure. Figure 40-3: 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. 2. 3. 4. 5. Allocate a number (N) of buffers of X bytes in system memory, where X is the DMA buffer length programmed in the DMA Configuration register. Allocate an area 8N bytes for the receive buffer descriptor list in system memory and create N entries in this list. Mark all entries in this list as owned by GMAC, i.e., bit 0 of word 0 set to 0. Mark the last descriptor in the queue with the wrap bit (bit 1 in word 0 set to 1). Write address of receive buffer descriptor list and control information to GMAC register receive buffer queue pointer The receive circuits can then be enabled by writing to the address recognition registers and the Network Control register. Note: 40.7.1.3 The queue pointers must be initialized and point to USED descriptors for all queues including those not intended for use. Transmit Buffer List Transmit data is read from areas of data (the buffers) in 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 40-5 “Transmit Buffer Descriptor Entry”. The Transmit Buffer Queue Pointer register points to this data structure. To create this list of buffers:  2017 Microchip Technology Inc. DS60001476B-page 977 SAMA5D2 SERIES 1. 2. 3. 4. 5. 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. Allocate an area 8N bytes for the transmit buffer descriptor list in system memory and create N entries in this list. Mark all entries in this list as owned by GMAC, i.e., bit 31 of word 1 set to 0. Mark the last descriptor in the queue with the wrap bit (bit 30 in word 1 set to 1). Write address of transmit buffer descriptor list and control information to GMAC register transmit buffer queue pointer. The transmit circuits can then be enabled by writing to the Network Control register. Note: 40.7.1.4 The queue pointers must be initialized and point to USED descriptors for all queues including those not intended for use. Address Matching The GMAC Hash register pair and the four Specific Address register pairs must be written with the required values. Each register pair comprises of 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. Each register pair may be written at any time, regardless of whether the receive circuits are enabled or disabled. As an example, to set Specific Address 1 register to recognize destination address 21:43:65:87:A9:CB, the following values are written to Specific Address 1 Bottom register and Specific Address 1 Top register: • Specific Address 1 Bottom register bits 31:0 (0x98): 0x8765_4321. • Specific Address 1 Top register bits 31:0 (0x9C): 0x0000_CBA9. Note: 40.7.1.5 The address matching is the first level of filtering. If there is a match, the screeners are the next level of filtering for routing the data to the appropriate queue. See Section 40.6.3.9 ”Priority Queueing in the DMA” for more details. PHY Maintenance 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 bits 18:16 are set to 010 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 Management Data Clock (MDC) cycle. This causes the transmission of a PHY management frame on MDIO. See section 22.2.4.5 of the IEEE 802.3 standard. Reading during the shift operation will return the current contents of the shift register. At the end of the management operation the bits will 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 Management Data Clock (MDC) should not toggle faster than 2.5 MHz (minimum period of 400 ns), as defined by the IEEE 802.3 standard. MDC is generated by dividing down MCK. Three bits in the Network Configuration register determine by how much MCK should be divided to produce MDC. 40.7.1.6 Interrupts There are 18 interrupt conditions that are detected within the GMAC. The conditions are ORed to make multiple interrupts. Depending on the overall system design this may be passed through a further level of interrupt collection (interrupt controller). On receipt of the interrupt signal, the CPU enters the interrupt handler. Refer to the device interrupt controller documentation to identify that it is the GMAC that is generating the interrupt. To ascertain which interrupt, read the Interrupt Status register. Note that in the default configuration this register will clear itself after being read, though this may be configured to be write-one-to-clear if desired. 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. 40.7.1.7 Transmitting Frames The procedure to set up a frame for transmission is the following: 1. 2. 3. 4. 5. 6. Enable transmit in the Network Control register. Allocate an area of system memory for transmit data. This does not have to be contiguous, varying byte lengths can be used if they conclude on byte borders. Set-up the transmit buffer list by writing buffer addresses to word zero of the transmit buffer descriptor entries and control and length to word one. Write data for transmission into the buffers pointed to by the descriptors. Write the address of the first buffer descriptor to transmit buffer descriptor queue pointer. Enable appropriate interrupts. DS60001476B-page 978  2017 Microchip Technology Inc. SAMA5D2 SERIES 7. Write to the transmit start bit (TSTART) in the Network Control register. 40.7.1.8 Receiving Frames When a frame is received and the receive circuits are enabled, the GMAC 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 one of the four Type ID registers. If it matches the hash address function. If it is a broadcast address (0xFFFFFFFFFFFF) and broadcasts are allowed. If the GMAC is configured to “copy all frames”. The register receive buffer queue pointer points to the next entry in the receive buffer descriptor list and the GMAC 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 GMAC then updates the receive buffer descriptor entry (see Table 40-4 “Receive Buffer Descriptor Entry”) with the reason for the address match and marks the area as being owned by software. Once this is complete, a receive complete interrupt is set. Software is then responsible for copying the data to the application area and releasing the buffer (by writing the ownership bit back to 0). If the GMAC is unable to write the data at a rate to match the incoming frame, then a receive overrun interrupt is set. If there is no receive buffer available, i.e., the next buffer is still owned by software, a receive buffer not available interrupt is set. If the frame is not successfully received, a statistics register is incremented and the frame is discarded without informing software.  2017 Microchip Technology Inc. DS60001476B-page 979 SAMA5D2 SERIES 40.7.2 Statistics Registers Statistics registers are described in the User Interface beginning with Section 40.8.47 ”GMAC Octets Transmitted Low Register” and ending with Section 40.8.91 ”GMAC UDP Checksum Errors Register”. The statistics register block begins at 0x100 and runs to 0x1B0, and comprises the registers listed below. Octets Transmitted Low Register Broadcast Frames Received Register Octets Transmitted High Register Multicast Frames Received Register Frames Transmitted Register Pause Frames Received Register Broadcast Frames Transmitted Register 64 Byte Frames Received Register Multicast Frames Transmitted Register 65 to 127 Byte Frames Received Register Pause Frames Transmitted Register 128 to 255 Byte Frames Received Register 64 Byte Frames Transmitted Register 256 to 511 Byte Frames Received Register 65 to 127 Byte Frames Transmitted Register 512 to 1023 Byte Frames Received Register 128 to 255 Byte Frames Transmitted Register 1024 to 1518 Byte Frames Received Register 256 to 511 Byte Frames Transmitted Register 1519 to Maximum Byte Frames Received Register 512 to 1023 Byte Frames Transmitted Register Undersize Frames Received Register 1024 to 1518 Byte Frames Transmitted Register Oversize Frames Received Register Greater Than 1518 Byte Frames Transmitted Register Jabbers Received Register Transmit Underruns Register Frame Check Sequence Errors Register Single Collision Frames Register Length Field Frame Errors Register Multiple Collision Frames Register Receive Symbol Errors Register Excessive Collisions Register Alignment Errors Register Late Collisions Register Receive Resource Errors Register Deferred Transmission Frames Register Receive Overrun Register Carrier Sense Errors Register IP Header Checksum Errors Register Octets Received Low Register TCP Checksum Errors Register Octets Received High Register UDP Checksum Errors Register Frames Received Register 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 (RXEN) is set in the Network Control register. Once a statistics register has been read, it is automatically cleared. When reading the Octets Transmitted and Octets Received registers, bits 31:0 should be read prior to bits 47:32 to ensure reliable operation. DS60001476B-page 980  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8 Ethernet MAC (GMAC) User Interface Table 40-18: Offset (1) (2) Register Mapping Register Name Access Reset 0x000 Network Control Register GMAC_NCR Read/Write 0x0000_0000 0x004 Network Configuration Register GMAC_NCFGR Read/Write 0x0008_0000 0x008 Network Status Register GMAC_NSR Read-only 0b01x0 0x00C User Register GMAC_UR Read/Write 0x0000_0000 0x010 DMA Configuration Register GMAC_DCFGR Read/Write 0x0002_0004 0x014 Transmit Status Register GMAC_TSR Read/Write 0x0000_0000 0x018 Receive Buffer Queue Base Address Register GMAC_RBQB Read/Write 0x0000_0000 0x01C Transmit Buffer Queue Base Address Register GMAC_TBQB Read/Write 0x0000_0000 0x020 Receive Status Register GMAC_RSR Read/Write 0x0000_0000 0x024 Interrupt Status Register GMAC_ISR Read-only 0x0000_0000 0x028 Interrupt Enable Register GMAC_IER Write-only – 0x02C Interrupt Disable Register GMAC_IDR Write-only – 0x030 Interrupt Mask Register GMAC_IMR Read/Write 0x07FF_FFFF 0x034 PHY Maintenance Register GMAC_MAN Read/Write 0x0000_0000 0x038 Received Pause Quantum Register GMAC_RPQ Read-only 0x0000_0000 0x03C Transmit Pause Quantum Register GMAC_TPQ Read/Write 0x0000_FFFF 0x040 TX Partial Store and Forward Register GMAC_TPSF Read/Write 0x0000_0FFF 0x044 RX Partial Store and Forward Register GMAC_RPSF Read/Write 0x0000_0FFF 0x048 RX Jumbo Frame Max Length Register GMAC_RJFML Read/Write 0x0000_3FFF 0x4C–0x07C Reserved – – – 0x080 Hash Register Bottom GMAC_HRB Read/Write 0x0000_0000 0x084 Hash Register Top GMAC_HRT Read/Write 0x0000_0000 0x088 Specific Address 1 Bottom Register GMAC_SAB1 Read/Write 0x0000_0000 0x08C Specific Address 1 Top Register GMAC_SAT1 Read/Write 0x0000_0000 0x090 Specific Address 2 Bottom Register GMAC_SAB2 Read/Write 0x0000_0000 0x094 Specific Address 2 Top Register GMAC_SAT2 Read/Write 0x0000_0000 0x098 Specific Address 3 Bottom Register GMAC_SAB3 Read/Write 0x0000_0000 0x09C Specific Address 3 Top Register GMAC_SAT3 Read/Write 0x0000_0000 0x0A0 Specific Address 4 Bottom Register GMAC_SAB4 Read/Write 0x0000_0000 0x0A4 Specific Address 4 Top Register GMAC_SAT4 Read/Write 0x0000_0000 0x0A8 Type ID Match 1 Register GMAC_TIDM1 Read/Write 0x0000_0000 0x0AC Type ID Match 2 Register GMAC_TIDM2 Read/Write 0x0000_0000 0x0B0 Type ID Match 3 Register GMAC_TIDM3 Read/Write 0x0000_0000 0x0B4 Type ID Match 4 Register GMAC_TIDM4 Read/Write 0x0000_0000  2017 Microchip Technology Inc. DS60001476B-page 981 SAMA5D2 SERIES Table 40-18: Register Mapping (Continued) Offset(1) (2) Register Name 0x0B8 Wake on LAN Register 0x0BC Access Reset GMAC_WOL Read/Write 0x0000_0000 IPG Stretch Register GMAC_IPGS Read/Write 0x0000_0000 0x0C0 Stacked VLAN Register GMAC_SVLAN Read/Write 0x0000_0000 0x0C4 Transmit PFC Pause Register GMAC_TPFCP Read/Write 0x0000_0000 0x0C8 Specific Address 1 Mask Bottom Register GMAC_SAMB1 Read/Write 0x0000_0000 0x0CC Specific Address 1 Mask Top Register GMAC_SAMT1 Read/Write 0x0000_0000 0x0D0–0x0D8 Reserved – – – 0x0DC 1588 Timer Nanosecond Comparison Register GMAC_NSC Read/Write 0x0000_0000 0x0E0 1588 Timer Second Comparison Low Register GMAC_SCL Read/Write 0x0000_0000 0x0E4 1588 Timer Second Comparison High Register GMAC_SCH Read/Write 0x0000_0000 0x0E8 PTP Event Frame Transmitted Seconds High Register GMAC_EFTSH Read-only 0x0000_0000 0x0EC PTP Event Frame Received Seconds High Register GMAC_EFRSH Read-only 0x0000_0000 0x0F0 PTP Peer Event Frame Transmitted Seconds High Register GMAC_PEFTSH Read-only 0x0000_0000 0x0F4 PTP Peer Event Frame Received Seconds High Register GMAC_PEFRSH Read-only 0x0000_0000 0x0F8–0x0FC Reserved – – – 0x100 Octets Transmitted Low Register GMAC_OTLO Read-only 0x0000_0000 0x104 Octets Transmitted High Register GMAC_OTHI Read-only 0x0000_0000 0x108 Frames Transmitted Register GMAC_FT Read-only 0x0000_0000 0x10C Broadcast Frames Transmitted Register GMAC_BCFT Read-only 0x0000_0000 0x110 Multicast Frames Transmitted Register GMAC_MFT Read-only 0x0000_0000 0x114 Pause Frames Transmitted Register GMAC_PFT Read-only 0x0000_0000 0x118 64 Byte Frames Transmitted Register GMAC_BFT64 Read-only 0x0000_0000 0x11C 65 to 127 Byte Frames Transmitted Register GMAC_TBFT127 Read-only 0x0000_0000 0x120 128 to 255 Byte Frames Transmitted Register GMAC_TBFT255 Read-only 0x0000_0000 0x124 256 to 511 Byte Frames Transmitted Register GMAC_TBFT511 Read-only 0x0000_0000 0x128 512 to 1023 Byte Frames Transmitted Register GMAC_TBFT1023 Read-only 0x0000_0000 0x12C 1024 to 1518 Byte Frames Transmitted Register GMAC_TBFT1518 Read-only 0x0000_0000 0x130 Greater Than 1518 Byte Frames Transmitted Register GMAC_GTBFT1518 Read-only 0x0000_0000 0x134 Transmit Underruns Register GMAC_TUR Read-only 0x0000_0000 0x138 Single Collision Frames Register GMAC_SCF Read-only 0x0000_0000 0x13C Multiple Collision Frames Register GMAC_MCF Read-only 0x0000_0000 0x140 Excessive Collisions Register GMAC_EC Read-only 0x0000_0000 0x144 Late Collisions Register GMAC_LC Read-only 0x0000_0000 0x148 Deferred Transmission Frames Register GMAC_DTF Read-only 0x0000_0000 DS60001476B-page 982  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 40-18: Register Mapping (Continued) Offset(1) (2) Register Name 0x14C Carrier Sense Errors Register 0x150 Access Reset GMAC_CSE Read-only 0x0000_0000 Octets Received Low Received Register GMAC_ORLO Read-only 0x0000_0000 0x154 Octets Received High Received Register GMAC_ORHI Read-only 0x0000_0000 0x158 Frames Received Register GMAC_FR Read-only 0x0000_0000 0x15C Broadcast Frames Received Register GMAC_BCFR Read-only 0x0000_0000 0x160 Multicast Frames Received Register GMAC_MFR Read-only 0x0000_0000 0x164 Pause Frames Received Register GMAC_PFR Read-only 0x0000_0000 0x168 64 Byte Frames Received Register GMAC_BFR64 Read-only 0x0000_0000 0x16C 65 to 127 Byte Frames Received Register GMAC_TBFR127 Read-only 0x0000_0000 0x170 128 to 255 Byte Frames Received Register GMAC_TBFR255 Read-only 0x0000_0000 0x174 256 to 511 Byte Frames Received Register GMAC_TBFR511 Read-only 0x0000_0000 0x178 512 to 1023 Byte Frames Received Register GMAC_TBFR1023 Read-only 0x0000_0000 0x17C 1024 to 1518 Byte Frames Received Register GMAC_TBFR1518 Read-only 0x0000_0000 0x180 1519 to Maximum Byte Frames Received Register GMAC_TMXBFR Read-only 0x0000_0000 0x184 Undersize Frames Received Register GMAC_UFR Read-only 0x0000_0000 0x188 Oversize Frames Received Register GMAC_OFR Read-only 0x0000_0000 0x18C Jabbers Received Register GMAC_JR Read-only 0x0000_0000 0x190 Frame Check Sequence Errors Register GMAC_FCSE Read-only 0x0000_0000 0x194 Length Field Frame Errors Register GMAC_LFFE Read-only 0x0000_0000 0x198 Receive Symbol Errors Register GMAC_RSE Read-only 0x0000_0000 0x19C Alignment Errors Register GMAC_AE Read-only 0x0000_0000 0x1A0 Receive Resource Errors Register GMAC_RRE Read-only 0x0000_0000 0x1A4 Receive Overrun Register GMAC_ROE Read-only 0x0000_0000 0x1A8 IP Header Checksum Errors Register GMAC_IHCE Read-only 0x0000_0000 0x1AC TCP Checksum Errors Register GMAC_TCE Read-only 0x0000_0000 0x1B0 UDP Checksum Errors Register GMAC_UCE Read-only 0x0000_0000 0x1B4–0x1B8 Reserved – – – 0x1BC 1588 Timer Increment Sub-nanoseconds Register GMAC_TISUBN Read/Write 0x0000_0000 0x1C0 1588 Timer Seconds High Register GMAC_TSH Read/Write 0x0000_0000 0x1C4–0x1CC Reserved – – – 0x1D0 1588 Timer Seconds Low Register GMAC_TSL Read/Write 0x0000_0000 0x1D4 1588 Timer Nanoseconds Register GMAC_TN Read/Write 0x0000_0000 0x1D8 1588 Timer Adjust Register GMAC_TA Write-only – 0x1DC 1588 Timer Increment Register GMAC_TI Read/Write 0x0000_0000 0x1E0 PTP Event Frame Transmitted Seconds Low Register GMAC_EFTSL Read-only 0x0000_0000  2017 Microchip Technology Inc. DS60001476B-page 983 SAMA5D2 SERIES Table 40-18: Register Mapping (Continued) Offset(1) (2) Register Name 0x1E4 PTP Event Frame Transmitted Nanoseconds Register 0x1E8 PTP Event Frame Received Seconds Low Register 0x1EC Access Reset GMAC_EFTN Read-only 0x0000_0000 GMAC_EFRSL Read-only 0x0000_0000 PTP Event Frame Received Nanoseconds Register GMAC_EFRN Read-only 0x0000_0000 0x1F0 PTP Peer Event Frame Transmitted Seconds Low Register GMAC_PEFTSL Read-only 0x0000_0000 0x1F4 PTP Peer Event Frame Transmitted Nanoseconds Register GMAC_PEFTN Read-only 0x0000_0000 0x1F8 PTP Peer Event Frame Received Seconds Low Register GMAC_PEFRSL Read-only 0x0000_0000 0x1FC PTP Peer Event Frame Received Nanoseconds Register GMAC_PEFRN Read-only 0x0000_0000 0x200–0x26C Reserved – – – 0x270 Received LPI Transitions GMAC_RXLPI Read-only 0x0000_0000 0x274 Received LPI Time GMAC_RXLPITIME Read-only 0x0000_0000 0x278 Transmit LPI Transitions GMAC_TXLPI Read-only 0x0000_0000 0x27C Transmit LPI Time GMAC_TXLPITIME Read-only 0x0000_0000 0x280–0x3FC Reserved – – GMAC_ISRPQ Read-only 0x0000_0000 – (3) 0x3FC + (index * 0x04) Interrupt Status Register Priority Queue 0x43C + (index * 0x04) Transmit Buffer Queue Base Address Register Priority Queue (3) GMAC_TBQBAPQ Read/Write 0x0000_0000 0x47C + (index * 0x04) Receive Buffer Queue Base Address Register Priority Queue (3) GMAC_RBQBAPQ Read/Write 0x0000_0000 0x49C + (index * 0x04) Receive Buffer Size Register Priority Queue (3) GMAC_RBSRPQ Read/Write 0x0000_0002 0x4BC Credit-Based Shaping Control Register GMAC_CBSCR Read/Write 0x0000_0000 0x4C0 Credit-Based Shaping IdleSlope Register for Queue A GMAC_CBSISQA Read/Write 0x0000_0000 0x4C4 Credit-Based Shaping IdleSlope Register for Queue B GMAC_CBSISQB Read/Write 0x0000_0000 0x500 + (index * 0x04) Screening Type 1 Register Priority Queue (4) GMAC_ST1RPQ Read/Write 0x0000_0000 0x540 + (index * 0x04) (5) GMAC_ST2RPQ Read/Write 0x0000_0000 Interrupt Enable Register Priority Queue (3) GMAC_IERPQ Write-only – 0x61C + (index * 0x04) Interrupt Disable Register Priority Queue (3) GMAC_IDRPQ Write-only – 0x63C + (index * 0x04) Interrupt Mask Register Priority Queue (3) GMAC_IMRPQ Read/Write 0x0000_0000 0x6E0 + (index * 0x04) Screening Type 2 Ethertype Register (6) 0x5FC + (index * 0x04) 0x700 + (index * 0x08) 0x704 + (index * 0x08) Screening Type 2 Register Priority Queue GMAC_ST2ER Read/Write 0x0000_0000 Screening Type 2 Compare Word 0 Register (7) GMAC_ST2CW0 Read/Write 0x0000_0000 Screening Type 2 Compare Word 1 Register (7) GMAC_ST2CW1 Read/Write 0x0000_0000 Note 1: If an offset is not listed in the Register Mapping, it must be considered as ‘reserved’. 2: Some register groups are not continuous in memory. DS60001476B-page 984  2017 Microchip Technology Inc. SAMA5D2 SERIES 3: The index range for the following registers is from 1 to 2: - GMAC_ISRPQ - GMAC_TBQBAPQ - GMAC_RBQBAPQ - GMAC_RBSRPQ - GMAC_IERPQ (cont’d.) - GMAC_IDRPQ - GMAC_IMRPQ 4: The index for GMAC_ST1RPQ registers ranges from 0 to 3. 5: The index for GMAC_ST2RPQ registers ranges from 0 to 7. 6: The index for GMAC_ST2ER registers ranges from 0 to 3. 7: The index for GMAC_ST2CW0 and GMAC_ST2CW1 registers ranges from 0 to 23.  2017 Microchip Technology Inc. DS60001476B-page 985 SAMA5D2 SERIES 40.8.1 GMAC Network Control Register Name: GMAC_NCR Address: 0xF8008000 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 TXLPIEN 18 FNP 17 TXPBPF 16 ENPBPR 15 SRTSM 14 – 13 – 12 TXZQPF 11 TXPF 10 THALT 9 TSTART 8 BP 7 WESTAT 6 INCSTAT 5 CLRSTAT 4 MPE 3 TXEN 2 RXEN 1 LBL 0 – LBL: Loop Back Local Connects GTX to GRX, GTXEN to GRXDV and forces full duplex mode. GRXCK and GTXCK may malfunction as the GMAC 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. RXEN: Receive Enable When set, RXEN enables the GMAC to receive data. When reset frame reception stops immediately and the receive pipeline will be cleared. The Receive Queue Pointer Register is unaffected. TXEN: Transmit Enable When set, TXEN enables the GMAC transmitter to send data. When reset transmission will stop immediately, the transmit pipeline and control registers will be cleared and the Transmit Queue Pointer Register will reset 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 10M or 100M half duplex mode, forces collisions on all received frames. 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. TXPF: Transmit Pause Frame Writing one to this bit causes a pause frame to be transmitted. TXZQPF: Transmit Zero Quantum Pause Frame Writing one to this bit causes a pause frame with zero quantum to be transmitted. DS60001476B-page 986  2017 Microchip Technology Inc. SAMA5D2 SERIES SRTSM: Store Receive Timestamp to Memory 0: Normal operation. 1: Causes the CRC of every received frame to be replaced with the value of the nanoseconds field of the 1588 timer that was captured as the receive frame passed the message timestamp point. Note that bit RFCS in register GMAC_NCFGR may not be set to 1 when the timer should be captured. ENPBPR: Enable PFC Priority-based Pause Reception Enables PFC Priority Based Pause Reception capabilities. Setting this bit enables PFC negotiation and recognition of priority-based pause frames. TXPBPF: Transmit PFC Priority-based Pause Frame Takes the values stored in the Transmit PFC Pause Register. FNP: Flush Next Packet Flush the next packet from the external RX DPRAM. Writing one to this bit will only have an effect if the DMA is not currently writing a packet already stored in the DPRAM to memory. TXLPIEN: Enable LPI Transmission When set, LPI (low power idle) is immediately transmitted.  2017 Microchip Technology Inc. DS60001476B-page 987 SAMA5D2 SERIES 40.8.2 GMAC Network Configuration Register Name: GMAC_NCFGR Address: 0xF8008004 Access: Read/Write 31 – 30 IRXER 29 RXBP 28 IPGSEN 27 – 26 IRXFCS 25 EFRHD 24 RXCOEN 23 DCPF 22 21 20 19 CLK 18 17 RFCS 16 LFERD 15 14 13 PEN 12 RTY 11 – 10 – 9 – 8 MAXFS 6 MTI HEN 5 NBC 4 CAF 3 JFRAME 2 DNVLAN 1 FD 0 SPD DBW RXBUFO 7 UNIHEN SPD: Speed Set to logic one to indicate 100 Mbps operation, logic zero for 10 Mbps. FD: Full Duplex If set to logic one, the transmit block ignores the state of collision and carrier sense and allows receive while transmitting. DNVLAN: Discard Non-VLAN FRAMES When set only VLAN tagged frames will be passed to the address matching logic. JFRAME: Jumbo Frame Size Set to one to enable jumbo frames up to 10240 bytes to be accepted. The default length is 10240 bytes. CAF: Copy All Frames When set to logic one, all valid frames will be accepted. NBC: No Broadcast When set to logic one, frames addressed to the broadcast address of all ones will not be accepted. MTIHEN: Multicast Hash Enable When set, multicast frames will be accepted when the 6-bit hash function of the destination address points to a bit that is set in the Hash Register. UNIHEN: Unicast Hash Enable When set, unicast frames will be accepted when the 6-bit hash function of the destination address points to a bit that is set in the Hash Register. MAXFS: 1536 Maximum Frame Size Setting this bit means the GMAC will accept frames up to 1536 bytes in length. Normally the GMAC would reject any frame above 1518 bytes. DS60001476B-page 988  2017 Microchip Technology Inc. SAMA5D2 SERIES RTY: Retry Test Must be set to zero for normal operation. If set to one the backoff between collisions will always be one slot time. Setting this bit to one helps test the too many retries condition. Also used in the pause frame tests to reduce the pause counter's decrement time from 512 bit times, to every GRXCK cycle. PEN: Pause Enable When set, transmission will pause if a non-zero 802.3 classic pause frame is received and PFC has not been negotiated. RXBUFO: Receive Buffer Offset Indicates the number of bytes by which the received data is offset from the start of the receive buffer LFERD: Length Field Error Frame Discard Setting this bit causes frames with a measured length shorter than the extracted length field (as indicated by bytes 13 and 14 in a nonVLAN tagged frame) to be discarded. This only applies to frames with a length field less than 0x0600. RFCS: Remove FCS Setting this bit will cause received frames to be written to memory without their frame check sequence (last 4 bytes). The frame length indicated will be reduced by four bytes in this mode. CLK: MDC CLock Division Set according to MCK speed. These three bits determine the number MCK will be divided by to generate Management Data Clock (MDC). For conformance with the 802.3 specification, MDC must not exceed 2.5 MHz (MDC is only active during MDIO read and write operations). Value Name Description 0 MCK_8 MCK divided by 8 (MCK up to 20 MHz) 1 MCK_16 MCK divided by 16 (MCK up to 40 MHz) 2 MCK_32 MCK divided by 32 (MCK up to 80 MHz) 3 MCK_48 MCK divided by 48 (MCK up to 120 MHz) 4 MCK_64 MCK divided by 64 (MCK up to 160 MHz) 5 MCK_96 MCK divided by 96 (MCK up to 240 MHz) DBW: Data Bus Width Should always be written to ‘0’. DCPF: Disable Copy of Pause Frames Set to one to prevent valid pause frames being copied to memory. When set, pause frames are not copied to memory regardless of the state of the Copy All Frames bit, whether a hash match is found or whether a type ID match is identified. If a destination address match is found, the pause frame will be copied to memory. Note that valid pause frames received will still increment pause statistics and pause the transmission of frames as required. RXCOEN: Receive Checksum Offload Enable When set, the receive checksum engine is enabled. Frames with bad IP, TCP or UDP checksums are discarded. EFRHD: Enable Frames Received in Half Duplex Enable frames to be received in half-duplex mode while transmitting. IRXFCS: Ignore RX FCS When set, frames with FCS/CRC errors will not be rejected. FCS error statistics will still be collected for frames with bad FCS and FCS status will be recorded in frame’s DMA descriptor. For normal operation this bit must be set to zero. IPGSEN: IP Stretch Enable When set, the transmit IPG can be increased above 96 bit times depending on the previous frame length using the IPG Stretch Register. RXBP: Receive Bad Preamble  2017 Microchip Technology Inc. DS60001476B-page 989 SAMA5D2 SERIES When set, frames with non-standard preamble are not rejected. IRXER: Ignore IPG GRXER When set, GRXER has no effect on the GMAC's operation when GRXDV is low. 40.8.3 GMAC Network Status Register Name: GMAC_NSR Address: 0xF8008008 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 RXLPIS 6 – 5 – 4 – 3 – 2 IDLE 1 MDIO 0 – MDIO: MDIO Input Status Returns status of the MDIO pin. IDLE: PHY Management Logic Idle The PHY management logic is idle (i.e., has completed). RXLPIS: LPI Indication Low power idle has been detected on receive. This bit is set when LPI is detected and reset when normal idle is detected. An interrupt is generated when the state of this bit changes. DS60001476B-page 990  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.4 GMAC User Register Name: GMAC_UR Address: 0xF800800C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 RMII RMII: Reduced MII Mode 0: MII mode is selected (default). 1: RMII mode is selected.  2017 Microchip Technology Inc. DS60001476B-page 991 SAMA5D2 SERIES 40.8.5 GMAC DMA Configuration Register Name: GMAC_DCFGR Address: 0xF8008010 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 DDRP 19 18 17 16 8 DRBS 15 – 14 – 13 – 12 – 11 TXCOEN 10 TXPBMS 9 7 ESPA 6 ESMA 5 – 4 3 2 FBLDO 1 RXBMS 0 FBLDO: Fixed Burst Length for DMA Data Operations: Selects the burst length to attempt to use on the AHB when transferring frame data. Not used for DMA management operations and only used where space and data size allow. Otherwise SINGLE type AHB transfers are used. One-hot priority encoding enforced automatically on register writes as follows, where ‘x’ represents don’t care: Value Name Description 0 – Reserved 1 SINGLE 00001: Always use SINGLE AHB bursts 2 – Reserved 4 INCR4 001xx: Attempt to use INCR4 AHB bursts (Default) 8 INCR8 01xxx: Attempt to use INCR8 AHB bursts 16 INCR16 1xxxx: Attempt to use INCR16 AHB bursts ESMA: Endian Swap Mode Enable for Management Descriptor Accesses When set, selects swapped endianism for AHB transfers. When clear, selects little endian mode. ESPA: Endian Swap Mode Enable for Packet Data Accesses When set, selects swapped endianism for AHB transfers. When clear, selects little endian mode. RXBMS: Receiver Packet Buffer Memory Size Select The default receive packet buffer size is 4 Kbytes. The table below shows how to configure this memory to FULL, HALF, QUARTER or EIGHTH of the default size. Value Name Description 0 EIGHTH 4/8 Kbyte Memory Size 1 QUARTER 4/4 Kbytes Memory Size 2 HALF 4/2 Kbytes Memory Size 3 FULL 4 Kbytes Memory Size DS60001476B-page 992  2017 Microchip Technology Inc. SAMA5D2 SERIES TXPBMS: Transmitter Packet Buffer Memory Size Select Having this bit at zero halves the amount of memory used for the transmit packet buffer. This reduces the amount of memory used by the GMAC. It is important to set this bit to one if the full configured physical memory is available. The value in brackets below represents the size that would result for the default maximum configured memory size of 4 Kbytes. 0: Do not use top address bit (2 Kbytes). 1: Use full configured addressable space (4 Kbytes). TXCOEN: Transmitter Checksum Generation Offload Enable Transmitter IP, TCP and UDP checksum generation offload enable. When set, the transmitter checksum generation engine is enabled to calculate and substitute checksums for transmit frames. When clear, frame data is unaffected. DRBS: DMA Receive Buffer Size DMA receive buffer size in AHB system memory. The value defined by these bits determines the size of buffer to use in main AHB system memory when writing received data. The value is defined in multiples of 64 bytes, thus a value of 0x01 corresponds to buffers of 64 bytes, 0x02 corresponds to 128 bytes etc. For example: – 0x02: 128 bytes – 0x18: 1536 bytes (1 × max length frame/buffer) – 0xA0: 10240 bytes (1 × 10K jumbo frame/buffer) Note that this value should never be written as zero. DDRP: DMA Discard Receive Packets When set, the GMAC DMA will automatically discard receive packets from the receiver packet buffer memory when no AHB resource is available. When low, the received packets will remain to be stored in the SRAM based packet buffer until AHB buffer resource next becomes available. A write to this bit is ignored if the DMA is not configured in the packet buffer full store and forward mode.  2017 Microchip Technology Inc. DS60001476B-page 993 SAMA5D2 SERIES 40.8.6 GMAC Transmit Status Register Name: GMAC_TSR Address: 0xF8008014 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 HRESP 7 – 6 – 5 TXCOMP 4 TFC 3 TXGO 2 RLE 1 COL 0 UBR UBR: Used Bit Read Set when a transmit buffer descriptor is read with its used bit set. Writing a one clears this bit. COL: Collision Occurred Set by the assertion of collision. Writing a one clears this bit. When operating in 10/100 mode, this status indicates either a collision or a late collision. RLE: Retry Limit Exceeded Writing a one clears this bit. TXGO: Transmit Go Transmit go, if high transmit is active. When using the DMA interface this bit represents the TXGO variable as specified in the transmit buffer description. TFC: Transmit Frame Corruption Due to AHB Error Transmit frame corruption due to AHB error. Set if an error occurs while midway through reading transmit frame from the AHB, including HRESP errors and buffers exhausted mid frame (if the buffers run out during transmission of a frame then transmission stops, FCS shall be bad and GTXER asserted). Also set in DMA packet buffer mode if single frame is too large for configured packet buffer memory size. Writing a one clears this bit. TXCOMP: Transmit Complete Set when a frame has been transmitted. Writing a one clears this bit. HRESP: HRESP Not OK Set when the DMA block sees HRESP not OK. Writing a one clears this bit. DS60001476B-page 994  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.7 GMAC Receive Buffer Queue Base Address Register Name: GMAC_RBQB Address: 0xF8008018 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR This register holds the start address of the receive buffer queue (receive buffers descriptor list). The receive buffer queue base address must be initialized before receive is enabled through bit 2 of the Network Control Register. Once reception is enabled, any write to the Receive Buffer Queue Base Address Register is ignored. 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. In terms of AMBA AHB operation, the descriptors are read from memory using a single 32-bit AHB access. The descriptors should be aligned at 32-bit boundaries and the descriptors are written to using two individual non sequential accesses. ADDR: Receive Buffer Queue Base Address Written with the address of the start of the receive queue.  2017 Microchip Technology Inc. DS60001476B-page 995 SAMA5D2 SERIES 40.8.8 GMAC Transmit Buffer Queue Base Address Register Name: GMAC_TBQB Address: 0xF800801C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR This register holds the start address of the transmit buffer queue (transmit buffers descriptor list). The Transmit Buffer Queue Base Address Register must be initialized before transmit is started through bit 9 of the Network Control Register. Once transmission has started, any write to the Transmit Buffer Queue Base Address Register is illegal and therefore ignored. Note that due to clock boundary synchronization, it takes a maximum of four MCK cycles from the writing of the transmit start bit before the transmitter is active. Writing to the Transmit Buffer Queue Base Address Register during this time may produce unpredictable results. Reading this register returns the location of the descriptor currently being accessed. Since the DMA handles two frames at once, this may not necessarily be pointing to the current frame being transmitted. In terms of AMBA AHB operation, the descriptors are written to memory using a single 32-bit AHB access. The descriptors should be aligned at 32-bit boundaries and the descriptors are read from memory using two individual non sequential accesses. ADDR: Transmit Buffer Queue Base Address Written with the address of the start of the transmit queue. DS60001476B-page 996  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.9 GMAC Receive Status Register Name: GMAC_RSR Address: 0xF8008020 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 HNO 2 RXOVR 1 REC 0 BNA This register, when read, provides receive status details. Once read, individual bits may be cleared by writing a one 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 will re-read the pointer each time an end of frame is received until a valid pointer is found. This bit is set following each descriptor read attempt that fails, even if consecutive pointers are unsuccessful and software has in the mean time cleared the status flag. Writing a one clears this bit. REC: Frame Received One or more frames have been received and placed in memory. Writing a one clears this bit. RXOVR: Receive Overrun This bit is set if the receive status was not taken at the end of the frame. This bit is also set if the packet buffer overflows. The buffer will be recovered if an overrun occurs. Writing a one clears this bit. HNO: HRESP Not OK Set when the DMA block sees HRESP not OK. Writing a one clears this bit.  2017 Microchip Technology Inc. DS60001476B-page 997 SAMA5D2 SERIES 40.8.10 GMAC Interrupt Status Register Name: GMAC_ISR Address: 0xF8008024 Access: Read-only 31 – 30 – 29 TSUTIMCOMP 28 WOL 27 RXLPISBC 26 SRI 25 PDRSFT 24 PDRQFT 23 PDRSFR 22 PDRQFR 21 SFT 20 DRQFT 19 SFR 18 DRQFR 17 – 16 – 15 – 14 PFTR 13 PTZ 12 PFNZ 11 HRESP 10 ROVR 9 – 8 – 7 TCOMP 6 TFC 5 RLEX 4 TUR 3 TXUBR 2 RXUBR 1 RCOMP 0 MFS This register indicates the source of the interrupt. In order that the bits of this register read 1, the corresponding interrupt source must be enabled in the mask register. If any bit is set in this register, the GMAC interrupt signal will be asserted in the system. MFS: Management Frame Sent 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: RX Used Bit Read Set when a receive buffer descriptor is read with its used bit set. Cleared on read. TXUBR: TX Used Bit Read Set when a transmit buffer descriptor is read with its used bit set. Cleared on read. TUR: Transmit Underrun This interrupt is set if the transmitter was forced to terminate a frame that it has already began transmitting due to further data being unavailable. This interrupt is set if a transmitter status write back has not completed when another status write back is attempted. This interrupt is also set when the transmit DMA has written the SOP data into the FIFO and either the AHB bus was not granted in time for further data, or because an AHB not OK response was returned, or because the used bit was read. RLEX: Retry Limit Exceeded Transmit error. Cleared on read. TFC: Transmit Frame Corruption Due to AHB Error Transmit frame corruption due to AHB error. Set if an error occurs while midway through reading transmit frame from the AHB, including HRESP errors and buffers exhausted mid frame. TCOMP: Transmit Complete Set when a frame has been transmitted. Cleared on read. ROVR: Receive Overrun Set when the receive overrun status bit is set. Cleared on read. HRESP: HRESP Not OK Set when the DMA block sees HRESP not OK. Cleared on read. PFNZ: Pause Frame with Non-zero Pause Quantum Received DS60001476B-page 998  2017 Microchip Technology Inc. SAMA5D2 SERIES Indicates a valid pause has been received that has a non-zero pause quantum field. Cleared on read. PTZ: Pause Time Zero Set when either the Pause Time register at address 0x38 decrements to zero, or when a valid pause frame is received with a zero pause quantum field. Cleared on read. PFTR: Pause Frame Transmitted Indicates a pause frame has been successfully transmitted after being initiated from the Network Control register. Cleared on read. DRQFR: PTP Delay Request Frame Received Indicates a PTP delay_req frame has been received. Cleared on read. SFR: PTP Sync Frame Received Indicates a PTP sync frame has been received. Cleared on read. DRQFT: PTP Delay Request Frame Transmitted Indicates a PTP delay_req frame has been transmitted. Cleared on read. SFT: PTP Sync Frame Transmitted Indicates a PTP sync frame has been transmitted. Cleared on read. PDRQFR: PDelay Request Frame Received Indicates a PTP pdelay_req frame has been received. Cleared on read. PDRSFR: PDelay Response Frame Received Indicates a PTP pdelay_resp frame has been received. Cleared on read. PDRQFT: PDelay Request Frame Transmitted Indicates a PTP pdelay_req frame has been transmitted. Cleared on read. PDRSFT: PDelay Response Frame Transmitted Indicates a PTP pdelay_resp frame has been transmitted. Cleared on read. SRI: TSU Seconds Register Increment Indicates the register has incremented. Cleared on read. RXLPISBC: Receive LPI indication Status Bit Change Receive LPI indication status bit change. Cleared on read. WOL: Wake On LAN WOL interrupt. Indicates a WOL event has been received. TSUTIMCOMP: TSU Timer Comparison Indicates when TSU timer count value is equal to programmed value. Cleared on read.  2017 Microchip Technology Inc. DS60001476B-page 999 SAMA5D2 SERIES 40.8.11 GMAC Interrupt Enable Register Name: GMAC_IER Address: 0xF8008028 Access: Write-only 31 – 30 – 29 TSUTIMCOMP 28 WOL 27 RXLPISBC 26 SRI 25 PDRSFT 24 PDRQFT 23 PDRSFR 22 PDRQFR 21 SFT 20 DRQFT 19 SFR 18 DRQFR 17 – 16 – 15 EXINT 14 PFTR 13 PTZ 12 PFNZ 11 HRESP 10 ROVR 9 – 8 – 7 TCOMP 6 TFC 5 RLEX 4 TUR 3 TXUBR 2 RXUBR 1 RCOMP 0 MFS This register is write-only and when read will return zero. The following values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. MFS: Management Frame Sent RCOMP: Receive Complete RXUBR: RX Used Bit Read TXUBR: TX Used Bit Read TUR: Transmit Underrun RLEX: Retry Limit Exceeded or Late Collision TFC: Transmit Frame Corruption Due to AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK PFNZ: Pause Frame with Non-zero Pause Quantum Received PTZ: Pause Time Zero PFTR: Pause Frame Transmitted EXINT: External Interrupt DRQFR: PTP Delay Request Frame Received SFR: PTP Sync Frame Received DRQFT: PTP Delay Request Frame Transmitted SFT: PTP Sync Frame Transmitted PDRQFR: PDelay Request Frame Received PDRSFR: PDelay Response Frame Received DS60001476B-page 1000  2017 Microchip Technology Inc. SAMA5D2 SERIES PDRQFT: PDelay Request Frame Transmitted PDRSFT: PDelay Response Frame Transmitted SRI: TSU Seconds Register Increment RXLPISBC: Enable RX LPI Indication WOL: Wake On LAN TSUTIMCOMP: TSU Timer Comparison  2017 Microchip Technology Inc. DS60001476B-page 1001 SAMA5D2 SERIES 40.8.12 GMAC Interrupt Disable Register Name: GMAC_IDR Address: 0xF800802C Access: Write-only 31 – 30 – 29 TSUTIMCOMP 28 WOL 27 RXLPISBC 26 SRI 25 PDRSFT 24 PDRQFT 23 PDRSFR 22 PDRQFR 21 SFT 20 DRQFT 19 SFR 18 DRQFR 17 – 16 – 15 EXINT 14 PFTR 13 PTZ 12 PFNZ 11 HRESP 10 ROVR 9 – 8 – 7 TCOMP 6 TFC 5 RLEX 4 TUR 3 TXUBR 2 RXUBR 1 RCOMP 0 MFS This register is write-only and when read will return zero. The following values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. MFS: Management Frame Sent RCOMP: Receive Complete RXUBR: RX Used Bit Read TXUBR: TX Used Bit Read TUR: Transmit Underrun RLEX: Retry Limit Exceeded or Late Collision TFC: Transmit Frame Corruption Due to AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK PFNZ: Pause Frame with Non-zero Pause Quantum Received PTZ: Pause Time Zero PFTR: Pause Frame Transmitted EXINT: External Interrupt DRQFR: PTP Delay Request Frame Received SFR: PTP Sync Frame Received DRQFT: PTP Delay Request Frame Transmitted SFT: PTP Sync Frame Transmitted PDRQFR: PDelay Request Frame Received PDRSFR: PDelay Response Frame Received DS60001476B-page 1002  2017 Microchip Technology Inc. SAMA5D2 SERIES PDRQFT: PDelay Request Frame Transmitted PDRSFT: PDelay Response Frame Transmitted SRI: TSU Seconds Register Increment RXLPISBC: Enable RX LPI Indication WOL: Wake On LAN TSUTIMCOMP: TSU Timer Comparison  2017 Microchip Technology Inc. DS60001476B-page 1003 SAMA5D2 SERIES 40.8.13 GMAC Interrupt Mask Register Name: GMAC_IMR Address: 0xF8008030 Access: Read/Write 31 – 30 – 29 TSUTIMCOMP 28 WOL 27 RXLPISBC 26 SRI 25 PDRSFT 24 PDRQFT 23 PDRSFR 22 PDRQFR 21 SFT 20 DRQFT 19 SFR 18 DRQFR 17 – 16 – 15 EXINT 14 PFTR 13 PTZ 12 PFNZ 11 HRESP 10 ROVR 9 – 8 – 7 TCOMP 6 TFC 5 RLEX 4 TUR 3 TXUBR 2 RXUBR 1 RCOMP 0 MFS The Interrupt Mask Register is a read-only register indicating which interrupts are masked. All bits are set at reset and can be reset individually by writing to the Interrupt Enable Register or set individually by writing to the Interrupt Disable Register. Having separate address locations for enable and disable saves the need for performing a read modify write when updating the Interrupt Mask Register. For test purposes there is a write-only function to this register that allows the bits in the Interrupt Status Register to be set or cleared, regardless of the state of the mask register. A write to this register directly affects the state of the corresponding bit in the Interrupt Status Register, causing an interrupt to be generated if a 1 is written. The following values are valid for all listed bit names of this register when read: 0: The corresponding interrupt is enabled. 1: The corresponding interrupt is not enabled. MFS: Management Frame Sent RCOMP: Receive Complete RXUBR: RX Used Bit Read TXUBR: TX Used Bit Read TUR: Transmit Underrun RLEX: Retry Limit Exceeded TFC: Transmit Frame Corruption Due to AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK PFNZ: Pause Frame with Non-zero Pause Quantum Received PTZ: Pause Time Zero PFTR: Pause Frame Transmitted EXINT: External Interrupt DRQFR: PTP Delay Request Frame Received SFR: PTP Sync Frame Received DRQFT: PTP Delay Request Frame Transmitted DS60001476B-page 1004  2017 Microchip Technology Inc. SAMA5D2 SERIES SFT: PTP Sync Frame Transmitted PDRQFR: PDelay Request Frame Received PDRSFR: PDelay Response Frame Received PDRQFT: PDelay Request Frame Transmitted PDRSFT: PDelay Response Frame Transmitted SRI: TSU Seconds Register Increment RXLPISBC: Enable RX LPI Indication WOL: Wake On LAN TSUTIMCOMP: TSU Timer Comparison  2017 Microchip Technology Inc. DS60001476B-page 1005 SAMA5D2 SERIES 40.8.14 GMAC PHY Maintenance Register Name: GMAC_MAN Address: 0xF8008034 Access: Read/Write 31 WZO 30 CLTTO 29 23 PHYA 22 21 15 14 28 27 26 OP 25 24 PHYA 20 REGA 19 12 11 10 9 8 3 2 1 0 13 18 17 16 WTN DATA 7 6 5 4 DATA 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 2 is set in the Network Status Register. It takes about 2000 MCK cycles to complete, when MDC is set for MCK divide by 32 in the Network Configuration Register. An interrupt is generated upon completion. 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. See Section 22.2.4.5 of the IEEE 802.3 standard. Reading during the shift operation returns the current contents of the shift register. At the end of management operation, the bits will 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, bit 30 should be written with a 0 rather than a 1. To write clause 45 PHYs, bits 31:28 should be written as 0x0001. See Table 40-19. Table 40-19: Clause 22/Clause 45 PHYs Read/Write Access Configuration (GMAC_MAN Bits 31:28) Bit Value PHY Access WZO CLTTO OP[1] OP[0] Read 0 1 1 0 Write 0 1 0 1 Read 0 0 1 1 Write 0 0 0 1 Read + Address 0 0 1 0 Clause 22 Clause 45 For a description of MDC generation, see Section 40.8.2 ”GMAC Network Configuration Register”. DATA: PHY Data For a write operation this field is written with the data to be written to the PHY. After a read operation this field contains the data read from the PHY. WTN: Write Ten Must be written to 10. DS60001476B-page 1006  2017 Microchip Technology Inc. SAMA5D2 SERIES REGA: Register Address Specifies the register in the PHY to access. PHYA: PHY Address OP: Operation 01: Write 10: Read CLTTO: Clause 22 Operation 0: Clause 45 operation 1: Clause 22 operation WZO: Write ZERO Must be written with 0.  2017 Microchip Technology Inc. DS60001476B-page 1007 SAMA5D2 SERIES 40.8.15 GMAC Receive Pause Quantum Register Name: GMAC_RPQ Address: 0xF8008038 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RPQ 7 6 5 4 RPQ RPQ: Received Pause Quantum Stores the current value of the Receive Pause Quantum Register which is decremented every 512 bit times. DS60001476B-page 1008  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.16 GMAC Transmit Pause Quantum Register Name: GMAC_TPQ Address: 0xF800803C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TPQ 7 6 5 4 TPQ TPQ: Transmit Pause Quantum Written with the pause quantum value for pause frame transmission.  2017 Microchip Technology Inc. DS60001476B-page 1009 SAMA5D2 SERIES 40.8.17 GMAC TX Partial Store and Forward Register Name: GMAC_TPSF Address: 0xF8008040 Access: Read/Write 31 ENTXP 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 7 6 5 4 1 0 TPB1ADR 3 2 TPB1ADR TPB1ADR: Transmit Partial Store and Forward Address Watermark value. Reset = 1. ENTXP: Enable TX Partial Store and Forward Operation DS60001476B-page 1010  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.18 GMAC RX Partial Store and Forward Register Name: GMAC_RPSF Address: 0xF8008044 Access: Read/Write 31 ENRXP 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 7 6 5 4 1 0 RPB1ADR 3 2 RPB1ADR RPB1ADR: Receive Partial Store and Forward Address Watermark value. Reset = 1. ENRXP: Enable RX Partial Store and Forward Operation  2017 Microchip Technology Inc. DS60001476B-page 1011 SAMA5D2 SERIES 40.8.19 GMAC RX Jumbo Frame Max Length Register Name: GMAC_RJFML Address: 0xF8008048 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 12 11 10 9 8 7 6 5 2 1 0 FML 4 3 FML FML: Frame Max Length Rx jumbo frame maximum length. DS60001476B-page 1012  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.20 GMAC Hash Register Bottom Name: GMAC_HRB Address: 0xF8008080 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The unicast hash enable (UNIHEN) and the multicast hash enable (MITIHEN) bits in the Network Configuration Register (Section 40.8.2 ”GMAC Network Configuration Register”) enable the reception of hash matched frames. See Section 40.6.9 ”Hash Addressing”. ADDR: Hash Address The first 32 bits of the Hash Address Register.  2017 Microchip Technology Inc. DS60001476B-page 1013 SAMA5D2 SERIES 40.8.21 GMAC Hash Register Top Name: GMAC_HRT Address: 0xF8008084 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The unicast hash enable (UNIHEN) and the multicast hash enable (MITIHEN) bits in the GMAC Network Configuration Register enable the reception of hash matched frames. See Section 40.6.9 ”Hash Addressing”. ADDR: Hash Address Bits 63 to 32 of the Hash Address Register. DS60001476B-page 1014  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.22 GMAC Specific Address 1 Bottom Register Name: GMAC_SAB1 Address: 0xF8008088 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 1 Least significant 32 bits of the destination address, that is, bits 31:0. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received.  2017 Microchip Technology Inc. DS60001476B-page 1015 SAMA5D2 SERIES 40.8.23 GMAC Specific Address 1 Top Register Name: GMAC_SAT1 Address: 0xF800808C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 1 The most significant bits of the destination address, that is, bits 47:32. DS60001476B-page 1016  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.24 GMAC Specific Address 2 Bottom Register Name: GMAC_SAB2 Address: 0xF8008090 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 2 Least significant 32 bits of the destination address, that is, bits 31:0. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received.  2017 Microchip Technology Inc. DS60001476B-page 1017 SAMA5D2 SERIES 40.8.25 GMAC Specific Address 2 Top Register Name: GMAC_SAT2 Address: 0xF8008094 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 2 The most significant bits of the destination address, that is, bits 47:32. DS60001476B-page 1018  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.26 GMAC Specific Address 3 Bottom Register Name: GMAC_SAB3 Address: 0xF8008098 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 3 Least significant 32 bits of the destination address, that is, bits 31:0. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received.  2017 Microchip Technology Inc. DS60001476B-page 1019 SAMA5D2 SERIES 40.8.27 GMAC Specific Address 3 Top Register Name: GMAC_SAT3 Address: 0xF800809C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 3 The most significant bits of the destination address, that is, bits 47:32. DS60001476B-page 1020  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.28 GMAC Specific Address 4 Bottom Register Name: GMAC_SAB4 Address: 0xF80080A0 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 4 Least significant 32 bits of the destination address, that is, bits 31:0. Bit zero indicates whether the address is multicast or unicast and corresponds to the least significant bit of the first byte received.  2017 Microchip Technology Inc. DS60001476B-page 1021 SAMA5D2 SERIES 40.8.29 GMAC Specific Address 4 Top Register Name: GMAC_SAT4 Address: 0xF80080A4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 ADDR 7 6 5 4 ADDR The addresses stored in the Specific Address Registers are deactivated at reset or when their corresponding Specific Address Register Bottom is written. They are activated when Specific Address Register Top is written. ADDR: Specific Address 4 The most significant bits of the destination address, that is, bits 47:32. DS60001476B-page 1022  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.30 GMAC Type ID Match 1 Register Name: GMAC_TIDM1 Address: 0xF80080A8 Access: Read/Write 31 ENID1 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TID 7 6 5 4 TID TID: Type ID Match 1 For use in comparisons with received frames type ID/length frames. ENID1: Enable Copying of TID Matched Frames 0: TID is not part of the comparison match. 1: TID is processed for the comparison match.  2017 Microchip Technology Inc. DS60001476B-page 1023 SAMA5D2 SERIES 40.8.31 GMAC Type ID Match 2 Register Name: GMAC_TIDM2 Address: 0xF80080AC Access: Read/Write 31 ENID2 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TID 7 6 5 4 TID TID: Type ID Match 2 For use in comparisons with received frames type ID/length frames. ENID2: Enable Copying of TID Matched Frames 0: TID is not part of the comparison match. 1: TID is processed for the comparison match. DS60001476B-page 1024  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.32 GMAC Type ID Match 3 Register Name: GMAC_TIDM3 Address: 0xF80080B0 Access: Read/Write 31 ENID3 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TID 7 6 5 4 TID TID: Type ID Match 3 For use in comparisons with received frames type ID/length frames. ENID3: Enable Copying of TID Matched Frames 0: TID is not part of the comparison match. 1: TID is processed for the comparison match.  2017 Microchip Technology Inc. DS60001476B-page 1025 SAMA5D2 SERIES 40.8.33 GMAC Type ID Match 4 Register Name: GMAC_TIDM4 Address: 0xF80080B4 Access: Read/Write 31 ENID4 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TID 7 6 5 4 TID TID: Type ID Match 4 For use in comparisons with received frames type ID/length frames. ENID4: Enable Copying of TID Matched Frames 0: TID is not part of the comparison match. 1: TID is processed for the comparison match. DS60001476B-page 1026  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.34 GMAC Wake on LAN Register Name: GMAC_WOL Address: 0xF80080B8 Access: 31 Read/Write 30 29 28 27 26 25 24 – 23 22 21 20 19 MTI 18 SA1 17 ARP 16 MAG 13 12 11 10 9 8 3 2 1 0 – 15 14 IP 7 6 5 4 IP IP: ARP Request IP Address Wake on LAN 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 will not generate an event, even if this is matched by the received frame. MAG: Magic Packet Event Enable Wake on LAN magic packet event enable. ARP: ARP Request Event Enable Wake on LAN ARP request event enable. SA1: Specific Address Register 1 Event Enable Wake on LAN Specific Address Register 1 event enable. MTI: Multicast Hash Event Enable Wake on LAN multicast hash event enable.  2017 Microchip Technology Inc. DS60001476B-page 1027 SAMA5D2 SERIES 40.8.35 GMAC IPG Stretch Register Name: GMAC_IPGS Address: 0xF80080BC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 FL 7 6 5 4 FL FL: Frame Length Bits 7:0 are multiplied with the previously transmitted frame length (including preamble). Bits 15:8 +1 divide the frame length. If the resulting number is greater than 96 and bit 28 is set in the Network Configuration Register then the resulting number is used for the transmit inter-packet-gap. 1 is added to bits 15:8 to prevent a divide by zero. See Section 40.6.4 ”MAC Transmit Block”. DS60001476B-page 1028  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.36 GMAC Stacked VLAN Register Name: GMAC_SVLAN Address: 0xF80080C0 Access: Read/Write 31 ESVLAN 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 VLAN_TYPE 7 6 5 4 VLAN_TYPE VLAN_TYPE: User Defined VLAN_TYPE Field User defined VLAN_TYPE field. When Stacked VLAN is enabled, the first VLAN tag in a received frame will only be accepted if the VLAN type field is equal to this user defined VLAN_TYPE, OR equal to the standard VLAN type (0x8100). Note that the second VLAN tag of a Stacked VLAN packet will only be matched correctly if its VLAN_TYPE field equals 0x8100. ESVLAN: Enable Stacked VLAN Processing Mode 0: Disable the stacked VLAN processing mode 1: Enable the stacked VLAN processing mode  2017 Microchip Technology Inc. DS60001476B-page 1029 SAMA5D2 SERIES 40.8.37 GMAC Transmit PFC Pause Register Name: GMAC_TPFCP Address: 0xF80080C4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 PQ 7 6 5 4 PEV PEV: Priority Enable Vector If bit 17 of the Network Control Register is written with a one then the priority enable vector of the PFC priority based pause frame will be set equal to the value stored in this register [7:0]. PQ: Pause Quantum If bit 17 of the Network Control Register is written with a one then for each entry equal to zero in the Transmit PFC Pause Register[15:8], the PFC pause frame's pause quantum field associated with that entry will be taken from the Transmit Pause Quantum Register. For each entry equal to one in the Transmit PFC Pause Register [15:8], the pause quantum associated with that entry will be zero. DS60001476B-page 1030  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.38 GMAC Specific Address 1 Mask Bottom Register Name: GMAC_SAMB1 Address: 0xF80080C8 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ADDR 23 22 21 20 ADDR 15 14 13 12 ADDR 7 6 5 4 ADDR ADDR: Specific Address 1 Mask Setting a bit to one masks the corresponding bit in the Specific Address 1 Register.  2017 Microchip Technology Inc. DS60001476B-page 1031 SAMA5D2 SERIES 40.8.39 GMAC Specific Address Mask 1 Top Register Name: GMAC_SAMT1 Address: 0xF80080CC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 ADDR 7 6 5 4 ADDR ADDR: Specific Address 1 Mask Setting a bit to one masks the corresponding bit in the Specific Address 1 Register. DS60001476B-page 1032  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.40 GMAC 1588 Timer Nanosecond Comparison Register Name: GMAC_NSC Address: 0xF80080DC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 20 19 18 17 16 15 14 13 11 10 9 8 3 2 1 0 NANOSEC 12 NANOSEC 7 6 5 4 NANOSEC NANOSEC: 1588 Timer Nanosecond Comparison Value Value is compared to the bits [45:24] of the TSU timer count value (upper 22 bits of nanosecond value).  2017 Microchip Technology Inc. DS60001476B-page 1033 SAMA5D2 SERIES 40.8.41 GMAC 1588 Timer Second Comparison Low Register Name: GMAC_SCL Address: 0xF80080E0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 SEC 23 22 21 20 SEC 15 14 13 12 SEC 7 6 5 4 SEC SEC: 1588 Timer Second Comparison Value Value is compared to seconds value bits [31:0] of the TSU timer count value. DS60001476B-page 1034  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.42 GMAC 1588 Timer Second Comparison High Register Name: GMAC_SCH Address: 0xF80080E4 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 SEC 7 6 5 4 SEC SEC: 1588 Timer Second Comparison Value Value is compared to the top 16 bits (most significant 16 bits [47:32] of seconds value) of the TSU timer count value.  2017 Microchip Technology Inc. DS60001476B-page 1035 SAMA5D2 SERIES 40.8.43 GMAC PTP Event Frame Transmitted Seconds High Register Name: GMAC_EFTSH Address: 0xF80080E8 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 timer seconds register held when the SFD of a PTP transmit primary event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1036  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.44 GMAC PTP Event Frame Received Seconds High Register Name: GMAC_EFRSH Address: 0xF80080EC Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 timer seconds register held when the SFD of a PTP transmit primary event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1037 SAMA5D2 SERIES 40.8.45 GMAC PTP Peer Event Frame Transmitted Seconds High Register Name: GMAC_PEFTSH Address: 0xF80080F0 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 timer seconds register held when the SFD of a PTP transmit peer event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1038  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.46 GMAC PTP Peer Event Frame Received Seconds High Register Name: GMAC_PEFRSH Address: 0xF80080F4 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 timer seconds register held when the SFD of a PTP transmit peer event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1039 SAMA5D2 SERIES 40.8.47 GMAC Octets Transmitted Low Register Name: GMAC_OTLO Address: 0xF8008100 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TXO 23 22 21 20 TXO 15 14 13 12 TXO 7 6 5 4 TXO When reading the Octets Transmitted and Octets Received Registers, bits 31:0 should be read prior to bits 47:32 to ensure reliable operation. TXO: Transmitted Octets Transmitted octets in frame without errors [31:0]. The number of octets transmitted in valid frames of any type. This counter is 48-bits, and is read through two registers. This count does not include octets from automatically generated pause frames. DS60001476B-page 1040  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.48 GMAC Octets Transmitted High Register Name: GMAC_OTHI Address: 0xF8008104 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TXO 7 6 5 4 TXO When reading the Octets Transmitted and Octets Received Registers, bits 31:0 should be read prior to bits 47:32 to ensure reliable operation. TXO: Transmitted Octets Transmitted octets in frame without errors [47:32]. The number of octets transmitted in valid frames of any type. This counter is 48-bits, and is read through two registers. This count does not include octets from automatically generated pause frames.  2017 Microchip Technology Inc. DS60001476B-page 1041 SAMA5D2 SERIES 40.8.49 GMAC Frames Transmitted Register Name: GMAC_FT Address: 0xF8008108 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 FTX 23 22 21 20 FTX 15 14 13 12 FTX 7 6 5 4 FTX FTX: Frames Transmitted without Error Frames transmitted without error. This register counts the number of frames successfully transmitted, i.e., no underrun and not too many retries. Excludes pause frames. DS60001476B-page 1042  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.50 GMAC Broadcast Frames Transmitted Register Name: GMAC_BCFT Address: 0xF800810C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 BFTX 23 22 21 20 BFTX 15 14 13 12 BFTX 7 6 5 4 BFTX BFTX: Broadcast Frames Transmitted without Error Broadcast frames transmitted without error. This register counts the number of broadcast frames successfully transmitted without error, i.e., no underrun and not too many retries. Excludes pause frames.  2017 Microchip Technology Inc. DS60001476B-page 1043 SAMA5D2 SERIES 40.8.51 GMAC Multicast Frames Transmitted Register Name: GMAC_MFT Address: 0xF8008110 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 MFTX 23 22 21 20 MFTX 15 14 13 12 MFTX 7 6 5 4 MFTX MFTX: Multicast Frames Transmitted without Error This register counts the number of multicast frames successfully transmitted without error, i.e., no underrun and not too many retries. Excludes pause frames. DS60001476B-page 1044  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.52 GMAC Pause Frames Transmitted Register Name: GMAC_PFT Address: 0xF8008114 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 PFTX 7 6 5 4 PFTX PFTX: Pause Frames Transmitted Register This register counts the number of pause frames transmitted. Only pause frames triggered by the register interface or through the external pause pins are counted as pause frames. Pause frames received through the FIFO interface are counted in the frames transmitted counter.  2017 Microchip Technology Inc. DS60001476B-page 1045 SAMA5D2 SERIES 40.8.53 GMAC 64 Byte Frames Transmitted Register Name: GMAC_BFT64 Address: 0xF8008118 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 64 Byte Frames Transmitted without Error This register counts the number of 64 byte frames successfully transmitted without error, i.e., no underrun and not too many retries. Excludes pause frames. DS60001476B-page 1046  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.54 GMAC 65 to 127 Byte Frames Transmitted Register Name: GMAC_TBFT127 Address: 0xF800811C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 65 to 127 Byte Frames Transmitted without Error This register counts the number of 65 to 127 byte frames successfully transmitted without error, i.e., no underrun and not too many retries. Excludes pause frames.  2017 Microchip Technology Inc. DS60001476B-page 1047 SAMA5D2 SERIES 40.8.55 GMAC 128 to 255 Byte Frames Transmitted Register Name: GMAC_TBFT255 Address: 0xF8008120 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 128 to 255 Byte Frames Transmitted without Error This register counts the number of 128 to 255 byte frames successfully transmitted without error, i.e., no underrun and not too many retries. DS60001476B-page 1048  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.56 GMAC 256 to 511 Byte Frames Transmitted Register Name: GMAC_TBFT511 Address: 0xF8008124 Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 256 to 511 Byte Frames Transmitted without Error This register counts the number of 256 to 511 byte frames successfully transmitted without error, i.e., no underrun and not too many retries.  2017 Microchip Technology Inc. DS60001476B-page 1049 SAMA5D2 SERIES 40.8.57 GMAC 512 to 1023 Byte Frames Transmitted Register Name: GMAC_TBFT1023 Address: 0xF8008128 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 512 to 1023 Byte Frames Transmitted without Error This register counts the number of 512 to 1023 byte frames successfully transmitted without error, i.e., no underrun and not too many retries. DS60001476B-page 1050  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.58 GMAC 1024 to 1518 Byte Frames Transmitted Register Name: GMAC_TBFT1518 Address: 0xF800812C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: 1024 to 1518 Byte Frames Transmitted without Error This register counts the number of 1024 to 1518 byte frames successfully transmitted without error, i.e., no underrun and not too many retries.  2017 Microchip Technology Inc. DS60001476B-page 1051 SAMA5D2 SERIES 40.8.59 GMAC Greater Than 1518 Byte Frames Transmitted Register Name: GMAC_GTBFT1518 Address: 0xF8008130 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFTX 23 22 21 20 NFTX 15 14 13 12 NFTX 7 6 5 4 NFTX NFTX: Greater than 1518 Byte Frames Transmitted without Error This register counts the number of 1518 or above byte frames successfully transmitted without error i.e., no underrun and not too many retries. DS60001476B-page 1052  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.60 GMAC Transmit Underruns Register Name: GMAC_TUR Address: 0xF8008134 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 TXUNR 0 TXUNR TXUNR: Transmit Underruns This register counts the number of frames not transmitted due to a transmit underrun. If this register is incremented then no other statistics register is incremented.  2017 Microchip Technology Inc. DS60001476B-page 1053 SAMA5D2 SERIES 40.8.61 GMAC Single Collision Frames Register Name: GMAC_SCF Address: 0xF8008138 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 15 14 13 12 11 10 9 8 3 2 1 0 16 SCOL SCOL 7 6 5 4 SCOL SCOL: Single Collision This register counts the number of frames experiencing a single collision before being successfully transmitted i.e., no underrun. DS60001476B-page 1054  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.62 GMAC Multiple Collision Frames Register Name: GMAC_MCF Address: 0xF800813C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 15 14 13 12 11 10 9 8 3 2 1 0 16 MCOL MCOL 7 6 5 4 MCOL MCOL: Multiple Collision This register counts the number of frames experiencing between two and fifteen collisions prior to being successfully transmitted, i.e., no underrun and not too many retries.  2017 Microchip Technology Inc. DS60001476B-page 1055 SAMA5D2 SERIES 40.8.63 GMAC Excessive Collisions Register Name: GMAC_EC Address: 0xF8008140 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 XCOL 0 XCOL XCOL: Excessive Collisions This register counts the number of frames that failed to be transmitted because they experienced 16 collisions. DS60001476B-page 1056  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.64 GMAC Late Collisions Register Name: GMAC_LC Address: 0xF8008144 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 LCOL 0 LCOL LCOL: Late Collisions This register counts the number of late collisions occurring after the slot time (512 bits) has expired. In 10/100 mode, late collisions are counted twice i.e., both as a collision and a late collision.  2017 Microchip Technology Inc. DS60001476B-page 1057 SAMA5D2 SERIES 40.8.65 GMAC Deferred Transmission Frames Register Name: GMAC_DTF Address: 0xF8008148 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 15 14 13 12 11 10 9 8 3 2 1 0 16 DEFT DEFT 7 6 5 4 DEFT DEFT: Deferred Transmission This register counts 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. DS60001476B-page 1058  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.66 GMAC Carrier Sense Errors Register Name: GMAC_CSE Address: 0xF800814C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 CSR 0 CSR CSR: Carrier Sense Error This register counts 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.  2017 Microchip Technology Inc. DS60001476B-page 1059 SAMA5D2 SERIES 40.8.67 GMAC Octets Received Low Register Name: GMAC_ORLO Address: 0xF8008150 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RXO 23 22 21 20 RXO 15 14 13 12 RXO 7 6 5 4 RXO When reading the Octets Transmitted and Octets Received Registers, bits [31:0] should be read prior to bits [47:32] to ensure reliable operation. RXO: Received Octets Received octets in frame without errors [31:0]. The number of octets received in valid frames of any type. This counter is 48-bits and is read through two registers. This count does not include octets from pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1060  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.68 GMAC Octets Received High Register Name: GMAC_ORHI Address: 0xF8008154 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RXO 7 6 5 4 RXO When reading the Octets Transmitted and Octets Received Registers, bits 31:0 should be read prior to bits 47:32 to ensure reliable operation. RXO: Received Octets Received octets in frame without errors [47:32]. The number of octets received in valid frames of any type. This counter is 48-bits and is read through two registers. This count does not include octets from pause frames, and is only incremented if the frame is successfully filtered and copied to memory.  2017 Microchip Technology Inc. DS60001476B-page 1061 SAMA5D2 SERIES 40.8.69 GMAC Frames Received Register Name: GMAC_FR Address: 0xF8008158 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 FRX 23 22 21 20 FRX 15 14 13 12 FRX 7 6 5 4 FRX FRX: Frames Received without Error Frames received without error. This register counts the number of frames successfully received. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1062  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.70 GMAC Broadcast Frames Received Register Name: GMAC_BCFR Address: 0xF800815C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 BFRX 23 22 21 20 BFRX 15 14 13 12 BFRX 7 6 5 4 BFRX BFRX: Broadcast Frames Received without Error Broadcast frames received without error. This register counts the number of broadcast frames successfully received. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory.  2017 Microchip Technology Inc. DS60001476B-page 1063 SAMA5D2 SERIES 40.8.71 GMAC Multicast Frames Received Register Name: GMAC_MFR Address: 0xF8008160 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 MFRX 23 22 21 20 MFRX 15 14 13 12 MFRX 7 6 5 4 MFRX MFRX: Multicast Frames Received without Error This register counts the number of multicast frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1064  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.72 GMAC Pause Frames Received Register Name: GMAC_PFR Address: 0xF8008164 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 PFRX 7 6 5 4 PFRX PFRX: Pause Frames Received Register This register counts the number of pause frames received without error.  2017 Microchip Technology Inc. DS60001476B-page 1065 SAMA5D2 SERIES 40.8.73 GMAC 64 Byte Frames Received Register Name: GMAC_BFR64 Address: 0xF8008168 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 64 Byte Frames Received without Error This register counts the number of 64 byte frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1066  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.74 GMAC 65 to 127 Byte Frames Received Register Name: GMAC_TBFR127 Address: 0xF800816C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 65 to 127 Byte Frames Received without Error This register counts the number of 65 to 127 byte frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory.  2017 Microchip Technology Inc. DS60001476B-page 1067 SAMA5D2 SERIES 40.8.75 GMAC 128 to 255 Byte Frames Received Register Name: GMAC_TBFR255 Address: 0xF8008170 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 128 to 255 Byte Frames Received without Error This register counts the number of 128 to 255 byte frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1068  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.76 GMAC 256 to 511 Byte Frames Received Register Name: GMAC_TBFR511 Address: 0xF8008174 Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 256 to 511 Byte Frames Received without Error This register counts the number of 256 to 511 byte frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory.  2017 Microchip Technology Inc. DS60001476B-page 1069 SAMA5D2 SERIES 40.8.77 GMAC 512 to 1023 Byte Frames Received Register Name: GMAC_TBFR1023 Address: 0xF8008178 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 512 to 1023 Byte Frames Received without Error This register counts the number of 512 to 1023 byte frames successfully received without error. Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. DS60001476B-page 1070  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.78 GMAC 1024 to 1518 Byte Frames Received Register Name: GMAC_TBFR1518 Address: 0xF800817C Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 1024 to 1518 Byte Frames Received without Error This register counts the number of 1024 to 1518 byte frames successfully received without error, i.e., no underrun and not too many retries.  2017 Microchip Technology Inc. DS60001476B-page 1071 SAMA5D2 SERIES 40.8.79 GMAC 1519 to Maximum Byte Frames Received Register Name: GMAC_TMXBFR Address: 0xF8008180 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 NFRX 23 22 21 20 NFRX 15 14 13 12 NFRX 7 6 5 4 NFRX NFRX: 1519 to Maximum Byte Frames Received without Error This register counts the number of 1519 byte or above frames successfully received without error. Maximum frame size is determined by the Network Configuration Register bit 8 (1536 maximum frame size) or bit 3 (jumbo frame size). Excludes pause frames, and is only incremented if the frame is successfully filtered and copied to memory. See Section 40.8.2 ”GMAC Network Configuration Register”. DS60001476B-page 1072  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.80 GMAC Undersized Frames Received Register Name: GMAC_UFR Address: 0xF8008184 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 UFRX 0 UFRX UFRX: Undersize Frames Received This register counts the number of frames received less than 64 bytes in length (10/100 mode, full duplex) that do not have either a CRC error or an alignment error.  2017 Microchip Technology Inc. DS60001476B-page 1073 SAMA5D2 SERIES 40.8.81 GMAC Oversized Frames Received Register Name: GMAC_OFR Address: 0xF8008188 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 OFRX 0 OFRX OFRX: Oversized Frames Received This register counts the number of frames received exceeding 1518 bytes (1536 bytes if bit 8 is set in the Network Configuration Register ) in length but do not have either a CRC error, an alignment error nor a receive symbol error. See Section 40.8.2 ”GMAC Network Configuration Register”. DS60001476B-page 1074  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.82 GMAC Jabbers Received Register Name: GMAC_JR Address: 0xF800818C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 JRX 0 JRX JRX: Jabbers Received The register counts the number of frames received exceeding 1518 bytes in length (1536 if bit 8 is set in Network Configuration Register) and have either a CRC error, an alignment error or a receive symbol error. See Section 40.8.2 ”GMAC Network Configuration Register”.  2017 Microchip Technology Inc. DS60001476B-page 1075 SAMA5D2 SERIES 40.8.83 GMAC Frame Check Sequence Errors Register Name: GMAC_FCSE Address: 0xF8008190 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 FCKR 0 FCKR FCKR: Frame Check Sequence Errors The register counts frames that are an integral number of bytes, have bad CRC and are between 64 and 1518 bytes in length (1536 if bit 8 is set in Network Configuration Register). 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. This register is incremented for a frame with bad FCS, regardless of whether it is copied to memory due to ignore FCS mode being enabled in bit 26 of the Network Configuration Register. See Section 40.8.2 ”GMAC Network Configuration Register”. DS60001476B-page 1076  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.84 GMAC Length Field Frame Errors Register Name: GMAC_LFFE Address: 0xF8008194 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 LFER 0 LFER LFER: Length Field Frame Errors This register counts the number of frames received that have a measured length shorter than that extracted from the length field (bytes 13 and 14). This condition is only counted if the value of the length field is less than 0x0600, the frame is not of excessive length and checking is enabled through bit 16 of the Network Configuration Register. See Section 40.8.2 ”GMAC Network Configuration Register”.  2017 Microchip Technology Inc. DS60001476B-page 1077 SAMA5D2 SERIES 40.8.85 GMAC Receive Symbol Errors Register Name: GMAC_RSE Address: 0xF8008198 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 RXSE 0 RXSE RXSE: Receive Symbol Errors This register counts the number of frames that had GRXER asserted during reception. For 10/100 mode symbol errors are counted regardless of frame length checks. Receive symbol errors will also be counted as an FCS or alignment error if the frame is between 64 and 1518 bytes (1536 bytes if bit 8 is set in the Network Configuration Register). If the frame is larger it will be recorded as a jabber error. See Section 40.8.2 ”GMAC Network Configuration Register”. DS60001476B-page 1078  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.86 GMAC Alignment Errors Register Name: GMAC_AE Address: 0xF800819C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 AER 0 AER AER: Alignment Errors This register counts the 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 is set in Network Configuration Register). 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. See Section 40.8.2 ”GMAC Network Configuration Register”.  2017 Microchip Technology Inc. DS60001476B-page 1079 SAMA5D2 SERIES 40.8.87 GMAC Receive Resource Errors Register Name: GMAC_RRE Address: 0xF80081A0 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 15 14 13 12 11 10 9 8 3 2 1 0 16 RXRER RXRER 7 6 5 4 RXRER RXRER: Receive Resource Errors This register counts 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 is set in Network Configuration Register). 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. See Section 40.8.2 ”GMAC Network Configuration Register”. DS60001476B-page 1080  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.88 GMAC Receive Overruns Register Name: GMAC_ROE Address: 0xF80081A4 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 8 7 6 5 4 3 2 1 RXOVR 0 RXOVR RXOVR: Receive Overruns This register counts the number of frames that are address recognized but were not copied to memory due to a receive overrun.  2017 Microchip Technology Inc. DS60001476B-page 1081 SAMA5D2 SERIES 40.8.89 GMAC IP Header Checksum Errors Register Name: GMAC_IHCE Address: 0xF80081A8 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 HCKER HCKER: IP Header Checksum Errors This register counts the number of frames discarded due to an incorrect IP header checksum, but are between 64 and 1518 bytes (1536 bytes if bit 8 is set in the Network Configuration Register) and do not have a CRC error, an alignment error, nor a symbol error. DS60001476B-page 1082  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.90 GMAC TCP Checksum Errors Register Name: GMAC_TCE Address: 0xF80081AC Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 TCKER TCKER: TCP Checksum Errors This register counts the number of frames discarded due to an incorrect TCP checksum, but are between 64 and 1518 bytes (1536 bytes if bit 8 is set in the Network Configuration Register) and do not have a CRC error, an alignment error, nor a symbol error.  2017 Microchip Technology Inc. DS60001476B-page 1083 SAMA5D2 SERIES 40.8.91 GMAC UDP Checksum Errors Register Name: GMAC_UCE Address: 0xF80081B0 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 UCKER UCKER: UDP Checksum Errors This register counts the number of frames discarded due to an incorrect UDP checksum, but are between 64 and 1518 bytes (1536 bytes if bit 8 is set in the Network Configuration Register) and do not have a CRC error, an alignment error, nor a symbol error. DS60001476B-page 1084  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.92 GMAC 1588 Timer Increment Sub-nanoseconds Register Name: GMAC_TISUBN Address: 0xF80081BC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 LSBTIR 7 6 5 4 LSBTIR LSBTIR: Lower Significant Bits of Timer Increment Register Lower significant bits of Timer Increment Register[15:0] giving a 24-bit timer_increment counter. These bits are the sub-ns value which the 1588 timer will be incremented each clock cycle. Bit n = 2(n-16) nsec giving a resolution of approximately 15.2E-15 sec.  2017 Microchip Technology Inc. DS60001476B-page 1085 SAMA5D2 SERIES 40.8.93 GMAC 1588 Timer Seconds High Register Name: GMAC_TSH Address: 0xF80081C0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TCS 7 6 5 4 TCS TCS: Timer Count in Seconds This register is writable. It increments by one when the 1588 nanoseconds counter counts to one second. It may also be incremented when the Timer Adjust Register is written. DS60001476B-page 1086  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.94 GMAC 1588 Timer Seconds Low Register Name: GMAC_TSL Address: 0xF80081D0 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TCS 23 22 21 20 TCS 15 14 13 12 TCS 7 6 5 4 TCS TCS: Timer Count in Seconds This register is writable. It increments by one when the 1588 nanoseconds counter counts to one second. It may also be incremented when the Timer Adjust Register is written.  2017 Microchip Technology Inc. DS60001476B-page 1087 SAMA5D2 SERIES 40.8.95 GMAC 1588 Timer Nanoseconds Register Name: GMAC_TN Address: 0xF80081D4 Access: Read/Write 31 – 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TNS 20 TNS 15 14 13 12 TNS 7 6 5 4 TNS TNS: Timer Count in Nanoseconds This register is writable. It can also be adjusted by writes to the 1588 Timer Adjust Register. It increments by the value of the 1588 Timer Increment Register each clock cycle. DS60001476B-page 1088  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.96 GMAC 1588 Timer Adjust Register Name: GMAC_TA Address: 0xF80081D8 Access: Write-only 31 ADJ 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ITDT 20 ITDT 15 14 13 12 ITDT 7 6 5 4 ITDT ITDT: Increment/Decrement The number of nanoseconds to increment or decrement the 1588 Timer Nanoseconds Register. If necessary, the 1588 Seconds Register will be incremented or decremented. ADJ: Adjust 1588 Timer Write as one to subtract from the 1588 timer. Write as zero to add to it.  2017 Microchip Technology Inc. DS60001476B-page 1089 SAMA5D2 SERIES 40.8.97 GMAC 1588 Timer Increment Register Name: GMAC_TI Address: 0xF80081DC Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 NIT 15 14 13 12 ACNS 7 6 5 4 CNS CNS: Count Nanoseconds A count of nanoseconds by which the 1588 Timer Nanoseconds Register will be incremented each clock cycle. ACNS: Alternative Count Nanoseconds Alternative count of nanoseconds by which the 1588 Timer Nanoseconds Register will be incremented each clock cycle. NIT: Number of Increments The number of increments after which the alternative increment is used. DS60001476B-page 1090  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.98 GMAC PTP Event Frame Transmitted Seconds Low Register Name: GMAC_EFTSL Address: 0xF80081E0 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 23 22 21 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Seconds Register holds when the SFD of a PTP transmit primary event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1091 SAMA5D2 SERIES 40.8.99 GMAC PTP Event Frame Transmitted Nanoseconds Register Name: GMAC_EFTN Address: 0xF80081E4 Access: Read-only 31 – 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Nanoseconds Register holds when the SFD of a PTP transmit primary event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1092  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.100 GMAC PTP Event Frame Received Seconds Low Register Name: GMAC_EFRSL Address: 0xF80081E8 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 23 22 21 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Seconds Register holds when the SFD of a PTP receive primary event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1093 SAMA5D2 SERIES 40.8.101 GMAC PTP Event Frame Received Nanoseconds Register Name: GMAC_EFRN Address: 0xF80081EC Access: Read-only 31 – 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Nanoseconds Register holds when the SFD of a PTP receive primary event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1094  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.102 GMAC PTP Peer Event Frame Transmitted Seconds Low Register Name: GMAC_PEFTSL Address: 0xF80081F0 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 23 22 21 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Seconds Register holds when the SFD of a PTP transmit peer event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1095 SAMA5D2 SERIES 40.8.103 GMAC PTP Peer Event Frame Transmitted Nanoseconds Register Name: GMAC_PEFTN Address: 0xF80081F4 Access: Read-only 31 – 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Nanoseconds Register holds when the SFD of a PTP transmit peer event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1096  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.104 GMAC PTP Peer Event Frame Received Seconds Low Register Name: GMAC_PEFRSL Address: 0xF80081F8 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 23 22 21 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Seconds Register holds when the SFD of a PTP receive primary event crosses the MII interface. An interrupt is issued when the register is updated.  2017 Microchip Technology Inc. DS60001476B-page 1097 SAMA5D2 SERIES 40.8.105 GMAC PTP Peer Event Frame Received Nanoseconds Register Name: GMAC_PEFRN Address: 0xF80081FC Access: Read-only 31 – 30 – 29 23 22 21 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RUD 20 RUD 15 14 13 12 RUD 7 6 5 4 RUD RUD: Register Update The register is updated with the value that the 1588 Timer Nanoseconds Register holds when the SFD of a PTP receive primary event crosses the MII interface. An interrupt is issued when the register is updated. DS60001476B-page 1098  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.106 GMAC Received LPI Transitions Name: GMAC_RXLPI Address: 0xF8008270 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 COUNT 7 6 5 4 COUNT COUNT: Count of RX LPI transitions (cleared on read) A count of the number of times there is a transition from receiving normal idle to receiving low power idle.  2017 Microchip Technology Inc. DS60001476B-page 1099 SAMA5D2 SERIES 40.8.107 GMAC Received LPI Time Name: GMAC_RXLPITIME Address: 0xF8008274 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 LPITIME 15 14 13 12 LPITIME 7 6 5 4 LPITIME LPITIME: Time in LPI (cleared on read) This field increments once every 16 MCK cycles when the bit LPI Indication (bit 7) is set in the Network Status register. DS60001476B-page 1100  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.108 GMAC Transmit LPI Transitions Name: GMAC_TXLPI Address: 0xF8008278 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 COUNT 7 6 5 4 COUNT COUNT: Count of LPI transitions (cleared on read) A count of the number of times the bit Enable LPI Transmission (bit 19) goes from low to high in the Network Control register.  2017 Microchip Technology Inc. DS60001476B-page 1101 SAMA5D2 SERIES 40.8.109 GMAC Transmit LPI Time Name: GMAC_TXLPITIME Address: 0xF800827C Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 LPITIME 15 14 13 12 LPITIME 7 6 5 4 LPITIME LPITIME: Time in LPI (cleared on read) This field increments once every 16 MCK cycles when the bit Enable LPI Transmission (bit 19) is set in the Network Control register. DS60001476B-page 1102  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.110 GMAC Interrupt Status Register Priority Queue x Name: GMAC_ISRPQx[x=1..2] Address: 0xF8008400 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 – 23 22 21 20 – 15 14 13 12 11 HRESP 10 ROVR 9 – 8 – 5 RLEX 4 – 3 – 2 RXUBR 1 RCOMP 0 – – 7 TCOMP 6 TFC RCOMP: Receive Complete RXUBR: RX Used Bit Read RLEX: Retry Limit Exceeded or Late Collision TFC: Transmit Frame Corruption Due to AHB Error Transmit frame corruption due to AHB error—set if an error occurs whilst midway through reading transmit frame from the AHB, including HRESP errors and buffers exhausted mid frame. TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK  2017 Microchip Technology Inc. DS60001476B-page 1103 SAMA5D2 SERIES 40.8.111 GMAC Transmit Buffer Queue Base Address Register Priority Queue x Name: GMAC_TBQBAPQx[x=1..2] Address: 0xF8008440 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – TXBQBA 23 22 21 20 TXBQBA 15 14 13 12 TXBQBA 7 6 5 4 TXBQBA These registers hold the start address of the transmit buffer queues (transmit buffers descriptor lists) for the additional queues and must be initialized to the address of valid descriptors, even if the priority queues are not used. TXBQBA: Transmit Buffer Queue Base Address Written with the address of the start of the transmit queue. DS60001476B-page 1104  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.112 GMAC Receive Buffer Queue Base Address Register Priority Queue x Name: GMAC_RBQBAPQx[x=1..2] Address: 0xF8008480 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 – 0 – RXBQBA 23 22 21 20 RXBQBA 15 14 13 12 RXBQBA 7 6 5 4 RXBQBA These registers hold the start address of the receive buffer queues (receive buffers descriptor lists) for the additional queues and must be initialized to the address of valid descriptors, even if the priority queues are not used. RXBQBA: Receive Buffer Queue Base Address Written with the address of the start of the receive queue.  2017 Microchip Technology Inc. DS60001476B-page 1105 SAMA5D2 SERIES 40.8.113 GMAC Receive Buffer Size Register Priority Queue x Name: GMAC_RBSRPQx[x=1..2] Address: 0xF80084A0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RBS 7 6 5 4 RBS RBS: Receive Buffer Size DMA receive buffer size in AHB system memory. The value defined by these bits determines the size of buffer to use in main AHB system memory when writing received data. The value is defined in multiples of 64 bytes such that a value of 0x01 corresponds to buffers of 64 bytes, 0x02 corresponds to 128 bytes etc. For example: – 0x02: 128 bytes – 0x18: 1536 bytes (1 ´ max length frame/buffer) – 0xA0: 10240 bytes (1 ´ 10K jumbo frame/buffer) Note that this value should never be written as zero. DS60001476B-page 1106  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.114 GMAC Credit-Based Shaping Control Register Name: GMAC_CBSCR Address: 0xF80084BC Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 QAE 0 QBE • QAE: Queue A CBS Enable 0: Credit-based shaping on the second highest priority queue (queue A) is disabled. 1: Credit-based shaping on the second highest priority queue (queue A) is enabled. • QBE: Queue B CBS Enable 0: Credit-based shaping on the highest priority queue (queue B) is disabled. 1: Credit-based shaping on the highest priority queue (queue B) is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1107 SAMA5D2 SERIES 40.8.115 GMAC Credit-Based Shaping IdleSlope Register for Queue A Name: GMAC_CBSISQA Address: 0xF80084C0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IS 23 22 21 20 IS 15 14 13 12 IS 7 6 5 4 IS Credit-based shaping must be disabled in GMAC_CBSCR before updating this register. IS: IdleSlope IdleSlope value for queue A in bytes/second. The IdleSlope value is defined as the rate of change of credit when a packet is waiting to be sent. This must not exceed the port transmit rate which is dependent on the speed of operation, e.g., 100 Mb/second = 32'h017D7840 If 50% of bandwidth was to be allocated to a particular queue in 100 Mb/second mode, then the IdleSlope value for that queue would be calculated as 32'h017D7840 / 2. DS60001476B-page 1108  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.116 GMAC Credit-Based Shaping IdleSlope Register for Queue B Name: GMAC_CBSISQB Address: 0xF80084C4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IS 23 22 21 20 IS 15 14 13 12 IS 7 6 5 4 IS Credit-based shaping must be disabled in GMAC_CBSCR before updating this register. IS: IdleSlope IdleSlope value for queue B in bytes/second. The IdleSlope value is defined as the rate of change of credit when a packet is waiting to be sent. This must not exceed the port transmit rate which is dependent on the speed of operation, e.g., 100 Mb/second = 32'h017D7840. If 50% of bandwidth was to be allocated to a particular queue in 100 Mb/second mode, then the IdleSlope value for that queue would be calculated as 32'h017D7840 / 2.  2017 Microchip Technology Inc. DS60001476B-page 1109 SAMA5D2 SERIES 40.8.117 GMAC Screening Type 1 Register x Priority Queue Name: GMAC_ST1RPQx[x=0..3] Address: 0xF8008500 Access: Read/Write 31 – 30 – 29 UDPE 28 DSTCE 23 22 21 20 27 26 25 24 UDPM 19 18 17 16 11 10 9 8 1 QNB 0 UDPM 15 14 13 12 UDPM 7 6 DSTCM 5 4 DSTCM 3 – 2 Screening type 1 registers are used to allocate up to 3 priority queues to received frames based on certain IP or UDP fields of incoming frames. QNB: Queue Number (0–2) If a match is successful, then the queue value programmed in bits 2:0 is allocated to the frame. DSTCM: Differentiated Services or Traffic Class Match When DS/TC match enable is set (bit 28), the DS (differentiated services) field of the received IPv4 header or TC field (traffic class) of IPv6 headers are matched against bits 11:4. UDPM: UDP Port Match When UDP port match enable is set (bit 29), the UDP Destination Port of the received UDP frame is matched against bits 27:12. DSTCE: Differentiated Services or Traffic Class Match Enable When DS/TC match enable is set (bit 28), the DS (differentiated services) field of the received IPv4 header or TC field (traffic class) of IPv6 headers are matched against bits 11:4. UDPE: UDP Port Match Enable When UDP port match enable is set (bit 29), the UDP Destination Port of the received UDP frame is matched against bits 27:12. DS60001476B-page 1110  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.118 GMAC Screening Type 2 Register x Priority Queue Name: GMAC_ST2RPQx[x=0..7] Address: 0xF8008540 Access: Read/Write 31 – 30 COMPCE 29 28 27 COMPC 26 25 23 22 21 COMPB 20 19 18 COMPAE 17 24 COMPBE 16 COMPA 15 14 COMPA 13 12 ETHE 11 10 I2ETH 9 8 VLANE 7 – 6 5 VLANP 4 3 – 2 1 QNB 0 Screening type 2 registers are used to allocate up to 3 priority queues to received frames based on the VLAN priority field of received ethernet frames. QNB: Queue Number (0–2) If a match is successful, then the queue value programmed in QNB is allocated to the frame. VLANP: VLAN Priority When VLAN match enable is set (bit 8), the VLAN priority field of the received frame is matched against bits 7:4 of this register. VLANE: VLAN Enable 0: VLAN match is disabled. 1: VLAN match is enabled. I2ETH: Index of Screening Type 2 EtherType register x When ETHE is set (bit 12), the field EtherType (last EtherType in the header if the frame is VLAN tagged) is compared with bits 15:0 in the register designated by the value of I2ETH. ETHE: EtherType Enable 0: EtherType match with bits 15:0 in the register designated by the value of I2ETH is disabled. 1: EtherType match with bits 15:0 in the register designated by the value of I2ETH is enabled. COMPA: Index of Screening Type 2 Compare Word 0/Word 1 register x COMPA is a pointer to the compare registers GMAC_ST2CW0x and GMAC_ST2CW1x. When COMPAE is set, the compare is true if the data at the frame offset ANDed with the value MASKVAL is equal to the value of COMPVAL ANDed with the value of MASKVAL. COMPAE: Compare A Enable 0: Comparison via the register designated by index COMPA is disabled. 1: Comparison via the register designated by index COMPA is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1111 SAMA5D2 SERIES COMPB: Index of Screening Type 2 Compare Word 0/Word 1 register x COMPB is a pointer to the compare registers GMAC_ST2CW0x and GMAC_ST2CW1x. When COMPBE is set, the compare is true if the data at the frame offset ANDed with the value MASKVAL is equal to the value of COMPVAL ANDed with the value of MASKVAL. COMPBE: Compare B Enable 0: Comparison via the register designated by index COMPB is disabled. 1: Comparison via the register designated by index COMPB is enabled. COMPC: Index of Screening Type 2 Compare Word 0/Word 1 register x COMPC is a pointer to the compare registers GMAC_ST2CW0x and GMAC_ST2CW1x. When COMPCE is set, the compare is true if the data at the frame offset ANDed with the value MASKVAL is equal to the value of COMPVAL ANDed with the value of MASKVAL. COMPCE: Compare C Enable 0: Comparison via the register designated by index COMPC is disabled. 1: Comparison via the register designated by index COMPC is enabled. DS60001476B-page 1112  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.119 GMAC Interrupt Enable Register Priority Queue x Name: GMAC_IERPQx[x=1..2] Address: 0xF8008600 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 – 23 22 21 20 – 15 14 13 12 11 HRESP 10 ROVR 9 – 8 – 5 RLEX 4 – 3 – 2 RXUBR 1 RCOMP 0 – – 7 TCOMP 6 TFC The following values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. RCOMP: Receive Complete RXUBR: RX Used Bit Read RLEX: Retry Limit Exceeded or Late Collision TFC: Transmit Frame Corruption Due to AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK  2017 Microchip Technology Inc. DS60001476B-page 1113 SAMA5D2 SERIES 40.8.120 GMAC Interrupt Disable Register Priority Queue x Name: GMAC_IDRPQx[x=1..2] Address: 0xF8008620 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 – 23 22 21 20 – 15 14 13 12 11 HRESP 10 ROVR 9 – 8 – 5 RLEX 4 – 3 – 2 RXUBR 1 RCOMP 0 – – 7 TCOMP 6 TFC The following values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. RCOMP: Receive Complete RXUBR: RX Used Bit Read RLEX: Retry Limit Exceeded or Late Collision TFC: Transmit Frame Corruption Due to AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK DS60001476B-page 1114  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.121 GMAC Interrupt Mask Register Priority Queue x Name: GMAC_IMRPQx[x=1..2] Address: 0xF8008640 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 – 23 22 21 20 – 15 14 13 12 11 HRESP 10 ROVR 9 – 8 – 5 RLEX 4 – 3 – 2 RXUBR 1 RCOMP 0 – – 7 TCOMP 6 AHB A read of this register returns the value of the receive complete interrupt mask. A write to this register directly affects the state of the corresponding bit in the Interrupt Status Register, causing an interrupt to be generated if a 1 is written. The following values are valid for all listed bit names of this register: 0: Corresponding interrupt is enabled. 1: Corresponding interrupt is disabled. RCOMP: Receive Complete RXUBR: RX Used Bit Read RLEX: Retry Limit Exceeded or Late Collision AHB: AHB Error TCOMP: Transmit Complete ROVR: Receive Overrun HRESP: HRESP Not OK  2017 Microchip Technology Inc. DS60001476B-page 1115 SAMA5D2 SERIES 40.8.122 GMAC Screening Type 2 EtherType Register x Name: GMAC_ST2ERx[x=0..3] Address: 0xF80086E0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 COMPVAL 7 6 5 4 COMPVAL COMPVAL: Ethertype Compare Value When the bit GMAC_ST2RPQ.ETHE is enabled, the EtherType (last EtherType in the header if the frame is VLAN tagged) is compared with bits 15:0 in the register designated by GMAC_ST2RPQ.I2ETH. DS60001476B-page 1116  2017 Microchip Technology Inc. SAMA5D2 SERIES 40.8.123 GMAC Screening Type 2 Compare Word 0 Register x Name: GMAC_ST2CW0x[x=0..23] Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 COMPVAL 23 22 21 20 COMPVAL 15 14 13 12 MASKVAL 7 6 5 4 MASKVAL MASKVAL: Mask Value The value of MASKVAL ANDed with the 2 bytes extracted from the frame is compared to the value of MASKVAL ANDed with the value of COMPVAL. COMPVAL: Compare Value The byte stored in bits [23:16] is compared against the first byte of the 2 bytes extracted from the frame. The byte stored in bits [31:24] is compared against the second byte of the 2 bytes extracted from the frame.  2017 Microchip Technology Inc. DS60001476B-page 1117 SAMA5D2 SERIES 40.8.124 GMAC Screening Type 2 Compare Word 1 Register x Name: GMAC_ST2CW1x[x=0..23] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 OFFSSTRT 7 OFFSSTRT 6 5 4 3 OFFSVAL 2 1 0 OFFSVAL: Offset Value in Bytes The value of OFFSVAL ranges from 0 to 127 bytes, and is counted from either the start of the frame, the byte after the EtherType field (last EtherType in the header if the frame is VLAN tagged), the byte after the IP header (IPv4 or IPv6) or the byte after the TCP/UDP header. OFFSSTRT: Ethernet Frame Offset Start Value Name Description 0 FRAMESTART Offset from the start of the frame 1 ETHERTYPE Offset from the byte after the EtherType field 2 IP Offset from the byte after the IP header field 3 TCP_UDP Offset from the byte after the TCP/UDP header field DS60001476B-page 1118  2017 Microchip Technology Inc. SAMA5D2 SERIES 41. USB High Speed Device Port (UDPHS) 41.1 Description The USB High Speed Device Port (UDPHS) is compliant with the Universal Serial Bus (USB), rev 2.0 High Speed device specification. Each endpoint can be configured in one of several USB transfer types. It can be associated with one, two or three banks of a Dual-port RAM used to store the current data payload. If two or three banks are used, one DPR bank is read or written by the processor, while the other is read or written by the USB device peripheral. This feature is mandatory for isochronous endpoints. 41.2 • • • • • • • • Embedded Characteristics 1 High-speed Device 1 UTMI Transceiver shared between Host and Device USB v2.0 High Speed (480 Mbits/s) Compliant 16 Endpoints up to 1024 bytes Embedded Dual-port RAM for Endpoints Suspend/Resume Logic (Command of UTMI) Up to Three Memory Banks for Endpoints (Not for Control Endpoint) 8 Kbytes of DPRAM  2017 Microchip Technology Inc. DS60001476B-page 1119 SAMA5D2 SERIES 41.3 Block Diagram Figure 41-1: Block Diagram APB bus APB Interface ctrl status AHB1 AHB bus Rd/Wr/Ready DMA AHB0 AHB bus UTMI USB2.0 CORE DFSDP/DHSDP DP DFSDM/DHSDM DM AHB Switch Local AHB Slave interface EPT Alloc 32 bits DPRAM System Clock Domain 16/8 bits USB Clock Domain PMC DS60001476B-page 1120  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.4 Typical Connection Figure 41-2: Board Schematic PIO (VBUS DETECT) 15k Ω (1) "B" Receptacle 1 = VBUS 2 = D3 = D+ 4 = GND 1 DHSDM/DFSDM 2 Shell = Shield (1) CRPB(2) 22k Ω 3 4 DHSDP/DFSDP 5K62 ± 1% Ω VBG (3) 10 pF GNDUTMII Note 1: The values shown on the 22 kΩ and 15 kΩ resistors are only valid with 3V3-supplied PIOs. 2: CRPB: Upstream Facing Port Bypass Capacitance of 1 µF to 10 µF (refer to “DC Electrical Characteristics” in Universal Serial Bus Specification Rev. 2) 3: 10 pF capacitor on VBG is a provision and may not be populated. 41.5 Product Dependencies 41.5.1 Power Management The UDPHS is not continuously clocked. For using the UDPHS, the programmer must first enable the UDPHS Clock in the Power Management Controller Peripheral Clock Enable Register (PMC_PCER). Then enable the PLL in the PMC UTMI Clock Configuration Register (CKGR_UCKR). Finally, enable BIAS in CKGR_UCKR. However, if the application does not require UDPHS operations, the UDPHS clock can be stopped when not needed and restarted later. 41.5.2 Interrupt Sources The UDPHS interrupt line is connected on one of the internal sources of the interrupt controller. Using the UDPHS interrupt requires the interrupt controller to be programmed first. Table 41-1: Peripheral IDs Instance ID UDPHS 42  2017 Microchip Technology Inc. DS60001476B-page 1121 SAMA5D2 SERIES 41.6 41.6.1 Functional Description UTMI Transceivers Sharing The High Speed USB Host Port A is shared with the High Speed USB Device port and connected to the second UTMI transceiver. The selection between Host Port A and USB Device is controlled by the UDPHS enable bit (EN_UDPHS) located in the UDPHS_CTRL register. Figure 41-3: USB Selection HS Transceiver HSIC HS Transceiver Transceiver EN_UDPHS 0 PB 41.6.2 PC 1 PA HS USB Host HS EHCI FS OHCI HS HSIC HS USB Device DMA DMA USB V2.0 High Speed Device Port Introduction The USB V2.0 High Speed Device Port provides communication services between host and attached USB devices. Each device is offered with a collection of communication flows (pipes) associated with each endpoint. Software on the host communicates with a USB Device through a set of communication flows. 41.6.3 USB V2.0 High Speed Transfer Types A communication flow is carried over one of four transfer types defined by the USB device. A device provides several logical communication pipes with the host. To each logical pipe is associated an endpoint. Transfer through a pipe belongs to one of the four transfer types: • Control Transfers: Used to configure a device at attach time and can be used for other device-specific purposes, including control of other pipes on the device. • Bulk Data Transfers: Generated or consumed in relatively large burst quantities and have wide dynamic latitude in transmission constraints. • Interrupt Data Transfers: Used for timely but reliable delivery of data, for example, characters or coordinates with human-perceptible echo or feedback response characteristics. • Isochronous Data Transfers: Occupy a prenegotiated amount of USB bandwidth with a prenegotiated delivery latency. (Also called streaming real time transfers.) As indicated below, transfers are sequential events carried out on the USB bus. Endpoints must be configured according to the transfer type they handle. DS60001476B-page 1122  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 41-2: USB Communication Flow Transfer Direction Bandwidth Endpoint Size Error Detection Retrying Control Bidirectional Not guaranteed 8, 16, 32, 64 Yes Automatic Isochronous Unidirectional Guaranteed 8–1024 Yes No Interrupt Unidirectional Not guaranteed 8–1024 Yes Yes Bulk Unidirectional Not guaranteed 8–512 Yes Yes 41.6.4 USB Transfer Event Definitions A transfer is composed of one or several transactions as shown in the following table. Table 41-3: USB Transfer Events Transfer Direction Type Transaction • Setup transaction → Data IN transactions → Status OUT transaction CONTROL (bidirectional) Control Transfer (1) • Setup transaction → Data OUT transactions → Status IN transaction • Setup transaction → Status IN transaction • Data IN transaction → Data IN transaction Bulk IN Transfer IN (device toward host) • Data IN transaction → Data IN transaction Interrupt IN Transfer Isochronous IN Transfer OUT (host toward device) (2) • Data IN transaction → Data IN transaction Bulk OUT Transfer • Data OUT transaction → Data OUT transaction Interrupt OUT Transfer • Data OUT transaction → Data OUT transaction Isochronous OUT Transfer (2) • Data OUT transaction → Data OUT transaction Note 1: Control transfer must use endpoints with one bank and can be aborted using a stall handshake. 2: Isochronous transfers must use endpoints configured with two or three banks. An endpoint handles all transactions related to the type of transfer for which it has been configured. Table 41-4: UDPHS Endpoint Description Mnemonic Nb Bank DMA High Band Width Max. Endpoint Size Endpoint Type 0 EPT_0 1 N N 64 Control 1 EPT_1 3 Y Y 1024 Ctrl/Bulk/Iso(1)/Interrupt 2 EPT_2 3 Y Y 1024 Ctrl/Bulk/Iso(1)/Interrupt 3 EPT_3 2 Y N 1024 Ctrl/Bulk/Iso(1)/Interrupt 4 EPT_4 2 Y N 1024 Ctrl/Bulk/Iso(1)/Interrupt 5 EPT_5 2 Y N 1024 Ctrl/Bulk/Iso(1)/Interrupt 6 EPT_6 2 Y N 1024 Ctrl/Bulk/Iso(1)/Interrupt 7 EPT_7 2 Y N 1024 Ctrl/Bulk/Iso(1)/Interrupt 8 EPT_8 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt 9 EPT_9 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt Endpoint #  2017 Microchip Technology Inc. DS60001476B-page 1123 SAMA5D2 SERIES Table 41-4: UDPHS Endpoint Description (Continued) Mnemonic Nb Bank DMA High Band Width Max. Endpoint Size Endpoint Type 10 EPT_10 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt 11 EPT_11 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt 12 EPT_12 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt 13 EPT_13 2 N N 1024 Ctrl/Bulk/Isov/Interrupt 14 EPT_14 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt 15 EPT_15 2 N N 1024 Ctrl/Bulk/Iso(1)/Interrupt Endpoint # Note 1: In Isochronous (Iso) mode, it is preferable that high bandwidth capability is available. The size of the internal DPRAM is 8 Kbytes. Suspend and resume are automatically detected by the UDPHS device, which notifies the processor by raising an interrupt. 41.6.5 USB V2.0 High Speed BUS Transactions Each transfer results in one or more transactions over the USB bus. There are five kinds of transactions flowing across the bus in packets: 1. 2. 3. 4. 5. Setup Transaction Data IN Transaction Data OUT Transaction Status IN Transaction Status OUT Transaction Figure 41-4: Control Read and Write Sequences Setup Stage Control Write Setup TX Setup Stage Control Read No Data Control Setup TX Data Stage Data OUT TX Status Stage Data OUT TX Data Stage Data IN TX Setup Stage Status Stage Setup TX Status IN TX Data IN TX Status IN TX Status Stage Status OUT TX A status IN or OUT transaction is identical to a data IN or OUT transaction. DS60001476B-page 1124  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.6.6 Endpoint Configuration The endpoint 0 is always a control endpoint, it must be programmed and active in order to be enabled when the End Of Reset interrupt occurs. To configure the endpoints: • Fill the configuration register (UDPHS_EPTCFG) with the endpoint size, direction (IN or OUT), type (CTRL, Bulk, IT, ISO) and the number of banks. • Fill the number of transactions (NB_TRANS) for isochronous endpoints. Note: For control endpoints the direction has no effect. • Verify that the EPT_MAPD flag is set. This flag is set if the endpoint size and the number of banks are correct compared to the FIFO maximum capacity and the maximum number of allowed banks. • Configure control flags of the endpoint and enable it in UDPHS_EPTCTLENBx according to Section 41.7.12 “UDPHS Endpoint Control Disable Register (Isochronous Endpoint)”. Control endpoints can generate interrupts and use only 1 bank. All endpoints (except endpoint 0) can be configured either as Bulk, Interrupt or Isochronous. Refer to Table 41-4: UDPHS Endpoint Description. The maximum packet size they can accept corresponds to the maximum endpoint size. Note: The endpoint size of 1024 is reserved for isochronous endpoints. The size of the DPRAM is 8 Kbytes. The DPR is shared by all active endpoints. The memory size required by the active endpoints must not exceed the size of the DPRAM. SIZE_DPRAM = SIZE _EPT0 + NB_BANK_EPT1 x SIZE_EPT1 + NB_BANK_EPT2 x SIZE_EPT2 + NB_BANK_EPT3 x SIZE_EPT3 + NB_BANK_EPT4 x SIZE_EPT4 + NB_BANK_EPT5 x SIZE_EPT5 + NB_BANK_EPT6 x SIZE_EPT6 +... (refer to 41.7.8 UDPHS Endpoint Configuration Register) If a user tries to configure endpoints with a size the sum of which is greater than the DPRAM, then the EPT_MAPD is not set. The application has access to the physical block of DPR reserved for the endpoint through a 64-Kbyte logical address space. The physical block of DPR allocated for the endpoint is remapped all along the 64-Kbyte logical address space. The application can write a 64-Kbyte buffer linearly.  2017 Microchip Technology Inc. DS60001476B-page 1125 SAMA5D2 SERIES Figure 41-5: Logical Address Space for DPR Access DPR 8 to 64 B 1 bank Logical address 8 to 64 B 64 KB EP0 8 to 1024 B 64 KB 8 to 1024 B 8 to 1024 B EP1 ... 64 KB EP2 8 to 1024 B 8 to1024 B x banks y banks z banks 8 to 1024 B 64 KB EP3 ... Configuration examples of UDPHS_EPTCTLx (UDPHS Endpoint Control Disable Register (Isochronous Endpoint)) for Bulk IN endpoint type follow below. • With DMA - AUTO_VALID: Automatically validate the packet and switch to the next bank. - EPT_ENABL: Enable endpoint. • Without DMA: - TXRDY: An interrupt is generated after each transmission. - EPT_ENABL: Enable endpoint. Configuration examples of Bulk OUT endpoint type follow below. • With DMA - AUTO_VALID: Automatically validate the packet and switch to the next bank. - EPT_ENABL: Enable endpoint. • Without DMA - RXRDY_TXKL: An interrupt is sent after a new packet has been stored in the endpoint FIFO. - EPT_ENABL: Enable endpoint. 41.6.7 DPRAM Management Endpoints can only be allocated in ascending order, from the endpoint 0 to the last endpoint to be allocated. The user shall therefore configure them in the same order. The allocation of an endpoint x starts when the Number of Banks field in the UDPHS Endpoint Configuration Register (UDPHS_EPTCFGx.BK_NUMBER) is different from zero. Then, the hardware allocates a memory area in the DPRAM and inserts it between the x-1 and x+1 endpoints. The x+1 endpoint memory window slides up and its data is lost. Note that the following endpoint memory windows (from x+2) do not slide. Disabling an endpoint, by writing a one to the Endpoint Disable bit in the UDPHS Endpoint Control Disable Register (UDPHS_EPTCTLDISx.EPT_DISABL), does not reset its configuration: • • • • Endpoint Banks (UDPHS_EPTCFGx.BK_NUMBER) Endpoint Size (UDPHS_EPTCFGx.EPT_SIZE) Endpoint Direction (UDPHS_EPTCFGx.EPT_DIR) Endpoint Type (UDPHS_EPTCFGx.EPT_TYPE) To free its memory, the user shall write a zero to the UDPHS_EPTCFGx.BK_NUMBER field. The x+1 endpoint memory window then slides down and its data is lost. Note that the following endpoint memory windows (from x+2) do not slide. DS60001476B-page 1126  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 41-6 illustrates the allocation and reorganization of the DPRAM in a typical example. Figure 41-6: Example of DPRAM Allocation and Reorganization Free Memory Free Memory Free Memory EPT5 EPT5 EPT5 Free Memory EPT5 Conflict EPT4 EPT4 EPT4 EPT3 EPT3 (always allocated) EPT4 EPT2 EPT2 EPT2 EPT2 EPT1 EPT1 EPT1 EPT1 EPT0 EPT0 EPT0 EPT0 Device: Device: EPT4 Lost Memory Device: Device: UDPHS_EPTCTLENBx.EPT_ENABL = 1 UDPHS_EPTCTLDIS3.EPT_DISABL = 1 UDPHS_EPTCFG3.BK_NUMBER = 0 UDPHS_EPTCFGx.BK_NUMBER 0 Endpoints 0..5 Enabled (Step 1) Endpoint 3 Disabled (Step 2) EPT3 (larger size) Endpoint 3 Memory Freed (Step 3) UDPHS_EPTCTLENB3.EPT_ENABL = 1 UDPHS_EPTCFG3.BK_NUMBER 0 Endpoint 3 Enabled (Step 4) DPRAM allocation sequence: 1. 2. 3. 4. The endpoints 0 to 5 are enabled, configured and allocated in ascending order. Each endpoint then owns a memory area in the DPRAM. The endpoint 3 is disabled, but its memory is kept allocated by the controller. In order to free its memory, its UDPHS_EPTCFGx.BK_NUMBER field is written to zero. The endpoint 4 memory window slides down, but the endpoint 5 does not move. If the user chooses to reconfigure the endpoint 3 with a larger size, the controller allocates a memory area after the endpoint 2 memory area and automatically slides up the endpoint 4 memory window. The endpoint 5 does not move and a memory conflict appears as the memory windows of the endpoints 4 and 5 overlap. The data of these endpoints is potentially lost. Note 1: There is no way the data of the endpoint 0 can be lost (except if it is de-allocated) as the memory allocation and de-allocation may affect only higher endpoints. 2: Deactivating then reactivating the same endpoint with the same configuration only modifies temporarily the controller DPRAM pointer and size for this endpoint. Nothing changes in the DPRAM, higher endpoints seem not to 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 endpoint. 3: When the user writes a value different from zero to the UDPHS_EPTCFGx.BK_NUMBER field, the Endpoint Mapped bit (UDPHS_EPTCFGx.EPT_MAPD) is set only if the configured size and number of banks are correct as compared to the endpoint maximal allowed values and to the maximal FIFO size (i.e., the DPRAM size). The UDPHS_EPTCFGx.EPT_MAPD value does not consider memory allocation conflicts. 41.6.8 Transfer With DMA USB packets of any length may be transferred when required by the UDPHS device. These transfers always feature sequential addressing. Packet data AHB bursts may be locked on a DMA buffer basis for drastic overall AHB bus bandwidth performance boost with paged memories. These clock-cycle consuming memory row (or bank) changes will then likely not occur, or occur only once instead of several times, during a single big USB packet DMA transfer in case another AHB master addresses the memory. The locked bursts result in up to 128word single-cycle unbroken AHB bursts for bulk endpoints and 256-word single-cycle unbroken bursts for isochronous endpoints. This maximum burst length is then controlled by the lowest programmed USB endpoint size (EPT_SIZE field in the UDPHS_EPTCFGx register) and DMA Size (BUFF_LENGTH field in the UDPHS_DMACONTROLx register).  2017 Microchip Technology Inc. DS60001476B-page 1127 SAMA5D2 SERIES The USB 2.0 device average throughput may be up to nearly 60 Mbyte/s. Its internal slave average access latency decreases as burst length increases due to the 0 wait-state side effect of unchanged endpoints. If at least 0 wait-state word burst capability is also provided by the external DMA AHB bus slaves, each of both DMA AHB busses need less than 50% bandwidth allocation for full USB 2.0 bandwidth usage at 30 MHz, and less than 25% at 60 MHz. The UDPHS DMA Channel Transfer Descriptor is described in Section 41.7.21 “UDPHS DMA Channel Transfer Descriptor”. Note: In case of debug, be careful to address the DMA to an SRAM address even if a remap is done. Figure 41-7: Example of DMA Chained List Transfer Descriptor UDPHS Registers (Current Transfer Descriptor) Next Descriptor Address DMA Channel Address Transfer Descriptor UDPHS Next Descriptor DMA Channel Control Next Descriptor Address DMA Channel Address DMA Channel Address Transfer Descriptor DMA Channel Control Next Descriptor Address DMA Channel Control DMA Channel Address DMA Channel Control Null Memory Area Data Buff 1 Data Buff 2 Data Buff 3 41.6.9 Transfer Without DMA Important: If the DMA is not to be used, it is necessary to disable it, otherwise it can be enabled by previous versions of software without warning. If this should occur, the DMA can process data before an interrupt without knowledge of the user. DS60001476B-page 1128  2017 Microchip Technology Inc. SAMA5D2 SERIES The recommended means to disable DMA are as follows: // Reset IP UDPHS AT91C_BASE_UDPHS->UDPHS_CTRL &= ~AT91C_UDPHS_EN_UDPHS; AT91C_BASE_UDPHS->UDPHS_CTRL |= AT91C_UDPHS_EN_UDPHS; // With OR without DMA !!! for( i=1; iUDPHS_IPFEATURES & AT91C_UDPHS_DMA_CHANNEL_NBR)>>4); i++ ) { // RESET endpoint canal DMA: // DMA stop channel command AT91C_BASE_UDPHS->UDPHS_DMA[i].UDPHS_DMACONTROL = 0; // STOP command // Disable endpoint AT91C_BASE_UDPHS->UDPHS_EPT[i].UDPHS_EPTCTLDIS |= 0XFFFFFFFF; // Reset endpoint config AT91C_BASE_UDPHS->UDPHS_EPT[i].UDPHS_EPTCTLCFG = 0; // Reset DMA channel (Buff count and Control field) AT91C_BASE_UDPHS->UDPHS_DMA[i].UDPHS_DMACONTROL = 0x02; // NON STOP command // Reset DMA channel 0 (STOP) AT91C_BASE_UDPHS->UDPHS_DMA[i].UDPHS_DMACONTROL = 0; // STOP command // Clear DMA channel status (read the register for clear it) AT91C_BASE_UDPHS->UDPHS_DMA[i].UDPHS_DMASTATUS = AT91C_BASE_UDPHS->UDPHS_DMA[i].UDPHS_DMASTATUS; } 41.6.10 41.6.10.1 Handling Transactions with USB V2.0 Device Peripheral Setup Transaction The setup packet is valid in the DPR while RX_SETUP is set. Once RX_SETUP is cleared by the application, the UDPHS accepts the next packets sent over the device endpoint. When a valid setup packet is accepted by the UDPHS: • • • • The UDPHS device automatically acknowledges the setup packet (sends an ACK response) Payload data is written in the endpoint Sets the RX_SETUP interrupt The BYTE_COUNT field in the UDPHS_EPTSTAx register is updated An endpoint interrupt is generated while RX_SETUP in the UDPHS_EPTSTAx register is not cleared. This interrupt is carried out to the microcontroller if interrupts are enabled for this endpoint. Thus, firmware must detect RX_SETUP polling UDPHS_EPTSTAx or catching an interrupt, read the setup packet in the FIFO, then clear the RX_SETUP bit in the UDPHS_EPTCLRSTA register to acknowledge the setup stage. If STALL_SNT was set to 1, then this bit is automatically reset when a setup token is detected by the device. Then, the device still accepts the setup stage. (Refer to Section 41.6.10.5 “STALL”). 41.6.10.2 NYET NYET is a High Speed only handshake. It is returned by a High Speed endpoint as part of the PING protocol. High Speed devices must support an improved NAK mechanism for Bulk OUT and control endpoints (except setup stage). This mechanism allows the device to tell the host whether it has sufficient endpoint space for the next OUT transfer (refer to USB 2.0 spec 8.5.1 NAK Limiting via Ping Flow Control). The NYET/ACK response to a High Speed Bulk OUT transfer and the PING response are automatically handled by hardware in the UDPHS_EPTCTLx register (except when the user wants to force a NAK response by using the NYET_DIS bit). If the endpoint responds instead to the OUT/DATA transaction with an NYET handshake, this means that the endpoint accepted the data but does not have room for another data payload. The host controller must return to using a PING token until the endpoint indicates it has space available.  2017 Microchip Technology Inc. DS60001476B-page 1129 SAMA5D2 SERIES Figure 41-8: NYET Example with Two Endpoint Banks data 0 ACK data 1 NYET t = 125 μs t=0 Bank 1 E Bank 0 F 41.6.10.3 PING t = 250 μs Bank 1 F Bank 1 F Bank 0 E' Bank 0 E ACK data 0 NYET t = 375 μs Bank 1 F Bank 0 E PING t = 500 μs Bank 1 F Bank 0 F NACK PING t = 625 μs Bank 1 E' Bank 0 F ACK E: empty E': begin to empty F: full Bank 1 E Bank 0 F Data IN • Bulk IN or Interrupt IN Data IN packets are sent by the device during the data or the status stage of a control transfer or during an (interrupt/bulk/isochronous) IN transfer. Data buffers are sent packet by packet under the control of the application or under the control of the DMA channel. There are three ways for an application to transfer a buffer in several packets over the USB: • • • • packet by packet (refer to “Bulk IN or Interrupt IN: Sending a Packet Under Application Control (Device to Host)” below) 64 Kbytes (refer to “Bulk IN or Interrupt IN: Sending a Packet Under Application Control (Device to Host)” below) DMA (refer to “Bulk IN or Interrupt IN: Sending a Buffer Using DMA (Device to Host)” below) Bulk IN or Interrupt IN: Sending a Packet Under Application Control (Device to Host) The application can write one or several banks. A simple algorithm can be used by the application to send packets regardless of the number of banks associated to the endpoint. Algorithm Description for Each Packet: • The application waits for the TXRDY flag to be cleared in the UDPHS_EPTSTAx register before it can perform a write access to the DPR. • The application writes one USB packet of data in the DPR through the 64 Kbytes endpoint logical memory window. • The application sets TXRDY flag in the UDPHS_EPTSETSTAx register. The application is notified that it is possible to write a new packet to the DPR by the TXRDY interrupt. This interrupt can be enabled or masked by setting the TXRDY bit in the UDPHS_EPTCTLENB/UDPHS_EPTCTLDIS register. Algorithm Description to Fill Several Packets: Using the previous algorithm, the application is interrupted for each packet. It is possible to reduce the application overhead by writing linearly several banks at the same time. The AUTO_VALID bit in the UDPHS_EPTCTLx must be set by writing the AUTO_VALID bit in the UDPHS_EPTCTLENBx register. The auto-valid-bank mechanism allows the transfer of data (IN and OUT) without the intervention of the CPU. This means that bank validation (set TXRDY or clear the RXRDY_TXKL bit) is done by hardware. • The application checks the BUSY_BANK_STA field in the UDPHS_EPTSTAx register. The application must wait that at least one bank is free. • The application writes a number of bytes inferior to the number of free DPR banks for the endpoint. Each time the application writes the last byte of a bank, the TXRDY signal is automatically set by the UDPHS. • If the last packet is incomplete (i.e., the last byte of the bank has not been written) the application must set the TXRDY bit in the UDPHS_EPTSETSTAx register. The application is notified that all banks are free, so that it is possible to write another burst of packets by the BUSY_BANK interrupt. This interrupt can be enabled or masked by setting the BUSY_BANK flag in the UDPHS_EPTCTLENB and UDPHS_EPTCTLDIS registers. This algorithm must not be used for isochronous transfer. In this case, the ping-pong mechanism does not operate. A Zero Length Packet can be sent by setting just the TXRDY flag in the UDPHS_EPTSETSTAx register. • Bulk IN or Interrupt IN: Sending a Buffer Using DMA (Device to Host) The UDPHS integrates a DMA host controller. This DMA controller can be used to transfer a buffer from the memory to the DPR or from the DPR to the processor memory under the UDPHS control. The DMA can be used for all transfer types except control transfer. Example DMA configuration: 1. Program UDPHS_DMAADDRESS x with the address of the buffer that should be transferred. DS60001476B-page 1130  2017 Microchip Technology Inc. SAMA5D2 SERIES 2. 3. - - Enable the interrupt of the DMA in UDPHS_IEN Program UDPHS_ DMACONTROLx: Size of buffer to send: size of the buffer to be sent to the host. END_B_EN: The endpoint can validate the packet (according to the values programmed in the AUTO_VALID and SHRT_PCKT fields of UDPHS_EPTCTLx.) (Refer to Section 41.7.12 “UDPHS Endpoint Control Disable Register (Isochronous Endpoint)” and Figure 41-13) END_BUFFIT: generate an interrupt when the BUFF_COUNT in UDPHS_DMASTATUSx reaches 0. CHANN_ENB: Run and stop at end of buffer The auto-valid-bank mechanism allows the transfer of data (IN & OUT) without the intervention of the CPU. This means that bank validation (set TXRDY or clear the RXRDY_TXKL bit) is done by hardware. A transfer descriptor can be used. Instead of programming the register directly, a descriptor should be programmed and the address of this descriptor is then given to UDPHS_DMANXTDSC to be processed after setting the LDNXT_DSC field (Load Next Descriptor Now) in UDPHS_DMACONTROLx register. The structure that defines this transfer descriptor must be aligned. Each buffer to be transferred must be described by a DMA Transfer descriptor (refer to Section 41.7.21 “UDPHS DMA Channel Transfer Descriptor”). Transfer descriptors are chained. Before executing transfer of the buffer, the UDPHS may fetch a new transfer descriptor from the memory address pointed by the UDPHS_DMANXTDSCx register. Once the transfer is complete, the transfer status is updated in the UDPHS_DMASTATUSx register. To chain a new transfer descriptor with the current DMA transfer, the DMA channel must be stopped. To do so, INTDIS_DMA and TXRDY may be set in the UDPHS_EPTCTLENBx register. It is also possible for the application to wait for the completion of all transfers. In this case the LDNXT_DSC bit in the last transfer descriptor UDPHS_DMACONTROLx register must be set to 0 and the CHANN_ENB bit set to 1. Then the application can chain a new transfer descriptor. The INTDIS_DMA can be used to stop the current DMA transfer if an enabled interrupt is triggered. This can be used to stop DMA transfers in case of errors. The application can be notified at the end of any buffer transfer (ENB_BUFFIT bit in the UDPHS_DMACONTROLx register). Figure 41-9: Data IN Transfer for Endpoint with One Bank Prevous Data IN TX USB Bus Packets Token IN Data IN 1 TXRDY Flag (UDPHS_EPTSTAx) Set by firmware Microcontroller Loads Data in FIFO ACK Token IN NAK Cleared by hardware Data is Sent on USB Bus Token IN Data IN 2 Set by firmware ACK Cleared by hardware Interrupt Pending TX_COMPLT Flag (UDPHS_EPTSTAx) Payload in FIFO Set by hardware DPR access by firmware FIFO Content  2017 Microchip Technology Inc. Interrupt Pending Data IN 1 Load in progress Cleared by firmware Cleared by firmware DPR access by hardware Data IN 2 DS60001476B-page 1131 SAMA5D2 SERIES Figure 41-10: Data IN Transfer for Endpoint with Two Banks Microcontroller Load Data IN Bank 0 USB Bus Packets Microcontroller Load Data IN Bank 1 UDPHS Device Send Bank 0 Token IN Set by firmware, Data payload written in FIFO Bank 0 Data IN ACK Set by firmware, Data payload written in FIFO Bank 1 Interrupt Pending TX_COMPLT Flag (UDPHS_EPTSTAx) Set by hardware Set by hardware Interrupt cleared by firmware Written by microcontroller Written by microcontroller Read by USB Device FIFO (DPR) Bank1 Written by microcontroller Read by UDPHS Device Data IN Followed By Status OUT Transfer at the End of a Control Transfer Device Sends the Last Data Payload to Host USB Bus Packets ACK Cleared by hardware Data payload fully transmitted Virtual TXRDY bank 1 (UDPHS_EPTSTAx) Figure 41-11: Data IN Token IN Cleared by hardware switch to next bank Virtual TXRDY bank 0 (UDPHS_EPTSTAx) FIFO (DPR) Bank 0 Microcontroller Load Data IN Bank 0 UDPHS Device Send Bank 1 Token IN Data IN Device Sends a Status OUT to Host ACK Token OUT Data OUT (ZLP) ACK Token OUT Data OUT (ZLP) ACK Interrupt Pending RXRDY (UDPHS_EPTSTAx) Set by hardware Cleared by firmware TX_COMPLT (UDPHS_EPTSTAx) Set by hardware Note: Cleared by firmware A NAK handshake is always generated at the first status stage token. DS60001476B-page 1132  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 41-12: Data OUT Followed by Status IN Transfer Host Sends the Last Data Payload to the Device USB Bus Packets Token OUT Device Sends a Status IN to the Host Data OUT ACK Token IN Data IN ACK Interrupt Pending RXRDY (UDPHS_EPTSTAx) Cleared by firmware Set by hardware TXRDY (UDPHS_EPTSTAx) Set by firmware Note: Clear by hardware Before proceeding to the status stage, the software should determine that there is no risk of extra data from the host (data stage). If not certain (non-predictable data stage length), then the software should wait for a NAK-IN interrupt before proceeding to the status stage. This precaution should be taken to avoid collision in the FIFO. Figure 41-13: Autovalid with DMA Bank (system) Write Bank 0 Bank 1 write bank 0 write bank 1 bank 0 is full Bank 1 Bank 0 Bank 1 write bank 0 bank 1 is full bank 0 is full Bank 0 IN data 0 Bank (usb) Bank 0 IN data 1 Bank 1 IN data 0 Bank 0 Bank 1 Virtual TXRDY Bank 0 Virtual TXRDY Bank 1 TXRDY (Virtual 0 & Virtual 1) Note: In the illustration above Autovalid validates a bank as full, although this might not be the case, in order to continue processing data and to send to DMA. • Isochronous IN  2017 Microchip Technology Inc. DS60001476B-page 1133 SAMA5D2 SERIES Isochronous-IN is used to transmit a stream of data whose timing is implied by the delivery rate. Isochronous transfer provides periodic, continuous communication between host and device. It guarantees bandwidth and low latencies appropriate for telephony, audio, video, etc. If the endpoint is not available (TXRDY_TRER = 0), then the device does not answer to the host. An ERR_FL_ISO interrupt is generated in the UDPHS_EPTSTAx register and once enabled, then sent to the CPU. The STALL_SNT command bit is not used for an ISO-IN endpoint. • High Bandwidth Isochronous Endpoint Handling: IN Example For high bandwidth isochronous endpoints, the DMA can be programmed with the number of transactions (BUFF_LENGTH field in UDPHS_DMACONTROLx) and the system should provide the required number of packets per microframe, otherwise, the host will notice a sequencing problem. A response should be made to the first token IN recognized inside a microframe under the following conditions: • If at least one bank has been validated, the correct DATAx corresponding to the programmed Number Of Transactions per Microframe (NB_TRANS) should be answered. In case of a subsequent missed or corrupted token IN inside the microframe, the USB 2.0 Core available data bank(s) that should normally have been transmitted during that microframe shall be flushed at its end. If this flush occurs, an error condition is flagged (ERR_FLUSH is set in UDPHS_EPTSTAx). • If no bank is validated yet, the default DATA0 ZLP is answered and underflow is flagged (ERR_FL_ISO is set in UDPHS_EPTSTAx). Then, no data bank is flushed at microframe end. • If no data bank has been validated at the time when a response should be made for the second transaction of NB_TRANS = 3 transactions microframe, a DATA1 ZLP is answered and underflow is flagged (ERR_FL_ISO is set in UDPHS_EPTSTAx). If and only if remaining untransmitted banks for that microframe are available at its end, they are flushed and an error condition is flagged (ERR_FLUSH is set in UDPHS_EPTSTAx). • If no data bank has been validated at the time when a response should be made for the last programmed transaction of a microframe, a DATA0 ZLP is answered and underflow is flagged (ERR_FL_ISO is set in UDPHS_EPTSTAx). If and only if the remaining untransmitted data bank for that microframe is available at its end, it is flushed and an error condition is flagged (ERR_FLUSH is set in UDPHS_EPTSTAx). • If at the end of a microframe no valid token IN has been recognized, no data bank is flushed and no error condition is reported. At the end of a microframe in which at least one data bank has been transmitted, if less than NB_TRANS banks have been validated for that microframe, an error condition is flagged (ERR_TRANS is set in UDPHS_EPTSTAx). Cases of Error (in UDPHS_EPTSTAx) • ERR_FL_ISO: There was no data to transmit inside a microframe, so a ZLP is answered by default. • ERR_FLUSH: At least one packet has been sent inside the microframe, but the number of token INs received is less than the number of transactions actually validated (TXRDY_TRER) and likewise with the NB_TRANS programmed. • ERR_TRANS: At least one packet has been sent inside the microframe, but the number of token INs received is less than the number of programmed NB_TRANS transactions and the packets not requested were not validated. • ERR_FL_ISO + ERR_FLUSH: At least one packet has been sent inside the microframe, but the data has not been validated in time to answer one of the following token INs. • ERR_FL_ISO + ERR_TRANS: At least one packet has been sent inside the microframe, but the data has not been validated in time to answer one of the following token INs and the data can be discarded at the microframe end. • ERR_FLUSH + ERR_TRANS: The first token IN has been answered and it was the only one received, a second bank has been validated but not the third, whereas NB_TRANS was waiting for three transactions. • ERR_FL_ISO + ERR_FLUSH + ERR_TRANS: The first token IN has been treated, the data for the second Token IN was not available in time, but the second bank has been validated before the end of the microframe. The third bank has not been validated, but three transactions have been set in NB_TRANS. 41.6.10.4 Data OUT • Bulk OUT or Interrupt OUT Like data IN, data OUT packets are sent by the host during the data or the status stage of control transfer or during an interrupt/bulk/ isochronous OUT transfer. Data buffers are sent packet by packet under the control of the application or under the control of the DMA channel. • Bulk OUT or Interrupt OUT: Receiving a Packet Under Application Control (Host to Device) Algorithm Description for Each Packet: • The application enables an interrupt on RXRDY_TXKL. • When an interrupt on RXRDY_TXKL is received, the application knows that UDPHS_EPTSTAx register BYTE_COUNT bytes have been received. • The application reads the BYTE_COUNT bytes from the endpoint. DS60001476B-page 1134  2017 Microchip Technology Inc. SAMA5D2 SERIES • The application clears RXRDY_TXKL. Note: If the application does not know the size of the transfer, it may not be a good option to use AUTO_VALID. Because if a zerolength-packet is received, the RXRDY_TXKL is automatically cleared by the AUTO_VALID hardware and if the endpoint interrupt is triggered, the software will not find its originating flag when reading the UDPHS_EPTSTAx register. Algorithm to Fill Several Packets: • The application enables the interrupts of BUSY_BANK and AUTO_VALID. • When a BUSY_BANK interrupt is received, the application knows that all banks available for the endpoint have been filled. Thus, the application can read all banks available. If the application does not know the size of the receive buffer, instead of using the BUSY_BANK interrupt, the application must use RXRDY_TXKL. • Bulk OUT or Interrupt OUT: Sending a Buffer Using DMA (Host To Device) To use the DMA setting, the AUTO_VALID field is mandatory. See “Bulk IN or Interrupt IN: Sending a Buffer Using DMA (Device to Host)” for more information. DMA Configuration Example: 1. 2. 3. - First program UDPHS_DMAADDRESSx with the address of the buffer that should be transferred. Enable the interrupt of the DMA in UDPHS_IEN Program the DMA Channelx Control Register: Size of buffer to be sent. END_B_EN: Can be used for OUT packet truncation (discarding of unbuffered packet data) at the end of DMA buffer. END_BUFFIT: Generate an interrupt when BUFF_COUNT in the UDPHS_DMASTATUSx register reaches 0. END_TR_EN: End of transfer enable, the UDPHS device can put an end to the current DMA transfer, in case of a short packet. END_TR_IT: End of transfer interrupt enable, an interrupt is sent after the last USB packet has been transferred by the DMA, if the USB transfer ended with a short packet. (Beneficial when the receive size is unknown.) CHANN_ENB: Run and stop at end of buffer. For OUT transfer, the bank will be automatically cleared by hardware when the application has read all the bytes in the bank (the bank is empty). Note 1: When a zero-length-packet is received, RXRDY_TXKL bit in UDPHS_EPTSTAx is cleared automatically by AUTO_VALID, and the application knows of the end of buffer by the presence of the END_TR_IT. 2: If the host sends a zero-length packet, and the endpoint is free, then the device sends an ACK. No data is written in the endpoint, the RXRDY_TXKL interrupt is generated, and the BYTE_COUNT field in UDPHS_EPTSTAx is null. Figure 41-14: Data OUT Transfer for Endpoint with One Bank Host Sends Data Payload USB Bus Packets Token OUT Data OUT 1 Token OUT Set by hardware Data OUT 1 Written by UDPHS Device  2017 Microchip Technology Inc. ACK Data OUT 2 Host Resends the Next Data Payload NAK Data OUT 2 Token OUT ACK Interrupt Pending RXRDY (UDPHS_EPTSTAx) FIFO (DPR) Content Microcontroller Transfers Data Host Sends the Next Data Payload Data OUT 1 Microcontroller read Cleared by firmware, Data payload written in FIFO Data OUT 2 Written by UDPHS Device DS60001476B-page 1135 SAMA5D2 SERIES Figure 41-15: Data OUT Transfer for an Endpoint with Two Banks Microcontroller reads Data 1 in bank 0, Host sends second data payload Host sends first data payload USB Bus Packets Virtual RXRDY Bank 0 Token OUT Data OUT 1 ACK Token OUT Data OUT 2 Virtual RXRDY Bank 1 Token OUT Data OUT 3 Cleared by firmware Interrupt pending Set by hardware, Data payload written in FIFO endpoint bank 0 ACK Microcontroller reads Data 2 in bank 1, Host sends third data payload Set by hardware Data payload written in FIFO endpoint bank 1 Cleared by firmware Interrupt pending RXRDY = (virtual bank 0 | virtual bank 1) (UDPHS_EPTSTAx) FIFO (DPR) Bank 0 Data OUT 1 Write by UDPHS Device FIFO (DPR) Bank 1 Data OUT 1 Data OUT 3 Read by microcontroller Write in progress Data OUT 2 Write by hardware Data OUT 2 Read by microcontroller • High Bandwidth Isochronous Endpoint OUT USB 2.0 supports individual High Speed isochronous endpoints that require data rates up to 192 Mb/s (24 MB/s): 3x1024 data bytes per microframe. To support such a rate, two or three banks may be used to buffer the three consecutive data packets. The microcontroller (or the DMA) should be able to empty the banks very rapidly (at least 24 MB/s on average). NB_TRANS field in UDPHS_EPTCFGx register = Number Of Transactions per Microframe. If NB_TRANS > 1 then it is High Bandwidth. DS60001476B-page 1136  2017 Microchip Technology Inc. SAMA5D2 SERIES Example: • If NB_TRANS = 3, the sequence should be either - MData0 - MData0/Data1 - MData0/Data1/Data2 • If NB_TRANS = 2, the sequence should be either - MData0 - MData0/Data1 • If NB_TRANS = 1, the sequence should be - Data0 Figure 41-16: USB Bus Transactions Bank Management, Example of Three Transactions per Microframe MDATA0 MDATA1 DATA2 MDATA0 MDATA1 DATA2 USB line t = 52.5 μs (40% of 125 μs) t=0 RXRDY Microcontroller FIFO (DPR) Access Read Bank 1 Read Bank 2 t = 125 μs RXRDY Read Bank 3 Read Bank 1 • Isochronous Endpoint Handling: OUT Example The user can ascertain the bank status (free or busy), and the toggle sequencing of the data packet for each bank with the UDPHS_EPTSTAx register in the three fields as follows: • TOGGLESQ_STA: PID of the data stored in the current bank • CURBK: Number of the bank currently being accessed by the microcontroller. • BUSY_BANK_STA: Number of busy bank This is particularly useful in case of a missing data packet. If the inter-packet delay between the OUT token and the Data is greater than the USB standard, then the ISO-OUT transaction is ignored. (Payload data is not written, no interrupt is generated to the CPU.) If there is a data CRC (Cyclic Redundancy Check) error, the payload is, none the less, written in the endpoint. The ERR_CRC_NTR flag is set in UDPHS_EPTSTAx register. If the endpoint is already full, the packet is not written in the DPRAM. The ERR_FL_ISO flag is set in UDPHS_EPTSTAx. If the payload data is greater than the maximum size of the endpoint, then the ERR_OVFLW flag is set. It is the task of the CPU to manage this error. The data packet is written in the endpoint (except the extra data). If the host sends a Zero Length Packet, and the endpoint is free, no data is written in the endpoint, the RXRDY_TXKL flag is set, and the BYTE_COUNT field in UDPHS_EPTSTAx register is null. The FRCESTALL command bit is unused for an isochronous endpoint. Otherwise, payload data is written in the endpoint, the RXRDY_TXKL interrupt is generated and the BYTE_COUNT in UDPHS_EPTSTAx register is updated. 41.6.10.5 STALL STALL is returned by a function in response to an IN token or after the data phase of an OUT or in response to a PING transaction. STALL indicates that a function is unable to transmit or receive data, or that a control pipe request is not supported. • OUT To stall an endpoint, set the FRCESTALL bit in UDPHS_EPTSETSTAx register and after the STALL_SNT flag has been set, set the TOGGLE_SEG bit in the UDPHS_EPTCLRSTAx register. • IN Set the FRCESTALL bit in UDPHS_EPTSETSTAx register.  2017 Microchip Technology Inc. DS60001476B-page 1137 SAMA5D2 SERIES Figure 41-17: Stall Handshake Data OUT Transfer USB Bus Packets Data OUT Token OUT Stall PID FRCESTALL Cleared by firmware Interrupt Pending Set by firmware STALL_SNT Set by hardware Figure 41-18: Cleared by firmware Stall Handshake Data IN Transfer USB Bus Packets Token IN Stall PID FRCESTALL Cleared by firmware Set by firmware Interrupt Pending STALL_SNT Set by hardware 41.6.11 Cleared by firmware Speed Identification The high speed reset is managed by hardware. At the connection, the host makes a reset which could be a classic reset (full speed) or a high speed reset. At the end of the reset process (full or high), the ENDRESET interrupt is generated. Then the CPU should read the SPEED bit in UDPHS_INTSTAx to ascertain the speed mode of the device. 41.6.12 USB V2.0 High Speed Global Interrupt Interrupts are defined in Section 41.7.3 “UDPHS Interrupt Enable Register” (UDPHS_IEN) and in Section 41.7.4 “UDPHS Interrupt Status Register” (UDPHS_INTSTA). 41.6.13 Endpoint Interrupts Interrupts are enabled in UDPHS_IEN (refer to Section 41.7.3 “UDPHS Interrupt Enable Register”) and individually masked in UDPHS_EPTCTLENBx (refer to Section 41.7.9 “UDPHS Endpoint Control Enable Register (Control, Bulk, Interrupt Endpoints)”). Table 41-5: Endpoint Interrupt Source Masks SHRT_PCKT Short Packet Interrupt BUSY_BANK Busy Bank Interrupt NAK_OUT NAKOUT Interrupt NAK_IN/ERR_FLUSH NAKIN/Error Flush Interrupt STALL_SNT/ERR_CRC_NTR Stall Sent/CRC error/Number of Transaction Error Interrupt RX_SETUP/ERR_FL_ISO Received SETUP/Error Flow Interrupt TXRDY_TRER TX Packet Read/Transaction Error Interrupt DS60001476B-page 1138  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 41-5: Endpoint Interrupt Source Masks TX_COMPLT Transmitted IN Data Complete Interrupt RXRDY_TXKL Received OUT Data Interrupt ERR_OVFLW Overflow Error Interrupt MDATA_RX MDATA Interrupt DATAX_RX DATAx Interrupt  2017 Microchip Technology Inc. DS60001476B-page 1139 SAMA5D2 SERIES Figure 41-19: UDPHS Interrupt Control Interface (UDPHS_IEN) Global IT mask Global IT sources DET_SUSPD MICRO_SOF USB Global IT Sources INT_SOF ENDRESET WAKE_UP ENDOFRSM UPSTR_RES (UDPHS_EPTCTLENBx) SHRT_PCKT EP mask BUSY_BANK EP sources NAK_OUT (UDPHS_IEN) EPT_0 husb2dev interrupt NAK_IN/ERR_FLUSH STALL_SNT/ER_CRC_NTR EPT0 IT Sources RX_SETUP/ERR_FL_ISO TXRDY_TRER TX_COMPLT RXRDY_TXKL ERR_OVFLW MDATA_RX DATAX_RX (UDPHS_IEN) EPT_x EP mask EP sources (UDPHS_EPTCTLx) INTDIS_DMA EPT1-6 IT Sources disable DMA channelx request (UDPHS_DMACONTROLx) mask (UDPHS_IEN) DMA_x END_BUFFIT mask DMA CH x END_TR_IT mask DESC_LD_IT DS60001476B-page 1140  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.6.14 41.6.14.1 Power Modes Controlling Device States A USB device has several possible states. Refer to Chapter 9 (USB Device Framework) of the Universal Serial Bus Specification, Rev 2.0. Figure 41-20: UDPHS Device State Diagram Attached Hub Reset Hub or Configured Deconfigured Bus Inactive Powered Suspended Bus Activity Power Interruption Reset Bus Inactive Suspended Default Bus Activity Reset Address Assigned Bus Inactive Suspended Address Bus Activity Device Deconfigured Device Configured Bus Inactive Configured Suspended Bus Activity Movement from one state to another depends on the USB bus state or on standard requests sent through control transactions via the default endpoint (endpoint 0). After a period of bus inactivity, the USB device enters Suspend mode. Accepting Suspend/Resume requests from the USB host is mandatory. Constraints in Suspend mode are very strict for bus-powered applications; devices may not consume more than 500 µA on the USB bus. While in Suspend mode, the host may wake up a device by sending a resume signal (bus activity) or a USB device may send a wakeup request to the host, e.g., waking up a PC by moving a USB mouse. The wakeup feature is not mandatory for all devices and must be negotiated with the host. 41.6.14.2 Not Powered State Self powered devices can detect 5V VBUS using a PIO. When the device is not connected to a host, device power consumption can be reduced by the DETACH bit in UDPHS_CTRL. Disabling the transceiver is automatically done. HSDM, HSDP, FSDP and FSDP lines are tied to GND pulldowns integrated in the hub downstream ports.  2017 Microchip Technology Inc. DS60001476B-page 1141 SAMA5D2 SERIES 41.6.14.3 Entering Attached State When no device is connected, the USB FSDP and FSDM signals are tied to GND by 15 KΩ pulldowns integrated in the hub downstream ports. When a device is attached to an hub downstream port, the device connects a 1.5 KΩ pullup on FSDP. The USB bus line goes into IDLE state, FSDP is pulled up by the device 1.5 KΩ resistor to 3.3V and FSDM is pulled down by the 15 KΩ resistor to GND of the host. After pullup connection, the device enters the powered state. The transceiver remains disabled until bus activity is detected. In case of low power consumption need, the device can be stopped. When the device detects the VBUS, the software must enable the USB transceiver by enabling the EN_UDPHS bit in UDPHS_CTRL register. The software can detach the pullup by setting DETACH bit in UDPHS_CTRL register. 41.6.14.4 From Powered State to Default State (Reset) After its connection to a USB host, the USB device waits for an end-of-bus reset. The unmasked flag ENDRESET is set in the UDPHS_IEN register and an interrupt is triggered. Once the ENDRESET interrupt has been triggered, the device enters Default State. In this state, the UDPHS software must: • Enable the default endpoint, setting the EPT_ENABL flag in the UDPHS_EPTCTLENB[0] register and, optionally, enabling the interrupt for endpoint 0 by writing 1 in EPT_0 of the UDPHS_IEN register. The enumeration then begins by a control transfer. • Configure the Interrupt Mask Register which has been reset by the USB reset detection • Enable the transceiver. In this state, the EN_UDPHS bit in UDPHS_CTRL register must be enabled. 41.6.14.5 From Default State to Address State (Address Assigned) After a Set Address standard device request, the USB host peripheral enters the address state. Warning: before the device enters address state, it must achieve the Status IN transaction of the control transfer, i.e., the UDPHS device sets its new address once the TX_COMPLT flag in the UDPHS_EPTCTL[0] register has been received and cleared. To move to address state, the driver software sets the DEV_ADDR field and the FADDR_EN flag in the UDPHS_CTRL register. 41.6.14.6 From Address State to Configured State (Device Configured) Once a valid Set Configuration standard request has been received and acknowledged, the device enables endpoints corresponding to the current configuration. This is done by setting the BK_NUMBER, EPT_TYPE, EPT_DIR and EPT_SIZE fields in the UDPHS_EPTCFGx registers and enabling them by setting the EPT_ENABL flag in the UDPHS_EPTCTLENBx registers, and, optionally, enabling corresponding interrupts in the UDPHS_IEN register. DS60001476B-page 1142  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.6.14.7 Entering Suspend State (Bus Activity) When a Suspend (no bus activity on the USB bus) is detected, the DET_SUSPD signal in the UDPHS_STA register is set. This triggers an interrupt if the corresponding bit is set in the UDPHS_IEN register. This flag is cleared by writing to the UDPHS_CLRINT register. Then the device enters Suspend mode. In this state bus powered devices must drain less than 500 µA from the 5V VBUS. As an example, the microcontroller switches to slow clock, disables the PLL and main oscillator, and goes into Idle mode. It may also switch off other devices on the board. The UDPHS device peripheral clocks can be switched off. Resume event is asynchronously detected. 41.6.14.8 Receiving a Host Resume In Suspend mode, a resume event on the USB bus line is detected asynchronously, transceiver and clocks disabled (however, the pullup should not be removed). Once the resume is detected on the bus, the signal WAKE_UP in the UDPHS_INTSTA is set. It may generate an interrupt if the corresponding bit in the UDPHS_IEN register is set. This interrupt may be used to wake up the core, enable PLL and main oscillators and configure clocks. 41.6.14.9 Sending an External Resume In Suspend State it is possible to wake up the host by sending an external resume. The device waits at least 5 ms after being entered in Suspend State before sending an external resume. The device must force a K state from 1 to 15 ms to resume the host. 41.6.15 Test Mode A device must support the TEST_MODE feature when in the Default, Address or Configured High Speed device states. TEST_MODE can be: • • • • Test_J Test_K Test_Packet Test_SEO_NAK (Refer to Section 41.7.7 “UDPHS Test Register” for definitions of each test mode.) const char test_packet_buffer[] = { 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, 0xAA,0xAA,0xAA,0xAA,0xAA,0xAA,0xAA,0xAA, 0xEE,0xEE,0xEE,0xEE,0xEE,0xEE,0xEE,0xEE, 0xFE,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF, 0x7F,0xBF,0xDF,0xEF,0xF7,0xFB,0xFD, 0xFC,0x7E,0xBF,0xDF,0xEF,0xF7,0xFB,0xFD,0x7E };  2017 Microchip Technology Inc. // // // // // // JKJKJKJK * 9 JJKKJJKK * 8 JJKKJJKK * 8 JJJJJJJKKKKKKK * 8 JJJJJJJK * 8 {JKKKKKKK * 10}, JK DS60001476B-page 1143 SAMA5D2 SERIES 41.7 USB High Speed Device Port (UDPHS) User Interface Table 41-6: Register Mapping Offset Register Name Access Reset 0x00 UDPHS Control Register UDPHS_CTRL Read/Write 0x0000_0200 0x04 UDPHS Frame Number Register UDPHS_FNUM Read-only 0x0000_0000 0x08–0x0C Reserved – – – 0x10 UDPHS Interrupt Enable Register UDPHS_IEN Read/Write 0x0000_0010 0x14 UDPHS Interrupt Status Register UDPHS_INTSTA Read-only 0x0000_0000 0x18 UDPHS Clear Interrupt Register UDPHS_CLRINT Write-only – 0x1C UDPHS Endpoints Reset Register UDPHS_EPTRST Write-only – 0x20–0xDC Reserved – – – 0xE0 UDPHS Test Register UDPHS_TST Read/Write 0x0000_0000 0xE4–0xFC Reserved – – – 0x100 + endpoint * 0x20 + 0x00 UDPHS Endpoint Configuration Register UDPHS_EPTCFG Read/Write 0x0000_0000 0x100 + endpoint * 0x20 + 0x04 UDPHS Endpoint Control Enable Register UDPHS_EPTCTLENB Write-only – 0x100 + endpoint * 0x20 + 0x08 UDPHS Endpoint Control Disable Register UDPHS_EPTCTLDIS Write-only – 0x100 + endpoint * 0x20 + 0x0C UDPHS Endpoint Control Register UDPHS_EPTCTL Read-only 0x0000_0000(1) 0x100 + endpoint * 0x20 + 0x10 Reserved (for endpoint) – – – 0x100 + endpoint * 0x20 + 0x14 UDPHS Endpoint Set Status Register UDPHS_EPTSETSTA Write-only – 0x100 + endpoint * 0x20 + 0x18 UDPHS Endpoint Clear Status Register UDPHS_EPTCLRSTA Write-only – UDPHS_EPTSTA Read-only 0x0000_0040 – – – UDPHS_DMANXTDSC 0x100 + endpoint * 0x20 + 0x1C UDPHS Endpoint Status Register (2) Registers 0x120–0x2FC UDPHS Endpoint1 to 15 0x300 + channel * 0x10 + 0x00 UDPHS DMA Next Descriptor Address Register Read/Write 0x0000_0000 0x300 + channel * 0x10 + 0x04 UDPHS DMA Channel Address Register UDPHS_DMAADDRESS Read/Write 0x0000_0000 0x300 + channel * 0x10 + 0x08 UDPHS DMA Channel Control Register UDPHS_DMACONTRO L Read/Write 0x0000_0000 0x300 + channel * 0x10 + 0x0C UDPHS DMA Channel Status Register UDPHS_DMASTATUS Read/Write 0x0000_0000 – – – 0x310–0x36C DMA Channel1 to 6 (3) Registers Note 1: The reset value for UDPHS_EPTCTL0 is 0x0000_0001. 2: The addresses for the UDPHS Endpoint registers shown here are for UDPHS Endpoint0. The structure of this group of registers is repeated successively for each endpoint according to the sequence of endpoint registers located between 0x120 and 0x2FC. 3: The DMA channel index refers to the corresponding EP number. When no DMA channel is assigned to one EP, the associated registers are reserved. This is the case for EP0, so DMA Channel 0 registers are reserved. DS60001476B-page 1144  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.1 UDPHS Control Register Name: UDPHS_CTRL Address: 0xFC02C000 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 PULLD_DIS 10 REWAKEUP 9 DETACH 8 EN_UDPHS 7 FADDR_EN 6 5 4 3 DEV_ADDR 2 1 0 DEV_ADDR: UDPHS Address (cleared upon USB reset) This field contains the default address (0) after power-up or UDPHS bus reset (read), or it is written with the value set by a SET_ADDRESS request received by the device firmware (write). FADDR_EN: Function Address Enable (cleared upon USB reset) 0: Device is not in address state (read), or only the default function address is used (write). 1: Device is in address state (read), or this bit is set by the device firmware after a successful status phase of a SET_ADDRESS transaction (write). When set, the only address accepted by the UDPHS controller is the one stored in the UDPHS Address field. It will not be cleared afterwards by the device firmware. It is cleared by hardware on hardware reset, or when UDPHS bus reset is received. EN_UDPHS: UDPHS Enable 0: UDPHS is disabled (read), or this bit disables and resets the UDPHS controller (write). Switch the host to UTMI. 1: UDPHS is enabled (read), or this bit enables the UDPHS controller (write). Switch the host to UTMI. DETACH: Detach Command 0: UDPHS is attached (read), or this bit pulls up the DP line (attach command) (write). 1: UDPHS is detached, UTMI transceiver is suspended (read), or this bit simulates a detach on the UDPHS line and forces the UTMI transceiver into suspend state (Suspend M = 0) (write). Refer to “PULLD_DIS: Pulldown Disable (cleared upon USB reset)” . REWAKEUP: Send Remote Wakeup (cleared upon USB reset) 0: Remote Wakeup is disabled (read), or this bit has no effect (write). 1: Remote Wakeup is enabled (read), or this bit forces an external interrupt on the UDPHS controller for Remote Wakeup purposes. An Upstream Resume is sent only after the UDPHS bus has been in SUSPEND state for at least 5 ms. This bit is automatically cleared by hardware at the end of the Upstream Resume.  2017 Microchip Technology Inc. DS60001476B-page 1145 SAMA5D2 SERIES PULLD_DIS: Pulldown Disable (cleared upon USB reset) When set, there is no pulldown on DP & DM. (DM Pulldown = DP Pulldown = 0). Note: If the DETACH bit is also set, device DP & DM are left in high impedance state. (Refer to “DETACH: Detach Command” . ) DETACH PULLD_DIS DP DM Condition 0 0 Pullup Pulldown Not recommended 0 1 Pullup High impedance state VBUS present 1 0 Pulldown Pulldown No VBUS 1 1 High impedance state High impedance state VBUS present & software disconnect DS60001476B-page 1146  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.2 UDPHS Frame Number Register Name: UDPHS_FNUM Address: 0xFC02C004 Access: Read-only 31 FNUM_ERR 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 12 11 10 FRAME_NUMBER 9 8 7 6 5 FRAME_NUMBER 4 3 1 MICRO_FRAME_NUM 0 2 MICRO_FRAME_NUM: Microframe Number (cleared upon USB reset) Number of the received microframe (0 to 7) in one frame.This field is reset at the beginning of each new frame (1 ms). One microframe is received each 125 microseconds (1 ms/8). FRAME_NUMBER: Frame Number as defined in the Packet Field Formats (cleared upon USB reset) This field is provided in the last received SOF packet (refer to INT_SOF in the UDPHS Interrupt Status Register). FNUM_ERR: Frame Number CRC Error (cleared upon USB reset) This bit is set by hardware when a corrupted Frame Number in Start of Frame packet (or Micro SOF) is received. This bit and the INT_SOF (or MICRO_SOF) interrupt are updated at the same time.  2017 Microchip Technology Inc. DS60001476B-page 1147 SAMA5D2 SERIES 41.7.3 UDPHS Interrupt Enable Register Name: UDPHS_IEN Address: 0xFC02C010 Access: Read/Write 31 DMA_7 30 DMA_6 29 DMA_5 28 DMA_4 27 DMA_3 26 DMA_2 25 DMA_1 24 – 23 EPT_15 22 EPT_14 21 EPT_13 20 EPT_12 19 EPT_11 18 EPT_10 17 EPT_9 16 EPT_8 15 EPT_7 14 EPT_6 13 EPT_5 12 EPT_4 11 EPT_3 10 EPT_2 9 EPT_1 8 EPT_0 7 UPSTR_RES 6 ENDOFRSM 5 WAKE_UP 4 ENDRESET 3 INT_SOF 2 MICRO_SOF 1 DET_SUSPD 0 – DET_SUSPD: Suspend Interrupt Enable (cleared upon USB reset) 0: Disable Suspend Interrupt. 1: Enable Suspend Interrupt. MICRO_SOF: Micro-SOF Interrupt Enable (cleared upon USB reset) 0: Disable Micro-SOF Interrupt. 1: Enable Micro-SOF Interrupt. INT_SOF: SOF Interrupt Enable (cleared upon USB reset) 0: Disable SOF Interrupt. 1: Enable SOF Interrupt. ENDRESET: End Of Reset Interrupt Enable (cleared upon USB reset) 0: Disable End Of Reset Interrupt. 1: Enable End Of Reset Interrupt. Automatically enabled after USB reset. WAKE_UP: Wake Up CPU Interrupt Enable (cleared upon USB reset) 0: Disable Wakeup CPU Interrupt. 1: Enable Wakeup CPU Interrupt. ENDOFRSM: End Of Resume Interrupt Enable (cleared upon USB reset) 0: Disable Resume Interrupt. 1: Enable Resume Interrupt. UPSTR_RES: Upstream Resume Interrupt Enable (cleared upon USB reset) 0: Disable Upstream Resume Interrupt. 1: Enable Upstream Resume Interrupt. DS60001476B-page 1148  2017 Microchip Technology Inc. SAMA5D2 SERIES EPT_x: Endpoint x Interrupt Enable (cleared upon USB reset) 0: Disable the interrupts for this endpoint. 1: Enable the interrupts for this endpoint. DMA_x: DMA Channel x Interrupt Enable (cleared upon USB reset) 0: Disable the interrupts for this channel. 1: Enable the interrupts for this channel.  2017 Microchip Technology Inc. DS60001476B-page 1149 SAMA5D2 SERIES 41.7.4 UDPHS Interrupt Status Register Name: UDPHS_INTSTA Address: 0xFC02C014 Access: Read-only 31 DMA_7 30 DMA_6 29 DMA_5 28 DMA_4 27 DMA_3 26 DMA_2 25 DMA_1 24 – 23 EPT_15 22 EPT_14 21 EPT_13 20 EPT_12 19 EPT_11 18 EPT_10 17 EPT_9 16 EPT_8 15 EPT_7 14 EPT_6 13 EPT_5 12 EPT_4 11 EPT_3 10 EPT_2 9 EPT_1 8 EPT_0 7 UPSTR_RES 6 ENDOFRSM 5 WAKE_UP 4 ENDRESET 3 INT_SOF 2 MICRO_SOF 1 DET_SUSPD 0 SPEED SPEED: Speed Status 0: Reset by hardware when the hardware is in Full Speed mode. 1: Set by hardware when the hardware is in High Speed mode. DET_SUSPD: Suspend Interrupt 0: Cleared by setting the DET_SUSPD bit in UDPHS_CLRINT register. 1: Set by hardware when a UDPHS Suspend (Idle bus for three frame periods, a J state for 3 ms) is detected. This triggers a UDPHS interrupt when the DET_SUSPD bit is set in UDPHS_IEN register. MICRO_SOF: Micro Start Of Frame Interrupt 0: Cleared by setting the MICRO_SOF bit in UDPHS_CLRINT register. 1: Set by hardware when an UDPHS micro start of frame PID (SOF) has been detected (every 125 us) or synthesized by the macro. This triggers a UDPHS interrupt when the MICRO_SOF bit is set in UDPHS_IEN. In case of detected SOF, the MICRO_FRAME_NUM field in UDPHS_FNUM register is incremented and the FRAME_NUMBER field does not change. Note: The Micro Start Of Frame Interrupt (MICRO_SOF), and the Start Of Frame Interrupt (INT_SOF) are not generated at the same time. INT_SOF: Start Of Frame Interrupt 0: Cleared by setting the INT_SOF bit in UDPHS_CLRINT. 1: Set by hardware when an UDPHS Start Of Frame PID (SOF) has been detected (every 1 ms) or synthesized by the macro. This triggers a UDPHS interrupt when the INT_SOF bit is set in UDPHS_IEN register. In case of detected SOF, in High Speed mode, the MICRO_FRAME_NUMBER field is cleared in UDPHS_FNUM register and the FRAME_NUMBER field is updated. ENDRESET: End Of Reset Interrupt 0: Cleared by setting the ENDRESET bit in UDPHS_CLRINT. 1: Set by hardware when an End Of Reset has been detected by the UDPHS controller. This triggers a UDPHS interrupt when the ENDRESET bit is set in UDPHS_IEN. DS60001476B-page 1150  2017 Microchip Technology Inc. SAMA5D2 SERIES WAKE_UP: Wake Up CPU Interrupt 0: Cleared by setting the WAKE_UP bit in UDPHS_CLRINT. 1: Set by hardware when the UDPHS controller is in SUSPEND state and is re-activated by a filtered non-idle signal from the UDPHS line (not by an upstream resume). This triggers a UDPHS interrupt when the WAKE_UP bit is set in UDPHS_IEN register. When receiving this interrupt, the user has to enable the device controller clock prior to operation. Note: this interrupt is generated even if the device controller clock is disabled. ENDOFRSM: End Of Resume Interrupt 0: Cleared by setting the ENDOFRSM bit in UDPHS_CLRINT. 1: Set by hardware when the UDPHS controller detects a good end of resume signal initiated by the host. This triggers a UDPHS interrupt when the ENDOFRSM bit is set in UDPHS_IEN. UPSTR_RES: Upstream Resume Interrupt 0: Cleared by setting the UPSTR_RES bit in UDPHS_CLRINT. 1: Set by hardware when the UDPHS controller is sending a resume signal called “upstream resume”. This triggers a UDPHS interrupt when the UPSTR_RES bit is set in UDPHS_IEN. EPT_x: Endpoint x Interrupt (cleared upon USB reset) 0: Reset when the UDPHS_EPTSTAx interrupt source is cleared. 1: Set by hardware when an interrupt is triggered by the UDPHS_EPTSTAx register and this endpoint interrupt is enabled by the EPT_x bit in UDPHS_IEN. DMA_x: DMA Channel x Interrupt 0: Reset when the UDPHS_DMASTATUSx interrupt source is cleared. 1: Set by hardware when an interrupt is triggered by the DMA Channelx and this endpoint interrupt is enabled by the DMA_x bit in UDPHS_IEN.  2017 Microchip Technology Inc. DS60001476B-page 1151 SAMA5D2 SERIES 41.7.5 UDPHS Clear Interrupt Register Name: UDPHS_CLRINT Address: 0xFC02C018 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 UPSTR_RES 6 ENDOFRSM 5 WAKE_UP 4 ENDRESET 3 INT_SOF 2 MICRO_SOF 1 DET_SUSPD 0 – DET_SUSPD: Suspend Interrupt Clear 0: No effect. 1: Clear the DET_SUSPD bit in UDPHS_INTSTA. MICRO_SOF: Micro Start Of Frame Interrupt Clear 0: No effect. 1: Clear the MICRO_SOF bit in UDPHS_INTSTA. INT_SOF: Start Of Frame Interrupt Clear 0: No effect. 1: Clear the INT_SOF bit in UDPHS_INTSTA. ENDRESET: End Of Reset Interrupt Clear 0: No effect. 1: Clear the ENDRESET bit in UDPHS_INTSTA. WAKE_UP: Wake Up CPU Interrupt Clear 0: No effect. 1: Clear the WAKE_UP bit in UDPHS_INTSTA. ENDOFRSM: End Of Resume Interrupt Clear 0: No effect. 1: Clear the ENDOFRSM bit in UDPHS_INTSTA. UPSTR_RES: Upstream Resume Interrupt Clear 0: No effect. 1: Clear the UPSTR_RES bit in UDPHS_INTSTA. DS60001476B-page 1152  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.6 UDPHS Endpoints Reset Register Name: UDPHS_EPTRST Address: 0xFC02C01C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 EPT_15 14 EPT_14 13 EPT_13 12 EPT_12 11 EPT_11 10 EPT_10 9 EPT_9 8 EPT_8 7 EPT_7 6 EPT_6 5 EPT_5 4 EPT_4 3 EPT_3 2 EPT_2 1 EPT_1 0 EPT_0 EPT_x: Endpoint x Reset 0: No effect. 1: Reset the Endpointx state. Setting this bit clears all bits in the Endpoint status UDPHS_EPTSTAx register except the TOGGLESQ_STA field.  2017 Microchip Technology Inc. DS60001476B-page 1153 SAMA5D2 SERIES 41.7.7 UDPHS Test Register Name: UDPHS_TST Address: 0xFC02C0E0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 OPMODE2 4 TST_PKT 3 TST_K 2 TST_J 1 0 SPEED_CFG SPEED_CFG: Speed Configuration Value Name Description 0 NORMAL Normal mode: The macro is in Full Speed mode, ready to make a High Speed identification, if the host supports it and then to automatically switch to High Speed mode. 1 – Reserved 2 HIGH_SPEED Force High Speed: Set this value to force the hardware to work in High Speed mode. Only for debug or test purpose. 3 FULL_SPEED Force Full Speed: Set this value to force the hardware to work only in Full Speed mode. In this configuration, the macro will not respond to a High Speed reset handshake. TST_J: Test J Mode 0: No effect. 1: Set to send the J state on the UDPHS line. This enables the testing of the high output drive level on the D+ line. TST_K: Test K Mode 0: No effect. 1: Set to send the K state on the UDPHS line. This enables the testing of the high output drive level on the D- line. TST_PKT: Test Packet Mode 0: No effect. 1: Set to repetitively transmit the packet stored in the current bank. This enables the testing of rise and fall times, eye patterns, jitter, and any other dynamic waveform specifications. OPMODE2: OpMode2 0: No effect. 1: Set to force the OpMode signal (UTMI interface) to “10”, to disable the bit-stuffing and the NRZI encoding. Note: For the Test mode, Test_SE0_NAK (refer to Universal Serial Bus Specification, Revision 2.0: 7.1.20, Test Mode Support). Force the device in High Speed mode, and configure a bulk-type endpoint. Do not fill this endpoint for sending NAK to the host. Upon command, a port’s transceiver must enter the High Speed Receive mode and remain in that mode until the exit action is taken. This enables the testing of output impedance, low level output voltage and loading characteristics. In addition, while in this mode, upstream facing ports (and only upstream facing ports) must respond to any IN token packet with a NAK handshake (only if the packet CRC is determined to be correct) within the normal allowed device response time. This enables testing of the device squelch level circuitry and, additionally, provides a general purpose stimulus/response test for basic functional testing. DS60001476B-page 1154  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.8 UDPHS Endpoint Configuration Register Name: UDPHS_EPTCFGx [x=0..15] Address: 0xFC02C100 [0], 0xFC02C120 [1], 0xFC02C140 [2], 0xFC02C160 [3], 0xFC02C180 [4], 0xFC02C1A0 [5], 0xFC02C1C0 [6], 0xFC02C1E0 [7], 0xFC02C200 [8], 0xFC02C220 [9], 0xFC02C240 [10], 0xFC02C260 [11], 0xFC02C280 [12], 0xFC02C2A0 [13], 0xFC02C2C0 [14], 0xFC02C2E0 [15] Access: Read/Write 31 EPT_MAPD 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 6 5 4 3 EPT_DIR 2 1 EPT_SIZE 7 BK_NUMBER EPT_TYPE 8 NB_TRANS 0 EPT_SIZE: Endpoint Size (cleared upon USB reset) Set this field according to the endpoint size(1) in bytes (refer to Section 41.6.6 “Endpoint Configuration”). Value Name Description 0 8 8 bytes 1 16 16 bytes 2 32 32 bytes 3 64 64 bytes 4 128 128 bytes 5 256 256 bytes 6 512 512 bytes 7 1024 1024 bytes Note 1: 1024 bytes is only for isochronous endpoint. EPT_DIR: Endpoint Direction (cleared upon USB reset) 0: Clear this bit to configure OUT direction for Bulk, Interrupt and Isochronous endpoints. 1: Set this bit to configure IN direction for Bulk, Interrupt and Isochronous endpoints. For Control endpoints this bit has no effect and should be left at zero. EPT_TYPE: Endpoint Type (cleared upon USB reset) Set this field according to the endpoint type (refer to Section 41.6.6 “Endpoint Configuration”). (Endpoint 0 should always be configured as control) Value Name Description 0 CTRL8 Control endpoint 1 ISO Isochronous endpoint 2 BULK Bulk endpoint 3 INT Interrupt endpoint BK_NUMBER: Number of Banks (cleared upon USB reset)  2017 Microchip Technology Inc. DS60001476B-page 1155 SAMA5D2 SERIES Set this field according to the endpoint’s number of banks (refer to Section 41.6.6 “Endpoint Configuration”). Value Name Description 0 0 Zero bank, the endpoint is not mapped in memory 1 1 One bank (bank 0) 2 2 Double bank (Ping-Pong: bank0/bank1) 3 3 Triple bank (bank0/bank1/bank2) NB_TRANS: Number Of Transaction per Microframe (cleared upon USB reset) The Number of transactions per microframe is set by software. Note: Meaningful for high bandwidth isochronous endpoint only. EPT_MAPD: Endpoint Mapped (cleared upon USB reset) 0: The user should reprogram the register with correct values. 1: Set by hardware when the endpoint size (EPT_SIZE) and the number of banks (BK_NUMBER) are correct regarding: – The FIFO max capacity (FIFO_MAX_SIZE in UDPHS_IPFEATURES register) – The number of endpoints/banks already allocated – The number of allowed banks for this endpoint DS60001476B-page 1156  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.9 UDPHS Endpoint Control Enable Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTCTLENBx [x=0..15] Address: 0xFC02C104 [0], 0xFC02C124 [1], 0xFC02C144 [2], 0xFC02C164 [3], 0xFC02C184 [4], 0xFC02C1A4 [5], 0xFC02C1C4 [6], 0xFC02C1E4 [7], 0xFC02C204 [8], 0xFC02C224 [9], 0xFC02C244 [10], 0xFC02C264 [11], 0xFC02C284 [12], 0xFC02C2A4 [13], 0xFC02C2C4 [14], 0xFC02C2E4 [15] Access: Write-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 15 NAK_OUT 14 NAK_IN 13 STALL_SNT 12 RX_SETUP 11 TXRDY 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 7 – 6 – 5 – 4 NYET_DIS 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_ENABL This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Control Register (Control, Bulk, Interrupt Endpoints)” . EPT_ENABL: Endpoint Enable 0: No effect. 1: Enable endpoint according to the device configuration. AUTO_VALID: Packet Auto-Valid Enable 0: No effect. 1: Enable this bit to automatically validate the current packet and switch to the next bank for both IN and OUT transfers. INTDIS_DMA: Interrupts Disable DMA 0: No effect. 1: If set, when an enabled endpoint-originated interrupt is triggered, the DMA request is disabled. NYET_DIS: NYET Disable (Only for High Speed Bulk OUT endpoints) 0: No effect. 1: Forces an ACK response to the next High Speed Bulk OUT transfer instead of a NYET response. ERR_OVFLW: Overflow Error Interrupt Enable 0: No effect. 1: Enable Overflow Error Interrupt. RXRDY_TXKL: Received OUT Data Interrupt Enable 0: No effect. 1: Enable Received OUT Data Interrupt.  2017 Microchip Technology Inc. DS60001476B-page 1157 SAMA5D2 SERIES TX_COMPLT: Transmitted IN Data Complete Interrupt Enable 0: No effect. 1: Enable Transmitted IN Data Complete Interrupt. TXRDY: TX Packet Ready Interrupt Enable 0: No effect. 1: Enable TX Packet Ready/Transaction Error Interrupt. RX_SETUP: Received SETUP 0: No effect. 1: Enable RX_SETUP Interrupt. STALL_SNT: Stall Sent Interrupt Enable 0: No effect. 1: Enable Stall Sent Interrupt. NAK_IN: NAKIN Interrupt Enable 0: No effect. 1: Enable NAKIN Interrupt. NAK_OUT: NAKOUT Interrupt Enable 0: No effect. 1: Enable NAKOUT Interrupt. BUSY_BANK: Busy Bank Interrupt Enable 0: No effect. 1: Enable Busy Bank Interrupt. SHRT_PCKT: Short Packet Send/Short Packet Interrupt Enable For OUT endpoints: 0: No effect. 1: Enable Short Packet Interrupt. For IN endpoints: Guarantees short packet at end of DMA Transfer if the UDPHS_DMACONTROLx register END_B_EN and UDPHS_EPTCTLx register AUTOVALID bits are also set. DS60001476B-page 1158  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.10 UDPHS Endpoint Control Enable Register (Isochronous Endpoints) Name: UDPHS_EPTCTLENBx [x=0..15] (ISOENDPT) Address: 0xFC02C104 [0], 0xFC02C124 [1], 0xFC02C144 [2], 0xFC02C164 [3], 0xFC02C184 [4], 0xFC02C1A4 [5], 0xFC02C1C4 [6], 0xFC02C1E4 [7], 0xFC02C204 [8], 0xFC02C224 [9], 0xFC02C244 [10], 0xFC02C264 [11], 0xFC02C284 [12], 0xFC02C2A4 [13], 0xFC02C2C4 [14], 0xFC02C2E4 [15] Access: Write-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 11 TXRDY_TRER 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_ENABL 15 – 7 MDATA_RX 14 13 12 ERR_FLUSH ERR_CRC_NTR ERR_FL_ISO 6 DATAX_RX 5 – 4 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Control Register (Isochronous Endpoint)” . EPT_ENABL: Endpoint Enable 0: No effect. 1: Enable endpoint according to the device configuration. AUTO_VALID: Packet Auto-Valid Enable 0: No effect. 1: Enable this bit to automatically validate the current packet and switch to the next bank for both IN and OUT transfers. INTDIS_DMA: Interrupts Disable DMA 0: No effect. 1: If set, when an enabled endpoint-originated interrupt is triggered, the DMA request is disabled. DATAX_RX: DATAx Interrupt Enable (Only for high bandwidth Isochronous OUT endpoints) 0: No effect. 1: Enable DATAx Interrupt. MDATA_RX: MDATA Interrupt Enable (Only for high bandwidth Isochronous OUT endpoints) 0: No effect. 1: Enable MDATA Interrupt. ERR_OVFLW: Overflow Error Interrupt Enable 0: No effect. 1: Enable Overflow Error Interrupt.  2017 Microchip Technology Inc. DS60001476B-page 1159 SAMA5D2 SERIES RXRDY_TXKL: Received OUT Data Interrupt Enable 0: No effect. 1: Enable Received OUT Data Interrupt. TX_COMPLT: Transmitted IN Data Complete Interrupt Enable 0: No effect. 1: Enable Transmitted IN Data Complete Interrupt. TXRDY_TRER: TX Packet Ready/Transaction Error Interrupt Enable 0: No effect. 1: Enable TX Packet Ready/Transaction Error Interrupt. ERR_FL_ISO: Error Flow Interrupt Enable 0: No effect. 1: Enable Error Flow ISO Interrupt. ERR_CRC_NTR: ISO CRC Error/Number of Transaction Error Interrupt Enable 0: No effect. 1: Enable Error CRC ISO/Error Number of Transaction Interrupt. ERR_FLUSH: Bank Flush Error Interrupt Enable 0: No effect. 1: Enable Bank Flush Error Interrupt. BUSY_BANK: Busy Bank Interrupt Enable 0: No effect. 1: Enable Busy Bank Interrupt. SHRT_PCKT: Short Packet Send/Short Packet Interrupt Enable For OUT endpoints: 0: No effect. 1: Enable Short Packet Interrupt. For IN endpoints: Guarantees short packet at end of DMA Transfer if the UDPHS_DMACONTROLx register END_B_EN and UDPHS_EPTCTLx register AUTOVALID bits are also set. DS60001476B-page 1160  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.11 UDPHS Endpoint Control Disable Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTCTLDISx [x=0..15] Address: 0xFC02C108 [0], 0xFC02C128 [1], 0xFC02C148 [2], 0xFC02C168 [3], 0xFC02C188 [4], 0xFC02C1A8 [5], 0xFC02C1C8 [6], 0xFC02C1E8 [7], 0xFC02C208 [8], 0xFC02C228 [9], 0xFC02C248 [10], 0xFC02C268 [11], 0xFC02C288 [12], 0xFC02C2A8 [13], 0xFC02C2C8 [14], 0xFC02C2E8 [15] Access: Write-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 15 NAK_OUT 14 NAK_IN 13 STALL_SNT 12 RX_SETUP 11 TXRDY 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 7 – 6 – 5 – 4 NYET_DIS 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_DISABL This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Control Register (Control, Bulk, Interrupt Endpoints)” . EPT_DISABL: Endpoint Disable 0: No effect. 1: Disable endpoint. AUTO_VALID: Packet Auto-Valid Disable 0: No effect. 1: Disable this bit to not automatically validate the current packet. INTDIS_DMA: Interrupts Disable DMA 0: No effect. 1: Disable the “Interrupts Disable DMA”. NYET_DIS: NYET Enable (Only for High Speed Bulk OUT endpoints) 0: No effect. 1: Let the hardware handle the handshake response for the High Speed Bulk OUT transfer. ERR_OVFLW: Overflow Error Interrupt Disable 0: No effect. 1: Disable Overflow Error Interrupt. RXRDY_TXKL: Received OUT Data Interrupt Disable 0: No effect. 1: Disable Received OUT Data Interrupt.  2017 Microchip Technology Inc. DS60001476B-page 1161 SAMA5D2 SERIES TX_COMPLT: Transmitted IN Data Complete Interrupt Disable 0: No effect. 1: Disable Transmitted IN Data Complete Interrupt. TXRDY: TX Packet Ready Interrupt Disable 0: No effect. 1: Disable TX Packet Ready/Transaction Error Interrupt. RX_SETUP: Received SETUP Interrupt Disable 0: No effect. 1: Disable RX_SETUP Interrupt. STALL_SNT: Stall Sent Interrupt Disable 0: No effect. 1: Disable Stall Sent Interrupt. NAK_IN: NAKIN Interrupt Disable 0: No effect. 1: Disable NAKIN Interrupt. NAK_OUT: NAKOUT Interrupt Disable 0: No effect. 1: Disable NAKOUT Interrupt. BUSY_BANK: Busy Bank Interrupt Disable 0: No effect. 1: Disable Busy Bank Interrupt. SHRT_PCKT: Short Packet Interrupt Disable For OUT endpoints: 0: No effect. 1: Disable Short Packet Interrupt. For IN endpoints: Never automatically add a zero length packet at end of DMA transfer. DS60001476B-page 1162  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.12 UDPHS Endpoint Control Disable Register (Isochronous Endpoint) Name: UDPHS_EPTCTLDISx [x=0..15] (ISOENDPT) Address: 0xFC02C108 [0], 0xFC02C128 [1], 0xFC02C148 [2], 0xFC02C168 [3], 0xFC02C188 [4], 0xFC02C1A8 [5], 0xFC02C1C8 [6], 0xFC02C1E8 [7], 0xFC02C208 [8], 0xFC02C228 [9], 0xFC02C248 [10], 0xFC02C268 [11], 0xFC02C288 [12], 0xFC02C2A8 [13], 0xFC02C2C8 [14], 0xFC02C2E8 [15] Access: Write-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 11 TXRDY_TRER 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_DISABL 15 – 7 MDATA_RX 14 13 12 ERR_FLUSH ERR_CRC_NTR ERR_FL_ISO 6 DATAX_RX 5 – 4 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Control Register (Isochronous Endpoint)” . EPT_DISABL: Endpoint Disable 0: No effect. 1: Disable endpoint. AUTO_VALID: Packet Auto-Valid Disable 0: No effect. 1: Disable this bit to not automatically validate the current packet. INTDIS_DMA: Interrupts Disable DMA 0: No effect. 1: Disable the “Interrupts Disable DMA”. DATAX_RX: DATAx Interrupt Disable (Only for High Bandwidth Isochronous OUT endpoints) 0: No effect. 1: Disable DATAx Interrupt. MDATA_RX: MDATA Interrupt Disable (Only for High Bandwidth Isochronous OUT endpoints) 0: No effect. 1: Disable MDATA Interrupt. ERR_OVFLW: Overflow Error Interrupt Disable 0: No effect. 1: Disable Overflow Error Interrupt.  2017 Microchip Technology Inc. DS60001476B-page 1163 SAMA5D2 SERIES RXRDY_TXKL: Received OUT Data Interrupt Disable 0: No effect. 1: Disable Received OUT Data Interrupt. TX_COMPLT: Transmitted IN Data Complete Interrupt Disable 0: No effect. 1: Disable Transmitted IN Data Complete Interrupt. TXRDY_TRER: TX Packet Ready/Transaction Error Interrupt Disable 0: No effect. 1: Disable TX Packet Ready/Transaction Error Interrupt. ERR_FL_ISO: Error Flow Interrupt Disable 0: No effect. 1: Disable Error Flow ISO Interrupt. ERR_CRC_NTR: ISO CRC Error/Number of Transaction Error Interrupt Disable 0: No effect. 1: Disable Error CRC ISO/Error Number of Transaction Interrupt. ERR_FLUSH: bank flush error Interrupt Disable 0: No effect. 1: Disable Bank Flush Error Interrupt. BUSY_BANK: Busy Bank Interrupt Disable 0: No effect. 1: Disable Busy Bank Interrupt. SHRT_PCKT: Short Packet Interrupt Disable For OUT endpoints: 0: No effect. 1: Disable Short Packet Interrupt. For IN endpoints: Never automatically add a zero length packet at end of DMA transfer. DS60001476B-page 1164  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.13 UDPHS Endpoint Control Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTCTLx [x=0..15] Address: 0xFC02C10C [0], 0xFC02C12C [1], 0xFC02C14C [2], 0xFC02C16C [3], 0xFC02C18C [4], 0xFC02C1AC [5], 0xFC02C1CC [6], 0xFC02C1EC [7], 0xFC02C20C [8], 0xFC02C22C [9], 0xFC02C24C [10], 0xFC02C26C [11], 0xFC02C28C [12], 0xFC02C2AC [13], 0xFC02C2CC [14], 0xFC02C2EC [15] Access: Read-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 15 NAK_OUT 14 NAK_IN 13 STALL_SNT 12 RX_SETUP 11 TXRDY 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 7 – 6 – 5 – 4 NYET_DIS 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_ENABL This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . EPT_ENABL: Endpoint Enable (cleared upon USB reset) 0: The endpoint is disabled according to the device configuration. Endpoint 0 should always be enabled after a hardware or UDPHS bus reset and participate in the device configuration. 1: The endpoint is enabled according to the device configuration. AUTO_VALID: Packet Auto-Valid Enabled (Not for CONTROL Endpoints) (cleared upon USB reset) Set this bit to automatically validate the current packet and switch to the next bank for both IN and OUT endpoints. For IN Transfer: If this bit is set, the UDPHS_EPTSTAx register TXRDY bit is set automatically when the current bank is full and at the end of DMA buffer if the UDPHS_DMACONTROLx register END_B_EN bit is set. The user may still set the UDPHS_EPTSTAx register TXRDY bit if the current bank is not full, unless the user needs to send a Zero Length Packet by software. For OUT Transfer: If this bit is set, the UDPHS_EPTSTAx register RXRDY_TXKL bit is automatically reset for the current bank when the last packet byte has been read from the bank FIFO or at the end of DMA buffer if the UDPHS_DMACONTROLx register END_B_EN bit is set. For example, to truncate a padded data packet when the actual data transfer size is reached. The user may still clear the UDPHS_EPTSTAx register RXRDY_TXKL bit, for example, after completing a DMA buffer by software if UDPHS_DMACONTROLx register END_B_EN bit was disabled or in order to cancel the read of the remaining data bank(s). INTDIS_DMA: Interrupt Disables DMA (cleared upon USB reset) If set, when an enabled endpoint-originated interrupt is triggered, the DMA request is disabled regardless of the UDPHS_IEN register EPT_x bit for this endpoint. Then, the firmware will have to clear or disable the interrupt source or clear this bit if transfer completion is needed. If the exception raised is associated with the new system bank packet, then the previous DMA packet transfer is normally completed, but the new DMA packet transfer is not started (not requested). If the exception raised is not associated to a new system bank packet (NAK_IN, NAK_OUT, etc.), then the request cancellation may happen at any time and may immediately stop the current DMA transfer. This may be used, for example, to identify or prevent an erroneous packet to be transferred into a buffer or to complete a DMA buffer by software after reception of a short packet. NYET_DIS: NYET Disable (Only for High Speed Bulk OUT Endpoints) (cleared upon USB reset) 0: Lets the hardware handle the handshake response for the High Speed Bulk OUT transfer.  2017 Microchip Technology Inc. DS60001476B-page 1165 SAMA5D2 SERIES 1: Forces an ACK response to the next High Speed Bulk OUT transfer instead of a NYET response. Note: According to the Universal Serial Bus Specification, Rev 2.0 (8.5.1.1 NAK Responses to OUT/DATA During PING Protocol), a NAK response to an HS Bulk OUT transfer is expected to be an unusual occurrence. ERR_OVFLW: Overflow Error Interrupt Enabled (cleared upon USB reset) 0: Overflow Error Interrupt is masked. 1: Overflow Error Interrupt is enabled. RXRDY_TXKL: Received OUT Data Interrupt Enabled (cleared upon USB reset) 0: Received OUT Data Interrupt is masked. 1: Received OUT Data Interrupt is enabled. TX_COMPLT: Transmitted IN Data Complete Interrupt Enabled (cleared upon USB reset) 0: Transmitted IN Data Complete Interrupt is masked. 1: Transmitted IN Data Complete Interrupt is enabled. TXRDY: TX Packet Ready Interrupt Enabled (cleared upon USB reset) 0: TX Packet Ready Interrupt is masked. 1: TX Packet Ready Interrupt is enabled. Caution: Interrupt source is active as long as the corresponding UDPHS_EPTSTAx register TXRDY flag remains low. If there are no more banks available for transmitting after the software has set UDPHS_EPTSTAx/TXRDY for the last transmit packet, then the interrupt source remains inactive until the first bank becomes free again to transmit at UDPHS_EPTSTAx/TXRDY hardware clear. RX_SETUP: Received SETUP Interrupt Enabled (cleared upon USB reset) 0: Received SETUP is masked. 1: Received SETUP is enabled. STALL_SNT: Stall Sent Interrupt Enabled (cleared upon USB reset) 0: Stall Sent Interrupt is masked. 1: Stall Sent Interrupt is enabled. NAK_IN: NAKIN Interrupt Enabled (cleared upon USB reset) 0: NAKIN Interrupt is masked. 1: NAKIN Interrupt is enabled. NAK_OUT: NAKOUT Interrupt Enabled (cleared upon USB reset) 0: NAKOUT Interrupt is masked. 1: NAKOUT Interrupt is enabled. BUSY_BANK: Busy Bank Interrupt Enabled (cleared upon USB reset) 0: BUSY_BANK Interrupt is masked. 1: BUSY_BANK Interrupt is enabled. For OUT endpoints: an interrupt is sent when all banks are busy. For IN endpoints: an interrupt is sent when all banks are free. SHRT_PCKT: Short Packet Interrupt Enabled (cleared upon USB reset) For OUT endpoints: send an Interrupt when a Short Packet has been received. 0: Short Packet Interrupt is masked. 1: Short Packet Interrupt is enabled. For IN endpoints: a Short Packet transmission is guaranteed upon end of the DMA Transfer, thus signaling a BULK or INTERRUPT end of transfer, but only if the UDPHS_DMACONTROLx register END_B_EN and UDPHS_EPTCTLx register AUTO_VALID bits are also set. DS60001476B-page 1166  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.14 UDPHS Endpoint Control Register (Isochronous Endpoint) Name: UDPHS_EPTCTLx [x=0..15] (ISOENDPT) Address: 0xFC02C10C [0], 0xFC02C12C [1], 0xFC02C14C [2], 0xFC02C16C [3], 0xFC02C18C [4], 0xFC02C1AC [5], 0xFC02C1CC [6], 0xFC02C1EC [7], 0xFC02C20C [8], 0xFC02C22C [9], 0xFC02C24C [10], 0xFC02C26C [11], 0xFC02C28C [12], 0xFC02C2AC [13], 0xFC02C2CC [14], 0xFC02C2EC [15] Access: Read-only 31 SHRT_PCKT 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 BUSY_BANK 17 – 16 – 11 TXRDY_TRER 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 3 INTDIS_DMA 2 – 1 AUTO_VALID 0 EPT_ENABL 15 – 7 MDATA_RX 14 13 12 ERR_FLUSH ERR_CRC_NTR ERR_FL_ISO 6 DATAX_RX 5 – 4 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . EPT_ENABL: Endpoint Enable (cleared upon USB reset) 0: The endpoint is disabled according to the device configuration. Endpoint 0 should always be enabled after a hardware or UDPHS bus reset and participate in the device configuration. 1: The endpoint is enabled according to the device configuration. AUTO_VALID: Packet Auto-Valid Enabled (cleared upon USB reset) Set this bit to automatically validate the current packet and switch to the next bank for both IN and OUT endpoints. For IN Transfer: If this bit is set, the UDPHS_EPTSTAx register TXRDY_TRER bit is set automatically when the current bank is full and at the end of DMA buffer if the UDPHS_DMACONTROLx register END_B_EN bit is set. The user may still set the UDPHS_EPTSTAx register TXRDY_TRER bit if the current bank is not full, unless the user needs to send a Zero Length Packet by software. For OUT Transfer: If this bit is set, the UDPHS_EPTSTAx register RXRDY_TXKL bit is automatically reset for the current bank when the last packet byte has been read from the bank FIFO or at the end of DMA buffer if the UDPHS_DMACONTROLx register END_B_EN bit is set. For example, to truncate a padded data packet when the actual data transfer size is reached. The user may still clear the UDPHS_EPTSTAx register RXRDY_TXKL bit, for example, after completing a DMA buffer by software if UDPHS_DMACONTROLx register END_B_EN bit was disabled or in order to cancel the read of the remaining data bank(s). INTDIS_DMA: Interrupt Disables DMA (cleared upon USB reset) If set, when an enabled endpoint-originated interrupt is triggered, the DMA request is disabled regardless of the UDPHS_IEN register EPT_x bit for this endpoint. Then, the firmware will have to clear or disable the interrupt source or clear this bit if transfer completion is needed. If the exception raised is associated with the new system bank packet, then the previous DMA packet transfer is normally completed, but the new DMA packet transfer is not started (not requested). If the exception raised is not associated to a new system bank packet (ex: ERR_FL_ISO), then the request cancellation may happen at any time and may immediately stop the current DMA transfer. This may be used, for example, to identify or prevent an erroneous packet to be transferred into a buffer or to complete a DMA buffer by software after reception of a short packet, or to perform buffer truncation on ERR_FL_ISO interrupt for adaptive rate. DATAX_RX: DATAx Interrupt Enabled (Only for High Bandwidth Isochronous OUT endpoints) (cleared upon USB reset) 0: No effect.  2017 Microchip Technology Inc. DS60001476B-page 1167 SAMA5D2 SERIES 1: Send an interrupt when a DATA2, DATA1 or DATA0 packet has been received meaning the whole microframe data payload has been received. MDATA_RX: MDATA Interrupt Enabled (Only for High Bandwidth Isochronous OUT endpoints) (cleared upon USB reset) 0: No effect. 1: Send an interrupt when an MDATA packet has been received and so at least one packet of the microframe data payload has been received. ERR_OVFLW: Overflow Error Interrupt Enabled (cleared upon USB reset) 0: Overflow Error Interrupt is masked. 1: Overflow Error Interrupt is enabled. RXRDY_TXKL: Received OUT Data Interrupt Enabled (cleared upon USB reset) 0: Received OUT Data Interrupt is masked. 1: Received OUT Data Interrupt is enabled. TX_COMPLT: Transmitted IN Data Complete Interrupt Enabled (cleared upon USB reset) 0: Transmitted IN Data Complete Interrupt is masked. 1: Transmitted IN Data Complete Interrupt is enabled. TXRDY_TRER: TX Packet Ready/Transaction Error Interrupt Enabled (cleared upon USB reset) 0: TX Packet Ready/Transaction Error Interrupt is masked. 1: TX Packet Ready/Transaction Error Interrupt is enabled. Caution: Interrupt source is active as long as the corresponding UDPHS_EPTSTAx register TXRDY_TRER flag remains low. If there are no more banks available for transmitting after the software has set UDPHS_EPTSTAx/TXRDY_TRER for the last transmit packet, then the interrupt source remains inactive until the first bank becomes free again to transmit at UDPHS_EPTSTAx/ TXRDY_TRER hardware clear. ERR_FL_ISO: Error Flow Interrupt Enabled (cleared upon USB reset) 0: Error Flow Interrupt is masked. 1: Error Flow Interrupt is enabled. ERR_CRC_NTR: ISO CRC Error/Number of Transaction Error Interrupt Enabled (cleared upon USB reset) 0: ISO CRC error/number of Transaction Error Interrupt is masked. 1: ISO CRC error/number of Transaction Error Interrupt is enabled. DS60001476B-page 1168  2017 Microchip Technology Inc. SAMA5D2 SERIES ERR_FLUSH: Bank Flush Error Interrupt Enabled (cleared upon USB reset) 0: Bank Flush Error Interrupt is masked. 1: Bank Flush Error Interrupt is enabled. BUSY_BANK: Busy Bank Interrupt Enabled (cleared upon USB reset) 0: BUSY_BANK Interrupt is masked. 1: BUSY_BANK Interrupt is enabled. For OUT endpoints: An interrupt is sent when all banks are busy. For IN endpoints: An interrupt is sent when all banks are free. SHRT_PCKT: Short Packet Interrupt Enabled (cleared upon USB reset) For OUT endpoints: send an Interrupt when a Short Packet has been received. 0: Short Packet Interrupt is masked. 1: Short Packet Interrupt is enabled. For IN endpoints: A Short Packet transmission is guaranteed upon end of the DMA Transfer, thus signaling an end of isochronous (micro)frame data, but only if the UDPHS_DMACONTROLx register END_B_EN and UDPHS_EPTCTLx register AUTO_VALID bits are also set.  2017 Microchip Technology Inc. DS60001476B-page 1169 SAMA5D2 SERIES 41.7.15 UDPHS Endpoint Set Status Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTSETSTAx [x=0..15] Address: 0xFC02C114 [0], 0xFC02C134 [1], 0xFC02C154 [2], 0xFC02C174 [3], 0xFC02C194 [4], 0xFC02C1B4 [5], 0xFC02C1D4 [6], 0xFC02C1F4 [7], 0xFC02C214 [8], 0xFC02C234 [9], 0xFC02C254 [10], 0xFC02C274 [11], 0xFC02C294 [12], 0xFC02C2B4 [13], 0xFC02C2D4 [14], 0xFC02C2F4 [15] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 TXRDY 10 – 9 RXRDY_TXKL 8 – 7 – 6 – 5 FRCESTALL 4 – 3 – 2 – 1 – 0 – This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Status Register (Control, Bulk, Interrupt Endpoints)” . FRCESTALL: Stall Handshake Request Set 0: No effect. 1: Set this bit to request a STALL answer to the host for the next handshake Refer to chapters 8.4.5 (Handshake Packets) and 9.4.5 (Get Status) of the Universal Serial Bus Specification, Rev 2.0 for more information on the STALL handshake. RXRDY_TXKL: KILL Bank Set (for IN Endpoint) 0: No effect. 1: Kill the last written bank. TXRDY: TX Packet Ready Set 0: No effect. 1: Set this bit after a packet has been written into the endpoint FIFO for IN data transfers – This flag is used to generate a Data IN transaction (device to host). – Device firmware checks that it can write a data payload in the FIFO, checking that TXRDY is cleared. – Transfer to the FIFO is done by writing in the “Buffer Address” register. – Once the data payload has been transferred to the FIFO, the firmware notifies the UDPHS device setting TXRDY to one. – UDPHS bus transactions can start. – TXCOMP is set once the data payload has been received by the host. – Data should be written into the endpoint FIFO only after this bit has been cleared. – Set this bit without writing data to the endpoint FIFO to send a Zero Length Packet. DS60001476B-page 1170  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.16 UDPHS Endpoint Set Status Register (Isochronous Endpoint) Name: UDPHS_EPTSETSTAx [x=0..15] (ISOENDPT) Address: 0xFC02C114 [0], 0xFC02C134 [1], 0xFC02C154 [2], 0xFC02C174 [3], 0xFC02C194 [4], 0xFC02C1B4 [5], 0xFC02C1D4 [6], 0xFC02C1F4 [7], 0xFC02C214 [8], 0xFC02C234 [9], 0xFC02C254 [10], 0xFC02C274 [11], 0xFC02C294 [12], 0xFC02C2B4 [13], 0xFC02C2D4 [14], 0xFC02C2F4 [15] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 TXRDY_TRER 10 – 9 RXRDY_TXKL 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Status Register (Isochronous Endpoint)” . RXRDY_TXKL: KILL Bank Set (for IN Endpoint) 0: No effect. 1: Kill the last written bank. TXRDY_TRER: TX Packet Ready Set 0: No effect. 1: Set this bit after a packet has been written into the endpoint FIFO for IN data transfers – This flag is used to generate a Data IN transaction (device to host). – Device firmware checks that it can write a data payload in the FIFO, checking that TXRDY_TRER is cleared. – Transfer to the FIFO is done by writing in the “Buffer Address” register. – Once the data payload has been transferred to the FIFO, the firmware notifies the UDPHS device setting TXRDY_TRER to one. – UDPHS bus transactions can start. – TXCOMP is set once the data payload has been sent. – Data should be written into the endpoint FIFO only after this bit has been cleared. – Set this bit without writing data to the endpoint FIFO to send a Zero Length Packet.  2017 Microchip Technology Inc. DS60001476B-page 1171 SAMA5D2 SERIES 41.7.17 UDPHS Endpoint Clear Status Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTCLRSTAx [x=0..15] Address: 0xFC02C118 [0], 0xFC02C138 [1], 0xFC02C158 [2], 0xFC02C178 [3], 0xFC02C198 [4], 0xFC02C1B8 [5], 0xFC02C1D8 [6], 0xFC02C1F8 [7], 0xFC02C218 [8], 0xFC02C238 [9], 0xFC02C258 [10], 0xFC02C278 [11], 0xFC02C298 [12], 0xFC02C2B8 [13], 0xFC02C2D8 [14], 0xFC02C2F8 [15] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 NAK_OUT 14 NAK_IN 13 STALL_SNT 12 RX_SETUP 11 – 10 TX_COMPLT 9 RXRDY_TXKL 8 – 7 – 6 TOGGLESQ 5 FRCESTALL 4 – 3 – 2 – 1 – 0 – This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Status Register (Control, Bulk, Interrupt Endpoints)” . FRCESTALL: Stall Handshake Request Clear 0: No effect. 1: Clear the STALL request. The next packets from host will not be STALLed. TOGGLESQ: Data Toggle Clear 0: No effect. 1: Clear the PID data of the current bank For OUT endpoints, the next received packet should be a DATA0. For IN endpoints, the next packet will be sent with a DATA0 PID. RXRDY_TXKL: Received OUT Data Clear 0: No effect. 1: Clear the RXRDY_TXKL flag of UDPHS_EPTSTAx. TX_COMPLT: Transmitted IN Data Complete Clear 0: No effect. 1: Clear the TX_COMPLT flag of UDPHS_EPTSTAx. RX_SETUP: Received SETUP Clear 0: No effect. 1: Clear the RX_SETUP flags of UDPHS_EPTSTAx. STALL_SNT: Stall Sent Clear 0: No effect. 1: Clear the STALL_SNT flags of UDPHS_EPTSTAx. NAK_IN: NAKIN Clear 0: No effect. 1: Clear the NAK_IN flags of UDPHS_EPTSTAx. NAK_OUT: NAKOUT Clear DS60001476B-page 1172  2017 Microchip Technology Inc. SAMA5D2 SERIES 0: No effect. 1: Clear the NAK_OUT flag of UDPHS_EPTSTAx.  2017 Microchip Technology Inc. DS60001476B-page 1173 SAMA5D2 SERIES 41.7.18 UDPHS Endpoint Clear Status Register (Isochronous Endpoint) Name: UDPHS_EPTCLRSTAx [x=0..15] (ISOENDPT) Address: 0xFC02C118 [0], 0xFC02C138 [1], 0xFC02C158 [2], 0xFC02C178 [3], 0xFC02C198 [4], 0xFC02C1B8 [5], 0xFC02C1D8 [6], 0xFC02C1F8 [7], 0xFC02C218 [8], 0xFC02C238 [9], 0xFC02C258 [10], 0xFC02C278 [11], 0xFC02C298 [12], 0xFC02C2B8 [13], 0xFC02C2D8 [14], 0xFC02C2F8 [15] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 13 12 ERR_FLUSH ERR_CRC_NTR ERR_FL_ISO 11 – 10 TX_COMPLT 9 RXRDY_TXKL 8 – 7 – 6 TOGGLESQ 3 – 2 – 1 – 0 – 5 – 4 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . For additional information, refer to “UDPHS Endpoint Status Register (Isochronous Endpoint)” . TOGGLESQ: Data Toggle Clear 0: No effect. 1: Clear the PID data of the current bank For OUT endpoints, the next received packet should be a DATA0. For IN endpoints, the next packet will be sent with a DATA0 PID. RXRDY_TXKL: Received OUT Data Clear 0: No effect. 1: Clear the RXRDY_TXKL flag of UDPHS_EPTSTAx. TX_COMPLT: Transmitted IN Data Complete Clear 0: No effect. 1: Clear the TX_COMPLT flag of UDPHS_EPTSTAx. ERR_FL_ISO: Error Flow Clear 0: No effect. 1: Clear the ERR_FL_ISO flags of UDPHS_EPTSTAx. ERR_CRC_NTR: Number of Transaction Error Clear 0: No effect. 1: Clear the ERR_CRC_NTR flags of UDPHS_EPTSTAx. ERR_FLUSH: Bank Flush Error Clear 0: No effect. 1: Clear the ERR_FLUSH flags of UDPHS_EPTSTAx. DS60001476B-page 1174  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.19 UDPHS Endpoint Status Register (Control, Bulk, Interrupt Endpoints) Name: UDPHS_EPTSTAx [x=0..15] Address: 0xFC02C11C [0], 0xFC02C13C [1], 0xFC02C15C [2], 0xFC02C17C [3], 0xFC02C19C [4], 0xFC02C1BC [5], 0xFC02C1DC [6], 0xFC02C1FC [7], 0xFC02C21C [8], 0xFC02C23C [9], 0xFC02C25C [10], 0xFC02C27C [11], 0xFC02C29C [12], 0xFC02C2BC [13], 0xFC02C2DC [14], 0xFC02C2FC [15] Access: Read-only 31 SHRT_PCKT 30 23 15 NAK_OUT 29 28 22 21 BYTE_COUNT 20 14 NAK_IN 7 6 TOGGLESQ_STA 27 BYTE_COUNT 26 19 18 BUSY_BANK_STA 25 24 17 16 CURBK_CTLDIR 13 STALL_SNT 12 RX_SETUP 11 TXRDY 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 5 FRCESTALL 4 – 3 – 2 – 1 – 0 – This register view is relevant only if EPT_TYPE = 0x0, 0x2 or 0x3 in “UDPHS Endpoint Configuration Register” . FRCESTALL: Stall Handshake Request (cleared upon USB reset) 0: No effect. 1: If set a STALL answer will be done to the host for the next handshake. This bit is reset by hardware upon received SETUP. TOGGLESQ_STA: Toggle Sequencing (cleared upon USB reset) Toggle Sequencing: – IN endpoint: It indicates the PID Data Toggle that will be used for the next packet sent. This is not relative to the current bank. – CONTROL and OUT endpoint: These bits are set by hardware to indicate the PID data of the current bank: Value Name Description 0 DATA0 DATA0 1 DATA1 DATA1 2 DATA2 Reserved for High Bandwidth Isochronous Endpoint 3 MDATA Reserved for High Bandwidth Isochronous Endpoint Note 1: In OUT transfer, the Toggle information is meaningful only when the current bank is busy (Received OUT Data = 1). 2: These bits are updated for OUT transfer: - A new data has been written into the current bank. - The user has just cleared the Received OUT Data bit to switch to the next bank. 3: This field is reset to DATA1 by the UDPHS_EPTCLRSTAx register TOGGLESQ bit, and by UDPHS_EPTCTLDISx (disable endpoint).  2017 Microchip Technology Inc. DS60001476B-page 1175 SAMA5D2 SERIES ERR_OVFLW: Overflow Error (cleared upon USB reset) This bit is set by hardware when a new too-long packet is received. Example: If the user programs an endpoint 64 bytes wide and the host sends 128 bytes in an OUT transfer, then the Overflow Error bit is set. This bit is updated at the same time as the BYTE_COUNT field. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). RXRDY_TXKL: Received OUT Data/KILL Bank (cleared upon USB reset) – Received OUT Data (for OUT endpoint or Control endpoint): This bit is set by hardware after a new packet has been stored in the endpoint FIFO. This bit is cleared by the device firmware after reading the OUT data from the endpoint. For multi-bank endpoints, this bit may remain active even when cleared by the device firmware, this if an other packet has been received meanwhile. Hardware assertion of this bit may generate an interrupt if enabled by the UDPHS_EPTCTLx register RXRDY_TXKL bit. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). – KILL Bank (for IN endpoint): – The bank is really cleared or the bank is sent, BUSY_BANK_STA is decremented. – The bank is not cleared but sent on the IN transfer, TX_COMPLT – The bank is not cleared because it was empty. The user should wait that this bit is cleared before trying to clear another packet. Note: “Kill a packet” may be refused if at the same time, an IN token is coming and the current packet is sent on the UDPHS line. In this case, the TX_COMPLT bit is set. Take notice however, that if at least two banks are ready to be sent, there is no problem to kill a packet even if an IN token is coming. In fact, in that case, the current bank is sent (IN transfer) and the last bank is killed. TX_COMPLT: Transmitted IN Data Complete (cleared upon USB reset) This bit is set by hardware after an IN packet has been accepted (ACK’ed) by the host. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). TXRDY: TX Packet Ready (cleared upon USB reset) This bit is cleared by hardware after the host has acknowledged the packet. For Multi-bank endpoints, this bit may remain clear even after software is set if another bank is available to transmit. Hardware clear of this bit may generate an interrupt if enabled by the UDPHS_EPTCTLx register TXRDY bit. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). RX_SETUP: Received SETUP (cleared upon USB reset) – (for Control endpoint only) This bit is set by hardware when a valid SETUP packet has been received from the host. It is cleared by the device firmware after reading the SETUP data from the endpoint FIFO. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). DS60001476B-page 1176  2017 Microchip Technology Inc. SAMA5D2 SERIES STALL_SNT: Stall Sent (cleared upon USB reset) – (for Control, Bulk and Interrupt endpoints) This bit is set by hardware after a STALL handshake has been sent as requested by the UDPHS_EPTSTAx register FRCESTALL bit. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). NAK_IN: NAK IN (cleared upon USB reset) This bit is set by hardware when a NAK handshake has been sent in response to an IN request from the Host. This bit is cleared by software. NAK_OUT: NAK OUT (cleared upon USB reset) This bit is set by hardware when a NAK handshake has been sent in response to an OUT or PING request from the Host. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by EPT_CTL_DISx (disable endpoint). CURBK_CTLDIR: Current Bank/Control Direction (cleared upon USB reset) – Current Bank (not relevant for Control endpoint): These bits are set by hardware to indicate the number of the current bank. Value Name Description 0 BANK0 Bank 0 (or single bank) 1 BANK1 Bank 1 2 BANK2 Bank 2 Note: The current bank is updated each time the user: - Sets the TX Packet Ready bit to prepare the next IN transfer and to switch to the next bank. - Clears the received OUT data bit to access the next bank. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). – Control Direction (for Control endpoint only): 0: A Control Write is requested by the Host. 1: A Control Read is requested by the Host. Note 1: This bit corresponds with the 7th bit of the bmRequestType (Byte 0 of the Setup Data). 2: This bit is updated after receiving new setup data. BUSY_BANK_STA: Busy Bank Number (cleared upon USB reset) These bits are set by hardware to indicate the number of busy banks. IN endpoint: It indicates the number of busy banks filled by the user, ready for IN transfer. OUT endpoint: It indicates the number of busy banks filled by OUT transaction from the Host. Value Name Description 0 0BUSYBANK All banks are free 1 1BUSYBANK 1 busy bank 2 2BUSYBANKS 2 busy banks 3 3BUSYBANKS 3 busy banks  2017 Microchip Technology Inc. DS60001476B-page 1177 SAMA5D2 SERIES BYTE_COUNT: UDPHS Byte Count (cleared upon USB reset) Byte count of a received data packet. This field is incremented after each write into the endpoint (to prepare an IN transfer). This field is decremented after each reading into the endpoint (OUT transfer). This field is also updated at RXRDY_TXKL flag clear with the next bank. This field is also updated at TXRDY flag set with the next bank. This field is reset by EPT_x of UDPHS_EPTRST register. SHRT_PCKT: Short Packet (cleared upon USB reset) An OUT Short Packet is detected when the receive byte count is less than the configured UDPHS_EPTCFGx register EPT_Size. This bit is updated at the same time as the BYTE_COUNT field. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). DS60001476B-page 1178  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.20 UDPHS Endpoint Status Register (Isochronous Endpoint) Name: UDPHS_EPTSTAx [x=0..15] (ISOENDPT) Address: 0xFC02C11C [0], 0xFC02C13C [1], 0xFC02C15C [2], 0xFC02C17C [3], 0xFC02C19C [4], 0xFC02C1BC [5], 0xFC02C1DC [6], 0xFC02C1FC [7], 0xFC02C21C [8], 0xFC02C23C [9], 0xFC02C25C [10], 0xFC02C27C [11], 0xFC02C29C [12], 0xFC02C2BC [13], 0xFC02C2DC [14], 0xFC02C2FC [15] Access: Read-only 31 SHRT_PCKT 30 23 15 – 29 28 22 21 BYTE_COUNT 20 14 13 12 ERR_FLUSH ERR_CRC_NTR ERR_FL_ISO 7 6 TOGGLESQ_STA 5 – 4 – 27 BYTE_COUNT 26 25 19 18 BUSY_BANK_STA 17 24 16 CURBK 11 TXRDY_TRER 10 TX_COMPLT 9 RXRDY_TXKL 8 ERR_OVFLW 3 – 2 – 1 – 0 – This register view is relevant only if EPT_TYPE = 0x1 in “UDPHS Endpoint Configuration Register” . TOGGLESQ_STA: Toggle Sequencing (cleared upon USB reset) Toggle Sequencing: – IN endpoint: It indicates the PID Data Toggle that will be used for the next packet sent. This is not relative to the current bank. – OUT endpoint: These bits are set by hardware to indicate the PID data of the current bank: Value Name Description 0 DATA0 DATA0 1 DATA1 DATA1 2 DATA2 Data2 (only for High Bandwidth Isochronous Endpoint) 3 MDATA MData (only for High Bandwidth Isochronous Endpoint) Note 1: In OUT transfer, the Toggle information is meaningful only when the current bank is busy (Received OUT Data = 1). 2: These bits are updated for OUT transfer: - A new data has been written into the current bank. - The user has just cleared the Received OUT Data bit to switch to the next bank. 3: For High Bandwidth Isochronous Out endpoint, it is recommended to check the UDPHS_EPTSTAx/TXRDY_TRER bit to know if the toggle sequencing is correct or not. 4: This field is reset to DATA1 by the UDPHS_EPTCLRSTAx register TOGGLESQ bit, and by UDPHS_EPTCTLDISx (disable endpoint). ERR_OVFLW: Overflow Error (cleared upon USB reset) This bit is set by hardware when a new too-long packet is received. Example: If the user programs an endpoint 64 bytes wide and the host sends 128 bytes in an OUT transfer, then the Overflow Error bit is set. This bit is updated at the same time as the BYTE_COUNT field. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). RXRDY_TXKL: Received OUT Data/KILL Bank (cleared upon USB reset) – Received OUT Data (for OUT endpoint or Control endpoint):  2017 Microchip Technology Inc. DS60001476B-page 1179 SAMA5D2 SERIES This bit is set by hardware after a new packet has been stored in the endpoint FIFO. This bit is cleared by the device firmware after reading the OUT data from the endpoint. For multi-bank endpoints, this bit may remain active even when cleared by the device firmware, this if an other packet has been received meanwhile. Hardware assertion of this bit may generate an interrupt if enabled by the UDPHS_EPTCTLx register RXRDY_TXKL bit. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). – KILL Bank (for IN endpoint): – The bank is really cleared or the bank is sent, BUSY_BANK_STA is decremented. – The bank is not cleared but sent on the IN transfer, TX_COMPLT – The bank is not cleared because it was empty. The user should wait that this bit is cleared before trying to clear another packet. Note: “Kill a packet” may be refused if at the same time, an IN token is coming and the current packet is sent on the UDPHS line. In this case, the TX_COMPLT bit is set. Take notice however, that if at least two banks are ready to be sent, there is no problem to kill a packet even if an IN token is coming. In fact, in that case, the current bank is sent (IN transfer) and the last bank is killed. TX_COMPLT: Transmitted IN Data Complete (cleared upon USB reset) This bit is set by hardware after an IN packet has been sent. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). TXRDY_TRER: TX Packet Ready/Transaction Error (cleared upon USB reset) – TX Packet Ready: This bit is cleared by hardware, as soon as the packet has been sent. For Multi-bank endpoints, this bit may remain clear even after software is set if another bank is available to transmit. Hardware clear of this bit may generate an interrupt if enabled by the UDPHS_EPTCTLx register TXRDY_TRER bit. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). – Transaction Error (for high bandwidth isochronous OUT endpoints) (Read-Only): This bit is set by hardware when a transaction error occurs inside one microframe. If one toggle sequencing problem occurs among the n-transactions (n = 1, 2 or 3) inside a microframe, then this bit is still set as long as the current bank contains one “bad” n-transaction (refer to “CURBK: Current Bank (cleared upon USB reset)” ). As soon as the current bank is relative to a new “good” n-transactions, then this bit is reset. Note 1: A transaction error occurs when the toggle sequencing does not comply with the Universal Serial Bus Specification, Rev 2.0 (5.9.2 High Bandwidth Isochronous endpoints) (Bad PID, missing data, etc.) 2: When a transaction error occurs, the user may empty all the “bad” transactions by clearing the Received OUT Data flag (RXRDY_TXKL). If this bit is reset, then the user should consider that a new n-transaction is coming. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint), and by UDPHS_EPTCTLDISx (disable endpoint). ERR_FL_ISO: Error Flow (cleared upon USB reset) This bit is set by hardware when a transaction error occurs. – Isochronous IN transaction is missed, the micro has no time to fill the endpoint (underflow). – Isochronous OUT data is dropped because the bank is busy (overflow). This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). ERR_CRC_NTR: CRC ISO Error/Number of Transaction Error (cleared upon USB reset) – CRC ISO Error (for Isochronous OUT endpoints) (Read-only): This bit is set by hardware if the last received data is corrupted (CRC error on data). This bit is updated by hardware when new data is received (Received OUT Data bit). – Number of Transaction Error (for High Bandwidth Isochronous IN endpoints): DS60001476B-page 1180  2017 Microchip Technology Inc. SAMA5D2 SERIES This bit is set at the end of a microframe in which at least one data bank has been transmitted, if less than the number of transactions per micro-frame banks (UDPHS_EPTCFGx register NB_TRANS) have been validated for transmission inside this microframe. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). ERR_FLUSH: Bank Flush Error (cleared upon USB reset) – (for High Bandwidth Isochronous IN endpoints) This bit is set when flushing unsent banks at the end of a microframe. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by EPT_CTL_DISx (disable endpoint). CURBK: Current Bank (cleared upon USB reset) – Current Bank: These bits are set by hardware to indicate the number of the current bank. Value Name Description 0 BANK0 Bank 0 (or single bank) 1 BANK1 Bank 1 2 BANK2 Bank 2 Note: The current bank is updated each time the user: - Sets the TX Packet Ready bit to prepare the next IN transfer and to switch to the next bank. - Clears the received OUT data bit to access the next bank. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). BUSY_BANK_STA: Busy Bank Number (cleared upon USB reset) These bits are set by hardware to indicate the number of busy banks. – IN endpoint: It indicates the number of busy banks filled by the user, ready for IN transfer. – OUT endpoint: It indicates the number of busy banks filled by OUT transaction from the Host. Value Name Description 0 0BUSYBANK All banks are free 1 1BUSYBANK 1 busy bank 2 2BUSYBANKS 2 busy banks 3 3BUSYBANKS 3 busy banks  2017 Microchip Technology Inc. DS60001476B-page 1181 SAMA5D2 SERIES BYTE_COUNT: UDPHS Byte Count (cleared upon USB reset) Byte count of a received data packet. This field is incremented after each write into the endpoint (to prepare an IN transfer). This field is decremented after each reading into the endpoint (OUT transfer). This field is also updated at RXRDY_TXKL flag clear with the next bank. This field is also updated at TXRDY_TRER flag set with the next bank. This field is reset by EPT_x of UDPHS_EPTRST register. SHRT_PCKT: Short Packet (cleared upon USB reset) An OUT Short Packet is detected when the receive byte count is less than the configured UDPHS_EPTCFGx register EPT_Size. This bit is updated at the same time as the BYTE_COUNT field. This bit is reset by UDPHS_EPTRST register EPT_x (reset endpoint) and by UDPHS_EPTCTLDISx (disable endpoint). DS60001476B-page 1182  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.21 UDPHS DMA Channel Transfer Descriptor The DMA channel transfer descriptor is loaded from the memory. Be careful with the alignment of this buffer. The structure of the DMA channel transfer descriptor is defined by three parameters as described below: Offset 0: The address must be aligned: 0xXXXX0 Next Descriptor Address Register: UDPHS_DMANXTDSCx Offset 4: The address must be aligned: 0xXXXX4 DMA Channelx Address Register: UDPHS_DMAADDRESSx Offset 8: The address must be aligned: 0xXXXX8 DMA Channelx Control Register: UDPHS_DMACONTROLx To use the DMA channel transfer descriptor, fill the structures with the correct value (as described in the following pages). Then write directly in UDPHS_DMANXTDSCx the address of the descriptor to be used first. Then write 1 in the LDNXT_DSC bit of UDPHS_DMACONTROLx (load next channel transfer descriptor). The descriptor is automatically loaded upon Endpointx request for packet transfer.  2017 Microchip Technology Inc. DS60001476B-page 1183 SAMA5D2 SERIES 41.7.22 UDPHS DMA Next Descriptor Address Register Name: UDPHS_DMANXTDSCx [x = 0..6] Address: 0xFC02C300 [0], 0xFC02C310 [1], 0xFC02C320 [2], 0xFC02C330 [3], 0xFC02C340 [4], 0xFC02C350 [5], 0xFC02C360 [6] Access: Read/Write 31 30 29 28 27 NXT_DSC_ADD 26 25 24 23 22 21 20 19 NXT_DSC_ADD 18 17 16 15 14 13 12 11 NXT_DSC_ADD 10 9 8 7 6 5 4 3 NXT_DSC_ADD 2 1 0 Note: Channel 0 is not used. NXT_DSC_ADD: Next Descriptor Address This field points to the next channel descriptor to be processed. This channel descriptor must be aligned, so bits 0 to 3 of the address must be equal to zero. DS60001476B-page 1184  2017 Microchip Technology Inc. SAMA5D2 SERIES 41.7.23 UDPHS DMA Channel Address Register Name: UDPHS_DMAADDRESSx [x = 0..6] Address: 0xFC02C304 [0], 0xFC02C314 [1], 0xFC02C324 [2], 0xFC02C334 [3], 0xFC02C344 [4], 0xFC02C354 [5], 0xFC02C364 [6] Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 BUFF_ADD 23 22 21 20 BUFF_ADD 15 14 13 12 BUFF_ADD 7 6 5 4 BUFF_ADD Note: Channel 0 is not used. BUFF_ADD: Buffer Address This field determines the AHB bus starting address of a DMA channel transfer. Channel start and end addresses may be aligned on any byte boundary. The firmware may write this field only when the UDPHS_DMASTATUS register CHANN_ENB bit is clear. This field is updated at the end of the address phase of the current access to the AHB bus. It is incrementing of the access byte width. The 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 UDPHS device, USB end of transfer if the UDPHS_DMACONTROLx register END_TR_EN bit is set.  2017 Microchip Technology Inc. DS60001476B-page 1185 SAMA5D2 SERIES 41.7.24 UDPHS DMA Channel Control Register Name: UDPHS_DMACONTROLx [x = 0..6] Address: 0xFC02C308 [0], 0xFC02C318 [1], 0xFC02C328 [2], 0xFC02C338 [3], 0xFC02C348 [4], 0xFC02C358 [5], 0xFC02C368 [6] Access: Read/Write 31 30 29 28 27 BUFF_LENGTH 26 25 24 23 22 21 20 19 BUFF_LENGTH 18 17 16 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 BURST_LCK 6 DESC_LD_IT 5 END_BUFFIT 4 END_TR_IT 3 END_B_EN 2 END_TR_EN 1 LDNXT_DSC 0 CHANN_ENB Note: Channel 0 is not used. CHANN_ENB: (Channel Enable Command) 0: DMA channel is disabled at and no transfer will occur upon request. This bit is also cleared by hardware when the channel source bus is disabled at end of buffer. If the UDPHS_DMACONTROL register LDNXT_DSC bit has been cleared by descriptor loading, the firmware will have to set the corresponding CHANN_ENB bit to start the described transfer, if needed. If the UDPHS_DMACONTROL register LDNXT_DSC bit is cleared, the channel is frozen and the channel registers may then be read and/ or written reliably as soon as both UDPHS_DMASTATUS register CHANN_ENB and CHANN_ACT flags read as 0. If a channel request is currently serviced when this bit is cleared, the DMA FIFO buffer is drained until it is empty, then the UDPHS_DMASTATUS register CHANN_ENB bit is cleared. If the LDNXT_DSC bit is set at or after this bit clearing, then the currently loaded descriptor is skipped (no data transfer occurs) and the next descriptor is immediately loaded. 1: UDPHS_DMASTATUS register CHANN_ENB bit will be set, thus enabling DMA channel data transfer. Then any pending request will start the transfer. This may be used to start or resume any requested transfer. LDNXT_DSC: Load Next Channel Transfer Descriptor Enable (Command) 0: No channel register is loaded after the end of the channel transfer. 1: The channel controller loads the next descriptor after the end of the current transfer, i.e., when the UDPHS_DMASTATUS/CHANN_ENB bit is reset. If the UDPHS_DMA CONTROL/CHANN_ENB bit is cleared, the next descriptor is immediately loaded upon transfer request. DMA Channel Control Command Summary LDNXT_DSC CHANN_ENB Description 0 0 Stop now 0 1 Run and stop at end of buffer 1 0 Load next descriptor now 1 1 Run and link at end of buffer END_TR_EN: End of Transfer Enable (Control) Used for OUT transfers only. 0: USB end of transfer is ignored. 1: UDPHS device can put an end to the current buffer transfer. DS60001476B-page 1186  2017 Microchip Technology Inc. SAMA5D2 SERIES When set, a BULK or INTERRUPT short packet or the last packet of an ISOCHRONOUS (micro) frame (DATAX) will close the current buffer and the UDPHS_DMASTATUSx register END_TR_ST flag will be raised. This is intended for UDPHS non-prenegotiated end of transfer (BULK or INTERRUPT) or ISOCHRONOUS microframe data buffer closure. END_B_EN: End of Buffer Enable (Control) 0: DMA Buffer End has no impact on USB packet transfer. 1: Endpoint can validate the packet (according to the values programmed in the UDPHS_EPTCTLx register AUTO_VALID and SHRT_PCKT fields) at DMA Buffer End, i.e., when the UDPHS_DMASTATUS register BUFF_COUNT reaches 0. This is mainly for short packet IN validation initiated by the DMA reaching end of buffer, but could be used for OUT packet truncation (discarding of unwanted packet data) at the end of DMA buffer. END_TR_IT: End of Transfer Interrupt Enable 0: UDPHS device initiated buffer transfer completion will not trigger any interrupt at UDPHS_STATUSx/END_TR_ST rising. 1: An interrupt is sent after the buffer transfer is complete, if the UDPHS device has ended the buffer transfer. Use when the receive size is unknown. END_BUFFIT: End of Buffer Interrupt Enable 0: UDPHS_DMA_STATUSx/END_BF_ST rising will not trigger any interrupt. 1: An interrupt is generated when the UDPHS_DMASTATUSx register BUFF_COUNT reaches zero. DESC_LD_IT: Descriptor Loaded Interrupt Enable 0: UDPHS_DMASTATUSx/DESC_LDST rising will not trigger any interrupt. 1: An interrupt is generated when a descriptor has been loaded from the bus. BURST_LCK: Burst Lock Enable 0: The DMA never locks bus access. 1: USB packets AHB data bursts are locked for maximum optimization of the bus bandwidth usage and maximization of fly-by AHB burst duration. BUFF_LENGTH: Buffer Byte Length (Write-only) This field determines the number of bytes to be transferred until end of buffer. The maximum channel transfer size (64 KBytes) is reached when this field is 0 (default value). If the transfer size is unknown, this field should be set to 0, but the transfer end may occur earlier under UDPHS device control. When this field is written, The UDPHS_DMASTATUSx register BUFF_COUNT field is updated with the write value. Note 1: Bits [31:2] are only writable when issuing a channel Control Command other than “Stop Now”. 2: For reliability it is highly recommended to wait for both UDPHS_DMASTATUSx register CHAN_ACT and CHAN_ENB flags are at 0, thus ensuring the channel has been stopped before issuing a command other than “Stop Now”.  2017 Microchip Technology Inc. DS60001476B-page 1187 SAMA5D2 SERIES 41.7.25 UDPHS DMA Channel Status Register Name: UDPHS_DMASTATUSx [x = 0..6] Address: 0xFC02C30C [0], 0xFC02C31C [1], 0xFC02C32C [2], 0xFC02C33C [3], 0xFC02C34C [4], 0xFC02C35C [5], 0xFC02C36C [6] Access: Read/Write 31 30 29 28 27 BUFF_COUNT 26 25 24 23 22 21 20 19 BUFF_COUNT 18 17 16 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 DESC_LDST 5 END_BF_ST 4 END_TR_ST 3 – 2 – 1 CHANN_ACT 0 CHANN_ENB Note: Channel 0 is not used. CHANN_ENB: Channel Enable Status 0: The DMA channel no longer transfers data, and may load the next descriptor if the UDPHS_DMACONTROLx register LDNXT_DSC bit is set. When any transfer is ended either due to an elapsed byte count or a UDPHS device initiated transfer end, this bit is automatically reset. 1: The DMA channel is currently enabled and transfers data upon request. This bit is normally set or cleared by writing into the UDPHS_DMACONTROLx register CHANN_ENB bit either by software or descriptor loading. If a channel request is currently serviced when the UDPHS_DMACONTROLx register CHANN_ENB bit is cleared, the DMA FIFO buffer is drained until it is empty, then this status bit is cleared. CHANN_ACT: Channel Active Status 0: The DMA channel is no longer trying to source the packet data. When a packet transfer is ended this bit is automatically reset. 1: The DMA channel is currently trying to source packet data, i.e., selected as the highest-priority requesting channel. When a packet transfer cannot be completed due to an END_BF_ST, this flag stays set during the next channel descriptor load (if any) and potentially until UDPHS packet transfer completion, if allowed by the new descriptor. END_TR_ST: End of Channel Transfer Status 0: Cleared automatically when read by software. 1: Set by hardware when the last packet transfer is complete, if the UDPHS device has ended the transfer. Valid until the CHANN_ENB flag is cleared at the end of the next buffer transfer. END_BF_ST: End of Channel Buffer Status 0: Cleared automatically when read by software. 1: Set by hardware when the BUFF_COUNT countdown reaches zero. Valid until the CHANN_ENB flag is cleared at the end of the next buffer transfer. DESC_LDST: Descriptor Loaded Status 0: Cleared automatically when read by software. 1: Set by hardware when a descriptor has been loaded from the system bus. Valid until the CHANN_ENB flag is cleared at the end of the next buffer transfer. BUFF_COUNT: Buffer Byte Count DS60001476B-page 1188  2017 Microchip Technology Inc. SAMA5D2 SERIES This field determines the current number of bytes still to be transferred for this buffer. This field is decremented from the AHB source bus access byte width at the end of this bus address phase. The access byte width is 4 by default, or less, at DMA start or end, if the start or end address is not aligned on a word boundary. At the end of buffer, the DMA accesses the UDPHS device only for the number of bytes needed to complete it. This field value is reliable (stable) only if the channel has been stopped or frozen (UDPHS_EPTCTLx register NT_DIS_DMA bit is used to disable the channel request) and the channel is no longer active CHANN_ACT flag is 0. Note: For OUT endpoints, if the receive buffer byte length (BUFF_LENGTH) has been defaulted to zero because the USB transfer length is unknown, the actual buffer byte length received is 0x10000-BUFF_COUNT.  2017 Microchip Technology Inc. DS60001476B-page 1189 SAMA5D2 SERIES 42. USB Host High Speed Port (UHPHS) 42.1 Description The USB Host High Speed Port (UHPHS) interfaces the USB with the host application. It handles Open HCI protocol (Open Host Controller Interface) as well as Enhanced HCI protocol (Enhanced Host Controller Interface). 42.2 Embedded Characteristics • Compliant with Enhanced HCI Rev 1.0 Specification - Compliant with USB V2.0 High-speed Specification - Supports High-speed 480 Mbps • Compliant with OpenHCI Rev 1.0 Specification - Compliant with USB V2.0 Full-speed and Low-speed Specification - Supports both Low-speed 1.5 Mbps and Full-speed 12 Mbps USB devices • Root Hub Integrated with 3 Downstream USB HS Ports • Embedded USB Transceivers • Supports Power Management • 2 Hosts (A and B) High Speed (EHCI), Port A shared with UDPHS • 1 Host (C) High Speed only (HSIC) DS60001476B-page 1190  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.3 Block Diagram Figure 42-1: Block Diagram HCI Slave Block AHB Slave OHCI Registers Root Hub Registers List Processor Block Control Embedded USB v2.0 Transceiver ED & TD Registers Root Hub and Host SIE Master AHB HCI Master Block Data HCI Slave Block Slave EHCI Registers USB High-speed Transceiver HHSDPA HHSDMA PORT S/M 1 USB High-speed Transceiver HHSDPB HHSDMB PORT S/M 2 USB Inter-chip Transceiver DATA STROBE FIFO 64 x 8 SOF Generator AHB PORT S/M 0 Packet Buffer FIFO Control List Processor Master AHB HCI Master Block Data Access to the USB host operational registers is achieved through the AHB bus slave interface. The Open HCI host controller and Enhanced HCI host controller initialize master DMA transfers through the AHB bus master interface as follows: • • • • Fetches endpoint descriptors and transfer descriptors Access to endpoint data from system memory Access to the HC communication area Write status and retire transfer descriptor Memory access errors (abort, misalignment) lead to an “Unrecoverable Error” indicated by the corresponding flag in the host controller operational registers. The USB root hub is integrated in the USB host. Several USB downstream ports are available. The number of downstream ports can be determined by the software driver reading the root hub’s operational registers. Device connection is automatically detected by the USB host port logic. USB physical transceivers are integrated in the product and driven by the root hub’s ports.  2017 Microchip Technology Inc. DS60001476B-page 1191 SAMA5D2 SERIES 42.4 Typical Connection Figure 42-2: Board Schematic to Interface UHP High-speed Host Controller PIO (VBUS ENABLE) +5V "A" Receptacle 1 = VBUS 2 = D3 = D+ 4 = GND HHSDM/HFSDM 3 4 Shell = Shield 1 2 HHSDP/HFSDP 5K62 ± 1% W VBG 10 pF GNDUTMII Note 1: 10 pF capacitor on VBG is a provision and may not be populated. 42.5 42.5.1 Product Dependencies I/O Lines HFSDPs, HFSDMs, HHSDPs and HHSDMs are not controlled by any PIO controllers. The embedded USB High Speed physical transceivers are controlled by the USB host controller. 42.5.2 Power Management The system embeds 3 transceivers. The USB Host High Speed requires a 480 MHz clock for the embedded High-speed transceivers. This clock (UPLLCK) is provided by the UTMI PLL. In case power consumption is saved by stopping the UTMI PLL, high-speed operations are not possible. Nevertheless, OHCI Full-speed operations remain possible by selecting PLLACK as the input clock of OHCI. The High-speed transceiver returns a 30 MHz clock to the USB Host controller. The USB Host controller requires 48 MHz and 12 MHz clocks for OHCI full-speed operations. These clocks must be generated by a PLL with a correct accuracy of ± 0.25% using the USBDIV field. Thus the USB Host peripheral receives three clocks from the Power Management Controller (PMC): the Peripheral Clock (MCK domain), the UHP48M and the UHP12M (built-in UHP48M divided by four) used by the OHCI to interface with the bus USB signals (recovered 12 MHz domain) in Full-speed operations. For High-speed operations, the user has to perform the following: • • • • • • • Enable UHP peripheral clock in PMC_PCER. Write PLLCOUNT field in CKGR_UCKR. Enable UPLL with UPLLEN bit in CKGR_UCKR. Wait until UTMI_PLL is locked (LOCKU bit in PMC_SR). Enable BIAS with BIASEN bit in CKGR_UCKR. Select UPLLCK as Input clock of OHCI part (USBS bit in PMC_USB register). Program OHCI clocks (UHP48M and UHP12M) with USBDIV field in PMC_USB register. USBDIV must be 9 (division by 10) if UPLLCK is selected. • Enable OHCI clocks with UHP bit in PMC_SCER. For OHCI Full-speed operations only, the user has to perform the following: DS60001476B-page 1192  2017 Microchip Technology Inc. SAMA5D2 SERIES • Enable UHP peripheral clock in PMC_PCER. • Select PLLACK as Input clock of OHCI part (USBS bit in PMC_USB register). • Program OHCI clocks (UHP48M and UHP12M) with USBDIV field in PMC_USB register. USBDIV value is to be calculated according to the PLLACK value and USB Full-speed accuracy. • Enable the OHCI clocks with UHP bit in PMC_SCER. Figure 42-3: UHP Clock Trees UPLL (480 MHz) AHB EHCI Master Interface 30 MHz USB 2.0 EHCI Host Controller Port Router EHCI User Interface 30 MHz UTMI Transceiver UTMI Transceiver 30 MHz HSIC MCK OHCI Master Interface Root Hub and Host SIE UHP48M UHP12M OHCI User Interface USB 1.1 OHCI Host Controller OHCI clocks 42.5.3 Interrupt Sources The USB host interface has an interrupt line connected to the interrupt controller. Handling USB host interrupts requires programming the interrupt controller before configuring the UHPHS.  2017 Microchip Technology Inc. DS60001476B-page 1193 SAMA5D2 SERIES 42.6 Functional Description Figure 42-4: USB Selection HS Transceiver HSIC HS Transceiver Transceiver EN_UDPHS 0 PB 42.6.1 PC 1 PA HS USB Host HS EHCI FS OHCI HS HSIC HS USB Device DMA DMA EHCI The USB Host Port controller is fully compliant with the Enhanced HCI specification. The USB Host Port User Interface (registers description) can be found in the Enhanced HCI Rev 1.0 Specification available on www.usb.org. The standard EHCI USB stack driver can be easily ported to the device architecture without hardware specialization. 42.6.2 OHCI The USB Host Port integrates a root hub and transceivers on downstream ports. It provides several Full-speed half-duplex serial communication ports at a baud rate of 12 Mbit/s. Up to 127 USB devices (printer, camera, mouse, keyboard, disk, etc.) and the USB hub can be connected to the USB host in the USB “tiered star” topology. The USB Host Port controller is fully compliant with the Open HCI specification. The USB Host Port User Interface (registers description) can be found in the Open HCI Rev 1.0 Specification available on www.usb.org. The standard OHCI USB stack driver can be easily ported to the device architecture without hardware specialization. This means that all standard class devices are automatically detected and available to the user’s application. As an example, integrating an HID (Human Interface Device) class driver provides a plug & play feature for all USB keyboards and mouses. 42.6.3 HSIC The High-Speed Inter-Chip (HSIC) is a standard for USB chip-to-chip interconnect with a 2-signal (strobe, data) source synchronous serial interface using 240 MHz DDR signaling to provide only high-speed 480 Mbps data rate. External cables, connectors and hot plug & play are not supported. The HSIC interface operates at high speed, 480 Mbps, and is fully compatible with existing USB software stacks. It meets all data transfer needs through a single unified USB software stack. DS60001476B-page 1194  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7 USB Host High Speed Port (UHPHS) User Interface The Enhanced USB Host Controller contains two sets of software-accessible hardware registers – Memory-mapped Host Controller Registers and optional PCI configuration registers. Note that the PCI configuration registers are only needed for PCI devices that implement the Host Controller. • Memory-mapped USB Host Controller Registers. This block of registers is memory-mapped into non-cacheable memory. This memory space must begin on a DWord (32-bit) boundary. This register space is divided into two sections: a set of read-only capability registers and a set of read/write operational registers. Table 42-1 describes each register space. Table 42-1: Offset Enhanced Interface Register Sets Register Set 0 to N-1 Capability Registers Explanation The capability registers specify the limits, restrictions, and capabilities of a host controller implementation. These values are used as parameters to the host controller driver. N to N+M-1 Note: Operational Registers The operational registers are used by system software to control and monitor the operational state of the host controller. Host controllers are not required to support exclusive-access mechanisms (such as PCI LOCK) for accesses to the memorymapped register space. Therefore, if software attempts exclusive-access mechanisms to the host controller memory-mapped register space, the results are undefined. • PCI Configuration Registers (for PCI devices). In addition to the normal PCI header, power management, and device-specific registers, two registers are needed in the PCI configuration space to support USB. The normal PCI header and device-specific registers are beyond the scope of this document (the UHPHS_CLASSC register is shown in this document). Note that HCD does not interact with the PCI configuration space. This space is used only by the PCI enumerator to identify the USB Host Controller, and assign the appropriate system resources. Table 42-2: Offset Register Mapping Register Name Access Reset Host Controller Capability Registers 0x00 UHPHS Host Controller Capability Register UHPHS_HCCAPBASE Read-only 0x0100 0010 0x04 UHPHS Host Controller Structural Parameters Register UHPHS_HCSPARAMS Read-only 0x0000 1116 0x08 UHPHS Host Controller Capability Parameters Register UHPHS_HCCPARAMS Read-only 0x0000 A010 0x0C Reserved – – – Host Controller Operational Registers 0x0008 0000 or 0x10 UHPHS USB Command Register UHPHS_USBCMD Read/Write(1) 0x14 UHPHS USB Status Register UHPHS_USBSTS Read/Write(1) 0x0000 1000 0x18 UHPHS USB Interrupt Enable Register UHPHS_USBINTR Read/Write 0x0000 0000 0x1C UHPHS USB Frame Index Register UHPHS_FRINDEX Read/Write 0x0000 0000 0x20 UHPHS Control Data Structure Segment Register UHPHS_CTRLDSSEGMENT Read/Write 0x0000 0000 0x24 UHPHS Periodic Frame List Base Address Register UHPHS_PERIODICLISTBASE Read/Write 0x0000 0000 0x28 UHPHS Asynchronous List Address Register UHPHS_ASYNCLISTADDR Read/Write 0x0000 0000 0x2C - 0x4F Reserved – – –  2017 Microchip Technology Inc. 0x0008 0B00(2) DS60001476B-page 1195 SAMA5D2 SERIES Table 42-2: Register Mapping (Continued) Offset Register Name Access Reset 0x50 UHPHS Configured Flag Register UHPHS_CONFIGFLAG Read/Write 0x0000 0000 0x54 UHPHS Port Status and Control Register 0 UHPHS_PORTSC_0 Read/Write(1) 0x58 UHPHS Port Status and Control Register 1 UHPHS_PORTSC_1 Read/Write(1) 0x5C UHPHS Port Status and Control Register 2 UHPHS_PORTSC_2 Read/Write(1) 0x90 EHCI Synopsys-Specific Registers 00 UHPHS_INSNREG00 Read/Write(1) 0x0000 0000 (1) 0x0020 0020 0x0000 2000 or 0x0000 3000(3) 0x0000 2000 or 0x0000 3000(3) 0x0000 2000 or 0x0000 3000(3) 0x94 EHCI Synopsys-Specific Registers 01 UHPHS_INSNREG01 Read/Write 0x98 EHCI Synopsys-Specific Registers 02 UHPHS_INSNREG02 Read/Write(1) (5) 0x9C EHCI Synopsys-Specific Registers 03 UHPHS_INSNREG03 Read/Write(1) 0x0000 0001 UHPHS_INSNREG04 Read/Write (1) 0x0000 0000 (1) 0x0000 1000 0xA0 EHCI Synopsys-Specific Registers 04 0xA4 EHCI Synopsys-Specific Registers 05 UHPHS_INSNREG05 Read/Write 0xA8 EHCI Synopsys-Specific Registers 06 UHPHS_INSNREG06 Read/Write(1) 0x0000 0000 UHPHS_INSNREG07 Read/Write (1) 0x0000 0000 Read/Write (1) 0x0000 0000 0xAC 0xB0 EHCI Synopsys-Specific Registers 07 EHCI Synopsys-Specific Registers 08 UHPHS_INSNREG08 Note 1: Field-dependent. 2: The default value depends on whether the Asynchronous Schedule Park Capability (ASPC) field in the UHPHS_HCCPARAMS register is enabled. Disabled (set to 0) = 0x0008 0000h; Enabled (set to 1) = 0x0008 0B00h. 3: The default value depends on the value of the Port Power Control (PPC) field in the UHPHS_HCSPARAMS register. 0x0000 2000h (with PPC set to 1); 0x0000 3000h (with PPC set to 0). 4: Software should not assume reserved bits are always 0 and should preserve these bits when writing to modifiable registers. 5: This value is determined by coreConsultant. DS60001476B-page 1196  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.1 UHPHS Host Controller Capability Register Name: UHPHS_HCCAPBASE Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 HCIVERSION 23 22 21 20 15 14 13 12 HCIVERSION – 7 6 5 4 CAPLENGTH CAPLENGTH: Capability Registers Length 10h: Default value. This field is used as an offset to add to register base to find the beginning of the Operational Register Space. HCIVERSION: Host Controller Interface Version Number 0100h: Default value. This is a two-byte field containing a BCD encoding of the EHCI revision number supported by this host controller. The most significant byte of this field represents a major revision and the least significant byte is the minor revision.  2017 Microchip Technology Inc. DS60001476B-page 1197 SAMA5D2 SERIES 42.7.2 UHPHS Host Controller Structural Parameters Register Name: UHPHS_HCSPARAMS Access: Read-only 31 30 29 28 27 26 25 24 18 – 10 17 9 16 P_INDICATOR 8 1 0 – 23 22 21 20 19 13 12 11 N_DP 15 14 N_CC 7 6 – N_PCC 5 4 PPC 3 2 N_PORTS This is a set of fields that are structural parameters: number of downstream ports, etc. N_PORTS: Number of Ports This field specifies the number of physical downstream ports implemented on this host controller. The value of this field determines how many port registers are addressable in the Operational Register Space. Valid values are in the range of 1H to FH. A zero in this field is undefined. PPC: Port Power Control This field indicates whether the host controller implementation includes port power control. A one in this bit indicates the ports have port power switches. A zero in this bit indicates the ports do not have port power switches. The value of this field affects the functionality of the Port Power field in each port status and control register (see Section 42.7.12 “UHPHS Port Status and Control Register”). N_PCC: Number of Ports per Companion Controller This field indicates the number of ports supported per companion host controller. It is used to indicate the port routing configuration to system software. For example, if N_PORTS has a value of 6 and N_CC has a value of 2, then N_PCC could have a value of 3. The convention is that the first N_PCC ports are assumed to be routed to companion controller 1, the next N_PCC ports to companion controller 2, etc. In the previous example, the N_PCC could have been 4, where the first four are routed to companion controller 1 and the last two are routed to companion controller 2. The number in this field must be consistent with N_PORTS and N_CC. N_CC: Number of Companion Controllers This field indicates the number of companion controllers associated with this USB 2.0 host controller. A zero in this field indicates there are no companion host controllers. Port-ownership hand-off is not supported. Only high-speed devices are supported on the host controller root ports. A value larger than zero in this field indicates there are companion USB 1.1 host controller(s). Port-ownership hand-offs are supported. High, Full- and Low-speed devices are supported on the host controller root ports. P_INDICATOR: Port Indicators This bit indicates whether the ports support port indicator control. When this bit is a 1, the port status and control registers include a read/ writeable field for controlling the state of the port indicator. See Section 42.7.12 “UHPHS Port Status and Control Register” for definition of the port indicator control field. N_DP: Debug Port Number Optional. This register identifies which of the host controller ports is the debug port. The value is the port number (1-based) of the debug port. A non-zero value in this field indicates the presence of a debug port. The value in this register must not be greater than N_PORTS (see above). DS60001476B-page 1198  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.3 UHPHS Host Controller Capability Parameters Register Name: UHPHS_HCCPARAMS Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 ASPC 1 PFLF 0 AC – 23 22 21 20 – 15 14 13 12 EECP 7 6 5 IST 4 This is a set of fields that are capability parameters: Multiple Mode control (time-base bit functionality), addressing capability, etc. AC: 64-bit Addressing Capability This field documents the addressing range capability of this implementation. The value of this field determines whether software should use 32-bit or 64-bit data structures. Values for this field have the following interpretation: 0: Data structures using 32-bit address memory pointers 1: Data structures using 64-bit address memory pointers Note: This is not tightly coupled with the UHPHS_USBBASE address register mapping control. The 64-bit Addressing Capability bit indicates whether the host controller can generate 64-bit addresses as a master. The UHPHS_USBBASE register indicates the host controller only needs to decode 32-bit addresses as a slave. PFLF: Programmable Frame List Flag The default value is implementation-dependent. If this bit is set to 0, then system software must use a frame list length of 1024 elements with this host controller. The UHPHS_USBCMD register Frame List Size field is a read-only register and should be set to 0. If set to 1, then system software can specify and use a smaller frame list and configure the host controller via the UHPHS_USBCMD register Frame List Size field. The frame list must always be aligned on a 4-kbyte page boundary. This requirement ensures that the frame list is always physically contiguous. ASPC: Asynchronous Schedule Park Capability The default value is Implementation dependent. If this bit is set to 1, then the host controller supports the park feature for high-speed queue heads in the Asynchronous Schedule. The feature can be disabled or enabled and set to a specific level by using the Asynchronous Schedule Park Mode Enable and Asynchronous Schedule Park Mode Count fields in the UHPHS_USBCMD register. IST: Isochronous Scheduling Threshold The default value is Implementation dependent. This field indicates, relative to the current position of the executing host controller, where software can reliably update the isochronous schedule. When bit [7] is 0, the value of the least significant 3 bits indicates the number of micro-frames a host controller can hold a set of isochronous data structures (one or more) before flushing the state. When bit [7] is set to 1, then host software assumes the host controller may cache an isochronous data structure for an entire frame. EECP: EHCI Extended Capabilities Pointer The default value is Implementation dependent. This optional field indicates the existence of a capabilities list. A value of 00h indicates no extended capabilities are implemented. A nonzero value in this register indicates the offset in PCI configuration space of the first EHCI extended capability. The pointer value must be 40h or greater if implemented to maintain the consistency of the PCI header defined for this class of device.  2017 Microchip Technology Inc. DS60001476B-page 1199 SAMA5D2 SERIES 42.7.4 UHPHS USB Command Register Name: UHPHS_USBCMD Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 ASPME 3 10 – 2 9 – 23 22 21 20 ITC 15 14 13 12 – 7 LHCR 6 IAAD 5 ASE 4 PSE FLS 8 ASPMC 1 HCRESET 0 RS The Command Register indicates the command to be executed by the serial bus host controller. Writing to the register causes a command to be executed. RS: Run/Stop (read/write) 0: Stop (default value). 1: Run. When set to 1, the Host Controller proceeds with execution of the schedule. The Host Controller continues execution as long as this bit is set to 1. When this bit is set to 0, the Host Controller completes the current and any actively pipelined transactions on the USB and then halts. The Host Controller must halt within 16 micro-frames after software clears the Run bit. The HC Halted bit in the status register indicates when the Host Controller has finished its pending pipelined transactions and has entered the stopped state. Software must not write 1 to this field unless the host controller is in the Halted state (i.e., HCHalted in the UHPHS_USBSTS register is 1). Doing so will yield undefined results. HCRESET: Host Controller Reset (read/write) This control bit is used by software to reset the host controller. The effects of this on Root Hub registers are similar to a Chip Hardware Reset. When software writes a 1 to this bit, the Host Controller resets its internal pipelines, timers, counters, state machines, etc. to their initial value. Any transaction currently in progress on USB is immediately terminated. A USB reset is not driven on downstream ports. PCI Configuration registers are not affected by this reset. All operational registers, including port registers and port state machines, are set to their initial values. Port ownership reverts to the companion host controller(s) with side effects. Software must reinitialize the host controller in order to return the host controller to an operational state. This bit is set to 0 by the Host Controller when the reset process is complete. Software cannot terminate the reset process early by writing a 0 to this register. Software should not set this bit to 1 when the HCHalted bit in the UHPHS_USBSTS register is 0. Attempting to reset an actively running host controller will result in undefined behavior. FLS: Frame List Size (read/write or read-only) This field is R/W only if Programmable Frame List Flag in the UHPHS_HCCPARAMS registers is set to 1. This field specifies the size of the frame list. The size of the frame list controls which bits in the Frame Index Register should be used for the Frame List Current index. 00b: 1024 elements (4096 bytes) (default value). 01b: 512 elements (2048 bytes). 10b: 256 elements (1024 bytes), for resource-constrained environments. 11b: Reserved. PSE: Periodic Schedule Enable (read/write) This bit controls whether the host controller skips processing the Periodic Schedule. 0: Do not process the Periodic Schedule (default value). 1: Use the UHPHS_PERIODICLISTBASE register to access the Periodic Schedule. ASE: Asynchronous Schedule Enable (read/write) DS60001476B-page 1200  2017 Microchip Technology Inc. SAMA5D2 SERIES This bit controls whether the host controller skips processing the Asynchronous Schedule. 0: Do not process the Asynchronous Schedule (default value). 1: Use the UHPHS_ASYNCLISTADDR register to access the Asynchronous Schedule. IAAD: Interrupt on Async Advance Doorbell (read/write) This bit is used as a doorbell by software to tell the host controller to issue an interrupt the next time it advances asynchronous schedule. Software must write a 1 to this bit to ring the doorbell. When the host controller has evicted all appropriate cached schedule state, it sets the Interrupt on Async Advance status bit in the UHPHS_USBSTS register. If the Interrupt on Async Advance Enable bit in the UHPHS_USBINTR register is set to 1, then the host controller will assert an interrupt at the next interrupt threshold. The host controller sets this bit to 0 after it has set the Interrupt on Async Advance status bit in the UHPHS_USBSTS register to 1. Software should not write a 1 to this bit when the asynchronous schedule is disabled. Doing so will yield undefined results. LHCR: Light Host Controller Reset (optional) (read/write) This control bit is not required. If implemented, it allows the driver to reset the EHCI controller without affecting the state of the ports or the relationship to the companion host controllers. For example, the UHPHS_PORTSC registers should not be reset to their default values and the CF bit setting should not go to 0 (retaining port ownership relationships). A host software read of this bit as 0 indicates the Light Host Controller Reset has completed and it is safe for host software to reinitialize the host controller. A host software read of this bit as 1 indicates the Light Host Controller Reset has not yet completed. If not implemented, a read of this field will always return a 0. ASPMC: Asynchronous Schedule Park Mode Count (optional) (read/write or read-only) If the Asynchronous Park Capability bit in the UHPHS_HCCPARAMS register is set to 1, then this field defaults to 3h and is R/W. Otherwise it defaults to 0 and is RO. It contains a count of the number of successive transactions the host controller is allowed to execute from a high-speed queue head on the Asynchronous schedule before continuing traversal of the Asynchronous schedule. Valid values are 1h to 3h. Software must not write a 0 to this bit when Park Mode Enable is set to 1 as this will result in undefined behavior. ASPME: Asynchronous Schedule Park Mode Enable (optional) (read/write or read-only) If the Asynchronous Park Capability bit in the UHPHS_HCCPARAMS register is set to 1, then this bit defaults to a 1h and is R/W. Otherwise the bit must be a 0 and is RO. Software uses this bit to enable or disable Park mode. When this bit is set to 1, Park mode is enabled. When this bit is set to 0, Park mode is disabled. ITC: Interrupt Threshold Control (read/write) This field is used by system software to select the maximum rate at which the host controller will issue interrupts. The only valid values are defined below. If software writes an invalid value to this register, the results are undefined. Value Maximum Interrupt Interval 00h Reserved 01h 1 micro-frame 02h 2 micro-frames 04h 4 micro-frames 08h 8 micro-frames (default, equates to 1 ms) 10h 16 micro-frames (2 ms) 20h 32 micro-frames (4 ms) 40h 64 micro-frames (8 ms) Any other value in this register yields undefined results. Software modifications to this bit while HCHalted bit is equal to 0 results in undefined behavior.  2017 Microchip Technology Inc. DS60001476B-page 1201 SAMA5D2 SERIES 42.7.5 UHPHS USB Status Register Name: UHPHS_USBSTS Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 1 USBERRINT 0 USBINT – 23 22 21 20 – 15 ASS 7 14 PSS 6 – 13 RCM 5 IAA 12 HCHLT 4 HSE – 3 FLR 2 PCD This register indicates pending interrupts and various states of the Host Controller. The status resulting from a transaction on the serial bus is not indicated in this register. Software sets a bit to 0 in this register by writing a 1 to it. USBINT: USB Interrupt (read/write clear) The Host Controller sets this bit to 1 on the completion of a USB transaction, which results in the retirement of a Transfer Descriptor that had its IOC bit set. The Host Controller also sets this bit to 1 when a short packet is detected (the actual number of bytes received was less than the expected number of bytes). USBERRINT: USB Error Interrupt (read/write clear) The Host Controller sets this bit to 1 when completion of a USB transaction results in an error condition (e.g., error counter underflow). If the TD on which the error interrupt occurred also had its IOC bit set, both this bit and USBINT bit are set. PCD: Port Change Detect (read/write clear) The Host Controller sets this bit to 1 when any port for which the Port Owner bit is set to 0 (see Section 42.7.12 “UHPHS Port Status and Control Register”) has a change bit transition from 0 to 1 or a Force Port Resume bit transition from 0 to 1 as a result of a J-K transition detected on a suspended port. This bit will also be set as a result of the Connect Status Change being set to 1 after system software has relinquished ownership of a connected port by writing 1 to a port's Port Owner bit. This bit is allowed to be maintained in the Auxiliary power well. Alternatively, it is also acceptable that on a D3 to D0 transition of the EHCI HC device, this bit is loaded with the OR of all of the PORTSC change bits (including: Force Port Resume, Over-Current Change, Enable/ Disable Change and Connect Status Change). FLR: Frame List Rollover (read/write clear) The Host Controller sets this bit to 1 when the Frame List Index (see Section 42.7.7 “UHPHS USB Frame Index Register”) rolls over from its maximum value to 0. The exact value at which the rollover occurs depends on the frame list size. For example, if the frame list size (as programmed in the Frame List Size field of the UHPHS_USBCMD register) is 1024, the Frame Index Register rolls over every time FRINDEX[13] toggles. Similarly, if the size is 512, the Host Controller sets this bit to 1 every time FRINDEX[12] toggles. HSE: Host System Error (read/write clear) The Host Controller sets this bit to 1 when a serious error occurs during a host system access involving the Host Controller module. In a PCI system, conditions that set this bit to 1 include PCI Parity error, PCI Master Abort, and PCI Target Abort. When this error occurs, the Host Controller clears the Run/Stop bit in the Command register to prevent further execution of the scheduled TDs. IAA: Interrupt on Async Advance (read/write clear) 0: Default. System software can force the host controller to issue an interrupt the next time the host controller advances the asynchronous schedule by writing 1 to the Interrupt on the Async Advance Doorbell bit in the UHPHS_USBCMD register. This status bit indicates the assertion of that interrupt source. HCHLT: HCHalted (read-only) 1: Default. DS60001476B-page 1202  2017 Microchip Technology Inc. SAMA5D2 SERIES This bit is 0 whenever the Run/Stop bit is 1. The Host Controller sets this bit to 1 after it has stopped executing as a result of the Run/Stop bit being set to 0, either by software or by the Host Controller hardware (e.g. internal error). RCM: Reclamation (read-only) 0: Default. This is a read-only status bit used to detect any empty asynchronous schedule. PSS: Periodic Schedule Status (read-only) 0: Default. The bit reports the current real status of the Periodic Schedule. If this bit is set to 0, then the status of the Periodic Schedule is disabled. If this bit is set to 1, then the status of the Periodic Schedule is enabled. The Host Controller is not required to immediately disable or enable the Periodic Schedule when software transitions the Periodic Schedule Enable bit in the UHPHS_USBCMD register. When this bit and the Periodic Schedule Enable bit are the same value, the Periodic Schedule is either enabled (1) or disabled (0). ASS: Asynchronous Schedule Status (read-only) 0: Default. The bit reports the current real status of the Asynchronous Schedule. If this bit is set to 0, then the status of the Asynchronous Schedule is disabled. If this bit is set to 1, then the status of the Asynchronous Schedule is enabled. The Host Controller is not required to immediately disable or enable the Asynchronous Schedule when software transitions the Asynchronous Schedule Enable bit in the UHPHS_USBCMD register. When this bit and the Asynchronous Schedule Enable bit are the same value, the Asynchronous Schedule is either enabled (1) or disabled (0).  2017 Microchip Technology Inc. DS60001476B-page 1203 SAMA5D2 SERIES 42.7.6 UHPHS USB Interrupt Enable Register Name: UHPHS_USBINTR Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 FLRE 2 PCIE 1 USBEIE 0 USBIE – 23 22 21 20 15 14 13 12 – – 7 6 – 5 IAAE 4 HSEE This register enables and disables reporting of the corresponding interrupt to the software. When a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. Interrupt sources that are disabled in this register still appear in the UHPHS_USBSTS to allow the software to poll for events. Each interrupt enable bit description indicates whether it is dependent on the interrupt threshold mechanism. For all enable register bits, 1= Enabled, 0= Disabled. USBIE: USB Interrupt Enable When this bit is set to 1, and the USBINT bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt at the next interrupt threshold. The interrupt is acknowledged by software clearing the USBINT bit. USBEIE: USB Error Interrupt Enable When this bit is set to 1, and the USBERRINT bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt at the next interrupt threshold. The interrupt is acknowledged by software clearing the USBERRINT bit. PCIE: Port Change Interrupt Enable When this bit is set to 1, and the Port Change Detect bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt. The interrupt is acknowledged by software clearing the Port Change Detect bit. FLRE: Frame List Rollover Enable When this bit is set to 1, and the Frame List Rollover bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt. The interrupt is acknowledged by software clearing the Frame List Rollover bit. HSEE: Host System Error Enable When this bit is set to 1, and the Host System Error Status bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt. The interrupt is acknowledged by software clearing the Host System Error bit. IAAE: Interrupt on Async Advance Enable When this bit is set to 1, and the Interrupt on Async Advance bit in the UHPHS_USBSTS register is 1, the host controller will issue an interrupt at the next interrupt threshold. The interrupt is acknowledged by software clearing the Interrupt on Async Advance bit. DS60001476B-page 1204  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.7 UHPHS USB Frame Index Register Name: UHPHS_FRINDEX Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 10 9 8 2 1 0 – 23 22 21 20 – 15 14 13 12 11 FI – 7 6 5 4 3 FI This register is used by the host controller to index into the periodic frame list. The register updates every 125 µs (once each micro-frame). Bits [N:3] are used to select a particular entry in the Periodic Frame List during periodic schedule execution. The number of bits used for the index depends on the size of the frame list as set by system software in the Frame List Size field in the UHPHS_USBCMD register (see Section 42.7.4 “UHPHS USB Command Register”). This register must be written as a DWord. Byte writes produce undefined results. This register cannot be written unless the Host Controller is in the Halted state as indicated by the HCHalted bit (UHPHS_USBSTS register, Section 42.7.5 “UHPHS USB Status Register”). A write to this register while the Run/Stop bit is set to 1 (UHPHS_USBCMD register, Section 42.7.4 “UHPHS USB Command Register”) produces undefined results. Writes to this register also affect the SOF value. FI: Frame Index The value in this register increments at the end of each time frame (e.g. micro-frame). Bits [N:3] are used for the Frame List current index. This means that each location of the frame list is accessed eight times (frames or micro-frames) before moving to the next index. The following illustrates values of N based on the value of the Frame List Size field in the UHPHS_USBCMD register. USBCMD [Frame List Size] Number Elements N 00b (1024) 12 01b (512) 11 10b (256) 10 11b Reserved – The SOF frame number value for the bus SOF token is derived or alternatively managed from this register. The value of FRINDEX must be 125 µs (1 micro-frame) ahead of the SOF token value. The SOF value may be implemented as an 11-bit shadow register. For this discussion, this shadow register is 11 bits and is named SOFV. SOFV updates every eight micro-frames (1 millisecond). An example implementation to achieve this behavior is to increment SOFV each time the FRINDEX[2:0] increments from 0 to 1. Software must use the value of FRINDEX to derive the current micro-frame number, both for high-speed isochronous scheduling purposes and to provide the “get micro-frame number” function required for client drivers. Therefore, the value of FRINDEX and the value of SOFV must be kept consistent if chip is reset or software writes to FRINDEX. Writes to FRINDEX must also write-through FRINDEX[13:3] to SOFV[10:0]. In order to keep the update as simple as possible, software should never write a FRINDEX value where the three least significant bits are 111b or 000b.  2017 Microchip Technology Inc. DS60001476B-page 1205 SAMA5D2 SERIES 42.7.8 UHPHS Control Data Structure Segment Register Name: UHPHS_CTRLDSSEGMENT Access: Read/Write This 32-bit register corresponds to the most significant address bits [63:32] for all EHCI data structures. If the 64-bit Addressing Capability field in UHPHS_HCCPARAMS is set to 0, then this register is not used. Software cannot write to it and a read from this register will return zeros. If the 64-bit Addressing Capability field in UHPHS_HCCPARAMS is 1, then this register is used with the link pointers to construct 64-bit addresses to EHCI control data structures. This register is concatenated with the link pointer from either the UHPHS_PERIODICLISTBASE, UHPHS_ASYNCLISTADDR, or any control data structure link field to construct a 64-bit address. This register must be written as a DWord. Byte writes produce undefined results. This register allows the host software to locate all control data structures within the same 4-Gigabyte memory segment. DS60001476B-page 1206  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.9 UHPHS Periodic Frame List Base Address Register Name: UHPHS_PERIODICLISTBASE Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 1 0 BA 23 22 21 20 15 14 13 12 BA BA 7 6 – 5 4 3 2 – This 32-bit register contains the beginning address of the Periodic Frame List in the system memory. If the host controller is in 64-bit mode (as indicated by a 1 in the 64-bit Addressing Capability field in the UHPHS_HCCSPARAMS register), then the most significant 32 bits of every control data structure address comes from the UHPHS_CTRLDSSEGMENT register (see Section 42.7.8 “UHPHS Control Data Structure Segment Register”). System software loads this register prior to starting the schedule execution by the Host Controller. The memory structure referenced by this physical memory pointer is assumed to be 4-Kbyte aligned. The contents of this register are combined with the Frame Index Register (UHPHS_FRINDEX) to enable the Host Controller to step through the Periodic Frame List in sequence. This register must be written as a DWord. Byte writes produce undefined results. BA: Base Address (Low) These bits correspond to memory address signals [31:12], respectively.  2017 Microchip Technology Inc. DS60001476B-page 1207 SAMA5D2 SERIES 42.7.10 UHPHS Asynchronous List Address Register Name: UHPHS_ASYNCLISTADDR Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 – 1 0 LPL 23 22 21 20 15 14 13 12 LPL LPL 7 6 LPL 5 4 This 32-bit register contains the address of the next asynchronous queue head to be executed. If the host controller is in 64-bit mode (as indicated by a 1 in the 64-bit Addressing Capability field in the UHPHS_HCCPARAMS register), then the most significant 32 bits of every control data structure address comes from the UHPHS_CTRLDSSEGMENT register (See Section 42.7.8 “UHPHS Control Data Structure Segment Register”). Bits [4:0] of this register cannot be modified by system software and will always return a zero when read. The memory structure referenced by this physical memory pointer is assumed to be 32-byte (cache line) aligned. This register must be written as a DWord. Byte writes produce undefined results. LPL: Link Pointer Low These bits correspond to memory address signals [31:5], respectively. This field may only reference a Queue Head (QH). DS60001476B-page 1208  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.11 UHPHS Configure Flag Register Name: UHPHS_CONFIGFLAG Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 CF – 23 22 21 20 – 15 14 13 12 – 7 6 5 4 – This register is in the auxiliary power well. It is only reset by hardware when the auxiliary power is initially applied or in response to a host controller reset. CF: Configure Flag (read/write) Host software sets this bit as the last action in its process of configuring the Host Controller. This bit controls the default port-routing control logic. Bit values and side-effects are listed below. 0: Port routing control logic default-routes each port to an implementation-dependent classic host controller (default value). 1: Port routing control logic default-routes all ports to this host controller.  2017 Microchip Technology Inc. DS60001476B-page 1209 SAMA5D2 SERIES 42.7.12 UHPHS Port Status and Control Register Name: UHPHS_PORTSC_x[x = 0..2] Access: Read/Write 31 30 29 28 27 26 19 18 25 24 17 16 9 – 1 CSC 8 PR 0 CCS – 23 – 15 22 WKOC_E 14 21 WKDSCNNT_E PIC 7 SUS 6 FPR 13 PO 5 OCC 20 WKCNNT_E 12 PP 4 OCA PTC 11 10 LS 3 PEDC 2 PED A host controller must implement one or more port registers. The number of port registers implemented by a particular instantiation of a host controller is documented in the UHPHS_HCSPARAMS register (Section 42.7.2 “UHPHS Host Controller Structural Parameters Register”). Software uses this information as an input parameter to determine how many ports need to be serviced. All ports have the structure defined below. This register is in the auxiliary power well. It is only reset by hardware when the auxiliary power is initially applied or in response to a host controller reset. The initial conditions of a port are: • No device connected • Port disabled If the port has port power control, software cannot change the state of the port until after it applies power to the port by setting port power to a 1. Software must not attempt to change the state of the port until after power is stable on the port. The host is required to have power stable to the port within 20 milliseconds of the 0 to 1 transition. Note 1: When a device is attached, the port state transitions to the connected state and system software will process this as with any status change notification. 2: If a port is being used as the Debug Port, then the port may report device connected and enabled when the Configured Flag is set to 0. CCS: Current Connect Status (read-only) 0: No device is present (default value). 1: Device is present on port. This value reflects the current state of the port, and may not correspond directly to the event that caused the Connect Status Change bit (Bit 1) to be set. This field is 0 if Port Power is 0. CSC: Connect Status Change (read/write clear) 0: No change (default value). 1: Change in Current Connect Status. Indicates a change has occurred in the port’s Current Connect Status. The host controller sets this bit for all changes to the port device connect status, even if system software has not cleared an existing connect status change. For example, the insertion status changes twice before system software has cleared the changed condition, hub hardware will be “setting” an already-set bit (i.e., the bit will remain set). Software sets this bit to 0 by writing a 1 to it. This field is 0 if Port Power is 0. DS60001476B-page 1210  2017 Microchip Technology Inc. SAMA5D2 SERIES PED: Port Enabled/Disabled (read/write) 0: Disable (default value). 1: Enable. Ports can only be enabled by the host controller as a part of the reset and enable. Software cannot enable a port by writing a 1 to this field. The host controller will only set this bit to 1 when the reset sequence determines that the attached device is a high-speed device. Ports can be disabled by either a fault condition (disconnect event or other fault condition) or by host software. Note that the bit status does not change until the port state actually changes. There may be a delay in disabling or enabling a port due to other host controller and bus events. When the port is disabled (0b), downstream propagation of data is blocked on this port, except for reset. This field is 0 if Port Power is 0. PEDC: Port Enable/Disable Change (read/write clear) 0: No change (default value). 1: Port enabled/disabled status has changed. For the root hub, this bit gets set to 1 only when a port is disabled due to the appropriate conditions existing at the EOF2 point (See Chapter 11 of the USB Specification for the definition of a Port Error). Software clears this bit by writing a 1 to it. This field is 0 if Port Power is 0. OCA: Over-current Active (read-only) 0: This port does not have an over-current condition (default value). 1: This port currently has an over-current condition. This bit will automatically transition from 1 to 0 when the over current condition is removed. OCC: Over-current Change (read/write clear) 0: Default value. 1: This bit gets set to 1 when there is a change to Over-current Active. Software clears this bit by writing 1 to this bit position. FPR: Force Port Resume (read/write) 0: No resume (K-state) detected/driven on port (default value). 1: Resume detected/driven on port. This functionality defined for manipulating this bit depends on the value of the Suspend bit. For example, if the port is not suspended (Suspend and Enabled bits are set to 1) and software transitions this bit to 1, then the effects on the bus are undefined. Software sets this bit to a 1 to drive resume signaling. The Host Controller sets this bit to 1 if a J-to-K transition is detected while the port is in the Suspend state. When this bit transitions to 1 because a J-to-K transition is detected, the Port Change Detect bit in the UHPHS_USBSTS register is also set to 1. If software sets this bit to 1, the host controller must not set the Port Change Detect bit. Note that when the EHCI controller owns the port, the resume sequence follows the defined sequence documented in the USB Specification Revision 2.0. The resume signaling (Full-speed 'K') is driven on the port as long as this bit remains set to 1. Software must appropriately time the Resume and set this bit to 0 when the appropriate amount of time has elapsed. Writing a 0 (from 1) causes the port to return to High-Speed mode (forcing the bus below the port into a high-speed idle).This bit will remain set to 1 until the port has switched to the high-speed idle. The host controller must complete this transition within 2 milliseconds of software setting this bit to 0. This field is 0 if Port Power is 0. SUS: Suspend (read/write) 0: Port not in suspend state (default value). 1: Port in suspend state.  2017 Microchip Technology Inc. DS60001476B-page 1211 SAMA5D2 SERIES Port Enabled Bit and Suspend bit of this register define the port states as follows: Bits [Port Enabled, Suspend] Port State 0X Disable 10 Enable 11 Suspend When in suspend state, downstream propagation of data is blocked on this port, except for port reset. The blocking occurs at the end of the current transaction, if a transaction was in progress when this bit was written to 1. In the suspend state, the port is sensitive to resume detection. Note that the bit status does not change until the port is suspended and that there may be a delay in suspending a port if there is a transaction currently in progress on the USB. A write of 0 to this bit is ignored by the host controller. The host controller will unconditionally set this bit to 0 when: • Software sets the Force Port Resume bit to 0 (from 1). • Software sets the Port Reset bit to 1 (from 0). If host software sets this bit to 1 when the port is not enabled (i.e., Port Enabled bit set to 0), the results are undefined. This field is 0 if Port Power is set to 0. PR: Port Reset (read/write) 0: Port is not in Reset (default value). 1: Port is in Reset. When software writes a 1 to this bit (from 0), the bus reset sequence as defined in the USB Specification Revision 2.0 is started. Software writes a 0 to this bit to terminate the bus reset sequence. Software must keep this bit set to 1 long enough to ensure the reset sequence, as specified in the USB Specification Revision 2.0, completes. Note: when software writes this bit to 1, it must also write 0 to the Port Enable bit. When software writes a 0 to this bit, there may be a delay before the bit status changes to 0. The bit status will not read as 0 until after the reset has completed. If the port is in High-Speed mode after reset is complete, the host controller will automatically enable this port (e.g. set the Port Enable bit to 1). A host controller must terminate the reset and stabilize the state of the port within 2 milliseconds of software transitioning this bit from 1 to 0. For example: if the port detects that the attached device is high-speed during reset, then the host controller must have the port in the enabled state within 2 ms of software writing this bit to 0. The HCHalted bit in the UHPHS_USBSTS register should be set to 0 before software attempts to use this bit. The host controller may hold Port Reset asserted to 1 when the HCHalted bit is 1. This field is 0 if Port Power is 0. LS: Line Status (read-only) These bits reflect the current logical levels of the D+ (bit 11) and D- (bit 10) signal lines. These bits are used for detection of low-speed USB devices prior to the port reset and enable sequence. This field is valid only when the port enable bit is 0 and the current connect status bit is set to 1. Bits are encoded as follows: Value USB State Interpretation 00b SE0 Not a low-speed device, perform EHCI reset 10b J-state Not a low-speed device, perform EHCI reset 01b K-state Low-speed device, release ownership of port 11b Undefined Not a low-speed device, perform EHCI reset This value of this field is undefined if Port Power is 0. PP: Port Power (read/write or read-only) DS60001476B-page 1212  2017 Microchip Technology Inc. SAMA5D2 SERIES The function of this bit depends on the value of the Port Power Control (PPC) field in the UHPHS_HCSPARAMS register. The behavior is as follows: PPC PP 0b 1b Operation Read-only. Host controller does not have port power control switches. Each port is hard-wired to power. Read/write. 1b 1b/0b Host controller has port power control switches. This bit represents the current setting of the switch (0 = off, 1 = on). When power is not available on a port (i.e., PP at 0), the port is non-functional and will not report attaches, detaches, etc. When an over-current condition is detected on a powered port and PPC is set to 1, the PP bit in each affected port may be transitioned by the host controller from 1 to 0 (removing power from the port). PO: Port Owner (read/write) 0: This bit unconditionally goes to a 0 when the Configured bit in the UHPHS_CONFIGFLAG register makes a 0 to 1 transition. 1: This bit unconditionally goes to 1 whenever the Configured bit is 0 (default value). System software uses this field to release ownership of the port to a selected host controller (in the event that the attached device is not a high-speed device). Software writes 1 to this bit when the attached device is not a high-speed device. A 1 in this bit means that a companion host controller owns and controls the port.  2017 Microchip Technology Inc. DS60001476B-page 1213 SAMA5D2 SERIES PIC: Port Indicator Control (read/write) 00b: Default value. Writing to these bits has no effect if the P_INDICATOR bit in the UHPHS_HCSPARAMS register is set to 0. If the P_INDICATOR bit is set to 1, then the bits are encoded as follows: Value Meaning 00b Port indicators are off 01b Amber 10b Green 11b Undefined Refer to the USB Specification Revision 2.0 for a description on how these bits are to be used. This field is 0 if Port Power is 0. PTC: Port Test Control (read/write) 0000b: Default value. When this field is set to 0, the port is NOT operating in a test mode. A non-zero value indicates that it is operating in test mode and the specific test mode is indicated by the specific value. Test mode bits are encoded as follows (0110b - 1111b are reserved): Value Test Mode 0000b Test mode not enabled 0001b Test J_STATE 0010b Test K_STATE 0011b Test SE0_NAK 0100b Test Packet 0101b Test FORCE_ENABLE Refer to the USB Specification Revision 2.0, Chapter 7, for details on each test mode. WKCNNT_E: Wake on Connect Enable (read/write) 0: Default value. Writing this bit to 1 enables the port to be sensitive to device connects as wakeup events. This field is 0 if Port Power is 0. WKDSCNNT_E: Wake on Disconnect Enable (read/write) 0: Default value. Writing this bit to 1 enables the port to be sensitive to device disconnects as wakeup events. This field is 0 if Port Power is 0. WKOC_E: Wake on Over-current Enable (read/write) 0: Default value. Writing this bit to 1 enables the port to be sensitive to over-current conditions as wakeup events. This field is 0 if Port Power is 0. DS60001476B-page 1214  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.13 EHCI: REG00 - Programmable Microframe Base Value Name: UHPHS_INSNREG00 Access: Read/Write 31 30 29 28 27 26 25 24 17 16 9 8 1 0 En – 23 22 15 14 21 20 19 18 13 12 11 10 – Debug MFC_8 Debug 7 6 5 MFC_16 4 MFC_16 3 2 The Programmable Microframe Base Value is used to change the microframe length value (default is microframe SOF = 125 µs) in order to reduce simulation time. En: Enable this Register 0: Register disabled (default value). 1: Register enabled. Note: Do not enable this register for the gate-level netlist. MFC_16: Microframe Counter with Word Byte Interface This value is used as the 1-microframe counter with 16-bit interface. MFC_8: Microframe Counter with Byte Interface This value is used as the 1-microframe counter with 8-bit interface. Debug: Debug Purposes This field is used for debug purposes only. In Heterogeneous mode, if the per port clock gets out of sync (but still within the ppm limits) of the phy_clk, then the per port SOF counter needs some correction relative to the global SOF counter. The RTL corrects itself if this happens. This field controls the SOF correction, in case some debugging is required for the correction. If bit 14 is set to 1, then it enables the RTL to use the value in bits 19:15 to perform the correction. In normal operating mode, these bits should not be written. Note: The “value” in bits [31:1] must be programmed as follows: (value + 32/64) * Clock Period = microframe timer duration Factor 32 is used for a 16-bit interface and factor 64 is used for an 8-bit interface. For example, for the full (125 µs) microframe duration: – In 8-bit, 60-MHz mode, the value is h1D0C (=7436), so (7436 + 64) * 16.67 ns = 125 µs – In 16-bit, 30-MHz mode, the value is hE86 (=3718), so (3718 + 32) * 33.33 ns = 125 µs For a 50 µs microframe duration: – In 8-bit, 60-MHz mode, the value is hB77 (=2395), so (2395 + 64) * 16.67 ns = 50 µs – In 16-bit, 30-MHz mode, the value is h5BC (=1468), so (1468 + 32) * 33.33 ns = 50 µs  2017 Microchip Technology Inc. DS60001476B-page 1215 SAMA5D2 SERIES 42.7.14 EHCI: REG01 - Programmable Packet Buffer OUT/IN Thresholds Name: UHPHS_INSNREG01 Access: Read/Write 31 30 29 23 22 21 15 14 13 7 6 5 28 27 Out_Threshold 20 19 Out_Threshold 12 11 In_Threshold 4 3 26 25 24 18 17 16 10 9 8 2 1 0 In_Threshold Programmable Packet Buffer OUT/IN thresholds (in CONFIG1 mode only, not applicable in Config2 mode). The value specified here is the number of DWORDs (32-bit entries). In_Threshold: Amount of Data Available in the IN Packet Buffer The IN threshold is used to start the memory transfer as soon as the IN threshold amount of data is available in the Packet Buffer. It is also used to disconnect the data write, if the threshold amount of data is not available in the Packet Buffer. Out_Threshold: Amount of Data Available in the OUT Packet Buffer The OUT threshold is used to start the USB transfer as soon as the OUT threshold amount of data is fetched from system memory. It is also used to disconnect the data fetch, if the threshold amount of space is not available in the Packet Buffer. The minimum OUT and IN threshold amount that can be programmed through INSN registers is 16 bytes. For INCRX configurations, the minimum threshold amount that can be programmed is the highest possible INCRX burst value. For example, if the value of the strap signals {ss_ena_incr16_i, ss_ena_incr8_i, ss_ena_incr4_i} is 3'b011 (for example, INCR16 burst is disabled, INCR8/INCR4 bursts are enabled), then the minimum OUT and IN threshold values should be 32 bytes (8 DWords). OUT and IN threshold values can be equal to the packet buffer depth only when one of the following conditions is met: • The packet buffer depth is equal to 512 bytes and isochronous/interrupt transactions are not initiated by the host controller. • The packet buffer depth is equal to 1024 bytes. The threshold default value depends on one of the following packet buffer configurations: • 1024 bytes depth, 256 bytes IN and OUT thresholds • 512 bytes depth, 128 bytes IN and OUT thresholds • 256 bytes depth, 64 bytes IN and OUT thresholds • 128 bytes depth, 64 bytes IN and OUT thresholds • 64 bytes depth, 60 bytes IN and OUT thresholds For INCRX configurations, the Break Memory Transfer bit is always enabled. Depending on the different packet buffer settings, not all MSB bits are used. DS60001476B-page 1216  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.15 EHCI: REG02 - Programmable Packet Buffer Depth Name: UHPHS_INSNREG02 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 1 0 – 23 22 21 20 15 14 13 12 – – 7 6 Dwords 5 4 3 2 Dwords Programmable Packet Buffer Depth (in CONFIG1 mode only, not applicable in Config2 mode). The value specified here is the number of DWORDs (32-bit entries). Dwords: Number of Entries For a maximum 256 entries for 1-Kbyte packet buffer, bits [8:0] are sufficient.  2017 Microchip Technology Inc. DS60001476B-page 1217 SAMA5D2 SERIES 42.7.16 EHCI: REG03 Name: UHPHS_INSNREG03 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 Tx_Tx 3 10 9 Per_Frame 1 8 TA_Offset 0 Break_Mem – 23 22 21 20 – 15 – 7 14 EN_CK256 6 13 Ignore_LS 5 12 4 TA_Offset 2 The default value for INSNREG03[0] depends on the host core configuration. So, if INCRx support is enabled, this bit is 1 after reset. Otherwise, it should stay at 0. Break_Mem: Break Memory Transfer (in CONFIG1 mode only, not applicable in CONFIG2 mode) 0: Disables this function. 1: Enables this function. Used in conjunction with INSNREG01 to enable breaking memory transactions into chunks once the OUT/IN threshold value is reached. TA_Offset: Time-Available Offset This value indicates the additional number of bytes to be accommodated for the time-available calculation. The USB traffic on the bus can be started only when sufficient time is available to complete the packet within the EOF1 point. Refer to the USB 2.0 specification for details of the EOF1 point. This time-available calculation is done in the hardware, and can be further offset by programming a value in this location. Note: Time-available calculation is added for future flexibility. The application is not required to program this field by default. Per_Frame: Periodic Frame List Fetch In CONFIG1 mode only (“EHCI Descriptor/Data Prefetching” is disabled in core configuration), setting this bit forces the host controller to fetch the periodic frame list in every microframe of a frame. If not set, then the periodic frame list is fetched only in microframe 0 of every frame. The default is 0 (not set). This bit can be changed only during core initialization and should not be changed afterwards. Tx_Tx: Tx-Tx turnaround Delay Add-on This field specifies the extra delays in phy_clks to be added to the “Transmit to Transmit turnaround delay” value maintained in the core. The default value of this register field is 0. This default value of 0 is sufficient for most PHYs. But for some PHYs which enter wait states during the token packet, it may be required to program a value greater than 0 to meet the transmit-to-transmit minimum turnaround time. It is recommended to use default value 0 and to change it only if there is an issue with minimum transmit-to-transmit turnaround time. This value should be programmed during core initialization and should not be changed afterwards. DS60001476B-page 1218  2017 Microchip Technology Inc. SAMA5D2 SERIES Ignore_LS: Ignore Linestate during TestSE0 Nak When set to 1 (default), the core ignores the linestate checking when transmitting SOF in SE0_NAK Test mode. When set to 0, the port state machine disables the port if it does not find the linestate to be in SE0 when transmitting SOF during the SE0_NAK test. While performing impedance measurement during the SE0_NAK test, the linestate could go to non SE0 forcing the core to disable the port. This bit is used to control the port behavior during this operation. EN_CK256: Enable 256 Clock Checking This bit controls the End of Resume sequence of the EHCI host controller. By default, the value of this bit is 0 and during the End of Resume sequence, the host controller waits for SE0 on the linestate before switching the PHY to High-Speed. When set to 1, during the End of Resume sequence, the controller waits for SE0 or 256 clocks before switching the PHY to High-Speed. Setting this bit to 1 enables the 256-clock check. Some of the UTMI PHYs do not present SE0 on the linestate during the End of Resume sequence. For such PHYs, this bit should be set, so that the core does not wait forever for SE0. This bit should be set only during initialization.  2017 Microchip Technology Inc. DS60001476B-page 1219 SAMA5D2 SERIES 42.7.17 EHCI: REG04 Name: UHPHS_INSNREG04 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 – 23 22 21 20 – 15 14 13 12 – 7 6 – 5 4 3 2 EN_AutoFunc NAK_RF – SDPE_TIME 1 0 HCSPARAMS_ HCCPARAMS_ W BW Bits [2:0] are used for debug purposes. Bits [(5+UHC2_N_PORTS):4] are functional bits where UHC2_N_PORTS indicates the number of physical USB ports. HCSPARAMS_W: HCSPARAMS Write When set, the HCSPARAMS register becomes writable. Upon system reset, this bit is 0. HCCPARAMS_BW: HCCPARAMS Bits Write When set, the HCCPARAMS register's bits 17, 15:4, and 2:0 become writable. Upon system reset, these bits are 0. SDPE_TIME: Scales Down Port Enumeration Time When set, Scales Down Port Enumeration Time is enabled. Reset value is 1’b0. Note: This bit can be used for both RTL and Gate level simulations. NAK_RF: NAK Reload Fix (Read/Write) 0: Enables this function. 1: Disables this function Incorrect NAK reload transition at the end of a microframe for backward compatibility with Release 2.40c. For more information, see the USB 2.0 Host-AHB Release Notes. Reset value is 1’b0. EN_AutoFunc: Enable Automatic Feature 0: Enables the automatic feature. The Suspend signal is deasserted (logic level 1'b1) when run/stop is reset by software, but the hchalted bit is not set yet. 1: Disables the automatic feature, which takes all ports out of suspend when software clears the run/stop bit. This is for backward compatibility. Bit [5] has an added functionality in release 2.80a and later. For systems where the host is halted without waking up all ports out of suspend, the port can remain suspended because the PHYCLK is not running when the halt is programmed. To avoid this, the DWC H20AHB host core automatically pulls ports out of suspend when the host is halted by software. This bit is used to disable this automatic function. Reset value is 0. DS60001476B-page 1220  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.18 EHCI: REG05 - UTMI Configuration Name: UHPHS_INSNREG05 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 11 10 17 VBusy 9 16 VPort 8 3 2 1 0 – 23 22 21 15 14 VPort 6 13 20 – 7 5 12 VControlLoadM 4 VStatus VControl Control and Status Register, used to read the UTMI registers from the following signals: VStatus: Vendor Status (Software RO) VControl: Vendor Control (Software R/W) VControlLoadM: Vendor Control Load Microframe 0: Load. 1: NOP (software R/W) VPort: Vendor Port (Software R/W) Valid values range from 1 to 15 depending on coreConsultant configuration. For example, if the number of ports is 3, then software should only write values 1, 2, and 3 to this field and not any other values in the range, that is, 0 or 4 to 15. For example, if the software writes value 4 to VPort, from that write onwards, any write to this register is ignored and the read value will always be 4. VBusy: Vendor Busy (Software RO) Hardware indicator that a write to this register has occurred and the hardware is currently processing the operation defined by the data written. When processing is finished, this bit is cleared.  2017 Microchip Technology Inc. DS60001476B-page 1221 SAMA5D2 SERIES 42.7.19 EHCI: REG06 - AHB Error Status Name: UHPHS_INSNREG06 Access: Read/Write 31 AHB_ERR 23 30 29 28 27 26 25 24 22 21 20 19 18 17 16 15 14 13 12 11 5 4 3 – – 7 6 Nb_Burst 10 9 HBURST 2 1 Nb_Success_Burst 8 Nb_Burst 0 Control and Status Register, used to read the UTMI registers from the following signals: Nb_Success_Burst: Number of Successful Bursts (read-only)(1) Number of successfully completed beats in the current burst before the AHB error occurred. Nb_Burst: Number of Bursts (read-only)(1) Number of beats expected in the burst at which the AHB error occurred. Valid values are 0 to 16. 5’b10001–5b11111: Reserved 5’b00000–5b10000: Valid HBURST: Burst Value (read-only)(1) Value of the control phase at which the AHB error occurred. Note 1: This field applies to AHB INCRX-enabled configurations only. AHB_ERR: AHB Error AHB Error Captured Indicator that an AHB error was encountered and values were captured. To clear this field the application must write a 0 to it. EHCI: – When no error, 0 is written to INSNREG06[8:4]. – When INCR4 and an error occur, 4 is written to INSNREG06[8:4]. – When INCR8 and an error occur, 8 is written to INSNREG06[8:4]. – When INCR16 and an error occur, 16 is written to INSNREG06[8:4]. – Other values except 4, 8, and 16 are not written to INSNREG06[8:4]. OHCI: – When no error, 0 is written to INSNREG06[8:4]. – When INCR4 and error occur, 4 is written to INSNREG06[8:4]. – Other values except 4 are not written to INSNREG06[8:4]. DS60001476B-page 1222  2017 Microchip Technology Inc. SAMA5D2 SERIES 42.7.20 EHCI: REG07 - AHB Master Error Address Name: UHPHS_INSNREG07 Access: Read Only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 AHB_ADDR 23 22 21 20 15 14 13 12 AHB_ADDR AHB_ADDR 7 6 5 4 AHB_ADDR AHB_ADDR: AHB Address (read only) AHB address of the control phase at which the AHB error occurred.  2017 Microchip Technology Inc. DS60001476B-page 1223 SAMA5D2 SERIES 42.7.21 EHCI: REG08 - HSIC Enable/Disable Name: UHPHS_INSNREG08 Access: Read / Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 HSIC_EN 1 0 – 23 22 21 20 15 14 13 12 – – 7 6 5 – 4 – HSIC_EN: HSIC Enable/Disable This register has R/W access to the host driver and gives control to the host driver to enable/disable the HSIC interface of PORT C. 0: PORT C is in the HSIC Disable state (see High-Speed Inter-Chip USB Electrical Specification, Version 1.0, Section 3.1.2).). HSIC is in the Disabled state after a power-on reset. 1: PORT C is in the HSIC Enable state (see High-Speed Inter-Chip USB Electrical Specification, Version 1.0, Section 3.1.2). DS60001476B-page 1224  2017 Microchip Technology Inc. SAMA5D2 SERIES 43. Audio Class D Amplifier (CLASSD) 43.1 Description The Audio Class D Amplifier (CLASSD) is a digital input, Pulse Width Modulated (PWM) output stereo Class D amplifier. It features a high quality interpolation filter embedding a digitally controlled gain, an equalizer and a de-emphasis filter. On its input side, the CLASSD is compatible with most common audio data rates. On the output side, its PWM output can drive either: • high-impedance single-ended or differential output loads (Audio DAC application) or, • external MOSFETs through an integrated non-overlapping circuit (Class D power amplifier application). 43.2 • • • • • • • • • • Embedded Characteristics Stereo PWM Class D Amplifier 16-bit Audio Data DSP clocks: 12.288 and 11.2896 MHz Input Sampling Rates: 8, 16, 32, 48, 96, 22.05, 44.1, 88.2 kHz 3-band Equalizer De-emphasis Filter Digital Volume Control Differential or Single-ended Outputs Non-overlapping Circuit to Control External MOSFETs Supports DMA  2017 Microchip Technology Inc. DS60001476B-page 1225 SAMA5D2 SERIES 43.3 Block Diagram Figure 43-1: CLASSD Block Diagram GCLK CLASSD /8 DSP Clock (DSPCLK) CLASSD_L0 DMA RDATA Interpolation LDATA Equalization trigger event dB SWAP MONOMODE Bridge CLASSD_L2 CLASSD_L3 Attenuator PIO PWM nonoverlap 0 EQCFG CLASSD_L1 0 dB Signal Routing MONO PWM nonoverlap FRAME ATTL CLKSEL ATTR PWMTYP CLASSD_R0 CLASSD_R1 CLASSD_R2 CLASSD_R3 NON_OVERLAP NOVRVAL LMUTE RMUTE User Interface + Control Logic Peripheral Clock Bus Clock PMC DS60001476B-page 1226  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.4 Pin Name List Table 43-1: Output Pins Assignment Versus Application Use Cases External MOS Driver (NON_OVERLAP = 1) 43.5 Direct Load (NON_OVERLAP = 0) Full H-Bridge (PWMTYP = 1) Half H-Bridge (PWMTYP = 0) Differential Load (PWMTYP = 1) Single-Ended Load (PWMTYP = 0) Pin Use Case 1 Use Case 2 Use Case 3A & 3B Use Case 4A & 4B Type CLASSD_L0 gate_pmos_leftp gate_pmos_left leftp left Output CLASSD_L1 gate_nmos_leftp gate_nmos_left Not used (fixed to 0) Not used (fixed to 0) Output CLASSD_L2 gate_pmos_leftn Not used (fixed to 1) leftn Not used (fixed to 0) Output CLASSD_L3 gate_nmos_leftn Not used (fixed to 1) Not used (fixed to 0) Not used (fixed to 0) Output CLASSD_R0 gate_pmos_rightp gate_pmos_right rightp right Output CLASSD_R1 gate_nmos_rightp gate_nmos_right Not used (fixed to 0) Not used (fixed to 0) Output CLASSD_R2 gate_pmos_rightn Not used (fixed to 1) rightn Not used (fixed to 0) Output CLASSD_R3 gate_nmos_rightn Not used (fixed to 1) Not used (fixed to 0) Not used (fixed to 0) Output Product Dependencies 43.5.1 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 CLASSD pins to their peripheral functions. Table 43-2: I/O Lines Instance Signal I/O Line Peripheral CLASSD CLASSD_L0 PA28 F CLASSD CLASSD_L1 PA29 F CLASSD CLASSD_L2 PA30 F CLASSD CLASSD_L3 PA31 F CLASSD CLASSD_R0 PB1 F CLASSD CLASSD_R1 PB2 F CLASSD CLASSD_R2 PB3 F CLASSD CLASSD_R3 PB4 F 43.5.2 Power Management The CLASSD is clocked through the Power Management Controller (PMC), thus the programmer must first configure the PMC to enable the CLASSD Peripheral Clock and provide a generic clock (GCLK). The fields NOVRVAL, NON_OVERLAP and PWMTYP in CLASSD_MR, and DSPCLKFREQ and FREQ in CLASSD_INTPMR, must be configured prior to applying the GCLK.  2017 Microchip Technology Inc. DS60001476B-page 1227 SAMA5D2 SERIES 43.5.3 Interrupt The CLASSD has an interrupt line connected to the interrupt controller. Handling the CLASSD interrupt requires programming the interrupt controller before configuring the CLASSD. Table 43-3: Peripheral IDs Instance ID CLASSD 59 43.6 Functional Description 43.6.1 Interpolator 43.6.1.1 Clock Configuration The interpolator accepts input sampling frequencies (fs) and the input DSP clock (DSPCLK) that can be configured in the CLASSD Interpolator Mode Register. GCLK must be configured in the PMC according to the desired DSPCLK so that DSPCLK = GCLK / 8. The following table provides authorized DSPCLK / fs ratios and associated filter types. Table 43-4: Authorized DSPCLK / fs Ratios & Filter Types DSPCLK fs 12.288 MHz 11.2896 MHz 8 kHz 2 –(1) 16 kHz 2 –(1) 32 kHz 2 –(1) 48 kHz 1 –(1) 96 kHz 3 –(1) 22.05 kHz –(1) 1 44.1 kHz –(1) 1 88.2 kHz –(1) 3 Note 1: This configuration is not authorized and raises the CFGERR flag in the CLASSD Interpolator Status Register. 43.6.1.2 CLASSD Frequency Response Interpolation is performed with a combination of Infinite Impulse Response (IIR) and Cascaded Integrator-Comb (CIC) filters. Given the input configuration, the coefficients of the filters are redefined to optimize their transfer function to optimize the audio bandwidth. The different types of filters are defined in Section 43.6.1.1 “Clock Configuration”. DS60001476B-page 1228  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 43-2: Type 1 Frequency Response dB dB Overall Figure 43-3: fs Ripple Type 2 Frequency Response dB dB fs fs Ripple Overall Figure 43-4: Type 3 Frequency Response dB dB Overall 43.6.2 fs fs fs Ripple Equalizer The CLASSD offers 12 pre-programmed equalization filters. A zero-cross detection system is used to modify the equalizer on-the-fly with minimum disturbance on the output signal. Section 43.7.3 “CLASSD Interpolator Mode Register” details the programming of the equalization filter. The following figures show the frequency response of the equalizer function implemented in the D/A channels.  2017 Microchip Technology Inc. DS60001476B-page 1229 SAMA5D2 SERIES Figure 43-5: Bass Filters Response dB fs Figure 43-6: Medium Filters Response dB fs DS60001476B-page 1230  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 43-7: Treble Filters Response dB fs 43.6.3 De-emphasis Filter Frequency Response The CLASSD includes a de-emphasis filter which can be enabled for 32, 44.1 or 48 kHz sampling frequencies. The response and the error generated by the digital approximation of the filter are illustrated in the following figures. Figure 43-8: De-emphasis Filter: Frequency Response & Error (fs = 32 kHz) Error Response (dB) Response (dB) Response Frequency (Hz) Frequency (Hz) De-emphasis Filter: Frequency Response & Error (fs = 44.1 kHz) Figure 43-9: Frequency (Hz)  2017 Microchip Technology Inc. Error Response (dB) Response (dB) Response Frequency (Hz) DS60001476B-page 1231 SAMA5D2 SERIES Figure 43-10: De-emphasis Filter: Frequency Response & Error (fs = 48 kHz) Frequency (Hz) 43.6.4 Error Response (dB) Response (dB) Response Frequency (Hz) Attenuator and Recommended Input Levels The CLASSD features a digital attenuator with an attenuation range of 0–77 dB and a step size of 1 dB. When attenuation greater than 77 dB is programmed, the attenuator mutes the channel. To avoid saturations in the PWM stage, it is recommended to avoid input levels greater than 1 dB below the digital full scale (-1 dBFS). This can done by programming a minimum attenuation of 1 dB. DS60001476B-page 1232  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.6.5 Pulse Width Modulator (PWM) The CLASSD Pulse Width Modulator generates fixed frequency pulse width modulated output signals. For the 44.1 kS/s and 48 kS/s standard audio sample rates, the PWM output frequency is set to 16 × fs: 705.6 kHz and 768 kHz respectively. For 8, 16, 24 and 96 kS/s, the 16× (interpolation) ratio is adapted to keep the output frequency at 768 kHz. In the same way, the output frequency is 705.6 kHz for the 22.05 and 88.2 kS/s cases. The CLASSD functions either as a DAC loaded by a medium-to-high resistive load (e.g., 1 kΩ to 100 kΩ) or as a Class D power amplifier controller driving an external power stage. Depending on the value of CLASSD_MR.NON_OVERLAP, the CLASSD drives: • Single-ended or differential resistive loads (NON_OVERLAP = 0) • Full or Half MOSFET H-bridges (NON_OVERLAP = 1) When driving an external power stage (NON_OVERLAP = 1), the CLASSD generates the signals to control complementary MOSFET pairs (PMOS and NMOS) with a non-overlapping delay between the NMOS and PMOS controls to avoid short circuit current. The non-overlapping delay can be adjusted in the CLASSD_MR.NOVRVAL field. The CLASSD can have a single-ended or a differential output. A specific pulse width modulation type is associated to each case. For single-ended output (CLASSD_MR.PWMTYP = 0), the PWM acts only on the falling edge of the PWM waveform (trailing edge PWM). For differential output (CLASSD_MR.PWMTYP = 1), both the rising and the falling edges of the PWM waveform are modulated (symmetric PWM). Modulation principles are illustrated in Figure 43-11 and Figure 43-12 for both types of PWM. In particular, when describing a null input, if PWMTYP = 0 (trailing edge PWM), the output waveform is a square wave with 50% duty cycle. With the same input and PWMTYP = 1, the differential output waveform is zero. This difference removes the classical L-C low pass filter when PWMTYP = 1. Figure 43-11: Output Waveform Modulation Principle for PWMTYP = 0 PWM Output VDD CLASSD_L0 0 time 1/fPWM  2017 Microchip Technology Inc. DS60001476B-page 1233 SAMA5D2 SERIES Figure 43-12: Output Waveform Modulation Principle for PWMTYP = 1 (Only Left Channel Pins Shown) PWM Outputs VDD CLASSD_L0 0 VDD CLASSD_L2 0 VDD CLASSD_L0 - CLASSD_L2 0 1/fPWM -VDD DS60001476B-page 1234  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.6.6 Application Schematics For Use Case Examples Figure 43-13: Use Case 1: Stereo Class D Amplifier With External Differential Power Stage VDDHV (> VDDIO) D1 R9 C5 CLASSD_L0 R1 GND C1 CLASSD_L1 leftp Q1 R2 LEFT CHANNEL R10 VDDHV (> VDDIO) SPEAKER LEFT D2 GND R11 CLASSD_L2 R3 C2 CLASSD_L3 Q2 leftn VDDIO CLASSD VDDIO R4 C7 R12 GND VDDHV (> VDDIO) GND D3 R13 C6 CLASSD_R0 R5 GND C3 CLASSD_R1 rightp Q3 RIGHT CHANNEL R6 R14 VDDHV (> VDDIO) SPEAKER RIGHT D4 GND R15 CLASSD_R2 R7 C4 CLASSD_R3 Q4 rightn Use case example: D1..D4 = e.g., 1N4148 Q1..Q4 = e.g., DMC2400UV R1..R8 = 10 ohm R9..R16 = 10 kohm C1..C4 = 10 nF C5..C6 = 10 μF C7 = 1 μF  2017 Microchip Technology Inc. R8 R16 GND DS60001476B-page 1235 SAMA5D2 SERIES Figure 43-14: Use Case 1: Waveforms CLASSD_MR.PWMTYP = 1, CLASSD_MR.NON_OVERLAP = 1 CLASSD_MR.NOVRVAL = 0 GCLK CLASSD_L0 CLASSD_L1 CLASSD_L2 CLASSD_L3 NOVRVAL = 0 PWM period CLASSD_MR.NOVRVAL = 3 GCLK CLASSD_L0 CLASSD_L1 CLASSD_L2 CLASSD_L3 NOVRVAL = 3 PWM period In Use Case 1, the external power stages are made of complementary low-cost MOSFETs. In addition to the RDSON and drain breakdown voltage characteristics, the choice of these components is driven by a low gate threshold voltage, a low input capacitance, a low total gate charge and a fast turn-on time characteristics. Series resistance (10 Ω) added to the gates of the MOSFETs are optional and may be adjusted to optimize the gate drive. They help to limit the output current peaks driven by the I/Os into the MOSFET gates in some cases. The 10k resistors ensure an OFF condition when not driven and the capacitor / diode network (C1..C2 / D1..D2) shifts the PMOS drive from the typical VDDIO level (3.3V) to a higher supply voltage (e.g., a 5V power domain). DS60001476B-page 1236  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 43-15: Use Case 2: Stereo Class D Amplifier With External Single-ended Power Stage VDDHV (> VDDIO) D1 C3 R5 CLASSD_L0 R1 GND C1 LF CLASSD_L1 Q1 LEFT CHANNEL left CC CF R2 VDDIO R6 VDDIO C4 CLASSD GND GND GND VDDHV (> VDDIO) D2 R7 CLASSD_R0 R3 C2 LF CLASSD_R1 Q2 RIGHT CHANNEL right CC CF R4 Use case example: D1..D2 = e.g., 1N4148 Q1..Q2 = e.g., DMC2400UV R1..R4 = 10 ohm R5..R8 = 10 kohm C1..C2 = 10 nF C3 = 10 μF C4 = 1 μF R8 GND GND In the Use Case 2 application schematic, the drive network of the MOSFETs gates follows the principles described in Use Case 1.  2017 Microchip Technology Inc. DS60001476B-page 1237 SAMA5D2 SERIES Figure 43-16: Use Case 2: Waveforms CLASSD_MR.PWMTYP = 0, CLASSD_MR.NON_OVERLAP = 1 CLASSD_MR.NOVRVAL = 0 GCLK CLASSD_L0 CLASSD_L1 NOVRVAL = 0 PWM period CLASSD_MR.NOVRVAL = 3 GCLK CLASSD_L0 CLASSD_L1 NOVRVAL = 3 A coupling capacitor (CC) and an L-C low pass filter (LF, CF) are added to the output of the power stage to remove both the DC and the high frequency components of the PWM signal. CC with the resistive part of the speaker (RSPK) forms a C-R high pass filter with a corner frequency of fHP = 1 / (2 × PI × CC × RSPK). LF, CF and RSPK form a second-order low pass filter of corner frequency fC = 1 / (2 × PI × sqrt (LF × CF)) and of quality factor Q = RSPK × sqrt (CF / LF). As a numerical example, consider the case fHP = 200 Hz, fC = 30 kHz, Q = 0.707 (maximally flat response) with RSPK = 8 Ω. This leads to CC = 100 µF, LF = 60 µH, CF = 470 nF. DS60001476B-page 1238  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 43-17: Use Case 3A: Stereo Audio DAC With Active Low Pass Filter and Single-ended Outputs 9.31k 470pF 4.7μF 649 8.66k 12.4k AVDD (> VDDIO) 1nF CLASSD_L0 4.7nF 1nF 4.7μF 4.7μF 100 4.7nF + 100k 10nF LEFT CHANNEL 649 left IC1 10nF CLASSD_L2 - 8.66k 12.4k 9.31k 470pF VDDIO AVDD/2 VDDIO 9.31k CLASSD 1μF GND 470pF 4.7μF 649 8.66k 12.4k AVDD (> VDDIO) 1nF CLASSD_R0 CLASSD_R2 4.7nF 4.7μF 100 1nF 4.7nF + 10nF RIGHT CHANNEL 649 right IC2 10nF 4.7μF - 8.66k 100k 12.4k 9.31k 470 pF Use case example: AVDD/2 IC1..IC2 = e.g., 1/2 LMV356 Figure 43-18: Use Case 3B: Stereo Audio DAC With Simple Passive Low Pass Filter and Differential Outputs 4.7μF leftp 649 CLASSD_L0 1nF 100k 1nF 100k 4.7nF CLASSD_L2 4.7μF LEFT CHANNEL CLASSD 4.7μF 649 leftn 649 rightp CLASSD_R0 1nF 100k 1nF 100k 4.7nF CLASSD_R2 4.7μF RIGHT CHANNEL 649  2017 Microchip Technology Inc. rightn DS60001476B-page 1239 SAMA5D2 SERIES Figure 43-19: Use Case 3A and 3B: Waveforms CLASSD_MR.PWMTYP = 1, CLASSD_MR.NON_OVERLAP = 0 DSPCLK CLASSD_L0 CLASSD_L2 PWM period In Use Case 3A, the CLASSD is used as an audio DAC. In this case, the differential outputs of the CLASSD are used. The application schematic suggested in Figure 43-17 implements a third order 10 kHz low pass Butterworth filter and makes the differential to singleended conversion. Note that in this schematic, the AVDD/2 point needs to be fed at low impedance (e.g., a buffered voltage). A simpler schematic (Use Case 3B) may also be possible, as shown in Figure 43-18, at the cost of higher out-of-band noise and differential outputs which may be acceptable in some applications. Figure 43-20: Use Case 4A: Stereo Audio DAC With Active Low Pass Filter and Single-ended Outputs 10k 220pF 4.7μF 909 9.09k 13k CLASSD_L0 AVDD (> VDDIO) - LEFT CHANNEL 10nF 100 AVDD/2 left + 10nF VDDIO VDDIO 4.7μF IC1 2.2nF 100k 10k CLASSD 1μF GND 220pF 4.7μF 909 9.09k 13k CLASSD_R0 AVDD (> VDDIO) - LEFT CHANNEL 10nF 100 4.7μF right IC2 2.2nF AVDD/2 + 10nF 100k Use case example: IC1..IC2 = e.g., 1/2 LMV356 DS60001476B-page 1240  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 43-21: Use Case 4B: Stereo Audio DAC With Passive Low Pass Filter and Single-ended Outputs 4.7 μF 820 left CLASSD_L0 LEFT CHANNEL 10 nF 100k 10 nF 100k CLASSD CLASSD_R0 RIGHT CHANNEL Figure 43-22: 4.7 μF 820 right Use Case 4A and 4B: Waveforms CLASSD_MR.PWMTYP = 0, CLASSD_MR.NON_OVERLAP = 0 DSPCLK CLASSD_L0 PWM period In Use Case 4A, the CLASSD is used as an audio DAC with active low pass filter. In this case, the single-ended outputs of the CLASSD are selected (PWMTYP = 0, trailing edge PWM) which leaves more I/Os to the application. A third order 30 kHz low pass Butterworth filter is shown in Figure 43-20. The AVDD/2 point can be fed at relatively high impedance as no current is drawn from this point (a simple resistive divider properly decoupled is acceptable). A reduced complexity schematic is presented in Figure 43-21 for less constrained applications. 43.6.7 Register Write Protection To prevent any single software error from corrupting CLASSD behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the CLASSD Write Protection Mode Register (CLASSD_WPMR). The following registers can be write-protected: • CLASSD Mode Register • CLASSD Interpolator Mode Register  2017 Microchip Technology Inc. DS60001476B-page 1241 SAMA5D2 SERIES 43.7 Audio Class D Amplifier (CLASSD) User Interface Table 43-5: Offset Register Mapping Register Name Access Reset 0x00 Control Register CLASSD_CR Write-only – 0x04 Mode Register CLASSD_MR Read/Write 0x00010022 0x08 Interpolator Mode Register CLASSD_INTPMR Read/Write 0x00304E4E 0x0C Interpolator Status Register CLASSD_INTSR Read-only 0x00000000 0x10 Transmit Holding Register CLASSD_THR Read/Write 0x00000000 0x14 Interrupt Enable Register CLASSD_IER Write-only – 0x18 Interrupt Disable Register CLASSD_IDR Write-only – 0x1C Interrupt Mask Register CLASSD_IMR Read/Write 0x00000000 0x20 Interrupt Status Register CLASSD_ISR Read-only 0x00000000 Reserved – – – Write Protection Mode Register CLASSD_WPMR Read/Write 0x00000000 Reserved – – – 0x24–0xE0 0xE4 0xE8–0xFC DS60001476B-page 1242  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.7.1 CLASSD Control Register Name: CLASSD_CR Address: 0xFC048000 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – SWRST SWRST: Software Reset 0: No effect. 1: Reset the CLASSD simulating a hardware reset.  2017 Microchip Technology Inc. DS60001476B-page 1243 SAMA5D2 SERIES 43.7.2 CLASSD Mode Register Name: CLASSD_MR Address: 0xFC048004 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – NON_OVERLAP 15 14 13 12 11 10 9 8 – – – – – – – PWMTYP NOVRVAL 7 6 5 4 3 2 1 0 – – RMUTE REN – – LMUTE LEN This register can only be written if the WPEN bit is cleared in the CLASSD Write Protection Mode Register. LEN: Left Channel Enable 0: Left channel is disabled. 1: Left channel is enabled. LMUTE: Left Channel Mute 0: Left channel is unmuted. 1: Left channel is muted. REN: Right Channel Enable 0: Right channel is disabled. 1: Right channel is enabled. RMUTE: Right Channel Mute 0: Right channel is unmuted. 1: Right channel is muted. PWMTYP: PWM Modulation Type 0 (TRAILING_EDGE): The signal is single-ended. If NON_OVERLAP is cleared, the signal is sent to CLASSD_L0 and CLASSD_R0 (see Figure 43-20 or Figure 43-21). If NON_OVERLAP is set, the signal is sent to CLASSD_L0/L1 and CLASSD_R0/R1 (see Figure 43-15). 1 (UNIFORM): The signal is differential. If NON_OVERLAP is cleared, the signal is sent to CLASSD_L0/L2 and CLASSD_R0/R2 (see Figure 43-17 or Figure 43-18). If NON_OVERLAP is set, the signal is sent to CLASSD_L0/L1/L2/L3 and CLASSD_R0/R1/R2/R3 (see Figure 43-13). NON_OVERLAP: Non-Overlapping Enable 0: Non-overlapping circuit is disabled. 1: Non-overlapping circuit is enabled. DS60001476B-page 1244  2017 Microchip Technology Inc. SAMA5D2 SERIES NOVRVAL: Non-Overlapping Value Value Name Description 0 5NS Non-overlapping time is 5 ns 1 10NS Non-overlapping time is 10 ns 2 15NS Non-overlapping time is 15 ns 3 20NS Non-overlapping time is 20 ns Note: This field has no effect when NON_OVERLAP = 0.  2017 Microchip Technology Inc. DS60001476B-page 1245 SAMA5D2 SERIES 43.7.3 CLASSD Interpolator Mode Register Name: CLASSD_INTPMR Address: 0xFC048008 Access: Read/Write 31 30 – 23 29 MONOMODE 22 – 15 28 21 20 FRAME 14 13 12 – 7 27 26 MONO 25 24 EQCFG 19 18 17 16 SWAP DEEMP – DSPCLKFREQ 11 10 9 8 2 1 0 ATTR 6 5 – 4 3 ATTL This register can only be written if the WPEN bit is cleared in the CLASSD Write Protection Mode Register. ATTL: Left Channel Attenuation Left channel attenuation is defined as follows: – if ATTL ≤ 77 the attenuation is -ATTL dB – else the left signal is muted ATTR: Right Channel Attenuation Right channel attenuation is defined as follows: – if ATTR ≤ 77 the attenuation is -ATTR dB – else the right signal is muted DSPCLKFREQ: DSP Clock Frequency 0 (12M288): DSP Clock (DSPCLK) is 12.288 MHz. 1 (11M2896): DSP Clock (DSPCLK) is 11.2896 MHz. DEEMP: Enable De-emphasis Filter 0 (DISABLED): De-emphasis filter is disabled. 1 (ENABLED): De-emphasis filter is enabled. SWAP: Swap Left and Right Channels 0 (LEFT_ON_LSB): Left channel is on CLASSD_THR[15:0], right channel is on CLASSD_THR[31:16]. 1 (RIGHT_ON_LSB): Right channel is on CLASSD_THR[15:0], left channel is on CLASSD_THR[31:16]. DS60001476B-page 1246  2017 Microchip Technology Inc. SAMA5D2 SERIES FRAME: CLASSD Incoming Data Sampling Frequency Value Name Description 0 FRAME_8K 8 kHz 1 FRAME_16K 16 kHz 2 FRAME_32K 32 kHz 3 FRAME_48K 48 kHz 4 FRAME_96K 96 kHz 5 FRAME_22K 22.05 kHz 6 FRAME_44K 44.1 kHz 7 FRAME_88K 88.2 kHz EQCFG: Equalization Selection Value Name Description 0 FLAT Flat Response 1 BBOOST12 Bass boost +12 dB 2 BBOOST6 Bass boost +6 dB 3 BCUT12 Bass cut -12 dB 4 BCUT6 Bass cut -6 dB 5 MBOOST3 Medium boost +3 dB 6 MBOOST8 Medium boost +8 dB 7 MCUT3 Medium cut -3 dB 8 MCUT8 Medium cut -8 dB 9 TBOOST12 Treble boost +12 dB 10 TBOOST6 Treble boost +6 dB 11 TCUT12 Treble cut -12 dB 12 TCUT6 Treble cut -6 dB Note: EQCFG field values 13–15 = Flat Response MONO: Mono Signal 0 (DISABLED): The signal is sent stereo to the left and right channels. 1 (ENABLED): The same signal is sent on both left and right channels. The sent signal is defined by the MONOMODE field value. MONOMODE: Mono Mode Selection This field defines which signal is sent on both channels when the MONO bit is set. Value Name Description 0 MONOMIX (left + right) / 2 is sent on both channels 1 MONOSAT (left + right) is sent to both channels. If the sum is too high, the result is saturated. 2 MONOLEFT THR[15:0] is sent on both left and right channels 3 MONORIGHT THR[31:16] is sent on both left and right channels  2017 Microchip Technology Inc. DS60001476B-page 1247 SAMA5D2 SERIES 43.7.4 CLASSD Interpolator Status Register Name: CLASSD_INTSR Address: 0xFC04800C Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – CFGERR CFGERR: Configuration Error 0: The frame and clock configuration are correct. 1: The frame and clock configuration are wrong (see Section 43.6.1.1 “Clock Configuration” for information about allowed configurations). DS60001476B-page 1248  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.7.5 CLASSD Transmit Holding Register Name: CLASSD_THR Address: 0xFC048010 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RDATA 23 22 21 20 RDATA 15 14 13 12 LDATA 7 6 5 4 LDATA LDATA: Left Channel Data RDATA: Right Channel Data  2017 Microchip Technology Inc. DS60001476B-page 1249 SAMA5D2 SERIES 43.7.6 CLASSD Interrupt Enable Register Name: CLASSD_IER Address: 0xFC048014 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready 0: No effect. 1: Enables the interrupt when the CLASSD is ready to receive a new data to convert. DS60001476B-page 1250  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.7.7 CLASSD Interrupt Disable Register Name: CLASSD_IDR Address: 0xFC048018 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready 0: No effect. 1: Disables the interrupt when the CLASSD is ready to receive a new data to convert.  2017 Microchip Technology Inc. DS60001476B-page 1251 SAMA5D2 SERIES 43.7.8 CLASSD Interrupt Mask Register Name: CLASSD_IMR Address: 0xFC04801C Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready 0: The interrupt is disabled. 1: The interrupt is enabled. DS60001476B-page 1252  2017 Microchip Technology Inc. SAMA5D2 SERIES 43.7.9 CLASSD Interrupt Status Register Name: CLASSD_ISR Address: 0xFC048020 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready 0: CLASSD has not been ready to convert a value since the last read of CLASSD_ISR. 1: CLASSD is ready to convert a value since the last read of CLASSD_ISR.  2017 Microchip Technology Inc. DS60001476B-page 1253 SAMA5D2 SERIES 43.7.10 CLASSD Write Protection Mode Register Name: CLASSD_WPMR Address: 0xFC0480E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x434C44 (“CLD” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x434C44 (“CLD” in ASCII). See Section 43.6.7 “Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x434C44 Name PASSWD DS60001476B-page 1254 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 44. Inter-IC Sound Controller (I2SC) 44.1 Description The Inter-IC Sound Controller (I2SC) provides a 5-wire, bidirectional, synchronous, digital audio link to external audio devices: I2SC_DI, I2SC_DO, I2SC_WS, I2SC_CK, and I2SC_MCK pins. The I2SC is compliant with the Inter-IC Sound (I2S) bus specification. The I2SC consists of a receiver, a transmitter and a common clock generator that can be enabled separately to provide Master, Slave or Controller modes with receiver and/or transmitter active. DMA Controller channels, separate for the receiver and for the transmitter, allow a continuous high bit rate data transfer without processor intervention to the following: • Audio CODECs in Master, Slave, or Controller mode • Stereo DAC or ADC through a dedicated I2S serial interface The I2SC uses a single DMA Controller channel for both audio channels. The 8- and 16-bit compact stereo format reduces the required DMA Controller bandwidth by transferring the left and right samples within the same data word. In Master mode, the I2SC can produce a 32 fs to 1024 fs master clock that provides an over-sampling clock to an external audio codec or digital signal processor (DSP). 44.2 Embedded Characteristics • Compliant with Inter-IC Sound (I2S) Bus Specification • Master, Slave, and Controller Modes - Slave: Data Received/Transmitted - Master: Data Received/Transmitted And Clocks Generated - Controller: Clocks Generated • Individual Enable and Disable of Receiver, Transmitter and Clocks • Configurable Clock Generator Common to Receiver and Transmitter - Suitable for a Wide Range of Sample Frequencies (fs), Including 32 kHz, 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, and 192 kHz - 32 fs to 1024 fs Master Clock Generated for External Oversampling Data Converters • Support for Multiple Data Formats - 32-, 24-, 20-, 18-, 16-, and 8-bit Mono or Stereo Format - 16- and 8-bit Compact Stereo Format, with Left and Right Samples Packed in the Same Word to Reduce Data Transfers • DMA Controller Interfaces the Receiver and Transmitter to Reduce Processor Overhead - One DMA Controller Channel for Both Audio Channels • Smart Holding Registers Management to Avoid Audio Channels Mix After Overrun or Underrun  2017 Microchip Technology Inc. DS60001476B-page 1255 SAMA5D2 SERIES 44.3 Block Diagram Figure 44-1: I2SC Block Diagram SFR SFR_I2SCLKSEL Peripheral Clock 0 I2SC PIO Selected Clock PMC I2SC_MCK (1) GCLK[PID] 1 Bus Interface I2SC_CK Clocks I2SC_WS Peripheral Bus Bridge DMA Controller Receiver I2SC_DI Transmitter I2SC_DO Events Interrupt Controller (1) For the value of ‘PID’, refer to I2SCx in the table “Peripheral Identifiers”. 44.4 I/O Lines Description Table 44-1: I/O Lines Description Pin Name Pin Description I2SC_MCK Master Clock Output I2SC_CK Serial Clock Input/Output I2SC_WS I2S Word Select Input/Output I2SC_DI Serial Data Input Input I2SC_DO Serial Data Output DS60001476B-page 1256 Type Output  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.5 Product Dependencies To use the I2SC, other parts of the system must be configured correctly, as described below. 44.5.1 I/O Lines The I2SC pins may be multiplexed with I/O Controller lines. The user must first program the PIO Controller to assign the required I2SC pins to their peripheral function. If the I2SC I/O lines are not used by the application, they can be used for other purposes by the PIO Controller. The user must enable the I2SC inputs and outputs that are used. Table 44-2: I/O Lines Instance Signal I/O Line Peripheral I2SC0 I2SC0_CK PC1 E I2SC0 I2SC0_CK PD19 E I2SC0 I2SC0_DI0 PC4 E I2SC0 I2SC0_DI0 PD22 E I2SC0 I2SC0_DO0 PC5 E I2SC0 I2SC0_DO0 PD23 E I2SC0 I2SC0_MCK PC2 E I2SC0 I2SC0_MCK PD20 E I2SC0 I2SC0_WS PC3 E I2SC0 I2SC0_WS PD21 E I2SC1 I2SC1_CK PA15 D I2SC1 I2SC1_CK PB15 D I2SC1 I2SC1_DI0 PA17 D I2SC1 I2SC1_DI0 PB17 D I2SC1 I2SC1_DO0 PA18 D I2SC1 I2SC1_DO0 PB18 D I2SC1 I2SC1_MCK PA14 D I2SC1 I2SC1_MCK PB14 D I2SC1 I2SC1_WS PA16 D I2SC1 I2SC1_WS PB16 D 44.5.2 Power Management If the CPU enters a Sleep mode that disables clocks used by the I2SC, the I2SC stops functioning and resumes operation after the system wakes up from Sleep mode. 44.5.3 Clocks The clock for the I2SC bus interface is generated by the Power Management Controller (PMC). I2SC must be disabled before disabling the clock to avoid freezing the I2SC in an undefined state. 44.5.4 DMA Controller The I2SC interfaces to the DMA Controller. Using the I2SC DMA functionality requires the DMA Controller to be programmed first.  2017 Microchip Technology Inc. DS60001476B-page 1257 SAMA5D2 SERIES 44.5.5 Interrupt Sources The I2SC interrupt line is connected to the Interrupt Controller. Using the I2SC interrupt requires the Interrupt Controller to be programmed first. Table 44-3: Peripheral IDs Instance ID I2SC0 54 I2SC1 55 44.6 44.6.1 Functional Description Initialization The I2SC features a receiver, a transmitter and a clock generator for Master and Controller modes. Receiver and transmitter share the same serial clock and word select. Before enabling the I2SC, the selected configuration must be written to the I2SC Mode Register (I2SC_MR) and to the I2S Clock Source Selection register (SFR_I2SCLKSEL) described in the section “Special Function Registers (SFR)”. If the I2SC_MR.IMCKMODE bit is set, the I2SC_MR.IMCKFS field must be configured as described in Section 44.6.5 “Serial Clock and Word Select Generation”. Once the I2SC_MR has been written, the I2SC clock generator, receiver, and transmitter can be enabled by writing a ’1’ to the CKEN, RXEN, and TXEN bits in the Control Register (I2SC_CR). The clock generator can be enabled alone in Controller mode to output clocks to the I2SC_MCK, I2SC_CK, and I2SC_WS pins. The clock generator must also be enabled if the receiver or the transmitter is enabled. The clock generator, receiver, and transmitter can be disabled independently by writing a ’1’ to I2SC_CR.CXDIS, I2SC_CR.RXDIS and/ or I2SC_CR.TXDIS, respectively. Once requested to stop, they stop only when the transmission of the pending frame transmission is completed. 44.6.2 Basic Operation The receiver can be operated by reading the Receiver Holding Register (I2SC_RHR), whenever the Receive Ready (RXRDY) bit in the Status Register (I2SC_SR) is set. Successive values read from RHR correspond to the samples from the left and right audio channels for the successive frames. The transmitter can be operated by writing to the Transmitter Holding Register (I2SC_THR), whenever the Transmit Ready (TXRDY) bit in the I2SC_SR is set. Successive values written to THR correspond to the samples from the left and right audio channels for the successive frames. The RXRDY and TXRDY bits can be polled by reading the I2SC_SR. The I2SC processor load can be reduced by enabling interrupt-driven operation. The RXRDY and/or TXRDY interrupt requests can be enabled by writing a ’1’ to the corresponding bit in the Interrupt Enable Register (I2SC_IER). The interrupt service routine associated to the I2SC interrupt request is executed whenever the Receive Ready or the Transmit Ready status bit is set. 44.6.3 Master, Controller and Slave Modes In Master and Controller modes, the I2SC provides the master clock, the serial clock and the word select. I2SC_MCK, I2SC_CK, and I2SC_WS pins are outputs. In Controller mode, the I2SC receiver and transmitter are disabled. Only the clocks are enabled and used by an external receiver and/or transmitter. In Slave mode, the I2SC receives the serial clock and the word select from an external master. I2SC_CK and I2SC_WS pins are inputs. The mode is selected by writing the MODE field in the I2SC_MR. Since the MODE field changes the direction of the I2SC_WS and I2SC_SCK pins, the I2SC_MR must be written when the I2SC is stopped. 44.6.4 I2S Reception and Transmission Sequence As specified in the I2S protocol, data bits are left-justified in the word select time slot, with the MSB transmitted first, starting one clock period after the transition on the word select line. DS60001476B-page 1258  2017 Microchip Technology Inc. SAMA5D2 SERIES I2S Reception and Transmission Sequence Figure 44-2: Serial Clock I2SC_CK Word Select I2SC_WS Data I2SC_DI/I2SC_DO MSB LSB Left Channel MSB Right Channel Data bits are sent on the falling edge of the serial clock and sampled on the rising edge of the serial clock. the word select line indicates the channel in transmission, a low level for the left channel and a high level for the right channel. The length of transmitted words can be chosen among 8, 16, 18, 20, 24, and 32 bits by writing the I2SC_MR.DATALENGTH field. If the time slot allows for more data bits than written in the I2SC_MR.DATALENGTH field, zeroes are appended to the transmitted data word or extra received bits are discarded. 44.6.5 Serial Clock and Word Select Generation The generation of clocks in the I2SC is described in Figure 44-3 ”I2SC Clock Generation”. In Slave mode, the serial clock and word select clock are driven by an external master. I2SC_CK and I2SC_WS pins are inputs. In Master mode, the user can configure the master clock, serial clock, and word select clock through the I2SC_MR. I2SC_MCK, I2SC_CK, and I2SC_WS pins are outputs and MCK is used to derive the I2SC clocks. In Master mode, if the peripheral clock frequency is higher than 96 MHz, GCLK[PID] from the PMC must be selected as the I2SC input clock by writing a ’1’ in the CLKSELx bit of the SFR_I2SCLKSEL register located in SFR. Audio codecs connected to the I2SC pins may require a master clock (I2SC_MCK) signal with a frequency multiple of the audio sample frequency (fs), such as 256fs. When the I2SC is in Master mode, writing a ’1’ to I2SC_MR.IMCKMODE outputs MCK as master clock to the I2SC_MCK pin, and divides MCK to create the internal bit clock, output on the I2SC_CK pin. The clock division factor is defined by writing to I2SC_MR.IMCKFS and I2SC_MR.DATALENGTH, as described in the I2SC_MR.IMCKFS field description. The master clock (I2SC_MCK) frequency is (2×16 × (IMCKFS + 1)) / (IMCKDIV + 1) times the sample frequency (fs), i.e., I2SC_WS frequency. Example: If the sampling rate is 44.1 kHz with an I2S master clock (I2SC_MCK) ratio of 256, the core frequency must be an integer multiple of 11.2896 MHz. Assuming an integer multiple of 4, the IMCKDIV field must be configured to 4; the field IMCKFS must then be set to 31. The serial clock (I2SC_CK) frequency is 2 × Slot Length times the sample frequency (fs), where Slot Length is defined in Table 44-4. Table 44-4: Slot Length I2SC_MR.DATALENGTH Word Length Slot Length 0 32 bits 32 1 24 bits 2 20 bits 3 18 bits 4 16 bits 5 16 bits compact stereo 6 8 bits 7 8 bits compact stereo 32 if I2SC_MR.IWS = 0 24 if I2SC_MR.IWS = 1 16 8 Warning: I2SC_MR.IMCKMODE must be written to ’1’ if the master clock frequency is strictly higher than the serial clock.  2017 Microchip Technology Inc. DS60001476B-page 1259 SAMA5D2 SERIES If a master clock output is not required, the MCK clock is used as I2SC_CK by clearing I2SC_MR.IMCKMODE. Alternatively, if the frequency of the MCK clock used is a multiple of the required I2SC_CK frequency, the I2SC_MCK to I2SC_CK divider can be used with the ratio defined by writing the I2SC_MR.IMCKFS field. The I2SC_WS pin is used as word select as described in Section 44.6.4 “I2S Reception and Transmission Sequence”. Figure 44-3: I2SC Clock Generation SFR.SFR_I2SCLKSEL.CLKSELx I2SC I2SC_CR.CKEN/CKDIS Peripheral Clock 0 GCLK[PID] 1 Selected Clock I2SC_MR.IMCKMODE Clock Divider Clock Enable Clock Divider I2SC_MR.IMCKMODE 0 I2SC_MR.IMCKDIV 1 I2SC_MCK I2SC_MR.IMCKFS I2SC_MR.DATALENGTH I2SC_CK Master i2sck_in 0 i2sck_in 1 Clock Enable Internal bit clock Slave I2SC_CR.CKEN/CKDIS I2SC_MR.MODE Clock Divider I2SC_MR.DATALENGTH I2SC_WS 0 i2sws_in Internal word clock 1 i2sws_in Slave 44.6.6 Mono When the Transmit Mono bit (TXMONO) in I2SC_MR is set, data written to the left channel is duplicated to the right output channel. When the Receive Mono bit (RXMONO) in I2SC_MR is set, data received from the left channel is duplicated to the right channel. 44.6.7 Holding Registers The I2SC user interface includes a Receive Holding Register (I2SC_RHR) and a Transmit Holding Register (I2SC_THR). These registers are used to access audio samples for both audio channels. When a new data word is available in I2SC_RHR, the Receive Ready bit (RXRDY) in I2SC_SR is set. Reading I2SC_RHR clears this bit. A receive overrun condition occurs if a new data word becomes available before the previous data word has been read from I2SC_RHR. In this case, the Receive Overrun bit in I2SC_SR and bit i of the RXORCH field in I2SC_SR are set, where i is the current receive channel number. When I2SC_THR is empty, the Transmit Ready bit (TXRDY) in I2SC_SR is set. Writing to I2SC_THR clears this bit. A transmit underrun condition occurs if a new data word needs to be transmitted before it has been written to I2SC_THR. In this case, the Transmit Underrun (TXUR) bit and bit i of the TXORCH field in I2SC_SR are set, where i is the current transmit channel number. If the TXSAME bit in I2SC_MR is ’0’, then a zero data word is transmitted in case of underrun. If I2SC_MR.TXSAME is ’1’, then the previous data word for the current transmit channel number is transmitted. DS60001476B-page 1260  2017 Microchip Technology Inc. SAMA5D2 SERIES Data words are right-justified in I2SC_RHR and I2SC_THR. For the 16-bit compact stereo data format, the left sample uses bits 15:0 and the right sample uses bits 31:16 of the same data word. For the 8-bit compact stereo data format, the left sample uses bits 7:0 and the right sample uses bits 15:8 of the same data word. 44.6.8 DMA Controller Operation All receiver audio channels are assigned to a single DMA Controller. The DMA Controller reads from the I2SC_RHR and writes to the I2SC_THR for both audio channels successively. The DMA Controller transfers may use 32-bit word, 16-bit halfword, or 8-bit byte depending on the value of the I2SC_MR.DATALENGTH field. 44.6.9 Loopback Mode For debug purposes, the I2SC can be configured to loop back the transmitter to the Receiver. Writing a ’1’ to the I2SC_MR.LOOP bit internally connects I2SC_DO to I2SC_DI, so that the transmitted data is also received. Writing a ’0’ to I2SC_MR.LOOP restores the normal behavior with independent Receiver and Transmitter. As for other changes to the Receiver or Transmitter configuration, the I2SC Receiver and Transmitter must be disabled before writing to I2SC_MR to update I2SC_MR.LOOP. 44.6.10 Interrupts An I2SC interrupt request can be triggered whenever one or several of the following bits are set in I2SC_SR: Receive Ready (RXRDY), Receive Overrun (RXOR), Transmit Ready (TXRDY) or Transmit Underrun (TXUR). The interrupt request is generated if the corresponding bit in the Interrupt Mask Register (I2SC_IMR) is set. Bits in I2SC_IMR are set by writing a ’1’ to the corresponding bit in I2SC_IER and cleared by writing a ’1’ to the corresponding bit in the Interrupt Disable Register (I2SC_IDR). The interrupt request remains active until the corresponding bit in I2SC_SR is cleared by writing a ’1’ to the corresponding bit in the Status Clear Register (I2SC_SCR). For debug purposes, interrupt requests can be simulated by writing a ’1’ to the corresponding bit in the Status Set Register (I2SC_SSR). Figure 44-4: Interrupt Block Diagram Set I2SC_IER Clear I2SC_IMR I2SC_IDR Transmitter TXRDY TXUR Interrupt Logic I2SC interrupt line Receiver RXRDY RXOR 44.7 I2SC Application Examples The I2SC supports several serial communication modes used in audio or high-speed serial links. Examples of standard applications are shown in the following figures. All serial link applications supported by the I2SC are not listed here.  2017 Microchip Technology Inc. DS60001476B-page 1261 SAMA5D2 SERIES Figure 44-5: Slave Transmitter I2SC Application Example I2SC Serial Clock I2SC_CK Stereo Audio DAC Word Select I2SC_WS Serial Data Out I2SC_DO I2SC_DI Serial Clock Word Select Serial Data Out DS60001476B-page 1262 MSB LSB MSB  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 44-6: Dual Microphone Application Block Diagram I2S Microphone for Left Channel I2SC I2SC_MCK I2SC_CK I2SC_WS Serial Clock Word Select SCK WS L/R Tied to 1 I2SC_DO I2SC_DI Serial Data In SD I2S Microphone for Right Channel SCK WS L/R Tied to 0 SD Serial Clock Word Select Left Channel Dstart Right Channel Dend Serial Data In  2017 Microchip Technology Inc. DS60001476B-page 1263 SAMA5D2 SERIES Figure 44-7: Codec Application Block Diagram I2SC I2SC_MCK Master Clock Serial Clock I2SC_CK Word Select I2SC_WS Serial Data Out I2SC_DO Serial Data In I2SC_DI MCLK I2S Audio Codec BCLK LRCLK/WCLK DAC_SDATA/DIN ADC_SDATA/DOUT Serial Clock Word Select Left Time Slot Dstart Right Time Slot Dend Serial Data Out Serial Data In DS60001476B-page 1264  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8 Inter-IC Sound Controller (I2SC) User Interface Table 44-5: Register Mapping Offset Register Name Access Reset 0x00 Control Register I2SC_CR Write-only – 0x04 Mode Register I2SC_MR Read/Write 0x00000000 0x08 Status Register I2SC_SR Read-only 0x00000000 0x0C Status Clear Register I2SC_SCR Write-only – 0x10 Status Set Register I2SC_SSR Write-only – 0x14 Interrupt Enable Register I2SC_IER Write-only – 0x18 Interrupt Disable Register I2SC_IDR Write-only – 0x1C Interrupt Mask Register I2SC_IMR Read-only 0x00000000 0x20 Receiver Holding Register I2SC_RHR Read-only 0x00000000 0x24 Transmitter Holding Register I2SC_THR Write-only – 0x28–0xFC Reserved – – –  2017 Microchip Technology Inc. DS60001476B-page 1265 SAMA5D2 SERIES 44.8.1 I2SC Control Register Name: I2SC_CR Address: 0xF8050000 (0), 0xFC04C000 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 SWRST 6 – 5 TXDIS 4 TXEN 3 CKDIS 2 CKEN 1 RXDIS 0 RXEN RXEN: Receiver Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit enables the I2SC receiver, if RXDIS is not one. Bit I2SC_SR.RXEN is set when the receiver is activated. RXDIS: Receiver Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit disables the I2SC receiver. Bit I2SC_SR.RXEN is cleared when the receiver is stopped. CKEN: Clocks Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit enables the I2SC clocks generation, if CKDIS is not one. CKDIS: Clocks Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a zone to this bit disables the I2SC clock generation. TXEN: Transmitter Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit enables the I2SC transmitter, if TXDIS is not one. Bit I2SC_SR.TXEN is set when the Transmitter is started. TXDIS: Transmitter Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit disables the I2SC transmitter. Bit I2SC_SR.TXEN is cleared when the Transmitter is stopped. SWRST: Software Reset 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit resets all the registers in the I2SC. The I2SC is disabled after the reset. DS60001476B-page 1266  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8.2 I2SC Mode Register Name: I2SC_MR Address: 0xF8050004 (0), 0xFC04C004 (1) Access: Read/Write 31 IWS 30 IMCKMODE 29 23 – 22 – 21 15 – 14 TXSAME 13 – 12 TXMONO 6 5 – 4 7 28 27 26 25 24 18 17 16 11 – 10 RXLOOP 9 – 8 RXMONO 3 DATALENGTH 2 1 – 0 MODE IMCKFS 20 19 IMCKDIV FORMAT The I2SC_MR must be written when the I2SC is stopped. The proper sequence is to write to I2SC_MR, then write to I2SC_CR to enable the I2SC or to disable the I2SC before writing a new value to I2SC_MR. MODE: Inter-IC Sound Controller Mode Value Name Description 0 SLAVE I2SC_CK and I2SC_WS pin inputs used as bit clock and word select/frame synchronization. 1 MASTER Bit clock and word select/frame synchronization generated by I2SC from MCK and output to I2SC_CK and I2SC_WS pins. Peripheral clock or GCLK is output as master clock on I2SC_MCK if I2SC_MR.IMCKMODE is set. DATALENGTH: Data Word Length Value Name Description 0 32_BITS Data length is set to 32 bits 1 24_BITS Data length is set to 24 bits 2 20_BITS Data length is set to 20 bits 3 18_BITS Data length is set to 18 bits 4 16_BITS Data length is set to 16 bits 5 16_BITS_COMPAC T Data length is set to 16-bit compact stereo. Left sample in bits 15:0 and right sample in bits 31:16 of same word. 6 8_BITS Data length is set to 8 bits 7 8_BITS_COMPACT Data length is set to 8-bit compact stereo. Left sample in bits 7:0 and right sample in bits 15:8 of the same word. FORMAT: Data Format Value Name Description 0 I2S I2S format, stereo with I2SC_WS low for left channel, and MSB of sample starting one I2SC_CK period after I2SC_WS edge 1 LJ Left-justified format, stereo with I2SC_WS high for left channel, and MSB of sample starting on I2SC_WS edge 2 – Reserved 3 – Reserved  2017 Microchip Technology Inc. DS60001476B-page 1267 SAMA5D2 SERIES RXMONO: Receive Mono 0: Stereo 1: Mono, with left audio samples duplicated to right audio channel by the I2SC. RXLOOP: Loopback Test Mode 0: Normal mode 1: I2SC_DO output of I2SC is internally connected to I2SC_DI input. TXMONO: Transmit Mono 0: Stereo 1: Mono, with left audio samples duplicated to right audio channel by the I2SC. TXSAME: Transmit Data when Underrun 0: Zero sample transmitted when underrun. 1: Previous sample transmitted when underrun IMCKDIV: Selected Clock to I2SC Master Clock Ratio I2SC_MCK Master clock output frequency is Selected Clock divided by (IMCKDIV + 1). Refer to the IMCKFS field description. Note 1: This field is write-only. Always read as ‘0’. 2: Do not write a ‘0’ to this field. IMCKFS: Master Clock to fs Ratio Master clock frequency is [2 x 16 × (IMCKFS + 1)] / (IMCKDIV + 1) times the sample rate, i.e., I2SC_WS frequency. Value Name Description 0 M2SF32 Sample frequency ratio set to 32 1 M2SF64 Sample frequency ratio set to 64 2 M2SF96 Sample frequency ratio set to 96 3 M2SF128 Sample frequency ratio set to 128 5 M2SF192 Sample frequency ratio set to 192 7 M2SF256 Sample frequency ratio set to 256 11 M2SF384 Sample frequency ratio set to 384 15 M2SF512 Sample frequency ratio set to 512 23 M2SF768 Sample frequency ratio set to 768 31 M2SF1024 Sample frequency ratio set to 1024 47 M2SF1536 Sample frequency ratio set to 1536 63 M2SF2048 Sample frequency ratio set to 2048 IMCKMODE: Master Clock Mode 0: No master clock generated (Selected Clock drives I2SC_CK output). 1: Master clock generated (internally generated clock is used as I2SC_MCK output). Warning: If I2SC_MCK frequency is the same as I2SC_CK, IMCKMODE must be cleared. Refer to Section 44.6.5 “Serial Clock and Word Select Generation” and Table 44-4 “Slot Length”. IWS: I2SC_WS Slot Width 0: I2SC_WS slot is 32 bits wide for DATALENGTH = 18/20/24 bits. 1: I2SC_WS slot is 24 bits wide for DATALENGTH = 18/20/24 bits. Refer to Table 44-4 “Slot Length”. DS60001476B-page 1268  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8.3 I2SC Status Register Name: I2SC_SR Address: 0xF8050008 (0), 0xFC04C008 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 20 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 7 – 6 TXUR 5 TXRDY 4 TXEN 3 – 2 RXOR 1 RXRDY TXURCH 8 RXORCH 0 RXEN RXEN: Receiver Enabled 0: This bit is cleared when the receiver is disabled, following a RXDIS or SWRST request in I2SC_CR. 1: This bit is set when the receiver is enabled, following a RXEN request in I2SC_CR. RXRDY: Receive Ready 0: This bit is cleared when I2SC_RHR is read. 1: This bit is set when received data is present in I2SC_RHR. RXOR: Receive Overrun 0: This bit is cleared when the corresponding bit in I2SC_SCR is written to ’1’. 1: This bit is set when an overrun error occurs on I2SC_RHR or when the corresponding bit in I2SC_SSR is written to ’1’. TXEN: Transmitter Enabled 0: This bit is cleared when the transmitter is disabled, following a I2SC_CR.TXDIS or I2SC_CR.SWRST request. 1: This bit is set when the transmitter is enabled, following a I2SC_CR.TXEN request. TXRDY: Transmit Ready 0: This bit is cleared when data is written to I2SC_THR. 1: This bit is set when I2SC_THR is empty and can be written with new data to be transmitted. TXUR: Transmit Underrun 0: This bit is cleared when the corresponding bit in I2SC_SCR is written to ’1’. 1: This bit is set when an underrun error occurs on I2SC_THR or when the corresponding bit in I2SC_SSR is written to ’1’. RXORCH: Receive Overrun Channel This field is cleared when I2SC_SCR.RXOR is written to ’1’. Bit i of this field is set when a receive overrun error occurred in channel i (i = 0 for first channel of the frame). TXURCH: Transmit Underrun Channel 0: This field is cleared when I2SC_SCR.TXUR is written to ’1’. 1: Bit i of this field is set when a transmit underrun error occurred in channel i (i = 0 for first channel of the frame).  2017 Microchip Technology Inc. DS60001476B-page 1269 SAMA5D2 SERIES 44.8.4 I2SC Status Clear Register Name: I2SC_SCR Address: 0xF805000C (0), 0xFC04C00C (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 20 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 7 – 6 TXUR 5 – 4 – 3 – 2 RXOR 1 – TXURCH 8 RXORCH 0 – RXOR: Receive Overrun Status Clear Writing a ’0’ to this bit has no effect. Writing a ’1’ to this bit clears the status bit. TXUR: Transmit Underrun Status Clear Writing a ’0’ to this bit has no effect. Writing a ’1’ to this bit clears the status bit. RXORCH: Receive Overrun Per Channel Status Clear Writing a ’0’ has no effect. Writing a ’1’ to any bit in this field clears the corresponding bit in the I2SC_SR and the corresponding interrupt request. TXURCH: Transmit Underrun Per Channel Status Clear Writing a ’0’ has no effect. Writing a ’1’ to any bit in this field clears the corresponding bit in the I2SC_SR and the corresponding interrupt request. DS60001476B-page 1270  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8.5 I2SC Status Set Register Name: I2SC_SSR Address: 0xF8050010 (0), 0xFC04C010 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 20 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 7 – 6 TXUR 5 – 4 – 3 – 2 RXOR 1 – TXURCH 8 RXORCH 0 – RXOR: Receive Overrun Status Set Writing a ’0’ to this bit has no effect. Writing a ’1’ to this bit sets the status bit. TXUR: Transmit Underrun Status Set Writing a ’0’ to this bit has no effect. Writing a ’1’ to this bit sets the status bit. RXORCH: Receive Overrun Per Channel Status Set Writing a ’0’ has no effect. Writing a ’1’ to any bit in this field sets the corresponding bit in I2SC_SR and the corresponding interrupt request. TXURCH: Transmit Underrun Per Channel Status Set Writing a ’0’ has no effect. Writing a ’1’ to any bit in this field sets the corresponding bit in I2SC_SR and the corresponding interrupt request.  2017 Microchip Technology Inc. DS60001476B-page 1271 SAMA5D2 SERIES 44.8.6 I2SC Interrupt Enable Register Name: I2SC_IER Address: 0xF8050014 (0), 0xFC04C014 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 TXUR 5 TXRDY 4 – 3 – 2 RXOR 1 RXRDY 0 – RXRDY: Receiver Ready Interrupt Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit sets the corresponding bit in I2SC_IMR. RXOR: Receiver Overrun Interrupt Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit sets the corresponding bit in I2SC_IMR. TXRDY: Transmit Ready Interrupt Enable 0: Writing a ’0’ to this bit as no effect. 1: Writing a ’1’ to this bit sets the corresponding bit in I2SC_IMR. TXUR: Transmit Underflow Interrupt Enable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit sets the corresponding bit in I2SC_IMR. DS60001476B-page 1272  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8.7 I2SC Interrupt Disable Register Name: I2SC_IDR Address: 0xF8050018 (0), 0xFC04C018 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 TXUR 5 TXRDY 4 – 3 – 2 RXOR 1 RXRDY 0 – RXRDY: Receiver Ready Interrupt Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit clears the corresponding bit in I2SC_IMR. RXOR: Receiver Overrun Interrupt Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit clears the corresponding bit in I2SC_IMR. TXRDY: Transmit Ready Interrupt Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit clears the corresponding bit in I2SC_IMR. TXUR: Transmit Underflow Interrupt Disable 0: Writing a ’0’ to this bit has no effect. 1: Writing a ’1’ to this bit clears the corresponding bit in I2SC_IMR.  2017 Microchip Technology Inc. DS60001476B-page 1273 SAMA5D2 SERIES 44.8.8 I2SC Interrupt Mask Register Name: I2SC_IMR Address: 0xF805001C (0), 0xFC04C01C (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 TXUR 5 TXRDY 4 – 3 – 2 RXOR 1 RXRDY 0 – RXRDY: Receiver Ready Interrupt Disable 0: The corresponding interrupt is disabled. This bit is cleared when the corresponding bit in I2SC_IDR is written to ’1’. 1: The corresponding interrupt is enabled. This bit is set when the corresponding bit in I2SC_IER is written to ’1’. RXOR: Receiver Overrun Interrupt Disable 0: The corresponding interrupt is disabled. This bit is cleared when the corresponding bit in I2SC_IDR is written to ’1’. 1: The corresponding interrupt is enabled. This bit is set when the corresponding bit in I2SC_IER is written to ’1’. TXRDY: Transmit Ready Interrupt Disable 0: The corresponding interrupt is disabled. This bit is cleared when the corresponding bit in I2SC_IDR is written to ’1’. 1: The corresponding interrupt is enabled. This bit is set when the corresponding bit in I2SC_IER is written to ’1’. TXUR: Transmit Underflow Interrupt Disable 0: The corresponding interrupt is disabled. This bit is cleared when the corresponding bit in I2SC_IDR is written to ’1’. 1: The corresponding interrupt is enabled. This bit is set when the corresponding bit in I2SC_IER is written to ’1’. DS60001476B-page 1274  2017 Microchip Technology Inc. SAMA5D2 SERIES 44.8.9 I2SC Receiver Holding Register Name: I2SC_RHR Address: 0xF8050020 (0), 0xFC04C020 (1) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RHR 23 22 21 20 RHR 15 14 13 12 RHR 7 6 5 4 RHR RHR: Receiver Holding Register This field is set by hardware to the last received data word. If I2SC_MR.DATALENGTH specifies fewer than 32 bits, data is right justified in the RHR field.  2017 Microchip Technology Inc. DS60001476B-page 1275 SAMA5D2 SERIES 44.8.10 I2SC Transmitter Holding Register Name: I2SC_THR Address: 0xF8050024 (0), 0xFC04C024 (1) Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 THR 23 22 21 20 THR 15 14 13 12 THR 7 6 5 4 THR THR: Transmitter Holding Register Next data word to be transmitted after the current word if TXRDY is not set. If I2SC_MR.DATALENGTH specifies fewer than 32 bits, data is right-justified in the THR field. DS60001476B-page 1276  2017 Microchip Technology Inc. SAMA5D2 SERIES 45. Synchronous Serial Controller (SSC) 45.1 Description The 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 TD/RD signal for data, the TK/RK signal for the clock and the TF/RF 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 high-level of programmability and its use of DMA enable a continuous high bit rate data transfer without processor intervention. Featuring connection to the DMA, the SSC enables interfacing with low processor overhead to: • Codecs in Master or Slave mode, • DAC through dedicated serial interface, particularly I2S, • Magnetic card reader. 45.2 • • • • • • Embedded Characteristics Provides Serial Synchronous Communication Links Used in Audio and Telecom Applications Contains an Independent Receiver and Transmitter and a Common Clock Divider Interfaced with the DMA Controller (DMAC) 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 Sync Signal 45.3 Block Diagram Figure 45-1: Block Diagram System Bus Peripheral Bridge Bus Clock DMA Peripheral Bus TF TK PMC TD Peripheral Clock SSC Interface PIO RF RK Interrupt Control RD SSC Interrupt  2017 Microchip Technology Inc. DS60001476B-page 1277 SAMA5D2 SERIES 45.4 Application Block Diagram Figure 45-2: Application Block Diagram OS or RTOS Driver Power Management Interrupt Management Test Management SSC Serial AUDIO DS60001476B-page 1278 Codec Time Slot Management Frame Management Line Interface  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.5 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 45-3: Audio Application Block Diagram Clock SCK TK Word Select WS I2S RECEIVER TF Data SD TD SSC RD Clock SCK RF Word Select WS RK MSB Data SD MSB LSB Right Channel Left Channel Figure 45-4: Codec Application Block Diagram Serial Data Clock (SCLK) TK Frame Sync (FSYNC) TF Serial Data Out CODEC TD SSC Serial Data In RD RF RK Serial Data Clock (SCLK) Frame Sync (FSYNC) First Time Slot Dstart Dend Serial Data Out Serial Data In  2017 Microchip Technology Inc. DS60001476B-page 1279 SAMA5D2 SERIES Figure 45-5: Time Slot Application Block Diagram SCLK TK FSYNC TF CODEC First Time Slot Data Out TD SSC Data In RD RF RK CODEC Second Time Slot Serial Data Clock (SCLK) Frame Sync (FSYNC) First Time Slot Second Time Slot Dstart Dend Serial Data Out Serial Data in 45.6 Pin Name List Table 45-1: I/O Lines Description Pin Name Pin Description RF Receive Frame Synchronization Input/Output RK Receive Clock Input/Output RD Receive Data Input TF Transmit Frame Synchronization Input/Output TK Transmit Clock Input/Output TD Transmit Data Output DS60001476B-page 1280 Type  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.7 Product Dependencies 45.7.1 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. Table 45-2: I/O Lines Instance Signal I/O Line Peripheral SSC0 RD0 PB23 C SSC0 RD0 PC15 E SSC0 RF0 PB25 C SSC0 RF0 PC17 E SSC0 RK0 PB24 C SSC0 RK0 PC16 E SSC0 TD0 PB22 C SSC0 TD0 PC14 E SSC0 TF0 PB21 C SSC0 TF0 PC13 E SSC0 TK0 PB20 C SSC0 TK0 PC12 E SSC1 RD1 PA17 B SSC1 RD1 PB17 C SSC1 RF1 PA19 B SSC1 RF1 PB19 C SSC1 RK1 PA18 B SSC1 RK1 PB18 C SSC1 TD1 PA16 B SSC1 TD1 PB16 C SSC1 TF1 PA15 B SSC1 TF1 PB15 C SSC1 TK1 PA14 B SSC1 TK1 PB14 C 45.7.2 Power Management The SSC is not continuously clocked. The SSC interface may be clocked through the Power Management Controller (PMC), therefore the programmer must first configure the PMC to enable the SSC clock. 45.7.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.  2017 Microchip Technology Inc. DS60001476B-page 1281 SAMA5D2 SERIES All SSC interrupts can be enabled/disabled configuring the SSC Interrupt Mask Register. Each pending and unmasked SSC interrupt asserts the SSC interrupt line. The SSC interrupt service routine can get the interrupt origin by reading the SSC Interrupt Status Register. Table 45-3: Peripheral IDs Instance ID SSC0 43 SSC1 44 DS60001476B-page 1282  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.8 Functional Description This section contains the functional description of the following: SSC Functional Block, Clock Management, Data Format, Start, Transmit, Receive and Frame Synchronization. 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 TK or RK pins. This allows the SSC to support many Slave mode data transfers. The maximum clock speed allowed on the TK and RK pins is the peripheral clock divided by 2. Figure 45-6: SSC Functional Block Diagram Transmitter Peripheral Clock TK Input Clock Divider Transmit Clock Controller RX clock TXEN RX Start Start Selector TF TK Frame Sync Controller TF Data Controller TD TX Start Transmit Shift Register Transmit Holding Register APB TX clock Clock Output Controller Transmit Sync Holding Register User Interface Receiver RK Input RK Frame Sync Controller RF Data Controller RD Receive Clock RX Clock Controller TX Clock RXEN TX Start Start RF Selector RC0R Interrupt Control Clock Output Controller RX Start Receive Shift Register Receive Holding Register Receive Sync Holding Register To Interrupt Controller  2017 Microchip Technology Inc. DS60001476B-page 1283 SAMA5D2 SERIES 45.8.1 Clock Management The transmit clock can be generated by: • an external clock received on the TK I/O pad • the receive clock • the internal clock divider The receive clock can be generated by: • an external clock received on the RK I/O pad • the transmit clock • the internal clock divider Furthermore, the transmitter block can generate an external clock on the TK I/O pad, and the receive block can generate an external clock on the RK I/O pad. This allows the SSC to support many Master and Slave mode data transfers. 45.8.1.1 Clock Divider Figure 45-7: Divided Clock Block Diagram Clock Divider SSC_CMR Peripheral Clock /2 12-bit Counter Divided Clock The peripheral clock divider is determined by the 12-bit field DIV counter and comparator (so its maximal value is 4095) in the Clock Mode Register (SSC_CMR), allowing a peripheral clock division by up to 8190. The Divided Clock is provided to both the receiver and the 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 peripheral clock divided by 2 times DIV. Each level of the Divided Clock has a duration of the peripheral 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 45-8: Divided Clock Generation Peripheral Clock Divided Clock DIV = 1 Divided Clock Frequency = fperipheral clock/2 Peripheral Clock Divided Clock DIV = 3 Divided Clock Frequency = fperipheral clock/6 45.8.1.2 Transmit Clock Management The transmit clock is generated from the receive clock or the divider clock or an external clock scanned on the TK I/O pad. The transmit clock is selected by the CKS field in the Transmit Clock Mode Register (SSC_TCMR). Transmit Clock can be inverted independently by the CKI bits in the SSC_TCMR. DS60001476B-page 1284  2017 Microchip Technology Inc. SAMA5D2 SERIES The transmitter can also drive the TK I/O pad continuously or be limited to the current data transfer. The clock output is configured by the SSC_TCMR. The Transmit Clock Inversion (CKI) bits have no effect on the clock outputs. Programming the SSC_TCMR to select TK pin (CKS field) and at the same time Continuous Transmit Clock (CKO field) can lead to unpredictable results. Figure 45-9: Transmit Clock Management TK (pin) Tri_state Controller Receive Clock Clock Output MUX Divider Clock CKO CKS  2017 Microchip Technology Inc. Data Transfer INV MUX Tri_state Controller CKI CKG Transmit Clock DS60001476B-page 1285 SAMA5D2 SERIES 45.8.1.3 Receive Clock Management The receive clock is generated from the transmit clock or the divider clock or an external clock scanned on the RK I/O pad. The Receive Clock is selected by the CKS field in SSC_RCMR (Receive Clock Mode Register). Receive Clocks can be inverted independently by the CKI bits in SSC_RCMR. The receiver can also drive the RK I/O pad continuously or be limited to the current data transfer. The clock output is configured by the SSC_RCMR. The Receive Clock Inversion (CKI) bits have no effect on the clock outputs. Programming the SSC_RCMR to select RK pin (CKS field) and at the same time Continuous Receive Clock (CKO field) can lead to unpredictable results. Figure 45-10: Receive Clock Management RK (pin) Tri_state Controller Transmit Clock Clock Output MUX Divider Clock CKO CKS DS60001476B-page 1286 Data Transfer INV MUX Tri_state Controller CKI CKG Receive Clock  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.8.1.4 Serial Clock Ratio Considerations The transmitter and the receiver can be programmed to operate with the clock signals provided on either the TK or RK pins. This allows the SSC to support many Slave mode data transfers. In this case, the maximum clock speed allowed on the RK pin is: - Peripheral clock divided by 2 if Receive Frame Synchronization is input - Peripheral clock divided by 3 if Receive Frame Synchronization is output In addition, the maximum clock speed allowed on the TK pin is: - Peripheral clock divided by 6 if Transmit Frame Synchronization is input - Peripheral clock divided by 2 if Transmit Frame Synchronization is output 45.8.2 Transmit Operations A transmit 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 SSC_TCMR. Refer to Section 45.8.4 “Start”. The frame synchronization is configured setting the Transmit Frame Mode Register (SSC_TFMR). Refer to Section 45.8.5 “Frame Synchronization”. To transmit data, the transmitter uses a shift register clocked by the transmit clock signal and the start mode selected in the SSC_TCMR. Data is written by the application to the SSC_THR then transferred to the shift register according to the data format selected. When both the SSC_THR and the transmit shift register are empty, the status flag TXEMPTY is set in the SSC_SR. When the Transmit Holding register is transferred in the transmit shift register, the status flag TXRDY is set in the SSC_SR and additional data can be loaded in the holding register. Figure 45-11: Transmit Block Diagram SSC_CRTXEN SSC_SRTXEN TXEN SSC_CRTXDIS SSC_RCMR.START SSC_TCMR.START RXEN TXEN TX Start RX Start Start RF Selector RF RC0R SSC_TCMR.STTDLY SSC_TFMR.FSDEN SSC_TFMR.DATNB SSC_TFMR.DATDEF SSC_TFMR.MSBF TX Controller TX Start Start Selector TD Transmit Shift Register SSC_TFMR.FSDEN SSC_TCMR.STTDLY != 0 SSC_TFMR.DATLEN 0 SSC_THR Transmit Clock 1 SSC_TSHR SSC_TFMR.FSLEN TX Controller counter reached STTDLY 45.8.3 Receive Operations A receive 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 (SSC_RCMR). Refer to Section 45.8.4 “Start”. The frame synchronization is configured by setting the Receive Frame Mode Register (SSC_RFMR). Refer to Section 45.8.5 “Frame Synchronization”. The receiver uses a shift register clocked by the receive clock signal and the start mode selected in the SSC_RCMR. The data is transferred from the shift register depending on the data format selected.  2017 Microchip Technology Inc. DS60001476B-page 1287 SAMA5D2 SERIES When the receiver shift register is full, the SSC transfers this data in the holding register, the status flag RXRDY is set in the SSC_SR and the data can be read in the receiver holding register. If another transfer occurs before read of the Receive Holding Register (SSC_RHR), the status flag OVERUN is set in the SSC_SR and the receiver shift register is transferred in the SSC_RHR. Figure 45-12: Receive Block Diagram SSC_CR.RXEN SSC_SR.RXEN SSC_CR.RXDIS SSC_TCMR.START SSC_RCMR.START TXEN RX Start RF Start Selector RXEN RF RC0R Start Selector SSC_RFMR.MSBF SSC_RFMR.DATNB RX Start RX Controller RD Receive Shift Register SSC_RCMR.STTDLY != 0 load SSC_RSHR SSC_RFMR.FSLEN load SSC_RHR Receive Clock SSC_RFMR.DATLEN RX Controller counter reached STTDLY 45.8.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 SSC_TCMR and in the Receive Start Selection (START) field of SSC_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 SSC_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 TF/RF • On detection of a low level/high level on TF/RF • On detection of a level change or an edge on TF/RF A start can be programmed in the same manner on either side of the Transmit/Receive Clock Register (SSC_RCMR/SSC_TCMR). Thus, the start could be on TF (Transmit) or RF (Receive). Moreover, the receiver can start when data is detected in the bit stream with the Compare Functions. Detection on TF/RF input/output is done by the field FSOS of the Transmit/Receive Frame Mode Register (SSC_TFMR/SSC_RFMR). DS60001476B-page 1288  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 45-13: Transmit Start Mode TK TF (Input) Start = Low Level on TF Start = Falling Edge on TF Start = High Level on TF Start = Rising Edge on TF Start = Level Change on TF Start = Any Edge on TF TD (Output) TD (Output) X BO B1 STTDLY BO X B1 STTDLY BO X TD (Output) B1 STTDLY TD (Output) BO X B1 STTDLY TD (Output) BO X B1 BO B1 STTDLY TD (Output) X B1 BO BO B1 STTDLY Figure 45-14: Receive Pulse/Edge Start Modes RK RF (Input) Start = Low Level on RF RD (Input) Start = Falling Edge on RF RD (Input) Start = High Level on RF Start = Rising Edge on RF Start = Level Change on RF Start = Any Edge on RF 45.8.5 X BO STTDLY BO X B1 STTDLY RD (Input) BO X B1 STTDLY RD (Input) BO X B1 STTDLY RD (Input) RD (Input) B1 BO X B1 BO B1 STTDLY X BO B1 BO B1 STTDLY Frame Synchronization The Transmit and Receive Frame Sync pins, TF and RF, can be programmed to generate different kinds of Frame Sync signals. The Frame Sync Output Selection (FSOS) field in the Receive Frame Mode Register (SSC_RFMR) and in the Transmit Frame Mode Register (SSC_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 SSC_RFMR and SSC_TFMR programs the length of the pulse, from 1 bit time up to 256 bit times. The periodicity of the Receive and Transmit Frame Sync pulse output can be programmed through the Period Divider Selection (PERIOD) field in SSC_RCMR and SSC_TCMR.  2017 Microchip Technology Inc. DS60001476B-page 1289 SAMA5D2 SERIES 45.8.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 RD line and store the data in the Receive Sync Holding Register and the transmitter can transfer Transmit Sync Holding Register in the shift register. The data length to be sampled/shifted out during the Frame Sync signal is programmed by the FSLEN field in SSC_RFMR/SSC_TFMR and has a maximum value of 256. 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 current 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 SSC_TFMR is set. If the Frame Sync length is equal to or lower than the delay between the start event and the current 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. 45.8.5.2 Frame Sync Edge Detection The Frame Sync Edge detection is programmed by the FSEDGE field in SSC_RFMR/SSC_TFMR. This sets the corresponding flags RXSYN/TXSYN in the SSC Status Register (SSC_SR) on Frame Sync Edge detection (signals RF/TF). 45.8.6 Receive Compare Modes Figure 45-15: Receive Compare Modes RK RD (Input) CMP0 CMP1 CMP2 CMP3 Ignored B0 B1 B2 Start FSLEN 45.8.6.1 STDLY DATLEN Compare Functions The length of the comparison patterns (Compare 0, Compare 1) and thus the number of bits they are compared to is defined by FSLEN, but with a maximum value of 256 bits. Comparison is always done by comparing the last bits received with the comparison pattern. Compare 0 can be one start event of the receiver. In this case, the receiver compares at each new sample the last bits received at the Compare 0 pattern contained in the Compare 0 Register (SSC_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 STOP bit in the SSC_RCMR. DS60001476B-page 1290  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.8.7 Data Format The data framing format of both the transmitter and the receiver are programmable through the Transmitter Frame Mode Register (SSC_TFMR) and the Receive Frame Mode Register (SSC_RFMR). In either case, the user can independently select the following parameters: • • • • • • Event that starts the data transfer (START) Delay in number of bit periods between the start event and the first data bit (STTDLY) Length of the data (DATLEN) Number of data to be transferred for each start event (DATNB) Length of synchronization transferred for each start event (FSLEN) Bit sense: most or least significant bit first (MSBF) Additionally, the transmitter can be used to transfer synchronization and select the level driven on the TD 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 SSC_TFMR. Table 45-4: Data Frame Registers Transmitter Receiver Field Length Comment SSC_TFMR SSC_RFMR DATLEN Up to 32 Size of word SSC_TFMR SSC_RFMR DATNB Up to 16 Number of words transmitted in frame SSC_TFMR SSC_RFMR MSBF – Most significant bit first SSC_TFMR SSC_RFMR FSLEN Up to 256 Size of Synchro data register SSC_TFMR – DATDE F 0 or 1 Data default value ended SSC_TFMR – FSDEN – Enable send SSC_TSHR SSC_TCMR SSC_RCMR PERIOD Up to 512 Frame size SSC_TCMR SSC_RCMR STTDLY Up to 255 Size of transmit start delay Figure 45-16: Transmit and Receive Frame Format in Edge/Pulse Start Modes Start Start PERIOD (1) TF/RF FSLEN TD (If FSDEN = 1) Sync Data Default From SSC_TSHR From DATDEF TD (If FSDEN = 0) RD Default Data Default From SSC_THR From DATDEF Data Data From DATDEF Sync Data Data From SSC_THR Ignored To SSC_RSHR STTDLY From SSC_THR From SSC_THR Data Data To SSC_RHR To SSC_RHR DATLEN DATLEN Sync Data Default From DATDEF Ignored Sync Data DATNB Note: 1. Example of input on falling edge of TF/RF. In the example illustrated in Figure 45-17, the SSC_THR is loaded twice. The FSDEN value has no effect on the transmission. SyncData cannot be output in Continuous mode.  2017 Microchip Technology Inc. DS60001476B-page 1291 SAMA5D2 SERIES Figure 45-17: Transmit Frame Format in Continuous Mode (STTDLY = 0) Start Data TD Default Data From SSC_THR From SSC_THR DATLEN DATLEN Start: 1. TXEMPTY set to 1 2. Write into the SSC_THR Figure 45-18: Receive Frame Format in Continuous Mode (STTDLY = 0) Start = Enable Receiver RD 45.8.8 Data Data To SSC_RHR To SSC_RHR DATLEN DATLEN Loop Mode The receiver can be programmed to receive transmissions from the transmitter. This is done by setting the Loop Mode (LOOP) bit in the SSC_RFMR. In this case, RD is connected to TD, RF is connected to TF and RK is connected to TK. 45.8.9 Interrupt Most bits in the SSC_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 the Interrupt Enable Register (SSC_IER) and Interrupt Disable Register (SSC_IDR). These registers enable and disable, respectively, the corresponding interrupt by setting and clearing the corresponding bit in the Interrupt Mask Register (SSC_IMR), which controls the generation of interrupts by asserting the SSC interrupt line connected to the interrupt controller. DS60001476B-page 1292  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 45-19: Interrupt Block Diagram SSC_IMR SSC_IER SSC_IDR Set Clear Transmitter TXRDY TXEMPTY TXSYN Interrupt Control SSC Interrupt Receiver RXRDY OVRUN RXSYN 45.8.10 Register Write Protection To prevent any single software error from corrupting SSC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the SSC Write Protection Mode Register (SSC_WPMR). If a write access to a write-protected register is detected, the WPVS flag in the SSC Write Protection Status Register (SSC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading the SSC_WPSR. The following registers can be write-protected: • • • • • • • SSC Clock Mode Register SSC Receive Clock Mode Register SSC Receive Frame Mode Register SSC Transmit Clock Mode Register SSC Transmit Frame Mode Register SSC Receive Compare 0 Register SSC Receive Compare 1 Register  2017 Microchip Technology Inc. DS60001476B-page 1293 SAMA5D2 SERIES 45.9 Synchronous Serial Controller (SSC) User Interface Table 45-5: Offset Register Mapping Register 0x0 Control Register 0x4 Clock Mode Register 0x8–0xC Reserved Name Access Reset SSC_CR Write-only – SSC_CMR Read/Write 0x0 – – – 0x10 Receive Clock Mode Register SSC_RCMR Read/Write 0x0 0x14 Receive Frame Mode Register SSC_RFMR Read/Write 0x0 0x18 Transmit Clock Mode Register SSC_TCMR Read/Write 0x0 0x1C Transmit Frame Mode Register SSC_TFMR Read/Write 0x0 0x20 Receive Holding Register SSC_RHR Read-only 0x0 0x24 Transmit Holding Register SSC_THR Write-only – – – – 0x28–0x2C Reserved 0x30 Receive Sync. Holding Register SSC_RSHR Read-only 0x0 0x34 Transmit Sync. Holding Register SSC_TSHR Read/Write 0x0 0x38 Receive Compare 0 Register SSC_RC0R Read/Write 0x0 0x3C Receive Compare 1 Register SSC_RC1R Read/Write 0x0 0x40 Status Register SSC_SR Read-only 0x000000CC 0x44 Interrupt Enable Register SSC_IER Write-only – 0x48 Interrupt Disable Register SSC_IDR Write-only – 0x4C Interrupt Mask Register SSC_IMR Read-only 0x0 – – – 0x50–0xE0 Reserved 0xE4 Write Protection Mode Register SSC_WPMR Read/Write 0x0 0xE8 Write Protection Status Register SSC_WPSR Read-only 0x0 0xEC–0xFC Reserved – – – 0x100–0x124 Reserved – – – DS60001476B-page 1294  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.1 SSC Control Register Name: SSC_CR Address: 0xF8004000 (0), 0xFC004000 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 SWRST 14 – 13 – 12 – 11 – 10 – 9 TXDIS 8 TXEN 7 – 6 – 5 – 4 – 3 – 2 – 1 RXDIS 0 RXEN RXEN: Receive Enable 0: No effect. 1: Enables Receive if RXDIS 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. TXEN: Transmit Enable 0: No effect. 1: Enables Transmit if TXDIS is not set. TXDIS: Transmit Disable 0: No effect. 1: Disables Transmit. If a character is currently being transmitted, disables at end of current character transmission. SWRST: Software Reset 0: No effect. 1: Performs a software reset. Has priority on any other bit in SSC_CR.  2017 Microchip Technology Inc. DS60001476B-page 1295 SAMA5D2 SERIES 45.9.2 SSC Clock Mode Register Name: SSC_CMR Address: 0xF8004004 (0), 0xFC004004 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 7 6 5 4 1 0 DIV 3 2 DIV This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. DIV: Clock Divider 0: The Clock Divider is not active. Any other value: The divided clock equals the peripheral clock divided by 2 times DIV. The maximum bit rate is fperipheral clock/2. The minimum bit rate is fperipheral clock/2 × 4095 = fperipheral clock/8190. DS60001476B-page 1296  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.3 SSC Receive Clock Mode Register Name: SSC_RCMR Address: 0xF8004010 (0), 0xFC004010 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 10 9 8 PERIOD 23 22 21 20 STTDLY 15 – 7 14 – 13 – 12 STOP 11 6 5 CKI 4 3 CKO CKG START 2 1 0 CKS This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. CKS: Receive Clock Selection Value Name Description 0 MCK Divided Clock 1 TK TK Clock signal 2 RK RK pin CKO: Receive Clock Output Mode Selection Value Name Description 0 NONE None, RK pin is an input 1 CONTINUOUS Continuous Receive Clock, RK pin is an output 2 TRANSFER Receive Clock only during data transfers, RK pin is an output 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. CKG: Receive Clock Gating Selection Value Name Description 0 CONTINUOUS None 1 EN_RF_LOW Receive Clock enabled only if RF Low 2 EN_RF_HIGH Receive Clock enabled only if RF High  2017 Microchip Technology Inc. DS60001476B-page 1297 SAMA5D2 SERIES START: Receive Start Selection Value Name Description 0 CONTINUOUS Continuous, as soon as the receiver is enabled, and immediately after the end of transfer of the previous data. 1 TRANSMIT Transmit start 2 RF_LOW Detection of a low level on RF signal 3 RF_HIGH Detection of a high level on RF signal 4 RF_FALLING Detection of a falling edge on RF signal 5 RF_RISING Detection of a rising edge on RF signal 6 RF_LEVEL Detection of any level change on RF signal 7 RF_EDGE Detection of any edge on RF signal 8 CMP_0 Compare 0 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. STTDLY: Receive Start Delay If STTDLY is not 0, a delay of STTDLY clock cycles is inserted between the start event and the current 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. 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. DS60001476B-page 1298  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.4 SSC Receive Frame Mode Register Name: SSC_RFMR Address: 0xF8004014 (0), 0xFC004014 (1) Access: Read/Write 31 30 29 28 27 – 26 – 21 FSOS 20 19 18 FSLEN_EXT 23 – 22 15 – 14 – 13 – 12 – 11 7 MSBF 6 – 5 LOOP 4 3 25 – 24 FSEDGE 17 16 9 8 1 0 FSLEN 10 DATNB 2 DATLEN This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. DATLEN: Data Length 0: Forbidden value (1-bit data length not supported). Any other value: The bit stream contains DATLEN + 1 data bits. LOOP: Loop Mode 0: Normal operating mode. 1: RD is driven by TD, RF is driven by TF and TK drives RK. 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. DATNB: Data Number per Frame This field defines the number of data words to be received after each transfer start, which is equal to (DATNB + 1). FSLEN: Receive Frame Sync Length This field defines 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. This field is used with FSLEN_EXT to determine the pulse length of the Receive Frame Sync signal. Pulse length is equal to FSLEN + (FSLEN_EXT × 16) + 1 Receive Clock periods. FSOS: Receive Frame Sync Output Selection Value Name Description 0 NONE None, RF pin is an input 1 NEGATIVE Negative Pulse, RF pin is an output 2 POSITIVE Positive Pulse, RF pin is an output 3 LOW Driven Low during data transfer, RF pin is an output 4 HIGH Driven High during data transfer, RF pin is an output 5 TOGGLING Toggling at each start of data transfer, RF pin is an output  2017 Microchip Technology Inc. DS60001476B-page 1299 SAMA5D2 SERIES FSEDGE: Frame Sync Edge Detection Determines which edge on Frame Sync will generate the interrupt RXSYN in the SSC Status Register. Value Name Description 0 POSITIVE Positive Edge Detection 1 NEGATIVE Negative Edge Detection FSLEN_EXT: FSLEN Field Extension Extends FSLEN field. For details, refer to ”FSLEN: Receive Frame Sync Length”. DS60001476B-page 1300  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.5 SSC Transmit Clock Mode Register Name: SSC_TCMR Address: 0xF8004018 (0), 0xFC004018 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 10 9 8 PERIOD 23 22 21 20 STTDLY 15 – 7 14 – 13 – 12 – 11 6 5 CKI 4 3 CKO CKG START 2 1 0 CKS This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. CKS: Transmit Clock Selection Value Name Description 0 MCK Divided Clock 1 RK RK Clock signal 2 TK TK pin CKO: Transmit Clock Output Mode Selection Value Name Description 0 NONE None, TK pin is an input 1 CONTINUOUS Continuous Transmit Clock, TK pin is an output 2 TRANSFER Transmit Clock only during data transfers, TK pin is an output 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. CKG: Transmit Clock Gating Selection Value Name Description 0 CONTINUOUS None 1 EN_TF_LOW Transmit Clock enabled only if TF Low 2 EN_TF_HIGH Transmit Clock enabled only if TF High  2017 Microchip Technology Inc. DS60001476B-page 1301 SAMA5D2 SERIES START: Transmit Start Selection Value Name Description 0 CONTINUOUS Continuous, as soon as a word is written in the SSC_THR (if Transmit is enabled), and immediately after the end of transfer of the previous data 1 RECEIVE Receive start 2 TF_LOW Detection of a low level on TF signal 3 TF_HIGH Detection of a high level on TF signal 4 TF_FALLING Detection of a falling edge on TF signal 5 TF_RISING Detection of a rising edge on TF signal 6 TF_LEVEL Detection of any level change on TF signal 7 TF_EDGE Detection of any edge on TF signal STTDLY: Transmit Start Delay If STTDLY is not 0, a delay of STTDLY clock cycles is inserted between the start event and the current 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) transmission, data is transmitted instead of the end of TAG. 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 × (PERIOD + 1) Transmit Clock. DS60001476B-page 1302  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.6 SSC Transmit Frame Mode Register Name: SSC_TFMR Address: 0xF800401C (0), 0xFC00401C (1) Access: Read/Write 31 30 29 28 27 – 26 – 21 FSOS 20 19 18 FSLEN_EXT 23 FSDEN 22 15 – 14 – 13 – 12 – 11 7 MSBF 6 – 5 DATDEF 4 3 25 – 24 FSEDGE 17 16 9 8 1 0 FSLEN 10 DATNB 2 DATLEN This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. DATLEN: Data Length 0: Forbidden value (1-bit data length not supported). Any other value: The bit stream contains DATLEN + 1 data bits. DATDEF: Data Default Value This bit defines the level driven on the TD 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 TD output is 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. 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). 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. This field is used with FSLEN_EXT to determine the pulse length of the Transmit Frame Sync signal. Pulse length is equal to FSLEN + (FSLEN_EXT × 16) + 1 Transmit Clock period. FSOS: Transmit Frame Sync Output Selection Value Name Description 0 NONE None, TF pin is an input 1 NEGATIVE Negative Pulse, TF pin is an output 2 POSITIVE Positive Pulse, TF pin is an output 3 LOW Driven Low during data transfer 4 HIGH Driven High during data transfer 5 TOGGLING Toggling at each start of data transfer  2017 Microchip Technology Inc. DS60001476B-page 1303 SAMA5D2 SERIES FSDEN: Frame Sync Data Enable 0: The TD line is driven with the default value during the Transmit Frame Sync signal. 1: SSC_TSHR value is shifted out during the transmission of the Transmit Frame Sync signal. FSEDGE: Frame Sync Edge Detection Determines which edge on frame synchronization will generate the interrupt TXSYN (Status Register). Value Name Description 0 POSITIVE Positive Edge Detection 1 NEGATIVE Negative Edge Detection FSLEN_EXT: FSLEN Field Extension Extends FSLEN field. For details, refer to FSLEN bit description above. DS60001476B-page 1304  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.7 SSC Receive Holding Register Name: SSC_RHR Address: 0xF8004020 (0), 0xFC004020 (1) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RDAT 23 22 21 20 RDAT 15 14 13 12 RDAT 7 6 5 4 RDAT RDAT: Receive Data Right aligned regardless of the number of data bits defined by DATLEN in SSC_RFMR.  2017 Microchip Technology Inc. DS60001476B-page 1305 SAMA5D2 SERIES 45.9.8 SSC Transmit Holding Register Name: SSC_THR Address: 0xF8004024 (0), 0xFC004024 (1) Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TDAT 23 22 21 20 TDAT 15 14 13 12 TDAT 7 6 5 4 TDAT TDAT: Transmit Data Right aligned regardless of the number of data bits defined by DATLEN in SSC_TFMR. DS60001476B-page 1306  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.9 SSC Receive Synchronization Holding Register Name: SSC_RSHR Address: 0xF8004030 (0), 0xFC004030 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RSDAT 7 6 5 4 RSDAT RSDAT: Receive Synchronization Data  2017 Microchip Technology Inc. DS60001476B-page 1307 SAMA5D2 SERIES 45.9.10 SSC Transmit Synchronization Holding Register Name: SSC_TSHR Address: 0xF8004034 (0), 0xFC004034 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TSDAT 7 6 5 4 TSDAT TSDAT: Transmit Synchronization Data DS60001476B-page 1308  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.11 SSC Receive Compare 0 Register Name: SSC_RC0R Address: 0xF8004038 (0), 0xFC004038 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 CP0 7 6 5 4 CP0 This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. CP0: Receive Compare Data 0  2017 Microchip Technology Inc. DS60001476B-page 1309 SAMA5D2 SERIES 45.9.12 SSC Receive Compare 1 Register Name: SSC_RC1R Address: 0xF800403C (0), 0xFC00403C (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 CP1 7 6 5 4 CP1 This register can only be written if the WPEN bit is cleared in the SSC Write Protection Mode Register. CP1: Receive Compare Data 1 DS60001476B-page 1310  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.13 SSC Status Register Name: SSC_SR Address: 0xF8004040 (0), 0xFC004040 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 RXEN 16 TXEN 15 – 14 – 13 – 12 – 11 RXSYN 10 TXSYN 9 CP1 8 CP0 7 – 6 – 5 OVRUN 4 RXRDY 3 – 2 – 1 TXEMPTY 0 TXRDY TXRDY: Transmit Ready 0: Data has been loaded in SSC_THR and is waiting to be loaded in the transmit shift register (TSR). 1: SSC_THR is empty. TXEMPTY: Transmit Empty 0: Data remains in SSC_THR or is currently transmitted from TSR. 1: Last data written in SSC_THR has been loaded in TSR and last data loaded in TSR has been transmitted. RXRDY: Receive Ready 0: SSC_RHR is empty. 1: Data has been received and loaded in SSC_RHR. OVRUN: Receive Overrun 0: No data has been loaded in SSC_RHR while previous data has not been read since the last read of the Status Register. 1: Data has been loaded in SSC_RHR while previous data has not yet been read 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. 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. 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.  2017 Microchip Technology Inc. DS60001476B-page 1311 SAMA5D2 SERIES 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. TXEN: Transmit Enable 0: Transmit is disabled. 1: Transmit is enabled. RXEN: Receive Enable 0: Receive is disabled. 1: Receive is enabled. DS60001476B-page 1312  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.14 SSC Interrupt Enable Register Name: SSC_IER Address: 0xF8004044 (0), 0xFC004044 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 RXSYN 10 TXSYN 9 CP1 8 CP0 7 – 6 – 5 OVRUN 4 RXRDY 3 – 2 – 1 TXEMPTY 0 TXRDY TXRDY: Transmit Ready Interrupt Enable 0: No effect. 1: Enables the Transmit Ready Interrupt. TXEMPTY: Transmit Empty Interrupt Enable 0: No effect. 1: Enables the Transmit Empty Interrupt. RXRDY: Receive Ready Interrupt Enable 0: No effect. 1: Enables the Receive Ready Interrupt. OVRUN: Receive Overrun Interrupt Enable 0: No effect. 1: Enables the Receive Overrun Interrupt. CP0: Compare 0 Interrupt Enable 0: No effect. 1: Enables the Compare 0 Interrupt. CP1: Compare 1 Interrupt Enable 0: No effect. 1: Enables the Compare 1 Interrupt. TXSYN: Tx Sync Interrupt Enable 0: No effect. 1: Enables the Tx Sync Interrupt. RXSYN: Rx Sync Interrupt Enable 0: No effect. 1: Enables the Rx Sync Interrupt.  2017 Microchip Technology Inc. DS60001476B-page 1313 SAMA5D2 SERIES 45.9.15 SSC Interrupt Disable Register Name: SSC_IDR Address: 0xF8004048 (0), 0xFC004048 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 RXSYN 10 TXSYN 9 CP1 8 CP0 7 – 6 – 5 OVRUN 4 RXRDY 3 – 2 – 1 TXEMPTY 0 TXRDY TXRDY: Transmit Ready Interrupt Disable 0: No effect. 1: Disables the Transmit Ready Interrupt. TXEMPTY: Transmit Empty Interrupt Disable 0: No effect. 1: Disables the Transmit Empty Interrupt. RXRDY: Receive Ready Interrupt Disable 0: No effect. 1: Disables the Receive Ready Interrupt. OVRUN: Receive Overrun Interrupt Disable 0: No effect. 1: Disables the Receive Overrun Interrupt. CP0: Compare 0 Interrupt Disable 0: No effect. 1: Disables the Compare 0 Interrupt. CP1: Compare 1 Interrupt Disable 0: No effect. 1: Disables the Compare 1 Interrupt. TXSYN: Tx Sync Interrupt Enable 0: No effect. 1: Disables the Tx Sync Interrupt. RXSYN: Rx Sync Interrupt Enable 0: No effect. 1: Disables the Rx Sync Interrupt. DS60001476B-page 1314  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.16 SSC Interrupt Mask Register Name: SSC_IMR Address: 0xF800404C (0), 0xFC00404C (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 RXSYN 10 TXSYN 9 CP1 8 CP0 7 – 6 – 5 OVRUN 4 RXRDY 3 – 2 – 1 TXEMPTY 0 TXRDY TXRDY: Transmit Ready Interrupt Mask 0: The Transmit Ready Interrupt is disabled. 1: The Transmit Ready Interrupt is enabled. TXEMPTY: Transmit Empty Interrupt Mask 0: The Transmit Empty Interrupt is disabled. 1: The Transmit Empty Interrupt is enabled. RXRDY: Receive Ready Interrupt Mask 0: The Receive Ready Interrupt is disabled. 1: The Receive Ready Interrupt is enabled. OVRUN: Receive Overrun Interrupt Mask 0: The Receive Overrun Interrupt is disabled. 1: The Receive Overrun Interrupt is enabled. CP0: Compare 0 Interrupt Mask 0: The Compare 0 Interrupt is disabled. 1: The Compare 0 Interrupt is enabled. CP1: Compare 1 Interrupt Mask 0: The Compare 1 Interrupt is disabled. 1: The Compare 1 Interrupt is enabled. TXSYN: Tx Sync Interrupt Mask 0: The Tx Sync Interrupt is disabled. 1: The Tx Sync Interrupt is enabled. RXSYN: Rx Sync Interrupt Mask 0: The Rx Sync Interrupt is disabled. 1: The Rx Sync Interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1315 SAMA5D2 SERIES 45.9.17 SSC Write Protection Mode Register Name: SSC_WPMR Address: 0xF80040E4 (0), 0xFC0040E4 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x535343 (“SSC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x535343 (“SSC” in ASCII). Refer to Section 45.8.10 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value 0x535343 Name PASSWD DS60001476B-page 1316 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 45.9.18 SSC Write Protection Status Register Name: SSC_WPSR Address: 0xF80040E8 (0), 0xFC0040E8 (1) Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of the SSC_WPSR. 1: A write protection violation has occurred since the last read of the SSC_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protect Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.  2017 Microchip Technology Inc. DS60001476B-page 1317 SAMA5D2 SERIES 46. Two-wire Interface (TWIHS) 46.1 Description The Two-wire Interface (TWIHS) interconnects components on a unique two-wire bus, made up of one clock line and one data line with speeds of up to 400 kbit/s in Fast mode and up to 3.4 Mbit/s in High-speed slave mode only, based on a byte-oriented transfer format. It can be used with any Two-wire Interface bus Serial EEPROM and I²C-compatible devices, such as a Real-Time Clock (RTC), Dot Matrix/ Graphic LCD Controller and temperature sensor. The TWIHS is programmable as a master or a slave with sequential or single-byte access. Multiple master capability is supported. A configurable baud rate generator permits the output data rate to be adapted to a wide range of core clock frequencies. Table 46-1 lists the compatibility level of the Two-wire Interface in Master mode and a full I2C compatible device. TWI Compatibility with I2C Standard Table 46-1: I2C Standard TWI Standard Mode Speed (100 kHz) Supported Fast Mode Speed (400 kHz) Supported High-speed Mode (Slave only, 3.4 MHz) Supported 7- or 10-bit(1) START Slave Addressing Byte(2) Supported Not Supported Repeated Start (Sr) Condition Supported ACK and NACK Management Supported Input Filtering Supported Slope Control Not Supported Clock Stretching Supported Multi Master Capability Supported Note 1: 10-bit support in Master mode only 2: START + b000000001 + Ack + Sr DS60001476B-page 1318  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.2 • • • • • • • • • • • • • Embedded Characteristics 2 TWIHSs 16-byte Transmit and Receive FIFOs Compatible with Two-wire Interface Serial Memory and I²C Compatible Devices(1) One, Two or Three Bytes for Slave Address Sequential Read/Write Operations Master and Multimaster Operation (Standard and Fast Modes Only) Slave Mode Operation (Standard, Fast and High-Speed Modes) Bit Rate: Up to 400 Kbit/s in Fast Mode and 3.4 Mbit/s in High-Speed Mode (Slave Mode Only) General Call Supported in Slave Mode SleepWalking (Asynchronous and Partial Wakeup) SMBus Support Connection to DMA Controller (DMA) Channel Capabilities Optimizes Data Transfers Register Write Protection Note 1: See Table 46-1 for details on compatibility with I²C Standard. 46.3 List of Abbreviations Table 46-2: Abbreviations Abbreviation Description TWI Two-wire Interface A Acknowledge NA Non Acknowledge P Stop S Start Sr Repeated Start SADR Slave Address ADR Any address except SADR R Read W Write  2017 Microchip Technology Inc. DS60001476B-page 1319 SAMA5D2 SERIES 46.4 Block Diagram Figure 46-1: Block Diagram Peripheral Bridge TWCK PIO PMC Peripheral Clock GCLK 46.4.1 TWD Two-wire Interface TWIHS Interrupt Interrupt Controller I/O Lines Description Table 46-3: I/O Lines Description Pin Name Pin Description Type TWD Two-wire Serial Data Input/Output TWCK Two-wire Serial Clock Input/Output DS60001476B-page 1320  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.5 Product Dependencies 46.5.1 I/O Lines Both TWD and TWCK are bidirectional lines, connected to a positive supply voltage via a current source or pull-up resistor. When the bus is free, both lines are high. The output stages of devices connected to the bus must have an open-drain or open-collector to perform the wired-AND function. TWD and TWCK pins may be multiplexed with PIO lines. To enable the TWIHS, the user must program the PIO Controller to dedicate TWD and TWCK as peripheral lines. When High-speed Slave mode is enabled, the analog pad filter must be enabled. The user must not program TWD and TWCK as open-drain. This is already done by the hardware. Table 46-4: I/O Lines Instance Signal I/O Line Peripheral TWIHS0 TWCK0 PC0 D TWIHS0 TWCK0 PC28 E TWIHS0 TWCK0 PD22 B TWIHS0 TWCK0 PD30 E TWIHS0 TWD0 PB31 D TWIHS0 TWD0 PC27 E TWIHS0 TWD0 PD21 B TWIHS0 TWD0 PD29 E TWIHS1 TWCK1 PC7 C TWIHS1 TWCK1 PD5 A TWIHS1 TWCK1 PD20 B TWIHS1 TWD1 PC6 C TWIHS1 TWD1 PD4 A TWIHS1 TWD1 PD19 B 46.5.2 Power Management Enable the peripheral clock. The TWIHS may be clocked through the Power Management Controller (PMC), thus the user must first configure the PMC to enable the TWIHS clock. 46.5.3 Interrupt Sources The TWIHS has an interrupt line connected to the Interrupt Controller. In order to handle interrupts, the Interrupt Controller must be programmed before configuring the TWIHS. Table 46-5: Peripheral IDs Instance ID TWIHS0 29 TWIHS1 30  2017 Microchip Technology Inc. DS60001476B-page 1321 SAMA5D2 SERIES 46.6 46.6.1 Functional Description Transfer Format The data put on the TWD line must be 8 bits long. Data is transferred MSB first; each byte must be followed by an acknowledgement. The number of bytes per transfer is unlimited. See Figure 46-3. Each transfer begins with a START condition and terminates with a STOP condition. See Figure 46-2. • A high-to-low transition on the TWD line while TWCK is high defines the START condition. • A low-to-high transition on the TWD line while TWCK is high defines the STOP condition. Figure 46-2: START and STOP Conditions TWD TWCK Start Figure 46-3: Stop Transfer Format TWD TWCK Start 46.6.2 Address R/W Ack Data Ack Data Ack Stop Modes of Operation The TWIHS has different modes of operation: • • • • • • Master Transmitter mode (Standard and Fast modes only) Master Receiver mode (Standard and Fast modes only) Multimaster Transmitter mode (Standard and Fast modes only) Multimaster Receiver mode (Standard and Fast modes only) Slave Transmitter mode (Standard, Fast and High-speed modes) Slave Receiver mode (Standard, Fast and High-speed modes) These modes are described in the following sections. DS60001476B-page 1322  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.6.3 Master Mode 46.6.3.1 Definition The master is the device that starts a transfer, generates a clock and stops it. This operating mode is not available if High-speed mode is selected. 46.6.3.2 Programming Master Mode The following registers must be programmed before entering Master mode: 1. 2. 3. 4. TWIHS_MMR.DADR (+ IADRSZ + IADR if a 10-bit device is addressed): The device address is used to access slave devices in Read or Write mode. TWIHS_CWGR.CKDIV + CHDIV + CLDIV: Clock Waveform register TWIHS_CR.SVDIS: Disables the Slave mode TWIHS_CR.MSEN: Enables the Master mode Note: 46.6.3.3 If the TWIHS is already in Master mode, the device address (DADR) can be configured without disabling the Master mode. Transfer Rate Clock Source The TWIHS speed is defined in the TWIHS_CWGR. The TWIHS baud rate can be based either on the peripheral clock if the CKSRC bit value is ‘0’ or on a GCLK clock if the CKSRC bit value is ‘1’. If CKSRC = 1, the baud rate is independent of the system/core clock (MCK) and thus the MCK frequency can be changed without affecting the TWIHS transfer rate. The GCLK frequency must always be three times lower than the peripheral clock frequency. 46.6.3.4 Master Transmitter Mode This operating mode is not available if High-speed mode is selected. After the master initiates a START condition when writing into the Transmit Holding register (TWIHS_THR), it sends a 7-bit slave address, configured in the Master Mode register (DADR in TWIHS_MMR), to notify the slave device. The bit following the slave address indicates the transfer direction, 0 in this case (MREAD = 0 in TWIHS_MMR). The TWIHS transfers require the slave to acknowledge each received byte. During the acknowledge clock pulse (9th pulse), the master releases the data line (HIGH), enabling the slave to pull it down in order to generate the acknowledge. If the slave does not acknowledge the byte, then the Not Acknowledge flag (NACK) is set in the TWIHS Status Register (TWIHS_SR) of the master and a STOP condition is sent. The NACK flag must be cleared by reading TWIHS_SR before the next write into TWIHS_THR. As with the other status bits, an interrupt can be generated if enabled in the Interrupt Enable register (TWIHS_IER). If the slave acknowledges the byte, the data written in the TWIHS_THR is then shifted in the internal shifter and transferred. When an acknowledge is detected, the TXRDY bit is set until a new write in the TWIHS_THR. TXRDY is used as Transmit Ready for the DMA transmit channel. While no new data is written in the TWIHS_THR, the serial clock line is tied low. When new data is written in the TWIHS_THR, the SCL is released and the data is sent. Setting the STOP bit in TWIHS_CR generates a STOP condition. After a master write transfer, the serial clock line is stretched (tied low) as long as no new data is written in the TWIHS_THR or until a STOP command is performed. To clear the TXRDY flag, first set the bit TWIHS_CR.MSDIS, then set the bit TWIHS_CR.MSEN. See Figure 46-4, Figure 46-5, and Figure 46-6.  2017 Microchip Technology Inc. DS60001476B-page 1323 SAMA5D2 SERIES Figure 46-4: Master Write with One Data Byte STOP Command sent (write in TWI_CR) S TWD DADR W A DATA A P TXCOMP TXRDY Write TWI_THR (DATA) Figure 46-5: Master Write with Multiple Data Bytes STOP command performed (by writing in the TWI_CR) S TWD DADR W A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP TXRDY Write TWI_THR (Data n) Write TWI_THR (Data n+1) Figure 46-6: Write TWI_THR (Data n+2) Last data sent Master Write with One-Byte Internal Address and Multiple Data Bytes STOP command performed (by writing in the TWI_CR) TWD S DADR W A IADR A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP TXRDY Write TWI_THR (Data n) Write TWI_THR (Data n+1) DS60001476B-page 1324 Write TWI_THR (Data n+2) Last data sent  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.6.3.5 Master Receiver Mode Master Receiver mode is not available if High-speed mode is selected. The read sequence begins by setting the START bit. After the START condition has been sent, the master sends a 7-bit slave address to notify the slave device. The bit following the slave address indicates the transfer direction, 1 in this case (MREAD = 1 in TWIHS_MMR). During the acknowledge clock pulse (9th pulse), the master releases the data line (HIGH), enabling the slave to pull it down in order to generate the acknowledge. The master polls the data line during this clock pulse and sets the NACK bit in the TWIHS_SR if the slave does not acknowledge the byte. If an acknowledge is received, the master is then ready to receive data from the slave. After data has been received, the master sends an acknowledge condition to notify the slave that the data has been received except for the last data (see Figure 46-7). When the RXRDY bit is set in the TWIHS_SR, a character has been received in the Receive Holding register (TWIHS_RHR). The RXRDY bit is reset when reading the TWIHS_RHR. When a single data byte read is performed, with or without internal address (IADR), the START and STOP bits must be set at the same time. See Figure 46-7. When a multiple data byte read is performed, with or without internal address (IADR), the STOP bit must be set after the next-to-last data received (same condition applies for START bit to generate a REPEATED START). See Figure 46-8. For internal address usage, see Section 46.6.3.6, Internal Address. If TWIHS_RHR is full (RXRDY high) and the master is receiving data, the serial clock line is tied low before receiving the last bit of the data and until the TWIHS_RHR is read. Once the TWIHS_RHR is read, the master stops stretching the serial clock line and ends the data reception. See Figure 46-9. Warning: When receiving multiple bytes in Master Read mode, if the next-to-last access is not read (the RXRDY flag remains high), the last access is not completed until TWIHS_RHR is read. The last access stops on the next-to-last bit (clock stretching). When the TWIHS_RHR is read, there is only half a bit period to send the STOP (or START) command, else another read access might occur (spurious access). A possible workaround is to set the STOP (or START) bit before reading the TWIHS_RHR on the next-to-last access (within IT handler). Figure 46-7: Master Read with One Data Byte S TWD DADR R A DATA N P TXCOMP Write START & STOP Bit RXRDY Read RHR Figure 46-8: TWD Master Read with Multiple Data Bytes S DADR R A DATA n A DATA (n+1) A DATA (n+m)-1 A DATA (n+m) N P TXCOMP Write START Bit RXRDY Read RHR DATA n Read RHR DATA (n+1) Read RHR DATA (n+m)-1 Read RHR DATA (n+m) Write STOP Bit after next-to-last data read  2017 Microchip Technology Inc. DS60001476B-page 1325 SAMA5D2 SERIES Figure 46-9: Master Read Clock Stretching with Multiple Data Bytes STOP command performed (by writing in the TWI_CR) Clock Streching S TWD DADR W A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP RXRDY Read RHR (Data n) Read RHR (Data n+1) Read RHR (Data n+2) RXRDY is used as receive ready for the DMA receive channel. 46.6.3.6 Internal Address The TWIHS can perform transfers with 7-bit slave address devices and with 10-bit slave address devices. • 7-bit Slave Addressing When addressing 7-bit slave devices, the internal address bytes are used to perform random address (read or write) accesses to reach one or more data bytes, e.g. within a memory page location in a serial memory. When performing read operations with an internal address, the TWIHS performs a write operation to set the internal address into the slave device, and then switch to Master Receiver mode. Note that the second START condition (after sending the IADR) is sometimes called “repeated start” (Sr) in I2C fully-compatible devices. See Figure 46-11. See Figure 46-10 and Figure 46-12 for the master write operation with internal address. The three internal address bytes are configurable through TWIHS_MMR. If the slave device supports only a 7-bit address, i.e., no internal address, IADRSZ must be set to 0. Table 46-6 shows the abbreviations used in Figure 46-10 and Figure 46-11. Table 46-6: Abbreviations Abbreviation Definition S Start Sr Repeated Start P Stop W Write R Read A Acknowledge NA Not Acknowledge DADR Device Address IADR Internal Address DS60001476B-page 1326  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-10: Master Write with One-, Two- or Three-Byte Internal Address and One Data Byte Three bytes internal address S TWD DADR W A IADR(23:16) A IADR(15:8) A IADR(7:0) A W A IADR(15:8) A IADR(7:0) A DATA A W A IADR(7:0) A DATA A DATA A P Two bytes internal address S TWD DADR P One byte internal address S TWD DADR Figure 46-11: P Master Read with One-, Two- or Three-Byte Internal Address and One Data Byte Three bytes internal address S TWD DADR A W IADR(23:16) A IADR(15:8) A IADR(7:0) A Sr DADR R A DATA N P Two bytes internal address S TWD DADR W A IADR(15:8) A IADR(7:0) A Sr W A IADR(7:0) A Sr R A DADR R A DATA N P One byte internal address TWD S DADR DADR DATA N P • 10-bit Slave Addressing For a slave address higher than seven bits, configure the address size (IADRSZ) and set the other slave address bits in the Internal Address register (TWIHS_IADR). The two remaining internal address bytes, IADR[15:8] and IADR[23:16], can be used the same way as in 7-bit slave addressing. Example: Address a 10-bit device (10-bit device address is b1 b2 b3 b4 b5 b6 b7 b8 b9 b10) 1. 2. 3. Program IADRSZ = 1, Program DADR with 1 1 1 1 0 b1 b2 (b1 is the MSB of the 10-bit address, b2, etc.) Program TWIHS_IADR with b3 b4 b5 b6 b7 b8 b9 b10 (b10 is the LSB of the 10-bit address) Figure 46-12 shows a byte write to a memory device. This demonstrates the use of internal addresses to access the device. Figure 46-12: Internal Address Usage S T A R T W R I T E Device Address FIRST WORD ADDRESS SECOND WORD ADDRESS S T O P DATA 0 M S B 46.6.3.7 LR A S / C BW K M S B A C K LA SC BK A C K Repeated Start In addition to Internal Address mode, REPEATED START (Sr) can be generated manually by writing the START bit at the end of a transfer instead of the STOP bit. In such case, the parameters of the next transfer (direction, SADR, etc.) need to be set before writing the START bit at the end of the previous transfer. See Section 46.6.3.14 “Read/Write Flowcharts” for detailed flowcharts. Note that generating a REPEATED START after a single data read is not supported. 46.6.3.8 Bus Clear Command The TWIHS can perform a Bus Clear command: 1. 2. Configure the Master mode (DADR, CKDIV, etc). Start the transfer by setting the CLEAR bit in the TWIHS_CR. Note: If alternative command is used (ACMEN bit set to ‘1’) DATAL field must be set to 0.  2017 Microchip Technology Inc. DS60001476B-page 1327 SAMA5D2 SERIES 46.6.3.9 Using the DMA Controller (DMAC) in Master Mode The use of the DMA significantly reduces the CPU load. To ensure correct implementation, follow the programming sequences below: • Data Transmit with the DMA in Master Mode If Alternative Command mode is disabled (ACMEN bit set to ‘0’): The DMA transfer size must be defined with the buffer size minus 1. The remaining character must be managed without DMA to ensure that the exact number of bytes are transmitted regardless of system bus latency conditions during the end of the buffer transfer period. 1. 2. 3. 4. 5. 6. 7. 8. 9. Initialize the DMA (channels, memory pointers, size - 1, etc.); Configure the Master mode (DADR, CKDIV, MREAD = 0, etc.) or Slave mode. Enable the DMA. Wait for the DMA status flag indicating that the buffer transfer is complete. Disable the DMA. Wait for the TXRDY flag in TWIHS_SR. Set the STOP bit in TWIHS_CR. Write the last character in TWIHS_THR. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. If Alternative Command mode is enabled (ACMEN bit set to ‘1’): 1. 2. 3. 4. 5. 6. Initialize the transmit DMA (memory pointers, transfer size). Configure the Master mode (DADR, CKDIV, etc.) and TWIHS_ACR. Start the transfer by setting the DMA TXTEN bit. Wait for the DMA ENDTX flag either by using the polling method or ENDTX interrupt. Disable the DMA by setting the DMA TXTDIS bit. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. • Data Receive with the DMA in Master Mode If Alternative Command mode is disabled (ACMEN bit set to ‘0’): The DMA transfer size must be defined with the buffer size minus 2. The two remaining characters must be managed without DMA to ensure that the exact number of bytes are received regardless of system bus latency conditions encountered during the end of buffer transfer period. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Initialize the DMA (channels, memory pointers, size - 2, etc.); Configure the Master mode (DADR, CKDIV, MREAD = 1, etc.) or Slave mode. Enable the DMA. (Master Only) Write the START bit in the TWIHS_CR to start the transfer. Wait for the DMA status flag indicating that the buffer transfer is complete. Disable the DMA. Wait for the RXRDY flag in the TWIHS_SR. Set the STOP bit in TWIHS_CR. Read the penultimate character in TWIHS_RHR. Wait for the RXRDY flag in the TWIHS_SR. Read the last character in TWIHS_RHR. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. DS60001476B-page 1328  2017 Microchip Technology Inc. SAMA5D2 SERIES If Alternative Command mode is enabled (ACMEN bit set to ‘1’): 1. 2. 3. 4. 5. 6. 7. Initialize the transmit DMA (memory pointers, transfer size). Configure the Master mode (DADR, CKDIV, etc.) and TWIHS_ACR. Set the DMA RXTEN bit. (Master Only) Write the START bit in the TWIHS_CR to start the transfer. Wait for the DMA ENDTX Flag either by using the polling method or ENDTX interrupt. Disable the DMA by setting the DMA TXTDIS bit. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. 46.6.3.10 SMBus Mode SMBus mode is enabled when a one is written to the SMEN bit in the TWIHS_CR. SMBus mode operation is similar to I²C operation with the following exceptions: • Only 7-bit addressing can be used. • The SMBus standard describes a set of timeout values to ensure progress and throughput on the bus. These timeout values must be programmed into TWIHS_SMBTR. • Transmissions can optionally include a CRC byte, called Packet Error Check (PEC). • A set of addresses has been reserved for protocol handling, such as alert response address (ARA) and host header (HH) address. Address matching on these addresses can be enabled by configuring the TWIHS_CR. • Packet Error Checking Each SMBus transfer can optionally end with a CRC byte, called the PEC byte. Writing a one to the PECEN bit in TWIHS_CR enables automatic PEC handling in the current transfer. Transfers with and without PEC can be intermixed in the same system, since some slaves may not support PEC. The PEC LFSR is always updated on every bit transmitted or received, so that PEC handling on combined transfers is correct. In Master Transmitter mode, the master calculates a PEC value and transmits it to the slave after all data bytes have been transmitted. Upon reception of this PEC byte, the slave compares it to the PEC value it has computed itself. If the values match, the data was received correctly, and the slave returns an ACK to the master. If the PEC values differ, data was corrupted, and the slave returns a NACK value. Some slaves may not be able to check the received PEC in time to return a NACK if an error occurred. In this case, the slave should always return an ACK after the PEC byte, and another method must be used to verify that the transmission was received correctly. In Master Receiver mode, the slave calculates a PEC value and transmits it to the master after all data bytes have been transmitted. Upon reception of this PEC byte, the master compares it to the PEC value it has computed itself. If the values match, the data was received correctly. If the PEC values differ, data was corrupted, and the PECERR bit in TWIHS_SR is set. In Master Receiver mode, the PEC byte is always followed by a NACK transmitted by the master, since it is the last byte in the transfer. In combined transfers, the PECRQ bit should only be set in the last of the combined transfers. If the Alternative Command mode is enabled, only the NPEC bit should be set. Consider the following transfer: S, ADR+W, COMMAND_BYTE, ACK, SR, ADR+R, DATA_BYTE, ACK, PEC_BYTE, NACK, P See Section 46.6.3.14 “Read/Write Flowcharts” for detailed flowcharts. • Timeouts The TLOWS and TLOWM fields in TWIHS_SMBTR configure the SMBus timeout values. If a timeout occurs, the master transmits a STOP condition and leaves the bus. The TOUT bit is also set in TWIHS_SR. 46.6.3.11 SMBus Quick Command (Master Mode Only) The TWIHS can perform a quick command: 1. 2. 3. Configure the Master mode (DADR, CKDIV, etc). Write the MREAD bit in the TWIHS_MMR at the value of the one-bit command to be sent. Start the transfer by setting the QUICK bit in the TWIHS_CR. Note: If alternative command is used (ACMEN bit set to ‘1’) DATAL field must be set to 0.  2017 Microchip Technology Inc. DS60001476B-page 1329 SAMA5D2 SERIES Figure 46-13: SMBus Quick Command TWD S DADR R/W A P TXCOMP TXRDY Write QUICK command in TWI_CR 46.6.3.12 Alternative Command Another way to configure the transfer is to enable the Alternative Command mode with the ACMEN bit of the TWIHS Control Register. In this mode, the transfer is configured through the TWIHS Alternative Command Register. It is possible to define a simple read or write transfer or a combined transfer with a repeated start. In order to set a simple transfer, the DATAL field and the DIR field of the TWIHS Alternative Command Register must be filled accordingly and the NDATAL field must be cleared. To begin the transfer, either set the START bit in the TWIHS Control Register in case of a read transfer, or write the TWIHS Transmit Holding Register in case of a write transfer. For a combined transfer linked by a repeated start, the NDATAL field must be filled with the length of the second transfer and NDIR with the corresponding direction. The PEC and NPEC bits are used to set a PEC field. In the case of a single transfer with PEC, the PEC bit must be set. In the case of a combined transfer, the NPEC bit must be set. Note: If Alternative Command mode is used, IADRSZ in TWIHS_MMR must be set to 0. See Section 46.6.3.14 “Read/Write Flowcharts” for detailed flowcharts. 46.6.3.13 Handling Errors in Alternative Command If a NACK is generated by a slave device or SMBus timeout error, the TWIHS stops the frame immediately, although the DMA transfer may still be active. To prevent a new frame from being restarted with the remaining DMA data (transmit), the TWIHS prevents any start of frame until the LOCK flag is cleared in the TWIHS_SR. The LOCK bit in the TWIHS_SR indicates the state of the TWIHS (locked or not locked). When the TWIHS is locked, no transfer begins until the LOCK is cleared by the LOCKCLR bit in the TWIHS_CR and error flags are cleared by reading the TWIHS_SR. In case of error, the TWIHS_THR may have been loaded with a new data. The THRCLR bit in the TWIHS_CR can be used to flush the TWIHS_THR. If the THRCLR bit is set, the TXRDY and TXCOMP flags are set. 46.6.3.14 Read/Write Flowcharts The flowcharts give examples for read and write operations. A polling or interrupt method can be used to check the status bits. The interrupt method requires that TWIHS_IER be configured first. DS60001476B-page 1330  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-14: TWIHS Write Operation with Single Data Byte 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 (DADR) - Transfer direction bit Write ==> bit MREAD = 0 Load Transmit register TWI_THR = Data to send Write STOP Command TWI_CR = STOP Read Status register No TXRDY = 1? Yes Read Status register No TXCOMP = 1? Yes Transfer finished  2017 Microchip Technology Inc. DS60001476B-page 1331 SAMA5D2 SERIES Figure 46-15: TWIHS Write 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 (DADR) - Internal address size (IADRSZ) - Transfer direction bit Write ==> bit MREAD = 0 Set the internal address TWI_IADR = address Load transmit register TWI_THR = Data to send Write STOP command TWI_CR = STOP Read Status register No TXRDY = 1? Yes Read Status register TXCOMP = 1? No Yes Transfer finished DS60001476B-page 1332  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-16: TWIHS Write 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 TWIHS_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Write ==> bit MREAD = 0 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Load Transmit register TWI_THR = Data to send Read Status register TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Write STOP Command TWI_CR = STOP Read Status register No TXCOMP = 1? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1333 SAMA5D2 SERIES Figure 46-17: SMBus Write Operation with Multiple Data Bytes with or without Internal Address and PEC Sending BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: - Master enable TWI_CR = MSEN + SVDIS + SMBEN + PECEN Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Write ==> bit MREAD = 0 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Load Transmit register TWI_THR = Data to send Read Status register TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Write PECRQ Command Write STOP Command TWI_CR = STOP & PECRQ Read Status register No TXCOMP = 1? Yes END DS60001476B-page 1334  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-18: SMBus Write Operation with Multiple Data Bytes with PEC and Alternative Command Mode BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: TWIH_CR = MSEN + SVDIS + ACMEN + SMBEN + PECEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR, PEC Load Transmit register TWI_THR = Data to send Read Status register TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Read Status register No TXCOMP = 1? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1335 SAMA5D2 SERIES Figure 46-19: TWIHS Write Operation with Multiple Data Bytes and Read Operation with Multiple Data Bytes (Sr) 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 = 0 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Load Transmit register TWI_THR = Data to send Read Status register TWI_THR = data to send TXRDY = 1? No Yes Data to send ? Yes No Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - TWI_IADR = address (if Internal address size = 0) - Transfer direction bit Read ==> bit MREAD = 1 Set the next transfer parameters and send the repeated start command Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) 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? No Yes END DS60001476B-page 1336  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-20: TWIHS Write Operation with Multiple Data Bytes + Read Operation and Alternative Command Mode + PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: - Master enable TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, PEC, NDATAL, NPEC - DIR = WRITE - NDIR = READ Load Transmit register TWI_THR = Data to send Read Status register TWI_THR = data to send TXRDY = 1? No Yes Data to send ? Yes No Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) No Last data to read ? Yes Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1337 SAMA5D2 SERIES Figure 46-21: TWIHS Read Operation with Single Data Byte 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 - Transfer direction bit Read ==> bit MREAD = 1 Start the transfer TWI_CR = START | STOP Read status register RXRDY = 1? No Yes Read Receive Holding Register Read Status register No TXCOMP = 1? Yes END DS60001476B-page 1338  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-22: TWIHS 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  2017 Microchip Technology Inc. DS60001476B-page 1339 SAMA5D2 SERIES Figure 46-23: TWIHS 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 TWIHS_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Read ==> bit MREAD = 1 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) 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? No Yes END DS60001476B-page 1340  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-24: TWIHS Read Operation with Multiple Data Bytes with or without Internal Address with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: TWI_CR = MSEN + SVDIS + SMBEN + PECEN Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Read ==> bit MREAD = 1 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) No Last data to read but one ? Yes Check PEC and Stop the transfer TWI_CR = STOP & PECRQ Read Status register No RXRDY = 1? Yes Read Receive Holding register (TWI_RHR) Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1341 SAMA5D2 SERIES Figure 46-25: TWIHS Read Operation with Multiple Data Bytes with Alternative Command Mode with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: TWI_CR = MSEN + SVDIS + SMBEN + ACMEN + PECEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR, PEC Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) No Last data to read ? Yes Read Status register No RXRDY = 1? Yes Read the received PEC: Read Receive Holding register (TWI_RHR) Read status register TXCOMP = 1? No Yes END DS60001476B-page 1342  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-26: TWIHS Read Operation with Multiple Data Bytes + Write Operation with Multiple Data Bytes (Sr) 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 No Internal address size = 0? Set the internal address TWI_IADR = address Yes Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) No Last data to read but one? Yes Set the Master Mode register: - Device slave address - Internal address size (if IADR used) -TWI_IADR = address (if Internal address size = 0) - Transfer direction bit Read ==> bit MREAD = 0 Set the next transfer parameters and send the repeated start command Start the transfer (Sr) TWI_CR = START Read Status register No Read the last byte of the first read transfer RXRDY = 1? Yes Read Receive Holding register (TWI_RHR) Read Status register TWI_THR = data to send No TXRDY = 1? Yes Data to send ? Yes No Stop the transfer TWI_CR = STOP Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1343 SAMA5D2 SERIES Figure 46-27: TWIHS Read Operation with Multiple Data Bytes + Write with Alternative Command Mode with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWI_CWGR (Needed only once) Set the Control register: - Master enable TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, PEC, NDATAL, NPEC - DIR = READ - NDIR = WRITE Start the transfer TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (TWI_RHR) No Last data to read ? Yes Read Status register TWI_THR = data to send No TXRDY = 1? Yes Data to send ? Yes No Read status register TXCOMP = 1? No Yes END DS60001476B-page 1344  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.6.3.15 FIFOs The TWIHS includes two FIFOs which can be enabled/disabled using the FIFOEN/FIFODIS bits in the TWIHS_CR. It is recommended to disable both Master and Slave modes before enabling or disabling the FIFO (MSDIS and SVDIS bit in TWIHS_CR). Writing the FIFOEN bit to ‘1’ will enable a 16-data Transmit FIFO and a 16-data Receive FIFO. Figure 46-28: FIFOs Block Diagram TWI TWIHS_THR write Transmit FIFO Receive FIFO TXDATA3 ....... TXDATA2 Threshold TXDATA0 ....... RXDATA3 TXDATA1 RXDATA2 Threshold ....... RXDATA1 ....... RXDATA0 Tx shifter TWIHS_RHR read Rx shifter TWD  2017 Microchip Technology Inc. DS60001476B-page 1345 SAMA5D2 SERIES • Sending Data with FIFO Enabled With the Transmit FIFO enabled, any write access to the TWIHS Transmit Holding Register (TWIHS_THR) brings the written data to the Transmit FIFO. As a consequence, it is not mandatory any more to monitor the TXRDY flag state to send multiple data without DMAC. Knowing the number of data to send and provided there is enough space in the Transmit FIFO, all the data to send can be written successively in the TWIHS_THR without checking the TXRDY flag between each access. The Transmit FIFO state can be checked reading the TXFL field in the TWIHS FIFO Level Register (TWIHS_FLR). Figure 46-29: Sending Data with FIFO Flowchart BEGIN Set TWI clock CLDIV, CHDIV, CKDIV) in TWIHS_CWGR (Needed only once) Set the Control register: TWIHS_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR Yes Enough space in the FIFO to write all the datas to send ? No Read TWIHS_SR Load Transmit register TWIHS_THR = Data to send No TXRDY = 1? No Yes All the datas have been written in TWIHS_THR ? Load Transmit register TWIHS_THR = Data to send No All the datas have been written in TWIHS_THR ? Read Status register No TXCOMP = 1? Yes END • Receiving Data with FIFO Enabled With Receive FIFO enabled, any read access on TWIHS_RHR will pull out a data from the Receive FIFO. As a consequence, it is not mandatory any more to monitor the RXRDY flag when DMAC is not used and there are multiple data to read. DS60001476B-page 1346  2017 Microchip Technology Inc. SAMA5D2 SERIES When data are present in the Receive FIFO (RXRDY flag set to ‘1’), the exact number of data can be checked with the RXFL field in the TWIHS_FLR and all the data read successively in the TWIHS_RHR without checking the RXRDY flag between each access. Figure 46-30: Receiving Data with FIFO Flowchart BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in TWIHS_CWGR (Needed only once) Set the Control register: - Master enable TWIHS_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL - DIR = READ Start the transfer TWIHS_CR = START Read TWIHS_SR RXRDY = 1? No Yes Read TWIHS_FSR and get the number of data in the Receive FIFO Read TWIHS_RHR All data have been read in TWIHS_RHR ? No Yes Read status register TXCOMP = 1? No Yes END • Clearing/Flushing FIFOs Each FIFO can be cleared/flushed using the TXFCLR and RXFCLR bits in the TWIHS_CR. • TXRDY and RXRDY Behavior If FIFOs are enabled, the behavior of the TXRDY and RXRDY flags will be slightly different. TXRDY will indicate if a data can be written in the Transmit FIFO. By default, the TXRDY flag will then stay at level ‘1’ as long as the Transmit FIFO is not full (TXRDYM = 0x0).  2017 Microchip Technology Inc. DS60001476B-page 1347 SAMA5D2 SERIES Figure 46-31: TXRDY in Single Data Mode and TXRDYM = 0x0 TWD S DADR W A DATA n A DATA n+1 A DATA n+2 A Write TWIHS_THR Read TWIHS_SR SVACC TXRDY TXFFF 1 TXFL 0 1 2 1 FIFO size - 1 FIFO full FIFO size - 1 TXCOMP RXRDY will indicate if an unread data is present in the Receive FIFO. By default, the RXRDY flag will then be at level ‘1’ as soon as one unread data is in the Receive FIFO (RXRDYM = 0x0). Figure 46-32: TWD RXRDY in Single Data Mode and RXRDYM = 0x0 S DADR R A DATA n A DATA n+1 A DATA n+2 A Read TWIHS_RHR Read TWIHS_SR SVACC RXRDY RXFFF RXFEF RXFL 0 1 FIFO full FIFO size - 1 0 TXCOMP TXRDY and RXRDY behavior can be modified using the TXRDYM and RXRDYM fields in the TWIHS FIFO Mode Register (TWIHS_FMR). In Single Data mode, there is no need to modify the TXRDY and RXRDY behavior; however, it may be useful in Multiple Data Mode. • Master Multiple Data Mode When the FIFOs are enabled, they operate in Multiple Data mode. In Multiple Data mode, it is possible to write/read up to four data in one TWIHS_THR/TWIHS_RHR register access. The number of data to write/read is defined by the size of the register access. If the access is a byte size register access, only one data will be written/read; if the access is a halfword-size register access, then two data will be written/read; finally, if the access is a word-size register access, then four data will be written/read. Written/Read data are always right-aligned, as shown in Section 46.7.16 “TWIHS Receive Holding Register (FIFO_ENABLED)” and Section 46.7.19 “TWIHS Transmit Holding Register (FIFO_ENABLED)”. As an example, if the Transmit FIFO is empty and there are six data to send, the options are: • Perform six TWIHS_THR-byte write accesses. • Perform three TWIHS_THR-halfword write accesses. • Perform one TWIHS_THR-word write access and one TWIHS_THR halfword write access. DS60001476B-page 1348  2017 Microchip Technology Inc. SAMA5D2 SERIES Similarly, for a Receive FIFO containing six data, the options are: • Perform six TWIHS_RHR-byte read accesses. • Perform three TWIHS_RHR-halfword read accesses. • Perform one TWIHS_RHR-word read access and one TWIHS_RHR-halfword read access. This mode can minimize the number of accesses by concatenating the data to send/read in one access. • TXRDY and RXRDY Configuration In Multiple Data mode, the TXRDYM and RXRDYM fields in the TWIHS_FMR become useful. As in Multiple Data mode, it is possible to write several data in the same access it might be useful to configure TXRDY flag behavior to indicate if 1, 2 or 4 data can be written in the FIFO depending on the access to perform on TWIHS_THR. If for instance four data are written each time in the TWIHS_THR it might be useful to configure TXRDYM field to 0x2 value so that TXRDY flag will be at ‘1’ only when at least four data can be written in the Transmit FIFO. In the same way if four data are read each time in the TWIHS_RHR it might be useful to configure RXRDYM field to 0x2 value so that RXRDY flag will be at ‘1’ only when at least four unread data are in the Receive FIFO. • DMAC If DMAC transfer is used it is mandatory to configure TXRDYM/RXRDYM to the right value depending on the DMAC channel size (byte, halfword or word). • Transmit FIFO Lock If a frame is terminated early due to a not-acknowledge error (NACK flag), SMBus timeout error (TOUT flag) or master code acknowledge error (MACK flag), a lock is set on the Transmit FIFO preventing any new frame from being sent until it is cleared. This allows clearing the FIFO if needed, reset DMAC channels, etc., without any risk. The LOCK bit in the TWIHS_SR is used to check the state of the Transmit FIFO lock. The Transmit FIFO lock can be cleared setting the TXFLCLR bit to ‘1’ in the TWIHS_CR. • FIFO Pointer Error In some specific cases, it is possible to generate a FIFO pointer error. • Transmit FIFO: If the Transmit FIFO is full and a write access is performed on the TWIHS_THR, it will generate a Transmit FIFO pointer error and set the TXFPTEF flag in TWIHS_FSR. In Multiple Data mode, if the number of data written in the TWIHS_THR (according to the register access size) is bigger than the Transmit FIFO free space, it will generate a Transmit FIFO pointer error and set the TXFPTEF flag in TWIHS_FSR. • Receive FIFO: In Multiple Data mode, if the number of data read in the TWIHS_RHR (according to the register access size) is bigger than the number of unread data in the Receive FIFO, it will generate a Receive FIFO pointer error and set the RXFPTEF flag in TWIHS_FSR. Pointer error should not happen if FIFO state is checked before writing/reading in TWIHS_THR/TWIHS_RHR. FIFO state can be checked either with TXRDY, RXRDY, TXFL or RXFL. When a pointer error occurs, other FIFO flags might not behave as expected; their state should be ignored. If a Transmit or Receive pointer error occurs, a software reset must be performed using the SWRST bit in the TWIHS_CR. Note that issuing a software while transmitting might leave a slave in an unknown state holding the TWD line. In such case, a Bus Clear Command will allow to make the slave release the TWD line (the first frame sent afterwards might not be received properly by the slave). • FIFO Thresholds Each Transmit and Receive FIFO includes a threshold feature used to set a flag and an interrupt when a FIFO threshold is crossed. Thresholds are defined as a number of data in the FIFO, and the FIFO state (TXFL or RXFL) represents the number of data currently in the FIFO. • Transmit FIFO: The Transmit FIFO threshold can be set using the TXFTHRES field in TWIHS_FMR. Each time the Transmit FIFO goes from the ‘above threshold’ to the ‘equal or below threshold’ state, the TXFTHF flag in TWIHS_FSR is set. This enables the application to know that the Transmit FIFO reached the defined threshold and to refill it before it becomes empty. • Receive FIFO: The Receive FIFO threshold can be set using the RXFTHRES field in TWIHS_FMR. Each time the Receive FIFO goes from the ‘below threshold’ to the ‘equal or above threshold’ state, the RXFTHF flag in TWIHS_FSR is set. This enables the application to know that the Receive FIFO reached the defined threshold and to read some data before it becomes full.  2017 Microchip Technology Inc. DS60001476B-page 1349 SAMA5D2 SERIES The TXFTHF and RXFTHF flags can be both configured to generate an interrupt using TWIHS_FIER and TWIHS_FIDR. • FIFO Flags FIFOs come with a set of flags which can be configured each to generate an interrupt through TWIHS_FIER and TWIHS_FIDR. FIFO flags state can be read in TWIHS_FSR. They are cleared on TWIHS_FSR read. 46.6.4 46.6.4.1 Multimaster Mode Definition In Multimaster mode, 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 that has lost arbitration may put its data on the bus by respecting arbitration. Arbitration is illustrated in Figure 46-34. 46.6.4.2 Different Multimaster Modes Two Multimaster modes may be distinguished: 1. 2. The TWIHS is considered as a master only and is never addressed. The TWIHS may be either a master or a slave and may be addressed. Note: Arbitration in supported in both Multimaster modes. • TWIHS as Master Only In this mode, the TWIHS 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 user must reinitiate the data transfer. If starting a transfer (ex.: DADR + START + W + Write in THR) and if the bus is busy, the TWIHS automatically waits for a STOP condition on the bus to initiate the transfer (see Figure 46-33). Note: The state of the bus (busy or free) is not indicated in the user interface. • TWIHS 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 TWIHS may be either a master or a slave, the user must manage the pseudo Multimaster mode described in the steps below: 1. 2. 3. 4. 5. 6. 7. Program the TWIHS in Slave mode (SADR + MSDIS + SVEN) and perform a slave access (if TWIHS is addressed). If the TWIHS has to be set in Master mode, wait until TXCOMP flag is at 1. Program the Master mode (DADR + SVDIS + MSEN) and start the transfer (ex: START + Write in THR). As soon as the Master mode is enabled, the TWIHS scans the bus in order to detect if it is busy or free. When the bus is considered free, the TWIHS initiates the transfer. 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. If the arbitration is lost (ARBLST is set to 1), the user must program the TWIHS in Slave mode in case the master that won the arbitration needs to access the TWIHS. If the TWIHS has to be set in Slave mode, wait until the TXCOMP flag is at 1 and then program the Slave mode. Note: If the arbitration is lost and the TWIHS is addressed, the TWIHS does not acknowledge, even if it is programmed in Slave mode as soon as ARBLST is set to 1. Then the master must repeat SADR. DS60001476B-page 1350  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-33: User Sends Data While the Bus is Busy TWCK START sent by the TWI STOP sent by the master DATA sent by a master TWD DATA sent by the TWI Bus is busy Bus is free Transfer is kept TWI DATA transfer A transfer is programmed (DADR + W + START + Write THR) Figure 46-34: Bus is considered as free Transfer is initiated Arbitration Cases TWCK TWD TWCK Data from a Master S 1 0 0 1 1 Data from TWI S 1 0 TWD S 1 0 0 1 P Arbitration is lost TWI stops sending data Data from the master 1 1 P Arbitration is lost S 1 0 1 S 1 0 0 1 1 S 1 0 0 1 1 The master stops sending data Data from the TWI ARBLST Bus is busy Transfer is kept TWI DATA transfer A transfer is programmed (DADR + W + START + Write THR) Bus is free Transfer is stopped Transfer is programmed again (DADR + W + START + Write THR) Bus is considered as free Transfer is initiated The flowchart shown in Figure 46-35 gives an example of read and write operations in Multimaster mode.  2017 Microchip Technology Inc. DS60001476B-page 1351 SAMA5D2 SERIES Figure 46-35: Multimaster Flowchart START Program the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1? Yes GACC = 1? No Yes No No SVREAD = 1? No EOSACC = 1? TXRDY= 1? Yes Yes No Write in TWI_THR TXCOMP = 1? No RXRDY= 1? Yes No No Yes Read TWI_RHR Need to perform a master access? GENERAL CALL TREATMENT Yes Decoding of the programming sequence No Prog seq OK? Change SADR Program the Master mode DADR + SVDIS + MSEN + CLK + R / W Read Status Register Yes No ARBLST = 1? Yes Yes No MREAD = 1? RXRDY= 0? TXRDY= 0? No No Read TWI_RHR Yes Yes Data to read? Data to send? Yes Write in TWI_THR No No Stop Transfer TWI_CR = STOP Read Status Register Yes DS60001476B-page 1352 TXCOMP = 0? No  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.6.5 Slave Mode 46.6.5.1 Definition 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). 46.6.5.2 Programming Slave Mode The following fields must be programmed before entering Slave mode: 1. 2. 3. 4. TWIHS_SMR.SADR: The slave device address is used in order to be accessed by master devices in Read or Write mode. (Optional) TWIHS_SMR.MASK can be set to mask some SADR address bits and thus allow multiple address matching. TWIHS_CR.MSDIS: Disables the Master mode. TWIHS_CR.SVEN: Enables the Slave mode. As the device receives the clock, values written in TWIHS_CWGR are ignored. 46.6.5.3 Receiving Data After a START or REPEATED START condition is detected, and if the address sent by the master matches the slave address programmed in the SADR (Slave Address) field, the 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, the EOSACC (End Of Slave Access) flag is set. • Read Sequence In the case of a read sequence (SVREAD is high), the TWIHS transfers data written in the TWIHS_THR 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. As soon as data is written in the TWIHS_THR, TXRDY (Transmit Holding Register Ready) flag is reset, and it is set when the internal shifter 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. To clear the TXRDY flag, first set the bit TWIHS_CR.SVDIS, then set the bit TWIHS_CR.SVEN. See Figure 46-36. • 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 TWIHS_RHR. RXRDY is reset when reading the TWIHS_RHR. The TWIHS 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, the TXCOMP flag is set and SVACC is reset. See Figure 46-37. • Clock Stretching Sequence If TWIHS_THR or TWIHS_RHR is not written/read in time, the TWIHS performs a clock stretching. Clock stretching information is given by the SCLWS (Clock Wait State) bit. See Figure 46-39 and Figure 46-40. Note: Clock stretching can be disabled by configuring the SCLWSDIS bit in the TWIHS_SMR. In that case, the UNRE and OVRE flags indicate an underrun (when TWIHS_THR is not filled on time) or an overrun (when TWIHS_RHR is not read on time). • General Call In the case where a GENERAL CALL is performed, the GACC (General Call Access) flag is set. After GACC is set, the user must interpret the meaning of the GENERAL CALL and decode the new address programming sequence. See Figure 46-38. 46.6.5.4 Data Transfer • Read Operation The Read mode is defined as a data requirement from the master.  2017 Microchip Technology Inc. DS60001476B-page 1353 SAMA5D2 SERIES 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, the TWIHS continues sending data loaded in the TWIHS_THR. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 46-36 describes the read operation. Figure 46-36: Read Access Ordered by a Master SADR matches, TWIHS answers with an ACK ACK/NACK from the Master SADR does not match, TWIHS answers with a NACK TWD S ADR R NA DATA NA P/S/Sr SADR R A DATA A A DATA NA S/Sr TXRDY Read RHR Write THR NACK SVACC SVREAD SVREAD has to be taken into account only while SVACC is active EOSACC Note 1: When SVACC is low, the state of SVREAD becomes irrelevant. 2: TXRDY is reset when data has been transmitted from TWIHS_THR to the internal shifter and set when this data has been acknowledged or non acknowledged. • 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, the TWIHS stores the received data in the TWIHS_RHR. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 46-37 describes the write operation. Figure 46-37: Write Access Ordered by a Master SADR does not match, TWIHS answers with a NACK TWD S ADR W NA DATA NA SADR matches, TWIHS answers with an ACK P/S/Sr SADR W A DATA A Read RHR A DATA NA S/Sr RXRDY SVACC SVREAD SVREAD has to be taken into account only while SVACC is active EOSACC Note 1: When SVACC is low, the state of SVREAD becomes irrelevant. 2: RXRDY is set when data has been transmitted from the internal shifter to the TWIHS_RHR and reset when this data is read. • General Call The general call is performed in order to change the address of the slave. DS60001476B-page 1354  2017 Microchip Technology Inc. SAMA5D2 SERIES If a GENERAL CALL is detected, GACC is set. After the detection of general call, decode the commands that follow. In case of a WRITE command, decode the programming sequence and program a new SADR if the programming sequence matches. Figure 46-38 describes the general call access. Figure 46-38: Master Performs a General Call 0000000 + W TXD S GENERAL CALL RESET command = 00000110X WRITE command = 00000100X A Reset or write DADD A DATA1 A DATA2 A A New SADR P New SADR Programming sequence GACC Reset after read SVACC Note: This method enables the user to create a personal programming sequence by choosing the programming bytes and their number. The programming sequence has to be provided to the master. • Clock Stretching In both Read and Write modes, it may occur that TWIHS_THR/TWIHS_RHR buffer is not filled/emptied before the transmission/reception of a new character. In this case, to avoid sending/receiving undesired data, a clock stretching mechanism is implemented. Note: Clock stretching can be disabled by setting the SCLWSDIS bit in the TWIHS_SMR. In that case the UNRE and OVRE flags indicate an underrun (when TWIHS_THR is not filled on time) or an overrun (when TWIHS_RHR is not read on time). Clock Stretching in Read Mode The clock is tied low if the internal shifter is empty and if a STOP or REPEATED START condition was not detected. It is tied low until the internal shifter is loaded. Figure 46-39 describes the clock stretching in Read mode. Figure 46-39: Clock Stretching in Read Mode TWIHS_THR S SADR R DATA1 1 DATA0 A DATA0 A DATA2 A DATA1 XXXXXXX DATA2 NA S 2 TWCK Write THR CLOCK is tied low by the TWIHS as long as THR is empty SCLWS TXRDY SVACC SVREAD As soon as a START is detected TXCOMP TWIHS_THR is transmitted to the internal shifter Ack or Nack from the master 1 The data is memorized in TWIHS_THR until a new value is written 2 The clock is stretched after the ACK, the state of TWD is undefined during clock stretching Note 1: TXRDY is reset when data has been written in the TWIHS_THR to the internal shifter and set when this data has been acknowledged or non acknowledged.  2017 Microchip Technology Inc. DS60001476B-page 1355 SAMA5D2 SERIES 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 stretching mechanism is started. Clock Stretching in Write Mode The clock is tied low if the internal shifter and the TWIHS_RHR is full. If a STOP or REPEATED_START condition was not detected, it is tied low until TWIHS_RHR is read. Figure 46-40 describes the clock stretching in Write mode. Figure 46-40: Clock Stretching in Write Mode TWCK CLOCK is tied low by the TWIHS as long as RHR is full S TWD SADR W A DATA0 A A DATA1 TWIHS_RHR NA DATA2 DATA1 DATA0 is not read in the RHR S ADR DATA2 SCLWS SCL is stretched after the acknowledge of DATA1 RXRDY Rd DATA0 Rd DATA1 Rd DATA2 SVACC SVREAD As soon as a START is detected TXCOMP Note 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 stretching mechanism is started and automatically reset when the mechanism is finished. • 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 46-41 describes the REPEATED START and the reversal from Read mode to Write mode. Figure 46-41: Repeated Start and Reversal from Read Mode to Write Mode TWIHS_THR TWD DATA0 S SADR R A DATA0 DATA1 A DATA1 NA Sr SADR W A DATA2 TWIHS_RHR A DATA3 DATA2 A P DATA3 SVACC SVREAD TXRDY RXRDY EOSACC TXCOMP Note: Cleared after read As soon as a START is detected TXCOMP is only set at the end of the transmission. This is because after the REPEATED START, SADR is detected again. DS60001476B-page 1356  2017 Microchip Technology Inc. SAMA5D2 SERIES Reversal of Write to Read The master initiates the communication by a write command and finishes it by a read command. Figure 46-42 describes the REPEATED START and the reversal from Write mode to Read mode. Figure 46-42: Repeated Start and Reversal from Write Mode to Read Mode DATA2 TWIHS_THR TWD S SADR W A DATA0 A TWIHS_RHR DATA1 DATA0 A Sr SADR R A DATA3 DATA2 A DATA3 NA P DATA1 SVACC SVREAD TXRDY RXRDY Read TWIHS_RHR EOSACC TXCOMP Cleared after read As soon as a START is detected Note 1: In this case, if TWIHS_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. This is because after the REPEATED START, SADR is detected again.  2017 Microchip Technology Inc. DS60001476B-page 1357 SAMA5D2 SERIES 46.6.5.5 Using the DMA Controller (DMAC) in Slave Mode The use of the DMAC significantly reduces the CPU load. • Data Transmit with the DMA in Slave Mode The following procedure shows an example to transmit data with DMA. 1. Initialize the transmit DMA (memory pointers, transfer size, etc). 2. Configure the Slave mode. 3. Enable the DMA. 4. Wait for the DMA status flag indicating that the buffer transfer is complete. 5. Disable the DMA. 6. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. • Data Receive with the DMA in Slave Mode The following procedure shows an example to transmit data with DMA where the number of characters to receive is known. 1. 2. 3. 4. 5. 6. Initialize the DMA (channels, memory pointers, size, etc.). Configure the Slave mode. Enable the DMA. Wait for the DMA status flag indicating that the buffer transfer is complete. Disable the DMA. (Only if peripheral clock must be disabled) Wait for the TXCOMP flag to be raised in TWIHS_SR. 46.6.5.6 SMBus Mode SMBus mode is enabled when a one is written to the SMEN bit in the TWIHS_CR. SMBus mode operation is similar to I²C operation with the following exceptions: • Only 7-bit addressing can be used. • The SMBus standard describes a set of timeout values to ensure progress and throughput on the bus. These timeout values must be programmed into the TWIHS_SMBTR. • Transmissions can optionally include a CRC byte, called Packet Error Check (PEC). • A set of addresses have been reserved for protocol handling, such as alert response address (ARA) and host header (HH) address. Address matching on these addresses can be enabled by configuring the TWIHS_CR. • Packet Error Checking Each SMBus transfer can optionally end with a CRC byte, called the PEC byte. Writing a one to the PECEN bit in TWIHS_CR will send/ check the PEC field in the current transfer. The PEC generator is always updated on every bit transmitted or received, so that PEC handling on the following linked transfers is correct. In Slave Receiver mode, the master calculates a PEC value and transmits it to the slave after all data bytes have been transmitted. Upon reception of this PEC byte, the slave compares it to the PEC value it has computed itself. If the values match, the data was received correctly, and the slave returns an ACK to the master. If the PEC values differ, data was corrupted, and the slave returns a NACK value. The PECERR bit in TWIHS_SR is set automatically if a PEC error occurred. In Slave Transmitter mode, the slave calculates a PEC value and transmits it to the master after all data bytes have been transmitted. Upon reception of this PEC byte, the master compares it to the PEC value it has computed itself. If the values match, the data was received correctly. If the PEC values differ, data was corrupted, and the master must take appropriate action. See Section 46.6.5.10 “Slave Read Write Flowcharts” for detailed flowcharts. • Timeouts The TWIHS SMBus Timing Register (TWIHS_SMBTR) configures the SMBus timeout values. If a timeout occurs, the slave leaves the bus. The TOUT bit is also set in TWIHS_SR. 46.6.5.7 High-Speed Slave Mode High-speed mode is enabled when a one is written to the HSEN bit in the TWIHS_CR. Furthermore, the analog pad filter must be enabled, a one must be written to the PADFEN bit in the TWIHS_FILTR and the FILT bit must be cleared. TWIHS High-speed mode operation is similar to TWIHS operation with the following exceptions: 1. 2. A master code is received first at normal speed before entering High-speed mode period. When TWIHS High-speed mode is active, clock stretching is only allowed after acknowledge (ACK), not-acknowledge (NACK), START (S) or REPEATED START (Sr) (as consequence OVF may happen). TWIHS High-speed mode allows transfers of up to 3.4 Mbit/s. DS60001476B-page 1358  2017 Microchip Technology Inc. SAMA5D2 SERIES The TWIHS slave in High-speed mode requires that the peripheral clock runs at a minimum of 14 MHz if slave clock stretching is enabled (SCLWSDIS bit at ‘0’). If slave clock stretching is disabled (SCLWSDIS bit at ‘1’), the peripheral clock must run at a minimum of 11 MHz (assuming the system has no latency). Note: When slave clock stretching is disabled, the TWIHS_RHR must always be read before receiving the next data (MASTER write frame). It is strongly recommended to use either the polling method on the RXRDY flag in TWIHS_SR, or the DMA. If the receive is managed by an interrupt, the TWIHS interrupt priority must be set to the right level and its latency minimized to avoid receive overrun. Note: When slave clock stretching is disabled, the TWIHS_THR must be filled with the first data to send before the beginning of the frame (MASTER read frame). It is strongly recommended to use either the polling method on the TXRDY flag in TWIHS_SR, or the DMA. If the transmit is managed by an interrupt, the TWIHS interrupt priority must be set to the right level and its latency minimized to avoid transmit underrun. • Read/Write Operation A TWIHS high-speed frame always begins with the following sequence: 1. 2. 3. START condition (S) Master Code (0000 1XXX) Not-acknowledge (NACK) When the TWIHS is programmed in Slave mode and TWIHS High-speed mode is activated, master code matching is activated and internal timings are set to match the TWIHS High-speed mode requirements. Figure 46-43: High-Speed Mode Read/Write F/S Mode S MASTER CODE HS Mode NA Sr SADR R/W A F/S Mode S MASTER CODE F/S Mode DATA A/NA P F/S Mode HS Mode NA Sr SADR R/W A DATA A/NA Sr SADR P • Usage TWIHS High-speed mode usage is the same as the standard TWIHS (See Section 46.6.3.14 “Read/Write Flowcharts”). 46.6.5.8 Alternative Command In Slave mode, Alternative Command mode is useful when SMBus mode is enabled to send or check the PEC byte. Alternative Command mode is enabled by setting the ACMEN bit of the TWIHS Control Register and the transfer is configured in TWIHS_ACR. For a combined transfer with PEC, only the NPEC bit in TWIHS_ACR must be set as the PEC byte is sent once at the end of the frame. See Section 46.6.5.10 “Slave Read Write Flowcharts” for detailed flowcharts. 46.6.5.9 Asynchronous Partial Wakeup (SleepWalking) The TWIHS includes an asynchronous start condition detector. It is capable of waking the device up from a Sleep mode upon an address match (and optionally an additional data match), including Sleep modes where the TWIHS peripheral clock is stopped. After detecting the START condition on the bus, the TWIHS stretches TWCK until the TWIHS peripheral clock has started. The time required for starting the TWIHS depends on which Sleep mode the device is in. After the TWIHS peripheral clock has started, the TWIHS releases its TWCK stretching and receives one byte of data (slave address) on the bus. At this time, only a limited part of the device, including the TWIHS module, receives a clock, thus saving power. If the address phase causes a TWIHS address match (and, optionally, if the first data byte causes data match as well), the entire device is woken up and normal TWIHS address matching actions are performed. Normal TWIHS transfer then follows. If the TWIHS is not addressed (or if the optional data match fails), the TWIHS peripheral clock is automatically stopped and the device returns to its original Sleep mode.  2017 Microchip Technology Inc. DS60001476B-page 1359 SAMA5D2 SERIES The TWIHS has the capability to match on more than one address. The SADR1EN, SADR2EN and SADR3EN bits in TWIHS_SMR enable address matching on additional addresses which can be configured through SADR1, SADR2 and SADR3 fields in the TWIHS_SWMR. The SleepWalking matching process can be extended to the first received data byte if DATAMEN bit in TWIHS_SMR is set and, in this case, a complete matching includes address matching and first received data matching. The field DATAM in TWIHS_SWMR configures the data to match on the first received byte. When the system is in Active mode and the TWIHS enters Asynchronous Partial Wakeup mode, the flag SVACC must be programmed as the unique source of the TWIHS interrupt and the data match comparison must be disabled. When the system exits Wait mode as the result of a matching condition, the SVACC flag is used to determine if the TWIHS is the source of exit. Figure 46-44: Address Match Only (Data Matching Disabled) Address Matching Area Clock Stretching SADR S PClk R/W A DATA A/NA DATA A/NA P PClk Startup PClk_request SystemWakeUp_req Figure 46-45: No Address Match (Data Matching Disabled) Address Matching Area Clock Stretching S PClk SADR R/W NA P PClk Startup PClk_request SystemWakeUp_req DS60001476B-page 1360  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-46: Address Match and Data Match (Data Matching Enabled) Address Matching + Data Matching Area Clock Stretching S PClk SADR W A DATA A DATA A/NA P PClk Startup PClk_request SystemWakeUp_req Figure 46-47: Address Match and No Data Match (Data Matching Enabled) Address Matching + Data Matching Area Clock Stretching S PClk SADR W A DATA NA DATA NA P PClk Startup PClk_request SystemWakeUp_req  2017 Microchip Technology Inc. DS60001476B-page 1361 SAMA5D2 SERIES 46.6.5.10 Slave Read Write Flowcharts The flowchart shown in Figure 46-48 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 TWIHS_IER be configured first. Figure 46-48: Read Write Flowchart in Slave Mode Set the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 1 ? TXRDY= 1 ? No No Write in TWI_THR No TXCOMP = 1 ? RXRDY= 1 ? No END Read TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR DS60001476B-page 1362  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-49: Read Write Flowchart in Slave Mode with SMBus PEC Set the SLAVE mode: SADR + MSDIS + SVEN + SMBEN + PECEN Read Status Register SVACC = 1 ? GACC = 1 ? No SVREAD = 1 ? No No No EOSACC = 1 ? TXRDY= 1 ? No RXRDY= 1 ? No Last data sent ? TXCOMP = 1 ? No Last data to read ? Write in TWI_THR END No Write in PECRQ Write in PECRQ Read TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR  2017 Microchip Technology Inc. DS60001476B-page 1363 SAMA5D2 SERIES Figure 46-50: Read Write Flowchart in Slave Mode with SMBus PEC and Alternative Command Mode Set the SLAVE mode: SADR + MSDIS + SVEN + SMBEN + PECEN + ACMEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 1 ? TXRDY= 1 ? No No Write in TWI_THR No TXCOMP = 1 ? RXRDY= 1 ? No END Read TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR DS60001476B-page 1364  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.6.5.11 FIFOs The TWIHS includes two FIFOs which can be enabled/disabled using the FIFOEN/FIFODIS bits in the TWIHS_CR. It is recommended to disable both Master and Slave modes before enabling or disabling the FIFO (MSDIS and SVDIS bit in TWIHS_CR). Writing the FIFOEN bit to ‘1’ will enable a 16-data Transmit FIFO and a 16-data Receive FIFO. Figure 46-51: FIFOs Block Diagram TWI TWIHS_THR write Transmit FIFO Receive FIFO TXDATA3 ....... TXDATA2 Threshold TXDATA0 ....... RXDATA3 TXDATA1 RXDATA2 Threshold ....... RXDATA1 ....... RXDATA0 Tx shifter TWIHS_RHR read Rx shifter TWD • Sending/Receiving Data with FIFO Enabled With the Transmit FIFO enabled, any write access to the TWIHS_THR will bring the written data to the Transmit FIFO. As a consequence, it is not mandatory any more to monitor the TXRDY flag state to send multiple data without DMAC. Knowing the number of data to send and provided there is enough space in the Transmit FIFO, all the data to send can be written successively in the TWIHS_THR without checking the TXRDY flag between each access. The Transmit FIFO state can be checked reading the TXFL field in the TWIHS_FLR. With Receive FIFO enabled, any read access on TWIHS_RHR will pull out a data from the Receive FIFO. As a consequence, it is not mandatory any more to monitor the RXRDY flag when DMAC is not used and there are multiple data to read. When data are present in the Receive FIFO (RXRDY flag set to ‘1’), the exact number of data can be checked with the RXFL field in the TWIHS_FLR and all the data read successively in the TWIHS_RHR without checking the RXRDY flag between each access.  2017 Microchip Technology Inc. DS60001476B-page 1365 SAMA5D2 SERIES Figure 46-52: Sending/Receiving Data with FIFO Flowchart START Set SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 0 ? No Enough space in the FIFO to write all the data to send ? Load Transmit register TWI_THR = Data to send No TXCOMP = 1 ? RXRDY= 0 ? TXRDY= 1 ? No Write in TWI_THR No END No All data have been written in TWI_THR ? No Read TWI_FSR and get the number of data in the Receive FIFO Read TWI_RHR All data have been read in TWI_RHR ? No GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR • Clearing/Flushing FIFOs Each FIFO can be cleared/flushed using the TXFCLR and RXFCLR bits in the TWIHS_CR. • TXRDY and RXRDY Behavior If FIFOs are enabled, the behavior of the TXRDY and RXRDY flags will be slightly different. TXRDY will indicate if a data can be written in the Transmit FIFO. By default, the TXRDY flag will then stay at level ‘1’ as long as the Transmit FIFO is not full (TXRDYM = 0x0). DS60001476B-page 1366  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 46-53: TXRDY in Single Data Mode and TXRDYM = 0x0 TWD S DADR W A DATA n A DATA n+1 A DATA n+2 A Write TWIHS_THR Read TWIHS_SR SVACC TXRDY TXFFF 1 TXFL 0 1 2 1 FIFO size - 1 FIFO full FIFO size - 1 TXCOMP RXRDY will indicate if an unread data is present in the Receive FIFO. By default, the RXRDY flag will then be at level ‘1’ as soon as one unread data is in the Receive FIFO (RXRDYM = 0x0). Figure 46-54: TWD RXRDY in Single Data Mode and RXRDYM = 0x0 S DADR R A DATA n A DATA n+1 A DATA n+2 A Read TWIHS_RHR Read TWIHS_SR SVACC RXRDY RXFFF RXFEF RXFL 0 1 FIFO full FIFO size - 1 0 TXCOMP TXRDY and RXRDY behavior can be modified using the TXRDYM and RXRDYM fields in the TWIHS_FMR. In Single Data mode, there is no need to modify the TXRDY and RXRDY behavior; however, it may be useful in Multiple Data mode. • Slave Multiple Data Mode When the FIFOs are enabled, they operate in Multiple Data mode. In Multiple Data mode, it is possible to write/read up to four data in one TWIHS_THR/TWIHS_RHR register access. The number of data to write/read is defined by the size of the register access. If the access is a byte-size register access, only one data will be written/read; if the access is a halfword-size register access, then two data will be written/read and finally, if the access is a wordsize register access, then four data will be written/read. Written/Read data are always right-aligned, as shown in Section 46.7.16 “TWIHS Receive Holding Register (FIFO_ENABLED)” and Section 46.7.19 “TWIHS Transmit Holding Register (FIFO_ENABLED)”. As an example, if the Transmit FIFO is empty and there are six data to send, the options are: • Perform six TWIHS_THR-byte write accesses. • Perform three TWIHS_THR-halfword write accesses.  2017 Microchip Technology Inc. DS60001476B-page 1367 SAMA5D2 SERIES • Perform one TWIHS_THR-word write access and one TWIHS_THR-halfword write access. Similarly, for a Receive FIFO containing six data, the options are: • Perform six TWIHS_RHR-byte read accesses. • Perform three TWIHS_RHR-halfword read accesses. • Perform one TWIHS_RHR-word read access and one TWIHS_RHR-halfword read access. Multiple Data mode allows to minimize the number of accesses by concatenating the data to send/read in one access. • TXRDY and RXRDY configuration In Multiple Data mode, the TXRDYM and RXRDYM fields in TWIHS_FMR become useful. As in Multiple Data mode, it is possible to write several data in the same access; it might be useful to configure the TXRDY flag behavior to indicate if 1, 2 or 4 data can be written in the FIFO depending on the access to perform on TWIHS_THR. If for instance four data are written each time in the TWIHS_THR it might be useful to configure the TXRDYM field to 0x2 value so that the TXRDY flag will be at ‘1’ only when at least four data can be written in the Transmit FIFO. In the same way, if four data are read each time in the TWIHS_RHR, it might be useful to configure the RXRDYM field to 0x2 value so that the RXRDY flag will be at ‘1’ only when at least four unread data are in the Receive FIFO. • DMAC If DMAC transfer is used, it is mandatory to configure TXRDYM/RXRDYM to the right value depending on the DMAC channel size (byte, halfword or word). • Transmit FIFO Lock If a frame is terminated early due to a not-acknowledge error (NACK flag), SMBus timeout error (TOUT flag) or master code acknowledge error (MACK flag), a lock is set on the Transmit FIFO preventing any new frame from being sent until it is cleared. This allows clearing the FIFO if needed, reset DMAC channels, etc., without any risk. The LOCK bit in the TWIHS_SR is used to check the state of the Transmit FIFO lock. The Transmit FIFO lock can be cleared by setting the TXFLCLR bit to ‘1’ in the TWIHS_CR. • FIFO Pointer Error In some specific cases, it is possible to generate a FIFO pointer error. • Transmit FIFO: If the Transmit FIFO is full and a write access is performed on the TWIHS_THR it will generate a Transmit FIFO pointer error and set the TXFPTEF flag in TWIHS_FSR. In Multiple Data mode, if the number of data written in the TWIHS_THR (according to the register access size) is bigger than the Transmit FIFO free space, it generates a Transmit FIFO pointer error and sets the TXFPTEF flag in TWIHS_FSR. • Receive FIFO: In Multiple Data mode, if the number of data read in the TWIHS_RHR (according to the register access size) is bigger than the number of unread data in the Receive FIFO, it generates a Receive FIFO pointer error and sets the RXFPTEF flag in TWIHS_FSR. Pointer error should not happen if the FIFO state is checked before writing/reading in the TWIHS_THR/TWIHS_RHR registers. The FIFO state can be checked either with TXRDY, RXRDY, TXFL or RXFL. When a pointer error occurs, other FIFO flags might not behave as expected; their state should be ignored. If a Transmit or Receive pointer error occurs, a software reset must be performed using the SWRST bit in the TWIHS_CR. Note that issuing a software while transmitting might leave a slave in an unknown state holding the TWD line. In such case, a Bus Clear Command will allow to make the slave release the TWD line (the first frame sent afterwards might not be received properly by the slave). • FIFO Thresholds Each Transmit and Receive FIFO includes a threshold feature used to set a flag and an interrupt when a FIFO threshold is crossed. Thresholds are defined as a number of data in the FIFO, and the FIFO state (TXFL or RXFL) represents the number of data currently in the FIFO. • Transmit FIFO: The Transmit FIFO threshold can be set using the TXFTHRES field in TWIHS_FMR. Each time the Transmit FIFO goes from the ‘above threshold’ to the ‘equal or below threshold’ state, the TXFTHF flag in TWIHS_FSR is set. This enables the application to know that the Transmit FIFO reached the defined threshold and to refill it before it becomes empty. • Receive FIFO: DS60001476B-page 1368  2017 Microchip Technology Inc. SAMA5D2 SERIES The Receive FIFO threshold can be set using the RXFTHRES field in TWIHS_FMR. Each time the Receive FIFO goes from the ‘below threshold’ to the ‘equal or above threshold’ state, the RXFTHF flag in TWIHS_FSR is set. This enables the application to know that the Receive FIFO reached the defined threshold and to read some data before it becomes full. The TXFTHF and RXFTHF flags can be both configured to generate an interrupt using TWIHS_FIER and TWIHS_FIDR. • FIFO Flags FIFOs come with a set of flags which can be configured each to generate an interrupt through TWIHS_FIER and TWIHS_FIDR. FIFO flags state can be read in TWIHS_FSR. They are cleared on TWIHS_FSR read. 46.6.6 TWIHS Comparison Function on Received Character The comparison function differs if asynchronous partial wakeup (SleepWalking) is enabled or not. If asynchronous partial wakeup is disabled (see the section “Power Management Controller (PMC)”), the TWIHS can extend the address matching on up to three slave addresses. The SADR1EN, SADR2EN and SADR3EN bits in TWIHS_SMR enable address matching on additional addresses which can be configured through SADR1, SADR2 and SADR3 fields in the TWIHS_SWMR. The DATAMEN bit in the TWIHS_SMR has no effect. The SVACC bit is set when there is a comparison match with the received slave address.  2017 Microchip Technology Inc. DS60001476B-page 1369 SAMA5D2 SERIES 46.6.7 Register Write Protection To prevent any single software error from corrupting TWIHS behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the TWIHS Write Protection Mode Register (TWIHS_WPMR). If a write access to a write-protected register is detected, the WPVS bit in the TWIHS Write Protection Status Register (TWIHS_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading TWIHS_WPSR. The following registers can be write-protected: • • • • TWIHS Slave Mode Register TWIHS Clock Waveform Generator Register TWIHS SMBus Timing Register TWIHS SleepWalking Matching Register DS60001476B-page 1370  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7 Two-wire Interface High Speed (TWIHS) User Interface Table 46-7: Register Mapping Offset Register Name Access Reset 0x00 Control Register TWIHS_CR Write-only – 0x04 Master Mode Register TWIHS_MMR Read/Write 0x00000000 0x08 Slave Mode Register TWIHS_SMR Read/Write 0x00000000 0x0C Internal Address Register TWIHS_IADR Read/Write 0x00000000 0x10 Clock Waveform Generator Register TWIHS_CWGR Read/Write 0x00000000 0x14–0x1C Reserved – – – 0x20 Status Register TWIHS_SR Read-only 0x0300F009 0x24 Interrupt Enable Register TWIHS_IER Write-only – 0x28 Interrupt Disable Register TWIHS_IDR Write-only – 0x2C Interrupt Mask Register TWIHS_IMR Read-only 0x00000000 0x30 Receive Holding Register TWIHS_RHR Read-only 0x00000000 0x34 Transmit Holding Register TWIHS_THR Write-only 0x00000000 0x38 SMBus Timing Register TWIHS_SMBTR Read/Write 0x00000000 0x3C Reserved – – – 0x40 Alternative Command Register TWIHS_ACR Read/Write – 0x44 Filter Register TWIHS_FILTR Read/Write 0x00000000 0x48 Reserved – – – 0x4C SleepWalking Matching Register TWIHS_SWMR Read/Write 0x00000000 0x50 FIFO Mode Register TWIHS_FMR Read/Write 0x00000000 0x54 FIFO Level Register TWIHS_FLR Read-only 0x00000000 0x58–0x5C Reserved – – – 0x60 FIFO Status Register TWIHS_FSR Read-only 0x00000000 0x64 FIFO Interrupt Enable Register TWIHS_FIER Write-only – 0x68 FIFO Interrupt Disable Register TWIHS_FIDR Write-only – 0x6C FIFO Interrupt Mask Register TWIHS_FIMR Read-only 0x00000000 0x70–0xCC Reserved – – – 0xD0 Reserved – – – 0xD4–0xE0 Reserved – – – 0xE4 Write Protection Mode Register TWIHS_WPMR Read/Write 0x00000000 Write Protection Status Register TWIHS_WPSR Read-only 0x00000000 Reserved – – – Reserved – – – 0xE8 0xEC–0xFC (1) 0x100–0x128 Note 1: All unlisted offset values are considered as “reserved”.  2017 Microchip Technology Inc. DS60001476B-page 1371 SAMA5D2 SERIES 46.7.1 TWIHS Control Register Name: TWIHS_CR Address: 0xF8028000 (0), 0xFC028000 (1) Access: Write-only 31 – 30 – 29 FIFODIS 28 FIFOEN 27 – 26 LOCKCLR 25 – 24 THRCLR 23 – 22 – 21 – 20 – 19 – 18 – 17 ACMDIS 16 ACMEN 15 CLEAR 14 PECRQ 13 PECDIS 12 PECEN 11 SMBDIS 10 SMBEN 9 HSDIS 8 HSEN 7 SWRST 6 QUICK 5 SVDIS 4 SVEN 3 MSDIS 2 MSEN 1 STOP 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 TWIHS Master Mode Register (TWIHS_MMR). This action is necessary when the TWIHS peripheral needs 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 (TWIHS_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, both START and STOP must 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 master data write operation, a STOP condition will be sent after the transmission of the current data is finished. MSEN: TWIHS Master Mode Enabled 0: No effect. 1: Enables the Master mode (MSDIS must be written to 0). Note: Switching from Slave to Master mode is only permitted when TXCOMP = 1. MSDIS: TWIHS 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: TWIHS Slave Mode Enabled 0: No effect. 1: Enables the Slave mode (SVDIS must be written to 0). Note: Switching from Master to Slave mode is only permitted when TXCOMP = 1. SVDIS: TWIHS Slave Mode Disabled 0: No effect. DS60001476B-page 1372  2017 Microchip Technology Inc. SAMA5D2 SERIES 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. QUICK: SMBus Quick Command 0: No effect. 1: If Master mode is enabled, a SMBus Quick Command is sent. SWRST: Software Reset 0: No effect. 1: Equivalent to a system reset. HSEN: TWIHS High-Speed Mode Enabled 0: No effect. 1: High-speed mode enabled. HSDIS: TWIHS High-Speed Mode Disabled 0: No effect. 1: High-speed mode disabled. SMBEN: SMBus Mode Enabled 0: No effect. 1: If SMBDIS = 0, SMBus mode enabled. SMBDIS: SMBus Mode Disabled 0: No effect. 1: SMBus mode disabled. PECEN: Packet Error Checking Enable 0: No effect. 1: SMBus PEC (CRC) generation and check enabled. PECDIS: Packet Error Checking Disable 0: No effect. 1: SMBus PEC (CRC) generation and check disabled. PECRQ: PEC Request 0: No effect. 1: A PEC check or transmission is requested.  2017 Microchip Technology Inc. DS60001476B-page 1373 SAMA5D2 SERIES CLEAR: Bus CLEAR Command 0: No effect. 1: If Master mode is enabled, sends a bus clear command. ACMEN: Alternative Command Mode Enable 0: No effect. 1: Alternative Command mode enabled. ACMDIS: Alternative Command Mode Disable 0: No effect. 1: Alternative Command mode disabled. THRCLR: Transmit Holding Register Clear 0: No effect. 1: Clears the Transmit Holding Register and set TXRDY, TXCOMP flags. LOCKCLR: Lock Clear 0: No effect. 1: Clears the TWIHS FSM lock. FIFOEN: FIFO Enable 0: No effect. 1: Enables the Transmit and Receive FIFOs FIFODIS: FIFO Disable 0: No effect. 1: Disables the Transmit and Receive FIFOs DS60001476B-page 1374  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.2 TWIHS Control Register (FIFO_ENABLED) Name: TWIHS_CR (FIFO_ENABLED) Address: 0xF8028000 (0), 0xFC028000 (1) Access: Write-only 31 – 30 – 29 FIFODIS 28 FIFOEN 27 – 26 TXFLCLR 25 RXFCLR 24 TXFCLR 23 – 22 – 21 – 20 – 19 – 18 – 17 ACMDIS 16 ACMEN 15 CLEAR 14 PECRQ 13 PECDIS 12 PECEN 11 SMBDIS 10 SMBEN 9 HSDIS 8 HSEN 7 SWRST 6 QUICK 5 SVDIS 4 SVEN 3 MSDIS 2 MSEN 1 STOP 0 START This configuration is relevant only if TWIHS_CR.FIFOEN = ‘1’. 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 TWIHS Master Mode Register (TWIHS_MMR). This action is necessary when the TWIHS peripheral needs 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 (TWIHS_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, both START and STOP must 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 master data write operation, a STOP condition will be sent after the transmission of the current data is finished. MSEN: TWIHS Master Mode Enabled 0: No effect. 1: Enables the Master mode (MSDIS must be written to 0). Note: Switching from Slave to Master mode is only permitted when TXCOMP = 1. MSDIS: TWIHS 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: TWIHS Slave Mode Enabled 0: No effect. 1: Enables the Slave mode (SVDIS must be written to 0). Note: Switching from Master to Slave mode is only permitted when TXCOMP = 1. SVDIS: TWIHS Slave Mode Disabled 0: No effect.  2017 Microchip Technology Inc. DS60001476B-page 1375 SAMA5D2 SERIES 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. QUICK: SMBus Quick Command 0: No effect. 1: If Master mode is enabled, a SMBus Quick Command is sent. SWRST: Software Reset 0: No effect. 1: Equivalent to a system reset. HSEN: TWIHS High-Speed Mode Enabled 0: No effect. 1: High-speed mode enabled. HSDIS: TWIHS High-Speed Mode Disabled 0: No effect. 1: High-speed mode disabled. SMBEN: SMBus Mode Enabled 0: No effect. 1: If SMBDIS = 0, SMBus mode enabled. SMBDIS: SMBus Mode Disabled 0: No effect. 1: SMBus mode disabled. PECEN: Packet Error Checking Enable 0: No effect. 1: SMBus PEC (CRC) generation and check enabled. PECDIS: Packet Error Checking Disable 0: No effect. 1: SMBus PEC (CRC) generation and check disabled. PECRQ: PEC Request 0: No effect. 1: A PEC check or transmission is requested. CLEAR: Bus CLEAR Command 0: No effect. 1: If Master mode is enabled, sends a bus clear command. ACMEN: Alternative Command Mode Enable 0: No effect. 1: Alternative Command mode enabled. ACMDIS: Alternative Command Mode Disable DS60001476B-page 1376  2017 Microchip Technology Inc. SAMA5D2 SERIES 0: No effect. 1: Alternative Command mode disabled. TXFCLR: Transmit FIFO Clear 0: No effect. 1: Clears the Transmit FIFO, Transmit FIFO will become empty. RXFCLR: Receive FIFO Clear 0: No effect. 1: Clears the Receive FIFO, Receive FIFO will become empty. TXFLCLR: Transmit FIFO Lock CLEAR 0: No effect. 1: Clears the Transmit FIFO Lock. FIFOEN: FIFO Enable 0: No effect. 1: Enables the Transmit and Receive FIFOs FIFODIS: FIFO Disable 0: No effect. 1: Disables the Transmit and Receive FIFOs  2017 Microchip Technology Inc. DS60001476B-page 1377 SAMA5D2 SERIES 46.7.3 TWIHS Master Mode Register Name: TWIHS_MMR Address: 0xF8028004 (0), 0xFC028004 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 21 20 19 DADR 18 17 16 15 – 14 – 13 – 12 MREAD 11 – 10 – 9 8 7 – 6 – 5 – 4 – 3 – 2 – 1 – IADRSZ 0 – IADRSZ: Internal Device Address Size Value Name Description 0 NONE No internal device address 1 1_BYTE One-byte internal device address 2 2_BYTE Two-byte internal device address 3 3_BYTE 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. These bits are only used in Master mode. DS60001476B-page 1378  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.4 TWIHS Slave Mode Register Name: TWIHS_SMR Address: 0xF8028008 (0), 0xFC028008 (1) Access: Read/Write 31 DATAMEN 30 SADR3EN 29 SADR2EN 28 SADR1EN 27 – 26 – 25 – 24 – 23 – 22 21 20 19 SADR 18 17 16 15 – 14 13 12 11 MASK 10 9 8 7 – 6 SCLWSDIS 5 – 4 – 3 SMHH 2 SMDA 1 – 0 NACKEN This register can only be written if the WPEN bit is cleared in the TWIHS Write Protection Mode Register. NACKEN: Slave Receiver Data Phase NACK enable 0: Normal value to be returned in the ACK cycle of the data phase in Slave Receiver mode. 1: NACK value to be returned in the ACK cycle of the data phase in Slave Receiver mode. SMDA: SMBus Default Address 0: Acknowledge of the SMBus default address disabled. 1: Acknowledge of the SMBus default address enabled. SMHH: SMBus Host Header 0: Acknowledge of the SMBus host header disabled. 1: Acknowledge of the SMBus host header enabled. SCLWSDIS: Clock Wait State Disable 0: No effect. 1: Clock stretching disabled in Slave mode, OVRE and UNRE indicate an overrun/underrun. MASK: Slave Address Mask A mask can be applied on the slave device address in Slave mode in order to allow multiple address answer. For each bit of the MASK field set to 1, the corresponding SADR bit is masked. If the MASK field value is 0, no mask is applied to the SADR field. 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. SADR1EN: Slave Address 1 Enable 0: Slave address 1 matching is disabled. 1: Slave address 1 matching is enabled. SADR2EN: Slave Address 2 Enable 0: Slave address 2 matching is disabled. 1: Slave address 2 matching is enabled. SADR3EN: Slave Address 3 Enable  2017 Microchip Technology Inc. DS60001476B-page 1379 SAMA5D2 SERIES 0: Slave address 3 matching is disabled. 1: Slave address 3 matching is enabled. DATAMEN: Data Matching Enable 0: Data matching on first received data is disabled. 1: Data matching on first received data is enabled. DS60001476B-page 1380  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.5 TWIHS Internal Address Register Name: TWIHS_IADR Address: 0xF802800C (0), 0xFC02800C (1) Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 IADR 15 14 13 12 IADR 7 6 5 4 IADR IADR: Internal Address 0, 1, 2 or 3 bytes depending on IADRSZ.  2017 Microchip Technology Inc. DS60001476B-page 1381 SAMA5D2 SERIES 46.7.6 TWIHS Clock Waveform Generator Register Name: TWIHS_CWGR Address: 0xF8028010 (0), 0xFC028010 (1) Access: Read/Write 31 – 30 – 29 – 28 27 26 HOLD 25 24 23 – 22 – 21 – 20 CKSRC 19 – 18 17 CKDIV 16 15 14 13 12 11 10 9 8 3 2 1 0 CHDIV 7 6 5 4 CLDIV This register can only be written if the WPEN bit is cleared in the TWIHS Write Protection Mode Register. TWIHS_CWGR is used in Master mode only. CLDIV: Clock Low Divider The SCL low period is defined as follows: If CKSRC = 0 tlow = ((CLDIV × 2CKDIV) + 3) × tperipheral clock If CKSRC = 1 tlow = (CLDIV × 2CKDIV) × texternal clock CHDIV: Clock High Divider The SCL high period is defined as follows: If CKSRC = 0 thigh = ((CHDIV × 2CKDIV) + 3) × tperipheral clock If CKSRC = 1 thigh = (CHDIV × 2CKDIV) × texternal clock CKDIV: Clock Divider The CKDIV is used to increase both SCL high and low periods. HOLD: TWD Hold Time Versus TWCK Falling If High-speed mode is selected TWD is internally modified on the TWCK falling edge to meet the I2C specified maximum hold time, else if High-speed mode is not configured TWD is kept unchanged after TWCK falling edge for a period of (HOLD + 3) × tperipheral clock. CKSRC: Transfer Rate Clock Source Value Name Description 0 PERIPH_CK Peripheral clock is used to generate the TWIHS baud rate. 1 GCLK GCLK is used to generate the TWIHS baud rate. 46.7.7 TWIHS Status Register Name: TWIHS_SR Address: 0xF8028020 (0), 0xFC028020 (1) DS60001476B-page 1382  2017 Microchip Technology Inc. SAMA5D2 SERIES Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 SDA 24 SCL 23 LOCK 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCLWS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 SVREAD 2 TXRDY 1 RXRDY 0 TXCOMP TXCOMP: Transmission Completed (cleared by writing TWIHS_THR) TXCOMP used in Master mode: 0: During the length of the current frame. 1: When both holding register and internal shifter are empty and STOP condition has been sent. TXCOMP behavior in Master mode can be seen in Figure 46-6 and in Figure 46-8. 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 46-39, Figure 46-40, Figure 46-41 and Figure 46-42. RXRDY: Receive Holding Register Ready (cleared by reading TWIHS_RHR) 0: No character has been received since the last TWIHS_RHR read operation. 1: A byte has been received in the TWIHS_RHR since the last read. RXRDY behavior in Master mode can be seen in Figure 46-7, Figure 46-8 and Figure 46-9. RXRDY behavior in Slave mode can be seen in Figure 46-37, Figure 46-40, Figure 46-41 and Figure 46-42. TXRDY: Transmit Holding Register Ready (cleared by writing TWIHS_THR) TXRDY used in Master mode: 0: The transmit holding register has not been transferred into the internal shifter. Set to 0 when writing into TWIHS_THR. 1: As soon as a data byte is transferred from TWIHS_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 (enables TWIHS). TXRDY behavior in Master mode can be seen in Figure 46-4, Figure 46-5 and Figure 46-6.  2017 Microchip Technology Inc. DS60001476B-page 1383 SAMA5D2 SERIES TXRDY used in Slave mode: 0: As soon as data is written in the TWIHS_THR, until this data has been transmitted and acknowledged (ACK or NACK). 1: Indicates that the TWIHS_THR is empty and that data has been transmitted and acknowledged. If TXRDY is high and if a NACK has been detected, the transmission is stopped. Thus when TRDY = NACK = 1, the user must not fill TWIHS_THR to avoid losing it. TXRDY behavior in Slave mode can be seen in Figure 46-36, Figure 46-39, Figure 46-41 and Figure 46-42. SVREAD: Slave Read This bit is used in Slave mode only. 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 46-36, Figure 46-37, Figure 46-41 and Figure 46-42. SVACC: Slave Access This bit is used in Slave mode only. 0: TWIHS 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 46-36, Figure 46-37, Figure 46-41 and Figure 46-42. GACC: General Call Access (cleared on read) This bit is used in Slave mode only. 0: No general call has been detected. 1: A general call has been detected. After the detection of general call, if need be, the user may acknowledge this access and decode the following bytes and respond according to the value of the bytes. GACC behavior can be seen in Figure 46-38. OVRE: Overrun Error (cleared on read) This bit is used only if clock stretching is disabled. 0: TWIHS_RHR has not been loaded while RXRDY was set. 1: TWIHS_RHR has been loaded while RXRDY was set. Reset by read in TWIHS_SR when TXCOMP is set. UNRE: Underrun Error (cleared on read) This bit is used only if clock stretching is disabled. 0: TWIHS_THR has been filled on time. 1: TWIHS_THR has not been filled on time. NACK: Not Acknowledged (cleared on read) NACK used in Master mode: 0: Each data byte has been correctly received by the far-end side TWIHS slave component. 1: A data or address byte has not been acknowledged by the slave component. Set at the same time as TXCOMP. DS60001476B-page 1384  2017 Microchip Technology Inc. SAMA5D2 SERIES 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 user must not fill TWIHS_THR even if TXRDY is set, because it means that the master stops the data transfer or re-initiate it. Note: in Slave Write mode, all data are acknowledged by the TWIHS. ARBLST: Arbitration Lost (cleared on read) This bit is used in Master mode only. 0: Arbitration won. 1: Arbitration lost. Another master of the TWIHS bus has won the multimaster arbitration. TXCOMP is set at the same time. SCLWS: Clock Wait State This bit is used in Slave mode only. 0: The clock is not stretched. 1: The clock is stretched. TWIHS_THR / TWIHS_RHR buffer is not filled / emptied before the transmission / reception of a new character. SCLWS behavior can be seen in Figure 46-39 and Figure 46-40. EOSACC: End Of Slave Access (cleared on read) This bit is used in Slave mode only. 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 46-41 and Figure 46-42. MCACK: Master Code Acknowledge (cleared on read) MACK used in Slave mode: 0: No Master Code has been received since the last read of TWIHS_SR. 1: A Master Code has been received since the last read of TWIHS_SR. TOUT: Timeout Error (cleared on read) 0: No SMBus timeout occurred since the last read of TWIHS_SR. 1: An SMBus timeout occurred since the last read of TWIHS_SR. PECERR: PEC Error (cleared on read) 0: No SMBus PEC error occurred since the last read of TWIHS_SR. 1: An SMBus PEC error occurred since the last read of TWIHS_SR. SMBDAM: SMBus Default Address Match (cleared on read) 0: No SMBus Default Address received since the last read of TWIHS_SR. 1: An SMBus Default Address was received since the last read of TWIHS_SR. SMBHHM: SMBus Host Header Address Match (cleared on read) 0: No SMBus Host Header Address received since the last read of TWIHS_SR. 1: An SMBus Host Header Address was received since the last read of TWIHS_SR. LOCK: TWIHS Lock due to Frame Errors (cleared by writing a one to bit LOCKCLR in TWIHS_CR) 0: The TWIHS is not locked or LOCKCLR command issued in TWIHS_CR. 1: The TWIHS is locked due to frame errors (see Section 46.6.3.13 “Handling Errors in Alternative Command”). SCL: SCL Line Value 0: SCL line sampled value is ‘0’. 1: SCL line sampled value is ‘1.’  2017 Microchip Technology Inc. DS60001476B-page 1385 SAMA5D2 SERIES SDA: SDA Line Value 0: SDA line sampled value is ‘0’. 1: SDA line sampled value is ‘1’. DS60001476B-page 1386  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.8 TWIHS Status Register (FIFO_ENABLED) Name: TWIHS_SR (FIFO_ENABLED) Address: 0xF8028020 (0), 0xFC028020 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 SDA 24 SCL 23 TXFLOCK 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCLWS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 SVREAD 2 TXRDY 1 RXRDY 0 TXCOMP TXCOMP: Transmission Completed (cleared by writing TWIHS_THR) TXCOMP used in Master mode: 0: During the length of the current frame. 1: When both holding register and internal shifter are empty and STOP condition has been sent. TXCOMP behavior in Master mode can be seen in Figure 46-6 and in Figure 46-8. 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 46-39, Figure 46-40, Figure 46-41 and Figure 46-42. RXRDY: Receive Holding Register Ready (cleared by reading TWIHS_RHR) 0: No character has been received since the last TWIHS_RHR read operation. 1: A byte has been received in the TWIHS_RHR since the last read. RXRDY behavior in Master mode can be seen in Figure 46-7, Figure 46-8 and Figure 46-9. RXRDY behavior in Slave mode can be seen in Figure 46-37, Figure 46-40, Figure 46-41 and Figure 46-42. TXRDY: Transmit Holding Register Ready (cleared by writing TWIHS_THR) TXRDY used in Master mode: 0: The transmit holding register has not been transferred into the internal shifter. Set to 0 when writing into TWIHS_THR. 1: As soon as a data byte is transferred from TWIHS_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 (enables TWIHS). TXRDY behavior in Master mode can be seen in Figure 46-4, Figure 46-5 and Figure 46-6.  2017 Microchip Technology Inc. DS60001476B-page 1387 SAMA5D2 SERIES TXRDY used in Slave mode: 0: As soon as data is written in the TWIHS_THR, until this data has been transmitted and acknowledged (ACK or NACK). 1: Indicates that the TWIHS_THR is empty and that data has been transmitted and acknowledged. If TXRDY is high and if a NACK has been detected, the transmission is stopped. Thus when TRDY = NACK = 1, the user must not fill TWIHS_THR to avoid losing it. TXRDY behavior in Slave mode can be seen in Figure 46-36, Figure 46-39, Figure 46-41 and Figure 46-42. SVREAD: Slave Read This bit is used in Slave mode only. 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 46-36, Figure 46-37, Figure 46-41 and Figure 46-42. SVACC: Slave Access This bit is used in Slave mode only. 0: TWIHS 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 46-36, Figure 46-37, Figure 46-41 and Figure 46-42. GACC: General Call Access (cleared on read) This bit is used in Slave mode only. 0: No general call has been detected. 1: A general call has been detected. After the detection of general call, if need be, the user may acknowledge this access and decode the following bytes and respond according to the value of the bytes. GACC behavior can be seen in Figure 46-38. OVRE: Overrun Error (cleared on read) This bit is used only if clock stretching is disabled. 0: TWIHS_RHR has not been loaded while RXRDY was set. 1: TWIHS_RHR has been loaded while RXRDY was set. Reset by read in TWIHS_SR when TXCOMP is set. UNRE: Underrun Error (cleared on read) This bit is used only if clock stretching is disabled. 0: TWIHS_THR has been filled on time. 1: TWIHS_THR has not been filled on time. NACK: Not Acknowledged (cleared on read) NACK used in Master mode: 0: Each data byte has been correctly received by the far-end side TWIHS slave component. 1: A data or address byte has not been acknowledged by the slave component. Set at the same time as TXCOMP. DS60001476B-page 1388  2017 Microchip Technology Inc. SAMA5D2 SERIES 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 user must not fill TWIHS_THR even if TXRDY is set, because it means that the master stops the data transfer or re-initiate it. Note: in Slave Write mode, all data are acknowledged by the TWIHS. ARBLST: Arbitration Lost (cleared on read) This bit is used in Master mode only. 0: Arbitration won. 1: Arbitration lost. Another master of the TWIHS bus has won the multimaster arbitration. TXCOMP is set at the same time. SCLWS: Clock Wait State This bit is used in Slave mode only. 0: The clock is not stretched. 1: The clock is stretched. TWIHS_THR / TWIHS_RHR buffer is not filled / emptied before the transmission / reception of a new character. SCLWS behavior can be seen in Figure 46-39 and Figure 46-40. EOSACC: End Of Slave Access (cleared on read) This bit is used in Slave mode only. 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 46-41 and Figure 46-42. MCACK: Master Code Acknowledge (cleared on read) MACK used in Slave mode: 0: No Master Code has been received since the last read of TWIHS_SR. 1: A Master Code has been received since the last read of TWIHS_SR. TOUT: Timeout Error (cleared on read) 0: No SMBus timeout occurred since the last read of TWIHS_SR. 1: An SMBus timeout occurred since the last read of TWIHS_SR. PECERR: PEC Error (cleared on read) 0: No SMBus PEC error occurred since the last read of TWIHS_SR. 1: An SMBus PEC error occurred since the last read of TWIHS_SR. SMBDAM: SMBus Default Address Match (cleared on read) 0: No SMBus Default Address received since the last read of TWIHS_SR. 1: An SMBus Default Address was received since the last read of TWIHS_SR. SMBHHM: SMBus Host Header Address Match (cleared on read) 0: No SMBus Host Header Address received since the last read of TWIHS_SR. 1: An SMBus Host Header Address was received since the last read of TWIHS_SR.  2017 Microchip Technology Inc. DS60001476B-page 1389 SAMA5D2 SERIES TXFLOCK: Transmit FIFO Lock 0: The Transmit FIFO is not locked. 1: The Transmit FIFO is locked. SCL: SCL Line Value 0: SCL line sampled value is ‘0’. 1: SCL line sampled value is ‘1.’ SDA: SDA Line Value 0: SDA line sampled value is ‘0’. 1: SDA line sampled value is ‘1’. DS60001476B-page 1390  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.9 TWIHS SMBus Timing Register Name: TWIHS_SMBTR Address: 0xF8028038 (0), 0xFC028038 (1) Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 THMAX 23 22 21 20 TLOWM 15 14 13 12 TLOWS 7 – 6 – 5 – 4 – PRESC This register can only be written if the WPEN bit is cleared in the TWIHS Write Protection Mode Register. PRESC: SMBus Clock Prescaler Used to specify how to prescale the TLOWS, TLOWM and THMAX counters in SMBTR. Counters are prescaled according to the following formula: f peripheral clock f Prescaled = --------------------------------( PRESC + 1 ) 2 TLOWS: Slave Clock Stretch Maximum Cycles 0: TLOW:SEXT timeout check disabled. 1–255: Clock cycles in slave maximum clock stretch count. Prescaled by PRESC. Used to time TLOW:SEXT. TLOWM: Master Clock Stretch Maximum Cycles 0: TLOW:MEXT timeout check disabled. 1–255: Clock cycles in master maximum clock stretch count. Prescaled by PRESC. Used to time TLOW:MEXT. THMAX: Clock High Maximum Cycles Clock cycles in clock high maximum count. Prescaled by PRESC. Used for bus free detection. Used to time THIGH:MAX.  2017 Microchip Technology Inc. DS60001476B-page 1391 SAMA5D2 SERIES 46.7.10 TWIHS Alternative Command Register Name: TWIHS_ACR Address: 0xF8028040 (0), 0xFC028040 (1) Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 NPEC 24 NDIR 19 18 17 16 11 – 10 – 9 PEC 8 DIR 3 2 1 0 NDATAL 15 – 14 – 13 – 12 – 7 6 5 4 DATAL DATAL: Data Length 0: No data to send (see Section 46.6.3.12 “Alternative Command”). 1–255: Number of bytes to send during the transfer. DIR: Transfer Direction 0: Write direction. 1: Read direction. PEC: PEC Request (SMBus Mode only) 0: The transfer does not use a PEC byte. 1: The transfer uses a PEC byte. NDATAL: Next Data Length 0: No data to send (see Section 46.6.3.12 “Alternative Command”. 1–255: Number of bytes to send for the next transfer. NDIR: Next Transfer Direction 0: Write direction. 1: Read direction. NPEC: Next PEC Request (SMBus Mode only) 0: The next transfer does not use a PEC byte. 1: The next transfer uses a PEC byte. DS60001476B-page 1392  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.11 TWIHS Filter Register Name: TWIHS_FILTR Address: 0xF8028044 (0), 0xFC028044 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 9 THRES 8 7 – 6 – 5 – 4 – 3 – 2 PADFCFG 1 PADFEN 0 FILT FILT: RX Digital Filter 0: No filtering applied on TWIHS inputs. 1: TWIHS input filtering is active (only in Standard and Fast modes) Note: TWIHS digital input filtering follows a majority decision based on three samples from SDA/SCL lines at peripheral clock frequency. PADFEN: PAD Filter Enable 0: PAD analog filter is disabled. 1: PAD analog filter is enabled. (The analog filter must be enabled if High-speed mode is enabled.) PADFCFG: PAD Filter Config See the electrical characteristics section for filter configuration details. THRES: Digital Filter Threshold 0: No filtering applied on TWIHS inputs. 1–7: Maximum pulse width of spikes to be suppressed by the input filter, defined in peripheral clock cycles.  2017 Microchip Technology Inc. DS60001476B-page 1393 SAMA5D2 SERIES 46.7.12 TWIHS Interrupt Enable Register Name: TWIHS_IER Address: 0xF8028024 (0), 0xFC028024 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Enable TOUT: Timeout Error Interrupt Enable PECERR: PEC Error Interrupt Enable SMBDAM: SMBus Default Address Match Interrupt Enable SMBHHM: SMBus Host Header Address Match Interrupt Enable 46.7.13 TWIHS Interrupt Disable Register Name: TWIHS_IDR Address: 0xF8028028 (0), 0xFC028028 (1) DS60001476B-page 1394  2017 Microchip Technology Inc. SAMA5D2 SERIES Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Disable TOUT: Timeout Error Interrupt Disable PECERR: PEC Error Interrupt Disable SMBDAM: SMBus Default Address Match Interrupt Disable SMBHHM: SMBus Host Header Address Match Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 1395 SAMA5D2 SERIES 46.7.14 TWIHS Interrupt Mask Register Name: TWIHS_IMR Address: 0xF802802C (0), 0xFC02802C (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Mask TOUT: Timeout Error Interrupt Mask PECERR: PEC Error Interrupt Mask SMBDAM: SMBus Default Address Match Interrupt Mask SMBHHM: SMBus Host Header Address Match Interrupt Mask DS60001476B-page 1396  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.15 TWIHS Receive Holding Register Name: TWIHS_RHR Address: 0xF8028030 (0), 0xFC028030 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 RXDATA RXDATA: Master or Slave Receive Holding Data  2017 Microchip Technology Inc. DS60001476B-page 1397 SAMA5D2 SERIES 46.7.16 TWIHS Receive Holding Register (FIFO_ENABLED) Name: TWIHS_RHR (FIFO_ENABLED) Address: 0xF8028030 (0), 0xFC028030 (1) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RXDATA3 23 22 21 20 RXDATA2 15 14 13 12 RXDATA1 7 6 5 4 RXDATA0 Note: If FIFO is enabled (FIFOEN bit in TWIHS_CR), see Master Multiple Data Mode for details. RXDATA0: Master or Slave Receive Holding Data 0 RXDATA1: Master or Slave Receive Holding Data 1 RXDATA2: Master or Slave Receive Holding Data 2 RXDATA3: Master or Slave Receive Holding Data 3 DS60001476B-page 1398  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.17 TWIHS SleepWalking Matching Register Name: TWIHS_SWMR Address: 0xF802804C (0), 0xFC02804C (1) Access: Read/Write 31 30 29 28 27 26 25 24 DATAM 23 – 22 21 20 19 SADR3 18 17 16 15 – 14 13 12 11 SADR2 10 9 8 7 – 6 5 4 3 SADR1 2 1 0 This register can only be written if the WPEN bit is cleared in the TWIHS Write Protection Mode Register. SADR1: Slave Address 1 Slave address 1. The TWIHS module matches on this additional address if SADR1EN bit is enabled. SADR2: Slave Address 2 Slave address 2. The TWIHS module matches on this additional address if SADR2EN bit is enabled. SADR3: Slave Address 3 Slave address 3. The TWIHS module matches on this additional address if SADR3EN bit is enabled. DATAM: Data Match The TWIHS module extends the SleepWalking matching process to the first received data, comparing it with DATAM if DATAMEN bit is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1399 SAMA5D2 SERIES 46.7.18 TWIHS Transmit Holding Register Name: TWIHS_THR Address: 0xF8028034 (0), 0xFC028034 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 TXDATA TXDATA: Master or Slave Transmit Holding Data DS60001476B-page 1400  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.19 TWIHS Transmit Holding Register (FIFO_ENABLED) Name: TWIHS_THR (FIFO_ENABLED) Address: 0xF8028034 (0), 0xFC028034 (1) Access: 31 Write-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TXDATA3 23 22 21 20 TXDATA2 15 14 13 12 TXDATA1 7 6 5 4 TXDATA0 Note: If FIFO is enabled (FIFOEN bit in TWIHS_CR), see Master Multiple Data Mode for details. TXDATA0: Master or Slave Transmit Holding Data 02 TXDATA1: Master or Slave Transmit Holding Data 1 TXDATA2: Master or Slave Transmit Holding Data 2 TXDATA3: Master or Slave Transmit Holding Data 3  2017 Microchip Technology Inc. DS60001476B-page 1401 SAMA5D2 SERIES 46.7.20 TWIHS FIFO Mode Register Name: TWIHS_FMR Address: 0xF8028050 (0), 0xFC028050 (1) Access: Read/Write 31 30 – – 29 28 27 26 25 24 23 22 – – 18 17 16 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 3 2 1 – – – – RXFTHRES 21 20 19 TXFTHRES 4 RXRDYM 0 TXRDYM TXRDYM: Transmitter Ready Mode If FIFOs are enabled, the TXRDY flag (in TWIHS_SR) behaves as follows. Value Name Description 0x0 ONE_DATA TXRDY will be at level ‘1’ when at least one data can be written in the Transmit FIFO 0x1 TWO_DATA TXRDY will be at level ‘1’ when at least two data can be written in the Transmit FIFO 0x2 FOUR_DATA TXRDY will be at level ‘1’ when at least four data can be written in the Transmit FIFO RXRDYM: Receiver Ready Mode If FIFOs are enabled, the RXRDY flag (in TWIHS_SR) behaves as follows. Value Name Description 0x0 ONE_DATA RXRDY will be at level ‘1’ when at least one unread data is in the Receive FIFO 0x1 TWO_DATA RXRDY will be at level ‘1’ when at least two unread data are in the Receive FIFO 0x2 FOUR_DATA RXRDY will be at level ‘1’ when at least four unread data are in the Receive FIFO TXFTHRES: Transmit FIFO Threshold 0–16: Defines the Transmit FIFO threshold value (number of data). TXFTH flag in TWIHS_FSR will be set when Transmit FIFO goes from “above” threshold state to “equal or below” threshold state. RXFTHRES: Receive FIFO Threshold 0–16: Defines the Receive FIFO threshold value (number of data). RXFTH flag in TWIHS_FSR will be set when Receive FIFO goes from “below” threshold state to “equal or above” threshold state. DS60001476B-page 1402  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.21 TWIHS FIFO Level Register Name: TWIHS_FLR Address: 0xF8028054 (0), 0xFC028054 (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – RXFL TXFL TXFL: Transmit FIFO Level 0: There is no data in the Transmit FIFO 1–16: Indicates the number of DATA in the Transmit FIFO RXFL: Receive FIFO Level 0: There is no unread data in the Receive FIFO 1–16: Indicates the number of unread DATA in the Receive FIFO  2017 Microchip Technology Inc. DS60001476B-page 1403 SAMA5D2 SERIES 46.7.22 TWIHS FIFO Status Register Name: TWIHS_FSR Address: 0xF8028060 (0), 0xFC028060 (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: Transmit FIFO Empty Flag (cleared on read) 0: Transmit FIFO is not empty. 1: Transmit FIFO has been emptied since the last read of TWIHS_FSR. TXFFF: Transmit FIFO Full Flag (cleared on read) 0: Transmit FIFO is not full. 1: Transmit FIFO has been filled since the last read of TWIHS_FSR. TXFTHF: Transmit FIFO Threshold Flag (cleared on read) 0: Number of DATA in Transmit FIFO is above TXFTHRES threshold. 1: Number of DATA in Transmit FIFO has reached TXFTHRES threshold since the last read of TWIHS_FSR. RXFEF: Receive FIFO Empty Flag 0: Receive FIFO is not empty. 1: Receive FIFO has been emptied since the last read of TWIHS_FSR. RXFFF: Receive FIFO Full Flag 0: Receive FIFO is not empty. 1: Receive FIFO has been filled since the last read of TWIHS_FSR. RXFTHF: Receive FIFO Threshold Flag 0: Number of unread DATA in Receive FIFO is below RXFTHRES threshold. 1: Number of unread DATA in Receive FIFO has reached RXFTHRES threshold since the last read of TWIHS_FSR. TXFPTEF: Transmit FIFO Pointer Error Flag 0: No Transmit FIFO pointer occurred 1: Transmit FIFO pointer error occurred. Transceiver must be reset See Section • “FIFO Pointer Error” for details. RXFPTEF: Receive FIFO Pointer Error Flag 0: No Receive FIFO pointer occurred 1: Receive FIFO pointer error occurred. Receiver must be reset See Section • “FIFO Pointer Error” for details. DS60001476B-page 1404  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.23 TWIHS FIFO Interrupt Enable Register Name: TWIHS_FIER Address: 0xF8028064 (0), 0xFC028064 (1) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. TXFEF: TXFEF Interrupt Enable TXFFF: TXFFF Interrupt Enable TXFTHF: TXFTHF Interrupt Enable RXFEF: RXFEF Interrupt Enable RXFFF: RXFFF Interrupt Enable RXFTHF: RXFTHF Interrupt Enable TXFPTEF: TXFPTEF Interrupt Enable RXFPTEF: RXFPTEF Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1405 SAMA5D2 SERIES 46.7.24 TWIHS FIFO Interrupt Disable Register Name: TWIHS_FIDR Address: 0xF8028068 (0), 0xFC028068 (1) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. TXFEF: TXFEF Interrupt Disable TXFFF: TXFFF Interrupt Disable TXFTHF: TXFTHF Interrupt Disable RXFEF: RXFEF Interrupt Disable RXFFF: RXFFF Interrupt Disable RXFTHF: RXFTHF Interrupt Disable TXFPTEF: TXFPTEF Interrupt Disable RXFPTEF: RXFPTEF Interrupt Disable DS60001476B-page 1406  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.25 TWIHS FIFO Interrupt Mask Register Name: TWIHS_FIMR Address: 0xF802806C (0), 0xFC02806C (1) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. TXFEF: TXFEF Interrupt Mask TXFFF: TXFFF Interrupt Mask TXFTHF: TXFTHF Interrupt Mask RXFEF: RXFEF Interrupt Mask RXFFF: RXFFF Interrupt Mask RXFTHF: RXFTHF Interrupt Mask TXFPTEF: TXFPTEF Interrupt Mask RXFPTEF: RXFPTEF Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1407 SAMA5D2 SERIES 46.7.26 TWIHS Write Protection Mode Register Name: TWIHS_WPMR Address: 0xF80280E4 (0), 0xFC0280E4 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x545749 (“TWI” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x545749 (“TWI” in ASCII). See Section 46.6.7 “Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x545749 Name PASSWD DS60001476B-page 1408 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0  2017 Microchip Technology Inc. SAMA5D2 SERIES 46.7.27 TWIHS Write Protection Status Register Name: TWIHS_WPSR Address: 0xF80280E8 (0), 0xFC0280E8 (1) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 23 22 21 20 WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of the TWIHS_WPSR. 1: A write protection violation has occurred since the last read of the TWIHS_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.  2017 Microchip Technology Inc. DS60001476B-page 1409 SAMA5D2 SERIES 47. Flexible Serial Communication Controller (FLEXCOM) 47.1 Description The Flexible Serial Communication Controller (FLEXCOM) offers several serial communication protocols that are managed by the three submodules USART, SPI, and TWI. 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 timeout 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, LIN, and SPI, 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 DMA Controller, which enables data transfers to the transmitter and from the receiver. The DMAC provides chained buffer management without any intervention of the processor. The Serial Peripheral Interface (SPI) circuit 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 turn being masters (multiple master protocol, contrary to single master protocol where one CPU is always the master while all of the others are always slaves). One master can simultaneously shift data into multiple slaves. However, only one slave can drive its output to write data back to the master at any given time. A slave device is selected when the master asserts its NSS signal. If multiple slave devices exist, the master generates a separate slave select signal for each slave (NPCS). 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(s) of the slave(s). • Master In Slave Out (MISO)—This data line supplies the output data from a slave to the input of the master. There may be no more than one slave transmitting data during any particular transfer. • Serial Clock (SPCK)—This control line is driven by the master and regulates the flow of the data bits. The master can transmit data at a variety of baud rates; there is one SPCK pulse for each bit that is transmitted. • Slave Select (NSS)—This control line allows slaves to be turned on and off by hardware. The Two-wire Interface (TWI) interconnects components on a unique two-wire bus, made up of one clock line and one data line with speeds of up to 400 kbits per second in Fast mode and up to 3.4 Mbits per second in High-speed Slave mode only, based on a byteoriented transfer format. It can be used with any Two-wire Interface bus Serial EEPROM and I2C-compatible devices, such as a RealTime Clock (RTC), Dot Matrix/Graphic LCD Controller and temperature sensor. The TWI is programmable as a master or a slave with sequential or single-byte access. Multiple master capability is supported. Arbitration of the bus is performed internally and puts the TWI in Slave mode automatically if the bus arbitration is lost. A configurable baud rate generator permits the output data rate to be adapted to a wide range of core clock frequencies. Table 47-1 lists the compatibility level of the Two-wire Interface in Master mode and a full I2C compatible device. DS60001476B-page 1410  2017 Microchip Technology Inc. SAMA5D2 SERIES TWI Compatibility with I2C Standard Table 47-1: I2C Standard TWI Standard Mode Speed (100 kHz) Supported Fast Mode Speed (400 kHz) Supported High-speed Mode (Slave only, 3.4 MHz) Supported 7- or 10-bit(1) Slave Addressing Supported Repeated Start (Sr) Condition Supported ACK and NACK Management Supported Input Filtering Supported Slope Control Not Supported Clock Stretching Supported Multi Master Capability Supported Note 1: 10-bit support in Master mode only.  2017 Microchip Technology Inc. DS60001476B-page 1411 SAMA5D2 SERIES 47.2 47.2.1 • • • • • • • • • • • • • Embedded Characteristics USART/UART Characteristics 32-byte Transmit and Receive FIFOs Programmable Baud Rate Generator Baud Rate can be Independent of the Processor/Peripheral Clock Comparison Function on Received Character 5-bit 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 - Digital Filter on Receive Line - MSB- or LSB-first - Optional Break Generation and Detection - By 8 or by 16 Oversampling Receiver Frequency - Optional Hardware Handshaking RTS-CTS - Receiver Timeout 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 kbit/s SPI Mode - MASTER or Slave - Serial Clock Programmable Phase and Polarity - SPI Serial Clock (SCK) Frequency up to fperipheral clock/6 LIN Mode - Compliant with LIN 1.3 and LIN 2.0 specifications - Master or Slave - Processing of Frames with Up to 256 Data Bytes - Response Data Length can be Configurable or Defined Automatically by the Identifier - Self-synchronization in Slave Node Configuration - Automatic Processing and Verification of the “Synch Break” and the “Synch Field” - “Synch Break” Detection Even When Partially Superimposed with a Data Byte - Automatic Identifier Parity Calculation/Sending and Verification - Parity Sending and Verification Can be Disabled - Automatic Checksum Calculation/sending and Verification - Checksum Sending and Verification Can be Disabled - Support Both “Classic” and “Enhanced” Checksum Types - Full LIN Error Checking and Reporting - Frame Slot Mode: Master Allocates Slots to the Scheduled Frames Automatically - Generation of the Wakeup Signal Test Modes - Remote Loopback, Local Loopback, Automatic Echo Supports Connection of: - Two DMA Controller (DMAC) Channels - Offers Buffer Transfer without Processor Intervention Register Write Protection DS60001476B-page 1412  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.2.2 SPI Characteristics • 32-byte Transmit and Receive FIFOs • Master or Slave Serial Peripheral Bus Interface - 8-bit to 16-bit programmable data length per chip select - Programmable phase and polarity per chip select - Programmable transfer delay between consecutive transfers and delay before SPI clock per chip select - Programmable delay between chip selects • Selectable Mode Fault Detection • Master Mode Can Drive SPCK up to Peripheral Clock • Master Mode Bit Rate Can Be Independent of the Processor/Peripheral Clock • Slave Mode Operates on SPCK, Asynchronously with Core and Bus Clock • Two Chip Selects with External Decoder Support Allow Communication with up to 3 Peripherals • Communication with Serial External Devices Supported - Serial memories, such as DataFlash and 3-wire EEPROMs - Serial peripherals, such as ADCs, DACs, LCD controllers, CAN controllers and sensors - External coprocessors • Connection to DMA Channel Capabilities, Optimizing Data Transfers - One channel for the receiver - One channel for the transmitter • Register Write Protection 47.2.3 TWI/SMBus Characteristics • • • • • • • • • • • 16-byte Transmit and Receive FIFOs Bit Rate: Up to 400 kbit/s in Fast Mode and 3.4 Mbit/s in High-Speed Mode (Slave Only) Bit Rate can be Independent of the Processor/Peripheral Clock SMBus Support Compatible with Two-wire Interface Serial Memory and I2C Compatible Devices(1) Master and Multi-Master Operation (Standard and Fast Mode Only) Slave Mode Operation (Standard, Fast and High-Speed Mode) One, Two or Three Bytes for Slave Address Sequential Read/Write Operations General Call Supported in Slave Mode Connection to DMA Controller Channels Optimizes Data Transfers - One Channel for the Receiver - One Channel for the Transmitter • Register Write Protection Note 1: See Table 47-1 for details on compatibility with I2C Standard.  2017 Microchip Technology Inc. DS60001476B-page 1413 SAMA5D2 SERIES 47.3 Block Diagram Figure 47-1: FLEXCOM Block Diagram FLEXCOM Channel PIO Controller mux RX trigger event DMA Controller (DMAC) TX trigger event Pads MR mux FLEXCOM Interrupt USART txd,rxd, sck, rts,cts SPI mosi, miso, spck, npcs0/1 clock1 Channel FLEXCOM I/Os mux Interrupt Controller MR clock2 twd, twck Bus clock TWI clock3 Peripheral Bridge FLEX_MR = MR APB FLEXCOM User Interface MR=1 Peripheral clock MR=2 MR=3 PMC GCLK 47.4 to USART, SPI, and TWI I/O Lines Description Table 47-2: I/O Lines Description Description Name USART/UART SPI TWI Type FLEXCOM_IO0 TXD MOSI TWD I/O FLEXCOM_IO1 RXD MISO TWCK I/O FLEXCOM_IO2 SCK SPCK – I/O FLEXCOM_IO3 CTS NPCS0/NSS – I/O FLEXCOM_IO4 RTS NPCS1 – O DS60001476B-page 1414  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.5 Product Dependencies 47.5.1 I/O Lines The pins used for interfacing the FLEXCOM are multiplexed with the PIO lines. The programmer must first program the PIO controller to assign the desired FLEXCOM pins to their peripheral function. If I/O lines of the FLEXCOM are not used by the application, they can be used for other purposes by the PIO Controller. Table 47-3: I/O Lines Instance Signal I/O Line Peripheral FLEXCOM0 FLEXCOM0_IO0 PB28 C FLEXCOM0 FLEXCOM0_IO1 PB29 C FLEXCOM0 FLEXCOM0_IO2 PB30 C FLEXCOM0 FLEXCOM0_IO3 PB31 C FLEXCOM0 FLEXCOM0_IO4 PC0 C FLEXCOM1 FLEXCOM1_IO0 PA24 A FLEXCOM1 FLEXCOM1_IO1 PA23 A FLEXCOM1 FLEXCOM1_IO2 PA22 A FLEXCOM1 FLEXCOM1_IO3 PA25 A FLEXCOM1 FLEXCOM1_IO4 PA26 A FLEXCOM2 FLEXCOM2_IO0 PA6 E FLEXCOM2 FLEXCOM2_IO0 PD26 C FLEXCOM2 FLEXCOM2_IO1 PA7 E FLEXCOM2 FLEXCOM2_IO1 PD27 C FLEXCOM2 FLEXCOM2_IO2 PA8 E FLEXCOM2 FLEXCOM2_IO2 PD28 C FLEXCOM2 FLEXCOM2_IO3 PA9 E FLEXCOM2 FLEXCOM2_IO3 PD29 C FLEXCOM2 FLEXCOM2_IO4 PA10 E FLEXCOM2 FLEXCOM2_IO4 PD30 C FLEXCOM3 FLEXCOM3_IO0 PA15 E FLEXCOM3 FLEXCOM3_IO0 PB23 E FLEXCOM3 FLEXCOM3_IO0 PC20 E FLEXCOM3 FLEXCOM3_IO1 PA13 E FLEXCOM3 FLEXCOM3_IO1 PB22 E FLEXCOM3 FLEXCOM3_IO1 PC19 E FLEXCOM3 FLEXCOM3_IO2 PA14 E FLEXCOM3 FLEXCOM3_IO2 PB21 E FLEXCOM3 FLEXCOM3_IO2 PC18 E FLEXCOM3 FLEXCOM3_IO3 PA16 E FLEXCOM3 FLEXCOM3_IO3 PB24 E FLEXCOM3 FLEXCOM3_IO3 PC21 E  2017 Microchip Technology Inc. DS60001476B-page 1415 SAMA5D2 SERIES Table 47-3: I/O Lines FLEXCOM3 FLEXCOM3_IO4 PA17 E FLEXCOM3 FLEXCOM3_IO4 PB25 E FLEXCOM3 FLEXCOM3_IO4 PC22 E FLEXCOM4 FLEXCOM4_IO0 PC28 B FLEXCOM4 FLEXCOM4_IO0 PD12 B FLEXCOM4 FLEXCOM4_IO0 PD21 C FLEXCOM4 FLEXCOM4_IO1 PC29 B FLEXCOM4 FLEXCOM4_IO1 PD13 B FLEXCOM4 FLEXCOM4_IO1 PD22 C FLEXCOM4 FLEXCOM4_IO2 PC30 B FLEXCOM4 FLEXCOM4_IO2 PD14 B FLEXCOM4 FLEXCOM4_IO2 PD23 C FLEXCOM4 FLEXCOM4_IO3 PC31 B FLEXCOM4 FLEXCOM4_IO3 PD15 B FLEXCOM4 FLEXCOM4_IO3 PD24 C FLEXCOM4 FLEXCOM4_IO4 PD0 B FLEXCOM4 FLEXCOM4_IO4 PD16 B FLEXCOM4 FLEXCOM4_IO4 PD25 C 47.5.2 Power Management The peripheral clock is not continuously provided to the FLEXCOM. The programmer must first enable the FLEXCOM Clock in the Power Management Controller (PMC) before using the USART or SPI or TWI. In SleepWalking mode (asynchronous partial wakeup), the PMC must be configured to enable SleepWalking for the FLEXCOM in the Sleepwalking Enable Register (PMC_SLPWK_ER). The peripheral clock can be automatically provided to the FLEXCOM, depending on the instructions (requests) provided by the FLEXCOM to the PMC. 47.5.3 Interrupt Sources The FLEXCOM interrupt line is connected on one of the internal sources of the Interrupt Controller. Using the FLEXCOM interrupt requires the Interrupt Controller to be programmed first. Table 47-4: Peripheral IDs Instance ID FLEXCOM0 19 FLEXCOM1 20 FLEXCOM2 21 FLEXCOM3 22 FLEXCOM4 23 DS60001476B-page 1416  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.6 Register Accesses Register accesses supports 8-bit, 16-bit and 32-bit accesses which means that only an 8-bit part of a 32-bit register can be written in one access for instance. For this the access must be done with the right size at the right address. 8-bit, 16-bit and 32-bit accesses are supported for register accesses however a field in a register cannot be partially written (e.g., if a field is bigger than 8 bits, the whole field must be written). This feature helps avoiding a read-modify-write process if only a small part of the register is to be modified. 47.7 47.7.1 USART Functional Description Baud Rate Generator The baud rate generator provides the bit period clock named “baud rate clock” to both the receiver and the transmitter. Configuring the USCLKS field in FLEX_US_MR selects the baud rate generator clock from one of the following sources: • • • • the peripheral clock a division of the peripheral clock, the divider being product dependent, but generally set to 8 a fully programmable generic clock (GCLK) provided by PMC and independent of processor/peripheral clock the external clock, available on the SCK 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 (FLEX_US_BRGR). If a zero is written to CD, the baud rate generator does not generate any clock. If a one is written to CD, the divider is bypassed and becomes inactive. If the external SCK clock is selected, the duration of the low and high levels of the signal provided on the SCK pin must be longer than a peripheral clock period. The frequency of the signal provided on SCK must be at least three times lower than peripheral clock in USART mode (field USART_MODE differs from 0xE or 0xF) or six times lower in SPI mode (field USART_MODE equals 0xE or 0xF). If GCLK is selected, the baud rate is independent of the processor/peripheral clock and thus processor/peripheral clock frequency can be changed without affecting the USART transfer. The GCLK frequency must be at least three times lower than peripheral clock frequency. If GCLK is selected (USCLKS = 2) and the SCK pin is driven (CLKO = 1), the CD field must be greater than 1. Figure 47-2: Baud Rate Generator USCLKS CD Peripheral clock 0 Peripheral clock/DIV 1 GCLK 2 SCK CD SCK 16-bit Counter FIDI >1 3 1 0 0 0 SYNC OVER Sampling Divider 0 Baud Rate Clock 1 1 SYNC USCLKS = 3 47.7.1.1 Sampling Clock 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 FLEX_US_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 FLEX_US_MR.OVER. If OVER is set, the receiver sampling is eight times higher than the baud rate clock. If OVER is cleared, the sampling is performed at 16 times the baud rate clock. The baud rate is calculated as per the following formula: Selected Clock Baud rate = -------------------------------------------------( 8 ( 2 – OVER )CD )  2017 Microchip Technology Inc. DS60001476B-page 1417 SAMA5D2 SERIES This gives a maximum baud rate of peripheral clock divided by 8, assuming that peripheral clock is the highest possible clock and that the OVER bit is set. • Baud Rate Calculation Example Table 47-5 shows calculations of CD to obtain a baud rate at 38,400 bit/s for different source clock frequencies. This table also shows the actual resulting baud rate and the error. Table 47-5: Baud Rate Example (OVER = 0) Source Clock (MHz) Expected Baud Rate (bit/s) Calculation Result CD Actual Baud Rate (bit/s) Error 3,686,400 38,400 6.00 6 38,400.00 0.00% 4,915,200 38,400 8.00 8 38,400.00 0.00% 5,000,000 38,400 8.14 8 39,062.50 1.70% 7,372,800 38,400 12.00 12 38,400.00 0.00% 8,000,000 38,400 13.02 13 38,461.54 0.16% 12,000,000 38,400 19.53 20 37,500.00 2.40% 12,288,000 38,400 20.00 20 38,400.00 0.00% 14,318,180 38,400 23.30 23 38,908.10 1.31% 14,745,600 38,400 24.00 24 38,400.00 0.00% 18,432,000 38,400 30.00 30 38,400.00 0.00% 24,000,000 38,400 39.06 39 38,461.54 0.16% 24,576,000 38,400 40.00 40 38,400.00 0.00% 25,000,000 38,400 40.69 40 38,109.76 0.76% 32,000,000 38,400 52.08 52 38,461.54 0.16% 32,768,000 38,400 53.33 53 38,641.51 0.63% 33,000,000 38,400 53.71 54 38,194.44 0.54% 40,000,000 38,400 65.10 65 38,461.54 0.16% 50,000,000 38,400 81.38 81 38,580.25 0.47% The baud rate is calculated with the following formula: Baud rate = MCK / CD × 16 The baud rate error is calculated with the following formula. It is not recommended to work with an error higher than 5%. Expected Baud Rate Error = 1 –  ------------------------------------------------------- Actual Baud Rate 47.7.1.2 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 FLEX_US_BRGR. If FP is not 0, the fractional part is activated. The resolution is one eighth of the clock divider. The fractional baud rate is calculated using the following formula: Selected Clock Baud rate = --------------------------------------------------------------------- 8 ( 2 – OVER )  CD + FP --------    8  The modified architecture is presented in Figure 47-3. DS60001476B-page 1418  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-3: Fractional Baud Rate Generator FP USCLKS CD Modulus Control FP SCK (CLKO = 1) CD Peripheral clock 0 Peripheral clock/DIV 1 PMC.GCLK 2 SCK 3 16-bit Counter Glitch-free Logic 1 (CLKO = 0) 0 FIDI >1 0 SYNC OVER 0 Sampling Divider 0 Baud Rate Clock 1 1 SYNC Sampling Clock USCLKS = 3 Warning: When the value of field FP is greater than 0, the SCK (oversampling clock) generates nonconstant duty cycles. The SCK high duration is increased by “selected clock” period from time to time. The duty cycle depends on the value of the CD field. 47.7.1.3 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 CD field in FLEX_US_BRGR: Selected Clock Baud rate = ---------------------------------------CD In Synchronous mode, if the external clock is selected (USCLKS = 3) and CLKO = 0 (Slave mode), the clock is provided directly by the signal on the USART SCK pin. No division is active. The value written in FLEX_US_BRGR has no effect. The external clock frequency must be at least three times lower than the system clock. In Synchronous mode master (USCLKS = 0 or 1, CLKO = 1), the receive part limits the SCK maximum frequency to fperipheral clock/3 in USART mode, or fperipheral clock/6 in SPI mode. When either the external clock SCK or the internal clock divided (peripheral clock/DIV or GCLK) is selected, the value programmed in CD must be even if the user has to ensure a 50:50 mark/space ratio on the SCK pin. If the peripheral clock is selected, the baud rate generator ensures a 50:50 duty cycle on the SCK pin, even if the value programmed in CD is odd. 47.7.1.4 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 47-6. Table 47-6: DI field Di (decimal) Binary and Decimal Values for Di 0001 0010 0011 0100 0101 0110 1000 1001 1 2 4 8 16 32 12 20  2017 Microchip Technology Inc. DS60001476B-page 1419 SAMA5D2 SERIES Fi is a binary value encoded on a 4-bit field, named FI, as represented in Table 47-7. Table 47-7: Binary and Decimal Values for Fi FI field 0000 0001 0010 0011 0100 0101 0110 1001 1010 1011 1100 1101 Fi (decimal) 372 372 558 744 1116 1488 1860 512 768 1024 1536 2048 Table 47-8 shows the resulting Fi/Di Ratio, which is the ratio between the ISO7816 clock and the baud rate clock. Table 47-8: Possible Values for the Fi/Di Ratio Fi/Di 372 558 744 1116 1488 1806 512 768 1024 1536 2048 1 372 558 744 1116 1488 1860 512 768 1024 1536 2048 2 186 279 372 558 744 930 256 384 512 768 1024 4 93 139.5 186 279 372 465 128 192 256 384 512 8 46.5 69.75 93 139.5 186 232.5 64 96 128 192 256 16 23.25 34.87 46.5 69.75 93 116.2 32 48 64 96 128 32 11.62 17.43 23.25 34.87 46.5 58.13 16 24 32 48 64 12 31 46.5 62 93 124 155 42.66 64 85.33 128 170.6 20 18.6 27.9 37.2 55.8 74.4 93 25.6 38.4 51.2 76.8 102.4 If the USART is configured in ISO7816 mode, the clock selected by the USCLKS field in FLEX_US_MR is first divided by the value programmed in field CD field in FLEX_US_BRGR. The resulting clock can be provided to the SCK pin to feed the smart card clock inputs. This means that FLEX_US_MR.CLKO can be set. This clock is then divided by the value programmed in the FI_DI_RATIO field in the FI DI Ratio Register (FLEX_US_FIDI). This is performed by the Sampling Divider, which performs a division by up to 65535 in ISO7816 mode. The noninteger 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 47-4 shows the relation between the Elementary Time Unit, corresponding to a bit time, and the ISO 7816 clock. Figure 47-4: Elementary Time Unit (ETU) FI_DI_RATIO ISO7816 Clock Cycles ISO7816 Clock on SCK ISO7816 I/O Line on TXD 1 ETU 47.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 USART Control Register (FLEX_US_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 FLEX_US_CR. However, the transmitter registers can be programmed before being enabled. The receiver and the transmitter can be enabled together or independently. DS60001476B-page 1420  2017 Microchip Technology Inc. SAMA5D2 SERIES 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 FLEX_US_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 FLEX_US_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 USART Transmit Holding Register (FLEX_US_THR). If a timeguard is programmed, it is handled normally. 47.7.3 47.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, 1 optional parity bit and up to 2 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 MODE9 bit in FLEX_US_MR. Nine bits are selected by setting the MODE9 bit regardless of the CHRL field. The parity bit is set according to the PAR field in FLEX_US_MR. The even, odd, space, marked or none parity bit can be configured. The MSBF bit in FLEX_US_MR configures which data bit is sent first. If written to 1, the most significant bit is sent first. If written to 0, the less significant bit is sent first. The number of stop bits is selected by the NBSTOP field in FLEX_US_MR. The 1.5 stop bit is supported in Asynchronous mode only. Figure 47-5: 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 FLEX_US_THR. The transmitter reports two status bits in the USART Channel Status Register (FLEX_US_CSR): TXRDY (Transmitter Ready), which indicates that FLEX_US_THR is empty and TXEMPTY, which indicates that all the characters written in FLEX_US_THR have been processed. When the current character processing is completed, the last character written in FLEX_US_THR is transferred into the shift register of the transmitter and FLEX_US_THR is emptied, thus TXRDY rises. Both TXRDY and TXEMPTY bits are low when the transmitter is disabled. Writing a character in FLEX_US_THR while TXRDY is low has no effect and the written character is lost. Figure 47-6: 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 FLEX_US_THR TXRDY TXEMPTY  2017 Microchip Technology Inc. DS60001476B-page 1421 SAMA5D2 SERIES 47.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 FLEX_US_MR.MAN bit 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 47-7 illustrates this coding scheme. Figure 47-7: 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 predefined 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 FLEX_US_MAN.TX_PP field. The TX_PL field is used to configure the preamble length. Figure 47-8 illustrates and defines the valid patterns. To improve flexibility, the encoding scheme can be configured using the FLEX_US_MAN.TX_MPOL bit. If the TX_MPOL bit 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 bit 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. Figure 47-8: Preamble Patterns, Default Polarity Assumed Manchester encoded data Txd SFD DATA SFD DATA SFD DATA SFD DATA 8-bit "ALL_ONE" Preamble Manchester encoded data Txd 8-bit "ALL_ZERO" Preamble Manchester encoded data Txd 8-bit "ZERO_ONE" Preamble Manchester encoded data Txd 8-bit "ONE_ZERO" Preamble A start frame delimiter is to be configured using the FLEX_US_MR.ONEBIT bit. It consists of a user-defined pattern that indicates the beginning of a valid data. Figure 47-9 illustrates these patterns. If the start frame delimiter, also known as the start bit, is one bit, (ONEBIT = 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 = 0), a sequence of three 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 DS60001476B-page 1422  2017 Microchip Technology Inc. SAMA5D2 SERIES a half bit times, then a transition to logic zero for the second one and a half bit times. If the FLEX_US_MR.MODSYNC bit 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 bit can be immediately updated with a modified character located in memory. To enable this mode, the FLEX_US_MR.VAR_SYNC bit must be set. In this case, the FLEX_US_MR.MODSYNC bit is bypassed and the sync configuration is held in the FLEX_US_THR.TXSYNH bit. The USART character format is modified and includes sync information. Figure 47-9: Start Frame Delimiter Preamble Length is set to 0 SFD Manchester encoded data DATA Txd One bit start frame delimiter SFD Manchester encoded data DATA Txd SFD Manchester encoded data Command Sync start frame delimiter DATA Txd Data Sync start frame delimiter • 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 FLEX_US_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 47-10: Bit Resynchronization Oversampling 16x Clock RXD Sampling point Expected edge Synchro. Error 47.7.3.3 Synchro. Jump Tolerance Synchro. Jump Synchro. Error 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 FLEX_US_MR.OVER bit.  2017 Microchip Technology Inc. DS60001476B-page 1423 SAMA5D2 SERIES The receiver samples the RXD line. If the line is sampled during one half of a bit time to 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 = 0), a start is detected at the eighth sample to 0. Data bits, parity bit and stop bit are assumed to have a duration corresponding to 16 oversampling clock cycles. If the oversampling is 8 (OVER = 1), a start bit is detected at the fourth sample to 0. Data bits, parity bit and stop bit are assumed to have a duration corresponding to 8 oversampling clock cycles. 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 NBSTOP field, 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 47-11 and Figure 47-12 illustrate start detection and character reception when USART operates in Asynchronous mode. Figure 47-11: Asynchronous Start Detection Baud Rate Clock Sampling Clock (x16) RXD Sampling 1 2 3 4 5 6 7 8 1 2 3 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 D0 Sampling Start Detection RXD Sampling 1 Figure 47-12: 2 3 4 5 6 7 0 1 Start Rejection 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 47.7.3.4 D1 D2 D3 D4 D5 D6 D7 Parity Bit Stop Bit Manchester Decoder When the FLEX_US_MR.MAN bit is set, 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 transmitter side. Use the FLEX_US_MAN.RX_PL field 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 the FLEX_US_MAN.RX_MPOL bit. Depending on the desired application, the preamble pattern matching is to be defined via the FLEX_US_MAN.RX_PP field. See Figure 47-8 for available preamble patterns. DS60001476B-page 1424  2017 Microchip Technology Inc. SAMA5D2 SERIES Unlike preamble, the start frame delimiter is shared between Manchester Encoder and Decoder. So, if ONEBIT bit = 1, only a zero encoded Manchester can be detected as a valid start frame delimiter. If ONEBIT = 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 to zero, a start bit is detected. See Figure 47-13. The sample pulse rejection mechanism applies. The FLEX_US_MAN.RXIDLEV bit informs the USART of the receiver line idle state value (receiver line inactive). The user must define RXIDLEV to ensure reliable synchronization. By default, RXIDLEV is set to one (receiver line is at level 1 when there is no activity). Figure 47-13: 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 resynchronizes 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 47-14 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, the MANE flag in FLEX_US_CSR is raised. It is cleared by writing a one to FLEX_US_CR.RSTSTA. See Figure 47-15 for an example of Manchester error detection during the data phase. Figure 47-14: Preamble Pattern Mismatch Preamble Mismatch Manchester coding error Manchester encoded data Preamble Mismatch invalid pattern SFD Txd DATA Preamble Length is set to 8 Figure 47-15: 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  2017 Microchip Technology Inc. Manchester Coding Error detected DS60001476B-page 1425 SAMA5D2 SERIES When the start frame delimiter is a sync pattern (ONEBIT = 0), both command and data delimiter are supported. If a valid sync is detected, the received character is written as RXCHR field in the Receive Holding Register (FLEX_US_RHR) 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-to-one transition. 47.7.3.5 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 configuration in Figure 47-16. Figure 47-16: Manchester Encoded Characters RF Transmission Fup frequency carrier ASK/FSK upstream receiver Upstream transmitter Fdown frequency carrier LNA VCO RF filter Demod Control Serial Configuration Interface bi-dir line ASK/FSK downstream transmitter Downstream receiver Manchester decoder USART receiver Manchester encoder USART transmitter PA RF filter Mod VCO Control The USART peripheral is configured as a Manchester encoder/decoder. Looking at the downstream communication channel, Manchester encoded characters are serially sent to the RF transmitter. 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 47-17 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 47-18. 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. DS60001476B-page 1426  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-17: ASK Modulator Output 1 0 0 1 0 0 1 NRZ stream Manchester encoded data default polarity unipolar output Txd ASK Modulator Output Upstream Frequency F0 Figure 47-18: FSK Modulator Output 1 NRZ stream Manchester encoded data default polarity unipolar output Txd FSK Modulator Output Uptstream Frequencies [F0, F0+offset] 47.7.3.6 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 47-19 illustrates a character reception in Synchronous mode. Figure 47-19: 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 Stop Bit Parity Bit 47.7.3.7 Receiver Operations When a character reception is completed, it is transferred to the Receive Holding Register (FLEX_US_RHR) and the FLEX_US_CSR.RXRDY bit is raised. If a character is completed while the RXRDY is set, the Overrun Error (OVRE) bit is set. The last character is transferred into FLEX_US_RHR and overwrites the previous one. The OVRE bit is cleared by writing a one to Reset Status bit FLEX_US_CR.RSTSTA.  2017 Microchip Technology Inc. DS60001476B-page 1427 SAMA5D2 SERIES Figure 47-20: 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 FLEX_US_CR Read FLEX_US_RHR RXRDY OVRE 47.7.3.8 Parity The USART supports five parity modes that are selected by writing to the FLEX_US_MR.PAR field. The PAR field also enables the Multidrop mode (see Section 47.7.3.9 ”Multidrop Mode”). 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 to 0 if a number of 1s in the character data bit is even, and to 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 to 1 if a number of 1s in the character data bit is even, and to 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 to 1 for all characters. The receiver parity checker reports an error if the parity bit is sampled to 0. If the space parity is used, the parity generator of the transmitter drives the parity bit to 0 for all characters. The receiver parity checker reports an error if the parity bit is sampled to 1. If parity is disabled, the transmitter does not generate any parity bit and the receiver does not report any parity error. Table 47-9 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 set to 1 in the character value, the parity bit is set to 1 when the parity is odd, or configured to 0 when the parity is even. Table 47-9: Parity Bit Examples Character Hexadecimal Binary Parity Bit Parity Mode A 0x41 0100 0001 1 Odd A 0x41 0100 0001 0 Even A 0x41 0100 0001 1 Mark A 0x41 0100 0001 0 Space A 0x41 0100 0001 None None When the receiver detects a parity error, it sets the Parity Error bit FLEX_US_CSR.PARE. The PARE bit can be cleared by writing a one to the FLEX_US_CR.RSTSTA bit. Figure 47-21 illustrates the parity bit status setting and clearing. DS60001476B-page 1428  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-21: Parity Error Baud Rate Clock RXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Bad Stop Parity Bit Bit RSTSTA = 1 Write FLEX_US_CR PARE Parity Error Detect Time Flags Report Time RXRDY 47.7.3.9 Multidrop Mode If the value 0x6 or 0x07 is written to the FLEX_US_MR.PAR field, the USART runs in Multidrop mode. This mode differentiates the data characters and the address characters. Data are transmitted with the parity bit to 0 and addresses are transmitted with the parity bit to 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 a one is written to the FLEX_US_CR.SENDA bit. To handle parity error, the PARE bit is cleared by writing a one to the FLEX_US_CR.RSTSTA bit. The transmitter sends an address byte (parity bit set) when the FLEX_US_CR.SENDA bit is written to 1. In this case, the next byte written to FLEX_US_THR is transmitted as an address. Any character written in FLEX_US_THR when the SENDA command is not written is transmitted normally with parity to 0. 47.7.3.10 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 (FLEX_US_TTGR). When this field is written to 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 47-22, the behavior of the 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 to 0 during the timeguard transmission if a character has been written in FLEX_US_THR. TXEMPTY remains low until the timeguard transmission is completed as the timeguard is part of the current character being transmitted.  2017 Microchip Technology Inc. DS60001476B-page 1429 SAMA5D2 SERIES Figure 47-22: Timeguard Operations TG = 4 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 Write FLEX_US_THR TXRDY TXEMPTY Table 47-10 indicates the maximum length of a timeguard period that the transmitter can handle in relation to the function of the baud rate. Table 47-10: Maximum Timeguard Length Depending on Baud Rate Baud Rate (bit/s) Bit Time (µs) Timeguard (ms) 1,200 833 212.50 9,600 104 26.56 14,400 69.4 17.71 19,200 52.1 13.28 28,800 34.7 8.85 38,400 26 6.63 56,000 17.9 4.55 57,600 17.4 4.43 115,200 8.7 2.21 47.7.3.11 Receiver Timeout The Receiver Timeout provides support in handling variable-length frames. This feature detects an idle condition on the RXD line. When a timeout is detected, the FLEX_US_CSR.TIMEOUT bit rises and can generate an interrupt, thus indicating to the driver an end of frame. The timeout delay period (during which the receiver waits for a new character) is programmed in the TO field of the Receiver Timeout Register (FLEX_US_RTOR). If the TO field is written to 0, the Receiver Timeout is disabled and no timeout is detected. The FLEX_US_CSR.TIMEOUT bit 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 FLEX_US_CSR.TIMEOUT bit rises. Then, the user can either: • Stop the counter clock until a new character is received. This is performed by writing a ‘1’ to FLEX_US_CR.STTTO. In this case, the idle state on RXD before a new character is received does not provide a timeout. This prevents having to handle an interrupt before a character is received and enables 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 a ‘1’ to FLEX_US_CR.RETTO. In this case, the counter starts counting down immediately from the value TO. This generates a periodic interrupt so that a user timeout can be handled, for example when no key is pressed on a keyboard. Figure 47-23 shows the block diagram of the Receiver Timeout feature. DS60001476B-page 1430  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-23: Receiver Timeout Block Diagram TO Baud Rate Clock 1 D Clock Q 16-bit Value 16-bit Timeout Counter = STTTO Character Received Load Clear TIMEOUT 0 RETTO Table 47-11 gives the maximum timeout period for some standard baud rates. Table 47-11: Maximum Timeout Period Baud Rate (bit/s) Bit Time (µs) Timeout (ms) 600 1,667 109,225 1,200 833 54,613 2,400 417 27,306 4,800 208 13,653 9,600 104 6,827 14,400 69 4,551 19,200 52 3,413 28,800 35 2,276 38,400 26 1,704 56,000 18 1,170 57,600 17 1,138 200,000 5 328 47.7.3.12 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 FLEX_US_CSR.FRAME bit. 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 a one to the FLEX_US_CR.RSTSTA bit.  2017 Microchip Technology Inc. DS60001476B-page 1431 SAMA5D2 SERIES Figure 47-24: Framing Error Status Baud Rate Clock RXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit RSTSTA = 1 Write FLEX_US_CR FRAME RXRDY 47.7.3.13 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 to 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 setting the FLEX_US_CR.STTBRK bit. This can be done at any time, either while the transmitter is empty (no character in either the shift register or in FLEX_US_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 the Start Break command is requested, further Start Break commands are ignored until the end of the break is completed. The break condition is removed by setting the FLEX_US_CR.STPBRK bit. If the Stop Break command 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 Start Break and Stop Break commands are processed only if the FLEX_US_CSR.TXRDY bit = 1 and the start of the break condition clears the TXRDY and TXEMPTY bits as if a character was processed. Setting both the FLEX_US_CR.STTBRK and FLEX_US_CR.STPBRK bits can lead to an unpredictable result. All Stop Break commands requested without a previous Start Break command are ignored. A byte written into the Transmit Holding register while a break is pending, but not started, is ignored. 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 47-25 illustrates the effect of both the Start Break (STTBRK) and Stop Break (STPBRK) commands on the TXD line. DS60001476B-page 1432  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-25: Break Transmission Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit STTBRK = 1 Break Transmission End of Break STPBRK = 1 Write FLEX_US_CR TXRDY TXEMPTY 47.7.3.14 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 to 0x00, but FRAME remains low. When the low stop bit is detected, the receiver asserts the FLEX_US_CSR.RXBRK bit. FLEX_US_CSR.RXBRK may be cleared by setting the FLEX_US_CR.RSTSTA bit. An end of receive break is detected by a high level for at least 2/16ths 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. 47.7.3.15 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 47-26. Figure 47-26: Connection with a Remote Device for Hardware Handshaking USART Remote Device TXD RXD RXD TXD CTS RTS RTS CTS Setting the USART to operate with hardware handshaking is performed by writing the FLEX_US_MR.USART_MODE field 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 DMAC channel for reception. The transmitter can handle hardware handshaking in any case.  2017 Microchip Technology Inc. DS60001476B-page 1433 SAMA5D2 SERIES Figure 47-27: RTS Line Software Control when FLEX_US_MR.USART_MODE = 2 RXD Write FLEX_US_CR.RTSDIS Write FLEX_US_CR.RTSEN RTS Figure 47-28 shows how the transmitter operates if hardware handshaking is enabled. The CTS pin disables the transmitter. If a character is being processed, 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 47-28: Transmitter Behavior when Operating with Hardware Handshaking CTS TXD If USART FIFOs are enabled (bit FLEX_US_CR.FIFOEN), the RTS pin can be controlled by the USART Receive FIFO thresholds. The RTS pin control through Receive FIFO thresholds can be activated with the FLEX_US_FMR.FRTSC bit. Once activated, the RTS pin will be controlled by Receive FIFO thresholds, set to level 1 each time RXFTHRES is reached and set to level ‘0’ each time RXFTHRES2 is reached (and RXFTHRES is not reached). Figure 47-29: Receiver Behavior When FIFO Enabled and FRTSC Set to ‘1’ RXD RXDIS = 1 Read FLEX_US_RHR RXEN = 1 Write FLEX_US_CR RTS above/equal RXFTHRES RXFTHRES = 3 below/equal RXFTHRES2 RXFTHRES2 = 1 RXFL Note: 47.7.4 0 1 2 3 2 1 2 In this mode, RXFTHRES must be > RXFTHRES2. 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 FLEX_US_MR.USART_MODE field to the value 0x4 for protocol T = 0 and to the value 0x6 for protocol T = 1. DS60001476B-page 1434  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.7.4.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 Figure 47.7.1.1). The USART connects to a smart card as shown in Figure 47-30. The TXD line becomes bidirectional and the baud rate generator feeds the ISO7816 clock on the SCK pin. 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 47-30: Connection of a Smart Card to the USART USART CLK SCK I/O TXD Smart Card 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. See Section 47.10.6 ”USART Mode Register” and PAR: Parity Type. 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. 47.7.4.2 Protocol T = 0 In T = 0 protocol, a character is made up of 1 start bit, 8 data bits, 1 parity bit and 1 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 47-31. If a parity error is detected by the receiver, it drives the I/O line to 0 during the guard time, as shown in Figure 47-32. 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 (FLEX_US_RHR). It appropriately sets the PARE bit in the Status Register (FLEX_US_CSR) so that the software can handle the error. Figure 47-31: T = 0 Protocol without Parity Error Baud Rate Clock RXD Start Bit  2017 Microchip Technology Inc. D0 D1 D2 D3 D4 D5 D6 D7 Parity Guard Guard Next Bit Time 1 Time 2 Start Bit DS60001476B-page 1435 SAMA5D2 SERIES Figure 47-32: T = 0 Protocol with Parity Error Baud Rate Clock Error I/O Start Bit D0 D1 D2 D3 D4 D5 D6 D7 Parity Guard Bit Time 1 Guard Start Time 2 Bit D0 D1 Repetition • Receive Error Counter The USART receiver also records the total number of errors. This can be read in the Number of Error (FLEX_US_NER) register. The NB_ERRORS field can record up to 255 errors. Reading FLEX_US_NER automatically clears the NB_ERRORS field. • Receive NACK Inhibit The USART can be configured to inhibit an error. This is done by writing a ‘1’ to FLEX_US_MR.INACK. In this case, no error signal is driven on the I/O line even if a parity bit is detected. Moreover, if INACK = 1, the erroneous received character is stored in the Receive Holding register as if no error occurred, and the RXRDY bit rises. • 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 FLEX_US_MR.MAX_ITERATION field 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, and the last repeated character is not acknowledged, the FLEX_US_CSR.ITER bit is set. If the repetition of the character is acknowledged by the receiver, the repetitions are stopped and the iteration counter is cleared. The FLEX_US_CSR.ITER bit can be cleared by writing the FLEX_US_CR.RSTIT bit to 1. • 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 FLEX_US_MR.DSNACK bit. The maximum number of NACKs transmitted is programmed in the MAX_ITERATION field. As soon as MAX_ITERATION is reached, no error signal is driven on the I/O line and the FLEX_US_CSR.ITER bit is set. 47.7.4.3 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 FLEX_US_CSR.PARE bit. DS60001476B-page 1436  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.7.5 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 47-33. The modulator and demodulator are compliant with the IrDA specification version 1.1 and support data transfer speeds ranging from 2.4 kbit/s to 115.2 kbit/s. The USART IrDA mode is enabled by setting the FLEX_US_MR.USART_MODE field to the value 0x8. The IrDA Filter Register (FLEX_US_IF) 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 47-33: Connection to IrDA Transceivers USART IrDA Transceivers Receiver Demodulator Transmitter Modulator RXD RX TXD TX The receiver and the transmitter must be enabled or disabled according to the direction of the transmission to be managed. To receive IrDA signals, the following needs to be done: • Disable TX and Enable RX • Configure the TXD pin as PIO and set it as an output to 0 (to avoid LED transmission). Disable the internal pullup (better for power consumption). • Receive data 47.7.5.1 IrDA Modulation For baud rates up to and including 115.2 kbit/s, 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 47-12. Table 47-12: IrDA Pulse Duration Baud Rate Pulse Duration (3/16) 2.4 kbit/s 78.13 µs 9.6 kbit/s 19.53 µs 19.2 kbit/s 9.77 µs 38.4 kbit/s 4.88 µs 57.6 kbit/s 3.26 µs 115.2 kbit/s 1.63 µs Figure 47-34 shows an example of character transmission.  2017 Microchip Technology Inc. DS60001476B-page 1437 SAMA5D2 SERIES Figure 47-34: IrDA Modulation Start Bit Transmitter Output Stop Bit Data Bits 0 1 0 1 0 0 1 1 0 1 TXD Bit Period 47.7.5.2 3/16 Bit Period IrDA Baud Rate Table 47-13 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 47-13: IrDA Baud Rate Error Peripheral Clock Baud Rate (bit/s) CD Baud Rate Error Pulse Time (µs) 3,686,400 115,200 2 0.00% 1.63 20,000,000 115,200 11 1.38% 1.63 32,768,000 115,200 18 1.25% 1.63 40,000,000 115,200 22 1.38% 1.63 3,686,400 57,600 4 0.00% 3.26 20,000,000 57,600 22 1.38% 3.26 32,768,000 57,600 36 1.25% 3.26 40,000,000 57,600 43 0.93% 3.26 3,686,400 38,400 6 0.00% 4.88 20,000,000 38,400 33 1.38% 4.88 32,768,000 38,400 53 0.63% 4.88 40,000,000 38,400 65 0.16% 4.88 3,686,400 19,200 12 0.00% 9.77 20,000,000 19,200 65 0.16% 9.77 32,768,000 19,200 107 0.31% 9.77 40,000,000 19,200 130 0.16% 9.77 3,686,400 9,600 24 0.00% 19.53 20,000,000 9,600 130 0.16% 19.53 32,768,000 9,600 213 0.16% 19.53 40,000,000 9,600 260 0.16% 19.53 3,686,400 2,400 96 0.00% 78.13 20,000,000 2,400 521 0.03% 78.13 32,768,000 2,400 853 0.04% 78.13 47.7.5.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 FLEX_US_IF. When a falling edge is detected on the RXD pin, the Filter Counter starts counting down at the peripheral clock speed. If a rising edge is detected on the RXD pin, the counter stops and is reloaded with FLEX_US_IF. If no rising edge is detected when the counter reaches 0, the input of the receiver is driven low during one bit time. DS60001476B-page 1438  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-35 illustrates the operations of the IrDA demodulator. Figure 47-35: IrDA Demodulator Operations MCK RXD Counter Value Receiver Input 6 5 4 3 Pulse Rejected 2 6 6 5 4 3 2 1 0 Pulse Accepted The programmed value in the FLEX_US_IF register must always meet the following criteria: tperipheral clock × (IRDA_FILTER + 3) < 1.41 µs As the IrDA mode uses the same logic as the ISO7816, note that the FLEX_US_FIDI.FI_DI_RATIO field must be set to a value higher than 0 to make sure IrDA communications operate correctly. 47.7.6 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 an RS485 bus is shown in Figure 47-36. Figure 47-36: Typical Connection to an RS485 Bus USART RXD TXD Differential Bus RTS The USART is set in RS485 mode by writing the value 0x1 to the FLEX_US_MR.USART_MODE field. 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 47-37 gives an example of the RTS waveform during a character transmission when the timeguard is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1439 SAMA5D2 SERIES Figure 47-37: Example of RTS Drive with Timeguard TG = 4 1 Baud Rate Clock TXD Start D0 Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit RTS Write FLEX_US_THR TXRDY TXEMPTY 47.7.7 USART Comparison Function on Received Character The CMP flag in FLEX_US_CSR is set when the received character matches the conditions programmed in FLEX_US_CMPR. The CMP flag is set as soon as FLEX_US_RHR is loaded with the new received character. The CMP flag is cleared by writing a one to FLEX_US_CR.RSTSTA. FLEX_US_CMPR (see Section 47.10.34 ”USART Comparison Register”) can be programmed to provide different comparison methods: • If VAL1 equals VAL2, then the comparison is performed on a single value and the flag is set to 1 if the received character equals VAL1. • If VAL1 is strictly lower than VAL2, then any value between VAL1 and VAL2 sets the CMP flag. • If VAL1 is strictly higher than VAL2, then the flag CMP is set to 1 if any received character equals VAL1 or VAL2. When the FLEX_US_CMPR.CMPMODE bit is set to FLAG_ONLY (value 0), all received data are loaded in FLEX_US_RHR and the CMP flag provides the status of the comparison result. By programming the START_CONDITION.CMPMODE bit (value 1), the comparison function result triggers the start of the loading of FLEX_US_RHR (see Figure 47-38). The trigger condition exists as soon as the received character value matches the condition defined by the programming of VAL1, VAL2 and CMPPAR in FLEX_US_CMPR. The comparison trigger event is restarted by writing a 1 to the FLEX_US_CR.REQCLR bit. The value programmed in the VAL1 and VAL2 fields must not exceed the maximum value of the received character (see CHRL field in USART Mode Register (FLEX_US_MR)). DS60001476B-page 1440  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-38: Receive Holding Register Management CMPMODE = 1, VAL1 = VAL2 = 0x06 Peripheral Clock RXD 0x0F 0x06 0xF0 0x08 0x06 RXRDY rising enabled RXRDY Write REQCLR 0x0F RHR 47.7.8 0x06 0xF0 0x08 0x06 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 (SCK): 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 bit rates. The SCK line cycles once for each bit that is transmitted. • Slave Select (NSS): This control line allows the master to select or deselect the slave.  2017 Microchip Technology Inc. DS60001476B-page 1441 SAMA5D2 SERIES 47.7.8.1 Modes of Operation The USART can operate in SPI Master mode or in SPI Slave mode. Operation in SPI Master mode is programmed by writing 0xE to the FLEX_US_MR.USART_MODE field. 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 SCK line is driven by the output pin SCK The NSS line is driven by the output pin RTS Operation in SPI Slave mode is programmed by writing to 0xF the FLEX_US_MR.USART_MODE field. 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 SCK line drives the input pin SCK The NSS line drives the input pin CTS In order to avoid an unpredictable 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). (See Section 47.7.8.4 ”Receiver and Transmitter Control”.) 47.7.8.2 Bit Rate In SPI mode, the bit rate generator operates in the same way as in USART Synchronous mode. See Section 47.7.1.3 ”Baud Rate in Synchronous Mode or SPI Mode”. However, some restrictions apply: In SPI Master mode: • The external clock SCK must not be selected (USCLKS ≠ 0x3), and the FLEX_US_MR.CLKO bit must be set in order to generate correctly the serial clock on the SCK pin. • To ensure a correct behavior of the receiver and the transmitter, the value programmed in CD must be ≥ 6. • If the divided peripheral clock is selected, the value programmed in CD must be even to ensure a 50:50 mark/space ratio on the SCK pin; this value can be odd if the peripheral clock is selected. In SPI Slave mode: • The external clock (SCK) selection is forced regardless of the value of the FLEX_US_MR.USCLKS field. Likewise, the value written in FLEX_US_BRGR has no effect, because the clock is provided directly by the signal on the USART SCK pin. • To ensure a correct behavior of the receiver and the transmitter, the external clock (SCK) frequency must be at least six times lower than the system clock. 47.7.8.3 Data Transfer Up to nine 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 MODE9 bit in FLEX_US_MR. The nine bits are selected by setting the MODE9 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 FLEX_US_MR.CPOL bit. The clock phase is programmed with the CPHA bit. These two parameters determine the edges of the clock signal upon which data are 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 47-14: SPI Bus Protocol Mode SPI Bus Protocol Mode CPOL CPHA 0 0 1 1 0 0 2 1 1 3 1 0 DS60001476B-page 1442  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-39: SPI Transfer Format (CPHA = 1, 8 bits per transfer) SCK cycle (for reference) 1 2 3 4 6 5 7 8 SCK (CPOL = 0) SCK (CPOL = 1) MOSI SPI Master ->TXD SPI Slave -> RXD MSB MISO SPI Master ->RXD SPI Slave -> TXD MSB 6 5 4 3 2 1 LSB 6 5 4 3 2 1 LSB NSS SPI Master -> RTS SPI Slave -> CTS Figure 47-40: SPI Transfer Format (CPHA = 0, 8 bits per transfer) SCK cycle (for reference) 1 2 3 4 5 8 7 6 SCK (CPOL = 0) SCK (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 47.7.8.4 Receiver and Transmitter Control See Section 47.7.2 ”Receiver and Transmitter Control”. 47.7.8.5 Character Transmission The characters are sent by writing in the Transmit Holding Register (FLEX_US_THR). An additional condition for transmitting a character can be added when the USART is configured in SPI Master mode. In the “USART Mode Register (SPI_MODE)” (FLEX_US_MR), the value configured on the WRDBT bit can prevent any character transmission (even if FLEX_US_THR has been written) while the receiver  2017 Microchip Technology Inc. DS60001476B-page 1443 SAMA5D2 SERIES side is not ready (character not read). When WRDBT = 0, the character is transmitted whatever the receiver status. If WRDBT = 1, the transmitter waits for the Receive Holding Register (FLEX_US_RHR) to be read before transmitting the character (RXRDY flag cleared), thus preventing any overflow (character loss) on the receiver side. The chip select line is deasserted for a period equivalent to 3 bits between the transmission of two data. The transmitter reports two status bits in FLEX_US_CSR: TXRDY (Transmitter Ready), which indicates that FLEX_US_THR is empty and TXEMPTY, which indicates that all the characters written in FLEX_US_THR have been processed. When the current character processing is completed, the last character written in FLEX_US_THR is transferred into the shift register of the transmitter and FLEX_US_THR is emptied, and thus TXRDY rises. Both the TXRDY and the TXEMPTY bits are low when the transmitter is disabled. Writing a character in FLEX_US_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 FLEX_US_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 a one to the FLEX_US_CR.RSTSTA bit. In SPI Master mode, the slave select line (NSS) is asserted at low level one tbit (tbit being the nominal time required to transmit a bit) before the transmission of the MSB bit and released at high level one 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 three tbit 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 a one to the FLEX_US_CR.RTSEN bit. The slave select line (NSS) can be released at high level only by writing a one to the FLEX_US_CR.RTSDIS bit (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 one tbit before the first serial clock cycle corresponding to the MSB bit. 47.7.8.6 Character Reception When a character reception is completed, it is transferred to the Receive Holding Register (FLEX_US_RHR) and the RXRDY bit in the Status Register (FLEX_US_CSR) rises. If a character is completed while RXRDY is set, the OVRE (Overrun Error) bit is set. The last character is transferred into FLEX_US_RHR and overwrites the previous one. The OVRE bit is cleared by writing a one to the FLEX_US_CR.RSTSTA bit. To ensure correct behavior of the receiver in SPI Slave mode, the master device sending the frame must ensure a minimum delay of one 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 one tbit before the first serial clock cycle corresponding to the MSB bit. 47.7.8.7 Receiver Timeout Because the receiver bit rate clock is active only during data transfers in SPI mode, a receiver timeout is impossible in this mode, whatever the timeout value is in field FLEX_US_RTOR.TO. 47.7.9 LIN Mode The LIN mode provides master node and slave node connectivity on a LIN bus. The LIN (Local Interconnect Network) is a serial communication protocol which efficiently supports the control of mechatronic nodes in distributed automotive applications. The main properties of the LIN bus are: • Single master/multiple slaves concept • Low-cost silicon implementation based on common UART/SCI interface hardware, an equivalent in software, or as a pure state machine. • Self synchronization without quartz or ceramic resonator in the slave nodes • Deterministic signal transmission • Low cost single-wire implementation • Speed up to 20 kbit/s LIN provides cost efficient bus communication where the bandwidth and versatility of CAN are not required. The LIN mode enables processing LIN frames with a minimum of action from the microprocessor. 47.7.9.1 Modes of Operation The USART can act either as a LIN master node or as a LIN slave node. DS60001476B-page 1444  2017 Microchip Technology Inc. SAMA5D2 SERIES The node configuration is chosen by setting the USART_MODE field in the USART Mode Register (FLEX_US_MR): • LIN master node (USART_MODE = 0xA) • LIN slave node (USART_MODE = 0xB) In order to avoid unpredictable behavior, any change of the LIN node configuration must be followed by a software reset of the transmitter and of the receiver (except the initial node configuration after a hardware reset). (See Section 47.7.9.3 ”Receiver and Transmitter Control”.) 47.7.9.2 Baud Rate Configuration See Section 47.7.1.1 ”Baud Rate in Asynchronous Mode”. • LIN master node: The baud rate is configured in FLEX_US_BRGR. • LIN slave node: The initial baud rate is configured in FLEX_US_BRGR. This configuration is automatically copied in the LIN Baud Rate Register (FLEX_US_LINBRR) when writing FLEX_US_BRGR. After the synchronization procedure, the baud rate is updated in FLEX_US_LINBRR. 47.7.9.3 Receiver and Transmitter Control See Section 47.7.2 ”Receiver and Transmitter Control”. 47.7.9.4 Character Transmission See Section 47.7.3.1 ”Transmitter Operations”. 47.7.9.5 Character Reception See Section 47.7.3.7 ”Receiver Operations”. 47.7.9.6 Header Transmission (Master Node Configuration) All the LIN Frames start with a header which is sent by the master node and consists of a Synch Break Field, Synch Field and Identifier Field. So in master node configuration, the frame handling starts with the sending of the header. The header is transmitted as soon as the identifier is written in the LIN Identifier Register (FLEX_US_LINIR). At this moment the flag TXRDY falls. The Break Field, the Synch Field and the Identifier Field are sent automatically one after the other. The Break Field consists of 13 dominant bits and 1 recessive bit, the Synch Field is the character 0x55 and the Identifier corresponds to the character written in the LIN Identifier Register (FLEX_US_LINIR). The Identifier parity bits can be automatically computed and sent (see Section 47.7.9.9 “Identifier Parity”). The flag TXRDY rises when the identifier character is transferred into the shift register of the transmitter. As soon as the Synch Break Field is transmitted, the FLEX_US_CSR.LINBK flag bit is set. Likewise, as soon as the Identifier Field is sent, the FLEX_US_CSR.LINID flag bit is set. These flags are reset by writing a one to the FLEX_US_CR.RSTSTA bit.  2017 Microchip Technology Inc. DS60001476B-page 1445 SAMA5D2 SERIES Figure 47-41: Header Transmission Baud Rate Clock TXD Break Field 13 dominant bits (at 0) Write FLEX_US_LINIR FLEX_US_LINIR Break Delimiter 1 recessive bit (at 1) Start 1 Bit 0 1 0 1 0 Synch Byte = 0x55 1 0 Stop Stop Start ID0 ID1 ID2 ID3 ID4 ID5 ID6 ID7 Bit Bit Bit ID TXRDY LINBK in FLEX_US_CSR LINID in FLEX_US_CSR Write RSTSTA=1 in FLEX_US_CR 47.7.9.7 Header Reception (Slave Node Configuration) All the LIN frames start with a header which is sent by the master node and consists of a Synch Break Field, Synch Field and Identifier Field. In slave node configuration, the frame handling starts with the reception of the header. The USART uses a break detection threshold of 11 nominal bit times at the actual baud rate. At any time, if 11 consecutive recessive bits are detected on the bus, the USART detects a Break Field. As long as a Break Field has not been detected, the USART stays idle and the received data are not taken in account. When a Break Field has been detected, the FLEX_US_CSR.LINBK flag is set and the USART expects the Synch Field character to be 0x55. This field is used to update the actual baud rate in order to remain synchronized (see Section 47.7.9.8 “Slave Node Synchronization”). If the received Synch character is not 0x55, an Inconsistent Synch Field error is generated (see Section 47.7.9.14 “LIN Errors”). After receiving the Synch Field, the USART expects to receive the Identifier Field. When the Identifier Field has been received, the FLEX_US_CSR.LINID flag bit is set. At this moment, the IDCHR field in the LIN Identifier Register (FLEX_US_LINIR) is updated with the received character. The Identifier parity bits can be automatically computed and checked (see Section 47.7.9.9 “Identifier Parity”). If the header is not entirely received within the time given by the maximum length of the header tHeader_Maximum, the FLEX_US_CSR.LINHTE error flag bit is set. The flag bits LINID, LINBK and LINHTE are reset by writing a one to the FLEX_US_CR.RSTSTA bit. DS60001476B-page 1446  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-42: Header Reception Baud Rate Clock RXD Break Field 13 dominant bits (at 0) Break Delimiter 1 recessive bit (at 1) Start 1 Bit 0 1 0 1 0 Synch Byte = 0x55 1 0 Stop Start Stop ID0 ID1 ID2 ID3 ID4 ID5 ID6 ID7 Bit Bit Bit LINBK LINID FLEX_US_LINIR Write RSTSTA=1 in FLEX_US_CR 47.7.9.8 Slave Node Synchronization The synchronization is done only in slave node configuration. The procedure is based on time measurement between the falling edges of the Synch Field. The falling edges are available in distances of 2, 4, 6 and 8 bit times. Figure 47-43: Synch Field Synch Field 8 tbit 2 tbit 2 tbit 2 tbit 2 tbit Start bit Stop bit The time measurement is made by a 19-bit counter driven by the sampling clock (see Section 47.7.1 “Baud Rate Generator”). When the start bit of the Synch Field is detected, the counter is reset. Then during the next eight tbit of the Synch Field, the counter is incremented. At the end of these eight tbit, the counter is stopped. At this moment, the 16 most significant bits of the counter (value divided by 8) give the new clock divider (LINCD) and the 3 least significant bits of this value (the remainder) give the new fractional part (LINFP). Once the Synch Field has been entirely received, the clock divider (LINCD) and the fractional part (LINFP) are updated in the LIN Baud Rate Register (FLEX_US_LINBRR) with the computed values, if the Synchronization is not disabled by the SYNCDIS bit in the LIN Mode Register (FLEX_US_LINMR). After reception of the Synch Field: • If it appears that the computed baud rate deviation compared to the initial baud rate is superior to the maximum tolerance FTol_Unsynch (±15%), then the clock divider (LINCD) and the fractional part (LINFP) are not updated, and the FLEX_US_CSR.LINSTE error flag bit is set. • If it appears that the sampled Synch character is not equal to 0x55, then the clock divider (LINCD) and the fractional part (LINFP) are not updated, and the FLEX_US_CSR.LINISFE error flag bit is set. Flags LINSTE and LINISFE are reset by writing a one to the FLEX_US_CR.RSTSTA bit.  2017 Microchip Technology Inc. DS60001476B-page 1447 SAMA5D2 SERIES Figure 47-44: Slave Node Synchronization Baud Rate Clock RXD Break Field 13 dominant bits (at 0) Break Delimiter 1 recessive bit (at 1) Start 1 Bit 0 1 0 1 0 Synch Byte = 0x55 1 0 Stop Start Stop ID0 ID1 ID2 ID3 ID4 ID5 ID6 ID7 Bit Bit Bit LINIDRX Reset Synchro Counter 000_0011_0001_0110_1101 FLEX_US_BRGR Clock Divider (CD) Initial CD FLEX_US_BRGR Fractional Part (FP) Initial FP FLEX_US_LINBRR Clock Divider (CD) Initial CD 0000_0110_0010_1101 FLEX_US_LINBRR Fractional Part (FP) Initial FP 101 The synchronization accuracy depends on several parameters: • The nominal clock frequency (fNom) (the theoretical slave node clock frequency) • The baud rate • The oversampling (OVER = 0 => 16X or OVER = 1 => 8X) The following formula is used to compute the deviation of the slave bit rate relative to the master bit rate after synchronization (fSLAVE is the real slave node clock frequency). [ α × 8 × ( 2 – Over ) + β ] × Baud rate Baud rate deviation =  100 × ---------------------------------------------------------------------------------------------- %   8 × f SLAVE    [ α × 8 × ( 2 – Over ) + β ] × Baud rate Baud rate deviation =  100 × ---------------------------------------------------------------------------------------------- % f TOL_UNSYNCH   8 ×  ------------------------------------- × f Nom     100 – 0.5 ≤ α ≤ +0.5 -1 < β < +1 fTOL_UNSYNCH is the deviation of the real slave node clock from the nominal clock frequency. The LIN Standard imposes that it must not exceed ±15%. The LIN Standard imposes also that for communication between two nodes, their bit rate must not differ by more than ±2%. This means that the baud rate deviation must not exceed ±1%. Therefore, a minimum value for the nominal clock frequency can be computed as follows:    [ 0.5 × 8 × ( 2 – Over ) + 1 ] × Baud rate f Nom ( min ) =  100 × -------------------------------------------------------------------------------------------------- Hz – 15   8 ×  ---------- + 1 × 1%    100  Examples: • • • • Baud rate = 20 kbit/s, OVER = 0 (Oversampling 16X) => fNom(min) = 2.64 MHz Baud rate = 20 kbit/s, OVER = 1 (Oversampling 8X) => fNom(min) = 1.47 MHz Baud rate = 1 kbit/s, OVER = 0 (Oversampling 16X) => fNom(min) = 132 kHz Baud rate = 1 kbit/s, OVER = 1 (Oversampling 8X) => fNom(min) = 74 kHz DS60001476B-page 1448  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.7.9.9 Identifier Parity A protected identifier consists of two subfields: the identifier and the identifier parity. Bits 0 to 5 are assigned to the identifier, and bits 6 and 7 are assigned to the parity. The USART interface can generate/check these parity bits, but this feature can also be disabled. The user can choose between two modes via the FLEX_US_LINMR.PARDIS bit: • PARDIS = 0: - During header transmission, the parity bits are computed and sent with the six least significant bits of the IDCHR field of the LIN Identifier Register (FLEX_US_LINIR). Bits 6 and 7 of this register are discarded. - During header reception, the parity bits of the identifier are checked. If the parity bits are wrong, an Identifier Parity error occurs (see Section 47.7.3.8 “Parity”). Only the six least significant bits of the IDCHR field are updated with the received Identifier. Bits 6 and 7 are stuck to 0. • PARDIS = 1: - During header transmission, all the bits of the IDCHR field of the LIN Identifier Register (FLEX_US_LINIR) are sent on the bus. - During header reception, all the bits of the IDCHR field are updated with the received Identifier.  2017 Microchip Technology Inc. DS60001476B-page 1449 SAMA5D2 SERIES 47.7.9.10 Node Action Depending on the identifier, the node is affected—or not—by the LIN response. Consequently, after sending or receiving the identifier, the USART must be configured. There are three possible configurations: • PUBLISH: the node sends the response. • SUBSCRIBE: the node receives the response. • IGNORE: the node is not concerned by the response, it does not send and does not receive the response. This configuration is made by the LIN Node Action (NACT) field in FLEX_US_LINMR (see Section 47.10.31 “USART LIN Mode Register”). Example: a LIN cluster that contains a master and two slaves: • Data transfer from the master to slave 1 and to slave 2: NACT(master) = PUBLISH NACT(slave 1) = SUBSCRIBE NACT(slave 2) = SUBSCRIBE • Data transfer from the master to slave 1 only: NACT(master) = PUBLISH NACT(slave 1) = SUBSCRIBE NACT(slave 2) = IGNORE • Data transfer from slave 1 to the master: NACT(master) = SUBSCRIBE NACT(slave 1) = PUBLISH NACT(slave 2) = IGNORE • Data transfer from slave 1 to slave 2: NACT(master) = IGNORE NACT(slave 1) = PUBLISH NACT(slave 2) = SUBSCRIBE • Data transfer from slave 2 to the master and to slave 1: NACT(master) = SUBSCRIBE NACT(slave 1) = SUBSCRIBE NACT(slave 2) = PUBLISH 47.7.9.11 Response Data Length The LIN response data length is the number of data fields (bytes) of the response excluding the checksum. The response data length can either be configured by the user or be defined automatically by bits 4 and 5 of the Identifier (compatibility to LIN Specification 1.1). The user can choose between these two modes by the FLEX_US_LINMR.DLM bit: • DLM = 0: The response data length is configured by the user via the FLEX_US_LINMR.DLC field. The response data length is equal to (DLC + 1) bytes. DLC can be programmed from 0 to 255, so the response can contain from 1 data byte up to 256 data bytes. • DLM = 1: The response data length is defined by the Identifier (IDCHR in FLEX_US_LINIR) according to the table below. The FLEX_US_LINMR.DLC field is discarded. The response can contain 2 or 4 or 8 data bytes. DS60001476B-page 1450  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 47-15: Response Data Length if DLM = 1 IDCHR[5] IDCHR[4] Response Data Length (bytes) 0 0 2 0 1 2 1 0 4 1 1 8 Figure 47-45: Response Data Length User configuration: 1–256 data fields (DLC+1) Identifier configuration: 2/4/8 data fields Sync Break 47.7.9.12 Sync Field Identifier Field Data Field Data Field Data Field Data Field Checksum Field Checksum The last field of a frame is the checksum. The checksum contains the inverted 8- bit sum with carry, over all data bytes or all data bytes and the protected identifier. Checksum calculation over the data bytes only is called classic checksum and it is used for communication with LIN 1.3 slaves. Checksum calculation over the data bytes and the protected identifier byte is called enhanced checksum and it is used for communication with LIN 2.0 slaves. The USART can be configured to: • Send/Check an Enhanced checksum automatically (CHKDIS = 0 & CHKTYP = 0) • Send/Check a Classic checksum automatically (CHKDIS = 0 & CHKTYP = 1) • Not send/check a checksum (CHKDIS = 1) This configuration is made by the Checksum Type (CHKTYP) and Checksum Disable (CHKDIS) bits of FLEX_US_LINMR. If the checksum feature is disabled, the user can send it manually all the same, by considering the checksum as a normal data byte and by adding 1 to the response data length (see Section 47.7.9.11 “Response Data Length”). 47.7.9.13 Frame Slot Mode This mode is useful only for master nodes. It respects the following rule: each frame slot shall be longer than or equal to tFrame_Maximum. If the Frame Slot mode is enabled (FSDIS = 0) and a frame transfer has been completed, the TXRDY flag is set again only after tFrame_Maximum delay, from the start of frame. So the master node cannot send a new header if the frame slot duration of the previous frame is inferior to tFrame_Maximum. If the Frame Slot mode is disabled (FSDIS = 1) and a frame transfer has been completed, the TXRDY flag is set again immediately. The tFrame_Maximum is calculated as follows: If the Checksum is sent (CHKDIS = 0): • • • • • tHeader_Nominal = 34 × tbit tResponse_Nominal = 10 × (NData + 1) × tbit tFrame_Maximum = 1.4 × (tHeader_Nominal + tResponse_Nominal + 1)(1) tFrame_Maximum = 1.4 × (34 + 10 × (DLC + 1 + 1) + 1) × tbit tFrame_Maximum = (77 + 14 × DLC) × tbit If the Checksum is not sent (CHKDIS = 1): • • • • tHeader_Nominal = 34 × tbit tResponse_Nominal = 10 × NData × tbit tFrame_Maximum = 1.4 × (tHeader_Nominal + tResponse_Nominal + 1)(1) tFrame_Maximum = 1.4 × (34 + 10 × (DLC + 1) + 1) × tbit  2017 Microchip Technology Inc. DS60001476B-page 1451 SAMA5D2 SERIES • tFrame_Maximum = (63 + 14 × DLC) × tbit Note 1: The term “+1” leads to an integer result for tFrame_Maximum (LIN Specification 1.3). Figure 47-46: Frame Slot Mode Frame slot = tFrame_Maximum Frame Header Break Synch Data3 Interframe space Response space Response Data 1 Protected Identifier Data N-1 Data N Checksum TXRDY Frame Slot Mode Frame Slot Mode Disabled Enabled Write FLEX_US_LINID Write FLEX_US_THR Data 1 Data 2 Data 3 Data N LINTC 47.7.9.14 LIN Errors • Bit Error This error is generated in master of slave node configuration, when the USART is transmitting and if the transmitted value on the Tx line is different from the value sampled on the Rx line. If a bit error is detected, the transmission is aborted at the next byte border. This error is reported by the FLEX_US_CSR.LINBE flag. • Inconsistent Synch Field Error This error is generated in slave node configuration, if the Synch Field character received is other than 0x55. This error is reported by the FLEX_US_CSR.LINISFE flag. • Identifier Parity Error This error is generated in slave node configuration, if the parity of the identifier is wrong. This error can be generated only if the parity feature is enabled (PARDIS = 0). This error is reported by the FLEX_US_CSR.LINIPE flag. • Checksum Error This error is generated in master of slave node configuration, if the received checksum is wrong. This flag can be set to 1 only if the checksum feature is enabled (CHKDIS = 0). This error is reported by the FLEX_US_CSR.LINCE flag. • Slave Not Responding Error This error is generated in master of slave node configuration, when the USART expects a response from another node (NACT = SUBSCRIBE) but no valid message appears on the bus within the time given by the maximum length of the message frame, tFrame_Maximum (see Section 47.7.9.13 “Frame Slot Mode”). This error is disabled if the USART does not expect any message (NACT = PUBLISH or NACT = IGNORE). This error is reported by the FLEX_US_CSR.LINSNRE. • Synch Tolerance Error This error is generated in slave node configuration if, after the clock synchronization procedure, it appears that the computed baud rate deviation compared to the initial baud rate is superior to the maximum tolerance FTol_Unsynch (±15%). This error is reported by the FLEX_US_CSR.LINSTE flag. • Header Timeout Error This error is generated in slave node configuration, if the Header is not entirely received within the time given by the maximum length of the Header, tHeader_Maximum. DS60001476B-page 1452  2017 Microchip Technology Inc. SAMA5D2 SERIES This error is reported by the FLEX_US_CSR.LINHTE flag. 47.7.9.15 • • • • • • • LIN Frame Handling Master Node Configuration Write FLEX_US_CR.TXEN and FLEX_US_CR.RXEN to enable both the transmitter and the receiver. Write FLEX_US_MR.USART_MODE to select the LIN mode and the master node configuration. Write FLEX_US_BRGR.CD and FLEX_US_BRGR.FP to configure the baud rate. Write NACT, PARDIS, CHKDIS, CHKTYPE, DLCM, FSDIS and DLC in FLEX_US_LINMR to configure the frame transfer. Check that FLEX_US_CSR. TXRDY is set to 1. Write FLEX_US_LINIR.IDCHR to send the header. What comes next depends on the NACT configuration: • Case 1: NACT = PUBLISH, the USART sends the response. - Wait until FLEX_US_CSR. TXRDY rises. - Write FLEX_US_THR.TCHR to send a byte. - If all the data have not been written, repeat the two previous steps. - Wait until FLEX_US_CSR.LINTC rises. - Check the LIN errors. • Case 2: NACT = SUBSCRIBE, the USART receives the response. - Wait until FLEX_US_CSR.RXRDY rises. - Read FLEX_US_RHR.RCHR. - If all the data have not been read, repeat the two previous steps. - Wait until FLEX_US_CSR.LINTC rises. - Check the LIN errors. • Case 3: NACT = IGNORE, the USART is not concerned by the response. - Wait until FLEX_US_CSR.LINTC rises. - Check the LIN errors. Figure 47-47: Master Node Configuration, NACT = PUBLISH Frame slot = tFrame_Maximum Frame Header Break Synch Data3 Interframe space Response space Protected Identifier Response Data 1 Data N-1 Data N Checksum TXRDY FSDIS=1 FS RXRDY Write FLEX_US_LINIR Write FLEX_US_THR Data 1 Data 2 Data 3 Data N LINTC  2017 Microchip Technology Inc. DS60001476B-page 1453 SAMA5D2 SERIES Figure 47-48: Master Node Configuration, NACT = SUBSCRIBE Frame slot = tFrame_Maximum Frame Header Break Synch Data3 Interframe space Response space Protected Identifier Response Data 1 Data N-1 Data N Checksum TXRDY FSDIS=1 FSDIS RXRDY Write FLEX_US_LINIR Read FLEX_US_RHR Data 1 Data N-2 Data N-1 Data N LINTC Figure 47-49: Master Node Configuration, NACT = IGNORE Frame slot = tFrame_Maximum Frame Break Response space Header Data3 Synch Protected Identifier Interframe space Response Data 1 Data N-1 Data N Checksum TXRDY FSDIS=1 FSDIS RXRDY Write FLEX_US_LINIR LINTC • • • • • • • • Slave Node Configuration Write FLEX_US_CR.TXEN and FLEX_US_CR.RXEN to enable both the transmitter and the receiver. Write FLEX_US_MR.USART_MODE to select the LIN mode and the slave node configuration. Write FLEX_US_BRGR.CD and FLEX_US_BRGR.FP to configure the baud rate. Wait until FLEX_US_CSR.LINID rises. Check LINISFE and LINPE errors. Read FLEX_US_RHR.IDCHR. Write NACT, PARDIS, CHKDIS, CHKTYPE, DLCM and DLC in FLEX_US_LINMR to configure the frame transfer. IMPORTANT: If the NACT configuration for this frame is PUBLISH, FLEX_US_LINMR must be written with NACT = PUBLISH even if this field is already correctly configured, in order to set the TXREADY flag and the corresponding write transfer request. What comes next depends on the NACT configuration: • Case 1: NACT = PUBLISH, the LIN controller sends the response. - Wait until FLEX_US_CSR.TXRDY rises. - Write FLEX_US_THR.TCHR to send a byte. - If all the data have not been written, repeat the two previous steps. - Wait until FLEX_US_CSR. LINTC rises. - Check the LIN errors. • Case 2: NACT = SUBSCRIBE, the USART receives the response. DS60001476B-page 1454  2017 Microchip Technology Inc. SAMA5D2 SERIES - Wait until FLEX_US_CSR.RXRDY rises. - Read FLEX_US_RHR.RCHR. - If all the data have not been read, repeat the two previous steps. - Wait until FLEX_US_CSR.LINTC rises. - Check the LIN errors. • Case 3: NACT = IGNORE, the USART is not concerned by the response. - Wait until FLEX_US_CSR.LINTC rises. - Check the LIN errors. Figure 47-50: Slave Node Configuration, NACT = PUBLISH Break Synch Protected Identifier Data 1 Data N-1 Data N Checksum Data N Checksum TXRDY RXRDY LINIDRX Read FLEX_US_LINID Write FLEX_US_THR Data 1 Data 2 Data 3 Data N LINTC Figure 47-51: Slave Node Configuration, NACT = SUBSCRIBE Break Synch Protected Identifier Data 1 Data N-1 TXRDY RXRDY LINIDRX Read FLEX_US_LINID Read FLEX_US_RHR Data 1 Data N-2 Data N-1 Data N LINTC  2017 Microchip Technology Inc. DS60001476B-page 1455 SAMA5D2 SERIES Figure 47-52: Slave Node Configuration, NACT = IGNORE Break Synch Protected Identifier Data 1 Data N-1 Data N Checksum TXRDY RXRDY LINIDRX Read FLEX_US_LINID Read FLEX_US_RHR LINTC 47.7.9.16 LIN Frame Handling with the DMAC The USART can be used in association with the DMAC in order to transfer data directly into/from the on- and off-chip memories without any processor intervention. The DMAC uses the trigger flags, TXRDY and RXRDY, to write or read into the USART. The DMAC always writes in the Transmit Holding Register (FLEX_US_THR) and it always reads in the Receive Holding Register (FLEX_US_RHR). The size of the data written or read by the DMAC in the USART is always a byte. • Master Node Configuration The user can choose between two DMAC modes by configuring the FLEX_US_LINMR.PDCM bit: • PDCM = 1: The LIN configuration is stored in the WRITE buffer and it is written by the DMAC in the Transmit Holding register FLEX_US_THR (instead of the LIN Mode register FLEX_US_LINMR). Because the DMAC transfer size is limited to a byte, the transfer is split into two accesses. During the first access, the NACT, PARDIS, CHKDIS, CHKTYP, DLM and FSDIS bits are written. During the second access, the 8-bit DLC field is written. • PDCM = 0: The LIN configuration is not stored in the WRITE buffer and it must be written by the user in FLEX_US_LINMR. The WRITE buffer also contains the Identifier and the data, if the USART sends the response (NACT = PUBLISH). The READ buffer contains the data if the USART receives the response (NACT = SUBSCRIBE). Figure 47-53: Master Node with DMAC (PDCM = 1) WRITE BUFFER WRITE BUFFER NACT PARDIS CHKDIS CHKTYP DLM FSDIS NACT PARDIS CHKDIS CHKTYP DLM FSDIS DLC DLC NODE ACTION = PUBLISH NODE ACTION = SUBSCRIBE IDENTIFIER APB bus APB bus IDENTIFIER (Peripheral) DMA Controller USART3 LIN Controller READ BUFFER (Peripheral) DMA Controller RXRDY USART3 LIN Controller TXRDY DATA 0 DATA N DS60001476B-page 1456 DATA 0 TXRDY DATA N  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-54: Master Node with DMAC (PDCM = 0) WRITE BUFFER WRITE BUFFER IDENTIFIER IDENTIFIER NODE ACTION = PUBLISH NODE ACTION = SUBSCRIBE APB bus DATA 0 APB bus READ BUFFER (Peripheral) DMA Controller | | | | USART3 LIN Controller TXRDY DATA 0 (Peripheral) DMA Controller USART3 LIN Controller RXRDY TXRDY DATA N DATA N • Slave Node Configuration In this configuration, the DMAC transfers only the data. The identifier must be read by the user in the LIN Identifier Register (FLEX_US_LINIR). The LIN mode must be written by the user in FLEX_US_LINMR. The WRITE buffer contains the data if the USART sends the response (NACT = PUBLISH). The READ buffer contains the data if the USART receives the response (NACT = SUBSCRIBE). Figure 47-55: Slave Node with DMAC WRITE BUFFER READ BUFFER DATA 0 DATA 0 NACT = SUBSCRIBE APB bus APB bus USART3 LIN Controller (Peripheral) DMA Controller TXRDY DATA N 47.7.9.17 USART3 LIN Controller (Peripheral) DMA Controller RXRDY DATA N Wakeup Request Any node in a sleeping LIN cluster may request a wakeup. In the LIN 2.0 specification, the wakeup request is issued by forcing the bus to the dominant state from 250 µs to 5 ms. For this, it is necessary to send the character 0xF0 in order to impose five successive dominant bits. Whatever the baud rate is, this character respects the specified timings. • Baud rate min = 1 kbit/s -> tbit = 1 ms -> 5 tbit = 5 ms • Baud rate max = 20 kbit/s -> tbit = 50 µs -> 5 tbit = 250 µs In the LIN 1.3 specification, the wakeup request should be generated with the character 0x80 in order to impose eight successive dominant bits. Using the FLEX_US_LINMR.WKUPTYP bit, the user can choose to send either a LIN 2.0 wakeup request (WKUPTYP = 0) or a LIN 1.3 wakeup request (WKUPTYP = 1). A wakeup request is transmitted by writing the FLEX_US_CR.LINWKUP bit to 1. Once the transfer is completed, the LINTC flag is asserted in the Status Register (FLEX_US_CSR). It is cleared by writing a one to the FLEX_US_CR.RSTSTA bit. 47.7.9.18 Bus Idle Timeout If the LIN bus is inactive for a certain duration, the slave nodes shall automatically enter in Sleep mode. In the LIN 2.0 specification, this timeout is defined as 4 seconds. In the LIN 1.3 specification, it is defined as 25,000 tbit. In slave Node configuration, the receiver timeout detects an idle condition on the RXD line. When a timeout is detected, the FLEX_US_CSR.TIMEOUT bit rises and can generate an interrupt, thus indicating to the driver to go into Sleep mode.  2017 Microchip Technology Inc. DS60001476B-page 1457 SAMA5D2 SERIES The timeout delay period (during which the receiver waits for a new character) is programmed in the FLEX_US_RTOR.TO field. If a zero is written to the TO field, the Receiver Timeout is disabled and no timeout is detected. The FLEX_US_CSR.TIMEOUT bit remains at 0. Otherwise, the receiver loads a 17-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 FLEX_US_CSR.TIMEOUT bit rises. If STTTO is performed, the counter clock is stopped until a first character is received. If RETTO is performed, the counter starts counting down immediately from the value TO. Table 47-16: Receiver Timeout Programming LIN Specification Baud Rate TO 1,000 bit/s 4,000 2,400 bit/s 9,600 9,600 bit/s 2.0 4s 38,400 19,200 bit/s 76,800 20,000 bit/s 80,000 1.3 47.7.10 Timeout period – 25,000 tbit 25,000 Test Modes The USART can be programmed to operate in three different test modes. The internal loopback capability allows on-board diagnostics. In Loopback mode, the USART interface pins are disconnected or not and reconfigured for loopback internally or externally. 47.7.10.1 Normal Mode Normal mode connects the RXD pin on the receiver input and the transmitter output on the TXD pin. Figure 47-56: 47.7.10.2 Normal Mode Configuration Receiver RXD Transmitter TXD 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 47-57. 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 47-57: 47.7.10.3 Automatic Echo Mode Configuration Receiver RXD Transmitter TXD Local Loopback Mode Local Loopback mode connects the output of the transmitter directly to the input of the receiver, as shown in Figure 47-58. 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. DS60001476B-page 1458  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-58: Local Loopback Mode Configuration RXD Receiver 1 Transmitter 47.7.10.4 TXD Remote Loopback Mode Remote Loopback mode directly connects the RXD pin to the TXD pin, as shown in Figure 47-59. The transmitter and the receiver are disabled and have no effect. This mode allows bit-by-bit retransmission. Figure 47-59: Remote Loopback Mode Configuration 1 Receiver RXD TXD Transmitter 47.7.11 47.7.11.1 USART FIFOs Overview The USART includes two FIFOs which can be enabled/disabled using FLEX_US_CR.FIFOEN/FIFODIS. It is recommended to disable both the transmitter and the receiver before enabling or disabling the FIFOs, using the FLEX_US_CR.TXDIS/RXDIS bits. Writing FLEX_US_CR.FIFOEN to ‘1’ enables a 32-data Transmit FIFO and a 32-data Receive FIFO. It is possible to write or to read single or multiple data in the same access to FLEX_US_THR/RHR. See Section 47.7.11.6 “USART Single Data Mode” and Section 47.7.11.7 “USART Multiple Data Mode”. Figure 47-60: FIFOs Block Diagram USART Transmit FIFO Receive FIFO TXCHR3 FLEX_US_THR write TXCHR2 Threshold RXCHR3 TXCHR1 TXCHR0 RXCHR2 Threshold RXCHR1 FLEX_US_RHR read RXCHR0 Tx shifter Rx shifter TXD RXD  2017 Microchip Technology Inc. DS60001476B-page 1459 SAMA5D2 SERIES 47.7.11.2 Sending Data with FIFO Enabled When the Transmit FIFO is enabled, write access to FLEX_US_THR loads the Transmit FIFO. The FIFO level is provided in FLEX_US_FLR.TXFL. If the FIFO can accept the number of data to be transmitted, there is no need to monitor FLEX_US_CSR.TXRDY and the data can be successively written in FLEX_US_THR. If the FIFO cannot accept the data due to insufficient space, wait for the TXRDY flag to be set before writing the data in FLEX_US_THR. When the space in the FIFO allows only a portion of the data to be written, the TXRDY flag must be monitored before writing the remaining data. Figure 47-61: Sending Data with FIFO Enabled BEGIN Read FLEX_US_FESR Yes Enough space in Transmit FIFO to write all the data to send? Write FLEX_US_THR No Read FLEX_US_CSR TXRDY = 1? No No All data have been written in FLEX_US_THR? Yes Yes Write FLEX_US_THR No All data have been written in FLEX_US_THR? Yes Read FLEX_US_CSR No TXEMPTY = 1 ? Yes END 47.7.11.3 Receiving Data with FIFO Enabled When the Receive FIFO is enabled, FLEX_US_RHR access reads the FIFO. When data are present in the Receive FIFO (RXRDY flag set to ‘1’), the exact number of data can be checked with FLEX_US_FLR.RXFL. All the data can be read successively in FLEX_US_RHR without checking the RXRDY flag between each access. DS60001476B-page 1460  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-62: Receiving Data with FIFO Enabled BEGIN Read FLEX_US_CSR RXRDY = 1 ? No Yes Read FLEX_US_FLR and get the number of data in Receive FIFO Read FLEX_US_RHR All data have been read in FLEX_US_RHR? No Yes END 47.7.11.4 Clearing/Flushing FIFOs Each FIFO can be cleared/flushed using FLEX_US_CR.TXFCLR/RXFCLR. 47.7.11.5 TXEMPTY, TXRDY and RXRDY Behavior FLEX_US_CSR.TXEMPTY, FLEX_US_CSR.TXRDY and FLEX_US_CSR.RXRDY flags display a specific behavior when FIFOs are enabled. The TXEMPTY flag is cleared as long as there are characters in the Transmit FIFO or in the internal shift register. TXEMPTY is set when there are no characters in the Transmit FIFO and in the internal shift register. TXRDY indicates if a data can be written in the Transmit FIFO. Thus the TXRDY flag is set as long as the Transmit FIFO can accept new data. Refer to Figure 47-63. RXRDY indicates if an unread data is present in the Receive FIFO. Thus the RXRDY flag is set as soon as one unread data is in the Receive FIFO. Refer to Figure 47-64. TXRDY and RXRDY behavior can be modified using the TXRDYM and RXRDYM fields in the USART FIFO Mode Register (FLEX_US_FMR) to reduce the number of accesses to FLEX_US_RHR/THR. However, for some configurations, the following constraints apply: • If FLEX_US_MR.MODE9 is set, FLEX_US_FMR.TXRDYM/RXRDYM must be cleared. • If FLEX_US_MR.USART_MODE is set to either LIN_MASTER or LIN_SLAVE, FLEX_US_FMR.TXRDYM/RXRDYM must be cleared. See USART FIFO Mode Register for the FIFO configuration.  2017 Microchip Technology Inc. DS60001476B-page 1461 SAMA5D2 SERIES Figure 47-63: TXRDY in Single Data Mode and TXRDYM = 0 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 Start D0 Bit Bit Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Start Bit Bit Bit Write FLEX_US_THR RSTSTA = 1 Write FLEX_US_CR TXRDY TXFFF 0 1 TXFL 1 2 3 4 3 FIFO size -1 FIFO full FIFO size -1 TXEMPTY Figure 47-64: RXRDY in Single Data Mode and RXRDYM = 0 Baud Rate Clock RXD 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 Start D0 Bit Bit Bit D1 D2 D3 D4 D5 D6 D7 Parity Stop Bit Bit RSTSTA = 1 Write FLEX_US_CR Read FLEX_US_RHR RXRDY 0 RXFL 1 FIFO full FIFO size - 1 FIFO size - 2 0 RXFFF RXFEF OVRE 47.7.11.6 USART Single Data Mode In Single Data mode, only one data is written every time FLEX_US_THR is accessed, and only one data is read every time FLEX_US_RHR is accessed. When FLEX_US_FMR.TXRDYM = 0, the Transmit FIFO operates in Single Data mode. When FLEX_US_FMR.RXRDYM = 0, the Receive FIFO operates in Single Data mode. If FLEX_US_MR.MODE9 is set, or if FLEX_US_MR.USART_MODE is set to either LIN_MASTER or LIN_SLAVE, the FIFOs must operate in Single Data mode. See Section 47.10.20 ”USART Receive Holding Register” and Section 47.10.22 ”USART Transmit Holding Register”. • DMAC DS60001476B-page 1462  2017 Microchip Technology Inc. SAMA5D2 SERIES The DMAC transfer type must be configured in bytes or halfwords when FIFOs operate in Single Data mode (the same applies when FIFOs are disabled). 47.7.11.7 USART Multiple Data Mode Multiple Data mode minimizes the number of accesses by concatenating the data to send/read in one access. When FLEX_US_FMR.TXRDYM > 0, the Transmit FIFO operates in Multiple Data mode. When FLEX_US_FMR.RXRDYM > 0, the Receive FIFO operates in Multiple Data mode. However, Multiple Data mode cannot be used for the following configurations: • If FLEX_US_MR.MODE9 is set • If FLEX_US_MR.USART_MODE is set to either LIN_MASTER or LIN_SLAVE In Multiple Data mode, it is possible to write/read up to four data in one FLEX_US_THR/FLEX_US_RHR access. The number of data to write/read is defined by the size of the register access. If the access is a byte-size register access, only one data is written/read, if the access is a halfword size register access, then two data are written/read and, finally, if the access is a word-size register access, four data are written/read. Written/read data are always right-aligned, as described in Section 47.10.21 ”USART Receive Holding Register (FIFO Multi Data)” and Section 47.10.23 ”USART Transmit Holding Register (FIFO Multi Data)”. As an example, if the Transmit FIFO is empty and there are six data to send, either of the following write accesses may be performed: • six FLEX_US_THR-byte write accesses • three FLEX_US_THR-halfword write accesses • one FLEX_US_THR word write access and one FLEX_US_THR halfword write access With a Receive FIFO containing six data, any of the following read accesses may be performed: • • • • six FLEX_US_RHR-byte read accesses three FLEX_US_RHR-halfword read accesses one FLEX_US_RHR-word read access and one FLEX_US_RHR-halfword read access TXRDY and RXRDY Configuration In Multiple Data mode, it is possible to write one or more data in the same FLEX_US_THR/FLEX_US_RHR access. The TXRDY flag indicates if one or more data can be written in the FIFO depending on the configuration of FLEX_US_FMR.TXRDYM/RXRDYM. As an example, if four data are written each time in FLEX_US_THR, it is useful to configure the TXRDYM field to the value ‘2’ so that the TXRDY flag is at ‘1’ only when at least four data can be written in the Transmit FIFO. In the same way, if four data are read each time in FLEX_US_RHR, it is useful to configure the RXRDYM field to the value ‘2’ so that the RXRDY flag is at ‘1’ only when at least four unread data are in the Receive FIFO. • DMAC When FIFOs operate in Multiple Data mode, the DMAC transfer type must be configured in byte, halfword or word depending on the FLEX_US_FMR.TXRDYM/RXRDYM settings. 47.7.11.8 Transmit FIFO Lock • LIN Mode: If a frame is aborted using the Abort LIN Transmission bit (FLEX_US_CR.LINABT), a lock is set on the Transmit FIFO, preventing any new frame from being sent until it is cleared. This allows clearing the FIFO if needed, resetting DMAC channels, etc., without any risk. The TXFLOCK bit in the USART FIFO Event Status Register (FLEX_US_FESR) is used to check the state of the Transmit FIFO lock. The Transmit FIFO lock can be cleared by setting FLEX_US_CR.TXFLCLR to ‘1’. 47.7.11.9 FIFO Pointer Error A FIFO overflow is reported in FLEX_US_FESR. If the Transmit FIFO is full and a write access is performed on FLEX_US_THR, it generates a Transmit FIFO pointer error and sets FLEX_US_FESR.TXFPTEF. In Multiple Data mode, if the number of data written in FLEX_US_THR (according to the register access size) is greater than the free space in the Transmit FIFO, a Transmit FIFO pointer error is generated and FLEX_US_FESR.TXFPTEF is set. A FIFO underflow is reported in FLEX_US_FESR. In Multiple Data mode, if the number of data read in FLEX_US_RHR (according to the register access size) is greater than the number of unread data in the Receive FIFO, a Receive FIFO pointer error is generated and FLEX_US_FESR.RXFPTEF is set.  2017 Microchip Technology Inc. DS60001476B-page 1463 SAMA5D2 SERIES No pointer error occurs if the FIFO state/level is checked before writing/reading in FLEX_US_THR/FLEX_US_RHR. The FIFO state/level can be checked either with TXRDY, RXRDY, TXFL or RXFL. When a pointer error occurs, other FIFO flags may not behave as expected; their states should be ignored. If a Transmit pointer error occurs, a transmitter reset must be performed using FLEX_US_CR.RSTTX. If a Receive pointer error occurs, a receiver reset must be performed using FLEX_US_CR.RSTRX. 47.7.11.10 FIFO Thresholds Each Transmit and Receive FIFO includes a threshold feature used to set a flag and an interrupt when a FIFO threshold is crossed. Thresholds are defined as a number of data in the FIFO, and the FIFO state (TXFL or RXFL) represents the number of data currently in the FIFO. The Transmit FIFO threshold can be set using the field FLEX_US_FMR.TXFTHRES. Each time the Transmit FIFO level goes from ‘above threshold’ to ‘equal or below threshold’, the flag FLEX_US_FESR.TXFTHF is set. The application is warned that the Transmit FIFO has reached the defined threshold and that it can be reloaded. The Receive FIFO threshold can be set using the field FLEX_US_FMR.RXFTHRES. Each time the Receive FIFO level goes from ‘below threshold’ to ‘equal or above threshold’, the flag FLEX_US_FESR.RXFTHF is set. The application is warned that the Receive FIFO has reached the defined threshold and that it can be read to prevent an underflow. The Receive FIFO threshold 2 can be set using the field FLEX_US_FMR.RXFTHRES2. Each time the Receive FIFO level goes from ‘above threshold 2’ to ‘equal or below threshold 2’, the flag FLEX_US_FESR.RXFTHF2 is set. The application is warned that the Receive FIFO has reached the defined threshold and that it can be read to prevent an underflow. The TXFTHF, RXFTHF and RXTHF2 flags can be configured to generate an interrupt using FLEX_US_FIER and FLEX_US_FIDR. 47.7.11.11 FIFO Flags FIFOs come with a set of flags which can be configured to generate interrupts through FLEX_US_FIER and FLEX_US_FIDR. FIFO flags state can be read in FLEX_US_FESR. They are cleared by writing FLEX_US_CR.RSTSTA to ‘1’. DS60001476B-page 1464  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.7.12 USART Register Write Protection The FLEXCOM operating mode (FLEX_MR.OPMODE) must be set to FLEX_MR_OPMODE_USART to enable access to the write protection registers. To prevent any single software error from corrupting USART behavior, certain registers in the address space can be write-protected by setting the WPEN (Write Protection Enable) bit in the USART Write Protection Mode Register (FLEX_US_WPMR). If a write access to a write-protected register is detected, the Write Protection Violation Status (WPVS) flag in the USART Write Protection Status Register (FLEX_US_WPSR) is set and the Write Protection Violation Source (WPVSRC) field indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading FLEX_US_WPSR. The following registers can be write-protected when WPEN is set: • • • • • • • • USART Mode Register USART Baud Rate Generator Register USART Receiver Timeout Register USART Transmitter Timeguard Register USART FI DI RATIO Register USART IrDA FILTER Register USART Manchester Configuration Register USART Comparison Register  2017 Microchip Technology Inc. DS60001476B-page 1465 SAMA5D2 SERIES 47.8 SPI Functional Description 47.8.1 Modes of Operation The SPI operates in Master mode or in Slave mode. • The SPI operates in Master mode by writing a 1 to the MSTR bit in the SPI Mode Register (FLEX_SPI_MR): - The pins NPCS0 to NPCS1 are all configured as outputs. - The SPCK pin is driven. - The MISO line is wired on the receiver input. - The MOSI line is driven as an output by the transmitter. • The SPI operates in Slave mode if the MSTR bit in FLEX_SPI_MR is written to 0: - The MISO line is driven by the transmitter output. - The MOSI line is wired on the receiver input. - The SPCK pin is driven by the transmitter to synchronize the receiver. - The NPCS0 pin becomes an input, and is used as a slave select signal (NSS). - Pin NPCS1 is not are not are not driven and can be used for other purposes. The data transfers are identically programmable for both modes of operation. The bit rate generator is activated only in Master mode. 47.8.2 Data Transfer Four combinations of polarity and phase are available for data transfers. The clock polarity is programmed with the CPOL bit in the SPI Chip Select Register (FLEX_SPI_CSR). The clock phase is programmed with the NCPHA bit. These two parameters determine the edges of the clock signal on which data are driven and sampled. Each of the two parameters has two possible states, resulting in four possible combinations that are incompatible with one another. Consequently, a master/slave pair must use the same parameter pair values to communicate. If multiple slaves are connected and require different configurations, the master must reconfigure itself each time it needs to communicate with a different slave. Table 47-17 shows the four modes and corresponding parameter settings. Table 47-17: SPI Bus Protocol Mode SPI Mode CPOL NCPHA Shift SPCK Edge Capture SPCK Edge SPCK Inactive Level 0 0 1 Falling Rising Low 1 0 0 Rising Falling Low 2 1 1 Rising Falling High 3 1 0 Falling Rising High Figure 47-65 and Figure 47-66 show examples of data transfers. DS60001476B-page 1466  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-65: SPI Transfer Format (NCPHA = 1, 8 bits per transfer) SPCK cycle (for reference) 1 2 3 4 5 6 7 8 SPCK (CPOL = 0) SPCK (CPOL = 1) MOSI (from master) MSB MISO (from slave) MSB 6 5 4 3 2 1 LSB 6 5 4 3 2 1 LSB * NSS (to slave) * Not defined. Figure 47-66: SPI Transfer Format (NCPHA = 0, 8 bits per transfer) 1 SPCK cycle (for reference) 2 3 4 5 7 6 8 SPCK (CPOL = 0) SPCK (CPOL = 1) MOSI (from master) MISO (from slave) * MSB 6 5 4 3 2 1 MSB 6 5 4 3 2 1 LSB LSB NSS (to slave) * Not defined. 47.8.3 Master Mode Operations When configured in Master mode, the SPI operates on the clock generated by the internal programmable bit rate generator. It fully controls the data transfers to and from the slave(s) connected to the SPI bus. The SPI drives the chip select line to the slave and the serial clock signal (SPCK).  2017 Microchip Technology Inc. DS60001476B-page 1467 SAMA5D2 SERIES The SPI features two holding registers, the Transmit Data Register (FLEX_SPI_TDR) and the Receive Data Register (FLEX_SPI_RDR), and a single shift register. The holding registers maintain the data flow at a constant rate. After enabling the SPI, a data transfer starts when the processor writes to FLEX_SPI_TDR. The written data are immediately transferred in the shift register and the transfer on the SPI bus starts. While the data in the shift register is shifted on the MOSI line, the MISO line is sampled and shifted in the shift register. Data cannot be loaded in FLEX_SPI_RDR without transmitting data. If there is no data to transmit, a dummy data can be used (FLEX_SPI_TDR filled with ones). When the WDRBT bit is set, a new data cannot be transmitted if FLEX_SPI_RDR has not been read. If Receiving mode is not required, for example when communicating with a slave receiver only (such as an LCD), the receive status flags in the SPI Status Register (FLEX_SPI_SR) can be discarded. Before writing the TDR, the FLEX_SPI_MR.PCS field must be set in order to select a slave. If new data are written in FLEX_SPI_TDR during the transfer, it is kept in FLEX_SPI_TDR until the current transfer is completed. Then, the received data are transferred from the shift register to FLEX_SPI_RDR, the data in FLEX_SPI_TDR is loaded in the shift register and a new transfer starts. As soon as the FLEX_SPI_TDR is written, the Transmit Data Register Empty (TDRE) flag in FLEX_SPI_SR is cleared. When the data written in FLEX_SPI_TDR is loaded into the shift register, the FLEX_SPI_SR.TDRE flag is set. The TDRE bit is used to trigger the Transmit DMA channel (see Figure 47-67). The end of transfer is indicated by FLEX_SPI_SR.TXEMPTY. If a transfer delay (DLYBCT) is greater than 0 for the last transfer, TXEMPTY is set after the completion of this delay. The peripheral clock can be switched off at this time. Note 1: When the SPI is enabled, the TDRE and TXEMPTY flags are set. 2: The TXEMPTY flag alone cannot be used to detect the end of the buffer DMA transfer. Figure 47-67: TDRE and TXEMPTY Flag Behavior Write FLEX_SPI_CR.SPIEN = 1 TDRE Write FLEX_SPI_THR Write FLEX_SPI_THR automatic set THR loaded in shifter Write FLEX_SPI_THR automatic set THR loaded in shifter automatic set THR loaded in shifter TXEMPTY Transfer Transfer DLYBCT Transfer DLYBCT DLYBCT The transfer of received data from the shift register to FLEX_SPI_RDR is indicated by the Receive Data Register Full (RDRF) bit in FLEX_SPI_SR. When the received data are read, the RDRF bit is cleared. If FLEX_SPI_RDR has not been read before new data are received, the Overrun Error bit (OVRES) in FLEX_SPI_SR is set. As long as this flag is set, data are loaded in FLEX_SPI_RDR. The user has to read the status register to clear the OVRES bit. Figure 47-68 shows a block diagram of the SPI when operating in Master mode. Figure 47-69 shows a flow chart describing how transfers are handled. DS60001476B-page 1468  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.8.3.1 Master Mode Block Diagram Figure 47-68: Master Mode Block Diagram FLEX_SPI_CSRx SCBR Baud Rate Generator Peripheral clock SPCK SPI Clock FLEX_SPI_SR FLEX_SPI_CSRx BITS NCPHA CPOL LSB MISO FLEX_SPI_RDR RDRF OVRES RD MSB Shift Register FLEX_SPI_TDR TD MOSI TDRE FLEX_SPI_CSRx FLEX_SPI_RDR CSAAT PCS PS NPCSx PCSDEC FLEX_SPI_MR PCS 0 Current Peripheral FLEX_SPI_TDR NPCS0 PCS 1 MSTR MODF NPCS0 MODFDIS  2017 Microchip Technology Inc. DS60001476B-page 1469 SAMA5D2 SERIES 47.8.3.2 Master Mode Flowchart Figure 47-69: Master Mode SPI Enable - NPCS defines the current Chip Select - CSAAT, DLYBS, DLYBCT refer to the fields of the Chip Select Register corresponding to the current Chip Select 1 TDRE ? 0 PS ? 1 0 0 Fixed peripheral PS ? 1 Fixed peripheral 0 1 CSAAT ? Variable peripheral Variable peripheral FLEX_SPI_TDR(PCS) = NPCS ? no NPCS = FLEX_SPI_TDR(PCS) NPCS = FLEX_SPI_MR(PCS) yes FLEX_SPI_MR(PCS) = NPCS ? no NPCS deasserted NPCS deasserted Delay DLYBCS Delay DLYBCS NPCS = FLEX_SPI_TDR(PCS) NPCS = FLEX_SPI_MR(PCS), FLEX_SPI_TDR(PCS) Delay DLYBS Serializer = FLEX_SPI_TDR(TD) TDRE = 1 Data Transfer FLEX_SPI_RDR(RD) = Serializer RDRF = 1 Delay DLYBCT 0 TDRE ? 1 1 CSAAT ? 0 NPCS deasserted Delay DLYBCS DS60001476B-page 1470  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-70 shows the behavior of Transmit Data Register Empty (TDRE), Receive Data Register (RDRF) and Transmission Register Empty (TXEMPTY) status flags within FLEX_SPI_SR during an 8-bit data transfer in Fixed mode without the DMAC involved. Figure 47-70: Status Register Flags Behavior 1 2 3 4 6 5 7 8 SPCK NPCS0 MOSI (from master) MSB 6 5 4 3 2 1 LSB TDRE RDR read Write in FLEX_SPI_TDR RDRF MISO (from slave) MSB 6 5 4 3 2 1 LSB TXEMPTY shift register empty 47.8.3.3 Clock Generation The SPI bit rate clock is generated by dividing a source clock which can be the peripheral clock or a programmable clock from the GCLK. The divider can be a value between 1 and 255. If the SCBR field is programmed to 1 and the clock source is GCLK, the operating bit rate is peripheral clock (refer to Section 66. “Electrical Characteristics” for the SPCK maximum frequency). Triggering a transfer while SCBR is at 0 can lead to unpredictable results. At reset, SCBR is 0 and the user has to program it to a valid value before performing the first transfer. The divisor can be defined independently for each chip select, as it has to be programmed in the FLEX_SPI_CSR.SCBR field. This allows the SPI to automatically adapt the bit rate for each interfaced peripheral without reprogramming. If GCLK is selected as source clock (FLEX_SPI_MR.BRSRCCLK = 1), the bit rate is independent of the processor/bus clock. Thus, the processor clock can be changed while SPI is enabled. The processor clock frequency changes must be performed only by programming the PMC_MCKR.PRES field (refer to Section 33. “Power Management Controller (PMC)”). Any other method to modify the processor/bus clock frequency (PLL multiplier, etc.) is forbidden when SPI is enabled. The peripheral clock frequency must be at least three times higher than GCLK. 47.8.3.4 Transfer Delays Figure 47-71 shows a chip select transfer change and consecutive transfers on the same chip select. Three delays can be programmed to modify the transfer waveforms: • The delay between the chip selects. It is programmable only once for all chip selects by writing the FLEX_SPI_MR.DLYBCS field. The SPI slave device deactivation delay is managed through DLYBCS. If there is only one SPI slave device connected to the master, the DLYBCS field does not need to be configured. If several slave devices are connected to a master, DLYBCS must be configured depending on the highest deactivation delay. Refer to the SPI slave device electrical characteristics. • The delay before SPCK, independently programmable for each chip select by writing the DLYBS field. The SPI slave device activation delay is managed through DLYBS. Refer to the SPI slave device electrical characteristics to define DLYBS. • The delay between consecutive transfers, independently programmable for each chip select by writing the DLYBCT field. The time required by the SPI slave device to process received data is managed through DLYBCT. This time depends on the SPI slave system activity. These delays allow the SPI to be adapted to the interfaced peripherals and their speed and bus release time.  2017 Microchip Technology Inc. DS60001476B-page 1471 SAMA5D2 SERIES Figure 47-71: Programmable Delays Chip Select 1 Chip Select 2 SPCK DLYBCS 47.8.3.5 DLYBS DLYBCT DLYBCT Peripheral Selection The serial peripherals are selected through the assertion of the NPCS0 to NPCS1 signals. By default, all NPCS signals are high before and after each transfer. • Fixed Peripheral Select Mode: SPI exchanges data with only one peripheral. Fixed Peripheral Select mode is enabled by writing the FLEX_SPI_MR.PS bit to zero. In this case, the current peripheral is defined by the FLEX_SPI_MR.PCS field, and the FLEX_SPI_TDR. PCS field has no effect. • Variable Peripheral Select Mode: Data can be exchanged with more than one peripheral without having to reprogram FLEX_SPI_MR.PCS. Variable Peripheral Select Mode is enabled by setting the FLEX_SPI_MR.PS bit to one. The FLEX_SPI_TDR.PCS field is used to select the current peripheral. This means that the peripheral selection can be defined for each new data. The value must be written in a single access to FLEX_SPI_TDR in the following format: [xxxxxxx(7-bit) + LASTXFER(1-bit)(1)+ xxxx(4-bit) + PCS (4-bit) + TD (8 to 16-bit data)] with LASTXFER at 0 or 1 depending on the CSAAT bit, and PCS equal to the chip select to assert, as defined in Section 47.10.48, SPI Transmit Data Register. Note 1: Optional The CSAAT, LASTXFER and CSNAAT bits are discussed in Section 47.8.3.9, Peripheral Deselection with DMA. If LASTXFER is used, the command must be issued after writing the last character. Instead of LASTXFER, the user can use the SPIDIS command. After the end of the DMA transfer, it is necessary to wait for the TXEMPTY flag and then write SPIDIS into the SPI Control Register (FLEX_SPI_CR). This does not change the configuration register values). The NPCS is disabled after the last character transfer. Then, another DMA transfer can be started if the FLEX_SPI_CR.SPIEN bit has previously been written. 47.8.3.6 SPI Direct Access Memory Controller (DMAC) In both Fixed and Variable modes, the Direct Memory Access Controller (DMAC) can be used to reduce processor overhead. The fixed peripheral selection allows buffer transfers with a single peripheral. Using the DMAC is an optimal means, as the size of the data transfer between the memory and the SPI is either 8 bits or 16 bits. However, if the peripheral selection is modified, FLEX_SPI_MR must be reprogrammed. The variable peripheral selection allows buffer transfers with multiple peripherals without reprogramming FLEX_SPI_MR. Data written in FLEX_SPI_TDR is 32 bits wide and defines the real data to be transmitted and the destination peripheral. Using the DMAC in this mode requires 32-bit wide buffers, with the data in the LSBs and the PCS and LASTXFER fields in the MSBs. However, the SPI still controls the number of bits (8 to 16) to be transferred through MISO and MOSI lines with the chip select configuration registers. This is not the optimal means in terms of memory size for the buffers, but it provides a very effective means to exchange data with several peripherals without any intervention of the processor. 47.8.3.7 Peripheral Chip Select Decoding The user can program the SPI to operate with up to 3 slave peripherals by decoding the two chip select lines, NPCS0 to NPCS1 with an external decoder/demultiplexer (see Figure 47-72). This can be enabled by setting the FLEX_SPI_MR.PCSDEC bit. When operating without decoding, the SPI makes sure that in any case only one chip select line is activated, i.e., one NPCS line driven low at a time. If two bits are defined low in a PCS field, only the lowest numbered chip select is driven low. When operating with decoding, the SPI directly outputs the value defined by the PCS field on the NPCS lines of either FLEX_SPI_MR or FLEX_SPI_TDR (depending on PS). DS60001476B-page 1472  2017 Microchip Technology Inc. SAMA5D2 SERIES As the SPI sets a default value of 0x3 on the chip select lines (i.e., all chip select lines at 1) when not processing any transfer, only 3 peripherals can be decoded. The SPI has only two Chip Select registers. As a result, when external decoding is activated, each NPCS chip select defines the characteristics of up to two peripherals. As an example, FLEX_SPI_CRS0 defines the characteristics of the externally decoded peripherals 0 to 1, corresponding to the PCS values 0x0 to 0x1. Consequently, the user has to make sure to connect compatible peripherals on the decoded chip select lines 0 to 1 and 2. Figure 47-72 shows this type of implementation. If the CSAAT bit is used, with or without the DMAC, the mode fault detection for NPCS0 line must be disabled. This is not needed for all other chip select lines since mode fault detection is only on NPCS0. Figure 47-72: Chip Select Decoding Application Block Diagram: Single Master/Multiple Slave Implementation SPCK MISO MOSI SPCK MISO MOSI SPCK MISO MOSI SPCK MISO MOSI Slave 0 Slave 1 Slave 3 NSS NSS NSS SPI Master NPCS0 NPCS1 Decoded chip select lines External 1-of-n Decoder/Demultiplexer 47.8.3.8 Peripheral Deselection without DMA During a transfer of more than one data on a Chip Select without the DMA, FLEX_SPI_TDR is loaded by the processor, the TDRE flag rises as soon as the content of FLEX_SPI_TDR is transferred into the internal shift register. When this flag is detected high, FLEX_SPI_TDR can be reloaded. If this reload by the processor occurs before the end of the current transfer, and if the next transfer is performed on the same chip select as the current transfer, the Chip Select is not deasserted between the two transfers. But depending on the application software handling the SPI status register flags (by interrupt or polling method) or servicing other interrupts or other tasks, the processor may not reload FLEX_SPI_TDR in time to keep the chip select active (low). A null DLYBCT value (delay between consecutive transfers) in FLEX_SPI_CSR, gives even less time for the processor to reload FLEX_SPI_TDR. With some SPI slave peripherals, if the chip select line must remain active (low) during a full set of transfers, communication errors can occur. To facilitate interfacing with such devices, the Chip Select registers [CSR0...CSR1] can be programmed with the Chip Select Active After Transfer (CSAAT) bit to 1. This allows the chip select lines to remain in their current state (low = active) until a transfer to another chip select is required. Even if FLEX_SPI_TDR is not reloaded, the chip select remains active. To de-assert the chip select line at the end of the transfer, the Last Transfer (LASTXFER) bit in FLEX_SPI_CR must be set after writing the last data to transmit into FLEX_SPI_TDR. 47.8.3.9 Peripheral Deselection with DMA DMA provides faster reloads of FLEX_SPI_TDR compared to software. However, depending on the system activity, it is not guaranteed that FLEX_SPI_TDR is written with the next data before the end of the current transfer. Consequently, a data can be lost by the deassertion of the NPCS line for SPI slave peripherals requiring the chip select line to remain active between two transfers. The only way to guarantee a safe transfer in this case is the use of the CSAAT and LASTXFER bits. When the CSAAT bit is cleared, the NPCS does not rise in all cases between two transfers on the same peripheral. During a transfer on a Chip Select, the TDRE flag rises as soon as the content of FLEX_SPI_TDR is transferred into the internal shift register. When this flag is detected, FLEX_SPI_TDR can be reloaded. If this reload occurs before the end of the current transfer and if the next transfer is performed on the same chip select as the current transfer, the Chip Select is not deasserted between the two transfers. This can lead to difficulties to interface with some serial peripherals requiring the chip select to be deasserted after each transfer. To facilitate interfacing with  2017 Microchip Technology Inc. DS60001476B-page 1473 SAMA5D2 SERIES such devices, FLEX_SPI_CSR can be programmed with the Chip Select Not Active After Transfer (CSNAAT) bit to 1. This allows the chip select lines to be deasserted systematically during a time “DLYBCS” (the value of the CSNAAT bit is processed only if the CSAAT bit is cleared for the same chip select). Figure 47-73 shows different peripheral deselection cases and the effect of the CSAAT and CSNAAT bits. Figure 47-73: Peripheral Deselection CSAAT = 0 and CSNAAT = 0 TDRE CSAAT = 1 and CSNAAT= 0 / 1 DLYBCT NPCS[0..n] DLYBCT A A A A DLYBCS A DLYBCS PCS = A PCS = A Write FLEX_SPI_TDR TDRE DLYBCT DLYBCT A NPCS[0..n] A A A DLYBCS A DLYBCS PCS=A PCS = A Write FLEX_SPI_TDR TDRE DLYBCT NPCS[0..n] DLYBCT A B A B DLYBCS DLYBCS PCS = B PCS = B Write FLEX_SPI_TDR CSAAT = 0 and CSNAAT = 0 CSAAT = 0 and CSNAAT = 1 DLYBCT DLYBCT TDRE NPCS[0..n] A A A A DLYBCS PCS = A PCS = A Write FLEX_SPI_TDR 47.8.3.10 Mode Fault Detection The SPI has the capability to operate in multi-master environment. Consequently, the NPCS0/NSS line must be monitored. If one of the masters on the SPI bus is currently transmitting, the NPCS0/NSS line is low and the SPI must not transmit a data. A mode fault is detected when the SPI is programmed in Master mode and a low level is driven by an external master on the NPCS0/NSS signal. In multi-master DS60001476B-page 1474  2017 Microchip Technology Inc. SAMA5D2 SERIES environment, NPCS0, MOSI, MISO and SPCK pins must be configured in open drain (through the PIO controller). When a mode fault is detected, the FLEX_SPI_SR.MODF bit is set until FLEX_SPI_SR is read and the SPI is automatically disabled until it is re-enabled by writing the FLEX_SPI_CR.SPIEN bit to 1. By default, the mode fault detection is enabled. The user can disable it by setting the FLEX_SPI_MR.MODFDIS bit. 47.8.4 SPI Slave Mode When operating in Slave mode, the SPI processes data bits on the clock provided on the SPI clock pin (SPCK). The SPI waits until NSS goes active before receiving the serial clock from an external master. When NSS falls, the clock is validated and the data are loaded in FLEX_SPI_RDR according to the configuration value of the FLEX_SPI_CSR0.BITS field. These bits are processed following a phase and a polarity defined respectively by the FLEX_SPI_CSR0.NCPHA and FLEX_SPI_CSR0.CPOL bits. Note that the BITS field, CPOL bit and NCPHA bit of the other Chip Select registers have no effect when the SPI is programmed in Slave mode. The bits are shifted out on the MISO line and sampled on the MOSI line. Note: For more information on the BITS field, see also the note below the FLEX_SPI_CSRx register bitmap in Section 47.10.54 “SPI Chip Select Register”. When all bits are processed, the received data are transferred in FLEX_SPI_RDR and the RDRF bit rises. If FLEX_SPI_RDR has not been read before new data are received, the Overrun Error bit (OVRES) in FLEX_SPI_SR is set. As long as this flag is set, data are loaded in FLEX_SPI_RDR. The user must read FLEX_SPI_SR to clear the OVRES bit. When a transfer starts, the data shifted out is the data present in the shift register. If no data has been written in FLEX_SPI_TDR, the last data received is transferred. If no data has been received since the last reset, all bits are transmitted low, as the shift register resets to 0. When a first data is written in FLEX_SPI_TDR, it is transferred immediately in the shift register and the TDRE flag rises. If new data is written, it remains in FLEX_SPI_TDR until a transfer occurs, i.e., NSS falls and there is a valid clock on the SPCK pin. When the transfer occurs, the last data written in FLEX_SPI_TDR is transferred in the shift register and the TDRE flag rises. This enables frequent updates of critical variables with single transfers. Then, a new data is loaded in the shift register from FLEX_SPI_TDR. If no character is ready to be transmitted, i.e., no character has been written in FLEX_SPI_TDR since the last load from FLEX_SPI_TDR to the shift register, FLEX_SPI_TDR is retransmitted. In this case the Underrun Error Status Flag (UNDES) is set in FLEX_SPI_SR. If NSS rises between two characters, it must be kept high for two MCK clock periods or more and the next SPCK capture edge must not occur less than four MCK periods after NSS rise. Figure 47-74 shows a block diagram of the SPI when operating in Slave mode. Figure 47-74: Slave Mode Functional Block Diagram SPCK NSS SPI Clock SPIEN SPIENS SPIDIS FLEX_SPI_SR FLEX_SPI_CSR0 BITS NCPHA CPOL MOSI LSB FLEX_SPI_RDR RDRF OVRES RD MSB Shift Register MISO FLEX_SPI_TDR TD 47.8.5 TDRE SPI Comparison Function on Received Character The comparison is only relevant for SPI Slave mode (MSTR = 0 in FLEX_US_MR). The effect of a comparison match changes if the system is in Wait or Active mode.  2017 Microchip Technology Inc. DS60001476B-page 1475 SAMA5D2 SERIES In Wait mode, if asynchronous partial wakeup is enabled, a system wakeup is performed (see Section 47.8.6 ”SPI Asynchronous and Partial Wakeup (SleepWalking)”). In Active mode, the CMP flag in FLEX_SPI_SR is raised. It is set when the received character matches the conditions programmed in the SPI Comparison Register (FLEX_SPI_CMPR). The CMP flag is set as soon as FLEX_SPI_RDR is loaded with the new received character. The CMP flag is cleared by reading FLEX_SPI_SR. FLEX_SPI_CMPR (see Section 47.10.57 “SPI Comparison Register”) can be programmed to provide different comparison methods. These are listed below: • If VAL1 equals VAL2, then the comparison is performed on a single value and the flag is set to 1 if the received character equals VAL1. • If VAL1 is strictly lower than VAL2, then any value between VAL1 and VAL2 sets the CMP flag. • If VAL1 is strictly higher than VAL2, then the flag CMP is set to 1 if any received character equals VAL1 or VAL2. When FLEX_SPI_MR.CMPMODE is cleared, all received data is loaded in FLEX_SPI_RDR and the CMP flag provides the status of the comparison result. By setting the CMPMODE bit, the comparison result triggers the start of FLEX_SPI_RDR loading (see Figure 47-75). The trigger condition exists as soon as the received character value matches the conditions defined by VAL1 and VAL2 in FLEX_SPI_CMPR. The comparison trigger event is restarted by writing a 1 to the FLEX_SPI_CR.REQCLR bit. The value programmed in VAL1 and VAL2 fields must not exceed the maximum value of the received character (see BITS field in SPI Chip Select Register (FLEX_SPI_CSR)). Figure 47-75: Receive Data Register Management CMPMODE = 1, VAL1 = VAL2 = 0x06 Peripheral Clock NSS MOSI 0x0F 0x06 0xF0 0x08 0x06 RDRF rising enabled RDRF Write REQCLR RDR 47.8.6 0x0F 0x06 0xF0 0x08 0x06 SPI Asynchronous and Partial Wakeup (SleepWalking) This operating mode is a means of data preprocessing that qualifies an incoming event, thus allowing the SPI to decide whether or not to wake up the system. Asynchronous and partial wakeup is mainly used when the system is in Wait mode (refer to Section 33. “Power Management Controller (PMC)” for further details). It can also be enabled when the system is fully running. Asynchronous and partial wakeup can be used only when SPI is configured in Slave mode (FLEX_SPI_MR.MSTR is cleared). The maximum SPI clock (SPCK) frequency that can be provided by the SPI master is bounded by the peripheral clock frequency. The SPCK frequency must be lower than or equal to the peripheral clock. The NSS line must be deasserted by the SPI master between two characters. The NSS deassertion duration time must be greater than or equal to six peripheral clock periods. The time between the assertion of NSS line (falling edge) and the first edge of the SPI clock must be higher than 15 µs. DS60001476B-page 1476  2017 Microchip Technology Inc. SAMA5D2 SERIES The FLEX_SPI_RDR register must be read before enabling the asynchronous and partial wakeup. When asynchronous and partial wakeup is enabled for the SPI (refer to Section 33. “Power Management Controller (PMC)”), the PMC decodes a clock request from the SPI. The request is generated as soon as there is a falling edge on the NSS line as this may indicate the beginning of a frame. If the system is in Wait mode (processor and peripheral clocks switched off), the PMC restarts the fast RC oscillator and provides the clock only to the SPI. The SPI processes the received frame and compares the received character with VAL1 and VAL2 in FLEX_SPI_CMPR (Section 47.10.57 “SPI Comparison Register”). The SPI instructs the PMC to disable the peripheral clock if the received character value does not meet the conditions defined by VAL1 and VAL2 fields in FLEX_SPI_CMPR (see Figure 47-77). If the received character value meets the conditions, the SPI instructs the PMC to exit the system from Wait mode (see Figure 47-77). The VAL1 and VAL2 fields can be programmed to provide different comparison methods and thus matching conditions. • If VAL1 equals VAL2, then the comparison is performed on a single value and the wakeup is triggered if the received character equals VAL1. • If VAL1 is strictly lower than VAL2, then any value between VAL1 and VAL2 wakes up the system. • If VAL1 is strictly higher than VAL2, the wakeup is triggered if any received character equals VAL1 or VAL2. • If VAL1 = 0 and VAL2 = 65535, the wakeup is triggered as soon as a character is received. If the processor and peripherals are running, the SPI can be configured in Asynchronous and Partial Wakeup mode by enabling the PMC_SLPWK_ER (refer to Section 33. “Power Management Controller (PMC)”). When activity is detected on the receive line, the SPI requests the clock from the PMC and the comparison is performed. If there is a comparison match, the SPI continues to request the clock. If there is no match, the clock is switched off for the SPI only, until a new activity is detected. The CMPMODE configuration has no effect when Asynchronous and Partial Wakeup mode is enabled for the SPI (refer to PMC_SLPWK_ER in Section 33. “Power Management Controller (PMC)”). When the system is in Active mode and the SPI enters Asynchronous and Partial Wakeup mode, the flag RDRF must be programmed as the unique source of the SPI interrupt. When the system exits Wait mode as the result of a matching condition, the RDRF flag is used to determine if the SPI is the source for the exit from Wait mode. Figure 47-76: Asynchronous Wakeup Use Case Example Case with VAL1 = VAL2 = 0x55 NSS Idle Idle MOSI RHR = 0x55, VAL1 = 0x55 => match PCLK_req PCLK (Main RC) 5us SystemWakeUp_req  2017 Microchip Technology Inc. DS60001476B-page 1477 SAMA5D2 SERIES Figure 47-77: Asynchronous Event Generating Only Partial Wakeup Case with VAL1 = VAL2 = 0x55 NSS Idle Idle MOSI RHR = 0x7F, VAL1 = 0x55 No Match PCLK_req PCLK (Main RC) 5us SystemWakeUp_req 47.8.7 47.8.7.1 SPI FIFOs Overview The SPI includes two FIFOs which can be enabled/disabled using the FLEX_SPI_CR.FIFOEN/FIFODIS. It is recommended to disable the SPI module before enabling or disabling the SPI FIFOs (FLEX_SPI_CR.SPIDIS). Writing FLEX_SPI_CR.FIFOEN to ‘1’ enables a FIFO_DEPTH-data Transmit FIFO and a FIFO_DEPTH-data Receive FIFO. It is possible to write or to read single or multiple data in the same access to FLEX_SPI_TDR/RDR. See Section 47.8.7.6 ”SPI Single Data Mode” and Section 47.8.7.7 ”SPI Multiple Data Mode”. Figure 47-78: FIFOs Block Diagram SPI Transmit FIFO Receive FIFO ....... TD3 FLEX_SPI_TDR write TD2 Threshold TD0 RD2 Threshold ....... RD1 ....... RD0 Tx shifter (Master) MOSI (Slave) MISO 47.8.7.2 ....... RD3 TD1 FLEX_SPI_RDR read Rx shifter (Master) MISO (Slave) MOSI Sending Data with FIFO Enabled When the Transmit FIFO is enabled, write access to FLEX_SPI_TDR loads the Transmit FIFO. DS60001476B-page 1478  2017 Microchip Technology Inc. SAMA5D2 SERIES The FIFO level is provided in FLEX_SPI_FLR.TXFL. If the FIFO can accept the number of data to be transmitted, there is no need to monitor FLEX_SPI_SR.TDRE and the data can be successively written in FLEX_SPI_TDR. If the FIFO cannot accept the data due to insufficient space, wait for the TDRE flag to be set before writing the data in FLEX_SPI_TDR. When the space in the FIFO allows only a portion of the data to be written, the TDRE flag must be monitored before writing the remaining data. Figure 47-79: Sending Data with FIFO Enabled BEGIN Read FLEX_SPI_FLR.TXFL Yes Enough space in Transmit FIFO to write the data to send? Write FLEX_SPI_TDR No Read FLEX_SPI_SR TDRE = 1 ? No No Data has been written in FLEX_SPI_TDR ? Yes Yes Write FLEX_SPI_TDR No All data has been written in FLEX_SPI_TDR ? Yes Read FLEX_SPI_SR No TXEMPTY = 1 ? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1479 SAMA5D2 SERIES 47.8.7.3 Receiving Data with FIFO Enabled When the Receive FIFO is enabled, FLEX_SPI_RDR access reads the FIFO. When data are present in the Receive FIFO (RDRF flag set to ‘1’), the exact number of data can be checked with FLEX_SPI_FLR.RXFL. All the data can be read successively in FLEX_SPI_RDR without checking the RDRF flag between each access. Figure 47-80: Receiving Data with FIFO Enabled BEGIN Read FLEX_SPI_SR RDRF = 1 ? No Yes Read FLEX_SPI_FLR.RXFL and get the number of data in Receive FIFO Read FLEX_SPI_RDR All data has been read in FLEX_SPI_RDR ? No Yes END 47.8.7.4 Clearing/Flushing FIFOs Each FIFO can be cleared/flushed using FLEX_SPI_CR.TXFCLR/RXFCLR. 47.8.7.5 TXEMPTY, TDRE and RDRF Behavior FLEX_SPI_SR.TXEMPTY, FLEX_SPI_SR.TDRE and FLEX_SPI_SR.RDRF flags display a specific behavior when FIFOs are enabled. The TXEMPTY flag is cleared as long as there are characters in the Transmit FIFO or in the internal shift register. TXEMPTY is set when there are no characters in the Transmit FIFO and in the internal shift register. TDRE indicates if a data can be written in the Transmit FIFO. Thus the TDRE flag is set as long as the Transmit FIFO can accept new data. See Figure 47-81. RDRF indicates if an unread data is present in the Receive FIFO. Thus the RDRF flag is set as soon as one unread data is in the Receive FIFO. See Figure 47-82. TDRE and RDRF behavior can be modified using the TXRDYM and RXRDYM fields in the SPI FIFO Mode Register (FLEX_SPI_FMR) to reduce the number of accesses to FLEX_SPI_TDR/RDR. However, for some configurations, the following constraints apply: • When the Variable Peripheral Select mode is used (FLEX_SPI_MR.PS=1), TXRDYM/RXRDYM must be cleared. • In Master mode (FLEX_SPI_MR.MSTR=1), RXRDYM must be cleared. As an example, in Master mode, the Transmit FIFO can be loaded with multiple data in the same access by configuring TXRDYM>0. See SPI FIFO Mode Register for the FIFO configuration. DS60001476B-page 1480  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-81: TDRE in Single Data Mode and TXRDYM = 0 1 3 2 SPCK NPCS0 MOSI MSB 6 (from master) MISO MSB (from slave) 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB Write FLEX_SPI_TDR Read FLEX_SPI_SR TDRE TXFFF 1 0 1 TXFL 2 3 2 FIFO size -1 FIFO full FIFO size -1 TXEMPTY Figure 47-82: RDRF in Single Data Mode and RXRDYM = 0 1 3 2 SPCK NPCS0 MOSI (from master) MISO (from slave) MSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB MSB 6 5 4 3 2 1 LSB MSB Read FLEX_SPI_RDR Read FLEX_SPI_SR RDRF RXFFF RXFEF RXFL  2017 Microchip Technology Inc. 0 1 FIFO full FIFO size -1 0 DS60001476B-page 1481 SAMA5D2 SERIES 47.8.7.6 SPI Single Data Mode In Single Data mode, only one data is written every time FLEX_SPI_TDR is accessed, and only one data is read every time FLEX_SPI_RDR is accessed. When FLEX_SPI_FMR.TXRDYM = 0, the Transmit FIFO operates in Single Data mode. When FLEX_SPI_FMR.RXRDYM = 0, the Receive FIFO operates in Single Data mode. If Master mode is used (FLEX_SPI_MR.MSTR=1), the Receive FIFO must operate in Single Data mode. If Variable Peripheral Select mode is used (FLEX_SPI_MR.PS=1), the Transmit FIFO must operate in Single Data mode. See Section 47.10.48 ”SPI Transmit Data Register” and Section 47.10.45 ”SPI Receive Data Register”. • DMAC When FIFOs operate in Single Data mode, the DMAC transfer type must be configured either in bytes, halfwords or words depending on FLEX_SPI_MR.PS bit value and FLEX_SPI_CSRx.BITS field value. The same applies when FIFOs are disabled. 47.8.7.7 SPI Multiple Data Mode Multiple Data mode minimizes the number of accesses by concatenating the data to send/read in one access. When FLEX_SPI_FMR.TXRDYM > 0, the Transmit FIFO operates in Multiple Data mode. When FLEX_SPI_FMR.RXRDYM > 0, the Receive FIFO operates in Multiple Data mode. Multiple data can be read from the Receive FIFO only in Slave mode (FLEX_SPI_MR.MSTR=0). The Transmit FIFO can be loaded with multiple data in the same access by configuring TXRDYM>0 and when FLEX_SPI_MR.PS=0. In Multiple Data mode, up to two data can be written in one FLEX_SPI_TDR write access. It is also possible to read up to four data in one FLEX_SPI_RDR access if FLEX_SPI_CSRx.BITS is configured to ‘0’ (8-bit data size) and up to two data if FLEX_SPI_CSRx.BITS is configured to a value other than ‘0’ (more than 8-bit data size). The number of data to write/read is defined by the size of the register access. If the access is a byte-size register access, only one data is written/read. If the access is a halfword size register access, then up to two data are read and only one data is written. Lastly, if the access is a word-size register access, then up to four data are read and up to two data are written. Written/read data are always right-aligned, as described in Section 47.10.46 ”SPI Receive Data Register (FIFO Multiple Data, 8-bit)”, Section 47.10.47 ”SPI Receive Data Register (FIFO Multiple Data, 16-bit)” and Section 47.10.49 ”SPI Transmit Data Register (FIFO Multiple Data, 8- to 16-bit)”. As an example, if the Transmit FIFO is empty and there are six data to send, either of the following write accesses may be performed: • six FLEX_SPI_TDR-byte write accesses • three FLEX_SPI_TDR-halfword write accesses With a Receive FIFO containing six data, any of the following read accesses may be performed: • • • • six FLEX_SPI_RDR-byte read accesses three FLEX_SPI_RDR-halfword read accesses one FLEX_SPI_RDR-word read access and one FLEX_SPI_RDR-halfword read access TDRE and RDRF Configuration In Multiple Data mode, it is possible to write one or more data in the same FLEX_SPI_TDR/RDR access. The TDRE flag indicates if one or more data can be written in the FIFO depending on the configuration of FLEX_SPI_FMR.TXRDYM/RXRDYM. As an example, if two data are written each time in FLEX_SPI_TDR, it is useful to configure the TXRDYM field to the value ‘1’ so that the TDRE flag is at ‘1’ only when at least two data can be written in the Transmit FIFO. Similarly, if four data are read each time in FLEX_SPI_RDR, it is useful to configure the RXRDYM field to the value ‘2’ so that the RDRF flag is at ‘1’ only when at least four unread data are in the Receive FIFO. • DMAC It is mandatory to configure DMAC channel size (byte, halfword or word) according to FLEX_SPI_FMR.TXRDYM/RXRDYM configuration. See Section 47.8.7.7 ”SPI Multiple Data Mode” for constraints. 47.8.7.8 FIFO Pointer Error A FIFO overflow is reported in FLEX_SPI_SR. If the Transmit FIFO is full and a write access is performed on FLEX_SPI_TDR, it generates a Transmit FIFO pointer error and sets FLEX_SPI_SR.TXFPTEF. DS60001476B-page 1482  2017 Microchip Technology Inc. SAMA5D2 SERIES In Multiple Data mode, if the number of data written in FLEX_SPI_TDR (according to the register access size) is greater than the free space in the Transmit FIFO, a Transmit FIFO pointer error is generated and FLEX_SPI_SR.TXFPTEF is set. A FIFO underflow is reported in FLEX_SPI_SR. In Multiple Data mode, if the number of data read in FLEX_SPI_RDR (according to the register access size) is greater than the number of unread data in the Receive FIFO, a Receive FIFO pointer error is generated and FLEX_SPI_SR.RXFPTEF is set. No pointer error occurs if the FIFO state/level is checked before writing/reading in FLEX_SPI_TDR/SPI_RDR. The FIFO state/level can be checked either with TXRDY, RXRDY, TXFL or RXFL. When a pointer error occurs, other FIFO flags may not behave as expected; their states should be ignored. If a pointer error occurs, a software reset must be performed using FLEX_SPI_CR.SWRST (configuration will be lost). 47.8.7.9 FIFO Thresholds Each Transmit and Receive FIFO includes a threshold feature used to set a flag and an interrupt when a FIFO threshold is crossed. Thresholds are defined as a number of data in the FIFO, and the FIFO state (TXFL or RXFL) represents the number of data currently in the FIFO. The Transmit FIFO threshold can be set using the field FLEX_SPI_FMR.TXFTHRES. Each time the Transmit FIFO level goes from ‘above threshold’ to ‘equal or below threshold’, the flag FLEX_SPI_SR.TXFTHF is set. The application is warned that the Transmit FIFO has reached the defined threshold and that it can be reloaded. The Receive FIFO threshold can be set using the field FLEX_SPI_FMR.RXFTHRES. Each time the Receive FIFO level goes from ‘below threshold’ to ‘equal or above threshold’, the flag FLEX_SPI_SR.RXFTHF is set. The application is warned that the Receive FIFO has reached the defined threshold and that it can be read to prevent an underflow. The TXFTHF and RXFTHF flags can be configured to generate an interrupt using FLEX_SPI_IER and FLEX_SPI_IDR. 47.8.7.10 FIFO Flags FIFOs come with a set of flags which can be configured to generate interrupts through FLEX_SPI_IER and FLEX_SPI_IDR. FIFO flags state can be read in FLEX_SPI_SR. They are cleared when FLEX_SPI_SR is read. 47.8.8 SPI Register Write Protection The FLEXCOM operating mode (FLEX_MR.OPMODE) must be set to FLEX_MR_OPMODE_SPI to enable access to the write protection registers. To prevent any single software error from corrupting SPI behavior, certain registers in the address space can be write-protected by setting the WPEN (Write Protection Enable) bit in the SPI Write Protection Mode Register (FLEX_SPI_WPMR). If a write access to a write-protected register is detected, the Write Protection Violation Status (WPVS) flag in the SPI Write Protection Status Register (FLEX_SPI_WPSR) is set and the Write Protection Violation Source (WPVSRC) field indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading FLEX_SPI_WPSR. The following register(s) can be write-protected when WPEN is set: • SPI Mode Register • SPI Chip Select Register • SPI Comparison Register 47.9 47.9.1 TWI Functional Description Transfer Format The data put on the TWD line must be 8 bits long. Data are transferred MSB first; each byte must be followed by an acknowledgement. The number of bytes per transfer is unlimited (see Figure 47-84). Each transfer begins with a START condition and terminates with a STOP condition (see Figure 47-83). • A high-to-low transition on the TWD line while TWCK is high defines the START condition. • A low-to-high transition on the TWD line while TWCK is high defines a STOP condition.  2017 Microchip Technology Inc. DS60001476B-page 1483 SAMA5D2 SERIES Figure 47-83: START and STOP Conditions TWD TWCK Start Figure 47-84: Stop Transfer Format TWD TWCK Start 47.9.2 Address R/W Ack Data Ack Data Ack Stop Modes of Operation The TWI has different modes of operation: • • • • • • Master Transmitter mode (Standard and Fast modes only) Master Receiver mode (Standard and Fast modes only) Multi-master Transmitter mode (Standard and Fast modes only) Multi-master Receiver mode (Standard and Fast modes only) Slave Transmitter mode (Standard, Fast and High-speed modes) Slave Receiver mode (Standard, Fast and High-speed modes) These modes are described in the following sections. 47.9.3 Master Mode 47.9.3.1 Definition The master is the device that starts a transfer, generates a clock and stops it. This operating mode is not available if High-speed mode is selected. 47.9.3.2 Programming Master Mode The following fields must be programmed before entering Master mode: 1. 2. 3. 4. DADR (+ IADRSZ + IADR if a 10-bit device is addressed): The device address is used to access slave devices in Read or Write mode. CWGR + CKDIV + CHDIV + CLDIV: Clock waveform. SVDIS: Disables Slave mode. MSEN: Enables Master mode. Note: 47.9.3.3 If the TWI is already in Master mode, the device address (DADR) can be configured without disabling the Master mode. Transfer Speed/Bit Rate The TWI speed is defined in FLEX_TWI_CWGR. The TWI bit rate can be based either on the peripheral clock if the BRSRCCLK bit value is 0 or on a programmable clock source provided by the GCLK if the BRSRCCLK bit value is 1. If BRSRCCLK = 1, the bit rate is independent of the processor/peripheral clock and thus processor/peripheral clock frequency can be changed without affecting the TWI transfer rate. The GCLK frequency must be at least three times lower than the peripheral clock frequency. 47.9.3.4 Master Transmitter Mode This operating mode is not available if High-speed mode is selected. DS60001476B-page 1484  2017 Microchip Technology Inc. SAMA5D2 SERIES After the master initiates a START condition when writing into the Transmit Holding register FLEX_TWI_THR, it sends a 7-bit slave address, configured in the Master Mode Register (DADR in FLEX_TWI_MMR), to notify the slave device. The bit following the slave address indicates the transfer direction, 0 in this case (FLEX_TWI_MMR.MREAD = 0). The TWI transfers require the slave to acknowledge each received byte. During the acknowledge clock pulse (ninth pulse), the master releases the data line (HIGH), enabling the slave to pull it down in order to generate the acknowledge. If the slave does not acknowledge the byte, then the Not Acknowledge flag (NACK) is set in the TWI Status Register (FLEX_TWI_SR) of the master and a STOP condition is sent. The NACK flag must be cleared by reading the TWI Status Register (FLEX_TWI_SR) before the next write into the TWI Transmit Holding Register (FLEX_TWI_THR). As with the other status bits, an interrupt can be generated if enabled in the interrupt enable Register (FLEX_TWI_IER). If the slave acknowledges the byte, the data written in FLEX_TWI_THR is then shifted in the internal shifter and transferred. When an acknowledge is detected, the TXRDY bit is set until a new write in FLEX_TWI_THR. TXRDY is used as transmit ready for the DMA transmit channel. Note: To clear the TXRDY flag in Master mode, write the FLEX_TWI_CR.MSDIS bit to 1, then write the FLEX_TWI_CR.MSEN bit to 1. While no new data is written in FLEX_TWI_THR, the serial clock line is tied low. When new data is written in FLEX_TWI_THR, the SCL is released and the data is sent. To generate a STOP event, the STOP command must be performed by writing in the STOP field of the TWI Control Register (FLEX_TWI_CR). After a master write transfer, the Serial Clock line is stretched (tied low) while no new data is written in FLEX_TWI_THR or until a STOP command is performed. See Figure 47-85, Figure 47-86, and Figure 47-87. Figure 47-85: Master Write with One Data Byte STOP Command sent (write in FLEX_TWI_CR) TWD S DADR W A DATA A P TXCOMP TXRDY Write FLEX_TWI_THR (DATA)  2017 Microchip Technology Inc. DS60001476B-page 1485 SAMA5D2 SERIES Figure 47-86: Master Write with Multiple Data Bytes STOP command performed (by writing in FLEX_TWI_CR) S TWD DADR W A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP TXRDY Write FLEX_TWI_THR (Data n) Write FLEX_TWI_THR (Data n+1) Figure 47-87: Write FLEX_TWI_THR (Data n+2) Last data sent Master Write with One Byte Internal Address and Multiple Data Bytes STOP command performed (by writing in FLEX_TWI_CR) TWD S DADR W A IADR A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP TXRDY Write FLEX_TWI_THR (Data n) Write FLEX_TWI_THR (Data n+1) 47.9.3.5 Write FLEX_TWI_THR (Data n+2) Last data sent Master Receiver Mode Master Receiver mode is not available if High-speed mode is selected. The read sequence begins by setting the START bit. After the start condition has been sent, the master sends a 7-bit slave address to notify the slave device. The bit following the slave address indicates the transfer direction, 1 in this case (FLEX_TWI_MMR.MREAD = 1). During the acknowledge clock pulse (9th pulse), the master releases the data line (HIGH), enabling the slave to pull it down in order to generate the acknowledge. The master polls the data line during this clock pulse and sets the FLEX_TWI_SR.NACK bit if the slave does not acknowledge the byte. If an acknowledge is received, the master is then ready to receive data from the slave. After data has been received, the master sends an acknowledge condition to notify the slave that the data has been received except for the last data (see Figure 47-88). When the FLEX_TWI_SR.RXRDY bit is set, a character has been received in the Receive Holding Register (FLEX_TWI_RHR). The RXRDY bit is reset when reading FLEX_TWI_RHR. When a single data byte read is performed, with or without internal address (IADR), the START and STOP bits must be set at the same time. See Figure 47-88. When a multiple data byte read is performed, with or without internal address (IADR), the STOP bit must be set after the next-to-last data received (same condition applies for START bit to generate a repeated start). See Figure 47-89. For internal address usage, see Section 47.9.3.6 “Internal Address”. DS60001476B-page 1486  2017 Microchip Technology Inc. SAMA5D2 SERIES If FLEX_TWI_RHR is full (RXRDY high) and the master is receiving data, the serial clock line will be tied low before receiving the last bit of the data and until FLEX_TWI_RHR is read. Once FLEX_TWI_RHR is read, the master will stop stretching the serial clock line and end the data reception. See Figure 47-90. Warning: When receiving multiple bytes in Master Read mode, if the next-to-last access is not read (the RXRDY flag remains high), the last access will not be completed until FLEX_TWI_RHR is read. The last access stops on the next-to-last bit (clock stretching). When FLEX_TWI_RHR is read there is only half a bit period to send the STOP bit (or START bit) command, else another read access might occur (spurious access). A possible workaround is to set the STOP bit (or START bit) before reading FLEX_TWI_RHR on the next-to-last access (within IT handler). Figure 47-88: Master Read with One Data Byte S TWD DADR R A DATA N P TXCOMP Write START & STOP Bit RXRDY Read RHR Figure 47-89: TWD S Master Read with Multiple Data Bytes DADR R A DATA n A DATA (n+1) A DATA (n+m)-1 A DATA (n+m) P N TXCOMP Write START Bit RXRDY Read RHR DATA n Read RHR DATA (n+1) Read RHR DATA (n+m)-1 Read RHR DATA (n+m) Write STOP Bit after next-to-last data read Figure 47-90: Master Read Clock Stretching with Multiple Data Bytes STOP command performed (by writing in FLEX_TWI_CR) Clock Streching TWD S DADR W A DATA n A DATA n+1 A DATA n+2 A P TWCK TXCOMP RXRDY Read RHR (Data n)  2017 Microchip Technology Inc. Read RHR (Data n+1) Read RHR (Data n+2) DS60001476B-page 1487 SAMA5D2 SERIES RXRDY is used as receive ready trigger event for the DMA receive channel. 47.9.3.6 Internal Address The TWI interface can perform transfers with 7-bit slave address devices and with 10-bit slave address devices. • 7-bit Slave Addressing When addressing 7-bit slave devices, the internal address bytes are used to perform random address (read or write) accesses to reach one or more data bytes, e.g., within a memory page location in a serial memory. When performing read operations with an internal address, the TWI performs a write operation to set the internal address into the slave device, and then switch to Master Receiver mode. Note that the second start condition (after sending the IADR) is sometimes called “repeated start” (Sr) in I2C fully-compatible devices. See Figure 4792. See Figure 47-91 and Figure 47-93 for the master write operation with internal address. The three internal address bytes are configurable through the Master Mode Register (FLEX_TWI_MMR). If the slave device supports only a 7-bit address, i.e., no internal address, IADRSZ must be configured to 0. The abbreviations listed below are used in Figure 47-91 and Figure 47-92: Table 0-1. S Start Sr Repeated Start P Stop W Write R Read A Acknowledge N Not Acknowledge DADR Device Address IADR Internal Address Figure 47-91: Master Write with One, Two or Three Bytes Internal Address and One Data Byte Three bytes internal address TWD S DADR W A IADR(23:16) A IADR(15:8) A IADR(7:0) A W A IADR(15:8) A IADR(7:0) A DATA A W A IADR(7:0) A DATA A DATA A P Two bytes internal address TWD S DADR P One byte internal address TWD S Figure 47-92: DADR P Master Read with One, Two or Three Bytes Internal Address and One Data Byte Three bytes internal address TWD S DADR W A IADR(23:16) A IADR(15:8) A IADR(7:0) A Sr DADR R A DATA N P Two bytes internal address TWD S DADR W A IADR(15:8) A IADR(7:0) A Sr W A IADR(7:0) A Sr R A DADR R A DATA N P One byte internal address TWD S DADR DADR DATA N P • 10-bit Slave Addressing DS60001476B-page 1488  2017 Microchip Technology Inc. SAMA5D2 SERIES For a slave address higher than seven bits, the user must configure the address size (IADRSZ) and set the other slave address bits in the Internal Address Register (FLEX_TWI_IADR). The two remaining internal address bytes, IADR[15:8] and IADR[23:16], can be used the same way as in 7-bit slave addressing. Example: Address a 10-bit device (10-bit device address is b1 b2 b3 b4 b5 b6 b7 b8 b9 b10) 1. 2. 3. Program IADRSZ = 1, Program DADR with 1 1 1 1 0 b1 b2 (b1 is the MSB of the 10-bit address, b2, etc.) Program FLEX_TWI_IADR with b3 b4 b5 b6 b7 b8 b9 b10 (b10 is the LSB of the 10-bit address) Figure 47-93 shows a byte write to an AT24LC512 EEPROM. This demonstrates the use of internal addresses to access the device. Figure 47-93: Internal Address Usage S T A R T Device Address W R I T E FIRST WORD ADDRESS SECOND WORD ADDRESS S T O P DATA 0 M S B 47.9.3.7 LR A S / C BW K M S B A C K LA SC BK A C K Repeated Start In addition to Internal Address mode, repeated start (Sr) can be generated manually by writing the START bit at the end of a transfer instead of the STOP bit. In such case the parameters of the next transfer (direction, SADR, etc.) will need to be set before writing the START bit at the end of the previous transfer. See Section 47.9.3.13 “Read/Write Flowcharts” for detailed flowcharts. Note that generating a repeated start after a single data read is not supported. 47.9.3.8 Bus Clear Command The TWI interface can perform a Bus Clear Command: 1. 2. Configure the Master mode (DADR, CKDIV, etc). Start the transfer by setting the FLEX_TWI_CR.CLEAR bit. Note: 47.9.3.9 If an alternative command is used (ACMEN bit = 1), the DATAL field must be cleared. SMBus Mode SMBus mode is enabled when the FLEX_TWI_CR.SMBEN bit is written to one. SMBus mode operation is similar to I²C operation with the following exceptions: 1. 2. Only 7-bit addressing can be used. The SMBus standard describes a set of timeout values to ensure progress and throughput on the bus. These timeout values must be programmed into FLEX_TWI_SMBTR. 3. Transmissions can optionally include a CRC byte, called Packet Error Check (PEC). 4. A set of addresses has been reserved for protocol handling, such as alert response address (ARA) and host header (HH) address. Address matching on these addresses can be enabled by configuring FLEX_TWI_CR appropriately. • Packet Error Checking Each SMBus transfer can optionally end with a CRC byte, called the PEC byte. Writing the FLEX_TWI_CR.PECEN bit to one enables automatic PEC handling in the current transfer. Transfers with and without PEC can freely be intermixed in the same system, since some slaves may not support PEC. The PEC LFSR is always updated on every bit transmitted or received, so that PEC handling on combined transfers will be correct. In Master Transmitter mode, the master calculates a PEC value and transmits it to the slave after all data bytes have been transmitted. Upon reception of this PEC byte, the slave will compare it to the PEC value it has computed itself. If the values match, the data was received correctly, and the slave will return an ACK to the master. If the PEC values differ, data was corrupted, and the slave will return a NACK value. Some slaves may not be able to check the received PEC in time to return a NACK if an error occurred. In this case, the slave should always return an ACK after the PEC byte, and some other mechanism must be implemented to verify that the transmission was received correctly.  2017 Microchip Technology Inc. DS60001476B-page 1489 SAMA5D2 SERIES In Master Receiver mode, the slave calculates a PEC value and transmits it to the master after all data bytes have been transmitted. Upon reception of this PEC byte, the master will compare it to the PEC value it has computed itself. If the values match, the data was received correctly. If the PEC values differ, data was corrupted, and the FLEX_TWI_SR.PECERR bit is set. In Master Receiver mode, the PEC byte is always followed by a NACK transmitted by the master, since it is the last byte in the transfer. In combined transfers, the PECRQ bit should only be set in the last of the combined transfers. If Alternative Command mode is enabled, only the NPEC bit should be set. Consider the following transfer: S, ADR+W, COMMAND_BYTE, ACK, SR, ADR+R, DATA_BYTE, ACK, PEC_BYTE, NACK, P See Section 47.9.3.13 “Read/Write Flowcharts” for detailed flowcharts. • Timeouts The FLEX_TWI_SMBTR.TLOWS/TLOWM fields configure the SMBus timeout values. If a timeout occurs, the master transmits a STOP condition and leaves the bus. Furthermore, the FLEX_TWI_SR.TOUT bit is set. 47.9.3.10 SMBus Quick Command (Master Mode Only) The TWI interface can perform a quick command: 1. 2. 3. Configure the Master mode (DADR, CKDIV, etc). Write the FLEX_TWI_MMR.MREAD bit at the value of the one-bit command to be sent. Start the transfer by setting the FLEX_TWI_CR.QUICK bit. Note: If an alternative command is used (ACMEN bit = 1), the DATAL field must be cleared. Figure 47-94: SMBus Quick Command TWD S DADR R/W A P TXCOMP TXRDY Write QUICK command in FLEX_TWI_CR 47.9.3.11 Alternative Command Another way to configure the transfer is to enable the Alternative Command mode with the ACMEN bit of the TWI Control Register. In this mode, the transfer is configured through the TWI Alternative Command Register. It is possible to define a simple read or write transfer or a combined transfer with a repeated start. In order to set a simple transfer, the DATAL field and the DIR field of the TWI Alternative Command Register must be filled accordingly and the NDATAL field must be cleared. To begin the transfer, either set the START bit in the TWI Control Register in case of a read transfer, or write the TWI Transmit Holding Register in case of a write transfer. For a combined transfer linked by a repeated start, the NDATAL field must be filled with the length of the second transfer and NDIR with the corresponding direction. The PEC and NPEC bits are used to set a PEC field. In the case of a single transfer with PEC, the PEC bit must be set. In the case of a combined transfer, the NPEC bit must be set. Note: If the Alternative Command mode is used, the TWIHS_MMR.IADRSZ field must be set to 0. See Section 47.9.3.13 “Read/Write Flowcharts” for detailed flowcharts. 47.9.3.12 Handling Errors in Alternative Command In case of NACK generated by a slave device or SMBus timeout error, the TWI stops immediately the frame, but the DMA transfer may still be active. To prevent a new frame to be restarted with the remaining DMA data (transmit), the TWI prevents any start of frame until the FLEX_TWI_SR.LOCK flag is cleared. The FLEX_TWI_SR.LOCK bit indicates the state of the TWI (locked or not locked). DS60001476B-page 1490  2017 Microchip Technology Inc. SAMA5D2 SERIES When the TWI is locked, no transfer can begin until the LOCK is cleared using the FLEX_TWI_CR.LOCKCLR bit and until the error flags are cleared reading FLEX_TWI_SR. In case of error, FLEX_TWI_THR may have been loaded with a new data. The FLEX_TWI_CR.THRCLR bit can be used to flush FLEX_TWI_THR. If the THRCLR bit is set, the TXRDY and TXCOMP flags are set. 47.9.3.13 Read/Write Flowcharts The flowcharts shown in Figure 47-96, Figure 47-97, Figure 47-102, Figure 47-103 and Figure 47-104 provide examples for read and write operations. A polling or interrupt method can be used to check the status bits. The interrupt method requires that the Interrupt Enable Register (FLEX_TWI_IER) be configured first. Figure 47-95: TWI Write Operation with Single Data Byte without Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address (DADR) - Transfer direction bit Write ==> bit MREAD = 0 Load Transmit register FLEX_TWI_THR = Data to send Write STOP Command FLEX_TWI_CR = STOP Read Status register No TXRDY = 1? Yes Read Status register No TXCOMP = 1? Yes Transfer finished  2017 Microchip Technology Inc. DS60001476B-page 1491 SAMA5D2 SERIES Figure 47-96: TWI Write Operation with Single Data Byte and Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address (DADR) - Internal address size (IADRSZ) - Transfer direction bit Write ==> bit MREAD = 0 Set the internal address FLEX_TWI_IADR = address Load transmit register FLEX_TWI_THR = Data to send Write STOP command FLEX_TWI_CR = STOP Read Status register No TXRDY = 1? Yes Read Status register TXCOMP = 1? No Yes Transfer finished DS60001476B-page 1492  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-97: TWI Write Operation with Multiple Data Bytes with or without Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Write ==> bit MREAD = 0 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Load Transmit register FLEX_TWI_THR = Data to send Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Write STOP Command FLEX_TWI_CR = STOP Read Status register No TXCOMP = 1? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1493 SAMA5D2 SERIES Figure 47-98: SMBus Write Operation with Multiple Data Bytes with or without Internal Address and PEC Sending BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS + SMBEN + PECEN Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Write ==> bit MREAD = 0 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Load Transmit register FLEX_TWI_THR = Data to send Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Write PECRQ Command Write STOP Command FLEX_TWI_CR = STOP & PECRQ Read Status register No TXCOMP = 1? Yes END DS60001476B-page 1494  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-99: SMBus Write Operation with Multiple Data Bytes with PEC and Alternative Command Mode BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: FLEX_TWI_CR = MSEN + SVDIS + ACMEN + SMBEN + PECEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR, PEC Load Transmit register FLEX_TWI_THR = Data to send Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send? Yes No Read Status register No TXCOMP = 1? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1495 SAMA5D2 SERIES Figure 47-100: TWI Write Operation with Multiple Data Bytes and Read Operation with Multiple Data Bytes (Sr) BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Read ==> bit MREAD = 0 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Load Transmit register FLEX_TWI_THR = Data to send Read Status register FLEX_TWI_THR = data to send TXRDY = 1? No Yes Data to send ? Yes No Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - FLEX_TWI_IADR = address (if Internal address size = 0) - Transfer direction bit Read ==> bit MREAD = 1 Set the next transfer parameters and send the repeated start command Start the transfer FLEX_TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read but one? Yes Stop the transfer FLEX_TWI_CR = STOP Read Status register No RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) Read status register TXCOMP = 1? No Yes END DS60001476B-page 1496  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-101: TWI Write Operation with Multiple Data Bytes + Read Operation and Alternative Command Mode + PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, PEC, NDATAL, NPEC - DIR = WRITE - NDIR = READ Load Transmit register FLEX_TWI_THR = Data to send Read Status register FLEX_TWI_THR = data to send TXRDY = 1? No Yes Data to send ? Yes No Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read ? Yes Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1497 SAMA5D2 SERIES Figure 47-102: TWI Read Operation with Single Data Byte without Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS Set the Master Mode register: - Device slave address - Transfer direction bit Read ==> bit MREAD = 1 Start the transfer FLEX_TWI_CR = START | STOP Read status register RXRDY = 1? No Yes Read Receive Holding Register Read Status register No TXCOMP = 1? Yes END DS60001476B-page 1498  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-103: TWI Read Operation with Single Data Byte and Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_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 FLEX_TWI_IADR = address Start the transfer FLEX_TWI_CR = START | STOP Read Status register No RXRDY = 1? Yes Read Receive Holding register Read Status register No TXCOMP = 1? Yes END  2017 Microchip Technology Inc. DS60001476B-page 1499 SAMA5D2 SERIES Figure 47-104: TWI Read Operation with Multiple Data Bytes with or without Internal Address BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_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 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Start the transfer FLEX_TWI_CR = START Read Status register No RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read but one? Yes Stop the transfer FLEX_TWI_CR = STOP Read Status register No RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) Read status register No TXCOMP = 1? Yes END DS60001476B-page 1500  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-105: TWI Read Operation with Multiple Data Bytes with or without Internal Address with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: FLEX_TWI_CR = MSEN + SVDIS + SMBEN + PECEN Set the Master Mode register: - Device slave address - Internal address size (if IADR used) - Transfer direction bit Read ==> bit MREAD = 1 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Start the transfer FLEX_TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read but one ? Yes Check PEC and Stop the transfer FLEX_TWI_CR = STOP & PECRQ Read Status register No RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1501 SAMA5D2 SERIES Figure 47-106: TWI Read Operation with Multiple Data Bytes with Alternative Command Mode with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: FLEX_TWI_CR = MSEN + SVDIS + SMBEN + ACMEN + PECEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR, PEC Start the transfer FLEX_TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read ? Yes Read Status register No RXRDY = 1? Yes Read the received PEC: Read Receive Holding register (FLEX_TWI_RHR) Read status register TXCOMP = 1? No Yes END DS60001476B-page 1502  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-107: TWI Read Operation with Multiple Data Bytes + Write Operation with Multiple Data Bytes (Sr) BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_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 No Internal address size = 0? Set the internal address FLEX_TWI_IADR = address Yes Start the transfer FLEX_TWI_CR = START Read Status register No RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read but one? Yes Set the Master Mode register: - Device slave address - Internal address size (if IADR used) -FLEX_TWI_IADR = address (if Internal address size = 0) - Transfer direction bit Read ==> bit MREAD = 0 Set the next transfer parameters and send the repeated start command Start the transfer (Sr) FLEX_TWI_CR = START Read Status register No Read the last byte of the first read transfer RXRDY = 1? Yes Read Receive Holding register (FLEX_TWI_RHR) Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send ? Yes No Stop the transfer FLEX_TWI_CR = STOP Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1503 SAMA5D2 SERIES Figure 47-108: TWI Read Operation with Multiple Data Bytes + Write with Alternative Command Mode with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, PEC, NDATAL, NPEC - DIR = READ - NDIR = WRITE Start the transfer FLEX_TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read ? Yes Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send ? Yes No Read status register TXCOMP = 1? No Yes END DS60001476B-page 1504  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-109: TWI Read Operation with Multiple Data Bytes + Write with Alternative Command Mode with PEC BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, PEC, NDATAL, NPEC - DIR = READ - NDIR = WRITE Start the transfer FLEX_TWI_CR = START Read Status register RXRDY = 1? No Yes Read Receive Holding register (FLEX_TWI_RHR) No Last data to read ? Yes Read Status register FLEX_TWI_THR = data to send No TXRDY = 1? Yes Data to send ? Yes No Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1505 SAMA5D2 SERIES 47.9.4 47.9.4.1 Multi-Master Mode Definition In Multi-Master mode, 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 that has lost arbitration may put its data on the bus by respecting arbitration. Arbitration is illustrated in Figure 47-111. 47.9.4.2 Different Multi-Master Modes Two Multi-Master modes may be distinguished: • TWI as Master Only—TWI is considered as a master only and will never be addressed. • TWI as Master or Slave—TWI may be either a master or a slave and may be addressed. Note: Arbitration in supported in both Multi-Master modes. • TWI as Master Only In this mode, the 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 user 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 47-110). Note: The state of the bus (busy or free) is not indicated in the user interface. • 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 user must manage the pseudo Multi-Master mode described in the steps below: 1. 2. 3. 4. 5. 6. 7. Program the TWI in Slave mode (SADR + MSDIS + SVEN) and perform a slave access (if TWI is addressed). If the TWI has to be set in Master mode, wait until TXCOMP flag is at 1. Program the Master mode (DADR + SVDIS + MSEN) and start the transfer (ex: START + Write in THR). As soon as the Master mode is enabled, the TWI scans the bus in order to detect if it is busy or free. When the bus is considered as free, the TWI initiates the transfer. 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. If the arbitration is lost (ARBLST is = 1), the user must program the TWI in Slave mode in case the master that won the arbitration needs to access the TWI. If the TWI has to be set in Slave mode, wait until TXCOMP flag is at 1 and then program the Slave mode. Note: In case the arbitration is lost and the TWI is addressed, the TWI will not acknowledge even if it is programmed in Slave mode as soon as ARBLST = 1. Then the master must repeat SADR. DS60001476B-page 1506  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-110: User Sends Data While the Bus is Busy TWCK START sent by the TWI STOP sent by the master DATA sent by a master TWD DATA sent by the TWI Bus is busy Bus is free Transfer is kept TWI DATA transfer A transfer is programmed (DADR + W + START + Write THR) Figure 47-111: Bus is considered as free Transfer is initiated Arbitration Cases TWCK TWD TWCK Data from a Master S 1 0 0 1 1 Data from TWI S 1 0 TWD S 1 0 0 1 P Arbitration is lost TWI stops sending data Data from the master 1 1 P Arbitration is lost S 1 0 1 S 1 0 0 1 1 S 1 0 0 1 1 The master stops sending data Data from the TWI ARBLST Bus is busy Transfer is kept TWI DATA transfer A transfer is programmed (DADR + W + START + Write THR)  2017 Microchip Technology Inc. Bus is free Transfer is stopped Transfer is programmed again (DADR + W + START + Write THR) Bus is considered as free Transfer is initiated DS60001476B-page 1507 SAMA5D2 SERIES The flowchart shown in Figure 47-112 gives an example of read and write operations in Multi-Master mode. Figure 47-112: Multi-Master Mode START Program the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? Yes GACC = 1 ? No No No No SVREAD = 1 ? EOSACC = 1 ? TXRDY = 1 ? Yes No Yes Yes Write in FLEX_TWI_THR No TXCOMP = 1 ? Yes Yes Read FLEX_TWI_RHR Need to perform a master access ? No No RXRDY= 1 ? GENERAL CALL TREATMENT Yes Decoding of the programming sequence No Prog seq OK ? Change SADR Program the Master mode DADR + SVDIS + MSEN + CLK + R / W Read Status Register Yes No ARBLST = 1 ? Yes Yes No MREAD = 1 ? RXRDY= 0 ? TXRDY= 0 ? No No Read FLEX_TWI_RHR Yes Yes Data to read? Data to send ? Yes Write in FLEX_TWI_THR No No Stop Transfer FLEX_TWI_CR = STOP Read Status Register Yes DS60001476B-page 1508 TXCOMP = 0 ? No  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.9.5 Slave Mode 47.9.5.1 Definition 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). 47.9.5.2 Programming Slave Mode The following fields must be programmed before entering Slave mode: 1. 2. 3. 4. FLEX_TWI_SMR.SADR: The slave device address is used in order to be accessed by master devices in Read or Write mode. (Optional) FLEX_TWI_SMR.MASK can be set to mask some SADR address bits and thus allow multiple address matching. FLEX_TWI_CR.MSDIS: Disables the Master mode. FLEX_TWI_CR.SVEN: Enables the Slave mode. As the device receives the clock, values written in FLEX_TWI_CWGR are not processed. 47.9.5.3 Receiving Data After a START or repeated START condition is detected, and if the address sent by the master matches the slave address programmed in the SADR (Slave Address) field, the 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. • Read Sequence In the case of a read sequence (SVREAD is high), the TWI transfers data written in FLEX_TWI_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 is reset. As soon as data is written in FLEX_TWI_THR, the TXRDY (Transmit Holding Register Ready) flag is reset, and it is set when the internal shifter 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 47-113. Note: To clear the TXRDY flag in Slave mode, write the FLEX_TWI_CR.SVDIS bit to 1, then write the FLEX_TWI_CR.SVEN bit to 1. • 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 FLEX_TWI_RHR (TWI Receive Holding Register). RXRDY is reset when reading FLEX_TWI_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 47-114. • Clock Stretching Sequence If FLEX_TWI_THR or FLEX_TWI_RHR is not written/read in time, the TWI performs a clock stretching. Clock stretching information is given by the SCLWS (Clock Wait State) bit. See Figure 47-116 and Figure 47-117. Note: Clock stretching can be disabled by configuring the FLEX_TWI_SMR.SCLWSDIS bit. In that case, UNRE and OVRE flags will indicate underrun (when FLEX_TWI_THR is not filled on time) or overrun (when FLEX_TWI_RHR is not read on time). • General Call In the case where a GENERAL CALL is performed, the GACC (General Call Access) flag is set. After GACC is set, it is up to the user to interpret the meaning of the GENERAL CALL and to decode the new address programming sequence. See Figure 47-115. 47.9.5.4 Data Transfer • Read Operation The Read mode is defined as a data requirement from the master.  2017 Microchip Technology Inc. DS60001476B-page 1509 SAMA5D2 SERIES 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 FLEX_TWI_THR. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 47-113 describes the read operation. Figure 47-113: Read Access Ordered by a Master SADR matches, TWI answers with an ACK SADR does not match, TWI answers with a NACK TWD S ADR R NA DATA NA P/S/Sr SADR R A DATA A ACK/NACK from the Master A DATA NA S/Sr TXRDY Read RHR Write THR NACK SVACC SVREAD SVREAD has to be taken into account only while SVACC is active EOSACC Note 1: When SVACC is low, the state of SVREAD becomes irrelevant. 2: TXRDY is reset when data has been transmitted from FLEX_TWI_THR to the internal shifter and set when this data has been acknowledged or non acknowledged. • 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 FLEX_TWI_RHR. If a STOP condition or a REPEATED START + an address different from SADR is detected, SVACC is reset. Figure 47-114 describes the write operation. Figure 47-114: Write Access Ordered by a Master SADR does not match, TWI answers with a NACK TWD S ADR W NA DATA NA SADR matches, TWI answers with an ACK P/S/Sr SADR W A DATA A Read RHR A DATA NA S/Sr RXRDY SVACC SVREAD SVREAD has to be taken into account only while SVACC is active EOSACC Note 1: When SVACC is low, the state of SVREAD becomes irrelevant. 2: RXRDY is set when data has been transmitted from the internal shifter to FLEX_TWI_RHR, and reset when this data is read. • General Call The general call is performed in order to change the address of the slave. DS60001476B-page 1510  2017 Microchip Technology Inc. SAMA5D2 SERIES If a GENERAL CALL is detected, GACC is set. After the detection of general call, it is up to the user to decode the commands which follow. In case of a WRITE command, the user has to decode the programming sequence and program a new SADR if the programming sequence matches. Figure 47-115 describes the general call access. Figure 47-115: Master Performs a General Call 0000000 + W TXD S GENERAL CALL RESET command = 00000110X WRITE command = 00000100X A Reset or write DADD A DATA1 A DATA2 A New SADR A P New SADR Programming sequence GACC Reset after read SVACC Note: This method allows to create a user-specific programming sequence by choosing the number of programming bytes. The programming sequence has to be provided to the master. • Clock Stretching In both Read and Write modes, it may happen that the FLEX_TWI_THR/FLEX_TWI_RHR buffer is not filled/emptied before the transmission/reception of a new character. In this case, to avoid sending/receiving undesired data, a clock stretching mechanism is implemented. Note: Clock stretching can be disabled by setting the FLEX_TWI_SMR.SCLWSDIS bit. In that case, the UNRE and OVRE flags will indicate an underrun (when FLEX_TWI_THR is not filled on time) or an overrun (when FLEX_TWI_RHR is not read on time). Clock Stretching in Read Mode The clock is tied low if the internal shifter is empty and if a STOP or REPEATED START condition was not detected. It is tied low until the internal shifter is loaded. Figure 47-116 describes the clock stretching in Read mode. Figure 47-116: Clock Stretching in Read Mode FLEX_TWI_THR S SADR R DATA1 1 DATA0 A DATA0 A DATA2 A DATA1 XXXXXXX DATA2 NA S 2 TWCK Write THR CLOCK is tied low by the TWI as long as THR is empty SCLWS TXRDY SVACC SVREAD As soon as a START is detected TXCOMP FLEX_TWI_THR is transmitted to the internal shifter. ACK or NACK from the master 1 The data is memorized in FLEX_TWI_THR until a new value is written. 2 The clock is stretched after the ACK, the state of TWD is undefined during clock stretching.  2017 Microchip Technology Inc. DS60001476B-page 1511 SAMA5D2 SERIES Note 1: TXRDY is reset when data has been written in FLEX_TWI_THR to the internal shifter, 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 stretching mechanism is started. Clock Stretching in Write Mode The clock is tied low if the internal shifter and FLEX_TWI_RHR are full. If a STOP or REPEATED_START condition was not detected, it is tied low until FLEX_TWI_RHR is read. Figure 47-117 describes the clock stretching in Write mode. Figure 47-117: Clock Stretching in Write Mode TWCK CLOCK is tied low by the TWI as long as RHR is full TWD S SADR W A DATA0 FLEX_TWI_RHR A DATA1 A DATA2 DATA0 is not read in the RHR DATA1 NA S ADR DATA2 SCLWS SCL is stretched after the acknowledge of DATA1 RXRDY Rd DATA0 Rd DATA1 Rd DATA2 SVACC SVREAD TXCOMP As soon as a START is detected Note 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 stretching mechanism is started and automatically reset when the mechanism is finished. • 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 47-118 describes the repeated start and the reversal from Read mode to Write mode. DS60001476B-page 1512  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-118: Repeated Start and Reversal from Read Mode to Write Mode FLEX_TWI_THR TWD DATA0 S SADR R A DATA0 DATA1 A DATA1 NA Sr SADR W A DATA2 A DATA3 DATA2 FLEX_TWI_RHR A P DATA3 SVACC SVREAD TXRDY RXRDY EOSACC Cleared after read As soon as a START is detected TXCOMP (1) Note: 1. TXCOMP is only set at the end of the transmission because after the repeated start, SADR is detected again. Reversal of Write to Read The master initiates the communication by a write command and finishes it by a read command. Figure 47-119 describes the repeated start and the reversal from Write mode to Read mode. Figure 47-119: Repeated Start and Reversal from Write Mode to Read Mode DATA2 FLEX_TWI_THR DATA3 (1) TWD S SADR W A DATA0 FLEX_TWI_RHR A DATA1 DATA0 A Sr SADR R A DATA2 A DATA3 NA P DATA1 SVACC SVREAD TXRDY RXRDY Read FLEX_TWI_RHR EOSACC TXCOMP Cleared after read As soon as a START is detected (2) Notes: 1. In this case, if FLEX_TWI_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. • SMBus Mode SMBus mode is enabled when the FLEX_TWI_CR.SMEN bit is written to one. SMBus mode operation is similar to I²C operation with the following exceptions: 1. 2. 3. 4. Only 7-bit addressing can be used. The SMBus standard describes a set of timeout values to ensure progress and throughput on the bus. These timeout values must be programmed into FLEX_TWI_SMBTR. Transmissions can optionally include a CRC byte, called Packet Error Check (PEC). A set of addresses have been reserved for protocol handling, such as alert response address (ARA) and host header (HH) address. Address matching on these addresses can be enabled by configuring FLEX_TWI_CR appropriately. Packet Error Checking Each SMBus transfer can optionally end with a CRC byte, called the PEC byte. Writing the FLEX_TWI_CR.PECEN bit to one will send/ check the FLEX_TWI_ACR.PEC field in the current transfer. The PEC generator is always updated on every bit transmitted or received, so that PEC handling on following linked transfers will be correct.  2017 Microchip Technology Inc. DS60001476B-page 1513 SAMA5D2 SERIES In Slave Receiver mode, the master calculates a PEC value and transmits it to the slave after all data bytes have been transmitted. Upon reception of this PEC byte, the slave will compare it to the PEC value it has computed itself. If the values match, the data was received correctly, and the slave will return an ACK to the master. If the PEC values differ, data was corrupted, and the slave will return a NACK value. The FLEX_TWI_SR.PECERR bit is set automatically if a PEC error occurred. In Slave Transmitter mode, the slave calculates a PEC value and transmits it to the master after all data bytes have been transmitted. Upon reception of this PEC byte, the master will compare it to the PEC value it has computed itself. If the values match, the data was received correctly. If the PEC values differ, data was corrupted, and the master must take appropriate action. See Section 47.9.5.8 “Slave Read/Write Flowcharts” for detailed flowcharts. Timeouts The TWI SMBus Timing Register (FLEX_TWI_SMBTR) configures the SMBus timeout values. If a timeout occurs, the slave will leave the bus. Furthermore, the FLEX_TWI_SR.TOUT bit is set. 47.9.5.5 High-Speed Slave Mode High-speed mode is enabled when the FLEX_TWI_CR.HSEN bit is written to one. Furthermore, the analog pad filter must be enabled, the FLEX_TWI_FILTR.PADFEN bit must be written to one and the FLEX_TWI_FILTR.FILT bit must be cleared. TWI High-speed mode operation is similar to TWI operation with the following exceptions: 1. 2. A master code is received first at normal speed before entering High-speed mode period. When TWI High-speed mode is active, clock stretching is only allowed after acknowledge (ACK), not-acknowledge (NACK), START (S) or repeated START (Sr) (asa consequence, OVF may happen). TWI High-speed mode allows transfers of up to 3.4 Mbit/s. The TWI slave in High-speed mode requires that the peripheral clock runs at a minimum of 14 MHz if slave clock stretching is enabled (SCLWSDIS bit at ‘0’). If slave clock stretching is disabled (SCLWSDIS bit at ‘1’), the peripheral clock must run at a minimum of 11 MHz (assuming the system has no latency). Note 1: When slave clock stretching is disabled, FLEX_TWI_RHR must always be read before receiving the next data (MASTER write frame). It is strongly recommended to use either the polling method on the FLEX_TWI_SR.RXRDY flag, or the DMA. If the receive is managed by an interrupt, the TWI interrupt priority must be set to the right level and its latency minimized to avoid receive overrun. 2: When slave clock stretching is disabled, FLEX_TWI_THR must be filled with the first data to send before the beginning of the frame (MASTER read frame). It is strongly recommended to use either the polling method on the FLEX_TWI_SR.TXRDY flag, or the DMA. If the transmit is managed by an interrupt, the TWI interrupt priority must be set to the right level and its latency minimized to avoid transmit underrun. • Read/Write Operation A TWI high-speed frame always begins with the following sequence: 1. 2. 3. START condition (S) Master Code (0000 1XXX) Not-acknowledge (NACK) When the TWI is programmed in Slave mode and TWI High-speed mode is activated, master code matching is activated and internal timings are set to match the TWI High-speed mode requirements. Figure 47-120: High-Speed Mode Read/Write FS Mode S MASTER CODE HS Mode NA Sr SADR R/W A FS Mode S MASTER CODE DS60001476B-page 1514 FS Mode DATA A/NA P FS Mode HS Mode NA Sr SADR R/W A DATA A/NA Sr SADR P  2017 Microchip Technology Inc. SAMA5D2 SERIES • Usage TWI High-speed mode usage is the same as the standard TWI (see Section 47.9.3.13 “Read/Write Flowcharts”). 47.9.5.6 Alternative Command In Slave mode, the Alternative Command mode is used when the SMBus mode is enabled to send or check the PEC byte. The Alternative Command mode is enabled by setting the ACMEN bit of the TWIHS Control Register, and the transfer is configured in TWIHS_ACR. For a combined transfer with PEC, only the NPEC bit in TWIHS_ACR must be set as the PEC byte is sent once at the end of the frame. See Section 47.9.5.8 “Slave Read/Write Flowcharts” for detailed flowcharts. 47.9.5.7 TWI Asynchronous and Partial Wakeup (SleepWalking) The TWI module includes an asynchronous start condition detector, it is capable of waking the device up from a Sleep mode upon an address match (and optionally an additional data match), including Sleep modes where the TWI peripheral clock is stopped. The FLEX_TWI_RHR register must be read prior to enable the asynchronous and partial wakeup. After detecting the START condition on the bus, the TWI will stretch TWCK until the TWI peripheral clock has started. The time required for starting the TWI peripheral depends on which Sleep mode the device is in. After the TWI peripheral clock has started, the TWI releases its TWCK stretching and receives one byte of data (slave address) on the bus. At this time, only a limited part of the device, including the TWI module, receives a clock, thus saving power. If the address phase causes a TWIS address match (and optionally if the first data byte causes data match as well), the entire device is wakened and normal TWI address matching actions are performed. Normal TWI transfer then follows. If the TWI module is not addressed (or if the optional data match fails), the TWI peripheral clock is automatically stopped and the device returns to its original Sleep mode. The TWI module has the capability to match on more than one address. The FLEX_TWI_SMR.SADR1EN/SADR2EN/SADR3EN bits enable address matching on additional addresses which can be configured through the FLEX_TWI_SWMR.SADR1/SADR2/SADR3 fields. The SleepWalking matching process can be extended to the first received data byte if the FLEX_TWI_SMR.DATAMEN bit is set. In that case, a complete matching includes address matching and first received data matching. The FLEX_TWI_SWMR.DATAM field can be used to configure the data to match on the first received byte. When the system is in Active mode and the TWI enters asynchronous partial Wakeup mode, the flag SVACC must be programmed as the unique source of the TWI interrupt and the data match comparison must be disabled. When the system exits Wait mode as the result of a matching condition, the SVACC flag is used to determine if the TWI is the source of the exit from Wait mode. Figure 47-121: Address Match and Data Matching Disabled Address Matching Clock Stretching S PClk SADR R/W A DATA A/NA DATA A/NA P PClk Startup PClk_request SystemWakeUp_req  2017 Microchip Technology Inc. DS60001476B-page 1515 SAMA5D2 SERIES Figure 47-122: Address Does Not Match and Data Matching Disabled Address Matching Clock Stretching SADR Sr PClk R/W NA P A DATA PClk Startup PClk_request SystemWakeUp_req Figure 47-123: Address and Data Match (Data Matching Enabled) Address Matching + Data Matching Clock Stretching Sr PClk SADR W A DATA A/NA P PClk Startup PClk_request SystemWakeUp_req DS60001476B-page 1516  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-124: Address Matches and Data Do Not Match (Data Matching Enabled) Address Matching + Data Matching Clock Stretching Sr PClk SADR W A DATA NA DATA NA P PClk Startup PClk_request SystemWakeUp_req  2017 Microchip Technology Inc. DS60001476B-page 1517 SAMA5D2 SERIES 47.9.5.8 Slave Read/Write Flowcharts The flowchart shown in Figure 47-125 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 (FLEX_TWI_IER) be configured first. Figure 47-125: Read/Write in Slave Mode START Set the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 1 ? TXRDY = 1 ? No No Write in FLEX_TWI_THR No TXCOMP = 1 ? RXRDY = 1 ? No END Read FLEX_TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR DS60001476B-page 1518  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 47-126: Read/Write in Slave Mode with SMBus PEC START Set the SLAVE mode: SADR + MSDIS + SVEN + SMBEN + PECEN Read Status Register SVACC = 1 ? GACC = 1 ? No SVREAD = 1 ? No No No EOSACC = 1 ? TXRDY = 1 ? No RXRDY = 1 ? No Last data sent ? TXCOMP = 1 ? No Last data to read ? Write in FLEX_TWI_THR END No Write in PECRQ Write in PECRQ Read FLEX_TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR  2017 Microchip Technology Inc. DS60001476B-page 1519 SAMA5D2 SERIES Figure 47-127: Read/Write in Slave Mode with SMBus PEC and Alternative Command Mode START Set the SLAVE mode: SADR + MSDIS + SVEN + SMBEN + PECEN + ACMEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 1 ? TXRDY = 1 ? No No Write in FLEX_TWI_THR No TXCOMP = 1 ? RXRDY= 1 ? No END Read FLEX_TWI_RHR GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR DS60001476B-page 1520  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.9.6 TWI FIFOs 47.9.6.1 Overview The TWI includes two FIFOs which can be enabled/disabled using FLEX_TWI_CR.FIFOEN/FIFODIS. It is recommended to disable both Master and Slave modes before enabling or disabling the FIFOs (FLEX_TWI_CR.MSDIS/SVDIS). Writing FLEX_TWI_CR.FIFOEN to ‘1’ enables a 16-data Transmit FIFO and a 16-data Receive FIFO. It is possible to write or to read single or multiple data in the same access to FLEX_TWI_THR/RHR, depending on FLEX_TWI_FMR.TXRDYM/RXRDYM settings. Figure 47-128: FIFOs Block Diagram TWI Transmit FIFO Receive FIFO ....... TXDATA3 FLEX_TWI_THR write TXDATA2 Threshold TXDATA0 ....... RXDATA3 TXDATA1 RXDATA2 Threshold ....... RXDATA1 ....... RXDATA0 Tx shifter FLEX_TWI_RHR read Rx shifter TWD 47.9.6.2 Sending Data with FIFO Enabled When the Transmit FIFO is enabled, write access to FLEX_TWI_THR loads the Transmit FIFO. The Transmit FIFO level is provided in FLEX_TWI_FLR.TXFL. If the FIFO can accept the number of data to be transmitted, there is no need to monitor FLEX_TWI_SR.TXRDY and the data can be successively written in FLEX_TWI_THR. If the FIFO cannot accept the data due to insufficient space, wait for the TXRDY flag to be set before writing the data in FLEX_TWI_THR. When the space in the FIFO allows only a portion of the data to be written, the TXRDY flag must be monitored before writing the remaining data. See Figure 47-129 ”Sending Data with FIFO Enabled in Master Mode” and Figure 47-131 ”Sending/Receiving Data with FIFO Enabled in Slave Mode”.  2017 Microchip Technology Inc. DS60001476B-page 1521 SAMA5D2 SERIES Figure 47-129: Sending Data with FIFO Enabled in Master Mode BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: FLEX_TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL, DIR Yes Enough space in the FIFO to write all the data to send? No Read FLEX_TWI_SR Load Transmit register FLEX_TWI_THR = Data to send No TXRDY = 1? No Yes All the data have been written in FLEX_TWI_THR? Load Transmit register FLEX_TWI_THR = Data to send No All the data have been written in FLEX_TWI_THR ? Read Status register No TXCOMP = 1? Yes END DS60001476B-page 1522  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.9.6.3 Receiving Data with FIFO Enabled When the Receive FIFO is enabled, FLEX_TWI_RHR access reads the FIFO. When data are present in the Receive FIFO (RXRDY flag set to ‘1’), the exact number of data can be checked with FLEX_TWI_FLR.RXFL. All the data can be read successively in FLEX_TWI_RHR without checking the FLEX_TWI_SR.RXRDY flag between each access. See Figure 47-130 ”Receiving Data with FIFO Enabled in Master Mode” and Figure 47-131 ”Sending/Receiving Data with FIFO Enabled in Slave Mode”. Figure 47-130: Receiving Data with FIFO Enabled in Master Mode BEGIN Set TWI clock (CLDIV, CHDIV, CKDIV) in FLEX_TWI_CWGR (Needed only once) Set the Control register: - Master enable FLEX_TWI_CR = MSEN + SVDIS + ACMEN Set the Master Mode register: - Device slave address Set the Alternative Command Register: - DATAL - DIR = READ Start the transfer FLEX_TWI_CR = START Read FLEX_TWI_SR RXRDY = 1? No Yes Read FLEX_TWI_FSR and get the number of data in the Receive FIFO Read FLEX_TWI_RHR All data have been read in FLEX_TWI_RHR? No Yes Read status register TXCOMP = 1? No Yes END  2017 Microchip Technology Inc. DS60001476B-page 1523 SAMA5D2 SERIES 47.9.6.4 Sending/Receiving with FIFO Enabled in Slave Mode See Section 47.9.6.2 ”Sending Data with FIFO Enabled” and Section 47.9.6.3 ”Receiving Data with FIFO Enabled” for details. Figure 47-131: Sending/Receiving Data with FIFO Enabled in Slave Mode START Set the SLAVE mode: SADR + MSDIS + SVEN Read Status Register SVACC = 1 ? No No EOSACC = 1 ? GACC = 1 ? No SVREAD = 0 ? No Enough space in the FIFO to write all the data to send ? Load Transmit register FLEX_TWI_THR = Data to send No TXCOMP = 1 ? No END RXRDY= 0 ? No TXRDY= 1 ? No Write in FLEX_TWI_THR All the data has been written in FLEX_TWI_THR ? No Read FLEX_TWI_FSR and get the number of data in the Receive FIFO Read FLEX_TWI_RHR All data have been read in FLEX_TWI_RHR ? No GENERAL CALL TREATMENT Decoding of the programming sequence Prog seq OK ? No Change SADR DS60001476B-page 1524  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.9.6.5 Clearing/Flushing FIFOs Each FIFO can be cleared/flushed using FLEX_TWI_CR.TXFCLR/RXFCLR. 47.9.6.6 TXRDY and RXRDY Behavior FLEX_TWI_SR.TXRDY/RXRDY flags display a specific behavior when FIFOs are enabled. TXRDY indicates if a data can be written in the Transmit FIFO. Thus the TXRDY flag is set as long as the Transmit FIFO can accept new data. Refer to Figure 47-132. RXRDY indicates if an unread data is present in the Receive FIFO. Thus the RXRDY flag is set as soon as one unread data is in the Receive FIFO. Refer to Figure 47-133. TXRDY and RXRDY behavior can be modified using the TXRDYM and RXRDYM fields in the TWI FIFO Mode Register (FLEX_TWI_FMR) to reduce the number of accesses to FLEX_TWI_THR/RHR. As an example, in Master mode, the Transmit FIFO can be loaded with multiple data in the same access by configuring TXRDYM>0. See TWI FIFO Mode Register for the FIFO configuration. Figure 47-132: TXRDY Behavior when TXRDYM = 0 in Master Mode TWD S DADR W A DATA n A DATA n+1 A DATA n+2 A Write FLEX_TWI_THR Read FLEX_TWI_SR TXRDY TXFFF 1 TXFL 0 1 2 1 FIFO size - 1 FIFO full FIFO size - 1 TXCOMP Figure 47-133: TWD RXRDY Behavior when RXRDYM = 0 in Master and Slave Modes S DADR R A DATA n A DATA n+1 A DATA n+2 A Read FLEX_TWI_RHR Read FLEX_TWI_SR RXRDY RXFFF RXFEF RXFL 0 1 FIFO full FIFO size - 1 0 TXCOMP  2017 Microchip Technology Inc. DS60001476B-page 1525 SAMA5D2 SERIES Figure 47-134: TXRDY Behavior when TXRDYM = 0 in Slave Mode TWD S DADR W A DATA n A DATA n+1 A DATA n+2 A Write FLEX_TWI_THR Read FLEX_TWI_SR SVACC TXRDY TXFFF TXFL 1 0 1 2 1 FIFO size - 1 FIFO full FIFO size - 1 TXCOMP 47.9.6.7 TWI Single Data Mode In Single Data mode, only one data is written every time FLEX_TWI_THR is accessed, and only one data is read every time FLEX_TWI_RHR is accessed. When FLEX_TWI_FMR.TXRDYM = 0, the Transmit FIFO operates in Single Data mode. When FLEX_TWI_FMR.RXRDYM = 0, the Receive FIFO operates in Single Data mode. See Section 47.10.73 ”TWI Transmit Holding Register” and Section 47.10.71 ”TWI Receive Holding Register”. 47.9.6.8 TWI Multiple Data Mode Multiple Data mode minimizes the number of accesses by concatenating the data to send/read in one access. When FLEX_TWI_FMR.TXRDYM > 0, the Transmit FIFO operates in Multiple Data mode. When FLEX_TWI_FMR.RXRDYM > 0, the Receive FIFO operates in Multiple Data mode. In Multiple Data mode, it is possible to write/read up to four data in one FLEX_TWI_THR/FLEX_TWI_RHR register access. The number of data to write/read is defined by the size of the register access. If the access is a byte-size register access, only one data is written/read. If the access is a halfword size register access, then up to two data are read and only one data is written. Lastly, if the access is a wordsize register access, then up to four data are read and up to two data are written. Written/Read data are always right-aligned, as described in Section 47.10.72 ”TWI Receive Holding Register (FIFO Enabled)” and Section 47.10.74 ”TWI Transmit Holding Register (FIFO Enabled)”. As an example, if the Transmit FIFO is empty and there are six data to send, either of the following write accesses may be performed: • six FLEX_TWI_THR-byte write accesses • three FLEX_TWI_THR-halfword write accesses • one FLEX_TWI_THR-word write access and one FLEX_TWI_THR halfword write access With a Receive FIFO containing six data, any of the following read accesses may be performed: • • • • six FLEX_TWI_RHR-byte read accesses three FLEX_TWI_RHR-halfword read accesses one FLEX_TWI_RHR-word read access and one FLEX_TWI_RHR-halfword read access TXRDY and RXRDY Configuration In Multiple Data mode, it is possible to write one or more data in the same FLEX_TWI_THR/FLEX_TWI_RHR access. The TXRDY flag indicates if one or more data can be written in the FIFO depending on the configuration of FLEX_TWI_FMR.TXRDYM/RXRDYM. As an example, if two data are written each time in FLEX_TWI_THR, it is useful to configure the TXRDYM field to the value ‘1’ so that the TXRDY flag is at ‘1’ only when at least two data can be written in the Transmit FIFO. In the same way, if four data are read each time in FLEX_TWI_RHR, it is useful to configure the RXRDYM field to the value ‘2’ so that the RXRDY flag is at ‘1’ only when at least four unread data are in the Receive FIFO. • DMAC DS60001476B-page 1526  2017 Microchip Technology Inc. SAMA5D2 SERIES When FIFOs operate in Multiple Data mode, the DMAC transfer type must be configured in byte, halfword or word depending on the FLEX_TWI_FMR.TXRDYM/RXRDYM settings. 47.9.6.9 Transmit FIFO Lock If a frame is terminated early due to a not-acknowledge error (NACK flag), SMBus timeout error (TOUT flag) or master code acknowledge error (MACK flag), a lock is set on the Transmit FIFO preventing any new frame from being sent until it is cleared. This allows clearing the FIFO if needed, resetting DMAC channels, etc., without any risk. FLEX_TWI_SR.LOCK is used to check the state of the Transmit FIFO lock. The Transmit FIFO lock can be cleared by setting FLEX_TWI_CR.TXFLCLR to ‘1’. 47.9.6.10 FIFO Pointer Error A FIFO overflow is reported in FLEX_TWI_FSR. If the Transmit FIFO is full and a write access is performed on FLEX_TWI_THR, it generates a Transmit FIFO pointer error and sets FLEX_TWI_FSR.TXFPTEF. In Multiple Data mode, if the number of data written in FLEX_TWI_THR (according to the register access size) is greater than the free space in the Transmit FIFO, a Transmit FIFO pointer error is generated and FLEX_TWI_FSR.TXFPTEF is set. A FIFO underflow is reported in FLEX_TWI_FSR. In Multiple Data mode, if the number of data read in FLEX_TWI_RHR (according to the register access size) is greater than the number of unread data in the Receive FIFO, a Receive FIFO pointer error is generated and FLEX_TWI_FSR.RXFPTEF is set. No pointer error occurs if the FIFO state/level is checked before writing/reading in FLEX_TWI_THR/FLEX_TWI_RHR. The FIFO state/ level can be checked either with TXRDY, RXRDY, TXFL or RXFL. When a pointer error occurs, other FIFO flags may not behave as expected; their states should be ignored. If a Transmit or Receive pointer error occurs, a software reset must be performed using FLEX_TWI_CR.SWRST. Note that issuing a software while transmitting might leave a slave in an unknown state holding the TWD line. In such case, a Bus Clear Command will allow to make the slave release the TWD line (the first frame sent afterwards might not be received properly by the slave). 47.9.6.11 FIFO Thresholds Each Transmit and Receive FIFO includes a threshold feature used to set a flag and an interrupt when a FIFO threshold is crossed. Thresholds are defined as a number of data in the FIFO, and the FIFO state (TXFL or RXFL) represents the number of data currently in the FIFO. The Transmit FIFO threshold can be set using the field FLEX_TWI_FMR.TXFTHRES. Each time the Transmit FIFO level goes from ‘above threshold’ to ‘equal or below threshold’, the flag FLEX_TWI_FESR.TXFTHF is set. The application is warned that the Transmit FIFO has reached the defined threshold and that it can be reloaded. The Receive FIFO threshold can be set using the field FLEX_TWI_FMR.RXFTHRES. Each time the Receive FIFO level goes from ‘below threshold’ to ‘equal or above threshold’, the flag FLEX_TWI_FESR.RXFTHF is set. The application is warned that the Receive FIFO has reached the defined threshold and that it can be read to prevent an underflow. The TXFTHF and RXFTHF flags can be configured to generate an interrupt using FLEX_TWI_FIER and FLEX_TWI_FIDR. 47.9.6.12 FIFO Flags FIFOs come with a set of flags which can be configured to generate interrupts through FLEX_TWI_FIER and FLEX_TWI_FIDR. FIFO flags state can be read in FLEX_TWI_FSR. They are cleared when FLEX_TWI_FSR is read. 47.9.7 TWI Comparison Function on Received Character The comparison function differs if the asynchronous partial wakeup (Sleepwalking) is enabled or not. If asynchronous partial wakeup is disabled (refer to Section 33. “Power Management Controller (PMC)”), the TWI has the capability to extend the address matching on up to three slave addresses. The FLEX_TWI_SMR.SADR1EN/SADR2EN/SADR3EN bits enable address matching on additional addresses which can be configured through the FLEX_TWI_SWMR.SADR1/SADR2/SADR3 fields. The DATAMEN bit has no effect. The SVACC bit is set when there is a comparison match with the received slave address. 47.9.8 TWI Register Write Protection The FLEXCOM operating mode (FLEX_MR.OPMODE) must be set to FLEX_MR_OPMODE_TWI to enable access to the write protection registers.  2017 Microchip Technology Inc. DS60001476B-page 1527 SAMA5D2 SERIES To prevent any single software error from corrupting TWI behavior, certain registers in the address space can be write-protected by setting the WPEN (Write Protection Enable) bit in the TWI Write Protection Mode Register (FLEX_TWI_WPMR). If a write access to a write-protected register is detected, the Write Protection Violation Status (WPVS) flag in the TWI Write Protection Status Register (FLEX_TWI_WPSR) is set and the Write Protection Violation Source (WPVSRC) field indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading FLEX_TWI_WPSR. The following register(s) can be write-protected when WPEN is set: • • • • TWI Slave Mode Register TWI Clock Waveform Generator Register TWI SMBus Timing Register TWI SleepWalking Matching Register DS60001476B-page 1528  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10 Flexible Serial Communication Unit (FLEXCOM) User Interface Table 47-18: Register Mapping Offset Register Name Access Reset 0x000 FLEXCOM Mode Register FLEX_MR Read/Write 0x0 Reserved – – – FLEXCOM Receive Holding Register FLEX_RHR Read-only 0x0 Reserved – – – FLEXCOM Transmit Holding Register FLEX_THR Read/Write 0x0 0x024–0x0FC Reserved – – – 0x100–0x1FC Reserved – – – 0x200 USART Control Register FLEX_US_CR Write-only – 0x204 USART Mode Register FLEX_US_MR Read/Write – 0x208 USART Interrupt Enable Register FLEX_US_IER Write-only – 0x20C USART Interrupt Disable Register FLEX_US_IDR Write-only – 0x210 USART Interrupt Mask Register FLEX_US_IMR Read-only 0x0 0x214 USART Channel Status Register FLEX_US_CSR Read-only – 0x218 USART Receive Holding Register FLEX_US_RHR Read-only 0x0 0x21C USART Transmit Holding Register FLEX_US_THR Write-only – 0x220 USART Baud Rate Generator Register FLEX_US_BRGR Read/Write 0x0 0x224 USART Receiver Timeout Register FLEX_US_RTOR Read/Write 0x0 0x228 USART Transmitter Timeguard Register FLEX_US_TTGR Read/Write 0x0 Reserved – – – 0x240 USART FI DI Ratio Register FLEX_US_FIDI Read/Write 0x174 0x244 USART Number of Errors Register FLEX_US_NER Read-only – 0x248 Reserved – – – 0x24C USART IrDA Filter Register FLEX_US_IF Read/Write 0x0 0x250 USART Manchester Configuration Register FLEX_US_MAN Read/Write 0xB0011004 0x254 USART LIN Mode Register FLEX_US_LINMR Read/Write 0x0 0x258 USART LIN Identifier Register FLEX_US_LINIR Read/Write(1) 0x0 0x25C USART LIN Baud Rate Register FLEX_US_LINBRR Read-only 0x0 Reserved – – – 0x290 USART Comparison Register FLEX_US_CMPR Read/Write 0x0 0x2A0 USART FIFO Mode Register FLEX_US_FMR Read/Write 0x0 0x2A4 USART FIFO Level Register FLEX_US_FLR Read-only 0x0 0x2A8 USART FIFO Interrupt Enable Register FLEX_US_FIER Write-only – 0x2AC USART FIFO Interrupt Disable Register FLEX_US_FIDR Write-only – 0x2B0 USART FIFO Interrupt Mask Register FLEX_US_FIMR Read-only 0x0 0x004–0x00C 0x010 0x014–0x01C 0x020 0x22C–0x23C 0x260–0x288  2017 Microchip Technology Inc. DS60001476B-page 1529 SAMA5D2 SERIES Table 47-18: Register Mapping (Continued) Offset Register Name Access Reset 0x2B4 USART FIFO Event Status Register FLEX_US_FESR Read-only 0x0 Reserved – – – 0x2E4 USART Write Protection Mode Register FLEX_US_WPMR Read/Write 0x0 0x2E8 USART Write Protection Status Register FLEX_US_WPSR Read-only 0x0 0x2EC–0x2F8 Reserved – – – 0x300–0x3FC Reserved – – – 0x400 SPI Control Register FLEX_SPI_CR Write-only – 0x404 SPI Mode Register FLEX_SPI_MR Read/Write 0x0 0x408 SPI Receive Data Register FLEX_SPI_RDR Read-only 0x0 0x40C SPI Transmit Data Register FLEX_SPI_TDR Write-only – 0x410 SPI Status Register FLEX_SPI_SR Read-only 0x0 0x414 SPI Interrupt Enable Register FLEX_SPI_IER Write-only – 0x418 SPI Interrupt Disable Register FLEX_SPI_IDR Write-only – 0x41C SPI Interrupt Mask Register FLEX_SPI_IMR Read-only 0x0 Reserved – – – 0x430 SPI Chip Select Register 0 FLEX_SPI_CSR0 Read/Write 0x0 0x434 SPI Chip Select Register 1 FLEX_SPI_CSR1 Read/Write 0x0 Reserved – – – 0x440 SPI FIFO Mode Register FLEX_SPI_FMR Read/Write 0x0 0x444 SPI FIFO Level Register FLEX_SPI_FLR Read-only 0x0 0x448 SPI Comparison Register FLEX_SPI_CMPR Read/Write 0x0 Reserved – – – 0x4E4 SPI Write Protection Mode Register FLEX_SPI_WPMR Read/Write 0x0 0x4E8 SPI Write Protection Status Register FLEX_SPI_WPSR Read-only 0x0 0x4EC–0x4F8 Reserved – – – 0x500–0x5FC Reserved – – – 0x600 TWI Control Register FLEX_TWI_CR Write-only – 0x604 TWI Master Mode Register FLEX_TWI_MMR Read/Write 0x00000000 0x608 TWI Slave Mode Register FLEX_TWI_SMR Read/Write 0x00000000 0x60C TWI Internal Address Register FLEX_TWI_IADR Read/Write 0x00000000 0x610 TWI Clock Waveform Generator Register FLEX_TWI_CWGR Read/Write 0x00000000 Reserved – – – 0x620 TWI Status Register FLEX_TWI_SR Read-only 0x0300F009 0x624 TWI Interrupt Enable Register FLEX_TWI_IER Write-only – 0x628 TWI Interrupt Disable Register FLEX_TWI_IDR Write-only – 0x62C TWI Interrupt Mask Register FLEX_TWI_IMR Read-only 0x00000000 0x2B8–0x2E0 0x420–0x42C 0x438–0x43C 0x44C–0x4E0 0x614–0x61C DS60001476B-page 1530  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 47-18: Register Mapping (Continued) Offset Register Name Access Reset 0x630 TWI Receive Holding Register FLEX_TWI_RHR Read-only 0x00000000 0x634 TWI Transmit Holding Register FLEX_TWI_THR Write-only – 0x638 TWI SMBus Timing Register FLEX_TWI_SMBTR Read/Write 0x00000000 0x63C Reserved – – – 0x640 TWI Alternative Command Register FLEX_TWI_ACR Read/Write 0x0 0x644 TWI Filter Register FLEX_TWI_FILTR Read/Write 0x00000000 0x648 Reserved – – – 0x64C TWI SleepWalking Matching Register FLEX_TWI_SWMR Read/Write 0x00000000 0x650 TWI FIFO Mode Register FLEX_TWI_FMR Read/Write 0x0 0x654 TWI FIFO Level Register FLEX_TWI_FLR Read-only 0x0 Reserved – – – 0x660 TWI FIFO Status Register FLEX_TWI_FSR Read-only 0x0 0x664 TWI FIFO Interrupt Enable Register FLEX_TWI_FIER Write-only – 0x668 TWI FIFO Interrupt Disable Register FLEX_TWI_FIDR Write-only – 0x66C TWI FIFO Interrupt Mask Register FLEX_TWI_FIMR Read-only 0x0 0x670–0x6CC Reserved – – – 0x6D0 Reserved – – – 0x6D4–0x6E0 Reserved – – – 0x6E4 TWI Write Protection Mode Register FLEX_TWI_WPMR Read/Write 0x00000000 0x6E8 TWI Write Protection Status Register FLEX_TWI_WPSR Read-only 0x00000000 0x6EC–0x6FC Reserved – – – 0x700–0x7FC Reserved – – – 0x658–0x65C Note 1: Write is possible only in LIN master node configuration.  2017 Microchip Technology Inc. DS60001476B-page 1531 SAMA5D2 SERIES 47.10.1 FLEXCOM Mode Register Name: FLEX_MR Address: 0xF8034000 (0), 0xF8038000 (1), 0xFC010000 (2), 0xFC014000 (3), 0xFC018000 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 0 OPMODE OPMODE: FLEXCOM Operating Mode Value Name Description 0 NO_COM No communication 1 USART 2 SPI 3 TWI DS60001476B-page 1532 All UART related protocols are selected (RS232, RS485, IrDA, ISO7816, LIN,) SPI/TWI related registers are not accessible and have no impact on IOs. SPI operating mode is selected. USART/TWI related registers are not accessible and have no impact on IOs. All TWI related protocols are selected (TWI, SMBus). USART/SPI related registers are not accessible and have no impact on IOs.  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.2 FLEXCOM Transmit Holding Register Name: FLEX_THR Address: 0xF8034020 (0), 0xF8038020 (1), 0xFC010020 (2), 0xFC014020 (3), 0xFC018020 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 TXDATA 7 6 5 4 TXDATA TXDATA: Transmit Data This register is a mirror of: • USART Transmit Holding Register (FLEX_US_THR) if FLEX_MR.OPMODE field equals 1 • SPI Transmit Data Register (FLEX_SPI_TDR) if FLEX_MR.OPMODE field equals 2 • TWI Transmit Holding Register (FLEX_TWI_THR) if FLEX_MR.OPMODE field equals 3  2017 Microchip Technology Inc. DS60001476B-page 1533 SAMA5D2 SERIES 47.10.3 FLEXCOM Receive Holding Register Name: FLEX_RHR Address: 0xF8034010 (0), 0xF8038010 (1), 0xFC010010 (2), 0xFC014010 (3), 0xFC018010 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 RXDATA 7 6 5 4 RXDATA RXDATA: Receive Data This register is a mirror of: • USART Receive Holding Register (FLEX_US_RHR) if FLEX_MR.OPMODE field equals 1 • SPI Receive Data Register (FLEX_SPI_RDR) if FLEX_MR.OPMODE field equals 2 • TWI Transmit Holding Register (FLEX_TWI_RHR) if FLEX_MR.OPMODE field equals 3 DS60001476B-page 1534  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.4 USART Control Register Name: FLEX_US_CR Address: 0xF8034200 (0), 0xF8038200 (1), 0xFC010200 (2), 0xFC014200 (3), 0xFC018200 (4) Access: Write-only 31 FIFODIS 30 FIFOEN 29 – 28 REQCLR 27 – 26 TXFLCLR 25 RXFCLR 24 TXFCLR 23 – 22 – 21 LINWKUP 20 LINABT 19 RTSDIS 18 RTSEN 17 – 16 – 15 RETTO 14 RSTNACK 13 RSTIT 12 SENDA 11 STTTO 10 STPBRK 9 STTBRK 8 RSTSTA 7 TXDIS 6 TXEN 5 RXDIS 4 RXEN 3 RSTTX 2 RSTRX 1 – 0 – For SPI control, see Section 47.10.5 ”USART Control Register (SPI_MODE)”. RSTRX: Reset Receiver 0: No effect. 1: Resets the receiver. RSTTX: Reset Transmitter 0: No effect. 1: Resets the transmitter. RXEN: Receiver Enable 0: No effect. 1: Enables the receiver, if RXDIS is 0. RXDIS: Receiver Disable 0: No effect. 1: Disables the receiver. TXEN: Transmitter Enable 0: No effect. 1: Enables the transmitter if TXDIS is 0. TXDIS: Transmitter Disable 0: No effect. 1: Disables the transmitter.  2017 Microchip Technology Inc. DS60001476B-page 1535 SAMA5D2 SERIES RSTSTA: Reset Status Bits 0: No effect. 1: Resets the status bits PARE, FRAME, OVRE, MANE, LINBE, LINISFE, LINIPE, LINCE, LINSNRE, LINSTE, LINHTE, LINID, LINTC, LINBK, CMP and RXBRK in FLEX_US_CSR. Also resets the status bits TXFEF, TXFFF, TXFTHF, RXFEF, RXFFF, RXFTHF, TXFPTEF, RXFPTEF in FLEX_US_FESR. STTBRK: Start Break 0: No effect. 1: Starts transmission of a break after the characters present in FLEX_US_THR and the Transmit Shift Register have been transmitted. No effect if a break is already being transmitted. 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. STTTO: Clear TIMEOUT Flag and Start Timeout After Next Character Received 0: No effect. 1: Starts waiting for a character before clocking the timeout counter. Immediately disables a timeout period in progress. Resets the FLEX_US_CSR.TIMEOUT status bit. SENDA: Send Address 0: No effect. 1: In Multidrop mode only, the next character written to FLEX_US_THR is sent with the address bit set. RSTIT: Reset Iterations 0: No effect. 1: Resets FLEX_US_CSR.ITER. No effect if the ISO7816 is not enabled. RSTNACK: Reset Non Acknowledge 0: No effect 1: Resets FLEX_US_CSR.NACK. RETTO: Start Timeout Immediately 0: No effect 1: Immediately restarts timeout period. RTSEN: Request to Send Enable 0: No effect. 1: Drives the RTS pin to 1 if FLEX_US_MR.USART_MODE field = 2, else drives the RTS pin to 0 if FLEX_US_MR.USART_MODE field = 0. RTSDIS: Request to Send Disable 0: No effect. 1: Drives the RTS pin to 0 if FLEX_US_MR.USART_MODE field = 2, else drives the RTS pin to 1 if FLEX_US_MR.USART_MODE field = 0. LINABT: Abort LIN Transmission 0: No effect. 1: Aborts the current LIN transmission. LINWKUP: Send LIN Wakeup Signal 0: No effect: 1: Sends a wakeup signal on the LIN bus. DS60001476B-page 1536  2017 Microchip Technology Inc. SAMA5D2 SERIES TXFCLR: Transmit FIFO Clear 0: No effect. 1: Empties the Transmit FIFO. RXFCLR: Receive FIFO Clear 0: No effect. 1: Empties the Receive FIFO. TXFLCLR: Transmit FIFO Lock CLEAR 0: No effect. 1: Clears the Transmit FIFO Lock REQCLR: Request to Clear the Comparison Trigger FIFOEN: FIFO Enable 0: No effect. 1: Enables the Transmit and Receive FIFOs. FIFODIS: FIFO Disable 0: No effect. 1: Disables the Transmit and Receive FIFOs.  2017 Microchip Technology Inc. DS60001476B-page 1537 SAMA5D2 SERIES 47.10.5 USART Control Register (SPI_MODE) Name: FLEX_US_CR (SPI_MODE) Address: 0xF8034200 (0), 0xF8038200 (1), 0xFC010200 (2), 0xFC014200 (3), 0xFC018200 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 RCS 18 FCS 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 RSTSTA 7 TXDIS 6 TXEN 5 RXDIS 4 RXEN 3 RSTTX 2 RSTRX 1 – 0 – This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. RSTRX: Reset Receiver 0: No effect. 1: Resets the receiver. RSTTX: Reset Transmitter 0: No effect. 1: Resets the transmitter. RXEN: Receiver Enable 0: No effect. 1: Enables the receiver, if RXDIS is 0. RXDIS: Receiver Disable 0: No effect. 1: Disables the receiver. TXEN: Transmitter Enable 0: No effect. 1: Enables the transmitter if TXDIS is 0. TXDIS: Transmitter Disable 0: No effect. 1: Disables the transmitter. RSTSTA: Reset Status Bits 0: No effect. 1: Resets the FLEX_US_CSR.OVRE/UNRE status bits. FCS: Force SPI Chip Select Applicable if USART operates in SPI Master mode (USART_MODE = 0xE): 0: No effect. 1: Forces the Slave Select Line NSS (RTS pin) to 0, even if USART is not transmitting, in order to address SPI slave devices supporting the CSAAT mode (Chip Select Active After Transfer). DS60001476B-page 1538  2017 Microchip Technology Inc. SAMA5D2 SERIES RCS: Release SPI Chip Select Applicable if USART operates in SPI Master mode (USART_MODE = 0xE): 0: No effect. 1: Releases the Slave Select Line NSS (RTS pin).  2017 Microchip Technology Inc. DS60001476B-page 1539 SAMA5D2 SERIES 47.10.6 USART Mode Register Name: FLEX_US_MR Address: 0xF8034204 (0), 0xF8038204 (1), 0xFC010204 (2), 0xFC014204 (3), 0xFC018204 (4) Access: Read/Write 31 ONEBIT 30 MODSYNC 29 MAN 28 FILTER 27 – 26 25 MAX_ITERATION 24 23 INVDATA 22 VAR_SYNC 21 DSNACK 20 INACK 19 OVER 18 CLKO 17 MODE9 16 MSBF 15 14 13 12 11 10 PAR 9 8 SYNC 4 3 2 1 0 CHMODE 7 NBSTOP 6 5 CHRL USCLKS USART_MODE This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. For SPI configuration, see Section 47.10.7 ”USART Mode Register (SPI_MODE)”. USART_MODE: USART Mode of Operation Value Name Description 0x0 NORMAL Normal mode 0x1 RS485 RS485 0x2 HW_HANDSHAKING Hardware handshaking 0x4 IS07816_T_0 IS07816 Protocol: T = 0 0x6 IS07816_T_1 IS07816 Protocol: T = 1 0x8 IRDA IrDA 0xA LIN_MASTER LIN Master mode 0xB LIN_SLAVE LIN Slave mode 0xE SPI_MASTER SPI Master mode (CLKO must be written to 1 and USCLKS = 0, 1 or 2) 0xF SPI_SLAVE SPI Slave mode USCLKS: Clock Selection Value Name Description 0 MCK Peripheral clock is selected 1 DIV Peripheral clock divided (DIV = 8) is selected 2 GCLK PMC generic clock is selected. If the SCK pin is driven (CLKO = 1), the CD field must be greater than 1. 3 SCK External pin SCK is selected DS60001476B-page 1540  2017 Microchip Technology Inc. SAMA5D2 SERIES CHRL: Character Length Value Name Description 0 5_BIT Character length is 5 bits 1 6_BIT Character length is 6 bits 2 7_BIT Character length is 7 bits 3 8_BIT Character length is 8 bits SYNC: Synchronous Mode Select 0: USART operates in Asynchronous mode (UART). 1: USART operates in Synchronous mode. PAR: Parity Type Value Name Description 0 EVEN Even parity 1 ODD Odd parity 2 SPACE Parity forced to 0 (Space) 3 MARK Parity forced to 1 (Mark) 4 NO No parity 6 MULTIDROP Multidrop mode NBSTOP: Number of Stop Bits Value Name Description 0 1_BIT 1 stop bit 1 1_5_BIT 1.5 stop bit (SYNC = 0) or reserved (SYNC = 1) 2 2_BIT 2 stop bits CHMODE: Channel Mode Value Name Description 0 NORMAL Normal mode 1 AUTOMATIC Automatic Echo. Receiver input is connected to the TXD pin. 2 LOCAL_LOOPBACK Local Loopback. Transmitter output is connected to the Receiver Input. 3 REMOTE_LOOPBACK Remote Loopback. RXD pin is internally connected to the TXD pin. MSBF: Bit Order 0: Least significant bit is sent/received first. 1: Most significant bit is sent/received first. MODE9: 9-bit Character Length 0: CHRL defines character length. 1: 9-bit character length.  2017 Microchip Technology Inc. DS60001476B-page 1541 SAMA5D2 SERIES CLKO: Clock Output Select 0: The USART does not drive the SCK pin (Synchronous Slave mode or Asynchronous mode with external baud rate clock source). 1: The USART drives the SCK pin if USCLKS does not select the external clock SCK (USART Synchronous Master mode). OVER: Oversampling Mode 0: 16x Oversampling. 1: 8x Oversampling. INACK: Inhibit Non Acknowledge 0: The NACK is generated. 1: The NACK is not generated. 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). 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 ITER is asserted. Note: The MAX_ITERATION field must be cleared if DSNACK is cleared. INVDATA: Inverted Data 0: The data field transmitted on TXD line is the same as the one written in FLEX_US_THR or the content read in FLEX_US_RHR is the same as RXD line. Normal mode of operation. 1: The data field transmitted on TXD line is inverted (voltage polarity only) compared to the value written in FLEX_US_THR or the content read in FLEX_US_RHR is inverted compared to what is received on RXD line (or ISO7816 IO line). Inverted mode of operation, useful for contactless card application. To be used with configuration bit MSBF. VAR_SYNC: Variable Synchronization of Command/Data Sync Start Frame Delimiter 0: User defined configuration of command or data sync field depending on MODSYNC value. 1: The sync field is updated when a character is written into FLEX_US_THR. MAX_ITERATION: Maximum Number of Automatic Iteration 0–7: Defines the maximum number of iterations in mode ISO7816, protocol T = 0. FILTER: 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). MAN: Manchester Encoder/Decoder Enable 0: Manchester encoder/decoder are disabled. 1: Manchester encoder/decoder are enabled. 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. ONEBIT: Start Frame Delimiter Selector 0: Start frame delimiter is COMMAND or DATA SYNC. 1: Start frame delimiter is one bit. DS60001476B-page 1542  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.7 USART Mode Register (SPI_MODE) Name: FLEX_US_MR (SPI_MODE) Address: 0xF8034204 (0), 0xF8038204 (1), 0xFC010204 (2), 0xFC014204 (3), 0xFC018204 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 WRDBT 19 – 18 – 17 – 16 CPOL 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 CPHA 6 5 4 3 2 1 0 7 CHRL USCLKS USART_MODE This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. USART_MODE: USART Mode of Operation Value Name Description 0xE SPI_MASTER SPI master 0xF SPI_SLAVE SPI slave USCLKS: Clock Selection Value Name Description 0 MCK Peripheral clock is selected 1 DIV Peripheral clock Divided (DIV= 8) is selected 2 GCLK A PMC generic clock is selected 3 SCK External pin SCK is selected CHRL: Character Length Value Name Description 3 8_BIT Character length is 8 bits CPHA: SPI Clock Phase – Applicable if USART operates in SPI mode (USART_MODE = 0xE or 0xF): 0: Data are changed on the leading edge of SPCK and captured on the following edge of SPCK. 1: Data are 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. CHMODE: Channel Mode Value 0 Name Description NORMAL Normal mode  2017 Microchip Technology Inc. DS60001476B-page 1543 SAMA5D2 SERIES 1 AUTOMATIC Automatic Echo mode. Receiver input is connected to the TXD pin. 2 LOCAL_LOOPBACK Local Loopback mode. Transmitter output is connected to the Receiver Input. 3 REMOTE_LOOPBACK Remote Loopback mode. RXD pin is internally connected to the TXD pin. CPOL: SPI Clock Polarity Applicable if USART operates in SPI mode (slave or master, USART_MODE = 0xE or 0xF): 0: The inactive state value of SPCK is logic level zero. 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. WRDBT: Wait Read Data Before Transfer 0: The character transmission starts as soon as a character is written into FLEX_US_THR (assuming TXRDY was set). 1: The character transmission starts when a character is written and only if RXRDY flag is cleared (Receive Holding Register has been read). DS60001476B-page 1544  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.8 USART Interrupt Enable Register Name: FLEX_US_IER Address: 0xF8034208 (0), 0xF8038208 (1), 0xFC010208 (2), 0xFC014208 (3), 0xFC018208 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 MANE 23 – 22 CMP 21 – 20 – 19 CTSIC 18 – 17 – 16 – 15 – 14 – 13 NACK 12 – 11 – 10 ITER 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 RXBRK 1 TXRDY 0 RXRDY For SPI-s-specific configurations, see Section 47.10.9 ”USART Interrupt Enable Register (SPI_MODE)”. For LIN-specific configurations, see Section 47.10.10 ”USART Interrupt Enable Register (LIN_MODE)”. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Enables the corresponding interrupt. RXRDY: RXRDY Interrupt Enable TXRDY: TXRDY Interrupt Enable RXBRK: Receiver Break Interrupt Enable OVRE: Overrun Error Interrupt Enable FRAME: Framing Error Interrupt Enable PARE: Parity Error Interrupt Enable TIMEOUT: Timeout Interrupt Enable TXEMPTY: TXEMPTY Interrupt Enable ITER: Max number of Repetitions Reached Interrupt Enable NACK: Non Acknowledge Interrupt Enable CTSIC: Clear to Send Input Change Interrupt Enable CMP: Comparison Interrupt Enable MANE: Manchester Error Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1545 SAMA5D2 SERIES 47.10.9 USART Interrupt Enable Register (SPI_MODE) Name: FLEX_US_IER (SPI_MODE) Address: 0xF8034208 (0), 0xF8038208 (1), 0xFC010208 (2), 0xFC014208 (3), 0xFC018208 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 CMP 21 – 20 – 19 NSSE 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 UNRE 9 TXEMPTY 8 – 7 – 6 – 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Enables the corresponding interrupt. RXRDY: RXRDY Interrupt Enable TXRDY: TXRDY Interrupt Enable OVRE: Overrun Error Interrupt Enable TXEMPTY: TXEMPTY Interrupt Enable UNRE: SPI Underrun Error Interrupt Enable NSSE: NSS Line (Driving CTS Pin) Rising or Falling Edge Event CMP: Comparison Interrupt Enable DS60001476B-page 1546  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.10 USART Interrupt Enable Register (LIN_MODE) Name: FLEX_US_IER (LIN_MODE) Address: 0xF8034208 (0), 0xF8038208 (1), 0xFC010208 (2), 0xFC014208 (3), 0xFC018208 (4) Access: Write-only 31 LINHTE 30 LINSTE 29 LINSNRE 28 LINCE 27 LINIPE 26 LINISFE 25 LINBE 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 LINTC 14 LINID 13 LINBK 12 – 11 – 10 – 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xA or 0xB in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Enables the corresponding interrupt. RXRDY: RXRDY Interrupt Enable TXRDY: TXRDY Interrupt Enable OVRE: Overrun Error Interrupt Enable FRAME: Framing Error Interrupt Enable PARE: Parity Error Interrupt Enable TIMEOUT: Timeout Interrupt Enable TXEMPTY: TXEMPTY Interrupt Enable LINBK: LIN Break Sent or LIN Break Received Interrupt Enable LINID: LIN Identifier Sent or LIN Identifier Received Interrupt Enable LINTC: LIN Transfer Completed Interrupt Enable LINBE: LIN Bus Error Interrupt Enable LINISFE: LIN Inconsistent Synch Field Error Interrupt Enable LINIPE: LIN Identifier Parity Interrupt Enable LINCE: LIN Checksum Error Interrupt Enable LINSNRE: LIN Slave Not Responding Error Interrupt Enable LINSTE: LIN Synch Tolerance Error Interrupt Enable LINHTE: LIN Header Timeout Error Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1547 SAMA5D2 SERIES 47.10.11 USART Interrupt Disable Register Name: FLEX_US_IDR Address: 0xF803420C (0), 0xF803820C (1), 0xFC01020C (2), 0xFC01420C (3), 0xFC01820C (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 MANE 23 – 22 CMP 21 – 20 – 19 CTSIC 18 – 17 – 16 – 15 – 14 – 13 NACK 12 – 11 – 10 ITER 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 RXBRK 1 TXRDY 0 RXRDY For SPI-specific configurations, see Section 47.10.12 ”USART Interrupt Disable Register (SPI_MODE)”. For LIN-specific configurations, see Section 47.10.13 ”USART Interrupt Disable Register (LIN_MODE)”. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Disables the corresponding interrupt. RXRDY: RXRDY Interrupt Disable TXRDY: TXRDY Interrupt Disable RXBRK: Receiver Break Interrupt Disable OVRE: Overrun Error Interrupt Enable FRAME: Framing Error Interrupt Disable PARE: Parity Error Interrupt Disable TIMEOUT: Timeout Interrupt Disable TXEMPTY: TXEMPTY Interrupt Disable ITER: Max Number of Repetitions Reached Interrupt Disable NACK: Non Acknowledge Interrupt Disable CTSIC: Clear to Send Input Change Interrupt Disable CMP: Comparison Interrupt Disable MANE: Manchester Error Interrupt Disable DS60001476B-page 1548  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.12 USART Interrupt Disable Register (SPI_MODE) Name: FLEX_US_IDR (SPI_MODE) Address: 0xF803420C (0), 0xF803820C (1), 0xFC01020C (2), 0xFC01420C (3), 0xFC01820C (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 CMP 21 – 20 – 19 NSSE 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 UNRE 9 TXEMPTY 8 – 7 – 6 – 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Disables the corresponding interrupt. RXRDY: RXRDY Interrupt Disable TXRDY: TXRDY Interrupt Disable OVRE: Overrun Error Interrupt Disable TXEMPTY: TXEMPTY Interrupt Disable UNRE: SPI Underrun Error Interrupt Disable NSSE: NSS Line (Driving CTS Pin) Rising or Falling Edge Event CMP: Comparison Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 1549 SAMA5D2 SERIES 47.10.13 USART Interrupt Disable Register (LIN_MODE) Name: FLEX_US_IDR (LIN_MODE) Address: 0xF803420C (0), 0xF803820C (1), 0xFC01020C (2), 0xFC01420C (3), 0xFC01820C (4) Access: Write-only 31 LINHTE 30 LINSTE 29 LINSNRE 28 LINCE 27 LINIPE 26 LINISFE 25 LINBE 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 LINTC 14 LINID 13 LINBK 12 – 11 – 10 – 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xA or 0xB in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Disables the corresponding interrupt. RXRDY: RXRDY Interrupt Disable TXRDY: TXRDY Interrupt Disable OVRE: Overrun Error Interrupt Disable FRAME: Framing Error Interrupt Disable PARE: Parity Error Interrupt Disable TIMEOUT: Timeout Interrupt Disable TXEMPTY: TXEMPTY Interrupt Disable LINBK: LIN Break Sent or LIN Break Received Interrupt Disable LINID: LIN Identifier Sent or LIN Identifier Received Interrupt Disable LINTC: LIN Transfer Completed Interrupt Disable LINBE: LIN Bus Error Interrupt Disable LINISFE: LIN Inconsistent Synch Field Error Interrupt Disable LINIPE: LIN Identifier Parity Interrupt Disable LINCE: LIN Checksum Error Interrupt Disable LINSNRE: LIN Slave Not Responding Error Interrupt Disable LINSTE: LIN Synch Tolerance Error Interrupt Disable LINHTE: LIN Header Timeout Error Interrupt Disable DS60001476B-page 1550  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.14 USART Interrupt Mask Register Name: FLEX_US_IMR Address: 0xF8034210 (0), 0xF8038210 (1), 0xFC010210 (2), 0xFC014210 (3), 0xFC018210 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 MANE 23 – 22 CMP 21 – 20 – 19 CTSIC 18 – 17 – 16 – 15 – 14 – 13 NACK 12 – 11 – 10 ITER 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 RXBRK 1 TXRDY 0 RXRDY For SPI-specific configurations, see Section 47.10.15 ”USART Interrupt Mask Register (SPI_MODE)”. For LIN-specific configurations, see Section 47.10.16 ”USART Interrupt Mask Register (LIN_MODE)”. The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. RXRDY: RXRDY Interrupt Mask TXRDY: TXRDY Interrupt Mask RXBRK: Receiver Break Interrupt Mask OVRE: Overrun Error Interrupt Mask FRAME: Framing Error Interrupt Mask PARE: Parity Error Interrupt Mask TIMEOUT: Timeout Interrupt Mask TXEMPTY: TXEMPTY Interrupt Mask ITER: Max Number of Repetitions Reached Interrupt Mask NACK: Non Acknowledge Interrupt Mask CTSIC: Clear to Send Input Change Interrupt Mask CMP: Comparison Interrupt Mask MANE: Manchester Error Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1551 SAMA5D2 SERIES 47.10.15 USART Interrupt Mask Register (SPI_MODE) Name: FLEX_US_IMR (SPI_MODE) Address: 0xF8034210 (0), 0xF8038210 (1), 0xFC010210 (2), 0xFC014210 (3), 0xFC018210 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 CMP 21 – 20 – 19 NSSE 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 UNRE 9 TXEMPTY 8 – 7 – 6 – 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. RXRDY: RXRDY Interrupt Mask TXRDY: TXRDY Interrupt Mask OVRE: Overrun Error Interrupt Mask TXEMPTY: TXEMPTY Interrupt Mask UNRE: SPI Underrun Error Interrupt Mask NSSE: NSS Line (Driving CTS Pin) Rising or Falling Edge Event CMP: Comparison Interrupt Mask DS60001476B-page 1552  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.16 USART Interrupt Mask Register (LIN_MODE) Name: FLEX_US_IMR (LIN_MODE) Address: 0xF8034210 (0), 0xF8038210 (1), 0xFC010210 (2), 0xFC014210 (3), 0xFC018210 (4) Access: Read-only 31 LINHTE 30 LINSTE 29 LINSNRE 28 LINCE 27 LINIPE 26 LINISFE 25 LINBE 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 LINTC 14 LINID 13 LINBK 12 – 11 – 10 – 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xA or 0xB in the USART Mode Register. The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. RXRDY: RXRDY Interrupt Mask TXRDY: TXRDY Interrupt Mask OVRE: Overrun Error Interrupt Mask FRAME: Framing Error Interrupt Mask PARE: Parity Error Interrupt Mask TIMEOUT: Timeout Interrupt Mask TXEMPTY: TXEMPTY Interrupt Mask LINBK: LIN Break Sent or LIN Break Received Interrupt Mask LINID: LIN Identifier Sent or LIN Identifier Received Interrupt Mask LINTC: LIN Transfer Completed Interrupt Mask LINBE: LIN Bus Error Interrupt Mask LINISFE: LIN Inconsistent Synch Field Error Interrupt Mask LINIPE: LIN Identifier Parity Interrupt Mask LINCE: LIN Checksum Error Interrupt Mask LINSNRE: LIN Slave Not Responding Error Interrupt Mask LINSTE: LIN Synch Tolerance Error Interrupt Mask LINHTE: LIN Header Timeout Error Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1553 SAMA5D2 SERIES 47.10.17 USART Channel Status Register Name: FLEX_US_CSR Address: 0xF8034214 (0), 0xF8038214 (1), 0xFC010214 (2), 0xFC014214 (3), 0xFC018214 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 MANE 23 CTS 22 CMP 21 – 20 – 19 CTSIC 18 – 17 – 16 – 15 – 14 – 13 NACK 12 – 11 – 10 ITER 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 RXBRK 1 TXRDY 0 RXRDY For SPI-specific configurations, see Section 47.10.18 ”USART Channel Status Register (SPI_MODE)”. For LIN-specific configurations, see Section 47.10.19 ”USART Channel Status Register (LIN_MODE)”. RXRDY: Receiver Ready (cleared by reading FLEX_US_RHR) When FIFOs are disabled: 0: No complete character has been received since the last read of FLEX_US_RHR or the receiver is disabled. If characters were received when the receiver was disabled, RXRDY changes to 1 when the receiver is enabled. 1: At least one complete character has been received and FLEX_US_RHR has not yet been read. When FIFOs are enabled: 0: Receive FIFO is empty; no data to read 1: At least one unread data is in the Receive FIFO RXRDY behavior with FIFO enabled is illustrated in Section 47.7.11.5 “TXEMPTY, TXRDY and RXRDY Behavior”. TXRDY: Transmitter Ready (cleared by writing FLEX_US_THR) When FIFOs are disabled: 0: A character in FLEX_US_THR is 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 FLEX_US_THR. When FIFOs are enabled: 0: Transmit FIFO is full and cannot accept more data 1: Transmit FIFO is not full; one or more data can be written according to TXRDYM field configuration TXRDY behavior with FIFO enabled is illustrated in Section 47.7.11.5 “TXEMPTY, TXRDY and RXRDY Behavior”. RXBRK: Break Received/End of Break 0: No break received or end of break detected since the last RSTSTA command was issued. 1: Break received or end of break detected since the last RSTSTA command was issued. DS60001476B-page 1554  2017 Microchip Technology Inc. SAMA5D2 SERIES OVRE: Overrun Error 0: No overrun error has occurred since the last RSTSTA command was issued. 1: At least one overrun error has occurred since the last RSTSTA command was issued. FRAME: Framing Error 0: No stop bit has been detected low since the last RSTSTA command was issued. 1: At least one stop bit has been detected low since the last RSTSTA command was issued. PARE: Parity Error 0: No parity error has been detected since the last RSTSTA command was issued. 1: At least one parity error has been detected since the last RSTSTA command was issued. TIMEOUT: Receiver Timeout 0: There has not been a timeout since the last Start Timeout command (FLEX_US_CR.STTTO) or the Timeout Register is 0. 1: There has been a timeout since the last Start Timeout command (FLEX_US_CR.STTTO). TXEMPTY: Transmitter Empty (cleared by writing FLEX_US_THR) 0: There are characters in either FLEX_US_THR or the Transmit Shift Register, or the transmitter is disabled. 1: There are no characters in FLEX_US_THR, nor in the Transmit Shift Register. ITER: Max Number of Repetitions Reached 0: Maximum number of repetitions has not been reached since the last RSTIT command was issued. 1: Maximum number of repetitions has been reached since the last RSTIT command was issued. NACK: Non Acknowledge Interrupt 0: Non acknowledge has not been detected since the last RSTNACK. 1: At least one non acknowledge has been detected since the last RSTNACK. CTSIC: Clear to Send Input Change Flag 0: No input change has been detected on the CTS pin since the last read of FLEX_US_CSR. 1: At least one input change has been detected on the CTS pin since the last read of FLEX_US_CSR. CMP: Comparison Status 0: No received character matched the comparison criteria programmed in VAL1, VAL2 fields and CMPPAR bit in since the last RSTSTA command was issued. 1: A received character matched the comparison criteria since the last RSTSTA command was issued. CTS: Image of CTS Input 0: CTS input is driven low. 1: CTS input is driven high. MANE: Manchester Error 0: No Manchester error has been detected since the last RSTSTA command was issued. 1: At least one Manchester error has been detected since the last RSTSTA command was issued.  2017 Microchip Technology Inc. DS60001476B-page 1555 SAMA5D2 SERIES 47.10.18 USART Channel Status Register (SPI_MODE) Name: FLEX_US_CSR (SPI_MODE) Address: 0xF8034214 (0), 0xF8038214 (1), 0xFC010214 (2), 0xFC014214 (3), 0xFC018214 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 NSS 22 CMP 21 – 20 – 19 NSSE 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 UNRE 9 TXEMPTY 8 – 7 – 6 – 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xE or 0xF in the USART Mode Register. RXRDY: Receiver Ready (cleared by reading FLEX_US_RHR) 0: No complete character has been received since the last read of FLEX_US_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. 1: At least one complete character has been received and FLEX_US_RHR has not yet been read. TXRDY: Transmitter Ready (cleared by writing FLEX_US_THR) 0: A character in FLEX_US_THR is waiting to be transferred to the Transmit Shift Register, or the transmitter is disabled. As soon as the transmitter is enabled, TXRDY becomes 1. 1: There is no character in FLEX_US_THR. OVRE: Overrun Error 0: No overrun error has occurred since the last RSTSTA command was issued. 1: At least one overrun error has occurred since the last RSTSTA command was issued. TXEMPTY: Transmitter Empty (cleared by writing FLEX_US_THR) 0: There are characters in either FLEX_US_THR or the Transmit Shift Register, or the transmitter is disabled. 1: There are no characters in FLEX_US_THR, nor in the Transmit Shift Register. UNRE: Underrun Error 0: No SPI underrun error has occurred since the last RSTSTA command was issued. 1: At least one SPI underrun error has occurred since the last RSTSTA command was issued. NSSE: NSS Line (Driving CTS Pin) Rising or Falling Edge Event (cleared on read) 0: No NSS line event has been detected since the last read of FLEX_US_CSR. 1: A rising or falling edge has been detected on the NSS line since the last read of FLEX_US_CSR. CMP: Comparison Match 0: No received character matched the comparison criteria programmed in VAL1, VAL2 fields and CMPPAR bit in FLEX_US_CMPR since the last RSTSTA command was issued. 1: A received character matched the comparison criteria since the last RSTSTA command was issued. NSS: Image of NSS Line 0: NSS line is driven low (if NSSE = 1, falling edge occurred on NSS line). 1: NSS line is driven high (if NSSE = 1, rising edge occurred on NSS line). DS60001476B-page 1556  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.19 USART Channel Status Register (LIN_MODE) Name: FLEX_US_CSR (LIN_MODE) Address: 0xF8034214 (0), 0xF8038214 (1), 0xFC010214 (2), 0xFC014214 (3), 0xFC018214 (4) Access: Read-only 31 LINHTE 30 LINSTE 29 LINSNRE 28 LINCE 27 LINIPE 26 LINISFE 25 LINBE 24 – 23 LINBLS 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 LINTC 14 LINID 13 LINBK 12 – 11 – 10 – 9 TXEMPTY 8 TIMEOUT 7 PARE 6 FRAME 5 OVRE 4 – 3 – 2 – 1 TXRDY 0 RXRDY This configuration is relevant only if USART_MODE = 0xA or 0xB in the USART Mode Register. RXRDY: Receiver Ready (cleared by reading FLEX_US_RHR) 0: No complete character has been received since the last read of FLEX_US_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. 1: At least one complete character has been received and FLEX_US_RHR has not yet been read. TXRDY: Transmitter Ready (cleared by writing FLEX_US_THR) 0: A character in FLEX_US_THR is waiting to be transferred to the Transmit Shift Register, or the transmitter is disabled. As soon as the transmitter is enabled, TXRDY becomes 1. 1: There is no character in FLEX_US_THR. OVRE: Overrun Error 0: No overrun error has occurred since the last RSTSTA command was issued. 1: At least one overrun error has occurred since the last RSTSTA command was issued. FRAME: Framing Error 0: No stop bit has been detected low since the last RSTSTA command was issued. 1: At least one stop bit has been detected low since the last RSTSTA command was issued. PARE: Parity Error 0: No parity error has been detected since the last RSTSTA command was issued. 1: At least one parity error has been detected since the last RSTSTA command was issued. TIMEOUT: Receiver Timeout 0: There has not been a timeout since the last start timeout command (FLEX_US_CR.STTTO) or the Timeout Register is 0. 1: There has been a timeout since the last start timeout command (FLEX_US_CR.STTTO).  2017 Microchip Technology Inc. DS60001476B-page 1557 SAMA5D2 SERIES TXEMPTY: Transmitter Empty (cleared by writing FLEX_US_THR) 0: There are characters in either FLEX_US_THR or the Transmit Shift Register, or the transmitter is disabled. 1: There are no characters in FLEX_US_THR, nor in the Transmit Shift Register. LINBK: LIN Break Sent or LIN Break Received Applicable if USART operates in LIN Master mode (USART_MODE = 0xA): 0: No LIN break has been sent since the last RSTSTA command was issued. 1: At least one LIN break has been sent since the last RSTSTA. If USART operates in LIN Slave mode (USART_MODE = 0xB): 0: No LIN break has received sent since the last RSTSTA command was issued. 1: At least one LIN break has been received since the last RSTSTA command was issued. LINID: LIN Identifier Sent or LIN Identifier Received If USART operates in LIN Master mode (USART_MODE = 0xA): 0: No LIN identifier has been sent since the last RSTSTA command was issued. 1: At least one LIN identifier has been sent since the last RSTSTA command was issued. If USART operates in LIN Slave mode (USART_MODE = 0xB): 0: No LIN identifier has been received since the last RSTSTA command was issued. 1: At least one LIN identifier has been received since the last RSTSTA. LINTC: LIN Transfer Completed 0: The USART is idle or a LIN transfer is ongoing. 1: A LIN transfer has been completed since the last RSTSTA command was issued. LINBLS: LIN Bus Line Status 0: LIN bus line is set to 0. 1: LIN bus line is set to 1. LINBE: LIN Bit Error 0: No bit error has been detected since the last RSTSTA command was issued. 1: A bit error has been detected since the last RSTSTA command was issued. LINISFE: LIN Inconsistent Synch Field Error 0: No LIN inconsistent synch field error has been detected since the last RSTSTA 1: The USART is configured as a slave node and a LIN Inconsistent synch field error has been detected since the last RSTSTA command was issued. LINIPE: LIN Identifier Parity Error 0: No LIN identifier parity error has been detected since the last RSTSTA command was issued. 1: A LIN identifier parity error has been detected since the last RSTSTA command was issued. LINCE: LIN Checksum Error 0: No LIN checksum error has been detected since the last RSTSTA command was issued. 1: A LIN checksum error has been detected since the last RSTSTA command was issued. LINSNRE: LIN Slave Not Responding Error 0: No LIN slave not responding error has been detected since the last RSTSTA command was issued. 1: A LIN slave not responding error has been detected since the last RSTSTA command was issued. LINSTE: LIN Synch Tolerance Error 0: No LIN synch tolerance error has been detected since the last RSTSTA command was issued. DS60001476B-page 1558  2017 Microchip Technology Inc. SAMA5D2 SERIES 1: A LIN synch tolerance error has been detected since the last RSTSTA command was issued. LINHTE: LIN Header Timeout Error 0: No LIN header timeout error has been detected since the last RSTSTA command was issued. 1: A LIN header timeout error has been detected since the last RSTSTA command was issued.  2017 Microchip Technology Inc. DS60001476B-page 1559 SAMA5D2 SERIES 47.10.20 USART Receive Holding Register Name: FLEX_US_RHR Address: 0xF8034218 (0), 0xF8038218 (1), 0xFC010218 (2), 0xFC014218 (3), 0xFC018218 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 RXSYNH 14 – 13 – 12 – 11 – 10 – 9 – 8 RXCHR 7 6 5 4 3 2 1 0 RXCHR Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit) and FLEX_US_FMR.RXRDYM = 0, see Section 47.7.11.6 “USART Single Data Mode” for details. RXCHR: Received Character Last character received if RXRDY is set. RXSYNH: Received Sync 0: Last character received is a data. 1: Last character received is a command. DS60001476B-page 1560  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.21 USART Receive Holding Register (FIFO Multi Data) Name: FLEX_US_RHR (FIFO_MULTI_DATA) Address: 0xF8034218 (0), 0xF8038218 (1), 0xFC010218 (2), 0xFC014218 (3), 0xFC018218 (4) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RXCHR3 23 22 21 20 RXCHR2 15 14 13 12 RXCHR1 7 6 5 4 RXCHR0 Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit) and FLEX_US_FMR.RXRDYM > 0, see Section 47.7.11.7 “USART Multiple Data Mode” for details. RXCHRx: Received Character First unread character in the Receive FIFO if RXRDY is set.  2017 Microchip Technology Inc. DS60001476B-page 1561 SAMA5D2 SERIES 47.10.22 USART Transmit Holding Register Name: FLEX_US_THR Address: 0xF803421C (0), 0xF803821C (1), 0xFC01021C (2), 0xFC01421C (3), 0xFC01821C (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 TXSYNH 14 – 13 – 12 – 11 – 10 – 9 – 8 TXCHR 7 6 5 4 3 2 1 0 TXCHR Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit) and FLEX_US_FMR.TXRDY = 0, see Section 47.7.11.6 “USART Single Data Mode” for details. TXCHR: Character to be Transmitted Next character to be transmitted after the current character if TXRDY is not set. 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. DS60001476B-page 1562  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.23 USART Transmit Holding Register (FIFO Multi Data) Name: FLEX_US_THR (FIFO_MULTI_DATA) Address: 0xF803421C (0), 0xF803821C (1), 0xFC01021C (2), 0xFC01421C (3), 0xFC01821C (4) Access: 31 Write-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TXCHR3 23 22 21 20 TXCHR2 15 14 13 12 TXCHR1 7 6 5 4 TXCHR0 Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit) and FLEX_US_FMR.TXRDY > 0, see Section 47.7.11.7 “USART Multiple Data Mode” for details. TXCHRx: Character to be Transmitted Next character to be transmitted.  2017 Microchip Technology Inc. DS60001476B-page 1563 SAMA5D2 SERIES 47.10.24 USART Baud Rate Generator Register Name: FLEX_US_BRGR Address: 0xF8034220 (0), 0xF8038220 (1), 0xFC010220 (2), 0xFC014220 (3), 0xFC018220 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 17 FP 16 15 14 13 12 11 10 9 8 3 2 1 0 CD 7 6 5 4 CD This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. CD: Clock Divider USART_MODE ≠ ISO7816 SYNC = 0 OVER = 0 CD OVER = 1 0 1 to 65535 SYNC = 1 or USART_MODE = SPI (master or Slave) USART_MODE = ISO7816 Baud Rate Clock Disabled CD = Selected Clock / (16 × Baud Rate) CD = Selected Clock / (8 × Baud Rate) CD = Selected Clock / Baud Rate CD = Selected Clock / (FI_DI_RATIO × Baud Rate) FP: Fractional Part 0: Fractional divider is disabled. 1–7: Baud rate resolution, defined by FP × 1/8. Warning: When the value of field FP is greater than 0, the SCK (oversampling clock) generates nonconstant duty cycles. The SCK high duration is increased by “selected clock” period from time to time. The duty cycle depends on the value of the CD field. DS60001476B-page 1564  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.25 USART Receiver Timeout Register Name: FLEX_US_RTOR Address: 0xF8034224 (0), 0xF8038224 (1), 0xFC010224 (2), 0xFC014224 (3), 0xFC018224 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 TO 15 14 13 12 11 10 9 8 3 2 1 0 TO 7 6 5 4 TO This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. TO: Timeout Value 0: The receiver timeout is disabled. 1–131071: The receiver timeout is enabled and the timeout delay is TO × bit period.  2017 Microchip Technology Inc. DS60001476B-page 1565 SAMA5D2 SERIES 47.10.26 USART Transmitter Timeguard Register Name: FLEX_US_TTGR Address: 0xF8034228 (0), 0xF8038228 (1), 0xFC010228 (2), 0xFC014228 (3), 0xFC018228 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 TG This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. TG: Timeguard Value 0: The transmitter timeguard is disabled. 1–255: The transmitter timeguard is enabled and TG is timeguard delay / bit period. DS60001476B-page 1566  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.27 USART FI DI RATIO Register Name: FLEX_US_FIDI Address: 0xF8034240 (0), 0xF8038240 (1), 0xFC010240 (2), 0xFC014240 (3), 0xFC018240 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 FI_DI_RATIO 7 6 5 4 FI_DI_RATIO This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. FI_DI_RATIO: FI Over DI Ratio Value 0: If ISO7816 mode is selected, the baud rate generator generates no signal. 1–2: Do not use. 3–65535: If ISO7816 mode is selected, the baud rate is the clock provided on SCK divided by FI_DI_RATIO.  2017 Microchip Technology Inc. DS60001476B-page 1567 SAMA5D2 SERIES 47.10.28 USART Number of Errors Register Name: FLEX_US_NER Address: 0xF8034244 (0), 0xF8038244 (1), 0xFC010244 (2), 0xFC014244 (3), 0xFC018244 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 NB_ERRORS This register is relevant only if USART_MODE = 0x4 or 0x6 in the USART Mode Register. NB_ERRORS: Number of Errors Total number of errors that occurred during an ISO7816 transfer. This register automatically clears when read. DS60001476B-page 1568  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.29 USART IrDA FILTER Register Name: FLEX_US_IF Address: 0xF803424C (0), 0xF803824C (1), 0xFC01024C (2), 0xFC01424C (3), 0xFC01824C (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 IRDA_FILTER This register is relevant only if USART_MODE = 0x8 in the USART Mode Register. This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. IRDA_FILTER: IrDA Filter The IRDA_FILTER value must be defined to meet the following criteria: tperipheral clock × (IRDA_FILTER + 3) < 1.41 µs  2017 Microchip Technology Inc. DS60001476B-page 1569 SAMA5D2 SERIES 47.10.30 USART Manchester Configuration Register Name: FLEX_US_MAN Address: 0xF8034250 (0), 0xF8038250 (1), 0xFC010250 (2), 0xFC014250 (3), 0xFC018250 (4) Access: Read/Write 31 RXIDLEV 30 DRIFT 29 ONE 28 RX_MPOL 27 – 26 – 23 – 22 – 21 – 20 – 19 18 15 – 14 – 13 – 12 TX_MPOL 11 – 7 – 6 – 5 – 4 – 3 25 24 RX_PP 17 16 10 – 9 8 2 1 RX_PL TX_PP 0 TX_PL This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. TX_PL: Transmitter Preamble Length 0: The transmitter preamble pattern generation is disabled 1–15: The preamble length is TX_PL × Bit Period TX_PP: Transmitter Preamble Pattern The following values assume that TX_MPOL field is not set: Value Name Description 0 ALL_ONE The preamble is composed of ‘1’s 1 ALL_ZERO The preamble is composed of ‘0’s 2 ZERO_ONE The preamble is composed of ‘01’s 3 ONE_ZERO The preamble is composed of ‘10’s 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. RX_PL: Receiver Preamble Length 0: The receiver preamble pattern detection is disabled 1–15: The detected preamble length is RX_PL × Bit Period RX_PP: Receiver Preamble Pattern detected The following values assume that RX_MPOL field is not set: Value Name Description 0 ALL_ONE The preamble is composed of ‘1’s 1 ALL_ZERO The preamble is composed of ‘0’s 2 ZERO_ONE The preamble is composed of ‘01’s 3 ONE_ZERO The preamble is composed of ‘10’s RX_MPOL: Receiver Manchester Polarity DS60001476B-page 1570  2017 Microchip Technology Inc. SAMA5D2 SERIES 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. ONE: Must Be Set to 1 Bit 29 must always be set to 1 when programming the FLEX_US_MAN register. DRIFT: Drift Compensation 0: The USART cannot recover from an important clock drift 1: The USART can recover from clock drift. The 16X Clock mode must be enabled. RXIDLEV: Receiver Idle Value 0: Receiver line idle value is 0. 1: Receiver line idle value is 1.  2017 Microchip Technology Inc. DS60001476B-page 1571 SAMA5D2 SERIES 47.10.31 USART LIN Mode Register Name: FLEX_US_LINMR Address: 0xF8034254 (0), 0xF8038254 (1), 0xFC010254 (2), 0xFC014254 (3), 0xFC018254 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 SYNCDIS 16 PDCM 15 14 13 12 11 10 9 8 3 CHKDIS 2 PARDIS 1 DLC 7 WKUPTYP 6 FSDIS 5 DLM 4 CHKTYP 0 NACT This register is relevant only if USART_MODE = 0xA or 0xB in the USART Mode Register. This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. NACT: LIN Node Action Value Name Description 0 PUBLISH The USART transmits the response. 1 SUBSCRIBE The USART receives the response. 2 IGNORE The USART does not transmit and does not receive the response. Values which are not listed in the table must be considered as “reserved”. PARDIS: Parity Disable 0: In master node configuration, the identifier parity is computed and sent automatically. In master node and slave node configuration, the parity is checked automatically. 1: Whatever the node configuration is, the Identifier parity is not computed/sent and it is not checked. CHKDIS: Checksum Disable 0: In master node configuration, the checksum is computed and sent automatically. In slave node configuration, the checksum is checked automatically. 1: Whatever the node configuration is, the checksum is not computed/sent and it is not checked. CHKTYP: Checksum Type 0: LIN 2.0 “enhanced” checksum 1: LIN 1.3 “classic” checksum DLM: Data Length Mode 0: The response data length is defined by the DLC field of this register. 1: The response data length is defined by the bits 5 and 6 of the identifier (FLEX_US_LINIR.IDCHR). DS60001476B-page 1572  2017 Microchip Technology Inc. SAMA5D2 SERIES FSDIS: Frame Slot Mode Disable 0: The Frame Slot mode is enabled. 1: The Frame Slot mode is disabled. WKUPTYP: Wakeup Signal Type 0: Setting the LINWKUP bit in the control register sends a LIN 2.0 wakeup signal. 1: Setting the LINWKUP bit in the control register sends a LIN 1.3 wakeup signal. DLC: Data Length Control 0–255: Defines the response data length if DLM = 0,in that case the response data length is equal to DLC+1 bytes. PDCM: DMAC Mode 0: The LIN mode register FLEX_US_LINMR is not written by the DMAC. 1: The LIN mode register FLEX_US_LINMR (excepting that flag) is written by the DMAC. SYNCDIS: Synchronization Disable 0: The synchronization procedure is performed in LIN slave node configuration. 1: The synchronization procedure is not performed in LIN slave node configuration.  2017 Microchip Technology Inc. DS60001476B-page 1573 SAMA5D2 SERIES 47.10.32 USART LIN Identifier Register Name: FLEX_US_LINIR Address: 0xF8034258 (0), 0xF8038258 (1), 0xFC010258 (2), 0xFC014258 (3), 0xFC018258 (4) Access: Read/Write or Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 IDCHR This register is relevant only if USART_MODE = 0xA or 0xB in Section 47.10.6 ”USART Mode Register”. IDCHR: Identifier Character If USART_MODE = 0xA (master node configuration): IDCHR is Read/Write and its value is the identifier character to be transmitted. If USART_MODE = 0xB (slave node configuration): IDCHR is Read-only and its value is the last identifier character that has been received. DS60001476B-page 1574  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.33 USART LIN Baud Rate Register Name: FLEX_US_LINBRR Address: 0xF803425C (0), 0xF803825C (1), 0xFC01025C (2), 0xFC01425C (3), 0xFC01825C (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 17 LINFP 16 15 14 13 12 11 10 9 8 3 2 1 0 LINCD 7 6 5 4 LINCD This register is relevant only if USART_MODE = 0xA or 0xB in Section 47.10.6 ”USART Mode Register”. Returns the baud rate value after the synchronization process completion. LINCD: Clock Divider after Synchronization LINFP: Fractional Part after Synchronization  2017 Microchip Technology Inc. DS60001476B-page 1575 SAMA5D2 SERIES 47.10.34 USART Comparison Register Name: FLEX_US_CMPR Address: 0xF8034290 (0), 0xF8038290 (1), 0xFC010290 (2), 0xFC014290 (3), 0xFC018290 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – VAL2 23 22 21 20 19 18 17 16 VAL2 15 14 13 12 11 10 9 8 – CMPPAR – CMPMODE – – – VAL1 7 6 5 4 3 2 1 0 VAL1 This register can only be written if the WPEN bit is cleared in the USART Write Protection Mode Register. VAL1: First Comparison Value for Received Character 0–511: The received character must be higher or equal to the value of VAL1 and lower or equal to VAL2 to set the FLEX_US_CSR.CMP flag. CMPMODE: Comparison Mode Value Name Description 0 FLAG_ONLY Any character is received and comparison function drives CMP flag. 1 START_CONDITION Comparison condition must be met to start reception. CMPPAR: Compare Parity 0: The parity is not checked and a bad parity cannot prevent from waking up the system. 1: The parity is checked and a matching condition on data can be cancelled by an error on parity bit, so no wakeup is performed. VAL2: Second Comparison Value for Received Character 0–511: The received character must be lower or equal to the value of VAL2 and higher or equal to VAL1 to set the FLEX_US_CSR.CMP flag. DS60001476B-page 1576  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.35 USART FIFO Mode Register Name: FLEX_US_FMR Address: 0xF80342A0 (0), 0xF80382A0 (1), 0xFC0102A0 (2), 0xFC0142A0 (3), 0xFC0182A0 (4) Access: Read/Write 31 30 – – 23 22 – – 15 14 – – 7 6 FRTSC – 29 28 27 26 25 24 18 17 16 10 9 8 3 2 1 – – RXFTHRES2 21 20 19 RXFTHRES 13 12 11 TXFTHRES 5 4 RXRDYM 0 TXRDYM TXRDYM: Transmitter Ready Mode If FIFOs are enabled, the FLEX_US_CSR.TXRDY flag behaves as follows. Value Name Description 0 ONE_DATA TXRDY will be at level ‘1’ when at least one data can be written in the Transmit FIFO 1 TWO_DATA TXRDY will be at level ‘1’ when at least two data can be written in the Transmit FIFO 2 FOUR_DATA TXRDY will be at level ‘1’ when at least four data can be written in the Transmit FIFO RXRDYM: Receiver Ready Mode If FIFOs are enabled, the FLEX_US_CSR.RXRDY flag behaves as follows. Value Name Description 0 ONE_DATA RXRDY will be at level ‘1’ when at least one unread data is in the Receive FIFO 1 TWO_DATA RXRDY will be at level ‘1’ when at least two unread data are in the Receive FIFO 2 FOUR_DATA RXRDY will be at level ‘1’ when at least four unread data are in the Receive FIFO FRTSC: FIFO RTS Pin Control enable (Hardware Handshaking mode only) 0: RTS pin is not controlled by Receive FIFO thresholds. 1: RTS pin is controlled by Receive FIFO thresholds. See Section 47.7.3.15 ”Hardware Handshaking” for details. TXFTHRES: Transmit FIFO Threshold 0–32: Defines the Transmit FIFO threshold value (number of data). The FLEX_US_FESR.TXFTHF flag will be set when Transmit FIFO goes from “above” threshold state to “equal or below” threshold state. RXFTHRES: Receive FIFO Threshold 0–32: Defines the Receive FIFO threshold value (number of data). The FLEX_US_FESR.RXFTHF flag will be set when Receive FIFO goes from “below” threshold state to “equal to or above” threshold state. RXFTHRES2: Receive FIFO Threshold 2 0–32: Defines the Receive FIFO threshold 2 value (number of data). The FLEX_US_FESR.RXFTHF2 flag will be set when Receive FIFO goes from “above” threshold state to “equal or below” threshold state.  2017 Microchip Technology Inc. DS60001476B-page 1577 SAMA5D2 SERIES 47.10.36 USART FIFO Level Register Name: FLEX_US_FLR Address: 0xF80342A4 (0), 0xF80382A4 (1), 0xFC0102A4 (2), 0xFC0142A4 (3), 0xFC0182A4 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – RXFL TXFL TXFL: Transmit FIFO Level 0: There is no data in the Transmit FIFO 1–32: Indicates the number of data in the Transmit FIFO RXFL: Receive FIFO Level 0: There is no unread data in the Receive FIFO 1–32: Indicates the number of unread data in the Receive FIFO DS60001476B-page 1578  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.37 USART FIFO Interrupt Enable Register Name: FLEX_US_FIER Address: 0xF80342A8 (0), 0xF80382A8 (1), 0xFC0102A8 (2), 0xFC0142A8 (3), 0xFC0182A8 (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – RXFTHF2 – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Enable TXFFF: TXFFF Interrupt Enable TXFTHF: TXFTHF Interrupt Enable RXFEF: RXFEF Interrupt Enable RXFFF: RXFFF Interrupt Enable RXFTHF: RXFTHF Interrupt Enable TXFPTEF: TXFPTEF Interrupt Enable RXFPTEF: RXFPTEF Interrupt Enable RXFTHF2: RXFTHF2 Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1579 SAMA5D2 SERIES 47.10.38 USART FIFO Interrupt Disable Register Name: FLEX_US_FIDR Address: 0xF80342AC (0), 0xF80382AC (1), 0xFC0102AC (2), 0xFC0142AC (3), 0xFC0182AC (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – RXFTHF2 – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Disable TXFFF: TXFFF Interrupt Disable TXFTHF: TXFTHF Interrupt Disable RXFEF: RXFEF Interrupt Disable RXFFF: RXFFF Interrupt Disable RXFTHF: RXFTHF Interrupt Disable TXFPTEF: TXFPTEF Interrupt Disable RXFPTEF: RXFPTEF Interrupt Disable RXFTHF2: RXFTHF2 Interrupt Disable DS60001476B-page 1580  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.39 USART FIFO Interrupt Mask Register Name: FLEX_US_FIMR Address: 0xF80342B0 (0), 0xF80382B0 (1), 0xFC0102B0 (2), 0xFC0142B0 (3), 0xFC0182B0 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – RXFTHF2 – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Mask TXFFF: TXFFF Interrupt Mask TXFTHF: TXFTHF Interrupt Mask RXFEF: RXFEF Interrupt Mask RXFFF: RXFFF Interrupt Mask RXFTHF: RXFTHF Interrupt Mask TXFPTEF: TXFPTEF Interrupt Mask RXFPTEF: RXFPTEF Interrupt Mask RXFTHF2: RXFTHF2 Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1581 SAMA5D2 SERIES 47.10.40 USART FIFO Event Status Register Name: FLEX_US_FESR Address: 0xF80342B4 (0), 0xF80382B4 (1), 0xFC0102B4 (2), 0xFC0142B4 (3), 0xFC0182B4 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – RXFTHF2 TXFLOCK 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: Transmit FIFO Empty Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Transmit FIFO is not empty. 1: Transmit FIFO has been emptied since the last RSTSTA command was issued. TXFFF: Transmit FIFO Full Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Transmit FIFO is not full. 1: Transmit FIFO has been filled since the last RSTSTA command was issued. TXFTHF: Transmit FIFO Threshold Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Number of data in Transmit FIFO is above TXFTHRES threshold. 1: Number of data in Transmit FIFO has reached TXFTHRES threshold since the last RSTSTA command was issued. RXFEF: Receive FIFO Empty Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Receive FIFO is not empty. 1: Receive FIFO has been emptied since the last RSTSTA command was issued. RXFFF: Receive FIFO Full Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Receive FIFO is not empty. 1: Receive FIFO has been filled since the last RSTSTA command was issued. RXFTHF: Receive FIFO Threshold Flag (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Number of unread data in Receive FIFO is below RXFTHRES threshold. 1: Number of unread data in Receive FIFO has reached RXFTHRES threshold since the last RSTSTA command was issued. TXFPTEF: Transmit FIFO Pointer Error Flag 0: No Transmit FIFO pointer occurred 1: Transmit FIFO pointer error occurred. Transceiver must be reset See Section 47.7.11.9 ”FIFO Pointer Error” for details. DS60001476B-page 1582  2017 Microchip Technology Inc. SAMA5D2 SERIES RXFPTEF: Receive FIFO Pointer Error Flag 0: No Receive FIFO pointer occurred 1: Receive FIFO pointer error occurred. Receiver must be reset See Section 47.7.11.9 ”FIFO Pointer Error” for details. TXFLOCK: Transmit FIFO Lock 0: The Transmit FIFO is not locked. 1: The Transmit FIFO is locked. RXFTHF2: Receive FIFO Threshold Flag 2 (cleared by writing the FLEX_US_CR.RSTSTA bit) 0: Number of unread data in Receive FIFO is above RXFTHRES threshold. 1: Number of unread data in Receive FIFO has reached RXFTHRES2 threshold since the last RSTSTA command was issued.  2017 Microchip Technology Inc. DS60001476B-page 1583 SAMA5D2 SERIES 47.10.41 USART Write Protection Mode Register Name: FLEX_US_WPMR Address: 0xF80342E4 (0), 0xF80382E4 (1), 0xFC0102E4 (2), 0xFC0142E4 (3), 0xFC0182E4 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection on configuration registers if WPKEY corresponds to 0x555341 (“USA” in ASCII). 1: Enables the write protection on configuration registers if WPKEY corresponds to 0x555341 (“USA” in ASCII). See Section 47.7.12 “USART Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x555341 Name Description PASSWD Writing any other value in this field aborts the write operation of bit WPEN. Always reads as 0. DS60001476B-page 1584  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.42 USART Write Protection Status Register Name: FLEX_US_WPSR Address: 0xF80342E8 (0), 0xF80382E8 (1), 0xFC0102E8 (2), 0xFC0142E8 (3), 0xFC0182E8 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 11 10 9 8 WPVSRC 15 14 13 12 WPVSRC 7 6 5 4 3 2 1 0 – – – – – – – WPVS WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of FLEX_US_WPSR. 1: A write protection violation has occurred since the last read of FLEX_US_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted.  2017 Microchip Technology Inc. DS60001476B-page 1585 SAMA5D2 SERIES 47.10.43 SPI Control Register Name: FLEX_SPI_CR Address: 0xF8034400 (0), 0xF8038400 (1), 0xFC010400 (2), 0xFC014400 (3), 0xFC018400 (4) Access: Write-only 31 30 29 28 27 26 25 24 FIFODIS FIFOEN – – – – – LASTXFER 23 22 21 20 19 18 17 16 – – – – – – RXFCLR TXFCLR 15 14 13 12 11 10 9 8 – – – REQCLR – – – – 7 6 5 4 3 2 1 0 SWRST – – – – – SPIDIS SPIEN SPIEN: SPI Enable 0: No effect. 1: Enables the SPI to transfer and receive data. SPIDIS: SPI Disable 0: No effect. 1: Disables the SPI. If a transfer is in progress when SPIDIS is set, the SPI completes the transmission of the shifter register and does not start any new transfer, even if the FLEX_US_THR is loaded. All pins are set in Input mode after completion of the transmission in progress, if any. SWRST: SPI Software Reset 0: No effect. 1: Reset the SPI. A software-triggered hardware reset of the SPI interface is performed. The SPI is in Slave mode after software reset. REQCLR: Request to Clear the Comparison Trigger SleepWalking enabled: 0: No effect. 1: Clears the potential clock request currently issued by SPI, thus the potential system wakeup is cancelled. SleepWalking disabled: 0: No effect. 1: Restarts the comparison trigger to enable FLEX_SPI_RDR loading. TXFCLR: Transmit FIFO Clear 0: No effect. 1: Empties the Transmit FIFO. DS60001476B-page 1586  2017 Microchip Technology Inc. SAMA5D2 SERIES RXFCLR: Receive FIFO Clear 0: No effect. 1: Empties the Receive FIFO. LASTXFER: Last Transfer 0: No effect. 1: The current NPCS will be de-asserted after the character written in TD has been transferred. When CSAAT is set, the communication with the current serial peripheral can be closed by raising the corresponding NPCS line as soon as TD transfer is completed. See Section 47.8.3.5 “Peripheral Selection” for more details. FIFOEN: FIFO Enable 0: No effect. 1: Enables the Transmit and Receive FIFOs FIFODIS: FIFO Disable 0: No effect. 1: Disables the Transmit and Receive FIFOs  2017 Microchip Technology Inc. DS60001476B-page 1587 SAMA5D2 SERIES 47.10.44 SPI Mode Register Name: FLEX_SPI_MR Address: 0xF8034404 (0), 0xF8038404 (1), 0xFC010404 (2), 0xFC014404 (3), 0xFC018404 (4) Access: Read/Write 31 30 29 28 27 26 25 17 24 DLYBCS 23 22 21 20 19 18 – – – – – – 16 15 14 13 12 11 10 9 8 – – – CMPMODE – – – – PCS 7 6 5 4 3 2 1 0 LLB – WDRBT MODFDIS BRSRCCLK PCSDEC PS MSTR This register can only be written if the WPEN bit is cleared in the SPI Write Protection Mode Register. MSTR: Master/Slave Mode 0: SPI is in Slave mode. 1: SPI is in Master mode. PS: Peripheral Select 0: Fixed Peripheral Select 1: Variable Peripheral Select PCSDEC: Chip Select Decode 0: The chip selects are directly connected to a peripheral device. 1: The two NPCS chip select lines are connected to a 2- to 4-bit decoder. When PCSDEC equals one, up to 3 Chip Select signals can be generated with the two NPCS lines using an external 2- to 4-bit decoder. The Chip Select registers define the characteristics of the 3 chip selects, with the following rules: FLEX_SPI_CSR0 defines peripheral chip select signals 0 to 1. FLEX_SPI_CSR1 defines peripheral chip select signal 2. BRSRCCLK: Bit Rate Source Clock Value Name Description 0 PERIPH_CLK The peripheral clock is the source clock for the bit rate generation. 1 GCLK GCLK is the source clock for the bit rate generation, thus the bit rate can be independent of the core/ peripheral clock. Note: If the bit BRSRCCLK = 1, the FLEX_US_CSRx.SCBR field must be programmed with a value greater than 1. MODFDIS: Mode Fault Detection 0: Mode fault detection is enabled. 1: Mode fault detection is disabled. DS60001476B-page 1588  2017 Microchip Technology Inc. SAMA5D2 SERIES WDRBT: Wait Data Read Before Transfer 0: No Effect. In Master mode, a transfer can be initiated regardless of the FLEX_SPI_RDR state. 1: In Master mode, a transfer can start only if FLEX_SPI_RDR is empty, i.e., does not contain any unread data. This mode prevents overrun error in reception. CMPMODE: Comparison Mode Value Name Description 0 FLAG_ONLY Any character is received and comparison function drives CMP flag. 1 START_CONDITION Comparison condition must be met to start reception of all incoming characters until REQCLR is set. LLB: Local Loopback Enable 0: Local loopback path disabled. 1: Local loopback path enabled. LLB controls the local loopback on the data shift register for testing in Master mode only (MISO is internally connected on MOSI). PCS: Peripheral Chip Select This field is only used if fixed peripheral select is active (PS = 0). If PCSDEC = 0: PCS = x0 NPCS[1:0] = 10 PCS = 01 NPCS[1:0] = 01 PCS = 11 forbidden (no peripheral is selected) (x = don’t care) If PCSDEC = 1: NPCS[1:0] output signals = PCS DLYBCS: Delay Between Chip Selects This field defines the delay between the inactivation and the activation of NPCS. The DLYBCS time guarantees nonoverlapping chip selects and solves bus contentions in case of peripherals having long data float times. If DLYBCS is ≤ 6, six peripheral clock periods are inserted by default. Otherwise, the following equations determine the delay: If FLEX_SPI_MR.BRSRCCLK = 0: DLYBCS = Delay Between Chip Selects × fperipheral clock If FLEX_SPI_MR.BRSRCCLK = 1: DLYBCS = Delay Between Chip Selects × fGCLK  2017 Microchip Technology Inc. DS60001476B-page 1589 SAMA5D2 SERIES 47.10.45 SPI Receive Data Register Name: FLEX_SPI_RDR Address: 0xF8034408 (0), 0xF8038408 (1), 0xFC010408 (2), 0xFC014408 (3), 0xFC018408 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – 15 14 13 12 PCS 11 10 9 8 3 2 1 0 RD 7 6 5 4 RD Note: If FIFO is enabled (FLEX_SPI_CR.FIFOEN) and FLEX_SPI_FMR.RXRDYM = 0, see Section 47.8.7.6 “SPI Single Data Mode” for details. RD: Receive Data Data received by the SPI Interface is stored in this register in a right-justified format. Unused bits are read as zero. PCS: Peripheral Chip Select In Master mode only, these bits indicate the value on the NPCS pins at the end of a transfer. Otherwise, these bits are read as zero. Note: When using Variable Peripheral Select mode (FLEX_SPI_MR.PS = 1), it is mandatory to set the FLEX_SPI_MR.WDRBT bit to 1 if the PCS field must be processed in FLEX_SPI_RDR. DS60001476B-page 1590  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.46 SPI Receive Data Register (FIFO Multiple Data, 8-bit) Name: FLEX_SPI_RDR (FIFO_MULTI_DATA_8) Address: 0xF8034408 (0), 0xF8038408 (1), 0xFC010408 (2), 0xFC014408 (3), 0xFC018408 (4) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RD3 23 22 21 20 RD2 15 14 13 12 RD1 7 6 5 4 RD0 Note: If FIFO is enabled (FLEX_SPI_CR.FIFOEN) and FLEX_SPI_FMR.RXRDYM > 0, see Section 47.8.7.7 “SPI Multiple Data Mode” for details. RDx: Receive Data First unread data in the Receive FIFO. Data received by the SPI Interface is stored in this register in a right-justified format. Unused bits are read as zero.  2017 Microchip Technology Inc. DS60001476B-page 1591 SAMA5D2 SERIES 47.10.47 SPI Receive Data Register (FIFO Multiple Data, 16-bit) Name: FLEX_SPI_RDR (FIFO_MULTI_DATA_16) Address: 0xF8034408 (0), 0xF8038408 (1), 0xFC010408 (2), 0xFC014408 (3), 0xFC018408 (4) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RD1 23 22 21 20 RD1 15 14 13 12 RD0 7 6 5 4 RD0 Note: If FIFO is enabled (FLEX_SPI_CR.FIFOEN) and FLEX_SPI_FMR.RXRDYM > 0, see Section 47.8.7.7 “SPI Multiple Data Mode” for details. RDx: Receive Data First unread data in the Receive FIFO. Data received by the SPI Interface is stored in this register in a right-justified format. Unused bits are read as zero. DS60001476B-page 1592  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.48 SPI Transmit Data Register Name: FLEX_SPI_TDR Address: 0xF803440C (0), 0xF803840C (1), 0xFC01040C (2), 0xFC01440C (3), 0xFC01840C (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – LASTXFER 23 22 21 20 19 18 17 16 – – – – 15 14 13 12 PCS 11 10 9 8 3 2 1 0 TD 7 6 5 4 TD Note: If FIFO is enabled (FLEX_SPI_CR.FIFOEN) and FLEX_SPI_FMR.TXRDYM = 0, see Section 47.8.7.6 “SPI Single Data Mode” for details. TD: Transmit Data Data to be transmitted by the SPI Interface is stored in this register. Information to be transmitted must be written to the transmit data register in a right-justified format. PCS: Peripheral Chip Select This field is only used if variable peripheral select is active (FLEX_SPI_MR.PS = 1). If FLEX_SPI_MR.PCSDEC = 0: PCS = x0 NPCS[1:0] = 10 PCS = 01 NPCS[1:0] = 01 PCS = 11 forbidden (no peripheral is selected) (x = don’t care) If FLEX_SPI_MR.PCSDEC = 1: NPCS[1:0] output signals = PCS LASTXFER: Last Transfer 0: No effect. 1: The current NPCS is de-asserted after the transfer of the character written in TD. When FLEX_SPI_CSRx.CSAAT is set, the communication with the current serial peripheral can be closed by raising the corresponding NPCS line as soon as TD transfer is completed. This field is only used if variable peripheral select is active (FLEX_SPI_MR.PS = 1).  2017 Microchip Technology Inc. DS60001476B-page 1593 SAMA5D2 SERIES 47.10.49 SPI Transmit Data Register (FIFO Multiple Data, 8- to 16-bit) Name: FLEX_SPI_TDR (FIFO_MULTI_DATA) Address: 0xF803440C (0), 0xF803840C (1), 0xFC01040C (2), 0xFC01440C (3), 0xFC01840C (4) Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TD1 23 22 21 20 TD1 15 14 13 12 TD0 7 6 5 4 TD0 Note: If FIFO is enabled (FLEX_SPI_CR.FIFOEN) and FLEX_SPI_FMR.TXRDYM > 0, see Section 47.8.7.7 “SPI Multiple Data Mode” for details. TDx: Transmit Data Next data to write in the Transmit FIFO. Information to be transmitted must be written to this register in a right-justified format. DS60001476B-page 1594  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.50 SPI Status Register Name: FLEX_SPI_SR Address: 0xF8034410 (0), 0xF8038410 (1), 0xFC010410 (2), 0xFC014410 (3), 0xFC018410 (4) Access: Read-only 31 30 29 28 27 26 25 24 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF 23 22 21 20 19 18 17 16 – – – – – – – SPIENS 15 14 13 12 11 10 9 8 – – – – CMP UNDES TXEMPTY NSSR 7 6 5 4 3 2 1 0 – – – – OVRES MODF TDRE RDRF RDRF: Receive Data Register Full (cleared by reading FLEX_SPI_RDR) When FIFOs are disabled: 0: No data has been received since the last read of FLEX_SPI_RDR. 1: Data has been received and the received data has been transferred from the internal shift register to FLEX_SPI_RDR since the last read of FLEX_SPI_RDR. When FIFOs are enabled: 0: Receive FIFO is empty; no data to read 1: At least one unread data is in the Receive FIFO RDRF behavior with FIFOs enabled is illustrated in Section 47.8.7.5 “TXEMPTY, TDRE and RDRF Behavior”. TDRE: Transmit Data Register Empty (cleared by writing FLEX_SPI_TDR) When FIFOs are disabled: 0: Data has been written to FLEX_SPI_TDR and not yet transferred to the internal shift register. 1: The last data written to FLEX_SPI_TDR has been transferred to the internal shift register. TDRE is cleared when the SPI is disabled or at reset. Enabling the SPI sets the TDRE flag. When FIFOs are enabled: 0: Transmit FIFO cannot accept more data. 1: Transmit FIFO can accept data; one or more data can be written according to TXRDYM field configuration. TDRE behavior with FIFOs enabled is illustrated in Section 47.8.7.5 “TXEMPTY, TDRE and RDRF Behavior”. MODF: Mode Fault Error (cleared on read) 0: No mode fault has been detected since the last read of FLEX_SPI_SR. 1: A mode fault occurred since the last read of FLEX_SPI_SR. OVRES: Overrun Error Status (cleared on read) 0: No overrun has been detected since the last read of FLEX_SPI_SR. 1: An overrun has occurred since the last read of FLEX_SPI_SR. An overrun occurs when FLEX_SPI_RDR is loaded at least twice from the shift register since the last read of FLEX_SPI_RDR. NSSR: NSS Rising (cleared on read) 0: No rising edge detected on NSS pin since the last read of FLEX_SPI_SR. 1: A rising edge occurred on NSS pin since the last read of FLEX_SPI_SR. TXEMPTY: Transmission Registers Empty (cleared by writing FLEX_SPI_TDR) 0: As soon as data is written in FLEX_SPI_TDR.  2017 Microchip Technology Inc. DS60001476B-page 1595 SAMA5D2 SERIES 1: FLEX_SPI_TDR and internal shift register are empty. If a transfer delay has been defined, TXEMPTY is set after the end of this delay. UNDES: Underrun Error Status (Slave mode only) (cleared on read) 0: No underrun has been detected since the last read of FLEX_SPI_SR. 1: A transfer starts whereas no data has been loaded in FLEX_SPI_TDR, cleared when FLEX_SPI_SR is read. SPIENS: SPI Enable Status 0: SPI is disabled. 1: SPI is enabled. CMP: Comparison Status (cleared on read) 0: No received character matched the comparison criteria programmed in VAL1 and VAL2 fields in FLEX_SPI_CMPR since the last read of FLEX_SPI_SR. 1: A received character matched the comparison criteria since the last read of FLEX_SPI_SR. TXFEF: Transmit FIFO Empty Flag (cleared on read) 0: Transmit FIFO is not empty. 1: Transmit FIFO has been emptied since the last read of FLEX_SPI_SR. TXFFF: Transmit FIFO Full Flag (cleared on read) 0: Transmit FIFO is not full or TXFF flag has been cleared. 1: Transmit FIFO has been filled since the last read of FLEX_SPI_SR. TXFTHF: Transmit FIFO Threshold Flag (cleared on read) 0: Number of data in Transmit FIFO is above TXFTHRES threshold. 1: Number of data in Transmit FIFO has reached TXFTHRES threshold since the last read of FLEX_SPI_SR. RXFEF: Receive FIFO Empty Flag 0: Receive FIFO is not empty or RXFE flag has been cleared. 1: Receive FIFO has been emptied (changing states from “not empty” to “empty”). RXFFF: Receive FIFO Full Flag 0: Receive FIFO is not empty or RXFE flag has been cleared. 1: Receive FIFO has been filled (changing states from “not full” to “full”). RXFTHF: Receive FIFO Threshold Flag 0: Number of unread data in Receive FIFO is below RXFTHRES threshold or RXFTH flag has been cleared. 1: Number of unread data in Receive FIFO has reached RXFTHRES threshold (changing states from “below threshold” to “equal to or above threshold”). TXFPTEF: Transmit FIFO Pointer Error Flag 0: No Transmit FIFO pointer occurred 1: Transmit FIFO pointer error occurred. Transceiver must be reset See Section 47.8.7.8 ”FIFO Pointer Error” for details. RXFPTEF: Receive FIFO Pointer Error Flag 0: No Receive FIFO pointer occurred 1: Receive FIFO pointer error occurred. Receiver must be reset See Section 47.8.7.8 ”FIFO Pointer Error” for details. DS60001476B-page 1596  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.51 SPI Interrupt Enable Register Name: FLEX_SPI_IER Address: 0xF8034414 (0), 0xF8038414 (1), 0xFC010414 (2), 0xFC014414 (3), 0xFC018414 (4) Access: Write-only 31 30 29 28 27 26 25 24 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – CMP UNDES TXEMPTY NSSR 7 6 5 4 3 2 1 0 – – – – OVRES MODF TDRE RDRF The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. RDRF: Receive Data Register Full Interrupt Enable TDRE: SPI Transmit Data Register Empty Interrupt Enable MODF: Mode Fault Error Interrupt Enable OVRES: Overrun Error Interrupt Enable NSSR: NSS Rising Interrupt Enable TXEMPTY: Transmission Registers Empty Enable UNDES: Underrun Error Interrupt Enable CMP: Comparison Interrupt Enable TXFEF: TXFEF Interrupt Enable TXFFF: TXFFF Interrupt Enable TXFTHF: TXFTHF Interrupt Enable RXFEF: RXFEF Interrupt Enable RXFFF: RXFFF Interrupt Enable RXFTHF: RXFTHF Interrupt Enable TXFPTEF: TXFPTEF Interrupt Enable RXFPTEF: RXFPTEF Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1597 SAMA5D2 SERIES 47.10.52 SPI Interrupt Disable Register Name: FLEX_SPI_IDR Address: 0xF8034418 (0), 0xF8038418 (1), 0xFC010418 (2), 0xFC014418 (3), 0xFC018418 (4) Access: Write-only 31 30 29 28 27 26 25 24 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – CMP UNDES TXEMPTY NSSR 7 6 5 4 3 2 1 0 – – – – OVRES MODF TDRE RDRF The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. RDRF: Receive Data Register Full Interrupt Disable TDRE: SPI Transmit Data Register Empty Interrupt Disable MODF: Mode Fault Error Interrupt Disable OVRES: Overrun Error Interrupt Disable NSSR: NSS Rising Interrupt Disable TXEMPTY: Transmission Registers Empty Disable UNDES: Underrun Error Interrupt Disable CMP: Comparison Interrupt Disable TXFEF: TXFEF Interrupt Disable TXFFF: TXFFF Interrupt Disable TXFTHF: TXFTHF Interrupt Disable RXFEF: RXFEF Interrupt Disable RXFFF: RXFFF Interrupt Disable RXFTHF: RXFTHF Interrupt Disable TXFPTEF: TXFPTEF Interrupt Disable RXFPTEF: RXFPTEF Interrupt Disable DS60001476B-page 1598  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.53 SPI Interrupt Mask Register Name: FLEX_SPI_IMR Address: 0xF803441C (0), 0xF803841C (1), 0xFC01041C (2), 0xFC01441C (3), 0xFC01841C (4) Access: Read-only 31 30 29 28 27 26 25 24 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – CMP UNDES TXEMPTY NSSR 7 6 5 4 3 2 1 0 – – – – OVRES MODF TDRE RDRF The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. RDRF: Receive Data Register Full Interrupt Mask TDRE: SPI Transmit Data Register Empty Interrupt Mask MODF: Mode Fault Error Interrupt Mask OVRES: Overrun Error Interrupt Mask NSSR: NSS Rising Interrupt Mask TXEMPTY: Transmission Registers Empty Mask UNDES: Underrun Error Interrupt Mask CMP: Comparison Interrupt Mask TXFEF: TXFEF Interrupt Mask TXFFF: TXFFF Interrupt Mask TXFTHF: TXFTHF Interrupt Mask RXFEF: RXFEF Interrupt Mask RXFFF: RXFFF Interrupt Mask RXFTHF: RXFTHF Interrupt Mask TXFPTEF: TXFPTEF Interrupt Mask RXFPTEF: RXFPTEF Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1599 SAMA5D2 SERIES 47.10.54 SPI Chip Select Register Name: FLEX_SPI_CSRx[x = 0..1] Address: 0xF8034430 (0), 0xF8038430 (1), 0xFC010430 (2), 0xFC014430 (3), 0xFC018430 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 DLYBCT 23 22 21 20 DLYBS 15 14 13 12 SCBR 7 6 5 4 BITS 3 2 1 0 CSAAT CSNAAT NCPHA CPOL This register can only be written if the WPEN bit is cleared in the SPI Write Protection Mode Register. Note: FLEX_SPI_CSRx must be written even if the user wants to use the default reset values. The BITS field is not updated with the translated value unless the register is written. CPOL: Clock Polarity 0: The inactive state value of SPCK is logic level zero. 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 NCPHA to produce the required clock/data relationship between master and slave devices. NCPHA: Clock Phase 0: Data are changed on the leading edge of SPCK and captured on the following edge of SPCK. 1: Data are captured on the leading edge of SPCK and changed on the following edge of SPCK. NCPHA determines which edge of SPCK causes data to change and which edge causes data to be captured. NCPHA is used with CPOL to produce the required clock/data relationship between master and slave devices. CSNAAT: Chip Select Not Active After Transfer (Ignored if CSAAT = 1) 0: The Peripheral Chip Select does not rise between two transfers if the FLEX_SPI_TDR is reloaded before the end of the first transfer and if the two transfers occur on the same Chip Select. 1: The Peripheral Chip Select rises systematically after each transfer performed on the same slave. It remains inactive after the end of transfer for a minimal duration of: If FLEX_SPI_MR.BRSRCCLK = 0: DLYBCS ----------------------------------f peripheral clock If FLEX_SPI_MR.BRSRCCLK = 1: DLYBCS ------------------------f GCLK (if DLYBCS ≠ 0) If DLYBCS < 6, a minimum of six periods is introduced. CSAAT: Chip Select Active After Transfer 0: The Peripheral Chip Select Line rises as soon as the last transfer is achieved. 1: The Peripheral Chip Select does not rise after the last transfer is achieved. It remains active until a new transfer is requested on a different chip select. BITS: Bits Per Transfer (See Note below the FLEX_SPI_CSRx bitmap.) DS60001476B-page 1600  2017 Microchip Technology Inc. SAMA5D2 SERIES The BITS field determines the number of data bits transferred. Reserved values should not be used. Value Name Description 0 8_BIT 8 bits for transfer 1 9_BIT 9 bits for transfer 2 10_BIT 10 bits for transfer 3 11_BIT 11 bits for transfer 4 12_BIT 12 bits for transfer 5 13_BIT 13 bits for transfer 6 14_BIT 14 bits for transfer 7 15_BIT 15 bits for transfer 8 16_BIT 16 bits for transfer – Reserved 9–15 SCBR: Serial Clock Bit Rate In Master mode, the SPI Interface uses a modulus counter to derive the SPCK bit rate from the clock defined by the bit BRSRCCLK. The bit rate is selected by writing a value from 1 to 255 in the SCBR field. The following equations determine the SPCK bit rate: If FLEX_SPI_MR.BRSRCCLK = 0: SCBR = fperipheral clock / SPCK Bit Rate If FLEX_SPI_MR.BRSRCCLK = 1: SCBR = fGCLK / SPCK Bit Rate Programming the SCBR field to 0 is forbidden. Triggering a transfer while SCBR is at 0 can lead to unpredictable results. If BRSRCCLK = 1 in FLEX_SPI_MR, SCBR must be programmed with a value greater than 1. At reset, SCBR is 0 and the user has to program it at a valid value before performing the first transfer. Note: If one of the FLEX_SPI_CSRx.SCBR fields is set to 1, the other FLEX_SPI_CSRx.SCBR fields must be set to 1 as well, if they are used to process transfers. If they are not used to transfer data, they can be set at any value. DLYBS: Delay Before SPCK This field defines the delay from NPCS falling edge (activation) to the first valid SPCK transition. When DLYBS = 0, the delay is half the SPCK clock period. Otherwise, the following equations determine the delay: If FLEX_SPI_MR.BRSRCCLK = 0: DLYBS = Delay Before SPCK × fperipheral clock If FLEX_SPI_MR.BRSRCCLK = 1: DLYBS = Delay Before SPCK × fGCLK DLYBCT: Delay Between Consecutive Transfers This field defines the delay between two consecutive transfers with the same peripheral without removing the chip select. The delay is always inserted after each transfer and before removing the chip select if needed. When DLYBCT = 0, no delay between consecutive transfers is inserted and the clock keeps its duty cycle over the character transfers. Otherwise, the following equations determine the delay: If FLEX_SPI_MR.BRSRCCLK = 0: DLYBCT = Delay Between Consecutive Transfers × fperipheral clock / 32 If FLEX_SPI_MR.BRSRCCLK = 1: DLYBCT = Delay Between Consecutive Transfers × fGCLK / 32  2017 Microchip Technology Inc. DS60001476B-page 1601 SAMA5D2 SERIES 47.10.55 SPI FIFO Mode Register Name: FLEX_SPI_FMR Address: 0xF8034440 (0), 0xF8038440 (1), 0xFC010440 (2), 0xFC014440 (3), 0xFC018440 (4) Access: Read/Write 31 30 – – 29 28 27 26 25 24 23 22 – – 18 17 16 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 3 2 1 – – – – RXFTHRES 21 20 19 TXFTHRES 4 RXRDYM 0 TXRDYM TXRDYM: Transmit Data Register Empty Mode If FIFOs are enabled, the FLEX_SPI_SR.TDRE flag behaves as follows. Value Name Description 0 ONE_DATA TDRE will be at level ‘1’ when at least one data can be written in the Transmit FIFO. 1 TWO_DATA TDRE will be at level ‘1’ when at least two data can be written in the Transmit FIFO. Cannot be used if FLEX_SPI_MR.PS =1. RXRDYM: Receive Data Register Full Mode If FIFOs are enabled, the FLEX_SPI_SR.RDRF flag behaves as follows. Value Name Description 0 ONE_DATA RDRF will be at level ‘1’ when at least one unread data is in the Receive FIFO. 1 TWO_DATA 2 FOUR_DATA RDRF will be at level ‘1’ when at least two unread data are in the Receive FIFO. Cannot be used if FLEX_SPI_MR.PS =1. RDRF will be at level ‘1’ when at least four unread data are in the Receive FIFO. Cannot be used when FLEX_SPI_CSRx.BITS is greater than 0, or if FLEX_SPI_MR.MSTR =1, or if FLEX_SPI_MR.PS =1. TXFTHRES: Transmit FIFO Threshold 0–32: Defines the Transmit FIFO threshold value (number of data). The FLEX_SPI_SR.TXFTH flag will be set when Transmit FIFO goes from “above” threshold state to “equal or below” threshold state. RXFTHRES: Receive FIFO Threshold 0–32: Defines the Receive FIFO threshold value (number of data). The FLEX_SPI_SR.RXFTH flag will be set when Receive FIFO goes from “below” threshold state to “equal to or above” threshold state. DS60001476B-page 1602  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.56 SPI FIFO Level Register Name: FLEX_SPI_FLR Address: 0xF8034444 (0), 0xF8038444 (1), 0xFC010444 (2), 0xFC014444 (3), 0xFC018444 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – RXFL TXFL TXFL: Transmit FIFO Level 0: There is no data in the Transmit FIFO 1–32: Indicates the number of data in the Transmit FIFO RXFL: Receive FIFO Level 0: There is no unread data in the Receive FIFO 1–32: Indicates the number of unread data in the Receive FIFO  2017 Microchip Technology Inc. DS60001476B-page 1603 SAMA5D2 SERIES 47.10.57 SPI Comparison Register Name: FLEX_SPI_CMPR Address: 0xF8034448 (0), 0xF8038448 (1), 0xFC010448 (2), 0xFC014448 (3), 0xFC018448 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 VAL2 23 22 21 20 VAL2 15 14 13 12 VAL1 7 6 5 4 VAL1 This register can only be written if the WPEN bit is cleared in the SPI Write Protection Mode Register. VAL1: First Comparison Value for Received Character 0–65535: The received character must be higher or equal to the value of VAL1 and lower or equal to VAL2 to set the FLEX_SPI_SR.CMP flag. If asynchronous partial wakeup (SleepWalking) is enabled in PMC_SLPWK_ER, the SPI requests a system wakeup if the condition is met. VAL2: Second Comparison Value for Received Character 0–65535: The received character must be lower or equal to the value of VAL2 and higher or equal to VAL1 to set the FLEX_SPI_CSR.CMP flag. If asynchronous partial wakeup (SleepWalking) is enabled in PMC_SLPWK_ER, the SPI requests a system wakeup if condition is met. DS60001476B-page 1604  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.58 SPI Write Protection Mode Register Name: FLEX_SPI_WPMR Address: 0xF80344E4 (0), 0xF80384E4 (1), 0xFC0104E4 (2), 0xFC0144E4 (3), 0xFC0184E4 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x535049 (“SPI” in ASCII) 1: Enables the write protection if WPKEY corresponds to 0x535049 (“SPI” in ASCII) See Section 47.8.8 “SPI Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x535049 Name PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of bit WPEN. Always reads as 0 DS60001476B-page 1605 SAMA5D2 SERIES 47.10.59 SPI Write Protection Status Register Name: FLEX_SPI_WPSR Address: 0xF80344E8 (0), 0xF80384E8 (1), 0xFC0104E8 (2), 0xFC0144E8 (3), 0xFC0184E8 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 WPVSRC 7 6 5 4 3 2 1 0 – – – – – – – WPVS WPVS: Write Protection Violation Status 0: No write protect violation has occurred since the last read of FLEX_SPI_WPSR. 1: A write protect violation has occurred since the last read of FLEX_SPI_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 1606  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.60 TWI Control Register Name: FLEX_TWI_CR Address: 0xF8034600 (0), 0xF8038600 (1), 0xFC010600 (2), 0xFC014600 (3), 0xFC018600 (4) Access: Write-only 31 – 30 – 29 FIFODIS 28 FIFOEN 27 – 26 LOCKCLR 25 – 24 THRCLR 23 – 22 – 21 – 20 – 19 – 18 – 17 ACMDIS 16 ACMEN 15 CLEAR 14 PECRQ 13 PECDIS 12 PECEN 11 SMBDIS 10 SMBEN 9 HSDIS 8 HSEN 7 SWRST 6 QUICK 5 SVDIS 4 SVEN 3 MSDIS 2 MSEN 1 STOP 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 TWI Master Mode Register (FLEX_TWI_MMR). This action is necessary when the TWI peripheral needs 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 (FLEX_TWI_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, both START and STOP must 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 master data write operation, a STOP condition will be sent after the transmission of the current data is finished. MSEN: TWI Master Mode Enabled 0: No effect. 1: Enables the Master mode (MSDIS must be written to 0). 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.  2017 Microchip Technology Inc. DS60001476B-page 1607 SAMA5D2 SERIES SVEN: TWI Slave Mode Enabled 0: No effect. 1: Enables the Slave mode (SVDIS must be written to 0). 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. QUICK: SMBus Quick Command 0: No effect. 1: If Master mode is enabled, a SMBus Quick Command is sent. SWRST: Software Reset 0: No effect. 1: Equivalent to a system reset. HSEN: TWI High-Speed Mode Enabled 0: No effect. 1: High-speed mode enabled. HSDIS: TWI High-Speed Mode Disabled 0: No effect. 1: High-speed mode disabled. SMBEN: SMBus Mode Enabled 0: No effect. 1: If SMBDIS = 0, SMBus mode enabled. SMBDIS: SMBus Mode Disabled 0: No effect. 1: SMBus mode disabled. PECEN: Packet Error Checking Enable 0: No effect. 1: SMBus PEC (CRC) generation and check enabled. PECDIS: Packet Error Checking Disable 0: No effect. 1: SMBus PEC (CRC) generation and check disabled. PECRQ: PEC Request 0: No effect. 1: A PEC check or transmission is requested. CLEAR: Bus CLEAR Command 0: No effect. 1: If Master mode is enabled, send a bus clear command. ACMEN: Alternative Command Mode Enable 0: No effect. 1: Alternative Command mode enabled. DS60001476B-page 1608  2017 Microchip Technology Inc. SAMA5D2 SERIES ACMDIS: Alternative Command Mode Disable 0: No effect. 1: Alternative Command mode disabled. THRCLR: Transmit Holding Register Clear 0: No effect. 1: Clear the Transmit Holding Register and set TXRDY, TXCOMP flags. LOCKCLR: Lock Clear 0: No effect. 1: Clear the TWI FSM lock. FIFOEN: FIFO Enable 0: No effect. 1: Enable the Transmit and Receive FIFOs FIFODIS: FIFO Disable 0: No effect. 1: Disable the Transmit and Receive FIFOs  2017 Microchip Technology Inc. DS60001476B-page 1609 SAMA5D2 SERIES 47.10.61 TWI Control Register (FIFO_ENABLED) Name: FLEX_TWI_CR (FIFO_ENABLED) Address: 0xF8034600 (0), 0xF8038600 (1), 0xFC010600 (2), 0xFC014600 (3), 0xFC018600 (4) Access: Write-only 31 – 30 – 29 FIFODIS 28 FIFOEN 27 – 26 TXFLCLR 25 RXFCLR 24 TXFCLR 23 – 22 – 21 – 20 – 19 – 18 – 17 ACMDIS 16 ACMEN 15 CLEAR 14 PECRQ 13 PECDIS 12 PECEN 11 SMBDIS 10 SMBEN 9 HSDIS 8 HSEN 7 SWRST 6 QUICK 5 SVDIS 4 SVEN 3 MSDIS 2 MSEN 1 STOP 0 START Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit), see Section 47.9.6.8 “TWI Multiple Data Mode” for details. 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 TWI Master Mode Register (FLEX_TWI_MMR). This action is necessary when the TWI peripheral needs 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 (FLEX_TWI_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, both START and STOP must 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 master data write operation, a STOP condition will be sent after the transmission of the current data is finished. MSEN: TWI Master Mode Enabled 0: No effect. 1: Enables the Master mode (MSDIS must be written to 0). 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: Enables the Slave mode (SVDIS must be written to 0). Note: Switching from Master to Slave mode is only permitted when TXCOMP = 1. SVDIS: TWI Slave Mode Disabled DS60001476B-page 1610  2017 Microchip Technology Inc. SAMA5D2 SERIES 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. QUICK: SMBus Quick Command 0: No effect. 1: If Master mode is enabled, a SMBus Quick Command is sent. SWRST: Software Reset 0: No effect. 1: Equivalent to a system reset. HSEN: TWI High-Speed Mode Enabled 0: No effect. 1: High-speed mode enabled. HSDIS: TWI High-Speed Mode Disabled 0: No effect. 1: High-speed mode disabled. SMBEN: SMBus Mode Enabled 0: No effect. 1: If SMBDIS = 0, SMBus mode enabled. SMBDIS: SMBus Mode Disabled 0: No effect. 1: SMBus mode disabled. PECEN: Packet Error Checking Enable 0: No effect. 1: SMBus PEC (CRC) generation and check enabled. PECDIS: Packet Error Checking Disable 0: No effect. 1: SMBus PEC (CRC) generation and check disabled. PECRQ: PEC Request 0: No effect. 1: A PEC check or transmission is requested. CLEAR: Bus CLEAR Command 0: No effect. 1: If Master mode is enabled, send a bus clear command. ACMEN: Alternative Command Mode Enable 0: No effect. 1: Alternative Command mode enabled. ACMDIS: Alternative Command Mode Disable 0: No effect. 1: Alternative Command mode disabled. TXFCLR: Transmit FIFO Clear 0: No effect.  2017 Microchip Technology Inc. DS60001476B-page 1611 SAMA5D2 SERIES 1: Empties the Transmit FIFO. RXFCLR: Receive FIFO Clear 0: No effect. 1: Empties the Receive FIFO. TXFLCLR: Transmit FIFO Lock CLEAR 0: No effect. 1: Clears the Transmit FIFO Lock. FIFOEN: FIFO Enable 0: No effect. 1: Enable the Transmit and Receive FIFOs. FIFODIS: FIFO Disable 0: No effect. 1: Disable the Transmit and Receive FIFOs. DS60001476B-page 1612  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.62 TWI Master Mode Register Name: FLEX_TWI_MMR Address: 0xF8034604 (0), 0xF8038604 (1), 0xFC010604 (2), 0xFC014604 (3), 0xFC018604 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 21 20 19 DADR 18 17 16 15 – 14 – 13 – 12 MREAD 11 – 10 – 9 8 7 – 6 – 5 – 4 – 3 – 2 – 1 – IADRSZ 0 – IADRSZ: Internal Device Address Size Value Name Description 0 NONE No internal device address 1 1_BYTE One-byte internal device address 2 2_BYTE Two-byte internal device address 3 3_BYTE 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.  2017 Microchip Technology Inc. DS60001476B-page 1613 SAMA5D2 SERIES 47.10.63 TWI Slave Mode Register Name: FLEX_TWI_SMR Address: 0xF8034608 (0), 0xF8038608 (1), 0xFC010608 (2), 0xFC014608 (3), 0xFC018608 (4) Access: Read/Write 31 DATAMEN 30 SADR3EN 29 SADR2EN 28 SADR1EN 27 – 26 – 25 – 24 – 23 – 22 21 20 19 SADR 18 17 16 15 – 14 13 12 11 MASK 10 9 8 7 – 6 SCLWSDIS 5 – 4 – 3 SMHH 2 SMDA 1 – 0 NACKEN This register can only be written if the WPEN bit is cleared in the TWI Write Protection Mode Register. NACKEN: Slave Receiver Data Phase NACK Enable 0: Normal value to be returned in the ACK cycle of the data phase in Slave Receiver mode. 1: NACK value to be returned in the ACK cycle of the data phase in Slave Receiver mode. SMDA: SMBus Default Address 0: Acknowledge of the SMBus Default Address disabled. 1: Acknowledge of the SMBus Default Address enabled. SMHH: SMBus Host Header 0: Acknowledge of the SMBus Host Header disabled. 1: Acknowledge of the SMBus Host Header enabled. SCLWSDIS: Clock Wait State Disable 0: No effect. 1: Clock stretching disabled in Slave mode, OVRE and UNRE will indicate overrun and underrun. MASK: Slave Address Mask A mask can be applied on the slave device address in Slave mode in order to allow multiple address answer. For each bit of the MASK field set to one, the corresponding SADR bit will be masked. If the MASK field is set to 0, no mask is applied to the SADR field. 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. SADR1EN: Slave Address 1 Enable 0: Slave address 1 matching is disabled. 1: Slave address 1 matching is enabled. SADR2EN: Slave Address 2 Enable 0: Slave address 2 matching is disabled. 1: Slave address 2 matching is enabled. SADR3EN: Slave Address 3 Enable DS60001476B-page 1614  2017 Microchip Technology Inc. SAMA5D2 SERIES 0: Slave address 3 matching is disabled. 1: Slave address 3 matching is enabled. DATAMEN: Data Matching Enable 0: Data matching on first received data is disabled. 1: Data matching on first received data is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1615 SAMA5D2 SERIES 47.10.64 TWI Internal Address Register Name: FLEX_TWI_IADR Address: 0xF803460C (0), 0xF803860C (1), 0xFC01060C (2), 0xFC01460C (3), 0xFC01860C (4) Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 IADR 15 14 13 12 IADR 7 6 5 4 IADR IADR: Internal Address 0, 1, 2 or 3 bytes depending on IADRSZ. DS60001476B-page 1616  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.65 TWI Clock Waveform Generator Register Name: FLEX_TWI_CWGR Address: 0xF8034610 (0), 0xF8038610 (1), 0xFC010610 (2), 0xFC014610 (3), 0xFC018610 (4) Access: Read/Write 31 – 30 – 29 – 28 27 26 HOLD 25 24 23 – 22 – 21 – 20 BRSRCCLK 19 – 18 17 CKDIV 16 15 14 13 12 11 10 9 8 3 2 1 0 CHDIV 7 6 5 4 CLDIV This register can only be written if the WPEN bit is cleared in the TWI Write Protection Mode Register. FLEX_TWI_CWGR is only used in Master mode. CLDIV: Clock Low Divider The SCL low period is defined as follows: If BRSRCCLK = 0: CLDIV = ((tlow / tperipheral clock) - 3) / 2CKDIV If BRSRCCLK = 1: CLDIV = (tlow / text_ck) / 2CKDIV CHDIV: Clock High Divider The SCL high period is defined as follows: If BRSRCCLK = 0: CHDIV = ((thigh / tperipheral clock) - 3) / 2CKDIV If BRSRCCLK = 1: CHDIV = (thigh / text_ck) / 2CKDIV CKDIV: Clock Divider The CKDIV is used to increase both SCL high and low periods. BRSRCCLK: Bit Rate Source Clock Value Name Description 0 PERIPH_CLK The peripheral clock is the source clock for the bit rate generation. 1 GCLK GCLK is the source clock for the bit rate generation, thus the bit rate can be independent of the core/ peripheral clock. HOLD: TWD Hold Time Versus TWCK Falling If High-speed mode is selected TWD is internally modified on the TWCK falling edge to meet the I2C specified maximum hold time, else if High-speed mode is not configured TWD is kept unchanged after TWCK falling edge for a period of (HOLD + 3) × tperipheral clock. CKSRC: Transfer Rate Clock Source Value Name Description 0 PERIPH_CLK The peripheral clock is used to generate the TWI bit rate. 1 GCLK GCLK is used to generate the TWI bit rate.  2017 Microchip Technology Inc. DS60001476B-page 1617 SAMA5D2 SERIES 47.10.66 TWI Status Register Name: FLEX_TWI_SR Address: 0xF8034620 (0), 0xF8038620 (1), 0xFC010620 (2), 0xFC014620 (3), 0xFC018620 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 SDA 24 SCL 23 LOCK 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCLWS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 SVREAD 2 TXRDY 1 RXRDY 0 TXCOMP TXCOMP: Transmission Completed (cleared by writing FLEX_TWI_THR) TXCOMP used in Master mode: 0: During the length of the current frame. 1: When both the holding register and the internal shifter are empty and STOP condition has been sent. TXCOMP behavior in Master mode can be seen in Figure 47-87 and in Figure 47-89. 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 47-116, Figure 47-117, Figure 47-118 and Figure 47-119. RXRDY: Receive Holding Register Ready (cleared when reading FLEX_TWI_RHR) When FIFOs are disabled: 0: No character has been received since the last FLEX_TWI_RHR read operation. 1: A byte has been received in FLEX_TWI_RHR since the last read. RXRDY behavior in Master mode can be seen in Figure 47-89. RXRDY behavior in Slave mode can be seen in Figure 47-114, Figure 47-117, Figure 47-118 and Figure 47-119. When FIFOs are enabled: 0: Receive FIFO is empty; no data to read 1: At least one unread data is in the Receive FIFO RXRDY behavior with FIFO enabled is illustrated in Section 47.9.6.6 “TXRDY and RXRDY Behavior”. DS60001476B-page 1618  2017 Microchip Technology Inc. SAMA5D2 SERIES TXRDY: Transmit Holding Register Ready (cleared by writing FLEX_TWI_THR) TXRDY used in Master mode: 0: The transmit holding register has not been transferred into the internal shifter. Set to 0 when writing into FLEX_TWI_THR. 1: As soon as a data byte is transferred from FLEX_TWI_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 (enables TWI). TXRDY behavior in Master mode can be seen in Figure 47-85, Figure 47-86 and Figure 47-87. TXRDY used in Slave mode: 0: As soon as data is written in FLEX_TWI_THR, until this data has been transmitted and acknowledged (ACK or NACK). 1: Indicates that FLEX_TWI_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 user must not fill FLEX_TWI_THR to avoid losing it. TXRDY behavior in Slave mode can be seen in Figure 47-113, Figure 47-116, Figure 47-118 and Figure 47-119. When FIFOs are enabled: 0: Transmit FIFO is full and cannot accept more data 1: Transmit FIFO is not full; one or more data can be written according to TXRDYM field configuration TXRDY behavior with FIFOs enabled is illustrated in Section 47.9.6.6 “TXRDY and RXRDY Behavior”. SVREAD: Slave Read 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 47-113, Figure 47-114, Figure 47-118 and Figure 47-119. SVACC: Slave Access 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 47-113, Figure 47-114, Figure 47-118 and Figure 47-119. GACC: General Call Access (cleared 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, if need be, the user may acknowledge this access and decode the following bytes and respond according to the value of the bytes. GACC behavior can be seen in Figure 47-115. OVRE: Overrun Error (cleared on read) This bit is only used in Slave mode if clock stretching is disabled. 0: FLEX_TWI_RHR has not been loaded while RXRDY was set. 1: FLEX_TWI_RHR has been loaded while RXRDY was set. Reset by read in FLEX_TWI_SR when TXCOMP is set. UNRE: Underrun Error (cleared on read) This bit is only used in Slave mode if clock stretching is disabled. 0: FLEX_TWI_THR has been filled on time. 1: FLEX_TWI_THR has not been filled on time. NACK: Not Acknowledged (cleared on read) NACK used in Master mode:  2017 Microchip Technology Inc. DS60001476B-page 1619 SAMA5D2 SERIES 0: Each data byte has been correctly received by the far-end side TWI slave component. 1: A data or address byte has not been acknowledged by the slave component. Set at the same time as TXCOMP. 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 user must not fill FLEX_TWI_THR even if TXRDY is set, because it means that the master will stop the data transfer or reinitiate it. Note that in Slave Write mode all data are acknowledged by the TWI. ARBLST: Arbitration Lost (cleared 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 This bit is only used in Slave mode. 0: The clock is not stretched. 1: The clock is stretched. FLEX_TWI_THR / FLEX_TWI_RHR buffer is not filled / emptied before the transmission / reception of a new character. SCLWS behavior can be seen in Figure 47-116 and Figure 47-117. EOSACC: End Of Slave Access (cleared 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 47-118 and Figure 47-119. MCACK: Master Code Acknowledge (cleared on read) MACK used in Slave mode: 0: No master code has been received. 1: A master code has been received. TOUT: Timeout Error (cleared on read) 0: No SMBus timeout occurred. 1: SMBus timeout occurred. PECERR: PEC Error (cleared on read) 0: No SMBus PEC error occurred. 1: A SMBus PEC error occurred. SMBDAM: SMBus Default Address Match (cleared on read) 0: No SMBus Default Address received. 1: A SMBus Default Address was received. SMBHHM: SMBus Host Header Address Match (cleared on read) 0: No SMBus Host Header Address received. 1: A SMBus Host Header Address was received. DS60001476B-page 1620  2017 Microchip Technology Inc. SAMA5D2 SERIES LOCK: TWI Lock Due to Frame Errors 0: The TWI is not locked. 1: The TWI is locked due to frame errors (see Section 47.9.3.12 ”Handling Errors in Alternative Command” and Section 47.9.6 ”TWI FIFOs”). SCL: SCL Line Value 0: SCL line sampled value is ‘0’. 1: SCL line sampled value is ‘1.’ SDA: SDA Line Value 0: SDA line sampled value is ‘0’. 1: SDA line sampled value is ‘1’.  2017 Microchip Technology Inc. DS60001476B-page 1621 SAMA5D2 SERIES 47.10.67 TWI Status Register (FIFO ENABLED) Name: FLEX_TWI_SR (FIFO_ENABLED) Address: 0xF8034620 (0), 0xF8038620 (1), 0xFC010620 (2), 0xFC014620 (3), 0xFC018620 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 SDA 24 SCL 23 TXFLOCK 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 – 14 – 13 – 12 – 11 EOSACC 10 SCLWS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 SVREAD 2 TXRDY 1 RXRDY 0 TXCOMP Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit), see Section 47.9.6.8 “TWI Multiple Data Mode” for details. TXCOMP: Transmission Completed (cleared by writing FLEX_TWI_THR) TXCOMP used in Master mode: 0: During the length of the current frame. 1: When both holding register and internal shifter are empty and STOP condition has been sent. TXCOMP behavior in Master mode can be seen in Figure 47-87 and in Figure 47-89. 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 47-116, Figure 47-117, Figure 47-118 and Figure 47-119. RXRDY: Receive Holding Register Ready (cleared when reading FLEX_TWI_RHR) When FIFOs are disabled: 0: No character has been received since the last FLEX_TWI_RHR read operation. 1: A byte has been received in FLEX_TWI_RHR since the last read. RXRDY behavior in Master mode can be seen in Figure 47-89. RXRDY behavior in Slave mode can be seen in Figure 47-114, Figure 47-117, Figure 47-118 and Figure 47-119. When FIFOs are enabled: 0: Receive FIFO is empty; no data to read. 1: At least one unread data is in the Receive FIFO. RXRDY behavior with FIFO enabled is illustrated in Section 47.9.6.6 “TXRDY and RXRDY Behavior”. TXRDY: Transmit Holding Register Ready (cleared by writing FLEX_TWI_THR) TXRDY used in Master mode: 0: The transmit holding register has not been transferred into the internal shifter. Set to 0 when writing into FLEX_TWI_THR. 1: As soon as a data byte is transferred from FLEX_TWI_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 (enables TWI). TXRDY behavior in Master mode can be seen in Figure 47-85, Figure 47-86 and Figure 47-87. TXRDY used in Slave mode: 0: As soon as data is written in FLEX_TWI_THR, until this data has been transmitted and acknowledged (ACK or NACK). 1: Indicates that FLEX_TWI_THR is empty and that data has been transmitted and acknowledged. DS60001476B-page 1622  2017 Microchip Technology Inc. SAMA5D2 SERIES If TXRDY is high and if a NACK has been detected, the transmission will be stopped. Thus when TRDY = NACK = 1, the user must not fill FLEX_TWI_THR to avoid losing it. TXRDY behavior in Slave mode can be seen in Figure 47-113, Figure 47-116, Figure 47-118 and Figure 47-119. When FIFOs are enabled: 0: Transmit FIFO is full and cannot accept more data. 1: Transmit FIFO is not full; one or more data can be written according to TXRDYM field configuration. TXRDY behavior with FIFOs enabled is illustrated in Section 47.9.6.6 “TXRDY and RXRDY Behavior”. SVREAD: Slave Read 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 47-113, Figure 47-114, Figure 47-118 and Figure 47-119. SVACC: Slave Access 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 47-113, Figure 47-114, Figure 47-118 and Figure 47-119. GACC: General Call Access (cleared 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, if need be, the user may acknowledge this access and decode the following bytes and respond according to the value of the bytes. GACC behavior can be seen in Figure 47-115. OVRE: Overrun Error (cleared on read) This bit is only used in Slave mode if clock stretching is disabled. 0: FLEX_TWI_RHR has not been loaded while RXRDY was set. 1: FLEX_TWI_RHR has been loaded while RXRDY was set. Reset by read in FLEX_TWI_SR when TXCOMP is set. UNRE: Underrun Error (cleared on read) This bit is only used in Slave mode if clock stretching is disabled. 0: FLEX_TWI_THR has been filled on time. 1: FLEX_TWI_THR has not been filled on time. NACK: Not Acknowledged (cleared 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 or address byte has not been acknowledged by the slave component. Set at the same time as TXCOMP. 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 user must not fill FLEX_TWI_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.  2017 Microchip Technology Inc. DS60001476B-page 1623 SAMA5D2 SERIES ARBLST: Arbitration Lost (cleared 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 This bit is only used in Slave mode. 0: The clock is not stretched. 1: The clock is stretched. FLEX_TWI_THR / FLEX_TWI_RHR buffer is not filled / emptied before the transmission / reception of a new character. SCLWS behavior can be seen in Figure 47-116 and Figure 47-117. EOSACC: End Of Slave Access (cleared 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 47-118 and Figure 47-119. MCACK: Master Code Acknowledge (cleared on read) MACK used in Slave mode: 0: No master code has been received. 1: A master code has been received. TOUT: Timeout Error (cleared on read) 0: No SMBus timeout occurred. 1: SMBus timeout occurred. PECERR: PEC Error (cleared on read) 0: No SMBus PEC error occurred. 1: A SMBus PEC error occurred. SMBDAM: SMBus Default Address Match (cleared on read) 0: No SMBus Default Address received. 1: A SMBus Default Address was received. SMBHHM: SMBus Host Header Address Match (cleared on read) 0: No SMBus Host Header Address received. 1: A SMBus Host Header Address was received. TXFLOCK: Transmit FIFO Lock 0: The Transmit FIFO is not locked. 1: The Transmit FIFO is locked. SCL: SCL Line Value 0: SCL line sampled value is ‘0’. 1: SCL line sampled value is ‘1.’ SDA: SDA Line Value 0: SDA line sampled value is ‘0’. 1: SDA line sampled value is ‘1’. DS60001476B-page 1624  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.68 TWI Interrupt Enable Register Name: FLEX_TWI_IER Address: 0xF8034624 (0), 0xF8038624 (1), 0xFC010624 (2), 0xFC014624 (3), 0xFC018624 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 TXBUFE 14 RXBUFF 13 ENDTX 12 ENDRX 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Enable TOUT: Timeout Error Interrupt Enable PECERR: PEC Error Interrupt Enable SMBDAM: SMBus Default Address Match Interrupt Enable SMBHHM: SMBus Host Header Address Match Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 1625 SAMA5D2 SERIES 47.10.69 TWI Interrupt Disable Register Name: FLEX_TWI_IDR Address: 0xF8034628 (0), 0xF8038628 (1), 0xFC010628 (2), 0xFC014628 (3), 0xFC018628 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 TXBUFE 14 RXBUFF 13 ENDTX 12 ENDRX 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Disable TOUT: Timeout Error Interrupt Disable PECERR: PEC Error Interrupt Disable SMBDAM: SMBus Default Address Match Interrupt Disable SMBHHM: SMBus Host Header Address Match Interrupt Disable DS60001476B-page 1626  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.70 TWI Interrupt Mask Register Name: FLEX_TWI_IMR Address: 0xF803462C (0), 0xF803862C (1), 0xFC01062C (2), 0xFC01462C (3), 0xFC01862C (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 SMBHHM 20 SMBDAM 19 PECERR 18 TOUT 17 – 16 MCACK 15 TXBUFE 14 RXBUFF 13 ENDTX 12 ENDRX 11 EOSACC 10 SCL_WS 9 ARBLST 8 NACK 7 UNRE 6 OVRE 5 GACC 4 SVACC 3 – 2 TXRDY 1 RXRDY 0 TXCOMP The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. 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 UNRE: Underrun 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 MCACK: Master Code Acknowledge Interrupt Mask TOUT: Timeout Error Interrupt Mask PECERR: PEC Error Interrupt Mask SMBDAM: SMBus Default Address Match Interrupt Mask SMBHHM: SMBus Host Header Address Match Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 1627 SAMA5D2 SERIES 47.10.71 TWI Receive Holding Register Name: FLEX_TWI_RHR Address: 0xF8034630 (0), 0xF8038630 (1), 0xFC010630 (2), 0xFC014630 (3), 0xFC018630 (4) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 RXDATA Note: If FIFO is enabled (FLEX_TWI_CR.FIFOEN bit) and FLEX_TWI_FMR.RXRDYM = 0, see Section 47.9.6.7 “TWI Single Data Mode” for details. RXDATA: Master or Slave Receive Holding Data DS60001476B-page 1628  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.72 TWI Receive Holding Register (FIFO Enabled) Name: FLEX_TWI_RHR (FIFO_ENABLED) Address: 0xF8034630 (0), 0xF8038630 (1), 0xFC010630 (2), 0xFC014630 (3), 0xFC018630 (4) Access: 31 Read-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RXDATA3 23 22 21 20 RXDATA2 15 14 13 12 RXDATA1 7 6 5 4 RXDATA0 Note: If FIFO is enabled (FLEX_TWI_CR.FIFOEN bit) and FLEX_TWI_FMR.RXRDYM > 0, see Section 47.9.6.8 “TWI Multiple Data Mode” for details. RXDATA0: Master or Slave Receive Holding Data 0 RXDATA1: Master or Slave Receive Holding Data 1 RXDATA2: Master or Slave Receive Holding Data 2 RXDATA3: Master or Slave Receive Holding Data 3  2017 Microchip Technology Inc. DS60001476B-page 1629 SAMA5D2 SERIES 47.10.73 TWI Transmit Holding Register Name: FLEX_TWI_THR Address: 0xF8034634 (0), 0xF8038634 (1), 0xFC010634 (2), 0xFC014634 (3), 0xFC018634 (4) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 TXDATA Note: If FIFO is enabled (FIFOEN bit in FLEX_TWI_CR) and FLEX_TWI_FMR.TXRDYM = 0, refer to Section 47.9.6.7 ”TWI Single Data Mode” for details. TXDATA: Master or Slave Transmit Holding Data DS60001476B-page 1630  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.74 TWI Transmit Holding Register (FIFO Enabled) Name: FLEX_TWI_THR (FIFO_ENABLED) Address: 0xF8034634 (0), 0xF8038634 (1), 0xFC010634 (2), 0xFC014634 (3), 0xFC018634 (4) Access: 31 Write-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 TXDATA3 23 22 21 20 TXDATA2 15 14 13 12 TXDATA1 7 6 5 4 TXDATA0 Note: If FIFO is enabled (FLEX_US_CR.FIFOEN bit) and FLEX_TWI_FMR.TXRDYM > 0, see Section 47.9.6.8 “TWI Multiple Data Mode” for details. TXDATA0: Master or Slave Transmit Holding Data 0 TXDATA1: Master or Slave Transmit Holding Data 1 TXDATA2: Master or Slave Transmit Holding Data 2 TXDATA3: Master or Slave Transmit Holding Data 3  2017 Microchip Technology Inc. DS60001476B-page 1631 SAMA5D2 SERIES 47.10.75 TWI SMBus Timing Register Name: FLEX_TWI_SMBTR Address: 0xF8034638 (0), 0xF8038638 (1), 0xFC010638 (2), 0xFC014638 (3), 0xFC018638 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 THMAX 23 22 21 20 TLOWM 15 14 13 12 TLOWS 7 – 6 – 5 – 4 – PRESC PRESC: SMBus Clock Prescaler Used to specify how to prescale the TLOWS, TLOWM and THMAX counters in SMBTR. Counters are prescaled according to the following formula: PRESC = Log(fMCK / fPrescaled) / Log(2) - 1 TLOWS: Slave Clock Stretch Maximum Cycles 0: TLOW:SEXT timeout check disabled. 1–255: Clock cycles in slave maximum clock stretch count. Prescaled by PRESC. Used to time TLOW:SEXT. TLOWM: Master Clock Stretch Maximum Cycles 0: TLOW:MEXT timeout check disabled. 1–255: Clock cycles in master maximum clock stretch count. Prescaled by PRESC. Used to time TLOW:MEXT. THMAX: Clock High Maximum Cycles Clock cycles in clock high maximum count. Prescaled by PRESC. Used for bus free detection. Used to time THIGH:MAX. DS60001476B-page 1632  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.76 TWI Alternative Command Register Name: FLEX_TWI_ACR Address: 0xF8034640 (0), 0xF8038640 (1), 0xFC010640 (2), 0xFC014640 (3), 0xFC018640 (4) Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 NPEC 24 NDIR 19 18 17 16 11 – 10 – 9 PEC 8 DIR 3 2 1 0 NDATAL 15 – 14 – 13 – 12 – 7 6 5 4 DATAL DATAL: Data Length 0: No data to send (see Section 47.9.3.11 “Alternative Command”). 1–255: Number of bytes to send during the transfer. DIR: Transfer Direction 0: Write direction. 1: Read direction. PEC: PEC Request (SMBus Mode only) 0: The transfer does not use a PEC byte. 1: The transfer uses a PEC byte. NDATAL: Next Data Length 0: No data to send (see Section 47.9.3.11 “Alternative Command”). 1–255: Number of bytes to send for the next transfer. NDIR: Next Transfer Direction 0: Write direction. 1: Read direction. NPEC: Next PEC Request (SMBus Mode only) 0: The next transfer does not use a PEC byte. 1: The next transfer uses a PEC byte.  2017 Microchip Technology Inc. DS60001476B-page 1633 SAMA5D2 SERIES 47.10.77 TWI Filter Register Name: FLEX_TWI_FILTR Address: 0xF8034644 (0), 0xF8038644 (1), 0xFC010644 (2), 0xFC014644 (3), 0xFC018644 (4) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 9 THRES 8 7 – 6 – 5 – 4 – 3 – 2 PADFCFG 1 PADFEN 0 FILT FILT: RX Digital Filter 0: No filtering applied on TWI inputs. 1: TWI input filtering is active. (Only in Standard and Fast modes) Note: TWI digital input filtering follows a majority decision based on three samples from SDA/SCL lines at peripheral clock frequency. PADFEN: PAD Filter Enable 0: PAD analog filter is disabled. 1: PAD analog filter is enabled. (The analog filter must be enabled if High-speed mode is enabled.) PADFCFG: PAD Filter Config See the section “Electrical Characteristics” for filter configuration details. THRES: Digital Filter Threshold 0: No filtering applied on TWI inputs. 1–7: Maximum pulse width of spikes which will be suppressed by the input filter, defined in peripheral clock cycles. DS60001476B-page 1634  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.78 TWI SleepWalking Matching Register Name: FLEX_TWI_SWMR Address: 0xF803464C (0), 0xF803864C (1), 0xFC01064C (2), 0xFC01464C (3), 0xFC01864C (4) Access: Read/Write 31 30 29 28 27 26 25 24 DATAM 23 – 22 21 20 19 SADR3 18 17 16 15 – 14 13 12 11 SADR2 10 9 8 7 – 6 5 4 3 SADR1 2 1 0 SADR1: Slave Address 1 Slave address 1. The TWI module will match on this additional address if SADR1EN bit is enabled. SADR2: Slave Address 2 Slave address 2. The TWI module will match on this additional address if SADR2EN bit is enabled. SADR3: Slave Address 3 Slave address 3. The TWI module will match on this additional address if SADR3EN bit is enabled. DATAM: Data Match The TWI module will extend the SleepWalking matching process to the first received data comparing it with DATAM if DATAMEN bit is enabled.  2017 Microchip Technology Inc. DS60001476B-page 1635 SAMA5D2 SERIES 47.10.79 TWI FIFO Mode Register Name: FLEX_TWI_FMR Address: 0xF8034650 (0), 0xF8038650 (1), 0xFC010650 (2), 0xFC014650 (3), 0xFC018650 (4) Access: Read/Write 31 30 – – 29 28 27 26 25 24 23 22 – – 18 17 16 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 3 2 1 – – – – RXFTHRES 21 20 19 TXFTHRES 4 RXRDYM 0 TXRDYM TXRDYM: Transmitter Ready Mode If FIFOs are enabled, the FLEX_TWI_SR.TXRDY flag behaves as follows. Value Name Description 0 ONE_DATA TXRDY will be at level ‘1’ when at least one data can be written in the Transmit FIFO 1 TWO_DATA TXRDY will be at level ‘1’ when at least two data can be written in the Transmit FIFO 2 FOUR_DATA TXRDY will be at level ‘1’ when at least four data can be written in the Transmit FIFO RXRDYM: Receiver Ready Mode If FIFOs are enabled, the FLEX_TWI_SR.RXRDY flag behaves as follows. Value Name Description 0 ONE_DATA RXRDY will be at level ‘1’ when at least one unread data is in the Receive FIFO 1 TWO_DATA RXRDY will be at level ‘1’ when at least two unread data are in the Receive FIFO 2 FOUR_DATA RXRDY will be at level ‘1’ when at least four unread data are in the Receive FIFO TXFTHRES: Transmit FIFO Threshold 0–16: Defines the Transmit FIFO threshold value (number of data). The FLEX_TWI_FSR.TXFTH flag will be set when Transmit FIFO goes from “above” threshold state to “equal or below” threshold state. RXFTHRES: Receive FIFO Threshold 0–16: Defines the Receive FIFO threshold value (number of data). The FLEX_TWI_FSR.RXFTH flag will be set when Receive FIFO goes from “below” threshold state to “equal to or above” threshold state. DS60001476B-page 1636  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.80 TWI FIFO Level Register Name: FLEX_TWI_FLR Address: 0xF8034654 (0), 0xF8038654 (1), 0xFC010654 (2), 0xFC014654 (3), 0xFC018654 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – RXFL TXFL TXFL: Transmit FIFO Level 0: There is no data in the Transmit FIFO 1–16: Indicates the number of data in the Transmit FIFO RXFL: Receive FIFO Level 0: There is no unread data in the Receive FIFO 1–16: Indicates the number of unread data in the Receive FIFO  2017 Microchip Technology Inc. DS60001476B-page 1637 SAMA5D2 SERIES 47.10.81 TWI FIFO Status Register Name: FLEX_TWI_FSR Address: 0xF8034660 (0), 0xF8038660 (1), 0xFC010660 (2), 0xFC014660 (3), 0xFC018660 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: Transmit FIFO Empty Flag (cleared on read) 0: Transmit FIFO is not empty. 1: Transmit FIFO has been emptied since the last read of FLEX_TWI_FSR. TXFFF: Transmit FIFO Full Flag (cleared on read) 0: Transmit FIFO is not full. 1: Transmit FIFO has been filled since the last read of FLEX_TWI_FSR. TXFTHF: Transmit FIFO Threshold Flag (cleared on read) 0: Number of data in Transmit FIFO is above TXFTHRES threshold. 1: Number of data in Transmit FIFO has reached TXFTHRES threshold since the last read of FLEX_TWI_FSR. RXFEF: Receive FIFO Empty Flag 0: Receive FIFO is not empty. 1: Receive FIFO has been emptied since the last read of FLEX_TWI_FSR. RXFFF: Receive FIFO Full Flag 0: Receive FIFO is not empty. 1: Receive FIFO has been filled since the last read of FLEX_TWI_FSR. RXFTHF: Receive FIFO Threshold Flag 0: Number of unread data in Receive FIFO is below RXFTHRES threshold. 1: Number of unread data in Receive FIFO has reached RXFTHRES threshold since the last read of FLEX_TWI_FSR. TXFPTEF: Transmit FIFO Pointer Error Flag 0: No Transmit FIFO pointer occurred 1: Transmit FIFO pointer error occurred. Transceiver must be reset See Section 47.9.6.10 ”FIFO Pointer Error” for details. DS60001476B-page 1638  2017 Microchip Technology Inc. SAMA5D2 SERIES RXFPTEF: Receive FIFO Pointer Error Flag 0: No Receive FIFO pointer occurred 1: Receive FIFO pointer error occurred. Receiver must be reset See Section 47.9.6.10 ”FIFO Pointer Error” for details.  2017 Microchip Technology Inc. DS60001476B-page 1639 SAMA5D2 SERIES 47.10.82 TWI FIFO Interrupt Enable Register Name: FLEX_TWI_FIER Address: 0xF8034664 (0), 0xF8038664 (1), 0xFC010664 (2), 0xFC014664 (3), 0xFC018664 (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Enable TXFFF: TXFFF Interrupt Enable TXFTHF: TXFTHF Interrupt Enable RXFEF: RXFEF Interrupt Enable RXFFF: RXFFF Interrupt Enable RXFTHF: RXFTHF Interrupt Enable TXFPTEF: TXFPTEF Interrupt Enable RXFPTEF: RXFPTEF Interrupt Enable DS60001476B-page 1640  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.83 TWI FIFO Interrupt Disable Register Name: FLEX_TWI_FIDR Address: 0xF8034668 (0), 0xF8038668 (1), 0xFC010668 (2), 0xFC014668 (3), 0xFC018668 (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Disable TXFFF: TXFFF Interrupt Disable TXFTHF: TXFTHF Interrupt Disable RXFEF: RXFEF Interrupt Disable RXFFF: RXFFF Interrupt Disable RXFTHF: RXFTHF Interrupt Disable TXFPTEF: TXFPTEF Interrupt Disable RXFPTEF: RXFPTEF Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 1641 SAMA5D2 SERIES 47.10.84 TWI FIFO Interrupt Mask Register Name: FLEX_TWI_FIMR Address: 0xF803466C (0), 0xF803866C (1), 0xFC01066C (2), 0xFC01466C (3), 0xFC01866C (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXFPTEF TXFPTEF RXFTHF RXFFF RXFEF TXFTHF TXFFF TXFEF TXFEF: TXFEF Interrupt Mask TXFFF: TXFFF Interrupt Mask TXFTHF: TXFTHF Interrupt Mask RXFEF: RXFEF Interrupt Mask RXFFF: RXFFF Interrupt Mask RXFTHF: RXFTHF Interrupt Mask TXFPTEF: TXFPTEF Interrupt Mask RXFPTEF: RXFPTEF Interrupt Mask DS60001476B-page 1642  2017 Microchip Technology Inc. SAMA5D2 SERIES 47.10.85 TWI Write Protection Mode Register Name: FLEX_TWI_WPMR Address: 0xF80346E4 (0), 0xF80386E4 (1), 0xFC0106E4 (2), 0xFC0146E4 (3), 0xFC0186E4 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x545749 (“TWI” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x545749 (“TWI” in ASCII). See Section 47.9.8 ”TWI Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value 0x545749 Name PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of bit WPEN. Always reads as 0 DS60001476B-page 1643 SAMA5D2 SERIES 47.10.86 TWI Write Protection Status Register Name: FLEX_TWI_WPSR Address: 0xF80346E8 (0), 0xF80386E8 (1), 0xFC0106E8 (2), 0xFC0146E8 (3), 0xFC0186E8 (4) Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 23 22 21 20 WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protect Violation Status 0: No Write Protection Violation has occurred since the last read of FLEX_TWI_WPSR. 1: A Write Protection Violation has occurred since the last read of FLEX_TWI_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 1644  2017 Microchip Technology Inc. SAMA5D2 SERIES 48. Universal Asynchronous Receiver Transmitter (UART) 48.1 Description The Universal Asynchronous Receiver Transmitter (UART) features a two-pin UART that can be used for communication and trace purposes and offers an ideal medium for in-situ programming solutions. Moreover, the association with a DMA controller permits packet handling for these tasks with processor time reduced to a minimum. 48.2 Embedded Characteristics • Two-pin UART - Independent Receiver and Transmitter with a Common Programmable Baud Rate Generator - Baud Rate can be Driven by Processor-Independent Generic Source Clock - Even, Odd, Mark or Space Parity Generation - Parity, Framing and Overrun Error Detection - Automatic Echo, Local Loopback and Remote Loopback Channel Modes - Digital Filter on Receive Line - Interrupt Generation - Support for Two DMA Channels with Connection to Receiver and Transmitter - Supports Asynchronous Partial Wakeup on Receive Line Activity (SleepWalking) - Comparison Function on Received Character - Receiver Timeout - Register Write Protection 48.3 Block Diagram Figure 48-1: UART Block Diagram UART UTXD Transmit DMA Controller Parallel Input/ Output Baud Rate Generator Receive bus clock URXD Bridge APB Interrupt Control GCLK PMC Table 48-1: uart_irq peripheral clock UART Pin Description Pin Name Description Type URXD UART Receive Data Input UTXD UART Transmit Data Output  2017 Microchip Technology Inc. DS60001476B-page 1645 SAMA5D2 SERIES 48.4 Product Dependencies 48.4.1 I/O Lines The UART pins are multiplexed with PIO lines. The user must first configure the corresponding PIO Controller to enable I/O line operations of the UART. Table 48-2: I/O Lines Instance Signal I/O Line Peripheral UART0 URXD0 PB26 C UART0 UTXD0 PB27 C UART1 URXD1 PC7 E UART1 URXD1 PD2 A UART1 UTXD1 PC8 E UART1 UTXD1 PD3 A UART2 URXD2 PD4 B UART2 URXD2 PD19 C UART2 URXD2 PD23 A UART2 UTXD2 PD5 B UART2 UTXD2 PD20 C UART2 UTXD2 PD24 A UART3 URXD3 PB11 C UART3 URXD3 PC12 D UART3 URXD3 PC31 C UART3 UTXD3 PB12 C UART3 UTXD3 PC13 D UART3 UTXD3 PD0 C UART4 URXD4 PB3 A UART4 UTXD4 PB4 A 48.4.2 Power Management The UART clock can be controlled through the Power Management Controller (PMC). In this case, the user must first configure the PMC to enable the UART clock. Usually, the peripheral identifier used for this purpose is 1. In SleepWalking mode (asynchronous partial wakeup), the PMC must be configured to enable SleepWalking for the UART in the Sleepwalking Enable Register (PMC_SLPWK_ER). Depending on the instructions (requests) provided by the UART to the PMC, the system clock may or may not be automatically provided to the UART. DS60001476B-page 1646  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.4.3 Interrupt Sources The UART interrupt line is connected to one of the interrupt sources of the Interrupt Controller. Interrupt handling requires programming of the Interrupt Controller before configuring the UART. Table 48-3: Peripheral IDs Instance ID UART0 24 UART1 25 UART2 26 UART3 27 UART4 28  2017 Microchip Technology Inc. DS60001476B-page 1647 SAMA5D2 SERIES 48.5 Functional Description The UART operates in Asynchronous mode only and supports only 8-bit character handling (with parity). It has no clock pin. The UART is made up of a receiver and a transmitter that operate independently, and a common baud rate generator. Receiver timeout and transmitter time guard are not implemented. However, all the implemented features are compatible with those of a standard USART. 48.5.1 Baud Rate Generator The baud rate generator provides the bit period clock named baud rate clock to both the receiver and the transmitter. The baud rate clock is the peripheral clock divided by 16 times the clock divisor (CD) value written in the Baud Rate Generator register (UART_BRGR). If UART_BRGR is set to 0, the baud rate clock is disabled and the UART remains inactive. The maximum allowable baud rate is peripheral clock or GCLK divided by 16. The minimum allowable baud rate is peripheral clock divided by (16 x 65536). The clock source driving the baud rate generator (peripheral clock or GCLK) can be selected by writing the bit BRSRCCK in UART_MR. If GCLK is selected, the baud rate is independent of the processor/bus clock. Thus the processor clock can be changed while UART is enabled. The processor clock frequency changes must be performed only by programming the field PRES in PMC_MCKR (see PMC section). Other methods to modify the processor/bus clock frequency (PLL multiplier, etc.) are forbidden when UART is enabled. The peripheral clock frequency must be at least three times higher than GCLK. Figure 48-2: Baud Rate Generator BRSRCCK CD CD Peripheral clock 0 16-bit Counter GCLK OUT >1 1 1 0 Divide by 16 Baud Rate Clock 0 Receiver Sampling Clock 48.5.2 48.5.2.1 Receiver Receiver Reset, Enable and Disable After device reset, the UART receiver is disabled and must be enabled before being used. The receiver can be enabled by writing the Control Register (UART_CR) with the bit RXEN at 1. At this command, the receiver starts looking for a start bit. The programmer can disable the receiver by writing UART_CR with the bit RXDIS at 1. If the receiver is waiting for a start bit, it is immediately stopped. However, if the receiver has already detected a start bit and is receiving the data, it waits for the stop bit before actually stopping its operation. The receiver can be put in reset state by writing UART_CR with the bit RSTRX at 1. In this case, the receiver immediately stops its current operations and is disabled, whatever its current state. If RSTRX is applied when data is being processed, this data is lost. 48.5.2.2 Start Detection and Data Sampling The UART only supports asynchronous operations, and this affects only its receiver. The UART receiver detects the start of a received character by sampling the URXD signal until it detects a valid start bit. A low level (space) on URXD is interpreted as a valid start bit if it is detected for more than seven cycles of the sampling clock, which is 16 times the baud rate. Hence, a space that is longer than 7/16 of the bit period is detected as a valid start bit. A space which is 7/16 of a bit period or shorter is ignored and the receiver continues to wait for a valid start bit. When a valid start bit has been detected, the receiver samples the URXD at the theoretical midpoint of each bit. It is assumed that each bit lasts 16 cycles of the sampling clock (1-bit period) so the bit sampling point is eight cycles (0.5-bit period) after the start of the bit. The first sampling point is therefore 24 cycles (1.5-bit periods) after detecting the falling edge of the start bit. Each subsequent bit is sampled 16 cycles (1-bit period) after the previous one. DS60001476B-page 1648  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 48-3: Start Bit Detection URXD S D0 D1 D2 D3 D4 D5 D6 D7 P D0 stop S D1 D2 D3 D4 D5 D6 D7 P stop RXRDY OVRE RSTSTA Figure 48-4: Character Reception Example: 8-bit, parity enabled 1 stop 0.5 bit period 1 bit period URXD Sampling 48.5.2.3 D0 D1 True Start Detection D2 D3 D4 D5 D6 Stop Bit D7 Parity Bit Receiver Ready When a complete character is received, it is transferred to the Receive Holding Register (UART_RHR) and the RXRDY status bit in the Status Register (UART_SR) is set. The bit RXRDY is automatically cleared when UART_RHR is read. Figure 48-5: URXD Receiver Ready S D0 D1 D2 D3 D4 D5 D6 D7 S P D0 D1 D2 D3 D4 D5 D6 D7 P RXRDY Read UART_RHR 48.5.2.4 Receiver Overrun The OVRE status bit in UART_SR is set if UART_RHR has not been read by the software (or the DMA Controller) since the last transfer, the RXRDY bit is still set and a new character is received. OVRE is cleared when the software writes a 1 to the bit RSTSTA (Reset Status) in UART_CR. Figure 48-6: URXD Receiver Overrun S D0 D1 D2 D3 D4 D5 D6 D7 P stop S D0 D1 D2 D3 D4 D5 D6 D7 P stop RXRDY OVRE RSTSTA  2017 Microchip Technology Inc. DS60001476B-page 1649 SAMA5D2 SERIES 48.5.2.5 Parity Error Each time a character is received, the receiver calculates the parity of the received data bits, in accordance with the field PAR in the Mode Register (UART_MR). It then compares the result with the received parity bit. If different, the parity error bit PARE in UART_SR is set at the same time RXRDY is set. The parity bit is cleared when UART_CR is written with the bit RSTSTA (Reset Status) at 1. If a new character is received before the reset status command is written, the PARE bit remains at 1. Figure 48-7: URXD Parity Error S D0 D1 D2 D3 D4 D5 D6 D7 P stop RXRDY PARE Wrong Parity Bit 48.5.2.6 RSTSTA Receiver Framing Error When a start bit is detected, it generates a character reception when all the data bits have been sampled. The stop bit is also sampled and when it is detected at 0, the FRAME (Framing Error) bit in UART_SR is set at the same time the RXRDY bit is set. The FRAME bit remains high until the Control Register (UART_CR) is written with the bit RSTSTA at 1. Figure 48-8: URXD Receiver Framing Error S D0 D1 D2 D3 D4 D5 D6 D7 P stop RXRDY FRAME Stop Bit Detected at 0 48.5.2.7 RSTSTA Receiver Digital Filter The UART embeds a digital filter on the receive line. It is disabled by default and can be enabled by writing a logical 1 in the FILTER bit of UART_MR. When enabled, the receive line is sampled using the 16x bit clock and a three-sample filter (majority 2 over 3) determines the value of the line. 48.5.2.8 Receiver Timeout The Receiver Timeout provides support in handling variable-length frames. This feature detects an idle condition on the RXD line. When a timeout is detected, the bit TIMEOUT in the UART_SR rises and can generate an interrupt, thus indicating to the driver an end of frame. The timeout delay period (during which the receiver waits for a new character) is programmed in the TO field of the Receiver Timeout register (UART_RTOR). If the TO field is written to 0, the Receiver Timeout is disabled and no timeout is detected. The TIMEOUT bit in the UART_SR remains at 0. Otherwise, the receiver loads an 8-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 UART_SR rises. Then, the user can either: • stop the counter clock until a new character is received. This is performed by writing a one to the STTTO (start Timeout) bit in the UART_CR. In this case, the idle state on RXD before a new character is received does not provide a timeout. This prevents having to handle an interrupt before a character is received and allows waiting for the next idle state on RXD after a frame is received, or • obtain an interrupt while no character is received. This is performed by writing a one to the RETTO (Reload and Start Timeout) bit in the UART_CR. If RETTO is performed, the counter starts counting down immediately from the TO value. This enables generation of a periodic interrupt so that a user timeout can be handled, for example when no key is pressed on a keyboard. DS60001476B-page 1650  2017 Microchip Technology Inc. SAMA5D2 SERIES 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 timeout. 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 TO value. This enables generation of a periodic interrupt so that a user timeout can be handled, for example when no key is pressed on a keyboard. Figure 48-9 shows the block diagram of the Receiver Timeout feature. Figure 48-9: Receiver Timeout Block Diagram TO Baud Rate Clock 1 D Q Clock 8-bit Time-out Counter 8-bit Value = STTTO Character Received Clear Load TIMEOUT 0 RETTO Table 48-4 gives the maximum timeout period for some standard baud rates. Table 48-4: Maximum Timeout Period Baud Rate (bit/s) Bit Time (µs) Timeout (µs) 600 1,667 425,085 1,200 833 212,415 2,400 417 106,335 4,800 208 53,040 9,600 104 26,520 14,400 69 17,595 19,200 52 13,260 28,800 35 8,925 38,400 26 6,630 56,000 18 4,590 57,600 17 4,335 200,000 5 1,275 48.5.3 48.5.3.1 Transmitter Transmitter Reset, Enable and Disable After device reset, the UART transmitter is disabled and must be enabled before being used. The transmitter is enabled by writing UART_CR with the bit TXEN at 1. From this command, the transmitter waits for a character to be written in the Transmit Holding Register (UART_THR) before actually starting the transmission. The programmer can disable the transmitter by writing UART_CR with the bit TXDIS at 1. If the transmitter is not operating, it is immediately stopped. However, if a character is being processed into the internal shift register and/or a character has been written in the UART_THR, the characters are completed before the transmitter is actually stopped. The programmer can also put the transmitter in its reset state by writing the UART_CR with the bit RSTTX at 1. This immediately stops the transmitter, whether or not it is processing characters.  2017 Microchip Technology Inc. DS60001476B-page 1651 SAMA5D2 SERIES 48.5.3.2 Transmit Format The UART transmitter drives the pin UTXD at the baud rate clock speed. The line is driven depending on the format defined in UART_MR and the data stored in the internal shift register. One start bit at level 0, then the 8 data bits, from the lowest to the highest bit, one optional parity bit and one stop bit at 1 are consecutively shifted out as shown in the following figure. The field PARE in UART_MR defines whether or not a parity bit is shifted out. When a parity bit is enabled, it can be selected between an odd parity, an even parity, or a fixed space or mark bit. Figure 48-10: Character Transmission Example: Parity enabled Baud Rate Clock UTXD Start Bit 48.5.3.3 D0 D1 D2 D3 D4 D5 D6 D7 Parity Bit Stop Bit Transmitter Control When the transmitter is enabled, the bit TXRDY (Transmitter Ready) is set in UART_SR. The transmission starts when the programmer writes in the UART_THR, and after the written character is transferred from UART_THR to the internal shift register. The TXRDY bit remains high until a second character is written in UART_THR. As soon as the first character is completed, the last character written in UART_THR is transferred into the internal shift register and TXRDY rises again, showing that the holding register is empty. When both the internal shift register and UART_THR are empty, i.e., all the characters written in UART_THR have been processed, the TXEMPTY bit rises after the last stop bit has been completed. Figure 48-11: Transmitter Control UART_THR Data 0 Data 1 Shift Register UTXD Data 0 S Data 0 Data 1 P stop S Data 1 P stop TXRDY TXEMPTY Write Data 0 in UART_THR 48.5.4 Write Data 1 in UART_THR DMA Support Both the receiver and the transmitter of the UART are connected to a DMA Controller (DMAC) channel. The DMA Controller channels are programmed via registers that are mapped within the DMAC user interface. 48.5.5 Comparison Function on Received Character When a comparison is performed on a received character, the result of the comparison is reported on the CMP flag in UART_SR when UART_RHR is loaded with the new received character. The CMP flag is cleared by writing a one to the RSTSTA bit in UART_CR. UART_CMPR (see Section 48.6.10 “UART Comparison Register”) can be programmed to provide different comparison methods. These are listed below: • If VAL1 equals VAL2, then the comparison is performed on a single value and the flag is set to 1 if the received character equals DS60001476B-page 1652  2017 Microchip Technology Inc. SAMA5D2 SERIES VAL1. • If VAL1 is strictly lower than VAL2, then any value between VAL1 and VAL2 sets the CMP flag. • If VAL1 is strictly higher than VAL2, then the flag CMP is set to 1 if either received character equals VAL1 or VAL2. By programming the CMPMODE bit to 1, the comparison function result triggers the start of the loading of UART_RHR (see Figure 4812). The trigger condition occurs as soon as the received character value matches the condition defined by the programming of VAL1, VAL2 and CMPPAR in UART_CMPR. The comparison trigger event can be restarted by writing a one to the REQCLR bit in UART_CR. Figure 48-12: Receive Holding Register Management CMPMODE = 1, VAL1 = VAL2 = 0x06 Peripheral Clock RXD 0x0F 0x06 0x08 0xF0 0x06 RXRDY rising enabled RXRDY Write REQCLR RDR 48.5.6 0x0F 0x06 0xF0 0x08 0x06 Asynchronous and Partial Wakeup (SleepWalking) Asynchronous and partial wakeup (SleepWalking) is a means of data preprocessing that qualifies an incoming event, thus allowing the UART to decide whether or not to wake up the system. SleepWalking is used primarily when the system is in Wait mode (refer to Section 33. “Power Management Controller (PMC)”) but can also be enabled when the system is fully running. No access must be performed in the UART between the enable of asynchronous partial wakeup and the wakeup performed by the UART. If the system is in Wait mode and asynchronous and partial wakeup is enabled, the maximum baud rate that can be achieved equals 19200. If the system is running or in Sleep mode, the maximum baud rate that can be achieved equals 115200 or higher. This limit is bounded by the peripheral clock frequency divided by 16. The UART_RHR must be read before enabling asynchronous and partial wakeup. When SleepWalking is enabled for the UART (refer to Section 33. “Power Management Controller (PMC)”), the PMC decodes a clock request from the UART. The request is generated as soon as there is a falling edge on the RXD line as this may indicate the beginning of a start bit. If the system is in Wait mode (processor and peripheral clocks switched off), the PMC restarts the fast RC oscillator and provides the clock only to the UART. As soon as the clock is provided by the PMC, the UART processes the received frame and compares the received character with VAL1 and VAL2 in UART_CMPR (Section 48.6.10 “UART Comparison Register”). The UART instructs the PMC to disable the clock if the received character value does not meet the conditions defined by VAL1 and VAL2 fields in UART_CMPR (see Figure 48-14). If the received character value meets the conditions, the UART instructs the PMC to exit the full system from Wait mode (see Figure 48-13). The VAL1 and VAL2 fields can be programmed to provide different comparison methods and thus matching conditions. • If VAL1 equals VAL2, then the comparison is performed on a single value and the wakeup is triggered if the received character equals VAL1. • If VAL1 is strictly lower than VAL2, then any value between VAL1 and VAL2 wakes up the system. • If VAL1 is strictly higher than VAL2, then the wakeup is triggered if the received character equals VAL1 or VAL2. • If VAL1 = 0 and VAL2 = 255, the wakeup is triggered as soon as a character is received.  2017 Microchip Technology Inc. DS60001476B-page 1653 SAMA5D2 SERIES The matching condition can be configured to include the parity bit (CMPPAR in UART_CMPR). Thus, if the received data matches the comparison condition defined by VAL1 and VAL2 but a parity error is encountered, the matching condition is cancelled and the UART instructs the PMC to disable the clock (see Figure 48-14). If the processor and peripherals are running, the UART can be configured in Asynchronous and partial wakeup mode by enabling the PMC_SLPWK_ER (see PMC section). When activity is detected on the receive line, the UART requests the clock from the PMC and the comparison is performed. If there is a comparison match, the UART continues to request the clock. If there is no match, the clock is switched off for the UART only, until a new activity is detected. The CMPMODE configuration has no effect when Asynchronous and Partial Wakeup mode is enabled for the UART (see PMC_SLPWK_ER in the PMC section). When the system is kept in active/running mode and the UART enters Asynchronous and Partial Wakeup mode, the flag CMP must be programmed as the unique source of the UART interrupt. When the system exits Wait mode as the result of a matching condition, the RXRDY flag is used to determine if the UART is the source of exit. Note: If the SleepWalking function is enabled on the UART, a divide by 8 of the peripheral clock versus the bus clock is not possible. Other dividers can be used with no constraints. DS60001476B-page 1654  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 48-13: Asynchronous Wakeup Use Case Examples Case with VAL1 = VAL2 = 0x55, CMPPAR = 1 RXD Idle Start D0 D1 D7 Parity = OK RHR = 0x55, VAL1 = 0x55 => match PCLK_req Stop => match and Parity OK PCLK (Main RC) SystemWakeUp_req Case with VAL1 = 0x54, VAL2 = 0x56, CMPPAR = 1 RXD Idle Start D0 D1 D7 Parity = OK RHR = 0x55, VAL1 = 0x54, VAL2 = 0x56 => match PCLK_req Stop => match and Parity OK PCLK (Main RC) SystemWakeUp_req Case with VAL1 = 0x75, VAL2 = 0x76, CMPPAR = 0 RXD Idle Start PCLK_req D0 D1 D7 Parity = NOK Stop RHR = 0x75, VAL1 = 0x75 => match PCLK (Main RC) SystemWakeUp_req  2017 Microchip Technology Inc. DS60001476B-page 1655 SAMA5D2 SERIES Figure 48-14: Asynchronous Event Generating Only Partial Wakeup Case with VAL1 = VAL2 = 0x00, CMPPAR = Don’t care RXD Idle Start D0 D1 D7 Parity Stop RHR = 0x85, VAL1 = 0x00 => no match PCLK_req PCLK (Main RC) SystemWakeUp_req Case with VAL1 = 0xF5, VAL2 = 0xF5, CMPPAR = 1 RXD Idle Start PCLK_req D0 D1 D7 Parity = NOK RHR = 0xF5, VAL1/2 = 0xF5 => match Stop => DATA match and Parity NOK PCLK (Main RC) SystemWakeUp_req 48.5.7 Register Write Protection To prevent any single software error from corrupting UART behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the UART Write Protection Mode Register (UART_WPMR). The following registers can be write-protected: • UART Mode Register • UART Baud Rate Generator Register • UART Comparison Register DS60001476B-page 1656  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.5.8 Test Modes The UART supports three test modes. These modes of operation are programmed by using the CHMODE field in UART_MR. The Automatic Echo mode allows a bit-by-bit retransmission. When a bit is received on the URXD line, it is sent to the UTXD line. The transmitter operates normally, but has no effect on the UTXD line. The Local Loopback mode allows the transmitted characters to be received. UTXD and URXD pins are not used and the output of the transmitter is internally connected to the input of the receiver. The URXD pin level has no effect and the UTXD line is held high, as in idle state. The Remote Loopback mode directly connects the URXD pin to the UTXD line. The transmitter and the receiver are disabled and have no effect. This mode allows a bit-by-bit retransmission. Figure 48-15: Test Modes Automatic Echo RXD Receiver Transmitter Disabled TXD Local Loopback Disabled Receiver RXD VDD Disabled Transmitter Remote Loopback TXD VDD Disabled RXD Receiver Disabled Transmitter  2017 Microchip Technology Inc. TXD DS60001476B-page 1657 SAMA5D2 SERIES 48.6 Universal Asynchronous Receiver Transmitter (UART) User Interface Table 48-5: Register Mapping Offset Register Name Access Reset 0x0000 Control Register UART_CR Write-only – 0x0004 Mode Register UART_MR Read/Write 0x0 0x0008 Interrupt Enable Register UART_IER Write-only – 0x000C Interrupt Disable Register UART_IDR Write-only – 0x0010 Interrupt Mask Register UART_IMR Read-only 0x0 0x0014 Status Register UART_SR Read-only – 0x0018 Receive Holding Register UART_RHR Read-only 0x0 0x001C Transmit Holding Register UART_THR Write-only – 0x0020 Baud Rate Generator Register UART_BRGR Read/Write 0x0 0x0024 Comparison Register UART_CMPR Read/Write 0x0 0x0028 Receiver Timeout Register UART_RTOR Read/Write 0x0 0x002C–0x003C Reserved – – – 0x0040–0x00E0 Reserved – – – Read/Write 0x0 0x00E4 Write Protection Mode Register 0x00E8 Reserved – – – 0x00EC–0x00FC Reserved – – – DS60001476B-page 1658 UART_WPMR  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.1 UART Control Register Name: UART_CR Address: 0xF801C000 (0), 0xF8020000 (1), 0xF8024000 (2), 0xFC008000 (3), 0xFC00C000 (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – REQCLR STTTO RETTO – RSTSTA 7 6 5 4 3 2 1 0 TXDIS TXEN RXDIS RXEN RSTTX RSTRX – – RSTRX: Reset Receiver 0: No effect. 1: The receiver logic is reset and disabled. If a character is being received, the reception is aborted. RSTTX: Reset Transmitter 0: No effect. 1: The transmitter logic is reset and disabled. If a character is being transmitted, the transmission is aborted. RXEN: Receiver Enable 0: No effect. 1: The receiver is enabled if RXDIS is 0. RXDIS: Receiver Disable 0: No effect. 1: The receiver is disabled. If a character is being processed and RSTRX is not set, the character is completed before the receiver is stopped. TXEN: Transmitter Enable 0: No effect. 1: The transmitter is enabled if TXDIS is 0. TXDIS: Transmitter Disable 0: No effect. 1: The transmitter is disabled. If a character is being processed and a character has been written in the UART_THR and RSTTX is not set, both characters are completed before the transmitter is stopped. RSTSTA: Reset Status 0: No effect. 1: Resets the status bits PARE, FRAME, CMP and OVRE in the UART_SR.  2017 Microchip Technology Inc. DS60001476B-page 1659 SAMA5D2 SERIES RETTO: Rearm Timeout 0: No effect. 1: Restarts timeout. STTTO: Start Timeout 0: No effect. 1: Starts waiting for a character before clocking the timeout counter. Resets status bit TIMEOUT in UART_SR. REQCLR: Request Clear SleepWalking enabled: 0: No effect. 1: Bit REQCLR clears the potential clock request currently issued by UART, thus the potential system wakeup is cancelled. SleepWalking disabled: 0: No effect. 1: Bit REQCLR restarts the comparison trigger to enable receive holding register loading. DS60001476B-page 1660  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.2 UART Mode Register Name: UART_MR Address: 0xF801C004 (0), 0xF8020004 (1), 0xF8024004 (2), 0xFC008004 (3), 0xFC00C004 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 14 13 12 11 10 9 – BRSRCCK 15 CHMODE 8 PAR – 7 6 5 4 3 2 1 0 – – – FILTER – – – – FILTER: Receiver Digital Filter 0 (DISABLED): UART does not filter the receive line. 1 (ENABLED): UART filters the receive line using a three-sample filter (16x-bit clock) (2 over 3 majority). PAR: Parity Type Value Name Description 0 EVEN Even Parity 1 ODD Odd Parity 2 SPACE Space: parity forced to 0 3 MARK Mark: parity forced to 1 4 NO No parity BRSRCCK: Baud Rate Source Clock 0 (PERIPH_CLK): The baud rate is driven by the peripheral clock 1 (GCLK): The baud rate is driven by a PMC-programmable clock GCLK (see section Power Management Controller (PMC)). CHMODE: Channel Mode Value Name Description 0 NORMAL Normal mode 1 AUTOMATIC Automatic echo 2 LOCAL_LOOPBACK Local loopback 3 REMOTE_LOOPBACK Remote loopback  2017 Microchip Technology Inc. DS60001476B-page 1661 SAMA5D2 SERIES 48.6.3 UART Interrupt Enable Register Name: UART_IER Address: 0xF801C008 (0), 0xF8020008 (1), 0xF8024008 (2), 0xFC008008 (3), 0xFC00C008 (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 CMP – – – – – TXEMPTY TIMEOUT 7 6 5 4 3 2 1 0 PARE FRAME OVRE – – – TXRDY RXRDY The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. RXRDY: Enable RXRDY Interrupt TXRDY: Enable TXRDY Interrupt OVRE: Enable Overrun Error Interrupt FRAME: Enable Framing Error Interrupt PARE: Enable Parity Error Interrupt TIMEOUT: Enable Timeout Interrupt TXEMPTY: Enable TXEMPTY Interrupt CMP: Enable Comparison Interrupt DS60001476B-page 1662  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.4 UART Interrupt Disable Register Name: UART_IDR Address: 0xF801C00C (0), 0xF802000C (1), 0xF802400C (2), 0xFC00800C (3), 0xFC00C00C (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 CMP – – – – – TXEMPTY TIMEOUT 7 6 5 4 3 2 1 0 PARE FRAME OVRE – – – TXRDY RXRDY The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. RXRDY: Disable RXRDY Interrupt TXRDY: Disable TXRDY Interrupt OVRE: Disable Overrun Error Interrupt FRAME: Disable Framing Error Interrupt PARE: Disable Parity Error Interrupt TIMEOUT: Disable Timeout Interrupt TXEMPTY: Disable TXEMPTY Interrupt CMP: Disable Comparison Interrupt  2017 Microchip Technology Inc. DS60001476B-page 1663 SAMA5D2 SERIES 48.6.5 UART Interrupt Mask Register Name: UART_IMR Address: 0xF801C010 (0), 0xF8020010 (1), 0xF8024010 (2), 0xFC008010 (3), 0xFC00C010 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 CMP – – – – – TXEMPTY TIMEOUT 7 6 5 4 3 2 1 0 PARE FRAME OVRE – – – TXRDY RXRDY The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. RXRDY: Mask RXRDY Interrupt TXRDY: Disable TXRDY Interrupt OVRE: Mask Overrun Error Interrupt FRAME: Mask Framing Error Interrupt PARE: Mask Parity Error Interrupt TIMEOUT: Mask Timeout Interrupt TXEMPTY: Mask TXEMPTY Interrupt CMP: Mask Comparison Interrupt DS60001476B-page 1664  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.6 UART Status Register Name: UART_SR Address: 0xF801C014 (0), 0xF8020014 (1), 0xF8024014 (2), 0xFC008014 (3), 0xFC00C014 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 CMP – – – – – TXEMPTY TIMEOUT 7 6 5 4 3 2 1 0 PARE FRAME OVRE – – – TXRDY RXRDY RXRDY: Receiver Ready 0: No character has been received since the last read of the UART_RHR, or the receiver is disabled. 1: At least one complete character has been received, transferred to UART_RHR and not yet read. TXRDY: Transmitter Ready 0: A character has been written to UART_THR and not yet transferred to the internal shift register, or the transmitter is disabled. 1: There is no character written to UART_THR not yet transferred to the internal shift register. 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. FRAME: Framing Error 0: No framing error has occurred since the last RSTSTA. 1: At least one framing error has occurred since the last RSTSTA. PARE: Parity Error 0: No parity error has occurred since the last RSTSTA. 1: At least one parity error has occurred since the last RSTSTA. TIMEOUT: Receiver Timeout 0: There has not been a timeout since the last Start Timeout command (STTTO in UART_CR) or the Timeout Register is 0. 1: There has been a timeout since the last Start Timeout command (STTTO in UART_CR). TXEMPTY: Transmitter Empty 0: There are characters in UART_THR, or characters being processed by the transmitter, or the transmitter is disabled. 1: There are no characters in UART_THR and there are no characters being processed by the transmitter. CMP: Comparison Match 0: No received character matches the comparison criteria programmed in VAL1, VAL2 fields and in CMPPAR bit since the last RSTSTA. 1: The received character matches the comparison criteria.  2017 Microchip Technology Inc. DS60001476B-page 1665 SAMA5D2 SERIES 48.6.7 UART Receiver Holding Register Name: UART_RHR Address: 0xF801C018 (0), 0xF8020018 (1), 0xF8024018 (2), 0xFC008018 (3), 0xFC00C018 (4) Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 RXCHR RXCHR: Received Character Last received character if RXRDY is set. DS60001476B-page 1666  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.8 UART Transmit Holding Register Name: UART_THR Address: 0xF801C01C (0), 0xF802001C (1), 0xF802401C (2), 0xFC00801C (3), 0xFC00C01C (4) Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 TXCHR TXCHR: Character to be Transmitted Next character to be transmitted after the current character if TXRDY is not set.  2017 Microchip Technology Inc. DS60001476B-page 1667 SAMA5D2 SERIES 48.6.9 UART Baud Rate Generator Register Name: UART_BRGR Address: 0xF801C020 (0), 0xF8020020 (1), 0xF8024020 (2), 0xFC008020 (3), 0xFC00C020 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 3 2 1 0 CD 7 6 5 4 CD CD: Clock Divisor 0: Baud rate clock is disabled 1 to 65,535: If BRSRCCK = 0: f peripheral clock CD = ------------------------------------16 × Baud Rate If BRSRCCK = 1: f GCLKx CD = ------------------------------------16 × Baud Rate DS60001476B-page 1668  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.10 UART Comparison Register Name: UART_CMPR Address: 0xF801C024 (0), 0xF8020024 (1), 0xF8024024 (2), 0xFC008024 (3), 0xFC00C024 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 VAL2 15 14 13 12 11 10 9 8 – CMPPAR – CMPMODE – – – – 7 6 5 4 3 2 1 0 VAL1 VAL1: First Comparison Value for Received Character 0–255: The received character must be higher or equal to the value of VAL1 and lower or equal to VAL2 to set CMP flag in UART_SR. If asynchronous partial wakeup (SleepWalking) is enabled in PMC_SLPWK_ER, the UART requests a system wakeup if the condition is met. CMPMODE: Comparison Mode Value Name Description 0 FLAG_ONLY Any character is received and comparison function drives CMP flag. 1 START_CONDITION Comparison condition must be met to start reception. CMPPAR: Compare Parity 0: The parity is not checked and a bad parity cannot prevent from waking up the system. 1: The parity is checked and a matching condition on data can be cancelled by an error on parity bit, so no wakeup is performed. VAL2: Second Comparison Value for Received Character 0–255: The received character must be lower or equal to the value of VAL2 and higher or equal to VAL1 to set CMP flag in UART_SR. If asynchronous partial wakeup (SleepWalking) is enabled in PMC_SLPWK_ER, the UART requests a system wakeup if condition is met.  2017 Microchip Technology Inc. DS60001476B-page 1669 SAMA5D2 SERIES 48.6.11 UART Receiver Timeout Register Name: UART_RTOR Address: 0xF801C028 (0), 0xF8020028 (1), 0xF8024028 (2), 0xFC008028 (3), 0xFC00C028 (4) Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 TO TO: Timeout Value 0: The receiver timeout is disabled. 1–255: The receiver timeout is enabled and the timeout delay is TO x bit period. DS60001476B-page 1670  2017 Microchip Technology Inc. SAMA5D2 SERIES 48.6.12 UART Write Protection Mode Register Name: UART_WPMR Address: 0xF801C0E4 (0), 0xF80200E4 (1), 0xF80240E4 (2), 0xFC0080E4 (3), 0xFC00C0E4 (4) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 6 5 4 3 2 1 0 – – – – – – – WPEN WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x554152 (UART in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x554152 (UART in ASCII). See Section 48.5.7 “Register Write Protection” for the list of registers that can be protected. WPKEY: Write Protection Key Value 0x554152 Name PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation. Always reads as 0. DS60001476B-page 1671 SAMA5D2 SERIES 49. Serial Peripheral Interface (SPI) 49.1 Description The Serial Peripheral Interface (SPI) circuit 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 turn being masters (multiple master protocol, contrary to single master protocol where one CPU is always the master while all of the others are always slaves). One master can simultaneously shift data into multiple slaves. However, only one slave can drive its output to write data back to the master at any given time. A slave device is selected when the master asserts its NSS signal. If multiple slave devices exist, the master generates a separate slave select signal for each slave (NPCS). 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(s) of the slave(s). • Master In Slave Out (MISO)—This data line supplies the output data from a slave to the input of the master. There may be no more than one slave transmitting data during any particular transfer. • Serial Clock (SPCK)—This control line is driven by the master and regulates the flow of the data bits. The master can transmit data at a variety of baud rates; there is one SPCK pulse for each bit that is transmitted. • Slave Select (NSS)—This control line allows slaves to be turned on and off by hardware. 49.2 Embedded Characteristics • Master or Slave Serial Peripheral Bus Interface - 8-bit to 16-bit programmable data length per chip select - Programmable phase and polarity per chip select - Programmable transfer delay between consecutive transfers and delay before SPI clock per chip select - Programmable delay between chip selects - Selectable mode fault detection • Master Mode can Drive SPCK up to Peripheral Clock • 16-data Transmit and Receive FIFOs • Master Mode Bit Rate can be Independent of the Processor/Peripheral Clock • Slave Mode Operates on SPCK, Asynchronously with Core and Bus Clock • Four Chip Selects with External Decoder Support Allow Communication with up to 15 Peripherals • Communication with Serial External Devices Supported - Serial memories, such as DataFlash and 3-wire EEPROMs - Serial peripherals, such as ADCs, DACs, LCD controllers, CAN controllers and sensors - External coprocessors • Connection to DMA Channel Capabilities, Optimizing Data Transfers - One channel for the receiver - One channel for the transmitter • Register Write Protection DS60001476B-page 1672  2017 Microchip Technology Inc. SAMA5D2 SERIES 49.3 Block Diagram Figure 49-1: Block Diagram AHB Matrix DMA Peripheral bridge Trigger events Bus clock PMC Peripheral clock SPI GCLK 49.4 Application Block Diagram Figure 49-2: Application Block Diagram: Single Master/Multiple Slave Implementation SPI Master SPCK SPCK MISO MISO MOSI MOSI NPCS0 NSS Slave 0 SPCK NPCS1 NPCS2 NPCS3 NC MISO Slave 1 MOSI NSS SPCK MISO Slave 2 MOSI NSS  2017 Microchip Technology Inc. DS60001476B-page 1673 SAMA5D2 SERIES 49.5 Signal Description Table 49-1: Signal Description Type Pin Name Pin Description Master Slave MISO Master In Slave Out Input Output MOSI Master Out Slave In Output Input SPCK Serial Clock Output Input NPCS1–NPCS3 Peripheral Chip Selects Output Unused NPCS0/NSS Peripheral Chip Select/Slave Select Output Input 49.6 Product Dependencies 49.6.1 I/O Lines The pins used for interfacing the compliant external devices can be multiplexed with PIO lines. The programmer must first program the PIO controllers to assign the SPI pins to their peripheral functions. Table 49-2: I/O Lines Instance Signal I/O Line Peripheral SPI0 SPI0_MISO PA16 A SPI0 SPI0_MISO PA31 C SPI0 SPI0_MOSI PA15 A SPI0 SPI0_MOSI PB0 C SPI0 SPI0_NPCS0 PA17 A SPI0 SPI0_NPCS0 PA30 C SPI0 SPI0_NPCS1 PA18 A SPI0 SPI0_NPCS1 PA29 C SPI0 SPI0_NPCS2 PA19 A SPI0 SPI0_NPCS2 PA27 C SPI0 SPI0_NPCS3 PA20 A SPI0 SPI0_NPCS3 PA28 C SPI0 SPI0_SPCK PA14 A SPI0 SPI0_SPCK PB1 C SPI1 SPI1_MISO PA24 D SPI1 SPI1_MISO PC3 D SPI1 SPI1_MISO PD27 A SPI1 SPI1_MOSI PA23 D SPI1 SPI1_MOSI PC2 D SPI1 SPI1_MOSI PD26 A SPI1 SPI1_NPCS0 PA25 D SPI1 SPI1_NPCS0 PC4 D DS60001476B-page 1674  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 49-2: 49.6.2 I/O Lines (Continued) SPI1 SPI1_NPCS0 PD28 A SPI1 SPI1_NPCS1 PA26 D SPI1 SPI1_NPCS1 PC5 D SPI1 SPI1_NPCS1 PD29 A SPI1 SPI1_NPCS2 PA27 D SPI1 SPI1_NPCS2 PC6 D SPI1 SPI1_NPCS2 PD30 A SPI1 SPI1_NPCS3 PA28 D SPI1 SPI1_NPCS3 PC7 D SPI1 SPI1_SPCK PA22 D SPI1 SPI1_SPCK PC1 D SPI1 SPI1_SPCK PD25 A Power Management The SPI can be clocked through the Power Management Controller (PMC), thus the programmer must first configure the PMC to enable the SPI clock. 49.6.3 Interrupt The SPI interface has an interrupt line connected to the interrupt controller. Handling the SPI interrupt requires programming the interrupt controller before configuring the SPI. Table 49-3: Peripheral IDs Instance ID SPI0 33 SPI1 34 49.6.4 Direct Memory Access Controller (DMAC) The SPI interface can be used in conjunction with the DMAC in order to reduce processor overhead. For a full description of the DMAC, refer to Section 38. “DMA Controller (XDMAC)”.  2017 Microchip Technology Inc. DS60001476B-page 1675 SAMA5D2 SERIES 49.7 Functional Description 49.7.1 Modes of Operation The SPI operates in Master mode or in Slave mode. • The SPI operates in Master mode by setting the MSTR bit in the SPI Mode Register (SPI_MR): - Pins NPCS0 to NPCS3 are all configured as outputs - The SPCK pin is driven - The MISO line is wired on the receiver input - The MOSI line is driven as an output by the transmitter. • The SPI operates in Slave mode if the MSTR bit in SPI_MR is written to ‘0’: - The MISO line is driven by the transmitter output - The MOSI line is wired on the receiver input - The SPCK pin is driven by the transmitter to synchronize the receiver. - The NPCS0 pin becomes an input, and is used as a slave select signal (NSS) - The NPCS1 to NPCS3 pins are not driven and can be used for other purposes. The data transfers are identically programmable for both modes of operation. The baud rate generator is activated only in Master mode. 49.7.2 Data Transfer Four combinations of polarity and phase are available for data transfers. The clock polarity is programmed with the CPOL bit in the SPI Chip Select registers (SPI_CSRx). The clock phase is programmed with the NCPHA bit. These two parameters determine the edges of the clock signal on 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. Consequently, a master/slave pair must use the same parameter pair values to communicate. If multiple slaves are connected and require different configurations, the master must reconfigure itself each time it needs to communicate with a different slave. Table 49-4 shows the four modes and corresponding parameter settings. Table 49-4: SPI Bus Protocol Modes SPI Mode CPOL NCPHA Shift SPCK Edge Capture SPCK Edge SPCK Inactive Level 0 0 1 Falling Rising Low 1 0 0 Rising Falling Low 2 1 1 Rising Falling High 3 1 0 Falling Rising High Figure 49-3 and Figure 49-4 show examples of data transfers. DS60001476B-page 1676  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 49-3: SPI Transfer Format (NCPHA = 1, 8 bits per transfer) 1 SPCK cycle (for reference) 2 3 4 6 5 7 8 SPCK (CPOL = 0) SPCK (CPOL = 1) MOSI (from master) MSB MISO (from slave) MSB 6 5 4 3 2 1 LSB 6 5 4 3 2 1 LSB * NSS (to slave) * Not defined. Figure 49-4: SPI Transfer Format (NCPHA = 0, 8 bits per transfer) 1 SPCK cycle (for reference) 2 3 4 5 7 6 8 SPCK (CPOL = 0) SPCK (CPOL = 1) MOSI (from master) MISO (from slave) * MSB 6 5 4 3 2 1 MSB 6 5 4 3 2 1 LSB LSB NSS (to slave) * Not defined. 49.7.3 Master Mode Operations When configured in Master mode, the SPI operates on the clock generated by the internal programmable baud rate generator. It fully controls the data transfers to and from the slave(s) connected to the SPI bus. The SPI drives the chip select line to the slave and the serial clock signal (SPCK).  2017 Microchip Technology Inc. DS60001476B-page 1677 SAMA5D2 SERIES The SPI features two holding registers, the Transmit Data Register (SPI_TDR) and the Receive Data Register (SPI_RDR), and a single shift register. The holding registers maintain the data flow at a constant rate. After enabling the SPI, a data transfer starts when the processor writes to SPI_TDR. The written data is immediately transferred into the internal shift register and the transfer on the SPI bus starts. While the data in the shift register is shifted on the MOSI line, the MISO line is sampled and shifted into the shift register. Data cannot be loaded in SPI_RDR without transmitting data. If there is no data to transmit, dummy data can be used (SPI_TDR filled with ones). If SPI_MR.WDRBT is set, transmission can occur only if SPI_RDR has been read. If Receiving mode is not required, for example when communicating with a slave receiver only (such as an LCD), the receive status flags in the SPI Status register (SPI_SR) can be discarded. Before writing SPI_TDR, SPI_MR.PCS must be set in order to select a slave. If new data is written in SPI_TDR during the transfer, it is kept in SPI_TDR until the current transfer is completed. Then, the received data is transferred from the shift register to SPI_RDR, the data in SPI_TDR is loaded in the shift register and a new transfer starts. As soon as SPI_TDR is written, the Transmit Data Register Empty (TDRE) flag in SPI_SR is cleared. When the data written in SPI_TDR is loaded into the shift register, TDRE in SPI_SR is set. The TDRE flag is used to trigger the Transmit DMA channel. See Figure 49-5. The end of transfer is indicated by the TXEMPTY flag in SPI_SR. If a transfer delay (DLYBCT) is greater than 0 for the last transfer, TXEMPTY is set after the completion of this delay. The peripheral clock can be switched off at this time. Note: When the SPI is enabled, the TDRE and TXEMPTY flags are set. Figure 49-5: TDRE and TXEMPTY Flag Behavior Write SPI_CR.SPIEN =1 TDRE Write SPI_TDR Write SPI_TDR automatic set TDR loaded in shifter Write SPI_TDR automatic set TDR loaded in shifter automatic set TDR loaded in shifter TXEMPTY Transfer Transfer DLYBCT Transfer DLYBCT DLYBCT The transfer of received data from the internal shift register to SPI_RDR is indicated by the Receive Data Register Full (RDRF) bit in SPI_SR. When the received data is read, SPI_SR.RDRF is cleared. If SPI_RDR has not been read before new data is received, the Overrun Error (OVRES) flag in SPI_SR is set. As long as this flag is set, data is loaded in SPI_RDR. The user has to read SPI_SR to clear OVRES. Figure 49-6 shows a block diagram of the SPI when operating in Master mode. Figure 49-7 shows a flow chart describing how transfers are handled. DS60001476B-page 1678  2017 Microchip Technology Inc. SAMA5D2 SERIES 49.7.3.1 Master Mode Block Diagram Figure 49-6: Master Mode Block Diagram SPI_CSRx SCBR Baud Rate Generator Peripheral clock SPCK SPI Clock SPI_CSRx BITS NCPHA CPOL LSB MISO SPI_RDR RDRF OVRES RD MSB Shift Register MOSI SPI_TDR TDRE TD SPI_CSRx SPI_RDR CSAAT PCS PS NPCSx PCSDEC SPI_MR PCS 0 Current Peripheral SPI_TDR PCS NPCS0 1 MSTR MODF NPCS0 MODFDIS  2017 Microchip Technology Inc. DS60001476B-page 1679 SAMA5D2 SERIES 49.7.3.2 Master Mode Flow Diagram Figure 49-7: Master Mode Flow Diagram SPI Enable TDRE/TXEMPTY are set TDRE ? (SW check) 0 1 Write SPI_TDR ? - NPCS defines the current chip select - CSAAT, DLYBS, DLYBCT refer to the fields of the Chip Select Register corresponding to the current chip select - ‘x 64: Values greater than 64 are interpreted as 64. The Receive FIFO 0 elements are indexed from 0 to F0S-1. F0WM: Receive FIFO 0 Watermark 0: Watermark interrupt disabled. 1-64: Level for Receive FIFO 0 watermark interrupt (MCAN_IR.RF0W). >64: Watermark interrupt disabled. F0OM: FIFO 0 Operation Mode FIFO 0 can be operated in Blocking or in Overwrite mode (see Section 53.5.4.2). 0: FIFO 0 Blocking mode. 1: FIFO 0 Overwrite mode. DS60001476B-page 2010  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.28 MCAN Receive FIFO 0 Status Name: MCAN_RXF0S Address: 0xF80540A4 (0), 0xFC0500A4 (1) Access: Read-only 31 – 23 – 15 – 7 – 30 – 22 – 14 – 6 29 – 21 28 – 20 27 – 19 13 12 11 26 – 18 25 RF0L 17 24 F0F 16 10 9 8 2 1 0 F0PI F0GI 5 4 3 F0FL F0FL: Receive FIFO 0 Fill Level Number of elements stored in Receive FIFO 0, range 0 to 64. F0GI: Receive FIFO 0 Get Index Receive FIFO 0 read index pointer, range 0 to 63. F0PI: Receive FIFO 0 Put Index Receive FIFO 0 write index pointer, range 0 to 63. F0F: Receive FIFO 0 Full 0: Receive FIFO 0 not full. 1: Receive FIFO 0 full. RF0L: Receive FIFO 0 Message Lost This bit is a copy of interrupt flag MCAN_IR.RF0L. When MCAN_IR.RF0L is reset, this bit is also reset. 0: No Receive FIFO 0 message lost 1: Receive FIFO 0 message lost, also set after write attempt to Receive FIFO 0 of size zero Note: Overwriting the oldest message when MCAN_RXF0C.F0OM = ‘1’ will not set this flag.  2017 Microchip Technology Inc. DS60001476B-page 2011 SAMA5D2 SERIES 53.6.29 MCAN Receive FIFO 0 Acknowledge Name: MCAN_RXF0A Address: 0xF80540A8 (0), 0xFC0500A8 (1) Access: Read/Write 31 – 23 – 15 – 7 – 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 F0AI F0AI: Receive FIFO 0 Acknowledge Index After the processor has read a message or a sequence of messages from Receive FIFO 0 it has to write the buffer index of the last element read from Receive FIFO 0 to F0AI. This will set the Receive FIFO 0 Get Index MCAN_RXF0S.F0GI to F0AI + 1 and update the FIFO 0 Fill Level MCAN_RXF0S.F0FL. DS60001476B-page 2012  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.30 MCAN Receive Buffer Configuration Name: MCAN_RXBC Address: 0xF80540AC (0), 0xFC0500AC (1) Access: Read/Write 31 – 23 – 15 30 – 22 – 14 29 – 21 – 13 28 – 20 – 12 7 6 5 4 27 – 19 – 11 26 – 18 – 10 25 – 17 – 9 24 – 16 – 8 3 2 1 – 0 – RBSA RBSA RBSA: Receive Buffer Start Address Configures the start address of the Receive Buffers section in the Message RAM (32-bit word address, see Figure 53-12). Also used to reference debug messages A,B,C. Write RBSA with the bits [15:2] of the 32-bit address.  2017 Microchip Technology Inc. DS60001476B-page 2013 SAMA5D2 SERIES 53.6.31 MCAN Receive FIFO 1 Configuration Name: MCAN_RXF1C Address: 0xF80540B0 (0), 0xFC0500B0 (1) Access: Read/Write 31 F1OM 23 – 15 30 29 28 22 21 20 14 13 12 27 F1WM 19 F1S 11 26 25 24 18 17 16 10 9 8 3 2 1 – 0 – F1SA 7 6 5 4 F1SA This register can only be written if the bits CCE and INIT are set in MCAN CC Control Register. F1SA: Receive FIFO 1 Start Address Start address of Receive FIFO 1 in Message RAM (32-bit word address, see Figure 53-12). Write F1SA with the bits [15:2] of the 32-bit address. F1S: Receive FIFO 1 Size 0: No Receive FIFO 1 1-64: Number of elements in Receive FIFO 1. >64: Values greater than 64 are interpreted as 64. The elements in Receive FIFO 1 are indexed from 0 to F1S - 1. F1WM: Receive FIFO 1 Watermark 0: Watermark interrupt disabled 1-64: Level for Receive FIFO 1 watermark interrupt (MCAN_IR.RF1W). >64: Watermark interrupt disabled. F1OM: FIFO 1 Operation Mode FIFO 1 can be operated in Blocking or in Overwrite mode (see Section 53.5.4.2). 0: FIFO 1 Blocking mode. 1: FIFO 1 Overwrite mode. DS60001476B-page 2014  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.32 MCAN Receive FIFO 1 Status Name: MCAN_RXF1S Address: 0xF80540B4 (0), 0xFC0500B4 (1) Access: Read-only 31 30 DMS 23 – 15 – 7 – 22 – 14 – 6 29 – 21 28 – 20 27 – 19 13 12 11 26 – 18 25 RF1L 17 24 F1F 16 10 9 8 2 1 0 F1PI F1GI 5 4 3 F1FL F1FL: Receive FIFO 1 Fill Level Number of elements stored in Receive FIFO 1, range 0 to 64. F1GI: Receive FIFO 1 Get Index Receive FIFO 1 read index pointer, range 0 to 63. F1PI: Receive FIFO 1 Put Index Receive FIFO 1 write index pointer, range 0 to 63. F1F: Receive FIFO 1 Full 0: Receive FIFO 1 not full. 1: Receive FIFO 1 full. RF1L: Receive FIFO 1 Message Lost This bit is a copy of interrupt flag IR.RF1L. When IR.RF1L is reset, this bit is also reset. 0: No Receive FIFO 1 message lost. 1: Receive FIFO 1 message lost, also set after write attempt to Receive FIFO 1 of size zero. Note: Overwriting the oldest message when MCAN_RXF1C.F1OM = ‘1’ will not set this flag. DMS: Debug Message Status Value Name Description 0 IDLE Idle state, wait for reception of debug messages, DMA request is cleared. 1 MSG_A Debug message A received. 2 MSG_AB Debug messages A, B received. 3 MSG_ABC Debug messages A, B, C received, DMA request is set.  2017 Microchip Technology Inc. DS60001476B-page 2015 SAMA5D2 SERIES 53.6.33 MCAN Receive FIFO 1 Acknowledge Name: MCAN_RXF1A Address: 0xF80540B8 (0), 0xFC0500B8 (1) Access: Read/Write 31 – 23 – 15 – 7 – 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 F1AI F1AI: Receive FIFO 1 Acknowledge Index After the processor has read a message or a sequence of messages from Receive FIFO 1 it has to write the buffer index of the last element read from Receive FIFO 1 to F1AI. This will set the Receive FIFO 1 Get Index MCAN_RXF1S.F1GI to F1AI + 1 and update the FIFO 1 Fill Level MCAN_RXF1S.F1FL. DS60001476B-page 2016  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.34 MCAN Receive Buffer / FIFO Element Size Configuration Name: MCAN_RXESC Address: 0xF80540BC (0), 0xFC0500BC (1) Access: Read/Write 31 – 23 – 15 – 7 – 30 – 22 – 14 – 6 29 – 21 – 13 – 5 F1DS 28 – 20 – 12 – 4 27 – 19 – 11 – 3 – 26 – 18 – 10 2 25 – 17 – 9 RBDS 1 F0DS 24 – 16 – 8 0 This register can only be written if the bits CCE and INIT are set in MCAN CC Control Register. Configures the number of data bytes belonging to a Receive Buffer / Receive FIFO element. Data field sizes >8 bytes are intended for CAN FD operation only. F0DS: Receive FIFO 0 Data Field Size Value Name Description 0 8_BYTE 8-byte data field 1 12_BYTE 12-byte data field 2 16_BYTE 16-byte data field 3 20_BYTE 20-byte data field 4 24_BYTE 24-byte data field 5 32_BYTE 32-byte data field 6 48_BYTE 48-byte data field 7 64_BYTE 64-byte data field F1DS: Receive FIFO 1 Data Field Size Value Name Description 0 8_BYTE 8-byte data field 1 12_BYTE 12-byte data field 2 16_BYTE 16-byte data field 3 20_BYTE 20-byte data field 4 24_BYTE 24-byte data field 5 32_BYTE 32-byte data field 6 48_BYTE 48-byte data field 7 64_BYTE 64-byte data field  2017 Microchip Technology Inc. DS60001476B-page 2017 SAMA5D2 SERIES RBDS: Receive Buffer Data Field Size Value Name Description 0 8_BYTE 8-byte data field 1 12_BYTE 12-byte data field 2 16_BYTE 16-byte data field 3 20_BYTE 20-byte data field 4 24_BYTE 24-byte data field 5 32_BYTE 32-byte data field 6 48_BYTE 48-byte data field 7 64_BYTE 64-byte data field Note: In case the data field size of an accepted CAN frame exceeds the data field size configured for the matching Receive Buffer or Receive FIFO, only the number of bytes as configured by MCAN_RXESC are stored to the Receive Buffer resp. Receive FIFO element. The rest of the frame’s data field is ignored. DS60001476B-page 2018  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.35 MCAN Tx Buffer Configuration Name: MCAN_TXBC Address: 0xF80540C0 (0), 0xFC0500C0 (1) Access: Read/Write 31 – 23 – 15 30 TFQM 22 – 14 29 28 27 26 25 24 18 17 16 TFQS 21 20 19 13 12 11 10 9 8 3 2 1 – 0 – NDTB TBSA 7 6 5 4 TBSA This register can only be written if the bits CCE and INIT are set in MCAN CC Control Register. TBSA: Tx Buffers Start Address Start address of Tx Buffers section in Message RAM (32-bit word address, see Figure 53-12). Write TBSA with the bits [15:2] of the 32-bit address. NDTB: Number of Dedicated Transmit Buffers 0: No dedicated Tx Buffers. 1-32: Number of dedicated Tx Buffers. >32: Values greater than 32 are interpreted as 32. TFQS: Transmit FIFO/Queue Size 0: No Tx FIFO/Queue. 1-32: Number of Tx Buffers used for Tx FIFO/Queue. >32: Values greater than 32 are interpreted as 32. TFQM: Tx FIFO/Queue Mode 0: Tx FIFO operation. 1: Tx Queue operation. Note: The sum of TFQS and NDTB may be not greater than 32. There is no check for erroneous configurations. The Tx Buffers section in the Message RAM starts with the dedicated Tx Buffers.  2017 Microchip Technology Inc. DS60001476B-page 2019 SAMA5D2 SERIES 53.6.36 MCAN Tx FIFO/Queue Status Name: MCAN_TXFQS Address: 0xF80540C4 (0), 0xFC0500C4 (1) Access: Read-only 31 – 23 – 15 – 7 – 30 – 22 – 14 – 6 – 29 – 21 TFQF 13 – 5 28 – 20 27 – 19 12 11 4 3 26 – 18 TFQPI 10 TFGI 2 25 – 17 24 – 16 9 8 1 0 TFFL The Tx FIFO/Queue status is related to the pending Tx requests listed in register MCAN_TXBRP. Therefore the effect of Add/Cancellation requests may be delayed due to a running Tx scan (MCAN_TXBRP not yet updated). TFFL: Tx FIFO Free Level Number of consecutive free Tx FIFO elements starting from TFGI, range 0 to 32. Read as zero when Tx Queue operation is configured (MCAN_TXBC.TFQM = ‘1’). TFGI: Tx FIFO Get Index Tx FIFO read index pointer, range 0 to 31. Read as zero when Tx Queue operation is configured (MCAN_TXBC.TFQM = ‘1’). TFQPI: Tx FIFO/Queue Put Index Tx FIFO/Queue write index pointer, range 0 to 31. TFQF: Tx FIFO/Queue Full 0: Tx FIFO/Queue not full. 1: Tx FIFO/Queue full. Note: In case of mixed configurations where dedicated Tx Buffers are combined with a Tx FIFO or a Tx Queue, the Put and Get Indices indicate the number of the Tx Buffer starting with the first dedicated Tx Buffers. Example: For a configuration of 12 dedicated Tx Buffers and a Tx FIFO of 20 Buffers a Put Index of 15 points to the fourth buffer of the Tx FIFO. DS60001476B-page 2020  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.37 MCAN Tx Buffer Element Size Configuration Name: MCAN_TXESC Address: 0xF80540C8 (0), 0xFC0500C8 (1) Access: Read/Write 31 – 23 – 15 – 7 – 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 – 28 – 20 – 12 – 4 – 27 – 19 – 11 – 3 – 26 – 18 – 10 – 2 25 – 17 – 9 – 1 TBDS 24 – 16 – 8 – 0 This register can only be written if the bits CCE and INIT are set in MCAN CC Control Register. Configures the number of data bytes belonging to a Tx Buffer element. Data field sizes > 8 bytes are intended for CAN FD operation only. TBDS: Tx Buffer Data Field Size Value Name Description 0 8_BYTE 8-byte data field 1 12_BYTE 12-byte data field 2 16_BYTE 16-byte data field 3 20_BYTE 20-byte data field 4 24_BYTE 24-byte data field 5 32_BYTE 32-byte data field 6 48_BYTE 48- byte data field 7 64_BYTE 64-byte data field Note: In case the data length code DLC of a Tx Buffer element is configured to a value higher than the Tx Buffer data field size MCAN_TXESC.TBDS, the bytes not defined by the Tx Buffer are transmitted as “0xCC” (padding bytes).  2017 Microchip Technology Inc. DS60001476B-page 2021 SAMA5D2 SERIES 53.6.38 MCAN Transmit Buffer Request Pending Name: MCAN_TXBRP Address: 0xF80540CC (0), 0xFC0500CC (1) Access: Read-only 31 TRP31 23 TRP23 15 TRP15 7 TRP7 30 TRP30 22 TRP22 14 TRP14 6 TRP6 29 TRP29 21 TRP21 13 TRP13 5 TRP5 28 TRP28 20 TRP20 12 TRP12 4 TRP4 27 TRP27 19 TRP19 11 TRP11 3 TRP3 26 TRP26 18 TRP18 10 TRP10 2 TRP2 25 TRP25 17 TRP17 9 TRP9 1 TRP1 24 TRP24 16 TRP16 8 TRP8 0 TRP0 TRPx: Transmission Request Pending for Buffer x Each Tx Buffer has its own Transmission Request Pending bit. The bits are set via register MCAN_TXBAR. The bits are reset after a requested transmission has completed or has been cancelled via register MCAN_TXBCR. TXBRP bits are set only for those Tx Buffers configured via MCAN_TXBC. After a MCAN_TXBRP bit has been set, a Tx scan (see Section 53.5.5) is started to check for the pending Tx request with the highest priority (Tx Buffer with lowest Message ID). A cancellation request resets the corresponding transmission request pending bit of register MCAN_TXBRP. In case a transmission has already been started when a cancellation is requested, this is done at the end of the transmission, regardless whether the transmission was successful or not. The cancellation request bits are reset directly after the corresponding TXBRP bit has been reset. After a cancellation has been requested, a finished cancellation is signalled via MCAN_TXBCF. • after successful transmission together with the corresponding MCAN_TXBTO bit. • when the transmission has not yet been started at the point of cancellation. • when the transmission has been aborted due to lost arbitration. • when an error occurred during frame transmission. In DAR mode, all transmissions are automatically cancelled if they are not successful. The corresponding MCAN_TXBCF bit is set for all unsuccessful transmissions. 0: No transmission request pending 1: Transmission request pending Note: MCAN_TXBRP bits which are set while a Tx scan is in progress are not considered during this particular Tx scan. In case a cancellation is requested for such a Tx Buffer, this Add Request is cancelled immediately, the corresponding MCAN_TXBRP bit is reset. DS60001476B-page 2022  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.39 MCAN Transmit Buffer Add Request Name: MCAN_TXBAR Address: 0xF80540D0 (0), 0xFC0500D0 (1) Access: 31 AR31 23 AR23 15 AR15 7 AR7 Read/Write 30 AR30 22 AR22 14 AR14 6 AR6 29 AR29 21 AR21 13 AR13 5 AR5 28 AR28 20 AR20 12 AR12 4 AR4 27 AR27 19 AR19 11 AR11 3 AR3 26 AR26 18 AR18 10 AR10 2 AR2 25 AR25 17 AR17 9 AR9 1 AR1 24 AR24 16 AR16 8 AR8 0 AR0 ARx: Add Request for Transmit Buffer x Each Transmit Buffer has its own Add Request bit. Writing a ‘1’ will set the corresponding Add Request bit; writing a ‘0’ has no impact. This enables the processor to set transmission requests for multiple Transmit Buffers with one write to MCAN_TXBAR. MCAN_TXBAR bits are set only for those Transmit Buffers configured via TXBC. When no Transmit scan is running, the bits are reset immediately, else the bits remain set until the Transmit scan process has completed. 0: No transmission request added. 1: Transmission requested added. Note: If an add request is applied for a Transmit Buffer with pending transmission request (corresponding MCAN_TXBRP bit already set), this Add Request is ignored.  2017 Microchip Technology Inc. DS60001476B-page 2023 SAMA5D2 SERIES 53.6.40 MCAN Transmit Buffer Cancellation Request Name: MCAN_TXBCR Address: 0xF80540D4 (0), 0xFC0500D4 (1) Access: 31 CR31 23 CR23 15 CR15 7 CR7 Read/Write 30 CR30 22 CR22 14 CR14 6 CR6 29 CR29 21 CR21 13 CR13 5 CR5 28 CR28 20 CR20 12 CR12 4 CR4 27 CR27 19 CR19 11 CR11 3 CR3 26 CR26 18 CR18 10 CR10 2 CR2 25 CR25 17 CR17 9 CR9 1 CR1 24 CR24 16 CR16 8 CR8 0 CR0 CRx: Cancellation Request for Transmit Buffer x Each Transmit Buffer has its own Cancellation Request bit. Writing a ‘1’ will set the corresponding Cancellation Request bit; writing a ‘0’ has no impact. This enables the processor to set cancellation requests for multiple Transmit Buffers with one write to MCAN_TXBCR. MCAN_TXBCR bits are set only for those Transmit Buffers configured via TXBC. The bits remain set until the corresponding bit of MCAN_TXBRP is reset. 0: No cancellation pending. 1: Cancellation pending. DS60001476B-page 2024  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.41 MCAN Transmit Buffer Transmission Occurred Name: MCAN_TXBTO Address: 0xF80540D8 (0), 0xFC0500D8 (1) Access: 31 TO31 23 TO23 15 TO15 7 TO7 Read-only 30 TO30 22 TO22 14 TO14 6 TO6 29 TO29 21 TO21 13 TO13 5 TO5 28 TO28 20 TO20 12 TO12 4 TO4 27 TO27 19 TO19 11 TO11 3 TO3 26 TO26 18 TO18 10 TO10 2 TO2 25 TO25 17 TO17 9 TO9 1 TO1 24 TO24 16 TO16 8 TO8 0 TO0 TOx: Transmission Occurred for Buffer x Each Transmit Buffer has its own Transmission Occurred bit. The bits are set when the corresponding MCAN_TXBRP bit is cleared after a successful transmission. The bits are reset when a new transmission is requested by writing a ‘1’ to the corresponding bit of register MCAN_TXBAR. 0: No transmission occurred. 1: Transmission occurred.  2017 Microchip Technology Inc. DS60001476B-page 2025 SAMA5D2 SERIES 53.6.42 MCAN Transmit Buffer Cancellation Finished Name: MCAN_TXBCF Address: 0xF80540DC (0), 0xFC0500DC (1) Access: 31 CF31 23 CF23 15 CF15 7 CF7 Read-only 30 CF30 22 CF22 14 CF14 6 CF6 29 CF29 21 CF21 13 CF13 5 CF5 28 CF28 20 CF20 12 CF12 4 CF4 27 CF27 19 CF19 11 CF11 3 CF3 26 CF26 18 CF18 10 CF10 2 CF2 25 CF25 17 CF17 9 CF9 1 CF1 24 CF24 16 CF16 8 CF8 0 CF0 CFx: Cancellation Finished for Transmit Buffer x Each Transmit Buffer has its own Cancellation Finished bit. The bits are set when the corresponding MCAN_TXBRP bit is cleared after a cancellation was requested via MCAN_TXBCR. In case the corresponding MCAN_TXBRP bit was not set at the point of cancellation, CF is set immediately. The bits are reset when a new transmission is requested by writing a ‘1’ to the corresponding bit of register MCAN_TXBAR. 0: No transmit buffer cancellation. 1: Transmit buffer cancellation finished. DS60001476B-page 2026  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.43 MCAN Transmit Buffer Transmission Interrupt Enable Name: MCAN_TXBTIE Address: 0xF80540E0 (0), 0xFC0500E0 (1) Access: 31 TIE31 23 TIE23 15 TIE15 7 TIE7 Read/Write 30 TIE30 22 TIE22 14 TIE14 6 TIE6 29 TIE29 21 TIE21 13 TIE13 5 TIE5 28 TIE28 20 TIE20 12 TIE12 4 TIE4 27 TIE27 19 TIE19 11 TIE11 3 TIE3 26 TIE26 18 TIE18 10 TIE10 2 TIE2 25 TIE25 17 TIE17 9 TIE9 1 TIE1 24 TIE24 16 TIE16 8 TIE8 0 TIE0 TIEx: Transmission Interrupt Enable for Buffer x Each Transmit Buffer has its own Transmission Interrupt Enable bit. 0: Transmission interrupt disabled 1: Transmission interrupt enable  2017 Microchip Technology Inc. DS60001476B-page 2027 SAMA5D2 SERIES 53.6.44 MCAN Transmit Buffer Cancellation Finished Interrupt Enable Name: MCAN_TXBCIE Address: 0xF80540E4 (0), 0xFC0500E4 (1) Access: Read/Write 31 CFIE31 23 CFIE23 15 CFIE15 7 CFIE7 30 CFIE30 22 CFIE22 14 CFIE14 6 CFIE6 29 CFIE29 21 CFIE21 13 CFIE13 5 CFIE5 28 CFIE28 20 CFIE20 12 CFIE12 4 CFIE4 27 CFIE27 19 CFIE19 11 CFIE11 3 CFIE3 26 CFIE26 18 CFIE18 10 CFIE10 2 CFIE2 25 CFIE25 17 CFIE17 9 CFIE9 1 CFIE1 24 CFIE24 16 CFIE16 8 CFIE8 0 CFIE0 CFIEx: Cancellation Finished Interrupt Enable for Transmit Buffer x Each Transmit Buffer has its own Cancellation Finished Interrupt Enable bit. 0: Cancellation finished interrupt disabled. 1: Cancellation finished interrupt enabled. DS60001476B-page 2028  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.45 MCAN Transmit Event FIFO Configuration Name: MCAN_TXEFC Address: 0xF80540F0 (0), 0xFC0500F0 (1) Access: Read/Write 31 – 23 – 15 30 – 22 – 14 29 28 27 26 25 24 18 17 16 EFWM 21 20 19 13 12 11 10 9 8 3 2 1 – 0 – EFS EFSA 7 6 5 4 EFSA This register can only be written if the bits CCE and INIT are set in MCAN CC Control Register. EFSA: Event FIFO Start Address Start address of Tx Event FIFO in Message RAM (32-bit word address, see Figure 53-12). Write EFSA with the bits [15:2] of the 32-bit address. EFS: Event FIFO Size 0: Tx Event FIFO disabled. 1-32: Number of Tx Event FIFO elements. >32: Values greater than 32 are interpreted as 32. The Tx Event FIFO elements are indexed from 0 to EFS - 1. EFWM: Event FIFO Watermark 0: Watermark interrupt disabled. 1-32: Level for Tx Event FIFO watermark interrupt (MCAN_IR.TEFW). >32: Watermark interrupt disabled.  2017 Microchip Technology Inc. DS60001476B-page 2029 SAMA5D2 SERIES 53.6.46 MCAN Tx Event FIFO Status Name: MCAN_TXEFS Address: 0xF80540F4 (0), 0xFC0500F4 (1) Access: Read-only 31 – 23 – 15 – 7 – 30 – 22 – 14 – 6 – 29 – 21 – 13 – 5 28 – 20 27 – 19 12 11 4 3 26 – 18 EFPI 10 EFGI 2 25 TEFL 17 24 EFF 16 9 8 1 0 EFFL EFFL: Event FIFO Fill Level Number of elements stored in Tx Event FIFO, range 0 to 32. EFGI: Event FIFO Get Index Tx Event FIFO read index pointer, range 0 to 31. EFPI: Event FIFO Put Index Tx Event FIFO write index pointer, range 0 to 31. EFF: Event FIFO Full 0: Tx Event FIFO not full 1: Tx Event FIFO full TEFL: Tx Event FIFO Element Lost This bit is a copy of interrupt flag MCAN_IR.TEFL. When MCAN_IR.TEFL is reset, this bit is also reset. 0: No Tx Event FIFO element lost 1: Tx Event FIFO element lost, also set after write attempt to Tx Event FIFO of size zero. DS60001476B-page 2030  2017 Microchip Technology Inc. SAMA5D2 SERIES 53.6.47 MCAN Tx Event FIFO Acknowledge Name: MCAN_TXEFA Address: 0xF80540F8 (0), 0xFC0500F8 (1) Access: 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 EFAI 25 – 17 – 9 – 1 24 – 16 – 8 – 0 EFAI: Event FIFO Acknowledge Index After the processor has read an element or a sequence of elements from the Tx Event FIFO, it has to write the index of the last element read from Tx Event FIFO to EFAI. This will set the Tx Event FIFO Get Index MCAN_TXEFS.EFGI to EFAI + 1 and update the FIFO 0 Fill Level MCAN_TXEFS.EFFL.  2017 Microchip Technology Inc. DS60001476B-page 2031 SAMA5D2 SERIES 54. Timer Counter (TC) 54.1 Description A Timer Counter (TC) module includes three identical TC channels. The number of implemented TC modules is device-specific. Each TC 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 multipurpose 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 TC embeds a quadrature decoder (QDEC) connected in front of the timers and driven by TIOA0, TIOB0 and TIOB1 inputs. When enabled, the QDEC performs the input lines filtering, decoding of quadrature signals and connects to the timers/counters in order to read the position and speed of the motor through the user interface. The TC block has two global registers which act upon all TC channels: • Block Control register (TC_BCR)—allows channels to be started simultaneously with the same instruction • Block Mode register (TC_BMR)—defines the external clock inputs for each channel, allowing them to be chained 54.2 Embedded Characteristics • Total of 6 Channels • 32-bit Channel Size • Wide Range of Functions Including: - Frequency measurement - Event counting - Interval measurement - Pulse generation - Delay timing - Pulse Width Modulation - Up/down capabilities - Quadrature decoder - 2-bit Gray up/down count for stepper motor • Each Channel is User-Configurable and Contains: - Three external clock inputs - Five Internal clock inputs - Two multipurpose input/output signals acting as trigger event - Trigger/capture events can be directly synchronized by PWM signals • Internal Interrupt Signal • Read of the Capture Registers by the DMAC • Compare Event Fault Generation for PWM • Register Write Protection 54.3 Block Diagram Table 54-1: Timer Counter Clock Assignment Name Definition TIMER_CLOCK1 GCLK [35], GCLK [36] TIMER_CLOCK2 System bus clock divided by 8 TIMER_CLOCK3 System bus clock divided by 32 TIMER_CLOCK4 System bus clock divided by 128 TIMER_CLOCK5 slow_clock Note: The GCLK frequency must be at least three times lower than peripheral clock frequency. DS60001476B-page 2032  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-1: Timer Counter Block Diagram Timer Counter Parallel I/O Controller TIMER_CLOCK1 TCLK0 TIMER_CLOCK2 TIOA1 TIOA2 TIMER_CLOCK3 TCLK1 TIMER_CLOCK4 XC0 Timer Counter Channel 0 XC1 TIOA TIOA0 TIOB0 TIOA0 TIOB TCLK2 TIOB0 XC2 TIMER_CLOCK5 TC0XC0S SYNC TCLK0 TCLK1 TCLK2 INT0 TCLK0 TCLK1 XC0 TIOA0 Timer Counter Channel 1 XC1 TIOA TIOA1 TIOB1 TIOA1 TIOB TIOA2 TCLK2 TIOB1 XC2 SYNC TC1XC1S TCLK0 XC0 TCLK1 XC1 TCLK2 XC2 Timer Counter Channel 2 INT1 TIOA TIOA2 TIOB2 TIOA2 TIOB TIOB2 TIOA0 TIOA1 SYNC TC2XC2S INT2 FAULT PWM Note: Interrupt Controller The QDEC connections are detailed in Figure 54-17. Table 54-2: Channel Signal Description Signal Name XC0, XC1, XC2 Description External Clock Inputs TIOAx Capture Mode: Timer Counter Input Waveform Mode: Timer Counter Output TIOBx Capture Mode: Timer Counter Input Waveform Mode: Timer Counter Input/Output INT SYNC Interrupt Signal Output (internal signal) Synchronization Input Signal (from configuration register)  2017 Microchip Technology Inc. DS60001476B-page 2033 SAMA5D2 SERIES 54.4 Pin List Table 54-3: Pin List Pin Name Description Type TCLK0–TCLK2 External Clock Input Input TIOA0–TIOA2 I/O Line A I/O TIOB0–TIOB2 I/O Line B I/O 54.5 Product Dependencies 54.5.1 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. Table 54-4: I/O Lines Instance Signal I/O Line Peripheral TC0 TCLK0 PA21 D TC0 TCLK1 PA29 A TC0 TCLK1 PC5 C TC0 TCLK1 PD13 A TC0 TCLK2 PB5 A TC0 TCLK2 PB24 D TC0 TCLK2 PD22 A TC0 TIOA0 PA19 D TC0 TIOA1 PA27 A TC0 TIOA1 PC3 C TC0 TIOA1 PD11 A TC0 TIOA2 PB6 A TC0 TIOA2 PB22 D TC0 TIOA2 PD20 A TC0 TIOB0 PA20 D TC0 TIOB1 PA28 A TC0 TIOB1 PC4 C TC0 TIOB1 PD12 A TC0 TIOB2 PB7 A TC0 TIOB2 PB23 D TC0 TIOB2 PD21 A TC1 TCLK3 PB8 A TC1 TCLK3 PB21 D TC1 TCLK3 PD31 D TC1 TCLK4 PA11 D DS60001476B-page 2034  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 54-4: 54.5.2 I/O Lines (Continued) TC1 TCLK4 PC11 D TC1 TCLK5 PA8 D TC1 TCLK5 PB30 D TC1 TIOA3 PB9 A TC1 TIOA3 PB19 D TC1 TIOA3 PD29 D TC1 TIOA4 PA9 D TC1 TIOA4 PC9 D TC1 TIOA5 PA6 D TC1 TIOA5 PB28 D TC1 TIOB3 PB10 A TC1 TIOB3 PB20 D TC1 TIOB3 PD30 D TC1 TIOB4 PA10 D TC1 TIOB4 PC10 D TC1 TIOB5 PA7 D TC1 TIOB5 PB29 D Power Management The TC is clocked through the Power Management Controller (PMC), thus the programmer must first configure the PMC to enable the Timer Counter clock. 54.5.3 Interrupt Sources The TC has an interrupt line connected to the interrupt controller. Handling the TC interrupt requires programming the interrupt controller before configuring the TC. Table 54-5: Peripheral IDs Instance ID TC0 35 TC1 36 54.5.4 Synchronization Inputs from PWM The TC has trigger/capture inputs internally connected to the PWM. Refer to Section 54.6.14 “Synchronization with PWM” and to the implementation of the Pulse Width Modulation (PWM) in this product. 54.5.5 Fault Output The TC has the FAULT output internally connected to the fault input of PWM. Refer to Section 54.6.18 “Fault Mode” and to the implementation of the Pulse Width Modulation (PWM) in this product. 54.6 54.6.1 Functional Description Description All channels of the Timer Counter are independent and identical in operation except when the QDEC is enabled. The registers for channel programming are listed in Table 54-6 “Register Mapping”.  2017 Microchip Technology Inc. DS60001476B-page 2035 SAMA5D2 SERIES 54.6.2 32-bit Counter Each 32-bit channel is organized around a 32-bit counter. The value of the counter is incremented at each positive edge of the selected clock. When the counter has reached the value 232-1 and passes to zero, an overflow occurs and the COVFS bit in the Interrupt Status register (TC_SR) is set. The current value of the counter is accessible in real time by reading the Counter Value register (TC_CV). The counter can be reset by a trigger. In this case, the counter value passes to zero on the next valid edge of the selected clock. 54.6.3 Clock Selection At block level, input clock signals of each channel can be connected either to the external inputs TCLKx, or to the internal I/O signals TIOAx for chaining(1) by programming the Block Mode register (TC_BMR). See Figure 54-2. Each channel can independently select an internal or external clock source for its counter(2): • External clock signals: XC0, XC1 or XC2 • Internal clock signals: GCLK [35], GCLK [36], System bus clock divided by 8, System bus clock divided by 32, System bus clock divided by 128, slow_clock This selection is made by the TCCLKS bits in the Channel Mode register (TC_CMRx). The selected clock can be inverted with TC_CMRx.CLKI. 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 TC_CMRx defines this signal (none, XC0, XC1, XC2). See Figure 54-3. Note 1: In Waveform mode, to chain two timers, it is mandatory to initialize some parameters: - Configure TIOx outputs to 1 or 0 by writing the required value to TC_CMRx.ASWTRG. - Bit TC_BCR.SYNC must be written to 1 to start the channels at the same time. 2: In all cases, if an external clock or asynchronous internal clock GCLK is used, the duration of each of its levels must be longer than the peripheral clock period, so the clock frequency will be at least 2.5 times lower than the peripheral clock. Figure 54-2: Clock Chaining Selection TC0XC0S Timer Counter Channel 0 TCLK0 TIOA1 TIOA0 XC0 TIOA2 XC1 = TCLK1 XC2 = TCLK2 TIOB0 SYNC TC1XC1S Timer Counter Channel 1 TCLK1 XC0 = TCLK0 TIOA0 TIOA1 XC1 TIOA2 XC2 = TCLK2 TIOB1 SYNC Timer Counter Channel 2 TC2XC2S XC0 = TCLK0 TCLK2 TIOA2 XC1 = TCLK1 TIOA0 XC2 TIOB2 TIOA1 SYNC DS60001476B-page 2036  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-3: Clock Selection TCCLKS TIMER_CLOCK1 CLKI Synchronous Edge Detection TIMER_CLOCK2 TIMER_CLOCK3 TIMER_CLOCK4 Selected Clock TIMER_CLOCK5 XC0 XC1 XC2 Peripheral Clock BURST 1 54.6.4 Clock Control The clock of each counter can be controlled in two different ways: it can be enabled/disabled and started/stopped. See Figure 54-4. • The clock can be enabled or disabled by the user with the CLKEN and the CLKDIS commands in the Channel Control register (TC_CCR). In Capture mode it can be disabled by an RB load event if TC_CMRx.LDBDIS is set to ‘1’. In Waveform mode, it can be disabled by an RC Compare event if TC_CMRx.CPCDIS is set to ‘1’. When disabled, the start or the stop actions have no effect: only a CLKEN command in the TC_CCR can reenable the clock. When the clock is enabled, TC_SR.CLKSTA is set. • 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 (TC_CMRx.LDBSTOP = 1) or an RC compare event in Waveform mode (TC_CMRx.CPCSTOP = 1). The start and the stop commands are effective only if the clock is enabled. Figure 54-4: Clock Control Selected Clock Trigger CLKSTA Q Q S CLKEN CLKDIS S R R Counter Clock  2017 Microchip Technology Inc. Stop Event Disable Event DS60001476B-page 2037 SAMA5D2 SERIES 54.6.5 Operating Modes Each channel can operate independently in two different modes: • Capture mode provides measurement on signals. • Waveform mode provides wave generation. The TC operating mode is programmed with TC_CMRx.WAVE. In Capture mode, TIOAx and TIOBx are configured as inputs. In Waveform mode, TIOAx is always configured to be an output and TIOBx is an output if it is not selected to be the external trigger. 54.6.6 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. 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. The following triggers are common to both modes: • Software Trigger: Each channel has a software trigger, available by setting TC_CCR.SWTRG. • 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 TC_BCR 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 TC_CMRx.CPCTRG is set . The channel can also be configured to have an external trigger. In Capture mode, the external trigger signal can be selected between TIOAx and TIOBx. In Waveform mode, an external event can be programmed on one of the following signals: TIOBx, XC0, XC1 or XC2. This external event can then be programmed to perform a trigger by setting TC_CMRx.ENETRG. If an external trigger is used, the duration of the pulses must be longer than the peripheral clock period in order to be detected. 54.6.7 Capture Mode Capture mode is entered by clearing TC_CMRx.WAVE. Capture mode allows the TC channel to perform measurements such as pulse timing, frequency, period, duty cycle and phase on TIOAx and TIOBx signals which are considered as inputs. Figure 54-6 shows the configuration of the TC channel when programmed in Capture mode. 54.6.8 Capture Registers A and B Registers A and B (TC_RA and TC_RB) are used as capture registers. They can be loaded with the counter value when a programmable event occurs on the signal TIOAx. TC_CMRx.LDRA defines the TIOAx selected edge for the loading of TC_RA, and TC_CMRx.LDRB defines the TIOAx selected edge for the loading of TC_RB. The subsampling ratio defined by TC_CMRx.SBSMPLR is applied to these selected edges, so that the loading of Register A and Register B occurs once every 1, 2, 4, 8 or 16 selected edges. TC_RA is loaded only if it has not been loaded since the last trigger or if TC_RB has been loaded since the last loading of TC_RA. TC_RB is loaded only if TC_RA has been loaded since the last trigger or the last loading of TC_RB. Loading TC_RA or TC_RB before the read of the last value loaded sets TC_SR.LOVRS. In this case, the old value is overwritten. When DMA is used, the Register AB (TC_RAB) address must be configured as source address of the transfer. TC_RAB provides the next unread value from TC_RA and TC_RB. It may be read by the DMA after a request has been triggered upon loading TC_RA or TC_RB. 54.6.9 Transfer with DMAC in Capture Mode The DMAC can perform access from the TC to system memory in Capture mode only. Figure 54-5 illustrates how TC_RA and TC_RB can be loaded in the system memory without processor intervention. DS60001476B-page 2038  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-5: Example of Transfer with DMAC in Capture Mode ETRGEDG = 1, LDRA = 1, LDRB = 2, ABETRG = 0 TIOB TIOA RA RB Internal Peripheral Trigger (when RA or RB loaded) Transfer to System Memory RA RB RA RB T1 T2 T3 T4 T1,T2,T3,T4 = System Bus load dependent (tmin = 8 Peripheral Clocks) ETRGEDG = 3, LDRA = 3, LDRB = 0, ABETRG = 0 TIOB TIOA RA Internal Peripheral Trigger (when RA loaded) Transfer to System Memory RA RA RA RA T1 T2 T3 T4 T1,T2,T3,T4 = System Bus load dependent (tmin = 8 Peripheral Clocks) 54.6.10 Trigger Conditions In addition to the SYNC signal, the software trigger and the RC compare trigger, an external trigger can be defined. TC_CMRx.ABETRG selects TIOAx or TIOBx input signal as an external trigger or the trigger signal from the output comparator of the PWM module. The External Trigger Edge Selection parameter (TC_CMR.ETRGEDG) defines the edge (rising, falling, or both) detected to generate an external trigger. If TC_CMRx.ETRGEDG = 0 (none), the external trigger is disabled.  2017 Microchip Technology Inc. DS60001476B-page 2039 SAMA5D2 SERIES Figure 54-6: Capture Mode Timer Counter Channel TCCLKS CLKI Synchronous Edge Detection TIMER_CLOCK1 TIMER_CLOCK2 CLKSTA TIMER_CLOCK3 CLKEN Q TIMER_CLOCK4 TIMER_CLOCK5 Q S R S XC0 CLKDIS R XC1 XC2 LDBSTOP Peripheral Clock LDBDIS BURST Register C Capture Register A 1 Capture Register B Compare RC = Counter SWTRG CLK OVF RESET SYNC Trig ABETRG CPCTRG ETRGEDG MTIOB Edge Detector TIOB CPCS LOVRS LDRBS Edge Detector COVFS TIOA Edge Detector LDRAS If RA is not loaded or RB is loaded LDRB TC1_IMR MTIOA LDRA ETRGS Edge Subsampler TC1_SR SBSMPLR If RA is loaded INT DS60001476B-page 2040  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.6.11 Waveform Mode Waveform mode is entered by setting TC_CMRx.WAVE. In Waveform mode, the TC channel generates one or two PWM signals with the same frequency and independently programmable duty cycles, or generates different types of one-shot or repetitive pulses. In this mode, TIOAx is configured as an output and TIOBx is defined as an output if it is not used as an external event (TC_CMR.EEVT). Figure 54-7 shows the configuration of the TC channel when programmed in Waveform operating mode. 54.6.12 Waveform Selection Depending on TC_CMRx.WAVSEL, the behavior of TC_CV varies. With any selection, TC_RA, TC_RB and TC_RC can all be used as compare registers. RA Compare is used to control the TIOAx output, RB Compare is used to control the TIOBx output (if correctly configured) and RC Compare is used to control TIOAx and/or TIOBx outputs. Figure 54-7: Waveform Mode TCCLKS CLKSTA TIMER_CLOCK1 Synchronous Edge Detection TIMER_CLOCK2 CLKEN CLKDIS ACPC CLKI TIMER_CLOCK3 Q TIMER_CLOCK4 S CPCDIS Q XC0 R S ACPA R XC1 XC2 CPCSTOP Peripheral Clock BURST Register A Register B Register C Compare RA = Compare RB = Compare RC = AEEVT MTIOA Output Controller TIMER_CLOCK5 TIOA WAVSEL ASWTRG 1 Counter CLK RESET SWTRG OVF BCPC SYNC Trig MTIOB BCPB EEVT BEEVT CPBS CPCS CPAS COVFS ENETRG ETRGS Edge Detector TC1_SR EEVTEDG Output Controller WAVSEL TIOB BSWTRG TIOB TC1_IMR Timer Counter Channel INT  2017 Microchip Technology Inc. DS60001476B-page 2041 SAMA5D2 SERIES 54.6.12.1 WAVSEL = 00 When TC_CMRx.WAVSEL = 00, the value of TC_CV is incremented from 0 to 232-1. Once 232-1 has been reached, the value of TC_CV is reset. Incrementation of TC_CV starts again and the cycle continues. See Figure 54-8. An external event trigger or a software trigger can reset the value of TC_CV. It is important to note that the trigger may occur at any time. See Figure 54-9. RC Compare cannot be programmed to generate a trigger in this configuration. At the same time, RC Compare can stop the counter clock (TC_CMR.CPCSTOP = 1) and/or disable the counter clock (TC_CMR.CPCDIS = 1). Figure 54-8: WAVSEL = 00 without Trigger Counter Value Counter cleared by compare match with 0xFFFF 0xFFFF RC RB RA Time Waveform Examples TIOB TIOA Figure 54-9: WAVSEL = 00 with Trigger Counter Value Counter cleared by compare match with 0xFFFF 0xFFFF RC Counter cleared by trigger RB RA Waveform Examples Time TIOB TIOA DS60001476B-page 2042  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.6.12.2 WAVSEL = 10 When TC_CMRx.WAVSEL = 10, the value of TC_CV is incremented from 0 to the value of RC, then automatically reset on a RC Compare. Once the value of TC_CV has been reset, it is then incremented and so on. See Figure 54-10. It is important to note that TC_CV can be reset at any time by an external event or a software trigger if both are programmed correctly. See Figure 54-11. In addition, RC Compare can stop the counter clock (TC_CMRx.CPCSTOP = 1) and/or disable the counter clock (TC_CMRx.CPCDIS = 1). Figure 54-10: WAVSEL = 10 without Trigger Counter Value 2n-1 (n = counter size) Counter cleared by compare match with RC RC RB RA Waveform Examples Time TIOB TIOA Figure 54-11: WAVSEL = 10 with Trigger Counter Value 2n-1 (n = counter size) Counter cleared by compare match with RC Counter cleared by trigger RC RB RA Waveform Examples Time TIOB TIOA 54.6.12.3 WAVSEL = 01 When TC_CMRx.WAVSEL = 01, the value of TC_CV is incremented from 0 to 232-1 . Once 232-1 is reached, the value of TC_CV is decremented to 0, then reincremented to 232-1 and so on. See Figure 54-12.  2017 Microchip Technology Inc. DS60001476B-page 2043 SAMA5D2 SERIES A trigger such as an external event or a software trigger can modify TC_CV at any time. If a trigger occurs while TC_CV is incrementing, TC_CV then decrements. If a trigger is received while TC_CV is decrementing, TC_CV then increments. See Figure 54-13. RC Compare cannot be programmed to generate a trigger in this configuration. At the same time, RC Compare can stop the counter clock (TC_CMRx.CPCSTOP = 1) and/or disable the counter clock (TC_CMRx.CPCDIS = 1). Figure 54-12: WAVSEL = 01 without Trigger Counter Value Counter decremented by compare match with 0xFFFF 0xFFFF RC RB RA Time Waveform Examples TIOB TIOA Figure 54-13: WAVSEL = 01 with Trigger Counter Value Counter decremented by compare match with 0xFFFF 0xFFFF Counter decremented by trigger RC RB Counter incremented by trigger RA Waveform Examples Time TIOB TIOA 54.6.12.4 WAVSEL = 11 When TC_CMRx.WAVSEL = 11, the value of TC_CV is incremented from 0 to RC. Once RC is reached, the value of TC_CV is decremented to 0, then reincremented to RC and so on. See Figure 54-14. A trigger such as an external event or a software trigger can modify TC_CV at any time. If a trigger occurs while TC_CV is incrementing, TC_CV then decrements. If a trigger is received while TC_CV is decrementing, TC_CV then increments. See Figure 54-15. DS60001476B-page 2044  2017 Microchip Technology Inc. SAMA5D2 SERIES RC Compare can stop the counter clock (TC_CMRx.CPCSTOP = 1) and/or disable the counter clock (TC_CMRx.CPCDIS = 1). Figure 54-14: WAVSEL = 11 without Trigger Counter Value 2n-1 (n = counter size) Counter decremented by compare match with RC RC RB RA Time Waveform Examples TIOB TIOA Figure 54-15: WAVSEL = 11 with Trigger Counter Value 2n-1 (n = counter size) RC RB Counter decremented by compare match with RC Counter decremented by trigger Counter incremented by trigger RA Waveform Examples Time TIOB TIOA  2017 Microchip Technology Inc. DS60001476B-page 2045 SAMA5D2 SERIES 54.6.13 External Event/Trigger Conditions An external event can be programmed to be detected on one of the clock sources (XC0, XC1, XC2) or TIOBx. The external event selected can then be used as a trigger. The event trigger is selected using TC_CMRx.EEVT. The trigger edge (rising, falling or both) for each of the possible external triggers is defined in TC_CMRx.EEVTEDG. If EEVTEDG is cleared (none), no external event is defined. If TIOBx is defined as an external event signal (EEVT = 0), TIOBx 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 TIOAx. When an external event is defined, it can be used as a trigger by setting TC_CMRx.ENETRG. 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 TC_CMRx.WAVSEL. 54.6.14 Synchronization with PWM The inputs TIOAx/TIOBx can be bypassed, and thus channel trigger/capture events can be directly driven by the independent PWM module. PWM comparator outputs (internal signals without dead-time insertion - OCx), respectively source of the PWMH/L[2:0] outputs, are routed to the internal TC inputs. These specific TC inputs are multiplexed with TIOA/B input signal to drive the internal trigger/capture events. The selection is made in the Extended Mode register (TC_EMR) fields TRIGSRCA and TRIGSRCB (see Section 54.7.14 “TC Extended Mode Register”). Each channel of the TC module can be synchronized by a different PWM channel as described in Figure 54-16. DS60001476B-page 2046  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-16: Synchronization with PWM Timer Counter TC_EMR0.TRIGSRCA Timer Counter Channel 0 TIOA0 TIOA0 1 TC_EMR0.TRIGSRCB TIOB0 TIOB0 1 TC_EMR1.TRIGSRCA Timer Counter Channel 1 TIOA1 TIOA1 1 TC_EMR1.TRIGSRCB TIOB1 TIOB1 1 TC_EMR2.TRIGSRCA Timer Counter Channel 2 TIOA2 TIOA2 1 TC_EMR2.TRIGSRCB TIOB2 TIOB2 1 PWM comparator outputs (internal signals) respectively source of PWMH/L[2:0]  2017 Microchip Technology Inc. DS60001476B-page 2047 SAMA5D2 SERIES 54.6.15 Output Controller The output controller defines the output level changes on TIOAx and TIOBx following an event. TIOBx control is used only if TIOBx is defined as output (not as an external event). The following events control TIOAx and TIOBx: • Software trigger • External event • RC compare RA Compare controls TIOAx, and RB Compare controls TIOBx. Each of these events can be programmed to set, clear or toggle the output as defined in the corresponding parameter in TC_CMR. 54.6.16 54.6.16.1 Quadrature Decoder Description The quadrature decoder (QDEC) is driven by TIOA0, TIOB0 and TIOB1 input pins and drives the timer counter of channel 0 and 1. Channel 2 can be used as a time base in case of speed measurement requirements (refer to Figure 54-17). When writing a ‘0’ to TC_BMR.QDEN, the QDEC is bypassed and the IO pins are directly routed to the timer counter function. TIOA0 and TIOB0 are to be driven by the two dedicated quadrature signals from a rotary sensor mounted on the shaft of the off-chip motor. A third signal from the rotary sensor can be processed through pin TIOB1 and is typically dedicated to be driven by an index signal if it is provided by the sensor. This signal is not required to decode the quadrature signals PHA, PHB. TC_CMRx.TCCLKS must be configured to select XC0 input (i.e., 0x101). TC_BMR.TC0XC0S has no effect as soon as the QDEC is enabled. Either speed or position/revolution can be measured. Position channel 0 accumulates the edges of PHA, PHB input signals giving a high accuracy on motor position whereas channel 1 accumulates the index pulses of the sensor, therefore the number of rotations. Concatenation of both values provides a high level of precision on motion system position. In Speed mode, position cannot be measured but revolution can be measured. Inputs from the rotary sensor can be filtered prior to downstream processing. Accommodation of input polarity, phase definition and other factors are configurable. Interruptions can be generated on different events. A compare function (using TC_RC) is available on channel 0 (speed/position) or channel 1 (rotation) and can generate an interrupt by means of TC_SRx.CPCS. DS60001476B-page 2048  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-17: Predefined Connection of the Quadrature Decoder with Timer Counters Reset pulse SPEEDEN Quadrature Decoder 1 1 (Filter + Edge Detect + QD) TIOA Timer Counter Channel 0 TIOA0 QDEN PHEdges 1 TIOB 1 XC0 TIOB0 TIOA0 PHA TIOB0 PHB TIOB1 IDX XC0 Speed/Position QDEN Index 1 TIOB TIOB1 1 XC0 Timer Counter Channel 1 XC0 Rotation Direction Timer Counter Channel 2 Speed Time Base 54.6.16.2 Input Preprocessing Input preprocessing consists of capabilities to take into account rotary sensor factors such as polarities and phase definition followed by configurable digital filtering. Each input can be negated and swapping PHA, PHB is also configurable. TC_BMR. MAXFILT is used to configure a minimum duration for which the pulse is stated as valid. When the filter is active, pulses with a duration lower than (MAXFILT +1) × tperipheral clock are not passed to downstream logic. The value of (MAXFILT +1) × tperipheral clock must not be greater than 10% of the minimum pulse on PHA, PHB or index when the rotary encoder speed is at its maximum. This speed depends on the application.  2017 Microchip Technology Inc. DS60001476B-page 2049 SAMA5D2 SERIES Figure 54-18: Input Stage Input Preprocessing MAXFILT SWAP 1 PHA Filter TIOA0 MAXFILT > 0 1 PHedge Direction and Edge Detection INVA 1 PHB Filter TIOB0 1 DIR 1 IDX INVB 1 1 IDX Filter TIOB1 IDXPHB INVIDX Input filtering can efficiently remove spurious pulses that might be generated by the presence of particulate contamination on the optical or magnetic disk of the rotary sensor. Spurious pulses can also occur in environments with high levels of electromagnetic interference. Or, simply if vibration occurs even when rotation is fully stopped and the shaft of the motor is in such a position that the beginning of one of the reflective or magnetic bars on the rotary sensor disk is aligned with the light or magnetic (Hall) receiver cell of the rotary sensor. Any vibration can make the PHA, PHB signals toggle for a short duration. DS60001476B-page 2050  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-19: Filtering Examples MAXFILT = 2 Peripheral Clock particulate contamination PHA,B Filter Out Optical/Magnetic disk strips PHA PHB motor shaft stopped so that rotary sensor cell is aligned with an edge of the disk rotation stop PHA PHB Edge area due to system vibration PHB Resulting PHA, PHB electrical waveforms PHA stop mechanical shock on system PHB vibration PHA, PHB electrical waveforms after filtering PHA PHB  2017 Microchip Technology Inc. DS60001476B-page 2051 SAMA5D2 SERIES 54.6.16.3 Direction Status and Change Detection After filtering, the quadrature signals are analyzed to extract the rotation direction and edges of the two quadrature signals detected in order to be counted by TC logic downstream. The direction status can be directly read at anytime in the TC_QISR. The polarity of the direction flag status depends on the configuration written in TC_BMR. INVA, INVB, INVIDX, SWAP modify the polarity of DIR flag. Any change in rotation direction is reported in the TC_QISR and can generate an interrupt. The direction change condition is reported as soon as two consecutive edges on a phase signal have sampled the same value on the other phase signal and there is an edge on the other signal. The two consecutive edges of one phase signal sampling the same value on other phase signal is not sufficient to declare a direction change, as particulate contamination may mask one or more reflective bars on the optical or magnetic disk of the sensor. Refer to Figure 54-20 for waveforms. Figure 54-20: Rotation Change Detection Direction Change under normal conditions PHA change condition Report Time PHB DIR DIRCHG No direction change due to particulate contamination masking a reflective bar missing pulse PHA same phase PHB DIR spurious change condition (if detected in a simple way) DIRCHG The direction change detection is disabled when TC_BMR.QDTRANS is set. In this case, the DIR flag report must not be used. A quadrature error is also reported by the QDEC via TC_QISR.QERR. This error is reported if the time difference between two edges on PHA, PHB is lower than a predefined value. This predefined value is configurable and corresponds to (TC_BMR.MAXFILT + 1) × tperipheral clock ns. After being filtered there is no reason to have two edges closer than (TC_BMR.MAXFILT + 1) × tperipheral clock ns under normal mode of operation. DS60001476B-page 2052  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-21: Quadrature Error Detection MAXFILT = 2 Peripheral Clock Abnormally formatted optical disk strips (theoretical view) PHA PHB strip edge inaccuracy due to disk etching/printing process PHA PHB resulting PHA, PHB electrical waveforms PHA Even with an abnormally formatted disk, there is no occurrence of PHA, PHB switching at the same time. PHB duration < MAXFILT QERR TC_BMR.MAXFILT must be tuned according to several factors such as the peripheral clock frequency, type of rotary sensor and rotation speed to be achieved. 54.6.16.4 Position and Rotation Measurement When TC_BMR.POSEN is set, the motor axis position is processed on channel 0 (by means of the PHA, PHB edge detections) and the number of motor revolutions are recorded on channel 1 if the IDX signal is provided on the TIOB1 input. If no IDX signal is available, the internal counter can be cleared for each revolution if the number of counts per revolution is configured in TC_RC0.RC and the TC_CMRx.CPCTRG bit is written to ‘1’. The position measurement can be read in the TC_CV0 register and the rotation measurement can be read in the TC_CV1 register. Channel 0 and 1 must be configured in Capture mode (TC_CMR0.WAVE = 0). ‘Rising edge’ must be selected as the External Trigger Edge (TC_CMR.ETRGEDG = 0x01) and ‘TIOAx’ must be selected as the External Trigger (TC_CMR.ABETRG = 0x1). The process must be started by configuring TC_CCR.CLKEN and TC_CCR.SWTRG. In parallel, the number of edges are accumulated on TC channel 0 and can be read on TC_CV0. Therefore, the accurate position can be read on both TC_CV registers and concatenated to form a 32-bit word. The TC channel 0 is cleared for each increment of IDX count value. Depending on the quadrature signals, the direction is decoded and allows to count up or down in TC channels 0 and 1. The direction status is reported on TC_QISR. 54.6.16.5 Speed Measurement When TC_BMR.SPEEDEN is set, the speed measure is enabled on channel 0.  2017 Microchip Technology Inc. DS60001476B-page 2053 SAMA5D2 SERIES A time base must be defined on channel 2 by writing the TC_RC2 period register. Channel 2 must be configured in Waveform mode (TC_CMR2.WAVE set). The TC_CMR.WAVSEL field must be defined with 0x10 to clear the counter by comparison and matching with TC_RC value. TC_CMR.ACPC must be defined at 0x11 to toggle TIOAx output. This time base is automatically fed back to TIOAx of channel 0 when TC_BMR.QDEN and TC_BMR.SPEEDEN are set. Channel 0 must be configured in Capture mode (TC_CMR0.WAVE = 0). TC_CMR0.ABETRG must be configured at 1 to select TIOAx as a trigger for this channel. EDGTRG must be set to 0x01, to clear the counter on a rising edge of the TIOAx signal and field LDRA must be set accordingly to 0x01, to load TC_RA0 at the same time as the counter is cleared (LDRB must be set to 0x01). As a consequence, at the end of each time base period the differentiation required for the speed calculation is performed. The process must be started by configuring bits CLKEN and SWTRG in the TC_CCR. The speed can be read on TC_RA0.RA. Channel 1 can still be used to count the number of revolutions of the motor. 54.6.16.6 Detecting a Missing Index Pulse To detect a missing index pulse due contamination, dust, etc., the TC_SR0.CPCS flag can be used. It is also possible to assert the interrupt line if the TC_SR0.CPCS flag is enabled as a source of the interrupt by writing a ‘1’ to TC_IER0.CPCS. The TC_RC0.RC field must be written with the nominal number of counts per revolution provided by the rotary encoder, plus a margin to eliminate potential noise (e.g., if nominal count per revolution is 1024, then TC_RC0.RC=1026). If the index pulse is missing, the timer value is not cleared and the nominal value is exceeded, then the comparator on the RC triggers an event, TC_SR0.CPCS=1, and the interrupt line is asserted if TC_IER0.CPCS=1. The missing index pulse detection is only valid if the bit TC_QISR.DIRCHG=0. 54.6.16.7 Detecting Contamination/Dust at Rotary Encoder Low Speed The contamination/dust that can be filtered when the rotary encoder speed is high may not be filtered at low speed, thus creating unsollicited direction change, etc. At low speed, even a minor contamination may appear as a long pulse, and thus not filtered and processed as a standard quadrature encoder pulse. This contamination can be detected by using the similar method as the missing index detection. A contamination exists on a phase line if TC_SR.CPCS = 1 and TC_QISR.DIRCHG = 1 when there is no sollicited change of direction. 54.6.16.8 Missing Pulse Detection and Autocorrection The QDEC is equipped with a circuitry which detects and corrects some errors that may result from contamination on optical disks or other materials producing the quadrature phase signals. The detection and autocorrection only works if the Count mode is configured for both phases (TC_BMR.EDGPHA = 1) and is enabled (TC_BMR.AUTOC = 1). If a pulse is missing on a phase signal, it is automatically detected and the pulse count reported in the CV field of the TC_CV0/1 is automatically corrected. There is no detection if both phase signals are affected at the same location on the device providing the quadrature signals because the detection requires a valid phase signal to detect the contamination on the other phase signal. DS60001476B-page 2054  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 54-22: Detection and Autocorrection of Missing Pulses Missing pulse due to a contamination (dust, scratch, etc.) PHA PHB detection Not a change of direction corrections 1 2 3 4 5 6 7 10 12 13 14 15 16 If a quadrature device is undamaged, the number of pulses counted for a predefined period of time must be the same with or without detection and autocorrection feature. Therefore, if the measurement results differ, a contamination exists on the device producing the quadrature signals. This does not substitute the measurements of the number of pulses between two index pulses (if available) but provides a complementary method to detect damaged quadrature devices. When the device providing quadrature signals is severely damaged, potentially leading to a number of consecutive missing pulses greater than 1, the downstream processing may be affected. It is possible to define the maximum admissible number of consecutive missing pulses before issuing a Missing Pulse Error flag (TC_QISR.MPE). The threshold triggering a MPE flag report can be configured in TC_BMR.MAXCMP. If the field MAXCMP is cleared, MPE never rises. The flag MAXCMP can trigger an interrupt while the QDEC is operating, thus providing a real time report of a potential problem on the quadrature device. 54.6.17 2-bit Gray Up/Down Counter for Stepper Motor Each channel can be independently configured to generate a 2-bit Gray count waveform on corresponding TIOAx, TIOBx outputs by means of TC_SMMRx.GCEN. Up or Down count can be defined by writing TC_SMMRx.DOWN. It is mandatory to configure the channel in Waveform mode in the TC_CMR. The period of the counters can be programmed in TC_RCx. Figure 54-23: 2-bit Gray Up/Down Counter WAVEx = GCENx =1 TIOAx TC_RCx TIOBx DOWNx 54.6.18 Fault Mode At any time, the TC_RCx registers can be used to perform a comparison on the respective current channel counter value (TC_CVx) with the value of TC_RCx register. The CPCSx flags can be set accordingly and an interrupt can be generated. This interrupt is processed but requires an unpredictable amount of time to be achieve the required action.  2017 Microchip Technology Inc. DS60001476B-page 2055 SAMA5D2 SERIES It is possible to trigger the FAULT output of the TIMER1 with TC_SR0.CPCS and/or TC_SR1.CPCS. Each source can be independently enabled/disabled in the TC_FMR. This can be useful to detect an overflow on speed and/or position when QDEC is processed and to act immediately by using the FAULT output. Figure 54-24: Fault Output Generation AND TC_SR0 flag CPCS OR TC_FMR / ENCF0 AND FAULT (to PWM input) TC_SR1 flag CPCS TC_FMR / ENCF1 DS60001476B-page 2056  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.6.19 Register Write Protection To prevent any single software error from corrupting TC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the TC Write Protection Mode Register (TC_WPMR). The Timer Counter clock of the first channel must be enabled to access TC_WPMR. The following registers can be write-protected when WPEN is set: • • • • • • • • • TC Block Mode Register TC Channel Mode Register: Capture Mode TC Channel Mode Register: Waveform Mode TC Fault Mode Register TC Stepper Motor Mode Register TC Register A TC Register B TC Register C TC Extended Mode Register  2017 Microchip Technology Inc. DS60001476B-page 2057 SAMA5D2 SERIES 54.7 Timer Counter (TC) User Interface Table 54-6: Register Mapping Offset(1) Register Name Access Reset 0x00 + channel * 0x40 + 0x00 Channel Control Register TC_CCR Write-only – 0x00 + channel * 0x40 + 0x04 Channel Mode Register TC_CMR Read/Write 0 0x00 + channel * 0x40 + 0x08 Stepper Motor Mode Register TC_SMMR Read/Write 0 0x00 + channel * 0x40 + 0x0C Register AB TC_RAB Read-only 0 0x00 + channel * 0x40 + 0x10 Counter Value TC_CV Read-only 0 0x00 + channel * 0x40 + 0x14 Register A TC_RA Read/Write(2) 0 0x00 + channel * 0x40 + 0x18 Register B TC_RB Read/Write(2) 0 0x00 + channel * 0x40 + 0x1C Register C TC_RC Read/Write 0 0x00 + channel * 0x40 + 0x20 Interrupt Status Register TC_SR Read-only 0 0x00 + channel * 0x40 + 0x24 Interrupt Enable Register TC_IER Write-only – 0x00 + channel * 0x40 + 0x28 Interrupt Disable Register TC_IDR Write-only – 0x00 + channel * 0x40 + 0x2C Interrupt Mask Register TC_IMR Read-only 0 0x00 + channel * 0x40 + 0x30 Extended Mode Register TC_EMR Read/Write 0 0x00 + channel * 0x40 + 0x34 Reserved – – – 0x00 + channel * 0x40 + 0x38 Reserved – – – 0x00 + channel * 0x40 + 0x3C Reserved – – – 0xC0 Block Control Register TC_BCR Write-only – 0xC4 Block Mode Register TC_BMR Read/Write 0 0xC8 QDEC Interrupt Enable Register TC_QIER Write-only – 0xCC QDEC Interrupt Disable Register TC_QIDR Write-only – 0xD0 QDEC Interrupt Mask Register TC_QIMR Read-only 0 0xD4 QDEC Interrupt Status Register TC_QISR Read-only 0 0xD8 Fault Mode Register TC_FMR Read/Write 0 0xD8 Reserved – – – 0xE4 Write Protection Mode Register TC_WPMR Read/Write 0 Reserved – – – 0xE8–0xFC Note 1: Channel index ranges from 0 to 2. 2: Read-only if TC_CMRx.WAVE = 0 DS60001476B-page 2058  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.1 TC Channel Control Register Name: TC_CCRx [x=0..2] Address: 0xF800C000 (0)[0], 0xF800C040 (0)[1], 0xF800C080 (0)[2], 0xF8010000 (1)[0], 0xF8010040 (1)[1], 0xF8010080 (1)[2] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 SWTRG 1 CLKDIS 0 CLKEN 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.  2017 Microchip Technology Inc. DS60001476B-page 2059 SAMA5D2 SERIES 54.7.2 TC Channel Mode Register: Capture Mode Name: TC_CMRx [x=0..2] (CAPTURE_MODE) Address: 0xF800C004 (0)[0], 0xF800C044 (0)[1], 0xF800C084 (0)[2], 0xF8010004 (1)[0], 0xF8010044 (1)[1], 0xF8010084 (1)[2] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 21 SBSMPLR 20 19 18 17 16 15 WAVE 14 CPCTRG 13 – 12 – 11 – 10 ABETRG 9 7 LDBDIS 6 LDBSTOP 5 4 3 CLKI 2 1 TCCLKS LDRB BURST LDRA 8 ETRGEDG 0 This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. TCCLKS: Clock Selection Value Name Description 0 TIMER_CLOCK1 Clock selected: internal GCLK [35], GCLK [36] clock signal (from PMC) 1 TIMER_CLOCK2 Clock selected: internal System bus clock divided by 8 clock signal (from PMC) 2 TIMER_CLOCK3 Clock selected: internal System bus clock divided by 32 clock signal (from PMC) 3 TIMER_CLOCK4 Clock selected: internal System bus clock divided by 128 clock signal (from PMC) 4 TIMER_CLOCK5 Clock selected: internal slow_clock clock signal (from PMC) 5 XC0 Clock selected: XC0 6 XC1 Clock selected: XC1 7 XC2 Clock selected: XC2 To operate at maximum peripheral clock frequency, refer to Section 54.7.14 “TC Extended Mode Register”. 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 Value Name Description 0 NONE The clock is not gated by an external signal. 1 XC0 XC0 is ANDed with the selected clock. 2 XC1 XC1 is ANDed with the selected clock. 3 XC2 XC2 is ANDed with the selected clock. LDBSTOP: Counter Clock Stopped with RB Loading 0: Counter clock is not stopped when RB loading occurs. DS60001476B-page 2060  2017 Microchip Technology Inc. SAMA5D2 SERIES 1: Counter clock is stopped when RB loading occurs. LDBDIS: Counter Clock Disable with RB Loading 0: Counter clock is not disabled when RB loading occurs. 1: Counter clock is disabled when RB loading occurs. ETRGEDG: External Trigger Edge Selection Value Name Description 0 NONE The clock is not gated by an external signal. 1 RISING Rising edge 2 FALLING Falling edge 3 EDGE Each edge ABETRG: TIOAx or TIOBx External Trigger Selection 0: TIOBx is used as an external trigger. 1: TIOAx 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: Waveform Mode 0: Capture mode is enabled. 1: Capture mode is disabled (Waveform mode is enabled). LDRA: RA Loading Edge Selection Value Name Description 0 NONE None 1 RISING Rising edge of TIOAx 2 FALLING Falling edge of TIOAx 3 EDGE Each edge of TIOAx LDRB: RB Loading Edge Selection Value Name Description 0 NONE None 1 RISING Rising edge of TIOAx 2 FALLING Falling edge of TIOAx 3 EDGE Each edge of TIOAx SBSMPLR: Loading Edge Subsampling Ratio Value Name Description 0 ONE Load a Capture register each selected edge 1 HALF Load a Capture register every 2 selected edges  2017 Microchip Technology Inc. DS60001476B-page 2061 SAMA5D2 SERIES 2 FOURTH Load a Capture register every 4 selected edges 3 EIGHTH Load a Capture register every 8 selected edges 4 SIXTEENTH Load a Capture register every 16 selected edges DS60001476B-page 2062  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.3 TC Channel Mode Register: Waveform Mode Name: TC_CMRx [x=0..2] (WAVEFORM_MODE) Address: 0xF800C004 (0)[0], 0xF800C044 (0)[1], 0xF800C084 (0)[2], 0xF8010004 (1)[0], 0xF8010044 (1)[1], 0xF8010084 (1)[2] Access: Read/Write 31 30 29 BSWTRG 23 28 27 BEEVT 22 21 ASWTRG 20 19 AEEVT 15 WAVE 14 13 7 CPCDIS 6 CPCSTOP WAVSEL 26 25 24 BCPC BCPB 18 17 16 ACPC 12 ENETRG 11 4 3 CLKI 5 BURST ACPA 10 9 EEVT 8 EEVTEDG 2 1 TCCLKS 0 This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. TCCLKS: Clock Selection Value Name Description 0 TIMER_CLOCK1 Clock selected: internal GCLK [35], GCLK [36] clock signal (from PMC) 1 TIMER_CLOCK2 Clock selected: internal System bus clock divided by 8 clock signal (from PMC) 2 TIMER_CLOCK3 Clock selected: internal System bus clock divided by 32 clock signal (from PMC) 3 TIMER_CLOCK4 Clock selected: internal System bus clock divided by 128 clock signal (from PMC) 4 TIMER_CLOCK5 Clock selected: internal slow_clock clock signal (from PMC) 5 XC0 Clock selected: XC0 6 XC1 Clock selected: XC1 7 XC2 Clock selected: XC2 To operate at maximum peripheral clock frequency, refer to Section 54.7.14 “TC Extended Mode Register”. 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 Value Name Description 0 NONE The clock is not gated by an external signal. 1 XC0 XC0 is ANDed with the selected clock. 2 XC1 XC1 is ANDed with the selected clock. 3 XC2 XC2 is ANDed with the selected clock.  2017 Microchip Technology Inc. DS60001476B-page 2063 SAMA5D2 SERIES 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 0: Counter clock is not disabled when counter reaches RC. 1: Counter clock is disabled when counter reaches RC. EEVTEDG: External Event Edge Selection Value Name Description 0 NONE None 1 RISING Rising edge 2 FALLING Falling edge 3 EDGE Each edge EEVT: External Event Selection Signal selected as external event. Value Name Description 0 TIOB (1) TIOB Direction TIOB Input 1 XC0 XC0 Output 2 XC1 XC1 Output 3 XC2 XC2 Output Note 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. 1: The external event resets the counter and starts the counter clock. Note: Whatever the value programmed in ENETRG, the selected external event only controls the TIOAx output and TIOBx if not used as input (trigger event input or other input used). WAVSEL: Waveform Selection Value Name Description 0 UP UP mode without automatic trigger on RC Compare 1 UPDOWN UPDOWN mode without automatic trigger on RC Compare 2 UP_RC UP mode with automatic trigger on RC Compare 3 UPDOWN_RC UPDOWN mode with automatic trigger on RC Compare WAVE: Waveform Mode 0: Waveform mode is disabled (Capture mode is enabled). 1: Waveform mode is enabled. ACPA: RA Compare Effect on TIOAx Value Name Description 0 NONE None DS60001476B-page 2064  2017 Microchip Technology Inc. SAMA5D2 SERIES 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle ACPC: RC Compare Effect on TIOAx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle AEEVT: External Event Effect on TIOAx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle ASWTRG: Software Trigger Effect on TIOAx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle BCPB: RB Compare Effect on TIOBx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle  2017 Microchip Technology Inc. DS60001476B-page 2065 SAMA5D2 SERIES BCPC: RC Compare Effect on TIOBx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle BEEVT: External Event Effect on TIOBx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle BSWTRG: Software Trigger Effect on TIOBx Value Name Description 0 NONE None 1 SET Set 2 CLEAR Clear 3 TOGGLE Toggle DS60001476B-page 2066  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.4 TC Stepper Motor Mode Register Name: TC_SMMRx [x=0..2] Address: 0xF800C008 (0)[0], 0xF800C048 (0)[1], 0xF800C088 (0)[2], 0xF8010008 (1)[0], 0xF8010048 (1)[1], 0xF8010088 (1)[2] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 DOWN 0 GCEN This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. GCEN: Gray Count Enable 0: TIOAx [x=0..2] and TIOBx [x=0..2] are driven by internal counter of channel x. 1: TIOAx [x=0..2] and TIOBx [x=0..2] are driven by a 2-bit Gray counter. DOWN: Down Count 0: Up counter. 1: Down counter.  2017 Microchip Technology Inc. DS60001476B-page 2067 SAMA5D2 SERIES 54.7.5 TC Register AB Name: TC_RABx [x=0..2] Address: 0xF800C00C (0)[0], 0xF800C04C (0)[1], 0xF800C08C (0)[2], 0xF801000C (1)[0], 0xF801004C (1)[1], 0xF801008C (1)[2] Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RAB 23 22 21 20 RAB 15 14 13 12 RAB 7 6 5 4 RAB RAB: Register A or Register B RAB contains the next unread capture Register A or Register B value in real time. It is usually read by the DMA after a request due to a valid load edge on TIOAx. When DMA is used, the RAB register address must be configured as source address of the transfer. DS60001476B-page 2068  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.6 TC Counter Value Register Name: TC_CVx [x=0..2] Address: 0xF800C010 (0)[0], 0xF800C050 (0)[1], 0xF800C090 (0)[2], 0xF8010010 (1)[0], 0xF8010050 (1)[1], 0xF8010090 (1)[2] Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 CV 23 22 21 20 CV 15 14 13 12 CV 7 6 5 4 CV CV: Counter Value CV contains the counter value in real time.  2017 Microchip Technology Inc. DS60001476B-page 2069 SAMA5D2 SERIES 54.7.7 TC Register A Name: TC_RAx [x=0..2] Address: 0xF800C014 (0)[0], 0xF800C054 (0)[1], 0xF800C094 (0)[2], 0xF8010014 (1)[0], 0xF8010054 (1)[1], 0xF8010094 (1)[2] Access: Read-only if TC_CMRx.WAVE = 0, Read/Write if TC_CMRx.WAVE = 1 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RA 23 22 21 20 RA 15 14 13 12 RA 7 6 5 4 RA This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. RA: Register A RA contains the Register A value in real time. DS60001476B-page 2070  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.8 TC Register B Name: TC_RBx [x=0..2] Address: 0xF800C018 (0)[0], 0xF800C058 (0)[1], 0xF800C098 (0)[2], 0xF8010018 (1)[0], 0xF8010058 (1)[1], 0xF8010098 (1)[2] Access: Read-only if TC_CMRx.WAVE = 0, Read/Write if TC_CMRx.WAVE = 1 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RB 23 22 21 20 RB 15 14 13 12 RB 7 6 5 4 RB This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. RB: Register B RB contains the Register B value in real time.  2017 Microchip Technology Inc. DS60001476B-page 2071 SAMA5D2 SERIES 54.7.9 TC Register C Name: TC_RCx [x=0..2] Address: 0xF800C01C (0)[0], 0xF800C05C (0)[1], 0xF800C09C (0)[2], 0xF801001C (1)[0], 0xF801005C (1)[1], 0xF801009C (1)[2] Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 RC 23 22 21 20 RC 15 14 13 12 RC 7 6 5 4 RC This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. RC: Register C RC contains the Register C value in real time. DS60001476B-page 2072  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.10 TC Interrupt Status Register Name: TC_SRx [x=0..2] Address: 0xF800C020 (0)[0], 0xF800C060 (0)[1], 0xF800C0A0 (0)[2], 0xF8010020 (1)[0], 0xF8010060 (1)[1], 0xF80100A0 (1)[2] Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 MTIOB 17 MTIOA 16 CLKSTA 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 ETRGS 6 LDRBS 5 LDRAS 4 CPCS 3 CPBS 2 CPAS 1 LOVRS 0 COVFS COVFS: Counter Overflow Status (cleared on read) 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 (cleared on read) 0: Load overrun has not occurred since the last read of the Status Register or TC_CMRx.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 TC_CMRx.WAVE = 0. CPAS: RA Compare Status (cleared on read) 0: RA Compare has not occurred since the last read of the Status Register or TC_CMRx.WAVE = 0. 1: RA Compare has occurred since the last read of the Status Register, if TC_CMRx.WAVE = 1. CPBS: RB Compare Status (cleared on read) 0: RB Compare has not occurred since the last read of the Status Register or TC_CMRx.WAVE = 0. 1: RB Compare has occurred since the last read of the Status Register, if TC_CMRx.WAVE = 1. CPCS: RC Compare Status (cleared on read) 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 (cleared on read) 0: RA Load has not occurred since the last read of the Status Register or TC_CMRx.WAVE = 1. 1: RA Load has occurred since the last read of the Status Register, if TC_CMRx.WAVE = 0. LDRBS: RB Loading Status (cleared on read) 0: RB Load has not occurred since the last read of the Status Register or TC_CMRx.WAVE = 1. 1: RB Load has occurred since the last read of the Status Register, if TC_CMRx.WAVE = 0. ETRGS: External Trigger Status (cleared on read) 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. CLKSTA: Clock Enabling Status  2017 Microchip Technology Inc. DS60001476B-page 2073 SAMA5D2 SERIES 0: Clock is disabled. 1: Clock is enabled. MTIOA: TIOAx Mirror 0: TIOAx is low. If TC_CMRx.WAVE = 0, TIOAx pin is low. If TC_CMRx.WAVE = 1, TIOAx is driven low. 1: TIOAx is high. If TC_CMRx.WAVE = 0, TIOAx pin is high. If TC_CMRx.WAVE = 1, TIOAx is driven high. MTIOB: TIOBx Mirror 0: TIOBx is low. If TC_CMRx.WAVE = 0, TIOBx pin is low. If TC_CMRx.WAVE = 1, TIOBx is driven low. 1: TIOBx is high. If TC_CMRx.WAVE = 0, TIOBx pin is high. If TC_CMRx.WAVE = 1, TIOBx is driven high. DS60001476B-page 2074  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.11 TC Interrupt Enable Register Name: TC_IERx [x=0..2] Address: 0xF800C024 (0)[0], 0xF800C064 (0)[1], 0xF800C0A4 (0)[2], 0xF8010024 (1)[0], 0xF8010064 (1)[1], 0xF80100A4 (1)[2] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 ETRGS 6 LDRBS 5 LDRAS 4 CPCS 3 CPBS 2 CPAS 1 LOVRS 0 COVFS The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. COVFS: Counter Overflow LOVRS: Load Overrun CPAS: RA Compare CPBS: RB Compare CPCS: RC Compare LDRAS: RA Loading LDRBS: RB Loading ETRGS: External Trigger  2017 Microchip Technology Inc. DS60001476B-page 2075 SAMA5D2 SERIES 54.7.12 TC Interrupt Disable Register Name: TC_IDRx [x=0..2] Address: 0xF800C028 (0)[0], 0xF800C068 (0)[1], 0xF800C0A8 (0)[2], 0xF8010028 (1)[0], 0xF8010068 (1)[1], 0xF80100A8 (1)[2] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 ETRGS 6 LDRBS 5 LDRAS 4 CPCS 3 CPBS 2 CPAS 1 LOVRS 0 COVFS The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. COVFS: Counter Overflow LOVRS: Load Overrun CPAS: RA Compare CPBS: RB Compare CPCS: RC Compare LDRAS: RA Loading LDRBS: RB Loading ETRGS: External Trigger DS60001476B-page 2076  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.13 TC Interrupt Mask Register Name: TC_IMRx [x=0..2] Address: 0xF800C02C (0)[0], 0xF800C06C (0)[1], 0xF800C0AC (0)[2], 0xF801002C (1)[0], 0xF801006C (1)[1], 0xF80100AC (1)[2] Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 ETRGS 6 LDRBS 5 LDRAS 4 CPCS 3 CPBS 2 CPAS 1 LOVRS 0 COVFS The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. COVFS: Counter Overflow LOVRS: Load Overrun CPAS: RA Compare CPBS: RB Compare CPCS: RC Compare LDRAS: RA Loading LDRBS: RB Loading 0ETRGS: External Trigger  2017 Microchip Technology Inc. DS60001476B-page 2077 SAMA5D2 SERIES 54.7.14 TC Extended Mode Register Name: TC_EMRx [x=0..2] Address: 0xF800C030 (0)[0], 0xF800C070 (0)[1], 0xF800C0B0 (0)[2], 0xF8010030 (1)[0], 0xF8010070 (1)[1], 0xF80100B0 (1)[2] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 NODIVCLK 7 – 6 – 5 4 3 – 2 – 1 TRIGSRCB 0 TRIGSRCA This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. TRIGSRCA: Trigger Source for Input A Value Name Description 0 EXTERNAL_TIOAx The trigger/capture input A is driven by external pin TIOAx 1 PWMx The trigger/capture input A is driven internally by PWMx TRIGSRCB: Trigger Source for Input B Value 0 1 Name Description EXTERNAL_TIOBx The trigger/capture input B is driven by external pin TIOBx PWMx For TC0 to TC10: The trigger/capture input B is driven internally by the comparator output (see Figure 54-16) of the PWMx. For TC11: The trigger/capture input B is driven internally by the GTSUCOMP signal of the Ethernet MAC (GMAC). NODIVCLK: No Divided Clock 0: The selected clock is defined by field TCCLKS in TC_CMRx. 1: The selected clock is peripheral clock and TCCLKS field (TC_CMRx) has no effect. DS60001476B-page 2078  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.15 TC Block Control Register Name: TC_BCR Address: 0xF800C0C0 (0), 0xF80100C0 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 SYNC SYNC: Synchro Command 0: No effect. 1: Asserts the SYNC signal which generates a software trigger simultaneously for each of the channels.  2017 Microchip Technology Inc. DS60001476B-page 2079 SAMA5D2 SERIES 54.7.16 TC Block Mode Register Name: TC_BMR Address: 0xF800C0C4 (0), 0xF80100C4 (1) Access: Read/Write 31 – 30 – 23 22 29 28 27 26 25 MAXCMP 24 MAXFILT 21 20 19 – 18 AUTOC 17 IDXPHB 16 SWAP 12 EDGPHA 11 QDTRANS 10 SPEEDEN 9 POSEN 8 QDEN 4 3 2 1 0 MAXFILT 15 INVIDX 14 INVB 13 INVA 7 – 6 – 5 TC2XC2S TC1XC1S TC0XC0S This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. TC0XC0S: External Clock Signal 0 Selection Value Name Description 0 TCLK0 Signal connected to XC0: TCLK0 1 – Reserved 2 TIOA1 Signal connected to XC0: TIOA1 3 TIOA2 Signal connected to XC0: TIOA2 TC1XC1S: External Clock Signal 1 Selection Value Name Description 0 TCLK1 Signal connected to XC1: TCLK1 1 – Reserved 2 TIOA0 Signal connected to XC1: TIOA0 3 TIOA2 Signal connected to XC1: TIOA2 TC2XC2S: External Clock Signal 2 Selection Value Name Description 0 TCLK2 Signal connected to XC2: TCLK2 1 – Reserved 2 TIOA0 Signal connected to XC2: TIOA0 3 TIOA1 Signal connected to XC2: TIOA1 DS60001476B-page 2080  2017 Microchip Technology Inc. SAMA5D2 SERIES QDEN: Quadrature Decoder Enabled 0: Disabled. 1: Enables the QDEC (filter, edge detection and quadrature decoding). Quadrature decoding (direction change) can be disabled using QDTRANS bit. One of the POSEN or SPEEDEN bits must be also enabled. POSEN: Position Enabled 0: Disable position. 1: Enables the position measure on channel 0 and 1. SPEEDEN: Speed Enabled 0: Disabled. 1: Enables the speed measure on channel 0, the time base being provided by channel 2. QDTRANS: Quadrature Decoding Transparent 0: Full quadrature decoding logic is active (direction change detected). 1: Quadrature decoding logic is inactive (direction change inactive) but input filtering and edge detection are performed. EDGPHA: Edge on PHA Count Mode 0: Edges are detected on PHA only. 1: Edges are detected on both PHA and PHB. INVA: Inverted PHA 0: PHA (TIOA0) is directly driving the QDEC. 1: PHA is inverted before driving the QDEC. INVB: Inverted PHB 0: PHB (TIOB0) is directly driving the QDEC. 1: PHB is inverted before driving the QDEC. INVIDX: Inverted Index 0: IDX (TIOA1) is directly driving the QDEC. 1: IDX is inverted before driving the QDEC. SWAP: Swap PHA and PHB 0: No swap between PHA and PHB. 1: Swap PHA and PHB internally, prior to driving the QDEC. IDXPHB: Index Pin is PHB Pin 0: IDX pin of the rotary sensor must drive TIOA1. 1: IDX pin of the rotary sensor must drive TIOB0. AUTOC: AutoCorrection of missing pulses 0 (DISABLED): The detection and autocorrection function is disabled. 1 (ENABLED): The detection and autocorrection function is enabled. MAXFILT: Maximum Filter 1–63: Defines the filtering capabilities. Pulses with a period shorter than MAXFILT+1 peripheral clock cycles are discarded. For more details on MAXFILT constraints, see Section 54.6.16.2 “Input Preprocessing” MAXCMP: Maximum Consecutive Missing Pulses 0: The flag MPE in TC_QISR never rises.  2017 Microchip Technology Inc. DS60001476B-page 2081 SAMA5D2 SERIES 1–15: Defines the number of consecutive missing pulses before a flag report. DS60001476B-page 2082  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.17 TC QDEC Interrupt Enable Register Name: TC_QIER Address: 0xF800C0C8 (0), 0xF80100C8 (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 MPE 2 QERR 1 DIRCHG 0 IDX IDX: Index 0: No effect. 1: Enables the interrupt when a rising edge occurs on IDX input. DIRCHG: Direction Change 0: No effect. 1: Enables the interrupt when a change on rotation direction is detected. QERR: Quadrature Error 0: No effect. 1: Enables the interrupt when a quadrature error occurs on PHA, PHB. MPE: Consecutive Missing Pulse Error 0: No effect. 1: Enables the interrupt when an occurrence of MAXCMP consecutive missing pulses is detected.  2017 Microchip Technology Inc. DS60001476B-page 2083 SAMA5D2 SERIES 54.7.18 TC QDEC Interrupt Disable Register Name: TC_QIDR Address: 0xF800C0CC (0), 0xF80100CC (1) Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 MPE 2 QERR 1 DIRCHG 0 IDX IDX: Index 0: No effect. 1: Disables the interrupt when a rising edge occurs on IDX input. DIRCHG: Direction Change 0: No effect. 1: Disables the interrupt when a change on rotation direction is detected. QERR: Quadrature Error 0: No effect. 1: Disables the interrupt when a quadrature error occurs on PHA, PHB. MPE: Consecutive Missing Pulse Error 0: No effect. 1: Disables the interrupt when an occurrence of MAXCMP consecutive missing pulses has been detected. DS60001476B-page 2084  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.19 TC QDEC Interrupt Mask Register Name: TC_QIMR Address: 0xF800C0D0 (0), 0xF80100D0 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 MPE 2 QERR 1 DIRCHG 0 IDX IDX: Index 0: The interrupt on IDX input is disabled. 1: The interrupt on IDX input is enabled. DIRCHG: Direction Change 0: The interrupt on rotation direction change is disabled. 1: The interrupt on rotation direction change is enabled. QERR: Quadrature Error 0: The interrupt on quadrature error is disabled. 1: The interrupt on quadrature error is enabled. MPE: Consecutive Missing Pulse Error 0: The interrupt on the maximum number of consecutive missing pulses specified in MAXCMP is disabled. 1: The interrupt on the maximum number of consecutive missing pulses specified in MAXCMP is enabled.  2017 Microchip Technology Inc. DS60001476B-page 2085 SAMA5D2 SERIES 54.7.20 TC QDEC Interrupt Status Register Name: TC_QISR Address: 0xF800C0D4 (0), 0xF80100D4 (1) Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 DIR 7 – 6 – 5 – 4 – 3 MPE 2 QERR 1 DIRCHG 0 IDX IDX: Index 0: No Index input change since the last read of TC_QISR. 1: The IDX input has changed since the last read of TC_QISR. DIRCHG: Direction Change 0: No change on rotation direction since the last read of TC_QISR. 1: The rotation direction changed since the last read of TC_QISR. QERR: Quadrature Error 0: No quadrature error since the last read of TC_QISR. 1: A quadrature error occurred since the last read of TC_QISR. MPE: Consecutive Missing Pulse Error 0: The number of consecutive missing pulses has not reached the maximum value specified in MAXCMP since the last read of TC_QISR. 1: An occurrence of MAXCMP consecutive missing pulses has been detected since the last read of TC_QISR. DIR: Direction Returns an image of the current rotation direction. DS60001476B-page 2086  2017 Microchip Technology Inc. SAMA5D2 SERIES 54.7.21 TC Fault Mode Register Name: TC_FMR Address: 0xF800C0D8 (0), 0xF80100D8 (1) Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 ENCF1 0 ENCF0 This register can only be written if the WPEN bit is cleared in the TC Write Protection Mode Register. ENCF0: Enable Compare Fault Channel 0 0: Disables the FAULT output source (CPCS flag) from channel 0. 1: Enables the FAULT output source (CPCS flag) from channel 0. ENCF1: Enable Compare Fault Channel 1 0: Disables the FAULT output source (CPCS flag) from channel 1. 1: Enables the FAULT output source (CPCS flag) from channel 1.  2017 Microchip Technology Inc. DS60001476B-page 2087 SAMA5D2 SERIES 54.7.22 TC Write Protection Mode Register Name: TC_WPMR Address: 0xF800C0E4 (0), 0xF80100E4 (1) Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x54494D (“TIM” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x54494D (“TIM” in ASCII). The Timer Counter clock of the first channel must be enabled to access this register. See Section 54.6.19 “Register Write Protection” for a list of registers that can be write-protected and Timer Counter clock conditions. WPKEY: Write Protection Key Value 0x54494D Name PASSWD DS60001476B-page 2088 Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0.  2017 Microchip Technology Inc. SAMA5D2 SERIES 55. Pulse Density Modulation Interface Controller (PDMIC) 55.1 Description The Pulse Density Modulation Interface Controller (PDMIC) is a PDM interface controller and decoder that support mono PDM format. It integrates a clock generator driving the PDM microphone and embeds filters which decimate the incoming bitstream to obtain most common audio rates. 55.2 • • • • • Embedded Characteristics 16-bit Resolution DMA Controller Support Up to 4 Conversions Stored PDM Clock Source can be Independent from Core Clock Register Write Protection 55.3 Block Diagram Figure 55-1: PDMIC Block Diagram PDM Interface Controller CLKS PMC Peripheral Clock 0 GCLK Clock 1 PDMIC Interrupt Control Logic Interrupt Controller System Bus DMA Peripheral Bridge PDMIC_DAT PDM Data Sampling PDMIC_CLK Digital Filter User Interface APB 55.4 Signal Description Table 55-1: PDMIC Pin Description Pin Name Description Type PDMIC_CLK Pulse Density Modulation Bitstream Sampling Clock Output PDMIC_DAT Pulse Density Modulation Data Input  2017 Microchip Technology Inc. DS60001476B-page 2089 SAMA5D2 SERIES 55.5 Product Dependencies 55.5.1 I/O Lines The pins used for interfacing the PDMIC are multiplexed with PIO lines. The programmer must first program the PIO controllers to assign the peripheral functions to PDMIC pins. Table 55-2: I/O Lines Instance Signal I/O Line Peripheral PDMIC PDMIC_CLK PB12 D PDMIC PDMIC_CLK PB27 D PDMIC PDMIC_DAT PB11 D PDMIC PDMIC_DAT PB26 D 55.5.2 Power Management The PDMIC is not continuously clocked. The user must first enable the PDMIC peripheral clock and the PDMIC Generic Clock in the Power Management Controller (PMC) before using the controller. 55.5.3 Interrupt Sources The PDMIC interrupt line is connected on one of the internal sources of the Interrupt Controller. Using the PDMIC interrupt requires the Interrupt Controller to be programmed first. Table 55-3: Peripheral IDs Instance ID PDMIC 48 DS60001476B-page 2090  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.6 Functional Description 55.6.1 PDM Interface 55.6.1.1 Description The PDM clock (PDMIC_CLK) is used to sample the PDM bitstream. The PDMIC_CLK frequency range is between peripheral clock/2 and peripheral clock/256 or between GCLK clock/2 and GCLK clock/ 256, depending on the selected clock source. The GCLK clock frequency must always be at least three times lower than the peripheral clock frequency. The field PRESCAL in the Mode Register (PDMIC_MR) must be programmed in order to provide a PDMIC_CLK frequency compliant with the microphone parameters. 55.6.1.2 Startup Sequence To start processing the bitstream coming from the PDM interface, follow the steps below: 1. 2. 3. Clear all bits in the Control Register (PDMIC_CR) or compute a soft reset using the SWRST bit of PDMIC_CR. Configure the PRESCAL field in PDMIC_MR according to the microphone specifications. Enable the PDM mode and start the conversions using the ENPDM bit in PDMIC_CR. 55.6.2 Digital Signal Processing (Digital Filter) 55.6.2.1 Description The PDMIC includes a DSP section containing a decimation filter, a droop compensation filter, a sixth-order low pass filter, a first-order high pass filter and an offset and gain compensation stage. A block diagram of the DSP section is represented in Figure 55-2. DSP Block Diagram. Data processed by the filtering section are two’s complement signals defined on 24 bits. The filtering of the decimation stage is performed by a fourth-order sinc-based filter whose zeros are placed in order to minimize aliasing effects of the decimation. The decimation ratio of this filter is either 32 or 64. The droop induced by this filter can be compensated by the droop compensation stage. The sixth-order low pass filter is used to decimate the sinc filter output by a ratio of 2. An optional first-order high pass filter is implemented in order to eliminate the DC component of the incoming signal. The overall decimation ratio of this DSP section is either 64 or 128. This fits an audio sampling rate of 48 kHz with a PDM microphone sampling frequency of either 3.072 or 6.144 MHz. The frequency response of the filters optimizes the gain flatness between 0 and 20 kHz (when the droop compensation filter is implemented and the high pass filter is bypassed) and highly reduces the aliasing effects of the decimation. Figure 55-2: DSP Block Diagram hpf_byp sincc_byp 16 or 32 bits data0 3 24 24 32 1 + SINC Filter Decimation Droop Compensation Low Pass Filter 32 1 signed right shift 0 1 0 1 16 LSBs ... 0 1 1 data Decimation offset * 28 55.6.2.2 ... signed right shift 32/64 High Pass Filter 0 { 2 gain scale shift Decimation Filter The sigma-delta architecture of the PDM microphone implies a filtering and a decimation of the bitstream at the output of the microphone bitstream. The decimation filter decimates the bitstream by either 32 or 64. To perform this operation, a fourth-order sinc filter with an OverSampling Ratio (OSR) of 32 or 64 is implemented with the following transfer function:  OSR – 1  –i 1 H ( z ) = ---------------4-   z  OSR   i=0  2017 Microchip Technology Inc. 4 DS60001476B-page 2091 SAMA5D2 SERIES The DC gain of this filter is unity and does not depend on its OSR. However, as it generates a fourth-order zero at Fs/OSR frequency multiples (Fs being the sampling frequency of the microphone), the frequency response of the decimation filter depends on the OSR parameter. See Section 55.6.2.3 “Droop Compensation” for frequency plots. Its non-flat frequency response can be compensated over the 0 to 20 kHz band by using the droop compensation filter when the decimated frequency is set to 48 kHz. See Section 55.6.2.3 “Droop Compensation”. If the decimated sampling rate is modified, the frequency response of this filter is scaled proportionally to the new frequency. In Figure 55-3 and Figure 55-4, Fs is the sampling rate of the PDM microphone. Figure 55-3: Spectral mask of an OSR = 32, Fs = 6.144 MHz, Fourth-Order Sinc Filter: Overall Response (continuous line) and 0 to 20 kHz Bandwidth Response (dashed line) frequency (kHz), base band, output sampling rate = 48 kHz 0 2.5 5 7.5 10 12.5 15 17.5 20 0 -24 -0.14 -48 -0.28 -72 -0.42 -96 -0.56 -120 0 Fs/16 2*Fs/16 3*Fs/16 4*Fs/16 5*Fs/16 frequency (Hz), overall mask 6*Fs/16 7*Fs/16 gain (dB), base band gain (dB), overall mask 0 -0.7 8*Fs/16 The zeros of this filter are located at multiples of Fs/32 Figure 55-4: Spectral Mask of an OSR = 64, Fs = 3.072 MHz, Fourth-order Sinc Filter: Overall Response (continuous line) and 0 to 20 kHz Bandwidth Response (dashed line) frequency (kHz), base band, output sampling rate = 48 kHz 2.5 5 7.5 10 12.5 15 17.5 20 0 -24 -0.6 -48 -1.2 -72 -1.8 -96 -2.4 -120 0 Fs/16 2*Fs/16 3*Fs/16 4*Fs/16 5*Fs/16 frequency (Hz), overall mask 6*Fs/16 7*Fs/16 gain (dB), base band gain (dB), overall mask 0 0 -3 8*Fs/16 The zeros of this filter are located at multiples of Fs/64. DS60001476B-page 2092  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.6.2.3 Droop Compensation The droop effect introduced by the sinc filter can be compensated in the 0 to 20 kHz by the droop compensation filter (see Figure 55-5). This is a second-order IIR filter which is applied on the signal output by the sinc. The default coefficients of the droop compensation filter are computed to optimize the droop of the sinc filter with the decimated frequency equal to 48 kHz. This filter compensates the droop of the sinc filter regardless of the OSR value. If the decimated sampling rate is modified, the frequency response of this filter is scaled proportionally to the new frequency. This filter can be bypassed by setting the SINBYP bit in the PDMIC DSP Configuration Register 0 (PDMIC_DSPR0). Figure 55-5: Droop Compensation Filter Overall Frequency Response droop compensation overall response 2 sinc filter response sinc filter+droop compensation response 0 gain (dB) -2 -4 -6 -8 -10 Figure 55-6: 0 1 2 3 4 5 6 frequency (Hz) 7 8 9 10 4 x 10 Droop Compensation Filter 0 to 20 kHz Band Flatness -4 2 droop compensation flatness in 0-20kHz band x 10 gain (dB) 1 0 -1 -2  2017 Microchip Technology Inc. 0 0.2 0.4 0.6 0.8 1 1.2 frequency (Hz) 1.4 1.6 1.8 2 4 x 10 DS60001476B-page 2093 SAMA5D2 SERIES 55.6.2.4 Low Pass Filter The PDMIC includes a sixth-order IIR filter that performs a low pass transfer function and decimates by 2 the output of the sinc filter. The coefficients are computed for a decimated sampling rate of 48 kHz and optimize the 0 to 20 kHz band flatness while rejecting the aliasing of the PDM microphone by at least 60 dB in the 28 to 48 kHz band. If the decimated sampling rate is modified, the frequency response of this filter is scaled proportionally to the new frequency. Figure 55-7 and Figure 55-8 are drawn for an output sampling frequency of 48 kHz. Figure 55-7: Low Pass Filter Spectral Mask Low pass filter spectral mask 0 -20 gain (dB) -40 -60 -80 -100 -120 Figure 55-8: 0 0.5 1 1.5 2 2.5 3 frequency (Hz) 3.5 4 4.5 5 4 x 10 Low Pass Filter Ripple in the 0 to 20 kHz Band Low pass filter 0-20kHz ripple 0.05 0.04 0.03 0.02 gain (dB) 0.01 0 -0.01 -0.02 -0.03 -0.04 -0.05 DS60001476B-page 2094 0 0.2 0.4 0.6 0.8 1 1.2 frequency (Hz) 1.4 1.6 1.8 2 4 x 10  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.6.2.5 High Pass Filter The PDMIC includes an optional first-order IIR filter performing a high pass transfer function after the low pass filter and before the decimation. The coefficients are computed for a decimated sampling rate of 48 kHz to obtain a -3dB cutoff frequency at 15 Hz. If the decimated sampling rate is modified, the frequency response of this filter is scaled proportionally to the new frequency. This filter can be bypassed by setting the HPFBYP bit in PDMIC_DSPR0 (see Section 55.7.8 “PDMIC DSP Configuration Register 0”). Figure 55-9 is drawn for an output sampling frequency of 48 kHz. Figure 55-9: High Pass Filter Spectral Mask in the 0 to 100 Hz Band High pass filter spectral mask 0 -5 gain (dB) -10 -15 -20 -25 -30 55.6.2.6 0 10 20 30 40 50 60 frequency (Hz) 70 80 90 100 Gain and Offset Compensation An offset, a gain, a scaling factor and a shift can be applied to a converted PDM microphone value using the following operation: 8 ( data 0 + offset × 2 ) × dgain data = ----------------------------------------------------------------------------scale + shift + 8 2 where: • data0 is a signed integer defined on 24 bits. It is the output of the filtering channel. • offset is a signed integer defined on 16 bits (see PDMIC DSP Configuration Register 1). It is multiplied by 28 to have the same weight as data0. • dgain is an unsigned integer defined on 15 bits (see PDMIC DSP Configuration Register 1). Only the 32 MSBs of the multiplication operation are used for scaling and shifting operations. dgain defaults to 0 after reset, which forces CDR to 0. It must be programmed to a non-zero value to read non-zero data into the PDMIC_CDR register. • scale is an unsigned integer defined on 4 bits (see PDMIC DSP Configuration Register 0). It shifts the multiplication operation result by scale bits to the right. Maximum allowed value is 15. • shift is an unsigned integer defined on 4 bits (see PDMIC DSP Configuration Register 0). It shifts the multiplication operation result by shift bits to the right. Maximum allowed value is 15. If the data transfer is configured in 32-bit mode (see PDMIC DSP Configuration Register 0), the 2shift division is not performed and the 32bit result of the remaining operation is sent. If the data transfer is configured in 16-bit mode, the 2shift division is performed. The result is then saturated to be within ±(215-1) and the 16 LSBs of this saturation operation are sent to the controller as the result of the PDM microphone conversion. Default parameters are defined to output a 16-bit result whatever the data transfer configuration may be.  2017 Microchip Technology Inc. DS60001476B-page 2095 SAMA5D2 SERIES 55.6.3 Conversion Results When a conversion is completed, the resulting 16-bit digital value is stored in the PDMIC Converted Data Register (PDMIC_CDR). The DRDY bit in the Interrupt Status Register (PDMIC_ISR) is set. In the case of a connected DMA Controller channel, DRDY rising triggers a data transfer request. In any case, DRDY can trigger an interrupt. Reading PDMIC_CDR clears the DRDY flag. Figure 55-10: DRDY Flag Behavior Write the PDMIC_CR with ENPDM = 1 Read the PDMIC_CDR Read the PDMIC_CDR DRDY (PDMIC_SR) If PDMIC_CDR is not read before further incoming data is converted, the Overrun Error (OVRE) flag is set in PDMIC_ISR. Likewise, new data converted when DRDY is high sets the OVRE bit (Overrun Error) in PDMIC_ISR. In case of overrun, the newly converted data is lost. The OVRE flag is automatically cleared when PDMIC_ISR is read. 55.6.4 Register Write Protection To prevent any single software error from corrupting PDMIC behavior, certain registers in the address space can be write-protected by setting the WPEN bit in the PDMIC Write Protection Mode Register (PDMIC_WPMR). If a write access to a write-protected register is detected, the WPVS flag in the PDMIC Write Protection Status Register (PDMIC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS bit is automatically cleared after reading PDMIC_WPSR. The following registers can be write-protected: • PDMIC Mode Register • PDMIC DSP Configuration Register 0 • PDMIC DSP Configuration Register 1 DS60001476B-page 2096  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7 Pulse Density Modulation Interface Controller (PDMIC) User Interface Table 55-4: Offset Register Mapping (1) Register Name Access Reset 0x00 Control Register PDMIC_CR Read/Write 0x00000000 0x04 Mode Register PDMIC_MR Read/Write 0x00F00000 Reserved – – – 0x14 Converted Data Register PDMIC_CDR Read-only 0x00000000 0x18 Interrupt Enable Register PDMIC_IER Write-only – 0x1C Interrupt Disable Register PDMIC_IDR Write-only – 0x20 Interrupt Mask Register PDMIC_IMR Read-only 0x00000000 0x24 Interrupt Status Register PDMIC_ISR Read-only 0x00000000 Reserved – – – 0x58 DSP Configuration Register 0 PDMIC_DSPR0 Read/Write 0x00000000 0x5C DSP Configuration Register 1 PDMIC_DSPR1 Read/Write 0x00000001 Reserved – – – 0xE4 Write Protection Mode Register PDMIC_WPMR Read/Write 0x00000000 0xE8 Write Protection Status Register PDMIC_WPSR Read-only 0x00000000 Reserved – – – 0x08–0x10 0x28–0x54 0x60–0xE0 0xEC–0xFC Note 1: If an offset is not listed in the table, it must be considered as “reserved”.  2017 Microchip Technology Inc. DS60001476B-page 2097 SAMA5D2 SERIES 55.7.1 PDMIC Control Register Name: PDMIC_CR Address: 0xF8018000 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 ENPDM 3 – 2 – 1 – 0 SWRST SWRST: Software Reset 0: No effect. 1: Resets the PDMIC, simulating a hardware reset. Warning: The read value of this bit is always 0. ENPDM: Enable PDM 0: Disables the PDM and stops the conversions. 1: Enables the PDM and starts the conversions. DS60001476B-page 2098  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7.2 PDMIC Mode Register Name: PDMIC_MR Address: 0xF8018004 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 13 12 11 PRESCAL 10 9 8 7 – 6 – 5 – 4 CLKS 3 – 2 – 1 – 0 – This register can only be written if the WPEN bit is cleared in the PDMIC Write Protection Mode Register. CLKS: Clock Source Selection 0: Peripheral clock selected 1: GCLK clock selected (This clock source can be independent of the processor clock.) PRESCAL: Prescaler Rate Selection PRESCAL determines the frequency of the PDM bitstream sampling clock (PDMIC_CLK): SELCK PRESCAL = --------------------------------------- – 1 2 × f PDMIC_CLK where SELCK is either fperipheral clock or fGCLK clock depending on the value of bit CLKS (fperipheral clock or fGCLK clock is the clock frequency in Hz).  2017 Microchip Technology Inc. DS60001476B-page 2099 SAMA5D2 SERIES 55.7.3 PDMIC Converted Data Register Name: PDMIC_CDR Address: 0xF8018014 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 DATA 23 22 21 20 DATA 15 14 13 12 DATA 7 6 5 4 DATA DATA: Data Converted The filtered output data is placed into this register at the end of a conversion and remains until it is read. DS60001476B-page 2100  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7.4 PDMIC Interrupt Enable Register Name: PDMIC_IER Address: 0xF8018018 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 OVRE 24 DRDY 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. DRDY: Data Ready Interrupt Enable OVRE: Overrun Error Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 2101 SAMA5D2 SERIES 55.7.5 PDMIC Interrupt Disable Register Name: PDMIC_IDR Address: 0xF801801C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 OVRE 24 DRDY 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. DRDY: Data Ready Interrupt Disable OVRE: General Overrun Error Interrupt Disable DS60001476B-page 2102  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7.6 PDMIC Interrupt Mask Register Name: PDMIC_IMR Address: 0xF8018020 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 OVRE 24 DRDY 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. DRDY: Data Ready Interrupt Mask OVRE: General Overrun Error Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 2103 SAMA5D2 SERIES 55.7.7 PDMIC Interrupt Status Register Name: PDMIC_ISR Address: 0xF8018024 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 OVRE 24 DRDY 19 18 17 16 FIFOCNT 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – FIFOCNT: FIFO Count Number of conversions available in the FIFO (not a source of interrupt). DRDY: Data Ready (cleared by reading PDMIC_CDR) 0: No data has been converted since the last read of PDMIC_CDR. 1: At least one data has been converted and is available in PDMIC_CDR. OVRE: Overrun Error (cleared on read) 0: No overrun error has occurred since the last read of PDMIC_ISR. 1: At least one overrun error has occurred since the last read of PDMIC_ISR. DS60001476B-page 2104  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7.8 PDMIC DSP Configuration Register 0 Name: PDMIC_DSPR0 Address: 0xF8018058 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 1 HPFBYP 0 – SHIFT 7 – 6 SCALE 5 OSR 4 3 SIZE 2 SINBYP This register can only be written if the WPEN bit is cleared in the PDMIC Write Protection Mode Register. HPFBYP: High-Pass Filter Bypass 0: High-pass filter enabled. 1: Bypasses the high-pass filter. SINBYP: SINCC Filter Bypass 0: Droop compensation filter enabled. 1: Bypasses the droop compensation filter. SIZE: Data Size 0: Converted data size is 16 bits. 1: Converted data size is 32 bits. OSR: Global Oversampling Ratio Value Name 0 128 Global Oversampling ratio is 128 (SINC filter oversampling ratio is 64) 1 64 Global Oversampling ratio is 64 (SINC filter oversampling ratio is 32) Note: Description Values not listed are reserved. SCALE: Data Scale Shifts the multiplication operation result by SCALE bits to the right. SHIFT: Data Shift Shifts the scaled result by SHIFT bits to the right.  2017 Microchip Technology Inc. DS60001476B-page 2105 SAMA5D2 SERIES 55.7.9 PDMIC DSP Configuration Register 1 Name: PDMIC_DSPR1 Address: 0xF801805C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 DGAIN 10 9 8 3 2 1 0 OFFSET 23 22 21 20 OFFSET 15 – 14 13 12 7 6 5 4 DGAIN This register can only be written if the WPEN bit is cleared in the PDMIC Write Protection Mode Register. DGAIN: Gain Correction Gain correction to apply to the final result. OFFSET: Offset Correction Offset correction to apply to the final result. DGAIN and OFFSET values can be determined using the formula in Section 55.6.2.6 “Gain and Offset Compensation”. DS60001476B-page 2106  2017 Microchip Technology Inc. SAMA5D2 SERIES 55.7.10 PDMIC Write Protection Mode Register Name: PDMIC_WPMR Address: 0xF80180E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY corresponds to 0x414443 (“ADC” in ASCII). 1: Enables the write protection if WPKEY corresponds to 0x414443 (“ADC” in ASCII). See Section 55.6.4 “Register Write Protection” for the list of registers that can be write-protected. WPKEY: Write Protection Key Value Name 0x414443 PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0. DS60001476B-page 2107 SAMA5D2 SERIES 55.7.11 PDMIC Write Protection Status Register Name: PDMIC_WPSR Address: 0xF80180E8 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of PDMIC_WPSR. 1: A write protection violation has occurred since the last read of PDMIC_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 2108  2017 Microchip Technology Inc. SAMA5D2 SERIES 56. Pulse Width Modulation Controller (PWM) 56.1 Description The Pulse Width Modulation Controller (PWM) generates output pulses on 4 channels independently according to parameters defined per channel. Each channel controls two complementary square output waveforms. Characteristics of the output waveforms such as period, duty-cycle, polarity and dead-times (also called dead-bands or non-overlapping times) are configured 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 peripheral clock. External triggers can be managed to allow output pulses to be modified in real time. All accesses to the PWM are made through registers mapped on the peripheral bus. All channels integrate a double buffering system in order to prevent any unexpected output waveform while modifying the period, the spread spectrum, the duty-cycle or the dead-times. Channels can be linked together as synchronous channels to be able to update their duty-cycle or dead-times at the same time. The update of duty-cycles of synchronous channels can be performed by the DMA Controller channel which offers buffer transfer without processor Intervention. The PWM includes a spread-spectrum counter to allow a constantly varying period (only for Channel 0). This counter may be useful to minimize electromagnetic interference or to reduce the acoustic noise of a PWM driven motor. The PWM provides 1 independent comparison units capable of comparing a programmed value to the counter of the synchronous channels (counter of channel 0). These comparisons are intended to generate software interrupts, to trigger pulses on the 2 independent event lines (in order to synchronize ADC conversions with a lot of flexibility independently of the PWM outputs) and to trigger DMA Controller transfer requests. PWM outputs can be overridden synchronously or asynchronously to their channel counter. The PWM provides a fault protection mechanism with 6 fault inputs, capable to detect a fault condition and to override the PWM outputs asynchronously (outputs forced to ‘0’, ‘1’ or Hi-Z). For safety usage, some configuration registers are write-protected.  2017 Microchip Technology Inc. DS60001476B-page 2109 SAMA5D2 SERIES 56.2 Embedded Characteristics • 4 Channels • 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 16-bit Counter for Each Channel - Independent Complementary Outputs with 16-bit Dead-Time Generator (Also Called Dead-Band or Non-Overlapping Time) for Each Channel - Independent Push-Pull Mode for Each Channel - Independent Enable Disable Command for Each Channel - Independent Clock Selection for Each Channel - Independent Period, Duty-Cycle and Dead-Time for Each Channel - Independent Double Buffering of Period, Duty-Cycle and Dead-Times for Each Channel - Independent Programmable Selection of The Output Waveform Polarity for Each Channel, with Double Buffering - Independent Programmable Center- or Left-aligned Output Waveform for Each Channel - Independent Output Override for Each Channel - Independent Interrupt for Each Channel, at Each Period for Left-Aligned or Center-Aligned Configuration - Independent Update Time Selection of Double Buffering Registers (Polarity, Duty Cycle) for Each Channel, at Each Period for Left-Aligned or Center-Aligned Configuration • External Trigger Input Management (e.g., for DC/DC or Lighting Control) - External PWM Reset Mode - External PWM Start Mode - Cycle-By-Cycle Duty Cycle Mode - Leading-Edge Blanking • Two 2-bit Gray Up/Down Channels for Stepper Motor Control • Spread Spectrum Counter to Allow a Constantly Varying Duty Cycle (only for Channel 0) • Synchronous Channel Mode - Synchronous Channels Share the Same Counter - Mode to Update the Synchronous Channels Registers after a Programmable Number of Periods - Synchronous Channels Supports Connection of one DMA Controller Channel Which Offers Buffer Transfer Without Processor Intervention To Update Duty-Cycle Registers • 2 Independent Events Lines Intended to Synchronize ADC Conversions - Programmable delay for Events Lines to delay ADC measurements • 1 Comparison Units Intended to Generate Interrupts, Pulses on Event Lines and DMA Controller Transfer Requests • 6 Programmable Fault Inputs Providing an Asynchronous Protection of PWM Outputs - 2 User Driven through PIO Inputs - PMC Driven when Crystal Oscillator Clock Fails - ADC Controller Driven through Configurable Comparison Function - Timer/Counter Driven through Configurable Comparison Function • Register Write Protection DS60001476B-page 2110  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.3 Block Diagram Figure 56-1: Pulse Width Modulation Controller Block Diagram PWM Controller PPM = Push-Pull Mode Channel x Update Period OCx Comparator Duty-Cycle 1 Clock Selector Counter Channel x PPM DTOHx Dead-Time Generator DTOLx PWMHx OOOHx Output Override Fault OOOLx Protection PWMHx PWMLx PWMLx 0 SYNCx 0 PWMEXTRG2 PIO Glitch Filter 1 ETM = External Trigger Mode Channel 2 1 Recoverable Fault Management Update 0 PWMEXTRG1 TRGIN2 PWM_ETRG2.TRGSRC Period PIO PWM_ETRG2.TRGFLT ETM OC2 Comparator Duty-Cycle PPM DTOH2 Dead-Time Generator DTOL2 PWMH2 PWMH2 PWML2 PWML2 OOOH2 Output Override Fault OOOL2 Protection 1 Clock Selector Counter Channel 2 0 SYNC2 0 Glitch Filter 1 ACC Channel 1 1 Recoverable Fault Management Update 0 TRGIN1 PWM_ETRG1.TRGSRC Period PWM_ETRG1.TRGFLT ETM OC1 1 Clock Selector Counter Channel 1 PPM DTOH1 Dead-Time Generator Comparator Duty-Cycle DTOL1 PWMH1 OOOH1 Output Override Fault OOOL1 Protection PWMH1 PWML1 PWML1 0 SYNC1 Channel 0 Update Period Comparator Duty-Cycle OC0 PPM DTOH0 Dead-Time Generator DTOL0 PWMH0 OOOH0 Output Override Fault OOOL0 Protection Fault Input Management PIO PWMFI0 event line 0 event line 1 Comparison Units Peripheral Clock PMC PWML0 Counter Channel 0 Clock Selector PWMFIx PWMH0 PWML0 Events Generator ADC event line x Clock Generator APB Interface Interrupt Controller Interrupt Generator APB Note: For a more detailed illustration of the fault protection circuitry, refer to Figure 56-16 “Fault Protection”.  2017 Microchip Technology Inc. DS60001476B-page 2111 SAMA5D2 SERIES 56.4 I/O Lines Description Each channel outputs two complementary external I/O lines. Table 56-1: I/O Line Description Name Description Type PWMHx PWM Waveform Output High for channel x Output PWMLx PWM Waveform Output Low for channel x Output PWMFIx PWM Fault Input x Input PWMEXTRGy PWM Trigger Input y Input 56.5 Product Dependencies 56.5.1 I/O Lines The pins used for interfacing the PWM are 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. All of the PWM outputs may or may not be enabled. If an application requires only four channels, then only four PIO lines are assigned to PWM outputs. Table 56-2: I/O Lines Instance Signal I/O Line Peripheral PWM PWMEXTRG1 PB3 D PWM PWMEXTRG2 PB10 C PWM PWMFI0 PB2 D PWM PWMFI1 PB9 C PWM PWMH0 PA30 D PWM PWMH1 PB0 D PWM PWMH2 PB5 C PWM PWMH3 PB7 C PWM PWML0 PA31 D PWM PWML1 PB1 D PWM PWML2 PB6 C PWM PWML3 PB8 C 56.5.2 Power Management The PWM is not continuously clocked. The programmer must first enable the PWM clock in the Power Management Controller (PMC) before using the PWM. 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. 56.5.3 Interrupt Sources The PWM interrupt line is connected on one of the internal sources of the Interrupt Controller. Using the PWM interrupt requires the Interrupt Controller to be programmed first. Table 56-3: Peripheral IDs Instance ID PWM 38 DS60001476B-page 2112  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.5.4 Fault Inputs The PWM has the fault inputs connected to the different modules. Refer to the implementation of these modules within the product for detailed information about the fault generation procedure. The PWM receives faults from: • • • • PIO inputs the PMC the ADC controller Timer/Counters Table 56-4: Fault Inputs Fault Generator External PWM Fault Input Number Polarity Level(1) Fault Input ID PB2 PWMFI0 User-defined 0 PB9 PWMFI1 User-defined 1 PMC – To be configured to 1 2 ADC – To be configured to 1 3 Timer0 – To be configured to 1 4 Timer1 – To be configured to 1 5 Note 1: FPOL field in PWMC_FMR.  2017 Microchip Technology Inc. DS60001476B-page 2113 SAMA5D2 SERIES 56.6 Functional Description The PWM controller is primarily composed of a clock generator module and 4 channels. • Clocked by the peripheral clock, 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. 56.6.1 PWM Clock Generator Figure 56-2: Functional View of the Clock Generator Block Diagram Peripheral Clock modulo n counter peripheral clock peripheral clock/2 peripheral clock/4 peripheral clock/8 peripheral clock/16 peripheral clock/32 peripheral clock/64 peripheral clock/128 peripheral clock/256 peripheral clock/512 peripheral clock/1024 Divider A PREA clkA DIVA PWM_MR Divider B PREB clkB DIVB PWM_MR The PWM peripheral clock 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. The clock generator is divided into different blocks: - a modulo n counter which provides 11 clocks: fperipheral clock, fperipheral clock/2, fperipheral clock/4, fperipheral clock/8, fperipheral clock/16, fperipheral clock/32, fperipheral clock/64, fperipheral clock/128, fperipheral clock/256, fperipheral clock/512, fperipheral clock/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 Clock register (PWM_CLK). The resulting clock clkA (clkB) is the clock selected divided by DIVA (DIVB) field value. After a reset of the PWM controller, DIVA (DIVB) and PREA (PREB) 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 the peripheral clock. This situation is also true when the PWM peripheral clock is turned off through the Power Management Controller. DS60001476B-page 2114  2017 Microchip Technology Inc. SAMA5D2 SERIES CAUTION: Before using the PWM controller, the programmer must first enable the peripheral clock in the Power Management Controller (PMC). 56.6.2 PWM Channel 56.6.2.1 Channel Block Diagram Figure 56-3: Functional View of the Channel Block Diagram Channel x Update Period MUX Comparator x OCx PWMHx OOOHx DTOHx Dead-Time Output Fault OOOLx PWMLx Generator DTOLx Override Protection Duty-Cycle MUX from Clock Generator Clock Selector SYNCx Counter Channel x from APB Peripheral Bus Counter Channel 0 2-bit gray counter z Comparator y MUX z = 0 (x = 0, y = 1), z = 1 (x = 2, y = 3), z = 2 (x = 4, y = 5), z = 3 (x = 6, y = 7) Channel y (= x+1) OCy PWMHy OOOHy DTOHy Dead-Time Output Fault Generator DTOLy Override OOOLy Protection PWMLy Each of the 4 channels is composed of six blocks: • A clock selector which selects one of the clocks provided by the clock generator (described in Section 56.6.1 “PWM Clock Generator”). • A counter clocked by the output of the clock selector. This counter is incremented or decremented according to the channel configuration and comparators matches. The size of the counter is 16 bits. • A comparator used to compute the OCx output waveform according to the counter value and the configuration. The counter value can be the one of the channel counter or the one of the channel 0 counter according to SYNCx bit in the PWM Sync Channels Mode Register (PWM_SCM). • A 2-bit configurable Gray counter enables the stepper motor driver. One Gray counter drives 2 channels. • A dead-time generator providing two complementary outputs (DTOHx/DTOLx) which allows to drive external power control switches safely. • An output override block that can force the two complementary outputs to a programmed value (OOOHx/OOOLx). • An asynchronous fault protection mechanism that has the highest priority to override the two complementary outputs (PWMHx/ PWMLx) in case of fault detection (outputs forced to ‘0’, ‘1’ or Hi-Z). 56.6.2.2 Comparator The comparator continuously compares its counter value with the channel period defined by CPRD in the PWM Channel Period Register (PWM_CPRDx) and the duty-cycle defined by CDTY in the PWM Channel Duty Cycle Register (PWM_CDTYx) to generate an output signal OCx accordingly. The different properties of the waveform of the output OCx are: • the clock selection. The 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 PWM Channel Mode Register (PWM_CMRx). This field is reset at ‘0’. • the waveform period. This channel parameter is defined in the CPRD field of the PWM_CPRDx register. If the waveform is left-aligned, then the output waveform period depends on the counter source clock and can be calculated: By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is:  2017 Microchip Technology Inc. DS60001476B-page 2115 SAMA5D2 SERIES ( X × CPRD ) ---------------------------------f peripheral clock By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (----------------------------------------------------X × C PRD × DIVA )( X × C PRD × DIVB ) or -----------------------------------------------------f peripheral clock f peripheral clock If the waveform is center-aligned, then the output waveform period depends on the counter source clock and can be calculated: By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is: (-----------------------------------------2 × X × CPRD ) f peripheral clock By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (--------------------------------------------------------------2 × X × C PRD × DIVA )f peripheral clock or (--------------------------------------------------------------2 × X × C PRD × DIVB )f peripheral clock • the waveform duty-cycle. This channel parameter is defined in the CDTY field of the PWM_CDTYx register. If the waveform is left-aligned, then: ( period – 1 ⁄ fchannel_x_clock × CDTY ) duty cycle = ---------------------------------------------------------------------------------------------------------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 bit of PWM_CMRx. By default, the signal starts by a low level. The DPOLI bit in PWM_CMRx defines the PWM polarity when the channel is disabled (CHIDx = 0 in PWM_SR). For more details, see Figure 56-5. - DPOLI = 0: PWM polarity when the channel is disabled is the same as the one defined for the beginning of the PWM period. - DPOLI = 1: PWM polarity when the channel is disabled is inverted compared to the one defined for the beginning of the PWM period. • 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 bit of PWM_CMRx. The default mode is left-aligned. Figure 56-4: Non-Overlapped Center-Aligned Waveforms No overlap OC0 OC1 Period Note: See Figure 56-5 for a detailed description of center-aligned waveforms. When center-aligned, the channel counter increases up to CPRD and decreases down to 0. This ends the period. When left-aligned, the 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. DS60001476B-page 2116  2017 Microchip Technology Inc. SAMA5D2 SERIES Waveforms are fixed at 0 when: • CDTY = CPRD and CPOL = 0 (Note that if TRGMODE = MODE3, the PWM waveform switches to 1 at the external trigger event (see Section 56.6.5.3 “Cycle-By-Cycle Duty Mode”)). • 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 (Note that if TRGMODE = MODE3, the PWM waveform switches to 0 at the external trigger event (see Section 56.6.5.3 “Cycle-By-Cycle Duty Mode”)). The waveform polarity must be set before enabling the channel. This immediately affects the channel output level. Modifying CPOL in PWM Channel Mode Register while the channel is enabled can lead to an unexpected behavior of the device being driven by PWM. In addition to generating the output signals OCx, the comparator generates interrupts depending on the counter value. When the output waveform is left-aligned, the interrupt occurs at the end of the counter period. When the output waveform is center-aligned, the bit CES of PWM_CMRx defines when the channel counter interrupt occurs. If CES is set to ‘0’, the interrupt occurs at the end of the counter period. If CES is set to ‘1’, the interrupt occurs at the end of the counter period and at half of the counter period. Figure 56-5 illustrates the counter interrupts depending on the configuration.  2017 Microchip Technology Inc. DS60001476B-page 2117 SAMA5D2 SERIES Figure 56-5: Waveform Properties Channel x slected clock 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 OCx CPOL(PWM_CMRx) = 0 DPOLI(PWM_CMRx) = 0 Output Waveform OCx CPOL(PWM_CMRx) = 0 DPOLI(PWM_CMRx) = 1 Output Waveform OCx CPOL(PWM_CMRx) = 1 DPOLI(PWM_CMRx) = 0 Output Waveform OCx CPOL(PWM_CMRx) = 1 DPOLI(PWM_CMRx) = 1 Counter Event CHIDx(PWM_ISR) CES(PWM_CMRx) = 0 Counter Event CHIDx(PWM_ISR) CES(PWM_CMRx) = 1 Left Aligned CALG(PWM_CMRx) = 0 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Period Output Waveform OCx CPOL(PWM_CMRx) = 0 DPOLI(PWM_CMRx) = 0 Output Waveform OCx CPOL(PWM_CMRx) = 0 DPOLI(PWM_CMRx) = 1 Output Waveform OCx CPOL(PWM_CMRx) = 1 DPOLI(PWM_CMRx) = 0 Output Waveform OCx CPOL(PWM_CMRx) = 1 DPOLI(PWM_CMRx) = 1 Counter Event CHIDx(PWM_ISR) DS60001476B-page 2118  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.2.3 Trigger Selection for Timer Counter The PWM controller can be used as a trigger source for the Timer Counter (TC) to achieve the two application examples described below. • Delay Measurement To measure the delay between the channel x comparator output (OCx) and the feedback from the bridge driver of the MOSFETs (see Figure 56-6), the bit TCTS in the PWM Channel Mode Register must be at 0. This defines the comparator output of the channel x as the TC trigger source. The TIOB trigger (TC internal input) is used to start the TC; the TIOA input (from PAD) is used to capture the delay. Figure 56-6: Triggering the TC: Delay Measurement Microcontroller PIO TIMER_COUNTER TIOA TIOA TIOA CH0 CH1 CH2 TIOB TIOB TIOB MOSFETs PWM Triggers BRIDGE DRIVER PWM0 PWM1 PWM2 PWM: OCx (internally routed to TIOB) TC: TIOA (from PAD) Capture event TC: Count value and capture event (TIOA/TIOB rising edge triggered) Capture event TC: Count value and capture event (TIOA/TIOB falling edge triggered) • Cumulated ON Time Measurement To measure the cumulated “ON” time of MOSFETs (see Figure 56-7), the bit TCTS of the PWM Channel Mode Register must be set to 1 to define the counter event (see Figure 56-5) as the Timer Counter trigger source.  2017 Microchip Technology Inc. DS60001476B-page 2119 SAMA5D2 SERIES Figure 56-7: Triggering the TC: Cumulated “ON” Time Measurement Microcontroller PIO TIMER_COUNTER TIOA TIOA TIOA CH0 CH1 CH2 TIOB TIOB TIOB MOSFETs PWM Triggers BRIDGE DRIVER PWM0 PWM1 PWM2 Center Aligned CALG(PWM_CMRx) = 1 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Period PWM: OCx TC: TIOA (from PAD) PWM Counter Event CES(PWM_CMRx) = 0 (internally routed to TIOB) TC: Count value (TIOA/TIOB rising edge triggered) Left Aligned CALG(PWM_CMRx) = 0 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Period PWM: OCx TC: TIOA (from PAD) PWM Counter Event (internally routed to TIOB) TC: Count value (TIOA/TIOB rising edge triggered) DS60001476B-page 2120  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.2.4 2-bit Gray Up/Down Counter for Stepper Motor A pair of channels may provide a 2-bit Gray count waveform on two outputs. Dead-time generator and other downstream logic can be configured on these channels. Up or Down Count mode can be configured on-the-fly by means of PWM_SMMR configuration registers. When GCEN0 is set to ‘1’, channels 0 and 1 outputs are driven with Gray counter. Figure 56-8: 2-bit Gray Up/Down Counter GCEN0 = 1 PWMH0 PWML0 PWMH1 PWML1 DOWNx  2017 Microchip Technology Inc. DS60001476B-page 2121 SAMA5D2 SERIES 56.6.2.5 Dead-Time Generator The dead-time generator uses the comparator output OCx to provide the two complementary outputs DTOHx and DTOLx, which allows the PWM macrocell to drive external power control switches safely. When the dead-time generator is enabled by setting the bit DTE to 1 or 0 in the PWM Channel Mode Register (PWM_CMRx), dead-times (also called dead-bands or non-overlapping times) are inserted between the edges of the two complementary outputs DTOHx and DTOLx. Note that enabling or disabling the dead-time generator is allowed only if the channel is disabled. The dead-time is adjustable by the PWM Channel Dead Time Register (PWM_DTx). Each output of the dead-time generator can be adjusted separately by DTH and DTL. The dead-time values can be updated synchronously to the PWM period by using the PWM Channel Dead Time Update Register (PWM_DTUPDx). The dead-time is based on a specific counter which uses the same selected clock that feeds the channel counter of the comparator. Depending on the edge and the configuration of the dead-time, DTOHx and DTOLx are delayed until the counter has reached the value defined by DTH or DTL. An inverted configuration bit (DTHI and DTLI bit in PWM_CMRx) is provided for each output to invert the deadtime outputs. The following figure shows the waveform of the dead-time generator. Figure 56-9: Complementary Output Waveforms Output waveform OCx CPOLx = 0 Output waveform DTOHx DTHIx = 0 Output waveform DTOLx DTLIx = 0 Output waveform DTOHx DTHIx = 1 Output waveform DTOLx DTLIx = 1 DTHx DTLx DTHx DTLx Output waveform OCx CPOLx = 1 Output waveform DTOHx DTHIx = 0 Output waveform DTOLx DTLIx = 0 Output waveform DTOHx DTHIx = 1 Output waveform DTOLx DTLIx = 1 • PWM Push-Pull Mode DS60001476B-page 2122  2017 Microchip Technology Inc. SAMA5D2 SERIES When a PWM channel is configured in Push-Pull mode, the dead-time generator output is managed alternately on each PWM cycle. The polarity of the PWM line during the idle state of the Push-Pull mode is defined by the DPOLI bit in the PWM Channel Mode Register (PWM_CMRx). The Push-Pull mode can be enabled separately on each channel by writing a one to bit PPM in the PWM Channel Mode Register. Figure 56-10: PWM Push-Pull Mode PWM Channel x Period Odd cycle Even cycle Odd cycle Even cycle Odd cycle Output Waveform OCx PWM_CMRx.CPOL = 0 Push-Pull Mode Disabled PWM_CMRx.PPM = 0 DTHx Output Waveform DTOHx PWM_CMRx.DTHI = 0 DTLx Output Waveform DTOLx PWM_CMRx.DTLI = 1 Push-Pull Mode Enabled PWM_CMRx.PPM = 1 PWM_CMRx.DPOLI = 0 DTHx Output Waveform DTOHx PWM_CMRx.DTHI = 0 Idle State Idle State DTLx Output Waveform DTOLx PWM_CMRx.DTLI = 1 Idle State Idle State Push-Pull Mode Enabled PWM_CMRx.PPM = 1 PWM_CMRx.DPOLI = 1 DTHx Output Waveform DTOHx PWM_CMRx.DTHI = 0 Idle State Idle State DTLx Output Waveform DTOLx PWM_CMRx.DTLI = 1  2017 Microchip Technology Inc. Idle State Idle State DS60001476B-page 2123 SAMA5D2 SERIES Figure 56-11: PWM Push-Pull Waveforms: Left-Aligned Mode Channel x slected clock CHIDx(PWM_SR) CHIDx(PWM_ENA) CHIDx(PWM_DIS) Left Aligned CALG(PWM_CMRx) = 0 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Output Waveforms Period PWM_CMRx Software configurations CPOL = 0 DPOLI = 0 DTE = 0 PPM = 1 CPOL = 1 DPOLI = 0 DTE = 0 PPM = 1 DTHI = 0 DTLI = 0 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 0 DTHI = 1 DTLI = 0 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 0 DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx PWM_CMRx Software configurations CPOL = 0 DPOLI = 1 DTE = 0 PPM = 1 CPOL = 1 DPOLI = 1 DTE = 0 PPM = 1 DTHI = 0 DTLI = 0 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 0 DTHI = 1 DTLI = 0 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 0 DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx DTOHx DS60001476B-page 2124 DTOLx  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-12: PWM Push-Pull Waveforms: Center-Aligned Mode Channel x slected clock CHIDx(PWM_SR) CHIDx(PWM_ENA) CHIDx(PWM_DIS) Left Aligned CALG(PWM_CMRx) = 0 PWM_CCNTx CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) Output Waveforms Period PWM_CMRx Software configurations CPOL = 0 DPOLI = 0 DTE = 0 PPM = 1 CPOL = 1 DPOLI = 0 DTE = 0 PPM = 1 DTHI = 0 DTLI = 0 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 0 DTHI = 1 DTLI = 0 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 0 DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx PWM_CMRx Software configurations CPOL = 0 DPOLI = 1 DTE = 0 PPM = 1 CPOL = 1 DPOLI = 1 DTE = 0 PPM = 1 DTHI = 0 DTLI = 0 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 0 DTHI = 1 DTLI = 0 DTHI = 0 DTLI = 1 DTHI = 1 DTLI = 1 DTHI = 0 DTLI = 0 DTOHx DTOLx DTOHx DTOLx DTOHx DTOLx DTOHx  2017 Microchip Technology Inc. DTOLx DS60001476B-page 2125 SAMA5D2 SERIES The PWM Push-Pull mode can be useful in transformer-based power converters, such as a half-bridge converter. The Push-Pull mode prevents the transformer core from being saturated by any direct current. Figure 56-13: Half-Bridge Converter Application: No Feedback Regulation C1 VDC + D1 PWMxH VIN L + COUT VOUT D2 + PWMxL C2 PWMx outputs PWM Controller PWM Configuration Example 1 PPM (PWM_CMRx) = 1 CPOL (PWM_CMRx) = 0 DPOLI (PWM_CMRx) = 0 PWM Channel x Period Even cycle Odd cycle Even cycle Odd cycle Even cycle VOUT CDTY (PWM_CDTYx) Output Waveform PWMxH DTHI (PWM_CMRx) = 0 DTH (PWM_DTx) = 0 CDTY (PWM_CDTYx) Output Waveform PWMxL DTLI (PWM_CMRx) = 1 DTL (PWM_DTx) = 0 PWM Configuration Example 2 PPM (PWM_CMRx) = 1 CPOL (PWM_CMRx) = 1 DPOLI (PWM_CMRx) = 1 PWM Channel x Period Even cycle Odd cycle Even cycle Odd cycle Even cycle VOUT CDTY (PWM_CDTYx) Output Waveform PWMxH DTHI (PWM_CMRx) = 0 DTH (PWM_DTx) = 0 CDTY (PWM_CDTYx) Output Waveform PWMxL DTLI (PWM_CMRx) = 1 DTL (PWM_DTx) = 0 DS60001476B-page 2126  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-14: Half-Bridge Converter Application: Feedback Regulation + VDC D1 PWMxH C1 L VIN + COUT VOUT D2 + C2 PWMxL PWMx outputs x = [1..2] PWM CONTROLLER PWMEXTRGx x = [1..2] Isolation Error Amplification VREF PWM Configuration PPM (PWM_CMRx) = 1 CPOL (PWM_CMRx) = 1 DPOLI (PWM_CMRx) = 1 MODE (PWM_ETRGx) = 3 PWM Channel x Period Even cycle Odd cycle Even cycle Odd cycle Even cycle VREF VOUT CDTY (PWM_CDTYx) Output Waveform PWMxH DTHI (PWM_CMRx) = 0 DTH (PWM_DTx) = 0 CDTY (PWM_CDTYx) Output Waveform PWMxL DTLI (PWM_CMRx) = 1 DTL (PWM_DTx) = 0  2017 Microchip Technology Inc. DS60001476B-page 2127 SAMA5D2 SERIES 56.6.2.6 Output Override The two complementary outputs DTOHx and DTOLx of the dead-time generator can be forced to a value defined by the software. Figure 56-15: Override Output Selection DTOHx 0 OOOHx OOVHx 1 OSHx DTOLx 0 OOOLx OOVLx 1 OSLx The fields OSHx and OSLx in the PWM Output Selection Register (PWM_OS) allow the outputs of the dead-time generator DTOHx and DTOLx to be overridden by the value defined in the fields OOVHx and OOVLx in the PWM Output Override Value Register (PWM_OOV). The set registers PWM Output Selection Set Register (PWM_OSS) and PWM Output Selection Set Update Register (PWM_OSSUPD) enable the override of the outputs of a channel regardless of other channels. In the same way, the clear registers PWM Output Selection Clear Register (PWM_OSC) and PWM Output Selection Clear Update Register (PWM_OSCUPD) disable the override of the outputs of a channel regardless of other channels. By using buffer registers PWM_OSSUPD and PWM_OSCUPD, the output selection of PWM outputs is done synchronously to the channel counter, at the beginning of the next PWM period. By using registers PWM_OSS and PWM_OSC, the output selection of PWM outputs is done asynchronously to the channel counter, as soon as the register is written. The value of the current output selection can be read in PWM_OS. While overriding PWM outputs, the channel counters continue to run, only the PWM outputs are forced to user defined values. DS60001476B-page 2128  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.2.7 Fault Protection 6 inputs provide fault protection which can force any of the PWM output pairs to a programmable value. This mechanism has priority over output overriding. Figure 56-16: Fault Protection Fault Protection of Channel x 0 Glitch Filter PWMFI0 FIV0 0 = 1 SET FMOD0 OUT 1 CLR Fault Input Management of PWMFI0 Fault 0 Status FS0 FPEx[0] FPE0[0] FFIL0 Write FCLR0 at 1 FPOL0 from fault 0 0 1 FMOD0 From Output Override OOHx 0 PWMHx SYNCx PWMEXTRG1 from ACC 1 0 Glitch Filter 1 1 Recoverable Fault 1 Management TRGIN1 0 RTRG1.TRGSRC PWM_ETRG1.RFEN High Impedance State 1 FPVHx 0 RTRG1.TRGFLT FPZHx 0 Glitch Filter PWMFI1 1 FIV1 0 = 1 SET OUT FMOD1 1 Fault 1 Status FS1 0 Fault protection on PWM channel x from fault 1 CLR Fault Input Management of PWMFI1 FPEx[1] FFIL1 FPOL1 Write FCLR1 at 1 FMOD1 0 FPE0[1] 1 from fault y High Impedance State SYNCx PWMEXTRG2 0 Glitch Filter 1 1 Recoverable Fault 2 Management TRGIN2 0 RTRG2.TRGSRC PWM_ETRG2.RFEN FIV2 1 = 0 FMOD2 FFIL2 FPOL2 1 0 1 PWMLx OOLx From Output Override 1 SET OUT 1 CLR Fault Input Management of PWMFI2 FPZLx RTRG2.TRGFLT 0 Glitch Filter PWMFI2 FPVLx Write FCLR2 at 1 Fault 2 Status FS2 0 FPEx[2] FMOD2 0 from fault 2 0 FPE0[2] 1 SYNCx 0 Glitch Filter PWMFI3 Fault Input Management of PWMFI3 1 FIV3 = 0 FMOD3 SET OUT 1 CLR Fault 3 Status FS3 FPEx[3] FPE0[3] FFIL3 FPOL3 Write FCLR3 at 1 FMOD3 from fault 3 0 1 SYNCx PWMFIy The polarity level of the fault inputs is configured by the FPOL field in the PWM Fault Mode Register (PWM_FMR). For fault inputs coming from internal peripherals such as ADC or Timer Counter, the polarity level must be FPOL = 1. For fault inputs coming from external GPIO pins the polarity level depends on the user's implementation. The configuration of the Fault Activation mode (FMOD field in PWMC_FMR) depends on the peripheral generating the fault. If the corresponding peripheral does not have “Fault Clear” management, then the FMOD configuration to use must be FMOD = 1, to avoid spurious fault detection. Refer to the corresponding peripheral documentation for details on handling fault generation. Fault inputs may or may not be glitch-filtered depending on the FFIL field in PWM_FMR. When the filter is activated, glitches on fault inputs with a width inferior to the PWM peripheral clock period are rejected. A fault becomes active as soon as its corresponding fault input has a transition to the programmed polarity level. If the corresponding bit FMOD is set to ‘0’ in PWM_FMR, the fault remains active as long as the fault input is at this polarity level. If the corresponding FMOD field is set to ‘1’, the fault remains active until the fault input is no longer at this polarity level and until it is cleared by writing the corresponding bit FCLR in the PWM Fault Clear Register (PWM_FCR). In the PWM Fault Status Register (PWM_FSR), the field FIV indicates the current level of the fault inputs and the field FIS indicates whether a fault is currently active. Each fault can be taken into account or not by the fault protection mechanism in each channel. To be taken into account in the channel x, the fault y must be enabled by the bit FPEx[y] in the PWM Fault Protection Enable registers (PWM_FPE1). However, synchronous channels (see Section 56.6.2.9 “Synchronous Channels”) do not use their own fault enable bits, but those of the channel 0 (bits FPE0[y]). The fault protection on a channel is triggered when this channel is enabled and when any one of the faults that are enabled for this channel is active. It can be triggered even if the PWM peripheral clock is not running but only by a fault input that is not glitch-filtered.  2017 Microchip Technology Inc. DS60001476B-page 2129 SAMA5D2 SERIES When the fault protection is triggered on a channel, the fault protection mechanism resets the counter of this channel and forces the channel outputs to the values defined by the fields FPVHx and FPVLx in the PWM Fault Protection Value Register 1 (PWM_FPV) and fields FPZHx/FPZLx in the PWM Fault Protection Value Register 2, as shown in Table 56-5. The output forcing is made asynchronously to the channel counter. Table 56-5: Forcing Values of PWM Outputs by Fault Protection FPZH/Lx FPVH/Lx Forcing Value of PWMH/Lx 0 0 0 0 1 1 1 – High impedance state (Hi-Z) CAUTION: • To prevent any unexpected activation of the status flag FSy in PWM_FSR, the FMODy bit can be set to ‘1’ only if the FPOLy bit has been previously configured to its final value. • To prevent any unexpected activation of the Fault Protection on the channel x, the bit FPEx[y] can be set to ‘1’ only if the FPOLy bit has been previously configured to its final value. If a comparison unit is enabled (see Section 56.6.3 “PWM Comparison Units”) and if a fault is triggered in the channel 0, then the comparison cannot match. As soon as the fault protection is triggered on a channel, an interrupt (different from the interrupt generated at the end of the PWM period) can be generated but only if it is enabled and not masked. The interrupt is reset by reading the interrupt status register, even if the fault which has caused the trigger of the fault protection is kept active. • Recoverable Fault The PWM provides a Recoverable Fault mode on fault 1 and 2 (see Figure 56-16). The recoverable fault signal is an internal signal generated as soon as an external trigger event occurs (see Section 56.6.5 “PWM External Trigger Mode”). When the fault 1 or 2 is defined as a recoverable fault, the corresponding fault input pin is ignored and bits FFIL1/2, FMOD1/2 and FFIL1/ 2 are not taken into account. The fault 1 is managed as a recoverable fault by the PWMEXTRG1 input trigger when PWM_ETRG1.RFEN = 1, PWM_ENA.CHID1 = 1, and PWM_ETRG1.TRGMODE ≠ 0. The fault 2 is managed as a recoverable fault by the PWMEXTRG2 input trigger when PWM_ETRG2.RFEN = 1, PWM_ENA.CHID2 = 1, and PWM_ETRG2.TRGMODE ≠ 0. Recoverable fault 1 and 2 can be taken into account by all channels by enabling the bit FPEx[1/2] in the PWM Fault Protection Enable registers (PWM_FPEx). However the synchronous channels (see Section 56.6.2.9 “Synchronous Channels”) do not use their own fault enable bits, but those of the channel 0 (bits FPE0[1/2]). When a recoverable fault is triggered (according to the PWM_ETRGx.TRGMODE setting), the PWM counter of the affected channels is not cleared (unlike in the classic fault protection mechanism) but the channel outputs are forced to the values defined by the fields FPVHx and FPVLx in the PWM Fault Protection Value Register 1 (PWM_FPV), as per Table 56-5. The output forcing is made asynchronously to the channel counter and lasts from the recoverable fault occurrence to the end of the next PWM cycle (if the recoverable fault is no longer present) (see Figure 56-17). The recoverable fault does not trigger an interrupt. The Fault Status FSy (with y = 1 or 2) is not reported in the PWM Fault Status Register when the fault y is a recoverable fault. DS60001476B-page 2130  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-17: Recoverable Fault Management PWM Channel y (y = 1 or 2) managed by external trigger External Trigger Mode: PWM_ETRG1.MODE = 3 (Cycle-by-Cycle Duty Mode) Recoverable management would have the same behavior with another external trigger mode CNT(PWM_CCNTy) CPRD(PWM_CPRDy) CDTY(PWM_CDTYy) 0 PWMEXTRGy Event TRG_EDGE(PWM_RTRGy) = 1 PWMHy PWM Channel x affected by the fault y: PWM_FPEx[y] = 1 CNT(PWM_CCNTx) CPRD(PWM_CPRDx) CDTY(PWM_CDTYx) 0 1 PWM cycle 1 PWM cycle Recoverable Fault for CHx (Internal signal) OOOHx PWMHx PWM Channel z affected by the fault y: PWM_FPEz[y] = 1 CNT(PWM_CCNTz) CPRD(PWM_CPRDz) CDTY(PWM_CDTYz) 0 1 PWM cycle 1 PWM cycle 1 PWM cycle Recoverable Fault for CHz (Internal signal) OOOHz PWMHz PWM_FSR.FSy  2017 Microchip Technology Inc. DS60001476B-page 2131 SAMA5D2 SERIES 56.6.2.8 Spread Spectrum Counter The PWM macrocell includes a spread spectrum counter allowing the generation of a constantly varying duty cycle on the output PWM waveform (only for the channel 0). This feature may be useful to minimize electromagnetic interference or to reduce the acoustic noise of a PWM driven motor. This is achieved by varying the effective period in a range defined by a spread spectrum value which is programmed by the field SPRD in the PWM Spread Spectrum Register (PWM_SSPR). The effective period of the output waveform is the value of the spread spectrum counter added to the programmed waveform period CPRD in the PWM Channel Period Register (PWM_CPRD0). It will cause the effective period to vary from CPRD-SPRD to CPRD+SPRD. This leads to a constantly varying duty cycle on the PWM output waveform because the duty cycle value programmed is unchanged. The value of the spread spectrum counter can change in two ways depending on the bit SPRDM in PWM_SSPR. If SPRDM = 0, the Triangular mode is selected. The spread spectrum counter starts to count from -SPRD when the channel 0 is enabled or after reset and counts upwards at each period of the channel counter. When it reaches SPRD, it restarts to count from -SPRD again. If SPRDM = 1, the Random mode is selected. A new random value is assigned to the spread spectrum counter at each period of the channel counter. This random value is between -SPRD and +SPRD and is uniformly distributed. Figure 56-18: Spread Spectrum Counter Max value of the channel counter CPRD+SPRD Period Value: CPRD Variation of the effective period CPRD-SPRD Duty Cycle Value: CDTY 0x0 56.6.2.9 Synchronous Channels Some channels can be linked together as synchronous channels. They have the same source clock, the same period, the same alignment and are started together. In this way, their counters are synchronized together. The synchronous channels are defined by the SYNCx bits in the PWM Sync Channels Mode Register (PWM_SCM). Only one group of synchronous channels is allowed. When a channel is defined as a synchronous channel, the channel 0 is also automatically defined as a synchronous channel. This is because the channel 0 counter configuration is used by all the synchronous channels. If a channel x is defined as a synchronous channel, the fields/bits for the channel 0 are used instead of those of channel x: • CPRE in PWM_CMR0 instead of CPRE in PWM_CMRx (same source clock) • CPRD in PWM_CPRD0 instead of CPRD in PWM_CPRDx (same period) • CALG in PWM_CMR0 instead of CALG in PWM_CMRx (same alignment) Modifying the fields CPRE, CPRD and CALG of for channels with index greater than 0 has no effect on output waveforms. Because counters of synchronous channels must start at the same time, they are all enabled together by enabling the channel 0 (by the CHID0 bit in PWM_ENA register). In the same way, they are all disabled together by disabling channel 0 (by the CHID0 bit in PWM_DIS register). However, a synchronous channel x different from channel 0 can be enabled or disabled independently from others (by the CHIDx bit in PWM_ENA and PWM_DIS registers). DS60001476B-page 2132  2017 Microchip Technology Inc. SAMA5D2 SERIES Defining a channel as a synchronous channel while it is an asynchronous channel (by writing the bit SYNCx to ‘1’ while it was at ‘0’) is allowed only if the channel is disabled at this time (CHIDx = 0 in PWM_SR). In the same way, defining a channel as an asynchronous channel while it is a synchronous channel (by writing the SYNCx bit to ‘0’ while it was ‘1’) is allowed only if the channel is disabled at this time. The UPDM field (Update Mode) in the PWM_SCM register selects one of the three methods to update the registers of the synchronous channels: • Method 1 (UPDM = 0): The period value, the duty-cycle values and the dead-time values must be written by the processor in their respective update registers (respectively PWM_CPRDUPDx, PWM_CDTYUPDx and PWM_DTUPDx).The update is triggered at the next PWM period as soon as the bit UPDULOCK in the PWM Sync Channels Update Control Register (PWM_SCUC) is set to ‘1’ (see “Method 1: Manual write of duty-cycle values and manual trigger of the update” ). • Method 2 (UPDM = 1): The period value, the duty-cycle values, the dead-time values and the update period value must be written by the processor in their respective update registers (respectively PWM_CPRDUPDx, PWM_CDTYUPDx and PWM_DTUPD). The update of the period value and of the dead-time values is triggered at the next PWM period as soon as the bit UPDULOCK in the PWM_SCUC register is set to ‘1’. The update of the duty-cycle values and the update period value is triggered automatically after an update period defined by the field UPR in the PWM Sync Channels Update Period Register (PWM_SCUP) (see “Method 2: Manual write of duty-cycle values and automatic trigger of the update” ). • Method 3 (UPDM = 2): Same as Method 2 apart from the fact that the duty-cycle values of ALL synchronous channels are written by the DMA Controller (see “Method 3: Automatic write of duty-cycle values and automatic trigger of the update” ). The user can choose to synchronize the DMA Controller transfer request with a comparison match (see Section 56.6.3 “PWM Comparison Units”), by the fields PTRM and PTRCS in the PWM_SCM register. The DMA destination address must be configured to access only the PWM DMA Register (PWM_DMAR). The DMA buffer data structure must consist of sequentially repeated duty cycles. The number of duty cycles in each sequence corresponds to the number of synchronized channels. Duty cycles in each sequence must be ordered from the lowest to the highest channel index. The size of the duty cycle is 16 bits. Table 56-6: Summary of the Update of Registers of Synchronous Channels Register UPDM = 0 UPDM = 2 Write by the processor Period Value (PWM_CPRDUPDx) Update is triggered at the next PWM period as soon as the bit UPDULOCK is set to ‘1’ Write by the processor Dead-Time Values (PWM_DTUPDx) Update is triggered at the next PWM period as soon as the bit UPDULOCK is set to ‘1’ Write by the processor Duty-Cycle Values (PWM_CDTYUPDx) UPDM = 1 Write by the processor Write by the DMA Controller Update is triggered at the next PWM period as soon as the bit UPDULOCK is set to ‘1’ Update is triggered at the next PWM period as soon as the update period counter has reached the value UPR Not applicable Write by the processor Not applicable Update is triggered at the next PWM period as soon as the update period counter has reached the value UPR Update Period Value (PWM_SCUPUPD) • Method 1: Manual write of duty-cycle values and manual trigger of the update In this mode, the update of the period value, the duty-cycle values and the dead-time values must be done by writing in their respective update registers with the processor (respectively PWM_CPRDUPDx, PWM_CDTYUPDx and PWM_DTUPDx). To trigger the update, the user must use the bit UPDULOCK in the PWM_SCUC register which allows to update synchronously (at the same PWM period) the synchronous channels: • If the bit UPDULOCK is set to ‘1’, the update is done at the next PWM period of the synchronous channels. • If the UPDULOCK bit is not set to ‘1’, the update is locked and cannot be performed. After writing the UPDULOCK bit to ‘1’, it is held at this value until the update occurs, then it is read 0. Sequence for Method 1: 1. 2. 3. 4. Select the manual write of duty-cycle values and the manual update by setting the UPDM field to ‘0’ in the PWM_SCM register. Define the synchronous channels by the SYNCx bits in the PWM_SCM register. Enable the synchronous channels by writing CHID0 in the PWM_ENA register. If an update of the period value and/or the duty-cycle values and/or the dead-time values is required, write registers that need to be updated (PWM_CPRDUPDx, PWM_CDTYUPDx and PWM_DTUPDx).  2017 Microchip Technology Inc. DS60001476B-page 2133 SAMA5D2 SERIES 5. 6. Set UPDULOCK to ‘1’ in PWM_SCUC. The update of the registers will occur at the beginning of the next PWM period. When the UPDULOCK bit is reset, go to Step 4. for new values. Figure 56-19: Method 1 (UPDM = 0) CCNT0 CDTYUPD 0x20 0x40 0x20 0x40 0x60 UPDULOCK CDTY 0x60 • Method 2: Manual write of duty-cycle values and automatic trigger of the update In this mode, the update of the period value, the duty-cycle values, the dead-time values and the update period value must be done by writing in their respective update registers with the processor (respectively PWM_CPRDUPDx, PWM_CDTYUPDx, PWM_DTUPDx and PWM_SCUPUPD). To trigger the update of the period value and the dead-time values, the user must use the bit UPDULOCK in the PWM_SCUC register, which updates synchronously (at the same PWM period) the synchronous channels: • If the bit UPDULOCK is set to ‘1’, the update is done at the next PWM period of the synchronous channels. • If the UPDULOCK bit is not set to ‘1’, the update is locked and cannot be performed. After writing the UPDULOCK bit to ‘1’, it is held at this value until the update occurs, then it is read 0. The update of the duty-cycle values and the update period is triggered automatically after an update period. To configure the automatic update, the user must define a value for the update period by the UPR field in the PWM_SCUP register. The PWM controller waits UPR+1 period of synchronous channels before updating automatically the duty values and the update period value. The status of the duty-cycle value write is reported in the PWM Interrupt Status Register 2 (PWM_ISR2) by the following flags: • WRDY: this flag is set to ‘1’ when the PWM Controller is ready to receive new duty-cycle values and a new update period value. It is reset to ‘0’ when the PWM_ISR2 register is read. Depending on the interrupt mask in the PWM Interrupt Mask Register 2 (PWM_IMR2), an interrupt can be generated by these flags. Sequence for Method 2: 1. 2. 3. 4. 5. Select the manual write of duty-cycle values and the automatic update by setting the field UPDM to ‘1’ in the PWM_SCM register Define the synchronous channels by the bits SYNCx in the PWM_SCM register. Define the update period by the field UPR in the PWM_SCUP register. Enable the synchronous channels by writing CHID0 in the PWM_ENA register. If an update of the period value and/or of the dead-time values is required, write registers that need to be updated (PWM_CPRDUPDx, PWM_DTUPDx), else go to Step 8. 6. Set UPDULOCK to ‘1’ in PWM_SCUC. 7. The update of these registers will occur at the beginning of the next PWM period. At this moment the bit UPDULOCK is reset, go to Step 5. for new values. 8. If an update of the duty-cycle values and/or the update period is required, check first that write of new update values is possible by polling the flag WRDY (or by waiting for the corresponding interrupt) in PWM_ISR2. 9. Write registers that need to be updated (PWM_CDTYUPDx, PWM_SCUPUPD). 10. The update of these registers will occur at the next PWM period of the synchronous channels when the Update Period is elapsed. Go to Step 8. for new values. DS60001476B-page 2134  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-20: Method 2 (UPDM = 1) CCNT0 CDTYUPD UPRUPD 0x1 UPR 0x1 UPRCNT 0x0 CDTY 0x60 0x40 0x20 0x3 0x3 0x1 0x20 0x0 0x1 0x0 0x40 0x1 0x0 0x1 0x2 0x3 0x0 0x1 0x2 0x60 WRDY  2017 Microchip Technology Inc. DS60001476B-page 2135 SAMA5D2 SERIES • Method 3: Automatic write of duty-cycle values and automatic trigger of the update In this mode, the update of the duty cycle values is made automatically by the DMA Controller. The update of the period value, the deadtime values and the update period value must be done by writing in their respective update registers with the processor (respectively PWM_CPRDUPDx, PWM_DTUPDx and PWM_SCUPUPD). To trigger the update of the period value and the dead-time values, the user must use the bit UPDULOCK which allows to update synchronously (at the same PWM period) the synchronous channels: • If the bit UPDULOCK is set to ‘1’, the update is done at the next PWM period of the synchronous channels. • If the UPDULOCK bit is not set to ‘1’, the update is locked and cannot be performed. After writing the UPDULOCK bit to ‘1’, it is held at this value until the update occurs, then it is read 0. The update of the duty-cycle values and the update period value is triggered automatically after an update period. To configure the automatic update, the user must define a value for the Update Period by the field UPR in the PWM_SCUP register. The PWM controller waits UPR+1 periods of synchronous channels before updating automatically the duty values and the update period value. Using the DMA Controller removes processor overhead by reducing its intervention during the transfer. This significantly reduces the number of clock cycles required for a data transfer, which improves microcontroller performance. The DMA Controller must write the duty-cycle values in the synchronous channels index order. For example if the channels 0, 1 and 3 are synchronous channels, the DMA Controller must write the duty-cycle of the channel 0 first, then the duty-cycle of the channel 1, and finally the duty-cycle of the channel 3. The status of the DMA Controller transfer is reported in PWM_ISR2 by the following flags: • WRDY: this flag is set to ‘1’ when the PWM Controller is ready to receive new duty-cycle values and a new update period value. It is reset to ‘0’ when PWM_ISR2 is read. The user can choose to synchronize the WRDY flag and the DMA Controller transfer request with a comparison match (see Section 56.6.3 “PWM Comparison Units”), by the fields PTRM and PTRCS in the PWM_SCM register. • UNRE: this flag is set to ‘1’ when the update period defined by the UPR field has elapsed while the whole data has not been written by the DMA Controller. It is reset to ‘0’ when PWM_ISR2 is read. Depending on the interrupt mask in PWM_IMR2, an interrupt can be generated by these flags. Sequence for Method 3: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Select the automatic write of duty-cycle values and automatic update by setting the field UPDM to 2 in the PWM_SCM register. Define the synchronous channels by the bits SYNCx in the PWM_SCM register. Define the update period by the field UPR in the PWM_SCUP register. Define when the WRDY flag and the corresponding DMA Controller transfer request must be set in the update period by the PTRM bit and the PTRCS field in the PWM_SCM register (at the end of the update period or when a comparison matches). Define the DMA Controller transfer settings for the duty-cycle values and enable it in the DMA Controller registers Enable the synchronous channels by writing CHID0 in the PWM_ENA register. If an update of the period value and/or of the dead-time values is required, write registers that need to be updated (PWM_CPRDUPDx, PWM_DTUPDx), else go to Step 10. Set UPDULOCK to ‘1’ in PWM_SCUC. The update of these registers will occur at the beginning of the next PWM period. At this moment the bit UPDULOCK is reset, go to Step 7. for new values. If an update of the update period value is required, check first that write of a new update value is possible by polling the flag WRDY (or by waiting for the corresponding interrupt) in PWM_ISR2, else go to Step 13. Write the register that needs to be updated (PWM_SCUPUPD). The update of this register will occur at the next PWM period of the synchronous channels when the Update Period is elapsed. Go to Step 10. for new values. Wait for the DMA status flag indicating that the buffer transfer is complete. If the transfer has ended, define a new DMA transfer for new duty-cycle values. Go to Step 5. DS60001476B-page 2136  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-21: Method 3 (UPDM = 2 and PTRM = 0) CCNT0 CDTYUPD UPRUPD 0x1 UPR 0x1 UPRCNT 0x0 CDTY 0x60 0x40 0x20 0x80 0xB0 0xA0 0x3 0x3 0x1 0x0 0x1 0x0 0x1 0x1 0x2 0x3 0x0 0x1 0x80 0x60 0x40 0x20 0x0 0x2 0xA0 transfer request WRDY Figure 56-22: Method 3 (UPDM = 2 and PTRM = 1 and PTRCS = 0) CCNT0 CDTYUPD 0x20 UPRUPD 0x1 UPR 0x1 UPRCNT 0x0 CDTY 0x20 0x60 0x40 0x80 0xB0 0xA0 0x3 0x3 0x1 0x0 0x40 0x1 0x0 0x60 0x1 0x0 0x80 0x1 0x2 0x3 0x0 0x1 0x2 0xA0 CMP0 match transfer request WRDY  2017 Microchip Technology Inc. DS60001476B-page 2137 SAMA5D2 SERIES 56.6.2.10 Update Time for Double-Buffering Registers All channels integrate a double-buffering system in order to prevent an unexpected output waveform while modifying the period, the spread spectrum value, the polarity, the duty-cycle, the dead-times, the output override, and the synchronous channels update period. This double-buffering system comprises the following update registers: • • • • • • • • PWM Sync Channels Update Period Update Register PWM Output Selection Set Update Register PWM Output Selection Clear Update Register PWM Spread Spectrum Update Register PWM Channel Duty Cycle Update Register PWM Channel Period Update Register PWM Channel Dead Time Update Register PWM Channel Mode Update Register When one of these update registers is written to, the write is stored, but the values are updated only at the next PWM period border. In Left-aligned mode (CALG = 0), the update occurs when the channel counter reaches the period value CPRD. In Center-aligned mode, the update occurs when the channel counter value is decremented and reaches the 0 value. In Center-aligned mode, it is possible to trigger the update of the polarity and the duty-cycle at the next half period border. This mode concerns the following update registers: • PWM Channel Duty Cycle Update Register • PWM Channel Mode Update Register The update occurs at the first half period following the write of the update register (either when the channel counter value is incrementing and reaches the period value CPRD, or when the channel counter value is decrementing and reaches the 0 value). To activate this mode, the user must write a one to the bit UPDS in the PWM Channel Mode Register. 56.6.3 PWM Comparison Units The PWM provides 1 independent comparison units able to compare a programmed value with the current value of the channel 0 counter (which is the channel counter of all synchronous channels, Section 56.6.2.9 “Synchronous Channels”). These comparisons are intended to generate pulses on the event lines (used to synchronize ADC, see Section 56.6.4 “PWM Event Lines”), to generate software interrupts and to trigger DMA Controller transfer requests for the synchronous channels (see “Method 3: Automatic write of duty-cycle values and automatic trigger of the update” ). Figure 56-23: Comparison Unit Block Diagram CEN [PWM_CMPMx] fault on channel 0 CV [PWM_CMPVx] CNT [PWM_CCNT0] Comparison x = 1 CNT [PWM_CCNT0] is decrementing = 0 1 CVM [PWM_CMPVx] CALG [PWM_CMR0] CPRCNT [PWM_CMPMx] CTR [PWM_CMPMx] DS60001476B-page 2138 =  2017 Microchip Technology Inc. SAMA5D2 SERIES The comparison x matches when it is enabled by the bit CEN in the PWM Comparison x Mode Register (PWM_CMPMx for the comparison x) and when the counter of the channel 0 reaches the comparison value defined by the field CV in PWM Comparison x Value Register (PWM_CMPVx for the comparison x). If the counter of the channel 0 is center-aligned (CALG = 1 in PWM Channel Mode Register), the bit CVM in PWM_CMPVx defines if the comparison is made when the counter is counting up or counting down (in Left-alignment mode CALG = 0, this bit is useless). If a fault is active on the channel 0, the comparison is disabled and cannot match (see Section 56.6.2.7 “Fault Protection”). The user can define the periodicity of the comparison x by the fields CTR and CPR in PWM_CMPMx. The comparison is performed periodically once every CPR+1 periods of the counter of the channel 0, when the value of the comparison period counter CPRCNT in PWM_CMPMx reaches the value defined by CTR. CPR is the maximum value of the comparison period counter CPRCNT. If CPR = CTR = 0, the comparison is performed at each period of the counter of the channel 0. The comparison x configuration can be modified while the channel 0 is enabled by using the PWM Comparison x Mode Update Register (PWM_CMPMUPDx registers for the comparison x). In the same way, the comparison x value can be modified while the channel 0 is enabled by using the PWM Comparison x Value Update Register (PWM_CMPVUPDx registers for the comparison x). The update of the comparison x configuration and the comparison x value is triggered periodically after the comparison x update period. It is defined by the field CUPR in PWM_CMPMx. The comparison unit has an update period counter independent from the period counter to trigger this update. When the value of the comparison update period counter CUPRCNT (in PWM_CMPMx) reaches the value defined by CUPR, the update is triggered. The comparison x update period CUPR itself can be updated while the channel 0 is enabled by using the PWM_CMPMUPDx register. CAUTION: The write of PWM_CMPVUPDx must be followed by a write of PWM_CMPMUPDx. The comparison match and the comparison update can be source of an interrupt, but only if it is enabled and not masked. These interrupts can be enabled by the PWM Interrupt Enable Register 2 and disabled by the PWM Interrupt Disable Register 2. The comparison match interrupt and the comparison update interrupt are reset by reading the PWM Interrupt Status Register 2.  2017 Microchip Technology Inc. DS60001476B-page 2139 SAMA5D2 SERIES Figure 56-24: Comparison Waveform CCNT0 CVUPD 0x6 0x6 0x2 CVMVUPD CTRUPD 0x1 0x2 CPRUPD 0x1 0x3 CUPRUPD 0x3 0x2 CV 0x6 0x2 CTR 0x1 0x2 CPR 0x1 0x3 CUPR 0x3 0x2 CUPRCNT 0x0 0x1 0x2 0x3 0x0 0x1 0x2 0x0 0x1 0x2 0x0 0x1 CPRCNT 0x0 0x1 0x0 0x1 0x0 0x1 0x2 0x3 0x0 0x1 0x2 0x3 0x6 CVM Comparison Update CMPU Comparison Match CMPM 56.6.4 PWM Event Lines The PWM provides 2 independent event lines intended to trigger actions in other peripherals (e.g., for the Analog-to-Digital Converter (ADC)). A pulse (one cycle of the peripheral clock) is generated on an event line, when at least one of the selected comparisons is matching. The comparisons can be selected or unselected independently by the CSEL bits in the PWM Event Line x Register (PWM_ELMRx for the Event Line x). An example of event generation is provided in Figure 56-26. DS60001476B-page 2140  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-25: Event Line Block Diagram CMPM0 (PWM_ISR2) CSEL0 (PWM_ELMRx) CMPM1 (PWM_ISR2) CSEL1 (PWM_ELMRx) CMPM2 (PWM_ISR2) CSEL2 (PWM_ELMRx) Pulse Generator Event Line x CMPM7 (PWM_ISR2) CSEL7 (PWM_ELMRx) Figure 56-26: Event Line Generation Waveform (Example) PWM_CCNTx CPRD(PWM_CPRD0) CV (PWM_CMPV1) CDTY(PWM_CDTY2) CDTY(PWM_CDTY1) CDTY(PWM_CDTY0) CV (PWM_CMPV0) Waveform OC0 Waveform OC1 Waveform OC2 Comparison Unit 0 Output PWM_CMPM0.CEN = 1 Comparison Unit 1 Output PWM_CMPM0.CEN = 1 Event Line 0 (trigger event for ADC) PWM_ELMR0.CSEL0 = 1 PWM_ELMR0.CSEL1 = 1 configurable delay PWM_CMPV0.CV configurable delay PWM_CMPV1.CV ADC conversion 56.6.5 ADC conversion PWM External Trigger Mode The PWM channels 1 and 2 can be configured to use an external trigger for generating specific PWM signals. The external trigger source can be selected through the bit TRGSRC of the PWM External Trigger Register (see Table 56-7). Table 56-7: Channel External Event Source Selection Trigger Source Selection Trigger Source PWM_ETRG1.TRGSRC = 0 From PWMEXTRG1 input PWM_ETRG1.TRGSRC = 1 From Analog Comparator Controller PWM_ETRG2.TRGSRC = 0 From PWMEXTRG2 input PWM_ETRG2.TRGSRC = 1 From Analog Comparator Controller 1 2  2017 Microchip Technology Inc. DS60001476B-page 2141 SAMA5D2 SERIES Each external trigger source can be filtered by writing a one to the TRGFILT bit in the corresponding PWM External Trigger Register (PWM_ETRGx). Each time an external trigger event is detected, the corresponding PWM channel counter value is stored in the MAXCNT field of the PWM_ETRGx register if it is greater than the previously stored value. Reading the PWM_ETRGx register will clear the MAXCNT value. Three different modes are available for channels 1 and 2 depending on the value of the TRGMODE field of the PWM_ETRGx register: • TRGMODE = 1: External PWM Reset Mode (see Section 56.6.5.1 “External PWM Reset Mode”) • TRGMODE = 2: External PWM Start Mode (see Section 56.6.5.2 “External PWM Start Mode”) • TRGMODE = 3: Cycle-By-Cycle Duty Mode (see Section 56.6.5.3 “Cycle-By-Cycle Duty Mode”) This feature is disabled when TRGMODE = 0. This feature should only be enabled if the corresponding channel is left-aligned (CALG = 0 in PWM Channel Mode Register of channel 1 or 2) and not managed as a synchronous channel (SYNCx = 0 in PWM Sync Channels Mode Register where x = 1 or 2). Programming the channel to be center-aligned or synchronous while TRGMODE is not 0 could lead to unexpected behavior. 56.6.5.1 External PWM Reset Mode External PWM Reset mode is selected by programming TRGMODE = 1 in the PWM_ETRGx register. In this mode, when an edge is detected on the PWMEXTRGx input, the internal PWM counter is cleared and a new PWM cycle is restarted. The edge polarity can be selected by programming the TRGEDGE bit in the PWM_ETRGx register. If no trigger event is detected when the internal channel counter has reached the CPRD value in the PWM Channel Period Register, the internal counter is cleared and a new PWM cycle starts. Note that this mode does not guarantee a constant tON or tOFF time. Figure 56-27: External PWM Reset Mode CNT(PWM_CCNTx) Channel x = [1,2] CPRD(PWM_CPRDx) Channel x = [1,2] tOFF Area CDTY(PWM_CDTYx) Channel x = [1,2] tON Area 0 TRGINx Event TRGEDGE(PWM_ETRGx) = 1 x = [1,2] TRGINx Event TRGEDGE(PWM_ETRGx) = 0 x = [1,2] tON tOFF Output Waveform OCx CPOL(PWM_CMRx) = 1 x = [1,2] Output Waveform OCx CPOL(PWM_CMRx) = 0 x = [1,2] DS60001476B-page 2142  2017 Microchip Technology Inc. SAMA5D2 SERIES • Application Example The external PWM Reset mode can be used in power factor correction applications. In the example below, the external trigger input is the PWMEXTRG1 (therefore the PWM channel used for regulation is the channel 1). The PWM channel 1 period (CPRD in the PWM Channel Period Register of the channel 1) must be programmed so that the TRGIN1 event always triggers before the PWM channel 1 period elapses. In Figure 56-28, an external circuit (not shown) is required to sense the inductor current IL. The internal PWM counter of the channel 1 is cleared when the inductor current falls below a specific threshold (IREF). This starts a new PWM period and increases the inductor current. Figure 56-28: External PWM Reset Mode: Power Factor Correction Application L D IL + VIN VAC CIN COUT VOUT PWMH1 VIN IL IREF Time TRGIN1 TRGEDGE(PWM_ETRG1) = 1 PWMH1  2017 Microchip Technology Inc. DS60001476B-page 2143 SAMA5D2 SERIES 56.6.5.2 External PWM Start Mode External PWM Start mode is selected by programming TRGMODE = 2 in the PWM_ETRGx register. In this mode, the internal PWM counter can only be reset once it has reached the CPRD value in the PWM Channel Period Register and when the correct level is detected on the corresponding external trigger input. Both conditions have to be met to start a new PWM period. The active detection level is defined by the bit TRGEDGE of the PWM_ETRGx register. Note that this mode guarantees a constant tON time and a minimum tOFF time. Figure 56-29: External PWM Start Mode CNT(PWM_CCNTx) Channel x = [1,2] CPRD(PWM_CPRDx) Channel x = [1,2] tOFF Area CDTY(PWM_CDTYx) Channel x = [1,2] tON Area 0 TRGINx Event TRGEDGE(PWM_ETRGx) = 1 x = [1,2] TRGINx Event TRGEDGE(PWM_ETRGx) = 0 x = [1,2] Minimum tOFF tON tOFF Minimum tOFF tON tOFF Minimum tOFF tON tOFF Output Waveform OCx CPOL(PWM_CMRx) = 1 x = [1,2] Output Waveform OCx CPOL(PWM_CMRx) = 0 x = [1,2] • Application Example The external PWM Start mode generates a modulated frequency PWM signal with a constant active level duration (tON) and a minimum inactive level duration (minimum tOFF). The tON time is defined by the CDTY value in the PWM Channel Duty Cycle Register. The minimum tOFF time is defined by CDTY - CPRD (PWM Channel Period Register). This mode can be useful in Buck DC/DC Converter applications. When the output voltage VOUT is above a specific threshold (Vref), the PWM inactive level is maintained as long as VOUT remains above this threshold. If VOUT is below this specific threshold, this mode guarantees a minimum tOFF time required for MOSFET driving (see Figure 56-30). DS60001476B-page 2144  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-30: External PWM Start Mode: Buck DC/DC Converter L IL PWMH1 VDC VIN CIN + D COUT + VOUT switch to high load VOUT VREF Time TRGIN1 TRGEDGE(PWM_ETRG1) = 0 PWMH1 Constant tON  2017 Microchip Technology Inc. tOFF Minimum tOFF DS60001476B-page 2145 SAMA5D2 SERIES 56.6.5.3 Cycle-By-Cycle Duty Mode • Description Cycle-by-cycle duty mode is selected by programming TRGMODE = 3 in PWM_ETRGx. In this mode, the PWM frequency is constant and is defined by the CPRD value in the PWM Channel Period Register. An external trigger event has no effect on the PWM output if it occurs while the internal PWM counter value is above the CDTY value of the PWM Channel Duty Cycle Register. If the internal PWM counter value is below the value of CDTY of the PWM Channel Duty Cycle Register, an external trigger event makes the PWM output inactive. The external trigger event can be detected on rising or falling edge according to the TRGEDGE bit in PWM_ETRGx. Figure 56-31: Cycle-By-Cycle Duty Mode CNT(PWM_CCNTx) Channel x = [1,2] CPRD(PWM_CPRDx) Channel x = [1,2] CDTY(PWM_CDTYx) Channel x = [1,2] 0 TRGINx Event TRGEDGE(PWM_ETRGx) = 1 x = [1,2] TRGINx Event TRGEDGE(PWM_ETRGx) = 0 x = [1,2] Output Waveform OCx CPOL(PWM_CMRx) = 1 x = [1,2] Output Waveform OCx CPOL(PWM_CMRx) = 0 x = [1,2] • Application Example Figure 56-32 illustrates an application example of the Cycle-by-cycle Duty mode. In an LED string control circuit, Cycle-by-cycle Duty mode can be used to automatically limit the current in the LED string. DS60001476B-page 2146  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 56-32: Cycle-By-Cycle Duty Mode: LED String Control L D IL VDC VIN + CIN PWMH0 L + COUT VOUT PWMH1 ILED RSHUNT ILED IREF Time TRGIN1 TRGEDGE(PWM_ETRG1) = 1 PWMH1  2017 Microchip Technology Inc. DS60001476B-page 2147 SAMA5D2 SERIES 56.6.5.4 Leading-Edge Blanking (LEB) PWM channels 1 and 2 support leading-edge blanking. Leading-edge blanking masks the external trigger input when a transient occurs on the corresponding PWM output. It masks potential spurious external events due to power transistor switching. The blanking delay on each external trigger input is configured by programming the LEBDELAYx in the PWM Leading-Edge Blanking Register. The LEB can be enabled on both the rising and the falling edges for the PWMH and PWML outputs through the bits PWMLFEN, PWMLREN, PWMHFEN, PWMHREN. Any event on the PWMEXTRGx input which occurs during the blanking time is ignored. Figure 56-33: Leading-Edge Blanking Switching Noise Analog Power Signal TRGINx input x = [1,2] Delay Delay Delay Delay Blanking signal on TRGINx x = [1,2] Blanked trigger event x x = [1,2] PWMx Output Waveform x = [1,2] DS60001476B-page 2148  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.6 56.6.6.1 PWM Controller Operations Initialization Before enabling the channels, they must be configured by the software application as described below: • • • • • • • • • • • • • • • • • • • Unlock User Interface by writing the WPCMD field in PWM_WPCR. Configuration of the clock generator (DIVA, PREA, DIVB, PREB in the PWM_CLK register if required). Selection of the clock for each channel (CPRE field in PWM_CMRx) Configuration of the waveform alignment for each channel (CALG field in PWM_CMRx) Selection of the counter event selection (if CALG = 1) for each channel (CES field in PWM_CMRx) Configuration of the output waveform polarity for each channel (CPOL bit in PWM_CMRx) Configuration of the period for each channel (CPRD in the PWM_CPRDx register). Writing in PWM_CPRDx register is possible while the channel is disabled. After validation of the channel, the user must use PWM_CPRDUPDx register to update PWM_CPRDx as explained below. Configuration of the duty-cycle for each channel (CDTY in the PWM_CDTYx register). Writing in PWM_CDTYx register is possible while the channel is disabled. After validation of the channel, the user must use PWM_CDTYUPDx register to update PWM_CDTYx as explained below. Configuration of the dead-time generator for each channel (DTH and DTL in PWM_DTx) if enabled (DTE bit in PWM_CMRx). Writing in the PWM_DTx register is possible while the channel is disabled. After validation of the channel, the user must use PWM_DTUPDx register to update PWM_DTx Selection of the synchronous channels (SYNCx in the PWM_SCM register) Selection of the moment when the WRDY flag and the corresponding DMA Controller transfer request are set (PTRM and PTRCS in the PWM_SCM register) Configuration of the Update mode (UPDM in PWM_SCM register) Configuration of the update period (UPR in PWM_SCUP register) if needed Configuration of the comparisons (PWM_CMPVx and PWM_CMPMx) Configuration of the event lines (PWM_ELMRx) Configuration of the fault inputs polarity (FPOL in PWM_FMR) Configuration of the fault protection (FMOD and FFIL in PWM_FMR, PWM_FPV and PWM_FPE1) Enable of the interrupts (writing CHIDx and FCHIDx in PWM_IER1, and writing WRDY, UNRE, CMPMx and CMPUx in PWM_IER2) Enable of the PWM channels (writing CHIDx in the PWM_ENA register) 56.6.6.2 Source Clock Selection Criteria The large number of source clocks can make selection difficult. The relationship between the value in the PWM Channel Period Register (PWM_CPRDx) and the PWM Channel Duty Cycle Register (PWM_CDTYx) helps the user select the appropriate clock. 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 PWM_CPRDx, the greater the PWM accuracy. For example, if the user sets 15 (in decimal) in PWM_CPRDx, the user is able to set a value from between 1 up to 14 in PWM_CDTYx. The resulting duty-cycle quantum cannot be lower than 1/15 of the PWM period. 56.6.6.3 Changing the Duty-Cycle, the Period and the Dead-Times It is possible to modulate the output waveform duty-cycle, period and dead-times. To prevent unexpected output waveform, the user must use the PWM Channel Duty Cycle Update Register (PWM_CDTYUPDx), the PWM Channel Period Update Register (PWM_CPRDUPDx) and the PWM Channel Dead Time Update Register (PWM_DTUPDx) to change waveform parameters while the channel is still enabled. • If the channel is an asynchronous channel (SYNCx = 0 in PWM Sync Channels Mode Register (PWM_SCM)), these registers hold the new period, duty-cycle and dead-times values until the end of the current PWM period and update the values for the next period. • If the channel is a synchronous channel and update method 0 is selected (SYNCx = 1 and UPDM = 0 in PWM_SCM register), these registers hold the new period, duty-cycle and dead-times values until the bit UPDULOCK is written at ‘1’ (in PWM Sync Channels Update Control Register (PWM_SCUC)) and the end of the current PWM period, then update the values for the next period. • If the channel is a synchronous channel and update method 1 or 2 is selected (SYNCx = 1 and UPDM = 1 or 2 in PWM_SCM register): - registers PWM_CPRDUPDx and PWM_DTUPDx hold the new period and dead-times values until the bit UPDULOCK is written at ‘1’ (in PWM_SCUC) and the end of the current PWM period, then update the values for the next period. - register PWM_CDTYUPDx holds the new duty-cycle value until the end of the update period of synchronous channels (when UPRCNT is equal to UPR in PWM Sync Channels Update Period Register (PWM_SCUP)) and the end of the current PWM period, then updates the value for the next period.  2017 Microchip Technology Inc. DS60001476B-page 2149 SAMA5D2 SERIES Note: If the update registers PWM_CDTYUPDx, PWM_CPRDUPDx and PWM_DTUPDx are written several times between two updates, only the last written value is taken into account. Figure 56-34: Synchronized Period, Duty-Cycle and Dead-Time Update User's Writing User's Writing User's Writing PWM_DTUPDx Value PWM_CPRDUPDx Value PWM_CDTYUPDx Value PWM_DTx PWM_CPRDx PWM_CDTYx - If Asynchronous Channel -> End of PWM period - If Synchronous Channel -> End of PWM period and UPDULOCK = 1 - If Asynchronous Channel -> End of PWM period - If Synchronous Channel - If UPDM = 0 -> End of PWM period and UPDULOCK = 1 - If UPDM = 1 or 2 -> End of PWM period and end of Update Period DS60001476B-page 2150  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.6.4 Changing the Update Period of Synchronous Channels It is possible to change the update period of synchronous channels while they are enabled. See “Method 2: Manual write of duty-cycle values and automatic trigger of the update” and “Method 3: Automatic write of duty-cycle values and automatic trigger of the update” . To prevent an unexpected update of the synchronous channels registers, the user must use the PWM Sync Channels Update Period Update Register (PWM_SCUPUPD) to change the update period of synchronous channels while they are still enabled. This register holds the new value until the end of the update period of synchronous channels (when UPRCNT is equal to UPR in PWM_SCUP) and the end of the current PWM period, then updates the value for the next period. Note 1: If the update register PWM_SCUPUPD is written several times between two updates, only the last written value is taken into account. 2: Changing the update period does make sense only if there is one or more synchronous channels and if the update method 1 or 2 is selected (UPDM = 1 or 2 in PWM Sync Channels Mode Register). Figure 56-35: Synchronized Update of Update Period Value of Synchronous Channels User's Writing PWM_SCUPUPD Value PWM_SCUP End of PWM period and end of update period of synchronous channels 56.6.6.5 Changing the Comparison Value and the Comparison Configuration It is possible to change the comparison values and the comparison configurations while the channel 0 is enabled (see Section 56.6.3 “PWM Comparison Units”). To prevent unexpected comparison match, the user must use the PWM Comparison x Value Update Register (PWM_CMPVUPDx) and the PWM Comparison x Mode Update Register (PWM_CMPMUPDx) to change, respectively, the comparison values and the comparison configurations while the channel 0 is still enabled. These registers hold the new values until the end of the comparison update period (when CUPRCNT is equal to CUPR in PWM Comparison x Mode Register (PWM_CMPMx) and the end of the current PWM period, then update the values for the next period. CAUTION: The write of the register PWM_CMPVUPDx must be followed by a write of the register PWM_CMPMUPDx. Note: If the update registers PWM_CMPVUPDx and PWM_CMPMUPDx are written several times between two updates, only the last written value are taken into account.  2017 Microchip Technology Inc. DS60001476B-page 2151 SAMA5D2 SERIES Figure 56-36: Synchronized Update of Comparison Values and Configurations User's Writing User's Writing PWM_CMPVUPDx Value Comparison value for comparison x PWM_CMPMUPDx Value Comparison configuration for comparison x PWM_CMPVx PWM_CMPMx End of channel0 PWM period and end of comparison update period and and PWM_CMPMx written End of channel0 PWM period and end of comparison update period 56.6.6.6 Interrupt Sources Depending on the interrupt mask in PWM_IMR1 and PWM_IMR2, an interrupt can be generated at the end of the corresponding channel period (CHIDx in the PWM Interrupt Status Register 1 (PWM_ISR1)), after a fault event (FCHIDx in PWM_ISR1), after a comparison match (CMPMx in PWM_ISR2), after a comparison update (CMPUx in PWM_ISR2) or according to the Transfer mode of the synchronous channels (WRDY and UNRE in PWM_ISR2). If the interrupt is generated by the flags CHIDx or FCHIDx, the interrupt remains active until a read operation in PWM_ISR1 occurs. If the interrupt is generated by the flags WRDY or UNRE or CMPMx or CMPUx, the interrupt remains active until a read operation in PWM_ISR2 occurs. A channel interrupt is enabled by setting the corresponding bit in PWM_IER1 and PWM_IER2. A channel interrupt is disabled by setting the corresponding bit in PWM_IDR1 and PWM_IDR2. DS60001476B-page 2152  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.6.7 Register Write Protection To prevent any single software error that may corrupt PWM behavior, the registers listed below can be write-protected by writing the field WPCMD in the PWM Write Protection Control Register (PWM_WPCR). They are divided into six groups: • Register group 0: - PWM Clock Register • Register group 1: - PWM Disable Register • Register group 2: - PWM Sync Channels Mode Register - PWM Channel Mode Register - PWM Stepper Motor Mode Register - PWM Fault Protection Value Register 2 - PWM Leading-Edge Blanking Register - PWM Channel Mode Update Register • Register group 3: - PWM Spread Spectrum Register - PWM Spread Spectrum Update Register - PWM Channel Period Register - PWM Channel Period Update Register • Register group 4: - PWM Channel Dead Time Register - PWM Channel Dead Time Update Register • Register group 5: - PWM Fault Mode Register - PWM Fault Protection Value Register 1 There are two types of write protection: • SW write protection—can be enabled or disabled by software • HW write protection—can be enabled by software but only disabled by a hardware reset of the PWM controller Both types of write protection can be applied independently to a particular register group by means of the WPCMD and WPRGx fields in PWM_WPCR. If at least one type of write protection is active, the register group is write-protected. The value of field WPCMD defines the action to be performed: • 0: Disables SW write protection of the register groups of which the bit WPRGx is at ‘1’ • 1: Enables SW write protection of the register groups of which the bit WPRGx is at ‘1’ • 2: Enables HW write protection of the register groups of which the bit WPRGx is at ‘1’ At any time, the user can determine whether SW or HW write protection is active in a particular register group by the fields WPSWS and WPHWS in the PWM Write Protection Status Register (PWM_WPSR). If a write access to a write-protected register is detected, the WPVS flag in PWM_WPSR is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS and WPVSRC fields are automatically cleared after reading PWM_WPSR.  2017 Microchip Technology Inc. DS60001476B-page 2153 SAMA5D2 SERIES 56.7 Pulse Width Modulation Controller (PWM) User Interface Table 56-8: Register Mapping Offset Register Name Access Reset 0x00 PWM Clock Register PWM_CLK Read/Write 0x0 0x04 PWM Enable Register PWM_ENA Write-only – 0x08 PWM Disable Register PWM_DIS Write-only – 0x0C PWM Status Register PWM_SR Read-only 0x0 0x10 PWM Interrupt Enable Register 1 PWM_IER1 Write-only – 0x14 PWM Interrupt Disable Register 1 PWM_IDR1 Write-only – 0x18 PWM Interrupt Mask Register 1 PWM_IMR1 Read-only 0x0 0x1C PWM Interrupt Status Register 1 PWM_ISR1 Read-only 0x0 0x20 PWM Sync Channels Mode Register PWM_SCM Read/Write 0x0 0x24 PWM DMA Register PWM_DMAR Write-only – 0x28 PWM Sync Channels Update Control Register PWM_SCUC Read/Write 0x0 0x2C PWM Sync Channels Update Period Register PWM_SCUP Read/Write 0x0 0x30 PWM Sync Channels Update Period Update Register PWM_SCUPUPD Write-only – 0x34 PWM Interrupt Enable Register 2 PWM_IER2 Write-only – 0x38 PWM Interrupt Disable Register 2 PWM_IDR2 Write-only – 0x3C PWM Interrupt Mask Register 2 PWM_IMR2 Read-only 0x0 0x40 PWM Interrupt Status Register 2 PWM_ISR2 Read-only 0x0 0x44 PWM Output Override Value Register PWM_OOV Read/Write 0x0 0x48 PWM Output Selection Register PWM_OS Read/Write 0x0 0x4C PWM Output Selection Set Register PWM_OSS Write-only – 0x50 PWM Output Selection Clear Register PWM_OSC Write-only – 0x54 PWM Output Selection Set Update Register PWM_OSSUPD Write-only – 0x58 PWM Output Selection Clear Update Register PWM_OSCUPD Write-only – 0x5C PWM Fault Mode Register PWM_FMR Read/Write 0x0 0x60 PWM Fault Status Register PWM_FSR Read-only 0x0 0x64 PWM Fault Clear Register PWM_FCR Write-only – 0x68 PWM Fault Protection Value Register 1 PWM_FPV1 Read/Write 0x0 0x6C PWM Fault Protection Enable Register PWM_FPE Read/Write 0x0 0x70–0x78 Reserved – – – 0x7C PWM Event Line 0 Mode Register PWM_ELMR0 Read/Write 0x0 0x80 PWM Event Line 1 Mode Register PWM_ELMR1 Read/Write 0x0 0x84–0x9C Reserved – – – 0xA0 PWM Spread Spectrum Register PWM_SSPR Read/Write 0x0 0xA4 PWM Spread Spectrum Update Register PWM_SSPUP Write-only – 0xA8–0xAC Reserved – – – DS60001476B-page 2154  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 56-8: Register Mapping (Continued) Offset Register Name Access Reset 0xB0 PWM Stepper Motor Mode Register PWM_SMMR Read/Write 0x0 0xC0 PWM Fault Protection Value 2 Register PWM_FPV2 Read/Write 0x003F_003F 0xC4–0xE0 Reserved – – – 0xE4 PWM Write Protection Control Register PWM_WPCR Write-only – 0xE8 PWM Write Protection Status Register PWM_WPSR Read-only 0x0 0xEC–0xFC Reserved – – – 0x100–0x12C Reserved – – – 0x130 PWM Comparison 0 Value Register PWM_CMPV0 Read/Write 0x0 0x134 PWM Comparison 0 Value Update Register PWM_CMPVUPD0 Write-only – 0x138 PWM Comparison 0 Mode Register PWM_CMPM0 Read/Write 0x0 0x13C PWM Comparison 0 Mode Update Register PWM_CMPMUPD0 Write-only – 0x140 PWM Comparison 1 Value Register PWM_CMPV1 Read/Write 0x0 0x144 PWM Comparison 1 Value Update Register PWM_CMPVUPD1 Write-only – 0x148 PWM Comparison 1 Mode Register PWM_CMPM1 Read/Write 0x0 0x14C PWM Comparison 1 Mode Update Register PWM_CMPMUPD1 Write-only – 0x150 PWM Comparison 2 Value Register PWM_CMPV2 Read/Write 0x0 0x154 PWM Comparison 2 Value Update Register PWM_CMPVUPD2 Write-only – 0x158 PWM Comparison 2 Mode Register PWM_CMPM2 Read/Write 0x0 0x15C PWM Comparison 2 Mode Update Register PWM_CMPMUPD2 Write-only – 0x160 PWM Comparison 3 Value Register PWM_CMPV3 Read/Write 0x0 0x164 PWM Comparison 3 Value Update Register PWM_CMPVUPD3 Write-only – 0x168 PWM Comparison 3 Mode Register PWM_CMPM3 Read/Write 0x0 0x16C PWM Comparison 3 Mode Update Register PWM_CMPMUPD3 Write-only – 0x170 PWM Comparison 4 Value Register PWM_CMPV4 Read/Write 0x0 0x174 PWM Comparison 4 Value Update Register PWM_CMPVUPD4 Write-only – 0x178 PWM Comparison 4 Mode Register PWM_CMPM4 Read/Write 0x0 0x17C PWM Comparison 4 Mode Update Register PWM_CMPMUPD4 Write-only – 0x180 PWM Comparison 5 Value Register PWM_CMPV5 Read/Write 0x0 0x184 PWM Comparison 5 Value Update Register PWM_CMPVUPD5 Write-only – 0x188 PWM Comparison 5 Mode Register PWM_CMPM5 Read/Write 0x0 0x18C PWM Comparison 5 Mode Update Register PWM_CMPMUPD5 Write-only – 0x190 PWM Comparison 6 Value Register PWM_CMPV6 Read/Write 0x0 0x194 PWM Comparison 6 Value Update Register PWM_CMPVUPD6 Write-only – 0x198 PWM Comparison 6 Mode Register PWM_CMPM6 Read/Write 0x0 0x19C PWM Comparison 6 Mode Update Register PWM_CMPMUPD6 Write-only – 0x1A0 PWM Comparison 7 Value Register PWM_CMPV7 Read/Write 0x0  2017 Microchip Technology Inc. DS60001476B-page 2155 SAMA5D2 SERIES Table 56-8: Register Mapping (Continued) Offset Register Name Access Reset 0x1A4 PWM Comparison 7 Value Update Register PWM_CMPVUPD7 Write-only – 0x1A8 PWM Comparison 7 Mode Register PWM_CMPM7 Read/Write 0x0 0x1AC PWM Comparison 7 Mode Update Register PWM_CMPMUPD7 Write-only – 0x1B0–0x1FC Reserved – – – 0x200 + ch_num * 0x20 + 0x00 PWM Channel Mode Register(1) PWM_CMR Read/Write 0x0 0x200 + ch_num * 0x20 + 0x04 PWM Channel Duty Cycle Register(1) PWM_CDTY Read/Write 0x0 0x200 + ch_num * 0x20 + 0x08 PWM Channel Duty Cycle Update Register(1) PWM_CDTYUPD Write-only – 0x200 + ch_num * 0x20 + 0x0C PWM Channel Period Register(1) PWM_CPRD Read/Write 0x0 0x200 + ch_num * 0x20 + 0x10 PWM Channel Period Update Register(1) PWM_CPRDUPD Write-only – 0x200 + ch_num * 0x20 + 0x14 PWM Channel Counter Register(1) PWM_CCNT Read-only 0x0 0x200 + ch_num * 0x20 + 0x18 PWM Channel Dead Time Register(1) PWM_DT Read/Write 0x0 0x200 + ch_num * 0x20 + 0x1C PWM Channel Dead Time Update Register(1) PWM_DTUPD Write-only – 0x400 + ch_num * 0x20 + 0x00 PWM Channel Mode Update Register(1) PWM_CMUPD Write-only – 0x42C PWM External Trigger Register 1 PWM_ETRG1 Read/Write 0x0 0x430 PWM Leading-Edge Blanking Register 1 PWM_LEBR1 Read/Write 0x0 0x434 PWM External Trigger Register 2 PWM_ETRG2 Read/Write 0x0 0x438 PWM Leading-Edge Blanking Register 2 PWM_LEBR2 Read/Write 0x0 Note 1: Some registers are indexed with “ch_num” index ranging from 2 to 3. DS60001476B-page 2156  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.1 PWM Clock Register Name: PWM_CLK Address: 0xF802C000 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 26 25 24 PREB 19 18 17 16 11 10 9 8 1 0 DIVB 15 – 14 – 13 – 12 – 7 6 5 4 PREA 3 2 DIVA This register can only be written if bits WPSWS0 and WPHWS0 are cleared in the PWM Write Protection Status Register. DIVA: CLKA Divide Factor Value Name 0 CLKA_POFF 1 PREA 2–255 PREA_DIV Description CLKA clock is turned off CLKA clock is clock selected by PREA CLKA clock is clock selected by PREA divided by DIVA factor DIVB: CLKB Divide Factor Value Name 0 CLKB_POFF 1 PREB 2–255 PREB_DIV Description CLKB clock is turned off CLKB clock is clock selected by PREB CLKB clock is clock selected by PREB divided by DIVB factor PREA: CLKA Source Clock Selection Value Name 0 CLK 1 CLK_DIV2 Peripheral clock/2 2 CLK_DIV4 Peripheral clock/4 3 CLK_DIV8 Peripheral clock/8 4 CLK_DIV16 Peripheral clock/16 5 CLK_DIV32 Peripheral clock/32 6 CLK_DIV64 Peripheral clock/64 7 CLK_DIV128 Peripheral clock/128 8 CLK_DIV256 Peripheral clock/256 9 CLK_DIV512 Peripheral clock/512 10 CLK_DIV1024 Peripheral clock/1024 Other –  2017 Microchip Technology Inc. Description Peripheral clock Reserved DS60001476B-page 2157 SAMA5D2 SERIES PREB: CLKB Source Clock Selection Value Name 0 CLK 1 CLK_DIV2 Peripheral clock/2 2 CLK_DIV4 Peripheral clock/4 3 CLK_DIV8 Peripheral clock/8 4 CLK_DIV16 Peripheral clock/16 5 CLK_DIV32 Peripheral clock/32 6 CLK_DIV64 Peripheral clock/64 7 CLK_DIV128 Peripheral clock/128 8 CLK_DIV256 Peripheral clock/256 9 CLK_DIV512 Peripheral clock/512 10 CLK_DIV1024 Peripheral clock/1024 Other – DS60001476B-page 2158 Description Peripheral clock Reserved  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.2 PWM Enable Register Name: PWM_ENA Address: 0xF802C004 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Channel ID 0: No effect. 1: Enable PWM output for channel x.  2017 Microchip Technology Inc. DS60001476B-page 2159 SAMA5D2 SERIES 56.7.3 PWM Disable Register Name: PWM_DIS Address: 0xF802C008 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 This register can only be written if bits WPSWS1 and WPHWS1 are cleared in the PWM Write Protection Status Register. CHIDx: Channel ID 0: No effect. 1: Disable PWM output for channel x. DS60001476B-page 2160  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.4 PWM Status Register Name: PWM_SR Address: 0xF802C00C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Channel ID 0: PWM output for channel x is disabled. 1: PWM output for channel x is enabled.  2017 Microchip Technology Inc. DS60001476B-page 2161 SAMA5D2 SERIES 56.7.5 PWM Interrupt Enable Register 1 Name: PWM_IER1 Address: 0xF802C010 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FCHID3 18 FCHID2 17 FCHID1 16 FCHID0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Counter Event on Channel x Interrupt Enable FCHIDx: Fault Protection Trigger on Channel x Interrupt Enable DS60001476B-page 2162  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.6 PWM Interrupt Disable Register 1 Name: PWM_IDR1 Address: 0xF802C014 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FCHID3 18 FCHID2 17 FCHID1 16 FCHID0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Counter Event on Channel x Interrupt Disable FCHIDx: Fault Protection Trigger on Channel x Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 2163 SAMA5D2 SERIES 56.7.7 PWM Interrupt Mask Register 1 Name: PWM_IMR1 Address: 0xF802C018 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FCHID3 18 FCHID2 17 FCHID1 16 FCHID0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Counter Event on Channel x Interrupt Mask FCHIDx: Fault Protection Trigger on Channel x Interrupt Mask DS60001476B-page 2164  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.8 PWM Interrupt Status Register 1 Name: PWM_ISR1 Address: 0xF802C01C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FCHID3 18 FCHID2 17 FCHID1 16 FCHID0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 CHID3 2 CHID2 1 CHID1 0 CHID0 CHIDx: Counter Event on Channel x 0: No new counter event has occurred since the last read of PWM_ISR1. 1: At least one counter event has occurred since the last read of PWM_ISR1. FCHIDx: Fault Protection Trigger on Channel x 0: No new trigger of the fault protection since the last read of PWM_ISR1. 1: At least one trigger of the fault protection since the last read of PWM_ISR1. Note: Reading PWM_ISR1 automatically clears CHIDx and FCHIDx flags.  2017 Microchip Technology Inc. DS60001476B-page 2165 SAMA5D2 SERIES 56.7.9 PWM Sync Channels Mode Register Name: PWM_SCM Address: 0xF802C020 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 PTRCS 21 20 PTRM 19 – 18 – 17 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 SYNC3 2 SYNC2 1 SYNC1 0 SYNC0 16 UPDM This register can only be written if bits WPSWS2 and WPHWS2 are cleared in the PWM Write Protection Status Register. SYNCx: Synchronous Channel x 0: Channel x is not a synchronous channel. 1: Channel x is a synchronous channel. UPDM: Synchronous Channels Update Mode Value Name Description 0 MODE0 Manual write of double buffer registers and manual update of synchronous channels(1) 1 MODE1 Manual write of double buffer registers and automatic update of synchronous channels(2) 2 MODE2 Automatic write of duty-cycle update registers by the DMA Controller and automatic update of synchronous channels(2) Note 1: The update occurs at the beginning of the next PWM period, when the UPDULOCK bit in PWM Sync Channels Update Control Register is set. 2: The update occurs when the Update Period is elapsed. PTRM: DMA Controller Transfer Request Mode UPDM PTRM WRDY Flag and DMA Controller Transfer Request 0 x The WRDY flag in PWM Interrupt Status Register 2 and the DMA transfer request are never set to ‘1’. 1 x The WRDY flag in PWM Interrupt Status Register 2 is set to ‘1’ as soon as the update period is elapsed, the DMA Controller transfer request is never set to ‘1’. 0 The WRDY flag in PWM Interrupt Status Register 2 and the DMA transfer request are set to ‘1’ as soon as the update period is elapsed. 1 The WRDY flag in PWM Interrupt Status Register 2 and the DMA transfer request are set to ‘1’ as soon as the selected comparison matches. 2 PTRCS: DMA Controller Transfer Request Comparison Selection Selection of the comparison used to set the flag WRDY and the corresponding DMA Controller transfer request. DS60001476B-page 2166  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.10 PWM DMA Register Name: PWM_DMAR Address: 0xF802C024 Access: Write- only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 DMADUTY 15 14 13 12 DMADUTY 7 6 5 4 DMADUTY Only the first 16 bits (channel counter size) are significant. DMADUTY: Duty-Cycle Holding Register for DMA Access Each write access to PWM_DMAR sequentially updates the CDTY field of PWM_CDTYx with DMADUTY (only for channel configured as synchronous). See “Method 3: Automatic write of duty-cycle values and automatic trigger of the update” .  2017 Microchip Technology Inc. DS60001476B-page 2167 SAMA5D2 SERIES 56.7.11 PWM Sync Channels Update Control Register Name: PWM_SCUC Address: 0xF802C028 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 UPDULOCK UPDULOCK: Synchronous Channels Update Unlock 0: No effect 1: If the UPDM field is set to ‘0’ in PWM Sync Channels Mode Register, writing the UPDULOCK bit to ‘1’ triggers the update of the period value, the duty-cycle and the dead-time values of synchronous channels at the beginning of the next PWM period. If the field UPDM is set to ‘1’ or ‘2’, writing the UPDULOCK bit to ‘1’ triggers only the update of the period value and of the dead-time values of synchronous channels. This bit is automatically reset when the update is done. DS60001476B-page 2168  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.12 PWM Sync Channels Update Period Register Name: PWM_SCUP Address: 0xF802C02C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 UPRCNT UPR UPR: Update Period Defines the time between each update of the synchronous channels if automatic trigger of the update is activated (UPDM = 1 or UPDM = 2 in PWM Sync Channels Mode Register). This time is equal to UPR+1 periods of the synchronous channels. UPRCNT: Update Period Counter Reports the value of the update period counter.  2017 Microchip Technology Inc. DS60001476B-page 2169 SAMA5D2 SERIES 56.7.13 PWM Sync Channels Update Period Update Register Name: PWM_SCUPUPD Address: 0xF802C030 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 2 1 0 UPRUPD This register acts as a double buffer for the UPR value. This prevents an unexpected automatic trigger of the update of synchronous channels. UPRUPD: Update Period Update Defines the wanted time between each update of the synchronous channels if automatic trigger of the update is activated (UPDM = 1 or UPDM = 2 in PWM Sync Channels Mode Register). This time is equal to UPR+1 periods of the synchronous channels. DS60001476B-page 2170  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.14 PWM Interrupt Enable Register 2 Name: PWM_IER2 Address: 0xF802C034 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 CMPU7 22 CMPU6 21 CMPU5 20 CMPU4 19 CMPU3 18 CMPU2 17 CMPU1 16 CMPU0 15 CMPM7 14 CMPM6 13 CMPM5 12 CMPM4 11 CMPM3 10 CMPM2 9 CMPM1 8 CMPM0 7 – 6 – 5 – 4 – 3 UNRE 2 – 1 – 0 WRDY WRDY: Write Ready for Synchronous Channels Update Interrupt Enable UNRE: Synchronous Channels Update Underrun Error Interrupt Enable CMPMx: Comparison x Match Interrupt Enable CMPUx: Comparison x Update Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 2171 SAMA5D2 SERIES 56.7.15 PWM Interrupt Disable Register 2 Name: PWM_IDR2 Address: 0xF802C038 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 CMPU7 22 CMPU6 21 CMPU5 20 CMPU4 19 CMPU3 18 CMPU2 17 CMPU1 16 CMPU0 15 CMPM7 14 CMPM6 13 CMPM5 12 CMPM4 11 CMPM3 10 CMPM2 9 CMPM1 8 CMPM0 7 – 6 – 5 – 4 – 3 UNRE 2 – 1 – 0 WRDY WRDY: Write Ready for Synchronous Channels Update Interrupt Disable UNRE: Synchronous Channels Update Underrun Error Interrupt Disable CMPMx: Comparison x Match Interrupt Disable CMPUx: Comparison x Update Interrupt Disable DS60001476B-page 2172  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.16 PWM Interrupt Mask Register 2 Name: PWM_IMR2 Address: 0xF802C03C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 CMPU7 22 CMPU6 21 CMPU5 20 CMPU4 19 CMPU3 18 CMPU2 17 CMPU1 16 CMPU0 15 CMPM7 14 CMPM6 13 CMPM5 12 CMPM4 11 CMPM3 10 CMPM2 9 CMPM1 8 CMPM0 7 – 6 – 5 – 4 – 3 UNRE 2 – 1 – 0 WRDY WRDY: Write Ready for Synchronous Channels Update Interrupt Mask UNRE: Synchronous Channels Update Underrun Error Interrupt Mask CMPMx: Comparison x Match Interrupt Mask CMPUx: Comparison x Update Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 2173 SAMA5D2 SERIES 56.7.17 PWM Interrupt Status Register 2 Name: PWM_ISR2 Address: 0xF802C040 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 CMPU7 22 CMPU6 21 CMPU5 20 CMPU4 19 CMPU3 18 CMPU2 17 CMPU1 16 CMPU0 15 CMPM7 14 CMPM6 13 CMPM5 12 CMPM4 11 CMPM3 10 CMPM2 9 CMPM1 8 CMPM0 7 – 6 – 5 – 4 – 3 UNRE 2 – 1 – 0 WRDY WRDY: Write Ready for Synchronous Channels Update 0: New duty-cycle and dead-time values for the synchronous channels cannot be written. 1: New duty-cycle and dead-time values for the synchronous channels can be written. UNRE: Synchronous Channels Update Underrun Error 0: No Synchronous Channels Update Underrun has occurred since the last read of the PWM_ISR2 register. 1: At least one Synchronous Channels Update Underrun has occurred since the last read of the PWM_ISR2 register. CMPMx: Comparison x Match 0: The comparison x has not matched since the last read of the PWM_ISR2 register. 1: The comparison x has matched at least one time since the last read of the PWM_ISR2 register. CMPUx: Comparison x Update 0: The comparison x has not been updated since the last read of the PWM_ISR2 register. 1: The comparison x has been updated at least one time since the last read of the PWM_ISR2 register. Note: Reading PWM_ISR2 automatically clears flags WRDY, UNRE and CMPSx. DS60001476B-page 2174  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.18 PWM Output Override Value Register Name: PWM_OOV Address: 0xF802C044 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OOVL3 18 OOVL2 17 OOVL1 16 OOVL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OOVH3 2 OOVH2 1 OOVH1 0 OOVH0 OOVHx: Output Override Value for PWMH output of the channel x 0: Override value is 0 for PWMH output of channel x. 1: Override value is 1 for PWMH output of channel x. OOVLx: Output Override Value for PWML output of the channel x 0: Override value is 0 for PWML output of channel x. 1: Override value is 1 for PWML output of channel x.  2017 Microchip Technology Inc. DS60001476B-page 2175 SAMA5D2 SERIES 56.7.19 PWM Output Selection Register Name: PWM_OS Address: 0xF802C048 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OSL3 18 OSL2 17 OSL1 16 OSL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSH3 2 OSH2 1 OSH1 0 OSH0 OSHx: Output Selection for PWMH output of the channel x 0: Dead-time generator output DTOHx selected as PWMH output of channel x. 1: Output override value OOVHx selected as PWMH output of channel x. OSLx: Output Selection for PWML output of the channel x 0: Dead-time generator output DTOLx selected as PWML output of channel x. 1: Output override value OOVLx selected as PWML output of channel x. DS60001476B-page 2176  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.20 PWM Output Selection Set Register Name: PWM_OSS Address: 0xF802C04C Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OSSL3 18 OSSL2 17 OSSL1 16 OSSL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSSH3 2 OSSH2 1 OSSH1 0 OSSH0 OSSHx: Output Selection Set for PWMH output of the channel x 0: No effect. 1: Output override value OOVHx selected as PWMH output of channel x. OSSLx: Output Selection Set for PWML output of the channel x 0: No effect. 1: Output override value OOVLx selected as PWML output of channel x.  2017 Microchip Technology Inc. DS60001476B-page 2177 SAMA5D2 SERIES 56.7.21 PWM Output Selection Clear Register Name: PWM_OSC Address: 0xF802C050 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OSCL3 18 OSCL2 17 OSCL1 16 OSCL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSCH3 2 OSCH2 1 OSCH1 0 OSCH0 OSCHx: Output Selection Clear for PWMH output of the channel x 0: No effect. 1: Dead-time generator output DTOHx selected as PWMH output of channel x. OSCLx: Output Selection Clear for PWML output of the channel x 0: No effect. 1: Dead-time generator output DTOLx selected as PWML output of channel x. DS60001476B-page 2178  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.22 PWM Output Selection Set Update Register Name: PWM_OSSUPD Address: 0xF802C054 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OSSUPL3 18 OSSUPL2 17 OSSUPL1 16 OSSUPL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSSUPH3 2 OSSUPH2 1 OSSUPH1 0 OSSUPH0 OSSUPHx: Output Selection Set for PWMH output of the channel x 0: No effect. 1: Output override value OOVHx selected as PWMH output of channel x at the beginning of the next channel x PWM period. OSSUPLx: Output Selection Set for PWML output of the channel x 0: No effect. 1: Output override value OOVLx selected as PWML output of channel x at the beginning of the next channel x PWM period.  2017 Microchip Technology Inc. DS60001476B-page 2179 SAMA5D2 SERIES 56.7.23 PWM Output Selection Clear Update Register Name: PWM_OSCUPD Address: 0xF802C058 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 OSCUPL3 18 OSCUPL2 17 OSCUPL1 16 OSCUPL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 OSCUPH3 2 OSCUPH2 1 OSCUPH1 0 OSCUPH0 OSCUPHx: Output Selection Clear for PWMH output of the channel x 0: No effect. 1: Dead-time generator output DTOHx selected as PWMH output of channel x at the beginning of the next channel x PWM period. OSCUPLx: Output Selection Clear for PWML output of the channel x 0: No effect. 1: Dead-time generator output DTOLx selected as PWML output of channel x at the beginning of the next channel x PWM period. DS60001476B-page 2180  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.24 PWM Fault Mode Register Name: PWM_FMR Address: 0xF802C05C Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 – 23 22 21 20 FFIL 15 14 13 12 FMOD 7 6 5 4 FPOL This register can only be written if bits WPSWS5 and WPHWS5 are cleared in the PWM Write Protection Status Register. Refer to Section 56.5.4 “Fault Inputs” for details on fault generation. FPOL: Fault Polarity For each bit y of FPOL, where y is the fault input number: 0: The fault y becomes active when the fault input y is at 0. 1: The fault y becomes active when the fault input y is at 1. FMOD: Fault Activation Mode For each bit y of FMOD, where y is the fault input number: 0: The fault y is active until the fault condition is removed at the peripheral(1) level. 1: The fault y stays active until the fault condition is removed at the peripheral(1) level AND until it is cleared in the PWM Fault Clear Register. Note 1: The peripheral generating the fault. FFIL: Fault Filtering For each bit y of FFIL, where y is the fault input number: 0: The fault input y is not filtered. 1: The fault input y is filtered. CAUTION: To prevent an unexpected activation of the status flag FSy in the PWM Fault Status Register, the bit FMODy can be set to ‘1’ only if the FPOLy bit has been previously configured to its final value.  2017 Microchip Technology Inc. DS60001476B-page 2181 SAMA5D2 SERIES 56.7.25 PWM Fault Status Register Name: PWM_FSR Address: 0xF802C060 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 – 23 22 21 20 – 15 14 13 12 FS 7 6 5 4 FIV Refer to Section 56.5.4 “Fault Inputs” for details on fault generation. FIV: Fault Input Value For each bit y of FIV, where y is the fault input number: 0: The current sampled value of the fault input y is 0 (after filtering if enabled). 1: The current sampled value of the fault input y is 1 (after filtering if enabled). FS: Fault Status For each bit y of FS, where y is the fault input number: 0: The fault y is not currently active. 1: The fault y is currently active. DS60001476B-page 2182  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.26 PWM Fault Clear Register Name: PWM_FCR Address: 0xF802C064 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 – 23 22 21 20 – 15 14 13 12 – 7 6 5 4 FCLR Refer to Section 56.5.4 “Fault Inputs” for details on fault generation. FCLR: Fault Clear For each bit y of FCLR, where y is the fault input number: 0: No effect. 1: If bit y of FMOD field is set to ‘1’ and if the fault input y is not at the level defined by the bit y of FPOL field, the fault y is cleared and becomes inactive (FMOD and FPOL fields belong to PWM Fault Mode Register), else writing this bit to ‘1’ has no effect.  2017 Microchip Technology Inc. DS60001476B-page 2183 SAMA5D2 SERIES 56.7.27 PWM Fault Protection Value Register 1 Name: PWM_FPV1 Address: 0xF802C068 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FPVL3 18 FPVL2 17 FPVL1 16 FPVL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 FPVH3 2 FPVH2 1 FPVH1 0 FPVH0 This register can only be written if bits WPSWS5 and WPHWS5 are cleared in the PWM Write Protection Status Register. Refer to Section 56.5.4 “Fault Inputs” for details on fault generation. FPVHx: Fault Protection Value for PWMH output on channel x This bit is taken into account only if the bit FPZHx is set to ‘0’ in PWM Fault Protection Value Register 2. 0: PWMH output of channel x is forced to ‘0’ when fault occurs. 1: PWMH output of channel x is forced to ‘1’ when fault occurs. FPVLx: Fault Protection Value for PWML output on channel x This bit is taken into account only if the bit FPZLx is set to ‘0’ in PWM Fault Protection Value Register 2. 0: PWML output of channel x is forced to ‘0’ when fault occurs. 1: PWML output of channel x is forced to ‘1’ when fault occurs. DS60001476B-page 2184  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.28 PWM Fault Protection Enable Register Name: PWM_FPE Address: 0xF802C06C Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 FPE3 23 22 21 20 FPE2 15 14 13 12 FPE1 7 6 5 4 FPE0 This register can only be written if bits WPSWS5 and WPHWS5 are cleared in the PWM Write Protection Status Register. Only the first 6 bits (number of fault input pins) of fields FPE0, FPE1, FPE2 and FPE3 are significant. Refer to Section 56.5.4 “Fault Inputs” for details on fault generation. FPEx: Fault Protection Enable for channel x For each bit y of FPEx, where y is the fault input number: 0: Fault y is not used for the fault protection of channel x. 1: Fault y is used for the fault protection of channel x. CAUTION: To prevent an unexpected activation of the fault protection, the bit y of FPEx field can be set to ‘1’ only if the corresponding FPOL field has been previously configured to its final value in PWM Fault Mode Register.  2017 Microchip Technology Inc. DS60001476B-page 2185 SAMA5D2 SERIES 56.7.29 PWM Event Line x Register Name: PWM_ELMRx Address: 0xF802C07C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 CSEL7 6 CSEL6 5 CSEL5 4 CSEL4 3 CSEL3 2 CSEL2 1 CSEL1 0 CSEL0 CSELy: Comparison y Selection 0: A pulse is not generated on the event line x when the comparison y matches. 1: A pulse is generated on the event line x when the comparison y match. DS60001476B-page 2186  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.30 PWM Spread Spectrum Register Name: PWM_SSPR Address: 0xF802C0A0 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 SPRDM 19 18 17 16 11 10 9 8 3 2 1 0 SPRD 15 14 13 12 SPRD 7 6 5 4 SPRD This register can only be written if bits WPSWS3 and WPHWS3 are cleared in the PWM Write Protection Status Register. Only the first 16 bits (channel counter size) are significant. SPRD: Spread Spectrum Limit Value The spread spectrum limit value defines the range for the spread spectrum counter. It is introduced in order to achieve constant varying PWM period for the output waveform. SPRDM: Spread Spectrum Counter Mode 0: Triangular mode. The spread spectrum counter starts to count from -SPRD when the channel 0 is enabled and counts upwards at each PWM period. When it reaches +SPRD, it restarts to count from -SPRD again. 1: Random mode. The spread spectrum counter is loaded with a new random value at each PWM period. This random value is uniformly distributed and is between -SPRD and +SPRD.  2017 Microchip Technology Inc. DS60001476B-page 2187 SAMA5D2 SERIES 56.7.31 PWM Spread Spectrum Update Register Name: PWM_SSPUP Address: 0xF802C0A4 Access: Write-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 SPRDUP 15 14 13 12 SPRDUP 7 6 5 4 SPRDUP This register can only be written if bits WPSWS3 and WPHWS3 are cleared in the PWM Write Protection Status Register. This register acts as a double buffer for the SPRD value. This prevents an unexpected waveform when modifying the spread spectrum limit value. Only the first 16 bits (channel counter size) are significant. SPRDUP: Spread Spectrum Limit Value Update The spread spectrum limit value defines the range for the spread spectrum counter. It is introduced in order to achieve constant varying period for the output waveform. DS60001476B-page 2188  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.32 PWM Stepper Motor Mode Register Name: PWM_SMMR Address: 0xF802C0B0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 DOWN1 16 DOWN0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 GCEN1 0 GCEN0 GCENx: Gray Count Enable 0: Disable Gray count generation on PWML[2*x], PWMH[2*x], PWML[2*x +1], PWMH[2*x +1] 1: Enable Gray count generation on PWML[2*x], PWMH[2*x], PWML[2*x +1], PWMH[2*x +1]. DOWNx: Down Count 0: Up counter. 1: Down counter.  2017 Microchip Technology Inc. DS60001476B-page 2189 SAMA5D2 SERIES 56.7.33 PWM Fault Protection Value Register 2 Name: PWM_FPV2 Address: 0xF802C0C0 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 FPZL3 18 FPZL2 17 FPZL1 16 FPZL0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 FPZH3 2 FPZH2 1 FPZH1 0 FPZH0 This register can only be written if bits WPSWS5 and WPHWS5 are cleared in the PWM Write Protection Status Register. FPZHx: Fault Protection to Hi-Z for PWMH output on channel x 0: When fault occurs, PWMH output of channel x is forced to value defined by the bit FPVHx in PWM Fault Protection Value Register 1. 1: When fault occurs, PWMH output of channel x is forced to high-impedance state. FPZLx: Fault Protection to Hi-Z for PWML output on channel x 0: When fault occurs, PWML output of channel x is forced to value defined by the bit FPVLx in PWM Fault Protection Value Register 1. 1: When fault occurs, PWML output of channel x is forced to high-impedance state. DS60001476B-page 2190  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.34 PWM Write Protection Control Register Name: PWM_WPCR Address: 0xF802C0E4 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 WPRG1 2 WPRG0 1 WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 WPRG5 6 WPRG4 5 WPRG3 4 WPRG2 0 WPCMD See Section 56.6.7 “Register Write Protection” for the list of registers that can be write-protected. WPCMD: Write Protection Command This command is performed only if the WPKEY corresponds to 0x50574D (“PWM” in ASCII). Value Name 0 DISABLE_SW_PROT Disables the software write protection of the register groups of which the bit WPRGx is at ‘1’. 1 ENABLE_SW_PROT Enables the software write protection of the register groups of which the bit WPRGx is at ‘1’. ENABLE_HW_PROT Enables the hardware write protection of the register groups of which the bit WPRGx is at ‘1’. Only a hardware reset of the PWM controller can disable the hardware write protection. Moreover, to meet security requirements, the PIO lines associated with the PWM can not be configured through the PIO interface. 2 Description WPRGx: Write Protection Register Group x 0: The WPCMD command has no effect on the register group x. 1: The WPCMD command is applied to the register group x. WPKEY: Write Protection Key Value Name 0x50574D PASSWD Description Writing any other value in this field aborts the write operation of the WPCMD field. Always reads as 0  2017 Microchip Technology Inc. DS60001476B-page 2191 SAMA5D2 SERIES 56.7.35 PWM Write Protection Status Register Name: PWM_WPSR Address: 0xF802C0E8 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 WPVSRC 23 22 21 20 WPVSRC 15 – 14 – 13 WPHWS5 12 WPHWS4 11 WPHWS3 10 WPHWS2 9 WPHWS1 8 WPHWS0 7 WPVS 6 – 5 WPSWS5 4 WPSWS4 3 WPSWS3 2 WPSWS2 1 WPSWS1 0 WPSWS0 WPSWSx: Write Protect SW Status 0: The SW write protection x of the register group x is disabled. 1: The SW write protection x of the register group x is enabled. WPHWSx: Write Protect HW Status 0: The HW write protection x of the register group x is disabled. 1: The HW write protection x of the register group x is enabled. WPVS: Write Protect Violation Status 0: No write protection violation has occurred since the last read of PWM_WPSR. 1: At least one write protection violation has occurred since the last read of PWM_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protect Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 2192  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.36 PWM Comparison x Value Register Name: PWM_CMPVx Address: 0xF802C130 [0], 0xF802C140 [1], 0xF802C150 [2], 0xF802C160 [3], 0xF802C170 [4], 0xF802C180 [5], 0xF802C190 [6], 0xF802C1A0 [7] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 CVM 23 22 21 20 19 18 17 16 11 10 9 8 3 2 1 0 CV 15 14 13 12 CV 7 6 5 4 CV Only the first 16 bits (channel counter size) of field CV are significant. CV: Comparison x Value Define the comparison x value to be compared with the counter of the channel 0. CVM: Comparison x Value Mode 0: The comparison x between the counter of the channel 0 and the comparison x value is performed when this counter is incrementing. 1: The comparison x between the counter of the channel 0 and the comparison x value is performed when this counter is decrementing. Note: This bit is not relevant if the counter of the channel 0 is left-aligned (CALG = 0 in PWM Channel Mode Register)  2017 Microchip Technology Inc. DS60001476B-page 2193 SAMA5D2 SERIES 56.7.37 PWM Comparison x Value Update Register Name: PWM_CMPVUPDx Address: 0xF802C134 [0], 0xF802C144 [1], 0xF802C154 [2], 0xF802C164 [3], 0xF802C174 [4], 0xF802C184 [5], 0xF802C194 [6], 0xF802C1A4 [7] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 CVMUPD 23 22 21 20 19 18 17 16 11 10 9 8 3 2 1 0 CVUPD 15 14 13 12 CVUPD 7 6 5 4 CVUPD This register acts as a double buffer for the CV and CVM values. This prevents an unexpected comparison x match. Only the first 16 bits (channel counter size) of field CVUPD are significant. CVUPD: Comparison x Value Update Define the comparison x value to be compared with the counter of the channel 0. CVMUPD: Comparison x Value Mode Update 0: The comparison x between the counter of the channel 0 and the comparison x value is performed when this counter is incrementing. 1: The comparison x between the counter of the channel 0 and the comparison x value is performed when this counter is decrementing. Note: This bit is not relevant if the counter of the channel 0 is left-aligned (CALG = 0 in PWM Channel Mode Register) CAUTION: The write of the register PWM_CMPVUPDx must be followed by a write of the register PWM_CMPMUPDx. DS60001476B-page 2194  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.38 PWM Comparison x Mode Register Name: PWM_CMPMx Address: 0xF802C138 [0], 0xF802C148 [1], 0xF802C158 [2], 0xF802C168 [3], 0xF802C178 [4], 0xF802C188 [5], 0xF802C198 [6], 0xF802C1A8 [7] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 22 21 20 19 18 17 16 9 8 1 – 0 CEN CUPRCNT 15 14 CUPR 13 12 11 10 CPRCNT 7 6 CPR 5 4 CTR 3 – 2 – CEN: Comparison x Enable 0: The comparison x is disabled and can not match. 1: The comparison x is enabled and can match. CTR: Comparison x Trigger The comparison x is performed when the value of the comparison x period counter (CPRCNT) reaches the value defined by CTR. CPR: Comparison x Period CPR defines the maximum value of the comparison x period counter (CPRCNT). The comparison x value is performed periodically once every CPR+1 periods of the channel 0 counter. CPRCNT: Comparison x Period Counter Reports the value of the comparison x period counter. Note: The field CPRCNT is read-only CUPR: Comparison x Update Period Defines the time between each update of the comparison x mode and the comparison x value. This time is equal to CUPR+1 periods of the channel 0 counter. CUPRCNT: Comparison x Update Period Counter Reports the value of the comparison x update period counter. Note: The field CUPRCNT is read-only  2017 Microchip Technology Inc. DS60001476B-page 2195 SAMA5D2 SERIES 56.7.39 PWM Comparison x Mode Update Register Name: PWM_CMPMUPDx Address: 0xF802C13C [0], 0xF802C14C [1], 0xF802C15C [2], 0xF802C16C [3], 0xF802C17C [4], 0xF802C18C [5], 0xF802C19C [6], 0xF802C1AC [7] Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 18 17 16 15 – 14 – 13 – 12 – 11 9 8 7 6 5 4 3 – 1 – 0 CENUPD CTRUPD CUPRUPD 10 CPRUPD 2 – This register acts as a double buffer for the CEN, CTR, CPR and CUPR values. This prevents an unexpected comparison x match. CENUPD: Comparison x Enable Update 0: The comparison x is disabled and can not match. 1: The comparison x is enabled and can match. CTRUPD: Comparison x Trigger Update The comparison x is performed when the value of the comparison x period counter (CPRCNT) reaches the value defined by CTR. CPRUPD: Comparison x Period Update CPR defines the maximum value of the comparison x period counter (CPRCNT). The comparison x value is performed periodically once every CPR+1 periods of the channel 0 counter. CUPRUPD: Comparison x Update Period Update Defines the time between each update of the comparison x mode and the comparison x value. This time is equal to CUPR+1 periods of the channel 0 counter. DS60001476B-page 2196  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.40 PWM Channel Mode Register Name: PWM_CMRx [x=0..3] Address: 0xF802C200 [0], 0xF802C220 [1], 0xF802C240 [2], 0xF802C260 [3] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 PPM 18 DTLI 17 DTHI 16 DTE 15 – 14 – 13 TCTS 12 DPOLI 11 UPDS 10 CES 9 CPOL 8 CALG 7 – 6 – 5 – 4 – 3 2 1 0 CPRE This register can only be written if bits WPSWS2 and WPHWS2 are cleared in the PWM Write Protection Status Register. CPRE: Channel Prescaler Value Name Description 0 MCK Peripheral clock 1 MCK_DIV_2 Peripheral clock/2 2 MCK_DIV_4 Peripheral clock/4 3 MCK_DIV_8 Peripheral clock/8 4 MCK_DIV_16 Peripheral clock/16 5 MCK_DIV_32 Peripheral clock/32 6 MCK_DIV_64 Peripheral clock/64 7 MCK_DIV_128 Peripheral clock/128 8 MCK_DIV_256 Peripheral clock/256 9 MCK_DIV_512 Peripheral clock/512 10 MCK_DIV_1024 Peripheral clock/1024 11 CLKA Clock A 12 CLKB Clock B CALG: Channel Alignment 0: The period is left-aligned. 1: The period is center-aligned. CPOL: Channel Polarity 0: The OCx output waveform (output from the comparator) starts at a low level. 1: The OCx output waveform (output from the comparator) starts at a high level.  2017 Microchip Technology Inc. DS60001476B-page 2197 SAMA5D2 SERIES CES: Counter Event Selection The bit CES defines when the channel counter event occurs when the period is center-aligned (flag CHIDx in PWM Interrupt Status Register 1). CALG = 0 (Left Alignment): 0/1: The channel counter event occurs at the end of the PWM period. CALG = 1 (Center Alignment): 0: The channel counter event occurs at the end of the PWM period. 1: The channel counter event occurs at the end of the PWM period and at half the PWM period. UPDS: Update Selection When the period is center aligned, the bit UPDS defines when the update of the duty cycle, the polarity value/mode occurs after writing the corresponding update registers. CALG = 0 (Left Alignment): 0/1: The update always occurs at the end of the PWM period after writing the update register(s). CALG = 1 (Center Alignment): 0: The update occurs at the next end of the PWM period after writing the update register(s). 1: The update occurs at the next end of the PWM half period after writing the update register(s). DPOLI: Disabled Polarity Inverted 0: When the PWM channel x is disabled (CHIDx(PWM_SR) = 0), the OCx output waveform is the same as the one defined by the CPOL bit. 1: When the PWM channel x is disabled (CHIDx(PWM_SR) = 0), the OCx output waveform is inverted compared to the one defined by the CPOL bit. TCTS: Timer Counter Trigger Selection 0: The comparator of the channel x (OCx) is used as the trigger source for the Timer Counter (TC). 1: The counter events of the channel x is used as the trigger source for the Timer Counter (TC). DTE: Dead-Time Generator Enable 0: The dead-time generator is disabled. 1: The dead-time generator is enabled. DTHI: Dead-Time PWMHx Output Inverted 0: The dead-time PWMHx output is not inverted. 1: The dead-time PWMHx output is inverted. DTLI: Dead-Time PWMLx Output Inverted 0: The dead-time PWMLx output is not inverted. 1: The dead-time PWMLx output is inverted. PPM: Push-Pull Mode 0: The Push-Pull mode is disabled for channel x. 1: The Push-Pull mode is enabled for channel x. DS60001476B-page 2198  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.41 PWM Channel Duty Cycle Register Name: PWM_CDTYx [x=0..3] Address: 0xF802C204 [0], 0xF802C224 [1], 0xF802C244 [2], 0xF802C264 [3] Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 CDTY 15 14 13 12 CDTY 7 6 5 4 CDTY Only the first 16 bits (channel counter size) are significant. CDTY: Channel Duty-Cycle Defines the waveform duty-cycle. This value must be defined between 0 and CPRD (PWM_CPRDx).  2017 Microchip Technology Inc. DS60001476B-page 2199 SAMA5D2 SERIES 56.7.42 PWM Channel Duty Cycle Update Register Name: PWM_CDTYUPDx [x=0..3] Address: 0xF802C208 [0], 0xF802C228 [1], 0xF802C248 [2], 0xF802C268 [3] Access: Write-only. 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 CDTYUPD 15 14 13 12 CDTYUPD 7 6 5 4 CDTYUPD This register acts as a double buffer for the CDTY value. This prevents an unexpected waveform when modifying the waveform duty-cycle. Only the first 16 bits (channel counter size) are significant. CDTYUPD: Channel Duty-Cycle Update Defines the waveform duty-cycle. This value must be defined between 0 and CPRD (PWM_CPRDx). DS60001476B-page 2200  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.43 PWM Channel Period Register Name: PWM_CPRDx [x=0..3] Address: 0xF802C20C [0], 0xF802C22C [1], 0xF802C24C [2], 0xF802C26C [3] Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 CPRD 15 14 13 12 CPRD 7 6 5 4 CPRD This register can only be written if bits WPSWS3 and WPHWS3 are cleared in the PWM Write Protection Status Register. Only the first 16 bits (channel counter size) are significant. CPRD: Channel Period If the waveform is left-aligned, then the output waveform period depends on the channel counter source clock and can be calculated: – By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is: ( X × CPRD )--------------------------------f peripheral clock – By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (----------------------------------------------------X × CPRD × DIVA )( X × C PRD × DIVB ) or -----------------------------------------------------f peripheral clock f peripheral clock If the waveform is center-aligned, then the output waveform period depends on the channel counter source clock and can be calculated: – By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is: (-----------------------------------------2 × X × CPRD ) f peripheral clock – By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (--------------------------------------------------------------2 × X × C PRD × DIVA )( 2 × X × C PRD × DIVB ) or ---------------------------------------------------------------f peripheral clock f peripheral clock  2017 Microchip Technology Inc. DS60001476B-page 2201 SAMA5D2 SERIES 56.7.44 PWM Channel Period Update Register Name: PWM_CPRDUPDx [x=0..3] Address: 0xF802C210 [0], 0xF802C230 [1], 0xF802C250 [2], 0xF802C270 [3] Access: Write-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 CPRDUPD 15 14 13 12 CPRDUPD 7 6 5 4 CPRDUPD This register can only be written if bits WPSWS3 and WPHWS3 are cleared in the PWM Write Protection Status Register. This register acts as a double buffer for the CPRD value. This prevents an unexpected waveform when modifying the waveform period. Only the first 16 bits (channel counter size) are significant. CPRDUPD: Channel Period Update If the waveform is left-aligned, then the output waveform period depends on the channel counter source clock and can be calculated: – By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is: (---------------------------------------------X × CPRDUPD ) f peripheral clock – By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (------------------------------------------------------------------X × CPRDUPD × DIVA )( X × CPRDUPD × DIVB ) or -------------------------------------------------------------------f peripheral clock f peripheral clock If the waveform is center-aligned, then the output waveform period depends on the channel counter source clock and can be calculated: – By using the PWM peripheral clock divided by a given prescaler value “X” (where X = 2PREA is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024). The resulting period formula is: (------------------------------------------------------2 × X × CPRDUPD )f peripheral clock – By using the PWM peripheral clock divided by a given prescaler value “X” (see above) and by either the DIVA or the DIVB divider. The formula becomes, respectively: (----------------------------------------------------------------------------2 × X × C PRDUPD × DIVA )( 2 × X × C PRDUPD × DIVB ) or -----------------------------------------------------------------------------f peripheral clock f peripheral clock DS60001476B-page 2202  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.45 PWM Channel Counter Register Name: PWM_CCNTx [x=0..3] Address: 0xF802C214 [0], 0xF802C234 [1], 0xF802C254 [2], 0xF802C274 [3] Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 2 1 0 CNT 15 14 13 12 CNT 7 6 5 4 CNT Only the first 16 bits (channel counter size) are significant. CNT: Channel Counter Register Channel counter value. This register is reset when: • the channel is enabled (writing CHIDx in the PWM_ENA register). • the channel counter reaches CPRD value defined in the PWM_CPRDx register if the waveform is left-aligned.  2017 Microchip Technology Inc. DS60001476B-page 2203 SAMA5D2 SERIES 56.7.46 PWM Channel Dead Time Register Name: PWM_DTx [x=0..3] Address: 0xF802C218 [0], 0xF802C238 [1], 0xF802C258 [2], 0xF802C278 [3] Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 DTL 23 22 21 20 DTL 15 14 13 12 DTH 7 6 5 4 DTH This register can only be written if bits WPSWS4 and WPHWS4 are cleared in the PWM Write Protection Status Register. Only the first 16 bits (dead-time counter size) of fields DTH and DTL are significant. DTH: Dead-Time Value for PWMHx Output Defines the dead-time value for PWMHx output. This value must be defined between 0 and the value (CPRD – CDTY) (PWM_CPRDx and PWM_CDTYx). DTL: Dead-Time Value for PWMLx Output Defines the dead-time value for PWMLx output. This value must be defined between 0 and CDTY (PWM_CDTYx). DS60001476B-page 2204  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.47 PWM Channel Dead Time Update Register Name: PWM_DTUPDx [x=0..3] Address: 0xF802C21C [0], 0xF802C23C [1], 0xF802C25C [2], 0xF802C27C [3] Access: 31 Write-only 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 DTLUPD 23 22 21 20 DTLUPD 15 14 13 12 DTHUPD 7 6 5 4 DTHUPD This register can only be written if bits WPSWS4 and WPHWS4 are cleared in the PWM Write Protection Status Register. This register acts as a double buffer for the DTH and DTL values. This prevents an unexpected waveform when modifying the dead-time values. Only the first 16 bits (dead-time counter size) of fields DTHUPD and DTLUPD are significant. DTHUPD: Dead-Time Value Update for PWMHx Output Defines the dead-time value for PWMHx output. This value must be defined between 0 and the value (CPRD – CDTY) (PWM_CPRDx and PWM_CDTYx). This value is applied only at the beginning of the next channel x PWM period. DTLUPD: Dead-Time Value Update for PWMLx Output Defines the dead-time value for PWMLx output. This value must be defined between 0 and CDTY (PWM_CDTYx). This value is applied only at the beginning of the next channel x PWM period.  2017 Microchip Technology Inc. DS60001476B-page 2205 SAMA5D2 SERIES 56.7.48 PWM Channel Mode Update Register Name: PWM_CMUPDx [x=0..3] Address: 0xF802C400 [0], 0xF802C420 [1], 0xF802C440 [2], 0xF802C460 [3] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 CPOLINVUP 12 – 11 – 10 – 9 CPOLUP 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register can only be written if bits WPSWS2 and WPHWS2 are cleared in the PWM Write Protection Status Register. This register acts as a double buffer for the CPOL value. This prevents an unexpected waveform when modifying the polarity value. CPOLUP: Channel Polarity Update The write of this bit is taken into account only if the bit CPOLINVUP is written at ‘0’ at the same time. 0: The OCx output waveform (output from the comparator) starts at a low level. 1: The OCx output waveform (output from the comparator) starts at a high level. CPOLINVUP: Channel Polarity Inversion Update If this bit is written at ‘1’, the write of the bit CPOLUP is not taken into account. 0: No effect. 1: The OCx output waveform (output from the comparator) is inverted. DS60001476B-page 2206  2017 Microchip Technology Inc. SAMA5D2 SERIES 56.7.49 PWM External Trigger Register Name: PWM_ETRGx [x=1..2] Address: 0xF802C42C [1], 0xF802C434 [2] Access: Read/Write 31 RFEN 30 TRGSRC 29 TRGFILT 28 TRGEDGE 27 – 26 – 25 24 23 22 21 20 19 18 17 16 11 10 9 8 3 2 1 0 TRGMODE MAXCNT 15 14 13 12 MAXCNT 7 6 5 4 MAXCNT MAXCNT: Maximum Counter value Maximum channel x counter value measured at the TRGINx event since the last read of the register. At the TRGINx event, if the channel x counter value is greater than the stored MAXCNT value, then MAXCNT is updated by the channel x counter value. TRGMODE: External Trigger Mode Value Name Description 0 OFF 1 MODE1 External PWM Reset Mode 2 MODE2 External PWM Start Mode 3 MODE3 Cycle-by-cycle Duty Mode External trigger is not enabled. TRGEDGE: Edge Selection Value Name 0 FALLING_ZERO 1 RISING_ONE Description TRGMODE = 1: TRGINx event detection on falling edge. TRGMODE = 2, 3: TRGINx active level is 0 TRGMODE = 1: TRGINx event detection on rising edge. TRGMODE = 2, 3: TRGINx active level is 1 TRGFILT: Filtered input 0: The external trigger input x is not filtered. 1: The external trigger input x is filtered. RFEN: Recoverable Fault Enable 0: The TRGINx signal does not generate a recoverable fault. 1: The TRGINx signal generate a recoverable fault in place of the fault x input. TRGSRC: Trigger Source 0: The TRGINx signal is driven by the PWMEXTRGx input. 1: The TRGINx signal is driven by the Analog Comparator Controller.  2017 Microchip Technology Inc. DS60001476B-page 2207 SAMA5D2 SERIES 56.7.50 PWM Leading-Edge Blanking Register Name: PWM_LEBRx [x=1..2] Address: 0xF802C430 [1], 0xF802C438 [2] Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 PWMHREN 18 PWMHFEN 17 PWMLREN 16 PWMLFEN 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 5 4 3 LEBDELAY 2 1 0 LEBDELAY: Leading-Edge Blanking Delay for TRGINx Leading-edge blanking duration for external trigger x input. The delay is calculated according to the following formula: LEBDELAY = (fperipheral clock × Delay) + 1 PWMLFEN: PWML Falling Edge Enable 0: Leading-edge blanking is disabled on PWMLx output falling edge. 1: Leading-edge blanking is enabled on PWMLx output falling edge. PWMLREN: PWML Rising Edge Enable 0: Leading-edge blanking is disabled on PWMLx output rising edge. 1: Leading-edge blanking is enabled on PWMLx output rising edge. PWMHFEN: PWMH Falling Edge Enable 0: Leading-edge blanking is disabled on PWMHx output falling edge. 1: Leading-edge blanking is enabled on PWMHx output falling edge. PWMHREN: PWMH Rising Edge Enable 0: Leading-edge blanking is disabled on PWMHx output rising edge. 1: Leading-edge blanking is enabled on PWMHx output rising edge. DS60001476B-page 2208  2017 Microchip Technology Inc. SAMA5D2 SERIES 57. Secure Fuse Controller (SFC) 57.1 Description The Secure Fuse Controller (SFC) interfaces the system with electrical fuses in a secure way. The default value of a fuse is logic ‘0’ (not programmed). A programmed fuse is logic ‘1’. An electrical fuse matrix is a type of non-volatile memory. Each fuse in the matrix can be programmed only one time. They are typically used to store calibration bits for analog cells such as oscillators, configuration settings, chip identifiers or cryptographic keys. A specific number of fuse bits are programmed during the production tests through the test interface. The remaining 544 fuse bits are programmed by the user and by software through the user interface. The SFC automatically reads the fuse values on start-up and stores them in 32-bit registers in order to make them accessible by the software. Only fuses set to level ‘1’ are programmed. Several security mechanisms make irregular data recovery more complex to achieve. 57.2 Embedded Characteristics • Fuse bits partitioned into two areas: - Reserved area - 544-bit user area • Program and read the fuse states by software • Automatic check of programmed fuses • Detection of irregular alteration of the fuse states in reserved area during start-up and report • Live detection of irregular alteration of all the fuse states and report • Part of fuse states maskable for reading  2017 Microchip Technology Inc. DS60001476B-page 2209 SAMA5D2 SERIES 57.3 Block Diagram Figure 57-1: SFC Block Diagram AHB Fuse States Fuse States User Interface Bridge APB Fuse Cell(s) Secure Fuse Controller (SFC) Controls Fuse cells protocol Security error SFC interrupt 57.4 57.4.1 Security Controller AIC (Advanced Interrupt Controller) Functional Description Accessing the SFC Setting the write-once FUSE bit in the SFR_SECURE register disables access to the Secure Fuse Controller (SFC). 57.4.2 Fuse Partitioning The fuses are split into a user area of 544 bits and a reserved area. The reserved area is typically used to store calibration bits for analog cells such as oscillators, configuration settings, chip identifiers, etc. The user area fuses are programmed later on by the user. 57.4.3 Fuse Integrity Checking The SFC automatically reads the fuses values at start-up and stores them in 32-bit registers in order to make them accessible by software. At this time, the SFC checks the integrity of the fuse states in the reserved area. If an inconsistency is detected, the CHECK error flag (named ACE for the reserved area) in the Status Register (SFC_SR) is set to ‘1’ and can trigger an interrupt. This flag is automatically cleared at ‘0’, when the Status Register (SFC_SR) is read. 57.4.4 Fuse Integrity Live Checking The SFC automatically checks the integrity of all fuse states at every time after the start-up is finished. This ensures that the fuses states cannot be changed without notice. If an inconsistency is detected, the LCHECK error flag in the Status Register (SFC_SR) is set to ‘1’ and can trigger an interrupt. This flag is automatically cleared at ‘0’, when the Status Register (SFC_SR) is read. 57.4.5 57.4.5.1 Fuse Access Fuse Reading The fuse states are automatically latched at core start-up and are available for reading in the Data Registers (SFC_DRx). The fuse states of bits 0 to 31 are available in the Data Register 0 (SFC_DR0), the fuse states of bits 32 to 63 are available in the Data Register 1 (SFC_DR1) and so on. When fuse programming is performed, the fuse states are automatically updated in the Data Registers (SFC_DRx). DS60001476B-page 2210  2017 Microchip Technology Inc. SAMA5D2 SERIES 57.4.5.2 Fuse Programming All the fuses can be written by software. The sequence of instructions to program fuses is the following: 1. 2. 3. 4. Write the key code 0xFB in the Key Register (SFC_KR). Write the word to program in the corresponding Data Register (SFC_DRx). For example, if fuses 0 to 31 must be programmed, Data Register 0 (SFC_DR0) must be written. If fuses 32 to 61 must be programmed, Data Register 1 (SFC_DR1) must be written. Only the data bits set to level ‘1’ are programmed. Wait for flag PGMC to rise in the Status Register (SFC_SR) by polling or interrupt. Check the value of flag PGMF: if it is set to 1, it means that the programming procedure failed. After programming, the fuses are read back in the corresponding SFC_DRx. 57.4.5.3 Fuse Masking It is possible to mask a fuse array. Once the fuse masking is enabled, the data registers from SFC_DR20 to SFC_DR23 are read at a value of ‘0’, regardless of the fuse state (the registers that are masked depend on the SFC hardware customizing). To activate fuse masking, the MSK bit of the SFC Mode Register (SFC_MR) must be written to level ‘1’. The MSK bit is set-only. Only a hardware reset can disable fuse masking. The MSK bit has no effect on the programming of masked fuses. 57.4.6 Fuse Functions The “Fuse Box Controller” section defines the fuse bits that can be used as general purpose bits when standard boot is used. If secure boot is used, refer to the device “Secure Boot Strategy” application note included in the Secure Package.  2017 Microchip Technology Inc. DS60001476B-page 2211 SAMA5D2 SERIES 57.5 Secure Fuse Controller (SFC) User Interface Table 57-1: Offset Register Mapping Register Name Access Reset 0x00 SFC Key Register SFC_KR Write-only – 0x04 SFC Mode Register SFC_MR Read/Write 0x0 Reserved – – – 0x10 SFC Interrupt Enable Register SFC_IER Write-only – 0x14 SFC Interrupt Disable Register SFC_IDR Write-only – 0x18 SFC Interrupt Mask Register SFC_IMR Read-only 0x0 0x1C SFC Status Register SFC_SR Read-only 0x0 0x20 SFC Data Register 0 SFC_DR0 Read/Write 0x0 0x24 SFC Data Register 1 SFC_DR1 Read/Write 0x0 ... ... ... ... SFC Data Register 23 SFC_DR23 Read/Write 0x0 Reserved – – – 0x08–0x0C ... 0x7C 0x80–0xFC DS60001476B-page 2212  2017 Microchip Technology Inc. SAMA5D2 SERIES 57.5.1 SFC Key Register Name: SFC_KR Address: 0xF804C000 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 6 5 4 3 2 1 0 KEY KEY: Key Code This field must be written with the correct key code (0xFB) prior to any write in a Data Register (SFC_DRx) in order to enable the fuse programming. For each write of SFC_DRx, this field must be written immediately before.  2017 Microchip Technology Inc. DS60001476B-page 2213 SAMA5D2 SERIES 57.5.2 SFC Mode Register Name: SFC_MR Address: 0xF804C004 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 SASEL 3 – 2 – 1 – 0 MSK MSK: Mask Data Registers 0: No effect 1: The data registers from SFC_DR20 to SFC_DR23 are always read at 0x00000000. Note: The MSK bit is set-only. Only a hardware reset can disable fuse masking. SASEL: Sense Amplifier Selection 0: Comparator type sense amplifier selected 1: Latch type sense amplifier selected DS60001476B-page 2214  2017 Microchip Technology Inc. SAMA5D2 SERIES 57.5.3 SFC Interrupt Enable Register Name: SFC_IER Address: 0xF804C010 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 ACE 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 LCHECK 3 – 2 – 1 PGMF 0 PGMC The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Enables the corresponding interrupt PGMC: Programming Sequence Completed Interrupt Enable PGMF: Programming Sequence Failed Interrupt Enable LCHECK: Live Integrity Check Error Interrupt Enable ACE: Area Check Error Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 2215 SAMA5D2 SERIES 57.5.4 SFC Interrupt Disable Register Name: SFC_IDR Address: 0xF804C014 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 ACE 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 LCHECK 3 – 2 – 1 PGMF 0 PGMC The following configuration values are valid for all listed bit names of this register: 0: No effect 1: Disables the corresponding interrupt PGMC: Programming Sequence Completed Interrupt Disable PGMF: Programming Sequence Failed Interrupt Disable LCHECK: Live Integrity Check Error Interrupt Disable ACE: Area Check Error Interrupt Disable DS60001476B-page 2216  2017 Microchip Technology Inc. SAMA5D2 SERIES 57.5.5 SFC Interrupt Mask Register Name: SFC_IMR Address: 0xF804C018 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 ACE 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 LCHECK 3 – 2 – 1 PGMF 0 PGMC The following configuration values are valid for all listed bit names of this register: 0: Corresponding interrupt is not enabled. 1: Corresponding interrupt is enabled. PGMC: Programming Sequence Completed Interrupt Mask PGMF: Programming Sequence Failed Interrupt Mask LCHECK: Live Integrity Checking Error Interrupt Mask ACE: Area Check Error Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 2217 SAMA5D2 SERIES 57.5.6 SFC Status Register Name: SFC_SR Address: 0xF804C01C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 ACE 16 APLE 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 LCHECK 3 – 2 – 1 PGMF 0 PGMC PGMC: Programming Sequence Completed (cleared on read) 0: No programming sequence completion since the last read of SFC_SR. 1: At least one programming sequence completion since the last read of SFC_SR. PGMF: Programming Sequence Failed (cleared on read) 0: No programming failure occurred during last programming sequence since the last read of SFC_SR. 1: A programming failure occurred since the last read of SFC_SR. LCHECK: Live Integrity Checking Error (cleared on read) 0: No live integrity check error since the last read of SFC_SR. 1: At least one live integrity check error since the last read of SFC_SR. APLE: Area Programming Lock Error (cleared on read) 0: No programming attempt has been made in the locked area since the last read of SFC_SR. 1: A programming attempt has been made in the locked area since the last read of SFC_SR. ACE: Area Check Error (cleared on read) 0: No check error in the reserved area since the last read of SFC_SR. 1: At least one check error in the reserved area since the last read of SFC_SR. DS60001476B-page 2218  2017 Microchip Technology Inc. SAMA5D2 SERIES 57.5.7 SFC Data Register x Name: SFC_DRx [x=0..23] Address: 0xF804C020 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 DATA 23 22 21 20 DATA 15 14 13 12 DATA 7 6 5 4 DATA DATA: Fuse Data READ: Reports the state of the corresponding fuses. WRITE: The data to be programmed in the corresponding fuses. Only bits with a value of ‘1’ are programmed. Writing this register automatically triggers a programming sequence of the corresponding fuses. Note that a write to the Key Register (SFC_KR) with the correct key code must always precede any write to SFC_DRx.  2017 Microchip Technology Inc. DS60001476B-page 2219 SAMA5D2 SERIES 58. Integrity Check Monitor (ICM) 58.1 Description The Integrity Check Monitor (ICM) is a DMA controller that performs hash calculation over multiple memory regions through the use of transfer descriptors located in memory (ICM Descriptor Area). The Hash function is based on the Secure Hash Algorithm (SHA). The ICM integrates two modes of operation. The first one is used to hash a list of memory regions and save the digests to memory (ICM Hash Area). The second mode is an active monitoring of the memory. In that mode, the hash function is evaluated and compared to the digest located at a predefined memory address (ICM Hash Area). If a mismatch occurs, an interrupt is raised. See Figure 58-1 for an example of fourregion monitoring. Hash and Descriptor areas are located in Memory instance i2, and the four regions are split in memory instances i0 and i1. Figure 58-1: Four-region Monitoring Example Processor Interrupt Controller ICM System Interconnect Memory i0 Memory Region 0 Memory Region 1 Memory i1 Memory i2 Memory Region 2 ICM Hash Area Memory Region 3 ICM Descriptor Area The ICM SHA engine is compliant with the American FIPS (Federal Information Processing Standard) Publication 180-2 specification. The following terms are concise definitions of the ICM concepts used throughout this document: • • • • Region—a partition of instruction or data memory space Region Descriptor—a data structure stored in memory, defining region attributes Region Attributes—region start address, region size, region SHA engine processing mode, Write Back or Compare function mode Context Registers—a set of ICM non-memory-mapped, internal registers which are automatically loaded, containing the attributes of the region being processed • Main List—a list of region descriptors. Each element associates the start address of a region with a set of attributes. • Secondary List—a linked list defined on a per region basis that describes the memory layout of the region (when the region is noncontiguous) • Hash Area—predefined memory space where the region hash results (digest) are stored 58.2 • • • • • • Embedded Characteristics DMA AHB Master Interface Supports Monitoring of up to 4 Non-Contiguous Memory Regions Supports Block Gathering Using Linked Lists Supports Secure Hash Algorithm (SHA1, SHA224, SHA256) Compliant with FIPS Publication 180-2 Configurable Processing Period: DS60001476B-page 2220  2017 Microchip Technology Inc. SAMA5D2 SERIES - When SHA1 algorithm is processed, the runtime period is either 85 or 209 clock cycles. - When SHA256 or SHA224 algorithm is processed, the runtime period is either 72 or 194 clock cycles. • Programmable Bus Burden 58.3 Block Diagram Figure 58-2: Integrity Check Monitor Block Diagram APB Host Interface Configuration Registers SHA Hash Engine Context Registers Monitoring FSM Integrity Scheduler Master DMA Interface Bus Layer  2017 Microchip Technology Inc. DS60001476B-page 2221 SAMA5D2 SERIES 58.4 Product Dependencies 58.4.1 Power Management The peripheral clock is not continuously provided to the ICM. The programmer must first enable the ICM clock in the Power Management Controller (PMC) before using the ICM. 58.4.2 Interrupt Sources The ICM interface has an interrupt line connected to the Interrupt Controller. Handling the ICM interrupt requires programming the interrupt controller before configuring the ICM. Table 58-1: Peripheral IDs Instance ID ICM 8 58.5 58.5.1 Functional Description Overview The Integrity Check Monitor (ICM) is a DMA controller that performs SHA-based memory hashing over memory regions. As shown in Figure 58-2, it integrates a DMA interface, a Monitoring Finite State Machine (FSM), an integrity scheduler, a set of context registers, a SHA engine, an interface for configuration and status registers. The ICM integrates a Secure Hash Algorithm engine (SHA). This engine requires a message padded according to FIPS180-2 specification when used as a SHA calculation unit only. Otherwise, if the ICM is used as integrated check for memory content, the padding is not mandatory. The SHA module produces an N-bit message digest each time a block is read and a processing period ends. N is 160 for SHA1, 224 for SHA224, 256 for SHA256. When the ICM module is enabled, it sequentially retrieves a circular list of region descriptors from the memory (Main List described in Figure 58-3). Up to four regions may be monitored. Each region descriptor is composed of four words indicating the layout of the memory region (see Figure 58-4). It also contains the hashing engine configuration on a per-region basis. As soon as the descriptor is loaded from the memory and context registers are updated with the data structure, the hashing operation starts. A programmable number of blocks (see TRSIZE field of the ICM_RCTRL structure member) is transferred from the memory to the SHA engine. When the desired number of blocks have been transferred, the digest is either moved to memory (Write Back function) or compared with a digest reference located in the system memory (Compare function). If a digest mismatch occurs, an interrupt is triggered if unmasked. The ICM module passes through the region descriptor list until the end of the list marked by an end of list marker (WRAP or EOM bit in ICM_RCFG structure member set to one). To continuously monitor the list of regions, the WRAP bit must be set to one in the last data structure and EOM must be cleared. DS60001476B-page 2222  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 58-3: ICM Region Descriptor and Hash Areas Main List infinite loop when wrap bit is set End of Region N WRAP=1 Region N Descriptor ICM Descriptor Area - Contiguous Read-only Memory Secondary List End of Region 1 List WRAP=0 Region 1 Descriptor End of Region 0 WRAP=0 Region 0 Descriptor Region N Hash ICM Hash Area Contiguous Read-write once Memory Region 1 Hash Region 0 Hash Each region descriptor supports gathering of data through the use of the Secondary List. Unlike the Main List, the Secondary List cannot modify the configuration attributes of the region. When the end of the Secondary List has been encountered, the ICM returns to the Main List. Memory integrity monitoring can be considered as a background service and the mandatory bandwidth shall be very limited. In order to limit the ICM memory bandwidth, use ICM_CFG.BBC to control the ICM memory load.  2017 Microchip Technology Inc. DS60001476B-page 2223 SAMA5D2 SERIES Figure 58-4: Region Descriptor Main List Region 3 Descriptor Region 2 Descriptor Optional Region 0 Secondary List Region 1 Descriptor ICM_DSCR Region 0 Descriptor End of Region 0 0x00C Region NEXT 0x00C Region NEXT 0x008 Region CTRL 0x008 Region CTRL 0x004 Region CFG 0x004 Unused 0x000 Region ADDR 0x000 Region ADDR Figure 58-5 shows an example of the mandatory ICM settings to monitor three memory data blocks of the system memory (defined as two regions) with one region being not contiguous (two separate areas) and one contiguous memory area. For each region, the SHA algorithm may be independently selected (different for each region). The wrap allows continuous monitoring. DS60001476B-page 2224  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 58-5: Example: Monitoring of 3 Memory Data Blocks (Defined as 2 Regions) Size of region 1 block (S1) R S i egi Bl n g on oc l e 1 k Da ta System Memory, data areas System Memory, region descriptor structure WRAP=1 effect @r1d NEXT=0 @md+28 S1 @md+24 WRAP=1, etc @md+20 Size of region 0 block 1 (S0B1) R D egi at o n a Bl 0 oc k 1 3 1 @r1d @md+16 NEXT=@sd @md+12 S0B0 @md+8 WRAP=0, etc @md+4 @r0db0 @md @r0db1 Region 0 Main Descriptor 1 2 R D egi at o n a Bl 0 oc k 0 3 Size of region 0 block 0 (S0B0) 2 Region 1 Single Descriptor NEXT=0 @sd+12 S0B1 @sd+8 unused @sd+4 @r0db1 @sd Region 0 Second Descriptor @r0db0 58.5.2 ICM Region Descriptor Structure The ICM Region Descriptor Area is a contiguous area of system memory that the controller and the processor can access. When the ICM is activated, the controller performs a descriptor fetch operation at *(ICM_DSCR) address. If the Main List contains more than one descriptor (i.e., more than one region is to be monitored), the fetch address is *(ICM_DSCR) + (RID 7 (HMAC) SHA_MR.UIEHV SHA_CR.FIRST  2017 Microchip Technology Inc. Set Clear end of 1st block DS60001476B-page 2313 SAMA5D2 SERIES 61.4.6 Automatic Padding The SHA module features an automatic padding computation to speed up the execution of the algorithm. The automatic padding function requires the following information: • Complete message size in bytes to be written in the MSGSIZE field of the SHA Message Size register (SHA_MSR). The size of the message is written at the end of the last block, as required by the FIPS180-2 specification (the size is automatically converted into a bit-size). • Number of remaining bytes (to write in the SHA_IDATARx) to be written in the BYTCNT field of the SHA Bytes Count register (SHA_BCR). Automatic padding occurs when the BYTCNT field reaches 0. At each write in the SHA Input registers, the BYTCNT field value is decreased by the number of bytes written. The BYTCNT field value must be written with the same value as the MSGSIZE field value if the full message is processed. If the message is partially preprocessed and an initial hash value is used, BYTCNT must be written with the remaining bytes to hash while MSGSIZE holds the message size. To disable the automatic padding feature, the MSGSIZE and BYTCNT fields must be configured with 0. DS60001476B-page 2314  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.4.7 Automatic Check The SHA module features an automatic check of the hash result with the expected hash. A check failure can generate an interrupt if configured in the SHA Interrupt Enable register (SHA_IER). Automatic check requires the automatic padding feature to be enabled (MSGSIZE and BYTCNT fields must be greater than 0). There are two methods to configure the expected hash result: • if SHA_MR.CHECK = 1, the expected hash result is read from the internal register (IR1). This method cannot be used when HMAC algorithms is selected because this register is already used to store user initial hash values for the second hash processing. IR1 cannot be read by software. • If SHA_MR.CHECK = 2, the expected hash result is written in the SHA_IDATARx after the message. When SHA_MR.CHECK = 2, the method can provide more flexibility of use if a message is stored in system memory together with its expected hash result. A DMA with linked list can be used to ease the transfer of the message and its expected hash result. Figure 61-2: Message and Expected Hash Result Memory Mapping SHA_MR.CHECK=2 System Memory SHA User Interface @m+60 @m+56 h @c+4 @c No DMA used SHA_MR.SMOD= 0,1 SHA_IDATAR0 write access n+14 SHA_IDATAR13 write access n+13 @m+52 es s @m+4 @m M M es sa ag e ge to to ha ha sh sh Size of SHA Block SHA_IDATAR7 write access n+21 as @c+24 E R xpe es c ul ted t H Size of Hash Result E R xpe es c ul ted t H as h @c+28 SHA_IDATAR1 write access n+1 SHA_IDATAR0 write access n DMA used SHA_MR.SMOD=2 DMA automatically loads the entire buffers into SHA_IDATAR0 only * * * SHA_IDATAR0 write access n to n+21 * the 3 upper bytes of access n+13 are “don’t care” The number of 32-bit words of the hash result to check with the expected hash can be selected with SHA_MR.CHKCNT. The status of the check is available in the CHKST field in the SHA Interrupt Status register (SHA_ISR). An interrupt can be generated (if enabled) when the check is completed. The check occurs several clock cycles after the computation of the requested hash, so the interrupt and the CHECKF bit are set several clock cycles after the DATRDY flag of the SHA_ISR. 61.4.8 Protocol Layers Improved Performances The SHA can be tightly coupled to the AES module to improve performances when processing protocol layers such as IPsec or OpenSSL. When the AES is configured to be tightly coupled to SHA (AES_MR), SHA must be always configured in Double Buffer mode (SHA_MR.DUALBUFF = 1). Refer to the section “Advanced Encryption Standard (AES)” for details.  2017 Microchip Technology Inc. DS60001476B-page 2315 SAMA5D2 SERIES 61.4.9 Start Modes SHA_MR.SMOD is used to select the Hash Processing Start mode. 61.4.9.1 Manual Mode In Manual mode, the sequence is as follows: 1. 2. 3. 4. 5. 6. 7. 8. 9. Set SHA_IER.DATRDY (Data Ready) , depending on whether an interrupt is required at the end of processing. If the initial hash values differ from the FIPS standard, set SHA_MR.UIHV and/or SHA_MR.UIEHV. If the initial hash values comply with the FIPS180-2 specification, clear SHA_MR.UIHV and/or SHA_MR.UIEHV. If automatic padding is required, configure SHA_MSR.MSGSIZE with the number of bytes of the message, and configure SHA_BCR.BYTCNT with the remaining number of bytes to write. The BYTCNT field must be written with a value different from MSGSIZE field value if the message is preprocessed and completed by using user initial hash values. If automatic padding is not required, configure SHA_MSR.MSGSIZE and SHA_BCR.BYTCNT to 0. For the first block of a message, the FIRST command must be set by writing a 1 into the corresponding bit of the Control register (SHA_CR). For the other blocks, there is nothing to write. Write the block to be processed in the SHA_IDATARx. To begin processing, set SHA_CR.START. When processing is completed, the bit DATRDY in the Interrupt Status register (SHA_ISR) rises. If an interrupt has been enabled by setting SHA_IER.DATRDY, the interrupt line of the SHA is activated. Repeat the write procedure for each block, start procedure and wait for the interrupt procedure up to the last block of the entire message. Each time the start procedure is complete, the DATRDY flag is cleared. After the last block is processed (DATRDY flag is set, if an interrupt has been enabled by setting SHA_IER.DATRDY, the interrupt line of the SHA is activated), read the message digest in the Output Data registers. The DATRDY flag is automatically cleared when reading the SHA_IODATARx registers. 61.4.9.2 Auto Mode In Auto mode, processing starts as soon as the correct number of SHA_IDATARx is written. No action in the SHA_CR is necessary. 61.4.9.3 DMA Mode The DMA can be used in association with the SHA to perform the algorithm on a complete message without any action by the software during processing. SHA_MR.SMOD must be configured to 2. The DMA must be configured with non-incremental addresses. The start address of any transfer descriptor must be set to point to the SHA_IDATAR0. The DMA chunk size must be set to transfer, for each trigger request, 16 words of 32 bits. The FIRST bit of the SHA_CR must be set before starting the DMA when the first block is transferred. The DMA generates an interrupt when the end of buffer transfer is completed but the SHA processing is still in progress. The end of SHA processing is indicated by the flag DATRDY in the SHA_ISR. If automatic padding is disabled, the end of SHA processing requires two interrupts to be verified. The DMA end of transfer interrupt must be verified first, then the SHA DATRDY interrupt must be enabled and verified (see Figure 61-3). If automatic padding is enabled, the end of SHA processing requires only one interrupt to be verified (see Figure 61-4). The DMA end of transfer is not required, so the SHA DATRDY interrupt must be enabled prior to start the DMA and DATRDY interrupt is the only one to be verified. DS60001476B-page 2316  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 61-3: interrupts Processing with DMA Enable DMA Channels associated with SHA_IDATARx registers Message Processing (Multiple Block) DMA status flag for end of buffer transfer Write accesses into SHA_IDATARx DATRDY Message fully transferred Figure 61-4: Message fully processed SHA result can be read interrupts Processing with DMA and Automatic Padding Enable DMA Channels associated with SHA_IDATARx registers Message Processing (Multiple Block) DMA status flag for end of buffer transfer Write accesses into SHA_IDATARx DATRDY Message fully processed SHA result can be read 61.4.9.4 SHA Register Endianness In ARM processor-based products, the system bus and processors manipulate data in little-endian form. The SHA interface requires littleendian format words. However, in accordance with the protocol of FIPS 180-2 specification, data is collected, processed and stored by the SHA algorithm in big-endian form. The following example illustrates how to configure the SHA: If the first 64 bits of a message (according to FIPS 180-2, i.e., big-endian format) to be processed is 0xcafedeca_01234567, then the SHA_IDATAR0 and SHA_IDATAR1 registers must be written with the following pattern: • SHA_IDATAR0 = 0xcadefeca • SHA_IDATAR1 = 0x67452301 In a little-endian system, the message (according to FIPS 180-2) starting with pattern 0xcafedeca_01234567 is stored into memory as follows: - 0xca stored at initial offset (for example 0x00), then 0xfe stored at initial offset + 1 (i.e., 0x01), 0xde stored at initial offset + 2 (i.e., 0x02), 0xca stored at initial offset + 3 (i.e., 0x03). If the message is received through a serial-to-parallel communication channel, the first received character is 0xca and it is stored at the first memory location (initial offset). The second byte, 0xfe, is stored at initial offset + 1. When reading on a 32-bit little-endian system bus, the first word read back from system memory is 0xcadefeca. When the SHA_IODATARx registers are read, the hash result is organized in little-endian format, allowing system memory storage in the same format as the message. Taking an example from the FIPS 180-2 specification Appendix B.1, the endian conversion can be observed.  2017 Microchip Technology Inc. DS60001476B-page 2317 SAMA5D2 SERIES For this example, the 512-bit message is: 0x6162638000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000018 and the expected SHA-256 result is: 0xba7816bf_8f01cfea_414140de_5dae2223_b00361a3_96177a9c_b410ff61_f20015ad If the message has not already been stored in the system memory, the first step is to convert the input message to little-endian before writing to the SHA_IDATARx registers. This would result in a write of: SHA_IDATAR0 = 0x80636261...... SHA_IDATAR15 = 0x18000000 The data in the output message digest registers, SHA_IODATARx, contain SHA_IODATAR0 = 0xbf1678ba... SHA_IODATAR7 = 0xad1500f2 which is the little-endian format of 0xba7816bf,..., 0xf20015ad. Reading SHA_IODATAR0 to SHA_IODATAR1 and storing into a little-endian memory system forces hash results to be stored in the same format as the message. When the output message is read, the user can convert back to big-endian for a resulting message value of: 0xba7816bf_8f01cfea_414140de_5dae2223_b00361a3_96177a9c_b410ff61_f20015ad 61.4.10 61.4.10.1 Security Features Unspecified Register Access Detection When an unspecified register access occurs, the URAD bit in the SHA_ISR is set. Its source is then reported in the Unspecified Register Access Type field (URAT). Only the last unspecified register access is available through the URAT field. Several kinds of unspecified register accesses can occur: • • • • SHA_IDATARx written during data processing in DMA mode SHA_IODATARx read during data processing SHA_MR written during data processing Write-only register read access The URAD bit and the URAT field can only be reset by the SWRST bit in the SHA_CR. DS60001476B-page 2318  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5 Secure Hash Algorithm (SHA) User Interface Table 61-3: Offset Register Mapping Register Name Access Reset 0x00 Control Register SHA_CR Write-only – 0x04 Mode Register SHA_MR Read/Write 0x0000100 Reserved – – – 0x10 Interrupt Enable Register SHA_IER Write-only – 0x14 Interrupt Disable Register SHA_IDR Write-only – 0x18 Interrupt Mask Register SHA_IMR Read-only 0x0 0x1C Interrupt Status Register SHA_ISR Read-only 0x0 0x20 Message Size Register SHA_MSR Read/Write 0x0 Reserved – – – Bytes Count Register SHA_BCR Read/Write 0x0 Reserved – Input Data 0 Register SHA_IDATAR0 ... ... 0x7C Input Data 15 Register 0x80 0x08–0x0C 0x24–0x2C 0x30 0x34–0x3C – – Write-only – ... ... SHA_IDATAR15 Write-only – Input/Output Data 0 Register SHA_IODATAR0 Read/Write 0x0 ... ... ... ... 0x9C Input/Output Data 7 Register SHA_IODATAR7 Read/Write 0x0 0xA0 Input/Output Data 8 Register SHA_IODATAR8 Read/Write 0x0 ... ... ... ... Input/Output Data 15 Register SHA_IODATAR15 Read/Write 0x0 – – – – 0x40 ... ... ... 0xBC 0xC0–0xE8 Reserved 0xEC–0xFC Reserved  2017 Microchip Technology Inc. – – DS60001476B-page 2319 SAMA5D2 SERIES 61.5.1 SHA Control Register Name: SHA_CR Address: 0xF0028000 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – WUIEHV WUIHV – – – SWRST 7 6 5 4 3 2 1 0 – – – FIRST – – – START START: Start Processing 0: No effect. 1: Starts manual hash algorithm process. FIRST: First Block of a Message 0: No effect. 1: Indicates that the next block to process is the first one of a message. SWRST: Software Reset 0: No effect. 1: Resets the SHA. A software-triggered hardware reset of the SHA interface is performed. WUIHV: Write User Initial Hash Values 0: SHA_IDATARx accesses are routed to the data registers. 1: SHA_IDATARx accesses are routed to the internal registers (IR0). WUIEHV: Write User Initial or Expected Hash Values 0: SHA_IDATARx accesses are routed to the data registers. 1: SHA_IDATARx accesses are routed to the internal registers (IR1). DS60001476B-page 2320  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5.2 SHA Mode Register Name: SHA_MR Address: 0xF0028004 Access: Read/Write 31 30 29 28 CHKCNT 27 26 – – 25 24 CHECK 23 22 21 20 19 18 17 16 – – – – – – – DUALBUFF 15 14 13 12 11 10 9 8 – – – – ALGO 7 6 5 4 3 2 – UIEHV UIHV PROCDLY – – 1 0 SMOD SMOD: Start Mode Value Name Description 0 MANUAL_START Manual mode 1 AUTO_START Auto mode 2 IDATAR0_START SHA_IDATAR0 access only mode (mandatory when DMA is used) Values not listed in the table must be considered as “reserved”. If a DMA transfer is used, configure the SMOD value to 2. See Section 61.4.9.3 “DMA Mode” for details. PROCDLY: Processing Delay Value Name Description 0 SHORTEST SHA processing runtime is the shortest one 1 LONGEST SHA processing runtime is the longest one (reduces the SHA bandwidth requirement, reduces the system bus overload) When SHA1 algorithm is processed, runtime period is either 85 or 209 clock cycles. When SHA256 or SHA224 algorithm is processed, runtime period is either 72 or 194 clock cycles. When SHA384 or SHA512 algorithm is processed, runtime period is either 88 or 209 clock cycles. UIHV: User Initial Hash Value Registers 0: The SHA algorithm is started with the standard initial values as defined in the FIPS180-2 specification. 1: The SHA algorithm is started with the user initial hash values stored in the internal register 0 (IR0). If HMAC is configured, UIHV has no effect (i.e. IR0 is selected). UIEHV: User Initial or Expected Hash Value Registers 0: The SHA algorithm is started with the standard initial values as defined in the FIPS180-2 specification. 1: The SHA algorithm is started with the user initial hash values stored in the internal register 1 (IR1). If HMAC is configured, UIEHV has no effect (i.e. IR1 is always selected). ALGO: SHA Algorithm Value Name Description 0 SHA1 SHA1 algorithm processed 1 SHA256 SHA256 algorithm processed 2 SHA384 SHA384 algorithm processed  2017 Microchip Technology Inc. DS60001476B-page 2321 SAMA5D2 SERIES Value Name Description 3 SHA512 SHA512 algorithm processed 4 SHA224 SHA224 algorithm processed 8 HMAC_SHA1 HMAC algorithm with SHA1 Hash processed 9 HMAC_SHA256 HMAC algorithm with SHA256 Hash processed 10 HMAC_SHA384 HMAC algorithm with SHA384 Hash processed 11 HMAC_SHA512 HMAC algorithm with SHA512 Hash processed 12 HMAC_SHA224 HMAC algorithm with SHA224 Hash processed Values not listed in the table must be considered as “reserved”. DUALBUFF: Dual Input Buffer Value Name Description 0 INACTIVE SHA_IDATARx and SHA_IODATARx cannot be written during processing of previous block. 1 ACTIVE SHA_IDATARx and SHA_IODATARx can be written during processing of previous block when SMOD value = 2. It speeds up the overall runtime of large files. CHECK: Hash Check Value Name Description 0 NO_CHECK No check is performed 1 CHECK_EHV Check is performed with expected hash stored in internal expected hash value registers. 2 CHECK_MESSAGE Check is performed with expected hash provided after the message. Values not listed in table must be considered as “reserved”. CHKCNT: Check Counter Number of 32-bit words to check. The value 0 indicates that the number of words to compare will be based on the algorithm selected (5 words for SHA1, 7 words for SHA224, 8 words for SHA256, 12 words for SHA384, 16 words for SHA512). DS60001476B-page 2322  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5.3 SHA Interrupt Enable Register Name: SHA_IER Address: 0xF0028010 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – CHECKF 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. DATRDY: Data Ready Interrupt Enable URAD: Unspecified Register Access Detection Interrupt Enable CHECKF: Check Done Interrupt Enable  2017 Microchip Technology Inc. DS60001476B-page 2323 SAMA5D2 SERIES 61.5.4 SHA Interrupt Disable Register Name: SHA_IDR Address: 0xF0028014 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – CHECKF 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. DATRDY: Data Ready Interrupt Disable URAD: Unspecified Register Access Detection Interrupt Disable CHECKF: Check Done Interrupt Disable DS60001476B-page 2324  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5.5 SHA Interrupt Mask Register Name: SHA_IMR Address: 0xF0028018 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – CHECKF 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. DATRDY: Data Ready Interrupt Mask URAD: Unspecified Register Access Detection Interrupt Mask CHECKF: Check Done Interrupt Mask  2017 Microchip Technology Inc. DS60001476B-page 2325 SAMA5D2 SERIES 61.5.6 SHA Interrupt Status Register Name: SHA_ISR Address: 0xF002801C Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – CHECKF 11 10 9 8 – – – URAD CHKST 15 14 13 12 URAT 7 6 5 4 3 2 1 0 – – – WRDY – – – DATRDY DATRDY: Data Ready (cleared by writing a 1 to bit SWRST or START in SHA_CR, or by reading SHA_IODATARx) 0: Output data is not valid. 1: 512/1024-bit block process is completed. DATRDY is cleared when one of the following conditions is met: • Bit START in SHA_CR is set. • Bit SWRST in SHA_CR is set. • The hash result is read. WRDY: Input Data Register Write Ready 0: SHA_IDATAR0 cannot be written 1: SHA_IDATAR0 can be written URAD: Unspecified Register Access Detection Status (cleared by writing a 1 to SWRST bit in SHA_CR) 0: No unspecified register access has been detected since the last SWRST. 1: At least one unspecified register access has been detected since the last SWRST. URAT: Unspecified Register Access Type (cleared by writing a 1 to SWRST bit in SHA_CR) Value Description 0 SHA_IDATAR0 to SHA_IDATAR15 written during the data processing in DMA mode (URAD = 1 and URAT = 0 can occur only if DUALBUFF is cleared in SHA_MR). 1 Output Data Register read during the data processing. 2 SHA_MR written during the data processing. 3 Write-only register read access. Only the last Unspecified Register Access Type is available through the URAT field. CHECKF: Check Done Status (cleared by writing START or SWRST bits in SHA_CR or by reading SHA_IODATARx) 0: Hash check has not been computed. 1: Hash check has been computed, status is available in the CHKST bits. CHKST: Check Status (cleared by writing START or SWRST bits in SHA_CR or by reading SHA_IODATARx) Value 5 indicates identical hash values (expected hash = hash result). Any other value indicates different hash values. DS60001476B-page 2326  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5.7 SHA Message Size Register Name: SHA_MSR Address: 0xF0028020 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 MSGSIZE 23 22 21 20 MSGSIZE 15 14 13 12 MSGSIZE 7 6 5 4 MSGSIZE MSGSIZE: Message Size The size in bytes of the message. When MSGSIZE differs from 0, the SHA appends the corresponding value converted in bits after the padding section, as described in the FIPS180-2 specification. To disable automatic padding, MSGSIZE field must be written to 0.  2017 Microchip Technology Inc. DS60001476B-page 2327 SAMA5D2 SERIES 61.5.8 SHA Bytes Count Register Name: SHA_BCR Address: 0xF0028030 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 BYTCNT 23 22 21 20 BYTCNT 15 14 13 12 BYTCNT 7 6 5 4 BYTCNT BYTCNT: Remaining Byte Count Before Auto Padding When the hash processing starts from the beginning of a message (without preprocessed hash part), BYTCNT must be written with the same value as the MSGSIZE. If a part of the message has been already hashed and the hash does not start from the beginning, BYTCNT must be configured with the number of bytes remaining to process before padding section. When read, provides the size in bytes of message remaining to be written before the automatic padding starts. BYTCNT field is automatically updated each time a write occurs in the SHA_IDATARx and SHA_IODATARx. When BYTCNT reaches 0, the MSGSIZE is converted into bit count and appended at the end of the message after the padding as described in the FIPS180-2 specification. To disable automatic padding, MSGSIZE and BYTCNT fields must be written to 0. DS60001476B-page 2328  2017 Microchip Technology Inc. SAMA5D2 SERIES 61.5.9 SHA Input Data x Register Name: SHA_IDATARx [x=0..15] Address: 0xF0028040 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IDATA 23 22 21 20 IDATA 15 14 13 12 IDATA 7 6 5 4 IDATA IDATA: Input Data The 32-bit Input Data registers allow to load the data block used for hash processing. These registers are write-only to prevent the input data from being read by another application. SHA_IDATAR0 corresponds to the first word of the block, SHA_IDATAR15 to the last word of the last block in case SHA algorithm is set to SHA1, SHA224, SHA256 or SHA_IODATA15R to the last word of the block if SHA algorithm is SHA384 or SHA512 (see Section 61.5.10 “SHA Input/Output Data Register x”).  2017 Microchip Technology Inc. DS60001476B-page 2329 SAMA5D2 SERIES 61.5.10 SHA Input/Output Data Register x Name: SHA_IODATARx [x=0..15] Address: 0xF0028080 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IODATA 23 22 21 20 IODATA 15 14 13 12 IODATA 7 6 5 4 IODATA IODATA: Input/Output Data These registers can be used to read the resulting message digest and to write the second part of the message block when the SHA algorithm is SHA-384 or SHA-512. SHA_IODATA0R to SHA_IODATA15R can be written or read but reading these offsets does not return the content of corresponding parts (words) of the message block. Only results from SHA calculation can be read through these registers. When SHA processing is in progress, these registers return 0x0000. SHA_IODATAR0 corresponds to the first word of the message digest; SHA_IODATAR4 to the last one in SHA1 mode, SHA_ODATAR6 in SHA224, SHA_IODATAR7 in SHA256, SHA_IODATAR11 in SHA384 or SHA_IODATAR15 in SHA512. When SHA224 is selected, the content of SHA_ODATAR7 must be ignored. When SHA384 is selected, the content of SHA_IODATAR12 to SHA_IODATAR15 must be ignored. DS60001476B-page 2330  2017 Microchip Technology Inc. SAMA5D2 SERIES 62. Triple Data Encryption Standard (TDES) 62.1 Description The Triple Data Encryption Standard (TDES) is compliant with the American FIPS (Federal Information Processing Standard) Publication 46-3 specification. The TDES supports the four different confidentiality modes of operation (ECB, CBC, OFB and CFB), specified in the FIPS (Federal Information Processing Standard) Publication 81 and is compatible with the Peripheral Data Controller channels for all of these modes, minimizing processor intervention for large buffer transfers. The TDES key is loaded by the software. The software can write up to three 64-bit keys, each stored in two 32-bit write-only registers, i.e., Key x Word Registers TDES_KEYxWR0 and TDES_KEYxWR1. The input data (and initialization vector for some modes) are stored in two corresponding 32-bit write-only registers: Input Data Registers TDES_IDATAR0 and TDES_IDATAR1 Initialization Vector Registers TDES_IVR0 and TDES_IVR1 As soon as the initialization vector, the input data and the keys are configured, the encryption/decryption process may be started. Then the encrypted/decrypted data is ready to be read out on the two 32-bit Output Data registers (TDES_ODATARx) or through the DMA channels. 62.2 Embedded Characteristics • • • • • • • • • Supports Single Data Encryption Standard (DES) and Triple Data Encryption Standard (TDES) Compliant with FIPS Publication 46-3, Data Encryption Standard (DES) 64-bit Cryptographic Key for TDES Two-key or Three-key Algorithms for TDES 18-clock Cycles Encryption/Decryption Processing Time for DES 50-clock Cycles Encryption/Decryption Processing Time for TDES Supports eXtended Tiny Encryption Algorithm (XTEA) 128-bit key for XTEA and Programmable Round Number up to 64 Supports the Four Standard Modes of Operation specified in the FIPS Publication 81, DES Modes of Operation - Electronic Code Book (ECB) - Cipher Block Chaining (CBC) - Cipher Feedback (CFB) - Output Feedback (OFB) • 8-, 16-, 32- and 64-bit Data Sizes Possible in CFB Mode • Last Output Data Mode Allowing Optimized Message (Data) Authentication Code (MAC) Generation • Connection to DMA Optimizes Data Transfers for all Operating Modes 62.3 Product Dependencies 62.3.1 Power Management The TDES may be clocked through the Power Management Controller (PMC), so the programmer must first configure the PMC to enable the TDES clock. 62.3.2 Interrupt Sources The TDES interface has an interrupt line connected to the Interrupt Controller. In order to handle interrupts, the Interrupt Controller must be programmed before configuring the TDES. Table 62-1: Peripheral IDs Instance ID TDES 11  2017 Microchip Technology Inc. DS60001476B-page 2331 SAMA5D2 SERIES 62.4 Functional Description The Data Encryption Standard (DES) and the Triple Data Encryption Algorithm (TDES) specify FIPS-approved cryptographic algorithms that can be used to protect electronic data. The TDES bit in the TDES Mode Register (TDES_MR) is used to select either the single DES or the Triple DES mode. Encryption (enciphering) converts data to an unintelligible form called ciphertext. Decrypting (deciphering) the ciphertext converts the data back into its original form, called plaintext. The CIPHER bit in TDES_MR is used to choose between encryption and decryption. A DES is capable of using cryptographic keys of 64 bits to encrypt and decrypt data in blocks of 64 bits. This 64-bit key is defined in the Key 1 Registers (TDES_KEY1WRx ). A TDES key consists of three DES keys, which is also referred to as a key bundle. These three 64-bit keys are defined, respectively, in the Key 1, 2 and 3 Registers (TDES_KEY1WRx, TDES_KEY2WRx and TDES_KEY3WRx). In Triple DES mode (TDESMOD = 1 in TDES_MR), the KEYMOD bit in TDES_MR is used to choose between a two- and a three-key algorithm, as summarized in Table 62-2. Table 62-2: TDES Algorithms Summary Data Processing Sequence Steps Algorithm Mode First Second Third Encryption Encryption with Key 1 Decryption with Key 2 Encryption with Key 3 Decryption Decryption with Key 3 Encryption with Key 2 Decryption with Key 1 Encryption Encryption with Key 1 Decryption with Key 2 Encryption with Key 1 Decryption Decryption with Key 1 Encryption with Key 2 Decryption with Key 1 Three-key Two-key The input to the encryption processes of the CBC, CFB, and OFB modes includes, in addition to the plaintext, a 64-bit data block called the initialization vector (IV), which must be set in the Initialization Vector Registers (TDES_IVRx). The initialization vector is used in an initial step in the encryption of a message and in the corresponding decryption of the message. The XTEA algorithm can be used instead of DES/TDES by configuring the TDESMOD field in TDES_MR with the appropriate value 0x2. An XTEA key consists of a 128-bit key. They are defined in the Key 1 and 2 Registers. The number of rounds of XTEA is defined in TDES_XTEA_RNDR and can be programmed up to 64 (1 round = 2 Feistel network rounds). All the start and operating modes of the TDES algorithm can be applied to the XTEA algorithm. 62.4.1 Operating Modes The TDES supports the following operating modes: • • • • ECB—Electronic Code Book CBC—Cipher Block Chaining OFB—Output Feedback CFB—Cipher Feedback - CFB8 (CFB where the length of the data segment is 8 bits) - CFB16 (CFB where the length of the data segment is 16 bits) - CFB32 (CFB where the length of the data segment is 32 bits) - CFB64 (CFB where the length of the data segment is 64 bits) The data pre-processing, post-processing and data chaining for each mode are automatically performed. Refer to the FIPS Publication 81 for more complete information. These modes are selected by setting the OPMOD field in TDES_MR. In CFB mode, four data sizes are possible (8, 16, 32 and 64 bits), configurable by means of the CFBS field in TDES_MR (see Section 62.5.2 “TDES Mode Register”). 62.4.2 Start Modes The SMOD field in TDES_MR selects the Encryption (or Decryption) start mode. 62.4.2.1 Manual Mode The sequence is as follows: 1. Write the TDES_MR register with all required fields, including but not limited to SMOD and OPMOD. DS60001476B-page 2332  2017 Microchip Technology Inc. SAMA5D2 SERIES 2. 3. Write the 64-bit key(s) in the different Key Registers (TDES_KEYxWRx), depending on whether one, two or three keys are required. Write the initialization vector (or counter) in the Initialization Vector Registers (TDES_IVRx). Note: 4. 5. Set the bit DATRDY (Data Ready) in the TDES Interrupt Enable register (TDES_IER), depending on whether an interrupt is required or not at the end of processing. Write the data to be encrypted/decrypted in the authorized Input Data Registers (see Table 62-3). Note: 6. 7. 8. The Initialization Vector Registers concern all modes except ECB. In 32-, 16- and 8-bit CFB modes, writing to TDES_IDATAR1 is not allowed and may lead to processing errors. Set the START bit in the TDES Control Register (TDES_CR) to begin the encryption or decryption process. When the processing completes, the bit DATRDY in the TDES Interrupt Status Register (TDES_ISR) rises. If an interrupt has been enabled by setting the bit DATRDY in TDES_IER, the interrupt line of the TDES is activated. When the software reads one of the Output Data Registers (TDES_ODATARx), the DATRDY bit is automatically cleared. Table 62-3: Authorized Input Data Registers Operating Mode Input Data Registers to Write ECB All CBC All OFB All CFB 64-bit All CFB 32-bit TDES_IDATAR0 CFB 16-bit TDES_IDATAR0 CFB 8-bit TDES_IDATAR0  2017 Microchip Technology Inc. DS60001476B-page 2333 SAMA5D2 SERIES 62.4.2.2 Auto Mode The Auto Mode is similar to the Manual Mode, except that as soon as the correct number of Input Data registers is written, processing is automatically started without any action in TDES_CR. 62.4.2.3 DMA Mode The DMA Controller can be used in association with the TDES to perform an encryption/decryption of a buffer without any action by the software during processing. The SMOD field of TDES_MR must be set to 0x2 and the DMA must be configured with non-incremental addresses. The start address of any transfer descriptor must be set in TDES_IDATAR0. The DMA chunk size configuration depends on the TDES mode of operation and is listed in Table 62-4. When writing data to TDES with the first DMA channel, data will be fetched from a memory buffer (source data). It is recommended to configure the size of source data to “words” even for CFB modes. On the contrary, the destination data size depends on the mode of operation. When reading data from the TDES with the second DMA channel, the source data is the data read from TDES and data destination is the memory buffer. In this case, source data size depends on the TDES mode of operation and is listed in Table 62-4. Table 62-4: DMA Data Transfer Type for the Different Operating Modes Operating Mode Chunk Size Destination/Source Data Transfer Type ECB 1 Word CBC 1 Word OFB 1 Word CFB 64-bit 1 Word CFB 32-bit 1 Word CFB 16-bit 1 Half-word CFB 8-bit 1 Byte 62.4.3 Last Output Data Mode This mode is used to generate cryptographic checksums on data (MAC) using a CBC-MAC or a CFB encryption algorithm (refer to FIPS Publication 81 Appendix F). After each end of encryption/decryption, the output data is available either on the output data registers for Manual and Auto modes or at the address specified in the receive buffer pointer for DMA mode (See Table 62-5 “Last Output Data Mode Behavior versus Start Modes”). The Last Output Data bit (LOD) in TDES_MR can be used to retrieve only the last data of several encryption/decryption processes. This data is only available on the Output Data Registers (TDES_ODATARx). Therefore, there is no need to define a read buffer in DMA mode. 62.4.3.1 Manual and Auto Modes • TDES_MR.LOD = 0 The DATRDY flag is cleared when at least one of the Output Data Registers is read. See Figure 62-1. DS60001476B-page 2334  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 62-1: Manual and Auto Modes with LOD = 0 Write START bit in TDES_CR (Manual mode) or Write TDES_IDATARx register(s) (Auto mode) Read TDES_ODATARx DATRDY Encryption or Decryption Process If the user does not want to read the output data registers between each encryption/decryption, the DATRDY flag will not be cleared. If the DATRDY flag is not cleared, the user will not be informed of the end of the encryptions/decryptions that follow. • TDES_MR.LOD = 1 The DATRDY flag is cleared when at least one Input Data Register is written, before the start of a new transfer. See Figure 62-2. No further Output Data Register reads are necessary between consecutive encryptions/decryptions. Figure 62-2: Manual and Auto Modes with LOD = 1 Write START bit in TDES_CR (Manual mode) or Write TDES_IDATARx register(s) (Auto mode) Write TDES_IDATARx register(s) DATRDY Encryption or Decryption Process 62.4.3.2 DMA Mode • TDES_MR.LOD = 0 This mode may be used for all TDES operating modes except CBC-MAC where LOD = 1 mode is recommended. The end of the encryption/decryption is indicated by the end of DMA transfer associated to TDES_ODATARx (see Figure 62-3). Two DMA channels are required: one for writing message blocks to TDES_IDATARx and one to obtain the result from TDES_ODATARx. Figure 62-3: DMA Transfer with LOD = 0 Enable DMA Channels associated with TDES_IDATARx and TDES_ODATARx Multiple Encryption or Decryption Processes DMA buffer transfer complete flag/channel m DMA buffer transfer complete flag/channel n Write accesses into TDES_IDATARx Read accesses into TDES_ODATARx Message fully processed (cipher or decipher) Last block can be read • TDES_MR.LOD = 1 This mode is optimized to process the TDES CBC-MAC operating mode.  2017 Microchip Technology Inc. DS60001476B-page 2335 SAMA5D2 SERIES The user must first wait for the DMA buffer transfer complete flag, then for the flag DATRDY to rise to ensure that the encryption/decryption is completed (see Figure 62-4). In this case, no receive buffers are required. The output data is only available on TDES_ODATARx. Figure 62-4: DMA Transfer with LOD = 1 Enable DMA Channels associated with TDES_IDATARx and TDES_ODATARx Multiple Encryption or Decryption Processes Write accesses into TDES_IDATARx DMA status flag for end of buffer transfer DATRDY Message fully processed (cipher or decipher) MAC result can be read Message fully transferred Table 62-5 summarizes the different cases. Table 62-5: Last Output Data Mode Behavior versus Start Modes Manual and Auto Modes Sequence DMA Transfer LOD = 0 LOD = 1 LOD = 0 LOD = 1 DATRDY Flag Clearing Condition (1) At least one Output Data Register must be read At least one Input Data Register must be written Not used Managed by the DMA End of Encryption/ Decryption DATRDY DATRDY 2 DMA Buffer transfer complete flags (channel m and channel n) DMA buffer transfer complete flag, then TDES DATRDY flag Encrypted/Decrypted Data Result Location In the Output Data Registers In the Output Data Registers Not available In the Output Data Registers Note 1: Depending on the mode, there are other ways of clearing the DATRDY flag. See Section 62.5.6 “TDES Interrupt Status Register”. Warning: In DMA mode, reading to the Output Data registers before the last data transfer may lead to unpredictable results. 62.4.4 62.4.4.1 Security Features Unspecified Register Access Detection When an unspecified register access occurs, the URAD bit in TDES_ISR is set. Its source is then reported in the Unspecified Register Access Type field (URAT). Only the last unspecified register access is available through the URAT field. Several kinds of unspecified register accesses can occur: • • • • Input Data Register written during the data processing in DMA mode Output Data Register read during the data processing Mode Register written during the data processing Write-only register read access The URAD bit and the URAT field can only be reset by the SWRST bit in TDES_CR. DS60001476B-page 2336  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5 Triple Data Encryption Standard (TDES) User Interface Table 62-6: Offset Register Mapping Register Name Access Reset 0x00 Control Register TDES_CR Write-only – 0x04 Mode Register TDES_MR Read/Write 0x2 Reserved – – – 0x10 Interrupt Enable Register TDES_IER Write-only – 0x14 Interrupt Disable Register TDES_IDR Write-only – 0x18 Interrupt Mask Register TDES_IMR Read-only 0x0 0x1C Interrupt Status Register TDES_ISR Read-only 0x0000001E 0x20 Key 1 Word Register 0 TDES_KEY1WR0 Write-only – 0x24 Key 1 Word Register 1 TDES_KEY1WR1 Write-only – 0x28 Key 2 Word Register 0 TDES_KEY2WR0 Write-only – 0x2C Key 2 Word Register 1 TDES_KEY2WR1 Write-only – 0x30 Key 3 Word Register 0 TDES_KEY3WR0 Write-only – 0x34 Key 3 Word Register 1 TDES_KEY3WR1 Write-only – Reserved – – – 0x40 Input Data Register 0 TDES_IDATAR0 Write-only – 0x44 Input Data Register 1 TDES_IDATAR1 Write-only – Reserved – – – 0x50 Output Data Register 0 TDES_ODATAR0 Read-only 0x0 0x54 Output Data Register 1 TDES_ODATAR1 Read-only 0x0 Reserved – – – 0x60 Initialization Vector Register 0 TDES_IVR0 Write-only – 0x64 Initialization Vector Register 1 TDES_IVR1 Write-only – Reserved – XTEA Rounds Register TDES_XTEA_RNDR 0x74–0xE0 Reserved 0x74–0xE0 Reserved 0x08–0x0C 0x38–0x3C 0x48–0x4C 0x58–0x5C 0x68–0x6C 0x70  2017 Microchip Technology Inc. – – Read/Write 0x0 – – – – – – DS60001476B-page 2337 SAMA5D2 SERIES 62.5.1 TDES Control Register Name: TDES_CR Address: 0xFC044000 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – SWRST 7 6 5 4 3 2 1 0 – – – – – – – START • START: Start Processing 0: No effect 1: Starts Manual encryption/decryption process. SWRST: Software Reset 0: No effect 1: Resets the TDES. A software triggered hardware reset of the TDES interface is performed. DS60001476B-page 2338  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.2 TDES Mode Register Name: TDES_MR Address: 0xFC044004 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 – – – – – – 15 14 13 12 11 10 LOD – – – 2 OPMOD 7 6 5 4 3 – – – KEYMOD – 16 CFBS 9 8 SMOD 1 TDESMOD 0 CIPHER CIPHER: Processing Mode 0 (DECRYPT): Decrypts data. 1 (ENCRYPT): Encrypts data. TDESMOD: ALGORITHM Mode Value Name Description 0 SINGLE_DES Single DES processing using Key 1 Registers 1 TRIPLE_DES Triple DES processing using Key 1, Key 2 and Key 3 Registers 2 XTEA XTEA processing using Key 1 and Key 2 Registers Values which are not listed in the table must be considered as “reserved”. KEYMOD: Key Mode 0: Three-key algorithm is selected. 1: Two-key algorithm is selected. There is no need to write Key 3 Registers TDES_KEY3WRx. SMOD: Start Mode Value Name Description 0 MANUAL_START Manual Mode 1 AUTO_START Auto Mode 2 IDATAR0_START TDES_IDATAR0 accesses only Auto Mode Values which are not listed in the table must be considered as “reserved”. If a DMA transfer is used, 0x2 must be configured. See Section 62.4.3.2 “DMA Mode” for more details.  2017 Microchip Technology Inc. DS60001476B-page 2339 SAMA5D2 SERIES OPMOD: Operating Mode Value Name Description 0 ECB Electronic Code Book mode 1 CBC Cipher Block Chaining mode 2 OFB Output Feedback mode 3 CFB Cipher Feedback mode For CBC-MAC operating mode, set OPMOD to CBC and LOD to 1. LOD: Last Output Data Mode 0: No effect. After each end of encryption/decryption, the output data is available either on the output data registers (Manual and Auto modes) . In Manual and Auto modes, the DATRDY flag is cleared when at least one of the Output Data registers is read. 1: The DATRDY flag is cleared when at least one of the Input Data Registers is written. No more Output Data Register reads are necessary between consecutive encryptions/decryptions (see Section 62.4.3 “Last Output Data Mode”). Warning: In DMA mode, reading to the Output Data registers before the last data encryption/decryption process may lead to unpredictable result. CFBS: Cipher Feedback Data Size Value Name Description 0 SIZE_64BIT 64-bit 1 SIZE_32BIT 32-bit 2 SIZE_16BIT 16-bit 3 SIZE_8BIT 8-bit DS60001476B-page 2340  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.3 TDES Interrupt Enable Register Name: TDES_IER Address: 0xFC044010 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Enable 0: No effect. 1: Enables the corresponding interrupt. URAD: Unspecified Register Access Detection Interrupt Enable 0: No effect. 1: Enables the corresponding interrupt.  2017 Microchip Technology Inc. DS60001476B-page 2341 SAMA5D2 SERIES 62.5.4 TDES Interrupt Disable Register Name: TDES_IDR Address: 0xFC044014 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Disable 0: No effect. 1: Disables the corresponding interrupt. URAD: Unspecified Register Access Detection Interrupt Disable 0: No effect. 1: Disables the corresponding interrupt. DS60001476B-page 2342  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.5 TDES Interrupt Mask Register Name: TDES_IMR Address: 0xFC044018 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – URAD 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Mask 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. URAD: Unspecified Register Access Detection Interrupt Mask 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled.  2017 Microchip Technology Inc. DS60001476B-page 2343 SAMA5D2 SERIES 62.5.6 TDES Interrupt Status Register Name: TDES_ISR Address: 0xFC04401C Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – URAD URAT 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready (cleared by setting bit START or bit SWRST in TDES_CR or by reading TDES_ODATARx) 0: Output data is not valid. 1: Encryption or decryption process is completed. Note: If TDES_MR.LOD = 1: In Manual and Auto modes, the DATRDY flag can also be cleared by writing at least one TDES_IDATARx. URAD: Unspecified Register Access Detection Status (cleared by setting bit TDES_CR.SWRST) 0: No unspecified register access has been detected since the last write of bit TDES_CR.SWRST. 1: At least one unspecified register access has been detected since the last write of bit TDES_CR.SWRST. URAT: Unspecified Register Access (cleared by setting bit TDES_CR.SWRST) Value Name Description 0 IDR_WR_PROCESSING Input Data Register written during data processing when SMOD = 0x2 mode. 1 ODR_RD_PROCESSING Output Data Register read during data processing. 2 MR_WR_PROCESSING Mode Register written during data processing. 3 WOR_RD_ACCESS Write-only register read access. Only the last Unspecified Register Access Type is available through the URAT field. DS60001476B-page 2344  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.7 TDES Key 1 Word Register x Name: TDES_KEY1WRx Address: 0xFC044020 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 KEY1W 23 22 21 20 KEY1W 15 14 13 12 KEY1W 7 6 5 4 KEY1W KEY1W: Key 1 Word The two 32-bit Key 1 Word registers are used to set the 64-bit cryptographic key used for encryption/decryption. KEY1W0 refers to the first word of the key and KEY1W1 to the last one. These registers are write-only to prevent the key from being read by another application. In XTEA mode, the key is defined on 128 bits. These registers contain the 64 LSB bits of the encryption/decryption key.  2017 Microchip Technology Inc. DS60001476B-page 2345 SAMA5D2 SERIES 62.5.8 TDES Key 2 Word Register x Name: TDES_KEY2WRx Address: 0xFC044028 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 KEY2W 23 22 21 20 KEY2W 15 14 13 12 KEY2W 7 6 5 4 KEY2W KEY2W: Key 2 Word The two 32-bit Key 2 Word registers are used to set the 64-bit cryptographic key used for encryption/decryption. KEY2W0 refers to the first word of the key and KEY2W1 to the last one. These registers are write-only to prevent the key from being read by another application. Note: TDES_KEY2WRx registers are not used in DES mode. In XTEA mode, the key is defined on 128 bits. These registers contain the 64 MSB bits of the encryption/decryption key. DS60001476B-page 2346  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.9 TDES Key 3 Word Register x Name: TDES_KEY3WRx Address: 0xFC044030 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 KEY3W 23 22 21 20 KEY3W 15 14 13 12 KEY3W 7 6 5 4 KEY3W KEY3W: Key 3 Word The two 32-bit Key 3 Word registers are used to set the 64-bit cryptographic key used for encryption/decryption. KEY3W0 refers to the first word of the key and KEY3W1 to the last one. These registers are write-only to prevent the key from being read by another application. Note: TDES_KEY3WRx registers are not used in DES mode, TDES with two-key algorithm selected and XTEA mode.  2017 Microchip Technology Inc. DS60001476B-page 2347 SAMA5D2 SERIES 62.5.10 TDES Input Data Register x Name: TDES_IDATARx Address: 0xFC044040 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IDATA 23 22 21 20 IDATA 15 14 13 12 IDATA 7 6 5 4 IDATA IDATA: Input Data The two 32-bit Input Data registers are used to set the 64-bit data block used for encryption/decryption. IDATA0 refers to the first word of the data to be encrypted/decrypted, and IDATA1 to the last one. These registers are write-only to prevent the input data from being read by another application. DS60001476B-page 2348  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.11 TDES Output Data Register x Name: TDES_ODATARx Address: 0xFC044050 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ODATA 23 22 21 20 ODATA 15 14 13 12 ODATA 7 6 5 4 ODATA ODATA: Output Data The two 32-bit Output Data registers contain the 64-bit data block which has been encrypted/decrypted. ODATA1 refers to the first word, ODATA2 to the last one.  2017 Microchip Technology Inc. DS60001476B-page 2349 SAMA5D2 SERIES 62.5.12 TDES Initialization Vector Register x Name: TDES_IVRx Address: 0xFC044060 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 IV 23 22 21 20 IV 15 14 13 12 IV 7 6 5 4 IV IV: Initialization Vector The two 32-bit Initialization Vector registers are used to set the 64-bit initialization vector data block, which is used by some modes of operation as an additional initial input. IV1 refers to the first word of the Initialization Vector, IV2 to the last one. These registers are write-only to prevent the Initialization Vector from being read by another application. Note: These registers are not used for the ECB mode and must not be written. DS60001476B-page 2350  2017 Microchip Technology Inc. SAMA5D2 SERIES 62.5.13 TDES XTEA Rounds Register Name: TDES_XTEA_RNDR Address: 0xFC044070 Access: Read/Write 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – XTEA_RNDS XTEA_RNDS: Number of Rounds This 6-bit field is used to define the number of complete rounds (1 complete round = 2 Feistel rounds) processed in XTEA algorithm. The value of XTEA_RNDS has no effect if the TDESMOD field in TDES_MR is set to 0x0 or 0x1. Note: 0x00 corresponds to 1 complete round, 0x01 corresponds to 2 complete rounds, etc.  2017 Microchip Technology Inc. DS60001476B-page 2351 SAMA5D2 SERIES 63. True Random Number Generator (TRNG) 63.1 Description The True Random Number Generator (TRNG) passes the American NIST Special Publication 800-22 (A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications) and the Diehard Suite of Tests. The TRNG may be used as an entropy source for seeding an NIST approved DRNG (Deterministic RNG) as required by FIPS PUB 1402 and 140-3. 63.2 Embedded Characteristics • Passes NIST Special Publication 800-22 Test Suite • Passes Diehard Suite of Tests • May be Used as Entropy Source for seeding a NIST-approved DRNG (Deterministic RNG) as required by FIPS PUB 140-2 and 1403 • Provides a 32-bit Random Number Every 84 Clock Cycles 63.3 Block Diagram Figure 63-1: TRNG Block Diagram TRNG Interrupt Controller PMC Control Logic MCK User Interface Entropy Source APB 63.4 Product Dependencies 63.4.1 Power Management The TRNG interface may be clocked through the Power Management Controller (PMC), thus the programmer must first configure the PMC to enable the TRNG user interface clock. The user interface clock is independent from any clock that may be used in the entropy source logic circuitry. The source of entropy can be enabled before enabling the user interface clock. 63.4.2 Interrupt Sources The TRNG interface has an interrupt line connected to the Interrupt Controller. In order to handle interrupts, the Interrupt Controller must be programmed before configuring the TRNG. Table 63-1: Peripheral IDs Instance ID TRNG 47 DS60001476B-page 2352  2017 Microchip Technology Inc. SAMA5D2 SERIES 63.5 Functional Description As soon as the TRNG is enabled in the Control register (TRNG_CR), the generator provides one 32-bit random value every 84 clock cycles. The TRNG interrupt line can be enabled in the Interrupt Enable register (TRNG_IER), and disabled in the Interrupt Disable register (TRNG_IDR). This interrupt is set when a new random value is available and the interrupt is cleared when the Status register (TRNG_ISR) is read. The flag TRNG_ISR.DATRDY is set when the random data is ready to be read out on the 32-bit Output Data register (TRNG_ODATA). The normal operating mode checks that the TRNG_ISR.DATRDY flag equals ‘1’ before reading TRNG_ODATA when a 32-bit random value is required by the software application. Figure 63-2: TRNG Data Generation Sequence Clock TRNG_CR.ENABLE = 1 84 clock cycles 84 clock cycles 84 clock cycles TRNG Interrupt Line, TRNG_ISR.DATRDY Read TRNG_ISR Read TRNG_ODATA  2017 Microchip Technology Inc. Read TRNG_ISR Read TRNG_ODATA DS60001476B-page 2353 SAMA5D2 SERIES 63.6 True Random Number Generator (TRNG) User Interface Table 63-2: Register Mapping Offset 0x00 Register Name Access Reset Write-only – – – Control Register TRNG_CR Reserved – 0x10 Interrupt Enable Register TRNG_IER Write-only – 0x14 Interrupt Disable Register TRNG_IDR Write-only – 0x18 Interrupt Mask Register TRNG_IMR Read-only 0x0000_0000 0x1C Interrupt Status Register TRNG_ISR Read-only 0x0000_0000 Reserved – – – Output Data Register TRNG_ODATA Read-only 0x0000_0000 0x54–0xE0 Reserved – – – 0xE4–0xE8 Reserved – – – 0xEC–0xFC Reserved – – – 0x04–0x0C 0x20–0x4C 0x50 DS60001476B-page 2354  2017 Microchip Technology Inc. SAMA5D2 SERIES 63.6.1 TRNG Control Register Name: TRNG_CR Address: 0xFC01C000 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 WAKEY 23 22 21 20 WAKEY 15 14 13 12 WAKEY 7 6 5 4 3 2 1 0 – – – – – – – ENABLE ENABLE: Enables the TRNG to Provide Random Values 0: Disables the TRNG. 1: Enables the TRNG if 0x524E47 (“RNG” in ASCII) is written in KEY field at the same time. WAKEY: Register Write Access Key Value 0x524E47 Name Description PASSWD Writing any other value in this field aborts the write operation.  2017 Microchip Technology Inc. DS60001476B-page 2355 SAMA5D2 SERIES 63.6.2 TRNG Interrupt Enable Register Name: TRNG_IER Address: 0xFC01C010 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Enable 0: No effect. 1: Enables the corresponding interrupt. DS60001476B-page 2356  2017 Microchip Technology Inc. SAMA5D2 SERIES 63.6.3 TRNG Interrupt Disable Register Name: TRNG_IDR Address: 0xFC01C014 Access: Write-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Disable 0: No effect. 1: Disables the corresponding interrupt.  2017 Microchip Technology Inc. DS60001476B-page 2357 SAMA5D2 SERIES 63.6.4 TRNG Interrupt Mask Register Name: TRNG_IMR Address: 0xFC01C018 Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready Interrupt Mask 0: The corresponding interrupt is not enabled. 1: The corresponding interrupt is enabled. DS60001476B-page 2358  2017 Microchip Technology Inc. SAMA5D2 SERIES 63.6.5 TRNG Interrupt Status Register Name: TRNG_ISR Address: 0xFC01C01C Access: Read-only 31 30 29 28 27 26 25 24 – – – – – – – – 23 22 21 20 19 18 17 16 – – – – – – – – 15 14 13 12 11 10 9 8 – – – – – – 7 6 5 4 3 2 1 0 – – – – – – – DATRDY DATRDY: Data Ready (cleared on read) 0: Output data is not valid or TRNG is disabled. 1: New random value is completed since the last read of TRNG_ODATA.  2017 Microchip Technology Inc. DS60001476B-page 2359 SAMA5D2 SERIES 63.6.6 TRNG Output Data Register Name: TRNG_ODATA Address: 0xFC01C050 Access: Read-only 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 ODATA 23 22 21 20 ODATA 15 14 13 12 ODATA 7 6 5 4 ODATA ODATA: Output Data The 32-bit Output Data register contains the 32-bit random data. DS60001476B-page 2360  2017 Microchip Technology Inc. SAMA5D2 SERIES 64. Security Module (SECUMOD) 64.1 Description The Security Module (SECUMOD) features different levels of security depending on the device reference. This section describes the protections embedded in the SECUMOD available on all SAMA5D2 devices. This module embeds the secure memories (5 Kbytes of SRAM and a 256-bit register bank) dedicated to the storage of sensitive data. These memories are scrambled with a programmable 32-bit key. When a fault is detected, regardless of the source, a clear signal can be sent automatically to the secure memories and clear their contents. For information specific to dynamic tamper protection (PIOBU), refer to the document "SAMA5D2 External Tamper Protections"(document no. 44095). For information specific to temperature, voltage and frequency monitoring for SAMA5D23 and SAMA5D28, refer to the document “SAMA5D23 and SAMA5D28 Environmental Monitors” (document no. 44036). 64.2 Embedded Characteristics A PIO Controller managing up to eight pads (PIOBU) and offering: • • • • Standard I/O function powered in the backup domain Eight external switch state change detectors Memory erase and scrambling Backup SRAM access and Zeroisation process  2017 Microchip Technology Inc. DS60001476B-page 2361 SAMA5D2 SERIES 64.3 Block Diagram Figure 64-1: SECUMOD Block Diagram PIOBUs intrusion CPU access pads[7:0] pads[7:0] rnd PIO Controller FNTRST User Interface Static/Dynamic Det IRQs Protection Manager SWKUP BUREG256b sources VDDCORE erase_cmd VDDBU reset key BUSRAM1Kb Erase automaton CLK32KHz (SYSTEM) on MCK (SYSTEM) clk RCOSC 64K clock BUSRAM4Kb scrambling descrambling X32CK CPU access XTALOSC 32K clock scrambling descrambling Test or JTAG intrusions ICLK clk IRNG rnd32 intrusion pads[3:0] TEST TCK/SWCLK TMS/SWDIO JTAGSEL Figure 64-1 represents the logic inside the SECUMOD. Analog cells are external to the IP and highlighted in green. DS60001476B-page 2362  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.3.1 I/O Lines Description Table 64-1: I/O Lines Description Name Description Type CLK32KHZ 32 kHz system clock from crystal or RC oscillator (SLCK) Input ICLK 64 kHz RC Oscillator Input PIOBU[7:0] Parallel IO backup controller, 8 pads I/O IRQ[1:0] Interrupt signals going to secure AIC Output SWKUP Wakeup signal going to system controller WKUP1 pin Output FNTRST Force Cortex-A5 test port reset Output 64.4 Product Dependencies 64.4.1 Interrupt Sources The SECUMOD provides two interrupt lines, each connected to one of the internal sources of the Advanced Interrupt Controller. Using these interrupts requires the AIC to be programmed first. Note that it is not recommended to use the interrupt lines in Edge-sensitive mode. The first interrupt line (SECURAM ID) is dedicated to backup memories access right violations signaling, or end of erase (automatic or software erase) signaling. The second interrupt line (SECUMOD ID) is shared by all the protection mechanisms. See the User Interface description (Section 64.6 “Security Module (SECUMOD) User Interface”) for more information about interrupt acknowledgement. The SECURAM and the SECUMOD interrupt lines are connected to the Interrupt Controller. The Interrupt Controller must be programmed before configuring the SECURAM or the SECUMOD. Table 64-2: Peripheral IDs Instance ID SECUMOD 16 SECURAM 51  2017 Microchip Technology Inc. DS60001476B-page 2363 SAMA5D2 SERIES 64.5 64.5.1 Functional Description Memory Mapping The SECUMOD embeds 5 Kbytes of SRAM split in two parts: the lower 4 Kbytes are erased in case of intrusion (BUSRAM4KB) while the upper 1 Kbyte is never erased (BUSRAM1KB). A 256-bit register bank is available as an additional memory and is totally erased in case of intrusion (BUREG256b). All memories support 8-bit, 16-bit and 32-bit access sizes. For power optimization, the transfers between the processor and these memories are decreased by a factor of 4. The base address value of the SECURAM is 0xF8044000. Figure 64-2: SECUMOD Internal Memory Map BUREG256b SECURAM Base + 0x1400 BUSRAM1KB, not auto-erasable SECURAM Base + 0x1000 5.08 Kbytes BUSRAM4KB, auto-erasable SECURAM Base (0xF8044000) 64.5.2 Scrambling Keys The secure memories (BUSRAM4KB, BUSRAM1KB and BUREG256b) are scrambled. The scrambling is enabled after reset and a scrambling key is automatically generated. The scrambling key can be modified through the Scrambling Key register (SECUMOD_SCRKEY). Scrambling can be disabled using the Control register (SECUMOD_CR). 64.5.3 Internal Random Number Generator (IRNG) The RNG cannot be read through the User Interface (a TrueRNG external to the SECUMOD is available for this purpose). DS60001476B-page 2364  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.5.4 Protection Mechanisms 64.5.4.1 PIO Backup Controller The SECUMOD includes a PIO Controller powered by VDDBU which handles the eight PIOBU I/O pins. Each I/O line is controlled by the PIO Controller and each pin can be configured to be driven. This is done by writing in the corresponding SECUMOD PIO Backup register (SECUMOD_PIOBUx). When SECUMOD_PIOBUx.OUTPUT is at ‘0’, the corresponding I/O line is used as an input only. When this bit is at ‘1’, the corresponding I/O line is driven by the PIO Backup Controller. • Output Mode When SECUMOD_PIOBUx.OUTPUT is set, the level driven on an I/O line can be determined by setting or clearing the PIO_SOD bit (Set Output Data). The value of this bit represents the data driven on the corresponding I/O line. • Input Mode The level on an I/O line can be read through the PIO_PDS bit (Pin Data Status) in the corresponding SECUMOD_PIOBUx. This bit indicates the level of the I/O line regardless of its configuration, whether as an input or driven by the PIO Controller. • Static Intrusion Detectors and Programmable Internal Pullup/Pulldown Intrusion detectors can be placed around the system to detect any intrusion attempt. This requires the corresponding I/O lines to be configured as inputs (SECUMOD_PIOBUx.OUTPUT = 0). • Static Intrusion Detection The detectors can be configured to detect either the rising edge or the falling edge on switches via SECUMOD_PIOBUx.SWITCH. Example: A detector can consist of a normally-closed switch which sends a zero signal to the Protection Unit. When an intrusion attempt occurs, the switch state changes to an open position. The debounce filter waits until an intrusion has been detected for a programmable continuous period to send an alarm signal to the Protection Unit. This is to prevent erroneous intrusion detections. • Internal Pullup/Pulldown The user has the possibility to connect an internal pullup or pulldown (around 100 kΩ) by configuring SECUMOD_PIOBUx.PULLUP accordingly. Configuring this field with a pullup or pulldown value activates the corresponding pullup/pulldown permanently. Note: Internal pullups are connected at reset state. • Scheduled Pullup/Pulldown In order to reduce the power consumption on the VDDBU power supply, all activated pullups/pulldowns can be scheduled by following the steps below: 1. 2. 3. Activate the required pullup/pulldown. Measure the level on the PIOBUx pin. Deactivate the pullup/pulldown. Scheduling is enabled by setting SECUMOD_PIOBUx.SCHEDULE. Note: This feature is only effective if the PULLUP field indicates that a pullup or a pulldown is connected. • Debouncing Time The debouncing time is common to all I/Os. The principle is presented in Figure 64-3. A period (fICLK/2) is allocated to each I/O. During that period, if SECUMOD_PIOBUx.SCHEDULE is set and if a pullup/pulldown is needed (PULLUP field different from 0), the pullup/pulldown is activated, the level is measured and the pullup/pulldown is deactivated. Otherwise, only the level is measured. Measurement is performed at the end of the allocated period.  2017 Microchip Technology Inc. DS60001476B-page 2365 SAMA5D2 SERIES Figure 64-3: Schedule Principle ICKL/2 ICKL/32 ICKL/256 tICLK/256 tICLK/256 PIOBU0 t PIOBU1 t PIOBU2 tICLK/32 t PIOBU3 t PIOBU4 t PIOBU5 t PIOBU6 t PIOBU7 Table 64-3: t Timings vs. fICLK fICLK (kHz) Timing Min = 38 Typ = 64 Max = 90 Units tICLK/2 53 31 22 µs tICLK/32 842 500 356 µs tICLK/256 6.74 4.00 2.84 ms • PIOBUx Alarm Filtering in Static Mode It is possible to filter the PIOBUx alarm detection by programming SECUMOD_PIOBUx.PIOBU_AFV. The steps are as follows: 1. 2. A 9-bit counter is incremented each time the value present on the corresponding input is not the expected one. An alarm is sent to the Protection Unit if the counter value reaches the value programmed in PIOBU_AFV. The previous 9-bit counter is reset only if the value present on the input is correct and stable for a continuous programmable period defined by SECUMOD_PIOBUx.PIOBU_RFV (a second counter is used for that operation). See Figure 64-4. DS60001476B-page 2366  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 64-4: PIOBUx Alarm Filtering Principle Start Counter1 = 0 and Counter2 = 0 Yes Input X Value correct ? Counter1 < PIOBUx_AFV ? Counter1 ++ and Counter2 = 0 No No Yes Counter2 ++ ALARM Yes Counter2 < PIOBUx_RFV ? No Counter1 = 0 and Counter2 = 0 At reset state, the debouncers are not activated (PIOBU_AFV and PIOBU_RFV fields set to 0), which implies that no alarm can be generated. Once both the PIOBU_AFV and the PIOBU_RFV fields have been programmed, the corresponding protection is activated and a CLR signal is generated automatically when an intrusion is detected. It is possible to generate an interrupt (or a wakeup signal) instead of clearing the secure memories content. To do so, the user must disable the protection in the Normal Mode Protection register (SECUMOD_NMPR) and configure the Normal Interrupt Enable Protection register (SECUMOD_NIEPR). Note: If the Normal Mode Protection/Backup Mode Protection registers are not hidden, their configuration has priority on the debouncer activation in the PIOBUx configuration registers, which means that CLR signal generation is enabled/disabled in those two registers. Setting the PIOBU_AFV and PIOBU_RFV fields configure the debouncer sensitivity and does not generate any clear signal when an intrusion is detected. Table 64-4: Debouncing Time vs. fICLK fICLK (kHz) Note: Debouncing Time Min = 38 Typ = 64 Max = 90 Unit Min (PIOBU_AFV = 1) 6.74 4.00 2.84 ms Max (PIOBU_AFV = 9) 3.45 2.05 1.46 s At reset state, the PIOBU_AFV and PIOBU_RFV fields are set to 0.  2017 Microchip Technology Inc. DS60001476B-page 2367 SAMA5D2 SERIES 64.5.4.2 JTAG Prevention • Debug Interface Access Prevention The SECUMOD can be used to block access to the system through the ARM processor's Debug Access Port interface. This feature is implemented via SECUMOD_JTAGCR, which enables assertion of the nDBGRESET reset input of the debug interface. Writing a ‘1’ to SECUMOD_JTAGCR.FNTRST prevents any activity on the TAP (Test Access Port) controller. On standard devices, FNTRST resets to ‘0’ and thus does not prevent debug access. FNTRST also locks the boundary scan when set. • Physical Restrictions for JTAG Debug Mode Invasive and non-invasive debug modes are controlled by four input pins of the Debug Access Port: DBGEN, SPIDEN, NIDEN and SPNIDEN. In order to restrict the debug to nonsecure software parts only, the SEC_DEBUG_DIS fuse has to be configured in the customer fuse matrix. Programming this fuse prevents JTAG secure debug irreversibly, but does not lock non-secure debug. • Software Restrictions for JTAG Debug Mode Setting SECUMOD_JTAGCR.CA5_DEBUG_MODE sets the DBGEN, SPIDEN, NIDEN and SPNIDEN Cortex inputs to the appropriate level in order to allow different debug permission levels. See Section 64.6.7 “SECUMOD JTAG Protection Control Register” for more information. • Software Prevention for JTAG Debug It is possible to prevent JTAG Debug accesses by forcing the reset signal of Debug Access Port by software. While the reset signal is maintained low, the JTAG Debug interface cannot be used. To maintain the Debug Access Port in reset state, set SECUMOD_JTAGCR.FNTRST (in this case, Boundary JTAG is also disabled). The key used for the BUREG256b scrambler/descrambler is derived from the BUSRAM4KB key and thus benefits from the same protection. 64.5.5 Erasing Secure Memories 64.5.5.1 BUSRAM4KB Erase Sequence • Principle The BUSRAM4KB Erase sequence is controlled by an automaton which is activated by the CLR signal. Table 64-5 shows the time to perform a partial erase (one erased word out of eight on the entire BUSRAM4KB), and the time to perform a full erase. Table 64-5: Erase Time Evaluation vs. fICLK fICLK Frequency (kHz) Erase Min = 38 Typ = 64 Max = 90 Partial Erase 1.68 1.00 0.71 Full Erase (4 Kbytes) 13.47 8.00 5.69 Unit ms During the Erase sequence, the upper 1 Kbyte of memory (BUSRAM1KB) is still accessible by the system. The erase is a write of random values instead of erase to zero. 64.5.5.2 BUREG256b Erase Sequence In parallel to the BUSRAM4KB Erase, the BUREG256b register bank is erased. BUREG256b is always reset after a VDDBU powerup. These registers are seen as zero after reset or after an erase. • During and After BUSRAM4KB and BUREG256b Erase Sequence Some flags can be read to know the real-time erase state of the memories. On completion of the Erase sequence, the SECURAM ID interrupt line is asserted. DS60001476B-page 2368  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.5.6 Operating Modes The SECUMOD is supplied by the VDDBU power supply. It is not possible to program the SECUMOD if VDDBU is not present. The SECUMOD macrocell is able to operate in two different modes: • When all supplies are present and can be monitored, the SECUMOD can be switched to Normal mode. • Otherwise, the SECUMOD must be in Backup mode. Note: After a powerup reset, the SECUMOD is in Backup mode. The mode is selected by setting either SECUMOD_CR.NORMAL or SECUMOD_CR.BACKUP. Note: The user must set SECUMOD_CR.BACKUP to enter Backup mode prior to shutting off the VDDCORE power supplies. In both modes, the user can enable or disable a protection by writing in the corresponding Mode Protection register. See Section 64.5.7 “Activation or Deactivation of Protections” for more information. 64.5.6.1 Protection Unit The Protection Unit is used to centralize all alarms coming from the different monitors. When an alarm is detected, the Protection Unit sends a Clear signal to the automaton, which starts the secure memories Erase sequence if the memory is not empty. The Protection Unit can also send: • an IRQ interrupt signal (only in Normal mode) • an SWKUP wakeup signal (only in Backup mode). When an interrupt or a wakeup signal is generated, it is up to the user to detect the source of the alarm and to act accordingly, i.e., to clear the secure memories content or not. As soon as an alarm is detected, the corresponding bit is set in the Status register (SECUMOD_SR). The only way to clear this bit is to set it in the Status Clear register (SECUMOD_SCR). Note: Once a status bit is raised, it should not be cleared before the next slow clock period. If a clear does occur, the status bit rises again and the same alarm will be seen twice. To prevent this, it is recommended to wait at least one slow clock period after reading the Status register before clearing the status bits. If a Clear of the secure memories content has been performed by the automaton, an ERASE_DONE flag is set to indicate that the secure memories content is not valid anymore. While the secure memories are erased, write accesses have no effect and read accesses return a static and invalid value (except for BUSRAM1KB). 64.5.7 Activation or Deactivation of Protections It is possible to activate or deactivate each protection separately by writing in the Normal and Backup Mode Protection registers. These registers are hidden and the only way to make them appear is to write SECUMOD_CR.KEY with the correct value. This command field acts on a toggle basis: writing the correct value makes the registers appear and disappear. At reset state, all protections are activated except the sixteen corresponding to the intrusion detectors (need to program PIOBUx). 64.5.8 Powerup Reset After a powerup reset, the SECUMOD is in Backup mode, but in an unpredictable state. The Slow Clock oscillator takes about one second to startup. It is also possible that monitors send alarms to the Protection Unit. However, a Clear command can be performed because the secure memories content is empty. Care must be taken when writing in BUSRAM4KB or BUREG256b after reset. The user must make sure that no Erase sequence is running, otherwise the write access to BUSRAM4KB or BUREG256b is aborted. It is recommended to wait for the system to be established before accessing BUSRAM4KB or BUREG256b. This can last for at least one or two seconds. The verification is performed by reading the Status register. If there is no error for a continuous period (one second, for example), the user can access BUSRAM4KB or BUREG256b. If at least one error is detected, the user has to wait first for the ERASE_DONE flag to rise, and then wait again for at least one slow clock period after reading the Status register before writing content in the Status Clear register. At this stage, all status bits should be cleared. The user must then ensure that no error is raised in the Status register during the next second, for example.  2017 Microchip Technology Inc. DS60001476B-page 2369 SAMA5D2 SERIES 64.6 Security Module (SECUMOD) User Interface Table 64-6: Register Mapping Offset Register Name Access Reset 0x0000 Control Register SECUMOD_CR Write-only - 0x0004 System Status Register SECUMOD_SYSR Read/Write 0x0000 00D4 0x0008 Status Register SECUMOD_SR Read-only 0x0000 0000 0x000C Reserved – – – 0x0010 Status Clear Register SECUMOD_SCR Write-only – 0x0014 RAM Access Ready Register SECUMOD_RAMRDY Read undefined 0x0018 PIO Backup Register 0 SECUMOD_PIOBU0 Read/Write 0x1000 0x001C PIO Backup Register 1 SECUMOD_PIOBU1 Read/Write 0x1000 0x0020 PIO Backup Register 2 SECUMOD_PIOBU2 Read/Write 0x1000 0x0024 PIO Backup Register 3 SECUMOD_PIOBU3 Read/Write 0x1000 0x0028 PIO Backup Register 4 SECUMOD_PIOBU4 Read/Write 0x1000 0x002C PIO Backup Register 5 SECUMOD_PIOBU5 Read/Write 0x1000 0x0030 PIO Backup Register 6 SECUMOD_PIOBU6 Read/Write 0x1000 0x0034 PIO Backup Register 7 SECUMOD_PIOBU7 Read/Write 0x1000 0x0038 Reserved – – – 0x003C Reserved – – – 0x0040 Reserved – – – 0x0044 Reserved – – – 0x0048 Reserved – – – 0x004C Reserved – – – 0x0050 Reserved – – – 0x0054 Reserved – – – 0x0058 Reserved – – 0x7 0x005C Reserved – – – 0x0060 Reserved – – – 0x0064 Reserved – – 0x1FFF 0x0068 JTAG Protection Control Register SECUMOD_JTAGCR Read/Write 0x8(1) / 0x0(2) 0x006C Reserved – – – 0x0070 Scrambling Key Register SECUMOD_SCRKEY Read/Write undefined 0x0074 RAM Access Rights Register SECUMOD_RAMACC Read/Write 0x3FFFF 0x0078 RAM Access Rights Status Register SECUMOD_RAMACCSR Read/Write 0x0000 0000 0x007C Backup Mode Protection Register SECUMOD_BMPR Read/Write 0xFFFF 0CCF(3) 0x0080 Normal Mode Protection Register SECUMOD_NMPR Read/Write 0xFFFF FFFF(3) 0x0084 Normal Interrupt Enable Protection Register SECUMOD_NIEPR Write-only – DS60001476B-page 2370  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 64-6: Register Mapping (Continued) Offset Register Name Access Reset 0x0088 Normal Interrupt Disable Protection Register SECUMOD_NIDPR Write-only – 0x008C Normal Interrupt Mask Protection Register SECUMOD_NIMPR Read-only 0x0(4) 0x0090 Wakeup Protection Register SECUMOD_WKPR Read/Write 0x0 Note 1: When fuse DEFDBG is not programmed. 2: When fuse DEFDBG is programmed. 3: PIO backup protections are off after backup reset whatever the reset value of this register. See SECUMOD_PIOBUx register descriptions to enable these protections. 4: After Peripheral Reset (other reset values are defined after Backup Reset).  2017 Microchip Technology Inc. DS60001476B-page 2371 SAMA5D2 SERIES 64.6.1 SECUMOD Control Register Name: SECUMOD_CR Address: 0xFC040000 Access: Write-only 31 30 29 28 27 26 25 24 19 18 17 16 10 9 8 – 1 NORMAL 0 BACKUP KEY 23 22 21 20 KEY 15 – 14 – 13 – 12 – 11 7 6 – 5 – 4 – 3 – SCRAMB 2 SWPROT BACKUP: Backup Mode 0: No effect. 1: Switches to Backup mode. NORMAL: Normal Mode 0: No effect. 1: Switches to Normal mode. SWPROT: Software Protection 0: No effect. 1: Starts the BUSRAM4KB and BUREG256b Clear content. SCRAMB: Memory Scrambling Enable 10: Memories are not scrambled. 01: Memories are scrambled (default). 00,11: No effect. KEY: Password This command field acts on a toggle basis: writing the value 0x89CA alternatively makes the Normal or Backup Protection Registers appear and disappear. Writing any other value in this field has no effect. DS60001476B-page 2372  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.2 SECUMOD System Status Register Name: SECUMOD_SYSR Address: 0xFC040004 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 SCRAMB 6 AUTOBKP 5 – 4 – 3 SWKUP 2 BACKUP 1 ERASE_ON 0 ERASE_DONE ERASE_DONE: Erasable Memories State (RW) 0: Secure memories content has not been erased since the last clear. 1: Secure memories content has been erased since the last clear. The user must write 1 into this bit to clear this flag. Note that not clearing this flag does not prevent the next erase processes. This flag also activates the SECURAM interrupt line as long as it is not cleared. ERASE_ON: Erase Process Ongoing (RO) 0: Erase automaton is not running. 1: Erase automaton is currently running, memories are not accessible. When ERASE_ON returns to 0, ERASE_DONE is set after half a period of ICLK. ERASE_ON ERASE_DONE Status 0 0 No Erase ongoing or since the last Erase. 1 0 An Erase process is running. 0 1 An Erase occurred and is finished. An Erase process is running. 1 1 The ERASE_DONE flag refers to a previous Erase process, but was not cleared. Action Nothing. Wait until the ERASE_ON flag is reset. ERASE_DONE will rise, see line below. Clear the ERASE_DONE flag. Wait until the ERASE_ON flag is reset, then clear the ERASE_DONE flag. BACKUP: Backup Mode (RO) 0: Normal mode active. 1: Backup mode active. SWKUP: SWKUP State (RO) 0: No SWKUP signal sent since the last clear. 1: SWKUP signal has been sent since the last clear.  2017 Microchip Technology Inc. DS60001476B-page 2373 SAMA5D2 SERIES AUTOBKP: Automatic Backup Mode Enabled (RO) 0: Disabled. 1: Enabled. SCRAMB: Scrambling Enabled (RO) 0: Disabled. 1: Enabled. DS60001476B-page 2374  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.3 SECUMOD Status Register Name: SECUMOD_SR Address: 0xFC040008 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – The following configuration values are valid for all listed bit names of this register: 0: No alarm generated since the last clear. 1: An alarm has been generated by the corresponding monitor since the last clear. DETx: PIOBU Intrusion Detector  2017 Microchip Technology Inc. DS60001476B-page 2375 SAMA5D2 SERIES 64.6.4 SECUMOD Status Clear Register Name: SECUMOD_SCR Address: 0xFC040010 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Clears the corresponding alarm flag bit. If the corresponding alarm was programmed to generate a SWKUP signal, clearing the alarm also clears the SWKUP status bit in the SECUMOD Status register. DETx: PIOBU Intrusion Detector DS60001476B-page 2376  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.5 SECUMOD RAM Access Ready Register Name: SECUMOD_RAMRDY Address: 0xFC040014 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 READY READY: Ready for system access flag When exiting Idle, System Reset or Backup mode, this flag must be read high before accessing the secure memories. The flag remains low until any ongoing process stops. Refer to the section “Real-time Clock (RTC) User Interface” for more information.  2017 Microchip Technology Inc. DS60001476B-page 2377 SAMA5D2 SERIES 64.6.6 SECUMOD PIO Backup Register x Name: SECUMOD_PIOBUx Address: 0xFC040018 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 SWITCH 14 SCHEDULE 13 12 11 – 10 PIO_PDS 9 PIO_SOD 8 OUTPUT 7 6 5 4 3 2 1 0 PULLUP PIOBU_RFV Note: PIOBU_AFV The FILTER3_5 and DYNSTAT fields only exist for even PIOBUs. PIOBU_AFV: PIOBU Alarm Filter Value This field is used to define the filter value prior to generating an alarm. PIOBU_AFV Maximum Counter Value 0 0 (No static protection) 1 2 2 4 3 8 4 16 5 32 6 64 7 128 8 256 9 512 This field must be set to 0 when Dynamic Intrusion is selected. PIOBU_RFV: PIOBUx Reset Filter Value This field is used to define the number of consecutive valid states to be reached before resetting the AFV counter. PIOBU_RFV Maximum Counter Value 0 0 (No static protection) 1 2 2 4 3 8 4 16 5 32 DS60001476B-page 2378  2017 Microchip Technology Inc. SAMA5D2 SERIES PIOBU_RFV Maximum Counter Value 6 64 7 128 8 256 9 512 This field must be set to 0 when Dynamic Intrusion is selected. OUTPUT: Configure I/O Line in Input/Output 0: The I/O line is a pure input. 1: The I/O line is enabled in output. PIO_SOD: Set/Clear the I/O Line when configured in Output Mode (OUTPUT =1) 0: Clears the data to be driven on the I/O line. 1: Sets the data to be driven on the I/O line. PIO_PDS: Level on the Pin in Input Mode (OUTPUT = 0) (Read-only) 0: The I/O line is at level 0. 1: The I/O line is at level 1. PULLUP: Programmable Pull-up State This field is used to control the internal pull-up or pull-down. PULLUP0 Status 0 0 No pull-up / pull-down connected 0 1 Pull-up connected 1 0 Pull-down connected 1 1 Reserved SCHEDULE: Pull-up/Down Scheduled 0: Pullup/pulldown is not scheduled. 1: Pullup/pulldown is scheduled. SWITCH: Switch State for Intrusion Detection 0: Input default state is low level. 1: Input default state is high level.  2017 Microchip Technology Inc. DS60001476B-page 2379 SAMA5D2 SERIES 64.6.7 SECUMOD JTAG Protection Control Register Name: SECUMOD_JTAGCR Address: 0xFC040068 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 WZO 3 2 CA5_DEBUG_MODE 1 0 FNTRST FNTRST: Force NTRST 0: The ARM processor’s TAP controller access and Boundary JTAG are not blocked by the SECUMOD. 1: nDBGRESET of the ARM processor’s TAP controller and Boundary JTAG reset are held low, preventing the processor to switch to debug state and Boundary JTAG to work. CA5_DEBUG_MODE: Cortex-A5 Invasive/Non-Invasive Secure/Non-Secure Debug Permissions This field is used to set different debug permission levels. For instance, it can be used to prevent debug on secure parts of the code. The table below shows the effect of the field value on the Cortex-A5 pins (SPIDEN, DBGEN, SPNIDEN and NIDEN). CA5_DEBUG_MODE Value Cortex-A5 Debug Permissions SPIDEN DBGEN SPNIDEN NIDEN b000 No Debug 0 0 0 0 b001 Non-Invasive, Non-Secure 0 0 0 1 b010 Full Non-Secure (Invasive and Non-Invasive) 0 1 0 0 b011 Full Non-Secure + Non-Invasive Secure 0 1 1 1 b100 Full Debug allowed 1 1 1 1 WZO: Write ZERO Must be written with 0. DS60001476B-page 2380  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.8 SECUMOD Scrambling Key Register Name: SECUMOD_SCRKEY Address: 0xFC040070 Access: 31 Read/Write 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 2 1 0 SCRKEY 23 22 21 20 SCRKEY 15 14 13 12 SCRKEY 7 6 5 4 SCRKEY SCRKEY: Scrambling Key Value This 32-bit key is used by the secure memories scrambler/descrambler logics. When changed, the readable content of the memories is made unintelligible instantaneously.  2017 Microchip Technology Inc. DS60001476B-page 2381 SAMA5D2 SERIES 64.6.9 SECUMOD RAM Access Rights Register Name: SECUMOD_RAMACC Address: 0xFC040074 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 6 5 4 3 7 RW3 RW5 RW2 RW4 2 RW1 1 0 RW0 The following configuration values are valid for all listed bit names of this register: 00: No access allowed 01: Only write access allowed 10: Only read access allowed 11: Read and write accesses allowed Accessing a forbidden area causes an interrupt (SECURAM ID). RW0: Access right for RAM region [0; 1 Kbyte] RW1: Access right for RAM region [1 Kbyte; 2 Kbytes] RW2: Access right for RAM region [2 Kbytes; 3 Kbytes] RW3: Access right for RAM region [3 Kbytes; 4 Kbytes] RW4: Access right for RAM region [4 Kbytes; 5 Kbytes] RW5: Access right for RAM region [5 Kbytes; 6 Kbytes] (register bank BUREG256b) DS60001476B-page 2382  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.10 SECUMOD RAM Access Rights Status Register Name: SECUMOD_RAMACCSR Address: 0xFC040078 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 10 9 8 6 5 4 3 7 RW3 RW5 RW2 RW4 2 RW1 1 0 RW0 The following configuration values are valid for all listed bit names of this register: 00: No access violation occurred 01: Write access violation occurred 10: Read access violation occurred 11: Read and write access violation occurred Writing any value to this register resets the register and the associated interrupt line (SECURAM ID). RW0: Access right status for RAM region [0; 1 Kbyte] RW1: Access right status for RAM region [1 Kbytes; 2 Kbytes] RW2: Access right status for RAM region [2 Kbytes; 3 Kbytes] RW3: Access right status for RAM region [3 Kbytes; 4 Kbytes] RW4: Access right status for RAM region [4 Kbytes; 5 Kbytes] RW5: Access right status for RAM region [5 Kbytes; 6 Kbytes] (register bank BUREG256b)  2017 Microchip Technology Inc. DS60001476B-page 2383 SAMA5D2 SERIES 64.6.11 SECUMOD Backup Mode Protection Register Name: SECUMOD_BMPR Address: 0xFC04007C Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection 0: Protection disabled. 1: Protection enabled. Reminder: Enabling PIOBU protection requires additional programming of PIOBUx registers. DS60001476B-page 2384  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.12 SECUMOD Normal Mode Protection Register Name: SECUMOD_NMPR Address: 0xFC040080 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection 0: Protection disabled. 1: Protection enabled. Reminder: Enabling PIOBU protection requires additional programming of PIOBUx registers.  2017 Microchip Technology Inc. DS60001476B-page 2385 SAMA5D2 SERIES 64.6.13 SECUMOD Normal Interrupt Enable Protection Register Name: SECUMOD_NIEPR Address: 0xFC040084 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection Interrupt Enable 0: No effect. 1: Enables the corresponding interrupt. DS60001476B-page 2386  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.14 SECUMOD Normal Interrupt Disable Protection Register Name: SECUMOD_NIDPR Address: 0xFC040088 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection Interrupt Disable 0: No effect. 1: Disables the corresponding interrupt.  2017 Microchip Technology Inc. DS60001476B-page 2387 SAMA5D2 SERIES 64.6.15 SECUMOD Normal Interrupt Mask Protection Register Name: SECUMOD_NIMPR Address: 0xFC04008C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection Interrupt Mask 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. DS60001476B-page 2388  2017 Microchip Technology Inc. SAMA5D2 SERIES 64.6.16 SECUMOD Wakeup Register Name: SECUMOD_WKPR Address: 0xFC040090 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 DET7 22 DET6 21 DET5 20 DET4 19 DET3 18 DET2 17 DET1 16 DET0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – DETx: PIOBU Intrusion Detector Protection 0: No wakeup signal is generated if the corresponding alarm is detected. 1: A wakeup signal (SWKUP) is generated if the corresponding alarm is detected.  2017 Microchip Technology Inc. DS60001476B-page 2389 SAMA5D2 SERIES 65. Analog-to-Digital Converter (ADC) 65.1 Description The ADC is based on a 12-bit Analog-to-Digital Converter (ADC) managed by an ADC Controller providing enhanced resolution up to 14 bits. See Figure 65-1 “Analog-to-Digital Converter Block Diagram”. It also integrates a 12-to-1 analog multiplexer, making possible the analog-to-digital conversions of 12 analog lines. The conversions extend from 0V to the voltage carried on pin ADVREF. Conversion results are reported in a common register for all channels, as well as in a channel-dedicated register. The 13-bit and 14-bit resolution modes are obtained by averaging multiple samples to decrease quantization noise. For the 13-bit mode, 4 samples are used, which gives a real sample rate of 1/4 of the actual sample frequency. For the 14-bit mode, 16 samples are used, giving a real sample rate of 1/16 of the actual sample frequency. This arrangement allows conversion speed to be traded off against for better accuracy. The software trigger, external trigger on rising edge of the ADTRG pin or internal triggers from Timer Counter output(s) are configurable. The comparison circuitry allows automatic detection of values below a threshold, higher than a threshold, in a given range or outside the range, thresholds and ranges being fully configurable. The ADC Controller internal fault output is directly connected to the PWM fault input. This input can be asserted by means of comparison circuitry to immediately put the PWM output in a safe state (pure combinational path). The ADC also integrates a Sleep mode and a conversion sequencer and connects with a DMA channel. These features reduce both power consumption and processor intervention. This ADC has a selectable single-ended or fully differential input. This ADC Controller includes a Resistive Touchscreen Controller. It supports 4-wire and 5-wire technologies. DS60001476B-page 2390  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.2 • • • • • • • • • • • • • • • • • • Embedded Characteristics 12-bit Resolution with Enhanced Mode up to 14 bits 1 Msps Conversion Rate Digital Averaging Function providing Enhanced Resolution Mode up to 14 bits Wide Range of Power Supply Operation Selectable Single-Ended or Differential Input Voltage Digital correction of offset and gain errors Resistive 4-wire and 5-wire Touchscreen Controller - Position and Pressure Measurement for 4-wire Screens - Position Measurement for 5-wire Screens - Average of Up to 8 Measures for Noise Filtering Programmable Pen Detection Sensitivity Integrated Multiplexer Offering Up to 12 Independent Analog Inputs Individual Enable and Disable of Each Channel Hardware or Software Trigger from: - External Trigger Pin - Timer Counter Outputs (Corresponding TIOA Trigger) - ADC Internal Trigger Counter - Trigger on Pen Contact Detection - PWM Event Line Drive of PWM Fault Input DMA Support Two Sleep Modes (Automatic Wakeup on Trigger) - Lowest Power Consumption (Voltage Reference OFF Between Conversions) - Fast Wakeup Time Response on Trigger Event (Voltage Reference ON Between Conversions) Channel Sequence Customizing Automatic Window Comparison of Converted Values Asynchronous Partial Wakeup (SleepWalking) on external trigger Register Write Protection  2017 Microchip Technology Inc. DS60001476B-page 2391 SAMA5D2 SERIES 65.3 Block Diagram Figure 65-1: Analog-to-Digital Converter Block Diagram Timer Counter Channels PWM RTC RTCOUT1 RTCOUT0 last channel trigger ADC Controller all channels trigger Trigger Selection ADTRG ADC Interrupt ADCCLK Internal Trigger Counter Interrupt Controller Control Logic SOC VDDANA ADVREF System Bus Touchscreen Analog Inputs AD0/XP/UL 0 AD1/XM/UR 1 Touchscreen Switches AD2/YP/LL AD3/YM/Sense User Interface Cyclic Pipeline DMA 12-bit Analog-to-Digital Converter 2 Peripheral Bridge 3 AD4/LR 4 PIO Bus Clock VIN+ VIN- S/H APB AD- Other Analog Inputs ADPeripheral Clock CHx ADADC cell GNDANA 65.4 Signal Description Table 65-1: ADC Pin Description Pin Name Description VDDANA Analog power supply ADVREF Reference voltage AD0–AD11 Analog input channels ADTRG External trigger 65.5 65.5.1 PMC Product Dependencies Power Management The ADC Controller is not continuously clocked. The programmer must first enable the ADC Controller peripheral clock in the Power Management Controller (PMC) before using the ADC Controller. However, if the application does not require ADC operations, the ADC Controller clock can be stopped when not needed and restarted when necessary. Configuring the ADC Controller does not require the ADC Controller clock to be enabled. DS60001476B-page 2392  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.5.2 Interrupt Sources The ADC interrupt line is connected on one of the internal sources of the Interrupt Controller. Using the ADC interrupt requires the interrupt controller to be programmed first. Table 65-2: Peripheral IDs Instance ID ADC 40 65.5.3 I/O Lines The digital input ADTRG is multiplexed with digital functions on the I/O line and the selection of ADTRG is made using the PIO controller. The analog inputs ADC_ADx are multiplexed with digital functions on the I/O lines. ADC_ADx inputs are selected as inputs of the ADCC when writing a one in the corresponding CHx bit of ADC_CHER and the digital functions are not selected. Table 65-3: I/O Lines Instance Signal I/O Line Peripheral ADC ADTRG PD31 A ADC AD0 PD19 X1 ADC AD1 PD20 X1 ADC AD2 PD21 X1 ADC AD3 PD22 X1 ADC AD4 PD23 X1 ADC AD5 PD24 X1 ADC AD6 PD25 X1 ADC AD7 PD26 X1 ADC AD8 PD27 X1 ADC AD9 PD28 X1 ADC AD10 PD29 X1 ADC AD11 PD30 X1 65.5.4 Hardware Triggers The ADC can use internal signals to start conversions. See the ADC_MR.TRGSEL field description in Section 65.7.2 “ADC Mode Register” for exact wiring of internal triggers. 65.5.5 Fault Output The ADC Controller has the FAULT output connected to the FAULT input of PWM. See Section 65.6.18 “Fault Event” and section “Pulse Width Modulation Controller (PWM)”.  2017 Microchip Technology Inc. DS60001476B-page 2393 SAMA5D2 SERIES 65.6 65.6.1 Functional Description Analog-to-Digital Conversion Once the programmed startup time (ADC_MR.STARTUP) has elapsed, ADC conversions are sequenced by three operating times: • Tracking time—the time for the ADC to charge its input sampling capacitor to the input voltage. When several channels are converted consecutively, the inherent tracking time is 6 ADC clock cycles. However, the tracking time can be increased using the TRACKTIM field in the Mode Register (ADC_MR). • ADC inherent conversion time—the time for the ADC to convert the sampled analog voltage. This time is constant and is defined from start of conversion to end of conversion. • Channel conversion period—the effective time between the end of the current channel conversion and the end of the next channel conversion. Figure 65-2: Sequence of Consecutive ADC Conversions with TRACKTIM = 0 ADCCLK Trigger event (Hard or Soft) Analog cell IOs ADC_ON ADC_Start ADC_eoc ADC_SEL CH0 CH1 CH2 CH0 LCDR CH1 DRDY CH0 conversion period Startup Time (and start CH0 tracking) CH0 tracking A to D for CH0 CH1 conversion period 5 x ADCCLK A to D for CH1 CH1 Tracking = 6 x ADCCLK DS60001476B-page 2394  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 65-3: Sequence of Consecutive ADC Conversions with TRACKTIM = 15 ADCCLK Trigger event (Hard or Soft) ADC_ON Analog cell IOs TRACKTIM=15 Effect TRACKTIM=15 Effect ADC_Start ADC_eoc CH0 ADC_SEL CH1 CH2 CH0 LCDR CH1 DRDY CH0 conversion period Startup Time (and start CH0 tracking) CH0 tracking A to D for CH0 CH1 conversion period 5 x ADCCLK CH1 Tracking = 7 x ADCCLK 65.6.2 A to D for CH1 CH2 Tracking = 7 xADCCLK ADC Clock The ADC uses the ADC clock (ADCCLK) to perform conversions. The ADC clock frequency is selected in the PRESCAL field of ADC_MR. To generate the ADC clock, the prescaler has two clock sources: the peripheral clock and the GCLK clock. This clock source is selected using the SRCCLK bit in the Extended Mode Register (ADC_EMR). If GCLK is selected as a source clock, the ADC clock frequency is independent of the processor/bus clock. At reset, the peripheral clock is selected. If the SRCCLK bit in ADC_EMR is cleared, the prescaler clock (presc_clk) is driven by peripheral_clock. If the SRCCLK bit in ADC_EMR is set, the prescaler clock is driven by GCLK. The ADC clock frequency is between fpresc_clk/2, if PRESCAL is 0, and fpresc_clk/512, if PRESCAL is set to 255 (0xFF). PRESCAL must be programmed to provide the ADC clock frequency parameter given in section “Electrical Characteristics”. 65.6.3 ADC Reference Voltage The voltage reference input of the ADC is the ADVREF pin. Refer to the “Electrical Characteristics” section for further details. 65.6.4 Conversion Resolution The ADC has a native resolution of 12 bits. The ADC controller provides enhanced resolution up to 14 bits by means of digital averaging. If ADTRG is asynchronous to the ADC peripheral clock, the internal resynchronization introduces a jitter of 1 peripheral clock. This jitter may reduce the resolution of the converted signal. The same applies when using the independent clock (ADC_MR.SRCCLK = 1), if the provided clock is asynchronous to ADC peripheral clock. 65.6.5 Conversion Results When a conversion is completed, the resulting digital value is stored in the Channel Data register (ADC_CDRx) of the current channel and in the ADC Last Converted Data register (ADC_LCDR). By setting the TAG option in the Extended Mode Register (ADC_EMR), ADC_LCDR presents the channel number associated with the last converted data in the CHNB field. When a conversion is completed, the channel EOC bit and the DRDY bit in the Interrupt Status register (ADC_ISR) are set. In the case of a connected DMA channel, DRDY rising triggers a data request. In any case, either EOC and DRDY can trigger an interrupt.  2017 Microchip Technology Inc. DS60001476B-page 2395 SAMA5D2 SERIES Reading one of the ADC_CDRx clears the corresponding EOC bit. Reading ADC_LCDR clears the DRDY bit. Figure 65-4: EOCx and DRDY Flag Behavior Write the ADC_CR with START = 1 Read the ADC_CDRx Write the ADC_CR with START = 1 Read the ADC_LCDR CHx (ADC_CHSR) EOCx (ADC_ISR) DRDY (ADC_ISR) If ADC_CDR is not read before further incoming data is converted, the corresponding OVREx flag is set in the Overrun Status register (ADC_OVER). If new data is converted when DRDY is high, the GOVRE bit is set in ADC_ISR. The OVREx flag is automatically cleared when ADC_OVER is read, and the GOVRE flag is automatically cleared when ADC_ISR is read. DS60001476B-page 2396  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 65-5: EOCx, OVREx and GOVREx Flag Behavior Trigger event CH0 (ADC_CHSR) CH1 (ADC_CHSR) ADC_LCDR Undefined Data ADC_CDR0 Undefined Data ADC_CDR1 EOC0 (ADC_ISR) Data B Data A Data A Data C Undefined Data Data B Conversion A EOC1 (ADC_ISR) Data C Read ADC_CDR0 Conversion C Conversion B GOVRE (ADC_ISR) Read ADC_CDR1 Read ADC_ISR DRDY (ADC_ISR) Read ADC_OVER OVRE0 (ADC_OVER) OVRE1 (ADC_OVER) 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 corresponding EOCx and GOVRE flags in ADC_ISR and OVREx flags in ADC_OVER are unpredictable. 65.6.6 Conversion Results Format The conversion results can be signed (2’s complement) or unsigned depending on the value of the SIGNMODE field (“SIGNMODE: Sign Mode” in ADC_EMR). If conversion results are signed and resolution is less than 16 bits, the sign is extended up to the bit 15 (e.g., 0xF43 for 12-bit resolution is read as 0xFF43, and 0x467 is read as 0x0467). 65.6.7 Conversion Triggers Conversions of the active analog channels are started with a software or hardware trigger. The software trigger is provided by writing the Control register (ADC_CR) with the START bit at 1. The list of external/internal events is provided in Section 65.7.2 “ADC Mode Register”. The hardware trigger is selected using the TRGSEL field in ADC_MR. The selected hardware trigger is enabled if TRGMOD = 1, 2 or 3 in the ADC Trigger Register (ADC_ TRGR). The ADC also provides a dual trigger mode (ADC_LCTMR.DUALTRIG = 1) in which the higher index channel can be sampled at a rhythm different from the other channels. The trigger of the last channel is generated by the RTC. See Section 65.6.12 “Last Channel Specific Measurement Trigger”. The TRGMOD field in the ADC Trigger register (ADC_TRGR) selects the hardware trigger from the following: • any edge, either rising or falling or both, detected on the external trigger pin ADTRG  2017 Microchip Technology Inc. DS60001476B-page 2397 SAMA5D2 SERIES • the Pen Detect, depending on how the PENDET bit is set in the ADC Touchscreen Mode register (ADC_TSMR) • a continuous trigger, meaning the ADC Controller restarts the next sequence as soon as it finishes the current one • a periodic trigger, which is defined by programming the TRGPER field in ADC_TRGR The minimum time between two consecutive trigger events must be strictly greater than the duration time of the longest conversion sequence according to configuration of registers ADC_MR, ADC_CHSR, ADC_SEQRx, and ADC_TSMR. If a hardware trigger is selected, the start of a conversion is triggered after a delay starting at each rising edge of the selected signal. Due to asynchronous handling, the delay may vary in a range of two peripheral clock periods to one ADC clock period. This delay introduces sampling jitter in the A/D conversion process and may therefore degrade the conversion performance (e.g., SNR, THD). Figure 65-6: Hardware Trigger Delay trigger start delay 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 (ADC_CHER) and Channel Disable (ADC_CHDR) registers enable the analog channels to be enabled or disabled independently. If the ADC is used with a DMA, only the transfers of converted data from enabled channels are performed and the resulting data buffers should be interpreted accordingly. 65.6.8 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 SLEEP bit in ADC_MR. Sleep mode is managed by a conversion sequencer, which automatically processes the conversions of all channels at lowest power consumption. This mode can be used when the minimum period of time between two successive trigger events is greater than the startup period of the ADC. Refer to section “Electrical Characteristics”. When a start conversion request occurs, the ADC is automatically activated. As the analog cell requires a startup 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. Events triggered during the sequence are ignored. The conversion sequencer allows automatic processing with minimum processor intervention and optimized power consumption. Conversion sequences can be performed periodically using the internal timer (ADC_TRGR) or the PWM event line. The periodic acquisition of several samples can be processed automatically without any intervention of the processor via the DMA. The sequence can be customized by programming the Sequence Channel Registers ADC_SEQR1 and ADC_SEQR2 and setting the USEQ bit of the Mode Register (ADC_MR). The user can choose a specific order of channels and can program up to 12 conversions by sequence. The user is free to create a personal sequence by writing channel numbers in ADC_SEQR1 and ADC_SEQR2. Not only can channel numbers be written in any sequence, channel numbers can be repeated several times. When the bit USEQ in ADC_MR is set, the fields USCHx in ADC_SEQR1 and ADC_SEQR2 are used to define the sequence. Only enabled USCHx fields will be part of the sequence. Each USCHx field has a corresponding enable, CHx-1, in ADC_CHER. If all ADC channels (i.e., 12) are used on an application board, there is no restriction of usage of the user sequence. However, if some ADC channels are not enabled for conversion but rather used as pure digital inputs, the respective indexes of these channels cannot be used in the user sequence fields (see ADC_SEQRx). For example, if channel 4 is disabled (ADC_CSR[4] = 0), ADC_SEQRx fields USCH1 up to USCH12 must not contain the value 4. Thus the length of the user sequence may be limited by this behavior. As an example, if only four channels over 12 (CH0 up to CH3) are selected for ADC conversions, the user sequence length cannot exceed four channels. Each trigger event may launch up to four successive conversions of any combination of channels 0 up to 3 but no more (i.e., in this case the sequence CH0, CH0, CH1, CH1, CH1 is impossible). A sequence that repeats the same channel several times requires more enabled channels than channels actually used for conversion. For example, the sequence CH0, CH0, CH1, CH1 requires four enabled channels (four free channels on application boards) whereas only CH0, CH1 are really converted. DS60001476B-page 2398  2017 Microchip Technology Inc. SAMA5D2 SERIES Note: 65.6.9 The reference voltage pins always remain connected in Normal mode as in Sleep mode. Comparison Window The ADC Controller features automatic comparison functions. It compares converted values to a low threshold, a high threshold or both, depending on the value of the CMPMODE field in ADC_EMR. The comparison can be done on all channels or only on the channel specified in the CMPSEL field of ADC_EMR. To compare all channels, the CMPALL bit of ADC_EMR must be set. If set, the CMPTYPE bit of ADC_EMR can be used to discard all conversion results that do not match the comparison conditions. Once a conversion result matches the comparison conditions, all the subsequent conversion results are stored in ADC_LCDR (even if these results do not meet the comparison conditions). Setting the CMPRST bit in ADC_CR immediately stops the conversion result storage until the next comparison match. If the CMPTYPE bit in ADC_EMR is cleared, all conversions are stored in ADC_LCDR. Only the conversions that match the comparison conditions trigger the COMPE flag in ADC_ISR. Moreover, a filtering option can be set by writing the number of consecutive comparison matches needed to raise the flag. This number can be written and read in the CMPFILTER field of ADC_EMR. The filtering option is dedicated to reinforcing the detection of an analog signal overpassing a predefined threshold. The filter is cleared as soon as ADC_ISR is read, so this filtering function must be used with peripheral DMA controller and works only when using Interrupt mode (no polling). The flag can be read on the COMPE bit of the Interrupt Status register (ADC_ISR) and can trigger an interrupt. The high threshold and the low threshold can be read/write in the Compare Window register (ADC_CWR). Depending on the sign of the conversion, chosen with the SIGNMODE field in the ADC Extended Mode Register, the high threshold and low threshold values must be signed or unsigned to maintain consistency during the comparison. If the conversion is signed, both thresholds must also be signed; if the conversion is unsigned, both thresholds must be unsigned. If comparison occurs on all channels, the SIGNMODE field must be set to ALL_UNSIGNED or ALL_SIGNED and the thresholds must be set accordingly. 65.6.10 65.6.10.1 Differential and Single-ended Input Modes Input-output Transfer Functions The ADC can be configured to operate in the following input voltage modes: • Single-ended—ADC_COR.DIFFx = 0. This is the default mode after a reset. • Differential—ADC_COR.DIFFx = 1 (see Figure 65-7). In Differential mode, the ADC requires differential input signals having a VDD/ 2 common mode voltage (refer to the “Electrical Characteristics” section). The following equations give the unsigned ADC input-output transfer function in each mode(1). With signed conversions (see field ADC_EMR.SIGNMODE), subtract 2047 from the ADC_LCDR.DATA value given below. Single-ended mode: ADx – GNDANA ADC_LCDR.LDATA = ----------------------------------------------------------- × 2 12 ADVREF – GNDANA Differential mode: ADx – ADx+1 ADC_LCDR.LDATA =  1 + ----------------------------------------------------------- × 2 11  ADVREF – GNDANA Note 1: Equations assume ADC_EMR.OSR = 1 If the ANACH bit is set in ADC_MR, the ADC can manage both differential channels and single-ended channels. If the ANACH bit is cleared, the parameters defined in ADC_COR are applied to all channels. Table 65-4 gives the internal positive and negative ADC inputs assignment with respect to the programmed mode (ADC_COR.DIFFx). For example, if Differential mode is required on channel 0, input pins AD0 and AD1 are used. In this case, only channel 0 must be enabled by writing a 1 to ADC_CHER.CH0.  2017 Microchip Technology Inc. DS60001476B-page 2399 SAMA5D2 SERIES Table 65-4: Input Pins and Channel Numbers Channel Number Input Pin Single-ended Mode AD0 CH0 AD1 CH1 AD2 CH2 AD3 CH3 AD4 CH4 AD5 CH5 AD6 CH6 AD7 CH7 AD8 CH8 AD9 CH9 AD10 CH10 AD11 CH11 Figure 65-7: Differential Mode CH0 CH2 CH4 CH6 CH8 CH10 Analog Full Scale Ranges in Single-Ended/Differential Applications Single-ended Full differential VADVREF VIN+ VIN+ gain=1 )½ ) VADVREF VIN- 0 65.6.11 ADC Timings The ADC startup time is programmed through the STARTUP field in ADC_MR. Refer to section “Electrical Characteristics”. The ADC controller provides an inherent tracking time of six ADC clock cycles. A minimal tracking time is necessary for the ADC to guarantee the best converted final value between two conversions. The tracking time can be adjusted to accommodate a range of source impedances. If more than six ADC clock cycles are required, the tracking time can be increased using the TRACKTIM field in ADC_MR. Warning: No input buffer amplifier to isolate the source is included in the ADC. Refer to section “Electrical Characteristics”. 65.6.12 Last Channel Specific Measurement Trigger The last channel (higher index available) embeds a specific mode allowing a measurement trigger period which differs from other active channels. This allows efficient management of the conversions especially if the channel is driven by a device with a variation of a different frequency from other converted channels (for example, but not limited to, temperature sensor). The last channel can be sampled in different ways through the ADC controller. The different methods of sampling depend on the configuration field TRGMOD in ADC_TRGR and bit CH11 in ADC_CHSR. The last channel conversion can be triggered like the other channels by enabling CH11 of ADC_CHER. DS60001476B-page 2400  2017 Microchip Technology Inc. SAMA5D2 SERIES The manual start can only be performed if field TRGMOD = 0. When the START bit in ADC_CR is set, the last channel conversion is scheduled together with the other enabled channels (if any). The result of the conversion is placed in ADC_CDR11 register and the associated flag EOC11 is set in ADC_ISR. If the last channel is enabled in ADC_CHSR, DUALTRIG is cleared and field TRGMOD = 1, 2, 3, 5, the last channel is periodically converted together with the other enabled channels and the result is placed in the ADC_LCDR and ADC_CDR11 registers. Thus the last channel conversion result is part of the DMA Controller buffer (see Figure 65-8). When the conversion result matches the conditions defined in the ADC_LCTMR and ADC_LCCWR, the LCCHG flag is set in ADC_ISR. Figure 65-8: Same Trigger for All Channels (ADC_CHSR[LCI] = 1 and ADC_TRGR.TRGMOD = 1, 2, 3, 5) ADC_LCTMR.DUALTRIG = 1 Internal/External Trigger Event (Defined by TRGSEL field) ADC_CDR[0] C0 Notes: LC0 LC1 C0 C LC C2 C1 LC0 ADC_CDR[LCI] ADC_LCDR C LC C LC ADC_SEL LC1 C LC2 LC3 C2 C LC C5 C4 C3 LC2 C1 LC LC3 LC5 LC4 C3 LC4 C4 LC5 ADC_SEL: Command to the ADC analog cell Cx: All ADC channel values except the last channel (highest index) LCx: Last channel value LCI: Last channel index Assuming ADC_CHSR[0] = 1 and ADC_CHSR[LCI] = 1 trig.event1 DMA Buffer Structure trig.event2 trig.event3 0 ADC_CDR[0] DMA Transfer Base Address (BA) 0 ADC_CDR[LCI] BA + 0x02 0 ADC_CDR[0] BA + 0x04 0 ADC_CDR[LCI] BA + 0x06 0 ADC_CDR[0] BA + 0x08 0 ADC_CDR[LCI] BA + 0x0A If the last channel is driven by a device with a slower variation compared to other channels (temperature sensor for example), the channel can be enabled/disabled at any time. However, this may not be optimal for downstream processing. The ADC controller allows a different way of triggering the measurement when DUALTRIG is set in the Last Channel Trigger Mode Register (ADC_LCTMR) but CH11 is not set in ADC_CHSR. Under these conditions, the last channel conversion is triggered with a period defined by the OUT1 field in the RTC_MR (Real-time Clock Mode Register) while other channels are still active. OUT1 configures an internal trigger generated by the RTC, totally independent of the internal/external triggers. The RTC event will be processed on the next internal/external trigger event as described in Figure 65-9. The internal/external trigger for other channels is selected through the TRGSEL field of ADC_MR. When DUALTRIG = 1, the result of each conversion of channel 11 is only uploaded in the ADC_CDR11 register and not in ADC_LCDR (see Figure 65-9). Therefore, there is no change in the structure of the peripheral DMA controller buffer due to the conversion of the last channel: only the enabled channels are kept in the buffer. The end of conversion of the last channel is reported by the EOC11 flag in ADC_ISR.  2017 Microchip Technology Inc. DS60001476B-page 2401 SAMA5D2 SERIES Figure 65-9: Independent Trigger Measurement for Last Channel (ADC_CHSR[LCI] = 0 and ADC_TRGR.TRGMOD = 1, 2, 3, 5) ADC_LCTMR.DUALTRIG = 1 period defined by RTC_MR.OUT1 Internal RTC Trigger event LC conv. scheduled on TRGSEL trigger event Internal/External Trigger Event (Defined by TRGSEL) C LC ADC_SEL ADC_CDR[0] and ADC_LCDR C0 ADC_CDR[LCI] LC0 Notes: C C1 C LC C C2 C3 LC1 C C4 C5 LC2 ADC_SEL: Command to the ADC analog cell Cx: All ADC channel values except the last channel (highest index) LCx: Last channel value LCI: Last channel index Assuming ADC_CHSR[0] = 1 trig.event1 DMA Buffer Structure trig.event2 trig.event3 DMA Transfer 0 ADC_CDR[0] Base Address (BA) 0 ADC_CDR[0] BA + 0x02 0 ADC_CDR[0] BA + 0x04 If DUALTRIG = 1 and field ADC_TRGR.TRGMOD = 0 and none of the channels are enabled in ADC_CHSR (ADC_CHSR = 0), then only channel 11 is converted at a rate defined by the trigger event signal that can be configured in RTC_MR.OUT1 (see Figure 65-10). This mode of operation, when combined with the Sleep mode operation of the ADC Controller, provides a low-power mode for last channel measure. This assumes there is no other ADC conversion to schedule at a high sampling rate or no other channel to convert. DS60001476B-page 2402  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 65-10: Only Last Channel Measurement Triggered at Low Speed (ADC_CHSR[LCI] = 0 and ADC_TRGR.TRGMOD = 0) ADC_LCTMR.DUALTRIG = 1 period defined by RTC_MR.OUT1 Internal RTC Trigger Event LCI ADC_SEL ADC_CDR[LCI] Notes: 65.6.13 LCI LC1 LC0 LC2 ADC_SEL: Command to the ADC analog cell LCx: Last channel value LCI: Last channel index Enhanced Resolution Mode and Digital Averaging Function 65.6.13.1 Enhanced Resolution Mode The Enhanced Resolution mode is enabled if the OSR field is configured to 1 or 2 in ADC_EMR. The enhancement is based on a digital averaging function. There is no averaging on the last index channel if the measure is triggered by an RTC event. In this mode, the ADC Controller will trade off conversion speed against accuracy by averaging multiple samples, thus providing a digital low-pass filter function. The selected oversampling ratio applies to all enabled channels when triggered by an RTC event. k = N–1 1 ADC_LCDR.LDATA = ----- × M Σ ADC ( k ) k = 0 where N and M are given in the table below. Table 65-5: Digital Averaging Function Configuration versus OSR Values ADC_EMR.OSR Value ADC_LCDR.LDATA Length N Value M Value Full Scale Value Maximum Value 0 12 bits 1 1 4095 4095 1 13 bits 4 2 8191 8190 2 14 bits 16 4 16383 16381 The average result is valid in ADC_CDRx (x corresponds to the index of the channel) only if the EOCn flag is set in ADC_ISR and if the OVREn flag is cleared in ADC_OVER. The average result for all channels is valid in ADC_LCDR only if DRDY is set and GOVRE is cleared in ADC_ISR. Note that ADC_CDRs are not buffered. Therefore, when an averaging sequence is ongoing, the value in these registers changes after each averaging sample. However, overrun flags in ADC_OVER rise as soon as the first sample of an averaging sequence is received. Thus the previous averaged value is not read, even if the new averaged value is not ready. Consequently, when an overrun flag rises in ADC_OVER, it means that the previous unread data is lost but it does not mean that this data has been overwritten by the new averaged value as the averaging sequence concerning this channel can still be ongoing.  2017 Microchip Technology Inc. DS60001476B-page 2403 SAMA5D2 SERIES When an oversampling is performed, the maximum value that can be read on ADC_CDRx or ADC_LCDR is not the full-scale value, even if the maximum voltage is supplied on the analog input. See Table 65-5 “Digital Averaging Function Configuration versus OSR Values”. 65.6.13.2 Averaging Function versus Trigger Events The samples can be defined in different ways for the averaging function depending on the configuration of the ASTE bit in ADC_EMR and the USEQ bit in ADC_MR. When USEQ = 0, there are two possible ways to generate the averaging through the trigger event. If ASTE = 0 in ADC_EMR, every trigger event generates one sample for each enabled channel as described in Figure 65-11. Therefore four trigger events are requested to obtain the result of averaging if OSR = 1. Figure 65-11: Digital Averaging Function Waveforms Over Multiple Trigger Events ADC_EMR.OSR = 1, ASTE = 0, ADC_CHSR[1:0] = 0x3 and ADC_MR.USEQ = 0 Internal/External Trigger Event ADC_SEL ADC_CDR[0] 0 0 1 CH0_0 0 1 0i1 0i2 0 1 1 0i3 0 1 CH0_1 0i1 Read ADC_CDR[0] EOC[0] OVR[0] ADC_CDR[1] CH1_0 1i1 1i2 1i3 CH1_1 1i1 Read ADC_CDR[1] Read ADC_CDR[1] EOC[1] ADC_LCDR CH1_0 CH0_1 CH1_1 DRDY Read ADC_LCDR Read ADC_LCDR Note: ADC_SEL: Command to the ADC analog cell 0i1, 0i2, 0i3, 1i1, 1i2, 1i3 are intermediate results and CH0_0, CH0_1, CH1_0 and CH1_1 are final results of average function. If ASTE = 1 in ADC_EMR and USEQ = 0 in ADC_MR, the sequence to be converted, defined in ADC_CHSR, is automatically repeated n times (where n corresponds to the oversampling ratio defined in the OSR field in ADC_EMR). As a result, only one trigger is required to obtain the result of the averaging function as described in Figure 65-12. DS60001476B-page 2404  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 65-12: Digital Averaging Function Waveforms on a Single Trigger Event ADC_EMR.OSR = 1, ASTE = 1, ADC_CHSR[1:0] = 0x3 and ADC_MR.USEQ = 0 Internal/External Trigger Event ADC_SEL ADC_CDR[0] 0 CH0_0 1 0 1 0i1 0 1 0i2 0 1 0 0i3 1 0 1 CH0_1 Read ADC_CDR[0] EOC[0] ADC_CDR[1] CH1_0 1i1 1i2 1i3 CH1_1 Read ADC_CDR[1] EOC[1] CH0_1 ADC_LCDR CH1_1 DRDY Read ADC_LCDR Note: ADC_SEL: Command to the ADC analog cell 0i1, 0i2, 0i3, 1i1, 1i2, 1i3 are intermediate results and CH0_0, CH0_1, CH1_0 and CH1_1 are final results of average function. When USEQ = 1, the user can define the channel sequence to be converted by configuring ADC_SEQRx and ADC_CHER so that channels are not interleaved during the averaging period. Under these conditions, a sample is defined for each end of conversion as described in Figure 65-13. When USEQ = 1 and ASTE = 1, OSR can be only configured to 1. Up to three channels can be converted in this mode. The averaging result will be placed in the corresponding ADC_CDRx and in ADC_LCDR for each trigger event. The ADC real sample rate remains the maximum ADC sample rate divided by 4. It is important that the user sequence follows a specific pattern. The user sequence must be programmed in such a way that it generates a stream of conversion, where a same channel is successively converted. Table 65-6: Example Sequence Configurations (USEQ = 1, ASTE = 1, OSR = 1) Number of Channels Non-interleaved Averaging - Register Value Register 1 (e.g., CH0) 2 (e.g., CH0, CH1) 3 (e.g., CH0, CH1, CH2) ADC_CHSR 0x0000_000F 0x0000_00FF 0x0000_0FFF ADC_SEQR1 0x0000_0000 0x1111_0000 0x1111_0000 ADC_SEQR2 0x0000_0000 0x0000_0000 0x0000_2222  2017 Microchip Technology Inc. DS60001476B-page 2405 SAMA5D2 SERIES Figure 65-13: Digital Averaging Function Waveforms on a Single Trigger Event, Non-interleaved ADC_EMR.OSR = 1, ASTE = 1, ADC_CHSR[7:0] = 0xFF and ADC_MR.USEQ = 1 ADC_SEQR1 = 0x1111_0000 Internal/External Trigger Event ADC_SEL ADC_CDR[0] 0 0 0 0 CH0_0 0i1 0i2 0i3 1 1 1 0 0 0 0 CH0_1 Read ADC_CDR[0] EOC[0] ADC_CDR[1] 1 CH1_0 1i1 1i2 1i3 CH1_1 Read ADC_CDR[1] EOC[1] ADC_LCDR CH0_1 CH1_1 DRDY Read ADC_LCDR Note: 65.6.14 ADC_SEL: Command to the ADC analog cell 0i1, 0i2, 0i3, 1i1, 1i2, 1i3 are intermediate results and CH0_0, CH0_1, CH1_0 and CH1_1 are final results of average function. Automatic Error Correction The ADC features automatic error correction of conversion results. Offset and gain error corrections are available. The correction can be enabled for each channel and correction values (offset and gain) are the same for all channels. To enable error correction, the corresponding ECORRx bit must be set in the Channel Error Correction Register (ADC_CECR). The offset and gain values used to compensate the results are the same for all correction-enabled channels and programmed in the Correction Values Register (ADC_CVR). The error correction for channels used with the touchscreen is available in the ADC Touchscreen Correction Values Register (ADC_TSCVR). The ADCMODE field in ADC_EMR is used to configure a running mode of the ADC Normal mode, Offset Error mode, or Gain Error mode (see Section 65.7.16 “ADC Extended Mode Register”). ADCMODE uses 3 internal references to be measured and to extract the offset and gain error from 3 point-measurement codes. If some references already exist on the final application connected to some input channel ADx, they can be used as a replacement of the ADCMODE to generate the 2 or 3 points of calibration and used to extract the GAINCORR and OFFSETCORR. After a reset, the running mode of the ADC is Normal mode. Offset Error mode and Gain Error mode are used to determine values of offset compensation and gain compensation, respectively, to apply to conversion results. Table 65-7 provides formulas to obtain the compensation values, with: • • • • • • OFFSETCORR—the Offset Correction value. OFFSETCORR is a signed value. GAINCORR—the Gain Correction value GCi—the intermediate Gain Compensation value Gs—the value 13 ConvValue—the value converted by the ADC (as returned in ADC_LCDR or ADC_CDR) Resolution—the resolution used to process the conversion (either RESOLUTION, RESOLUTION+1 or RESOLUTION+2). DS60001476B-page 2406  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 65-7: ADC Running Modes ADC_EMR.ADCMODE Mode Description 0 Normal Normal mode of operation to perform conversions 1 Offset Error For unsigned conversions: OFFSETCORR = ConvValue − 2(Resolution − 1) For signed conversions: OFFSETCORR = ConvValue 2 GCi = ConvValue Gain Error 3 3584 ( Gs ) GAINCORR = ------------------------------------------------- × 2 GCi – ConvValue The final conversion result after error correction is obtained using the following formula: GAINCORR Corrected Data = ( Converted Data + OFFSETCORR ) × ---------------------------------( Gs ) 2  2017 Microchip Technology Inc. DS60001476B-page 2407 SAMA5D2 SERIES 65.6.15 65.6.15.1 Touchscreen Touchscreen Mode The TSMODE parameter of the ADC Touchscreen Mode register (ADC_TSMR) is used to enable/disable the touchscreen functionality, to select the type of screen (4-wire or 5-wire) and, in the case of a 4-wire screen and to activate (or not) the pressure measurement. In 4-wire mode, channel 0, 1, 2 and 3 must not be used for classic ADC conversions. Likewise, in 5-wire mode, channel 0, 1, 2, 3, and 4 must not be used for classic ADC conversions. 65.6.15.2 4-wire Resistive Touchscreen Principles A resistive touchscreen is based on two resistive films, each one being fitted with a pair of electrodes, placed at the top and bottom on one film, and on the right and left on the other. In between, there is a layer acting as an insulator, but also enables contact when you press the screen. This is illustrated in Figure 65-14. The ADC controller can perform the following tasks without external components: • position measurement • pressure measurement • pen detection Figure 65-14: Touchscreen Position Measurement Pen Contact XP YM YP XM VDD XP YP XP Volt XM GND Vertical Position Detection 65.6.15.3 VDD YP Volt YM GND Horizontal Position Detection 4-wire Position Measurement Method As shown in Figure 65-14, to detect the position of a contact, a supply is first applied from top to bottom. Due to the linear resistance of the film, there is a voltage gradient from top to bottom. When a contact is performed on the screen, the voltage propagates at the point the two surfaces come into contact with the second film. If the input impedance on the right and left electrodes sense is high enough, the film does not affect this voltage, despite its resistive nature. For the horizontal direction, the same method is used, but by applying supply from left to right. The range depends on the supply voltage and on the loss in the switches that connect to the top and bottom electrodes. In an ideal world (linear, with no loss through switches), the horizontal position is equal to: VYM / VDD or VYP / VDD. The implementation with on-chip power switches is shown in Figure 65-15. The voltage measurement at the output of the switch compensates for the switches loss. It is possible to correct for switch loss by performing the operation: DS60001476B-page 2408  2017 Microchip Technology Inc. SAMA5D2 SERIES [VYP - VXM] / [VXP - VXM]. This requires additional measurements, as shown in Figure 65-15. Figure 65-15: Touchscreen Switches Implementation XP VDDANA 0 XM GNDANA 1 To the ADC YP VDDANA 2 YM GNDANA 3 VDDANA VDDANA Switch Resistor Switch Resistor YP XP XP YP YM XM Switch Resistor Switch Resistor GND Horizontal Position Detection 65.6.15.4 GND Vertical Position Detection 4-wire Pressure Measurement Method The method to measure the pressure (Rp) applied to the touchscreen is based on the known resistance of the X-Panel resistance (Rxp). Three conversions (Xpos,Z1,Z2) are necessary to determine the value of Rp (Zaxis resistance). Rp = Rxp × (Xpos/1024) × [(Z2/Z1)-1]  2017 Microchip Technology Inc. DS60001476B-page 2409 SAMA5D2 SERIES Figure 65-16: Pressure Measurement VDDANA VDDANA Switch Resistor Switch Resistor XP YM YP Rp YM XM Open circuit Switch Resistor XP YP Rp XM GND XPos Measure(Yp) YM XM Open circuit Switch Resistor Switch Resistor Open circuit XP YP Rp 65.6.15.5 VDDANA Switch Resistor GND GND Z1 Measure(Xp) Z2 Measure(Xp) 5-wire Resistive Touchscreen Principles To make a 5-wire touchscreen, a resistive layer with a contact point at each corner and a conductive layer are used. The 5-wire touchscreen differs from the 4-wire type mainly in that the voltage gradient is applied only to one layer, the resistive layer, while the other layer is the sense layer for both measurements. The measurement of the X position is obtained by biasing the upper left corner and lower left corner to VDDANA and the upper right corner and lower right to ground. To measure along the Y axis, bias the upper left corner and upper right corner to VDDANA and bias the lower left corner and lower right corner to ground. Figure 65-17: 5-Wire Principle UL Pen Contact Resistive layer UR Sense LL LR Conductive Layer UL VDDANA UR VDDANA for Yp GND for Xp Sense LL VDDANA for Xp GND for Yp DS60001476B-page 2410 LR GND  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.6.15.6 5-wire Position Measurement Method In an application only monitoring clicks, 100 points per second is typically needed. For handwriting or motion detection, the number of measurements to consider is approximately 200 points per second. This must take into account that multiple measurements are included (over sampling, filtering) to compute the correct point. The 5-wire touchscreen panel works by applying a voltage at the corners of the resistive layer and measuring the vertical or horizontal resistive network with the sense input. The ADC converts the voltage measured at the point the panel is touched. A measurement of the Y position of the pointing device is made by: • Connecting Upper left (UL) and upper right (UR) corners to VDDANA • Connecting Lower left (LL) and lower right (LR) corners to ground. The voltage measured is determined by the voltage divider developed at the point of touch (Y position) and the SENSE input is converted by ADC. A measurement of the X position of the pointing device is made by: • Connecting the upper left (UL) and lower left (LL) corners to ground • Connecting the upper right and lower right corners to VDDANA. The voltage measured is determined by the voltage divider developed at the point of touch (X position) and the SENSE input is converted by ADC. Figure 65-18: Touchscreen Switches Implementation UL VDDANA UR GNDANA 0 VDDANA 1 GNDANA LL VDDANA Sense LR UL VDDANA 2 To the ADC 3 GNDANA 4 UR VDDANA for Ypos GND for Xpos Sense LL  2017 Microchip Technology Inc. VDDANA for Xpos GND for Ypos LR GND DS60001476B-page 2411 SAMA5D2 SERIES 65.6.15.7 Sequence and Noise Filtering The ADC Controller can manage ADC conversions and touchscreen measurement. On each trigger event the sequence of ADC conversions is performed as described in Section 65.6.8 “Sleep Mode and Conversion Sequencer”. The touchscreen measure frequency can be specified in number of trigger events by writing the TSFREQ parameter in ADC_TSMR. An internal counter counts triggers up to TSFREQ, and every time it rolls out, a touchscreen sequence is appended to the classic ADC conversion sequence (see Figure 65-19). Additionally the user can average multiple touchscreen measures by writing the TSAV parameter in ADC_TSMR. This can be 1, 2, 4 or 8 measures performed on consecutive triggers as illustrated in Figure 65-19 below. Consequently, the TSFREQ parameter must be greater or equal to the TSAV parameter. Figure 65-19: Insertion of Touchscreen Sequences (TSFREQ = 2; TSAV = 1) Trigger event ADC_SEL C T C T C C C C: Classic ADC Conversion Sequence - T C T C T: Touchscreen Sequence XRDY Read the ADC_XPOSR Read the ADC_XPOSR YRDY Note: 65.6.15.8 ADC_SEL: Command to the ADC analog cell Read the ADC_YPOSR Read the ADC_YPOSR Measured Values, Registers and Flags As soon as the controller finishes the Touchscreen sequence, XRDY, YRDY and PRDY are set and can generate an interrupt. These flags can be read in the ADC Interrupt Status register (ADC_ISR). They are reset independently by reading in the ADC Touchscreen X Position register (ADC_XPOSR), the ADC Touchscreen Y Position register (ADC_YPOSR) and the ADC Touchscreen Pressure register (ADC_PRESSR). ADC_XPOSR presents XPOS (VX - VXmin) on its LSB and XSCALE (VXMAX - VXmin) aligned on the 16th bit. ADC_YPOSR presents YPOS (VY - VYmin) on its LSB and YSCALE (VYMAX - VYmin) aligned on the 16th bit. To improve the quality of the measure, the user must calculate XPOS/XSCALE and YPOS/YSCALE. VXMAX, VXmin, VYMAX, and VYmin are measured at the first startup of the controller. These values can change during use, so it can be necessary to refresh them. Refresh can be done by writing ‘1’ in the TSCALIB field of the control register (ADC_CR). ADC_PRESSR presents Z1 on its LSB and Z2 aligned on the 16th bit. See Section 65.6.15.4 “4-wire Pressure Measurement Method”. 65.6.15.9 Pen Detect Method When there is no contact, it is not necessary to perform a conversion. However, it is important to detect a contact by keeping the power consumption as low as possible. The implementation polarizes one panel by closing the switch on (XP/UL) and ties the horizontal panel by an embedded resistor connected to YM / Sense. This resistor is enabled by a fifth switch. Since there is no contact, no current is flowing and there is no related power consumption. As soon as a contact occurs, a current is flowing in the Touchscreen and a Schmitt trigger detects the voltage in the resistor. The Touchscreen Interrupt configuration is entered by programming the PENDET bit in ADC_TSMR. If this bit is written at 1, the controller samples the pen contact state when it is not converting and waiting for a trigger. To complete the circuit, a programmable debouncer is placed at the output of the Schmitt trigger. This debouncer is programmable up to 215 ADC clock periods. The debouncer length can be selected by programming the field PENDBC in ADC_TSMR. Due to the analog switch’s structure, the debouncer circuitry is only active when no conversion (touchscreen or classic ADC channels) is in progress. Thus, if the time between the end of a conversion sequence and the arrival of the next trigger event is lower than the debouncing time configured on PENDBC, the debouncer will not detect any contact. DS60001476B-page 2412  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 65-20: Touchscreen Pen Detect X+/UL VDDANA X-/UR GNDANA 0 VDDANA 1 GNDANA Y+/LL Y-/SENSE LR VDDANA GNDANA GNDANA 2 To the ADC 3 4 PENDBC Debouncer Pen Interrupt GND The touchscreen pen detect can be used to generate an ADC interrupt to wake up the system. The pen detect generates two types of status, reported in ADC_ISR: • the PEN bit is set as soon as a contact exceeds the debouncing time as defined by PENDBC and remains set until ADC_ISR is read. • the NOPEN bit is set as soon as no current flows for a time over the debouncing time as defined by PENDBC and remains set until ADC_ISR is read. Both bits are automatically cleared as soon as ADC_ISR is read, and can generate an interrupt by writing ADC_IER. Moreover, the rising of either one of them clears the other, they cannot be set at the same time. The PENS bit of ADC_ISR shows the current status of the pen contact. 65.6.16 Asynchronous and Partial Wakeup (SleepWalking) This operating mode is a means of data pre-processing that qualifies an incoming event, thus allowing the ADC to decide whether or not to wake up the system. Asynchronous and partial wakeup is mainly used when the system is in Wait mode (refer to the PMC section for further details). It can also be enabled when the system is fully running. Once the Asynchronous and partial wakeup mode is enabled, no access must be performed in the ADC before a wakeup is performed by the ADC. When the Asynchronous and partial wakeup mode is enabled for the ADC (refer to the PMC section), the PMC decodes a clock request from the ADC. The clock request is generated as soon as a trigger event occurs. Only a trigger from RTC or ADTRG pin can be used in partial wakeup mode. The selection between RTC or ADTRG pin is performed through the ADC_MR.TRGSEL field. If the system is in Wait mode (processor and peripheral clocks switched off), the PMC restarts the fast RC oscillator and provides the clock only to the ADC. To perform a conversion at regular intervals with RTC trigger, the RTC must be configured with the following settings: RTC_MR.OUT0=7 and RTC_MR.THIGH=7. The period of the trigger can be defined in RTC_MR.TPERIOD. To trigger a conversion using the ADTRG pin, the minimum high level duration of the ADTRG signal must be greater than 2 clock periods of the fast RC oscillator. The maximum duration of the high level must be limited to the amount of startup and conversion time. As soon as the clock is provided by the PMC, the ADC processes the conversions and compares the converted values with LOWTHRES and HIGHTHRES field values in ADC_CWR.  2017 Microchip Technology Inc. DS60001476B-page 2413 SAMA5D2 SERIES The ADC instructs the PMC to disable the clock if the converted value does not meet the conditions defined by LOWTHRES and HIGHTHRES field values in ADC_CWR. If the converted value meets the conditions, the ADC instructs the PMC to exit the full system from Wait mode. If the processor and peripherals are running, the ADC can be configured in Asynchronous and partial wakeup mode by enabling the PMC_SLPWK_ER (refer to the PMC section). When a trigger event occurs, the ADC requests the clock from the PMC and the comparison is performed. If there is a comparison match, the ADC continues to request the clock. If there is no match, the clock is switched off for the ADC only, until a new trigger event is detected. It is recommended to write a ‘1’ to the SLEEP bit to reduce the power consumption of the analog part of the ADC when the system is waiting for a trigger event. 65.6.17 Buffer Structure The DMA read channel is triggered each time a new data is stored in ADC_LCDR. The same structure of data is repeatedly stored in ADC_LCDR each time a trigger event occurs. Depending on user mode of operation (ADC_MR, ADC_CHSR, ADC_SEQR1, ADC_SEQR2, ADC_TSMR) the structure differs. Each data read to DMA buffer, carried on a half-word (16-bit), consists of last converted data right aligned and when TAG is set in ADC_EMR, the four most significant bits are carrying the channel number thus allowing an easier post-processing in the DMA buffer or better checking the DMA buffer integrity. Figure 65-21: Buffer Structure Assuming ADC_CHSR = 0x000_01600 ADC_EMR.TAG = 1 trig.event1 DMA Buffer Structure trig.event2 Assuming ADC_CHSR = 0x000_01600 ADC_EMR.TAG = 0 5 ADC_CDR5 DMA Transfer Base Address (BA) 6 ADC_CDR6 BA + 0x02 8 ADC_CDR8 BA + 0x04 5 ADC_CDR5 6 trig.event1 0 ADC_CDR5 0 ADC_CDR6 0 ADC_CDR8 BA + 0x06 0 ADC_CDR5 ADC_CDR6 BA + 0x08 0 ADC_CDR6 8 ADC_CDR8 BA + 0x0A 0 ADC_CDR8 5 ADC_CDR5 BA + [(N-1) * 6] 0 ADC_CDR5 6 ADC_CDR6 BA + [(N-1) * 6]+ 0x02 0 ADC_CDR6 8 ADC_CDR8 BA + [(N-1) * 6]+ 0x04 0 ADC_CDR8 DMA Buffer Structure trig.event2 trig.eventN trig.eventN As soon as touchscreen conversions are required, the pen detection function may help the post-processing of the buffer. See Section 65.6.17.4 “Pen Detection Status”. 65.6.17.1 Classic ADC Channels Only (Touchscreen Disabled) When no touchscreen conversion is required (i.e., TSMODE = 0 in ADC_TSMR), the structure of data within the buffer is defined by ADC_MR, ADC_CHSR, ADC_SEQRx. See Figure 65-21. If the user sequence is not used (i.e., USEQ is cleared in ADC_MR) then only the value of ADC_CHSR defines the data structure. For each trigger event, enabled channels will be consecutively stored in ADC_LCDR and automatically read to the buffer. When the user sequence is configured (i.e., USEQ is set in ADC_MR) not only does ADC_CHSR modify the data structure of the buffer, but ADC_SEQRx registers may modify the data structure of the buffer as well. 65.6.17.2 Touchscreen Channels Only When only touchscreen conversions are required (i.e., TSMODE ≠ 0 in ADC_TSMR and ADC_CHSR equals 0), the structure of data within the buffer is defined by ADC_TSMR. DS60001476B-page 2414  2017 Microchip Technology Inc. SAMA5D2 SERIES When TSMODE = 1 or 3, each trigger event adds two half-words in the buffer (assuming TSAV = 0), first half-word being XPOS of ADC_XPOSR then YPOS of ADC_YPOSR. If TSAV/TSFREQ ≠ 0, the data structure remains unchanged. Not all trigger events add data to the buffer. When TSMODE = 2, each trigger event adds four half-words to the buffer (assuming TSAV = 0), first half-word being XPOS of ADC_XPOSR followed by YPOS of ADC_YPOSR and finally Z1 followed by Z2, both located in ADC_PRESSR. When TAG is set (ADC_EMR), the CHNB field (four most significant bits of ADC_LCDR) is cleared when XPOS is transmitted and set when YPOS is transmitted, allowing an easier post-processing of the buffer or a better checking of the buffer integrity. In case 4-wire with Pressure mode is selected, Z1 value is transmitted to the buffer along with tag set to 2 and Z2 is tagged with value 3. XSCALE and YSCALE (calibration values) are not transmitted to the buffer because they are supposed to be constant and moreover only measured at the very first startup of the controller or upon user request. There is no change in buffer structure whatever the value of PENDET bit configuration in ADC_TSMR but it is recommended to use the pen detection function for buffer post-processing (see Section 65.6.17.4 “Pen Detection Status”).  2017 Microchip Technology Inc. DS60001476B-page 2415 SAMA5D2 SERIES Figure 65-22: Buffer Structure When Only Touchscreen Channels are Enabled Assuming ADC_TSMR.TSMOD = 1 or 3 ADC_TSMR.TSAV = 0 ADC_CHSR = 0x000_00000, ADC_EMR.TAG = 1 Assuming ADC_TSMR.TSMOD = 1 or 3 ADC_TSMR.TSAV = 0 ADC_CHSR = 0x000_00000, ADC_EMR.TAG = 0 trig.event1 trig.event1 DMA Buffer Structure trig.event2 0 ADC_XPOSR DMA Transfer Base Address (BA) 1 ADC_YPOSR BA + 0x02 0 ADC_XPOSR BA + 0x04 1 ADC_YPOSR BA + 0x06 0 ADC_XPOSR BA + [(N-1) * 4] DMA Buffer Structure trig.event2 trig.eventN 1 ADC_YPOSR DMA Buffer Structure trig.event2 0 ADC_YPOSR 0 ADC_XPOSR 0 ADC_YPOSR 0 ADC_XPOSR 0 ADC_YPOSR BA + [(N-1) * 4]+ 0x02 Assuming ADC_TSMR.TSMOD = 2 ADC_TSMR.TSAV = 0 ADC_CHSR = 0x000_00000, ADC_EMR.TAG = 0 0 ADC_XPOSR trig.event1 DMA Transfer Base Address (BA) 0 ADC_XPOSR 1 ADC_YPOSR BA + 0x02 0 ADC_YPOSR 2 ADC_PRESSR(Z1) BA + 0x04 0 ADC_PRESSR(Z1) 3 ADC_PRESSR(Z2) BA + 0x06 0 ADC_PRESSR(Z2) 0 ADC_XPOSR BA + 0x08 0 ADC_XPOSR 1 ADC_YPOSR BA + 0x0A 0 ADC_YPOSR 2 ADC_PRESSR(Z1) BA + 0x0C 0 ADC_PRESSR(Z1) 3 ADC_PRESSR(Z2) BA + 0x0E 0 ADC_PRESSR(Z2) 0 ADC_XPOSR BA + [(N-1) * 8] 0 ADC_XPOSR 1 ADC_YPOSR 0 ADC_YPOSR 2 ADC_PRESSR(Z1) BA + [(N-1) * 8]+ 0x04 0 ADC_PRESSR(Z1) 3 ADC_PRESSR(Z2) BA + [(N-1) * 8]+ 0x06 0 ADC_PRESSR(Z2) DMA Buffer Structure trig.event2 trig.eventN DS60001476B-page 2416 ADC_XPOSR trig.eventN Assuming ADC_TSMR.TSMOD = 2 ADC_TSMR.TSAV = 0 ADC_CHSR = 0x000_00000, ADC_EMR.TAG = 1 trig.event1 0 trig.eventN BA + [(N-1) * 8]+ 0x02  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.6.17.3 Interleaved Channels When both classic ADC channels (CH4/CH5 up to CH12 are set in ADC_CHSR) and touchscreen conversions are required (TSMODE ≠ 0 in ADC_TSMR), the structure of the buffer differs according to TSAV and TSFREQ values. If TSFREQ ≠ 0, not all events generate touchscreen conversions, therefore the buffer structure is based on 2TSFREQ trigger events. Given a TSFREQ value, the location of touchscreen conversion results depends on TSAV value. When TSFREQ = 0, TSAV must equal 0. There is no change in buffer structure whatever the value of PENDET bit configuration in ADC_TSMR but it is recommended to use the pen detection function for buffer post-processing (see Section 65.6.17.4 “Pen Detection Status”).  2017 Microchip Technology Inc. DS60001476B-page 2417 SAMA5D2 SERIES Figure 65-23: Buffer Structure When Classic ADC and Touchscreen Channels are Interleaved Assuming ADC_TSMR.TSMOD = 1 ADC_TSMR.TSAV = ADC_TSMR.TSFREQ = 0 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 1 trig.event1 8 DMA Buffer Structure trig.event2 ADC_CDR8 DMA Transfer Base Address (BA) 0 ADC_XPOSR BA + 0x02 1 ADC_YPOSR BA + 0x04 Assuming ADC_TSMR.TSMOD = 1 ADC_TSMR.TSAV = ADC_TSMR.TSFREQ = 0 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 0 trig.event1 DMA Buffer Structure trig.event2 8 0 ADC_CDR8 BA + 0x06 ADC_XPOSR BA + 0x08 BA + 0x0A 1 ADC_YPOSR 8 ADC_CDR8 BA + [(N-1) * 6] ADC_XPOSR BA + [(N-1) * 6]+ 0x02 ADC_YPOSR BA + [(N-1) * 6]+ 0x04 trig.eventN 1 Assuming ADC_TSMR.TSMOD = 1 ADC_TSMR.TSAV = 0, ADC_TSMR.TSFREQ = 1 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 1 trig.event1 ADC_CDR8 DMA Transfer Base Address (BA) 0 ADC_XPOSR BA + 0x02 1 ADC_YPOSR BA + 0x04 8 ADC_CDR8 BA + 0x06 8 trig.event3 ADC_CDR8 BA + 0x08 0 ADC_XPOSR BA + 0x0A 1 ADC_YPOSR BA + 0x0c 8 ADC_CDR8 BA + 0x0e 8 ADC_CDR8 BA + [(N-1) * 8] 0 ADC_XPOSR BA + [(N-1) * 8]+ 0x02 1 ADC_YPOSR BA + [(N-1) * 8]+ 0x04 8 ADC_CDR8 BA + [(N-1) * 8]+ 0x06 8 trig.event4 trig.eventN trig.eventN+1 0 ADC_XPOSR 0 ADC_YPOSR 0 ADC_CDR8 0 ADC_XPOSR 0 ADC_YPOSR 0 ADC_CDR8 0 ADC_XPOSR 0 ADC_YPOSR Assuming ADC_TSMR.TSMOD = 1 ADC_TSMR.TSAV = 1, ADC_TSMR.TSFREQ = 1 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 1 trig.event1 trig.event2 trig.event2 ADC_CDR8 trig.eventN 0 DMA Buffer Structure 0 DMA Buffer Structure 8 ADC_CDR8 8 ADC_CDR8 0 ADC_XPOSR 1 ADC_YPOSR 8 ADC_CDR8 8 ADC_CDR8 0 ADC_XPOSR 1 ADC_YPOSR 8 ADC_CDR8 8 ADC_CDR8 0 ADC_XPOSR 1 ADC_YPOSR trig.event3 trig.event4 trig.eventN DS60001476B-page 2418 trig.eventN+1  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.6.17.4 Pen Detection Status If the pen detection measure is enabled (PENDET is set in ADC_TSMR), the XPOS, YPOS, Z1, Z2 values transmitted to the buffer through ADC_LCDR are cleared (including the CHNB field), if the PENS flag of ADC_ISR is 0. When the PENS flag is set, XPOS, YPOS, Z1, Z2 are normally transmitted. Therefore, using pen detection together with tag function eases the post-processing of the buffer, especially to determine which touchscreen converted values correspond to a period of time when the pen was in contact with the screen. When the pen detection is disabled or the tag function is disabled, XPOS, YPOS, Z1, Z2 are normally transmitted without tag and no relationship can be found with pen status, thus post-processing may not be easy. Figure 65-24: Buffer Structure With and Without Pen Detection Enabled Assuming ADC_TSMR.TSMOD = 1, PENDET = 1 ADC_TSMR.TSAV = ADC_TSMR.TSFREQ = 0 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 1 ADC_CDR8 DMA Transfer Base Address (BA) 0 ADC_XPOSR BA + 0x02 1 ADC_YPOSR BA + 0x04 PENS = 1 8 DMA buffer Structure trig.event2 8 0 ADC_CDR8 BA + 0x06 ADC_XPOSR BA + 0x08 trig.event1 DMA buffer Structure PENS = 1 trig.event1 Assuming ADC_TSMR.TSMOD = 1, PENDET = 1 ADC_TSMR.TSAV = ADC_TSMR.TSFREQ = 0 ADC_CHSR = 0x000_0100, ADC_EMR.TAG = 0 BA + 0x0A 1 ADC_YPOSR 8 ADC_CDR8 BA + [(N-1) * 6] 0 BA + [(N-1) * 6]+ 0x02 0 0 BA + [(N-1) * 6]+ 0x04 8 ADC_CDR8 0 0 0 0 0 2 successive tags cleared => PENS = 0 65.6.18 ADC_CDR8 0 ADC_XPOSR 0 ADC_YPOSR 0 ADC_CDR8 0 ADC_XPOSR 0 ADC_YPOSR 0 ADC_CDR8 0 ADC_XPOSR* 0 ADC_YPOSR* 0 ADC_CDR8 0 ADC_XPOSR* 0 ADC_YPOSR* trig.eventN PENS = 0 PENS = 0 trig.eventN trig.eventN+1 trig.event2 0 ADC_XPOSR*, ADC_YPOSR* can be any value when PENS = 0 Fault Event The ADC Controller internal fault output is directly connected to the PWM fault input. The fault event may be asserted depending on the configuration of ADC_EMR, ADC_CWR, ADC_LCMR and ADC_LCCWR and converted values. Two types of comparison can trigger a comparison event (fault output pulse): • The first comparison type is based on ADC_LCCWR settings, i.e., on all converted channels except the last one; • The second comparison type is linked to the last channel. As an example, overcurrent and temperature exceeding limits can trigger a fault to PWM. When the comparison event occurs, the ADC fault output generates a pulse of one peripheral clock cycle to the PWM fault input. This fault line can be enabled or disabled within PWM. Should it be activated and asserted by the ADC Controller, the PWM outputs are immediately placed in a safe state (pure combinational path). Note that the ADC fault output connected to the PWM is not the COMPE bit. Thus the Fault mode (FMOD) within the PWM configuration must be FMOD = 1. 65.6.19 Register Write Protection To prevent any single software error from corrupting ADC behavior, certain registers in the address space can be write-protected by setting the bit WPEN in the “ADC Write Protection Mode Register” (ADC_WPMR).  2017 Microchip Technology Inc. DS60001476B-page 2419 SAMA5D2 SERIES If a write access to the protected registers is detected, the WPVS flag in the “ADC Write Protection Status Register” (ADC_WPSR) is set and the field WPVSRC indicates the register in which the write access has been attempted. The WPVS flag is automatically reset by reading ADC_WPSR. The following registers are write-protected when WPEN is set in ADC_WPMR: • • • • • • • • • • • • • • • • ADC Mode Register ADC Channel Sequence 1 Register ADC Channel Sequence 2 Register ADC Channel Enable Register ADC Channel Disable Register ADC Last Channel Trigger Mode Register ADC Last Channel Compare Window Register ADC Extended Mode Register ADC Compare Window Register ADC Channel Offset Register ADC Analog Control Register ADC Touchscreen Mode Register ADC Trigger Register ADC Correction Values Register ADC Channel Error Correction Register ADC Touchscreen Correction Values Register DS60001476B-page 2420  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7 Analog-to-Digital (ADC) User Interface Table 65-8: Offset Register Mapping Register Name Access Reset 0x00 Control Register ADC_CR Write-only – 0x04 Mode Register ADC_MR Read/Write 0x00000000 0x08 Channel Sequence Register 1 ADC_SEQR1 Read/Write 0x00000000 0x0C Channel Sequence Register 2 ADC_SEQR2 Read/Write 0x00000000 0x10 Channel Enable Register ADC_CHER Write-only – 0x14 Channel Disable Register ADC_CHDR Write-only – 0x18 Channel Status Register ADC_CHSR Read-only 0x00000000 0x1C Reserved – – – 0x20 Last Converted Data Register ADC_LCDR Read-only 0x00000000 0x24 Interrupt Enable Register ADC_IER Write-only – 0x28 Interrupt Disable Register ADC_IDR Write-only – 0x2C Interrupt Mask Register ADC_IMR Read-only 0x00000000 0x30 Interrupt Status Register ADC_ISR Read-only 0x00000000 0x34 Last Channel Trigger Mode Register ADC_LCTMR Read/Write 0x00000000 0x38 Last Channel Compare Window Register ADC_LCCWR Read/Write 0x00000000 0x3C Overrun Status Register ADC_OVER Read-only 0x00000000 0x40 Extended Mode Register ADC_EMR Read/Write 0x00000000 0x44 Compare Window Register ADC_CWR Read/Write 0x00000000 0x48 Reserved – – – 0x4C Channel Offset Register ADC_COR Read/Write 0x00000000 0x50 Channel Data Register 0 ADC_CDR0 Read-only 0x00000000 0x54 Channel Data Register 1 ADC_CDR1 Read-only 0x00000000 ... ... ... ... Channel Data Register 11 ADC_CDR11 Read-only 0x00000000 Reserved – – – Analog Control Register ADC_ACR Read/Write 0x00000101 Reserved – – – 0xB0 Touchscreen Mode Register ADC_TSMR Read/Write 0x00000000 0xB4 Touchscreen X Position Register ADC_XPOSR Read-only 0x00000000 0xB8 Touchscreen Y Position Register ADC_YPOSR Read-only 0x00000000 0xBC Touchscreen Pressure Register ADC_PRESSR Read-only 0x00000000 0xC0 Trigger Register ADC_TRGR Read/Write 0x00000000 Reserved – – – 0xD4 Correction Values Register ADC_CVR Read/Write 0x00000000 0xD8 Channel Error Correction Register ADC_CECR Read/Write 0x00000000 ... 0x7C 0x80-–0x90 0x94 0x98–0xAC 0xC4–0xD0  2017 Microchip Technology Inc. DS60001476B-page 2421 SAMA5D2 SERIES Table 65-8: Register Mapping (Continued) Offset Register Name 0xDC Touchscreen Correction Values Register ADC_TSCVR 0xE0 Reserved – 0xE4 Write Protection Mode Register 0xE8 0xEC–0xFC Note: Access Reset Read/Write 0x00000000 – – ADC_WPMR Read/Write 0x00000000 Write Protection Status Register ADC_WPSR Read-only 0x00000000 Reserved – – – Any offset not listed in the table must be considered as “reserved”. DS60001476B-page 2422  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.1 ADC Control Register Name: ADC_CR Address: 0xFC030000 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 CMPRST 3 – 2 TSCALIB 1 START 0 SWRST SWRST: Software Reset 0: No effect. 1: Resets the ADC, simulating a hardware reset. START: Start Conversion 0: No effect. 1: Begins analog-to-digital conversion. TSCALIB: Touchscreen Calibration 0: No effect. 1: Programs screen calibration (VDD/GND measurement) If conversion is in progress, the calibration sequence starts at the beginning of a new conversion sequence. If no conversion is in progress, the calibration sequence starts at the second conversion sequence located after the TSCALIB command (Sleep mode, waiting for a trigger event). TSCALIB measurement sequence does not affect the Last Converted Data Register (ADC_LCDR). CMPRST: Comparison Restart 0: No effect. 1: Stops the conversion result storage until the next comparison match.  2017 Microchip Technology Inc. DS60001476B-page 2423 SAMA5D2 SERIES 65.7.2 ADC Mode Register Name: ADC_MR Address: 0xFC030004 Access: Read/Write 31 USEQ 30 MAXSPEED 29 28 23 ANACH 22 – 21 – 20 – 15 14 13 12 27 26 TRANSFER 25 24 17 16 TRACKTIM 19 18 STARTUP 11 10 9 8 3 2 TRGSEL 1 0 – PRESCAL 7 – 6 FWUP 5 SLEEP 4 – This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. TRGSEL: Trigger Selection Value Name 0 ADC_TRIG0 ADTRG 1 ADC_TRIG1 TIOA0 2 ADC_TRIG2 TIOA1 3 ADC_TRIG3 TIOA2 4 ADC_TRIG4 PWM event line 0 5 ADC_TRIG5 PWM event line 1 6 ADC_TRIG6 TIOA3 7 ADC_TRIG7 RTCOUT0 Note: Description The trigger selection can be performed only if TRGMOD = 1, 2 or 3 in ADC Trigger Register. SLEEP: Sleep Mode Value Name 0 NORMAL 1 SLEEP Description Normal Mode: The ADC core and reference voltage circuitry are kept ON between conversions. Sleep Mode: The wakeup time can be modified by programming the FWUP bit. FWUP: Fast Wakeup Value Name Description 0 OFF If SLEEP is 1, then both ADC core and reference voltage circuitry are OFF between conversions 1 ON If SLEEP is 1, then Fast Wakeup Sleep mode: The voltage reference is ON between conversions and ADC core is OFF PRESCAL: Prescaler Rate Selection PRESCAL = (fperipheral clock / (2 × fADCCLK)) – 1. DS60001476B-page 2424  2017 Microchip Technology Inc. SAMA5D2 SERIES STARTUP: Startup Time Value Name Description 0 SUT0 0 periods of ADCCLK 1 SUT8 8 periods of ADCCLK 2 SUT16 16 periods of ADCCLK 3 SUT24 24 periods of ADCCLK 4 SUT64 64 periods of ADCCLK 5 SUT80 80 periods of ADCCLK 6 SUT96 96 periods of ADCCLK 7 SUT112 112 periods of ADCCLK 8 SUT512 512 periods of ADCCLK 9 SUT576 576 periods of ADCCLK 10 SUT640 640 periods of ADCCLK 11 SUT704 704 periods of ADCCLK 12 SUT768 768 periods of ADCCLK 13 SUT832 832 periods of ADCCLK 14 SUT896 896 periods of ADCCLK 15 SUT960 960 periods of ADCCLK ANACH: Analog Change Value Name Description 0 NONE No analog change on channel switching: DIFF0 is used for all channels. 1 ALLOWED Allows different analog settings for each channel. See ADC Channel Offset Register. TRACKTIM: Tracking Time Value Name Description 0 ADCCLK6 The tracking time is 6 ADC clock cycles. 1–14 – The tracking time is 6 ADC clock cycles. 15 ADCCLK7 The tracking time is 7 ADC clock cycles. TRANSFER: Transfer Time The TRANSFER field must be set to 2 to guarantee the optimal transfer time. MAXSPEED: Maximum Sampling Rate Enable in Freerun Mode This bit should always be set to 0. USEQ: Use Sequence Enable Value Name 0 NUM_ORDER Normal mode: The controller converts channels in a simple numeric order depending only on the channel index. 1 REG_ORDER User Sequence mode: The sequence respects what is defined in ADC_SEQR1 and ADC_SEQR2 registers and can be used to convert the same channel several times.  2017 Microchip Technology Inc. Description DS60001476B-page 2425 SAMA5D2 SERIES 65.7.3 ADC Channel Sequence 1 Register Name: ADC_SEQR1 Address: 0xFC030008 Access: Read/Write 31 30 29 28 27 26 USCH8 23 22 21 20 19 18 USCH6 15 14 13 6 24 17 16 9 8 1 0 USCH5 12 11 10 USCH4 7 25 USCH7 USCH3 5 4 3 USCH2 2 USCH1 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. USCHx: User Sequence Number x The allowed range is 0 up to 11, thus only the sequencer from CH0 to CH11 can be used. This register activates only if the USEQ field in ADC_MR field is set to ‘1’. Any USCHx field is processed only if the CHx-1 it in ADC_CHSR reads logical ‘1’, else any value written in USCHx does not add the corresponding channel in the conversion sequence. Configuring the same value in different fields leads to multiple samples of the same channel during the conversion sequence. This can be done consecutively, or not, according to user needs. When configuring consecutive fields with the same value, the associated channel is sampled as many time as the number of consecutive values, this part of the conversion sequence being triggered by a unique event. DS60001476B-page 2426  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.4 ADC Channel Sequence 2 Register Name: ADC_SEQR2 Address: 0xFC03000C Access: 31 Read/Write 30 29 28 27 26 – 23 22 21 20 19 18 – 15 14 13 6 24 17 16 9 8 1 0 – 12 11 10 – 7 25 – USCH11 5 4 USCH10 3 2 USCH9 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. USCHx: User Sequence Number x The sequence number x (USCHx) can be programmed by the Channel number CHy where y is the value written in this field. The allowed range is 0 up to 11. So it is only possible to use the sequencer from CH0 to CH11. This register activates only if the USEQ field in ADC_MR is set to ‘1’. Any USCHx field is processed only if the CHx-1 bit in ADC_CHSR reads logical ‘1’. Else, any value written in USCHx does not add the corresponding channel in the conversion sequence. Configuring the same value in different fields leads to multiple samples of the same channel during the conversion sequence. This can be done consecutively, or not, according to user needs.  2017 Microchip Technology Inc. DS60001476B-page 2427 SAMA5D2 SERIES 65.7.5 ADC Channel Enable Register Name: ADC_CHER Address: 0xFC030010 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 CH11 10 CH10 9 CH9 8 CH8 7 CH7 6 CH6 5 CH5 4 CH4 3 CH3 2 CH2 1 CH1 0 CH0 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. CHx: Channel x Enable 0: No effect. 1: Enables the corresponding channel. Note: If USEQ = 1 in ADC_MR, CHx corresponds to the enable of sequence number x+1 described in ADC_SEQR1 and ADC_SEQR2 (e.g. CH0 enables sequence number USCH1). DS60001476B-page 2428  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.6 ADC Channel Disable Register Name: ADC_CHDR Address: 0xFC030014 Access: Write-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 CH11 10 CH10 9 CH9 8 CH8 7 CH7 6 CH6 5 CH5 4 CH4 3 CH3 2 CH2 1 CH1 0 CH0 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. CHx: Channel x Disable 0: No effect. 1: Disables the corresponding channel. 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 corresponding EOCx and GOVRE flags in ADC_ISR and OVREx flags in ADC_OVER are unpredictable.  2017 Microchip Technology Inc. DS60001476B-page 2429 SAMA5D2 SERIES 65.7.7 ADC Channel Status Register Name: ADC_CHSR Address: 0xFC030018 Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 CH11 10 CH10 9 CH9 8 CH8 7 CH7 6 CH6 5 CH5 4 CH4 3 CH3 2 CH2 1 CH1 0 CH0 CHx: Channel x Status 0: The corresponding channel is disabled. 1: The corresponding channel is enabled. DS60001476B-page 2430  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.8 ADC Last Converted Data Register Name: ADC_LCDR Address: 0xFC030020 Access: Read-only 31 – 30 – 29 – 28 27 26 CHNBOSR 25 24 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 3 2 1 0 LDATA 7 6 5 4 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. If OSR = 0 and TAG = 1 in ADC_EMR, the 4 MSB of LDATA carry the channel number to obtain a packed system memory buffer made of 1 converted data stored in a halfword (16-bit) instead of 1 converted data in a 32-bit word, thus dividing by 2 the size of the memory buffer. CHNBOSR: Channel Number in Oversampling Mode Indicates the last converted channel when the TAG bit is set in ADC_EMR and the OSR field is not equal to 0 in ADC_EMR0. If the TAG bit is not set, CHNBOSR = 0.  2017 Microchip Technology Inc. DS60001476B-page 2431 SAMA5D2 SERIES 65.7.9 ADC Interrupt Enable Register Name: ADC_IER Address: 0xFC030024 Access: Write-only 31 – 30 NOPEN 29 PEN 28 – 27 – 26 COMPE 25 GOVRE 24 DRDY 23 – 22 PRDY 21 YRDY 20 XRDY 19 LCCHG 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 EOC11 10 EOC10 9 EOC9 8 EOC8 7 EOC7 6 EOC6 5 EOC5 4 EOC4 3 EOC3 2 EOC2 1 EOC1 0 EOC0 The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Enables the corresponding interrupt. EOCx: End of Conversion Interrupt Enable x LCCHG: Last Channel Change Interrupt Enable XRDY: Touchscreen Measure XPOS Ready Interrupt Enable YRDY: Touchscreen Measure YPOS Ready Interrupt Enable PRDY: Touchscreen Measure Pressure Ready Interrupt Enable DRDY: Data Ready Interrupt Enable GOVRE: General Overrun Error Interrupt Enable COMPE: Comparison Event Interrupt Enable PEN: Pen Contact Interrupt Enable NOPEN: No Pen Contact Interrupt Enable DS60001476B-page 2432  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.10 ADC Interrupt Disable Register Name: ADC_IDR Address: 0xFC030028 Access: Write-only 31 – 30 NOPEN 29 PEN 28 – 27 – 26 COMPE 25 GOVRE 24 DRDY 23 – 22 PRDY 21 YRDY 20 XRDY 19 LCCHG 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 EOC11 10 EOC10 9 EOC9 8 EOC8 7 EOC7 6 EOC6 5 EOC5 4 EOC4 3 EOC3 2 EOC2 1 EOC1 0 EOC0 The following configuration values are valid for all listed bit names of this register: 0: No effect. 1: Disables the corresponding interrupt. EOCx: End of Conversion Interrupt Disable x LCCHG: Last Channel Change Interrupt Disable XRDY: Touchscreen Measure XPOS Ready Interrupt Disable YRDY: Touchscreen Measure YPOS Ready Interrupt Disable PRDY: Touchscreen Measure Pressure Ready Interrupt Disable DRDY: Data Ready Interrupt Disable GOVRE: General Overrun Error Interrupt Disable COMPE: Comparison Event Interrupt Disable PEN: Pen Contact Interrupt Disable NOPEN: No Pen Contact Interrupt Disable  2017 Microchip Technology Inc. DS60001476B-page 2433 SAMA5D2 SERIES 65.7.11 ADC Interrupt Mask Register Name: ADC_IMR Address: 0xFC03002C Access: Read-only 31 – 30 NOPEN 29 PEN 28 – 27 – 26 COMPE 25 GOVRE 24 DRDY 23 – 22 PRDY 21 YRDY 20 XRDY 19 LCCHG 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 EOC11 10 EOC10 9 EOC9 8 EOC8 7 EOC7 6 EOC6 5 EOC5 4 EOC4 3 EOC3 2 EOC2 1 EOC1 0 EOC0 The following configuration values are valid for all listed bit names of this register: 0: The corresponding interrupt is disabled. 1: The corresponding interrupt is enabled. EOCx: End of Conversion Interrupt Mask x LCCHG: Last Channel Change Interrupt Disable XRDY: Touchscreen Measure XPOS Ready Interrupt Mask YRDY: Touchscreen Measure YPOS Ready Interrupt Mask PRDY: Touchscreen Measure Pressure Ready Interrupt Mask DRDY: Data Ready Interrupt Mask GOVRE: General Overrun Error Interrupt Mask COMPE: Comparison Event Interrupt Mask PEN: Pen Contact Interrupt Mask NOPEN: No Pen Contact Interrupt Mask DS60001476B-page 2434  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.12 ADC Interrupt Status Register Name: ADC_ISR Address: 0xFC030030 Access: Read-only 31 PENS 30 NOPEN 29 PEN 28 – 27 – 26 COMPE 25 GOVRE 24 DRDY 23 – 22 PRDY 21 YRDY 20 XRDY 19 LCCHG 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 EOC11 10 EOC10 9 EOC9 8 EOC8 7 EOC7 6 EOC6 5 EOC5 4 EOC4 3 EOC3 2 EOC2 1 EOC1 0 EOC0 EOCx: End of Conversion x (automatically set / cleared) 0: The corresponding analog channel is disabled, or the conversion is not finished. This flag is cleared when reading the corresponding ADC_CDRx registers. 1: The corresponding analog channel is enabled and conversion is complete. LCCHG: Last Channel Change (cleared on read) 0: There is no comparison match (defined in the Last Channel Compare Window register (ADC_LCCWR) since the last read of ADC_ISR. 1: The converted value reported on ADC_CDR11 has changed since the last read of ADC_ISR, according to what is defined in the Last Channel Trigger Mode register (ADC_LCTMR) and Last Channel Compare Window register (ADC_LCCWR). XRDY: Touchscreen XPOS Measure Ready (cleared on read) 0: No measure has been performed since the last read of ADC_XPOSR. 1: At least one measure has been performed since the last read of ADC_ISR. YRDY: Touchscreen YPOS Measure Ready (cleared on read) 0: No measure has been performed since the last read of ADC_YPOSR. 1: At least one measure has been performed since the last read of ADC_ISR. PRDY: Touchscreen Pressure Measure Ready (cleared on read) 0: No measure has been performed since the last read of ADC_PRESSR. 1: At least one measure has been performed since the last read of ADC_ISR. DRDY: Data Ready (automatically set / cleared) 0: No data has been converted since the last read of ADC_LCDR. 1: At least one data has been converted and is available in ADC_LCDR. GOVRE: General Overrun Error (cleared on read) 0: No general overrun error occurred since the last read of ADC_ISR. 1: At least one general overrun error has occurred since the last read of ADC_ISR. COMPE: Comparison Event (cleared on read) 0: No comparison event since the last read of ADC_ISR. 1: At least one comparison event (defined in ADC_EMR and ADC_CWR) has occurred since the last read of ADC_ISR. PEN: Pen contact (cleared on read) 0: No pen contact since the last read of ADC_ISR. 1: At least one pen contact since the last read of ADC_ISR.  2017 Microchip Technology Inc. DS60001476B-page 2435 SAMA5D2 SERIES NOPEN: No Pen Contact (cleared on read) 0: No loss of pen contact since the last read of ADC_ISR. 1: At least one loss of pen contact since the last read of ADC_ISR. PENS: Pen Detect Status 0: The pen does not press the screen. 1: The pen presses the screen. Note: PENS is not a source of interruption. DS60001476B-page 2436  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.13 ADC Last Channel Trigger Mode Register Name: ADC_LCTMR Address: 0xFC030034 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 4 3 – 2 – 1 – 0 DUALTRIG CMPMOD This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. DUALTRIG: Dual Trigger ON 0: All channels are triggered by event defined by TRGSEL in ADC_MR. 1: Last channel (higher index) trigger period is defined by OUT1 in RTC_MR. CMPMOD: Last Channel Comparison Mode Value Name Description 0 LOW Generates the LCCHG flag in ADC_ISR when the converted data is lower than the low threshold of the window. 1 HIGH Generates the LCCHG flag in ADC_ISR when the converted data is higher than the high threshold of the window. 2 IN 3 OUT Generates the LCCHG flag in ADC_ISR when the converted data is in the comparison window. Generates the LCCHG flag in ADC_ISR when the converted data is out of the comparison window.  2017 Microchip Technology Inc. DS60001476B-page 2437 SAMA5D2 SERIES 65.7.14 ADC Last Channel Compare Window Register Name: ADC_LCCWR Address: 0xFC030038 Access: Read/Write 31 – 30 – 29 – 28 – 23 22 21 20 27 26 25 24 17 16 9 8 1 0 HIGHTHRES 19 18 11 10 HIGHTHRES 15 – 14 – 13 – 12 – 7 6 5 4 LOWTHRES 3 2 LOWTHRES This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. LOWTHRES: Low Threshold Low threshold associated to compare settings of ADC_LCTMR. HIGHTHRES: High Threshold High threshold associated to compare settings of ADC_LCTMR. DS60001476B-page 2438  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.15 ADC Overrun Status Register Name: ADC_OVER Address: 0xFC03003C Access: Read-only 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 OVRE11 10 OVRE10 9 OVRE9 8 OVRE8 7 OVRE7 6 OVRE6 5 OVRE5 4 OVRE4 3 OVRE3 2 OVRE2 1 OVRE1 0 OVRE0 OVREx: Overrun Error x 0: No overrun error on the corresponding channel since the last read of ADC_OVER. 1: An overrun error has occurred on the corresponding channel since the last read of ADC_OVER.  2017 Microchip Technology Inc. DS60001476B-page 2439 SAMA5D2 SERIES 65.7.16 ADC Extended Mode Register Name: ADC_EMR Address: 0xFC030040 Access: Read/Write 31 – 30 – 29 28 23 – 22 – 21 SRCCLK 15 – 14 – 13 7 6 27 – 26 20 ASTE 19 – 18 – 17 12 11 – 10 – 9 CMPALL 8 – 4 3 – 2 CMPTYPE 1 0 ADCMODE CMPFILTER 5 CMPSEL 25 24 TAG SIGNMODE 16 OSR CMPMODE This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. CMPMODE: Comparison Mode Value Name Description 0 LOW When the converted data is lower than the low threshold of the window, generates the COMPE flag in ADC_ISR or, in Partial Wakeup mode, defines the conditions to exit system from Wait mode. 1 HIGH When the converted data is higher than the high threshold of the window, generates the COMPE flag in ADC_ISR or, in Partial Wakeup mode, defines the conditions to exit system from Wait mode. 2 IN 3 OUT When the converted data is in the comparison window, generates the COMPE flag in ADC_ISR or, in Partial Wakeup mode, defines the conditions to exit system from Wait mode. When the converted data is out of the comparison window, generates the COMPE flag in ADC_ISR or, in Partial Wakeup mode, defines the conditions to exit system from Wait mode. CMPTYPE: Comparison Type Value Name 0 FLAG_ONLY 1 START_CONDITIO N Description Any conversion is performed and comparison function drives the COMPE flag. Comparison conditions must be met to start the storage of all conversions until the CMPRST bit is set. CMPSEL: Comparison Selected Channel If CMPALL = 0: CMPSEL indicates which channel has to be compared. If CMPALL = 1: No effect. CMPALL: Compare All Channels 0: Only channel indicated in CMPSEL field is compared. 1: All channels are compared. CMPFILTER: Compare Event Filtering Number of consecutive compare events necessary to raise the flag = CMPFILTER+1 When programmed to 0, the flag rises as soon as an event occurs. See Section 65.6.9 “Comparison Window” when using filtering option (CMPFILTER > 0). DS60001476B-page 2440  2017 Microchip Technology Inc. SAMA5D2 SERIES OSR: Over Sampling Rate Value Name Description 0 NO_AVERAGE 1 OSR4 1-bit enhanced resolution by averaging. ADC sample rate divided by 4. 2 OSR16 2-bit enhanced resolution by averaging. ADC sample rate divided by 16. No averaging. ADC sample rate is maximum. ASTE: Averaging on Single Trigger Event Value Name Description 0 MULTI_TRIG_AVERAGE The average requests several trigger events. 1 SINGLE_TRIG_AVERAGE The average requests only one trigger event. SRCCLK: External Clock Selection 0 (PERIPH_CLK): The peripheral clock is the source for the ADC prescaler. 1 (GCLK): GCLK is the source clock for the ADC prescaler, thus the ADC clock can be independent of the core/peripheral clock. TAG: Tag of ADC_LCDR 0: Sets CHNB field to zero in ADC_LCDR. 1: Appends the channel number to the conversion result in ADC_LCDR. SIGNMODE: Sign Mode Value Name 0 SE_UNSG_DF_SIGN 1 SE_SIGN_DF_UNSG 2 ALL_UNSIGNED 3 ALL_SIGNED Description Single-Ended channels: Unsigned conversions. Differential channels: Signed conversions. Single-Ended channels: Signed conversions. Differential channels: Unsigned conversions. All channels: Unsigned conversions. All channels: Signed conversions. If conversion results are signed and resolution is below 16 bits, the sign is extended up to the bit 15 (for example, 0xF43 for 12-bit resolution will be read as 0xFF43 and 0x467 will be read as 0x0467). See Section 65.6.6 “Conversion Results Format”. ADCMODE: ADC Running Mode Value Name Description 0 NORMAL 1 OFFSET_ERROR 2 GAIN_ERROR_HIGH Gain Error mode to measure the gain error. See Table 65-7. 3 GAIN_ERROR_LOW Gain Error mode to measure the gain error. See Table 65-7. Normal mode of operation. Offset Error mode to measure the offset error. See Table 65-7. See Section 65.6.14 “Automatic Error Correction” for details on ADC running mode.  2017 Microchip Technology Inc. DS60001476B-page 2441 SAMA5D2 SERIES 65.7.17 ADC Compare Window Register Name: ADC_CWR Address: 0xFC030044 Access: Read/Write 31 30 29 28 27 26 25 24 18 17 16 10 9 8 2 1 0 HIGHTHRES 23 22 21 20 19 HIGHTHRES 15 14 13 12 11 LOWTHRES 7 6 5 4 3 LOWTHRES This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. LOWTHRES: Low Threshold Low threshold associated to compare settings of ADC_EMR. HIGHTHRES: High Threshold High threshold associated to compare settings of ADC_EMR. DS60001476B-page 2442  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.18 ADC Channel Offset Register Name: ADC_COR Access: Read/Write 31 – 30 – 29 – 28 – 27 DIFF11 26 DIFF10 25 DIFF9 24 DIFF8 23 DIFF7 22 DIFF6 21 DIFF5 20 DIFF4 19 DIFF3 18 DIFF2 17 DIFF1 16 DIFF0 15 – 14 – 13 – 12 – 11 – 10 – 9 – 8 – 7 – 6 – 5 – 4 – 3 – 2 – 1 – 0 – This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. DIFFx: Differential Inputs for Channel x 0: Corresponding channel is set in Single-ended mode. 1: Corresponding channel is set in Differential mode.  2017 Microchip Technology Inc. DS60001476B-page 2443 SAMA5D2 SERIES 65.7.19 ADC Channel Data Register Name: ADC_CDRx [x=0..11] Address: 0xFC030050 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 14 13 12 11 10 9 8 2 1 0 DATA 7 6 5 4 3 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. ADC_CDRx is only loaded if the corresponding analog channel is enabled. DS60001476B-page 2444  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.20 ADC Analog Control Register Name: ADC_ACR Address: 0xFC030094 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 – 10 – 9 7 – 6 – 5 – 4 – 3 – 2 – 1 8 IBCTL 0 PENDETSENS This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. Note 1: By default, bits 12 and 13 are set to 1 and 0, respectively, and must not be modified. PENDETSENS: Pen Detection Sensitivity Modifies the pen detection input pull-up resistor value. Refer to section “Electrical Characteristics” for further details. IBCTL: ADC Bias Current Control Adapts performance versus power consumption. Refer to “Electrical Characteristics” for further details.  2017 Microchip Technology Inc. DS60001476B-page 2445 SAMA5D2 SERIES 65.7.21 ADC Touchscreen Mode Register Name: ADC_TSMR Address: 0xFC0300B0 Access: Read/Write 31 30 29 28 27 – 26 – 18 PENDBC 23 – 22 NOTSDMA 21 – 20 – 19 15 – 14 – 13 – 12 – 11 7 – 6 – 5 4 3 – TSAV 25 – 24 PENDET 17 16 9 8 TSSCTIM 10 TSFREQ 2 – 1 0 TSMODE This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. TSMODE: Touchscreen Mode Value Name Description 0 NONE No Touchscreen 1 4_WIRE_NO_PM 2 4_WIRE 4-wire Touchscreen with pressure measurement 3 5_WIRE 5-wire Touchscreen 4-wire Touchscreen without pressure measurement When TSMOD equals 01 or 10 (i.e., 4-wire mode), channels 0, 1, 2 and 3 must not be used for classic ADC conversions. When TSMOD equals 11 (i.e., 5-wire mode), channels 0, 1, 2, 3, and 4 must not be used. TSAV: Touchscreen Average Value Name Description 0 NO_FILTER No Filtering. Only one ADC conversion per measure 1 AVG2CONV Averages 2 ADC conversions 2 AVG4CONV Averages 4 ADC conversions 3 AVG8CONV Averages 8 ADC conversions TSFREQ: Touchscreen Frequency Defines the touchscreen frequency compared to the trigger frequency. TSFREQ must be greater or equal to TSAV. The touchscreen frequency is: Touchscreen Frequency = Trigger Frequency / 2TSFREQ TSSCTIM: Touchscreen Switches Closure Time Defines closure time of analog switches necessary to establish the measurement conditions. The closure time is: Switch Closure Time = (TSSCTIM × 4) ADCCLK periods. DS60001476B-page 2446  2017 Microchip Technology Inc. SAMA5D2 SERIES PENDET: Pen Contact Detection Enable 0: Pen contact detection disabled. 1: Pen contact detection enabled. When PENDET = 1, XPOS, YPOS, Z1, Z2 values of ADC_XPOSR, ADC_YPOSR, ADC_PRESSR are automatically cleared when PENS = 0 in ADC_ISR. NOTSDMA: No TouchScreen DMA 0: XPOS, YPOS, Z1, Z2 are transmitted in ADC_LCDR. 1: XPOS, YPOS, Z1, Z2 are never transmitted in ADC_LCDR, therefore the buffer does not contains touchscreen values. PENDBC: Pen Detect Debouncing Period Debouncing period = 2PENDBC ADCCLK periods.  2017 Microchip Technology Inc. DS60001476B-page 2447 SAMA5D2 SERIES 65.7.22 ADC Touchscreen X Position Register Name: ADC_XPOSR Address: 0xFC0300B4 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 26 25 24 17 16 9 8 1 0 XSCALE 19 18 11 10 XSCALE 15 – 14 – 13 – 12 – 7 6 5 4 XPOS 3 2 XPOS XPOS: X Position The position measured is stored here. If XPOS = 0 or XPOS = XSIZE, the pen is on the border. When pen detection is enabled (PENDET set to ‘1’ in ADC_TSMR), XPOS is tied to 0 while there is no detection of contact on the touchscreen (i.e., when PENS bit is cleared in ADC_ISR). XSCALE: Scale of XPOS Indicates the max value that XPOS can reach. This value should be close to 212. DS60001476B-page 2448  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.23 ADC Touchscreen Y Position Register Name: ADC_YPOSR Address: 0xFC0300B8 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 26 25 24 17 16 9 8 1 0 YSCALE 19 18 11 10 YSCALE 15 – 14 – 13 – 12 – 7 6 5 4 YPOS 3 2 YPOS YPOS: Y Position The position measured is stored here. If YPOS = 0 or YPOS = YSIZE, the pen is on the border. When pen detection is enabled (PENDET set to ‘1’ in ADC_TSMR), YPOS is tied to 0 while there is no detection of contact on the touchscreen (i.e., when PENS bit is cleared in ADC_ISR). YSCALE: Scale of YPOS Indicates the max value that YPOS can reach. This value should be close to 212.  2017 Microchip Technology Inc. DS60001476B-page 2449 SAMA5D2 SERIES 65.7.24 ADC Touchscreen Pressure Register Name: ADC_PRESSR Address: 0xFC0300BC Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 26 25 24 17 16 9 8 1 0 Z2 19 18 11 10 Z2 15 – 14 – 13 – 12 – 7 6 5 4 Z1 3 2 Z1 Z1: Data of Z1 Measurement Data Z1 necessary to calculate pen pressure. When pen detection is enabled (PENDET set to ‘1’ in ADC_TSMR), Z1 is tied to 0 while there is no detection of contact on the touchscreen (i.e., when PENS bit is cleared in ADC_ISR). Z2: Data of Z2 Measurement Data Z2 necessary to calculate pen pressure. When pen detection is enabled (PENDET set to ‘1’ in ADC_TSMR), Z2 is tied to 0 while there is no detection of contact on the touchscreen (i.e., when PENS bit is cleared in ADC_ISR). Note: These two values are unavailable if TSMODE is not set to 2 in ADC_TSMR. DS60001476B-page 2450  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.25 ADC Trigger Register Name: ADC_TRGR Address: 0xFC0300C0 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 TRGPER 23 22 21 20 TRGPER 15 14 13 12 11 10 9 8 – – – – – – – – 7 6 5 4 3 2 0 – – – – – 1 TRGMOD This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. TRGMOD: Trigger Mode Value Name Description 0 NO_TRIGGER 1 EXT_TRIG_RISE External trigger rising edge 2 EXT_TRIG_FALL External trigger falling edge 3 EXT_TRIG_ANY External trigger any edge 4 PEN_TRIG 5 PERIOD_TRIG ADC internal periodic trigger (see field TRGPER) 6 CONTINUOUS Continuous mode No trigger, only software trigger can start conversions Pen Detect Trigger (shall be selected only if PENDET is set and TSAMOD = Touchscreen only mode) TRGPER: Trigger Period Effective only if TRGMOD defines a periodic trigger. Defines the periodic trigger period, with the following equation: Trigger Period = (TRGPER + 1) / ADCCLK The minimum time between two consecutive trigger events must be strictly greater than the duration time of the longest conversion sequence depending on the configuration of registers ADC_MR, ADC_CHSR, ADC_SEQRx, ADC_TSMR. When TRGMOD is set to pen detect trigger (i.e., 100) and averaging is used (i.e., field TSAV ≠ 0 in ADC_TSMR) only one measure is performed. Thus, XRDY, YRDY, PRDY, DRDY will not rise on pen contact trigger. To achieve measurement, several triggers must be provided either by software or by setting the TRGMOD on continuous trigger (i.e., 110) until flags rise.  2017 Microchip Technology Inc. DS60001476B-page 2451 SAMA5D2 SERIES 65.7.26 ADC Correction Values Register Name: ADC_CVR Address: 0xFC0300D4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 GAINCORR 23 22 21 20 GAINCORR 15 14 13 12 11 OFFSETCORR 10 9 8 7 6 5 4 2 1 0 3 OFFSETCORR This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. OFFSETCORR: Offset Correction Offset correction to apply on converted data. The offset is signed (2’s complement), only bits 0 to 11 are relevant (other bits are ignored and read as 0). GAINCORR: Gain Correction Gain correction to apply on converted data. Only bits 0 to 13 are relevant (other bits are ignored and read as 0). DS60001476B-page 2452  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.27 ADC Channel Error Correction Register Name: ADC_CECR Address: 0xFC0300D8 Access: Read/Write 31 – 30 – 29 – 28 – 27 – 26 – 25 – 24 – 23 – 22 – 21 – 20 – 19 – 18 – 17 – 16 – 15 – 14 – 13 – 12 – 11 ECORR11 10 ECORR10 9 ECORR9 8 ECORR8 7 ECORR7 6 ECORR6 5 ECORR5 4 ECORR4 3 ECORR3 2 ECORR2 1 ECORR1 0 ECORR0 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. ECORRx: Error Correction Enable for channel x 0: Automatic error correction is disabled for channel x. 1: Automatic error correction is enabled for channel x.  2017 Microchip Technology Inc. DS60001476B-page 2453 SAMA5D2 SERIES 65.7.28 ADC Touchscreen Correction Values Register Name: ADC_TSCVR Address: 0xFC0300DC Access: Read/Write 31 30 29 28 27 TSGAINCORR 26 25 24 23 22 21 20 19 TSGAINCORR 18 17 16 15 14 13 12 11 TSOFFSETCORR 10 9 8 7 6 5 4 3 TSOFFSETCORR 2 1 0 This register can only be written if the WPEN bit is cleared in the ADC Write Protection Mode Register. TSOFFSETCORR: Touchscreen Offset Correction Offset correction to apply on converted data for the touchscreen channels. The offset is signed (2’s complement), only bits 0 to 11 are relevant (other bits are ignored and read as 0). TSGAINCORR: Touchscreen Gain Correction Gain correction to apply on converted data for the touchscreen channels. Only bits 0 to 13 are relevant (other bits are ignored and read as 0). DS60001476B-page 2454  2017 Microchip Technology Inc. SAMA5D2 SERIES 65.7.29 ADC Write Protection Mode Register Name: ADC_WPMR Address: 0xFC0300E4 Access: Read/Write 31 30 29 28 27 26 25 24 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPEN WPKEY 23 22 21 20 WPKEY 15 14 13 12 WPKEY 7 – 6 – 5 – 4 – WPEN: Write Protection Enable 0: Disables the write protection if WPKEY value corresponds to 0x414443 (“ADC” in ASCII). 1: Enables the write protection if WPKEY value corresponds to 0x414443 (“ADC” in ASCII). See Section 65.6.19 “Register Write Protection” for the list of write-protected registers. WPKEY: Write Protection Key Value Name 0x414443 PASSWD  2017 Microchip Technology Inc. Description Writing any other value in this field aborts the write operation of the WPEN bit. Always reads as 0 DS60001476B-page 2455 SAMA5D2 SERIES 65.7.30 ADC Write Protection Status Register Name: ADC_WPSR Address: 0xFC0300E8 Access: Read-only 31 – 30 – 29 – 28 – 23 22 21 20 27 – 26 – 25 – 24 – 19 18 17 16 11 10 9 8 3 – 2 – 1 – 0 WPVS WPVSRC 15 14 13 12 WPVSRC 7 – 6 – 5 – 4 – WPVS: Write Protection Violation Status 0: No write protection violation has occurred since the last read of ADC_WPSR. 1: A write protection violation has occurred since the last read of ADC_WPSR. If this violation is an unauthorized attempt to write a protected register, the associated violation is reported into field WPVSRC. WPVSRC: Write Protection Violation Source When WPVS = 1, WPVSRC indicates the register address offset at which a write access has been attempted. DS60001476B-page 2456  2017 Microchip Technology Inc. SAMA5D2 SERIES 66. Electrical Characteristics 66.1 Absolute Maximum Ratings Table 66-1: Absolute Maximum Ratings* Storage Temperature . . . . . . . . . . . . . . . . . . . . -60°C to + 150°C *NOTICE: Voltage on Input Pins with Respect to Ground . . . . . . . . . . . . . . . . . . . .-0.3V to +4.0V Maximum Operating Voltage VDDCORE, VDDPLLA, VDDUTMIC and VDDHSIC . . . . . . 1.5V VDDIODDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.0V 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. VDDBU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.0V VDDIOPx, VDDUTMII, VDDISC, VDDSDMMC, VDDOSC, VDDANA, VDDAUDIOPLL . . . . . . . . . . . . . . . . . 4.0V VDDFUSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.0V Total DC Output Current on all I/O lines . . . . . . . . . . . . . .350 mA 66.2 DC Characteristics The following characteristics are applicable to the operating temperature range TA = -40°C to +105°C, unless otherwise specified. Table 66-2: Symbol Recommended Thermal Operating Conditions Parameter Conditions Min Typ Max Unit -40 – +105 °C -40 – +125 °C LFBGA289 – 34.8 – TFBGA256 – 27.4 – TFBGA196 – 44.6 – LFBGA289 – 10.9 – TFBGA256 – 9.3 – TFBGA196 – 11.2 – At TA = 85°C, LFBGA289 – – 1149 mW At TA = 105°C, LFBGA289 – – 575 mW TA Operating Temperature – TJ Junction Temperature – RthJA Junction-to-ambient thermal resistance RthJC Junction-to-case thermal resistance PD Power Dissipation PD Power Dissipation PD Power Dissipation  2017 Microchip Technology Inc. °C/W °C/W At TA = 85°C, TFBGA256 – – 1460 mW At TA = 105°C, TFBGA256 – – 730 mW At TA = 85°C, TFBGA196 – – 897 mW At TA = 105°C, TFBGA196 – – 448 mW DS60001476B-page 2457 SAMA5D2 SERIES Table 66-3: Symbol VDDCORE VDDBU VDDANA VDDIOP0 VDDIOP1 VDDIOP2 DC Characteristics Parameter Conditions Min Typ Max Unit DC Supply Core – 1.1 1.2 1.32 V Allowable Voltage Ripple rms value 10 kHz to 20 MHz – – 15 mV – Slope – 1.3 DC Supply I/Os, Backup Must be established first 1.65 Allowable Voltage Ripple rms value 10 kHz to 10 MHz Slope VDDUTMIC VDDUTMII VDDHSIC VDDAUDIOPLL VDDFUSE VDDSDMMC V – 30 mV – 2.4 – – V/ms 1.65 DC Supply I/Os, Backup The ADC is not functional below 2.0V rms value 10 kHz to 20 MHz Slope – 3.6 V – – 20 mV 2.4 – – V/ms 1.65 – 3.6 V – – 20 mV 1.65 – 3.6 V – – 20 mV 1.65 – 3.6 V – – 20 mV 1.1 1.2 1.32 V rms value 10 kHz to 10 MHz – – 20 rms value > 10 MHz – – 20 1.1 1.2 1.32 V – – 20 mV 3.0 3.3 3.6 V – – 20 mV 1.1 1.2 1.3 V – – 20 mV DC Supply LCD I/Os Allowable Voltage Ripple rms value 10 kHz to 20 MHz DC Supply Peripheral I/Os Peripheral I/O Lines Allowable Voltage Ripple rms value 10 kHz to 20 MHz DC Supply Peripheral I/Os Peripheral I/O Lines Allowable Voltage Ripple rms value 10 kHz to 20 MHz PLL A and Main Oscillator Supply – Allowable Voltage Ripple V/ms – Allowable Voltage Ripple VDDPLLA – 3.6 DC Supply UDPHS and UHPHS UTMI+ Core – Allowable Voltage Ripple rms value 10 kHz to 10 MHz DC Supply UDPHS and UHPHS UTMI+ Interface – Allowable Voltage Ripple rms value 10 kHz to 10 MHz DC Supply HSIC Phy – Allowable Voltage Ripple rms value 10 kHz to 10 MHz mV DC Supply AUDIO PLL – 3.0 3.3 3.6 V Allowable Voltage Ripple rms value 10 kHz to 10 MHz – – 20 mV DC Supply Fuse Box For fuse programming only 2.25 2.5 2.75 V Allowable Voltage Ripple rms value 10 kHz to 10 MHz – – 20 mV 1.65 – 3.6 V – – 20 mV DC Supply Peripheral I/Os SDMMC I/Os Lines Allowable Voltage Ripple rms value 10 kHz to 10 MHz DS60001476B-page 2458  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-4: Symbol VDDISC VDDOSC DC Characteristics Parameter Conditions Min Typ Max DC Supply Peripheral I/Os ISC I/Os Lines Allowable Voltage Ripple rms value 10 kHz to 10 MHz 1.65 – 3.6 V – – 20 mV 1.65 – 3.6 V – – 15 mV 1.7 1.14 1.283 1.425 1.8 1.2 1.35 1.5 1.95 1.30 1.45 1.575 V VDDIO in 3.3V range -0.3 – 0.8 VDDIO in 1.8V range -0.3 – 0.3 x VDDIO VDDIO in 3.3V range 2 – VDDIO +0.3 VDDIO in 1.8V range 0.7 x VDDIO – VDDIO +0.3 DC Supply Oscillator – Unit Allowable Voltage Ripple rms value 10 kHz to 10 MHz VDDIODDR DC Supply SDRAM I/Os - LPDDR1-DDR2 Interface I/O lines - LPDDR2-LPDDR3 Interface I/O lines - DDR3L Interface I/O lines - DDR3 Interface I/O lines VIL Low-level Input Voltage VIH High-level Input Voltage VOL Low-level Output Voltage IO MAX – – 0.41 V VOH High-level Output Voltage IO MAX VDDIO - 0.4 – – V All PIO lines, VDDIOx in 3.3V range 0.34 – – Vhys Schmitt Trigger Hysteresis All PIO lines, VDDIOx in 1.8V range 0.2 – – IOL IOH IOL IOH (2) (2) IOlL(or ISINK) (VOL = 0.4V) V V All GPIO_x, 1.8V: Low -1 – – All GPIO_x, 1.8V: Medium -10 – – All GPIO_x, 1.8V: High -18 – – All GPIO_x, 1.8V: Low – – 1 – – 10 All GPIO_x, 1.8V: High – – 18 All GPIO_x, 3.3V: Low -2 – – All GPIO_x, 3.3V: Medium -20 – – All GPIO_x, 3.3V: High -32 – – All GPIO_x, 3.3V: Low – – 2 IOH (or ISOURCE) (VOH = VDDIO - 0.4V) All GPIO_x, 1.8V: Medium IOlL(or ISINK) (VOL = 0.4V) V IOH (or ISOURCE) (VOH = VDDIO - 0.4V) All GPIO_x, 3.3V: Medium – – 20 All GPIO_x, 3.3V: High – – 32 mA mA mA mA IIL Low-level Input Current LCDPCK, ISC_MCK, GPIO, QSPI_SCK -1 – 1 µA IIH High-level Input Current LCDPCK, ISC_MCK, GPIO, QSPI_SCK -1 – 1 µA IIL Low-level Input Current GPIO_AD -1 – 1 µA IIH High-level Input Current GPIO_AD -1 – 1 µA  2017 Microchip Technology Inc. DS60001476B-page 2459 SAMA5D2 SERIES Table 66-5: Symbol RPULLUP RPULLDOWN DC Characteristics Parameter Typ Max GPIO_CLK, GPIO_IO, GPIO: 1.8V 80 143 310 GPIO_CLK, GPIO_IO, GPIO: 3.3V 40 66 130 GPIO_CLK, GPIO_IO, GPIO: 1.8V 80 161 430 Unit kΩ Pull-down Resistor Pull-up Resistor RPULLDOWN Pull-down Resistor Notes: Min Pull-up Resistor RPULLUP RSERIAL Conditions kΩ Serial Resistor GPIO_CLK, GPIO_IO, GPIO: 3.3V 40 77 160 GPIO_AD: 1.8V 280 380 480 GPIO_AD: 3.3V 280 380 480 GPIO_AD: 1.8V 280 380 480 GPIO_AD: 3.3V 280 380 480 GPIO – 30 – Ω GPIO_IO – 13 – Ω GPIO_CLK, GPIO_AD – 0 – Ω kΩ kΩ 1. VDDIO voltage must be equal to VDDIN voltage. 2. Current injection may lead to performance degradation or functional failures. Table 66-6: I/O Switching Frequency GPIO_IO GPIO_CLK GPIO_AD GPIO Table 66-7: CLoad = 30pF 1.8V 2.5V 3.3V Low 8 12 15 Medium 60 80 90 High 80 110 110 Low 10 15 18 Medium 90 100 120 High – – – Low 10 15 18 Medium 90 100 120 High – – – Low 7 10 12 Medium 40 50 60 High 50 60 70 Unit MHz QSPI I/O Switching Frequency GPIO Type GPIO_QSPI VDD Drive GPIO Type Description Maximum output frequency Output duty cycle DS60001476B-page 2460 Name Conditions Min Max Unit fmax – Load = 30 pF – 133 MHz Load = 30 pF 45 55 %  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.3 Power Consumption This section provides information about the current consumption on different power supply rails of the device. It gives current consumption in: • Active mode when running a CoreMark and in predefined use cases • Low-power modes: Backup mode, Idle mode and Ultra Low-power mode • By peripheral with representative activity 66.4 Active Mode Active mode is the normal running mode with the ARM core clock running off a PLL. The power management controller is used to adapt the frequency and to disable the peripheral clocks. 66.4.1 Active Mode Power Consumption Versus Modes The power consumption values are measured under the following operating conditions: • • • • • • • • Parts are from typical process VDDIOPx = 3.3V VDDSDMMC0 and VDDSDMMC1 = 1.8V to 3.3V (high frequency) VDDCORE = 1.2V +/-2% VDDBU = 1.6V to 3.6V TA = as specified in Table 66-8 and Table 66-10 There is no consumption on the device’s I/Os. All peripheral clocks are disabled. Figure 66-1: Measurement Schematics VDDBU AMP1 VDDCORE AMP2  2017 Microchip Technology Inc. DS60001476B-page 2461 SAMA5D2 SERIES Table 66-8: Typical Peripheral Power Consumption by Peripheral in Active Mode Peripheral Clock Conditions (T A = 25°C) Consumption on VDDCORE MCK/2 – XDMAC0 MCK – XDMAC1 MCK – ICM MCK/2 3.52 AES MCK 8.79 AESB MCK 7.49 TDES MCK/2 0.85 MCK 3.88 GMAC SHA MCK 45.21 HSMC MCK/2 20.12 PIOA MCK/2 11.39 MPDDRC FLEXCOM0 FLEX0_USART FLEX0_SPI Consumption (typ) See Note 1. 12 *MCK + 1840*DR (Data rate in Mbits/s) Unit µA See Note 2. 17.6 * MCK + 4.92 * DR (MCK in MHz, Data rate in Mbytes/s) – – µA/MHz See Note 3. 67 * MCK + 3.11 * DR + 1609 (MCK in MHz, Data rate in Mbytes/s) µA – – µA/MHz 5.21 MCK/2 FLEX0_TWI 7.39 Peripheral Clock Enabled 3.88 FLEXCOM1 MCK/2 FLEXCOM2 MCK/2 See FLEXCOM0 FLEXCOM3 MCK/2 See FLEXCOM0 FLEXCOM4 MCK/2 See FLEXCOM0 UART0 MCK/2 1.09 UART1 MCK/2 0.97 UART2 MCK/2 1.21 UART3 MCK/2 0.85 UART4 MCK/2 0.85 TWIHS0 MCK/2 3.27 TWIHS1 MCK/2 3.39 SDMMC0 MCK 8.61 SDMMC1 MCK 8.61 SPI0 MCK/2 4.61 SPI1 MCK/2 4.48 TC0 MCK/2 3.03 TC1 MCK/2 4 PWM MCK/2 7.03 ADC MCK/2 2.3 DS60001476B-page 2462 Conditions See FLEXCOM0  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-9: Typical Peripheral Power Consumption by Peripheral in Active Mode Peripheral UHPHS Clock Conditions (T A = 25°C) Consumption on VDDCORE MCK/2 Conditions Consumption (typ) Unit See Note 4. 12 *MCK + 490*DR (MCK in MHz, Data rate in Mbytes/s) See Note 5. 10 *MCK + 206*DR (MCK in MHz, Data rate in Mbytes/s) – – See Note 6. 9.8 *MCK + 32 *Pix_CLK + 15.7*DR_Baselayer +30.1*DR_Overlayer (MCK & Pixelclock in MHz, Data rate in Mbytes/s); µA – UDPHS MCK/2 SSC0 MCK/2 1.58 SSC1 MCK/2 1.58 LCDC MCK Peripheral Clock Enabled ISC – MCK TRNG MCK/2 760 PDMIC MCK/2 8.24 QSPI0 MCK 1.94 QSPI1 MCK 1.94 I2SC0 MCK/2 0.61 I2SC1 MCK/2 0.61 CAN0 MCK/2 9.7 CAN1 MCK/2 7.27 µA/MHz µA See Note 7. 10.9*MCK + 22.4*ISPCK + 12.38*DR_sensor (MCK & ISPCK in MHz, Data rate in Mbytes/s) – – – – µA/MHz Notes: 1. In Linux OS, use the ‘iperf’ command to perform bidirectional data transfers. Measure GMAC consumption at different transfer speeds. 2. XDMAC is initialized and one channel performs a memory-to-memory transfer. During test, the data rate is adjusted by changing the DMA setting and the burst size. 3. DDR3 devices are initialized (fully functional). XDMAC performs a memory-to-memory transfer inside the DDR area. Total consumption of MPDDRC and XDMAC is measured. MPDDRC consumption is calculated by discounting XDMAC consumption. 4. In Linux OS, measure UHPHS consumption at different transfer speeds. 5. In Linux OS, build a mass storage using UDPHS. Measure UDPHS consumption at different transfer speeds. 6. The LCD timing engine and each display layer are switched on in sequence. The static image (using random data) is displayed under various resolutions. The 24-bpp RGB888 color space is set for all layers. Auxiliary functions such as rotation, scaling, color space conversion, color look-up table, and chroma upsampling are disabled. 7. ISC performs image sensor preview. In order to maximize performance, each Peripheral Clock has been timed to H32MX clock frequency. The peripheral frequency can be reduced with the help of a divider in PMC_PCR.  2017 Microchip Technology Inc. DS60001476B-page 2463 SAMA5D2 SERIES Table 66-10: Power Consumption in Active Mode: AMP2 Consumption Dhrystone CoreMark (mA) (mA) Conditions T A = 25°C PLL clock is 1000 MHz, ARM Core clock is 500 MHz, MCK is 166 MHz. – Caches L1 and L2 enabled – Code running off of internal SRAM – Code speed optimization – Run Dhrystone / CoreMark benchmark – Peripheral clock disabled 66.5 MRL C MRL B 114.4 108.8 MRL A 237.2 233.7 Low-power Modes The various low-power modes enable balancing device power consumption and wakeup time. The modes are described below, in the order of lowest to highest power consumption. 66.5.1 Backup Mode The Backup mode allows to achieve the lowest power consumption in the system with limited functionality. In this mode, only the backup area is powered, maintaining the RTC, the backup registers, the backup SRAM and the security module running. This mode is entered by shutting down all the power rails except the VDDBU (refer to Section 24. “Shutdown Controller (SHDWC)”). To exit Backup mode, the SHDN pin (connected to the enable of the external Power Management IC) must be driven high by an internal event (RTC) or by one of the external events listed below: • WKUP0 to WKUP9 pins (level transition, configurable debouncing) • Character received on a serial com receiver (RXLP) • Analog comparison The Backup Mode functionality has been extended with the possibility to keep the DDR memory in self-refresh state. 66.5.2 Backup Mode with DDR in Self-refresh The Backup mode with DDR in self-refresh is used to keep the DDR contents when the system is powered off. This mode is achieved by maintaining the backup area and the VDDIODDR powered. The sequence below must be performed to enter the Backup Self-refresh mode: • Software saves all the context information to resume (application-dependent). • Put the DDR in Self-refresh mode and wait until the self-refresh status is OK (refer to Section 36. “Multiport DDR-SDRAM Controller (MPDDRC)”). • Set SFRBU_DDRBUMCR.BUMEN (Section 20.3.3 “SFRBU DDR BU Mode Control Register”) • Enter the Backup mode as described above. The method to exit this mode is the same as described for the Backup mode. Once the system is restarted, the software checks the state of the SFRBU_DDRBUMCR.BUMEN bit and reinitializes the DDR controller. The DDR memory exits Self-refresh mode when a memory access in the DDR memory space is performed. 66.5.3 Ultra Low-power (ULP) Mode The purpose of the Ultra Low-power mode is to achieve the lowest power consumption with the system in Retention mode and able to resume on wake up events (any interrupt or hardware event). This mode is a combination of the Wait for Interrupt mode of the ARM core and the system clocks frequency reduced or shut-off. To obtain the best results, care must be taken that the I/Os (pull-up/pull-down, etc.), USB transceivers, etc., are set to the appropriate state. The Ultra Low-power mode features two submodes: • ULP0 mode • ULP1 mode DS60001476B-page 2464  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.5.3.1 ULP0 Mode The ULP0 mode maintains a very low frequency clock to wake up on any interrupt. The selection of the clock depends on the current consumption target versus wake up time. The higher the frequency, the higher the power consumption. The sequence to enter ULP0 mode is detailed below. The code used to enter this mode must be executed out of the internal SRAM. 1. 2. 3. 4. 5. 6. 7. Set the DDR to Self-Refresh mode. Set the interrupts to wake up the system. Disable all peripheral clocks. Set the I/Os to an appropriate state and disable the USB transceivers (refer to Section 19. “Special Function Registers (SFR)”). Switch the system clock to the selected clock (RC12MHZ, 32 KHz Slow Clock.) according to the power consumption and wakeup time awaited (see Table 66-13). Disable the PLLs and all unused clocks (main oscillator, 12 MHz RC oscillator or 32 KHz oscillator). Enter the Wait for Interrupt mode and disable the PCK clock in the PMC_SCDR. The wake up from ULP0 mode is triggered by any enabled interrupt. When resuming, the software reconfigures the system (oscillator, PLL, etc.) in the same state as before WFI. 66.5.3.2 ULP1 Mode Unlike the ULP0 mode, all the clocks are off in the ULP1 mode, but the number of wake up sources is limited to the list below: • • • • • • • • • WKUP0 pin (level transition, configurable debouncing) WKUP1 Secumod wakeup signal WKUP2 pin to WKUP9 pin (shared with PIOBU0 to PIOBU7) RTC alarm USB Resume from Suspend mode SDMMC card detect RXLP event ACC event Any SleepWalking event coming from TWI, FLEXCOMx, SPI, ADC The sequence to enter the ULP1 mode is detailed below. The code used to enter this mode must be executed out of the internal SRAM. 1. 2. 3. 4. 5. 6. 7. 8. Set the DDR to Self-Refresh mode. Set the events to enable a system wakeup. Disable all peripheral clocks. Set the I/Os to an appropriate state and disable the USB transceivers (refer to Section 19. “Special Function Registers (SFR)”). Switch the system clock to the 12 MHz RC oscillator. Disable the PLLs and the main oscillator. Enter the ULP1 mode by either: a) setting the WAITMODE bit in CKGR_MOR, or b) setting the LPM bit in PMC_FSMR and executing the processor WaitForEvent (WFE) instruction. After setting the WAITMODE bit or using the WFE instruction, wait for the PMC_SR.MCKRDY bit to be set. 66.5.4 Idle Mode The purpose of Idle mode is to optimize power consumption of the device versus response time. In this mode, only the core clock is stopped. The peripheral clocks, including the DDR controller clock, can be enabled. The current consumption in this mode is applicationdependent and can be reduced by enabling Dynamic Clock Gating (L2CC_POWCR.DCKGATEN = 1). This mode is entered via the Wait for Interrupt (WFI) instruction and PCK disabling. The processor can be awakened from an interrupt. The system resumes where it was before entering WFI mode. 66.5.5 Low-power Mode Summary Table The modes detailed above are the main low-power modes. Each part can be set to on or off separately and wakeup sources can be configured individually. Table 66-11 shows a summary of the low-power mode configurations.  2017 Microchip Technology Inc. DS60001476B-page 2465 SAMA5D2 SERIES Table 66-11: Low-power Mode Configuration Summary Low-power Mode Backup Submode – Ultra-low-power Self-refresh ULP0 64 kHz RC Oscillator, 32 kHz Oscillator, RTC, Backup Memory and Registers, POR ULP1 ON 12 MHz RC Oscillator OFF VDDCORE Regulator ON OFF ON Core OFF (not powered) Powered (not clocked) Memory, Peripherals OFF (not powered) Mode Entry Potential Wakeup Sources DDR in Self-refresh, CKGR_MOR.WAITMODE=1 DDR in Self-refresh, WFI WKUP0 pin, any PIOBU configured as WKUP pin, RTC alarm, any level above comparator source or character received Backup mode sources Any interrupt Wakeup pins, WOL Any interrupt Clocked back at 512 Hz Clocked back at 12 MHz Clocked back at full speed Reset Wakeup Time(1) Powered (clocked) DDR in Self-refresh, Frequency reduced in PMC, WFI PIO State While in Lowpower Mode Consumption Powered (not clocked) DDR in Self-refresh, Shutdown Controller Reset (2) Powered (512 Hz) Shutdown Controller, FLEXCOM SleepWalking Core at Wakeup PIO State at Wakeup Idle Previous state saved Inputs with pullups IVDDBU= 4.5 μA typ(3) at 25°C/3.0V Startup time Unchanged IVDDBU= 4.5 μA typ(3) at 25°C/3.0V 0.21 mA at 25°C/ 1.1V 0.17 mA at 25°C/ 1.1V IVDDIODDR = 40 μA 0.27 mA at 25°C/ 1.2V 0.27 mA at 25°C/ 1.2V Startup time 300 ms 15 µs 28 mA at 25°C/ 1.2V(4) 800 ns at 498 MHz Note 1: When considering wakeup time, the time required to start the PLL is not taken into account. Once started, the device works with the main oscillator. The user has to add the PLL startup time if it is needed in the system. The wakeup time is defined as the time taken for wakeup until the first instruction is fetched. 2: The external loads on PIOs are not taken into account in the calculation. 3: Total current consumption. 4: Dynamic Clock Gating enabled (L2CC_POWCR.DCKGATEN = 1) DS60001476B-page 2466  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.5.6 Low-power Consumption Versus Modes The low-power consumption values are measured under the following operating conditions: • • • • • • • • Parts are from typical process VDDIOPx = 3.3V VDDSDMMC0 and VDDSDMMC1 = 1.8V to 3.3V (high frequency) VDDCORE = 1.2V +/-2% VDDBU = 1.6V to 3.6V TA = as specified in Table 66-12, Table 66-13, Table 66-14 There is no consumption on the device’s I/Os. All peripheral clocks are disabled. Figure 66-2: Measurement Schematics VDDBU AMP1 VDDCORE AMP2 In order to maximize performances, each Peripheral Clock has been timed to H32MX clock frequency. The peripheral frequency can be reduced with the help of a divider in PMC_PCR. Table 66-12: Typical Power Consumption in Idle Mode: AMP2 Conditions PLL clock is 1000 MHz, ARM Core clock is 500 MHz, MCK is 166 MHz. – Core clock is stopped – Peripheral clocks, including the DDR Controller clock, can be enabled – Mode is entered via Wait for Interrupt (WFI) instruction and PCK disabling – Measure IDDCORE + IDDBU – Peripheral clock disabled Table 66-13: Consumption T A 25°C T A 70°C 28.2 29.6 T A 85°C T A 105°C 30.8 33.4 Unit mA VDDCORE Power Consumption in Ultra Low-power Mode: AMP2 Mode Conditions Consumption (mA) T A 25°C T A 70°C Wakeup T A 85°C T A 105°C Time µs ULP1 Fast Wakeup ARM Core clock is disabled. MCK is 0. 0.3 1.4 2.4 4.6 15 ULP0 12 MHz ARM Core clock is disabled. MCK is 12 MHz. 3.2 4.2 5.3 7.7 13 ULP0 750 kHz ARM Core clock is disabled. MCK is 750 kHz. 1.6 2.6 3.7 6.1 205 ULP0 187 kHz ARM Core clock is disabled. MCK is 187.5 kHz. 1.5 2.5 3.6 6.0 820 ULP0 32 kHz ARM Core clock is disabled. MCK is 32 kHz. 0.3 1.5 2.6 5.0 4690  2017 Microchip Technology Inc. DS60001476B-page 2467 SAMA5D2 SERIES Table 66-14: Typical Power Consumption for Backup Mode VDDBU (V) Consumption (μA) Conditions T A = 25°C T A = 70°C T A = 85°C T A = 105°C 1.6 4.2 12.1 19.3 36.8 1.7 4.2 12.1 19.3 36.9 1.8 4.3 12.1 19.4 36.9 1.9 4.3 12.1 19.4 36.9 2 4.3 12.1 19.4 37 2.1 4.3 12.2 19.4 37 2.2 4.3 12.2 19.5 37 2.3 4.4 12.2 19.5 37 2.4 4.4 12.2 19.5 37 4.4 12.3 19.5 37.1 4.4 12.3 19.6 37.1 2.7 4.4 12.3 19.6 37.1 2.8 4.4 12.3 19.6 37.2 2.9 4.5 12.4 19.6 37.2 3 4.5 12.4 19.7 37.3 3.1 4.5 12.5 19.8 37.7 3.2 4.6 12.8 20.3 38.3 3.3 4.9 13.4 20.9 38.9 3.4 5.5 14.1 21.6 39.7 3.5 6.2 14.9 22.4 40.5 3.6 7 15.7 23.3 41.4 2.5 VDDB U Only 2.6 66.6 Unit µA Clock Characteristics 66.6.1 Processor Clock Characteristics Table 66-15: Symbol 1/(tCPPCK) Processor Clock Waveform Parameters Parameter Processor Clock Frequency Conditions Min Max VDDCORE[1.1V, 1.32V], TA = [-40°C, +85°C] 250(1) 400 VDDCORE[1.2V, 1.32V], TA = [-40°C, +85°C] 250(1) 500 Unit MHz Note 1: Limitation for DDR2 (125 MHz) usage only. There are no limitations to DDR3, DDR3L, LPDDR1, LPDDR2 and LPDDR3. DS60001476B-page 2468  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.6.2 Master Clock Characteristics The master clock is the maximum clock at which the system is able to run. It is given by the smallest value of the internal bus clock and EBI clock. Table 66-16: Symbol Master Clock Waveform Parameters Parameter Conditions VDDCORE[1.1V, 1.32V], TA = [-40°C, +85°C] Min Max 125(1) 133 125(1) 166(2) Unit VDDCORE[1.2V, 1.32V], in DDR2 or LPDDR1 mode, VDDIODDR[1.8V, 1.95V], TA = [-40°C, +85°C] 1/(tCPMCK) Master Clock Frequency in LPDDR2 or LPDDR3 mode, VDDIODDR[1.2V, 1.30V], TA = [-40°C, +85°C] in DDR3 mode, VDDIODDR[1.5V, 1.575V], TA = [-40°C, +85°C] MHz in DDR3L mode, VDDIODDR[1.35V, 1.45V], TA = [-40°C, +85°C] Security disabled Note 1: Limitation for DDR2 usage only. There are no limitations to DDR3, DDR3L, LPDDR1, LPDDR2 and LPDDR3. 2: The JEDEC standard specifies a maximum clock frequency of 125 MHz for DDR3 and DDR3L in DLL Off mode. However, check with memory suppliers for higher frequencies.  2017 Microchip Technology Inc. DS60001476B-page 2469 SAMA5D2 SERIES 66.7 Oscillator Characteristics 66.7.1 Main Oscillator Characteristics Table 66-17: Symbol 8 to 24 MHz Crystal Oscillator Characteristics Parameter fOSC Operating Frequency – Duty Cycle Conditions Min FREQ(2) = 00, 11 FREQ = 01 FREQ = 10 – Typ Max Unit 8 12 16 – 12 16 24 MHz 40 50 60 % – – 18.5 10.5 6 ms tSTART Startup Time FREQ(2) = 00, 11 FREQ = 01 FREQ = 10 IDDON Current Consumption (on VDDIO) @ 12 MHz @ 24 MHz – 1.2 1.7 3.5 4 mA Standby Current Internal Parasitic Capacitance(1) – – 0.02 0.1 µA 1.4 1.6 1.8 pF 150 300 400 µW IDD_STDBY CPARA PON Notes: From XIN to XOUT FREQ = 00 FREQ = 01, 11 – – FREQ = 10 1. The external capacitors value can be determined by using the following formula: CLEXT = (2 x CCRYSTAL ) - CBOARD - (CPARA x 2) where: CLEXT : external capacitor value which must be soldered from XIN to GND and XOUT to GND Drive level CCRYSTAL : crystal targeted load CBOARD: external board parasitic capacitance (from XIN to GND or XOUT to GND) CPARA: internal parasitic capacitance 2. The SFR_UTMICKTRIM.FREQ field defines the input frequency for the UTMI and the main oscillator. It is important to select the correct FREQ value because this has a direct influence on USB frequency. Figure 66-3: Main Oscillator Schematics CPARA XIN XOUT GNDOSC CCRYSTAL CLEXT DS60001476B-page 2470 CLEXT  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.7.1.1 Recommended Crystal Characteristics The following characteristics are applicable to the operating temperature range TA = -40°C to 85°C and to the worst case of power supply, unless otherwise specified. Table 66-18: Symbol Recommended Crystal Characteristics Parameter ESR Equivalent Series Resistance CM Motional Capacitance CS Shunt Capacitance Allowed crystal capacitive load CCRYSTAL 66.7.1.2 Conditions Min Typ Max FREQ = 00, 11 – – 100 FREQ = 10, 01 – – 80 FREQ = 00 5 – 9 FREQ = 01, 10, 11 1.3 – 3.2 FREQ = 00, 01, 10 – – 3 FREQ = 11 – – 1.3 12.5 8 – 18 12.5 pF Min Typ Max Unit From crystal specification FREQ = 00, 01, 11 FREQ = 10 Unit Ω fF pF XIN Clock Characteristics Table 66-19: XIN Clock Electrical Characteristics Symbol Parameter Conditions 1/(tCPXIN) XIN Clock Frequency – – – 50 MHz tCPXIN XIN Clock Period – – XIN Clock High Half-period – tCLXIN XIN Clock Low Half-period – – 0.6 x tCPXIN 0.6 x tCPXIN ns tCHXIN 20 0.4 x tCPXIN 0.4 x tCPXIN CIN XIN Input Capacitance – – – 25 pF RIN XIN Pulldown Resistor – – – 500 kΩ VIN Note: – VDDOSC V XIN Voltage – VDDOSC These characteristics apply only when the Main Oscillator is in Bypass mode (i.e., when MOSCEN = 0 and OSCBYPASS = 1 in CKGR_MOR). Refer to “PMC Clock Generator Main Oscillator Register” in the section "Power Management Controller (PMC)". 66.7.2 Conditions RC Oscillator Frequency @ 25°C Startup Time Duty IDDON tSTART ns 12 MHz RC Oscillator Characteristics Parameter fOSC – ns 12 MHz RC Oscillator Characteristics Table 66-20: Symbol – Min Typ Max Unit 11.63 – 12.12 MHz – – – 15 µs Duty Cycle – 45 50 55 % Current Consumption After startup time – 160 350 µA  2017 Microchip Technology Inc. DS60001476B-page 2471 SAMA5D2 SERIES 66.7.3 32.768 kHz Crystal Oscillator Characteristics Table 66-21: Symbol 32.768 kHz Crystal Oscillator Characteristics Parameter Conditions Min Typ fOSC Operating Frequency Normal mode with crystal – tSTART Startup Time Cm > 3fF – CCRYSTAL32 = 12.5 pF ESR < 50k ohm IDDON CCRYSTAL32 = 6 pF Current Consumption CCRYSTAL32 = 12.5 pF ESR < 100k ohm CPARA32 Figure 66-4: Internal Parasitic Capacitance – CCRYSTAL32 = 6 pF Between XIN32 and XOUT32 Max Unit 32.768 – kHz – 1200 ms 440 900 600 900 800 1200 nA 700 1200 1.4 1.6 1.8 pF Min Typ Max Unit kΩ 32 kHz Oscillator Schematics CPARA32 XIN32 XOUT32 GNDBU CCRYSTAL32 CLEXT32 Table 66-22: CLEXT32 Recommended 32.768 kHz Crystal Characteristics Symbol Parameter Conditions ESR Equivalent Series Resistor Crystal at 32.768 kHz – – 100 – Duty Cycle – 40 50 60 % Cm Motional Capacitance Crystal at 32.768 kHz 3 – 8 fF CSHUNT Shunt Capacitance Crystal at 32.768 kHz 0.6 – 2 pF CCRYSTAL32 Allowed Crystal Capacitance (1) Load From crystal specification 6 – 12.5 pF – Drive Level – – 0.2 1. The external capacitors value can be determined by using the following formula: CLEXT32 = (2 x CCRYSTAL32 ) - CBOARD - (CPARA32 x 2) where: CLEXT32 is the external capacitor value which must be soldered from XIN32 to GND and XOUT32 to GND µW PON Note: CCRYSTAL32 is the crystal targeted load CBOARD is the external board parasitic capacitance (from XIN to GND or XOUT to GND) CPARA32 is the internal parasitic capacitance DS60001476B-page 2472  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.7.4 64 kHz RC Oscillator Characteristics Table 66-23: 64 kHz RC Oscillator Characteristics Symbol Parameter Conditions fOSC RC Oscillator Frequency – 40 tSTART Startup Time – 11 IDDON Current Consumption After startup time – 66.8 Min Typ Max Unit 90 kHz 17 30 µs 93 140 nA PLL Characteristics Table 66-24: PLLA Characteristics Symbol Parameter Conditions fIN Input Frequency fOUT Output Frequency IPLL Current Consumption tSTART Startup Time Table 66-25: Min Typ Max Unit – 8 – 24 MHz – 600 – 1200 MHz Active mode – – 14.5 mA Standby mode – – 2 µA – – – 60 µs Typ Max Unit – 24 MHz UTMI PLL Characteristics Symbol Parameter Conditions fIN Input Frequency – Min 12 480 fOUT Output Frequency – IVDDUT MII Current Consumption In Active mode, on VDDUTMII, @480 MHz – 6.3 7.0 mA tST ART Startup Time – – – 60 µs Table 66-26: MHz Audio PLL Characteristics Symbol Parameter Conditions Min Typ Max Unit fIN fAUDIOPINCLK Input Frequency AUDIOCORECLK frequency range AUDIOPINCLK frequency range – 12 – 24 MHz – 620 – 700 MHz – 8 12.288 48 MHz fAUDIOPLLCLK AUDIOPLLCLK frequency range – – – 150 MHz IPLL Current Consumption 6 – 20 mA tSTART Startup Time – – 100 µs tSET Settling Time – – 100 µs fAUDIOCORECLK (1) On VDDAUDIOPLL From OFF to stable AUDIOCORECLK frequency When changing FRACR or NR in PMC_AUDIO_PLL0 or PMC_AUDIO_PLL1 Note: 1. Loop filter is set as recommended in fields BIAS_FILTER and DCO_FILTER of PMC_AUDIO_PLL0.  2017 Microchip Technology Inc. DS60001476B-page 2473 SAMA5D2 SERIES 66.9 USB HS Characteristics 66.9.1 Electrical Characteristics The device conforms to all voltage, power, and timing characteristics and specifications set forth in the USB 2.0 Specification. Refer to the USB 2.0 Specification for more information. 66.9.2 Dynamic Power Consumption Table 66-27: USB Transceiver Dynamic Power Consumption Symbol Parameter Conditions IBIAS Bias Generator Current Consumption IVDDUTMII IVDDUTMIC Note: Min Typ Max Unit – – 0.7 0.8 mA HS Transceiver Current Consumption HS transmission – 47 60 mA HS Transceiver Current Consumption HS reception – 18 27 mA LS / FS Transceiver Current Consumption FS transmission 0m cable(1) – 4 6 mA LS / FS Transceiver Current Consumption FS transmission 5m cable(1) – 26 30 mA LS / FS Transceiver Current Consumption (1) FS reception – 3 4.5 mA Core – – 5.5 9 mA 1. Including 1 mA due to pull-up/pull-down current consumption. 66.10 PTC Characteristics Table 66-28: PTC Characteristics Symbol Parameter Conditions CC Compensation Capacitance Error on Serial filtering Resistance PTC Current Consumption ERS IPTCT Min Typ Max Unit Type Programmable max code 0x3FFF 30 – – pF - 20, 50, 100 kOhm -20 – 20 % - – – 500 µA - – 66.11 ADC Characteristics Electrical data are in accordance with an operating temperature range from -40°C to +85°C unless otherwise specified. ADVREF is the positive reference of the ADC. 66.11.1 66.11.1.1 ADC Power Supply Power Supply Characteristics Table 66-29: Symbol Power Supply Characteristics Parameter Conditions Min Typ Max Unit - 2 0.4 2.2 4 0.6 3.0 µA mA mA (1) IVDDIN Sleep mode Analog Current Consumption Fast Wakeup mode Normal mode, single sampling 1 2 Sleep mode(1) 80 100 Normal mode Note: 1. In Sleep mode, the ADC core, the Sample and Hold and the internal reference operational amplifier are off. IVDDCORE Digital Current Consumption DS60001476B-page 2474 µA µA  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.11.2 External Reference Voltage VADVREF is an external reference voltage applied on the pin ADVREF. The quality of the reference voltage VADVREF is critical to the performance of the ADC. A DC variation of the reference voltage VADVREF is converted to a gain error by the ADC. The noise generated by VADVREF is converted by the ADC to count noise. Table 66-30: Symbol ADVREF Electrical Characteristics Parameter Conditions Min Typ Max Unit Voltage Range Full operational 2 – VDDANA V RMS Noise Bandwidth 10 kHz to 1 MHz – – 100 µV RADVREF Input DC Impedance ADC reference resistance bridge(1) 6 8 10 kΩ IADVREF Current VADVREF = 3.3V - - 460 µA VADVREF Note: 66.11.3 1. When the ADC is off, the ADVREF impedance has a minimum of 1 MΩ. ADC Timings Table 66-31: ADC Timing Characteristics Symbol Parameter Conditions Min Typ Max Unit fADC_Clock Clock Frequency – 0.2 – 20 MHz fS Sampling Frequency – – – 1 MHz (1) Sleep mode to Normal mode tSTART Note: ADC Startup Time Fast Wakeup mode to Normal mode 4 – – 2 µs 1. tADC_Clock = 1/fADC_Clock ADC conversion time = 21 tADC_Clock. The Tracking time of the ADC has a minimal value of tTRACKTIM = 15 tADC_Clock. 66.11.4 ADC Transfer Function The DATA code in ADC_CDR is up to 12-bit positive integer or two’s complement (signed integer). 66.11.4.1 Differential Mode (12-bit mode) A differential input voltage VIN = VINP - VINN can be applied between two selected differential pins, e.g. ADC0_AD0 and ADC0_AD1. The ideal code Ci is calculated by using the following formula and rounding the result to the nearest positive integer. 2047 C i = ------------------------- × V IN V ADVREF For the other resolution defined by RES, the code Ci is extended to the corresponding resolution.  2017 Microchip Technology Inc. DS60001476B-page 2475 SAMA5D2 SERIES Table 66-32 is a computation example for the above formula, where VADVREF = 3V. Table 66-32: 66.11.4.2 Input Voltage Values in Differential Mode, Non-signed Output Signed Ci VIN -2048 -3 0 0 2047 3 Single-ended Mode (12-bit mode) A single input voltage VIN can be applied to selected pins, e.g., ADC0_AD0 or ADC0_AD1. The ideal code Ci is calculated using the following formula and rounding the result to the nearest positive integer. The single-ended ideal code conversion formula is: 4095 C i = ------------------------- × V IN V ADVREF For the other resolution defined by RES, the code Ci is extended to the corresponding resolution. Table 66-33 is a computation example for the above formula, where VADVREF = 3V: Table 66-33: 66.11.4.3 Input Voltage Values in Single-ended Mode Non-signed Ci VIN 0 0 2047 1.5 4095 3 Example of LSB Computation The LSB is relative to the analog scale VADVREF. The term LSB expresses the quantization step in volts, also used for one ADC code variation. • Single-ended (SE) (ex: VADVREF = 3.0V) - Gain = 1, LSB = (3.0V / 4096) = 732 µV • Differential (DIFF) (ex: VADVREF = 3.0V) - Gain = 0.5, LSB = (6.0V / 4096) = 1465 µV The data include the ADC performances, as the PGA and ADC core cannot be separated. The temperature and voltage dependencies are given as separate parameters. 66.11.4.4 Gain and Offset Errors For: • a given gain error: EG (%) • a given ideal code (Ci) • a given offset error: EO (LSB of 12 bits) in 12-bit mode, the actual code (CA) is calculated using the following formula EG C A =  1 + ---------- × ( C i – 2047 ) + 2047 + E O  100 • Differential Mode In Differential mode, the offset is defined when the differential input voltage is zero. DS60001476B-page 2476  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-5: Gain and Offset Errors in Differential Mode ADC codes EG = (EFS+) - (EFS-) 2047 EFS+ EO = Offset error 0 EFS- -2048 -VADVREF/2 VIN Differential VADVREF/2 0 where: • Full-scale error EFS = (EFS+) - (EFS-), unit is LSB code • Offset error EO is the offset error measured for VIN = 0V • Gain error EG = 100 × EFS / 4096, unit in % The error values in Table 66-35 include the sample-and-hold error as well as the PGA gain error. • Single-ended Mode Figure 66-6 illustrates the ADC output code relative to an input voltage VIN between 0V (Ground) and VADVREF. The ADC is configured in Single-ended mode by connecting internally the negative differential input to VADVREF / 2. As the ADC continues to work internally in Differential mode, the offset is measured at VADVREF / 2. The offset at VINP = 0 can be computed using the transfer function and the corresponding EG and EO. Figure 66-6: Gain and Offset Errors in Single-ended Mode ADC codes EG = Gain error = EFS - EO 4095 EFS = Full-scale error EO = Offset error 2047 VIN Single-ended 0 VADVREF/2 VADVREF where: • Full-scale error EFS = (EFS+) - (EFS-), unit is LSB² code • Offset error EO is the offset error measured for VINP = 0V • Gain error EG = 100 x EFS / 2048, unit in % The error values in Table 66-35 include the DAC, the sample-and-hold error as well as the PGA gain error.  2017 Microchip Technology Inc. DS60001476B-page 2477 SAMA5D2 SERIES 66.11.5 ADC Electrical Characteristics Table 66-34: ADC INL and DNL, VADVREF = 3.3V Symbol Parameter INL Integral Non-Linearity DNL Differential Non-Linearity Conditions Min Typ Max Unit – 1 – 1 LSB – 1 – 1 LSB Differential Mode Single-Ended Mode INL Integral Non-Linearity – 1.5 – 1.5 LSB DNL Differential Non-Linearity – 1 – 1 LSB Min Typ Max Unit Table 66-35: ADC Offset and Gain Error, VADVREF = 3.3V Symbol Parameter Conditions EO Differential Offset Error – -2.0 – 2.0 LSB EG Differential Gain Error – -0.2 – 0.2 % EO Single-ended Offset Error – -2.0 – 2.0 LSB EG Single-ended Gain Error – -0.2 – 0.2 % Min Typ Max Unit Differential Mode Single-Ended Mode Table 66-36: Symbol ADC Analog Input Characteristics Parameter Conditions VFS Analog Input Full Scale Range(1) ADC_COR.DIFFx = 0 0 – VADVREF ADC_COR.DIFFx = 1 – VINCM Common Mode input range -VADVREF 0.4 × VADVREF 0.6 × CIN ADC sampling capacitance Analog input parasitic capacitance(4) CP_ADx (2) ADC_COR.DIFFx = 1 ADx pin configured as analog input VVDDANA VVDDANA – – 3 – – 10 – – 1 / (fS × ZIN Common Mode Input impedance(3) Notes: 1. VFS = VADx in Single-ended mode, VFS = (VADx - VADx+1) in Differential mode On ADx pin – CP_ADx) V V pF Ω 2. VINCM = (VADx + VADx+1) / 2 3. See Figure 63-7. When converting one single channel, most of the input parasitic capacitance in not switched, therefore the common mode input impedance reduces to ZIN = 1 / (fS × CIN) 4. Includes CIN DS60001476B-page 2478  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.11.6 ADC Channel Input Impedance Figure 66-7: Input Channel Model S&H Differential model S&H Single-ended model VINP VINP ZIN RON RON ZIN CIN CIN VDAC VDAC CIN VINN RON where: • ZIN is the input impedance in Single-ended or Differential mode • CIN = 2 pF ±20% depending on the gain value and mode (SE or DIFF); temperature dependency is negligible • RON is typical 2 kΩ and 8 kΩ max (worst case process and high temperature) The following formula is used to calculate input impedance: 1 Z IN = --------------------f S × C IN where: • fS is the sampling frequency of the ADC channel • Typ values are used to compute ADC input impedance ZIN Table 66-37: fS (MHz) ZIN Input Impedance 1 0.5 0.25 0.125 0.0625 0.03125 0.015625 0.007813 8 16 32 64 CIN = 2 pF ZIN (MΩ) 0.5 1 2 4 • Track and Hold Time versus Source Output Impedance Figure 66-8 shows a simplified acquisition path. Figure 66-8: Simplified Acquisition Path ADC Input ZSOURCE Mux. Sample & Hold 12-bit ADC RON CIN During the tracking phase, the ADC tracks the input signal during the tracking time shown below: tTRACK = n × CIN × (RON + ZSOURCE) / 1000  2017 Microchip Technology Inc. DS60001476B-page 2479 SAMA5D2 SERIES where • Tracking time expressed in ns and ZSOURCE expressed in Ω • n = 8 for 12-bit accuracy • RON = 2 kΩ Table 66-38: Number of Tau:n Resolution (bits) 12 RES 0 n 8 The ADC already includes a tracking time of 15 tADC Clock. 66.12 Analog Comparator Characteristics Table 66-39: Symbol VDDBU VCOM Px Analog Comparator Characteristics Parameter Conditions Power Supply Voltage Range Analog Comparator is supplied by VDDIN (VDDBU) On COMPP or COMPN input Input Voltage Range Min Typ Max Unit 1.62 3.3 3.6 V 0 – VDDBU V Vhys Hysteresis – 35 – 70 mV TPD Propagation Delay COMPx Input Signal Frequency 100mV Overdrive – – 350 µs Common mode and differential – – 1 kHz IVDDBU Current Consumption (VDDBU) OFF Mode (ACC_MR.ACEN = 0) – ON Mode (ACC_MR.ACEN = 1) – 100 200 tST ART Startup Time – – – 300 fin DS60001476B-page 2480 50 nA µs  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.13 POR Characteristics Figure 66-9 provides a general presentation of Power-On-Reset (POR) characteristics. Figure 66-9: General Presentation of POR Behavior VDD VT+ VT- Static Dynamic Vop Vnop NRST tRST When a very slow (versus tRST) supply rising slope is applied on the POR VDD pin, the reset time becomes negligible and the reset signal is released when VDD raises higher than VT+. When a very fast (versus tRST) supply rising slope is applied on the POR VDD pin, the voltage threshold becomes negligible and the reset signal is released after tRST. It is the smallest possible reset time. Table 66-40: VDDBU Power-On Reset Characteristics Symbol Parameter Conditions Min Typ Max Unit VT + Threshold Voltage Rising – 1.3 – 1.5 V VT - Threshold Voltage Falling – 1.22 – 1.4 V Vhys Hysteresis Voltage – 50 – 160 mV tRST Reset Timeout Period – 890 – 5100 µs Conditions Min Typ Max Unit Table 66-41: VDDCORE Power-On Reset Characteristics Symbol Parameter VT + Threshold Voltage Rising – 0.927 – 1.075 V VT - Threshold Voltage Falling – 0.848 – 1.025 V Vhys Hysteresis Voltage – 38 – 109 mV tRST Reset Timeout Period – 150 – 650 µs Conditions Min Typ Max Unit Table 66-42: VDDANA Power-On Reset Characteristics Symbol Parameter VT + Threshold Voltage Rising – 1.3 – 1.5 V VT - Threshold Voltage Falling – 1.22 – 1.4 V Vhys Hysteresis Voltage – 50 – 160 mV tRST Reset Timeout Period – 130 – 650 µs  2017 Microchip Technology Inc. DS60001476B-page 2481 SAMA5D2 SERIES 66.14 SMC Timings 66.14.1 Timing Conditions SMC timings are given in max corners. Timings assuming a capacitance load on data, control and address pads are given in Table 66-43. Table 66-43: Capacitance Load Corner Supply Max Min 3.3V 50 pF 5 pF 1.8V 30 pF 5 pF In the tables that follow, tCPMCK is the MCK period. DS60001476B-page 2482  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.14.2 66.14.2.1 SMC IOSET1 Timing Extraction SMC IOSET1 Read Timings Table 66-44: SMC IOSET1 Read Signals - NRD Controlled (READ_MODE = 1) Parameter Symbol Min Power supply 1.8V 3.3V Unit 16.4 15 ns 0 0 ns 14.4 13 ns 0 0 ns NO HOLD SETTINGS (nrd hold = 0) SMC1 Data Setup before NRD High SMC2 Data Hold after NRD High HOLD SETTINGS (nrd hold ≠ 0) SMC3 Data Setup before NRD High SMC4 Data Hold after NRD High HOLD or NO HOLD SETTINGS (nrd hold ≠ 0, nrd hold =0) SMC5 NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25 Valid before NRD High SMC6 NCS low before NRD High SMC7 NRD Pulse Width Table 66-45: (nrd setup + nrd pulse) × tCPMCK (nrd setup + nrd pulse) × tCPMCK ns (nrd setup + nrd pulse - ncs rd setup) × tCPMCK (nrd setup + nrd pulse - ncs rd setup) × tCPMCK ns nrd pulse × tCPMCK nrd pulse × tCPMCK ns SMC IOSET1 Read Signals - NCS Controlled (READ_MODE = 0) Parameter Symbol Min Power supply 1.8V 3.3V Unit 17.9 15.7 ns 0 0 ns 15.9 13.7 ns 0 0 ns NO HOLD SETTINGS (ncs rd hold = 0) SMC8 Data Setup before NCS High SMC9 Data Hold after NCS High HOLD SETTINGS (ncs rd hold ≠ 0) SMC10 Data Setup before NCS High SMC11 Data Hold after NCS High HOLD or NO HOLD SETTINGS (ncs rd hold ≠ 0, ncs rd hold = 0) SMC12 NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25 valid before NCS High SMC13 NRD low before NCS High SMC14 NCS Pulse Width  2017 Microchip Technology Inc. (ncs rd setup + ncs rd pulse) × tCPMCK (ncs rd setup + ncs rd pulse) × tCPMCK ns (ncs rd setup + ncs rd pulse - nrd setup) × tCPMCK (ncs rd setup + ncs rd pulse - nrd setup) × tCPMCK ns ncs rd pulse length × tCPMCK ncs rd pulse length × tCPMCK ns DS60001476B-page 2483 SAMA5D2 SERIES 66.14.2.2 SMC IOSET1 Write Timings Table 66-46: SMC IOSET1 Write Signals - NWE Controlled (WRITE_MODE = 1) Parameter Symbol Min Power supply 1.8V 3.3V Unit HOLD or NO HOLD SETTINGS (nwe hold ≠ 0, nwe hold = 0) SMC15 Data Out Valid before NWE High nwe pulse × tCPMCK nwe pulse × tCPMCK ns SMC16 NWE Pulse Width nwe pulse × tCPMCK nwe pulse × tCPMCK ns SMC17 NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 valid before NWE low nwe setup × tCPMCK nwe pulse × tCPMCK ns SMC18 NCS low before NWE high (nwe setup - ncs rd setup + nwe pulse) (nwe setup - ncs rd setup + nwe pulse) × tCPMCK × tCPMCK ns HOLD SETTINGS (nwe hold ≠ 0) SMC19 NWE High to Data OUT, NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 change SMC20 NWE High to NCS Inactive(1) nwe hold × tCPMCK nwe hold × tCPMCK ns (nwe hold - ncs wr hold) × tCPMCK (nwe hold - ncs wr hold) × tCPMCK ns 1.3 ns NO HOLD SETTINGS (nwe hold = 0) SMC21 NWE High to Data OUT, NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25, NCS change(1) 2.3 Note 1: hold length = total cycle duration - setup duration - pulse duration. “hold length” is for “ncs wr hold length” or “NWE hold length”. Table 66-47: SMC IOSET1 Write NCS Controlled (WRITE_MODE = 0) Parameter Symbol Power supply SMC22 Data Out Valid before NCS High SMC23 NCS Pulse Width SMC24 NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 valid before NCS low SMC25 NWE low before NCS high SMC26 NCS High to Data Out, NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25, change SMC27 NCS High to NWE Inactive DS60001476B-page 2484 Min 1.8V 3.3V Unit ncs wr pulse × tCPMCK ncs wr pulse × tCPMCK ns SMC14 SMC14 ns ncs wr setup × tCPMCK ncs wr setup × tCPMCK ns (ncs wr setup - nwe setup + ncs pulse) × tCPMCK (ncs wr setup - nwe setup + ncs pulse) × tCPMCK ns ncs wr hold × tCPMCK ncs wr hold × tCPMCK ns (ncs wr hold - nwe hold) × tCPMCK (ncs wr hold - nwe hold) × tCPMCK ns  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.14.3 66.14.3.1 SMC IOSET2 Timing Extraction SMC IOSET2 Read Timings Table 66-48: SMC IOSET2 Read Signals - NRD Controlled (READ_MODE = 1) Parameter Symbol Min Power supply 1.8V 3.3V Unit 16.5 15 ns 0 0 ns NO HOLD SETTINGS (nrd hold = 0) SMC1 Data Setup before NRD High SMC2 Data Hold after NRD High HOLD SETTINGS (nrd hold ≠ 0) SMC3 Data Setup before NRD High 14 12.6 ns SMC4 Data Hold after NRD High 0 0 ns (nrd setup + nrd pulse) × tCPMCK (nrd setup + nrd pulse) × tCPMCK ns (nrd setup + nrd pulse - ncs rd setup) × tCPMCK (nrd setup + nrd pulse - ncs rd setup) × tCPMCK ns nrd pulse × tCPMCK nrd pulse × tCPMCK ns 3.3V Unit 18.1 15.7 ns 0 0 ns 15.7 13.3 ns 0 0 ns HOLD or NO HOLD SETTINGS (nrd hold ≠ 0, nrd hold =0) SMC5 NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25 Valid before NRD High SMC6 NCS low before NRD High SMC7 NRD Pulse Width Table 66-49: SMC IOSET2 Read Signals - NCS Controlled (READ_MODE = 0) Parameter Symbol Min Power supply 1.8V NO HOLD SETTINGS (ncs rd hold = 0) SMC8 Data Setup before NCS High SMC9 Data Hold after NCS High HOLD SETTINGS (ncs rd hold ≠ 0) SMC10 Data Setup before NCS High SMC11 Data Hold after NCS High HOLD or NO HOLD SETTINGS (ncs rd hold ≠ 0, ncs rd hold = 0) SMC12 NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25 valid before NCS High SMC13 NRD low before NCS High SMC14 NCS Pulse Width  2017 Microchip Technology Inc. (ncs rd setup + ncs rd pulse) × tCPMCK (ncs rd setup + ncs rd pulse) × tCPMCK ns (ncs rd setup + ncs rd pulse - nrd setup) × tCPMCK (ncs rd setup + ncs rd pulse - nrd setup) × tCPMCK ns ncs rd pulse length × tCPMCK ncs rd pulse length × tCPMCK ns DS60001476B-page 2485 SAMA5D2 SERIES 66.14.3.2 SMC IOSET2 Write Timings Table 66-50: SMC IOSET2 Write Signals - NWE Controlled (WRITE_MODE = 1) Parameter Symbol Min Power supply 1.8V 3.3V Unit HOLD or NO HOLD SETTINGS (nwe hold ≠ 0, nwe hold = 0) SMC15 Data Out Valid before NWE High nwe pulse × tCPMCK nwe pulse × tCPMCK ns SMC16 NWE Pulse Width nwe pulse × tCPMCK nwe pulse × tCPMCK ns SMC17 NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 valid before NWE low nwe setup × tCPMCK nwe pulse × tCPMCK ns SMC18 NCS low before NWE high (nwe setup - ncs rd setup + nwe pulse) (nwe setup - ncs rd setup + nwe pulse) × tCPMCK × tCPMCK ns HOLD SETTINGS (nwe hold ≠ 0) SMC19 NWE High to Data OUT, NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 change SMC20 NWE High to NCS Inactive(1) nwe hold × tCPMCK nwe hold × tCPMCK ns (nwe hold - ncs wr hold) × tCPMCK (nwe hold - ncs wr hold) × tCPMCK ns 0.6 ns NO HOLD SETTINGS (nwe hold = 0) SMC21 NWE High to Data OUT, NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25, NCS change((1) 1.2 Note 1: hold length = total cycle duration - setup duration - pulse duration. “hold length” is for “ncs wr hold length” or “NWE hold length”. Table 66-51: SMC IOSET2 Write NCS Controlled (WRITE_MODE = 0) Parameter Symbol Power supply SMC22 Data Out Valid before NCS High SMC23 NCS Pulse Width SMC24 NBS0/A0 NBS1, NBS2/A1, NBS3, A2–A25 valid before NCS low SMC25 NWE low before NCS high SMC26 NCS High to Data Out, NBS0/A0, NBS1, NBS2/A1, NBS3, A2–A25, change SMC27 NCS High to NWE Inactive DS60001476B-page 2486 Min 1.8V 3.3V Unit ncs wr pulse × tCPMCK ncs wr pulse × tCPMCK ns SMC14 SMC14 ns ncs wr setup × tCPMCK ncs wr setup × tCPMCK ns (ncs wr setup - nwe setup + ncs pulse) × tCPMCK (ncs wr setup - nwe setup + ncs pulse) × tCPMCK ns ncs wr hold × tCPMCK ncs wr hold × tCPMCK ns (ncs wr hold - nwe hold) × tCPMCK (ncs wr hold - nwe hold) × tCPMCK ns  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-10: SMC Timings - NCS Controlled Read and Write SMC12 SMC12 SMC24 SMC26 A0/A1/NBS[3:0]/A2–A25 SMC13 SMC13 NRD NCS SMC14 SMC14 SMC9 SMC8 SMC10 SMC23 SMC11 SMC22 SMC26 D0–D15 SMC27 SMC25 NWE NCS Controlled READ with NO HOLD Figure 66-11: NCS Controlled READ with HOLD NCS Controlled WRITE SMC Timings - NRD Controlled Read and NWE Controlled Write SMC21 SMC5 SMC5 SMC17 SMC17 SMC19 A0/A1/NBS[3:0]/A2–A25 SMC6 SMC18 SMC18 SMC21 SMC6 SMC20 NCS NRD SMC7 SMC7 SMC1 SMC2 SMC15 SMC21 SMC3 SMC15 SMC4 SMC19 D0–D31 NWE SMC16 NRD Controlled READ with NO HOLD NWE Controlled WRITE with NO HOLD SMC16 NRD Controlled READ with HOLD NWE Controlled WRITE with HOLD 66.15 FLEXCOM Timings 66.15.1 FLEXCOM USART in Asynchronous Modes Refer to Section 66.16 “USART in Asynchronous Modes”. 66.15.2 66.15.2.1 FLEXCOM SPI Timings Timing Conditions Timings assuming a capacitance load on MISO, SPCK and MOSI are given in Table 66-63. Table 66-52: Capacitance Load for MISO, SPCK and MOSI (FLEXCOM 0, 1, 2, 3, 4) Corner Supply Max Min 3.3V 40 pF 5 pF 1.8V 20 pF 5 pF  2017 Microchip Technology Inc. DS60001476B-page 2487 SAMA5D2 SERIES 66.15.2.2 Timing Extraction Figure 66-12: FLEXCOM in SPI Master Modes 1 and 2 SPCK SPI0 SPI1 MISO SPI2 MOSI Figure 66-13: FLEXCOM in SPI Master Modes 0 and 3 SPCK SPI4 SPI3 MISO SPI5 MOSI Figure 66-14: FLEXCOM in SPI Slave Modes 0 and 3 NPCS0 SPI13 SPI12 SPCK SPI6 MISO SPI7 SPI8 MOSI DS60001476B-page 2488  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-15: FLEXCOM in SPI Slave Modes 1 and 2 NPCS0 SPI13 SPI12 SPCK SPI9 MISO SPI10 SPI11 MOSI Figure 66-16: FLEXCOM in SPI Slave Mode - NPCS Timings SPI14 SPI6 SPI15 SPCK (CPOL = 0) SPI12 SPI13 SPI9 SPCK (CPOL = 1) SPI16 MISO Table 66-53: FLEXCOM0 in SPI Mode IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.3 – 12.8 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 3.9 0 4.2 ns SPI3 MISO Setup time before SPCK falls 14.7 – 13.4 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 3.9 0 4.6 ns 13.4 9.1 11.9 ns Slave Mode SPI6 SPCK falling to MISO  2017 Microchip Technology Inc. 10.9 DS60001476B-page 2489 SAMA5D2 SERIES Table 66-53: FLEXCOM0 in SPI Mode IOSET1 Timings (Continued) Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit SPI7 MOSI Setup time before SPCK rises 5.3 – 5 – ns SPI8 MOSI Hold time after SPCK rises 0.4 – 0.3 – ns SPI9 SPCK rising to MISO 10.7 13.1 9 11.5 ns SPI10 MOSI Setup time before SPCK falls 5.3 – 5 – ns SPI11 MOSI Hold time after SPCK falls 0.4 – 0.3 – ns SPI12 NPCS0 setup to SPCK rising 5.6 – 5.4 – ns SPI13 NPCS0 hold after SPCK falling 0.7 – 0.6 – ns SPI14 NPCS0 setup to SPCK falling 5.4 – 5.2 – ns SPI15 NPCS0 hold after SPCK rising 0.2 – 0.1 – ns SPI16 NPCS0 falling to MISO valid 17.5 – 16.2 – ns DS60001476B-page 2490  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-54: FLEXCOM1 in SPI Mode IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 15.7 – 13.8 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.5 0 2.6 ns SPI3 MISO Setup time before SPCK falls 15.2 – 13.9 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 1.7 0 2.4 ns Slave Mode SPI6 SPCK falling to MISO 11.4 13.7 9.4 12.3 ns SPI7 MOSI Setup time before SPCK rises 2.4 – 2.1 – ns SPI8 MOSI Hold time after SPCK rises 1 – 0.9 – ns SPI9 SPCK rising to MISO 11 13.1 9 11.6 ns SPI10 MOSI Setup time before SPCK falls 2.4 – 2.1 – ns SPI11 MOSI Hold time after SPCK falls 1 – 0.9 – ns SPI12 NPCS0 setup to SPCK rising 3.9 – 3.7 – ns SPI13 NPCS0 hold after SPCK falling 1.1 – 1 – ns SPI14 NPCS0 setup to SPCK falling 3.4 – 3.3 – ns SPI15 NPCS0 hold after SPCK rising 0.6 – 0.4 – ns SPI16 NPCS0 falling to MISO valid 16.8 – 15.5 – ns  2017 Microchip Technology Inc. DS60001476B-page 2491 SAMA5D2 SERIES Table 66-55: FLEXCOM2 in SPI Mode IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 15.3 – 13.4 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.5 0 3 ns SPI3 MISO Setup time before SPCK falls 15.6 – 13.7 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 2.6 0 3.1 ns 11.7 13.5 9.4 11.7 ns 2 – 1.6 – ns Slave Mode SPI6 SPCK falling to MISO SPI7 MOSI Setup time before SPCK rises SPI8 MOSI Hold time after SPCK rises 0.5 – 0.5 – ns SPI9 SPCK rising to MISO 11.7 13.5 9.4 11.5 ns SPI10 MOSI Setup time before SPCK falls 2 – 1.6 – ns SPI11 MOSI Hold time after SPCK falls 0.5 – 0.5 – ns SPI12 NPCS0 setup to SPCK rising 4 – 3.7 – ns SPI13 NPCS0 hold after SPCK falling 0.6 – 0.6 – ns SPI14 NPCS0 setup to SPCK falling 3.9 – 3.7 – ns SPI15 NPCS0 hold after SPCK rising 0.4 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 16.8 – 13.6 – ns DS60001476B-page 2492  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-56: FLEXCOM2 in SPI Mode IOSET2 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 13.3 – 11.2 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 4.4 0 4.1 ns SPI3 MISO Setup time before SPCK falls 4.3 – 12.5 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0.3 4.4 0.4 4.4 ns Slave Mode SPI6 SPCK falling to MISO 10.1 12.2 8.2 10.4 ns SPI7 MOSI Setup time before SPCK rises 3.3 – 3.1 – ns SPI8 MOSI Hold time after SPCK rises 0.8 – 0.7 – ns SPI9 SPCK rising to MISO 9.8 11.8 7.9 9.8 ns SPI10 MOSI Setup time before SPCK falls 3.3 – 3.1 – ns SPI11 MOSI Hold time after SPCK falls 0.8 – 0.7 – ns SPI12 NPCS0 setup to SPCK rising 5.3 – 5.2 – ns SPI13 NPCS0 hold after SPCK falling 0.8 – 0.6 – ns SPI14 NPCS0 setup to SPCK falling 5 – 4.9 – ns SPI15 NPCS0 hold after SPCK rising 0.2 – 0.1 – ns SPI16 NPCS0 falling to MISO valid 15.9 – 14.2 – ns  2017 Microchip Technology Inc. DS60001476B-page 2493 SAMA5D2 SERIES Table 66-57: FLEXCOM3 in SPI Mode IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.6 – 12.7 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.6 0 2.9 ns SPI3 MISO Setup time before SPCK falls 14.2 – 13 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 1.8 0 2.9 ns Slave Mode SPI6 SPCK falling to MISO 11.6 14.1 9.5 12.7 ns SPI7 MOSI Setup time before SPCK rises 3.3 – 3.2 – ns SPI8 MOSI Hold time after SPCK rises 0.9 – 0.7 – ns SPI9 SPCK rising to MISO 11.2 13.6 9.1 12.2 ns SPI10 MOSI Setup time before SPCK falls 3.3 – 3.2 – ns SPI11 MOSI Hold time after SPCK falls 0.9 – 0.7 – ns SPI12 NPCS0 setup to SPCK rising 2.8 – 2.6 – ns SPI13 NPCS0 hold after SPCK falling 1.5 – 1.3 – ns SPI14 NPCS0 setup to SPCK falling 2.3 – 2.2 – ns SPI15 NPCS0 hold after SPCK rising 1 – 0.7 – ns SPI16 NPCS0 falling to MISO valid 15.4 – 14.1 – ns DS60001476B-page 2494  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-58: FLEXCOM3 in SPI Mode IOSET2 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.1 – 12.6 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 3.8 0 4.1 ns SPI3 MISO Setup time before SPCK falls 14.9 – 13.7 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 3.9 0 4.5 ns Slave Mode SPI6 SPCK falling to MISO 10.6 13.1 8.6 11.8 ns SPI7 MOSI Setup time before SPCK rises 3.7 – 3.5 – ns SPI8 MOSI Hold time after SPCK rises 0.6 – 0.5 – ns SPI9 SPCK rising to MISO 10.2 12.6 8.2 11.1 ns SPI10 MOSI Setup time before SPCK falls 3.7 – 3.5 – ns SPI11 MOSI Hold time after SPCK falls 0.6 – 0.5 – ns SPI12 NPCS0 setup to SPCK rising 4.5 – 4.3 – ns SPI13 NPCS0 hold after SPCK falling 1 – 0.9 – ns SPI14 NPCS0 setup to SPCK falling 4 – 3.9 – ns SPI15 NPCS0 hold after SPCK rising 0.4 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 16.9 – 15.6 – ns  2017 Microchip Technology Inc. DS60001476B-page 2495 SAMA5D2 SERIES Table 66-59: FLEXCOM3 in SPI Mode IOSET3 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.2 – 12.7 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 3.4 0 3.7 ns SPI3 MISO Setup time before SPCK falls 15.1 – 13.8 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 3.5 0 4.2 ns Slave Mode SPI6 SPCK falling to MISO 11.4 14.1 9.4 12.8 ns SPI7 MOSI Setup time before SPCK rises 5.4 – 5.1 – ns SPI8 MOSI Hold time after SPCK rises 0.4 – 0.3 – ns SPI9 SPCK rising to MISO 11 13.6 9 12.2 ns SPI10 MOSI Setup time before SPCK falls 5.4 – 5.1 – ns SPI11 MOSI Hold time after SPCK falls 0.4 – 0.3 – ns SPI12 NPCS0 setup to SPCK rising 4.3 – 4.2 – ns SPI13 NPCS0 hold after SPCK falling 1.1 – 0.9 – ns SPI14 NPCS0 setup to SPCK falling 3.8 – 3.7 – ns SPI15 NPCS0 hold after SPCK rising 0.5 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 17.5 – 16.2 – ns DS60001476B-page 2496  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-60: FLEXCOM4 in SPI Mode IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.7 – 13.1 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.7 0 3.2 ns SPI3 MISO Setup time before SPCK falls 15.2 – 13.8 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 2.9 0 3.6 ns Slave Mode SPI6 SPCK falling to MISO 10.9 13.2 8.9 11.9 ns SPI7 MOSI Setup time before SPCK rises 3.3 – 3.2 – ns SPI8 MOSI Hold time after SPCK rises 0.7 – 0.6 – ns SPI9 SPCK rising to MISO 10.5 12.7 8.5 11.3 ns SPI10 MOSI Setup time before SPCK falls 3.3 – 3.2 – ns SPI11 MOSI Hold time after SPCK falls 0.7 – 0.6 – ns SPI12 NPCS0 setup to SPCK rising 5.7 – 5.5 – ns SPI13 NPCS0 hold after SPCK falling 0.6 – 0.5 – ns SPI14 NPCS0 setup to SPCK falling 5.2 – 5 – ns SPI15 NPCS0 hold after SPCK rising 0 – 0 – ns SPI16 NPCS0 falling to MISO valid 17.8 – 16.5 – ns  2017 Microchip Technology Inc. DS60001476B-page 2497 SAMA5D2 SERIES Table 66-61: FLEXCOM4 in SPI Mode IOSET2 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.7 – 11.5 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.7 0 4.7 ns SPI3 MISO Setup time before SPCK falls 15.2 – 12.8 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 2.9 0.8 5.1 ns Slave Mode SPI6 SPCK falling to MISO 10.9 13.2 7.8 10.2 ns SPI7 MOSI Setup time before SPCK rises 3.3 – 2.2 – ns SPI8 MOSI Hold time after SPCK rises 0.7 – 0.8 – ns SPI9 SPCK rising to MISO 10.5 12.7 7.7 9.9 ns SPI10 MOSI Setup time before SPCK falls 3.3 – 2.2 – ns SPI11 MOSI Hold time after SPCK falls 0.7 – 0.8 – ns SPI12 NPCS0 setup to SPCK rising 5.6 – 3.3 – ns SPI13 NPCS0 hold after SPCK falling 0.6 – 1.1 – ns SPI14 NPCS0 setup to SPCK falling 5.2 – 3.1 – ns SPI15 NPCS0 hold after SPCK rising 0 – 0.8 – ns SPI16 NPCS0 falling to MISO valid 17.8 – 12.9 – ns DS60001476B-page 2498  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-62: FLEXCOM4 in SPI Mode IOSET3 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.2 – 12.2 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 3.6 0 3.6 ns SPI3 MISO Setup time before SPCK falls 15.1 – 13.3 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0.1 3.7 0.1 4 ns Slave Mode SPI6 SPCK falling to MISO 9.9 12.4 8 10.5 ns SPI7 MOSI Setup time before SPCK rises 3.9 – 3.7 – ns SPI8 MOSI Hold time after SPCK rises 0.8 – 0.7 – ns SPI9 SPCK rising to MISO 9.5 11.9 7.7 9.9 ns SPI10 MOSI Setup time before SPCK falls 3.9 – 3.7 – ns SPI11 MOSI Hold time after SPCK falls 0.8 – 0.7 – ns SPI12 NPCS0 setup to SPCK rising 4.8 – 4.6 – ns SPI13 NPCS0 hold after SPCK falling 1 – 0.9 – ns SPI14 NPCS0 setup to SPCK falling 4.4 – 4.3 – ns SPI15 NPCS0 hold after SPCK rising 0.5 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 16 – 14.2 – ns Figure 66-17: Minimum and Maximum Access Time for SPI Output Signal SPCK SPI0 SPI1 MISO SPI2max MOSI SPI2min 66.15.3 FLEXCOM TWI Timings Refer to Section 66.18 “TWI Timings”.  2017 Microchip Technology Inc. DS60001476B-page 2499 SAMA5D2 SERIES 66.16 USART in Asynchronous Modes In Asynchronous modes, the maximum baud rate that can be achieved is MCK2 / 8, if the bit USART_MR.OVER=1. Example: if MCK2 = 83 MHz, the baud rate is 10.375 MBit/s. 66.17 SPI Timings 66.17.1 Maximum SPI Frequency The following formulas give maximum SPI frequency in Master Read and Write modes and in Slave Read and Write modes. • Master Write Mode The SPI send data to a slave device only, e.g. an LCD. The limit is given by SPI2 (or SPI5) timing. • Master Read Mode 1 f SPCK max = -------------------------------------------------------------SPI 0 ( or SPI 3 ) + t VALID tVALID is the slave time response to output data after deleting an SPCK edge. The fSPCK max is given between the maximum frequency given by the above formula and the pad I/O limitation. • Slave Read Mode In Slave mode, SPCK is the input clock for the SPI. The max SPCK frequency is given by setup and hold timings SPI7/SPI8 (or SPI10/ SPI11). Since this gives a frequency well above the pad limit, the limit in Slave Read mode is given by the SPCK pad. • Slave Write Mode 1 f SPCK max = ---------------------------------------------------------------SPI 6 ( or SPI 9 ) + t SETUP tSETUP is the setup time from the master before sampling data (6 ns). The fSPCK max is given between the maximum frequency given by the above formula and the pad I/O limitation. 66.17.2 Timing Conditions Timings assuming a capacitance load on MISO, SPCK and MOSI are given in Table 66-63. Table 66-63: Capacitance Load for MISO, SPCK and MOSI (SPI0 and SPI1) Corner 66.17.3 Supply Max Min 3.3V 40 pF 5 pF 1.8V 20 pF 5 pF Timing Extraction In Figure 66-19 “SPI Master Modes 1 and 2” and Figure 66-20 “SPI Master Modes 0 and 3” below, the MOSI line shifting edge is represented with a hold time = 0. However, it is important to note that for this device, the MISO line is sampled prior to the MOSI line shifting edge. As shown in Figure 66-18 “MISO Capture in Master Mode”, the device sampling point extends the propagation delay (tp) for slave and routing delays to more than half the SPI clock period, whereas the common sampling point allows only less than half the SPI clock period. As an example, an SPI Slave working in Mode 0 is safely driven if the SPI Master is configured in Mode 0. DS60001476B-page 2500  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-18: MISO Capture in Master Mode 0 < delay < SPI0 or SPI3 SPCK (generated by the master) MISO Bit N (slave answer) Bit N+1 MISO cannot be provided before the edge tp Common sampling point Device sampling point Safe margin, always >0 Extended tp Internal shift register Bit N Figure 66-19: SPI Master Modes 1 and 2 SPCK SPI0 SPI1 MISO SPI2 MOSI Figure 66-20: SPI Master Modes 0 and 3 SPCK SPI3 SPI4 MISO SPI5 MOSI  2017 Microchip Technology Inc. DS60001476B-page 2501 SAMA5D2 SERIES Figure 66-21: SPI Slave Modes 0 and 3 NPCS0 SPI13 SPI12 SPCK SPI6 MISO SPI7 SPI8 MOSI Figure 66-22: SPI Slave Modes 1 and 2 NPCS0 SPI13 SPI12 SPCK SPI9 MISO SPI10 SPI11 MOSI DS60001476B-page 2502  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-23: SPI Slave Mode - NPCS Timings SPI14 SPI6 SPI15 SPCK (CPOL = 0) SPI12 SPI13 SPI9 SPCK (CPOL = 1) SPI16 MISO Table 66-64: SPI0 IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.3 – 12.4 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 1.9 0 2.4 ns SPI3 MISO Setup time before SPCK falls 13.8 – 12.6 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 1.2 0 2.3 ns Slave Mode SPI6 SPCK falling to MISO 10.5 12.6 8.4 10.9 ns SPI7 MOSI Setup time before SPCK rises 1.5 – 1.4 – ns SPI8 MOSI Hold time after SPCK rises 1.7 – 1.5 – ns SPI9 SPCK rising to MISO 10 12 8 10.2 ns SPI10 MOSI Setup time before SPCK falls 1.5 – 1.4 – ns SPI11 MOSI Hold time after SPCK falls 1.7 – 1.5 – ns SPI12 NPCS0 setup to SPCK rising 4.4 – 4.3 – ns SPI13 NPCS0 hold after SPCK falling 1.5 – 1.3 – ns SPI14 NPCS0 setup to SPCK falling 3.9 – 3.9 – ns SPI15 NPCS0 hold after SPCK rising 0.8 – 0.5 – ns SPI16 NPCS0 falling to MISO valid 13.3 – 11.7 – ns  2017 Microchip Technology Inc. DS60001476B-page 2503 SAMA5D2 SERIES Table 66-65: SPI0 IOSET2 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.5 – 13 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 2.5 0 3 ns SPI3 MISO Setup time before SPCK falls 14.9 – 13.6 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 2.7 0 3.4 ns Slave Mode SPI6 SPCK falling to MISO 10.3 12. 8.5 11.2 ns SPI7 MOSI Setup time before SPCK rises 2.3 – 2.2 – ns SPI8 MOSI Hold time after SPCK rises 1 – 0.9 – ns SPI9 SPCK rising to MISO 9.9 12 8.1 10.5 ns SPI10 MOSI Setup time before SPCK falls 2.3 – 2.2 – ns SPI11 MOSI Hold time after SPCK falls 1 – 0.9 – ns SPI12 NPCS0 setup to SPCK rising 6.1 – 5.9 – ns SPI13 NPCS0 hold after SPCK falling 0.8 – 0.7 – ns SPI14 NPCS0 setup to SPCK falling 5.6 – 5.6 – ns SPI15 NPCS0 hold after SPCK rising 0.2 – 0.1 – ns SPI16 NPCS0 falling to MISO valid 15.1 – 13.8 – ns DS60001476B-page 2504  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-66: SPI1 IOSET1 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 14.6 – 13.1 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 0.8 0 1.2 ns SPI3 MISO Setup time before SPCK falls 15 – 13.7 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 0.9 0 1.6 ns Slave Mode SPI6 SPCK falling to MISO 10.3 12.4 8.3 11.2 ns SPI7 MOSI Setup time before SPCK rises 3.5 – 3.4 – ns SPI8 MOSI Hold time after SPCK rises 0.8 – 0.7 – ns SPI9 SPCK rising to MISO 9.8 11.8 7.8 10.4 ns SPI10 MOSI Setup time before SPCK falls 3.5 – 3.4 – ns SPI11 MOSI Hold time after SPCK falls 0.8 – 0.7 – ns SPI12 NPCS0 setup to SPCK rising 4.9 – 4.8 – ns SPI13 NPCS0 hold after SPCK falling 1.1 – 0.9 – ns SPI14 NPCS0 setup to SPCK falling 4.4 – 4.4 – ns SPI15 NPCS0 hold after SPCK rising 0.5 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 14.7 – 13.4 – ns  2017 Microchip Technology Inc. DS60001476B-page 2505 SAMA5D2 SERIES Table 66-67: SPI1 IOSET2 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 15.5 – 13.6 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 1.2 0 1.7 ns SPI3 MISO Setup time before SPCK falls 14.9 – 13.7 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 0.5 0 1.6 ns 10.7 12.9 8.6 11.1 ns Slave Mode SPI6 SPCK falling to MISO SPI7 MOSI Setup time before SPCK rises 3 – 2.9 – ns SPI8 MOSI Hold time after SPCK rises 1 – 0.9 – ns SPI9 SPCK rising to MISO 10.3 12.4 8.2 10.5 ns SPI10 MOSI Setup time before SPCK falls 3 – 2.9 – ns SPI11 MOSI Hold time after SPCK falls 1 – 0.9 – ns SPI12 NPCS0 setup to SPCK rising 4.4 – 4.3 – ns SPI13 NPCS0 hold after SPCK falling 1 – 0.9 – ns SPI14 NPCS0 setup to SPCK falling 4 – 4 – ns SPI15 NPCS0 hold after SPCK rising 0.4 – 0.3 – ns SPI16 NPCS0 falling to MISO valid 14.5 – 12.9 – ns DS60001476B-page 2506  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-68: SPI1 IOSET3 Timings Power Supply Symbol Parameter 1.8V Min 3.3V Max Min Max Unit 13.7 – 11.7 – ns Master Mode SPI0 MISO Setup time before SPCK rises SPI1 MISO Hold time after SPCK rises 0 – 0 – ns SPI2 SPCK rising to MOSI 0 3.1 0 2.9 ns SPI3 MISO Setup time before SPCK falls 14.1 – 12.4 – ns SPI4 MISO Hold time after SPCK falls 0 – 0 – ns SPI5 SPCK falling to MOSI 0 3.1 0 3.3 ns Slave Mode SPI6 SPCK falling to MISO 9.5 11.4 7.5 9.6 ns SPI7 MOSI Setup time before SPCK rises 4.5 – 4.4 – ns SPI8 MOSI Hold time after SPCK rises 0.7 – 0.5 – ns SPI9 SPCK rising to MISO 9.1 11 7.1 9.8 ns SPI10 MOSI Setup time before SPCK falls 4.5 – 4.4 – ns SPI11 MOSI Hold time after SPCK falls 0.7 – 0.5 – ns SPI12 NPCS0 setup to SPCK rising 5.1 – 4.9 – ns SPI13 NPCS0 hold after SPCK falling 0.9 – 0.8 – ns SPI14 NPCS0 setup to SPCK falling 4.7 – 4.6 – ns SPI15 NPCS0 hold after SPCK rising 0.3 – 0.2 – ns SPI16 NPCS0 falling to MISO valid 13.9 – 12.2 – ns Figure 66-24: Minimum and Maximum Access Time for SPI Output Signal SPCK SPI0 SPI1 MISO SPI2max MOSI SPI2min  2017 Microchip Technology Inc. DS60001476B-page 2507 SAMA5D2 SERIES 66.18 TWI Timings Figure 66-25: Two-wire Serial Bus Timing tfo tHIGH tr tLOW tLOW TWCK tsu(start) th(start) th(data) tsu(data) tsu(stop) TWD tBUF Table 66-69 describes the requirements for devices connected to the Two-wire Serial Bus. Table 66-69: Two-wire Serial Bus Requirements Symbol Parameter Conditions Min Max Unit VIL Input Low-voltage – -0.3 0.3 × VDDIO V VIH Input High-voltage – 0.7 × VDDIO VCC + 0.3 V Vhys Hysteresis of Schmitt Trigger Inputs – 0.150 – V VOL Output Low-voltage 3 mA sink current – 0.4 V (2) 300 ns 10 pF < Cb < 400 pF Figure 66-25 20 + 0.1Cb(2) 250 ns tr Rise Time for both TWD and TWCK tfo Output Fall Time from VIHmin to VILmax Ci(1) Capacitance for each I/O Pin – – 10 pF fTWCK TWCK Clock Frequency – 0 400 kHz Rp Value of Pull-up Resistor fTWCK ≤ 100 kHz (VDDIO - 0.4V) ÷ 3mA 1000ns ÷ Cb Ω fTWCK > 100 kHz (VDDIO - 0.4V) ÷ 3mA 300ns ÷ Cb Ω fTWCK ≤ 100 kHz (3) – µs fTWCK > 100 kHz (3) – µs fTWCK ≤ 100 kHz (4) – µs fTWCK > 100 kHz (4) – µs fTWCK ≤ 100 kHz tHIGH – µs fTWCK > 100 kHz tHIGH – µs fTWCK ≤ 100 kHz tHIGH – µs fTWCK > 100 kHz tHIGH – µs fTWCK ≤ 100 kHz 0 (HOLD + 3) × tperipheral µs fTWCK > 100 kHz 0 tLOW Low Period of the TWCK Clock tHIGH High Period of the TWCK Clock th(start) Hold Time (repeated) START condition tsu(start) Setup Time for a Repeated START condition th(data) 20 + 0.1Cb clock Data Hold Time DS60001476B-page 2508 (HOLD + 3) × tperipheral µs clock  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-69: Symbol tsu(data) Two-wire Serial Bus Requirements (Continued) Parameter Conditions Min Max Unit fTWCK ≤ 100 kHz tLOW - (HOLD + 3) × tperipheral clock – ns fTWCK > 100 kHz tLOW - (HOLD + 3) × tperipheral clock – ns fTWCK ≤ 100 kHz tHIGH – µs fTWCK > 100 kHz tHIGH – µs fTWCK ≤ 100 kHz tLOW – µs fTWCK > 100 kHz tLOW – µs Data Setup Time tsu(stop) Setup time for STOP condition tBUF Bus free time between a STOP and START condition Note 1: Required only for fTWCK > 100 kHz 2: Cb = capacitance of one bus line in pF. Per I2C Standard, Cb Max = 400 pF 3: The TWCK low period is defined as follows: tLOW = ((CLDIV × 2CKDIV) + 4) × tMCK 4: The TWCK high period is defined as follows: tHIGH = ((CHDIV × 2CKDIV) + 4) × tMCK  2017 Microchip Technology Inc. DS60001476B-page 2509 SAMA5D2 SERIES 66.19 QSPI Timings 66.19.1 Maximum QSPI Frequency The following formulas give maximum QSPI frequency in Master Read and Write modes. • Master Write Mode The QSPI sends data to a slave device only, e.g. an LCD. The limit is given by QSPI2 (or QSPI5) timing. • Master Read Mode 1 f QSCK max = -----------------------------------------------------------------------QSPI 0 ( or QSPI 3 ) + t VALID tVALID is the slave time response to output data after detecting a QSCK edge. The fQSCK max is given between the maximum frequency given by the above formula and the pad I/O limitation. 66.19.2 Timing Conditions Timings assuming a capacitance load are given in Table 66-70. Table 66-70: Capacitance Load (QSPI 0 and QSPI1) Corner 66.19.3 Supply Max Min 3.3V 30 pF 5 pF 1.8V 20 pF 5 pF Timing Extraction Figure 66-26: QSPI Master Mode 0 QSCK QSPI0 QSPI1 QIOx_DIN QSPI2 QIOx_DOUT Figure 66-27: QSPI Master Mode 1 QSCK QSPI3 QSPI4 QIOx_DIN QSPI5 QIOx_DOUT DS60001476B-page 2510  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-28: QSPI Master Mode 2 QSCK QSPI6 QSPI7 QIOx_DIN QSPI8 QIOx_DOUT Figure 66-29: QSPI Master Mode 3 QSCK QSPI9 QSPI10 QIOx_DIN QSPI11 QIOx_DOUT  2017 Microchip Technology Inc. DS60001476B-page 2511 SAMA5D2 SERIES Table 66-71: QSPI0 IOSET1 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 0 QSPI0 QIOx Input setup time before SCK falls 1.5 – 1.4 – ns QSPI1 QIOx Input hold time after SCK falls 0.4 – 0.5 – ns QSPI2 SCK falling to QIOx valid 0 3.4 0 2.4 ns QSPI3 QIOx Input setup time before SCK rises 11 – 8.7 – ns QSPI4 QIOx Input hold time after SCK rises 0.1 – 0 – ns QSPI5 SCK rising to QIOx valid 0 3 0 2.2 ns Mode 1 Mode 2 QSPI6 QIOx Input setup time before SCK rises 1.7 – 1.4 – ns QSPI7 QIOx Input hold time after SCK rises 0.1 – 0 – ns QSPI8 SCK rising to QIOx valid 0 3.3 0 2.3 ns QSPI9 QIOx Input setup time before SCK falls 11 – 8.9 – ns QSPI10 QIOx Input hold time after SCK falls 0.4 – 0.4 – ns QSPI11 SCK falling to QIOx valid 0 3.2 0 2.4 ns Mode 3 Table 66-72: QSPI0 IOSET2 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 0 QSPI0 QIOx Input setup time before SCK falls 2.2 – 2.2 – ns QSPI1 QIOx Input hold time after SCK falls 0.8 – 0.7 – ns QSPI2 SCK falling to QIOx valid 0 1.8 0 2 ns Mode 1 QSPI3 QIOx Input setup time before SCK rises 12.7 – 10.5 – ns QSPI4 QIOx Input hold time after SCK rises 0.3 – 0.2 – ns QSPI5 SCK rising to QIOx valid 0 2.2 0 1.9 ns Mode 2 QSPI6 QIOx Input setup time before SCK rises 2.6 – 2.5 – ns QSPI7 QIOx Input hold time after SCK rises 0.3 – 0.2 – ns QSPI8 SCK rising to QIOx valid 0 2.4 0 2 ns QIOx Input setup time before SCK falls 12 – 10.5 – ns Mode 3 QSPI9 DS60001476B-page 2512  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-72: QSPI0 IOSET2 Timings (Continued) Power Supply Symbol Parameter QSPI10 QIOx Input hold time after SCK falls QSPI11 SCK falling to QIOx valid Table 66-73: 1.8V 3.3V Min Max Min Max Unit 0.8 – 0.7 – ns 0 1.5 0 1.9 ns QSPI0 IOSET3 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 0 QSPI0 QIOx Input setup time before SCK falls 1.8 – 1.7 – ns QSPI1 QIOx Input hold time after SCK falls 0.8 – 0.7 – ns QSPI2 SCK falling to QIOx valid 0 1.8 0 2.1 ns Mode 1 QSPI3 QIOx Input setup time before SCK rises 12.3 – 10.1 – ns QSPI4 QIOx Input hold time after SCK rises 0.5 – 0.3 – ns QSPI5 SCK rising to QIOx valid 0 2.2 0 2 ns QSPI6 QIOx Input setup time before SCK rises 2 – 1.7 – ns QSPI7 QIOx Input hold time after SCK rises 0.5 – 0.3 – ns QSPI8 SCK rising to QIOx valid 0 2.5 0 2.2 ns Mode 2 Mode 3 QSPI9 QIOx Input setup time before SCK falls 11.7 – 10.2 – ns QSPI10 QIOx Input hold time after SCK falls 0.8 – 0.7 – ns QSPI11 SCK falling to QIOx valid 0 1.5 1.2 2 ns Table 66-74: QSPI1 IOSET1 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit 1.1 – 0.9 – ns Mode 0 QSPI0 QIOx Input setup time before SCK falls QSPI1 QIOx Input hold time after SCK falls 1 – 0.7 – ns QSPI2 SCK falling to QIOx valid 0 3.2 0 2.4 ns QSPI3 QIOx Input setup time before SCK rises 12 – 9.7 – ns QSPI4 QIOx Input hold time after SCK rises 0.8 – 0.5 – ns QSPI5 SCK rising to QIOx valid 0 2.7 0 2.1 ns Mode 1 Mode 2  2017 Microchip Technology Inc. DS60001476B-page 2513 SAMA5D2 SERIES Table 66-74: QSPI1 IOSET1 Timings (Continued) Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit QSPI6 QIOx Input setup time before SCK rises 1.1 – 0.8 – ns QSPI7 QIOx Input hold time after SCK rises 0.8 – 0.5 – ns QSPI8 SCK rising to QIOx valid 0 3 0 2.3 ns 12.2 – 10 – ns Mode 3 QSPI9 QIOx Input setup time before SCK falls QSPI10 QIOx Input hold time after SCK falls 1 – 0.7 – ns QSPI11 SCK falling to QIOx valid 0 3 0 2.4 ns Table 66-75: QSPI1 IOSET2 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 0 QSPI0 QIOx Input setup time before SCK falls 1.9 – 1.9 – ns QSPI1 QIOx Input hold time after SCK falls 0.8 – 0.7 – ns QSPI2 SCK falling to QIOx valid 0 1.5 0 1.9 ns Mode 1 QSPI3 QIOx Input setup time before SCK rises 12.6 – 10.4 – ns QSPI4 QIOx Input hold time after SCK rises 0.2 – 0.1 – ns QSPI5 SCK rising to QIOx valid 0 1.9 0 1.8 ns Mode 2 QSPI6 QIOx Input setup time before SCK rises 2.2 – 2.1 – ns QSPI7 QIOx Input hold time after SCK rises 0.2 – 0.1 – ns QSPI8 SCK rising to QIOx valid 0 2.2 0 2 ns Mode 3 QSPI9 QIOx Input setup time before SCK falls 11.9 – 10.4 – ns QSPI10 QIOx Input hold time after SCK falls 0.8 – 0.7 – ns QSPI11 SCK falling to QIOx valid 0 1.3 0 1.9 ns Table 66-76: QSPI1 IOSET3 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 0 QSPI0 QIOx Input setup time before SCK falls 1.8 – 1.8 – ns QSPI1 QIOx Input hold time after SCK falls 0.9 – 0.7 – ns QSPI2 SCK falling to QIOx valid 0 1.3 0 1.8 ns DS60001476B-page 2514  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-76: QSPI1 IOSET3 Timings (Continued) Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit Mode 1 QSPI3 QIOx Input setup time before SCK rises 13.1 – 10.9 – ns QSPI4 QIOx Input hold time after SCK rises 0.4 – 0.2 – ns QSPI5 SCK rising to QIOx valid 0 1.7 0 1.7 ns Mode 2 QSPI6 QIOx Input setup time before SCK rises 2.2 – 2.1 – ns QSPI7 QIOx Input hold time after SCK rises 0.4 – 0.2 – ns QSPI8 SCK rising to QIOx valid 0 2 0 1.8 ns Mode 3 QSPI9 QIOx Input setup time before SCK falls 12.5 – 11 – ns QSPI10 QIOx Input hold time after SCK falls 0.9 – 0.7 – ns QSPI11 SCK falling to QIOx valid 0 1.1 0 1.7 ns 66.20 MPDDRC Timings 66.20.1 Board Design Constraints As the SAMA5D2 series embeds impedance calibrated pads, there are no capacitive constraints on DDR signals. However, a board must be designed and equipped in order to respect propagation time and intrinsic delay in the SDRAM device. In all cases, line length to memory device must not exceed 5 cm. 66.20.2 DDR2-SDRAM Note: For DDR2 memory, the SHIFT_SAMPLING field value in the MPRDDRC_RD_DATA_PATH register must be configured to 1. Table 66-77: Symbol tDDRCK 66.20.3 System Clock Waveform Parameters Parameter DDRCK Cycle Time Conditions Min Max Unit VDDCORE[1.1V, 1.32V], TA = 85°C 7.5 8.0 ns VDDCORE[1.2V, 1.32V], VDDIODDR[1.75V, 1.9V], TA = 85°C 6.0 8.0 ns LPDDR1-SDRAM Note: For LPDDR1 memory, the SHIFT_SAMPLING field value in the MPRDDRC_RD_DATA_PATH register must be configured as follows: SHIFT_SAMPLING = 0 for 0 < DDR_CLK < 94 MHz SHIFT_SAMPLING = 1 for 94 MHz < DDR_CLK < 166 MHz  2017 Microchip Technology Inc. DS60001476B-page 2515 SAMA5D2 SERIES Table 66-78: System Clock Waveform Parameters Symbol Parameter Conditions Min Max Unit tDDRCK DDRCK Cycle Time VDDCORE[1.1V, 1.32V], TA = 85°C 7.5 – ns tDDRCK DDRCK Cycle Time VDDCORE[1.2V, 1.32V], VDDIODDR[1.75V, 1.9V], TA = 85°C 6 – ns 66.20.4 LPDDR2/LPDDR3-SDRAM Note: For LPDDR2/LPDDR3 memory, the SHIFT_SAMPLING field value in the MPRDDRC_RD_DATA_PATH register must be configured as follows: SHIFT_SAMPLING = 0 for 0 < DDR_CLK < 80 MHz SHIFT_SAMPLING = 1 for 80 MHz < DDR_CLK < 166 MHz Table 66-79: System Clock Waveform Parameters Symbol Parameter Conditions Min Max Unit tDDRCK DDRCK Cycle Time VDDCORE[1.1V, 1.32V], TA = 85°C 7.5 – ns tDDRCK DDRCK Cycle Time VDDCORE[1.1V, 1.32V], VDDIODDR[1.18V, 1.3V], TA = 85°C 6 – ns 66.20.5 DDR3/DDR3L-SDRAM Note: For DDR3/DDR3L memory, the SHIFT_SAMPLING field value in the MPRDDRC_RD_DATA_PATH register must be configured to 2. Table 66-80: System Clock Waveform Parameters Symbol Parameter Conditions Min Max Unit tDDRCK DDRCK Cycle Time VDDCORE[1.1V, 1.32V], TA = 85°C 8.0 – ns tDDRCK DDRCK Cycle Time VDDCORE[1.1V, 1.32V], VDDIODDR[1.18V, 1.3V], TA = 85°C 8.0 – ns 66.21 SSC Timings 66.21.1 Timing Conditions Timings assuming a capacitance load are given in Table 66-81. Table 66-81: Capacitance Load (SSC0 and SSC1) Corner Supply Max Min 3.3V 30 pF 5 pF 1.8V 20 pF 5 pF DS60001476B-page 2516  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.21.2 Timing Extraction Figure 66-30: SSC Transmitter, TK and TF in Output TK (CKI =0) TK (CKI =1) SSC0 TF/TD Figure 66-31: SSC Transmitter, TK in Input and TF in Output TK (CKI = 0) TK (CKI = 1) SSC1 TF/TD Figure 66-32: SSC Transmitter, TK in Output and TF in Input TK (CKI = 0) TK (CKI = 1) SSC2 SSC3 TF SSC4 TD  2017 Microchip Technology Inc. DS60001476B-page 2517 SAMA5D2 SERIES Figure 66-33: SSC Transmitter, TK and TF in Input TK (CKI = 0) TK (CKI = 1) SSC5 SSC6 TF SSC7 TD Figure 66-34: SSC Receiver RK and RF in Input RK (CKI = 0) RK (CKI = 1) SSC8 SSC9 RF/RD Figure 66-35: SSC Receiver, RK in Input and RF in Output RK (CKI = 0) RK (CKI = 1) SSC8 SSC9 RD SSC10 RF DS60001476B-page 2518  2017 Microchip Technology Inc. SAMA5D2 SERIES Figure 66-36: SSC Receiver, RK and RF in Output RK (CKI = 0) RK (CKI = 1) SSC12 SSC11 RD SSC13 RF Figure 66-37: SSC Receiver, RK in Output and RF in Input RK (CKI = 0) RK (CKI = 1) SSC12 SSC11 RF/RD Table 66-82: SSC0 IOSET1 Timings Power supply Symbol 1.8V Parameter Conditions Min 3.3V Max Min Max Unit Transmitter SSC0 TK edge to TF/TD (TK output, TF output) (1) – 0 3 0 3.3 ns SSC1 TK edge to TF/TD (TK input, TF output) (1) – 3.7 13 3 11.3 ns SSC2 TF setup time before TK edge (TK output) – 12.8 – 11.2 – ns SSC3 TF hold time after TK edge (TK output) – 0 – 0 – ns – 0 3 0 3.3 ns SSC4 TK edge to TF/TD (TK output, TF input)(1) 2 × tCPMCK 3+ (2 × tCPMCK) 2 × tCPMCK 3.3 + (2 × tCPMCK) ns SSC5 TF setup time before TK edge (TK input) – 0 – 0 – SSC6 TF hold time after TK edge (TK input) – tCPMCK – tCPMCK –  2017 Microchip Technology Inc. STTDLY = 0 START = 4, 5 or 7 DS60001476B-page 2519 SAMA5D2 SERIES Table 66-82: SSC0 IOSET1 Timings (Continued) Power supply Symbol Parameter SSC7 TK edge to TF/TD (TK input, TF input)(1) 1.8V Conditions – STTDLY = 0 START = 4, 5 or 7 3.3V Min Max Min Max 3.7 13 3.2 11.3 3.7 + (3 × tCPMCK) 13 + (3 × tCPMCK) 3.2 + (3 × tCPMCK) 11.3 + (3 × tCPMCK) Unit Receiver SSC8 RF/RD setup time before RK edge (RK input) – 0 – 0 – ns SSC9 RF/RD hold time after RK edge (RK input) – tCPMCK – tCPMCK – ns SSC10 RK edge to RF (RK input) (1) – 3.5 12 2.9 10.4 ns SSC11 RF/RD setup time before RK edge (RK output) – 13.6 - tCPMCK – 12 - tCPMCK – ns SSC12 RF/RD hold time after RK edge (RK output) – tCPMCK – tCPMCK – ns SSC13 RK edge to RF (RK output) (1) – 0 3 0 3.3 ns Note 1: For output signals (TF, TD, RF), minimum and maximum access times are defined. The minimum access time is the time between the TK (or RK) edge and the signal change. The maximum access time is the time between the TK edge and the signal stabilization. Figure 66-38 illustrates the minimum and maximum accesses for SSC0. The same applies for SSC1, SSC4, SSC7, SSC10 and SSC13. DS60001476B-page 2520  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-83: SSC0 IOSET2 Timings Power supply Symbol 1.8V Parameter Conditions Min 3.3V Max Min Max Unit Transmitter SSC0 TK edge to TF/TD (TK output, TF output) (1) – 0 3.4 0 3.7 ns SSC1 TK edge to TF/TD (TK input, TF output) (1) – 3.5 12.3 2.8 10.5 ns SSC2 TF setup time before TK edge (TK output) – 12 – 10.3 – ns SSC3 TF hold time after TK edge (TK output) – 0 – 0 – ns – 0 3.4 0 3.5 ns SSC4 TK edge to TF/TD (TK output, TF input) (1) 2 × tCPMCK 3.4 + (2 × tCPMCK) 2 × tCPMCK 3.5 + (2 × tCPMCK) ns SSC5 TF setup time before TK edge (TK input) – 0 – 0 – SSC6 TF hold time after TK edge (TK input) – tCPMCK – tCPMCK – – 3.6 12.3 3 10.4 SSC7 TK edge to TF/TD (TK input, TF input) (1) 3.6 + (3 × tCPMCK) 12.3 + (3 × tCPMCK) 3+ (3 × tCPMCK) 10.4 + (3 × tCPMCK) STTDLY = 0 START = 4, 5 or 7 STTDLY = 0 START = 4, 5 or 7 Receiver SSC8 RF/RD setup time before RK edge (RK input) – 0 – 0 – ns SSC9 RF/RD hold time after RK edge (RK input) – tCPMCK – tCPMCK – ns SSC10 RK edge to RF (RK input) (1) – 3.3 11.5 2.7 9.8 ns SSC11 RF/RD setup time before RK edge (RK output) – 13.8 - tCPMCK – 12.1 - tCPMCK – ns SSC12 RF/RD hold time after RK edge (RK output) – tCPMCK – tCPMCK – ns SSC13 RK edge to RF (RK output) (1) – 0 2.8 0 3.1 ns Note 1: For output signals (TF, TD, RF), minimum and maximum access times are defined. The minimum access time is the time between the TK (or RK) edge and the signal change. The maximum access time is the time between the TK edge and the signal stabilization. Figure 66-38 illustrates the minimum and maximum accesses for SSC0. The same applies for SSC1, SSC4, SSC7, SSC10 and SSC13.  2017 Microchip Technology Inc. DS60001476B-page 2521 SAMA5D2 SERIES Table 66-84: SSC1 IOSET1 Timings Power supply Symbol 1.8V Parameter Conditions Min 3.3V Max Min Max Unit Transmitter SSC0 TK edge to TF/TD (TK output, TF output) (1) – 0 2.6 0 2.7 ns SSC1 TK edge to TF/TD (TK input, TF output) (1) – 3.6 12.7 3 10.9 ns SSC2 TF setup time before TK edge (TK output) – 13.4 – 11.2 – ns SSC3 TF hold time after TK edge (TK output) – 0 – 0 – ns – 0 2.1 0 2 ns SSC4 TK edge to TF/TD (TK output, TF input) (1) 2 × tCPMCK 2.1 + (2 × tCPMCK) 2 × tCPMCK 2+ (2 × tCPMCK) ns SSC5 TF setup time before TK edge (TK input) – 0 – 0 – SSC6 TF hold time after TK edge (TK input) – tCPMCK – tCPMCK – – 3.6 12.2 3 10.2 SSC7 TK edge to TF/TD (TK input, TF input) (1) 3.6 + (3 × tCPMCK) 12.2 + (3 × tCPMCK) 3+ (3 × tCPMCK) 10.2 + (3 × tCPMCK) STTDLY = 0 START = 4, 5 or 7 STTDLY = 0 START = 4, 5 or 7 Receiver SSC8 RF/RD setup time before RK edge (RK input) – 0 – 0 – ns SSC9 RF/RD hold time after RK edge (RK input) – tCPMCK – tCPMCK – ns SSC10 RK edge to RF (RK input) (1) – 3.4 11.8 2.7 9.9 ns SSC11 RF/RD setup time before RK edge (RK output) – 12.2 - tCPMCK – 10.3 - tCPMCK – ns SSC12 RF/RD hold time after RK edge (RK output) – tCPMCK – tCPMCK – ns SSC13 RK edge to RF (RK output) (1) – 0 3.3 0 3.4 ns Note 1: For output signals (TF, TD, RF), minimum and maximum access times are defined. The minimum access time is the time between the TK (or RK) edge and the signal change. The maximum access time is the time between the TK edge and the signal stabilization. Figure 66-38 illustrates the minimum and maximum accesses for SSC0. The same applies for SSC1, SSC4, SSC7, SSC10 and SSC13. DS60001476B-page 2522  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-85: SSC1 IOSET2 Timings Power supply Symbol 1.8V Parameter Conditions Min 3.3V Max Min Max Unit Transmitter SSC0 TK edge to TF/TD (TK output, TF output) (1) – 0 2.5 0 2.6 ns SSC1 TK edge to TF/TD (TK input, TF output) (1) – 3.7 13 3.1 11.3 ns SSC2 TF setup time before TK edge (TK output) – 14.3 – 12.2 – ns SSC3 TF hold time after TK edge (TK output) – 0 – 0 – ns – 0 2.1 0 1.8 ns SSC4 TK edge to TF/TD (TK output, TF input) (1) 2 × tCPMCK 2.1 + (2 × tCPMCK) 2 × tCPMCK 1.8 + (2 × tCPMCK) ns SSC5 TF setup time before TK edge (TK input) – 0 – 0 – SSC6 TF hold time after TK edge (TK input) – tCPMCK – tCPMCK – – 3.7 12.6 3.1 10.4 SSC7 TK edge to TF/TD (TK input, TF input) (1) 3.7 + (3 × tCPMCK) 12.6 + (3 × tCPMCK) 3.1 + (3 × tCPMCK) 10.4 + (3 × tCPMCK) STTDLY = 0 START = 4, 5 or 7 STTDLY = 0 START = 4, 5 or 7 Receiver SSC8 RF/RD setup time before RK edge (RK input) – 0 – 0 – ns SSC9 RF/RD hold time after RK edge (RK input) – tCPMCK – tCPMCK – ns SSC10 RK edge to RF (RK input) (1) – 3.6 12.2 3 10.3 ns SSC11 RF/RD setup time before RK edge (RK output) – 12.3 - tCPMCK – 10.5 - tCPMCK – ns SSC12 RF/RD hold time after RK edge (RK output) – tCPMCK – tCPMCK – ns SSC13 RK edge to RF (RK output) (1) – 0 2.9 0 3.1 ns Note 1: For output signals (TF, TD, RF), minimum and maximum access times are defined. The minimum access time is the time between the TK (or RK) edge and the signal change. The maximum access time is the time between the TK edge and the signal stabilization. Figure 66-38 illustrates the minimum and maximum accesses for SSC0. The same applies for SSC1, SSC4, SSC7, SSC10 and SSC13.  2017 Microchip Technology Inc. DS60001476B-page 2523 SAMA5D2 SERIES Figure 66-38: Minimum and Maximum Access Time of Output Signals TK (CKI = 0) TK (CKI = 1) SSC0min SSC0max TF/TD DS60001476B-page 2524  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.22 PDMIC Timings 66.22.1 Timing Conditions Timings assuming capacitance loads are given in Table 66-86. Table 66-86: Capacitance Load Corner 66.22.2 Supply Max Min 3.3V 30 pF 5 pF 1.8V 20 pF 5 pF Timing Extraction Figure 66-39: PDMIC Timing Diagram PDMCLK PDM0 PDM1 PDMDAT0 PDM2 PDM3 PDMDAT0 Table 66-87: PDMIC IOSET1 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit PDMIC0 DATA setup time right 3.5 – 3.5 – ns PDMIC1 DATA hold time right 3.1 – 3.5 – ns PDMIC2 DATA setup time left 3.5 – 3.5 – ns PDMIC3 DATA hold time left 3.1 – 3.5 – ns Table 66-88: PDMIC IOSET2 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit PDMIC0 DATA setup time right 4.2 – 4.2 – ns PDMIC1 DATA hold time right 2 – 2 – ns PDMIC2 DATA setup time left 4.2 – 4.2 – ns PDMIC3 DATA hold time left 2 – 2 – ns  2017 Microchip Technology Inc. DS60001476B-page 2525 SAMA5D2 SERIES 66.23 I2SC Timings 66.23.1 Timing Conditions Timings assuming capacitance loads are given in Table 66-86. Table 66-89: Capacitance Load (I2SC0 and I2SC1) Corner 66.23.2 Supply Max Min 3.3V 30 pF 5 pF 1.8V 20 pF 5 pF Timing Extraction Table 66-90: I2SC0 IOSET1 Timings Power Supply Symbol 1.8V Parameter 3.3V Min Max Min Max Unit 12.5 – 10.8 – ns Master I2SC0 SDI Input setup time before SCK rises I2SC1 SDI Input hold time after SCK rises 0 – 0 – ns I2SC2 SCK falling to SDO valid 0 3.9 0 4 ns I2SC3 SCK falling to WS valid 0 2.7 0 3.1 ns Slave I2SC4 SDI Input setup time before SCK rises 1.1 – 1 – ns I2SC5 SDI Input hold time after SCK rises 1.3 – 1.2 – ns I2SC6 WS Input setup time before SCK rises 2 – 1.8 – ns I2SC7 WS Input hold time after SCK rises 0.9 – 0.8 – ns I2SC8 SCK falling to SDO valid 4.2 14 3.6 12 ns Table 66-91: I2SC0 IOSET2 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit 11.7 – 9.7 – ns Master I2SC0 SDI Input setup time before SCK rises I2SC1 SDI Input hold time after SCK rises 0 – 0 – ns I2SC2 SCK falling to SDO valid 0 3 0 3 ns I2SC3 SCK falling to WS valid 0.1 4.7 0.2 4.8 ns Slave I2SC4 SDI Input setup time before SCK rises 1.7 – 1.5 – ns I2SC5 SDI Input hold time after SCK rises 0.6 – 0.4 – ns I2SC6 WS Input setup time before SCK rises 3.6 – 3.4 – ns I2SC7 WS Input hold time after SCK rises 0.7 – 0.6 – ns DS60001476B-page 2526  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-91: I2SC0 IOSET2 Timings (Continued) Power Supply Symbol I2SC8 Table 66-92: 1.8V Parameter 3.3V Min Max Min Max Unit 3.7 12 3 10 ns SCK falling to SDO valid I2SC1 IOSET1 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit 13.1 – 11.4 – ns Master I2SC0 SDI Input setup time before SCK rises I2SC1 SDI Input hold time after SCK rises 0 – 0 – ns I2SC2 SCK falling to SDO valid 0 3.5 0 3.6 ns I2SC3 SCK falling to WS valid 0 2.9 0 3 ns 1.4 – 1.3 – ns 1 – 0.8 – ns Slave I2SC4 SDI Input setup time before SCK rises I2SC5 SDI Input hold time after SCK rises I2SC6 WS Input setup time before SCK rises 2.4 – 2.1 – ns I2SC7 WS Input hold time after SCK rises 0.8 – 0.7 – ns I2SC8 SCK falling to SDO valid 4.4 13.8 3.7 11.9 ns Table 66-93: I2SC1 IOSET2 Timings Power Supply Symbol Parameter 1.8V 3.3V Min Max Min Max Unit 12.9 – 11.2 – ns Master I2SC0 SDI Input setup time before SCK rises I2SC1 SDI Input hold time after SCK rises 0 – 0 – ns I2SC2 SCK falling to SDO valid 0 3.6 0 3.7 ns I2SC3 SCK falling to WS valid 0 2.9 0 3 ns Slave I2SC4 SDI Input setup time before SCK rises 1.1 – 1 – ns I2SC5 SDI Input hold time after SCK rises 1.2 – 1 – ns I2SC6 WS Input setup time before SCK rises 2.2 – 2 – ns I2SC7 WS Input hold time after SCK rises 0.9 – 0.7 – ns I2SC8 SCK falling to SDO valid 4.3 14 3.7 12 ns  2017 Microchip Technology Inc. DS60001476B-page 2527 SAMA5D2 SERIES 66.24 ISC Timings 66.24.1 Timing Conditions Timings assuming capacitance loads are given in Table 66-94. Table 66-94: Capacitance Load Corner 66.24.2 Supply Max Min 3.3V 30 pF 5 pF 1.8V 20 pF 5 pF Timing Extraction Figure 66-40: ISC Timing Diagram PIXCLK ISC5 DATA[7:0] Valid Data Valid Data ISC1 VSYNC HSYNC FIELD ISC2 Valid Control ISC3 Table 66-95: ISC4 ISC IOSET1 Timings Power Supply Symbol 1.8V 3.3V Parameter Min Max Min Max Unit ISC1 DATA setup time before PIXCLK rises 3.9 – 3.6 – ns ISC2 DATA hold time after PIXCLK rises 0.7 – 0.6 – ns ISC3 VSYNC/HSYNC/FIELD setup time before PIXCLK rises 4.4 – 4.2 – ns ISC4 CONTROL VSYNC/HSYNC/FIELD hold time after PIXCLK rises 0.4 – 0.3 – ns ISC5 PIXCLK frequency – 96 – 96 MHz Table 66-96: ISC IOSET2 Timings Power Supply Symbol 1.8V 3.3V Parameter Min Max Min Max Unit ISC1 DATA setup time before PIXCLK rises 4.3 – 4.2 – ns ISC2 DATA hold time after PIXCLK rises 0.5 – 0.3 – ns ISC3 VSYNC/HSYNC/FIELD setup time before PIXCLK rises 4.6 – 4.4 – ns ISC4 CONTROL VSYNC/HSYNC/FIELD hold time after PIXCLK rises 0.2 – 0 – ns ISC5 PIXCLK frequency – 96 – 96 MHz DS60001476B-page 2528  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 66-97: ISC IOSET3 Timings Power Supply Symbol 1.8V 3.3V Parameter Min Max Min Max Unit ISC1 DATA setup time before PIXCLK rises 4.6 – 4.2 – ns ISC2 DATA hold time after PIXCLK rises 0.5 – 0.4 – ns ISC3 VSYNC/HSYNC/FIELD setup time before PIXCLK rises 4.3 – 4 – ns ISC4 CONTROL VSYNC/HSYNC/FIELD hold time after PIXCLK rises 1.5 – 0.4 – ns ISC5 PIXCLK frequency – 96 – 96 MHz Table 66-98: ISC IOSET4 Timings Power Supply Symbol 1.8V 3.3V Parameter Min Max Min Max Unit ISC1 DATA setup time before PIXCLK rises 4.3 – 4 – ns ISC2 DATA hold time after PIXCLK rises 0.5 – 0.4 – ns ISC3 VSYNC/HSYNC/FIELD setup time before PIXCLK rises 4.2 – 4 – ns ISC4 CONTROL VSYNC/HSYNC/FIELD hold time after PIXCLK rises 0.5 – 0.3 – ns ISC5 PIXCLK frequency – 96 – 96 MHz 66.25 SDMMC Timings The Secure Digital Multimedia Card (SDMMC) Controller supports the embedded MultiMedia Card (e.MMC) Specification V4.51, the SD Memory Card Specification V3.0, and the SDIO V3.0 specification. It is compliant with the SD Host Controller Standard V3.0 specification. Features are different for the two instances of SDMMC: SDMMC0: SD 3.0, eMMC 4.51, 8 bits SDMMC1: SD 2.0, eMMC 4.41, 4 bits only In SDR104 mode (SD 3.0), SDMMC0 is limited to 120 MHz (instead of 208 MHz). In HS200 mode (eMMC 4.51), SDMMC0 is limited to 120 MHz (instead of 200 MHz).  2017 Microchip Technology Inc. DS60001476B-page 2529 SAMA5D2 SERIES 66.26 GMAC Timings 66.26.1 Timing Conditions Timings assuming a capacitance load on data and clock are given in Table 66-99. Table 66-99: Capacitance Load on Data, Clock Pads Corner 66.26.2 Supply Max Min 3.3V 20 pF 0 pF Timing Constraints Table 66-100: Ethernet MAC Signals Relative to GMDC Symbol Parameter EMAC1 EMAC2 EMAC3 Min Max Unit Setup for GMDIO from GMDC rising 10 – ns Hold for GMDIO from GMDC rising 10 – ns 0 300 ns GMDIO toggling from GMDC rising(1) Note 1: For Ethernet MAC output signals, minimum and maximum access time are defined. The minimum access time is the time between the GMDC rising edge and the signal change. The maximum access timing is the time between the GMDC rising edge and the signal stabilizes. Figure 66-41 illustrates minimum and maximum accesses for EMAC3. Figure 66-41: Minimum and Maximum Access Time of Ethernet MAC Output Signals GMDC EMAC1 EMAC2 EMAC3 max GMDIO EMAC4 EMAC5 EMAC3 min DS60001476B-page 2530  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.26.2.1 Ethernet MAC MII Mode Table 66-101: Ethernet MAC MII Specific Signals Symbol Parameter Min Max Unit EMAC4 Setup for GCOL from GTXCK rising 10 – ns EMAC5 Hold for GCOL from GTXCK rising 10 – ns EMAC6 Setup for GCRS from GTXCK rising 10 – ns EMAC7 Hold for GCRS from GTXCK rising 10 – ns EMAC8 GTXER toggling from GTXCK rising 10 25 ns EMAC9 GTXEN toggling from GTXCK rising 10 25 ns EMAC10 GTX toggling from GTXCK rising 10 25 ns EMAC11 Setup for GRX from GRXCK 10 – ns EMAC12 Hold for GRX from GRXCK 10 – ns EMAC13 Setup for GRXER from GRXCK 10 – ns EMAC14 Hold for GRXER from GRXCK 10 – ns EMAC15 Setup for GRXDV from GRXCK 10 – ns EMAC16 Hold for GRXDV from GRXCK 10 – ns  2017 Microchip Technology Inc. DS60001476B-page 2531 SAMA5D2 SERIES Figure 66-42: Ethernet MAC MII Mode GMDC EMAC1 EMAC3 EMAC2 GMDIO EMAC4 EMAC5 EMAC6 EMAC7 GCOL GCRS GTXCK EMAC8 GTXER EMAC9 GTXEN EMAC10 GTX[3:0] GRXCK EMAC11 EMAC12 GRX[3:0] EMAC13 EMAC14 EMAC15 EMAC16 GRXER GRXDV DS60001476B-page 2532  2017 Microchip Technology Inc. SAMA5D2 SERIES 66.26.2.2 Ethernet MAC RMII Mode Table 66-102: Ethernet MAC RMII Mode Symbol Parameter Min Max Unit EMAC21 GTXEN toggling from GREFCK rising 2 16 ns EMAC22 GTX toggling from GREFCK rising 2 16 ns EMAC23 Setup for GRX from GREFCK rising 4 – ns EMAC24 Hold for GRX from GREFCK rising 2 – ns EMAC25 Setup for GRXER from GREFCK rising 4 – ns EMAC26 Hold for GRXER from GREFCK rising 2 – ns EMAC27 Setup for GCRSDV from GREFCK rising 4 – ns EMAC28 Hold for GCRSDV from GREFCK rising 2 – ns Figure 66-43: Ethernet MAC RMII Timings GREFCK EMAC21 GTXEN EMAC22 GTX[1:0] EMAC23 EMAC24 GRX[1:0] EMAC25 EMAC26 EMAC27 EMAC28 GRXER GCRSDV  2017 Microchip Technology Inc. DS60001476B-page 2533 SAMA5D2 SERIES 67. Mechanical Characteristics 67.1 289-ball LFBGA Mechanical Characteristics Figure 67-1: 289-ball LFBGA Package Details Table 67-1: 289-ball LFBGA Package Characteristics Moisture Sensitivity Level Table 67-2: Device and 289-ball LFBGA Package Weight 445 Table 67-3: 3 mg Package Reference JEDEC Drawing Reference NA J-STD-609 Classification e8 Table 67-4: 289-ball LFBGA Package Information Ball Land 0.450 mm +/-0.05 Nominal Ball Diameter 0.4 mm Solder Mask Opening 0.350 mm +/-0.05 Solder Mask Definition SMD Solder OSP DS60001476B-page 2534  2017 Microchip Technology Inc. SAMA5D2 SERIES 67.2 256-ball TFBGA Mechanical Characteristics Figure 67-2: 256-ball TFBGA Package Details Table 67-5: 256-ball TFBGA Package Characteristics Moisture Sensitivity Level Table 67-6: Device and 256-ball TFBGA Package Weight 110.3 Table 67-7: 3 mg Package Reference JEDEC Drawing Reference NA J-STD-609 Classification e8 Table 67-8: 256-ball TFBGA Package Information Ball Land 0.350 mm +/-0.05 Nominal Ball Diameter 0.25 mm Solder Mask Opening 0.250 mm +/-0.05 Solder Mask Definition SMD Solder OSP  2017 Microchip Technology Inc. DS60001476B-page 2535 SAMA5D2 SERIES 67.3 196-ball TFBGA Mechanical Characteristics Figure 67-3: 196-ball TFBGA Package Details Table 67-9: 196-ball TFBGA Package Characteristics Moisture Sensitivity Level Table 67-10: Device and 196-ball TFBGA Package Weight 234.2 Table 67-11: 3 mg Package Reference JEDEC Drawing Reference NA J-STD-609 Classification e8 Table 67-12: 196-ball TFBGA Package Information Ball Land 0.350 mm +/-0.05 Nominal Ball Diameter 0.3 mm Solder Mask Opening 0.275 mm +/-0.30 Solder Mask Definition SMD Solder OSP DS60001476B-page 2536  2017 Microchip Technology Inc. SAMA5D2 SERIES 68. Schematic Checklist The schematic checklist provides the user with the requirements regarding the different pin connections that must be considered before starting any new board design as well as information on the minimum hardware resources required to quickly develop an application with the SAMA5D2. It does not consider PCB layout constraints. It also provides recommendations regarding low-power design constraints to minimize power consumption. This information is not intended to be exhaustive. Its objective is to cover as many configurations of use as possible. The checklist contains a column for use by designers, making it easy to track and verify each line item.  2017 Microchip Technology Inc. DS60001476B-page 2537 SAMA5D2 SERIES 68.1 Power Supply CAUTION: The board design must comply with the powerup and powerdown sequence guidelines provided in the datasheet to guarantee reliable operation of the device. Figure 68-1: 1.2V, 1.35V/1.5V, 2V, 2.5V, 3.3V Power Supplies Schematics(1) LDO/BATTERY VDDBU 100 nF 3.3V GNDBU VDDISC PMIC 100 nF DC/DC GNDISC VDDSDMMC 100 nF 3.3V GNDSDMMC VDDIOP 100 nF GNDIOP VDDHSIC 100 nF GNDUTMIC VDDUTMIC DC/DC 4.7 μF 100 nF 10 μH GNDUTMIC 1.2V VDDPLLA 1Ω 100 nF 5V 4.7 μF GNDPLLA VDDCORE 20 μF 100 nF DC/DC GNDCORE VDDIODDR 1.35V 20 μF 100 nF SAMA5D2 GNDIODDR LDO VDDFUSE 100 nF 2.5V GNDFUSE LDO VDDANA 100 nF 3.3V GNDANA VDDUTMII 100 nF GNDUTMII 10 μH VDDAUDIOPLL 4.7 μF 100 nF GNDAUDIOPLL GNDDPLL 10 μH VDDOSC 1Ω 100 nF 4.7 μF GNDOSC Note 1: These values are given only as typical examples. DS60001476B-page 2538  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 68-1: Signal Name Power Supply Connections Recommended Pin Connection 1.1V to 1.32V VDDCORE Decoupling/Filtering capacitors (10 µF and 100 nF)(1)(2) Description Powers the core Supply ripple must not exceed 10 mVrms. Powers the PLLA cell. VDDPLLA 1.1V to 1.32V Decoupling capacitor (100 nF)(1)(2) The VDDPLLA power supply pin draws small current, but it is noise-sensitive. Care must be taken in VDDPLLA power supply routing, decoupling and also on bypass capacitors. Supply ripple must not exceed 10 mVrms. VDDIODDR VDDISC VDDIOP0,1,2 VDDBU 1.14V to 1.30V Powers LPDDR2-LPDDR3 interface 1.283V to 1.45V Powers DDR3L interface 1.425V to 1.575V Powers DDR3 interface 1.7V to 1.95V Powers LPDDR1-DDR2 interface Decoupling/Filtering capacitors (10 µF and 100 nF)(1)(2) Decoupling/filtering capacitors must be added to improve startup stability and reduce source voltage drop. 1.65V to 3.6V Decoupling capacitor (100 nF)(1)(2) 1.65V to 3.6V Decoupling capacitors (100 nF)(1)(2) Powers the ISC Interface I/O lines. Powers the peripherals I/O lines. Decoupling/filtering capacitors must be added to improve startup stability and reduce source voltage drop. 1.65V to 3.6V Powers the Slow Clock oscillator, the internal 64 kHz RC and a part of the System Controller. Decoupling capacitor (100 nF)(1)(2) Must be established first. Supply ripple must not exceed 30 mVrms. VDDUTMIC VDDUTMII VDDHSIC 1.1V to 1.32V Decoupling capacitors (100 nF)(1)(2) 3.0V to 3.6V Decoupling capacitor (100 nF)(1)(2) 1.1V to 1.3V Decoupling capacitors (100 nF)(1)(2) DC Supply UTMI Phy (Core) and PLL UTMI Decoupling/filtering capacitors must be added to improve startup stability and reduce source voltage drop. DC Supply UTMI Phy (Interface) Decoupling/filtering capacitors must be added to improve startup stability and reduce source voltage drop. DC Supply HSIC Phy Powers the main oscillator cell. VDDOSC 1.65V to 3.6V Decoupling/Filtering RLC circuit(1) The VDDOSC power supply pin is noise-sensitive. Care must be taken in VDDOSC power supply routing, decoupling and also on bypass capacitors. Supply ripple must not exceed 30 mVrms. VDDSDMMC VDDANA 1.65V to 3.6V Decoupling capacitor (100 nF)(1)(2) 1.65V to 3.6V Decoupling capacitor (100 nF)(1)(2)  2017 Microchip Technology Inc. Powers the SDMMC I/O lines. Powers the analog parts. DS60001476B-page 2539 SAMA5D2 SERIES Table 68-1: Signal Name VDDFUSE VDDAUDIOPLL Power Supply Connections (Continued) Recommended Pin Connection Description 2.25V to 2.75V Powers the fuse box for programming. Decoupling capacitor (100 nF)(1)(2) VDDFUSE must not be left floating. 3.0V to 3.6V Decoupling capacitor (100 nF)(1)(2) Powers the Audio PLL. GNDCORE pins are common to VDDCORE pins. GNDCORE Core Chip ground GNDPLLA PLLA cell ground GNDPLL pin should be connected as shortly as possible to the system ground plane. GNDIODDR DDR2/LPDDR1/LPDDR2/DDR3/LPDDR3 interface I/O lines ground GNDIODDR pins should be connected as shortly as possible to the system ground plane. GNDCORE pins should be connected as shortly as possible to the system ground plane. GNDPLL pin is provided for VDDPLLA pins. GNDISC pins are common to VDDISC pins. GNDISC VDDISC ground GNDIOP0,1,2 Peripherals and ISC I/O lines ground GNDBU Backup ground GNDISC pins should be connected as shortly as possible to the system ground plane. GNDIOPx pins are common to VDDIOPx pins. GNDIOP pins should be connected as shortly as possible to the system ground plane. GNDBU pin is provided for VDDBU pins. GNDBU pin should be connected as shortly as possible to the system ground plane. GNDUTMIC pins are common to VDDUTMIC and VDDHSIC pins. GNDUTMIC VDDUTMIC and VDDHSIC ground GNDUTMII UDPHS and UHPHS UTMI+ Core and Interface, and PLL UTMI ground GNDOSC Oscillator ground GNDSDMMC SDMMC ground GNDUTMIC pins should be connected as shortly as possible to the system ground plane. GNDUTMII pins are common to VDDUTMII and VDDUTMIC pins. GNDUTMII pins should be connected as shortly as possible to the system ground plane. GNDOSC pin is provided for VDDOSC pins. GNDOSC pin should be connected as shortly as possible to the system ground plane. SDMMC pins are common to VDDSDMMC pins. GNDSDMMC pins should be connected as shortly as possible to the system ground plane. GNDANA pins are common to VDDANA pins. GNDANA Analog ground GNDFUSE Fuse box ground GNDANA pins should be connected as shortly as possible to the system ground plane. GNDFUSE pins are common to VDDFUSE pins. DS60001476B-page 2540 GNDFUSE pins should be connected as shortly as possible to the system ground plane.  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 68-1: Signal Name GNDAUDIOPLL GNDDPLL Power Supply Connections (Continued) Recommended Pin Connection Description GNDAUDIOPLL and GNDDPLL pins are common to VDDAUDIOPLL. Audio PLL ground GNDAUDIOPLL and GNDDPLL pins should be connected as shortly as possible to the system ground plane. Note 1: These values are given only as typical examples. 2: Decoupling capacitors must be connected as close as possible to the microprocessor and on each relevant pin. 100nF VDDCORE 100nF VDDCORE 100nF VDDCORE GND For more information, see Table 66-41 “VDDCORE Power-On Reset Characteristics”. 68.2 Power-On Reset The SAMA5D2 embeds several Power-On Resets (PORs) to ensure the power supply is established when the reset is released. These PORs are dedicated to VDDBU, VDDIOP and VDDCORE respectively.  2017 Microchip Technology Inc. DS60001476B-page 2541 SAMA5D2 SERIES 68.3 Clock, Oscillator and PLL Table 68-2:  Clock, Oscillator and PLL Connections Signal Name Recommended Pin Connection Description Crystal Load Capacitance to check (CCRYSTAL) SAMA5D2 Crystals between 8 and 24 MHz XIN XIN XOUT USB High Speed (not Full Speed) 12 MHz Host and Device peripherals need a 12 MHz clock. Main Oscillator in Normal Mode XOUT GNDOSC CCRYSTAL Capacitors on XIN and XOUT (Crystal Load Capacitance dependent) CLEXT CLEXT Refer to Section 66. “Electrical Characteristics”. XIN XIN: external clock source XOUT XOUT: can be left unconnected Square wave signal, high level = VDDOSC External clock source up to 50 MHz 12 MHz Main Oscillator in Bypass Mode USB High speed (not Full Speed) Duty Cycle: 40 to 60% Host and Device peripherals need a 12 MHz clock. Refer to Section 66. “Electrical Characteristics”. XIN XIN: can be left unconnected XOUT XOUT: can be left unconnected Typical nominal frequency 12 MHz (Internal 12 MHz RC Oscillator) 12 MHz Main Oscillator Disabled USB High Speed (not Full Speed) Duty Cycle: 45 to 55% Host and Device peripherals need a 12 MHz clock. Refer to Section 66. “Electrical Characteristics” DS60001476B-page 2542  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 68-2:  Clock, Oscillator and PLL Connections (Continued) Signal Name Recommended Pin Connection Description Crystal load capacitance to check (CCRYSTAL32) SAMA5D2 XIN32 XIN32 32.768 kHz Crystal XOUT32 GNDBU XOUT32 Capacitors on XIN32 and XOUT32 Slow Clock Oscillator C CRYSTAL32 (Crystal Load Capacitance dependent) CLEXT32 CLEXT32 Refer to Section 66. “Electrical Characteristics”. XIN32 Square wave signal, high level = VDDBU XOUT32 Slow Clock Oscillator in Bypass Mode XIN32: external clock source External clock source up to 44 kHz XOUT32: can be left unconnected Duty Cycle: 40 to 60% Refer to Section 66. “Electrical Characteristics”. XIN32 XIN32: can be left unconnected Typical nominal frequency 32 kHz (internal 64 kHz RC oscillator) XOUT32: can be left unconnected Duty Cycle: 45 to 55% XOUT32 Slow Clock Oscillator Disabled Refer to Section 66. “Electrical Characteristics”. Bias Voltage Reference for USB To reduce as much as possible the noise on VBG pin, check the layout considerations below: - VBG path as short as possible - Ground connection to GNDUTMII VBG 0.9–1.1V(2) 5K62 ± 1% W VBG 10 pF GNDUTMII VBG can be left unconnected if USB is not used. Refer to Section 4. “Signal Description”.  2017 Microchip Technology Inc. DS60001476B-page 2543 SAMA5D2 SERIES 68.3.1 How to Define the Oscillator Load Capacitance The load capacitance is the equivalent capacitor value that circuit must “show” to the crystal in order to oscillate at the target frequency. The load is set by two external capacitors placed on each side of the crystal to gnd. The load of the crystal is the external capacitor value divided by two as it is represented in the figure below (in this case 2 * CLOAD includes ALL the parasitics capacitors). AIO33XIN AIO33XIN AIO33XIN AIO33XIN The CLOAD value must be specified by the crystal manufacturer. Parameters such as the parasitics of internal ASIC due to routing, IO pads, package and board must be calculated in order to reach the crystal load (refer to Section 66.7 “Oscillator Characteristics” to Section 66.7.3 “32.768 kHz Crystal Oscillator Characteristics”). The external capacitor value can be determined by using the following formula: CEXT = (2 * CLOAD) - CBOARD - CPACKAGE - CPAD - CROUTING - (CPARA * 2) where: - CEXT: external capacitor value which must be soldered from aio33xin to gnd and from aio33xout to gnd CLOAD: crystal-targeted load. Refer to CLOAD parameter in the crystal electrical specification. CBOARD: external calculated (or measured) value due to board parasitics CPACKAGE: parasitics capacitance due to package and bonding CPAD: parasitics capacitance of the I/O pad used for internal connection CROUTING: parasitics due to internal chip routing CPARA: internal load parasitic due to internal structure. Refer to CPARA parameter in Section 66.7 “Oscillator Characteristics”. Table 68-3: Main Oscillator Load Capacitance Oscillator 12 MHz < Frequency < 24 MHz Frequency = 24 MHz Main Oscillator 12.5 pF < CLOAD < 17.5 pF 10 pF < CLOAD < 12.5 pF Table 68-4: 32.768 kHz Oscillator Load Capacitance Oscillator Frequency 32.768 kHz Oscillator 6 pF < CLOAD < 12.5 pF In our case, the minimum targeted load for the 32.768 kHz oscillator is 6 pF. The typical parasitic load of the oscillator is 0.5 pF. If routed + externals capacitances (package + board + external soldered + internal connection and internal pads parasitics) are about 1 pF, the external load must be 6 pF – 0.5 pF - 1 pF = 4.5 pF, which means that 9 pF is the target value (9 pF from aio33xin to gnd and 11 pF from aio33xout to gnd). If a 12.5 pF load is targeted, the externals capacitances must be 12.5 pF - 0.5 pF - 1 pF = 11 pF, which is 22 pF (22 pF from aio33xin to gnd and 22 pF from aio33xout to gnd). Example 1: Crystal CLOAD= 6 pF Cl = 6 pF then Cxin_gnd_total = 12 pF and Cxout_gnd_total = 12 pF 9 pF external capacitor needed DS60001476B-page 2544  2017 Microchip Technology Inc. SAMA5D2 SERIES Example 2: Crystal CLOAD = 12.5 pF Cl = 12.5 pF then Cxin_gnd = 25 pF and Cxout_gnd = 25 pF 22 pF external capacitor needed 68.4 ICE and JTAG Table 68-5:  ICE and JTAG Connections(1) Signal Name Recommended Pin Connection Pull-up (100 TCK kΩ)(2) If Debug mode is not required, this pin can be used as GPIO. Pull-up (100 kΩ)(2) TMS If Debug mode is not required, this pin can be used as GPIO. Pull-up (100 kΩ)(2) TDI If Debug mode is not required, this pin can be used as GPIO. Description This pin is a Schmitt trigger input. Internal pull-up resistor to VDDIOP (100 kΩ). This pin is a Schmitt trigger input. Internal pull-up resistor to VDDIOP (100 kΩ). This pin is a Schmitt trigger input. Internal pull-up resistor to VDDIOP (100 kΩ). Floating TDO If Debug mode is not required, this pin can be used as GPIO. Refer to the pin description section. NTRST JTAGSEL If Debug mode is not required, this pin can be used as GPIO. In harsh environments(3), it is strongly recommended to tie this pin to GNDBU if not used or to add an external low-value resistor (such as 1 kΩ). Output driven at up to VDDIOP. This pin is a Schmitt trigger input. Internal pull-up resistor to VDDIOP (100 kΩ). Internal pull-down resistor to GNDBU (15 kΩ). Must be tied to VDDBU to enter JTAG Boundary Scan. Note 1: It is recommended to establish accessibility to a JTAG connector for debug in any case. 2: These values are given only as typical examples. 3: In a well-shielded environment subject to low magnetic and electric field interference, the pin may be left unconnected. In noisy environments, a connection to ground is recommended.  2017 Microchip Technology Inc. DS60001476B-page 2545 SAMA5D2 SERIES 68.5 Reset and Test Table 68-6:  Reset and Test Connections Signal Name Recommended Pin Connection Description Application-dependent NRST Can be connected to a pushbutton for hardware reset. In applications with a storage element on VDDBU (battery, supercapacitor, etc.), NRST must be tied to an non-permanent supply (satisfying VIH conditions on NRST) and not to VDDBU. Typically, this may be the application’s primary 3.3V supply (VDDIOP0, VDDIOP1 or any other). The recommended pull-up value is 10 kOhms minimum. Doing so, the NRST level is 'L' when the non-permanent supply is removed. On the contrary, if this pin is tied to VDDBU: NRST pin is a Schmitt trigger input. No internal pull-up resistor. • the circuit driving this pin low may not be operational when the input power of the application is removed. Therefore the processor may not be properly reset during powerup or powerdown phases, • a leakage path from VDDBU to the application's input power may be created when this input power is removed. (This may be for example through a clampling diode that may be present on an external integrated circuit driving NRST.) TST In harsh environments(1), it is strongly recommended to tie this pin to GNDBU to add an external low-value resistor (such as 10 kΩ). This pin is a Schmitt trigger input. Internal pull-down resistor to GNDBU (15 kΩ). Note 1: In a well-shielded environment subject to low magnetic and electric field interference, the pin may be left unconnected. In noisy environments, a connection to ground is recommended. DS60001476B-page 2546  2017 Microchip Technology Inc. SAMA5D2 SERIES 68.6 Shutdown/Wakeup Logic Table 68-7:  Shutdown/Wakeup Logic Connections Signal Name Recommended Pin Connection Description Application-dependent A typical application connects pin SHDN to the shutdown input of the DC/DC Converter providing the main power supplies. SHDN WKUP 68.7 Signal Name Recommended Pin Connection Application-dependent PCx To reduce power consumption if not used, the relevant PIO can be configured as an output, driven at ‘0’ with internal pull-up disabled. Analog-to-Digital Converter (ADC) Table 68-9: ADC Connections Signal Name ADVREF Recommended Pin Connection Description 3.3 V to VDDANA ADVREF is a pure analog input. Decoupling/filtering capacitors To reduce power consumption if the ADC is not used, connect ADVREF to GNDANA. Application-dependent External Bus Interface (EBI) Table 68-10:  In Section 6. “Package and Pinout”, refer to the column ‘Reset State’ of the Pin Description table. Schmitt trigger on all inputs. PDx 68.9 Description All PIOs are pulled up inputs (100 kΩ) at reset except those which are multiplexed with the Address Bus signals that require to be enabled as peripherals: PBx  This pin is an input only. WKUP behavior can be configured through the Shutdown Controller (SHDWC). PIO Connections PAx 68.8 SHDN pin is driven low to GNDBU by the Shutdown Controller (SHDWC). Parallel Input/Output (PIO) Table 68-8:  0 V to VDDBU This pin is a push-pull output. EBI Connections Signal Name Recommended Pin Connection D0–D15 Application-dependent A0–A25 Application-dependent Description Data Bus (D0 to D15) All data lines are pulled up inputs at reset. Address Bus (A0 to A25) All address lines are pulled up inputs at reset. Table 68-11 and Table 68-12 detail the connections to be applied between the EBI pins and the external devices for each memory controller.  2017 Microchip Technology Inc. DS60001476B-page 2547 SAMA5D2 SERIES Table 68-11: EBI Pins and External Static Devices Connections Pins of the Interfaced Device Signals: EBI_ 8-bit Static Device 16-bit Static Device 2 x 8-bit Static Devices Controller SMC (Static Memory Controller) D0–D7 D0–D7 D0–D7 D0–D7 D8–D15 – D8–D15 D8–D15 A0/NBS0 A0 – NLB A1 A1 A0 A0 A2–A22 A[2:22] A[1:21] A[1:21] A23–A25 A[23:25] A[22:24] A[22:24] NCS0 CS CS CS NCS1 CS CS CS NCS2 CS CS CS NCS3/NANDCS CS CS CS NRD/NANDOE OE OE OE NWE/NWR0/NANDWE NWR1/NBS1 WE WE (1) WE WE(1) – NUB Note 1: NWR0 enables lower byte writes. NWR1 enables upper byte writes. Table 68-12: EBI Pins and NAND Flash Device Connections Signals: EBI_ Pins of the Interfaced Device 8-bit NAND Flash Controller 16-bit NAND Flash NFC (NAND Flash Controller) D0–D7 NFD0–NFD7 NFD0–NFD7 D8–D15 – NFD8–NFD15 A21/NANDALE ALE ALE A22/NANDCLE CLE CLE NRD/NANDOE RE RE NWE/NWR0/NANDWE WE WE NCS3/NANDCS CE CE NANDRDY R/B R/B A0/NBS0 – – A1–A20 – – A23–A25 – – NWR1/NBS1 – – NCS0 – – NCS1 – – DS60001476B-page 2548  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 68-12: EBI Pins and NAND Flash Device Connections (Continued) Pins of the Interfaced Device Signals: EBI_ 8-bit NAND Flash Controller 16-bit NAND Flash NFC (NAND Flash Controller) NCS2 – – NWAIT – – 68.10 USB High-Speed Host Port (UHPHS) / USB High-Speed Device Port (UDPHS) Table 68-13: UHPHS/UDPHS Connections Signal Name Recommended Pin Connection Description Application-dependent(2)(3) Pull-down output at reset Application-dependent(2) Pull-down output at reset (2) Pull-down output at reset (1) UHPHS UDPHS HSIC HHSDPA/DHSDPB HHSDMA/DHSDMB(1) HHSDP/HHSDM HHSTROBE/HHDATA Application-dependent Note 1: UDPHS shares Port A with UHPHS. 2: Example of a USB High Speed Host connection, refer to section Section 42. “USB Host High Speed Port (UHPHS)”. "A" Receptacle 1 = VBUS 2 = D3 = D+ 4 = GND +5V PIO (VBUS ENABLE) 5 SH1 A VBUS DM DP GND 1 2 3 4 HHSDM/HFSDM 90 ohms differential trace impedance HHSDP/HFSDP SH2 6 Shell = Shield 5K62 ± 1% W VBG 10 pF GNDUTMII 3: Typical USB High Speed Device connection, refer to Section 41. “USB High Speed Device Port (UDPHS)”.  2017 Microchip Technology Inc. DS60001476B-page 2549 SAMA5D2 SERIES "B" Receptacle 1 = VBUS 2 = D3 = D+ 4 = GND 15k (1) PIO (VBUS DETECT) 5 22k (1) CRPB1–10 μF SH1 VBUS DM DP GND 1 2 3 4 A DHSDM/DFSDM 90 ohms differential trace impedance DHSDP/DFSDP SH2 6 Shell = Shield 5K62 ± 1%Ω VBG 10 pF GNDUTMII Note 1: The values shown on the 22 kΩ and 15 kΩ resistors are only valid with 3.3-V supplied PIOs. 68.11 Boot Program Hardware Constraints Refer to Section 16. “Standard Boot Strategies” for more details on the boot program. 68.12 Layout and Design Constraints Note: 68.12.1 All PIOs shared, multiplexed, connected to various components and connectors must be connected through serial resistors 22R and 39R for clock signals. The resistors must be populated as close as possible to the SAMA5D2. General Considerations This chapter provides routing guidelines for layout and design of a printed circuit board using high-speed interfaces, Serial, Ethernet and USB 2.0. The signal integrity rules for high-speed interfaces need to be considered. In fact, it is highly recommended that the board design be simulated to determine optimum layout for signal integrity and quality. Keep in mind that this document can only highlight the most important issues that should be considered when designing the SAMA5D2 board. The designer has to take into account the corresponding information (specification, design guidelines, etc.) contained in the documentation of all other devices that are to be implemented on board. 68.12.2 Considerations for High-Speed Differential Interfaces The following is a list of suggestions for designing with high-speed differential signals. This should help implementing these interfaces while providing maximum SAMA5D2 board performance. • Use controlled impedance PCB traces that match the specified differential impedance. • Keep the trace lengths of the differential signal pairs as short as possible. • The differential signal pair traces should be trace-length matched and the maximum trace-length mismatch should not exceed the specified values. Match each differential pair per segment. • Maintain parallelism and symmetry between differential signals with the trace spacing needed to achieve the specified differential impedance. • Maintain maximum possible separation between the differential pairs and any high-speed clocks/periodic signals (CMOS/TTL) and any connector leaving the PCB (such as I/O connectors, control and signal headers, or power connectors). • Route differential signals on the signal layer nearest to the ground plane using a minimum of vias and corners. This will reduce signal reflections and impedance changes. Use GND stitching vias when changing layers. • It is best to put CMOS/TTL and differential signals on different layers which should be isolated by the power and ground planes. • Avoid tight bends. When it becomes necessary to turn 90°, use two 45° turns or an arc instead of making a single 90° turn. • Do not route traces under crystals, crystal oscillators, clock synthetizers, magnetic devices or ICs that use, and/or generate, clocks. • Stubs on differential signals should be avoided due to the fact that stubs cause signal reflections and affect signal quality. • Keep the length of high-speed clock and periodic signal traces that run parallel to high-speed signal lines at a minimum to avoid DS60001476B-page 2550  2017 Microchip Technology Inc. SAMA5D2 SERIES crosstalk. Based on EMI testing experience, the minimum suggested spacing to clock signals is 50 mil. • Use a minimum of 20 mil spacing between the differential signal pairs and other signal traces for optimal signal quality. This helps to prevent crosstalk. • Route all traces over continuous planes (VCC or GND) with no interruptions. • Avoid crossing over anti-etch if at all possible. Crossing over anti-etch (split planes) increases inductance and radiation levels by forcing a greater loop area. 68.12.3 DDR Layout and Design Considerations Refer to the document “SAMA5D2 Layout Recommendations”, document no. 44041. 68.12.4 e.MMC routing Refer to the Micron Technical Note TN-FC-35: e•MMC PCB Design Guide. This document is intended as guide for PCB designers using Micron e•MMC devices and discusses the primary issues affecting design and layout. 68.12.5 USB Trace Routing Guidelines • Maintain parallelism between USB differential signals with the trace spacing needed to achieve 90-ohm differential impedance. Deviations will normally occur due to package breakout and routing to connector pins. Just ensure the amount and lengths of the deviations are kept to the minimum possible. • Use an impedance calculator to determine the trace width and spacing required for the specific board stack-up being used. Example: Layer Stacking, 7.5-mil traces with 7.5-mil spacing results in approximately 90-ohm differential trace impedance. • Minimize the length of high-speed clock and periodic signal traces that run parallel to high-speed USB signal lines, to minimize crosstalk. Based on EMI testing experience, the minimum suggested spacing to clock signals is 50 mils. • Based on simulation data, use 20-mil minimum spacing between high-speed USB signal pairs and other signal traces for optimal signal quality. This helps to prevent crosstalk. Table 68-14: USB Trace Routing Guidelines Parameter Trace Routing 14.0 inches Signal length allowance for the SAMA5D2 Valid for a damping value of the PCB trace of 0.11 dB/ inch @ 0.4 GHz (common value for FR-4 based material) Differential impedance 90 ohms +/-15% Single-ended impedance 45 ohms +/-10% Trace width (W) 5 mils (microstrip routing) Spacing between differential pairs (intra-pair) 6 mils (microstrip routing) Spacing between pairs (inter-pair) Min. 20 mils Spacing between differential pairs and high-speed periodic signals Min. 50 mils Spacing between differential pairs and low-speed nonperiodic signals Min. 20 mils Length matching between differential pairs (intra-pair) 150 mils Reference plane GND referenced preferred Spacing from edge of plane Min. 40 mils Vias usage Try to minimize the number of vias 68.12.6 QSPI Pull-up Resistors The ROM code removes the internal pull-up resistors when it configures PIO controller to mux the QSPI controller I/O lines. Therefore the probing step may fail if the Quad I/O mode of the memory has not been enabled yet and if this memory does not embed internal pullup resistor on #HOLD or #RESET pin.  2017 Microchip Technology Inc. DS60001476B-page 2551 SAMA5D2 SERIES For this reason, it is recommended to add external pull-up resistors if needed on the four I/O data lines MOSI/IO0, MISO/IO1, #WP/IO2 and #HOLD/IO3. Another solution is to update the Quad Enable non-volatile bit in the relevant register to reassign #WP and #HOLD/#RESET pins to functions IO2 and IO3. 68.12.7 Considerations for PTC Interface Particular care must be taken during the layout of the PTC interface for the signals PTC_Xm and PTC_Yn. The PTC Debug Port (PTC_PORT_x) can be routed normally. X-Lines (PTC_Xm) • • • • • Must be routed on TOP and BOTTOM side as often as possible. Can be routed in inner layer when necessary. A maximum of 4 vias per line is allowed. Is possible to cross the lines if necessary. X-lines must be as short as possible with a maximum intrinsic capacitance of 15pF. Y-Lines (PTC_Yn) • • • • Must be routed on TOP side only. Only one via per line is allowed. Never cross the Y-lines. Y-lines must be as short as possible with a maximum intrinsic capacitance of 15pF. Respect an absolute clearance in PTC routing area. No ground path or plane, no power path or plane, and no signals except other PTC lines respecting the recommendations above should overlay the PTC signals in another PCB layer. DS60001476B-page 2552  2017 Microchip Technology Inc. SAMA5D2 SERIES 69. Marking All devices are marked with the company logo and the ordering code. Additional marking is as follows: YYWWC V XXXXXXX ARM where • • • • • “YY”: Manufactory year “WW”: Manufactory week “C”: Assembly country code (optional) “V”: Revision “XXXXXXX”: Lot number  2017 Microchip Technology Inc. DS60001476B-page 2553 SAMA5D2 SERIES 70. Ordering Information Table 70-1: SAMA5D2 Ordering Information Ordering Code MRL Package Carrier Type ATSAMA5D21C-CU C Tray ATSAMA5D21C-CUR C Tape and reel ATSAMA5D22C-CN C Tray ATSAMA5D22C-CNR C Tape and reel ATSAMA5D22C-CU C Operating Temperature Range -40°C to 85°C -40°C to 105°C Tray -40°C to 85°C TFBGA196 ATSAMA5D22C-CUR C Tape and reel ATSAMA5D23C-CN C Tray ATSAMA5D23C-CNR C Tape and reel ATSAMA5D23C-CU C Tray ATSAMA5D23C-CUR C Tape and reel ATSAMA5D24C-CU C -40°C to 105°C -40°C to 85°C Tray TFBGA256 -40°C to 85°C ATSAMA5D24C-CUR C Tape and reel ATSAMA5D26C-CN C Tray ATSAMA5D26C-CNR C Tape and reel ATSAMA5D26C-CU C Tray ATSAMA5D26C-CUR C Tape and reel ATSAMA5D27C-CN C Tray ATSAMA5D27C-CNR C Tape and reel ATSAMA5D27C-CU C Tray ATSAMA5D27C-CUR C Tape and reel ATSAMA5D28C-CN C Tray ATSAMA5D28C-CNR C Tape and reel ATSAMA5D28C-CU C Tray ATSAMA5D28C-CUR C Tape and reel ATSAMA5D21B-CU B Tray ATSAMA5D21B-CUR B Tape and reel ATSAMA5D22B-CN B Tray ATSAMA5D22B-CNR B Tape and reel ATSAMA5D22B-CU B -40°C to 105°C -40°C to 85°C -40°C to 105°C LFBGA289 -40°C to 85°C -40°C to 105°C -40°C to 85°C -40°C to 85°C -40°C to 105°C Tray -40°C to 85°C TFBGA196 ATSAMA5D22B-CUR B Tape and reel ATSAMA5D23B-CN B Tray ATSAMA5D23B-CNR B Tape and reel ATSAMA5D23B-CU B Tray ATSAMA5D23B-CUR B Tape and reel -40°C to 105°C -40°C to 85°C DS60001476B-page 2554  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 70-1: SAMA5D2 Ordering Information Ordering Code ATSAMA5D24B-CU MRL Package B Carrier Type Operating Temperature Range Tray TFBGA256 -40°C to 85°C ATSAMA5D24B-CUR B Tape and reel ATSAMA5D26B-CN B Tray ATSAMA5D26B-CNR B Tape and reel ATSAMA5D26B-CU B Tray ATSAMA5D26B-CUR B Tape and reel ATSAMA5D27B-CN B Tray ATSAMA5D27B-CNR B Tape and reel ATSAMA5D27B-CU B Tray ATSAMA5D27B-CUR B Tape and reel ATSAMA5D28B-CN B Tray ATSAMA5D28B-CNR B Tape and reel ATSAMA5D28B-CU B Tray ATSAMA5D28B-CUR B Tape and reel ATSAMA5D22A-CU A -40°C to 105°C -40°C to 85°C -40°C to 105°C LFBGA289 -40°C to 85°C -40°C to 105°C -40°C to 85°C Tray TFBGA196 ATSAMA5D22A-CUR A ATSAMA5D24A-CU A Tape and reel Tray TFBGA256 ATSAMA5D24A-CUR A Tape and reel ATSAMA5D27A-CU A Tray ATSAMA5D27A-CUR A ATSAMA5D28A-CU A  2017 Microchip Technology Inc. LFBGA289 -40°C to 85°C Tape and reel Tray DS60001476B-page 2555 SAMA5D2 SERIES 71. Errata Errata is described in the following sections: - Section 71.1 “Errata - SAMA5D2 MRL C Parts” - Section 71.2 “Errata - SAMA5D2 MRL B Parts” - Section 71.3 “Errata - SAMA5D2 MRL A Parts” 71.1 Errata - SAMA5D2 MRL C Parts This section describes errata relevant to the devices listed in Table 71-2. Table 71-1: SAMA5D2 MRL C Parts Device Name ATSAMA5D21C ATSAMA5D22C ATSAMA5D23C ATSAMA5D24C ATSAMA5D26C ATSAMA5D27C ATSAMA5D28C 71.1.1 Issue: GMAC Timestamps and PTP packets Bad association of timestamps and the PTP packets An issue in the association mechanism between event registers and queued PTP packets may lead to timestamps incorrectly associated with these packets. Even if it is highly unlikely to queue consecutive packets of the same type, there is no way to know to which frame the content of the PTP event registers refers. Workaround: None 71.1.2 Issue: SDMMC software ‘Reset for All’ Command Software ‘Reset for All’ command is not guaranteed The software ‘Reset for All’ command is not guaranteed, and some registers of the host controller may not properly reset. The setting of the different registers must be checked before reinitializing the SD card. Workaround: None 71.1.3 Issue: FLEXCOM SMBUS FLEXCOM SMBUS alert signalling is not functional The TWI function embedded in the FLEXCOM does not support SMBUS alert signal management. Workaround: If this signal is mandatory in the application, the user can use one of the standalone TWIs (TWIHS0, TWIHS1) supporting the SMBUS alert signaling. DS60001476B-page 2556  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.1.4 Issue: TWI/TWIHS Clear Command The TWI/TWIHS Clear command does not work Bus reset using the “CLEAR” bit of the TWI/TWIHS control register does not work correctly during a bus busy state. Workaround: When the TWI master detects the SDA line stuck in low state the procedure to recover is: 1. 2. 3. 4. 5. 6. Reconfigure the SDA/SCL lines as PIO. Try to assert a Logic 1 on the SDA line (PIO output = 1). Read the SDA line state. If the PIO state is a Logic 0, then generate a clock pulse on SCL (1-0-1 transition). Read the SDA line state. If the SDA line = 0, go to Step 3; if SDA = 1, go to Step 5. Generate a STOP condition. Reconfigure SDA/SCL PIOs as peripheral. 71.1.5 Issue: SSC TD Output Unexpected delay on TD output When SSC is configured with the following conditions: • RCMR.START = Start on falling edge/Start on Rising edge/Start on any edge, • RFMR.FSOS = None (input), • TCMR.START = Receive Start, an unexpected delay of 2 or 3 system clock cycles is added to the TD output. Workaround: None 71.1.6 Issue: I2SC First Sent Data I2SC first sent data corrupted Right after I2SC reset, the first data sent by I2SC controller on the I2SDO line is corrupted. The following data are not affected. Workaround: None 71.1.7 Issue: Quad I/O Serial Peripheral Interface (QSPI) QSPI hangs with long DLYCS QSPI hangs if a command is written to any QSPI register during the DLYCS delay. There is no status bit to flag the end of the delay. Workaround: The field DLYCS defines a minimum period for which Chip Select is deasserted, required by some memories. This delay is generally < 60 ns and comprises internal execution time, arbitration and latencies. Thus, DLYCS must be configured to be slightly higher than the value specified for the slave device. The software must wait for this same period of time plus an additional delay before a command can be written to the QSPI.  2017 Microchip Technology Inc. DS60001476B-page 2557 SAMA5D2 SERIES 71.1.8 Master/Processor Clock Prescaler Issue: Change of the field PMC_MCKR.PRES is not allowed if Master/Processor Clock Prescaler frequency is too high PMC_MCKR.PRES cannot be changed if the clock applied to the Master/Processor Clock Prescaler (see “Master Clock Controller”, in Section 33. “Power Management Controller (PMC)”) is greater than 312 MHz (VDDCORE[1.1, 1.32]) and 394 MHz (VDDCORE[1.2, 1.32]). Workaround: 1. 2. 3. Set PMC_MCKR.CSS to MAIN_CLK. Set PMC_MCKR.PRES to the required value. Change PMC_MCKR.CSS to the new clock source (PLLA_CLK, UPLLCK). 71.1.9 Issue: Master CAN-FD Controller (MCAN) Flexible data rate feature does not support CRC CAN-FD peripheral (BOSCH V320) does not support the CRC scheme which includes the stuff bit count introduced by the ISO standardization committee. CAN 2.0 operation is not impacted. Workaround: None. 71.1.10 Issue: MCAN Interrupt MCAN_IR.MRAF Needless activation of interrupt MCAN_IR.MRAF During frame reception while the MCAN is in Error Passive state and the Receive Error Counter has the value MCAN_ECR.REC = 127, it may happen that MCAN_IR.MRAF is set although there was no Message RAM access failure. If MCAN_IR.MRAF is enabled, an interrupt to the Host CPU is generated. Workaround: The Message RAM Access Failure interrupt routine needs to check whether MCAN_ECR.RP = ’1’ and MCAN_ECR.REC = 127. In this case, reset MCAN_IR.MRAF. No further action is required. 71.1.11 Issue: MCAN Bus Integration State Return of receiver from Bus Integration state after Protocol Exception Event In case a started transmission is aborted shortly before the transmission of the FDF bit, a receiver will detect a recessive FDF bit followed by a recessive res bit. In this case receiving MCANs with Protocol Exception Event Handling enabled will detect a protocol exception event and will enter Bus Integration state. These receivers are expected to leave Bus Integration state after 11 consecutive recessive bits. Instead of starting to count 11 recessive bits directly after entering Bus Integration state, the MCAN needs to see at least one dominant bit. Workaround: Disable Protocol Exception Event Handling (MCAN_CCCR.PXHD = ’1’). DS60001476B-page 2558  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.1.12 Issue: MCAN Message RAM/RAM Arbiter Message RAM/RAM Arbiter not responding in time When the MCAN wants to store a received frame, and the Message RAM/RAM Arbiter does not respond in time, this message cannot be stored completely and it is discarded with the reception of the next message. Interrupt flag MCAN_IR.MRAF is set. It may happen that the next received message is stored incomplete. In this case, the respective Rx Buffer or Rx FIFO element holds inconsistent data. Workaround: Configure the RAM Watchdog to the maximum expected Message RAM access delay. In case the Message RAM / RAM Arbiter does not respond within this time, the Watchdog Interrupt MCAN_IR.WDI is set. In this case discard the frame received after MCAN_IR.MRAF has been activated. 71.1.13 Issue: MCAN Frame Receiving Data loss (payload) in case storage of a received frame has not completed until end of EOF field is reached This erratum is applicable only if the MCAN peripheral clock frequency is below 77 MHz. During frame reception, the Rx Handler needs access to the Message RAM for acceptance filtering (read access) and storage of accepted messages (write access). The time needed for acceptance filtering and storage of a received message depends on the MCAN peripheral clock frequency, the number of MCANs connected to a single Message RAM, the Message RAM arbitration scheme, and the number of configured filter elements. In case storage of a received message has not completed until the end of the received frame is reached, the following faulty behavior can be observed: • The last write to the Message RAM to complete storage of the received message is omitted, this data is lost. Applies for data frames with DLC > 0, worst case is DLC = 1. • Rx FIFO: FIFO put index MCAN_RXFnS.FnPI is updated although the last FIFO element holds corrupted data. • Rx Buffer: New Data flag MCAN_NDATn.NDxx is set although the Rx Buffer holds corrupted data. • Interrupt flag MCAN_IR.MRAF is not set. Workaround: Reduce the maximum number of configured filter elements for the MCANs attached to the Message RAM until the calculated clock frequency is below the MCAN peripheral clock frequency used with the device. 71.1.14 Issue: MCAN Edge Filtering Edge filtering causes mis-synchronization when falling edge at Rx input pin coincides with end of integration phase When edge filtering is enabled (MCAN_CCCR.EFBI = ’1’) and when the end of the integration phase coincides with a falling edge at the Rx input pin, it may happen that the MCAN synchronizes itself wrongly and does not correctly receive the first bit of the frame. In this case the CRC will detect that the first bit was received incorrectly; it will rate the received FD frame as faulty and an error frame will be sent. The issue only occurs when there is a falling edge at the Rx input pin (CANRX) within the last time quantum (tq) before the end of the integration phase. The last time quantum of the integration phase is at the sample point of the 11th recessive bit of the integration phase. When the edge filtering is enabled, the bit timing logic of the MCAN sees the Rx input signal delayed by the edge filtering. When the integration phase ends, the edge filtering is automatically disabled. This affects the reset of the FD CRC registers at the beginning of the frame. The Classical CRC register are not affected, so this issue does not affect the reception of Classical frames. In CAN communication, the MCAN may enter integrating state (either by resetting MCAN_CCCR.INIT or by protocol exception event) while a frame is active on the bus. In this case the 11 recessive bits are counted between the acknowledge bit and the following start of frame. All nodes have synchronized at the beginning of the dominant acknowledge bit. This means that the edge of the following start of frame bit cannot fall on the sample point, so the issue does not occur. The issue occurs only when the MCAN is, by local errors, missynchronized with regard to the other nodes, or not synchronized at all. Glitch filtering as specified in ISO 11898-1:2015 is fully functional.  2017 Microchip Technology Inc. DS60001476B-page 2559 SAMA5D2 SERIES Edge filtering was introduced for applications where the data bit time is at least two tq (of the nominal bit time) long. In that case, edge filtering requires at least two consecutive dominant time quanta before the counter counting the 11 recessive bits for idle detection is restarted. This means edge filtering covers the theoretical case of occasional 1-tq-long dominant spikes on the CAN bus that would delay idle detection. Repeated dominant spikes on the CAN bus would disturb all CAN communication, so the filtering to speed up idle detection would not help network performance. When this rare event occurs, the MCAN sends an error frame and the sender of the affected frame retransmits the frame. When the retransmitted frame is received, the MCAN has left the integration phase and the frame will be received correctly. Edge filtering is only applied during integration phase, it is never used during normal operation. As the integration phase is very short with respect to “active communication time”, the impact on total error frame rate is negligible. The issue has no impact on data integrity. The MCAN enters integration phase under the following conditions: • when MCAN_CCCR.INIT is set to ’0’ after start-up • after a protocol exception event (only when MCAN_CCCR.PXHD = ’0’) Workaround: Disable edge filtering or wait on retransmission in case this rare event happens. 71.1.15 Issue: MCAN_NBTP.NTSEG2 Configuration Configuration of MCAN_NBTP.NTSEG2 = ’0’ not allowed When MCAN_NBTP.NTSEG2 is configured to zero (Phase_Seg2(N) = 1), and when there is a pending transmission request, a dominant third bit of Intermission may cause the MCAN to wrongly transmit the first identifier bit dominant instead of recessive, even if this bit was configured as ’1’ in the MCAN’s Tx Buffer Element. A phase buffer segment 2 of length ’1’ (Phase_Seg2(N) = 1) is not sufficient to switch to the first identifier bit after the sample point in Intermission where the dominant bit was detected. The CAN protocol according to ISO 11898-1 defines that a dominant third bit of Intermission causes a pending transmission to be started immediately. The received dominant bit is handled as if the MCAN has transmitted a Start-of-Frame (SoF) bit. The ISO 11898-1 specifies the minimum configuration range for Phase_Seg2(N) to be 2..8 tq. Therefore excluding a Phase_Seg2(N) of ’1’ will not affect MCAN conformance. Workaround: Use the range 1..127 for MCAN_NBTP.NTSEG2 instead of 0..127. 71.1.16 Issue: MCAN DAR Mode Retransmission in DAR mode due to lost arbitration at the first two identifier bits When the MCAN is configured in DAR mode (MCAN_CCCR.DAR = ’1’) the Automatic Retransmission for transmitted messages that have been disturbed by an error or have lost arbitration is disabled. When the transmission attempt is not successful, the Tx Buffer’s transmission request bit (MCAN_TXBRP.TRPxx) shall be cleared and its cancellation finished bit (MCAN_TXBCF.CFxx) shall be set. When the transmitted message loses arbitration at one of the first two identifier bits, it may happen that instead of the bits of the actually transmitted Tx Buffer, the MCAN_TXBRP.TRPxx and MCAN_TXBCF.CFxx bits of the previously started Tx Buffer (or Tx Buffer 0 if there is no previous transmission attempt) are written (MCAN_TXBRP.TRPxx = ’0’, MCAN_TXBCF.CFxx = ’1’). If in this case the MCAN_TXBRP.TRPxx bit of the Tx Buffer that lost arbitration at the first two identifier bits has not been cleared, retransmission is attempted. When the MCAN loses arbitration again at the immediately following retransmission, then actually and previously transmitted Tx Buffers are the same and this Tx Buffer’s MCAN_TXBRP.TRPxx bit is cleared and its MCAN_TXBCF.CFxx bit is set. Workaround: None. DS60001476B-page 2560  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.1.17 MCAN Tx FIFO Message Issue: Tx FIFO message sequence inversion Assume the case that there are two Tx FIFO messages in the output pipeline of the Tx Message Handler. Transmission of Tx FIFO message 1 is started: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: -Now a non Tx FIFO message with a higher CAN priority is requested. Due to its priority it will be inserted into the output pipeline. The TxMH performs so called "message scans" to keep the output pipeline up to date with the highest priority messages from the Message RAM. After the following two message scans, the output pipeline has the following content: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: non Tx FIFO message with higher CAN priority Position 3: Tx FIFO message 2 If the transmission of Tx FIFO message 1 is not successful (lost arbitration or CAN bus error) it is pushed from the output pipeline by the non Tx FIFO message with higher CAN priority. The following scan re-inserts Tx FIFO message 1 into the output pipeline at position 3: Position 1: non Tx FIFO message with higher CAN priority (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: Tx FIFO message 1 Now Tx FIFO message 2 is in the output pipeline in front of Tx FIFO message 1 and they are transmitted in that order, resulting in a message sequence inversion. Workaround: 1. First Workaround Use two dedicated Tx Buffers, e.g. use Tx Buffers 4 and 5 instead of the Tx FIFO. The pseudo-code below replaces the function that fills the Tx FIFO. Write message to Tx Buffer 4. Transmit Loop: • • • • • • 2. Request Tx Buffer 4 - write MCAN_TXBAR.A4 Write message to Tx Buffer 5 Wait until transmission of Tx Buffer 4 completed - MCAN_IR.TC, read MCAN_TXBTO.TO4 Request Tx Buffer 5 - write MCAN_TXBAR.A5 Write message to Tx Buffer 4 Wait until transmission of Tx Buffer 5 completed - MCAN_IR.TC, read MCAN_TXBTO.TO5 Second Workaround Assure that only one Tx FIFO element is pending for transmission at any time. The Tx FIFO elements may be filled at any time with messages to be transmitted, but their transmission requests are handled separately. Each time a Tx FIFO transmission has completed and the Tx FIFO gets empty (MCAN_IR.TFE = ’1’) the next Tx FIFO element is requested. 3. Third Workaround Use only a Tx FIFO. Send the message with the higher priority also from Tx FIFO. Drawback: The higher priority message has to wait until the preceding messages in the Tx FIFO have been sent.  2017 Microchip Technology Inc. DS60001476B-page 2561 SAMA5D2 SERIES 71.1.18 MCAN High Priority Message (HPM) Issue: Unexpected High Priority Message (HPM) interrupt There are two configurations where the issue occurs: Configuration A: • At least one Standard Message ID Filter Element is configured with priority flag set (S0.SFEC = "100"/"101"/"110") • No Extended Message ID Filter Element configured • Non-matching extended frames are accepted (MCAN_GFC.ANFE = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority extended message under the following conditions: 1. 2. A standard HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next an extended frame is received and accepted because of MCAN_GFC.ANFE configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Configuration B: • At least one Extended Message ID Filter Element is configured with priority flag set (F0.EFEC = "100"/"101"/"110") • No Standard Message ID Filter Element configured • Non-matching standard frames are accepted (MCAN_GFC.ANFS = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority standard message under the following conditions: 1. 2. An extended HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next a standard frame is received and accepted because of MCAN_GFC.ANFS configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Workaround: Configuration A: Setup an Extended Message ID Filter Element with the following configuration: • • • • F0.EFEC = "001"/"010" - select Rx FIFO for storage of extended frames F0.EFID1 = any value - value not relevant as all ID bits are masked out by F1.EFID2 F1.EFT = "10" - classic filter, F0.EFID1 = filter, F1.EFID2 = mask F1.EFID2 = zero - all bits of the received extended ID are masked out Now all extended frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of F0.EFEC. Configuration B: Setup a Standard Message ID Filter Element with the following configuration: • • • • S0.SFEC = "001"/"010" - select Rx FIFO for storage of standard frames S0.SFID1 = any value - value not relevant as all ID bits are masked out by S0.SFID2 S0.SFT = "10" - classic filter, S0.SFID1 = filter, S0.SFID2 = mask S0.SFID2 = zero - all bits of the received standard ID are masked out Now all standard frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of S0.SFEC. DS60001476B-page 2562  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.1.19 ROM Code: Using JTAG IOSET 4 Issue: JTAG_TCK on IOSET 4 pin has a wrong configuration after boot The JTAG_TCK signal on IOSET 4 shares its pin (PA22) with the clock signal of the following boot memory interfaces: SDMMC1, SPI1 IOSET 2, QSPI 0 IOSET 3. If JTAG IOSET 4 is selected by the user as JTAG debug port in the Boot Configuration Word, and if the ROM Code boots, or tries to boot, on any of the external memory interfaces stated above, the JTAG clock pin (TCK) is reset at its default mode (PIO) at the end of the ROM Code execution. This occurs with the default memory boot configuration because the ROM Code tries to boot on SDMMC1 even when bit EXT_MEM_BOOT_ENABLE is not set. Workaround: Do not select, or disable, external memory boot interface SDMMC1, SPI1 IOSET 2 or QSPI0 IOSET 3. However, if using one of these boot interfaces is required, reconfigure the PA22 pin in JTAG TCK IOSET 4 mode in the bootstrap or application. 71.2 Errata - SAMA5D2 MRL B Parts This section describes errata relevant to the devices listed in Table 71-2. Table 71-2: SAMA5D2 MRL B Parts Device Name ATSAMA5D21B ATSAMA5D22B ATSAMA5D23B ATSAMA5D24B ATSAMA5D26B ATSAMA5D27B ATSAMA5D28B 71.2.1 Issue: GMAC Timestamps and PTP packets Issue: Bad association of timestamps and the PTP packets An issue in the association mechanism between event registers and queued PTP packets may lead to timestamps incorrectly associated with these packets. Even if it is highly unlikely to queue consecutive packets of the same type, there is no way to know to which frame the content of the PTP event registers refers. Workaround: None 71.2.2 Issue: ROM Code: SDMMC0 and SDMMC1 boot issue The card detect pin is not correctly sampled in the ROM code, which leads to a nondeterministic boot ability on the SDMMC0/SDMMC1 interfaces (SDCard or eMMC). Workaround: Use another boot media (e.g., serial flash) for the first level boot, and either deactivate the boot on SDMMC0/1 in the Boot Configuration Word in the Fuse area or remove any bootable program stored in the eMMC or SDCard connected to the chip at startup.  2017 Microchip Technology Inc. DS60001476B-page 2563 SAMA5D2 SERIES 71.2.3 Issue: SDMMC Software ‘Reset for All’ Command Software ‘Reset for All’ command is not guaranteed The software ‘Reset for All’ command is not guaranteed, and some registers of the host controller may not properly reset. The setting of the different registers must be checked before reinitializing the SD card. Workaround: None 71.2.4 Issue: FLEXCOM SMBUS FLEXCOM SMBUS alert signalling is not functional The TWI function embedded in the FLEXCOM does not support SMBUS alert signal management. Workaround: If this signal is mandatory in the application, the user can use one of the standalone TWIs (TWIHS0, TWIHS1) supporting the SMBUS alert signaling. 71.2.5 Issue: TWI/TWIHS Clear Command The TWI/TWIHS Clear command does not work Bus reset using the “CLEAR” bit of the TWI/TWIHS control register does not work correctly during a bus busy state. Workaround: When the TWI master detects the SDA line stuck in low state the procedure to recover is: 1. 2. 3. 4. 5. 6. Reconfigure the SDA/SCL lines as PIO. Try to assert a Logic 1 on the SDA line (PIO output = 1). Read the SDA line state. If the PIO state is a Logic 0, then generate a clock pulse on SCL (1-0-1 transition). Read the SDA line state. If the SDA line = 0, go to Step 3; if SDA = 1, go to Step 5. Generate a STOP condition. Reconfigure SDA/SCL PIOs as peripheral. 71.2.6 Issue: SSC TD Output Unexpected delay on TD output When SSC is configured with the following conditions: • RCMR.START = Start on falling edge/Start on Rising edge/Start on any edge, • RFMR.FSOS = None (input), • TCMR.START = Receive Start, an unexpected delay of 2 or 3 system clock cycles is added to the TD output. Workaround: None 71.2.7 Issue: I2SC First Sent Data I2SC first sent data corrupted Right after I2SC reset, the first data sent by I2SC controller on the I2SDO line is corrupted. The following data are not affected. Workaround: None DS60001476B-page 2564  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.2.8 Quad I/O Serial Peripheral Interface (QSPI) Issue: QSPI hangs with long DLYCS QSPI hangs if a command is written to any QSPI register during the DLYCS delay. There is no status bit to flag the end of the delay. Workaround: The field DLYCS defines a minimum period for which Chip Select is deasserted, required by some memories. This delay is generally < 60 ns and comprises internal execution time, arbitration and latencies. Thus, DLYCS must be configured to be slightly higher than the value specified for the slave device. The software must wait for this same period of time plus an additional delay before a command can be written to the QSPI. 71.2.9 Master/Processor Clock Prescaler Issue: Change of the field PMC_MCKR.PRES is not allowed if Master/Processor Clock Prescaler frequency is too high PMC_MCKR.PRES cannot be changed if the clock applied to the Master/Processor Clock Prescaler (see “Master Clock Controller”, in Section 33. “Power Management Controller (PMC)”) is greater than 312 MHz (VDDCORE[1.1, 1.32]) and 394 MHz (VDDCORE[1.2, 1.32]). Workaround: 1. 2. 3. Set PMC_MCKR.CSS to MAIN_CLK. Set PMC_MCKR.PRES to the required value. Change PMC_MCKR.CSS to the new clock source (PLLA_CLK, UPLLCK). 71.2.10 Issue: Master CAN-FD Controller (MCAN) Flexible data rate feature does not support CRC CAN-FD peripheral (BOSCH V320) does not support the CRC scheme which includes the stuff bit count introduced by the ISO standardization committee. CAN 2.0 operation is not impacted. Workaround: None. 71.2.11 Issue: MCAN Interrupt MCAN_IR.MRAF Needless activation of interrupt MCAN_IR.MRAF During frame reception while the MCAN is in Error Passive state and the Receive Error Counter has the value MCAN_ECR.REC = 127, it may happen that MCAN_IR.MRAF is set although there was no Message RAM access failure. If MCAN_IR.MRAF is enabled, an interrupt to the Host CPU is generated. Workaround: The Message RAM Access Failure interrupt routine needs to check whether MCAN_ECR.RP = ’1’ and MCAN_ECR.REC = 127. In this case, reset MCAN_IR.MRAF. No further action is required.  2017 Microchip Technology Inc. DS60001476B-page 2565 SAMA5D2 SERIES 71.2.12 Issue: MCAN Bus Integration State Return of receiver from Bus Integration state after Protocol Exception Event In case a started transmission is aborted shortly before the transmission of the FDF bit, a receiver will detect a recessive FDF bit followed by a recessive res bit. In this case receiving MCANs with Protocol Exception Event Handling enabled will detect a protocol exception event and will enter Bus Integration state. These receivers are expected to leave Bus Integration state after 11 consecutive recessive bits. Instead of starting to count 11 recessive bits directly after entering Bus Integration state, the MCAN needs to see at least one dominant bit. Workaround: Disable Protocol Exception Event Handling (MCAN_CCCR.PXHD = ’1’). 71.2.13 Issue: MCAN Message RAM/RAM Arbiter Message RAM/RAM Arbiter not responding in time When the MCAN wants to store a received frame, and the Message RAM/RAM Arbiter does not respond in time, this message cannot be stored completely and it is discarded with the reception of the next message. Interrupt flag MCAN_IR.MRAF is set. It may happen that the next received message is stored incomplete. In this case, the respective Rx Buffer or Rx FIFO element holds inconsistent data. Workaround: Configure the RAM Watchdog to the maximum expected Message RAM access delay. In case the Message RAM / RAM Arbiter does not respond within this time, the Watchdog Interrupt MCAN_IR.WDI is set. In this case discard the frame received after MCAN_IR.MRAF has been activated. 71.2.14 Issue: MCAN Frame Receiving Data loss (payload) in case storage of a received frame has not completed until end of EOF field is reached This erratum is applicable only if the MCAN peripheral clock frequency is below 77 MHz. During frame reception, the Rx Handler needs access to the Message RAM for acceptance filtering (read access) and storage of accepted messages (write access). The time needed for acceptance filtering and storage of a received message depends on the MCAN peripheral clock frequency, the number of MCANs connected to a single Message RAM, the Message RAM arbitration scheme, and the number of configured filter elements. In case storage of a received message has not completed until the end of the received frame is reached, the following faulty behavior can be observed: • The last write to the Message RAM to complete storage of the received message is omitted, this data is lost. Applies for data frames with DLC > 0, worst case is DLC = 1. • Rx FIFO: FIFO put index MCAN_RXFnS.FnPI is updated although the last FIFO element holds corrupted data. • Rx Buffer: New Data flag MCAN_NDATn.NDxx is set although the Rx Buffer holds corrupted data. • Interrupt flag MCAN_IR.MRAF is not set. Workaround: Reduce the maximum number of configured filter elements for the MCANs attached to the Message RAM until the calculated clock frequency is below the MCAN peripheral clock frequency used with the device. 71.2.15 Issue: MCAN Edge Filtering Edge filtering causes mis-synchronization when falling edge at Rx input pin coincides with end of integration phase When edge filtering is enabled (MCAN_CCCR.EFBI = ’1’) and when the end of the integration phase coincides with a falling edge at the Rx input pin, it may happen that the MCAN synchronizes itself wrongly and does not correctly receive the first bit of the frame. In this case the CRC will detect that the first bit was received incorrectly; it will rate the received FD frame as faulty and an error frame will be sent. DS60001476B-page 2566  2017 Microchip Technology Inc. SAMA5D2 SERIES The issue only occurs when there is a falling edge at the Rx input pin (CANRX) within the last time quantum (tq) before the end of the integration phase. The last time quantum of the integration phase is at the sample point of the 11th recessive bit of the integration phase. When the edge filtering is enabled, the bit timing logic of the MCAN sees the Rx input signal delayed by the edge filtering. When the integration phase ends, the edge filtering is automatically disabled. This affects the reset of the FD CRC registers at the beginning of the frame. The Classical CRC register are not affected, so this issue does not affect the reception of Classical frames. In CAN communication, the MCAN may enter integrating state (either by resetting MCAN_CCCR.INIT or by protocol exception event) while a frame is active on the bus. In this case the 11 recessive bits are counted between the acknowledge bit and the following start of frame. All nodes have synchronized at the beginning of the dominant acknowledge bit. This means that the edge of the following start of frame bit cannot fall on the sample point, so the issue does not occur. The issue occurs only when the MCAN is, by local errors, missynchronized with regard to the other nodes, or not synchronized at all. Glitch filtering as specified in ISO 11898-1:2015 is fully functional. Edge filtering was introduced for applications where the data bit time is at least two tq (of the nominal bit time) long. In that case, edge filtering requires at least two consecutive dominant time quanta before the counter counting the 11 recessive bits for idle detection is restarted. This means edge filtering covers the theoretical case of occasional 1-tq-long dominant spikes on the CAN bus that would delay idle detection. Repeated dominant spikes on the CAN bus would disturb all CAN communication, so the filtering to speed up idle detection would not help network performance. When this rare event occurs, the MCAN sends an error frame and the sender of the affected frame retransmits the frame. When the retransmitted frame is received, the MCAN has left the integration phase and the frame will be received correctly. Edge filtering is only applied during integration phase, it is never used during normal operation. As the integration phase is very short with respect to “active communication time”, the impact on total error frame rate is negligible. The issue has no impact on data integrity. The MCAN enters integration phase under the following conditions: • when MCAN_CCCR.INIT is set to ’0’ after start-up • after a protocol exception event (only when MCAN_CCCR.PXHD = ’0’) Workaround: Disable edge filtering or wait on retransmission in case this rare event happens. 71.2.16 Issue: MCAN_NBTP.NTSEG2 Configuration Configuration of MCAN_NBTP.NTSEG2 = ’0’ not allowed When MCAN_NBTP.NTSEG2 is configured to zero (Phase_Seg2(N) = 1), and when there is a pending transmission request, a dominant third bit of Intermission may cause the MCAN to wrongly transmit the first identifier bit dominant instead of recessive, even if this bit was configured as ’1’ in the MCAN’s Tx Buffer Element. A phase buffer segment 2 of length ’1’ (Phase_Seg2(N) = 1) is not sufficient to switch to the first identifier bit after the sample point in Intermission where the dominant bit was detected. The CAN protocol according to ISO 11898-1 defines that a dominant third bit of Intermission causes a pending transmission to be started immediately. The received dominant bit is handled as if the MCAN has transmitted a Start-of-Frame (SoF) bit. The ISO 11898-1 specifies the minimum configuration range for Phase_Seg2(N) to be 2..8 tq. Therefore excluding a Phase_Seg2(N) of ’1’ will not affect MCAN conformance. Workaround: Use the range 1..127 for MCAN_NBTP.NTSEG2 instead of 0..127. 71.2.17 Issue: MCAN DAR Mode Retransmission in DAR mode due to lost arbitration at the first two identifier bits When the MCAN is configured in DAR mode (MCAN_CCCR.DAR = ’1’) the Automatic Retransmission for transmitted messages that have been disturbed by an error or have lost arbitration is disabled. When the transmission attempt is not successful, the Tx Buffer’s transmission request bit (MCAN_TXBRP.TRPxx) shall be cleared and its cancellation finished bit (MCAN_TXBCF.CFxx) shall be set. When the transmitted message loses arbitration at one of the first two identifier bits, it may happen that instead of the bits of the actually transmitted Tx Buffer, the MCAN_TXBRP.TRPxx and MCAN_TXBCF.CFxx bits of the previously started Tx Buffer (or Tx Buffer 0 if there is no previous transmission attempt) are written (MCAN_TXBRP.TRPxx = ’0’, MCAN_TXBCF.CFxx = ’1’). If in this case the MCAN_TXBRP.TRPxx bit of the Tx Buffer that lost arbitration at the first two identifier bits has not been cleared, retransmission is attempted.  2017 Microchip Technology Inc. DS60001476B-page 2567 SAMA5D2 SERIES When the MCAN loses arbitration again at the immediately following retransmission, then actually and previously transmitted Tx Buffers are the same and this Tx Buffer’s MCAN_TXBRP.TRPxx bit is cleared and its MCAN_TXBCF.CFxx bit is set. Workaround: None. 71.2.18 MCAN Tx FIFO Message Issue: Tx FIFO message sequence inversion Assume the case that there are two Tx FIFO messages in the output pipeline of the Tx Message Handler. Transmission of Tx FIFO message 1 is started: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: -Now a non Tx FIFO message with a higher CAN priority is requested. Due to its priority it will be inserted into the output pipeline. The TxMH performs so called "message scans" to keep the output pipeline up to date with the highest priority messages from the Message RAM. After the following two message scans, the output pipeline has the following content: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: non Tx FIFO message with higher CAN priority Position 3: Tx FIFO message 2 If the transmission of Tx FIFO message 1 is not successful (lost arbitration or CAN bus error) it is pushed from the output pipeline by the non Tx FIFO message with higher CAN priority. The following scan re-inserts Tx FIFO message 1 into the output pipeline at position 3: Position 1: non Tx FIFO message with higher CAN priority (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: Tx FIFO message 1 Now Tx FIFO message 2 is in the output pipeline in front of Tx FIFO message 1 and they are transmitted in that order, resulting in a message sequence inversion. Workaround: 1. First Workaround Use two dedicated Tx Buffers, e.g. use Tx Buffers 4 and 5 instead of the Tx FIFO. The pseudo-code below replaces the function that fills the Tx FIFO. Write message to Tx Buffer 4. Transmit Loop: • • • • • • 2. Request Tx Buffer 4 - write MCAN_TXBAR.A4 Write message to Tx Buffer 5 Wait until transmission of Tx Buffer 4 completed - MCAN_IR.TC, read MCAN_TXBTO.TO4 Request Tx Buffer 5 - write MCAN_TXBAR.A5 Write message to Tx Buffer 4 Wait until transmission of Tx Buffer 5 completed - MCAN_IR.TC, read MCAN_TXBTO.TO5 Second Workaround Assure that only one Tx FIFO element is pending for transmission at any time. The Tx FIFO elements may be filled at any time with messages to be transmitted, but their transmission requests are handled separately. Each time a Tx FIFO transmission has completed and the Tx FIFO gets empty (MCAN_IR.TFE = ’1’) the next Tx FIFO element is requested. 3. Third Workaround Use only a Tx FIFO. Send the message with the higher priority also from Tx FIFO. Drawback: The higher priority message has to wait until the preceding messages in the Tx FIFO have been sent. DS60001476B-page 2568  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.2.19 MCAN High Priority Message (HPM) Issue: Unexpected High Priority Message (HPM) interrupt There are two configurations where the issue occurs: Configuration A: • At least one Standard Message ID Filter Element is configured with priority flag set (S0.SFEC = "100"/"101"/"110") • No Extended Message ID Filter Element configured • Non-matching extended frames are accepted (MCAN_GFC.ANFE = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority extended message under the following conditions: 1. 2. A standard HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next an extended frame is received and accepted because of MCAN_GFC.ANFE configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Configuration B: • At least one Extended Message ID Filter Element is configured with priority flag set (F0.EFEC = "100"/"101"/"110") • No Standard Message ID Filter Element configured • Non-matching standard frames are accepted (MCAN_GFC.ANFS = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority standard message under the following conditions: 1. 2. An extended HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next a standard frame is received and accepted because of MCAN_GFC.ANFS configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Workaround: Configuration A: Setup an Extended Message ID Filter Element with the following configuration: • • • • F0.EFEC = "001"/"010" - select Rx FIFO for storage of extended frames F0.EFID1 = any value - value not relevant as all ID bits are masked out by F1.EFID2 F1.EFT = "10" - classic filter, F0.EFID1 = filter, F1.EFID2 = mask F1.EFID2 = zero - all bits of the received extended ID are masked out Now all extended frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of F0.EFEC. Configuration B: Setup a Standard Message ID Filter Element with the following configuration: • • • • S0.SFEC = "001"/"010" - select Rx FIFO for storage of standard frames S0.SFID1 = any value - value not relevant as all ID bits are masked out by S0.SFID2 S0.SFT = "10" - classic filter, S0.SFID1 = filter, S0.SFID2 = mask S0.SFID2 = zero - all bits of the received standard ID are masked out Now all standard frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of S0.SFEC. 71.2.20 Issue: ROM Code: Using JTAG IOSET 4 JTAG_TCK on IOSET 4 pin has a wrong configuration after boot The JTAG_TCK signal on IOSET 4 shares its pin (PA22) with the clock signal of the following boot memory interfaces: SDMMC1, SPI1 IOSET 2, QSPI 0 IOSET 3.  2017 Microchip Technology Inc. DS60001476B-page 2569 SAMA5D2 SERIES If JTAG IOSET 4 is selected by the user as JTAG debug port in the Boot Configuration Word, and if the ROM Code boots, or tries to boot, on any of the external memory interfaces stated above, the JTAG clock pin (TCK) is reset at its default mode (PIO) at the end of the ROM Code execution. This occurs as soon as EXT_MEM_BOOT_ENABLE is set. Workaround: Do not select, or disable, external memory boot interface SDMMC1, SPI1 IOSET 2 or QSPI0 IOSET 3. However, if using one of these boot interfaces is required, reconfigure the PA22 pin in JTAG TCK IOSET 4 mode in the bootstrap or application. 71.3 Errata - SAMA5D2 MRL A Parts This section describes errata relevant to the devices listed in Table 71-3. Table 71-3: SAMA5D2 MRL A Parts Device Name ATSAMA5D22A ATSAMA5D24A ATSAMA5D27A ATSAMA5D28A 71.3.1 Issue: GMAC Timestamps and PTP packets Issue: Bad association of timestamps and the PTP packets An issue in the association mechanism between event registers and queued PTP packets may lead to timestamps incorrectly associated with these packets. Even if it is highly unlikely to queue consecutive packets of the same type, there is no way to know to which frame the content of the PTP event registers refers. Workaround: None 71.3.2 Issue: ROM Code: Main External Clock Frequency Support for SAM-BA Monitor ROM code v1.1 supports ONLY a 12 and 16 MHz external clock frequency to allow USB connection to be used for SAM-BA Monitor Workaround: None 71.3.3 Issue: ROM Code: Watchdog after SAM-BA Monitor Connection Watchdog reset occurs when reenabling the watchdog When no bootable program is found in an external memory, the Watchdog is disabled just before the ROM Code runs SAM-BA Monitor. The ROM code sets the Watchdog Timer Mode register (WDT_MR) to the value 0x00008000 and then clears the counter value. If a program loaded and executed using the SAM-BA Monitor Go command reenables the watchdog, a watchdog reset is immediately executed whatever the value of the watchdog counter. DS60001476B-page 2570  2017 Microchip Technology Inc. SAMA5D2 SERIES Workaround: To avoid any unexpected watchdog reset when reenabling the watchdog, the following sequence has to be performed: 1. 2. 3. Write 0x00000000 in the WDT_MR. Wait for three slow clock cycles. Write the final value in the WDT_MR. 71.3.4 Issue: ROM Code: SPI Bootup Frequency SPI frequency at bootup is not 11 MHz The SPI frequency at the boot of the device is set to 16 MHz instead of 11 MHz. A margin was applied to the SPI timings and make them compliant with a 16 MHz clock. The SPI boot remains functional. Workaround: None. 71.3.5 Issue: Unique Serial Number The serial number stored in the SFR registers (SFR_SN0 and SFR_SN1) is not correct The serial number (SFR_SN0, SFR_SN1) has only 16 bits set. This serial number cannot be used as a 64-bit unique ID. Workaround: None 71.3.6 Issue: Fuse Masking The Partial Fuse Masking function does not work The fuse masking function described in Section 57. “Secure Fuse Controller (SFC)” does not work. If the ROM code is used in Secure mode, the overall fuses are masked by the ROM code even if some of them are not used. Workaround: None 71.3.7 Issue: Fuse Writing The first two bits of each 32-bit block of the fuse matrix cannot be written The first two bits of each 32-bit block of the fuse matrix cannot be written, so that any word (32 bits) written needs to set to 0 the first two bits of each word (32 bits) of the fuse matrix. Workaround: None 71.3.8 Issue: HSIC Startup At HSIC startup, the strobe default state is wrong The strobe line should be at logic state 0 when HSIC is powered ON, and disabled. Currently, powering up the product sets the strobe line at logic state 1 before the HSIC is enabled. In this case, a connected device tries to connect before the HSIC is enabled. Workaround: Connect the device after the SAMA5D2 has been started.  2017 Microchip Technology Inc. DS60001476B-page 2571 SAMA5D2 SERIES 71.3.9 Issue: ADC SleepWalking ADC SleepWalking is not functional Workaround: None 71.3.10 Issue: ADC Last Channel Low-speed Trigger The last channel can be triggered at low speed but cannot be programmed by the OUT1 field of the RTC. Only the 1-Hz sampling period is available. Workaround: None 71.3.11 Issue: ADC Trigger Events ADC trigger events RTCOUT0 and RTCOUT1 are not functional RTCOUT0 issue leads to ADC Sleepwalking not functional. RTCOUT1 issue makes the last channel specific measurement trigger work at 1 Hz only. Workaround: None 71.3.12 Issue: ACC Output ACC output connection issue The Analog Comparator (ACC) output is not connected to the PWM event line. Workaround: None 71.3.13 Issue: SDMMC Software 'Reset For all' Command Software 'Reset For all' command is not guaranteed The software 'Reset For all' command is not guaranteed, and some registers of the host controller may not properly reset. The setting of the different registers must be checked before reinitializing the SD card. Workaround: None 71.3.14 Issue: SDMMC Status Flag INTCLKS Status flag INTCLKS may not work correctly When the SDMMC internal clock is disabled (SDMMC_CCR. INTCLKEN = 0) and reenabled after a few cycles (SDMMC_CCR. INTCLKEN = 1), the status flag INTCLKS may get stuck at 0. Workaround: A delay loop of 6 cycles minimum of the slowest clock (HCLOCK or BASECLK) must be inserted between SDMMC_CCR. INTCLKEN = 0 and SDMMC_CCR. INTCLKEN = 1. DS60001476B-page 2572  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.3.15 Issue: PMC GCLK Fields GCLK fields are reprogrammed unexpectedly When configuring a peripheral featuring no GCLK, the GCLK fields (GCKEN, GCKCSS, GCKDIV) of FLEXCOM0 are reconfigured. No other parameter is modified. Workaround: When accessing a peripheral featuring no GCLK, fill the GCLK fields with the GCLK configuration of FLEXCOM0. 71.3.16 Issue: PMC SleepWalking PMC SleepWalking is not functional In Ultra-Low Power mode (ULP1) using simultaneously partial wakeup (SleepWalking) and full wakeup (PIOBU used as wakeup pins or internal events RTC, etc.) may not resume from ULP1. Workaround: None. 71.3.17 Issue: CLASSD Peripheral Unexpected offset and noise level in Differential Output mode When the CLASSD peripheral is set to Differential Output mode (PWMTYP = 1), a significant output offset and an increased level of noise are observed on the audio outputs. The offset is systematic and is equal to 1/16 of the digital full scale. Workaround: To avoid the offset, add the opposite offset on the input signal of the CLASSD peripheral. 71.3.18 Issue: FLEXCOM SMBUS FLEXCOM SMBUS alert signalling is not functional The TWI function embedded in the FLEXCOM does not support SMBUS alert signal management. Workaround: If this signal is mandatory in the application, the user can use one of the standalone TWIs (TWIHS0, TWIHS1) supporting the SMBUS alert signaling. 71.3.19 Issue: TWI/TWIHS Clear Command The TWI/TWIHS Clear command does not work Bus reset using the “CLEAR” bit of the TWI/TWIHS control register does not work correctly during a bus busy state.. Workaround: When the TWI master detects the SDA line stuck in low state the procedure to recover is: 1. 2. 3. 4. 5. 6. Reconfigure the SDA/SCL lines as PIO. Try to assert a Logic 1 on the SDA line (PIO output = 1). Read the SDA line state. If the PIO state is a Logic 0, then generate a clock pulse on SCL (1-0-1 transition). Read the SDA line state. If the SDA line = 0, go to Step 3; if SDA = 1, go to Step 5. Generate a STOP condition. Reconfigure SDA/SCL PIOs as peripheral.  2017 Microchip Technology Inc. DS60001476B-page 2573 SAMA5D2 SERIES 71.3.20 Issue: MPDDRC tFAW tFAW timing violation DDR2/LPDDR2 memory devices with 8 banks have an additional requirement for tFAW: no more than four Activate commands must be issued in any given tFAW period. Workaround: Increase the value of tRRD to 3 to avoid the issue. 71.3.21 Issue: Audio PLL Audio PLL output frequency range The frequency range of the AUDIOCORECLK signal (AUDIOPLL output) provided in Table 66-26 “Audio PLL Characteristics” (fCORE parameter) does not comply with the applicable specification. Workaround: The AUDIOCORECLK signal can be operated from 720 MHz to 790 MHz if the following restricted operating conditions are met: - Junction temperature (Tj) range: 0°C to +40°C - VDDCORE/VDDPLL supply range: 1.20V to 1.32V - Bits in register PMC_AUDIO_PLL0 are set to (01)2 71.3.22 Issue: SSC TD Output Unexpected delay on TD output When SSC is configured with the following conditions: • RCMR.START = Start on falling edge/Start on Rising edge/Start on any edge, • RFMR.FSOS = None (input), • TCMR.START = Receive Start, an unexpected delay of 2 or 3 system clock cycles is added to the TD output. Workaround: None 71.3.23 Issue: I2SC First Sent Data I2SC first sent data corrupted Right after I2SC reset, the first data sent by I2SC controller on the I2SDO line is corrupted. The following data are not affected. Workaround: None 71.3.24 Issue: Quad I/O Serial Peripheral Interface (QSPI) QSPI hangs with long DLYCS QSPI hangs if a command is written to any QSPI register during the DLYCS delay. There is no status bit to flag the end of the delay. Workaround: The field DLYCS defines a minimum period for which Chip Select is de-asserted, required by some memories. This delay is generally < 60 ns and comprises internal execution time, arbitration and latencies. Thus, DLYCS must be configured to be slightly higher than the value specified for the slave device. The software must wait for this same period of time plus an additional delay before a command can be written to the QSPI. DS60001476B-page 2574  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.3.25 Master/Processor Clock Prescaler Issue: Change of the field PMC_MCKR.PRES is not allowed if Master/Processor Clock Prescaler frequency is too high PMC_MCKR.PRES cannot be changed if the clock applied to the Master/Processor Clock Prescaler (see “Master Clock Controller”, in Section 33. “Power Management Controller (PMC)”) is greater than 312 MHz (VDDCORE[1.1, 1.32]) and 394 MHz (VDDCORE[1.2, 1.32]). Workaround: 1. 2. 3. Set PMC_MCKR.CSS to MAIN_CLK. Set PMC_MCKR.PRES to the required value. Change PMC_MCKR.CSS to the new clock source (PLLA_CLK, UPLLCK). 71.3.26 Issue: Master CAN-FD Controller (MCAN) Flexible data rate feature does not support CRC CAN-FD peripheral (BOSCH V320) does not support the CRC scheme which includes the stuff bit count introduced by the ISO standardization committee. CAN 2.0 operation is not impacted. Workaround: None. 71.3.27 Issue: MCAN Interrupt MCAN_IR.MRAF Needless activation of interrupt MCAN_IR.MRAF During frame reception while the MCAN is in Error Passive state and the Receive Error Counter has the value MCAN_ECR.REC = 127, it may happen that MCAN_IR.MRAF is set although there was no Message RAM access failure. If MCAN_IR.MRAF is enabled, an interrupt to the Host CPU is generated. Workaround: The Message RAM Access Failure interrupt routine needs to check whether MCAN_ECR.RP = ’1’ and MCAN_ECR.REC = 127. In this case, reset MCAN_IR.MRAF. No further action is required. 71.3.28 Issue: MCAN Bus Integration State Return of receiver from Bus Integration state after Protocol Exception Event In case a started transmission is aborted shortly before the transmission of the FDF bit, a receiver will detect a recessive FDF bit followed by a recessive res bit. In this case receiving MCANs with Protocol Exception Event Handling enabled will detect a protocol exception event and will enter Bus Integration state. These receivers are expected to leave Bus Integration state after 11 consecutive recessive bits. Instead of starting to count 11 recessive bits directly after entering Bus Integration state, the MCAN needs to see at least one dominant bit. Workaround: Disable Protocol Exception Event Handling (MCAN_CCCR.PXHD = ’1’).  2017 Microchip Technology Inc. DS60001476B-page 2575 SAMA5D2 SERIES 71.3.29 Issue: MCAN Message RAM/RAM Arbiter Message RAM/RAM Arbiter not responding in time When the MCAN wants to store a received frame, and the Message RAM/RAM Arbiter does not respond in time, this message cannot be stored completely and it is discarded with the reception of the next message. Interrupt flag MCAN_IR.MRAF is set. It may happen that the next received message is stored incomplete. In this case, the respective Rx Buffer or Rx FIFO element holds inconsistent data. Workaround: Configure the RAM Watchdog to the maximum expected Message RAM access delay. In case the Message RAM / RAM Arbiter does not respond within this time, the Watchdog Interrupt MCAN_IR.WDI is set. In this case discard the frame received after MCAN_IR.MRAF has been activated. 71.3.30 Issue: MCAN Frame Receiving Data loss (payload) in case storage of a received frame has not completed until end of EOF field is reached This erratum is applicable only if the MCAN peripheral clock frequency is below 77 MHz. During frame reception, the Rx Handler needs access to the Message RAM for acceptance filtering (read access) and storage of accepted messages (write access). The time needed for acceptance filtering and storage of a received message depends on the MCAN peripheral clock frequency, the number of MCANs connected to a single Message RAM, the Message RAM arbitration scheme, and the number of configured filter elements. In case storage of a received message has not completed until the end of the received frame is reached, the following faulty behavior can be observed: • The last write to the Message RAM to complete storage of the received message is omitted, this data is lost. Applies for data frames with DLC > 0, worst case is DLC = 1. • Rx FIFO: FIFO put index MCAN_RXFnS.FnPI is updated although the last FIFO element holds corrupted data. • Rx Buffer: New Data flag MCAN_NDATn.NDxx is set although the Rx Buffer holds corrupted data. • Interrupt flag MCAN_IR.MRAF is not set. Workaround: Reduce the maximum number of configured filter elements for the MCANs attached to the Message RAM until the calculated clock frequency is below the MCAN peripheral clock frequency used with the device. 71.3.31 Issue: MCAN Edge Filtering Edge filtering causes mis-synchronization when falling edge at Rx input pin coincides with end of integration phase When edge filtering is enabled (MCAN_CCCR.EFBI = ’1’) and when the end of the integration phase coincides with a falling edge at the Rx input pin, it may happen that the MCAN synchronizes itself wrongly and does not correctly receive the first bit of the frame. In this case the CRC will detect that the first bit was received incorrectly; it will rate the received FD frame as faulty and an error frame will be sent. The issue only occurs when there is a falling edge at the Rx input pin (CANRX) within the last time quantum (tq) before the end of the integration phase. The last time quantum of the integration phase is at the sample point of the 11th recessive bit of the integration phase. When the edge filtering is enabled, the bit timing logic of the MCAN sees the Rx input signal delayed by the edge filtering. When the integration phase ends, the edge filtering is automatically disabled. This affects the reset of the FD CRC registers at the beginning of the frame. The Classical CRC register are not affected, so this issue does not affect the reception of Classical frames. In CAN communication, the MCAN may enter integrating state (either by resetting MCAN_CCCR.INIT or by protocol exception event) while a frame is active on the bus. In this case the 11 recessive bits are counted between the acknowledge bit and the following start of frame. All nodes have synchronized at the beginning of the dominant acknowledge bit. This means that the edge of the following start of frame bit cannot fall on the sample point, so the issue does not occur. The issue occurs only when the MCAN is, by local errors, missynchronized with regard to the other nodes, or not synchronized at all. Glitch filtering as specified in ISO 11898-1:2015 is fully functional. DS60001476B-page 2576  2017 Microchip Technology Inc. SAMA5D2 SERIES Edge filtering was introduced for applications where the data bit time is at least two tq (of the nominal bit time) long. In that case, edge filtering requires at least two consecutive dominant time quanta before the counter counting the 11 recessive bits for idle detection is restarted. This means edge filtering covers the theoretical case of occasional 1-tq-long dominant spikes on the CAN bus that would delay idle detection. Repeated dominant spikes on the CAN bus would disturb all CAN communication, so the filtering to speed up idle detection would not help network performance. When this rare event occurs, the MCAN sends an error frame and the sender of the affected frame retransmits the frame. When the retransmitted frame is received, the MCAN has left the integration phase and the frame will be received correctly. Edge filtering is only applied during integration phase, it is never used during normal operation. As the integration phase is very short with respect to “active communication time”, the impact on total error frame rate is negligible. The issue has no impact on data integrity. The MCAN enters integration phase under the following conditions: • when MCAN_CCCR.INIT is set to ’0’ after start-up • after a protocol exception event (only when MCAN_CCCR.PXHD = ’0’) Workaround: Disable edge filtering or wait on retransmission in case this rare event happens. 71.3.32 Issue: MCAN_NBTP.NTSEG2 Configuration Configuration of MCAN_NBTP.NTSEG2 = ’0’ not allowed When MCAN_NBTP.NTSEG2 is configured to zero (Phase_Seg2(N) = 1), and when there is a pending transmission request, a dominant third bit of Intermission may cause the MCAN to wrongly transmit the first identifier bit dominant instead of recessive, even if this bit was configured as ’1’ in the MCAN’s Tx Buffer Element. A phase buffer segment 2 of length ’1’ (Phase_Seg2(N) = 1) is not sufficient to switch to the first identifier bit after the sample point in Intermission where the dominant bit was detected. The CAN protocol according to ISO 11898-1 defines that a dominant third bit of Intermission causes a pending transmission to be started immediately. The received dominant bit is handled as if the MCAN has transmitted a Start-of-Frame (SoF) bit. The ISO 11898-1 specifies the minimum configuration range for Phase_Seg2(N) to be 2..8 tq. Therefore excluding a Phase_Seg2(N) of ’1’ will not affect MCAN conformance. Workaround: Use the range 1..127 for MCAN_NBTP.NTSEG2 instead of 0..127. 71.3.33 Issue: MCAN DAR Mode Retransmission in DAR mode due to lost arbitration at the first two identifier bits When the MCAN is configured in DAR mode (MCAN_CCCR.DAR = ’1’) the Automatic Retransmission for transmitted messages that have been disturbed by an error or have lost arbitration is disabled. When the transmission attempt is not successful, the Tx Buffer’s transmission request bit (MCAN_TXBRP.TRPxx) shall be cleared and its cancellation finished bit (MCAN_TXBCF.CFxx) shall be set. When the transmitted message loses arbitration at one of the first two identifier bits, it may happen that instead of the bits of the actually transmitted Tx Buffer, the MCAN_TXBRP.TRPxx and MCAN_TXBCF.CFxx bits of the previously started Tx Buffer (or Tx Buffer 0 if there is no previous transmission attempt) are written (MCAN_TXBRP.TRPxx = ’0’, MCAN_TXBCF.CFxx = ’1’). If in this case the MCAN_TXBRP.TRPxx bit of the Tx Buffer that lost arbitration at the first two identifier bits has not been cleared, retransmission is attempted. When the MCAN loses arbitration again at the immediately following retransmission, then actually and previously transmitted Tx Buffers are the same and this Tx Buffer’s MCAN_TXBRP.TRPxx bit is cleared and its MCAN_TXBCF.CFxx bit is set. Workaround: None.  2017 Microchip Technology Inc. DS60001476B-page 2577 SAMA5D2 SERIES 71.3.34 MCAN Tx FIFO Message Issue: Tx FIFO message sequence inversion Assume the case that there are two Tx FIFO messages in the output pipeline of the Tx Message Handler. Transmission of Tx FIFO message 1 is started: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: -Now a non Tx FIFO message with a higher CAN priority is requested. Due to its priority it will be inserted into the output pipeline. The TxMH performs so called "message scans" to keep the output pipeline up to date with the highest priority messages from the Message RAM. After the following two message scans, the output pipeline has the following content: Position 1: Tx FIFO message 1 (transmission ongoing) Position 2: non Tx FIFO message with higher CAN priority Position 3: Tx FIFO message 2 If the transmission of Tx FIFO message 1 is not successful (lost arbitration or CAN bus error) it is pushed from the output pipeline by the non Tx FIFO message with higher CAN priority. The following scan re-inserts Tx FIFO message 1 into the output pipeline at position 3: Position 1: non Tx FIFO message with higher CAN priority (transmission ongoing) Position 2: Tx FIFO message 2 Position 3: Tx FIFO message 1 Now Tx FIFO message 2 is in the output pipeline in front of Tx FIFO message 1 and they are transmitted in that order, resulting in a message sequence inversion. Workaround: 1. First Workaround Use two dedicated Tx Buffers, e.g. use Tx Buffers 4 and 5 instead of the Tx FIFO. The pseudo-code below replaces the function that fills the Tx FIFO. Write message to Tx Buffer 4. Transmit Loop: • • • • • • 2. Request Tx Buffer 4 - write MCAN_TXBAR.A4 Write message to Tx Buffer 5 Wait until transmission of Tx Buffer 4 completed - MCAN_IR.TC, read MCAN_TXBTO.TO4 Request Tx Buffer 5 - write MCAN_TXBAR.A5 Write message to Tx Buffer 4 Wait until transmission of Tx Buffer 5 completed - MCAN_IR.TC, read MCAN_TXBTO.TO5 Second Workaround Assure that only one Tx FIFO element is pending for transmission at any time. The Tx FIFO elements may be filled at any time with messages to be transmitted, but their transmission requests are handled separately. Each time a Tx FIFO transmission has completed and the Tx FIFO gets empty (MCAN_IR.TFE = ’1’) the next Tx FIFO element is requested. 3. Third Workaround Use only a Tx FIFO. Send the message with the higher priority also from Tx FIFO. Drawback: The higher priority message has to wait until the preceding messages in the Tx FIFO have been sent. DS60001476B-page 2578  2017 Microchip Technology Inc. SAMA5D2 SERIES 71.3.35 MCAN High Priority Message (HPM) Issue: Unexpected High Priority Message (HPM) interrupt There are two configurations where the issue occurs: Configuration A: • At least one Standard Message ID Filter Element is configured with priority flag set (S0.SFEC = "100"/"101"/"110") • No Extended Message ID Filter Element configured • Non-matching extended frames are accepted (MCAN_GFC.ANFE = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority extended message under the following conditions: 1. 2. A standard HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next an extended frame is received and accepted because of MCAN_GFC.ANFE configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Configuration B: • At least one Extended Message ID Filter Element is configured with priority flag set (F0.EFEC = "100"/"101"/"110") • No Standard Message ID Filter Element configured • Non-matching standard frames are accepted (MCAN_GFC.ANFS = "00"/"01") The HPM interrupt flag MCAN_IR.HPM is set erroneously on reception of a non-high-priority standard message under the following conditions: 1. 2. An extended HPM frame is received, and accepted by a filter with priority flag set. Then, interrupt flag MCAN_IR.HPM is set as expected. Next a standard frame is received and accepted because of MCAN_GFC.ANFS configuration. Then, interrupt flag MCAN_IR.HPM is set erroneously. Workaround: Configuration A: Setup an Extended Message ID Filter Element with the following configuration: • • • • F0.EFEC = "001"/"010" - select Rx FIFO for storage of extended frames F0.EFID1 = any value - value not relevant as all ID bits are masked out by F1.EFID2 F1.EFT = "10" - classic filter, F0.EFID1 = filter, F1.EFID2 = mask F1.EFID2 = zero - all bits of the received extended ID are masked out Now all extended frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of F0.EFEC. Configuration B: Setup a Standard Message ID Filter Element with the following configuration: • • • • S0.SFEC = "001"/"010" - select Rx FIFO for storage of standard frames S0.SFID1 = any value - value not relevant as all ID bits are masked out by S0.SFID2 S0.SFT = "10" - classic filter, S0.SFID1 = filter, S0.SFID2 = mask S0.SFID2 = zero - all bits of the received standard ID are masked out Now all standard frames are stored in Rx FIFO 0 respectively Rx FIFO 1 depending on the configuration of S0.SFEC.  2017 Microchip Technology Inc. DS60001476B-page 2579 SAMA5D2 SERIES 71.3.36 Issue: ROM Code: Using JTAG IOSET 4 JTAG_TCK on IOSET 4 pin has a wrong configuration after boot The JTAG_TCK signal on IOSET 4 shares its pin (PA22) with the clock signal of the following boot memory interfaces: SDMMC1, SPI1 IOSET 2, QSPI 0 IOSET 3. If JTAG IOSET 4 is selected by the user as JTAG debug port in the Boot Configuration Word, and if the ROM Code boots, or tries to boot, on any of the external memory interfaces stated above, the JTAG clock pin (TCK) is reset at its default mode (PIO) at the end of the ROM Code execution. This occurs as soon as EXT_MEM_BOOT_ENABLE is set. Workaround: Do not select, or disable, external memory boot interface SDMMC1, SPI1 IOSET 2 or QSPI0 IOSET 3. However, if using one of these boot interfaces is required, reconfigure the PA22 pin in JTAG TCK IOSET 4 mode in the bootstrap or application. DS60001476B-page 2580  2017 Microchip Technology Inc. SAMA5D2 SERIES 72. Revision History Table 72-1: Issue Date SAMA5D2 Datasheet DS60001476 Rev. B Revision History Changes Section 6. “Package and Pinout” Table 6-2 Pin Description: added notes (2) and (3). Table 6-3 Pin Description (SAMA5D23 pins different from those in Table 6-2 “Pin Description”): added note (2) . Table 6-4 Pin Description (SAMA5D28B/C pins different from those in Table 6-2 “Pin Description”): added note (2). Section 7. “Power Considerations” Updated Figure 7-1 “Recommended Powerup Sequence” and Table 7-2 “Powerup Timing Specification”. Section 16. “Standard Boot Strategies” Updated Section 16.4.7.3 “SDCard / e.MMC Boot”. Reworked Section 16.4.7.6 “QSPI NOR Flash Boot for MRL C”. Section 29. “Peripheral Touch Controller (PTC)” - Replaced "Peripheral Touch Controller" with "Peripheral Touch Controller Subsystem". - Changed "PTC_IRQ_EVT" to "PTC_IRQ". - Replaced "PIO" and "IO" with "GPIO". Updated: Jul-2017 - Figure 29-1. "PTC Block Diagram" - Section 29.2 “Embedded Characteristics” - Section 29.5.2 “I/O Lines” - Section 29.5.3 “Interrupt Sources” - Section 29.6.2.3 “Firmware in SRAM Code Area” Section 29.5.1 “Power Management”: updated description of “SLCK”. Section 29.6.3.1 “PTC Digital Controller Operations”: modified Sensing mode description. Renamed and reworked Section 29.7.1 “PTC Command Register” and Section 29.7.2 “PTC Interrupt Status Register”. Section 29.7.3 “PTC Enable Register”: removed field CLR_IRQEN, and replaced field SET_IRQEN with bits IER0, IER1, IER2, IER3. Renamed the following registers: - “Mode 1: Write Access” to “PTC Command Register” - “Host Flags” to “PTC Interrupt Status Register” - “Host Flags Control” to “PTC Enable Register” Section 39. “LCD Controller (LCDC)” Corrected Figure 39-1. Block Diagram (added “PP Layer” block). cont’d on next page DS60001476B-page 2582  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-1: Issue Date SAMA5D2 Datasheet DS60001476 Rev. B Revision History Changes Section 66. “Electrical Characteristics” Added Section 66.10 ”PTC Characteristics”. Section 66.5.3.1 “ULP0 Mode”: updated steps (5) and (6). Table 66-9 “Typical Peripheral Power Consumption by Peripheral in Active Mode”: corrected UHPHS consumption value from "12 *MCK + 4900*DR" to "12 *MCK + 490*DR" and UDPHS consumption value from “10 *MCK + 2060*DR” to “10 *MCK + 206*DR” Table 66-13 “VDDCORE Power Consumption in Ultra Low-power Mode: AMP2”: removed ULP0 512 Hz row. Section 68. “Schematic Checklist” Removed Section 68.3 “Shutdown Considerations” and Section 68.4 “Wakeup Considerations” (redundant with content in Section 7. “Power Considerations”). Table 68-1 “Power Supply Connections”: updated VDDCORE recommended pin connection from “1.08V to 1.32V” to “1.1V to 1.32V”. Jul-2017 Table 68-2 “Clock, Oscillator and PLL Connections”: updated main oscillator recommended pin connection from "Crystals between 8 and 16 MHz" to "Crystals between 8 and 24 MHz". Table 68-6 “Reset and Test Connections”: updated NRST recommended pin connection. Section 69. “Marking” Updated marking information. Section 71. “Errata” Added the following issues in Section 71.1 “Errata - SAMA5D2 MRL C Parts”: Section 71.1.9 “Master CAN-FD Controller (MCAN)” to Section 71.1.18 “MCAN High Priority Message (HPM)” and Section 71.1.19 “ROM Code: Using JTAG IOSET 4”. Added the following issues in Section 71.2 “Errata - SAMA5D2 MRL B Parts”: Section 71.2.10 “Master CAN-FD Controller (MCAN)” to Section 71.2.19 “MCAN High Priority Message (HPM)” and Section 71.2.20 “ROM Code: Using JTAG IOSET 4”. Added the following issues in Section 71.3 “Errata - SAMA5D2 MRL A Parts”: Section 71.3.26 “Master CAN-FD Controller (MCAN)” to Section 71.3.35 “MCAN High Priority Message (HPM)” and Section 71.3.36 “ROM Code: Using JTAG IOSET 4”. End  2017 Microchip Technology Inc. DS60001476B-page 2583 SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes General - Template update: Moved from Atmel to Microchip template. - The datasheet is assigned a new document number (DS60001476) and revision letter is reset to A. --- Document number DS60001476 revision A corresponds to what would have been 11267 revision F. - ISBN number assigned. “Features” : added PTC. Table 2. “Configuration Summary”: added PTC. Corrected number of Timers. Section 3. “Block Diagram” Figure 3-1. SAMA5D2 Series Block Diagram: corrected SDMMC signals. Updated peripheral bridge naming. Added PTC. Removed signal names. Section 4. “Signal Description” Table 4-1 “Signal Description List”: renamed SDMMCx_VDDSEL to SDMMCx_1V8SEL. Added PTC pins on PD0 to PD18. Added Section 5. “Safety and Security Features”. Mar-2017 Section 6. “Package and Pinout” Added Note on IO sets. Table 6-2 “Pin Description”: for P15/R14 renamed SDMMC0_VDDSEL to SDMMC0_1V8SEL. Section 7. “Power Considerations” Table 7-1 “SAMA5D2 Power Supplies”: in VDDBU row, corrected RC Oscillator frequency to 64 kHz. Section 8. “Memories” Figure 8-1. Memory Mapping: renamed MATRIXx blocks. Added PTC. Renamed TC blocks. Added SYSCWP block. Section 12. “Chip Identifier (CHIPID)” Table 12-1 “SAMA5D2 Chip ID Registers”: added chip ids for MRL C revision. Section 11. “Peripherals” Table 11-1 “Peripheral Identifiers”: corrected reference to SDMMC. Assigned ID 58 to Peripheral Touch Controller (PTC). Section 11.4 “Peripheral Clock Types”: removed clock type HCLOCK and PCLOCK from table. Section 13. “ARM Cortex-A5” Section 13.4.7.3 “Debug”: updated Note. cont’d on next page DS60001476B-page 2584  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 16. “Standard Boot Strategies” Replaced all occurrences of “Spansion” by “Cypress”. Updated Section 16.3 “Chip Setup”. Updated Section 16.4.1 “Boot Configuration Word”. Section 16.4.2 “Boot Sequence Controller Configuration Register”: updated BUREG_VALID bit description. Added Note to descriptions of SDMMC_0 and SDMMC_1 in Section 16.4.4 “Boot Configuration Word”. Updated Section 16.4.5 “NVM Boot Sequence” and figures. Renamed Section 16.4.7.5 “QSPI NOR Flash Boot for MRL A and MRL B”. Added Section 16.4.7.6 “QSPI NOR Flash Boot for MRL C”. Updated Section 16.4.8 “Hardware and Software Constraints”: -- added Table 16-6 “Clock Frequencies during External Memory Boot Sequence”. -- Table 16-7 “PIO Driven during Boot Program Execution”: renamed SDMMC_VDDSEL to SDMMC0_1V8SEL. Added column “Drive Strength (MRL C only)”. Section 16.5 “SAM-BA Monitor”: deleted sentence on Main Clock; updated 3rd paragraph. Updated Section 16.6.1 “Fuse Bit Mapping”. Section 18. “Matrix (H64MX/H32MX)” Table 18-5 “List of H32MX Slaves”: added Peripheral Touch Controller (PTC) at Slave 6. Table 18-6 “Master to Slave Access on H32MX”: added Peripheral Touch Controller (PTC) at Slave 6. Table 18-9 “Peripheral Identifiers”: added PTC at ID 58. Mar-2017 Section 19. “Special Function Registers (SFR)” Section 19.3.5 “UTMI Clock Trimming Register”: VBG now 2 bits wide at index [17:16] (was [19:16]). Section 20. “Special Function Registers Backup (SFRBU)” Section 20.3.3 “SFRBU DDR BU Mode Control Register” changed occurrences of VCCCORE to VDDCORE. Section 26. “Real-time Clock (RTC)” Table 26-1 “Register Mapping”: updated offsets as of 0xCC. Deleted RTC_WPMR at offset 0xE4. Deleted “Section 25.6.23 RTC Write Protection Mode Register”. Added Section 27. “System Controller Write Protection (SYSCWP)”. Added Section 29. “Peripheral Touch Controller (PTC)”. Section 33. “Power Management Controller (PMC)” Reorganized order of sub-sections within the chapter. Updated Figure 33-2. H32MX 32-bit Matrix Clock Configuration. Figure 33-1. General Clock Block Diagram: updated PMC_PCR block. Added Section 33.8 “Core and Bus Independent Clocks for Peripherals”. Added Section 33.9 “Peripheral and Generic Clock Controller”. Deleted section “Peripheral Clock Controller”. Deleted section “Generic Clock Controller”. Figure 33-10. Clock Failure Detection (Example): corrected CDFEV to CFDEV and CDFS to CFDS. Section 33.19 “Programming Sequence”: deleted paragraph on DIVA from Step 6. Section 33.22.10 “PMC Clock Generator PLLA Register”: changed DIVA description for value ‘0’. cont’d on next page  2017 Microchip Technology Inc. DS60001476B-page 2585 SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 35. “External Memories” Updated Figure 35-2. MPDDRC Block Diagram. Table 35-1 “DDR/LPDDR I/O Lines Description”: DDR_DQS[3:0] and DDR_DQSN[3:0] now type I/O. Aligned signal names in schematics of Section 35.1 “Multiport DDR-SDRAM Controller (MPDDRC)” with signal names in Table 35-2 “I/O Lines Usage vs Operating Modes”. Section 36. “Multiport DDR-SDRAM Controller (MPDDRC)” Section 36.1 “Description”: corrected supported CAS latency. Section 36.4.1 “Low-power DDR1-SDRAM Initialization”: updated Step 12. Section 36.4.2 “DDR2-SDRAM Initialization”: updated Step 22. Section 36.4.3 “Low-power DDR2-SDRAM Initialization”: updated Step 22. Section 36.4.4 “DDR3-SDRAM/DDR3L-SDRAM Initialization”: updated Step 13. Section 36.4.5 “Low-power DDR3-SDRAM Initialization”: updated Step 22. Table 36-1 “CAS Write Latency”: added row for Low-power DDR3-SDRAM. Corrected typo in note. Table 36-2 “CAS Read Latency”: added row for Low-power DDR3-SDRAM. Corrected typo in note. Mar-2017 Section 36.7.2 “MPDDRC Refresh Timer Register”: updated the method to compute COUNT. Section 36.7.3 “MPDDRC Configuration Register”: updated NC field description table. Section 36.7.6 “MPDDRC Timing Parameter 2 Register”: in TRPA description, added “In the case of LPDDR2-SDRAM, this field is equivalent to tRPAB.” Section 36.7.10 “MPDDRC Low-power DDR2 Low-power DDR3 and DDR3 Calibration and MR4 Register”: in COUNT_CAL field description, added ‘One ZQCS command can effectively correct at least 1.5% of output impedance errors within Tzqcs.’ and ‘TSens and VSens are given by the manufacturer (Output Driver Sensitivity definition). Tdriftrate and Vdriftrate are defined by the end user.’ Section 38. “DMA Controller (XDMAC)” Added information regarding XDMAC_CC.INITD in Section 38.8 “XDMAC Software Requirements” and Section 38.9.28 “XDMAC Channel x [x = 0..15] Configuration Register”. Section 38.9.3 “XDMAC Global Weighted Arbiter Configuration Register”: replaced “XDMAC scheduler” with “DMAC scheduler” throughout. Section 39. “LCD Controller (LCDC)” Standardized signal names from ‘LCD_XXX’ to ‘LCDXXX’ (‘underscore’ character removed) Section 39.2 “Embedded Characteristics”: removed “(at synthesis time)” from characteristic “Asynchronous Output Mode Supported”. cont’d on next page DS60001476B-page 2586  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 40. “Ethernet MAC (GMAC)” Section 40.2 “Embedded Characteristics”: deleted queue sizes (now found in Table 40-6 “Queue Size”). Table 40.6.3.9 “Priority Queueing in the DMA”: added Table 40-6 “Queue Size” and updated queue sizes. Section 40.6.15 “Timestamp Unit”: changed pin reference from “TIOB11/PD22” to “TIOA11/PD21”. Added Section 40.6.18 “Energy-efficient Ethernet Support” Updated Section 40.6.19 “802.1Qav Support - Credit-based Shaping”: added definitions of portTransmitRate and IdleSlope; updated content on queue priority management. Added Section 40.6.20 “LPI Operation in the GMAC”. Table 40-18 “Register Mapping”: added registers at offsets 0x270 to 0x27C. Section 40.8.1 “GMAC Network Control Register”: added bit 19: TXLPIEN: Enable LPI Transmission (was ‘reserved’). Added bit description. Changed description of SRTSM bit. Section 40.8.3 “GMAC Network Status Register”: added bit 7: RXLPIS: LPI Indication (was ‘reserved’). Added bit description. Added bit 27: RXLPISBC: Receive LPI indication Status Bit Change and bit description and added bit 29: TSUTIMCOMP: TSU timer comparison interrupt and bit description in: - Section 40.8.10 “GMAC Interrupt Status Register” - Section 40.8.11 “GMAC Interrupt Enable Register” - Section 40.8.12 “GMAC Interrupt Disable Register” Mar-2017 - Section 40.8.13 “GMAC Interrupt Mask Register” Section 40.8.13 “GMAC Interrupt Mask Register”: added bit 26, SRI, and bit 28, WOL, and bit descriptions. Added following sections: - Section 40.8.106 “GMAC Received LPI Transitions” - Section 40.8.107 “GMAC Received LPI Time” - Section 40.8.108 “GMAC Transmit LPI Transitions” - Section 40.8.109 “GMAC Transmit LPI Time” Section 40.8.115 “GMAC Credit-Based Shaping IdleSlope Register for Queue A” and Section 40.8.116 “GMAC Credit-Based Shaping IdleSlope Register for Queue B”: updated example for calculation of IdleSlope. Section 41. “USB High Speed Device Port (UDPHS)” Table 41-6 “Register Mapping”: offsets 0xD0 to 0xDC now ‘reserved’. Deleted internal registers: - UDPHS Test SOF Counter Register - UDPHS Test A Counter Register - UDPHS Test B Counter Register - UDPHS Test Mode Register Section 43. “Audio Class D Amplifier (CLASSD)” Section 43.6.6 “Application Schematics For Use Case Examples”: for Use Case 1, added information on external MOSFET selection. cont’d on next page  2017 Microchip Technology Inc. DS60001476B-page 2587 SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 44. “Inter-IC Sound Controller (I2SC)” In text, tables and figures, pin names changed to: - I2SC_MCK - I2SC_CK - I2SC_WS - I2SC_DI - I2SC_DO Updated Figure 44-1. I2SC Block Diagram. Section 44.6.1 “Initialization”: added detail on configuring SFR_I2SCLKSEL. Section 44.6.5 “Serial Clock and Word Select Generation”: updated paragraph on I2SC input clock selection in Master mode. Updated Figure 44-3. I2SC Clock Generation. Updated figures in Section 44.7 “I2SC Application Examples”. Section 44.8.2 “I2SC Mode Register”: updated MODE bit description for value ‘1’. Updated IMCKDIV and IMCKMODE field descriptions. Mar-2017 Section 46. “Two-wire Interface (TWIHS)” Added Section 46.7.2 “TWIHS Control Register (FIFO_ENABLED)”. Added Section 46.7.8 “TWIHS Status Register (FIFO_ENABLED)”. Section 47. “Flexible Serial Communication Controller (FLEXCOM)” Corrected Figure 47-27. RTS Line Software Control when FLEX_US_MR.USART_MODE = 2. Reworked Section 47.7.11 “USART FIFOs”. Updated Section 47.8.3.5 “Peripheral Selection”. Reworked Section 47.8.7 “SPI FIFOs”. Section 47.9.3.9 “SMBus Mode”: corrected typo in SMBEN bit name (was ‘SMEN’). Created Section 47.9.6 “TWI FIFOs” by merging Section 10.3.15 “TWI Master Mode FIFOs” and Section 10.5.9 “TWI Slave Mode FIFOs” Section 47.10.43 “SPI Control Register”: updated TXFCLR and RXFCLR bit descriptions. Section 47.10.50 “SPI Status Register”: updated RDRF and TDRE bit descriptions. Section 47.10.55 “SPI FIFO Mode Register”: updated TXRDYM description for value ‘1’. Deleted row for value ‘2’. Updated RXRDYM description for value ‘1’ and for value ‘2’. Added Section 47.10.61 “TWI Control Register (FIFO_ENABLED)”. Added Section 47.10.67 “TWI Status Register (FIFO ENABLED)”. cont’d on next page DS60001476B-page 2588  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 49. “Serial Peripheral Interface (SPI)” Section 49.7.3.5 “Peripheral Selection”: modified sub-section “Variable Peripheral Select Mode”. Section 49.7.5 “SPI Comparison Function on Received Character”: replace ‘When the CMPMODE bit is cleared in SPI_CMPR’ with ‘When SPI_MR.CMPMODE is cleared’ In Section 49.7.7 “FIFOs” updated: - Section 49.7.7.1 “Overview” - Section 49.7.7.2 “Sending Data with FIFO Enabled” - Section 49.7.7.3 “Receiving Data with FIFO Enabled” - Section 49.7.7.5 “TXEMPTY, TDRE and RDRF Behavior” - Section 49.7.7.6 “Single Data Mode” - Section 49.7.7.7 “Multiple Data Mode” - “TDRE and RDRF Configuration” Section 49.8.1 “SPI Control Register”: updated TXFCLR and RXFCLR bit descriptions. Section 49.8.8 “SPI Status Register”: updated RDRF and TDRE bit descriptions. Mar-2017 Section 49.8.13 “SPI FIFO Mode Register”: updated TXRDYM description for value ‘1’. Deleted row for value ‘2’. Updated RXRDYM description for value ‘1’ and for value ‘2’. Updated “DMAC” in Section 49.7.7.7 “Multiple Data Mode”. Section 50. “Quad Serial Peripheral Interface (QSPI)” Section 50.1 “Description”: added Note on device support. Removed references to Double Data Rate (DDR) in Section 50.2 “Embedded Characteristics” and Section 50.6.5.2 “Instruction Frame Transmission”. Section 50.6.5 “QSPI Serial Memory Mode”: updated text on data transfer constraint. Updated Figure 50-8. Instruction Frame. Figure 50-9. Instruction Transmission Flow Diagram: - Corrected typos: --- “Wait for flag QSPI_SR.INSTRE ... “ (was “QSPI_CR“) --- “Wait for flag QSPI_SR.CSR ... “ (was “QSPI_CR“) - Added new instruction: “Read QSPI_SR (dummy read) to clear QSPI_SR.INSTRE and QSPI_SR.CSR“ Updated Figure 50-10. Continuous Read Mode, Figure 50-16. Instruction Transmission Waveform 6, Figure 50-17. Instruction Transmission Waveform 7 and Figure 50-18. Instruction Transmission Waveform 8. cont’d on next page  2017 Microchip Technology Inc. DS60001476B-page 2589 SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 51. “Secure Digital MultiMedia Card Controller (SDMMC)” Section 51.2 “Embedded Characteristics”: updated bullets on support for MMC at default speed and at high speed. Section 51.3 “Embedded Features for SDMMC0 and SDMMC1”: updated information on SDMMC1. Section 51.10.1.3 “Boot Procedure, ADMA Mode”: removed note after step j. Section 51.13.2 “SDMMC Block Size Register” updated BLKSIZE field description. Section 51.13.9 “SDMMC Present State Register”: updated BUFWREN field description. Section 51.13.16 “SDMMC Clock Control Register”: updated SDCLKFSEL field description. Section 51.13.17 “SDMMC Timeout Control Register”: updated equation in DTCVAL field description. Section 51.13.18 “SDMMC Software Reset Register”: in SWRSTALL field description, updated list of registers cleared to 0 . Section 51.13.21 “SDMMC Error Interrupt Status Register (SD_SDIO)”: in CURLIM bit description, corrected reference to SDMMC_PCR (was SDMMC_PSR). Section 51.13.22 “SDMMC Error Interrupt Status Register (e.MMC)”: updated ACMD bit description. Section 51.13.31 “SDMMC Auto CMD Error Status Register”: changed register access to Read-only. Section 51.13.32 “SDMMC Host Control 2 Register (SD_SDIO)”: corrected typo in bit 7 name (is SCLKSEL; was SLCKSEL). Updated VS18EN bit description. Section 51.13.33 “SDMMC Host Control 2 Register (e.MMC)”: corrected typo in bit 7 name (is SCLKSEL; was SLCKSEL). Section 51.13.41 “SDMMC Preset Value Register”: in Table 51-8 “Preset Value Register Select Condition”: corrected HSEN value in row for High Speed. Mar-2017 Section 51.13.45 “SDMMC e.MMC Control 1 Register”: in DDR bit description Note, replaced ‘HSEN’ with ‘DDR’. Section 51.13.51 “SDMMC Retuning Counter Value Register”: updated description for TCVAL. Section 53. “Controller Area Network (MCAN)” Section 53.1 “Description”: updated information on compliance. Section 53.4.4 “Address Configuration”: added cross-reference for clarity. Section 53.5.1.4 “Transmitter Delay Compensation”: changed NTSEG1 to TSEG1. Section 54. “Timer Counter (TC)” Table 54-1 “Timer Counter Clock Assignment”: added Note below table. Section 54.6.16.2 “Input Preprocessing”: removed unit following equation in 3rd paragraph. Added limitation on maximum pulse duration. Section 54.6.16.4 “Position and Rotation Measurement”: in 3rd paragraph, added “The process must be started by configuring TC_CCR.CLKEN and TC_CCR.SWTRG.” Section 54.6.16.6 “Detecting a Missing Index Pulse”: corrected value of TC_RC0.RC in example in 2nd paragraph. Added Section 54.6.16.7 “Detecting Contamination/Dust at Rotary Encoder Low Speed”. Section 54.7.16 “TC Block Mode Register”: updated MAXFILT field description. In Section 54.7.17 “TC QDEC Interrupt Enable Register”, Section 54.7.18 “TC QDEC Interrupt Disable Register” and Section 54.7.19 “TC QDEC Interrupt Mask Register”: at index 3, added bit MPE and bit description. Corrected occurrences of ‘MAXMP’ to ‘MAXCMP’ in Section 54.7.19 “TC QDEC Interrupt Mask Register” and in Section 54.7.20 “TC QDEC Interrupt Status Register” cont’d on next page DS60001476B-page 2590  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 56. “Pulse Width Modulation Controller (PWM)” Section 56.6.2.2 “Comparator”: corrected ‘CRPD’ to ‘CPRD’ in formulae. Table 56-8 “Register Mapping”: modfied offsets for “PWM External Trigger Register 1”, “PWM Leading-Edge Blanking Register 1”, “PWM External Trigger Register 2” and “PWM Leading-Edge Blanking Register 2”. Section 56.7.43 “PWM Channel Period Register”: corrected ‘CRPD’ to ‘CPRD’ in CPRD description. Section 56.7.44 “PWM Channel Period Update Register”: corrected ‘CRPDUPD’ to ‘CPRDUPD’ in CPRDUDP description. Section 57. “Secure Fuse Controller (SFC)” Removed all occurrences of ‘Atmel reserved area’ ( now just ‘reserved area’). Modified bit names for APLE and ACE in: - Section 57.5.3 “SFC Interrupt Enable Register” - Section 57.5.4 “SFC Interrupt Disable Register” - Section 57.5.5 “SFC Interrupt Mask Register” - Section 57.5.6 “SFC Status Register” Section 58. “Integrity Check Monitor (ICM)” Updated Section 58.5.5 “ICM Automatic Monitoring Mode”. Section 58.6.1 “ICM Configuration Register”: updated ASCD description. Mar-2017 Section 59. “Advanced Encryption Standard Bridge (AESB)” Section 59.1 “Embedded Characteristics”: replaced "12 clock cycles encryption/decryption processing time with a 128-bit cryptographic key" with "10 clock cycles encryption/decryptioninherent processing time". In Section 59.3.6 “Automatic Bridge Mode”, updated Section 59.3.6.1 “Description”. Section 60. “Advanced Encryption Standard (AES)” Replaced references to “keys” and to “AES_KEYWRx registers” with “AES Key Registers”. Section 60.1 “Description”: corrected index of AES_KEYWR0 registers from 3 to 7. Section 60.2 “Embedded Characteristics” replaced “12/14/16 Clock Cycles Encryption/Decryption Processing Time” with “10/12/14 Clock Cycles Encryption/Decryption Inherent Processing Time” Section 61. “Secure Hash Algorithm (SHA)” Corrected typos in some figures. Section 61.4.9.1 “Manual Mode”: updated Step 2. Section 61.5.2 “SHA Mode Register”: updated SMOD bit description. Section 62. “Triple Data Encryption Standard (TDES)” Replaced references to “TDES_KEYxWRx registers” with “Key Registers”. Section 63. “True Random Number Generator (TRNG)” Section 63.6.1 “TRNG Control Register”: changed field name to WAKEY (was KEY). Added Section 64. “Security Module (SECUMOD)”. cont’d on next page  2017 Microchip Technology Inc. DS60001476B-page 2591 SAMA5D2 SERIES Table 72-2: Issue Date SAMA5D2 Datasheet DS60001476 Rev. A Revision History Changes Section 65. “Analog-to-Digital Converter (ADC)” Section 65.5.3 “I/O Lines”: “ADC_ADTRG” corrected to “ADTRG”. Section 65.6.14 “Automatic Error Correction”: added information about ADCMODE field. Table 65-7 “ADC Running Modes”: updated Offset Error row. Section 65.6.18 “Fault Event”: reworked and renamed section (was previously “Fault Output”). Section 65.7.2 “ADC Mode Register”: at index 30, added bit MAXSPEED and bit description Section 65.7.12 “ADC Interrupt Status Register”: updated LCCHG bit description. Section 65.7.20 “ADC Analog Control Register”: added Note (1). Section 66. “Electrical Characteristics” Table 66-3 “DC Characteristics”: updated min and max valued for low-level and high-level input currents (all pads). Changed ISI_MCK to ISC_MCK. Updated Table 66-8 “Typical Peripheral Power Consumption by Peripheral in Active Mode” with new column “Clock”. Table 66-10 “Power Consumption in Active Mode: AMP2”: Removed columns DMIPS and CoreMark. In Section 66.15 “FLEXCOM Timings”, added Section 66.15.1 “FLEXCOM USART in Asynchronous Modes” and Section 66.15.3 “FLEXCOM TWI Timings”. In Section 66.15.2 “FLEXCOM SPI Timings”, removed note below all tables from Table 66-53 “FLEXCOM0 in SPI Mode IOSET1 Timings” to Table 66-62 “FLEXCOM4 in SPI Mode IOSET3 Timings”. Added Section 66.16 “USART in Asynchronous Modes”. Mar-2017 Section 66.17 “SPI Timings”: updated limitation on fSPCK in “Master Read Mode” and “Slave Write Mode” . Removed note below Table 66-64 “SPI0 IOSET1 Timings”, Table 66-65 “SPI0 IOSET2 Timings”, Table 66-66 “SPI1 IOSET1 Timings”, Table 66-67 “SPI1 IOSET2 Timings” and Table 66-68 “SPI1 IOSET3 Timings”. Section 66.19 “QSPI Timings”: updated limitation on fQSCK in “Master Read Mode” . Section 66.20.3 “LPDDR1-SDRAM”, Table 66-77 “System Clock Waveform Parameters”: updated min value of tDDRCK for VDDCORE[1.2V, 1.32V]. Section 66.20.4 “LPDDR2/LPDDR3-SDRAM”, Table 66-78 “System Clock Waveform Parameters”: updated min value of tDDRCK for VDDCORE[1.2V, 1.32V]. Section 66.20.5 “DDR3/DDR3L-SDRAM”: updated min values in Table 66-79 “System Clock Waveform Parameters”. Section 66.24 “ISC Timings”: updated Figure 66-40. ISC Timing Diagram and Timings tables. Section 68. “Schematic Checklist” Table 68-1 “Power Supply Connections”: removed reference to VCCCORE. Added Section 68.12.7 “Considerations for PTC Interface”. Section 70. “Ordering Information” Updated Table 70-1 “SAMA5D2 Ordering Information” with MRL C ordering codes. Section 71. “Errata” Added Section 71.1 “Errata - SAMA5D2 MRL C Parts”. Section 71.2 “Errata - SAMA5D2 MRL B Parts”: added Section 71.1.1 “GMAC Timestamps and PTP packets”. Section 71.3 “Errata - SAMA5D2 MRL A Parts”: added - Section 71.1.1 “GMAC Timestamps and PTP packets” - Section 71.3.4 “ROM Code: SPI Bootup Frequency”. End DS60001476B-page 2592  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-3: Issue Date 25-Jul-16 Table 72-4: SAMA5D2 Datasheet Rev. 11267E Revision History Changes Deleted Section 61. “Security Module”. SAMA5D2 Datasheet Rev. 11267D Revision History Issue Date Changes Minor formatting and editorial changes throughout “Introduction” Updated listed DDR memories “Features” Frequency of digital fractional PLL for audio “11.289 MHz” corrected to “11.2896 MHz” “Two 64-bit, 16-channel DMA controllers” changed to “51 DMA Channels including two 16-channel 64-bit Central DMA Controllers” Section 1. “Description” Updated description of Low-power modes Section 2. “Configuration Summary” “Class D amplifier” changed to “stereo Class D amplifier” Updated text at end of section Section 3. “Block Diagram” Figure 3-1 “SAMA5D2 Series Block Diagram”: added ISC_MSK input; updated description of crystal oscillators; “PWMEXTRIG0-1” renumbered to “PWMEXTRG1–2” Added note “See Section 35. “DMA Controller (XDMAC)” for peripheral connections to DMA.” 12-May-16 Section 4. “Signal Description” Table 4-1 “Signal Description List”: NRST signal function “Microcontroller Reset” changed to “Microprocessor Reset”; “PWMEXTRG0-1” renumbered to “PWMEXTRG1–2”; “Self-refresh mode” changed to “Backup Self-refresh mode” in DDR_CKE comments Section 5. “Package and Pinout” Separated content into Section 5.1 “Packages” and Section 5.2 “Pinouts” Table 5-2 “Pin Description (SAMA5D21, SAMA5D22, SAMA5D24, SAMA5D26, SAMA5D27, SAMA5D28A)”: “ADVREFP” corrected to “ADVREF”; “PWMEXTRG0” and “PWMEXTRG1” renumbered to “PWMEXTRG1” and “PWMEXTRG2”; removed empty function cells for primary signals PA30, PA31, and PB0–PB7; removed “SEC, FILTER” from “Reset State” column header; added footnote on reset states Added Table 5-3 “Pin Description (SAMA5D23 pins different from those in SAMA5D21/SAMA5D22)” and Table 5-4 “Pin Description (SAMA5D28B pins different from those in SAMA5D28A)” Section 6. “Power Considerations” Table 6-1 “SAMA5D2 Power Supplies”: updated rows VDDUTMIC, VDDHSIC and VDDOSC Section 6.4.1 “VDDBU Power Architecture”: reworded second paragraph and deleted “typically less than 2 µA” Section 7. “Memories” Section 7.2.1 “External Bus Interface”: “The slew rates are determined by programming the SFR_EBICFG bit in SFR registers” changed to “The drive levels are configured with the DRIVEx field in the EBI Configuration Register (SFR_EBICFG)”  2017 Microchip Technology Inc. DS60001476B-page 2593 SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 8. “Event System” Section 8-1 “Real-time Event Mapping List”: instance of “ADC_ADTRG” corrected to “ADTRG” Section 9. “System Controller” Section 9.1 “Power-On Reset”: “dedicated to VDDBU, VDDIOP and VDDCORE” changed to “dedicated to monitoring VDDBU, VDDIOP and VDDCORE” Section 10. “Peripherals” Table 10-1 “Peripheral identifiers”: in ‘Instance Name’ column, renamed CAN0 and CAN1 to MCAN0 and MCAN1 Section 10.4 “Peripheral Clock Types”: in SLOW_CLOCK description, “32768-Hz crystal oscillator or by the on-chip 32kHz RC oscillator” changed to “32.768 kHz crystal oscillator or by the on-chip 64 kHz RC oscillator” Section 11. “Chip Identifier (CHIPID)” Updated Table 11-1 “SAMA5D2 Chip ID Registers” Section 13. “L2 Cache Controller (L2CC)” Table 13-2 “Register Mapping”: reset value 0x0000_0000 changed to 0x0000_0111 for L2CC_TRCR and L2CC_DRCR Section 14. “Debug and Test Features” Table 14-1 “Debug and Test Pin List”: NRST pin function “Microcontroller Reset” changed to “Microprocessor Reset” Section 15. “Standard Boot Strategies” “Boot Sequence Control Register (BSCR)” renamed to “Boot Sequence Controller Configuration Register” Section 15.1 “Description”: “This microcontroller can be configured” changed to “This microprocessor can be configured” Figure 15-10 “Galois Field Table Mapping”: modified Galois field table offsets 12-May-16 Section 15.4.2 “Boot Sequence Controller Configuration Register”: added address Section 15.4.3 “Boot Configuration Word”: added reference to “Customer Fuse Matrix” Added Section 15.4.6.5 “QSPI Flash Boot” Table 15-3 “PIO Driven during Boot Program Execution”: NAND Flash PIO line PIOC17 changed to PIOB0 Section 18. “Special Function Registers (SFR)” Table 18-1 “Register Mapping”: removed EBI Configuration Register / SFR_EBICFG (offset 0x40 now reserved) Section 18.3.1 “DDR Configuration Register”: added note Removed section “EBI Configuration Register” Section 21. “Watchdog Timer (WDT)” Section 21.4 “Functional Description”: in eighth paragraph, “To prevent a software deadlock that continuously triggers the watchdog, the reload of the watchdog must occur...” changed to “The reload of the watchdog must occur...” Section 25. “Real-time Clock (RTC)” Reworked Section 25.5.6 “Updating Time/Calendar” Reworked Figure 25-7 “Calibration Circuitry Waveforms” AD index ‘7’ replaced with generic ‘n’ in Section 25.5.8 “Waveform Generation” Updated Figure 25-8 “Waveform Generation for ADC Trigger Event” Section 25.6.2 “RTC Mode Register”: - updated descriptions of fields OUT0 and OUT1 - added fields TPERIOD and THIGH Section 27. “Low Power Asynchronous Receiver (RXLP)” Pin/signal name “LPRXD” changed to “RXD” DS60001476B-page 2594  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 29. “Clock Generator” Section 29.2 “Embedded Characteristics”: AUDIOPLLCK changed to AUDIOPLLCLK Figure 29-1 “Clock Generator Block Diagram”: lines changed to arrows for OSCSEL to multiplexer, for MOSCSEL to multiplexer, and for PLLADIV2 to “PLLA and Divider” block Figure 29-5 “Divider and PLLA Block Diagram”: added PLLADIV2 divider Updated Section 29.8 “Audio PLL” Section 30. “Power Management Controller (PMC)” AUDIOPLLCK changed to AUDIOPLLCLK in Section 30.15 “Programmable Clock Controller” and Section 30.16 “Generic Clock Controller” 12-May-16 Figure 30-1 “General Clock Block Diagram”: added PLLA block; repositioned PLLACK signal; at bottom of diagram “PCKx” changed to “PCKx (to pads)” Table 30-3 “Register Mapping”: PMC_AUDIO_PLL0 reset value ‘0x0000_0000’ changed to ‘0x0000_00D0’ Section 30. “Power Management Controller (PMC)” (cont”d) Section 30.22.11 “PMC Master Clock Register”: updated CSS field description Section 30.22.13 “PMC Programmable Clock Register”: added addresses 0xF0014044 and 0xF0014048; updated CSS field description Section 30.22.39 “PMC Audio PLL Control Register 0”: added fields DCO_FILTER (bits 29:28), DCO_GAIN (bits 27:24) and PLLFLT (bits 7:4) Section 30.22.40 “PMC Audio PLL Control Register 1”: updated DIV field description (cont’don next page)  2017 Microchip Technology Inc. DS60001476B-page 2595 SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 31. “Parallel Input/Output Controller (PIO)” Section 31.4.2 “External Interrupt Lines”: “are generally multiplexed” changed to “are multiplexed” Section 31.5 “Functional Description”: removed entire section “Peripheral Muxing Example” Table 31-4 “Register Mapping”: - added reset value for PIO_CFGR, PIO_ODSR, PIO_IMR, S_PIO_CFGR, S_PIO_ODSR and S_PIO_IMR - “PIO I/O Freeze Register” corrected to “PIO I/O Freeze Configuration Register” - defined offset range 0x400–0x4FC as reserved - reserved offset range 0x5E8–0x5F8 changed to 0x5E8–0x5FC - “Secure PIO I/O Freeze Register” corrected to “Secure PIO I/O Freeze Configuration Register” Removed duplicated or invalid addresses in Section 31.7.1 “PIO Mask Register”, Section 31.7.2 “PIO Configuration Register”, Section 31.7.3 “PIO Pin Data Status Register”, Section 31.7.4 “PIO Lock Status Register”, Section 31.7.5 “PIO Set Output Data Register”, and Section 31.7.6 “PIO Clear Output Data Register” Section 31.7.7 “PIO Output Data Status Register”: removed duplicated or invalid addresses; access “Read-only or Read/ Write” corrected to “Read/Write” Removed duplicated or invalid addresses in Section 31.7.8 “PIO Interrupt Enable Register”, Section 31.7.9 “PIO Interrupt Disable Register”, Section 31.7.10 “PIO Interrupt Mask Register”, and Section 31.7.11 “PIO Interrupt Status Register” Section 31.7.12 “PIO I/O Freeze Configuration Register”: corrected title (was “PIO Freeze Configuration Register”); removed duplicated or invalid addresses; access “Read/Write” corrected to “Write-only” Removed duplicated or invalid addresses in Section 31.7.15 “Secure PIO Mask Register”, Section 31.7.16 “Secure PIO Configuration Register”, Section 31.7.17 “Secure PIO Pin Data Status Register”, Section 31.7.18 “Secure PIO Lock Status Register”, Section 31.7.19 “Secure PIO Set Output Data Register” and Section 31.7.20 “Secure PIO Clear Output 12-May-16 Data Register” Section 31.7.21 “Secure PIO Output Data Status Register”: removed duplicated or invalid addresses; access “Read-only or Read/Write” corrected to “Read/Write” Removed duplicated or invalid addresses in Section 31.7.22 “Secure PIO Interrupt Enable Register”, Section 31.7.23 “Secure PIO Interrupt Disable Register”, Section 31.7.24 “Secure PIO Interrupt Mask Register”, and Section 31.7.25 “Secure PIO Interrupt Status Register” Section 31.7.29 “Secure PIO I/O Freeze Configuration Register”: corrected title (was “Secure PIO Freeze Configuration Register”); removed duplicated or invalid addresses; access “Read/Write” corrected to “Write-only” Section 31.7.30 “Secure PIO Slow Clock Divider Debouncing Register”: added sentence about register write protection Section 32. “External Memories” Table 32-1 “DDR/LPDDR I/O Lines Description”: updated DDR_VREF function description Section 33. “Multiport DDR-SDRAM Controller (MPDDRC)” Section 33.4.1 “Low-power DDR1-SDRAM Initialization”: in first paragraph, removed content about configuring register SFR_DDRCFG Section 33.6 “Software Interface/SDRAM Organization, Address Mapping”: modified description of Interleaved mode (“at each SDRAM end page” corrected to “at each DDRSDRAM end of page”) Harmonized register naming throughout Section 33.7 “AHB Multiport DDR-SDRAM Controller (MPDDRC) User Interface” Removed all MPDDRC DLL registers (offset range 0x100–0x158 now reserved) Section 33.7.3 “MPDDRC Configuration Register”: modified description of DECOD bit value ‘1’ (“at each SDRAM end page” corrected to “at each DDR-SDRAM end of page”) Section 33.7.12 “MPDDRC I/O Calibration Register”: updated RZQ values in RDIV field description DS60001476B-page 2596  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 34. “Static Memory Controller (SMC)” Section 34.17.3 “NFC Initialization”: instances of “rbn” changed to “Ready/Busy” Section 34.20.3 “NFC Status Register”: bit RB_EDGE3 (bit 27) replaced by RB_EDGE0 (bit 24); updated RB_RISE and RB_FALL bit descriptions Bit RB_EDGE3 (bit 27) replaced by RB_EDGE0 (bit 24) in Section 34.20.4 “NFC Interrupt Enable Register”, Section 34.20.5 “NFC Interrupt Disable Register” and Section 34.20.6 “NFC Interrupt Mask Register” Deleted invalid addresses in Section 34.20.30 “PMECC Error Location SIGMA0 Register” and Section 34.20.31 “PMECC Error Location SIGMAx Register” Section 34.20.32 “PMECC Error Location x Register”: register index “x=0..23” corrected to “x=0..31” Section 34.20.36 “Timings Register”: removed RBNSEL field Section 35. “DMA Controller (XDMAC)” Added XDMAC_CCx.CSIZE configuration to Table 35-2 “DMA Channels Definition (XDMAC0)” and Table 35-3 “DMA Channels Definition (XDMAC1)” Table 35-5 “Register Mapping”: - XDMAC_GCFG access Read-only corrected to Read/Write - XDMAC_GWAC access Read-only corrected to Read/Write Section 35.9.2 “XDMAC Global Configuration Register”: access Read-only corrected to Read/Write Section 35.9.3 “XDMAC Global Weighted Arbiter Configuration Register”: access Read-only corrected to Read/Write Section 36. “LCD Controller (LCDC)” Updated ”Section 36.2 “Embedded Characteristics” 12-May-16 Updated Section 36.6.1.1 “Pixel Clock Period Configuration” Section 37. “Ethernet MAC (GMAC)” Table 37-1 “GMAC Connections in Different Modes”: added table Note on GTXCK Updated Section 37.5.3 “Interrupt Sources” Section 37.7.1.2 “Receive Buffer List” and Section 37.7.1.3 “Transmit Buffer List”: added note at end of sections on queue pointer intilaization Section 37.8.107 “GMAC Transmit Buffer Queue Base Address Register Priority Queue x” and Section 37.8.108 “GMAC Receive Buffer Queue Base Address Register Priority Queue x”: changed sentence on register initialization Section 39. “USB Host High Speed Port (UHPHS)” Section 39.2 “Embedded Characteristics”: “X Hosts (A and B) High Speed (EHCI)” corrected to “2 Hosts (A and B) High Speed (EHCI)” Table 39-2 “Register Mapping”: inserted reserved offset 0x0C Section 39.7.19 “EHCI: REG06 - AHB Error Status”: instances of “INSNREG[8:4]” changed to “INSNREG06[8:4]” Section 40. “Audio Class D Amplifier (CLASSD)” Section 40.2 “Embedded Characteristics”: DSP clock frequency “11.289 MHz” corrected to “11.2896 MHz” Section 40.5.2 “Power Management”: field name “NOVRLAP” corrected to “NOVRVAL” Figure 40-21 “Use Case 4B: Stereo Audio DAC With Passive Low Pass Filter and Single-ended Outputs”: changed title (was “Use Case 4B: Stereo Audio DAC With Passive Low Pass Filter and Differential Outputs”) Section 42. “Synchronous Serial Controller (SSC)” Figure 42-19 “Interrupt Block Diagram”: “RXSYNC” renamed to “RXSYN”; “TXSYNC” renamed to “TXSYN” Section 42.8.10 “Register Write Protection”: in first sentence, “AIC behavior” corrected to “SSC behavior”  2017 Microchip Technology Inc. DS60001476B-page 2597 SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 43. “Two-wire Interface (TWIHS)” Section 43.6.3.10 “SMBus Mode”: Deleted “A dedicated bus line, SMBALERT, allows a slave to get a master attention” from listed exceptions Section 43.6.5.6 “SMBus Mode”: Deleted “A dedicated bus line, SMBALERT, allows a slave to get a master attention” from listed exceptions Deleted note about debugger read access in Section 43.7.6 “TWIHS Status Register”, Section 43.7.13 “TWIHS Receive Holding Register” and Section 43.7.25 “TWIHS Write Protection Status Register” Section 44. “Flexible Serial Communication Controller (FLEXCOM)” Section 44.7.1.2 “Fractional Baud Rate in Asynchronous Mode”: in first paragraph, deleted sentence “This feature is only available when using USART Normal mode.” Figure 44-8 “Preamble Patterns, Default Polarity Assumed”: instances of “8 bit width” changed to “8-bit” Figure 44-11 “Asynchronous Start Detection”: added missing arrowheads Section 44.7.3.11 “Receiver Timeout”: removed redundant paragraphs on STTTO and RETTO; reworded two bullets Section 44.7.4 “ISO7816 Mode”: at end of second paragraph, “value 0x5 for protocol T = 1” changed to “value 0x6 for protocol T = 1” Section 44.7.4.2 “Protocol T = 0”: reworded content under “Receive NACK Inhibit” Section 44.7.7 “USART Comparison Function on Received Character”: modified information about the CMPMODE bit Table 44-18 “Register Mapping”: added TWI SleepWalking Matching Register (FLEX_TWI_SWMR) Section 44.10.41 “USART Write Protection Mode Register”: rephrased WPEN bit description Corrected order of all sections from Section 44.10.66 “TWI Interrupt Enable Register” to Section 44.10.76 “TWI SleepWalking Matching Register” 12-May-16 Section 44.10.76 “TWI SleepWalking Matching Register”: added addresses Section 46. “Serial Peripheral Interface (SPI)” Figure 46-1 “Block Diagram”: added GCLK output from PMC to SPI Modified transmission condition description in Section 46.7.3 “Master Mode Operations” Section 46.7.4 “SPI Slave Mode”: added sentence about NSS rising between characters Section 46.7.5 “SPI Comparison Function on Received Character”: in seventh paragraph, added “if SleepWalking mode is disabled” to sentence “The comparison trigger event is...” Updated Section 46.7.8 “Register Write Protection” Section 46.8.2 “SPI Mode Register”: added bits BRSRCCLK (Bit Rate Source Clock) and LSBHALF (LSB Timing Selection); updated description of field DLYBCS Section 46.8.12 “SPI Chip Select Register”: updated description of fields CSNAAT, SCBR, DLYBS and DLYBCT Section 47. “Quad Serial Peripheral Interface (QSPI)” Section 47.2 “Embedded Characteristics”: added bullet “Interface to Serial Flash Memories Operating in Single Data Rate or Double Data Rate Modes” Section 47. “Quad Serial Peripheral Interface (QSPI)” (cont’d) NSS renamed to QCS in Figure 47-2 “QSPI Transfer Format (QSPI_SCR.CPHA = 0, 8 bits per transfer)” and Figure 473 “QSPI Transfer Format (QSPI_SCR.CPHA = 1, 8 bits per transfer)” Section 47.7.2 “QSPI Mode Register”: added note “This field is forced to LASTXFER when SMM is written to ‘1’ to CSMODE field description; modified equation in description of fields DLYBCT and DLYCS Section 47.7.5 “QSPI Status Register”: updated descriptions of bits CSR and INSTRE Section 47.7.9 “QSPI Serial Clock Register”: modified equation in description of fields SCBR and DLYBS DS60001476B-page 2598  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 48. “Secure Digital Multimedia Card Controller (SDMMC)” Added Section 48.3 “Embedded Features for SDMMC0 and SDMMC1” Figure 48-1 “Block Diagram”: added two notes Table 48-3 “Register Mapping”: updated SDMMC_APSR reset value (SDMMC0 different from SDMMC1) Section 48.13.18 “SDMMC Software Reset Register”: updated SWRSTCMD bit description Section 48.13.58 “SDMMC Calibration Control Register”: in CNTVAL field description, “tSTARTUP = ...” corrected to “tSTARTUP = 2 µs” Section 49. “Image Sensor Controller (ISC)” Added Section 49.4 “Product Dependencies” Table 49-18 “Register Mapping”: defined offset range 0x404–0x40C as reserved Section 50. “Controller Area Network (MCAN)” “GCLK3” changed to “GCLK” in Section 50.3 “Block Diagram” and Section 50.4.2 “Power Management” Added Table 50-2 “Peripheral IDs” Updated Section 50.5.1.3 “CAN FD Operation” Section 50.5.1.4 “Transmitter Delay Compensation”: modified title (was “Transceiver Delay Compensation”); revised content Section 50.5.1.5 “Restricted Operation Mode”: added ‘Note’ Section 50.5.3 “Timeout Counter”: “baud rate” changed to “bit rate” in ‘Note’ Section 50.5.4.1 “Acceptance Filtering”: “described in Section” corrected to “described in “Rx FIFO Overwrite Mode” Updated Figure 50-5 “Standard Message ID Filter Path”and Figure 50-6 “Extended Message ID Filter Path” 12-May-16 Updated register names in Figure 50-7 “Rx FIFO Status” and Figure 50-8 “Rx FIFO Overflow Handling” Section 50.5.7.2 “Rx Buffer and FIFO Element”: “R1 Bit 21 FDF: Extended Data Length” renamed to “R1 Bit 21 FDF: FD Format” Section 50.5.7.4 “Tx Event FIFO Element”: “E1 Bit 21 FDF: Extended Data Length” renamed to “E1 Bit 21 FDF: FD Format” Table 50-14 “Register Mapping”: - deleted row “0x00–0x04 / Reserved” - “Fast Bit Timing and Prescaler Register” renamed to “Data Bit Timing and Prescaler Register” - “Bit Timing and Prescaler Register” renamed to “Nominal Bit Timing and Prescaler Register” Section 50.6.4 “MCAN Data Bit Timing and Prescaler Register”: changed name (was “MCAN Fast Bit Timing and Prescaler Register”); field FBRP replaced by field DBRP Section 50.6.7 “MCAN CC Control Register”: updated descriptions of fields FDOE, BRSE, PXHD and EFB; removed NISO bit Section 50.6.8 “MCAN Nominal Bit Timing and Prescaler Register”: “NBRP: Nominal Baud Rate Prescaler” changed to “NBRP: Nominal Bit Rate Prescaler” Section 50.6.9 “MCAN Timestamp Counter Configuration Register”: updated TSS field description Section 50.6.10 “MCAN Timestamp Counter Value Register”: updated TSC field description Section 50. “Controller Area Network (MCAN)” (cont’d) Section 50.6.20 “MCAN Global Filter Configuration”: added details on register description; updated ANFE and ANFS field descriptions. Added details on register description in Section 50.6.21 “MCAN Standard ID Filter Configuration” and Section 50.6.22 “MCAN Extended ID Filter Configuration” Section 50.6.24 “MCAN High Priority Message Status”: updated description of MSI field value ‘1’  2017 Microchip Technology Inc. DS60001476B-page 2599 SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 51. “Timer Counter (TC)” Replaced TIOA, TIOB, TCLK with TIOAx, TIOBx, TCLKx Table 51-1 “Timer Counter Clock Assignment”: updated definitions Section 51.6.3 “Clock Selection”: updated bullet “Internal clock signals”, updated notes 1 and 2 Section 51.6.9 “Transfer with DMAC in Capture Mode”: updated title (added “in Capture Mode”) Updated Figure 51-5 “Example of Transfer with DMAC in Capture Mode” Section 51.6.16.4 “Position and Rotation Measurement”: updated text in first paragraph Added Section 51.6.16.6 “Detecting a Missing Index Pulse” Updated TCCLKS field description in Section 51.7.2 “TC Channel Mode Register: Capture Mode” and Section 51.7.3 “TC Channel Mode Register: Waveform Mode” Section 53. “Pulse Width Modulation Controller (PWM)” Throughout, “PWMTRG” and “EXTTRG” renamed to “PWMEXTRG” Table 53-2 “I/O Lines”: “PWMEXTRG0” and “PWMEXTRG1” renumbered to “PWMEXTRG1” and “PWMEXTRG2” Updated Section “Recoverable Fault” Updated Figure 53-1 “Pulse Width Modulation Controller Block Diagram” and added note below figure Updated Figure 53-16 “Fault Protection” Section 54. “Secure Fuse Controller (SFC)” Table 54-1 “Register Mapping”: removed reset value from SFC_IER and SFC_IDR (both registers are write-only) 12-May-16 Section 55. “Integrity Check Monitor (ICM)” Table 55-8 “Register Mapping”: ICM_SR access “Write-only” corrected to “Read-only” Section 57. “Advanced Encryption Standard (AES)” Table 57-5 “Register Mapping”: AES_ALPHAR[0..3] access “Write” corrected to “Write-only” Section 57.5.20 “AES Alpha Word Register x”: access “Write” corrected to “Write-only” Section 59. “Triple Data Encryption Standard (TDES)” Section 59.4.1 “Operating Modes”: deleted sentence “The OFB and CFB modes of operation are only available if 2-key mode is selected (KEYMOD = 1 in TDES_MR).” Section 59.4.3 “Last Output Data Mode”: deleted sentence “No more Output Data Register reads are necessary between consecutive encryptions/decryptions (see Section 59.4.3 “Last Output Data Mode”).” Section 59.5.2 “TDES Mode Register”: in OPMOD field description, deleted sentence “The OFB and CFB modes of operation are only available if 2-key mode is selected (KEYMOD = 1).” Section 61. “Security Module” Updated Figure 61-2 “Security Module Internal Memory Map” Section 61. “Analog-to-Digital Converter (ADC)” Section 61.1 “Description”: - deleted sentence “A digital error correction circuit based on the multi-bit redundant signed digit (RSD) algorithm is implemented to reduce INL and DNL errors.” - deleted sentence “Finally, the user can configure ADC timings, such as startup time and tracking time.” DS60001476B-page 2600  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 61. “Analog-to-Digital Converter (ADC)” (cont’d) Updated Section 61.2 “Embedded Characteristics” Updated Figure 61-1 “Analog-to-Digital Converter Block Diagram” Revised Section 61.5 “Product Dependencies” Revised Section 61.6.1 “Analog-to-Digital Conversion” Updated Section 61.6.3 “ADC Reference Voltage” and Section 61.6.4 “Conversion Resolution” Updated Section 61.6.7 “Conversion Triggers” Section 61.6.9 “Comparison Window”: in fourth paragraph, instance of “ADC_SR” corrected to “ADC_ISR” Section 61.6.10 “Differential and Single-ended Input Modes”: changed title (was “Differential Inputs”) and revised content Updated Section 61.6.11 “ADC Timings”, Section 61.6.12 “Last Channel Specific Measurement Trigger”, Section 61.6.13 “Enhanced Resolution Mode and Digital Averaging Function” and Section 61.6.14 “Automatic Error Correction” Instances of GND renamed to GNDANA in Figure 61-15 “Touchscreen Switches Implementation”, Figure 61-18 “Touchscreen Switches Implementation” and Figure 61-20 “Touchscreen Pen Detect” Updated Section 61.6.16 “Asynchronous and Partial Wakeup (SleepWalking)” Section 61.6.17.1 “Classic ADC Channels Only (Touchscreen Disabled)”: changed title (was “Classical ADC Channels Only”) Section 61.6.19 “Register Write Protection”: updated list of protectable registers Table 61-8 “Register Mapping”: - defined 0x48 as reserved - added row 0x4C / Channel Offset Register / ADC_COR - added offset 0x7C for ADC_CDR11 12-May-16 - defined offset range 0x80–0x90 as reserved - added row 0x94 / Analog Control Register / ADC_ACR - defined offset range 0xC4–0xD0 as reserved - added row 0xD4 / Correction Values Register / ADC_CVR - added row 0xD8 / Channel Error Correction Register / ADC_CECR - added row 0xDC / Touchscreen Correction Values Register / ADC_TSCVR - defined offset 0xE0 as reserved Section 61.7.2 “ADC Mode Register”: updated TRACKIM field description Added LCCHG (Last Channel Change) bit in Section 61.7.9 “ADC Interrupt Enable Register”, Section 61.7.10 “ADC Interrupt Disable Register”, Section 61.7.11 “ADC Interrupt Mask Register” and Section 61.7.12 “ADC Interrupt Status Register” Section 61.7.13 “ADC Last Channel Trigger Mode Register”: updated CMPMOD field description Section 61.7.16 “ADC Extended Mode Register”: updated CMPMODE field description; added descriptions for fields OSR ASTE Section 61.7.18 “ADC Channel Offset Register”: added address; removed bits OFF11:OFF0 from bitmap; modified DIFFx field description Section 61.7.20 “ADC Analog Control Register”: added address; added IBCTL field Section 61.7.25 “ADC Trigger Register”: added sentence about write protection Removed Section “Correction Select Register” Added sentence about write protection in Section 61.7.26 “ADC Correction Values Register” and Section 61.7.27 “ADC Channel Error Correction Register” Added Section 61.7.28 “ADC Touchscreen Correction Values Register”  2017 Microchip Technology Inc. DS60001476B-page 2601 SAMA5D2 SERIES Table 72-4: SAMA5D2 Datasheet Rev. 11267D Revision History (Continued) Issue Date Changes Section 62. “Electrical Characteristics” “ADVREFP” corrected to “ADVREF” Section 62.2 “DC Characteristics”: in first sentence, “TA = -40°C to +85°C” changed to “TA = -40°C to +105°C” Added Table 62-2 “Recommended Thermal Operating Conditions” Updated Section 62.4 “Active Mode” Table 62-8 “Low-power Mode Configuration Summary”: updated values for ‘Consumption’ and ‘Wakeup Time’ Updated Section 62.5.6 “Low-power Consumption Versus Modes” Table 62-9 “Typical Power Consumption in Idle Mode: AMP2”: updated consumption values Table 62-10 “VDDCORE Power Consumption in Ultra Low-power Mode: AMP2”: updated consumption values; updated wakeup time for ULP1 Fast Wakeup mode Table 62-11 “Typical Power Consumption for Backup Mode”: updated consumption values Updated Table 62-12 “Processor Clock Waveform Parameters” and Table 62-13 “Master Clock Waveform Parameters” Updated Section 62.7.1 “Main Oscillator Characteristics” Table 62-17 “12 MHz RC Oscillator Characteristics”: updated startup time values Updated Section 62.7.3 “32.768 kHz Crystal Oscillator Characteristics” Updated Table 62-23 “Audio PLL Characteristics” Section 62.10 “ADC Characteristics”: deleted sentence “The VREFN pin must be connected to ground.” Table 62-25 “Power Supply Characteristics”: updated Analog Current Consumption value for Fast Wakeup mode Table 62-26 “ADVREF Electrical Characteristics”: “VREFP” corrected to “ADVREF”; updated Current value 12-May-16 Section 62.10.4.1 “Differential Mode (12-bit mode)” and Section 62.10.4.2 “Single-ended Mode (12-bit mode)”: in equation, “VVREFP” corrected to “VADVREF” Section 62.10.4.4 “Gain and Offset Errors”: “VVREFP” corrected to “VADVREF” Table 62-27 “ADC Timing Characteristics”: updated footnote Added Table 62-32 “ADC Analog Input Characteristics” Table 62-37 “VDDCORE Power-On Reset Characteristics”: updated Hysteresis Voltage values Section 62.14.1 “Maximum SPI Frequency”: updated values in “Master Read Mode” and “Slave Write Mode” Revised Section 62.18 “MPDDRC Timings” Corrected CKI values in Figure 62-33 “SSC Transmitter, TK and TF in Input”, Figure 62-35 “SSC Receiver, RK in Input and RF in Output”, Figure 62-36 “SSC Receiver, RK and RF in Output” and Figure 62-38 “Minimum and Maximum Access Time of Output Signals” Section 64. “Schematic Checklist” Figure 64-1 “1.2V, 1.35V/1.5V, 2V, 2.5V, 3.3V Power Supplies Schematics(1)”: GNDHSIC changed to GNDUTMIC Table 64-1 “Power Supply Connections”: updated GNDUTMIC row; removed GNDHSIC row; in second footnote, “microcontroller” changed to “microprocessor” Table 64-2 “Clock, Oscillator and PLL Connections”: “(internal 32-kHz RC oscillator) changed to “(internal 64 kHz RC oscillator)” Section 64.5.1 “How to Define the Oscillator Load Capacitance”: instances of “32-KHz Oscillator” changed to “32.768 kHz Oscillator” Added Section 64.14.6 “QSPI Pull-up Resistors” Updated Section 66. “Ordering Information” Section 67. “Errata” Updated content (errata now collected in Section 67.1 “Errata - SAMA5D2 MRL-B Parts” and Section 67.2 “Errata SAMA5D2 MRL-A Parts”) DS60001476B-page 2602  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-5: Issue Date SAMA5D2 Datasheet Rev. 11267C Revision History Changes Changed datasheet status from ‘Preliminary’ to ‘Complete’. Added “Introduction” and transferred Description to Section 1. Section 2. “Configuration Summary” Added device compatibility information Section 4. “Signal Description” Table 4-1 “Signal Description List”: modified rows PIOBU 0-7 and DDR_RESETN Section 6. “Power Considerations” Added Section 6.4.1 “VDDBU Power Architecture” Updated Section 6.2 “Powerup Considerations” and Section 6.3 “Powerdown Considerations” Section 7. “Memories” Updated Section 7.1.2 “Internal ROM” Section 10. “Peripherals” Updated Table 10-1 “Peripheral identifiers” and Section 10.4 “Peripheral Clock Types” Section 16. “AXI Matrix (AXIMX)” Table 16-1 “Register Mapping”: removed 0x00000000 reset value from all rows Section 17. “Matrix (H64MX/H32MX)” Section 17.2 “Embedded Characteristics”: removed "Master number forwarding to slaves" characteristic 8-Jan-16 Updated Table 17-1 “List of H64MX Masters”, Table 17-2 “List of H64MX Slaves”, Table 17-4 “List of H32MX Masters”, Table 17-5 “List of H32MX Slaves” Table 17-3 “Master to Slave Access on H64MX”: updated ‘SDMMC0-SDMMC1’ row Table 17-6 “Master to Slave Access on H32MX”: updated ‘Slave 5’ rows Section 17.12.2 “Security of APB Slaves”: added introduction and bulleted list introduced by “As a general rule” Added Section 17.12.3 “Security Types of AHB Master Peripherals” and Section 17.12.4 “Security Types of AHB Slave Peripherals” Section 17-9 “Peripheral Identifiers”: corrected some security type names Section 17.13 “AHB Matrix (MATRIX) User Interface”: added introduction and modified reset value of Updated Security Areas Split Slave x Registers in Table 17-10 “Register Mapping” Section 24. “Watchdog Timer (WDT)” Replaced “Idle mode” with “Sleep mode (Idle mode)” in Section 24.1 “Description” and with “Sleep mode” in Section 24.4 “Functional Description” Section 22. “Reset Controller (RSTC)” Renamed 'proc_nreset' to 'Processor Reset', 'periph_nreset' to 'Peripheral Reset', 'backup_neset' to 'Backup Reset', 'rstc_irq' to 'Reset Controller Interrupt', 'wd_fault' to 'Watchdog Fault', ‘user_reset’ to User Reset. Updated text and figures to show that Processor Reset and Peripheral Reset signals are merged. Section 23. “Shutdown Controller (SHDWC)” Updated Figure 23-1 “Shutdown Controller Block Diagram” and Table 23-1 “I/O Lines Description” Section 23.7.3 “Shutdown Status Register”: corrected register table (added WKUPIS9) Section 23.7.4 “Shutdown Wakeup Inputs Register”: corrected register table (added WKUPT9 and WKUPEN9)  2017 Microchip Technology Inc. DS60001476B-page 2603 SAMA5D2 SERIES Table 72-5: Issue Date SAMA5D2 Datasheet Rev. 11267C Revision History (Continued) Changes Section 29. “Real-time Clock (RTC)” Removed RTC Milliseconds Register (RTC_MSR) and all related information in Section 29.1 “Description”, Section 29.2 “Embedded Characteristics”, Section 29.5 “Functional Description” and Section 29.6 “Real-time Clock (RTC) User Interface”. Table 29-1 “Register Mapping”: modified RTC_CALR reset value Section 29.6.1 “RTC Control Register”: updated CALEVSEL field description Updated Section 29.6.22 “RTC TimeStamp Source Register” Section 29. “Clock Generator” Section 29.2 “Embedded Characteristics”: replaced "400 to 1000 MHz programmable PLL" with "600 to 1200 MHz programmable PLL" and replaced “HCLOCK” with “HCLOCK_LS/HS” and “PCLOCK” with “PCLOCK_LS/HS” Section 29.4 “Slow Clock”: removed “This allows the slow clock to be valid in a short time (about 100 μs)” Section 29.8 “Audio PLL”: updated all equations and added “in the 700 MHz range” after “The PLL core operates at 700 MHz (AUDIOCORECLOCK)” Updated Figure 29-3. Main Clock Block Diagram and Figure 29-4. Main Clock Source Selection Section 30. “Power Management Controller (PMC)” Updated Section 30.6 “Matrix Clock Controller” Updated Section 30-1 “General Clock Block Diagram” Section 30.19 “Programming Sequence”, sub-section “Selecting Master Clock and Processor Clock”: updated sequence following "If a new value for CSS field corresponds to PLL Clock" Section 30.22.11 “PMC Master Clock Register”: updated H32MXDIV field description Section 33. “Multi-port DDR-SDRAM Controller (MPDDRC)” 8-Jan-16 Section 33-2 “Single Write Access, Row Closed, DDR-SDRAM Devices” to Section 33-8 “SINGLE Write Access Followed by a Read Access, DDR2-SDRAM Devices”: replaced “D[15:0]” with “DATA” Updated Section 33.7.9 “MPDDRC Low-power DDR2 Low-power DDR3 Low-power Register” Section 33.7.10 “MPDDRC Low-power DDR2 Low-power DDR3 and DDR3 Calibration and MR4 Register”: updated MR4_READ field description Section 34. “Static Memory Controller (SMC)” Removed NFCCMD field and modified Section 34.17.2.1 “Building NFC Address Command Example” and Section 34.17.2.2 “NFC Address Command” accordingly Table 34-20 “Register Mapping”: corrected offset values of PMECC Error Location 31 Register and of subsequent reserved range; removed reset value from HSMC_CTRL (register is write-only) Section 42. “DMA Controller (XDMAC)” Section 42.5.4.1 “Single Block With Single Microblock Transfer”: added text on memory-to-memory transfer Section 42.8 “XDMAC Software Requirements”: added bullet on memory-to-memory transfer Table 42-5 “Register Mapping”: corrected access of XDMAC_GTYPE, XDMAC_GWAC, XDMAC_CIM Section 42.9.6 “XDMAC Global Interrupt Mask Register”: corrected access to Read-only Section 42.9.28 “XDMAC Channel x [x = 0..15] Configuration Register”: corrected INITD and PERID field descriptions Section 36. “LCD Controller (LCDC)” Modified width of fields in Section 36.7.2 “LCD Controller Configuration Register 1” and Section 36.7.3 “LCD Controller Configuration Register 2” Section 40. “Audio Class D Amplifier (CLASSD)” Replaced ‘audio clock’ with ‘generic clock’ and ‘ACLK’ with ‘GCLK’ throughout the section DS60001476B-page 2604  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-5: Issue Date SAMA5D2 Datasheet Rev. 11267C Revision History (Continued) Changes Section 41. “Inter-IC Sound Controller (I2SC)” Section 41.6.3 “Master, Controller and Slave Modes”: removed text fragment: ‘in order to avoid unwanted glitches on the I2SWS and I2SCK pins.’ Section 41.8.2 “Inter-IC Sound Controller Mode Register”: removed text fragment: ‘in order to avoid unexpected behavior on the I2SWS, I2SCK and I2SDO outputs.’ and added note (2) below IMCKDIV field description. Section 44. “Flexible Serial Communication Controller (FLEXCOM)” Restored all references to ISO7816 specification Updated Figure 44-3 “Fractional Baud Rate Generator” Added Figure 44-27 “RTS line software control when FLEX_US_MR.USART_MODE = 2” Section 44.10.6 “USART Mode Register”: updated USART_MODE field description (SPI_MASTER item) Section 44.10.44 “SPI Mode Register”: added LBHPC bit Section 55. “Universal Asynchronous Receiver Transmitter (UART)” Section 55.6.9 “UART Baud Rate Generator Register”: in CD field description, corrected equation after “If BRSRCCK = 1” Section 59. “Quad SPI Interface (QSPI)” Section 59.7.5 “QSPI Status Register”: updated RDRF, TDRE, TXEMPTY, and OVRES field descriptions Section 48. “Secure Digital Multimedia Card Controller (SDMMC)” Section 48.12.41 “SDMMC Preset Value Register”: updated CLKGSEL field description Section 49. “Image Sensor Controller (ISC)” 8-Jan-16 Section 49.1 “Description”: removed "serial csi-2 based CMOS/CCD sensor" (not supported). Section 50. “Controller Area Network (MCAN)” Changed MCAN interrupt line names to MCAN_INT0 and MCAN_INT1 thoughout the section Section 50.6.7 “MCAN CC Control Register”: added bit NISO Section 51. “Timer Counter (TC)” Reformatted and renamed Table 51-2 “Channel Signal Description” Section 51.6.3 “Clock Selection”: updated notes (1) and (2) Section 52. “Pulse Density Modulation Interface Controller (PDMIC)” Replaced all instances of “PCK” with “GCLK” Section 52.2 “Embedded Characteristics”: removed ‘Multiplexed PDM Input Support’ characteristic Updated Section 52.5.2 “Power Management” and Section 52.6.2.1 “Description” Section 52.6.2.6 “Gain and Offset Compensation”: updated dgain bullet Section 52.7.3 “PDMIC Converted Data Register”: updated DATA field description Section 52.7.8 “PDMIC DSP Configuration Register 0”: updated OSR field description Section 61. “Security Module” Section 61.5.5 “SECUMOD Status Clear Register”: removed MCKM field description Section 61.5.18 “SECUMOD Wake Up Register”: removed TPML field description Section 77. “Analog-to-Digital Converter (ADC)” Section 77.7.2 “ADC Mode Register”: updated TRACKTIM and TRANSFER field descriptions.  2017 Microchip Technology Inc. DS60001476B-page 2605 SAMA5D2 SERIES Table 72-5: Issue Date SAMA5D2 Datasheet Rev. 11267C Revision History (Continued) Changes Section 62. “Electrical Characteristics” Updated tables from Table 62-3 “DC Characteristics” to Table 62-35 “Analog Comparator Characteristics” Updated Figure 62-3 “Main Oscillator Schematics” Corrected Gain Error formula under Figure 62-6 “Gain and Offset Errors in Single-ended Mode” Removed Figure 63-4 “Single-ended Mode ADC” and Figure 63-5 “Differential Mode ADC” Updated wake-up pin numbers in Section 62.5.1 “Backup Mode” and Section 62.5.3.2 “ULP1 Mode” 8-Jan-16 Updated Section 62.5.4 “Idle Mode” and Section 62.23 “SDMMC Timings” Section 62.14.3 “Timing Extraction”: added introduction and Figure 62-12 “MISO Capture in Master Mode” Section 64. “Schematic Checklist” Removed Table 65-12. “EBI Pins and NAND Flash Device Connections” and Table 65-13. “DDR2 I/O Lines Usage vs Operating Modes” Reorganized Section 66. “Ordering Information” Updated Section 67. “Errata” DS60001476B-page 2606  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-6: Issue Date SAMA5D2 Datasheet Rev. 11267B Revision History Changes “Features” Updated Security features Section 3. “Block Diagram” Updated Figure 3-1 “SAMA5D2 Series Block Diagram”. Section 5. “Package and Pinout” Updated Table 5-2 “Pin Description (SAMA5D21, SAMA5D22, SAMA5D24, SAMA5D26, SAMA5D27, SAMA5D28A)” Removed Section 4.2 “Input/Output Description” and Section 4-3 “SAMA5D2 I/O Type Description” Section 6. “Power Considerations” Updated Table 6-1 “SAMA5D2 Power Supplies” Updated Figure 6-1 “Recommended Powerup Sequence”, Figure 6-2 “Recommended Powerdown Sequence”, Figure 63 “Recommended Backup Mode Entry”, Figure 6-4 “Recommended Power Supply Sequencing at Wakeup” Section 8. “Event System” Updated Table 8-1 “Real-time Event Mapping List” Section 15. “Standard Boot Strategies” Replaced all instances of "GPBR" with "BUREG". Section 20. “Special Function Registers (SFR)” Updated Section 20.3.15 “I2S Register” Section 20. “Advanced Interrupt Controller (AIC)” Removed Sections “Interrupt Vectoring” and “Fast Interrupt Vectoring” 13-Nov-15 Updated Section 20.8.3.3 “Interrupt Handlers”and Section 20.8.4.3 “Fast Interrupt Handlers” Section 29. “Power Management Controller (PMC)” Replaced “generated clock” with “generic clock”, and “GCK” with “GCLK” Updated Section 29.22.8 “PMC Clock Generator Main Oscillator Register” Section 37. “Parallel Input/Output Controller (PIO)” Removed all references to programmable I/O delay Added Section 32. “External Memories” Section 33. “Multi-port DDR-SDRAM Controller (MPDDRC)” Section 33.4.3 “Low-power DDR2-SDRAM Initialization”: added Step 14., Step 15. and Step 21. Section 33.4.5 “Low-power DDR3-SDRAM Initialization”: added Step 14., Step 15. and Step 21. Section 33.7.8 “MPDDRC Memory Device Register”: updated DBW field description; corrected location of fields RL3 and WL Section 37. “Ethernet MAC (GMAC)” Updated Section 37.1 “Description” Section 37.5.2 “Power Management”: deleted reference to PMC_PCER Section 37.5.3 “Interrupt Sources”: deleted reference to ‘Advanced Interrupt Controller’. Replaced by ‘Interrupt Controller’. Section 37.6.14 “IEEE 1588 Support”: deleted reference to GMAC_TSSx. Removed reference to ‘output pins’ in 2nd paragraph. Section 37.6.15 “Time Stamp Unit”: added information on GTSUCOMP signal in last paragraph  2017 Microchip Technology Inc. DS60001476B-page 2607 SAMA5D2 SERIES Table 72-6: Issue Date SAMA5D2 Datasheet Rev. 11267B Revision History (Continued) Changes Section 39. “Audio Class D Amplifier (CLASSD)” Updated Figure 39-1. CLASSD Block Diagram Section 41. “Inter-IC Sound Controller (I2SC)” Replaced all instances of “PCKx” with “GCLK” Removed all references to Time Division Multiplexed (TDM) format (not supported) Section 41.1 “Description”: replaced “The I2SC can use either a single DMA Controller channel for both audio channels or one DMA Controller channel per audio channel.” with “The I2SC uses a single DMA Controller channel for both audio channels.”, and updated Section 41.2 “Embedded Characteristics” and Section 41.6.8 “DMA Controller Operation” accordingly Section 41.8.2 “Inter-IC Sound Controller Mode Register”: removed fields RXDMA and TXDMA Section 44. “Flexible Serial Communication Controller (FLEXCOM)” Added SPI mode in UART/USART Replaced all instances of ‘PCK’ with ‘GCLK’ Replaced all instances of ‘DMAC/PDC’ with ‘DMAC’ Removed SleepWalking characteristic from UART/USART mode Removed all references to ISO7816 specification Section 44.10.6 “USART Mode Register”updated USCLKS field description Section 44.10.44 “SPI Mode Register”: updated BRSRCCLK and DLYBCS field descriptions Section 44.10.54 “SPI Chip Select Register”: updated CSNAAT, SCBR, DLYBS and DLYBCT field descriptions Section 44.10.64 “TWI Clock Waveform Generator Register”: updated BRSRCCLK and CKSRC field descriptions 13-Nov-15 Updated Figure 44-1 “FLEXCOM Block Diagram” and Figure 44-67 “Master Mode Block Diagram” Section 42. “Two-wire Interface (TWIHS)” Replaced all instances of “PMC_PCK” with “GCLK” Section 55. “Universal Asynchronous Receiver Transmitter (UART)” Replaced "Processor-Independent Source Clock" with "Processor-Independent Generic Source Clock" and "PCK" with "GCLK" Section 48. “Secure Digital Multimedia Card Controller (SDMMC)” Updated revision of supported e.MMC specification (from V4.41 to V4.51) Section 51. “Pulse Density Modulation Interface Controller (PDMIC)” Removed all references to PDC Removed Section 1.6.4 “Buffer Structure” Section 54. “Secure Fuse Controller (SFC)” Removed all references to lock fuse (not supported) Section 54.4.5.3 “Fuse Masking”: corrected data register names Section 54.5.2 “SFC Mode Register”: updated MSK field description Table 54-1 “Register Mapping”: modified SFC_IER and SFC_IDR access type from “Read/Write” to “Write-only” Section 57. “Advanced Encryption Standard (AES)” Updated Figure 57-12 “Generation of an ESP IPSec Frame without ESN” and Figure 57-13 “Generation of an ESP IPSec Frame with ESN” Added Section 61. “Security Module” DS60001476B-page 2608  2017 Microchip Technology Inc. SAMA5D2 SERIES Table 72-6: Issue Date SAMA5D2 Datasheet Rev. 11267B Revision History (Continued) Changes Section 61. “Analog-to-Digital Converter (ADC)” Updated enhanced resolution value from 12 bits to 14 bits Renamed “Hold time” to “Transfer time” Replaced all instances of “PMC PCK” with “GCLK” Added Section 61.6.6 “Conversion Results Format”, Section 61.7.13 “ADC Last Channel Trigger Mode Register”, Section 61.7.14 “ADC Last Channel Compare Window Register” Section 61.2 “Embedded Characteristics”: corrected conversion rate Section 61.6.9 “Comparison Window”: added paragraph about bit SIGNMODE Section 61.6.14 “Automatic Error Correction”: replaced “GAIN_ERROR_SIZE-1” with appropriate value; replaced “Gs-1” with “Gs” in formulas Section 61.6.14 “Automatic Error Correction”, Section 62.7.27 “Correction Values Register”: replaced “GAIN_ERROR_SIZE-1” and “OFFSET_ERROR_SIZE-1” with appropriate values Section 61.7.2 “ADC Mode Register”: updated TRGSEL and TRACKTIM field descriptions Updated Section 61.7.8 “ADC Last Converted Data Register” Section 61.7.16 “ADC Extended Mode Register”: added bit SIGNMODE Updated Section 61.7.18 “ADC Channel Offset Register” Updated Section 61-1 “Analog-to-Digital Converter Block Diagram” and Section 61-7 “Analog Full Scale Ranges in Single-Ended/Differential Applications” Updated Table 62-5 “Oversampling Digital Output Range Values” Section 62. “Electrical Characteristics” Added: 13-Nov-15 - Section 62.11 “Analog Comparator Characteristics” - Section 62.14.1 “Maximum SPI Frequency” - Section 62.16.1 “Maximum QSPI Frequency” - Table 62-4 “I/O Switching Frequency” - Table 62-5 “QSPI I/O Switching Frequency” - Table 62-22 “UTMI PLL Characteristics” - Table 62-23 “Audio PLL Characteristics” Updated: - Table 62-1 “Absolute Maximum Ratings*” - Table 62-3 “DC Characteristics” - Table 63-8 “Typical Peripheral Power Consumption by Peripheral in Active Mode” to Table 62-11 “Typical Power Consumption for Backup Mode” - Table 62-14 “8 to 24 MHz Crystal Oscillator Characteristics” - Table 62-17 “12 MHz RC Oscillator Characteristics” to Table 62-22 “UTMI PLL Characteristics” - Table 62-36 “VDDBU Power-On Reset Characteristics” to Table 62-38 “VDDANA Power-On Reset Characteristics” Reworked Section 62.9 “USB HS Characteristics” Section 64. “Schematic Checklist” Updated: - Section 64.14.3 “DDR Layout and Design Considerations” - Figure 64-1 “1.2V, 1.35V/1.5V, 2V, 2.5V, 3.3V Power Supplies Schematics(1)” - Table 64-1 “Power Supply Connections”  2017 Microchip Technology Inc. DS60001476B-page 2609 SAMA5D2 SERIES Table 72-7: SAMA5D2 Datasheet Rev. 11267A Revision History Issue Date Changes 10-Sep-15 Preliminary Datasheet - First issue 25-Feb-15 Advance Information Datasheet. DS60001476B-page 2610  2017 Microchip Technology Inc. SAMA5D2 SERIES The Microchip Web Site Microchip provides online support via our web site at www.microchip.com. This web site is used as a means to make files and information easily available to customers. Accessible by using your favorite Internet browser, the web site contains the following information: • Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software • General Technical Support – Frequently Asked Questions (FAQ), technical support requests, online discussion groups, Microchip consultant program member listing • Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives Customer Change Notification Service Microchip’s customer notification service helps keep customers current on Microchip products. Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest. To register, access the Microchip web site at www.microchip.com. Under “Design Support”, click on “Customer Change Notification” and follow the registration instructions. Customer Support Users of Microchip products can receive assistance through several channels: • • • • Distributor or Representative Local Sales Office Field Application Engineer (FAE) Technical Support Customers should contact their distributor, representative or Field Application Engineer (FAE) for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in the back of this document. Technical support is available through the web site at: http://microchip.com/support  2017 Microchip Technology Inc. DS60001476B-page 2611 SAMA5D2 SERIES Product Identification System To order or obtain information, e.g., on pricing or delivery, refer to the factory or the listed sales office. ATSAMA5 D21 C - C U R Example: a) Architecture ATSAMA5D21C-CUR = ARM Cortex-A5 general-purpose microprocessor, 196-ball, Industrial temperature, BGA Package. Product Group Mask Revision Package Temperature Range Carrier Type Architecture: ATSAMA5 = ARM Cortex-A5 CPU Product Group: D21, D22, D23 D24 D26, D27, D28 = 196-ball general-purpose microprocessors = 256-ball general-purpose microprocessors = 289-ball general-purpose microprocessors Mask Revision: C Package: C = BGA Temperature Range: U N = -40°C to +85°C (Industrial) = -40°C to +105°C (Extended Industrial) Carrier Type: Blank R = Standard Packaging (tray) = Tape and Reel(1) DS60001476B-page 2612 Note 1: 2: Tape and Reel identifier only appears in the catalog part number description. This identifier is used for ordering purposes and is not printed on the device package. Check with your Microchip Sales Office for package availability with the Tape and Reel option. Small form-factor packaging options may be available. Please check www.microchip.com/packaging for small-form factor package availability, or contact your local Sales Office.  2017 Microchip Technology Inc. Microchip Devices Code Protection Feature Note the following details of the code protection feature on Microchip devices: • Microchip products meet the specification contained in their particular Microchip Data Sheet. • Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. • There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property. • Microchip is willing to work with the customer who is concerned about the integrity of their code. • Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.” Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act. Legal Notice Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated. Trademarks The Microchip name and logo, the Microchip logo, AnyRate, AVR, AVR logo, AVR Freaks, BeaconThings, BitCloud, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq, KeeLoq logo, Kleer, LANCheck, LINK MD, MediaLB, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch, RightTouch, SAM-BA, SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight Load, IntelliMOS, mTouch, Precision Edge, and Quiet-Wire are registered trademarks of Microchip Technology Incorporated in the U.S.A. Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BodyCom, chipKIT, chipKIT logo, CodeGuard, CryptoAuthentication, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial Programming, ICSP, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, Mindi, MiWi, motorBench, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PureSilicon, QMatrix, RightTouch logo, REAL ICE, Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total Endurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries. GestIC is a registered trademarks of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries. All other trademarks mentioned herein are property of their respective companies. © 2017, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved. ISBN: 978-1-5224-1912-9  2017 Microchip Technology Inc. DS60001476B-page 2613 Quality Management System Certified by DNV ISO/TS 16949 Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition, Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified. DS60001476B-page 2614  2017 Microchip Technology Inc. Worldwide Sales and Service AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE Corporate Office 2355 West Chandler Blvd. Chandler, AZ 85224-6199 Tel: 480-792-7200 Fax: 480-792-7277 Technical Support: http://www.microchip.com/ support Web Address: www.microchip.com Asia Pacific Office Suites 3707-14, 37th Floor Tower 6, The Gateway Harbour City, Kowloon China - Xiamen Tel: 86-592-2388138 Fax: 86-592-2388130 Austria - Wels Tel: 43-7242-2244-39 Fax: 43-7242-2244-393 China - Zhuhai Tel: 86-756-3210040 Fax: 86-756-3210049 Denmark - Copenhagen Tel: 45-4450-2828 Fax: 45-4485-2829 India - Bangalore Tel: 91-80-3090-4444 Fax: 91-80-3090-4123 Finland - Espoo Tel: 358-9-4520-820 Atlanta Duluth, GA Tel: 678-957-9614 Fax: 678-957-1455 Hong Kong Tel: 852-2943-5100 Fax: 852-2401-3431 Australia - Sydney Tel: 61-2-9868-6733 Fax: 61-2-9868-6755 China - Beijing Tel: 86-10-8569-7000 Fax: 86-10-8528-2104 Austin, TX Tel: 512-257-3370 China - Chengdu Tel: 86-28-8665-5511 Fax: 86-28-8665-7889 Boston Westborough, MA Tel: 774-760-0087 Fax: 774-760-0088 China - Chongqing Tel: 86-23-8980-9588 Fax: 86-23-8980-9500 Chicago Itasca, IL Tel: 630-285-0071 Fax: 630-285-0075 Dallas Addison, TX Tel: 972-818-7423 Fax: 972-818-2924 Detroit Novi, MI Tel: 248-848-4000 Houston, TX Tel: 281-894-5983 Indianapolis Noblesville, IN Tel: 317-773-8323 Fax: 317-773-5453 Los Angeles Mission Viejo, CA Tel: 949-462-9523 Fax: 949-462-9608 Raleigh, NC Tel: 919-844-7510 New York, NY Tel: 631-435-6000 San Jose, CA Tel: 408-735-9110 Tel: 408-436-4270 Canada - Toronto Tel: 905-673-0699 Fax: 905-673-6509 DS60001476B-page 2615 China - Dongguan Tel: 86-769-8702-9880 China - Guangzhou Tel: 86-20-8755-8029 China - Hangzhou Tel: 86-571-8792-8115 Fax: 86-571-8792-8116 China - Hong Kong SAR Tel: 852-2943-5100 Fax: 852-2401-3431 China - Nanjing Tel: 86-25-8473-2460 Fax: 86-25-8473-2470 China - Qingdao Tel: 86-532-8502-7355 Fax: 86-532-8502-7205 China - Shanghai Tel: 86-21-5407-5533 Fax: 86-21-5407-5066 China - Shenyang Tel: 86-24-2334-2829 Fax: 86-24-2334-2393 China - Shenzhen Tel: 86-755-8864-2200 Fax: 86-755-8203-1760 India - New Delhi Tel: 91-11-4160-8631 Fax: 91-11-4160-8632 India - Pune Tel: 91-20-3019-1500 Japan - Osaka Tel: 81-6-6152-7160 Fax: 81-6-6152-9310 Japan - Tokyo Tel: 81-3-6880- 3770 Fax: 81-3-6880-3771 Korea - Daegu Tel: 82-53-744-4301 Fax: 82-53-744-4302 Korea - Seoul Tel: 82-2-554-7200 Fax: 82-2-558-5932 or 82-2-558-5934 Malaysia - Kuala Lumpur Tel: 60-3-6201-9857 Fax: 60-3-6201-9859 Malaysia - Penang Tel: 60-4-227-8870 Fax: 60-4-227-4068 Philippines - Manila Tel: 63-2-634-9065 Fax: 63-2-634-9069 Singapore Tel: 65-6334-8870 Fax: 65-6334-8850 Taiwan - Hsin Chu Tel: 886-3-5778-366 Fax: 886-3-5770-955 Taiwan - Kaohsiung Tel: 886-7-213-7828 China - Wuhan Tel: 86-27-5980-5300 Fax: 86-27-5980-5118 Taiwan - Taipei Tel: 886-2-2508-8600 Fax: 886-2-2508-0102 China - Xian Tel: 86-29-8833-7252 Fax: 86-29-8833-7256 Thailand - Bangkok Tel: 66-2-694-1351 Fax: 66-2-694-1350 France - Paris Tel: 33-1-69-53-63-20 Fax: 33-1-69-30-90-79 France - Saint Cloud Tel: 33-1-30-60-70-00 Germany - Garching Tel: 49-8931-9700 Germany - Haan Tel: 49-2129-3766400 Germany - Heilbronn Tel: 49-7131-67-3636 Germany - Karlsruhe Tel: 49-721-625370 Germany - Munich Tel: 49-89-627-144-0 Fax: 49-89-627-144-44 Germany - Rosenheim Tel: 49-8031-354-560 Israel - Ra’anana Tel: 972-9-744-7705 Italy - Padova Tel: 39-049-7625286 Netherlands - Drunen Tel: 31-416-690399 Fax: 31-416-690340 Norway - Trondheim Tel: 47-7288-4388 Poland - Warsaw Tel: 48-22-3325737 Romania - Bucharest Tel: 40-21-407-87-50 Spain - Madrid Tel: 34-91-708-08-90 Fax: 34-91-708-08-91 Sweden - Gothenberg Tel: 46-31-704-60-40 Sweden - Stockholm Tel: 46-8-5090-4654 UK - Wokingham Tel: 44-118-921-5800 Fax: 44-118-921-5820  2017 Microchip Technology Inc.