Stellaris® LM4F120H5QR Microcontroller Data Sheet

TE X AS INS TRUM E NTS - ADVANCE INFO R MAT ION
Stellaris LM4F120H5QR Microcontroller

D ATA SHE E T
D S -LM4F 120H5 Q R- 1 2 4 5 4 . 2 4 8 0
C o p yri g h t 2 0 07-2012 Te xa s In stru me n ts In co rporated
Copyright
Copyright 2007-2012 Texas Instruments Incorporated All rights reserved. Stellaris and StellarisWare are registered trademarks of Texas Instruments Incorporated. ARM and Thumb are registered trademarks and Cortex is a trademark of ARM Limited. Other names and brands may be claimed as the property of others. ADVANCE INFORMATION concerns new products in the sampling or preproduction phase of development. Characteristic data and other specifications are subject to change without notice. Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of Texas Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet. Texas Instruments Incorporated 108 Wild Basin, Suite 350 Austin, TX 78746 http://www.ti.com/stellaris http://www-k.ext.ti.com/sc/technical-support/product-information-centers.htm
2 Texas Instruments-Advance Information
April 25, 2012
Table of Contents
Revision History ............................................................................................................................. 34 About This Document .................................................................................................................... 38
Audience .............................................................................................................................................. About This Manual ................................................................................................................................ Related Documents ............................................................................................................................... Documentation Conventions .................................................................................................................. 38 38 38 39 41 44 47 47 49 51 55 61 63 64 64
1
1.1 1.2 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.3.5 1.3.6 1.3.7 1.4
Architectural Overview .......................................................................................... 41

Stellaris LM4F Series Overview ..................................................................................... LM4F120H5QR Microcontroller Overview ....................................................................... LM4F120H5QR Microcontroller Features ........................................................................ ARM Cortex-M4F Processor Core .................................................................................. On-Chip Memory ........................................................................................................... Serial Communications Peripherals ................................................................................ System Integration ........................................................................................................ Analog .......................................................................................................................... JTAG and ARM Serial Wire Debug ................................................................................ Packaging and Temperature .......................................................................................... LM4F120H5QR Microcontroller Hardware Details ...........................................................
2
2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.4.7 2.5 2.5.1 2.5.2 2.5.3 2.5.4
The Cortex-M4F Processor ................................................................................... 65

Block Diagram .............................................................................................................. 66 Overview ...................................................................................................................... 67 System-Level Interface .................................................................................................. 67 Integrated Configurable Debug ...................................................................................... 67 Trace Port Interface Unit (TPIU) ..................................................................................... 68 Cortex-M4F System Component Details ......................................................................... 68 Programming Model ...................................................................................................... 69 Processor Mode and Privilege Levels for Software Execution ........................................... 69 Stacks .......................................................................................................................... 70 Register Map ................................................................................................................ 70 Register Descriptions .................................................................................................... 72 Exceptions and Interrupts .............................................................................................. 88 Data Types ................................................................................................................... 88 Memory Model .............................................................................................................. 88 Memory Regions, Types and Attributes ........................................................................... 90 Memory System Ordering of Memory Accesses .............................................................. 91 Behavior of Memory Accesses ....................................................................................... 91 Software Ordering of Memory Accesses ......................................................................... 92 Bit-Banding ................................................................................................................... 93 Data Storage ................................................................................................................ 95 Synchronization Primitives ............................................................................................. 96 Exception Model ........................................................................................................... 97 Exception States ........................................................................................................... 98 Exception Types ............................................................................................................ 98 Exception Handlers ..................................................................................................... 102 Vector Table ................................................................................................................ 102
April 25, 2012 Texas Instruments-Advance Information
Table of Contents
2.5.5 2.5.6 2.5.7 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.7 2.7.1 2.7.2 2.7.3 2.8
Exception Priorities ...................................................................................................... Interrupt Priority Grouping ............................................................................................ Exception Entry and Return ......................................................................................... Fault Handling ............................................................................................................. Fault Types ................................................................................................................. Fault Escalation and Hard Faults .................................................................................. Fault Status Registers and Fault Address Registers ...................................................... Lockup ....................................................................................................................... Power Management .................................................................................................... Entering Sleep Modes ................................................................................................. Wake Up from Sleep Mode .......................................................................................... The Wake-Up Interrupt Controller ................................................................................. Instruction Set Summary ..............................................................................................
103 104 104 107 108 108 109 109 110 110 110 111 111
3
3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.2 3.3 3.4 3.5 3.6 3.7
Cortex-M4 Peripherals ......................................................................................... 118

Functional Description ................................................................................................. 118 System Timer (SysTick) ............................................................................................... 119 Nested Vectored Interrupt Controller (NVIC) .................................................................. 120 System Control Block (SCB) ........................................................................................ 121 Memory Protection Unit (MPU) ..................................................................................... 121 Floating-Point Unit (FPU) ............................................................................................. 126 Register Map .............................................................................................................. 130 System Timer (SysTick) Register Descriptions .............................................................. 133 NVIC Register Descriptions .......................................................................................... 137 System Control Block (SCB) Register Descriptions ........................................................ 152 Memory Protection Unit (MPU) Register Descriptions .................................................... 181 Floating-Point Unit (FPU) Register Descriptions ............................................................ 190
4
4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.4 4.5 4.5.1 4.5.2
JTAG Interface ...................................................................................................... 196

Block Diagram ............................................................................................................ Signal Description ....................................................................................................... Functional Description ................................................................................................. JTAG Interface Pins ..................................................................................................... JTAG TAP Controller ................................................................................................... Shift Registers ............................................................................................................ Operational Considerations .......................................................................................... Initialization and Configuration ..................................................................................... Register Descriptions .................................................................................................. Instruction Register (IR) ............................................................................................... Data Registers ............................................................................................................ Signal Description ....................................................................................................... Functional Description ................................................................................................. Device Identification .................................................................................................... Reset Control .............................................................................................................. Non-Maskable Interrupt ............................................................................................... Power Control ............................................................................................................. Clock Control .............................................................................................................. System Control ........................................................................................................... Initialization and Configuration ..................................................................................... 197 197 198 198 200 200 201 203 203 204 206 208 208 208 209 213 214 215 222 225
5
5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3
System Control ..................................................................................................... 208
April 25, 2012
5.4 5.5 5.6
Register Map .............................................................................................................. 226 System Control Register Descriptions ........................................................................... 231 System Control Legacy Register Descriptions ............................................................... 415
6
6.1 6.2 6.3
System Exception Module ................................................................................... 472

Functional Description ................................................................................................. 472 Register Map .............................................................................................................. 472 Register Descriptions .................................................................................................. 472
7
7.1 7.2 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.3.5 7.3.6 7.3.7 7.3.8 7.3.9 7.3.10 7.3.11 7.3.12 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.5 7.6
Hibernation Module .............................................................................................. 480

Block Diagram ............................................................................................................ Signal Description ....................................................................................................... Functional Description ................................................................................................. Register Access Timing ............................................................................................... Hibernation Clock Source ............................................................................................ System Implementation ............................................................................................... Battery Management ................................................................................................... Real-Time Clock .......................................................................................................... Battery-Backed Memory .............................................................................................. Power Control Using HIB ............................................................................................. Power Control Using VDD3ON Mode ........................................................................... Initiating Hibernate ...................................................................................................... Waking from Hibernate ................................................................................................ Arbitrary Power Removal ............................................................................................. Interrupts and Status ................................................................................................... Initialization and Configuration ..................................................................................... Initialization ................................................................................................................. RTC Match Functionality (No Hibernation) .................................................................... RTC Match/Wake-Up from Hibernation ......................................................................... External Wake-Up from Hibernation .............................................................................. RTC or External Wake-Up from Hibernation .................................................................. Register Map .............................................................................................................. Register Descriptions .................................................................................................. 481 481 482 482 483 484 485 486 487 487 488 488 488 488 488 489 489 490 490 490 491 491 492
8
8.1 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.3 8.4 8.5 8.6
Internal Memory ................................................................................................... 510

Block Diagram ............................................................................................................ 510 Functional Description ................................................................................................. 511 SRAM ........................................................................................................................ 511 ROM .......................................................................................................................... 512 Flash Memory ............................................................................................................. 514 EEPROM .................................................................................................................... 518 Register Map .............................................................................................................. 523 Flash Memory Register Descriptions (Flash Control Offset) ............................................ 525 EEPROM Register Descriptions (EEPROM Offset) ........................................................ 543 Memory Register Descriptions (System Control Offset) .................................................. 559
9
9.1 9.2 9.2.1 9.2.2
Micro Direct Memory Access (DMA) ................................................................ 568

Block Diagram ............................................................................................................ Functional Description ................................................................................................. Channel Assignments .................................................................................................. Priority ........................................................................................................................ 569 569 570 571
Table of Contents
9.2.3 9.2.4 9.2.5 9.2.6 9.2.7 9.2.8 9.2.9 9.2.10 9.3 9.3.1 9.3.2 9.3.3 9.3.4 9.3.5 9.4 9.5 9.6
Arbitration Size ............................................................................................................ 571 Request Types ............................................................................................................ 571 Channel Configuration ................................................................................................. 572 Transfer Modes ........................................................................................................... 574 Transfer Size and Increment ........................................................................................ 582 Peripheral Interface ..................................................................................................... 582 Software Request ........................................................................................................ 582 Interrupts and Errors .................................................................................................... 583 Initialization and Configuration ..................................................................................... 583 Module Initialization ..................................................................................................... 583 Configuring a Memory-to-Memory Transfer ................................................................... 584 Configuring a Peripheral for Simple Transmit ................................................................ 585 Configuring a Peripheral for Ping-Pong Receive ............................................................ 587 Configuring Channel Assignments ................................................................................ 589 Register Map .............................................................................................................. 589 DMA Channel Control Structure ................................................................................. 591 DMA Register Descriptions ........................................................................................ 598
10
10.1 10.2 10.2.1 10.2.2 10.2.3 10.2.4 10.2.5 10.2.6 10.3 10.4 10.5
General-Purpose Input/Outputs (GPIOs) ........................................................... 632

Signal Description ....................................................................................................... 632 Functional Description ................................................................................................. 634 Data Control ............................................................................................................... 636 Interrupt Control .......................................................................................................... 637 Mode Control .............................................................................................................. 638 Commit Control ........................................................................................................... 639 Pad Control ................................................................................................................. 639 Identification ............................................................................................................... 639 Initialization and Configuration ..................................................................................... 639 Register Map .............................................................................................................. 640 Register Descriptions .................................................................................................. 643
11
11.1 11.2 11.3 11.3.1 11.3.2 11.3.3 11.3.4 11.3.5 11.3.6 11.3.7 11.4 11.4.1 11.4.2 11.4.3 11.4.4 11.4.5 11.5 11.6
General-Purpose Timers ...................................................................................... 686

Block Diagram ............................................................................................................ 687 Signal Description ....................................................................................................... 688 Functional Description ................................................................................................. 689 GPTM Reset Conditions .............................................................................................. 690 Timer Modes ............................................................................................................... 690 Wait-for-Trigger Mode .................................................................................................. 700 Synchronizing GP Timer Blocks ................................................................................... 701 DMA Operation ........................................................................................................... 702 Accessing Concatenated 16/32-Bit GPTM Register Values ............................................ 702 Accessing Concatenated 32/64-Bit Wide GPTM Register Values .................................... 702 Initialization and Configuration ..................................................................................... 704 One-Shot/Periodic Timer Mode .................................................................................... 704 Real-Time Clock (RTC) Mode ...................................................................................... 705 Input Edge-Count Mode ............................................................................................... 705 Input Edge Timing Mode .............................................................................................. 706 PWM Mode ................................................................................................................. 706 Register Map .............................................................................................................. 707 Register Descriptions .................................................................................................. 708
April 25, 2012
12
12.1 12.2 12.2.1 12.3 12.4 12.5
Watchdog Timers ................................................................................................. 756

Block Diagram ............................................................................................................ Functional Description ................................................................................................. Register Access Timing ............................................................................................... Initialization and Configuration ..................................................................................... Register Map .............................................................................................................. Register Descriptions .................................................................................................. 757 757 758 758 758 759
13
13.1 13.2 13.3 13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 13.3.6 13.3.7 13.4 13.4.1 13.4.2 13.5 13.6
Analog-to-Digital Converter (ADC) ..................................................................... 781

Block Diagram ............................................................................................................ 782 Signal Description ....................................................................................................... 783 Functional Description ................................................................................................. 784 Sample Sequencers .................................................................................................... 784 Module Control ............................................................................................................ 785 Hardware Sample Averaging Circuit ............................................................................. 788 Analog-to-Digital Converter .......................................................................................... 788 Differential Sampling ................................................................................................... 791 Internal Temperature Sensor ........................................................................................ 793 Digital Comparator Unit ............................................................................................... 794 Initialization and Configuration ..................................................................................... 798 Module Initialization ..................................................................................................... 798 Sample Sequencer Configuration ................................................................................. 799 Register Map .............................................................................................................. 799 Register Descriptions .................................................................................................. 801
14
Universal Asynchronous Receivers/Transmitters (UARTs) ............................. 861

862 862 863 863 864 865 865 866 866 867 869 869 870 871 871 871 872 874 925 925 926 926 927
14.1 Block Diagram ............................................................................................................ 14.2 Signal Description ....................................................................................................... 14.3 Functional Description ................................................................................................. 14.3.1 Transmit/Receive Logic ............................................................................................... 14.3.2 Baud-Rate Generation ................................................................................................. 14.3.3 Data Transmission ...................................................................................................... 14.3.4 Serial IR (SIR) ............................................................................................................. 14.3.5 ISO 7816 Support ....................................................................................................... 14.3.6 Modem Handshake Support ......................................................................................... 14.3.7 LIN Support ................................................................................................................ 14.3.8 9-Bit UART Mode ........................................................................................................ 14.3.9 FIFO Operation ........................................................................................................... 14.3.10 Interrupts .................................................................................................................... 14.3.11 Loopback Operation .................................................................................................... 14.3.12 DMA Operation ........................................................................................................... 14.4 Initialization and Configuration ..................................................................................... 14.5 Register Map .............................................................................................................. 14.6 Register Descriptions ..................................................................................................
15
15.1 15.2 15.3 15.3.1 15.3.2
Synchronous Serial Interface (SSI) .................................................................... 924

Block Diagram ............................................................................................................ Signal Description ....................................................................................................... Functional Description ................................................................................................. Bit Rate Generation ..................................................................................................... FIFO Operation ...........................................................................................................
Table of Contents
15.3.3 15.3.4 15.3.5 15.4 15.5 15.6
Interrupts .................................................................................................................... Frame Formats ........................................................................................................... DMA Operation ........................................................................................................... Initialization and Configuration ..................................................................................... Register Map .............................................................................................................. Register Descriptions ..................................................................................................
927 928 935 936 937 938
16
16.1 16.2 16.3 16.3.1 16.3.2 16.3.3 16.3.4 16.3.5 16.4 16.5 16.6 16.7 16.8
Inter-Integrated Circuit (I2C) Interface ................................................................ 967

Block Diagram ............................................................................................................ 968 Signal Description ....................................................................................................... 968 Functional Description ................................................................................................. 969 I2C Bus Functional Overview ........................................................................................ 969 Available Speed Modes ............................................................................................... 973 Interrupts .................................................................................................................... 974 Loopback Operation .................................................................................................... 975 Command Sequence Flow Charts ................................................................................ 976 Initialization and Configuration ..................................................................................... 984 Register Map .............................................................................................................. 985 Register Descriptions (I2C Master) ............................................................................... 986 Register Descriptions (I2C Slave) ............................................................................... 1001 Register Descriptions (I2C Status and Control) ............................................................ 1011
17
Controller Area Network (CAN) Module ........................................................... 1014
17.1 Block Diagram ........................................................................................................... 1015 17.2 Signal Description ..................................................................................................... 1015 17.3 Functional Description ............................................................................................... 1016 17.3.1 Initialization ............................................................................................................... 1017 17.3.2 Operation .................................................................................................................. 1017 17.3.3 Transmitting Message Objects ................................................................................... 1018 17.3.4 Configuring a Transmit Message Object ...................................................................... 1019 17.3.5 Updating a Transmit Message Object ......................................................................... 1020 17.3.6 Accepting Received Message Objects ........................................................................ 1020 17.3.7 Receiving a Data Frame ............................................................................................ 1021 17.3.8 Receiving a Remote Frame ........................................................................................ 1021 17.3.9 Receive/Transmit Priority ........................................................................................... 1021 17.3.10 Configuring a Receive Message Object ...................................................................... 1022 17.3.11 Handling of Received Message Objects ...................................................................... 1023 17.3.12 Handling of Interrupts ................................................................................................ 1025 17.3.13 Test Mode ................................................................................................................. 1026 17.3.14 Bit Timing Configuration Error Considerations ............................................................. 1028 17.3.15 Bit Time and Bit Rate ................................................................................................. 1028 17.3.16 Calculating the Bit Timing Parameters ........................................................................ 1030 17.4 Register Map ............................................................................................................ 1033 17.5 CAN Register Descriptions ......................................................................................... 1034
18
18.1 18.2 18.3 18.3.1
Universal Serial Bus (USB) Controller ............................................................. 1064

Block Diagram ........................................................................................................... Signal Description ..................................................................................................... Functional Description ............................................................................................... Operation .................................................................................................................. 1064 1065 1065 1065
April 25, 2012
18.3.2 18.4 18.4.1 18.5 18.6
DMA Operation ......................................................................................................... 1070 Initialization and Configuration .................................................................................... 1071 Endpoint Configuration .............................................................................................. 1071 Register Map ............................................................................................................ 1072 Register Descriptions ................................................................................................. 1075
19
19.1 19.2 19.3 19.3.1 19.4 19.5 19.6
Analog Comparators .......................................................................................... 1121

Block Diagram ........................................................................................................... Signal Description ..................................................................................................... Functional Description ............................................................................................... Internal Reference Programming ................................................................................ Initialization and Configuration .................................................................................... Register Map ............................................................................................................ Register Descriptions ................................................................................................. 1122 1122 1123 1123 1126 1126 1127
20 21
21.1
Pin Diagram ........................................................................................................ 1136 Signal Tables ...................................................................................................... 1137

Connections for Unused Signals ................................................................................. 1156
22 23
Operating Characteristics ................................................................................. 1157 Electrical Characteristics .................................................................................. 1158
23.1 Maximum Ratings ...................................................................................................... 1158 23.2 Recommended Operating Conditions ......................................................................... 1159 23.3 Load Conditions ........................................................................................................ 1160 23.4 JTAG and Boundary Scan .......................................................................................... 1161 23.5 Power and Brown-Out ............................................................................................... 1162 23.6 Reset ........................................................................................................................ 1163 23.7 On-Chip Low Drop-Out (LDO) Regulator ..................................................................... 1164 23.8 Clocks ...................................................................................................................... 1165 23.8.1 PLL Specifications ..................................................................................................... 1165 23.8.2 PIOSC Specifications ................................................................................................ 1166 23.8.3 Internal 30-kHz Oscillator Specifications ..................................................................... 1166 23.8.4 Hibernation Clock Source Specifications ..................................................................... 1166 23.8.5 Main Oscillator Specifications ..................................................................................... 1167 23.8.6 System Clock Specification with ADC Operation .......................................................... 1170 23.8.7 System Clock Specification with USB Operation .......................................................... 1170 23.9 Sleep Modes ............................................................................................................. 1171 23.10 Hibernation Module ................................................................................................... 1171 23.11 Flash Memory and EEPROM ..................................................................................... 1172 23.12 Input/Output Characteristics ....................................................................................... 1173 23.13 Analog-to-Digital Converter (ADC) .............................................................................. 1174 23.14 Synchronous Serial Interface (SSI) ............................................................................. 1176 23.15 Inter-Integrated Circuit (I2C) Interface ......................................................................... 1178 23.16 Universal Serial Bus (USB) Controller ......................................................................... 1178 23.17 Analog Comparator ................................................................................................... 1178 23.18 Current Consumption ................................................................................................. 1180 23.18.1 Preliminary Current Consumption ............................................................................... 1180
A B
Register Quick Reference ................................................................................. 1182 Ordering and Contact Information ................................................................... 1224
Table of Contents
B.1 B.2 B.3 B.4
Ordering Information .................................................................................................. Part Markings ............................................................................................................ Kits ........................................................................................................................... Support Information ...................................................................................................
1224 1224 1224 1225
C
C.1 C.1.1
Package Information .......................................................................................... 1226

64-Pin LQFP Package ............................................................................................... 1226 Package Dimensions ................................................................................................. 1226
April 25, 2012
List of Figures
Figure 1-1. Figure 1-2. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 3-1. Figure 3-2. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4. Figure 5-5. Figure 5-6. Figure 7-1. Figure 7-2. Figure 7-3. Figure 7-4. Figure 8-1. Figure 8-2. Figure 9-1. Figure 9-2. Figure 9-3. Figure 9-4. Figure 9-5. Figure 9-6. Figure 10-1. Figure 10-2. Figure 10-3. Figure 10-4. Figure 11-1. Figure 11-2. Figure 11-3. Figure 11-4. Figure 11-5. Figure 11-6. Figure 11-7. Stellaris LM4F Block Diagram .............................................................................. 42 Stellaris LM4F120H5QR Microcontroller High-Level Block Diagram ........................ 46 CPU Block Diagram ............................................................................................. 67 TPIU Block Diagram ............................................................................................ 68 Cortex-M4F Register Set ...................................................................................... 71 Bit-Band Mapping ................................................................................................ 95 Data Storage ....................................................................................................... 96 Vector Table ...................................................................................................... 103 Exception Stack Frame ...................................................................................... 106 SRD Use Example ............................................................................................. 124 FPU Register Bank ............................................................................................ 127 JTAG Module Block Diagram .............................................................................. 197 Test Access Port State Machine ......................................................................... 200 IDCODE Register Format ................................................................................... 206 BYPASS Register Format ................................................................................... 206 Boundary Scan Register Format ......................................................................... 207 Basic RST Configuration .................................................................................... 211 External Circuitry to Extend Power-On Reset ....................................................... 211 Reset Circuit Controlled by Switch ...................................................................... 212 Power Architecture ............................................................................................ 215 Main Clock Tree ................................................................................................ 218 Module Clock Selection ...................................................................................... 225 Hibernation Module Block Diagram ..................................................................... 481 Using a Crystal as the Hibernation Clock Source with a Single Battery Source ...... 483 Using a Dedicated Oscillator as the Hibernation Clock Source with VDD3ON Mode ................................................................................................................ 484 Using a Regulator for Both VDD and VBAT ............................................................ 485 Internal Memory Block Diagram .......................................................................... 510 EEPROM Block Diagram ................................................................................... 511 DMA Block Diagram ......................................................................................... 569 Example of Ping-Pong DMA Transaction ........................................................... 575 Memory Scatter-Gather, Setup and Configuration ................................................ 577 Memory Scatter-Gather, DMA Copy Sequence .................................................. 578 Peripheral Scatter-Gather, Setup and Configuration ............................................. 580 Peripheral Scatter-Gather, DMA Copy Sequence ............................................... 581 Digital I/O Pads ................................................................................................. 635 Analog/Digital I/O Pads ...................................................................................... 636 GPIODATA Write Example ................................................................................. 637 GPIODATA Read Example ................................................................................. 637 GPTM Module Block Diagram ............................................................................ 687 Reading the RTC Value ...................................................................................... 694 Input Edge-Count Mode Example, Counting Down ............................................... 696 16-Bit Input Edge-Time Mode Example ............................................................... 697 16-Bit PWM Mode Example ................................................................................ 699 CCP Output, GPTMTnMATCHR > GPTMTnILR ................................................... 699 CCP Output, GPTMTnMATCHR = GPTMTnILR ................................................... 700
11
Table of Contents
Figure 11-8. Figure 11-9. Figure 12-1. Figure 13-1. Figure 13-2. Figure 13-3. Figure 13-4. Figure 13-5. Figure 13-6. Figure 13-7. Figure 13-8. Figure 13-9. Figure 13-10. Figure 13-11. Figure 13-12. Figure 13-13. Figure 13-14. Figure 14-1. Figure 14-2. Figure 14-3. Figure 14-4. Figure 14-5. Figure 15-1. Figure 15-2. Figure 15-3. Figure 15-4. Figure 15-5. Figure 15-6. Figure 15-7. Figure 15-8. Figure 15-9. Figure 15-10. Figure 15-11. Figure 15-12. Figure 16-1. Figure 16-2. Figure 16-3. Figure 16-4. Figure 16-5. Figure 16-6. Figure 16-7. Figure 16-8. Figure 16-9. Figure 16-10. Figure 16-11. Figure 16-12.
CCP Output, GPTMTnILR > GPTMTnMATCHR ................................................... 700 Timer Daisy Chain ............................................................................................. 701 WDT Module Block Diagram .............................................................................. 757 Implementation of Two ADC Blocks .................................................................... 782 ADC Module Block Diagram ............................................................................... 783 ADC Sample Phases ......................................................................................... 786 Doubling the ADC Sample Rate .......................................................................... 787 Skewed Sampling .............................................................................................. 787 Sample Averaging Example ............................................................................... 788 ADC Input Equivalency Diagram ......................................................................... 789 ADC Voltage Reference ..................................................................................... 790 ADC Conversion Result ..................................................................................... 791 Differential Voltage Representation ..................................................................... 793 Internal Temperature Sensor Characteristic ......................................................... 794 Low-Band Operation (CIC=0x0) .......................................................................... 796 Mid-Band Operation (CIC=0x1) .......................................................................... 797 High-Band Operation (CIC=0x3) ......................................................................... 798 UART Module Block Diagram ............................................................................. 862 UART Character Frame ..................................................................................... 864 IrDA Data Modulation ......................................................................................... 866 LIN Message ..................................................................................................... 868 LIN Synchronization Field ................................................................................... 869 SSI Module Block Diagram ................................................................................. 925 TI Synchronous Serial Frame Format (Single Transfer) ........................................ 929 TI Synchronous Serial Frame Format (Continuous Transfer) ................................ 929 Freescale SPI Format (Single Transfer) with SPO=0 and SPH=0 .......................... 930 Freescale SPI Format (Continuous Transfer) with SPO=0 and SPH=0 .................. 930 Freescale SPI Frame Format with SPO=0 and SPH=1 ......................................... 931 Freescale SPI Frame Format (Single Transfer) with SPO=1 and SPH=0 ............... 932 Freescale SPI Frame Format (Continuous Transfer) with SPO=1 and SPH=0 ........ 932 Freescale SPI Frame Format with SPO=1 and SPH=1 ......................................... 933 MICROWIRE Frame Format (Single Frame) ........................................................ 934 MICROWIRE Frame Format (Continuous Transfer) ............................................. 935 MICROWIRE Frame Format, SSIFss Input Setup and Hold Requirements ............ 935 I2C Block Diagram ............................................................................................. 968 I2C Bus Configuration ........................................................................................ 969 START and STOP Conditions ............................................................................. 970 Complete Data Transfer with a 7-Bit Address ....................................................... 970 R/S Bit in First Byte ............................................................................................ 971 Data Validity During Bit Transfer on the I2C Bus ................................................... 971 High-Speed Data Format ................................................................................... 973 Master Single TRANSMIT .................................................................................. 977 Master Single RECEIVE ..................................................................................... 978 Master TRANSMIT with Repeated START ........................................................... 979 Master RECEIVE with Repeated START ............................................................. 980 Master RECEIVE with Repeated START after TRANSMIT with Repeated START .............................................................................................................. 981
April 25, 2012
Figure 16-13. Master TRANSMIT with Repeated START after RECEIVE with Repeated START .............................................................................................................. 982 Figure 16-14. High Speed Mode Master Transmit ..................................................................... 983 Figure 16-15. Slave Command Sequence ................................................................................ 984 Figure 17-1. CAN Controller Block Diagram .......................................................................... 1015 Figure 17-2. CAN Data/Remote Frame ................................................................................. 1016 Figure 17-3. Message Objects in a FIFO Buffer .................................................................... 1025 Figure 17-4. CAN Bit Time ................................................................................................... 1029 Figure 18-1. USB Module Block Diagram ............................................................................. 1064 Figure 19-1. Analog Comparator Module Block Diagram ....................................................... 1122 Figure 19-2. Structure of Comparator Unit ............................................................................ 1123 Figure 19-3. Comparator Internal Reference Structure .......................................................... 1124 Figure 20-1. 64-Pin LQFP Package Pin Diagram .................................................................. 1136 Figure 23-1. ESD Protection on GPIOs and XOSCn Pins ...................................................... 1159 Figure 23-2. ESD Protection on Non-Power, Non-GPIO, and Non-XOSCn Pins ...................... 1159 Figure 23-3. Load Conditions ............................................................................................... 1160 Figure 23-4. JTAG Test Clock Input Timing ........................................................................... 1161 Figure 23-5. JTAG Test Access Port (TAP) Timing ................................................................ 1162 Figure 23-6. Power-On and Brown-Out Reset and Voltage Parameters .................................. 1163 Figure 23-7. Brown-Out Reset Timing .................................................................................. 1163 Figure 23-8. External Reset Timing (RST) ............................................................................ 1164 Figure 23-9. Software Reset Timing ..................................................................................... 1164 Figure 23-10. Watchdog Reset Timing ................................................................................... 1164 Figure 23-11. MOSC Failure Reset Timing ............................................................................. 1164 Figure 23-12. Hibernation Module Timing ............................................................................... 1172 Figure 23-13. ADC Input Equivalency Diagram ....................................................................... 1176 Figure 23-14. SSI Timing for TI Frame Format (FRF=01), Single Transfer Timing Measurement .................................................................................................. 1177 Figure 23-15. SSI Timing for MICROWIRE Frame Format (FRF=10), Single Transfer ............... 1177 Figure 23-16. SSI Timing for SPI Frame Format (FRF=00), with SPH=1 ................................... 1177 Figure 23-17. I2C Timing ....................................................................................................... 1178 Figure C-1. Stellaris LM4F120H5QR 64-Pin LQFP Package ................................................ 1226
13
Table of Contents
List of Tables
Table 1. Table 2. Table 1-1. Table 1-2. Table 1-3. Table 1-4. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 2-6. Table 2-7. Table 2-8. Table 2-9. Table 2-10. Table 2-11. Table 2-12. Table 2-13. Table 3-1. Table 3-2. Table 3-3. Table 3-4. Table 3-5. Table 3-6. Table 3-7. Table 3-8. Table 3-9. Table 3-10. Table 4-1. Table 4-2. Table 4-3. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 5-7. Table 5-8. Table 6-1. Table 7-1. Table 7-2. Table 7-3. Table 7-4. Table 7-5. Revision History .................................................................................................. 34 Documentation Conventions ................................................................................ 39 Stellaris LM4F Device Series ................................................................................ 42 Stellaris LM4F12x Series ..................................................................................... 43 Stellaris LM4F Family of Devices .......................................................................... 43 Stellaris LM4F120H5QR Microcontroller Features ................................................. 45 Summary of Processor Mode, Privilege Level, and Stack Use ................................ 70 Processor Register Map ....................................................................................... 71 PSR Register Combinations ................................................................................. 77 Memory Map ....................................................................................................... 88 Memory Access Behavior ..................................................................................... 91 SRAM Memory Bit-Banding Regions .................................................................... 93 Peripheral Memory Bit-Banding Regions ............................................................... 93 Exception Types .................................................................................................. 99 Interrupts .......................................................................................................... 100 Exception Return Behavior ................................................................................. 107 Faults ............................................................................................................... 108 Fault Status and Fault Address Registers ............................................................ 109 Cortex-M4F Instruction Summary ....................................................................... 111 Core Peripheral Register Regions ....................................................................... 118 Memory Attributes Summary .............................................................................. 122 TEX, S, C, and B Bit Field Encoding ................................................................... 124 Cache Policy for Memory Attribute Encoding ....................................................... 125 AP Bit Field Encoding ........................................................................................ 125 Memory Region Attributes for Stellaris Microcontrollers ........................................ 126 QNaN and SNaN Handling ................................................................................. 129 Peripherals Register Map ................................................................................... 130 Interrupt Priority Levels ...................................................................................... 160 Example SIZE Field Values ................................................................................ 188 JTAG_SWD_SWO Signals (64LQFP) ................................................................. 197 JTAG Port Pins State after Power-On Reset or RST assertion .............................. 198 JTAG Instruction Register Commands ................................................................. 204 System Control & Clocks Signals (64LQFP) ........................................................ 208 Reset Sources ................................................................................................... 209 Clock Source Options ........................................................................................ 216 Possible System Clock Frequencies Using the SYSDIV Field ............................... 219 Examples of Possible System Clock Frequencies Using the SYSDIV2 Field .......... 219 Examples of Possible System Clock Frequencies with DIV400=1 ......................... 220 System Control Register Map ............................................................................. 226 RCC2 Fields that Override RCC Fields ............................................................... 251 System Exception Register Map ......................................................................... 472 Hibernate Signals (64LQFP) ............................................................................... 481 Counter Behavior with a TRIM Value of 0x8003 ................................................... 486 Counter Behavior with a TRIM Value of 0x7FFC .................................................. 487 Hibernation Module Clock Operation ................................................................... 490 Hibernation Module Register Map ....................................................................... 491
April 25, 2012
Table 8-1. Table 8-2. Table 8-3. Table 9-1. Table 9-2. Table 9-3. Table 9-4. Table 9-5. Table 9-6. Table 9-7. Table 9-8. Table 9-9. Table 9-10. Table 9-11. Table 9-12.
Flash Memory Protection Policy Combinations .................................................... 515 User-Programmable Flash Memory Resident Registers ....................................... 518 Flash Register Map ............................................................................................ 523 DMA Channel Assignments .............................................................................. 570 Request Type Support ....................................................................................... 572 Control Structure Memory Map ........................................................................... 573 Channel Control Structure .................................................................................. 573 DMA Read Example: 8-Bit Peripheral ................................................................ 582 DMA Interrupt Assignments .............................................................................. 583 Channel Control Structure Offsets for Channel 30 ................................................ 584 Channel Control Word Configuration for Memory Transfer Example ...................... 584 Channel Control Structure Offsets for Channel 7 .................................................. 585 Channel Control Word Configuration for Peripheral Transmit Example .................. 586 Primary and Alternate Channel Control Structure Offsets for Channel 8 ................. 587 Channel Control Word Configuration for Peripheral Ping-Pong Receive Example ............................................................................................................ 588 Table 9-13. DMA Register Map .......................................................................................... 590 Table 10-1. GPIO Pins With Non-Zero Reset Values .............................................................. 633 Table 10-2. GPIO Pins and Alternate Functions (64LQFP) ..................................................... 633 Table 10-3. GPIO Pad Configuration Examples ..................................................................... 639 Table 10-4. GPIO Interrupt Configuration Example ................................................................ 640 Table 10-5. GPIO Pins With Non-Zero Reset Values .............................................................. 641 Table 10-6. GPIO Register Map ........................................................................................... 641 Table 10-7. GPIO Pins With Non-Zero Reset Values .............................................................. 653 Table 10-8. GPIO Pins With Non-Zero Reset Values .............................................................. 659 Table 10-9. GPIO Pins With Non-Zero Reset Values .............................................................. 661 Table 10-10. GPIO Pins With Non-Zero Reset Values .............................................................. 664 Table 10-11. GPIO Pins With Non-Zero Reset Values .............................................................. 670 Table 11-1. Available CCP Pins ............................................................................................ 687 Table 11-2. General-Purpose Timers Signals (64LQFP) ......................................................... 688 Table 11-3. General-Purpose Timer Capabilities .................................................................... 690 Table 11-4. Counter Values When the Timer is Enabled in Periodic or One-Shot Modes .......... 691 Table 11-5. 16-Bit Timer With Prescaler Configurations ......................................................... 692 Table 11-6. 32-Bit Timer (configured in 32/64-bit mode) With Prescaler Configurations ............ 692 Table 11-7. Counter Values When the Timer is Enabled in RTC Mode .................................... 693 Table 11-8. Counter Values When the Timer is Enabled in Input Edge-Count Mode ................. 695 Table 11-9. Counter Values When the Timer is Enabled in Input Event-Count Mode ................ 696 Table 11-10. Counter Values When the Timer is Enabled in PWM Mode ................................... 698 Table 11-11. Timeout Actions for GPTM Modes ...................................................................... 701 Table 11-12. Timers Register Map .......................................................................................... 707 Table 12-1. Watchdog Timers Register Map .......................................................................... 759 Table 13-1. ADC Signals (64LQFP) ...................................................................................... 783 Table 13-2. Samples and FIFO Depth of Sequencers ............................................................ 784 Table 13-3. Differential Sampling Pairs ................................................................................. 791 Table 13-4. ADC Register Map ............................................................................................. 799 Table 14-1. UART Signals (64LQFP) .................................................................................... 863 Table 14-2. Flow Control Mode ............................................................................................. 867 Table 14-3. UART Register Map ........................................................................................... 873
15
Table of Contents
Table 15-1. Table 15-2. Table 16-1. Table 16-2. Table 16-3. Table 16-4. Table 16-5. Table 17-1. Table 17-2. Table 17-3. Table 17-4. Table 17-5. Table 18-1. Table 18-2. Table 18-3. Table 18-4. Table 18-5. Table 19-1. Table 19-2. Table 19-3. Table 19-4. Table 19-5. Table 21-1. Table 21-2. Table 21-3. Table 21-4. Table 21-5. Table 21-6. Table 21-7. Table 22-1. Table 22-2. Table 22-3. Table 23-1. Table 23-2. Table 23-3. Table 23-4. Table 23-5. Table 23-6. Table 23-7. Table 23-8. Table 23-9. Table 23-10. Table 23-11. Table 23-12. Table 23-13. Table 23-14.
SSI Signals (64LQFP) ........................................................................................ 926 SSI Register Map .............................................................................................. 937 I2C Signals (64LQFP) ........................................................................................ 968 Examples of I2C Master Timer Period versus Speed Mode ................................... 974 Examples of I2C Master Timer Period in High-Speed Mode .................................. 974 Inter-Integrated Circuit (I2C) Interface Register Map ............................................. 985 Write Field Decoding for I2CMCS[3:0] Field ......................................................... 991 Controller Area Network Signals (64LQFP) ........................................................ 1016 Message Object Configurations ........................................................................ 1021 CAN Protocol Ranges ...................................................................................... 1029 CANBIT Register Values .................................................................................. 1029 CAN Register Map ........................................................................................... 1033 USB Signals (64LQFP) .................................................................................... 1065 Remainder (MAXLOAD/4) ................................................................................ 1070 Actual Bytes Read ........................................................................................... 1071 Packet Sizes That Clear RXRDY ...................................................................... 1071 Universal Serial Bus (USB) Controller Register Map ........................................... 1072 Analog Comparators Signals (64LQFP) ............................................................. 1122 Internal Reference Voltage and ACREFCTL Field Values ................................... 1124 Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 0 .......................................................................................................... 1125 Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 1 .......................................................................................................... 1125 Analog Comparators Register Map ................................................................... 1126 GPIO Pins With Default Alternate Functions ...................................................... 1137 Signals by Pin Number ..................................................................................... 1138 Signals by Signal Name ................................................................................... 1143 Signals by Function, Except for GPIO ............................................................... 1148 GPIO Pins and Alternate Functions ................................................................... 1152 Possible Pin Assignments for Alternate Functions .............................................. 1154 Connections for Unused Signals (64-Pin LQFP) ................................................. 1156 Temperature Characteristics ............................................................................. 1157 Thermal Characteristics ................................................................................... 1157 ESD Absolute Maximum Ratings ...................................................................... 1157 Maximum Ratings ............................................................................................ 1158 Recommended DC Operating Conditions .......................................................... 1159 GPIO Current Restrictions ................................................................................ 1160 GPIO Package Side Assignments ..................................................................... 1160 JTAG Characteristics ....................................................................................... 1161 Power Characteristics ...................................................................................... 1162 Reset Characteristics ....................................................................................... 1163 LDO Regulator Characteristics ......................................................................... 1164 Phase Locked Loop (PLL) Characteristics ......................................................... 1165 Actual PLL Frequency ...................................................................................... 1165 PIOSC Clock Characteristics ............................................................................ 1166 30-kHz Clock Characteristics ............................................................................ 1166 HIB Oscillator Input Characteristics ................................................................... 1166 Main Oscillator Input Characteristics ................................................................. 1167
April 25, 2012
Table 23-15. Table 23-16. Table 23-17. Table 23-18. Table 23-19. Table 23-20. Table 23-21. Table 23-22. Table 23-23. Table 23-24. Table 23-25. Table 23-26. Table 23-27. Table 23-28. Table 23-29. Table 23-30.
Crystal Parameters .......................................................................................... 1169 Supported MOSC Crystal Frequencies .............................................................. 1169 System Clock Characteristics with ADC Operation ............................................. 1170 System Clock Characteristics with USB Operation ............................................. 1170 Sleep Modes AC Characteristics ....................................................................... 1171 Hibernation Module Battery Characteristics ....................................................... 1171 Hibernation Module AC Characteristics ............................................................. 1171 Flash Memory Characteristics ........................................................................... 1172 EEPROM Characteristics ................................................................................. 1172 GPIO Module Characteristics ............................................................................ 1173 ADC Electrical Characteristics .......................................................................... 1174 SSI Characteristics .......................................................................................... 1176 I2C Characteristics ........................................................................................... 1178 Analog Comparator Characteristics ................................................................... 1178 Analog Comparator Voltage Reference Characteristics ...................................... 1179 Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 0 .......................................................................................................... 1179 Table 23-31. Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 1 .......................................................................................................... 1179 Table 23-32. Preliminary Current Consumption ..................................................................... 1180 Table B-1. Part Ordering Information ................................................................................. 1224
17
Table of Contents
List of Registers
The Cortex-M4F Processor ........................................................................................................... 65
Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Cortex General-Purpose Register 0 (R0) ........................................................................... 73 Cortex General-Purpose Register 1 (R1) ........................................................................... 73 Cortex General-Purpose Register 2 (R2) ........................................................................... 73 Cortex General-Purpose Register 3 (R3) ........................................................................... 73 Cortex General-Purpose Register 4 (R4) ........................................................................... 73 Cortex General-Purpose Register 5 (R5) ........................................................................... 73 Cortex General-Purpose Register 6 (R6) ........................................................................... 73 Cortex General-Purpose Register 7 (R7) ........................................................................... 73 Cortex General-Purpose Register 8 (R8) ........................................................................... 73 Cortex General-Purpose Register 9 (R9) ........................................................................... 73 Cortex General-Purpose Register 10 (R10) ....................................................................... 73 Cortex General-Purpose Register 11 (R11) ........................................................................ 73 Cortex General-Purpose Register 12 (R12) ....................................................................... 73 Stack Pointer (SP) ........................................................................................................... 74 Link Register (LR) ............................................................................................................ 75 Program Counter (PC) ..................................................................................................... 76 Program Status Register (PSR) ........................................................................................ 77 Priority Mask Register (PRIMASK) .................................................................................... 81 Fault Mask Register (FAULTMASK) .................................................................................. 82 Base Priority Mask Register (BASEPRI) ............................................................................ 83 Control Register (CONTROL) ........................................................................................... 84 Floating-Point Status Control (FPSC) ................................................................................ 86 SysTick Control and Status Register (STCTRL), offset 0x010 ........................................... 134 SysTick Reload Value Register (STRELOAD), offset 0x014 .............................................. 136 SysTick Current Value Register (STCURRENT), offset 0x018 ........................................... 137 Interrupt 0-31 Set Enable (EN0), offset 0x100 .................................................................. 138 Interrupt 32-63 Set Enable (EN1), offset 0x104 ................................................................ 138 Interrupt 64-95 Set Enable (EN2), offset 0x108 ................................................................ 138 Interrupt 96-127 Set Enable (EN3), offset 0x10C ............................................................. 138 Interrupt 128-138 Set Enable (EN4), offset 0x110 ............................................................ 139 Interrupt 0-31 Clear Enable (DIS0), offset 0x180 .............................................................. 140 Interrupt 32-63 Clear Enable (DIS1), offset 0x184 ............................................................ 140 Interrupt 64-95 Clear Enable (DIS2), offset 0x188 ............................................................ 140 Interrupt 96-127 Clear Enable (DIS3), offset 0x18C .......................................................... 140 Interrupt 128-138 Clear Enable (DIS4), offset 0x190 ........................................................ 141 Interrupt 0-31 Set Pending (PEND0), offset 0x200 ........................................................... 142 Interrupt 32-63 Set Pending (PEND1), offset 0x204 ......................................................... 142 Interrupt 64-95 Set Pending (PEND2), offset 0x208 ......................................................... 142 Interrupt 96-127 Set Pending (PEND3), offset 0x20C ....................................................... 142 Interrupt 128-138 Set Pending (PEND4), offset 0x210 ...................................................... 143 Interrupt 0-31 Clear Pending (UNPEND0), offset 0x280 ................................................... 144 Interrupt 32-63 Clear Pending (UNPEND1), offset 0x284 .................................................. 144 Interrupt 64-95 Clear Pending (UNPEND2), offset 0x288 .................................................. 144
Cortex-M4 Peripherals ................................................................................................................. 118
April 25, 2012
Register 22: Register 23: Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: Register 31: Register 32: Register 33: Register 34: Register 35: Register 36: Register 37: Register 38: Register 39: Register 40: Register 41: Register 42: Register 43: Register 44: Register 45: Register 46: Register 47: Register 48: Register 49: Register 50: Register 51: Register 52: Register 53: Register 54: Register 55: Register 56: Register 57: Register 58: Register 59: Register 60: Register 61: Register 62: Register 63: Register 64: Register 65: Register 66: Register 67: Register 68: Register 69:
Interrupt 96-127 Clear Pending (UNPEND3), offset 0x28C ............................................... 144 Interrupt 128-138 Clear Pending (UNPEND4), offset 0x290 .............................................. 145 Interrupt 0-31 Active Bit (ACTIVE0), offset 0x300 ............................................................. 146 Interrupt 32-63 Active Bit (ACTIVE1), offset 0x304 ........................................................... 146 Interrupt 64-95 Active Bit (ACTIVE2), offset 0x308 ........................................................... 146 Interrupt 96-127 Active Bit (ACTIVE3), offset 0x30C ........................................................ 146 Interrupt 128-138 Active Bit (ACTIVE4), offset 0x310 ....................................................... 147 Interrupt 0-3 Priority (PRI0), offset 0x400 ......................................................................... 148 Interrupt 4-7 Priority (PRI1), offset 0x404 ......................................................................... 148 Interrupt 8-11 Priority (PRI2), offset 0x408 ....................................................................... 148 Interrupt 12-15 Priority (PRI3), offset 0x40C .................................................................... 148 Interrupt 16-19 Priority (PRI4), offset 0x410 ..................................................................... 148 Interrupt 20-23 Priority (PRI5), offset 0x414 ..................................................................... 148 Interrupt 24-27 Priority (PRI6), offset 0x418 ..................................................................... 148 Interrupt 28-31 Priority (PRI7), offset 0x41C .................................................................... 148 Interrupt 32-35 Priority (PRI8), offset 0x420 ..................................................................... 148 Interrupt 36-39 Priority (PRI9), offset 0x424 ..................................................................... 148 Interrupt 40-43 Priority (PRI10), offset 0x428 ................................................................... 148 Interrupt 44-47 Priority (PRI11), offset 0x42C ................................................................... 148 Interrupt 48-51 Priority (PRI12), offset 0x430 ................................................................... 148 Interrupt 52-55 Priority (PRI13), offset 0x434 ................................................................... 148 Interrupt 56-59 Priority (PRI14), offset 0x438 ................................................................... 148 Interrupt 60-63 Priority (PRI15), offset 0x43C .................................................................. 148 Interrupt 64-67 Priority (PRI16), offset 0x440 ................................................................... 150 Interrupt 68-71 Priority (PRI17), offset 0x444 ................................................................... 150 Interrupt 72-75 Priority (PRI18), offset 0x448 ................................................................... 150 Interrupt 76-79 Priority (PRI19), offset 0x44C .................................................................. 150 Interrupt 80-83 Priority (PRI20), offset 0x450 ................................................................... 150 Interrupt 84-87 Priority (PRI21), offset 0x454 ................................................................... 150 Interrupt 88-91 Priority (PRI22), offset 0x458 ................................................................... 150 Interrupt 92-95 Priority (PRI23), offset 0x45C .................................................................. 150 Interrupt 96-99 Priority (PRI24), offset 0x460 ................................................................... 150 Interrupt 100-103 Priority (PRI25), offset 0x464 ............................................................... 150 Interrupt 104-107 Priority (PRI26), offset 0x468 ............................................................... 150 Interrupt 108-111 Priority (PRI27), offset 0x46C ............................................................... 150 Interrupt 112-115 Priority (PRI28), offset 0x470 ................................................................ 150 Interrupt 116-119 Priority (PRI29), offset 0x474 ................................................................ 150 Interrupt 120-123 Priority (PRI30), offset 0x478 ............................................................... 150 Interrupt 124-127 Priority (PRI31), offset 0x47C ............................................................... 150 Interrupt 128-131 Priority (PRI32), offset 0x480 ............................................................... 150 Interrupt 132-135 Priority (PRI33), offset 0x484 ............................................................... 150 Interrupt 136-138 Priority (PRI34), offset 0x488 ............................................................... 150 Software Trigger Interrupt (SWTRIG), offset 0xF00 .......................................................... 152 Auxiliary Control (ACTLR), offset 0x008 .......................................................................... 153 CPU ID Base (CPUID), offset 0xD00 ............................................................................... 155 Interrupt Control and State (INTCTRL), offset 0xD04 ........................................................ 156 Vector Table Offset (VTABLE), offset 0xD08 .................................................................... 159 Application Interrupt and Reset Control (APINT), offset 0xD0C ......................................... 160
19
Table of Contents
Register 70: Register 71: Register 72: Register 73: Register 74: Register 75: Register 76: Register 77: Register 78: Register 79: Register 80: Register 81: Register 82: Register 83: Register 84: Register 85: Register 86: Register 87: Register 88: Register 89: Register 90: Register 91: Register 92: Register 93: Register 94: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22:
System Control (SYSCTRL), offset 0xD10 ....................................................................... 162 Configuration and Control (CFGCTRL), offset 0xD14 ....................................................... 164 System Handler Priority 1 (SYSPRI1), offset 0xD18 ......................................................... 166 System Handler Priority 2 (SYSPRI2), offset 0xD1C ........................................................ 167 System Handler Priority 3 (SYSPRI3), offset 0xD20 ......................................................... 168 System Handler Control and State (SYSHNDCTRL), offset 0xD24 .................................... 169 Configurable Fault Status (FAULTSTAT), offset 0xD28 ..................................................... 173 Hard Fault Status (HFAULTSTAT), offset 0xD2C .............................................................. 179 Memory Management Fault Address (MMADDR), offset 0xD34 ........................................ 180 Bus Fault Address (FAULTADDR), offset 0xD38 .............................................................. 181 MPU Type (MPUTYPE), offset 0xD90 ............................................................................. 182 MPU Control (MPUCTRL), offset 0xD94 .......................................................................... 183 MPU Region Number (MPUNUMBER), offset 0xD98 ....................................................... 185 MPU Region Base Address (MPUBASE), offset 0xD9C ................................................... 186 MPU Region Base Address Alias 1 (MPUBASE1), offset 0xDA4 ....................................... 186 MPU Region Base Address Alias 2 (MPUBASE2), offset 0xDAC ...................................... 186 MPU Region Base Address Alias 3 (MPUBASE3), offset 0xDB4 ....................................... 186 MPU Region Attribute and Size (MPUATTR), offset 0xDA0 ............................................... 188 MPU Region Attribute and Size Alias 1 (MPUATTR1), offset 0xDA8 .................................. 188 MPU Region Attribute and Size Alias 2 (MPUATTR2), offset 0xDB0 .................................. 188 MPU Region Attribute and Size Alias 3 (MPUATTR3), offset 0xDB8 .................................. 188 Coprocessor Access Control (CPAC), offset 0xD88 .......................................................... 191 Floating-Point Context Control (FPCC), offset 0xF34 ........................................................ 192 Floating-Point Context Address (FPCA), offset 0xF38 ...................................................... 194 Floating-Point Default Status Control (FPDSC), offset 0xF3C ........................................... 195 Device Identification 0 (DID0), offset 0x000 ..................................................................... 232 Device Identification 1 (DID1), offset 0x004 ..................................................................... 234 Brown-Out Reset Control (PBORCTL), offset 0x030 ........................................................ 236 Raw Interrupt Status (RIS), offset 0x050 .......................................................................... 237 Interrupt Mask Control (IMC), offset 0x054 ...................................................................... 239 Masked Interrupt Status and Clear (MISC), offset 0x058 .................................................. 241 Reset Cause (RESC), offset 0x05C ................................................................................ 243 Run-Mode Clock Configuration (RCC), offset 0x060 ......................................................... 245 GPIO High-Performance Bus Control (GPIOHBCTL), offset 0x06C ................................... 249 Run-Mode Clock Configuration 2 (RCC2), offset 0x070 .................................................... 251 Main Oscillator Control (MOSCCTL), offset 0x07C ........................................................... 254 Deep Sleep Clock Configuration (DSLPCLKCFG), offset 0x144 ........................................ 255 System Properties (SYSPROP), offset 0x14C .................................................................. 257 Precision Internal Oscillator Calibration (PIOSCCAL), offset 0x150 ................................... 258 Precision Internal Oscillator Statistics (PIOSCSTAT), offset 0x154 .................................... 260 PLL Frequency 0 (PLLFREQ0), offset 0x160 ................................................................... 261 PLL Frequency 1 (PLLFREQ1), offset 0x164 ................................................................... 262 PLL Status (PLLSTAT), offset 0x168 ............................................................................... 263 Watchdog Timer Peripheral Present (PPWD), offset 0x300 ............................................... 264 16/32-Bit General-Purpose Timer Peripheral Present (PPTIMER), offset 0x304 ................. 265 General-Purpose Input/Output Peripheral Present (PPGPIO), offset 0x308 ........................ 267 Micro Direct Memory Access Peripheral Present (PPDMA), offset 0x30C .......................... 270
System Control ............................................................................................................................ 208
April 25, 2012
Register 23: Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: Register 31: Register 32: Register 33: Register 34: Register 35: Register 36: Register 37: Register 38: Register 39: Register 40: Register 41: Register 42: Register 43: Register 44: Register 45: Register 46: Register 47: Register 48: Register 49: Register 50: Register 51: Register 52: Register 53: Register 54: Register 55: Register 56: Register 57: Register 58: Register 59: Register 60: Register 61: Register 62: Register 63:
Hibernation Peripheral Present (PPHIB), offset 0x314 ...................................................... 271 Universal Asynchronous Receiver/Transmitter Peripheral Present (PPUART), offset 0x318 ........................................................................................................................... 272 Synchronous Serial Interface Peripheral Present (PPSSI), offset 0x31C ............................ 274 Inter-Integrated Circuit Peripheral Present (PPI2C), offset 0x320 ...................................... 276 Universal Serial Bus Peripheral Present (PPUSB), offset 0x328 ........................................ 278 Controller Area Network Peripheral Present (PPCAN), offset 0x334 .................................. 279 Analog-to-Digital Converter Peripheral Present (PPADC), offset 0x338 ............................. 280 Analog Comparator Peripheral Present (PPACMP), offset 0x33C ...................................... 281 Pulse Width Modulator Peripheral Present (PPPWM), offset 0x340 ................................... 282 Quadrature Encoder Interface Peripheral Present (PPQEI), offset 0x344 ........................... 283 EEPROM Peripheral Present (PPEEPROM), offset 0x358 ................................................ 284 32/64-Bit Wide General-Purpose Timer Peripheral Present (PPWTIMER), offset 0x35C ..... 285 Watchdog Timer Software Reset (SRWD), offset 0x500 ................................................... 287 16/32-Bit General-Purpose Timer Software Reset (SRTIMER), offset 0x504 ...................... 289 General-Purpose Input/Output Software Reset (SRGPIO), offset 0x508 ............................ 291 Micro Direct Memory Access Software Reset (SRDMA), offset 0x50C ............................... 293 Hibernation Software Reset (SRHIB), offset 0x514 ........................................................... 294 Universal Asynchronous Receiver/Transmitter Software Reset (SRUART), offset 0x518 .... 295 Synchronous Serial Interface Software Reset (SRSSI), offset 0x51C ................................ 297 Inter-Integrated Circuit Software Reset (SRI2C), offset 0x520 ........................................... 299 Universal Serial Bus Software Reset (SRUSB), offset 0x528 ............................................ 301 Controller Area Network Software Reset (SRCAN), offset 0x534 ....................................... 302 Analog-to-Digital Converter Software Reset (SRADC), offset 0x538 .................................. 303 Analog Comparator Software Reset (SRACMP), offset 0x53C .......................................... 305 EEPROM Software Reset (SREEPROM), offset 0x558 .................................................... 306 32/64-Bit Wide General-Purpose Timer Software Reset (SRWTIMER), offset 0x55C .......... 307 Watchdog Timer Run Mode Clock Gating Control (RCGCWD), offset 0x600 ...................... 309 16/32-Bit General-Purpose Timer Run Mode Clock Gating Control (RCGCTIMER), offset 0x604 ........................................................................................................................... 310 General-Purpose Input/Output Run Mode Clock Gating Control (RCGCGPIO), offset 0x608 ........................................................................................................................... 312 Micro Direct Memory Access Run Mode Clock Gating Control (RCGCDMA), offset 0x60C ........................................................................................................................... 314 Hibernation Run Mode Clock Gating Control (RCGCHIB), offset 0x614 ............................. 315 Universal Asynchronous Receiver/Transmitter Run Mode Clock Gating Control (RCGCUART), offset 0x618 .................................................................................................................. 316 Synchronous Serial Interface Run Mode Clock Gating Control (RCGCSSI), offset 0x61C ........................................................................................................................... 318 Inter-Integrated Circuit Run Mode Clock Gating Control (RCGCI2C), offset 0x620 ............. 320 Universal Serial Bus Run Mode Clock Gating Control (RCGCUSB), offset 0x628 ............... 322 Controller Area Network Run Mode Clock Gating Control (RCGCCAN), offset 0x634 ......... 323 Analog-to-Digital Converter Run Mode Clock Gating Control (RCGCADC), offset 0x638 .... 324 Analog Comparator Run Mode Clock Gating Control (RCGCACMP), offset 0x63C ............. 325 EEPROM Run Mode Clock Gating Control (RCGCEEPROM), offset 0x658 ....................... 326 32/64-Bit Wide General-Purpose Timer Run Mode Clock Gating Control (RCGCWTIMER), offset 0x65C .................................................................................................................. 327 Watchdog Timer Sleep Mode Clock Gating Control (SCGCWD), offset 0x700 .................... 329
21
Table of Contents
Register 64: Register 65: Register 66: Register 67: Register 68: Register 69: Register 70: Register 71: Register 72: Register 73: Register 74: Register 75: Register 76: Register 77: Register 78: Register 79: Register 80: Register 81: Register 82: Register 83: Register 84: Register 85: Register 86: Register 87: Register 88: Register 89: Register 90: Register 91: Register 92: Register 93: Register 94: Register 95:
16/32-Bit General-Purpose Timer Sleep Mode Clock Gating Control (SCGCTIMER), offset 0x704 ........................................................................................................................... 330 General-Purpose Input/Output Sleep Mode Clock Gating Control (SCGCGPIO), offset 0x708 ........................................................................................................................... 332 Micro Direct Memory Access Sleep Mode Clock Gating Control (SCGCDMA), offset 0x70C ........................................................................................................................... 334 Hibernation Sleep Mode Clock Gating Control (SCGCHIB), offset 0x714 ........................... 335 Universal Asynchronous Receiver/Transmitter Sleep Mode Clock Gating Control (SCGCUART), offset 0x718 ............................................................................................ 336 Synchronous Serial Interface Sleep Mode Clock Gating Control (SCGCSSI), offset 0x71C ........................................................................................................................... 338 Inter-Integrated Circuit Sleep Mode Clock Gating Control (SCGCI2C), offset 0x720 ........... 340 Universal Serial Bus Sleep Mode Clock Gating Control (SCGCUSB), offset 0x728 ............. 342 Controller Area Network Sleep Mode Clock Gating Control (SCGCCAN), offset 0x734 ....... 343 Analog-to-Digital Converter Sleep Mode Clock Gating Control (SCGCADC), offset 0x738 ........................................................................................................................... 344 Analog Comparator Sleep Mode Clock Gating Control (SCGCACMP), offset 0x73C .......... 345 EEPROM Sleep Mode Clock Gating Control (SCGCEEPROM), offset 0x758 ..................... 346 32/64-Bit Wide General-Purpose Timer Sleep Mode Clock Gating Control (SCGCWTIMER), offset 0x75C .................................................................................................................. 347 Watchdog Timer Deep-Sleep Mode Clock Gating Control (DCGCWD), offset 0x800 .......... 349 16/32-Bit General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCTIMER), offset 0x804 .................................................................................................................. 350 General-Purpose Input/Output Deep-Sleep Mode Clock Gating Control (DCGCGPIO), offset 0x808 ........................................................................................................................... 352 Micro Direct Memory Access Deep-Sleep Mode Clock Gating Control (DCGCDMA), offset 0x80C ........................................................................................................................... 354 Hibernation Deep-Sleep Mode Clock Gating Control (DCGCHIB), offset 0x814 .................. 355 Universal Asynchronous Receiver/Transmitter Deep-Sleep Mode Clock Gating Control (DCGCUART), offset 0x818 ............................................................................................ 356 Synchronous Serial Interface Deep-Sleep Mode Clock Gating Control (DCGCSSI), offset 0x81C ........................................................................................................................... 358 Inter-Integrated Circuit Deep-Sleep Mode Clock Gating Control (DCGCI2C), offset 0x820 ........................................................................................................................... 360 Universal Serial Bus Deep-Sleep Mode Clock Gating Control (DCGCUSB), offset 0x828 ........................................................................................................................... 362 Controller Area Network Deep-Sleep Mode Clock Gating Control (DCGCCAN), offset 0x834 ........................................................................................................................... 363 Analog-to-Digital Converter Deep-Sleep Mode Clock Gating Control (DCGCADC), offset 0x838 ........................................................................................................................... 364 Analog Comparator Deep-Sleep Mode Clock Gating Control (DCGCACMP), offset 0x83C ........................................................................................................................... 365 EEPROM Deep-Sleep Mode Clock Gating Control (DCGCEEPROM), offset 0x858 ........... 366 32/64-Bit Wide General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCWTIMER), offset 0x85C ...................................................................................... 367 Watchdog Timer Power Control (PCWD), offset 0x900 ..................................................... 369 16/32-Bit General-Purpose Timer Power Control (PCTIMER), offset 0x904 ....................... 371 General-Purpose Input/Output Power Control (PCGPIO), offset 0x908 .............................. 374 Micro Direct Memory Access Power Control (PCDMA), offset 0x90C ................................ 377 Hibernation Power Control (PCHIB), offset 0x914 ............................................................ 378
April 25, 2012
Register 96: Register 97: Register 98: Register 99: Register 100: Register 101: Register 102: Register 103: Register 104: Register 105: Register 106: Register 107: Register 108: Register 109: Register 110: Register 111: Register 112: Register 113: Register 114: Register 115: Register 116: Register 117: Register 118: Register 119: Register 120: Register 121: Register 122: Register 123: Register 124: Register 125: Register 126: Register 127: Register 128: Register 129: Register 130: Register 131: Register 132: Register 133: Register 134: Register 135: Register 136: Register 137: Register 138: Register 139: Register 140: Register 141:
Universal Asynchronous Receiver/Transmitter Power Control (PCUART), offset 0x918 ...... 379 Synchronous Serial Interface Power Control (PCSSI), offset 0x91C .................................. 383 Inter-Integrated Circuit Power Control (PCI2C), offset 0x920 ............................................ 385 Universal Serial Bus Power Control (PCUSB), offset 0x928 .............................................. 387 Controller Area Network Power Control (PCCAN), offset 0x934 ........................................ 388 Analog-to-Digital Converter Power Control (PCADC), offset 0x938 .................................... 389 Analog Comparator Power Control (PCACMP), offset 0x93C ............................................ 391 EEPROM Power Control (PCEEPROM), offset 0x958 ...................................................... 392 32/64-Bit Wide General-Purpose Timer Power Control (PCWTIMER), offset 0x95C ........... 393 Watchdog Timer Peripheral Ready (PRWD), offset 0xA00 ................................................ 396 16/32-Bit General-Purpose Timer Peripheral Ready (PRTIMER), offset 0xA04 ................... 397 General-Purpose Input/Output Peripheral Ready (PRGPIO), offset 0xA08 ......................... 399 Micro Direct Memory Access Peripheral Ready (PRDMA), offset 0xA0C ........................... 401 Hibernation Peripheral Ready (PRHIB), offset 0xA14 ....................................................... 402 Universal Asynchronous Receiver/Transmitter Peripheral Ready (PRUART), offset 0xA18 ........................................................................................................................... 403 Synchronous Serial Interface Peripheral Ready (PRSSI), offset 0xA1C ............................. 405 Inter-Integrated Circuit Peripheral Ready (PRI2C), offset 0xA20 ....................................... 407 Universal Serial Bus Peripheral Ready (PRUSB), offset 0xA28 ......................................... 409 Controller Area Network Peripheral Ready (PRCAN), offset 0xA34 ................................... 410 Analog-to-Digital Converter Peripheral Ready (PRADC), offset 0xA38 ............................... 411 Analog Comparator Peripheral Ready (PRACMP), offset 0xA3C ....................................... 412 EEPROM Peripheral Ready (PREEPROM), offset 0xA58 ................................................. 413 32/64-Bit Wide General-Purpose Timer Peripheral Ready (PRWTIMER), offset 0xA5C ...... 414 Device Capabilities 0 (DC0), offset 0x008 ........................................................................ 416 Device Capabilities 1 (DC1), offset 0x010 ........................................................................ 418 Device Capabilities 2 (DC2), offset 0x014 ........................................................................ 421 Device Capabilities 3 (DC3), offset 0x018 ........................................................................ 424 Device Capabilities 4 (DC4), offset 0x01C ....................................................................... 428 Device Capabilities 5 (DC5), offset 0x020 ........................................................................ 431 Device Capabilities 6 (DC6), offset 0x024 ........................................................................ 433 Device Capabilities 7 (DC7), offset 0x028 ........................................................................ 434 Device Capabilities 8 (DC8), offset 0x02C ....................................................................... 437 Software Reset Control 0 (SRCR0), offset 0x040 ............................................................. 440 Software Reset Control 1 (SRCR1), offset 0x044 ............................................................. 442 Software Reset Control 2 (SRCR2), offset 0x048 ............................................................. 445 Run Mode Clock Gating Control Register 0 (RCGC0), offset 0x100 ................................... 447 Run Mode Clock Gating Control Register 1 (RCGC1), offset 0x104 ................................... 450 Run Mode Clock Gating Control Register 2 (RCGC2), offset 0x108 ................................... 453 Sleep Mode Clock Gating Control Register 0 (SCGC0), offset 0x110 ................................. 455 Sleep Mode Clock Gating Control Register 1 (SCGC1), offset 0x114 ................................. 457 Sleep Mode Clock Gating Control Register 2 (SCGC2), offset 0x118 ................................. 460 Deep Sleep Mode Clock Gating Control Register 0 (DCGC0), offset 0x120 ....................... 462 Deep-Sleep Mode Clock Gating Control Register 1 (DCGC1), offset 0x124 ....................... 464 Deep Sleep Mode Clock Gating Control Register 2 (DCGC2), offset 0x128 ....................... 467 Device Capabilities 9 (DC9), offset 0x190 ........................................................................ 469 Non-Volatile Memory Information (NVMSTAT), offset 0x1A0 ............................................. 471
23
Table of Contents
System Exception Module .......................................................................................................... 472

Register 1: Register 2: Register 3: Register 4: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 23: Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: System Exception Raw Interrupt Status (SYSEXCRIS), offset 0x000 ................................ System Exception Interrupt Mask (SYSEXCIM), offset 0x004 ........................................... System Exception Masked Interrupt Status (SYSEXCMIS), offset 0x008 ........................... System Exception Interrupt Clear (SYSEXCIC), offset 0x00C ........................................... Hibernation RTC Counter (HIBRTCC), offset 0x000 ......................................................... Hibernation RTC Match 0 (HIBRTCM0), offset 0x004 ....................................................... Hibernation RTC Load (HIBRTCLD), offset 0x00C ........................................................... Hibernation Control (HIBCTL), offset 0x010 ..................................................................... Hibernation Interrupt Mask (HIBIM), offset 0x014 ............................................................. Hibernation Raw Interrupt Status (HIBRIS), offset 0x018 .................................................. Hibernation Masked Interrupt Status (HIBMIS), offset 0x01C ............................................ Hibernation Interrupt Clear (HIBIC), offset 0x020 ............................................................. Hibernation RTC Trim (HIBRTCT), offset 0x024 ............................................................... Hibernation RTC Sub Seconds (HIBRTCSS), offset 0x028 ............................................... Hibernation Data (HIBDATA), offset 0x030-0x06F ............................................................ 473 475 477 479 493 494 495 496 500 502 504 506 507 508 509
Hibernation Module ..................................................................................................................... 480
Internal Memory ........................................................................................................................... 510

Flash Memory Address (FMA), offset 0x000 .................................................................... 526 Flash Memory Data (FMD), offset 0x004 ......................................................................... 527 Flash Memory Control (FMC), offset 0x008 ..................................................................... 528 Flash Controller Raw Interrupt Status (FCRIS), offset 0x00C ............................................ 530 Flash Controller Interrupt Mask (FCIM), offset 0x010 ........................................................ 533 Flash Controller Masked Interrupt Status and Clear (FCMISC), offset 0x014 ..................... 535 Flash Memory Control 2 (FMC2), offset 0x020 ................................................................. 538 Flash Write Buffer Valid (FWBVAL), offset 0x030 ............................................................. 539 Flash Write Buffer n (FWBn), offset 0x100 - 0x17C .......................................................... 540 Flash Size (FSIZE), offset 0xFC0 .................................................................................... 541 SRAM Size (SSIZE), offset 0xFC4 .................................................................................. 542 ROM Software Map (ROMSWMAP), offset 0xFCC ........................................................... 543 EEPROM Size Information (EESIZE), offset 0x000 .......................................................... 544 EEPROM Current Block (EEBLOCK), offset 0x004 .......................................................... 545 EEPROM Current Offset (EEOFFSET), offset 0x008 ........................................................ 546 EEPROM Read-Write (EERDWR), offset 0x010 .............................................................. 547 EEPROM Read-Write with Increment (EERDWRINC), offset 0x014 .................................. 548 EEPROM Done Status (EEDONE), offset 0x018 .............................................................. 549 EEPROM Support Control and Status (EESUPP), offset 0x01C ........................................ 551 EEPROM Unlock (EEUNLOCK), offset 0x020 .................................................................. 553 EEPROM Protection (EEPROT), offset 0x030 ................................................................. 554 EEPROM Password (EEPASS0), offset 0x034 ................................................................. 555 EEPROM Password (EEPASS1), offset 0x038 ................................................................. 555 EEPROM Password (EEPASS2), offset 0x03C ................................................................ 555 EEPROM Interrupt (EEINT), offset 0x040 ........................................................................ 556 EEPROM Block Hide (EEHIDE), offset 0x050 .................................................................. 557 EEPROM Debug Mass Erase (EEDBGME), offset 0x080 ................................................. 558 EEPROM Peripheral Properties (EEPROMPP), offset 0xFC0 ........................................... 559 ROM Control (RMCTL), offset 0x0F0 .............................................................................. 560 Flash Memory Protection Read Enable 0 (FMPRE0), offset 0x130 and 0x200 ................... 561
April 25, 2012
Flash Memory Protection Read Enable 1 (FMPRE1), offset 0x204 .................................... 561 Flash Memory Protection Read Enable 2 (FMPRE2), offset 0x208 .................................... 561 Flash Memory Protection Read Enable 3 (FMPRE3), offset 0x20C ................................... 561 Flash Memory Protection Program Enable 0 (FMPPE0), offset 0x134 and 0x400 ............... 562 Flash Memory Protection Program Enable 1 (FMPPE1), offset 0x404 ............................... 562 Flash Memory Protection Program Enable 2 (FMPPE2), offset 0x408 ............................... 562 Flash Memory Protection Program Enable 3 (FMPPE3), offset 0x40C ............................... 562 Boot Configuration (BOOTCFG), offset 0x1D0 ................................................................. 564 User Register 0 (USER_REG0), offset 0x1E0 .................................................................. 567 User Register 1 (USER_REG1), offset 0x1E4 .................................................................. 567 User Register 2 (USER_REG2), offset 0x1E8 .................................................................. 567 User Register 3 (USER_REG3), offset 0x1EC ................................................................. 567 DMA Channel Source Address End Pointer (DMASRCENDP), offset 0x000 ...................... 592 DMA Channel Destination Address End Pointer (DMADSTENDP), offset 0x004 ................ 593 DMA Channel Control Word (DMACHCTL), offset 0x008 .................................................. 594 DMA Status (DMASTAT), offset 0x000 ............................................................................ 599 DMA Configuration (DMACFG), offset 0x004 ................................................................... 601 DMA Channel Control Base Pointer (DMACTLBASE), offset 0x008 .................................. 602 DMA Alternate Channel Control Base Pointer (DMAALTBASE), offset 0x00C .................... 603 DMA Channel Wait-on-Request Status (DMAWAITSTAT), offset 0x010 ............................. 604 DMA Channel Software Request (DMASWREQ), offset 0x014 ......................................... 605 DMA Channel Useburst Set (DMAUSEBURSTSET), offset 0x018 .................................... 606 DMA Channel Useburst Clear (DMAUSEBURSTCLR), offset 0x01C ................................. 607 DMA Channel Request Mask Set (DMAREQMASKSET), offset 0x020 .............................. 608 DMA Channel Request Mask Clear (DMAREQMASKCLR), offset 0x024 ........................... 609 DMA Channel Enable Set (DMAENASET), offset 0x028 ................................................... 610 DMA Channel Enable Clear (DMAENACLR), offset 0x02C ............................................... 611 DMA Channel Primary Alternate Set (DMAALTSET), offset 0x030 .................................... 612 DMA Channel Primary Alternate Clear (DMAALTCLR), offset 0x034 ................................. 613 DMA Channel Priority Set (DMAPRIOSET), offset 0x038 ................................................. 614 DMA Channel Priority Clear (DMAPRIOCLR), offset 0x03C .............................................. 615 DMA Bus Error Clear (DMAERRCLR), offset 0x04C ........................................................ 616 DMA Channel Assignment (DMACHASGN), offset 0x500 ................................................. 617 DMA Channel Interrupt Status (DMACHIS), offset 0x504 .................................................. 618 DMA Channel Map Select 0 (DMACHMAP0), offset 0x510 ............................................... 619 DMA Channel Map Select 1 (DMACHMAP1), offset 0x514 ............................................... 620 DMA Channel Map Select 2 (DMACHMAP2), offset 0x518 ............................................... 621 DMA Channel Map Select 3 (DMACHMAP3), offset 0x51C .............................................. 622 DMA Peripheral Identification 0 (DMAPeriphID0), offset 0xFE0 ......................................... 623 DMA Peripheral Identification 1 (DMAPeriphID1), offset 0xFE4 ......................................... 624 DMA Peripheral Identification 2 (DMAPeriphID2), offset 0xFE8 ......................................... 625 DMA Peripheral Identification 3 (DMAPeriphID3), offset 0xFEC ........................................ 626 DMA Peripheral Identification 4 (DMAPeriphID4), offset 0xFD0 ......................................... 627 DMA PrimeCell Identification 0 (DMAPCellID0), offset 0xFF0 ........................................... 628 DMA PrimeCell Identification 1 (DMAPCellID1), offset 0xFF4 ........................................... 629 DMA PrimeCell Identification 2 (DMAPCellID2), offset 0xFF8 ........................................... 630 DMA PrimeCell Identification 3 (DMAPCellID3), offset 0xFFC ........................................... 631
Micro Direct Memory Access (DMA) ........................................................................................ 568
25
Table of Contents
General-Purpose Input/Outputs (GPIOs) ................................................................................... 632

Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 23: Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: Register 31: Register 32: Register 33: Register 34: Register 35: Register 36: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: GPIO Data (GPIODATA), offset 0x000 ............................................................................ 644 GPIO Direction (GPIODIR), offset 0x400 ......................................................................... 645 GPIO Interrupt Sense (GPIOIS), offset 0x404 .................................................................. 646 GPIO Interrupt Both Edges (GPIOIBE), offset 0x408 ........................................................ 647 GPIO Interrupt Event (GPIOIEV), offset 0x40C ................................................................ 648 GPIO Interrupt Mask (GPIOIM), offset 0x410 ................................................................... 649 GPIO Raw Interrupt Status (GPIORIS), offset 0x414 ........................................................ 650 GPIO Masked Interrupt Status (GPIOMIS), offset 0x418 ................................................... 651 GPIO Interrupt Clear (GPIOICR), offset 0x41C ................................................................ 652 GPIO Alternate Function Select (GPIOAFSEL), offset 0x420 ............................................ 653 GPIO 2-mA Drive Select (GPIODR2R), offset 0x500 ........................................................ 655 GPIO 4-mA Drive Select (GPIODR4R), offset 0x504 ........................................................ 656 GPIO 8-mA Drive Select (GPIODR8R), offset 0x508 ........................................................ 657 GPIO Open Drain Select (GPIOODR), offset 0x50C ......................................................... 658 GPIO Pull-Up Select (GPIOPUR), offset 0x510 ................................................................ 659 GPIO Pull-Down Select (GPIOPDR), offset 0x514 ........................................................... 661 GPIO Slew Rate Control Select (GPIOSLR), offset 0x518 ................................................ 663 GPIO Digital Enable (GPIODEN), offset 0x51C ................................................................ 664 GPIO Lock (GPIOLOCK), offset 0x520 ............................................................................ 666 GPIO Commit (GPIOCR), offset 0x524 ............................................................................ 667 GPIO Analog Mode Select (GPIOAMSEL), offset 0x528 ................................................... 669 GPIO Port Control (GPIOPCTL), offset 0x52C ................................................................. 670 GPIO ADC Control (GPIOADCCTL), offset 0x530 ............................................................ 672 GPIO DMA Control (GPIODMACTL), offset 0x534 ........................................................... 673 GPIO Peripheral Identification 4 (GPIOPeriphID4), offset 0xFD0 ....................................... 674 GPIO Peripheral Identification 5 (GPIOPeriphID5), offset 0xFD4 ....................................... 675 GPIO Peripheral Identification 6 (GPIOPeriphID6), offset 0xFD8 ....................................... 676 GPIO Peripheral Identification 7 (GPIOPeriphID7), offset 0xFDC ...................................... 677 GPIO Peripheral Identification 0 (GPIOPeriphID0), offset 0xFE0 ....................................... 678 GPIO Peripheral Identification 1 (GPIOPeriphID1), offset 0xFE4 ....................................... 679 GPIO Peripheral Identification 2 (GPIOPeriphID2), offset 0xFE8 ....................................... 680 GPIO Peripheral Identification 3 (GPIOPeriphID3), offset 0xFEC ...................................... 681 GPIO PrimeCell Identification 0 (GPIOPCellID0), offset 0xFF0 .......................................... 682 GPIO PrimeCell Identification 1 (GPIOPCellID1), offset 0xFF4 .......................................... 683 GPIO PrimeCell Identification 2 (GPIOPCellID2), offset 0xFF8 .......................................... 684 GPIO PrimeCell Identification 3 (GPIOPCellID3), offset 0xFFC ......................................... 685 GPTM Configuration (GPTMCFG), offset 0x000 .............................................................. GPTM Timer A Mode (GPTMTAMR), offset 0x004 ........................................................... GPTM Timer B Mode (GPTMTBMR), offset 0x008 ........................................................... GPTM Control (GPTMCTL), offset 0x00C ........................................................................ GPTM Synchronize (GPTMSYNC), offset 0x010 .............................................................. GPTM Interrupt Mask (GPTMIMR), offset 0x018 .............................................................. GPTM Raw Interrupt Status (GPTMRIS), offset 0x01C ..................................................... GPTM Masked Interrupt Status (GPTMMIS), offset 0x020 ................................................ GPTM Interrupt Clear (GPTMICR), offset 0x024 .............................................................. GPTM Timer A Interval Load (GPTMTAILR), offset 0x028 ................................................ 709 711 715 719 723 727 730 733 736 738
General-Purpose Timers ............................................................................................................. 686
April 25, 2012
Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 23: Register 24: Register 25: Register 26: Register 27: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9:
GPTM Timer B Interval Load (GPTMTBILR), offset 0x02C ................................................ 739 GPTM Timer A Match (GPTMTAMATCHR), offset 0x030 .................................................. 740 GPTM Timer B Match (GPTMTBMATCHR), offset 0x034 ................................................. 741 GPTM Timer A Prescale (GPTMTAPR), offset 0x038 ....................................................... 742 GPTM Timer B Prescale (GPTMTBPR), offset 0x03C ...................................................... 743 GPTM TimerA Prescale Match (GPTMTAPMR), offset 0x040 ........................................... 744 GPTM TimerB Prescale Match (GPTMTBPMR), offset 0x044 ........................................... 745 GPTM Timer A (GPTMTAR), offset 0x048 ....................................................................... 746 GPTM Timer B (GPTMTBR), offset 0x04C ....................................................................... 747 GPTM Timer A Value (GPTMTAV), offset 0x050 ............................................................... 748 GPTM Timer B Value (GPTMTBV), offset 0x054 .............................................................. 749 GPTM RTC Predivide (GPTMRTCPD), offset 0x058 ........................................................ 750 GPTM Timer A Prescale Snapshot (GPTMTAPS), offset 0x05C ........................................ 751 GPTM Timer B Prescale Snapshot (GPTMTBPS), offset 0x060 ........................................ 752 GPTM Timer A Prescale Value (GPTMTAPV), offset 0x064 .............................................. 753 GPTM Timer B Prescale Value (GPTMTBPV), offset 0x068 .............................................. 754 GPTM Peripheral Properties (GPTMPP), offset 0xFC0 ..................................................... 755 Watchdog Load (WDTLOAD), offset 0x000 ...................................................................... 760 Watchdog Value (WDTVALUE), offset 0x004 ................................................................... 761 Watchdog Control (WDTCTL), offset 0x008 ..................................................................... 762 Watchdog Interrupt Clear (WDTICR), offset 0x00C .......................................................... 764 Watchdog Raw Interrupt Status (WDTRIS), offset 0x010 .................................................. 765 Watchdog Masked Interrupt Status (WDTMIS), offset 0x014 ............................................. 766 Watchdog Test (WDTTEST), offset 0x418 ....................................................................... 767 Watchdog Lock (WDTLOCK), offset 0xC00 ..................................................................... 768 Watchdog Peripheral Identification 4 (WDTPeriphID4), offset 0xFD0 ................................. 769 Watchdog Peripheral Identification 5 (WDTPeriphID5), offset 0xFD4 ................................. 770 Watchdog Peripheral Identification 6 (WDTPeriphID6), offset 0xFD8 ................................. 771 Watchdog Peripheral Identification 7 (WDTPeriphID7), offset 0xFDC ................................ 772 Watchdog Peripheral Identification 0 (WDTPeriphID0), offset 0xFE0 ................................. 773 Watchdog Peripheral Identification 1 (WDTPeriphID1), offset 0xFE4 ................................. 774 Watchdog Peripheral Identification 2 (WDTPeriphID2), offset 0xFE8 ................................. 775 Watchdog Peripheral Identification 3 (WDTPeriphID3), offset 0xFEC ................................. 776 Watchdog PrimeCell Identification 0 (WDTPCellID0), offset 0xFF0 .................................... 777 Watchdog PrimeCell Identification 1 (WDTPCellID1), offset 0xFF4 .................................... 778 Watchdog PrimeCell Identification 2 (WDTPCellID2), offset 0xFF8 .................................... 779 Watchdog PrimeCell Identification 3 (WDTPCellID3 ), offset 0xFFC .................................. 780 ADC Active Sample Sequencer (ADCACTSS), offset 0x000 ............................................. 802 ADC Raw Interrupt Status (ADCRIS), offset 0x004 ........................................................... 803 ADC Interrupt Mask (ADCIM), offset 0x008 ..................................................................... 805 ADC Interrupt Status and Clear (ADCISC), offset 0x00C .................................................. 807 ADC Overflow Status (ADCOSTAT), offset 0x010 ............................................................ 810 ADC Event Multiplexer Select (ADCEMUX), offset 0x014 ................................................. 812 ADC Underflow Status (ADCUSTAT), offset 0x018 ........................................................... 817 ADC Sample Sequencer Priority (ADCSSPRI), offset 0x020 ............................................. 818 ADC Sample Phase Control (ADCSPC), offset 0x024 ...................................................... 820
Watchdog Timers ......................................................................................................................... 756
Analog-to-Digital Converter (ADC) ............................................................................................. 781
27
Table of Contents
ADC Processor Sample Sequence Initiate (ADCPSSI), offset 0x028 ................................. 822 ADC Sample Averaging Control (ADCSAC), offset 0x030 ................................................. 824 ADC Digital Comparator Interrupt Status and Clear (ADCDCISC), offset 0x034 ................. 825 ADC Sample Sequence Input Multiplexer Select 0 (ADCSSMUX0), offset 0x040 ............... 827 ADC Sample Sequence Control 0 (ADCSSCTL0), offset 0x044 ........................................ 829 ADC Sample Sequence Result FIFO 0 (ADCSSFIFO0), offset 0x048 ................................ 832 ADC Sample Sequence Result FIFO 1 (ADCSSFIFO1), offset 0x068 ................................ 832 ADC Sample Sequence Result FIFO 2 (ADCSSFIFO2), offset 0x088 ................................ 832 ADC Sample Sequence Result FIFO 3 (ADCSSFIFO3), offset 0x0A8 ............................... 832 ADC Sample Sequence FIFO 0 Status (ADCSSFSTAT0), offset 0x04C ............................. 833 ADC Sample Sequence FIFO 1 Status (ADCSSFSTAT1), offset 0x06C ............................. 833 ADC Sample Sequence FIFO 2 Status (ADCSSFSTAT2), offset 0x08C ............................ 833 ADC Sample Sequence FIFO 3 Status (ADCSSFSTAT3), offset 0x0AC ............................ 833 ADC Sample Sequence 0 Operation (ADCSSOP0), offset 0x050 ...................................... 835 ADC Sample Sequence 0 Digital Comparator Select (ADCSSDC0), offset 0x054 .............. 837 ADC Sample Sequence Input Multiplexer Select 1 (ADCSSMUX1), offset 0x060 ............... 839 ADC Sample Sequence Input Multiplexer Select 2 (ADCSSMUX2), offset 0x080 ............... 839 ADC Sample Sequence Control 1 (ADCSSCTL1), offset 0x064 ........................................ 840 ADC Sample Sequence Control 2 (ADCSSCTL2), offset 0x084 ........................................ 840 ADC Sample Sequence 1 Operation (ADCSSOP1), offset 0x070 ...................................... 842 ADC Sample Sequence 2 Operation (ADCSSOP2), offset 0x090 ..................................... 842 ADC Sample Sequence 1 Digital Comparator Select (ADCSSDC1), offset 0x074 .............. 843 ADC Sample Sequence 2 Digital Comparator Select (ADCSSDC2), offset 0x094 .............. 843 ADC Sample Sequence Input Multiplexer Select 3 (ADCSSMUX3), offset 0x0A0 ............... 845 ADC Sample Sequence Control 3 (ADCSSCTL3), offset 0x0A4 ........................................ 846 ADC Sample Sequence 3 Operation (ADCSSOP3), offset 0x0B0 ..................................... 847 ADC Sample Sequence 3 Digital Comparator Select (ADCSSDC3), offset 0x0B4 .............. 848 ADC Digital Comparator Reset Initial Conditions (ADCDCRIC), offset 0xD00 ..................... 849 ADC Digital Comparator Control 0 (ADCDCCTL0), offset 0xE00 ....................................... 854 ADC Digital Comparator Control 1 (ADCDCCTL1), offset 0xE04 ....................................... 854 ADC Digital Comparator Control 2 (ADCDCCTL2), offset 0xE08 ....................................... 854 ADC Digital Comparator Control 3 (ADCDCCTL3), offset 0xE0C ...................................... 854 ADC Digital Comparator Control 4 (ADCDCCTL4), offset 0xE10 ....................................... 854 ADC Digital Comparator Control 5 (ADCDCCTL5), offset 0xE14 ....................................... 854 ADC Digital Comparator Control 6 (ADCDCCTL6), offset 0xE18 ....................................... 854 ADC Digital Comparator Control 7 (ADCDCCTL7), offset 0xE1C ...................................... 854 ADC Digital Comparator Range 0 (ADCDCCMP0), offset 0xE40 ....................................... 856 ADC Digital Comparator Range 1 (ADCDCCMP1), offset 0xE44 ....................................... 856 ADC Digital Comparator Range 2 (ADCDCCMP2), offset 0xE48 ....................................... 856 ADC Digital Comparator Range 3 (ADCDCCMP3), offset 0xE4C ...................................... 856 ADC Digital Comparator Range 4 (ADCDCCMP4), offset 0xE50 ....................................... 856 ADC Digital Comparator Range 5 (ADCDCCMP5), offset 0xE54 ....................................... 856 ADC Digital Comparator Range 6 (ADCDCCMP6), offset 0xE58 ....................................... 856 ADC Digital Comparator Range 7 (ADCDCCMP7), offset 0xE5C ...................................... 856 ADC Peripheral Properties (ADCPP), offset 0xFC0 .......................................................... 857 ADC Peripheral Configuration (ADCPC), offset 0xFC4 ..................................................... 859 ADC Clock Configuration (ADCCC), offset 0xFC8 ............................................................ 860
April 25, 2012
Universal Asynchronous Receivers/Transmitters (UARTs) ..................................................... 861

Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 23: Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: Register 31: Register 32: Register 33: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: UART Data (UARTDR), offset 0x000 ............................................................................... 875 UART Receive Status/Error Clear (UARTRSR/UARTECR), offset 0x004 ........................... 877 UART Flag (UARTFR), offset 0x018 ................................................................................ 880 UART IrDA Low-Power Register (UARTILPR), offset 0x020 ............................................. 882 UART Integer Baud-Rate Divisor (UARTIBRD), offset 0x024 ............................................ 883 UART Fractional Baud-Rate Divisor (UARTFBRD), offset 0x028 ....................................... 884 UART Line Control (UARTLCRH), offset 0x02C ............................................................... 885 UART Control (UARTCTL), offset 0x030 ......................................................................... 887 UART Interrupt FIFO Level Select (UARTIFLS), offset 0x034 ........................................... 891 UART Interrupt Mask (UARTIM), offset 0x038 ................................................................. 893 UART Raw Interrupt Status (UARTRIS), offset 0x03C ...................................................... 896 UART Masked Interrupt Status (UARTMIS), offset 0x040 ................................................. 899 UART Interrupt Clear (UARTICR), offset 0x044 ............................................................... 902 UART DMA Control (UARTDMACTL), offset 0x048 .......................................................... 904 UART LIN Control (UARTLCTL), offset 0x090 ................................................................. 905 UART LIN Snap Shot (UARTLSS), offset 0x094 ............................................................... 906 UART LIN Timer (UARTLTIM), offset 0x098 ..................................................................... 907 UART 9-Bit Self Address (UART9BITADDR), offset 0x0A4 ............................................... 908 UART 9-Bit Self Address Mask (UART9BITAMASK), offset 0x0A8 .................................... 909 UART Peripheral Properties (UARTPP), offset 0xFC0 ...................................................... 910 UART Clock Configuration (UARTCC), offset 0xFC8 ........................................................ 911 UART Peripheral Identification 4 (UARTPeriphID4), offset 0xFD0 ..................................... 912 UART Peripheral Identification 5 (UARTPeriphID5), offset 0xFD4 ..................................... 913 UART Peripheral Identification 6 (UARTPeriphID6), offset 0xFD8 ..................................... 914 UART Peripheral Identification 7 (UARTPeriphID7), offset 0xFDC ..................................... 915 UART Peripheral Identification 0 (UARTPeriphID0), offset 0xFE0 ...................................... 916 UART Peripheral Identification 1 (UARTPeriphID1), offset 0xFE4 ...................................... 917 UART Peripheral Identification 2 (UARTPeriphID2), offset 0xFE8 ...................................... 918 UART Peripheral Identification 3 (UARTPeriphID3), offset 0xFEC ..................................... 919 UART PrimeCell Identification 0 (UARTPCellID0), offset 0xFF0 ........................................ 920 UART PrimeCell Identification 1 (UARTPCellID1), offset 0xFF4 ........................................ 921 UART PrimeCell Identification 2 (UARTPCellID2), offset 0xFF8 ........................................ 922 UART PrimeCell Identification 3 (UARTPCellID3), offset 0xFFC ........................................ 923 SSI Control 0 (SSICR0), offset 0x000 .............................................................................. 939 SSI Control 1 (SSICR1), offset 0x004 .............................................................................. 941 SSI Data (SSIDR), offset 0x008 ...................................................................................... 943 SSI Status (SSISR), offset 0x00C ................................................................................... 944 SSI Clock Prescale (SSICPSR), offset 0x010 .................................................................. 946 SSI Interrupt Mask (SSIIM), offset 0x014 ......................................................................... 947 SSI Raw Interrupt Status (SSIRIS), offset 0x018 .............................................................. 948 SSI Masked Interrupt Status (SSIMIS), offset 0x01C ........................................................ 950 SSI Interrupt Clear (SSIICR), offset 0x020 ....................................................................... 952 SSI DMA Control (SSIDMACTL), offset 0x024 ................................................................. 953 SSI Clock Configuration (SSICC), offset 0xFC8 ............................................................... 954 SSI Peripheral Identification 4 (SSIPeriphID4), offset 0xFD0 ............................................. 955 SSI Peripheral Identification 5 (SSIPeriphID5), offset 0xFD4 ............................................. 956
Synchronous Serial Interface (SSI) ............................................................................................ 924
29
Table of Contents
Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 23: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13: Register 14: Register 15: Register 16: Register 17: Register 18: Register 19: Register 20: Register 21: Register 22: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9: Register 10: Register 11: Register 12: Register 13:
SSI Peripheral Identification 6 (SSIPeriphID6), offset 0xFD8 ............................................. SSI Peripheral Identification 7 (SSIPeriphID7), offset 0xFDC ............................................ SSI Peripheral Identification 0 (SSIPeriphID0), offset 0xFE0 ............................................. SSI Peripheral Identification 1 (SSIPeriphID1), offset 0xFE4 ............................................. SSI Peripheral Identification 2 (SSIPeriphID2), offset 0xFE8 ............................................. SSI Peripheral Identification 3 (SSIPeriphID3), offset 0xFEC ............................................ SSI PrimeCell Identification 0 (SSIPCellID0), offset 0xFF0 ............................................... SSI PrimeCell Identification 1 (SSIPCellID1), offset 0xFF4 ............................................... SSI PrimeCell Identification 2 (SSIPCellID2), offset 0xFF8 ............................................... SSI PrimeCell Identification 3 (SSIPCellID3), offset 0xFFC ...............................................
957 958 959 960 961 962 963 964 965 966
Inter-Integrated Circuit (I2C) Interface ........................................................................................ 967

I2C Master Slave Address (I2CMSA), offset 0x000 ........................................................... 987 I2C Master Control/Status (I2CMCS), offset 0x004 ........................................................... 988 I2C Master Data (I2CMDR), offset 0x008 ......................................................................... 993 I2C Master Timer Period (I2CMTPR), offset 0x00C ........................................................... 994 I2C Master Interrupt Mask (I2CMIMR), offset 0x010 ......................................................... 995 I2C Master Raw Interrupt Status (I2CMRIS), offset 0x014 ................................................. 996 I2C Master Masked Interrupt Status (I2CMMIS), offset 0x018 ........................................... 997 I2C Master Interrupt Clear (I2CMICR), offset 0x01C ......................................................... 998 I2C Master Configuration (I2CMCR), offset 0x020 ............................................................ 999 I2C Master Clock Low Timeout Count (I2CMCLKOCNT), offset 0x024 ............................. 1000 I2C Master Bus Monitor (I2CMBMON), offset 0x02C ....................................................... 1001 I2C Slave Own Address (I2CSOAR), offset 0x800 .......................................................... 1002 I2C Slave Control/Status (I2CSCSR), offset 0x804 ......................................................... 1003 I2C Slave Data (I2CSDR), offset 0x808 ......................................................................... 1005 I2C Slave Interrupt Mask (I2CSIMR), offset 0x80C ......................................................... 1006 I2C Slave Raw Interrupt Status (I2CSRIS), offset 0x810 ................................................. 1007 I2C Slave Masked Interrupt Status (I2CSMIS), offset 0x814 ............................................ 1008 I2C Slave Interrupt Clear (I2CSICR), offset 0x818 .......................................................... 1009 I2C Slave Own Address 2 (I2CSOAR2), offset 0x81C ..................................................... 1010 I2C Slave ACK Control (I2CSACKCTL), offset 0x820 ...................................................... 1011 I2C Peripheral Properties (I2CPP), offset 0xFC0 ............................................................ 1012 I2C Peripheral Configuration (I2CPC), offset 0xFC4 ....................................................... 1013 CAN Control (CANCTL), offset 0x000 ............................................................................ 1035 CAN Status (CANSTS), offset 0x004 ............................................................................. 1037 CAN Error Counter (CANERR), offset 0x008 ................................................................. 1040 CAN Bit Timing (CANBIT), offset 0x00C ........................................................................ 1041 CAN Interrupt (CANINT), offset 0x010 ........................................................................... 1042 CAN Test (CANTST), offset 0x014 ................................................................................ 1043 CAN Baud Rate Prescaler Extension (CANBRPE), offset 0x018 ..................................... 1045 CAN IF1 Command Request (CANIF1CRQ), offset 0x020 .............................................. 1046 CAN IF2 Command Request (CANIF2CRQ), offset 0x080 .............................................. 1046 CAN IF1 Command Mask (CANIF1CMSK), offset 0x024 ................................................ 1047 CAN IF2 Command Mask (CANIF2CMSK), offset 0x084 ................................................ 1047 CAN IF1 Mask 1 (CANIF1MSK1), offset 0x028 .............................................................. 1050 CAN IF2 Mask 1 (CANIF2MSK1), offset 0x088 .............................................................. 1050
Controller Area Network (CAN) Module ................................................................................... 1014
April 25, 2012
CAN IF1 Mask 2 (CANIF1MSK2), offset 0x02C .............................................................. 1051 CAN IF2 Mask 2 (CANIF2MSK2), offset 0x08C .............................................................. 1051 CAN IF1 Arbitration 1 (CANIF1ARB1), offset 0x030 ....................................................... 1053 CAN IF2 Arbitration 1 (CANIF2ARB1), offset 0x090 ....................................................... 1053 CAN IF1 Arbitration 2 (CANIF1ARB2), offset 0x034 ....................................................... 1054 CAN IF2 Arbitration 2 (CANIF2ARB2), offset 0x094 ....................................................... 1054 CAN IF1 Message Control (CANIF1MCTL), offset 0x038 ................................................ 1056 CAN IF2 Message Control (CANIF2MCTL), offset 0x098 ................................................ 1056 CAN IF1 Data A1 (CANIF1DA1), offset 0x03C ............................................................... 1059 CAN IF1 Data A2 (CANIF1DA2), offset 0x040 ................................................................ 1059 CAN IF1 Data B1 (CANIF1DB1), offset 0x044 ................................................................ 1059 CAN IF1 Data B2 (CANIF1DB2), offset 0x048 ................................................................ 1059 CAN IF2 Data A1 (CANIF2DA1), offset 0x09C ............................................................... 1059 CAN IF2 Data A2 (CANIF2DA2), offset 0x0A0 ............................................................... 1059 CAN IF2 Data B1 (CANIF2DB1), offset 0x0A4 ............................................................... 1059 CAN IF2 Data B2 (CANIF2DB2), offset 0x0A8 ............................................................... 1059 CAN Transmission Request 1 (CANTXRQ1), offset 0x100 .............................................. 1060 CAN Transmission Request 2 (CANTXRQ2), offset 0x104 .............................................. 1060 CAN New Data 1 (CANNWDA1), offset 0x120 ............................................................... 1061 CAN New Data 2 (CANNWDA2), offset 0x124 ............................................................... 1061 CAN Message 1 Interrupt Pending (CANMSG1INT), offset 0x140 ................................... 1062 CAN Message 2 Interrupt Pending (CANMSG2INT), offset 0x144 ................................... 1062 CAN Message 1 Valid (CANMSG1VAL), offset 0x160 ..................................................... 1063 CAN Message 2 Valid (CANMSG2VAL), offset 0x164 ..................................................... 1063 USB Device Functional Address (USBFADDR), offset 0x000 .......................................... 1076 USB Power (USBPOWER), offset 0x001 ....................................................................... 1077 USB Transmit Interrupt Status (USBTXIS), offset 0x002 ................................................. 1079 USB Receive Interrupt Status (USBRXIS), offset 0x004 ................................................. 1081 USB Transmit Interrupt Enable (USBTXIE), offset 0x006 ................................................ 1082 USB Receive Interrupt Enable (USBRXIE), offset 0x008 ................................................. 1084 USB General Interrupt Status (USBIS), offset 0x00A ...................................................... 1085 USB Interrupt Enable (USBIE), offset 0x00B .................................................................. 1086 USB Frame Value (USBFRAME), offset 0x00C .............................................................. 1088 USB Endpoint Index (USBEPIDX), offset 0x00E ............................................................ 1089 USB Test Mode (USBTEST), offset 0x00F ..................................................................... 1090 USB FIFO Endpoint 0 (USBFIFO0), offset 0x020 ........................................................... 1091 USB FIFO Endpoint 1 (USBFIFO1), offset 0x024 ........................................................... 1091 USB FIFO Endpoint 2 (USBFIFO2), offset 0x028 ........................................................... 1091 USB FIFO Endpoint 3 (USBFIFO3), offset 0x02C ........................................................... 1091 USB FIFO Endpoint 4 (USBFIFO4), offset 0x030 ........................................................... 1091 USB FIFO Endpoint 5 (USBFIFO5), offset 0x034 ........................................................... 1091 USB FIFO Endpoint 6 (USBFIFO6), offset 0x038 ........................................................... 1091 USB FIFO Endpoint 7 (USBFIFO7), offset 0x03C ........................................................... 1091 USB Transmit Dynamic FIFO Sizing (USBTXFIFOSZ), offset 0x062 ................................ 1092 USB Receive Dynamic FIFO Sizing (USBRXFIFOSZ), offset 0x063 ................................ 1092 USB Transmit FIFO Start Address (USBTXFIFOADD), offset 0x064 ................................ 1093 USB Receive FIFO Start Address (USBRXFIFOADD), offset 0x066 ................................ 1093
Universal Serial Bus (USB) Controller ..................................................................................... 1064
31
Table of Contents
Register 24: Register 25: Register 26: Register 27: Register 28: Register 29: Register 30: Register 31: Register 32: Register 33: Register 34: Register 35: Register 36: Register 37: Register 38: Register 39: Register 40: Register 41: Register 42: Register 43: Register 44: Register 45: Register 46: Register 47: Register 48: Register 49: Register 50: Register 51: Register 52: Register 53: Register 54: Register 55: Register 56: Register 57: Register 58: Register 59: Register 60: Register 61: Register 62: Register 63: Register 64: Register 65: Register 66: Register 67: Register 68: Register 69: Register 70: Register 71:
USB Connect Timing (USBCONTIM), offset 0x07A ........................................................ 1094 USB Full-Speed Last Transaction to End of Frame Timing (USBFSEOF), offset 0x07D .... 1095 USB Low-Speed Last Transaction to End of Frame Timing (USBLSEOF), offset 0x07E .... 1096 USB Maximum Transmit Data Endpoint 1 (USBTXMAXP1), offset 0x110 ......................... 1097 USB Maximum Transmit Data Endpoint 2 (USBTXMAXP2), offset 0x120 ........................ 1097 USB Maximum Transmit Data Endpoint 3 (USBTXMAXP3), offset 0x130 ........................ 1097 USB Maximum Transmit Data Endpoint 4 (USBTXMAXP4), offset 0x140 ........................ 1097 USB Maximum Transmit Data Endpoint 5 (USBTXMAXP5), offset 0x150 ........................ 1097 USB Maximum Transmit Data Endpoint 6 (USBTXMAXP6), offset 0x160 ........................ 1097 USB Maximum Transmit Data Endpoint 7 (USBTXMAXP7), offset 0x170 ........................ 1097 USB Control and Status Endpoint 0 Low (USBCSRL0), offset 0x102 ............................... 1098 USB Control and Status Endpoint 0 High (USBCSRH0), offset 0x103 ............................. 1100 USB Receive Byte Count Endpoint 0 (USBCOUNT0), offset 0x108 ................................. 1101 USB Transmit Control and Status Endpoint 1 Low (USBTXCSRL1), offset 0x112 ............. 1102 USB Transmit Control and Status Endpoint 2 Low (USBTXCSRL2), offset 0x122 ............. 1102 USB Transmit Control and Status Endpoint 3 Low (USBTXCSRL3), offset 0x132 ............. 1102 USB Transmit Control and Status Endpoint 4 Low (USBTXCSRL4), offset 0x142 ............. 1102 USB Transmit Control and Status Endpoint 5 Low (USBTXCSRL5), offset 0x152 ............. 1102 USB Transmit Control and Status Endpoint 6 Low (USBTXCSRL6), offset 0x162 ............. 1102 USB Transmit Control and Status Endpoint 7 Low (USBTXCSRL7), offset 0x172 ............. 1102 USB Transmit Control and Status Endpoint 1 High (USBTXCSRH1), offset 0x113 ............ 1104 USB Transmit Control and Status Endpoint 2 High (USBTXCSRH2), offset 0x123 ........... 1104 USB Transmit Control and Status Endpoint 3 High (USBTXCSRH3), offset 0x133 ........... 1104 USB Transmit Control and Status Endpoint 4 High (USBTXCSRH4), offset 0x143 ........... 1104 USB Transmit Control and Status Endpoint 5 High (USBTXCSRH5), offset 0x153 ........... 1104 USB Transmit Control and Status Endpoint 6 High (USBTXCSRH6), offset 0x163 ........... 1104 USB Transmit Control and Status Endpoint 7 High (USBTXCSRH7), offset 0x173 ........... 1104 USB Maximum Receive Data Endpoint 1 (USBRXMAXP1), offset 0x114 ......................... 1106 USB Maximum Receive Data Endpoint 2 (USBRXMAXP2), offset 0x124 ......................... 1106 USB Maximum Receive Data Endpoint 3 (USBRXMAXP3), offset 0x134 ......................... 1106 USB Maximum Receive Data Endpoint 4 (USBRXMAXP4), offset 0x144 ......................... 1106 USB Maximum Receive Data Endpoint 5 (USBRXMAXP5), offset 0x154 ......................... 1106 USB Maximum Receive Data Endpoint 6 (USBRXMAXP6), offset 0x164 ......................... 1106 USB Maximum Receive Data Endpoint 7 (USBRXMAXP7), offset 0x174 ......................... 1106 USB Receive Control and Status Endpoint 1 Low (USBRXCSRL1), offset 0x116 ............. 1107 USB Receive Control and Status Endpoint 2 Low (USBRXCSRL2), offset 0x126 ............. 1107 USB Receive Control and Status Endpoint 3 Low (USBRXCSRL3), offset 0x136 ............. 1107 USB Receive Control and Status Endpoint 4 Low (USBRXCSRL4), offset 0x146 ............. 1107 USB Receive Control and Status Endpoint 5 Low (USBRXCSRL5), offset 0x156 ............. 1107 USB Receive Control and Status Endpoint 6 Low (USBRXCSRL6), offset 0x166 ............. 1107 USB Receive Control and Status Endpoint 7 Low (USBRXCSRL7), offset 0x176 ............. 1107 USB Receive Control and Status Endpoint 1 High (USBRXCSRH1), offset 0x117 ............ 1110 USB Receive Control and Status Endpoint 2 High (USBRXCSRH2), offset 0x127 ............ 1110 USB Receive Control and Status Endpoint 3 High (USBRXCSRH3), offset 0x137 ............ 1110 USB Receive Control and Status Endpoint 4 High (USBRXCSRH4), offset 0x147 ............ 1110 USB Receive Control and Status Endpoint 5 High (USBRXCSRH5), offset 0x157 ............ 1110 USB Receive Control and Status Endpoint 6 High (USBRXCSRH6), offset 0x167 ............ 1110 USB Receive Control and Status Endpoint 7 High (USBRXCSRH7), offset 0x177 ............ 1110
April 25, 2012
Register 72: Register 73: Register 74: Register 75: Register 76: Register 77: Register 78: Register 79: Register 80: Register 81: Register 82: Register 83: Register 84: Register 85: Register 1: Register 2: Register 3: Register 4: Register 5: Register 6: Register 7: Register 8: Register 9:
USB Receive Byte Count Endpoint 1 (USBRXCOUNT1), offset 0x118 ............................. 1112 USB Receive Byte Count Endpoint 2 (USBRXCOUNT2), offset 0x128 ............................ 1112 USB Receive Byte Count Endpoint 3 (USBRXCOUNT3), offset 0x138 ............................ 1112 USB Receive Byte Count Endpoint 4 (USBRXCOUNT4), offset 0x148 ............................ 1112 USB Receive Byte Count Endpoint 5 (USBRXCOUNT5), offset 0x158 ............................ 1112 USB Receive Byte Count Endpoint 6 (USBRXCOUNT6), offset 0x168 ............................ 1112 USB Receive Byte Count Endpoint 7 (USBRXCOUNT7), offset 0x178 ............................ 1112 USB Receive Double Packet Buffer Disable (USBRXDPKTBUFDIS), offset 0x340 ........... 1113 USB Transmit Double Packet Buffer Disable (USBTXDPKTBUFDIS), offset 0x342 .......... 1114 USB Device RESUME Raw Interrupt Status (USBDRRIS), offset 0x410 .......................... 1115 USB Device RESUME Interrupt Mask (USBDRIM), offset 0x414 ..................................... 1116 USB Device RESUME Interrupt Status and Clear (USBDRISC), offset 0x418 .................. 1117 USB DMA Select (USBDMASEL), offset 0x450 .............................................................. 1118 USB Peripheral Properties (USBPP), offset 0xFC0 ........................................................ 1120 Analog Comparator Masked Interrupt Status (ACMIS), offset 0x000 ................................ 1128 Analog Comparator Raw Interrupt Status (ACRIS), offset 0x004 ..................................... 1129 Analog Comparator Interrupt Enable (ACINTEN), offset 0x008 ....................................... 1130 Analog Comparator Reference Voltage Control (ACREFCTL), offset 0x010 ..................... 1131 Analog Comparator Status 0 (ACSTAT0), offset 0x020 ................................................... 1132 Analog Comparator Status 1 (ACSTAT1), offset 0x040 ................................................... 1132 Analog Comparator Control 0 (ACCTL0), offset 0x024 ................................................... 1133 Analog Comparator Control 1 (ACCTL1), offset 0x044 ................................................... 1133 Analog Comparator Peripheral Properties (ACMPPP), offset 0xFC0 ................................ 1135
Analog Comparators ................................................................................................................. 1121
33
Revision History
Revision History
The revision history table notes changes made between the indicated revisions of the LM4F120H5QR data sheet. Table 1. Revision History
Date April 2012 Revision Description Document revision number is now auto-generated and indicates the revision of the source files. In the JTAG chapter, clarified that the "Recovering a Locked Microcontroller" procedure erases EEPROM and returns its wear-leveling counters to factory default values. In the Hibernation Module chapter, corrected the reset value of the Hibernation RTC Sub Seconds (HIBRTCSS) register. In the System Control chapter, reorganized registers to group legacy registers at the end of the chapter. In the uDMA chapter, in the "DMA Channel Assignments" and "Request Type Support" tables, corrected to show uDMA support for burst requests from the general-purpose timer, not single requests. In the SSI chapter, added the SLBY6 bit to the SSI Control 1 (SSICR1) register. This allows the system clock to operate at least 6 times faster (overriding 12 times faster normally) than SSICLK. In the I2C chapter, clarified description of Quick Command. In the Operating Characteristics chapter, deleted the Maximum power dissipation parameter from the "Thermal Characteristics" table. In the Electrical Characteristics chapter: Removed pending characterization notes in a number of tables where data has been reviewed. In the Power Characteristics table, adjusted the minimum, nominal, and maximum values for POR and BOR thresholds. In the Main Oscillator Input Characteristics table, adjusted the maximum value for the main oscillator startup time. In the HIB Oscillator Input Characteristics table, added Max value for Oscillator startup time and changed Min and Max values for External clock reference duty cycle. Added Crystal Parameters table. In the Hibernation Module Battery Characteristics table, adjusted the values for low battery detect voltage. In the Flash Memory Characteristics table, adjusted the maximum values for TPROG64 and TERASE. In the GPIO Module Characteristics table, adjusted the values for the GPIO rise and fall times. In the ADC Electrical Characteristics table, updated Max value for the ADC input common mode voltage parameter, and adjusted system performance parameter values. In the SSI Characteristics table, adjusted values for SSIClk rise and fall times. In Preliminary Current Consumption table, updated Nom value for Deep-sleep mode parameter. 12454.2480
March 2012 12013
Additional minor data sheet clarifications and corrections. In Cortex-M4 Peripherals chapter:
April 25, 2012
Table 1. Revision History (continued)

Date Revision Description Corrected missing bits in Interrupt 128-138 Set Enable (EN4), Interrupt 128-138 Clear Enable (DIS4), Interrupt 128-138 Set Pending (PEND4), Interrupt 128-138 Clear Pending (UNPEND4), and Interrupt 128-138 Active Bit (ACTIVE4) registers. Added missing Interrupt 132-135 Priority (PRI33) and Interrupt 136-138 Priority (PRI34) registers.
In the System Control chapter, Corrected Power Architecture figure. Added note that the configuration of the system clock must not be changed while an EEPROM operation is in process. Corrected to 1 the reset for bit 27 in the Device Identification 0 (DID0) register. Clarified the Software Reset (SRx), Run Mode Clock Gating Control (RCGCx), Sleep Mode Clock Gating Control (SCGCx), Deep-Sleep Mode Clock Gating Control (DCGCx), Power Control (PCx) and Peripheral Ready (PRx) registers by removing those bits without meaning because that feature is not present. Conversely, the Peripheral Present (PPx) registers show bit fields available for all devices in this family, with a 0 indicating the feature is not present.
In the Hibernation chapter: Corrected Hibernation Module block diagram. Clarified the implementation for VDD3ON mode. Removed LOWBATEN bit from the Hibernation Control (HIBCTL) register.
In the Timer chapter, noted that if PWM output inversion is enabled, edge detection interrupt behavior is reversed. In the Watchdog Timers chapter, added information on servicing the watchdog timer to the Initialization and Configuration section. In the ADC chapter: Corrected figure "ADC Input Equivalency Diagram". Changed the voltage reference internal signal names to VREFP and VREFN. Clarified "Differential Sampling" section. Corrected figure "Internal Temperature Sensor Characteristic". Corrected PSn bit field locations in ADC Trigger Source Select (ADCTSSEL) register. Corrected resets for ADC Control (ADCCTL) and ADC Sample Sequence Control 3 (ADCSSCTL3) registers.
In the UART chapter: Added note to UART LIN Timer (UARTLTIM) register that if the PIOSC is being used as the UART baud clock, the value in this register should be read twice to ensure the data is correct. Removed RANGE bit from the UART 9-Bit Self Address Mask (UART9BITAMASK) register. Corrected CS bit field values in the UART Clock Configuration (UARTCC) register.
In the SSI chapter: Clarified the steps in the initialization and configuration section.
35
Revision History

Date Revision Description Corrected CS bit field values in the SSI Clock Configuration (SSICC) register.
In the I2C chapter: Clarified the operation of the clock low timeout. Added information about high-speed operation and Fast Plus mode. Corrected reset for I2C Master Bus Monitor (I2CMBMON) register.
In the USB chapter, corrected reset for ECNT bit in USB Peripheral Properties (USBPP) register. In the Analog Comparators chapter: Rewrote Internal Reference Programming section. Corrected bit description for RNG in the Analog Comparator Reference Voltage Control (ACREFCTL) register.
In the Signal Tables chapter, deleted erroneously included LPC signals. In the Electrical Characteristics chapter: Clarified GPIO pad operation and specifications, including ESD protection, VOH, VOL, input hysteresis, input leakage, and injection current. Corrected Nom value for TCK clock Low and High time. Clarified reset timing when in Deep-sleep mode. Corrected frequency range for the internal 30-kHz oscillator. Clarified VIH, VIL, and input hysteresis for the Hibernation oscillator inputs. Changed unit values for TWAKE_TO_HIB from microseconds to hibernate clocks in table "Hibernation Module AC Characteristics". Added values to the table "GPIO Module Characteristics". Added specifications for the ADC when using the internal reference. Added specification for ADC input common mode voltage when in differential mode. Added specification for current consumption on VDDA.
November 2011 11003
Additional minor data sheet clarifications and corrections. Re-organized Architectural Overview chapter. In the System Control chapter: Corrected reset value for Run Mode Clock Gating Control Register 0 (RCGC0) register. Corrected reset for the System Properties (SYSPROP) register. Removed TPSW bit from Non-Volatile Memory Information (NVMSTAT) register as the ROM Software Map (ROMSWMAP) register contains this information. Changed bit names in System Exception Raw Interrupt Status (SYSEXCRIS), System Exception Interrupt Mask (SYSEXCIM), System Exception Masked Interrupt Status (SYSEXCMIS), and System Exception Interrupt Clear (SYSEXCIC) registers to indicate they are for floating-point exceptions. Removed references to RTCCLK as it is not supported on this device. In Hibernation chapter, added section "Arbitrary Power Removal" and corrected figure "Using a Dedicated Oscillator as the Hibernation Clock Source with VDD3ON Mode ".
April 25, 2012

Date Revision Description In the Internal Memory chapter, clarified programming and use of the non-volatile registers, including corrections to the Boot Configuration (BOOTCFG) and User Register n (USER_REGn) registers. In the GPIO chapter, corrected table "GPIO Pins With Non-Zero Reset Values". In the General-Purpose Timers chapter, added clarifications on timer operation. In the UART chapter, clarified interrupt behavior. In the I2C chapter: Added content for Fast-Mode Plus (1 Mbps) mode and High-Speed mode (3.33 Mbps), correcting the reset value of the Device Capabilities 2 (DC2), I2C Master Control/Status (I2CMCS), and I2C Peripheral Properties (I2CPP) registers. Corrected reset for the I2C Master Control/Status (I2CMCS) register. Added the HSTPR bit to the I2C Master Timer Period (I2CMTPR) register. Added the I2C Peripheral Configuration (I2CPC) register. In the USB chapter: Corrected description for the USB Device RESUME Interrupt Mask (USBDRIM) register. Removed DISCON bit from USB General Interrupt Status (USBIS) register, as it is only used for USB OTG.
In the Analog Comparators chapter: Corrected table "Internal Reference Voltage and ACREFCTL Field Values". Corrected bit fields in the Analog Comparator Peripheral Properties (ACMPPP) register.
In the Electrical Characteristics chapter: Clarified load capacitance equations. Corrected values in table "Analog Comparator Voltage Reference Characteristics". Additional minor data sheet clarifications and corrections.
September 2011 10502
Started tracking revision history.
37
About This Document
About This Document

This data sheet provides reference information for the LM4F120H5QR microcontroller, describing the functional blocks of the system-on-chip (SoC) device designed around the ARM Cortex-M4F core.
Audience
This manual is intended for system software developers, hardware designers, and application developers.
About This Manual

This document is organized into sections that correspond to each major feature.
Related Documents
The following related documents are available on the Stellaris web site at www.ti.com/stellaris: Stellaris Errata ARM Cortex-M4 Errata Cortex-M3/M4 Instruction Set Technical User's Manual Stellaris Boot Loader User's Guide Stellaris Graphics Library User's Guide Stellaris Peripheral Driver Library User's Guide Stellaris ROM Users Guide Stellaris USB Library User's Guide The following related documents are also referenced: ARM Debug Interface V5 Architecture Specification ARM Embedded Trace Macrocell Architecture Specification IEEE Standard 1149.1-Test Access Port and Boundary-Scan Architecture This documentation list was current as of publication date. Please check the web site for additional documentation, including application notes and white papers.
April 25, 2012
Documentation Conventions
This document uses the conventions shown in Table 2 on page 39. Table 2. Documentation Conventions
Notation Meaning General Register Notation REGISTER APB registers are indicated in uppercase bold. For example, PBORCTL is the Power-On and Brown-Out Reset Control register. If a register name contains a lowercase n, it represents more than one register. For example, SRCRn represents any (or all) of the three Software Reset Control registers: SRCR0, SRCR1 , and SRCR2. A single bit in a register. Two or more consecutive and related bits. A hexadecimal increment to a register's address, relative to that module's base address as specified in Table 2-4 on page 88. Registers are numbered consecutively throughout the document to aid in referencing them. The register number has no meaning to software. Register bits marked reserved are reserved for future use. In most cases, reserved bits are set to 0; however, user software should not rely on the value of a reserved bit. To provide software compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. The range of register bits inclusive from xx to yy. For example, 31:15 means bits 15 through 31 in that register. This value in the register bit diagram indicates whether software running on the controller can change the value of the bit field. Software can read this field. The bit or field is cleared by hardware after reading the bit/field. Software can read this field. Always write the chip reset value. Software can read or write this field. Software can read or write this field. Writing to it with any value clears the register. Software can read or write this field. A write of a 0 to a W1C bit does not affect the bit value in the register. A write of a 1 clears the value of the bit in the register; the remaining bits remain unchanged. This register type is primarily used for clearing interrupt status bits where the read operation provides the interrupt status and the write of the read value clears only the interrupts being reported at the time the register was read. R/W1S W1C Software can read or write a 1 to this field. A write of a 0 to a R/W1S bit does not affect the bit value in the register. Software can write this field. A write of a 0 to a W1C bit does not affect the bit value in the register. A write of a 1 clears the value of the bit in the register; the remaining bits remain unchanged. A read of the register returns no meaningful data. This register is typically used to clear the corresponding bit in an interrupt register. WO Register Bit/Field Reset Value 0 1 Pin/Signal Notation [] pin signal Pin alternate function; a pin defaults to the signal without the brackets. Refers to the physical connection on the package. Refers to the electrical signal encoding of a pin. Only a write by software is valid; a read of the register returns no meaningful data. This value in the register bit diagram shows the bit/field value after any reset, unless noted. Bit cleared to 0 on chip reset. Bit set to 1 on chip reset. Nondeterministic.
bit bit field offset 0xnnn Register N reserved
yy:xx Register Bit/Field Types RC RO R/W R/WC R/W1C
39
About This Document
Table 2. Documentation Conventions (continued)

Notation assert a signal Meaning Change the value of the signal from the logically False state to the logically True state. For active High signals, the asserted signal value is 1 (High); for active Low signals, the asserted signal value is 0 (Low). The active polarity (High or Low) is defined by the signal name (see SIGNAL and SIGNAL below). Change the value of the signal from the logically True state to the logically False state. Signal names are in uppercase and in the Courier font. An overbar on a signal name indicates that it is active Low. To assert SIGNAL is to drive it Low; to deassert SIGNAL is to drive it High. Signal names are in uppercase and in the Courier font. An active High signal has no overbar. To assert SIGNAL is to drive it High; to deassert SIGNAL is to drive it Low.
deassert a signal SIGNAL SIGNAL Numbers X
An uppercase X indicates any of several values is allowed, where X can be any legal pattern. For example, a binary value of 0X00 can be either 0100 or 0000, a hex value of 0xX is 0x0 or 0x1, and so on. Hexadecimal numbers have a prefix of 0x. For example, 0x00FF is the hexadecimal number FF. All other numbers within register tables are assumed to be binary. Within conceptual information, binary numbers are indicated with a b suffix, for example, 1011b, and decimal numbers are written without a prefix or suffix.
0x
April 25, 2012
Architectural Overview
Texas Instruments is the industry leader in bringing 32-bit capabilities and the full benefits of ARM Cortex-M-based microcontrollers to the broadest reach of the microcontroller market. For current users of 8- and 16-bit MCUs, Stellaris with Cortex-M offers a direct path to the strongest ecosystem of development tools, software and knowledge in the industry. Designers who migrate to Stellaris benefit from great tools, small code footprint and outstanding performance. Even more important, designers can enter the ARM ecosystem with full confidence in a compatible roadmap from $1 to 1 GHz. With blazingly-fast responsiveness, Thumb-2 technology combines both 16-bit and 32-bit instructions to deliver the best balance of code density and performance. Thumb-2 uses 26 percent less memory than pure 32-bit code to reduce system cost while delivering 25 percent better performance. The Texas Instruments Stellaris family of microcontrollers brings high-performance 32-bit computing to cost-sensitive embedded microcontroller applications. This chapter contains an overview of the Stellaris LM4F series of microcontrollers as well as details on the LM4F120H5QR microcontroller: Stellaris LM4F Series Overview on page 41 LM4F120H5QR Microcontroller Overview on page 44 LM4F120H5QR Microcontroller Features on page 47 LM4F120H5QR Microcontroller Hardware Details on page 64
1.1
Stellaris LM4F Series Overview

The Stellaris LM4F series of ARM Cortex-M4 microcontrollers provides top performance and advanced integration. The product family is positioned for cost-conscious applications requiring significant control processing and connectivity capabilities such as: Low power, hand-held smart devices Gaming equipment Home and commercial site monitoring and control Motion control Medical instrumentation Test and measurement equipment Factory automation Fire and security Smart Energy/Smart Grid solutions Intelligent lighting control Transportation
41
Figure 1-1. Stellaris LM4F Block Diagram
The Stellaris LM4F microcontrollers consist of fifteen pin-compatible series of devices, summarized below. Each series has a range of embedded Flash and SRAM sizes. Table 1-1. Stellaris LM4F Device Series
General MCU (LM4F11x Series) LM4F110 LM4F111 LM4F112 General MCU + USB Device LM4F120 LM4F121 LM4F122 (LM4F21x (LM4F12x Series) (LM4F13x Series) Series) LM4F130 LM4F131 LM4F132 LM4F210 LM4F211 LM4F212 General MCU + USB OTG Motion Control Motion Control + USB OTG (LM4F23x Series) LM4F230 LM4F231 LM4F232 64-pin LQFP 64-pin LQFP 100-pin LQFP 144-pin LQFP 157-ball BGA (LM4F212 and LM4F232 only) Package
The Stellaris LM4F12x Series for general MCU control applications with USB Device provides USB Device capability and a generous number of serial peripherals in three packages.
April 25, 2012
Table 1-2. Stellaris LM4F12x Series

Part Number Flash (KB) SRAM (KB) 5-V Tolerant GPIOs Package Notes
LM4F120B2QR LM4F120C4QR LM4F120E5QR LM4F120H5QR LM4F121B2QR LM4F121C4QR LM4F121E5QR LM4F121H5QR LM4F122C4QC LM4F122E5QC LM4F122H5QC LM4F122H5QD
32 64 128 256 32 64 128 256 64 128 256 256
12 24 32 32 12 24 32 32 24 32 32 32 105 144-pin LQFP 69 100-pin LQFP Includes low-power hibernate functionality, and additional serial and analog functionality in larger pin-count packages. 49 No low-power hibernate functionality, but 64-pin LQFP includes additional serial functionality, and up to six more I/Os than the LM4F120 Series. 43 64-pin LQFP Includes low-power hibernate functionality.
Table 1-3. Stellaris LM4F Family of Devices

ADC Channels Battery-Backed Hibernation Analog/Digital Comparators UART Modem Signalling QEI Channels ADC External Reference 5-V Tolerant b GPIOs PWM Faults SRAM (KB) Flash (KB) CAN MAC
Part Number LM4F110B2QR LM4F110C4QR LM4F110E5QR LM4F110H5QR LM4F111B2QR LM4F111C4QR LM4F111E5QR LM4F111H5QR LM4F112C4QC LM4F112E5QC LM4F112H5QC LM4F112H5QD LM4F120B2QR LM4F120C4QR LM4F120E5QR LM4F120H5QR LM4F121B2QR LM4F121C4QR LM4F121E5QR LM4F121H5QR LM4F122C4QC
32 64 128 256 32 64 128 256 64 128 256 256 32 64 128 256 32 64 128 256 64
12 24 32 32 12 24 32 32 24 32 32 32 12 24 32 32 12 24 32 32 24
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
D D D D D D D D D
8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
4 4 4 4 6 6 6 6 6 6 6 6 4 4 4 4 6 6 6 6 6
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
12 12 12 12 12 12 12 12 22 22 22 24 12 12 12 12 12 12 12 12 22
2/16 2/16 2/16 2/16 2/16 2/16 2/16 2/16 3/16 3/16 3/16
0-43 64LQFP 0-43 64LQFP 0-43 64LQFP 0-43 64LQFP 0-49 64LQFP 0-49 64LQFP 0-49 64LQFP 0-49 64LQFP 0-69 100LQFP 0-69 100LQFP 0-69 100LQFP
3/16 0-105 144LQFP 2/16 2/16 2/16 2/16 2/16 2/16 2/16 2/16 3/16 0-43 64LQFP 0-43 64LQFP 0-43 64LQFP 0-43 64LQFP 0-49 64LQFP 0-49 64LQFP 0-49 64LQFP 0-49 64LQFP 0-69 100LQFP
Package
SSI/SPI
UART
PWM
USB
I2C
43
Table 1-3. Stellaris LM4F Family of Devices (continued)

ADC Channels Battery-Backed Hibernation Analog/Digital Comparators UART Modem Signalling QEI Channels ADC External Reference 5-V Tolerant b GPIOs PWM Faults SRAM (KB) Flash (KB) CAN MAC
Part Number LM4F122E5QC LM4F122H5QC LM4F122H5QD LM4F130C4QR LM4F130E5QR LM4F130H5QR LM4F131C4QR LM4F131E5QR LM4F131H5QR LM4F132C4QC LM4F132E5QC LM4F132H5QC LM4F132H5QD LM4F210E5QR LM4F210H5QR LM4F211E5QR LM4F211H5QR LM4F212E5QC LM4F212H5BB LM4F212H5QC LM4F212H5QD LM4F230E5QR LM4F230H5QR LM4F231E5QR LM4F231H5QR LM4F232E5QC LM4F232H5BB LM4F232H5QC LM4F232H5QD
128 256 256 64 128 256 64 128 256 64 128 256 256 128 256 128 256 128 256 256 256 128 256 128 256 128 256 256 256
32 32 32 24 32 32 24 32 32 24 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32
16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16
2 2 6 6 8 8 8 8 2 2 6 6 8 8 8 8
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
D D D O O O O O O O O O O O O O O O O O O
8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
6 6 6 4 4 4 6 6 6 6 6 6 6 4 4 6 6 6 6 6 6 4 4 6 6 6 6 6 6
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
22 22 24 12 12 12 12 12 12 22 22 22 24 12 12 12 12 22 24 22 24 12 12 12 12 22 24 22 24
3/16 3/16
0-69 100LQFP 0-69 100LQFP
3/16 0-105 144LQFP 2/16 2/16 2/16 2/16 2/16 2/16 3/16 3/16 3/16 0-43 64LQFP 0-43 64LQFP 0-43 64LQFP 0-49 64LQFP 0-49 64LQFP 0-49 64LQFP 0-69 100LQFP 0-69 100LQFP 0-69 100LQFP
3/16 0-105 144LQFP 2/16 2/16 2/16 2/16 3/16 0-43 64LQFP 0-43 64LQFP 0-49 64LQFP 0-49 64LQFP 0-69 100LQFP
3/16 0-120 157BGA 3/16 0-69 100LQFP
3/16 0-105 144LQFP 2/16 2/16 2/16 2/16 3/16 0-43 64LQFP 0-43 64LQFP 0-49 64LQFP 0-49 64LQFP 0-69 100LQFP
3/16 0-120 157BGA 3/16 0-69 100LQFP
3/16 0-105 144LQFP
a. USB options for Stellaris microcontrollers include Device Only (D) capability, Host/Device (H) capability, and On-The-Go/Host/Device capability (O). b. Minimum is number of pins dedicated to GPIO; additional pins are available if certain peripherals are not used. See data sheet for details.
1.2
LM4F120H5QR Microcontroller Overview

The Stellaris LM4F120H5QR microcontroller combines complex integration and high performance with the features shown in Table 1-4.
April 25, 2012
Package
SSI/SPI
UART
PWM
USB
I2C
Table 1-4. Stellaris LM4F120H5QR Microcontroller Features

Feature Core Performance Flash System SRAM EEPROM Internal ROM Description ARM Cortex-M4F processor core 80-MHz operation; 100 DMIPS performance 256 KB single-cycle Flash memory 32 KB single-cycle SRAM 2KB of EEPROM Internal ROM loaded with StellarisWare software Communication Interfaces Universal Asynchronous Receivers/Transmitter (UART) Eight UARTs Synchronous Serial Interface (SSI) Inter-Integrated Circuit (I2C) Four SSI modules Four I2C modules with four transmission speeds including high-speed mode CAN 2.0 A/B controllers USB 2.0 Device System Integration Micro Direct Memory Access (DMA) General-Purpose Timer (GPTM) Watchdog Timer (WDT) Hibernation General-Purpose Input/Output (GPIO) ARM PrimeCell 32-channel configurable DMA controller Six 16/32-bit GPTM blocks and six 32/64-bit Wide GPTM blocks Two watchdog timers Lower-power battery-backed Hibernation module Six physical GPIO blocks Analog Support Analog-to-Digital Converter (ADC) Analog Comparator Controller Digital Comparator JTAG and Serial Wire Debug (SWD) Package Operating Range Two 12-bit ADC modules Two independent integrated analog comparators 16 digital comparators One JTAG module with integrated ARM SWD 64-pin LQFP Industrial (-40C to 85C) temperature range
Controller Area Network (CAN) Universal Serial Bus (USB)
Figure 1-2 on page 46 shows the features on the Stellaris LM4F120H5QR microcontroller. Note that there are two on-chip buses that connect the core to the peripherals. The Advanced Peripheral Bus (APB) bus is the legacy bus. The Advanced High-Performance Bus (AHB) bus provides better back-to-back access performance than the APB bus.
45
Figure 1-2. Stellaris LM4F120H5QR Microcontroller High-Level Block Diagram
JTAG/SWD ARM Cortex-M4F (80MHz) System Controland Clocks (w/ Precis. Osc.) ETM NVIC FPU MPU ICodebus System Bus DCodebus Flash (256KB) ROM Boot Loader DriverLib AES & CRC
LM4F120H5QR
Bus Matrix
SRAM (32KB)
SYSTEM PERIPHERALS Watchdog Timer (2) Hibernation Module GeneralPurpose Timer (12)
DMA
EEPROM (2K)
Advanced Peripheral Bus (APB)
GPIOs (43)
Advanced High-Performance Bus (AHB)
SERIAL PERIPHERALS UART (8)
USBDevice (FSPHY)
SSI (4)
I2C (4) CAN Controller (1)
ANALOG PERIPHERALS Analog Comparator (2) 12- BitADC Channels (12)
April 25, 2012
For applications requiring extreme conservation of power, the LM4F120H5QR microcontroller features a battery-backed Hibernation module to efficiently power down the LM4F120H5QR to a low-power state during extended periods of inactivity. With a power-up/power-down sequencer, a continuous time counter (RTC), a pair of match registers, an APB interface to the system bus, and dedicated battery-backed memory, the Hibernation module positions the LM4F120H5QR microcontroller perfectly for battery applications. In addition, the LM4F120H5QR microcontroller offers the advantages of ARM's widely available development tools, System-on-Chip (SoC) infrastructure IP applications, and a large user community. Additionally, the microcontroller uses ARM's Thumb-compatible Thumb-2 instruction set to reduce memory requirements and, thereby, cost. Finally, the LM4F120H5QR microcontroller is code-compatible to all members of the extensive Stellaris family; providing flexibility to fit precise needs. Texas Instruments offers a complete solution to get to market quickly, with evaluation and development boards, white papers and application notes, an easy-to-use peripheral driver library, and a strong support, sales, and distributor network.
1.3
LM4F120H5QR Microcontroller Features

The LM4F120H5QR microcontroller component features and general function are discussed in more detail in the following section.
1.3.1
ARM Cortex-M4F Processor Core

All members of the Stellaris product family, including the LM4F120H5QR microcontroller, are designed around an ARM Cortex-M processor core. The ARM Cortex-M processor provides the core for a high-performance, low-cost platform that meets the needs of minimal memory implementation, reduced pin count, and low power consumption, while delivering outstanding computational performance and exceptional system response to interrupts.
1.3.1.1
Processor Core (see page 65)

32-bit ARM Cortex-M4F architecture optimized for small-footprint embedded applications 80-MHz operation; 100 DMIPS performance Outstanding processing performance combined with fast interrupt handling Thumb-2 mixed 16-/32-bit instruction set delivers the high performance expected of a 32-bit ARM core in a compact memory size usually associated with 8- and 16-bit devices, typically in the range of a few kilobytes of memory for microcontroller-class applications Single-cycle multiply instruction and hardware divide Atomic bit manipulation (bit-banding), delivering maximum memory utilization and streamlined peripheral control Unaligned data access, enabling data to be efficiently packed into memory IEEE754-compliant single-precision Floating-Point Unit (FPU) 16-bit SIMD vector processing unit Fast code execution permits slower processor clock or increases sleep mode time
47
Harvard architecture characterized by separate buses for instruction and data Efficient processor core, system and memories Hardware division and fast digital-signal-processing orientated multiply accumulate Saturating arithmetic for signal processing Deterministic, high-performance interrupt handling for time-critical applications Memory protection unit (MPU) to provide a privileged mode for protected operating system functionality Enhanced system debug with extensive breakpoint and trace capabilities Serial Wire Debug and Serial Wire Trace reduce the number of pins required for debugging and tracing Migration from the ARM7 processor family for better performance and power efficiency Optimized for single-cycle Flash memory usage Ultra-low power consumption with integrated sleep modes
1.3.1.2
System Timer (SysTick) (see page 119)

ARM Cortex-M4F includes an integrated system timer, SysTick. SysTick provides a simple, 24-bit, clear-on-write, decrementing, wrap-on-zero counter with a flexible control mechanism. The counter can be used in several different ways, for example: An RTOS tick timer that fires at a programmable rate (for example, 100 Hz) and invokes a SysTick routine A high-speed alarm timer using the system clock A variable rate alarm or signal timerthe duration is range-dependent on the reference clock used and the dynamic range of the counter A simple counter used to measure time to completion and time used An internal clock-source control based on missing/meeting durations.
1.3.1.3
Nested Vectored Interrupt Controller (NVIC) (see page 120)

The LM4F120H5QR controller includes the ARM Nested Vectored Interrupt Controller (NVIC). The NVIC and Cortex-M4F prioritize and handle all exceptions in Handler Mode. The processor state is automatically stored to the stack on an exception and automatically restored from the stack at the end of the Interrupt Service Routine (ISR). The interrupt vector is fetched in parallel to the state saving, enabling efficient interrupt entry. The processor supports tail-chaining, meaning that back-to-back interrupts can be performed without the overhead of state saving and restoration. Software can set eight priority levels on 7 exceptions (system handlers) and 65 interrupts. Deterministic, fast interrupt processing: always 12 cycles, or just 6 cycles with tail-chaining External non-maskable interrupt signal (NMI) available for immediate execution of NMI handler for safety critical applications
April 25, 2012
Dynamically reprioritizable interrupts Exceptional interrupt handling via hardware implementation of required register manipulations
1.3.1.4
System Control Block (SCB) (see page 121)

The SCB provides system implementation information and system control, including configuration, control, and reporting of system exceptions.
1.3.1.5
Memory Protection Unit (MPU) (see page 121)

The MPU supports the standard ARM7 Protected Memory System Architecture (PMSA) model. The MPU provides full support for protection regions, overlapping protection regions, access permissions, and exporting memory attributes to the system.
1.3.1.6
Floating-Point Unit (FPU) (see page 126)

The FPU fully supports single-precision add, subtract, multiply, divide, multiply and accumulate, and square root operations. It also provides conversions between fixed-point and floating-point data formats, and floating-point constant instructions. 32-bit instructions for single-precision (C float) data-processing operations Combined Multiply and Accumulate instructions for increased precision (Fused MAC) Hardware support for conversion, addition, subtraction, multiplication with optional accumulate, division, and square-root Hardware support for denormals and all IEEE rounding modes 32 dedicated 32-bit single-precision registers, also addressable as 16 double-word registers Decoupled three stage pipeline
1.3.2
On-Chip Memory
The LM4F120H5QR microcontroller is integrated with the following set of on-chip memory and features: 32 KB single-cycle SRAM 256 KB single-cycle Flash memory Internal ROM loaded with StellarisWare software: Stellaris Peripheral Driver Library Stellaris Boot Loader Advanced Encryption Standard (AES) cryptography tables Cyclic Redundancy Check (CRC) error detection functionality 2KB EEPROM
1.3.2.1
SRAM (see page 511)

The LM4F120H5QR microcontroller provides 32 KB of single-cycle on-chip SRAM. The internal SRAM of the Stellaris devices is located at offset 0x2000.0000 of the device memory map.
49
Because read-modify-write (RMW) operations are very time consuming, ARM has introduced bit-banding technology in the Cortex-M4F processor. With a bit-band-enabled processor, certain regions in the memory map (SRAM and peripheral space) can use address aliases to access individual bits in a single, atomic operation. Data can be transferred to and from the SRAM using the Micro Direct Memory Access Controller (DMA).
1.3.2.2
Flash Memory (see page 514)

The LM4F120H5QR microcontroller provides 256 KB of single-cycle on-chip Flash memory. The Flash memory is organized as a set of 1-KB blocks that can be individually erased. Erasing a block causes the entire contents of the block to be reset to all 1s. These blocks are paired into a set of 2-KB blocks that can be individually protected. The blocks can be marked as read-only or execute-only, providing different levels of code protection. Read-only blocks cannot be erased or programmed, protecting the contents of those blocks from being modified. Execute-only blocks cannot be erased or programmed, and can only be read by the controller instruction fetch mechanism, protecting the contents of those blocks from being read by either the controller or by a debugger.
1.3.2.3
ROM (see page 512)

The LM4F120H5QR ROM is preprogrammed with the following software and programs: Stellaris Peripheral Driver Library Stellaris Boot Loader Advanced Encryption Standard (AES) cryptography tables Cyclic Redundancy Check (CRC) error-detection functionality The Stellaris Peripheral Driver Library is a royalty-free software library for controlling on-chip peripherals with a boot-loader capability. The library performs both peripheral initialization and control functions, with a choice of polled or interrupt-driven peripheral support. In addition, the library is designed to take full advantage of the stellar interrupt performance of the ARM Cortex-M4F core. No special pragmas or custom assembly code prologue/epilogue functions are required. For applications that require in-field programmability, the royalty-free Stellaris Boot Loader can act as an application loader and support in-field firmware updates. The Advanced Encryption Standard (AES) is a publicly defined encryption standard used by the U.S. Government. AES is a strong encryption method with reasonable performance and size. In addition, it is fast in both hardware and software, is fairly easy to implement, and requires little memory. The Texas Instruments encryption package is available with full source code, and is based on lesser general public license (LGPL) source. An LGPL means that the code can be used within an application without any copyleft implications for the application (the code does not automatically become open source). Modifications to the package source, however, must be open source. CRC (Cyclic Redundancy Check) is a technique to validate a span of data has the same contents as when previously checked. This technique can be used to validate correct receipt of messages (nothing lost or modified in transit), to validate data after decompression, to validate that Flash memory contents have not been changed, and for other cases where the data needs to be validated. A CRC is preferred over a simple checksum (e.g. XOR all bits) because it catches changes more readily.
April 25, 2012
1.3.2.4
EEPROM (see page 518)

The LM4F120H5QR microcontroller includes an EEPROM with the following features: 2K bytes of memory accessible as 512 32-bit words 32 blocks of 16 words (64 bytes) each Built-in wear leveling Access protection per block Lock protection option for the whole peripheral as well as per block using 32-bit to 96-bit unlock codes (application selectable) Interrupt support for write completion to avoid polling Endurance of 500K writes (when writing at fixed offset in every alternate page in circular fashion) to 15M operations (when cycling through two pages ) per each 2-page block.
1.3.3
Serial Communications Peripherals

The LM4F120H5QR controller supports both asynchronous and synchronous serial communications with: CAN 2.0 A/B controller USB 2.0 Device Eight UARTs with IrDA, 9-bit and ISO 7816 support (one UART with modem flow control) Four I2C modules with four transmission speeds including high-speed mode Four Synchronous Serial Interface modules (SSI) The following sections provide more detail on each of these communications functions.
1.3.3.1
Controller Area Network (see page 1014)

Controller Area Network (CAN) is a multicast shared serial-bus standard for connecting electronic control units (ECUs). CAN was specifically designed to be robust in electromagnetically noisy environments and can utilize a differential balanced line like RS-485 or twisted-pair wire. Originally created for automotive purposes, it is now used in many embedded control applications (for example, industrial or medical). Bit rates up to 1 Mbps are possible at network lengths below 40 meters. Decreased bit rates allow longer network distances (for example, 125 Kbps at 500m). A transmitter sends a message to all CAN nodes (broadcasting). Each node decides on the basis of the identifier received whether it should process the message. The identifier also determines the priority that the message enjoys in competition for bus access. Each CAN message can transmit from 0 to 8 bytes of user information. The LM4F120H5QR microcontroller includes one CAN unit with the following features: CAN protocol version 2.0 part A/B Bit rates up to 1 Mbps
51
32 message objects with individual identifier masks Maskable interrupt Disable Automatic Retransmission mode for Time-Triggered CAN (TTCAN) applications Programmable Loopback mode for self-test operation Programmable FIFO mode enables storage of multiple message objects Gluelessly attaches to an external CAN transceiver through the CANnTX and CANnRX signals
1.3.3.2
USB (see page 1064)

Universal Serial Bus (USB) is a serial bus standard designed to allow peripherals to be connected and disconnected using a standardized interface without rebooting the system. The LM4F120H5QR microcontroller supports the USB 2.0 full-speed configuration in Device mode. The USB module has the following features: Complies with USB-IF certification standards USB 2.0 full-speed (12 Mbps) and low-speed (1.5 Mbps) operation with integrated PHY 4 transfer types: Control, Interrupt, Bulk, and Isochronous 16 endpoints 1 dedicated control IN endpoint and 1 dedicated control OUT endpoint 7 configurable IN endpoints and 7 configurable OUT endpoints 4 KB dedicated endpoint memory: one endpoint may be defined for double-buffered 1023-byte isochronous packet size Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive for up to three IN endpoints and three OUT endpoints Channel requests asserted when FIFO contains required amount of data
1.3.3.3
UART (see page 861)

A Universal Asynchronous Receiver/Transmitter (UART) is an integrated circuit used for RS-232C serial communications, containing a transmitter (parallel-to-serial converter) and a receiver (serial-to-parallel converter), each clocked separately. The LM4F120H5QR microcontroller includes eight fully programmable 16C550-type UARTs. Although the functionality is similar to a 16C550 UART, this UART design is not register compatible. The UART can generate individually masked interrupts from the Rx, Tx, modem flow control, and error conditions. The module generates a single combined interrupt when any of the interrupts are asserted and are unmasked. The eight UARTs have the following features:
April 25, 2012
Programmable baud-rate generator allowing speeds up to 5 Mbps for regular speed (divide by 16) and 10 Mbps for high speed (divide by 8) Separate 16x8 transmit (TX) and receive (RX) FIFOs to reduce CPU interrupt service loading Programmable FIFO length, including 1-byte deep operation providing conventional double-buffered interface FIFO trigger levels of 1/8, 1/4, 1/2, 3/4, and 7/8 Standard asynchronous communication bits for start, stop, and parity Line-break generation and detection Fully programmable serial interface characteristics 5, 6, 7, or 8 data bits Even, odd, stick, or no-parity bit generation/detection 1 or 2 stop bit generation IrDA serial-IR (SIR) encoder/decoder providing Programmable use of IrDA Serial Infrared (SIR) or UART input/output Support of IrDA SIR encoder/decoder functions for data rates up to 115.2 Kbps half-duplex Support of normal 3/16 and low-power (1.41-2.23 s) bit durations Programmable internal clock generator enabling division of reference clock by 1 to 256 for low-power mode bit duration Support for communication with ISO 7816 smart cards Modem flow control (on UART1) LIN protocol support EIA-485 9-bit support Standard FIFO-level and End-of-Transmission interrupts Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive Receive single request asserted when data is in the FIFO; burst request asserted at programmed FIFO level Transmit single request asserted when there is space in the FIFO; burst request asserted at programmed FIFO level
1.3.3.4
I2C (see page 967)

The Inter-Integrated Circuit (I2C) bus provides bi-directional data transfer through a two-wire design (a serial data line SDA and a serial clock line SCL). The I2C bus interfaces to external I2C devices
53
such as serial memory (RAMs and ROMs), networking devices, LCDs, tone generators, and so on. The I2C bus may also be used for system testing and diagnostic purposes in product development and manufacture. Each device on the I2C bus can be designated as either a master or a slave. I2C module supports both sending and receiving data as either a master or a slave and can operate simultaneously as both a master and a slave. Both the I2C master and slave can generate interrupts. The LM4F120H5QR microcontroller includes four I2C modules with the following features: Devices on the I2C bus can be designated as either a master or a slave Supports both transmitting and receiving data as either a master or a slave Supports simultaneous master and slave operation Four I2C modes Master transmit Master receive Slave transmit Slave receive Four transmission speeds: Standard (100 Kbps) Fast-mode (400 Kbps) Fast-mode plus (1 Mbps) High-speed mode (3.33 Mbps) Clock low timeout interrupt Dual slave address capability Clock low timeout interrupt Dual slave address capability Master and slave interrupt generation Master generates interrupts when a transmit or receive operation completes (or aborts due to an error) Slave generates interrupts when data has been transferred or requested by a master or when a START or STOP condition is detected Master with arbitration and clock synchronization, multimaster support, and 7-bit addressing mode
April 25, 2012
1.3.3.5
SSI (see page 924)

Synchronous Serial Interface (SSI) is a four-wire bi-directional communications interface that converts data between parallel and serial. The SSI module performs serial-to-parallel conversion on data received from a peripheral device, and parallel-to-serial conversion on data transmitted to a peripheral device. The SSI module can be configured as either a master or slave device. As a slave device, the SSI module can also be configured to disable its output, which allows a master device to be coupled with multiple slave devices. The TX and RX paths are buffered with separate internal FIFOs. The SSI module also includes a programmable bit rate clock divider and prescaler to generate the output serial clock derived from the SSI module's input clock. Bit rates are generated based on the input clock and the maximum bit rate is determined by the connected peripheral. The LM4F120H5QR microcontroller includes four SSI modules with the following features: Programmable interface operation for Freescale SPI, MICROWIRE, or Texas Instruments synchronous serial interfaces Master or slave operation Programmable clock bit rate and prescaler Separate transmit and receive FIFOs, each 16 bits wide and 8 locations deep Programmable data frame size from 4 to 16 bits Internal loopback test mode for diagnostic/debug testing Standard FIFO-based interrupts and End-of-Transmission interrupt Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive Receive single request asserted when data is in the FIFO; burst request asserted when FIFO contains 4 entries Transmit single request asserted when there is space in the FIFO; burst request asserted when FIFO contains 4 entries
1.3.4
System Integration
The LM4F120H5QR microcontroller provides a variety of standard system functions integrated into the device, including: Direct Memory Access Controller (DMA) System control and clocks including on-chip precision 16-MHz oscillator Six 32-bit timers (up to twelve 16-bit) Six wide 64-bit timers (up to twelve 32-bit) Twelve 16/32-bit Capture Compare PWM (CCP) pins Twelve 32/64-bit Capture Compare PWM (CCP) pins
55
Lower-power battery-backed Hibernation module Real-Time Clock in Hibernation module Two Watchdog Timers One timer runs off the main oscillator One timer runs off the precision internal oscillator Up to 43 GPIOs, depending on configuration Highly flexible pin muxing allows use as GPIO or one of several peripheral functions Independently configurable to 2, 4 or 8 mA drive capability Up to 4 GPIOs can have 18 mA drive capability The following sections provide more detail on each of these functions.
1.3.4.1
Direct Memory Access (see page 568)

The LM4F120H5QR microcontroller includes a Direct Memory Access (DMA) controller, known as micro-DMA (DMA). The DMA controller provides a way to offload data transfer tasks from the Cortex-M4F processor, allowing for more efficient use of the processor and the available bus bandwidth. The DMA controller can perform transfers between memory and peripherals. It has dedicated channels for each supported on-chip module and can be programmed to automatically perform transfers between peripherals and memory as the peripheral is ready to transfer more data. The DMA controller provides the following features: ARM PrimeCell 32-channel configurable DMA controller Support for memory-to-memory, memory-to-peripheral, and peripheral-to-memory in multiple transfer modes Basic for simple transfer scenarios Ping-pong for continuous data flow Scatter-gather for a programmable list of arbitrary transfers initiated from a single request Highly flexible and configurable channel operation Independently configured and operated channels Dedicated channels for supported on-chip modules Flexible channel assignments One channel each for receive and transmit path for bidirectional modules Dedicated channel for software-initiated transfers Per-channel configurable priority scheme Optional software-initiated requests for any channel Two levels of priority Design optimizations for improved bus access performance between DMA controller and the processor core
April 25, 2012
DMA controller access is subordinate to core access RAM striping Peripheral bus segmentation Data sizes of 8, 16, and 32 bits Transfer size is programmable in binary steps from 1 to 1024 Source and destination address increment size of byte, half-word, word, or no increment Maskable peripheral requests Interrupt on transfer completion, with a separate interrupt per channel
1.3.4.2
System Control and Clocks (see page 208)

System control determines the overall operation of the device. It provides information about the device, controls power-saving features, controls the clocking of the device and individual peripherals, and handles reset detection and reporting. Device identification information: version, part number, SRAM size, Flash memory size, and so on Power control On-chip fixed Low Drop-Out (LDO) voltage regulator Hibernation module handles the power-up/down 3.3 V sequencing and control for the core digital logic and analog circuits Low-power options for microcontroller: Sleep and Deep-sleep modes with clock gating Low-power options for on-chip modules: software controls shutdown of individual peripherals and memory 3.3-V supply brown-out detection and reporting via interrupt or reset Multiple clock sources for microcontroller system clock Precision Oscillator (PIOSC): On-chip resource providing a 16 MHz 1% frequency at room temperature 16 MHz 3% across temperature Can be recalibrated with 7-bit trim resolution Software power down control for low power modes Main Oscillator (MOSC): A frequency-accurate clock source by one of two means: an external single-ended clock source is connected to the OSC0 input pin, or an external crystal is connected across the OSC0 input and OSC1 output pins. External crystal used with or without on-chip PLL: select supported frequencies from 4 MHz to 25 MHz. External oscillator: from DC to maximum device speed Internal 30-kHz Oscillator: on chip resource providing a 30 kHz 50% frequency, used during power-saving modes
57
32.768-kHz external oscillator for the Hibernation Module: eliminates need for additional crystal for main clock source Flexible reset sources Power-on reset (POR) Reset pin assertion Brown-out reset (BOR) detector alerts to system power drops Software reset Watchdog timer reset MOSC failure
1.3.4.3
Programmable Timers (see page 686)

Programmable timers can be used to count or time external events that drive the Timer input pins. Each 16/32-bit GPTM block provides two 16-bit timers/counters that can be configured to operate independently as timers or event counters, or configured to operate as one 32-bit timer or one 32-bit Real-Time Clock (RTC). Each 32/64-bit Wide GPTM block provides two 32-bit timers/counters that can be configured to operate independently as timersor event counters, or configured to operate as one 64-bit timer or one 64-bit Real-Time Clock (RTC). Timers can also be used to trigger analog-to-digital (ADC) conversions. The General-Purpose Timer Module (GPTM) contains six 16/32-bit GPTM blocks and six 32/64-bit Wide GPTM blocks with the following functional options: 16/32-bit operating modes: 16- or 32-bit programmable one-shot timer 16- or 32-bit programmable periodic timer 16-bit general-purpose timer with an 8-bit prescaler 32-bit Real-Time Clock (RTC) when using an external 32.768-KHz clock as the input 16-bit input-edge count- or time-capture modes with an 8-bit prescaler 16-bit PWM mode with an 8-bit prescaler and software-programmable output inversion of the PWM signal 32/64-bit operating modes: 32- or 64-bit programmable one-shot timer 32- or 64-bit programmable periodic timer 32-bit general-purpose timer with a 16-bit prescaler 64-bit Real-Time Clock (RTC) when using an external 32.768-KHz clock as the input 32-bit input-edge count- or time-capture modes with a16-bit prescaler
April 25, 2012
32-bit PWM mode with a 16-bit prescaler and software-programmable output inversion of the PWM signal Count up or down Twelve 16/32-bit Capture Compare PWM pins (CCP) Twelve 32/64-bit Capture Compare PWM pins (CCP) Daisy chaining of timer modules to allow a single timer to initiate multiple timing events Timer synchronization allows selected timers to start counting on the same clock cycle ADC event trigger User-enabled stalling when the microcontroller asserts CPU Halt flag during debug (excluding RTC mode) Ability to determine the elapsed time between the assertion of the timer interrupt and entry into the interrupt service routine. Efficient transfers using Micro Direct Memory Access Controller (DMA) Dedicated channel for each timer Burst request generated on timer interrupt
1.3.4.4
CCP Pins (see page 694)

Capture Compare PWM pins (CCP) can be used by the General-Purpose Timer Module to time/count external events using the CCP pin as an input. Alternatively, the GPTM can generate a simple PWM output on the CCP pin. The LM4F120H5QR microcontroller includes twelve 16/32-bit CCP pins that can be programmed to operate in the following modes: Capture: The GP Timer is incremented/decremented by programmed events on the CCP input. The GP Timer captures and stores the current timer value when a programmed event occurs. Compare: The GP Timer is incremented/decremented by programmed events on the CCP input. The GP Timer compares the current value with a stored value and generates an interrupt when a match occurs. PWM: The GP Timer is incremented/decremented by the system clock. A PWM signal is generated based on a match between the counter value and a value stored in a match register and is output on the CCP pin.
1.3.4.5
Hibernation Module (see page 480)

The Hibernation module provides logic to switch power off to the main processor and peripherals and to wake on external or time-based events. The Hibernation module includes power-sequencing logic and has the following features: 32-bit real-time seconds counter (RTC) with 1/32,768 second resolution 32-bit RTC seconds match register and 15-bit sub seconds match for timed wake-up and interrupt generation with 1/32,768 second resolution
59
RTC predivider trim for making fine adjustments to the clock rate Two mechanisms for power control System power control using discrete external regulator On-chip power control using internal switches under register control Dedicated pin for waking using an external signal RTC operational and hibernation memory valid as long as VBAT is valid Low-battery detection, signaling, and interrupt generation, with optional wake on low battery GPIO pin state can be retained during hibernation Clock source from a 32.768-kHz external crystal or oscillator 16 32-bit words of battery-backed memory to save state during hibernation Programmable interrupts for RTC match, external wake, and low battery events
1.3.4.6
Watchdog Timers (see page 756)

A watchdog timer is used to regain control when a system has failed due to a software error or to the failure of an external device to respond in the expected way. The Stellaris Watchdog Timer can generate an interrupt, a non-maskable interrupt, or a reset when a time-out value is reached. In addition, the Watchdog Timer is ARM FiRM-compliant and can be configured to generate an interrupt to the microcontroller on its first time-out, and to generate a reset signal on its second time-out. Once the Watchdog Timer has been configured, the lock register can be written to prevent the timer configuration from being inadvertently altered. The LM4F120H5QR microcontroller has two Watchdog Timer modules: Watchdog Timer 0 uses the system clock for its timer clock; Watchdog Timer 1 uses the PIOSC as its timer clock. The Stellaris Watchdog Timer module has the following features: 32-bit down counter with a programmable load register Separate watchdog clock with an enable Programmable interrupt generation logic with interrupt masking and optional NMI function Lock register protection from runaway software Reset generation logic with an enable/disable User-enabled stalling when the microcontroller asserts the CPU Halt flag during debug
1.3.4.7
Programmable GPIOs (see page 632)

General-purpose input/output (GPIO) pins offer flexibility for a variety of connections. The Stellaris GPIO module is comprised of six physical GPIO blocks, each corresponding to an individual GPIO port. The GPIO module is FiRM-compliant (compliant to the ARM Foundation IP for Real-Time Microcontrollers specification) and supports 0-43 programmable input/output pins. The number of GPIOs available depends on the peripherals being used (see Signal Tables on page 1137 for the signals available to each GPIO pin).
April 25, 2012
Up to 43 GPIOs, depending on configuration Highly flexible pin muxing allows use as GPIO or one of several peripheral functions 5-V-tolerant in input configuration Two means of port access: either Advanced High-Performance Bus (AHB) with better back-to-back access performance, or the legacy Advanced Peripheral Bus (APB) for backwards-compatibility with existing code for Ports A-G Fast toggle capable of a change every clock cycle for ports on AHB, every two clock cycles for ports on APB Programmable control for GPIO interrupts Interrupt generation masking Edge-triggered on rising, falling, or both Level-sensitive on High or Low values Bit masking in both read and write operations through address lines Can be used to initiate an ADC sample sequence or a DMA transfer Pin state can be retained during Hibernation mode Pins configured as digital inputs are Schmitt-triggered Programmable control for GPIO pad configuration Weak pull-up or pull-down resistors 2-mA, 4-mA, and 8-mA pad drive for digital communication; up to four pads can sink 18-mA for high-current applications Slew rate control for 8-mA pad drive Open drain enables Digital input enables
1.3.5
Analog
The LM4F120H5QR microcontroller provides analog functions integrated into the device, including: Two 12-bit Analog-to-Digital Converters (ADC) with 12 analog input channels and a sample rate of one million samples/second Two analog comparators 16 digital comparators On-chip voltage regulator The following provides more detail on these analog functions.
61
1.3.5.1
ADC (see page 781)

An analog-to-digital converter (ADC) is a peripheral that converts a continuous analog voltage to a discrete digital number. The Stellaris ADC module features 12-bit conversion resolution and supports 12 input channels plus an internal temperature sensor. Four buffered sample sequencers allow rapid sampling of up to 12 analog input sources without controller intervention. Each sample sequencer provides flexible programming with fully configurable input source, trigger events, interrupt generation, and sequencer priority. Each ADC module has a digital comparator function that allows the conversion value to be diverted to a comparison unit that provides eight digital comparators. The LM4F120H5QR microcontroller provides two ADC modules with the following features: 12 shared analog input channels 12-bit precision ADC Single-ended and differential-input configurations On-chip internal temperature sensor Maximum sample rate of one million samples/second Optional phase shift in sample time programmable from 22.5 to 337.5 Four programmable sample conversion sequencers from one to eight entries long, with corresponding conversion result FIFOs Flexible trigger control Controller (software) Timers Analog Comparators GPIO Hardware averaging of up to 64 samples Digital comparison unit providing eight digital comparators Converter uses VDDA and GNDA as the voltage reference Power and ground for the analog circuitry is separate from the digital power and ground Efficient transfers using Micro Direct Memory Access Controller (DMA) Dedicated channel for each sample sequencer ADC module uses burst requests for DMA
1.3.5.2
Analog Comparators (see page 1121)

An analog comparator is a peripheral that compares two analog voltages and provides a logical output that signals the comparison result. The LM4F120H5QR microcontroller provides two independent integrated analog comparators that can be configured to drive an output or generate an interrupt or ADC event.
April 25, 2012
The comparator can provide its output to a device pin, acting as a replacement for an analog comparator on the board, or it can be used to signal the application via interrupts or triggers to the ADC to cause it to start capturing a sample sequence. The interrupt generation and ADC triggering logic is separate. This means, for example, that an interrupt can be generated on a rising edge and the ADC triggered on a falling edge. The LM4F120H5QR microcontroller provides two independent integrated analog comparators with the following functions: Compare external pin input to external pin input or to internal programmable voltage reference Compare a test voltage against any one of the following voltages: An individual external reference voltage A shared single external reference voltage A shared internal reference voltage
1.3.6
JTAG and ARM Serial Wire Debug (see page 196)

The Joint Test Action Group (JTAG) port is an IEEE standard that defines a Test Access Port and Boundary Scan Architecture for digital integrated circuits and provides a standardized serial interface for controlling the associated test logic. The TAP, Instruction Register (IR), and Data Registers (DR) can be used to test the interconnections of assembled printed circuit boards and obtain manufacturing information on the components. The JTAG Port also provides a means of accessing and controlling design-for-test features such as I/O pin observation and control, scan testing, and debugging. Texas Instruments replaces the ARM SW-DP and JTAG-DP with the ARM Serial Wire JTAG Debug Port (SWJ-DP) interface. The SWJ-DP interface combines the SWD and JTAG debug ports into one module providing all the normal JTAG debug and test functionality plus real-time access to system memory without halting the core or requiring any target resident code. The SWJ-DP interface has the following features: IEEE 1149.1-1990 compatible Test Access Port (TAP) controller Four-bit Instruction Register (IR) chain for storing JTAG instructions IEEE standard instructions: BYPASS, IDCODE, SAMPLE/PRELOAD, EXTEST and INTEST ARM additional instructions: APACC, DPACC and ABORT Integrated ARM Serial Wire Debug (SWD) Serial Wire JTAG Debug Port (SWJ-DP) Flash Patch and Breakpoint (FPB) unit for implementing breakpoints Data Watchpoint and Trace (DWT) unit for implementing watchpoints, trigger resources, and system profiling Instrumentation Trace Macrocell (ITM) for support of printf style debugging Embedded Trace Macrocell (ETM) for instruction trace capture Trace Port Interface Unit (TPIU) for bridging to a Trace Port Analyzer
63
1.3.7
Packaging and Temperature

Industrial-range (-40C to 85C) 64-pin RoHS-compliant LQFP package
1.4
LM4F120H5QR Microcontroller Hardware Details

Details on the pins and package can be found in the following sections: Pin Diagram on page 1136 Signal Tables on page 1137 Operating Characteristics on page 1157 Electrical Characteristics on page 1158 Package Information on page 1226
April 25, 2012
The Cortex-M4F Processor

The ARM Cortex-M4F processor provides a high-performance, low-cost platform that meets the system requirements of minimal memory implementation, reduced pin count, and low power consumption, while delivering outstanding computational performance and exceptional system response to interrupts. Features include: 32-bit ARM Cortex-M4F architecture optimized for small-footprint embedded applications 80-MHz operation; 100 DMIPS performance Outstanding processing performance combined with fast interrupt handling Thumb-2 mixed 16-/32-bit instruction set delivers the high performance expected of a 32-bit ARM core in a compact memory size usually associated with 8- and 16-bit devices, typically in the range of a few kilobytes of memory for microcontroller-class applications Single-cycle multiply instruction and hardware divide Atomic bit manipulation (bit-banding), delivering maximum memory utilization and streamlined peripheral control Unaligned data access, enabling data to be efficiently packed into memory IEEE754-compliant single-precision Floating-Point Unit (FPU) 16-bit SIMD vector processing unit Fast code execution permits slower processor clock or increases sleep mode time Harvard architecture characterized by separate buses for instruction and data Efficient processor core, system and memories Hardware division and fast digital-signal-processing orientated multiply accumulate Saturating arithmetic for signal processing Deterministic, high-performance interrupt handling for time-critical applications Memory protection unit (MPU) to provide a privileged mode for protected operating system functionality Enhanced system debug with extensive breakpoint and trace capabilities Serial Wire Debug and Serial Wire Trace reduce the number of pins required for debugging and tracing Migration from the ARM7 processor family for better performance and power efficiency Optimized for single-cycle Flash memory usage Ultra-low power consumption with integrated sleep modes
65
The Stellaris family of microcontrollers builds on this core to bring high-performance 32-bit computing to cost-sensitive embedded microcontroller applications, such as factory automation and control, industrial control power devices, building and home automation, and stepper motor control. This chapter provides information on the Stellaris implementation of the Cortex-M4F processor, including the programming model, the memory model, the exception model, fault handling, and power management. For technical details on the instruction set, see the ARM Cortex-M4 Technical Reference Manual.
2.1
Block Diagram
The Cortex-M4F processor is built on a high-performance processor core, with a 3-stage pipeline Harvard architecture, making it ideal for demanding embedded applications. The processor delivers exceptional power efficiency through an efficient instruction set and extensively optimized design, providing high-end processing hardware including IEEE754-compliant single-precision floating-point computation, a range of single-cycle and SIMD multiplication and multiply-with-accumulate capabilities, saturating arithmetic and dedicated hardware division. To facilitate the design of cost-sensitive devices, the Cortex-M4F processor implements tightly coupled system components that reduce processor area while significantly improving interrupt handling and system debug capabilities. The Cortex-M4F processor implements a version of the Thumb instruction set based on Thumb-2 technology, ensuring high code density and reduced program memory requirements. The Cortex-M4F instruction set provides the exceptional performance expected of a modern 32-bit architecture, with the high code density of 8-bit and 16-bit microcontrollers. The Cortex-M4F processor closely integrates a nested interrupt controller (NVIC), to deliver industry-leading interrupt performance. The Stellaris NVIC includes a non-maskable interrupt (NMI) and provides eight interrupt priority levels. The tight integration of the processor core and NVIC provides fast execution of interrupt service routines (ISRs), dramatically reducing interrupt latency. The hardware stacking of registers and the ability to suspend load-multiple and store-multiple operations further reduce interrupt latency. Interrupt handlers do not require any assembler stubs which removes code overhead from the ISRs. Tail-chaining optimization also significantly reduces the overhead when switching from one ISR to another. To optimize low-power designs, the NVIC integrates with the sleep modes, including Deep-sleep mode, which enables the entire device to be rapidly powered down.
April 25, 2012
Figure 2-1. CPU Block Diagram

FPU CM4 Core Instructions Memory Protection Unit Data
Nested Vectored Interrupt Controller
Interrupts Sleep Debug
ARM Cortex-M4F
Embedded Trace Macrocell
Trace Port Interface Unit
Serial Wire Output Trace Port (SWO)
Flash Patch and Breakpoint
Instrumentation Data Watchpoint Trace Macrocell and Trace ROM Table Adv. Peripheral Bus Bus Matrix I-code bus D-code bus System bus
Private Peripheral Bus (internal)
Serial Wire JTAG Debug Port
Debug Access Port
2.2
2.2.1
Overview
System-Level Interface
The Cortex-M4F processor provides multiple interfaces using AMBA technology to provide high-speed, low-latency memory accesses. The core supports unaligned data accesses and implements atomic bit manipulation that enables faster peripheral controls, system spinlocks, and thread-safe Boolean data handling. The Cortex-M4F processor has a memory protection unit (MPU) that provides fine-grain memory control, enabling applications to implement security privilege levels and separate code, data and stack on a task-by-task basis.
2.2.2
Integrated Configurable Debug

The Cortex-M4F processor implements a complete hardware debug solution, providing high system visibility of the processor and memory through either a traditional JTAG port or a 2-pin Serial Wire Debug (SWD) port that is ideal for microcontrollers and other small package devices. The Stellaris implementation replaces the ARM SW-DP and JTAG-DP with the ARM CoreSight-compliant Serial Wire JTAG Debug Port (SWJ-DP) interface. The SWJ-DP interface combines the SWD and JTAG debug ports into one module. See the ARM Debug Interface V5 Architecture Specification for details on SWJ-DP. For system trace, the processor integrates an Instrumentation Trace Macrocell (ITM) alongside data watchpoints and a profiling unit. To enable simple and cost-effective profiling of the system trace events, a Serial Wire Viewer (SWV) can export a stream of software-generated messages, data trace, and profiling information through a single pin.
67
The Embedded Trace Macrocell (ETM) delivers unrivaled instruction trace capture in an area smaller than traditional trace units, enabling full instruction trace. For more details on the ARM ETM, see the ARM Embedded Trace Macrocell Architecture Specification. The Flash Patch and Breakpoint Unit (FPB) provides up to eight hardware breakpoint comparators that debuggers can use. The comparators in the FPB also provide remap functions of up to eight words in the program code in the CODE memory region. This enables applications stored in a read-only area of Flash memory to be patched in another area of on-chip SRAM or Flash memory. If a patch is required, the application programs the FPB to remap a number of addresses. When those addresses are accessed, the accesses are redirected to a remap table specified in the FPB configuration. For more information on the Cortex-M4F debug capabilities, see theARM Debug Interface V5 Architecture Specification.
2.2.3
Trace Port Interface Unit (TPIU)

The TPIU acts as a bridge between the Cortex-M4F trace data from the ITM, and an off-chip Trace Port Analyzer, as shown in Figure 2-2 on page 68. Figure 2-2. TPIU Block Diagram
Debug ATB Slave Port
ATB Interface
Asynchronous FIFO
Trace Out (serializer)
Serial Wire Trace Port (SWO)
APB Slave Port
APB Interface
2.2.4
Cortex-M4F System Component Details

The Cortex-M4F includes the following system components: SysTick A 24-bit count-down timer that can be used as a Real-Time Operating System (RTOS) tick timer or as a simple counter (see System Timer (SysTick) on page 119). Nested Vectored Interrupt Controller (NVIC) An embedded interrupt controller that supports low latency interrupt processing (see Nested Vectored Interrupt Controller (NVIC) on page 120).
April 25, 2012
System Control Block (SCB) The programming model interface to the processor. The SCB provides system implementation information and system control, including configuration, control, and reporting of system exceptions (see System Control Block (SCB) on page 121). Memory Protection Unit (MPU) Improves system reliability by defining the memory attributes for different memory regions. The MPU provides up to eight different regions and an optional predefined background region (see Memory Protection Unit (MPU) on page 121). Floating-Point Unit (FPU) Fully supports single-precision add, subtract, multiply, divide, multiply and accumulate, and square-root operations. It also provides conversions between fixed-point and floating-point data formats, and floating-point constant instructions.
2.3
Programming Model
This section describes the Cortex-M4F programming model. In addition to the individual core register descriptions, information about the processor modes and privilege levels for software execution and stacks is included.
2.3.1
Processor Mode and Privilege Levels for Software Execution

The Cortex-M4F has two modes of operation: Thread mode Used to execute application software. The processor enters Thread mode when it comes out of reset. Handler mode Used to handle exceptions. When the processor has finished exception processing, it returns to Thread mode. In addition, the Cortex-M4F has two privilege levels: Unprivileged In this mode, software has the following restrictions: Limited access to the MSR and MRS instructions and no use of the CPS instruction No access to the system timer, NVIC, or system control block Possibly restricted access to memory or peripherals Privileged In this mode, software can use all the instructions and has access to all resources. In Thread mode, the CONTROL register (see page 84) controls whether software execution is privileged or unprivileged. In Handler mode, software execution is always privileged.
69
Only privileged software can write to the CONTROL register to change the privilege level for software execution in Thread mode. Unprivileged software can use the SVC instruction to make a supervisor call to transfer control to privileged software.
2.3.2
Stacks
The processor uses a full descending stack, meaning that the stack pointer indicates the last stacked item on the memory. When the processor pushes a new item onto the stack, it decrements the stack pointer and then writes the item to the new memory location. The processor implements two stacks: the main stack and the process stack, with a pointer for each held in independent registers (see the SP register on page 74). In Thread mode, the CONTROL register (see page 84) controls whether the processor uses the main stack or the process stack. In Handler mode, the processor always uses the main stack. The options for processor operations are shown in Table 2-1 on page 70. Table 2-1. Summary of Processor Mode, Privilege Level, and Stack Use
Processor Mode Thread Handler Use Applications Exception handlers Privilege Level Privileged or unprivileged Always privileged
a
Stack Used Main stack or process stack Main stack

a
a. See CONTROL (page 84).
2.3.3
Register Map
Figure 2-3 on page 71 shows the Cortex-M4F register set. Table 2-2 on page 71 lists the Core registers. The core registers are not memory mapped and are accessed by register name, so the base address is n/a (not applicable) and there is no offset.
April 25, 2012
Figure 2-3. Cortex-M4F Register Set

R0 R1 R2 Low registers R3 R4 R5 R6 R7 R8 R9 High registers R10 R11 R12 Stack Pointer Link Register Program Counter SP (R13) LR (R14) PC (R15) PSR PRIMASK FAULTMASK BASEPRI CONTROL CONTROL register Exception mask registers Special registers Program status register PSP MSP
General-purpose registers
Banked version of SP
Table 2-2. Processor Register Map

Offset Name R0 R1 R2 R3 R4 R5 R6 R7 R8 R9 R10 R11 Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset Description Cortex General-Purpose Register 0 Cortex General-Purpose Register 1 Cortex General-Purpose Register 2 Cortex General-Purpose Register 3 Cortex General-Purpose Register 4 Cortex General-Purpose Register 5 Cortex General-Purpose Register 6 Cortex General-Purpose Register 7 Cortex General-Purpose Register 8 Cortex General-Purpose Register 9 Cortex General-Purpose Register 10 Cortex General-Purpose Register 11 See page 73 73 73 73 73 73 73 73 73 73 73 73
71
Table 2-2. Processor Register Map (continued)

Offset Name R12 SP LR PC PSR PRIMASK FAULTMASK BASEPRI CONTROL FPSC Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset 0xFFFF.FFFF 0x0100.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description Cortex General-Purpose Register 12 Stack Pointer Link Register Program Counter Program Status Register Priority Mask Register Fault Mask Register Base Priority Mask Register Control Register Floating-Point Status Control See page 73 74 75 76 77 81 82 83 84 86
2.3.4
Register Descriptions
This section lists and describes the Cortex-M4F registers, in the order shown in Figure 2-3 on page 71. The core registers are not memory mapped and are accessed by register name rather than offset. Note: The register type shown in the register descriptions refers to type during program execution in Thread mode and Handler mode. Debug access can differ.
April 25, 2012
Register 1: Cortex General-Purpose Register 0 (R0) Register 2: Cortex General-Purpose Register 1 (R1) Register 3: Cortex General-Purpose Register 2 (R2) Register 4: Cortex General-Purpose Register 3 (R3) Register 5: Cortex General-Purpose Register 4 (R4) Register 6: Cortex General-Purpose Register 5 (R5) Register 7: Cortex General-Purpose Register 6 (R6) Register 8: Cortex General-Purpose Register 7 (R7) Register 9: Cortex General-Purpose Register 8 (R8) Register 10: Cortex General-Purpose Register 9 (R9) Register 11: Cortex General-Purpose Register 10 (R10) Register 12: Cortex General-Purpose Register 11 (R11) Register 13: Cortex General-Purpose Register 12 (R12)
The Rn registers are 32-bit general-purpose registers for data operations and can be accessed from either privileged or unprivileged mode.
Cortex General-Purpose Register 0 (R0)
Type R/W, reset 31 30 29 28 27 26 25 24 DATA Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 DATA Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name DATA
Type R/W
Reset -
Description Register data.
73
Register 14: Stack Pointer (SP)

The Stack Pointer (SP) is register R13. In Thread mode, the function of this register changes depending on the ASP bit in the Control Register (CONTROL) register. When the ASP bit is clear, this register is the Main Stack Pointer (MSP). When the ASP bit is set, this register is the Process Stack Pointer (PSP). On reset, the ASP bit is clear, and the processor loads the MSP with the value from address 0x0000.0000. The MSP can only be accessed in privileged mode; the PSP can be accessed in either privileged or unprivileged mode.
Stack Pointer (SP)
Type R/W, reset 31 30 29 28 27 26 25 24 SP Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 SP Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name SP
Type R/W
Reset -
Description This field is the address of the stack pointer.
April 25, 2012
Register 15: Link Register (LR)

The Link Register (LR) is register R14, and it stores the return information for subroutines, function calls, and exceptions. LR can be accessed from either privileged or unprivileged mode. EXC_RETURN is loaded into LR on exception entry. See Table 2-10 on page 107 for the values and description.
Link Register (LR)
Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 LINK Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 LINK Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name LINK
Type R/W
Reset
Description
0xFFFF.FFFF This field is the return address.
75
Register 16: Program Counter (PC)

The Program Counter (PC) is register R15, and it contains the current program address. On reset, the processor loads the PC with the value of the reset vector, which is at address 0x0000.0004. Bit 0 of the reset vector is loaded into the THUMB bit of the EPSR at reset and must be 1. The PC register can be accessed in either privileged or unprivileged mode.
Program Counter (PC)
Type R/W, reset 31 30 29 28 27 26 25 24 PC Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 PC Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name PC
Type R/W
Reset -
Description This field is the current program address.
April 25, 2012
Register 17: Program Status Register (PSR)

Note: This register is also referred to as xPSR. The Program Status Register (PSR) has three functions, and the register bits are assigned to the different functions: Application Program Status Register (APSR), bits 31:27, bits 19:16 Execution Program Status Register (EPSR), bits 26:24, 15:10 Interrupt Program Status Register (IPSR), bits 7:0 The PSR, IPSR, and EPSR registers can only be accessed in privileged mode; the APSR register can be accessed in either privileged or unprivileged mode. APSR contains the current state of the condition flags from previous instruction executions. EPSR contains the Thumb state bit and the execution state bits for the If-Then (IT) instruction or the Interruptible-Continuable Instruction (ICI) field for an interrupted load multiple or store multiple instruction. Attempts to read the EPSR directly through application software using the MSR instruction always return zero. Attempts to write the EPSR using the MSR instruction in application software are always ignored. Fault handlers can examine the EPSR value in the stacked PSR to determine the operation that faulted (see Exception Entry and Return on page 104). IPSR contains the exception type number of the current Interrupt Service Routine (ISR). These registers can be accessed individually or as a combination of any two or all three registers, using the register name as an argument to the MSR or MRS instructions. For example, all of the registers can be read using PSR with the MRS instruction, or APSR only can be written to using APSR with the MSR instruction. page 77 shows the possible register combinations for the PSR. See the MRS and MSR instruction descriptions in the Cortex-M3/M4 Instruction Set Technical User's Manual for more information about how to access the program status registers. Table 2-3. PSR Register Combinations
Register PSR IEPSR IAPSR EAPSR Type R/W RO R/W R/W
a b a, b
Combination APSR, EPSR, and IPSR EPSR and IPSR APSR and IPSR APSR and EPSR
a. The processor ignores writes to the IPSR bits. b. Reads of the EPSR bits return zero, and the processor ignores writes to these bits.
Program Status Register (PSR)

Type R/W, reset 0x0100.0000
31 N Type Reset R/W 0 15 30 Z R/W 0 14 29 C R/W 0 13 ICI / IT Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 28 V R/W 0 12 27 Q R/W 0 11 RO 0 10 26 ICI / IT RO 0 9 reserved RO 0 RO 0 RO 0 RO 0 RO 0 25 24 THUMB RO 1 8 RO 0 7 23 22 21 20 19 18 GE RO 0 4 ISRNUM RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 17 16
reserved RO 0 6 RO 0 5
77
Bit/Field 31
Name N
Type R/W
Reset 0
Description APSR Negative or Less Flag Value Description 1 0 The previous operation result was negative or less than. The previous operation result was positive, zero, greater than, or equal.
The value of this bit is only meaningful when accessing PSR or APSR. 30 Z R/W 0 APSR Zero Flag Value Description 1 0 The previous operation result was zero. The previous operation result was non-zero.
The value of this bit is only meaningful when accessing PSR or APSR. 29 C R/W 0 APSR Carry or Borrow Flag Value Description 1 0 The previous add operation resulted in a carry bit or the previous subtract operation did not result in a borrow bit. The previous add operation did not result in a carry bit or the previous subtract operation resulted in a borrow bit.
The value of this bit is only meaningful when accessing PSR or APSR. 28 V R/W 0 APSR Overflow Flag Value Description 1 0 The previous operation resulted in an overflow. The previous operation did not result in an overflow.
The value of this bit is only meaningful when accessing PSR or APSR. 27 Q R/W 0 APSR DSP Overflow and Saturation Flag Value Description 1 0 DSP Overflow or saturation has occurred. DSP overflow or saturation has not occurred since reset or since the bit was last cleared.
The value of this bit is only meaningful when accessing PSR or APSR. This bit is cleared by software using an MRS instruction.
April 25, 2012
Bit/Field 26:25
Name ICI / IT
Type RO
Reset 0x0
Description EPSR ICI / IT status These bits, along with bits 15:10, contain the Interruptible-Continuable Instruction (ICI) field for an interrupted load multiple or store multiple instruction or the execution state bits of the IT instruction. When EPSR holds the ICI execution state, bits 26:25 are zero. The If-Then block contains up to four instructions following an IT instruction. Each instruction in the block is conditional. The conditions for the instructions are either all the same, or some can be the inverse of others. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information. The value of this field is only meaningful when accessing PSR or EPSR.
24
THUMB
RO
EPSR Thumb State This bit indicates the Thumb state and should always be set. The following can clear the THUMB bit: The BLX, BX and POP{PC} instructions Restoration from the stacked xPSR value on an exception return Bit 0 of the vector value on an exception entry or reset
Attempting to execute instructions when this bit is clear results in a fault or lockup. See Lockup on page 109 for more information. The value of this bit is only meaningful when accessing PSR or EPSR. 23:20 reserved RO 0x00 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Greater Than or Equal Flags See the description of the SEL instruction in the Cortex-M3/M4 Instruction Set Technical User's Manual for more information. The value of this field is only meaningful when accessing PSR or APSR. 15:10 ICI / IT RO 0x0 EPSR ICI / IT status These bits, along with bits 26:25, contain the Interruptible-Continuable Instruction (ICI) field for an interrupted load multiple or store multiple instruction or the execution state bits of the IT instruction. When an interrupt occurs during the execution of an LDM, STM, PUSH POP, VLDM, VSTM, VPUSH, or VPOP instruction, the processor stops the load multiple or store multiple instruction operation temporarily and stores the next register operand in the multiple operation to bits 15:12. After servicing the interrupt, the processor returns to the register pointed to by bits 15:12 and resumes execution of the multiple load or store instruction. When EPSR holds the ICI execution state, bits 11:10 are zero. The If-Then block contains up to four instructions following a 16-bit IT instruction. Each instruction in the block is conditional. The conditions for the instructions are either all the same, or some can be the inverse of others. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information. The value of this field is only meaningful when accessing PSR or EPSR. 9:8 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
19:16
GE
R/W
0x0
79
Bit/Field 7:0
Name ISRNUM
Type RO
Reset 0x00
Description IPSR ISR Number This field contains the exception type number of the current Interrupt Service Routine (ISR). Value 0x00 0x01 0x02 0x03 0x04 0x05 0x06 Description Thread mode Reserved NMI Hard fault Memory management fault Bus fault Usage fault
0x07-0x0A Reserved 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 ... 0x9A SVCall Reserved for Debug Reserved PendSV SysTick Interrupt Vector 0 Interrupt Vector 1 ... Interrupt Vector 138
See Exception Types on page 98 for more information. The value of this field is only meaningful when accessing PSR or IPSR.
April 25, 2012
Register 18: Priority Mask Register (PRIMASK)

The PRIMASK register prevents activation of all exceptions with programmable priority. Reset, non-maskable interrupt (NMI), and hard fault are the only exceptions with fixed priority. Exceptions should be disabled when they might impact the timing of critical tasks. This register is only accessible in privileged mode. The MSR and MRS instructions are used to access the PRIMASK register, and the CPS instruction may be used to change the value of the PRIMASK register. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information on these instructions. For more information on exception priority levels, see Exception Types on page 98.
Priority Mask Register (PRIMASK)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 PRIMASK R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Priority Mask Value Description 1 0 Prevents the activation of all exceptions with configurable priority. No effect.
PRIMASK
R/W
81
Register 19: Fault Mask Register (FAULTMASK)

The FAULTMASK register prevents activation of all exceptions except for the Non-Maskable Interrupt (NMI). Exceptions should be disabled when they might impact the timing of critical tasks. This register is only accessible in privileged mode. The MSR and MRS instructions are used to access the FAULTMASK register, and the CPS instruction may be used to change the value of the FAULTMASK register. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information on these instructions. For more information on exception priority levels, see Exception Types on page 98.
Fault Mask Register (FAULTMASK)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0

FAULTMASK
R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Fault Mask Value Description 1 0 Prevents the activation of all exceptions except for NMI. No effect.
FAULTMASK
R/W
The processor clears the FAULTMASK bit on exit from any exception handler except the NMI handler.
April 25, 2012
Register 20: Base Priority Mask Register (BASEPRI)

The BASEPRI register defines the minimum priority for exception processing. When BASEPRI is set to a nonzero value, it prevents the activation of all exceptions with the same or lower priority level as the BASEPRI value. Exceptions should be disabled when they might impact the timing of critical tasks. This register is only accessible in privileged mode. For more information on exception priority levels, see Exception Types on page 98.
Base Priority Mask Register (BASEPRI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 BASEPRI RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 RO 0 RO 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Base Priority Any exception that has a programmable priority level with the same or lower priority as the value of this field is masked. The PRIMASK register can be used to mask all exceptions with programmable priority levels. Higher priority exceptions have lower priority levels. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 All exceptions are unmasked. All exceptions with priority level 1-7 are masked. All exceptions with priority level 2-7 are masked. All exceptions with priority level 3-7 are masked. All exceptions with priority level 4-7 are masked. All exceptions with priority level 5-7 are masked. All exceptions with priority level 6-7 are masked. All exceptions with priority level 7 are masked.
7:5
BASEPRI
R/W
0x0
4:0
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
83
Register 21: Control Register (CONTROL)

The CONTROL register controls the stack used and the privilege level for software execution when the processor is in Thread mode, and indicates whether the FPU state is active. This register is only accessible in privileged mode. Handler mode always uses MSP, so the processor ignores explicit writes to the ASP bit of the CONTROL register when in Handler mode. The exception entry and return mechanisms automatically update the CONTROL register based on the EXC_RETURN value (see Table 2-10 on page 107). In an OS environment, threads running in Thread mode should use the process stack and the kernel and exception handlers should use the main stack. By default, Thread mode uses MSP. To switch the stack pointer used in Thread mode to PSP, either use the MSR instruction to set the ASP bit, as detailed in the Cortex-M3/M4 Instruction Set Technical User's Manual, or perform an exception return to Thread mode with the appropriate EXC_RETURN value, as shown in Table 2-10 on page 107. Note: When changing the stack pointer, software must use an ISB instruction immediately after the MSR instruction, ensuring that instructions after the ISB execute use the new stack pointer. See the Cortex-M3/M4 Instruction Set Technical User's Manual.
Control Register (CONTROL)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 FPCA R/W 0 RO 0 1 ASP R/W 0 RO 0 0 TMPL R/W 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Floating-Point Context Active Value Description 1 0 Floating-point context active No floating-point context active
FPCA
R/W
The Cortex-M4F uses this bit to determine whether to preserve floating-point state when processing an exception.
Important:
Two bits control when FPCA can be enabled: the ASPEN bit in the Floating-Point Context Control (FPCC) register and the DISFPCA bit in the Auxiliary Control (ACTLR) register.
April 25, 2012
Bit/Field 1
Name ASP
Type R/W
Reset 0
Description Active Stack Pointer Value Description 1 0 PSP is the current stack pointer. MSP is the current stack pointer
In Handler mode, this bit reads as zero and ignores writes. The Cortex-M4F updates this bit automatically on exception return. 0 TMPL R/W 0 Thread Mode Privilege Level Value Description 1 0 Unprivileged software can be executed in Thread mode. Only privileged software can be executed in Thread mode.
85
Register 22: Floating-Point Status Control (FPSC)

The FPSC register provides all necessary user-level control of the floating-point system.
Floating-Point Status Control (FPSC)
Type R/W, reset 31 N Type Reset R/W 15 30 Z R/W 14 29 C R/W 13 28 V R/W 12 27
reserved
26 AHP R/W 10
25 DN R/W 9
24 FZ R/W 8
23 RMODE R/W 7 IDC
22
21
20
19
18
17
16
reserved RO 0 5 reserved RO 0 4 IXC R/W RO 0 3 UFC R/W RO 0 2 OFC R/W RO 0 1 DZC R/W RO 0 0 IOC R/W -
RO 0 11
R/W 6
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
R/W -
RO 0
RO 0
Bit/Field 31
Name N
Type R/W
Reset -
Description Negative Condition Code Flag Floating-point comparison operations update this condition code flag.
30
R/W
Zero Condition Code Flag Floating-point comparison operations update this condition code flag.
29
R/W
Carry Condition Code Flag Floating-point comparison operations update this condition code flag.
28
R/W
Overflow Condition Code Flag Floating-point comparison operations update this condition code flag.
27
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Alternative Half-Precision When set, alternative half-precision format is selected. When clear, IEEE half-precision format is selected. The AHP bit in the FPDSC register holds the default value for this bit.
26
AHP
R/W
25
DN
R/W
Default NaN Mode When set, any operation involving one or more NaNs returns the Default NaN. When clear, NaN operands propagate through to the output of a floating-point operation. The DN bit in the FPDSC register holds the default value for this bit.
24
FZ
R/W
Flush-to-Zero Mode When set, Flush-to-Zero mode is enabled. When clear, Flush-to-Zero mode is disabled and the behavior of the floating-point system is fully compliant with the IEEE 754 standard. The FZ bit in the FPDSC register holds the default value for this bit.
April 25, 2012
Bit/Field 23:22
Name RMODE
Type R/W
Reset -
Description Rounding Mode The specified rounding mode is used by almost all floating-point instructions. The RMODE bit in the FPDSC register holds the default value for this bit. Value Description 0x0 0x1 0x2 0x3 Round to Nearest (RN) mode Round towards Plus Infinity (RP) mode Round towards Minus Infinity (RM) mode Round towards Zero (RZ) mode
21:8
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Input Denormal Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
IDC
R/W
6:5
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Inexact Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
IXC
R/W
UFC
R/W
Underflow Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
OFC
R/W
Overflow Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
DZC
R/W
Division by Zero Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
IOC
R/W
Invalid Operation Cumulative Exception When set, indicates this exception has occurred since 0 was last written to this bit.
87
2.3.5
Exceptions and Interrupts

The Cortex-M4F processor supports interrupts and system exceptions. The processor and the Nested Vectored Interrupt Controller (NVIC) prioritize and handle all exceptions. An exception changes the normal flow of software control. The processor uses Handler mode to handle all exceptions except for reset. See Exception Entry and Return on page 104 for more information. The NVIC registers control interrupt handling. See Nested Vectored Interrupt Controller (NVIC) on page 120 for more information.
2.3.6
Data Types
The Cortex-M4F supports 32-bit words, 16-bit halfwords, and 8-bit bytes. The processor also supports 64-bit data transfer instructions. All instruction and data memory accesses are little endian. See Memory Regions, Types and Attributes on page 90 for more information.
2.4
Memory Model
This section describes the processor memory map, the behavior of memory accesses, and the bit-banding features. The processor has a fixed memory map that provides up to 4 GB of addressable memory. The memory map for the LM4F120H5QR controller is provided in Table 2-4 on page 88. In this manual, register addresses are given as a hexadecimal increment, relative to the modules base address as shown in the memory map. The regions for SRAM and peripherals include bit-band regions. Bit-banding provides atomic operations to bit data (see Bit-Banding on page 93). The processor reserves regions of the Private peripheral bus (PPB) address range for core peripheral registers (see Cortex-M4 Peripherals on page 118). Note: Within the memory map, all reserved space returns a bus fault when read or written.
Table 2-4. Memory Map

Start Memory 0x0000.0000 0x0004.0000 0x0100.0000 0x2000.0000 0x2000.8000 0x2200.0000 0x2210.0000 FiRM Peripherals 0x4000.0000 0x4000.1000 0x4000.2000 0x4000.4000 0x4000.5000 0x4000.6000 0x4000.0FFF 0x4000.1FFF 0x4000.3FFF 0x4000.4FFF 0x4000.5FFF 0x4000.6FFF Watchdog timer 0 Watchdog timer 1 Reserved GPIO Port A GPIO Port B GPIO Port C 759 759 643 643 643 0x0003.FFFF 0x00FF.FFFF 0x1FFF.FFFF 0x2000.7FFF 0x21FF.FFFF 0x220F.FFFF 0x3FFF.FFFF On-chip Flash Reserved Reserved for ROM Bit-banded on-chip SRAM Reserved Bit-band alias of bit-banded on-chip SRAM starting at 0x2000.0000 Reserved 525 512 511 511 End Description For details, see page ...
April 25, 2012
Table 2-4. Memory Map (continued)

Start 0x4000.7000 0x4000.8000 0x4000.9000 0x4000.A000 0x4000.B000 0x4000.C000 0x4000.D000 0x4000.E000 0x4000.F000 0x4001.0000 0x4001.1000 0x4001.2000 0x4001.3000 0x4001.4000 Peripherals 0x4002.0000 0x4002.1000 0x4002.2000 0x4002.3000 0x4002.4000 0x4002.5000 0x4002.6000 0x4003.0000 0x4003.1000 0x4003.2000 0x4003.3000 0x4003.4000 0x4003.5000 0x4003.6000 0x4003.7000 0x4003.8000 0x4003.9000 0x4003.A000 0x4003.C000 0x4003.D000 0x4004.0000 0x4004.1000 0x4004.C000 0x4004.D000 0x4004.E000 0x4004.F000 0x4002.0FFF 0x4002.1FFF 0x4002.2FFF 0x4002.3FFF 0x4002.4FFF 0x4002.5FFF 0x4002.FFFF 0x4003.0FFF 0x4003.1FFF 0x4003.2FFF 0x4003.3FFF 0x4003.4FFF 0x4003.5FFF 0x4003.6FFF 0x4003.7FFF 0x4003.8FFF 0x4003.9FFF 0x4003.BFFF 0x4003.CFFF 0x4003.FFFF 0x4004.0FFF 0x4004.BFFF 0x4004.CFFF 0x4004.DFFF 0x4004.EFFF 0x4004.FFFF I2C 0 I2C 1 I2C I2C 2 3 986 986 986 986 643 643 708 708 708 708 708 708 708 708 801 801 1121 1034 708 708 708 708 End 0x4000.7FFF 0x4000.8FFF 0x4000.9FFF 0x4000.AFFF 0x4000.BFFF 0x4000.CFFF 0x4000.DFFF 0x4000.EFFF 0x4000.FFFF 0x4001.0FFF 0x4001.1FFF 0x4001.2FFF 0x4001.3FFF 0x4001.FFFF Description GPIO Port D SSI0 SSI1 SSI2 SSI3 UART0 UART1 UART2 UART3 UART4 UART5 UART6 UART7 Reserved For details, see page ... 643 938 938 938 938 874 874 874 874 874 874 874 874 -
GPIO Port E GPIO Port F Reserved 16/32-bit Timer 0 16/32-bit Timer 1 16/32-bit Timer 2 16/32-bit Timer 3 16/32-bit Timer 4 16/32-bit Timer 5 32/64-bit Timer 0 32/64-bit Timer 1 ADC0 ADC1 Reserved Analog Comparators Reserved CAN0 Controller Reserved 32/64-bit Timer 2 32/64-bit Timer 3 32/64-bit Timer 4 32/64-bit Timer 5
89
Table 2-4. Memory Map (continued)

Start 0x4005.0000 0x4005.1000 0x4005.8000 0x4005.9000 0x4005.A000 0x4005.B000 0x4005.C000 0x4005.D000 0x4005.E000 0x400A.F000 0x400B.0000 0x400F.9000 0x400F.A000 0x400F.C000 0x400F.D000 0x400F.E000 0x400F.F000 0x4010.0000 0x4200.0000 0x4400.0000 Private Peripheral Bus 0xE000.0000 0xE000.1000 0xE000.2000 0xE000.3000 0xE000.E000 0xE000.F000 0xE004.0000 0xE004.1000 0xE004.2000 0xE000.0FFF 0xE000.1FFF 0xE000.2FFF 0xE000.DFFF 0xE000.EFFF 0xE003.FFFF 0xE004.0FFF 0xE004.1FFF 0xFFFF.FFFF Instrumentation Trace Macrocell (ITM) Data Watchpoint and Trace (DWT) Flash Patch and Breakpoint (FPB) Reserved 67 67 67 End 0x4005.0FFF 0x4005.7FFF 0x4005.8FFF 0x4005.9FFF 0x4005.AFFF 0x4005.BFFF 0x4005.CFFF 0x4005.DFFF 0x400A.EFFF 0x400A.FFFF 0x400F.8FFF 0x400F.9FFF 0x400F.BFFF 0x400F.CFFF 0x400F.DFFF 0x400F.EFFF 0x400F.FFFF 0x41FF.FFFF 0x43FF.FFFF 0xDFFF.FFFF Description USB Reserved GPIO Port A (AHB aperture) GPIO Port B (AHB aperture) GPIO Port C (AHB aperture) GPIO Port D (AHB aperture) GPIO Port E (AHB aperture) GPIO Port F (AHB aperture) Reserved EEPROM and Key Locker Reserved System Exception Module Reserved Hibernation Module Flash memory control System control DMA Reserved Bit-banded alias of 0x4000.0000 through 0x400F.FFFF Reserved For details, see page ... 1075 643 643 643 643 643 643 543 472 492 525 231 589 -
Cortex-M4F Peripherals (SysTick, NVIC, MPU, FPU and SCB) 130 Reserved Trace Port Interface Unit (TPIU) Embedded Trace Macrocell (ETM) Reserved 68 67 -
2.4.1
Memory Regions, Types and Attributes

The memory map and the programming of the MPU split the memory map into regions. Each region has a defined memory type, and some regions have additional memory attributes. The memory type and attributes determine the behavior of accesses to the region. The memory types are: Normal: The processor can re-order transactions for efficiency and perform speculative reads. Device: The processor preserves transaction order relative to other transactions to Device or Strongly Ordered memory. Strongly Ordered: The processor preserves transaction order relative to all other transactions.
April 25, 2012
The different ordering requirements for Device and Strongly Ordered memory mean that the memory system can buffer a write to Device memory but must not buffer a write to Strongly Ordered memory. An additional memory attribute is Execute Never (XN), which means the processor prevents instruction accesses. A fault exception is generated only on execution of an instruction executed from an XN region.
2.4.2
Memory System Ordering of Memory Accesses

For most memory accesses caused by explicit memory access instructions, the memory system does not guarantee that the order in which the accesses complete matches the program order of the instructions, providing the order does not affect the behavior of the instruction sequence. Normally, if correct program execution depends on two memory accesses completing in program order, software must insert a memory barrier instruction between the memory access instructions (see Software Ordering of Memory Accesses on page 92). However, the memory system does guarantee ordering of accesses to Device and Strongly Ordered memory. For two memory access instructions A1 and A2, if both A1 and A2 are accesses to either Device or Strongly Ordered memory, and if A1 occurs before A2 in program order, A1 is always observed before A2.
2.4.3
Behavior of Memory Accesses

Table 2-5 on page 91 shows the behavior of accesses to each region in the memory map. See Memory Regions, Types and Attributes on page 90 for more information on memory types and the XN attribute. Stellaris devices may have reserved memory areas within the address ranges shown below (refer to Table 2-4 on page 88 for more information). Table 2-5. Memory Access Behavior
Address Range Memory Region Memory Type Execute Never (XN) Description
0x0000.0000 - 0x1FFF.FFFF Code 0x2000.0000 - 0x3FFF.FFFF SRAM
Normal Normal
This executable region is for program code. Data can also be stored here. This executable region is for data. Code can also be stored here. This region includes bit band and bit band alias areas (see Table 2-6 on page 93). This region includes bit band and bit band alias areas (see Table 2-7 on page 93). This executable region is for data. This region is for external device memory. This region includes the NVIC, system timer, and system control block. -
0x4000.0000 - 0x5FFF.FFFF Peripheral 0x6000.0000 - 0x9FFF.FFFF External RAM 0xA000.0000 - 0xDFFF.FFFF External device 0xE000.0000- 0xE00F.FFFF Private peripheral bus 0xE010.0000- 0xFFFF.FFFF Reserved
Device Normal Device Strongly Ordered -
XN XN XN -
The Code, SRAM, and external RAM regions can hold programs. However, it is recommended that programs always use the Code region because the Cortex-M4F has separate buses that can perform instruction fetches and data accesses simultaneously. The MPU can override the default memory access behavior described in this section. For more information, see Memory Protection Unit (MPU) on page 121. The Cortex-M4F prefetches instructions ahead of execution and speculatively prefetches from branch target addresses.
91
2.4.4
Software Ordering of Memory Accesses

The order of instructions in the program flow does not always guarantee the order of the corresponding memory transactions for the following reasons: The processor can reorder some memory accesses to improve efficiency, providing this does not affect the behavior of the instruction sequence. The processor has multiple bus interfaces. Memory or devices in the memory map have different wait states. Some memory accesses are buffered or speculative. Memory System Ordering of Memory Accesses on page 91 describes the cases where the memory system guarantees the order of memory accesses. Otherwise, if the order of memory accesses is critical, software must include memory barrier instructions to force that ordering. The Cortex-M4F has the following memory barrier instructions: The Data Memory Barrier (DMB) instruction ensures that outstanding memory transactions complete before subsequent memory transactions. The Data Synchronization Barrier (DSB) instruction ensures that outstanding memory transactions complete before subsequent instructions execute. The Instruction Synchronization Barrier (ISB) instruction ensures that the effect of all completed memory transactions is recognizable by subsequent instructions. Memory barrier instructions can be used in the following situations: MPU programming If the MPU settings are changed and the change must be effective on the very next instruction, use a DSB instruction to ensure the effect of the MPU takes place immediately at the end of context switching. Use an ISB instruction to ensure the new MPU setting takes effect immediately after programming the MPU region or regions, if the MPU configuration code was accessed using a branch or call. If the MPU configuration code is entered using exception mechanisms, then an ISB instruction is not required. Vector table If the program changes an entry in the vector table and then enables the corresponding exception, use a DMB instruction between the operations. The DMB instruction ensures that if the exception is taken immediately after being enabled, the processor uses the new exception vector. Self-modifying code If a program contains self-modifying code, use an ISB instruction immediately after the code modification in the program. The ISB instruction ensures subsequent instruction execution uses the updated program. Memory map switching
April 25, 2012
If the system contains a memory map switching mechanism, use a DSB instruction after switching the memory map in the program. The DSB instruction ensures subsequent instruction execution uses the updated memory map. Dynamic exception priority change When an exception priority has to change when the exception is pending or active, use DSB instructions after the change. The change then takes effect on completion of the DSB instruction. Memory accesses to Strongly Ordered memory, such as the System Control Block, do not require the use of DMB instructions. For more information on the memory barrier instructions, see the Cortex-M3/M4 Instruction Set Technical User's Manual.
2.4.5
Bit-Banding
A bit-band region maps each word in a bit-band alias region to a single bit in the bit-band region. The bit-band regions occupy the lowest 1 MB of the SRAM and peripheral memory regions. Accesses to the 32-MB SRAM alias region map to the 1-MB SRAM bit-band region, as shown in Table 2-6 on page 93. Accesses to the 32-MB peripheral alias region map to the 1-MB peripheral bit-band region, as shown in Table 2-7 on page 93. For the specific address range of the bit-band regions, see Table 2-4 on page 88. Note: A word access to the SRAM or the peripheral bit-band alias region maps to a single bit in the SRAM or peripheral bit-band region. A word access to a bit band address results in a word access to the underlying memory, and similarly for halfword and byte accesses. This allows bit band accesses to match the access requirements of the underlying peripheral. Table 2-6. SRAM Memory Bit-Banding Regions
Address Range Memory Region Instruction and Data Accesses Direct accesses to this memory range behave as SRAM memory accesses, but this region is also bit addressable through bit-band alias. Data accesses to this region are remapped to bit band region. A write operation is performed as read-modify-write. Instruction accesses are not remapped. 0x2000.0000 - 0x200F.FFFF SRAM bit-band region
0x2200.0000 - 0x23FF.FFFF SRAM bit-band alias
Table 2-7. Peripheral Memory Bit-Banding Regions

Address Range Memory Region Instruction and Data Accesses Direct accesses to this memory range behave as peripheral memory accesses, but this region is also bit addressable through bit-band alias. Data accesses to this region are remapped to bit band region. A write operation is performed as read-modify-write. Instruction accesses are not permitted. 0x4000.0000 - 0x400F.FFFF Peripheral bit-band region
0x4200.0000 - 0x43FF.FFFF Peripheral bit-band alias
The following formula shows how the alias region maps onto the bit-band region: bit_word_offset = (byte_offset x 32) + (bit_number x 4) bit_word_addr = bit_band_base + bit_word_offset
93
where: bit_word_offset The position of the target bit in the bit-band memory region. bit_word_addr The address of the word in the alias memory region that maps to the targeted bit. bit_band_base The starting address of the alias region. byte_offset The number of the byte in the bit-band region that contains the targeted bit. bit_number The bit position, 0-7, of the targeted bit. Figure 2-4 on page 95 shows examples of bit-band mapping between the SRAM bit-band alias region and the SRAM bit-band region: The alias word at 0x23FF.FFE0 maps to bit 0 of the bit-band byte at 0x200F.FFFF: 0x23FF.FFE0 = 0x2200.0000 + (0x000F.FFFF*32) + (0*4) The alias word at 0x23FF.FFFC maps to bit 7 of the bit-band byte at 0x200F.FFFF: 0x23FF.FFFC = 0x2200.0000 + (0x000F.FFFF*32) + (7*4) The alias word at 0x2200.0000 maps to bit 0 of the bit-band byte at 0x2000.0000: 0x2200.0000 = 0x2200.0000 + (0*32) + (0*4) The alias word at 0x2200.001C maps to bit 7 of the bit-band byte at 0x2000.0000: 0x2200.001C = 0x2200.0000+ (0*32) + (7*4)
April 25, 2012
Figure 2-4. Bit-Band Mapping

32-MB Alias Region
0x23FF.FFFC 0x23FF.FFF8 0x23FF.FFF4 0x23FF.FFF0 0x23FF.FFEC 0x23FF.FFE8 0x23FF.FFE4 0x23FF.FFE0
0x2200.001C
0x2200.0018
0x2200.0014
0x2200.0010
0x2200.000C
0x2200.0008
0x2200.0004
0x2200.0000
1-MB SRAM Bit-Band Region

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
0x200F.FFFF
0x200F.FFFE
0x200F.FFFD
0x200F.FFFC
0x2000.0003
0x2000.0002
0x2000.0001
0x2000.0000
2.4.5.1
Directly Accessing an Alias Region

Writing to a word in the alias region updates a single bit in the bit-band region. Bit 0 of the value written to a word in the alias region determines the value written to the targeted bit in the bit-band region. Writing a value with bit 0 set writes a 1 to the bit-band bit, and writing a value with bit 0 clear writes a 0 to the bit-band bit. Bits 31:1 of the alias word have no effect on the bit-band bit. Writing 0x01 has the same effect as writing 0xFF. Writing 0x00 has the same effect as writing 0x0E. When reading a word in the alias region, 0x0000.0000 indicates that the targeted bit in the bit-band region is clear and 0x0000.0001 indicates that the targeted bit in the bit-band region is set.
2.4.5.2
Directly Accessing a Bit-Band Region

Behavior of Memory Accesses on page 91 describes the behavior of direct byte, halfword, or word accesses to the bit-band regions.
2.4.6
Data Storage
The processor views memory as a linear collection of bytes numbered in ascending order from zero. For example, bytes 0-3 hold the first stored word, and bytes 4-7 hold the second stored word. Data is stored in little-endian format, with the least-significant byte (lsbyte) of a word stored at the lowest-numbered byte, and the most-significant byte (msbyte) stored at the highest-numbered byte. Figure 2-5 on page 96 illustrates how data is stored.
95
Figure 2-5. Data Storage

Memory 7 0 31 Address A A+1 A+2 A+3 B0 B1 B2 B3 msbyte lsbyte B3 24 23 B2 16 15 B1 8 7 B0 0 Register
2.4.7
Synchronization Primitives
The Cortex-M4F instruction set includes pairs of synchronization primitives which provide a non-blocking mechanism that a thread or process can use to obtain exclusive access to a memory location. Software can use these primitives to perform a guaranteed read-modify-write memory update sequence or for a semaphore mechanism. A pair of synchronization primitives consists of: A Load-Exclusive instruction, which is used to read the value of a memory location and requests exclusive access to that location. A Store-Exclusive instruction, which is used to attempt to write to the same memory location and returns a status bit to a register. If this status bit is clear, it indicates that the thread or process gained exclusive access to the memory and the write succeeds; if this status bit is set, it indicates that the thread or process did not gain exclusive access to the memory and no write was performed. The pairs of Load-Exclusive and Store-Exclusive instructions are: The word instructions LDREX and STREX The halfword instructions LDREXH and STREXH The byte instructions LDREXB and STREXB Software must use a Load-Exclusive instruction with the corresponding Store-Exclusive instruction. To perform an exclusive read-modify-write of a memory location, software must: 1. Use a Load-Exclusive instruction to read the value of the location. 2. Modify the value, as required. 3. Use a Store-Exclusive instruction to attempt to write the new value back to the memory location. 4. Test the returned status bit. If the status bit is clear, the read-modify-write completed successfully. If the status bit is set, no write was performed, which indicates that the value returned at step 1 might be out of date. The software must retry the entire read-modify-write sequence. Software can use the synchronization primitives to implement a semaphore as follows:
April 25, 2012
1. Use a Load-Exclusive instruction to read from the semaphore address to check whether the semaphore is free. 2. If the semaphore is free, use a Store-Exclusive to write the claim value to the semaphore address. 3. If the returned status bit from step 2 indicates that the Store-Exclusive succeeded, then the software has claimed the semaphore. However, if the Store-Exclusive failed, another process might have claimed the semaphore after the software performed step 1. The Cortex-M4F includes an exclusive access monitor that tags the fact that the processor has executed a Load-Exclusive instruction. The processor removes its exclusive access tag if: It executes a CLREX instruction. It executes a Store-Exclusive instruction, regardless of whether the write succeeds. An exception occurs, which means the processor can resolve semaphore conflicts between different threads. For more information about the synchronization primitive instructions, see the Cortex-M3/M4 Instruction Set Technical User's Manual.
2.5
Exception Model
The ARM Cortex-M4F processor and the Nested Vectored Interrupt Controller (NVIC) prioritize and handle all exceptions in Handler Mode. The processor state is automatically stored to the stack on an exception and automatically restored from the stack at the end of the Interrupt Service Routine (ISR). The vector is fetched in parallel to the state saving, enabling efficient interrupt entry. The processor supports tail-chaining, which enables back-to-back interrupts to be performed without the overhead of state saving and restoration. Table 2-8 on page 99 lists all exception types. Software can set eight priority levels on seven of these exceptions (system handlers) as well as on 65 interrupts (listed in Table 2-9 on page 100). Priorities on the system handlers are set with the NVIC System Handler Priority n (SYSPRIn) registers. Interrupts are enabled through the NVIC Interrupt Set Enable n (ENn) register and prioritized with the NVIC Interrupt Priority n (PRIn) registers. Priorities can be grouped by splitting priority levels into preemption priorities and subpriorities. All the interrupt registers are described in Nested Vectored Interrupt Controller (NVIC) on page 120. Internally, the highest user-programmable priority (0) is treated as fourth priority, after a Reset, Non-Maskable Interrupt (NMI), and a Hard Fault, in that order. Note that 0 is the default priority for all the programmable priorities. Important: After a write to clear an interrupt source, it may take several processor cycles for the NVIC to see the interrupt source de-assert. Thus if the interrupt clear is done as the last action in an interrupt handler, it is possible for the interrupt handler to complete while the NVIC sees the interrupt as still asserted, causing the interrupt handler to be re-entered errantly. This situation can be avoided by either clearing the interrupt source at the beginning of the interrupt handler or by performing a read or write after the write to clear the interrupt source (and flush the write buffer). See Nested Vectored Interrupt Controller (NVIC) on page 120 for more information on exceptions and interrupts.
97
2.5.1
Exception States
Each exception is in one of the following states: Inactive. The exception is not active and not pending. Pending. The exception is waiting to be serviced by the processor. An interrupt request from a peripheral or from software can change the state of the corresponding interrupt to pending. Active. An exception that is being serviced by the processor but has not completed. Note: An exception handler can interrupt the execution of another exception handler. In this case, both exceptions are in the active state.
Active and Pending. The exception is being serviced by the processor, and there is a pending exception from the same source.
2.5.2
Exception Types
The exception types are: Reset. Reset is invoked on power up or a warm reset. The exception model treats reset as a special form of exception. When reset is asserted, the operation of the processor stops, potentially at any point in an instruction. When reset is deasserted, execution restarts from the address provided by the reset entry in the vector table. Execution restarts as privileged execution in Thread mode. NMI. A non-maskable Interrupt (NMI) can be signaled using the NMI signal or triggered by software using the Interrupt Control and State (INTCTRL) register. This exception has the highest priority other than reset. NMI is permanently enabled and has a fixed priority of -2. NMIs cannot be masked or prevented from activation by any other exception or preempted by any exception other than reset. Hard Fault. A hard fault is an exception that occurs because of an error during exception processing, or because an exception cannot be managed by any other exception mechanism. Hard faults have a fixed priority of -1, meaning they have higher priority than any exception with configurable priority. Memory Management Fault. A memory management fault is an exception that occurs because of a memory protection related fault, including access violation and no match. The MPU or the fixed memory protection constraints determine this fault, for both instruction and data memory transactions. This fault is used to abort instruction accesses to Execute Never (XN) memory regions, even if the MPU is disabled. Bus Fault. A bus fault is an exception that occurs because of a memory-related fault for an instruction or data memory transaction such as a prefetch fault or a memory access fault. This fault can be enabled or disabled. Usage Fault. A usage fault is an exception that occurs because of a fault related to instruction execution, such as: An undefined instruction An illegal unaligned access Invalid state on instruction execution
April 25, 2012
An error on exception return An unaligned address on a word or halfword memory access or division by zero can cause a usage fault when the core is properly configured. SVCall. A supervisor call (SVC) is an exception that is triggered by the SVC instruction. In an OS environment, applications can use SVC instructions to access OS kernel functions and device drivers. Debug Monitor. This exception is caused by the debug monitor (when not halting). This exception is only active when enabled. This exception does not activate if it is a lower priority than the current activation. PendSV. PendSV is a pendable, interrupt-driven request for system-level service. In an OS environment, use PendSV for context switching when no other exception is active. PendSV is triggered using the Interrupt Control and State (INTCTRL) register. SysTick. A SysTick exception is an exception that the system timer generates when it reaches zero when it is enabled to generate an interrupt. Software can also generate a SysTick exception using the Interrupt Control and State (INTCTRL) register. In an OS environment, the processor can use this exception as system tick. Interrupt (IRQ). An interrupt, or IRQ, is an exception signaled by a peripheral or generated by a software request and fed through the NVIC (prioritized). All interrupts are asynchronous to instruction execution. In the system, peripherals use interrupts to communicate with the processor. Table 2-9 on page 100 lists the interrupts on the LM4F120H5QR controller. For an asynchronous exception, other than reset, the processor can execute another instruction between when the exception is triggered and when the processor enters the exception handler. Privileged software can disable the exceptions that Table 2-8 on page 99 shows as having configurable priority (see the SYSHNDCTRL register on page 169 and the DIS0 register on page 140). For more information about hard faults, memory management faults, bus faults, and usage faults, see Fault Handling on page 107. Table 2-8. Exception Types
Exception Type Reset Non-Maskable Interrupt (NMI) Hard Fault Memory Management Bus Fault Usage Fault SVCall Debug Monitor Vector Number 0 1 2 3 4 5 6 7-10 11 12 13 Priority -3 (highest) -2 -1 programmable programmable programmable programmable programmable c c c c a
Vector Address or b Offset 0x0000.0000 0x0000.0004 0x0000.0008 0x0000.000C 0x0000.0010 0x0000.0014 0x0000.0018 0x0000.002C 0x0000.0030 -
Activation Stack top is loaded from the first entry of the vector table on reset. Asynchronous Asynchronous Synchronous Synchronous when precise and asynchronous when imprecise Synchronous Reserved Synchronous Synchronous Reserved
99
Table 2-8. Exception Types (continued)

Exception Type PendSV SysTick Interrupts Vector Number 14 15 16 and above Priority
a
Vector Address or b Offset

c c
Activation Asynchronous Asynchronous
programmable programmable programmable
0x0000.0038 0x0000.003C
0x0000.0040 and above Asynchronous
a. 0 is the default priority for all the programmable priorities. b. See Vector Table on page 102. c. See SYSPRI1 on page 166. d. See PRIn registers on page 148.
Table 2-9. Interrupts

Vector Number 0-15 16 17 18 19 20 21 22 23 24 25-29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47-48 49 Interrupt Number (Bit in Interrupt Registers) 0 1 2 3 4 5 6 7 8 9-13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31-32 33 Vector Address or Offset 0x0000.0000 0x0000.003C 0x0000.0040 0x0000.0044 0x0000.0048 0x0000.004C 0x0000.0050 0x0000.0054 0x0000.0058 0x0000.005C 0x0000.0060 0x0000.0078 0x0000.007C 0x0000.0080 0x0000.0084 0x0000.0088 0x0000.008C 0x0000.0090 0x0000.0094 0x0000.0098 0x0000.009C 0x0000.00A0 0x0000.00A4 0x0000.00A8 0x0000.00B0 0x0000.00B4 0x0000.00B8 0x0000.00C4 Description Processor exceptions GPIO Port A GPIO Port B GPIO Port C GPIO Port D GPIO Port E UART0 UART1 SSI0 I2C0 Reserved ADC0 Sequence 0 ADC0 Sequence 1 ADC0 Sequence 2 ADC0 Sequence 3 Watchdog Timers 0 and 1 16/32-Bit Timer 0A 16/32-Bit Timer 0B 16/32-Bit Timer 1A 16/32-Bit Timer 1B 16/32-Bit Timer 2A 16/32-Bit Timer 2B Analog Comparator 0 Analog Comparator 1 Reserved System Control Flash Memory Control and EEPROM Control GPIO Port F Reserved UART2
April 25, 2012
Table 2-9. Interrupts (continued)

Vector Number 50 51 52 53 54 55 56-58 59 60 61 62 63 64 65 66 67 68-72 73 74 75 76 77 78 79 80-83 84 85 86 87 88-107 108 109 110 111 112 113 114 115 116 117 Interrupt Number (Bit in Interrupt Registers) 34 35 36 37 38 39 40-42 43 44 45 46 47 48 49 50 51 52-56 57 58 59 60 61 62 63 64-67 68 69 70 71 72-91 92 93 94 95 96 97 98 99 100 101 Vector Address or Offset 0x0000.00C8 0x0000.00CC 0x0000.00D0 0x0000.00D4 0x0000.00DC 0x0000.00EC 0x0000.00F0 0x0000.00F8 0x0000.00FC 0x0000.0100 0x0000.0104 0x0000.0108 0x0000.010C 0x0000.0124 0x0000.0128 0x0000.012C 0x0000.0130 0x0000.0134 0x0000.0138 0x0000.013C 0x0000.0140 0x0000.014C 0x0000.0150 0x0000.0154 0x0000.0158 0x0000.015C 0x0000.0160 0x0000.01AC 0x0000.01B0 0x0000.01B4 0x0000.01B8 0x0000.01BC 0x0000.01C0 0x0000.01C4 0x0000.01C8 0x0000.01CC 0x0000.01D0 0x0000.01D4 Description SSI1 16/32-Bit Timer 3A 16/32-Bit Timer 3B I2C1 Reserved CAN0 Reserved Hibernation Module USB Reserved DMA Software DMA Error ADC1 Sequence 0 ADC1 Sequence 1 ADC1 Sequence 2 ADC1 Sequence 3 Reserved SSI2 SSI3 UART3 UART4 UART5 UART6 UART7 Reserved I2C2 I2C3 16/32-Bit Timer 4A 16/32-Bit Timer 4B Reserved 16/32-Bit Timer 5A 16/32-Bit Timer 5B 32/64-Bit Timer 0A 32/64-Bit Timer 0B 32/64-Bit Timer 1A 32/64-Bit Timer 1B 32/64-Bit Timer 2A 32/64-Bit Timer 2B 32/64-Bit Timer 3A 32/64-Bit Timer 3B
101
Table 2-9. Interrupts (continued)

Vector Number 118 119 120 121 122 123-154 Interrupt Number (Bit in Interrupt Registers) 102 103 104 105 106 107-138 Vector Address or Offset 0x0000.01D8 0x0000.01DC 0x0000.01E0 0x0000.01E4 0x0000.01E8 Description 32/64-Bit Timer 4A 32/64-Bit Timer 4B 32/64-Bit Timer 5A 32/64-Bit Timer 5B System Exception (imprecise) Reserved
2.5.3
Exception Handlers
The processor handles exceptions using: Interrupt Service Routines (ISRs). Interrupts (IRQx) are the exceptions handled by ISRs. Fault Handlers. Hard fault, memory management fault, usage fault, and bus fault are fault exceptions handled by the fault handlers. System Handlers. NMI, PendSV, SVCall, SysTick, and the fault exceptions are all system exceptions that are handled by system handlers.
2.5.4
Vector Table
The vector table contains the reset value of the stack pointer and the start addresses, also called exception vectors, for all exception handlers. The vector table is constructed using the vector address or offset shown in Table 2-8 on page 99. Figure 2-6 on page 103 shows the order of the exception vectors in the vector table. The least-significant bit of each vector must be 1, indicating that the exception handler is Thumb code
April 25, 2012
Figure 2-6. Vector Table

Exception number IRQ number 154 . . . 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 -10 -11 -12 -13 -14 0x0018 0x0014 0x0010 0x000C 0x0008 0x0004 0x0000 Usage fault Bus fault Memory management fault Hard fault NMI Reset Initial SP value -5 0x002C 2 1 0 -1 -2 138 Offset 0x0268 . . . 0x004C 0x0048 0x0044 0x0040 0x003C 0x0038 Vector IRQ131 . . . IRQ2 IRQ1 IRQ0 Systick PendSV Reserved Reserved for Debug SVCall
Reserved
On system reset, the vector table is fixed at address 0x0000.0000. Privileged software can write to the Vector Table Offset (VTABLE) register to relocate the vector table start address to a different memory location, in the range 0x0000.0400 to 0x3FFF.FC00 (see Vector Table on page 102). Note that when configuring the VTABLE register, the offset must be aligned on a 1024-byte boundary.
2.5.5
Exception Priorities
As Table 2-8 on page 99 shows, all exceptions have an associated priority, with a lower priority value indicating a higher priority and configurable priorities for all exceptions except Reset, Hard fault, and NMI. If software does not configure any priorities, then all exceptions with a configurable priority have a priority of 0. For information about configuring exception priorities, see page 166 and page 148. Note: Configurable priority values for the Stellaris implementation are in the range 0-7. This means that the Reset, Hard fault, and NMI exceptions, with fixed negative priority values, always have higher priority than any other exception.
For example, assigning a higher priority value to IRQ[0] and a lower priority value to IRQ[1] means that IRQ[1] has higher priority than IRQ[0]. If both IRQ[1] and IRQ[0] are asserted, IRQ[1] is processed before IRQ[0].
103
If multiple pending exceptions have the same priority, the pending exception with the lowest exception number takes precedence. For example, if both IRQ[0] and IRQ[1] are pending and have the same priority, then IRQ[0] is processed before IRQ[1]. When the processor is executing an exception handler, the exception handler is preempted if a higher priority exception occurs. If an exception occurs with the same priority as the exception being handled, the handler is not preempted, irrespective of the exception number. However, the status of the new interrupt changes to pending.
2.5.6
Interrupt Priority Grouping

To increase priority control in systems with interrupts, the NVIC supports priority grouping. This grouping divides each interrupt priority register entry into two fields: An upper field that defines the group priority A lower field that defines a subpriority within the group Only the group priority determines preemption of interrupt exceptions. When the processor is executing an interrupt exception handler, another interrupt with the same group priority as the interrupt being handled does not preempt the handler. If multiple pending interrupts have the same group priority, the subpriority field determines the order in which they are processed. If multiple pending interrupts have the same group priority and subpriority, the interrupt with the lowest IRQ number is processed first. For information about splitting the interrupt priority fields into group priority and subpriority, see page 160.
2.5.7
Exception Entry and Return

Descriptions of exception handling use the following terms: Preemption. When the processor is executing an exception handler, an exception can preempt the exception handler if its priority is higher than the priority of the exception being handled. See Interrupt Priority Grouping on page 104 for more information about preemption by an interrupt. When one exception preempts another, the exceptions are called nested exceptions. See Exception Entry on page 105 more information. Return. Return occurs when the exception handler is completed, and there is no pending exception with sufficient priority to be serviced and the completed exception handler was not handling a late-arriving exception. The processor pops the stack and restores the processor state to the state it had before the interrupt occurred. See Exception Return on page 106 for more information. Tail-Chaining. This mechanism speeds up exception servicing. On completion of an exception handler, if there is a pending exception that meets the requirements for exception entry, the stack pop is skipped and control transfers to the new exception handler. Late-Arriving. This mechanism speeds up preemption. If a higher priority exception occurs during state saving for a previous exception, the processor switches to handle the higher priority exception and initiates the vector fetch for that exception. State saving is not affected by late arrival because the state saved is the same for both exceptions. Therefore, the state saving continues uninterrupted. The processor can accept a late arriving exception until the first instruction of the exception handler of the original exception enters the execute stage of the processor. On
April 25, 2012
return from the exception handler of the late-arriving exception, the normal tail-chaining rules apply.
2.5.7.1
Exception Entry
Exception entry occurs when there is a pending exception with sufficient priority and either the processor is in Thread mode or the new exception is of higher priority than the exception being handled, in which case the new exception preempts the original exception. When one exception preempts another, the exceptions are nested. Sufficient priority means the exception has more priority than any limits set by the mask registers (see PRIMASK on page 81, FAULTMASK on page 82, and BASEPRI on page 83). An exception with less priority than this is pending but is not handled by the processor. When the processor takes an exception, unless the exception is a tail-chained or a late-arriving exception, the processor pushes information onto the current stack. This operation is referred to as stacking and the structure of eight data words is referred to as stack frame. When using floating-point routines, the Cortex-M4F processor automatically stacks the architected floating-point state on exception entry. Figure 2-7 on page 106 shows the Cortex-M4F stack frame layout when floating-point state is preserved on the stack as the result of an interrupt or an exception. Note: Where stack space for floating-point state is not allocated, the stack frame is the same as that of ARMv7-M implementations without an FPU. Figure 2-7 on page 106 shows this stack frame also.
105
Figure 2-7. Exception Stack Frame

... {aligner} FPSCR S15 S14 S13 S12 S11 S10 S9 S8 S7 S6 S5 S4 S3 S2 S1 S0 xPSR PC LR R12 R3 R2 R1 R0 Exception frame with floating-point storage Pre-IRQ top of stack
Decreasing memory address
IRQ top of stack
... {aligner} xPSR PC LR R12 R3 R2 R1 R0 Exception frame without floating-point storage
Pre-IRQ top of stack
IRQ top of stack
Immediately after stacking, the stack pointer indicates the lowest address in the stack frame. The stack frame includes the return address, which is the address of the next instruction in the interrupted program. This value is restored to the PC at exception return so that the interrupted program resumes. In parallel to the stacking operation, the processor performs a vector fetch that reads the exception handler start address from the vector table. When stacking is complete, the processor starts executing the exception handler. At the same time, the processor writes an EXC_RETURN value to the LR, indicating which stack pointer corresponds to the stack frame and what operation mode the processor was in before the entry occurred. If no higher-priority exception occurs during exception entry, the processor starts executing the exception handler and automatically changes the status of the corresponding pending interrupt to active. If another higher-priority exception occurs during exception entry, known as late arrival, the processor starts executing the exception handler for this exception and does not change the pending status of the earlier exception.
2.5.7.2
Exception Return
Exception return occurs when the processor is in Handler mode and executes one of the following instructions to load the EXC_RETURN value into the PC:
April 25, 2012
An LDM or POP instruction that loads the PC A BX instruction using any register An LDR instruction with the PC as the destination EXC_RETURN is the value loaded into the LR on exception entry. The exception mechanism relies on this value to detect when the processor has completed an exception handler. The lowest five bits of this value provide information on the return stack and processor mode. Table 2-10 on page 107 shows the EXC_RETURN values with a description of the exception return behavior. EXC_RETURN bits 31:5 are all set. When this value is loaded into the PC, it indicates to the processor that the exception is complete, and the processor initiates the appropriate exception return sequence. Table 2-10. Exception Return Behavior
EXC_RETURN[31:0] 0xFFFF.FFE0 0xFFFF.FFE1 Description Reserved Return to Handler mode. Exception return uses floating-point state from MSP. Execution uses MSP after return. 0xFFFF.FFE2 - 0xFFFF.FFE8 0xFFFF.FFE9 Reserved Return to Thread mode. Exception return uses floating-point state from MSP. Execution uses MSP after return. 0xFFFF.FFEA - 0xFFFF.FFEC 0xFFFF.FFED Reserved Return to Thread mode. Exception return uses floating-point state from PSP. Execution uses PSP after return. 0xFFFF.FFEE - 0xFFFF.FFF0 0xFFFF.FFF1 Reserved Return to Handler mode. Exception return uses non-floating-point state from MSP. Execution uses MSP after return. 0xFFFF.FFF2 - 0xFFFF.FFF8 0xFFFF.FFF9 Reserved Return to Thread mode. Exception return uses non-floating-point state from MSP. Execution uses MSP after return. 0xFFFF.FFFA - 0xFFFF.FFFC 0xFFFF.FFFD Reserved Return to Thread mode. Exception return uses non-floating-point state from PSP. Execution uses PSP after return. 0xFFFF.FFFE - 0xFFFF.FFFF Reserved
2.6
Fault Handling
Faults are a subset of the exceptions (see Exception Model on page 97). The following conditions generate a fault: A bus error on an instruction fetch or vector table load or a data access.
107
An internally detected error such as an undefined instruction or an attempt to change state with a BX instruction. Attempting to execute an instruction from a memory region marked as Non-Executable (XN). An MPU fault because of a privilege violation or an attempt to access an unmanaged region.
2.6.1
Fault Types
Table 2-11 on page 108 shows the types of fault, the handler used for the fault, the corresponding fault status register, and the register bit that indicates the fault has occurred. See page 173 for more information about the fault status registers. Table 2-11. Faults
Fault Bus error on a vector read Fault escalated to a hard fault MPU or default memory mismatch on instruction access MPU or default memory mismatch on data access MPU or default memory mismatch on exception stacking MPU or default memory mismatch on exception unstacking MPU or default memory mismatch during lazy floating-point state preservation Bus error during exception stacking Handler Hard fault Hard fault Memory management fault Memory management fault Memory management fault Memory management fault Memory management fault Bus fault Fault Status Register Hard Fault Status (HFAULTSTAT) Hard Fault Status (HFAULTSTAT) Memory Management Fault Status (MFAULTSTAT) Memory Management Fault Status (MFAULTSTAT) Memory Management Fault Status (MFAULTSTAT) Memory Management Fault Status (MFAULTSTAT) Memory Management Fault Status (MFAULTSTAT) Bus Fault Status (BFAULTSTAT) Bus Fault Status (BFAULTSTAT) Bus Fault Status (BFAULTSTAT) Bus Fault Status (BFAULTSTAT) Bus Fault Status (BFAULTSTAT) Bus Fault Status (BFAULTSTAT) Usage Fault Status (UFAULTSTAT) Usage Fault Status (UFAULTSTAT) Usage Fault Status (UFAULTSTAT) Usage Fault Status (UFAULTSTAT) Usage Fault Status (UFAULTSTAT) Usage Fault Status (UFAULTSTAT) Bit Name VECT FORCED IERR DERR MSTKE MUSTKE MLSPERR
a
BSTKE BUSTKE IBUS BLSPE PRECISE IMPRE NOCP UNDEF INVSTAT INVPC UNALIGN DIV0
Bus error during exception unstacking Bus fault Bus error during instruction prefetch Bus fault
Bus error during lazy floating-point state Bus fault preservation Precise data bus error Imprecise data bus error Attempt to access a coprocessor Undefined instruction Attempt to enter an invalid instruction b set state Invalid EXC_RETURN value Illegal unaligned load or store Divide by 0 Bus fault Bus fault Usage fault Usage fault Usage fault Usage fault Usage fault Usage fault
a. Occurs on an access to an XN region even if the MPU is disabled. b. Attempting to use an instruction set other than the Thumb instruction set, or returning to a non load-store-multiple instruction with ICI continuation.
2.6.2
Fault Escalation and Hard Faults

All fault exceptions except for hard fault have configurable exception priority (see SYSPRI1 on page 166). Software can disable execution of the handlers for these faults (see SYSHNDCTRL on page 169).
April 25, 2012
Usually, the exception priority, together with the values of the exception mask registers, determines whether the processor enters the fault handler, and whether a fault handler can preempt another fault handler as described in Exception Model on page 97. In some situations, a fault with configurable priority is treated as a hard fault. This process is called priority escalation, and the fault is described as escalated to hard fault. Escalation to hard fault occurs when: A fault handler causes the same kind of fault as the one it is servicing. This escalation to hard fault occurs because a fault handler cannot preempt itself because it must have the same priority as the current priority level. A fault handler causes a fault with the same or lower priority as the fault it is servicing. This situation happens because the handler for the new fault cannot preempt the currently executing fault handler. An exception handler causes a fault for which the priority is the same as or lower than the currently executing exception. A fault occurs and the handler for that fault is not enabled. If a bus fault occurs during a stack push when entering a bus fault handler, the bus fault does not escalate to a hard fault. Thus if a corrupted stack causes a fault, the fault handler executes even though the stack push for the handler failed. The fault handler operates but the stack contents are corrupted. Note: Only Reset and NMI can preempt the fixed priority hard fault. A hard fault can preempt any exception other than Reset, NMI, or another hard fault.
2.6.3
Fault Status Registers and Fault Address Registers

The fault status registers indicate the cause of a fault. For bus faults and memory management faults, the fault address register indicates the address accessed by the operation that caused the fault, as shown in Table 2-12 on page 109. Table 2-12. Fault Status and Fault Address Registers
Handler Hard fault Status Register Name Hard Fault Status (HFAULTSTAT) Address Register Name Memory Management Fault Address (MMADDR) Bus Fault Address (FAULTADDR) Register Description page 179 page 173 page 180 page 173 page 181 page 173
Memory management Memory Management Fault Status fault (MFAULTSTAT) Bus fault Usage fault Bus Fault Status (BFAULTSTAT) Usage Fault Status (UFAULTSTAT)
2.6.4
Lockup
The processor enters a lockup state if a hard fault occurs when executing the NMI or hard fault handlers. When the processor is in the lockup state, it does not execute any instructions. The processor remains in lockup state until it is reset, an NMI occurs, or it is halted by a debugger. Note: If the lockup state occurs from the NMI handler, a subsequent NMI does not cause the processor to leave the lockup state.
109
2.7
Power Management
The Cortex-M4F processor sleep modes reduce power consumption: Sleep mode stops the processor clock. Deep-sleep mode stops the system clock and switches off the PLL and Flash memory. The SLEEPDEEP bit of the System Control (SYSCTRL) register selects which sleep mode is used (see page 162). For more information about the behavior of the sleep modes, see System Control on page 222. This section describes the mechanisms for entering sleep mode and the conditions for waking up from sleep mode, both of which apply to Sleep mode and Deep-sleep mode.
2.7.1
Entering Sleep Modes

This section describes the mechanisms software can use to put the processor into one of the sleep modes. The system can generate spurious wake-up events, for example a debug operation wakes up the processor. Therefore, software must be able to put the processor back into sleep mode after such an event. A program might have an idle loop to put the processor back to sleep mode.
2.7.1.1
Wait for Interrupt

The wait for interrupt instruction, WFI, causes immediate entry to sleep mode unless the wake-up condition is true (see Wake Up from WFI or Sleep-on-Exit on page 111). When the processor executes a WFI instruction, it stops executing instructions and enters sleep mode. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information.
2.7.1.2
Wait for Event

The wait for event instruction, WFE, causes entry to sleep mode conditional on the value of a one-bit event register. When the processor executes a WFE instruction, it checks the event register. If the register is 0, the processor stops executing instructions and enters sleep mode. If the register is 1, the processor clears the register and continues executing instructions without entering sleep mode. If the event register is 1, the processor must not enter sleep mode on execution of a WFE instruction. Typically, this situation occurs if an SEV instruction has been executed. Software cannot access this register directly. See the Cortex-M3/M4 Instruction Set Technical User's Manual for more information.
2.7.1.3
Sleep-on-Exit
If the SLEEPEXIT bit of the SYSCTRL register is set, when the processor completes the execution of all exception handlers, it returns to Thread mode and immediately enters sleep mode. This mechanism can be used in applications that only require the processor to run when an exception occurs.
2.7.2
Wake Up from Sleep Mode

The conditions for the processor to wake up depend on the mechanism that cause it to enter sleep mode.
April 25, 2012
2.7.2.1
Wake Up from WFI or Sleep-on-Exit

Normally, the processor wakes up only when the NVIC detects an exception with sufficient priority to cause exception entry. Some embedded systems might have to execute system restore tasks after the processor wakes up and before executing an interrupt handler. Entry to the interrupt handler can be delayed by setting the PRIMASK bit and clearing the FAULTMASK bit. If an interrupt arrives that is enabled and has a higher priority than current exception priority, the processor wakes up but does not execute the interrupt handler until the processor clears PRIMASK. For more information about PRIMASK and FAULTMASK, see page 81 and page 82.
2.7.2.2
Wake Up from WFE

The processor wakes up if it detects an exception with sufficient priority to cause exception entry. In addition, if the SEVONPEND bit in the SYSCTRL register is set, any new pending interrupt triggers an event and wakes up the processor, even if the interrupt is disabled or has insufficient priority to cause exception entry. For more information about SYSCTRL, see page 162.
2.7.3
The Wake-Up Interrupt Controller

The Wake-Up Interrupt Controller (WIC) is a peripheral that can detect an interrupt and wake the processor from deep sleep mode. The WIC is enabled only when the DEEPSLEEP bit in the SCR register is set (see page 162). The WIC is not programmable, and does not have any registers or user interface. It operates entirely from hardware signals. When the WIC is enabled and the processor enters deep sleep mode, the power management unit in the system can power down most of the Cortex-M4F processor. This has the side effect of stopping the SysTick timer. When the WIC receives an interrupt, it takes a number of clock cycles to wake up the processor and restore its state, before it can process the interrupt. This means interrupt latency is increased in deep sleep mode. Note: If the processor detects a connection to a debugger it disables the WIC.
2.8
Instruction Set Summary

The processor implements a version of the Thumb instruction set. Table 2-13 on page 111 lists the supported instructions. Note: In Table 2-13 on page 111: Angle brackets, <>, enclose alternative forms of the operand Braces, {}, enclose optional operands The Operands column is not exhaustive Op2 is a flexible second operand that can be either a register or a constant Most instructions can use an optional condition code suffix
For more information on the instructions and operands, see the instruction descriptions in the ARM Cortex-M4 Technical Reference Manual. Table 2-13. Cortex-M4F Instruction Summary
Mnemonic ADC, ADCS ADD, ADDS ADD, ADDW Operands {Rd,} Rn, Op2 {Rd,} Rn, Op2 {Rd,} Rn , #imm12 Brief Description Add with carry Add Add Flags N,Z,C,V N,Z,C,V -
111
Table 2-13. Cortex-M4F Instruction Summary (continued)

Mnemonic ADR AND, ANDS ASR, ASRS B BFC BFI BIC, BICS BKPT BL BLX BX CBNZ CBZ CLREX CLZ CMN CMP CPSID CPSIE DMB DSB EOR, EORS ISB IT LDM LDMDB, LDMEA LDMFD, LDMIA LDR LDRB, LDRBT LDRD LDREX LDREXB LDREXH LDRH, LDRHT LDRSB, LDRSBT LDRSH, LDRSHT LDRT LSL, LSLS LSR, LSRS Operands Rd, label {Rd,} Rn, Op2 Rd, Rm, <Rs|#n> label Rd, #lsb, #width Rd, Rn, #lsb, #width {Rd,} Rn, Op2 #imm label Rm Rm Rn, label Rn, label Rd, Rm Rn, Op2 Rn, Op2 i i {Rd,} Rn, Op2 Rn{!}, reglist Rn{!}, reglist Rn{!}, reglist Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, Rt2, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn] Rt, [Rn] Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn, #offset] Rd, Rm, <Rs|#n> Rd, Rm, <Rs|#n> Brief Description Load PC-relative address Logical AND Arithmetic shift right Branch Bit field clear Bit field insert Bit clear Breakpoint Branch with link Branch indirect with link Branch indirect Compare and branch if non-zero Compare and branch if zero Clear exclusive Count leading zeros Compare negative Compare Change processor state, disable interrupts Change processor state, enable interrupts Data memory barrier Data synchronization barrier Exclusive OR Instruction synchronization barrier If-Then condition block Flags N,Z,C N,Z,C N,Z,C N,Z,C,V N,Z,C,V N,Z,C -
Load multiple registers, increment after Load multiple registers, decrement before -
Load multiple registers, increment after Load register with word Load register with byte Load register with two bytes Load register exclusive Load register exclusive with byte Load register exclusive with halfword Load register with halfword Load register with signed byte Load register with signed halfword Load register with word Logical shift left Logical shift right N,Z,C N,Z,C
April 25, 2012

Mnemonic MLA MLS MOV, MOVS MOV, MOVW MOVT MRS MSR MUL, MULS MVN, MVNS NOP ORN, ORNS ORR, ORRS PKHTB, PKHBT POP PUSH QADD QADD16 QADD8 QASX QDADD QDSUB QSAX QSUB QSUB16 QSUB8 RBIT REV REV16 REVSH ROR, RORS RRX, RRXS RSB, RSBS SADD16 SADD8 SASX SBC, SBCS SBFX SDIV Operands Rd, Rn, Rm, Ra Rd, Rn, Rm, Ra Rd, Op2 Rd, #imm16 Rd, #imm16 Rd, spec_reg spec_reg, Rm {Rd,} Rn, Rm Rd, Op2 {Rd,} Rn, Op2 {Rd,} Rn, Op2 {Rd,} Rn, Rm, Op2 reglist reglist {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm Rd, Rn Rd, Rn Rd, Rn Rd, Rn Rd, Rm, <Rs|#n> Rd, Rm {Rd,} Rn, Op2 {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Op2 Rd, Rn, #lsb, #width {Rd,} Rn, Rm Brief Description Multiply with accumulate, 32-bit result Multiply and subtract, 32-bit result Move Move 16-bit constant Move top Move from special register to general register Move from general register to special register Multiply, 32-bit result Move NOT No operation Logical OR NOT Logical OR Pack halfword Pop registers from stack Push registers onto stack Saturating add Saturating add 16 Saturating add 8 Saturating add and subtract with exchange Saturating double and add Saturating double and subtract Saturating subtract and add with exchange Saturating subtract Saturating subtract 16 Saturating subtract 8 Reverse bits Reverse byte order in a word Reverse byte order in each halfword Reverse byte order in bottom halfword and sign extend Rotate right Rotate right with extend Reverse subtract Signed add 16 Signed add 8 Flags N,Z,C N,Z,C N,Z,C,V N,Z N,Z,C N,Z,C N,Z,C Q Q Q Q N,Z,C N,Z,C N,Z,C,V GE GE
Signed add and subtract with exchange GE Subtract with carry Signed bit field extract Signed divide N,Z,C,V -
113

Mnemonic SEL SEV SHADD16 SHADD8 SHASX SHSAX SHSUB16 SHSUB8 SMLABB, SMLABT, SMLATB, SMLATT SMLAD, SMLADX SMLAL SMLALBB, SMLALBT, SMLALTB, SMLALTT SMLALD, SMLALDX SMLAWB,SMLAWT SMLSD SMLSDX SMLSLD SMLSLDX SMMLA SMMLS, SMMLR SMMUL, SMMULR SMUAD SMUADX SMULBB, SMULBT, SMULTB, SMULTT SMULL SMULWB, SMULWT RdLo, RdHi, Rn, Rm {Rd,} Rn, Rm Signed multiply (32x32), 64-bit result Signed multiply by halfword {Rd,} Rn, Rm Signed multiply halfwords {Rd,} Rn, Rm Signed dual multiply add Q {Rd,} Rn, Rm Rd, Rn, Rm, Ra Rd, Rn, Rm, Ra Signed most significant word multiply accumulate Signed most significant word multiply subtract Signed most significant word multiply RdLo, RdHi, Rn, Rm Signed multiply subtract long dual RdLo, RdHi, Rn, Rm Rd, Rn, Rm, Ra Rd, Rn, Rm, Ra Signed multiply accumulate long dual Signed multiply accumulate, word by halfword Signed multiply subtract dual Q Q RdLo, RdHi, Rn, Rm RdLo, RdHi, Rn, Rm Signed multiply with accumulate (32x32+64), 64-bit result Signed multiply accumulate long (halfwords) Rd, Rn, Rm, Ra Signed multiply accumulate dual Q Operands {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm Rd, Rn, Rm, Ra Brief Description Select bytes Send event Signed halving add 16 Signed halving add 8 Signed halving add and subtract with exchange Signed halving add and subtract with exchange Signed halving subtract 16 Signed halving subtract 8 Signed multiply accumulate long (halfwords) Flags Q
April 25, 2012

Mnemonic SMUSD, SMUSDX SSAT SSAT16 SSAX SSUB16 SSUB8 STM STMDB, STMEA STMFD, STMIA STR STRB, STRBT STRD STREX STREXB STREXH STRH, STRHT STRSB, STRSBT STRSH, STRSHT STRT SUB, SUBS SUB, SUBW SVC SXTAB SXTAB16 SXTAH SXTB16 SXTB SXTH TBB TBH TEQ TST UADD16 UADD8 UASX UHADD16 UHADD8 UHASX Rd, #n, Rm {,shift #s} Rd, #n, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm Rn{!}, reglist Rn{!}, reglist Rn{!}, reglist Rt, [Rn {, #offset}] Rt, [Rn {, #offset}] Rt, Rt2, [Rn {, #offset}] Rt, Rt, [Rn {, #offset}] Rd, Rt, [Rn] Rd, Rt, [Rn] Rt, [Rn {, #offset}] Rt, [Rn {, #offset}] Rt, [Rn {, #offset}] Rt, [Rn {, #offset}] {Rd,} Rn, Op2 {Rd,} Rn, #imm12 #imm {Rd,} Rn, Rm, {,ROR #} {Rd,} Rn, Rm,{,ROR #} {Rd,} Rn, Rm,{,ROR #} {Rd,} Rm {,ROR #n} {Rd,} Rm {,ROR #n} {Rd,} Rm {,ROR #n} [Rn, Rm] [Rn, Rm, LSL #1] Rn, Op2 Rn, Op2 {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm Signed saturate Signed saturate 16 Saturating subtract and add with exchange Signed subtract 16 Signed subtract 8 Q Q GE Operands {Rd,} Rn, Rm Brief Description Signed dual multiply subtract Flags -
Store multiple registers, increment after Store multiple registers, decrement before -
Store multiple registers, increment after Store register word Store register byte Store register two words Store register exclusive Store register exclusive byte Store register exclusive halfword Store register halfword Store register signed byte Store register signed halfword Store register word Subtract Subtract 12-bit constant Supervisor call Extend 8 bits to 32 and add Dual extend 8 bits to 16 and add Extend 16 bits to 32 and add Signed extend byte 16 Sign extend a byte Sign extend a halfword Table branch byte Table branch halfword Test equivalence Test Unsigned add 16 Unsigned add 8 Unsigned add and subtract with exchange Unsigned halving add 16 Unsigned halving add 8 N,Z,C,V N,Z,C,V N,Z,C N,Z,C GE GE GE -
Unsigned halving add and subtract with exchange
115

Mnemonic UHSAX UHSUB16 UHSUB8 UBFX UDIV UMAAL Operands {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm Rd, Rn, #lsb, #width {Rd,} Rn, Rm RdLo, RdHi, Rn, Rm Brief Description Flags Unsigned halving subtract and add with exchange Unsigned halving subtract 16 Unsigned halving subtract 8 Unsigned bit field extract Unsigned divide Unsigned multiply accumulate accumulate long (32x32+64), 64-bit result Unsigned multiply with accumulate (32x32+32+32), 64-bit result -
UMLAL UMULL UQADD16 UQADD8 UQASX UQSAX UQSUB16 UQSUB8 USAD8 USADA8 USAT USAT16 USAX USUB16 USUB8 UXTAB UXTAB16 UXTAH UXTB UXTB16 UXTH VABS.F32 VADD.F32 VCMP.F32 VCMPE.F32
RdLo, RdHi, Rn, Rm RdLo, RdHi, Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm, Ra Rd, #n, Rm {,shift #s} Rd, #n, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm {Rd,} Rn, Rm, {,ROR #} {Rd,} Rn, Rm, {,ROR #} {Rd,} Rn, Rm, {,ROR #} {Rd,} Rm, {,ROR #n} {Rd,} Rm, {,ROR #n} {Rd,} Rm, {,ROR #n} Sd, Sm {Sd,} Sn, Sm Sd, <Sm | #0.0> Sd, <Sm | #0.0>
Unsigned multiply (32x 2), 64-bit result Unsigned Saturating Add 16 Unsigned Saturating Add 8 -
Unsigned Saturating Add and Subtract with Exchange Unsigned Saturating Subtract and Add with Exchange Unsigned Saturating Subtract 16 Unsigned Saturating Subtract 8 -
Unsigned Sum of Absolute Differences Unsigned Sum of Absolute Differences and Accumulate Unsigned Saturate Unsigned Saturate 16 Unsigned Subtract and add with Exchange Unsigned Subtract 16 Unsigned Subtract 8 Rotate, extend 8 bits to 32 and Add Q Q GE GE GE -
Rotate, dual extend 8 bits to 16 and Add Rotate, unsigned extend and Add Halfword Zero extend a Byte Unsigned Extend Byte 16 Zero extend a Halfword Floating-point Absolute Floating-point Add -
Compare two floating-point registers, or FPSCR one floating-point register and zero Compare two floating-point registers, or FPSCR one floating-point register and zero with Invalid Operation check Convert between floating-point and integer -
VCVT.S32.F32
Sd, Sm
April 25, 2012

Mnemonic VCVT.S16.F32 VCVTR.S32.F32 VCVT<B|H>.F32.F16 VCVTT<B|T>.F32.F16 VDIV.F32 VFMA.F32 VFNMA.F32 VFMS.F32 VFNMS.F32 VLDM.F<32|64> VLDR.F<32|64> VLMA.F32 VLMS.F32 VMOV.F32 VMOV VMOV VMOV VMOV VMOV VMRS VMSR VMUL.F32 VNEG.F32 VNMLA.F32 VNMLS.F32 VNMUL VPOP VPUSH VSQRT.F32 VSTM VSTR.F3<32|64> VSUB.F<32|64> WFE WFI Operands Sd, Sd, #fbits Sd, Sm Sd, Sm Sd, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm Rn{!}, list <Dd|Sd>, [Rn] {Sd,} Sn, Sm {Sd,} Sn, Sm Sd, #imm Sd, Sm Sn, Rt Sm, Sm1, Rt, Rt2 Dd[x], Rt Rt, Dn[x] Rt, FPSCR FPSCR, Rt {Sd,} Sn, Sm Sd, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm {Sd,} Sn, Sm list list Sd, Sm Rn{!}, list Sd, [Rn] {Sd,} Sn, Sm Brief Description Flags Convert between floating-point and fixed point Convert between floating-point and integer with rounding Converts half-precision value to single-precision Converts single-precision register to half-precision Floating-point Divide -
Floating-point Fused Multiply Accumulate Floating-point Fused Negate Multiply Accumulate Floating-point Fused Multiply Subtract Floating-point Fused Negate Multiply Subtract Load Multiple extension registers -
Load an extension register from memory Floating-point Multiply Accumulate Floating-point Multiply Subtract Floating-point Move immediate Floating-point Move register Copy ARM core register to single precision Copy 2 ARM core registers to 2 single precision Copy ARM core register to scalar Copy scalar to ARM core register Move FPSCR to ARM core register or APSR N,Z,C,V
Move to FPSCR from ARM Core register FPSCR Floating-point Multiply Floating-point Negate Floating-point Multiply and Add Floating-point Multiply and Subtract Floating-point Multiply Pop extension registers Push extension registers Calculates floating-point Square Root Floating-point register Store Multiple -
Stores an extension register to memory Floating-point Subtract Wait for event Wait for interrupt -
117
Cortex-M4 Peripherals
This chapter provides information on the Stellaris implementation of the Cortex-M4 processor peripherals, including: SysTick (see page 119) Provides a simple, 24-bit clear-on-write, decrementing, wrap-on-zero counter with a flexible control mechanism. Nested Vectored Interrupt Controller (NVIC) (see page 120) Facilitates low-latency exception and interrupt handling Controls power management Implements system control registers System Control Block (SCB) (see page 121) Provides system implementation information and system control, including configuration, control, and reporting of system exceptions. Memory Protection Unit (MPU) (see page 121) Supports the standard ARMv7 Protected Memory System Architecture (PMSA) model. The MPU provides full support for protection regions, overlapping protection regions, access permissions, and exporting memory attributes to the system. Floating-Point Unit (FPU) (see page 126) Fully supports single-precision add, subtract, multiply, divide, multiply and accumulate, and square root operations. It also provides conversions between fixed-point and floating-point data formats, and floating-point constant instructions. Table 3-1 on page 118 shows the address map of the Private Peripheral Bus (PPB). Some peripheral register regions are split into two address regions, as indicated by two addresses listed. Table 3-1. Core Peripheral Register Regions
Address 0xE000.E010-0xE000.E01F 0xE000.E100-0xE000.E4EF 0xE000.EF00-0xE000.EF03 0xE000.E008-0xE000.E00F 0xE000.ED00-0xE000.ED3F 0xE000.ED90-0xE000.EDB8 0xE000.EF30-0xE000.EF44 Memory Protection Unit Floating Point Unit 121 126 System Control Block 121 Core Peripheral System Timer Nested Vectored Interrupt Controller Description (see page ...) 119 120
3.1
Functional Description
This chapter provides information on the Stellaris implementation of the Cortex-M4 processor peripherals: SysTick, NVIC, SCB and MPU.
April 25, 2012
3.1.1
System Timer (SysTick)

Cortex-M4 includes an integrated system timer, SysTick, which provides a simple, 24-bit clear-on-write, decrementing, wrap-on-zero counter with a flexible control mechanism. The counter can be used in several different ways, for example as: An RTOS tick timer that fires at a programmable rate (for example, 100 Hz) and invokes a SysTick routine. A high-speed alarm timer using the system clock. A variable rate alarm or signal timerthe duration is range-dependent on the reference clock used and the dynamic range of the counter. A simple counter used to measure time to completion and time used. An internal clock source control based on missing/meeting durations. The COUNT bit in the STCTRL control and status register can be used to determine if an action completed within a set duration, as part of a dynamic clock management control loop. The timer consists of three registers: SysTick Control and Status (STCTRL): A control and status counter to configure its clock, enable the counter, enable the SysTick interrupt, and determine counter status. SysTick Reload Value (STRELOAD): The reload value for the counter, used to provide the counter's wrap value. SysTick Current Value (STCURRENT): The current value of the counter. When enabled, the timer counts down on each clock from the reload value to zero, reloads (wraps) to the value in the STRELOAD register on the next clock edge, then decrements on subsequent clocks. Clearing the STRELOAD register disables the counter on the next wrap. When the counter reaches zero, the COUNT status bit is set. The COUNT bit clears on reads. Writing to the STCURRENT register clears the register and the COUNT status bit. The write does not trigger the SysTick exception logic. On a read, the current value is the value of the register at the time the register is accessed. The SysTick counter runs on either the system clock or the precision internal oscillator (PIOSC) divided by 4. If this clock signal is stopped for low power mode, the SysTick counter stops. SysTick can be kept running during Deep-sleep mode by setting the CLK_SRC bit in the SysTick Control and Status Register (STCTRL) register and ensuring that the PIOSCPD bit in the Deep Sleep Clock Configuration (DSLPCLKCFG) register is clear. Ensure software uses aligned word accesses to access the SysTick registers. The SysTick counter reload and current value are undefined at reset; the correct initialization sequence for the SysTick counter is: 1. Program the value in the STRELOAD register. 2. Clear the STCURRENT register by writing to it with any value. 3. Configure the STCTRL register for the required operation. Note: When the processor is halted for debugging, the counter does not decrement.
119
3.1.2
Nested Vectored Interrupt Controller (NVIC)

This section describes the Nested Vectored Interrupt Controller (NVIC) and the registers it uses. The NVIC supports: 65 interrupts. A programmable priority level of 0-7 for each interrupt. A higher level corresponds to a lower priority, so level 0 is the highest interrupt priority. Low-latency exception and interrupt handling. Level and pulse detection of interrupt signals. Dynamic reprioritization of interrupts. Grouping of priority values into group priority and subpriority fields. Interrupt tail-chaining. An external Non-maskable interrupt (NMI). The processor automatically stacks its state on exception entry and unstacks this state on exception exit, with no instruction overhead, providing low latency exception handling.
3.1.2.1
Level-Sensitive and Pulse Interrupts

The processor supports both level-sensitive and pulse interrupts. Pulse interrupts are also described as edge-triggered interrupts. A level-sensitive interrupt is held asserted until the peripheral deasserts the interrupt signal. Typically this happens because the ISR accesses the peripheral, causing it to clear the interrupt request. A pulse interrupt is an interrupt signal sampled synchronously on the rising edge of the processor clock. To ensure the NVIC detects the interrupt, the peripheral must assert the interrupt signal for at least one clock cycle, during which the NVIC detects the pulse and latches the interrupt. When the processor enters the ISR, it automatically removes the pending state from the interrupt (see Hardware and Software Control of Interrupts on page 120 for more information). For a level-sensitive interrupt, if the signal is not deasserted before the processor returns from the ISR, the interrupt becomes pending again, and the processor must execute its ISR again. As a result, the peripheral can hold the interrupt signal asserted until it no longer needs servicing.
3.1.2.2
Hardware and Software Control of Interrupts

The Cortex-M4 latches all interrupts. A peripheral interrupt becomes pending for one of the following reasons: The NVIC detects that the interrupt signal is High and the interrupt is not active. The NVIC detects a rising edge on the interrupt signal. Software writes to the corresponding interrupt set-pending register bit, or to the Software Trigger Interrupt (SWTRIG) register to make a Software-Generated Interrupt pending. See the INT bit in the PEND0 register on page 142 or SWTRIG on page 152. A pending interrupt remains pending until one of the following:
April 25, 2012
The processor enters the ISR for the interrupt, changing the state of the interrupt from pending to active. Then: For a level-sensitive interrupt, when the processor returns from the ISR, the NVIC samples the interrupt signal. If the signal is asserted, the state of the interrupt changes to pending, which might cause the processor to immediately re-enter the ISR. Otherwise, the state of the interrupt changes to inactive. For a pulse interrupt, the NVIC continues to monitor the interrupt signal, and if this is pulsed the state of the interrupt changes to pending and active. In this case, when the processor returns from the ISR the state of the interrupt changes to pending, which might cause the processor to immediately re-enter the ISR. If the interrupt signal is not pulsed while the processor is in the ISR, when the processor returns from the ISR the state of the interrupt changes to inactive. Software writes to the corresponding interrupt clear-pending register bit For a level-sensitive interrupt, if the interrupt signal is still asserted, the state of the interrupt does not change. Otherwise, the state of the interrupt changes to inactive. For a pulse interrupt, the state of the interrupt changes to inactive, if the state was pending or to active, if the state was active and pending.
3.1.3
System Control Block (SCB)

The System Control Block (SCB) provides system implementation information and system control, including configuration, control, and reporting of the system exceptions.
3.1.4
Memory Protection Unit (MPU)

This section describes the Memory protection unit (MPU). The MPU divides the memory map into a number of regions and defines the location, size, access permissions, and memory attributes of each region. The MPU supports independent attribute settings for each region, overlapping regions, and export of memory attributes to the system. The memory attributes affect the behavior of memory accesses to the region. The Cortex-M4 MPU defines eight separate memory regions, 0-7, and a background region. When memory regions overlap, a memory access is affected by the attributes of the region with the highest number. For example, the attributes for region 7 take precedence over the attributes of any region that overlaps region 7. The background region has the same memory access attributes as the default memory map, but is accessible from privileged software only. The Cortex-M4 MPU memory map is unified, meaning that instruction accesses and data accesses have the same region settings. If a program accesses a memory location that is prohibited by the MPU, the processor generates a memory management fault, causing a fault exception and possibly causing termination of the process in an OS environment. In an OS environment, the kernel can update the MPU region setting dynamically based on the process to be executed. Typically, an embedded OS uses the MPU for memory protection. Configuration of MPU regions is based on memory types (see Memory Regions, Types and Attributes on page 90 for more information).
121
Table 3-2 on page 122 shows the possible MPU region attributes. See the section called MPU Configuration for a Stellaris Microcontroller on page 126 for guidelines for programming a microcontroller implementation. Table 3-2. Memory Attributes Summary
Memory Type Strongly Ordered Device Normal Description All accesses to Strongly Ordered memory occur in program order. Memory-mapped peripherals Normal memory
To avoid unexpected behavior, disable the interrupts before updating the attributes of a region that the interrupt handlers might access. Ensure software uses aligned accesses of the correct size to access MPU registers: Except for the MPU Region Attribute and Size (MPUATTR) register, all MPU registers must be accessed with aligned word accesses. The MPUATTR register can be accessed with byte or aligned halfword or word accesses. The processor does not support unaligned accesses to MPU registers. When setting up the MPU, and if the MPU has previously been programmed, disable unused regions to prevent any previous region settings from affecting the new MPU setup.
3.1.4.1
Updating an MPU Region

To update the attributes for an MPU region, the MPU Region Number (MPUNUMBER), MPU Region Base Address (MPUBASE) and MPUATTR registers must be updated. Each register can be programmed separately or with a multiple-word write to program all of these registers. You can use the MPUBASEx and MPUATTRx aliases to program up to four regions simultaneously using an STM instruction. Updating an MPU Region Using Separate Words This example simple code configures one region: ; R1 = region number ; R2 = size/enable ; R3 = attributes ; R4 = address LDR R0,=MPUNUMBER STR R1, [R0, #0x0] STR R4, [R0, #0x4] STRH R2, [R0, #0x8] STRH R3, [R0, #0xA]
; ; ; ; ;
0xE000ED98, MPU region number register Region Number Region Base Address Region Size and Enable Region Attribute
Disable a region before writing new region settings to the MPU if you have previously enabled the region being changed. For example: ; R1 = region number ; R2 = size/enable ; R3 = attributes ; R4 = address LDR R0,=MPUNUMBER
; 0xE000ED98, MPU region number register
April 25, 2012
STR R1, [R0, #0x0] BIC R2, R2, #1 STRH R2, [R0, #0x8] STR R4, [R0, #0x4] STRH R3, [R0, #0xA] ORR R2, #1 STRH R2, [R0, #0x8]
; ; ; ; ; ; ;
Region Number Disable Region Size and Enable Region Base Address Region Attribute Enable Region Size and Enable
Software must use memory barrier instructions: Before MPU setup, if there might be outstanding memory transfers, such as buffered writes, that might be affected by the change in MPU settings. After MPU setup, if it includes memory transfers that must use the new MPU settings. However, memory barrier instructions are not required if the MPU setup process starts by entering an exception handler, or is followed by an exception return, because the exception entry and exception return mechanism cause memory barrier behavior. Software does not need any memory barrier instructions during MPU setup, because it accesses the MPU through the Private Peripheral Bus (PPB), which is a Strongly Ordered memory region. For example, if all of the memory access behavior is intended to take effect immediately after the programming sequence, then a DSB instruction and an ISB instruction should be used. A DSB is required after changing MPU settings, such as at the end of context switch. An ISB is required if the code that programs the MPU region or regions is entered using a branch or call. If the programming sequence is entered using a return from exception, or by taking an exception, then an ISB is not required. Updating an MPU Region Using Multi-Word Writes The MPU can be programmed directly using multi-word writes, depending how the information is divided. Consider the following reprogramming: ; R1 = region number ; R2 = address ; R3 = size, attributes in one LDR R0, =MPUNUMBER ; 0xE000ED98, MPU region number register STR R1, [R0, #0x0] ; Region Number STR R2, [R0, #0x4] ; Region Base Address STR R3, [R0, #0x8] ; Region Attribute, Size and Enable An STM instruction can be used to optimize this: ; R1 = region number ; R2 = address ; R3 = size, attributes in one LDR R0, =MPUNUMBER ; 0xE000ED98, MPU region number register STM R0, {R1-R3} ; Region number, address, attribute, size and enable This operation can be done in two words for pre-packed information, meaning that the MPU Region Base Address (MPUBASE) register (see page 186) contains the required region number and has the VALID bit set. This method can be used when the data is statically packed, for example in a boot loader:
123
; R1 = address and region number in one ; R2 = size and attributes in one LDR R0, =MPUBASE ; 0xE000ED9C, MPU Region Base register STR R1, [R0, #0x0] ; Region base address and region number combined ; with VALID (bit 4) set STR R2, [R0, #0x4] ; Region Attribute, Size and Enable Subregions Regions of 256 bytes or more are divided into eight equal-sized subregions. Set the corresponding bit in the SRD field of the MPU Region Attribute and Size (MPUATTR) register (see page 188) to disable a subregion. The least-significant bit of the SRD field controls the first subregion, and the most-significant bit controls the last subregion. Disabling a subregion means another region overlapping the disabled range matches instead. If no other enabled region overlaps the disabled subregion, the MPU issues a fault. Regions of 32, 64, and 128 bytes do not support subregions. With regions of these sizes, the SRD field must be configured to 0x00, otherwise the MPU behavior is unpredictable. Example of SRD Use Two regions with the same base address overlap. Region one is 128 KB, and region two is 512 KB. To ensure the attributes from region one apply to the first 128 KB region, configure the SRD field for region two to 0x03 to disable the first two subregions, as Figure 3-1 on page 124 shows. Figure 3-1. SRD Use Example
Offset from base address 512KB 448KB 384KB 320KB 256KB 192KB 128KB Disabled subregion 64KB Disabled subregion 0 Region 2, with subregions
Region 1
Base address of both regions
3.1.4.2
MPU Access Permission Attributes

The access permission bits, TEX, S, C, B, AP, and XN of the MPUATTR register, control access to the corresponding memory region. If an access is made to an area of memory without the required permissions, then the MPU generates a permission fault. Table 3-3 on page 124 shows the encodings for the TEX, C, B, and S access permission bits. All encodings are shown for completeness, however the current implementation of the Cortex-M4 does not support the concept of cacheability or shareability. Refer to the section called MPU Configuration for a Stellaris Microcontroller on page 126 for information on programming the MPU for Stellaris implementations. Table 3-3. TEX, S, C, and B Bit Field Encoding
TEX 000b 000 S x x
a a
C 0 0
B 0 1
Memory Type Strongly Ordered Device
Shareability Shareable Shareable
Other Attributes -
April 25, 2012
Table 3-3. TEX, S, C, and B Bit Field Encoding (continued)

TEX 000 000 000 000 001 001 001 001 001 001 010 010 010 1BB 1BB S 0 1 0 1 0 1 x x
a a
C 1 1 1 1 0 0 0 1 1 1 0 0 1 A A
B 0 0 1 1 0 0 1 0 1 1 0 1 x
a
Memory Type Normal Normal Normal Normal Normal Normal Reserved encoding Reserved encoding Normal Normal Device Reserved encoding Reserved encoding Normal Normal
Shareability Not shareable Shareable Not shareable Shareable Not shareable Shareable Not shareable Shareable Not shareable Not shareable Shareable
Other Attributes Outer and inner write-through. No write allocate.
Outer and inner noncacheable. Outer and inner write-back. Write and read allocate. Nonshared Device. Cached memory (BB = outer policy, AA = inner policy). See Table 3-4 for the encoding of the AA and BB bits.
0 1 x x x
a a a
0 1
A A
a. The MPU ignores the value of this bit.
Table 3-4 on page 125 shows the cache policy for memory attribute encodings with a TEX value in the range of 0x4-0x7. Table 3-4. Cache Policy for Memory Attribute Encoding
Encoding, AA or BB 00 01 10 11 Corresponding Cache Policy Non-cacheable Write back, write and read allocate Write through, no write allocate Write back, no write allocate
Table 3-5 on page 125 shows the AP encodings in the MPUATTR register that define the access permissions for privileged and unprivileged software. Table 3-5. AP Bit Field Encoding
AP Bit Field 000 001 010 011 100 101 Privileged Permissions No access R/W R/W R/W Unpredictable RO Unprivileged Permissions No access No access RO R/W Unpredictable No access Description All accesses generate a permission fault. Access from privileged software only. Writes by unprivileged software generate a permission fault. Full access. Reserved. Reads by privileged software only.
125
Table 3-5. AP Bit Field Encoding (continued)

AP Bit Field 110 111 Privileged Permissions RO RO Unprivileged Permissions RO RO Description Read-only, by privileged or unprivileged software. Read-only, by privileged or unprivileged software.
MPU Configuration for a Stellaris Microcontroller Stellaris microcontrollers have only a single processor and no caches. As a result, the MPU should be programmed as shown in Table 3-6 on page 126. Table 3-6. Memory Region Attributes for Stellaris Microcontrollers
Memory Region Flash memory Internal SRAM External SRAM Peripherals TEX 000b 000b 000b 000b S 0 1 1 1 C 1 1 1 0 B 0 0 1 1 Memory Type and Attributes Normal memory, non-shareable, write-through Normal memory, shareable, write-through Normal memory, shareable, write-back, write-allocate Device memory, shareable
In current Stellaris microcontroller implementations, the shareability and cache policy attributes do not affect the system behavior. However, using these settings for the MPU regions can make the application code more portable. The values given are for typical situations.
3.1.4.3
MPU Mismatch
When an access violates the MPU permissions, the processor generates a memory management fault (see Exceptions and Interrupts on page 88 for more information). The MFAULTSTAT register indicates the cause of the fault. See page 173 for more information.
3.1.5
Floating-Point Unit (FPU)

This section describes the Floating-Point Unit (FPU) and the registers it uses. The FPU provides: 32-bit instructions for single-precision (C float) data-processing operations Combined Multiply and Accumulate instructions for increased precision (Fused MAC) Hardware support for conversion, addition, subtraction, multiplication with optional accumulate, division, and square-root Hardware support for denormals and all IEEE rounding modes 32 dedicated 32-bit single-precision registers, also addressable as 16 double-word registers Decoupled three stage pipeline The Cortex-M4F FPU fully supports single-precision add, subtract, multiply, divide, multiply and accumulate, and square root operations. It also provides conversions between fixed-point and floating-point data formats, and floating-point constant instructions. The FPU provides floating-point computation functionality that is compliant with the ANSI/IEEE Std 754-2008, IEEE Standard for Binary Floating-Point Arithmetic, referred to as the IEEE 754 standard. The FPU's single-precision extension registers can also be accessed as 16 doubleword registers for load, store, and move operations.
April 25, 2012
3.1.5.1
FPU Views of the Register Bank

The FPU provides an extension register file containing 32 single-precision registers. These can be viewed as: Sixteen 64-bit doubleword registers, D0-D15 Thirty-two 32-bit single-word registers, S0-S31 A combination of registers from the above views Figure 3-2. FPU Register Bank
S0 S1 S2 S3 S4 S5 S6 S7 ... S28 S29 S30 S31 D0 D1 D2 D3 ... D14 D15
The mapping between the registers is as follows: S<2n> maps to the least significant half of D<n> S<2n+1> maps to the most significant half of D<n> For example, you can access the least significant half of the value in D6 by accessing S12, and the most significant half of the elements by accessing S13.
3.1.5.2
Modes of Operation
The FPU provides three modes of operation to accommodate a variety of applications. Full-Compliance mode. In Full-Compliance mode, the FPU processes all operations according to the IEEE 754 standard in hardware. Flush-to-Zero mode. Setting the FZ bit of the Floating-Point Status and Control (FPSC) register enables Flush-to-Zero mode. In this mode, the FPU treats all subnormal input operands of arithmetic CDP operations as zeros in the operation. Exceptions that result from a zero operand are signalled appropriately. VABS, VNEG, and VMOV are not considered arithmetic CDP operations and are not affected by Flush-to-Zero mode. A result that is tiny, as described in the IEEE 754 standard, where the destination precision is smaller in magnitude than the minimum normal value before rounding, is replaced with a zero. The IDC bit in FPSC indicates when an input flush occurs. The UFC bit in FPSC indicates when a result flush occurs. Default NaN mode. Setting the DN bit in the FPSC register enables default NaN mode. In this mode, the result of any arithmetic data processing operation that involves an input NaN, or that generates a NaN result, returns the default NaN. Propagation of the fraction bits is maintained only by VABS,
127
VNEG, and VMOV operations. All other CDP operations ignore any information in the fraction bits of an input NaN.
3.1.5.3
Compliance with the IEEE 754 standard

When Default NaN (DN) and Flush-to-Zero (FZ) modes are disabled, FPv4 functionality is compliant with the IEEE 754 standard in hardware. No support code is required to achieve this compliance.
3.1.5.4
Complete Implementation of the IEEE 754 standard

The Cortex-M4F floating point instruction set does not support all operations defined in the IEEE 754-2008 standard. Unsupported operations include, but are not limited to the following: Remainder Round floating-point number to integer-valued floating-point number Binary-to-decimal conversions Decimal-to-binary conversions Direct comparison of single-precision and double-precision values The Cortex-M4 FPU supports fused MAC operations as described in the IEEE standard. For complete implementation of the IEEE 754-2008 standard, floating-point functionality must be augmented with library functions.
3.1.5.5
IEEE 754 standard implementation choices

NaN handling All single-precision values with the maximum exponent field value and a nonzero fraction field are valid NaNs. A most-significant fraction bit of zero indicates a Signaling NaN (SNaN). A one indicates a Quiet NaN (QNaN). Two NaN values are treated as different NaNs if they differ in any bit. The below table shows the default NaN values.
Sign 0 Fraction 0xFF Fraction bit [22] = 1, bits [21:0] are all zeros
Processing of input NaNs for ARM floating-point functionality and libraries is defined as follows: In full-compliance mode, NaNs are handled as described in the ARM Architecture Reference Manual. The hardware processes the NaNs directly for arithmetic CDP instructions. For data transfer operations, NaNs are transferred without raising the Invalid Operation exception. For the non-arithmetic CDP instructions, VABS, VNEG, and VMOV, NaNs are copied, with a change of sign if specified in the instructions, without causing the Invalid Operation exception. In default NaN mode, arithmetic CDP instructions involving NaN operands return the default NaN regardless of the fractions of any NaN operands. SNaNs in an arithmetic CDP operation set the IOC flag, FPSCR[0]. NaN handling by data transfer and non-arithmetic CDP instructions is the same as in full-compliance mode.
April 25, 2012
Table 3-7. QNaN and SNaN Handling

Instruction Type Default NaN Mode Off Arithmetic CDP On Non-arithmetic CDP Off/On FCMP(Z) FCMPE(Z) Load/store Off/On With QNaN Operand The QNaN or one of the QNaN operands, if there is more than one, is returned according to the rules given in the ARM Architecture Reference Manual. Default NaN returns. With SNaN Operand IOC set. The SNaN is quieted and the result NaN is determined by the rules given in the ARM Architecture Reference Manual. IOCa set. Default NaN returns.
a
NaN passes to destination with sign changed as appropriate. Unordered compare. IOC set. Unordered compare. All NaNs transferred. IOC set. Unordered compare. IOC set. Unordered compare.
a. IOC is the Invalid Operation exception flag, FPSCR[0].
Comparisons Comparison results modify the flags in the FPSCR. You can use the MVRS APSR_nzcv instruction (formerly FMSTAT) to transfer the current flags from the FPSCR to the APSR. See the ARM Architecture Reference Manual for mapping of IEEE 754-2008 standard predicates to ARM conditions. The flags used are chosen so that subsequent conditional execution of ARM instructions can test the predicates defined in the IEEE standard. Underflow The Cortex-M4F FPU uses the before rounding form of tininess and the inexact result form of loss of accuracy as described in the IEEE 754-2008 standard to generate Underflow exceptions. In flush-to-zero mode, results that are tiny before rounding, as described in the IEEE standard, are flushed to a zero, and the UFC flag, FPSCR[3], is set. See the ARM Architecture Reference Manual for information on flush-to-zero mode. When the FPU is not in flush-to-zero mode, operations are performed on subnormal operands. If the operation does not produce a tiny result, it returns the computed result, and the UFC flag, FPSCR[3], is not set. The IXC flag, FPSCR[4], is set if the operation is inexact. If the operation produces a tiny result, the result is a subnormal or zero value, and the UFC flag, FPSCR[3], is set if the result was also inexact.
3.1.5.6
Exceptions
The FPU sets the cumulative exception status flag in the FPSCR register as required for each instruction, in accordance with the FPv4 architecture. The FPU does not support user-mode traps. The exception enable bits in the FPSCR read-as-zero, and writes are ignored. The processor also has six output pins, FPIXC, FPUFC, FPOFC, FPDZC, FPIDC, and FPIOC, that each reflect the status of one of the cumulative exception flags. For a description of these outputs, see the ARM Cortex-M4 Integration and Implementation Manual (ARM DII 0239, available from ARM). The processor can reduce the exception latency by using lazy stacking. See Auxiliary Control Register, ACTLR on page 4-5. This means that the processor reserves space on the stack for the FP state, but does not save that state information to the stack. See the ARMv7-M Architecture Reference Manual (available from ARM) for more information.
3.1.5.7
Enabling the FPU

The FPU is disabled from reset. You must enable it before you can use any floating-point instructions. The processor must be in privileged mode to read from and write to the Coprocessor Access
129
Control (CPAC) register. The below example code sequence enables the FPU in both privileged and user modes. ; CPACR is located at address 0xE000ED88 LDR.W R0, =0xE000ED88 ; Read CPACR LDR R1, [R0] ; Set bits 20-23 to enable CP10 and CP11 coprocessors ORR R1, R1, #(0xF << 20) ; Write back the modified value to the CPACR STR R1, [R0]; wait for store to complete DSB ;reset pipeline now the FPU is enabled ISB
3.2
Register Map
Table 3-8 on page 130 lists the Cortex-M4 Peripheral SysTick, NVIC, MPU, FPU and SCB registers. The offset listed is a hexadecimal increment to the register's address, relative to the Core Peripherals base address of 0xE000.E000. Note: Register spaces that are not used are reserved for future or internal use. Software should not modify any reserved memory address.
Table 3-8. Peripherals Register Map

Offset Name Type Reset Description See page
System Timer (SysTick) Registers 0x010 0x014 0x018 STCTRL STRELOAD STCURRENT R/W R/W R/WC 0x0000.0004 SysTick Control and Status Register SysTick Reload Value Register SysTick Current Value Register 134 136 137
Nested Vectored Interrupt Controller (NVIC) Registers 0x100 0x104 0x108 0x10C 0x110 0x180 0x184 0x188 0x18C 0x190 0x200 0x204 EN0 EN1 EN2 EN3 EN4 DIS0 DIS1 DIS2 DIS3 DIS4 PEND0 PEND1 R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Interrupt 0-31 Set Enable Interrupt 32-63 Set Enable Interrupt 64-95 Set Enable Interrupt 96-127 Set Enable Interrupt 128-138 Set Enable Interrupt 0-31 Clear Enable Interrupt 32-63 Clear Enable Interrupt 64-95 Clear Enable Interrupt 96-127 Clear Enable Interrupt 128-138 Clear Enable Interrupt 0-31 Set Pending Interrupt 32-63 Set Pending 138 138 138 138 139 140 140 140 140 141 142 142
April 25, 2012
Table 3-8. Peripherals Register Map (continued)

Offset 0x208 0x20C 0x210 0x280 0x284 0x288 0x28C 0x290 0x300 0x304 0x308 0x30C 0x310 0x400 0x404 0x408 0x40C 0x410 0x414 0x418 0x41C 0x420 0x424 0x428 0x42C 0x430 0x434 0x438 0x43C 0x440 0x444 0x448 Name PEND2 PEND3 PEND4 UNPEND0 UNPEND1 UNPEND2 UNPEND3 UNPEND4 ACTIVE0 ACTIVE1 ACTIVE2 ACTIVE3 ACTIVE4 PRI0 PRI1 PRI2 PRI3 PRI4 PRI5 PRI6 PRI7 PRI8 PRI9 PRI10 PRI11 PRI12 PRI13 PRI14 PRI15 PRI16 PRI17 PRI18 Type R/W R/W R/W R/W R/W R/W R/W R/W RO RO RO RO RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description Interrupt 64-95 Set Pending Interrupt 96-127 Set Pending Interrupt 128-138 Set Pending Interrupt 0-31 Clear Pending Interrupt 32-63 Clear Pending Interrupt 64-95 Clear Pending Interrupt 96-127 Clear Pending Interrupt 128-138 Clear Pending Interrupt 0-31 Active Bit Interrupt 32-63 Active Bit Interrupt 64-95 Active Bit Interrupt 96-127 Active Bit Interrupt 128-138 Active Bit Interrupt 0-3 Priority Interrupt 4-7 Priority Interrupt 8-11 Priority Interrupt 12-15 Priority Interrupt 16-19 Priority Interrupt 20-23 Priority Interrupt 24-27 Priority Interrupt 28-31 Priority Interrupt 32-35 Priority Interrupt 36-39 Priority Interrupt 40-43 Priority Interrupt 44-47 Priority Interrupt 48-51 Priority Interrupt 52-55 Priority Interrupt 56-59 Priority Interrupt 60-63 Priority Interrupt 64-67 Priority Interrupt 68-71 Priority Interrupt 72-75 Priority See page 142 142 143 144 144 144 144 145 146 146 146 146 147 148 148 148 148 148 148 148 148 148 148 148 148 148 148 148 148 150 150 150
131

Offset 0x44C 0x450 0x454 0x458 0x45C 0x460 0x464 0x468 0x46C 0x470 0x474 0x478 0x47C 0x480 0x484 0x488 0xF00 Name PRI19 PRI20 PRI21 PRI22 PRI23 PRI24 PRI25 PRI26 PRI27 PRI28 PRI29 PRI30 PRI31 PRI32 PRI33 PRI34 SWTRIG Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W WO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description Interrupt 76-79 Priority Interrupt 80-83 Priority Interrupt 84-87 Priority Interrupt 88-91 Priority Interrupt 92-95 Priority Interrupt 96-99 Priority Interrupt 100-103 Priority Interrupt 104-107 Priority Interrupt 108-111 Priority Interrupt 112-115 Priority Interrupt 116-119 Priority Interrupt 120-123 Priority Interrupt 124-127 Priority Interrupt 128-131 Priority Interrupt 132-135 Priority Interrupt 136-138 Priority Software Trigger Interrupt See page 150 150 150 150 150 150 150 150 150 150 150 150 150 150 150 150 152
System Control Block (SCB) Registers 0x008 0xD00 0xD04 0xD08 0xD0C 0xD10 0xD14 0xD18 0xD1C 0xD20 0xD24 0xD28 0xD2C 0xD34 ACTLR CPUID INTCTRL VTABLE APINT SYSCTRL CFGCTRL SYSPRI1 SYSPRI2 SYSPRI3 SYSHNDCTRL FAULTSTAT HFAULTSTAT MMADDR R/W RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W1C R/W1C R/W 0x0000.0000 0x410F.C241 0x0000.0000 0x0000.0000 0xFA05.0000 0x0000.0000 0x0000.0200 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Auxiliary Control CPU ID Base Interrupt Control and State Vector Table Offset Application Interrupt and Reset Control System Control Configuration and Control System Handler Priority 1 System Handler Priority 2 System Handler Priority 3 System Handler Control and State Configurable Fault Status Hard Fault Status Memory Management Fault Address 153 155 156 159 160 162 164 166 167 168 169 173 179 180
April 25, 2012

Offset 0xD38 Name FAULTADDR Type R/W Reset Description Bus Fault Address See page 181
Memory Protection Unit (MPU) Registers 0xD90 0xD94 0xD98 0xD9C 0xDA0 0xDA4 0xDA8 0xDAC 0xDB0 0xDB4 0xDB8 MPUTYPE MPUCTRL MPUNUMBER MPUBASE MPUATTR MPUBASE1 MPUATTR1 MPUBASE2 MPUATTR2 MPUBASE3 MPUATTR3 RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 0x0000.0800 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 MPU Type MPU Control MPU Region Number MPU Region Base Address MPU Region Attribute and Size MPU Region Base Address Alias 1 MPU Region Attribute and Size Alias 1 MPU Region Base Address Alias 2 MPU Region Attribute and Size Alias 2 MPU Region Base Address Alias 3 MPU Region Attribute and Size Alias 3 182 183 185 186 188 186 188 186 188 186 188
Floating-Point Unit (FPU) Registers 0xD88 0xF34 0xF38 0xF3C CPAC FPCC FPCA FPDSC R/W R/W R/W R/W 0x0000.0000 0xC000.0000 0x0000.0000 Coprocessor Access Control Floating-Point Context Control Floating-Point Context Address Floating-Point Default Status Control 191 192 194 195
3.3
System Timer (SysTick) Register Descriptions

This section lists and describes the System Timer registers, in numerical order by address offset.
133
Register 1: SysTick Control and Status Register (STCTRL), offset 0x010

Note: This register can only be accessed from privileged mode. The SysTick STCTRL register enables the SysTick features.
SysTick Control and Status Register (STCTRL)
Base 0xE000.E000 Offset 0x010 Type R/W, reset 0x0000.0004
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 CLK_SRC R/W 1 RO 0 1 INTEN R/W 0 23 22 21 20 19 18 17 16 COUNT RO 0 0 ENABLE R/W 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Count Flag Value 0 1 Description The SysTick timer has not counted to 0 since the last time this bit was read. The SysTick timer has counted to 0 since the last time this bit was read.
16
COUNT
RO
This bit is cleared by a read of the register or if the STCURRENT register is written with any value. If read by the debugger using the DAP, this bit is cleared only if the MasterType bit in the AHB-AP Control Register is clear. Otherwise, the COUNT bit is not changed by the debugger read. See the ARM Debug Interface V5 Architecture Specification for more information on MasterType. 15:3 reserved RO 0x000 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Source Value Description 0 1 Precision internal oscillator (PIOSC) divided by 4 System clock
CLK_SRC
R/W
April 25, 2012
Bit/Field 1
Name INTEN
Type R/W
Reset 0
Description Interrupt Enable Value 0 1 Description Interrupt generation is disabled. Software can use the COUNT bit to determine if the counter has ever reached 0. An interrupt is generated to the NVIC when SysTick counts to 0.
ENABLE
R/W
Enable Value 0 1 Description The counter is disabled. Enables SysTick to operate in a multi-shot way. That is, the counter loads the RELOAD value and begins counting down. On reaching 0, the COUNT bit is set and an interrupt is generated if enabled by INTEN. The counter then loads the RELOAD value again and begins counting.
135
Register 2: SysTick Reload Value Register (STRELOAD), offset 0x014

Note: This register can only be accessed from privileged mode. The STRELOAD register specifies the start value to load into the SysTick Current Value (STCURRENT) register when the counter reaches 0. The start value can be between 0x1 and 0x00FF.FFFF. A start value of 0 is possible but has no effect because the SysTick interrupt and the COUNT bit are activated when counting from 1 to 0. SysTick can be configured as a multi-shot timer, repeated over and over, firing every N+1 clock pulses, where N is any value from 1 to 0x00FF.FFFF. For example, if a tick interrupt is required every 100 clock pulses, 99 must be written into the RELOAD field. Note that in order to access this register correctly, the system clock must be faster than 8 MHz.
SysTick Reload Value Register (STRELOAD)
Base 0xE000.E000 Offset 0x014 Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RELOAD Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5
RELOAD R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Reload Value Value to load into the SysTick Current Value (STCURRENT) register when the counter reaches 0.
23:0
RELOAD
R/W
0x00.0000
April 25, 2012
Register 3: SysTick Current Value Register (STCURRENT), offset 0x018

Note: This register can only be accessed from privileged mode. The STCURRENT register contains the current value of the SysTick counter.
SysTick Current Value Register (STCURRENT)
Base 0xE000.E000 Offset 0x018 Type R/WC, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 R/WC 0 7 R/WC 0 6 R/WC 0 5
CURRENT R/WC 0 4 R/WC 0 3 R/WC 0 2 R/WC 0 1 R/WC 0 0
CURRENT Type Reset R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0 R/WC 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Current Value This field contains the current value at the time the register is accessed. No read-modify-write protection is provided, so change with care. This register is write-clear. Writing to it with any value clears the register. Clearing this register also clears the COUNT bit of the STCTRL register.
23:0
CURRENT
R/WC
0x00.0000
3.4
NVIC Register Descriptions

This section lists and describes the NVIC registers, in numerical order by address offset. The NVIC registers can only be fully accessed from privileged mode, but interrupts can be pended while in unprivileged mode by enabling the Configuration and Control (CFGCTRL) register. Any other unprivileged mode access causes a bus fault. Ensure software uses correctly aligned register accesses. The processor does not support unaligned accesses to NVIC registers. An interrupt can enter the pending state even if it is disabled. Before programming the VTABLE register to relocate the vector table, ensure the vector table entries of the new vector table are set up for fault handlers, NMI, and all enabled exceptions such as interrupts. For more information, see page 159.
137
Register 4: Interrupt 0-31 Set Enable (EN0), offset 0x100 Register 5: Interrupt 32-63 Set Enable (EN1), offset 0x104 Register 6: Interrupt 64-95 Set Enable (EN2), offset 0x108 Register 7: Interrupt 96-127 Set Enable (EN3), offset 0x10C
Note: This register can only be accessed from privileged mode. The ENn registers enable interrupts and show which interrupts are enabled. Bit 0 of EN0 corresponds to Interrupt 0; bit 31 corresponds to Interrupt 31. Bit 0 of EN1 corresponds to Interrupt 32; bit 31 corresponds to Interrupt 63. Bit 0 of EN2 corresponds to Interrupt 64; bit 31 corresponds to Interrupt 95. Bit 0 of EN3 corresponds to Interrupt 96; bit 31 corresponds to Interrupt 127. Bit 0 of EN4 (see page 139) corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments. If a pending interrupt is enabled, the NVIC activates the interrupt based on its priority. If an interrupt is not enabled, asserting its interrupt signal changes the interrupt state to pending, but the NVIC never activates the interrupt, regardless of its priority.
Interrupt 0-31 Set Enable (EN0)
31 30 29 28 27 26 25 24 INT Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 INT Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name INT
Type R/W
Reset
Description
0x0000.0000 Interrupt Enable Value 0 1 Description On a read, indicates the interrupt is disabled. On a write, no effect. On a read, indicates the interrupt is enabled. On a write, enables the interrupt. A bit can only be cleared by setting the corresponding INT[n] bit in the DISn register.
April 25, 2012
Register 8: Interrupt 128-138 Set Enable (EN4), offset 0x110

Note: This register can only be accessed from privileged mode. The EN4 register enables interrupts and shows which interrupts are enabled. Bit 0 corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments. If a pending interrupt is enabled, the NVIC activates the interrupt based on its priority. If an interrupt is not enabled, asserting its interrupt signal changes the interrupt state to pending, but the NVIC never activates the interrupt, regardless of its priority.
Interrupt 128-138 Set Enable (EN4)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 INT R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:11
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Enable Value 0 1 Description On a read, indicates the interrupt is disabled. On a write, no effect. On a read, indicates the interrupt is enabled. On a write, enables the interrupt. A bit can only be cleared by setting the corresponding INT[n] bit in the DIS4 register.
10:0
INT
R/W
0x0
139
Register 9: Interrupt 0-31 Clear Enable (DIS0), offset 0x180 Register 10: Interrupt 32-63 Clear Enable (DIS1), offset 0x184 Register 11: Interrupt 64-95 Clear Enable (DIS2), offset 0x188 Register 12: Interrupt 96-127 Clear Enable (DIS3), offset 0x18C
Note: This register can only be accessed from privileged mode. The DISn registers disable interrupts. Bit 0 of DIS0 corresponds to Interrupt 0; bit 31 corresponds to Interrupt 31. Bit 0 of DIS1 corresponds to Interrupt 32; bit 31 corresponds to Interrupt 63. Bit 0 of DIS2 corresponds to Interrupt 64; bit 31 corresponds to Interrupt 95. Bit 0 of DIS3 corresponds to Interrupt 96; bit 31 corresponds to Interrupt 127. Bit 0 of DIS4 (see page 141) corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 0-31 Clear Enable (DIS0)
Bit/Field 31:0
Name INT
Type R/W
Reset
Description
0x0000.0000 Interrupt Disable Value Description 0 1 On a read, indicates the interrupt is disabled. On a write, no effect. On a read, indicates the interrupt is enabled. On a write, clears the corresponding INT[n] bit in the EN0 register, disabling interrupt [n].
April 25, 2012
Register 13: Interrupt 128-138 Clear Enable (DIS4), offset 0x190

Note: This register can only be accessed from privileged mode. The DIS4 register disables interrupts. Bit 0 corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 128-138 Clear Enable (DIS4)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:11
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Disable Value Description 0 1 On a read, indicates the interrupt is disabled. On a write, no effect. On a read, indicates the interrupt is enabled. On a write, clears the corresponding INT[n] bit in the EN4 register, disabling interrupt [n].
10:0
INT
R/W
0x0
141
Register 14: Interrupt 0-31 Set Pending (PEND0), offset 0x200 Register 15: Interrupt 32-63 Set Pending (PEND1), offset 0x204 Register 16: Interrupt 64-95 Set Pending (PEND2), offset 0x208 Register 17: Interrupt 96-127 Set Pending (PEND3), offset 0x20C
Note: This register can only be accessed from privileged mode. The PENDn registers force interrupts into the pending state and show which interrupts are pending. Bit 0 of PEND0 corresponds to Interrupt 0; bit 31 corresponds to Interrupt 31. Bit 0 of PEND1 corresponds to Interrupt 32; bit 31 corresponds to Interrupt 63. Bit 0 of PEND2 corresponds to Interrupt 64; bit 31 corresponds to Interrupt 95. Bit 0 of PEND3 corresponds to Interrupt 96; bit 31 corresponds to Interrupt 127. Bit 0 of PEND4 (see page 143) corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 0-31 Set Pending (PEND0)
Bit/Field 31:0
Name INT
Type R/W
Reset
Description
0x0000.0000 Interrupt Set Pending Value 0 1 Description On a read, indicates that the interrupt is not pending. On a write, no effect. On a read, indicates that the interrupt is pending. On a write, the corresponding interrupt is set to pending even if it is disabled. If the corresponding interrupt is already pending, setting a bit has no effect. A bit can only be cleared by setting the corresponding INT[n] bit in the UNPEND0 register.
April 25, 2012
Register 18: Interrupt 128-138 Set Pending (PEND4), offset 0x210

Note: This register can only be accessed from privileged mode. The PEND4 register forces interrupts into the pending state and shows which interrupts are pending. Bit 0 corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 128-138 Set Pending (PEND4)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:11
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Set Pending Value 0 1 Description On a read, indicates that the interrupt is not pending. On a write, no effect. On a read, indicates that the interrupt is pending. On a write, the corresponding interrupt is set to pending even if it is disabled. If the corresponding interrupt is already pending, setting a bit has no effect. A bit can only be cleared by setting the corresponding INT[n] bit in the UNPEND4 register.
10:0
INT
R/W
0x0
143
Register 19: Interrupt 0-31 Clear Pending (UNPEND0), offset 0x280 Register 20: Interrupt 32-63 Clear Pending (UNPEND1), offset 0x284 Register 21: Interrupt 64-95 Clear Pending (UNPEND2), offset 0x288 Register 22: Interrupt 96-127 Clear Pending (UNPEND3), offset 0x28C
Note: This register can only be accessed from privileged mode. The UNPENDn registers show which interrupts are pending and remove the pending state from interrupts. Bit 0 of UNPEND0 corresponds to Interrupt 0; bit 31 corresponds to Interrupt 31. Bit 0 of UNPEND1 corresponds to Interrupt 32; bit 31 corresponds to Interrupt 63. Bit 0 of UNPEND2 corresponds to Interrupt 64; bit 31 corresponds to Interrupt 95. Bit 0 of UNPEND3 corresponds to Interrupt 96; bit 31 corresponds to Interrupt 127. Bit 0 of UNPEND4 (see page 145) corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 0-31 Clear Pending (UNPEND0)
Bit/Field 31:0
Name INT
Type R/W
Reset
Description
0x0000.0000 Interrupt Clear Pending Value Description 0 1 On a read, indicates that the interrupt is not pending. On a write, no effect. On a read, indicates that the interrupt is pending. On a write, clears the corresponding INT[n] bit in the PEND0 register, so that interrupt [n] is no longer pending. Setting a bit does not affect the active state of the corresponding interrupt.
April 25, 2012
Register 23: Interrupt 128-138 Clear Pending (UNPEND4), offset 0x290

Note: This register can only be accessed from privileged mode. The UNPEND4 register shows which interrupts are pending and removes the pending state from interrupts. Bit 0 corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments.
Interrupt 128-138 Clear Pending (UNPEND4)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:11
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Clear Pending Value Description 0 1 On a read, indicates that the interrupt is not pending. On a write, no effect. On a read, indicates that the interrupt is pending. On a write, clears the corresponding INT[n] bit in the PEND4 register, so that interrupt [n] is no longer pending. Setting a bit does not affect the active state of the corresponding interrupt.
10:0
INT
R/W
0x0
145
Register 24: Interrupt 0-31 Active Bit (ACTIVE0), offset 0x300 Register 25: Interrupt 32-63 Active Bit (ACTIVE1), offset 0x304 Register 26: Interrupt 64-95 Active Bit (ACTIVE2), offset 0x308 Register 27: Interrupt 96-127 Active Bit (ACTIVE3), offset 0x30C
Note: This register can only be accessed from privileged mode. The UNPENDn registers indicate which interrupts are active. Bit 0 of ACTIVE0 corresponds to Interrupt 0; bit 31 corresponds to Interrupt 31. Bit 0 of ACTIVE1 corresponds to Interrupt 32; bit 31 corresponds to Interrupt 63. Bit 0 of ACTIVE2 corresponds to Interrupt 64; bit 31 corresponds to Interrupt 95. Bit 0 of ACTIVE3 corresponds to Interrupt 96; bit 31 corresponds to Interrupt 127. Bit 0 of ACTIVE4 (see page 147) corresponds to Interrupt 128; bit 10 corresponds to Interrupt 138. See Table 2-9 on page 100 for interrupt assignments. Caution Do not manually set or clear the bits in this register.
Interrupt 0-31 Active Bit (ACTIVE0)
Base 0xE000.E000 Offset 0x300 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 INT Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 INT Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name INT
Type RO
Reset
Description
0x0000.0000 Interrupt Active Value Description 0 1 The corresponding interrupt is not active. The corresponding interrupt is active, or active and pending.
April 25, 2012
Register 28: Interrupt 128-138 Active Bit (ACTIVE4), offset 0x310

Note: This register can only be accessed from privileged mode. The ACTIVE4 register indicates which interrupts are active. Bit 0 corresponds to Interrupt 128; bit 10 corresponds to Interrupt 131. See Table 2-9 on page 100 for interrupt assignments. Caution Do not manually set or clear the bits in this register.
Interrupt 128-138 Active Bit (ACTIVE4)
Base 0xE000.E000 Offset 0x310 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 INT RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:11
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Active Value Description 0 1 The corresponding interrupt is not active. The corresponding interrupt is active, or active and pending.
10:0
INT
RO
0x0
147
Register 29: Interrupt 0-3 Priority (PRI0), offset 0x400 Register 30: Interrupt 4-7 Priority (PRI1), offset 0x404 Register 31: Interrupt 8-11 Priority (PRI2), offset 0x408 Register 32: Interrupt 12-15 Priority (PRI3), offset 0x40C Register 33: Interrupt 16-19 Priority (PRI4), offset 0x410 Register 34: Interrupt 20-23 Priority (PRI5), offset 0x414 Register 35: Interrupt 24-27 Priority (PRI6), offset 0x418 Register 36: Interrupt 28-31 Priority (PRI7), offset 0x41C Register 37: Interrupt 32-35 Priority (PRI8), offset 0x420 Register 38: Interrupt 36-39 Priority (PRI9), offset 0x424 Register 39: Interrupt 40-43 Priority (PRI10), offset 0x428 Register 40: Interrupt 44-47 Priority (PRI11), offset 0x42C Register 41: Interrupt 48-51 Priority (PRI12), offset 0x430 Register 42: Interrupt 52-55 Priority (PRI13), offset 0x434 Register 43: Interrupt 56-59 Priority (PRI14), offset 0x438 Register 44: Interrupt 60-63 Priority (PRI15), offset 0x43C
Note: This register can only be accessed from privileged mode. The PRIn registers (see also page 150) provide 3-bit priority fields for each interrupt. These registers are byte accessible. Each register holds four priority fields that are assigned to interrupts as follows:
PRIn Register Bit Field Bits 31:29 Bits 23:21 Bits 15:13 Bits 7:5 Interrupt Interrupt [4n+3] Interrupt [4n+2] Interrupt [4n+1] Interrupt [4n]
See Table 2-9 on page 100 for interrupt assignments. Each priority level can be split into separate group priority and subpriority fields. The PRIGROUP field in the Application Interrupt and Reset Control (APINT) register (see page 160) indicates the position of the binary point that splits the priority and subpriority fields. These registers can only be accessed from privileged mode.
April 25, 2012
Interrupt 0-3 Priority (PRI0)

31 30 INTD Type Reset R/W 0 15 R/W 0 14 INTB Type Reset R/W 0 R/W 0 R/W 0 RO 0 RO 0 R/W 0 13 RO 0 12 RO 0 11 29 28 27 26 reserved RO 0 10 reserved RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 R/W 0 7 25 24 23 22 INTC R/W 0 6 INTA R/W 0 R/W 0 RO 0 RO 0 R/W 0 5 RO 0 4 RO 0 3 21 20 19 18 reserved RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0 17 16
Bit/Field 31:29
Name INTD
Type R/W
Reset 0x0
Description Interrupt Priority for Interrupt [4n+3] This field holds a priority value, 0-7, for the interrupt with the number [4n+3], where n is the number of the Interrupt Priority register (n=0 for PRI0, and so on). The lower the value, the greater the priority of the corresponding interrupt.
28:24
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Priority for Interrupt [4n+2] This field holds a priority value, 0-7, for the interrupt with the number [4n+2], where n is the number of the Interrupt Priority register (n=0 for PRI0, and so on). The lower the value, the greater the priority of the corresponding interrupt.
23:21
INTC
R/W
0x0
20:16
reserved
RO
0x0
15:13
INTB
R/W
0x0
12:8
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Priority for Interrupt [4n] This field holds a priority value, 0-7, for the interrupt with the number [4n], where n is the number of the Interrupt Priority register (n=0 for PRI0, and so on). The lower the value, the greater the priority of the corresponding interrupt.
7:5
INTA
R/W
0x0
4:0
reserved
RO
0x0
149
Register 45: Interrupt 64-67 Priority (PRI16), offset 0x440 Register 46: Interrupt 68-71 Priority (PRI17), offset 0x444 Register 47: Interrupt 72-75 Priority (PRI18), offset 0x448 Register 48: Interrupt 76-79 Priority (PRI19), offset 0x44C Register 49: Interrupt 80-83 Priority (PRI20), offset 0x450 Register 50: Interrupt 84-87 Priority (PRI21), offset 0x454 Register 51: Interrupt 88-91 Priority (PRI22), offset 0x458 Register 52: Interrupt 92-95 Priority (PRI23), offset 0x45C Register 53: Interrupt 96-99 Priority (PRI24), offset 0x460 Register 54: Interrupt 100-103 Priority (PRI25), offset 0x464 Register 55: Interrupt 104-107 Priority (PRI26), offset 0x468 Register 56: Interrupt 108-111 Priority (PRI27), offset 0x46C Register 57: Interrupt 112-115 Priority (PRI28), offset 0x470 Register 58: Interrupt 116-119 Priority (PRI29), offset 0x474 Register 59: Interrupt 120-123 Priority (PRI30), offset 0x478 Register 60: Interrupt 124-127 Priority (PRI31), offset 0x47C Register 61: Interrupt 128-131 Priority (PRI32), offset 0x480 Register 62: Interrupt 132-135 Priority (PRI33), offset 0x484 Register 63: Interrupt 136-138 Priority (PRI34), offset 0x488
Note: This register can only be accessed from privileged mode. The PRIn registers (see also page 148) provide 3-bit priority fields for each interrupt. These registers are byte accessible. Each register holds four priority fields that are assigned to interrupts as follows:
PRIn Register Bit Field Bits 31:29 Bits 23:21 Bits 15:13 Bits 7:5 Interrupt Interrupt [4n+3] Interrupt [4n+2] Interrupt [4n+1] Interrupt [4n]
See Table 2-9 on page 100 for interrupt assignments. Each priority level can be split into separate group priority and subpriority fields. The PRIGROUP field in the Application Interrupt and Reset Control (APINT) register (see page 160) indicates the position of the binary point that splits the priority and subpriority fields . These registers can only be accessed from privileged mode.
April 25, 2012
Interrupt 64-67 Priority (PRI16)

31 30 INTD Type Reset R/W 0 15 R/W 0 14 INTB Type Reset R/W 0 R/W 0 R/W 0 RO 0 RO 0 R/W 0 13 RO 0 12 RO 0 11 29 28 27 26 reserved RO 0 10 reserved RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 R/W 0 7 25 24 23 22 INTC R/W 0 6 INTA R/W 0 R/W 0 RO 0 RO 0 R/W 0 5 RO 0 4 RO 0 3 21 20 19 18 reserved RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0 17 16
Bit/Field 31:29
Name INTD
Type R/W
Reset 0x0
Description Interrupt Priority for Interrupt [4n+3] This field holds a priority value, 0-7, for the interrupt with the number [4n+3], where n is the number of the Interrupt Priority register (n=0 for PRI0, and so on). The lower the value, the greater the priority of the corresponding interrupt.
28:24
reserved
RO
0x0
23:21
INTC
R/W
0x0
20:16
reserved
RO
0x0
15:13
INTB
R/W
0x0
12:8
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Priority for Interrupt [4n] This field holds a priority value, 0-7, for the interrupt with the number [4n], where n is the number of the Interrupt Priority register (n=0 for PRI0, and so on). The lower the value, the greater the priority of the corresponding interrupt.
7:5
INTA
R/W
0x0
4:0
reserved
RO
0x0
151
Register 64: Software Trigger Interrupt (SWTRIG), offset 0xF00

Note: Only privileged software can enable unprivileged access to the SWTRIG register. Writing an interrupt number to the SWTRIG register generates a Software Generated Interrupt (SGI). See Table 2-9 on page 100 for interrupt assignments. When the MAINPEND bit in the Configuration and Control (CFGCTRL) register (see page 164) is set, unprivileged software can access the SWTRIG register.
Software Trigger Interrupt (SWTRIG)
Base 0xE000.E000 Offset 0xF00 Type WO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 INTID RO 0 RO 0 RO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt ID This field holds the interrupt ID of the required SGI. For example, a value of 0x3 generates an interrupt on IRQ3.
7:0
INTID
WO
0x00
3.5
System Control Block (SCB) Register Descriptions

This section lists and describes the System Control Block (SCB) registers, in numerical order by address offset. The SCB registers can only be accessed from privileged mode. All registers must be accessed with aligned word accesses except for the FAULTSTAT and SYSPRI1-SYSPRI3 registers, which can be accessed with byte or aligned halfword or word accesses. The processor does not support unaligned accesses to system control block registers.
April 25, 2012
Register 65: Auxiliary Control (ACTLR), offset 0x008

Note: This register can only be accessed from privileged mode. The ACTLR register provides disable bits for IT folding, write buffer use for accesses to the default memory map, and interruption of multi-cycle instructions. By default, this register is set to provide optimum performance from the Cortex-M4 processor and does not normally require modification.
Auxiliary Control (ACTLR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
DISOOFP DISFPCA R/W 0 R/W 0
DISFOLD DISWBUF DISMCYC R/W 0 R/W 0 R/W 0
Bit/Field 31:10
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Disable Out-Of-Order Floating Point Disables floating-point instructions completing out of order with respect to integer instructions.
DISOOFP
R/W
DISFPCA
R/W
Disable CONTROL.FPCA Disable automatic update of the FPCA bit in the CONTROL register.
Important:
7:3
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Disable IT Folding Value Description 0 1 No effect. Disables IT folding.
DISFOLD
R/W
In some situations, the processor can start executing the first instruction in an IT block while it is still executing the IT instruction. This behavior is called IT folding, and improves performance, However, IT folding can cause jitter in looping. If a task must avoid jitter, set the DISFOLD bit before executing the task, to disable IT folding.
153
Bit/Field 1
Name DISWBUF
Type R/W
Reset 0
Description Disable Write Buffer Value Description 0 1 No effect. Disables write buffer use during default memory map accesses. In this situation, all bus faults are precise bus faults but performance is decreased because any store to memory must complete before the processor can execute the next instruction. Note: This bit only affects write buffers implemented in the Cortex-M4 processor.
DISMCYC
R/W
Disable Interrupts of Multiple Cycle Instructions Value Description 0 1 No effect. Disables interruption of load multiple and store multiple instructions. In this situation, the interrupt latency of the processor is increased because any LDM or STM must complete before the processor can stack the current state and enter the interrupt handler.
April 25, 2012
Register 66: CPU ID Base (CPUID), offset 0xD00

Note: This register can only be accessed from privileged mode. The CPUID register contains the ARM Cortex-M4 processor part number, version, and implementation information.
CPU ID Base (CPUID)
Base 0xE000.E000 Offset 0xD00 Type RO, reset 0x410F.C241
31 30 29 28 IMP Type Reset RO 0 15 RO 1 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 PARTNO Type Reset RO 1 RO 1 RO 0 RO 0 RO 0 RO 0 RO 1 RO 0 RO 0 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 1 8 RO 0 7 RO 0 6 27 26 25 24 23 22 VAR RO 0 5 RO 0 4 RO 1 3 RO 1 2 REV RO 0 RO 1 21 20 19 18 CON RO 1 1 RO 1 0 17 16
Bit/Field 31:24
Name IMP
Type RO
Reset 0x41
Description Implementer Code Value Description 0x41 ARM
23:20
VAR
RO
0x0
Variant Number Value Description 0x0 The rn value in the rnpn product revision identifier, for example, the 0 in r0p0.
19:16
CON
RO
0xF
Constant Value Description 0xF Always reads as 0xF.
15:4
PARTNO
RO
0xC24
Part Number Value Description 0xC24 Cortex-M4 processor.
3:0
REV
RO
0x1
Revision Number Value Description 0x1 The pn value in the rnpn product revision identifier, for example, the 1 in r0p1.
155
Register 67: Interrupt Control and State (INTCTRL), offset 0xD04

Note: This register can only be accessed from privileged mode. The INCTRL register provides a set-pending bit for the NMI exception, and set-pending and clear-pending bits for the PendSV and SysTick exceptions. In addition, bits in this register indicate the exception number of the exception being processed, whether there are preempted active exceptions, the exception number of the highest priority pending exception, and whether any interrupts are pending. When writing to INCTRL, the effect is unpredictable when writing a 1 to both the PENDSV and UNPENDSV bits, or writing a 1 to both the PENDSTSET and PENDSTCLR bits.
Interrupt Control and State (INTCTRL)
Base 0xE000.E000 Offset 0xD04 Type R/W, reset 0x0000.0000
31 NMISET Type Reset R/W 0 15 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
PENDSV UNPENDSV PENDSTSET PENDSTCLR reserved R/W 0 12 WO 0 11 RETBASE RO 0 RO 0 RO 0 R/W 0 10 WO 0 9 reserved RO 0 RO 0 RO 0 8
ISRPRE ISRPEND RO 0 7 RO 0 6
reserved RO 0 5 RO 0 4 VECACT RO 0 3
VECPEND RO 0 2 RO 0 1 RO 0 0
VECPEND Type Reset RO 0 RO 0 RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31
Name NMISET
Type R/W
Reset 0
Description NMI Set Pending Value Description 0 1 On a read, indicates an NMI exception is not pending. On a write, no effect. On a read, indicates an NMI exception is pending. On a write, changes the NMI exception state to pending. Because NMI is the highest-priority exception, normally the processor enters the NMI exception handler as soon as it registers the setting of this bit, and clears this bit on entering the interrupt handler. A read of this bit by the NMI exception handler returns 1 only if the NMI signal is reasserted while the processor is executing that handler.
30:29
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PendSV Set Pending Value Description 0 1 On a read, indicates a PendSV exception is not pending. On a write, no effect. On a read, indicates a PendSV exception is pending. On a write, changes the PendSV exception state to pending. Setting this bit is the only way to set the PendSV exception state to pending. This bit is cleared by writing a 1 to the UNPENDSV bit.
28
PENDSV
R/W
April 25, 2012
Bit/Field 27
Name UNPENDSV
Type WO
Reset 0
Description PendSV Clear Pending Value Description 0 1 On a write, no effect. On a write, removes the pending state from the PendSV exception.
This bit is write only; on a register read, its value is unknown. 26 PENDSTSET R/W 0 SysTick Set Pending Value Description 0 1 On a read, indicates a SysTick exception is not pending. On a write, no effect. On a read, indicates a SysTick exception is pending. On a write, changes the SysTick exception state to pending. This bit is cleared by writing a 1 to the PENDSTCLR bit. 25 PENDSTCLR WO 0 SysTick Clear Pending Value Description 0 1 On a write, no effect. On a write, removes the pending state from the SysTick exception.
This bit is write only; on a register read, its value is unknown. 24 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Debug Interrupt Handling Value Description 0 1 The release from halt does not take an interrupt. The release from halt takes an interrupt.
23
ISRPRE
RO
This bit is only meaningful in Debug mode and reads as zero when the processor is not in Debug mode. 22 ISRPEND RO 0 Interrupt Pending Value Description 0 1 No interrupt is pending. An interrupt is pending.
This bit provides status for all interrupts excluding NMI and Faults. 21:20 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
157
Bit/Field 19:12
Name VECPEND
Type RO
Reset 0x00
Description Interrupt Pending Vector Number This field contains the exception number of the highest priority pending enabled exception. The value indicated by this field includes the effect of the BASEPRI and FAULTMASK registers, but not any effect of the PRIMASK register. Value 0x00 0x01 0x02 0x03 0x04 0x05 0x06 Description No exceptions are pending Reserved NMI Hard fault Memory management fault Bus fault Usage fault
0x07-0x0A Reserved 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 ... 0x9A SVCall Reserved for Debug Reserved PendSV SysTick Interrupt Vector 0 Interrupt Vector 1 ... Interrupt Vector 138
0x94-0x7F Reserved
11
RETBASE
RO
Return to Base Value Description 0 1 There are preempted active exceptions to execute. There are no active exceptions, or the currently executing exception is the only active exception.
This bit provides status for all interrupts excluding NMI and Faults. This bit only has meaning if the processor is currently executing an ISR (the Interrupt Program Status (IPSR) register is non-zero). 10:8 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Pending Vector Number This field contains the active exception number. The exception numbers can be found in the description for the VECPEND field. If this field is clear, the processor is in Thread mode. This field contains the same value as the ISRNUM field in the IPSR register. Subtract 16 from this value to obtain the IRQ number required to index into the Interrupt Set Enable (ENn), Interrupt Clear Enable (DISn), Interrupt Set Pending (PENDn), Interrupt Clear Pending (UNPENDn), and Interrupt Priority (PRIn) registers (see page 77).
7:0
VECACT
RO
0x00
April 25, 2012
Register 68: Vector Table Offset (VTABLE), offset 0xD08

Note: This register can only be accessed from privileged mode. The VTABLE register indicates the offset of the vector table base address from memory address 0x0000.0000.
Vector Table Offset (VTABLE)
31 30 29 BASE R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7 28 27 26 25 24 23 22 OFFSET R/W 0 6 R/W 0 5 reserved R/W 0 R/W 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14
OFFSET Type Reset R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:30
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Vector Table Base Value Description 0 1 The vector table is in the code memory region. The vector table is in the SRAM memory region.
29
BASE
R/W
28:10
OFFSET
R/W
0x000.00
Vector Table Offset When configuring the OFFSET field, the offset must be aligned to the number of exception entries in the vector table. Because there are 138 interrupts, the offset must be aligned on a 1024-byte boundary.
9:0
reserved
RO
0x00
159
Register 69: Application Interrupt and Reset Control (APINT), offset 0xD0C
Note: This register can only be accessed from privileged mode. The APINT register provides priority grouping control for the exception model, endian status for data accesses, and reset control of the system. To write to this register, 0x05FA must be written to the VECTKEY field, otherwise the write is ignored. The PRIGROUP field indicates the position of the binary point that splits the INTx fields in the Interrupt Priority (PRIx) registers into separate group priority and subpriority fields. Table 3-9 on page 160 shows how the PRIGROUP value controls this split. The bit numbers in the Group Priority Field and Subpriority Field columns in the table refer to the bits in the INTA field. For the INTB field, the corresponding bits are 15:13; for INTC, 23:21; and for INTD, 31:29. Note: Determining preemption of an exception uses only the group priority field.
Table 3-9. Interrupt Priority Levels

PRIGROUP Bit Field 0x0 - 0x4 0x5 0x6 0x7 Binary Point bxxx. bxx.y bx.yy b.yyy
a
Group Priority Field Subpriority Field [7:5] [7:6] [7] None None [5] [6:5] [7:5]
Group Priorities 8 4 2 1
Subpriorities 1 2 4 8
a. INTx field showing the binary point. An x denotes a group priority field bit, and a y denotes a subpriority field bit.
Application Interrupt and Reset Control (APINT)

Base 0xE000.E000 Offset 0xD0C Type R/W, reset 0xFA05.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
VECTKEY Type Reset R/W 1 15

ENDIANESS
R/W 1 14
R/W 1 13
R/W 1 12
R/W 1 11
R/W 0 10
R/W 1 9 PRIGROUP
R/W 0 8
R/W 0 7
R/W 0 6
R/W 0 5 reserved
R/W 0 4
R/W 0 3
R/W 1 2
R/W 0 1
R/W 1 0
reserved RO 0 RO 0 RO 0 RO 0 R/W 0
SYSRESREQ VECTCLRACT VECTRESET
Type Reset
RO 0
R/W 0
R/W 0
RO 0
RO 0
RO 0
RO 0
RO 0
WO 0
WO 0
WO 0
Bit/Field 31:16
Name VECTKEY
Type R/W
Reset 0xFA05
Description Register Key This field is used to guard against accidental writes to this register. 0x05FA must be written to this field in order to change the bits in this register. On a read, 0xFA05 is returned.
15
ENDIANESS
RO
Data Endianess The Stellaris implementation uses only little-endian mode so this is cleared to 0.
14:11
reserved
RO
0x0
April 25, 2012
Bit/Field 10:8
Name PRIGROUP
Type R/W
Reset 0x0
Description Interrupt Priority Grouping This field determines the split of group priority from subpriority (see Table 3-9 on page 160 for more information).
7:3
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. System Reset Request Value Description 0 1 No effect. Resets the core and all on-chip peripherals except the Debug interface.
SYSRESREQ
WO
This bit is automatically cleared during the reset of the core and reads as 0. 1 VECTCLRACT WO 0 Clear Active NMI / Fault This bit is reserved for Debug use and reads as 0. This bit must be written as a 0, otherwise behavior is unpredictable. 0 VECTRESET WO 0 System Reset This bit is reserved for Debug use and reads as 0. This bit must be written as a 0, otherwise behavior is unpredictable.
161
Register 70: System Control (SYSCTRL), offset 0xD10

Note: This register can only be accessed from privileged mode. The SYSCTRL register controls features of entry to and exit from low-power state.
System Control (SYSCTRL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4

SEVONPEND
RO 0 3
reserved
RO 0 2
RO 0 1
RO 0 0
reserved
SLEEPDEEP SLEEPEXIT
R/W 0
RO 0
R/W 0
R/W 0
RO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Wake Up on Pending Value Description 0 1 Only enabled interrupts or events can wake up the processor; disabled interrupts are excluded. Enabled events and all interrupts, including disabled interrupts, can wake up the processor.
SEVONPEND
R/W
When an event or interrupt enters the pending state, the event signal wakes up the processor from WFE. If the processor is not waiting for an event, the event is registered and affects the next WFE. The processor also wakes up on execution of a SEV instruction or an external event. 3 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Deep Sleep Enable Value Description 0 1 Use Sleep mode as the low power mode. Use Deep-sleep mode as the low power mode.
SLEEPDEEP
R/W
April 25, 2012
Bit/Field 1
Name SLEEPEXIT
Type R/W
Reset 0
Description Sleep on ISR Exit Value Description 0 1 When returning from Handler mode to Thread mode, do not sleep when returning to Thread mode. When returning from Handler mode to Thread mode, enter sleep or deep sleep on return from an ISR.
Setting this bit enables an interrupt-driven application to avoid returning to an empty main application. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
163
Register 71: Configuration and Control (CFGCTRL), offset 0xD14

Note: This register can only be accessed from privileged mode. The CFGCTRL register controls entry to Thread mode and enables: the handlers for NMI, hard fault and faults escalated by the FAULTMASK register to ignore bus faults; trapping of divide by zero and unaligned accesses; and access to the SWTRIG register by unprivileged software (see page 152).
Configuration and Control (CFGCTRL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 5 RO 0 4 DIV0 R/W 0 RO 0 3

UNALIGNED
RO 0 2
reserved
RO 0 1
MAINPEND
RO 0 0 BASETHR R/W 0
STKALIGN BFHFNMIGN
R/W 1
R/W 0
R/W 0
RO 0
R/W 0
Bit/Field 31:10
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Stack Alignment on Exception Entry Value Description 0 1 The stack is 4-byte aligned. The stack is 8-byte aligned.
STKALIGN
R/W
On exception entry, the processor uses bit 9 of the stacked PSR to indicate the stack alignment. On return from the exception, it uses this stacked bit to restore the correct stack alignment. 8 BFHFNMIGN R/W 0 Ignore Bus Fault in NMI and Fault This bit enables handlers with priority -1 or -2 to ignore data bus faults caused by load and store instructions. The setting of this bit applies to the hard fault, NMI, and FAULTMASK escalated handlers. Value Description 0 1 Data bus faults caused by load and store instructions cause a lock-up. Handlers running at priority -1 and -2 ignore data bus faults caused by load and store instructions.
Set this bit only when the handler and its data are in absolutely safe memory. The normal use of this bit is to probe system devices and bridges to detect control path problems and fix them. 7:5 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Bit/Field 4
Name DIV0
Type R/W
Reset 0
Description Trap on Divide by 0 This bit enables faulting or halting when the processor executes an SDIV or UDIV instruction with a divisor of 0. Value Description 0 1 Do not trap on divide by 0. A divide by zero returns a quotient of 0. Trap on divide by 0.
UNALIGNED
R/W
Trap on Unaligned Access Value Description 0 1 Do not trap on unaligned halfword and word accesses. Trap on unaligned halfword and word accesses. An unaligned access generates a usage fault.
Unaligned LDM, STM, LDRD, and STRD instructions always fault regardless of whether UNALIGNED is set. 2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Allow Main Interrupt Trigger Value Description 0 1 Disables unprivileged software access to the SWTRIG register. Enables unprivileged software access to the SWTRIG register (see page 152).
MAINPEND
R/W
BASETHR
R/W
Thread State Control Value Description 0 1 The processor can enter Thread mode only when no exception is active. The processor can enter Thread mode from any level under the control of an EXC_RETURN value (see Exception Return on page 106 for more information).
165
Register 72: System Handler Priority 1 (SYSPRI1), offset 0xD18

Note: This register can only be accessed from privileged mode. The SYSPRI1 register configures the priority level, 0 to 7 of the usage fault, bus fault, and memory management fault exception handlers. This register is byte-accessible.
System Handler Priority 1 (SYSPRI1)
31 30 29 28 27 26 25 24 23 22 USAGE RO 0 10 reserved R/W 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 R/W 0 7 R/W 0 6 MEM R/W 0 R/W 0 RO 0 RO 0 R/W 0 5 RO 0 4 RO 0 3 21 20 19 18 reserved RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0 17 16
reserved Type Reset RO 0 15 RO 0 14 BUS Type Reset R/W 0 R/W 0 RO 0 13 RO 0 12 RO 0 11
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Usage Fault Priority This field configures the priority level of the usage fault. Configurable priority values are in the range 0-7, with lower values having higher priority.
23:21
USAGE
R/W
0x0
20:16
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Bus Fault Priority This field configures the priority level of the bus fault. Configurable priority values are in the range 0-7, with lower values having higher priority.
15:13
BUS
R/W
0x0
12:8
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Memory Management Fault Priority This field configures the priority level of the memory management fault. Configurable priority values are in the range 0-7, with lower values having higher priority.
7:5
MEM
R/W
0x0
4:0
reserved
RO
0x0
April 25, 2012
Register 73: System Handler Priority 2 (SYSPRI2), offset 0xD1C

Note: This register can only be accessed from privileged mode. The SYSPRI2 register configures the priority level, 0 to 7 of the SVCall handler. This register is byte-accessible.
Base 0xE000.E000 Offset 0xD1C Type R/W, reset 0x0000.0000
31 30 SVC Type Reset R/W 0 15 R/W 0 14 R/W 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 29 28 27 26 25 24 23 22 reserved RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 21 20 19 18 17 16
Bit/Field 31:29
Name SVC
Type R/W
Reset 0x0
Description SVCall Priority This field configures the priority level of SVCall. Configurable priority values are in the range 0-7, with lower values having higher priority.
28:0
reserved
RO
0x000.0000
167
Register 74: System Handler Priority 3 (SYSPRI3), offset 0xD20

Note: This register can only be accessed from privileged mode. The SYSPRI3 register configures the priority level, 0 to 7 of the SysTick exception and PendSV handlers. This register is byte-accessible.
31 30 TICK Type Reset R/W 0 15 R/W 0 14 R/W 0 13 RO 0 12 RO 0 11 29 28 27 26 reserved RO 0 10 RO 0 9 RO 0 8 R/W 0 7 25 24 23 22 PENDSV R/W 0 6 DEBUG RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 RO 0 RO 0 R/W 0 5 RO 0 4 RO 0 3 21 20 19 18 reserved RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0 17 16
Bit/Field 31:29
Name TICK
Type R/W
Reset 0x0
Description SysTick Exception Priority This field configures the priority level of the SysTick exception. Configurable priority values are in the range 0-7, with lower values having higher priority.
28:24
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PendSV Priority This field configures the priority level of PendSV. Configurable priority values are in the range 0-7, with lower values having higher priority.
23:21
PENDSV
R/W
0x0
20:8
reserved
RO
0x000
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Debug Priority This field configures the priority level of Debug. Configurable priority values are in the range 0-7, with lower values having higher priority.
7:5
DEBUG
R/W
0x0
4:0
reserved
RO
0x0.0000
April 25, 2012
Register 75: System Handler Control and State (SYSHNDCTRL), offset 0xD24
Note: This register can only be accessed from privileged mode. The SYSHNDCTRL register enables the system handlers, and indicates the pending status of the usage fault, bus fault, memory management fault, and SVC exceptions as well as the active status of the system handlers. If a system handler is disabled and the corresponding fault occurs, the processor treats the fault as a hard fault. This register can be modified to change the pending or active status of system exceptions. An OS kernel can write to the active bits to perform a context switch that changes the current exception type. Caution Software that changes the value of an active bit in this register without correct adjustment to the stacked content can cause the processor to generate a fault exception. Ensure software that writes to this register retains and subsequently restores the current active status. If the value of a bit in this register must be modified after enabling the system handlers, a read-modify-write procedure must be used to ensure that only the required bit is modified.
System Handler Control and State (SYSHNDCTRL)
31 30 29 28 27 26 25 reserved Type Reset RO 0 15 SVC Type Reset R/W 0 RO 0 14 BUSP R/W 0 RO 0 13 MEMP R/W 0 RO 0 12 USAGEP R/W 0 RO 0 11 TICK R/W 0 RO 0 10 PNDSV R/W 0 RO 0 9
reserved
24
23
22
21
20
19
18 USAGE
17 BUS R/W 0 1 BUSA R/W 0
16 MEM R/W 0 0 MEMA R/W 0
RO 0 8 MON R/W 0
RO 0 7 SVCA R/W 0
RO 0 6
RO 0 5 reserved
RO 0 4
RO 0 3 USGA
R/W 0 2
reserved
RO 0
RO 0
RO 0
RO 0
R/W 0
RO 0
Bit/Field 31:19
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Usage Fault Enable Value Description 0 1 Disables the usage fault exception. Enables the usage fault exception.
18
USAGE
R/W
17
BUS
R/W
Bus Fault Enable Value Description 0 1 Disables the bus fault exception. Enables the bus fault exception.
169
Bit/Field 16
Name MEM
Type R/W
Reset 0
Description Memory Management Fault Enable Value Description 0 1 Disables the memory management fault exception. Enables the memory management fault exception.
15
SVC
R/W
SVC Call Pending Value Description 0 1 An SVC call exception is not pending. An SVC call exception is pending.
This bit can be modified to change the pending status of the SVC call exception. 14 BUSP R/W 0 Bus Fault Pending Value Description 0 1 A bus fault exception is not pending. A bus fault exception is pending.
This bit can be modified to change the pending status of the bus fault exception. 13 MEMP R/W 0 Memory Management Fault Pending Value Description 0 1 A memory management fault exception is not pending. A memory management fault exception is pending.
This bit can be modified to change the pending status of the memory management fault exception. 12 USAGEP R/W 0 Usage Fault Pending Value Description 0 1 A usage fault exception is not pending. A usage fault exception is pending.
This bit can be modified to change the pending status of the usage fault exception. 11 TICK R/W 0 SysTick Exception Active Value Description 0 1 A SysTick exception is not active. A SysTick exception is active.
This bit can be modified to change the active status of the SysTick exception, however, see the Caution above before setting this bit.
April 25, 2012
Bit/Field 10
Name PNDSV
Type R/W
Reset 0
Description PendSV Exception Active Value Description 0 1 A PendSV exception is not active. A PendSV exception is active.
This bit can be modified to change the active status of the PendSV exception, however, see the Caution above before setting this bit. 9 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Debug Monitor Active Value Description 0 1 The Debug monitor is not active. The Debug monitor is active.
MON
R/W
SVCA
R/W
SVC Call Active Value Description 0 1 SVC call is not active. SVC call is active.
This bit can be modified to change the active status of the SVC call exception, however, see the Caution above before setting this bit. 6:4 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Usage Fault Active Value Description 0 1 Usage fault is not active. Usage fault is active.
USGA
R/W
This bit can be modified to change the active status of the usage fault exception, however, see the Caution above before setting this bit. 2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Bus Fault Active Value Description 0 1 Bus fault is not active. Bus fault is active.
BUSA
R/W
This bit can be modified to change the active status of the bus fault exception, however, see the Caution above before setting this bit.
171
Bit/Field 0
Name MEMA
Type R/W
Reset 0
Description Memory Management Fault Active Value Description 0 1 Memory management fault is not active. Memory management fault is active.
This bit can be modified to change the active status of the memory management fault exception, however, see the Caution above before setting this bit.
April 25, 2012
Register 76: Configurable Fault Status (FAULTSTAT), offset 0xD28

Note: This register can only be accessed from privileged mode. The FAULTSTAT register indicates the cause of a memory management fault, bus fault, or usage fault. Each of these functions is assigned to a subregister as follows: Usage Fault Status (UFAULTSTAT), bits 31:16 Bus Fault Status (BFAULTSTAT), bits 15:8 Memory Management Fault Status (MFAULTSTAT), bits 7:0 FAULTSTAT is byte accessible. FAULTSTAT or its subregisters can be accessed as follows: The complete FAULTSTAT register, with a word access to offset 0xD28 The MFAULTSTAT, with a byte access to offset 0xD28 The MFAULTSTAT and BFAULTSTAT, with a halfword access to offset 0xD28 The BFAULTSTAT, with a byte access to offset 0xD29 The UFAULTSTAT, with a halfword access to offset 0xD2A
Bits are cleared by writing a 1 to them. In a fault handler, the true faulting address can be determined by: 1. Read and save the Memory Management Fault Address (MMADDR) or Bus Fault Address (FAULTADDR) value. 2. Read the MMARV bit in MFAULTSTAT, or the BFARV bit in BFAULTSTAT to determine if the MMADDR or FAULTADDR contents are valid. Software must follow this sequence because another higher priority exception might change the MMADDR or FAULTADDR value. For example, if a higher priority handler preempts the current fault handler, the other fault might change the MMADDR or FAULTADDR value.
Configurable Fault Status (FAULTSTAT)
Base 0xE000.E000 Offset 0xD28 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 DIV0 RO 0 11 BUSTKE R/W1C 0 RO 0 10 IMPRE R/W1C 0 R/W1C 0 9 PRECISE R/W1C 0 24 UNALIGN R/W1C 0 8 IBUS R/W1C 0 RO 0 7 MMARV R/W1C 0 23 22 21 20 19 NOCP RO 0 4 R/W1C 0 3 MUSTKE R/W1C 0 18 INVPC R/W1C 0 2
reserved
17 INVSTAT R/W1C 0 1 DERR R/W1C 0
16 UNDEF R/W1C 0 0 IERR R/W1C 0
reserved Type Reset RO 0 15 BFARV Type Reset R/W1C 0 RO 0 14

reserved
reserved RO 0 6
reserved
RO 0 13
RO 0 12
RO 0 5
BLSPERR BSTKE R/W1C 0 R/W1C 0
MLSPERR MSTKE R/W1C 0 R/W1C 0
RO 0
RO 0
RO 0
Bit/Field 31:26
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
173
Bit/Field 25
Name DIV0
Type R/W1C
Reset 0
Description Divide-by-Zero Usage Fault Value Description 0 1 No divide-by-zero fault has occurred, or divide-by-zero trapping is not enabled. The processor has executed an SDIV or UDIV instruction with a divisor of 0.
When this bit is set, the PC value stacked for the exception return points to the instruction that performed the divide by zero. Trapping on divide-by-zero is enabled by setting the DIV0 bit in the Configuration and Control (CFGCTRL) register (see page 164). This bit is cleared by writing a 1 to it. 24 UNALIGN R/W1C 0 Unaligned Access Usage Fault Value Description 0 1 No unaligned access fault has occurred, or unaligned access trapping is not enabled. The processor has made an unaligned memory access.
Unaligned LDM, STM, LDRD, and STRD instructions always fault regardless of the configuration of this bit. Trapping on unaligned access is enabled by setting the UNALIGNED bit in the CFGCTRL register (see page 164). This bit is cleared by writing a 1 to it. 23:20 reserved RO 0x00 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. No Coprocessor Usage Fault Value Description 0 1 A usage fault has not been caused by attempting to access a coprocessor. The processor has attempted to access a coprocessor.
19
NOCP
R/W1C
This bit is cleared by writing a 1 to it. 18 INVPC R/W1C 0 Invalid PC Load Usage Fault Value Description 0 1 A usage fault has not been caused by attempting to load an invalid PC value. The processor has attempted an illegal load of EXC_RETURN to the PC as a result of an invalid context or an invalid EXC_RETURN value.
When this bit is set, the PC value stacked for the exception return points to the instruction that tried to perform the illegal load of the PC. This bit is cleared by writing a 1 to it.
April 25, 2012
Bit/Field 17
Name INVSTAT
Type R/W1C
Reset 0
Description Invalid State Usage Fault Value Description 0 1 A usage fault has not been caused by an invalid state. The processor has attempted to execute an instruction that makes illegal use of the EPSR register.
When this bit is set, the PC value stacked for the exception return points to the instruction that attempted the illegal use of the Execution Program Status Register (EPSR) register. This bit is not set if an undefined instruction uses the EPSR register. This bit is cleared by writing a 1 to it. 16 UNDEF R/W1C 0 Undefined Instruction Usage Fault Value Description 0 1 A usage fault has not been caused by an undefined instruction. The processor has attempted to execute an undefined instruction.
When this bit is set, the PC value stacked for the exception return points to the undefined instruction. An undefined instruction is an instruction that the processor cannot decode. This bit is cleared by writing a 1 to it. 15 BFARV R/W1C 0 Bus Fault Address Register Valid Value Description 0 1 The value in the Bus Fault Address (FAULTADDR) register is not a valid fault address. The FAULTADDR register is holding a valid fault address.
This bit is set after a bus fault, where the address is known. Other faults can clear this bit, such as a memory management fault occurring later. If a bus fault occurs and is escalated to a hard fault because of priority, the hard fault handler must clear this bit. This action prevents problems if returning to a stacked active bus fault handler whose FAULTADDR register value has been overwritten. This bit is cleared by writing a 1 to it. 14 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Bus Fault on Floating-Point Lazy State Preservation Value Description 0 1 No bus fault has occurred during floating-point lazy state preservation. A bus fault has occurred during floating-point lazy state preservation.
13
BLSPERR
R/W1C
This bit is cleared by writing a 1 to it.
175
Bit/Field 12
Name BSTKE
Type R/W1C
Reset 0
Description Stack Bus Fault Value Description 0 1 No bus fault has occurred on stacking for exception entry. Stacking for an exception entry has caused one or more bus faults.
When this bit is set, the SP is still adjusted but the values in the context area on the stack might be incorrect. A fault address is not written to the FAULTADDR register. This bit is cleared by writing a 1 to it. 11 BUSTKE R/W1C 0 Unstack Bus Fault Value Description 0 1 No bus fault has occurred on unstacking for a return from exception. Unstacking for a return from exception has caused one or more bus faults.
This fault is chained to the handler. Thus, when this bit is set, the original return stack is still present. The SP is not adjusted from the failing return, a new save is not performed, and a fault address is not written to the FAULTADDR register. This bit is cleared by writing a 1 to it. 10 IMPRE R/W1C 0 Imprecise Data Bus Error Value Description 0 1 An imprecise data bus error has not occurred. A data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error.
When this bit is set, a fault address is not written to the FAULTADDR register. This fault is asynchronous. Therefore, if the fault is detected when the priority of the current process is higher than the bus fault priority, the bus fault becomes pending and becomes active only when the processor returns from all higher-priority processes. If a precise fault occurs before the processor enters the handler for the imprecise bus fault, the handler detects that both the IMPRE bit is set and one of the precise fault status bits is set. This bit is cleared by writing a 1 to it. 9 PRECISE R/W1C 0 Precise Data Bus Error Value Description 0 1 A precise data bus error has not occurred. A data bus error has occurred, and the PC value stacked for the exception return points to the instruction that caused the fault.
When this bit is set, the fault address is written to the FAULTADDR register. This bit is cleared by writing a 1 to it.
April 25, 2012
Bit/Field 8
Name IBUS
Type R/W1C
Reset 0
Description Instruction Bus Error Value Description 0 1 An instruction bus error has not occurred. An instruction bus error has occurred.
The processor detects the instruction bus error on prefetching an instruction, but sets this bit only if it attempts to issue the faulting instruction. When this bit is set, a fault address is not written to the FAULTADDR register. This bit is cleared by writing a 1 to it. 7 MMARV R/W1C 0 Memory Management Fault Address Register Valid Value Description 0 1 The value in the Memory Management Fault Address (MMADDR) register is not a valid fault address. The MMADDR register is holding a valid fault address.
If a memory management fault occurs and is escalated to a hard fault because of priority, the hard fault handler must clear this bit. This action prevents problems if returning to a stacked active memory management fault handler whose MMADDR register value has been overwritten. This bit is cleared by writing a 1 to it. 6 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Memory Management Fault on Floating-Point Lazy State Preservation Value Description 0 1 No memory management fault has occurred during floating-point lazy state preservation. No memory management fault has occurred during floating-point lazy state preservation.
MLSPERR
R/W1C
This bit is cleared by writing a 1 to it. 4 MSTKE R/W1C 0 Stack Access Violation Value Description 0 1 No memory management fault has occurred on stacking for exception entry. Stacking for an exception entry has caused one or more access violations.
When this bit is set, the SP is still adjusted but the values in the context area on the stack might be incorrect. A fault address is not written to the MMADDR register. This bit is cleared by writing a 1 to it.
177
Bit/Field 3
Name MUSTKE
Type R/W1C
Reset 0
Description Unstack Access Violation Value Description 0 1 No memory management fault has occurred on unstacking for a return from exception. Unstacking for a return from exception has caused one or more access violations.
This fault is chained to the handler. Thus, when this bit is set, the original return stack is still present. The SP is not adjusted from the failing return, a new save is not performed, and a fault address is not written to the MMADDR register. This bit is cleared by writing a 1 to it. 2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Data Access Violation Value Description 0 1 A data access violation has not occurred. The processor attempted a load or store at a location that does not permit the operation.
DERR
R/W1C
When this bit is set, the PC value stacked for the exception return points to the faulting instruction and the address of the attempted access is written to the MMADDR register. This bit is cleared by writing a 1 to it. 0 IERR R/W1C 0 Instruction Access Violation Value Description 0 1 An instruction access violation has not occurred. The processor attempted an instruction fetch from a location that does not permit execution.
This fault occurs on any access to an XN region, even when the MPU is disabled or not present. When this bit is set, the PC value stacked for the exception return points to the faulting instruction and the address of the attempted access is not written to the MMADDR register. This bit is cleared by writing a 1 to it.
April 25, 2012
Register 77: Hard Fault Status (HFAULTSTAT), offset 0xD2C

Note: This register can only be accessed from privileged mode. The HFAULTSTAT register gives information about events that activate the hard fault handler. Bits are cleared by writing a 1 to them.
Hard Fault Status (HFAULTSTAT)
Base 0xE000.E000 Offset 0xD2C Type R/W1C, reset 0x0000.0000
31 DBG Type Reset R/W1C 0 15 30 FORCED R/W1C 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 VECT R/W1C 0 RO 0 0

reserved
RO 0
Bit/Field 31
Name DBG
Type R/W1C
Reset 0
Description Debug Event This bit is reserved for Debug use. This bit must be written as a 0, otherwise behavior is unpredictable.
30
FORCED
R/W1C
Forced Hard Fault Value Description 0 1 No forced hard fault has occurred. A forced hard fault has been generated by escalation of a fault with configurable priority that cannot be handled, either because of priority or because it is disabled.
When this bit is set, the hard fault handler must read the other fault status registers to find the cause of the fault. This bit is cleared by writing a 1 to it. 29:2 reserved RO 0x00 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Vector Table Read Fault Value Description 0 1 No bus fault has occurred on a vector table read. A bus fault occurred on a vector table read.
VECT
R/W1C
This error is always handled by the hard fault handler. When this bit is set, the PC value stacked for the exception return points to the instruction that was preempted by the exception. This bit is cleared by writing a 1 to it. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
179
Register 78: Memory Management Fault Address (MMADDR), offset 0xD34

Note: This register can only be accessed from privileged mode. The MMADDR register contains the address of the location that generated a memory management fault. When an unaligned access faults, the address in the MMADDR register is the actual address that faulted. Because a single read or write instruction can be split into multiple aligned accesses, the fault address can be any address in the range of the requested access size. Bits in the Memory Management Fault Status (MFAULTSTAT) register indicate the cause of the fault and whether the value in the MMADDR register is valid (see page 173).
Memory Management Fault Address (MMADDR)
Base 0xE000.E000 Offset 0xD34 Type R/W, reset 31 30 29 28 27 26 25 24 ADDR Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 ADDR Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name ADDR
Type R/W
Reset -
Description Fault Address When the MMARV bit of MFAULTSTAT is set, this field holds the address of the location that generated the memory management fault.
April 25, 2012
Register 79: Bus Fault Address (FAULTADDR), offset 0xD38

Note: This register can only be accessed from privileged mode. The FAULTADDR register contains the address of the location that generated a bus fault. When an unaligned access faults, the address in the FAULTADDR register is the one requested by the instruction, even if it is not the address of the fault. Bits in the Bus Fault Status (BFAULTSTAT) register indicate the cause of the fault and whether the value in the FAULTADDR register is valid (see page 173).
Bus Fault Address (FAULTADDR)
Base 0xE000.E000 Offset 0xD38 Type R/W, reset 31 30 29 28 27 26 25 24 ADDR Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 ADDR Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name ADDR
Type R/W
Reset -
Description Fault Address When the FAULTADDRV bit of BFAULTSTAT is set, this field holds the address of the location that generated the bus fault.
3.6
Memory Protection Unit (MPU) Register Descriptions

This section lists and describes the Memory Protection Unit (MPU) registers, in numerical order by address offset. The MPU registers can only be accessed from privileged mode.
181
Register 80: MPU Type (MPUTYPE), offset 0xD90

Note: This register can only be accessed from privileged mode. The MPUTYPE register indicates whether the MPU is present, and if so, how many regions it supports.
MPU Type (MPUTYPE)
Base 0xE000.E000 Offset 0xD90 Type RO, reset 0x0000.0800
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5
IREGION RO 0 4 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
SEPARATE
DREGION Type Reset RO 0 RO 0 RO 0 RO 0 RO 1
RO 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Number of I Regions This field indicates the number of supported MPU instruction regions. This field always contains 0x00. The MPU memory map is unified and is described by the DREGION field.
23:16
IREGION
RO
0x00
15:8
DREGION
RO
0x08
Number of D Regions Value Description 0x08 Indicates there are eight supported MPU data regions.
7:1
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Separate or Unified MPU Value Description 0 Indicates the MPU is unified.
SEPARATE
RO
April 25, 2012
Register 81: MPU Control (MPUCTRL), offset 0xD94

Note: This register can only be accessed from privileged mode. The MPUCTRL register enables the MPU, enables the default memory map background region, and enables use of the MPU when in the hard fault, Non-maskable Interrupt (NMI), and Fault Mask Register (FAULTMASK) escalated handlers. When the ENABLE and PRIVDEFEN bits are both set: For privileged accesses, the default memory map is as described in Memory Model on page 88. Any access by privileged software that does not address an enabled memory region behaves as defined by the default memory map. Any access by unprivileged software that does not address an enabled memory region causes a memory management fault. Execute Never (XN) and Strongly Ordered rules always apply to the System Control Space regardless of the value of the ENABLE bit. When the ENABLE bit is set, at least one region of the memory map must be enabled for the system to function unless the PRIVDEFEN bit is set. If the PRIVDEFEN bit is set and no regions are enabled, then only privileged software can operate. When the ENABLE bit is clear, the system uses the default memory map, which has the same memory attributes as if the MPU is not implemented (see Table 2-5 on page 91 for more information). The default memory map applies to accesses from both privileged and unprivileged software. When the MPU is enabled, accesses to the System Control Space and vector table are always permitted. Other areas are accessible based on regions and whether PRIVDEFEN is set. Unless HFNMIENA is set, the MPU is not enabled when the processor is executing the handler for an exception with priority 1 or 2. These priorities are only possible when handling a hard fault or NMI exception or when FAULTMASK is enabled. Setting the HFNMIENA bit enables the MPU when operating with these two priorities.
MPU Control (MPUCTRL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 ENABLE R/W 0
PRIVDEFEN HFNMIENA
R/W 0
R/W 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
183
Bit/Field 2
Name PRIVDEFEN
Type R/W
Reset 0
Description MPU Default Region This bit enables privileged software access to the default memory map. Value Description 0 If the MPU is enabled, this bit disables use of the default memory map. Any memory access to a location not covered by any enabled region causes a fault. If the MPU is enabled, this bit enables use of the default memory map as a background region for privileged software accesses.
When this bit is set, the background region acts as if it is region number -1. Any region that is defined and enabled has priority over this default map. If the MPU is disabled, the processor ignores this bit. 1 HFNMIENA R/W 0 MPU Enabled During Faults This bit controls the operation of the MPU during hard fault, NMI, and FAULTMASK handlers. Value Description 0 1 The MPU is disabled during hard fault, NMI, and FAULTMASK handlers, regardless of the value of the ENABLE bit. The MPU is enabled during hard fault, NMI, and FAULTMASK handlers.
When the MPU is disabled and this bit is set, the resulting behavior is unpredictable. 0 ENABLE R/W 0 MPU Enable Value Description 0 1 The MPU is disabled. The MPU is enabled.
When the MPU is disabled and the HFNMIENA bit is set, the resulting behavior is unpredictable.
April 25, 2012
Register 82: MPU Region Number (MPUNUMBER), offset 0xD98

Note: This register can only be accessed from privileged mode. The MPUNUMBER register selects which memory region is referenced by the MPU Region Base Address (MPUBASE) and MPU Region Attribute and Size (MPUATTR) registers. Normally, the required region number should be written to this register before accessing the MPUBASE or the MPUATTR register. However, the region number can be changed by writing to the MPUBASE register with the VALID bit set (see page 186). This write updates the value of the REGION field.
MPU Region Number (MPUNUMBER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 NUMBER R/W 0 R/W 0 RO 0 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. MPU Region to Access This field indicates the MPU region referenced by the MPUBASE and MPUATTR registers. The MPU supports eight memory regions.
2:0
NUMBER
R/W
0x0
185
Register 83: MPU Region Base Address (MPUBASE), offset 0xD9C Register 84: MPU Region Base Address Alias 1 (MPUBASE1), offset 0xDA4 Register 85: MPU Region Base Address Alias 2 (MPUBASE2), offset 0xDAC Register 86: MPU Region Base Address Alias 3 (MPUBASE3), offset 0xDB4
Note: This register can only be accessed from privileged mode. The MPUBASE register defines the base address of the MPU region selected by the MPU Region Number (MPUNUMBER) register and can update the value of the MPUNUMBER register. To change the current region number and update the MPUNUMBER register, write the MPUBASE register with the VALID bit set. The ADDR field is bits 31:N of the MPUBASE register. Bits (N-1):5 are reserved. The region size, as specified by the SIZE field in the MPU Region Attribute and Size (MPUATTR) register, defines the value of N where: N = Log2(Region size in bytes) If the region size is configured to 4 GB in the MPUATTR register, there is no valid ADDR field. In this case, the region occupies the complete memory map, and the base address is 0x0000.0000. The base address is aligned to the size of the region. For example, a 64-KB region must be aligned on a multiple of 64 KB, for example, at 0x0001.0000 or 0x0002.0000.
MPU Region Base Address (MPUBASE)
Base 0xE000.E000 Offset 0xD9C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 ADDR Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 ADDR Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 VALID WO 0 R/W 0 3
reserved
23
22
21
20
19
18
17
16
R/W 0 2
R/W 0 1 REGION
R/W 0 0
RO 0
R/W 0
R/W 0
R/W 0
Bit/Field 31:5
Name ADDR
Type R/W
Reset 0x0000.000
Description Base Address Mask Bits 31:N in this field contain the region base address. The value of N depends on the region size, as shown above. The remaining bits (N-1):5 are reserved. Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Bit/Field 4
Name VALID
Type WO
Reset 0
Description Region Number Valid Value Description 0 The MPUNUMBER register is not changed and the processor updates the base address for the region specified in the MPUNUMBER register and ignores the value of the REGION field. The MPUNUMBER register is updated with the value of the REGION field and the base address is updated for the region specified in the REGION field.
This bit is always read as 0. 3 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Region Number On a write, contains the value to be written to the MPUNUMBER register. On a read, returns the current region number in the MPUNUMBER register.
2:0
REGION
R/W
0x0
187
Register 87: MPU Region Attribute and Size (MPUATTR), offset 0xDA0 Register 88: MPU Region Attribute and Size Alias 1 (MPUATTR1), offset 0xDA8 Register 89: MPU Region Attribute and Size Alias 2 (MPUATTR2), offset 0xDB0 Register 90: MPU Region Attribute and Size Alias 3 (MPUATTR3), offset 0xDB8
Note: This register can only be accessed from privileged mode. The MPUATTR register defines the region size and memory attributes of the MPU region specified by the MPU Region Number (MPUNUMBER) register and enables that region and any subregions. The MPUATTR register is accessible using word or halfword accesses with the most-significant halfword holding the region attributes and the least-significant halfword holds the region size and the region and subregion enable bits. The MPU access permission attribute bits, XN, AP, TEX, S, C, and B, control access to the corresponding memory region. If an access is made to an area of memory without the required permissions, then the MPU generates a permission fault. The SIZE field defines the size of the MPU memory region specified by the MPUNUMBER register as follows: (Region size in bytes) = 2(SIZE+1) The smallest permitted region size is 32 bytes, corresponding to a SIZE value of 4. Table 3-10 on page 188 gives example SIZE values with the corresponding region size and value of N in the MPU Region Base Address (MPUBASE) register. Table 3-10. Example SIZE Field Values
SIZE Encoding 00100b (0x4) 01001b (0x9) 10011b (0x13) 11101b (0x1D) 11111b (0x1F) Region Size 32 B 1 KB 1 MB 1 GB 4 GB Value of N 5 10 20 30
a
Note Minimum permitted size -
No valid ADDR field in MPUBASE; the Maximum possible size region occupies the complete memory map.
a. Refers to the N parameter in the MPUBASE register (see page 186).
MPU Region Attribute and Size (MPUATTR)

Base 0xE000.E000 Offset 0xDA0 Type R/W, reset 0x0000.0000
31 30 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 29 28 XN R/W 0 12 SRD Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 27
reserved
26
25 AP
24
23
22
21
20 TEX
19
18 S
17 C R/W 0 1
16 B R/W 0 0 ENABLE
reserved R/W 0 8 RO 0 7 reserved RO 0 RO 0 R/W 0 RO 0 6 R/W 0 5
RO 0 11
R/W 0 10
R/W 0 9
R/W 0 4
R/W 0 3 SIZE
R/W 0 2
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
April 25, 2012
Bit/Field 31:29
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Instruction Access Disable Value Description 0 1 Instruction fetches are enabled. Instruction fetches are disabled.
28
XN
R/W
27
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Access Privilege For information on using this bit field, see Table 3-5 on page 125.
26:24
AP
R/W
23:22
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Type Extension Mask For information on using this bit field, see Table 3-3 on page 124.
21:19
TEX
R/W
0x0
18
R/W
Shareable For information on using this bit, see Table 3-3 on page 124.
17
R/W
Cacheable For information on using this bit, see Table 3-3 on page 124.
16
R/W
Bufferable For information on using this bit, see Table 3-3 on page 124.
15:8
SRD
R/W
0x00
Subregion Disable Bits Value Description 0 1 The corresponding subregion is enabled. The corresponding subregion is disabled.
Region sizes of 128 bytes and less do not support subregions. When writing the attributes for such a region, configure the SRD field as 0x00. See the section called Subregions on page 124 for more information. 7:6 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Region Size Mask The SIZE field defines the size of the MPU memory region specified by the MPUNUMBER register. Refer to Table 3-10 on page 188 for more information.
5:1
SIZE
R/W
0x0
189
Bit/Field 0
Name ENABLE
Type R/W
Reset 0
Description Region Enable Value Description 0 1 The region is disabled. The region is enabled.
3.7
Floating-Point Unit (FPU) Register Descriptions

This section lists and describes the Floating-Point Unit (FPU) registers, in numerical order by address offset.
April 25, 2012
Register 91: Coprocessor Access Control (CPAC), offset 0xD88

The CPAC register specifies the access privileges for coprocessors.
Coprocessor Access Control (CPAC)
31 30 29 28 27 26 25 24 23 CP11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 7 R/W 0 6 R/W 0 5 22 21 CP10 R/W 0 4 RO 0 3 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11
reserved RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CP11 Coprocessor Access Privilege Value Description 0x0 0x1 0x2 0x3 Access Denied Any attempted access generates a NOCP Usage Fault. Privileged Access Only An unprivileged access generates a NOCP fault. Reserved The result of any access is unpredictable. Full Access
23:22
CP11
R/W
0x00
21:20
CP10
R/W
0x00
CP10 Coprocessor Access Privilege Value Description 0x0 0x1 0x2 0x3 Access Denied Any attempted access generates a NOCP Usage Fault. Privileged Access Only An unprivileged access generates a NOCP fault. Reserved The result of any access is unpredictable. Full Access
19:0
reserved
RO
0x00
191
Register 92: Floating-Point Context Control (FPCC), offset 0xF34

The FPCC register sets or returns FPU control data.
Floating-Point Context Control (FPCC)
Base 0xE000.E000 Offset 0xF34 Type R/W, reset 0xC000.0000
31 ASPEN Type Reset R/W 1 15 30 LSPEN R/W 1 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 MONRDY R/W 0 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved RO 0 7
reserved
RO 0 6 BFRDY R/W 0
RO 0 5 MMRDY R/W 0
RO 0 4 HFRDY R/W 0
RO 0 3 THREAD R/W 0
RO 0 2
reserved
RO 0 1 USER R/W 0
RO 0 0 LSPACT R/W 0
RO 0
RO 0
Bit/Field 31
Name ASPEN
Type R/W
Reset 1
Description Automatic State Preservation Enable When set, enables the use of the FRACTV bit in the CONTROL register on execution of a floating-point instruction. This results in automatic hardware state preservation and restoration, for floating-point context, on exception entry and exit.
Important:
30
LSPEN
R/W
Lazy State Preservation Enable When set, enables automatic lazy state preservation for floating-point context.
29:9
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Monitor Ready When set, DebugMonitor is enabled and priority permits setting MON_PEND when the floating-point stack frame was allocated.
MONRDY
R/W
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Bus Fault Ready When set, BusFault is enabled and priority permitted setting the BusFault handler to the pending state when the floating-point stack frame was allocated.
BFRDY
R/W
MMRDY
R/W
Memory Management Fault Ready When set, MemManage is enabled and priority permitted setting the MemManage handler to the pending state when the floating-point stack frame was allocated.
April 25, 2012
Bit/Field 4
Name HFRDY
Type R/W
Reset 0
Description Hard Fault Ready When set, priority permitted setting the HardFault handler to the pending state when the floating-point stack frame was allocated.
THREAD
R/W
Thread Mode When set, mode was Thread Mode when the floating-point stack frame was allocated.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. User Privilege Level When set, privilege level was user when the floating-point stack frame was allocated.
USER
R/W
LSPACT
R/W
Lazy State Preservation Active When set, Lazy State preservation is active. Floating-point stack frame has been allocated but saving state to it has been deferred.
193
Register 93: Floating-Point Context Address (FPCA), offset 0xF38

The FPCA register holds the location of the unpopulated floating-point register space allocated on an exception stack frame.
Floating-Point Context Address (FPCA)
Base 0xE000.E000 Offset 0xF38 Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
ADDRESS Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 ADDRESS Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W RO 0 R/W 8 R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 reserved RO 0 RO 0 R/W 0
Bit/Field 31:3
Name ADDRESS
Type R/W
Reset -
Description Address The location of the unpopulated floating-point register space allocated on an exception stack frame.
2:0
reserved
RO
0x00
April 25, 2012
Register 94: Floating-Point Default Status Control (FPDSC), offset 0xF3C

The FPDSC register holds the default values for the Floating-Point Status Control (FPSC) register.
Floating-Point Default Status Control (FPDSC)
Base 0xE000.E000 Offset 0xF3C Type R/W, reset 0x0000.0000
31 30 29 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 28 27 26 AHP R/W 10 25 DN R/W 9 24 FZ R/W 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 23 RMODE R/W 7 R/W 6 RO 0 5 RO 0 4 22 21 20 19 18 17 16
reserved RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:27
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. AHP Bit Default This bit holds the default value for the AHP bit in the FPSC register.
26
AHP
R/W
25
DN
R/W
DN Bit Default This bit holds the default value for the DN bit in the FPSC register.
24
FZ
R/W
FZ Bit Default This bit holds the default value for the FZ bit in the FPSC register.
23:22
RMODE
R/W
RMODE Bit Default This bit holds the default value for the RMODE bit field in the FPSC register. Value Description 0x0 0x1 0x2 0x3 Round to Nearest (RN) mode Round towards Plus Infinity (RP) mode Round towards Minus Infinity (RM) mode Round towards Zero (RZ) mode
21:0
reserved
RO
0x00
195
JTAG Interface
JTAG Interface
The Joint Test Action Group (JTAG) port is an IEEE standard that defines a Test Access Port and Boundary Scan Architecture for digital integrated circuits and provides a standardized serial interface for controlling the associated test logic. The TAP, Instruction Register (IR), and Data Registers (DR) can be used to test the interconnections of assembled printed circuit boards and obtain manufacturing information on the components. The JTAG Port also provides a means of accessing and controlling design-for-test features such as I/O pin observation and control, scan testing, and debugging. The JTAG port is comprised of four pins: TCK, TMS, TDI, and TDO. Data is transmitted serially into the controller on TDI and out of the controller on TDO. The interpretation of this data is dependent on the current state of the TAP controller. For detailed information on the operation of the JTAG port and TAP controller, please refer to the IEEE Standard 1149.1-Test Access Port and Boundary-Scan Architecture. The Stellaris JTAG controller works with the ARM JTAG controller built into the Cortex-M4F core by multiplexing the TDO outputs from both JTAG controllers. ARM JTAG instructions select the ARM TDO output while Stellaris JTAG instructions select the Stellaris TDO output. The multiplexer is controlled by the Stellaris JTAG controller, which has comprehensive programming for the ARM, Stellaris, and unimplemented JTAG instructions. The Stellaris JTAG module has the following features: IEEE 1149.1-1990 compatible Test Access Port (TAP) controller Four-bit Instruction Register (IR) chain for storing JTAG instructions IEEE standard instructions: BYPASS, IDCODE, SAMPLE/PRELOAD, EXTEST and INTEST ARM additional instructions: APACC, DPACC and ABORT Integrated ARM Serial Wire Debug (SWD) Serial Wire JTAG Debug Port (SWJ-DP) Flash Patch and Breakpoint (FPB) unit for implementing breakpoints Data Watchpoint and Trace (DWT) unit for implementing watchpoints, trigger resources, and system profiling Instrumentation Trace Macrocell (ITM) for support of printf style debugging Embedded Trace Macrocell (ETM) for instruction trace capture Trace Port Interface Unit (TPIU) for bridging to a Trace Port Analyzer See the ARM Debug Interface V5 Architecture Specification for more information on the ARM JTAG controller.
April 25, 2012
4.1
Block Diagram
Figure 4-1. JTAG Module Block Diagram
TCK TMS
TAP Controller
TDI
Instruction Register (IR)
BYPASS Data Register Boundary Scan Data Register IDCODE Data Register ABORT Data Register DPACC Data Register APACC Data Register
TDO
Cortex-M4F Debug Port
4.2
Signal Description
The following table lists the external signals of the JTAG/SWD controller and describes the function of each. The JTAG/SWD controller signals are alternate functions for some GPIO signals, however note that the reset state of the pins is for the JTAG/SWD function. The JTAG/SWD controller signals are under commit protection and require a special process to be configured as GPIOs, see Commit Control on page 639. The column in the table below titled "Pin Mux/Pin Assignment" lists the GPIO pin placement for the JTAG/SWD controller signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) is set to choose the JTAG/SWD function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the JTAG/SWD controller signals to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
Table 4-1. JTAG_SWD_SWO Signals (64LQFP)

Pin Name SWCLK SWDIO SWO TCK TDI TDO Pin Number Pin Mux / Pin Assignment 52 51 49 52 50 49 PC0 (1) PC1 (1) PC3 (1) PC0 (1) PC2 (1) PC3 (1) Pin Type I I/O O I I O Buffer Type TTL TTL TTL TTL TTL TTL
a
Description JTAG/SWD CLK. JTAG TMS and SWDIO. JTAG TDO and SWO. JTAG/SWD CLK. JTAG TDI. JTAG TDO and SWO.
197
JTAG Interface
Table 4-1. JTAG_SWD_SWO Signals (64LQFP) (continued)

Pin Name TMS Pin Number Pin Mux / Pin Assignment 51 PC1 (1) Pin Type I Buffer Type TTL
a
Description JTAG TMS and SWDIO.
a. The TTL designation indicates the pin has TTL-compatible voltage levels.
4.3
A high-level conceptual drawing of the JTAG module is shown in Figure 4-1 on page 197. The JTAG module is composed of the Test Access Port (TAP) controller and serial shift chains with parallel update registers. The TAP controller is a simple state machine controlled by the TCK and TMS inputs. The current state of the TAP controller depends on the sequence of values captured on TMS at the rising edge of TCK. The TAP controller determines when the serial shift chains capture new data, shift data from TDI towards TDO, and update the parallel load registers. The current state of the TAP controller also determines whether the Instruction Register (IR) chain or one of the Data Register (DR) chains is being accessed. The serial shift chains with parallel load registers are comprised of a single Instruction Register (IR) chain and multiple Data Register (DR) chains. The current instruction loaded in the parallel load register determines which DR chain is captured, shifted, or updated during the sequencing of the TAP controller. Some instructions, like EXTEST and INTEST, operate on data currently in a DR chain and do not capture, shift, or update any of the chains. Instructions that are not implemented decode to the BYPASS instruction to ensure that the serial path between TDI and TDO is always connected (see Table 4-3 on page 204 for a list of implemented instructions). See JTAG and Boundary Scan on page 1161 for JTAG timing diagrams. Note: Of all the possible reset sources, only Power-On reset (POR) and the assertion of the RST input have any effect on the JTAG module. The pin configurations are reset by both the RST input and POR, whereas the internal JTAG logic is only reset with POR. See Reset Sources on page 209 for more information on reset.
4.3.1
JTAG Interface Pins

The JTAG interface consists of four standard pins: TCK, TMS, TDI, and TDO. These pins and their associated state after a power-on reset or reset caused by the RST input are given in Table 4-2. Detailed information on each pin follows. Note: The following pins are configured as JTAG port pins out of reset. Refer to General-Purpose Input/Outputs (GPIOs) on page 632 for information on how to reprogram the configuration of these pins.
Table 4-2. JTAG Port Pins State after Power-On Reset or RST assertion
Pin Name TCK TMS TDI TDO Data Direction Input Input Input Output Internal Pull-Up Enabled Enabled Enabled Enabled Internal Pull-Down Disabled Disabled Disabled Disabled Drive Strength N/A N/A N/A 2-mA driver Drive Value N/A N/A N/A High-Z
April 25, 2012
4.3.1.1
Test Clock Input (TCK)

The TCK pin is the clock for the JTAG module. This clock is provided so the test logic can operate independently of any other system clocks and to ensure that multiple JTAG TAP controllers that are daisy-chained together can synchronously communicate serial test data between components. During normal operation, TCK is driven by a free-running clock with a nominal 50% duty cycle. When necessary, TCK can be stopped at 0 or 1 for extended periods of time. While TCK is stopped at 0 or 1, the state of the TAP controller does not change and data in the JTAG Instruction and Data Registers is not lost. By default, the internal pull-up resistor on the TCK pin is enabled after reset, assuring that no clocking occurs if the pin is not driven from an external source. The internal pull-up and pull-down resistors can be turned off to save internal power as long as the TCK pin is constantly being driven by an external source (see page 659 and page 661).
4.3.1.2
Test Mode Select (TMS)

The TMS pin selects the next state of the JTAG TAP controller. TMS is sampled on the rising edge of TCK. Depending on the current TAP state and the sampled value of TMS, the next state may be entered. Because the TMS pin is sampled on the rising edge of TCK, the IEEE Standard 1149.1 expects the value on TMS to change on the falling edge of TCK. Holding TMS high for five consecutive TCK cycles drives the TAP controller state machine to the Test-Logic-Reset state. When the TAP controller enters the Test-Logic-Reset state, the JTAG module and associated registers are reset to their default values. This procedure should be performed to initialize the JTAG controller. The JTAG Test Access Port state machine can be seen in its entirety in Figure 4-2 on page 200. By default, the internal pull-up resistor on the TMS pin is enabled after reset. Changes to the pull-up resistor settings on GPIO Port C should ensure that the internal pull-up resistor remains enabled on PC1/TMS; otherwise JTAG communication could be lost (see page 659).
4.3.1.3
Test Data Input (TDI)

The TDI pin provides a stream of serial information to the IR chain and the DR chains. TDI is sampled on the rising edge of TCK and, depending on the current TAP state and the current instruction, may present this data to the proper shift register chain. Because the TDI pin is sampled on the rising edge of TCK, the IEEE Standard 1149.1 expects the value on TDI to change on the falling edge of TCK. By default, the internal pull-up resistor on the TDI pin is enabled after reset. Changes to the pull-up resistor settings on GPIO Port C should ensure that the internal pull-up resistor remains enabled on PC2/TDI; otherwise JTAG communication could be lost (see page 659).
4.3.1.4
Test Data Output (TDO)

The TDO pin provides an output stream of serial information from the IR chain or the DR chains. The value of TDO depends on the current TAP state, the current instruction, and the data in the chain being accessed. In order to save power when the JTAG port is not being used, the TDO pin is placed in an inactive drive state when not actively shifting out data. Because TDO can be connected to the TDI of another controller in a daisy-chain configuration, the IEEE Standard 1149.1 expects the value on TDO to change on the falling edge of TCK. By default, the internal pull-up resistor on the TDO pin is enabled after reset, assuring that the pin remains at a constant logic level when the JTAG port is not being used. The internal pull-up and
199
JTAG Interface
pull-down resistors can be turned off to save internal power if a High-Z output value is acceptable during certain TAP controller states (see page 659 and page 661).
4.3.2
JTAG TAP Controller

The JTAG TAP controller state machine is shown in Figure 4-2. The TAP controller state machine is reset to the Test-Logic-Reset state on the assertion of a Power-On-Reset (POR). In order to reset the JTAG module after the microcontroller has been powered on, the TMS input must be held HIGH for five TCK clock cycles, resetting the TAP controller and all associated JTAG chains. Asserting the correct sequence on the TMS pin allows the JTAG module to shift in new instructions, shift in data, or idle during extended testing sequences. For detailed information on the function of the TAP controller and the operations that occur in each state, please refer to IEEE Standard 1149.1. Figure 4-2. Test Access Port State Machine
Test Logic Reset
0 Run Test Idle 1 Select DR Scan 0 1 Capture DR 0 Shift DR 1 Exit 1 DR 0 Pause DR 1 0 Exit 2 DR 1 Update DR 1 0 0 0 0 1 1 1 Select IR Scan 0 Capture IR 0 Shift IR 1 Exit 1 IR 0 Pause IR 1 Exit 2 IR 1 Update IR 1 0 0 0 1 1
4.3.3
Shift Registers
The Shift Registers consist of a serial shift register chain and a parallel load register. The serial shift register chain samples specific information during the TAP controllers CAPTURE states and allows this information to be shifted out on TDO during the TAP controllers SHIFT states. While the sampled data is being shifted out of the chain on TDO, new data is being shifted into the serial shift register on TDI. This new data is stored in the parallel load register during the TAP controllers UPDATE states. Each of the shift registers is discussed in detail in Register Descriptions on page 203.
April 25, 2012
4.3.4
Operational Considerations
Certain operational parameters must be considered when using the JTAG module. Because the JTAG pins can be programmed to be GPIOs, board configuration and reset conditions on these pins must be considered. In addition, because the JTAG module has integrated ARM Serial Wire Debug, the method for switching between these two operational modes is described below.
4.3.4.1
GPIO Functionality
When the microcontroller is reset with either a POR or RST, the JTAG/SWD port pins default to their JTAG/SWD configurations. The default configuration includes enabling digital functionality (DEN[3:0] set in the Port C GPIO Digital Enable (GPIODEN) register), enabling the pull-up resistors (PUE[3:0] set in the Port C GPIO Pull-Up Select (GPIOPUR) register), disabling the pull-down resistors (PDE[3:0] cleared in the Port C GPIO Pull-Down Select (GPIOPDR) register) and enabling the alternate hardware function (AFSEL[3:0] set in the Port C GPIO Alternate Function Select (GPIOAFSEL) register) on the JTAG/SWD pins. See page 653, page 659, page 661, and page 664. It is possible for software to configure these pins as GPIOs after reset by clearing AFSEL[3:0] in the Port C GPIOAFSEL register. If the user does not require the JTAG/SWD port for debugging or board-level testing, this provides four more GPIOs for use in the design. Caution It is possible to create a software sequence that prevents the debugger from connecting to the Stellaris microcontroller. If the program code loaded into flash immediately changes the JTAG pins to their GPIO functionality, the debugger may not have enough time to connect and halt the controller before the JTAG pin functionality switches. As a result, the debugger may be locked out of the part. This issue can be avoided with a software routine that restores JTAG functionality based on an external or software trigger. The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware peripherals. Protection is provided for the GPIO pins that can be used as the four JTAG/SWD pins (PC[3:0])and the NMI pin (PD7 and PF0). Writes to protected bits of the GPIO Alternate Function Select (GPIOAFSEL) register (see page 653), GPIO Pull Up Select (GPIOPUR) register (see page 659), GPIO Pull-Down Select (GPIOPDR) register (see page 661), and GPIO Digital Enable (GPIODEN) register (see page 664) are not committed to storage unless the GPIO Lock (GPIOLOCK) register (see page 666) has been unlocked and the appropriate bits of the GPIO Commit (GPIOCR) register (see page 667) have been set.
4.3.4.2
Communication with JTAG/SWD

Because the debug clock and the system clock can be running at different frequencies, care must be taken to maintain reliable communication with the JTAG/SWD interface. In the Capture-DR state, the result of the previous transaction, if any, is returned, together with a 3-bit ACK response. Software should check the ACK response to see if the previous operation has completed before initiating a new transaction. Alternatively, if the system clock is at least 8 times faster than the debug clock (TCK or SWCLK), the previous operation has enough time to complete and the ACK bits do not have to be checked.
4.3.4.3
Recovering a "Locked" Microcontroller

Note: Performing the sequence below restores the non-volatile registers discussed in Non-Volatile Register Programming on page 517 to their factory default values. The mass erase of the Flash memory caused by the sequence below occurs prior to the non-volatile registers being restored. In addition, the EEPROM is erased and its wear-leveling counters are returned to factory default values when performing the sequence below.
201
JTAG Interface
If software configures any of the JTAG/SWD pins as GPIO and loses the ability to communicate with the debugger, there is a debug port unlock sequence that can be used to recover the microcontroller. Performing a total of ten JTAG-to-SWD and SWD-to-JTAG switch sequences while holding the microcontroller in reset mass erases the Flash memory. The debug port unlock sequence is: 1. Assert and hold the RST signal. 2. Apply power to the device. 3. Perform steps 1 and 2 of the JTAG-to-SWD switch sequence on the section called JTAG-to-SWD Switching on page 203. 4. Perform steps 1 and 2 of the SWD-to-JTAG switch sequence on the section called SWD-to-JTAG Switching on page 203. 5. Perform steps 1 and 2 of the JTAG-to-SWD switch sequence. 6. Perform steps 1 and 2 of the SWD-to-JTAG switch sequence. 7. Perform steps 1 and 2 of the JTAG-to-SWD switch sequence. 8. Perform steps 1 and 2 of the SWD-to-JTAG switch sequence. 9. Perform steps 1 and 2 of the JTAG-to-SWD switch sequence. 10. Perform steps 1 and 2 of the SWD-to-JTAG switch sequence. 11. Perform steps 1 and 2 of the JTAG-to-SWD switch sequence. 12. Perform steps 1 and 2 of the SWD-to-JTAG switch sequence. 13. Release the RST signal. 14. Wait 400 ms. 15. Power-cycle the microcontroller.
4.3.4.4
ARM Serial Wire Debug (SWD)

In order to seamlessly integrate the ARM Serial Wire Debug (SWD) functionality, a serial-wire debugger must be able to connect to the Cortex-M4F core without having to perform, or have any knowledge of, JTAG cycles. This integration is accomplished with a SWD preamble that is issued before the SWD session begins. The switching preamble used to enable the SWD interface of the SWJ-DP module starts with the TAP controller in the Test-Logic-Reset state. From here, the preamble sequences the TAP controller through the following states: Run Test Idle, Select DR, Select IR, Test Logic Reset, Test Logic Reset, Run Test Idle, Run Test Idle, Select DR, Select IR, Test Logic Reset, Test Logic Reset, Run Test Idle, Run Test Idle, Select DR, Select IR, and Test Logic Reset states. Stepping through this sequence of the TAP state machine enables the SWD interface and disables the JTAG interface. For more information on this operation and the SWD interface, see the ARM Debug Interface V5 Architecture Specification. Because this sequence is a valid series of JTAG operations that could be issued, the ARM JTAG TAP controller is not fully compliant to the IEEE Standard 1149.1. This instance is the only one
April 25, 2012
where the ARM JTAG TAP controller does not meet full compliance with the specification. Due to the low probability of this sequence occurring during normal operation of the TAP controller, it should not affect normal performance of the JTAG interface. JTAG-to-SWD Switching To switch the operating mode of the Debug Access Port (DAP) from JTAG to SWD mode, the external debug hardware must send the switching preamble to the microcontroller. The 16-bit TMS command for switching to SWD mode is defined as b1110.0111.1001.1110, transmitted LSB first. This command can also be represented as 0xE79E when transmitted LSB first. The complete switch sequence should consist of the following transactions on the TCK/SWCLK and TMS/SWDIO signals: 1. Send at least 50 TCK/SWCLK cycles with TMS/SWDIO High to ensure that both JTAG and SWD are in their reset/idle states. 2. Send the 16-bit JTAG-to-SWD switch command, 0xE79E, on TMS. 3. Send at least 50 TCK/SWCLK cycles with TMS/SWDIO High to ensure that if SWJ-DP was already in SWD mode, the SWD goes into the line reset state before sending the switch sequence. SWD-to-JTAG Switching To switch the operating mode of the Debug Access Port (DAP) from SWD to JTAG mode, the external debug hardware must send a switch command to the microcontroller. The 16-bit TMS command for switching to JTAG mode is defined as b1110.0111.0011.1100, transmitted LSB first. This command can also be represented as 0xE73C when transmitted LSB first. The complete switch sequence should consist of the following transactions on the TCK/SWCLK and TMS/SWDIO signals: 1. Send at least 50 TCK/SWCLK cycles with TMS/SWDIO High to ensure that both JTAG and SWD are in their reset/idle states. 2. Send the 16-bit SWD-to-JTAG switch command, 0xE73C, on TMS. 3. Send at least 50 TCK/SWCLK cycles with TMS/SWDIO High to ensure that if SWJ-DP was already in JTAG mode, the JTAG goes into the Test Logic Reset state before sending the switch sequence.
4.4
Initialization and Configuration

After a Power-On-Reset or an external reset (RST), the JTAG pins are automatically configured for JTAG communication. No user-defined initialization or configuration is needed. However, if the user application changes these pins to their GPIO function, they must be configured back to their JTAG functionality before JTAG communication can be restored. To return the pins to their JTAG functions, enable the four JTAG pins (PC[3:0]) for their alternate function using the GPIOAFSEL register. In addition to enabling the alternate functions, any other changes to the GPIO pad configurations on the four JTAG pins (PC[3:0]) should be returned to their default settings.
4.5
The registers in the JTAG TAP Controller or Shift Register chains are not memory mapped and are not accessible through the on-chip Advanced Peripheral Bus (APB). Instead, the registers within the JTAG controller are all accessed serially through the TAP Controller. These registers include the Instruction Register and the six Data Registers.
203
JTAG Interface
4.5.1
Instruction Register (IR)

The JTAG TAP Instruction Register (IR) is a four-bit serial scan chain connected between the JTAG TDI and TDO pins with a parallel load register. When the TAP Controller is placed in the correct states, bits can be shifted into the IR. Once these bits have been shifted into the chain and updated, they are interpreted as the current instruction. The decode of the IR bits is shown in Table 4-3. A detailed explanation of each instruction, along with its associated Data Register, follows. Table 4-3. JTAG Instruction Register Commands
IR[3:0] 0x0 0x1 0x2 0x8 0xA 0xB 0xE 0xF All Others Instruction EXTEST INTEST SAMPLE / PRELOAD ABORT DPACC APACC IDCODE BYPASS Reserved Description Drives the values preloaded into the Boundary Scan Chain by the SAMPLE/PRELOAD instruction onto the pads. Drives the values preloaded into the Boundary Scan Chain by the SAMPLE/PRELOAD instruction into the controller. Captures the current I/O values and shifts the sampled values out of the Boundary Scan Chain while new preload data is shifted in. Shifts data into the ARM Debug Port Abort Register. Shifts data into and out of the ARM DP Access Register. Shifts data into and out of the ARM AC Access Register. Loads manufacturing information defined by the IEEE Standard 1149.1 into the IDCODE chain and shifts it out. Connects TDI to TDO through a single Shift Register chain. Defaults to the BYPASS instruction to ensure that TDI is always connected to TDO.
4.5.1.1
EXTEST Instruction
The EXTEST instruction is not associated with its own Data Register chain. Instead, the EXTEST instruction uses the data that has been preloaded into the Boundary Scan Data Register using the SAMPLE/PRELOAD instruction. When the EXTEST instruction is present in the Instruction Register, the preloaded data in the Boundary Scan Data Register associated with the outputs and output enables are used to drive the GPIO pads rather than the signals coming from the core. With tests that drive known values out of the controller, this instruction can be used to verify connectivity. While the EXTEST instruction is present in the Instruction Register, the Boundary Scan Data Register can be accessed to sample and shift out the current data and load new data into the Boundary Scan Data Register.
4.5.1.2
INTEST Instruction
The INTEST instruction is not associated with its own Data Register chain. Instead, the INTEST instruction uses the data that has been preloaded into the Boundary Scan Data Register using the SAMPLE/PRELOAD instruction. When the INTEST instruction is present in the Instruction Register, the preloaded data in the Boundary Scan Data Register associated with the inputs are used to drive the signals going into the core rather than the signals coming from the GPIO pads. With tests that drive known values into the controller, this instruction can be used for testing. It is important to note that although the RST input pin is on the Boundary Scan Data Register chain, it is only observable. While the INTEST instruction is present in the Instruction Register, the Boundary Scan Data Register can be accessed to sample and shift out the current data and load new data into the Boundary Scan Data Register.
April 25, 2012
4.5.1.3
SAMPLE/PRELOAD Instruction
The SAMPLE/PRELOAD instruction connects the Boundary Scan Data Register chain between TDI and TDO. This instruction samples the current state of the pad pins for observation and preloads new test data. Each GPIO pad has an associated input, output, and output enable signal. When the TAP controller enters the Capture DR state during this instruction, the input, output, and output-enable signals to each of the GPIO pads are captured. These samples are serially shifted out on TDO while the TAP controller is in the Shift DR state and can be used for observation or comparison in various tests. While these samples of the inputs, outputs, and output enables are being shifted out of the Boundary Scan Data Register, new data is being shifted into the Boundary Scan Data Register from TDI. Once the new data has been shifted into the Boundary Scan Data Register, the data is saved in the parallel load registers when the TAP controller enters the Update DR state. This update of the parallel load register preloads data into the Boundary Scan Data Register that is associated with each input, output, and output enable. This preloaded data can be used with the EXTEST and INTEST instructions to drive data into or out of the controller. See Boundary Scan Data Register on page 206 for more information.
4.5.1.4
ABORT Instruction
The ABORT instruction connects the associated ABORT Data Register chain between TDI and TDO. This instruction provides read and write access to the ABORT Register of the ARM Debug Access Port (DAP). Shifting the proper data into this Data Register clears various error bits or initiates a DAP abort of a previous request. See the ABORT Data Register on page 207 for more information.
4.5.1.5
DPACC Instruction
The DPACC instruction connects the associated DPACC Data Register chain between TDI and TDO. This instruction provides read and write access to the DPACC Register of the ARM Debug Access Port (DAP). Shifting the proper data into this register and reading the data output from this register allows read and write access to the ARM debug and status registers. See DPACC Data Register on page 207 for more information.
4.5.1.6
APACC Instruction
The APACC instruction connects the associated APACC Data Register chain between TDI and TDO. This instruction provides read and write access to the APACC Register of the ARM Debug Access Port (DAP). Shifting the proper data into this register and reading the data output from this register allows read and write access to internal components and buses through the Debug Port. See APACC Data Register on page 207 for more information.
4.5.1.7
IDCODE Instruction
The IDCODE instruction connects the associated IDCODE Data Register chain between TDI and TDO. This instruction provides information on the manufacturer, part number, and version of the ARM core. This information can be used by testing equipment and debuggers to automatically configure input and output data streams. IDCODE is the default instruction loaded into the JTAG Instruction Register when a Power-On-Reset (POR) is asserted, or the Test-Logic-Reset state is entered. See IDCODE Data Register on page 206 for more information.
4.5.1.8
BYPASS Instruction
The BYPASS instruction connects the associated BYPASS Data Register chain between TDI and TDO. This instruction is used to create a minimum length serial path between the TDI and TDO ports. The BYPASS Data Register is a single-bit shift register. This instruction improves test efficiency by
205
JTAG Interface
allowing components that are not needed for a specific test to be bypassed in the JTAG scan chain by loading them with the BYPASS instruction. See BYPASS Data Register on page 206 for more information.
4.5.2
Data Registers
The JTAG module contains six Data Registers. These serial Data Register chains include: IDCODE, BYPASS, Boundary Scan, APACC, DPACC, and ABORT and are discussed in the following sections.
4.5.2.1
IDCODE Data Register

The format for the 32-bit IDCODE Data Register defined by the IEEE Standard 1149.1 is shown in Figure 4-3. The standard requires that every JTAG-compliant microcontroller implement either the IDCODE instruction or the BYPASS instruction as the default instruction. The LSB of the IDCODE Data Register is defined to be a 1 to distinguish it from the BYPASS instruction, which has an LSB of 0. This definition allows auto-configuration test tools to determine which instruction is the default instruction. The major uses of the JTAG port are for manufacturer testing of component assembly and program development and debug. To facilitate the use of auto-configuration debug tools, the IDCODE instruction outputs a value of 0x4BA0.0477. This value allows the debuggers to automatically configure themselves to work correctly with the Cortex-M4F during debug. Figure 4-3. IDCODE Register Format
31 TDI
28 27
12 11
1 0
Version
Part Number
Manufacturer ID
TDO
4.5.2.2
BYPASS Data Register

The format for the 1-bit BYPASS Data Register defined by the IEEE Standard 1149.1 is shown in Figure 4-4. The standard requires that every JTAG-compliant microcontroller implement either the BYPASS instruction or the IDCODE instruction as the default instruction. The LSB of the BYPASS Data Register is defined to be a 0 to distinguish it from the IDCODE instruction, which has an LSB of 1. This definition allows auto-configuration test tools to determine which instruction is the default instruction. Figure 4-4. BYPASS Register Format
0
TDI
TDO
4.5.2.3
Boundary Scan Data Register

The format of the Boundary Scan Data Register is shown in Figure 4-5. Each GPIO pin, starting with a GPIO pin next to the JTAG port pins, is included in the Boundary Scan Data Register. Each GPIO pin has three associated digital signals that are included in the chain. These signals are input, output, and output enable, and are arranged in that order as shown in the figure. When the Boundary Scan Data Register is accessed with the SAMPLE/PRELOAD instruction, the input, output, and output enable from each digital pad are sampled and then shifted out of the chain
April 25, 2012
to be verified. The sampling of these values occurs on the rising edge of TCK in the Capture DR state of the TAP controller. While the sampled data is being shifted out of the Boundary Scan chain in the Shift DR state of the TAP controller, new data can be preloaded into the chain for use with the EXTEST and INTEST instructions. The EXTEST instruction forces data out of the controller, and the INTEST instruction forces data into the controller. Figure 4-5. Boundary Scan Register Format
TDI I N O U T 1st GPIO O E
...
I N
O U T mth GPIO
O E
I N
O U T (m+1)th GPIO
O E
...
I N
O U T GPIO nth
O E
TDO
4.5.2.4
APACC Data Register

The format for the 35-bit APACC Data Register defined by ARM is described in the ARM Debug Interface V5 Architecture Specification.
4.5.2.5
DPACC Data Register

The format for the 35-bit DPACC Data Register defined by ARM is described in the ARM Debug Interface V5 Architecture Specification.
4.5.2.6
ABORT Data Register

The format for the 35-bit ABORT Data Register defined by ARM is described in the ARM Debug Interface V5 Architecture Specification.
207
System Control
System Control
System control configures the overall operation of the device and provides information about the device. Configurable features include reset control, NMI operation, power control, clock control, and low-power modes.
5.1
Signal Description
The following table lists the external signals of the System Control module and describes the function of each. The NMI signal is the alternate function for two GPIO signals and functions as a GPIO after reset. PD7 and PF0 are under commit protection and require a special process to be configured as any alternate function or to subsequently return to the GPIO function, see Commit Control on page 639. The column in the table below titled "Pin Mux/Pin Assignment" lists the GPIO pin placement for the NMI signal. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the NMI function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the NMI signal to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632. The remaining signals (with the word "fixed" in the Pin Mux/Pin Assignment column) have a fixed pin assignment and function.
Table 5-1. System Control & Clocks Signals (64LQFP)

Pin Name NMI OSC0 OSC1 RST Pin Number Pin Mux / Pin Assignment 10 28 40 41 38 PD7 (8) PF0 (8) fixed fixed fixed Pin Type I I O I Buffer Type TTL Analog Analog TTL
a
Description Non-maskable interrupt. Main oscillator crystal input or an external clock reference input. Main oscillator crystal output. Leave unconnected when using a single-ended clock source. System reset input.
5.2
The System Control module provides the following capabilities: Device identification, see Device Identification on page 208 Local control, such as reset (see Reset Control on page 209), power (see Power Control on page 214) and clock control (see Clock Control on page 215) System control (Run, Sleep, and Deep-Sleep modes), see System Control on page 222
5.2.1
Device Identification
Several read-only registers provide software with information on the microcontroller, such as version, part number, memory sizes, and peripherals present on the device. The Device Identification 0 (DID0) (page 232) and Device Identification 1 (DID1) (page 234) registers provide details about the device's version, package, temperature range, and so on. The Peripheral Present registers starting at System Control offset 0x300, such as the Watchdog Timer Peripheral Present (PPWD) register, provide information on how many of each type of module are included on the device. Finally,
April 25, 2012
information about the capabilities of the on-chip peripherals are provided at offset 0xFC0 in each peripheral's register space in the Peripheral Properties registers, such as the GPTM Peripheral Properties (GPTMPP) register. Previous generations of Stellaris devices used the Device Capabilities (DC0-DC9) registers for information about the peripherals and their capabilities. These registers are present on this device for backward software capability, but provide no information about peripherals that were not available on older devices.
5.2.2
Reset Control
This section discusses aspects of hardware functions during reset as well as system software requirements following the reset sequence.
5.2.2.1
Reset Sources
The LM4F120H5QR microcontroller has six sources of reset: 1. Power-on reset (POR) (see page 210). 2. External reset input pin (RST) assertion (see page 210). 3. Internal brown-out (BOR) detector (see page 212). 4. Software-initiated reset (with the software reset registers) (see page 212). 5. A watchdog timer reset condition violation (see page 213). 6. MOSC failure (see page 214). Table 5-2 provides a summary of results of the various reset operations. Table 5-2. Reset Sources
Reset Source Power-On Reset RST Brown-Out Reset Software System Request Reset using the SYSRESREQ bit in the APINT register. Software System Request Reset using the VECTRESET bit in the APINT register. Software Peripheral Reset Watchdog Reset MOSC Failure Reset Core Reset? Yes Yes Yes Yes JTAG Reset? Yes Pin Config Only Pin Config Only Pin Config Only On-Chip Peripherals Reset? Yes Yes Yes Yes
Yes
Pin Config Only
No
No Yes Yes
Pin Config Only Pin Config Only Pin Config Only
Yes
Yes Yes
a. Programmable on a module-by-module basis using the Software Reset Control Registers.
After a reset, the Reset Cause (RESC) register is set with the reset cause. The bits in this register are sticky and maintain their state across multiple reset sequences, except when an internal POR is the cause, in which case, all the bits in the RESC register are cleared except for the POR indicator. A bit in the RESC register can be cleared by writing a 0. At any reset that resets the core, the user has the opportunity to direct the core to execute the ROM Boot Loader or the application in Flash memory by using any GPIO signal as configured in the Boot Configuration (BOOTCFG) register.
209
System Control
At reset, the following sequence is performed: 1. The BOOTCFG register is read. If the EN bit is clear, the ROM Boot Loader is executed. 2. In the ROM Boot Loader, the status of the specified GPIO pin is compared with the specified polarity. If the status matches the specified polarity, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 3. f then EN bit is set or the status doesn't match the specified polarity, the data at address 0x0000.0004 is read, and if the data at this address is 0xFFFF.FFFF, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 4. If there is data at address 0x0000.0004 that is not 0xFFFF.FFFF, the stack pointer (SP) is loaded from Flash memory at address 0x0000.0000 and the program counter (PC) is loaded from address 0x0000.0004. The user application begins executing. For example, if the BOOTCFG register is written and committed with the value of 0x0000.3C01, then PB7 is examined at reset to determine if the ROM Boot Loader should be executed. If PB7 is Low, the core unconditionally begins executing the ROM boot loader. If PB7 is High, then the application in Flash memory is executed if the reset vector at location 0x0000.0004 is not 0xFFFF.FFFF. Otherwise, the ROM boot loader is executed.
5.2.2.2
Power-On Reset (POR)

Note: The JTAG controller can only be reset by the power-on reset. The internal Power-On Reset (POR) circuit monitors the power supply voltage (VDD) and generates a reset signal to all of the internal logic including JTAG when the power supply ramp reaches a threshold value (VTH). The microcontroller must be operating within the specified operating parameters when the on-chip power-on reset pulse is complete (see Power and Brown-Out on page 1162). For applications that require the use of an external reset signal to hold the microcontroller in reset longer than the internal POR, the RST input may be used as discussed in External RST Pin on page 210. The Power-On Reset sequence is as follows: 1. The microcontroller waits for internal POR to go inactive. 2. The internal reset is released and the core loads from memory the initial stack pointer, the initial program counter, and the first instruction designated by the program counter, and then begins execution. The internal POR is only active on the initial power-up of the microcontroller and when the microcontroller wakes from hibernation. The Power-On Reset timing is shown in Figure 23-6 on page 1163.
5.2.2.3
External RST Pin

Note: It is recommended that the trace for the RST signal must be kept as short as possible. Be sure to place any components connected to the RST signal as close to the microcontroller as possible.
If the application only uses the internal POR circuit, the RST input must be connected to the power supply (VDD) through an optional pull-up resistor (0 to 100K ) as shown in Figure 5-1 on page 211. The RST input has filtering which requires a minimum pulse width in order for the reset pulse to be recognized, see Table 23-7 on page 1163.
April 25, 2012
Figure 5-1. Basic RST Configuration
VDD Stellaris RPU RST
RPU = 0 to 100 k The external reset pin (RST) resets the microcontroller including the core and all the on-chip peripherals. The external reset sequence is as follows: 1. The external reset pin (RST) is asserted for the duration specified by TMIN and then de-asserted (see Reset on page 1163). 2. The internal reset is released and the core loads from memory the initial stack pointer, the initial program counter, and the first instruction designated by the program counter, and then begins execution. To improve noise immunity and/or to delay reset at power up, the RST input may be connected to an RC network as shown in Figure 5-2 on page 211. Figure 5-2. External Circuitry to Extend Power-On Reset
VDD Stellaris RPU RST C1
RPU = 1 k to 100 k C1 = 1 nF to 10 F If the application requires the use of an external reset switch, Figure 5-3 on page 212 shows the proper circuitry to use.
211
System Control
Figure 5-3. Reset Circuit Controlled by Switch
VDD Stellaris RPU RST C1 RS
Typical RPU = 10 k Typical RS = 470 C1 = 10 nF The RPU and C1 components define the power-on delay. The external reset timing is shown in Figure 23-8 on page 1164.
5.2.2.4
Brown-Out Reset (BOR)

The microcontroller provides a brown-out detection circuit that triggers if the power supply (VDD) drops below a brown-out threshold voltage (VBTH). If a brown-out condition is detected, the system may generate an interrupt or a system reset. The default condition is to generate an interrupt, so BOR must be enabled. Brown-out resets are controlled with the Power-On and Brown-Out Reset Control (PBORCTL) register. The BORIOR bit in the PBORCTL register must be set for a brown-out condition to trigger a reset; if BORIOR is clear, an interrupt is generated. The brown-out reset sequence is as follows: 1. When VDD drops below VBTH, an internal BOR condition is set. 2. If the BOR condition exists, an internal reset is asserted. 3. The internal reset is released and the microcontroller fetches and loads the initial stack pointer, the initial program counter, the first instruction designated by the program counter, and begins execution. The result of a brown-out reset is equivalent to that of an assertion of the external RST input, and the reset is held active until the proper VDD level is restored. The RESC register can be examined in the reset interrupt handler to determine if a Brown-Out condition was the cause of the reset, thus allowing software to determine what actions are required to recover. The internal Brown-Out Reset timing is shown in Figure 23-7 on page 1163.
5.2.2.5
Software Reset
Software can reset a specific peripheral or generate a reset to the entire microcontroller. Peripherals can be individually reset by software via peripheral-specific reset registers available beginning at System Control offset 0x500 (for example the Watchdog Timer Software Reset (SRWD) register). If the bit position corresponding to a peripheral is set and subsequently cleared, the peripheral is reset.
April 25, 2012
The entire microcontroller, including the core, can be reset by software by setting the SYSRESREQ bit in the Application Interrupt and Reset Control (APINT) register. The software-initiated system reset sequence is as follows: 1. A software microcontroller reset is initiated by setting the SYSRESREQ bit. 2. An internal reset is asserted. 3. The internal reset is deasserted and the microcontroller loads from memory the initial stack pointer, the initial program counter, and the first instruction designated by the program counter, and then begins execution. The core only can be reset by software by setting the VECTRESET bit in the APINT register. The software-initiated core reset sequence is as follows: 1. A core reset is initiated by setting the VECTRESET bit. 2. An internal reset is asserted. 3. The internal reset is deasserted and the microcontroller loads from memory the initial stack pointer, the initial program counter, and the first instruction designated by the program counter, and then begins execution. The software-initiated system reset timing is shown in Figure 23-9 on page 1164.
5.2.2.6
Watchdog Timer Reset

The Watchdog Timer module's function is to prevent system hangs. The LM4F120H5QR microcontroller has two Watchdog Timer modules in case one watchdog clock source fails. One watchdog is run off the system clock and the other is run off the Precision Internal Oscillator (PIOSC). Each module operates in the same manner except that because the PIOSC watchdog timer module is in a different clock domain, register accesses must have a time delay between them. The watchdog timer can be configured to generate an interrupt or a non-maskable interrupt to the microcontroller on its first time-out and to generate a reset on its second time-out. After the watchdog's first time-out event, the 32-bit watchdog counter is reloaded with the value of the Watchdog Timer Load (WDTLOAD) register and resumes counting down from that value. If the timer counts down to zero again before the first time-out interrupt is cleared, and the reset signal has been enabled, the watchdog timer asserts its reset signal to the microcontroller. The watchdog timer reset sequence is as follows: 1. The watchdog timer times out for the second time without being serviced. 2. An internal reset is asserted. 3. The internal reset is released and the microcontroller loads from memory the initial stack pointer, the initial program counter, and the first instruction designated by the program counter, and then begins execution. For more information on the Watchdog Timer module, see Watchdog Timers on page 756. The watchdog reset timing is shown in Figure 23-10 on page 1164.
5.2.3
Non-Maskable Interrupt
The microcontroller has four sources of non-maskable interrupt (NMI):
213
System Control
The assertion of the NMI signal A main oscillator verification error The NMISET bit in the Interrupt Control and State (INTCTRL) register in the Cortex-M4F (see page 156). The Watchdog module time-out interrupt when the INTTYPE bit in the Watchdog Control (WDTCTL) register is set (see page 762). Software must check the cause of the interrupt in order to distinguish among the sources.
5.2.3.1
NMI Pin
The NMI signal is an alternate function for either GPIO port pin PD7 or PF0. The alternate function must be enabled in the GPIO for the signal to be used as an interrupt, as described in General-Purpose Input/Outputs (GPIOs) on page 632. Note that enabling the NMI alternate function requires the use of the GPIO lock and commit function just like the GPIO port pins associated with JTAG/SWD functionality, see page 667. The active sense of the NMI signal is High; asserting the enabled NMI signal above VIH initiates the NMI interrupt sequence.
5.2.3.2
Main Oscillator Verification Failure

The LM4F120H5QR microcontroller provides a main oscillator verification circuit that generates an error condition if the oscillator is running too fast or too slow. If the main oscillator verification circuit is enabled and a failure occurs, either a power-on reset is generated and control is transferred to the NMI handler, or an interrupt is generated. The MOSCIM bit in the MOSCCTL register determines which action occurs. In either case, the system clock source is automatically switched to the PIOSC. If a MOSC failure reset occurs, the NMI handler is used to address the main oscillator verification failure because the necessary code can be removed from the general reset handler, speeding up reset processing. The detection circuit is enabled by setting the CVAL bit in the Main Oscillator Control (MOSCCTL) register. The main oscillator verification error is indicated in the main oscillator fail status (MOSCFAIL) bit in the Reset Cause (RESC) register. The main oscillator verification circuit action is described in more detail in Main Oscillator Verification Circuit on page 222.
5.2.4
Power Control
The Stellaris microcontroller provides an integrated LDO regulator that is used to provide power to the majority of the microcontroller's internal logic. Figure 5-4 shows the power architecture. An external LDO may not be used. Note: VDDA must be supplied with a voltage that meets the specification in Table 23-2 on page 1159, or the microcontroller does not function properly. VDDA is the supply for all of the analog circuitry on the device, including the clock circuitry.
April 25, 2012
Figure 5-4. Power Architecture
VDDC
Internal Logic and PLL
GND
VDDC
GND
LDO
LDO Voltage Regulator
+3.3V VDD GND
I/O Buffers
VDD GND
VDDA
GNDA
Analog Circuits
VDDA GNDA
5.2.5
Clock Control
System control determines the control of clocks in this part.
5.2.5.1
Fundamental Clock Sources

There are multiple clock sources for use in the microcontroller: Precision Internal Oscillator (PIOSC). The precision internal oscillator is an on-chip clock source that is the clock source the microcontroller uses during and following POR. It does not require the use of any external components and provides a clock that is 16 MHz 1% at room temperature and 3% across temperature. The PIOSC allows for a reduced system cost in applications that require an accurate clock source. If the main oscillator is required, software must enable the main oscillator following reset and allow the main oscillator to stabilize before changing the clock reference. If the Hibernation Module clock source is a 32.768-kHz oscillator, the precision internal oscillator can be trimmed by software based on a reference clock for increased accuracy. Regardless of whether or not the PIOSC is the source for the system clock, the PIOSC can be configured to be the source for the ADC clock as well as the baud clock for the UART and SSI, see System Control on page 222. Main Oscillator (MOSC). The main oscillator provides a frequency-accurate clock source by one of two means: an external single-ended clock source is connected to the OSC0 input pin, or
215
System Control
an external crystal is connected across the OSC0 input and OSC1 output pins. If the PLL is being used, the crystal value must be one of the supported frequencies between 5 MHz to 25 MHz (inclusive). If the PLL is not being used, the crystal may be any one of the supported frequencies between 4 MHz to 25 MHz. The single-ended clock source range is from DC through the specified speed of the microcontroller. The supported crystals are listed in the XTAL bit field in the RCC register (see page 245). Note that the MOSC provides the clock source for the USB PLL and must be connected to a crystal or an oscillator. Internal 30-kHz Oscillator. The internal 30-kHz oscillator provides an operational frequency of 30 kHz 50%. It is intended for use during Deep-Sleep power-saving modes. This power-savings mode benefits from reduced internal switching and also allows the MOSC to be powered down. Hibernation Module Clock Source. The Hibernation module is clocked by a 32.768-kHz oscillator connected to the XOSC0 pin. The 32.768-kHz oscillator can be used for the system clock, thus eliminating the need for an additional crystal or oscillator. The Hibernation module clock source is intended to provide the system with a real-time clock source and may also provide an accurate source of Deep-Sleep or Hibernate mode power savings. The internal system clock (SysClk), is derived from any of the above sources plus two others: the output of the main internal PLL and the precision internal oscillator divided by four (4 MHz 1%). The frequency of the PLL clock reference must be in the range of 5 MHz to 25 MHz (inclusive). Table 5-3 on page 216 shows how the various clock sources can be used in a system. Table 5-3. Clock Source Options
Clock Source Precision Internal Oscillator Drive PLL? Yes Used as SysClk? BYPASS = 0, OSCSRC Yes = 0x1 Yes BYPASS = 1, OSCSRC = 0x1 BYPASS = 1, OSCSRC = 0x2 BYPASS = 1, OSCSRC = 0x0 BYPASS = 1, OSCSRC = 0x3 BYPASS = 1, OSCSRC2 = 0x7
Precision Internal Oscillator divide by No 4 (4 MHz 1%) Main Oscillator Internal 30-kHz Oscillator Hibernation Module 32.768-kHz Oscillator Yes No No
BYPASS = 0, OSCSRC Yes = 0x0 Yes Yes
5.2.5.2
Clock Configuration
The Run-Mode Clock Configuration (RCC) and Run-Mode Clock Configuration 2 (RCC2) registers provide control for the system clock. The RCC2 register is provided to extend fields that offer additional encodings over the RCC register. When used, the RCC2 register field values are used by the logic over the corresponding field in the RCC register. In particular, RCC2 provides for a larger assortment of clock configuration options. These registers control the following clock functionality: Source of clocks in sleep and deep-sleep modes System clock derived from PLL or other clock source Enabling/disabling of oscillators and PLL Clock divisors Crystal input selection
April 25, 2012
Important: Write the RCC register prior to writing the RCC2 register. If a subsequent write to the RCC register is required, include another register access after writing the RCC register and before writing the RCC2 register. The configuration of the system clock must not be changed while an EEPROM operation is in process. Software must wait until the WORKING bit in the EEPROM Done Status (EEDONE) register is clear before making any changes to the system clock. Figure 5-5 shows the logic for the main clock tree. The peripheral blocks are driven by the system clock signal and can be individually enabled/disabled. The ADC clock signal can be selected from the PIOSC, the system clock if the PLL is disabled, or the PLL output divided down to 16 MHz if the PLL is enabled. Note: If the ADC module is not using the PIOSC as the clock source, the system clock must be at least 16 MHz. When the USB module is in operation, MOSC must be the clock source, either with or without using the PLL, and the system clock must be at least 30 MHz.
217
System Control
Figure 5-5. Main Clock Tree

XTALa USBPWRDN c USB PLL (480 MHz)
USB Clock
XTALa PWRDN b
CS f
MOSCDIS a PLL (400 MHz) 2 IOSCDIS a System Clock Precision Internal OSC (16 MHz) 4 Internal OSC (30 kHz) 25 Hibernation OSC (32.768 kHz) OSCSRC b,d CS f BYPASS b,d PWRDN SSI Baud Clock SYSDIV
e
Main OSC
DIV400
BYPASS b,d USESYSDIV a,d
UART Baud Clock
CS f
ADC Clock
Note:
a. b. c. d. e. f.
Control provided by RCC register bit/field. Control provided by RCC register bit/field or RCC2 register bit/field, if overridden with RCC2 register bit USERCC2. Control provided by RCC2 register bit/field. Also may be controlled by DSLPCLKCFG when in deep sleep mode. Control provided by RCC register SYSDIV field, RCC2 register SYSDIV2 field if overridden with USERCC2 bit, or [SYSDIV2,SYSDIV2LSB] if both USERCC2 and DIV400 bits are set. Control provided by UARTCC, SSICC, and ADCCC register field.
Communication Clock Sources In addition to the main clock tree described above, the UART, and SSI modules all have a Clock Control register in the peripheral's register map at offset 0xFC8 that can be used to select the clock source for the module's baud clock. Users can choose between the system clock, which is the default source for the baud clock, and the PIOSC. Note that there may be special considerations when using the PIOSC as the baud clock. For more information, see the Clock Control register description in the chapter describing the operation of the module. Using the SYSDIV and SYSDIV2 Fields In the RCC register, the SYSDIV field specifies which divisor is used to generate the system clock from either the PLL output or the oscillator source (depending on how the BYPASS bit in this register is configured). When using the PLL, the VCO frequency of 400 MHz is predivided by 2 before the divisor is applied. Table 5-4 shows how the SYSDIV encoding affects the system clock frequency,
April 25, 2012
depending on whether the PLL is used (BYPASS=0) or another clock source is used (BYPASS=1). The divisor is equivalent to the SYSDIV encoding plus 1. For a list of possible clock sources, see Table 5-3 on page 216. Table 5-4. Possible System Clock Frequencies Using the SYSDIV Field
SYSDIV 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF Divisor /1 /2 /3 /4 /5 /6 /7 /8 /9 /10 /11 /12 /13 /14 /15 /16 Frequency (BYPASS=0) Frequency (BYPASS=1) reserved reserved 66.67 MHz 50 MHz 40 MHz 33.33 MHz 28.57 MHz 25 MHz 22.22 MHz 20 MHz 18.18 MHz 16.67 MHz 15.38 MHz 14.29 MHz 13.33 MHz 12.5 MHz (default) Clock source frequency/2 Clock source frequency/2 Clock source frequency/3 Clock source frequency/4 Clock source frequency/5 Clock source frequency/6 Clock source frequency/7 Clock source frequency/8 Clock source frequency/9 Clock source frequency/10 Clock source frequency/11 Clock source frequency/12 Clock source frequency/13 Clock source frequency/14 Clock source frequency/15 Clock source frequency/16 StellarisWare Parameter SYSCTL_SYSDIV_1 SYSCTL_SYSDIV_2 SYSCTL_SYSDIV_3 SYSCTL_SYSDIV_4 SYSCTL_SYSDIV_5 SYSCTL_SYSDIV_6 SYSCTL_SYSDIV_7 SYSCTL_SYSDIV_8 SYSCTL_SYSDIV_9 SYSCTL_SYSDIV_10 SYSCTL_SYSDIV_11 SYSCTL_SYSDIV_12 SYSCTL_SYSDIV_13 SYSCTL_SYSDIV_14 SYSCTL_SYSDIV_15 SYSCTL_SYSDIV_16
b
a. This parameter is used in functions such as SysCtlClockSet() in the Stellaris Peripheral Driver Library. b. SYSCTL_SYSDIV_1 does not set the USESYSDIV bit. As a result, using this parameter without enabling the PLL results in the system clock having the same frequency as the clock source.
The SYSDIV2 field in the RCC2 register is 2 bits wider than the SYSDIV field in the RCC register so that additional larger divisors up to /64 are possible, allowing a lower system clock frequency for improved Deep Sleep power consumption. When using the PLL, the VCO frequency of 400 MHz is predivided by 2 before the divisor is applied. The divisor is equivalent to the SYSDIV2 encoding plus 1. Table 5-5 shows how the SYSDIV2 encoding affects the system clock frequency, depending on whether the PLL is used (BYPASS2=0) or another clock source is used (BYPASS2=1). For a list of possible clock sources, see Table 5-3 on page 216. Table 5-5. Examples of Possible System Clock Frequencies Using the SYSDIV2 Field
SYSDIV2 0x00 0x01 0x02 0x03 0x04 ... 0x09 ... 0x3F Divisor /1 /2 /3 /4 /5 ... /10 ... /64 Frequency (BYPASS2=0) reserved reserved 66.67 MHz 50 MHz 40 MHz ... 20 MHz ... 3.125 MHz Frequency (BYPASS2=1) Clock source frequency/2 Clock source frequency/2 Clock source frequency/3 Clock source frequency/4 Clock source frequency/5 ... Clock source frequency/10 ... Clock source frequency/64 StellarisWare Parameter SYSCTL_SYSDIV_1 SYSCTL_SYSDIV_2 SYSCTL_SYSDIV_3 SYSCTL_SYSDIV_4 SYSCTL_SYSDIV_5 ... SYSCTL_SYSDIV_10 ... SYSCTL_SYSDIV_64
b a
a. This parameter is used in functions such as SysCtlClockSet() in the Stellaris Peripheral Driver Library.
219
System Control
b. SYSCTL_SYSDIV_1 does not set the USESYSDIV bit. As a result, using this parameter without enabling the PLL results in the system clock having the same frequency as the clock source.
To allow for additional frequency choices when using the PLL, the DIV400 bit is provided along with the SYSDIV2LSB bit. When the DIV400 bit is set, bit 22 becomes the LSB for SYSDIV2. In this situation, the divisor is equivalent to the (SYSDIV2 encoding with SYSDIV2LSB appended) plus one. Table 5-6 shows the frequency choices when DIV400 is set. When the DIV400 bit is clear, SYSDIV2LSB is ignored, and the system clock frequency is determined as shown in Table 5-5 on page 219. Table 5-6. Examples of Possible System Clock Frequencies with DIV400=1
SYSDIV2 0x00 0x01 SYSDIV2LSB reserved 0 1 0 1 0 1 0 1 ... 0 1 Divisor /2 /3 /4 /5 /6 /7 /8 /9 /10 ... /127 /128 Frequency (BYPASS2=0) reserved reserved reserved 80 MHz 66.67 MHz reserved 50 MHz 44.44 MHz 40 MHz ... 3.15 MHz 3.125 MHz
a
StellarisWare Parameter SYSCTL_SYSDIV_2_5 SYSCTL_SYSDIV_3 SYSCTL_SYSDIV_4 SYSCTL_SYSDIV_4_5 SYSCTL_SYSDIV_5 ... SYSCTL_SYSDIV_63_5 SYSCTL_SYSDIV_64
0x02
0x03
0x04 ... 0x3F
a. Note that DIV400 and SYSDIV2LSB are only valid when BYPASS2=0. b. This parameter is used in functions such as SysCtlClockSet() in the Stellaris Peripheral Driver Library.
5.2.5.3
Precision Internal Oscillator Operation (PIOSC)

The microcontroller powers up with the PIOSC running. If another clock source is desired, the PIOSC must remain enabled as it is used for internal functions. The PIOSC can only be disabled during Deep-Sleep mode. It can be powered down by setting the IOSCDIS bit in the RCC register. The PIOSC generates a 16-MHz clock with a 1% accuracy at room temperatures. Across the extended temperature range, the accuracy is 3%. At the factory, the PIOSC is set to 16 MHz at room temperature, however, the frequency can be trimmed for other voltage or temperature conditions using software in one of three ways: Default calibration: clear the UTEN bit and set the UPDATE bit in the Precision Internal Oscillator Calibration (PIOSCCAL) register. User-defined calibration: The user can program the UT value to adjust the PIOSC frequency. As the UT value increases, the generated period increases. To commit a new UT value, first set the UTEN bit, then program the UT field, and then set the UPDATE bit. The adjustment finishes within a few clock periods and is glitch free. Automatic calibration using the Hibernation module with a functioning 32.768-kHz clock source: Set the CAL bit in the PIOSCCAL register; the results of the calibration are shown in the RESULT field in the Precision Internal Oscillator Statistic (PIOSCSTAT) register. After calibration is complete, the PIOSC is trimmed using the trimmed value returned in the CT field.
April 25, 2012
5.2.5.4
Crystal Configuration for the Main Oscillator (MOSC)

The main oscillator supports the use of a select number of crystals from 4 to 25 MHz. The XTAL bit in the RCC register (see page 245) describes the available crystal choices and default programming values. Software configures the RCC register XTAL field with the crystal number. If the PLL is used in the design, the XTAL field value is internally translated to the PLL settings.
5.2.5.5
Main PLL Frequency Configuration

The main PLL is disabled by default during power-on reset and is enabled later by software if required. Software specifies the output divisor to set the system clock frequency and enables the main PLL to drive the output. The PLL operates at 400 MHz, but is divided by two prior to the application of the output divisor, unless the DIV400 bit in the RCC2 register is set. To configure the PIOSC to be the clock source for the main PLL, program the OSCRC2 field in the Run-Mode Clock Configuration 2 (RCC2) register to be 0x1. If the main oscillator provides the clock reference to the main PLL, the translation provided by hardware and used to program the PLL is available for software in the PLL Frequency n (PLLFREQn) registers (see page 261). The internal translation provides a translation within 1% of the targeted PLL VCO frequency. Table 23-10 on page 1165 shows the actual PLL frequency and error for a given crystal choice. The Crystal Value field (XTAL) in the Run-Mode Clock Configuration (RCC) register (see page 245) describes the available crystal choices and default programming of the PLLFREQn registers. Any time the XTAL field changes, the new settings are translated and the internal PLL settings are updated.
5.2.5.6
USB PLL Frequency Configuration

The USB PLL is disabled by default during power-on reset and is enabled later by software. The USB PLL must be enabled and running for proper USB function. The main oscillator is the only clock reference for the USB PLL. The USB PLL is enabled by clearing the USBPWRDN bit of the RCC2 register. The XTAL bit field (Crystal Value) of the RCC register describes the available crystal choices. The main oscillator must be connected to one of the following crystal values in order to correctly generate the USB clock: 5, 6, 8, 10, 12, 16, 18, 20, 24, or 25 MHz. Only these crystals provide the necessary USB PLL VCO frequency to conform with the USB timing specifications.
5.2.5.7
PLL Modes
Both PLLs have two modes of operation: Normal and Power-Down Normal: The PLL multiplies the input clock reference and drives the output. Power-Down: Most of the PLL internal circuitry is disabled and the PLL does not drive the output. The modes are programmed using the RCC/RCC2 register fields (see page 245 and page 251).
5.2.5.8
PLL Operation
If a PLL configuration is changed, the PLL output frequency is unstable until it reconverges (relocks) to the new setting. The time between the configuration change and relock is TREADY (see Table 23-9 on page 1165). During the relock time, the affected PLL is not usable as a clock reference. Software can poll the LOCK bit in the PLL Status (PLLSTAT) register to determine when the PLL has locked.
221
System Control
Either PLL is changed by one of the following: Change to the XTAL value in the RCC registerwrites of the same value do not cause a relock. Change in the PLL from Power-Down to Normal mode. A counter clocked by the system clock is used to measure the TREADY requirement. The down counter is set to 0x200 if the PLL is powering up. If the M or N values in the PLLFREQn registers are changed, the counter is set to 0xC0. Hardware is provided to keep the PLL from being used as a system clock until the TREADY condition is met after one of the two changes above. It is the user's responsibility to have a stable clock source (like the main oscillator) before the RCC/RCC2 register is switched to use the PLL. If the main PLL is enabled and the system clock is switched to use the PLL in one step, the system control hardware continues to clock the microcontroller from the oscillator selected by the RCC/RCC2 register until the main PLL is stable (TREADY time met), after which it changes to the PLL. Software can use many methods to ensure that the system is clocked from the main PLL, including periodically polling the PLLLRIS bit in the Raw Interrupt Status (RIS) register, and enabling the PLL Lock interrupt. The USB PLL is not protected during the lock time (TREADY), and software should ensure that the USB PLL has locked before using the interface. Software can use many methods to ensure the TREADY period has passed, including periodically polling the USBPLLLRIS bit in the Raw Interrupt Status (RIS) register, and enabling the USB PLL Lock interrupt.
5.2.5.9
Main Oscillator Verification Circuit

The clock control includes circuitry to ensure that the main oscillator is running at the appropriate frequency. The circuit monitors the main oscillator frequency and signals if the frequency is outside of the allowable band of attached crystals. The detection circuit is enabled using the CVAL bit in the Main Oscillator Control (MOSCCTL) register. If this circuit is enabled and detects an error, and if the MOSCIM bit in the MOSCCTL register is clear, then the following sequence is performed by the hardware: 1. The MOSCFAIL bit in the Reset Cause (RESC) register is set. 2. The system clock is switched from the main oscillator to the PIOSC. 3. An internal power-on reset is initiated. 4. Reset is de-asserted and the processor is directed to the NMI handler during the reset sequence. if the MOSCIM bit in the MOSCCTL register is set, then the following sequence is performed by the hardware: 1. The system clock is switched from the main oscillator to the PIOSC. 2. The MOFRIS bit in the RIS register is set to indicate a MOSC failure.
5.2.6
System Control
For power-savings purposes, the peripheral-specific RCGCx, SCGCx, and DCGCx registers (for example, RCGCWD) control the clock gating logic for that peripheral or block in the system while the microcontroller is in Run, Sleep, and Deep-Sleep mode, respectively. These registers are located in the System Control register map starting at offsets 0x600, 0x700, and 0x800, respectively. There
April 25, 2012
must be a delay of 3 system clocks after a peripheral module clock is enabled in the RCGC register before any module registers are accessed. Important: To support legacy software, the RCGCn, SCGCn, and DCGCn registers are available at offsets 0x100 - 0x128. A write to any of these legacy registers also writes the corresponding bit in the peripheral-specific RCGCx, SCGCx, and DCGCx registers. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. It is recommended that new software use the new registers and not rely on legacy operation. If software uses a peripheral-specific register to write a legacy peripheral (such as TIMER0), the write causes proper operation, but the value of that bit is not reflected in the legacy register. Any bits that are changed by writing to a legacy register can be read back correctly with a read of the legacy register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information. There are four levels of operation for the microcontroller defined as: Run mode Sleep mode Deep-Sleep mode Hibernate mode The following sections describe the different modes in detail. Caution If the Cortex-M4F Debug Access Port (DAP) has been enabled, and the device wakes from a low power sleep or deep-sleep mode, the core may start executing code before all clocks to peripherals have been restored to their Run mode configuration. The DAP is usually enabled by software tools accessing the JTAG or SWD interface when debugging or flash programming. If this condition occurs, a Hard Fault is triggered when software accesses a peripheral with an invalid clock. A software delay loop can be used at the beginning of the interrupt routine that is used to wake up a system from a WFI (Wait For Interrupt) instruction. This stalls the execution of any code that accesses a peripheral register that might cause a fault. This loop can be removed for production software as the DAP is most likely not enabled during normal execution. Because the DAP is disabled by default (power on reset), the user can also power cycle the device. The DAP is not enabled unless it is enabled through the JTAG or SWD interface.
5.2.6.1
Run Mode
In Run mode, the microcontroller actively executes code. Run mode provides normal operation of the processor and all of the peripherals that are currently enabled by the the peripheral-specific RCGC registers. The system clock can be any of the available clock sources including the PLL.
5.2.6.2
Sleep Mode
In Sleep mode, the clock frequency of the active peripherals is unchanged, but the processor and the memory subsystem are not clocked and therefore no longer execute code. Sleep mode is entered by the Cortex-M4F core executing a WFI (Wait for Interrupt) instruction. Any properly configured
223
System Control
interrupt event in the system brings the processor back into Run mode. See Power Management on page 110 for more details. Peripherals are clocked that are enabled in the peripheral-specific SCGC registers when auto-clock gating is enabled (see the RCC register) or the the peripheral-specific RCGC registers when the auto-clock gating is disabled. The system clock has the same source and frequency as that during Run mode. Important: Before executing the WFI instruction, software must confirm that the EEPROM is not busy by checking to see that the WORKING bit in the EEPROM Done Status (EEDONE) register is clear.
5.2.6.3
Deep-Sleep Mode
In Deep-Sleep mode, the clock frequency of the active peripherals may change (depending on the Run mode clock configuration) in addition to the processor clock being stopped. An interrupt returns the microcontroller to Run mode from one of the sleep modes; the sleep modes are entered on request from the code. Deep-Sleep mode is entered by first setting the SLEEPDEEP bit in the System Control (SYSCTRL) register (see page 162) and then executing a WFI instruction. Any properly configured interrupt event in the system brings the processor back into Run mode. See Power Management on page 110 for more details. The Cortex-M4F processor core and the memory subsystem are not clocked in Deep-Sleep mode. Peripherals are clocked that are enabled in the the peripheral-specific DCGC registers when auto-clock gating is enabled (see the RCC register) or the peripheral-specific RCGC registers when auto-clock gating is disabled. The system clock source is specified in the DSLPCLKCFG register. When the DSLPCLKCFG register is used, the internal oscillator source is powered up, if necessary, and other clocks are powered down. If the PLL is running at the time of the WFI instruction, hardware powers the PLL down and overrides the SYSDIV field of the active RCC/RCC2 register, to be determined by the DSDIVORIDE setting in the DSLPCLKCFG register, up to /16 or /64 respectively. When the Deep-Sleep exit event occurs, hardware brings the system clock back to the source and frequency it had at the onset of Deep-Sleep mode before enabling the clocks that had been stopped during the Deep-Sleep duration. If the PIOSC is used as the PLL reference clock source, it may continue to provide the clock during Deep-Sleep. See page 255. Important: Before executing the WFI instruction, software must confirm that the EEPROM is not busy by checking to see that the WORKING bit in the EEPROM Done Status (EEDONE) register is clear. To provide the lowest possible Deep-Sleep power consumption as well the ability to wake the processor from a peripheral without reconfiguring the peripheral for a change in clock, some of the communications modules have a Clock Control register at offset 0xFC8 in the module register space. The CS field in the Clock Control register allows the user to select the PIOSC as the clock source for the module's baud clock. When the microcontroller enters Deep-Sleep mode, the PIOSC becomes the source for the module clock as well, which allows the transmit and receive FIFOs to continue operation while the part is in Deep-Sleep. Figure 5-6 on page 225 shows how the clocks are selected.
April 25, 2012
Figure 5-6. Module Clock Selection

Clock Control Register
PIOSC
1 Baud Clock 0
Deep Sleep
1 Module Clock System Clock 0
5.2.6.4
Hibernate Mode
In this mode, the power supplies are turned off to the main part of the microcontroller and only the Hibernation module's circuitry is active. An external wake event or RTC event is required to bring the microcontroller back to Run mode. The Cortex-M4F processor and peripherals outside of the Hibernation module see a normal "power on" sequence and the processor starts running code. Software can determine if the microcontroller has been restarted from Hibernate mode by inspecting the Hibernation module registers. For more information on the operation of Hibernate mode, see Hibernation Module on page 480.
5.3

The PLL is configured using direct register writes to the RCC/RCC2 register. If the RCC2 register is being used, the USERCC2 bit must be set and the appropriate RCC2 bit/field is used. The steps required to successfully change the PLL-based system clock are: 1. Bypass the PLL and system clock divider by setting the BYPASS bit and clearing the USESYS bit in the RCC register, thereby configuring the microcontroller to run off a "raw" clock source and allowing for the new PLL configuration to be validated before switching the system clock to the PLL. 2. Select the crystal value (XTAL) and oscillator source (OSCSRC), and clear the PWRDN bit in RCC/RCC2. Setting the XTAL field automatically pulls valid PLL configuration data for the appropriate crystal, and clearing the PWRDN bit powers and enables the PLL and its output. 3. Select the desired system divider (SYSDIV) in RCC/RCC2 and set the USESYS bit in RCC. The SYSDIV field determines the system frequency for the microcontroller. 4. Wait for the PLL to lock by polling the PLLLRIS bit in the Raw Interrupt Status (RIS) register. 5. Enable use of the PLL by clearing the BYPASS bit in RCC/RCC2.
225
System Control
5.4
Register Map
Table 5-7 on page 226 lists the System Control registers, grouped by function. The offset listed is a hexadecimal increment to the register's address, relative to the System Control base address of 0x400F.E000. Note: Spaces in the System Control register space that are not used are reserved for future or internal use. Software should not modify any reserved memory address. Additional Flash and ROM registers defined in the System Control register space are described in the Internal Memory on page 510.
Table 5-7. System Control Register Map

System Control Registers 0x000 0x004 0x030 0x050 0x054 0x058 0x05C 0x060 0x06C 0x070 0x07C 0x144 0x14C 0x150 0x154 0x160 0x164 0x168 0x300 0x304 0x308 0x30C 0x314 DID0 DID1 PBORCTL RIS IMC MISC RESC RCC GPIOHBCTL RCC2 MOSCCTL DSLPCLKCFG SYSPROP PIOSCCAL PIOSCSTAT PLLFREQ0 PLLFREQ1 PLLSTAT PPWD PPTIMER PPGPIO PPDMA PPHIB RO RO R/W RO R/W R/W1C R/W R/W R/W R/W R/W R/W RO R/W RO RO RO RO RO RO RO RO RO 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0780.3D51 0x0000.7E00 0x07C0.6810 0x0000.0000 0x0780.0000 0x0000.1D31 0x0000.0000 0x0000.0040 0x0000.0032 0x0000.0001 0x0000.0000 0x0000.0003 0x0000.003F 0x0000.003F 0x0000.0001 0x0000.0001 Device Identification 0 Device Identification 1 Brown-Out Reset Control Raw Interrupt Status Interrupt Mask Control Masked Interrupt Status and Clear Reset Cause Run-Mode Clock Configuration GPIO High-Performance Bus Control Run-Mode Clock Configuration 2 Main Oscillator Control Deep Sleep Clock Configuration System Properties Precision Internal Oscillator Calibration Precision Internal Oscillator Statistics PLL Frequency 0 PLL Frequency 1 PLL Status Watchdog Timer Peripheral Present 16/32-Bit General-Purpose Timer Peripheral Present General-Purpose Input/Output Peripheral Present Micro Direct Memory Access Peripheral Present Hibernation Peripheral Present 232 234 236 237 239 241 243 245 249 251 254 255 257 258 260 261 262 263 264 265 267 270 271
April 25, 2012
Table 5-7. System Control Register Map (continued)

Offset Name Type Reset Description Universal Asynchronous Receiver/Transmitter Peripheral Present Synchronous Serial Interface Peripheral Present Inter-Integrated Circuit Peripheral Present Universal Serial Bus Peripheral Present Controller Area Network Peripheral Present Analog-to-Digital Converter Peripheral Present Analog Comparator Peripheral Present Pulse Width Modulator Peripheral Present Quadrature Encoder Interface Peripheral Present EEPROM Peripheral Present 32/64-Bit Wide General-Purpose Timer Peripheral Present Watchdog Timer Software Reset 16/32-Bit General-Purpose Timer Software Reset General-Purpose Input/Output Software Reset Micro Direct Memory Access Software Reset Hibernation Software Reset Universal Asynchronous Receiver/Transmitter Software Reset Synchronous Serial Interface Software Reset Inter-Integrated Circuit Software Reset Universal Serial Bus Software Reset Controller Area Network Software Reset Analog-to-Digital Converter Software Reset Analog Comparator Software Reset EEPROM Software Reset 32/64-Bit Wide General-Purpose Timer Software Reset Watchdog Timer Run Mode Clock Gating Control 16/32-Bit General-Purpose Timer Run Mode Clock Gating Control General-Purpose Input/Output Run Mode Clock Gating Control Micro Direct Memory Access Run Mode Clock Gating Control See page 272 274 276 278 279 280 281 282 283 284 285 287 289 291 293 294 295 297 299 301 302 303 305 306 307 309 310
0x318 0x31C 0x320 0x328 0x334 0x338 0x33C 0x340 0x344 0x358 0x35C 0x500 0x504 0x508 0x50C 0x514 0x518 0x51C 0x520 0x528 0x534 0x538 0x53C 0x558 0x55C 0x600 0x604
PPUART PPSSI PPI2C PPUSB PPCAN PPADC PPACMP PPPWM PPQEI PPEEPROM PPWTIMER SRWD SRTIMER SRGPIO SRDMA SRHIB SRUART SRSSI SRI2C SRUSB SRCAN SRADC SRACMP SREEPROM SRWTIMER RCGCWD RCGCTIMER
RO RO RO RO RO RO RO RO RO RO RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W
0x0000.00FF 0x0000.000F 0x0000.000F 0x0000.0001 0x0000.0001 0x0000.0003 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.0001 0x0000.003F 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000
0x608
RCGCGPIO
R/W
0x0000.0000
312
0x60C
RCGCDMA
R/W
0x0000.0000
314
227
System Control

Offset 0x614 0x618 Name RCGCHIB RCGCUART Type R/W R/W Reset 0x0000.0001 0x0000.0000 Description Hibernation Run Mode Clock Gating Control Universal Asynchronous Receiver/Transmitter Run Mode Clock Gating Control Synchronous Serial Interface Run Mode Clock Gating Control Inter-Integrated Circuit Run Mode Clock Gating Control Universal Serial Bus Run Mode Clock Gating Control Controller Area Network Run Mode Clock Gating Control Analog-to-Digital Converter Run Mode Clock Gating Control Analog Comparator Run Mode Clock Gating Control EEPROM Run Mode Clock Gating Control 32/64-Bit Wide General-Purpose Timer Run Mode Clock Gating Control Watchdog Timer Sleep Mode Clock Gating Control 16/32-Bit General-Purpose Timer Sleep Mode Clock Gating Control General-Purpose Input/Output Sleep Mode Clock Gating Control Micro Direct Memory Access Sleep Mode Clock Gating Control Hibernation Sleep Mode Clock Gating Control Universal Asynchronous Receiver/Transmitter Sleep Mode Clock Gating Control Synchronous Serial Interface Sleep Mode Clock Gating Control Inter-Integrated Circuit Sleep Mode Clock Gating Control Universal Serial Bus Sleep Mode Clock Gating Control Controller Area Network Sleep Mode Clock Gating Control Analog-to-Digital Converter Sleep Mode Clock Gating Control Analog Comparator Sleep Mode Clock Gating Control EEPROM Sleep Mode Clock Gating Control 32/64-Bit Wide General-Purpose Timer Sleep Mode Clock Gating Control Watchdog Timer Deep-Sleep Mode Clock Gating Control See page 315 316
0x61C 0x620 0x628 0x634 0x638 0x63C 0x658 0x65C 0x700 0x704
RCGCSSI RCGCI2C RCGCUSB RCGCCAN RCGCADC RCGCACMP RCGCEEPROM RCGCWTIMER SCGCWD SCGCTIMER
R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W
0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000
318 320 322 323 324 325 326 327 329 330
0x708
SCGCGPIO
R/W
0x0000.0000
332
0x70C 0x714 0x718
SCGCDMA SCGCHIB SCGCUART
R/W R/W R/W
0x0000.0000 0x0000.0001 0x0000.0000
334 335 336
0x71C 0x720 0x728 0x734
SCGCSSI SCGCI2C SCGCUSB SCGCCAN
R/W R/W R/W R/W
0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000
338 340 342 343
0x738 0x73C 0x758 0x75C 0x800
SCGCADC SCGCACMP SCGCEEPROM SCGCWTIMER DCGCWD
R/W R/W R/W R/W R/W
0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000
344 345 346 347 349
April 25, 2012

Offset Name Type Reset Description 16/32-Bit General-Purpose Timer Deep-Sleep Mode Clock Gating Control General-Purpose Input/Output Deep-Sleep Mode Clock Gating Control Micro Direct Memory Access Deep-Sleep Mode Clock Gating Control Hibernation Deep-Sleep Mode Clock Gating Control Universal Asynchronous Receiver/Transmitter Deep-Sleep Mode Clock Gating Control Synchronous Serial Interface Deep-Sleep Mode Clock Gating Control Inter-Integrated Circuit Deep-Sleep Mode Clock Gating Control Universal Serial Bus Deep-Sleep Mode Clock Gating Control Controller Area Network Deep-Sleep Mode Clock Gating Control Analog-to-Digital Converter Deep-Sleep Mode Clock Gating Control Analog Comparator Deep-Sleep Mode Clock Gating Control EEPROM Deep-Sleep Mode Clock Gating Control 32/64-Bit Wide General-Purpose Timer Deep-Sleep Mode Clock Gating Control Watchdog Timer Power Control 16/32-Bit General-Purpose Timer Power Control General-Purpose Input/Output Power Control Micro Direct Memory Access Power Control Hibernation Power Control Universal Asynchronous Receiver/Transmitter Power Control Synchronous Serial Interface Power Control Inter-Integrated Circuit Power Control Universal Serial Bus Power Control Controller Area Network Power Control Analog-to-Digital Converter Power Control Analog Comparator Power Control See page 350
0x804
DCGCTIMER
R/W
0x0000.0000
0x808
DCGCGPIO
R/W
0x0000.0000
352
0x80C 0x814 0x818
DCGCDMA DCGCHIB DCGCUART
R/W R/W R/W
0x0000.0000 0x0000.0001 0x0000.0000
354 355 356
0x81C
DCGCSSI
R/W
0x0000.0000
358
0x820
DCGCI2C
R/W
0x0000.0000
360
0x828
DCGCUSB
R/W
0x0000.0000
362
0x834
DCGCCAN
R/W
0x0000.0000
363
0x838
DCGCADC
R/W
0x0000.0000
364
0x83C 0x858 0x85C 0x900 0x904 0x908 0x90C 0x914 0x918 0x91C 0x920 0x928 0x934 0x938 0x93C
DCGCACMP DCGCEEPROM DCGCWTIMER PCWD PCTIMER PCGPIO PCDMA PCHIB PCUART PCSSI PCI2C PCUSB PCCAN PCADC PCACMP
R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W
0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0003 0x0000.003F 0x0000.7FFF 0x0000.0001 0x0000.0001 0x0000.00FF 0x0000.000F 0x0000.003F 0x0000.0001 0x0000.0003 0x0000.0003 0x0000.0001
365 366 367 369 371 374 377 378 379 383 385 387 388 389 391
229
System Control

Offset 0x958 0x95C 0xA00 0xA04 0xA08 0xA0C 0xA14 0xA18 0xA1C 0xA20 0xA28 0xA34 0xA38 0xA3C 0xA58 0xA5C Name PCEEPROM PCWTIMER PRWD PRTIMER PRGPIO PRDMA PRHIB PRUART PRSSI PRI2C PRUSB PRCAN PRADC PRACMP PREEPROM PRWTIMER Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description EEPROM Power Control 32/64-Bit Wide General-Purpose Timer Power Control Watchdog Timer Peripheral Ready 16/32-Bit General-Purpose Timer Peripheral Ready General-Purpose Input/Output Peripheral Ready Micro Direct Memory Access Peripheral Ready Hibernation Peripheral Ready Universal Asynchronous Receiver/Transmitter Peripheral Ready Synchronous Serial Interface Peripheral Ready Inter-Integrated Circuit Peripheral Ready Universal Serial Bus Peripheral Ready Controller Area Network Peripheral Ready Analog-to-Digital Converter Peripheral Ready Analog Comparator Peripheral Ready EEPROM Peripheral Ready 32/64-Bit Wide General-Purpose Timer Peripheral Ready See page 392 393 396 397 399 401 402 403 405 407 409 410 411 412 413 414
System Control Legacy Registers 0x008 0x010 0x014 0x018 0x01C 0x020 0x024 0x028 0x02C 0x040 0x044 0x048 0x100 0x104 DC0 DC1 DC2 DC3 DC4 DC5 DC6 DC7 DC8 SRCR0 SRCR1 SRCR2 RCGC0 RCGC1 RO RO RO RO RO RO RO RO RO RO RO RO RO RO 0x007F.007F 0x1103.2FFF 0x030F.F037 0xBFFF.0FC0 0x0004.F03F 0x0000.0000 0x0000.0011 0xFFFF.FFFF 0x0FFF.0FFF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0040 0x0000.0000 Device Capabilities 0 Device Capabilities 1 Device Capabilities 2 Device Capabilities 3 Device Capabilities 4 Device Capabilities 5 Device Capabilities 6 Device Capabilities 7 Device Capabilities 8 Software Reset Control 0 Software Reset Control 1 Software Reset Control 2 Run Mode Clock Gating Control Register 0 Run Mode Clock Gating Control Register 1 416 418 421 424 428 431 433 434 437 440 442 445 447 450
April 25, 2012

Offset 0x108 0x110 0x114 0x118 0x120 0x124 0x128 0x190 0x1A0 Name RCGC2 SCGC0 SCGC1 SCGC2 DCGC0 DCGC1 DCGC2 DC9 NVMSTAT Type RO RO RO RO RO RO RO RO RO Reset 0x0000.0000 0x0000.0040 0x0000.0000 0x0000.0000 0x0000.0040 0x0000.0000 0x0000.0000 0x00FF.00FF 0x0000.0001 Description Run Mode Clock Gating Control Register 2 Sleep Mode Clock Gating Control Register 0 Sleep Mode Clock Gating Control Register 1 Sleep Mode Clock Gating Control Register 2 Deep Sleep Mode Clock Gating Control Register 0 Deep-Sleep Mode Clock Gating Control Register 1 Deep Sleep Mode Clock Gating Control Register 2 Device Capabilities 9 Non-Volatile Memory Information See page 453 455 457 460 462 464 467 469 471
5.5
System Control Register Descriptions

All addresses given are relative to the System Control base address of 0x400F.E000. Registers provided for legacy software support only are listed in System Control Legacy Register Descriptions on page 415.
231
System Control
Register 1: Device Identification 0 (DID0), offset 0x000

This register identifies the version of the microcontroller. Each microcontroller is uniquely identified by the combined values of the CLASS field in the DID0 register and the PARTNO field in the DID1 register.
Device Identification 0 (DID0)
Base 0x400F.E000 Offset 0x000 Type RO, reset 31
reserved
30
29 VER
28
27
26
25
24
23
22
21
20 CLASS
19
18
17
16
reserved RO 1 12 MAJOR RO 1 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4
Type Reset
RO 0 15
RO 0 14
RO 0 13
RO 0 3 MINOR
RO 1 2
RO 0 1
RO 1 0
Type Reset
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
RO -
Bit/Field 31
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DID0 Version This field defines the DID0 register format version. The version number is numeric. The value of the VER field is encoded as follows (all other encodings are reserved): Value Description 0x1 Second version of the DID0 register format.
30:28
VER
RO
0x01
27:24
reserved
RO
0x08
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Device Class The CLASS field value identifies the internal design from which all mask sets are generated for all microcontrollers in a particular product line. The CLASS field value is changed for new product lines, for changes in fab process (for example, a remap or shrink), or any case where the MAJOR or MINOR fields require differentiation from prior microcontrollers. The value of the CLASS field is encoded as follows (all other encodings are reserved): Value Description 0x05 Stellaris Blizzard-class microcontrollers
23:16
CLASS
RO
0x05
April 25, 2012
Bit/Field 15:8
Name MAJOR
Type RO
Reset -
Description Major Revision This field specifies the major revision number of the microcontroller. The major revision reflects changes to base layers of the design. The major revision number is indicated in the part number as a letter (A for first revision, B for second, and so on). This field is encoded as follows: Value Description 0x0 0x1 0x2 Revision A (initial device) Revision B (first base layer revision) Revision C (second base layer revision)
and so on. 7:0 MINOR RO Minor Revision This field specifies the minor revision number of the microcontroller. The minor revision reflects changes to the metal layers of the design. The MINOR field value is reset when the MAJOR field is changed. This field is numeric and is encoded as follows: Value Description 0x0 0x1 0x2 Initial device, or a major revision update. First metal layer change. Second metal layer change.
and so on.
233
System Control
Register 2: Device Identification 1 (DID1), offset 0x004

This register identifies the device family, part number, temperature range, pin count, and package type. Each microcontroller is uniquely identified by the combined values of the CLASS field in the DID0 register and the PARTNO field in the DID1 register.
Device Identification 1 (DID1)
Base 0x400F.E000 Offset 0x004 Type RO, reset 31 30 VER Type Reset RO 0 15 RO 0 14 PINCOUNT Type Reset RO 0 RO 1 RO 1 RO 0 RO 0 RO 0 13 RO 1 12 RO 0 11 RO 0 10 reserved RO 0 RO 0 RO 0 RO 0 29 28 27 26 FAM RO 0 9 RO 0 8 RO 0 7 RO 0 6 TEMP RO 0 RO 1 RO 0 RO 0 5 25 24 23 22 21 20 19 18 17 16
PARTNO RO 0 4 PKG RO 1 RO 0 3 RO 1 2 ROHS RO 1 RO RO 0 1 QUAL RO RO 0 0
Bit/Field 31:28
Name VER
Type RO
Reset 0x1
Description DID1 Version This field defines the DID1 register format version. The version number is numeric. The value of the VER field is encoded as follows (all other encodings are reserved): Value Description 0x0 0x1 Initial DID1 register format definition, indicating a Stellaris LM3Snnn device. Second version of the DID1 register format.
27:24
FAM
RO
0x0
Family This field provides the family identification of the device within the Stellaris product portfolio. The value is encoded as follows (all other encodings are reserved): Value Description 0x0 Stellaris family of microcontrollers, that is, all devices with external part numbers starting with LM3S, LM4S, and LM4F.
23:16
PARTNO
RO
0x4
Part Number This field provides the part number of the device within the family. The reset value shown indicates the LM4F120H5QR microcontroller.
April 25, 2012
Bit/Field 15:13
Name PINCOUNT
Type RO
Reset 0x3
Description Package Pin Count This field specifies the number of pins on the device package. The value is encoded as follows (all other encodings are reserved): Value Description 0x0 0x1 0x2 0x3 0x4 0x5 28-pin package 48-pin package 100-pin package 64-pin package 144-pin package 157-pin package
12:8
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Temperature Range This field specifies the temperature rating of the device. The value is encoded as follows (all other encodings are reserved): Value Description 0x0 0x1 0x2 Commercial temperature range (0C to 70C) Industrial temperature range (-40C to 85C) Extended temperature range (-40C to 105C)
7:5
TEMP
RO
0x1
4:3
PKG
RO
0x1
Package Type This field specifies the package type. The value is encoded as follows (all other encodings are reserved): Value Description 0x0 0x1 0x2 SOIC package LQFP package BGA package
ROHS
RO
0x1
RoHS-Compliance This bit specifies whether the device is RoHS-compliant. A 1 indicates the part is RoHS-compliant.
1:0
QUAL
RO
Qualification Status This field specifies the qualification status of the device. The value is encoded as follows (all other encodings are reserved): Value Description 0x0 0x1 0x2 Engineering Sample (unqualified) Pilot Production (unqualified) Fully Qualified
235
System Control
Register 3: Brown-Out Reset Control (PBORCTL), offset 0x030

This register is responsible for controlling reset conditions after initial power-on reset.
Brown-Out Reset Control (PBORCTL)
Base 0x400F.E000 Offset 0x030 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 BORIOR R/W 0 RO 0 0

reserved
RO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. BOR Interrupt or Reset Value Description 0 1 A Brown Out Event causes an interrupt to be generated to the interrupt controller. A Brown Out Event causes a reset of the microcontroller.
BORIOR
R/W
reserved
RO
April 25, 2012
Register 4: Raw Interrupt Status (RIS), offset 0x050

This register indicates the status for system control raw interrupts. An interrupt is sent to the interrupt controller if the corresponding bit in the Interrupt Mask Control (IMC) register is set. Writing a 1 to the corresponding bit in the Masked Interrupt Status and Clear (MISC) register clears an interrupt status bit.
Raw Interrupt Status (RIS)
Base 0x400F.E000 Offset 0x050 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 PLLLRIS RO 0 RO 0 5 reserved RO 0 RO 0 RO 0 4 RO 0 3 MOFRIS RO 0 RO 0 2

reserved
RO 0 1 BORRIS RO 0
RO 0 0
reserved
MOSCPUPRIS USBPLLLRIS
RO 0
RO 0
RO 0
RO 0
Bit/Field 31:9
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. MOSC Power Up Raw Interrupt Status Value Description 1 Sufficient time has passed for the MOSC to reach the expected frequency. The value for this power-up time is indicated by TMOSC_START. Sufficient time has not passed for the MOSC to reach the expected frequency.
MOSCPUPRIS
RO
This bit is cleared by writing a 1 to the MOSCPUPMIS bit in the MISC register. 7 USBPLLLRIS RO 0 USB PLL Lock Raw Interrupt Status Value Description 1 0 The USB PLL timer has reached TREADY indicating that sufficient time has passed for the USB PLL to lock. The USB PLL timer has not reached TREADY.
This bit is cleared by writing a 1 to the USBPLLLMIS bit in the MISC register. 6 PLLLRIS RO 0 PLL Lock Raw Interrupt Status Value Description 1 0 The PLL timer has reached TREADY indicating that sufficient time has passed for the PLL to lock. The PLL timer has not reached TREADY.
This bit is cleared by writing a 1 to the PLLLMIS bit in the MISC register.
237
System Control
Bit/Field 5:4
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Main Oscillator Failure Raw Interrupt Status Value Description 1 0 The MOSCIM bit in the MOSCCTL register is set and the main oscillator has failed. The main oscillator has not failed.
MOFRIS
RO
This bit is cleared by writing a 1 to the MOFMIS bit in the MISC register. 2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Brown-Out Reset Raw Interrupt Status Value Description 1 0 A brown-out condition is currently active. A brown-out condition is not currently active.
BORRIS
RO
Note the BORIOR bit in the PBORCTL register must be cleared to cause an interrupt due to a Brown Out Event. This bit is cleared by writing a 1 to the BORMIS bit in the MISC register. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Register 5: Interrupt Mask Control (IMC), offset 0x054

This register contains the mask bits for system control raw interrupts. A raw interrupt, indicated by a bit being set in the Raw Interrupt Status (RIS) register, is sent to the interrupt controller if the corresponding bit in this register is set.
Interrupt Mask Control (IMC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 PLLLIM R/W 0 RO 0 5 reserved RO 0 RO 0 RO 0 4 RO 0 3 MOFIM RO 0 RO 0 2
reserved
RO 0 1 BORIM R/W 0
RO 0 0
reserved
MOSCPUPIM USBPLLLIM
R/W 0
R/W 0
RO 0
RO 0
Bit/Field 31:9
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. MOSC Power Up Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the MOSCPUPRIS bit in the RIS register is set. The MOSCPUPRIS interrupt is suppressed and not sent to the interrupt controller.
MOSCPUPIM
R/W
USBPLLLIM
R/W
USB PLL Lock Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the USBPLLLRIS bit in the RIS register is set. The USBPLLLRIS interrupt is suppressed and not sent to the interrupt controller.
PLLLIM
R/W
PLL Lock Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the PLLLRIS bit in the RIS register is set. The PLLLRIS interrupt is suppressed and not sent to the interrupt controller.
5:4
reserved
RO
0x0
239
System Control
Bit/Field 3
Name MOFIM
Type RO
Reset 0
Description Main Oscillator Failure Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the MOFRIS bit in the RIS register is set. The MOFRIS interrupt is suppressed and not sent to the interrupt controller.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Brown-Out Reset Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the BORRIS bit in the RIS register is set. The BORRIS interrupt is suppressed and not sent to the interrupt controller.
BORIM
R/W
reserved
RO
April 25, 2012
Register 6: Masked Interrupt Status and Clear (MISC), offset 0x058

On a read, this register gives the current masked status value of the corresponding interrupt in the Raw Interrupt Status (RIS) register. All of the bits are R/W1C, thus writing a 1 to a bit clears the corresponding raw interrupt bit in the RIS register (see page 237).
Masked Interrupt Status and Clear (MISC)
Base 0x400F.E000 Offset 0x058 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 PLLLMIS R/W1C 0 RO 0 5 reserved RO 0 RO 0 RO 0 4 RO 0 3 MOFMIS RO 0 RO 0 2
reserved
RO 0 1 BORMIS R/W1C 0
RO 0 0
reserved
MOSCPUPMIS USBPLLLMIS
R/W1C 0
R/W1C 0
RO 0
RO 0
Bit/Field 31:9
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. MOSC Power Up Masked Interrupt Status Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because sufficient time has passed for the MOSC PLL to lock. Writing a 1 to this bit clears it and also the MOSCPUPRIS bit in the RIS register. 0 When read, a 0 indicates that sufficient time has not passed for the MOSC PLL to lock. A write of 0 has no effect on the state of this bit.
MOSCPUPMIS
R/W1C
USBPLLLMIS
R/W1C
USB PLL Lock Masked Interrupt Status Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because sufficient time has passed for the USB PLL to lock. Writing a 1 to this bit clears it and also the USBPLLLRIS bit in the RIS register. 0 When read, a 0 indicates that sufficient time has not passed for the USB PLL to lock. A write of 0 has no effect on the state of this bit.
241
System Control
Bit/Field 6
Name PLLLMIS
Type R/W1C
Reset 0
Description PLL Lock Masked Interrupt Status Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because sufficient time has passed for the PLL to lock. Writing a 1 to this bit clears it and also the PLLLRIS bit in the RIS register. 0 When read, a 0 indicates that sufficient time has not passed for the PLL to lock. A write of 0 has no effect on the state of this bit.
5:4
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Main Oscillator Failure Masked Interrupt Status Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because the main oscillator failed. Writing a 1 to this bit clears it and also the MOFRIS bit in the RIS register. 0 When read, a 0 indicates that the main oscillator has not failed. A write of 0 has no effect on the state of this bit.
MOFMIS
RO
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. BOR Masked Interrupt Status Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because of a brown-out condition. Writing a 1 to this bit clears it and also the BORRIS bit in the RIS register. 0 When read, a 0 indicates that a brown-out condition has not occurred. A write of 0 has no effect on the state of this bit.
BORMIS
R/W1C
reserved
RO
April 25, 2012
Register 7: Reset Cause (RESC), offset 0x05C

This register is set with the reset cause after reset. The bits in this register are sticky and maintain their state across multiple reset sequences, except when an power-on reset is the cause, in which case, all bits other than POR in the RESC register are cleared.
Reset Cause (RESC)
Base 0x400F.E000 Offset 0x05C Type R/W, reset 31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 WDT1 RO 0 RO 0 RO 0 RO 0 R/W RO 0 4 SW R/W RO 0 3 WDT0 R/W RO 0 2 BOR R/W RO 0 1 POR R/W 23 22 21 20 19 18 17 16
MOSCFAIL
R/W 0 EXT R/W -
Bit/Field 31:17
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. MOSC Failure Reset Value Description 1 When read, this bit indicates that the MOSC circuit was enabled for clock validation and failed while the MOSCIM bit in the MOSCCTL register is clear, generating a reset event. When read, this bit indicates that a MOSC failure has not generated a reset since the previous power-on reset. Writing a 0 to this bit clears it.
16
MOSCFAIL
R/W
15:6
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Reset Value Description 1 0 When read, this bit indicates that Watchdog Timer 1 timed out and generated a reset. When read, this bit indicates that Watchdog Timer 1 has not generated a reset since the previous power-on reset. Writing a 0 to this bit clears it.
WDT1
R/W
243
System Control
Bit/Field 4
Name SW
Type R/W
Reset -
Description Software Reset Value Description 1 0 When read, this bit indicates that a software reset has caused a reset event. When read, this bit indicates that a software reset has not generated a reset since the previous power-on reset. Writing a 0 to this bit clears it.
WDT0
R/W
Watchdog Timer 0 Reset Value Description 1 0 When read, this bit indicates that Watchdog Timer 0 timed out and generated a reset. When read, this bit indicates that Watchdog Timer 0 has not generated a reset since the previous power-on reset. Writing a 0 to this bit clears it.
BOR
R/W
Brown-Out Reset Value Description 1 0 When read, this bit indicates that a brown-out reset has caused a reset event. When read, this bit indicates that a brown-out reset has not generated a reset since the previous power-on reset. Writing a 0 to this bit clears it.
POR
R/W
Power-On Reset Value Description 1 0 When read, this bit indicates that a power-on reset has caused a reset event. When read, this bit indicates that a power-on reset has not generated a reset. Writing a 0 to this bit clears it.
EXT
R/W
External Reset Value Description 1 0 When read, this bit indicates that an external reset (RST assertion) has caused a reset event. When read, this bit indicates that an external reset (RST assertion) has not caused a reset event since the previous power-on reset. Writing a 0 to this bit clears it.
April 25, 2012
Register 8: Run-Mode Clock Configuration (RCC), offset 0x060

The bits in this register configure the system clock and oscillators. Important: Write the RCC register prior to writing the RCC2 register. If a subsequent write to the RCC register is required, include another register access after writing the RCC register and before writing the RCC2 register.
Run-Mode Clock Configuration (RCC)
Base 0x400F.E000 Offset 0x060 Type R/W, reset 0x0780.3D51
31 30 29 28 27 ACG RO 0 12
reserved
26
25 SYSDIV
24
23
22
USESYSDIV
21
20
19
18
17
16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 PWRDN R/W 1
reserved RO 0 5 OSCSRC RO 0 4 RO 0 3 reserved RO 0 RO 0 RO 0 2 RO 0 1 RO 0 0
R/W 0 11 BYPASS R/W 1
R/W 1 10
R/W 1 9
R/W 1 8 XTAL
R/W 1 7
R/W 0 6
reserved Type Reset RO 0 RO 0
IOSCDIS MOSCDIS R/W 0 R/W 1
RO 1
R/W 1
R/W 0
R/W 1
R/W 0
R/W 1
R/W 0
R/W 1
Bit/Field 31:28
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Auto Clock Gating This bit specifies whether the system uses the Sleep-Mode Clock Gating Control (SCGCn) registers and Deep-Sleep-Mode Clock Gating Control (DCGCn) registers if the microcontroller enters a Sleep or Deep-Sleep mode (respectively). Value Description 1 The SCGCn or DCGCn registers are used to control the clocks distributed to the peripherals when the microcontroller is in a sleep mode. The SCGCn and DCGCn registers allow unused peripherals to consume less power when the microcontroller is in a sleep mode. The Run-Mode Clock Gating Control (RCGCn) registers are used when the microcontroller enters a sleep mode.
27
ACG
R/W
The RCGCn registers are always used to control the clocks in Run mode. 26:23 SYSDIV R/W 0xF System Clock Divisor Specifies which divisor is used to generate the system clock from either the PLL output or the oscillator source (depending on how the BYPASS bit in this register is configured). See Table 5-4 on page 219 for bit encodings. If the SYSDIV value is less than MINSYSDIV (see page 418), and the PLL is being used, then the MINSYSDIV value is used as the divisor. If the PLL is not being used, the SYSDIV value can be less than MINSYSDIV.
245
System Control
Bit/Field 22
Name USESYSDIV
Type R/W
Reset 0
Description Enable System Clock Divider Value Description 1 The system clock divider is the source for the system clock. The system clock divider is forced to be used when the PLL is selected as the source. If the USERCC2 bit in the RCC2 register is set, then the SYSDIV2 field in the RCC2 register is used as the system clock divider rather than the SYSDIV field in this register. 0 The system clock is used undivided.
21:14
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL Power Down Value Description 1 The PLL is powered down. Care must be taken to ensure that another clock source is functioning and that the BYPASS bit is set before setting this bit. The PLL is operating normally.
13
PWRDN
R/W
12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL Bypass Value Description 1 0 The system clock is derived from the OSC source and divided by the divisor specified by SYSDIV. The system clock is the PLL output clock divided by the divisor specified by SYSDIV.
11
BYPASS
R/W
See Table 5-4 on page 219 for programming guidelines. Note: The ADC must be clocked from the PLL or directly from a 16-MHz clock source to operate properly.
April 25, 2012
Bit/Field 10:6
Name XTAL
Type R/W
Reset 0x15
Description Crystal Value This field specifies the crystal value attached to the main oscillator. The encoding for this field is provided below. Frequencies that may be used with the USB interface are indicated in the table. To function within the clocking requirements of the USB specification, a crystal of 5, 6, 8, 10, 12, or 16 MHz must be used. Value 0x00-0x5 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 4 MHz 4.096 MHz 4.9152 MHz 5 MHz (USB) 5.12 MHz 6 MHz (USB) 6.144 MHz 7.3728 MHz 8 MHz (USB) 8.192 MHz 10.0 MHz (USB) 12.0 MHz (USB) 12.288 MHz 13.56 MHz 14.31818 MHz 16.0 MHz (reset value)(USB) 16.384 MHz 18.0 MHz (USB) 20.0 MHz (USB) 24.0 MHz (USB) 25.0 MHz (USB) Crystal Frequency (MHz) Not Using the PLL Crystal Frequency (MHz) Using the PLL
reserved reserved reserved reserved
247
System Control
Bit/Field 5:4
Name OSCSRC
Type R/W
Reset 0x1
Description Oscillator Source Selects the input source for the OSC. The values are: Value Input Source 0x0 0x1 MOSC Main oscillator PIOSC Precision internal oscillator (default) 0x2 0x3 PIOSC/4 Precision internal oscillator / 4 30 kHz 30-kHz internal oscillator For additional oscillator sources, see the RCC2 register.
3:2
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Precision Internal Oscillator Disable Value Description 1 0 The precision internal oscillator (PIOSC) is disabled. The precision internal oscillator is enabled.
IOSCDIS
R/W
MOSCDIS
R/W
Main Oscillator Disable Value Description 1 0 The main oscillator is disabled (default). The main oscillator is enabled.
April 25, 2012
Register 9: GPIO High-Performance Bus Control (GPIOHBCTL), offset 0x06C

This register controls which internal bus is used to access each GPIO port. When a bit is clear, the corresponding GPIO port is accessed across the legacy Advanced Peripheral Bus (APB) bus and through the APB memory aperture. When a bit is set, the corresponding port is accessed across the Advanced High-Performance Bus (AHB) bus and through the AHB memory aperture. Each GPIO port can be individually configured to use AHB or APB, but may be accessed only through one aperture. The AHB bus provides better back-to-back access performance than the APB bus. The address aperture in the memory map changes for the ports that are enabled for AHB access (see Table 10-6 on page 641). Important: Ports K-N and P-Q are only available on the AHB bus, and therefore the corresponding bits reset to 1. If one of these bits is cleared, the corresponding port is disabled. If any of these ports is in use, read-modify-write operations should be used to change the value of this register so that these ports remain enabled.
GPIO High-Performance Bus Control (GPIOHBCTL)
Base 0x400F.E000 Offset 0x06C Type R/W, reset 0x0000.7E00
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 PORTF RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 PORTE R/W 0 RO 0 3 PORTD R/W 0 RO 0 2 PORTC R/W 0 RO 0 1 PORTB R/W 0 RO 0 0 PORTA R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Port F Advanced High-Performance Bus This bit defines the memory aperture for Port F. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
PORTF
R/W
PORTE
R/W
Port E Advanced High-Performance Bus This bit defines the memory aperture for Port E. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
249
System Control
Bit/Field 3
Name PORTD
Type R/W
Reset 0
Description Port D Advanced High-Performance Bus This bit defines the memory aperture for Port D. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
PORTC
R/W
Port C Advanced High-Performance Bus This bit defines the memory aperture for Port C. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
PORTB
R/W
Port B Advanced High-Performance Bus This bit defines the memory aperture for Port B. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
PORTA
R/W
Port A Advanced High-Performance Bus This bit defines the memory aperture for Port A. Value Description 1 0 Advanced High-Performance Bus (AHB) Advanced Peripheral Bus (APB). This bus is the legacy bus.
April 25, 2012
Register 10: Run-Mode Clock Configuration 2 (RCC2), offset 0x070

This register overrides the RCC equivalent register fields, as shown in Table 5-8, when the USERCC2 bit is set, allowing the extended capabilities of the RCC2 register to be used while also providing a means to be backward-compatible to previous parts. Each RCC2 field that supersedes an RCC field is located at the same LSB bit position; however, some RCC2 fields are larger than the corresponding RCC field. Table 5-8. RCC2 Fields that Override RCC Fields
RCC2 Field... SYSDIV2, bits[28:23] PWRDN2, bit[13] BYPASS2, bit[11] OSCSRC2, bits[6:4] Overrides RCC Field SYSDIV, bits[26:23] PWRDN, bit[13] BYPASS, bit[11] OSCSRC, bits[5:4]
Important: Write the RCC register prior to writing the RCC2 register. If a subsequent write to the RCC register is required, include another register access after writing the RCC register and before writing the RCC2 register.
Run-Mode Clock Configuration 2 (RCC2)
Base 0x400F.E000 Offset 0x070 Type R/W, reset 0x07C0.6810
31 30 29
reserved
28
27
26
25
24
23
22
SYSDIV2LSB
21
20
19
18
17
16
USERCC2 DIV400 Type Reset R/W 0 15

reserved
SYSDIV2 R/W 0 12
reserved
reserved RO 0 5 OSCSRC2 RO 0 4 RO 0 3 RO 0 2 reserved R/W 1 RO 0 RO 0 RO 0 RO 0 RO 0 1 RO 0 0
R/W 0 14
USBPWRDN
RO 0 13 PWRDN2 R/W 1
R/W 0 11 BYPASS2 R/W 1
R/W 1 10
R/W 1 9
R/W 1 8
R/W 1 7
R/W 1 6
reserved RO 0 RO 0 RO 0 RO 0 R/W 0
Type Reset
RO 0
R/W 1
RO 0
R/W 0
Bit/Field 31
Name USERCC2
Type R/W
Reset 0
Description Use RCC2 Value Description 1 0 The RCC2 register fields override the RCC register fields. The RCC register fields are used, and the fields in RCC2 are ignored.
30
DIV400
R/W
Divide PLL as 400 MHz vs. 200 MHz This bit, along with the SYSDIV2LSB bit, allows additional frequency choices. Value Description 1 Append the SYSDIV2LSB bit to the SYSDIV2 field to create a 7 bit divisor using the 400 MHz PLL output, see Table 5-6 on page 220. Use SYSDIV2 as is and apply to 200 MHz predivided PLL output. See Table 5-5 on page 219 for programming guidelines.
251
System Control
Bit/Field 29
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. System Clock Divisor 2 Specifies which divisor is used to generate the system clock from either the PLL output or the oscillator source (depending on how the BYPASS2 bit is configured). SYSDIV2 is used for the divisor when both the USESYSDIV bit in the RCC register and the USERCC2 bit in this register are set. See Table 5-5 on page 219 for programming guidelines.
28:23
SYSDIV2
R/W
0x0F
22
SYSDIV2LSB
R/W
Additional LSB for SYSDIV2 When DIV400 is set, this bit becomes the LSB of SYSDIV2. If DIV400 is clear, this bit is not used. See Table 5-5 on page 219 for programming guidelines. This bit can only be set or cleared when DIV400 is set.
21:15
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Power-Down USB PLL Value Description 1 0 The USB PLL is powered down. The USB PLL operates normally.
14
USBPWRDN
R/W
13
PWRDN2
R/W
Power-Down PLL 2 Value Description 1 0 The PLL is powered down. The PLL operates normally.
12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL Bypass 2 Value Description 1 0 The system clock is derived from the OSC source and divided by the divisor specified by SYSDIV2. The system clock is the PLL output clock divided by the divisor specified by SYSDIV2.
11
BYPASS2
R/W
See Table 5-5 on page 219 for programming guidelines. Note: The ADC must be clocked from the PLL or directly from a 16-MHz clock source to operate properly.
10:7
reserved
RO
0x0
April 25, 2012
Bit/Field 6:4
Name OSCSRC2
Type R/W
Reset 0x1
Description Oscillator Source 2 Selects the input source for the OSC. The values are: Value 0x0 0x1 0x2 0x3 Description MOSC Main oscillator PIOSC Precision internal oscillator PIOSC/4 Precision internal oscillator / 4 30 kHz 30-kHz internal oscillator 0x4-0x6 Reserved 0x7 32.768 kHz 32.768-kHz external oscillator
3:0
reserved
RO
0x0
253
System Control
Register 11: Main Oscillator Control (MOSCCTL), offset 0x07C

This register provides control over the features of the main oscillator, including the ability to enable the MOSC clock verification circuit, what action to take when the MOSC fails, and whether or not a crystal is connected. When enabled, this circuit monitors the frequency of the MOSC to verify that the oscillator is operating within specified limits. If the clock goes invalid after being enabled, the microcontroller issues a power-on reset and reboots to the NMI handler or generates an interrupt.
Main Oscillator Control (MOSCCTL)
Base 0x400F.E000 Offset 0x07C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 CVAL R/W 0
NOXTAL MOSCIM R/W 0 R/W 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. No Crystal Connected Value Description 1 This bit should be set when a crystal or external oscillator is not connected to the OSC0 and OSC1 inputs to reduce power consumption. This bit should be cleared when a crystal or oscillator is connected to the OSC0 and OSC1 inputs, regardless of whether or not the MOSC is used or powered down.
NOXTAL
R/W
MOSCIM
R/W
MOSC Failure Action Value Description 1 0 If the MOSC fails, an interrupt is generated as indicated by the MOFRIS bit in the RIS register.. If the MOSC fails, a MOSC failure reset is generated and reboots to the NMI handler.
Regardless of the action taken, if the MOSC fails, the oscillator source is switched to the PIOSC automatically. 0 CVAL R/W 0 Clock Validation for MOSC Value Description 1 0 The MOSC monitor circuit is enabled. The MOSC monitor circuit is disabled.
April 25, 2012
Register 12: Deep Sleep Clock Configuration (DSLPCLKCFG), offset 0x144

This register provides configuration information for the hardware control of Deep Sleep Mode.
Deep Sleep Clock Configuration (DSLPCLKCFG)
31 30 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 R/W 0 12 R/W 0 11 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 29 28 27 26 25 24 23 22 21 20 19 reserved R/W 1 8 R/W 1 7 RO 0 6 RO 0 5 DSOSCSRC R/W 0 R/W 0 RO 0 RO 0 4 RO 0 3 RO 0 2 reserved RO 0 RO 0 RO 0 RO 0 1 RO 0 0 18 17 16
DSDIVORIDE R/W 1 10 R/W 1 9
Bit/Field 31:29
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Divider Field Override If Deep-Sleep mode is enabled when the PLL is running, the PLL is disabled. This 6-bit field contains a system divider field that overrides the SYSDIV field in the RCC register or the SYSDIV2 field in the RCC2 register during Deep Sleep. This divider is applied to the source selected by the DSOSCSRC field. Value Description 0x0 0x1 0x2 0x3 ... /1 /2 /3 /4 ...
28:23
DSDIVORIDE
R/W
0x0F
0x3F /64
22:7
reserved
RO
0x000
255
System Control
Bit/Field 6:4
Name DSOSCSRC
Type R/W
Reset 0x0
Description Clock Source Specifies the clock source during Deep-Sleep mode. Value 0x0 Description MOSC Use the main oscillator as the source. Note: If the PIOSC is being used as the clock reference for the PLL, the PIOSC is the clock source instead of MOSC in Deep-Sleep mode.
0x1 0x2 0x3
PIOSC Use the precision internal 16-MHz oscillator as the source. Reserved 30 kHz Use the 30-kHz internal oscillator as the source.
0x4-0x6 Reserved 0x7 32.768 kHz Use the Hibernation module 32.768-kHz external oscillator as the source.
3:0
reserved
RO
0x0
April 25, 2012
Register 13: System Properties (SYSPROP), offset 0x14C

This register provides information on whether certain System Control properties are present on the microcontroller.
System Properties (SYSPROP)
Base 0x400F.E000 Offset 0x14C Type RO, reset 0x0000.1D31
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 1 RO 1 RO 1 RO 0 RO 1 RO 0 RO 0 RO 1 RO 1 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 FPU RO 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0xE98
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. FPU Present This bit indicates if the FPU is present in the Cortex-M4 core. Value Description 0 1 FPU is not present. FPU is present.
FPU
RO
0x1
257
System Control
Register 14: Precision Internal Oscillator Calibration (PIOSCCAL), offset 0x150

This register provides the ability to update or recalibrate the precision internal oscillator. Note that a 32.768-kHz oscillator must be used as the Hibernation module clock source for the user to be able to calibrate the PIOSC.
Precision Internal Oscillator Calibration (PIOSCCAL)
31 UTEN Type Reset R/W 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 CAL RO 0 RO 0 R/W 0 RO 0 8 UPDATE R/W 0 30 29 28 27 26 25 24 23 reserved RO 0 7
reserved
22
21
20
19
18
17
16
RO 0 6
RO 0 5
RO 0 4
RO 0 3 UT
RO 0 2
RO 0 1
RO 0 0
reserved Type Reset RO 0 RO 0 RO 0 RO 0
RO 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
Bit/Field 31
Name UTEN
Type R/W
Reset 0
Description Use User Trim Value Value Description 1 0 The trim value in bits[6:0] of this register are used for any update trim operation. The factory calibration value is used for an update trim operation.
30:10
reserved
RO
0x0000
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Start Calibration Value Description 1 Starts a new calibration of the PIOSC. Results are in the PIOSCSTAT register. The resulting trim value from the operation is active in the PIOSC after the calibration completes. The result overrides any previous update trim operation whether the calibration passes or fails. No action.
CAL
R/W
This bit is auto-cleared after it is set. 8 UPDATE R/W 0 Update Trim Value Description 1 0 Updates the PIOSC trim value with the UT bit or the DT bit in the PIOSCSTAT register. Used with UTEN. No action.
This bit is auto-cleared after the update. 7 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Bit/Field 6:0
Name UT
Type R/W
Reset 0x0
Description User Trim Value User trim value that can be loaded into the PIOSC. Refer to Main PLL Frequency Configuration on page 221 for more information on calibrating the PIOSC.
259
System Control
Register 15: Precision Internal Oscillator Statistics (PIOSCSTAT), offset 0x154

This register provides the user information on the PIOSC calibration. Note that a 32.768-kHz oscillator must be used as the Hibernation module clock source for the user to be able to calibrate the PIOSC.
Precision Internal Oscillator Statistics (PIOSCSTAT)
31 30 29 28 27 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RESULT RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7
reserved
26
25
24
23
22
21
20
19 DT
18
17
16
RO 6
RO 5
RO 4
RO 3 CT
RO 2
RO 1
RO 0
RO 0
RO 1
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31:23
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Default Trim Value This field contains the default trim value. This value is loaded into the PIOSC after every full power-up.
22:16
DT
RO
15:10
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Calibration Result Value Description 0x0 0x1 0x2 0x3 Calibration has not been attempted. The last calibration operation completed to meet 1% accuracy. The last calibration operation failed to meet 1% accuracy. Reserved
9:8
RESULT
RO
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Calibration Trim Value This field contains the trim value from the last calibration operation. After factory calibration CT and DT are the same.
6:0
CT
RO
0x40
April 25, 2012
Register 16: PLL Frequency 0 (PLLFREQ0), offset 0x160

This register always contains the current M value presented to the system PLL. The PLL frequency can be calculated using the following equation: PLL frequency = (XTAL frequency * MDIV) / ((Q + 1) * (N + 1)) where MDIV = MINT + (MFRAC / 1024) The Q and N values are shown in the PLLFREQ1 register. Table 23-10 on page 1165 shows the M, Q, and N values as well as the resulting PLL frequency for the various XTAL configurations.
PLL Frequency 0 (PLLFREQ0)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 MFRAC RO 0 8 RO 0 7 RO 0 6 RO 0 5 MINT RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 MFRAC Type Reset RO 1 RO 1 RO 0 RO 0 RO 0 12 RO 0 11 RO 0 10 RO 0 9
Bit/Field 31:20
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL M Fractional Value This field contains the integer value of the PLL M value.
19:10
MFRAC
RO
0x32
9:0
MINT
RO
0x00
PLL M Integer Value This field contains the integer value of the PLL M value.
261
System Control
Register 17: PLL Frequency 1 (PLLFREQ1), offset 0x164

This register always contains the current Q and N values presented to the system PLL. The M value is shown in the PLLFREQ0 register. Table 23-10 on page 1165 shows the M, Q, and N values as well as the resulting PLL frequency for the various XTAL configurations.
PLL Frequency 1 (PLLFREQ1)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 13 RO 0 12 RO 0 11 RO 0 10 Q RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 N RO 0 RO 0 RO 1 RO 0 1 RO 0 0
Bit/Field 31:13
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL Q Value This field contains the PLL Q value.
12:8
RO
0x0
7:5
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL N Value This field contains the PLL N value.
4:0
RO
0x1
April 25, 2012
Register 18: PLL Status (PLLSTAT), offset 0x168

This register shows the direct status of the PLL lock.
PLL Status (PLLSTAT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 LOCK RO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PLL Lock Value Description 1 0 The PLL powered and locked. The PLL is unpowered or is not yet locked.
LOCK
RO
0x0
263
System Control
Register 19: Watchdog Timer Peripheral Present (PPWD), offset 0x300

The PPWD register provides software information regarding the watchdog modules. Important: This register should be used to determine which watchdog timers are implemented on this microcontroller. However, to support legacy software, the DC1 register is available. A read of the DC1 register correctly identifies if a legacy module is present.
Watchdog Timer Peripheral Present (PPWD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 P1 RO 1 RO 0 0 P0 RO 1
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Present Value Description 1 0 Watchdog module 1 is present. Watchdog module 1 is not present.
P1
RO
0x1
P0
RO
0x1
Watchdog Timer 0 Present Value Description 1 0 Watchdog module 0 is present. Watchdog module 0 is not present.
April 25, 2012
Register 20: 16/32-Bit General-Purpose Timer Peripheral Present (PPTIMER), offset 0x304
The PPTIMER register provides software information regarding the 16/32-bit general-purpose timer modules. Important: This register should be used to determine which timers are implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if a legacy module is present. Software must use this register to determine if a module that is not supported by the DC2 register is present.
16/32-Bit General-Purpose Timer Peripheral Present (PPTIMER)
Base 0x400F.E000 Offset 0x304 Type RO, reset 0x0000.003F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 P5 RO 0 RO 0 RO 0 RO 0 RO 1 RO 0 4 P4 RO 1 RO 0 3 P3 RO 1 RO 0 2 P2 RO 1 RO 0 1 P1 RO 1 RO 0 0 P0 RO 1
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Present Value Description 1 0 16/32-bit general-purpose timer module 5 is present. 16/32-bit general-purpose timer module 6 is not present.
P5
RO
0x1
P4
RO
0x1
16/32-Bit General-Purpose Timer 4 Present Value Description 1 0 16/32-bit general-purpose timer module 4 is present. 16/32-bit general-purpose timer module 4 is not present.
P3
RO
0x1
265
System Control
Bit/Field 2
Name P2
Type RO
Reset 0x1
Description 16/32-Bit General-Purpose Timer 2 Present Value Description 1 0 16/32-bit general-purpose timer module 2 is present. 16/32-bit general-purpose timer module 2 is not present.
P1
RO
0x1
P0
RO
0x1
April 25, 2012
Register 21: General-Purpose Input/Output Peripheral Present (PPGPIO), offset 0x308

The PPGPIO register provides software information regarding the general-purpose input/output modules. Important: This register should be used to determine which GPIO ports are implemented on this microcontroller. However, to support legacy software, the DC4 register is available. A read of the DC4 register correctly identifies if a legacy module is present. Software must use this register to determine if a module that is not supported by the DC4 register is present.
General-Purpose Input/Output Peripheral Present (PPGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15

reserved
RO 0 14 P14 RO 0
RO 0 13 P13 RO 0
RO 0 12 P12 RO 0
RO 0 11 P11 RO 0
RO 0 10 P10 RO 0
RO 0 9 P9 RO 0
RO 0 8 P8 RO 0
RO 0 7 P7 RO 0
RO 0 6 P6 RO 0
RO 0 5 P5 RO 1
RO 0 4 P4 RO 1
RO 0 3 P3 RO 1
RO 0 2 P2 RO 1
RO 0 1 P1 RO 1
RO 0 0 P0 RO 1
Type Reset
RO 0
Bit/Field 31:15
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port Q Present Value Description 1 0 GPIO Port Q is present. GPIO Port Q is not present.
14
P14
RO
0x0
13
P13
RO
0x0
GPIO Port P Present Value Description 1 0 GPIO Port P is present. GPIO Port P is not present.
12
P12
RO
0x0
GPIO Port N Present Value Description 1 0 GPIO Port N is present. GPIO Port N is not present.
267
System Control
Bit/Field 11
Name P11
Type RO
Reset 0x0
Description GPIO Port M Present Value Description 1 0 GPIO Port M is present. GPIO Port M is not present.
10
P10
RO
0x0
GPIO Port L Present Value Description 1 0 GPIO Port L is present. GPIO Port L is not present.
P9
RO
0x0
GPIO Port K Present Value Description 1 0 GPIO Port K is present. GPIO Port K is not present.
P8
RO
0x0
GPIO Port J Present Value Description 1 0 GPIO Port J is present. GPIO Port J is not present.
P7
RO
0x0
GPIO Port H Present Value Description 1 0 GPIO Port H is present. GPIO Port H is not present.
P6
RO
0x0
GPIO Port G Present Value Description 1 0 GPIO Port G is present. GPIO Port G is not present.
P5
RO
0x1
GPIO Port F Present Value Description 1 0 GPIO Port F is present. GPIO Port F is not present.
April 25, 2012
Bit/Field 4
Name P4
Type RO
Reset 0x1
Description GPIO Port E Present Value Description 1 0 GPIO Port E is present. GPIO Port E is not present.
P3
RO
0x1
GPIO Port D Present Value Description 1 0 GPIO Port D is present. GPIO Port D is not present.
P2
RO
0x1
GPIO Port C Present Value Description 1 0 GPIO Port C is present. GPIO Port C is not present.
P1
RO
0x1
GPIO Port B Present Value Description 1 0 GPIO Port B is present. GPIO Port B is not present.
P0
RO
0x1
GPIO Port A Present Value Description 1 0 GPIO Port A is present. GPIO Port A is not present.
269
System Control
Register 22: Micro Direct Memory Access Peripheral Present (PPDMA), offset 0x30C
The PPDMA register provides software information regarding the DMA module. Important: This register should be used to determine if the DMA module is implemented on this microcontroller. However, to support legacy software, the DC7 register is available. A read of the DC7 register correctly identifies if the DMA module is present.
Micro Direct Memory Access Peripheral Present (PPDMA)
Base 0x400F.E000 Offset 0x30C Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 P0 RO 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Present Value Description 1 0 DMA module is present. DMA module is not present.
P0
RO
0x1
April 25, 2012
Register 23: Hibernation Peripheral Present (PPHIB), offset 0x314

The PPHIB register provides software information regarding the Hibernation module. Important: This register should be used to determine if the Hibernation module is implemented on this microcontroller. However, to support legacy software, the DC1 register is available. A read of the DC1 register correctly identifies if the Hibernation module is present.
Hibernation Peripheral Present (PPHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Present Value Description 1 0 Hibernation module is present. Hibernation module is not present.
P0
RO
0x1
271
System Control
Register 24: Universal Asynchronous Receiver/Transmitter Peripheral Present (PPUART), offset 0x318
The PPUART register provides software information regarding the UART modules. Important: This register should be used to determine which UART modules are implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if a legacy UART module is present. Software must use this register to determine if a module that is not supported by the DC2 register is present.
Universal Asynchronous Receiver/Transmitter Peripheral Present (PPUART)
Base 0x400F.E000 Offset 0x318 Type RO, reset 0x0000.00FF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 P7 RO 0 RO 0 RO 0 RO 1 RO 0 6 P6 RO 1 RO 0 5 P5 RO 1 RO 0 4 P4 RO 1 RO 0 3 P3 RO 1 RO 0 2 P2 RO 1 RO 0 1 P1 RO 1 RO 0 0 P0 RO 1
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Present Value Description 1 0 UART module 7 is present. UART module 7 is not present.
P7
RO
0x1
P6
RO
0x1
UART Module 6 Present Value Description 1 0 UART module 6 is present. UART module 6 is not present.
P5
RO
0x1
April 25, 2012
Bit/Field 4
Name P4
Type RO
Reset 0x1
Description UART Module 4 Present Value Description 1 0 UART module 4 is present. UART module 4 is not present.
P3
RO
0x1
P2
RO
0x1
P1
RO
0x1
P0
RO
0x1
273
System Control
Register 25: Synchronous Serial Interface Peripheral Present (PPSSI), offset 0x31C
The PPSSI register provides software information regarding the SSI modules. Important: This register should be used to determine which SSI modules are implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if a legacy SSI module is present. Software must use this register to determine if a module that is not supported by the DC2 register is present.
Synchronous Serial Interface Peripheral Present (PPSSI)
Base 0x400F.E000 Offset 0x31C Type RO, reset 0x0000.000F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 P3 RO 1 RO 0 2 P2 RO 1 RO 0 1 P1 RO 1 RO 0 0 P0 RO 1
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Present Value Description 1 0 SSI module 3 is present. SSI module 3 is not present.
P3
RO
0x1
P2
RO
0x1
SSI Module 2 Present Value Description 1 0 SSI module 2 is present. SSI module 2 is not present.
P1
RO
0x1
SSI Module 1 Present Value Description 1 0 SSI module 1 is present. SSI module 1 is not present.
April 25, 2012
Bit/Field 0
Name P0
Type RO
Reset 0x1
Description SSI Module 0 Present Value Description 1 0 SSI module 0 is present. SSI module 0 is not present.
275
System Control
Register 26: Inter-Integrated Circuit Peripheral Present (PPI2C), offset 0x320

The PPI2C register provides software information regarding the I2C modules. Important: This register should be used to determine which I2C modules are implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if a legacy I2C module is present. Software must use this register to determine if a module that is not supported by the DC2 register is present.
Inter-Integrated Circuit Peripheral Present (PPI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 5 Present Value Description 1 0 I2C module 5 is present. I2C module 5 is not present.
P5
RO
0x0
P4
RO
0x0
I2C Module 4 Present Value Description 1 0 I2C module 4 is present. I2C module 4 is not present.
P3
RO
0x1
April 25, 2012
Bit/Field 2
Name P2
Type RO
Reset 0x1
Description I2C Module 2 Present Value Description 1 0 I2C module 2 is present. I2C module 2 is not present.
P1
RO
0x1
P0
RO
0x1
277
System Control
Register 27: Universal Serial Bus Peripheral Present (PPUSB), offset 0x328
The PPUSB register provides software information regarding the USB module. Important: This register should be used to determine if the USB module is implemented on this microcontroller. However, to support legacy software, the DC6 register is available. A read of the DC6 register correctly identifies if the USB module is present.
Universal Serial Bus Peripheral Present (PPUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Present Value Description 1 0 USB module is present. USB module is not present.
P0
RO
0x1
April 25, 2012
Register 28: Controller Area Network Peripheral Present (PPCAN), offset 0x334
The PPCAN register provides software information regarding the CAN modules. Important: This register should be used to determine which CAN modules are implemented on this microcontroller. However, to support legacy software, the DC1 register is available. A read of the DC1 register correctly identifies if a legacy CAN module is present.
Controller Area Network Peripheral Present (PPCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 1 Present Value Description 1 0 CAN module 1 is present. CAN module 1 is not present.
P1
RO
0x0
P0
RO
0x1
CAN Module 0 Present Value Description 1 0 CAN module 0 is present. CAN module 0 is not present.
279
System Control
Register 29: Analog-to-Digital Converter Peripheral Present (PPADC), offset 0x338

The PPADC register provides software information regarding the ADC modules. Important: This register should be used to determine which ADC modules are implemented on this microcontroller. However, to support legacy software, the DC1 register is available. A read of the DC1 register correctly identifies if a legacy ADC module is present.
Analog-to-Digital Converter Peripheral Present (PPADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Present Value Description 1 0 ADC module 1 is present. ADC module 1 is not present.
P1
RO
0x1
P0
RO
0x1
ADC Module 0 Present Value Description 1 0 ADC module 0 is present. ADC module 0 is not present.
April 25, 2012
Register 30: Analog Comparator Peripheral Present (PPACMP), offset 0x33C

The PPACMP register provides software information regarding the analog comparator module. Important: This register should be used to determine if the analog comparator module is implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if the analog comparator module is present. Note that the Analog Comparator Peripheral Properties (ACMPPP) register indicates how many analog comparator blocks are included in the module.
Analog Comparator Peripheral Present (PPACMP)
Base 0x400F.E000 Offset 0x33C Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module Present Value Description 1 0 Analog comparator module is present. Analog comparator module is not present.
P0
RO
0x1
281
System Control
Register 31: Pulse Width Modulator Peripheral Present (PPPWM), offset 0x340
The PPPWM register provides software information regarding the PWM modules. Important: This register should be used to determine which PWM modules are implemented on this microcontroller. However, to support legacy software, the DC1 register is available. A read of the DC1 register correctly identifies if the legacy PWM module is present. Software must use this register to determine if a module that is not supported by the DC1 register is present.
Pulse Width Modulator Peripheral Present (PPPWM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PWM Module 1 Present Value Description 1 0 PWM module 1 is present. PWM module 1 is not present.
P1
RO
0x0
P0
RO
0x0
PWM Module 0 Present Value Description 1 0 PWM module 0 is present. PWM module 0 is not present.
April 25, 2012
Register 32: Quadrature Encoder Interface Peripheral Present (PPQEI), offset 0x344
The PPQEI register provides software information regarding the QEI modules. Important: This register should be used to determine which QEI modules are implemented on this microcontroller. However, to support legacy software, the DC2 register is available. A read of the DC2 register correctly identifies if a legacy QEI module is present.
Quadrature Encoder Interface Peripheral Present (PPQEI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. QEI Module 1 Present Value Description 1 0 QEI module 1 is present. QEI module 1 is not present.
P1
RO
0x0
P0
RO
0x0
QEI Module 0 Present Value Description 1 0 QEI module 0 is present. QEI module 0 is not present.
283
System Control
Register 33: EEPROM Peripheral Present (PPEEPROM), offset 0x358

The PPEEPROM register provides software information regarding the EEPROM module.
EEPROM Peripheral Present (PPEEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Present Value Description 1 0 EEPROM module is present. EEPROM module is not present.
P0
RO
0x1
April 25, 2012
Register 34: 32/64-Bit Wide General-Purpose Timer Peripheral Present (PPWTIMER), offset 0x35C
The PPWTIMER register provides software information regarding the 32/64-bit wide general-purpose timer modules.
32/64-Bit Wide General-Purpose Timer Peripheral Present (PPWTIMER)
Base 0x400F.E000 Offset 0x35C Type RO, reset 0x0000.003F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Present Value Description 1 0 32/64-bit wide general-purpose timer module 5 is present. 32/64-bit wide general-purpose timer module 5 is not present.
P5
RO
0x1
P4
RO
0x1
32/64-Bit Wide General-Purpose Timer 4 Present Value Description 1 0 32/64-bit wide general-purpose timer module 4 is present. 32/64-bit wide general-purpose timer module 4 is not present.
P3
RO
0x1
P2
RO
0x1
285
System Control
Bit/Field 1
Name P1
Type RO
Reset 0x1
Description 32/64-Bit Wide General-Purpose Timer 1 Present Value Description 1 0 32/64-bit wide general-purpose timer module 1 is present. 32/64-bit wide general-purpose timer module 1 is not present.
P0
RO
0x1
April 25, 2012
Register 35: Watchdog Timer Software Reset (SRWD), offset 0x500

The SRWD register provides software the capability to reset the available watchdog modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRWD register. While the SRWD bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRWD bit. There may be latency from the clearing of the SRWD bit to when the peripheral is ready for use. Software can check the corresponding PRWD bit to be sure. Important: This register should be used to reset the watchdog modules. To support legacy software, the SRCR0 register is available. Setting a bit in the SRCR0 register also resets the corresponding module. Any bits that are changed by writing to the SRCR0 register can be read back correctly when reading the SRCR0 register. If software uses this register to reset a legacy peripheral (such as Watchdog 1), the write causes proper operation, but the value of that bit is not reflected in the SRCR0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Watchdog Timer Software Reset (SRWD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 R1 R/W 0 RO 0 0 R0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Software Reset Value Description 1 0 Watchdog module 1 is reset. Watchdog module 1 is not reset.
R1
R/W
287
System Control
Bit/Field 0
Name R0
Type R/W
Reset 0
Description Watchdog Timer 0 Software Reset Value Description 1 0 Watchdog module 0 is reset. Watchdog module 0 is not reset.
April 25, 2012
Register 36: 16/32-Bit General-Purpose Timer Software Reset (SRTIMER), offset 0x504
The SRTIMER register provides software the capability to reset the available 16/32-bit timer modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the timer modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRTIMER register. While the SRTIMER bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRTIMER bit. There may be latency from the clearing of the SRTIMER bit to when the peripheral is ready for use. Software can check the corresponding PRTIMER bit to be sure. Important: This register should be used to reset the timer modules. To support legacy software, the SRCR1 register is available. Setting a bit in the SRCR1 register also resets the corresponding module. Any bits that are changed by writing to the SRCR1 register can be read back correctly when reading the SRCR1 register. Software must use this register to reset modules that are not present in the legacy registers. If software uses this register to reset a legacy peripheral (such as Timer 1), the write causes proper operation, but the value of that bit is not reflected in the SRCR1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
16/32-Bit General-Purpose Timer Software Reset (SRTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 R5 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 R4 R/W 0 RO 0 3 R3 R/W 0 RO 0 2 R2 R/W 0 RO 0 1 R1 R/W 0 RO 0 0 R0 R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Software Reset Value Description 1 0 16/32-bit general-purpose timer module 5 is reset. 16/32-bit general-purpose timer module 5 is not reset.
R5
R/W
289
System Control
Bit/Field 4
Name R4
Type R/W
Reset 0
Description 16/32-Bit General-Purpose Timer 4 Software Reset Value Description 1 0 16/32-bit general-purpose timer module 4 is reset. 16/32-bit general-purpose timer module 4 is not reset.
R3
R/W
16/32-Bit General-Purpose Timer 3 Software Reset Value Description 1 0 16/32-bit general-purpose timer module 3 is reset. 16/32-bit general-purpose timer module 3 is not reset.
R2
R/W
R1
R/W
R0
R/W
April 25, 2012
Register 37: General-Purpose Input/Output Software Reset (SRGPIO), offset 0x508

The SRGPIO register provides software the capability to reset the available GPIO modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the GPIO modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRGPIO register. While the SRGPIO bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRGPIO bit. There may be latency from the clearing of the SRGPIO bit to when the peripheral is ready for use. Software can check the corresponding PRGPIO bit to be sure. Important: This register should be used to reset the GPIO modules. To support legacy software, the SRCR2 register is available. Setting a bit in the SRCR2 register also resets the corresponding module. Any bits that are changed by writing to the SRCR2 register can be read back correctly when reading the SRCR2 register. Software must use this register to reset modules that are not present in the legacy registers. If software uses this register to reset a legacy peripheral (such as GPIO A), the write causes proper operation, but the value of that bit is not reflected in the SRCR2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
General-Purpose Input/Output Software Reset (SRGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Software Reset Value Description 1 0 GPIO Port F is reset. GPIO Port F is not reset.
R5
R/W
291
System Control
Bit/Field 4
Name R4
Type R/W
Reset 0
Description GPIO Port E Software Reset Value Description 1 0 GPIO Port E is reset. GPIO Port E is not reset.
R3
R/W
GPIO Port D Software Reset Value Description 1 0 GPIO Port D is reset. GPIO Port D is not reset.
R2
R/W
GPIO Port C Software Reset Value Description 1 0 GPIO Port C is reset. GPIO Port C is not reset.
R1
R/W
GPIO Port B Software Reset Value Description 1 0 GPIO Port B is reset. GPIO Port B is not reset.
R0
R/W
GPIO Port A Software Reset Value Description 1 0 GPIO Port A is reset. GPIO Port A is not reset.
April 25, 2012
Register 38: Micro Direct Memory Access Software Reset (SRDMA), offset 0x50C
The SRDMA register provides software the capability to reset the available DMA module. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the DMA module and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRDMA register. While the SRDMA bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRDMA bit. There may be latency from the clearing of the SRDMA bit to when the peripheral is ready for use. Software can check the corresponding PRDMA bit to be sure. Important: This register should be used to reset the DMA module. To support legacy software, the SRCR2 register is available. Setting the UDMA bit in the SRCR2 register also resets the DMA module. If the UDMA bit is set by writing to the SRCR2 register, it can be read back correctly when reading the SRCR2 register. If software uses this register to reset the DMA module, the write causes proper operation, but the value of the UDMA bit is not reflected in the SRCR2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Micro Direct Memory Access Software Reset (SRDMA)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 R0 R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Software Reset Value Description 1 0 DMA module is reset. DMA module is not reset.
R0
R/W
293
System Control
Register 39: Hibernation Software Reset (SRHIB), offset 0x514

The SRHIB register provides software the capability to reset the available Hibernation module. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the Hibernation module and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRHIB register. While the SRHIB bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRHIB bit. There may be latency from the clearing of the SRHIB bit to when the peripheral is ready for use. Software can check the corresponding PRHIB bit to be sure. Important: This register should be used to reset the Hibernation module. To support legacy software, the SRCR0 register is available. Setting the HIB bit in the SRCR0 register also resets the Hibernation module. If the HIB bit is set by writing to the SRCR0 register, it can be read back correctly when reading the SRCR0 register. If software uses this register to reset the Hibernation module, the write causes proper operation, but the value of the HIB bit is not reflected in the SRCR0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Hibernation Software Reset (SRHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Software Reset Value Description 1 0 Hibernation module is reset. Hibernation module is not reset.
R0
R/W
April 25, 2012
Register 40: Universal Asynchronous Receiver/Transmitter Software Reset (SRUART), offset 0x518
The SRUART register provides software the capability to reset the available UART modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the UART modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRUART register. While the SRUART bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRUART bit. There may be latency from the clearing of the SRUART bit to when the peripheral is ready for use. Software can check the corresponding PRUART bit to be sure. Important: This register should be used to reset the UART modules. To support legacy software, the SRCR1 register is available. Setting a bit in the SRCR1 register also resets the corresponding module. Any bits that are changed by writing to the SRCR1 register can be read back correctly when reading the SRCR1 register. Software must use this register to reset modules that are not present in the legacy registers. If software uses this register to reset a legacy peripheral (such as UART0), the write causes proper operation, but the value of that bit is not reflected in the SRCR1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Asynchronous Receiver/Transmitter Software Reset (SRUART)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 R7 RO 0 RO 0 RO 0 R/W 0 RO 0 6 R6 R/W 0 RO 0 5 R5 R/W 0 RO 0 4 R4 R/W 0 RO 0 3 R3 R/W 0 RO 0 2 R2 R/W 0 RO 0 1 R1 R/W 0 RO 0 0 R0 R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Software Reset Value Description 1 0 UART module 7 is reset. UART module 7 is not reset.
R7
R/W
295
System Control
Bit/Field 6
Name R6
Type R/W
Reset 0
Description UART Module 6 Software Reset Value Description 1 0 UART module 6 is reset. UART module 6 is not reset.
R5
R/W
UART Module 5 Software Reset Value Description 1 0 UART module 5 is reset. UART module 5 is not reset.
R4
R/W
R3
R/W
R2
R/W
R1
R/W
R0
R/W
April 25, 2012
Register 41: Synchronous Serial Interface Software Reset (SRSSI), offset 0x51C
The SRSSI register provides software the capability to reset the available SSI modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the SSI modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRSSI register. While the SRSSI bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRSSI bit. There may be latency from the clearing of the SRSSI bit to when the peripheral is ready for use. Software can check the corresponding PRSSI bit to be sure. Important: This register should be used to reset the SSI modules. To support legacy software, the SRCR1 register is available. Setting a bit in the SRCR1 register also resets the corresponding module. Any bits that are changed by writing to the SRCR1 register can be read back correctly when reading the SRCR1 register. Software must use this register to reset modules that are not present in the legacy registers. If software uses this register to reset a legacy peripheral (such as SSI0), the write causes proper operation, but the value of that bit is not reflected in the SRCR1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Synchronous Serial Interface Software Reset (SRSSI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 R3 R/W 0 RO 0 2 R2 R/W 0 RO 0 1 R1 R/W 0 RO 0 0 R0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Software Reset Value Description 1 0 SSI module 3 is reset. SSI module 3 is not reset.
R3
R/W
297
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description SSI Module 2 Software Reset Value Description 1 0 SSI module 2 is reset. SSI module 2 is not reset.
R1
R/W
SSI Module 1 Software Reset Value Description 1 0 SSI module 1 is reset. SSI module 1 is not reset.
R0
R/W
SSI Module 0 Software Reset Value Description 1 0 SSI module 0 is reset. SSI module 0 is not reset.
April 25, 2012
Register 42: Inter-Integrated Circuit Software Reset (SRI2C), offset 0x520

The SRI2C register provides software the capability to reset the available I2C modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the I2C modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRI2C register. While the SRI2C bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRI2C bit. There may be latency from the clearing of the SRI2C bit to when the peripheral is ready for use. Software can check the corresponding PRI2C bit to be sure. Important: This register should be used to reset the I2C modules. To support legacy software, the SRCR1 register is available. Setting a bit in the SRCR1 register also resets the corresponding module. Any bits that are changed by writing to the SRCR1 register can be read back correctly when reading the SRCR1 register. Software must use this register to reset modules that are not present in the legacy registers. If software uses this register to reset a legacy peripheral (such as I2C0), the write causes proper operation, but the value of that bit is not reflected in the SRCR1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Inter-Integrated Circuit Software Reset (SRI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Software Reset Value Description 1 0 I2C module 3 is reset. I2C module 3 is not reset.
R3
R/W
299
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description I2C Module 2 Software Reset Value Description 1 0 I2C module 2 is reset. I2C module 2 is not reset.
R1
R/W
I2C Module 1 Software Reset Value Description 1 0 I2C module 1 is reset. I2C module 1 is not reset.
R0
R/W
I2C Module 0 Software Reset Value Description 1 0 I2C module 0 is reset. I2C module 0 is not reset.
April 25, 2012
Register 43: Universal Serial Bus Software Reset (SRUSB), offset 0x528
The SRUSB register provides software the capability to reset the available USB module. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the USB module and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRUSB register. While the SRUSB bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRUSB bit. There may be latency from the clearing of the SRUSB bit to when the peripheral is ready for use. Software can check the corresponding PRUSB bit to be sure. Important: This register should be used to reset the USB module. To support legacy software, the SRCR2 register is available. Setting the USB0 bit in the SRCR2 register also resets the USB module. If the USB0 bit is set by writing to the SRCR2 register, it can be read back correctly when reading the SRCR2 register. If software uses this register to reset the USB module, the write causes proper operation, but the value of the USB0 bit is not reflected in the SRCR2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Serial Bus Software Reset (SRUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Software Reset Value Description 1 0 USB module is reset. USB module is not reset.
R0
R/W
301
System Control
Register 44: Controller Area Network Software Reset (SRCAN), offset 0x534
The SRCAN register provides software the capability to reset the available CAN modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the CAN modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRCAN register. While the SRCAN bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRCAN bit. There may be latency from the clearing of the SRCAN bit to when the peripheral is ready for use. Software can check the corresponding PRCAN bit to be sure. Important: This register should be used to reset the CAN modules. To support legacy software, the SRCR0 register is available. Setting a bit in the SRCR0 register also resets the corresponding module. Any bits that are changed by writing to the SRCR0 register can be read back correctly when reading the SRCR0 register. If software uses this register to reset a legacy peripheral (such as CAN0), the write causes proper operation, but the value of that bit is not reflected in the SRCR0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Controller Area Network Software Reset (SRCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Software Reset Value Description 1 0 CAN module 0 is reset. CAN module 0 is not reset.
R0
R/W
April 25, 2012
Register 45: Analog-to-Digital Converter Software Reset (SRADC), offset 0x538

The SRADC register provides software the capability to reset the available ADC modules. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the ADC modules and has the same bit polarity as the corresponding SRCRn bits. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRADC register. While the SRADC bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRADC bit. There may be latency from the clearing of the SRADC bit to when the peripheral is ready for use. Software can check the corresponding PRADC bit to be sure. Important: This register should be used to reset the ADC modules. To support legacy software, the SRCR0 register is available. Setting a bit in the SRCR0 register also resets the corresponding module. Any bits that are changed by writing to the SRCR0 register can be read back correctly when reading the SRCR0 register. If software uses this register to reset a legacy peripheral (such as ADC0), the write causes proper operation, but the value of that bit is not reflected in the SRCR0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog-to-Digital Converter Software Reset (SRADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Software Reset Value Description 1 0 ADC module 1 is reset. ADC module 1 is not reset.
R1
R/W
303
System Control
Bit/Field 0
Name R0
Type R/W
Reset 0
Description ADC Module 0 Software Reset Value Description 1 0 ADC module 0 is reset. ADC module 0 is not reset.
April 25, 2012
Register 46: Analog Comparator Software Reset (SRACMP), offset 0x53C

The SRACMP register provides software the capability to reset the available analog comparator module. This register provides the same capability as the legacy Software Reset Control n SRCRn registers specifically for the analog comparator module and has the same bit polarity as the corresponding SRCRn bits. A block is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRACMP register. While the SRACMP bit is 1, the module is held in reset. 2. Software completes the reset process by clearing the SRACMP bit. There may be latency from the clearing of the SRACMP bit to when the module is ready for use. Software can check the corresponding PRACMP bit to be sure. Important: This register should be used to reset the analog comparator module. To support legacy software, the SRCR1 register is available. Setting any of the COMPn bits in the SRCR0 register also resets the analog comparator module. If any of the COMPn bits are set by writing to the SRCR1 register, it can be read back correctly when reading the SRCR0 register. If software uses this register to reset the analog comparator module, the write causes proper operation, but the value of R0 is not reflected by the COMPn bits in the SRCR1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog Comparator Software Reset (SRACMP)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Software Reset Value Description 1 0 Analog comparator module is reset. Analog comparator module is not reset.
R0
R/W
305
System Control
Register 47: EEPROM Software Reset (SREEPROM), offset 0x558

The SREEPROM register provides software the capability to reset the available EEPROM module. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SREEPROM register. While the SREEPROM bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SREEPROM bit. There may be latency from the clearing of the SREEPROM bit to when the peripheral is ready for use. Software can check the corresponding PREEPROM bit to be sure.
EEPROM Software Reset (SREEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Software Reset Value Description 1 0 EEPROM module is reset. EEPROM module is not reset.
R0
R/W
April 25, 2012
Register 48: 32/64-Bit Wide General-Purpose Timer Software Reset (SRWTIMER), offset 0x55C
The SRWTIMER register provides software the capability to reset the available 32/64-bit wide timer modules. A peripheral is reset by software using a simple two-step process: 1. Software sets a bit (or bits) in the SRWTIMER register. While the SRWTIMER bit is 1, the peripheral is held in reset. 2. Software completes the reset process by clearing the SRWTIMER bit. There may be latency from the clearing of the SRWTIMER bit to when the peripheral is ready for use. Software can check the corresponding PRWTIMER bit to be sure.
32/64-Bit Wide General-Purpose Timer Software Reset (SRWTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Software Reset Value Description 1 0 32/64-bit wide general-purpose timer module 5 is reset. 32/64-bit wide general-purpose timer module 5 is not reset.
R5
R/W
R4
R/W
32/64-Bit Wide General-Purpose Timer 4 Software Reset Value Description 1 0 32/64-bit wide general-purpose timer module 4 is reset. 32/64-bit wide general-purpose timer module 4 is not reset.
R3
R/W
307
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description 32/64-Bit Wide General-Purpose Timer 2 Software Reset Value Description 1 0 32/64-bit wide general-purpose timer module 2 is reset. 32/64-bit wide general-purpose timer module 2 is not reset.
R1
R/W
R0
R/W
April 25, 2012
Register 49: Watchdog Timer Run Mode Clock Gating Control (RCGCWD), offset 0x600
The RCGCWD register provides software the capability to enable and disable watchdog modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the watchdog modules. To support legacy software, the RCGC0 register is available. A write to the RCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC0 register can be read back correctly with a read of the RCGC0 register. If software uses this register to write a legacy peripheral (such as Watchdog 0), the write causes proper operation, but the value of that bit is not reflected in the RCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Watchdog Timer Run Mode Clock Gating Control (RCGCWD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 1 in Run mode. Watchdog module 1 is disabled.
R1
R/W
R0
R/W
Watchdog Timer 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 0 in Run mode. Watchdog module 0 is disabled.
309
System Control
Register 50: 16/32-Bit General-Purpose Timer Run Mode Clock Gating Control (RCGCTIMER), offset 0x604
The RCGCTIMER register provides software the capability to enable and disable 16/32-bit timer modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the timer modules. To support legacy software, the RCGC1 register is available. A write to the RCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC1 register can be read back correctly with a read of the RCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in the RCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
16/32-Bit General-Purpose Timer Run Mode Clock Gating Control (RCGCTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 5 in Run mode. 16/32-bit general-purpose timer module 5 is disabled.
R5
R/W
April 25, 2012
Bit/Field 4
Name R4
Type R/W
Reset 0
Description 16/32-Bit General-Purpose Timer 4 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 4 in Run mode. 16/32-bit general-purpose timer module 4 is disabled.
R3
R/W
16/32-Bit General-Purpose Timer 3 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 3 in Run mode. 16/32-bit general-purpose timer module 3 is disabled.
R2
R/W
R1
R/W
R0
R/W
311
System Control
Register 51: General-Purpose Input/Output Run Mode Clock Gating Control (RCGCGPIO), offset 0x608
The RCGCGPIO register provides software the capability to enable and disable GPIO modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the GPIO modules. To support legacy software, the RCGC2 register is available. A write to the RCGC2 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC2 register can be read back correctly with a read of the RCGC2 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as GPIO A), the write causes proper operation, but the value of that bit is not reflected in the RCGC2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
General-Purpose Input/Output Run Mode Clock Gating Control (RCGCGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port F in Run mode. GPIO Port F is disabled.
R5
R/W
R4
R/W
GPIO Port E Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port E in Run mode. GPIO Port E is disabled.
April 25, 2012
Bit/Field 3
Name R3
Type R/W
Reset 0
Description GPIO Port D Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port D in Run mode. GPIO Port D is disabled.
R2
R/W
GPIO Port C Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port C in Run mode. GPIO Port C is disabled.
R1
R/W
GPIO Port B Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port B in Run mode. GPIO Port B is disabled.
R0
R/W
GPIO Port A Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port A in Run mode. GPIO Port A is disabled.
313
System Control
Register 52: Micro Direct Memory Access Run Mode Clock Gating Control (RCGCDMA), offset 0x60C
The RCGCDMA register provides software the capability to enable and disable the DMA module in Run mode. When enabled, the module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the DMA module. To support legacy software, the RCGC2 register is available. A write to the UDMA bit in the RCGC2 register also writes the R0 bit in this register. If the UDMA bit is changed by writing to the RCGC2 register, it can be read back correctly with a read of the RCGC2 register. If software uses this register to control the clock for the DMA module, the write causes proper operation, but the UDMA bit in the RCGC2 register does not reflect the value of the R0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Micro Direct Memory Access Run Mode Clock Gating Control (RCGCDMA)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the DMA module in Run mode. DMA module is disabled.
R0
R/W
April 25, 2012
Register 53: Hibernation Run Mode Clock Gating Control (RCGCHIB), offset 0x614
The RCGCHIB register provides software the capability to enable and disable the Hibernation module in Run mode. When enabled, the module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the Hibernation module. To support legacy software, the RCGC0 register is available. A write to the HIB bit in the RCGC0 register also writes the R0 bit in this register. If the HIB bit is changed by writing to the RCGC0 register, it can be read back correctly with a read of the RCGC0 register. If software uses this register to control the clock for the Hibernation module, the write causes proper operation, but the HIB bit in the RCGC0 register does not reflect the value of the R0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Hibernation Run Mode Clock Gating Control (RCGCHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the Hibernation module in Run mode. Hibernation module is disabled.
R0
R/W
315
System Control
Register 54: Universal Asynchronous Receiver/Transmitter Run Mode Clock Gating Control (RCGCUART), offset 0x618
The RCGCUART register provides software the capability to enable and disable the UART modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the UART modules. To support legacy software, the RCGC1 register is available. A write to the RCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC1 register can be read back correctly with a read of the RCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as UART0), the write causes proper operation, but the value of that bit is not reflected in the RCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Asynchronous Receiver/Transmitter Run Mode Clock Gating Control (RCGCUART)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 7 in Run mode. UART module 7 is disabled.
R7
R/W
R6
R/W
UART Module 6 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 6 in Run mode. UART module 6 is disabled.
April 25, 2012
Bit/Field 5
Name R5
Type R/W
Reset 0
Description UART Module 5 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 5 in Run mode. UART module 5 is disabled.
R4
R/W
R3
R/W
R2
R/W
R1
R/W
R0
R/W
317
System Control
Register 55: Synchronous Serial Interface Run Mode Clock Gating Control (RCGCSSI), offset 0x61C
The RCGCSSI register provides software the capability to enable and disable the SSI modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the SSI modules. To support legacy software, the RCGC1 register is available. A write to the RCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC1 register can be read back correctly with a read of the RCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as SSI0), the write causes proper operation, but the value of that bit is not reflected in the RCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Synchronous Serial Interface Run Mode Clock Gating Control (RCGCSSI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 3 in Run mode. SSI module 3 is disabled.
R3
R/W
R2
R/W
SSI Module 2 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 2 in Run mode. SSI module 2 is disabled.
April 25, 2012
Bit/Field 1
Name R1
Type R/W
Reset 0
Description SSI Module 1 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 1 in Run mode. SSI module 1 is disabled.
R0
R/W
SSI Module 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 0 in Run mode. SSI module 0 is disabled.
319
System Control
Register 56: Inter-Integrated Circuit Run Mode Clock Gating Control (RCGCI2C), offset 0x620
The RCGCI2C register provides software the capability to enable and disable the I2C modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the I2C modules. To support legacy software, the RCGC1 register is available. A write to the RCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC1 register can be read back correctly with a read of the RCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as I2C0), the write causes proper operation, but the value of that bit is not reflected in the RCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Inter-Integrated Circuit Run Mode Clock Gating Control (RCGCI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 3 in Run mode. I2C module 3 is disabled.
R3
R/W
R2
R/W
I2C Module 2 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 2 in Run mode. I2C module 2 is disabled.
April 25, 2012
Bit/Field 1
Name R1
Type R/W
Reset 0
Description I2C Module 1 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 1 in Run mode. I2C module 1 is disabled.
R0
R/W
I2C Module 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 0 in Run mode. I2C module 0 is disabled.
321
System Control
Register 57: Universal Serial Bus Run Mode Clock Gating Control (RCGCUSB), offset 0x628
The RCGCUSB register provides software the capability to enable and disable the USB module in Run mode. When enabled, the module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the USB module. To support legacy software, the RCGC2 register is available. A write to the USB0 bit in the RCGC2 register also writes the R0 bit in this register. If the USB0 bit is changed by writing to the RCGC2 register, it can be read back correctly with a read of the RCGC2 register. If software uses this register to control the clock for the USB module, the write causes proper operation, but the USB0 bit in the RCGC2 register does not reflect the value of the R0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Serial Bus Run Mode Clock Gating Control (RCGCUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the USB module in Run mode. USB module is disabled.
R0
R/W
April 25, 2012
Register 58: Controller Area Network Run Mode Clock Gating Control (RCGCCAN), offset 0x634
The RCGCCAN register provides software the capability to enable and disable the CAN modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the CAN modules. To support legacy software, the RCGC0 register is available. A write to the RCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC0 register can be read back correctly with a read of the RCGC0 register. If software uses this register to write a legacy peripheral (such as CAN0), the write causes proper operation, but the value of that bit is not reflected in the RCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Controller Area Network Run Mode Clock Gating Control (RCGCCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to CAN module 0 in Run mode. CAN module 0 is disabled.
R0
R/W
323
System Control
Register 59: Analog-to-Digital Converter Run Mode Clock Gating Control (RCGCADC), offset 0x638
The RCGCADC register provides software the capability to enable and disable the ADC modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the ADC modules. To support legacy software, the RCGC0 register is available. A write to the RCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the RCGC0 register can be read back correctly with a read of the RCGC0 register. If software uses this register to write a legacy peripheral (such as ADC0), the write causes proper operation, but the value of that bit is not reflected in the RCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog-to-Digital Converter Run Mode Clock Gating Control (RCGCADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 1 in Run mode. ADC module 1 is disabled.
R1
R/W
R0
R/W
ADC Module 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 0 in Run mode. ADC module 0 is disabled.
April 25, 2012
Register 60: Analog Comparator Run Mode Clock Gating Control (RCGCACMP), offset 0x63C
The RCGCACMP register provides software the capability to enable and disable the analog comparator module in Run mode. When enabled, the module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding RCGCn bits. Important: This register should be used to control the clocking for the analog comparator module. To support legacy software, the RCGC1 register is available. Setting any of the COMPn bits in the RCGC1 register also sets the R0 bit in this register. If any of the COMPn bits are set by writing to the RCGC1 register, it can be read back correctly when reading the RCGC1 register. If software uses this register to change the clocking for the analog comparator module, the write causes proper operation, but the value R0 is not reflected by the COMPn bits in the RCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog Comparator Run Mode Clock Gating Control (RCGCACMP)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the analog comparator module in Run mode. Analog comparator module is disabled.
R0
R/W
325
System Control
Register 61: EEPROM Run Mode Clock Gating Control (RCGCEEPROM), offset 0x658
The RCGCEEPROM register provides software the capability to enable and disable the EEPROM module in Run mode. When enabled, the module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault.
EEPROM Run Mode Clock Gating Control (RCGCEEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the EEPROM module in Run mode. EEPROM module is disabled.
R0
R/W
April 25, 2012
Register 62: 32/64-Bit Wide General-Purpose Timer Run Mode Clock Gating Control (RCGCWTIMER), offset 0x65C
The RCGCWTIMER register provides software the capability to enable and disable 3264-bit timer modules in Run mode. When enabled, a module is provided a clock and accesses to module registers are allowed. When disabled, the clock is disabled to save power and accesses to module registers generate a bus fault. This register provides the same capability as the legacy Run Mode Clock Gating Control Register n RCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding RCGCn bits.
32/64-Bit Wide General-Purpose Timer Run Mode Clock Gating Control (RCGCWTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 5 in Run mode. 32/64-bit wide general-purpose timer module 5 is disabled.
R5
R/W
R4
R/W
32/64-Bit Wide General-Purpose Timer 4 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 4 in Run mode. 32/64-bit wide general-purpose timer module 4 is disabled.
R3
R/W
327
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description 32/64-Bit Wide General-Purpose Timer 2 Run Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 2 in Run mode. 32/64-bit wide general-purpose timer module 2 is disabled.
R1
R/W
R0
R/W
April 25, 2012
Register 63: Watchdog Timer Sleep Mode Clock Gating Control (SCGCWD), offset 0x700
The SCGCWD register provides software the capability to enable and disable watchdog modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the watchdog modules. To support legacy software, the SCGC0 register is available. A write to the SCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC0 register can be read back correctly with a read of the SCGC0 register. If software uses this register to write a legacy peripheral (such as Watchdog 0), the write causes proper operation, but the value of that bit is not reflected in the SCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Watchdog Timer Sleep Mode Clock Gating Control (SCGCWD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 1 in sleep mode. Watchdog module 1 is disabled.
S1
R/W
S0
R/W
Watchdog Timer 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 0 in sleep mode. Watchdog module 0 is disabled.
329
System Control
Register 64: 16/32-Bit General-Purpose Timer Sleep Mode Clock Gating Control (SCGCTIMER), offset 0x704
The SCGCTIMER register provides software the capability to enable and disable 16/32-bit timer modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the timer modules. To support legacy software, the SCGC1 register is available. A write to the SCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC1 register can be read back correctly with a read of the SCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in the SCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
16/32-Bit General-Purpose Timer Sleep Mode Clock Gating Control (SCGCTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 S5 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 S4 R/W 0 RO 0 3 S3 R/W 0 RO 0 2 S2 R/W 0 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 5 in sleep mode. 16/32-bit general-purpose timer module 5 is disabled.
S5
R/W
S4
R/W
16/32-Bit General-Purpose Timer 4 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 4 in sleep mode. 16/32-bit general-purpose timer module 4 is disabled.
April 25, 2012
Bit/Field 3
Name S3
Type R/W
Reset 0
Description 16/32-Bit General-Purpose Timer 3 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 3 in sleep mode. 16/32-bit general-purpose timer module 3 is disabled.
S2
R/W
S1
R/W
S0
R/W
331
System Control
Register 65: General-Purpose Input/Output Sleep Mode Clock Gating Control (SCGCGPIO), offset 0x708
The SCGCGPIO register provides software the capability to enable and disable GPIO modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the GPIO modules. To support legacy software, the SCGC2 register is available. A write to the SCGC2 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC2 register can be read back correctly with a read of the SCGC2 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as GPIO A), the write causes proper operation, but the value of that bit is not reflected in the SCGC2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
General-Purpose Input/Output Sleep Mode Clock Gating Control (SCGCGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port F in sleep mode. GPIO Port F is disabled.
S5
R/W
S4
R/W
GPIO Port E Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port E in sleep mode. GPIO Port E is disabled.
April 25, 2012
Bit/Field 3
Name S3
Type R/W
Reset 0
Description GPIO Port D Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port D in sleep mode. GPIO Port D is disabled.
S2
R/W
GPIO Port C Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port C in sleep mode. GPIO Port C is disabled.
S1
R/W
GPIO Port B Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port B in sleep mode. GPIO Port B is disabled.
S0
R/W
GPIO Port A Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port A in sleep mode. GPIO Port A is disabled.
333
System Control
Register 66: Micro Direct Memory Access Sleep Mode Clock Gating Control (SCGCDMA), offset 0x70C
The SCGCDMA register provides software the capability to enable and disable the DMA module in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the DMA module. To support legacy software, the SCGC2 register is available. A write to the UDMA bit in the SCGC2 register also writes the S0 bit in this register. If the UDMA bit is changed by writing to the SCGC2 register, it can be read back correctly with a read of the SCGC2 register. If software uses this register to control the clock for the DMA module, the write causes proper operation, but the UDMA bit in the SCGC2 register does not reflect the value of the S0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Micro Direct Memory Access Sleep Mode Clock Gating Control (SCGCDMA)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 S0 R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the DMA module in sleep mode. DMA module is disabled.
S0
R/W
April 25, 2012
Register 67: Hibernation Sleep Mode Clock Gating Control (SCGCHIB), offset 0x714
The SCGCHIB register provides software the capability to enable and disable the Hibernation module in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the Hibernation module. To support legacy software, the SCGC0 register is available. A write to the HIB bit in the SCGC0 register also writes the S0 bit in this register. If the HIB bit is changed by writing to the SCGC0 register, it can be read back correctly with a read of the SCGC0 register. If software uses this register to control the clock for the Hibernation module, the write causes proper operation, but the HIB bit in the SCGC0 register does not reflect the value of the S0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Hibernation Sleep Mode Clock Gating Control (SCGCHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the Hibernation module in sleep mode. Hibernation module is disabled.
S0
R/W
335
System Control
Register 68: Universal Asynchronous Receiver/Transmitter Sleep Mode Clock Gating Control (SCGCUART), offset 0x718
The SCGCUART register provides software the capability to enable and disable the UART modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the UART modules. To support legacy software, the SCGC1 register is available. A write to the SCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC1 register can be read back correctly with a read of the SCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as UART0), the write causes proper operation, but the value of that bit is not reflected in the SCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Asynchronous Receiver/Transmitter Sleep Mode Clock Gating Control (SCGCUART)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 S7 RO 0 RO 0 RO 0 R/W 0 RO 0 6 S6 R/W 0 RO 0 5 S5 R/W 0 RO 0 4 S4 R/W 0 RO 0 3 S3 R/W 0 RO 0 2 S2 R/W 0 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 7 in sleep mode. UART module 7 is disabled.
S7
R/W
S6
R/W
UART Module 6 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 6 in sleep mode. UART module 6 is disabled.
April 25, 2012
Bit/Field 5
Name S5
Type R/W
Reset 0
Description UART Module 5 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 5 in sleep mode. UART module 5 is disabled.
S4
R/W
S3
R/W
S2
R/W
S1
R/W
S0
R/W
337
System Control
Register 69: Synchronous Serial Interface Sleep Mode Clock Gating Control (SCGCSSI), offset 0x71C
The SCGCSSI register provides software the capability to enable and disable the SSI modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the SSI modules. To support legacy software, the SCGC1 register is available. A write to the SCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC1 register can be read back correctly with a read of the SCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as SSI0), the write causes proper operation, but the value of that bit is not reflected in the SCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Synchronous Serial Interface Sleep Mode Clock Gating Control (SCGCSSI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 S3 R/W 0 RO 0 2 S2 R/W 0 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 3 in sleep mode. SSI module 3 is disabled.
S3
R/W
S2
R/W
SSI Module 2 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 2 in sleep mode. SSI module 2 is disabled.
April 25, 2012
Bit/Field 1
Name S1
Type R/W
Reset 0
Description SSI Module 1 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 1 in sleep mode. SSI module 1 is disabled.
S0
R/W
SSI Module 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 0 in sleep mode. SSI module 0 is disabled.
339
System Control
Register 70: Inter-Integrated Circuit Sleep Mode Clock Gating Control (SCGCI2C), offset 0x720
The SCGCI2C register provides software the capability to enable and disable the I2C modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the I2C modules. To support legacy software, the SCGC1 register is available. A write to the SCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC1 register can be read back correctly with a read of the SCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as I2C0), the write causes proper operation, but the value of that bit is not reflected in the SCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Inter-Integrated Circuit Sleep Mode Clock Gating Control (SCGCI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 S3 R/W 0 RO 0 2 S2 R/W 0 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 3 in sleep mode. I2C module 3 is disabled.
S3
R/W
S2
R/W
I2C Module 2 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 2 in sleep mode. I2C module 2 is disabled.
April 25, 2012
Bit/Field 1
Name S1
Type R/W
Reset 0
Description I2C Module 1 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 1 in sleep mode. I2C module 1 is disabled.
S0
R/W
I2C Module 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 0 in sleep mode. I2C module 0 is disabled.
341
System Control
Register 71: Universal Serial Bus Sleep Mode Clock Gating Control (SCGCUSB), offset 0x728
The SCGCUSB register provides software the capability to enable and disable the USB module in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the USB module. To support legacy software, the SCGC2 register is available. A write to the USB0 bit in the SCGC2 register also writes the S0 bit in this register. If the USB0 bit is changed by writing to the SCGC2 register, it can be read back correctly with a read of the SCGC2 register. If software uses this register to control the clock for the USB module, the write causes proper operation, but the USB0 bit in the SCGC2 register does not reflect the value of the S0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Serial Bus Sleep Mode Clock Gating Control (SCGCUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the USB module in sleep mode. USB module is disabled.
S0
R/W
April 25, 2012
Register 72: Controller Area Network Sleep Mode Clock Gating Control (SCGCCAN), offset 0x734
The SCGCCAN register provides software the capability to enable and disable the CAN modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the CAN modules. To support legacy software, the SCGC0 register is available. A write to the SCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC0 register can be read back correctly with a read of the SCGC0 register. If software uses this register to write a legacy peripheral (such as CAN0), the write causes proper operation, but the value of that bit is not reflected in the SCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Controller Area Network Sleep Mode Clock Gating Control (SCGCCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to CAN module 0 in sleep mode. CAN module 0 is disabled.
S0
R/W
343
System Control
Register 73: Analog-to-Digital Converter Sleep Mode Clock Gating Control (SCGCADC), offset 0x738
The SCGCADC register provides software the capability to enable and disable the ADC modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the ADC modules. To support legacy software, the SCGC0 register is available. A write to the SCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the SCGC0 register can be read back correctly with a read of the SCGC0 register. If software uses this register to write a legacy peripheral (such as ADC0), the write causes proper operation, but the value of that bit is not reflected in the SCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog-to-Digital Converter Sleep Mode Clock Gating Control (SCGCADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 S1 R/W 0 RO 0 0 S0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 1 in sleep mode. ADC module 1 is disabled.
S1
R/W
S0
R/W
ADC Module 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 0 in sleep mode. ADC module 0 is disabled.
April 25, 2012
Register 74: Analog Comparator Sleep Mode Clock Gating Control (SCGCACMP), offset 0x73C
The SCGCACMP register provides software the capability to enable and disable the analog comparator module in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding SCGCn bits. Important: This register should be used to control the clocking for the analog comparator module. To support legacy software, the SCGC1 register is available. Setting any of the COMPn bits in the SCGC1 register also sets the S0 bit in this register. If any of the COMPn bits are set by writing to the SCGC1 register, it can be read back correctly when reading the SCGC1 register. If software uses this register to change the clocking for the analog comparator module, the write causes proper operation, but the value S0 is not reflected by the COMPn bits in the SCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog Comparator Sleep Mode Clock Gating Control (SCGCACMP)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the analog comparator module in sleep mode. Analog comparator module is disabled.
S0
R/W
345
System Control
Register 75: EEPROM Sleep Mode Clock Gating Control (SCGCEEPROM), offset 0x758
The SCGCEEPROM register provides software the capability to enable and disable the EEPROM module in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power.
EEPROM Sleep Mode Clock Gating Control (SCGCEEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the EEPROM module in sleep mode. EEPROM module is disabled.
S0
R/W
April 25, 2012
Register 76: 32/64-Bit Wide General-Purpose Timer Sleep Mode Clock Gating Control (SCGCWTIMER), offset 0x75C
The SCGCWTIMER register provides software the capability to enable and disable 3264-bit timer modules in sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Sleep Mode Clock Gating Control Register n SCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding SCGCn bits.
32/64-Bit Wide General-Purpose Timer Sleep Mode Clock Gating Control (SCGCWTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 5 in sleep mode. 32/64-bit wide general-purpose timer module 5 is disabled.
S5
R/W
S4
R/W
32/64-Bit Wide General-Purpose Timer 4 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 4 in sleep mode. 32/64-bit wide general-purpose timer module 4 is disabled.
S3
R/W
347
System Control
Bit/Field 2
Name S2
Type R/W
Reset 0
Description 32/64-Bit Wide General-Purpose Timer 2 Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 2 in sleep mode. 32/64-bit wide general-purpose timer module 2 is disabled.
S1
R/W
S0
R/W
April 25, 2012
Register 77: Watchdog Timer Deep-Sleep Mode Clock Gating Control (DCGCWD), offset 0x800
The DCGCWD register provides software the capability to enable and disable watchdog modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the watchdog modules. To support legacy software, the DCGC0 register is available. A write to the DCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC0 register can be read back correctly with a read of the DCGC0 register. If software uses this register to write a legacy peripheral (such as Watchdog 0), the write causes proper operation, but the value of that bit is not reflected in the DCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Watchdog Timer Deep-Sleep Mode Clock Gating Control (DCGCWD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 1 in deep-sleep mode. Watchdog module 1 is disabled.
D1
R/W
D0
R/W
Watchdog Timer 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to Watchdog module 0 in deep-sleep mode. Watchdog module 0 is disabled.
349
System Control
Register 78: 16/32-Bit General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCTIMER), offset 0x804
The DCGCTIMER register provides software the capability to enable and disable 16/32-bit timer modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the timer modules. To support legacy software, the DCGC1 register is available. A write to the DCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC1 register can be read back correctly with a read of the DCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in the DCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
16/32-Bit General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 D5 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 D4 R/W 0 RO 0 3 D3 R/W 0 RO 0 2 D2 R/W 0 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 5 in deep-sleep mode. 16/32-bit general-purpose timer module 5 is disabled.
D5
R/W
April 25, 2012
Bit/Field 4
Name D4
Type R/W
Reset 0
Description 16/32-Bit General-Purpose Timer 4 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 4 in deep-sleep mode. 16/32-bit general-purpose timer module 4 is disabled.
D3
R/W
16/32-Bit General-Purpose Timer 3 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 16/32-bit general-purpose timer module 3 in deep-sleep mode. 16/32-bit general-purpose timer module 3 is disabled.
D2
R/W
D1
R/W
D0
R/W
351
System Control
Register 79: General-Purpose Input/Output Deep-Sleep Mode Clock Gating Control (DCGCGPIO), offset 0x808
The DCGCGPIO register provides software the capability to enable and disable GPIO modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the GPIO modules. To support legacy software, the DCGC2 register is available. A write to the DCGC2 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC2 register can be read back correctly with a read of the DCGC2 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as GPIO A), the write causes proper operation, but the value of that bit is not reflected in the DCGC2 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
General-Purpose Input/Output Deep-Sleep Mode Clock Gating Control (DCGCGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port F in deep-sleep mode. GPIO Port F is disabled.
D5
R/W
D4
R/W
GPIO Port E Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port E in deep-sleep mode. GPIO Port E is disabled.
April 25, 2012
Bit/Field 3
Name D3
Type R/W
Reset 0
Description GPIO Port D Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port D in deep-sleep mode. GPIO Port D is disabled.
D2
R/W
GPIO Port C Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port C in deep-sleep mode. GPIO Port C is disabled.
D1
R/W
GPIO Port B Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port B in deep-sleep mode. GPIO Port B is disabled.
D0
R/W
GPIO Port A Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to GPIO Port A in deep-sleep mode. GPIO Port A is disabled.
353
System Control
Register 80: Micro Direct Memory Access Deep-Sleep Mode Clock Gating Control (DCGCDMA), offset 0x80C
The DCGCDMA register provides software the capability to enable and disable the DMA module in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the DMA module. To support legacy software, the DCGC2 register is available. A write to the UDMA bit in the DCGC2 register also writes the D0 bit in this register. If the UDMA bit is changed by writing to the DCGC2 register, it can be read back correctly with a read of the DCGC2 register. If software uses this register to control the clock for the DMA module, the write causes proper operation, but the UDMA bit in the DCGC2 register does not reflect the value of the D0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Micro Direct Memory Access Deep-Sleep Mode Clock Gating Control (DCGCDMA)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 D0 R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the DMA module in deep-sleep mode. DMA module is disabled.
D0
R/W
April 25, 2012
Register 81: Hibernation Deep-Sleep Mode Clock Gating Control (DCGCHIB), offset 0x814
The DCGCHIB register provides software the capability to enable and disable the Hibernation module in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the Hibernation module. To support legacy software, the DCGC0 register is available. A write to the HIB bit in the DCGC0 register also writes the D0 bit in this register. If the HIB bit is changed by writing to the DCGC0 register, it can be read back correctly with a read of the DCGC0 register. If software uses this register to control the clock for the Hibernation module, the write causes proper operation, but the HIB bit in the DCGC0 register does not reflect the value of the D0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Hibernation Deep-Sleep Mode Clock Gating Control (DCGCHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the Hibernation module in deep-sleep mode. Hibernation module is disabled.
D0
R/W
355
System Control
Register 82: Universal Asynchronous Receiver/Transmitter Deep-Sleep Mode Clock Gating Control (DCGCUART), offset 0x818
The DCGCUART register provides software the capability to enable and disable the UART modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the UART modules. To support legacy software, the DCGC1 register is available. A write to the DCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC1 register can be read back correctly with a read of the DCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as UART0), the write causes proper operation, but the value of that bit is not reflected in the DCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Asynchronous Receiver/Transmitter Deep-Sleep Mode Clock Gating Control (DCGCUART)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 D7 RO 0 RO 0 RO 0 R/W 0 RO 0 6 D6 R/W 0 RO 0 5 D5 R/W 0 RO 0 4 D4 R/W 0 RO 0 3 D3 R/W 0 RO 0 2 D2 R/W 0 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 7 in deep-sleep mode. UART module 7 is disabled.
D7
R/W
D6
R/W
UART Module 6 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 6 in deep-sleep mode. UART module 6 is disabled.
April 25, 2012
Bit/Field 5
Name D5
Type R/W
Reset 0
Description UART Module 5 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to UART module 5 in deep-sleep mode. UART module 5 is disabled.
D4
R/W
D3
R/W
D2
R/W
D1
R/W
D0
R/W
357
System Control
Register 83: Synchronous Serial Interface Deep-Sleep Mode Clock Gating Control (DCGCSSI), offset 0x81C
The DCGCSSI register provides software the capability to enable and disable the SSI modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the SSI modules. To support legacy software, the DCGC1 register is available. A write to the DCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC1 register can be read back correctly with a read of the DCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as SSI0), the write causes proper operation, but the value of that bit is not reflected in the DCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Synchronous Serial Interface Deep-Sleep Mode Clock Gating Control (DCGCSSI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 D3 R/W 0 RO 0 2 D2 R/W 0 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 3 in deep-sleep mode. SSI module 3 is disabled.
D3
R/W
D2
R/W
SSI Module 2 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 2 in deep-sleep mode. SSI module 2 is disabled.
April 25, 2012
Bit/Field 1
Name D1
Type R/W
Reset 0
Description SSI Module 1 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 1 in deep-sleep mode. SSI module 1 is disabled.
D0
R/W
SSI Module 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to SSI module 0 in deep-sleep mode. SSI module 0 is disabled.
359
System Control
Register 84: Inter-Integrated Circuit Deep-Sleep Mode Clock Gating Control (DCGCI2C), offset 0x820
The DCGCI2C register provides software the capability to enable and disable the I2C modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the I2C modules. To support legacy software, the DCGC1 register is available. A write to the DCGC1 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC1 register can be read back correctly with a read of the DCGC1 register. Software must use this register to support modules that are not present in the legacy registers. If software uses this register to write a legacy peripheral (such as I2C0), the write causes proper operation, but the value of that bit is not reflected in the DCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Inter-Integrated Circuit Deep-Sleep Mode Clock Gating Control (DCGCI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 D3 R/W 0 RO 0 2 D2 R/W 0 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 3 in deep-sleep mode. I2C module 3 is disabled.
D3
R/W
D2
R/W
I2C Module 2 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 2 in deep-sleep mode. I2C module 2 is disabled.
April 25, 2012
Bit/Field 1
Name D1
Type R/W
Reset 0
Description I2C Module 1 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 1 in deep-sleep mode. I2C module 1 is disabled.
D0
R/W
I2C Module 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to I2C module 0 in deep-sleep mode. I2C module 0 is disabled.
361
System Control
Register 85: Universal Serial Bus Deep-Sleep Mode Clock Gating Control (DCGCUSB), offset 0x828
The DCGCUSB register provides software the capability to enable and disable the USB module in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the USB module. To support legacy software, the DCGC2 register is available. A write to the USB0 bit in the DCGC2 register also writes the D0 bit in this register. If the USB0 bit is changed by writing to the DCGC2 register, it can be read back correctly with a read of the DCGC2 register. If software uses this register to control the clock for the USB module, the write causes proper operation, but the USB0 bit in the DCGC2 register does not reflect the value of the D0 bit. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Universal Serial Bus Deep-Sleep Mode Clock Gating Control (DCGCUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the USB module in deep-sleep mode. USB module is disabled.
D0
R/W
April 25, 2012
Register 86: Controller Area Network Deep-Sleep Mode Clock Gating Control (DCGCCAN), offset 0x834
The DCGCCAN register provides software the capability to enable and disable the CAN modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the CAN modules. To support legacy software, the DCGC0 register is available. A write to the DCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC0 register can be read back correctly with a read of the DCGC0 register. If software uses this register to write a legacy peripheral (such as CAN0), the write causes proper operation, but the value of that bit is not reflected in the DCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Controller Area Network Deep-Sleep Mode Clock Gating Control (DCGCCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to CAN module 0 in deep-sleep mode. CAN module 0 is disabled.
D0
R/W
363
System Control
Register 87: Analog-to-Digital Converter Deep-Sleep Mode Clock Gating Control (DCGCADC), offset 0x838
The DCGCADC register provides software the capability to enable and disable the ADC modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the ADC modules. To support legacy software, the DCGC0 register is available. A write to the DCGC0 register also writes the corresponding bit in this register. Any bits that are changed by writing to the DCGC0 register can be read back correctly with a read of the DCGC0 register. If software uses this register to write a legacy peripheral (such as ADC0), the write causes proper operation, but the value of that bit is not reflected in the DCGC0 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog-to-Digital Converter Deep-Sleep Mode Clock Gating Control (DCGCADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 D1 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 1 in deep-sleep mode. ADC module 1 is disabled.
D1
R/W
D0
R/W
ADC Module 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to ADC module 0 in deep-sleep mode. ADC module 0 is disabled.
April 25, 2012
Register 88: Analog Comparator Deep-Sleep Mode Clock Gating Control (DCGCACMP), offset 0x83C
The DCGCACMP register provides software the capability to enable and disable the analog comparator module in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the watchdog modules and has the same bit polarity as the corresponding DCGCn bits. Important: This register should be used to control the clocking for the analog comparator module. To support legacy software, the DCGC1 register is available. Setting any of the COMPn bits in the DCGC1 register also sets the D0 bit in this register. If any of the COMPn bits are set by writing to the DCGC1 register, it can be read back correctly when reading the DCGC1 register. If software uses this register to change the clocking for the analog comparator module, the write causes proper operation, but the value D0 is not reflected by the COMPn bits in the DCGC1 register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Analog Comparator Deep-Sleep Mode Clock Gating Control (DCGCACMP)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the analog comparator module in deep-sleep mode. Analog comparator module is disabled.
D0
R/W
365
System Control
Register 89: EEPROM Deep-Sleep Mode Clock Gating Control (DCGCEEPROM), offset 0x858
The DCGCEEPROM register provides software the capability to enable and disable the EEPROM module in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power.
EEPROM Deep-Sleep Mode Clock Gating Control (DCGCEEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to the EEPROM module in deep-sleep mode. EEPROM module is disabled.
D0
R/W
April 25, 2012
Register 90: 32/64-Bit Wide General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCWTIMER), offset 0x85C
The DCGCWTIMER register provides software the capability to enable and disable 32/64-bit wide timer modules in deep-sleep mode. When enabled, a module is provided a clock. When disabled, the clock is disabled to save power. This register provides the same capability as the legacy Deep-Sleep Mode Clock Gating Control Register n DCGCn registers specifically for the timer modules and has the same bit polarity as the corresponding DCGCn bits.
32/64-Bit Wide General-Purpose Timer Deep-Sleep Mode Clock Gating Control (DCGCWTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 5 in deep-sleep mode. 32/64-bit wide general-purpose timer module 5 is disabled.
D5
R/W
D4
R/W
32/64-Bit Wide General-Purpose Timer 4 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 4 in deep-sleep mode. 32/64-bit wide general-purpose timer module 4 is disabled.
D3
R/W
367
System Control
Bit/Field 2
Name D2
Type R/W
Reset 0
Description 32/64-Bit Wide General-Purpose Timer 2 Deep-Sleep Mode Clock Gating Control Value Description 1 0 Enable and provide a clock to 32/64-bit wide general-purpose timer module 2 in deep-sleep mode. 32/64-bit wide general-purpose timer module 2 is disabled.
D1
R/W
D0
R/W
April 25, 2012
Register 91: Watchdog Timer Power Control (PCWD), offset 0x900

The PCWD register controls the power provided to the watchdog modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRWD register if the active mode changes and the corresponding bit in the RCGCWD, SCGCWD, or DCGCWD register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The watchdog modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Watchdog Timer Power Control (PCWD)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWD, SCGCWD or DCGCWD bit is cleared. Value Description 1 Watchdog module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Watchdog module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P1
R/W
369
System Control
Bit/Field 0
Name P0
Type R/W
Reset 1
Description Watchdog Timer 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWD, SCGCWD or DCGCWD bit is cleared. Value Description 1 Watchdog module 0 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Watchdog module 0 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
April 25, 2012
Register 92: 16/32-Bit General-Purpose Timer Power Control (PCTIMER), offset 0x904
The PCTIMER register controls the power provided to the 16/32-bit timer modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding modules state is not retained. Software should perform a peripheral reset using the SRTIMER register if the active mode changes and the corresponding bit in the RCGCTIMER, SCGCTIMER, or DCGCTIMER register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The timer modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
16/32-Bit General-Purpose Timer Power Control (PCTIMER)

Base 0x400F.E000 Offset 0x904 Type R/W, reset 0x0000.003F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 P5 RO 0 RO 0 RO 0 RO 0 R/W 1 RO 0 4 P4 R/W 1 RO 0 3 P3 R/W 1 RO 0 2 P2 R/W 1 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCTIMER, SCGCTIMER or DCGCTIMER bit is cleared. Value Description 1 Timer module 5 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 5 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P5
R/W
371
System Control
Bit/Field 4
Name P4
Type R/W
Reset 1
Description 16/32-Bit General-Purpose Timer 4 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCTIMER, SCGCTIMER or DCGCTIMER bit is cleared. Value Description 1 Timer module 4 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 4 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P3
R/W
16/32-Bit General-Purpose Timer 3 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCTIMER, SCGCTIMER or DCGCTIMER bit is cleared. Value Description 1 Timer module 3 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 3 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P2
R/W
April 25, 2012
Bit/Field 1
Name P1
Type R/W
Reset 1
Description 16/32-Bit General-Purpose Timer 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCTIMER, SCGCTIMER or DCGCTIMER bit is cleared. Value Description 1 Timer module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
373
System Control
Register 93: General-Purpose Input/Output Power Control (PCGPIO), offset 0x908

The PCGPIO register controls the power provided to the GPIO modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRGPIO register if the active mode changes and the corresponding bit in the RCGCGPIO, SCGCGPIO, or DCGCGPIO register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The GPIO modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
General-Purpose Input/Output Power Control (PCGPIO)

Base 0x400F.E000 Offset 0x908 Type R/W, reset 0x0000.7FFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port F is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port F is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P5
R/W
April 25, 2012
Bit/Field 4
Name P4
Type R/W
Reset 1
Description GPIO Port E Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port E is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port E is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P3
R/W
GPIO Port D Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port D is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port D is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P2
R/W
GPIO Port C Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port C is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port C is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
375
System Control
Bit/Field 1
Name P1
Type R/W
Reset 1
Description GPIO Port B Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port B is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port B is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
GPIO Port A Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCGPIO, SCGCGPIO or DCGCGPIO bit is cleared. Value Description 1 GPIO Port A is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 GPIO Port A is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
April 25, 2012
Register 94: Micro Direct Memory Access Power Control (PCDMA), offset 0x90C
The PCDMA register controls the power provided to the DMA module. Clearing the bit corresponding to the module indicates to the hardware that firmware requests that the peripheral be unpowered. When the bit in this register is set, the module's state is not retained. Software should perform a peripheral reset using the SRDMA register if the active mode changes and the corresponding bit in the RCGCDMA, SCGCDMA, or DCGCDMA register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The DMA module does not currently have the ability to respond to the power down request. Setting the bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Micro Direct Memory Access Power Control (PCDMA)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 P0 R/W 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCDMA, SCGCDMA or DCGCDMA bit is cleared. Value Description 1 The DMA module is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 The DMA module is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
377
System Control
Register 95: Hibernation Power Control (PCHIB), offset 0x914

The PCHIB register controls the power provided to the Hibernation module. Clearing the bit corresponding to the module indicates to the hardware that firmware requests that the peripheral be unpowered. When the bit in this register is set, the module's state is not retained. Software should perform a peripheral reset using the SRHIB register if the active mode changes and the corresponding bit in the RCGCHIB, SCGCHIB, or DCGCHIB register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The Hibernation module does not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Hibernation Power Control (PCHIB)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCHIB, SCGCHIB or DCGCHIB bit is cleared. Value Description 1 The Hibernation module is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 The Hibernation module is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
April 25, 2012
Register 96: Universal Asynchronous Receiver/Transmitter Power Control (PCUART), offset 0x918
The PCUART register controls the power provided to the UART modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRUART register if the active mode changes and the corresponding bit in the RCGCUART, SCGCUART, or DCGCUART register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The UART modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Universal Asynchronous Receiver/Transmitter Power Control (PCUART)

Base 0x400F.E000 Offset 0x918 Type R/W, reset 0x0000.00FF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 P7 RO 0 RO 0 RO 0 R/W 1 RO 0 6 P6 R/W 1 RO 0 5 P5 R/W 1 RO 0 4 P4 R/W 1 RO 0 3 P3 R/W 1 RO 0 2 P2 R/W 1 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCUART, SCGCUART or DCGCUART bit is cleared. Value Description 1 UART module 7 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 UART module 7 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P7
R/W
379
System Control
Bit/Field 6
Name P6
Type R/W
Reset 1
Description UART Module 6 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCUART, SCGCUART or DCGCUART bit is cleared. Value Description 1 UART module 6 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 UART module 6 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P5
R/W
UART Module 5 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCUART, SCGCUART or DCGCUART bit is cleared. Value Description 1 UART module 5 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 UART module 5 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P4
R/W
April 25, 2012
Bit/Field 3
Name P3
Type R/W
Reset 1
P2
R/W
P1
R/W
381
System Control
Bit/Field 0
Name P0
Type R/W
Reset 1
April 25, 2012
Register 97: Synchronous Serial Interface Power Control (PCSSI), offset 0x91C
The PCSSI register controls the power provided to the SSI modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRSSI register if the active mode changes and the corresponding bit in the RCGCSSI, SCGCSSI, or DCGCSSI register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The SSI modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Synchronous Serial Interface Power Control (PCSSI)

Base 0x400F.E000 Offset 0x91C Type R/W, reset 0x0000.000F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 P3 R/W 1 RO 0 2 P2 R/W 1 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCSSI, SCGCSSI or DCGCSSI bit is cleared. Value Description 1 SSI module 3 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 SSI module 3 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P3
R/W
383
System Control
Bit/Field 2
Name P2
Type R/W
Reset 1
Description SSI Module 2 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCSSI, SCGCSSI or DCGCSSI bit is cleared. Value Description 1 SSI module 2 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 SSI module 2 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P1
R/W
SSI Module 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCSSI, SCGCSSI or DCGCSSI bit is cleared. Value Description 1 SSI module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 SSI module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
SSI Module 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCSSI, SCGCSSI or DCGCSSI bit is cleared. Value Description 1 SSI module 0 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 SSI module 0 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
April 25, 2012
Register 98: Inter-Integrated Circuit Power Control (PCI2C), offset 0x920

The PCI2C register controls the power provided to the I2C modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRI2C register if the active mode changes and the corresponding bit in the RCGCI2C, SCGCI2C, or DCGCI2C register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The I2C modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Inter-Integrated Circuit Power Control (PCI2C)

Base 0x400F.E000 Offset 0x920 Type R/W, reset 0x0000.003F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 P3 R/W 1 RO 0 2 P2 R/W 1 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCI2C, SCGCI2C or DCGCI2C bit is cleared. Value Description 1 I2C module 3 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 I2C module 3 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P3
R/W
385
System Control
Bit/Field 2
Name P2
Type R/W
Reset 1
Description I2C Module 2 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCI2C, SCGCI2C or DCGCI2C bit is cleared. Value Description 1 I2C module 2 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 I2C module 2 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P1
R/W
I2C Module 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCI2C, SCGCI2C or DCGCI2C bit is cleared. Value Description 1 I2C module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 I2C module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
I2C Module 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCI2C, SCGCI2C or DCGCI2C bit is cleared. Value Description 1 I2C module 0 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 I2C module 0 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
April 25, 2012
Register 99: Universal Serial Bus Power Control (PCUSB), offset 0x928
The PCUSB register controls the power provided to the USB module. Clearing the bit corresponding to the module indicates to the hardware that firmware requests that the peripheral be unpowered. When the bit in this register is set, the module's state is not retained. Software should perform a peripheral reset using the SRUSB register if the active mode changes and the corresponding bit in the RCGCUSB, SCGCUSB, or DCGCUSB register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state.
Universal Serial Bus Power Control (PCUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCUSB, SCGCUSB or DCGCUSB bit is cleared. Value Description 1 The USB module is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 The USB module is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
387
System Control
Register 100: Controller Area Network Power Control (PCCAN), offset 0x934
The PCCAN register controls the power provided to the CAN modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRCAN register if the active mode changes and the corresponding bit in the RCGCCAN, SCGCCAN, or DCGCCAN register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state.
Controller Area Network Power Control (PCCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCCAN, SCGCCAN or DCGCCAN bit is cleared. Value Description 1 CAN module 0 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 CAN module 0 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
April 25, 2012
Register 101: Analog-to-Digital Converter Power Control (PCADC), offset 0x938

The PCADC register controls the power provided to the ADC modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRADC register if the active mode changes and the corresponding bit in the RCGCADC, SCGCADC, or DCGCADC register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The ADC modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Analog-to-Digital Converter Power Control (PCADC)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 P1 R/W 1 RO 0 0 P0 R/W 1
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCADC, SCGCADC or DCGCADC bit is cleared. Value Description 1 ADC module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 ADC module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P1
R/W
389
System Control
Bit/Field 0
Name P0
Type R/W
Reset 1
Description ADC Module 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCADC, SCGCADC or DCGCADC bit is cleared. Value Description 1 ADC module 0 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 ADC module 0 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
April 25, 2012
Register 102: Analog Comparator Power Control (PCACMP), offset 0x93C

The PCACMP register controls the power provided to the analog comparator module. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding module's state is not retained. Software should perform a peripheral reset using the SRACMP register if the active mode changes and the corresponding bit in the RCGCACMP, SCGCACMP, or DCGCACMP register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The analog comparator module does not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
Analog Comparator Power Control (PCACMP)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCACMP, SCGCACMP or DCGCACMP bit is cleared. Value Description 1 The analog comparator module is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 The analog comparator module is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
391
System Control
Register 103: EEPROM Power Control (PCEEPROM), offset 0x958

The PCEEPROM register controls the power provided to the EEPROM module. Clearing the bit corresponding to the module indicates to the hardware that firmware requests that the peripheral be unpowered. When the bit in this register is set, the modules state is not retained. Software should perform a peripheral reset using the SREEPROM register if the active mode changes and the corresponding bit in the RCGCEEPROM, SCGCEEPROM, or DCGCEEPROM register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The EEPROM module does not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
EEPROM Power Control (PCEEPROM)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCEEPROM, SCGCEEPROM or DCGCEEPROM bit is cleared. Value Description 1 The EEPROM module is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 The EEPROM module is not powered and does not receive a clock. In this case, the modules state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
April 25, 2012
Register 104: 32/64-Bit Wide General-Purpose Timer Power Control (PCWTIMER), offset 0x95C
The PCWTIMER register controls the power provided to the 32/64-bit wide timer modules. Clearing the bit corresponding to one of the modules indicates to the hardware that firmware requests that the peripheral be unpowered. When a bit in this register is set, the corresponding modules state is not retained. Software should perform a peripheral reset using the SRWTIMER register if the active mode changes and the corresponding bit in the RCGCWTIMER, SCGCWTIMER, or DCGCWTIMER register is a 1 or the Pn bit is changed from a 0 to a 1. Software must re-initialize the module when re-enabled due to the loss of state. Note: The timer modules do not currently have the ability to respond to the power down request. Setting a bit in this register has no effect on power consumption. This register is provided for future software compatibility.
32/64-Bit Wide General-Purpose Timer Power Control (PCWTIMER)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWTIMER, SCGCWTIMER or DCGCWTIMER bit is cleared. Value Description 1 Timer module 5 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 5 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P5
R/W
393
System Control
Bit/Field 4
Name P4
Type R/W
Reset 1
Description 32/64-Bit Wide General-Purpose Timer 4 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWTIMER, SCGCWTIMER or DCGCWTIMER bit is cleared. Value Description 1 Timer module 4 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 4 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P3
R/W
32/64-Bit Wide General-Purpose Timer 3 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWTIMER, SCGCWTIMER or DCGCWTIMER bit is cleared. Value Description 1 Timer module 3 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 3 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P2
R/W
April 25, 2012
Bit/Field 1
Name P1
Type R/W
Reset 1
Description 32/64-Bit Wide General-Purpose Timer 1 Power Control The value of this bit does not have meaning unless the corresponding, active mode RCGCWTIMER, SCGCWTIMER or DCGCWTIMER bit is cleared. Value Description 1 Timer module 1 is powered, but does not receive a clock. In this case, the module is inactive. This configuration provides the second-lowest power consumption of the module because it consumes only leakage current. 0 Timer module 1 is not powered and does not receive a clock. In this case, the module's state is not retained. This configuration provides the lowest power consumption state of the module because it consumes no dynamic nor leakage current.
P0
R/W
395
System Control
Register 105: Watchdog Timer Peripheral Ready (PRWD), offset 0xA00

The PRWD register indicates whether the watchdog modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCWD bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCWD bit is changed. A reset change is initiated if the corresponding SRWD bit is changed from 0 to 1. The PRWD bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Watchdog Timer Peripheral Ready (PRWD)
Base 0x400F.E000 Offset 0xA00 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer 1 Peripheral Ready Value Description 1 0 Watchdog module 1 is ready for access. Watchdog module 1 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
R0
R/W
Watchdog Timer 0 Peripheral Ready Value Description 1 0 Watchdog module 0 is ready for access. Watchdog module 0 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
April 25, 2012
Register 106: 16/32-Bit General-Purpose Timer Peripheral Ready (PRTIMER), offset 0xA04
The PRTIMER register indicates whether the timer modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCTIMER bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCTIMER bit is changed. A reset change is initiated if the corresponding SRTIMER bit is changed from 0 to 1. The PRTIMER bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
16/32-Bit General-Purpose Timer Peripheral Ready (PRTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 16/32-Bit General-Purpose Timer 5 Peripheral Ready Value Description 1 0 16/32-bit timer module 5 is ready for access. 16/32-bit timer module 5 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R5
R/W
R4
R/W
16/32-Bit General-Purpose Timer 4 Peripheral Ready Value Description 1 0 16/32-bit timer module 4 is ready for access. 16/32-bit timer module 4 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
397
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description 16/32-Bit General-Purpose Timer 2 Peripheral Ready Value Description 1 0 16/32-bit timer module 2 is ready for access. 16/32-bit timer module 2 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
R0
R/W
April 25, 2012
Register 107: General-Purpose Input/Output Peripheral Ready (PRGPIO), offset 0xA08

The PRGPIO register indicates whether the GPIO modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCGPIO bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCGPIO bit is changed. A reset change is initiated if the corresponding SRGPIO bit is changed from 0 to 1. The PRGPIO bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
General-Purpose Input/Output Peripheral Ready (PRGPIO)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port F Peripheral Ready Value Description 1 0 GPIO Port F is ready for access. GPIO Port F is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R5
R/W
R4
R/W
GPIO Port E Peripheral Ready Value Description 1 0 GPIO Port E is ready for access. GPIO Port E is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
GPIO Port D Peripheral Ready Value Description 1 0 GPIO Port D is ready for access. GPIO Port D is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
399
System Control
Bit/Field 2
Name R2
Type R/W
Reset 0
Description GPIO Port C Peripheral Ready Value Description 1 0 GPIO Port C is ready for access. GPIO Port C is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
GPIO Port B Peripheral Ready Value Description 1 0 GPIO Port B is ready for access. GPIO Port B is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
GPIO Port A Peripheral Ready Value Description 1 0 GPIO Port A is ready for access. GPIO Port A is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
April 25, 2012
Register 108: Micro Direct Memory Access Peripheral Ready (PRDMA), offset 0xA0C
The PRDMA register indicates whether the DMA module is ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCDMA bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCDMA bit is changed. A reset change is initiated if the corresponding SRDMA bit is changed from 0 to 1. The PRDMA bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Micro Direct Memory Access Peripheral Ready (PRDMA)
Base 0x400F.E000 Offset 0xA0C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Module Peripheral Ready Value Description 1 0 The DMA module is ready for access. The DMA module is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
401
System Control
Register 109: Hibernation Peripheral Ready (PRHIB), offset 0xA14

The PRHIB register indicates whether the Hibernation module is ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCHIB bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCHIB bit is changed. A reset change is initiated if the corresponding SRHIB bit is changed from 0 to 1. The PRHIB bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Hibernation Peripheral Ready (PRHIB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Module Peripheral Ready Value Description 1 0 The Hibernation module is ready for access. The Hibernation module is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
April 25, 2012
Register 110: Universal Asynchronous Receiver/Transmitter Peripheral Ready (PRUART), offset 0xA18
The PRUART register indicates whether the UART modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCUART bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCUART bit is changed. A reset change is initiated if the corresponding SRUART bit is changed from 0 to 1. The PRUART bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Universal Asynchronous Receiver/Transmitter Peripheral Ready (PRUART)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Module 7 Peripheral Ready Value Description 1 0 UART module 7 is ready for access. UART module 7 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R7
R/W
R6
R/W
UART Module 6 Peripheral Ready Value Description 1 0 UART module 6 is ready for access. UART module 6 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R5
R/W
403
System Control
Bit/Field 4
Name R4
Type R/W
Reset 0
Description UART Module 4 Peripheral Ready Value Description 1 0 UART module 4 is ready for access. UART module 4 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
R2
R/W
R1
R/W
R0
R/W
April 25, 2012
Register 111: Synchronous Serial Interface Peripheral Ready (PRSSI), offset 0xA1C
The PRSSI register indicates whether the SSI modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCSSI bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCSSI bit is changed. A reset change is initiated if the corresponding SRSSI bit is changed from 0 to 1. The PRSSI bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Synchronous Serial Interface Peripheral Ready (PRSSI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 3 Peripheral Ready Value Description 1 0 SSI module 3 is ready for access. SSI module 3 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
R2
R/W
SSI Module 2 Peripheral Ready Value Description 1 0 SSI module 2 is ready for access. SSI module 2 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
SSI Module 1 Peripheral Ready Value Description 1 0 SSI module 1 is ready for access. SSI module 1 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
405
System Control
Bit/Field 0
Name R0
Type R/W
Reset 0
Description SSI Module 0 Peripheral Ready Value Description 1 0 SSI module 0 is ready for access. SSI module 0 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
April 25, 2012
Register 112: Inter-Integrated Circuit Peripheral Ready (PRI2C), offset 0xA20

The PRI2C register indicates whether the I2C modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCI2C bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCI2C bit is changed. A reset change is initiated if the corresponding SRI2C bit is changed from 0 to 1. The PRI2C bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Inter-Integrated Circuit Peripheral Ready (PRI2C)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Module 3 Peripheral Ready Value Description 1 0 I2C module 3 is ready for access. I2C module 3 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
R2
R/W
I2C Module 2 Peripheral Ready Value Description 1 0 I2C module 2 is ready for access. I2C module 2 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
I2C Module 1 Peripheral Ready Value Description 1 0 I2C module 1 is ready for access. I2C module 1 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
407
System Control
Bit/Field 0
Name R0
Type R/W
Reset 0
Description I2C Module 0 Peripheral Ready Value Description 1 0 I2C module 0 is ready for access. I2C module 0 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
April 25, 2012
Register 113: Universal Serial Bus Peripheral Ready (PRUSB), offset 0xA28
The PRUSB register indicates whether the USB module is ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCUSB bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCUSB bit is changed. A reset change is initiated if the corresponding SRUSB bit is changed from 0 to 1. The PRUSB bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Universal Serial Bus Peripheral Ready (PRUSB)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module Peripheral Ready Value Description 1 0 The USB module is ready for access. The USB module is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
409
System Control
Register 114: Controller Area Network Peripheral Ready (PRCAN), offset 0xA34
The PRCAN register indicates whether the CAN modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCCAN bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCCAN bit is changed. A reset change is initiated if the corresponding SRCAN bit is changed from 0 to 1. The PRCAN bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Controller Area Network Peripheral Ready (PRCAN)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 0 Peripheral Ready Value Description 1 0 CAN module 0 is ready for access. CAN module 0 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
April 25, 2012
Register 115: Analog-to-Digital Converter Peripheral Ready (PRADC), offset 0xA38

The PRADC register indicates whether the ADC modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCADC bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCADC bit is changed. A reset change is initiated if the corresponding SRADC bit is changed from 0 to 1. The PRADC bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Analog-to-Digital Converter Peripheral Ready (PRADC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Peripheral Ready Value Description 1 0 ADC module 1 is ready for access. ADC module 1 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
R0
R/W
ADC Module 0 Peripheral Ready Value Description 1 0 ADC module 0 is ready for access. ADC module 0 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
411
System Control
Register 116: Analog Comparator Peripheral Ready (PRACMP), offset 0xA3C

The PRACMP register indicates whether the analog comparator module is ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCACMP bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCACMP bit is changed. A reset change is initiated if the corresponding SRACMP bit is changed from 0 to 1. The PRACMP bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
Analog Comparator Peripheral Ready (PRACMP)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator Module 0 Peripheral Ready Value Description 1 0 The analog comparator module is ready for access. The analog comparator module is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
April 25, 2012
Register 117: EEPROM Peripheral Ready (PREEPROM), offset 0xA58

The PREEPROM register indicates whether the EEPROM module is ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCEEPROM bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCEEPROM bit is changed. A reset change is initiated if the corresponding SREEPROM bit is changed from 0 to 1. The PREEPROM bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
EEPROM Peripheral Ready (PREEPROM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Module Peripheral Ready Value Description 1 0 The EEPROM module is ready for access. The EEPROM module is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R0
R/W
413
System Control
Register 118: 32/64-Bit Wide General-Purpose Timer Peripheral Ready (PRWTIMER), offset 0xA5C
The PRWTIMER register indicates whether the timer modules are ready to be accessed by software following a change in status of power, Run mode clocking, or reset. A power change is initiated if the corresponding PCWTIMER bit is changed from 0 to 1. A Run mode clocking change is initiated if the corresponding RCGCWTIMER bit is changed. A reset change is initiated if the corresponding SRWTIMER bit is changed from 0 to 1. The PRWTIMER bit is cleared on any of the above events and is not set again until the module is completely powered, enabled, and internally reset.
32/64-Bit Wide General-Purpose Timer Peripheral Ready (PRWTIMER)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:6
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide General-Purpose Timer 5 Peripheral Ready Value Description 1 0 32/64-bit wide timer module 5 is ready for access. 32/64-bit wide timer module 5 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R5
R/W
R4
R/W
32/64-Bit Wide General-Purpose Timer 4 Peripheral Ready Value Description 1 0 32/64-bit wide timer module 4 is ready for access. 32/64-bit wide timer module 4 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R3
R/W
April 25, 2012
Bit/Field 2
Name R2
Type R/W
Reset 0
Description 32/64-Bit Wide General-Purpose Timer 2 Peripheral Ready Value Description 1 0 32/64-bit wide timer module 2 is ready for access. 32/64-bit wide timer module 2 is not ready for access. It is unclocked, unpowered, or in the process of completing a reset sequence.
R1
R/W
R0
R/W
5.6
System Control Legacy Register Descriptions

All addresses given are relative to the System Control base address of 0x400F.E000. Important: Register in this section are provided for legacy software support only; registers in System Control Register Descriptions on page 231 should be used instead.
415
System Control
Register 119: Device Capabilities 0 (DC0), offset 0x008

This legacy register is predefined by the part and can be used to verify features. Important: This register is provided for legacy software support only. The Flash Size (FSIZE) and SRAM Size (SSIZE) registers should be used to determine this microcontroller's memory sizes. A read of DC0 correctly identifies legacy memory sizes but software must use FSIZE and SSIZE for memory sizes that are not listed below.
Device Capabilities 0 (DC0)
Base 0x400F.E000 Offset 0x008 Type RO, reset 0x007F.007F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
SRAMSZ Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0
FLASHSZ Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1
Bit/Field 31:16
Name SRAMSZ
Type RO
Reset 0x7F
Description SRAM Size Indicates the size of the on-chip SRAM. Value Description 0x7 0xF 2 KB of SRAM 4 KB of SRAM
0x17 6 KB of SRAM 0x1F 8 KB of SRAM 0x2F 12 KB of SRAM 0x3F 16 KB of SRAM 0x4F 20 KB of SRAM 0x5F 24 KB of SRAM 0x7F 32 KB of SRAM
April 25, 2012
Bit/Field 15:0
Name FLASHSZ
Type RO
Reset 0x7F
Description Flash Size Indicates the size of the on-chip Flash memory. Value Description 0x3 0x7 0xF 8 KB of Flash 16 KB of Flash 32 KB of Flash
0x1F 64 KB of Flash 0x2F 96 KB of Flash 0x3F 128 KB of Flash 0x5F 192 KB of Flash 0x7F 256 KB of Flash
417
System Control

This register is predefined by the part and can be used to verify features. If any bit is clear in this register, the module is not present. The corresponding bit in the RCGC0, SCGC0, DCGC0, and the peripheral-specific RCGC, SCGC, and DCGC registers cannot be set. Important: This register is provided for legacy software support only. The Peripheral Present registers should be used to determine which modules are implemented on this microcontroller. A read of DC1 correctly identifies if a legacy module is present but software must use the Peripheral Present registers to determine if a module is present that is not supported by the DCn registers. Likewise, the ADC Peripheral Properties (ADCPP) register should be used to determine the maximum ADC sample rate and whether the temperature sensor is present. However, to support legacy software, the MAXADCnSPD fields and the TEMPSNS bit are available. A read of DC1 correctly identifies the maximum ADC sample rate for legacy rates and whether the temperature sensor is present.
Base 0x400F.E000 Offset 0x010 Type RO, reset 0x1103.2FFF
31 30 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 29 28 WDT1 RO 1 12 27 26 25 CAN1 RO 0 9 24 CAN0 RO 1 8 23 22 21 PWM1 RO 0 5 TEMPSNS RO 1 20 PWM0 RO 0 4 PLL RO 1 19 18 17 ADC1 RO 1 1 SWD RO 1 16 ADC0 RO 1 0 JTAG RO 1
reserved RO 0 7 MPU RO 1 RO 0 6 HIB RO 1
reserved RO 0 3 WDT0 RO 1 RO 0 2 SWO RO 1
MINSYSDIV Type Reset RO 0 RO 0 RO 1 RO 0
MAXADC1SPD RO 1 RO 1
Bit/Field 31:29
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Timer1 Present When set, indicates that watchdog timer 1 is present.
28
WDT1
RO
0x1
27:26
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN Module 1 Present When set, indicates that CAN unit 1 is present.
25
CAN1
RO
0x0
24
CAN0
RO
0x1
CAN Module 0 Present When set, indicates that CAN unit 0 is present.
23:22
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PWM Module 1 Present When set, indicates that the PWM module is present.
21
PWM1
RO
0x0
April 25, 2012
Bit/Field 20
Name PWM0
Type RO
Reset 0x0
Description PWM Module 0 Present When set, indicates that the PWM module is present.
19:18
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Module 1 Present When set, indicates that ADC module 1 is present.
17
ADC1
RO
0x1
16
ADC0
RO
0x1
ADC Module 0 Present When set, indicates that ADC module 0 is present
15:12
MINSYSDIV
RO
0x2
System Clock Divider Minimum 4-bit divider value for system clock. The reset value is hardware-dependent. See the RCC register for how to change the system clock divisor using the SYSDIV bit. Value Description 0x1 0x2 0x3 0x4 0x7 0x9 Specifies an 80-MHz CPU clock with a PLL divider of 2.5. Specifies a 66-MHz CPU clock with a PLL divider of 3. Specifies a 50-MHz CPU clock with a PLL divider of 4. Specifies a 40-MHz CPU clock with a PLL divider of 5. Specifies a 25-MHz clock with a PLL divider of 8. Specifies a 20-MHz clock with a PLL divider of 10.
11:10
MAXADC1SPD
RO
0x3
Max ADC1 Speed This field indicates the maximum rate at which the ADC samples data. Value Description 0x3 0x2 0x1 0x0 1M samples/second 500K samples/second 250K samples/second 125K samples/second
9:8
MAXADC0SPD
RO
0x3
Max ADC0 Speed This field indicates the maximum rate at which the ADC samples data. Value Description 0x3 0x2 0x1 0x0 1M samples/second 500K samples/second 250K samples/second 125K samples/second
MPU
RO
0x1
MPU Present When set, indicates that the Cortex-M4F Memory Protection Unit (MPU) module is present. See the "Cortex-M4F Peripherals" chapter for details on the MPU.
419
System Control
Bit/Field 6
Name HIB
Type RO
Reset 0x1
Description Hibernation Module Present When set, indicates that the Hibernation module is present.
TEMPSNS
RO
0x1
Temp Sensor Present When set, indicates that the on-chip temperature sensor is present.
PLL
RO
0x1
PLL Present When set, indicates that the on-chip Phase Locked Loop (PLL) is present.
WDT0
RO
0x1
Watchdog Timer 0 Present When set, indicates that watchdog timer 0 is present.
SWO
RO
0x1
SWO Trace Port Present When set, indicates that the Serial Wire Output (SWO) trace port is present.
SWD
RO
0x1
SWD Present When set, indicates that the Serial Wire Debugger (SWD) is present.
JTAG
RO
0x1
JTAG Present When set, indicates that the JTAG debugger interface is present.
April 25, 2012

This register is predefined by the part and can be used to verify features. If any bit is clear in this register, the module is not present. The corresponding bit in the RCGC1, SCGC1, DCGC1, and the peripheral-specific RCGC, SCGC, and DCGC registers registers cannot be set. Important: This register is provided for legacy software support only. The Peripheral Present registers should be used to determine which modules are implemented on this microcontroller. A read of DC2 correctly identifies if a legacy module is present but software must use the Peripheral Present registers to determine if a module is present that is not supported by the DCn registers. Note that the Analog Comparator Peripheral Present (PPACMP) register identifies whether the analog comparator module is present. The Analog Comparator Peripheral Properties (ACMPPP) register indicates how many analog comparator blocks are present in the module.
Base 0x400F.E000 Offset 0x014 Type RO, reset 0x030F.F037
31
reserved
30 EPI0 RO 0 14 I2C1 RO 1
29
reserved
28 I2S0 RO 0 12 I2C0 RO 1
27
reserved
26 COMP2 RO 0 10
25 COMP1 RO 1 9 QEI1 RO 0
24 COMP0 RO 1 8 QEI0 RO 0
23
22
21
20
19 TIMER3
18 TIMER2 RO 1 2 UART2 RO 1
reserved RO 0 7 reserved RO 0 RO 0 RO 0 6 RO 0 5 SSI1 RO 1 RO 0 4 SSI0 RO 1
Type Reset
RO 0 15 I2C1HS
RO 0 13 I2C0HS RO 1
RO 0 11
RO 1 3
reserved
reserved RO 0 RO 0
Type Reset
RO 1
RO 0
Bit/Field 31
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EPI Module 0 Present When set, indicates that EPI module 0 is present.
30
EPI0
RO
0x0
29
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2S Module 0 Present When set, indicates that I2S module 0 is present.
28
I2S0
RO
0x0
27
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator 2 Present When set, indicates that analog comparator 2 is present.
26
COMP2
RO
0x0
25
COMP1
RO
0x1
Analog Comparator 1 Present When set, indicates that analog comparator 1 is present.
421
System Control
Bit/Field 24
Name COMP0
Type RO
Reset 0x1
Description Analog Comparator 0 Present When set, indicates that analog comparator 0 is present.
23:20
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Timer Module 3 Present When set, indicates that General-Purpose Timer module 3 is present.
19
TIMER3
RO
0x1
18
TIMER2
RO
0x1
Timer Module 2 Present When set, indicates that General-Purpose Timer module 2 is present.
17
TIMER1
RO
0x1
16
TIMER0
RO
0x1
15
I2C1HS
RO
0x1
I2C Module 1 Speed When set, indicates that I2C module 1 can operate in high-speed mode.
14
I2C1
RO
0x1
I2C Module 1 Present When set, indicates that I2C module 1 is present.
13
I2C0HS
RO
0x1
I2C Module 0 Speed When set, indicates that I2C module 0 can operate in high-speed mode.
12
I2C0
RO
0x1
I2C Module 0 Present When set, indicates that I2C module 0 is present.
11:10
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. QEI Module 1 Present When set, indicates that QEI module 1 is present.
QEI1
RO
0x0
QEI0
RO
0x0
QEI Module 0 Present When set, indicates that QEI module 0 is present.
7:6
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Module 1 Present When set, indicates that SSI module 1 is present.
SSI1
RO
0x1
SSI0
RO
0x1
SSI Module 0 Present When set, indicates that SSI module 0 is present.
reserved
RO
April 25, 2012
Bit/Field 2
Name UART2
Type RO
Reset 0x1
Description UART Module 2 Present When set, indicates that UART module 2 is present.
UART1
RO
0x1
UART Module 1 Present When set, indicates that UART module 1 is present.
UART0
RO
0x1
UART Module 0 Present When set, indicates that UART module 0 is present.
423
System Control

This register is predefined by the part and can be used to verify features. If any bit is clear in this register, the feature is not present. Important: This register is provided for legacy software support only. For some modules, the peripheral-resident Peripheral Properties registers should be used to determine which pins are available on this microcontroller. A read of DC3 correctly identifies if a legacy pin is present but software must use the Peripheral Properties registers to determine if a pin is present that is not supported by the DCn registers.
Base 0x400F.E000 Offset 0x018 Type RO, reset 0xBFFF.0FC0
31 32KHZ Type Reset RO 1 15
PWMFAULT
30
reserved
29 CCP5 RO 1 13
28 CCP4 RO 1 12
27 CCP3 RO 1 11 C1O RO 1
26 CCP2 RO 1 10
25 CCP1 RO 1 9
24 CCP0 RO 1 8 C0O RO 1
23
22
21
20
19
18
17
16
ADC0AIN7 ADC0AIN6 ADC0AIN5 ADC0AIN4 ADC0AIN3 ADC0AIN2 ADC0AIN1 ADC0AIN0
RO 0 14 C2O RO 0
RO 1 7
RO 1 6
RO 1 5 PWM5 RO 0
RO 1 4 PWM4 RO 0
RO 1 3 PWM3 RO 0
RO 1 2 PWM2 RO 0
RO 1 1 PWM1 RO 0
RO 1 0 PWM0 RO 0
C2PLUS C2MINUS RO 0 RO 0
Type Reset
RO 0
Bit/Field 31
Name 32KHZ
Type RO
Reset 0x1
Description 32KHz Input Clock Available When set, indicates an even CCP pin is present and can be used as a 32-KHz input clock. Note: The GPTMPP register does not provide this information.
30
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CCP5 Pin Present When set, indicates that Capture/Compare/PWM pin 5 is present. Note: The GPTMPP register does not provide this information.
29
CCP5
RO
0x1
28
CCP4
RO
0x1
CCP4 Pin Present When set, indicates that Capture/Compare/PWM pin 4 is present. Note: The GPTMPP register does not provide this information.
27
CCP3
RO
0x1
26
CCP2
RO
0x1
April 25, 2012
Bit/Field 25
Name CCP1
Type RO
Reset 0x1
Description CCP1 Pin Present When set, indicates that Capture/Compare/PWM pin 1 is present. Note: The GPTMPP register does not provide this information.
24
CCP0
RO
0x1
23
ADC0AIN7
RO
0x1
ADC Module 0 AIN7 Pin Present When set, indicates that ADC module 0 input pin 7 is present. Note: The CH field in the ADCPP register provides this information.
22
ADC0AIN6
RO
0x1
21
ADC0AIN5
RO
0x1
20
ADC0AIN4
RO
0x1
19
ADC0AIN3
RO
0x1
18
ADC0AIN2
RO
0x1
17
ADC0AIN1
RO
0x1
16
ADC0AIN0
RO
0x1
15
PWMFAULT
RO
0x0
PWM Fault Pin Present When set, indicates that a PWM Fault pin is present. See DC5 for specific Fault pins on this device. Note: The FCNT field in the PWMPP register provides this information.
14
C2O
RO
0x0
C2o Pin Present When set, indicates that the analog comparator 2 output pin is present. Note: The C2O bit in the ACMPPP register provides this information.
425
System Control
Bit/Field 13
Name C2PLUS
Type RO
Reset 0x0
Description C2+ Pin Present When set, indicates that the analog comparator 2 (+) input pin is present. Note: This pin is present when analog comparator 2 is present.
12
C2MINUS
RO
0x0
C2- Pin Present When set, indicates that the analog comparator 2 (-) input pin is present. Note: This pin is present when analog comparator 2 is present.
11
C1O
RO
0x1
10
C1PLUS
RO
0x1
C1+ Pin Present When set, indicates that the analog comparator 1 (+) input pin is present. Note: This pin is present when analog comparator 1 is present.
C1MINUS
RO
0x1
C0O
RO
0x1
C0PLUS
RO
0x1
C0+ Pin Present When set, indicates that the analog comparator 0 (+) input pin is present. Note: This pin is present when analog comparator 0 is present.
C0MINUS
RO
0x1
PWM5
RO
0x0
PWM5 Pin Present When set, indicates that the PWM pin 5 is present. Note: The GCNT field in the PWMPP register provides this information.
PWM4
RO
0x0
PWM3
RO
0x0
April 25, 2012
Bit/Field 2
Name PWM2
Type RO
Reset 0x0
Description PWM2 Pin Present When set, indicates that the PWM pin 2 is present. Note: The GCNT field in the PWMPP register provides this information.
PWM1
RO
0x0
PWM0
RO
0x0
427
System Control
Register 123: Device Capabilities 4 (DC4), offset 0x01C

This register is predefined by the part and can be used to verify features. If any bit is clear in this register, the module is not present. The corresponding bit in the RCGC2, SCGC2, DCGC2, and the peripheral-specific RCGC, SCGC, and DCGC registers registers cannot be set. Important: This register is provided for legacy software support only. The Peripheral Present registers should be used to determine which modules are implemented on this microcontroller. A read of DC4 correctly identifies if a legacy module is present but software must use the Peripheral Present registers to determine if a module is present that is not supported by the DCn registers. The peripheral-resident Peripheral Properties registers should be used to determine which pins and features are available on this microcontroller. A read of DC4 correctly identifies if a legacy pin or feature is present. Software must use the Peripheral Properties registers to determine if a pin or feature is present that is not supported by the DCn registers.
Base 0x400F.E000 Offset 0x01C Type RO, reset 0x0004.F03F
31
reserved
30 EPHY0 RO 0 14 CCP6 RO 1
29
reserved
28 EMAC0 RO 0 12 ROM RO 1
27
26 reserved
25
24 E1588
23
22
21 reserved
20
19
18 PICAL
17
16
reserved RO 0 1 GPIOB RO 1 RO 0 0 GPIOA RO 1
Type Reset
RO 0 15 CCP7
RO 0 13 UDMA RO 1
RO 0 11
RO 0 10 reserved
RO 0 9
RO 0 8 GPIOJ
RO 0 7 GPIOH RO 0
RO 0 6 GPIOG RO 0
RO 0 5 GPIOF RO 1
RO 0 4 GPIOE RO 1
RO 0 3 GPIOD RO 1
RO 1 2 GPIOC RO 1
Type Reset
RO 1
RO 0
RO 0
RO 0
RO 0
Bit/Field 31
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Ethernet PHY Layer 0 Present When set, indicates that Ethernet PHY layer 0 is present.
30
EPHY0
RO
0x0
29
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Ethernet MAC Layer 0 Present When set, indicates that Ethernet MAC layer 0 is present.
28
EMAC0
RO
0x0
27:25
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 1588 Capable When set, indicates that Ethernet MAC layer 0 is 1588 capable.
24
E1588
RO
0x0
April 25, 2012
Bit/Field 23:19
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PIOSC Calibrate When set, indicates that the PIOSC can be calibrated by software.
18
PICAL
RO
0x1
17:16
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CCP7 Pin Present When set, indicates that Capture/Compare/PWM pin 7 is present. Note: The GPTMPP register does not provide this information.
15
CCP7
RO
0x1
14
CCP6
RO
0x1
13
UDMA
RO
0x1
Micro-DMA Module Present When set, indicates that the micro-DMA module present.
12
ROM
RO
0x1
Internal Code ROM Present When set, indicates that internal code ROM is present.
11:9
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Port J Present When set, indicates that GPIO Port J is present.
GPIOJ
RO
0x0
GPIOH
RO
0x0
GPIO Port H Present When set, indicates that GPIO Port H is present.
GPIOG
RO
0x0
GPIO Port G Present When set, indicates that GPIO Port G is present.
GPIOF
RO
0x1
GPIO Port F Present When set, indicates that GPIO Port F is present.
GPIOE
RO
0x1
GPIO Port E Present When set, indicates that GPIO Port E is present.
GPIOD
RO
0x1
GPIO Port D Present When set, indicates that GPIO Port D is present.
GPIOC
RO
0x1
GPIO Port C Present When set, indicates that GPIO Port C is present.
GPIOB
RO
0x1
GPIO Port B Present When set, indicates that GPIO Port B is present.
429
System Control
Bit/Field 0
Name GPIOA
Type RO
Reset 0x1
Description GPIO Port A Present When set, indicates that GPIO Port A is present.
April 25, 2012

This register is predefined by the part and can be used to verify PWM features. If any bit is clear in this register, the module is not present. Important: This register is provided for legacy software support only. The PWM Peripheral Properties (PWMPP) register should be used to determine what pins and features are available on PWM modules. A read of this register correctly identifies if a legacy pin or feature is present. Software must use the PWMPP register to determine if a pin or feature that is not supported by the DCn registers is present.
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12
PWMFAULT3 PWMFAULT2 PWMFAULT1 PWMFAULT0
reserved RO 0 7 PWM7 RO 0 6 PWM6 RO 0
PWMEFLT PWMESYNC RO 0 5 PWM5 RO 0 RO 0 4 PWM4 RO 0 RO 0 3 PWM3 RO 0
reserved RO 0 2 PWM2 RO 0 RO 0 1 PWM1 RO 0 RO 0 0 PWM0 RO 0
RO 0 11
RO 0 10
RO 0 9
RO 0 8
RO 0
Bit/Field 31:28
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PWM Fault 3 Pin Present When set, indicates that the PWM Fault 3 pin is present.
27
PWMFAULT3
RO
0x0
26
PWMFAULT2
RO
0x0
PWM Fault 2 Pin Present When set, indicates that the PWM Fault 2 pin is present.
25
PWMFAULT1
RO
0x0
24
PWMFAULT0
RO
0x0
23:22
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PWM Extended Fault Active When set, indicates that the PWM Extended Fault feature is active.
21
PWMEFLT
RO
0x0
20
PWMESYNC
RO
0x0
PWM Extended SYNC Active When set, indicates that the PWM Extended SYNC feature is active.
19:8
reserved
RO
431
System Control
Bit/Field 7
Name PWM7
Type RO
Reset 0x0
Description PWM7 Pin Present When set, indicates that the PWM pin 7 is present.
PWM6
RO
0x0
PWM6 Pin Present When set, indicates that the PWM pin 6 is present.
PWM5
RO
0x0
PWM4
RO
0x0
PWM3
RO
0x0
PWM2
RO
0x0
PWM1
RO
0x0
PWM0
RO
0x0
April 25, 2012

This register is predefined by the part and can be used to verify features. If any bit is clear in this register, the module is not present. The corresponding bit in the RCGC0, SCGC0, and DCGC0 registers cannot be set. Important: This register is provided for legacy software support only. The USB Peripheral Properties (USBPP) register should be used to determine what features are available on the USB module. A read of this register correctly identifies if a legacy feature is present. Software must use the USBPP register to determine if a pin or feature that is not supported by the DCn registers is present.
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 USB0PHY RO 1 RO 0 3 reserved RO 0 RO 0 RO 0 RO 0 2 RO 0 1 USB0 RO 1 RO 0 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module 0 PHY Present When set, indicates that the USB module 0 PHY is present.
USB0PHY
RO
0x1
3:2
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB Module 0 Present This field indicates that USB module 0 is present and specifies its capability. sysValue Description 0x0 0x1 0x2 0x3 NA USB0 is not present. DEVICE USB0 is Device Only. HOST USB0 is Device or Host. OTG USB0 is OTG.
1:0
USB0
RO
0x1
433
System Control

This register is predefined by the part and can be used to verify DMA channel features. A 1 indicates the channel is available on this device; a 0 that the channel is only available on other devices in the family. Channels can have multiple assignments, see Channel Assignments on page 570 for more information. Important: This register is provided for legacy software support only. The DMACHANS bit field in the DMA Status (DMASTAT) register indicates the number of DMA channels.
Base 0x400F.E000 Offset 0x028 Type RO, reset 0xFFFF.FFFF
31
reserved
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
DMACH30 DMACH29 DMACH28 DMACH27 DMACH26 DMACH25 DMACH24 DMACH23 DMACH22 DMACH21 DMACH20 DMACH19 DMACH18 DMACH17 DMACH16 RO 1 14 RO 1 13 RO 1 12 RO 1 11 RO 1 10 RO 1 9 RO 1 8 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0
Type Reset
RO 1 15
DMACH15 DMACH14 DMACH13 DMACH12 DMACH11 DMACH10 DMACH9 DMACH8 DMACH7 DMACH6 DMACH5 DMACH4 DMACH3 DMACH2 DMACH1 DMACH0 Type Reset RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1
Bit/Field 31
Name reserved
Type RO
Reset 0x1
Description DMA Channel 31 When set, indicates DMA channel 31 is available.
30
DMACH30
RO
0x1
DMA Channel 30 When set, indicates DMA channel 30 is available.
29
DMACH29
RO
0x1
28
DMACH28
RO
0x1
27
DMACH27
RO
0x1
26
DMACH26
RO
0x1
25
DMACH25
RO
0x1
24
DMACH24
RO
0x1
23
DMACH23
RO
0x1
22
DMACH22
RO
0x1
April 25, 2012
Bit/Field 21
Name DMACH21
Type RO
Reset 0x1
20
DMACH20
RO
0x1
19
DMACH19
RO
0x1
18
DMACH18
RO
0x1
17
DMACH17
RO
0x1
16
DMACH16
RO
0x1
15
DMACH15
RO
0x1
14
DMACH14
RO
0x1
13
DMACH13
RO
0x1
12
DMACH12
RO
0x1
11
DMACH11
RO
0x1
10
DMACH10
RO
0x1
DMACH9
RO
0x1
DMACH8
RO
0x1
DMACH7
RO
0x1
DMACH6
RO
0x1
DMACH5
RO
0x1
DMACH4
RO
0x1
435
System Control
Bit/Field 3
Name DMACH3
Type RO
Reset 0x1
DMACH2
RO
0x1
DMACH1
RO
0x1
DMACH0
RO
0x1
April 25, 2012
Register 127: Device Capabilities 8 (DC8), offset 0x02C

This register is predefined by the part and can be used to verify features. Important: This register is provided for legacy software support only. The ADC Peripheral Properties (ADCPP) register should be used to determine how many input channels are available on the ADC module. A read of this register correctly identifies if legacy channels are present but software must use the ADCPP register to determine if a channel is present that is not supported by the DCn registers.
Base 0x400F.E000 Offset 0x02C Type RO, reset 0x0FFF.0FFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
ADC1AIN15 ADC1AIN14 ADC1AIN13 ADC1AIN12 ADC1AIN11 ADC1AIN10 ADC1AIN9 ADC1AIN8 ADC1AIN7 ADC1AIN6 ADC1AIN5 ADC1AIN4 ADC1AIN3 ADC1AIN2 ADC1AIN1 ADC1AIN0
Type Reset
RO 0 15
RO 0 14
RO 0 13
RO 0 12
RO 1 11
RO 1 10
RO 1 9
RO 1 8
RO 1 7
RO 1 6
RO 1 5
RO 1 4
RO 1 3
RO 1 2
RO 1 1
RO 1 0
ADC0AIN15 ADC0AIN14 ADC0AIN13 ADC0AIN12 ADC0AIN11 ADC0AIN10 ADC0AIN9 ADC0AIN8 ADC0AIN7 ADC0AIN6 ADC0AIN5 ADC0AIN4 ADC0AIN3 ADC0AIN2 ADC0AIN1 ADC0AIN0
Type Reset
RO 0
RO 0
RO 0
RO 0
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
RO 1
Bit/Field 31
Name ADC1AIN15
Type RO
Reset 0x0
Description ADC Module 1 AIN15 Pin Present When set, indicates that ADC module 1 input pin 15 is present.
30
ADC1AIN14
RO
0x0
ADC Module 1 AIN14 Pin Present When set, indicates that ADC module 1 input pin 14 is present.
29
ADC1AIN13
RO
0x0
28
ADC1AIN12
RO
0x0
27
ADC1AIN11
RO
0x1
26
ADC1AIN10
RO
0x1
25
ADC1AIN9
RO
0x1
24
ADC1AIN8
RO
0x1
23
ADC1AIN7
RO
0x1
22
ADC1AIN6
RO
0x1
437
System Control
Bit/Field 21
Name ADC1AIN5
Type RO
Reset 0x1
20
ADC1AIN4
RO
0x1
19
ADC1AIN3
RO
0x1
18
ADC1AIN2
RO
0x1
17
ADC1AIN1
RO
0x1
16
ADC1AIN0
RO
0x1
15
ADC0AIN15
RO
0x0
14
ADC0AIN14
RO
0x0
13
ADC0AIN13
RO
0x0
12
ADC0AIN12
RO
0x0
11
ADC0AIN11
RO
0x1
10
ADC0AIN10
RO
0x1
ADC0AIN9
RO
0x1
ADC0AIN8
RO
0x1
ADC0AIN7
RO
0x1
ADC0AIN6
RO
0x1
ADC0AIN5
RO
0x1
ADC0AIN4
RO
0x1
April 25, 2012
Bit/Field 3
Name ADC0AIN3
Type RO
Reset 0x1
ADC0AIN2
RO
0x1
ADC0AIN1
RO
0x1
ADC0AIN0
RO
0x1
439
System Control
Register 128: Software Reset Control 0 (SRCR0), offset 0x040

This register allows individual modules to be reset. Writes to this register are masked by the bits in the Device Capabilities 1 (DC1) register. Important: This register is provided for legacy software support only. The peripheral-specific Software Reset registers (such as SRWD) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this legacy register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Watchdog 1), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Software Reset Control 0 (SRCR0)
31 30 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 29 28 WDT1 RO 0 12 RO 0 11 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 27 26 reserved RO 0 10 RO 0 9 25 24 CAN0 RO 0 8 RO 0 7 RO 0 6 HIB RO 0 23 22 21 20 19 18 17 ADC1 RO 0 3 WDT0 RO 0 RO 0 RO 0 2 RO 0 1 reserved RO 0 RO 0 16 ADC0 RO 0 0
reserved RO 0 5 reserved RO 0 RO 0 RO 0 4
Bit/Field 31:29
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT1 Reset Control When this bit is set, Watchdog Timer module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
28
WDT1
RO
0x0
27:25
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN0 Reset Control When this bit is set, CAN module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
24
CAN0
RO
0x0
23:18
reserved
RO
April 25, 2012
Bit/Field 17
Name ADC1
Type RO
Reset 0x0
Description ADC1 Reset Control When this bit is set, ADC module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
16
ADC0
RO
0x0
ADC0 Reset Control When this bit is set, ADC module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
15:7
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. HIB Reset Control When this bit is set, the Hibernation module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
HIB
RO
0x0
5:4
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT0 Reset Control When this bit is set, Watchdog Timer module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
WDT0
RO
0x0
2:0
reserved
RO
441
System Control

This register allows individual modules to be reset. Writes to this register are masked by the bits in the Device Capabilities 2 (DC2) register. Important: This register is provided for legacy software support only. The peripheral-specific Software Reset registers (such as SRTIMER) should be used to reset specific peripherals. A write to this register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as TIMER0), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information. Note that the Software Reset Analog Comparator (SRACMP) register has only one bit to set the analog comparator module. Resetting the module resets all the blocks. If any of the COMPn bits are set, the entire analog comparator module is reset. It is not possible to reset the blocks individually.
31 30 29 28 27 26 25 COMP1 RO 0 11 RO 0 10 RO 0 9 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 24 COMP0 RO 0 8 RO 0 7 23 22 21 20 19 TIMER3 RO 0 4 SSI0 RO 0 RO 0 3
reserved

reserved
reserved RO 0 6 RO 0 5 SSI1 RO 0
RO 0 14 I2C1 RO 0
RO 0 13
reserved
RO 0 12 I2C0 RO 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31:26
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comp 1 Reset Control When this bit is set, Analog Comparator module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
25
COMP1
RO
0x0
24
COMP0
RO
0x0
Analog Comp 0 Reset Control When this bit is set, Analog Comparator module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
23:20
reserved
RO
April 25, 2012
Bit/Field 19
Name TIMER3
Type RO
Reset 0x0
Description Timer 3 Reset Control Timer 3 Reset Control. When this bit is set, General-Purpose Timer module 3 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
18
TIMER2
RO
0x0
Timer 2 Reset Control When this bit is set, General-Purpose Timer module 2 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
17
TIMER1
RO
0x0
16
TIMER0
RO
0x0
15
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C1 Reset Control When this bit is set, I2C module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
14
I2C1
RO
0x0
13
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C0 Reset Control When this bit is set, I2C module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
12
I2C0
RO
0x0
11:6
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI1 Reset Control When this bit is set, SSI module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
SSI1
RO
0x0
SSI0
RO
0x0
SSI0 Reset Control When this bit is set, SSI module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
reserved
RO
443
System Control
Bit/Field 2
Name UART2
Type RO
Reset 0x0
Description UART2 Reset Control When this bit is set, UART module 2 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
UART1
RO
0x0
UART1 Reset Control When this bit is set, UART module 1 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
UART0
RO
0x0
UART0 Reset Control When this bit is set, UART module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
April 25, 2012

This register allows individual modules to be reset. Writes to this register are masked by the bits in the Device Capabilities 4 (DC4) register. Important: This register is provided for legacy software support only. The peripheral-specific Software Reset registers (such as SRDMA) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as the DMA), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 UDMA RO 0 RO 0 RO 0 RO 0 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 GPIOF RO 0 RO 0 4 GPIOE RO 0 RO 0 3 GPIOD RO 0 RO 0 2 GPIOC RO 0 RO 0 1 GPIOB RO 0 23 22 21 20 19 18 17 16 USB0 RO 0 0 GPIOA RO 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB0 Reset Control When this bit is set, USB module 0 is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
16
USB0
RO
0x0
15:14
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Micro-DMA Reset Control When this bit is set, uDMA module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
13
UDMA
RO
0x0
12:6
reserved
RO
445
System Control
Bit/Field 5
Name GPIOF
Type RO
Reset 0x0
Description Port F Reset Control When this bit is set, Port F module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
GPIOE
RO
0x0
Port E Reset Control When this bit is set, Port E module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
GPIOD
RO
0x0
Port D Reset Control When this bit is set, Port D module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
GPIOC
RO
0x0
Port C Reset Control When this bit is set, Port C module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
GPIOB
RO
0x0
Port B Reset Control When this bit is set, Port B module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
GPIOA
RO
0x0
Port A Reset Control When this bit is set, Port A module is reset. All internal data is lost and the registers are returned to their reset states. This bit must be manually cleared after being set.
April 25, 2012
Register 131: Run Mode Clock Gating Control Register 0 (RCGC0), offset 0x100
This register controls the clock gating logic in normal Run mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC0 is the clock configuration register for running operation, SCGC0 for Sleep operation, and DCGC0 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Note that there must be a delay of 3 system clocks after a module clock is enabled before any registers in that module are accessed. Important: This register is provided for legacy software support only. The peripheral-specific Run Mode Clock Gating Control registers (such as RCGCWD) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Watchdog 1), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information. Likewise, the ADC Peripheral Configuration (ADCPC) register should be used to configure the ADC sample rate. However, to support legacy software, the MAXADCnSPD fields are available. A write to these legacy fields also writes the corresponding field in the peripheral-specific register. If a field is changed by writing to this register, it can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support rates that are not available in this register. If software uses a peripheral-specific register to set the ADC rate, the write causes proper operation, but the value of that field is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
447
System Control
Run Mode Clock Gating Control Register 0 (RCGC0)

31 30 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 29 28 WDT1 RO 0 12 RO 0 11 27 26 reserved RO 0 10 RO 0 9 25 24 CAN0 RO 0 8 RO 0 7
reserved
23
22
21
20
19
18
17 ADC1
16 ADC0 RO 0 0
reserved RO 0 6 HIB RO 1 RO 0 5 reserved RO 0 RO 0 RO 0 4 RO 0 3 WDT0 RO 0 RO 0 RO 0 2
RO 0 1 reserved RO 0
RO 0
RO 0
Bit/Field 31:29
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT1 Clock Gating Control This bit controls the clock gating for the Watchdog Timer module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
28
WDT1
RO
0x0
27:25
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN0 Clock Gating Control This bit controls the clock gating for CAN module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
24
CAN0
RO
0x0
23:18
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC1 Clock Gating Control This bit controls the clock gating for SAR ADC module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
17
ADC1
RO
0x0
16
ADC0
RO
0x0
ADC0 Clock Gating Control This bit controls the clock gating for ADC module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
15:12
reserved
RO
April 25, 2012
Bit/Field 11:10
Name MAXADC1SPD
Type RO
Reset 0x0
Description ADC1 Sample Speed This field sets the rate at which ADC module 1 samples data. You cannot set the rate higher than the maximum rate. You can set the sample rate by setting the MAXADC1SPD bit as follows (all other encodings are reserved): Value Description 0x3 0x2 0x1 0x0 1M samples/second 500K samples/second 250K samples/second 125K samples/second
9:8
MAXADC0SPD
RO
0x0
ADC0 Sample Speed This field sets the rate at which ADC0 samples data. You cannot set the rate higher than the maximum rate. You can set the sample rate by setting the MAXADC0SPD bit as follows (all other encodings are reserved): Value Description 0x3 0x2 0x1 0x0 1M samples/second 500K samples/second 250K samples/second 125K samples/second
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. HIB Clock Gating Control This bit controls the clock gating for the Hibernation module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
HIB
RO
0x1
5:4
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT0 Clock Gating Control This bit controls the clock gating for the Watchdog Timer module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
WDT0
RO
0x0
2:0
reserved
RO
449
System Control
This register controls the clock gating logic in normal Run mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC1 is the clock configuration register for running operation, SCGC1 for Sleep operation, and DCGC1 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Note that there must be a delay of 3 system clocks after a module clock is enabled before any registers in that module are accessed. Important: This register is provided for legacy software support only. The peripheral-specific Run Mode Clock Gating Control registers (such as RCGCTIMER) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
reserved

reserved
RO 0 14 I2C1 RO 0
RO 0 13
reserved
RO 0 12 I2C0 RO 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31:26
Name reserved
Type RO
Reset 0
April 25, 2012
Bit/Field 25
Name COMP1
Type RO
Reset 0x0
Description Analog Comparator 1 Clock Gating This bit controls the clock gating for analog comparator 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
24
COMP0
RO
0x0
Analog Comparator 0 Clock Gating This bit controls the clock gating for analog comparator 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
23:20
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Timer 3 Clock Gating Control This bit controls the clock gating for General-Purpose Timer module 3. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
19
TIMER3
RO
0x0
18
TIMER2
RO
0x0
Timer 2 Clock Gating Control This bit controls the clock gating for General-Purpose Timer module 2. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
17
TIMER1
RO
0x0
16
TIMER0
RO
0x0
15
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C1 Clock Gating Control This bit controls the clock gating for I2C module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
14
I2C1
RO
0x0
13
reserved
RO
451
System Control
Bit/Field 12
Name I2C0
Type RO
Reset 0x0
Description I2C0 Clock Gating Control This bit controls the clock gating for I2C module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
11:6
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI1 Clock Gating Control This bit controls the clock gating for SSI module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
SSI1
RO
0x0
SSI0
RO
0x0
SSI0 Clock Gating Control This bit controls the clock gating for SSI module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART2 Clock Gating Control This bit controls the clock gating for UART module 2. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
UART2
RO
0x0
UART1
RO
0x0
UART1 Clock Gating Control This bit controls the clock gating for UART module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
UART0
RO
0x0
April 25, 2012
This register controls the clock gating logic in normal Run mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC2 is the clock configuration register for running operation, SCGC2 for Sleep operation, and DCGC2 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Note that there must be a delay of 3 system clocks after a module clock is enabled before any registers in that module are accessed. Important: This register is provided for legacy software support only. The peripheral-specific Run Mode Clock Gating Control registers (such as RCGCDMA) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as the DMA), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Bit/Field 31:17
Name reserved
Type RO
Reset 0
453
System Control
Bit/Field 16
Name USB0
Type RO
Reset 0x0
Description USB0 Clock Gating Control This bit controls the clock gating for USB module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
15:14
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Micro-DMA Clock Gating Control This bit controls the clock gating for micro-DMA. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
13
UDMA
RO
0x0
12:6
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Port F Clock Gating Control This bit controls the clock gating for Port F. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
GPIOF
RO
0x0
GPIOE
RO
0x0
Port E Clock Gating Control Port E Clock Gating Control. This bit controls the clock gating for Port E. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
GPIOD
RO
0x0
Port D Clock Gating Control Port D Clock Gating Control. This bit controls the clock gating for Port D. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
GPIOC
RO
0x0
Port C Clock Gating Control This bit controls the clock gating for Port C. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
GPIOB
RO
0x0
Port B Clock Gating Control This bit controls the clock gating for Port B. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
GPIOA
RO
0x0
Port A Clock Gating Control This bit controls the clock gating for Port A. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
April 25, 2012
Register 134: Sleep Mode Clock Gating Control Register 0 (SCGC0), offset 0x110
This register controls the clock gating logic in Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC0 is the clock configuration register for running operation, SCGC0 for Sleep operation, and DCGC0 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Sleep Mode Clock Gating Control registers (such as SCGCWD) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Watchdog 1), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Sleep Mode Clock Gating Control Register 0 (SCGC0)
Bit/Field 31:29
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT1 Clock Gating Control This bit controls the clock gating for Watchdog Timer module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
28
WDT1
RO
0x0
455
System Control
Bit/Field 27:25
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN0 Clock Gating Control This bit controls the clock gating for CAN module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
24
CAN0
RO
0x0
23:18
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC1 Clock Gating Control This bit controls the clock gating for ADC module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
17
ADC1
RO
0x0
16
ADC0
RO
0x0
15:7
reserved
RO
HIB
RO
0x1
5:4
reserved
RO
WDT0
RO
0x0
2:0
reserved
RO
April 25, 2012
This register controls the clock gating logic in Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC1 is the clock configuration register for running operation, SCGC1 for Sleep operation, and DCGC1 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Sleep Mode Clock Gating Control registers (such as SCGCTIMER) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
reserved

reserved
RO 0 14 I2C1 RO 0
RO 0 13
reserved
RO 0 12 I2C0 RO 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31:26
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator 1 Clock Gating This bit controls the clock gating for analog comparator 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
25
COMP1
RO
0x0
457
System Control
Bit/Field 24
Name COMP0
Type RO
Reset 0x0
23:20
reserved
RO
19
TIMER3
RO
0x0
18
TIMER2
RO
0x0
17
TIMER1
RO
0x0
16
TIMER0
RO
0x0
15
reserved
RO
14
I2C1
RO
0x0
13
reserved
RO
12
I2C0
RO
0x0
11:6
reserved
RO
April 25, 2012
Bit/Field 5
Name SSI1
Type RO
Reset 0x0
Description SSI1 Clock Gating Control This bit controls the clock gating for SSI module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
SSI0
RO
0x0
reserved
RO
UART2
RO
0x0
UART1
RO
0x0
UART0
RO
0x0
459
System Control
This register controls the clock gating logic in Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC2 is the clock configuration register for running operation, SCGC2 for Sleep operation, and DCGC2 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Sleep Mode Clock Gating Control registers (such as SCGCDMA) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as the DMA), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Bit/Field 31:17
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB0 Clock Gating Control This bit controls the clock gating for USB module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
16
USB0
RO
0x0
April 25, 2012
Bit/Field 15:14
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Micro-DMA Clock Gating Control This bit controls the clock gating for micro-DMA. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
13
UDMA
RO
0x0
12:6
reserved
RO
GPIOF
RO
0x0
GPIOE
RO
0x0
GPIOD
RO
0x0
GPIOC
RO
0x0
GPIOB
RO
0x0
GPIOA
RO
0x0
461
System Control
Register 137: Deep Sleep Mode Clock Gating Control Register 0 (DCGC0), offset 0x120
This register controls the clock gating logic in Deep-Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC0 is the clock configuration register for running operation, SCGC0 for Sleep operation, and DCGC0 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Deep Sleep Mode Clock Gating Control registers (such as DCGCWD) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Watchdog 1), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Deep Sleep Mode Clock Gating Control Register 0 (DCGC0)
Bit/Field 31:29
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT1 Clock Gating Control This bit controls the clock gating for the Watchdog Timer module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
28
WDT1
RO
0x0
April 25, 2012
Bit/Field 27:25
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. CAN0 Clock Gating Control This bit controls the clock gating for CAN module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
24
CAN0
RO
0x0
23:18
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC1 Clock Gating Control This bit controls the clock gating for ADC module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
17
ADC1
RO
0x0
16
ADC0
RO
0x0
15:7
reserved
RO
HIB
RO
0x1
5:4
reserved
RO
WDT0
RO
0x0
2:0
reserved
RO
463
System Control
Register 138: Deep-Sleep Mode Clock Gating Control Register 1 (DCGC1), offset 0x124
This register controls the clock gating logic in Deep-Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC1 is the clock configuration register for running operation, SCGC1 for Sleep operation, and DCGC1 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Deep Sleep Mode Clock Gating Control registers (such as DCGCTIMER) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as Timer 0), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Deep-Sleep Mode Clock Gating Control Register 1 (DCGC1)
reserved

reserved
RO 0 14 I2C1 RO 0
RO 0 13
reserved
RO 0 12 I2C0 RO 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31:26
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Analog Comparator 1 Clock Gating This bit controls the clock gating for analog comparator 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
25
COMP1
RO
0x0
April 25, 2012
Bit/Field 24
Name COMP0
Type RO
Reset 0x0
23:20
reserved
RO
19
TIMER3
RO
0x0
18
TIMER2
RO
0x0
17
TIMER1
RO
0x0
16
TIMER0
RO
0x0
15
reserved
RO
14
I2C1
RO
0x0
13
reserved
RO
12
I2C0
RO
0x0
11:6
reserved
RO
465
System Control
Bit/Field 5
Name SSI1
Type RO
Reset 0x0
Description SSI1 Clock Gating Control This bit controls the clock gating for SSI module 1. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
SSI0
RO
0x0
reserved
RO
UART2
RO
0x0
UART1
RO
0x0
UART0
RO
0x0
April 25, 2012
Register 139: Deep Sleep Mode Clock Gating Control Register 2 (DCGC2), offset 0x128
This register controls the clock gating logic in Deep-Sleep mode. Each bit controls a clock enable for a given interface, function, or module. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled (saving power). If the module is unclocked, reads or writes to the module generate a bus fault. The reset state of these bits is 0 (unclocked) unless otherwise noted, so that all functional modules are disabled. It is the responsibility of software to enable the ports necessary for the application. Note that these registers may contain more bits than there are interfaces, functions, or modules to control. This configuration is implemented to assure reasonable code compatibility with other family and future parts. RCGC2 is the clock configuration register for running operation, SCGC2 for Sleep operation, and DCGC2 for Deep-Sleep operation. Setting the ACG bit in the Run-Mode Clock Configuration (RCC) register specifies that the system uses sleep modes. Important: This register is provided for legacy software support only. The peripheral-specific Deep Sleep Mode Clock Gating Control registers (such as DCGCDMA) should be used to reset specific peripherals. A write to this legacy register also writes the corresponding bit in the peripheral-specific register. Any bits that are changed by writing to this register can be read back correctly with a read of this register. Software must use the peripheral-specific registers to support modules that are not present in the legacy registers. If software uses a peripheral-specific register to write a legacy peripheral (such as the DMA), the write causes proper operation, but the value of that bit is not reflected in this register. If software uses both legacy and peripheral-specific register accesses, the peripheral-specific registers must be accessed by read-modify-write operations that affect only peripherals that are not present in the legacy registers. In this manner, both the peripheral-specific and legacy registers have coherent information.
Deep Sleep Mode Clock Gating Control Register 2 (DCGC2)
Bit/Field 31:17
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. USB0 Clock Gating Control This bit controls the clock gating for USB module 0. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
16
USB0
RO
0x0
467
System Control
Bit/Field 15:14
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Micro-DMA Clock Gating Control This bit controls the clock gating for micro-DMA. If set, the module receives a clock and functions. Otherwise, the module is unclocked and disabled. If the module is unclocked, a read or write to the module generates a bus fault.
13
UDMA
RO
0x0
12:6
reserved
RO
GPIOF
RO
0x0
GPIOE
RO
0x0
GPIOD
RO
0x0
GPIOC
RO
0x0
GPIOB
RO
0x0
GPIOA
RO
0x0
April 25, 2012

This register is predefined by the part and can be used to verify ADC digital comparator features. Important: This register is provided for legacy software support only. The ADC Peripheral Properties (ADCPP) register should be used to determine how many digital comparators are available on the ADC module. A read of this register correctly identifies if legacy comparators are present. Software must use the ADCPP register to determine if a comparator that is not supported by the DCn registers is present.
Base 0x400F.E000 Offset 0x190 Type RO, reset 0x00FF.00FF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8
ADC1DC7 ADC1DC6 ADC1DC5 ADC1DC4 ADC1DC3 ADC1DC2 ADC1DC1 ADC1DC0 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0
ADC0DC7 ADC0DC6 ADC0DC5 ADC0DC4 ADC0DC3 ADC0DC2 ADC0DC1 ADC0DC0 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1
Bit/Field 31:24
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC1 DC7 Present When set, indicates that ADC module 1 Digital Comparator 7 is present.
23
ADC1DC7
RO
0x1
22
ADC1DC6
RO
0x1
ADC1 DC6 Present When set, indicates that ADC module 1 Digital Comparator 6 is present.
21
ADC1DC5
RO
0x1
20
ADC1DC4
RO
0x1
19
ADC1DC3
RO
0x1
18
ADC1DC2
RO
0x1
17
ADC1DC1
RO
0x1
16
ADC1DC0
RO
0x1
469
System Control
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC0 DC7 Present When set, indicates that ADC module 0 Digital Comparator 7 is present.
ADC0DC7
RO
0x1
ADC0DC6
RO
0x1
ADC0DC5
RO
0x1
ADC0DC4
RO
0x1
ADC0DC3
RO
0x1
ADC0DC2
RO
0x1
ADC0DC1
RO
0x1
ADC0DC0
RO
0x1
April 25, 2012
Register 141: Non-Volatile Memory Information (NVMSTAT), offset 0x1A0

This register is predefined by the part and can be used to verify features. Important: This register is provided for legacy software support only. The ROM Third-Party Software (ROMSWMAP) register should be used to determine the presence of third-party software in the on-chip ROM on this microcontroller. A read of the TPSW bit in this register correctly identifies the presence of legacy third-party software. Software should use the ROMSWMAP register for software that is not on legacy devices.
Non-Volatile Memory Information (NVMSTAT)
Base 0x400F.E000 Offset 0x1A0 Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 FWB RO 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32 Word Flash Write Buffer Available When set, indicates that the 32 word Flash memory write buffer feature is available.
FWB
RO
0x1
471
System Exception Module

This module is an AHB peripheral that handles system-level Cortex-M4 FPU exceptions. For functions with registers mapped into this aperture; if the function is not available on a device, then all writes to the associated registers are ignored and reads return zeros.
6.1
The System Exception module provides control and status of the system-level interrupts. All the interrupt events are ORed together before being sent to the interrupt controller, so the System Exception module can only generate a single interrupt request to the controller at any given time. Software can service multiple interrupt events in a single interrupt service routine by reading the System Exception Masked Interrupt Status (SYSEXCMIS) register. The interrupt events that can trigger a controller-level interrupt are defined in the System Exception Interrupt Mask (SYSEXCIM) register by setting the corresponding interrupt mask bits. If interrupts are not used, the raw interrupt status is always visible via the System Exception Raw Interrupt Status (SYSEXCRIS) register. Interrupts are always cleared (for both the SYSEXCMIS and SYSEXCRIS registers) by writing a 1 to the corresponding bit in the System Exception Interrupt Clear (SYSEXCIC) register.
6.2
Register Map
Table 6-1 on page 472 lists the System Exception module registers. The offset listed is a hexadecimal increment to the register's address, relative to the System Exception base address of 0x400F.9000. Note: Spaces in the System Exception register space that are not used are reserved for future or internal use. Software should not modify any reserved memory address.
Table 6-1. System Exception Register Map

Offset 0x000 0x004 0x008 0x00C Name SYSEXCRIS SYSEXCIM SYSEXCMIS SYSEXCIC Type RO R/W RO W1C Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description System Exception Raw Interrupt Status System Exception Interrupt Mask System Exception Masked Interrupt Status System Exception Interrupt Clear See page 473 475 477 479
6.3
All addresses given are relative to the System Exception base address of 0x400F.9000.
April 25, 2012
Register 1: System Exception Raw Interrupt Status (SYSEXCRIS), offset 0x000

The SYSEXCRIS register is the raw interrupt status register. On a read, this register gives the current raw status value of the corresponding interrupt. A write has no effect.
System Exception Raw Interrupt Status (SYSEXCRIS)
Base 0x400F.9000 Offset 0x000 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5

FPIXCRIS
RO 0 4
RO 0 3
RO 0 2
FPIOCRIS
RO 0 1
FPDZCRIS
RO 0 0
FPIDCRIS
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
FPOFCRIS FPUFCRIS
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Floating-Point Inexact Exception Raw Interrupt Status Value Description 0 1 No interrupt A floating-point inexact exception has occurred.
FPIXCRIS
RO
This bit is cleared by writing a 1 to the IXCIC bit in the SYSEXCIC register. 4 FPOFCRIS RO 0 Floating-Point Overflow Exception Raw Interrupt Status Value Description 0 1 No interrupt A floating-point overflow exception has occurred.
This bit is cleared by writing a 1 to the OFCIC bit in the SYSEXCIC register. 3 FPUFCRIS RO 0 Floating-Point Underflow Exception Raw Interrupt Status Value Description 0 1 No interrupt A floating-point underflow exception has occurred.
This bit is cleared by writing a 1 to the UFCIC bit in the SYSEXCIC register.
473
Bit/Field 2
Name FPIOCRIS
Type RO
Reset 0
Description Floating-Point Invalid Operation Raw Interrupt Status Value Description 0 1 No interrupt A floating-point invalid operation exception has occurred.
This bit is cleared by writing a 1 to the IOCIC bit in the SYSEXCIC register. 1 FPDZCRIS RO 0 Floating-Point Divide By 0 Exception Raw Interrupt Status Value Description 0 1 No interrupt A floating-point divide by 0 exception has occurred.
This bit is cleared by writing a 1 to the DZCIC bit in the SYSEXCIC register. 0 FPIDCRIS RO 0 Floating-Point Input Denormal Exception Raw Interrupt Status Value Description 0 1 No interrupt A floating-point input denormal exception has occurred.
This bit is cleared by writing a 1 to the IDCIC bit in the SYSEXCIC register.
April 25, 2012
Register 2: System Exception Interrupt Mask (SYSEXCIM), offset 0x004

The SYSEXCIM register is the interrupt mask set/clear register. On a read, this register gives the current value of the mask on the relevant interrupt. Setting a bit allows the corresponding raw interrupt signal to be routed to the interrupt controller. Clearing a bit prevents the raw interrupt signal from being sent to the interrupt controller.
System Exception Interrupt Mask (SYSEXCIM)
Base 0x400F.9000 Offset 0x004 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0
reserved Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
FPIXCIM FPOFCIM FPUFCIM FPIOCIM FPDZCIM FPIDCIM R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:6
Name reserved
Type R/W
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Floating-Point Inexact Exception Interrupt Mask Value Description 0 1 The FPIXCRIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPISCRIS bit in the SYSEXCRIS register is set.
FPIXCIM
R/W
FPOFCIM
R/W
Floating-Point Overflow Exception Interrupt Mask Value Description 0 1 The FPOFCIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPOFCRIS bit in the SYSEXCRIS register is set.
FPUFCIM
R/W
Floating-Point Underflow Exception Interrupt Mask Value Description 0 1 The FPUFCRIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPUFCRIS bit in the SYSEXCRIS register is set.
475
Bit/Field 2
Name FPIOCIM
Type R/W
Reset 0
Description Floating-Point Invalid Operation Interrupt Mask Value Description 0 1 The FPIOCRIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPIOCRIS bit in the SYSEXCRIS register is set.
FPDZCIM
R/W
Floating-Point Divide By 0 Exception Interrupt Mask Value Description 0 1 The FPDZCRIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPDZCRIS bit in the SYSEXCRIS register is set.
FPIDCIM
R/W
Floating-Point Input Denormal Exception Interrupt Mask Value Description 0 1 The FPIDCRIS interrupt is suppressed and not sent to the interrupt controller. An interrupt is sent to the interrupt controller when the FPIDCRIS bit in the SYSEXCRIS register is set.
April 25, 2012
Register 3: System Exception Masked Interrupt Status (SYSEXCMIS), offset 0x008

The SYSEXCMIS register is the masked interrupt status register. On a read, this register gives the current masked status value of the corresponding interrupt. A write has no effect.
System Exception Masked Interrupt Status (SYSEXCMIS)
Base 0x400F.9000 Offset 0x008 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
FPIXCMIS FPOFCMIS FPUFCMIS FPIOCMIS FPDZCMIS FPIDCMIS
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Floating-Point Inexact Exception Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to an inexact exception.
FPIXCMIS
RO
This bit is cleared by writing a 1 to the FPIXCIC bit in the SYSEXCIC register. 4 FPOFCMIS RO 0 Floating-Point Overflow Exception Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to an overflow exception.
This bit is cleared by writing a 1 to the FPOFCIC bit in the SYSEXCIC register. 3 FPUFCMIS RO 0 Floating-Point Underflow Exception Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to an underflow exception.
This bit is cleared by writing a 1 to the FPUFCIC bit in the SYSEXCIC register.
477
Bit/Field 2
Name FPIOCMIS
Type RO
Reset 0
Description Floating-Point Invalid Operation Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to an invalid operation.
This bit is cleared by writing a 1 to the FPIOCIC bit in the SYSEXCIC register. 1 FPDZCMIS RO 0 Floating-Point Divide By 0 Exception Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to a divide by 0 exception.
This bit is cleared by writing a 1 to the FPDZCIC bit in the SYSEXCIC register. 0 FPIDCMIS RO 0 Floating-Point Input Denormal Exception Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to an input denormal exception.
This bit is cleared by writing a 1 to the FPIDCIC bit in the SYSEXCIC register.
April 25, 2012
Register 4: System Exception Interrupt Clear (SYSEXCIC), offset 0x00C

The SYSEXCIC register is the interrupt clear register. On a write of 1, the corresponding interrupt (both raw interrupt and masked interrupt, if enabled) is cleared. A write of 0 has no effect.
System Exception Interrupt Clear (SYSEXCIC)
Base 0x400F.9000 Offset 0x00C Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset W1C 0 15 W1C 0 14 W1C 0 13 W1C 0 12 W1C 0 11 W1C 0 10 W1C 0 9 W1C 0 8 W1C 0 7 W1C 0 6 W1C 0 5 W1C 0 4 W1C 0 3 W1C 0 2 W1C 0 1 W1C 0 0
reserved Type Reset W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0
FPIXCIC FPOFCIC FPUFCIC FPIOCIC FPDZCIC FPIDCIC W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0
Bit/Field 31:6
Name reserved
Type W1C
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Floating-Point Inexact Exception Interrupt Clear Writing a 1 to this bit clears the FPIXCRIS bit in the SYSEXCRIS register and the FPIXCMIS bit in the SYSEXCMIS register.
FPIXCIC
W1C
FPOFCIC
W1C
Floating-Point Overflow Exception Interrupt Clear Writing a 1 to this bit clears the FPOFCRIS bit in the SYSEXCRIS register and the FPOFCMIS bit in the SYSEXCMIS register.
FPUFCIC
W1C
Floating-Point Underflow Exception Interrupt Clear Writing a 1 to this bit clears the FPUFCRIS bit in the SYSEXCRIS register and the FPUFCMIS bit in the SYSEXCMIS register.
FPIOCIC
W1C
Floating-Point Invalid Operation Interrupt Clear Writing a 1 to this bit clears the FPIOCRIS bit in the SYSEXCRIS register and the FPIOCMIS bit in the SYSEXCMIS register.
FPDZCIC
W1C
Floating-Point Divide By 0 Exception Interrupt Clear Writing a 1 to this bit clears the FPDZCRIS bit in the SYSEXCRIS register and the FPDZCMIS bit in the SYSEXCMIS register.
FPIDCIC
W1C
Floating-Point Input Denormal Exception Interrupt Clear Writing a 1 to this bit clears the FPIDCRIS bit in the SYSEXCRIS register and the FPIDCMIS bit in the SYSEXCMIS register.
479
Hibernation Module
Hibernation Module
The Hibernation Module manages removal and restoration of power to provide a means for reducing power consumption. When the processor and peripherals are idle, power can be completely removed with only the Hibernation module remaining powered. Power can be restored based on an external signal or at a certain time using the built-in Real-Time Clock (RTC). The Hibernation module can be independently supplied from a battery or an auxiliary power supply. The Hibernation module has the following features: 32-bit real-time seconds counter (RTC) with 1/32,768 second resolution 32-bit RTC seconds match register and 15-bit sub seconds match for timed wake-up and interrupt generation with 1/32,768 second resolution RTC predivider trim for making fine adjustments to the clock rate Two mechanisms for power control System power control using discrete external regulator On-chip power control using internal switches under register control Dedicated pin for waking using an external signal RTC operational and hibernation memory valid as long as VBAT is valid Low-battery detection, signaling, and interrupt generation, with optional wake on low battery GPIO pin state can be retained during hibernation Clock source from a 32.768-kHz external crystal or oscillator 16 32-bit words of battery-backed memory to save state during hibernation Programmable interrupts for RTC match, external wake, and low battery events
April 25, 2012
7.1
Block Diagram
Figure 7-1. Hibernation Module Block Diagram
HIBCTL.CLK32EN XOSC0 XOSC1 Pre-Divider HIBRTCT Interrupts HIBIM HIBRIS HIBMIS HIBIC MATCH Clock Source for System Clock Interrupts to CPU
Battery-Backed Memory 16 words HIBDATA WAKE
RTC HIBRTCC HIBRTCLD HIBRTCM0 HIBRTCSS HIBCTL.RTCEN
LOWBAT Power Sequence Logic
VBAT
Low Battery Detect
HIB
HIBCTL.VBATSEL HIBCTL.BATCHK
HIBCTL.RTCWEN HIBCTL.EXTWEN HIBCTL.VABORT HIBCTL.HIBREQ HIBCTL.BATWKEN
7.2
Signal Description
The following table lists the external signals of the Hibernation module and describes the function of each.
Table 7-1. Hibernate Signals (64LQFP)

Pin Name GNDX Pin Number Pin Mux / Pin Assignment 35 fixed Pin Type Buffer Type Power
a
Description GND for the Hibernation oscillator. When using a crystal clock source, this pin should only be connected to the crystal load capacitors to improve oscillator immunity to system noise. When using an external oscillator, this pin should be connected to GND. An output that indicates the processor is in Hibernate mode. Power source for the Hibernation module. It is normally connected to the positive terminal of a battery and serves as the battery backup/Hibernation module power-source supply. An external input that brings the processor out of Hibernate mode when asserted.
HIB VBAT
33 37
fixed fixed
O -
TTL Power
WAKE
32
fixed
TTL
481
Hibernation Module
Table 7-1. Hibernate Signals (64LQFP) (continued)

Pin Name XOSC0 Pin Number Pin Mux / Pin Assignment 34 fixed Pin Type I Buffer Type Analog
a
Description Hibernation module oscillator crystal input or an external clock reference input. Note that this is either a 32.768-kHz crystal or a 32.768-kHz oscillator for the Hibernation module RTC. Hibernation module oscillator crystal output. Leave unconnected when using a single-ended clock source.
XOSC1
36
fixed
Analog
7.3
The Hibernation module provides two mechanisms for power control: The first mechanism controls the power to the microcontroller with a control signal (HIB) that signals an external voltage regulator to turn on or off. The second mechanism uses internal switches to control power to the Cortex-M4F as well as to most analog and digital functions while retaining I/O pin power (VDD3ON mode). The Hibernation module power source is determined dynamically. The supply voltage of the Hibernation module is the larger of the main voltage source (VDD) or the battery/auxilliary voltage source (VBAT). The Hibernation module also has an independent clock source to maintain a real-time clock (RTC) when the system clock is powered down. Hibernate mode can be entered through one of two ways: The user initiates hibernation by setting the HIBREQ bit in the Hibernation Control (HIBCTL) register Power is arbitrarily removed from VDD while a valid VBAT is applied Once in hibernation, the module signals an external voltage regulator to turn the power back on when an external pin (WAKE) is asserted or when the internal RTC reaches a certain value. The Hibernation module can also detect when the battery voltage is low and optionally prevent hibernation or wake from hibernation when this occurs. When waking from hibernation, the HIB signal is deasserted. The return of VDD causes a POR to be executed. The time from when the WAKE signal is asserted to when code begins execution is equal to the wake-up time (tWAKE_TO_HIB) plus the power-on reset time (TPOR).
7.3.1
Register Access Timing

Because the Hibernation module has an independent clocking domain, hibernation registers must be written only with a timing gap between accesses. The delay time is tHIB_REG_ACCESS, therefore software must guarantee that this delay is inserted between back-to-back writes to Hibernation registers or between a write followed by a read. The WC interrupt in the HIBMIS register can be used to notify the application when the Hibernation modules registers can be accessed. Alternatively, software may make use of the WRC bit in the Hibernation Control (HIBCTL) register to ensure that the required timing gap has elapsed. This bit is cleared on a write operation and set once the write completes, indicating to software that another write or read may be started safely. Software should poll HIBCTL for WRC=1 prior to accessing any hibernation register.
April 25, 2012
Back-to-back reads from Hibernation module registers have no timing restrictions. Reads are performed at the full peripheral clock rate.
7.3.2
Hibernation Clock Source

In systems where the Hibernation module is used to put the microcontroller into hibernation, the module must be clocked by an external source that is independent from the main system clock, even if the RTC feature is not used. An external oscillator or crystal is used for this purpose. To use a crystal, a 32.768-kHz crystal is connected to the XOSC0 and XOSC1 pins. Alternatively, a 32.768-kHz oscillator can be connected to the XOSC0 pin, leaving XOSC1 unconnected. Care must be taken that the voltage amplitude of the 32.768-kHz oscillator is less than VBAT, otherwise, the Hibernation module may draw power from the oscillator and not VBAT during hibernation. See Figure 7-2 on page 483 and Figure 7-3 on page 484. The Hibernation clock source is enabled by setting the CLK32EN bit of the HIBCTL register. The CLK32EN bit must be set before accessing any other Hibernation module register. If a crystal is used for the clock source, the software must leave a delay of tHIBOSC_START after writing to the CLK32EN bit and before any other accesses to the Hibernation module registers. The delay allows the crystal to power up and stabilize. If an oscillator is used for the clock source, no delay is needed. When using an external clock source, the OSCBYP bit in the HIBCTL register should be set. When using a crystal clock source, the GNDX pin should only be connected to the crystal load capacitors to improve oscillator immunity to system noise as shown in Figure 7-2 on page 483. When using an external clock source, the GNDX pin should be connected to GND. Figure 7-2. Using a Crystal as the Hibernation Clock Source with a Single Battery Source
Regulator or Switch Input Voltage
IN OUT EN XOSC0
Stellaris Microcontroller
VDD
X1
XOSC1
C1
C2
GNDX
HIB WAKE VBAT GND
Open drain external wake up circuit
3V Battery
RPU
Note:
X1 = Crystal frequency is fXOSC_XTAL. C1,2 = Capacitor value derived from crystal vendor load capacitance specifications. RPU = Pull-up resistor is 200 k See Hibernation Clock Source Specifications on page 1166 for specific parameter values.
483
Hibernation Module
Figure 7-3. Using a Dedicated Oscillator as the Hibernation Clock Source with VDD3ON Mode
Stellaris Microcontroller Regulator Input Voltage
IN OUT VDD
Clock Source (fEXT_OSC) N.C.
XOSC0
XOSC1 GNDX
HIB WAKE VBAT GND
RPU
3V Battery
Note:
RPU = Pull-up resistor is 1 M
7.3.3
System Implementation
Several different system configurations are possible when using the Hibernation module: Using a single battery source, where the battery provides both VDD and VBAT, as shown in Figure 7-2 on page 483. Using the VDD3ON mode, where VDD continues to be powered in hibernation, allowing the GPIO pins to retain their states, as shown in Figure 7-3 on page 484. In this mode, VDDC is powered off internally. The GPIO retention will be released when power is reapplied and the GPIOs will be initialized to their default values. Using separate sources for VDD and VBAT. In this mode, additional circuitry is required for system start-up without a battery or with a depleted battery, see the schematics for the EK-LM4F232 board for more information. Using a regulator to provide both VDD and VBAT with a switch enabled by HIB to remove VDD during hibernation as shown in Figure 7-4 on page 485.
April 25, 2012
Figure 7-4. Using a Regulator for Both VDD and VBAT

Stellaris Microcontroller Regulator Input Voltage
IN OUT
Switch
IN OUT EN XOSC0 VDD
X1
XOSC1
C1
C2
GNDX
HIB WAKE VBAT GND
RPU
Adding external capacitance to the VBAT supply reduces the accuracy of the low-battery measurement and should be avoided if possible. The diagrams referenced in this section only show the connection to the Hibernation pins and not to the full system. If the application does not require the use of the Hibernation module, refer to Connections for Unused Signals on page 1156. In this situation, the HIB bit in the Run Mode Clock Gating Control Register 0 (RCGC0) and the Hibernation Run Mode Clock Gating Control (RCGCHIB) registers must be cleared, disabling the system clock to the Hibernation module and Hibernation module registers are not accessible.
7.3.4
Battery Management
Important: System-level factors may affect the accuracy of the low-battery detect circuit. The designer should consider battery type, discharge characteristics, and a test load during battery voltage measurements. The Hibernation module can be independently powered by a battery or an auxiliary power source using the VBAT pin. The module can monitor the voltage level of the battery and detect when the voltage drops below VLOWBAT. The voltage threshold can be between 1.9 V and 2.5 V and is configured using the VBATSEL field in the HIBCTL register. The module can also be configured so that it does not go into Hibernate mode if the battery voltage drops below this threshold. In addition, battery voltage is monitored while in hibernation, and the microcontroller can be configured to wake from hibernation if the battery voltage goes below the threshold using the BATWKEN bit in the HIBCTL register. The Hibernation module is designed to detect a low-battery condition and set the LOWBAT bit of the Hibernation Raw Interrupt Status (HIBRIS) register when this occurs. If the VABORT bit in the HIBCTL register is also set, then the module is prevented from entering Hibernate mode when a low-battery is detected. The module can also be configured to generate an interrupt for the low-battery condition (see Interrupts and Status on page 488). Note that the Hibernation module draws power from whichever source (VBAT or VDD) has the higher voltage. Therefore, it is important to design the circuit to ensure that VDD is higher that VBAT under nominal conditions or else the Hibernation module draws power from the battery even when VDD is available.
485
Hibernation Module
7.3.5
Real-Time Clock
The Hibernation module includes a real-time clock that consists of a 32-bit seconds counter and a 15-bit sub seconds counter. The clock signal from the 32.768-kHz Hibernation oscillator provides the clock source for the RTC. The RTC counters are reset by the Hibernation module reset. The RTC 32-bit seconds counter can be set by the user using the Hibernation RTC Load (HIBRTCLD) register. When the 32-bit seconds counter is set, the 15-bit sub second counter is cleared. The RTC value can be read by first reading the HIBRTCC register, reading the RTCSSC field in the Hibernation RTC Sub Seconds (HIBRTCSS) register, and then rereading the HIBRTCC register. If the two values for HIBRTCC are equal, the read is valid. The Hibernation module also includes a 32-bit match register and a 15-bit field (RTCSSM) in the HIBRTCSS register that are compared to the value of the RTC 32-bit counter and 15-bit sub seconds counter. When a match occurs, the processor can be programmed to wake from Hibernation mode and/or to generate an interrupt to the processor. The match interrupt generation takes priority over the interrupt clear. Therefore, writes to the RTCALT0 bit in the Hibernation Interrupt Clear (HIBIC) register do not clear the bit if the RTC equals the match value. The match interrupt is cleared when the RTC is disabled using the RTCEN bit in the HIBCTL register. The RTC counting rate can be adjusted to compensate for inaccuracies in the clock source by using the predivider trim register, HIBRTCT. This register has a nominal value of 0x7FFF, and is used for one second out of every 64 seconds, when bits [5:0] in the HIBRTCC register change from 0x00 to 0x01, to divide the input clock. This configuration allows the software to make fine corrections to the clock rate by adjusting the predivider trim register up or down from 0x7FFF. The predivider trim should be adjusted up from 0x7FFF in order to slow down the RTC rate and down from 0x7FFF in order to speed up the RTC rate. Care must be taken when using trim values that are near to the sub seconds match value in the HIBRTCSS register. It is possible when using trim values above 0x7FFF to receive two match interrupts for the same counter value. In addition, it is possible when using trim values below 0x7FFF to miss a match interrupt. In the case of a trim value above 0x7FFF, when the RTCSSC value in the HIBRTCSS register reaches 0x7FFF, the RTCC value increments from 0x0 to 0x1 while the RTCSSC value is decreased by the trim amount. The RTCSSC value is counted up again to 0x7FFF before rolling over to 0x0 to begin counting up again. If the match value is within this range, the match interrupt is triggered twice. For example, as shown in Table 7-2 on page 486, if the match interrupt was configured with RTCM0=0x1 and RTCSSM=0x7FFD, two interrupts would be triggered. Table 7-2. Counter Behavior with a TRIM Value of 0x8003
RTCC [6:0] 0x00 0x00 0x00 0x01 0x01 0x01 0x01 0x01 0x01 0x01 RTCSSC 0x7FFD 0x7FFE 0x7FFF 0x7FFC 0x7FFD 0x7FFE 0x7FFF 0x0 0x1 0x7FFB
April 25, 2012
Table 7-2. Counter Behavior with a TRIM Value of 0x8003 (continued)

RTCC [6:0] 0x01 0x01 0x01 0x01 0x02 RTCSSC 0x7FFC 0x7FFD 0x7FFE 0x7FFF 0x0
In the case of a trim value below 0x7FFF, the RTCSSC value is advanced from 0x7FFF to the trim value while the RTCC value is incremented from 0x0 to 0x1. If the match value is within that range, the match interrupt is not triggered. For example, as shown in Table 7-3 on page 487, if the match interrupt was configured with RTCM0=0x1 and RTCSSM=0x2,an interrupt would never be triggered. Table 7-3. Counter Behavior with a TRIM Value of 0x7FFC
RTCC [6:0] 0x00 0x00 0x00 0x01 0x01 0x01 RTCSSC 0x7FFD 0x7FFE 0x7FFF 0x3 0x4 0x5
The RTC must be enabled with the RTCEN bit of the HIBCTL register. The RTC can be configured to generate interrupts by using the interrupt registers (see Interrupts and Status on page 488). As long as the RTC is enabled and a valid VBAT is present, the RTC continues counting, regardless of whether VDD is present or if the part is in hibernation.
7.3.6
Battery-Backed Memory
The Hibernation module contains 16 32-bit words of memory that are powered from the battery or auxiliary power supply and therefore retained during hibernation. The processor software can save state information in this memory prior to hibernation and recover the state upon waking. The battery-backed memory can be accessed through the HIBDATA registers. If both VDD and VBAT are removed, the contents of the HIBDATA registers are not retained.
7.3.7
Power Control Using HIB

Important: The Hibernation Module requires special system implementation considerations when using HIB to control power, as it is intended to power-down all other sections of the microcontroller. All system signals and power supplies that connect to the chip must be driven to 0 VDC or powered down with the same regulator controlled by HIB. The Hibernation module controls power to the microcontroller through the use of the HIB pin which is intended to be connected to the enable signal of the external regulator(s) providing 3.3 V to the microcontroller and other circuits. When the HIB signal is asserted by the Hibernation module, the external regulator is turned off and no longer powers the microcontroller and any parts of the system that are powered by the regulator. The Hibernation module remains powered from the VBAT supply (which could be a battery or an auxiliary power source) until a Wake event. Power to the microcontroller is restored by deasserting the HIB signal, which causes the external regulator to turn power back on to the chip.
487
Hibernation Module
7.3.8
Power Control Using VDD3ON Mode

The Hibernation module may also be configured to cut power to all internal modules. While in this state, all pins are held in the state they were in prior to entering hibernation. For example, inputs remain inputs; outputs driven high remain driven high, and so on. In the VDD3ON mode, the regulator should maintain 3.3 V power to the microcontroller during Hibernate. This power control mode is enabled by setting the VDD3ON bit in HIBCTL.
7.3.9
Initiating Hibernate
Hibernate mode is initiated when the HIBREQ bit of the HIBCTL register is set. If a wake-up condition has not been configured using the PINWEN or RTCWEN bits in the HIBCTL register, the hibernation request is ignored. If a Flash memory write operation is in progress when the HIBREQ bit is set, an interlock feature holds off the transition into Hibernate mode until the write has completed. In addition, if the battery voltage is below the threshold voltage defined by the VBATSEL field in the HIBCTL register, the hibernation request is ignored.
7.3.10
Waking from Hibernate

The Hibernation module is configured to wake from the external WAKE pin by setting the PINWEN bit of the HIBCTL register. It is configured to wake from RTC match by setting the RTCWEN bit. Note that the WAKE pin uses the Hibernation module's internal power supply as the logic 1 reference. Upon either external wake-up or RTC match, the Hibernation module delays coming out of hibernation until VDD is above the minimum specified voltage, see Table 23-2 on page 1159. When the Hibernation module wakes, the microcontroller performs a normal power-on reset. Note that this reset does not reset the Hibernation module, but does reset the rest of the microcontroller. Software can detect that the power-on was due to a wake from hibernation by examining the raw interrupt status register (see Interrupts and Status on page 488) and by looking for state data in the battery-backed memory (see Battery-Backed Memory on page 487).
7.3.11
Arbitrary Power Removal

If the CLK32EN bit is set and either the PINWEN bit or the RTCEN bit is set, the microcontroller goes into hibernation if VDD is arbitrarily removed. The microcontroller wakes from hibernation when power is reapplied. If the CLK32EN bit is set but neither the PINWEN bit nor the RTCEN bit is set, the microcontroller still goes into hibernation if power is removed, however, when VDD is reapplied, the MCU executes a cold POR and the Hibernation module is reset. If the CLK32EN bit is not set and VDD is arbitrarily removed, the part is simply powered off and executes a cold POR when power is reapplied. If VDD is arbitrarily removed while a Flash memory write operation is in progress, the write operation must be retried after VDD is reapplied.
7.3.12
Interrupts and Status

The Hibernation module can generate interrupts when the following conditions occur: Assertion of WAKE pin RTC match Low battery detected Write complete/capable
April 25, 2012
All of the interrupts are ORed together before being sent to the interrupt controller, so the Hibernate module can only generate a single interrupt request to the controller at any given time. The software interrupt handler can service multiple interrupt events by reading the Hibernation Masked Interrupt Status (HIBMIS) register. Software can also read the status of the Hibernation module at any time by reading the HIBRIS register which shows all of the pending events. This register can be used after waking from hibernation to see if a wake condition was caused by one of the events above or by a power loss. The events that can trigger an interrupt are configured by setting the appropriate bits in the Hibernation Interrupt Mask (HIBIM) register. Pending interrupts can be cleared by writing the corresponding bit in the Hibernation Interrupt Clear (HIBIC) register.
7.4

The Hibernation module has several different configurations. The following sections show the recommended programming sequence for various scenarios. Because the Hibernation module runs at 32.768 kHz and is asynchronous to the rest of the microcontroller, which is run off the system clock, software must allow a delay of tHIB_REG_ACCESS after writes to registers (see Register Access Timing on page 482). The WC interrupt in the HIBMIS register can be used to notify the application when the Hibernation modules registers can be accessed.
7.4.1
Initialization
The Hibernation module comes out of reset with the system clock enabled to the module, but if the system clock to the module has been disabled, then it must be re-enabled, even if the RTC feature is not used. See page 315. If a 32.768-kHz crystal is used as the Hibernation module clock source, perform the following steps: 1. Write 0x0000.0010 to the HIBIM register to enable the WC interrupt. 2. Write 0x40 to the HIBCTL register at offset 0x10 to enable the oscillator input. 3. Wait until the WC interrupt in the HIBMIS register has been triggered before performing any other operations with the Hibernation module. If a 32.768-kHz single-ended oscillator is used as the Hibernation module clock source, then perform the following steps: 1. Write 0x0000.0010 to the HIBIM register to enable the WC interrupt. 2. Write 0x0001.0040 to the HIBCTL register at offset 0x10 to enable the oscillator input and bypass the on-chip oscillator. 3. Wait until the WC interrupt in the HIBMIS register has been triggered before performing any other operations with the Hibernation module. The above steps are only necessary when the entire system is initialized for the first time. If the microcontroller has been in hibernation, then the Hibernation module has already been powered up and the above steps are not necessary. The software can detect that the Hibernation module and clock are already powered by examining the CLK32EN bit of the HIBCTL register. Table 7-4 on page 490 illustrates how the clocks function with various bit setting both in normal operation and in hibernation.
489
Hibernation Module
Table 7-4. Hibernation Module Clock Operation

CLK32EN PINWEN RTCWEN RTCEN Result Normal Operation 0 1 1 1 1 1 X 0 0 1 1 1 X 0 1 0 0 1 X 1 1 0 1 1 Hibernation module disabled Result Hibernation Hibernation module disabled
RTC match capability enabled. No hibernation Module clocked Module clocked Module clocked Module clocked RTC match for wake-up event Clock is powered down during hibernation and powered up again on external wake-up event. Clock is powered up during hibernation for RTC. Wake up on external event. RTC match or external wake-up event, whichever occurs first.
7.4.2
RTC Match Functionality (No Hibernation)

Use the following steps to implement the RTC match functionality of the Hibernation module: 1. Write 0x0000.0040 to the HIBCTL register at offset 0x010 to enable 32.768-kHz Hibernation oscillator. 2. Write the required RTC match value to the HIBRTCM0 register at offset 0x004 and the RTCSSM field in the HIBRTCSS register at offset 0x028. 3. Write the required RTC load value to the HIBRTCLD register at offset 0x00C. 4. Set the required RTC match interrupt mask in the RTCALT0 in the HIBIM register at offset 0x014. 5. Write 0x0000.0041 to the HIBCTL register at offset 0x010 to enable the RTC to begin counting.
7.4.3
RTC Match/Wake-Up from Hibernation

Use the following steps to implement the RTC match and wake-up functionality of the Hibernation module: 1. Write 0x0000.0040 to the HIBCTL register at offset 0x010 to enable 32.768-kHz Hibernation oscillator. 2. Write the required RTC match value to the HIBRTCM0 register at offset 0x004 and the RTCSSM field in the HIBRTCSS register at offset 0x028. 3. Write the required RTC load value to the HIBRTCLD register at offset 0x00C. This write causes the 15-bit sub seconds counter to be cleared. 4. Write any data to be retained during power cut to the HIBDATA register at offsets 0x030-0x06F. 5. Set the RTC Match Wake-Up and start the hibernation sequence by writing 0x0000.004B to the HIBCTL register at offset 0x010.
7.4.4
External Wake-Up from Hibernation

Use the following steps to implement the Hibernation module with the external WAKE pin as the wake-up source for the microcontroller: 1. Write 0x0000.0040 to the HIBCTL register at offset 0x010 to enable 32.768-kHz Hibernation oscillator.
April 25, 2012
2. Write any data to be retained during power cut to the HIBDATA register at offsets 0x030-0x06F. 3. Enable the external wake and start the hibernation sequence by writing 0x0000.0052 to the HIBCTL register at offset 0x010. Note that in this mode, if the RTC is disabled, then the Hibernation clock source is powered down during Hibernate mode and is powered up again on the external wake event to save power during hibernation. If the RTC is enabled before hibernation, it continues to operate during hibernation.
7.4.5
RTC or External Wake-Up from Hibernation

1. Write 0x0000.0040 to the HIBCTL register at offset 0x010 to enable 32.768-kHz Hibernation oscillator. 2. Write the required RTC match value to the HIBRTCM0 register at offset 0x004 and the RTCSSM field in the HIBRTCSS register at offset 0x028. 3. Write the required RTC load value to the HIBRTCLD register at offset 0x00C. This write causes the 15-bit sub seconds counter to be cleared. 4. Write any data to be retained during power cut to the HIBDATA register at offsets 0x030-0x06F. 5. Set the RTC Match/External Wake-Up and start the hibernation sequence by writing 0x0000.005B to the HIBCTL register at offset 0x010.
7.5
Register Map
Table 7-5 on page 491 lists the Hibernation registers. All addresses given are relative to the Hibernation Module base address at 0x400F.C000. Note that the system clock to the Hibernation module must be enabled before the registers can be programmed (see page 315). There must be a delay of 3 system clocks after the Hibernation module clock is enabled before any Hibernation module registers are accessed. In addition, the CLK32EN bit in the HIBCTL register must be set before accessing any other Hibernation module register. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Important: The Hibernation module registers are reset under two conditions: 1. A system reset when the RTCEN and the PINWEN bits in the HIBCTL register are both cleared. 2. A cold POR, when both the VDD and VBAT supplies are removed. Any other reset condition is ignored by the Hibernation module. Table 7-5. Hibernation Module Register Map
Offset 0x000 0x004 Name HIBRTCC HIBRTCM0 Type RO R/W Reset 0x0000.0000 0xFFFF.FFFF Description Hibernation RTC Counter Hibernation RTC Match 0 See page 493 494
491
Hibernation Module
Table 7-5. Hibernation Module Register Map (continued)

Offset 0x00C 0x010 0x014 0x018 0x01C 0x020 0x024 0x028 0x0300x06F Name HIBRTCLD HIBCTL HIBIM HIBRIS HIBMIS HIBIC HIBRTCT HIBRTCSS HIBDATA Type R/W R/W R/W RO RO R/W1C R/W R/W R/W Reset 0x0000.0000 0x8000.2000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.7FFF 0x0000.0000 Description Hibernation RTC Load Hibernation Control Hibernation Interrupt Mask Hibernation Raw Interrupt Status Hibernation Masked Interrupt Status Hibernation Interrupt Clear Hibernation RTC Trim Hibernation RTC Sub Seconds Hibernation Data See page 495 496 500 502 504 506 507 508 509
7.6
The remainder of this section lists and describes the Hibernation module registers, in numerical order by address offset.
April 25, 2012
Register 1: Hibernation RTC Counter (HIBRTCC), offset 0x000

This register is the current 32-bit value of the RTC counter. The RTC counter consists of a 32-bit seconds counter and a 15-bit sub seconds counter. The RTC counters are reset by the Hibernation module reset. The RTC 32-bit seconds counter can be set by the user using the HIBRTCLD register. When the 32-bit seconds counter is set, the 15-bit sub second counter is cleared. The RTC value can be read by first reading the HIBRTCC register, reading the RTCSSC field in the HIBRTCSS register, and then rereading the HIBRTCC register. If the two values for HIBRTCC are equal, the read is valid.
Hibernation RTC Counter (HIBRTCC)
Base 0x400F.C000 Offset 0x000 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 RTCC Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RTCC Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name RTCC
Type RO
Reset
Description
0x0000.0000 RTC Counter A read returns the 32-bit counter value, which represents the seconds elapsed since the RTC was enabled. This register is read-only. To change the value, use the HIBRTCLD register.
493
Hibernation Module
Register 2: Hibernation RTC Match 0 (HIBRTCM0), offset 0x004

This register is the 32-bit seconds match register for the RTC counter. The 15-bit sub second match value is stored in the reading the RTCSSC field in the HIBRTCSS register and can be used in conjunction with this register for a more precise time match. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Hibernation RTC Match 0 (HIBRTCM0)

Base 0x400F.C000 Offset 0x004 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 RTCM0 Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 RTCM0 Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name RTCM0
Type R/W
Reset
Description
0xFFFF.FFFF RTC Match 0 A write loads the value into the RTC match register. A read returns the current match value.
April 25, 2012
Register 3: Hibernation RTC Load (HIBRTCLD), offset 0x00C

This register is used to load a 32-bit value loaded into the RTC counter. The load occurs immediately upon this register being written. When this register is written, the 15-bit sub seconds counter is also cleared. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Hibernation RTC Load (HIBRTCLD)

Base 0x400F.C000 Offset 0x00C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 RTCLD Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 RTCLD Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name RTCLD
Type R/W
Reset
Description
0x0000.0000 RTC Load A write loads the current value into the RTC counter (RTCC). A read returns the 32-bit load value.
495
Hibernation Module
Register 4: Hibernation Control (HIBCTL), offset 0x010

This register is the control register for the Hibernation module. This register must be written last before a hibernate event is issued. Writes to other registers after the HIBREQ bit is set are not guaranteed to complete before hibernation is entered.
Hibernation Control (HIBCTL)
Base 0x400F.C000 Offset 0x010 Type R/W, reset 0x8000.2000
31 WRC Type Reset RO 1 15
reserved
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
reserved RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5
reserved
OSCHYS OSCDRV OSCBYP RO 0 4 RO 0 3 R/W 0 2

reserved
R/W 0 1 HIBREQ R/W 0
R/W 0 0 RTCEN R/W 0
VBATSEL R/W 0 R/W 1
reserved RO 0 RO 0
BATCHK BATWKEN VDD3ON VABORT CLK32EN R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
PINWEN RTCWEN R/W 0 R/W 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31
Name WRC
Type RO
Reset 1
Description Write Complete/Capable Value Description 0 The interface is processing a prior write and is busy. Any write operation that is attempted while WRC is 0 results in undetermined behavior. The interface is ready to accept a write.
Software must poll this bit between write requests and defer writes until WRC=1 to ensure proper operation. An interrupt can be configured to indicate the WRC has completed. The bit name WRC means "Write Complete," which is the normal use of the bit (between write accesses). However, because the bit is set out-of-reset, the name can also mean "Write Capable" which simply indicates that the interface may be written to by software. This difference may be exploited by software at reset time to detect which method of programming is appropriate: 0 = software delay loops required; 1 = WRC paced available. 30:19 reserved RO 0x000 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32.768-kHz Oscillator Hysteresis Control This bit is used to prevent self oscillations when the Hibernation oscillator is powered down or does not have a crystal attached. For lowest power states, this should be set. Value Description 1 0 Hysteresis is enabled. Hysteresis is disabled.
18
OSCHYS
R/W
April 25, 2012
Bit/Field 17
Name OSCDRV
Type R/W
Reset 0
Description Oscillator Drive Capability This bit is used to compensate for larger or smaller filtering capacitors. Note: This bit is not meant to be changed once the Hibernation oscillator has started. Oscillator stability is not guaranteed if the user changes this value after the the oscillator is running.
Value Description 1 0 High drive strength is enabled, 24 pF. Low drive strength is enabled, 12 pF.
16
OSCBYP
R/W
Oscillator Bypass Value Description 1 The internal 32.768-kHz Hibernation oscillator is disabled and powered down. This bit should be set when using a single-ended oscillator attached to XOSC0. The internal 32.768-kHz Hibernation oscillator is enabled. This bit should be cleared when using an external 32.768-kHz crystal.
15
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Select for Low-Battery Comparator This field selects the battery level that is used when checking the battery status. If the battery voltage is below the specified level, the LOWBAT interrupt bit in the HIBRIS register is set. Value Description 0x0 0x1 0x2 0x3 1.9 Volts 2.1 Volts (default) 2.3 Volts 2.5 Volts
14:13
VBATSEL
R/W
0x1
12:11
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Check Battery Status Value Description 1 When read, indicates the low-battery comparator cycle has not completed. Setting this bit initiates a low-battery comparator cycle. If the battery voltage is below the level specified by VBATSEL field, the LOWBAT interrupt bit in the HIBRIS register is set. A hibernation request is held off if a battery check is in progress. 0 When read, indicates that the low-battery comparator cycle is not active. Writing a 0 has no effect.
10
BATCHK
R/W
497
Hibernation Module
Bit/Field 9
Name BATWKEN
Type R/W
Reset 0
Description Wake on Low Battery Value Description 1 When this bit is set, the battery voltage level is checked every 512 seconds while in hibernation. If the voltage is below the level specified by VBATSEL field, the microcontroller wakes from hibernation and the LOWBAT interrupt bit in the HIBRIS register is set. The battery voltage level is not automatically checked. Low battery voltage does not cause the microcontroller to wake from hibernation.
VDD3ON
R/W
VDD Powered Value Description 1 0 The internal switches control the power to the on-chip modules (VDD3ON mode). The internal switches are not used. The HIB signal should be used to control an external switch or regulator.
Note that regardless of the status of the VDD3ON bit, the HIB signal is asserted during Hibernate mode. Thus, when VDD3ON is set, the HIB signal should not be connected to the 3.3V regulator, and the 3.3V power source should remain connected. When this bit is set while in hibernation, all pins are held in the state they were in prior to entering hibernation. For example, inputs remain inputs; outputs driven high remain driven high, and so on. 7 VABORT R/W 0 Power Cut Abort Enable Value 1 Description When this bit is set, the battery voltage level is checked before entering hibernation. If VBAT is less than the voltage specified by VBATSEL, the microcontroller does not go into hibernation. The microcontroller goes into hibernation regardless of the voltage level of the battery.
CLK32EN
R/W
Clocking Enable This bit must be enabled to use the Hibernation module. Value 1 0 Description The Hibernation module clock source is enabled. The Hibernation module clock source is disabled.
reserved
RO
April 25, 2012
Bit/Field 4
Name PINWEN
Type R/W
Reset 0
Description External WAKE Pin Enable Value 1 0 Description An assertion of the WAKE pin takes the microcontroller out of hibernation. The status of the WAKE pin has no effect on hibernation.
RTCWEN
R/W
RTC Wake-up Enable Value 1 Description An RTC match event (the value the HIBRTCC register matches the value of the HIBRTCM0 register and the value of the RTCSSC field matches the RTCSSM field in the HIBRTCSS register) takes the microcontroller out of hibernation. An RTC match event has no effect on hibernation.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hibernation Request Value 1 0 Description Set this bit to initiate hibernation. No hibernation request.
HIBREQ
R/W
After a wake-up event, this bit is automatically cleared by hardware. A hibernation request is ignored if both the PINWEN and RTCWEN bits are clear. A hibernation request is held off if the BATCHK bit is set. 0 RTCEN R/W 0 RTC Timer Enable Value 1 0 Description The Hibernation module RTC is enabled. The Hibernation module RTC is disabled.
499
Hibernation Module
Register 5: Hibernation Interrupt Mask (HIBIM), offset 0x014

This register is the interrupt mask register for the Hibernation module interrupt sources. Each bit in this register masks the corresponding bit in the Hibernation Raw Interrupt Status (HIBRIS) register. If a bit is unmasked, the interrupt is sent to the interrupt controller. If the bit is masked, the interrupt is not sent to the interrupt controller. If the WC bit is set before the CLK32EN has been set, the mask value is not preserved over a hibernate cycle unless the bit is written a second time. Note: The WRC bit of this register is in the system clock domain such that a write to this bit is immediate and may be done before the CLKEN bit is set in the HIBCTL register.
Hibernation Interrupt Mask (HIBIM)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 WC R/W 0 RO 0 3 EXTW R/W 0 RO 0 2 LOWBAT R/W 0 RO 0 1
reserved
RO 0 0 RTCALT0 R/W 0
RO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. External Write Complete/Capable Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the WC bit in the HIBRIS register is set. The WC interrupt is suppressed and not sent to the interrupt controller.
WC
R/W
EXTW
R/W
External Wake-Up Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the EXTW bit in the HIBRIS register is set. The EXTW interrupt is suppressed and not sent to the interrupt controller.
LOWBAT
R/W
Low Battery Voltage Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the LOWBAT bit in the HIBRIS register is set. The LOWBAT interrupt is suppressed and not sent to the interrupt controller.
April 25, 2012
Bit/Field 1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RTC Alert 0 Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the RTCALT0 bit in the HIBRIS register is set. The RTCALT0 interrupt is suppressed and not sent to the interrupt controller.
RTCALT0
R/W
501
Hibernation Module
Register 6: Hibernation Raw Interrupt Status (HIBRIS), offset 0x018

This register is the raw interrupt status for the Hibernation module interrupt sources. Each bit can be masked by clearing the corresponding bit in the HIBIM register. When a bit is masked, the interrupt is not sent to the interrupt controller. Bits in this register are cleared by writing a 1 to the corresponding bit in the Hibernation Interrupt Clear (HIBIC) register or by entering hibernation.
Hibernation Raw Interrupt Status (HIBRIS)
Base 0x400F.C000 Offset 0x018 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 WC RO 0 RO 0 3 EXTW RO 0 RO 0 2 LOWBAT RO 0 RO 0 1

reserved
RO 0 0 RTCALT0 RO 0
RO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Write Complete/Capable Raw Interrupt Status Value Description 1 0 The WRC bit in the HIBCTL has been set. The WRC bit in the HIBCTL has not been set.
WC
RO
This bit is cleared by writing a 1 to the WC bit in the HIBIC register. 3 EXTW RO 0 External Wake-Up Raw Interrupt Status Value Description 1 0 The WAKE pin has been asserted. The WAKE pin has not been asserted.
This bit is cleared by writing a 1 to the EXTW bit in the HIBIC register. 2 LOWBAT RO 0 Low Battery Voltage Raw Interrupt Status Value Description 1 0 The battery voltage dropped below VLOWBAT. The battery voltage has not dropped below VLOWBAT.
This bit is cleared by writing a 1 to the LOWBAT bit in the HIBIC register. 1 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Bit/Field 0
Name RTCALT0
Type RO
Reset 0
Description RTC Alert 0 Raw Interrupt Status Value Description 1 The value of the HIBRTCC register matches the value in the HIBRTCM0 register and the value of the RTCSSC field matches the RTCSSM field in the HIBRTCSS register. No match
This bit is cleared by writing a 1 to the RTCALT0 bit in the HIBIC register.
503
Hibernation Module
Register 7: Hibernation Masked Interrupt Status (HIBMIS), offset 0x01C

This register is the masked interrupt status for the Hibernation module interrupt sources. Bits in this register are the AND of the corresponding bits in the HIBRIS and HIBIM registers. When both corresponding bits are set, the bit in this register is set, and the interrupt is sent to the interrupt controller.
Hibernation Masked Interrupt Status (HIBMIS)
Base 0x400F.C000 Offset 0x01C Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 WC RO 0 RO 0 3 EXTW RO 0 RO 0 2 LOWBAT RO 0 RO 0 1

reserved
RO 0 0 RTCALT0 RO 0
RO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Write Complete/Capable Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to the WRC bit being set. The WRC bit has not been set or the interrupt is masked.
WC
RO
This bit is cleared by writing a 1 to the WC bit in the HIBIC register. 3 EXTW RO 0 External Wake-Up Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a WAKE pin assertion. An external wake-up interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the EXTW bit in the HIBIC register. 2 LOWBAT RO 0 Low Battery Voltage Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a low-battery voltage condition. A low-battery voltage interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the LOWBAT bit in the HIBIC register. 1 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Bit/Field 0
Name RTCALT0
Type RO
Reset 0
Description RTC Alert 0 Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to an RTC match. An RTC match interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the RTCALT0 bit in the HIBIC register.
505
Hibernation Module
Register 8: Hibernation Interrupt Clear (HIBIC), offset 0x020

This register is the interrupt write-one-to-clear register for the Hibernation module interrupt sources. Writing a 1 to a bit clears the corresponding interrupt in the HIBRIS register.
Hibernation Interrupt Clear (HIBIC)
Base 0x400F.C000 Offset 0x020 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 WC R/W1C 0 RO 0 3 EXTW R/W1C 0 RO 0 2 LOWBAT R/W1C 0 RO 0 1
reserved
RO 0 0 RTCALT0 R/W1C 0
RO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Write Complete/Capable Masked Interrupt Clear Writing a 1 to this bit clears the WC bit in the HIBRIS and HIBMIS registers. Reads return an indeterminate value.
WC
R/W1C
EXTW
R/W1C
External Wake-Up Masked Interrupt Clear Writing a 1 to this bit clears the EXTW bit in the HIBRIS and HIBMIS registers. Reads return an indeterminate value.
LOWBAT
R/W1C
Low Battery Voltage Masked Interrupt Clear Writing a 1 to this bit clears the LOWBAT bit in the HIBRIS and HIBMIS registers. Reads return an indeterminate value.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RTC Alert0 Masked Interrupt Clear Writing a 1 to this bit clears the RTCALT0 bit in the HIBRIS and HIBMIS registers. Reads return an indeterminate value. Note: The timer interrupt source cannot be cleared if the RTC value and the HIBRTCM0 register / RTCMSS field values are equal. The match interrupt takes priority over the interrupt clear.
RTCALT0
R/W1C
April 25, 2012
Register 9: Hibernation RTC Trim (HIBRTCT), offset 0x024

This register contains the value that is used to trim the RTC clock predivider. It represents the computed underflow value that is used during the trim cycle. It is represented as 0x7FFF N clock cycles, where N is the number of clock cycles to add or subtract every 63 seconds. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Hibernation RTC Trim (HIBRTCT)

Base 0x400F.C000 Offset 0x024 Type R/W, reset 0x0000.7FFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 TRIM Type Reset R/W 0 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RTC Trim Value This value is loaded into the RTC predivider every 64 seconds. It is used to adjust the RTC rate to account for drift and inaccuracy in the clock source. Compensation can be adjusted by software by moving the default value of 0x7FFF up or down. Moving the value up slows down the RTC and moving the value down speeds up the RTC.
15:0
TRIM
R/W
0x7FFF
507
Hibernation Module
Register 10: Hibernation RTC Sub Seconds (HIBRTCSS), offset 0x028

This register contains the RTC sub seconds counter and match values. The RTC value can be read by first reading the HIBRTCC register, reading the RTCSSC field in the HIBRTCSS register, and then rereading the HIBRTCC register. If the two values for HIBRTCC are equal, the read is valid. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Hibernation RTC Sub Seconds (HIBRTCSS)

31
reserved
30
29
28
27
26
25
24
23 RTCSSM
22
21
20
19
18
17
16
Type Reset
RO 0 15
reserved
R/W 0 14
R/W 0 13
R/W 0 12
R/W 0 11
R/W 0 10
R/W 0 9
R/W 0 8
R/W 0 7 RTCSSC
R/W 0 6
R/W 0 5
R/W 0 4
R/W 0 3
R/W 0 2
R/W 0 1
R/W 0 0
Type Reset
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RTC Sub Seconds Match A write loads the value into the RTC sub seconds match register in 1/32,768 of a second increments. A read returns the current 1/32,768 seconds match value.
30:16
RTCSSM
R/W
0x0000
15
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RTC Sub Seconds Count A read returns the sub second RTC count in 1/32,768 seconds.
14:0
RTCSSC
RO
0x0000
April 25, 2012
Register 11: Hibernation Data (HIBDATA), offset 0x030-0x06F

This address space is implemented as a 16x32-bit memory (64 bytes). It can be loaded by the system processor in order to store state information and does not lose power during a power cut operation as long as a battery is present. The MEMPD bit in the HIBCTL register must be clear in order to be able to access the HIBDATA registers. Note: The Hibernation module registers are on the Hibernation module clock domain and have special timing requirements. Software should make use of the WRC bit in the HIBCTL register to ensure that the required timing gap has elapsed. If the WRC bit is clear, any attempted write access is ignored. See Register Access Timing on page 482.
Hibernation Data (HIBDATA)

Base 0x400F.C000 Offset 0x030-0x06F Type R/W, reset 31 30 29 28 27 26 25 24 RTD Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 RTD Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name RTD
Type R/W
Reset -
Description Hibernation Module NV Data
509
Internal Memory
Internal Memory
The LM4F120H5QR microcontroller comes with 32 KB of bit-banded SRAM, internal ROM, 256 KB of Flash memory, and 2KB of EEPROM. The Flash memory controller provides a user-friendly interface, making Flash memory programming a simple task. Flash memory is organized in 1-KB independently erasable blocks and memory protection can be applied to the Flash memory on a 2-KB block basis. The EEPROM module provides a well-defined register interface to support accesses to the EEPROM with both a random access style of read and write as well as a rolling or sequential access scheme. A password model allows the application to lock one or more EEPROM blocks to control access on 16-word boundaries.
8.1
Block Diagram
Figure 8-1 on page 510 illustrates the internal SRAM, ROM, and Flash memory blocks and control logic. The dashed boxes in the figure indicate registers residing in the System Control module. Figure 8-1. Internal Memory Block Diagram
ROM Control RMCTL ROM Array
Flash Control
Icode Bus
FMA FMD
Cortex-M4F
Dcode Bus
FMC FCRIS FCIM FCMISC Flash Array
System Bus
FSIZE SSIZE Flash Write Buffer FMC2 FWBVAL FWBn 32 words
Bridge Flash Protection FMPRE FMPPE FMPREn FMPPEn User Registers BOOTCFG SRAM Array USER_REG0 USER_REG1 USER_REG2 USER_REG3
April 25, 2012
Figure 8-2 on page 511 illustrates the internal EEPROM block and control logic. The EEPROM block is connected to the AHB bus. Figure 8-2. EEPROM Block Diagram
EEPROM Control EESIZE EEPAGE EEOFFSET EERDWR EERDWRINC EEDONE EESUPP EEUNLOCK EEPROT EEPASS0 EEPASS1 EEPASS2 EEINT EEHIDE EEDBGME ... Block n Security Program EEPROM Array Block 0 Block 1 Block 2 Block 3
8.2
This section describes the functionality of the SRAM, ROM, Flash, and EEPROM memories. Note: The DMA controller can transfer data to and from the on-chip SRAM. However, because the Flash memory and ROM are located on a separate internal bus, it is not possible to transfer data from the Flash memory or ROM with the DMA controller.
8.2.1
SRAM
The internal SRAM of the Stellaris devices is located at address 0x2000.0000 of the device memory map. To reduce the number of time consuming read-modify-write (RMW) operations, ARM provides bit-banding technology in the processor. With a bit-band-enabled processor, certain regions in the memory map (SRAM and peripheral space) can use address aliases to access individual bits in a single, atomic operation. The bit-band base is located at address 0x2200.0000. The bit-band alias is calculated by using the formula: bit-band alias = bit-band base + (byte offset * 32) + (bit number * 4) For example, if bit 3 at address 0x2000.1000 is to be modified, the bit-band alias is calculated as: 0x2200.0000 + (0x1000 * 32) + (3 * 4) = 0x2202.000C With the alias address calculated, an instruction performing a read/write to address 0x2202.000C allows direct access to only bit 3 of the byte at address 0x2000.1000. For details about bit-banding, see Bit-Banding on page 93.
511
Internal Memory
Note:
The SRAM is implemented using two 32-bit wide SRAM banks (separate SRAM arrays). The banks are partitioned such that one bank contains all even words (the even bank) and the other contains all odd words (the odd bank). A write access that is followed immediately by a read access to the same bank incurs a stall of a single clock cycle. However, a write to one bank followed by a read of the other bank can occur in successive clock cycles without incurring any delay.
8.2.2
ROM
The internal ROM of the Stellaris device is located at address 0x0100.0000 of the device memory map. Detailed information on the ROM contents can be found in the Stellaris ROM Users Guide. The ROM contains the following components: Stellaris Boot Loader and vector table Stellaris Peripheral Driver Library (DriverLib) release for product-specific peripherals and interfaces Advanced Encryption Standard (AES) cryptography tables Cyclic Redundancy Check (CRC) error detection functionality The boot loader is used as an initial program loader (when the Flash memory is empty) as well as an application-initiated firmware upgrade mechanism (by calling back to the boot loader). The Peripheral Driver Library APIs in ROM can be called by applications, reducing Flash memory requirements and freeing the Flash memory to be used for other purposes (such as additional features in the application). Advance Encryption Standard (AES) is a publicly defined encryption standard used by the U.S. Government and Cyclic Redundancy Check (CRC) is a technique to validate if a block of data has the same contents as when previously checked.
8.2.2.1
Boot Loader Overview

The Stellaris Boot Loader is used to download code to the Flash memory of a device without the use of a debug interface. When the core is reset, the user has the opportunity to direct the core to execute the ROM Boot Loader or the application in Flash memory by using any GPIO signal in Ports A-H as configured in the Boot Configuration (BOOTCFG) register. At reset, the following sequence is performed: 1. The BOOTCFG register is read. If the EN bit is clear, the ROM Boot Loader is executed. 2. In the ROM Boot Loader, the status of the specified GPIO pin is compared with the specified polarity. If the status matches the specified polarity, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 3. If the EN bit is set or the status doesn't match the specified polarity, the data at address 0x0000.0004 is read, and if the data at this address is 0xFFFF.FFFF, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 4. If there is data at address 0x0000.0004 that is not 0xFFFF.FFFF, the stack pointer (SP) is loaded from Flash memory at address 0x0000.0000 and the program counter (PC) is loaded from address 0x0000.0004. The user application begins executing. The boot loader uses a simple packet interface to provide synchronous communication with the device. The speed of the boot loader is determined by the internal oscillator (PIOSC) frequency as it does not enable the PLL. The following serial interfaces can be used:
April 25, 2012
UART0 SSI0 I2C0 USB The data format and communication protocol are identical for the UART0, SSI0, and I2C0 interfaces. Note: The Flash-memory-resident version of the boot loader also supports CAN.
See the Stellaris Boot Loader User's Guide for information on the boot loader software. The USB boot loader uses the standard Device Firmware Upgrade USB device class. Considerations When Using the UART Boot Loader in ROM U0Tx is not driven by the ROM boot loader until the auto-bauding process has completed. If U0Tx is floating during this time, the receiver it is connected to may see transitions on the signal, which could be interpreted by its UART as valid characters. To handle this situation, put a pull-up or pull-down on U0Tx, providing a defined state for the signal until the ROM boot loader begins driving U0Tx. A pull-up is preferred as it indicates that the UART is idle, rather than a pull-down, which indicates a break condition.
8.2.2.2
Stellaris Peripheral Driver Library

The Stellaris Peripheral Driver Library contains a file called driverlib/rom.h that assists with calling the peripheral driver library functions in the ROM. The detailed description of each function is available in the Stellaris ROM Users Guide. See the "Using the ROM" chapter of the Stellaris Peripheral Driver Library User's Guide for more details on calling the ROM functions and using driverlib/rom.h. The driverlib/rom_map.h header file is also provided to aid portability when using different Stellaris devices which might have a different subset of DriverLib functions in ROM. The driverlib/rom_map.h header file uses build-time labels to route function calls to the ROM if those functions are available on a given device, otherwise, it routes to Flash-resident versions of the functions. A table at the beginning of the ROM points to the entry points for the APIs that are provided in the ROM. Accessing the API through these tables provides scalability; while the API locations may change in future versions of the ROM, the API tables will not. The tables are split into two levels; the main table contains one pointer per peripheral which points to a secondary table that contains one pointer per API that is associated with that peripheral. The main table is located at 0x0100.0010, right after the Cortex-M4F vector table in the ROM. DriverLib functions are described in detail in the Stellaris Peripheral Driver Library User's Guide. Additional APIs are available for graphics and USB functions, but are not preloaded into ROM. The Stellaris Graphics Library provides a set of graphics primitives and a widget set for creating graphical user interfaces on Stellaris microcontroller-based boards that have a graphical display (for more information, see the Stellaris Graphics Library User's Guide). The Stellaris USB Library is a set of data types and functions for creating USB Device, Host or On-The-Go (OTG) applications on Stellaris microcontroller-based boards (for more information, see the Stellaris USB Library User's Guide).
8.2.2.3
Advanced Encryption Standard (AES) Cryptography Tables

AES is a strong encryption method with reasonable performance and size. AES is fast in both hardware and software, is fairly easy to implement, and requires little memory. AES is ideal for
513
Internal Memory
applications that can use pre-arranged keys, such as setup during manufacturing or configuration. Four data tables used by the XySSL AES implementation are provided in the ROM. The first is the forward S-box substitution table, the second is the reverse S-box substitution table, the third is the forward polynomial table, and the final is the reverse polynomial table. See the Stellaris ROM Users Guide for more information on AES.
8.2.2.4
Cyclic Redundancy Check (CRC) Error Detection

The CRC technique can be used to validate correct receipt of messages (nothing lost or modified in transit), to validate data after decompression, to validate that Flash memory contents have not been changed, and for other cases where the data needs to be validated. A CRC is preferred over a simple checksum (e.g. XOR all bits) because it catches changes more readily. See the Stellaris ROM Users Guide for more information on CRC.
8.2.3
Flash Memory
At system clock speeds of 40 MHz and below, the Flash memory is read in a single cycle. The Flash memory is organized as a set of 1-KB blocks that can be individually erased. An individual 32-bit word can be programmed to change bits from 1 to 0. In addition, a write buffer provides the ability to program 32 continuous words in Flash memory in half the time of programming the words individually. Erasing a block causes the entire contents of the block to be reset to all 1s. The 1-KB blocks are paired into sets of 2-KB blocks that can be individually protected. The protection allows blocks to be marked as read-only or execute-only, providing different levels of code protection. Read-only blocks cannot be erased or programmed, protecting the contents of those blocks from being modified. Execute-only blocks cannot be erased or programmed and can only be read by the controller instruction fetch mechanism, protecting the contents of those blocks from being read by either the controller or a debugger.
8.2.3.1
Prefetch Buffer
The Flash memory controller has a prefetch buffer that is automatically used when the CPU frequency is greater than 40 MHz. In this mode, the Flash memory operates at half of the system clock. The prefetch buffer fetches two 32-bit words per clock allowing instructions to be fetched with no wait states while code is executing linearly. The fetch buffer includes a branch speculation mechanism that recognizes a branch and avoids extra wait states by not reading the next word pair. Also, short loop branches often stay in the buffer. As a result, some branches can be executed with no wait states. Other branches incur a single wait state.
8.2.3.2
Flash Memory Protection

The user is provided two forms of Flash memory protection per 2-KB Flash memory block in four pairs of 32-bit wide registers. The policy for each protection form is controlled by individual bits (per policy per block) in the FMPPEn and FMPREn registers. Flash Memory Protection Program Enable (FMPPEn): If a bit is set, the corresponding block may be programmed (written) or erased. If a bit is cleared, the corresponding block may not be changed. Flash Memory Protection Read Enable (FMPREn): If a bit is set, the corresponding block may be executed or read by software or debuggers. If a bit is cleared, the corresponding block may only be executed, and contents of the memory block are prohibited from being read as data. The policies may be combined as shown in Table 8-1 on page 515.
April 25, 2012
Table 8-1. Flash Memory Protection Policy Combinations

FMPPEn 0 1 0 FMPREn 0 0 1 Protection Execute-only protection. The block may only be executed and may not be written or erased. This mode is used to protect code. The block may be written, erased or executed, but not read. This combination is unlikely to be used. Read-only protection. The block may be read or executed but may not be written or erased. This mode is used to lock the block from further modification while allowing any read or execute access. No protection. The block may be written, erased, executed or read.
A Flash memory access that attempts to read a read-protected block (FMPREn bit is set) is prohibited and generates a bus fault. A Flash memory access that attempts to program or erase a program-protected block (FMPPEn bit is set) is prohibited and can optionally generate an interrupt (by setting the AMASK bit in the Flash Controller Interrupt Mask (FCIM) register) to alert software developers of poorly behaving software during the development and debug phases. Note that if a FMPREn bit is cleared, all read accesses to the Flash memory block are disallowed, including any data accesses. Care must be taken not to store required data in a Flash memory block that has the associated FMPREn bit cleared. The factory settings for the FMPREn and FMPPEn registers are a value of 1 for all implemented banks. These settings create a policy of open access and programmability. The register bits may be changed by clearing the specific register bit. The changes are effective immediately, but are not permanent until the register is committed (saved), at which point the bit change is permanent. If a bit is changed from a 1 to a 0 and not committed, it may be restored by executing a power-on reset sequence. The changes are committed using the Flash Memory Control (FMC) register. Details on programming these bits are discussed in Non-Volatile Register Programming on page 517.
8.2.3.3
Interrupts
The Flash memory controller can generate interrupts when the following conditions are observed: Programming Interrupt - signals when a program or erase action is complete. Access Interrupt - signals when a program or erase action has been attempted on a 2-kB block of memory that is protected by its corresponding FMPPEn bit. The interrupt events that can trigger a controller-level interrupt are defined in the Flash Controller Masked Interrupt Status (FCMIS) register (see page 533) by setting the corresponding MASK bits. If interrupts are not used, the raw interrupt status is always visible via the Flash Controller Raw Interrupt Status (FCRIS) register (see page 530). Interrupts are always cleared (for both the FCMIS and FCRIS registers) by writing a 1 to the corresponding bit in the Flash Controller Masked Interrupt Status and Clear (FCMISC) register (see page 535).
8.2.3.4
Flash Memory Programming

The Stellaris devices provide a user-friendly interface for Flash memory programming. All erase/program operations are handled via three registers: Flash Memory Address (FMA), Flash Memory Data (FMD), and Flash Memory Control (FMC). Note that if the debug capabilities of the microcontroller have been deactivated, resulting in a "locked" state, a recovery sequence must be performed in order to reactivate the debug module. See Recovering a "Locked" Microcontroller on page 201.
515
Internal Memory
During a Flash memory operation (write, page erase, or mass erase) access to the Flash memory is inhibited. As a result, instruction and literal fetches are held off until the Flash memory operation is complete. If instruction execution is required during a Flash memory operation, the code that is executing must be placed in SRAM and executed from there while the flash operation is in progress. Note: When programming Flash memory, the following characteristics of the memory must be considered: Only an erase can change bits from 0 to 1. A write can only change bits from 1 to 0. If the write attempts to change a 0 to a 1, the write fails and no bits are changed. A flash operation can be started before entering Sleep or Deep-sleep mode (using the wait for interrupt instruction, WFI), but will not complete while in Sleep or Deep-sleep . Instead, the operation completes after an event has woken the system. This means that you cannot rely on the PRIS bit in the Flash Controller Raw Interrupt Status (FCRIS) register to actually wake the device from Sleep or Deep-Sleep. To program a 32-bit word 1. Write source data to the FMD register. 2. Write the target address to the FMA register. 3. Write the Flash memory write key and the WRITE bit (a value of 0xA442.0001) to the FMC register. 4. Poll the FMC register until the WRITE bit is cleared. To perform an erase of a 1-KB page 1. Write the page address to the FMA register. 2. Write the Flash memory write key and the ERASE bit (a value of 0xA442.0002) to the FMC register. 3. Poll the FMC register until the ERASE bit is cleared or, alternatively, enable the programming interrupt using the PMASK bit in the FCIM register. To perform a mass erase of the Flash memory 1. Write the Flash memory write key and the MERASE bit (a value of 0xA442.0004) to the FMC register. 2. Poll the FMC register until the MERASE bit is cleared or, alternatively, enable the programming interrupt using the PMASK bit in the FCIM register.
8.2.3.5
32-Word Flash Memory Write Buffer

A 32-word write buffer provides the capability to perform faster write accesses to the Flash memory by programming 2 32-bit words at a time, allowing 32 words to be programmed in the same time as 16. The data for the buffered write is written to the Flash Write Buffer (FWBn) registers.
April 25, 2012
The registers are 32-word aligned with Flash memory, and therefore the register FWB0 corresponds with the address in FMA where bits [6:0] of FMA are all 0. FWB1 corresponds with the address in FMA + 0x4 and so on. Only the FWBn registers that have been updated since the previous buffered Flash memory write operation are written. The Flash Write Buffer Valid (FWBVAL) register shows which registers have been written since the last buffered Flash memory write operation. This register contains a bit for each of the 32 FWBn registers, where bit[n] of FWBVAL corresponds to FWBn. The FWBn register has been updated if the corresponding bit in the FWBVAL register is set. To program 32 words with a single buffered Flash memory write operation 1. Write the source data to the FWBn registers. 2. Write the target address to the FMA register. This must be a 32-word aligned address (that is, bits [6:0] in FMA must be 0s). 3. Write the Flash memory write key and the WRBUF bit (a value of 0xA442.0001) to the FMC2 register. 4. Poll the FMC2 register until the WRBUF bit is cleared or wait for the PMIS interrupt to be signaled.
8.2.3.6
Non-Volatile Register Programming

This section discusses how to update the registers shown in Table 8-2 on page 518 that are resident within the Flash memory itself. These registers exist in a separate space from the main Flash memory array and are not affected by an ERASE or MASS ERASE operation. With the exception of the Boot Configuration (BOOTCFG) register, the settings in these registers can be written, their functions verified, and their values read back before they are committed, at which point they become non-volatile. If a value in one of these registers has not been committed, a power-on reset restores the last committed value or the default value if the register has never been committed. Other types of reset have no effect. Once the register contents are committed, the only way to restore the factory default values is to perform the sequence described in Recovering a "Locked" Microcontroller on page 201. To write to a non-volatile register: Bits can only be changed from 1 to 0. For all registers except the BOOTCFG register, write the data to the register address provided in the register description. For the BOOTCFG register, write the data to the FMD register. The registers can be read to verify their contents. To verify what is to be stored in the BOOTCFG register, read the FMD register. Reading the BOOTCFG register returns the previously committed value or the default value if the register has never been committed. The new values are effectively immediately for all registers except BOOTCFG, as the new value for the register is not stored in the register until it has been committed. Prior to committing the register value, a power-on reset restores the last committed value or the default value if the register has never been committed. To commit a new value to a non-volatile register: Write the data as described above. Write to the FMA register the value shown in Table 8-2 on page 518.
517
Internal Memory
Write the Flash memory write key and set the COMT bit in the FMC register. These values must be written to the FMC register at the same time. Committing a non-volatile register has the same timing as a write to regular Flash memory, defined by TPROG64, as shown in Table 23-22 on page 1172. Software can poll the COMT bit in the FMC register to determine when the operation is complete, or an interrupt can be enabled by setting the PMASK bit in the FCIM register. When committing the BOOTCFG register, the INVDRIS bit in the FCRIS register is set if a bit that has already been committed as a 0 is attempted to be committed as a 1. Once the value has been committed, a power-on reset has no effect on the register contents. Changes to the BOOTCFG register are effective after the next power-on reset. Once the NW bit has been changed to 0 and committed, further changes to the BOOTCFG register are not allowed. Important: After being committed, these registers can only be restored to their factory default values by performing the sequence described in Recovering a "Locked" Microcontroller on page 201. The mass erase of the main Flash memory array caused by the sequence is performed prior to restoring these registers. Table 8-2. User-Programmable Flash Memory Resident Registers
Register to be Committed FMPRE0 FMPRE1 FMPRE2 FMPRE3 FMPPE0 FMPPE1 FMPPE2 FMPPE3 USER_REG0 USER_REG1 USER_REG2 USER_REG3 BOOTCFG FMA Value 0x0000.0000 0x0000.0002 0x0000.0004 0x0000.0006 0x0000.0001 0x0000.0003 0x0000.0005 0x0000.0007 0x8000.0000 0x8000.0001 0x8000.0002 0x8000.0003 0x7510.0000 Data Source FMPRE0 FMPRE1 FMPRE2 FMPRE3 FMPPE0 FMPPE1 FMPPE2 FMPPE3 USER_REG0 USER_REG1 USER_REG2 USER_REG3 FMD
8.2.4
EEPROM
The LM4F120H5QR microcontroller includes an EEPROM with the following features: 2K bytes of memory accessible as 512 32-bit words 32 blocks of 16 words (64 bytes) each Built-in wear leveling Access protection per block
April 25, 2012
Lock protection option for the whole peripheral as well as per block using 32-bit to 96-bit unlock codes (application selectable) Interrupt support for write completion to avoid polling Endurance of 500K writes (when writing at fixed offset in every alternate page in circular fashion) to 15M operations (when cycling through two pages ) per each 2-page block.
8.2.4.1
The EEPROM module provides a well-defined register interface to support accesses to the EEPROM with both a random access style of read and write as well as a rolling or sequential access scheme. A protection mechanism allows locking EEPROM blocks to prevent writes under a set of circumstances as well as reads under the same or different circumstances. The password model allows the application to lock one or more EEPROM blocks to control access on 16-word boundaries. Important: The configuration of the system clock must not be changed while an EEPROM operation is in process. Software must wait until the WORKING bit in the EEPROM Done Status (EEDONE) register is clear before making any changes to the system clock. Blocks There are 32 blocks of 16 words each in the EEPROM. Bytes and half-words can be read, and these accesses do not have to occur on a word boundary. The entire word is read and any unneeded data is simply ignored. They are writable only on a word basis. To write a byte, it is necessary to read the word value, modify the appropriate byte, and write the word back. Each block is addressable as an offset within the EEPROM, using a block select register. Each word is offset addressable within the selected block. The current block is selected by the EEPROM Current Block (EEBLOCK) register. The current offset is selected and checked for validity by the EEPROM Current Offset (EEOFFSET) register. The application may write the EEOFFSET register any time, and it is also automatically incremented when the EEPROM Read-Write with Increment (EERDWRINC) register is accessed. However, the EERDWRINC register does not increment the block number, but instead wraps within the block. Blocks are individually protectable. Attempts to read from a block for which the application does not have permission return 0xFFFF.FFFF. Attempts to write into a block for which the application does not have permission results in an error in the EEDONE register. Timing Considerations After enabling or resetting the EEPROM module, software must wait until the WORKING bit in the EEDONE register is clear before accessing any EEPROM registers. In the event that there are Flash memory writes or erases and EEPROM writes active, it is possible for the EEPROM process to be interrupted by the Flash memory write/erase and then continue after the Flash memory write is completed. This action may change the amount of time that the EEPROM operation takes. EEPROM operations must be completed before entering Sleep or Deep-Sleep mode. Ensure the EEPROM operations have completed by checking the EEPROM Done Status (EEDONE) register before issuing a WFI instruction to enter Sleep or Deep-Sleep. Reads of words within a block are at direct speed, which means that wait states are automatically generated if the system clock is faster than the speed of the EEPROM. The read access time is specified in Table 23-23 on page 1172.
519
Internal Memory
Writing the EEOFFSET register also does not incur any penalties. Writing the EEBLOCK register is not delayed, but any attempt to access data within that block is delayed by 4 clocks after writing EEBLOCK. This time is used to load block specific information. Writes to words within a block are delayed by a variable amount of time. The application may use an interrupt to be notified when the write is done, or alternatively poll for the done status in the EEDONE register. The variability ranges from the write timing of the EEPROM to the erase timing of EEPROM, where the erase timing is less than the write timing of most external EEPROMs. Locking and Passwords The EEPROM can be locked at both the module level and the block level. The lock is controlled by a password that is stored in the EEPROM Password (EEPASSn) registers and can be any 32-bit to 96-bit value other than all 1s. Block 0 is the master block, the password for block 0 protects the control registers as well as all other blocks. Each block can be further protected with a password for that block. If a password is registered for block 0, then the whole module is locked at reset. The locking behavior is such that blocks 1 to 31 are inaccessible until block 0 is unlocked, and block 0 follows the rules defined by its protection bits. As a result, the EEBLOCK register cannot be changed from 0 until block 0 is unlocked. A password registered with any block, including block 0, allows for protection rules that control access of that block based on whether it is locked or unlocked. Generally, the lock can be used to prevent write accesses when locked or can prevent read and write accesses when locked. All password protected blocks are locked at reset. To unlock a block, the correct password value must be written to the EEPROM Unlock (EEUNLOCK) register by writing to it once, twice, or three times, depending on the size of the password. A block or the module may be re-locked by writing 0xFFFF.FFFF to the EEUNLOCK register because 0xFFFF.FFFF is not a valid password. Protection and Access Control The protection bits provide discrete control of read and write access for each block which allows various protection models per block, including: Without password: Readable and writable at any time. This mode is the default when there is no password. Without password: Readable but not writable. With password: Readable, but only writable when unlocked by the password. This mode is the default when there is a password. With password: Readable or writable only when unlocked. With password: Readable only when unlocked, not writable. Additionally, access protection may be applied based on the processor mode. This configuration allows for supervisor-only access or supervisor and user access, which is the default. Supervisor-only access mode also prevents access by the DMA and Debugger. Additionally, the master block may be used to control access protection for the protection mechanism itself. If access control for block 0 is for supervisor only, then the whole module may only be accessed in supervisor mode.
April 25, 2012
Note that for blocks 1 to 31, they are inaccessible for read or write if block 0 has a password and it is not unlocked. If block 0 has a master password, then the strictest protection defined for block 0 or an individual block is implemented on the remaining blocks. Hidden Blocks Hiding provides a temporary form of protection. Every block except block 0 can be hidden, which prevents all accesses until the next reset. This mechanism can allow a boot or initialization routine to access some data which is then made inaccessible to all further accesses. Because boot and initialization routines control the capabilities of the application, hidden blocks provide a powerful isolation of the data when debug is disabled. A typical use model would be to have the initialization code store passwords, keys, and/or hashes to use for verification of the rest of the application. Once performed, the block is then hidden and made inaccessible until the next reset which then re-enters the initialization code. Power and Reset Safety Once the EEDONE register indicates that a location has been successfully written, the data is retained until that location is written again. There is no power or reset race after the EEDONE register indicates a write has completed. Interrupt Control The EEPROM module allows for an interrupt when a write completes to eliminate the need for polling. The interrupt can be used to drive an application ISR which can then write more words or verify completion. The interrupt mechanism is used any time the EEDONE register goes from working to done, whether because of an error or the successful completion of a program or erase operation. This interrupt mechanism works for data writes, writes to password and protection registers, forced erase by the EEPROM Support Control and Status (EESUPP) register, and mass erase using the EEPROM Debug Mass Erase (EEDGBME) register. The EEPROM interrupt is signaled to the core using the Flash memory interrupt vector. Software can determine that the source of the interrupt was the EEPROM by examining bit 2 of the Flash Controller Masked Interrupt Status and Clear (FCMISC) register. Theory of Operation The EEPROM operates using a traditional Flash bank model which implements EEPROM-type cells, but uses sector erase. Additionally, words are replicated in the pages to allow 500K+ erase cycles when needed, which means that each word has a latest version. As a result, a write creates a new version of the word in a new location, making the previous value obsolete. Each sector contains two blocks. Each block contains locations for the active copy plus six redundant copies. Passwords, protection bits, and control data are all stored in the pages. When a page runs out of room to store the latest version of a word, a copy buffer is used. The copy buffer copies the latest words of each block. The original page is then erased. Finally, the copy buffer contents are copied back to the page. This mechanism ensures that data cannot be lost due to power down, even during an operation. The EEPROM mechanism properly tracks all state information to provide complete safety and protection. Although it should not normally be possible, errors during programming can occur in certain circumstances, for example, the voltage rail dropping during programming. In these cases, the EESUPP register can be used to finish an operation as described in the section called Error During Programming on page 522.
521
Internal Memory
Manual Copy Buffer Erase The copy buffer is only used when a main block is full because a word has been written seven times and there is no more room to store its latest version. In this situation, the latest versions of all the words in the block are copied to the copy buffer, allowing the main block to be erased safely, providing power down safety. If the copy buffer itself is full, then it must first be erased, which adds extra time. By performing a manual erase of the copy buffer, this overhead does not occur during a future write access. The EREQ bit in the EESUPP register is set if the copy buffer must be erased. If so, the START bit can be written by the application to force the erase at a more convenient time. The EEDONE and EEINT registers can be used to detect completion. Error During Programming Operations such as data-write, password set, protection set, and copy buffer erase may perform multiple operations. For example, a normal write performs two underlying writes: the control word write and the data write. If the control word writes but the data fails (for example, due to a voltage drop), the overall write fails with indication provided in the EEDONE register. Failure and the corrective action is broken down by the type of operation: If a normal write fails such that the control word is written but the data fails to write, the safe course of action is to retry the operation once the system is otherwise stable, for example, when the voltage is stabilized. After the retry, the control word and write data are advanced to the next location. If a password or protection write fails, the safe course of action is to retry the operation once the system is otherwise stable. In the event that multi-word passwords may be written outside of a manufacturing or bring-up mode, care must be taken to ensure all words are written in immediate succession. If not, then partial password unlock would need to be supported to recover. If the word write requires the block to be written to the copy buffer, then it is possible to fail or lose power during the subsequent operations. A control word mechanism is used to track what step the EEPROM was in if a failure occurs. If not completed, the EESUPP register indicates the partial completion, and the EESUPP START bit can be written to allow it to continue to completion. If a copy buffer erase fails or power is lost while erasing, the EESUPP register indicates it is not complete and allows it to be restarted After a reset and prior to writing any data to the EEPROM, software must read the EESUPP register and check for the presence of any error condition which may indicate that a write or erase was in progress when the system was reset due to a voltage drop. If either the PRETRY or ERETRY bits are set, the peripheral should be reset by setting and then clearing the R0 bit in the EEPROM Software Reset (SREEPROM) register and waiting for the WORKING bit in the EEDONE register to clear before again checking the EESUPP register for error indicators. This procedure should allow the EEPROM to recover from the write or erase error. In very isolated cases, the EESUPP register may continue to register an error after this operation, in which case the reset should be repeated. After recovery, the application should rewrite the data which was being programmed when the initial failure occurred. Endurance Endurance is per meta-block which is 2 blocks. Endurance is measured in two ways: 1. To the application, it is the number of writes that can be performed.
April 25, 2012
2. To the microcontroller, it is the number of erases that can be performed on the meta-block. Because of the second measure, the number of writes depends on how the writes are performed. For example: One word can be written more than 500K times, but, these writes impact the meta-block that the word is within. As a result, writing one word 500K times, then trying to write a nearby word 500K times is not assured to work. To ensure success, the words should be written more in parallel. All words can be written in a sweep with a total of more than 500K sweeps which updates all words more than 500K times. Different words can be written such that any or all words can be written more than 500K times when write counts per word stay about the same. For example, offset 0 could be written 3 times, then offset 1 could be written 2 times, then offset 2 is written 4 times, then offset 1 is written twice, then offset 0 is written again. As a result, all 3 offsets would have 4 writes at the end of the sequence. This kind of balancing within 7 writes maximizes the endurance of different words within the same meta-block.
8.2.4.2
EEPROM Initialization and Configuration

Before writing to any EEPROM registers, the clock to the EEPROM module must be enabled, see page 326. A common setup is as follows: Block 0 has a password. Block 0 is readable by all, but only writable when unlocked. Block 0 has an ID and other public data. In this configuration, the ID is readable any time, but the rest of the EEPROM is locked to accesses by the application. The rest of the blocks only become available when parts of the application that are allowed to access the EEPROM choose to unlock block 0.
8.3
Register Map
Table 8-3 on page 523 lists the ROM Controller register and the Flash memory and control registers. The offset listed is a hexadecimal increment to the particular memory controller's base address. The Flash memory register offsets are relative to the Flash memory control base address of 0x400F.D000. The EEPROM registers are relative to the EEPROM base address of 0x400A.F000. The ROM and Flash memory protection register offsets are relative to the System Control base address of 0x400F.E000.
Table 8-3. Flash Register Map

Flash Memory Registers (Flash Control Offset) 0x000 0x004 0x008 FMA FMD FMC R/W R/W R/W 0x0000.0000 0x0000.0000 0x0000.0000 Flash Memory Address Flash Memory Data Flash Memory Control 526 527 528
523
Internal Memory
Table 8-3. Flash Register Map (continued)

Offset 0x00C 0x010 0x014 0x020 0x030 0x100 0x17C 0xFC0 0xFC4 0xFCC Name FCRIS FCIM FCMISC FMC2 FWBVAL FWBn FSIZE SSIZE ROMSWMAP Type RO R/W R/W1C R/W R/W R/W RO RO RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.007F 0x0000.007F 0x0000.0000 Description Flash Controller Raw Interrupt Status Flash Controller Interrupt Mask Flash Controller Masked Interrupt Status and Clear Flash Memory Control 2 Flash Write Buffer Valid Flash Write Buffer n Flash Size SRAM Size ROM Software Map See page 530 533 535 538 539 540 541 542 543
EEPROM Registers (EEPROM Control Offset) 0x000 0x004 0x008 0x010 0x014 0x018 0x01C 0x020 0x030 0x034 0x038 0x03C 0x040 0x050 0x080 0xFC0 EESIZE EEBLOCK EEOFFSET EERDWR EERDWRINC EEDONE EESUPP EEUNLOCK EEPROT EEPASS0 EEPASS1 EEPASS2 EEINT EEHIDE EEDBGME EEPROMPP RO R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W R/W R/W R/W RO 0x0020.0200 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.001F EEPROM Size Information EEPROM Current Block EEPROM Current Offset EEPROM Read-Write EEPROM Read-Write with Increment EEPROM Done Status EEPROM Support Control and Status EEPROM Unlock EEPROM Protection EEPROM Password EEPROM Password EEPROM Password EEPROM Interrupt EEPROM Block Hide EEPROM Debug Mass Erase EEPROM Peripheral Properties 544 545 546 547 548 549 551 553 554 555 555 555 556 557 558 559
Memory Registers (System Control Offset) 0x0F0 0x130 0x200 0x134 RMCTL FMPRE0 FMPRE0 FMPPE0 R/W1C R/W R/W R/W 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF ROM Control Flash Memory Protection Read Enable 0 Flash Memory Protection Read Enable 0 Flash Memory Protection Program Enable 0 560 561 561 562
April 25, 2012
Table 8-3. Flash Register Map (continued)

Offset 0x400 0x1D0 0x1E0 0x1E4 0x1E8 0x1EC 0x204 0x208 0x20C 0x404 0x408 0x40C Name FMPPE0 BOOTCFG USER_REG0 USER_REG1 USER_REG2 USER_REG3 FMPRE1 FMPRE2 FMPRE3 FMPPE1 FMPPE2 FMPPE3 Type R/W RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset 0xFFFF.FFFF 0xFFFF.FFFE 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF 0xFFFF.FFFF Description Flash Memory Protection Program Enable 0 Boot Configuration User Register 0 User Register 1 User Register 2 User Register 3 Flash Memory Protection Read Enable 1 Flash Memory Protection Read Enable 2 Flash Memory Protection Read Enable 3 Flash Memory Protection Program Enable 1 Flash Memory Protection Program Enable 2 Flash Memory Protection Program Enable 3 See page 562 564 567 567 567 567 561 561 561 562 562 562
8.4
Flash Memory Register Descriptions (Flash Control Offset)

This section lists and describes the Flash Memory registers, in numerical order by address offset. Registers in this section are relative to the Flash control base address of 0x400F.D000.
525
Internal Memory
Register 1: Flash Memory Address (FMA), offset 0x000

During a single word write operation, this register contains a 4-byte-aligned address and specifies where the data is written. During a write operation that uses the write buffer, this register contains a 128-byte (32-word) aligned address that specifies the start of the 32-word block to be written. During erase operations, this register contains a 1 KB-aligned CPU byte address and specifies which block is erased. Note that the alignment requirements must be met by software or the results of the operation are unpredictable.
Flash Memory Address (FMA)
Base 0x400F.D000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 OFFSET Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2
OFFSET R/W 0 1 R/W 0 0
R/W 0
R/W 0
Bit/Field 31:18
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Address Offset Address offset in Flash memory where operation is performed, except for non-volatile registers (see Non-Volatile Register Programming on page 517 for details on values for this field).
17:0
OFFSET
R/W
0x0
April 25, 2012
Register 2: Flash Memory Data (FMD), offset 0x004

This register contains the data to be written during the programming cycle. This register is not used during erase cycles.
Flash Memory Data (FMD)
31 30 29 28 27 26 25 24 DATA Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 DATA Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name DATA
Type R/W
Reset
Description
0x0000.0000 Data Value Data value for write operation.
527
Internal Memory
Register 3: Flash Memory Control (FMC), offset 0x008

When this register is written, the Flash memory controller initiates the appropriate access cycle for the location specified by the Flash Memory Address (FMA) register (see page 526). If the access is a write access, the data contained in the Flash Memory Data (FMD) register (see page 527) is written to the specified address. This register must be the final register written and initiates the memory operation. The four control bits in the lower byte of this register are used to initiate memory operations. Care must be taken not to set multiple control bits as the results of such an operation are unpredictable.
Flash Memory Control (FMC)
31 30 29 28 27 26 25 24 WRKEY Type Reset WO 0 15 WO 0 14 WO 0 13 WO 0 12 WO 0 11 WO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 WO 0 9 WO 0 8 WO 0 7 WO 0 6 WO 0 5 WO 0 4 WO 0 3 COMT R/W 0 WO 0 2 MERASE R/W 0 WO 0 1 ERASE R/W 0 WO 0 0 WRITE R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:16
Name WRKEY
Type WO
Reset 0x0000
Description Flash Memory Write Key This field contains a write key, which is used to minimize the incidence of accidental Flash memory writes. The value 0xA442 must be written into this field for a Flash memory write to occur. Writes to the FMC register without this WRKEY value are ignored. A read of this field returns the value 0.
15:4
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Commit Register Value This bit is used to commit writes to Flash-memory-resident registers and to monitor the progress of that process. Value Description 1 Set this bit to commit (write) the register value to a Flash-memory-resident register. When read, a 1 indicates that the previous commit access is not complete. 0 A write of 0 has no effect on the state of this bit. When read, a 0 indicates that the previous commit access is complete. See Non-Volatile Register Programming on page 517 for more information on programming Flash-memory-resident registers.
COMT
R/W
April 25, 2012
Bit/Field 2
Name MERASE
Type R/W
Reset 0
Description Mass Erase Flash Memory This bit is used to mass erase the Flash main memory and to monitor the progress of that process. Value Description 1 Set this bit to erase the Flash main memory. When read, a 1 indicates that the previous mass erase operation is not complete. 0 A write of 0 has no effect on the state of this bit. When read, a 0 indicates that the previous mass erase operation is complete. For information on erase time, see Flash Memory and EEPROM on page 1172.
ERASE
R/W
Erase a Page of Flash Memory This bit is used to erase a page of Flash memory and to monitor the progress of that process. Value Description 1 Set this bit to erase the Flash memory page specified by the contents of the FMA register. When read, a 1 indicates that the previous page erase operation is not complete. 0 A write of 0 has no effect on the state of this bit. When read, a 0 indicates that the previous page erase operation is complete. For information on erase time, see Flash Memory and EEPROM on page 1172.
WRITE
R/W
Write a Word into Flash Memory This bit is used to write a word into Flash memory and to monitor the progress of that process. Value Description 1 Set this bit to write the data stored in the FMD register into the Flash memory location specified by the contents of the FMA register. When read, a 1 indicates that the write update operation is not complete. 0 A write of 0 has no effect on the state of this bit. When read, a 0 indicates that the previous write update operation is complete. For information on programming time, see Flash Memory and EEPROM on page 1172.
529
Internal Memory
Register 4: Flash Controller Raw Interrupt Status (FCRIS), offset 0x00C

This register indicates that the Flash memory controller has an interrupt condition. An interrupt is sent to the interrupt controller only if the corresponding FCIM register bit is set.
Flash Controller Raw Interrupt Status (FCRIS)
Base 0x400F.D000 Offset 0x00C Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 ERRIS RO 0 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 ERIS RO 0 RO 0 1 PRIS RO 0 RO 0 0 ARIS RO 0
PROGRIS reserved RO 0 RO 0
INVDRIS VOLTRIS RO 0 RO 0
Bit/Field 31:14
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Program Verify Error Raw Interrupt Status Value Description 1 An interrupt is pending because the verify of a PROGRAM operation failed. If this error occurs when using the Flash write buffer, software must inspect the affected words to determine where the error occurred. An interrupt has not occurred.
13
PROGRIS
RO
This bit is cleared by writing a 1 to the PROGMISC bit in the FCMISC register. 12 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Erase Verify Error Raw Interrupt Status Value Description 1 An interrupt is pending because the verify of an ERASE operation failed. If this error occurs when using the Flash write buffer, software must inspect the affected words to determine where the error occurred. An interrupt has not occurred.
11
ERRIS
RO
This bit is cleared by writing a 1 to the ERMISC bit in the FCMISC register.
April 25, 2012
Bit/Field 10
Name INVDRIS
Type RO
Reset 0
Description Invalid Data Raw Interrupt Status Value Description 1 An interrupt is pending because a bit that was previously programmed as a 0 is now being requested to be programmed as a 1. An interrupt has not occurred.
This bit is cleared by writing a 1 to the INVMISC bit in the FCMISC register. 9 VOLTRIS RO 0 Pump Voltage Raw Interrupt Status Value Description 1 An interrupt is pending because the regulated voltage of the pump went out of spec during the Flash operation and the operation was terminated. An interrupt has not occurred.
This bit is cleared by writing a 1 to the VOLTMISC bit in the FCMISC register. 8:3 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Raw Interrupt Status This bit provides status EEPROM operation. Value Description 1 0 An EEPROM interrupt has occurred. An EEPROM interrupt has not occurred.
ERIS
RO
This bit is cleared by writing a 1 to the EMISC bit in the FCMISC register. 1 PRIS RO 0 Programming Raw Interrupt Status This bit provides status on programming cycles which are write or erase actions generated through the FMC or FMC2 register bits (see page 528 and page 538). Value Description 1 0 The programming or erase cycle has completed. The programming or erase cycle has not completed.
This status is sent to the interrupt controller when the PMASK bit in the FCIM register is set. This bit is cleared by writing a 1 to the PMISC bit in the FCMISC register.
531
Internal Memory
Bit/Field 0
Name ARIS
Type RO
Reset 0
Description Access Raw Interrupt Status Value Description 1 A program or erase action was attempted on a block of Flash memory that contradicts the protection policy for that block as set in the FMPPEn registers. No access has tried to improperly program or erase the Flash memory.
This status is sent to the interrupt controller when the AMASK bit in the FCIM register is set. This bit is cleared by writing a 1 to the AMISC bit in the FCMISC register.
April 25, 2012
Register 5: Flash Controller Interrupt Mask (FCIM), offset 0x010

This register controls whether the Flash memory controller generates interrupts to the controller.
Flash Controller Interrupt Mask (FCIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13

PROGMASK
RO 0 12
reserved
RO 0 11
RO 0 10
RO 0 9
RO 0 8
RO 0 7
RO 0 6
RO 0 5
RO 0 4
RO 0 3
RO 0 2 EMASK
RO 0 1 PMASK R/W 0
RO 0 0 AMASK R/W 0
ERMASK INVDMASK VOLTMASK R/W 0 R/W 0 R/W 0 RO 0 RO 0
reserved RO 0 RO 0 RO 0 RO 0
R/W 0
RO 0
R/W 0
Bit/Field 31:14
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PROGVER Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the PROGRIS bit is set. The PROGRIS interrupt is suppressed and not sent to the interrupt controller.
13
PROGMASK
R/W
12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ERVER Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the ERRIS bit is set. The ERRIS interrupt is suppressed and not sent to the interrupt controller.
11
ERMASK
R/W
10
INVDMASK
R/W
Invalid Data Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the INVDRIS bit is set. The INVDRIS interrupt is suppressed and not sent to the interrupt controller.
533
Internal Memory
Bit/Field 9
Name VOLTMASK
Type R/W
Reset 0
Description VOLT Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the VOLTRIS bit is set. The VOLTRIS interrupt is suppressed and not sent to the interrupt controller.
8:3
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the ERIS bit is set. The ERIS interrupt is suppressed and not sent to the interrupt controller.
EMASK
R/W
PMASK
R/W
Programming Interrupt Mask This bit controls the reporting of the programming raw interrupt status to the interrupt controller. Value Description 1 0 An interrupt is sent to the interrupt controller when the PRIS bit is set. The PRIS interrupt is suppressed and not sent to the interrupt controller.
AMASK
R/W
Access Interrupt Mask This bit controls the reporting of the access raw interrupt status to the interrupt controller. Value Description 1 0 An interrupt is sent to the interrupt controller when the ARIS bit is set. The ARIS interrupt is suppressed and not sent to the interrupt controller.
April 25, 2012
Register 6: Flash Controller Masked Interrupt Status and Clear (FCMISC), offset 0x014
This register provides two functions. First, it reports the cause of an interrupt by indicating which interrupt source or sources are signalling the interrupt. Second, it serves as the method to clear the interrupt reporting.
Flash Controller Masked Interrupt Status and Clear (FCMISC)
Base 0x400F.D000 Offset 0x014 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

PROGMISC
RO 0 12
reserved
RO 0 11
RO 0 10
RO 0 9
RO 0 8
RO 0 7
RO 0 6
RO 0 5
RO 0 4
RO 0 3
RO 0 2 EMISC
RO 0 1 PMISC R/W1C 0
RO 0 0 AMISC R/W1C 0
ERMISC INVDMISC VOLTMISC R/W1C 0 R/W1C 0 R/W1C 0 RO 0 RO 0
reserved RO 0 RO 0 RO 0 RO 0
R/W1C 0
RO 0
R/W1C 0
Bit/Field 31:14
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PROGVER Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled. Writing a 1 to this bit clears PROGMISC and also the PROGRIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that an interrupt has not occurred. A write of 0 has no effect on the state of this bit.
13
PROGMISC
R/W1C
12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ERVER Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled. Writing a 1 to this bit clears ERMISC and also the ERRIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that an interrupt has not occurred. A write of 0 has no effect on the state of this bit.
11
ERMISC
R/W1C
535
Internal Memory
Bit/Field 10
Name INVDMISC
Type R/W1C
Reset 0
Description Invalid Data Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled. Writing a 1 to this bit clears INVDMISC and also the INVDRIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that an interrupt has not occurred. A write of 0 has no effect on the state of this bit.
VOLTMISC
R/W1C
VOLT Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled. Writing a 1 to this bit clears VOLTMISC and also the VOLTRIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that an interrupt has not occurred. A write of 0 has no effect on the state of this bit.
8:3
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled. Writing a 1 to this bit clears EMISC and also the ERIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that an interrupt has not occurred. A write of 0 has no effect on the state of this bit.
EMISC
R/W1C
PMISC
R/W1C
Programming Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because a programming cycle completed. Writing a 1 to this bit clears PMISC and also the PRIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that a programming cycle complete interrupt has not occurred. A write of 0 has no effect on the state of this bit.
April 25, 2012
Bit/Field 0
Name AMISC
Type R/W1C
Reset 0
Description Access Masked Interrupt Status and Clear Value Description 1 When read, a 1 indicates that an unmasked interrupt was signaled because a program or erase action was attempted on a block of Flash memory that contradicts the protection policy for that block as set in the FMPPEn registers. Writing a 1 to this bit clears AMISC and also the ARIS bit in the FCRIS register (see page 530). 0 When read, a 0 indicates that no improper accesses have occurred. A write of 0 has no effect on the state of this bit.
537
Internal Memory
Register 7: Flash Memory Control 2 (FMC2), offset 0x020

When this register is written, the Flash memory controller initiates the appropriate access cycle for the location specified by the Flash Memory Address (FMA) register (see page 526). If the access is a write access, the data contained in the Flash Write Buffer (FWB) registers is written. This register must be the final register written as it initiates the memory operation.
Flash Memory Control 2 (FMC2)
31 30 29 28 27 26 25 24 WRKEY Type Reset WO 0 15 WO 0 14 WO 0 13 WO 0 12 WO 0 11 WO 0 10 WO 0 9 WO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 WO 0 7 WO 0 6 WO 0 5 WO 0 4 WO 0 3 WO 0 2 WO 0 1 WO 0 0 WRBUF R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:16
Name WRKEY
Type WO
Reset 0x0000
Description Flash Memory Write Key This field contains a write key, which is used to minimize the incidence of accidental Flash memory writes. The value 0xA442 must be written into this field for a write to occur. Writes to the FMC2 register without this WRKEY value are ignored. A read of this field returns the value 0.
15:1
reserved
RO
0x000
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Buffered Flash Memory Write This bit is used to start a buffered write to Flash memory. Value Description 1 Set this bit to write the data stored in the FWBn registers to the location specified by the contents of the FMA register. When read, a 1 indicates that the previous buffered Flash memory write access is not complete. 0 A write of 0 has no effect on the state of this bit. When read, a 0 indicates that the previous buffered Flash memory write access is complete. For information on programming time, see Flash Memory and EEPROM on page 1172.
WRBUF
R/W
April 25, 2012
Register 8: Flash Write Buffer Valid (FWBVAL), offset 0x030

This register provides a bitwise status of which FWBn registers have been written by the processor since the last write of the Flash memory write buffer. The entries with a 1 are written on the next write of the Flash memory write buffer. This register is cleared after the write operation by hardware. A protection violation on the write operation also clears this status. Software can program the same 32 words to various Flash memory locations by setting the FWB[n] bits after they are cleared by the write operation. The next write operation then uses the same data as the previous one. In addition, if a FWBn register change should not be written to Flash memory, software can clear the corresponding FWB[n] bit to preserve the existing data when the next write operation occurs.
Flash Write Buffer Valid (FWBVAL)
31 30 29 28 27 26 25 24 FWB[n] Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 FWB[n] Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name FWB[n]
Type R/W
Reset 0x0
Description Flash Memory Write Buffer Value Description 1 The corresponding FWBn register has been updated since the last buffer write operation and is ready to be written to Flash memory. The corresponding FWBn register has no new data to be written.
Bit 0 corresponds to FWB0, offset 0x100, and bit 31 corresponds to FWB31, offset 0x13C.
539
Internal Memory
Register 9: Flash Write Buffer n (FWBn), offset 0x100 - 0x17C

These 32 registers hold the contents of the data to be written into the Flash memory on a buffered Flash memory write operation. The offset selects one of the 32-bit registers. Only FWBn registers that have been updated since the preceding buffered Flash memory write operation are written into the Flash memory, so it is not necessary to write the entire bank of registers in order to write 1 or 2 words. The FWBn registers are written into the Flash memory with the FWB0 register corresponding to the address contained in FMA. FWB1 is written to the address FMA+0x4 etc. Note that only data bits that are 0 result in the Flash memory being modified. A data bit that is 1 leaves the content of the Flash memory bit at its previous value.
Flash Write Buffer n (FWBn)
Base 0x400F.D000 Offset 0x100 - 0x17C Type R/W, reset 0x0000.0000
Bit/Field 31:0
Name DATA
Type R/W
Reset
Description
0x0000.0000 Data Data to be written into the Flash memory.
April 25, 2012
Register 10: Flash Size (FSIZE), offset 0xFC0

This register indicates the size of the on-chip Flash memory. Important: This register should be used to determine the size of the Flash memory that is implemented on this microcontroller. However, to support legacy software, the DC0 register is available. A read of the DC0 register correctly identifies legacy memory sizes. Software must use the FSIZE register for memory sizes that are not listed in the DC0 register description.
Flash Size (FSIZE)
Base 0x400F.D000 Offset 0xFC0 Type RO, reset 0x0000.007F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 SIZE Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Flash Size Indicates the size of the on-chip Flash memory. Value Description
15:0
SIZE
RO
0x7F
0x0003 8 KB of Flash 0x0007 16 KB of Flash 0x000F 32 KB of Flash 0x001F 64 KB of Flash 0x002F 96 KB of Flash 0x003F 128 KB of Flash 0x005F 192 KB of Flash 0x007F 256 KB of Flash
541
Internal Memory
Register 11: SRAM Size (SSIZE), offset 0xFC4

This register indicates the size of the on-chip SRAM. Important: This register should be used to determine the size of the SRAM that is implemented on this microcontroller. However, to support legacy software, the DC0 register is available. A read of the DC0 register correctly identifies legacy memory sizes. Software must use the SSIZE register for memory sizes that are not listed in the DC0 register description.
SRAM Size (SSIZE)
Base 0x400F.D000 Offset 0xFC4 Type RO, reset 0x0000.007F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 SIZE Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SRAM Size Indicates the size of the on-chip SRAM. Value Description
15:0
SIZE
RO
0x7F
0x0007 2 KB of SRAM 0x000F 4 KB of SRAM 0x0017 6 KB of SRAM 0x001F 8 KB of SRAM 0x002F 12 KB of SRAM 0x003F 16 KB of SRAM 0x004F 20 KB of SRAM 0x005F 24 KB of SRAM 0x007F 32 KB of SRAM
April 25, 2012
Register 12: ROM Software Map (ROMSWMAP), offset 0xFCC

This register indicates the presence of third-party software in the on-chip ROM. Important: This register should be used to determine the presence of third-party software in the on-chip ROM on this microcontroller. However, to support legacy software, the NVMSTAT register is available. A read of the TPSW bit in the NVMSTAT register correctly identifies the presence of legacy third-party software. Software should use the ROMSWMAP register for software that is not on legacy devices.
ROM Software Map (ROMSWMAP)
Base 0x400F.D000 Offset 0xFCC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0

SAFERTOS
RO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SafeRTOS Present Value Description 0 1 SafeRTOS is not in the on-chip ROM. SafeRTOS is in the on-chip ROM.
SAFERTOS
RO
0x0
8.5
EEPROM Register Descriptions (EEPROM Offset)

This section lists and describes the EEPROM registers, in numerical order by address offset. Registers in this section are relative to the EEPROM base address of 0x400A.F000. Note that the EEPROM module clock must be enabled before the registers can be programmed (see page 326). There must be a delay of 3 system clocks after the EEPROM module clock is enabled before any EEPROM module registers are accessed. In addition, after enabling or resetting the EEPROM module, software must wait until the WORKING bit in the EEDONE register is clear before accessing any EEPROM registers.
543
Internal Memory
Register 13: EEPROM Size Information (EESIZE), offset 0x000

The EESIZE register indicates the number of 16-word blocks and 32-bit words in the EEPROM.
EEPROM Size Information (EESIZE)
Base 0x400A.F000 Offset 0x000 Type RO, reset 0x0020.0200
31 30 29 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 28 27 26 25 24 23 22 21 BLKCNT RO 1 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 20 19 18 17 16
WORDCNT Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
Bit/Field 31:27
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Number of 16-Word Blocks This value encoded in this field describes the number of 16-word blocks in the EEPROM.
26:16
BLKCNT
RO
0x20
15:0
WORDCNT
RO
0x200
Number of 32-Bit Words This value encoded in this field describes the number of 32-bit words in the EEPROM.
April 25, 2012
Register 14: EEPROM Current Block (EEBLOCK), offset 0x004

The EEBLOCK register is used to select the EEPROM block for subsequent reads, writes, and protection control. The value is a block offset into the EEPROM, such that the first block is 0, then second block is 1, etc. Each block contains 16 words. Attempts to set an invalid block causes the BLOCK field to be configured to 0. To verify that the intended block is being accessed, software can read the BLOCK field after it has been written. An invalid block can be either a non-existent block or a block that has been hidden using the EEHIDE register. Note that block 0 cannot be hidden.
EEPROM Current Block (EEBLOCK)
Base 0x400A.F000 Offset 0x004 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 BLOCK Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x00000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Current Block This field specifies the block in the EEPROM that is selected for subsequent accesses. Once this field is configured, the read-write registers operate against the specified block, using the EEOFFSET register to select the word within the block. Additionally, the protection and unlock registers are used for the selected block. The maximum value that can be written into this register is determined by the block count, as indicated by the EESIZE register. Attempts to write this field larger than the maximum number of blocks or to a locked block causes this field to be configured to 0.
15:0
BLOCK
R/W
0x0000
545
Internal Memory
Register 15: EEPROM Current Offset (EEOFFSET), offset 0x008

The EEOFFSET register is used to select the EEPROM word to read or write within the block selected by the EEBLOCK register. The value is a word offset into the block. Because accesses to the EERDWRINC register change the offset, software can read the contents of this register to determine the current offset.
EEPROM Current Offset (EEOFFSET)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 OFFSET R/W 0 R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Current Address Offset This value is the current address specified as an offset into the block selected by the EEBLOCK register. Once configured, the read-write registers, EERDRWR and EERDWRINC, operate against that address. The offset is automatically incremented by the EERDWRINC register, with wrap around within the block, which means the offset is incremented from 15 back to 0.
3:0
OFFSET
R/W
0x0
April 25, 2012
Register 16: EEPROM Read-Write (EERDWR), offset 0x010

The EERDWR register is used to read or write the EEPROM word at the address pointed to by the EEBLOCK and EEOFFSET registers. If the protection or access rules do not permit access, the operation is handled as follows: if reading is not allowed, the value 0xFFFF.FFFF is returned in all cases; if writing is not allowed, the EEDONE register is configured to indicate an error.
EEPROM Read-Write (EERDWR)
Base 0x400A.F000 Offset 0x010 Type R/W, reset 31 30 29 28 27 26 25 24 VALUE Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 VALUE Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name VALUE
Type R/W
Reset -
Description EEPROM Read or Write Data On a read, this field contains the value at the word pointed to by EEOFFSET. On a write, this field contains the data to be stored at the word pointed to by EEOFFSET. For writes, configuring this field starts the write process. If protection and access rules do not permit reads, all 1s are returned. If protection and access rules do not permit writes, the write fails and the EEDONE register indicates failure.
547
Internal Memory
Register 17: EEPROM Read-Write with Increment (EERDWRINC), offset 0x014

The EERDWRINC register is used to read or write the EEPROM word at the address pointed to by the EEBLOCK and EEOFFSET registers, and then increment the OFFSET field in the EEOFFSET register. If the protection or access rules do not permit access, the operation is handled as follows: if reading is not allowed, the value 0xFFFF.FFFF is returned in all cases; if writing is not allowed, the EEDONE register is configured to indicate an error. In all cases, the OFFSET field is incremented. If the last value is reached, OFFSET wraps around to 0 and points to the first word.
EEPROM Read-Write with Increment (EERDWRINC)
Base 0x400A.F000 Offset 0x014 Type R/W, reset 31 30 29 28 27 26 25 24 VALUE Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 VALUE Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name VALUE
Type R/W
Reset -
Description EEPROM Read or Write Data with Increment On a read, this field contains the value at the word pointed to by EEOFFSET. On a write, this field contains the data to be stored at the word pointed to by EEOFFSET. For writes, configuring this field starts the write process. If protection and access rules do not permit reads, all 1s are returned. If protection and access rules do not permit writes, the write fails and the EEDONE register indicates failure. Regardless of error, the OFFSET field in the EEOFFSET register is incremented by 1, and the value wraps around if the last word is reached.
April 25, 2012
Register 18: EEPROM Done Status (EEDONE), offset 0x018

The EEDONE register indicates the successful or failed completion of a write using the EERDWR or EERDWRINC register, protection set using the EEPROT register, password registered using the EEPASS register, copy buffer erase or program retry using the EESUPP register, or a debug mass erase using the EEDBGME register. The EEDONE register can be used with the EEINT register to generate an interrupt to report the status. The normal usage is to poll the EEDONE register or read the register after an interrupt is triggered. When the EEDONE bit 0 is set, then the operation is still in progress. When the EEDONE bit 0 is clear, then the value of EEDONE indicates the completion status. If EEDONE==0, then the write completed successfully. If EEDONE!=0, then an error occurred and the source of the error is given by the set bit(s). If an error occurs, corrective action may be taken as explained on page 551.
EEPROM Done Status (EEDONE)
Base 0x400A.F000 Offset 0x018 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 INVPL RO 0 RO 0 7 reserved RO 0 RO 0 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
WRBUSY NOPERM WKCOPY WKERASE reserved WORKING RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
Bit/Field 31:9
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Invalid Program Voltage Level Value Description 1 An error occurred during programming due to the voltage level dropping below the level required for EEPROM programming. This operation can be retried, however the voltage must be stabilized before retrying. No error
INVPL
RO
7:6
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Write Busy Value Description 1 0 An attempt to access the EEPROM was made while a write was in progress. No error
WRBUSY
RO
549
Internal Memory
Bit/Field 4
Name NOPERM
Type RO
Reset 0
Description Write Without Permission Value Description 1 An attempt was made to write without permission. This error can result because the block is locked, the write violates the programmed access protection, or when an attempt is made to write a password when the password has already been written. No error
WKCOPY
RO
Working on a Copy Value Description 1 0 A write is in progress and is waiting for the EEPROM to copy to or from the copy buffer. The EEPROM is not copying.
WKERASE
RO
Working on an Erase Value Description 1 0 A write is in progress and the original block is being erased after being copied. The EEPROM is not erasing.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EEPROM Working Value Description 1 0 The EEPROM is performing the requested operation. The EEPROM is not working.
WORKING
RO
April 25, 2012
Register 19: EEPROM Support Control and Status (EESUPP), offset 0x01C
The EESUPP register indicates if internal operations are required because an internal copy buffer must be erased or a programming failure has occurred and the operation must be completed. These conditions are explained below as well as in more detail in the section called Manual Copy Buffer Erase on page 522 and the section called Error During Programming on page 522. The EREQ bit is set if the internal copy buffer must be erased the next time it is used because it is full. To avoid the delay of waiting for the copy buffer to be erased on the next write, it can be erased manually using this register by setting the START bit. If either PRETRY or ERETRY is set indicating that an operation must be completed, setting the START bit causes the operation to be performed again. These bits are not changed by reset, so any condition that occurred before a reset is still indicated after a reset.
EEPROM Support Control and Status (EESUPP)
Base 0x400A.F000 Offset 0x01C Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 EREQ RO RO 0 0 START R/W 0
PRETRY ERETRY RO RO -
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Programming Must Be Retried Value Description 1 0 Programming from a copy in either direction failed to complete and must be restarted by setting the START bit. Programming has not failed.
PRETRY
RO
ERETRY
RO
Erase Must Be Retried Value Description 1 Erasing failed to complete and must be restarted by setting the START bit. If the failed erase is due to the erase of a main buffer, the copy will be performed after the erase completes successfully. Erasing has not failed.
551
Internal Memory
Bit/Field 1
Name EREQ
Type RO
Reset -
Description Erase Required Value Description 1 0 An erase of the copy buffer is required. The copy buffer has available space.
START
R/W
Start Erase Setting this bit starts error recovery if the PRETRY or ERETRY bit is set. If both the PRETRY and the ERETRY bits are clear, setting this bit starts erasing the copy buffer if EREQ is set. If none of the other bits in this register are set, setting this bit is ignored. After this bit is set, the WORKING bit in the EEDONE register is set and is cleared when the operation is complete. In addition, the EEINT register can be used to generate an interrupt on completion. If this bit is set while an operation is in progress, the write is ignored. The START bit is automatically cleared when the operation completes.
April 25, 2012
Register 20: EEPROM Unlock (EEUNLOCK), offset 0x020

The EEUNLOCK register can be used to unlock the whole EEPROM or a single block using a password. Unlocking is only required if a password is registered using the EEPASSn registers for the block that is selected by the EEBLOCK register. If block 0 has a password, it locks the remaining blocks from any type of access, but uses its own protection mechanism, for example readable, but not writable when locked. In addition, if block 0 has a password, it must be unlocked before unlocking any other block. The EEUNLOCK register is written between 1 and 3 times to form the 32-bit, 64-bit, or 96-bit password registered using the EEPASSn registers. The value used to configure the EEPASS0 register must always be written last. For example, for a 96-bit password, the value used to configure the EEPASS2 register must be written first followed by the EEPASS1 and EEPASS0 register values. The block or the whole EEPROM can be re-locked by writing 0xFFFF.FFFF to this register. In the event that an invalid value is written to this register, the block remains locked. The state of the EEPROM lock can be determined by reading back the EEUNLOCK register. If a multi-word password is set and the number of words written is incorrect, writing 0xFFFF.FFFF to this register reverts the EEPROM lock to the locked state, and the proper unlock sequence can be retried. Note that the internal logic is balanced to prevent any electrical or time-based attack being used to find the correct password or its length.
EEPROM Unlock (EEUNLOCK)
Base 0x400A.F000 Offset 0x020 Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
UNLOCK Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 UNLOCK Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0
Bit/Field 31:0
Name UNLOCK
Type R/W
Reset -
Description EEPROM Unlock Value Description 1 0 The EEPROM is unlocked. The EEPROM is locked.
The EEPROM is locked if the block referenced by the EEBLOCK register has a password registered, or if the master block (block 0) has a password. Unlocking is performed by writing the password to this register. The block or the EEPROM stays unlocked until it is locked again or until the next reset. It can be locked again by writing 0xFFFF.FFFF to this register.
553
Internal Memory
Register 21: EEPROM Protection (EEPROT), offset 0x030

The EEPROT register is used to set or read the protection for the current block, as selected by the EEBLOCK register. Protection and access control is used to determine when a block's contents can be read or written.
EEPROM Protection (EEPROT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 ACC R/W 0 R/W 0 RO 0 2 RO 0 1 PROT R/W 0 R/W 0 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Access Control Value Description 1 Only supervisor code may access this block of the EEPROM. DMA and Debug are also prevented from accessing the EEPROM. Both user and supervisor code may access this block of the EEPROM.
ACC
R/W
If this bit is set for block 0, then the whole EEPROM may only be accessed by supervisor code. 2:0 PROT R/W 0x0 Protection Control The Protection bits control what context is needed for reading and writing the block selected by the EEBLOCK register, or if block 0 is selected, all blocks. The following values are allowed: Value Description 0x0 This setting is the default. If there is no password, the block is not protected and is readable and writable. If there is a password, the block is readable, but only writable when unlocked. 0x1 If there is a password, the block is readable or writable only when unlocked. This value has no meaning when there is no password. 0x2 If there is no password, the block is readable, not writable. If there is a password, the block is readable only when unlocked, but is not writable under any conditions. 0x3 Reserved
April 25, 2012
Register 22: EEPROM Password (EEPASS0), offset 0x034 Register 23: EEPROM Password (EEPASS1), offset 0x038 Register 24: EEPROM Password (EEPASS2), offset 0x03C
The EEPASSn registers are used to configure a password for a block. A password may only be set once and cannot be changed. The password may be 32-bits, 64-bits, or 96-bits. Each word of the password can be any 32-bit value other than 0xFFFF.FFFF (all 1s). To set a password, the EEPASS0 register is written to with a value other than 0xFFFF.FFFF. When the write completes, as indicated in the EEDONE register, the application may choose to write to the EEPASS1 register with a value other than 0xFFFF.FFFF. When that write completes, the application may choose to write to the EEPASS2 register with a value other than 0xFFFF.FFFF to create a 96-bit password. The registers do not have to be written consecutively, and the EEPASS1 and EEPASS2 registers may be written at a later date. Based on whether 1, 2, or all 3 registers have been written, the unlock code also requires the same number of words to unlock. Note: Once the password is written, the block is not actually locked until either a reset occurs or 0xFFFF.FFFF is written to EEUNLOCK.
EEPROM Password (EEPASSn)

Base 0x400A.F000 Offset 0x034 Type R/W, reset 31 30 29 28 27 26 25 24 PASS Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 PASS Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name PASS
Type R/W
Reset -
Description Password This register reads as 0x1 if a password is registered for this block and 0x0 if no password is registered. A write to this register if it reads as 0x0 sets the password. If an attempt is made to write to this register when it reads as 0x1, the write is ignored and the NOPERM bit in the EEDONE register is set.
555
Internal Memory
Register 25: EEPROM Interrupt (EEINT), offset 0x040

The EEINT register is used to control whether an interrupt should be generated when a write to EEPROM completes as indicated by the EEDONE register value changing from 0x1 to any other value. If the INT bit in this register is set, the ERIS bit in the Flash Controller Raw Interrupt Status (FCRIS) register is set whenever the EEDONE register value changes from 0x1 as the Flash memory and the EEPROM share an interrupt vector.
EEPROM Interrupt (EEINT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 INT R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Enable Value Description 1 An interrupt is generated when the EEDONE register transitions from 1 to 0 or an error occurs. The EEDONE register provides status after a write to an offset location as well as a write to the password and protection bits. No interrupt is generated.
INT
R/W
April 25, 2012
Register 26: EEPROM Block Hide (EEHIDE), offset 0x050

The EEHIDE register is used to hide one or more blocks other than block 0. Once hidden, the block is not accessible until the next reset. This model allows initialization code to have access to data which is not visible to the rest of the application. This register also provides for additional security in that there is no password to search for in the code or data.
EEPROM Block Hide (EEHIDE)
31 30 29 28 27 26 25 24 Hn Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 Hn Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0
reserved
23
22
21
20
19
18
17
16
RO 0
Bit/Field 31:1
Name Hn
Type R/W
Reset 0x0000.000
Description Hide Block Value Description 1 The block number that corresponds to the bit number is hidden. A hidden block cannot be accessed, and the OFFSET value in the EEBLOCK register cannot be set to that block number. If an attempt is made to configure the OFFSET field to a hidden block, the EEBLOCK register is cleared. Any attempt to clear a bit in this register that is set is ignored. 0 The corresponding block is not hidden.
reserved
RO
557
Internal Memory
Register 27: EEPROM Debug Mass Erase (EEDBGME), offset 0x080

The EEDBGME register is used to mass erase the EEPROM block back to its default state from the factory. This register is intended to be used only for debug and test purposes, not in production environments. The erase takes place in such a way as to be secure. It first erases all data and then erases the protection mechanism. This register can only be written from supervisor mode by the core, and can also be written by the Stellaris debug controller when enabled. A key is used to avoid accidental use of this mechanism. Note that if a power down takes place while erasing, the mechanism should be used again to complete the operation. Powering off prematurely does not expose secured data. To start a mass erase, the whole register must be written as 0xE37B.0001. The register reads back as 0x1 until the erase is fully completed at which time it reads as 0x0. The EEDONE register is set to 0x1 when the erase is started and changes to 0x0 or an error when the mass erase is complete. Note that mass erasing the EEPROM block means that the wear-leveling counters are also reset to the factory default.
EEPROM Debug Mass Erase (EEDBGME)
31 30 29 28 27 26 25 24 KEY Type Reset WO 0 15 WO 0 14 WO 0 13 WO 0 12 WO 0 11 WO 0 10 WO 0 9 WO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 WO 0 7 WO 0 6 WO 0 5 WO 0 4 WO 0 3 WO 0 2 WO 0 1 WO 0 0 ME R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:16
Name KEY
Type WO
Reset 0x0000
Description Erase Key This field must be written with 0xE37B for the ME field to be effective.
15:1
reserved
RO
0x000
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Mass Erase Value Description 1 0 When written as a 1, the EEPROM is mass erased. This bit continues to read as 1 until the EEPROM is fully erased. No action.
ME
R/W
April 25, 2012
Register 28: EEPROM Peripheral Properties (EEPROMPP), offset 0xFC0

The EEPROMPP register indicates the size of the EEPROM for this part.
EEPROM Peripheral Properties (EEPROMPP)
Base 0x400A.F000 Offset 0xFC0 Type RO, reset 0x0000.001F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 SIZE RO 1 RO 1 RO 1 RO 0 1 RO 0 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 2-KB EEPROM Size
4:0
SIZE
RO
0x1F
8.6
Memory Register Descriptions (System Control Offset)

The remainder of this section lists and describes the registers that reside in the System Control address space, in numerical order by address offset. Registers in this section are relative to the System Control base address of 0x400F.E000.
559
Internal Memory
Register 29: ROM Control (RMCTL), offset 0x0F0

This register provides control of the ROM controller state. This register offset is relative to the System Control base address of 0x400F.E000. At reset, the following sequence is performed: 1. The BOOTCFG register is read. If the EN bit is clear, the ROM Boot Loader is executed. 2. In the ROM Boot Loader, the status of the specified GPIO pin is compared with the specified polarity. If the status matches the specified polarity, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 3. If the EN bit is set or the status doesn't match the specified polarity, the data at address 0x0000.0004 is read, and if the data at this address is 0xFFFF.FFFF, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 4. If there is data at address 0x0000.0004 that is not 0xFFFF.FFFF, the stack pointer (SP) is loaded from Flash memory at address 0x0000.0000 and the program counter (PC) is loaded from address 0x0000.0004. The user application begins executing.
ROM Control (RMCTL)
Base 0x400F.E000 Offset 0x0F0 Type R/W1C, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 BA R/W1C 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Boot Alias Value Description 1 0 The microcontroller's ROM appears at address 0x0. The Flash memory is at address 0x0.
BA
R/W1C
This bit is cleared by writing a 1 to this bit position.
April 25, 2012
Register 30: Flash Memory Protection Read Enable 0 (FMPRE0), offset 0x130 and 0x200 Register 31: Flash Memory Protection Read Enable 1 (FMPRE1), offset 0x204 Register 32: Flash Memory Protection Read Enable 2 (FMPRE2), offset 0x208 Register 33: Flash Memory Protection Read Enable 3 (FMPRE3), offset 0x20C
Note: Note: The FMPRE0 register is aliased for backwards compatibility. Offset is relative to System Control base address of 0x400F.E000.
This register stores the read-only protection bits for each 2-KB flash block (FMPPEn stores the execute-only bits). This register is loaded during the power-on reset sequence. The factory settings for the FMPREn and FMPPEn registers are a value of 1 for all implemented 2-KB blocks. This achieves a policy of open access and programmability. The register bits may be changed by writing the specific register bit. However, this register is R/W0; the user can only change the protection bit from a 1 to a 0 (and may NOT change a 0 to a 1). The changes are not permanent until the register is committed (saved), at which point the bit change is permanent. If a bit is changed from a 1 to a 0 and not committed, it may be restored by executing a power-on reset sequence. The reset value shown only applies to power-on reset; any other type of reset does not affect this register. Once committed, the only way to restore the factory default value of this register is to perform the sequence detailed in Recovering a "Locked" Microcontroller on page 201. Each FMPREn register controls a 64-k block of Flash. For additional information, see the "Flash Memory Protection" section. FMPRE0: 0 to 64 KB FMPRE1: 65 to 128 KB FMPRE2: 129 to 192 KB FMPRE3: 193 to 256 KB
Flash Memory Protection Read Enable n (FMPREn)

Base 0x400F.E000 Offset 0x130 and 0x200 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
READ_ENABLE Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0
READ_ENABLE Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1
Bit/Field 31:0
Name READ_ENABLE
Type R/W
Reset
Description
0xFFFF.FFFF Flash Read Enable Each bit configures a 2-KB flash block to be read only. The policies may be combined as shown in the table "Flash Protection Policy Combinations".
561
Internal Memory
Register 34: Flash Memory Protection Program Enable 0 (FMPPE0), offset 0x134 and 0x400 Register 35: Flash Memory Protection Program Enable 1 (FMPPE1), offset 0x404 Register 36: Flash Memory Protection Program Enable 2 (FMPPE2), offset 0x408 Register 37: Flash Memory Protection Program Enable 3 (FMPPE3), offset 0x40C
Note: Note: The FMPPE0 register is aliased for backwards compatibility. Offset is relative to System Control base address of 0x400FE000.
This register stores the execute-only protection bits for each 2-KB flash block (FMPREn stores the read-only protection bits). This register is loaded during the power-on reset sequence. The factory settings for the FMPREn and FMPPEn registers are a value of 1 for all implemented banks. This achieves a policy of open access and programmability. The register bits may be changed by writing the specific register bit. However, this register is R/W0; the user can only change the protection bit from a 1 to a 0 (and may NOT change a 0 to a 1). The changes are not permanent until the register is committed (saved), at which point the bit change is permanent. If a bit is changed from a 1 to a 0 and not committed, it may be restored by executing a power-on reset sequence. The reset value shown only applies to power-on reset; any other type of reset does not affect this register. Once committed, the only way to restore the factory default value of this register is to perform the sequence detailed in Recovering a "Locked" Microcontroller on page 201. For additional information, see the "Flash Memory Protection" section. Each FMPPEn register controls a 64-k block of Flash. For additional information, see the "Flash Memory Protection" section. FMPPE0: 0 to 64 KB FMPPE1: 65 to 128 KB FMPPE2: 129 to 192 KB FMPPE3: 193 to 256 KB
Flash Memory Protection Program Enable n (FMPPEn)

Base 0x400F.E000 Offset 0x134 and 0x400 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
PROG_ENABLE Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0
PROG_ENABLE Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1
April 25, 2012
Bit/Field 31:0
Name PROG_ENABLE
Type R/W
Reset
Description
0xFFFF.FFFF Flash Programming Enable Each bit configures a 2-KB flash block to be execute only. The policies may be combined as shown in the table "Flash Protection Policy Combinations".
563
Internal Memory
Register 38: Boot Configuration (BOOTCFG), offset 0x1D0

Note: Offset is relative to System Control base address of 0x400F.E000. This register is not written directly, but instead uses the FMD register as explained in Non-Volatile Register Programming on page 517. This register provides configuration of a GPIO pin to enable the ROM Boot Loader as well as a write-once mechanism to disable external debugger access to the device. At reset, the user has the opportunity to direct the core to execute the ROM Boot Loader or the application in Flash memory by using any GPIO signal from Ports A-Q as configured by the bits in this register. At reset, the following sequence is performed: 1. The BOOTCFG register is read. If the EN bit is clear, the ROM Boot Loader is executed. 2. In the ROM Boot Loader, the status of the specified GPIO pin is compared with the specified polarity. If the status matches the specified polarity, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 3. If the EN bit is set or the status doesn't match the specified polarity, the data at address 0x0000.0004 is read, and if the data at this address is 0xFFFF.FFFF, the ROM is mapped to address 0x0000.0000 and execution continues out of the ROM Boot Loader. 4. If there is data at address 0x0000.0004 that is not 0xFFFF.FFFF, the stack pointer (SP) is loaded from Flash memory at address 0x0000.0000 and the program counter (PC) is loaded from address 0x0000.0004. The user application begins executing. The DBG0 bit is cleared by the factory and the DBG1 bit is set, which enables external debuggers. Clearing the DBG1 bit disables any external debugger access to the device, starting with the next power-up cycle of the device. The NW bit indicates that bits in the register can be changed from 1 to 0. Software can clear the NW bit to prevent further changes to the bits in this register. By committing the register values using the COMT bit in the FMC register, the register contents become non-volatile and are therefore retained following power cycling. Prior to being committed, bits can only be changed from 1 to 0. The reset value shown only applies to power-on reset when the register is not yet committed; any other type of reset does not affect this register. Once committed, the register retains its value through power-on reset. Once committed, the only way to restore the factory default value of this register is to perform the sequence detailed in Recovering a "Locked" Microcontroller on page 201.
Boot Configuration (BOOTCFG)
Base 0x400F.E000 Offset 0x1D0 Type RO, reset 0xFFFF.FFFE
31 NW Type Reset RO 1 15 RO 1 14 PORT Type Reset RO 1 RO 1 RO 1 RO 1 RO 1 13 RO 1 12 RO 1 11 PIN RO 1 RO 1 RO 1 10 RO 1 9 POL RO 1 RO 1 8 EN RO 1 RO 1 RO 1 30 29 28 27 26 25 24 23 reserved RO 1 7 RO 1 6 RO 1 5 reserved RO 1 RO 1 RO 1 RO 1 RO 1 4 RO 1 3 RO 1 2 RO 1 1 DBG1 RO 1 RO 1 0 DBG0 RO 0 22 21 20 19 18 17 16
April 25, 2012
Bit/Field 31
Name NW
Type RO
Reset 1
Description Not Written When set, this bit indicates that the values in this register can be changed from 1 to 0. When clear, this bit specifies that the contents of this register cannot be changed.
30:16
reserved
RO
0xFFFF
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Boot GPIO Port This field selects the port of the GPIO port pin that enables the ROM boot loader at reset. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Port A Port B Port C Port D Port E Port F Port G Port H
15:13
PORT
RO
0x7
12:10
PIN
RO
0x7
Boot GPIO Pin This field selects the pin number of the GPIO port pin that enables the ROM boot loader at reset. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Pin 0 Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 Pin 7
POL
RO
Boot GPIO Polarity When set, this bit selects a high level for the GPIO port pin to enable the ROM boot loader at reset. When clear, this bit selects a low level for the GPIO port pin.
EN
RO
Boot GPIO Enable Clearing this bit enables the use of a GPIO pin to enable the ROM Boot Loader at reset. When this bit is set, the contents of address 0x0000.0004 are checked to see if the Flash memory has been programmed. If the contents are not 0xFFFF.FFFF, the core executes out of Flash memory. If the Flash has not been programmed, the core executes out of ROM.
565
Internal Memory
Bit/Field 7:2
Name reserved
Type RO
Reset 0x3F
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Debug Control 1 The DBG1 bit must be 1 and DBG0 must be 0 for debug to be available.
DBG1
RO
DBG0
RO
Debug Control 0 The DBG1 bit must be 1 and DBG0 must be 0 for debug to be available.
April 25, 2012
Register 39: User Register 0 (USER_REG0), offset 0x1E0 Register 40: User Register 1 (USER_REG1), offset 0x1E4 Register 41: User Register 2 (USER_REG2), offset 0x1E8 Register 42: User Register 3 (USER_REG3), offset 0x1EC
Note: Offset is relative to System Control base address of 0x400F.E000. These registers each provide 32 bits of user-defined data that is non-volatile. Bits can only be changed from 1 to 0. The reset value shown only applies to power-on reset when the register is not yet committed; any other type of reset does not affect this register. Once committed, the register retains its value through power-on reset. Once committed, the only way to restore the factory default value of this register is to perform the sequence detailed in Recovering a "Locked" Microcontroller on page 201.
User Register n (USER_REGn)
Base 0x400F.E000 Offset 0x1E0 Type R/W, reset 0xFFFF.FFFF
Bit/Field 31:0
Name DATA
Type R/W
Reset
Description
0xFFFF.FFFF User Data Contains the user data value. This field is initialized to all 1s and once committed, retains its value through power-on reset.
567
Micro Direct Memory Access (DMA)

The LM4F120H5QR microcontroller includes a Direct Memory Access (DMA) controller, known as micro-DMA (DMA). The DMA controller provides a way to offload data transfer tasks from the Cortex-M4F processor, allowing for more efficient use of the processor and the available bus bandwidth. The DMA controller can perform transfers between memory and peripherals. It has dedicated channels for each supported on-chip module and can be programmed to automatically perform transfers between peripherals and memory as the peripheral is ready to transfer more data. The DMA controller provides the following features: ARM PrimeCell 32-channel configurable DMA controller Support for memory-to-memory, memory-to-peripheral, and peripheral-to-memory in multiple transfer modes Basic for simple transfer scenarios Ping-pong for continuous data flow Scatter-gather for a programmable list of arbitrary transfers initiated from a single request Highly flexible and configurable channel operation Independently configured and operated channels Dedicated channels for supported on-chip modules Flexible channel assignments One channel each for receive and transmit path for bidirectional modules Dedicated channel for software-initiated transfers Per-channel configurable priority scheme Optional software-initiated requests for any channel Two levels of priority Design optimizations for improved bus access performance between DMA controller and the processor core DMA controller access is subordinate to core access RAM striping Peripheral bus segmentation Data sizes of 8, 16, and 32 bits Transfer size is programmable in binary steps from 1 to 1024 Source and destination address increment size of byte, half-word, word, or no increment Maskable peripheral requests

April 25, 2012
Interrupt on transfer completion, with a separate interrupt per channel
9.1
Block Diagram
Figure 9-1. DMA Block Diagram
DMA error
uDMA Controller
request done
System Memory CH Control Table
Peripheral DMA Channel 0 Peripheral DMA Channel N-1
request done
Nested Vectored Interrupt Controller (NVIC)
IRQ
General Peripheral N Registers
request done
ARM Cortex-M4F
DMASTAT DMACFG DMACTLBASE DMAALTBASE DMAWAITSTAT DMASWREQ DMAUSEBURSTSET DMAUSEBURSTCLR DMAREQMASKSET DMAREQMASKCLR DMAENASET DMAENACLR DMAALTSET DMAALTCLR DMAPRIOSET DMAPRIOCLR DMAERRCLR DMACHASGN DMACHIS DMACHMAPn
DMASRCENDP DMADSTENDP DMACHCTRL DMASRCENDP DMADSTENDP DMACHCTRL
Transfer Buffers Used by DMA
9.2
The DMA controller is a flexible and highly configurable DMA controller designed to work efficiently with the microcontroller's Cortex-M4F processor core. It supports multiple data sizes and address increment schemes, multiple levels of priority among DMA channels, and several transfer modes to allow for sophisticated programmed data transfers. The DMA controller's usage of the bus is always subordinate to the processor core, so it never holds up a bus transaction by the processor. Because the DMA controller is only using otherwise-idle bus cycles, the data transfer bandwidth it provides is essentially free, with no impact on the rest of the system. The bus architecture has been optimized to greatly enhance the ability of the processor core and the DMA controller to efficiently share the on-chip bus, thus improving performance. The optimizations include RAM striping and peripheral bus segmentation, which in many cases allow both the processor core and the DMA controller to access the bus and perform simultaneous data transfers. The DMA controller can transfer data to and from the on-chip SRAM. However, because the Flash memory and ROM are located on a separate internal bus, it is not possible to transfer data from the Flash memory or ROM with the DMA controller. Each peripheral function that is supported has a dedicated channel on the DMA controller that can be configured independently. The DMA controller implements a unique configuration method using channel control structures that are maintained in system memory by the processor. While simple transfer modes are supported, it is also possible to build up sophisticated "task" lists in memory that allow the DMA controller to perform arbitrary-sized transfers to and from arbitrary locations as part of a single transfer request. The DMA controller also supports the use of ping-pong buffering to accommodate constant streaming of data to or from a peripheral.
569
Each channel also has a configurable arbitration size. The arbitration size is the number of items that are transferred in a burst before the DMA controller rearbitrates for channel priority. Using the arbitration size, it is possible to control exactly how many items are transferred to or from a peripheral each time it makes a DMA service request.
9.2.1
Channel Assignments
Each DMA channel has up to five possible assignments which are selected using the DMA Channel Map Select n (DMACHMAPn) registers with 4-bit assignment fields for each DMA channel. Table 9-1 on page 570 shows the DMA channel mapping. The Enc. column shows the encoding for the respective DMACHMAPn bit field. Encodings 0x5 - 0xF are all reserved. To support legacy software which uses the DMA Channel Assignment (DMACHASGN) register, Enc. 0 is equivalent to a DMACHASGN bit being clear, and Enc. 1 is equivalent to a DMACHASGN bit being set. If the DMACHASGN register is read, bit fields return 0 if the corresponding DMACHMAPn register field value are equal to 0, otherwise they return 1 if the corresponding DMACHMAPn register field values are not equal to 0. The Type indication in the table indicates if a particular peripheral uses a single request (S), burst request (B) or either (SB). Note: Channels noted in the table as "Available for software" may be assigned to peripherals in the future. However, they are currently available for software use. Channel 30 is dedicated for software use. The USB endpoints mapped to DMA channels 0-3 can be changed with the USBDMASEL register (see page 1118).
Table 9-1. DMA Channel Assignments

Enc. Ch # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 0 Peripheral USB0 EP1 RX USB0 EP1 TX USB0 EP2 RX USB0 EP2 TX USB0 EP3 RX USB0 EP3 TX Software Software UART0 RX UART0 TX SSI0 RX SSI0 TX Software Software ADC0 SS0 ADC0 SS1 ADC0 SS2 ADC0 SS3 GPTimer 0A GPTimer 0B GPTimer 1A Type SB B B B B B B B SB SB SB SB B B B B B B B B B 1 Peripheral UART2 RX UART2 TX GPTimer 3A GPTimer 3B GPTimer 2A GPTimer 2B GPTimer 2A GPTimer 2B UART1 RX UART1 TX SSI1 RX SSI1 TX UART2 RX UART2 TX GPTimer 2A GPTimer 2B Software Software GPTimer 1A GPTimer 1B Software Type SB SB B B B B B B SB SB SB SB SB SB B B B B B B B 2 Peripheral Software Software Software Software Software Software UART5 RX UART5 TX Software Software UART6 RX UART6 TX SSI2 RX SSI2 TX SSI3 RX SSI3 TX UART3 RX UART3 TX UART4 RX UART4 TX UART7 RX Type B B B B B B SB SB B B SB SB SB SB SB SB SB SB SB SB SB 3 Peripheral GPTimer 4A GPTimer 4B Software Software GPIO A GPIO B GPIO C GPIO D GPTimer 5A GPTimer 5B GPTimer 6A GPTimer 6B GPTimer 7A GPTimer 7B GPIO E GPIO F GPTimer 8A GPTimer 8B GPIO B Software Software Type B B B B B B B B B B B B B B B B B B B B B 4 Peripheral Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Software Type B B B B B B B B B B B B B B B B B B B B B
April 25, 2012
Table 9-1. DMA Channel Assignments (continued)

Enc. Ch # 21 22 23 24 25 26 27 28 29 30 31 0 Peripheral GPTimer 1B UART1 RX UART1 TX SSI1 RX SSI1 TX Software Software Software Software Software Reserved Type B SB SB SB SB B B B B B B 1 Peripheral Software Software Software ADC1 SS0 ADC1 SS1 ADC1 SS2 ADC1 SS3 Software Software Software Reserved Type B B B B B B B B B B B 2 Peripheral UART7 TX Software Software Software Software Software Software Software Software Software Reserved Type SB B B B B B B B B B B 3 Peripheral Software Software Software GPTimer 9A GPTimer 9B GPTimer 10A GPTimer 10B GPTimer 11A GPTimer 11B Software Reserved Type B B B B B B B B B B B 4 Peripheral Software Software Software Software Software Software Software Software Software Software Reserved Type B B B B B B B B B B B
9.2.2
Priority
The DMA controller assigns priority to each channel based on the channel number and the priority level bit for the channel. Channel number 0 has the highest priority and as the channel number increases, the priority of a channel decreases. Each channel has a priority level bit to provide two levels of priority: default priority and high priority. If the priority level bit is set, then that channel has higher priority than all other channels at default priority. If multiple channels are set for high priority, then the channel number is used to determine relative priority among all the high priority channels. The priority bit for a channel can be set using the DMA Channel Priority Set (DMAPRIOSET) register and cleared with the DMA Channel Priority Clear (DMAPRIOCLR) register.
9.2.3
Arbitration Size
When a DMA channel requests a transfer, the DMA controller arbitrates among all the channels making a request and services the DMA channel with the highest priority. Once a transfer begins, it continues for a selectable number of transfers before rearbitrating among the requesting channels again. The arbitration size can be configured for each channel, ranging from 1 to 1024 item transfers. After the DMA controller transfers the number of items specified by the arbitration size, it then checks among all the channels making a request and services the channel with the highest priority. If a lower priority DMA channel uses a large arbitration size, the latency for higher priority channels is increased because the DMA controller completes the lower priority burst before checking for higher priority requests. Therefore, lower priority channels should not use a large arbitration size for best response on high priority channels. The arbitration size can also be thought of as a burst size. It is the maximum number of items that are transferred at any one time in a burst. Here, the term arbitration refers to determination of DMA channel priority, not arbitration for the bus. When the DMA controller arbitrates for the bus, the processor always takes priority. Furthermore, the DMA controller is held off whenever the processor must perform a bus transaction on the same bus, even in the middle of a burst transfer.
9.2.4
Request Types
The DMA controller responds to two types of requests from a peripheral: single or burst. Each peripheral may support either or both types of requests. A single request means that the peripheral
571
is ready to transfer one item, while a burst request means that the peripheral is ready to transfer multiple items. The DMA controller responds differently depending on whether the peripheral is making a single request or a burst request. If both are asserted, and the DMA channel has been set up for a burst transfer, then the burst request takes precedence. See Table 9-2 on page 572, which shows how each peripheral supports the two request types. Table 9-2. Request Type Support
Peripheral ADC General-Purpose Timer GPIO SSI TX SSI RX UART TX UART RX USB TX USB RX Single Request Signal None None Raw interrupt pulse TX FIFO Not Full RX FIFO Not Empty TX FIFO Not Full RX FIFO Not Empty None None Burst Request Signal Sequencer IE bit Trigger event None TX FIFO Level (fixed at 4) RX FIFO Level (fixed at 4) TX FIFO Level (configurable) RX FIFO Level (configurable) FIFO TXRDY FIFO RXRDY
9.2.4.1
Single Request
When a single request is detected, and not a burst request, the DMA controller transfers one item and then stops to wait for another request.
9.2.4.2
Burst Request
When a burst request is detected, the DMA controller transfers the number of items that is the lesser of the arbitration size or the number of items remaining in the transfer. Therefore, the arbitration size should be the same as the number of data items that the peripheral can accommodate when making a burst request. For example, the UART generates a burst request based on the FIFO trigger level. In this case, the arbitration size should be set to the amount of data that the FIFO can transfer when the trigger level is reached. A burst transfer runs to completion once it is started, and cannot be interrupted, even by a higher priority channel. Burst transfers complete in a shorter time than the same number of non-burst transfers. It may be desirable to use only burst transfers and not allow single transfers. For example, perhaps the nature of the data is such that it only makes sense when transferred together as a single unit rather than one piece at a time. The single request can be disabled by using the DMA Channel Useburst Set (DMAUSEBURSTSET) register. By setting the bit for a channel in this register, the DMA controller only responds to burst requests for that channel.
9.2.5
Channel Configuration
The DMA controller uses an area of system memory to store a set of channel control structures in a table. The control table may have one or two entries for each DMA channel. Each entry in the table structure contains source and destination pointers, transfer size, and transfer mode. The control table can be located anywhere in system memory, but it must be contiguous and aligned on a 1024-byte boundary. Table 9-3 on page 573 shows the layout in memory of the channel control table. Each channel may have one or two control structures in the control table: a primary control structure and an optional alternate control structure. The table is organized so that all of the primary entries are in the first
April 25, 2012
half of the table, and all the alternate structures are in the second half of the table. The primary entry is used for simple transfer modes where transfers can be reconfigured and restarted after each transfer is complete. In this case, the alternate control structures are not used and therefore only the first half of the table must be allocated in memory; the second half of the control table is not necessary, and that memory can be used for something else. If a more complex transfer mode is used such as ping-pong or scatter-gather, then the alternate control structure is also used and memory space should be allocated for the entire table. Any unused memory in the control table may be used by the application. This includes the control structures for any channels that are unused by the application as well as the unused control word for each channel. Table 9-3. Control Structure Memory Map
Offset 0x0 0x10 ... 0x1F0 0x200 0x210 ... 0x3F0 Channel 0, Primary 1, Primary ... 31, Primary 0, Alternate 1, Alternate ... 31, Alternate
Table 9-4 shows an individual control structure entry in the control table. Each entry is aligned on a 16-byte boundary. The entry contains four long words: the source end pointer, the destination end pointer, the control word, and an unused entry. The end pointers point to the ending address of the transfer and are inclusive. If the source or destination is non-incrementing (as for a peripheral register), then the pointer should point to the transfer address. Table 9-4. Channel Control Structure
Offset 0x000 0x004 0x008 0x00C Description Source End Pointer Destination End Pointer Control Word Unused
The control word contains the following fields: Source and destination data sizes Source and destination address increment size Number of transfers before bus arbitration Total number of items to transfer Useburst flag Transfer mode
573
The control word and each field are described in detail in DMA Channel Control Structure on page 591. The DMA controller updates the transfer size and transfer mode fields as the transfer is performed. At the end of a transfer, the transfer size indicates 0, and the transfer mode indicates "stopped." Because the control word is modified by the DMA controller, it must be reconfigured before each new transfer. The source and destination end pointers are not modified, so they can be left unchanged if the source or destination addresses remain the same. Prior to starting a transfer, a DMA channel must be enabled by setting the appropriate bit in the DMA Channel Enable Set (DMAENASET) register. A channel can be disabled by setting the channel bit in the DMA Channel Enable Clear (DMAENACLR) register. At the end of a complete DMA transfer, the controller automatically disables the channel.
9.2.6
Transfer Modes
The DMA controller supports several transfer modes. Two of the modes support simple one-time transfers. Several complex modes support a continuous flow of data.
9.2.6.1
Stop Mode
While Stop is not actually a transfer mode, it is a valid value for the mode field of the control word. When the mode field has this value, the DMA controller does not perform any transfers and disables the channel if it is enabled. At the end of a transfer, the DMA controller updates the control word to set the mode to Stop.
9.2.6.2
Basic Mode
In Basic mode, the DMA controller performs transfers as long as there are more items to transfer, and a transfer request is present. This mode is used with peripherals that assert a DMA request signal whenever the peripheral is ready for a data transfer. Basic mode should not be used in any situation where the request is momentary even though the entire transfer should be completed. For example, a software-initiated transfer creates a momentary request, and in Basic mode, only the number of transfers specified by the ARBSIZE field in the DMA Channel Control Word (DMACHCTL) register is transferred on a software request, even if there is more data to transfer. When all of the items have been transferred using Basic mode, the DMA controller sets the mode for that channel to Stop.
9.2.6.3
Auto Mode
Auto mode is similar to Basic mode, except that once a transfer request is received, the transfer runs to completion, even if the DMA request is removed. This mode is suitable for software-triggered transfers. Generally, Auto mode is not used with a peripheral. When all the items have been transferred using Auto mode, the DMA controller sets the mode for that channel to Stop.
9.2.6.4
Ping-Pong
Ping-Pong mode is used to support a continuous data flow to or from a peripheral. To use Ping-Pong mode, both the primary and alternate data structures must be implemented. Both structures are set up by the processor for data transfer between memory and a peripheral. The transfer is started using the primary control structure. When the transfer using the primary control structure is complete, the DMA controller reads the alternate control structure for that channel to continue the transfer. Each time this happens, an interrupt is generated, and the processor can reload the control structure for the just-completed transfer. Data flow can continue indefinitely this way, using the primary and alternate control structures to switch back and forth between buffers as the data flows to or from the peripheral.
April 25, 2012
Refer to Figure 9-2 on page 575 for an example showing operation in Ping-Pong mode. Figure 9-2. Example of Ping-Pong DMA Transaction
DMA Controller SOURCE DEST CONTROL Unused
transfer continues using alternate transfers using BUFFER A
Cortex-M3 Processor BUFFER A
Primary Structure
Pe rip
he ral /D M
AI
nte rru p
Alternate Structure
SOURCE DEST CONTROL Unused

transfer continues using primary
transfers using BUFFER B
BUFFER B
Process data in BUFFER A Reload primary structure
Pe
rip
he
Time
ral
/D M
AI
nte
rru pt
Primary Structure

transfer continues using alternate
transfers using BUFFER A
BUFFER A
Process data in BUFFER B Reload alternate structure
Pe
rip
he
ral
/D M
AI
nte
rru
pt
Alternate Structure
transfers using BUFFER B
BUFFER B
Process data in BUFFER B Reload alternate structure
9.2.6.5
Memory Scatter-Gather
Memory Scatter-Gather mode is a complex mode used when data must be transferred to or from varied locations in memory instead of a set of contiguous locations in a memory buffer. For example,
575
a gather DMA operation could be used to selectively read the payload of several stored packets of a communication protocol and store them together in sequence in a memory buffer. In Memory Scatter-Gather mode, the primary control structure is used to program the alternate control structure from a table in memory. The table is set up by the processor software and contains a list of control structures, each containing the source and destination end pointers, and the control word for a specific transfer. The mode of each control word must be set to Scatter-Gather mode. Each entry in the table is copied in turn to the alternate structure where it is then executed. The DMA controller alternates between using the primary control structure to copy the next transfer instruction from the list and then executing the new transfer instruction. The end of the list is marked by programming the control word for the last entry to use Auto transfer mode. Once the last transfer is performed using Auto mode, the DMA controller stops. A completion interrupt is generated only after the last transfer. It is possible to loop the list by having the last entry copy the primary control structure to point back to the beginning of the list (or to a new list). It is also possible to trigger a set of other channels to perform a transfer, either directly, by programming a write to the software trigger for another channel, or indirectly, by causing a peripheral action that results in a DMA request. By programming the DMA controller using this method, a set of arbitrary transfers can be performed based on a single DMA request. Refer to Figure 9-3 on page 577 and Figure 9-4 on page 578, which show an example of operation in Memory Scatter-Gather mode. This example shows a gather operation, where data in three separate buffers in memory is copied together into one buffer. Figure 9-3 on page 577 shows how the application sets up a DMA task list in memory that is used by the controller to perform three sets of copy operations from different locations in memory. The primary control structure for the channel that is used for the operation is configured to copy from the task list to the alternate control structure. Figure 9-4 on page 578 shows the sequence as the DMA controller performs the three sets of copy operations. First, using the primary control structure, the DMA controller loads the alternate control structure with task A. It then performs the copy operation specified by task A, copying the data from the source buffer A to the destination buffer. Next, the DMA controller again uses the primary control structure to load task B into the alternate control structure, and then performs the B operation with the alternate control structure. The process is repeated for task C.
April 25, 2012
Figure 9-3. Memory Scatter-Gather, Setup and Configuration

1 Source and Destination Buffer in Memory 2 Task List in Memory 3 Channel Control Table in Memory
4 WORDS (SRC A) A
SRC DST ITEMS=4 Unused SRC DST TASK A SRC DST ITEMS=12 TASK B
Channel Primary Control Structure
16 WORDS (SRC B) B
ITEMS=16 Unused SRC DST ITEMS=1 Unused
TASK C
SRC DST ITEMS=n
Channel Alternate Control Structure
1 WORD (SRC C) C
4 (DEST A)
16 (DEST B)
1 (DEST C)
NOTES: 1. Application has a need to copy data items from three separate locations in memory into one combined buffer. 2. Application sets up DMA task list in memory, which contains the pointers and control configuration for three DMA copy tasks. 3. Application sets up the channel primary control structure to copy each task configuration, one at a time, to the alternate control structure, where it is executed by the DMA controller. 4. The SRC and DST pointers in the task list must point to the last location in the corresponding buffer.
577
Figure 9-4. Memory Scatter-Gather, DMA Copy Sequence

Task List in Memory DMA Control Table in Memory Buffers in Memory SRC A
SRC
PRI
DST
SRC B
COPIED SRC
TASK A TASK B TASK C

COPIED
SRC C
ALT
DST
DEST A DEST B DEST C
Using the channels primary control structure, the DMA controller copies task A configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer A to the destination buffer.
Task List in Memory
DMA Control Table in Memory
Buffers in Memory
SRC A
SRC
SRC B PRI
DST

COPIED
SRC
SRC C
COPIED
ALT
DST
Using the channels primary control structure, the DMA controller copies task B configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer B to the destination buffer.
Task List in Memory
Buffers in Memory
SRC A
SRC
PRI
DST
SRC B

COPIED
SRC
SRC C
ALT
DST
COPIED
Using the channels primary control structure, the DMA controller copies task C configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer C to the destination buffer.
April 25, 2012
9.2.6.6
Peripheral Scatter-Gather
Peripheral Scatter-Gather mode is very similar to Memory Scatter-Gather, except that the transfers are controlled by a peripheral making a DMA request. Upon detecting a request from the peripheral, the DMA controller uses the primary control structure to copy one entry from the list to the alternate control structure and then performs the transfer. At the end of this transfer, the next transfer is started only if the peripheral again asserts a DMA request. The DMA controller continues to perform transfers from the list only when the peripheral is making a request, until the last transfer is complete. A completion interrupt is generated only after the last transfer. By using this method, the DMA controller can transfer data to or from a peripheral from a set of arbitrary locations whenever the peripheral is ready to transfer data. Refer to Figure 9-5 on page 580 and Figure 9-6 on page 581, which show an example of operation in Peripheral Scatter-Gather mode. This example shows a gather operation, where data from three separate buffers in memory is copied to a single peripheral data register. Figure 9-5 on page 580 shows how the application sets up a DMA task list in memory that is used by the controller to perform three sets of copy operations from different locations in memory. The primary control structure for the channel that is used for the operation is configured to copy from the task list to the alternate control structure. Figure 9-6 on page 581 shows the sequence as the DMA controller performs the three sets of copy operations. First, using the primary control structure, the DMA controller loads the alternate control structure with task A. It then performs the copy operation specified by task A, copying the data from the source buffer A to the peripheral data register. Next, the DMA controller again uses the primary control structure to load task B into the alternate control structure, and then performs the B operation with the alternate control structure. The process is repeated for task C.
579
Figure 9-5. Peripheral Scatter-Gather, Setup and Configuration

1 Source Buffer in Memory 2 Task List in Memory 3 Channel Control Table in Memory
4 WORDS (SRC A) A
SRC DST ITEMS=4 Unused SRC DST TASK A SRC DST ITEMS=12 TASK B
Channel Primary Control Structure
16 WORDS (SRC B) B
ITEMS=16 Unused SRC DST ITEMS=1 Unused
TASK C
SRC DST ITEMS=n
Channel Alternate Control Structure
1 WORD (SRC C) C
Peripheral Data Register

DEST
NOTES: 1. Application has a need to copy data items from three separate locations in memory into a peripheral data register. 2. Application sets up DMA task list in memory, which contains the pointers and control configuration for three DMA copy tasks. 3. Application sets up the channel primary control structure to copy each task configuration, one at a time, to the alternate control structure, where it is executed by the DMA controller.
April 25, 2012
Figure 9-6. Peripheral Scatter-Gather, DMA Copy Sequence

Task List in Memory DMA Control Table in Memory Buffers in Memory SRC A
SRC
PRI
DST
SRC B
COPIED SRC

COPIED
SRC C
ALT
DST
Using the channels primary control structure, the DMA controller copies task A configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer A to the peripheral data register.
Task List in Memory
Buffers in Memory
SRC A
SRC
PRI
DST
SRC B SRC C
COPIED

COPIED
SRC
ALT
DST
Using the channels primary control structure, the DMA controller copies task B configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer B to the peripheral data register.
Task List in Memory
Buffers in Memory
SRC A
SRC
PRI
DST
SRC B

COPIED
SRC
SRC C
ALT
DST COPIED
Using the channels primary control structure, the DMA controller copies task C configuration to the channels alternate control structure.
Then, using the channels alternate control structure, the DMA controller copies data from the source buffer C to the peripheral data register.
581
9.2.7
Transfer Size and Increment

The DMA controller supports transfer data sizes of 8, 16, or 32 bits. The source and destination data size must be the same for any given transfer. The source and destination address can be auto-incremented by bytes, half-words, or words, or can be set to no increment. The source and destination address increment values can be set independently, and it is not necessary for the address increment to match the data size as long as the increment is the same or larger than the data size. For example, it is possible to perform a transfer using 8-bit data size, but using an address increment of full words (4 bytes). The data to be transferred must be aligned in memory according to the data size (8, 16, or 32 bits). Table 9-5 shows the configuration to read from a peripheral that supplies 8-bit data. Table 9-5. DMA Read Example: 8-Bit Peripheral
Field Source data size Destination data size Source address increment Destination address increment Source end pointer Destination end pointer Configuration 8 bits 8 bits No increment Byte Peripheral read FIFO register End of the data buffer in memory
9.2.8
Peripheral Interface
Each peripheral that supports DMA has a single request and/or burst request signal that is asserted when the peripheral is ready to transfer data (see Table 9-2 on page 572). The request signal can be disabled or enabled using the DMA Channel Request Mask Set (DMAREQMASKSET) and DMA Channel Request Mask Clear (DMAREQMASKCLR) registers. The DMA request signal is disabled, or masked, when the channel request mask bit is set. When the request is not masked, the DMA channel is configured correctly and enabled, and the peripheral asserts the request signal, the DMA controller begins the transfer. Note: When using DMA to transfer data to and from a peripheral, the peripheral must disable all interrupts to the NVIC.
When a DMA transfer is complete, the DMA controller generates an interrupt, see Interrupts and Errors on page 583 for more information. For more information on how a specific peripheral interacts with the DMA controller, refer to the DMA Operation section in the chapter that discusses that peripheral.
9.2.9
Software Request
One DMA channel is dedicated to software-initiated transfers. This channel also has a dedicated interrupt to signal completion of a DMA transfer. A transfer is initiated by software by first configuring and enabling the transfer, and then issuing a software request using the DMA Channel Software Request (DMASWREQ) register. For software-based transfers, the Auto transfer mode should be used. It is possible to initiate a transfer on any channel using the DMASWREQ register. If a request is initiated by software using a peripheral DMA channel, then the completion interrupt occurs on the interrupt vector for the peripheral instead of the software interrupt vector. Any channel may be used for software requests as long as the corresponding peripheral is not using DMA for data transfer.
April 25, 2012
9.2.10
Interrupts and Errors

When a DMA transfer is complete, the DMA controller generates a completion interrupt on the interrupt vector of the peripheral. Therefore, if DMA is used to transfer data for a peripheral and interrupts are used, then the interrupt handler for that peripheral must be designed to handle the DMA transfer completion interrupt. If the transfer uses the software DMA channel, then the completion interrupt occurs on the dedicated software DMA interrupt vector (see Table 9-6 on page 583). When DMA is enabled for a peripheral, the DMA controller stops the normal transfer interrupts for a peripheral from reaching the interrupt controller (the interrupts are still reported in the peripheral's interrupt registers). Thus, when a large amount of data is transferred using DMA, instead of receiving multiple interrupts from the peripheral as data flows, the interrupt controller receives only one interrupt when the transfer is complete. Unmasked peripheral error interrupts continue to be sent to the interrupt controller. When a DMA channel generates a completion interrupt, the CHIS bit corresponding to the peripheral channel is set in the DMA Channel Interrupt Status (DMACHIS) register (see page 618). This register can be used by the peripheral interrupt handler code to determine if the interrupt was caused by the DMA channel or an error event reported by the peripheral's interrupt registers. The completion interrupt request from the DMA controller is automatically cleared when the interrupt handler is activated. If the DMA controller encounters a bus or memory protection error as it attempts to perform a data transfer, it disables the DMA channel that caused the error and generates an interrupt on the DMA error interrupt vector. The processor can read the DMA Bus Error Clear (DMAERRCLR) register to determine if an error is pending. The ERRCLR bit is set if an error occurred. The error can be cleared by writing a 1 to the ERRCLR bit. Table 9-6 shows the dedicated interrupt assignments for the DMA controller. Table 9-6. DMA Interrupt Assignments
Interrupt 46 47 Assignment DMA Software Channel Transfer DMA Error
9.3
9.3.1

Module Initialization
Before the DMA controller can be used, it must be enabled in the System Control block and in the peripheral. The location of the channel control structure must also be programmed. The following steps should be performed one time during system initialization: 1. Enable the DMA clock using the RCGCDMA register (see page 314). 2. Enable the DMA controller by setting the MASTEREN bit of the DMA Configuration (DMACFG) register. 3. Program the location of the channel control table by writing the base address of the table to the DMA Channel Control Base Pointer (DMACTLBASE) register. The base address must be aligned on a 1024-byte boundary.
583
9.3.2
Configuring a Memory-to-Memory Transfer

DMA channel 30 is dedicated for software-initiated transfers. However, any channel can be used for software-initiated, memory-to-memory transfer if the associated peripheral is not being used.
9.3.2.1
Configure the Channel Attributes

First, configure the channel attributes: 1. Program bit 30 of the DMA Channel Priority Set (DMAPRIOSET) or DMA Channel Priority Clear (DMAPRIOCLR) registers to set the channel to High priority or Default priority. 2. Set bit 30 of the DMA Channel Primary Alternate Clear (DMAALTCLR) register to select the primary channel control structure for this transfer. 3. Set bit 30 of the DMA Channel Useburst Clear (DMAUSEBURSTCLR) register to allow the DMA controller to respond to single and burst requests. 4. Set bit 30 of the DMA Channel Request Mask Clear (DMAREQMASKCLR) register to allow the DMA controller to recognize requests for this channel.
9.3.2.2
Configure the Channel Control Structure

Now the channel control structure must be configured. This example transfers 256 words from one memory buffer to another. Channel 30 is used for a software transfer, and the control structure for channel 30 is at offset 0x1E0 of the channel control table. The channel control structure for channel 30 is located at the offsets shown in Table 9-7. Table 9-7. Channel Control Structure Offsets for Channel 30
Offset Control Table Base + 0x1E0 Control Table Base + 0x1E4 Control Table Base + 0x1E8 Description Channel 30 Source End Pointer Channel 30 Destination End Pointer Channel 30 Control Word
Configure the Source and Destination The source and destination end pointers must be set to the last address for the transfer (inclusive). 1. Program the source end pointer at offset 0x1E0 to the address of the source buffer + 0x3FC. 2. Program the destination end pointer at offset 0x1E4 to the address of the destination buffer + 0x3FC. The control word at offset 0x1E8 must be programmed according to Table 9-8. Table 9-8. Channel Control Word Configuration for Memory Transfer Example
Field in DMACHCTL DSTINC DSTSIZE SRCINC SRCSIZE reserved Bits 31:30 29:28 27:26 25:24 23:18 Value 2 2 2 2 0 Description 32-bit destination address increment 32-bit destination data size 32-bit source address increment 32-bit source data size Reserved
April 25, 2012
Table 9-8. Channel Control Word Configuration for Memory Transfer Example (continued)
Field in DMACHCTL ARBSIZE XFERSIZE NXTUSEBURST XFERMODE Bits 17:14 13:4 3 2:0 Value 3 255 0 2 Description Arbitrates after 8 transfers Transfer 256 items N/A for this transfer type Use Auto-request transfer mode
9.3.2.3
Start the Transfer

Now the channel is configured and is ready to start. 1. Enable the channel by setting bit 30 of the DMA Channel Enable Set (DMAENASET) register. 2. Issue a transfer request by setting bit 30 of the DMA Channel Software Request (DMASWREQ) register. The DMA transfer begins. If the interrupt is enabled, then the processor is notified by interrupt when the transfer is complete. If needed, the status can be checked by reading bit 30 of the DMAENASET register. This bit is automatically cleared when the transfer is complete. The status can also be checked by reading the XFERMODE field of the channel control word at offset 0x1E8. This field is automatically cleared at the end of the transfer.
9.3.3
Configuring a Peripheral for Simple Transmit

This example configures the DMA controller to transmit a buffer of data to a peripheral. The peripheral has a transmit FIFO with a trigger level of 4. The example peripheral uses DMA channel 7.
9.3.3.1

First, configure the channel attributes: 1. Configure bit 7 of the DMA Channel Priority Set (DMAPRIOSET) or DMA Channel Priority Clear (DMAPRIOCLR) registers to set the channel to High priority or Default priority. 2. Set bit 7 of the DMA Channel Primary Alternate Clear (DMAALTCLR) register to select the primary channel control structure for this transfer. 3. Set bit 7 of the DMA Channel Useburst Clear (DMAUSEBURSTCLR) register to allow the DMA controller to respond to single and burst requests. 4. Set bit 7 of the DMA Channel Request Mask Clear (DMAREQMASKCLR) register to allow the DMA controller to recognize requests for this channel.
9.3.3.2

This example transfers 64 bytes from a memory buffer to the peripheral's transmit FIFO register using DMA channel 7. The control structure for channel 7 is at offset 0x070 of the channel control table. The channel control structure for channel 7 is located at the offsets shown in Table 9-9. Table 9-9. Channel Control Structure Offsets for Channel 7
Offset Control Table Base + 0x070 Description Channel 7 Source End Pointer
585
Table 9-9. Channel Control Structure Offsets for Channel 7 (continued)

Offset Control Table Base + 0x074 Control Table Base + 0x078 Description Channel 7 Destination End Pointer Channel 7 Control Word
Configure the Source and Destination The source and destination end pointers must be set to the last address for the transfer (inclusive). Because the peripheral pointer does not change, it simply points to the peripheral's data register. 1. Program the source end pointer at offset 0x070 to the address of the source buffer + 0x3F. 2. Program the destination end pointer at offset 0x074 to the address of the peripheral's transmit FIFO register. The control word at offset 0x078 must be programmed according to Table 9-10. Table 9-10. Channel Control Word Configuration for Peripheral Transmit Example
Field in DMACHCTL DSTINC DSTSIZE SRCINC SRCSIZE reserved ARBSIZE XFERSIZE NXTUSEBURST XFERMODE Bits 31:30 29:28 27:26 25:24 23:18 17:14 13:4 3 2:0 Value 3 0 0 0 0 2 63 0 1 Description Destination address does not increment 8-bit destination data size 8-bit source address increment 8-bit source data size Reserved Arbitrates after 4 transfers Transfer 64 items N/A for this transfer type Use Basic transfer mode
Note:
In this example, it is not important if the peripheral makes a single request or a burst request. Because the peripheral has a FIFO that triggers at a level of 4, the arbitration size is set to 4. If the peripheral does make a burst request, then 4 bytes are transferred, which is what the FIFO can accommodate. If the peripheral makes a single request (if there is any space in the FIFO), then one byte is transferred at a time. If it is important to the application that transfers only be made in bursts, then the Channel Useburst SET[7] bit should be set in the DMA Channel Useburst Set (DMAUSEBURSTSET) register.
9.3.3.3
Start the Transfer

Now the channel is configured and is ready to start. 1. Enable the channel by setting bit 7 of the DMA Channel Enable Set (DMAENASET) register. The DMA controller is now configured for transfer on channel 7. The controller makes transfers to the peripheral whenever the peripheral asserts a DMA request. The transfers continue until the entire buffer of 64 bytes has been transferred. When that happens, the DMA controller disables the channel and sets the XFERMODE field of the channel control word to 0 (Stopped). The status of the transfer can be checked by reading bit 7 of the DMA Channel Enable Set (DMAENASET) register. This bit is automatically cleared when the transfer is complete. The status can also be checked by reading the XFERMODE field of the channel control word at offset 0x078. This field is automatically cleared at the end of the transfer.
April 25, 2012
If peripheral interrupts are enabled, then the peripheral interrupt handler receives an interrupt when the entire transfer is complete.
9.3.4
Configuring a Peripheral for Ping-Pong Receive

This example configures the DMA controller to continuously receive 8-bit data from a peripheral into a pair of 64-byte buffers. The peripheral has a receive FIFO with a trigger level of 8. The example peripheral uses DMA channel 8.
9.3.4.1

First, configure the channel attributes: 1. Configure bit 8 of the DMA Channel Priority Set (DMAPRIOSET) or DMA Channel Priority Clear (DMAPRIOCLR) registers to set the channel to High priority or Default priority. 2. Set bit 8 of the DMA Channel Primary Alternate Clear (DMAALTCLR) register to select the primary channel control structure for this transfer. 3. Set bit 8 of the DMA Channel Useburst Clear (DMAUSEBURSTCLR) register to allow the DMA controller to respond to single and burst requests. 4. Set bit 8 of the DMA Channel Request Mask Clear (DMAREQMASKCLR) register to allow the DMA controller to recognize requests for this channel.
9.3.4.2

This example transfers bytes from the peripheral's receive FIFO register into two memory buffers of 64 bytes each. As data is received, when one buffer is full, the DMA controller switches to use the other. To use Ping-Pong buffering, both primary and alternate channel control structures must be used. The primary control structure for channel 8 is at offset 0x080 of the channel control table, and the alternate channel control structure is at offset 0x280. The channel control structures for channel 8 are located at the offsets shown in Table 9-11. Table 9-11. Primary and Alternate Channel Control Structure Offsets for Channel 8
Offset Control Table Base + 0x080 Control Table Base + 0x084 Control Table Base + 0x088 Control Table Base + 0x280 Control Table Base + 0x284 Control Table Base + 0x288 Description Channel 8 Primary Source End Pointer Channel 8 Primary Destination End Pointer Channel 8 Primary Control Word Channel 8 Alternate Source End Pointer Channel 8 Alternate Destination End Pointer Channel 8 Alternate Control Word
Configure the Source and Destination The source and destination end pointers must be set to the last address for the transfer (inclusive). Because the peripheral pointer does not change, it simply points to the peripheral's data register. Both the primary and alternate sets of pointers must be configured. 1. Program the primary source end pointer at offset 0x080 to the address of the peripheral's receive buffer.
587
2. Program the primary destination end pointer at offset 0x084 to the address of ping-pong buffer A + 0x3F. 3. Program the alternate source end pointer at offset 0x280 to the address of the peripheral's receive buffer. 4. Program the alternate destination end pointer at offset 0x284 to the address of ping-pong buffer B + 0x3F. The primary control word at offset 0x088 and the alternate control word at offset 0x288 are initially programmed the same way. 1. Program the primary channel control word at offset 0x088 according to Table 9-12. 2. Program the alternate channel control word at offset 0x288 according to Table 9-12. Table 9-12. Channel Control Word Configuration for Peripheral Ping-Pong Receive Example
Field in DMACHCTL DSTINC DSTSIZE SRCINC SRCSIZE reserved ARBSIZE XFERSIZE NXTUSEBURST XFERMODE Bits 31:30 29:28 27:26 25:24 23:18 17:14 13:4 3 2:0 Value 0 0 3 0 0 3 63 0 3 Description 8-bit destination address increment 8-bit destination data size Source address does not increment 8-bit source data size Reserved Arbitrates after 8 transfers Transfer 64 items N/A for this transfer type Use Ping-Pong transfer mode
Note:
In this example, it is not important if the peripheral makes a single request or a burst request. Because the peripheral has a FIFO that triggers at a level of 8, the arbitration size is set to 8. If the peripheral does make a burst request, then 8 bytes are transferred, which is what the FIFO can accommodate. If the peripheral makes a single request (if there is any data in the FIFO), then one byte is transferred at a time. If it is important to the application that transfers only be made in bursts, then the Channel Useburst SET[8] bit should be set in the DMA Channel Useburst Set (DMAUSEBURSTSET) register.
9.3.4.3
Configure the Peripheral Interrupt

An interrupt handler should be configured when using DMA Ping-Pong mode, it is best to use an interrupt handler. However, the Ping-Pong mode can be configured without interrupts by polling. The interrupt handler is triggered after each buffer is complete. 1. Configure and enable an interrupt handler for the peripheral.
9.3.4.4
Enable the DMA Channel

Now the channel is configured and is ready to start. 1. Enable the channel by setting bit 8 of the DMA Channel Enable Set (DMAENASET) register.
April 25, 2012
9.3.4.5
Process Interrupts
The DMA controller is now configured and enabled for transfer on channel 8. When the peripheral asserts the DMA request signal, the DMA controller makes transfers into buffer A using the primary channel control structure. When the primary transfer to buffer A is complete, it switches to the alternate channel control structure and makes transfers into buffer B. At the same time, the primary channel control word mode field is configured to indicate Stopped, and an interrupt is pending. When an interrupt is triggered, the interrupt handler must determine which buffer is complete and process the data or set a flag that the data must be processed by non-interrupt buffer processing code. Then the next buffer transfer must be set up. In the interrupt handler: 1. Read the primary channel control word at offset 0x088 and check the XFERMODE field. If the field is 0, this means buffer A is complete. If buffer A is complete, then: a. Process the newly received data in buffer A or signal the buffer processing code that buffer A has data available. b. Reprogram the primary channel control word at offset 0x88 according to Table 9-12 on page 588. 2. Read the alternate channel control word at offset 0x288 and check the XFERMODE field. If the field is 0, this means buffer B is complete. If buffer B is complete, then: a. Process the newly received data in buffer B or signal the buffer processing code that buffer B has data available. b. Reprogram the alternate channel control word at offset 0x288 according to Table 9-12 on page 588.
9.3.5
Configuring Channel Assignments

Channel assignments for each DMA channel can be changed using the DMACHMAPn registers. Each 4-bit field represents a DMA channel. Refer to Table 9-1 on page 570 for channel assignments.
9.4
Register Map
Table 9-13 on page 590 lists the DMA channel control structures and registers. The channel control structure shows the layout of one entry in the channel control table. The channel control table is located in system memory, and the location is determined by the application, thus, the base address is n/a (not applicable) and noted as so above the register descriptions. In the table below, the offset for the channel control structures is the offset from the entry in the channel control table. See Channel Configuration on page 572 and Table 9-3 on page 573 for a description of how the entries in the channel control table are located in memory. The DMA register addresses are given as a hexadecimal increment, relative to the DMA base address of 0x400F.F000. Note that the DMA module clock must be enabled before the registers can be programmed (see page 314). There must be a delay of 3 system clocks after the DMA module clock is enabled before any DMA module registers are accessed.
589
Table 9-13. DMA Register Map

DMA Channel Control Structure (Offset from Channel Control Table Base) 0x000 0x004 0x008 DMASRCENDP DMADSTENDP DMACHCTL R/W R/W R/W DMA Channel Source Address End Pointer DMA Channel Destination Address End Pointer DMA Channel Control Word 592 593 594
DMA Registers (Offset from DMA Base Address) 0x000 0x004 0x008 0x00C 0x010 0x014 0x018 0x01C 0x020 0x024 0x028 0x02C 0x030 0x034 0x038 0x03C 0x04C 0x500 0x504 0x510 0x514 0x518 0x51C 0xFD0 0xFE0 0xFE4 0xFE8 DMASTAT DMACFG DMACTLBASE DMAALTBASE DMAWAITSTAT DMASWREQ DMAUSEBURSTSET DMAUSEBURSTCLR DMAREQMASKSET DMAREQMASKCLR DMAENASET DMAENACLR DMAALTSET DMAALTCLR DMAPRIOSET DMAPRIOCLR DMAERRCLR DMACHASGN DMACHIS DMACHMAP0 DMACHMAP1 DMACHMAP2 DMACHMAP3 DMAPeriphID4 DMAPeriphID0 DMAPeriphID1 DMAPeriphID2 RO WO R/W RO RO WO R/W WO R/W WO R/W WO R/W WO R/W WO R/W R/W R/W1C R/W R/W R/W R/W RO RO RO RO 0x001F.0000 0x0000.0000 0x0000.0200 0xFFFF.FFC0 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0004 0x0000.0030 0x0000.00B2 0x0000.000B DMA Status DMA Configuration DMA Channel Control Base Pointer DMA Alternate Channel Control Base Pointer DMA Channel Wait-on-Request Status DMA Channel Software Request DMA Channel Useburst Set DMA Channel Useburst Clear DMA Channel Request Mask Set DMA Channel Request Mask Clear DMA Channel Enable Set DMA Channel Enable Clear DMA Channel Primary Alternate Set DMA Channel Primary Alternate Clear DMA Channel Priority Set DMA Channel Priority Clear DMA Bus Error Clear DMA Channel Assignment DMA Channel Interrupt Status DMA Channel Map Select 0 DMA Channel Map Select 1 DMA Channel Map Select 2 DMA Channel Map Select 3 DMA Peripheral Identification 4 DMA Peripheral Identification 0 DMA Peripheral Identification 1 DMA Peripheral Identification 2 599 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 627 623 624 625
April 25, 2012
Table 9-13. DMA Register Map (continued)

Offset 0xFEC 0xFF0 0xFF4 0xFF8 0xFFC Name DMAPeriphID3 DMAPCellID0 DMAPCellID1 DMAPCellID2 DMAPCellID3 Type RO RO RO RO RO Reset 0x0000.0000 0x0000.000D 0x0000.00F0 0x0000.0005 0x0000.00B1 Description DMA Peripheral Identification 3 DMA PrimeCell Identification 0 DMA PrimeCell Identification 1 DMA PrimeCell Identification 2 DMA PrimeCell Identification 3 See page 626 628 629 630 631
9.5
DMA Channel Control Structure

The DMA Channel Control Structure holds the transfer settings for a DMA channel. Each channel has two control structures, which are located in a table in system memory. Refer to Channel Configuration on page 572 for an explanation of the Channel Control Table and the Channel Control Structure. The channel control structure is one entry in the channel control table. Each channel has a primary and alternate structure. The primary control structures are located at offsets 0x0, 0x10, 0x20 and so on. The alternate control structures are located at offsets 0x200, 0x210, 0x220, and so on.
591
Register 1: DMA Channel Source Address End Pointer (DMASRCENDP), offset 0x000
DMA Channel Source Address End Pointer (DMASRCENDP) is part of the Channel Control Structure and is used to specify the source address for a DMA transfer. The DMA controller can transfer data to and from the on-chip SRAM. However, because the Flash memory and ROM are located on a separate internal bus, it is not possible to transfer data to/from the Flash memory or ROM with the DMA controller. Note: The offset specified is from the base address of the control structure in system memory, not the DMA module base address.
DMA Channel Source Address End Pointer (DMASRCENDP)

Base n/a Offset 0x000 Type R/W, reset 31 30 29 28 27 26 25 24 ADDR Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 ADDR Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name ADDR
Type R/W
Reset -
Description Source Address End Pointer This field points to the last address of the DMA transfer source (inclusive). If the source address is not incrementing (the SRCINC field in the DMACHCTL register is 0x3), then this field points at the source location itself (such as a peripheral data register).
April 25, 2012
Register 2: DMA Channel Destination Address End Pointer (DMADSTENDP), offset 0x004
DMA Channel Destination Address End Pointer (DMADSTENDP) is part of the Channel Control Structure and is used to specify the destination address for a DMA transfer. Note: The offset specified is from the base address of the control structure in system memory, not the DMA module base address.
DMA Channel Destination Address End Pointer (DMADSTENDP)

Base n/a Offset 0x004 Type R/W, reset 31 30 29 28 27 26 25 24 ADDR Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 ADDR Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name ADDR
Type R/W
Reset -
Description Destination Address End Pointer This field points to the last address of the DMA transfer destination (inclusive). If the destination address is not incrementing (the DSTINC field in the DMACHCTL register is 0x3), then this field points at the destination location itself (such as a peripheral data register).
593
Register 3: DMA Channel Control Word (DMACHCTL), offset 0x008

DMA Channel Control Word (DMACHCTL) is part of the Channel Control Structure and is used to specify parameters of a DMA transfer. Note: The offset specified is from the base address of the control structure in system memory, not the DMA module base address.
DMA Channel Control Word (DMACHCTL)

Base n/a Offset 0x008 Type R/W, reset 31 DSTINC Type Reset R/W 15 R/W 14 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
DSTSIZE R/W 13 R/W 12
SRCINC R/W 11 R/W 10
SRCSIZE R/W 9 R/W 8 R/W 7 R/W 6
reserved R/W 5 R/W 4 R/W 3

NXTUSEBURST
ARBSIZE R/W 2 R/W 1 XFERMODE R/W R/W R/W R/W 0
ARBSIZE Type Reset R/W R/W R/W R/W R/W R/W -
XFERSIZE R/W R/W R/W R/W R/W R/W -
R/W -
Bit/Field 31:30
Name DSTINC
Type R/W
Reset -
Description Destination Address Increment This field configures the destination address increment. The address increment value must be equal or greater than the value of the destination size (DSTSIZE). Value Description 0x0 0x1 0x2 0x3 Byte Increment by 8-bit locations Half-word Increment by 16-bit locations Word Increment by 32-bit locations No increment Address remains set to the value of the Destination Address End Pointer (DMADSTENDP) for the channel
29:28
DSTSIZE
R/W
Destination Data Size This field configures the destination item data size. Note: DSTSIZE must be the same as SRCSIZE.
Value Description 0x0 0x1 0x2 0x3 Byte 8-bit data size Half-word 16-bit data size Word 32-bit data size Reserved
April 25, 2012
Bit/Field 27:26
Name SRCINC
Type R/W
Reset -
Description Source Address Increment This field configures the source address increment. The address increment value must be equal or greater than the value of the source size (SRCSIZE). Value Description 0x0 0x1 0x2 0x3 Byte Increment by 8-bit locations Half-word Increment by 16-bit locations Word Increment by 32-bit locations No increment Address remains set to the value of the Source Address End Pointer (DMASRCENDP) for the channel
25:24
SRCSIZE
R/W
Source Data Size This field configures the source item data size. Note: DSTSIZE must be the same as SRCSIZE.
Value Description 0x0 0x1 0x2 0x3 Byte 8-bit data size. Half-word 16-bit data size. Word 32-bit data size. Reserved
23:18
reserved
R/W
595
Bit/Field 17:14
Name ARBSIZE
Type R/W
Reset -
Description Arbitration Size This field configures the number of transfers that can occur before the DMA controller re-arbitrates. The possible arbitration rate configurations represent powers of 2 and are shown below. Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 Description 1 Transfer Arbitrates after each DMA transfer 2 Transfers 4 Transfers 8 Transfers 16 Transfers 32 Transfers 64 Transfers 128 Transfers 256 Transfers 512 Transfers In this configuration, no arbitration occurs during the DMA transfer because the maximum transfer size is 1024.
0xA-0xF 1024 Transfers
13:4
XFERSIZE
R/W
Transfer Size (minus 1) This field configures the total number of items to transfer. The value of this field is 1 less than the number to transfer (value 0 means transfer 1 item). The maximum value for this 10-bit field is 1023 which represents a transfer size of 1024 items. The transfer size is the number of items, not the number of bytes. If the data size is 32 bits, then this value is the number of 32-bit words to transfer. The DMA controller updates this field immediately prior to entering the arbitration process, so it contains the number of outstanding items that is necessary to complete the DMA cycle.
NXTUSEBURST
R/W
Next Useburst This field controls whether the Useburst SET[n] bit is automatically set for the last transfer of a peripheral scatter-gather operation. Normally, for the last transfer, if the number of remaining items to transfer is less than the arbitration size, the DMA controller uses single transfers to complete the transaction. If this bit is set, then the controller uses a burst transfer to complete the last transfer.
April 25, 2012
Bit/Field 2:0
Name XFERMODE
Type R/W
Reset -
Description DMA Transfer Mode This field configures the operating mode of the DMA cycle. Refer to Transfer Modes on page 574 for a detailed explanation of transfer modes. Because this register is in system RAM, it has no reset value. Therefore, this field should be initialized to 0 before the channel is enabled. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Stop Basic Auto-Request Ping-Pong Memory Scatter-Gather Alternate Memory Scatter-Gather Peripheral Scatter-Gather Alternate Peripheral Scatter-Gather
XFERMODE Bit Field Values. Stop Channel is stopped or configuration data is invalid. No more transfers can occur. Basic For each trigger (whether from a peripheral or a software request), the DMA controller performs the number of transfers specified by the ARBSIZE field. Auto-Request The initial request (software- or peripheral-initiated) is sufficient to complete the entire transfer of XFERSIZE items without any further requests. Ping-Pong This mode uses both the primary and alternate control structures for this channel. When the number of transfers specified by the XFERSIZE field have completed for the current control structure (primary or alternate), the DMA controller switches to the other one. These switches continue until one of the control structures is not set to ping-pong mode. At that point, the DMA controller stops. An interrupt is generated on completion of the transfers configured by each control structure. See Ping-Pong on page 574. Memory Scatter-Gather When using this mode, the primary control structure for the channel is configured to allow a list of operations (tasks) to be performed. The source address pointer specifies the start of a table of tasks to be copied to the alternate control structure for this channel. The XFERMODE field for the alternate control structure should be configured to 0x5 (Alternate memory scatter-gather) to perform the task. When the task completes, the DMA switches back to the primary channel control structure, which then copies the next task to the alternate control structure. This process continues until the table of tasks is empty. The last task must have an XFERMODE value other than 0x5. Note that for continuous operation, the last task can update the primary channel control structure back to the start of the list or to another list. See Memory Scatter-Gather on page 575.
597
Alternate Memory Scatter-Gather This value must be used in the alternate channel control data structure when the DMA controller operates in Memory Scatter-Gather mode. Peripheral Scatter-Gather This value must be used in the primary channel control data structure when the DMA controller operates in Peripheral Scatter-Gather mode. In this mode, the DMA controller operates exactly the same as in Memory Scatter-Gather mode, except that instead of performing the number of transfers specified by the XFERSIZE field in the alternate control structure at one time, the DMA controller only performs the number of transfers specified by the ARBSIZE field per trigger; see Basic mode for details. See Peripheral Scatter-Gather on page 579. Alternate Peripheral Scatter-Gather This value must be used in the alternate channel control data structure when the DMA controller operates in Peripheral Scatter-Gather mode.
9.6
DMA Register Descriptions

The register addresses given are relative to the DMA base address of 0x400F.F000.
April 25, 2012
Register 4: DMA Status (DMASTAT), offset 0x000

The DMA Status (DMASTAT) register returns the status of the DMA controller. You cannot read this register when the DMA controller is in the reset state.
DMA Status (DMASTAT)
Base 0x400F.F000 Offset 0x000 Type RO, reset 0x001F.0000
31 30 29 28 27 26 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 STATE RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 5 RO 1 4 RO 1 3 25 24 23 22 21 20 19 18 DMACHANS RO 1 2 reserved RO 0 RO 0 RO 1 1 RO 1 0 MASTEN RO 0 17 16
Bit/Field 31:21
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Available DMA Channels Minus 1 This field contains a value equal to the number of DMA channels the DMA controller is configured to use, minus one. The value of 0x1F corresponds to 32 DMA channels.
20:16
DMACHANS
RO
0x1F
15:8
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Control State Machine Status This field shows the current status of the control state machine. Status can be one of the following. Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 Description Idle Reading channel controller data. Reading source end pointer. Reading destination end pointer. Reading source data. Writing destination data. Waiting for DMA request to clear. Writing channel controller data. Stalled Done
7:4
STATE
RO
0x0
0xA-0xF Undefined
3:1
reserved
RO
0x0
599
Bit/Field 0
Name MASTEN
Type RO
Reset 0
Description Master Enable Status Value Description 0 1 The DMA controller is disabled. The DMA controller is enabled.
April 25, 2012
Register 5: DMA Configuration (DMACFG), offset 0x004

The DMACFG register controls the configuration of the DMA controller.
DMA Configuration (DMACFG)
Base 0x400F.F000 Offset 0x004 Type WO, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 reserved Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0 MASTEN WO -
Bit/Field 31:1
Name reserved
Type WO
Reset -
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Controller Master Enable Value Description 0 1 Disables the DMA controller. Enables DMA controller.
MASTEN
WO
601
Register 6: DMA Channel Control Base Pointer (DMACTLBASE), offset 0x008

The DMACTLBASE register must be configured so that the base pointer points to a location in system memory. The amount of system memory that must be assigned to the DMA controller depends on the number of DMA channels used and whether the alternate channel control data structure is used. See Channel Configuration on page 572 for details about the Channel Control Table. The base address must be aligned on a 1024-byte boundary. This register cannot be read when the DMA controller is in the reset state.
DMA Channel Control Base Pointer (DMACTLBASE)
Base 0x400F.F000 Offset 0x008 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 ADDR Type Reset R/W 0 15 R/W 0 14 R/W 0 13 ADDR Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 RO 0 RO 0 RO 0 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 R/W 0 5 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:10
Name ADDR
Type R/W
Reset 0x0000.00
Description Channel Control Base Address This field contains the pointer to the base address of the channel control table. The base address must be 1024-byte aligned.
9:0
reserved
RO
0x00
April 25, 2012
Register 7: DMA Alternate Channel Control Base Pointer (DMAALTBASE), offset 0x00C
The DMAALTBASE register returns the base address of the alternate channel control data. This register removes the necessity for application software to calculate the base address of the alternate channel control structures. This register cannot be read when the DMA controller is in the reset state.
DMA Alternate Channel Control Base Pointer (DMAALTBASE)
Base 0x400F.F000 Offset 0x00C Type RO, reset 0x0000.0200
31 30 29 28 27 26 25 24 ADDR Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 ADDR Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name ADDR
Type RO
Reset
Description
0x0000.0200 Alternate Channel Address Pointer This field provides the base address of the alternate channel control structures.
603
Register 8: DMA Channel Wait-on-Request Status (DMAWAITSTAT), offset 0x010

This read-only register indicates that the DMA channel is waiting on a request. A peripheral can hold off the DMA from performing a single request until the peripheral is ready for a burst request to enhance the DMA performance. The use of this feature is dependent on the design of the peripheral and is not controllable by software in any way. This register cannot be read when the DMA controller is in the reset state.
DMA Channel Wait-on-Request Status (DMAWAITSTAT)
Base 0x400F.F000 Offset 0x010 Type RO, reset 0xFFFF.FFC0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
WAITREQ[n] Type Reset RO 1 15 RO 1 14 RO 1 13 RO 1 12 RO 1 11 RO 1 10 RO 1 9 RO 1 8 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0
WAITREQ[n] Type Reset RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
Bit/Field 31:0
Name WAITREQ[n]
Type RO
Reset
Description
0xFFFF.FFC0 Channel [n] Wait Status These bits provide the channel wait-on-request status. Bit 0 corresponds to channel 0. Value Description 1 0 The corresponding channel is waiting on a request. The corresponding channel is not waiting on a request.
April 25, 2012
Register 9: DMA Channel Software Request (DMASWREQ), offset 0x014

Each bit of the DMASWREQ register represents the corresponding DMA channel. Setting a bit generates a request for the specified DMA channel.
DMA Channel Software Request (DMASWREQ)
Base 0x400F.F000 Offset 0x014 Type WO, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
SWREQ[n] Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0
SWREQ[n] Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO -
Bit/Field 31:0
Name SWREQ[n]
Type WO
Reset -
Description Channel [n] Software Request These bits generate software requests. Bit 0 corresponds to channel 0. Value Description 1 0 Generate a software request for the corresponding channel. No request generated.
These bits are automatically cleared when the software request has been completed.
605
Register 10: DMA Channel Useburst Set (DMAUSEBURSTSET), offset 0x018

Each bit of the DMAUSEBURSTSET register represents the corresponding DMA channel. Setting a bit disables the channel's single request input from generating requests, configuring the channel to only accept burst requests. Reading the register returns the status of USEBURST. If the amount of data to transfer is a multiple of the arbitration (burst) size, the corresponding SET[n] bit is cleared after completing the final transfer. If there are fewer items remaining to transfer than the arbitration (burst) size, the DMA controller automatically clears the corresponding SET[n] bit, allowing the remaining items to transfer using single requests. In order to resume transfers using burst requests, the corresponding bit must be set again. A bit should not be set if the corresponding peripheral does not support the burst request model. Refer to Request Types on page 571 for more details about request types.
DMA Channel Useburst Set (DMAUSEBURSTSET)
31 30 29 28 27 26 25 24 SET[n] Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 SET[n] Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name SET[n]
Type R/W
Reset
Description
0x0000.0000 Channel [n] Useburst Set Value Description 0 1 DMA channel [n] responds to single or burst requests. DMA channel [n] responds only to burst requests.
Bit 0 corresponds to channel 0. This bit is automatically cleared as described above. A bit can also be manually cleared by setting the corresponding CLR[n] bit in the DMAUSEBURSTCLR register.
April 25, 2012
Register 11: DMA Channel Useburst Clear (DMAUSEBURSTCLR), offset 0x01C

Each bit of the DMAUSEBURSTCLR register represents the corresponding DMA channel. Setting a bit clears the corresponding SET[n] bit in the DMAUSEBURSTSET register.
DMA Channel Useburst Clear (DMAUSEBURSTCLR)
Base 0x400F.F000 Offset 0x01C Type WO, reset 31 30 29 28 27 26 25 24 CLR[n] Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 CLR[n] Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name CLR[n]
Type WO
Reset -
Description Channel [n] Useburst Clear Value Description 0 1 No effect. Setting a bit clears the corresponding SET[n] bit in the DMAUSEBURSTSET register meaning that DMA channel [n] responds to single and burst requests.
607
Register 12: DMA Channel Request Mask Set (DMAREQMASKSET), offset 0x020
Each bit of the DMAREQMASKSET register represents the corresponding DMA channel. Setting a bit disables DMA requests for the channel. Reading the register returns the request mask status. When a DMA channel's request is masked, that means the peripheral can no longer request DMA transfers. The channel can then be used for software-initiated transfers.
DMA Channel Request Mask Set (DMAREQMASKSET)
Bit/Field 31:0
Name SET[n]
Type R/W
Reset
Description
0x0000.0000 Channel [n] Request Mask Set Value Description 0 1 The peripheral associated with channel [n] is enabled to request DMA transfers. The peripheral associated with channel [n] is not able to request DMA transfers. Channel [n] may be used for software-initiated transfers.
Bit 0 corresponds to channel 0. A bit can only be cleared by setting the corresponding CLR[n] bit in the DMAREQMASKCLR register.
April 25, 2012
Register 13: DMA Channel Request Mask Clear (DMAREQMASKCLR), offset 0x024
Each bit of the DMAREQMASKCLR register represents the corresponding DMA channel. Setting a bit clears the corresponding SET[n] bit in the DMAREQMASKSET register.
DMA Channel Request Mask Clear (DMAREQMASKCLR)
Base 0x400F.F000 Offset 0x024 Type WO, reset 31 30 29 28 27 26 25 24 CLR[n] Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 CLR[n] Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name CLR[n]
Type WO
Reset -
Description Channel [n] Request Mask Clear Value Description 0 1 No effect. Setting a bit clears the corresponding SET[n] bit in the DMAREQMASKSET register meaning that the peripheral associated with channel [n] is enabled to request DMA transfers.
609
Register 14: DMA Channel Enable Set (DMAENASET), offset 0x028

Each bit of the DMAENASET register represents the corresponding DMA channel. Setting a bit enables the corresponding DMA channel. Reading the register returns the enable status of the channels. If a channel is enabled but the request mask is set (DMAREQMASKSET), then the channel can be used for software-initiated transfers.
DMA Channel Enable Set (DMAENASET)
Bit/Field 31:0
Name SET[n]
Type R/W
Reset
Description
0x0000.0000 Channel [n] Enable Set Value Description 0 1 DMA Channel [n] is disabled. DMA Channel [n] is enabled.
Bit 0 corresponds to channel 0. A bit can only be cleared by setting the corresponding CLR[n] bit in the DMAENACLR register or when the end of a DMA transfer occurs.
April 25, 2012
Register 15: DMA Channel Enable Clear (DMAENACLR), offset 0x02C

Each bit of the DMAENACLR register represents the corresponding DMA channel. Setting a bit clears the corresponding SET[n] bit in the DMAENASET register.
DMA Channel Enable Clear (DMAENACLR)
Bit/Field 31:0
Name CLR[n]
Type WO
Reset -
Description Clear Channel [n] Enable Clear Value Description 0 1 No effect. Setting a bit clears the corresponding SET[n] bit in the DMAENASET register meaning that channel [n] is disabled for DMA transfers. The controller disables a channel when it completes the DMA cycle.
Note:
611
Register 16: DMA Channel Primary Alternate Set (DMAALTSET), offset 0x030
Each bit of the DMAALTSET register represents the corresponding DMA channel. Setting a bit configures the DMA channel to use the alternate control data structure. Reading the register returns the status of which control data structure is in use for the corresponding DMA channel.
DMA Channel Primary Alternate Set (DMAALTSET)
Bit/Field 31:0
Name SET[n]
Type R/W
Reset
Description
0x0000.0000 Channel [n] Alternate Set Value Description 0 1 DMA channel [n] is using the primary control structure. DMA channel [n] is using the alternate control structure.
Bit 0 corresponds to channel 0. A bit can only be cleared by setting the corresponding CLR[n] bit in the DMAALTCLR register. Note: For Ping-Pong and Scatter-Gather cycle types, the DMA controller automatically sets these bits to select the alternate channel control data structure.
April 25, 2012
Register 17: DMA Channel Primary Alternate Clear (DMAALTCLR), offset 0x034
Each bit of the DMAALTCLR register represents the corresponding DMA channel. Setting a bit clears the corresponding SET[n] bit in the DMAALTSET register.
DMA Channel Primary Alternate Clear (DMAALTCLR)
Base 0x400F.F000 Offset 0x034 Type WO, reset 31 30 29 28 27 26 25 24 CLR[n] Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 CLR[n] Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name CLR[n]
Type WO
Reset -
Description Channel [n] Alternate Clear Value Description 0 1 No effect. Setting a bit clears the corresponding SET[n] bit in the DMAALTSET register meaning that channel [n] is using the primary control structure. For Ping-Pong and Scatter-Gather cycle types, the DMA controller automatically sets these bits to select the alternate channel control data structure.
Note:
613
Register 18: DMA Channel Priority Set (DMAPRIOSET), offset 0x038

Each bit of the DMAPRIOSET register represents the corresponding DMA channel. Setting a bit configures the DMA channel to have a high priority level. Reading the register returns the status of the channel priority mask.
DMA Channel Priority Set (DMAPRIOSET)
Bit/Field 31:0
Name SET[n]
Type R/W
Reset
Description
0x0000.0000 Channel [n] Priority Set Value Description 0 1 DMA channel [n] is using the default priority level. DMA channel [n] is using a high priority level.
Bit 0 corresponds to channel 0. A bit can only be cleared by setting the corresponding CLR[n] bit in the DMAPRIOCLR register.
April 25, 2012
Register 19: DMA Channel Priority Clear (DMAPRIOCLR), offset 0x03C

Each bit of the DMAPRIOCLR register represents the corresponding DMA channel. Setting a bit clears the corresponding SET[n] bit in the DMAPRIOSET register.
DMA Channel Priority Clear (DMAPRIOCLR)
Bit/Field 31:0
Name CLR[n]
Type WO
Reset -
Description Channel [n] Priority Clear Value Description 0 1 No effect. Setting a bit clears the corresponding SET[n] bit in the DMAPRIOSET register meaning that channel [n] is using the default priority level.
615
Register 20: DMA Bus Error Clear (DMAERRCLR), offset 0x04C

The DMAERRCLR register is used to read and clear the DMA bus error status. The error status is set if the DMA controller encountered a bus error while performing a transfer. If a bus error occurs on a channel, that channel is automatically disabled by the DMA controller. The other channels are unaffected.
DMA Bus Error Clear (DMAERRCLR)
Base 0x400F.F000 Offset 0x04C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 ERRCLR R/W1C 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Bus Error Status Value Description 0 1 No bus error is pending. A bus error is pending.
ERRCLR
R/W1C
April 25, 2012
Register 21: DMA Channel Assignment (DMACHASGN), offset 0x500

Each bit of the DMACHASGN register represents the corresponding DMA channel. Setting a bit selects the secondary channel assignment as specified in Table 9-1 on page 570. Note: This register is provided to support legacy software. New software should use the DMACHMAPn registers. If a bit is clear in this register, the corresponding field in the DMACHMAPn registers is configured to 0x0. If a bit is set in this register, the corresponding field is configured to 0x1. If this register is read, a bit reads as 0 if the corresponding DMACHMAPn register field value is equal to 0, otherwise it reads as 1 if the corresponding DMACHMAPn register field value is not equal to 0.
DMA Channel Assignment (DMACHASGN)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
CHASGN[n] Type Reset R/W 15 R/W 14 R/W 13 R/W 12 R/W 11 R/W 10 R/W 9 R/W 8 R/W 7 R/W 6 R/W 5 R/W 4 R/W 3 R/W 2 R/W 1 R/W 0
CHASGN[n] Type Reset R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W -
Bit/Field 31:0
Name CHASGN[n]
Type R/W
Reset -
Description Channel [n] Assignment Select Value Description 0 1 Use the primary channel assignment. Use the secondary channel assignment.
617
Register 22: DMA Channel Interrupt Status (DMACHIS), offset 0x504

Each bit of the DMACHIS register represents the corresponding DMA channel. A bit is set when that DMA channel causes a completion interrupt. The bits are cleared by a writing a 1.
DMA Channel Interrupt Status (DMACHIS)
Base 0x400F.F000 Offset 0x504 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 CHIS[n] Type Reset R/W1C 0 15 R/W1C 0 14 R/W1C 0 13 R/W1C 0 12 R/W1C 0 11 R/W1C 0 10 R/W1C 0 9 R/W1C 0 8 CHIS[n] Type Reset R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 R/W1C 0 7 R/W1C 0 6 R/W1C 0 5 R/W1C 0 4 R/W1C 0 3 R/W1C 0 2 R/W1C 0 1 R/W1C 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name CHIS[n]
Type R/W1C
Reset
Description
0x0000.0000 Channel [n] Interrupt Status Value Description 1 0 The corresponding DMA channel caused an interrupt. The corresponding DMA channel has not caused an interrupt.
April 25, 2012
Register 23: DMA Channel Map Select 0 (DMACHMAP0), offset 0x510

Each 4-bit field of the DMACHMAP0 register configures the DMA channel assignment as specified in Table 9-1 on page 570. Note: To support legacy software which uses the DMA Channel Assignment (DMACHASGN) register, a value of 0x0 is equivalent to a DMACHASGN bit being clear, and a value of 0x1 is equivalent to a DMACHASGN bit being set.
DMA Channel Map Select 0 (DMACHMAP0)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
CH7SEL Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11
CH6SEL R/W 0 10 CH2SEL R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 9 R/W 0 8 R/W 0 7
CH5SEL R/W 0 6 CH1SEL R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 5 R/W 0 4 R/W 0 3
CH4SEL R/W 0 2 CH0SEL R/W 0 R/W 0 R/W 0 R/W 0 1 R/W 0 0
CH3SEL Type Reset R/W 0 R/W 0 R/W 0
Bit/Field 31:28
Name CH7SEL
Type R/W
Reset 0x00
Description DMA Channel 7 Source Select See Table 9-1 on page 570 for channel assignments.
27:24
CH6SEL
R/W
0x00
DMA Channel 6 Source Select See Table 9-1 on page 570 for channel assignments.
23:20
CH5SEL
R/W
0x00
19:16
CH4SEL
R/W
0x00
15:12
CH3SEL
R/W
0x00
11:8
CH2SEL
R/W
0x00
7:4
CH1SEL
R/W
0x00
3:0
CH0SEL
R/W
0x00
619


31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
CH14SEL R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7
CH13SEL R/W 0 6 CH9SEL R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 5 R/W 0 4 R/W 0 3
CH12SEL R/W 0 2 CH8SEL R/W 0 R/W 0 R/W 0 R/W 0 1 R/W 0 0
CH11SEL Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
CH10SEL R/W 0 R/W 0
Bit/Field 31:28
Name CH15SEL
Type R/W
Reset 0x00
27:24
CH14SEL
R/W
0x00
23:20
CH13SEL
R/W
0x00
19:16
CH12SEL
R/W
0x00
15:12
CH11SEL
R/W
0x00
11:8
CH10SEL
R/W
0x00
7:4
CH9SEL
R/W
0x00
3:0
CH8SEL
R/W
0x00
April 25, 2012


31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
CH22SEL R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7
CH21SEL R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3
CH20SEL R/W 0 2 R/W 0 1 R/W 0 0
CH18SEL R/W 0 R/W 0 R/W 0 R/W 0
CH16SEL R/W 0 R/W 0 R/W 0
Bit/Field 31:28
Name CH23SEL
Type R/W
Reset 0x00
27:24
CH22SEL
R/W
0x00
23:20
CH21SEL
R/W
0x00
19:16
CH20SEL
R/W
0x00
15:12
CH19SEL
R/W
0x00
11:8
CH18SEL
R/W
0x00
7:4
CH17SEL
R/W
0x00
3:0
CH16SEL
R/W
0x00
621
Register 26: DMA Channel Map Select 3 (DMACHMAP3), offset 0x51C


Base 0x400F.F000 Offset 0x51C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
CH30SEL R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7
CH29SEL R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3
CH28SEL R/W 0 2 R/W 0 1 R/W 0 0
CH24SEL R/W 0 R/W 0 R/W 0
Bit/Field 31:28
Name CH31SEL
Type R/W
Reset 0x00
27:24
CH30SEL
R/W
0x00
23:20
CH29SEL
R/W
0x00
19:16
CH28SEL
R/W
0x00
15:12
CH27SEL
R/W
0x00
11:8
CH26SEL
R/W
0x00
7:4
CH25SEL
R/W
0x00
3:0
CH24SEL
R/W
0x00
April 25, 2012
Register 27: DMA Peripheral Identification 0 (DMAPeriphID0), offset 0xFE0

The DMAPeriphIDn registers are hard-coded, and the fields within the registers determine the reset values.
DMA Peripheral Identification 0 (DMAPeriphID0)
Base 0x400F.F000 Offset 0xFE0 Type RO, reset 0x0000.0030
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 PID0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Peripheral ID Register [7:0] Can be used by software to identify the presence of this peripheral.
7:0
PID0
RO
0x30
623

Base 0x400F.F000 Offset 0xFE4 Type RO, reset 0x0000.00B2
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID1
RO
0xB2
April 25, 2012

Base 0x400F.F000 Offset 0xFE8 Type RO, reset 0x0000.000B
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID2
RO
0x0B
625
Register 30: DMA Peripheral Identification 3 (DMAPeriphID3), offset 0xFEC

The DMAPeriphIDn registers are hard-coded and the fields within the registers determine the reset values.
Base 0x400F.F000 Offset 0xFEC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID3
RO
0x00
April 25, 2012
Register 31: DMA Peripheral Identification 4 (DMAPeriphID4), offset 0xFD0

Base 0x400F.F000 Offset 0xFD0 Type RO, reset 0x0000.0004
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Peripheral ID Register Can be used by software to identify the presence of this peripheral.
7:0
PID4
RO
0x04
627
Register 32: DMA PrimeCell Identification 0 (DMAPCellID0), offset 0xFF0

The DMAPCellIDn registers are hard-coded, and the fields within the registers determine the reset values.
DMA PrimeCell Identification 0 (DMAPCellID0)
Base 0x400F.F000 Offset 0xFF0 Type RO, reset 0x0000.000D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 CID0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 0 RO 1 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA PrimeCell ID Register [7:0] Provides software a standard cross-peripheral identification system.
7:0
CID0
RO
0x0D
April 25, 2012

Base 0x400F.F000 Offset 0xFF4 Type RO, reset 0x0000.00F0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID1
RO
0xF0
629

Base 0x400F.F000 Offset 0xFF8 Type RO, reset 0x0000.0005
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x00
7:0
CID2
RO
0x05
April 25, 2012
Register 35: DMA PrimeCell Identification 3 (DMAPCellID3), offset 0xFFC

Base 0x400F.F000 Offset 0xFFC Type RO, reset 0x0000.00B1
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x00
7:0
CID3
RO
0xB1
631
General-Purpose Input/Outputs (GPIOs)
10

The GPIO module is composed of six physical GPIO blocks, each corresponding to an individual GPIO port (Port A, Port B, Port C, Port D, Port E, Port F). The GPIO module supports up to 43 programmable input/output pins, depending on the peripherals being used. The GPIO module has the following features: Up to 43 GPIOs, depending on configuration Highly flexible pin muxing allows use as GPIO or one of several peripheral functions 5-V-tolerant in input configuration Two means of port access: either Advanced High-Performance Bus (AHB) with better back-to-back access performance, or the legacy Advanced Peripheral Bus (APB) for backwards-compatibility with existing code for Ports A-G Fast toggle capable of a change every clock cycle for ports on AHB, every two clock cycles for ports on APB Programmable control for GPIO interrupts Interrupt generation masking Edge-triggered on rising, falling, or both Level-sensitive on High or Low values Bit masking in both read and write operations through address lines Can be used to initiate an ADC sample sequence or a DMA transfer Pin state can be retained during Hibernation mode Pins configured as digital inputs are Schmitt-triggered Programmable control for GPIO pad configuration Weak pull-up or pull-down resistors 2-mA, 4-mA, and 8-mA pad drive for digital communication; up to four pads can sink 18-mA for high-current applications Slew rate control for 8-mA pad drive Open drain enables Digital input enables
10.1
Signal Description
GPIO signals have alternate hardware functions. The following table lists the GPIO pins and their analog and digital alternate functions. All GPIO signals are 5-V tolerant when configured as inputs except for PB0 and PB1, which are limited to 3.6 V. The digital alternate hardware functions are
April 25, 2012
enabled by setting the appropriate bit in the GPIO Alternate Function Select (GPIOAFSEL) and GPIODEN registers and configuring the PMCx bit field in the GPIO Port Control (GPIOPCTL) register to the numeric encoding shown in the table below. Analog signals in the table below are also 5-V tolerant and are configured by clearing the DEN bit in the GPIO Digital Enable (GPIODEN) register. The AINx analog signals have internal circuitry to protect them from voltages over VDD (up to the maximum specified in Table 23-1 on page 1158), but analog performance specifications are only guaranteed if the input signal swing at the I/O pad is kept inside the range 0 V < VIN < VDD. Note that each pin must be programmed individually; no type of grouping is implied by the columns in the table. Table entries that are shaded gray are the default values for the corresponding GPIO pin. Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-1. GPIO Pins With Non-Zero Reset Values
GPIO Pins PA[1:0] PA[5:2] PB[3:2] PC[3:0] Default State UART0 SSI0 I2C0 JTAG/SWD GPIOAFSEL GPIODEN GPIOPDR GPIOPUR 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 1 GPIOPCTL 0x1 0x2 0x3 0x1
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware signals including the GPIO pins that can function as JTAG/SWD signals and the NMI signal. The commit control process must be followed for these pins, even if they are programmed as alternate functions other than JTAG/SWD or NMI, see Commit Control on page 639. Table 10-2. GPIO Pins and Alternate Functions (64LQFP)
IO PA0 PA1 PA2 PA3 PA4 PA5 PA6 PA7 PB0 PB1 PB2 PB3 PB4 PB5 PB6 Pin 17 18 19 20 21 22 23 24 45 46 47 48 58 57 1 Analog Function AIN10 AIN11 Digital Function (GPIOPCTL PMCx Bit Field Encoding) 1 U0Rx U0Tx U1Rx U1Tx 2 SSI0Clk SSI0Fss SSI0Rx SSI0Tx SSI2Clk SSI2Fss SSI2Rx 3 I2C1SCL I2C1SDA I2C0SCL I2C0SDA 4 5 6 7 T2CCP0 T2CCP1 T3CCP0 T3CCP1 8 a
9 -
14 -
15 -
T1CCP0 CAN0Rx T1CCP1 CAN0Tx T0CCP0 -
633
Table 10-2. GPIO Pins and Alternate Functions (64LQFP) (continued)

IO PB7 PC0 PC1 PC2 PC3 PC4 PC5 PC6 PC7 PD0 PD1 PD2 PD3 PD4 PD5 PD6 PD7 PE0 PE1 PE2 PE3 PE4 PE5 PF0 PF1 PF2 PF3 PF4 Pin 4 52 51 50 49 16 15 14 13 61 62 63 64 43 44 53 10 9 8 7 6 59 60 28 29 30 31 5 Analog Function C1C1+ C0+ C0AIN7 AIN6 AIN5 AIN4 USB0DM USB0DP AIN3 AIN2 AIN1 AIN0 AIN9 AIN8 Digital Function (GPIOPCTL PMCx Bit Field Encoding) 1 TCK SWCLK TMS SWDIO TDI TDO SWO U4Rx U4Tx U3Rx U3Tx 2 SSI2Tx U1Rx U1Tx 3 4 5 6 7 T0CCP1 T4CCP0 T4CCP1 T5CCP0 T5CCP1 8 a
9 C0o C1o -
14 TRD1 TRD0 TRCLK -
15 -
WT0CCP0 U1RTS WT0CCP1 U1CTS WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1 WT4CCP0 WT4CCP1 WT5CCP0 WT5CCP1 T0CCP0 T0CCP1 T1CCP0 T1CCP1 T2CCP0 NMI CAN0Rx CAN0Tx NMI -
SSI3Clk SSI1Clk I2C3SCL SSI3Fss SSI1Fss I2C3SDA SSI3Rx SSI1Rx SSI3Tx SSI1Tx U6Rx U6Tx U2Rx U2Tx U7Rx U7Tx U5Rx U5Tx U1RTS U1CTS I2C2SCL I2C2SDA
SSI1Rx CAN0Rx SSI1Tx SSI1Clk -
SSI1Fss CAN0Tx -
a. The digital signals that are shaded gray are the power-on default values for the corresponding GPIO pin. Encodings 10-13 are not used on this device.
10.2
Each GPIO port is a separate hardware instantiation of the same physical block (see Figure 10-1 on page 635 and Figure 10-2 on page 636). The LM4F120H5QR microcontroller contains six ports and thus six of these physical GPIO blocks. Note that not all pins are implemented on every block. Some GPIO pins can function as I/O signals for the on-chip peripheral modules. For information on which GPIO pins are used for alternate hardware functions, refer to Table 21-5 on page 1152.
April 25, 2012
Figure 10-1. Digital I/O Pads

Port Control GPIOPCTL Periph 0 MUX Periph 1 Periph n Pad Output Digital I/O Pad Package I/O Pin MUX Commit Control GPIOLOCK GPIOCR Mode Control GPIOAFSEL
Alternate Input Alternate Output Alternate Output Enable
DEMUX
Pad Input
Data Control GPIODATA GPIODIR Interrupt Control Interrupt GPIOIS GPIOIBE GPIOIEV GPIOIM GPIORIS GPIOMIS GPIOICR
GPIO Input GPIO Output
GPIO Output Enable
Pad Output Enable
MUX
Pad Control GPIODR2R GPIODR4R GPIODR8R GPIOSLR GPIOPUR GPIOPDR GPIOODR GPIODEN Identification Registers
GPIOPeriphID0 GPIOPeriphID1 GPIOPeriphID2 GPIOPeriphID3
GPIOPCellID0 GPIOPCellID1 GPIOPCellID2 GPIOPCellID3
635
Figure 10-2. Analog/Digital I/O Pads

Port Control GPIOPCTL Periph 0 MUX Periph 1 Periph n
Pad Output
Commit Control GPIOLOCK GPIOCR
Mode Control GPIOAFSEL

DEMUX
Alternate Input Alternate Output Alternate Output Enable
Pad Input
Analog/Digital I/O Pad
Package I/O Pin
MUX
Data Control GPIODATA GPIODIR Interrupt Control GPIOIS GPIOIBE GPIOIEV GPIOIM GPIORIS GPIOMIS GPIOICR
GPIO Input GPIO Output
MUX
Pad Output Enable
GPIO Output Enable
Interrupt
Pad Control GPIODR2R GPIODR4R GPIODR8R GPIOSLR GPIOPUR GPIOPDR GPIOODR GPIODEN GPIOAMSEL Analog Circuitry Identification Registers ADC
(for GPIO pins that connect to the ADC input MUX)
GPIOPCellID0 GPIOPCellID1 GPIOPCellID2 GPIOPCellID3
Isolation Circuit
10.2.1
Data Control
The data control registers allow software to configure the operational modes of the GPIOs. The data direction register configures the GPIO as an input or an output while the data register either captures incoming data or drives it out to the pads. Caution It is possible to create a software sequence that prevents the debugger from connecting to the Stellaris microcontroller. If the program code loaded into flash immediately changes the JTAG pins to their GPIO functionality, the debugger may not have enough time to connect and halt the controller before the JTAG pin functionality switches. As a result, the debugger may be locked out of the part. This issue can be avoided with a software routine that restores JTAG functionality based on an external or software trigger.
10.2.1.1
Data Direction Operation

The GPIO Direction (GPIODIR) register (see page 645) is used to configure each individual pin as an input or output. When the data direction bit is cleared, the GPIO is configured as an input, and the corresponding data register bit captures and stores the value on the GPIO port. When the data direction bit is set, the GPIO is configured as an output, and the corresponding data register bit is driven out on the GPIO port.
April 25, 2012
10.2.1.2
Data Register Operation

To aid in the efficiency of software, the GPIO ports allow for the modification of individual bits in the GPIO Data (GPIODATA) register (see page 644) by using bits [9:2] of the address bus as a mask. In this manner, software drivers can modify individual GPIO pins in a single instruction without affecting the state of the other pins. This method is more efficient than the conventional method of performing a read-modify-write operation to set or clear an individual GPIO pin. To implement this feature, the GPIODATA register covers 256 locations in the memory map. During a write, if the address bit associated with that data bit is set, the value of the GPIODATA register is altered. If the address bit is cleared, the data bit is left unchanged. For example, writing a value of 0xEB to the address GPIODATA + 0x098 has the results shown in Figure 10-3, where u indicates that data is unchanged by the write. Figure 10-3. GPIODATA Write Example
ADDR[9:2] 0x098 0xEB GPIODATA
9 0
8 0
7 1
6 0
5 0
4 1
3 1
2 0
1 0
0 0
u 7
u 6
1 5
u 4
u 3
0 2
1 1
u 0
During a read, if the address bit associated with the data bit is set, the value is read. If the address bit associated with the data bit is cleared, the data bit is read as a zero, regardless of its actual value. For example, reading address GPIODATA + 0x0C4 yields as shown in Figure 10-4. Figure 10-4. GPIODATA Read Example
ADDR[9:2] 0x0C4 GPIODATA Returned Value
9 0
8 0
7 1
6 1
5 0
4 0
3 0
2 1
1 0
0 0
0 7
0 6
1 5
1 4
0 3
0 2
0 1
0 0
10.2.2
Interrupt Control
The interrupt capabilities of each GPIO port are controlled by a set of seven registers. These registers are used to select the source of the interrupt, its polarity, and the edge properties. When one or more GPIO inputs cause an interrupt, a single interrupt output is sent to the interrupt controller for the entire GPIO port. For edge-triggered interrupts, software must clear the interrupt to enable any further interrupts. For a level-sensitive interrupt, the external source must hold the level constant for the interrupt to be recognized by the controller. Three registers define the edge or sense that causes interrupts: GPIO Interrupt Sense (GPIOIS) register (see page 646)
637
GPIO Interrupt Both Edges (GPIOIBE) register (see page 647) GPIO Interrupt Event (GPIOIEV) register (see page 648) Interrupts are enabled/disabled via the GPIO Interrupt Mask (GPIOIM) register (see page 649). When an interrupt condition occurs, the state of the interrupt signal can be viewed in two locations: the GPIO Raw Interrupt Status (GPIORIS) and GPIO Masked Interrupt Status (GPIOMIS) registers (see page 650 and page 651). As the name implies, the GPIOMIS register only shows interrupt conditions that are allowed to be passed to the interrupt controller. The GPIORIS register indicates that a GPIO pin meets the conditions for an interrupt, but has not necessarily been sent to the interrupt controller. Interrupts are cleared by writing a 1 to the appropriate bit of the GPIO Interrupt Clear (GPIOICR) register (see page 652). When programming the interrupt control registers (GPIOIS, GPIOIBE, or GPIOIEV), the interrupts should be masked (GPIOIM cleared). Writing any value to an interrupt control register can generate a spurious interrupt if the corresponding bits are enabled.
10.2.2.1
ADC Trigger Source

Any GPIO pin can be configured to be an external trigger for the ADC using the GPIO ADC Control (GPIOADCCTL) register. If any GPIO is configured as a non-masked interrupt pin (the appropriate bit of GPIOIM is set), and an interrupt for that port is generated, a trigger signal is sent to the ADC. If the ADC Event Multiplexer Select (ADCEMUX) register is configured to use the external trigger, an ADC conversion is initiated. See page 812. Note that if the Port B GPIOADCCTL register is cleared, PB4 can still be used as an external trigger for the ADC. This is a legacy mode which allows code written for previous Stellaris devices to operate on this microcontroller.
10.2.2.2
DMA Trigger Source

Any GPIO pin can be configured to be an external trigger for the DMA using the GPIO DMA Control (GPIODMACTL) register. If any GPIO is configured as a non-masked interrupt pin (the appropriate bit of GPIOIM is set), an interrupt for that port is generated and an external trigger signal is sent to the DMAa dma_req signal is sent to the DMA. If the DMA is configured to start a transfer based on the GPIO signal, a transfer is initiated. When transfer is complete, the dma_done signal is sent from the DMA to the GPIO and is reported as a DMA (done) interrupt in the GPIORIS register.
10.2.3
Mode Control
The GPIO pins can be controlled by either software or hardware. Software control is the default for most signals and corresponds to the GPIO mode, where the GPIODATA register is used to read or write the corresponding pins. When hardware control is enabled via the GPIO Alternate Function Select (GPIOAFSEL) register (see page 653), the pin state is controlled by its alternate function (that is, the peripheral). Further pin muxing options are provided through the GPIO Port Control (GPIOPCTL) register which selects one of several peripheral functions for each GPIO. For information on the configuration options, refer to Table 21-5 on page 1152. Note: If any pin is to be used as an ADC input, the appropriate bit in the GPIOAMSEL register must be set to disable the analog isolation circuit.
April 25, 2012
10.2.4
Commit Control
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware peripherals. Protection is provided for the GPIO pins that can be used as the four JTAG/SWD pins (PC[3:0])and the NMI pin (PD7 and PF0). Writes to protected bits of the GPIO Alternate Function Select (GPIOAFSEL) register (see page 653), GPIO Pull Up Select (GPIOPUR) register (see page 659), GPIO Pull-Down Select (GPIOPDR) register (see page 661), and GPIO Digital Enable (GPIODEN) register (see page 664) are not committed to storage unless the GPIO Lock (GPIOLOCK) register (see page 666) has been unlocked and the appropriate bits of the GPIO Commit (GPIOCR) register (see page 667) have been set.
10.2.5
Pad Control
The pad control registers allow software to configure the GPIO pads based on the application requirements. The pad control registers include the GPIODR2R, GPIODR4R, GPIODR8R, GPIOODR, GPIOPUR, GPIOPDR, GPIOSLR, and GPIODEN registers. These registers control drive strength, open-drain configuration, pull-up and pull-down resistors, slew-rate control and digital input enable for each GPIO.
10.2.6
Identification
The identification registers configured at reset allow software to detect and identify the module as a GPIO block. The identification registers include the GPIOPeriphID0-GPIOPeriphID7 registers as well as the GPIOPCellID0-GPIOPCellID3 registers.
10.3

The GPIO modules may be accessed via two different memory apertures. The legacy aperture, the Advanced Peripheral Bus (APB), is backwards-compatible with previous Stellaris parts. The other aperture, the Advanced High-Performance Bus (AHB), offers the same register map but provides better back-to-back access performance than the APB bus. These apertures are mutually exclusive. The aperture enabled for a given GPIO port is controlled by the appropriate bit in the GPIOHBCTL register (see page 249). Note that GPIO can only be accessed through the AHB aperture. To use the pins in a particular GPIO port, the clock for the port must be enabled by setting the appropriate GPIO Port bit field (GPIOn) in the RCGCGPIO register (see page 312). When the internal POR signal is asserted and until otherwise configured, all GPIO pins are configured to be undriven (tristate): GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, and GPIOPUR=0, except for the pins shown in Table 10-1 on page 633. Table 10-3 on page 639 shows all possible configurations of the GPIO pads and the control register settings required to achieve them. Table 10-4 on page 640 shows how a rising edge interrupt is configured for pin 2 of a GPIO port.
Table 10-3. GPIO Pad Configuration Examples

Configuration Digital Input (GPIO) Digital Output (GPIO) Open Drain Output (GPIO) Open Drain Input/Output (I2CSDA) Digital Input (Timer CCP) GPIO Register Bit Value AFSEL 0 0 0 1 1 DIR 0 1 1 X X
a
ODR 0 0 1 1 0
DEN 1 1 1 1 1
PUR ? ? X X ?
PDR ? ? X X ?
DR2R X ? ? ? X
DR4R X ? ? ? X
DR8R X ? ? ? X
SLR X ? ? ? X
639
Table 10-3. GPIO Pad Configuration Examples (continued)

Configuration Digital Output (Timer PWM) Digital Input/Output (SSI) Digital Input/Output (UART) Analog Input (Comparator) Digital Output (Comparator) GPIO Register Bit Value AFSEL 1 1 1 0 1 DIR X X X 0 X
a
ODR 0 0 0 0 0
DEN 1 1 1 0 1
PUR ? ? ? 0 ?
PDR ? ? ? 0 ?
DR2R ? ? ? X ?
DR4R ? ? ? X ?
DR8R ? ? ? X ?
SLR ? ? ? X ?
a. X=Ignored (dont care bit) ?=Can be either 0 or 1, depending on the configuration
Table 10-4. GPIO Interrupt Configuration Example

Register GPIOIS GPIOIBE GPIOIEV Desired Interrupt Event Trigger 0=edge 1=level 0=single edge 1=both edges 0=Low level, or falling edge 1=High level, or rising edge GPIOIM a. X=Ignored (dont care bit) 0=masked 1=not masked 0 0 0 0 0 1 0 0 X X X X X 1 X X X X X X X 0 X X Pin 2 Bit Value 7 X 6 X
a
5 X
4 X
3 X
2 0
1 X
0 X
10.4
Register Map
Table 10-6 on page 641 lists the GPIO registers. Each GPIO port can be accessed through one of two bus apertures. The legacy aperture, the Advanced Peripheral Bus (APB), is backwards-compatible with previous Stellaris parts. The other aperture, the Advanced High-Performance Bus (AHB), offers the same register map but provides better back-to-back access performance than the APB bus. Important: The GPIO registers in this chapter are duplicated in each GPIO block; however, depending on the block, all eight bits may not be connected to a GPIO pad. In those cases, writing to unconnected bits has no effect, and reading unconnected bits returns no meaningful data. The offset listed is a hexadecimal increment to the registers address, relative to that GPIO ports base address: GPIO Port A (APB): 0x4000.4000 GPIO Port A (AHB): 0x4005.8000 GPIO Port B (APB): 0x4000.5000 GPIO Port B (AHB): 0x4005.9000
April 25, 2012
GPIO Port C (APB): 0x4000.6000 GPIO Port C (AHB): 0x4005.A000 GPIO Port D (APB): 0x4000.7000 GPIO Port D (AHB): 0x4005.B000 GPIO Port E (APB): 0x4002.4000 GPIO Port E (AHB): 0x4005.C000 GPIO Port F (APB): 0x4002.5000 GPIO Port F (AHB): 0x4005.D000
Note that each GPIO module clock must be enabled before the registers can be programmed (see page 312). There must be a delay of 3 system clocks after the GPIO module clock is enabled before any GPIO module registers are accessed. Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-5. GPIO Pins With Non-Zero Reset Values
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware signals including the GPIO pins that can function as JTAG/SWD signals and the NMI signal. The commit control process must be followed for these pins, even if they are programmed as alternate functions other than JTAG/SWD or NMI, see Commit Control on page 639. The default register type for the GPIOCR register is RO for all GPIO pins with the exception of the NMI pin and the four JTAG/SWD pins (PD7, PF0, and PC[3:0]). These six pins are the only GPIOs that are protected by the GPIOCR register. Because of this, the register type for GPIO Port D7, GPIO Port F0, and GPIO Port C[3:0] is R/W. The default reset value for the GPIOCR register is 0x0000.00FF for all GPIO pins, with the exception of the NMI pin and the four JTAG/SWD pins (PD7, PF0, and PC[3:0]). To ensure that the JTAG port is not accidentally programmed as GPIO pins, the PC[3:0] pins default to non-committable. Similarly, to ensure that the NMI pin is not accidentally programmed as a GPIO pin, the PD7 and PF0 pins default to non-committable. Because of this, the default reset value of GPIOCR for GPIO Port C is 0x0000.00F0, for GPIO Port D is 0x0000.007F, and for GPIO Port F is 0x0000.00FE. Table 10-6. GPIO Register Map
Offset 0x000 0x400 0x404 Name GPIODATA GPIODIR GPIOIS Type R/W R/W R/W Reset 0x0000.0000 0x0000.0000 0x0000.0000 Description GPIO Data GPIO Direction GPIO Interrupt Sense See page 644 645 646
641
Table 10-6. GPIO Register Map (continued)

Offset 0x408 0x40C 0x410 0x414 0x418 0x41C 0x420 0x500 0x504 0x508 0x50C 0x510 0x514 0x518 0x51C 0x520 0x524 0x528 0x52C 0x530 0x534 0xFD0 0xFD4 0xFD8 0xFDC 0xFE0 0xFE4 0xFE8 0xFEC 0xFF0 0xFF4 0xFF8 Name GPIOIBE GPIOIEV GPIOIM GPIORIS GPIOMIS GPIOICR GPIOAFSEL GPIODR2R GPIODR4R GPIODR8R GPIOODR GPIOPUR GPIOPDR GPIOSLR GPIODEN GPIOLOCK GPIOCR GPIOAMSEL GPIOPCTL GPIOADCCTL GPIODMACTL GPIOPeriphID4 GPIOPeriphID5 GPIOPeriphID6 GPIOPeriphID7 GPIOPeriphID0 GPIOPeriphID1 GPIOPeriphID2 GPIOPeriphID3 GPIOPCellID0 GPIOPCellID1 GPIOPCellID2 Type R/W R/W R/W RO RO W1C R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W RO RO RO RO RO RO RO RO RO RO RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.00FF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0061 0x0000.0000 0x0000.0018 0x0000.0001 0x0000.000D 0x0000.00F0 0x0000.0005 Description GPIO Interrupt Both Edges GPIO Interrupt Event GPIO Interrupt Mask GPIO Raw Interrupt Status GPIO Masked Interrupt Status GPIO Interrupt Clear GPIO Alternate Function Select GPIO 2-mA Drive Select GPIO 4-mA Drive Select GPIO 8-mA Drive Select GPIO Open Drain Select GPIO Pull-Up Select GPIO Pull-Down Select GPIO Slew Rate Control Select GPIO Digital Enable GPIO Lock GPIO Commit GPIO Analog Mode Select GPIO Port Control GPIO ADC Control GPIO DMA Control GPIO Peripheral Identification 4 GPIO Peripheral Identification 5 GPIO Peripheral Identification 6 GPIO Peripheral Identification 7 GPIO Peripheral Identification 0 GPIO Peripheral Identification 1 GPIO Peripheral Identification 2 GPIO Peripheral Identification 3 GPIO PrimeCell Identification 0 GPIO PrimeCell Identification 1 GPIO PrimeCell Identification 2 See page 647 648 649 650 651 652 653 655 656 657 658 659 661 663 664 666 667 669 670 672 673 674 675 676 677 678 679 680 681 682 683 684
April 25, 2012
Table 10-6. GPIO Register Map (continued)

Offset 0xFFC Name GPIOPCellID3 Type RO Reset 0x0000.00B1 Description GPIO PrimeCell Identification 3 See page 685
10.5
The remainder of this section lists and describes the GPIO registers, in numerical order by address offset.
643
Register 1: GPIO Data (GPIODATA), offset 0x000

The GPIODATA register is the data register. In software control mode, values written in the GPIODATA register are transferred onto the GPIO port pins if the respective pins have been configured as outputs through the GPIO Direction (GPIODIR) register (see page 645). In order to write to GPIODATA, the corresponding bits in the mask, resulting from the address bus bits [9:2], must be set. Otherwise, the bit values remain unchanged by the write. Similarly, the values read from this register are determined for each bit by the mask bit derived from the address used to access the data register, bits [9:2]. Bits that are set in the address mask cause the corresponding bits in GPIODATA to be read, and bits that are clear in the address mask cause the corresponding bits in GPIODATA to be read as 0, regardless of their value. A read from GPIODATA returns the last bit value written if the respective pins are configured as outputs, or it returns the value on the corresponding input pin when these are configured as inputs. All bits are cleared by a reset.
GPIO Data (GPIODATA)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DATA RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Data This register is virtually mapped to 256 locations in the address space. To facilitate the reading and writing of data to these registers by independent drivers, the data read from and written to the registers are masked by the eight address lines [9:2]. Reads from this register return its current state. Writes to this register only affect bits that are not masked by ADDR[9:2] and are configured as outputs. See Data Register Operation on page 637 for examples of reads and writes.
7:0
DATA
R/W
0x00
April 25, 2012
Register 2: GPIO Direction (GPIODIR), offset 0x400

The GPIODIR register is the data direction register. Setting a bit in the GPIODIR register configures the corresponding pin to be an output, while clearing a bit configures the corresponding pin to be an input. All bits are cleared by a reset, meaning all GPIO pins are inputs by default.
GPIO Direction (GPIODIR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DIR RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Data Direction Value Description 0 1 Corresponding pin is an input. Corresponding pins is an output.
7:0
DIR
R/W
0x00
645
Register 3: GPIO Interrupt Sense (GPIOIS), offset 0x404

The GPIOIS register is the interrupt sense register. Setting a bit in the GPIOIS register configures the corresponding pin to detect levels, while clearing a bit configures the corresponding pin to detect edges. All bits are cleared by a reset.
GPIO Interrupt Sense (GPIOIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 IS RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Sense Value Description 0 1 The edge on the corresponding pin is detected (edge-sensitive). The level on the corresponding pin is detected (level-sensitive).
7:0
IS
R/W
0x00
April 25, 2012
Register 4: GPIO Interrupt Both Edges (GPIOIBE), offset 0x408

The GPIOIBE register allows both edges to cause interrupts. When the corresponding bit in the GPIO Interrupt Sense (GPIOIS) register (see page 646) is set to detect edges, setting a bit in the GPIOIBE register configures the corresponding pin to detect both rising and falling edges, regardless of the corresponding bit in the GPIO Interrupt Event (GPIOIEV) register (see page 648). Clearing a bit configures the pin to be controlled by the GPIOIEV register. All bits are cleared by a reset.
GPIO Interrupt Both Edges (GPIOIBE)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 IBE RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Both Edges Value Description 0 1 Interrupt generation is controlled by the GPIO Interrupt Event (GPIOIEV) register (see page 648). Both edges on the corresponding pin trigger an interrupt.
7:0
IBE
R/W
0x00
647
Register 5: GPIO Interrupt Event (GPIOIEV), offset 0x40C

The GPIOIEV register is the interrupt event register. Setting a bit in the GPIOIEV register configures the corresponding pin to detect rising edges or high levels, depending on the corresponding bit value in the GPIO Interrupt Sense (GPIOIS) register (see page 646). Clearing a bit configures the pin to detect falling edges or low levels, depending on the corresponding bit value in the GPIOIS register. All bits are cleared by a reset.
GPIO Interrupt Event (GPIOIEV)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x40C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 IEV RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Event Value Description 0 1 A falling edge or a Low level on the corresponding pin triggers an interrupt. A rising edge or a High level on the corresponding pin triggers an interrupt.
7:0
IEV
R/W
0x00
April 25, 2012
Register 6: GPIO Interrupt Mask (GPIOIM), offset 0x410

The GPIOIM register is the interrupt mask register. Setting a bit in the GPIOIM register allows interrupts that are generated by the corresponding pin to be sent to the interrupt controller on the combined interrupt signal. Clearing a bit prevents an interrupt on the corresponding pin from being sent to the interrupt controller. All bits are cleared by a reset.
GPIO Interrupt Mask (GPIOIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 IME RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Mask Enable Value Description 0 1 The interrupt from the corresponding pin is masked. The interrupt from the corresponding pin is sent to the interrupt controller.
7:0
IME
R/W
0x00
649
Register 7: GPIO Raw Interrupt Status (GPIORIS), offset 0x414

The GPIORIS register is the raw interrupt status register. A bit in this register is set when an interrupt condition occurs on the corresponding GPIO pin. If the corresponding bit in the GPIO Interrupt Mask (GPIOIM) register (see page 649) is set, the interrupt is sent to the interrupt controller. Bits read as zero indicate that corresponding input pins have not initiated an interrupt. A bit in this register can be cleared by writing a 1 to the corresponding bit in the GPIO Interrupt Clear (GPIOICR) register.
GPIO Raw Interrupt Status (GPIORIS)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x414 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RIS RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Raw Status Value Description 0 1 An interrupt condition has not occurred on the corresponding pin. An interrupt condition has occurred on the corresponding pin.
7:0
RIS
RO
0x00
A bit is cleared by writing a 1 to the corresponding bit in the GPIOICR register.
April 25, 2012
Register 8: GPIO Masked Interrupt Status (GPIOMIS), offset 0x418

The GPIOMIS register is the masked interrupt status register. If a bit is set in this register, the corresponding interrupt has triggered an interrupt to the interrupt controller. If a bit is clear, either no interrupt has been generated, or the interrupt is masked. Note that if the Port B GPIOADCCTL register is cleared, PB4 can still be used as an external trigger for the ADC. This is a legacy mode which allows code written for previous Stellaris devices to operate on this microcontroller. GPIOMIS is the state of the interrupt after masking.
GPIO Masked Interrupt Status (GPIOMIS)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x418 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 MIS RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Masked Interrupt Status Value Description 0 1 An interrupt condition on the corresponding pin is masked or has not occurred. An interrupt condition on the corresponding pin has triggered an interrupt to the interrupt controller.
7:0
MIS
RO
0x00
A bit is cleared by writing a 1 to the corresponding bit in the GPIOICR register.
651
Register 9: GPIO Interrupt Clear (GPIOICR), offset 0x41C

The GPIOICR register is the interrupt clear register. Writing a 1 to a bit in this register clears the corresponding interrupt bit in the GPIORIS and GPIOMIS registers. Writing a 0 has no effect.
GPIO Interrupt Clear (GPIOICR)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x41C Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 IC RO 0 RO 0 RO 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 W1C 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Interrupt Clear Value Description 0 1 The corresponding interrupt is unaffected. The corresponding interrupt is cleared.
7:0
IC
W1C
0x00
April 25, 2012
Register 10: GPIO Alternate Function Select (GPIOAFSEL), offset 0x420

The GPIOAFSEL register is the mode control select register. If a bit is clear, the pin is used as a GPIO and is controlled by the GPIO registers. Setting a bit in this register configures the corresponding GPIO line to be controlled by an associated peripheral. Several possible peripheral functions are multiplexed on each GPIO. The GPIO Port Control (GPIOPCTL) register is used to select one of the possible functions. Table 21-5 on page 1152 details which functions are muxed on each GPIO pin. The reset value for this register is 0x0000.0000 for GPIO ports that are not listed in the table below. Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-7. GPIO Pins With Non-Zero Reset Values
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware signals including the GPIO pins that can function as JTAG/SWD signals and the NMI signal. The commit control process must be followed for these pins, even if they are programmed as alternate functions other than JTAG/SWD or NMI, see Commit Control on page 639. Caution It is possible to create a software sequence that prevents the debugger from connecting to the Stellaris microcontroller. If the program code loaded into flash immediately changes the JTAG pins to their GPIO functionality, the debugger may not have enough time to connect and halt the controller before the JTAG pin functionality switches. As a result, the debugger may be locked out of the part. This issue can be avoided with a software routine that restores JTAG functionality based on an external or software trigger. The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware peripherals. Protection is provided for the GPIO pins that can be used as the four JTAG/SWD pins (PC[3:0])and the NMI pin (PD7 and PF0). Writes to protected bits of the GPIO Alternate Function Select (GPIOAFSEL) register (see page 653), GPIO Pull Up Select (GPIOPUR) register (see page 659), GPIO Pull-Down Select (GPIOPDR) register (see page 661), and GPIO Digital Enable (GPIODEN) register (see page 664) are not committed to storage unless the GPIO Lock (GPIOLOCK) register (see page 666) has been unlocked and the appropriate bits of the GPIO Commit (GPIOCR) register (see page 667) have been set. When using the I2C module, in addition to setting the GPIOAFSEL register bits for the I2C clock and data pins, the pins should be set to open drain using the GPIO Open Drain Select (GPIOODR) register (see examples in Initialization and Configuration on page 639).
653
GPIO Alternate Function Select (GPIOAFSEL)

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x420 Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 AFSEL RO 0 RO 0 RO 0 R/W R/W R/W R/W R/W R/W R/W R/W RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Alternate Function Select Value Description 0 1 The associated pin functions as a GPIO and is controlled by the GPIO registers. The associated pin functions as a peripheral signal and is controlled by the alternate hardware function. The reset value for this register is 0x0000.0000 for GPIO ports that are not listed in Table 10-1 on page 633.
7:0
AFSEL
R/W
April 25, 2012
Register 11: GPIO 2-mA Drive Select (GPIODR2R), offset 0x500

The GPIODR2R register is the 2-mA drive control register. Each GPIO signal in the port can be individually configured without affecting the other pads. When setting the DRV2 bit for a GPIO signal, the corresponding DRV4 bit in the GPIODR4R register and DRV8 bit in the GPIODR8R register are automatically cleared by hardware. By default, all GPIO pins have 2-mA drive.
GPIO 2-mA Drive Select (GPIODR2R)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x500 Type R/W, reset 0x0000.00FF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DRV2 RO 0 RO 0 RO 0 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Output Pad 2-mA Drive Enable Value Description 1 0 The corresponding GPIO pin has 2-mA drive. The drive for the corresponding GPIO pin is controlled by the GPIODR4R or GPIODR8R register.
7:0
DRV2
R/W
0xFF
Setting a bit in either the GPIODR4 register or the GPIODR8 register clears the corresponding 2-mA enable bit. The change is effective on the second clock cycle after the write if accessing GPIO via the APB memory aperture. If using AHB access, the change is effective on the next clock cycle.
655

The GPIODR4R register is the 4-mA drive control register. Each GPIO signal in the port can be individually configured without affecting the other pads. When setting the DRV4 bit for a GPIO signal, the corresponding DRV2 bit in the GPIODR2R register and DRV8 bit in the GPIODR8R register are automatically cleared by hardware.
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
DRV4
R/W
0x00
April 25, 2012

The GPIODR8R register is the 8-mA drive control register. Each GPIO signal in the port can be individually configured without affecting the other pads. When setting the DRV8 bit for a GPIO signal, the corresponding DRV2 bit in the GPIODR2R register and DRV4 bit in the GPIODR4R register are automatically cleared by hardware. The 8-mA setting is also used for high-current operation. Note: There is no configuration difference between 8-mA and high-current operation. The additional current capacity results from a shift in the VOH/VOL levels. See Recommended Operating Conditions on page 1159 for further information.

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
DRV8
R/W
0x00
657
Register 14: GPIO Open Drain Select (GPIOODR), offset 0x50C

The GPIOODR register is the open drain control register. Setting a bit in this register enables the open-drain configuration of the corresponding GPIO pad. When open-drain mode is enabled, the corresponding bit should also be set in the GPIO Digital Enable (GPIODEN) register (see page 664). Corresponding bits in the drive strength and slew rate control registers (GPIODR2R, GPIODR4R, GPIODR8R, and GPIOSLR) can be set to achieve the desired rise and fall times. The GPIO acts as an input if the corresponding bit in the GPIODIR register is cleared. If open drain is selected while the GPIO is configured as an input, the GPIO will remain an input and the open-drain selection has no effect until the GPIO is changed to an output. When using the I2C module, in addition to configuring the pin to open drain, the GPIO Alternate Function Select (GPIOAFSEL) register bits for the I2C data pins should be set (see examples in Initialization and Configuration on page 639).
GPIO Open Drain Select (GPIOODR)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x50C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 ODE RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Output Pad Open Drain Enable Value Description 1 0 The corresponding pin is configured as open drain. The corresponding pin is not configured as open drain.
7:0
ODE
R/W
0x00
April 25, 2012
Register 15: GPIO Pull-Up Select (GPIOPUR), offset 0x510

The GPIOPUR register is the pull-up control register. When a bit is set, a weak pull-up resistor on the corresponding GPIO signal is enabled. Setting a bit in GPIOPUR automatically clears the corresponding bit in the GPIO Pull-Down Select (GPIOPDR) register (see page 661). Write access to this register is protected with the GPIOCR register. Bits in GPIOCR that are cleared prevent writes to the equivalent bit in this register. Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-8. GPIO Pins With Non-Zero Reset Values
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware signals including the GPIO pins that can function as JTAG/SWD signals and the NMI signal. The commit control process must be followed for these pins, even if they are programmed as alternate functions other than JTAG/SWD or NMI, see Commit Control on page 639. Note: The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware peripherals. Protection is provided for the GPIO pins that can be used as the four JTAG/SWD pins (PC[3:0])and the NMI pin (PD7 and PF0). Writes to protected bits of the GPIO Alternate Function Select (GPIOAFSEL) register (see page 653), GPIO Pull Up Select (GPIOPUR) register (see page 659), GPIO Pull-Down Select (GPIOPDR) register (see page 661), and GPIO Digital Enable (GPIODEN) register (see page 664) are not committed to storage unless the GPIO Lock (GPIOLOCK) register (see page 666) has been unlocked and the appropriate bits of the GPIO Commit (GPIOCR) register (see page 667) have been set.
659
GPIO Pull-Up Select (GPIOPUR)

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x510 Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 PUE RO 0 RO 0 RO 0 R/W R/W R/W R/W R/W R/W R/W R/W RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Pad Weak Pull-Up Enable Value Description 1 0 The corresponding pin has a weak pull-up resistor. The corresponding pin is not affected.
7:0
PUE
R/W
Setting a bit in the GPIOPDR register clears the corresponding bit in the GPIOPUR register. The change is effective on the second clock cycle after the write if accessing GPIO via the APB memory aperture. If using AHB access, the change is effective on the next clock cycle. The reset value for this register is 0x0000.0000 for GPIO ports that are not listed in Table 10-1 on page 633.
April 25, 2012
Register 16: GPIO Pull-Down Select (GPIOPDR), offset 0x514

The GPIOPDR register is the pull-down control register. When a bit is set, a weak pull-down resistor on the corresponding GPIO signal is enabled. Setting a bit in GPIOPDR automatically clears the corresponding bit in the GPIO Pull-Up Select (GPIOPUR) register (see page 659). Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-9. GPIO Pins With Non-Zero Reset Values
661
GPIO Pull-Down Select (GPIOPDR)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 PDE RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Pad Weak Pull-Down Enable Value Description 1 0 The corresponding pin has a weak pull-down resistor. The corresponding pin is not affected.
7:0
PDE
R/W
0x00
Setting a bit in the GPIOPUR register clears the corresponding bit in the GPIOPDR register. The change is effective on the second clock cycle after the write if accessing GPIO via the APB memory aperture. If using AHB access, the change is effective on the next clock cycle.
April 25, 2012
Register 17: GPIO Slew Rate Control Select (GPIOSLR), offset 0x518
The GPIOSLR register is the slew rate control register. Slew rate control is only available when using the 8-mA drive strength option via the GPIO 8-mA Drive Select (GPIODR8R) register (see page 657).
GPIO Slew Rate Control Select (GPIOSLR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 SRL RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Slew Rate Limit Enable (8-mA drive only) Value Description 1 0 Slew rate control is enabled for the corresponding pin. Slew rate control is disabled for the corresponding pin.
7:0
SRL
R/W
0x00
663
Register 18: GPIO Digital Enable (GPIODEN), offset 0x51C

Note: Pins configured as digital inputs are Schmitt-triggered. The GPIODEN register is the digital enable register. By default, all GPIO signals except those listed below are configured out of reset to be undriven (tristate). Their digital function is disabled; they do not drive a logic value on the pin and they do not allow the pin voltage into the GPIO receiver. To use the pin as a digital input or output (either GPIO or alternate function), the corresponding GPIODEN bit must be set. Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-10. GPIO Pins With Non-Zero Reset Values
April 25, 2012
GPIO Digital Enable (GPIODEN)

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x51C Type R/W, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DEN RO 0 RO 0 RO 0 R/W R/W R/W R/W R/W R/W R/W R/W RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Enable Value Description 0 1 The digital functions for the corresponding pin are disabled. The digital functions for the corresponding pin are enabled. The reset value for this register is 0x0000.0000 for GPIO ports that are not listed in Table 10-1 on page 633.
7:0
DEN
R/W
665
Register 19: GPIO Lock (GPIOLOCK), offset 0x520

The GPIOLOCK register enables write access to the GPIOCR register (see page 667). Writing 0x4C4F.434B to the GPIOLOCK register unlocks the GPIOCR register. Writing any other value to the GPIOLOCK register re-enables the locked state. Reading the GPIOLOCK register returns the lock status rather than the 32-bit value that was previously written. Therefore, when write accesses are disabled, or locked, reading the GPIOLOCK register returns 0x0000.0001. When write accesses are enabled, or unlocked, reading the GPIOLOCK register returns 0x0000.0000.
GPIO Lock (GPIOLOCK)
31 30 29 28 27 26 25 24 LOCK Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 LOCK Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 1 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name LOCK
Type R/W
Reset
Description
0x0000.0001 GPIO Lock A write of the value 0x4C4F.434B unlocks the GPIO Commit (GPIOCR) register for write access.A write of any other value or a write to the GPIOCR register reapplies the lock, preventing any register updates. A read of this register returns the following values: Value Description 0x1 0x0 The GPIOCR register is locked and may not be modified. The GPIOCR register is unlocked and may be modified.
April 25, 2012
Register 20: GPIO Commit (GPIOCR), offset 0x524

The GPIOCR register is the commit register. The value of the GPIOCR register determines which bits of the GPIOAFSEL, GPIOPUR, GPIOPDR, and GPIODEN registers are committed when a write to these registers is performed. If a bit in the GPIOCR register is cleared, the data being written to the corresponding bit in the GPIOAFSEL, GPIOPUR, GPIOPDR, or GPIODEN registers cannot be committed and retains its previous value. If a bit in the GPIOCR register is set, the data being written to the corresponding bit of the GPIOAFSEL, GPIOPUR, GPIOPDR, or GPIODEN registers is committed to the register and reflects the new value. The contents of the GPIOCR register can only be modified if the status in the GPIOLOCK register is unlocked. Writes to the GPIOCR register are ignored if the status in the GPIOLOCK register is locked. Important: This register is designed to prevent accidental programming of the registers that control connectivity to the NMI and JTAG/SWD debug hardware. By initializing the bits of the GPIOCR register to 0 for PD7, PF0, and PC[3:0], the NMI and JTAG/SWD debug port can only be converted to GPIOs through a deliberate set of writes to the GPIOLOCK, GPIOCR, and the corresponding registers. Because this protection is currently only implemented on the NMI and JTAG/SWD pins on PD7, PF0, and PC[3:0], all of the other bits in the GPIOCR registers cannot be written with 0x0. These bits are hardwired to 0x1, ensuring that it is always possible to commit new values to the GPIOAFSEL, GPIOPUR, GPIOPDR, or GPIODEN register bits of these other pins.
GPIO Commit (GPIOCR)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x524 Type -, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 CR RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
667
Bit/Field 7:0
Name CR
Type -
Reset -
Description GPIO Commit Value Description 1 0 The corresponding GPIOAFSEL, GPIOPUR, GPIOPDR, or GPIODEN bits can be written. The corresponding GPIOAFSEL, GPIOPUR, GPIOPDR, or GPIODEN bits cannot be written. The default register type for the GPIOCR register is RO for all GPIO pins with the exception of the NMI pin and the four JTAG/SWD pins (PD7, PF0, and PC[3:0]). These six pins are the only GPIOs that are protected by the GPIOCR register. Because of this, the register type for GPIO Port D7, GPIO Port F0, and GPIO Port C[3:0] is R/W. The default reset value for the GPIOCR register is 0x0000.00FF for all GPIO pins, with the exception of the NMI pin and the four JTAG/SWD pins (PD7, PF0, and PC[3:0]). To ensure that the JTAG port is not accidentally programmed as GPIO pins, the PC[3:0] pins default to non-committable. Similarly, to ensure that the NMI pin is not accidentally programmed as a GPIO pin, the PD7 and PF0 pins default to non-committable. Because of this, the default reset value of GPIOCR for GPIO Port C is 0x0000.00F0, for GPIO Port D is 0x0000.007F, and for GPIO Port F is 0x0000.00FE.
Note:
April 25, 2012
Register 21: GPIO Analog Mode Select (GPIOAMSEL), offset 0x528

Important: This register is only valid for ports and pins that can be used as ADC AINx inputs. If any pin is to be used as an ADC input, the appropriate bit in GPIOAMSEL must be set to disable the analog isolation circuit. The GPIOAMSEL register controls isolation circuits to the analog side of a unified I/O pad. Because the GPIOs may be driven by a 5-V source and affect analog operation, analog circuitry requires isolation from the pins when they are not used in their analog function. Each bit of this register controls the isolation circuitry for the corresponding GPIO signal. For information on which GPIO pins can be used for ADC functions, refer to Table 21-5 on page 1152.
GPIO Analog Mode Select (GPIOAMSEL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
GPIOAMSEL R/W 0 R/W 0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Analog Mode Select Value Description 1 0 The analog function of the pin is enabled, the isolation is disabled, and the pin is capable of analog functions. The analog function of the pin is disabled, the isolation is enabled, and the pin is capable of digital functions as specified by the other GPIO configuration registers. This register and bits are only valid for GPIO signals that share analog function through a unified I/O pad.
3:0
GPIOAMSEL
R/W
0x0
Note:
The reset state of this register is 0 for all signals.
669
Register 22: GPIO Port Control (GPIOPCTL), offset 0x52C

The GPIOPCTL register is used in conjunction with the GPIOAFSEL register and selects the specific peripheral signal for each GPIO pin when using the alternate function mode. Most bits in the GPIOAFSEL register are cleared on reset, therefore most GPIO pins are configured as GPIOs by default. When a bit is set in the GPIOAFSEL register, the corresponding GPIO signal is controlled by an associated peripheral. The GPIOPCTL register selects one out of a set of peripheral functions for each GPIO, providing additional flexibility in signal definition. For information on the defined encodings for the bit fields in this register, refer to Table 21-5 on page 1152. The reset value for this register is 0x0000.0000 for GPIO ports that are not listed in the table below. Note: If the same signal is assigned to two different GPIO port pins, the signal is assigned to the port with the lowest letter and the assignment to the higher letter port is ignored.
Important: All GPIO pins are configured as GPIOs and tri-stated by default (GPIOAFSEL=0, GPIODEN=0, GPIOPDR=0, GPIOPUR=0, and GPIOPCTL=0), with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 10-11. GPIO Pins With Non-Zero Reset Values
The GPIO commit control registers provide a layer of protection against accidental programming of critical hardware signals including the GPIO pins that can function as JTAG/SWD signals and the NMI signal. The commit control process must be followed for these pins, even if they are programmed as alternate functions other than JTAG/SWD or NMI, see Commit Control on page 639.
GPIO Port Control (GPIOPCTL)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0x52C Type R/W, reset 31 30 PMC7 Type Reset R/W 15 R/W 14 PMC3 Type Reset R/W R/W R/W R/W R/W R/W R/W 13 R/W 12 R/W 11 R/W 10 PMC2 R/W R/W R/W R/W 29 28 27 26 PMC6 R/W 9 R/W 8 R/W 7 R/W 6 PMC1 R/W R/W R/W R/W 25 24 23 22 PMC5 R/W 5 R/W 4 R/W 3 R/W 2 PMC0 R/W R/W 21 20 19 18 PMC4 R/W 1 R/W 0 17 16
April 25, 2012
Bit/Field 31:28
Name PMC7
Type R/W
Reset -
Description Port Mux Control 7 This field controls the configuration for GPIO pin 7.
27:24
PMC6
R/W
Port Mux Control 6 This field controls the configuration for GPIO pin 6.
23:20
PMC5
R/W
19:16
PMC4
R/W
15:12
PMC3
R/W
11:8
PMC2
R/W
7:4
PMC1
R/W
3:0
PMC0
R/W
671
Register 23: GPIO ADC Control (GPIOADCCTL), offset 0x530

This register is used to configure a GPIO pin as a source for the ADC trigger. Note that if the Port B GPIOADCCTL register is cleared, PB4 can still be used as an external trigger for the ADC. This is a legacy mode which allows code written for previous Stellaris devices to operate on this microcontroller.
GPIO ADC Control (GPIOADCCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 ADCEN RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Trigger Enable Value Description 1 0 The corresponding pin is used to trigger the ADC. The corresponding pin is not used to trigger the ADC.
7:0
ADCEN
R/W
0x00
April 25, 2012
Register 24: GPIO DMA Control (GPIODMACTL), offset 0x534

This register is used to configure a GPIO pin as a source for the DMA trigger.
GPIO DMA Control (GPIODMACTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DMAEN RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA Trigger Enable Value Description 1 0 The corresponding pin is used to trigger the DMA. The corresponding pin is not used to trigger the DMA.
7:0
DMAEN
R/W
0x00
673
Register 25: GPIO Peripheral Identification 4 (GPIOPeriphID4), offset 0xFD0

The GPIOPeriphID4, GPIOPeriphID5, GPIOPeriphID6, and GPIOPeriphID7 registers can conceptually be treated as one 32-bit register; each register contains eight bits of the 32-bit register, used by software to identify the peripheral.
GPIO Peripheral Identification 4 (GPIOPeriphID4)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFD0 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Peripheral ID Register [7:0]
7:0
PID4
RO
0x00
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID5
RO
0x00
675

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID6
RO
0x00
April 25, 2012
Register 28: GPIO Peripheral Identification 7 (GPIOPeriphID7), offset 0xFDC

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFDC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID7
RO
0x00
677
Register 29: GPIO Peripheral Identification 0 (GPIOPeriphID0), offset 0xFE0

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFE0 Type RO, reset 0x0000.0061
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO Peripheral ID Register [7:0] Can be used by software to identify the presence of this peripheral.
7:0
PID0
RO
0x61
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID1
RO
0x00
679

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID2
RO
0x18
April 25, 2012
Register 32: GPIO Peripheral Identification 3 (GPIOPeriphID3), offset 0xFEC

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFEC Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID3
RO
0x01
681
Register 33: GPIO PrimeCell Identification 0 (GPIOPCellID0), offset 0xFF0

The GPIOPCellID0, GPIOPCellID1, GPIOPCellID2, and GPIOPCellID3 registers are four 8-bit wide registers, that can conceptually be treated as one 32-bit register. The register is used as a standard cross-peripheral identification system.
GPIO PrimeCell Identification 0 (GPIOPCellID0)
GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFF0 Type RO, reset 0x0000.000D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPIO PrimeCell ID Register [7:0] Provides software a standard cross-peripheral identification system.
7:0
CID0
RO
0x0D
April 25, 2012

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFF4 Type RO, reset 0x0000.00F0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID1
RO
0xF0
683

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFF8 Type RO, reset 0x0000.0005
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID2
RO
0x05
April 25, 2012
Register 36: GPIO PrimeCell Identification 3 (GPIOPCellID3), offset 0xFFC

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000 Offset 0xFFC Type RO, reset 0x0000.00B1
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID3
RO
0xB1
685
General-Purpose Timers
11
Programmable timers can be used to count or time external events that drive the Timer input pins. The Stellaris General-Purpose Timer Module (GPTM) contains six 16/32-bit GPTM blocks and six 32/64-bit Wide GPTM blocks. Each 16/32-bit GPTM block provides two 16-bit timers/counters (referred to as Timer A and Timer B) that can be configured to operate independently as timers or event counters, or concatenated to operate as one 32-bit timer or one 32-bit Real-Time Clock (RTC). Each 32/64-bit Wide GPTM block provides 32-bit timers for Timer A and Timer B that can be concatenated to operate as a 64-bit timer. Timers can also be used to trigger DMA transfers. In addition, timers can be used to trigger analog-to-digital conversions (ADC). The ADC trigger signals from all of the general-purpose timers are ORed together before reaching the ADC module, so only one timer should be used to trigger ADC events. The GPT Module is one timing resource available on the Stellaris microcontrollers. Other timer resources include the System Timer (SysTick) (see 119). The General-Purpose Timer Module (GPTM) contains six 16/32-bit GPTM blocks and six 32/64-bit Wide GPTM blocks with the following functional options: 16/32-bit operating modes: 16- or 32-bit programmable one-shot timer 16- or 32-bit programmable periodic timer 16-bit general-purpose timer with an 8-bit prescaler 32-bit Real-Time Clock (RTC) when using an external 32.768-KHz clock as the input 16-bit input-edge count- or time-capture modes with an 8-bit prescaler 16-bit PWM mode with an 8-bit prescaler and software-programmable output inversion of the PWM signal 32/64-bit operating modes: 32- or 64-bit programmable one-shot timer 32- or 64-bit programmable periodic timer 32-bit general-purpose timer with a 16-bit prescaler 64-bit Real-Time Clock (RTC) when using an external 32.768-KHz clock as the input 32-bit input-edge count- or time-capture modes with a16-bit prescaler 32-bit PWM mode with a 16-bit prescaler and software-programmable output inversion of the PWM signal Count up or down Twelve 16/32-bit Capture Compare PWM pins (CCP) Twelve 32/64-bit Capture Compare PWM pins (CCP)
April 25, 2012
Daisy chaining of timer modules to allow a single timer to initiate multiple timing events Timer synchronization allows selected timers to start counting on the same clock cycle ADC event trigger User-enabled stalling when the microcontroller asserts CPU Halt flag during debug (excluding RTC mode) Ability to determine the elapsed time between the assertion of the timer interrupt and entry into the interrupt service routine. Efficient transfers using Micro Direct Memory Access Controller (DMA) Dedicated channel for each timer Burst request generated on timer interrupt
11.1
Block Diagram
In the block diagram, the specific Capture Compare PWM (CCP) pins available depend on the Stellaris device. See Table 11-1 on page 687 for the available CCP pins and their timer assignments.
Figure 11-1. GPTM Module Block Diagram

0xFFFF.FFFF (Up Counter Modes, 32-/64-bit) 0x0000.0000 (Down Counter Modes, 32-/64-bit) 0xFFFF (Up Counter Modes, 16-/32-bit) 0x0000 (Down Counter Modes, 16-/32-bit) Timer A Free-Running Value Timer A Control GPTMTAPS GPTMTAPMR GPTMTAPR
GPTMTAMATCHR
TA Comparator Clock / Edge Detect GPTMTAR En GPTMTAPV GPTMTAV GPTMTBV GPTMTBPV RTC Divider RTC Predivider GPTMRTCPD
Interrupt / Config GPTMCFG Timer A Interrupt GPTMCTL GPTMIMR GPTMRIS Timer B Interrupt GPTMMIS GPTMICR GPTMSYNC GPTMPP
GPTMTAILR GPTMTAMR
32 KHz or Even CCP Pin
Timer B Control GPTMTBMR GPTMTBILR

GPTMTBMATCHR
GPTMTBR En Clock / Edge Detect TB Comparator Odd CCP Pin
GPTMTBPR Timer B Free-Running Value GPTMTBPMR GPTMTBPS 0x0000 (Down Counter Modes, 16-/32-bit) 0xFFFF (Up Counter Modes, 16-/32-bit) 0x0000.0000 (Down Counter Modes, 32-/64-bit) 0xFFFF.FFFF (Up Counter Modes, 32-/64-bit)
System Clock
Table 11-1. Available CCP Pins

Timer 16/32-Bit Timer 0 Up/Down Counter Timer A Even CCP Pin T0CCP0 Odd CCP Pin -
687
Table 11-1. Available CCP Pins (continued)

Timer Up/Down Counter Timer B 16/32-Bit Timer 1 Timer A Timer B 16/32-Bit Timer 2 Timer A Timer B 16/32-Bit Timer 3 Timer A Timer B 16/32-Bit Timer 4 Timer A Timer B 16/32-Bit Timer 5 Timer A Timer B 32/64-Bit Wide Timer 0 Timer A Timer B 32/64-Bit Wide Timer 1 Timer A Timer B 32/64-Bit Wide Timer 2 Timer A Timer B 32/64-Bit Wide Timer 3 Timer A Timer B 32/64-Bit Wide Timer 4 Timer A Timer B 32/64-Bit Wide Timer 5 Timer A Timer B Even CCP Pin T1CCP0 T2CCP0 T3CCP0 T4CCP0 T5CCP0 WT0CCP0 WT1CCP0 WT2CCP0 WT3CCP0 WT4CCP0 WT5CCP0 Odd CCP Pin T0CCP1 T1CCP1 T2CCP1 T3CCP1 T4CCP1 T5CCP1 WT0CCP1 WT1CCP1 WT2CCP1 WT3CCP1 WT4CCP1 WT5CCP1
11.2
Signal Description
The following table lists the external signals of the GP Timer module and describes the function of each. The GP Timer signals are alternate functions for some GPIO signals and default to be GPIO signals at reset. The column in the table below titled "Pin Mux/Pin Assignment" lists the possible GPIO pin placements for these GP Timer signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the GP Timer function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the GP Timer signal to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
Table 11-2. General-Purpose Timers Signals (64LQFP)

Pin Name T0CCP0 T0CCP1 T1CCP0 Pin Number Pin Mux / Pin Assignment 1 28 4 29 30 58 PB6 (7) PF0 (7) PB7 (7) PF1 (7) PF2 (7) PB4 (7) Pin Type I/O I/O I/O Buffer Type TTL TTL TTL
a
Description 16/32-Bit Timer 0 Capture/Compare/PWM 0. 16/32-Bit Timer 0 Capture/Compare/PWM 1. 16/32-Bit Timer 1 Capture/Compare/PWM 0.
April 25, 2012
Table 11-2. General-Purpose Timers Signals (64LQFP) (continued)

Pin Name T1CCP1 T2CCP0 T2CCP1 T3CCP0 T3CCP1 T4CCP0 T4CCP1 T5CCP0 T5CCP1 WT0CCP0 WT0CCP1 WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1 WT4CCP0 WT4CCP1 WT5CCP0 WT5CCP1 Pin Number Pin Mux / Pin Assignment 31 57 5 45 46 47 48 52 51 50 49 16 15 14 13 61 62 63 64 43 44 53 10 PF3 (7) PB5 (7) PF4 (7) PB0 (7) PB1 (7) PB2 (7) PB3 (7) PC0 (7) PC1 (7) PC2 (7) PC3 (7) PC4 (7) PC5 (7) PC6 (7) PC7 (7) PD0 (7) PD1 (7) PD2 (7) PD3 (7) PD4 (7) PD5 (7) PD6 (7) PD7 (7) Pin Type I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description 16/32-Bit Timer 1 Capture/Compare/PWM 1. 16/32-Bit Timer 2 Capture/Compare/PWM 0. 16/32-Bit Timer 2 Capture/Compare/PWM 1. 16/32-Bit Timer 3 Capture/Compare/PWM 0. 16/32-Bit Timer 3 Capture/Compare/PWM 1. 16/32-Bit Timer 4 Capture/Compare/PWM 0. 16/32-Bit Timer 4 Capture/Compare/PWM 1. 16/32-Bit Timer 5 Capture/Compare/PWM 0. 16/32-Bit Timer 5 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 1.
11.3
The main components of each GPTM block are two free-running up/down counters (referred to as Timer A and Timer B), two match registers, two prescaler match registers, two shadow registers, and two load/initialization registers and their associated control functions. The exact functionality of each GPTM is controlled by software and configured through the register interface. Timer A and Timer B can be used individually, in which case they have a 16-bit counting range for the 16/32-bit GPTM blocks and a 32-bit counting range for 32/64-bit Wide GPTM blocks. In addition, Timer A and Timer B can be concatenated to provide a 32-bit counting range for the 16/32-bit GPTM blocks and a 64-bit counting range for the 32/64-bit Wide GPTM blocks. Note that the prescaler can only be used when the timers are used individually. The available modes for each GPTM block are shown in Table 11-3 on page 690. Note that when counting down in one-shot or periodic modes, the prescaler acts as a true prescaler and contains the least-significant bits of the count. When counting up in one-shot or periodic modes, the prescaler acts as a timer extension and holds the most-significant bits of the count. In input edge count, input edge time and PWM mode, the prescaler always acts as a timer extension, regardless of the count direction.
689
Table 11-3. General-Purpose Timer Capabilities

Mode Timer Use Individual One-shot Concatenated Individual Periodic Concatenated RTC Edge Count Edge Time PWM Concatenated Individual Individual Individual Up or Down Up Up or Down Up or Down Down 32-bit 32-bit 16-bit 16-bit 16-bit 64-bit 64-bit 32-bit 32-bit 32-bit 8-bit 8-bit 8-bit 16-bit 16-bit 16-bit Up or Down Up or Down 32-bit 16-bit 64-bit 32-bit 8-bit 16-bit Count Direction Up or Down Counter Size 16/32-bit GPTM 16-bit 32/64-bit Wide GPTM 32-bit Prescaler Size 16/32-bit GPTM 8-bit
a
32/64-bit Wide GPTM 16-bit
Prescaler Behavior (Count Direction) Timer Extension (Up), Prescaler (Down) N/A Timer Extension (Up), Prescaler (Down) N/A N/A Timer Extension (Both) Timer Extension (Both) Timer Extension
a. The prescaler is only available when the timers are used individually
Software configures the GPTM using the GPTM Configuration (GPTMCFG) register (see page 709), the GPTM Timer A Mode (GPTMTAMR) register (see page 711), and the GPTM Timer B Mode (GPTMTBMR) register (see page 715). When in one of the concatentated modes, Timer A and Timer B can only operate in one mode. However, when configured in an individual mode, Timer A and Timer B can be independently configured in any combination of the individual modes.
11.3.1
GPTM Reset Conditions

After reset has been applied to the GPTM module, the module is in an inactive state, and all control registers are cleared and in their default states. Counters Timer A and Timer B are initialized to all 1s, along with their corresponding load registers: the GPTM Timer A Interval Load (GPTMTAILR) register (see page 738) and the GPTM Timer B Interval Load (GPTMTBILR) register (see page 739) and shadow registers: the GPTM Timer A Value (GPTMTAV) register (see page 748) and the GPTM Timer B Value (GPTMTBV) register (see page 749). The prescale counters are initialized to 0x00: the GPTM Timer A Prescale (GPTMTAPR) register (see page 742), the GPTM Timer B Prescale (GPTMTBPR) register (see page 743), the GPTM Timer A Prescale Snapshot (GPTMTAPS) register (see page 751), the GPTM Timer B Prescale Snapshot (GPTMTBPS) register (see page 752), the GPTM Timer A Prescale Value (GPTMTAPV) register (see page 753), and the GPTM Timer B Prescale Value (GPTMTBPV) register (see page 754).
11.3.2
Timer Modes
This section describes the operation of the various timer modes. When using Timer A and Timer B in concatenated mode, only the Timer A control and status bits must be used; there is no need to use Timer B control and status bits. The GPTM is placed into individual/split mode by writing a value of 0x4 to the GPTM Configuration (GPTMCFG) register (see page 709). In the following sections, the variable "n" is used in bit field and register names to imply either a Timer A function or a Timer B function. Throughout this section, the timeout event in down-count mode is 0x0 and in up-count mode is the value in the GPTM Timer n Interval Load (GPTMTnILR) and the optional GPTM Timer n Prescale (GPTMTnPR) registers.
April 25, 2012
11.3.2.1
One-Shot/Periodic Timer Mode

The selection of one-shot or periodic mode is determined by the value written to the TnMR field of the GPTM Timer n Mode (GPTMTnMR) register (see page 711). The timer is configured to count up or down using the TnCDIR bit in the GPTMTnMR register. When software sets the TnEN bit in the GPTM Control (GPTMCTL) register (see page 719), the timer begins counting up from 0x0 or down from its preloaded value. Alternatively, if the TnWOT bit is set in the GPTMTnMR register, once the TnEN bit is set, the timer waits for a trigger to begin counting (see Wait-for-Trigger Mode on page 700). Table 11-4 on page 691 shows the values that are loaded into the timer registers when the timer is enabled. Table 11-4. Counter Values When the Timer is Enabled in Periodic or One-Shot Modes
Register TnR TnV TnPS TnPV Count Down Mode GPTMTnILR GPTMTnILR GPTMTnPR in individual mode; not available in concatenated mode GPTMTnPR in individual mode; not available in concatenated mode Count Up Mode 0x0 0x0 0x0 in individual mode; not available in concatenated mode 0x0 in individual mode; not available in concatenated mode
When the timer is counting down and it reaches the timeout event (0x0), the timer reloads its start value from the GPTMTnILR and the GPTMTnPR registers on the next cycle. When the timer is counting up and it reaches the timeout event (the value in the GPTMTnILR and the optional GPTMTnPR registers), the timer reloads with 0x0. If configured to be a one-shot timer, the timer stops counting and clears the TnEN bit in the GPTMCTL register. If configured as a periodic timer, the timer starts counting again on the next cycle. In periodic, snap-shot mode (TnMR field is 0x2 and the TnSNAPS bit is set in the GPTMTnMR register), the value of the timer at the time-out event is loaded into the GPTMTnR register and the value of the prescaler is loaded into the GPTMTnPS register. The free-running counter value is shown in the GPTMTnV register and the free-running prescaler value is shown in the GPTMTnPV register. In this manner, software can determine the time elapsed from the interrupt assertion to the ISR entry by examining the snapshot values and the current value of the free-running timer. Snapshot mode is not available when the timer is configured in one-shot mode. In addition to reloading the count value, the GPTM generates interrupts and triggers when it reaches the time-out event. The GPTM sets the TnTORIS bit in the GPTM Raw Interrupt Status (GPTMRIS) register (see page 730), and holds it until it is cleared by writing the GPTM Interrupt Clear (GPTMICR) register (see page 736). If the time-out interrupt is enabled in the GPTM Interrupt Mask (GPTMIMR) register (see page 727), the GPTM also sets the TnTOMIS bit in the GPTM Masked Interrupt Status (GPTMMIS) register (see page 733). By setting the TnMIE bit in the GPTMTnMR register, an interrupt condition can also be generated when the Timer value equals the value loaded into the GPTM Timer n Match (GPTMTnMATCHR) and GPTM Timer n Prescale Match (GPTMTnPMR) registers. This interrupt has the same status, masking, and clearing functions as the time-out interrupt, but uses the match interrupt bits instead (for example, the raw interrupt status is monitored via TnMRIS bit in the GPTM Raw Interrupt Status (GPTMRIS) register). Note that the interrupt status bits are not updated by the hardware unless the TnMIE bit in the GPTMTnMR register is set, which is different than the behavior for the time-out interrupt. The ADC trigger is enabled by setting the TnOTE bit in GPTMCTL. The DMA trigger is enabled by configuring and enabling the appropriate DMA channel. See Channel Configuration on page 572. If software updates the GPTMTnILR or the GPTMTnPR register while the counter is counting down, the counter loads the new value on the next clock cycle and continues counting from the new value
691
if the TnILD bit in the GPTMTnMR register is clear. If the TnILD bit is set, the counter loads the new value after the next timeout. If software updates the GPTMTnILR or the GPTMTnPR register while the counter is counting up, the timeout event is changed on the next cycle to the new value. If software updates the GPTM Timer n Value (GPTMTnV) register while the counter is counting up or down, the counter loads the new value on the next clock cycle and continues counting from the new value. If software updates the GPTMTnMATCHR or the GPTMTnPMR registers, the new values are reflected on the next clock cycle if the TnMRSU bit in the GPTMTnMR register is clear. If the TnMRSU bit is set, the new value don't take effect until the next timeout. When using a 32/64-bit wide timer block in a 64-bit mode, certain registers must be accessed in the manner described in Accessing Concatenated 32/64-Bit Wide GPTM Register Values on page 702. If the TnSTALL bit in the GPTMCTL register is set, the timer freezes counting while the processor is halted by the debugger. The timer resumes counting when the processor resumes execution. The following table shows a variety of configurations for a 16-bit free-running timer while using the prescaler. All values assume an 80-MHz clock with Tc=12.5 ns (clock period). The prescaler can only be used when a 16/32-bit timer is configured in 16-bit mode and when a 32/64-bit timer is configured in 32-bit mode. Table 11-5. 16-Bit Timer With Prescaler Configurations
Prescale (8-bit value) 00000000 00000001 00000010 -----------11111101 11111110 11111111 a. Tc is the clock period. # of Timer Clocks (Tc) 1 2 3 -254 255 256
a
Max Time 0.8192 1.6384 2.4576 -208.0768 208.896 209.7152
Units ms ms ms -ms ms ms
The following table shows a variety of configurations for a 32-bit free-running timer using the prescaler while configured in 32/64-bit mode. All values assume an 80-MHz clock with Tc=12.5 ns (clock period). Table 11-6. 32-Bit Timer (configured in 32/64-bit mode) With Prescaler Configurations
Prescale (16-bit value) 0x0000 0x0001 0x0002 -----------0xFFFD 0xFFFE 0xFFFF a. Tc is the clock period. # of Timer Clocks (Tc) 1 2 3 -65534 65535 65536
a
Max Time 53.687 107.374 214.748 -0.879 1.759 3.518
Units s s s -106 s 106 s 106 s
11.3.2.2
Real-Time Clock Timer Mode

In Real-Time Clock (RTC) mode, the concatenated versions of the Timer A and Timer B registers are configured as an up-counter. When RTC mode is selected for the first time after reset, the
April 25, 2012
counter is loaded with a value of 0x1. All subsequent load values must be written to the GPTM Timer n Interval Load (GPTMTnILR) registers (see page 738). Table 11-7 on page 693 shows the values that are loaded into the timer registers when the timer is enabled. Table 11-7. Counter Values When the Timer is Enabled in RTC Mode
Register TnR TnV TnPS TnPV Count Down Mode Not available Not available Not available Not available Count Up Mode 0x1 0x1 Not available Not available
The input clock on a CCP0 input is required to be 32.768 KHz in RTC mode. The clock signal is then divided down to a 1-Hz rate and is passed along to the input of the counter. When software writes the TAEN bit in the GPTMCTL register, the counter starts counting up from its preloaded value of 0x1. When the current count value matches the preloaded value in the GPTMTnMRTATCHR registers, the GPTM asserts the RTCRIS bit in GPTMRIS and continues counting until either a hardware reset, or it is disabled by software (clearing the TAEN bit). When the timer value reaches the terminal count, the timer rolls over and continues counting up from 0x0. If the RTC interrupt is enabled in GPTMIMR, the GPTM also sets the RTCMIS bit in GPTMMIS and generates a controller interrupt. The status flags are cleared by writing the RTCCINT bit in GPTMICR. In this mode, the GPTMTnR and GPTMTnV registers always have the same value. When using a 32/64-bit wide timer block in a RTC mode, certain registers must be accessed in the manner described in Accessing Concatenated 32/64-Bit Wide GPTM Register Values on page 702. The value of the RTC predivider can be read in the GPTM RTC Predivide (GPTMRTCPD) register. To ensure that the RTC value is coherent, software should follow the process detailed in Figure 11-2 on page 694.
693
Figure 11-2. Reading the RTC Value

Read Timer B = B1
Read Timer A = A1
Read Predivider
Read Timer A = A2
Does A1=A2?
no
yes Read Timer B = B2
Does B1=B2?
no
yes Done
In addition to generating interrupts, a DMA trigger can be generated. The DMA trigger is enabled by configuring and enabling the appropriate DMA channel. See Channel Configuration on page 572. If the TASTALL bit in the GPTMCTL register is set, the timer does not freeze when the processor is halted by the debugger if the RTCEN bit is set in GPTMCTL.
11.3.2.3
Input Edge-Count Mode

Note: For rising-edge detection, the input signal must be High for at least two system clock periods following the rising edge. Similarly, for falling-edge detection, the input signal must be Low for at least two system clock periods following the falling edge. Based on this criteria, the maximum input frequency for edge detection is 1/4 of the system frequency.
In Edge-Count mode, the timer is configured as a 24-bit or 48-bit up- or down-counter including the optional prescaler with the upper count value stored in the GPTM Timer n Prescale (GPTMTnPR) register and the lower bits in the GPTMTnR register. In this mode, the timer is capable of capturing three types of events: rising edge, falling edge, or both. To place the timer in Edge-Count mode, the TnCMR bit of the GPTMTnMR register must be cleared. The type of edge that the timer counts is determined by the TnEVENT fields of the GPTMCTL register. During initialization in down-count mode, the GPTMTnMATCHR and GPTMTnPMR registers are configured so that the difference
April 25, 2012
between the value in the GPTMTnILR and GPTMTnPR registers and the GPTMTnMATCHR and GPTMTnPMR registers equals the number of edge events that must be counted. In up-count mode, the timer counts from 0x0 to the value in the GPTMTnMATCHR and GPTMTnPMR registers. Table 11-8 on page 695 shows the values that are loaded into the timer registers when the timer is enabled. Table 11-8. Counter Values When the Timer is Enabled in Input Edge-Count Mode
Register TnR TnV TnPS TnPV Count Down Mode GPTMTnILR GPTMTnILR GPTMTnPR GPTMTnPR Count Up Mode 0x0 0x0 0x0 0x0
When software writes the TnEN bit in the GPTM Control (GPTMCTL) register, the timer is enabled for event capture. Each input event on the CCP pin decrements or increments the counter by 1 until the event count matches GPTMTnMATCHR and GPTMTnPMR. When the counts match, the GPTM asserts the CnMRIS bit in the GPTM Raw Interrupt Status (GPTMRIS) register, and holds it until it is cleared by writing the GPTM Interrupt Clear (GPTMICR) register. If the capture mode match interrupt is enabled in the GPTM Interrupt Mask (GPTMIMR) register, the GPTM also sets the CnMMIS bit in the GPTM Masked Interrupt Status (GPTMMIS) register. In this mode, the GPTMTnR and GPTMTnPS registers hold the count of the input events while the GPTMTnV and GPTMTnPV registers hold the free-running timer value and the free-running prescaler value. In addition to generating interrupts, an ADC and/or a DMA trigger can be generated. The ADC trigger is enabled by setting the TnOTE bit in GPTMCTL.The DMA trigger is enabled by configuring and enabling the appropriate DMA channel. See Channel Configuration on page 572. After the match value is reached in down-count mode, the counter is then reloaded using the value in GPTMTnILR and GPTMTnPR registers, and stopped because the GPTM automatically clears the TnEN bit in the GPTMCTL register. Once the event count has been reached, all further events are ignored until TnEN is re-enabled by software. In up-count mode, the timer is reloaded with 0x0 and continues counting. Figure 11-3 on page 696 shows how Input Edge-Count mode works. In this case, the timer start value is set to GPTMTnILR =0x000A and the match value is set to GPTMTnMATCHR =0x0006 so that four edge events are counted. The counter is configured to detect both edges of the input signal. Note that the last two edges are not counted because the timer automatically clears the TnEN bit after the current count matches the value in the GPTMTnMATCHR register.
695
Figure 11-3. Input Edge-Count Mode Example, Counting Down

Timer stops, flags asserted Timer reload on next cycle
Count
Ignored
Ignored
0x000A 0x0009 0x0008 0x0007 0x0006
Input Signal
11.3.2.4
Input Edge-Time Mode

Note: For rising-edge detection, the input signal must be High for at least two system clock periods following the rising edge. Similarly, for falling edge detection, the input signal must be Low for at least two system clock periods following the falling edge. Based on this criteria, the maximum input frequency for edge detection is 1/4 of the system frequency.
In Edge-Time mode, the timer is configured as a 24-bit or 48-bit up- or down-counter including the optional prescaler with the upper timer value stored in the GPTMTnPR) register and the lower bits in the GPTMTnILR register. In this mode, the timer is initialized to the value loaded in the GPTMTnILR and GPTMTnPR registers when counting down and 0x0 when counting up. The timer is capable of capturing three types of events: rising edge, falling edge, or both. The timer is placed into Edge-Time mode by setting the TnCMR bit in the GPTMTnMR register, and the type of event that the timer captures is determined by the TnEVENT fields of the GPTMCTL register. Table 11-9 on page 696 shows the values that are loaded into the timer registers when the timer is enabled. Table 11-9. Counter Values When the Timer is Enabled in Input Event-Count Mode
Register TnR TnV TnPS TnPV Count Down Mode GPTMTnILR GPTMTnILR GPTMTnPR GPTMTnPR Count Up Mode 0x0 0x0 0x0 0x0
When software writes the TnEN bit in the GPTMCTL register, the timer is enabled for event capture. When the selected input event is detected, the current timer counter value is captured in the GPTMTnR and GPTMTnPS registers and is available to be read by the microcontroller. The GPTM then asserts the CnERIS bit in the GPTM Raw Interrupt Status (GPTMRIS) register, and holds it until it is cleared by writing the GPTM Interrupt Clear (GPTMICR) register. If the capture mode event interrupt is enabled in the GPTM Interrupt Mask (GPTMIMR) register, the GPTM also sets the CnEMIS bit in the GPTM Masked Interrupt Status (GPTMMIS) register. In this mode, the
April 25, 2012
GPTMTnR and GPTMTnPSregisters hold the time at which the selected input event occurred while the GPTMTnV and GPTMTnPV registers hold the free-running timer value and the free-running prescaler value. These registers can be read to determine the time that elapsed between the interrupt assertion and the entry into the ISR. In addition to generating interrupts, an ADC and/or a DMA trigger can be generated. The ADC trigger is enabled by setting the TnOTE bit in GPTMCTL.The DMA trigger is enabled by configuring and enabling the appropriate DMA channel. See Channel Configuration on page 572. After an event has been captured, the timer does not stop counting. It continues to count until the TnEN bit is cleared. When the timer reaches the timeout value, it is reloaded with 0x0 in up-count mode and the value from the GPTMTnILR and GPTMTnPR registers in down-count mode. Figure 11-4 on page 697 shows how input edge timing mode works. In the diagram, it is assumed that the start value of the timer is the default value of 0xFFFF, and the timer is configured to capture rising edge events. Each time a rising edge event is detected, the current count value is loaded into the GPTMTnR and GPTMTnPS registers, and is held there until another rising edge is detected (at which point the new count value is loaded into the GPTMTnR and GPTMTnPS registers). Figure 11-4. 16-Bit Input Edge-Time Mode Example
Count
0xFFFF
GPTMTnR=X
GPTMTnR=Y
GPTMTnR=Z
Y Time
Input Signal
Note:
When operating in Edge-time mode, the counter uses a modulo 224 count if prescalar is enabled or 216, if not. If there is a possibility the edge could take longer than the count, then another timer can be implemented to ensure detection of the missed edge.
11.3.2.5
PWM Mode
The GPTM supports a simple PWM generation mode. In PWM mode, the timer is configured as a 24-bit or 48-bit down-counter with a start value (and thus period) defined by the GPTMTnILR and GPTMTnPR registers. In this mode, the PWM frequency and period are synchronous events and therefore guaranteed to be glitch free. PWM mode is enabled with the GPTMTnMR register by setting the TnAMS bit to 0x1, the TnCMR bit to 0x0, and the TnMR field to 0x1 or 0x2. Table 11-10 on page 698 shows the values that are loaded into the timer registers when the timer is enabled.
697
Table 11-10. Counter Values When the Timer is Enabled in PWM Mode
Register GPTMTnR GPTMTnV GPTMTnPS GPTMTnPV Count Down Mode GPTMTnILR GPTMTnILR GPTMTnPR GPTMTnPR Count Up Mode Not available Not available Not available Not available
When software writes the TnEN bit in the GPTMCTL register, the counter begins counting down until it reaches the 0x0 state. Alternatively, if the TnWOT bit is set in the GPTMTnMR register, once the TnEN bit is set, the timer waits for a trigger to begin counting (see Wait-for-Trigger Mode on page 700). On the next counter cycle in periodic mode, the counter reloads its start value from the GPTMTnILR and GPTMTnPR registers and continues counting until disabled by software clearing the TnEN bit in the GPTMCTL register. The timer is capable of generating interrupts based on three types of events: rising edge, falling edge, or both. The event is configured by the TnEVENT field of the GPTMCTL register, and the interrupt is enabled by setting the TnPWMIE bit in the GPTMTnMR register. When the event occurs, the CnERIS bit is set in the GPTM Raw Interrupt Status (GPTMRIS) register, and holds it until it is cleared by writing the GPTM Interrupt Clear (GPTMICR) register . If the capture mode event interrupt is enabled in the GPTM Interrupt Mask (GPTMIMR) register , the GPTM also sets the CnEMIS bit in the GPTM Masked Interrupt Status (GPTMMIS) register. Note that the interrupt status bits are not updated unless the TnPWMIE bit is set. In this mode, the GPTMTnR and GPTMTnV registers always have the same value, as do the GPTMPnPS and the GPTMTnPV registers. The output PWM signal asserts when the counter is at the value of the GPTMTnILR and GPTMTnPR registers (its start state), and is deasserted when the counter value equals the value in the GPTMTnMATCHR and GPTMTnPMR registers. Software has the capability of inverting the output PWM signal by setting the TnPWML bit in the GPTMCTL register. Note: If PWM output inversion is enabled, edge detection interrupt behavior is reversed. Thus, if a positive-edge interrupt trigger has been set and the PWM inversion generates a positive edge, no event-trigger interrupt asserts. Instead, the interrupt is generated on the negative edge of the PWM signal.
Figure 11-5 on page 699 shows how to generate an output PWM with a 1-ms period and a 66% duty cycle assuming a 50-MHz input clock and TnPWML =0 (duty cycle would be 33% for the TnPWML =1 configuration). For this example, the start value is GPTMTnILR=0xC350 and the match value is GPTMTnMATCHR=0x411A.
April 25, 2012
Figure 11-5. 16-Bit PWM Mode Example

Count
0xC350 GPTMTnR=GPTMnMR GPTMTnR=GPTMnMR
0x411A
Time
TnEN set TnPWML = 0
Output Signal
TnPWML = 1
When synchronizing the timers using the GPTMSYNC register, the timer must be properly configured to avoid glitches on the CCP outputs. Both the PLO and the MRSU bits must be set in the GPTMTnMR register. Figure 11-6 on page 699 shows how the CCP output operates when the PLO and MRSU bits are set and the GPTMTnMATCHR value is greater than the GPTMTnILR value. Figure 11-6. CCP Output, GPTMTnMATCHR > GPTMTnILR
GPTMnILR
GPTMnMATCHR
CCP CCP set if GPTMnMATCHR GPTMnILR

Figure 11-7 on page 700 shows how the CCP output operates when the PLO and MRSU bits are set and the GPTMTnMATCHR value is the same as the GPTMTnILR value. In this situation, if the PLO
CounterValue
699
bit is 0, the CCP signal goes high when the GPTMTnILR value is loaded and the match would be essentially ignored. Figure 11-7. CCP Output, GPTMTnMATCHR = GPTMTnILR
GPTMnILR
GPTMnMATCHR
CCP CCP not set if GPTMnMATCHR = GPTMnILR

Figure 11-8 on page 700 shows how the CCP output operates when the PLO and MRSU bits are set and the GPTMTnILR is greater than the GPTMTnMATCHR value. Figure 11-8. CCP Output, GPTMTnILR > GPTMTnMATCHR
GPTMnILR GPTMnMATCHR = GPTMnILR-1 GPTMnMATCHR = GPTMnILR-2
CounterValue
GPTMnMATCHR == 0
CCP CCP CCP
Pulse width is 1 clock when GPTMnMATCHR = GPTMnILR - 1 Pulse width is 2 clocks when GPTMnMATCHR = GPTMnILR - 2 Pulse width is GPTMnILR clocks when GPTMnMATCHR= 0
11.3.3
Wait-for-Trigger Mode
The Wait-for-Trigger mode allows daisy chaining of the timer modules such that once configured, a single timer can initiate mulitple timing events using the Timer triggers. Wait-for-Trigger mode is enabled by setting the TnWOT bit in the GPTMTnMR register. When the TnWOT bit is set, Timer N+1 does not begin counting until the timer in the previous position in the daisy chain (Timer N) reaches its time-out event. The daisy chain is configured such that GPTM1 always follows GPTM0, GPTM2 follows GPTM1, and so on. If Timer A is configured as a 32-bit (16/32-bit mode) or 64-bit (32/64-bit wide mode) timer (controlled by the GPTMCFG field in the GPTMCFG register), it triggers Timer A
April 25, 2012
in the next module. If Timer A is configured as a 16-bit (16/32-bit mode) or 32-bit (32/64-bit wide mode) timer, it triggers Timer B in the same module, and Timer B triggers Timer A in the next module. Care must be taken that the TAWOT bit is never set in GPTM0. Figure 11-9 on page 701 shows how the GPTMCFG bit affects the daisy chain. This function is valid for one-shot, periodic, and PWM modes. Figure 11-9. Timer Daisy Chain
GP Timer N+1
1 0 GPTMCFG
Timer B Timer A
Timer B ADC Trigger Timer A ADC Trigger
GP Timer N
1 0 GPTMCFG
Timer B Timer A
Timer B ADC Trigger Timer A ADC Trigger
11.3.4
Synchronizing GP Timer Blocks

The GPTM Synchronizer Control (GPTMSYNC) register in the GPTM0 block can be used to synchronize selected timers to begin counting at the same time. Setting a bit in the GPTMSYNC register causes the associated timer to perform the actions of a timeout event. An interrupt is not generated when the timers are synchronized. If a timer is being used in concatenated mode, only the bit for Timer A must be set in the GPTMSYNC register. Table 11-11 on page 701 shows the actions for the timeout event performed when the timers are synchronized in the various timer modes. Table 11-11. Timeout Actions for GPTM Modes
Mode Count Dir Time Out Action N/A Count value = ILR Count value = 0 Count value = 0 N/A Count value = ILR Count value = 0 Count value = ILR Count value = 0 Count value = ILR Count value = 0 Count value = ILR 32- and 64-bit One-Shot (concatenated timers) 32- and 64-bit Periodic (concatenated timers) 32- and 64-bit RTC (concatenated timers) Down Up Up
16- and 32- bit One Shot (individual/split timers) 16- and 32- bit Periodic Down (individual/split timers) Up 16- and 32- bit Edge-Count (individual/split timers) 16- and 32- bit Edge-Time (individual/split timers) 16- and 32-bit PWM Down Up Down Up Down
701
11.3.5
DMA Operation
The timers each have a dedicated DMA channel and can provide a request signal to the DMA controller. The request is a burst type and occurs whenever a timer raw interrupt condition occurs. The arbitration size of the DMA transfer should be set to the amount of data that should be transferred whenever a timer event occurs. For example, to transfer 256 items, 8 items at a time every 10 ms, configure a timer to generate a periodic timeout at 10 ms. Configure the DMA transfer for a total of 256 items, with a burst size of 8 items. Each time the timer times out, the DMA controller transfers 8 items, until all 256 items have been transferred. No other special steps are needed to enable Timers for DMA operation. Refer to Micro Direct Memory Access (DMA) on page 568 for more details about programming the DMA controller.
11.3.6
Accessing Concatenated 16/32-Bit GPTM Register Values

The GPTM is placed into concatenated mode by writing a 0x0 or a 0x1 to the GPTMCFG bit field in the GPTM Configuration (GPTMCFG) register. In both configurations, certain 16/32-bit GPTM registers are concatenated to form pseudo 32-bit registers. These registers include: GPTM Timer A Interval Load (GPTMTAILR) register [15:0], see page 738 GPTM Timer B Interval Load (GPTMTBILR) register [15:0], see page 739 GPTM Timer A (GPTMTAR) register [15:0], see page 746 GPTM Timer B (GPTMTBR) register [15:0], see page 747 GPTM Timer A Value (GPTMTAV) register [15:0], see page 748 GPTM Timer B Value (GPTMTBV) register [15:0], see page 749 GPTM Timer A Match (GPTMTAMATCHR) register [15:0], see page 740 GPTM Timer B Match (GPTMTBMATCHR) register [15:0], see page 741 In the 32-bit modes, the GPTM translates a 32-bit write access to GPTMTAILR into a write access to both GPTMTAILR and GPTMTBILR. The resulting word ordering for such a write operation is: GPTMTBILR[15:0]:GPTMTAILR[15:0] Likewise, a 32-bit read access to GPTMTAR returns the value: GPTMTBR[15:0]:GPTMTAR[15:0] A 32-bit read access to GPTMTAV returns the value: GPTMTBV[15:0]:GPTMTAV[15:0]
11.3.7
Accessing Concatenated 32/64-Bit Wide GPTM Register Values

On the 32/64-bit Wide GPTM blocks, concatenated register values (64-bits and 48-bits) are not readily available as the bit width for these accesses is greater than the bus width of the processor core. In the concatenated timer modes and the individual timer modes when using the prescaler, software must perform atomic accesses for the value to be coherent. When reading timer values that are greater than 32 bits, software should follow these steps:
April 25, 2012
1. Read the appropriate Timer B register or prescaler register. 2. Read the corresponding Timer A register. 3. Re-read the Timer B register or prescaler register. 4. Compare the Timer B or prescaler values from the first and second reads. If they are the same, the timer value is coherent. If they are not the same, repeat steps 1-4 once more so that they are the same. The following pseudo code illustrates this process: high = timer_high; low = timer_low; if (high != timer_high); { high = timer_high; low = timer_low; } The registers that must be read in this manner are shown below: 64-bit reads GPTMTAV and GPTMTBV GPTMTAR and GPTMTBR 48-bit reads GPTMTAR and GPTMTAPS GPTMTBR and GPTMTBPS GPTMTAV and GPTMTAPV GPTMTBV and GPTMTBPV Similarly, write accesses must also be performed by writing the upper bits prior to writing the lower bits as follows: 1. Write the appropriate Timer B register or prescaler register. 2. Write the corresponding Timer A register. The registers that must be written in this manner are shown below: 64-bit writes GPTMTAV and GPTMTBV //low overflowed into high
703
GPTMTAMATCHR and GPTMTBMATCHR GPTMTAILR and GPTMTBILR 48-bit writes GPTMTAV and GPTMTAPV GPTMTBV and GPTMTBPV GPTMTAMATCHR and GPTMTAPMR GPTMTBMATCHR and GPTMTBPMR GPTMTAILR and GPTMTAPR GPTMTBILR and GPTMTBPR When writing a 64-bit value, If there are two consecutive writes to any of the registers listed above under the "64-bit writes" heading, whether the register is in Timer A or Timer B, or if a register Timer A is written prior to writing the corresponding register in Timer B, then an error is reported using the WUERIS bit in the GPTMRIS register. This error can be promoted to interrupt if it is not masked. Note that this error is not reported for the prescaler registers because use of the prescaler is optional. As a result, programmers must take care to follow the protocol outlined above.
11.4

To use a GPTM, the appropriate TIMERn bit must be set in the RCGCTIMER or RCGCWTIMER register (see page 310 and page 327). If using any CCP pins, the clock to the appropriate GPIO module must be enabled via the RCGCGPIO register (see page 312). To find out which GPIO port to enable, refer to Table 21-4 on page 1148. Configure the PMCn fields in the GPIOPCTL register to assign the CCP signals to the appropriate pins (see page 670 and Table 21-5 on page 1152). This section shows module initialization and configuration examples for each of the supported timer modes.
11.4.1
One-Shot/Periodic Timer Mode

The GPTM is configured for One-Shot and Periodic modes by the following sequence: 1. Ensure the timer is disabled (the TnEN bit in the GPTMCTL register is cleared) before making any changes. 2. Write the GPTM Configuration Register (GPTMCFG) with a value of 0x0000.0000. 3. Configure the TnMR field in the GPTM Timer n Mode Register (GPTMTnMR): a. Write a value of 0x1 for One-Shot mode. b. Write a value of 0x2 for Periodic mode. 4. Optionally configure the TnSNAPS, TnWOT, TnMTE, and TnCDIR bits in the GPTMTnMR register to select whether to capture the value of the free-running timer at time-out, use an external trigger to start counting, configure an additional trigger or interrupt, and count up or down. 5. Load the start value into the GPTM Timer n Interval Load Register (GPTMTnILR).
April 25, 2012
6. If interrupts are required, set the appropriate bits in the GPTM Interrupt Mask Register (GPTMIMR). 7. Set the TnEN bit in the GPTMCTL register to enable the timer and start counting. 8. Poll the GPTMRIS register or wait for the interrupt to be generated (if enabled). In both cases, the status flags are cleared by writing a 1 to the appropriate bit of the GPTM Interrupt Clear Register (GPTMICR). If the TnMIE bit in the GPTMTnMR register is set, the RTCRIS bit in the GPTMRIS register is set, and the timer continues counting. In One-Shot mode, the timer stops counting after the time-out event. To re-enable the timer, repeat the sequence. A timer configured in Periodic mode reloads the timer and continues counting after the time-out event.
11.4.2
Real-Time Clock (RTC) Mode

To use the RTC mode, the timer must have a 32.768-KHz input signal on an even CCP input. To enable the RTC feature, follow these steps: 1. Ensure the timer is disabled (the TAEN bit is cleared) before making any changes. 2. Write the GPTM Configuration Register (GPTMCFG) with a value of 0x0000.0001. 3. Write the match value to the GPTM Timer n Match Register (GPTMTnMATCHR). 4. Set/clear the RTCEN bit in the GPTM Control Register (GPTMCTL) as needed. 5. If interrupts are required, set the RTCIM bit in the GPTM Interrupt Mask Register (GPTMIMR). 6. Set the TAEN bit in the GPTMCTL register to enable the timer and start counting. When the timer count equals the value in the GPTMTnMATCHR register, the GPTM asserts the RTCRIS bit in the GPTMRIS register and continues counting until Timer A is disabled or a hardware reset. The interrupt is cleared by writing the RTCCINT bit in the GPTMICR register.
11.4.3
Input Edge-Count Mode

A timer is configured to Input Edge-Count mode by the following sequence: 1. Ensure the timer is disabled (the TnEN bit is cleared) before making any changes. 2. Write the GPTM Configuration (GPTMCFG) register with a value of 0x0000.0004. 3. In the GPTM Timer Mode (GPTMTnMR) register, write the TnCMR field to 0x0 and the TnMR field to 0x3. 4. Configure the type of event(s) that the timer captures by writing the TnEVENT field of the GPTM Control (GPTMCTL) register. 5. If a prescaler is to be used, write the prescale value to the GPTM Timer n Prescale Register (GPTMTnPR). 6. Load the timer start value into the GPTM Timer n Interval Load (GPTMTnILR) register. 7. Load the event count into the GPTM Timer n Match (GPTMTnMATCHR) register.
705
8. If interrupts are required, set the CnMIM bit in the GPTM Interrupt Mask (GPTMIMR) register. 9. Set the TnEN bit in the GPTMCTL register to enable the timer and begin waiting for edge events. 10. Poll the CnMRIS bit in the GPTMRIS register or wait for the interrupt to be generated (if enabled). In both cases, the status flags are cleared by writing a 1 to the CnMCINT bit of the GPTM Interrupt Clear (GPTMICR) register. When counting down in Input Edge-Count Mode, the timer stops after the programmed number of edge events has been detected. To re-enable the timer, ensure that the TnEN bit is cleared and repeat #4 on page 705 through #9 on page 706.
11.4.4
Input Edge Timing Mode

A timer is configured to Input Edge Timing mode by the following sequence: 1. Ensure the timer is disabled (the TnEN bit is cleared) before making any changes. 2. Write the GPTM Configuration (GPTMCFG) register with a value of 0x0000.0004. 3. In the GPTM Timer Mode (GPTMTnMR) register, write the TnCMR field to 0x1 and the TnMR field to 0x3. 4. Configure the type of event that the timer captures by writing the TnEVENT field of the GPTM Control (GPTMCTL) register. 5. If a prescaler is to be used, write the prescale value to the GPTM Timer n Prescale Register (GPTMTnPR). 6. Load the timer start value into the GPTM Timer n Interval Load (GPTMTnILR) register. 7. If interrupts are required, set the CnEIM bit in the GPTM Interrupt Mask (GPTMIMR) register. 8. Set the TnEN bit in the GPTM Control (GPTMCTL) register to enable the timer and start counting. 9. Poll the CnERIS bit in the GPTMRIS register or wait for the interrupt to be generated (if enabled). In both cases, the status flags are cleared by writing a 1 to the CnECINT bit of the GPTM Interrupt Clear (GPTMICR) register. The time at which the event happened can be obtained by reading the GPTM Timer n (GPTMTnR) register. In Input Edge Timing mode, the timer continues running after an edge event has been detected, but the timer interval can be changed at any time by writing the GPTMTnILR register. The change takes effect at the next cycle after the write.
11.4.5
PWM Mode
A timer is configured to PWM mode using the following sequence: 1. Ensure the timer is disabled (the TnEN bit is cleared) before making any changes. 2. Write the GPTM Configuration (GPTMCFG) register with a value of 0x0000.0004. 3. In the GPTM Timer Mode (GPTMTnMR) register, set the TnAMS bit to 0x1, the TnCMR bit to 0x0, and the TnMR field to 0x2.
April 25, 2012
4. Configure the output state of the PWM signal (whether or not it is inverted) in the TnPWML field of the GPTM Control (GPTMCTL) register. 5. If a prescaler is to be used, write the prescale value to the GPTM Timer n Prescale Register (GPTMTnPR). 6. If PWM interrupts are used, configure the interrupt condition in the TnEVENT field in the GPTMCTL register and enable the interrupts by setting the TnPWMIE bit in the GPTMTnMR register. Note that edge detect interrupt behavior is reversed when the PWM output is inverted (see page 719). 7. Load the timer start value into the GPTM Timer n Interval Load (GPTMTnILR) register. 8. Load the GPTM Timer n Match (GPTMTnMATCHR) register with the match value. 9. Set the TnEN bit in the GPTM Control (GPTMCTL) register to enable the timer and begin generation of the output PWM signal. In PWM Timing mode, the timer continues running after the PWM signal has been generated. The PWM period can be adjusted at any time by writing the GPTMTnILR register, and the change takes effect at the next cycle after the write.
11.5
Register Map
Table 11-12 on page 707 lists the GPTM registers. The offset listed is a hexadecimal increment to the registers address, relative to that timers base address: 16/32-bit Timer 0: 0x4003.0000 16/32-bit Timer 1: 0x4003.1000 16/32-bit Timer 2: 0x4003.2000 16/32-bit Timer 3: 0x4003.3000 16/32-bit Timer 4: 0x4003.4000 16/32-bit Timer 5: 0x4003.5000 32/64-bit Wide Timer 0: 0x4003.6000 32/64-bit Wide Timer 1: 0x4003.7000 32/64-bit Wide Timer 2: 0x4004.C000 32/64-bit Wide Timer 3: 0x4004.D000 32/64-bit Wide Timer 4: 0x4004.E000 32/64-bit Wide Timer 5: 0x4004.F000
The SIZE field in the GPTM Peripheral Properties (GPTMPP) register identifies whether a module has a 16/32-bit or 32/64-bit wide timer. Note that the GP Timer module clock must be enabled before the registers can be programmed (see page 310 or page 327). There must be a delay of 3 system clocks after the Timer module clock is enabled before any Timer module registers are accessed. Table 11-12. Timers Register Map
Offset 0x000 0x004 Name GPTMCFG GPTMTAMR Type R/W R/W Reset 0x0000.0000 0x0000.0000 Description GPTM Configuration GPTM Timer A Mode See page 709 711
707
Table 11-12. Timers Register Map (continued)

Offset 0x008 0x00C 0x010 0x018 0x01C 0x020 0x024 0x028 0x02C 0x030 0x034 0x038 0x03C 0x040 0x044 0x048 0x04C 0x050 0x054 0x058 0x05C 0x060 0x064 0x068 0xFC0 Name GPTMTBMR GPTMCTL GPTMSYNC GPTMIMR GPTMRIS GPTMMIS GPTMICR GPTMTAILR GPTMTBILR GPTMTAMATCHR GPTMTBMATCHR GPTMTAPR GPTMTBPR GPTMTAPMR GPTMTBPMR GPTMTAR GPTMTBR GPTMTAV GPTMTBV GPTMRTCPD GPTMTAPS GPTMTBPS GPTMTAPV GPTMTBPV GPTMPP Type R/W R/W R/W R/W RO RO W1C R/W R/W R/W R/W R/W R/W R/W R/W RO RO RW RW RO RO RO RO RO RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0xFFFF.FFFF 0xFFFF.FFFF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0xFFFF.FFFF 0xFFFF.FFFF 0x0000.7FFF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description GPTM Timer B Mode GPTM Control GPTM Synchronize GPTM Interrupt Mask GPTM Raw Interrupt Status GPTM Masked Interrupt Status GPTM Interrupt Clear GPTM Timer A Interval Load GPTM Timer B Interval Load GPTM Timer A Match GPTM Timer B Match GPTM Timer A Prescale GPTM Timer B Prescale GPTM TimerA Prescale Match GPTM TimerB Prescale Match GPTM Timer A GPTM Timer B GPTM Timer A Value GPTM Timer B Value GPTM RTC Predivide GPTM Timer A Prescale Snapshot GPTM Timer B Prescale Snapshot GPTM Timer A Prescale Value GPTM Timer B Prescale Value GPTM Peripheral Properties See page 715 719 723 727 730 733 736 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755
11.6
The remainder of this section lists and describes the GPTM registers, in numerical order by address offset.
April 25, 2012
Register 1: GPTM Configuration (GPTMCFG), offset 0x000

This register configures the global operation of the GPTM module. The value written to this register determines whether the GPTM is in 32- or 64-bit mode (concatenated timers) or in 16- or 32-bit mode (individual, split timers). Important: Bits in this register should only be changed when the TAEN and TBEN bits in the GPTMCTL register are cleared.
GPTM Configuration (GPTMCFG)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 GPTMCFG R/W 0 R/W 0 RO 0 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
709
Bit/Field 2:0
Name GPTMCFG
Type R/W
Reset 0x0
Description GPTM Configuration The GPTMCFG values are defined as follows: Value 0x0 Description For a 16/32-bit timer, this value selects the 32-bit timer configuration. For a 32/64-bit wide timer, this value selects the 64-bit timer configuration. 0x1 For a 16/32-bit timer, this value selects the 32-bit real-time clock (RTC) counter configuration. For a 32/64-bit wide timer, this value selects the 64-bit real-time clock (RTC) counter configuration. 0x2-0x3 Reserved 0x4 For a 16/32-bit timer, this value selects the 16-bit timer configuration. For a 32/64-bit wide timer, this value selects the 32-bit timer configuration. The function is controlled by bits 1:0 of GPTMTAMR and GPTMTBMR. 0x5-0x7 Reserved
April 25, 2012
Register 2: GPTM Timer A Mode (GPTMTAMR), offset 0x004

This register configures the GPTM based on the configuration selected in the GPTMCFG register. When in PWM mode, set the TAAMS bit, clear the TACMR bit, and configure the TAMR field to 0x1 or 0x2. This register controls the modes for Timer A when it is used individually. When Timer A and Timer B are concatenated, this register controls the modes for both Timer A and Timer B, and the contents of GPTMTBMR are ignored. Important: Except for the TCACT bit field, all other bits in this register should only be changed when the TAEN bit in the GPTMCTL register is cleared.
GPTM Timer A Mode (GPTMTAMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TAPLO RO 0 R/W 0 RO 0 10 RO 0 9 RO 0 8 TAILD R/W 0 RO 0 7 RO 0 6 RO 0 5 TAMIE R/W 0 RO 0 4 TACDIR R/W 0 RO 0 3 TAAMS R/W 0 RO 0 2 TACMR R/W 0 R/W 0 RO 0 1 TAMR R/W 0 RO 0 0
reserved Type Reset RO 0 RO 0 RO 0
TAMRSU TAPWMIE R/W 0 R/W 0
TASNAPS TAWOT R/W 0 R/W 0
Bit/Field 31:12
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A PWM Legacy Operation Value Description 0 1 Legacy operation with CCP pin driven Low when the GPTMTAILR is reloaded after the timer reaches 0. CCP is driven High when the GPTMTAILR is reloaded after the timer reaches 0.
11
TAPLO
R/W
This bit is only valid in PWM mode.
711
Bit/Field 10
Name TAMRSU
Type R/W
Reset 0
Description GPTM Timer A Match Register Update Value Description 0 1 Update the GPTMTAMATCHR register and the GPTMTAPR register, if used, on the next cycle. Update the GPTMTAMATCHR register and the GPTMTAPR register, if used, on the next timeout.
If the timer is disabled (TAEN is clear) when this bit is set, GPTMTAMATCHR and GPTMTAPR are updated when the timer is enabled. If the timer is stalled (TASTALL is set), GPTMTAMATCHR and GPTMTAPR are updated according to the configuration of this bit. 9 TAPWMIE R/W 0 GPTM Timer A PWM Interrupt Enable This bit enables interrupts in PWM mode on rising, falling, or both edges of the CCP output, as defined by the TAEVENT field in the GPTMCTL register. Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
This bit is only valid in PWM mode. 8 TAILD R/W 0 GPTM Timer A Interval Load Write Value Description 0 Update the GPTMTAR and GPTMTAV registers with the value in the GPTMTAILR register on the next cycle. Also update the GPTMTAPS and GPTMTAPV registers with the value in the GPTMTAPR register on the next cycle. Update the GPTMTAR and GPTMTAV registers with the value in the GPTMTAILR and GPTMTAPV registers on the next timeout. Also update the GPTMTAPS register with the value in the GPTMTAPR register on the next timeout.
Note the state of this bit has no effect when counting up. The bit descriptions above apply if the timer is enabled and running. If the timer is disabled (TAEN is clear) when this bit is set, GPTMTAR, GPTMTAV, GPTMTAPS, and GPTMTAPV are updated when the timer is enabled. If the timer is stalled (TASTALL is set), GPTMTAR and GPTMTAPS are updated according to the configuration of this bit. 7 TASNAPS R/W 0 GPTM Timer A Snap-Shot Mode Value Description 0 1 Snap-shot mode is disabled. If Timer A is configured in the periodic mode, the actual free-running value of Timer A is loaded at the time-out event into the GPTM Timer A (GPTMTAR) register. If the timer prescaler is used, the prescaler snapshot is loaded into the GPTM Timer A (GPTMTAPR).
April 25, 2012
Bit/Field 6
Name TAWOT
Type R/W
Reset 0
Description GPTM Timer A Wait-on-Trigger Value Description 0 1 Timer A begins counting as soon as it is enabled. If Timer A is enabled (TAEN is set in the GPTMCTL register), Timer A does not begin counting until it receives a trigger from the timer in the previous position in the daisy chain, see Figure 11-9 on page 701. This function is valid for one-shot, periodic, and PWM modes.
This bit must be clear for GP Timer Module 0, Timer A. 5 TAMIE R/W 0 GPTM Timer A Match Interrupt Enable Value Description 0 1 The match interrupt is disabled. An interrupt is generated when the match value in the GPTMTAMATCHR register is reached in the one-shot and periodic modes.
TACDIR
R/W
GPTM Timer A Count Direction Value Description 0 1 The timer counts down. The timer counts up. When counting up, the timer starts from a value of 0x0.
When in PWM or RTC mode, the status of this bit is ignored. PWM mode always counts down and RTC mode always counts up. 3 TAAMS R/W 0 GPTM Timer A Alternate Mode Select The TAAMS values are defined as follows: Value Description 0 1 Capture mode is enabled. PWM mode is enabled. Note: To enable PWM mode, you must also clear the TACMR bit and configure the TAMR field to 0x1 or 0x2.
TACMR
R/W
GPTM Timer A Capture Mode The TACMR values are defined as follows: Value Description 0 1 Edge-Count mode Edge-Time mode
713
Bit/Field 1:0
Name TAMR
Type R/W
Reset 0x0
Description GPTM Timer A Mode The TAMR values are defined as follows: Value Description 0x0 0x1 0x2 0x3 Reserved One-Shot Timer mode Periodic Timer mode Capture mode
The Timer mode is based on the timer configuration defined by bits 2:0 in the GPTMCFG register.
April 25, 2012
Register 3: GPTM Timer B Mode (GPTMTBMR), offset 0x008

This register configures the GPTM based on the configuration selected in the GPTMCFG register. When in PWM mode, set the TBAMS bit, clear the TBCMR bit, and configure the TBMR field to 0x1 or 0x2. This register controls the modes for Timer B when it is used individually. When Timer A and Timer B are concatenated, this register is ignored and GPTMTBMR controls the modes for both Timer A and Timer B. Important: Except for the TCACT bit field, all other bits in this register should only be changed when the TBEN bit in the GPTMCTL register is cleared.
GPTM Timer B Mode (GPTMTBMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TBPLO RO 0 R/W 0 RO 0 10 RO 0 9 RO 0 8 TBILD R/W 0 RO 0 7 RO 0 6 RO 0 5 TBMIE R/W 0 RO 0 4 TBCDIR R/W 0 RO 0 3 TBAMS R/W 0 RO 0 2 TBCMR R/W 0 R/W 0 RO 0 1 TBMR R/W 0 RO 0 0
TBMRSU TBPWMIE R/W 0 R/W 0
TBSNAPS TBWOT R/W 0 R/W 0
Bit/Field 31:12
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B PWM Legacy Operation Value Description 0 1 Legacy operation with CCP pin driven Low when the GPTMTAILR is reloaded after the timer reaches 0. CCP is driven High when the GPTMTAILR is reloaded after the timer reaches 0.
11
TBPLO
R/W
This bit is only valid in PWM mode.
715
Bit/Field 10
Name TBMRSU
Type R/W
Reset 0
Description GPTM Timer B Match Register Update Value Description 0 1 Update the GPTMTBMATCHR register and the GPTMTBPR register, if used, on the next cycle. Update the GPTMTBMATCHR register and the GPTMTBPR register, if used, on the next timeout.
If the timer is disabled (TBEN is clear) when this bit is set, GPTMTBMATCHR and GPTMTBPR are updated when the timer is enabled. If the timer is stalled (TBSTALL is set), GPTMTBMATCHR and GPTMTBPR are updated according to the configuration of this bit. 9 TBPWMIE R/W 0 GPTM Timer B PWM Interrupt Enable This bit enables interrupts in PWM mode on rising, falling, or both edges of the CCP output as defined by the TBEVENT field in the GPTMCTL register. Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
This bit is only valid in PWM mode. 8 TBILD R/W 0 GPTM Timer B Interval Load Write Value Description 0 Update the GPTMTBR and GPTMTBV registers with the value in the GPTMTBILR register on the next cycle. Also update the GPTMTBPS and GPTMTBPV registers with the value in the GPTMTBPR register on the next cycle. Update the GPTMTBR and GPTMTBV registers with the value in the GPTMTBILR register on the next timeout. Also update the GPTMTBPS and GPTMTBPV registers with the value in the GPTMTBPR register on the next timeout.
Note the state of this bit has no effect when counting up. The bit descriptions above apply if the timer is enabled and running. If the timer is disabled (TBEN is clear) when this bit is set, GPTMTBR, GPTMTBV, GPTMTBPS, and GPTMTBPV are updated when the timer is enabled. If the timer is stalled (TBSTALL is set), GPTMTBR and GPTMTBPS are updated according to the configuration of this bit. 7 TBSNAPS R/W 0 GPTM Timer B Snap-Shot Mode Value Description 0 1 Snap-shot mode is disabled. If Timer B is configured in the periodic mode, the actual free-running value of Timer B is loaded at the time-out event into the GPTM Timer B (GPTMTBR) register. If the timer prescaler is used, the prescaler snapshot is loaded into the GPTM Timer B (GPTMTBPR).
April 25, 2012
Bit/Field 6
Name TBWOT
Type R/W
Reset 0
Description GPTM Timer B Wait-on-Trigger Value Description 0 1 Timer B begins counting as soon as it is enabled. If Timer B is enabled (TBEN is set in the GPTMCTL register), Timer B does not begin counting until it receives an it receives a trigger from the timer in the previous position in the daisy chain, see Figure 11-9 on page 701. This function is valid for one-shot, periodic, and PWM modes.
TBMIE
R/W
GPTM Timer B Match Interrupt Enable Value Description 0 1 The match interrupt is disabled. An interrupt is generated when the match value in the GPTMTBMATCHR register is reached in the one-shot and periodic modes.
TBCDIR
R/W
GPTM Timer B Count Direction Value Description 0 1 The timer counts down. The timer counts up. When counting up, the timer starts from a value of 0x0.
When in PWM or RTC mode, the status of this bit is ignored. PWM mode always counts down and RTC mode always counts up. 3 TBAMS R/W 0 GPTM Timer B Alternate Mode Select The TBAMS values are defined as follows: Value Description 0 1 Capture mode is enabled. PWM mode is enabled. Note: To enable PWM mode, you must also clear the TBCMR bit and configure the TBMR field to 0x1 or 0x2.
TBCMR
R/W
GPTM Timer B Capture Mode The TBCMR values are defined as follows: Value Description 0 1 Edge-Count mode Edge-Time mode
717
Bit/Field 1:0
Name TBMR
Type R/W
Reset 0x0
Description GPTM Timer B Mode The TBMR values are defined as follows: Value Description 0x0 0x1 0x2 0x3 Reserved One-Shot Timer mode Periodic Timer mode Capture mode
The timer mode is based on the timer configuration defined by bits 2:0 in the GPTMCFG register.
April 25, 2012
Register 4: GPTM Control (GPTMCTL), offset 0x00C

This register is used alongside the GPTMCFG and GMTMTnMR registers to fine-tune the timer configuration, and to enable other features such as timer stall and the output trigger. The output trigger can be used to initiate transfers on the ADC module. Important: Bits in this register should only be changed when the TnEN bit for the respective timer is cleared.
GPTM Control (GPTMCTL)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x00C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

reserved
RO 0 14 TBPWML R/W 0
RO 0 13 TBOTE R/W 0
RO 0 12
reserved
RO 0 11
RO 0 10
RO 0 9 TBSTALL R/W 0
RO 0 8 TBEN R/W 0
RO 0 7
reserved
RO 0 6 TAPWML R/W 0
RO 0 5 TAOTE R/W 0
RO 0 4 RTCEN R/W 0
RO 0 3
RO 0 2
RO 0 1 TASTALL R/W 0
RO 0 0 TAEN R/W 0
TBEVENT R/W 0 R/W 0
TAEVENT R/W 0 R/W 0
Type Reset
RO 0
RO 0
RO 0
Bit/Field 31:15
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B PWM Output Level The TBPWML values are defined as follows: Value Description 0 1 Output is unaffected. Output is inverted.
14
TBPWML
R/W
13
TBOTE
R/W
GPTM Timer B Output Trigger Enable The TBOTE values are defined as follows: Value Description 0 1 The output Timer B ADC trigger is disabled. The output Timer B ADC trigger is enabled.
In addition, the ADC must be enabled and the timer selected as a trigger source with the EMn bit in the ADCEMUX register (see page 812).
719
Bit/Field 12
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Event Mode The TBEVENT values are defined as follows: Value Description 0x0 0x1 0x2 0x3 Note: Positive edge Negative edge Reserved Both edges If PWM output inversion is enabled, edge detection interrupt behavior is reversed. Thus, if a positive-edge interrupt trigger has been set and the PWM inversion generates a postive edge, no event-trigger interrupt asserts. Instead, the interrupt is generated on the negative edge of the PWM signal.
11:10
TBEVENT
R/W
0x0
TBSTALL
R/W
GPTM Timer B Stall Enable The TBSTALL values are defined as follows: Value Description 0 1 Timer B continues counting while the processor is halted by the debugger. Timer B freezes counting while the processor is halted by the debugger.
If the processor is executing normally, the TBSTALL bit is ignored. 8 TBEN R/W 0 GPTM Timer B Enable The TBEN values are defined as follows: Value Description 0 1 Timer B is disabled. Timer B is enabled and begins counting or the capture logic is enabled based on the GPTMCFG register.
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A PWM Output Level The TAPWML values are defined as follows: Value Description 0 1 Output is unaffected. Output is inverted.
TAPWML
R/W
April 25, 2012
Bit/Field 5
Name TAOTE
Type R/W
Reset 0
Description GPTM Timer A Output Trigger Enable The TAOTE values are defined as follows: Value Description 0 1 The output Timer A ADC trigger is disabled. The output Timer A ADC trigger is enabled.
In addition, the ADC must be enabled and the timer selected as a trigger source with the EMn bit in the ADCEMUX register (see page 812). 4 RTCEN R/W 0 GPTM RTC Stall Enable The RTCEN values are defined as follows: Value Description 0 1 RTC counting freezes while the processor is halted by the debugger. RTC counting continues while the processor is halted by the debugger.
If the RTCEN bit is set, it prevents the timer from stalling in all operating modes, even if TnSTALL is set. 3:2 TAEVENT R/W 0x0 GPTM Timer A Event Mode The TAEVENT values are defined as follows: Value Description 0x0 0x1 0x2 0x3 Note: Positive edge Negative edge Reserved Both edges If PWM output inversion is enabled, edge detection interrupt behavior is reversed. Thus, if a positive-edge interrupt trigger has been set and the PWM inversion generates a postive edge, no event-trigger interrupt asserts. Instead, the interrupt is generated on the negative edge of the PWM signal.
TASTALL
R/W
GPTM Timer A Stall Enable The TASTALL values are defined as follows: Value Description 0 1 Timer A continues counting while the processor is halted by the debugger. Timer A freezes counting while the processor is halted by the debugger.
If the processor is executing normally, the TASTALL bit is ignored.
721
Bit/Field 0
Name TAEN
Type R/W
Reset 0
Description GPTM Timer A Enable The TAEN values are defined as follows: Value Description 0 1 Timer A is disabled. Timer A is enabled and begins counting or the capture logic is enabled based on the GPTMCFG register.
April 25, 2012
Register 5: GPTM Synchronize (GPTMSYNC), offset 0x010

Note: This register is only implemented on GPTM Module 0 only. This register allows software to synchronize a number of timers.
GPTM Synchronize (GPTMSYNC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 SYNCT4 R/W 0 R/W 0 RO 0 8
SYNCWT5 R/W 0 7 SYNCT3 R/W 0 R/W 0 R/W 0 6
SYNCWT1 Type Reset R/W 0 R/W 0
SYNCWT0 R/W 0 R/W 0
SYNCT5 R/W 0 R/W 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Synchronize GPTM 32/64-Bit Timer 5 The SYNCWT5 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 32/64-Bit Timer 5 is not affected. A timeout event for Timer A of GPTM 32/64-Bit Timer 5 is triggered. A timeout event for Timer B of GPTM 32/64-Bit Timer 5 is triggered. A timeout event for both Timer A and Timer B of GPTM 32/64-Bit Timer 5 is triggered.
23:22
SYNCWT5
R/W
0x0
723
Bit/Field 21:20
Name SYNCWT4
Type R/W
Reset 0x0
Description Synchronize GPTM 32/64-Bit Timer 4 The SYNCWT4 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 32/64-Bit Timer 4 is not affected. A timeout event for Timer A of GPTM 32/64-Bit Timer 4 is triggered. A timeout event for Timer B of GPTM 32/64-Bit Timer 4 is triggered. A timeout event for both Timer A and Timer B of GPTM 32/64-Bit Timer 4 is triggered.
19:18
SYNCWT3
R/W
0x0
Synchronize GPTM 32/64-Bit Timer 3 The SYNCWT3 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 32/64-Bit Timer 3 is not affected. A timeout event for Timer A of GPTM 32/64-Bit Timer 3 is triggered. A timeout event for Timer B of GPTM 32/64-Bit Timer 3 is triggered. A timeout event for both Timer A and Timer B of GPTM 32/64-Bit Timer 3 is triggered.
17:16
SYNCWT2
R/W
0x0
15:14
SYNCWT1
R/W
0x0
April 25, 2012
Bit/Field 13:12
Name SYNCWT0
Type R/W
Reset 0x0
Description Synchronize GPTM 32/64-Bit Timer 0 The SYNCWT0 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 32/64-Bit Timer 0 is not affected. A timeout event for Timer A of GPTM 32/64-Bit Timer 0 is triggered. A timeout event for Timer B of GPTM 32/64-Bit Timer 0 is triggered. A timeout event for both Timer A and Timer B of GPTM 32/64-Bit Timer 0 is triggered.
11:10
SYNCT5
R/W
0x0
Synchronize GPTM 16/32-Bit Timer 5 The SYNCT5 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 16/32-Bit Timer 5 is not affected. A timeout event for Timer A of GPTM 16/32-Bit Timer 5 is triggered. A timeout event for Timer B of GPTM 16/32-Bit Timer 5 is triggered. A timeout event for both Timer A and Timer B of GPTM 16/32-Bit Timer 5 is triggered.
9:8
SYNCT4
R/W
0x0
7:6
SYNCT3
R/W
0x0
725
Bit/Field 5:4
Name SYNCT2
Type R/W
Reset 0x0
Description Synchronize GPTM 16/32-Bit Timer 2 The SYNCT2 values are defined as follows: Value Description 0x0 0x1 0x2 0x3 GPTM 16/32-Bit Timer 2 is not affected. A timeout event for Timer A of GPTM 16/32-Bit Timer 2 is triggered. A timeout event for Timer B of GPTM 16/32-Bit Timer 2 is triggered. A timeout event for both Timer A and Timer B of GPTM 16/32-Bit Timer 2 is triggered.
3:2
SYNCT1
R/W
0x0
1:0
SYNCT0
R/W
0x0
April 25, 2012
Register 6: GPTM Interrupt Mask (GPTMIMR), offset 0x018

This register allows software to enable/disable GPTM controller-level interrupts. Setting a bit enables the corresponding interrupt, while clearing a bit disables it.
GPTM Interrupt Mask (GPTMIMR)
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TBMIM RO 0 R/W 0 RO 0 10 CBEIM R/W 0 RO 0 9 CBMIM R/W 0 RO 0 8 TBTOIM R/W 0 RO 0 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 5 RO 0 4 TAMIM R/W 0 RO 0 3 RTCIM R/W 0 RO 0 2 CAEIM R/W 0 RO 0 1 CAMIM R/W 0 23 22 21 20 19 18 17 16 WUEIM R/W 0 0 TATOIM R/W 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide GPTM Write Update Error Interrupt Mask The WUEIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
16
WUEIM
R/W
15:12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Match Interrupt Mask The TBMIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
11
TBMIM
R/W
727
Bit/Field 10
Name CBEIM
Type R/W
Reset 0
Description GPTM Timer B Capture Mode Event Interrupt Mask The CBEIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
CBMIM
R/W
GPTM Timer B Capture Mode Match Interrupt Mask The CBMIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
TBTOIM
R/W
GPTM Timer B Time-Out Interrupt Mask The TBTOIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
7:5
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Match Interrupt Mask The TAMIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
TAMIM
R/W
RTCIM
R/W
GPTM RTC Interrupt Mask The RTCIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
CAEIM
R/W
GPTM Timer A Capture Mode Event Interrupt Mask The CAEIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
April 25, 2012
Bit/Field 1
Name CAMIM
Type R/W
Reset 0
Description GPTM Timer A Capture Mode Match Interrupt Mask The CAMIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
TATOIM
R/W
GPTM Timer A Time-Out Interrupt Mask The TATOIM values are defined as follows: Value Description 0 1 Interrupt is disabled. Interrupt is enabled.
729
Register 7: GPTM Raw Interrupt Status (GPTMRIS), offset 0x01C

This register shows the state of the GPTM's internal interrupt signal. These bits are set whether or not the interrupt is masked in the GPTMIMR register. Each bit can be cleared by writing a 1 to its corresponding bit in GPTMICR.
GPTM Raw Interrupt Status (GPTMRIS)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x01C Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TBMRIS RO 0 RO 0 RO 0 10 CBERIS RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 5 RO 0 4 TAMRIS RO 0 RO 0 3 RTCRIS RO 0 RO 0 2 CAERIS RO 0 RO 0 1 23 22 21 20 19 18 17 16 WUERIS R/W 0 0
CBMRIS TBTORIS RO 0 RO 0
CAMRIS TATORIS RO 0 RO 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide GPTM Write Update Error Raw Interrupt Status Value Description 1 Either a Timer A register or a Timer B register was written twice in a row or a Timer A register was written before the corresponding Timer B register was written. No error.
16
WUERIS
R/W
15:12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Match Raw Interrupt Value Description 1 The TBMIE bit is set in the GPTMTBMR register, and the match values in the GPTMTBMATCHR and (optionally) GPTMTBPMR registers have been reached when configured in one-shot or periodic mode. The match value has not been reached.
11
TBMRIS
RO
This bit is cleared by writing a 1 to the TBMCINT bit in the GPTMICR register.
April 25, 2012
Bit/Field 10
Name CBERIS
Type RO
Reset 0
Description GPTM Timer B Capture Mode Event Raw Interrupt Value Description 1 A capture mode event has occurred for Timer B. This interrupt asserts when the subtimer is configured in Input Edge-Time mode or when configured in PWM mode with the PWM interrupt enabled by setting the TBPWMIE bit in the GPTMTBMR. The capture mode event for Timer B has not occurred.
This bit is cleared by writing a 1 to the CBECINT bit in the GPTMICR register. 9 CBMRIS RO 0 GPTM Timer B Capture Mode Match Raw Interrupt Value Description 1 The capture mode match has occurred for Timer B. This interrupt asserts when the values in the GPTMTBR and GPTMTBPR match the values in the GPTMTBMATCHR and GPTMTBPMR when configured in Input Edge-Time mode. The capture mode match for Timer B has not occurred.
This bit is cleared by writing a 1 to the CBMCINT bit in the GPTMICR register. 8 TBTORIS RO 0 GPTM Timer B Time-Out Raw Interrupt Value Description 1 Timer B has timed out. This interrupt is asserted when a one-shot or periodic mode timer reaches it's count limit (0 or the value loaded into GPTMTBILR, depending on the count direction). Timer B has not timed out.
This bit is cleared by writing a 1 to the TBTOCINT bit in the GPTMICR register. 7:5 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Match Raw Interrupt Value Description 1 The TAMIE bit is set in the GPTMTAMR register, and the match value in the GPTMTAMATCHR and (optionally) GPTMTAPMR registers have been reached when configured in one-shot or periodic mode. The match value has not been reached.
TAMRIS
RO
This bit is cleared by writing a 1 to the TAMCINT bit in the GPTMICR register.
731
Bit/Field 3
Name RTCRIS
Type RO
Reset 0
Description GPTM RTC Raw Interrupt Value Description 1 0 The RTC event has occurred. The RTC event has not occurred.
This bit is cleared by writing a 1 to the RTCCINT bit in the GPTMICR register. 2 CAERIS RO 0 GPTM Timer A Capture Mode Event Raw Interrupt Value Description 1 A capture mode event has occurred for Timer A. This interrupt asserts when the subtimer is configured in Input Edge-Time mode or when configured in PWM mode with the PWM interrupt enabled by setting the TAPWMIE bit in the GPTMTAMR. The capture mode event for Timer A has not occurred.
This bit is cleared by writing a 1 to the CAECINT bit in the GPTMICR register. 1 CAMRIS RO 0 GPTM Timer A Capture Mode Match Raw Interrupt Value Description 1 A capture mode match has occurred for Timer A. This interrupt asserts when the values in the GPTMTAR and GPTMTAPR match the values in the GPTMTAMATCHR and GPTMTAPMR when configured in Input Edge-Time mode. The capture mode match for Timer A has not occurred.
This bit is cleared by writing a 1 to the CAMCINT bit in the GPTMICR register. 0 TATORIS RO 0 GPTM Timer A Time-Out Raw Interrupt Value Description 1 Timer A has timed out. This interrupt is asserted when a one-shot or periodic mode timer reaches it's count limit (0 or the value loaded into GPTMTAILR, depending on the count direction). Timer A has not timed out.
This bit is cleared by writing a 1 to the TATOCINT bit in the GPTMICR register.
April 25, 2012
Register 8: GPTM Masked Interrupt Status (GPTMMIS), offset 0x020

This register show the state of the GPTM's controller-level interrupt. If an interrupt is unmasked in GPTMIMR, and there is an event that causes the interrupt to be asserted, the corresponding bit is set in this register. All bits are cleared by writing a 1 to the corresponding bit in GPTMICR.
GPTM Masked Interrupt Status (GPTMMIS)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x020 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TBMMIS RO 0 RO 0 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 5 RO 0 4 TAMMIS RO 0 RO 0 3 RTCMIS RO 0 RO 0 2 RO 0 1 23 22 21 20 19 18 17 16 WUEMIS RO 0 0
CBEMIS CBMMIS TBTOMIS RO 0 RO 0 RO 0
CAEMIS CAMMIS TATOMIS RO 0 RO 0 RO 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide GPTM Write Update Error Masked Interrupt Status Value Description 1 0 An unmasked Write Update Error has occurred. An unmasked Write Update Error has not occurred.
16
WUEMIS
RO
15:12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Match Masked Interrupt Value Description 1 0 An unmasked Timer B Mode Match interrupt has occurred. A Timer B Mode Match interrupt has not occurred or is masked.
11
TBMMIS
RO
This bit is cleared by writing a 1 to the TBMCINT bit in the GPTMICR register.
733
Bit/Field 10
Name CBEMIS
Type RO
Reset 0
Description GPTM Timer B Capture Mode Event Masked Interrupt Value Description 1 0 An unmasked Capture B event interrupt has occurred. A Capture B event interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the CBECINT bit in the GPTMICR register. 9 CBMMIS RO 0 GPTM Timer B Capture Mode Match Masked Interrupt Value Description 1 0 An unmasked Capture B Match interrupt has occurred. A Capture B Mode Match interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the CBMCINT bit in the GPTMICR register. 8 TBTOMIS RO 0 GPTM Timer B Time-Out Masked Interrupt Value Description 1 0 An unmasked Timer B Time-Out interrupt has occurred. A Timer B Time-Out interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the TBTOCINT bit in the GPTMICR register. 7:5 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Match Masked Interrupt Value Description 1 0 An unmasked Timer A Mode Match interrupt has occurred. A Timer A Mode Match interrupt has not occurred or is masked.
TAMMIS
RO
This bit is cleared by writing a 1 to the TAMCINT bit in the GPTMICR register. 3 RTCMIS RO 0 GPTM RTC Masked Interrupt Value Description 1 0 An unmasked RTC event interrupt has occurred. An RTC event interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the RTCCINT bit in the GPTMICR register.
April 25, 2012
Bit/Field 2
Name CAEMIS
Type RO
Reset 0
Description GPTM Timer A Capture Mode Event Masked Interrupt Value Description 1 0 An unmasked Capture A event interrupt has occurred. A Capture A event interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the CAECINT bit in the GPTMICR register. 1 CAMMIS RO 0 GPTM Timer A Capture Mode Match Masked Interrupt Value Description 1 0 An unmasked Capture A Match interrupt has occurred. A Capture A Mode Match interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the CAMCINT bit in the GPTMICR register. 0 TATOMIS RO 0 GPTM Timer A Time-Out Masked Interrupt Value Description 1 0 An unmasked Timer A Time-Out interrupt has occurred. A Timer A Time-Out interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the TATOCINT bit in the GPTMICR register.
735
Register 9: GPTM Interrupt Clear (GPTMICR), offset 0x024

This register is used to clear the status bits in the GPTMRIS and GPTMMIS registers. Writing a 1 to a bit clears the corresponding bit in the GPTMRIS and GPTMMIS registers.
GPTM Interrupt Clear (GPTMICR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x024 Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 23 22 21 20 19 18 17 16 WUECINT R/W 0 0
TBMCINT CBECINT CBMCINT TBTOCINT W1C 0 W1C 0 W1C 0 W1C 0
TAMCINT RTCCINT CAECINT CAMCINT TATOCINT W1C 0 W1C 0 W1C 0 W1C 0 W1C 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 32/64-Bit Wide GPTM Write Update Error Interrupt Clear Writing a 1 to this bit clears the WUERIS bit in the GPTMRIS register and the WUEMIS bit in the GPTMMIS register.
16
WUECINT
R/W
15:12
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Match Interrupt Clear Writing a 1 to this bit clears the TBMRIS bit in the GPTMRIS register and the TBMMIS bit in the GPTMMIS register.
11
TBMCINT
W1C
10
CBECINT
W1C
GPTM Timer B Capture Mode Event Interrupt Clear Writing a 1 to this bit clears the CBERIS bit in the GPTMRIS register and the CBEMIS bit in the GPTMMIS register.
CBMCINT
W1C
GPTM Timer B Capture Mode Match Interrupt Clear Writing a 1 to this bit clears the CBMRIS bit in the GPTMRIS register and the CBMMIS bit in the GPTMMIS register.
TBTOCINT
W1C
GPTM Timer B Time-Out Interrupt Clear Writing a 1 to this bit clears the TBTORIS bit in the GPTMRIS register and the TBTOMIS bit in the GPTMMIS register.
April 25, 2012
Bit/Field 7:5
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Match Interrupt Clear Writing a 1 to this bit clears the TAMRIS bit in the GPTMRIS register and the TAMMIS bit in the GPTMMIS register.
TAMCINT
W1C
RTCCINT
W1C
GPTM RTC Interrupt Clear Writing a 1 to this bit clears the RTCRIS bit in the GPTMRIS register and the RTCMIS bit in the GPTMMIS register.
CAECINT
W1C
GPTM Timer A Capture Mode Event Interrupt Clear Writing a 1 to this bit clears the CAERIS bit in the GPTMRIS register and the CAEMIS bit in the GPTMMIS register.
CAMCINT
W1C
GPTM Timer A Capture Mode Match Interrupt Clear Writing a 1 to this bit clears the CAMRIS bit in the GPTMRIS register and the CAMMIS bit in the GPTMMIS register.
TATOCINT
W1C
GPTM Timer A Time-Out Raw Interrupt Writing a 1 to this bit clears the TATORIS bit in the GPTMRIS register and the TATOMIS bit in the GPTMMIS register.
737
Register 10: GPTM Timer A Interval Load (GPTMTAILR), offset 0x028

When the timer is counting down, this register is used to load the starting count value into the timer. When the timer is counting up, this register sets the upper bound for the timeout event. When a 16/32-bit GPTM is configured to one of the 32-bit modes, GPTMTAILR appears as a 32-bit register (the upper 16-bits correspond to the contents of the GPTM Timer B Interval Load (GPTMTBILR) register). In a 16-bit mode, the upper 16 bits of this register read as 0s and have no effect on the state of GPTMTBILR. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAILR contains bits 31:0 of the 64-bit count and the GPTM Timer B Interval Load (GPTMTBILR) register contains bits 63:32.
GPTM Timer A Interval Load (GPTMTAILR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x028 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 TAILR Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 TAILR Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TAILR
Type R/W
Reset
Description
0xFFFF.FFFF GPTM Timer A Interval Load Register Writing this field loads the counter for Timer A. A read returns the current value of GPTMTAILR.
April 25, 2012
Register 11: GPTM Timer B Interval Load (GPTMTBILR), offset 0x02C

When the timer is counting down, this register is used to load the starting count value into the timer. When the timer is counting up, this register sets the upper bound for the timeout event. When a 16/32-bit GPTM is configured to one of the 32-bit modes, the contents of bits 15:0 in this register are loaded into the upper 16 bits of the GPTMTAILR register. Reads from this register return the current value of Timer B and writes are ignored. In a 16-bit mode, bits 15:0 are used for the load value. Bits 31:16 are reserved in both cases. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAILR contains bits 31:0 of the 64-bit count and the GPTMTBILR register contains bits 63:32.
GPTM Timer B Interval Load (GPTMTBILR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x02C Type R/W, reset 31 30 29 28 27 26 25 24 TBILR Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 TBILR Type Reset R/W 0 R/W 0 R/W 1 R/W 0 R/W 0 R/W 1 R/W 1 R/W 0 R/W 0 R/W 1 R/W 0 R/W 0 R/W 1 R/W 0 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 0 3 R/W 0 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TBILR
Type R/W
Reset
Description
0x0000.FFFF GPTM Timer B Interval Load Register (for 16/32-bit) Writing this field loads the counter for Timer B. A read returns the current 0xFFFF.FFFF value of GPTMTBILR. (for 32/64-bit) When a 16/32-bit GPTM is in 32-bit mode, writes are ignored, and reads return the current value of GPTMTBILR.
739
Register 12: GPTM Timer A Match (GPTMTAMATCHR), offset 0x030

This register is loaded with a match value. Interrupts can be generated when the timer value is equal to the value in this register in one-shot or periodic mode. In Edge-Count mode, this register along with GPTMTAILR, determines how many edge events are counted. The total number of edge events counted is equal to the value in GPTMTAILR minus this value. In PWM mode, this value along with GPTMTAILR, determines the duty cycle of the output PWM signal. When a 16/32-bit GPTM is configured to one of the 32-bit modes, GPTMTAMATCHR appears as a 32-bit register (the upper 16-bits correspond to the contents of the GPTM Timer B Match (GPTMTBMATCHR) register). In a 16-bit mode, the upper 16 bits of this register read as 0s and have no effect on the state of GPTMTBMATCHR. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAMATCHR contains bits 31:0 of the 64-bit match value and the GPTM Timer B Match (GPTMTBMATCHR) register contains bits 63:32.
GPTM Timer A Match (GPTMTAMATCHR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x030 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 TAMR Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 TAMR Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TAMR
Type R/W
Reset
Description
0xFFFF.FFFF GPTM Timer A Match Register This value is compared to the GPTMTAR register to determine match events.
April 25, 2012
Register 13: GPTM Timer B Match (GPTMTBMATCHR), offset 0x034

This register is loaded with a match value. Interrupts can be generated when the timer value is equal to the value in this register in one-shot or periodic mode. In Edge-Count mode, this register along with GPTMTBILR, determines how many edge events are counted. The total number of edge events counted is equal to the value in GPTMTBILR minus this value. In PWM mode, this value along with GPTMTBILR, determines the duty cycle of the output PWM signal. When a 16/32-bit GPTM is configured to one of the 32-bit modes, the contents of bits 15:0 in this register are loaded into the upper 16 bits of the GPTMTAMATCHR register. Reads from this register return the current match value of Timer B and writes are ignored. In a 16-bit mode, bits 15:0 are used for the match value. Bits 31:16 are reserved in both cases. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAMATCHR contains bits 31:0 of the 64-bit match value and the GPTMTBMATCHR register contains bits 63:32.
GPTM Timer B Match (GPTMTBMATCHR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x034 Type R/W, reset 31 30 29 28 27 26 25 24 TBMR Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 TBMR Type Reset R/W 0 R/W 0 R/W 1 R/W 0 R/W 0 R/W 1 R/W 1 R/W 0 R/W 0 R/W 1 R/W 0 R/W 0 R/W 1 R/W 0 R/W 1 R/W 1 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 0 3 R/W 0 2 R/W 1 1 R/W 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TBMR
Type R/W
Reset
Description
0x0000.FFFF GPTM Timer B Match Register (for 16/32-bit) This value is compared to the GPTMTBR register to determine match 0xFFFF.FFFF events. (for 32/64-bit)
741
Register 14: GPTM Timer A Prescale (GPTMTAPR), offset 0x038

This register allows software to extend the range of the timers when they are used individually. When in one-shot or periodic down count modes, this register acts as a true prescaler for the timer counter. When acting as a true prescaler, the prescaler counts down to 0 before the value in the GPTMTAR and GPTMTAV registers are incremented. In all other individual/split modes, this register is a linear extension of the upper range of the timer counter, holding bits 23:16 in the 16-bit modes of the 16/32-bit GPTM and bits 47:32 in the 32-bit modes of the 32/64-bit Wide GPTM.
GPTM Timer A Prescale (GPTMTAPR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 TAPSR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
TAPSRH Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Prescale High Byte The register loads this value on a write. A read returns the current value of the register. For the 16/32-bit GPTM, this field is reserved. For the 32/64-bit Wide GPTM, this field contains the upper 8-bits of the 16-bit prescaler. Refer to Table 11-5 on page 692 for more details and an example.
15:8
TAPSRH
R/W
0x00
7:0
TAPSR
R/W
0x00
GPTM Timer A Prescale The register loads this value on a write. A read returns the current value of the register. For the 16/32-bit GPTM, this field contains the entire 8-bit prescaler. For the 32/64-bit Wide GPTM, this field contains the lower 8-bits of the 16-bit prescaler. Refer to Table 11-5 on page 692 for more details and an example.
April 25, 2012
Register 15: GPTM Timer B Prescale (GPTMTBPR), offset 0x03C

This register allows software to extend the range of the timers when they are used individually. When in one-shot or periodic down count modes, this register acts as a true prescaler for the timer counter. When acting as a true prescaler, the prescaler counts down to 0 before the value in the GPTMTBR and GPTMTBV registers are incremented. In all other individual/split modes, this register is a linear extension of the upper range of the timer counter, holding bits 23:16 in the 16-bit modes of the 16/32-bit GPTM and bits 47:32 in the 32-bit modes of the 32/64-bit Wide GPTM.
GPTM Timer B Prescale (GPTMTBPR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x03C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 TBPSR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
TBPSRH Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Prescale High Byte The register loads this value on a write. A read returns the current value of the register. For the 16/32-bit GPTM, this field is reserved. For the 32/64-bit Wide GPTM, this field contains the upper 8-bits of the 16-bit prescaler. Refer to Table 11-5 on page 692 for more details and an example.
15:8
TBPSRH
R/W
0x00
7:0
TBPSR
R/W
0x00
GPTM Timer B Prescale The register loads this value on a write. A read returns the current value of this register. For the 16/32-bit GPTM, this field contains the entire 8-bit prescaler. For the 32/64-bit Wide GPTM, this field contains the lower 8-bits of the 16-bit prescaler. Refer to Table 11-5 on page 692 for more details and an example.
743
Register 16: GPTM TimerA Prescale Match (GPTMTAPMR), offset 0x040

This register allows software to extend the range of the GPTMTAMATCHR when the timers are used individually. This register holds bits 23:16 in the 16-bit modes of the 16/32-bit GPTM and bits 47:32 in the 32-bit modes of the 32/64-bit Wide GPTM.
GPTM TimerA Prescale Match (GPTMTAPMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 TAPSMR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
TAPSMRH Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Prescale Match High Byte This value is used alongside GPTMTAMATCHR to detect timer match events while using a prescaler. For the 16/32-bit GPTM, this field is reserved. For the 32/64-bit Wide GPTM, this field contains the upper 8-bits of the 16-bit prescale match value.
15:8
TAPSMRH
R/W
0x00
7:0
TAPSMR
R/W
0x00
GPTM TimerA Prescale Match This value is used alongside GPTMTAMATCHR to detect timer match events while using a prescaler. For the 16/32-bit GPTM, this field contains the entire 8-bit prescaler match value. For the 32/64-bit Wide GPTM, this field contains the lower 8-bits of the 16-bit prescaler match value.
April 25, 2012
Register 17: GPTM TimerB Prescale Match (GPTMTBPMR), offset 0x044

This register allows software to extend the range of the GPTMTBMATCHR when the timers are used individually. This register holds bits 23:16 in the 16-bit modes of the 16/32-bit GPTM and bits 47:32 in the 32-bit modes of the 32/64-bit Wide GPTM.
GPTM TimerB Prescale Match (GPTMTBPMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 TBPSMR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
TBPSMRH Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Prescale Match High Byte This value is used alongside GPTMTBMATCHR to detect timer match events while using a prescaler. For the 16/32-bit GPTM, this field is reserved. For the 32/64-bit Wide GPTM, this field contains the upper 8-bits of the 16-bit prescale match value.
15:8
TBPSMRH
R/W
0x00
7:0
TBPSMR
R/W
0x00
GPTM TimerB Prescale Match This value is used alongside GPTMTBMATCHR to detect timer match events while using a prescaler. For the 16/32-bit GPTM, this field contains the entire 8-bit prescaler match value. For the 32/64-bit Wide GPTM, this field contains the lower 8-bits of the 16-bit prescaler match value.
745
Register 18: GPTM Timer A (GPTMTAR), offset 0x048

This register shows the current value of the Timer A counter in all cases except for Input Edge Count and Time modes. In the Input Edge Count mode, this register contains the number of edges that have occurred. In the Input Edge Time mode, this register contains the time at which the last edge event took place. When a 16/32-bit GPTM is configured to one of the 32-bit modes, GPTMTAR appears as a 32-bit register (the upper 16-bits correspond to the contents of the GPTM Timer B (GPTMTBR) register). In the16-bit Input Edge Count, Input Edge Time, and PWM modes, bits 15:0 contain the value of the counter and bits 23:16 contain the value of the prescaler, which is the upper 8 bits of the count. Bits 31:24 always read as 0. To read the value of the prescaler in 16-bit One-Shot and Periodic modes, read bits [23:16] in the GPTMTAV register. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAR contains bits 31:0 of the 64-bit timer value and the GPTM Timer B (GPTMTBR) register contains bits 63:32. In a 32-bit mode, the value of the prescaler is stored in the GPTM Timer A Prescale Snapshot (GPTMTAPS) register.
GPTM Timer A (GPTMTAR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x048 Type RO, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 TAR Type Reset RO 1 15 RO 1 14 RO 1 13 RO 1 12 RO 1 11 RO 1 10 RO 1 9 RO 1 8 TAR Type Reset RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TAR
Type RO
Reset
Description
0xFFFF.FFFF GPTM Timer A Register A read returns the current value of the GPTM Timer A Count Register, in all cases except for Input Edge Count and Time modes. In the Input Edge Count mode, this register contains the number of edges that have occurred. In the Input Edge Time mode, this register contains the time at which the last edge event took place.
April 25, 2012
Register 19: GPTM Timer B (GPTMTBR), offset 0x04C

This register shows the current value of the Timer B counter in all cases except for Input Edge Count and Time modes. In the Input Edge Count mode, this register contains the number of edges that have occurred. In the Input Edge Time mode, this register contains the time at which the last edge event took place. When a 16/32-bit GPTM is configured to one of the 32-bit modes, the contents of bits 15:0 in this register are loaded into the upper 16 bits of the GPTMTAR register. Reads from this register return the current value of Timer B. In a 16-bit mode, bits 15:0 contain the value of the counter and bits 23:16 contain the value of the prescaler in Input Edge Count, Input Edge Time, and PWM modes, which is the upper 8 bits of the count. Bits 31:24 always read as 0. To read the value of the prescaler in 16-bit One-Shot and Periodic modes, read bits [23:16] in the GPTMTBV register. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAR contains bits 31:0 of the 64-bit timer value and the GPTM Timer B (GPTMTBR) register contains bits 63:32. In a 32-bit mode, the value of the prescaler is stored in the GPTM Timer B Prescale Snapshot (GPTMTBPS) register.
GPTM Timer B (GPTMTBR)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x04C Type RO, reset 31 30 29 28 27 26 25 24 TBR Type Reset RO 1 15 RO 1 14 RO 1 13 RO 1 12 RO 1 11 RO 1 10 RO 1 9 RO 1 8 TBR Type Reset RO 0 RO 0 RO 1 RO 0 RO 0 RO 1 RO 1 RO 0 RO 0 RO 1 RO 0 RO 0 RO 1 RO 0 RO 1 RO 1 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 0 3 RO 0 2 RO 1 1 RO 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TBR
Type RO
Reset 0x0000.FFFF (for 16/32-bit) 0xFFFF.FFFF (for 32/64-bit)
Description GPTM Timer B Register A read returns the current value of the GPTM Timer B Count Register, in all cases except for Input Edge Count and Time modes. In the Input Edge Count mode, this register contains the number of edges that have occurred. In the Input Edge Time mode, this register contains the time at which the last edge event took place.
747
Register 20: GPTM Timer A Value (GPTMTAV), offset 0x050

When read, this register shows the current, free-running value of Timer A in all modes. Software can use this value to determine the time elapsed between an interrupt and the ISR entry when using the snapshot feature with the periodic operating mode. When written, the value written into this register is loaded into the GPTMTAR register on the next clock cycle. When a 16/32-bit GPTM is configured to one of the 32-bit modes, GPTMTAV appears as a 32-bit register (the upper 16-bits correspond to the contents of the GPTM Timer B Value (GPTMTBV) register). In a 16-bit mode, bits 15:0 contain the value of the counter and bits 23:16 contain the current, free-running value of the prescaler, which is the upper 8 bits of the count in Input Edge Count, Input Edge Time, PWM and one-shot or periodic up count modes. In one-shot or periodic down count modes, the prescaler stored in 23:16 is a true prescaler, meaning bits 23:16 count down before decrementing the value in bits 15:0. The prescaler in bits 31:24 always reads as 0. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTAV contains bits 31:0 of the 64-bit timer value and the GPTM Timer B Value (GPTMTBV) register contains bits 63:32. In a 32-bit mode, the current, free-running value of the prescaler is stored in the GPTM Timer A Prescale Value (GPTMTAPV) register.mint
GPTM Timer A Value (GPTMTAV)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x050 Type RW, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 TAV Type Reset RW 1 15 RW 1 14 RW 1 13 RW 1 12 RW 1 11 RW 1 10 RW 1 9 RW 1 8 TAV Type Reset RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 RW 1 7 RW 1 6 RW 1 5 RW 1 4 RW 1 3 RW 1 2 RW 1 1 RW 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TAV
Type RW
Reset
Description
0xFFFF.FFFF GPTM Timer A Value A read returns the current, free-running value of Timer A in all modes. When written, the value written into this register is loaded into the GPTMTAR register on the next clock cycle.
April 25, 2012
Register 21: GPTM Timer B Value (GPTMTBV), offset 0x054

When read, this register shows the current, free-running value of Timer B in all modes. Software can use this value to determine the time elapsed between an interrupt and the ISR entry. When written, the value written into this register is loaded into the GPTMTBR register on the next clock cycle. When a 16/32-bit GPTM is configured to one of the 32-bit modes, the contents of bits 15:0 in this register are loaded into the upper 16 bits of the GPTMTAV register. Reads from this register return the current free-running value of Timer B. In a 16-bit mode, bits 15:0 contain the value of the counter and bits 23:16 contain the current, free-running value of the prescaler, which is the upper 8 bits of the count in Input Edge Count, Input Edge Time, PWM and one-shot or periodic up count modes. In one-shot or periodic down count modes, the prescaler stored in 23:16 is a true prescaler, meaning bits 23:16 count down before decrementing the value in bits 15:0. The prescaler in bits 31:24 always reads as 0. When a 32/64-bit Wide GPTM is configured to one of the 64-bit modes, GPTMTBV contains bits 63:32 of the 64-bit timer value and the GPTM Timer A Value (GPTMTAV) register contains bits 31:0. In a 32-bit mode, the current, free-running value of the prescaler is stored in the GPTM Timer B Prescale Value (GPTMTBPV) register.
GPTM Timer B Value (GPTMTBV)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x054 Type RW, reset 31 30 29 28 27 26 25 24 TBV Type Reset RW 1 15 RW 1 14 RW 1 13 RW 1 12 RW 1 11 RW 1 10 RW 1 9 RW 1 8 TBV Type Reset RW 0 RW 0 RW 1 RW 0 RW 0 RW 1 RW 1 RW 0 RW 0 RW 1 RW 0 RW 0 RW 1 RW 0 RW 1 RW 1 RW 1 7 RW 1 6 RW 1 5 RW 1 4 RW 0 3 RW 0 2 RW 1 1 RW 1 0 23 22 21 20 19 18 17 16
Bit/Field 31:0
Name TBV
Type RW
Reset 0x0000.FFFF (for 16/32-bit) 0xFFFF.FFFF (for 32/64-bit)
Description GPTM Timer B Value A read returns the current, free-running value of Timer A in all modes. When written, the value written into this register is loaded into the GPTMTAR register on the next clock cycle.
749
Register 22: GPTM RTC Predivide (GPTMRTCPD), offset 0x058

This register provides the current RTC predivider value when the timer is operating in RTC mode. Software must perform an atomic access with consecutive reads of the GPTMTAR, GPTMTBR, and GPTMRTCPD registers, see Figure 11-2 on page 694 for more information.
GPTM RTC Predivide (GPTMRTCPD)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x058 Type RO, reset 0x0000.7FFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RTCPD Type Reset RO 0 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
15:0
RTCPD
RO
0x0000.7FFF RTC Predivide Counter Value The current RTC predivider value when the timer is operating in RTC mode. This field has no meaning in other timer modes.
April 25, 2012
Register 23: GPTM Timer A Prescale Snapshot (GPTMTAPS), offset 0x05C

This register shows the current value of the Timer A pre-scaler in the 16-bit modes. For the 32/64-bit Wide GPTM, this register shows the current value of the Timer A prescaler in the 32-bit modes. This register is ununsed in 16/32-bit GPTM mode.
GPTM Timer A Prescale Snapshot (GPTMTAPS)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0x05C Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 PSS Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Prescaler Snapshot A read returns the current value of the GPTM Timer A Prescaler.
15:0
PSS
RO
0x0000
751
Register 24: GPTM Timer B Prescale Snapshot (GPTMTBPS), offset 0x060

This register shows the current value of the Timer B pre-scaler in the 16-bit modes. For the 32/64-bit Wide GPTM, this register shows the current value of the Timer B prescaler in the 32-bit modes. This register is ununsed in 16/32-bit GPTM mode.
GPTM Timer B Prescale Snapshot (GPTMTBPS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 PSS Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Prescaler Value A read returns the current value of the GPTM Timer A Prescaler.
15:0
PSS
RO
0x0000
April 25, 2012
Register 25: GPTM Timer A Prescale Value (GPTMTAPV), offset 0x064

This register shows the current value of the Timer A free running pre-scaler in the 16-bit modes. For the 32/64-bit Wide GPTM, this register shows the current free-running value of the Timer A prescaler in the 32-bit modes. Software can use this value in conjunction with the GPTMTAV register to determine the time elapsed between an interrupt and the ISR entry. This register is ununsed in 16/32-bit GPTM mode.
GPTM Timer A Prescale Value (GPTMTAPV)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 PSV Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer A Prescaler Value A read returns the current, free-running value of the Timer A prescaler.
15:0
PSV
RO
0x0000
753
Register 26: GPTM Timer B Prescale Value (GPTMTBPV), offset 0x068

This register shows the current value of the Timer B free running pre-scaler in the 16-bit modes. For the 32/64-bit Wide GPTM, this register shows the current free-running value of the Timer B prescaler in the 32-bit modes. Software can use this value in conjunction with the GPTMTBV register to determine the time elapsed between an interrupt and the ISR entry. This register is ununsed in 16/32-bit GPTM mode.
GPTM Timer B Prescale Value (GPTMTBPV)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 PSV Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. GPTM Timer B Prescaler Value A read returns the current, free-running value of the Timer A prescaler.
15:0
PSV
RO
0x0000
April 25, 2012
Register 27: GPTM Peripheral Properties (GPTMPP), offset 0xFC0

The GPTMPP register provides information regarding the properties of the General-Purpose Timer module.
GPTM Peripheral Properties (GPTMPP)
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000 Offset 0xFC0 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 SIZE RO 0 RO 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Count Size Value Description 1 0 Timer A and Timer B counters are 32 bits each with a 16-bit prescale counter. Timer A and Timer B counters are 16 bits each with an 8-bit prescale counter.
3:0
SIZE
RO
0x0
755
Watchdog Timers
12
Watchdog Timers
A watchdog timer can generate a non-maskable interrupt (NMI), a regular interrupt or a reset when a time-out value is reached. The watchdog timer is used to regain control when a system has failed due to a software error or due to the failure of an external device to respond in the expected way. The LM4F120H5QR microcontroller has two Watchdog Timer Modules, one module is clocked by the system clock (Watchdog Timer 0) and the other is clocked by the PIOSC (Watchdog Timer 1). The two modules are identical except that WDT1 is in a different clock domain, and therefore requires synchronizers. As a result, WDT1 has a bit defined in the Watchdog Timer Control (WDTCTL) register to indicate when a write to a WDT1 register is complete. Software can use this bit to ensure that the previous access has completed before starting the next access. The Stellaris LM4F120H5QR controller has two Watchdog Timer modules with the following features: 32-bit down counter with a programmable load register Separate watchdog clock with an enable Programmable interrupt generation logic with interrupt masking and optional NMI function Lock register protection from runaway software Reset generation logic with an enable/disable User-enabled stalling when the microcontroller asserts the CPU Halt flag during debug The Watchdog Timer can be configured to generate an interrupt to the controller on its first time-out, and to generate a reset signal on its second time-out. Once the Watchdog Timer has been configured, the lock register can be written to prevent the timer configuration from being inadvertently altered.
April 25, 2012
12.1
Block Diagram
Figure 12-1. WDT Module Block Diagram
Control / Clock / Interrupt Generation WDTCTL WDTICR Interrupt/NMI WDTRIS WDTMIS WDTLOCK System Clock/ PIOSC WDTTEST Comparator WDTVALUE 32-Bit Down Counter 0x0000.0000 WDTLOAD
Identification Registers WDTPCellID0 WDTPCellID1 WDTPCellID2 WDTPCellID3 WDTPeriphID0 WDTPeriphID1 WDTPeriphID2 WDTPeriphID3 WDTPeriphID4 WDTPeriphID5 WDTPeriphID6 WDTPeriphID7
12.2
The Watchdog Timer module generates the first time-out signal when the 32-bit counter reaches the zero state after being enabled; enabling the counter also enables the watchdog timer interrupt. The watchdog interrupt can be programmed to be an non-maskable interrupt (NMI) using the INTTYPE bit in the WDTCTL register. After the first time-out event, the 32-bit counter is re-loaded with the value of the Watchdog Timer Load (WDTLOAD) register, and the timer resumes counting down from that value. Once the Watchdog Timer has been configured, the Watchdog Timer Lock (WDTLOCK) register is written, which prevents the timer configuration from being inadvertently altered by software. If the timer counts down to its zero state again before the first time-out interrupt is cleared, and the reset signal has been enabled by setting the RESEN bit in the WDTCTL register, the Watchdog timer asserts its reset signal to the system. If the interrupt is cleared before the 32-bit counter reaches its second time-out, the 32-bit counter is loaded with the value in the WDTLOAD register, and counting resumes from that value. If WDTLOAD is written with a new value while the Watchdog Timer counter is counting, then the counter is loaded with the new value and continues counting.
757
Watchdog Timers
Writing to WDTLOAD does not clear an active interrupt. An interrupt must be specifically cleared by writing to the Watchdog Interrupt Clear (WDTICR) register. The Watchdog module interrupt and reset generation can be enabled or disabled as required. When the interrupt is re-enabled, the 32-bit counter is preloaded with the load register value and not its last state.
12.2.1
Register Access Timing

Because the Watchdog Timer 1 module has an independent clocking domain, its registers must be written with a timing gap between accesses. Software must guarantee that this delay is inserted between back-to-back writes to WDT1 registers or between a write followed by a read to the registers. The timing for back-to-back reads from the WDT1 module has no restrictions. The WRC bit in the Watchdog Control (WDTCTL) register for WDT1 indicates that the required timing gap has elapsed. This bit is cleared on a write operation and set once the write completes, indicating to software that another write or read may be started safely. Software should poll WDTCTL for WRC=1 prior to accessing another register. Note that WDT0 does not have this restriction as it runs off the system clock.
12.3

To use the WDT, its peripheral clock must be enabled by setting the WDT bit in the RCGC0n register, see page 447. The Watchdog Timer is configured using the following sequence: 1. Load the WDTLOAD register with the desired timer load value. 2. If WDT1, wait for the WRC bit in the WDTCTL register to be set. 3. If the Watchdog is configured to trigger system resets, set the RESEN bit in the WDTCTL register. 4. If WDT1, wait for the WRC bit in the WDTCTL register to be set. 5. Set the INTEN bit in the WDTCTL register to enable the Watchdog and lock the control register. If software requires that all of the watchdog registers are locked, the Watchdog Timer module can be fully locked by writing any value to the WDTLOCK register. To unlock the Watchdog Timer, write a value of 0x1ACC.E551. To service the watchdog, periodically reload the count value into the WDTLOAD register to restart the count. The interrupt can be enabled using the INTEN bit in the WDTCTL register to allow the processor to attempt corrective action if the watchdog is not serviced often enough. The RESEN bit in WDTCTL can be set so that the system resets if the failure is not recoverable using the ISR.
12.4
Register Map
Table 12-1 on page 759 lists the Watchdog registers. The offset listed is a hexadecimal increment to the register's address, relative to the Watchdog Timer base address: WDT0: 0x4000.0000 WDT1: 0x4000.1000 Note that the Watchdog Timer module clock must be enabled before the registers can be programmed (see page 447).
April 25, 2012
Table 12-1. Watchdog Timers Register Map

Offset 0x000 0x004 Name WDTLOAD WDTVALUE Type R/W RO Reset 0xFFFF.FFFF 0xFFFF.FFFF 0x0000.0000 (WDT0) 0x8000.0000 (WDT1) 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0005 0x0000.0018 0x0000.0018 0x0000.0001 0x0000.000D 0x0000.00F0 0x0000.0006 0x0000.00B1 Description Watchdog Load Watchdog Value See page 760 761
0x008
WDTCTL
R/W
Watchdog Control
762
0x00C 0x010 0x014 0x418 0xC00 0xFD0 0xFD4 0xFD8 0xFDC 0xFE0 0xFE4 0xFE8 0xFEC 0xFF0 0xFF4 0xFF8 0xFFC
WDTICR WDTRIS WDTMIS WDTTEST WDTLOCK WDTPeriphID4 WDTPeriphID5 WDTPeriphID6 WDTPeriphID7 WDTPeriphID0 WDTPeriphID1 WDTPeriphID2 WDTPeriphID3 WDTPCellID0 WDTPCellID1 WDTPCellID2 WDTPCellID3
WO RO RO R/W R/W RO RO RO RO RO RO RO RO RO RO RO RO
Watchdog Interrupt Clear Watchdog Raw Interrupt Status Watchdog Masked Interrupt Status Watchdog Test Watchdog Lock Watchdog Peripheral Identification 4 Watchdog Peripheral Identification 5 Watchdog Peripheral Identification 6 Watchdog Peripheral Identification 7 Watchdog Peripheral Identification 0 Watchdog Peripheral Identification 1 Watchdog Peripheral Identification 2 Watchdog Peripheral Identification 3 Watchdog PrimeCell Identification 0 Watchdog PrimeCell Identification 1 Watchdog PrimeCell Identification 2 Watchdog PrimeCell Identification 3
764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780
12.5
The remainder of this section lists and describes the WDT registers, in numerical order by address offset.
759
Watchdog Timers
Register 1: Watchdog Load (WDTLOAD), offset 0x000

This register is the 32-bit interval value used by the 32-bit counter. When this register is written, the value is immediately loaded and the counter restarts counting down from the new value. If the WDTLOAD register is loaded with 0x0000.0000, an interrupt is immediately generated.
Watchdog Load (WDTLOAD)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x000 Type R/W, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
WDTLOAD Type Reset R/W 1 15 R/W 1 14 R/W 1 13 R/W 1 12 R/W 1 11 R/W 1 10 R/W 1 9 R/W 1 8 R/W 1 7 R/W 1 6 R/W 1 5 R/W 1 4 R/W 1 3 R/W 1 2 R/W 1 1 R/W 1 0
WDTLOAD Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1
Bit/Field 31:0
Name WDTLOAD
Type R/W
Reset
Description
0xFFFF.FFFF Watchdog Load Value
April 25, 2012
Register 2: Watchdog Value (WDTVALUE), offset 0x004

This register contains the current count value of the timer.
Watchdog Value (WDTVALUE)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x004 Type RO, reset 0xFFFF.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
WDTVALUE Type Reset RO 1 15 RO 1 14 RO 1 13 RO 1 12 RO 1 11 RO 1 10 RO 1 9 RO 1 8 RO 1 7 RO 1 6 RO 1 5 RO 1 4 RO 1 3 RO 1 2 RO 1 1 RO 1 0
WDTVALUE Type Reset RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1 RO 1
Bit/Field 31:0
Name WDTVALUE
Type RO
Reset
Description
0xFFFF.FFFF Watchdog Value Current value of the 32-bit down counter.
761
Watchdog Timers
Register 3: Watchdog Control (WDTCTL), offset 0x008

This register is the watchdog control register. The watchdog timer can be configured to generate a reset signal (on second time-out) or an interrupt on time-out. When the watchdog interrupt has been enabled by setting the INTEN bit, all subsequent writes to the INTEN bit are ignored. The only mechanism that can re-enable writes to this bit is a hardware reset. Important: Because the Watchdog Timer 1 module has an independent clocking domain, its registers must be written with a timing gap between accesses. Software must guarantee that this delay is inserted between back-to-back writes to WDT1 registers or between a write followed by a read to the registers. The timing for back-to-back reads from the WDT1 module has no restrictions. The WRC bit in the Watchdog Control (WDTCTL) register for WDT1 indicates that the required timing gap has elapsed. This bit is cleared on a write operation and set once the write completes, indicating to software that another write or read may be started safely. Software should poll WDTCTL for WRC=1 prior to accessing another register. Note that WDT0 does not have this restriction as it runs off the system clock and therefore does not have a WRC bit.
Watchdog Control (WDTCTL)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x008 Type R/W, reset 0x0000.0000 (WDT0) and 0x8000.0000 (WDT1)
31 WRC Type Reset RO 1 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 30 29 28 27 26 25 24 23 reserved RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 INTTYPE R/W 0 RO 0 1 RESEN R/W 0 RO 0 0 INTEN R/W 0 22 21 20 19 18 17 16
Bit/Field 31
Name WRC
Type RO
Reset 1
Description Write Complete The WRC values are defined as follows: Value Description 0 1 A write access to one of the WDT1 registers is in progress. A write access is not in progress, and WDT1 registers can be read or written. This bit is reserved for WDT0 and has a reset value of 0.
Note: 30:3 reserved RO 0x000.000
April 25, 2012
Bit/Field 2
Name INTTYPE
Type R/W
Reset 0
Description Watchdog Interrupt Type The INTTYPE values are defined as follows: Value Description 0 1 Watchdog interrupt is a standard interrupt. Watchdog interrupt is a non-maskable interrupt.
RESEN
R/W
Watchdog Reset Enable The RESEN values are defined as follows: Value Description 0 1 Disabled. Enable the Watchdog module reset output.
INTEN
R/W
Watchdog Interrupt Enable The INTEN values are defined as follows: Value Description 0 1 Interrupt event disabled (once this bit is set, it can only be cleared by a hardware reset). Interrupt event enabled. Once enabled, all writes are ignored.
763
Watchdog Timers
Register 4: Watchdog Interrupt Clear (WDTICR), offset 0x00C

This register is the interrupt clear register. A write of any value to this register clears the Watchdog interrupt and reloads the 32-bit counter from the WDTLOAD register. Value for a read or reset is indeterminate.
Watchdog Interrupt Clear (WDTICR)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x00C Type WO, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
WDTINTCLR Type Reset WO 15 WO 14 WO 13 WO 12 WO 11 WO 10 WO 9 WO 8 WO 7 WO 6 WO 5 WO 4 WO 3 WO 2 WO 1 WO 0
WDTINTCLR Type Reset WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO WO -
Bit/Field 31:0
Name WDTINTCLR
Type WO
Reset -
Description Watchdog Interrupt Clear
April 25, 2012
Register 5: Watchdog Raw Interrupt Status (WDTRIS), offset 0x010

This register is the raw interrupt status register. Watchdog interrupt events can be monitored via this register if the controller interrupt is masked.
Watchdog Raw Interrupt Status (WDTRIS)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x010 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 WDTRIS RO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Raw Interrupt Status Value Description 1 0 A watchdog time-out event has occurred. The watchdog has not timed out.
WDTRIS
RO
765
Watchdog Timers
Register 6: Watchdog Masked Interrupt Status (WDTMIS), offset 0x014

This register is the masked interrupt status register. The value of this register is the logical AND of the raw interrupt bit and the Watchdog interrupt enable bit.
Watchdog Masked Interrupt Status (WDTMIS)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x014 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 WDTMIS RO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Masked Interrupt Status Value Description 1 0 A watchdog time-out event has been signalled to the interrupt controller. The watchdog has not timed out or the watchdog timer interrupt is masked.
WDTMIS
RO
April 25, 2012
Register 7: Watchdog Test (WDTTEST), offset 0x418

This register provides user-enabled stalling when the microcontroller asserts the CPU halt flag during debug.
Watchdog Test (WDTTEST)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0x418 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 STALL R/W 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 reserved RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:9
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Stall Enable Value Description 1 If the microcontroller is stopped with a debugger, the watchdog timer stops counting. Once the microcontroller is restarted, the watchdog timer resumes counting. The watchdog timer continues counting if the microcontroller is stopped with a debugger.
STALL
R/W
7:0
reserved
RO
0x00
767
Watchdog Timers
Register 8: Watchdog Lock (WDTLOCK), offset 0xC00

Writing 0x1ACC.E551 to the WDTLOCK register enables write access to all other registers. Writing any other value to the WDTLOCK register re-enables the locked state for register writes to all the other registers. Reading the WDTLOCK register returns the lock status rather than the 32-bit value written. Therefore, when write accesses are disabled, reading the WDTLOCK register returns 0x0000.0001 (when locked; otherwise, the returned value is 0x0000.0000 (unlocked)).
Watchdog Lock (WDTLOCK)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xC00 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
WDTLOCK Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0
WDTLOCK Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:0
Name WDTLOCK
Type R/W
Reset
Description
0x0000.0000 Watchdog Lock A write of the value 0x1ACC.E551 unlocks the watchdog registers for write access. A write of any other value reapplies the lock, preventing any register updates. A read of this register returns the following values: Value Description
0x0000.0001 Locked 0x0000.0000 Unlocked
April 25, 2012
Register 9: Watchdog Peripheral Identification 4 (WDTPeriphID4), offset 0xFD0

The WDTPeriphIDn registers are hard-coded and the fields within the register determine the reset value.
Watchdog Peripheral Identification 4 (WDTPeriphID4)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFD0 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. WDT Peripheral ID Register [7:0]
7:0
PID4
RO
0x00
769
Watchdog Timers

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID5
RO
0x00
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID6
RO
0x00
771
Watchdog Timers
Register 12: Watchdog Peripheral Identification 7 (WDTPeriphID7), offset 0xFDC

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFDC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID7
RO
0x00
April 25, 2012
Register 13: Watchdog Peripheral Identification 0 (WDTPeriphID0), offset 0xFE0

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFE0 Type RO, reset 0x0000.0005
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog Peripheral ID Register [7:0]
7:0
PID0
RO
0x05
773
Watchdog Timers

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID1
RO
0x18
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID2
RO
0x18
775
Watchdog Timers
Register 16: Watchdog Peripheral Identification 3 (WDTPeriphID3), offset 0xFEC

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFEC Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID3
RO
0x01
April 25, 2012
Register 17: Watchdog PrimeCell Identification 0 (WDTPCellID0), offset 0xFF0

The WDTPCellIDn registers are hard-coded and the fields within the register determine the reset value.
Watchdog PrimeCell Identification 0 (WDTPCellID0)
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFF0 Type RO, reset 0x0000.000D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Watchdog PrimeCell ID Register [7:0]
7:0
CID0
RO
0x0D
777
Watchdog Timers

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFF4 Type RO, reset 0x0000.00F0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID1
RO
0xF0
April 25, 2012

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFF8 Type RO, reset 0x0000.0006
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID2
RO
0x06
779
Watchdog Timers
Register 20: Watchdog PrimeCell Identification 3 (WDTPCellID3 ), offset 0xFFC

WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000 Offset 0xFFC Type RO, reset 0x0000.00B1
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID3
RO
0xB1
April 25, 2012
13
Analog-to-Digital Converter (ADC)

An analog-to-digital converter (ADC) is a peripheral that converts a continuous analog voltage to a discrete digital number. Two identical converter modules are included, which share 12 input channels. The Stellaris ADC module features 12-bit conversion resolution and supports 12 input channels, plus an internal temperature sensor. Each ADC module contains four programmable sequencers allowing the sampling of multiple analog input sources without controller intervention. Each sample sequencer provides flexible programming with fully configurable input source, trigger events, interrupt generation, and sequencer priority. A digital comparator function is included which allows the conversion value to be diverted to a digital comparator module. Each ADC module provides eight digital comparators. Each digital comparator evaluates the ADC conversion value against its two user-defined values to determine the operational range of the signal. The trigger source for ADC0 and ADC1 may be independent or the two ADC modules may operate from the same trigger source and operate on the same or different inputs. A phase shifter can delay the start of sampling by a specified phase angle. When using both ADC modules, it is possible to configure the converters to start the conversions coincidentally or within a relative phase from each other, see Sample Phase Control on page 786. The Stellaris LM4F120H5QR microcontroller provides two ADC modules with each having the following features: 12 shared analog input channels 12-bit precision ADC Single-ended and differential-input configurations On-chip internal temperature sensor Maximum sample rate of one million samples/second Optional phase shift in sample time programmable from 22.5 to 337.5 Four programmable sample conversion sequencers from one to eight entries long, with corresponding conversion result FIFOs Flexible trigger control Controller (software) Timers Analog Comparators GPIO Hardware averaging of up to 64 samples Digital comparison unit providing eight digital comparators Converter uses VDDA and GNDA as the voltage reference Power and ground for the analog circuitry is separate from the digital power and ground
781
Efficient transfers using Micro Direct Memory Access Controller (DMA) Dedicated channel for each sample sequencer ADC module uses burst requests for DMA
13.1
Block Diagram
The Stellaris microcontroller contains two identical Analog-to-Digital Converter modules. These two modules, ADC0 and ADC1, share the same 12 analog input channels. Each ADC module operates independently and can therefore execute different sample sequences, sample any of the analog input channels at any time, and generate different interrupts and triggers. Figure 13-1 on page 782 shows how the two modules are connected to analog inputs and the system bus. Figure 13-1. Implementation of Two ADC Blocks
Triggers Interrupts/ Triggers
ADC 0
Input Channels
ADC 1
Interrupts/ Triggers
Figure 13-2 on page 783 provides details on the internal configuration of the ADC controls and data registers.
April 25, 2012
Figure 13-2. ADC Module Block Diagram

VDDA/GNDA Trigger Events Comparator GPIO Timer PWM Comparator GPIO Timer PWM Comparator GPIO Timer PWM Comparator GPIO Timer PWM Sample Sequencer 0 ADCSSMUX0 ADCACTSS ADCOSTAT ADCUSTAT SS2 ADCSSPRI ADCSPC ADCPP ADCPC SS1 Sample Sequencer 1 ADCSSMUX1 ADCSSEMUX1 ADCSSCTL1 ADCSSFSTAT1 Sample Sequencer 2 ADCSSMUX2 ADCEMUX ADCPSSI ADCSSEMUX2 ADCSSCTL2 ADCSSFSTAT2 Sample Sequencer 3 ADCSSMUX3 ADCSSEMUX3 ADCSSCTL3 ADCSSFSTAT3 DC Interrupts ADCSSFIFO0 ADCSSFIFO1 ADCSSFIFO2 ADCSSFIFO3 FIFO Block Digital Comparator ADCSSOPn ADCSSDCn ADCDCCTLn ADCDCCMPn ADCDCRIC Hardware Averager ADCSAC ADCSSEMUX0 ADCSSCTL0 ADCSSFSTAT0 Analog-to-Digital Converter Analog Inputs (AINx)
SS3
Control/Status
SS0
SS0 Interrupt SS1 Interrupt SS2 Interrupt SS3 Interrupt
Interrupt Control ADCIM ADCRIS ADCISC ADCDCISC
PWM Trigger
13.2
Signal Description
The following table lists the external signals of the ADC module and describes the function of each. The AINx signals are analog functions for some GPIO signals. The column in the table below titled "Pin Mux/Pin Assignment" lists the GPIO pin placement for the ADC signals. These signals are configured by clearing the corresponding DEN bit in the GPIO Digital Enable (GPIODEN) register and setting the corresponding AMSEL bit in the GPIO Analog Mode Select (GPIOAMSEL) register. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
Table 13-1. ADC Signals (64LQFP)

Pin Name AIN0 AIN1 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7 AIN8 Pin Number Pin Mux / Pin Assignment 6 7 8 9 64 63 62 61 60 PE3 PE2 PE1 PE0 PD3 PD2 PD1 PD0 PE5 Pin Type I I I I I I I I I Buffer Type Analog Analog Analog Analog Analog Analog Analog Analog Analog
a
Description Analog-to-digital converter input 0. Analog-to-digital converter input 1. Analog-to-digital converter input 2. Analog-to-digital converter input 3. Analog-to-digital converter input 4. Analog-to-digital converter input 5. Analog-to-digital converter input 6. Analog-to-digital converter input 7. Analog-to-digital converter input 8.
783
Table 13-1. ADC Signals (64LQFP) (continued)

Pin Name AIN9 AIN10 AIN11 Pin Number Pin Mux / Pin Assignment 59 58 57 PE4 PB4 PB5 Pin Type I I I Buffer Type Analog Analog Analog
a
Description Analog-to-digital converter input 9. Analog-to-digital converter input 10. Analog-to-digital converter input 11.
13.3
The Stellaris ADC collects sample data by using a programmable sequence-based approach instead of the traditional single or double-sampling approaches found on many ADC modules. Each sample sequence is a fully programmed series of consecutive (back-to-back) samples, allowing the ADC to collect data from multiple input sources without having to be re-configured or serviced by the processor. The programming of each sample in the sample sequence includes parameters such as the input source and mode (differential versus single-ended input), interrupt generation on sample completion, and the indicator for the last sample in the sequence. In addition, the DMA can be used to more efficiently move data from the sample sequencers without CPU intervention.
13.3.1
Sample Sequencers
The sampling control and data capture is handled by the sample sequencers. All of the sequencers are identical in implementation except for the number of samples that can be captured and the depth of the FIFO. Table 13-2 on page 784 shows the maximum number of samples that each sequencer can capture and its corresponding FIFO depth. Each sample that is captured is stored in the FIFO. In this implementation, each FIFO entry is a 32-bit word, with the lower 12 bits containing the conversion result. Table 13-2. Samples and FIFO Depth of Sequencers
Sequencer SS3 SS2 SS1 SS0 Number of Samples 1 4 4 8 Depth of FIFO 1 4 4 8
For a given sample sequence, each sample is defined by bit fields in the ADC Sample Sequence Input Multiplexer Select (ADCSSMUXn) and ADC Sample Sequence Control (ADCSSCTLn) registers, where "n" corresponds to the sequence number. The ADCSSMUXn fields select the input pin, while the ADCSSCTLn fields contain the sample control bits corresponding to parameters such as temperature sensor selection, interrupt enable, end of sequence, and differential input mode. Sample sequencers are enabled by setting the respective ASENn bit in the ADC Active Sample Sequencer (ADCACTSS) register and should be configured before being enabled. Sampling is then initiated by setting the SSn bit in the ADC Processor Sample Sequence Initiate (ADCPSSI) register. In addition, sample sequences may be initiated on multiple ADC modules simultaneously using the GSYNC and SYNCWAIT bits in the ADCPSSI register during the configuration of each ADC module. For more information on using these bits, refer to page 822. When configuring a sample sequence, multiple uses of the same input pin within the same sequence are allowed. In the ADCSSCTLn register, the IEn bits can be set for any combination of samples, allowing interrupts to be generated after every sample in the sequence if necessary. Also, the END bit can be set at any point within a sample sequence. For example, if Sequencer 0 is used, the END
April 25, 2012
bit can be set in the nibble associated with the fifth sample, allowing Sequencer 0 to complete execution of the sample sequence after the fifth sample. After a sample sequence completes execution, the result data can be retrieved from the ADC Sample Sequence Result FIFO (ADCSSFIFOn) registers. The FIFOs are simple circular buffers that read a single address to "pop" result data. For software debug purposes, the positions of the FIFO head and tail pointers are visible in the ADC Sample Sequence FIFO Status (ADCSSFSTATn) registers along with FULL and EMPTY status flags. If a write is attempted when the FIFO is full, the write does not occur and an overflow condition is indicated. Overflow and underflow conditions are monitored using the ADCOSTAT and ADCUSTAT registers.
13.3.2
Module Control
Outside of the sample sequencers, the remainder of the control logic is responsible for tasks such as: Interrupt generation DMA operation Sequence prioritization Trigger configuration Comparator configuration External voltage reference Sample phase control Module clocking Most of the ADC control logic runs at the ADC clock rate of 16 MHz. The internal ADC divider is configured for 16-MHz operation automatically by hardware when the system XTAL is selected with the PLL.
13.3.2.1
Interrupts
The register configurations of the sample sequencers and digital comparators dictate which events generate raw interrupts, but do not have control over whether the interrupt is actually sent to the interrupt controller. The ADC module's interrupt signals are controlled by the state of the MASK bits in the ADC Interrupt Mask (ADCIM) register. Interrupt status can be viewed at two locations: the ADC Raw Interrupt Status (ADCRIS) register, which shows the raw status of the various interrupt signals; and the ADC Interrupt Status and Clear (ADCISC) register, which shows active interrupts that are enabled by the ADCIM register. Sequencer interrupts are cleared by writing a 1 to the corresponding IN bit in ADCISC. Digital comparator interrupts are cleared by writing a 1 to the ADC Digital Comparator Interrupt Status and Clear (ADCDCISC) register.
13.3.2.2
DMA Operation
DMA may be used to increase efficiency by allowing each sample sequencer to operate independently and transfer data without processor intervention or reconfiguration. The ADC module provides a request signal from each sample sequencer to the associated dedicated channel of the DMA controller. The ADC does not support single transfer requests. A burst transfer request is asserted when the interrupt bit for the sample sequence is set (IE bit in the ADCSSCTLn register is set).
785
The arbitration size of the DMA transfer must be a power of 2, and the associated IE bits in the ADCSSCTLn register must be set. For example, if the DMA channel of SS0 has an arbitration size of four, the IE3 bit (4th sample) and the IE7 bit (8th sample) must be set. Thus the DMA request occurs every time 4 samples have been acquired. No other special steps are needed to enable the ADC module for DMA operation. Refer to the Micro Direct Memory Access (DMA) on page 568 for more details about programming the DMA controller.
13.3.2.3
Prioritization
When sampling events (triggers) happen concurrently, they are prioritized for processing by the values in the ADC Sample Sequencer Priority (ADCSSPRI) register. Valid priority values are in the range of 0-3, with 0 being the highest priority and 3 being the lowest. Multiple active sample sequencer units with the same priority do not provide consistent results, so software must ensure that all active sample sequencer units have a unique priority value.
13.3.2.4
Sampling Events
Sample triggering for each sample sequencer is defined in the ADC Event Multiplexer Select (ADCEMUX) register. Trigger sources include processor (default), analog comparators, an external signal on a GPIO specified by the GPIO ADC Control (GPIOADCCTL) register, a GP Timer, and continuous sampling. The processor triggers sampling by setting the SSx bits in the ADC Processor Sample Sequence Initiate (ADCPSSI) register. Care must be taken when using the continuous sampling trigger. If a sequencer's priority is too high, it is possible to starve other lower priority sequencers. Generally, a sample sequencer using continuous sampling should be set to the lowest priority. Continuous sampling can be used with a digital comparator to cause an interrupt when a particular voltage is seen on an input.
13.3.2.5
Sample Phase Control

The trigger source for ADC0 and ADC1 may be independent or the two ADC modules may operate from the same trigger source and operate on the same or different inputs. If the converters are running at the same sample rate, they may be configured to start the conversions coincidentally or with one of 15 different discrete phases relative to each other. The sample time can be delayed from the standard sampling time in 22.5 increments up to 337.5 using the ADC Sample Phase Control (ADCSPC) register. Figure 13-3 on page 786 shows an example of various phase relationships at a 1 Msps rate.
Figure 13-3. ADC Sample Phases

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
ADC Sample Clock PHASE 0x0 (0.0) PHASE 0x1 (22.5)

. . . . . . . . . . . .
PHASE 0xE (315.0) PHASE 0xF (337.5)
This feature can be used to double the sampling rate of an input. Both ADC module 0 and ADC module 1 can be programmed to sample the same input. ADC module 0 could sample at the standard
April 25, 2012
position (the PHASE field in the ADCSPC register is 0x0). ADC module 1 can be configured to sample at 180 (PHASE = 0x8). The two modules can be be synchronized using the GSYNC and SYNCWAIT bits in the ADC Processor Sample Sequence Initiate (ADCPSSI) register. Software could then combine the results from the two modules to create a sample rate of two million samples/second at 16 MHz as shown in Figure 13-4 on page 787. Figure 13-4. Doubling the ADC Sample Rate
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
ADC Sample Clock GSYNC ADC 0 PHASE 0x0 (0.0) ADC 1 PHASE 0x8 (180.0)
Using the ADCSPC register, ADC0 and ADC1 may provide a number of interesting applications: Coincident sampling of different signals. The sample sequence steps run coincidently in both converters. ADC Module 0, ADCSPC = 0x0, sampling AIN0 ADC Module 1, ADCSPC = 0x0, sampling AIN1 Skewed sampling of the same signal. The sample sequence steps are 1/2 of an ADC clock (500 s for a 1Ms/s ADC) out of phase with each other. This configuration doubles the conversion bandwidth of a single input when software combines the results as shown in Figure 13-5 on page 787. ADC Module 0, ADCSPC = 0x0, sampling AIN0 ADC Module 1, ADCSPC = 0x8, sampling AIN0 Figure 13-5. Skewed Sampling
ADC0 ADC1
S1 S1
S2 S2
S3 S3
S4 S4
S5 S5
S6 S6
S7 S7
S8 S8
787
13.3.2.6
Module Clocking
The module is clocked by a 16-MHz clock which can be sourced by a divided version of the PLL output, the PIOSC or an external source connected to MOSC (with the PLL in bypass mode). When the PLL is operating, the ADC clock is derived from the PLL 25 by default. However, the PIOSC can be used for the module clock using the ADC Clock Configuration (ADCCC) register. When the PLL is bypassed, the module clock source clock attached to the MOSC must be 16 MHz unless the PIOSC is used for the clock source. The ADC module can continue to operate in Deep-Sleep mode if the PIOSC is the ADC module clock source.
13.3.3
Hardware Sample Averaging Circuit

Higher precision results can be generated using the hardware averaging circuit, however, the improved results are at the cost of throughput. Up to 64 samples can be accumulated and averaged to form a single data entry in the sequencer FIFO. Throughput is decreased proportionally to the number of samples in the averaging calculation. For example, if the averaging circuit is configured to average 16 samples, the throughput is decreased by a factor of 16. By default the averaging circuit is off, and all data from the converter passes through to the sequencer FIFO. The averaging hardware is controlled by the ADC Sample Averaging Control (ADCSAC) register (see page 824). A single averaging circuit has been implemented, thus all input channels receive the same amount of averaging whether they are single-ended or differential. Figure 13-6 shows an example in which the ADCSAC register is set to 0x2 for 4x hardware oversampling and the IE1 bit is set for the sample sequence, resulting in an interrupt after the second averaged value is stored in the FIFO. Figure 13-6. Sample Averaging Example
A+B+C+D 4
A+B+C+D 4
INT
13.3.4 Analog-to-Digital Converter
The Analog-to-Digital Converter (ADC) module uses a Successive Approximation Register (SAR) architecture to deliver a 12-bit, low-power, high-precision conversion value. The successive
April 25, 2012
approximation uses a switched capacitor array to perform the dual functions of sampling and holding the signal as well as providing the 12-bit DAC operation. The ADC requires a 16-MHz clock. This clock can be a divided version of the PLL output, the PIOSC or a 16-MHz clock source connected to MOSC. The MOSC provides the best results, followed by the PLL divided down, and then the PIOSC. Figure 13-7 shows the ADC input equivalency diagram; for parameter values, see Analog-to-Digital Converter (ADC) on page 1174. Figure 13-7. ADC Input Equivalency Diagram
Stellaris Microcontroller Zs Rs Pin

InputPAD Equivalent Circuit
ESDclamps toGNDonly
ZADC RADC 12bit SARADC Converter 12bit Word
VS
Cs
VADCIN
5VESD Clamp
IL
Pin
RADC
Pin
RADC
CADC
The ADC operates from both the 3.3-V analog and 1.2-V digital power supplies. The ADC clock can be configured to reduce power consumption when ADC conversions are not required (see System Control on page 222). The analog inputs are connected to the ADC through specially balanced input paths to minimize the distortion and cross-talk on the inputs. Detailed information on the ADC power supplies and analog inputs can be found in Analog-to-Digital Converter (ADC) on page 1174.
13.3.4.1
Voltage Reference
The ADC uses internal signals VREFP and VREFN as references to produce a conversion value from the selected analog input. VREFP is connected to VDDA and VREFN is connected to GNDA. as shown in Figure 13-8.
789
Figure 13-8. ADC Voltage Reference

VDDA VDDA VREFP
GNDA
VREFN GNDA
ADC
The range of this conversion value is from 0x000 to 0xFFF. In single-ended-input mode, the 0x000 value corresponds to the voltage level on VREFN; the 0xFFF value corresponds to the voltage level on VREFP. This configuration results in a resolution that can be calculated using the following equation: mV per ADC code = (VREFP - VREFN) / 4096 While the analog input pads can handle voltages beyond this range, the ADC conversions saturate in under-voltage and over-voltage cases. Analog input voltages above VREFP saturate at 0xFFF while those below VREFN saturate at 0x000. Figure 13-9 on page 791 shows the ADC conversion function of the analog inputs.
April 25, 2012
Figure 13-9. ADC Conversion Result

0xFFF
0xC00
0x800
0x400
EF
EF
EF
EF
VR
-V
-V
EF
EF
(V R
(V
- Input Saturation
13.3.5
Differential Sampling
In addition to traditional single-ended sampling, the ADC module supports differential sampling of two analog input channels. To enable differential sampling, software must set the Dn bit in the ADCSSCTL0n register in a step's configuration nibble. When a sequence step is configured for differential sampling, the input pair to sample must be configured in the ADCSSMUXn register. Differential pair 0 samples analog inputs 0 and 1; differential pair 1 samples analog inputs 2 and 3; and so on (see Table 13-3 on page 791). The ADC does not support other differential pairings such as analog input 0 with analog input 3. Table 13-3. Differential Sampling Pairs
Differential Pair 0 1 2 3 4 5 Analog Inputs 0 and 1 2 and 3 4 and 5 6 and 7 8 and 9 10 and 11
(V
EF
-V
VR
EF
VIN
791
The voltage sampled in differential mode is the difference between the odd and even channels: Input Positive Voltage: VIN+ = VIN_EVEN (even channel) Input Negative Voltage: VIN- = VIN_ODD (odd channel) The input differential voltage is defined as: VIND = VIN+ - VIN-, therefore: If VIND = 0, then the conversion result = 0x800 If VIND > 0, then the conversion result > 0x800 (range is 0x8000xFFF) If VIND < 0, then the conversion result < 0x800 (range is 00x800) When using differential sampling, the following definitions are relevant: Input Common Mode Voltage: VINCM = (VIN+ + VIN-) / 2 Reference Positive Voltage: VREFP Reference Negative Voltage: VREFN Reference Differential Voltage: VREFD = VREFP - VREFN Reference Common Mode Voltage: VREFCM = (VREFP + VREFN) / 2 The following conditions provide optimal results in differential mode: Both VIN_EVEN and VIN_ODD must be in the range of (VREFP to VREFN) for a valid conversion result The maximum possible differential input swing, or the maximum differential range, is: -VREFDto +VREFD, so the maximum peak-to-peak input differential signal is (+VREFD - -VREFD) = 2 * VREFD= 2 * (VREFP - VREFN) In order to take advantage of the maximum possible differential input swing, VINCM should be very close to VREFCM, see Table 23-25 on page 1174. If VINCM is not equal to VREFCM, the differential input signal may clip at either maximum or minimum voltage, because either single ended input can never be larger than VREFP or smaller than VREFN, and it is not possible to achieve full swing. Thus any difference in common mode between the input voltage and the reference voltage limits the differential dynamic range of the ADC. Because the maximum peak-to-peak differential signal voltage is 2 * (VREFP - VREFN), the ADC codes are interpreted as: mV per ADC code = (2 *(VREFP - VREFN)) / 4096 Figure 13-10 shows how the differential voltage, V, is represented in ADC codes.
April 25, 2012
Figure 13-10. Differential Voltage Representation
0xFFF
0x800
-(VREFP - VREFN)
0 V
VREFP - VREFN
- Input Saturation
13.3.6
Internal Temperature Sensor

The temperature sensor serves two primary purposes: 1) to notify the system that internal temperature is too high or low for reliable operation and 2) to provide temperature measurements for calibration of the Hibernate module RTC trim value. The temperature sensor does not have a separate enable, because it also contains the bandgap reference and must always be enabled. The reference is supplied to other analog modules; not just the ADC. In addition, the temperature sensor has a second power-down input in the 3.3 V domain which provides control by the Hibernation module. The internal temperature sensor converts a temperature measurement into a voltage. This voltage value, VTSENS, is given by the following equation (where TEMP is the temperature in C): VTSENS = 2.7 - ((TEMP + 55) / 75) This relation is shown in Figure 13-11 on page 794.
793
Figure 13-11. Internal Temperature Sensor Characteristic
VTSENS = 2.7 V (TEMP+55) 75
VTSENS
2.5 V
1.633 V
0.833 V
-40 C
25 C
85 C
Temp
The temperature sensor reading can be sampled in a sample sequence by setting the TSn bit in the ADCSSCTLn register. The temperature reading from the temperature sensor can also be given as a function of the ADC value. The following formula calculates temperature (TEMP in ) based on the ADC reading (ADCCODE, given as an unsigned decimal number from 0 to 4095) and the maximum ADC voltage range (VREFP - VREFN): TEMP = 147.5 - ((75 * (VREFP - VREFN) ADCCODE) / 4096)
13.3.7
Digital Comparator Unit

An ADC is commonly used to sample an external signal and to monitor its value to ensure that it remains in a given range. To automate this monitoring procedure and reduce the amount of processor overhead that is required, each module provides eight digital comparators. Conversions from the ADC that are sent to the digital comparators are compared against the user programmable limits in the ADC Digital Comparator Range (ADCDCCMPn) registers. The ADC can be configured to generate an interrupt depending on whether the ADC is operating within the low, mid or high-band region configured in the ADCDCCMPn bit fields. The digital comparators four operational modes (Once, Always, Hysteresis Once, Hysteresis Always) can be additionally applied to the interrupt configuration.
13.3.7.1
Output Functions
ADC conversions can either be stored in the ADC Sample Sequence FIFOs or compared using the digital comparator resources as defined by the SnDCOP bits in the ADC Sample Sequence n Operation (ADCSSOPn) register. These selected ADC conversions are used by their respective
April 25, 2012
digital comparator to monitor the external signal. Each comparator has two possible output functions: processor interrupts and triggers. Each function has its own state machine to track the monitored signal. Even though the interrupt and trigger functions can be enabled individually or both at the same time, the same conversion data is used by each function to determine if the right conditions have been met to assert the associated output. Interrupts The digital comparator interrupt function is enabled by setting the CIE bit in the ADC Digital Comparator Control (ADCDCCTLn) register. This bit enables the interrupt function state machine to start monitoring the incoming ADC conversions. When the appropriate set of conditions is met, and the DCONSSx bit is set in the ADCIM register, an interrupt is sent to the interrupt controller.
13.3.7.2
Operational Modes
Four operational modes are provided to support a broad range of applications and multiple possible signaling requirements: Always, Once, Hysteresis Always, and Hysteresis Once. The operational mode is selected using the CIM field in the ADCDCCTLn register. Always Mode In the Always operational mode, the associated interrupt or trigger is asserted whenever the ADC conversion value meets its comparison criteria. The result is a string of assertions on the interrupt or trigger while the conversions are within the appropriate range. Once Mode In the Once operational mode, the associated interrupt or trigger is asserted whenever the ADC conversion value meets its comparison criteria, and the previous ADC conversion value did not. The result is a single assertion of the interrupt or trigger when the conversions are within the appropriate range. Hysteresis-Always Mode The Hysteresis-Always operational mode can only be used in conjunction with the low-band or high-band regions because the mid-band region must be crossed and the opposite region entered to clear the hysteresis condition. In the Hysteresis-Always mode, the associated interrupt or trigger is asserted in the following cases: 1) the ADC conversion value meets its comparison criteria or 2) a previous ADC conversion value has met the comparison criteria, and the hysteresis condition has not been cleared by entering the opposite region. The result is a string of assertions on the interrupt or trigger that continue until the opposite region is entered. Hysteresis-Once Mode The Hysteresis-Once operational mode can only be used in conjunction with the low-band or high-band regions because the mid-band region must be crossed and the opposite region entered to clear the hysteresis condition. In the Hysteresis-Once mode, the associated interrupt or trigger is asserted only when the ADC conversion value meets its comparison criteria, the hysteresis condition is clear, and the previous ADC conversion did not meet the comparison criteria. The result is a single assertion on the interrupt or trigger.
13.3.7.3
Function Ranges
The two comparison values, COMP0 and COMP1, in the ADC Digital Comparator Range (ADCDCCMPn) register effectively break the conversion area into three distinct regions. These
795
regions are referred to as the low-band (less than or equal to COMP0), mid-band (greater than COMP0 but less than or equal to COMP1), and high-band (greater than COMP1) regions. COMP0 and COMP1 may be programmed to the same value, effectively creating two regions, but COMP1 must always be greater than or equal to the value of COMP0. A COMP1 value that is less than COMP0 generates unpredictable results. Low-Band Operation To operate in the low-band region, either the CIC field field in the ADCDCCTLn register must be programmed to 0x0. This setting causes interrupts or triggers to be generated in the low-band region as defined by the programmed operational mode. An example of the state of the interrupt/trigger signal in the low-band region for each of the operational modes is shown in Figure 13-12 on page 796. Note that a "0" in a column following the operational mode name (Always, Once, Hysteresis Always, and Hysteresis Once) indicates that the interrupt or trigger signal is de-asserted and a "1" indicates that the signal is asserted. Figure 13-12. Low-Band Operation (CIC=0x0)
COMP1
COMP0
Always Once Hysteresis Always Hysteresis Once
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
1 1 1 1
1 0 1 0
1 0 1 0
0 0 1 0
0 0 1 0
1 1 1 0
1 0 1 0
0 0 1 0
0 0 0 0
0 0 0 0
0 0 0 0
1 1 1 1
Mid-Band Operation To operate in the mid-band region, either the CIC field field in the ADCDCCTLn register must be programmed to 0x1. This setting causes interrupts or triggers to be generated in the mid-band region according the operation mode. Only the Always and Once operational modes are available in the mid-band region. An example of the state of the interrupt/trigger signal in the mid-band region for each of the allowed operational modes is shown in Figure 13-13 on page 797. Note that a "0" in a column following the operational mode name (Always or Once) indicates that the interrupt or trigger signal is de-asserted and a "1" indicates that the signal is asserted.
April 25, 2012
Figure 13-13. Mid-Band Operation (CIC=0x1)
COMP1
COMP0
0 0 -
0 0 -
1 1 -
1 0 -
0 0 -
0 0 -
0 0 -
1 1 -
1 0 -
1 0 -
0 0 -
0 0 -
1 1 -
1 0 -
0 0 -
0 0 -
High-Band Operation To operate in the high-band region, either the CIC field field in the ADCDCCTLn register must be programmed to 0x3. This setting causes interrupts or triggers to be generated in the high-band region according the operation mode. An example of the state of the interrupt/trigger signal in the high-band region for each of the allowed operational modes is shown in Figure 13-14 on page 798. Note that a "0" in a column following the operational mode name (Always, Once, Hysteresis Always, and Hysteresis Once) indicates that the interrupt or trigger signal is de-asserted and a "1" indicates that the signal is asserted.
797
Figure 13-14. High-Band Operation (CIC=0x3)
COMP1
COMP0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
1 1 1 1
1 0 1 0
1 0 1 0
0 0 1 0
0 0 1 0
1 1 1 0
1 0 1 0
0 0 1 0
0 0 0 0
0 0 0 0
1 1 1 1
1 0 1 0
13.4

In order for the ADC module to be used, the PLL must be enabled and programmed to a supported crystal frequency in the RCC register (see page 245). Using unsupported frequencies can cause faulty operation in the ADC module.
13.4.1
Module Initialization
Initialization of the ADC module is a simple process with very few steps: enabling the clock to the ADC, disabling the analog isolation circuit associated with all inputs that are to be used, and reconfiguring the sample sequencer priorities (if needed). The initialization sequence for the ADC is as follows: 1. Enable the ADC clock using the RCGCADC register (see page 324). 2. Enable the clock to the appropriate GPIO modules via the RCGCGPIO register (see page 312). To find out which GPIO ports to enable, refer to Signal Description on page 783. 3. Set the GPIO AFSEL bits for the ADC input pins (see page 653). To determine which GPIOs to configure, see Table 21-4 on page 1148. 4. Configure the AINx signals to be analog inputs by clearing the corresponding DEN bit in the GPIO Digital Enable (GPIODEN) register (see page 664). 5. Disable the analog isolation circuit for all ADC input pins that are to be used by writing a 1 to the appropriate bits of the GPIOAMSEL register (see page 669) in the associated GPIO block.
April 25, 2012
6. If required by the application, reconfigure the sample sequencer priorities in the ADCSSPRI register. The default configuration has Sample Sequencer 0 with the highest priority and Sample Sequencer 3 as the lowest priority.
13.4.2
Sample Sequencer Configuration

Configuration of the sample sequencers is slightly more complex than the module initialization because each sample sequencer is completely programmable. The configuration for each sample sequencer should be as follows: 1. Ensure that the sample sequencer is disabled by clearing the corresponding ASENn bit in the ADCACTSS register. Programming of the sample sequencers is allowed without having them enabled. Disabling the sequencer during programming prevents erroneous execution if a trigger event were to occur during the configuration process. 2. Configure the trigger event for the sample sequencer in the ADCEMUX register. 3. For each sample in the sample sequence, configure the corresponding input source in the ADCSSMUXn register. 4. For each sample in the sample sequence, configure the sample control bits in the corresponding nibble in the ADCSSCTLn register. When programming the last nibble, ensure that the END bit is set. Failure to set the END bit causes unpredictable behavior. 5. If interrupts are to be used, set the corresponding MASK bit in the ADCIM register. 6. Enable the sample sequencer logic by setting the corresponding ASENn bit in the ADCACTSS register.
13.5
Register Map
Table 13-4 on page 799 lists the ADC registers. The offset listed is a hexadecimal increment to the registers address, relative to that ADC module's base address of: ADC0: 0x4003.8000 ADC1: 0x4003.9000 Note that the ADC module clock must be enabled before the registers can be programmed (see page 324). There must be a delay of 3 system clocks after the ADC module clock is enabled before any ADC module registers are accessed.
Table 13-4. ADC Register Map

Offset 0x000 0x004 0x008 0x00C 0x010 0x014 Name ADCACTSS ADCRIS ADCIM ADCISC ADCOSTAT ADCEMUX Type R/W RO R/W R/W1C R/W1C R/W Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description ADC Active Sample Sequencer ADC Raw Interrupt Status ADC Interrupt Mask ADC Interrupt Status and Clear ADC Overflow Status ADC Event Multiplexer Select See page 802 803 805 807 810 812
799
Table 13-4. ADC Register Map (continued)

Offset 0x018 0x020 0x024 0x028 0x030 0x034 0x040 0x044 0x048 0x04C 0x050 0x054 0x060 0x064 0x068 0x06C 0x070 0x074 0x080 0x084 0x088 0x08C 0x090 0x094 0x0A0 0x0A4 0x0A8 0x0AC 0x0B0 0x0B4 0xD00 0xE00 Name ADCUSTAT ADCSSPRI ADCSPC ADCPSSI ADCSAC ADCDCISC ADCSSMUX0 ADCSSCTL0 ADCSSFIFO0 ADCSSFSTAT0 ADCSSOP0 ADCSSDC0 ADCSSMUX1 ADCSSCTL1 ADCSSFIFO1 ADCSSFSTAT1 ADCSSOP1 ADCSSDC1 ADCSSMUX2 ADCSSCTL2 ADCSSFIFO2 ADCSSFSTAT2 ADCSSOP2 ADCSSDC2 ADCSSMUX3 ADCSSCTL3 ADCSSFIFO3 ADCSSFSTAT3 ADCSSOP3 ADCSSDC3 ADCDCRIC ADCDCCTL0 Type R/W1C R/W R/W R/W R/W R/W1C R/W R/W RO RO R/W R/W R/W R/W RO RO R/W R/W R/W R/W RO RO R/W R/W R/W R/W RO RO R/W R/W WO R/W Reset 0x0000.0000 0x0000.3210 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0100 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0100 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0100 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0100 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description ADC Underflow Status ADC Sample Sequencer Priority ADC Sample Phase Control ADC Processor Sample Sequence Initiate ADC Sample Averaging Control ADC Digital Comparator Interrupt Status and Clear ADC Sample Sequence Input Multiplexer Select 0 ADC Sample Sequence Control 0 ADC Sample Sequence Result FIFO 0 ADC Sample Sequence FIFO 0 Status ADC Sample Sequence 0 Operation ADC Sample Sequence 0 Digital Comparator Select ADC Sample Sequence Input Multiplexer Select 1 ADC Sample Sequence Control 1 ADC Sample Sequence Result FIFO 1 ADC Sample Sequence FIFO 1 Status ADC Sample Sequence 1 Operation ADC Sample Sequence 1 Digital Comparator Select ADC Sample Sequence Input Multiplexer Select 2 ADC Sample Sequence Control 2 ADC Sample Sequence Result FIFO 2 ADC Sample Sequence FIFO 2 Status ADC Sample Sequence 2 Operation ADC Sample Sequence 2 Digital Comparator Select ADC Sample Sequence Input Multiplexer Select 3 ADC Sample Sequence Control 3 ADC Sample Sequence Result FIFO 3 ADC Sample Sequence FIFO 3 Status ADC Sample Sequence 3 Operation ADC Sample Sequence 3 Digital Comparator Select ADC Digital Comparator Reset Initial Conditions ADC Digital Comparator Control 0 See page 817 818 820 822 824 825 827 829 832 833 835 837 839 840 832 833 842 843 839 840 832 833 842 843 845 846 832 833 847 848 849 854
April 25, 2012
Table 13-4. ADC Register Map (continued)

Offset 0xE04 0xE08 0xE0C 0xE10 0xE14 0xE18 0xE1C 0xE40 0xE44 0xE48 0xE4C 0xE50 0xE54 0xE58 0xE5C 0xFC0 0xFC4 0xFC8 Name ADCDCCTL1 ADCDCCTL2 ADCDCCTL3 ADCDCCTL4 ADCDCCTL5 ADCDCCTL6 ADCDCCTL7 ADCDCCMP0 ADCDCCMP1 ADCDCCMP2 ADCDCCMP3 ADCDCCMP4 ADCDCCMP5 ADCDCCMP6 ADCDCCMP7 ADCPP ADCPC ADCCC Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W RO R/W R/W Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x00B0.20C7 0x0000.0007 0x0000.0000 Description ADC Digital Comparator Control 1 ADC Digital Comparator Control 2 ADC Digital Comparator Control 3 ADC Digital Comparator Control 4 ADC Digital Comparator Control 5 ADC Digital Comparator Control 6 ADC Digital Comparator Control 7 ADC Digital Comparator Range 0 ADC Digital Comparator Range 1 ADC Digital Comparator Range 2 ADC Digital Comparator Range 3 ADC Digital Comparator Range 4 ADC Digital Comparator Range 5 ADC Digital Comparator Range 6 ADC Digital Comparator Range 7 ADC Peripheral Properties ADC Peripheral Configuration ADC Clock Configuration See page 854 854 854 854 854 854 854 856 856 856 856 856 856 856 856 857 859 860
13.6
The remainder of this section lists and describes the ADC registers, in numerical order by address offset.
801
Register 1: ADC Active Sample Sequencer (ADCACTSS), offset 0x000

This register controls the activation of the sample sequencers. Each sample sequencer can be enabled or disabled independently.
ADC Active Sample Sequencer (ADCACTSS)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 ASEN3 R/W 0 RO 0 2 ASEN2 R/W 0 RO 0 1 ASEN1 R/W 0 RO 0 0 ASEN0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC SS3 Enable Value Description 1 0 Sample Sequencer 3 is enabled. Sample Sequencer 3 is disabled.
ASEN3
R/W
ASEN2
R/W
ADC SS2 Enable Value Description 1 0 Sample Sequencer 2 is enabled. Sample Sequencer 2 is disabled.
ASEN1
R/W
ASEN0
R/W
April 25, 2012
Register 2: ADC Raw Interrupt Status (ADCRIS), offset 0x004

This register shows the status of the raw interrupt signal of each sample sequencer. These bits may be polled by software to look for interrupt conditions without sending the interrupts to the interrupt controller.
ADC Raw Interrupt Status (ADCRIS)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x004 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 INR3 RO 0 RO 0 2 INR2 RO 0 RO 0 1 INR1 RO 0 23 22 21 20 19 18 17 16 INRDC RO 0 0 INR0 RO 0
Bit/Field 31:17
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator Raw Interrupt Status Value Description 1 0 At least one bit in the ADCDCISC register is set, meaning that a digital comparator interrupt has occurred. All bits in the ADCDCISC register are clear.
16
INRDC
RO
15:4
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 Raw Interrupt Status Value Description 1 0 A sample has completed conversion and the respective ADCSSCTL3 IEn bit is set, enabling a raw interrupt. An interrupt has not occurred.
INR3
RO
This bit is cleared by writing a 1 to the IN3 bit in the ADCISC register. 2 INR2 RO 0 SS2 Raw Interrupt Status Value Description 1 0 A sample has completed conversion and the respective ADCSSCTL2 IEn bit is set, enabling a raw interrupt. An interrupt has not occurred.
This bit is cleared by writing a 1 to the IN2 bit in the ADCISC register.
803
Bit/Field 1
Name INR1
Type RO
Reset 0
Description SS1 Raw Interrupt Status Value Description 1 0 A sample has completed conversion and the respective ADCSSCTL1 IEn bit is set, enabling a raw interrupt. An interrupt has not occurred.
This bit is cleared by writing a 1 to the IN1 bit in the ADCISC register. 0 INR0 RO 0 SS0 Raw Interrupt Status Value Description 1 0 A sample has completed conversion and the respective ADCSSCTL0 IEn bit is set, enabling a raw interrupt. An interrupt has not occurred.
This bit is cleared by writing a 1 to the IN0 bit in the ADCISC register.
April 25, 2012
Register 3: ADC Interrupt Mask (ADCIM), offset 0x008

This register controls whether the sample sequencer and digital comparator raw interrupt signals are sent to the interrupt controller. Each raw interrupt signal can be masked independently. Only a single DCONSSn bit should be set at any given time. Setting more than one of these bits results in the INRDC bit from the ADCRIS register being masked, and no interrupt is generated on any of the sample sequencer interrupt lines.
ADC Interrupt Mask (ADCIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4
DCONSS3 DCONSS2 DCONSS1 DCONSS0 R/W 0 3 MASK3 R/W 0 R/W 0 2 MASK2 R/W 0 R/W 0 1 MASK1 R/W 0 R/W 0 0 MASK0 R/W 0
Bit/Field 31:20
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator Interrupt on SS3 Value Description 1 The raw interrupt signal from the digital comparators (INRDC bit in the ADCRIS register) is sent to the interrupt controller on the SS3 interrupt line. The status of the digital comparators does not affect the SS3 interrupt status.
19
DCONSS3
R/W
18
DCONSS2
R/W
Digital Comparator Interrupt on SS2 Value Description 1 The raw interrupt signal from the digital comparators (INRDC bit in the ADCRIS register) is sent to the interrupt controller on the SS2 interrupt line. The status of the digital comparators does not affect the SS2 interrupt status.
17
DCONSS1
R/W
Digital Comparator Interrupt on SS1 Value Description 1 The raw interrupt signal from the digital comparators (INRDC bit in the ADCRIS register) is sent to the interrupt controller on the SS1 interrupt line. The status of the digital comparators does not affect the SS1 interrupt status.
805
Bit/Field 16
Name DCONSS0
Type R/W
Reset 0
Description Digital Comparator Interrupt on SS0 Value Description 1 The raw interrupt signal from the digital comparators (INRDC bit in the ADCRIS register) is sent to the interrupt controller on the SS0 interrupt line. The status of the digital comparators does not affect the SS0 interrupt status.
15:4
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 Interrupt Mask Value Description 1 0 The raw interrupt signal from Sample Sequencer 3 (ADCRIS register INR3 bit) is sent to the interrupt controller. The status of Sample Sequencer 3 does not affect the SS3 interrupt status.
MASK3
R/W
MASK2
R/W
SS2 Interrupt Mask Value Description 1 0 The raw interrupt signal from Sample Sequencer 2 (ADCRIS register INR2 bit) is sent to the interrupt controller. The status of Sample Sequencer 2 does not affect the SS2 interrupt status.
MASK1
R/W
MASK0
R/W
April 25, 2012
Register 4: ADC Interrupt Status and Clear (ADCISC), offset 0x00C

This register provides the mechanism for clearing sample sequencer interrupt conditions and shows the status of interrupts generated by the sample sequencers and the digital comparators which have been sent to the interrupt controller. When read, each bit field is the logical AND of the respective INR and MASK bits. Sample sequencer interrupts are cleared by writing a 1 to the corresponding bit position. Digital comparator interrupts are cleared by writing a 1 to the appropriate bits in the ADCDCISC register. If software is polling the ADCRIS instead of generating interrupts, the sample sequence INRn bits are still cleared via the ADCISC register, even if the INn bit is not set.
ADC Interrupt Status and Clear (ADCISC)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x00C Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4
DCINSS3 DCINSS2 DCINSS1 DCINSS0 RO 0 3 IN3 R/W1C 0 RO 0 2 IN2 R/W1C 0 RO 0 1 IN1 R/W1C 0 RO 0 0 IN0 R/W1C 0
Bit/Field 31:20
Name reserved
Type RO
Reset 0x000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator Interrupt Status on SS3 Value Description 1 Both the INRDC bit in the ADCRIS register and the DCONSS3 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
19
DCINSS3
RO
This bit is cleared by writing a 1 to it. Clearing this bit also clears the INRDC bit in the ADCRIS register. 18 DCINSS2 RO 0 Digital Comparator Interrupt Status on SS2 Value Description 1 Both the INRDC bit in the ADCRIS register and the DCONSS2 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1 to it. Clearing this bit also clears the INRDC bit in the ADCRIS register.
807
Bit/Field 17
Name DCINSS1
Type RO
Reset 0
Description Digital Comparator Interrupt Status on SS1 Value Description 1 Both the INRDC bit in the ADCRIS register and the DCONSS1 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1 to it. Clearing this bit also clears the INRDC bit in the ADCRIS register. 16 DCINSS0 RO 0 Digital Comparator Interrupt Status on SS0 Value Description 1 Both the INRDC bit in the ADCRIS register and the DCONSS0 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1 to it. Clearing this bit also clears the INRDC bit in the ADCRIS register. 15:4 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 Interrupt Status and Clear Value Description 1 Both the INR3 bit in the ADCRIS register and the MASK3 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
IN3
R/W1C
This bit is cleared by writing a 1. Clearing this bit also clears the INR3 bit in the ADCRIS register. 2 IN2 R/W1C 0 SS2 Interrupt Status and Clear Value Description 1 Both the INR2 bit in the ADCRIS register and the MASK2 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1. Clearing this bit also clears the INR2 bit in the ADCRIS register.
April 25, 2012
Bit/Field 1
Name IN1
Type R/W1C
Reset 0
Description SS1 Interrupt Status and Clear Value Description 1 Both the INR1 bit in the ADCRIS register and the MASK1 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1. Clearing this bit also clears the INR1 bit in the ADCRIS register. 0 IN0 R/W1C 0 SS0 Interrupt Status and Clear Value Description 1 Both the INR0 bit in the ADCRIS register and the MASK0 bit in the ADCIM register are set, providing a level-based interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1. Clearing this bit also clears the INR0 bit in the ADCRIS register.
809
Register 5: ADC Overflow Status (ADCOSTAT), offset 0x010

This register indicates overflow conditions in the sample sequencer FIFOs. Once the overflow condition has been handled by software, the condition can be cleared by writing a 1 to the corresponding bit position.
ADC Overflow Status (ADCOSTAT)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x010 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 OV3 R/W1C 0 RO 0 2 OV2 R/W1C 0 RO 0 1 OV1 R/W1C 0 RO 0 0 OV0 R/W1C 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 FIFO Overflow Value Description 1 The FIFO for Sample Sequencer 3 has hit an overflow condition, meaning that the FIFO is full and a write was requested. When an overflow is detected, the most recent write is dropped. The FIFO has not overflowed.
OV3
R/W1C
This bit is cleared by writing a 1. 2 OV2 R/W1C 0 SS2 FIFO Overflow Value Description 1 The FIFO for Sample Sequencer 2 has hit an overflow condition, meaning that the FIFO is full and a write was requested. When an overflow is detected, the most recent write is dropped. The FIFO has not overflowed.
This bit is cleared by writing a 1. 1 OV1 R/W1C 0 SS1 FIFO Overflow Value Description 1 The FIFO for Sample Sequencer 1 has hit an overflow condition, meaning that the FIFO is full and a write was requested. When an overflow is detected, the most recent write is dropped. The FIFO has not overflowed.
This bit is cleared by writing a 1.
April 25, 2012
Bit/Field 0
Name OV0
Type R/W1C
Reset 0
Description SS0 FIFO Overflow Value Description 1 The FIFO for Sample Sequencer 0 has hit an overflow condition, meaning that the FIFO is full and a write was requested. When an overflow is detected, the most recent write is dropped. The FIFO has not overflowed.
811
Register 6: ADC Event Multiplexer Select (ADCEMUX), offset 0x014

The ADCEMUX selects the event (trigger) that initiates sampling for each sample sequencer. Each sample sequencer can be configured with a unique trigger source.
ADC Event Multiplexer Select (ADCEMUX)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 EM3 Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 13 RO 0 12 RO 0 11 RO 0 10 EM2 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 EM1 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 EM0 R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
April 25, 2012
Bit/Field 15:12
Name EM3
Type R/W
Reset 0x0
Description SS3 Trigger Select This field selects the trigger source for Sample Sequencer 3. The valid configurations for this field are: Value 0x0 Event Processor (default) The trigger is initiated by setting the SSn bit in the ADCPSSI register. 0x1 Analog Comparator 0 This trigger is configured by the Analog Comparator Control 0 (ACCTL0) register (page 1133). 0x2 Analog Comparator 1 This trigger is configured by the Analog Comparator Control 1 (ACCTL1) register (page 1133). 0x3 0x4 reserved External (GPIO Pins) This trigger is connected to the GPIO interrupt for the corresponding GPIO (see ADC Trigger Source on page 638). Note: GPIOs that have AINx signals as alternate functions can be used to trigger the ADC. However, the pin cannot be used as both a GPIO and an analog input.
0x5
Timer In addition, the trigger must be enabled with the TnOTE bit in the GPTMCTL register (page 719).
0x6 0x7 0x8 0x9
0xA-0xE reserved 0xF Always (continuously sample)
813
Bit/Field 11:8
Name EM2
Type R/W
Reset 0x0
0x5
0x6 0x7 0x8 0x9
April 25, 2012
Bit/Field 7:4
Name EM1
Type R/W
Reset 0x0
0x5
0x6 0x7 0x8 0x9
815
Bit/Field 3:0
Name EM0
Type R/W
Reset 0x0
Description SS0 Trigger Select This field selects the trigger source for Sample Sequencer 0 The valid configurations for this field are: Value 0x0 Event Processor (default) The trigger is initiated by setting the SSn bit in the ADCPSSI register. 0x1 Analog Comparator 0 This trigger is configured by the Analog Comparator Control 0 (ACCTL0) register (page 1133). 0x2 Analog Comparator 1 This trigger is configured by the Analog Comparator Control 1 (ACCTL1) register (page 1133). 0x3 0x4 reserved External (GPIO Pins) This trigger is connected to the GPIO interrupt for the corresponding GPIO (see ADC Trigger Source on page 638). Note: GPIOs that have AINx signals as alternate functions can be used to trigger the ADC. However, the pin cannot be used as both a GPIO and an analog input.
0x5
0x6 0x7 0x8 0x9
April 25, 2012
Register 7: ADC Underflow Status (ADCUSTAT), offset 0x018

This register indicates underflow conditions in the sample sequencer FIFOs. The corresponding underflow condition is cleared by writing a 1 to the relevant bit position.
ADC Underflow Status (ADCUSTAT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 UV3 R/W1C 0 RO 0 2 UV2 R/W1C 0 RO 0 1 UV1 R/W1C 0 RO 0 0 UV0 R/W1C 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 FIFO Underflow The valid configurations for this field are shown below. This bit is cleared by writing a 1. Value Description 1 The FIFO for the Sample Sequencer has hit an underflow condition, meaning that the FIFO is empty and a read was requested. The problematic read does not move the FIFO pointers, and 0s are returned. The FIFO has not underflowed.
UV3
R/W1C
UV2
R/W1C
SS2 FIFO Underflow The valid configurations are the same as those for the UV3 field. This bit is cleared by writing a 1.
UV1
R/W1C
UV0
R/W1C
817
Register 8: ADC Sample Sequencer Priority (ADCSSPRI), offset 0x020

This register sets the priority for each of the sample sequencers. Out of reset, Sequencer 0 has the highest priority, and Sequencer 3 has the lowest priority. When reconfiguring sequence priorities, each sequence must have a unique priority for the ADC to operate properly.
ADC Sample Sequencer Priority (ADCSSPRI)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 SS3 R/W 1 R/W 1 RO 0 12 RO 0 11 RO 0 10 RO 0 9 SS2 R/W 1 R/W 0 RO 0 8 RO 0 7 reserved RO 0 RO 0 R/W 0 RO 0 6 RO 0 5 SS1 R/W 1 RO 0 4 RO 0 3 reserved RO 0 RO 0 R/W 0 RO 0 2 RO 0 1 SS0 R/W 0 RO 0 0
reserved RO 0 RO 0
Bit/Field 31:14
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS3 Priority This field contains a binary-encoded value that specifies the priority encoding of Sample Sequencer 3. A priority encoding of 0x0 is highest and 0x3 is lowest. The priorities assigned to the sequencers must be uniquely mapped. The ADC may not operate properly if two or more fields are equal.
13:12
SS3
R/W
0x3
11:10
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS2 Priority This field contains a binary-encoded value that specifies the priority encoding of Sample Sequencer 2. A priority encoding of 0x0 is highest and 0x3 is lowest. The priorities assigned to the sequencers must be uniquely mapped. The ADC may not operate properly if two or more fields are equal.
9:8
SS2
R/W
0x2
7:6
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SS1 Priority This field contains a binary-encoded value that specifies the priority encoding of Sample Sequencer 1. A priority encoding of 0x0 is highest and 0x3 is lowest. The priorities assigned to the sequencers must be uniquely mapped. The ADC may not operate properly if two or more fields are equal.
5:4
SS1
R/W
0x1
3:2
reserved
RO
0x0
April 25, 2012
Bit/Field 1:0
Name SS0
Type R/W
Reset 0x0
Description SS0 Priority This field contains a binary-encoded value that specifies the priority encoding of Sample Sequencer 0. A priority encoding of 0x0 is highest and 0x3 is lowest. The priorities assigned to the sequencers must be uniquely mapped. The ADC may not operate properly if two or more fields are equal.
819
Register 9: ADC Sample Phase Control (ADCSPC), offset 0x024

This register allows the ADC module to sample at one of 16 different discrete phases from 0.0 through 337.5. For example, the sample rate could be effectively doubled by sampling a signal using one ADC module configured with the standard sample time and the second ADC module configured with a 180.0 phase lag. Note: Care should be taken when the PHASE field is non-zero, as the resulting delay in sampling the AINx input may result in undesirable system consequences. The time from ADC trigger to sample is increased and could make the response time longer than anticipated. The added latency could have ramifications in the system design. Designers should carefully consider the impact of this delay.
ADC Sample Phase Control (ADCSPC)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 PHASE R/W 0 R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
April 25, 2012
Bit/Field 3:0
Name PHASE
Type R/W
Reset 0x0
Description Phase Difference This field selects the sample phase difference from the standard sample time. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF ADC sample lags by 0.0 ADC sample lags by 22.5 ADC sample lags by 45.0 ADC sample lags by 67.5 ADC sample lags by 90.0 ADC sample lags by 112.5 ADC sample lags by 135.0 ADC sample lags by 157.5 ADC sample lags by 180.0 ADC sample lags by 202.5 ADC sample lags by 225.0 ADC sample lags by 247.5 ADC sample lags by 270.0 ADC sample lags by 292.5 ADC sample lags by 315.0 ADC sample lags by 337.5
821
Register 10: ADC Processor Sample Sequence Initiate (ADCPSSI), offset 0x028
This register provides a mechanism for application software to initiate sampling in the sample sequencers. Sample sequences can be initiated individually or in any combination. When multiple sequences are triggered simultaneously, the priority encodings in ADCSSPRI dictate execution order. This register also provides a means to configure and then initiate concurrent sampling on all ADC modules. To do this, the first ADC module should be configured. The ADCPSSI register for that module should then be written. The appropriate SS bits should be set along with the SYNCWAIT bit. Additional ADC modules should then be configured following the same procedure. Once the final ADC module is configured, its ADCPSSI register should be written with the appropriate SS bits set along with the GSYNC bit. All of the ADC modules then begin concurrent sampling according to their configuration.
ADC Processor Sample Sequence Initiate (ADCPSSI)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x028 Type R/W, reset 31 GSYNC Type Reset R/W 0 15 RO 0 14 30 29 reserved RO 0 13 RO 0 12 28 27
SYNCWAIT
26
25
24
23
22
21 reserved
20
19
18
17
16
R/W 0 11
RO 0 10
RO 0 9
RO 0 8
RO 0 7
RO 0 6
RO 0 5
RO 0 4
RO 0 3 SS3
RO 0 2 SS2 WO -
RO 0 1 SS1 WO -
RO 0 0 SS0 WO -
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0
WO -
Bit/Field 31
Name GSYNC
Type R/W
Reset 0
Description Global Synchronize Value Description 1 This bit initiates sampling in multiple ADC modules at the same time. Any ADC module that has been initialized by setting an SSn bit and the SYNCWAIT bit starts sampling once this bit is written. This bit is cleared once sampling has been initiated.
30:28
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Synchronize Wait Value Description 1 0 This bit allows the sample sequences to be initiated, but delays sampling until the GSYNC bit is set. Sampling begins when a sample sequence has been initiated.
27
SYNCWAIT
R/W
26:4
reserved
RO
0x0000.0
April 25, 2012
Bit/Field 3
Name SS3
Type WO
Reset -
Description SS3 Initiate Value Description 1 0 Begin sampling on Sample Sequencer 3, if the sequencer is enabled in the ADCACTSS register. No effect.
Only a write by software is valid; a read of this register returns no meaningful data. 2 SS2 WO SS2 Initiate Value Description 1 0 Begin sampling on Sample Sequencer 2, if the sequencer is enabled in the ADCACTSS register. No effect.
Only a write by software is valid; a read of this register returns no meaningful data.
823
Register 11: ADC Sample Averaging Control (ADCSAC), offset 0x030

This register controls the amount of hardware averaging applied to conversion results. The final conversion result stored in the FIFO is averaged from 2 AVG consecutive ADC samples at the specified ADC speed. If AVG is 0, the sample is passed directly through without any averaging. If AVG=6, then 64 consecutive ADC samples are averaged to generate one result in the sequencer FIFO. An AVG=7 provides unpredictable results.
ADC Sample Averaging Control (ADCSAC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 AVG R/W 0 R/W 0 RO 0 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Hardware Averaging Control Specifies the amount of hardware averaging that will be applied to ADC samples. The AVG field can be any value between 0 and 6. Entering a value of 7 creates unpredictable results. Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 No hardware oversampling 2x hardware oversampling 4x hardware oversampling 8x hardware oversampling 16x hardware oversampling 32x hardware oversampling 64x hardware oversampling reserved
2:0
AVG
R/W
0x0
April 25, 2012
Register 12: ADC Digital Comparator Interrupt Status and Clear (ADCDCISC), offset 0x034
This register provides status and acknowledgement of digital comparator interrupts. One bit is provided for each comparator.
ADC Digital Comparator Interrupt Status and Clear (ADCDCISC)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 DCINT7 RO 0 RO 0 RO 0 R/W1C 0 RO 0 6 DCINT6 R/W1C 0 RO 0 5 DCINT5 R/W1C 0 RO 0 4 DCINT4 R/W1C 0 RO 0 3 DCINT3 R/W1C 0 RO 0 2 DCINT2 R/W1C 0 RO 0 1 DCINT1 R/W1C 0 RO 0 0 DCINT0 R/W1C 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator 7 Interrupt Status and Clear Value Description 1 0 Digital Comparator 7 has generated an interrupt. No interrupt.
DCINT7
R/W1C
This bit is cleared by writing a 1. 6 DCINT6 R/W1C 0 Digital Comparator 6 Interrupt Status and Clear Value Description 1 0 Digital Comparator 6 has generated an interrupt. No interrupt.
825
Bit/Field 4
Name DCINT4
Type R/W1C
Reset 0
Description Digital Comparator 4 Interrupt Status and Clear Value Description 1 0 Digital Comparator 4 has generated an interrupt. No interrupt.
April 25, 2012
Register 13: ADC Sample Sequence Input Multiplexer Select 0 (ADCSSMUX0), offset 0x040
This register defines the analog input configuration for each sample in a sequence executed with Sample Sequencer 0. This register is 32 bits wide and contains information for eight possible samples.
ADC Sample Sequence Input Multiplexer Select 0 (ADCSSMUX0)
31 30 MUX7 Type Reset R/W 0 15 R/W 0 14 MUX3 Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 MUX2 R/W 0 R/W 0 R/W 0 R/W 0 29 28 27 26 MUX6 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 MUX1 R/W 0 R/W 0 R/W 0 R/W 0 25 24 23 22 MUX5 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 MUX0 R/W 0 R/W 0 21 20 19 18 MUX4 R/W 0 1 R/W 0 0 17 16
Bit/Field 31:28
Name MUX7
Type R/W
Reset 0x0
Description 8th Sample Input Select The MUX7 field is used during the eighth sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion. The value set here indicates the corresponding pin, for example, a value of 0x1 indicates the input is AIN1.
27:24
MUX6
R/W
0x0
7th Sample Input Select The MUX6 field is used during the seventh sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
23:20
MUX5
R/W
0x0
6th Sample Input Select The MUX5 field is used during the sixth sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
19:16
MUX4
R/W
0x0
5th Sample Input Select The MUX4 field is used during the fifth sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
15:12
MUX3
R/W
0x0
4th Sample Input Select The MUX3 field is used during the fourth sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
11:8
MUX2
R/W
0x0
3rd Sample Input Select The MUX2 field is used during the third sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
827
Bit/Field 7:4
Name MUX1
Type R/W
Reset 0x0
Description 2nd Sample Input Select The MUX1 field is used during the second sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
3:0
MUX0
R/W
0x0
1st Sample Input Select The MUX0 field is used during the first sample of a sequence executed with the sample sequencer. It specifies which of the analog inputs is sampled for the analog-to-digital conversion.
April 25, 2012
Register 14: ADC Sample Sequence Control 0 (ADCSSCTL0), offset 0x044

This register contains the configuration information for each sample for a sequence executed with a sample sequencer. When configuring a sample sequence, the END bit must be set for the final sample, whether it be after the first sample, eighth sample, or any sample in between. This register is 32 bits wide and contains information for eight possible samples.
ADC Sample Sequence Control 0 (ADCSSCTL0)
31 TS7 Type Reset R/W 0 15 TS3 Type Reset R/W 0 30 IE7 R/W 0 14 IE3 R/W 0 29 END7 R/W 0 13 END3 R/W 0 28 D7 R/W 0 12 D3 R/W 0 27 TS6 R/W 0 11 TS2 R/W 0 26 IE6 R/W 0 10 IE2 R/W 0 25 END6 R/W 0 9 END2 R/W 0 24 D6 R/W 0 8 D2 R/W 0 23 TS5 R/W 0 7 TS1 R/W 0 22 IE5 R/W 0 6 IE1 R/W 0 21 END5 R/W 0 5 END1 R/W 0 20 D5 R/W 0 4 D1 R/W 0 19 TS4 R/W 0 3 TS0 R/W 0 18 IE4 R/W 0 2 IE0 R/W 0 17 END4 R/W 0 1 END0 R/W 0 16 D4 R/W 0 0 D0 R/W 0
Bit/Field 31
Name TS7
Type R/W
Reset 0
Description 8th Sample Temp Sensor Select Value Description 1 0 The temperature sensor is read during the eighth sample of the sample sequence. The input pin specified by the ADCSSMUXn register is read during the eighth sample of the sample sequence.
30
IE7
R/W
8th Sample Interrupt Enable Value Description 1 The raw interrupt signal (INR0 bit) is asserted at the end of the eighth sample's conversion. If the MASK0 bit in the ADCIM register is set, the interrupt is promoted to the interrupt controller. The raw interrupt is not asserted to the interrupt controller.
It is legal to have multiple samples within a sequence generate interrupts. 29 END7 R/W 0 8th Sample is End of Sequence Value Description 1 0 The eighth sample is the last sample of the sequence. Another sample in the sequence is the final sample.
It is possible to end the sequence on any sample position. Software must set an ENDn bit somewhere within the sequence. Samples defined after the sample containing a set ENDn bit are not requested for conversion even though the fields may be non-zero.
829
Bit/Field 28
Name D7
Type R/W
Reset 0
Description 8th Sample Diff Input Select Value Description 1 The analog input is differentially sampled. The corresponding ADCSSMUXn nibble must be set to the pair number "i", where the paired inputs are "2i and 2i+1". The analog inputs are not differentially sampled.
Because the temperature sensor does not have a differential option, this bit must not be set when the TS7 bit is set. 27 TS6 R/W 0 7th Sample Temp Sensor Select Same definition as TS7 but used during the seventh sample. 26 IE6 R/W 0 7th Sample Interrupt Enable Same definition as IE7 but used during the seventh sample. 25 END6 R/W 0 7th Sample is End of Sequence Same definition as END7 but used during the seventh sample. 24 D6 R/W 0 7th Sample Diff Input Select Same definition as D7 but used during the seventh sample. 23 TS5 R/W 0 6th Sample Temp Sensor Select Same definition as TS7 but used during the sixth sample. 22 IE5 R/W 0 6th Sample Interrupt Enable Same definition as IE7 but used during the sixth sample. 21 END5 R/W 0 6th Sample is End of Sequence Same definition as END7 but used during the sixth sample. 20 D5 R/W 0 6th Sample Diff Input Select Same definition as D7 but used during the sixth sample. 19 TS4 R/W 0 5th Sample Temp Sensor Select Same definition as TS7 but used during the fifth sample. 18 IE4 R/W 0 5th Sample Interrupt Enable Same definition as IE7 but used during the fifth sample. 17 END4 R/W 0 5th Sample is End of Sequence Same definition as END7 but used during the fifth sample. 16 D4 R/W 0 5th Sample Diff Input Select Same definition as D7 but used during the fifth sample. 15 TS3 R/W 0 4th Sample Temp Sensor Select Same definition as TS7 but used during the fourth sample. 14 IE3 R/W 0 4th Sample Interrupt Enable Same definition as IE7 but used during the fourth sample.
April 25, 2012
Bit/Field 13
Name END3
Type R/W
Reset 0
Description 4th Sample is End of Sequence Same definition as END7 but used during the fourth sample.
12
D3
R/W
4th Sample Diff Input Select Same definition as D7 but used during the fourth sample.
11
TS2
R/W
3rd Sample Temp Sensor Select Same definition as TS7 but used during the third sample.
10
IE2
R/W
3rd Sample Interrupt Enable Same definition as IE7 but used during the third sample.
END2
R/W
3rd Sample is End of Sequence Same definition as END7 but used during the third sample.
D2
R/W
3rd Sample Diff Input Select Same definition as D7 but used during the third sample.
TS1
R/W
2nd Sample Temp Sensor Select Same definition as TS7 but used during the second sample.
IE1
R/W
2nd Sample Interrupt Enable Same definition as IE7 but used during the second sample.
END1
R/W
2nd Sample is End of Sequence Same definition as END7 but used during the second sample.
D1
R/W
2nd Sample Diff Input Select Same definition as D7 but used during the second sample.
TS0
R/W
1st Sample Temp Sensor Select Same definition as TS7 but used during the first sample.
IE0
R/W
1st Sample Interrupt Enable Same definition as IE7 but used during the first sample.
END0
R/W
1st Sample is End of Sequence Same definition as END7 but used during the first sample.
D0
R/W
1st Sample Diff Input Select Same definition as D7 but used during the first sample.
831
Register 15: ADC Sample Sequence Result FIFO 0 (ADCSSFIFO0), offset 0x048 Register 16: ADC Sample Sequence Result FIFO 1 (ADCSSFIFO1), offset 0x068 Register 17: ADC Sample Sequence Result FIFO 2 (ADCSSFIFO2), offset 0x088 Register 18: ADC Sample Sequence Result FIFO 3 (ADCSSFIFO3), offset 0x0A8
Important: This register is read-sensitive. See the register description for details. This register contains the conversion results for samples collected with the sample sequencer (the ADCSSFIFO0 register is used for Sample Sequencer 0, ADCSSFIFO1 for Sequencer 1, ADCSSFIFO2 for Sequencer 2, and ADCSSFIFO3 for Sequencer 3). Reads of this register return conversion result data in the order sample 0, sample 1, and so on, until the FIFO is empty. If the FIFO is not properly handled by software, overflow and underflow conditions are registered in the ADCOSTAT and ADCUSTAT registers.
ADC Sample Sequence Result FIFO n (ADCSSFIFOn)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x048 Type RO, reset 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 DATA RO 0 RO RO RO RO RO RO RO RO RO RO RO RO RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:12
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Conversion Result Data
11:0
DATA
RO
April 25, 2012
Register 19: ADC Sample Sequence FIFO 0 Status (ADCSSFSTAT0), offset 0x04C Register 20: ADC Sample Sequence FIFO 1 Status (ADCSSFSTAT1), offset 0x06C Register 21: ADC Sample Sequence FIFO 2 Status (ADCSSFSTAT2), offset 0x08C Register 22: ADC Sample Sequence FIFO 3 Status (ADCSSFSTAT3), offset 0x0AC
This register provides a window into the sample sequencer, providing full/empty status information as well as the positions of the head and tail pointers. The reset value of 0x100 indicates an empty FIFO with the head and tail pointers both pointing to index 0. The ADCSSFSTAT0 register provides status on FIFO0, which has 8 entries; ADCSSFSTAT1 on FIFO1, which has 4 entries; ADCSSFSTAT2 on FIFO2, which has 4 entries; and ADCSSFSTAT3 on FIFO3 which has a single entry.
ADC Sample Sequence FIFO n Status (ADCSSFSTATn)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x04C Type RO, reset 0x0000.0100
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 reserved Type Reset RO 0 RO 0 RO 0 RO 0 13 RO 0 12 FULL RO 0 RO 0 RO 0 11 RO 0 10 reserved RO 0 RO 0 RO 0 9 RO 0 8 EMPTY RO 1 RO 0 RO 0 RO 0 7 RO 0 6 HPTR RO 0 RO 0 RO 0 RO 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 TPTR RO 0 RO 0 RO 0 1 RO 0 0
Bit/Field 31:13
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. FIFO Full Value Description 1 0 The FIFO is currently full. The FIFO is not currently full.
12
FULL
RO
11:9
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. FIFO Empty Value Description 1 0 The FIFO is currently empty. The FIFO is not currently empty.
EMPTY
RO
833
Bit/Field 7:4
Name HPTR
Type RO
Reset 0x0
Description FIFO Head Pointer This field contains the current "head" pointer index for the FIFO, that is, the next entry to be written. Valid values are 0x0-0x7 for FIFO0; 0x0-0x3 for FIFO1 and FIFO2; and 0x0 for FIFO3.
3:0
TPTR
RO
0x0
FIFO Tail Pointer This field contains the current "tail" pointer index for the FIFO, that is, the next entry to be read. Valid values are 0x0-0x7 for FIFO0; 0x0-0x3 for FIFO1 and FIFO2; and 0x0 for FIFO3.
April 25, 2012
Register 23: ADC Sample Sequence 0 Operation (ADCSSOP0), offset 0x050

This register determines whether the sample from the given conversion on Sample Sequence 0 is saved in the Sample Sequence FIFO0 or sent to the digital comparator unit.
ADC Sample Sequence 0 Operation (ADCSSOP0)
31 30 reserved Type Reset RO 0 15 RO 0 14 reserved Type Reset RO 0 RO 0 RO 0 RO 0 13 29 28 S7DCOP R/W 0 12 S3DCOP R/W 0 RO 0 RO 0 11 27 26 reserved RO 0 10 reserved RO 0 RO 0 RO 0 9 25 24 S6DCOP R/W 0 8 S2DCOP R/W 0 RO 0 RO 0 7 23 22 reserved RO 0 6 reserved RO 0 RO 0 RO 0 5 21 20 S5DCOP R/W 0 4 S1DCOP R/W 0 RO 0 RO 0 3 19 18 reserved RO 0 2 reserved RO 0 RO 0 RO 0 1 17 16 S4DCOP R/W 0 0 S0DCOP R/W 0
Bit/Field 31:29
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 7 Digital Comparator Operation Value Description 1 The eighth sample is sent to the digital comparator unit specified by the S7DCSEL bit in the ADCSSDC0 register, and the value is not written to the FIFO. The eighth sample is saved in Sample Sequence FIFO0.
28
S7DCOP
R/W
27:25
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 6 Digital Comparator Operation Same definition as S7DCOP but used during the seventh sample.
24
S6DCOP
R/W
23:21
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 5 Digital Comparator Operation Same definition as S7DCOP but used during the sixth sample.
20
S5DCOP
R/W
19:17
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 4 Digital Comparator Operation Same definition as S7DCOP but used during the fifth sample.
16
S4DCOP
R/W
15:13
reserved
RO
0x0
835
Bit/Field 12
Name S3DCOP
Type R/W
Reset 0
Description Sample 3 Digital Comparator Operation Same definition as S7DCOP but used during the fourth sample.
11:9
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 2 Digital Comparator Operation Same definition as S7DCOP but used during the third sample.
S2DCOP
R/W
7:5
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 1 Digital Comparator Operation Same definition as S7DCOP but used during the second sample.
S1DCOP
R/W
3:1
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 0 Digital Comparator Operation Same definition as S7DCOP but used during the first sample.
S0DCOP
R/W
April 25, 2012
Register 24: ADC Sample Sequence 0 Digital Comparator Select (ADCSSDC0), offset 0x054
This register determines which digital comparator receives the sample from the given conversion on Sample Sequence 0, if the corresponding SnDCOP bit in the ADCSSOP0 register is set.
ADC Sample Sequence 0 Digital Comparator Select (ADCSSDC0)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
S7DCSEL Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11
S6DCSEL R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7
S5DCSEL R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3
S4DCSEL R/W 0 2 R/W 0 1 R/W 0 0
S3DCSEL Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
S2DCSEL R/W 0 R/W 0 R/W 0 R/W 0
S0DCSEL R/W 0 R/W 0 R/W 0
Bit/Field 31:28
Name S7DCSEL
Type R/W
Reset 0x0
Description Sample 7 Digital Comparator Select When the S7DCOP bit in the ADCSSOP0 register is set, this field indicates which digital comparator unit (and its associated set of control registers) receives the eighth sample from Sample Sequencer 0. Note: Values not listed are reserved.
Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Digital Comparator Unit 0 (ADCDCCMP0 and ADCDCCTL0) Digital Comparator Unit 1 (ADCDCCMP1 and ADCDCCTL1) Digital Comparator Unit 2 (ADCDCCMP2 and ADCDCCTL2) Digital Comparator Unit 3 (ADCDCCMP3 and ADCDCCTL3) Digital Comparator Unit 4 (ADCDCCMP4 and ADCDCCTL4) Digital Comparator Unit 5 (ADCDCCMP5 and ADCDCCTL5) Digital Comparator Unit 6 (ADCDCCMP6 and ADCDCCTL6) Digital Comparator Unit 7 (ADCDCCMP7 and ADCDCCTL7)
27:24
S6DCSEL
R/W
0x0
Sample 6 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the seventh sample.
23:20
S5DCSEL
R/W
0x0
Sample 5 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the sixth sample.
19:16
S4DCSEL
R/W
0x0
Sample 4 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the fifth sample.
15:12
S3DCSEL
R/W
0x0
Sample 3 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the fourth sample.
837
Bit/Field 11:8
Name S2DCSEL
Type R/W
Reset 0x0
Description Sample 2 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the third sample.
7:4
S1DCSEL
R/W
0x0
Sample 1 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the second sample.
3:0
S0DCSEL
R/W
0x0
Sample 0 Digital Comparator Select This field has the same encodings as S7DCSEL but is used during the first sample.
April 25, 2012
Register 25: ADC Sample Sequence Input Multiplexer Select 1 (ADCSSMUX1), offset 0x060 Register 26: ADC Sample Sequence Input Multiplexer Select 2 (ADCSSMUX2), offset 0x080
This register defines the analog input configuration for each sample in a sequence executed with Sample Sequencer 1 or 2. These registers are 16 bits wide and contain information for four possible samples. See the ADCSSMUX0 register on page 827 for detailed bit descriptions. The ADCSSMUX1 register affects Sample Sequencer 1 and the ADCSSMUX2 register affects Sample Sequencer 2.
ADC Sample Sequence Input Multiplexer Select n (ADCSSMUXn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 MUX3 Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 13 RO 0 12 RO 0 11 RO 0 10 MUX2 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 MUX1 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 MUX0 R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 4th Sample Input Select 3rd Sample Input Select 2nd Sample Input Select 1st Sample Input Select
15:12 11:8 7:4 3:0
MUX3 MUX2 MUX1 MUX0
R/W R/W R/W R/W
0x0 0x0 0x0 0x0
839
Register 27: ADC Sample Sequence Control 1 (ADCSSCTL1), offset 0x064 Register 28: ADC Sample Sequence Control 2 (ADCSSCTL2), offset 0x084
These registers contain the configuration information for each sample for a sequence executed with Sample Sequencer 1 or 2. When configuring a sample sequence, the END bit must be set for the final sample, whether it be after the first sample, fourth sample, or any sample in between. These registers are 16-bits wide and contain information for four possible samples. See the ADCSSCTL0 register on page 829 for detailed bit descriptions. The ADCSSCTL1 register configures Sample Sequencer 1 and the ADCSSCTL2 register configures Sample Sequencer 2.
ADC Sample Sequence Control n (ADCSSCTLn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 TS3 Type Reset R/W 0 RO 0 14 IE3 R/W 0 RO 0 13 END3 R/W 0 RO 0 12 D3 R/W 0 RO 0 11 TS2 R/W 0 RO 0 10 IE2 R/W 0 RO 0 9 END2 R/W 0 RO 0 8 D2 R/W 0 RO 0 7 TS1 R/W 0 RO 0 6 IE1 R/W 0 RO 0 5 END1 R/W 0 RO 0 4 D1 R/W 0 RO 0 3 TS0 R/W 0 RO 0 2 IE0 R/W 0 RO 0 1 END0 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 4th Sample Temp Sensor Select Same definition as TS7 but used during the fourth sample.
15
TS3
R/W
14
IE3
R/W
4th Sample Interrupt Enable Same definition as IE7 but used during the fourth sample.
13
END3
R/W
4th Sample is End of Sequence Same definition as END7 but used during the fourth sample.
12
D3
R/W
4th Sample Diff Input Select Same definition as D7 but used during the fourth sample.
11
TS2
R/W
3rd Sample Temp Sensor Select Same definition as TS7 but used during the third sample.
10
IE2
R/W
3rd Sample Interrupt Enable Same definition as IE7 but used during the third sample.
END2
R/W
3rd Sample is End of Sequence Same definition as END7 but used during the third sample.
D2
R/W
3rd Sample Diff Input Select Same definition as D7 but used during the third sample.
April 25, 2012
Bit/Field 7
Name TS1
Type R/W
Reset 0
Description 2nd Sample Temp Sensor Select Same definition as TS7 but used during the second sample.
IE1
R/W
2nd Sample Interrupt Enable Same definition as IE7 but used during the second sample.
END1
R/W
2nd Sample is End of Sequence Same definition as END7 but used during the second sample.
D1
R/W
2nd Sample Diff Input Select Same definition as D7 but used during the second sample.
TS0
R/W
1st Sample Temp Sensor Select Same definition as TS7 but used during the first sample.
IE0
R/W
END0
R/W
D0
R/W
841
Register 29: ADC Sample Sequence 1 Operation (ADCSSOP1), offset 0x070 Register 30: ADC Sample Sequence 2 Operation (ADCSSOP2), offset 0x090
This register determines whether the sample from the given conversion on Sample Sequence n is saved in the Sample Sequence n FIFO or sent to the digital comparator unit. The ADCSSOP1 register controls Sample Sequencer 1 and the ADCSSOP2 register controls Sample Sequencer 2.
ADC Sample Sequence n Operation (ADCSSOPn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 reserved Type Reset RO 0 RO 0 RO 0 RO 0 13 RO 0 12 S3DCOP R/W 0 RO 0 RO 0 11 RO 0 10 reserved RO 0 RO 0 RO 0 9 RO 0 8 S2DCOP R/W 0 RO 0 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 5 RO 0 4 S1DCOP R/W 0 RO 0 RO 0 3 RO 0 2 reserved RO 0 RO 0 RO 0 1 RO 0 0 S0DCOP R/W 0
Bit/Field 31:13
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 3 Digital Comparator Operation Value Description 1 The fourth sample is sent to the digital comparator unit specified by the S3DCSEL bit in the ADCSSDC0n register, and the value is not written to the FIFO. The fourth sample is saved in Sample Sequence FIFOn.
12
S3DCOP
R/W
11:9
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 2 Digital Comparator Operation Same definition as S3DCOP but used during the third sample.
S2DCOP
R/W
7:5
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 1 Digital Comparator Operation Same definition as S3DCOP but used during the second sample.
S1DCOP
R/W
3:1
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 0 Digital Comparator Operation Same definition as S3DCOP but used during the first sample.
S0DCOP
R/W
April 25, 2012
Register 31: ADC Sample Sequence 1 Digital Comparator Select (ADCSSDC1), offset 0x074 Register 32: ADC Sample Sequence 2 Digital Comparator Select (ADCSSDC2), offset 0x094
These registers determine which digital comparator receives the sample from the given conversion on Sample Sequence n if the corresponding SnDCOP bit in the ADCSSOPn register is set. The ADCSSDC1 register controls the selection for Sample Sequencer 1 and the ADCSSDC2 register controls the selection for Sample Sequencer 2.
ADC Sample Sequence n Digital Comparator Select (ADCSSDCn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
S3DCSEL Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 3 Digital Comparator Select When the S3DCOP bit in the ADCSSOPn register is set, this field indicates which digital comparator unit (and its associated set of control registers) receives the eighth sample from Sample Sequencer n. Note: Values not listed are reserved.
15:12
S3DCSEL
R/W
0x0
Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Digital Comparator Unit 0 (ADCDCCMP0 and ADCCCTL0) Digital Comparator Unit 1 (ADCDCCMP1 and ADCCCTL1) Digital Comparator Unit 2 (ADCDCCMP2 and ADCCCTL2) Digital Comparator Unit 3 (ADCDCCMP3 and ADCCCTL3) Digital Comparator Unit 4 (ADCDCCMP4 and ADCCCTL4) Digital Comparator Unit 5 (ADCDCCMP5 and ADCCCTL5) Digital Comparator Unit 6 (ADCDCCMP6 and ADCCCTL6) Digital Comparator Unit 7 (ADCDCCMP7 and ADCCCTL7)
11:8
S2DCSEL
R/W
0x0
Sample 2 Digital Comparator Select This field has the same encodings as S3DCSEL but is used during the third sample.
843
Bit/Field 7:4
Name S1DCSEL
Type R/W
Reset 0x0
Description Sample 1 Digital Comparator Select This field has the same encodings as S3DCSEL but is used during the second sample.
3:0
S0DCSEL
R/W
0x0
Sample 0 Digital Comparator Select This field has the same encodings as S3DCSEL but is used during the first sample.
April 25, 2012
Register 33: ADC Sample Sequence Input Multiplexer Select 3 (ADCSSMUX3), offset 0x0A0
This register defines the analog input configuration for the sample executed with Sample Sequencer 3. This register is 4 bits wide and contains information for one possible sample. See the ADCSSMUX0 register on page 827 for detailed bit descriptions.
ADC Sample Sequence Input Multiplexer Select 3 (ADCSSMUX3)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x0A0 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 MUX0 R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 1st Sample Input Select
3:0
MUX0
R/W
845
Register 34: ADC Sample Sequence Control 3 (ADCSSCTL3), offset 0x0A4

This register contains the configuration information for a sample executed with Sample Sequencer 3. This register is 4 bits wide and contains information for one possible sample. See the ADCSSCTL0 register on page 829 for detailed bit descriptions.
ADC Sample Sequence Control 3 (ADCSSCTL3)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x0A4 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 TS0 R/W 0 RO 0 2 IE0 R/W 0 RO 0 1 END0 R/W 0 RO 0 0 D0 R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 1st Sample Temp Sensor Select Same definition as TS7 but used during the first sample.
TS0
R/W
IE0
R/W
END0
R/W
D0
R/W
April 25, 2012
Register 35: ADC Sample Sequence 3 Operation (ADCSSOP3), offset 0x0B0

This register determines whether the sample from the given conversion on Sample Sequence 3 is saved in the Sample Sequence 3 FIFO or sent to the digital comparator unit.
ADC Sample Sequence 3 Operation (ADCSSOP3)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x0B0 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 S0DCOP R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 0 Digital Comparator Operation Value Description 1 The sample is sent to the digital comparator unit specified by the S0DCSEL bit in the ADCSSDC03 register, and the value is not written to the FIFO. The sample is saved in Sample Sequence FIFO3.
S0DCOP
R/W
847
Register 36: ADC Sample Sequence 3 Digital Comparator Select (ADCSSDC3), offset 0x0B4
This register determines which digital comparator receives the sample from the given conversion on Sample Sequence 3 if the corresponding SnDCOP bit in the ADCSSOP3 register is set.
ADC Sample Sequence 3 Digital Comparator Select (ADCSSDC3)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0x0B4 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sample 0 Digital Comparator Select When the S0DCOP bit in the ADCSSOP3 register is set, this field indicates which digital comparator unit (and its associated set of control registers) receives the sample from Sample Sequencer 3. Note: Values not listed are reserved.
3:0
S0DCSEL
R/W
0x0
Value Description 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Digital Comparator Unit 0 (ADCDCCMP0 and ADCCCTL0) Digital Comparator Unit 1 (ADCDCCMP1 and ADCCCTL1) Digital Comparator Unit 2 (ADCDCCMP2 and ADCCCTL2) Digital Comparator Unit 3 (ADCDCCMP3 and ADCCCTL3) Digital Comparator Unit 4 (ADCDCCMP4 and ADCCCTL4) Digital Comparator Unit 5 (ADCDCCMP5 and ADCCCTL5) Digital Comparator Unit 6 (ADCDCCMP6 and ADCCCTL6) Digital Comparator Unit 7 (ADCDCCMP7 and ADCCCTL7)
April 25, 2012
Register 37: ADC Digital Comparator Reset Initial Conditions (ADCDCRIC), offset 0xD00
This register provides the ability to reset any of the digital comparator interrupt or trigger functions back to their initial conditions. Resetting these functions ensures that the data that is being used by the interrupt and trigger functions in the digital comparator unit is not stale.
ADC Digital Comparator Reset Initial Conditions (ADCDCRIC)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xD00 Type WO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8
DCTRIG7 DCTRIG6 DCTRIG5 DCTRIG4 DCTRIG3 DCTRIG2 DCTRIG1 DCTRIG0 WO 0 7 DCINT7 RO 0 RO 0 RO 0 WO 0 WO 0 6 DCINT6 WO 0 WO 0 5 DCINT5 WO 0 WO 0 4 DCINT4 WO 0 WO 0 3 DCINT3 WO 0 WO 0 2 DCINT2 WO 0 WO 0 1 DCINT1 WO 0 WO 0 0 DCINT0 WO 0
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator Trigger 7 Value Description 1 0 Resets the Digital Comparator 7 trigger unit to its initial conditions. No effect.
23
DCTRIG7
WO
When the trigger has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the trigger, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used. After setting this bit, software should wait until the bit clears before continuing. 22 DCTRIG6 WO 0 Digital Comparator Trigger 6 Value Description 1 0 Resets the Digital Comparator 6 trigger unit to its initial conditions. No effect.
When the trigger has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the trigger, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used.
849
Bit/Field 21
Name DCTRIG5
Type WO
Reset 0
Description Digital Comparator Trigger 5 Value Description 1 0 Resets the Digital Comparator 5 trigger unit to its initial conditions. No effect.
When the trigger has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the trigger, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used. 20 DCTRIG4 WO 0 Digital Comparator Trigger 4 Value Description 1 0 Resets the Digital Comparator 4 trigger unit to its initial conditions. No effect.
When the trigger has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the trigger, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used.
April 25, 2012
Bit/Field 17
Name DCTRIG1
Type WO
Reset 0
Description Digital Comparator Trigger 1 Value Description 1 0 Resets the Digital Comparator 1 trigger unit to its initial conditions. No effect.
When the trigger has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the trigger, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used. 15:8 reserved RO 0x00 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Digital Comparator Interrupt 7 Value Description 1 0 Resets the Digital Comparator 7 interrupt unit to its initial conditions. No effect.
DCINT7
WO
When the interrupt has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the interrupt, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used. 6 DCINT6 WO 0 Digital Comparator Interrupt 6 Value Description 1 0 Resets the Digital Comparator 6 interrupt unit to its initial conditions. No effect.
When the interrupt has been cleared, this bit is automatically cleared. Because the digital comparators use the current and previous ADC conversion values to determine when to assert the interrupt, it is important to reset the digital comparator to initial conditions when starting a new sequence so that stale data is not used.
851
Bit/Field 5
Name DCINT5
Type WO
Reset 0
Description Digital Comparator Interrupt 5 Value Description 1 0 Resets the Digital Comparator 5 interrupt unit to its initial conditions. No effect.
April 25, 2012
Bit/Field 1
Name DCINT1
Type WO
Reset 0
Description Digital Comparator Interrupt 1 Value Description 1 0 Resets the Digital Comparator 1 interrupt unit to its initial conditions. No effect.
853
Register 38: ADC Digital Comparator Control 0 (ADCDCCTL0), offset 0xE00 Register 39: ADC Digital Comparator Control 1 (ADCDCCTL1), offset 0xE04 Register 40: ADC Digital Comparator Control 2 (ADCDCCTL2), offset 0xE08 Register 41: ADC Digital Comparator Control 3 (ADCDCCTL3), offset 0xE0C Register 42: ADC Digital Comparator Control 4 (ADCDCCTL4), offset 0xE10 Register 43: ADC Digital Comparator Control 5 (ADCDCCTL5), offset 0xE14 Register 44: ADC Digital Comparator Control 6 (ADCDCCTL6), offset 0xE18 Register 45: ADC Digital Comparator Control 7 (ADCDCCTL7), offset 0xE1C
This register provides the comparison encodings that generate an interrupt.
ADC Digital Comparator Control n (ADCDCCTLn)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xE00 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 CIE R/W 0 R/W 0 RO 0 3 CIC R/W 0 R/W 0 RO 0 2 RO 0 1 CIM R/W 0 RO 0 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparison Interrupt Enable Value Description 1 Enables the comparison interrupt. The ADC conversion data is used to determine if an interrupt should be generated according to the programming of the CIC and CIM fields. Disables the comparison interrupt. ADC conversion data has no effect on interrupt generation.
CIE
R/W
April 25, 2012
Bit/Field 3:2
Name CIC
Type R/W
Reset 0x0
Description Comparison Interrupt Condition This field specifies the operational region in which an interrupt is generated when the ADC conversion data is compared against the values of COMP0 and COMP1. The COMP0 and COMP1 fields are defined in the ADCDCCMPx registers. Value Description 0x0 0x1 0x2 0x3 Low Band ADC Data < COMP0 COMP1 Mid Band COMP0 ADC Data < COMP1 reserved High Band COMP0 < COMP1 ADC Data
1:0
CIM
R/W
0x0
Comparison Interrupt Mode This field specifies the mode by which the interrupt comparison is made. Value Description 0x0 Always This mode generates an interrupt every time the ADC conversion data falls within the selected operational region. 0x1 Once This mode generates an interrupt the first time that the ADC conversion data enters the selected operational region. 0x2 Hysteresis Always This mode generates an interrupt when the ADC conversion data falls within the selected operational region and continues to generate the interrupt until the hysteresis condition is cleared by entering the opposite operational region. 0x3 Hysteresis Once This mode generates an interrupt the first time that the ADC conversion data falls within the selected operational region. No additional interrupts are generated until the hysteresis condition is cleared by entering the opposite operational region.
855
Register 46: ADC Digital Comparator Range 0 (ADCDCCMP0), offset 0xE40 Register 47: ADC Digital Comparator Range 1 (ADCDCCMP1), offset 0xE44 Register 48: ADC Digital Comparator Range 2 (ADCDCCMP2), offset 0xE48 Register 49: ADC Digital Comparator Range 3 (ADCDCCMP3), offset 0xE4C Register 50: ADC Digital Comparator Range 4 (ADCDCCMP4), offset 0xE50 Register 51: ADC Digital Comparator Range 5 (ADCDCCMP5), offset 0xE54 Register 52: ADC Digital Comparator Range 6 (ADCDCCMP6), offset 0xE58 Register 53: ADC Digital Comparator Range 7 (ADCDCCMP7), offset 0xE5C
This register defines the comparison values that are used to determine if the ADC conversion data falls in the appropriate operating region. Note: The value in the COMP1 field must be greater than or equal to the value in the COMP0 field or unexpected results can occur.
ADC Digital Comparator Range n (ADCDCCMPn)

ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xE40 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 COMP1 RO 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 R/W 0 7 R/W 0 6 COMP0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 21 20 19 18 17 16
Bit/Field 31:28
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Compare 1 The value in this field is compared against the ADC conversion data. The result of the comparison is used to determine if the data lies within the high-band region. Note that the value of COMP1 must be greater than or equal to the value of COMP0.
27:16
COMP1
R/W
0x000
15:12
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Compare 0 The value in this field is compared against the ADC conversion data. The result of the comparison is used to determine if the data lies within the low-band region.
11:0
COMP0
R/W
0x000
April 25, 2012
Register 54: ADC Peripheral Properties (ADCPP), offset 0xFC0

The ADCPP register provides information regarding the properties of the ADC module.
ADC Peripheral Properties (ADCPP)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xFC0 Type RO, reset 0x00B0.20C7
31 30 29 28 27 26 25 24 23 TS RO 0 10 RO 0 9 RO 0 8 RO 1 7 CH RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 RO 1 RO 0 RO 0 RO 0 RO 1 RO 0 6 RO 1 5 22 21 20 RSL RO 1 4 RO 0 3 RO 0 2 MSR RO 1 RO 1 RO 0 1 19 18 17 TYPE RO 0 0 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 DC Type Reset RO 0 RO 0 RO 1 RO 0 12 RO 0 11
Bit/Field 31:24
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Temperature Sensor Value Description 1 0 The ADC module has a temperature sensor. The ADC module does not have a temperature sensor.
23
TS
RO
0x1
This field provides the similar information as the legacy DC1 register TEMPSNS bit. 22:18 RSL RO 0xC Resolution This field specifies the maximum number of binary bits used to represent the converted sample. The field is encoded as a binary value, in the range of 0 to 32 bits. 17:16 TYPE RO 0x0 ADC Architecture Value 0x0 Description SAR
0x1 - 0x3 Reserved
15:10
DC
RO
0x8
Digital Comparator Count This field specifies the number of ADC digital comparators available to the converter. The field is encoded as a binary value, in the range of 0 to 63. This field provides similar information to the legacy DC9 register ADCnDCn bits.
857
Bit/Field 9:4
Name CH
Type RO
Reset 0xC
Description ADC Channel Count This field specifies the number of ADC input channels available to the converter. This field is encoded as a binary value, in the range of 0 to 63. This field provides similar information to the legacy DC3 and DC8 register ADCnAINn bits.
3:0
MSR
RO
0x7
Maximum ADC Sample Rate This field specifies the maximum number of ADC conversions per second. The MSR field is encoded as follows: Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Description Reserved 125 ksps Reserved 250 ksps Reserved 500 ksps Reserved 1 Msps
0x8 - 0xF Reserved
April 25, 2012
Register 55: ADC Peripheral Configuration (ADCPC), offset 0xFC4

The ADCPC register provides information regarding the configuration of the peripheral.
ADC Peripheral Configuration (ADCPC)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xFC4 Type R/W, reset 0x0000.0007
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 1 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 SR R/W 1 R/W 1 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset
Description
0x0000.0000 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 0x7 ADC Sample Rate This field specifies the number of ADC conversions per second and is used in Run, Sleep, and Deep-sleep modes. The field encoding is based on the legacy RCGC0 register encoding. The programmed sample rate cannot exceed the maximum sample rate specified by the MSR field in the ADCPP register. The SR field is encoded as follows: Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Description Reserved 125 ksps Reserved 250 ksps Reserved 500 ksps Reserved 1 Msps
3:0
SR
R/W
0x8 - 0xF Reserved
859
Register 56: ADC Clock Configuration (ADCCC), offset 0xFC8

The ADCCC register controls the clock source for the ADC module.
ADC Clock Configuration (ADCCC)
ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000 Offset 0xFC8 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 CS R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. ADC Clock Source The following table specifies the clock source that generates the ADC clock input, see Figure 5-5 on page 218. Value 0x0 Description Either the 16-MHz system clock (if the PLL bypass is in effect) or the 16 MHz clock derived from PLL 25 (default). Note that when the PLL is bypassed, the system clock must be at least 16 MHz. 0x1 PIOSC The PIOSC provides a 16-MHz clock source for the ADC. If the PIOSC is used as the clock source, the ADC module can continue to operate in Deep-Sleep mode. 0x2 - 0xF Reserved
3:0
CS
R/W
April 25, 2012
14
Universal Asynchronous Receivers/Transmitters (UARTs)

The Stellaris LM4F120H5QR controller includes eight Universal Asynchronous Receiver/Transmitter (UART) with the following features: Programmable baud-rate generator allowing speeds up to 5 Mbps for regular speed (divide by 16) and 10 Mbps for high speed (divide by 8) Separate 16x8 transmit (TX) and receive (RX) FIFOs to reduce CPU interrupt service loading Programmable FIFO length, including 1-byte deep operation providing conventional double-buffered interface FIFO trigger levels of 1/8, 1/4, 1/2, 3/4, and 7/8 Standard asynchronous communication bits for start, stop, and parity Line-break generation and detection Fully programmable serial interface characteristics 5, 6, 7, or 8 data bits Even, odd, stick, or no-parity bit generation/detection 1 or 2 stop bit generation IrDA serial-IR (SIR) encoder/decoder providing Programmable use of IrDA Serial Infrared (SIR) or UART input/output Support of IrDA SIR encoder/decoder functions for data rates up to 115.2 Kbps half-duplex Support of normal 3/16 and low-power (1.41-2.23 s) bit durations Programmable internal clock generator enabling division of reference clock by 1 to 256 for low-power mode bit duration Support for communication with ISO 7816 smart cards Modem flow control (on UART1) LIN protocol support EIA-485 9-bit support Standard FIFO-level and End-of-Transmission interrupts Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive
861
Receive single request asserted when data is in the FIFO; burst request asserted at programmed FIFO level Transmit single request asserted when there is space in the FIFO; burst request asserted at programmed FIFO level
14.1
Block Diagram
Figure 14-1. UART Module Block Diagram

PIOSC System Clock UARTCTL Clock Control Baud Clock
DMA Request
DMA Control UARTDMACTL
Interrupt
Interrupt Control
TxFIFO 16 x 8
Identification Registers UARTPCellID0 UARTPCellID1 UARTPCellID2 UARTPCellID3 UARTPeriphID0 UARTPeriphID1 UARTPeriphID2 UARTPeriphID3 UARTPeriphID4 UARTPeriphID5 UARTPeriphID6 UARTPeriphID7
UARTIFLS UARTIM UARTMIS UARTRIS UARTICR
. . .
Transmitter
(with SIR Transmit Encoder)
UnTx
Baud Rate Generator UARTDR UARTIBRD UARTFBRD Receiver

(with SIR Receive Decoder)
Control/Status UARTRSR/ECR UARTFR UARTLCRH UARTCTL UARTILPR UARTLCTL UARTLSS UARTLTIM UART9BITADDR UART9BITAMASK UARTPP RxFIFO 16 x 8
UnRx
. . .
14.2
Signal Description
The following table lists the external signals of the UART module and describes the function of each. The UART signals are alternate functions for some GPIO signals and default to be GPIO signals at reset, with the exception of the U0Rx and U0Tx pins which default to the UART function. The column in the table below titled "Pin Mux/Pin Assignment" lists the possible GPIO pin placements for these UART signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the UART function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the UART signal to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
April 25, 2012
Table 14-1. UART Signals (64LQFP)

Pin Name U0Rx U0Tx U1CTS U1RTS U1Rx U1Tx U2Rx U2Tx U3Rx U3Tx U4Rx U4Tx U5Rx U5Tx U6Rx U6Tx U7Rx U7Tx Pin Number Pin Mux / Pin Assignment 17 18 15 29 16 28 16 45 15 46 53 10 14 13 16 15 59 60 43 44 9 8 PA0 (1) PA1 (1) PC5 (8) PF1 (1) PC4 (8) PF0 (1) PC4 (2) PB0 (1) PC5 (2) PB1 (1) PD6 (1) PD7 (1) PC6 (1) PC7 (1) PC4 (1) PC5 (1) PE4 (1) PE5 (1) PD4 (1) PD5 (1) PE0 (1) PE1 (1) Pin Type I O I O I O I O I O I O I O I O I O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description UART module 0 receive. UART module 0 transmit. UART module 1 Clear To Send modem flow control input signal. UART module 1 Request to Send modem flow control output line. UART module 1 receive. UART module 1 transmit. UART module 2 receive. UART module 2 transmit. UART module 3 receive. UART module 3 transmit. UART module 4 receive. UART module 4 transmit. UART module 5 receive. UART module 5 transmit. UART module 6 receive. UART module 6 transmit. UART module 7 receive. UART module 7 transmit.
14.3
Each Stellaris UART performs the functions of parallel-to-serial and serial-to-parallel conversions. It is similar in functionality to a 16C550 UART, but is not register compatible. The UART is configured for transmit and/or receive via the TXE and RXE bits of the UART Control (UARTCTL) register (see page 887). Transmit and receive are both enabled out of reset. Before any control registers are programmed, the UART must be disabled by clearing the UARTEN bit in UARTCTL. If the UART is disabled during a TX or RX operation, the current transaction is completed prior to the UART stopping. The UART module also includes a serial IR (SIR) encoder/decoder block that can be connected to an infrared transceiver to implement an IrDA SIR physical layer. The SIR function is programmed using the UARTCTL register.
14.3.1
Transmit/Receive Logic
The transmit logic performs parallel-to-serial conversion on the data read from the transmit FIFO. The control logic outputs the serial bit stream beginning with a start bit and followed by the data bits (LSB first), parity bit, and the stop bits according to the programmed configuration in the control registers. See Figure 14-2 on page 864 for details.
863
The receive logic performs serial-to-parallel conversion on the received bit stream after a valid start pulse has been detected. Overrun, parity, frame error checking, and line-break detection are also performed, and their status accompanies the data that is written to the receive FIFO. Figure 14-2. UART Character Frame
UnTX 1 0 n Start LSB 5-8 data bits Parity bit if enabled MSB 1-2 stop bits
14.3.2
Baud-Rate Generation
The baud-rate divisor is a 22-bit number consisting of a 16-bit integer and a 6-bit fractional part. The number formed by these two values is used by the baud-rate generator to determine the bit period. Having a fractional baud-rate divisor allows the UART to generate all the standard baud rates. The 16-bit integer is loaded through the UART Integer Baud-Rate Divisor (UARTIBRD) register (see page 883) and the 6-bit fractional part is loaded with the UART Fractional Baud-Rate Divisor (UARTFBRD) register (see page 884). The baud-rate divisor (BRD) has the following relationship to the system clock (where BRDI is the integer part of the BRD and BRDF is the fractional part, separated by a decimal place.) BRD = BRDI + BRDF = UARTSysClk / (ClkDiv * Baud Rate) where UARTSysClk is the system clock connected to the UART, and ClkDiv is either 16 (if HSE in UARTCTL is clear) or 8 (if HSE is set). By default, this will be the main system clock described in Clock Control on page 215. Alternatively, the UART may be clocked from the internal precision oscillator (PIOSC), independent of the system clock selection. This will allow the UART clock to be programmed indpendently of the system clock PLL settings. See the UARTCC register for more details. The 6-bit fractional number (that is to be loaded into the DIVFRAC bit field in the UARTFBRD register) can be calculated by taking the fractional part of the baud-rate divisor, multiplying it by 64, and adding 0.5 to account for rounding errors: UARTFBRD[DIVFRAC] = integer(BRDF * 64 + 0.5) The UART generates an internal baud-rate reference clock at 8x or 16x the baud-rate (referred to as Baud8 and Baud16, depending on the setting of the HSE bit (bit 5) in UARTCTL). This reference clock is divided by 8 or 16 to generate the transmit clock, and is used for error detection during receive operations. Note that the state of the HSE bit has no effect on clock generation in ISO 7816 smart card mode (when the SMART bit in the UARTCTL register is set). Along with the UART Line Control, High Byte (UARTLCRH) register (see page 885), the UARTIBRD and UARTFBRD registers form an internal 30-bit register. This internal register is only updated when a write operation to UARTLCRH is performed, so any changes to the baud-rate divisor must be followed by a write to the UARTLCRH register for the changes to take effect. To update the baud-rate registers, there are four possible sequences: UARTIBRD write, UARTFBRD write, and UARTLCRH write UARTFBRD write, UARTIBRD write, and UARTLCRH write UARTIBRD write and UARTLCRH write
April 25, 2012
UARTFBRD write and UARTLCRH write
14.3.3
Data Transmission
Data received or transmitted is stored in two 16-byte FIFOs, though the receive FIFO has an extra four bits per character for status information. For transmission, data is written into the transmit FIFO. If the UART is enabled, it causes a data frame to start transmitting with the parameters indicated in the UARTLCRH register. Data continues to be transmitted until there is no data left in the transmit FIFO. The BUSY bit in the UART Flag (UARTFR) register (see page 880) is asserted as soon as data is written to the transmit FIFO (that is, if the FIFO is non-empty) and remains asserted while data is being transmitted. The BUSY bit is negated only when the transmit FIFO is empty, and the last character has been transmitted from the shift register, including the stop bits. The UART can indicate that it is busy even though the UART may no longer be enabled. When the receiver is idle (the UnRx signal is continuously 1), and the data input goes Low (a start bit has been received), the receive counter begins running and data is sampled on the eighth cycle of Baud16 or fourth cycle of Baud8 depending on the setting of the HSE bit (bit 5) in UARTCTL (described in Transmit/Receive Logic on page 863). The start bit is valid and recognized if the UnRx signal is still low on the eighth cycle of Baud16 (HSE clear) or the fourth cycle of Baud 8 (HSE set), otherwise it is ignored. After a valid start bit is detected, successive data bits are sampled on every 16th cycle of Baud16 or 8th cycle of Baud8 (that is, one bit period later) according to the programmed length of the data characters and value of the HSE bit in UARTCTL. The parity bit is then checked if parity mode is enabled. Data length and parity are defined in the UARTLCRH register. Lastly, a valid stop bit is confirmed if the UnRx signal is High, otherwise a framing error has occurred. When a full word is received, the data is stored in the receive FIFO along with any error bits associated with that word.
14.3.4
Serial IR (SIR)
The UART peripheral includes an IrDA serial-IR (SIR) encoder/decoder block. The IrDA SIR block provides functionality that converts between an asynchronous UART data stream and a half-duplex serial SIR interface. No analog processing is performed on-chip. The role of the SIR block is to provide a digital encoded output and decoded input to the UART. When enabled, the SIR block uses the UnTx and UnRx pins for the SIR protocol. These signals should be connected to an infrared transceiver to implement an IrDA SIR physical layer link. The SIR block can receive and transmit, but it is only half-duplex so it cannot do both at the same time. Transmission must be stopped before data can be received. The IrDA SIR physical layer specifies a minimum 10-ms delay between transmission and reception.The SIR block has two modes of operation: In normal IrDA mode, a zero logic level is transmitted as a high pulse of 3/16th duration of the selected baud rate bit period on the output pin, while logic one levels are transmitted as a static LOW signal. These levels control the driver of an infrared transmitter, sending a pulse of light for each zero. On the reception side, the incoming light pulses energize the photo transistor base of the receiver, pulling its output LOW and driving the UART input pin LOW. In low-power IrDA mode, the width of the transmitted infrared pulse is set to three times the period of the internally generated IrLPBaud16 signal (1.63 s, assuming a nominal 1.8432 MHz frequency) by changing the appropriate bit in the UARTCR register. See page 882 for more information on IrDA low-power pulse-duration configuration. Figure 14-3 on page 866 shows the UART transmit and receive signals, with and without IrDA modulation.
865
Figure 14-3. IrDA Data Modulation

Start bit Data bits 0 Stop bit 0 1 1 0 1
UnTx UnTx with IrDA
Bit period
3 16 Bit period
UnRx with IrDA
UnRx
0 Start
0 Data bits
1 Stop
In both normal and low-power IrDA modes: During transmission, the UART data bit is used as the base for encoding During reception, the decoded bits are transferred to the UART receive logic The IrDA SIR physical layer specifies a half-duplex communication link, with a minimum 10-ms delay between transmission and reception. This delay must be generated by software because it is not automatically supported by the UART. The delay is required because the infrared receiver electronics might become biased or even saturated from the optical power coupled from the adjacent transmitter LED. This delay is known as latency or receiver setup time.
14.3.5
ISO 7816 Support

The UART offers basic support to allow communication with an ISO 7816 smartcard. When bit 3 (SMART) of the UARTCTL register is set, the UnTx signal is used as a bit clock, and the UnRx signal is used as the half-duplex communication line connected to the smartcard. A GPIO signal can be used to generate the reset signal to the smartcard. The remaining smartcard signals should be provided by the system design. The maximum clock rate in this mode is system clock / 16. When using ISO 7816 mode, the UARTLCRH register must be set to transmit 8-bit words (WLEN bits 6:5 configured to 0x3) with EVEN parity (PEN set and EPS set). In this mode, the UART automatically uses 2 stop bits, and the STP2 bit of the UARTLCRH register is ignored. If a parity error is detected during transmission, UnRx is pulled Low during the second stop bit. In this case, the UART aborts the transmission, flushes the transmit FIFO and discards any data it contains, and raises a parity error interrupt, allowing software to detect the problem and initiate retransmission of the affected data. Note that the UART does not support automatic retransmission in this case.
14.3.6
Modem Handshake Support

This section describes how to configure and use the modem flow control signals for UART1 when connected as a DTE (data terminal equipment) or as a DCE (data communications equipment). In general, a modem is a DCE and a computing device that connects to a modem is the DTE.
14.3.6.1
Signaling
The status signals provided by UART1 differ based on whether the UART is used as a DTE or DCE. When used as a DTE, the modem flow control signals are defined as:
April 25, 2012
U1CTS is Clear To Send U1RTS is Request To Send When used as a DCE, the the modem flow control signals are defined as: U1CTS is Request To Send U1RTS is Clear To Send
14.3.6.2
Flow Control
Flow control can be accomplished by either hardware or software. The following sections describe the different methods. Hardware Flow Control (RTS/CTS) Hardware flow control between two devices is accomplished by connecting the U1RTS output to the Clear-To-Send input on the receiving device, and connecting the Request-To-Send output on the receiving device to the U1CTS input. The U1CTS input controls the transmitter. The transmitter may only transmit data when the U1CTS input is asserted. The U1RTS output signal indicates the state of the receive FIFO. U1CTS remains asserted until the preprogrammed watermark level is reached, indicating that the Receive FIFO has no space to store additional characters. The UARTCTL register bits 15 (CTSEN) and 14 (RTSEN) specify the flow control mode as shown in Table 14-2 on page 867. Table 14-2. Flow Control Mode
CTSEN 1 1 0 0 RTSEN 1 0 1 0 Description RTS and CTS flow control enabled Only CTS flow control enabled Only RTS flow control enabled Both RTS and CTS flow control disabled
Note that when RTSEN is 1, software cannot modify the U1RTS output value through the UARTCTL register Request to Send (RTS) bit, and the status of the RTS bit should be ignored. Software Flow Control (Modem Status Interrupts) Software flow control between two devices is accomplished by using interrupts to indicate the status of the UART. Interrupts may be generated for the U1CTS signal using bit 3 of the UARTIM register. The raw and masked interrupt status may be checked using the UARTRIS and UARTMIS register. These interrupts may be cleared using the UARTICR register.
14.3.7
LIN Support
The UART module offers hardware support for the LIN protocol as either a master or a slave. The LIN mode is enabled by setting the LIN bit in the UARTCTL register. A LIN message is identified by the use of a Sync Break at the beginning of the message. The Sync Break is a transmission of a series of 0s. The Sync Break is followed by the Sync data field (0x55). Figure 14-4 on page 868 illustrates the structure of a LIN message.
867
Figure 14-4. LIN Message
Message Frame Header

Synch Break Synch Field Ident Field Data Field(s)
Response
Data Field Checksum Field
In-Frame Response
Interbyte Space
The UART should be configured as followed to operate in LIN mode: 1. Configure the UART for 1 start bit, 8 data bits, no parity, and 1 stop bit. Enable the Transmit FIFO. 2. Set the LIN bit in the UARTCTL register. When preparing to send a LIN message, the TXFIFO should contain the Sync data (0x55) at FIFO location 0 and the Identifier data at location 1, followed by the data to be transmitted, and with the checksum in the final FIFO entry.
14.3.7.1
LIN Master
The UART is enabled to be the LIN master by setting the MASTER bit in the UARTLCTL register. The length of the Sync Break is programmable using the BLEN field in the UARTLCTL register and can be 13-16 bits (baud clock cycles).
14.3.7.2
LIN Slave
The LIN UART slave is required to adjust its baud rate to that of the LIN master. In slave mode, the LIN UART recognizes the Sync Break, which must be at least 13 bits in duration. A timer is provided to capture timing data on the 1st and 5th falling edges of the Sync field so that the baud rate can be adjusted to match the master. After detecting a Sync Break, the UART waits for the synchronization field. The first falling edge generates an interrupt using the LME1RIS bit in the UARTRIS register, and the timer value is captured and stored in the UARTLSS register (T1). On the fifth falling edge, a second interrupt is generated using the LME5RIS bit in the UARTRIS register, and the timer value is captured again (T2). The actual baud rate can be calculated using (T2-T1)/8, and the local baud rate should be adjusted as needed. Figure 14-5 on page 869 illustrates the synchronization field.
April 25, 2012
Figure 14-5. LIN Synchronization Field

Sync Break Synch Field
10
11
12
13 0 1 2 Edge 1 3 8 Tbit 4 5 6 Edge 5 7 8
Sync Break Detect
14.3.8
9-Bit UART Mode

The UART provides a 9-bit mode that is enabled with the 9BITEN bit in the UART9BITADDR register. This feature is useful in a multi-drop configuration of the UART where a single master connected to multiple slaves can communicate with a particular slave through its address or set of addresses along with a qualifier for an address byte. All the slaves check for the address qualifier in the place of the parity bit and, if set, then compare the byte received with the preprogrammed address. If the address matches, then it receives or sends further data. If the address does not match, it drops the address byte and any subsequent data bytes. If the UART is in 9-bit mode, then the receiver operates with no parity mode. The address can be predefined to match with the received byte and it can be configured with the UART9BITADDR register. The matching can be extended to a set of addresses using the address mask in the UART9BITAMASK register. By default, the UART9BITAMASK is 0xFF, meaning that only the specified address is matched. When not finding a match, the rest of the data bytes with the 9th bit cleared are dropped. If a match is found, then an interrupt is generated to the NVIC for further action. The subsequent data bytes with the cleared 9th bit are stored in the FIFO. Software can mask this interrupt in case DMA and/or FIFO operations are enabled for this instance and processor intervention is not required. All the send transactions with 9-bit mode are data bytes and the 9th bit is cleared. Software can override the 9th bit to be set (to indicate address) by overriding the parity settings to sticky parity with odd parity enabled for a particular byte. To match the transmission time with correct parity settings, the address byte can be transmitted as a single then a burst transfer. The Transmit FIFO does not hold the address/data bit, hence software should take care of enabling the address bit appropriately.
14.3.9
FIFO Operation
The UART has two 16x8 FIFOs; one for transmit and one for receive. Both FIFOs are accessed via the UART Data (UARTDR) register (see page 875). Read operations of the UARTDR register return a 12-bit value consisting of 8 data bits and 4 error flags while write operations place 8-bit data in the transmit FIFO. Out of reset, both FIFOs are disabled and act as 1-byte-deep holding registers. The FIFOs are enabled by setting the FEN bit in UARTLCRH (page 885). FIFO status can be monitored via the UART Flag (UARTFR) register (see page 880) and the UART Receive Status (UARTRSR) register. Hardware monitors empty, full and overrun conditions. The UARTFR register contains empty and full flags (TXFE, TXFF, RXFE, and RXFF bits), and the UARTRSR register shows overrun status via the OE bit. If the FIFOs are disabled, the empty and full flags are set according to the status of the 1-byte-deep holding registers. The trigger points at which the FIFOs generate interrupts is controlled via the UART Interrupt FIFO Level Select (UARTIFLS) register (see page 891). Both FIFOs can be individually configured to trigger interrupts at different levels. Available configurations include , , , , and . For example,
869
if the option is selected for the receive FIFO, the UART generates a receive interrupt after 4 data bytes are received. Out of reset, both FIFOs are configured to trigger an interrupt at the mark.
14.3.10
Interrupts
The UART can generate interrupts when the following conditions are observed: Overrun Error Break Error Parity Error Framing Error Receive Timeout Transmit (when condition defined in the TXIFLSEL bit in the UARTIFLS register is met, or if the EOT bit in UARTCTL is set, when the last bit of all transmitted data leaves the serializer) Receive (when condition defined in the RXIFLSEL bit in the UARTIFLS register is met) All of the interrupt events are ORed together before being sent to the interrupt controller, so the UART can only generate a single interrupt request to the controller at any given time. Software can service multiple interrupt events in a single interrupt service routine by reading the UART Masked Interrupt Status (UARTMIS) register (see page 899). The interrupt events that can trigger a controller-level interrupt are defined in the UART Interrupt Mask (UARTIM) register (see page 893) by setting the corresponding IM bits. If interrupts are not used, the raw interrupt status is always visible via the UART Raw Interrupt Status (UARTRIS) register (see page 896). Interrupts are always cleared (for both the UARTMIS and UARTRIS registers) by writing a 1 to the corresponding bit in the UART Interrupt Clear (UARTICR) register (see page 902). The receive timeout interrupt is asserted when the receive FIFO is not empty, and no further data is received over a 32-bit period. The receive timeout interrupt is cleared either when the FIFO becomes empty through reading all the data (or by reading the holding register), or when a 1 is written to the corresponding bit in the UARTICR register. The receive interrupt changes state when one of the following events occurs: If the FIFOs are enabled and the receive FIFO reaches the programmed trigger level, the RXRIS bit is set. The receive interrupt is cleared by reading data from the receive FIFO until it becomes less than the trigger level, or by clearing the interrupt by writing a 1 to the RXIC bit. If the FIFOs are disabled (have a depth of one location) and data is received thereby filling the location, the RXRIS bit is set. The receive interrupt is cleared by performing a single read of the receive FIFO, or by clearing the interrupt by writing a 1 to the RXIC bit. The transmit interrupt changes state when one of the following events occurs: If the FIFOs are enabled and the transmit FIFO reaches the programmed trigger level, the TXRIS bit is set. The transmit interrupt is cleared by writing data to the transmit FIFO until it becomes greater than the trigger level, or by clearing the interrupt by writing a 1 to the TXIC bit.
April 25, 2012
If the FIFOs are disabled (have a depth of one location) and there is no data present in the transmitters single location, the TXRIS bit is set. It is cleared by performing a single write to the transmit FIFO, or by clearing the interrupt by writing a 1 to the TXIC bit.
14.3.11
Loopback Operation
The UART can be placed into an internal loopback mode for diagnostic or debug work by setting the LBE bit in the UARTCTL register (see page 887). In loopback mode, data transmitted on the UnTx output is received on the UnRx input. Note that the LBE bit should be set before the UART is enabled.
14.3.12
DMA Operation
The UART provides an interface to the DMA controller with separate channels for transmit and receive. The DMA operation of the UART is enabled through the UART DMA Control (UARTDMACTL) register. When DMA operation is enabled, the UART asserts a DMA request on the receive or transmit channel when the associated FIFO can transfer data. For the receive channel, a single transfer request is asserted whenever any data is in the receive FIFO. A burst transfer request is asserted whenever the amount of data in the receive FIFO is at or above the FIFO trigger level configured in the UARTIFLS register. For the transmit channel, a single transfer request is asserted whenever there is at least one empty location in the transmit FIFO. The burst request is asserted whenever the transmit FIFO contains fewer characters than the FIFO trigger level. The single and burst DMA transfer requests are handled automatically by the DMA controller depending on how the DMA channel is configured. To enable DMA operation for the receive channel, set the RXDMAE bit of the DMA Control (UARTDMACTL) register. To enable DMA operation for the transmit channel, set the TXDMAE bit of the UARTDMACTL register. The UART can also be configured to stop using DMA for the receive channel if a receive error occurs. If the DMAERR bit of the UARTDMACR register is set and a receive error occurs, the DMA receive requests are automatically disabled. This error condition can be cleared by clearing the appropriate UART error interrupt. If DMA is enabled, then the DMA controller triggers an interrupt when a transfer is complete. The interrupt occurs on the UART interrupt vector. Therefore, if interrupts are used for UART operation and DMA is enabled, the UART interrupt handler must be designed to handle the DMA completion interrupt. See Micro Direct Memory Access (DMA) on page 568 for more details about programming the DMA controller.
14.4

To enable and initialize the UART, the following steps are necessary: 1. Enable the UART module using the RCGCUART register (see page 316). 2. Enable the clock to the appropriate GPIO module via the RCGCGPIO register (see page 312). To find out which GPIO port to enable, refer to Table 21-5 on page 1152. 3. Set the GPIO AFSEL bits for the appropriate pins (see page 653). To determine which GPIOs to configure, see Table 21-4 on page 1148. 4. Configure the GPIO current level and/or slew rate as specified for the mode selected (see page 655 and page 663).
871
5. Configure the PMCn fields in the GPIOPCTL register to assign the UART signals to the appropriate pins (see page 670 and Table 21-5 on page 1152). To use the UART, the peripheral clock must be enabled by setting the appropriate bit in the RCGCUART register (page 316). In addition, the clock to the appropriate GPIO module must be enabled via the RCGCGPIO register (page 312) in the System Control module. To find out which GPIO port to enable, refer to Table 21-5 on page 1152. This section discusses the steps that are required to use a UART module. For this example, the UART clock is assumed to be 20 MHz, and the desired UART configuration is: 115200 baud rate Data length of 8 bits One stop bit No parity FIFOs disabled No interrupts The first thing to consider when programming the UART is the baud-rate divisor (BRD), because the UARTIBRD and UARTFBRD registers must be written before the UARTLCRH register. Using the equation described in Baud-Rate Generation on page 864, the BRD can be calculated: BRD = 20,000,000 / (16 * 115,200) = 10.8507 which means that the DIVINT field of the UARTIBRD register (see page 883) should be set to 10 decimal or 0xA. The value to be loaded into the UARTFBRD register (see page 884) is calculated by the equation: UARTFBRD[DIVFRAC] = integer(0.8507 * 64 + 0.5) = 54 With the BRD values in hand, the UART configuration is written to the module in the following order: 1. Disable the UART by clearing the UARTEN bit in the UARTCTL register. 2. Write the integer portion of the BRD to the UARTIBRD register. 3. Write the fractional portion of the BRD to the UARTFBRD register. 4. Write the desired serial parameters to the UARTLCRH register (in this case, a value of 0x0000.0060). 5. Configure the UART clock source by writing to the UARTCC register. 6. Optionally, configure the DMA channel (see Micro Direct Memory Access (DMA) on page 568) and enable the DMA option(s) in the UARTDMACTL register. 7. Enable the UART by setting the UARTEN bit in the UARTCTL register.
14.5
Register Map
Table 14-3 on page 873 lists the UART registers. The offset listed is a hexadecimal increment to the registers address, relative to that UARTs base address:
April 25, 2012
UART0: 0x4000.C000 UART1: 0x4000.D000 UART2: 0x4000.E000 UART3: 0x4000.F000 UART4: 0x4001.0000 UART5: 0x4001.1000 UART6: 0x4001.2000 UART7: 0x4001.3000
Note that the UART module clock must be enabled before the registers can be programmed (see page 316). There must be a delay of 3 system clocks after the UART module clock is enabled before any UART module registers are accessed. Note: The UART must be disabled (see the UARTEN bit in the UARTCTL register on page 887) before any of the control registers are reprogrammed. When the UART is disabled during a TX or RX operation, the current transaction is completed prior to the UART stopping.
Table 14-3. UART Register Map

Offset 0x000 0x004 0x018 0x020 0x024 0x028 0x02C 0x030 0x034 0x038 0x03C 0x040 0x044 0x048 0x090 0x094 0x098 0x0A4 0x0A8 0xFC0 0xFC8 Name UARTDR UARTRSR/UARTECR UARTFR UARTILPR UARTIBRD UARTFBRD UARTLCRH UARTCTL UARTIFLS UARTIM UARTRIS UARTMIS UARTICR UARTDMACTL UARTLCTL UARTLSS UARTLTIM UART9BITADDR UART9BITAMASK UARTPP UARTCC Type R/W R/W RO R/W R/W R/W R/W R/W R/W R/W RO RO W1C R/W R/W RO RO R/W R/W RO R/W Reset 0x0000.0000 0x0000.0000 0x0000.0090 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0300 0x0000.0012 0x0000.0000 0x0000.000F 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.00FF 0x0000.0003 0x0000.0000 Description UART Data UART Receive Status/Error Clear UART Flag UART IrDA Low-Power Register UART Integer Baud-Rate Divisor UART Fractional Baud-Rate Divisor UART Line Control UART Control UART Interrupt FIFO Level Select UART Interrupt Mask UART Raw Interrupt Status UART Masked Interrupt Status UART Interrupt Clear UART DMA Control UART LIN Control UART LIN Snap Shot UART LIN Timer UART 9-Bit Self Address UART 9-Bit Self Address Mask UART Peripheral Properties UART Clock Configuration See page 875 877 880 882 883 884 885 887 891 893 896 899 902 904 905 906 907 908 909 910 911
873
Table 14-3. UART Register Map (continued)

Offset 0xFD0 0xFD4 0xFD8 0xFDC 0xFE0 0xFE4 0xFE8 0xFEC 0xFF0 0xFF4 0xFF8 0xFFC Name UARTPeriphID4 UARTPeriphID5 UARTPeriphID6 UARTPeriphID7 UARTPeriphID0 UARTPeriphID1 UARTPeriphID2 UARTPeriphID3 UARTPCellID0 UARTPCellID1 UARTPCellID2 UARTPCellID3 Type RO RO RO RO RO RO RO RO RO RO RO RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0060 0x0000.0000 0x0000.0018 0x0000.0001 0x0000.000D 0x0000.00F0 0x0000.0005 0x0000.00B1 Description UART Peripheral Identification 4 UART Peripheral Identification 5 UART Peripheral Identification 6 UART Peripheral Identification 7 UART Peripheral Identification 0 UART Peripheral Identification 1 UART Peripheral Identification 2 UART Peripheral Identification 3 UART PrimeCell Identification 0 UART PrimeCell Identification 1 UART PrimeCell Identification 2 UART PrimeCell Identification 3 See page 912 913 914 915 916 917 918 919 920 921 922 923
14.6
The remainder of this section lists and describes the UART registers, in numerical order by address offset.
April 25, 2012
Register 1: UART Data (UARTDR), offset 0x000

Important: This register is read-sensitive. See the register description for details. This register is the data register (the interface to the FIFOs). For transmitted data, if the FIFO is enabled, data written to this location is pushed onto the transmit FIFO. If the FIFO is disabled, data is stored in the transmitter holding register (the bottom word of the transmit FIFO). A write to this register initiates a transmission from the UART. For received data, if the FIFO is enabled, the data byte and the 4-bit status (break, frame, parity, and overrun) is pushed onto the 12-bit wide receive FIFO. If the FIFO is disabled, the data byte and status are stored in the receiving holding register (the bottom word of the receive FIFO). The received data can be retrieved by reading this register.
UART Data (UARTDR)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 OE RO 0 RO 0 RO 0 10 BE RO 0 RO 0 9 PE RO 0 RO 0 8 FE RO 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 DATA R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:12
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Overrun Error Value Description 1 0 New data was received when the FIFO was full, resulting in data loss. No data has been lost due to a FIFO overrun.
11
OE
RO
875
Bit/Field 10
Name BE
Type RO
Reset 0
Description UART Break Error Value Description 1 A break condition has been detected, indicating that the receive data input was held Low for longer than a full-word transmission time (defined as start, data, parity, and stop bits). No break condition has occurred
In FIFO mode, this error is associated with the character at the top of the FIFO. When a break occurs, only one 0 character is loaded into the FIFO. The next character is only enabled after the received data input goes to a 1 (marking state), and the next valid start bit is received. 9 PE RO 0 UART Parity Error Value Description 1 0 The parity of the received data character does not match the parity defined by bits 2 and 7 of the UARTLCRH register. No parity error has occurred
In FIFO mode, this error is associated with the character at the top of the FIFO. 8 FE RO 0 UART Framing Error Value Description 1 0 The received character does not have a valid stop bit (a valid stop bit is 1). No framing error has occurred
7:0
DATA
R/W
0x00
Data Transmitted or Received Data that is to be transmitted via the UART is written to this field. When read, this field contains the data that was received by the UART.
April 25, 2012
Register 2: UART Receive Status/Error Clear (UARTRSR/UARTECR), offset 0x004

The UARTRSR/UARTECR register is the receive status register/error clear register. In addition to the UARTDR register, receive status can also be read from the UARTRSR register. If the status is read from this register, then the status information corresponds to the entry read from UARTDR prior to reading UARTRSR. The status information for overrun is set immediately when an overrun condition occurs. The UARTRSR register cannot be written. A write of any value to the UARTECR register clears the framing, parity, break, and overrun errors. All the bits are cleared on reset. Read-Only Status Register
UART Receive Status/Error Clear (UARTRSR/UARTECR)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x004 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 OE RO 0 RO 0 2 BE RO 0 RO 0 1 PE RO 0 RO 0 0 FE RO 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Overrun Error Value Description 1 0 New data was received when the FIFO was full, resulting in data loss. No data has been lost due to a FIFO overrun.
OE
RO
This bit is cleared by a write to UARTECR. The FIFO contents remain valid because no further data is written when the FIFO is full, only the contents of the shift register are overwritten. The CPU must read the data in order to empty the FIFO.
877
Bit/Field 2
Name BE
Type RO
Reset 0
Description UART Break Error Value Description 1 A break condition has been detected, indicating that the receive data input was held Low for longer than a full-word transmission time (defined as start, data, parity, and stop bits). No break condition has occurred
This bit is cleared to 0 by a write to UARTECR. In FIFO mode, this error is associated with the character at the top of the FIFO. When a break occurs, only one 0 character is loaded into the FIFO. The next character is only enabled after the receive data input goes to a 1 (marking state) and the next valid start bit is received. 1 PE RO 0 UART Parity Error Value Description 1 0 The parity of the received data character does not match the parity defined by bits 2 and 7 of the UARTLCRH register. No parity error has occurred
This bit is cleared to 0 by a write to UARTECR. 0 FE RO 0 UART Framing Error Value Description 1 0 The received character does not have a valid stop bit (a valid stop bit is 1). No framing error has occurred
This bit is cleared to 0 by a write to UARTECR. In FIFO mode, this error is associated with the character at the top of the FIFO.
Write-Only Error Clear Register

UART Receive Status/Error Clear (UARTRSR/UARTECR)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x004 Type WO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset WO 0 15 WO 0 14 WO 0 13 WO 0 12 WO 0 11 WO 0 10 WO 0 9 WO 0 8 WO 0 7 WO 0 6 WO 0 5 WO 0 4 DATA WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 WO 0 3 WO 0 2 WO 0 1 WO 0 0
reserved Type Reset WO 0 WO 0 WO 0 WO 0 WO 0
April 25, 2012
Bit/Field 31:8
Name reserved
Type WO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Error Clear A write to this register of any data clears the framing, parity, break, and overrun flags.
7:0
DATA
WO
0x00
879
Register 3: UART Flag (UARTFR), offset 0x018

The UARTFR register is the flag register. After reset, the TXFF, RXFF, and BUSY bits are 0, and TXFE and RXFE bits are 1. The CTS bit indicate the modem flow control. Note that the modem bits are only implemented on UART1 and are reserved on UART0 and UART2.
UART Flag (UARTFR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 TXFE RO 0 RO 0 RO 0 RO 1 RO 0 6 RXFF RO 0 RO 0 5 TXFF RO 0 RO 0 4 RXFE RO 1 RO 0 3 BUSY RO 0 RO 0 2 reserved RO 0 RO 0 RO 0 1 RO 0 0 CTS RO 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Transmit FIFO Empty The meaning of this bit depends on the state of the FEN bit in the UARTLCRH register. Value Description 1 If the FIFO is disabled (FEN is 0), the transmit holding register is empty. If the FIFO is enabled (FEN is 1), the transmit FIFO is empty. 0 The transmitter has data to transmit.
TXFE
RO
RXFF
RO
UART Receive FIFO Full The meaning of this bit depends on the state of the FEN bit in the UARTLCRH register. Value Description 1 If the FIFO is disabled (FEN is 0), the receive holding register is full. If the FIFO is enabled (FEN is 1), the receive FIFO is full. 0 The receiver can receive data.
April 25, 2012
Bit/Field 5
Name TXFF
Type RO
Reset 0
Description UART Transmit FIFO Full The meaning of this bit depends on the state of the FEN bit in the UARTLCRH register. Value Description 1 If the FIFO is disabled (FEN is 0), the transmit holding register is full. If the FIFO is enabled (FEN is 1), the transmit FIFO is full. 0 The transmitter is not full.
RXFE
RO
UART Receive FIFO Empty The meaning of this bit depends on the state of the FEN bit in the UARTLCRH register. Value Description 1 If the FIFO is disabled (FEN is 0), the receive holding register is empty. If the FIFO is enabled (FEN is 1), the receive FIFO is empty. 0 The receiver is not empty.
BUSY
RO
UART Busy Value Description 1 The UART is busy transmitting data. This bit remains set until the complete byte, including all stop bits, has been sent from the shift register. The UART is not busy.
This bit is set as soon as the transmit FIFO becomes non-empty (regardless of whether UART is enabled). 2:1 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clear To Send Value Description 1 0 The U1CTS signal is asserted. The U1CTS signal is not asserted.
CTS
RO
881
Register 4: UART IrDA Low-Power Register (UARTILPR), offset 0x020

The UARTILPR register stores the 8-bit low-power counter divisor value used to derive the low-power SIR pulse width clock by dividing down the system clock (SysClk). All the bits are cleared when reset. The internal IrLPBaud16 clock is generated by dividing down SysClk according to the low-power divisor value written to UARTILPR. The duration of SIR pulses generated when low-power mode is enabled is three times the period of the IrLPBaud16 clock. The low-power divisor value is calculated as follows: ILPDVSR = SysClk / FIrLPBaud16 where FIrLPBaud16 is nominally 1.8432 MHz. The divisor must be programmed such that 1.42 MHz < FIrLPBaud16 < 2.12 MHz, resulting in a low-power pulse duration of 1.412.11 s (three times the period of IrLPBaud16). The minimum frequency of IrLPBaud16 ensures that pulses less than one period of IrLPBaud16 are rejected, but pulses greater than 1.4 s are accepted as valid pulses. Note: Zero is an illegal value. Programming a zero value results in no IrLPBaud16 pulses being generated.
UART IrDA Low-Power Register (UARTILPR)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 ILPDVSR RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. IrDA Low-Power Divisor This field contains the 8-bit low-power divisor value.
7:0
ILPDVSR
R/W
0x00
April 25, 2012
Register 5: UART Integer Baud-Rate Divisor (UARTIBRD), offset 0x024

The UARTIBRD register is the integer part of the baud-rate divisor value. All the bits are cleared on reset. The minimum possible divide ratio is 1 (when UARTIBRD=0), in which case the UARTFBRD register is ignored. When changing the UARTIBRD register, the new value does not take effect until transmission/reception of the current character is complete. Any changes to the baud-rate divisor must be followed by a write to the UARTLCRH register. See Baud-Rate Generation on page 864 for configuration details.
UART Integer Baud-Rate Divisor (UARTIBRD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 DIVINT Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Integer Baud-Rate Divisor
15:0
DIVINT
R/W
0x0000
883
Register 6: UART Fractional Baud-Rate Divisor (UARTFBRD), offset 0x028

The UARTFBRD register is the fractional part of the baud-rate divisor value. All the bits are cleared on reset. When changing the UARTFBRD register, the new value does not take effect until transmission/reception of the current character is complete. Any changes to the baud-rate divisor must be followed by a write to the UARTLCRH register. See Baud-Rate Generation on page 864 for configuration details.
UART Fractional Baud-Rate Divisor (UARTFBRD)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0
DIVFRAC R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Fractional Baud-Rate Divisor
5:0
DIVFRAC
R/W
0x0
April 25, 2012
Register 7: UART Line Control (UARTLCRH), offset 0x02C

The UARTLCRH register is the line control register. Serial parameters such as data length, parity, and stop bit selection are implemented in this register. When updating the baud-rate divisor (UARTIBRD and/or UARTIFRD), the UARTLCRH register must also be written. The write strobe for the baud-rate divisor registers is tied to the UARTLCRH register.
UART Line Control (UARTLCRH)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x02C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 SPS RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 6 WLEN R/W 0 RO 0 5 RO 0 4 FEN R/W 0 RO 0 3 STP2 R/W 0 RO 0 2 EPS R/W 0 RO 0 1 PEN R/W 0 RO 0 0 BRK R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Stick Parity Select When bits 1, 2, and 7 of UARTLCRH are set, the parity bit is transmitted and checked as a 0. When bits 1 and 7 are set and 2 is cleared, the parity bit is transmitted and checked as a 1. When this bit is cleared, stick parity is disabled.
SPS
R/W
6:5
WLEN
R/W
0x0
UART Word Length The bits indicate the number of data bits transmitted or received in a frame as follows: Value Description 0x0 0x1 0x2 0x3 5 bits (default) 6 bits 7 bits 8 bits
885
Bit/Field 4
Name FEN
Type R/W
Reset 0
Description UART Enable FIFOs Value Description 1 0 The transmit and receive FIFO buffers are enabled (FIFO mode). The FIFOs are disabled (Character mode). The FIFOs become 1-byte-deep holding registers.
STP2
R/W
UART Two Stop Bits Select Value Description 1 Two stop bits are transmitted at the end of a frame. The receive logic does not check for two stop bits being received. When in 7816 smartcard mode (the SMART bit is set in the UARTCTL register), the number of stop bits is forced to 2. 0 One stop bit is transmitted at the end of a frame.
EPS
R/W
UART Even Parity Select Value Description 1 Even parity generation and checking is performed during transmission and reception, which checks for an even number of 1s in data and parity bits. Odd parity is performed, which checks for an odd number of 1s.
This bit has no effect when parity is disabled by the PEN bit. 1 PEN R/W 0 UART Parity Enable Value Description 1 0 Parity checking and generation is enabled. Parity is disabled and no parity bit is added to the data frame.
BRK
R/W
UART Send Break Value Description 1 A Low level is continually output on the UnTx signal, after completing transmission of the current character. For the proper execution of the break command, software must set this bit for at least two frames (character periods). Normal use.
April 25, 2012
Register 8: UART Control (UARTCTL), offset 0x030

The UARTCTL register is the control register. All the bits are cleared on reset except for the Transmit Enable (TXE) and Receive Enable (RXE) bits, which are set. To enable the UART module, the UARTEN bit must be set. If software requires a configuration change in the module, the UARTEN bit must be cleared before the configuration changes are written. If the UART is disabled during a transmit or receive operation, the current transaction is completed prior to the UART stopping. Note: The UARTCTL register should not be changed while the UART is enabled or else the results are unpredictable. The following sequence is recommended for making changes to the UARTCTL register. 1. Disable the UART. 2. Wait for the end of transmission or reception of the current character. 3. Flush the transmit FIFO by clearing bit 4 (FEN) in the line control register (UARTLCRH). 4. Reprogram the control register. 5. Enable the UART.
UART Control (UARTCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RXE RO 0 RO 0 R/W 1 RO 0 8 TXE R/W 1 RO 0 7 LBE R/W 0 RO 0 6 LIN R/W 0 RO 0 5 HSE R/W 0 RO 0 4 EOT R/W 0 RO 0 3 SMART R/W 0 RO 0 2 SIRLP R/W 0 RO 0 1 SIREN R/W 0 RO 0 0 UARTEN R/W 0
Bit/Field 31:10
Name reserved
Type RO
Reset 0x0000
887
Bit/Field 9
Name RXE
Type R/W
Reset 1
Description UART Receive Enable Value Description 1 0 The receive section of the UART is enabled. The receive section of the UART is disabled.
If the UART is disabled in the middle of a receive, it completes the current character before stopping. Note: 8 TXE R/W 1 To enable reception, the UARTEN bit must also be set.
UART Transmit Enable Value Description 1 0 The transmit section of the UART is enabled. The transmit section of the UART is disabled.
If the UART is disabled in the middle of a transmission, it completes the current character before stopping. Note: 7 LBE R/W 0 To enable transmission, the UARTEN bit must also be set.
UART Loop Back Enable Value Description 1 0 The UnTx path is fed through the UnRx path. Normal operation.
LIN
R/W
LIN Mode Enable Value Description 1 0 The UART operates in LIN mode. Normal operation.
HSE
R/W
High-Speed Enable Value Description 0 1 Note: The UART is clocked using the system clock divided by 16. The UART is clocked using the system clock divided by 8. System clock used is also dependent on the baud-rate divisor configuration (see page 883) and page 884). The state of this bit has no effect on clock generation in ISO 7816 smart card mode (the SMART bit is set).
April 25, 2012
Bit/Field 4
Name EOT
Type R/W
Reset 0
Description End of Transmission This bit determines the behavior of the TXRIS bit in the UARTRIS register. Value Description 1 0 The TXRIS bit is set only after all transmitted data, including stop bits, have cleared the serializer. The TXRIS bit is set when the transmit FIFO condition specified in UARTIFLS is met.
SMART
R/W
ISO 7816 Smart Card Support Value Description 1 0 The UART operates in Smart Card mode. Normal operation.
The application must ensure that it sets 8-bit word length (WLEN set to 0x3) and even parity (PEN set to 1, EPS set to 1, SPS set to 0) in UARTLCRH when using ISO 7816 mode. In this mode, the value of the STP2 bit in UARTLCRH is ignored and the number of stop bits is forced to 2. Note that the UART does not support automatic retransmission on parity errors. If a parity error is detected on transmission, all further transmit operations are aborted and software must handle retransmission of the affected byte or message. 2 SIRLP R/W 0 UART SIR Low-Power Mode This bit selects the IrDA encoding mode. Value Description 1 The UART operates in SIR Low-Power mode. Low-level bits are transmitted with a pulse width which is 3 times the period of the IrLPBaud16 input signal, regardless of the selected bit rate. Low-level bits are transmitted as an active High pulse with a width of 3/16th of the bit period.
Setting this bit uses less power, but might reduce transmission distances. See page 882 for more information. 1 SIREN R/W 0 UART SIR Enable Value Description 1 0 The IrDA SIR block is enabled, and the UART will transmit and receive data using SIR protocol. Normal operation.
889
Bit/Field 0
Name UARTEN
Type R/W
Reset 0
Description UART Enable Value Description 1 0 The UART is enabled. The UART is disabled.
If the UART is disabled in the middle of transmission or reception, it completes the current character before stopping.
April 25, 2012
Register 9: UART Interrupt FIFO Level Select (UARTIFLS), offset 0x034

The UARTIFLS register is the interrupt FIFO level select register. You can use this register to define the FIFO level at which the TXRIS and RXRIS bits in the UARTRIS register are triggered. The interrupts are generated based on a transition through a level rather than being based on the level. That is, the interrupts are generated when the fill level progresses through the trigger level. For example, if the receive trigger level is set to the half-way mark, the interrupt is triggered as the module is receiving the 9th character. Out of reset, the TXIFLSEL and RXIFLSEL bits are configured so that the FIFOs trigger an interrupt at the half-way mark.
UART Interrupt FIFO Level Select (UARTIFLS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RXIFLSEL RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 1 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 TXIFLSEL R/W 1 R/W 0 RO 0 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Receive Interrupt FIFO Level Select The trigger points for the receive interrupt are as follows: Value 0x0 0x1 0x2 0x3 0x4 Description RX FIFO full RX FIFO full RX FIFO full (default) RX FIFO full RX FIFO full
5:3
RXIFLSEL
R/W
0x2
0x5-0x7 Reserved
891
Bit/Field 2:0
Name TXIFLSEL
Type R/W
Reset 0x2
Description UART Transmit Interrupt FIFO Level Select The trigger points for the transmit interrupt are as follows: Value 0x0 0x1 0x2 0x3 0x4 Description TX FIFO empty TX FIFO empty TX FIFO empty (default) TX FIFO empty TX FIFO empty
0x5-0x7 Reserved Note: If the EOT bit in UARTCTL is set (see page 887), the transmit interrupt is generated once the FIFO is completely empty and all data including stop bits have left the transmit serializer. In this case, the setting of TXIFLSEL is ignored.
April 25, 2012
Register 10: UART Interrupt Mask (UARTIM), offset 0x038

The UARTIM register is the interrupt mask set/clear register. On a read, this register gives the current value of the mask on the relevant interrupt. Setting a bit allows the corresponding raw interrupt signal to be routed to the interrupt controller. Clearing a bit prevents the raw interrupt signal from being sent to the interrupt controller.
UART Interrupt Mask (UARTIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 LME5IM Type Reset R/W 0 RO 0 14 LME1IM R/W 0 RO 0 13 LMSBIM R/W 0 RO 0 12 9BITIM R/W 0 RO 0 11
reserved
RO 0 10 OEIM R/W 0
RO 0 9 BEIM R/W 0
RO 0 8 PEIM R/W 0
RO 0 7 FEIM R/W 0
RO 0 6 RTIM R/W 0
RO 0 5 TXIM R/W 0
RO 0 4 RXIM R/W 0
RO 0 3
RO 0 2
RO 0 1 CTSIM R/W 0
RO 0 0
reserved
reserved RO 0 RO 0
RO 0
RO 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. LIN Mode Edge 5 Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the LME5RIS bit in the UARTRIS register is set. The LME5RIS interrupt is suppressed and not sent to the interrupt controller.
15
LME5IM
R/W
14
LME1IM
R/W
LIN Mode Edge 1 Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the LME1RIS bit in the UARTRIS register is set. The LME1RIS interrupt is suppressed and not sent to the interrupt controller.
893
Bit/Field 13
Name LMSBIM
Type R/W
Reset 0
Description LIN Mode Sync Break Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the LMSBRIS bit in the UARTRIS register is set. The LMSBRIS interrupt is suppressed and not sent to the interrupt controller.
12
9BITIM
R/W
9-Bit Mode Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the 9BITRIS bit in the UARTRIS register is set. The 9BITRIS interrupt is suppressed and not sent to the interrupt controller.
11
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Overrun Error Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the OERIS bit in the UARTRIS register is set. The OERIS interrupt is suppressed and not sent to the interrupt controller.
10
OEIM
R/W
BEIM
R/W
UART Break Error Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the BERIS bit in the UARTRIS register is set. The BERIS interrupt is suppressed and not sent to the interrupt controller.
PEIM
R/W
UART Parity Error Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the PERIS bit in the UARTRIS register is set. The PERIS interrupt is suppressed and not sent to the interrupt controller.
April 25, 2012
Bit/Field 7
Name FEIM
Type R/W
Reset 0
Description UART Framing Error Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the FERIS bit in the UARTRIS register is set. The FERIS interrupt is suppressed and not sent to the interrupt controller.
RTIM
R/W
UART Receive Time-Out Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the RTRIS bit in the UARTRIS register is set. The RTRIS interrupt is suppressed and not sent to the interrupt controller.
TXIM
R/W
UART Transmit Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the TXRIS bit in the UARTRIS register is set. The TXRIS interrupt is suppressed and not sent to the interrupt controller.
RXIM
R/W
UART Receive Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the RXRIS bit in the UARTRIS register is set. The RXRIS interrupt is suppressed and not sent to the interrupt controller.
3:2
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Clear to Send Modem Interrupt Mask Value Description 1 0 An interrupt is sent to the interrupt controller when the CTSRIS bit in the UARTRIS register is set. The CTSRIS interrupt is suppressed and not sent to the interrupt controller.
CTSIM
R/W
This bit is implemented only on UART1 and is reserved for UART0 and UART2. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
895
Register 11: UART Raw Interrupt Status (UARTRIS), offset 0x03C

The UARTRIS register is the raw interrupt status register. On a read, this register gives the current raw status value of the corresponding interrupt. A write has no effect.
UART Raw Interrupt Status (UARTRIS)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x03C Type RO, reset 0x0000.000F
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

reserved
RO 0 10 OERIS RO 0
RO 0 9 BERIS RO 0
RO 0 8 PERIS RO 0
RO 0 7 FERIS RO 0
RO 0 6 RTRIS RO 0
RO 0 5 TXRIS RO 0
RO 0 4 RXRIS RO 0
RO 0 3
RO 0 2
RO 0 1 CTSRIS RO 0
RO 0 0
reserved
LME5RIS LME1RIS LMSBRIS 9BITRIS Type Reset RO 0 RO 0 RO 0 R/W 0
reserved RO 0 RO 0
RO 0
RO 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. LIN Mode Edge 5 Raw Interrupt Status Value Description 1 0 The timer value at the 5th falling edge of the LIN Sync Field has been captured. No interrupt
15
LME5RIS
RO
This bit is cleared by writing a 1 to the LME5IC bit in the UARTICR register. 14 LME1RIS RO 0 LIN Mode Edge 1 Raw Interrupt Status Value Description 1 0 The timer value at the 1st falling edge of the LIN Sync Field has been captured. No interrupt
This bit is cleared by writing a 1 to the LME1IC bit in the UARTICR register. 13 LMSBRIS RO 0 LIN Mode Sync Break Raw Interrupt Status Value Description 1 0 A LIN Sync Break has been detected. No interrupt
This bit is cleared by writing a 1 to the LMSBIC bit in the UARTICR register.
April 25, 2012
Bit/Field 12
Name 9BITRIS
Type R/W
Reset 0
Description 9-Bit Mode Raw Interrupt Status Value Description 1 0 A receive address match has occurred. No interrupt
This bit is cleared by writing a 1 to the 9BITIC bit in the UARTICR register. 11 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Overrun Error Raw Interrupt Status Value Description 1 0 An overrun error has occurred. No interrupt
10
OERIS
RO
This bit is cleared by writing a 1 to the OEIC bit in the UARTICR register. 9 BERIS RO 0 UART Break Error Raw Interrupt Status Value Description 1 0 A break error has occurred. No interrupt
This bit is cleared by writing a 1 to the BEIC bit in the UARTICR register. 8 PERIS RO 0 UART Parity Error Raw Interrupt Status Value Description 1 0 A parity error has occurred. No interrupt
This bit is cleared by writing a 1 to the PEIC bit in the UARTICR register. 7 FERIS RO 0 UART Framing Error Raw Interrupt Status Value Description 1 0 A framing error has occurred. No interrupt
This bit is cleared by writing a 1 to the FEIC bit in the UARTICR register. 6 RTRIS RO 0 UART Receive Time-Out Raw Interrupt Status Value Description 1 0 A receive time out has occurred. No interrupt
This bit is cleared by writing a 1 to the RTIC bit in the UARTICR register.
897
Bit/Field 5
Name TXRIS
Type RO
Reset 0
Description UART Transmit Raw Interrupt Status Value Description 1 If the EOT bit in the UARTCTL register is clear, the transmit FIFO level has passed through the condition defined in the UARTIFLS register. If the EOT bit is set, the last bit of all transmitted data and flags has left the serializer. 0 No interrupt
This bit is cleared by writing a 1 to the TXIC bit in the UARTICR register or by writing data to the transmit FIFO until it becomes greater than the trigger level, if the FIFO is enabled, or by writing a single byte if the FIFO is disabled. 4 RXRIS RO 0 UART Receive Raw Interrupt Status Value Description 1 0 The receive FIFO level has passed through the condition defined in the UARTIFLS register. No interrupt
This bit is cleared by writing a 1 to the RXIC bit in the UARTICR register or by reading data from the receive FIFO until it becomes less than the trigger level, if the FIFO is enabled, or by reading a single byte if the FIFO is disabled. 3:2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Clear to Send Modem Raw Interrupt Status Value Description 1 0 Clear to Send used for software flow control. No interrupt
CTSRIS
RO
This bit is cleared by writing a 1 to the CTSIC bit in the UARTICR register. This bit is implemented only on UART1 and is reserved for UART0 and UART2. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Register 12: UART Masked Interrupt Status (UARTMIS), offset 0x040

The UARTMIS register is the masked interrupt status register. On a read, this register gives the current masked status value of the corresponding interrupt. A write has no effect.
UART Masked Interrupt Status (UARTMIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

reserved
RO 0 10 OEMIS RO 0
RO 0 9 BEMIS RO 0
RO 0 8 PEMIS RO 0
RO 0 7 FEMIS RO 0
RO 0 6 RTMIS RO 0
RO 0 5 TXMIS RO 0
RO 0 4 RXMIS RO 0
RO 0 3
RO 0 2
RO 0 1 CTSMIS RO 0
RO 0 0
reserved
LME5MIS LME1MIS LMSBMIS 9BITMIS Type Reset RO 0 RO 0 RO 0 R/W 0
reserved RO 0 RO 0
RO 0
RO 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. LIN Mode Edge 5 Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to the 5th falling edge of the LIN Sync Field. An interrupt has not occurred or is masked.
15
LME5MIS
RO
This bit is cleared by writing a 1 to the LME5IC bit in the UARTICR register. 14 LME1MIS RO 0 LIN Mode Edge 1 Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to the 1st falling edge of the LIN Sync Field. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the LME1IC bit in the UARTICR register.
899
Bit/Field 13
Name LMSBMIS
Type RO
Reset 0
Description LIN Mode Sync Break Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to the receipt of a LIN Sync Break. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the LMSBIC bit in the UARTICR register. 12 9BITMIS R/W 0 9-Bit Mode Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a receive address match. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the 9BITIC bit in the UARTICR register. 11 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Overrun Error Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to an overrun error. An interrupt has not occurred or is masked.
10
OEMIS
RO
This bit is cleared by writing a 1 to the OEIC bit in the UARTICR register. 9 BEMIS RO 0 UART Break Error Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a break error. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the BEIC bit in the UARTICR register. 8 PEMIS RO 0 UART Parity Error Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a parity error. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the PEIC bit in the UARTICR register. 7 FEMIS RO 0 UART Framing Error Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a framing error. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the FEIC bit in the UARTICR register.
April 25, 2012
Bit/Field 6
Name RTMIS
Type RO
Reset 0
Description UART Receive Time-Out Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to a receive time out. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the RTIC bit in the UARTICR register. 5 TXMIS RO 0 UART Transmit Masked Interrupt Status Value Description 1 An unmasked interrupt was signaled due to passing through the specified transmit FIFO level (if the EOT bit is clear) or due to the transmission of the last data bit (if the EOT bit is set). An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the TXIC bit in the UARTICR register or by writing data to the transmit FIFO until it becomes greater than the trigger level, if the FIFO is enabled, or by writing a single byte if the FIFO is disabled. 4 RXMIS RO 0 UART Receive Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to passing through the specified receive FIFO level. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the RXIC bit in the UARTICR register or by reading data from the receive FIFO until it becomes less than the trigger level, if the FIFO is enabled, or by reading a single byte if the FIFO is disabled. 3:2 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Clear to Send Modem Masked Interrupt Status Value Description 1 0 An unmasked interrupt was signaled due to Clear to Send. An interrupt has not occurred or is masked.
CTSMIS
RO
This bit is cleared by writing a 1 to the CTSIC bit in the UARTICR register. This bit is implemented only on UART1 and is reserved for UART0 and UART2. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
901
Register 13: UART Interrupt Clear (UARTICR), offset 0x044

The UARTICR register is the interrupt clear register. On a write of 1, the corresponding interrupt (both raw interrupt and masked interrupt, if enabled) is cleared. A write of 0 has no effect.
UART Interrupt Clear (UARTICR)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x044 Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 LME5IC Type Reset W1C 0 RO 0 14 LME1IC W1C 0 RO 0 13 LMSBIC W1C 0 RO 0 12 9BITIC R/W 0 RO 0 11
reserved
RO 0 10 OEIC W1C 0
RO 0 9 BEIC W1C 0
RO 0 8 PEIC W1C 0
RO 0 7 FEIC W1C 0
RO 0 6 RTIC W1C 0
RO 0 5 TXIC W1C 0
RO 0 4 RXIC W1C 0
RO 0 3
RO 0 2
RO 0 1 CTSMIC W1C 0
RO 0 0
reserved
reserved RO 0 RO 0
RO 0
RO 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. LIN Mode Edge 5 Interrupt Clear Writing a 1 to this bit clears the LME5RIS bit in the UARTRIS register and the LME5MIS bit in the UARTMIS register.
15
LME5IC
W1C
14
LME1IC
W1C
LIN Mode Edge 1 Interrupt Clear Writing a 1 to this bit clears the LME1RIS bit in the UARTRIS register and the LME1MIS bit in the UARTMIS register.
13
LMSBIC
W1C
LIN Mode Sync Break Interrupt Clear Writing a 1 to this bit clears the LMSBRIS bit in the UARTRIS register and the LMSBMIS bit in the UARTMIS register.
12
9BITIC
R/W
9-Bit Mode Interrupt Clear Writing a 1 to this bit clears the 9BITRIS bit in the UARTRIS register and the 9BITMIS bit in the UARTMIS register.
11
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Overrun Error Interrupt Clear Writing a 1 to this bit clears the OERIS bit in the UARTRIS register and the OEMIS bit in the UARTMIS register.
10
OEIC
W1C
BEIC
W1C
Break Error Interrupt Clear Writing a 1 to this bit clears the BERIS bit in the UARTRIS register and the BEMIS bit in the UARTMIS register.
April 25, 2012
Bit/Field 8
Name PEIC
Type W1C
Reset 0
Description Parity Error Interrupt Clear Writing a 1 to this bit clears the PERIS bit in the UARTRIS register and the PEMIS bit in the UARTMIS register.
FEIC
W1C
Framing Error Interrupt Clear Writing a 1 to this bit clears the FERIS bit in the UARTRIS register and the FEMIS bit in the UARTMIS register.
RTIC
W1C
Receive Time-Out Interrupt Clear Writing a 1 to this bit clears the RTRIS bit in the UARTRIS register and the RTMIS bit in the UARTMIS register.
TXIC
W1C
Transmit Interrupt Clear Writing a 1 to this bit clears the TXRIS bit in the UARTRIS register and the TXMIS bit in the UARTMIS register.
RXIC
W1C
Receive Interrupt Clear Writing a 1 to this bit clears the RXRIS bit in the UARTRIS register and the RXMIS bit in the UARTMIS register.
3:2
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Clear to Send Modem Interrupt Clear Writing a 1 to this bit clears the CTSRIS bit in the UARTRIS register and the CTSMIS bit in the UARTMIS register. This bit is implemented only on UART1 and is reserved for UART0 and UART2.
CTSMIC
W1C
reserved
RO
903
Register 14: UART DMA Control (UARTDMACTL), offset 0x048

The UARTDMACTL register is the DMA control register.
UART DMA Control (UARTDMACTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
DMAERR TXDMAE RXDMAE R/W 0 R/W 0 R/W 0
Bit/Field 31:3
Name reserved
Type RO
Reset
Description
0x00000.000 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 0 DMA on Error Value Description 1 0 DMA receive requests are automatically disabled when a receive error occurs. DMA receive requests are unaffected when a receive error occurs.
DMAERR
R/W
TXDMAE
R/W
Transmit DMA Enable Value Description 1 0 DMA for the transmit FIFO is enabled. DMA for the transmit FIFO is disabled.
RXDMAE
R/W
Receive DMA Enable Value Description 1 0 DMA for the receive FIFO is enabled. DMA for the receive FIFO is disabled.
April 25, 2012
Register 15: UART LIN Control (UARTLCTL), offset 0x090

The UARTLCTL register is the configures the operation of the UART when in LIN mode.
UART LIN Control (UARTLCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 BLEN RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 RO 0 4 RO 0 3 RO 0 2 reserved RO 0 RO 0 RO 0 1 RO 0 0 MASTER R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Sync Break Length Value Description 0x3 0x2 0x1 0x0 Sync break length is 16T bits Sync break length is 15T bits Sync break length is 14T bits Sync break length is 13T bits (default)
5:4
BLEN
R/W
0x0
3:1
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. LIN Master Enable Value Description 1 0 The UART operates as a LIN master. The UART operates as a LIN slave.
MASTER
R/W
905
Register 16: UART LIN Snap Shot (UARTLSS), offset 0x094

The UARTLSS register captures the free-running timer value when either the Sync Edge 1 or the Sync Edge 5 is detected in LIN mode.
UART LIN Snap Shot (UARTLSS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 TSS Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Timer Snap Shot This field contains the value of the free-running timer when either the Sync Edge 5 or the Sync Edge 1 was detected.
15:0
TSS
RO
0x0000
April 25, 2012
Register 17: UART LIN Timer (UARTLTIM), offset 0x098

The UARTLTIM register contains the current timer value for the free-running timer that is used to calculate the baud rate when in LIN slave mode. The value in this register is used along with the value in the UART LIN Snap Shot (UARTLSS) register to adjust the baud rate to match that of the master. Note: If the PIOSC is being used as the UART baud clock (the CS field in the UART Clock Configuration (UARTCC) register is 0x1), the value in this register should be read twice to ensure the data is correct. If the data does not match, the value should be read again until two consecutive values match. This step is not necessary when using the system clock for the UART baud clock (the CS field is 0x0).
UART LIN Timer (UARTLTIM)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 TIMER Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Timer Value This field contains the value of the free-running timer.
15:0
TIMER
RO
0x0000
907
Register 18: UART 9-Bit Self Address (UART9BITADDR), offset 0x0A4

The UART9BITADDR register is used to write the specific address that should be matched with the receiving byte when the 9-bit Address Mask (UART9BITAMASK) is set to 0xFF. This register is used in conjunction with UART9BITAMASK to form a match for address-byte received.
UART 9-Bit Self Address (UART9BITADDR)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x0A4 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 9BITEN Type Reset R/W 0 RO 0 RO 0 RO 0 RO 0 14 RO 0 13 RO 0 12 RO 0 11 reserved RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 ADDR R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Enable 9-Bit Mode Value Description 1 0 9-bit mode is enabled. 9-bit mode is disabled.
15
9BITEN
R/W
14:8
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Self Address for 9-Bit Mode This field contains the address that should be matched when UART9BITAMASK is 0xFF.
7:0
ADDR
R/W
0x00
April 25, 2012
Register 19: UART 9-Bit Self Address Mask (UART9BITAMASK), offset 0x0A8
The UART9BITAMASK register is used to enable the address mask for 9-bit mode. The address bits are masked to create a set of addresses to be matched with the received address byte.
UART 9-Bit Self Address Mask (UART9BITAMASK)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0x0A8 Type R/W, reset 0x0000.00FF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 MASK RO 0 RO 0 RO 0 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Self Address Mask for 9-Bit Mode This field contains the address mask that creates a set of addresses that should be matched.
7:0
MASK
R/W
0xFF
909
Register 20: UART Peripheral Properties (UARTPP), offset 0xFC0

The UARTPP register provides information regarding the properties of the UART module.
UART Peripheral Properties (UARTPP)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFC0 Type RO, reset 0x0000.0003
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 NB RO 1 RO 0 0 SC RO 1
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. 9-Bit Support Value Description 1 0 The UART module provides support for the transmission of 9-bit data for RS-485 support. The UART module does not provide support for the transmission of 9-bit data for RS-485 support.
NB
RO
0x1
SC
RO
0x1
Smart Card Support Value Description 1 0 The UART module provides smart card support. The UART module does not provide smart card support.
April 25, 2012
Register 21: UART Clock Configuration (UARTCC), offset 0xFC8

The UARTCC register controls the baud clock source for the UART module. For more information, see the section called Communication Clock Sources on page 218. Note: If the PIOSC is used for the UART baud clock, the system clock frequency must be at least 9 MHz in Run mode.
UART Clock Configuration (UARTCC)

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFC8 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Baud Clock Source The following table specifies the source that generates for the UART baud clock: Value 0x0 Description System clock (based on clock source and divisor factor)
3:0
CS
R/W
0x1-0x4 reserved 0x5 PIOSC
0x5-0xF Reserved
911
Register 22: UART Peripheral Identification 4 (UARTPeriphID4), offset 0xFD0

The UARTPeriphIDn registers are hard-coded and the fields within the registers determine the reset values.
UART Peripheral Identification 4 (UARTPeriphID4)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFD0 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART Peripheral ID Register [7:0] Can be used by software to identify the presence of this peripheral.
7:0
PID4
RO
0x00
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID5
RO
0x00
913

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID6
RO
0x00
April 25, 2012
Register 25: UART Peripheral Identification 7 (UARTPeriphID7), offset 0xFDC

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFDC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID7
RO
0x00
915
Register 26: UART Peripheral Identification 0 (UARTPeriphID0), offset 0xFE0

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFE0 Type RO, reset 0x0000.0060
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID0
RO
0x60
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID1
RO
0x00
917

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID2
RO
0x18
April 25, 2012
Register 29: UART Peripheral Identification 3 (UARTPeriphID3), offset 0xFEC

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFEC Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID3
RO
0x01
919
Register 30: UART PrimeCell Identification 0 (UARTPCellID0), offset 0xFF0

The UARTPCellIDn registers are hard-coded and the fields within the registers determine the reset values.
UART PrimeCell Identification 0 (UARTPCellID0)
UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFF0 Type RO, reset 0x0000.000D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. UART PrimeCell ID Register [7:0] Provides software a standard cross-peripheral identification system.
7:0
CID0
RO
0x0D
April 25, 2012

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFF4 Type RO, reset 0x0000.00F0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID1
RO
0xF0
921

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFF8 Type RO, reset 0x0000.0005
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID2
RO
0x05
April 25, 2012
Register 33: UART PrimeCell Identification 3 (UARTPCellID3), offset 0xFFC

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000 Offset 0xFFC Type RO, reset 0x0000.00B1
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID3
RO
0xB1
923
Synchronous Serial Interface (SSI)
15

The Stellaris microcontroller includes four Synchronous Serial Interface (SSI) modules. Each SSI module is a master or slave interface for synchronous serial communication with peripheral devices that have either Freescale SPI, MICROWIRE, or Texas Instruments synchronous serial interfaces. The Stellaris LM4F120H5QR controller includes four SSI modules with the following features: Programmable interface operation for Freescale SPI, MICROWIRE, or Texas Instruments synchronous serial interfaces Master or slave operation Programmable clock bit rate and prescaler Separate transmit and receive FIFOs, each 16 bits wide and 8 locations deep Programmable data frame size from 4 to 16 bits Internal loopback test mode for diagnostic/debug testing Standard FIFO-based interrupts and End-of-Transmission interrupt Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive Receive single request asserted when data is in the FIFO; burst request asserted when FIFO contains 4 entries Transmit single request asserted when there is space in the FIFO; burst request asserted when FIFO contains 4 entries
April 25, 2012
15.1
Block Diagram
Figure 15-1. SSI Module Block Diagram

DMA Request DMA Control SSIDMACTL
Interrupt
Interrupt Control TxFIFO 8 x 16
SSIIM SSIMIS SSIRIS SSIICR Control/Status
. . . SSITx
SSICR0 SSICR1 SSISR SSIDR
SSIRx Transmit/ Receive Logic RxFIFO 8 x 16 SSIClk SSIFss
Clock Prescaler System Clock PIOSC Clock Control SSICC SSICPSR
. . .
SSI Baud Clock Identification Registers SSIPCellID0 SSIPCellID1 SSIPCellID2 SSIPCellID3 SSIPeriphID0 SSIPeriphID1 SSIPeriphID2 SSIPeriphID3 SSIPeriphID4 SSIPeriphID5 SSIPeriphID6 SSIPeriphID7
15.2
Signal Description
The following table lists the external signals of the SSI module and describes the function of each. Most SSI signals are alternate functions for some GPIO signals and default to be GPIO signals at reset. The exceptions to this rule are the SSI0Clk, SSI0Fss, SSI0Rx, and SSI0Tx pins, which default to the SSI function. The "Pin Mux/Pin Assignment" column in the following table lists the possible GPIO pin placements for the SSI signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the SSI function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control
925
(GPIOPCTL) register (page 670) to assign the SSI signal to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632. Table 15-1. SSI Signals (64LQFP)
Pin Name SSI0Clk SSI0Fss SSI0Rx SSI0Tx SSI1Clk SSI1Fss SSI1Rx SSI1Tx SSI2Clk SSI2Fss SSI2Rx SSI2Tx SSI3Clk SSI3Fss SSI3Rx SSI3Tx Pin Number Pin Mux / Pin Assignment 19 20 21 22 30 61 31 62 28 63 29 64 58 57 1 4 61 62 63 64 PA2 (2) PA3 (2) PA4 (2) PA5 (2) PF2 (2) PD0 (2) PF3 (2) PD1 (2) PF0 (2) PD2 (2) PF1 (2) PD3 (2) PB4 (2) PB5 (2) PB6 (2) PB7 (2) PD0 (1) PD1 (1) PD2 (1) PD3 (1) Pin Type I/O I/O I O I/O I/O I O I/O I/O I O I/O I/O I O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description SSI module 0 clock SSI module 0 frame signal SSI module 0 receive SSI module 0 transmit SSI module 1 clock SSI module 1 frame signal SSI module 1 receive SSI module 1 transmit SSI module 2 clock SSI module 2 frame signal SSI module 2 receive SSI module 2 transmit SSI module 3 clock SSI module 3 frame signal SSI module 3 receive SSI module 3 transmit
15.3
The SSI performs serial-to-parallel conversion on data received from a peripheral device. The CPU accesses data, control, and status information. The transmit and receive paths are buffered with internal FIFO memories allowing up to eight 16-bit values to be stored independently in both transmit and receive modes. The SSI also supports the DMA interface. The transmit and receive FIFOs can be programmed as destination/source addresses in the DMA module. DMA operation is enabled by setting the appropriate bit(s) in the SSIDMACTL register (see page 953).
15.3.1
Bit Rate Generation

The SSI includes a programmable bit rate clock divider and prescaler to generate the serial output clock. Bit rates are supported to 2 MHz and higher, although maximum bit rate is determined by peripheral devices. The serial bit rate is derived by dividing down the input clock (SysClk). The clock is first divided by an even prescale value CPSDVSR from 2 to 254, which is programmed in the SSI Clock Prescale (SSICPSR) register (see page 946). The clock is further divided by a value from 1 to 256, which is 1 + SCR, where SCR is the value programmed in the SSI Control 0 (SSICR0) register (see page 939). The frequency of the output clock SSIClk is defined by: SSIClk = SysClk / (CPSDVSR * (1 + SCR))
April 25, 2012
Note:
The PIOSC is used as the source for the SSIClk when the CS field in the SSI Clock Configuration (SSICC) register is configured to 0x1. For master mode, the system clock or the PIOSC must be at least two times faster than the SSIClk, with the restriction that SSIClk cannot be faster than 25 MHz. For slave mode, the system clock or the PIOSC must be at least 6 times faster than the SSIClk.
See Synchronous Serial Interface (SSI) on page 1176 to view SSI timing parameters.
15.3.2
15.3.2.1
FIFO Operation
Transmit FIFO
The common transmit FIFO is a 16-bit wide, 8-locations deep, first-in, first-out memory buffer. The CPU writes data to the FIFO by writing the SSI Data (SSIDR) register (see page 943), and data is stored in the FIFO until it is read out by the transmission logic. When configured as a master or a slave, parallel data is written into the transmit FIFO prior to serial conversion and transmission to the attached slave or master, respectively, through the SSITx pin. In slave mode, the SSI transmits data each time the master initiates a transaction. If the transmit FIFO is empty and the master initiates, the slave transmits the 8th most recent value in the transmit FIFO. If less than 8 values have been written to the transmit FIFO since the SSI module clock was enabled using the Rn bit in the RCGCSSI register, then 0 is transmitted. Care should be taken to ensure that valid data is in the FIFO as needed. The SSI can be configured to generate an interrupt or a DMA request when the FIFO is empty.
15.3.2.2
Receive FIFO
The common receive FIFO is a 16-bit wide, 8-locations deep, first-in, first-out memory buffer. Received data from the serial interface is stored in the buffer until read out by the CPU, which accesses the read FIFO by reading the SSIDR register. When configured as a master or slave, serial data received through the SSIRx pin is registered prior to parallel loading into the attached slave or master receive FIFO, respectively.
15.3.3
Interrupts
The SSI can generate interrupts when the following conditions are observed: Transmit FIFO service (when the transmit FIFO is half full or less) Receive FIFO service (when the receive FIFO is half full or more) Receive FIFO time-out Receive FIFO overrun End of transmission All of the interrupt events are ORed together before being sent to the interrupt controller, so the SSI generates a single interrupt request to the controller regardless of the number of active interrupts. Each of the four individual maskable interrupts can be masked by clearing the appropriate bit in the SSI Interrupt Mask (SSIIM) register (see page 947). Setting the appropriate mask bit enables the interrupt. The individual outputs, along with a combined interrupt output, allow use of either a global interrupt service routine or modular device drivers to handle interrupts. The transmit and receive dynamic
927
dataflow interrupts have been separated from the status interrupts so that data can be read or written in response to the FIFO trigger levels. The status of the individual interrupt sources can be read from the SSI Raw Interrupt Status (SSIRIS) and SSI Masked Interrupt Status (SSIMIS) registers (see page 948 and page 950, respectively). The receive FIFO has a time-out period that is 32 periods at the rate of SSIClk (whether or not SSIClk is currently active) and is started when the RX FIFO goes from EMPTY to not-EMPTY. If the RX FIFO is emptied before 32 clocks have passed, the time-out period is reset. As a result, the ISR should clear the Receive FIFO Time-out Interrupt just after reading out the RX FIFO by writing a 1 to the RTIC bit in the SSI Interrupt Clear (SSIICR) register. The interrupt should not be cleared so late that the ISR returns before the interrupt is actually cleared, or the ISR may be re-activated unnecessarily. The End-of-Transmission (EOT) interrupt indicates that the data has been transmitted completely. This interrupt can be used to indicate when it is safe to turn off the SSI module clock or enter sleep mode. In addition, because transmitted data and received data complete at exactly the same time, the interrupt can also indicate that read data is ready immediately, without waiting for the receive FIFO time-out period to complete.
15.3.4
Frame Formats
Each data frame is between 4 and 16 bits long depending on the size of data programmed and is transmitted starting with the MSB. There are three basic frame types that can be selected by programming the FRF bit in the SSICR0 register: Texas Instruments synchronous serial Freescale SPI MICROWIRE For all three formats, the serial clock (SSIClk) is held inactive while the SSI is idle, and SSIClk transitions at the programmed frequency only during active transmission or reception of data. The idle state of SSIClk is utilized to provide a receive timeout indication that occurs when the receive FIFO still contains data after a timeout period. For Freescale SPI and MICROWIRE frame formats, the serial frame (SSIFss) pin is active Low, and is asserted (pulled down) during the entire transmission of the frame. For Texas Instruments synchronous serial frame format, the SSIFss pin is pulsed for one serial clock period starting at its rising edge, prior to the transmission of each frame. For this frame format, both the SSI and the off-chip slave device drive their output data on the rising edge of SSIClk and latch data from the other device on the falling edge. Unlike the full-duplex transmission of the other two frame formats, the MICROWIRE format uses a special master-slave messaging technique which operates at half-duplex. In this mode, when a frame begins, an 8-bit control message is transmitted to the off-chip slave. During this transmit, no incoming data is received by the SSI. After the message has been sent, the off-chip slave decodes it and, after waiting one serial clock after the last bit of the 8-bit control message has been sent, responds with the requested data. The returned data can be 4 to 16 bits in length, making the total frame length anywhere from 13 to 25 bits.
15.3.4.1
Texas Instruments Synchronous Serial Frame Format

Figure 15-2 on page 929 shows the Texas Instruments synchronous serial frame format for a single transmitted frame.
April 25, 2012
Figure 15-2. TI Synchronous Serial Frame Format (Single Transfer)

SSIClk SSIFss
SSITx/SSIRx
MSB 4 to 16 bits
LSB
In this mode, SSIClk and SSIFss are forced Low, and the transmit data line SSITx is tristated whenever the SSI is idle. Once the bottom entry of the transmit FIFO contains data, SSIFss is pulsed High for one SSIClk period. The value to be transmitted is also transferred from the transmit FIFO to the serial shift register of the transmit logic. On the next rising edge of SSIClk, the MSB of the 4 to 16-bit data frame is shifted out on the SSITx pin. Likewise, the MSB of the received data is shifted onto the SSIRx pin by the off-chip serial slave device. Both the SSI and the off-chip serial slave device then clock each data bit into their serial shifter on each falling edge of SSIClk. The received data is transferred from the serial shifter to the receive FIFO on the first rising edge of SSIClk after the LSB has been latched. Figure 15-3 on page 929 shows the Texas Instruments synchronous serial frame format when back-to-back frames are transmitted. Figure 15-3. TI Synchronous Serial Frame Format (Continuous Transfer)
SSIClk SSIFss SSITx/SSIRx MSB 4 to 16 bits LSB
15.3.4.2
Freescale SPI Frame Format

The Freescale SPI interface is a four-wire interface where the SSIFss signal behaves as a slave select. The main feature of the Freescale SPI format is that the inactive state and phase of the SSIClk signal are programmable through the SPO and SPH bits in the SSISCR0 control register. SPO Clock Polarity Bit When the SPO clock polarity control bit is clear, it produces a steady state Low value on the SSIClk pin. If the SPO bit is set, a steady state High value is placed on the SSIClk pin when data is not being transferred.
929
SPH Phase Control Bit The SPH phase control bit selects the clock edge that captures data and allows it to change state. The state of this bit has the most impact on the first bit transmitted by either allowing or not allowing a clock transition before the first data capture edge. When the SPH phase control bit is clear, data is captured on the first clock edge transition. If the SPH bit is set, data is captured on the second clock edge transition.
15.3.4.3
Freescale SPI Frame Format with SPO=0 and SPH=0

Single and continuous transmission signal sequences for Freescale SPI format with SPO=0 and SPH=0 are shown in Figure 15-4 on page 930 and Figure 15-5 on page 930. Figure 15-4. Freescale SPI Format (Single Transfer) with SPO=0 and SPH=0
SSIClk SSIFss SSIRx MSB 4 to 16 bits SSITx MSB LSB LSB Q
Note:
Q is undefined.
Figure 15-5. Freescale SPI Format (Continuous Transfer) with SPO=0 and SPH=0
SSIClk SSIFss SSIRx LSB MSB 4 to16 bits SSITx LSB MSB LSB MSB LSB MSB
In this configuration, during idle periods: SSIClk is forced Low SSIFss is forced High The transmit data line SSITx is arbitrarily forced Low When the SSI is configured as a master, it enables the SSIClk pad When the SSI is configured as a slave, it disables the SSIClk pad If the SSI is enabled and valid data is in the transmit FIFO, the start of transmission is signified by the SSIFss master signal being driven Low, causing slave data to be enabled onto the SSIRx input line of the master. The master SSITx output pad is enabled.
April 25, 2012
One half SSIClk period later, valid master data is transferred to the SSITx pin. Once both the master and slave data have been set, the SSIClk master clock pin goes High after one additional half SSIClk period. The data is now captured on the rising and propagated on the falling edges of the SSIClk signal. In the case of a single word transmission, after all bits of the data word have been transferred, the SSIFss line is returned to its idle High state one SSIClk period after the last bit has been captured. However, in the case of continuous back-to-back transmissions, the SSIFss signal must be pulsed High between each data word transfer because the slave select pin freezes the data in its serial peripheral register and does not allow it to be altered if the SPH bit is clear. Therefore, the master device must raise the SSIFss pin of the slave device between each data transfer to enable the serial peripheral data write. On completion of the continuous transfer, the SSIFss pin is returned to its idle state one SSIClk period after the last bit has been captured.
15.3.4.4

The transfer signal sequence for Freescale SPI format with SPO=0 and SPH=1 is shown in Figure 15-6 on page 931, which covers both single and continuous transfers. Figure 15-6. Freescale SPI Frame Format with SPO=0 and SPH=1
SSIClk SSIFss SSIRx SSITx Q Q MSB 4 to 16 bits MSB LSB LSB Q
Note:
Q is undefined.
In this configuration, during idle periods: SSIClk is forced Low SSIFss is forced High The transmit data line SSITx is arbitrarily forced Low When the SSI is configured as a master, it enables the SSIClk pad When the SSI is configured as a slave, it disables the SSIClk pad If the SSI is enabled and valid data is in the transmit FIFO, the start of transmission is signified by the SSIFss master signal being driven Low. The master SSITx output is enabled. After an additional one-half SSIClk period, both master and slave valid data are enabled onto their respective transmission lines. At the same time, the SSIClk is enabled with a rising edge transition. Data is then captured on the falling edges and propagated on the rising edges of the SSIClk signal. In the case of a single word transfer, after all bits have been transferred, the SSIFss line is returned to its idle High state one SSIClk period after the last bit has been captured.
931
For continuous back-to-back transfers, the SSIFss pin is held Low between successive data words, and termination is the same as that of the single word transfer.
15.3.4.5

Single and continuous transmission signal sequences for Freescale SPI format with SPO=1 and SPH=0 are shown in Figure 15-7 on page 932 and Figure 15-8 on page 932. Figure 15-7. Freescale SPI Frame Format (Single Transfer) with SPO=1 and SPH=0
SSIClk
SSIFss SSIRx MSB 4 to 16 bits SSITx MSB LSB LSB Q
Note:
Q is undefined.
Figure 15-8. Freescale SPI Frame Format (Continuous Transfer) with SPO=1 and SPH=0
SSIClk SSIFss SSITx/SSIRx LSB MSB 4 to 16 bits LSB MSB
In this configuration, during idle periods: SSIClk is forced High SSIFss is forced High The transmit data line SSITx is arbitrarily forced Low When the SSI is configured as a master, it enables the SSIClk pad When the SSI is configured as a slave, it disables the SSIClk pad If the SSI is enabled and valid data is in the transmit FIFO, the start of transmission is signified by the SSIFss master signal being driven Low, causing slave data to be immediately transferred onto the SSIRx line of the master. The master SSITx output pad is enabled. One-half period later, valid master data is transferred to the SSITx line. Once both the master and slave data have been set, the SSIClk master clock pin becomes Low after one additional half SSIClk period, meaning that data is captured on the falling edges and propagated on the rising edges of the SSIClk signal. In the case of a single word transmission, after all bits of the data word are transferred, the SSIFss line is returned to its idle High state one SSIClk period after the last bit has been captured.
April 25, 2012
However, in the case of continuous back-to-back transmissions, the SSIFss signal must be pulsed High between each data word transfer because the slave select pin freezes the data in its serial peripheral register and does not allow it to be altered if the SPH bit is clear. Therefore, the master device must raise the SSIFss pin of the slave device between each data transfer to enable the serial peripheral data write. On completion of the continuous transfer, the SSIFss pin is returned to its idle state one SSIClk period after the last bit has been captured.
15.3.4.6

The transfer signal sequence for Freescale SPI format with SPO=1 and SPH=1 is shown in Figure 15-9 on page 933, which covers both single and continuous transfers. Figure 15-9. Freescale SPI Frame Format with SPO=1 and SPH=1
SSIClk SSIFss SSIRx Q MSB 4 to 16 bits SSITx MSB LSB LSB Q
Note:
Q is undefined.
In this configuration, during idle periods: SSIClk is forced High SSIFss is forced High The transmit data line SSITx is arbitrarily forced Low When the SSI is configured as a master, it enables the SSIClk pad When the SSI is configured as a slave, it disables the SSIClk pad If the SSI is enabled and valid data is in the transmit FIFO, the start of transmission is signified by the SSIFss master signal being driven Low. The master SSITx output pad is enabled. After an additional one-half SSIClk period, both master and slave data are enabled onto their respective transmission lines. At the same time, SSIClk is enabled with a falling edge transition. Data is then captured on the rising edges and propagated on the falling edges of the SSIClk signal. After all bits have been transferred, in the case of a single word transmission, the SSIFss line is returned to its idle high state one SSIClk period after the last bit has been captured. For continuous back-to-back transmissions, the SSIFss pin remains in its active Low state until the final bit of the last word has been captured and then returns to its idle state as described above. For continuous back-to-back transfers, the SSIFss pin is held Low between successive data words and termination is the same as that of the single word transfer.
15.3.4.7
MICROWIRE Frame Format

Figure 15-10 on page 934 shows the MICROWIRE frame format for a single frame. Figure 15-11 on page 935 shows the same format when back-to-back frames are transmitted.
933
Figure 15-10. MICROWIRE Frame Format (Single Frame)

SSIClk SSIFss SSITx SSIRx MSB 8-bit control 0 MSB 4 to 16 bits output data LSB LSB
MICROWIRE format is very similar to SPI format, except that transmission is half-duplex instead of full-duplex and uses a master-slave message passing technique. Each serial transmission begins with an 8-bit control word that is transmitted from the SSI to the off-chip slave device. During this transmission, no incoming data is received by the SSI. After the message has been sent, the off-chip slave decodes it and, after waiting one serial clock after the last bit of the 8-bit control message has been sent, responds with the required data. The returned data is 4 to 16 bits in length, making the total frame length anywhere from 13 to 25 bits. In this configuration, during idle periods: SSIClk is forced Low SSIFss is forced High The transmit data line SSITx is arbitrarily forced Low A transmission is triggered by writing a control byte to the transmit FIFO. The falling edge of SSIFss causes the value contained in the bottom entry of the transmit FIFO to be transferred to the serial shift register of the transmit logic and the MSB of the 8-bit control frame to be shifted out onto the SSITx pin. SSIFss remains Low for the duration of the frame transmission. The SSIRx pin remains tristated during this transmission. The off-chip serial slave device latches each control bit into its serial shifter on each rising edge of SSIClk. After the last bit is latched by the slave device, the control byte is decoded during a one clock wait-state, and the slave responds by transmitting data back to the SSI. Each bit is driven onto the SSIRx line on the falling edge of SSIClk. The SSI in turn latches each bit on the rising edge of SSIClk. At the end of the frame, for single transfers, the SSIFss signal is pulled High one clock period after the last bit has been latched in the receive serial shifter, causing the data to be transferred to the receive FIFO. Note: The off-chip slave device can tristate the receive line either on the falling edge of SSIClk after the LSB has been latched by the receive shifter or when the SSIFss pin goes High.
For continuous transfers, data transmission begins and ends in the same manner as a single transfer. However, the SSIFss line is continuously asserted (held Low) and transmission of data occurs back-to-back. The control byte of the next frame follows directly after the LSB of the received data from the current frame. Each of the received values is transferred from the receive shifter on the falling edge of SSIClk, after the LSB of the frame has been latched into the SSI.
April 25, 2012
Figure 15-11. MICROWIRE Frame Format (Continuous Transfer)

SSIClk
SSIFss SSITx LSB MSB 8-bit control SSIRx 0 MSB 4 to 16 bits output data LSB MSB LSB
In the MICROWIRE mode, the SSI slave samples the first bit of receive data on the rising edge of SSIClk after SSIFss has gone Low. Masters that drive a free-running SSIClk must ensure that the SSIFss signal has sufficient setup and hold margins with respect to the rising edge of SSIClk. Figure 15-12 on page 935 illustrates these setup and hold time requirements. With respect to the SSIClk rising edge on which the first bit of receive data is to be sampled by the SSI slave, SSIFss must have a setup of at least two times the period of SSIClk on which the SSI operates. With respect to the SSIClk rising edge previous to this edge, SSIFss must have a hold of at least one SSIClk period. Figure 15-12. MICROWIRE Frame Format, SSIFss Input Setup and Hold Requirements
tSetup=(2*tSSIClk ) tHold=tSSIClk SSIClk SSIFss
SSIRx
First RX data to be sampled by SSI slave
15.3.5
DMA Operation
The SSI peripheral provides an interface to the DMA controller with separate channels for transmit and receive. The DMA operation of the SSI is enabled through the SSI DMA Control (SSIDMACTL) register. When DMA operation is enabled, the SSI asserts a DMA request on the receive or transmit channel when the associated FIFO can transfer data. For the receive channel, a single transfer request is asserted whenever any data is in the receive FIFO. A burst transfer request is asserted whenever the amount of data in the receive FIFO is 4 or more items. For the transmit channel, a single transfer request is asserted whenever at least one empty location is in the transmit FIFO. The burst request is asserted whenever the transmit FIFO has 4 or more empty slots. The single and burst DMA transfer requests are handled automatically by the DMA controller depending how the DMA channel is configured. To enable DMA operation for the receive channel, the RXDMAE bit of the DMA Control (SSIDMACTL) register should be set. To enable DMA operation for the transmit channel, the TXDMAE bit of SSIDMACTL should be set. If DMA is enabled, then the DMA controller triggers an interrupt when a transfer is complete. The interrupt occurs on the SSI interrupt vector. Therefore, if interrupts are used for SSI operation and DMA is enabled, the SSI interrupt handler must be designed to handle the DMA completion interrupt.
935
See Micro Direct Memory Access (DMA) on page 568 for more details about programming the DMA controller.
15.4

To enable and initialize the SSI, the following steps are necessary: 1. Enable the SSI module using the RCGCSSI register (see page 318). 2. Enable the clock to the appropriate GPIO module via the RCGCGPIO register (see page 312). To find out which GPIO port to enable, refer to Table 21-5 on page 1152. 3. Set the GPIO AFSEL bits for the appropriate pins (see page 653). To determine which GPIOs to configure, see Table 21-4 on page 1148. 4. Configure the PMCn fields in the GPIOPCTL register to assign the SSI signals to the appropriate pins. See page 670 and Table 21-5 on page 1152. For each of the frame formats, the SSI is configured using the following steps: 1. Ensure that the SSE bit in the SSICR1 register is clear before making any configuration changes. 2. Select whether the SSI is a master or slave: a. For master operations, set the SSICR1 register to 0x0000.0000. b. For slave mode (output enabled), set the SSICR1 register to 0x0000.0004. c. For slave mode (output disabled), set the SSICR1 register to 0x0000.000C. 3. Configure the SSI clock source by writing to the SSICC register. 4. Configure the clock prescale divisor by writing the SSICPSR register. 5. Write the SSICR0 register with the following configuration: Serial clock rate (SCR) Desired clock phase/polarity, if using Freescale SPI mode (SPH and SPO) The protocol mode: Freescale SPI, TI SSF, MICROWIRE (FRF) The data size (DSS) 6. Optionally, configure the DMA channel (see Micro Direct Memory Access (DMA) on page 568) and enable the DMA option(s) in the SSIDMACTL register. 7. Enable the SSI by setting the SSE bit in the SSICR1 register. As an example, assume the SSI must be configured to operate with the following parameters: Master operation Freescale SPI mode (SPO=1, SPH=1) 1 Mbps bit rate
April 25, 2012
8 data bits Assuming the system clock is 20 MHz, the bit rate calculation would be: SSIClk = SysClk / (CPSDVSR * (1 + SCR)) 1x106 = 20x106 / (CPSDVSR * (1 + SCR)) In this case, if CPSDVSR=0x2, SCR must be 0x9. The configuration sequence would be as follows: 1. Ensure that the SSE bit in the SSICR1 register is clear. 2. Write the SSICR1 register with a value of 0x0000.0000. 3. Write the SSICPSR register with a value of 0x0000.0002. 4. Write the SSICR0 register with a value of 0x0000.09C7. 5. The SSI is then enabled by setting the SSE bit in the SSICR1 register.
15.5
Register Map
Table 15-2 on page 937 lists the SSI registers. The offset listed is a hexadecimal increment to the registers address, relative to that SSI modules base address: SSI0: 0x4000.8000 SSI1: 0x4000.9000 SSI2: 0x4000.A000 SSI3: 0x4000.B000
Note that the SSI module clock must be enabled before the registers can be programmed (see page 318). There must be a delay of 3 system clocks after the SSI module clock is enabled before any SSI module registers are accessed. Note: The SSI must be disabled (see the SSE bit in the SSICR1 register) before any of the control registers are reprogrammed.
Table 15-2. SSI Register Map

Offset 0x000 0x004 0x008 0x00C 0x010 0x014 0x018 0x01C 0x020 Name SSICR0 SSICR1 SSIDR SSISR SSICPSR SSIIM SSIRIS SSIMIS SSIICR Type R/W R/W R/W RO R/W R/W RO RO W1C Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0003 0x0000.0000 0x0000.0000 0x0000.0008 0x0000.0000 0x0000.0000 Description SSI Control 0 SSI Control 1 SSI Data SSI Status SSI Clock Prescale SSI Interrupt Mask SSI Raw Interrupt Status SSI Masked Interrupt Status SSI Interrupt Clear See page 939 941 943 944 946 947 948 950 952
937
Table 15-2. SSI Register Map (continued)

Offset 0x024 0xFC8 0xFD0 0xFD4 0xFD8 0xFDC 0xFE0 0xFE4 0xFE8 0xFEC 0xFF0 0xFF4 0xFF8 0xFFC Name SSIDMACTL SSICC SSIPeriphID4 SSIPeriphID5 SSIPeriphID6 SSIPeriphID7 SSIPeriphID0 SSIPeriphID1 SSIPeriphID2 SSIPeriphID3 SSIPCellID0 SSIPCellID1 SSIPCellID2 SSIPCellID3 Type R/W R/W RO RO RO RO RO RO RO RO RO RO RO RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0022 0x0000.0000 0x0000.0018 0x0000.0001 0x0000.000D 0x0000.00F0 0x0000.0005 0x0000.00B1 Description SSI DMA Control SSI Clock Configuration SSI Peripheral Identification 4 SSI Peripheral Identification 5 SSI Peripheral Identification 6 SSI Peripheral Identification 7 SSI Peripheral Identification 0 SSI Peripheral Identification 1 SSI Peripheral Identification 2 SSI Peripheral Identification 3 SSI PrimeCell Identification 0 SSI PrimeCell Identification 1 SSI PrimeCell Identification 2 SSI PrimeCell Identification 3 See page 953 954 955 956 957 958 959 960 961 962 963 964 965 966
15.6
The remainder of this section lists and describes the SSI registers, in numerical order by address offset.
April 25, 2012
Register 1: SSI Control 0 (SSICR0), offset 0x000

The SSICR0 register contains bit fields that control various functions within the SSI module. Functionality such as protocol mode, clock rate, and data size are configured in this register.
SSI Control 0 (SSICR0)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 SCR Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 SPH R/W 0 RO 0 6 SPO R/W 0 R/W 0 RO 0 5 FRF R/W 0 R/W 0 R/W 0 RO 0 4 RO 0 3 RO 0 2 DSS R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Serial Clock Rate This bit field is used to generate the transmit and receive bit rate of the SSI. The bit rate is: BR=SysClk/(CPSDVSR * (1 + SCR)) where CPSDVSR is an even value from 2-254 programmed in the SSICPSR register, and SCR is a value from 0-255.
15:8
SCR
R/W
0x00
SPH
R/W
SSI Serial Clock Phase This bit is only applicable to the Freescale SPI Format. The SPH control bit selects the clock edge that captures data and allows it to change state. This bit has the most impact on the first bit transmitted by either allowing or not allowing a clock transition before the first data capture edge. Value Description 0 1 Data is captured on the first clock edge transition. Data is captured on the second clock edge transition.
SPO
R/W
SSI Serial Clock Polarity Value Description 0 1 A steady state Low value is placed on the SSIClk pin. A steady state High value is placed on the SSIClk pin when data is not being transferred.
939
Bit/Field 5:4
Name FRF
Type R/W
Reset 0x0
Description SSI Frame Format Select Value Frame Format 0x0 0x1 0x2 0x3 Freescale SPI Frame Format Texas Instruments Synchronous Serial Frame Format MICROWIRE Frame Format Reserved
3:0
DSS
R/W
0x0
SSI Data Size Select Value Data Size
0x0-0x2 Reserved 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF 4-bit data 5-bit data 6-bit data 7-bit data 8-bit data 9-bit data 10-bit data 11-bit data 12-bit data 13-bit data 14-bit data 15-bit data 16-bit data
April 25, 2012
Register 2: SSI Control 1 (SSICR1), offset 0x004

The SSICR1 register contains bit fields that control various functions within the SSI module. Master and slave mode functionality is controlled by this register.
SSI Control 1 (SSICR1)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 SLBY6 RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 EOT R/W 0 RO 0 3 SOD R/W 0 RO 0 2 MS R/W 0 RO 0 1 SSE R/W 0 RO 0 0 LBM R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Slave Bypass Mode Value Description 0 1 SSI Module operates standard mode such that the slave is clocked at a 12:1 ratio of system clock to SSInCLK. SSI module functions such that the slave operates at a 6:1 ratio of system clock to SSInCLK.
SLBY6
R/W
EOT
R/W
End of Transmission Value Description 0 1 The TXRIS interrupt indicates that the transmit FIFO is half full or less. The End of Transmit interrupt mode for the TXRIS interrupt is enabled.
SOD
R/W
SSI Slave Mode Output Disable This bit is relevant only in the Slave mode (MS=1). In multiple-slave systems, it is possible for the SSI master to broadcast a message to all slaves in the system while ensuring that only one slave drives data onto the serial output line. In such systems, the TXD lines from multiple slaves could be tied together. To operate in such a system, the SOD bit can be configured so that the SSI slave does not drive the SSITx pin. Value Description 0 1 SSI can drive the SSITx output in Slave mode. SSI must not drive the SSITx output in Slave mode.
941
Bit/Field 2
Name MS
Type R/W
Reset 0
Description SSI Master/Slave Select This bit selects Master or Slave mode and can be modified only when the SSI is disabled (SSE=0). Value Description 0 1 The SSI is configured as a master. The SSI is configured as a slave.
SSE
R/W
SSI Synchronous Serial Port Enable Value Description 0 1 SSI operation is disabled. SSI operation is enabled. Note: This bit must be cleared before any control registers are reprogrammed.
LBM
R/W
SSI Loopback Mode Value Description 0 1 Normal serial port operation enabled. Output of the transmit serial shift register is connected internally to the input of the receive serial shift register.
April 25, 2012
Register 3: SSI Data (SSIDR), offset 0x008

Important: This register is read-sensitive. See the register description for details. The SSIDR register is 16-bits wide. When the SSIDR register is read, the entry in the receive FIFO that is pointed to by the current FIFO read pointer is accessed. When a data value is removed by the SSI receive logic from the incoming data frame, it is placed into the entry in the receive FIFO pointed to by the current FIFO write pointer. When the SSIDR register is written to, the entry in the transmit FIFO that is pointed to by the write pointer is written to. Data values are removed from the transmit FIFO one value at a time by the transmit logic. Each data value is loaded into the transmit serial shifter, then serially shifted out onto the SSITx pin at the programmed bit rate. When a data size of less than 16 bits is selected, the user must right-justify data written to the transmit FIFO. The transmit logic ignores the unused bits. Received data less than 16 bits is automatically right-justified in the receive buffer. When the SSI is programmed for MICROWIRE frame format, the default size for transmit data is eight bits (the most significant byte is ignored). The receive data size is controlled by the programmer. The transmit FIFO and the receive FIFO are not cleared even when the SSE bit in the SSICR1 register is cleared, allowing the software to fill the transmit FIFO before enabling the SSI.
SSI Data (SSIDR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 DATA Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Receive/Transmit Data A read operation reads the receive FIFO. A write operation writes the transmit FIFO. Software must right-justify data when the SSI is programmed for a data size that is less than 16 bits. Unused bits at the top are ignored by the transmit logic. The receive logic automatically right-justifies the data.
15:0
DATA
R/W
0x0000
943
Register 4: SSI Status (SSISR), offset 0x00C

The SSISR register contains bits that indicate the FIFO fill status and the SSI busy status.
SSI Status (SSISR)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0x00C Type RO, reset 0x0000.0003
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 BSY RO 0 RO 0 3 RFF RO 0 RO 0 2 RNE RO 0 RO 0 1 TNF RO 1 RO 0 0 TFE RO 1
Bit/Field 31:5
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Busy Bit Value Description 0 1 The SSI is idle. The SSI is currently transmitting and/or receiving a frame, or the transmit FIFO is not empty.
BSY
RO
RFF
RO
SSI Receive FIFO Full Value Description 0 1 The receive FIFO is not full. The receive FIFO is full.
RNE
RO
SSI Receive FIFO Not Empty Value Description 0 1 The receive FIFO is empty. The receive FIFO is not empty.
TNF
RO
SSI Transmit FIFO Not Full Value Description 0 1 The transmit FIFO is full. The transmit FIFO is not full.
April 25, 2012
Bit/Field 0
Name TFE
Type RO
Reset 1
Description SSI Transmit FIFO Empty Value Description 0 1 The transmit FIFO is not empty. The transmit FIFO is empty.
945
Register 5: SSI Clock Prescale (SSICPSR), offset 0x010

The SSICPSR register specifies the division factor which is used to derive the SSIClk from the system clock. The clock is further divided by a value from 1 to 256, which is 1 + SCR. SCR is programmed in the SSICR0 register. The frequency of the SSIClk is defined by: SSIClk = SysClk / (CPSDVSR * (1 + SCR)) The value programmed into this register must be an even number between 2 and 254. The least-significant bit of the programmed number is hard-coded to zero. If an odd number is written to this register, data read back from this register has the least-significant bit as zero.
SSI Clock Prescale (SSICPSR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0
CPSDVSR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Clock Prescale Divisor This value must be an even number from 2 to 254, depending on the frequency of SSIClk. The LSB always returns 0 on reads.
7:0
CPSDVSR
R/W
0x00
April 25, 2012
Register 6: SSI Interrupt Mask (SSIIM), offset 0x014

The SSIIM register is the interrupt mask set or clear register. It is a read/write register and all bits are cleared on reset. On a read, this register gives the current value of the mask on the corresponding interrupt. Setting a bit sets the mask, preventing the interrupt from being signaled to the interrupt controller. Clearing a bit clears the corresponding mask, enabling the interrupt to be sent to the interrupt controller.
SSI Interrupt Mask (SSIIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 TXIM R/W 0 RO 0 2 RXIM R/W 0 RO 0 1 RTIM R/W 0 RO 0 0 RORIM R/W 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Transmit FIFO Interrupt Mask Value Description 0 1 The transmit FIFO interrupt is masked. The transmit FIFO interrupt is not masked.
TXIM
R/W
RXIM
R/W
SSI Receive FIFO Interrupt Mask Value Description 0 1 The receive FIFO interrupt is masked. The receive FIFO interrupt is not masked.
RTIM
R/W
SSI Receive Time-Out Interrupt Mask Value Description 0 1 The receive FIFO time-out interrupt is masked. The receive FIFO time-out interrupt is not masked.
RORIM
R/W
SSI Receive Overrun Interrupt Mask Value Description 0 1 The receive FIFO overrun interrupt is masked. The receive FIFO overrun interrupt is not masked.
947
Register 7: SSI Raw Interrupt Status (SSIRIS), offset 0x018

The SSIRIS register is the raw interrupt status register. On a read, this register gives the current raw status value of the corresponding interrupt prior to masking. A write has no effect.
SSI Raw Interrupt Status (SSIRIS)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0x018 Type RO, reset 0x0000.0008
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 TXRIS RO 1 RO 0 2 RXRIS RO 0 RO 0 1 RTRIS RO 0 RO 0 0 RORRIS RO 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Transmit FIFO Raw Interrupt Status Value Description 0 1 No interrupt. If the EOT bit in the SSICR1 register is clear, the transmit FIFO is half empty or less. If the EOT bit is set, the transmit FIFO is empty, and the last bit has been transmitted out of the serializer. This bit is cleared when the transmit FIFO is more than half full (if the EOT bit is clear) or when it has any data in it (if the EOT bit is set).
TXRIS
RO
RXRIS
RO
SSI Receive FIFO Raw Interrupt Status Value Description 0 1 No interrupt. The receive FIFO is half full or more.
This bit is cleared when the receive FIFO is less than half full. 1 RTRIS RO 0 SSI Receive Time-Out Raw Interrupt Status Value Description 0 1 No interrupt. The receive time-out has occurred.
This bit is cleared when a 1 is written to the RTIC bit in the SSI Interrupt Clear (SSIICR) register.
April 25, 2012
Bit/Field 0
Name RORRIS
Type RO
Reset 0
Description SSI Receive Overrun Raw Interrupt Status Value Description 0 1 No interrupt. The receive FIFO has overflowed
This bit is cleared when a 1 is written to the RORIC bit in the SSI Interrupt Clear (SSIICR) register.
949
Register 8: SSI Masked Interrupt Status (SSIMIS), offset 0x01C

The SSIMIS register is the masked interrupt status register. On a read, this register gives the current masked status value of the corresponding interrupt. A write has no effect.
SSI Masked Interrupt Status (SSIMIS)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0x01C Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 TXMIS RO 0 RO 0 2 RXMIS RO 0 RO 0 1 RTMIS RO 0 RO 0 0 RORMIS RO 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Transmit FIFO Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to the transmit FIFO being half empty or less (if the EOT bit is clear) or due to the transmission of the last data bit (if the EOT bit is set).
TXMIS
RO
This bit is cleared when the transmit FIFO is more than half empty (if the EOT bit is clear) or when it has any data in it (if the EOT bit is set). 2 RXMIS RO 0 SSI Receive FIFO Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to the receive FIFO being half full or more.
This bit is cleared when the receive FIFO is less than half full. 1 RTMIS RO 0 SSI Receive Time-Out Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to the receive time out.
This bit is cleared when a 1 is written to the RTIC bit in the SSI Interrupt Clear (SSIICR) register.
April 25, 2012
Bit/Field 0
Name RORMIS
Type RO
Reset 0
Description SSI Receive Overrun Masked Interrupt Status Value Description 0 1 An interrupt has not occurred or is masked. An unmasked interrupt was signaled due to the receive FIFO overflowing.
This bit is cleared when a 1 is written to the RORIC bit in the SSI Interrupt Clear (SSIICR) register.
951
Register 9: SSI Interrupt Clear (SSIICR), offset 0x020

The SSIICR register is the interrupt clear register. On a write of 1, the corresponding interrupt is cleared. A write of 0 has no effect.
SSI Interrupt Clear (SSIICR)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0x020 Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RTIC W1C 0 RO 0 0 RORIC W1C 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Receive Time-Out Interrupt Clear Writing a 1 to this bit clears the RTRIS bit in the SSIRIS register and the RTMIS bit in the SSIMIS register.
RTIC
W1C
RORIC
W1C
SSI Receive Overrun Interrupt Clear Writing a 1 to this bit clears the RORRIS bit in the SSIRIS register and the RORMIS bit in the SSIMIS register.
April 25, 2012
Register 10: SSI DMA Control (SSIDMACTL), offset 0x024

The SSIDMACTL register is the DMA control register.
SSI DMA Control (SSIDMACTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
TXDMAE RXDMAE R/W 0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Transmit DMA Enable Value Description 0 1 DMA for the transmit FIFO is disabled. DMA for the transmit FIFO is enabled.
TXDMAE
R/W
RXDMAE
R/W
Receive DMA Enable Value Description 0 1 DMA for the receive FIFO is disabled. DMA for the receive FIFO is enabled.
953
Register 11: SSI Clock Configuration (SSICC), offset 0xFC8

The SSICC register controls the baud clock source for the SSI module. Note: If the PIOSC is used for the SSI baud clock, the system clock frequency must be at least 16 MHz in Run mode.
SSI Clock Configuration (SSICC)

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFC8 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Baud Clock Source The following table specifies the source that generates for the SSI baud clock: Value 0x0 0x1-0x4 0x5 Description System clock (based on clock source and divisor factor) reserved PIOSC
3:0
CS
R/W
0x6 - 0xF Reserved
April 25, 2012
Register 12: SSI Peripheral Identification 4 (SSIPeriphID4), offset 0xFD0

The SSIPeriphIDn registers are hard-coded and the fields within the register determine the reset value.
SSI Peripheral Identification 4 (SSIPeriphID4)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFD0 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI Peripheral ID Register [7:0] Can be used by software to identify the presence of this peripheral.
7:0
PID4
RO
0x00
955

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID5
RO
0x00
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID6
RO
0x00
957
Register 15: SSI Peripheral Identification 7 (SSIPeriphID7), offset 0xFDC

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFDC Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID7
RO
0x00
April 25, 2012
Register 16: SSI Peripheral Identification 0 (SSIPeriphID0), offset 0xFE0

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFE0 Type RO, reset 0x0000.0022
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID0
RO
0x22
959

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID1
RO
0x00
April 25, 2012

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID2
RO
0x18
961
Register 19: SSI Peripheral Identification 3 (SSIPeriphID3), offset 0xFEC

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFEC Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
PID3
RO
0x01
April 25, 2012
Register 20: SSI PrimeCell Identification 0 (SSIPCellID0), offset 0xFF0

The SSIPCellIDn registers are hard-coded, and the fields within the register determine the reset value.
SSI PrimeCell Identification 0 (SSIPCellID0)
SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFF0 Type RO, reset 0x0000.000D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. SSI PrimeCell ID Register [7:0] Provides software a standard cross-peripheral identification system.
7:0
CID0
RO
0x0D
963

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFF4 Type RO, reset 0x0000.00F0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID1
RO
0xF0
April 25, 2012

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFF8 Type RO, reset 0x0000.0005
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID2
RO
0x05
965
Register 23: SSI PrimeCell Identification 3 (SSIPCellID3), offset 0xFFC

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000 Offset 0xFFC Type RO, reset 0x0000.00B1
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
7:0
CID3
RO
0xB1
April 25, 2012
16
Inter-Integrated Circuit (I2C) Interface

The Inter-Integrated Circuit (I2C) bus provides bi-directional data transfer through a two-wire design (a serial data line SDA and a serial clock line SCL), and interfaces to external I2C devices such as serial memory (RAMs and ROMs), networking devices, LCDs, tone generators, and so on. The I2C bus may also be used for system testing and diagnostic purposes in product development and manufacture. The LM4F120H5QR microcontroller includes providing the ability to interact (both transmit and receive) with other I2C devices on the bus. The Stellaris LM4F120H5QR controller includes I2C modules with the following features: Devices on the I2C bus can be designated as either a master or a slave Supports both transmitting and receiving data as either a master or a slave Supports simultaneous master and slave operation Four I2C modes Master transmit Master receive Slave transmit Slave receive Four transmission speeds: Standard (100 Kbps) Fast-mode (400 Kbps) Fast-mode plus (1 Mbps) High-speed mode (3.33 Mbps) Clock low timeout interrupt Dual slave address capability Clock low timeout interrupt Dual slave address capability Master and slave interrupt generation Master generates interrupts when a transmit or receive operation completes (or aborts due to an error) Slave generates interrupts when data has been transferred or requested by a master or when a START or STOP condition is detected Master with arbitration and clock synchronization, multimaster support, and 7-bit addressing mode
967
16.1
Block Diagram
Figure 16-1. I2C Block Diagram
I2C Control I2CMSA I2CMCS I2CMDR Interrupt I2CMTPR I2CMIMR I2CMRIS I2CMMIS I2CMICR I2CMCR I2CMCLKOCNT I2CMBMON I2CPP I2CSOAR I2CSCSR I2CSDR I2CSIMR I2CSRIS I2CSMIS I2CSICR I2CSSOAR2 I2CSACKCTL I C Slave Core
2
I2CSCL I C Master Core I2CSDA I2CSCL I2C I/O Select I2CSDA I2CSCL
2
I2CSDA
16.2
Signal Description
The following table lists the external signals of the I2C interface and describes the function of each. The I2C interface signals are alternate functions for some GPIO signals and default to be GPIO signals at reset, with the exception of the I2C0SCL and I2CSDA pins which default to the I2C function. The column in the table below titled "Pin Mux/Pin Assignment" lists the possible GPIO pin placements for the I2C signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the I2C function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the I2C signal to the specified GPIO port pin. Note that the I2CSCL pin should be set to open drain using the GPIO Open Drain Select (GPIOODR) register. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
Table 16-1. I2C Signals (64LQFP)

Pin Name I2C0SCL Pin Number Pin Mux / Pin Assignment 47 PB2 (3) Pin Type I/O Buffer Type OD
a
Description I2C module 0 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 0 data. I2C module 1 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 1 data. I2C module 2 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 2 data.
I2C0SDA I2C1SCL
48 23
PB3 (3) PA6 (3)
I/O I/O
OD OD
I2C1SDA I2C2SCL
24 59
PA7 (3) PE4 (3)
I/O I/O
OD OD
I2C2SDA
60
PE5 (3)
I/O
OD
April 25, 2012
Table 16-1. I2C Signals (64LQFP) (continued)

Pin Name I2C3SCL Pin Number Pin Mux / Pin Assignment 61 PD0 (3) Pin Type I/O Buffer Type OD
a
Description I2C module 3 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 3 data.
I2C3SDA
62
PD1 (3)
I/O
OD
16.3
Each I2C module is comprised of both master and slave functions. For proper operation, the SDA pin must be configured as an open-drain signal. Due to the internal circuitry that supports high-speed operation, the SCL pin must not be configured as an open-drain signal, although the internal circuitry causes it to act as if it were an open drain signal. A typical I2C bus configuration is shown in Figure 16-2. Refer to the I2C-bus specification and user manual to determine the size of the pull-ups needed for proper operation. See Inter-Integrated Circuit (I2C) Interface on page 1178 for I2C timing diagrams. Figure 16-2. I2C Bus Configuration
SCL SDA
I2CSCL I2CSDA
RPUP
RPUP
I2C Bus
SCL SDA SCL SDA
Stellaris
3rd Party Device with I2C Interface
3rd Party Device with I2C Interface
16.3.1
I2C Bus Functional Overview

The I2C bus uses only two signals: SDA and SCL, named I2CSDA and I2CSCL on Stellaris microcontrollers. SDA is the bi-directional serial data line and SCL is the bi-directional serial clock line. The bus is considered idle when both lines are High. Every transaction on the I2C bus is nine bits long, consisting of eight data bits and a single acknowledge bit. The number of bytes per transfer (defined as the time between a valid START and STOP condition, described in START and STOP Conditions on page 969) is unrestricted, but each byte has to be followed by an acknowledge bit, and data must be transferred MSB first. When a receiver cannot receive another complete byte, it can hold the clock line SCL Low and force the transmitter into a wait state. The data transfer continues when the receiver releases the clock SCL.
16.3.1.1
START and STOP Conditions

The protocol of the I2C bus defines two states to begin and end a transaction: START and STOP. A High-to-Low transition on the SDA line while the SCL is High is defined as a START condition, and a Low-to-High transition on the SDA line while SCL is High is defined as a STOP condition. The bus is considered busy after a START condition and free after a STOP condition. See Figure 16-3.
969
Figure 16-3. START and STOP Conditions

SDA SCL
START condition STOP condition
SDA SCL
The STOP bit determines if the cycle stops at the end of the data cycle or continues on to a repeated START condition. To generate a single transmit cycle, the I2C Master Slave Address (I2CMSA) register is written with the desired address, the R/S bit is cleared, and the Control register is written with ACK=X (0 or 1), STOP=1, START=1, and RUN=1 to perform the operation and stop. When the operation is completed (or aborted due an error), the interrupt pin becomes active and the data may be read from the I2C Master Data (I2CMDR) register. When the I2C module operates in Master receiver mode, the ACK bit is normally set causing the I2C bus controller to transmit an acknowledge automatically after each byte. This bit must be cleared when the I2C bus controller requires no further data to be transmitted from the slave transmitter. When operating in slave mode, two bits in the I2C Slave Raw Interrupt Status (I2CSRIS) register indicate detection of start and stop conditions on the bus; while two bits in the I2C Slave Masked Interrupt Status (I2CSMIS) register allow start and stop conditions to be promoted to controller interrupts (when interrupts are enabled).
16.3.1.2
Data Format with 7-Bit Address

Data transfers follow the format shown in Figure 16-4. After the START condition, a slave address is transmitted. This address is 7-bits long followed by an eighth bit, which is a data direction bit (R/S bit in the I2CMSA register). If the R/S bit is clear, it indicates a transmit operation (send), and if it is set, it indicates a request for data (receive). A data transfer is always terminated by a STOP condition generated by the master, however, a master can initiate communications with another device on the bus by generating a repeated START condition and addressing another slave without first generating a STOP condition. Various combinations of receive/transmit formats are then possible within a single transfer. Figure 16-4. Complete Data Transfer with a 7-Bit Address
SDA
MSB LSB R/S ACK MSB LSB ACK
SCL
Start
2
Slave address
2
Data
9
Stop
The first seven bits of the first byte make up the slave address (see Figure 16-5). The eighth bit determines the direction of the message. A zero in the R/S position of the first byte means that the master transmits (sends) data to the selected slave, and a one in this position means that the master receives data from the slave.
April 25, 2012
Figure 16-5. R/S Bit in First Byte

MSB LSB R/S Slave address
16.3.1.3
Data Validity
The data on the SDA line must be stable during the high period of the clock, and the data line can only change when SCL is Low (see Figure 16-6). Figure 16-6. Data Validity During Bit Transfer on the I2C Bus
SDA
SCL
ge Data line Chan stable of data allowed
16.3.1.4
Acknowledge
All bus transactions have a required acknowledge clock cycle that is generated by the master. During the acknowledge cycle, the transmitter (which can be the master or slave) releases the SDA line. To acknowledge the transaction, the receiver must pull down SDA during the acknowledge clock cycle. The data transmitted out by the receiver during the acknowledge cycle must comply with the data validity requirements described in Data Validity on page 971. When a slave receiver does not acknowledge the slave address, SDA must be left High by the slave so that the master can generate a STOP condition and abort the current transfer. If the master device is acting as a receiver during a transfer, it is responsible for acknowledging each transfer made by the slave. Because the master controls the number of bytes in the transfer, it signals the end of data to the slave transmitter by not generating an acknowledge on the last data byte. The slave transmitter must then release SDA to allow the master to generate the STOP or a repeated START condition. If the slave is required to provide a manual ACK or NACK, the I2C Slave ACK Control (I2CSACKCTL) register allows the slave to NACK for invalid data or command or ACK for valid data or command. When this operation is enabled, the I2C clock is pulled low after the last data bit until this register is written with the indicated response.
16.3.1.5
Clock Low Timeout

The I2C slave can extend the transaction by pulling the clock low periodically to create a slow bit transfer rate. The I2C module has a 12-bit programmable counter that is used to track how long the clock has been held low. The upper 8 bits of the count value are software programmable through the I2C Master Clock Low Timeout Count (I2CMCLKOCNT) register. Application can program the 8 most significant bits of the counter to reflect the acceptable cumulative low period in transaction. The count is loaded at the START condition and counts down on each falling edge of the internal bus clock of the master. Note that the internal bus clock generated for this counter keeps running at the programmed I2C speed even if the SCL is held low on the bus. Upon reaching terminal count,
971
the master state machine forces Abort on the bus by issuing a STOP condition at the instance of SCL and SDA release. As an example, if an I2C module was operating at 100 kHz speed, programming the I2CMCLKOCNT register to 0xDA would result in a cumulative clock low period of 34.88 ms. The CLKRIS bit in the I2C Master Raw Interrupt Status (I2CMRIS) register is set when the clock timeout period is reached, allowing the master to start corrective action to resolve the remote slave state. In addition, the CLKTO bit in the I2C Master Control/Status (I2CMCS) register is set; this bit is cleared when a STOP condition is sent or during the I2C master reset.. The status of the raw SDA and SCL signals are readable by software through the SDA and SCL bits in the I2C Master Bus Monitor (I2CMBMON) register to help determine the state of the remote slave. If the slave holds the clock low continuously, the only solution is to interrupt the processor using the CLKRIS bit and resolve the condition at higher protocol levels by resetting both the master and the remote slave.
16.3.1.6
Dual Address
The I2C interface supports dual address capability for the slave. The additional programmable address is provided and can be matched if enabled. In legacy mode with dual address disabled, the I2C slave provides an ACK on the bus if the address matches the OAR field in the I2CSOAR register. In dual address mode, the I2C slave provides an ACK on the bus if either the OAR field in the I2CSOAR register or the OAR2 field in the I2CSOAR2 register is matched. The enable for dual address is programmable through the OAR2EN bit in the I2CSOAR2 register and there is no disable on the legacy address. The OAR2SEL bit in the I2CSCSR register indicates if the address that was ACKed is the alternate address or not. When this bit is clear, it indicates either legacy operation or no address match.
16.3.1.7
Arbitration
A master may start a transfer only if the bus is idle. It's possible for two or more masters to generate a START condition within minimum hold time of the START condition. In these situations, an arbitration scheme takes place on the SDA line, while SCL is High. During arbitration, the first of the competing master devices to place a '1' (High) on SDA while another master transmits a '0' (Low) switches off its data output stage and retires until the bus is idle again. Arbitration can take place over several bits. Its first stage is a comparison of address bits, and if both masters are trying to address the same device, arbitration continues on to the comparison of data bits.
16.3.1.8
High-Speed Operation
The Stellaris I2C peripheral has support for High-speed operation as both a master and slave. When operating as a master, the protocol is shown in Figure 16-7. The master is responsible for sending a master code byte in either Standard (100 Kbps) or Fast-mode (400 Kbps) before it begins transferring in High-speed mode. The master code byte must contain data in the form of 0000.1XXX and is used to tell the slave devices to prepare for a High-speed transfer. The master code byte should never be acknowledged by a slave since it is only used to indicate that the upcoming data is going to be transferred at a higher data rate. To send the master code byte, software should place the value of the master code byte into the I2CMSA register and write the I2CMCS register with a value of 0x11. This places the I2C master peripheral in High-speed mode, and all subsequent transfers (until STOP) are carried out at High-speed data rate using the normal I2CMCS command bits, without setting the HS bit in the I2CMCS register. Again, setting the HS bit in the I2CMCS register is only necessary during the master code byte.
April 25, 2012
When operating as a High-speed slave, there is no additional software required. Figure 16-7. High-Speed Data Format
SDA Device-Specific SCL NAK Address R/W Data
Standard (100 KHz) or Fast Mode (400 KHz)
High Speed (3.3 Mbps)
Note:
High-Speed mode is 3.4 Mbps, provided correct system clock frequency is set and there is appropriate pull strength on SCL and SDA lines.
16.3.2
Available Speed Modes

The I2C bus can run in Standard mode (100 kbps), Fast mode (400 kbps), Fast mode plus (1 Mbps) or High-Speed mode (3.33 Mbps). The selected mode should match the speed of the other I2C devices on the bus.
16.3.2.1
Standard, Fast, and Fast Plus Modes

Standard, Fast, and Fast Plus modes are selected using a value in the I2C Master Timer Period (I2CMTPR) register that results in an SCL frequency of 100 kbps for Standard mode, 400 kbps for Fast mode, or 1 Mbps for Fast mode plus. The I2C clock rate is determined by the parameters CLK_PRD, TIMER_PRD, SCL_LP, and SCL_HP where: CLK_PRD is the system clock period SCL_LP is the low phase of SCL (fixed at 6) SCL_HP is the high phase of SCL (fixed at 4) TIMER_PRD is the programmed value in the I2CMTPR register (see page 994). The I2C clock period is calculated as follows: SCL_PERIOD = 2 (1 + TIMER_PRD) (SCL_LP + SCL_HP) CLK_PRD For example: CLK_PRD = 50 ns TIMER_PRD = 2 SCL_LP=6 SCL_HP=4 yields a SCL frequency of: 1/SCL_PERIOD = 333 Khz Table 16-2 gives examples of the timer periods that should be used to generate Standard, Fast mode, and Fast mode plus SCL frequencies based on various system clock frequencies.
973
Table 16-2. Examples of I2C Master Timer Period versus Speed Mode
System Clock 4 MHz 6 MHz 12.5 MHz 16.7 MHz 20 MHz 25 MHz 33 MHz 40 MHz 50 MHz 80 MHz Timer Period 0x01 0x02 0x06 0x08 0x09 0x0C 0x10 0x13 0x18 0x27 Standard Mode 100 Kbps 100 Kbps 89 Kbps 93 Kbps 100 Kbps 96.2 Kbps 97.1 Kbps 100 Kbps 100 Kbps 100 Kbps Timer Period 0x01 0x02 0x02 0x03 0x04 0x04 0x06 0x09 Fast Mode 312 Kbps 278 Kbps 333 Kbps 312 Kbps 330 Kbps 400 Kbps 357 Kbps 400 Kbps Timer Period 0x01 0x02 0x03 Fast Mode Plus 1000 Kbps 833 Kbps 1000 Kbps
16.3.2.2
High-Speed Mode
High-Speed mode is configured by setting the HS bit in the I2C Master Control/Status (I2CMCS) register. High-Speed mode transmits data at a high bit rate with a 66.6%/33.3% duty cycle, but communication and arbitration are done at Standard, Fast mode, or Fast-mode plus speed, depending on which is selected by the user. When the HS bit in the I2CMCS register is set, current mode pull-ups are enabled. The clock period can be selected using the equation above, but in this case, SCL_LP=2 and SCL_HP=1. So for example: CLK_PRD = 25 ns TIMER_PRD = 1 SCL_LP=2 SCL_HP=1 yields a SCL frequency of: 1/T = 3.33 Mhz Table 16-3 on page 974 gives examples of timer period and system clock in High-Speed mode. Table 16-3. Examples of I2C Master Timer Period in High-Speed Mode
System Clock 40 MHz 50 MHz 80 MHz Timer Period 0x01 0x02 0x03 Transmission Mode 3.33 Mbps 2.77 Mbps 3.33 Mbps
16.3.3
Interrupts
The I2C can generate interrupts when the following conditions are observed: Master transaction completed Master arbitration lost Master transaction error
April 25, 2012
Master bus timeout Slave transaction received Slave transaction requested Stop condition on bus detected Start condition on bus detected The I2C master and I2C slave modules have separate interrupt signals. While both modules can generate interrupts for multiple conditions, only a single interrupt signal is sent to the interrupt controller.
16.3.3.1
I2C Master Interrupts

The I2C master module generates an interrupt when a transaction completes (either transmit or receive), when arbitration is lost, or when an error occurs during a transaction. To enable the I2C master interrupt, software must set the IM bit in the I2C Master Interrupt Mask (I2CMIMR) register. When an interrupt condition is met, software must check the ERROR and ARBLST bits in the I2C Master Control/Status (I2CMCS) register to verify that an error didn't occur during the last transaction and to ensure that arbitration has not been lost. An error condition is asserted if the last transaction wasn't acknowledged by the slave. If an error is not detected and the master has not lost arbitration, the application can proceed with the transfer. The interrupt is cleared by writing a 1 to the IC bit in the I2C Master Interrupt Clear (I2CMICR) register. If the application doesn't require the use of interrupts, the raw interrupt status is always visible via the I2C Master Raw Interrupt Status (I2CMRIS) register.
16.3.3.2
I2C Slave Interrupts

The slave module can generate an interrupt when data has been received or requested. This interrupt is enabled by setting the DATAIM bit in the I2C Slave Interrupt Mask (I2CSIMR) register. Software determines whether the module should write (transmit) or read (receive) data from the I2C Slave Data (I2CSDR) register, by checking the RREQ and TREQ bits of the I2C Slave Control/Status (I2CSCSR) register. If the slave module is in receive mode and the first byte of a transfer is received, the FBR bit is set along with the RREQ bit. The interrupt is cleared by setting the DATAIC bit in the I2C Slave Interrupt Clear (I2CSICR) register. In addition, the slave module can generate an interrupt when a start and stop condition is detected. These interrupts are enabled by setting the STARTIM and STOPIM bits of the I2C Slave Interrupt Mask (I2CSIMR) register and cleared by writing a 1 to the STOPIC and STARTIC bits of the I2C Slave Interrupt Clear (I2CSICR) register. If the application doesn't require the use of interrupts, the raw interrupt status is always visible via the I2C Slave Raw Interrupt Status (I2CSRIS) register.
16.3.4
Loopback Operation
The I2C modules can be placed into an internal loopback mode for diagnostic or debug work by setting the LPBK bit in the I2C Master Configuration (I2CMCR) register. In loopback mode, the SDA and SCL signals from the master and slave modules are tied together.
975
16.3.5
Command Sequence Flow Charts

This section details the steps required to perform the various I2C transfer types in both master and slave mode.
16.3.5.1
I2C Master Command Sequences

The figures that follow show the command sequences available for the I2C master.
April 25, 2012
Figure 16-8. Master Single TRANSMIT

Idle
Write Slave Address to I2CMSA
Sequence may be omitted in a Single Master system
Write data to I2CMDR
Read I2CMCS
NO
BUSBSY bit=0?
YES
Write ---0-111 to I2CMCS
Read I2CMCS
NO
BUSY bit=0?
YES
Error Service
NO
ERROR bit=0?
YES
Idle
977
Figure 16-9. Master Single RECEIVE

Idle
Read I2CMCS
NO
BUSBSY bit=0?
YES
Write ---00111 to I2CMCS
Read I2CMCS
NO
BUSY bit=0?
YES
Error Service
NO
ERROR bit=0?
YES
Read data from I2CMDR
Idle
April 25, 2012
Figure 16-10. Master TRANSMIT with Repeated START

Idle
Read I2CMCS
BUSY bit=0?
NO
Read I2CMCS
YES
ERROR bit=0?
NO
NO
BUSBSY bit=0?
YES
YES
NO
ARBLST bit=1?
Write ---0-011 to I2CMCS Write ---0-001 to I2CMCS

NO
YES
Index=n?
YES
Error Service
Idle
Read I2CMCS
NO
BUSY bit=0?
YES
Error Service
NO
ERROR bit=0?
YES
Idle
979
Figure 16-11. Master RECEIVE with Repeated START

Idle Sequence may be omitted in a Single Master system
Read I2CMCS
Read I2CMCS
BUSY bit=0?
NO
YES
NO
BUSBSY bit=0? ERROR bit=0?

YES
NO
NO
ARBLST bit=1?
YES
NO
Write ---0-100 to I2CMCS Index=m-1? Error Service

YES
Idle
Read I2CMCS
BUSY bit=0?
NO
YES
NO
ERROR bit=0?
YES
Error Service
Idle
April 25, 2012
Figure 16-12. Master RECEIVE with Repeated START after TRANSMIT with Repeated START
Idle
Master operates in Master Transmit mode STOP condition is not generated
Write ---01011 to I2CMCS Repeated START condition is generated with changing data direction
Master operates in Master Receive mode
Idle
981
Figure 16-13. Master TRANSMIT with Repeated START after RECEIVE with Repeated START
Idle
Master operates in Master Receive mode STOP condition is not generated
Write ---0-011 to I2CMCS Repeated START condition is generated with changing data direction
Master operates in Master Transmit mode
Idle
April 25, 2012
Figure 16-14. High Speed Mode Master Transmit

IDLE
write slave address to I2MSA register Master code and arbitration is always done in FAST or STANDARD mode
write ---10001 to I2CMCS register
read I2CMCS register
no
Busy=0'
yes
no
Error=0'
IDLE
yes
Normal sequence starts here. The sequence below covers SINGLE send
write Slave Address to I2MSA register
write Data to I2CMDR register
write ---0-111 to I2CMCS register
read I2CMCS register
no
Busy=0'
yes
yes
Error=0'
no
IDLE
Error service
IDLE
983
16.3.5.2
I2C Slave Command Sequences

Figure 16-15 on page 984 presents the command sequence available for the I2C slave. Figure 16-15. Slave Command Sequence
Idle
Write OWN Slave Address to I2CSOAR
Write -------1 to I2CSCSR
Read I2CSCSR
NO
TREQ bit=1?
NO
RREQ bit=1?
YES
FBR is also valid
YES
Write data to I2CSDR
Read data from I2CSDR
16.4

The following example shows how to configure the I2C module to transmit a single byte as a master. This assumes the system clock is 20 MHz. 1. Enable the I2C clock using the RCGCI2C register in the System Control module (see page 320). 2. Enable the clock to the appropriate GPIO module via the RCGCGPIO register in the System Control module (see page 312). To find out which GPIO port to enable, refer to Table 21-5 on page 1152. 3. In the GPIO module, enable the appropriate pins for their alternate function using the GPIOAFSEL register (see page 653). To determine which GPIOs to configure, see Table 21-4 on page 1148. 4. Enable the I2CSDA pin for open-drain operation. See page 658.
April 25, 2012
5. Configure the PMCn fields in the GPIOPCTL register to assign the I2C signals to the appropriate pins. See page 670 and Table 21-5 on page 1152. 6. Initialize the I2C Master by writing the I2CMCR register with a value of 0x0000.0010. 7. Set the desired SCL clock speed of 100 Kbps by writing the I2CMTPR register with the correct value. The value written to the I2CMTPR register represents the number of system clock periods in one SCL clock period. The TPR value is determined by the following equation: TPR = (System Clock/(2*(SCL_LP + SCL_HP)*SCL_CLK))-1; TPR = (20MHz/(2*(6+4)*100000))-1; TPR = 9 Write the I2CMTPR register with the value of 0x0000.0009. 8. Specify the slave address of the master and that the next operation is a Transmit by writing the I2CMSA register with a value of 0x0000.0076. This sets the slave address to 0x3B. 9. Place data (byte) to be transmitted in the data register by writing the I2CMDR register with the desired data. 10. Initiate a single byte transmit of the data from Master to Slave by writing the I2CMCS register with a value of 0x0000.0007 (STOP, START, RUN). 11. Wait until the transmission completes by polling the I2CMCS registers BUSBSY bit until it has been cleared. 12. Check the ERROR bit in the I2CMCS register to confirm the transmit was acknowledged.
16.5
Register Map
Table 16-4 on page 985 lists the I2C registers. All addresses given are relative to the I2C base address: I2C 0: 0x4002.0000 I2C 1: 0x4002.1000 I2C 2: 0x4002.2000 I2C 3: 0x4002.3000
Note that the I2C module clock must be enabled before the registers can be programmed (see page 320). There must be a delay of 3 system clocks after the I2C module clock is enabled before any I2C module registers are accessed. The hw_i2c.h file in the StellarisWare Driver Library uses a base address of 0x800 for the I2C slave registers. Be aware when using registers with offsets between 0x800 and 0x818 that StellarisWare uses an offset between 0x000 and 0x018 with the slave base address. Table 16-4. Inter-Integrated Circuit (I2C) Interface Register Map
Offset I2C Master 0x000 0x004 I2CMSA I2CMCS R/W R/W 0x0000.0000 0x0000.0020 I2C Master Slave Address I2C Master Control/Status 987 988 Name Type Reset Description See page
985
Table 16-4. Inter-Integrated Circuit (I2C) Interface Register Map (continued)

Offset 0x008 0x00C 0x010 0x014 0x018 0x01C 0x020 0x024 0x02C I2C Slave 0x800 0x804 0x808 0x80C 0x810 0x814 0x818 0x81C 0x820 I2CSOAR I2CSCSR I2CSDR I2CSIMR I2CSRIS I2CSMIS I2CSICR I2CSOAR2 I2CSACKCTL R/W RO R/W R/W RO RO WO R/W R/W 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 I2C Slave Own Address I2C Slave Control/Status I2C Slave Data I2C Slave Interrupt Mask I2C Slave Raw Interrupt Status I2C Slave Masked Interrupt Status I2C Slave Interrupt Clear I2C Slave Own Address 2 I2C Slave ACK Control 1002 1003 1005 1006 1007 1008 1009 1010 1011 Name I2CMDR I2CMTPR I2CMIMR I2CMRIS I2CMMIS I2CMICR I2CMCR I2CMCLKOCNT I2CMBMON Type R/W R/W R/W RO RO WO R/W R/W RO Reset 0x0000.0000 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0003 Description I2C Master Data I2C Master Timer Period I2C Master Interrupt Mask I2C Master Raw Interrupt Status I2C Master Masked Interrupt Status I2C Master Interrupt Clear I2C Master Configuration I2C Master Clock Low Timeout Count I2C Master Bus Monitor See page 993 994 995 996 997 998 999 1000 1001
I2C Status and Control 0xFC0 0xFC4 I2CPP I2CPC RO RO 0x0000.0001 0x0000.0001 I2C Peripheral Properties I2C Peripheral Configuration 1012 1013
16.6
Register Descriptions (I2C Master)

The remainder of this section lists and describes the I2C master registers, in numerical order by address offset.
April 25, 2012
Register 1: I2C Master Slave Address (I2CMSA), offset 0x000

This register consists of eight bits: seven address bits (A6-A0), and a Receive/Send bit, which determines if the next operation is a Receive (High), or Transmit (Low).
I2C Master Slave Address (I2CMSA)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x000 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 SA RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0 R/S R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Slave Address This field specifies bits A6 through A0 of the slave address.
7:1
SA
R/W
0x00
R/S
R/W
Receive/Send The R/S bit specifies if the next operation is a Receive (High) or Transmit (Low). Value Description 0 1 Transmit Receive
987
Register 2: I2C Master Control/Status (I2CMCS), offset 0x004

This register accesses status bits when read and control bits when written. When read, the status register indicates the state of the I2C bus controller. When written, the control register configures the I2C controller operation. The START bit generates the START or REPEATED START condition. The STOP bit determines if the cycle stops at the end of the data cycle or continues on to a repeated START condition. To generate a single transmit cycle, the I2C Master Slave Address (I2CMSA) register is written with the desired address, the R/S bit is cleared, and this register is written with ACK=X (0 or 1), STOP=1, START=1, and RUN=1 to perform the operation and stop. When the operation is completed (or aborted due an error), an interrupt becomes active and the data may be read from the I2CMDR register. When the I2C module operates in Master receiver mode, the ACK bit is normally set, causing the I2C bus controller to transmit an acknowledge automatically after each byte. This bit must be cleared when the I2C bus controller requires no further data to be transmitted from the slave transmitter. Read-Only Status Register
I2C Master Control/Status (I2CMCS)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x004 Type RO, reset 0x0000.0020
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 CLKTO RO 0 RO 0 RO 0 RO 0 RO 0 6 BUSBSY RO 0 RO 0 5 IDLE RO 1 RO 0 4 ARBLST RO 0 RO 0 3 RO 0 2 RO 0 1 ERROR RO 0 RO 0 0 BUSY RO 0
DATACK ADRACK RO 0 RO 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Timeout Error Value Description 0 1 No clock timeout error. The clock timeout error has occurred.
CLKTO
RO
This bit is cleared when the master sends a STOP condition or if the I2C master is reset.
April 25, 2012
Bit/Field 6
Name BUSBSY
Type RO
Reset 0
Description Bus Busy Value Description 0 1 The I2C bus is idle. The I2C bus is busy.
The bit changes based on the START and STOP conditions. 5 IDLE RO 1 I2C Idle Value Description 0 1 The I2C controller is not idle. The I2C controller is idle.
ARBLST
RO
Arbitration Lost Value Description 0 1 The I2C controller won arbitration. The I2C controller lost arbitration.
DATACK
RO
Acknowledge Data Value Description 0 1 The transmitted data was acknowledged The transmitted data was not acknowledged.
ADRACK
RO
Acknowledge Address Value Description 0 1 The transmitted address was acknowledged The transmitted address was not acknowledged.
ERROR
RO
Error Value Description 0 1 No error was detected on the last operation. An error occurred on the last operation.
The error can be from the slave address not being acknowledged or the transmit data not being acknowledged. 0 BUSY RO 0 I2C Busy Value Description 0 1 The controller is idle. The controller is busy.
When the BUSY bit is set, the other status bits are not valid.
989
Write-Only Control Register

I2C Master Control/Status (I2CMCS)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x004 Type WO, reset 0x0000.0020
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 HS WO 0 RO 0 3 ACK WO 0 RO 0 2 STOP WO 0 RO 0 1 START WO 0 RO 0 0 RUN WO 0
Bit/Field 31:5
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. High-Speed Enable Value Description 0 The master operates in Standard, Fast mode, or Fast mode plus as selected by using a value in the I2CMTPR register that results in an SCL frequency of 100 kbps for Standard mode, 400 kbps for Fast mode, or 1 Mpbs for Fast mode plus. The master operates in High-Speed mode with transmission speeds up to 3.33 Mbps.
HS
WO
ACK
WO
Data Acknowledge Enable Value Description 0 1 The received data byte is not acknowledged automatically by the master. The received data byte is acknowledged automatically by the master. See field decoding in Table 16-5 on page 991.
STOP
WO
Generate STOP Value Description 0 1 The controller does not generate the STOP condition. The controller generates the STOP condition. See field decoding in Table 16-5 on page 991.
April 25, 2012
Bit/Field 1
Name START
Type WO
Reset 0
Description Generate START Value Description 0 1 The controller does not generate the START condition. The controller generates the START or repeated START condition. See field decoding in Table 16-5 on page 991.
RUN
WO
I2C Master Enable Value Description 0 1 The master is disabled. The master is enabled to transmit or receive data. See field decoding in Table 16-5 on page 991.
Table 16-5. Write Field Decoding for I2CMCS[3:0] Field

Current I2CMSA[0] State R/S 0 0 1 Idle 1 1 1 I2CMCS[3:0] ACK X
a
STOP 0 1 0 1 0 1
START 1 1 1 1 1 1
RUN 1 1 1 1 1 1
Description START condition followed by TRANSMIT (master goes to the Master Transmit state). START condition followed by a TRANSMIT and STOP condition (master remains in Idle state). START condition followed by RECEIVE operation with negative ACK (master goes to the Master Receive state). START condition followed by RECEIVE and STOP condition (master remains in Idle state). START condition followed by RECEIVE (master goes to the Master Receive state). Illegal NOP TRANSMIT operation (master remains in Master Transmit state). STOP condition (master goes to Idle state). TRANSMIT followed by STOP condition (master goes to Idle state). Repeated START condition followed by a TRANSMIT (master remains in Master Transmit state). Repeated START condition followed by TRANSMIT and STOP condition (master goes to Idle state). Repeated START condition followed by a RECEIVE operation with a negative ACK (master goes to Master Receive state). Repeated START condition followed by a TRANSMIT and STOP condition (master goes to Idle state). Repeated START condition followed by RECEIVE (master goes to Master Receive state). Illegal. NOP.
X 0 0 1 1
All other combinations not listed are non-operations. X X X 0 0 Master Transmit 1 X X X X X 0 0 1 1 0 1 0 0 0 0 1 1 1 1 0 1 1 1 1
1 1 1
0 1 1
1 0 1
1 1 1
1 1 1
All other combinations not listed are non-operations.
991
Table 16-5. Write Field Decoding for I2CMCS[3:0] Field (continued)

Current I2CMSA[0] State R/S X X X X X 1 Master Receive 1 1 0 0 0 1 X X 1 0 0 1 1 1 1 1 1 1 1 1 I2CMCS[3:0] ACK 0 X 0 1 1 0 STOP 0 1 1 0 1 0 START 0 0 0 0 0 1 RUN 1 0 1 1 1 1 Description RECEIVE operation with negative ACK (master remains in Master Receive state). STOP condition (master goes to Idle state).
b
RECEIVE followed by STOP condition (master goes to Idle state). RECEIVE operation (master remains in Master Receive state). Illegal. Repeated START condition followed by RECEIVE operation with a negative ACK (master remains in Master Receive state). Repeated START condition followed by RECEIVE and STOP condition (master goes to Idle state). Repeated START condition followed by RECEIVE (master remains in Master Receive state). Repeated START condition followed by TRANSMIT (master goes to Master Transmit state). Repeated START condition followed by TRANSMIT and STOP condition (master goes to Idle state). NOP.
All other combinations not listed are non-operations.
a. An X in a table cell indicates the bit can be 0 or 1. b. In Master Receive mode, a STOP condition should be generated only after a Data Negative Acknowledge executed by the master or an Address Negative Acknowledge executed by the slave.
April 25, 2012
Register 3: I2C Master Data (I2CMDR), offset 0x008

Important: This register is read-sensitive. See the register description for details. This register contains the data to be transmitted when in the Master Transmit state and the data received when in the Master Receive state.
I2C Master Data (I2CMDR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Data Transferred Data transferred during transaction.
7:0
DATA
R/W
0x00
993
Register 4: I2C Master Timer Period (I2CMTPR), offset 0x00C

This register is programmed to set the timer period for the SCL clock and assign the SCL clock to either standard or high-speed mode.
I2C Master Timer Period (I2CMTPR)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x00C Type R/W, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 HS RO 0 RO 0 RO 0 WO 0 R/W 0 R/W 0 R/W 0 RO 0 6 RO 0 5 RO 0 4 RO 0 3 TPR R/W 0 R/W 0 R/W 0 R/W 1 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. High-Speed Enable Value Description 1 0 The SCL Clock Period set by TPR applies to High-speed mode (3.33 Mbps). The SCL Clock Period set by TPR applies to Standard mode (100 Kbps), Fast-mode (400 Kbps), or Fast-mode plus (1 Mbps).
HS
WO
0x0
6:0
TPR
R/W
0x1
SCL Clock Period This field specifies the period of the SCL clock. SCL_PRD = 2(1 + TPR)(SCL_LP + SCL_HP)CLK_PRD where: SCL_PRD is the SCL line period (I2C clock). TPR is the Timer Period register value (range of 1 to 127). SCL_LP is the SCL Low period (fixed at 6). SCL_HP is the SCL High period (fixed at 4). CLK_PRD is the system clock period in ns.
April 25, 2012
Register 5: I2C Master Interrupt Mask (I2CMIMR), offset 0x010

This register controls whether a raw interrupt is promoted to a controller interrupt.
I2C Master Interrupt Mask (I2CMIMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 CLKIM R/W 0 RO 0 0 IM R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Timeout Interrupt Mask Value Description 1 0 The clock timeout interrupt is sent to the interrupt controller when the CLKRIS bit in the I2CMRIS register is set. The CLKRIS interrupt is suppressed and not sent to the interrupt controller.
CLKIM
R/W
IM
R/W
Master Interrupt Mask Value Description 1 0 The master interrupt is sent to the interrupt controller when the RIS bit in the I2CMRIS register is set. The RIS interrupt is suppressed and not sent to the interrupt controller.
995
Register 6: I2C Master Raw Interrupt Status (I2CMRIS), offset 0x014

This register specifies whether an interrupt is pending.
I2C Master Raw Interrupt Status (I2CMRIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 CLKRIS RO 0 RO 0 0 RIS RO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Timeout Raw Interrupt Status Value Description 1 0 The clock timeout interrupt is pending. No interrupt.
CLKRIS
RO
This bit is cleared by writing a 1 to the CLKIC bit in the I2CMICR register. 0 RIS RO 0 Master Raw Interrupt Status Value Description 1 0 A master interrupt is pending. No interrupt.
This bit is cleared by writing a 1 to the IC bit in the I2CMICR register.
April 25, 2012
Register 7: I2C Master Masked Interrupt Status (I2CMMIS), offset 0x018

This register specifies whether an interrupt was signaled.
I2C Master Masked Interrupt Status (I2CMMIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 CLKMIS RO 0 RO 0 0 MIS RO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Timeout Masked Interrupt Status Value Description 1 0 An unmasked clock timeout interrupt was signaled and is pending. No interrupt.
CLKMIS
RO
This bit is cleared by writing a 1 to the CLKIC bit in the I2CMICR register. 0 MIS RO 0 Masked Interrupt Status Value Description 1 0 An unmasked master interrupt was signaled and is pending. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the IC bit in the I2CMICR register.
997
Register 8: I2C Master Interrupt Clear (I2CMICR), offset 0x01C

This register clears the raw and masked interrupts.
I2C Master Interrupt Clear (I2CMICR)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x01C Type WO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 CLKIC WO 0 RO 0 0 IC WO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clock Timeout Interrupt Clear Writing a 1 to this bit clears the CLKRIS bit in the I2CMRIS register and the CLKMIS bit in the I2CMMIS register. A read of this register returns no meaningful data.
CLKIC
WO
IC
WO
Master Interrupt Clear Writing a 1 to this bit clears the RIS bit in the I2CMRIS register and the MIS bit in the I2CMMIS register. A read of this register returns no meaningful data.
April 25, 2012
Register 9: I2C Master Configuration (I2CMCR), offset 0x020

This register configures the mode (Master or Slave) and sets the interface for test mode loopback.
I2C Master Configuration (I2CMCR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 SFE RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 4 MFE R/W 0 RO 0 RO 0 3 RO 0 2 reserved RO 0 RO 0 RO 0 1 RO 0 0 LPBK R/W 0
Bit/Field 31:6
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Slave Function Enable Value Description 1 0 Slave mode is enabled. Slave mode is disabled.
SFE
R/W
MFE
R/W
I2C Master Function Enable Value Description 1 0 Master mode is enabled. Master mode is disabled.
3:1
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Loopback Value Description 1 0 The controller in a test mode loopback configuration. Normal operation.
LPBK
R/W
999
Register 10: I2C Master Clock Low Timeout Count (I2CMCLKOCNT), offset 0x024
This register contains the upper 8 bits of a 12-bit counter that can be used to keep the timeout limit for clock stretching by a remote slave. The lower four bits of the counter are not user visible.
I2C Master Clock Low Timeout Count (I2CMCLKOCNT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 CNTL RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Master Count This field contains the upper 8 bits of a 12-bit counter for the clock low timeout count.
7:0
CNTL
R/W
April 25, 2012
Register 11: I2C Master Bus Monitor (I2CMBMON), offset 0x02C

This register is used to determine the SCL and SDA signal status.
I2C Master Bus Monitor (I2CMBMON)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0x02C Type RO, reset 0x0000.0003
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 SDA RO 1 RO 0 0 SCL RO 1
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C SDA Status Value Description 1 0 The I2CSDA signal is high. The I2CSDA signal is low.
SDA
RO
SCL
RO
I2C SCL Status Value Description 1 0 The I2CSCL signal is high. The I2CSCL signal is low.
16.7
Register Descriptions (I2C Slave)

The remainder of this section lists and describes the I2C slave registers, in numerical order by address offset.
1001
Register 12: I2C Slave Own Address (I2CSOAR), offset 0x800

This register consists of seven address bits that identify the Stellaris I2C device on the I2C bus.
I2C Slave Own Address (I2CSOAR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 OAR R/W 0 R/W 0 R/W 0 R/W 0 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:7
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Slave Own Address This field specifies bits A6 through A0 of the slave address.
6:0
OAR
R/W
0x00
April 25, 2012
Register 13: I2C Slave Control/Status (I2CSCSR), offset 0x804

This register functions as a control register when written, and a status register when read. Read-Only Status Register
I2C Slave Control/Status (I2CSCSR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 OAR2SEL RO 0 RO 0 2 FBR RO 0 RO 0 1 TREQ RO 0 RO 0 0 RREQ RO 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. OAR2 Address Matched Value Description 1 0 OAR2 address matched and ACKed by the slave. Either the address is not matched or the match is in legacy mode.
OAR2SEL
RO
This bit gets reevaluated after every address comparison. 2 FBR RO 0 First Byte Received Value Description 1 0 The first byte following the slaves own address has been received. The first byte has not been received.
This bit is only valid when the RREQ bit is set and is automatically cleared when data has been read from the I2CSDR register. Note: 1 TREQ RO 0 This bit is not used for slave transmit operations.
Transmit Request Value Description 1 The I2C controller has been addressed as a slave transmitter and is using clock stretching to delay the master until data has been written to the I2CSDR register. No outstanding transmit request.
1003
Bit/Field 0
Name RREQ
Type RO
Reset 0
Description Receive Request Value Description 1 The I2C controller has outstanding receive data from the I2C master and is using clock stretching to delay the master until the data has been read from the I2CSDR register. No outstanding receive data.
Write-Only Control Register

I2C Slave Control/Status (I2CSCSR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 DA WO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Device Active Value Description 0 1 Disables the I2C slave operation. Enables the I2C slave operation.
DA
WO
Once this bit has been set, it should not be set again unless it has been cleared by writing a 0 or by a reset, otherwise transfer failures may occur.
April 25, 2012
Register 14: I2C Slave Data (I2CSDR), offset 0x808

Important: This register is read-sensitive. See the register description for details. This register contains the data to be transmitted when in the Slave Transmit state, and the data received when in the Slave Receive state.
I2C Slave Data (I2CSDR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Data for Transfer This field contains the data for transfer during a slave receive or transmit operation.
7:0
DATA
R/W
0x00
1005
Register 15: I2C Slave Interrupt Mask (I2CSIMR), offset 0x80C

This register controls whether a raw interrupt is promoted to a controller interrupt.
I2C Slave Interrupt Mask (I2CSIMR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
STOPIM STARTIM DATAIM R/W 0 R/W 0 R/W 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Stop Condition Interrupt Mask Value Description 1 0 The STOP condition interrupt is sent to the interrupt controller when the STOPRIS bit in the I2CSRIS register is set. The STOPRIS interrupt is suppressed and not sent to the interrupt controller.
STOPIM
R/W
STARTIM
R/W
Start Condition Interrupt Mask Value Description 1 0 The START condition interrupt is sent to the interrupt controller when the STARTRIS bit in the I2CSRIS register is set. The STARTRIS interrupt is suppressed and not sent to the interrupt controller.
DATAIM
R/W
Data Interrupt Mask Value Description 1 The data received or data requested interrupt is sent to the interrupt controller when the DATARIS bit in the I2CSRIS register is set. The DATARIS interrupt is suppressed and not sent to the interrupt controller.
April 25, 2012
Register 16: I2C Slave Raw Interrupt Status (I2CSRIS), offset 0x810
This register specifies whether an interrupt is pending.
I2C Slave Raw Interrupt Status (I2CSRIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
STOPRIS STARTRIS DATARIS RO 0 RO 0 RO 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Stop Condition Raw Interrupt Status Value Description 1 0 A STOP condition interrupt is pending. No interrupt.
STOPRIS
RO
This bit is cleared by writing a 1 to the STOPIC bit in the I2CSICR register. 1 STARTRIS RO 0 Start Condition Raw Interrupt Status Value Description 1 0 A START condition interrupt is pending. No interrupt.
This bit is cleared by writing a 1 to the STARTIC bit in the I2CSICR register. 0 DATARIS RO 0 Data Raw Interrupt Status Value Description 1 0 A data received or data requested interrupt is pending. No interrupt.
This bit is cleared by writing a 1 to the DATAIC bit in the I2CSICR register.
1007
Register 17: I2C Slave Masked Interrupt Status (I2CSMIS), offset 0x814
This register specifies whether an interrupt was signaled.
I2C Slave Masked Interrupt Status (I2CSMIS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
STOPMIS STARTMIS DATAMIS RO 0 RO 0 RO 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Stop Condition Masked Interrupt Status Value Description 1 0 An unmasked STOP condition interrupt was signaled is pending. An interrupt has not occurred or is masked.
STOPMIS
RO
This bit is cleared by writing a 1 to the STOPIC bit in the I2CSICR register. 1 STARTMIS RO 0 Start Condition Masked Interrupt Status Value Description 1 0 An unmasked START condition interrupt was signaled is pending. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the STARTIC bit in the I2CSICR register. 0 DATAMIS RO 0 Data Masked Interrupt Status Value Description 1 0 An unmasked data received or data requested interrupt was signaled is pending. An interrupt has not occurred or is masked.
This bit is cleared by writing a 1 to the DATAIC bit in the I2CSICR register.
April 25, 2012
Register 18: I2C Slave Interrupt Clear (I2CSICR), offset 0x818

This register clears the raw interrupt. A read of this register returns no meaningful data.
I2C Slave Interrupt Clear (I2CSICR)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 DATAIC WO 0
STOPIC STARTIC WO 0 WO 0
Bit/Field 31:3
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Stop Condition Interrupt Clear Writing a 1 to this bit clears the STOPRIS bit in the I2CSRIS register and the STOPMIS bit in the I2CSMIS register. A read of this register returns no meaningful data.
STOPIC
WO
STARTIC
WO
Start Condition Interrupt Clear Writing a 1 to this bit clears the STARTRIS bit in the I2CSRIS register and the STARTMIS bit in the I2CSMIS register. A read of this register returns no meaningful data.
DATAIC
WO
Data Interrupt Clear Writing a 1 to this bit clears the STOPRIS bit in the I2CSRIS register and the STOPMIS bit in the I2CSMIS register. A read of this register returns no meaningful data.
1009
Register 19: I2C Slave Own Address 2 (I2CSOAR2), offset 0x81C

This register consists of seven address bits that identify the alternate address for the I2C device on the I2C bus.
I2C Slave Own Address 2 (I2CSOAR2)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 OAR2EN RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 6 RO 0 5 RO 0 4 RO 0 3 OAR2 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Slave Own Address 2 Enable Value Description 1 0 Enables the use of the alternate address in the OAR2 field. The alternate address is disabled.
OAR2EN
R/W
6:0
OAR2
R/W
0x00
I2C Slave Own Address 2 This field specifies the alternate OAR2 address.
April 25, 2012
Register 20: I2C Slave ACK Control (I2CSACKCTL), offset 0x820

This register enables the I2C slave to NACK for invalid data or command or ACK for valid data or command. The I2C clock is pulled low after the last data bit until this register is written.
I2C Slave ACK Control (I2CSACKCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
ACKOVAL ACKOEN R/W 0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. I2C Slave ACK Override Value Value Description 1 0 A NACK is sent indicating invalid data or command. An ACK is sent indicating valid data or command.
ACKOVAL
R/W
ACKOEN
R/W
I2C Slave ACK Override Enable Value Description 1 0 An ACK or NACK is sent according to the value written to the ACKOVAL bit. A response in not provided.
16.8
Register Descriptions (I2C Status and Control)

The remainder of this section lists and describes the I2C status and control registers, in numerical order by address offset.
1011
Register 21: I2C Peripheral Properties (I2CPP), offset 0xFC0

The I2CPP register provides information regarding the properties of the I2C module.
I2C Peripheral Properties (I2CPP)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0xFC0 Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 HS RO 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. High-Speed Capable Value Description 1 0 The interface is capable of High-Speed operation. The interface is capable of Standard, Fast, or Fast mode plus operation.
HS
RO
0x1
April 25, 2012
Register 22: I2C Peripheral Configuration (I2CPC), offset 0xFC4

The I2CPC register provides information regarding the configuration of the I2C module.
I2C Peripheral Configuration (I2CPC)
I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000 Offset 0xFC4 Type RO, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 HS RO 1
Bit/Field 31:1
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. High-Speed Capable Value Description 1 The interface is set to High-Speed operation. Note that this encoding may only be used if the I2CPP HS bit is set. Otherwise, this encoding is not available. The interface is set to Standard, Fast or Fast mode plus operation.
HS
RO
1013
Controller Area Network (CAN) Module
17

Controller Area Network (CAN) is a multicast, shared serial bus standard for connecting electronic control units (ECUs). CAN was specifically designed to be robust in electromagnetically-noisy environments and can utilize a differential balanced line like RS-485 or a more robust twisted-pair wire. Originally created for automotive purposes, it is also used in many embedded control applications (such as industrial and medical). Bit rates up to 1 Mbps are possible at network lengths less than 40 meters. Decreased bit rates allow longer network distances (for example, 125 Kbps at 500 meters). The Stellaris LM4F120H5QR microcontroller includes one CAN unit with the following features: CAN protocol version 2.0 part A/B Bit rates up to 1 Mbps 32 message objects with individual identifier masks Maskable interrupt Disable Automatic Retransmission mode for Time-Triggered CAN (TTCAN) applications Programmable Loopback mode for self-test operation Programmable FIFO mode enables storage of multiple message objects Gluelessly attaches to an external CAN transceiver through the CANnTX and CANnRX signals
April 25, 2012
17.1
Block Diagram
Figure 17-1. CAN Controller Block Diagram
CAN Control
CANCTL CANSTS CANERR CANBIT CANINT CANTST CANBRPE
CAN Interface 1
CANIF1CRQ CANIF1CMSK CANIF1MSK1 CANIF1MSK2 CANIF1ARB1 CANIF1ARB2 CANIF1MCTL CANIF1DA1 CANIF1DA2 CANIF1DB1 CANIF1DB2 CAN Core
CAN Tx
APB Pins APB Interface
CAN Rx
CAN Interface 2
CANIF2CRQ CANIF2CMSK CANIF2MSK1 CANIF2MSK2 CANIF2ARB1 CANIF2ARB2 CANIF2MCTL CANIF2DA1 CANIF2DA2 CANIF2DB1 CANIF2DB2
Message Object Registers

CANTXRQ1 CANTXRQ2 CANNWDA1 CANNWDA2 CANMSG1INT CANMSG2INT CANMSG1VAL CANMSG2VAL
Message RAM 32 Message Objects
17.2
Signal Description
The following table lists the external signals of the CAN controller and describes the function of each. The CAN controller signals are alternate functions for some GPIO signals and default to be GPIO signals at reset. The column in the table below titled "Pin Mux/Pin Assignment" lists the possible GPIO pin placements for the CAN signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the CAN controller function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the CAN signal to the specified GPIO port pin. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
1015
Table 17-1. Controller Area Network Signals (64LQFP)

Pin Name CAN0Rx Pin Number Pin Mux / Pin Assignment 28 58 59 31 57 60 PF0 (3) PB4 (8) PE4 (8) PF3 (3) PB5 (8) PE5 (8) Pin Type I Buffer Type TTL
a
Description CAN module 0 receive.
CAN0Tx
TTL
CAN module 0 transmit.
17.3
The Stellaris CAN controller conforms to the CAN protocol version 2.0 (parts A and B). Message transfers that include data, remote, error, and overload frames with an 11-bit identifier (standard) or a 29-bit identifier (extended) are supported. Transfer rates can be programmed up to 1 Mbps. The CAN module consists of three major parts: CAN protocol controller and message handler Message memory CAN register interface A data frame contains data for transmission, whereas a remote frame contains no data and is used to request the transmission of a specific message object. The CAN data/remote frame is constructed as shown in Figure 17-2.
Figure 17-2. CAN Data/Remote Frame

Start Of Frame Bus Idle Remote Transmission Request CRC Sequence A C K 1 1 1 Delimiter Bits
R S Control O Message Delimiter T Field R F 11 or 29 1 6
Data Field
EOP
IFS
Bus Idle
Number 1 Of Bits
0 . . . 64
15
CRC Sequence Arbitration Field CRC Field
End of Frame Field
Interframe Field
Bit Stuffing CAN Data Frame
Acknowledgement Field
The protocol controller transfers and receives the serial data from the CAN bus and passes the data on to the message handler. The message handler then loads this information into the appropriate
April 25, 2012
message object based on the current filtering and identifiers in the message object memory. The message handler is also responsible for generating interrupts based on events on the CAN bus. The message object memory is a set of 32 identical memory blocks that hold the current configuration, status, and actual data for each message object. These memory blocks are accessed via either of the CAN message object register interfaces. The message memory is not directly accessible in the Stellaris memory map, so the Stellaris CAN controller provides an interface to communicate with the message memory via two CAN interface register sets for communicating with the message objects. The message object memory cannot be directly accessed, so these two interfaces must be used to read or write to each message object. The two message object interfaces allow parallel access to the CAN controller message objects when multiple objects may have new information that must be processed. In general, one interface is used for transmit data and one for receive data.
17.3.1
Initialization
To use the CAN controller, the peripheral clock must be enabled using the RCGC0 register (see page 447). In addition, the clock to the appropriate GPIO module must be enabled via the RCGC2 register (see page 453). To find out which GPIO port to enable, refer to Table 21-4 on page 1148. Set the GPIO AFSEL bits for the appropriate pins (see page 653). Configure the PMCn fields in the GPIOPCTL register to assign the CAN signals to the appropriate pins. See page 670 and Table 21-5 on page 1152. Software initialization is started by setting the INIT bit in the CAN Control (CANCTL) register (with software or by a hardware reset) or by going bus-off, which occurs when the transmitter's error counter exceeds a count of 255. While INIT is set, all message transfers to and from the CAN bus are stopped and the CANnTX signal is held High. Entering the initialization state does not change the configuration of the CAN controller, the message objects, or the error counters. However, some configuration registers are only accessible while in the initialization state. To initialize the CAN controller, set the CAN Bit Timing (CANBIT) register and configure each message object. If a message object is not needed, label it as not valid by clearing the MSGVAL bit in the CAN IFn Arbitration 2 (CANIFnARB2) register. Otherwise, the whole message object must be initialized, as the fields of the message object may not have valid information, causing unexpected results. Both the INIT and CCE bits in the CANCTL register must be set in order to access the CANBIT register and the CAN Baud Rate Prescaler Extension (CANBRPE) register to configure the bit timing. To leave the initialization state, the INIT bit must be cleared. Afterwards, the internal Bit Stream Processor (BSP) synchronizes itself to the data transfer on the CAN bus by waiting for the occurrence of a sequence of 11 consecutive recessive bits (indicating a bus idle condition) before it takes part in bus activities and starts message transfers. Message object initialization does not require the CAN to be in the initialization state and can be done on the fly. However, message objects should all be configured to particular identifiers or set to not valid before message transfer starts. To change the configuration of a message object during normal operation, clear the MSGVAL bit in the CANIFnARB2 register to indicate that the message object is not valid during the change. When the configuration is completed, set the MSGVAL bit again to indicate that the message object is once again valid.
17.3.2
Operation
Two sets of CAN Interface Registers (CANIF1x and CANIF2x) are used to access the message objects in the Message RAM. The CAN controller coordinates transfers to and from the Message RAM to and from the registers. The two sets are independent and identical and can be used to queue transactions. Generally, one interface is used to transmit data and one is used to receive data.
1017
Once the CAN module is initialized and the INIT bit in the CANCTL register is cleared, the CAN module synchronizes itself to the CAN bus and starts the message transfer. As each message is received, it goes through the message handler's filtering process, and if it passes through the filter, is stored in the message object specified by the MNUM bit in the CAN IFn Command Request (CANIFnCRQ) register. The whole message (including all arbitration bits, data-length code, and eight data bytes) is stored in the message object. If the Identifier Mask (the MSK bits in the CAN IFn Mask 1 and CAN IFn Mask 2 (CANIFnMSKn) registers) is used, the arbitration bits that are masked to "don't care" may be overwritten in the message object. The CPU may read or write each message at any time via the CAN Interface Registers. The message handler guarantees data consistency in case of concurrent accesses. The transmission of message objects is under the control of the software that is managing the CAN hardware. Message objects can be used for one-time data transfers or can be permanent message objects used to respond in a more periodic manner. Permanent message objects have all arbitration and control set up, and only the data bytes are updated. At the start of transmission, the appropriate TXRQST bit in the CAN Transmission Request n (CANTXRQn) register and the NEWDAT bit in the CAN New Data n (CANNWDAn) register are set. If several transmit messages are assigned to the same message object (when the number of message objects is not sufficient), the whole message object has to be configured before the transmission of this message is requested. The transmission of any number of message objects may be requested at the same time; they are transmitted according to their internal priority, which is based on the message identifier (MNUM) for the message object, with 1 being the highest priority and 32 being the lowest priority. Messages may be updated or set to not valid any time, even when their requested transmission is still pending. The old data is discarded when a message is updated before its pending transmission has started. Depending on the configuration of the message object, the transmission of a message may be requested autonomously by the reception of a remote frame with a matching identifier. Transmission can be automatically started by the reception of a matching remote frame. To enable this mode, set the RMTEN bit in the CAN IFn Message Control (CANIFnMCTL) register. A matching received remote frame causes the TXRQST bit to be set, and the message object automatically transfers its data or generates an interrupt indicating a remote frame was requested. A remote frame can be strictly a single message identifier, or it can be a range of values specified in the message object. The CAN mask registers, CANIFnMSKn, configure which groups of frames are identified as remote frame requests. The UMASK bit in the CANIFnMCTL register enables the MSK bits in the CANIFnMSKn register to filter which frames are identified as a remote frame request. The MXTD bit in the CANIFnMSK2 register should be set if a remote frame request is expected to be triggered by 29-bit extended identifiers.
17.3.3
Transmitting Message Objects

If the internal transmit shift register of the CAN module is ready for loading, and if a data transfer is not occurring between the CAN Interface Registers and message RAM, the valid message object with the highest priority that has a pending transmission request is loaded into the transmit shift register by the message handler and the transmission is started. The message object's NEWDAT bit in the CANNWDAn register is cleared. After a successful transmission, and if no new data was written to the message object since the start of the transmission, the TXRQST bit in the CANTXRQn register is cleared. If the CAN controller is configured to interrupt on a successful transmission of a message object, (the TXIE bit in the CAN IFn Message Control (CANIFnMCTL) register is set), the INTPND bit in the CANIFnMCTL register is set after a successful transmission. If the CAN module has lost the arbitration or if an error occurred during the transmission, the message is re-transmitted as soon as the CAN bus is free again. If, meanwhile, the transmission of a message with higher priority has been requested, the messages are transmitted in the order of their priority.
April 25, 2012
17.3.4
Configuring a Transmit Message Object

The following steps illustrate how to configure a transmit message object. 1. In the CAN IFn Command Mask (CANIFnCMASK) register: Set the WRNRD bit to specify a write to the CANIFnCMASK register; specify whether to transfer the IDMASK, DIR, and MXTD of the message object into the CAN IFn registers using the MASK bit Specify whether to transfer the ID, DIR, XTD, and MSGVAL of the message object into the interface registers using the ARB bit Specify whether to transfer the control bits into the interface registers using the CONTROL bit Specify whether to clear the INTPND bit in the CANIFnMCTL register using the CLRINTPND bit Specify whether to clear the NEWDAT bit in the CANNWDAn register using the NEWDAT bit Specify which bits to transfer using the DATAA and DATAB bits 2. In the CANIFnMSK1 register, use the MSK[15:0] bits to specify which of the bits in the 29-bit or 11-bit message identifier are used for acceptance filtering. Note that MSK[15:0] in this register are used for bits [15:0] of the 29-bit message identifier and are not used for an 11-bit identifier. A value of 0x00 enables all messages to pass through the acceptance filtering. Also note that in order for these bits to be used for acceptance filtering, they must be enabled by setting the UMASK bit in the CANIFnMCTL register. 3. In the CANIFnMSK2 register, use the MSK[12:0] bits to specify which of the bits in the 29-bit or 11-bit message identifier are used for acceptance filtering. Note that MSK[12:0] are used for bits [28:16] of the 29-bit message identifier; whereas MSK[12:2] are used for bits [10:0] of the 11-bit message identifier. Use the MXTD and MDIR bits to specify whether to use XTD and DIR for acceptance filtering. A value of 0x00 enables all messages to pass through the acceptance filtering. Also note that in order for these bits to be used for acceptance filtering, they must be enabled by setting the UMASK bit in the CANIFnMCTL register. 4. For a 29-bit identifier, configure ID[15:0] in the CANIFnARB1 register for bits [15:0] of the message identifier and ID[12:0] in the CANIFnARB2 register for bits [28:16] of the message identifier. Set the XTD bit to indicate an extended identifier; set the DIR bit to indicate transmit; and set the MSGVAL bit to indicate that the message object is valid. 5. For an 11-bit identifier, disregard the CANIFnARB1 register and configure ID[12:2] in the CANIFnARB2 register for bits [10:0] of the message identifier. Clear the XTD bit to indicate a standard identifier; set the DIR bit to indicate transmit; and set the MSGVAL bit to indicate that the message object is valid. 6. In the CANIFnMCTL register: Optionally set the UMASK bit to enable the mask (MSK, MXTD, and MDIR specified in the CANIFnMSK1 and CANIFnMSK2 registers) for acceptance filtering Optionally set the TXIE bit to enable the INTPND bit to be set after a successful transmission
1019
Optionally set the RMTEN bit to enable the TXRQST bit to be set on the reception of a matching remote frame allowing automatic transmission Set the EOB bit for a single message object Configure the DLC[3:0] field to specify the size of the data frame. Take care during this configuration not to set the NEWDAT, MSGLST, INTPND or TXRQST bits. 7. Load the data to be transmitted into the CAN IFn Data (CANIFnDA1, CANIFnDA2, CANIFnDB1, CANIFnDB2) registers. Byte 0 of the CAN data frame is stored in DATA[7:0] in the CANIFnDA1 register. 8. Program the number of the message object to be transmitted in the MNUM field in the CAN IFn Command Request (CANIFnCRQ) register. 9. When everything is properly configured, set the TXRQST bit in the CANIFnMCTL register. Once this bit is set, the message object is available to be transmitted, depending on priority and bus availability. Note that setting the RMTEN bit in the CANIFnMCTL register can also start message transmission if a matching remote frame has been received.
17.3.5
Updating a Transmit Message Object

The CPU may update the data bytes of a Transmit Message Object any time via the CAN Interface Registers and neither the MSGVAL bit in the CANIFnARB2 register nor the TXRQST bits in the CANIFnMCTL register have to be cleared before the update. Even if only some of the data bytes are to be updated, all four bytes of the corresponding CANIFnDAn/CANIFnDBn register have to be valid before the content of that register is transferred to the message object. Either the CPU must write all four bytes into the CANIFnDAn/CANIFnDBn register or the message object is transferred to the CANIFnDAn/CANIFnDBn register before the CPU writes the new data bytes. In order to only update the data in a message object, the WRNRD, DATAA and DATAB bits in the CANIFnMSKn register are set, followed by writing the updated data into CANIFnDA1, CANIFnDA2, CANIFnDB1, and CANIFnDB2 registers, and then the number of the message object is written to the MNUM field in the CAN IFn Command Request (CANIFnCRQ) register. To begin transmission of the new data as soon as possible, set the TXRQST bit in the CANIFnMSKn register. To prevent the clearing of the TXRQST bit in the CANIFnMCTL register at the end of a transmission that may already be in progress while the data is updated, the NEWDAT and TXRQST bits have to be set at the same time in the CANIFnMCTL register. When these bits are set at the same time, NEWDAT is cleared as soon as the new transmission has started.
17.3.6
Accepting Received Message Objects

When the arbitration and control field (the ID and XTD bits in the CANIFnARB2 and the RMTEN and DLC[3:0] bits of the CANIFnMCTL register) of an incoming message is completely shifted into the CAN controller, the message handling capability of the controller starts scanning the message RAM for a matching valid message object. To scan the message RAM for a matching message object, the controller uses the acceptance filtering programmed through the mask bits in the CANIFnMSKn register and enabled using the UMASK bit in the CANIFnMCTL register. Each valid message object, starting with object 1, is compared with the incoming message to locate a matching message object in the message RAM. If a match occurs, the scanning is stopped and the message handler proceeds depending on whether it is a data frame or remote frame that was received.
April 25, 2012
17.3.7
Receiving a Data Frame

The message handler stores the message from the CAN controller receive shift register into the matching message object in the message RAM. The data bytes, all arbitration bits, and the DLC bits are all stored into the corresponding message object. In this manner, the data bytes are connected with the identifier even if arbitration masks are used. The NEWDAT bit of the CANIFnMCTL register is set to indicate that new data has been received. The CPU should clear this bit when it reads the message object to indicate to the controller that the message has been received, and the buffer is free to receive more messages. If the CAN controller receives a message and the NEWDAT bit is already set, the MSGLST bit in the CANIFnMCTL register is set to indicate that the previous data was lost. If the system requires an interrupt on successful reception of a frame, the RXIE bit of the CANIFnMCTL register should be set. In this case, the INTPND bit of the same register is set, causing the CANINT register to point to the message object that just received a message. The TXRQST bit of this message object should be cleared to prevent the transmission of a remote frame.
17.3.8
Receiving a Remote Frame

A remote frame contains no data, but instead specifies which object should be transmitted. When a remote frame is received, three different configurations of the matching message object have to be considered: Table 17-2. Message Object Configurations
Configuration in CANIFnMCTL Description DIR = 1 (direction = transmit); programmed in the At the reception of a matching remote frame, the TXRQST bit of this CANIFnARB2 register message object is set. The rest of the message object remains unchanged, and the controller automatically transfers the data in RMTEN = 1 (set the TXRQST bit of the the message object as soon as possible. CANIFnMCTL register at reception of the frame to enable transmission) UMASK = 1 or 0 DIR = 1 (direction = transmit); programmed in the At the reception of a matching remote frame, the TXRQST bit of this CANIFnARB2 register message object remains unchanged, and the remote frame is ignored. This remote frame is disabled, the data is not transferred RMTEN = 0 (do not change the TXRQST bit of the and nothing indicates that the remote frame ever happened. CANIFnMCTL register at reception of the frame) UMASK = 0 (ignore mask in the CANIFnMSKn register) DIR = 1 (direction = transmit); programmed in the At the reception of a matching remote frame, the TXRQST bit of this CANIFnARB2 register message object is cleared. The arbitration and control field (ID + XTD + RMTEN + DLC) from the shift register is stored into the message RMTEN = 0 (do not change the TXRQST bit of the object in the message RAM, and the NEWDAT bit of this message CANIFnMCTL register at reception of the frame) object is set. The data field of the message object remains unchanged; the remote frame is treated similar to a received data UMASK = 1 (use mask (MSK, MXTD, and MDIR in frame. This mode is useful for a remote data request from another the CANIFnMSKn register) for acceptance filtering) CAN device for which the Stellaris controller does not have readily available data. The software must fill the data and answer the frame manually.
17.3.9
Receive/Transmit Priority
The receive/transmit priority for the message objects is controlled by the message number. Message object 1 has the highest priority, while message object 32 has the lowest priority. If more than one transmission request is pending, the message objects are transmitted in order based on the message
1021
object with the lowest message number. This prioritization is separate from that of the message identifier which is enforced by the CAN bus. As a result, if message object 1 and message object 2 both have valid messages to be transmitted, message object 1 is always transmitted first regardless of the message identifier in the message object itself.
17.3.10
Configuring a Receive Message Object

The following steps illustrate how to configure a receive message object. 1. Program the CAN IFn Command Mask (CANIFnCMASK) register as described in the Configuring a Transmit Message Object on page 1019 section, except that the WRNRD bit is set to specify a write to the message RAM. 2. Program the CANIFnMSK1and CANIFnMSK2 registers as described in the Configuring a Transmit Message Object on page 1019 section to configure which bits are used for acceptance filtering. Note that in order for these bits to be used for acceptance filtering, they must be enabled by setting the UMASK bit in the CANIFnMCTL register. 3. In the CANIFnMSK2 register, use the MSK[12:0] bits to specify which of the bits in the 29-bit or 11-bit message identifier are used for acceptance filtering. Note that MSK[12:0] are used for bits [28:16] of the 29-bit message identifier; whereas MSK[12:2] are used for bits [10:0] of the 11-bit message identifier. Use the MXTD and MDIR bits to specify whether to use XTD and DIR for acceptance filtering. A value of 0x00 enables all messages to pass through the acceptance filtering. Also note that in order for these bits to be used for acceptance filtering, they must be enabled by setting the UMASK bit in the CANIFnMCTL register. 4. Program the CANIFnARB1 and CANIFnARB2 registers as described in the Configuring a Transmit Message Object on page 1019 section to program XTD and ID bits for the message identifier to be received; set the MSGVAL bit to indicate a valid message; and clear the DIR bit to specify receive. 5. In the CANIFnMCTL register: Optionally set the UMASK bit to enable the mask (MSK, MXTD, and MDIR specified in the CANIFnMSK1 and CANIFnMSK2 registers) for acceptance filtering Optionally set the RXIE bit to enable the INTPND bit to be set after a successful reception Clear the RMTEN bit to leave the TXRQST bit unchanged Set the EOB bit for a single message object Configure the DLC[3:0] field to specify the size of the data frame Take care during this configuration not to set the NEWDAT, MSGLST, INTPND or TXRQST bits. 6. Program the number of the message object to be received in the MNUM field in the CAN IFn Command Request (CANIFnCRQ) register. Reception of the message object begins as soon as a matching frame is available on the CAN bus. When the message handler stores a data frame in the message object, it stores the received Data Length Code and eight data bytes in the CANIFnDA1, CANIFnDA2, CANIFnDB1, and CANIFnDB2 register. Byte 0 of the CAN data frame is stored in DATA[7:0] in the CANIFnDA1 register. If the Data Length Code is less than 8, the remaining bytes of the message object are overwritten by unspecified values.
April 25, 2012
The CAN mask registers can be used to allow groups of data frames to be received by a message object. The CAN mask registers, CANIFnMSKn, configure which groups of frames are received by a message object. The UMASK bit in the CANIFnMCTL register enables the MSK bits in the CANIFnMSKn register to filter which frames are received. The MXTD bit in the CANIFnMSK2 register should be set if only 29-bit extended identifiers are expected by this message object.
17.3.11
Handling of Received Message Objects

The CPU may read a received message any time via the CAN Interface registers because the data consistency is guaranteed by the message handler state machine. Typically, the CPU first writes 0x007F to the CANIFnCMSK register and then writes the number of the message object to the CANIFnCRQ register. That combination transfers the whole received message from the message RAM into the Message Buffer registers (CANIFnMSKn, CANIFnARBn, and CANIFnMCTL). Additionally, the NEWDAT and INTPND bits are cleared in the message RAM, acknowledging that the message has been read and clearing the pending interrupt generated by this message object. If the message object uses masks for acceptance filtering, the CANIFnARBn registers show the full, unmasked ID for the received message. The NEWDAT bit in the CANIFnMCTL register shows whether a new message has been received since the last time this message object was read. The MSGLST bit in the CANIFnMCTL register shows whether more than one message has been received since the last time this message object was read. MSGLST is not automatically cleared, and should be cleared by software after reading its status. Using a remote frame, the CPU may request new data from another CAN node on the CAN bus. Setting the TXRQST bit of a receive object causes the transmission of a remote frame with the receive object's identifier. This remote frame triggers the other CAN node to start the transmission of the matching data frame. If the matching data frame is received before the remote frame could be transmitted, the TXRQST bit is automatically reset. This prevents the possible loss of data when the other device on the CAN bus has already transmitted the data slightly earlier than expected.
17.3.11.1 Configuration of a FIFO Buffer

With the exception of the EOB bit in the CANIFnMCTL register, the configuration of receive message objects belonging to a FIFO buffer is the same as the configuration of a single receive message object (see Configuring a Receive Message Object on page 1022). To concatenate two or more message objects into a FIFO buffer, the identifiers and masks (if used) of these message objects have to be programmed to matching values. Due to the implicit priority of the message objects, the message object with the lowest message object number is the first message object in a FIFO buffer. The EOB bit of all message objects of a FIFO buffer except the last one must be cleared. The EOB bit of the last message object of a FIFO buffer is set, indicating it is the last entry in the buffer.
17.3.11.2 Reception of Messages with FIFO Buffers

Received messages with identifiers matching to a FIFO buffer are stored starting with the message object with the lowest message number. When a message is stored into a message object of a FIFO buffer, the NEWDAT of the CANIFnMCTL register bit of this message object is set. By setting NEWDAT while EOB is clear, the message object is locked and cannot be written to by the message handler until the CPU has cleared the NEWDAT bit. Messages are stored into a FIFO buffer until the last message object of this FIFO buffer is reached. Until all of the preceding message objects have been released by clearing the NEWDAT bit, all further messages for this FIFO buffer are written into the last message object of the FIFO buffer and therefore overwrite previous messages.
1023
17.3.11.3 Reading from a FIFO Buffer

When the CPU transfers the contents of a message object from a FIFO buffer by writing its number to the CANIFnCRQ register, the TXRQST and CLRINTPND bits in the CANIFnCMSK register should be set such that the NEWDAT and INTPEND bits in the CANIFnMCTL register are cleared after the read. The values of these bits in the CANIFnMCTL register always reflect the status of the message object before the bits are cleared. To assure the correct function of a FIFO buffer, the CPU should read out the message objects starting with the message object with the lowest message number. When reading from the FIFO buffer, the user should be aware that a new received message is placed in the message object with the lowest message number for which the NEWDAT bit of the CANIFnMCTL register is clear. As a result, the order of the received messages in the FIFO is not guaranteed. Figure 17-3 on page 1025 shows how a set of message objects which are concatenated to a FIFO Buffer can be handled by the CPU.
April 25, 2012
Figure 17-3. Message Objects in a FIFO Buffer

START
Message Interrupt
Read Interrupt Pointer
0x0000
Case Interrupt Pointer
else
0x8000
Status Change Interrupt Handling MNUM = Interrupt Pointer
END
Write MNUM to IFn Command Request (Read Message to IFn Registers, Reset NEWDAT = 0, Reset INTPND = 0
Read IFn Message Control Yes No NEWDAT = 1
Read Data from IFn Data A,B
EOB = 1 No MNUM = MNUM + 1
Yes
17.3.12
Handling of Interrupts
If several interrupts are pending, the CAN Interrupt (CANINT) register points to the pending interrupt with the highest priority, disregarding their chronological order. The status interrupt has the highest
1025
priority. Among the message interrupts, the message object's interrupt with the lowest message number has the highest priority. A message interrupt is cleared by clearing the message object's INTPND bit in the CANIFnMCTL register or by reading the CAN Status (CANSTS) register. The status Interrupt is cleared by reading the CANSTS register. The interrupt identifier INTID in the CANINT register indicates the cause of the interrupt. When no interrupt is pending, the register reads as 0x0000. If the value of the INTID field is different from 0, then an interrupt is pending. If the IE bit is set in the CANCTL register, the interrupt line to the interrupt controller is active. The interrupt line remains active until the INTID field is 0, meaning that all interrupt sources have been cleared (the cause of the interrupt is reset), or until IE is cleared, which disables interrupts from the CAN controller. The INTID field of the CANINT register points to the pending message interrupt with the highest interrupt priority. The SIE bit in the CANCTL register controls whether a change of the RXOK, TXOK, and LEC bits in the CANSTS register can cause an interrupt. The EIE bit in the CANCTLregister controls whether a change of the BOFF and EWARN bits in the CANSTS register can cause an interrupt. The IE bit in the CANCTL register controls whether any interrupt from the CAN controller actually generates an interrupt to the interrupt controller. The CANINT register is updated even when the IE bit in the CANCTL register is clear, but the interrupt is not indicated to the CPU. A value of 0x8000 in the CANINT register indicates that an interrupt is pending because the CAN module has updated, but not necessarily changed, the CANSTS register, indicating that either an error or status interrupt has been generated. A write access to the CANSTS register can clear the RXOK, TXOK, and LEC bits in that same register; however, the only way to clear the source of a status interrupt is to read the CANSTS register. The source of an interrupt can be determined in two ways during interrupt handling. The first is to read the INTID bit in the CANINT register to determine the highest priority interrupt that is pending, and the second is to read the CAN Message Interrupt Pending (CANMSGnINT) register to see all of the message objects that have pending interrupts. An interrupt service routine reading the message that is the source of the interrupt may read the message and clear the message object's INTPND bit at the same time by setting the CLRINTPND bit in the CANIFnCMSK register. Once the INTPND bit has been cleared, the CANINT register contains the message number for the next message object with a pending interrupt.
17.3.13
Test Mode
A Test Mode is provided which allows various diagnostics to be performed. Test Mode is entered by setting the TEST bit in the CANCTL register. Once in Test Mode, the TX[1:0], LBACK, SILENT and BASIC bits in the CAN Test (CANTST) register can be used to put the CAN controller into the various diagnostic modes. The RX bit in the CANTST register allows monitoring of the CANnRX signal. All CANTST register functions are disabled when the TEST bit is cleared.
17.3.13.1 Silent Mode

Silent Mode can be used to analyze the traffic on a CAN bus without affecting it by the transmission of dominant bits (Acknowledge Bits, Error Frames). The CAN Controller is put in Silent Mode setting the SILENT bit in the CANTST register. In Silent Mode, the CAN controller is able to receive valid data frames and valid remote frames, but it sends only recessive bits on the CAN bus and cannot start a transmission. If the CAN Controller is required to send a dominant bit (ACK bit, overload flag, or active error flag), the bit is rerouted internally so that the CAN Controller monitors this dominant bit, although the CAN bus remains in recessive state.
April 25, 2012
17.3.13.2 Loopback Mode

Loopback mode is useful for self-test functions. In Loopback Mode, the CAN Controller internally routes the CANnTX signal on to the CANnRX signal and treats its own transmitted messages as received messages and stores them (if they pass acceptance filtering) into the message buffer. The CAN Controller is put in Loopback Mode by setting the LBACK bit in the CANTST register. To be independent from external stimulation, the CAN Controller ignores acknowledge errors (a recessive bit sampled in the acknowledge slot of a data/remote frame) in Loopback Mode. The actual value of the CANnRX signal is disregarded by the CAN Controller. The transmitted messages can be monitored on the CANnTX signal.
17.3.13.3 Loopback Combined with Silent Mode

Loopback Mode and Silent Mode can be combined to allow the CAN Controller to be tested without affecting a running CAN system connected to the CANnTX and CANnRX signals. In this mode, the CANnRX signal is disconnected from the CAN Controller and the CANnTX signal is held recessive. This mode is enabled by setting both the LBACK and SILENT bits in the CANTST register.
17.3.13.4 Basic Mode

Basic Mode allows the CAN Controller to be operated without the Message RAM. In Basic Mode, The CANIF1 registers are used as the transmit buffer. The transmission of the contents of the IF1 registers is requested by setting the BUSY bit of the CANIF1CRQ register. The CANIF1 registers are locked while the BUSY bit is set. The BUSY bit indicates that a transmission is pending. As soon the CAN bus is idle, the CANIF1 registers are loaded into the shift register of the CAN Controller and transmission is started. When the transmission has completed, the BUSY bit is cleared and the locked CANIF1 registers are released. A pending transmission can be aborted at any time by clearing the BUSY bit in the CANIF1CRQ register while the CANIF1 registers are locked. If the CPU has cleared the BUSY bit, a possible retransmission in case of lost arbitration or an error is disabled. The CANIF2 Registers are used as a receive buffer. After the reception of a message, the contents of the shift register are stored in the CANIF2 registers, without any acceptance filtering. Additionally, the actual contents of the shift register can be monitored during the message transfer. Each time a read message object is initiated by setting the BUSY bit of the CANIF2CRQ register, the contents of the shift register are stored into the CANIF2 registers. In Basic Mode, all message-object-related control and status bits and of the control bits of the CANIFnCMSK registers are not evaluated. The message number of the CANIFnCRQ registers is also not evaluated. In the CANIF2MCTL register, the NEWDAT and MSGLST bits retain their function, the DLC[3:0] field shows the received DLC, the other control bits are cleared. Basic Mode is enabled by setting the BASIC bit in the CANTST register.
17.3.13.5 Transmit Control

Software can directly override control of the CANnTX signal in four different ways. CANnTX is controlled by the CAN Controller The sample point is driven on the CANnTX signal to monitor the bit timing CANnTX drives a low value CANnTX drives a high value
1027
The last two functions, combined with the readable CAN receive pin CANnRX, can be used to check the physical layer of the CAN bus. The Transmit Control function is enabled by programming the TX[1:0] field in the CANTST register. The three test functions for the CANnTX signal interfere with all CAN protocol functions. TX[1:0] must be cleared when CAN message transfer or Loopback Mode, Silent Mode, or Basic Mode are selected.
17.3.14
Bit Timing Configuration Error Considerations

Even if minor errors in the configuration of the CAN bit timing do not result in immediate failure, the performance of a CAN network can be reduced significantly. In many cases, the CAN bit synchronization amends a faulty configuration of the CAN bit timing to such a degree that only occasionally an error frame is generated. In the case of arbitration, however, when two or more CAN nodes simultaneously try to transmit a frame, a misplaced sample point may cause one of the transmitters to become error passive. The analysis of such sporadic errors requires a detailed knowledge of the CAN bit synchronization inside a CAN node and of the CAN nodes' interaction on the CAN bus.
17.3.15
Bit Time and Bit Rate

The CAN system supports bit rates in the range of lower than 1 Kbps up to 1000 Kbps. Each member of the CAN network has its own clock generator. The timing parameter of the bit time can be configured individually for each CAN node, creating a common bit rate even though the CAN nodes' oscillator periods may be different. Because of small variations in frequency caused by changes in temperature or voltage and by deteriorating components, these oscillators are not absolutely stable. As long as the variations remain inside a specific oscillator's tolerance range, the CAN nodes are able to compensate for the different bit rates by periodically resynchronizing to the bit stream. According to the CAN specification, the bit time is divided into four segments (see Figure 17-4 on page 1029): the Synchronization Segment, the Propagation Time Segment, the Phase Buffer Segment 1, and the Phase Buffer Segment 2. Each segment consists of a specific, programmable number of time quanta (see Table 17-3 on page 1029). The length of the time quantum (tq), which is the basic time unit of the bit time, is defined by the CAN controller's input clock (fsys) and the Baud Rate Prescaler (BRP): tq = BRP / fsys The fsys input clock is the system clock frequency as configured by the RCC or RCC2 registers (see page 245 or page 251). The Synchronization Segment Sync is that part of the bit time where edges of the CAN bus level are expected to occur; the distance between an edge that occurs outside of Sync and the Sync is called the phase error of that edge. The Propagation Time Segment Prop is intended to compensate for the physical delay times within the CAN network. The Phase Buffer Segments Phase1 and Phase2 surround the Sample Point. The (Re-)Synchronization Jump Width (SJW) defines how far a resynchronization may move the Sample Point inside the limits defined by the Phase Buffer Segments to compensate for edge phase errors. A given bit rate may be met by different bit-time configurations, but for the proper function of the CAN network, the physical delay times and the oscillator's tolerance range have to be considered.
April 25, 2012
Figure 17-4. CAN Bit Time

Nominal CAN Bit Time TSEG1
a
TSEG2
c
Sync
Prop
Phase1
Phase2
1 Time Quantum q (tq)

a. TSEG1 = Prop + Phase1 b. TSEG2 = Phase2 c. Phase1 = Phase2 or Phase1 + 1 = Phase2
Sample Point
Table 17-3. CAN Protocol Ranges

Parameter BRP Sync Prop Phase1 Phase2 SJW Range [1 .. 64] 1 tq [1 .. 8] tq [1 .. 8] tq [1 .. 8] tq [1 .. 4] tq
Remark Defines the length of the time quantum tq. The CANBRPE register can be used to extend the range to 1024. Fixed length, synchronization of bus input to system clock Compensates for the physical delay times May be lengthened temporarily by synchronization May be shortened temporarily by synchronization May not be longer than either Phase Buffer Segment
a. This table describes the minimum programmable ranges required by the CAN protocol.
The bit timing configuration is programmed in two register bytes in the CANBIT register. In the CANBIT register, the four components TSEG2, TSEG1, SJW, and BRP have to be programmed to a numerical value that is one less than its functional value; so instead of values in the range of [1..n], values in the range of [0..n-1] are programmed. That way, for example, SJW (functional range of [1..4]) is represented by only two bits in the SJW bit field. Table 17-4 shows the relationship between the CANBIT register values and the parameters. Table 17-4. CANBIT Register Values
CANBIT Register Field TSEG2 TSEG1 SJW BRP Setting Phase2 - 1 Prop + Phase1 - 1 SJW - 1 BRP
Therefore, the length of the bit time is (programmed values): [TSEG1 + TSEG2 + 3] tq or (functional values): [Sync + Prop + Phase1 + Phase2] tq The data in the CANBIT register is the configuration input of the CAN protocol controller. The baud rate prescaler (configured by the BRP field) defines the length of the time quantum, the basic time
1029
unit of the bit time; the bit timing logic (configured by TSEG1, TSEG2, and SJW) defines the number of time quanta in the bit time. The processing of the bit time, the calculation of the position of the sample point, and occasional synchronizations are controlled by the CAN controller and are evaluated once per time quantum. The CAN controller translates messages to and from frames. In addition, the controller generates and discards the enclosing fixed format bits, inserts and extracts stuff bits, calculates and checks the CRC code, performs the error management, and decides which type of synchronization is to be used. The bit value is received or transmitted at the sample point. The information processing time (IPT) is the time after the sample point needed to calculate the next bit to be transmitted on the CAN bus. The IPT includes any of the following: retrieving the next data bit, handling a CRC bit, determining if bit stuffing is required, generating an error flag or simply going idle. The IPT is application-specific but may not be longer than 2 tq; the CAN's IPT is 0 tq. Its length is the lower limit of the programmed length of Phase2. In case of synchronization, Phase2 may be shortened to a value less than IPT, which does not affect bus timing.
17.3.16
Calculating the Bit Timing Parameters

Usually, the calculation of the bit timing configuration starts with a required bit rate or bit time. The resulting bit time (1/bit rate) must be an integer multiple of the system clock period. The bit time may consist of 4 to 25 time quanta. Several combinations may lead to the required bit time, allowing iterations of the following steps. The first part of the bit time to be defined is Prop. Its length depends on the delay times measured in the system. A maximum bus length as well as a maximum node delay has to be defined for expandable CAN bus systems. The resulting time for Prop is converted into time quanta (rounded up to the nearest integer multiple of tq). Sync is 1 tq long (fixed), which leaves (bit time - Prop - 1) tq for the two Phase Buffer Segments. If the number of remaining tq is even, the Phase Buffer Segments have the same length, that is, Phase2 = Phase1, else Phase2 = Phase1 + 1. The minimum nominal length of Phase2 has to be regarded as well. Phase2 may not be shorter than the CAN controller's Information Processing Time, which is, depending on the actual implementation, in the range of [0..2] tq. The length of the synchronization jump width is set to the least of 4, Phase1 or Phase2. The oscillator tolerance range necessary for the resulting configuration is calculated by the formula given below:
(1 df ) fnom fosc (1 + df ) fnom

where: df
(Phase _ seg1, Phase _ seg2) min 2 (13 tbit Phase _ Seg 2)
df = Maximum tolerance of oscillator frequency fosc =max =oscillator frequency df Actual 2 df fnom fnom = Nominal oscillator frequency Maximum frequency tolerance must take into account the following formulas:
April 25, 2012
( fnom fosc ( + fnom (1 1df )df )fnom fosc (1 +1df )df )fnom
(Phase _ seg1, Phase _ seg2) min (Phase _ seg1, Phase _ seg2) min df df 2 (13 tbit Phase _ Seg 2) 2 (13 tbit Phase _ Seg 2)
df df max 2= 2 dffnom max = df fnom
where: Phase1 and Phase2 are from Table 17-3 on page 1029 tbit = Bit Time dfmax = Maximum difference between two oscillators If more than one configuration is possible, that configuration allowing the highest oscillator tolerance range should be chosen. CAN nodes with different system clocks require different configurations to come to the same bit rate. The calculation of the propagation time in the CAN network, based on the nodes with the longest delay times, is done once for the whole network. The CAN system's oscillator tolerance range is limited by the node with the lowest tolerance range. The calculation may show that bus length or bit rate have to be decreased or that the oscillator frequencies' stability has to be increased in order to find a protocol-compliant configuration of the CAN bit timing.
17.3.16.1 Example for Bit Timing at High Baud Rate

In this example, the frequency of CAN clock is 25 MHz, and the bit rate is 1 Mbps. bit time = 1 s = n * tq = 5 * tq = 200 ns tq = (Baud rate Prescaler)/CAN Baud rate Prescaler = tq * CAN Baud rate Prescaler = 200E-9 * tSync = 1 * tq = 200 ns delay delay delay tProp of bus driver 50 ns of receiver circuit 30 ns of bus line (40m) 220 ns 400 ns = 2 * tq tq Clock Clock 25E6 = 5 \\fixed at 1 time quanta
\\400 is next integer multiple of tq
bit time = tSync + bit time = tSync + tPhase 1 + tPhase2 tPhase 1 + tPhase2 tPhase 1 + tPhase2 tPhase1 = 1 * tq tPhase2 = 1 * tq
tTSeg1 + tTSeg2 = 5 * tq tProp + tPhase 1 + tPhase2 = bit time - tSync - tProp = (5 * tq) - (1 * tq) - (2 * tq) = 2 * tq \\tPhase2 = tPhase1
1031
tTSeg1 = tProp + tPhase1 tTSeg1 = (2 * tq) + (1 * tq) tTSeg1 = 3 * tq tTSeg2 = tPhase2 tTSeg2 = (Information Processing Time + 1) * tq tTSeg2 = 1 * tq \\Assumes IPT=0 tSJW = 1 * tq \\Least of 4, Phase1 and Phase2
In the above example, the bit field values for the CANBIT register are:
TSEG2 = TSeg2 -1 = 1-1 =0 TSEG1 = TSeg1 -1 = 3-1 =2 SJW = SJW -1 = 1-1 =0 BRP = Baud rate prescaler - 1 = 5-1 =4
The final value programmed into the CANBIT register = 0x0204.
17.3.16.2 Example for Bit Timing at Low Baud Rate

In this example, the frequency of the CAN clock is 50 MHz, and the bit rate is 100 Kbps. bit time = 10 s = n * tq = 10 * tq tq = 1 s tq = (Baud rate Prescaler)/CAN Clock Baud rate Prescaler = tq * CAN Clock Baud rate Prescaler = 1E-6 * 50E6 = 50 tSync = 1 * tq = 1 s delay delay delay tProp of bus driver 200 ns of receiver circuit 80 ns of bus line (40m) 220 ns 1 s = 1 * tq \\fixed at 1 time quanta
\\1 s is next integer multiple of tq
bit time = tSync + bit time = tSync + tPhase 1 + tPhase2 tPhase 1 + tPhase2 tPhase 1 + tPhase2 tPhase1 = 4 * tq tPhase2 = 4 * tq
tTSeg1 + tTSeg2 = 10 * tq tProp + tPhase 1 + tPhase2 = bit time - tSync - tProp = (10 * tq) - (1 * tq) - (1 * tq) = 8 * tq \\tPhase1 = tPhase2
April 25, 2012
tTSeg1 tTSeg1 tTSeg1 tTSeg2 tTSeg2 tTSeg2
= = = = = =
tProp + tPhase1 (1 * tq) + (4 * tq) 5 * tq tPhase2 (Information Processing Time + 4) tq 4 * tq \\Assumes IPT=0 \\Least of 4, Phase1, and Phase2
= TSeg2 -1 = 4-1 =3
tSJW = 4 * tq
TSEG2
TSEG1
= TSeg1 -1 = 5-1 =4
SJW
= SJW -1 = 4-1 =3
BRP
= Baud rate prescaler - 1 = 50-1 =49
The final value programmed into the CANBIT register = 0x34F1.
17.4
Register Map
Table 17-5 on page 1033 lists the registers. All addresses given are relative to the CAN base address of: CAN0: 0x4004.0000 Note that the CAN controller clock must be enabled before the registers can be programmed (see page 323). There must be a delay of 3 system clocks after the CAN module clock is enabled before any CAN module registers are accessed.
Table 17-5. CAN Register Map

Offset 0x000 0x004 0x008 0x00C 0x010 0x014 0x018 0x020 0x024 Name CANCTL CANSTS CANERR CANBIT CANINT CANTST CANBRPE CANIF1CRQ CANIF1CMSK Type R/W R/W RO R/W RO R/W R/W R/W R/W Reset 0x0000.0001 0x0000.0000 0x0000.0000 0x0000.2301 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0001 0x0000.0000 Description CAN Control CAN Status CAN Error Counter CAN Bit Timing CAN Interrupt CAN Test CAN Baud Rate Prescaler Extension CAN IF1 Command Request CAN IF1 Command Mask See page 1035 1037 1040 1041 1042 1043 1045 1046 1047
1033
Table 17-5. CAN Register Map (continued)

Offset 0x028 0x02C 0x030 0x034 0x038 0x03C 0x040 0x044 0x048 0x080 0x084 0x088 0x08C 0x090 0x094 0x098 0x09C 0x0A0 0x0A4 0x0A8 0x100 0x104 0x120 0x124 0x140 0x144 0x160 0x164 Name CANIF1MSK1 CANIF1MSK2 CANIF1ARB1 CANIF1ARB2 CANIF1MCTL CANIF1DA1 CANIF1DA2 CANIF1DB1 CANIF1DB2 CANIF2CRQ CANIF2CMSK CANIF2MSK1 CANIF2MSK2 CANIF2ARB1 CANIF2ARB2 CANIF2MCTL CANIF2DA1 CANIF2DA2 CANIF2DB1 CANIF2DB2 CANTXRQ1 CANTXRQ2 CANNWDA1 CANNWDA2 CANMSG1INT CANMSG2INT CANMSG1VAL CANMSG2VAL Type R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W RO RO RO RO RO RO RO RO Reset 0x0000.FFFF 0x0000.FFFF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0001 0x0000.0000 0x0000.FFFF 0x0000.FFFF 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description CAN IF1 Mask 1 CAN IF1 Mask 2 CAN IF1 Arbitration 1 CAN IF1 Arbitration 2 CAN IF1 Message Control CAN IF1 Data A1 CAN IF1 Data A2 CAN IF1 Data B1 CAN IF1 Data B2 CAN IF2 Command Request CAN IF2 Command Mask CAN IF2 Mask 1 CAN IF2 Mask 2 CAN IF2 Arbitration 1 CAN IF2 Arbitration 2 CAN IF2 Message Control CAN IF2 Data A1 CAN IF2 Data A2 CAN IF2 Data B1 CAN IF2 Data B2 CAN Transmission Request 1 CAN Transmission Request 2 CAN New Data 1 CAN New Data 2 CAN Message 1 Interrupt Pending CAN Message 2 Interrupt Pending CAN Message 1 Valid CAN Message 2 Valid See page 1050 1051 1053 1054 1056 1059 1059 1059 1059 1046 1047 1050 1051 1053 1054 1056 1059 1059 1059 1059 1060 1060 1061 1061 1062 1062 1063 1063
17.5
CAN Register Descriptions

The remainder of this section lists and describes the CAN registers, in numerical order by address offset. There are two sets of Interface Registers that are used to access the Message Objects in the Message RAM: CANIF1x and CANIF2x. The function of the two sets are identical and are used to queue transactions.
April 25, 2012
Register 1: CAN Control (CANCTL), offset 0x000

This control register initializes the module and enables test mode and interrupts. The bus-off recovery sequence (see CAN Specification Rev. 2.0) cannot be shortened by setting or clearing INIT. If the device goes bus-off, it sets INIT, stopping all bus activities. Once INIT has been cleared by the CPU, the device then waits for 129 occurrences of Bus Idle (129 * 11 consecutive High bits) before resuming normal operations. At the end of the bus-off recovery sequence, the Error Management Counters are reset. During the waiting time after INIT is cleared, each time a sequence of 11 High bits has been monitored, a BITERROR0 code is written to the CANSTS register (the LEC field = 0x5), enabling the CPU to readily check whether the CAN bus is stuck Low or continuously disturbed, and to monitor the proceeding of the bus-off recovery sequence.
CAN Control (CANCTL)
CAN0 base: 0x4004.0000 Offset 0x000 Type R/W, reset 0x0000.0001
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 TEST RO 0 RO 0 RO 0 R/W 0 RO 0 6 CCE R/W 0 RO 0 5 DAR R/W 0 RO 0 4

reserved
RO 0 3 EIE R/W 0
RO 0 2 SIE R/W 0
RO 0 1 IE R/W 0
RO 0 0 INIT R/W 1
RO 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Test Mode Enable Value 0 1 Description The CAN controller is operating normally. The CAN controller is in test mode.
TEST
R/W
CCE
R/W
Configuration Change Enable Value 0 1 Description Write accesses to the CANBIT register are not allowed. Write accesses to the CANBIT register are allowed if the INIT bit is 1.
DAR
R/W
Disable Automatic-Retransmission Value 0 1 Description Auto-retransmission of disturbed messages is enabled. Auto-retransmission is disabled.
1035
Bit/Field 4
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Error Interrupt Enable Value 0 1 Description No error status interrupt is generated. A change in the BOFF or EWARN bits in the CANSTS register generates an interrupt.
EIE
R/W
SIE
R/W
Status Interrupt Enable Value 0 1 Description No status interrupt is generated. An interrupt is generated when a message has successfully been transmitted or received, or a CAN bus error has been detected. A change in the TXOK, RXOK or LEC bits in the CANSTS register generates an interrupt.
IE
R/W
CAN Interrupt Enable Value 0 1 Description Interrupts disabled. Interrupts enabled.
INIT
R/W
Initialization Value 0 1 Description Normal operation. Initialization started.
April 25, 2012
Register 2: CAN Status (CANSTS), offset 0x004

Important: This register is read-sensitive. See the register description for details. The status register contains information for interrupt servicing such as Bus-Off, error count threshold, and error types. The LEC field holds the code that indicates the type of the last error to occur on the CAN bus. This field is cleared when a message has been transferred (reception or transmission) without error. The unused error code 0x7 may be written by the CPU to manually set this field to an invalid error so that it can be checked for a change later. An error interrupt is generated by the BOFF and EWARN bits, and a status interrupt is generated by the RXOK, TXOK, and LEC bits, if the corresponding enable bits in the CAN Control (CANCTL) register are set. A change of the EPASS bit or a write to the RXOK, TXOK, or LEC bits does not generate an interrupt. Reading the CAN Status (CANSTS) register clears the CAN Interrupt (CANINT) register, if it is pending.
CAN Status (CANSTS)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 BOFF RO 0 RO 0 RO 0 RO 0 RO 0 6 EWARN RO 0 RO 0 5 EPASS RO 0 RO 0 4 RXOK R/W 0 RO 0 3 TXOK R/W 0 R/W 0 RO 0 2 RO 0 1 LEC R/W 0 R/W 0 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Bus-Off Status Value 0 1 Description The CAN controller is not in bus-off state. The CAN controller is in bus-off state.
BOFF
RO
EWARN
RO
Warning Status Value 0 1 Description Both error counters are below the error warning limit of 96. At least one of the error counters has reached the error warning limit of 96.
1037
Bit/Field 5
Name EPASS
Type RO
Reset 0
Description Error Passive Value 0 1 Description The CAN module is in the Error Active state, that is, the receive or transmit error count is less than or equal to 127. The CAN module is in the Error Passive state, that is, the receive or transmit error count is greater than 127.
RXOK
R/W
Received a Message Successfully Value 0 1 Description Since this bit was last cleared, no message has been successfully received. Since this bit was last cleared, a message has been successfully received, independent of the result of the acceptance filtering.
This bit must be cleared by writing a 0 to it. 3 TXOK R/W 0 Transmitted a Message Successfully Value 0 1 Description Since this bit was last cleared, no message has been successfully transmitted. Since this bit was last cleared, a message has been successfully transmitted error-free and acknowledged by at least one other node.
This bit must be cleared by writing a 0 to it.
April 25, 2012
Bit/Field 2:0
Name LEC
Type R/W
Reset 0x0
Description Last Error Code This is the type of the last error to occur on the CAN bus. Value 0x0 0x1 Description No Error Stuff Error More than 5 equal bits in a sequence have occurred in a part of a received message where this is not allowed. 0x2 Format Error A fixed format part of the received frame has the wrong format. 0x3 ACK Error The message transmitted was not acknowledged by another node. 0x4 Bit 1 Error When a message is transmitted, the CAN controller monitors the data lines to detect any conflicts. When the arbitration field is transmitted, data conflicts are a part of the arbitration protocol. When other frame fields are transmitted, data conflicts are considered errors. A Bit 1 Error indicates that the device wanted to send a High level (logical 1) but the monitored bus value was Low (logical 0). 0x5 Bit 0 Error A Bit 0 Error indicates that the device wanted to send a Low level (logical 0), but the monitored bus value was High (logical 1). During bus-off recovery, this status is set each time a sequence of 11 High bits has been monitored. By checking for this status, software can monitor the proceeding of the bus-off recovery sequence without any disturbances to the bus. 0x6 CRC Error The CRC checksum was incorrect in the received message, indicating that the calculated value received did not match the calculated CRC of the data. 0x7 No Event When the LEC bit shows this value, no CAN bus event was detected since this value was written to the LEC field.
1039
Register 3: CAN Error Counter (CANERR), offset 0x008

This register contains the error counter values, which can be used to analyze the cause of an error.
CAN Error Counter (CANERR)
CAN0 base: 0x4004.0000 Offset 0x008 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RP Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 14 RO 0 13 RO 0 12 RO 0 11 REC RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 TEC RO 0 RO 0 RO 0 RO 0 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Received Error Passive Value 0 1 Description The Receive Error counter is below the Error Passive level (127 or less). The Receive Error counter has reached the Error Passive level (128 or greater).
15
RP
RO
14:8
REC
RO
0x00
Receive Error Counter This field contains the state of the receiver error counter (0 to 127).
7:0
TEC
RO
0x00
Transmit Error Counter This field contains the state of the transmit error counter (0 to 255).
April 25, 2012
Register 4: CAN Bit Timing (CANBIT), offset 0x00C

This register is used to program the bit width and bit quantum. Values are programmed to the system clock frequency. This register is write-enabled by setting the CCE and INIT bits in the CANCTL register. See Bit Time and Bit Rate on page 1028 for more information.
CAN Bit Timing (CANBIT)
CAN0 base: 0x4004.0000 Offset 0x00C Type R/W, reset 0x0000.2301
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

reserved
RO 0 14
RO 0 13 TSEG2
RO 0 12
RO 0 11
RO 0 10 TSEG1
RO 0 9
RO 0 8
RO 0 7 SJW
RO 0 6
RO 0 5
RO 0 4
RO 0 3 BRP
RO 0 2
RO 0 1
RO 0 0
Type Reset
RO 0
R/W 0
R/W 1
R/W 0
R/W 0
R/W 0
R/W 1
R/W 1
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 1
Bit/Field 31:15
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Time Segment after Sample Point 0x00-0x07: The actual interpretation by the hardware of this value is such that one more than the value programmed here is used. So, for example, the reset value of 0x2 means that 3 (2+1) bit time quanta are defined for Phase2 (see Figure 17-4 on page 1029). The bit time quanta is defined by the BRP field.
14:12
TSEG2
R/W
0x2
11:8
TSEG1
R/W
0x3
Time Segment Before Sample Point 0x00-0x0F: The actual interpretation by the hardware of this value is such that one more than the value programmed here is used. So, for example, the reset value of 0x3 means that 4 (3+1) bit time quanta are defined for Phase1 (see Figure 17-4 on page 1029). The bit time quanta is defined by the BRP field.
7:6
SJW
R/W
0x0
(Re)Synchronization Jump Width 0x00-0x03: The actual interpretation by the hardware of this value is such that one more than the value programmed here is used. During the start of frame (SOF), if the CAN controller detects a phase error (misalignment), it can adjust the length of TSEG2 or TSEG1 by the value in SJW. So the reset value of 0 adjusts the length by 1 bit time quanta.
5:0
BRP
R/W
0x1
Baud Rate Prescaler The value by which the oscillator frequency is divided for generating the bit time quanta. The bit time is built up from a multiple of this quantum. 0x00-0x03F: The actual interpretation by the hardware of this value is such that one more than the value programmed here is used. BRP defines the number of CAN clock periods that make up 1 bit time quanta, so the reset value is 2 bit time quanta (1+1). The CANBRPE register can be used to further divide the bit time.
1041
Register 5: CAN Interrupt (CANINT), offset 0x010

This register indicates the source of the interrupt. If several interrupts are pending, the CAN Interrupt (CANINT) register points to the pending interrupt with the highest priority, disregarding the order in which the interrupts occurred. An interrupt remains pending until the CPU has cleared it. If the INTID field is not 0x0000 (the default) and the IE bit in the CANCTL register is set, the interrupt is active. The interrupt line remains active until the INTID field is cleared by reading the CANSTS register, or until the IE bit in the CANCTL register is cleared. Note: Reading the CAN Status (CANSTS) register clears the CAN Interrupt (CANINT) register, if it is pending.
CAN Interrupt (CANINT)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 INTID Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Identifier The number in this field indicates the source of the interrupt. Value 0x0000 0x0001-0x0020 0x0021-0x7FFF 0x8000 0x8001-0xFFFF Description No interrupt pending Number of the message object that caused the interrupt Reserved Status Interrupt Reserved
15:0
INTID
RO
0x0000
April 25, 2012
Register 6: CAN Test (CANTST), offset 0x014

This register is used for self-test and external pin access. It is write-enabled by setting the TEST bit in the CANCTL register. Different test functions may be combined, however, CAN transfers are affected if the TX bits in this register are not zero.
CAN Test (CANTST)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RX RO 0 RO 0 RO 0 RO 0 R/W 0 RO 0 6 TX R/W 0 RO 0 5 RO 0 4 LBACK R/W 0 RO 0 3 SILENT R/W 0 RO 0 2 BASIC R/W 0 RO 0 1 reserved RO 0 RO 0 RO 0 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Receive Observation Value 0 1 Description The CANnRx pin is low. The CANnRx pin is high.
RX
RO
6:5
TX
R/W
0x0
Transmit Control Overrides control of the CANnTx pin. Value 0x0 Description CAN Module Control CANnTx is controlled by the CAN module; default operation 0x1 Sample Point The sample point is driven on the CANnTx signal. This mode is useful to monitor bit timing. 0x2 Driven Low CANnTx drives a low value. This mode is useful for checking the physical layer of the CAN bus. 0x3 Driven High CANnTx drives a high value. This mode is useful for checking the physical layer of the CAN bus.
1043
Bit/Field 4
Name LBACK
Type R/W
Reset 0
Description Loopback Mode Value 0 1 Description Loopback mode is disabled. Loopback mode is enabled. In loopback mode, the data from the transmitter is routed into the receiver. Any data on the receive input is ignored.
SILENT
R/W
Silent Mode Value 0 1 Description Silent mode is disabled. Silent mode is enabled. In silent mode, the CAN controller does not transmit data but instead monitors the bus. This mode is also known as Bus Monitor mode.
BASIC
R/W
Basic Mode Value 0 1 Description Basic mode is disabled. Basic mode is enabled. In basic mode, software should use the CANIF1 registers as the transmit buffer and use the CANIF2 registers as the receive buffer.
1:0
reserved
RO
0x0
April 25, 2012
Register 7: CAN Baud Rate Prescaler Extension (CANBRPE), offset 0x018

This register is used to further divide the bit time set with the BRP bit in the CANBIT register. It is write-enabled by setting the CCE bit in the CANCTL register.
CAN Baud Rate Prescaler Extension (CANBRPE)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 BRPE R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:4
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Baud Rate Prescaler Extension 0x00-0x0F: Extend the BRP bit in the CANBIT register to values up to 1023. The actual interpretation by the hardware is one more than the value programmed by BRPE (MSBs) and BRP (LSBs).
3:0
BRPE
R/W
0x0
1045
Register 8: CAN IF1 Command Request (CANIF1CRQ), offset 0x020 Register 9: CAN IF2 Command Request (CANIF2CRQ), offset 0x080
A message transfer is started as soon as there is a write of the message object number to the MNUM field when the TXRQST bit in the CANIF1MCTL register is set. With this write operation, the BUSY bit is automatically set to indicate that a transfer between the CAN Interface Registers and the internal message RAM is in progress. After a wait time of 3 to 6 CAN_CLK periods, the transfer between the interface register and the message RAM completes, which then clears the BUSY bit.
CAN IFn Command Request (CANIFnCRQ)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 BUSY Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 reserved RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 9 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 MNUM R/W 0 R/W 0 R/W 0 R/W 1 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Busy Flag Value 0 1 Description This bit is cleared when read/write action has finished. This bit is set when a write occurs to the message number in this register.
15
BUSY
RO
14:6
reserved
RO
0x00
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Message Number Selects one of the 32 message objects in the message RAM for data transfer. The message objects are numbered from 1 to 32. Value 0x00 Description Reserved 0 is not a valid message number; it is interpreted as 0x20, or object 32. 0x01-0x20 0x21-0x3F Message Number Indicates specified message object 1 to 32. Reserved Not a valid message number; values are shifted and it is interpreted as 0x01-0x1F.
5:0
MNUM
R/W
0x01
April 25, 2012
Register 10: CAN IF1 Command Mask (CANIF1CMSK), offset 0x024 Register 11: CAN IF2 Command Mask (CANIF2CMSK), offset 0x084
Reading the Command Mask registers provides status for various functions. Writing to the Command Mask registers specifies the transfer direction and selects which buffer registers are the source or target of the data transfer. Note that when a read from the message object buffer occurs when the WRNRD bit is clear and the CLRINTPND and/or NEWDAT bits are set, the interrupt pending and/or new data flags in the message object buffer are cleared.
CAN IFn Command Mask (CANIFnCMSK)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 WRNRD RO 0 RO 0 RO 0 R/W 0 RO 0 6 MASK R/W 0 RO 0 5 ARB R/W 0 RO 0 4 RO 0 3 RO 0 2

NEWDAT / TXRQST
RO 0 1 DATAA R/W 0
RO 0 0 DATAB R/W 0
CONTROL CLRINTPND R/W 0 R/W 0
R/W 0
Bit/Field 31:8
Name reserved
Type RO
Reset 0x0000.00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Write, Not Read Value 0 Description Transfer the data in the CAN message object specified by the the MNUM field in the CANIFnCRQ register into the CANIFn registers. Transfer the data in the CANIFn registers to the CAN message object specified by the MNUM field in the CAN Command Request (CANIFnCRQ). Interrupt pending and new data conditions in the message buffer can be cleared by reading from the buffer (WRNRD = 0) when the CLRINTPND and/or NEWDAT bits are set.
WRNRD
R/W
Note:
MASK
R/W
Access Mask Bits Value 0 1 Description Mask bits unchanged. Transfer IDMASK + DIR + MXTD of the message object into the Interface registers.
1047
Bit/Field 5
Name ARB
Type R/W
Reset 0
Description Access Arbitration Bits Value 0 1 Description Arbitration bits unchanged. Transfer ID + DIR + XTD + MSGVAL of the message object into the Interface registers.
CONTROL
R/W
Access Control Bits Value 0 1 Description Control bits unchanged. Transfer control bits from the CANIFnMCTL register into the Interface registers.
CLRINTPND
R/W
Clear Interrupt Pending Bit The function of this bit depends on the configuration of the WRNRD bit. Value 0 Description If WRNRD is clear, the interrupt pending status is transferred from the message buffer into the CANIFnMCTL register. If WRNRD is set, the INTPND bit in the message object remains unchanged. 1 If WRNRD is clear, the interrupt pending status is cleared in the message buffer. Note the value of this bit that is transferred to the CANIFnMCTL register always reflects the status of the bits before clearing. If WRNRD is set, the INTPND bit is cleared in the message object.
NEWDAT / TXRQST
R/W
NEWDAT / TXRQST Bit The function of this bit depends on the configuration of the WRNRD bit. Value 0 Description If WRNRD is clear, the value of the new data status is transferred from the message buffer into the CANIFnMCTL register. If WRNRD is set, a transmission is not requested. 1 If WRNRD is clear, the new data status is cleared in the message buffer. Note the value of this bit that is transferred to the CANIFnMCTL register always reflects the status of the bits before clearing. If WRNRD is set, a transmission is requested. Note that when this bit is set, the TXRQST bit in the CANIFnMCTL register is ignored.
April 25, 2012
Bit/Field 1
Name DATAA
Type R/W
Reset 0
Description Access Data Byte 0 to 3 The function of this bit depends on the configuration of the WRNRD bit. Value 0 1 Description Data bytes 0-3 are unchanged. If WRNRD is clear, transfer data bytes 0-3 in CANIFnDA1 and CANIFnDA2 to the message object. If WRNRD is set, transfer data bytes 0-3 in message object to CANIFnDA1 and CANIFnDA2.
DATAB
R/W
Access Data Byte 4 to 7 The function of this bit depends on the configuration of the WRNRD bit as follows: Value 0 1 Description Data bytes 4-7 are unchanged. If WRNRD is clear, transfer data bytes 4-7 in CANIFnDA1 and CANIFnDA2 to the message object. If WRNRD is set, transfer data bytes 4-7 in message object to CANIFnDA1 and CANIFnDA2.
1049
Register 12: CAN IF1 Mask 1 (CANIF1MSK1), offset 0x028 Register 13: CAN IF2 Mask 1 (CANIF2MSK1), offset 0x088
The mask information provided in this register accompanies the data (CANIFnDAn), arbitration information (CANIFnARBn), and control information (CANIFnMCTL) to the message object in the message RAM. The mask is used with the ID bit in the CANIFnARBn register for acceptance filtering. Additional mask information is contained in the CANIFnMSK2 register.
CAN IFn Mask 1 (CANIFnMSK1)
CAN0 base: 0x4004.0000 Offset 0x028 Type R/W, reset 0x0000.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 MSK Type Reset R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 R/W 1 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Identifier Mask When using a 29-bit identifier, these bits are used for bits [15:0] of the ID. The MSK field in the CANIFnMSK2 register are used for bits [28:16] of the ID. When using an 11-bit identifier, these bits are ignored. Value 0 1 Description The corresponding identifier field (ID) in the message object cannot inhibit the match in acceptance filtering. The corresponding identifier field (ID) is used for acceptance filtering.
15:0
MSK
R/W
0xFFFF
April 25, 2012
Register 14: CAN IF1 Mask 2 (CANIF1MSK2), offset 0x02C Register 15: CAN IF2 Mask 2 (CANIF2MSK2), offset 0x08C
This register holds extended mask information that accompanies the CANIFnMSK1 register.
CAN IFn Mask 2 (CANIFnMSK2)
CAN0 base: 0x4004.0000 Offset 0x02C Type R/W, reset 0x0000.FFFF
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 MXTD Type Reset R/W 1 RO 0 14 MDIR R/W 1 RO 0 13

reserved
RO 0 12
RO 0 11
RO 0 10
RO 0 9
RO 0 8
RO 0 7
RO 0 6 MSK
RO 0 5
RO 0 4
RO 0 3
RO 0 2
RO 0 1
RO 0 0
RO 1
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 1
R/W 1
R/W 1
R/W 1
R/W 1
R/W 1
R/W 1
R/W 1
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Mask Extended Identifier Value 0 1 Description The extended identifier bit (XTD in the CANIFnARB2 register) has no effect on the acceptance filtering. The extended identifier bit XTD is used for acceptance filtering.
15
MXTD
R/W
14
MDIR
R/W
Mask Message Direction Value 0 1 Description The message direction bit (DIR in the CANIFnARB2 register) has no effect for acceptance filtering. The message direction bit DIR is used for acceptance filtering.
13
reserved
RO
1051
Bit/Field 12:0
Name MSK
Type R/W
Reset 0xFF
Description Identifier Mask When using a 29-bit identifier, these bits are used for bits [28:16] of the ID. The MSK field in the CANIFnMSK1 register are used for bits [15:0] of the ID. When using an 11-bit identifier, MSK[12:2] are used for bits [10:0] of the ID. Value 0 1 Description The corresponding identifier field (ID) in the message object cannot inhibit the match in acceptance filtering. The corresponding identifier field (ID) is used for acceptance filtering.
April 25, 2012
Register 16: CAN IF1 Arbitration 1 (CANIF1ARB1), offset 0x030 Register 17: CAN IF2 Arbitration 1 (CANIF2ARB1), offset 0x090
These registers hold the identifiers for acceptance filtering.
CAN IFn Arbitration 1 (CANIFnARB1)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 ID Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Message Identifier This bit field is used with the ID field in the CANIFnARB2 register to create the message identifier. When using a 29-bit identifier, bits 15:0 of the CANIFnARB1 register are [15:0] of the ID, while bits 12:0 of the CANIFnARB2 register are [28:16] of the ID. When using an 11-bit identifier, these bits are not used.
15:0
ID
R/W
0x0000
1053
Register 18: CAN IF1 Arbitration 2 (CANIF1ARB2), offset 0x034 Register 19: CAN IF2 Arbitration 2 (CANIF2ARB2), offset 0x094
These registers hold information for acceptance filtering.
CAN IFn Arbitration 2 (CANIFnARB2)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 MSGVAL Type Reset R/W 0 RO 0 14 XTD R/W 0 RO 0 13 DIR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 RO 0 6 ID R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Message Valid Value 0 1 Description The message object is ignored by the message handler. The message object is configured and ready to be considered by the message handler within the CAN controller.
15
MSGVAL
R/W
All unused message objects should have this bit cleared during initialization and before clearing the INIT bit in the CANCTL register. The MSGVAL bit must also be cleared before any of the following bits are modified or if the message object is no longer required: the ID fields in the CANIFnARBn registers, the XTD and DIR bits in the CANIFnARB2 register, or the DLC field in the CANIFnMCTL register. 14 XTD R/W 0 Extended Identifier Value 0 1 Description An 11-bit Standard Identifier is used for this message object. A 29-bit Extended Identifier is used for this message object.
April 25, 2012
Bit/Field 13
Name DIR
Type R/W
Reset 0
Description Message Direction Value 0 Description Receive. When the TXRQST bit in the CANIFnMCTL register is set, a remote frame with the identifier of this message object is received. On reception of a data frame with matching identifier, that message is stored in this message object. Transmit. When the TXRQST bit in the CANIFnMCTL register is set, the respective message object is transmitted as a data frame. On reception of a remote frame with matching identifier, the TXRQST bit of this message object is set (if RMTEN=1).
12:0
ID
R/W
0x000
Message Identifier This bit field is used with the ID field in the CANIFnARB2 register to create the message identifier. When using a 29-bit identifier, ID[15:0] of the CANIFnARB1 register are [15:0] of the ID, while these bits, ID[12:0], are [28:16] of the ID. When using an 11-bit identifier, ID[12:2] are used for bits [10:0] of the ID. The ID field in the CANIFnARB1 register is ignored.
1055
Register 20: CAN IF1 Message Control (CANIF1MCTL), offset 0x038 Register 21: CAN IF2 Message Control (CANIF2MCTL), offset 0x098
This register holds the control information associated with the message object to be sent to the Message RAM.
CAN IFn Message Control (CANIFnMCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 UMASK R/W 0 RO 0 11 TXIE R/W 0 RO 0 10 RXIE R/W 0 RO 0 9 RMTEN R/W 0 RO 0 8 TXRQST R/W 0 RO 0 7 EOB R/W 0 RO 0 RO 0 6 RO 0 5 reserved RO 0 RO 0 R/W 0 R/W 0 RO 0 4 RO 0 3 RO 0 2 DLC R/W 0 R/W 0 RO 0 1 RO 0 0
NEWDAT MSGLST INTPND Type Reset R/W 0 R/W 0 R/W 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. New Data Value 0 Description No new data has been written into the data portion of this message object by the message handler since the last time this flag was cleared by the CPU. The message handler or the CPU has written new data into the data portion of this message object.
15
NEWDAT
R/W
14
MSGLST
R/W
Message Lost Value 0 1 Description No message was lost since the last time this bit was cleared by the CPU. The message handler stored a new message into this object when NEWDAT was set; the CPU has lost a message.
This bit is only valid for message objects when the DIR bit in the CANIFnARB2 register is clear (receive). 13 INTPND R/W 0 Interrupt Pending Value 0 1 Description This message object is not the source of an interrupt. This message object is the source of an interrupt. The interrupt identifier in the CANINT register points to this message object if there is not another interrupt source with a higher priority.
April 25, 2012
Bit/Field 12
Name UMASK
Type R/W
Reset 0
Description Use Acceptance Mask Value 0 1 Description Mask is ignored. Use mask (MSK, MXTD, and MDIR bits in the CANIFnMSKn registers) for acceptance filtering.
11
TXIE
R/W
Transmit Interrupt Enable Value 0 1 Description The INTPND bit in the CANIFnMCTL register is unchanged after a successful transmission of a frame. The INTPND bit in the CANIFnMCTL register is set after a successful transmission of a frame.
10
RXIE
R/W
Receive Interrupt Enable Value 0 1 Description The INTPND bit in the CANIFnMCTL register is unchanged after a successful reception of a frame. The INTPND bit in the CANIFnMCTL register is set after a successful reception of a frame.
RMTEN
R/W
Remote Enable Value 0 1 Description At the reception of a remote frame, the TXRQST bit in the CANIFnMCTL register is left unchanged. At the reception of a remote frame, the TXRQST bit in the CANIFnMCTL register is set.
TXRQST
R/W
Transmit Request Value 0 1 Description This message object is not waiting for transmission. The transmission of this message object is requested and is not yet done. If the WRNRD and TXRQST bits in the CANIFnCMSK register are set, this bit is ignored.
Note:
1057
Bit/Field 7
Name EOB
Type R/W
Reset 0
Description End of Buffer Value 0 1 Description Message object belongs to a FIFO Buffer and is not the last message object of that FIFO Buffer. Single message object or last message object of a FIFO Buffer.
This bit is used to concatenate two or more message objects (up to 32) to build a FIFO buffer. For a single message object (thus not belonging to a FIFO buffer), this bit must be set. 6:4 reserved RO 0x0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Data Length Code Value 0x0-0x8 0x9-0xF Description Specifies the number of bytes in the data frame. Defaults to a data frame with 8 bytes.
3:0
DLC
R/W
0x0
The DLC field in the CANIFnMCTL register of a message object must be defined the same as in all the corresponding objects with the same identifier at other nodes. When the message handler stores a data frame, it writes DLC to the value given by the received message.
April 25, 2012
Register 22: CAN IF1 Data A1 (CANIF1DA1), offset 0x03C Register 23: CAN IF1 Data A2 (CANIF1DA2), offset 0x040 Register 24: CAN IF1 Data B1 (CANIF1DB1), offset 0x044 Register 25: CAN IF1 Data B2 (CANIF1DB2), offset 0x048 Register 26: CAN IF2 Data A1 (CANIF2DA1), offset 0x09C Register 27: CAN IF2 Data A2 (CANIF2DA2), offset 0x0A0 Register 28: CAN IF2 Data B1 (CANIF2DB1), offset 0x0A4 Register 29: CAN IF2 Data B2 (CANIF2DB2), offset 0x0A8
These registers contain the data to be sent or that has been received. In a CAN data frame, data byte 0 is the first byte to be transmitted or received and data byte 7 is the last byte to be transmitted or received. In CAN's serial bit stream, the MSB of each byte is transmitted first.
CAN IFn Data nn (CANIFnDnn)
CAN0 base: 0x4004.0000 Offset 0x03C Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 DATA Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Data The CANIFnDA1 registers contain data bytes 1 and 0; CANIFnDA2 data bytes 3 and 2; CANIFnDB1 data bytes 5 and 4; and CANIFnDB2 data bytes 7 and 6.
15:0
DATA
R/W
0x0000
1059
Register 30: CAN Transmission Request 1 (CANTXRQ1), offset 0x100 Register 31: CAN Transmission Request 2 (CANTXRQ2), offset 0x104
The CANTXRQ1 and CANTXRQ2 registers hold the TXRQST bits of the 32 message objects. By reading out these bits, the CPU can check which message object has a transmission request pending. The TXRQST bit of a specific message object can be changed by three sources: (1) the CPU via the CANIFnMCTL register, (2) the message handler state machine after the reception of a remote frame, or (3) the message handler state machine after a successful transmission. The CANTXRQ1 register contains the TXRQST bits of the first 16 message objects in the message RAM; the CANTXRQ2 register contains the TXRQST bits of the second 16 message objects.
CAN Transmission Request n (CANTXRQn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 TXRQST Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Transmission Request Bits Value 0 1 Description The corresponding message object is not waiting for transmission. The transmission of the corresponding message object is requested and is not yet done.
15:0
TXRQST
RO
0x0000
April 25, 2012
Register 32: CAN New Data 1 (CANNWDA1), offset 0x120 Register 33: CAN New Data 2 (CANNWDA2), offset 0x124
The CANNWDA1 and CANNWDA2 registers hold the NEWDAT bits of the 32 message objects. By reading these bits, the CPU can check which message object has its data portion updated. The NEWDAT bit of a specific message object can be changed by three sources: (1) the CPU via the CANIFnMCTL register, (2) the message handler state machine after the reception of a data frame, or (3) the message handler state machine after a successful transmission. The CANNWDA1 register contains the NEWDAT bits of the first 16 message objects in the message RAM; the CANNWDA2 register contains the NEWDAT bits of the second 16 message objects.
CAN New Data n (CANNWDAn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 NEWDAT Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. New Data Bits Value 0 Description No new data has been written into the data portion of the corresponding message object by the message handler since the last time this flag was cleared by the CPU. The message handler or the CPU has written new data into the data portion of the corresponding message object.
15:0
NEWDAT
RO
0x0000
1061
Register 34: CAN Message 1 Interrupt Pending (CANMSG1INT), offset 0x140 Register 35: CAN Message 2 Interrupt Pending (CANMSG2INT), offset 0x144
The CANMSG1INT and CANMSG2INT registers hold the INTPND bits of the 32 message objects. By reading these bits, the CPU can check which message object has an interrupt pending. The INTPND bit of a specific message object can be changed through two sources: (1) the CPU via the CANIFnMCTL register, or (2) the message handler state machine after the reception or transmission of a frame. This field is also encoded in the CANINT register. The CANMSG1INT register contains the INTPND bits of the first 16 message objects in the message RAM; the CANMSG2INT register contains the INTPND bits of the second 16 message objects.
CAN Message n Interrupt Pending (CANMSGnINT)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 INTPND Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Interrupt Pending Bits Value 0 1 Description The corresponding message object is not the source of an interrupt. The corresponding message object is the source of an interrupt.
15:0
INTPND
RO
0x0000
April 25, 2012
Register 36: CAN Message 1 Valid (CANMSG1VAL), offset 0x160 Register 37: CAN Message 2 Valid (CANMSG2VAL), offset 0x164
The CANMSG1VAL and CANMSG2VAL registers hold the MSGVAL bits of the 32 message objects. By reading these bits, the CPU can check which message object is valid. The message valid bit of a specific message object can be changed with the CANIFnARB2 register. The CANMSG1VAL register contains the MSGVAL bits of the first 16 message objects in the message RAM; the CANMSG2VAL register contains the MSGVAL bits of the second 16 message objects in the message RAM.
CAN Message n Valid (CANMSGnVAL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 MSGVAL Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Message Valid Bits Value 0 1 Description The corresponding message object is not configured and is ignored by the message handler. The corresponding message object is configured and should be considered by the message handler.
15:0
MSGVAL
RO
0x0000
1063
Universal Serial Bus (USB) Controller
18

The Stellaris USB controller operates as a full-speed or low-speed function controller during point-to-point communications with USB Host functions. The controller complies with the USB 2.0 standard, which includes SUSPEND and RESUME signaling. 16 endpoints including two hard-wired for control transfers (one endpoint for IN and one endpoint for OUT) plus 14 endpoints defined by firmware along with a dynamic sizable FIFO support multiple packet queueing. DMA access to the FIFO allows minimal interference from system software. Software-controlled connect and disconnect allows flexibility during USB device startup. The Stellaris USB module has the following features: Complies with USB-IF certification standards USB 2.0 full-speed (12 Mbps) and low-speed (1.5 Mbps) operation with integrated PHY 4 transfer types: Control, Interrupt, Bulk, and Isochronous 16 endpoints 1 dedicated control IN endpoint and 1 dedicated control OUT endpoint 7 configurable IN endpoints and 7 configurable OUT endpoints 4 KB dedicated endpoint memory: one endpoint may be defined for double-buffered 1023-byte isochronous packet size Efficient transfers using Micro Direct Memory Access Controller (DMA) Separate channels for transmit and receive for up to three IN endpoints and three OUT endpoints Channel requests asserted when FIFO contains required amount of data
18.1
Block Diagram
DMA Requests Endpoint Control CPU Interface Transmit EP0 31 Control Receive EP Reg. Decoder UTM Synchronization USB PHY Data Sync Packet Decode USB FS/LS PHY Timers CRC Gen/Check Cycle Control Tx Buff Tx Buff FIFO Decoder Packet Encode/Decode Packet Encode FIFO RAM Controller Rx Rx Buff Buff Common Regs Cycle Control AHB bus Slave mode Interrupts Interrupt Control
Figure 18-1. USB Module Block Diagram
USB Data Lines D+ and D-
April 25, 2012
18.2
Signal Description
The following table lists the external signals of the USB controller and describes the function of each. These signals have dedicated functions and are not alternate functions for any GPIO signals.
Table 18-1. USB Signals (64LQFP)

Pin Name USB0DM USB0DP Pin Number Pin Mux / Pin Assignment 43 44 PD4 PD5 Pin Type I/O I/O Buffer Type Analog Analog
a
Description Bidirectional differential data pin (D- per USB specification) for USB0. Bidirectional differential data pin (D+ per USB specification) for USB0.
18.3
The Stellaris USB controller provides the ability for the controller to serve as a Device-only controller. The controller can only be used in Device mode to connect USB-enabled peripherals to the USB controller. For Device mode, the USB controller requires a B connector in the system to provide Device connectivity. Note: When the USB module is in operation, MOSC must be the clock source, either with or without using the PLL, and the system clock must be at least 30 MHz.
18.3.1
Operation
This section describes the Stellaris USB controller's actions. IN endpoints, OUT endpoints, entry into and exit from SUSPEND mode, and recognition of Start of Frame (SOF) are all described. IN transactions are controlled by an endpoints transmit interface and use the transmit endpoint registers for the given endpoint. OUT transactions are handled with an endpoint's receive interface and use the receive endpoint registers for the given endpoint. When configuring the size of the FIFOs for endpoints, take into account the maximum packet size for an endpoint. Bulk. Bulk endpoints should be the size of the maximum packet (up to 64 bytes) or twice the maximum packet size if double buffering is used (described further in the following section). Interrupt. Interrupt endpoints should be the size of the maximum packet (up to 64 bytes) or twice the maximum packet size if double buffering is used. Isochronous. Isochronous endpoints are more flexible and can be up to 1023 bytes. Control. It is also possible to specify a separate control endpoint for a USB Device. However, in most cases the USB Device should use the dedicated control endpoint on the USB controllers endpoint 0.
18.3.1.1
Endpoints
The USB controller provides two dedicated control endpoints (IN and OUT) and 14 configurable endpoints (7 IN and 7 OUT) that can be used for communications with a Host controller. The endpoint number and direction associated with an endpoint is directly related to its register designation. For example, when the Host is transmitting to endpoint 1, all configuration and data is in the endpoint 1 transmit register interface.
1065
Endpoint 0 is a dedicated control endpoint used for all control transactions to endpoint 0 during enumeration or when any other control requests are made to endpoint 0. Endpoint 0 uses the first 64 bytes of the USB controller's FIFO RAM as a shared memory for both IN and OUT transactions. The remaining 14 endpoints can be configured as control, bulk, interrupt, or isochronous endpoints. They should be treated as 7 configurable IN and 7 configurable OUT endpoints. The endpoint pairs are not required to have the same type for their IN and OUT endpoint configuration. For example, the OUT portion of an endpoint pair could be a bulk endpoint, while the IN portion of that endpoint pair could be an interrupt endpoint. The address and size of the FIFOs attached to each endpoint can be modified to fit the application's needs.
18.3.1.2
IN Transactions
Data for IN transactions is handled through the FIFOs attached to the transmit endpoints. The sizes of the FIFOs for the 7 configurable IN endpoints are determined by the USB Transmit FIFO Start Address (USBTXFIFOADD) register. The maximum size of a data packet that may be placed in a transmit endpoints FIFO for transmission is programmable and is determined by the value written to the USB Maximum Transmit Data Endpoint n (USBTXMAXPn) register for that endpoint. The endpoints FIFO can also be configured to use double-packet or single-packet buffering. When double-packet buffering is enabled, two data packets can be buffered in the FIFO, which also requires that the FIFO is at least two packets in size. When double-packet buffering is disabled, only one packet can be buffered, even if the packet size is less than half the FIFO size. Note: The maximum packet size set for any endpoint must not exceed the FIFO size. The USBTXMAXPn register should not be written to while data is in the FIFO as unexpected results may occur.
Single-Packet Buffering If the size of the transmit endpoint's FIFO is less than twice the maximum packet size for this endpoint (as set in the USB Transmit Dynamic FIFO Sizing (USBTXFIFOSZ) register), only one packet can be buffered in the FIFO and single-packet buffering is required. When each packet is completely loaded into the transmit FIFO, the TXRDY bit in the USB Transmit Control and Status Endpoint n Low (USBTXCSRLn) register must be set. If the AUTOSET bit in the USB Transmit Control and Status Endpoint n High (USBTXCSRHn) register is set, the TXRDY bit is automatically set when a maximum-sized packet is loaded into the FIFO. For packet sizes less than the maximum, the TXRDY bit must be set manually. When the TXRDY bit is set, either manually or automatically, the packet is ready to be sent. When the packet has been successfully sent, both TXRDY and FIFONE are cleared, and the appropriate transmit endpoint interrupt signaled. At this point, the next packet can be loaded into the FIFO. Double-Packet Buffering If the size of the transmit endpoint's FIFO is at least twice the maximum packet size for this endpoint, two packets can be buffered in the FIFO and double-packet buffering is allowed. As each packet is loaded into the transmit FIFO, the TXRDY bit in the USBTXCSRLn register must be set. If the AUTOSET bit in the USBTXCSRHn register is set, the TXRDY bit is automatically set when a maximum-sized packet is loaded into the FIFO. For packet sizes less than the maximum, TXRDY must be set manually. When the TXRDY bit is set, either manually or automatically, the packet is ready to be sent. After the first packet is loaded, TXRDY is immediately cleared and an interrupt is generated. A second packet can now be loaded into the transmit FIFO and TXRDY set again (either manually or automatically if the packet is the maximum size). At this point, both packets are ready to be sent. After each packet has been successfully sent, TXRDY is automatically cleared and the appropriate transmit endpoint interrupt signaled to indicate that another packet can now be loaded into the transmit FIFO. The state of the FIFONE bit in the USBTXCSRLn register at this point
April 25, 2012
indicates how many packets may be loaded. If the FIFONE bit is set, then another packet is in the FIFO and only one more packet can be loaded. If the FIFONE bit is clear, then no packets are in the FIFO and two more packets can be loaded. Note: Double-packet buffering is disabled if an endpoints corresponding EPn bit is set in the USB Transmit Double Packet Buffer Disable (USBTXDPKTBUFDIS) register. This bit is set by default, so it must be cleared to enable double-packet buffering.
18.3.1.3
OUT Transactions
OUT transactions are handled through the USB controller receive FIFOs. The sizes of the receive FIFOs for the 7 configurable OUT endpoints are determined by the USB Receive FIFO Start Address (USBRXFIFOADD) register. The maximum amount of data received by an endpoint in any packet is determined by the value written to the USB Maximum Receive Data Endpoint n (USBRXMAXPn) register for that endpoint. When double-packet buffering is enabled, two data packets can be buffered in the FIFO. When double-packet buffering is disabled, only one packet can be buffered even if the packet is less than half the FIFO size. Note: In all cases, the maximum packet size must not exceed the FIFO size.
Single-Packet Buffering If the size of the receive endpoint FIFO is less than twice the maximum packet size for an endpoint, only one data packet can be buffered in the FIFO and single-packet buffering is required. When a packet is received and placed in the receive FIFO, the RXRDY and FULL bits in the USB Receive Control and Status Endpoint n Low (USBRXCSRLn) register are set and the appropriate receive endpoint is signaled, indicating that a packet can now be unloaded from the FIFO. After the packet has been unloaded, the RXRDY bit must be cleared in order to allow further packets to be received. This action also generates the acknowledge signaling to the Host controller. If the AUTOCL bit in the USB Receive Control and Status Endpoint n High (USBRXCSRHn) register is set and a maximum-sized packet is unloaded from the FIFO, the RXRDY and FULL bits are cleared automatically. For packet sizes less than the maximum, RXRDY must be cleared manually. Double-Packet Buffering If the size of the receive endpoint FIFO is at least twice the maximum packet size for the endpoint, two data packets can be buffered and double-packet buffering can be used. When the first packet is received and loaded into the receive FIFO, the RXRDY bit in the USBRXCSRLn register is set and the appropriate receive endpoint interrupt is signaled to indicate that a packet can now be unloaded from the FIFO. Note: The FULL bit in USBRXCSRLn is not set when the first packet is received. It is only set if a second packet is received and loaded into the receive FIFO.
After each packet has been unloaded, the RXRDY bit must be cleared to allow further packets to be received. If the AUTOCL bit in the USBRXCSRHn register is set and a maximum-sized packet is unloaded from the FIFO, the RXRDY bit is cleared automatically. For packet sizes less than the maximum, RXRDY must be cleared manually. If the FULL bit is set when RXRDY is cleared, the USB controller first clears the FULL bit, then sets RXRDY again to indicate that there is another packet waiting in the FIFO to be unloaded. Note: Double-packet buffering is disabled if an endpoints corresponding EPn bit is set in the USB Receive Double Packet Buffer Disable (USBRXDPKTBUFDIS) register. This bit is set by default, so it must be cleared to enable double-packet buffering.
1067
18.3.1.4
Scheduling
The Device has no control over the scheduling of transactions as scheduling is determined by the Host controller. The Stellaris USB controller can set up a transaction at any time. The USB controller waits for the request from the Host controller and generates an interrupt when the transaction is complete or if it was terminated due to some error. If the Host controller makes a request and the Device controller is not ready, the USB controller sends a busy response (NAK) to all requests until it is ready.
18.3.1.5
Additional Actions
The USB controller responds automatically to certain conditions on the USB bus or actions by the Host controller such as when the USB controller automatically stalls a control transfer or unexpected zero length OUT data packets. Stalled Control Transfer The USB controller automatically issues a STALL handshake to a control transfer under the following conditions: 1. The Host sends more data during an OUT data phase of a control transfer than was specified in the Device request during the SETUP phase. This condition is detected by the USB controller when the Host sends an OUT token (instead of an IN token) after the last OUT packet has been unloaded and the DATAEND bit in the USB Control and Status Endpoint 0 Low (USBCSRL0) register has been set. 2. The Host requests more data during an IN data phase of a control transfer than was specified in the Device request during the SETUP phase. This condition is detected by the USB controller when the Host sends an IN token (instead of an OUT token) after the CPU has cleared TXRDY and set DATAEND in response to the ACK issued by the Host to what should have been the last packet. 3. The Host sends more than USBRXMAXPn bytes of data with an OUT data token. 4. The Host sends more than a zero length data packet for the OUT STATUS phase. Zero Length OUT Data Packets A zero-length OUT data packet is used to indicate the end of a control transfer. In normal operation, such packets should only be received after the entire length of the Device request has been transferred. However, if the Host sends a zero-length OUT data packet before the entire length of Device request has been transferred, it is signaling the premature end of the transfer. In this case, the USB controller automatically flushes any IN token ready for the data phase from the FIFO and sets the DATAEND bit in the USBCSRL0 register. Setting the Device Address When a Host is attempting to enumerate the USB Device, it requests that the Device change its address from zero to some other value. The address is changed by writing the value that the Host requested to the USB Device Functional Address (USBFADDR) register. However, care should be taken when writing to USBFADDR to avoid changing the address before the transaction is complete. This register should only be set after the SET_ADDRESS command is complete. Like all control transactions, the transaction is only complete after the Device has left the STATUS phase. In the case of a SET_ADDRESS command, the transaction is completed by responding to the IN
April 25, 2012
request from the Host with a zero-byte packet. Once the Device has responded to the IN request, the USBFADDR register should be programmed to the new value as soon as possible to avoid missing any new commands sent to the new address. Note: If the USBFADDR register is set to the new value as soon as the Device receives the OUT transaction with the SET_ADDRESS command in the packet, it changes the address during the control transfer. In this case, the Device does not receive the IN request that allows the USB transaction to exit the STATUS phase of the control transfer because it is sent to the old address. As a result, the Host does not get a response to the IN request, and the Host fails to enumerate the Device.
18.3.1.6
SUSPEND
When no activity has occurred on the USB bus for 3 ms, the USB controller automatically enters SUSPEND mode. If the SUSPEND interrupt has been enabled in the USB Interrupt Enable (USBIE) register, an interrupt is generated at this time. When in SUSPEND mode, the PHY also goes into SUSPEND mode. When RESUME signaling is detected, the USB controller exits SUSPEND mode and takes the PHY out of SUSPEND. If the RESUME interrupt is enabled, an interrupt is generated. The USB controller can also be forced to exit SUSPEND mode by setting the RESUME bit in the USB Power (USBPOWER) register. When this bit is set, the USB controller exits SUSPEND mode and drives RESUME signaling onto the bus. The RESUME bit must be cleared after 10 ms (a maximum of 15 ms) to end RESUME signaling. To meet USB power requirements, the controller can be put into Deep Sleep mode which keeps the controller in a static state. The USB controller is not able to Hibernate because all the internal states are lost as a result.
18.3.1.7
Start-of-Frame
When the USB controller is operating in Device mode, it receives a Start-Of-Frame (SOF) packet from the Host once every millisecond. When the SOF packet is received, the 11-bit frame number contained in the packet is written into the USB Frame Value (USBFRAME) register, and an SOF interrupt is also signaled and can be handled by the application. Once the USB controller has started to receive SOF packets, it expects one every millisecond. If no SOF packet is received after 1.00358 ms, the packet is assumed to have been lost, and the USBFRAME register is not updated. The USB controller continues and resynchronizes these pulses to the received SOF packets when these packets are successfully received again.
18.3.1.8
USB RESET
When a RESET condition is detected on the USB bus, the USB controller automatically performs the following actions: Clears the USBFADDR register. Clears the USB Endpoint Index (USBEPIDX) register. Flushes all endpoint FIFOs. Clears all control/status registers. Enables all endpoint interrupts. Generates a RESET interrupt.
1069
When the application software driving the USB controller receives a RESET interrupt, any open pipes are closed and the USB controller waits for bus enumeration to begin.
18.3.1.9
Connect/Disconnect
The USB controller connection to the USB bus is handled by software. The USB PHY can be switched between normal mode and non-driving mode by setting or clearing the SOFTCONN bit of the USBPOWER register. When the SOFTCONN bit is set, the PHY is placed in its normal mode, and the USB0DP/USB0DM lines of the USB bus are enabled. At the same time, the USB controller is placed into a state, in which it does not respond to any USB signaling except a USB RESET. When the SOFTCONN bit is cleared, the PHY is put into non-driving mode, USB0DP and USB0DM are tristated, and the USB controller appears to other devices on the USB bus as if it has been disconnected. The non-driving mode is the default so the USB controller appears disconnected until the SOFTCONN bit has been set. The application software can then choose when to set the PHY into its normal mode. Systems with a lengthy initialization procedure may use this to ensure that initialization is complete, and the system is ready to perform enumeration before connecting to the USB bus. Once the SOFTCONN bit has been set, the USB controller can be disconnected by clearing this bit. Note: The USB controller does not generate an interrupt when the Device is connected to the Host. However, an interrupt is generated when the Host terminates a session.
18.3.2
DMA Operation
The USB peripheral provides an interface connected to the DMA controller with separate channels for 3 transmit endpoints and 3 receive endpoints. Software selects which endpoints to service with the DMA channels using the USB DMA Select (USBDMASEL) register. The DMA operation of the USB is enabled through the USBTXCSRHn and USBRXCSRHn registers, for the TX and RX channels respectively. When DMA operation is enabled, the USB asserts a DMA request on the enabled receive or transmit channel when the associated FIFO can transfer data. When either FIFO can transfer data, the burst request for that channel is asserted. The DMA channel must be configured to operate in Basic mode, and the size of the DMA transfer must be restricted to whole multiples of the size of the USB FIFO. Both read and write transfers of the USB FIFOs using DMA must be configured in this manner. For example, if the USB endpoint is configured with a FIFO size of 64 bytes, the DMA channel can be used to transfer 64 bytes to or from the endpoint FIFO. If the number of bytes to transfer is less than 64, then a programmed I/O method must be used to copy the data to or from the FIFO. If the DMAMOD bit in the USBTXCSRHn/USBRXCSRHn register is clear, an interrupt is generated after every packet is transferred, but the DMA continues transferring data. If the DMAMOD bit is set, an interrupt is generated only when the entire DMA transfer is complete. The interrupt occurs on the USB interrupt vector. Therefore, if interrupts are used for USB operation and the DMA is enabled, the USB interrupt handler must be designed to handle the DMA completion interrupt. Care must be taken when using the DMA to unload the receive FIFO as data is read from the receive FIFO in 4 byte chunks regardless of value of the MAXLOAD field in the USBRXCSRHn register. The RXRDY bit is cleared as follows. Table 18-2. Remainder (MAXLOAD/4)
Value 0 1 2 Description MAXLOAD = 64 bytes MAXLOAD = 61 bytes MAXLOAD = 62 bytes
April 25, 2012
Table 18-2. Remainder (MAXLOAD/4) (continued)

Value 3 Description MAXLOAD = 63 bytes
Table 18-3. Actual Bytes Read

Value 0 1 2 3 Description MAXLOAD MAXLOAD+3 MAXLOAD+2 MAXLOAD+1
Table 18-4. Packet Sizes That Clear RXRDY

Value 0 1 2 3 Description MAXLOAD, MAXLOAD-1, MAXLOAD-2, MAXLOAD-3 MAXLOAD MAXLOAD, MAXLOAD-1 MAXLOAD, MAXLOAD-1, MAXLOAD-2
To enable DMA operation for the endpoint receive channel, the DMAEN bit of the USBRXCSRHn register should be set. To enable DMA operation for the endpoint transmit channel, the DMAEN bit of the USBTXCSRHn register must be set. See Micro Direct Memory Access (DMA) on page 568 for more details about programming the DMA controller.
18.4

To use the USB Controller, the peripheral clock must be enabled via the RCGCUSB register (see page 322). The initial configuration in all cases requires that the processor enable the USB controller and USB controllers physical layer interface (PHY) before setting any registers. The next step is to enable the USB PLL so that the correct clocking is provided to the PHY. The USB controller provides a method to set the current operating mode of the USB controller. This register should be written with the desired default mode so that the controller can respond to external USB events.
18.4.1
Endpoint Configuration
To start communication, the endpoint registers must first be configured. An endpoint must be configured before enumerating to the Host controller. The endpoint 0 configuration is limited because it is a fixed-function, fixed-FIFO-size endpoint. The endpoint requires little setup but does require a software-based state machine to progress through the setup, data, and status phases of a standard control transaction. The configuration of the remaining endpoints is done once before enumerating and then only changed if an alternate configuration is selected by the Host controller. Once the type of endpoint is configured, a FIFO area must be assigned to each endpoint. In the case of bulk, control and interrupt endpoints, each has a maximum of 64 bytes per transaction. Isochronous endpoints can have packets with up to
1071
1023 bytes per packet. In either mode, the maximum packet size for the given endpoint must be set prior to sending or receiving data. Configuring each endpoints FIFO involves reserving a portion of the overall USB FIFO RAM to each endpoint. The total FIFO RAM available is 2 Kbytes with the first 64 bytes reserved for endpoint 0. The endpoints FIFO must be at least as large as the maximum packet size. The FIFO can also be configured as a double-buffered FIFO so that interrupts occur at the end of each packet and allow filling the other half of the FIFO. The USB Device controller's soft connect must be enabled when the Device is ready to start communications, indicating to the Host controller that the Device is ready to start the enumeration process.
18.5
Register Map
Table 18-5 on page 1072 lists the registers. All addresses given are relative to the USB base address of 0x4005.0000. Note that the USB controller clock must be enabled before the registers can be programmed (see page 322). There must be a delay of 3 system clocks after the USB module clock is enabled before any USB module registers are accessed.
Table 18-5. Universal Serial Bus (USB) Controller Register Map

Offset 0x000 0x001 0x002 0x004 0x006 0x008 0x00A 0x00B 0x00C 0x00E 0x00F 0x020 0x024 0x028 0x02C 0x030 0x034 0x038 0x03C 0x062 Name USBFADDR USBPOWER USBTXIS USBRXIS USBTXIE USBRXIE USBIS USBIE USBFRAME USBEPIDX USBTEST USBFIFO0 USBFIFO1 USBFIFO2 USBFIFO3 USBFIFO4 USBFIFO5 USBFIFO6 USBFIFO7 USBTXFIFOSZ Type R/W R/W RO RO R/W R/W RO R/W RO R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W R/W Reset 0x00 0x20 0x0000 0x0000 0xFFFF 0xFFFE 0x00 0x06 0x0000 0x00 0x00 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x00 Description USB Device Functional Address USB Power USB Transmit Interrupt Status USB Receive Interrupt Status USB Transmit Interrupt Enable USB Receive Interrupt Enable USB General Interrupt Status USB Interrupt Enable USB Frame Value USB Endpoint Index USB Test Mode USB FIFO Endpoint 0 USB FIFO Endpoint 1 USB FIFO Endpoint 2 USB FIFO Endpoint 3 USB FIFO Endpoint 4 USB FIFO Endpoint 5 USB FIFO Endpoint 6 USB FIFO Endpoint 7 USB Transmit Dynamic FIFO Sizing See page 1076 1077 1079 1081 1082 1084 1085 1086 1088 1089 1090 1091 1091 1091 1091 1091 1091 1091 1091 1092
April 25, 2012
Table 18-5. Universal Serial Bus (USB) Controller Register Map (continued)
Offset 0x063 0x064 0x066 0x07A 0x07D 0x07E 0x102 0x103 0x108 0x110 0x112 0x113 0x114 0x116 0x117 0x118 0x120 0x122 0x123 0x124 0x126 0x127 0x128 0x130 0x132 0x133 0x134 0x136 0x137 0x138 0x140 Name USBRXFIFOSZ USBTXFIFOADD USBRXFIFOADD USBCONTIM USBFSEOF USBLSEOF USBCSRL0 USBCSRH0 USBCOUNT0 USBTXMAXP1 USBTXCSRL1 USBTXCSRH1 USBRXMAXP1 USBRXCSRL1 USBRXCSRH1 USBRXCOUNT1 USBTXMAXP2 USBTXCSRL2 USBTXCSRH2 USBRXMAXP2 USBRXCSRL2 USBRXCSRH2 USBRXCOUNT2 USBTXMAXP3 USBTXCSRL3 USBTXCSRH3 USBRXMAXP3 USBRXCSRL3 USBRXCSRH3 USBRXCOUNT3 USBTXMAXP4 Type R/W R/W R/W R/W R/W R/W W1C W1C RO R/W R/W R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W RO R/W Reset 0x00 0x0000 0x0000 0x5C 0x77 0x72 0x00 0x00 0x00 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 Description USB Receive Dynamic FIFO Sizing USB Transmit FIFO Start Address USB Receive FIFO Start Address USB Connect Timing USB Full-Speed Last Transaction to End of Frame Timing USB Low-Speed Last Transaction to End of Frame Timing USB Control and Status Endpoint 0 Low USB Control and Status Endpoint 0 High USB Receive Byte Count Endpoint 0 USB Maximum Transmit Data Endpoint 1 USB Transmit Control and Status Endpoint 1 Low USB Transmit Control and Status Endpoint 1 High USB Maximum Receive Data Endpoint 1 USB Receive Control and Status Endpoint 1 Low USB Receive Control and Status Endpoint 1 High USB Receive Byte Count Endpoint 1 USB Maximum Transmit Data Endpoint 2 USB Transmit Control and Status Endpoint 2 Low USB Transmit Control and Status Endpoint 2 High USB Maximum Receive Data Endpoint 2 USB Receive Control and Status Endpoint 2 Low USB Receive Control and Status Endpoint 2 High USB Receive Byte Count Endpoint 2 USB Maximum Transmit Data Endpoint 3 USB Transmit Control and Status Endpoint 3 Low USB Transmit Control and Status Endpoint 3 High USB Maximum Receive Data Endpoint 3 USB Receive Control and Status Endpoint 3 Low USB Receive Control and Status Endpoint 3 High USB Receive Byte Count Endpoint 3 USB Maximum Transmit Data Endpoint 4 See page 1092 1093 1093 1094 1095 1096 1098 1100 1101 1097 1102 1104 1106 1107 1110 1112 1097 1102 1104 1106 1107 1110 1112 1097 1102 1104 1106 1107 1110 1112 1097
1073
Offset 0x142 0x143 0x144 0x146 0x147 0x148 0x150 0x152 0x153 0x154 0x156 0x157 0x158 0x160 0x162 0x163 0x164 0x166 0x167 0x168 0x170 0x172 0x173 0x174 0x176 0x177 0x178 0x340 0x342 0x410 0x414 0x418 Name USBTXCSRL4 USBTXCSRH4 USBRXMAXP4 USBRXCSRL4 USBRXCSRH4 USBRXCOUNT4 USBTXMAXP5 USBTXCSRL5 USBTXCSRH5 USBRXMAXP5 USBRXCSRL5 USBRXCSRH5 USBRXCOUNT5 USBTXMAXP6 USBTXCSRL6 USBTXCSRH6 USBRXMAXP6 USBRXCSRL6 USBRXCSRH6 USBRXCOUNT6 USBTXMAXP7 USBTXCSRL7 USBTXCSRH7 USBRXMAXP7 USBRXCSRL7 USBRXCSRH7 USBRXCOUNT7 USBRXDPKTBUFDIS USBTXDPKTBUFDIS USBDRRIS USBDRIM USBDRISC Type R/W R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W RO R/W R/W R/W R/W R/W R/W RO R/W R/W RO R/W W1C Reset 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x00 0x00 0x0000 0x00 0x00 0x0000 0x0000 0x0000 0x0000.0000 0x0000.0000 0x0000.0000 Description USB Transmit Control and Status Endpoint 4 Low USB Transmit Control and Status Endpoint 4 High USB Maximum Receive Data Endpoint 4 USB Receive Control and Status Endpoint 4 Low USB Receive Control and Status Endpoint 4 High USB Receive Byte Count Endpoint 4 USB Maximum Transmit Data Endpoint 5 USB Transmit Control and Status Endpoint 5 Low USB Transmit Control and Status Endpoint 5 High USB Maximum Receive Data Endpoint 5 USB Receive Control and Status Endpoint 5 Low USB Receive Control and Status Endpoint 5 High USB Receive Byte Count Endpoint 5 USB Maximum Transmit Data Endpoint 6 USB Transmit Control and Status Endpoint 6 Low USB Transmit Control and Status Endpoint 6 High USB Maximum Receive Data Endpoint 6 USB Receive Control and Status Endpoint 6 Low USB Receive Control and Status Endpoint 6 High USB Receive Byte Count Endpoint 6 USB Maximum Transmit Data Endpoint 7 USB Transmit Control and Status Endpoint 7 Low USB Transmit Control and Status Endpoint 7 High USB Maximum Receive Data Endpoint 7 USB Receive Control and Status Endpoint 7 Low USB Receive Control and Status Endpoint 7 High USB Receive Byte Count Endpoint 7 USB Receive Double Packet Buffer Disable USB Transmit Double Packet Buffer Disable USB Device RESUME Raw Interrupt Status USB Device RESUME Interrupt Mask USB Device RESUME Interrupt Status and Clear See page 1102 1104 1106 1107 1110 1112 1097 1102 1104 1106 1107 1110 1112 1097 1102 1104 1106 1107 1110 1112 1097 1102 1104 1106 1107 1110 1112 1113 1114 1115 1116 1117
April 25, 2012
Offset 0x450 0xFC0 Name USBDMASEL USBPP Type R/W RO Reset 0x0033.2211 0x0000.1050 Description USB DMA Select USB Peripheral Properties See page 1118 1120
18.6
The LM4F120H5QR USB controller has Device only capabilities as specified in the USB0 bit field in the DC6 register (see page 433).
1075
Register 1: USB Device Functional Address (USBFADDR), offset 0x000

USBFADDR is an 8-bit register that contains the 7-bit address of the Device part of the transaction. This register must be written with the address received through a SET_ADDRESS command, which is then used for decoding the function address in subsequent token packets. Important: See the section called Setting the Device Address on page 1068 for special considerations when writing this register.
USB Device Functional Address (USBFADDR)
Base 0x4005.0000 Offset 0x000 Type R/W, reset 0x00
7
reserved
3 FUNCADDR
Type Reset
RO 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
R/W 0
Bit/Field 7
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Function Address Function Address of Device as received through SET_ADDRESS.
6:0
FUNCADDR
R/W
0x00
April 25, 2012
Register 2: USB Power (USBPOWER), offset 0x001

USBPOWER is an 8-bit register used for controlling SUSPEND and RESUME signaling and some basic operational aspects of the USB controller.
USB Power (USBPOWER)
7 ISOUP Type Reset R/W 0 6
SOFTCONN
5 reserved RO 1
3 RESET RO 0
RESUME SUSPEND PWRDNPHY R/W 0 RO 0 R/W 0
R/W 0
RO 0
Bit/Field 7
Name ISOUP
Type R/W
Reset 0
Description Isochronous Update Value Description 1 The USB controller waits for an SOF token from the time the TXRDY bit is set in the USBTXCSRLn register before sending the packet. If an IN token is received before an SOF token, then a zero-length data packet is sent. No effect. This bit is only valid for isochronous transfers.
0 Note: 6 SOFTCONN R/W 0
Soft Connect/Disconnect Value Description 1 0 The USB D+/D- lines are enabled. The USB D+/D- lines are tri-stated.
5:4
reserved
RO
0x2
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RESET Signaling Value Description 1 0 RESET signaling is present on the bus. RESET signaling is not present on the bus.
RESET
RO
RESUME
R/W
RESUME Signaling Value Description 1 0 Enables RESUME signaling when the Device is in SUSPEND mode. Ends RESUME signaling on the bus.
This bit must be cleared by software 10 ms (a maximum of 15 ms) after being set.
1077
Bit/Field 1
Name SUSPEND
Type RO
Reset 0
Description SUSPEND Mode Value Description 1 0 The USB controller is in SUSPEND mode. This bit is cleared when software reads the interrupt register or sets the RESUME bit above.
PWRDNPHY
R/W
Power Down PHY Value Description 1 0 Powers down the internal USB PHY. No effect.
April 25, 2012
Register 3: USB Transmit Interrupt Status (USBTXIS), offset 0x002

Important: This register is read-sensitive. See the register description for details. USBTXIS is a 16-bit read-only register that indicates which interrupts are currently active for endpoint 0 and the transmit endpoints 17. The meaning of the EPn bits in this register is based on the mode of the device. The EP1 through EP7 bits always indicate that the USB controller is sending data; however, the bits refer to IN endpoints. The EP0 bit is special and indicates that either a control IN or control OUT endpoint has generated an interrupt. Note: Bits relating to endpoints that have not been configured always return 0. Note also that all active interrupts are cleared when this register is read.
USB Transmit Interrupt Status (USBTXIS)

Base 0x4005.0000 Offset 0x002 Type RO, reset 0x0000
15 14 13 12 11 10 9 8 7 EP7 RO 0 RO 0 RO 0 RO 0 6 EP6 RO 0 5 EP5 RO 0 4 EP4 RO 0 3 EP3 RO 0 2 EP2 RO 0 1 EP1 RO 0 0 EP0 RO 0
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. TX Endpoint 7 Interrupt Value Description 0 1 No interrupt. The Endpoint 7 transmit interrupt is asserted.
EP7
RO
EP6
RO
TX Endpoint 6 Interrupt Same description as EP7.
EP5
RO
EP4
RO
EP3
RO
EP2
RO
EP1
RO
1079
Bit/Field 0
Name EP0
Type RO
Reset 0
Description TX and RX Endpoint 0 Interrupt Value Description 0 1 No interrupt. The Endpoint 0 transmit and receive interrupt is asserted.
April 25, 2012
Register 4: USB Receive Interrupt Status (USBRXIS), offset 0x004

Important: This register is read-sensitive. See the register description for details. USBRXIS is a 16-bit read-only register that indicates which of the interrupts for receive endpoints 17 are currently active. Note: Bits relating to endpoints that have not been configured always return 0. Note also that all active interrupts are cleared when this register is read.
USB Receive Interrupt Status (USBRXIS)

15 14 13 12 11 10 9 8 7 EP7 RO 0 RO 0 RO 0 RO 0 6 EP6 RO 0 5 EP5 RO 0 4 EP4 RO 0 3 EP3 RO 0 2 EP2 RO 0 1 EP1 RO 0 0
reserved
RO 0
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RX Endpoint 7 Interrupt Value Description 0 1 No interrupt. The Endpoint 7 transmit interrupt is asserted.
EP7
RO
EP6
RO
RX Endpoint 6 Interrupt Same description as EP7.
EP5
RO
EP4
RO
EP3
RO
EP2
RO
EP1
RO
reserved
RO
1081
Register 5: USB Transmit Interrupt Enable (USBTXIE), offset 0x006

USBTXIE is a 16-bit register that provides interrupt enable bits for the interrupts in the USBTXIS register. When a bit is set, the USB interrupt is asserted to the interrupt controller when the corresponding interrupt bit in the USBTXIS register is set. When a bit is cleared, the interrupt in the USBTXIS register is still set but the USB interrupt to the interrupt controller is not asserted. On reset, all interrupts are enabled.
USB Transmit Interrupt Enable (USBTXIE)
Base 0x4005.0000 Offset 0x006 Type R/W, reset 0xFFFF
15 14 13 12 11 10 9 8 7 EP7 RO 0 RO 0 RO 0 R/W 1 6 EP6 R/W 1 5 EP5 R/W 1 4 EP4 R/W 1 3 EP3 R/W 1 2 EP2 R/W 1 1 EP1 R/W 1 0 EP0 R/W 1
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. TX Endpoint 7 Interrupt Enable Value Description 1 0 An interrupt is sent to the interrupt controller when the EP7 bit in the USBTXIS register is set. The EP7 transmit interrupt is suppressed and not sent to the interrupt controller.
EP7
R/W
EP6
R/W
TX Endpoint 6 Interrupt Enable Same description as EP7.
EP5
R/W
EP4
R/W
EP3
R/W
EP2
R/W
EP1
R/W
April 25, 2012
Bit/Field 0
Name EP0
Type R/W
Reset 1
Description TX and RX Endpoint 0 Interrupt Enable Value Description 1 0 An interrupt is sent to the interrupt controller when the EP0 bit in the USBTXIS register is set. The EP0 transmit and receive interrupt is suppressed and not sent to the interrupt controller.
1083
Register 6: USB Receive Interrupt Enable (USBRXIE), offset 0x008

USBRXIE is a 16-bit register that provides interrupt enable bits for the interrupts in the USBRXIS register. When a bit is set, the USB interrupt is asserted to the interrupt controller when the corresponding interrupt bit in the USBRXIS register is set. When a bit is cleared, the interrupt in the USBRXIS register is still set but the USB interrupt to the interrupt controller is not asserted. On reset, all interrupts are enabled.
USB Receive Interrupt Enable (USBRXIE)
Base 0x4005.0000 Offset 0x008 Type R/W, reset 0xFFFE
15 14 13 12 11 10 9 8 7 EP7 RO 0 RO 0 RO 0 R/W 1 6 EP6 R/W 1 5 EP5 R/W 1 4 EP4 R/W 1 3 EP3 R/W 1 2 EP2 R/W 1 1 EP1 R/W 1 0
reserved
RO 0
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RX Endpoint 7 Interrupt Enable Value Description 1 0 An interrupt is sent to the interrupt controller when the EP7 bit in the USBRXIS register is set. The EP7 receive interrupt is suppressed and not sent to the interrupt controller.
EP7
R/W
EP6
R/W
RX Endpoint 6 Interrupt Enable Same description as EP7.
EP5
R/W
EP4
R/W
EP3
R/W
EP2
R/W
EP1
R/W
reserved
RO
April 25, 2012
Register 7: USB General Interrupt Status (USBIS), offset 0x00A

Important: This register is read-sensitive. See the register description for details. USBIS is an 8-bit read-only register that indicates which USB interrupts are currently active. All active interrupts are cleared when this register is read.
USB General Interrupt Status (USBIS)
Base 0x4005.0000 Offset 0x00A Type RO, reset 0x00
7 6 reserved Type Reset RO 0 RO 0 RO 0 RO 0 5 4 3 SOF RO 0 2 RESET RO 0 1 0
RESUME SUSPEND RO 0 RO 0
Bit/Field 7:4
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Start of Frame Value Description 1 0 A new frame has started. No interrupt.
SOF
RO
RESET
RO
RESET Signaling Detected Value Description 1 0 RESET signaling has been detected on the bus. No interrupt.
RESUME
RO
RESUME Signaling Detected Value Description 1 0 RESUME signaling has been detected on the bus while the USB controller is in SUSPEND mode. No interrupt.
This interrupt can only be used if the USB controller's system clock is enabled. If the user disables the clock programming, the USBDRRIS, USBDRIM, and USBDRISC registers should be used. 0 SUSPEND RO 0 SUSPEND Signaling Detected Value Description 1 0 SUSPEND signaling has been detected on the bus. No interrupt.
1085
Register 8: USB Interrupt Enable (USBIE), offset 0x00B

USBIE is an 8-bit register that provides interrupt enable bits for each of the interrupts in USBIS. At reset interrupts 1 and 2 are enabled.
USB Interrupt Enable (USBIE)
Base 0x4005.0000 Offset 0x00B Type R/W, reset 0x06
7 reserved Type Reset RO 0 RO 0 6 5 DISCON R/W 0 4
reserved
3 SOF R/W 0
2 RESET R/W 1
RESUME SUSPEND R/W 1 R/W 0
RO 0
Bit/Field 7:6
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Enable Disconnect Interrupt Value Description 1 0 An interrupt is sent to the interrupt controller when the DISCON bit in the USBIS register is set. The DISCON interrupt is suppressed and not sent to the interrupt controller.
DISCON
R/W
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Enable Start-of-Frame Interrupt Value Description 1 0 An interrupt is sent to the interrupt controller when the SOF bit in the USBIS register is set. The SOF interrupt is suppressed and not sent to the interrupt controller.
SOF
R/W
RESET
R/W
Enable RESET Interrupt Value Description 1 0 An interrupt is sent to the interrupt controller when the RESET bit in the USBIS register is set. The RESET interrupt is suppressed and not sent to the interrupt controller.
April 25, 2012
Bit/Field 1
Name RESUME
Type R/W
Reset 1
Description Enable RESUME Interrupt Value Description 1 0 An interrupt is sent to the interrupt controller when the RESUME bit in the USBIS register is set. The RESUME interrupt is suppressed and not sent to the interrupt controller.
SUSPEND
R/W
Enable SUSPEND Interrupt Value Description 1 0 An interrupt is sent to the interrupt controller when the SUSPEND bit in the USBIS register is set. The SUSPEND interrupt is suppressed and not sent to the interrupt controller.
1087
Register 9: USB Frame Value (USBFRAME), offset 0x00C

USBFRAME is a 16-bit read-only register that holds the last received frame number.
USB Frame Value (USBFRAME)
Base 0x4005.0000 Offset 0x00C Type RO, reset 0x0000
15 14 13 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 12 11 10 9 8 7 6 5 FRAME RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 4 3 2 1 0
Bit/Field 15:11
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Frame Number
10:0
FRAME
RO
0x000
April 25, 2012
Register 10: USB Endpoint Index (USBEPIDX), offset 0x00E

Each endpoint's buffer can be accessed by configuring a FIFO size and starting address. The USBEPIDX 8-bit register is used with the USBTXFIFOSZ, USBRXFIFOSZ, USBTXFIFOADD, and USBRXFIFOADD registers.
USB Endpoint Index (USBEPIDX)
Base 0x4005.0000 Offset 0x00E Type R/W, reset 0x00
7 6 reserved Type Reset RO 0 RO 0 RO 0 RO 0 R/W 0 5 4 3 2 EPIDX R/W 0 R/W 0 R/W 0 1 0
Bit/Field 7:4
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Endpoint Index This bit field configures which endpoint is accessed when reading or writing to one of the USB controller's indexed registers. A value of 0x0 corresponds to Endpoint 0 and a value of 0x7 corresponds to Endpoint 7.
3:0
EPIDX
R/W
0x0
1089
Register 11: USB Test Mode (USBTEST), offset 0x00F

USBTEST is an 8-bit register that is primarily used to put the USB controller into one of the four test modes for operation described in the USB 2.0 Specification, in response to a SET FEATURE: USBTESTMODE command. This register is not used in normal operation. Note: Only one of these bits should be set at any time.
USB Test Mode (USBTEST)

Base 0x4005.0000 Offset 0x00F Type R/W, reset 0x00
7
reserved
2 reserved
FIFOACC FORCEFS R/W1S 0 R/W 0 RO 0 RO 0
Type Reset
RO 0
RO 0
RO 0
RO 0
Bit/Field 7
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. FIFO Access Value Description 1 0 Transfers the packet in the endpoint 0 transmit FIFO to the endpoint 0 receive FIFO. No effect.
FIFOACC
R/W1S
This bit is cleared automatically. 5 FORCEFS R/W 0 Force Full-Speed Mode Value Description 1 0 Forces the USB controller into Full-Speed mode upon receiving a USB RESET. The USB controller operates at Low Speed.
4:0
reserved
RO
0x0
April 25, 2012
Register 12: USB FIFO Endpoint 0 (USBFIFO0), offset 0x020 Register 13: USB FIFO Endpoint 1 (USBFIFO1), offset 0x024 Register 14: USB FIFO Endpoint 2 (USBFIFO2), offset 0x028 Register 15: USB FIFO Endpoint 3 (USBFIFO3), offset 0x02C Register 16: USB FIFO Endpoint 4 (USBFIFO4), offset 0x030 Register 17: USB FIFO Endpoint 5 (USBFIFO5), offset 0x034 Register 18: USB FIFO Endpoint 6 (USBFIFO6), offset 0x038 Register 19: USB FIFO Endpoint 7 (USBFIFO7), offset 0x03C
Important: This register is read-sensitive. See the register description for details. These 32-bit registers provide an address for CPU access to the FIFOs for each endpoint. Writing to these addresses loads data into the Transmit FIFO for the corresponding endpoint. Reading from these addresses unloads data from the Receive FIFO for the corresponding endpoint. Transfers to and from FIFOs may be 8-bit, 16-bit or 32-bit as required, and any combination of accesses is allowed provided the data accessed is contiguous. All transfers associated with one packet must be of the same width so that the data is consistently byte-, halfword- or word-aligned. However, the last transfer may contain fewer bytes than the previous transfers in order to complete an odd-byte or odd-word transfer. Depending on the size of the FIFO and the expected maximum packet size, the FIFOs support either single-packet or double-packet buffering (see the section called Single-Packet Buffering on page 1067). Burst writing of multiple packets is not supported as flags must be set after each packet is written. Following a STALL response or a transmit error on endpoint 17, the associated FIFO is completely flushed.
USB FIFO Endpoint n (USBFIFOn)
Base 0x4005.0000 Offset 0x020 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
EPDATA Type Reset R/W 0 15 R/W 0 14 R/W 0 13 R/W 0 12 R/W 0 11 R/W 0 10 R/W 0 9 R/W 0 8 EPDATA Type Reset R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 R/W 0 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0
Bit/Field 31:0
Name EPDATA
Type R/W
Reset
Description
0x0000.0000 Endpoint Data Writing to this register loads the data into the Transmit FIFO and reading unloads data from the Receive FIFO.
1091
Register 20: USB Transmit Dynamic FIFO Sizing (USBTXFIFOSZ), offset 0x062 Register 21: USB Receive Dynamic FIFO Sizing (USBRXFIFOSZ), offset 0x063
These 8-bit registers allow the selected TX/RX endpoint FIFOs to be dynamically sized. USBEPIDX is used to configure each transmit endpoint's FIFO size.
USB Dynamic FIFO Sizing (USBnXFIFOSZ)
7 6 reserved Type Reset RO 0 RO 0 RO 0 5 4 DPB R/W 0 R/W 0 R/W 0 3 2 SIZE R/W 0 R/W 0 1 0
Bit/Field 7:5
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Double Packet Buffer Support Value Description 0 1 Only single-packet buffering is supported. Double-packet buffering is supported.
DPB
R/W
3:0
SIZE
R/W
0x0
Max Packet Size Maximum packet size to be allowed. If DPB = 0, the FIFO also is this size; if DPB = 1, the FIFO is twice this size. Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 Packet Size (Bytes) 8 16 32 64 128 256 512 1024 2048
0x9-0xF Reserved
April 25, 2012
Register 22: USB Transmit FIFO Start Address (USBTXFIFOADD), offset 0x064 Register 23: USB Receive FIFO Start Address (USBRXFIFOADD), offset 0x066
USBTXFIFOADD and USBRXFIFOADD are 16-bit registers that control the start address of the selected transmit and receive endpoint FIFOs.
USB Transmit FIFO Start Address (USBnXFIFOADD)
15 14 13 12 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 11 10 9 8 7 6 5 4 ADDR R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 3 2 1 0
Bit/Field 15:9
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Transmit/Receive Start Address Start address of the endpoint FIFO. Value Start Address 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 ... 0 8 16 24 32 40 48 56 64 ...
8:0
ADDR
R/W
0x00
0x1FF 4095
1093
Register 24: USB Connect Timing (USBCONTIM), offset 0x07A

This 8-bit configuration register specifies connection delay.
USB Connect Timing (USBCONTIM)
Base 0x4005.0000 Offset 0x07A Type R/W, reset 0x5C
7 6 WTCON Type Reset R/W 0 R/W 1 R/W 0 R/W 1 R/W 1 R/W 1 5 4 3 2 WTID R/W 0 R/W 0 1 0
Bit/Field 7:4
Name WTCON
Type R/W
Reset 0x5
Description Connect Wait This field configures the wait required to allow for the users connect/disconnect filter, in units of 533.3 ns. The default corresponds to 2.667 s.
3:0
WTID
R/W
0xC
Wait ID This field configures the delay required from the enable of the ID detection to when the ID value is valid, in units of 4.369 ms. The default corresponds to 52.43 ms.
April 25, 2012
Register 25: USB Full-Speed Last Transaction to End of Frame Timing (USBFSEOF), offset 0x07D
This 8-bit configuration register specifies the minimum time gap allowed between the start of the last transaction and the EOF for full-speed transactions.
USB Full-Speed Last Transaction to End of Frame Timing (USBFSEOF)
Base 0x4005.0000 Offset 0x07D Type R/W, reset 0x77
7 6 5 4 FSEOFG Type Reset R/W 0 R/W 1 R/W 1 R/W 1 R/W 0 R/W 1 R/W 1 R/W 1 3 2 1 0
Bit/Field 7:0
Name FSEOFG
Type R/W
Reset 0x77
Description Full-Speed End-of-Frame Gap This field is used during full-speed transactions to configure the gap between the last transaction and the End-of-Frame (EOF), in units of 533.3 ns. The default corresponds to 63.46 s.
1095
Register 26: USB Low-Speed Last Transaction to End of Frame Timing (USBLSEOF), offset 0x07E
This 8-bit configuration register specifies the minimum time gap that is to be allowed between the start of the last transaction and the EOF for low-speed transactions.
USB Low-Speed Last Transaction to End of Frame Timing (USBLSEOF)
Base 0x4005.0000 Offset 0x07E Type R/W, reset 0x72
7 6 5 4 LSEOFG Type Reset R/W 0 R/W 1 R/W 1 R/W 1 R/W 0 R/W 0 R/W 1 R/W 0 3 2 1 0
Bit/Field 7:0
Name LSEOFG
Type R/W
Reset 0x72
Description Low-Speed End-of-Frame Gap This field is used during low-speed transactions to set the gap between the last transaction and the End-of-Frame (EOF), in units of 1.067 s. The default corresponds to 121.6 s.
April 25, 2012
Register 27: USB Maximum Transmit Data Endpoint 1 (USBTXMAXP1), offset 0x110 Register 28: USB Maximum Transmit Data Endpoint 2 (USBTXMAXP2), offset 0x120 Register 29: USB Maximum Transmit Data Endpoint 3 (USBTXMAXP3), offset 0x130 Register 30: USB Maximum Transmit Data Endpoint 4 (USBTXMAXP4), offset 0x140 Register 31: USB Maximum Transmit Data Endpoint 5 (USBTXMAXP5), offset 0x150 Register 32: USB Maximum Transmit Data Endpoint 6 (USBTXMAXP6), offset 0x160 Register 33: USB Maximum Transmit Data Endpoint 7 (USBTXMAXP7), offset 0x170
The USBTXMAXPn 16-bit register defines the maximum amount of data that can be transferred through the transmit endpoint in a single operation. Bits 10:0 define (in bytes) the maximum payload transmitted in a single transaction. The value set can be up to 1024 bytes but is subject to the constraints placed by the USB Specification on packet sizes for bulk, interrupt and isochronous transfers in full-speed operation. The total amount of data represented by the value written to this register must not exceed the FIFO size for the transmit endpoint, and must not exceed half the FIFO size if double-buffering is required. If this register is changed after packets have been sent from the endpoint, the transmit endpoint FIFO must be completely flushed (using the FLUSH bit in USBTXCSRLn) after writing the new value to this register. Note: USBTXMAXPn must be set to an even number of bytes for proper interrupt generation in DMA Basic Mode.
USB Maximum Transmit Data Endpoint n (USBTXMAXPn)

15 14 13 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 12 11 10 9 8 7 6 5 MAXLOAD R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 4 3 2 1 0
Bit/Field 15:11
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Maximum Payload This field specifies the maximum payload in bytes per transaction.
10:0
MAXLOAD
R/W
0x000
1097
Register 34: USB Control and Status Endpoint 0 Low (USBCSRL0), offset 0x102
USBCSRL0 is an 8-bit register that provides control and status bits for endpoint 0.
USB Control and Status Endpoint 0 Low (USBCSRL0)
Base 0x4005.0000 Offset 0x102 Type W1C, reset 0x00
7 6 5 STALL R/W 0 4 3 2 1 TXRDY R/W 0 0 RXRDY RO 0
SETENDC RXRDYC Type Reset W1C 0 W1C 0
SETEND DATAEND STALLED RO 0 R/W 0 R/W 0
Bit/Field 7
Name SETENDC
Type W1C
Reset 0
Description Setup End Clear Writing a 1 to this bit clears the SETEND bit.
RXRDYC
W1C
RXRDY Clear Writing a 1 to this bit clears the RXRDY bit.
STALL
R/W
Send Stall Value Description 0 1 No effect. Terminates the current transaction and transmits the STALL handshake.
This bit is cleared automatically after the STALL handshake is transmitted. 4 SETEND RO 0 Setup End Value Description 0 1 A control transaction has not ended or ended after the DATAEND bit was set. A control transaction has ended before the DATAEND bit has been set. The EP0 bit in the USBTXIS register is also set in this situation.
This bit is cleared by writing a 1 to the SETENDC bit. 3 DATAEND R/W 0 Data End Value Description 0 1 No effect. Set this bit in the following situations: When setting TXRDY for the last data packet When clearing RXRDY after unloading the last data packet When setting TXRDY for a zero-length data packet
This bit is cleared automatically.
April 25, 2012
Bit/Field 2
Name STALLED
Type R/W
Reset 0
Description Endpoint Stalled Value Description 0 1 A STALL handshake has not been transmitted. A STALL handshake has been transmitted.
Software must clear this bit. 1 TXRDY R/W 0 Transmit Packet Ready Value Description 0 1 No transmit packet is ready. Software sets this bit after loading an IN data packet into the TX FIFO. The EP0 bit in the USBTXIS register is also set in this situation.
This bit is cleared automatically when the data packet has been transmitted. 0 RXRDY RO 0 Receive Packet Ready Value Description 0 1 No data packet has been received. A data packet has been received. The EP0 bit in the USBTXIS register is also set in this situation.
This bit is cleared by writing a 1 to the RXRDYC bit.
1099
Register 35: USB Control and Status Endpoint 0 High (USBCSRH0), offset 0x103
USBSR0H is an 8-bit register that provides control and status bits for endpoint 0.
USB Control and Status Endpoint 0 High (USBCSRH0)
Base 0x4005.0000 Offset 0x103 Type W1C, reset 0x00
7 6 5 4 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 3 2 1 0 FLUSH R/W 0
Bit/Field 7:1
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Flush FIFO Value Description 0 1 No effect. Flushes the next packet to be transmitted/read from the endpoint 0 FIFO. The FIFO pointer is reset and the TXRDY/RXRDY bit is cleared.
FLUSH
R/W
This bit is automatically cleared after the flush is performed.
Important:
This bit should only be set when TXRDY/RXRDY is set. At other times, it may cause data to be corrupted.
April 25, 2012
Register 36: USB Receive Byte Count Endpoint 0 (USBCOUNT0), offset 0x108
USBCOUNT0 is an 8-bit read-only register that indicates the number of received data bytes in the endpoint 0 FIFO. The value returned changes as the contents of the FIFO change and is only valid while the RXRDY bit is set.
USB Receive Byte Count Endpoint 0 (USBCOUNT0)
7
reserved
3 COUNT
Type Reset
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 7
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. FIFO Count COUNT is a read-only value that indicates the number of received data bytes in the endpoint 0 FIFO.
6:0
COUNT
RO
0x00
1101
Register 37: USB Transmit Control and Status Endpoint 1 Low (USBTXCSRL1), offset 0x112 Register 38: USB Transmit Control and Status Endpoint 2 Low (USBTXCSRL2), offset 0x122 Register 39: USB Transmit Control and Status Endpoint 3 Low (USBTXCSRL3), offset 0x132 Register 40: USB Transmit Control and Status Endpoint 4 Low (USBTXCSRL4), offset 0x142 Register 41: USB Transmit Control and Status Endpoint 5 Low (USBTXCSRL5), offset 0x152 Register 42: USB Transmit Control and Status Endpoint 6 Low (USBTXCSRL6), offset 0x162 Register 43: USB Transmit Control and Status Endpoint 7 Low (USBTXCSRL7), offset 0x172
USBTXCSRLn is an 8-bit register that provides control and status bits for transfers through the currently selected transmit endpoint.
USB Transmit Control and Status Endpoint n Low (USBTXCSRLn)
7
reserved
6 CLRDT R/W 0
5 STALLED R/W 0
4 STALL R/W 0
3 FLUSH R/W 0
2 UNDRN R/W 0
1 FIFONE R/W 0
0 TXRDY R/W 0
Type Reset
RO 0
Bit/Field 7
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Clear Data Toggle Writing a 1 to this bit clears the DT bit in the USBTXCSRHn register.
CLRDT
R/W
STALLED
R/W
Endpoint Stalled Value Description 0 1 A STALL handshake has not been transmitted. A STALL handshake has been transmitted. The FIFO is flushed and the TXRDY bit is cleared.
Software must clear this bit.
April 25, 2012
Bit/Field 4
Name STALL
Type R/W
Reset 0
Description Send STALL Value Description 0 1 No effect. Issues a STALL handshake to an IN token.
Software clears this bit to terminate the STALL condition. Note: 3 FLUSH R/W 0 This bit has no effect in isochronous transfers.
Flush FIFO Value Description 0 1 No effect. Flushes the latest packet from the endpoint transmit FIFO. The FIFO pointer is reset and the TXRDY bit is cleared. The EPn bit in the USBTXIS register is also set in this situation.
This bit may be set simultaneously with the TXRDY bit to abort the packet that is currently being loaded into the FIFO. Note that if the FIFO is double-buffered, FLUSH may have to be set twice to completely clear the FIFO.
Important:
2 UNDRN R/W 0 Underrun
This bit should only be set when the TXRDY bit is set. At other times, it may cause data to be corrupted.
Value Description 0 1 No underrun. An IN token has been received when TXRDY is not set.
Software must clear this bit. 1 FIFONE R/W 0 FIFO Not Empty Value Description 0 1 The FIFO is empty. At least one packet is in the transmit FIFO.
TXRDY
R/W
Transmit Packet Ready Value Description 0 1 No transmit packet is ready. Software sets this bit after loading a data packet into the TX FIFO.
This bit is cleared automatically when a data packet has been transmitted. The EPn bit in the USBTXIS register is also set at this point. TXRDY is also automatically cleared prior to loading a second packet into a double-buffered FIFO.
1103
Register 44: USB Transmit Control and Status Endpoint 1 High (USBTXCSRH1), offset 0x113 Register 45: USB Transmit Control and Status Endpoint 2 High (USBTXCSRH2), offset 0x123 Register 46: USB Transmit Control and Status Endpoint 3 High (USBTXCSRH3), offset 0x133 Register 47: USB Transmit Control and Status Endpoint 4 High (USBTXCSRH4), offset 0x143 Register 48: USB Transmit Control and Status Endpoint 5 High (USBTXCSRH5), offset 0x153 Register 49: USB Transmit Control and Status Endpoint 6 High (USBTXCSRH6), offset 0x163 Register 50: USB Transmit Control and Status Endpoint 7 High (USBTXCSRH7), offset 0x173
USBTXCSRHn is an 8-bit register that provides additional control for transfers through the currently selected transmit endpoint.
USB Transmit Control and Status Endpoint n High (USBTXCSRHn)
7 AUTOSET Type Reset R/W 0 6 ISO R/W 0 5 MODE R/W 0 4 DMAEN R/W 0 3 FDT R/W 0 2 DMAMOD R/W 0 1 reserved RO 0 RO 0 0
Bit/Field 7
Name AUTOSET
Type R/W
Reset 0
Description Auto Set Value Description 0 1 The TXRDY bit must be set manually. Enables the TXRDY bit to be automatically set when data of the maximum packet size (value in USBTXMAXPn) is loaded into the transmit FIFO. If a packet of less than the maximum packet size is loaded, then the TXRDY bit must be set manually.
ISO
R/W
Isochronous Transfers Value Description 0 1 Enables the transmit endpoint for bulk or interrupt transfers. Enables the transmit endpoint for isochronous transfers.
April 25, 2012
Bit/Field 5
Name MODE
Type R/W
Reset 0
Description Mode Value Description 0 1 Note: Enables the endpoint direction as RX. Enables the endpoint direction as TX. This bit only has an effect where the same endpoint FIFO is used for both transmit and receive transactions.
DMAEN
R/W
DMA Request Enable Value Description 0 1 Note: Disables the DMA request for the transmit endpoint. Enables the DMA request for the transmit endpoint. 3 TX and 3 RX endpoints can be connected to the DMA module. If this bit is set for a particular endpoint, the DMAATX, DMABTX, or DMACTX field in the USB DMA Select (USBDMASEL) register must be programmed correspondingly.
FDT
R/W
Force Data Toggle Value Description 0 1 No effect. Forces the endpoint DT bit to switch and the data packet to be cleared from the FIFO, regardless of whether an ACK was received. This bit can be used by interrupt transmit endpoints that are used to communicate rate feedback for isochronous endpoints.
DMAMOD
R/W
DMA Request Mode Value Description 0 1 An interrupt is generated after every DMA packet transfer. An interrupt is generated only after the entire DMA transfer is complete. This bit must not be cleared either before or in the same cycle as the above DMAEN bit is cleared.
Note:
1:0
reserved
RO
1105
Register 51: USB Maximum Receive Data Endpoint 1 (USBRXMAXP1), offset 0x114 Register 52: USB Maximum Receive Data Endpoint 2 (USBRXMAXP2), offset 0x124 Register 53: USB Maximum Receive Data Endpoint 3 (USBRXMAXP3), offset 0x134 Register 54: USB Maximum Receive Data Endpoint 4 (USBRXMAXP4), offset 0x144 Register 55: USB Maximum Receive Data Endpoint 5 (USBRXMAXP5), offset 0x154 Register 56: USB Maximum Receive Data Endpoint 6 (USBRXMAXP6), offset 0x164 Register 57: USB Maximum Receive Data Endpoint 7 (USBRXMAXP7), offset 0x174
The USBRXMAXPn is a 16-bit register which defines the maximum amount of data that can be transferred through the selected receive endpoint in a single operation. Bits 10:0 define (in bytes) the maximum payload transmitted in a single transaction. The value set can be up to 1024 bytes but is subject to the constraints placed by the USB Specification on packet sizes for bulk, interrupt and isochronous transfers in full-speed operations. The total amount of data represented by the value written to this register must not exceed the FIFO size for the receive endpoint, and must not exceed half the FIFO size if double-buffering is required. Note: USBRXMAXPn must be set to an even number of bytes for proper interrupt generation in DMA Basic mode.
USB Maximum Receive Data Endpoint n (USBRXMAXPn)

15 14 13 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 12 11 10 9 8 7 6 5 MAXLOAD R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 4 3 2 1 0
Bit/Field 15:11
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Maximum Payload The maximum payload in bytes per transaction.
10:0
MAXLOAD
R/W
0x000
April 25, 2012
Register 58: USB Receive Control and Status Endpoint 1 Low (USBRXCSRL1), offset 0x116 Register 59: USB Receive Control and Status Endpoint 2 Low (USBRXCSRL2), offset 0x126 Register 60: USB Receive Control and Status Endpoint 3 Low (USBRXCSRL3), offset 0x136 Register 61: USB Receive Control and Status Endpoint 4 Low (USBRXCSRL4), offset 0x146 Register 62: USB Receive Control and Status Endpoint 5 Low (USBRXCSRL5), offset 0x156 Register 63: USB Receive Control and Status Endpoint 6 Low (USBRXCSRL6), offset 0x166 Register 64: USB Receive Control and Status Endpoint 7 Low (USBRXCSRL7), offset 0x176
USBRXCSRLn is an 8-bit register that provides control and status bits for transfers through the currently selected receive endpoint.
USB Receive Control and Status Endpoint n Low (USBRXCSRLn)
7 CLRDT Type Reset W1C 0 6 STALLED R/W 0 5 STALL R/W 0 4 3 2 OVER R/W 0 1 FULL RO 0 0 RXRDY R/W 0
FLUSH DATAERR R/W 0 RO 0
Bit/Field 7
Name CLRDT
Type W1C
Reset 0
Description Clear Data Toggle Writing a 1 to this bit clears the DT bit in the USBRXCSRHn register.
STALLED
R/W
Endpoint Stalled Value Description 0 1 A STALL handshake has not been transmitted. A STALL handshake has been transmitted.
Software must clear this bit. 5 STALL R/W 0 Send STALL Value Description 0 1 No effect. Issues a STALL handshake.
Software must clear this bit to terminate the STALL condition. Note: This bit has no effect where the endpoint is being used for isochronous transfers.
1107
Bit/Field 4
Name FLUSH
Type R/W
Reset 0
Description Flush FIFO Value Description 0 1 No effect. Flushes the next packet from the endpoint receive FIFO. The FIFO pointer is reset and the RXRDY bit is cleared.
The CPU writes a 1 to this bit to flush the next packet to be read from the endpoint receive FIFO. The FIFO pointer is reset and the RXRDY bit is cleared. Note that if the FIFO is double-buffered, FLUSH may have to be set twice to completely clear the FIFO.
Important:
3 DATAERR RO 0 Data Error
This bit should only be set when the RXRDY bit is set. At other times, it may cause data to be corrupted.
Value Description 0 1 Normal operation. Indicates that RXRDY is set and the data packet has a CRC or bit-stuff error.
This bit is cleared when RXRDY is cleared. Note: This bit is only valid when the endpoint is operating in Isochronous mode. In Bulk mode, it always returns zero.
OVER
R/W
Overrun Value Description 0 1 No overrun error. Indicates that an OUT packet cannot be loaded into the receive FIFO.
Software must clear this bit. Note: This bit is only valid when the endpoint is operating in Isochronous mode. In Bulk mode, it always returns zero.
FULL
RO
FIFO Full Value Description 0 1 The receive FIFO is not full. No more packets can be loaded into the receive FIFO.
April 25, 2012
Bit/Field 0
Name RXRDY
Type R/W
Reset 0
Description Receive Packet Ready Value Description 0 1 No data packet has been received. A data packet has been received. The EPn bit in the USBRXIS register is also set in this situation.
If the AUTOCLR bit in the USBRXCSRHn register is set, then the this bit is automatically cleared when a packet of USBRXMAXPn bytes has been unloaded from the receive FIFO. If the AUTOCLR bit is clear, or if packets of less than the maximum packet size are unloaded, then software must clear this bit manually when the packet has been unloaded from the receive FIFO.
1109
Register 65: USB Receive Control and Status Endpoint 1 High (USBRXCSRH1), offset 0x117 Register 66: USB Receive Control and Status Endpoint 2 High (USBRXCSRH2), offset 0x127 Register 67: USB Receive Control and Status Endpoint 3 High (USBRXCSRH3), offset 0x137 Register 68: USB Receive Control and Status Endpoint 4 High (USBRXCSRH4), offset 0x147 Register 69: USB Receive Control and Status Endpoint 5 High (USBRXCSRH5), offset 0x157 Register 70: USB Receive Control and Status Endpoint 6 High (USBRXCSRH6), offset 0x167 Register 71: USB Receive Control and Status Endpoint 7 High (USBRXCSRH7), offset 0x177
USBRXCSRHn is an 8-bit register that provides additional control and status bits for transfers through the currently selected receive endpoint.
USB Receive Control and Status Endpoint n High (USBRXCSRHn)
7 AUTOCL Type Reset R/W 0 6 ISO R/W 0 5 DMAEN R/W 0 4
DISNYET / PIDERR
3 DMAMOD R/W 0
1 reserved
R/W 0
RO 0
RO 0
RO 0
Bit/Field 7
Name AUTOCL
Type R/W
Reset 0
Description Auto Clear Value Description 0 1 No effect. Enables the RXRDY bit to be automatically cleared when a packet of USBRXMAXPn bytes has been unloaded from the receive FIFO. When packets of less than the maximum packet size are unloaded, RXRDY must be cleared manually. Care must be taken when using DMA to unload the receive FIFO as data is read from the receive FIFO in 4 byte chunks regardless of the value of the MAXLOAD field in the USBRXMAXPn register, see DMA Operation on page 1070.
ISO
R/W
Isochronous Transfers Value Description 0 1 Enables the receive endpoint for isochronous transfers. Enables the receive endpoint for bulk/interrupt transfers.
April 25, 2012
Bit/Field 5
Name DMAEN
Type R/W
Reset 0
Description DMA Request Enable Value Description 0 1 Note: Disables the DMA request for the receive endpoint. Enables the DMA request for the receive endpoint. 3 TX and 3 RX endpoints can be connected to the DMA module. If this bit is set for a particular endpoint, the DMAARX, DMABRX, or DMACRX field in the USB DMA Select (USBDMASEL) register must be programmed correspondingly.
DISNYET / PIDERR
R/W
Disable NYET / PID Error Value Description 0 1 No effect. For bulk or interrupt transactions: Disables the sending of NYET handshakes. When this bit is set, all successfully received packets are acknowledged, including at the point at which the FIFO becomes full. For isochronous transactions: Indicates a PID error in the received packet.
DMAMOD
R/W
DMA Request Mode Value Description 0 1 An interrupt is generated after every DMA packet transfer. An interrupt is generated only after the entire DMA transfer is complete. This bit must not be cleared either before or in the same cycle as the above DMAEN bit is cleared.
Note:
2:0
reserved
RO
0x0
1111
Register 72: USB Receive Byte Count Endpoint 1 (USBRXCOUNT1), offset 0x118 Register 73: USB Receive Byte Count Endpoint 2 (USBRXCOUNT2), offset 0x128 Register 74: USB Receive Byte Count Endpoint 3 (USBRXCOUNT3), offset 0x138 Register 75: USB Receive Byte Count Endpoint 4 (USBRXCOUNT4), offset 0x148 Register 76: USB Receive Byte Count Endpoint 5 (USBRXCOUNT5), offset 0x158 Register 77: USB Receive Byte Count Endpoint 6 (USBRXCOUNT6), offset 0x168 Register 78: USB Receive Byte Count Endpoint 7 (USBRXCOUNT7), offset 0x178
Note: The value returned changes as the FIFO is unloaded and is only valid while the RXRDY bit in the USBRXCSRLn register is set.
USBRXCOUNTn is a 16-bit read-only register that holds the number of data bytes in the packet currently in line to be read from the receive FIFO. If the packet is transmitted as multiple bulk packets, the number given is for the combined packet.
USB Receive Byte Count Endpoint n (USBRXCOUNTn)
15 14 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 13 12 11 10 9 8 7 6 COUNT RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 5 4 3 2 1 0
Bit/Field 15:13
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Receive Packet Count Indicates the number of bytes in the receive packet.
12:0
COUNT
RO
0x000
April 25, 2012
Register 79: USB Receive Double Packet Buffer Disable (USBRXDPKTBUFDIS), offset 0x340
USBRXDPKTBUFDIS is a 16-bit register that indicates which of the receive endpoints have disabled the double-packet buffer functionality (see the section called Double-Packet Buffering on page 1067).
USB Receive Double Packet Buffer Disable (USBRXDPKTBUFDIS)
reserved
RO 0
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EP7 RX Double-Packet Buffer Disable Value Description 0 1 Disables double-packet buffering. Enables double-packet buffering.
EP7
R/W
EP6
R/W
EP6 RX Double-Packet Buffer Disable Same description as EP7.
EP5
R/W
EP4
R/W
EP3
R/W
EP2
R/W
EP1
R/W
reserved
RO
1113
Register 80: USB Transmit Double Packet Buffer Disable (USBTXDPKTBUFDIS), offset 0x342
USBTXDPKTBUFDIS is a 16-bit register that indicates which of the transmit endpoints have disabled the double-packet buffer functionality (see the section called Double-Packet Buffering on page 1066).
USB Transmit Double Packet Buffer Disable (USBTXDPKTBUFDIS)
reserved
RO 0
Bit/Field 15:8
Name reserved
Type RO
Reset 0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. EP7 TX Double-Packet Buffer Disable Value Description 0 1 Disables double-packet buffering. Enables double-packet buffering.
EP7
R/W
EP6
R/W
EP6 TX Double-Packet Buffer Disable Same description as EP7.
EP5
R/W
EP4
R/W
EP3
R/W
EP2
R/W
EP1
R/W
reserved
RO
April 25, 2012
Register 81: USB Device RESUME Raw Interrupt Status (USBDRRIS), offset 0x410
The USBDRRIS 32-bit register is the raw interrupt status register. On a read, this register gives the current raw status value of the corresponding interrupt prior to masking. A write has no effect.
USB Device RESUME Raw Interrupt Status (USBDRRIS)
Base 0x4005.0000 Offset 0x410 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 RESUME RO 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RESUME Interrupt Status Value Description 1 0 A RESUME status has been detected. An interrupt has not occurred.
RESUME
RO
This bit is cleared by writing a 1 to the RESUME bit in the USBDRISC register.
1115
Register 82: USB Device RESUME Interrupt Mask (USBDRIM), offset 0x414
The USBDRIM 32-bit register is the masked interrupt status register. On a read, this register gives the current value of the mask on the corresponding interrupt. Setting a bit sets the mask, preventing the interrupt from being signaled to the interrupt controller. Clearing a bit clears the corresponding mask, enabling the interrupt to be sent to the interrupt controller.
USB Device RESUME Interrupt Mask (USBDRIM)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 RESUME R/W 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RESUME Interrupt Mask Value Description 1 The raw interrupt signal from a detected RESUME is sent to the interrupt controller. This bit should only be set when a SUSPEND has been detected (the SUSPEND bit in the USBIS register is set). A detected RESUME does not affect the interrupt status.
RESUME
R/W
April 25, 2012
Register 83: USB Device RESUME Interrupt Status and Clear (USBDRISC), offset 0x418
The USBDRISC 32-bit register is the interrupt clear register. On a write of 1, the corresponding interrupt is cleared. A write of 0 has no effect.
USB Device RESUME Interrupt Status and Clear (USBDRISC)
Base 0x4005.0000 Offset 0x418 Type W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 RO 0 8 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 RO 0 0 RESUME R/W1C 0
Bit/Field 31:1
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. RESUME Interrupt Status and Clear Value Description 1 0 The RESUME bits in the USBDRRIS and USBDRCIM registers are set, providing an interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
RESUME
R/W1C
This bit is cleared by writing a 1. Clearing this bit also clears the RESUME bit in the USBDRCRIS register.
1117
Register 84: USB DMA Select (USBDMASEL), offset 0x450

This 32-bit register specifies which endpoints are mapped to the 6 allocated DMA channels, see Table 9-1 on page 570 for more information on channel assignments.
USB DMA Select (USBDMASEL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 DMABRX R/W 0 R/W 0 R/W 0 R/W 1 R/W 0 R/W 0 RO 0 9 RO 0 8 R/W 0 7
DMACTX R/W 0 6 DMAATX R/W 0 R/W 0 R/W 1 R/W 0 R/W 1 5 R/W 1 4 R/W 0 3
DMACRX R/W 0 2 DMAARX R/W 0 R/W 0 R/W 1 R/W 1 1 R/W 1 0
DMABTX Type Reset R/W 0 R/W 0 R/W 1
Bit/Field 31:24
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. DMA C TX Select Specifies the TX mapping of the third USB endpoint on DMA channel 5 (primary assignment). Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Description reserved Endpoint 1 TX Endpoint 2 TX Endpoint 3 TX Endpoint 4 TX Endpoint 5 TX Endpoint 6 TX Endpoint 7 TX
23:20
DMACTX
R/W
0x3
0x8 - 0xF reserved
April 25, 2012
Bit/Field 19:16
Name DMACRX
Type R/W
Reset 0x3
Description DMA C RX Select Specifies the RX and TX mapping of the third USB endpoint on DMA channel 4 (primary assignment). Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 Description reserved Endpoint 1 RX Endpoint 2 RX Endpoint 3 RX Endpoint 4 RX Endpoint 5 RX Endpoint 6 RX Endpoint 7 RX
0x8 - 0xF reserved
15:12
DMABTX
R/W
0x2
DMA B TX Select Specifies the TX mapping of the second USB endpoint on DMA channel 3 (primary assignment). Same bit definitions as the DMACTX field.
11:8
DMABRX
R/W
0x2
DMA B RX Select Specifies the RX mapping of the second USB endpoint on DMA channel 2 (primary assignment). Same bit definitions as the DMACRX field.
7:4
DMAATX
R/W
0x1
DMA A TX Select Specifies the TX mapping of the first USB endpoint on DMA channel 1 (primary assignment). Same bit definitions as the DMACTX field.
3:0
DMAARX
R/W
0x1
DMA A RX Select Specifies the RX mapping of the first USB endpoint on DMA channel 0 (primary assignment). Same bit definitions as the DMACRX field.
1119
Register 85: USB Peripheral Properties (USBPP), offset 0xFC0

The USBPP register provides information regarding the properties of the USB module.
USB Peripheral Properties (USBPP)
Base 0x4005.0000 Offset 0xFC0 Type RO, reset 0x0000.1050
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 ECNT Type Reset RO 0 RO 0 RO 0 RO 1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 11 RO 0 10 RO 0 9 RO 0 8 RO 0 7 USB RO 1 RO 0 6 RO 0 5

reserved
RO 0 4 PHY RO 1
RO 0 3
RO 0 2 TYPE
RO 0 1
RO 0 0
RO 0
RO 0
RO 0
RO 0
RO 0
Bit/Field 31:16
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Endpoint Count This field defines the number of endpoints provided.
15:8
ECNT
RO
0x10
7:6
USB
RO
0x1
USB Capability Value Description 0x0 0x1 0x2 0x3 NA USB is not present. DEVICE Device Only HOST Device or Host OTG Device, Host, or OTG
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. PHY Present Value Description 1 0 A PHY is integrated with the USB MAC. A PHY is not integrated with the USB MAC.
PHY
RO
0x1
3:0
TYPE
RO
0x0
Controller Type Value 0x0 Description The first-generation USB controller.
0x1 - 0xF Reserved
April 25, 2012
19
Analog Comparators
An analog comparator is a peripheral that compares two analog voltages and provides a logical output that signals the comparison result. Note: Not all comparators have the option to drive an output pin. See Signal Description on page 1122 for more information.
The comparator can provide its output to a device pin, acting as a replacement for an analog comparator on the board. In addition, the comparator can signal the application via interrupts or trigger the start of a sample sequence in the ADC. The interrupt generation and ADC triggering logic is separate and independent. This flexibility means, for example, that an interrupt can be generated on a rising edge and the ADC triggered on a falling edge. The Stellaris LM4F120H5QR microcontroller provides two independent integrated analog comparators with the following functions: Compare external pin input to external pin input or to internal programmable voltage reference Compare a test voltage against any one of the following voltages: An individual external reference voltage A shared single external reference voltage A shared internal reference voltage
1121
Analog Comparators
19.1
Block Diagram
Figure 19-1. Analog Comparator Module Block Diagram
C2C2+ -ve input +ve input Comparator 2 output C2o trigger
+ve input (alternate) ACCTL2 trigger ACSTAT2 reference input C1C1+ -ve input +ve input interrupt
Comparator 1 output trigger C1o trigger
+ve input (alternate) ACCTL1 ACSTAT1 interrupt reference input C0C0+ -ve input +ve input
Comparator 0 output trigger interrupt C0o trigger
+ve input (alternate) ACCTL0 ACSTAT0 reference input Voltage Ref Internal Bus ACREFCTL
Interrupt Control ACRIS Interrupt ACMIS ACINTEN
Module Status ACMPPP
19.2
Signal Description
The following table lists the external signals of the Analog Comparators and describes the function of each. The Analog Comparator output signals are alternate functions for some GPIO signals and default to be GPIO signals at reset. The column in the table below titled "Pin Mux/Pin Assignment" lists the possible GPIO pin placements for the Analog Comparator signals. The AFSEL bit in the GPIO Alternate Function Select (GPIOAFSEL) register (page 653) should be set to choose the Analog Comparator function. The number in parentheses is the encoding that must be programmed into the PMCn field in the GPIO Port Control (GPIOPCTL) register (page 670) to assign the Analog Comparator signal to the specified GPIO port pin. The positive and negative input signals are configured by clearing the DEN bit in the GPIO Digital Enable (GPIODEN) register. For more information on configuring GPIOs, see General-Purpose Input/Outputs (GPIOs) on page 632.
Table 19-1. Analog Comparators Signals (64LQFP)

Pin Name C0+ C0C0o C1+ Pin Number Pin Mux / Pin Assignment 14 13 28 15 PC6 PC7 PF0 (9) PC5 Pin Type I I O I Buffer Type Analog Analog TTL Analog
a
Description Analog comparator 0 positive input. Analog comparator 0 negative input. Analog comparator 0 output. Analog comparator 1 positive input.
April 25, 2012
Table 19-1. Analog Comparators Signals (64LQFP) (continued)

Pin Name C1C1o Pin Number Pin Mux / Pin Assignment 16 29 PC4 PF1 (9) Pin Type I O Buffer Type Analog TTL
a
Description Analog comparator 1 negative input. Analog comparator 1 output.
19.3
The comparator compares the VIN- and VIN+ inputs to produce an output, VOUT. VIN- < VIN+, VOUT = 1 VIN- > VIN+, VOUT = 0 As shown in Figure 19-2 on page 1123, the input source for VIN- is an external input, Cn-, where n is the analog comparator number. In addition to an external input, Cn+, input sources for VIN+ can be the C0+ or an internal reference, VIREF. Figure 19-2. Structure of Comparator Unit
- ve input + ve input + ve input (alternate) reference input 0 1 2 CINV IntGen TrigGen ACCTL ACSTAT output
internal bus
A comparator is configured through two status/control registers, Analog Comparator Control (ACCTL) and Analog Comparator Status (ACSTAT). The internal reference is configured through one control register, Analog Comparator Reference Voltage Control (ACREFCTL). Interrupt status and control are configured through three registers, Analog Comparator Masked Interrupt Status (ACMIS), Analog Comparator Raw Interrupt Status (ACRIS), and Analog Comparator Interrupt Enable (ACINTEN). Typically, the comparator output is used internally to generate an interrupt as controlled by the ISEN bit in the ACCTL register. The output may also be used to drive one of the external pins (C0o, C1o, or C2o), or generate an analog-to-digital converter (ADC) trigger. Important: The ASRCP bits in the ACCTL register must be set before using the analog comparators.
19.3.1
Internal Reference Programming

The structure of the internal reference is shown in Figure 19-3 on page 1124. The internal reference is controlled by a single configuration register (ACREFCTL).
trigger interrupt
1123
Analog Comparators
Figure 19-3. Comparator Internal Reference Structure

N*R N*R
0xF
0xE
0x1
0x0
Note:
In the figure above, N*R represents a multiple of the R value that produces the results specified in Table 19-2 on page 1124.
The internal reference can be programmed in one of two modes (low range or high range) depending on the RNG bit in the ACREFCTL register. When RNG is clear, the internal reference is in high-range mode, and when RNG is set the internal reference is in low-range mode. In each range, the internal reference, VIREF, has 16 pre-programmed thresholds or step values. The threshold to be used to compare the external input voltage against is selected using the VREF field in the ACREFCTL register. In the high-range mode, the VIREF threshold voltages start at the ideal high-range starting voltage of VDDA/4.2 and increase in ideal constant voltage steps of VDDA/29.4. In the low-range mode, the VIREF threshold voltages start at 0 V and increase in ideal constant voltage steps of VDDA/22.12. The ideal VIREF step voltages for each mode and their dependence on the RNG and VREF fields are summarized in Table 19-2. Table 19-2. Internal Reference Voltage and ACREFCTL Field Values
ACREFCTL Register EN Bit Value EN=0 RNG Bit Value RNG=X RNG=0 Output Reference Voltage Based on VREF Field Value 0 V (GND) for any value of VREF. It is recommended that RNG=1 and VREF=0 to minimize noise on the reference ground. VIREF High Range: 16 voltage threshold values indexed by VREF = 0x0 .. 0xF Ideal starting voltage (VREF=0): VDDA / 4.2 Ideal step size: VDDA/ 29.4 Ideal VIREF threshold values: VIREF (VREF) = VDDA / 4.2 + VREF * (VDDA/ 29.4), for VREF = 0x0 .. 0xF EN=1 RNG=1 For minimum and maximum VIREF threshold values, see Table 19-3 on page 1125. VIREF Low Range: 16 voltage threshold values indexed by VREF = 0x0 .. 0xF Ideal starting voltage (VREF=0): 0 V Ideal step size: VDDA/ 22.12 Ideal VIREF threshold values: VIREF (VREF) = VREF * (VDDA/ 22.12), for VREF = 0x0 .. 0xF For minimum and maximum VIREF threshold values, see Table 19-4 on page 1125.
Note that the values shown in Table 19-2 are the ideal values of the VIREF thresholds. These values actually vary between minimum and maximum values for each threshold step, depending on process and temperature. The minimum and maximum values for each step are given by:
April 25, 2012
VIREF(VREF) [Min] = Ideal VIREF(VREF) (Ideal Step size 2 mV) / 2 VIREF(VREF) [Max] = Ideal VIREF(VREF) + (Ideal Step size 2 mV) / 2 Examples of minimum and maximum VIREF values for VDDA = 3.3V for high and low ranges, are shown inTable 19-3 and Table 19-4. Note that these examples are only valid for VDDA = 3.3V; values scale up and down with VDDA. Table 19-3. Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 0
VREF Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF VIREF Min 0.731 0.843 0.955 1.067 1.180 1.292 1.404 1.516 1.629 1.741 1.853 1.965 2.078 2.190 2.302 2.414 Ideal VIREF 0.786 0.898 1.010 1.122 1.235 1.347 1.459 1.571 1.684 1.796 1.908 2.020 2.133 2.245 2.357 2.469 VIREF Max 0.841 0.953 1.065 1.178 1.290 1.402 1.514 1.627 1.739 1.851 1.963 2.076 2.188 2.300 2.412 2.525 Unit V V V V V V V V V V V V V V V V
Table 19-4. Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 1
VREF Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD VIREF Min 0.000 0.076 0.225 0.374 0.523 0.672 0.822 0.971 1.120 1.269 1.418 1.567 1.717 1.866 Ideal VIREF 0.000 0.149 0.298 0.448 0.597 0.746 0.895 1.044 1.193 1.343 1.492 1.641 1.790 1.939 VIREF Max 0.074 0.223 0.372 0.521 0.670 0.820 0.969 1.118 1.267 1.416 1.565 1.715 1.864 2.013 Unit V V V V V V V V V V V V V V
1125
Analog Comparators
Table 19-4. Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 1 (continued)
VREF Value 0xE 0xF VIREF Min 2.015 2.164 Ideal VIREF 2.089 2.238 VIREF Max 2.162 2.311 Unit V V
19.4

The following example shows how to configure an analog comparator to read back its output value from an internal register. 1. Enable the analog comparator clock by writing a value of 0x0000.0001 to the RCGCACMP register in the System Control module (see page 325). 2. Enable the clock to the appropriate GPIO modules via the RCGCGPIO register (see page 312). To find out which GPIO ports to enable, refer to Table 21-5 on page 1152. 3. In the GPIO module, enable the GPIO port/pin associated with the input signals as GPIO inputs. To determine which GPIO to configure, see Table 21-4 on page 1148. 4. Configure the PMCn fields in the GPIOPCTL register to assign the analog comparator output signals to the appropriate pins (see page 670 and Table 21-5 on page 1152). 5. Configure the internal voltage reference to 1.65 V by writing the ACREFCTL register with the value 0x0000.030C. 6. Configure the comparator to use the internal voltage reference and to not invert the output by writing the ACCTLn register with the value of 0x0000.040C. 7. Delay for 10 s. 8. Read the comparator output value by reading the ACSTATn registers OVAL value. Change the level of the comparator negative input signal C- to see the OVAL value change.
19.5
Register Map
Table 19-5 on page 1126 lists the comparator registers. The offset listed is a hexadecimal increment to the registers address, relative to the Analog Comparator base address of 0x4003.C000. Note that the analog comparator clock must be enabled before the registers can be programmed (see page 325). There must be a delay of 3 system clocks after the analog comparator module clock is enabled before any analog comparator module registers are accessed.
Table 19-5. Analog Comparators Register Map

Offset 0x000 0x004 0x008 0x010 Name ACMIS ACRIS ACINTEN ACREFCTL Type R/W1C RO R/W R/W Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 Description Analog Comparator Masked Interrupt Status Analog Comparator Raw Interrupt Status Analog Comparator Interrupt Enable Analog Comparator Reference Voltage Control See page 1128 1129 1130 1131
April 25, 2012
Table 19-5. Analog Comparators Register Map (continued)

Offset 0x020 0x024 0x040 0x044 0xFC0 Name ACSTAT0 ACCTL0 ACSTAT1 ACCTL1 ACMPPP Type RO R/W RO R/W RO Reset 0x0000.0000 0x0000.0000 0x0000.0000 0x0000.0000 0x0003.0003 Description Analog Comparator Status 0 Analog Comparator Control 0 Analog Comparator Status 1 Analog Comparator Control 1 Analog Comparator Peripheral Properties See page 1132 1133 1132 1133 1135
19.6
The remainder of this section lists and describes the Analog Comparator registers, in numerical order by address offset.
1127
Analog Comparators
Register 1: Analog Comparator Masked Interrupt Status (ACMIS), offset 0x000

This register provides a summary of the interrupt status (masked) of the comparators.
Analog Comparator Masked Interrupt Status (ACMIS)
Base 0x4003.C000 Offset 0x000 Type R/W1C, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 IN1 R/W1C 0 RO 0 0 IN0 R/W1C 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator 1 Masked Interrupt Status Value Description 1 0 The IN1 bits in the ACRIS register and the ACINTEN registers are set, providing an interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
IN1
R/W1C
This bit is cleared by writing a 1. Clearing this bit also clears the IN1 bit in the ACRIS register. 0 IN0 R/W1C 0 Comparator 0 Masked Interrupt Status Value Description 1 0 The IN0 bits in the ACRIS register and the ACINTEN registers are set, providing an interrupt to the interrupt controller. No interrupt has occurred or the interrupt is masked.
This bit is cleared by writing a 1. Clearing this bit also clears the IN0 bit in the ACRIS register.
April 25, 2012
Register 2: Analog Comparator Raw Interrupt Status (ACRIS), offset 0x004

This register provides a summary of the interrupt status (raw) of the comparators. The bits in this register must be enabled to generate interrupts using the ACINTEN register.
Analog Comparator Raw Interrupt Status (ACRIS)
Base 0x4003.C000 Offset 0x004 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 IN1 RO 0 RO 0 0 IN0 RO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator 1 Interrupt Status Value Description 1 0 Comparator 1 has generated an interruptfor an event as configured by the ISEN bit in the ACCTL1 register. An interrupt has not occurred.
IN1
RO
This bit is cleared by writing a 1 to the IN1 bit in the ACMIS register. 0 IN0 RO 0 Comparator 0 Interrupt Status Value Description 1 0 Comparator 0 has generated an interrupt for an event as configured by the ISEN bit in the ACCTL0 register. An interrupt has not occurred.
This bit is cleared by writing a 1 to the IN0 bit in the ACMIS register.
1129
Analog Comparators
Register 3: Analog Comparator Interrupt Enable (ACINTEN), offset 0x008

This register provides the interrupt enable for the comparators.
Analog Comparator Interrupt Enable (ACINTEN)
Base 0x4003.C000 Offset 0x008 Type R/W, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 IN1 R/W 0 RO 0 0 IN0 R/W 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x00
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator 1 Interrupt Enable Value Description 1 0 The raw interrupt signal comparator 1 is sent to the interrupt controller. A comparator 1 interrupt does not affect the interrupt status.
IN1
R/W
IN0
R/W
Comparator 0 Interrupt Enable Value Description 1 0 The raw interrupt signal comparator 0 is sent to the interrupt controller. A comparator 0 interrupt does not affect the interrupt status.
April 25, 2012
Register 4: Analog Comparator Reference Voltage Control (ACREFCTL), offset 0x010

This register specifies whether the resistor ladder is powered on as well as the range and tap.
Analog Comparator Reference Voltage Control (ACREFCTL)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 EN RO 0 RO 0 R/W 0 RO 0 8 RNG R/W 0 RO 0 RO 0 7 RO 0 6 reserved RO 0 RO 0 RO 0 R/W 0 R/W 0 RO 0 5 RO 0 4 RO 0 3 RO 0 2 VREF R/W 0 R/W 0 RO 0 1 RO 0 0
Bit/Field 31:10
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Resistor Ladder Enable Value Description 0 1 The resistor ladder is unpowered. Powers on the resistor ladder. The resistor ladder is connected to VDDA.
EN
R/W
This bit is cleared at reset so that the internal reference consumes the least amount of power if it is not used. 8 RNG R/W 0 Resistor Ladder Range Value Description 0 1 The ideal step size for the internal reference is VDDA / 29.4. The ideal step size for the internal reference is VDDA / 22.12.
7:4
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Resistor Ladder Voltage Ref The VREF bit field specifies the resistor ladder tap that is passed through an analog multiplexer. The voltage corresponding to the tap position is the internal reference voltage available for comparison. See Table 19-2 on page 1124 for some output reference voltage examples.
3:0
VREF
R/W
0x0
1131
Analog Comparators
Register 5: Analog Comparator Status 0 (ACSTAT0), offset 0x020 Register 6: Analog Comparator Status 1 (ACSTAT1), offset 0x040
These registers specify the current output value of the comparator.
Analog Comparator Status n (ACSTATn)
Base 0x4003.C000 Offset 0x020 Type RO, reset 0x0000.0000
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8 RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 0 1 OVAL RO 0 RO 0 0

reserved
RO 0
Bit/Field 31:2
Name reserved
Type RO
Reset 0x0000.000
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator Output Value Value Description 0 1 VIN- > VIN+ VIN- < VIN+
OVAL
RO
VIN - is the voltage on the Cn- pin. VIN+ is the voltage on the Cn+ pin, the C0+ pin, or the internal voltage reference (VIREF) as defined by the ASRCP bit in the ACCTL register. 0 reserved RO 0 Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation.
April 25, 2012
Register 7: Analog Comparator Control 0 (ACCTL0), offset 0x024 Register 8: Analog Comparator Control 1 (ACCTL1), offset 0x044
These registers configure the comparators input and output.
Analog Comparator Control n (ACCTLn)
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 TOEN RO 0 R/W 0 RO 0 10 ASRCP R/W 0 R/W 0 RO 0 9 RO 0 8

reserved
RO 0 7 TSLVAL R/W 0
RO 0 6 TSEN R/W 0
RO 0 5
RO 0 4 ISLVAL
RO 0 3 ISEN R/W 0
RO 0 2
RO 0 1 CINV
RO 0 0
reserved
RO 0
R/W 0
R/W 0
R/W 0
R/W 0
RO 0
Bit/Field 31:12
Name reserved
Type RO
Reset 0x0000.0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Trigger Output Enable Value Description 0 1 ADC events are suppressed and not sent to the ADC. ADC events are sent to the ADC.
11
TOEN
R/W
10:9
ASRCP
R/W
0x0
Analog Source Positive The ASRCP field specifies the source of input voltage to the VIN+ terminal of the comparator. The encodings for this field are as follows: Value Description 0x0 0x1 0x2 0x3 Pin value of Cn+ Pin value of C0+ Internal voltage reference (VIREF) Reserved
reserved
RO
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Trigger Sense Level Value Value Description 0 1 An ADC event is generated if the comparator output is Low. An ADC event is generated if the comparator output is High.
TSLVAL
R/W
1133
Analog Comparators
Bit/Field 6:5
Name TSEN
Type R/W
Reset 0x0
Description Trigger Sense The TSEN field specifies the sense of the comparator output that generates an ADC event. The sense conditioning is as follows: Value Description 0x0 0x1 0x2 0x3 Level sense, see TSLVAL Falling edge Rising edge Either edge
ISLVAL
R/W
Interrupt Sense Level Value Value Description 0 1 An interrupt is generated if the comparator output is Low. An interrupt is generated if the comparator output is High.
3:2
ISEN
R/W
0x0
Interrupt Sense The ISEN field specifies the sense of the comparator output that generates an interrupt. The sense conditioning is as follows: Value Description 0x0 0x1 0x2 0x3 Level sense, see ISLVAL Falling edge Rising edge Either edge
CINV
R/W
Comparator Output Invert Value Description 0 1 The output of the comparator is unchanged. The output of the comparator is inverted prior to being processed by hardware.
reserved
RO
April 25, 2012
Register 9: Analog Comparator Peripheral Properties (ACMPPP), offset 0xFC0

The ACMPPP register provides information regarding the properties of the analog comparator module.
Analog Comparator Peripheral Properties (ACMPPP)
Base 0x4003.C000 Offset 0xFC0 Type RO, reset 0x0003.0003
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 C1O RO 0 7 RO 0 6 RO 0 5 RO 0 4 RO 0 3 RO 0 2 RO 1 1 CMP1 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 1 16 C0O RO 1 0 CMP0 RO 1
reserved Type Reset RO 0 15 RO 0 14 RO 0 13 RO 0 12 RO 0 11 RO 0 10 RO 0 9 reserved Type Reset RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 RO 0 8
Bit/Field 31:18
Name reserved
Type RO
Reset 0x0
Description Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator Output 1 Present Value Description 1 0 Comparator output 1 is present. Comparator output 1 is not present.
17
C1O
RO
0x1
16
C0O
RO
0x1
Comparator Output 0 Present Value Description 1 0 Comparator output 0 is present. Comparator output 0 is not present.
15:2
reserved
RO
0x0
Software should not rely on the value of a reserved bit. To provide compatibility with future products, the value of a reserved bit should be preserved across a read-modify-write operation. Comparator 1 Present Value Description 1 0 Comparator 1 is present. Comparator 1 is not present.
CMP1
RO
0x1
CMP0
RO
0x1
Comparator 0 Present Value Description 1 0 Comparator 0 is present. Comparator 0 is not present.
1135
Pin Diagram
20
Pin Diagram
The LM4F120H5QR microcontroller pin diagram is shown below. Each GPIO signal is identified by its GPIO port unless it defaults to an alternate function on reset. In this case, the GPIO port name is followed by the default alternate function. To see a complete list of possible functions for each pin, see Table 21-5 on page 1152.
Figure 20-1. 64-Pin LQFP Package Pin Diagram
April 25, 2012
21
Signal Tables
The following tables list the signals available for each pin. Signals are configured as GPIOs on reset, except for those noted below. Use the GPIOAMSEL register (see page 669) to select analog mode. For a GPIO pin to be used for an alternate digital function, the corresponding bit in the GPIOAFSEL register (see page 653) must be set. Further pin muxing options are provided through the PMCx bit field in the GPIOPCTL register (see page 670), which selects one of several available peripheral functions for that GPIO. Important: All GPIO pins are configured as GPIOs by default with the exception of the pins shown in the table below. A Power-On-Reset (POR) or asserting RST puts the pins back to their default state. Table 21-1. GPIO Pins With Default Alternate Functions
GPIO Pin PA[1:0] PA[5:2] PB[3:2] PC[3:0] Default State UART0 SSI0 I2C0 JTAG/SWD GPIOAFSEL Bit 0 0 0 1 GPIOPCTL PMCx Bit Field 0x1 0x1 0x1 0x3
Table 21-2 on page 1138 shows the pin-to-signal-name mapping, including functional characteristics of the signals. Each possible alternate analog and digital function is listed for each pin. Table 21-3 on page 1143 lists the signals in alphabetical order by signal name. If it is possible for a signal to be on multiple pins, each possible pin assignment is listed. The "Pin Mux" column indicates the GPIO and the encoding needed in the PMCx bit field in the GPIOPCTL register. Table 21-4 on page 1148 groups the signals by functionality, except for GPIOs. If it is possible for a signal to be on multiple pins, each possible pin assignment is listed. Table 21-5 on page 1152 lists the GPIO pins and their analog and digital alternate functions. The AINx analog signals are not 5-V tolerant and go through an isolation circuit before reaching their circuitry. These signals are configured by clearing the corresponding DEN bit in the GPIO Digital Enable (GPIODEN) register and setting the corresponding AMSEL bit in the GPIO Analog Mode Select (GPIOAMSEL) register. Other analog signals are 5-V tolerant and are connected directly to their circuitry (C0-, C0+, C1-, C1+). These signals are configured by clearing the DEN bit in the GPIO Digital Enable (GPIODEN) register. The digital signals are enabled by setting the appropriate bit in the GPIO Alternate Function Select (GPIOAFSEL) and GPIODEN registers and configuring the PMCx bit field in the GPIO Port Control (GPIOPCTL) register to the numeric enoding shown in the table below. Table entries that are shaded gray are the default values for the corresponding GPIO pin. Table 21-6 on page 1154 lists the signals based on number of possible pin assignments. This table can be used to plan how to configure the pins for a particular functionality. Application Note AN01274 Configuring Stellaris Microcontrollers with Pin Multiplexing provides an overview of the pin muxing implementation, an explanation of how a system designer defines a pin configuration, and examples of the pin configuration process. Note: All digital inputs are Schmitt triggered.
1137
Signal Tables
Table 21-2. Signals by Pin Number

Pin Number Pin Name PB6 1 SSI2Rx T0CCP0 VDDA 2 Pin Type I/O I I/O Buffer Type TTL TTL TTL Power
a
Description GPIO port B bit 6. SSI module 2 receive 16/32-Bit Timer 0 Capture/Compare/PWM 0. The positive supply for the analog circuits (ADC, Analog Comparators, etc.). These are separated from VDD to minimize the electrical noise contained on VDD from affecting the analog functions. VDDA pins must be supplied with a voltage that meets the specification in Table 23-2 on page 1159, regardless of system implementation. The ground reference for the analog circuits (ADC, Analog Comparators, etc.). These are separated from GND to minimize the electrical noise contained on VDD from affecting the analog functions. GPIO port B bit 7. SSI module 2 transmit 16/32-Bit Timer 0 Capture/Compare/PWM 1. GPIO port F bit 4. 16/32-Bit Timer 2 Capture/Compare/PWM 0. GPIO port E bit 3. Analog-to-digital converter input 0. GPIO port E bit 2. Analog-to-digital converter input 1. GPIO port E bit 1. Analog-to-digital converter input 2. UART module 7 transmit. GPIO port E bit 0. Analog-to-digital converter input 3. UART module 7 receive. GPIO port D bit 7. Non-maskable interrupt. UART module 2 transmit. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 1. Positive supply for I/O and some logic. Ground reference for logic and I/O pins. GPIO port C bit 7. Analog comparator 0 negative input. UART module 3 transmit. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 1. GPIO port C bit 6. Analog comparator 0 positive input. UART module 3 receive. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 0.
GNDA 3
Power
PB7 4 SSI2Tx T0CCP1 PF4 5 T2CCP0 PE3 6 AIN0 PE2 7 AIN1 PE1 8 AIN2 U7Tx PE0 9 AIN3 U7Rx PD7 NMI 10 U2Tx WT5CCP1 11 12 VDD GND PC7 C013 U3Tx WT1CCP1 PC6 C0+ 14 U3Rx WT1CCP0
I/O O I/O I/O I/O I/O I I/O I I/O I O I/O I I I/O I O I/O I/O I O I/O I/O I I I/O
TTL TTL TTL TTL TTL TTL Analog TTL Analog TTL Analog TTL TTL Analog TTL TTL TTL TTL TTL Power Power TTL Analog TTL TTL TTL Analog TTL TTL
April 25, 2012
Table 21-2. Signals by Pin Number (continued)

Pin Number Pin Name PC5 C1+ U1CTS 15 U1Tx U4Tx WT0CCP1 PC4 C1U1RTS 16 U1Rx U4Rx WT0CCP0 PA0 17 U0Rx PA1 18 U0Tx PA2 19 SSI0Clk PA3 20 SSI0Fss PA4 21 SSI0Rx PA5 22 SSI0Tx PA6 23 I2C1SCL PA7 24 I2C1SDA VDDC 25 Pin Type I/O I I O O I/O I/O I O I I I/O I/O I I/O O I/O I/O I/O I/O I/O I I/O O I/O I/O I/O I/O Buffer Type TTL Analog TTL TTL TTL TTL TTL Analog TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL OD TTL OD Power
a
Description GPIO port C bit 5. Analog comparator 1 positive input. UART module 1 Clear To Send modem flow control input signal. UART module 1 transmit. UART module 4 transmit. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 1. GPIO port C bit 4. Analog comparator 1 negative input. UART module 1 Request to Send modem flow control output line. UART module 1 receive. UART module 4 receive. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 0. GPIO port A bit 0. UART module 0 receive. GPIO port A bit 1. UART module 0 transmit. GPIO port A bit 2. SSI module 0 clock GPIO port A bit 3. SSI module 0 frame signal GPIO port A bit 4. SSI module 0 receive GPIO port A bit 5. SSI module 0 transmit GPIO port A bit 6. I2C module 1 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. GPIO port A bit 7. I2C module 1 data. Positive supply for most of the logic function, including the processor core and most peripherals. The voltage on this pin is 1.2 V and is supplied by the on-chip LDO. The VDDC pins should only be connected to each other and an external capacitor as specified in Table 23-8 on page 1164 . Positive supply for I/O and some logic. Ground reference for logic and I/O pins. GPIO port F bit 0. Analog comparator 0 output. CAN module 0 receive. Non-maskable interrupt. SSI module 1 receive 16/32-Bit Timer 0 Capture/Compare/PWM 0. UART module 1 Request to Send modem flow control output line.
26 27
VDD GND PF0 C0o CAN0Rx
I/O O I I I I/O O
Power Power TTL TTL TTL TTL TTL TTL TTL
28
NMI SSI1Rx T0CCP0 U1RTS
1139
Signal Tables

Pin Number Pin Name PF1 C1o SSI1Tx 29 T0CCP1 TRD1 U1CTS PF2 SSI1Clk 30 T1CCP0 TRD0 PF3 CAN0Tx 31 SSI1Fss T1CCP1 TRCLK 32 33 34 GNDX 35 Power WAKE HIB XOSC0 Pin Type I/O O O I/O O I I/O I/O I/O O I/O O I/O I/O O I O I Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL Analog
a
Description GPIO port F bit 1. Analog comparator 1 output. SSI module 1 transmit 16/32-Bit Timer 0 Capture/Compare/PWM 1. Trace data 1. UART module 1 Clear To Send modem flow control input signal. GPIO port F bit 2. SSI module 1 clock 16/32-Bit Timer 1 Capture/Compare/PWM 0. Trace data 0. GPIO port F bit 3. CAN module 0 transmit. SSI module 1 frame signal 16/32-Bit Timer 1 Capture/Compare/PWM 1. Trace clock. An external input that brings the processor out of Hibernate mode when asserted. An output that indicates the processor is in Hibernate mode. Hibernation module oscillator crystal input or an external clock reference input. Note that this is either a 32.768-kHz crystal or a 32.768-kHz oscillator for the Hibernation module RTC. GND for the Hibernation oscillator. When using a crystal clock source, this pin should only be connected to the crystal load capacitors to improve oscillator immunity to system noise. When using an external oscillator, this pin should be connected to GND. Hibernation module oscillator crystal output. Leave unconnected when using a single-ended clock source. Power source for the Hibernation module. It is normally connected to the positive terminal of a battery and serves as the battery backup/Hibernation module power-source supply. System reset input. Ground reference for logic and I/O pins. Main oscillator crystal input or an external clock reference input. Main oscillator crystal output. Leave unconnected when using a single-ended clock source. Positive supply for I/O and some logic. GPIO port D bit 4. UART module 6 receive. Bidirectional differential data pin (D- per USB specification) for USB0. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 0.
36
XOSC1 VBAT
O -
Analog Power
37 38 39 40 41 42 RST GND OSC0 OSC1 VDD PD4 U6Rx 43 USB0DM WT4CCP0 I I O I/O I I/O I/O TTL Power Analog Analog Power TTL TTL Analog TTL
April 25, 2012

Pin Number Pin Name PD5 U6Tx 44 USB0DP WT4CCP1 PB0 45 T2CCP0 U1Rx PB1 46 T2CCP1 U1Tx PB2 47 I2C0SCL T3CCP0 PB3 48 I2C0SDA T3CCP1 PC3 SWO 49 T5CCP1 TDO PC2 50 T5CCP0 TDI PC1 SWDIO 51 T4CCP1 TMS PC0 SWCLK 52 T4CCP0 TCK PD6 53 U2Rx WT5CCP0 54 55 VDD GND VDDC 56 Pin Type I/O O I/O I/O I/O I/O I I/O I/O O I/O I/O I/O I/O I/O I/O I/O O I/O O I/O I/O I I/O I/O I/O I I/O I I/O I I/O I I/O Buffer Type TTL TTL Analog TTL TTL TTL TTL TTL TTL TTL TTL OD TTL TTL OD TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL Power Power Power
a
Description GPIO port D bit 5. UART module 6 transmit. Bidirectional differential data pin (D+ per USB specification) for USB0. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 1. GPIO port B bit 0. This pin is not 5-V tolerant. 16/32-Bit Timer 2 Capture/Compare/PWM 0. UART module 1 receive. GPIO port B bit 1. This pin is not 5-V tolerant. 16/32-Bit Timer 2 Capture/Compare/PWM 1. UART module 1 transmit. GPIO port B bit 2. I2C module 0 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. 16/32-Bit Timer 3 Capture/Compare/PWM 0. GPIO port B bit 3. I2C module 0 data. 16/32-Bit Timer 3 Capture/Compare/PWM 1. GPIO port C bit 3. JTAG TDO and SWO. 16/32-Bit Timer 5 Capture/Compare/PWM 1. JTAG TDO and SWO. GPIO port C bit 2. 16/32-Bit Timer 5 Capture/Compare/PWM 0. JTAG TDI. GPIO port C bit 1. JTAG TMS and SWDIO. 16/32-Bit Timer 4 Capture/Compare/PWM 1. JTAG TMS and SWDIO. GPIO port C bit 0. JTAG/SWD CLK. 16/32-Bit Timer 4 Capture/Compare/PWM 0. JTAG/SWD CLK. GPIO port D bit 6. UART module 2 receive. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 0. Positive supply for I/O and some logic. Ground reference for logic and I/O pins. Positive supply for most of the logic function, including the processor core and most peripherals. The voltage on this pin is 1.2 V and is supplied by the on-chip LDO. The VDDC pins should only be connected to each other and an external capacitor as specified in Table 23-8 on page 1164 .
1141
Signal Tables

Pin Number Pin Name PB5 AIN11 57 CAN0Tx SSI2Fss T1CCP1 PB4 AIN10 58 CAN0Rx SSI2Clk T1CCP0 PE4 AIN9 59 CAN0Rx I2C2SCL U5Rx PE5 AIN8 60 CAN0Tx I2C2SDA U5Tx PD0 AIN7 I2C3SCL 61 SSI1Clk SSI3Clk WT2CCP0 PD1 AIN6 I2C3SDA 62 SSI1Fss SSI3Fss WT2CCP1 PD2 AIN5 63 SSI1Rx SSI3Rx WT3CCP0 I/O I/O I/O I/O I I/O I/O I/O I/O I/O I I I I/O TTL TTL TTL TTL Analog OD TTL TTL TTL TTL Analog TTL TTL TTL Pin Type I/O I O I/O I/O I/O I I I/O I/O I/O I I I/O I I/O I O I/O O I/O I I/O Buffer Type TTL Analog TTL TTL TTL TTL Analog TTL TTL TTL TTL Analog TTL OD TTL TTL Analog TTL OD TTL TTL Analog OD
a
Description GPIO port B bit 5. Analog-to-digital converter input 11. CAN module 0 transmit. SSI module 2 frame signal 16/32-Bit Timer 1 Capture/Compare/PWM 1. GPIO port B bit 4. Analog-to-digital converter input 10. CAN module 0 receive. SSI module 2 clock 16/32-Bit Timer 1 Capture/Compare/PWM 0. GPIO port E bit 4. Analog-to-digital converter input 9. CAN module 0 receive. I2C module 2 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. UART module 5 receive. GPIO port E bit 5. Analog-to-digital converter input 8. CAN module 0 transmit. I2C module 2 data. UART module 5 transmit. GPIO port D bit 0. Analog-to-digital converter input 7. I2C module 3 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. SSI module 1 clock SSI module 3 clock 32/64-Bit Wide Timer 2 Capture/Compare/PWM 0. GPIO port D bit 1. Analog-to-digital converter input 6. I2C module 3 data. SSI module 1 frame signal SSI module 3 frame signal 32/64-Bit Wide Timer 2 Capture/Compare/PWM 1. GPIO port D bit 2. Analog-to-digital converter input 5. SSI module 1 receive SSI module 3 receive 32/64-Bit Wide Timer 3 Capture/Compare/PWM 0.
April 25, 2012

Pin Number Pin Name PD3 AIN4 64 SSI1Tx SSI3Tx WT3CCP1 Pin Type I/O I O O I/O Buffer Type TTL Analog TTL TTL TTL
a
Description GPIO port D bit 3. Analog-to-digital converter input 4. SSI module 1 transmit SSI module 3 transmit 32/64-Bit Wide Timer 3 Capture/Compare/PWM 1.
Table 21-3. Signals by Signal Name

Pin Name AIN0 AIN1 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7 AIN8 AIN9 AIN10 AIN11 C0+ C0C0o C1+ C1C1o CAN0Rx Pin Number Pin Mux / Pin Assignment 6 7 8 9 64 63 62 61 60 59 58 57 14 13 28 15 16 29 28 58 59 31 57 60 12 27 39 55 3 PE3 PE2 PE1 PE0 PD3 PD2 PD1 PD0 PE5 PE4 PB4 PB5 PC6 PC7 PF0 (9) PC5 PC4 PF1 (9) PF0 (3) PB4 (8) PE4 (8) PF3 (3) PB5 (8) PE5 (8) fixed Pin Type I I I I I I I I I I I I I I O I I O I Buffer Type Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog TTL Analog Analog TTL TTL
a
Description Analog-to-digital converter input 0. Analog-to-digital converter input 1. Analog-to-digital converter input 2. Analog-to-digital converter input 3. Analog-to-digital converter input 4. Analog-to-digital converter input 5. Analog-to-digital converter input 6. Analog-to-digital converter input 7. Analog-to-digital converter input 8. Analog-to-digital converter input 9. Analog-to-digital converter input 10. Analog-to-digital converter input 11. Analog comparator 0 positive input. Analog comparator 0 negative input. Analog comparator 0 output. Analog comparator 1 positive input. Analog comparator 1 negative input. Analog comparator 1 output. CAN module 0 receive.
CAN0Tx
TTL
GND
Power
Ground reference for logic and I/O pins.
GNDA
fixed
Power
The ground reference for the analog circuits (ADC, Analog Comparators, etc.). These are separated from GND to minimize the electrical noise contained on VDD from affecting the analog functions.
1143
Signal Tables
Table 21-3. Signals by Signal Name (continued)

Pin Name GNDX Pin Number Pin Mux / Pin Assignment 35 fixed Pin Type Buffer Type Power
a
Description GND for the Hibernation oscillator. When using a crystal clock source, this pin should only be connected to the crystal load capacitors to improve oscillator immunity to system noise. When using an external oscillator, this pin should be connected to GND. An output that indicates the processor is in Hibernate mode. I2C module 0 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 0 data. I2C module 1 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 1 data. I2C module 2 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 2 data. I2C module 3 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 3 data. Non-maskable interrupt. Main oscillator crystal input or an external clock reference input. Main oscillator crystal output. Leave unconnected when using a single-ended clock source. GPIO port A bit 0. GPIO port A bit 1. GPIO port A bit 2. GPIO port A bit 3. GPIO port A bit 4. GPIO port A bit 5. GPIO port A bit 6. GPIO port A bit 7. GPIO port B bit 0. This pin is not 5-V tolerant. GPIO port B bit 1. This pin is not 5-V tolerant. GPIO port B bit 2. GPIO port B bit 3. GPIO port B bit 4. GPIO port B bit 5. GPIO port B bit 6. GPIO port B bit 7.
HIB I2C0SCL
33 47
fixed PB2 (3)
O I/O
TTL OD
I2C0SDA I2C1SCL
48 23
PB3 (3) PA6 (3)
I/O I/O
OD OD
I2C1SDA I2C2SCL
24 59
PA7 (3) PE4 (3)
I/O I/O
OD OD
I2C2SDA I2C3SCL
60 61
PE5 (3) PD0 (3)
I/O I/O
OD OD
I2C3SDA NMI OSC0 OSC1 PA0 PA1 PA2 PA3 PA4 PA5 PA6 PA7 PB0 PB1 PB2 PB3 PB4 PB5 PB6 PB7
62 10 28 40 41 17 18 19 20 21 22 23 24 45 46 47 48 58 57 1 4
PD1 (3) PD7 (8) PF0 (8) fixed fixed -
I/O I I O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O
OD TTL Analog Analog TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
April 25, 2012

Pin Name PC0 PC1 PC2 PC3 PC4 PC5 PC6 PC7 PD0 PD1 PD2 PD3 PD4 PD5 PD6 PD7 PE0 PE1 PE2 PE3 PE4 PE5 PF0 PF1 PF2 PF3 PF4 RST SSI0Clk SSI0Fss SSI0Rx SSI0Tx SSI1Clk SSI1Fss SSI1Rx SSI1Tx SSI2Clk SSI2Fss Pin Number Pin Mux / Pin Assignment 52 51 50 49 16 15 14 13 61 62 63 64 43 44 53 10 9 8 7 6 59 60 28 29 30 31 5 38 19 20 21 22 30 61 31 62 28 63 29 64 58 57 fixed PA2 (2) PA3 (2) PA4 (2) PA5 (2) PF2 (2) PD0 (2) PF3 (2) PD1 (2) PF0 (2) PD2 (2) PF1 (2) PD3 (2) PB4 (2) PB5 (2) Pin Type I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I I/O I/O I O I/O I/O I O I/O I/O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description GPIO port C bit 0. GPIO port C bit 1. GPIO port C bit 2. GPIO port C bit 3. GPIO port C bit 4. GPIO port C bit 5. GPIO port C bit 6. GPIO port C bit 7. GPIO port D bit 0. GPIO port D bit 1. GPIO port D bit 2. GPIO port D bit 3. GPIO port D bit 4. GPIO port D bit 5. GPIO port D bit 6. GPIO port D bit 7. GPIO port E bit 0. GPIO port E bit 1. GPIO port E bit 2. GPIO port E bit 3. GPIO port E bit 4. GPIO port E bit 5. GPIO port F bit 0. GPIO port F bit 1. GPIO port F bit 2. GPIO port F bit 3. GPIO port F bit 4. System reset input. SSI module 0 clock SSI module 0 frame signal SSI module 0 receive SSI module 0 transmit SSI module 1 clock SSI module 1 frame signal SSI module 1 receive SSI module 1 transmit SSI module 2 clock SSI module 2 frame signal
1145
Signal Tables

Pin Name SSI2Rx SSI2Tx SSI3Clk SSI3Fss SSI3Rx SSI3Tx SWCLK SWDIO SWO T0CCP0 T0CCP1 T1CCP0 T1CCP1 T2CCP0 T2CCP1 T3CCP0 T3CCP1 T4CCP0 T4CCP1 T5CCP0 T5CCP1 TCK TDI TDO TMS TRCLK TRD0 TRD1 U0Rx U0Tx U1CTS U1RTS U1Rx U1Tx Pin Number Pin Mux / Pin Assignment 1 4 61 62 63 64 52 51 49 1 28 4 29 30 58 31 57 5 45 46 47 48 52 51 50 49 52 50 49 51 31 30 29 17 18 15 29 16 28 16 45 15 46 PB6 (2) PB7 (2) PD0 (1) PD1 (1) PD2 (1) PD3 (1) PC0 (1) PC1 (1) PC3 (1) PB6 (7) PF0 (7) PB7 (7) PF1 (7) PF2 (7) PB4 (7) PF3 (7) PB5 (7) PF4 (7) PB0 (7) PB1 (7) PB2 (7) PB3 (7) PC0 (7) PC1 (7) PC2 (7) PC3 (7) PC0 (1) PC2 (1) PC3 (1) PC1 (1) PF3 (14) PF2 (14) PF1 (14) PA0 (1) PA1 (1) PC5 (8) PF1 (1) PC4 (8) PF0 (1) PC4 (2) PB0 (1) PC5 (2) PB1 (1) Pin Type I O I/O I/O I O I I/O O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I I O I O O O I O I O I O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description SSI module 2 receive SSI module 2 transmit SSI module 3 clock SSI module 3 frame signal SSI module 3 receive SSI module 3 transmit JTAG/SWD CLK. JTAG TMS and SWDIO. JTAG TDO and SWO. 16/32-Bit Timer 0 Capture/Compare/PWM 0. 16/32-Bit Timer 0 Capture/Compare/PWM 1. 16/32-Bit Timer 1 Capture/Compare/PWM 0. 16/32-Bit Timer 1 Capture/Compare/PWM 1. 16/32-Bit Timer 2 Capture/Compare/PWM 0. 16/32-Bit Timer 2 Capture/Compare/PWM 1. 16/32-Bit Timer 3 Capture/Compare/PWM 0. 16/32-Bit Timer 3 Capture/Compare/PWM 1. 16/32-Bit Timer 4 Capture/Compare/PWM 0. 16/32-Bit Timer 4 Capture/Compare/PWM 1. 16/32-Bit Timer 5 Capture/Compare/PWM 0. 16/32-Bit Timer 5 Capture/Compare/PWM 1. JTAG/SWD CLK. JTAG TDI. JTAG TDO and SWO. JTAG TMS and SWDIO. Trace clock. Trace data 0. Trace data 1. UART module 0 receive. UART module 0 transmit. UART module 1 Clear To Send modem flow control input signal. UART module 1 Request to Send modem flow control output line. UART module 1 receive. UART module 1 transmit.
April 25, 2012

Pin Name U2Rx U2Tx U3Rx U3Tx U4Rx U4Tx U5Rx U5Tx U6Rx U6Tx U7Rx U7Tx USB0DM USB0DP VBAT Pin Number Pin Mux / Pin Assignment 53 10 14 13 16 15 59 60 43 44 9 8 43 44 37 PD6 (1) PD7 (1) PC6 (1) PC7 (1) PC4 (1) PC5 (1) PE4 (1) PE5 (1) PD4 (1) PD5 (1) PE0 (1) PE1 (1) PD4 PD5 fixed Pin Type I O I O I O I O I O I O I/O I/O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL Analog Analog Power
a
Description UART module 2 receive. UART module 2 transmit. UART module 3 receive. UART module 3 transmit. UART module 4 receive. UART module 4 transmit. UART module 5 receive. UART module 5 transmit. UART module 6 receive. UART module 6 transmit. UART module 7 receive. UART module 7 transmit. Bidirectional differential data pin (D- per USB specification) for USB0. Bidirectional differential data pin (D+ per USB specification) for USB0. Power source for the Hibernation module. It is normally connected to the positive terminal of a battery and serves as the battery backup/Hibernation module power-source supply. Positive supply for I/O and some logic.
VDD
11 26 42 54 2
fixed
Power
VDDA
fixed
Power
The positive supply for the analog circuits (ADC, Analog Comparators, etc.). These are separated from VDD to minimize the electrical noise contained on VDD from affecting the analog functions. VDDA pins must be supplied with a voltage that meets the specification in Table 23-2 on page 1159, regardless of system implementation. Positive supply for most of the logic function, including the processor core and most peripherals. The voltage on this pin is 1.2 V and is supplied by the on-chip LDO. The VDDC pins should only be connected to each other and an external capacitor as specified in Table 23-8 on page 1164 . An external input that brings the processor out of Hibernate mode when asserted. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 1.
VDDC
25 56
fixed
Power
WAKE WT0CCP0 WT0CCP1 WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1
32 16 15 14 13 61 62 63 64
fixed PC4 (7) PC5 (7) PC6 (7) PC7 (7) PD0 (7) PD1 (7) PD2 (7) PD3 (7)
I I/O I/O I/O I/O I/O I/O I/O I/O
TTL TTL TTL TTL TTL TTL TTL TTL TTL
1147
Signal Tables

Pin Name WT4CCP0 WT4CCP1 WT5CCP0 WT5CCP1 XOSC0 Pin Number Pin Mux / Pin Assignment 43 44 53 10 34 PD4 (7) PD5 (7) PD6 (7) PD7 (7) fixed Pin Type I/O I/O I/O I/O I Buffer Type TTL TTL TTL TTL Analog
a
Description 32/64-Bit Wide Timer 4 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 1. Hibernation module oscillator crystal input or an external clock reference input. Note that this is either a 32.768-kHz crystal or a 32.768-kHz oscillator for the Hibernation module RTC. Hibernation module oscillator crystal output. Leave unconnected when using a single-ended clock source.
XOSC1
36
fixed
Analog
Table 21-4. Signals by Function, Except for GPIO

Function Pin Name AIN0 AIN1 AIN2 AIN3 AIN4 AIN5 ADC AIN6 AIN7 AIN8 AIN9 AIN10 AIN11 C0+ C0C0o Analog Comparators C1+ C1C1o CAN0Rx Controller Area Network Pin Number 6 7 8 9 64 63 62 61 60 59 58 57 14 13 28 15 16 29 28 58 59 31 57 60 31 30 29 Pin Type I I I I I I I I I I I I I I O I I O I Buffer Type Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog Analog TTL Analog Analog TTL TTL
a
Description Analog-to-digital converter input 0. Analog-to-digital converter input 1. Analog-to-digital converter input 2. Analog-to-digital converter input 3. Analog-to-digital converter input 4. Analog-to-digital converter input 5. Analog-to-digital converter input 6. Analog-to-digital converter input 7. Analog-to-digital converter input 8. Analog-to-digital converter input 9. Analog-to-digital converter input 10. Analog-to-digital converter input 11. Analog comparator 0 positive input. Analog comparator 0 negative input. Analog comparator 0 output. Analog comparator 1 positive input. Analog comparator 1 negative input. Analog comparator 1 output. CAN module 0 receive.
CAN0Tx
TTL
TRCLK Core TRD0 TRD1
O O O
TTL TTL TTL
Trace clock. Trace data 0. Trace data 1.
April 25, 2012
Table 21-4. Signals by Function, Except for GPIO (continued)

Function Pin Name T0CCP0 T0CCP1 T1CCP0 T1CCP1 T2CCP0 T2CCP1 T3CCP0 T3CCP1 T4CCP0 General-Purpose Timers T4CCP1 T5CCP0 T5CCP1 WT0CCP0 WT0CCP1 WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1 WT4CCP0 WT4CCP1 WT5CCP0 WT5CCP1 Pin Number 1 28 4 29 30 58 31 57 5 45 46 47 48 52 51 50 49 16 15 14 13 61 62 63 64 43 44 53 10 Pin Type I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O Buffer Type TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
a
Description 16/32-Bit Timer 0 Capture/Compare/PWM 0. 16/32-Bit Timer 0 Capture/Compare/PWM 1. 16/32-Bit Timer 1 Capture/Compare/PWM 0. 16/32-Bit Timer 1 Capture/Compare/PWM 1. 16/32-Bit Timer 2 Capture/Compare/PWM 0. 16/32-Bit Timer 2 Capture/Compare/PWM 1. 16/32-Bit Timer 3 Capture/Compare/PWM 0. 16/32-Bit Timer 3 Capture/Compare/PWM 1. 16/32-Bit Timer 4 Capture/Compare/PWM 0. 16/32-Bit Timer 4 Capture/Compare/PWM 1. 16/32-Bit Timer 5 Capture/Compare/PWM 0. 16/32-Bit Timer 5 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 0 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 1 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 2 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 3 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 4 Capture/Compare/PWM 1. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 0. 32/64-Bit Wide Timer 5 Capture/Compare/PWM 1.
1149
Signal Tables

Function Pin Name GNDX Pin Number 35 Pin Type Buffer Type Power
a
Description GND for the Hibernation oscillator. When using a crystal clock source, this pin should only be connected to the crystal load capacitors to improve oscillator immunity to system noise. When using an external oscillator, this pin should be connected to GND. An output that indicates the processor is in Hibernate mode. Power source for the Hibernation module. It is normally connected to the positive terminal of a battery and serves as the battery backup/Hibernation module power-source supply. An external input that brings the processor out of Hibernate mode when asserted. Hibernation module oscillator crystal input or an external clock reference input. Note that this is either a 32.768-kHz crystal or a 32.768-kHz oscillator for the Hibernation module RTC. Hibernation module oscillator crystal output. Leave unconnected when using a single-ended clock source. I2C module 0 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 0 data. I2C module 1 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 1 data. I2C module 2 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 2 data. I2C module 3 clock. Note that this signal has an active pull-up. The corresponding port pin should not be configured as open drain. I2C module 3 data. JTAG/SWD CLK. JTAG TMS and SWDIO. JTAG TDO and SWO. JTAG/SWD CLK. JTAG TDI. JTAG TDO and SWO. JTAG TMS and SWDIO.
HIB VBAT Hibernate WAKE XOSC0
33 37
O -
TTL Power
32 34
I I
TTL Analog
XOSC1
36
Analog
I2C0SCL
47
I/O
OD
I2C0SDA I2C1SCL
48 23
I/O I/O
OD OD
I2C1SDA I2C I2C2SCL
24 59
I/O I/O
OD OD
I2C2SDA I2C3SCL
60 61
I/O I/O
OD OD
I2C3SDA SWCLK SWDIO SWO JTAG/SWD/SWO TCK TDI TDO TMS
62 52 51 49 52 50 49 51
I/O I I/O O I I O I
OD TTL TTL TTL TTL TTL TTL TTL
April 25, 2012

Function Pin Name GND Pin Number 12 27 39 55 3 Pin Type Buffer Type Power
a
Description Ground reference for logic and I/O pins.
GNDA
Power
The ground reference for the analog circuits (ADC, Analog Comparators, etc.). These are separated from GND to minimize the electrical noise contained on VDD from affecting the analog functions. Positive supply for I/O and some logic.
VDD
11 26 42 54 2
Power
Power
VDDA
Power
The positive supply for the analog circuits (ADC, Analog Comparators, etc.). These are separated from VDD to minimize the electrical noise contained on VDD from affecting the analog functions. VDDA pins must be supplied with a voltage that meets the specification in Table 23-2 on page 1159, regardless of system implementation. Positive supply for most of the logic function, including the processor core and most peripherals. The voltage on this pin is 1.2 V and is supplied by the on-chip LDO. The VDDC pins should only be connected to each other and an external capacitor as specified in Table 23-8 on page 1164 . SSI module 0 clock SSI module 0 frame signal SSI module 0 receive SSI module 0 transmit SSI module 1 clock SSI module 1 frame signal SSI module 1 receive SSI module 1 transmit SSI module 2 clock SSI module 2 frame signal SSI module 2 receive SSI module 2 transmit SSI module 3 clock SSI module 3 frame signal SSI module 3 receive SSI module 3 transmit
VDDC
25 56
Power
SSI0Clk SSI0Fss SSI0Rx SSI0Tx SSI1Clk SSI1Fss SSI1Rx SSI SSI1Tx SSI2Clk SSI2Fss SSI2Rx SSI2Tx SSI3Clk SSI3Fss SSI3Rx SSI3Tx
19 20 21 22 30 61 31 62 28 63 29 64 58 57 1 4 61 62 63 64
I/O I/O I O I/O I/O I O I/O I/O I O I/O I/O I O
TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL
1151
Signal Tables

Function Pin Name NMI OSC0 System Control & Clocks OSC1 RST U0Rx U0Tx U1CTS U1RTS U1Rx U1Tx U2Rx UART U2Tx U3Rx U3Tx U4Rx U4Tx U5Rx U5Tx U6Rx U6Tx U7Rx U7Tx USB0DM USB USB0DP Pin Number 10 28 40 41 38 17 18 15 29 16 28 16 45 15 46 53 10 14 13 16 15 59 60 43 44 9 8 43 44 Pin Type I I O I I O I O I O I O I O I O I O I O I O I/O I/O Buffer Type TTL Analog Analog TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL TTL Analog Analog
a
Description Non-maskable interrupt. Main oscillator crystal input or an external clock reference input. Main oscillator crystal output. Leave unconnected when using a single-ended clock source. System reset input. UART module 0 receive. UART module 0 transmit. UART module 1 Clear To Send modem flow control input signal. UART module 1 Request to Send modem flow control output line. UART module 1 receive. UART module 1 transmit. UART module 2 receive. UART module 2 transmit. UART module 3 receive. UART module 3 transmit. UART module 4 receive. UART module 4 transmit. UART module 5 receive. UART module 5 transmit. UART module 6 receive. UART module 6 transmit. UART module 7 receive. UART module 7 transmit. Bidirectional differential data pin (D- per USB specification) for USB0. Bidirectional differential data pin (D+ per USB specification) for USB0.
Table 21-5. GPIO Pins and Alternate Functions

IO PA0 PA1 PA2 PA3 PA4 PA5 Pin 17 18 19 20 21 22 Analog Function Digital Function (GPIOPCTL PMCx Bit Field Encoding) 1 U0Rx U0Tx 2 SSI0Clk SSI0Fss SSI0Rx SSI0Tx 3 4 5 6 7 8 a
9 -
14 -
15 -
April 25, 2012
Table 21-5. GPIO Pins and Alternate Functions (continued)

IO PA6 PA7 PB0 PB1 PB2 PB3 PB4 PB5 PB6 PB7 PC0 PC1 PC2 PC3 PC4 PC5 PC6 PC7 PD0 PD1 PD2 PD3 PD4 PD5 PD6 PD7 PE0 PE1 PE2 PE3 PE4 PE5 PF0 PF1 PF2 PF3 PF4 Pin 23 24 45 46 47 48 58 57 1 4 52 51 50 49 16 15 14 13 61 62 63 64 43 44 53 10 9 8 7 6 59 60 28 29 30 31 5 Analog Function AIN10 AIN11 C1C1+ C0+ C0AIN7 AIN6 AIN5 AIN4 USB0DM USB0DP AIN3 AIN2 AIN1 AIN0 AIN9 AIN8 Digital Function (GPIOPCTL PMCx Bit Field Encoding) 1 U1Rx U1Tx TCK SWCLK TMS SWDIO
a
2 SSI2Clk SSI2Fss SSI2Rx SSI2Tx U1Rx U1Tx -
3 I2C1SCL I2C1SDA I2C0SCL I2C0SDA -
4 -
5 -
6 -
7 T2CCP0 T2CCP1 T3CCP0 T3CCP1
8 -
9 C0o C1o -
14 TRD1 TRD0 TRCLK -
15 -
T1CCP0 CAN0Rx T1CCP1 CAN0Tx T0CCP0 T0CCP1 T4CCP0 T4CCP1 T5CCP0 T5CCP1 -
TDI TDO SWO U4Rx U4Tx U3Rx U3Tx
WT0CCP0 U1RTS WT0CCP1 U1CTS WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1 WT4CCP0 WT4CCP1 WT5CCP0 WT5CCP1 T0CCP0 T0CCP1 T1CCP0 T1CCP1 T2CCP0 NMI CAN0Rx CAN0Tx NMI -
SSI3Clk SSI1Clk I2C3SCL SSI3Fss SSI1Fss I2C3SDA SSI3Rx SSI1Rx SSI3Tx SSI1Tx U6Rx U6Tx U2Rx U2Tx U7Rx U7Tx U5Rx U5Tx U1RTS U1CTS I2C2SCL I2C2SDA
SSI1Rx CAN0Rx SSI1Tx SSI1Clk -
SSI1Fss CAN0Tx -
a. The digital signals that are shaded gray are the power-on default values for the corresponding GPIO pin. Encodings 10-13 are not used on this device.
1153
Signal Tables
Table 21-6. Possible Pin Assignments for Alternate Functions

# of Possible Assignments Alternate Function AIN0 AIN1 AIN10 AIN11 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7 AIN8 AIN9 C0+ C0C0o C1+ C1C1o I2C0SCL I2C0SDA one I2C1SCL I2C1SDA I2C2SCL I2C2SDA I2C3SCL I2C3SDA SSI0Clk SSI0Fss SSI0Rx SSI0Tx SSI2Clk SSI2Fss SSI2Rx SSI2Tx SSI3Clk SSI3Fss SSI3Rx SSI3Tx SWCLK SWDIO SWO GPIO Function PE3 PE2 PB4 PB5 PE1 PE0 PD3 PD2 PD1 PD0 PE5 PE4 PC6 PC7 PF0 PC5 PC4 PF1 PB2 PB3 PA6 PA7 PE4 PE5 PD0 PD1 PA2 PA3 PA4 PA5 PB4 PB5 PB6 PB7 PD0 PD1 PD2 PD3 PC0 PC1 PC3
April 25, 2012
Table 21-6. Possible Pin Assignments for Alternate Functions (continued)

# of Possible Assignments Alternate Function T2CCP1 T3CCP0 T3CCP1 T4CCP0 T4CCP1 T5CCP0 T5CCP1 TCK TDI TDO TMS TRCLK TRD0 TRD1 U0Rx U0Tx U2Rx U2Tx U3Rx U3Tx U4Rx U4Tx U5Rx U5Tx U6Rx U6Tx U7Rx U7Tx USB0DM USB0DP WT0CCP0 WT0CCP1 WT1CCP0 WT1CCP1 WT2CCP0 WT2CCP1 WT3CCP0 WT3CCP1 WT4CCP0 WT4CCP1 WT5CCP0 GPIO Function PB1 PB2 PB3 PC0 PC1 PC2 PC3 PC0 PC2 PC3 PC1 PF3 PF2 PF1 PA0 PA1 PD6 PD7 PC6 PC7 PC4 PC5 PE4 PE5 PD4 PD5 PE0 PE1 PD4 PD5 PC4 PC5 PC6 PC7 PD0 PD1 PD2 PD3 PD4 PD5 PD6
1155
Signal Tables
Table 21-6. Possible Pin Assignments for Alternate Functions (continued)

# of Possible Assignments Alternate Function WT5CCP1 NMI SSI1Clk SSI1Fss SSI1Rx SSI1Tx T0CCP0 T0CCP1 two T1CCP0 T1CCP1 T2CCP0 U1CTS U1RTS U1Rx U1Tx CAN0Rx three CAN0Tx GPIO Function PD7 PD7 PF0 PD0 PF2 PD1 PF3 PD2 PF0 PD3 PF1 PB6 PF0 PB7 PF1 PB4 PF2 PB5 PF3 PB0 PF4 PC5 PF1 PC4 PF0 PB0 PC4 PB1 PC5 PB4 PE4 PF0 PB5 PE5 PF3
21.1
Connections for Unused Signals

Table 21-7 on page 1156 shows how to handle signals for functions that are not used in a particular system implementation for devices that are in a 64-pin LQFP package. Two options are shown in the table: an acceptable practice and a preferred practice for reduced power consumption and improved EMC characteristics. If a module is not used in a system, and its inputs are grounded, it is important that the clock to the module is never enabled by setting the corresponding bit in the RCGCx register. Table 21-7. Connections for Unused Signals (64-Pin LQFP)
Function GPIO Signal Name All unused GPIOs HIB VBAT WAKE Hibernate XOSC0 XOSC1 GNDX No Connects NC OSC0 System Control OSC1 RST USB0DM USB USB0DP Pin Number 33 37 32 34 36 35 40 41 38 43 44 Acceptable Practice NC NC NC NC NC NC GND NC NC NC Preferred Practice GND NC VDD GND GND NC GND NC GND NC
Pull up as shown in Figure Connect through a capacitor to 5-1 on page 211 GND as close to pin as possible NC NC GND GND
April 25, 2012
22
Operating Characteristics
Table 22-1. Temperature Characteristics
Characteristic Symbol Value -40 to +85 -65 to +150 Unit C C Industrial operating temperature range TA Unpowered storage temperature range TS
Table 22-2. Thermal Characteristics

Characteristic
a c
Symbol Value 50
b
Unit C/W C
Thermal resistance (junction to ambient) JA Junction temperature, -40 to +125 TJ
TA + (P JA)
a. Junction to ambient thermal resistance JA numbers are determined by a package simulator. b. Preliminary. c. Power dissipation is a function of temperature.
Table 22-3. ESD Absolute Maximum Ratings

Parameter Name VESDHBM VESDCDM
Min -
Nom -
Max 2.0 500
Unit kV V
a. All Stellaris parts are ESD tested following the JEDEC standard.
1157
Electrical Characteristics
23
23.1
Maximum Ratings
The maximum ratings are the limits to which the device can be subjected without permanently damaging the device. Device reliability may be adversely affected by exposure to absolute-maximum ratings for extended periods. Note: The device is not guaranteed to operate properly at the maximum ratings.
Table 23-1. Maximum Ratings

Parameter VDD VDDA VBAT VIN_GPIO IGPIOMAX INON Parameter Name
a
Value Min 0 0 0 -0.3 -0.3 Max 4 4 4 5.5 VDD + 0.3 25 pending

e
Unit V V V V V mA mA
VDD supply voltage VDDA supply voltage VBAT battery supply voltage Input voltage on GPIOs, regardless of whether the bc microcontroller is powered Input voltage for PB0 and PB1 when configured as GPIO Maximum current per output pin Maximum current into or out of a non-power, non-GPIO, d non-XOSCn pin when the microcontroller is unpowered
a. Voltages are measured with respect to GND. b. Applies to static and dynamic signals including overshoot. c. Refer to Figure 23-1 on page 1159 for a representation of the ESD protection on GPIOs. d. Refer to Figure 23-2 on page 1159 for a representation of the ESD protection on these pins. e. Pending characterization.
Important: This device contains circuitry to protect the inputs against damage due to high-static voltages or electric fields; however, it is advised that normal precautions be taken to avoid application of any voltage higher than maximum-rated voltages to this high-impedance circuit. Reliability of operation is enhanced if unused inputs are connected to an appropriate logic voltage level (see Connections for Unused Signals on page 1156). Figure 23-1 on page 1159 shows a diagram of the ESD protection on GPIOs and the XOSC0 and XOSC1 pins.
April 25, 2012
Figure 23-1. ESD Protection on GPIOs and XOSCn Pins
VDD
I/O Pad
ESD Clamp GND

Figure 23-2 on page 1159 shows a diagram of the ESD protection on non-power, non-GPIO, and non-XOSCn pins. Figure 23-2. ESD Protection on Non-Power, Non-GPIO, and Non-XOSCn Pins
VDD
I/O Pad
GND
23.2
Recommended Operating Conditions

For special high-current applications, the GPIO output buffers may be used with the following restrictions. With the GPIO pins configured as 8-mA output drivers, a total of four GPIO outputs may be used to sink current loads up to 18 mA each. At 18-mA sink current loading, the VOL value is specified as 1.2 V. The high-current GPIO package pins must be selected such that there are only a maximum of two per side of the physical package with the total number of high-current GPIO outputs not exceeding four for the entire package. Table 23-2. Recommended DC Operating Conditions
Parameter VDD VDDA VDDC VIH VIL Parameter Name VDD supply voltage VDDA supply voltage VDDC supply voltage GPIO high-level input voltage GPIO low-level input voltage Min 2.97 2.97 1.08 0.65 * VDD 0 Nom 3.3 3.3 1.2 Max 3.63 3.63 1.32 VDD 0.35 * VDD Unit V V V V V
1159
Table 23-2. Recommended DC Operating Conditions (continued)

Parameter VHYS VOH VOL Parameter Name GPIO Input Hysteresis High-level output voltage Low-level output voltage High-level source current, VOH=2.4 V IOH
a
Min 0.2 2.4 -
Nom -
Max 0.4
Unit V V V
2-mA Drive 4-mA Drive 8-mA Drive Low-level sink current, VOL=0.4 V
a
-2.0 -4.0 -8.0
mA mA mA
2-mA Drive IOL 4-mA Drive 8-mA Drive 8-mA Drive, VOL=1.2 V
2.0 4.0 8.0 18.0
mA mA mA mA
a. IO specifications reflect the maximum current where the corresponding output voltage meets the VOH/VOL thresholds. IO current can exceed these limits (subject to absolute maximum ratings).
Table 23-3. GPIO Current Restrictions

Parameter IMAXL IMAXB IMAXR IMAXT Parameter Name
Min
b b
Nom -
Max 30 35 40 40
Unit mA mA mA mA
Cumulative maximum GPIO current per side, left
Cumulative maximum GPIO current per side, bottom Cumulative maximum GPIO current per side, right Cumulative maximum GPIO current per side, top
b
a. Based on design simulations, not tested in production. b. Sum of sink and source current for GPIOs as shown in Table 23-4 on page 1160.
Table 23-4. GPIO Package Side Assignments

Side Left Bottom Right Top GPIOs PB[6-7], PC[4-7], PD7, PE[0-3], PF4 PA[0-7], PF[0-3] PB[0-3], PD[4-5] PB[4-5], PC[0-3], PD[0-3,6], PE[4-5]
23.3
Load Conditions
Unless otherwise specified, the following conditions are true for all timing measurements. Figure 23-3. Load Conditions
pin
CL = 50 pF
GND
April 25, 2012
23.4
JTAG and Boundary Scan

Table 23-5. JTAG Characteristics
Parameter No. J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 Parameter FTCK TTCK TTCK_LOW TTCK_HIGH TTCK_R TTCK_F TTMS_SU TTMS_HLD TTDI_SU TTDI_HLD Parameter Name TCK operational clock frequency TCK operational clock period TCK clock Low time TCK clock High time TCK rise time TCK fall time TMS setup time to TCK rise TMS hold time from TCK rise TDI setup time to TCK rise TDI hold time from TCK rise TCK fall to Data Valid from High-Z, 2-mA drive TCK fall to Data Valid from High-Z, 4-mA drive J11 TTDO_ZDV TCK fall to Data Valid from High-Z, 8-mA drive TCK fall to Data Valid from High-Z, 8-mA drive with slew rate control TCK fall to Data Valid from Data Valid, 2-mA drive TCK fall to Data Valid from Data Valid, 4-mA drive J12 TTDO_DV TCK fall to Data Valid from Data Valid, 8-mA drive TCK fall to Data Valid from Data Valid, 8-mA drive with slew rate control TCK fall to High-Z from Data Valid, 2-mA drive TCK fall to High-Z from Data Valid, 4-mA drive J13 TTDO_DVZ TCK fall to High-Z from Data Valid, 8-mA drive TCK fall to High-Z from Data Valid, 8-mA drive with slew rate control a. A ratio of at least 8:1 must be kept between the system clock and TCK. a
Min 0 100 0 0 8 4 18 4
Nom tTCK/2 tTCK/2 13 9 8 10 14 10 8 10 7 7 7 8
Max 10 10 10 35 26 26 29 20 26 21 26 16 16 16 19
Unit MHz ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns
Figure 23-4. JTAG Test Clock Input Timing

J2 J3 J4
TCK
J6 J5
1161
Figure 23-5. JTAG Test Access Port (TAP) Timing

TCK
J7 J8 J7 J8
TMS
TMS Input Valid J9 J10
TMS Input Valid J9 J10
TDI
J11
TDI Input Valid J12 TDO Output Valid
TDI Input Valid J13 TDO Output Valid
TDO
23.5
Power and Brown-Out

Table 23-6. Power Characteristics
Parameter No. P1 P2 Parameter TVDDRISE VTH VBTH TPOR TBOR Parameter Name Supply voltage (VDD) rise time Power-On Reset threshold (rising edge) Power-On Reset threshold (falling edge) Brown-Out Reset threshold (rising edge) Brown-Out Reset threshold (falling edge) Power-On Reset timeout Brown-Out Reset timeout Min 2.0 2.0 2.8 2.8 1 Nom 2.31 2.27 2.92 2.90 Max 2.6 2.6 3.1 3.1 500 a
Unit ms V V V V s s
P3 P4 P5
a. After the minimum timeout, BOR stays active as long as the power supply is below VBTH. The voltage level is checked every clock cycle after the initial countdown completes. BOR is deasserted on the next clock cycle after the BOR condition goes away.
April 25, 2012
Figure 23-6. Power-On and Brown-Out Reset and Voltage Parameters
VDD P2R = P3R
P1
P3F P2F
P4
/POR
0
/BOR
0
Figure 23-7. Brown-Out Reset Timing

P3
VDD
P5
/Reset (Internal)
23.6
Reset
Table 23-7. Reset Characteristics
Parameter No. R1 R2 R3 R4 Parameter TIRHWR TIRSWR TIRWDR TIRMFR Parameter Name Internal reset timeout after hardware reset a (RST pin) Internal reset timeout after software-initiated system reset Internal reset timeout after watchdog reset Internal reset timeout after MOSC failure reset Min 20 Nom 1 1 1 Max b
Unit s s s s
1163
Table 23-7. Reset Characteristics (continued)

Parameter No. R5 Parameter TMIN Parameter Name Minimum RST pulse width Min 100 Nom Max Unit ns
a. When in Deep-Sleep mode with the IOSC as the clock source, the internal reset timeout after a hardware reset is 30 s * the Deep-sleep clock divider (DSDIVORIDE). b. After the minimum timeout, internal reset stays active as long as the RST pin is asserted, and is released when the RST pin is deasserted.
Figure 23-8. External Reset Timing (RST)
RST
R5 R1
/Reset (Internal)
Figure 23-9. Software Reset Timing
SW Reset
R2
/Reset (Internal)
Figure 23-10. Watchdog Reset Timing
WDOG Reset (Internal)

R3
/Reset (Internal)
Figure 23-11. MOSC Failure Reset Timing
MOSC Fail Reset (Internal)

R4
/Reset (Internal)
23.7
On-Chip Low Drop-Out (LDO) Regulator

Table 23-8. LDO Regulator Characteristics
Parameter CLDO Parameter Name External filter capacitor size for internal power a supply Min 2.5 Nom Max 4.0 Unit F
April 25, 2012
Table 23-8. LDO Regulator Characteristics (continued)

Parameter ESR ESL VLDO IINRUSH Parameter Name Filter capacitor equivalent series resistance Filter capacitor equivalent series inductance LDO output voltage Inrush current Min 10 1.08 50 Nom 1.2 Max 100 0.5 1.32 250 Unit m nH V mA
a. The capacitor should be connected as close as possible to pin 56.
23.8
23.8.1
Clocks
The following sections provide specifications on the various clock sources and mode.
PLL Specifications
The following tables provide specifications for using the PLL. Table 23-9. Phase Locked Loop (PLL) Characteristics
Parameter FREF_XTAL FREF_EXT FPLL Parameter Name Crystal reference External clock referencea PLL frequency
b
Min 5 5
a a
Nom 400 -
Max 25 25 512 * (N+1) 128 * (N+1)

c c
Unit MHz MHz MHz reference clocks reference clocks

d d
PLL lock time, enabling the PLL TREADY PLL lock time, changing the XTAL field in the RCC/RCC2 register or changing the OSCSRC between MOSC and PIOSC
a. If the PLL is not used, the minimum input frequency can be 4 MHz. b. PLL frequency is automatically calculated by the hardware based on the XTAL field of the RCC register. c. N is the value in the N field in the PLLFREQ1 register. d. A reference clock is the clock period of the crystal being used, which can be MOSC or PIOSC. For example, a 16-MHz crystal connected to MOSC yields a reference clock of 62.5 ns.
Table 23-10 on page 1165 shows the actual frequency of the PLL based on the crystal frequency used (defined by the XTAL field in the RCC register). Table 23-10. Actual PLL Frequency
XTAL Crystal Frequency (MHz) 5.0 5.12 6.0 6.144 7.3728 8.0 8.192 10.0 12.0 12.288 MINT MFRAC Q N PLL Multiplier PLL Frequency (MHz) 400 400 400 400 399.9984 400 400 400 400 400 Error
0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12
0x50 0x9C 0xC8 0xC3 0xA2 0x32 0xC3 0x50 0xC8 0xC3
0x0 0x100 0x0 0x140 0x30A 0x0 0x140 0x0 0x0 0x140
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x1 0x2 0x2 0x2 0x0 0x3 0x1 0x5 0x5
80 156.25 200 195.3125 162.7598 50 195.3125 80 200 195.3125
0.0004% -
1165
Table 23-10. Actual PLL Frequency (continued)

XTAL Crystal Frequency (MHz) 13.56 14.318 16.0 16.384 18 20 24 25 MINT MFRAC Q N PLL Multiplier PLL Frequency (MHz) 399.9979 399.9982 400 400 400 400 400 400 Error
0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A
0xB0 0xC3 0x32 0xC3 0xC8 0x50 0x32 0x50
0x3F6 0x238 0x0 0x140 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x5 0x6 0x1 0x7 0x8 0x3 0x2 0x4
176.9902 195.5547 50 195.3125 200 80 50 80
0.0005% 0.0005% -
23.8.2
PIOSC Specifications
Table 23-11. PIOSC Clock Characteristics
Parameter FPIOSC25 FPIOSCT Parameter Name Internal 16-MHz precision oscillator frequency variance, factory calibrated at 25 C Internal 16-MHz precision oscillator frequency variance, factory calibrated at 25 C, across specified temperature range Internal 16-MHz precision oscillator frequency variance, user calibrated at a chosen temperature Min Nom 0.25% Max 1% 3% Unit -
FPIOSCUCAL
0.25%
1%
23.8.3
Internal 30-kHz Oscillator Specifications

Table 23-12. 30-kHz Clock Characteristics
Parameter FIOSC30KHZ Parameter Name Internal 30-KHz oscillator frequency Min 10 Nom 30 Max 90 Unit KHz
23.8.4
Hibernation Clock Source Specifications

Table 23-13. HIB Oscillator Input Characteristics
Parameter FHIBOSC C1, C2 CPKG CPCB C0 CSHUNT ESR DL TSTART Parameter Name Parallel resonance frequency External load capacitance on XOSC0, XOSC1 pins Device package stray shunt capacitance PCB stray shunt capacitance Crystal shunt capacitance Total shunt capacitance
a b a a a a
Min 12 c b
Nom 32.768 0.5 0.5 3 600
Max 24 4 50 75 0.25 1500

d
Unit KHz pF pF pF pF pF k k W ms
Crystal effective series resistance, OSCDRV = 0 Crystal effective series resistance, OSCDRV = 1 Oscillator output drive level Oscillator startup time, when using a crystal
April 25, 2012
Table 23-13. HIB Oscillator Input Characteristics (continued)

Parameter Parameter Name CMOS input high level, when using an external oscillator with Supply > 3.3 V CMOS input high level, when using an external oscillator with 1.8 V Supply 3.3 V CMOS input low level, when using an external oscillator with 1.8 V Supply 3.63 V
e
Min 2.64 0.8 * Supply 360 30
Nom 960 -
Max 0.2 * Supply 1390 70
Unit V V V mV %
e VIH
VIL
VHYS
CMOS input buffer hysteresis, when using an external oscillator with 1.8 V Supply 3.63 V
DCHIBOSC_EXT External clock reference duty cycle
a. See information below table. b. Crystal ESR specified by crystal manufacturer. c. Oscillator startup time is specified from the time the oscillator is enabled to when it reaches a stable point of oscillation such that the internal clock is valid. d. Only valid for 3.3 V +/-10% supply conditions. Measured with OSCDRV bit set (high drive strength enabled, 24 pF). e. Specification is relative to the larger of VDD or VBAT.
The load capacitors added on the board, C1 and C2, should be chosen such that the following equation is satisfied (see Table 23-13 on page 1166 for typical values). CL = load capacitance specified by crystal manufacturer CL = (C1*C2)/(C1+C2) + CPKG + CPCB CSHUNT = CPKG + CPCB + C0 (total shunt capacitance seen across XOSC0, XOSC1) CPKG, CPCB as measured across the XOSC0, XOSC1 pins excluding the crystal Clear the OSCDRV bit in the Hibernation Control (HIBCTL) register for C1,2 18 pF; set the OSCDRV bit for C1,2 > 18 pF. C0 = Shunt capacitance of crystal specified by the crystal manufacturer
23.8.5
Main Oscillator Specifications

Table 23-14. Main Oscillator Input Characteristics
Parameter FMOSC C1, C2 CPKG CPCB C0 CSHUNT Parameter Name Parallel resonance frequency External load capacitance on OSC0, OSC1 pins Device package stray shunt capacitance PCB stray shunt capacitance Crystal shunt capacitance Total shunt capacitance
b bc b b b
Min 4
a
Nom 0.5 0.5 4 -
Max 25 24 4
Unit MHz pF pF pF pF pF
12 -
1167
Table 23-14. Main Oscillator Input Characteristics (continued)

Parameter Parameter Name Crystal effective series resistance, 4 MHz Crystal effective series resistance, 6 MHz Crystal effective series resistance, 8 MHz ESR
dc dc dc dc dc dc
Min f
Nom OSCPWR -
Max 300 200 130 120 100 50 18 VDD 0.35 * VDD 55
Unit mW ms V V mV %
Crystal effective series resistance, 12 MHz Crystal effective series resistance, 16 MHz Crystal effective series resistance, 25 MHz
e
DL TSTART VIH VIL VHYS
Oscillator output drive level
Oscillator startup time, when using a crystal
0.65 * VDD GND 150 45
CMOS input high level, when using an external oscillator CMOS input low level, when using an external oscillator CMOS input buffer hysteresis, when using an external oscillator
DCHIBOSC_EXT External clock reference duty cycle
a. 5 MHz is the minimum when using the PLL. b. See information below table. c. Crystal vendors can be contacted to confirm these specifications are met for a specific crystal part number if the vendors generic crystal datasheet show limits outside of these specifications. d. Crystal ESR specified by crystal manufacturer. e. OSCPWR = (2 * pi * FP * CL * 2.5)2 * ESR / 2. An estimation of the typical power delivered to the crystal is based on the CL, FP and ESR parameters of the crystal in the circuit as calculated by the OSCPWR equation. Ensure that the value calculated for OSCPWR does not exceed the crystal's drive-level maximum. f. Oscillator startup time is specified from the time the oscillator is enabled to when it reaches a stable point of oscillation such that the internal clock is valid.
The load capacitors added on the board, C1 and C2, should be chosen such that the following equation is satisfied (see Table 23-14 on page 1167 for typical values and Table 23-15 on page 1169 for detailed crystal parameter information). CL = load capacitance specified by crystal manufacturer CL = (C1*C2)/(C1+C2) + CSHUNT CSHUNT = C0 + CPKG + CPCB (total shunt capacitance seen across OSC0, OSC1 crystal inputs) CPKG, CPCB = the mutual caps as measured across the OSC0,OSC1 pins excluding the crystal. C0 = Shunt capacitance of crystal specified by the crystal manufacturer
April 25, 2012
Table 23-15. Crystal Parameters

Crystal Parameters Crystal Spec Typical Values Max Values Max Dl (uW) (mm x mm) Recommended Component Values Rs(K Ohm) 0 0 0 0 0 2 0 2 1 WC Dl(uW) 132 164 214 277 362 188 437 181 331
Freq (MHz)
MFG Part#
PKG Size
Holder
ESR (Ohm)
MFG
CL1(pF) 12 12 12 12 12
NDK NX8045GB4.000M-STDCJL-5 NDK NX8045GB5.000M-STDCSF-4 NDK NX8045GB6.000M-STDCSF-4 NDK NX8045GB8.000M-STDCSF-6 NDK NX3225GA12.000MHZSTD-CRG-2 NDK NX5032GA12.000MHZLN-CD-1 NDK NX3225GA16.000MHZSTD-CRG-2 NDK NX5032GA16.000MHZLN-CD-1 NDK NX3225GA25.000MHZSTD-CRG-2 auris Q-25.000MHC3225/4F-30-30-E-12-TR
NX8045GB
8 x 4.5
STD-CJL-5 1.00 2.70 598.10 300 500
NX8045GB
8 x 4.5
STD-CJL-4 1.00 2.80 356.50 250 500
NX8045GB
8 x 4.5
STD-CJL-4 1.30 4.10 173.20 250 500
NX8045GB
8 x 4.5
STD-CSF-6 1.00 2.80 139.30 200 500
NX3225GA 3.2 x2.5
12 STD-CRG-2 0.70 2.20 81.00
100 200
CL2(pF) 12 12 12 12 12 12 12 12 12 16
L1(mH)
C0(pF)
C1(fF)
Cl(pf)
2.5 147
NX5032GA
5 x3.2
12 LN-CD-1
0.93 3.12 56.40
120 500
12
NX3225GA 3.2 x2.5
16 STD-CRG-2 1.00 2.90 33.90
80
200
12
NX5032GA
5 x3.2
16 LN-CD-1
1.02 3.82 25.90
120 500
10
NX3225GA 3.2 x2.5
25 STD-CRG-2 1.10 4.70
8.70
50
200
12
HC3225/4
3.2 x2.5
25 HC3225
1.58 5.01
8.34
50
500 12
16
Table 23-16. Supported MOSC Crystal Frequencies

Value 0x00-0x5 0x06 0x07 0x08 0x09 4 MHz 4.096 MHz 4.9152 MHz
Crystal Frequency (MHz) Not Using the PLL
Crystal Frequency (MHz) Using the PLL
reserved reserved reserved reserved 5 MHz (USB)
1169
Table 23-16. Supported MOSC Crystal Frequencies (continued)

Value 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A Crystal Frequency (MHz) Not Using the PLL Crystal Frequency (MHz) Using the PLL 5.12 MHz 6 MHz (USB) 6.144 MHz 7.3728 MHz 8 MHz (USB) 8.192 MHz 10.0 MHz (USB) 12.0 MHz (USB) 12.288 MHz 13.56 MHz 14.31818 MHz 16.0 MHz (reset value)(USB) 16.384 MHz 18.0 MHz (USB) 20.0 MHz (USB) 24.0 MHz (USB) 25.0 MHz (USB)
a. Frequencies that may be used with the USB interface are indicated in the table.
23.8.6
System Clock Specification with ADC Operation

Table 23-17. System Clock Characteristics with ADC Operation
Parameter Fsysadc Parameter Name System clock frequency when the ADC a module is operating (when PLL is bypassed). Min 15.9952 Nom 16 Max 16.0048 Unit MHz
a. Clock frequency (plus jitter) must be stable inside specified range. ADC can be clocked from the PLL, directly from an external clock source, or from the PIOSC, as long as frequency absolute precision is inside specified range.
23.8.7
System Clock Specification with USB Operation

Table 23-18. System Clock Characteristics with USB Operation
Parameter Fsysusb Parameter Name System clock frequency when the USB module is operating (note that MOSC must be the clock source, either with or without using the PLL) Min 20 Nom Max Unit MHz
April 25, 2012
23.9
Sleep Modes
Table 23-19. Sleep Modes AC Characteristics
Parameter No Parameter TWAKE_S
a
Parameter Name Time to wake from interrupt in sleep mode

b
Min -
Nom 1.25
Max 2 -
Unit system clocks s
D1 TWAKE_DS
Time to wake from interrupt in deep-sleep mode, using PIOSC for both Run mode and Deep-sleep bc mode Time to wake from interrupt in deep-sleep mode, using PIOSC for Run mode and IOSC for Deep-sleep bc mode mode
350
D2
TWAKE_PLL_DS Time to wake from interrupt in deep-sleep mode b when using the PLL
TREADY
ms
a. Values in this table assume the IOSC is the clock source during sleep or deep-sleep mode. b. Specified from registering the interrupt to first instruction. c. If the main oscillator is used for run mode, add the main oscillator startup time, TSTART.
23.10
Hibernation Module
The Hibernation module requires special system implementation considerations because it is intended to power down all other sections of its host device, refer to Hibernation Module on page 480. Table 23-20. Hibernation Module Battery Characteristics
Parameter Parameter Name VBAT Battery supply voltage Low battery detect voltage, VBATSEL=0x0 VLOWBAT Low battery detect voltage, VBATSEL=0x1 Low battery detect voltage, VBATSEL=0x2 Low battery detect voltage, VBATSEL=0x3 Min 1.8 1.8 2.0 2.2 2.4 Nominal 3.0 1.9 2.1 2.3 2.5 Max 3.6 2.0 2.2 2.4 2.6 Unit V V V V V
Table 23-21. Hibernation Module AC Characteristics

Parameter No H1 H2 H3 Parameter TWAKE TWAKE_TO_HIB TVDD_RAMP Parameter Name WAKE assertion time WAKE assert to HIB desassert (wake up time) VDD ramp to 3.0 V Min 100 Nom Depends on characteristics of power supply Max 1 Unit ns hibernation clock period s
H4
TVDD_CODE
VDD at 3.0 V to internal POR deassert; first instruction executes
500
1171
Figure 23-12. Hibernation Module Timing
H1
WAKE
H2
HIB
H3
VDD
H4
POR
23.11
Flash Memory and EEPROM

Table 23-22. Flash Memory Characteristics
Parameter PECYC TRET TPROG64 Parameter Name Number of guaranteed program/erase cycles before a failure Data retention, -40C to +85C Program time for double-word-aligned 64 bits of b data Page erase time, <1k cycles endurance Page erase time, 100k cycles endurance Mass erase time, <1k cycles endurance Mass erase time, 100k cycles endurance Min 100,000 10 30 2 70 Nom 50 25 200 Max 300 900 900 Unit cycles years s ms ms ms ms
TERASE TME
a. A program/erase cycle is defined as switching the bits from 1-> 0 -> 1. b. If programming fewer than 64 bits of data, the programming time is the same. For example, if only 32 bits of data need to be programmed, the other 32 bits are masked off.
Table 23-23. EEPROM Characteristics

Parameter Parameter Name EPECYC ETRET
Min
Nom -
Max -
Unit cycles years
Number of guaranteed mass program/erase cycles of a single 500,000 b word before failure Data retention, -40C to +85C 10
April 25, 2012
Table 23-23. EEPROM Characteristics (continued)

Parameter Parameter Name Program time for 32 bits of data - space available Program time for 32 bits of data - requires a copy to the copy buffer, copy buffer has space and less than 10% of EEPROM endurance used Program time for 32 bits of data - requires a copy to the copy buffer, copy buffer has space and greater than 90% of EEPROM endurance used Program time for 32 bits of data - requires a copy to the copy buffer, copy buffer requires an erase and less than 10% of EEPROM endurance used Program time for 32 bits of data - requires a copy to the copy buffer, copy buffer requires an erase and greater than 90% of EEPROM endurance used ETREAD ETME Read access time Mass erase time, <1k cycles endurance Mass erase time, 100k cycles endurance Min Nom 110 30 Max 600 Unit s ms
900
ms
ETPROG
60
ms
1800
ms
70 -
4 200 -
900
system clocks ms ms
a. Because the EEPROM operates as a background task and does not prevent the CPU from executing from Flash memory, the operation will complete within the maximum time specified provided the EEPROM operation is not stalled by a Flash memory program or erase operation. b. A program/erase cycle is defined as switching the bits from 1-> 0 -> 1.
23.12
Input/Output Characteristics
Note: All GPIOs are 5-V tolerant, except PB0 and PB1. See Signal Description on page 632 for more information on GPIO configuration.
ab
Table 23-24. GPIO Module Characteristics

Parameter Parameter Name RGPIOPU RGPIOPD GPIO internal pull-up resistor GPIO internal pull-down resistor
Min 13 13
c
Nom 20 20 14.2 11.9
Max 30 35 1.0 2.0 700 100 10 f
Unit k k A A A A A A A mA ns ns ns ns
GPIO input leakage current, 0 V VIN VDD GPIO pins ILKG+
GPIO input leakage current, 0 V < VIN VDD, GPIO pins configured as ADC or analog comparator inputs GPIO input leakage current, VDD< VIN 4.0 V
cd ce
GPIO input leakage current, 4.0 V < VIN 5.5 V ILKGIINJ+ IINJGPIO input leakage current, -0.3 V VIN < 0 V GPIO input leakage current, VIN < -0.3 V DC injection current, VDD < VIN 5.5 V DC injection current, VIN 0 V GPIO rise time, 2-mA drive TGPIOR GPIO rise time, 4-mA drive GPIO rise time, 8-mA drive
h h h g c c
ILKG+ 0.5 16.1 15.5 11.2 11.8
8.1 9.5
GPIO rise time, 8-mA drive with slew rate control
1173
Table 23-24. GPIO Module Characteristics (continued)

Parameter Parameter Name GPIO fall time, 2-mA drive TGPIOF GPIO fall time, 4-mA drive GPIO fall time, 8-mA drive
i i
Min
Nom 25.2 13.3
Max 29.4 16.8 11.2 12.9
Unit ns ns ns ns
i i
8.6 11.3
GPIO fall time, 8-mA drive with slew rate control
a. VDD must be within the range specified in Table 23-2 on page 1159. b. Leakage and Injection current characteristics specified in this table also apply to XOSC0 and XOSC1 inputs. c. The leakage current is measured with VIN applied to the corresponding pin(s). The leakage of digital port pins is measured individually. The port pin is configured as an input and the pullup/pulldown resistor is disabled. d. To protect internal circuitry from over-voltage, the GPIOs have an internal voltage clamp that limits internal swings to VDD without affecting swing at the I/O pad. This internal clamp starts turning on while VDD < VIN < 4.0 V and causes a somewhat larger (but bounded) current draw. To save power, static input voltages between VDD and 4 V should be avoided. e. Leakage current above maximum voltage (VIN = 5.5V) is not guaranteed, this condition is not allowed and can result in permanent damage to the device. f. In this case, ILKG- is unbounded and must be limited to IINJ- using an external resistor. g. Current injection is internally bounded for GPIOs, and maximum current into the pin is given by ILKG+ for VDD < VIN < 5.5 V. h. Time measured from 20% to 80% of VDD. i. Time measured from 80% to 20% of VDD.
23.13

Table 23-25. ADC Electrical Characteristics
Parameter Parameter Name POWER SUPPLY REQUIREMENTS VDDA GNDA ADC supply voltage ADC ground voltage 2.97 3.3 0
b
Min
Nom
Max
Unit
3.63 -
V V
VDDA / GNDA VOLTAGE REFERENCE CREF ANALOG INPUT Single-ended, full- scale analog input voltage, cd internal reference Differential, full-scale analog input voltage, ce internal reference Input common mode voltage, differential f mode ADC input leakage current
g g g
Voltage reference decoupling capacitance
1.0 // 0.01
0 -VDDA -
VDDA VDDA (VREFP + VREFN) / 2 25 2.0 2.5 10 500
V V mV
VADCIN
VINCM
IL RADC CADC RS FADC FCONV TS TC
A k pF
ADC equivalent input resistance

g
ADC equivalent input capacitance Analog source resistance
SAMPLING DYNAMICS ADC conversion clock frequency ADC conversion rate ADC sample time ADC conversion time 16 1 250 1 MHz MSPS ns s
April 25, 2012
Table 23-25. ADC Electrical Characteristics (continued)

Parameter TLT N INL DNL EO EG ET VTSENS STSENS ETSENS Parameter Name Latency from trigger to start of conversion Min Nom 2 Max Unit ADC clocks
SYSTEM PERFORMANCE when using internal reference Resolution Integral nonlinearity error, over full input range Differential nonlinearity error, over full input range Offset error Gain error
i j
12 1.5 0.8 5.0 10.0 10.0 3.0 1.0 15.0 30.0 30.0
bits LSB LSB LSB LSB LSB
Total unadjusted error, over full input range
TEMPERATURE SENSOR Temperature sensor voltage, junction temperature 25 C Temperature sensor slope, ambient temperature --40 C to 85 C Temperature sensor accuracy, ambient k temperature --40 C to 85 C 1.633 -13.3 5 V mV/C C
a. At ambient temperature= -40 C to 85 C, VREF+= 3.3V, FADC=16 MHz unless otherwise noted. b. Two capacitors in parallel. c. Internal reference is connected directly between VDDA and GNDA (VREFi = VDDA - GNDA). In this mode, EO, EG, ET, and dynamic specifications are adversely affected due to internal voltage drop and noise on VDDA and GNDA. d. VADCIN = VINP - VINN e. With signal common mode as VDDA/2. f. This parameter is defined as the average of the differential inputs. g. As shown in Figure 23-13 on page 1176, RADC is the total equivalent resistance in the input line all the way up to the sampling node at the input of the ADC. h. See System Clock Specification with ADC Operation on page 1170 for full ADC clock frequency specification. i. Gain error is measured at max code after compensating for offset. Gain error is equivalent to "Full Scale Error." It can be given in % of slope error, or in LSB, as done here. j. Total Unadjusted Error is the maximum error at any one code versus the ideal ADC curve. It includes all other errors (offset error, gain error and INL) at any given ADC code. k. Note that this parameter does not include ADC error.
1175
Figure 23-13. ADC Input Equivalency Diagram
Stellaris Microcontroller Zs Rs Pin

ESDclamps toGNDonly
ZADC RADC 12bit SARADC Converter 12bit Word
VS
Cs
VADCIN
5VESD Clamp
IL
Pin
RADC
Pin
RADC
CADC
23.14

Table 23-26. SSI Characteristics
Parameter No. S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 Parameter TCLK_PER TCLK_HIGH TCLK_LOW TCLKR TCLKF TDMD TDMS TDMH TDSS TDSH Parameter Name SSIClk cycle time SSIClk high time SSIClk low time SSIClk rise time SSIClk fall time
b b a
Min 40 0 1 2 1 2
Nom 0.5 0.5 8.1 8.6 -
Max 11.2 11.2 1 -
Unit ns t clk_per t clk_per ns ns system clocks system clocks system clocks system clocks system clocks
Data from master valid delay time Data from master setup time Data from master hold time Data from slave setup time Data from slave hold time
a. In master mode, the system clock must be at least twice as fast as the SSIClk; in slave mode, the system clock must be at least 6 times faster than the SSIClk. b. Note that the delays shown are using 8-mA drive strength.
April 25, 2012
Figure 23-14. SSI Timing for TI Frame Format (FRF=01), Single Transfer Timing Measurement
S1 S2 S5 S4
SSIClk
S3
SSIFss
SSITx SSIRx
MSB
4 to 16 bits
LSB
Figure 23-15. SSI Timing for MICROWIRE Frame Format (FRF=10), Single Transfer
S2 S1 S5 S4
SSIClk
S3
SSIFss
SSITx
MSB 8-bit control
LSB
SSIRx
MSB 4 to 16 bits output data
LSB
Figure 23-16. SSI Timing for SPI Frame Format (FRF=00), with SPH=1
S1 S5 S4 S2
SSIClk (SPO=1)
S3
SSIClk (SPO=0)
S7 S8
SSITx (master)
S6
MSB
S9 S10
LSB
SSIRx (slave)
MSB
LSB
SSIFss
1177
23.15

Table 23-27. I2C Characteristics
Parameter No. I1 I2 I3 I4
a a b
Parameter TSCH TLP TSRT TDH TSFT THT TDS TSCSR TSCS
Parameter Name Start condition hold time Clock Low period I2CSCL/I2CSDA rise time (VIL =0.5 V to V IH =2.4 V) Data hold time I2CSCL/I2CSDA fall time (VIH =2.4 V to V IL =0.5 V) Clock High time Data setup time Start condition setup time (for repeated start condition only) Stop condition setup time I2C
Min 36 36 2 24 18 36 24
Nom 9 -
Max (see note b) 10 -
Unit system clocks system clocks ns system clocks ns system clocks system clocks system clocks system clocks
a c
I5 I6 I7 I8 I9
a. Values depend on the value programmed into the TPR bit in the Master Timer Period (I2CMTPR) register; a TPR programmed for the maximum I2CSCL frequency (TPR=0x2) results in a minimum output timing as shown in the table above. The I 2C interface is designed to scale the actual data transition time to move it to the middle of the I2CSCL Low period. The actual position is affected by the value programmed into the TPR; however, the numbers given in the above values are minimum values. b. Because I2CSCL and I2CSDA operate as open-drain-type signals, which the controller can only actively drive Low, the time I2CSCL or I2CSDA takes to reach a high level depends on external signal capacitance and pull-up resistor values. c. Specified at a nominal 50 pF load.
Figure 23-17. I2C Timing

I2 I6 I5
I2CSCL
I1 I4 I7 I8 I3 I9
I2CSDA
23.16

The Stellaris USB controller electrical specifications are compliant with the Universal Serial Bus Specification Rev. 2.0 (full-speed and low-speed support). Some components of the USB system are integrated within the LM4F120H5QR microcontroller and specific to the Stellaris microcontroller design.
23.17
Analog Comparator
Table 23-28. Analog Comparator Characteristics
Parameter VINP,VINN VCM Parameter Name Input voltage range Input common mode voltage range Min GNDA GNDA Nom Max VDDA VDDA Unit V V
April 25, 2012
Table 23-28. Analog Comparator Characteristics (continued)

Parameter VOS IINP,IINN CMRR TRT TMC Parameter Name Input offset voltage Input leakage current over full voltage range Common mode rejection ratio Response time Comparator mode change to Output Valid Min Nom 10 50 Max 25
a
Unit mV A dB
2.0 1.0
b
s s
10
a. Measured at VREF=100 mV. b. Measured at external VREF=100 mV, input signal switching from 75 mV to 125 mV.
Table 23-29. Analog Comparator Voltage Reference Characteristics

Parameter RHR RLR AHR ALR Parameter Name Resolution in high range Resolution in low range Absolute accuracy high range Absolute accuracy low range Min Nom VDDA/29.4 VDDA/22.12 Max RHR/2 RLR/2 Unit V V V V
VREF Value 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF VIREF Min 0.731 0.843 0.955 1.067 1.180 1.292 1.404 1.516 1.629 1.741 1.853 1.965 2.078 2.190 2.302 2.414 Ideal VIREF 0.786 0.898 1.010 1.122 1.235 1.347 1.459 1.571 1.684 1.796 1.908 2.020 2.133 2.245 2.357 2.469 VIREF Max 0.841 0.953 1.065 1.178 1.290 1.402 1.514 1.627 1.739 1.851 1.963 2.076 2.188 2.300 2.412 2.525 Unit V V V V V V V V V V V V V V V V
VREF Value 0x0 0x1 0x2 0x3 VIREF Min 0.000 0.076 0.225 0.374 Ideal VIREF 0.000 0.149 0.298 0.448 VIREF Max 0.074 0.223 0.372 0.521 Unit V V V V
1179
Table 23-31. Analog Comparator Voltage Reference Characteristics, VDDA = 3.3V, EN= 1, and RNG = 1 (continued)
VREF Value 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF VIREF Min 0.523 0.672 0.822 0.971 1.120 1.269 1.418 1.567 1.717 1.866 2.015 2.164 Ideal VIREF 0.597 0.746 0.895 1.044 1.193 1.343 1.492 1.641 1.790 1.939 2.089 2.238 VIREF Max 0.670 0.820 0.969 1.118 1.267 1.416 1.565 1.715 1.864 2.013 2.162 2.311 Unit V V V V V V V V V V V V
23.18
23.18.1
Current Consumption
Preliminary Current Consumption
The following table provides preliminary figures for current consumption while ongoing characterization is completed. Table 23-32. Preliminary Current Consumption
Parameter Parameter Name Conditions Nom 50 Max Unit mA Run mode 1 (Flash loop) VDD = 3.3 V VDDA = 3.3 V Peripherals = All ON System Clock = 80 MHz (with PLL) Temp = 25C Run mode 1 (SRAM loop) VDD = 3.3 V VDDA = 3.3 V Peripherals = All ON System Clock = 80 MHz (with PLL) IDD_RUN Temp = 25C Run mode 2 (Flash loop) VDD = 3.3 V VDDA = 3.3 V Peripherals = All OFF System Clock = 80 MHz (with PLL) Temp = 25C Run mode 2 (SRAM loop) VDD = 3.3 V VDDA = 3.3 V Peripherals = All OFF System Clock = 80 MHz (with PLL) Temp = 25C 20 mA 30 mA 40 mA
April 25, 2012
Table 23-32. Preliminary Current Consumption (continued)

Parameter
a IDDA_RUN
Parameter Name Run mode
Conditions VDD = 3.6 V VDDA = 3.6 V Peripherals = All ON System Clock = 80 MHz (with PLL) Temp = 25C VDD = 3.3 V VDDA = 3.3 V Peripherals = All OFF System Clock = 80 MHz (with PLL) Temp = 25C VDD = 3.3 V VDDA = 3.3 V
Nom -
Max 4.5
Unit mA
12
mA
4.5
mA
IDD_SLEEP
Sleep mode
Peripherals = All OFF System Clock =16 MHz (with PIOSC) Temp = 25C VDD = 3.3 V VDDA = 3.3 V Peripherals = All OFF System Clock =1 MHz (with PIOSC/16) Temp = 25C
b b
3.8
mA
IDD_DEEPSLEEP Deep-sleep mode
VDD = 3.3 V VDDA = 3.3 V Peripherals = All OFF System Clock = IOSC30KHZ Temp = 25C
1.05
mA
IHIB_NORTC
Hibernate mode (external VBAT = 3.0 V wake, RTC disabled) VDD = 0 V VDDA = 0 V System Clock = OFF Hibernate Module = 32.768 kHz
1.6
IHIB_RTC
Hibernate mode (RTC enabled)
VBAT = 3.0 V VDD = 0 V VDDA = 0 V System Clock = OFF Hibernate Module = 32.768 kHz
1.7
IHIB_VDD3ON
Hibernate mode (VDD3ON mode)
VBAT = 3.0 V VDD = 3.3 V VDDA = 3.3 V System Clock = OFF Hibernate Module = 32.768 kHz
5.0
a. The value for IDDA_RUN is included in the above values for IDD_RUN. b. Note that if the MOSC is the source of the Run-mode system clock and is powered down in Sleep mode, wake time is increased by TMOSC_SETTLE.
1181
Register Quick Reference
A
31 15 30 14

29 13 28 12 27 11 26 10 25 9 24 8 23 7 22 6 21 5 20 4 19 3 18 2 17 1 16 0

R0, type R/W, , reset - (see page 73) DATA DATA R1, type R/W, , reset - (see page 73) DATA DATA R2, type R/W, , reset - (see page 73) DATA DATA R3, type R/W, , reset - (see page 73) DATA DATA R4, type R/W, , reset - (see page 73) DATA DATA R5, type R/W, , reset - (see page 73) DATA DATA R6, type R/W, , reset - (see page 73) DATA DATA R7, type R/W, , reset - (see page 73) DATA DATA R8, type R/W, , reset - (see page 73) DATA DATA R9, type R/W, , reset - (see page 73) DATA DATA R10, type R/W, , reset - (see page 73) DATA DATA R11, type R/W, , reset - (see page 73) DATA DATA R12, type R/W, , reset - (see page 73) DATA DATA SP, type R/W, , reset - (see page 74) SP SP LR, type R/W, , reset 0xFFFF.FFFF (see page 75) LINK LINK PC, type R/W, , reset - (see page 76) PC PC
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PSR, type R/W, , reset 0x0100.0000 (see page 77) N Z C ICI / IT PRIMASK, type R/W, , reset 0x0000.0000 (see page 81) V Q ICI / IT THUMB ISRNUM GE
PRIMASK FAULTMASK, type R/W, , reset 0x0000.0000 (see page 82)
FAULTMASK
BASEPRI, type R/W, , reset 0x0000.0000 (see page 83)
BASEPRI CONTROL, type R/W, , reset 0x0000.0000 (see page 84)
FPCA FPSC, type R/W, , reset - (see page 86) N Z C V AHP DN FZ RMODE IDC IXC UFC OFC
ASP
TMPL
DZC
IOC
Cortex-M4 Peripherals System Timer (SysTick) Registers

Base 0xE000.E000
STCTRL, type R/W, offset 0x010, reset 0x0000.0004 COUNT CLK_SRC STRELOAD, type R/W, offset 0x014, reset RELOAD RELOAD STCURRENT, type R/WC, offset 0x018, reset CURRENT CURRENT INTEN ENABLE
Cortex-M4 Peripherals Nested Vectored Interrupt Controller (NVIC) Registers

Base 0xE000.E000
EN0, type R/W, offset 0x100, reset 0x0000.0000 INT INT EN1, type R/W, offset 0x104, reset 0x0000.0000 INT INT EN2, type R/W, offset 0x108, reset 0x0000.0000 INT INT EN3, type R/W, offset 0x10C, reset 0x0000.0000 INT INT EN4, type R/W, offset 0x110, reset 0x0000.0000
INT DIS0, type R/W, offset 0x180, reset 0x0000.0000 INT INT
1183
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
DIS1, type R/W, offset 0x184, reset 0x0000.0000 INT INT DIS2, type R/W, offset 0x188, reset 0x0000.0000 INT INT DIS3, type R/W, offset 0x18C, reset 0x0000.0000 INT INT DIS4, type R/W, offset 0x190, reset 0x0000.0000
INT PEND0, type R/W, offset 0x200, reset 0x0000.0000 INT INT PEND1, type R/W, offset 0x204, reset 0x0000.0000 INT INT PEND2, type R/W, offset 0x208, reset 0x0000.0000 INT INT PEND3, type R/W, offset 0x20C, reset 0x0000.0000 INT INT PEND4, type R/W, offset 0x210, reset 0x0000.0000
INT UNPEND0, type R/W, offset 0x280, reset 0x0000.0000 INT INT UNPEND1, type R/W, offset 0x284, reset 0x0000.0000 INT INT UNPEND2, type R/W, offset 0x288, reset 0x0000.0000 INT INT UNPEND3, type R/W, offset 0x28C, reset 0x0000.0000 INT INT UNPEND4, type R/W, offset 0x290, reset 0x0000.0000
INT ACTIVE0, type RO, offset 0x300, reset 0x0000.0000 INT INT ACTIVE1, type RO, offset 0x304, reset 0x0000.0000 INT INT ACTIVE2, type RO, offset 0x308, reset 0x0000.0000 INT INT
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
ACTIVE3, type RO, offset 0x30C, reset 0x0000.0000 INT INT ACTIVE4, type RO, offset 0x310, reset 0x0000.0000
INT PRI0, type R/W, offset 0x400, reset 0x0000.0000 INTD INTB PRI1, type R/W, offset 0x404, reset 0x0000.0000 INTD INTB PRI2, type R/W, offset 0x408, reset 0x0000.0000 INTD INTB PRI3, type R/W, offset 0x40C, reset 0x0000.0000 INTD INTB PRI4, type R/W, offset 0x410, reset 0x0000.0000 INTD INTB PRI5, type R/W, offset 0x414, reset 0x0000.0000 INTD INTB PRI6, type R/W, offset 0x418, reset 0x0000.0000 INTD INTB PRI7, type R/W, offset 0x41C, reset 0x0000.0000 INTD INTB PRI8, type R/W, offset 0x420, reset 0x0000.0000 INTD INTB PRI9, type R/W, offset 0x424, reset 0x0000.0000 INTD INTB PRI10, type R/W, offset 0x428, reset 0x0000.0000 INTD INTB PRI11, type R/W, offset 0x42C, reset 0x0000.0000 INTD INTB PRI12, type R/W, offset 0x430, reset 0x0000.0000 INTD INTB PRI13, type R/W, offset 0x434, reset 0x0000.0000 INTD INTB PRI14, type R/W, offset 0x438, reset 0x0000.0000 INTD INTB INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA
1185
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PRI15, type R/W, offset 0x43C, reset 0x0000.0000 INTD INTB PRI16, type R/W, offset 0x440, reset 0x0000.0000 INTD INTB PRI17, type R/W, offset 0x444, reset 0x0000.0000 INTD INTB PRI18, type R/W, offset 0x448, reset 0x0000.0000 INTD INTB PRI19, type R/W, offset 0x44C, reset 0x0000.0000 INTD INTB PRI20, type R/W, offset 0x450, reset 0x0000.0000 INTD INTB PRI21, type R/W, offset 0x454, reset 0x0000.0000 INTD INTB PRI22, type R/W, offset 0x458, reset 0x0000.0000 INTD INTB PRI23, type R/W, offset 0x45C, reset 0x0000.0000 INTD INTB PRI24, type R/W, offset 0x460, reset 0x0000.0000 INTD INTB PRI25, type R/W, offset 0x464, reset 0x0000.0000 INTD INTB PRI26, type R/W, offset 0x468, reset 0x0000.0000 INTD INTB PRI27, type R/W, offset 0x46C, reset 0x0000.0000 INTD INTB PRI28, type R/W, offset 0x470, reset 0x0000.0000 INTD INTB PRI29, type R/W, offset 0x474, reset 0x0000.0000 INTD INTB PRI30, type R/W, offset 0x478, reset 0x0000.0000 INTD INTB PRI31, type R/W, offset 0x47C, reset 0x0000.0000 INTD INTB INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA INTC INTA
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PRI32, type R/W, offset 0x480, reset 0x0000.0000 INTD INTB PRI33, type R/W, offset 0x484, reset 0x0000.0000 INTD INTB PRI34, type R/W, offset 0x488, reset 0x0000.0000 INTD INTB SWTRIG, type WO, offset 0xF00, reset 0x0000.0000 INTC INTA INTC INTA INTC INTA
INTID
Cortex-M4 Peripherals System Control Block (SCB) Registers

Base 0xE000.E000
ACTLR, type R/W, offset 0x008, reset 0x0000.0000
DISOOFP DISFPCA CPUID, type RO, offset 0xD00, reset 0x410F.C241 IMP PARTNO INTCTRL, type R/W, offset 0xD04, reset 0x0000.0000 NMISET VECPEND PENDSV UNPENDSV PENDSTSET PENDSTCLR RETBASE ISRPRE ISRPEND VECACT VAR
DISFOLD DISWBUF DISMCYC
CON REV
VECPEND
VTABLE, type R/W, offset 0xD08, reset 0x0000.0000 BASE OFFSET APINT, type R/W, offset 0xD0C, reset 0xFA05.0000 VECTKEY
ENDIANESS
OFFSET
PRIGROUP
SYSRESREQ VECTCLRACT VECTRESET
SYSCTRL, type R/W, offset 0xD10, reset 0x0000.0000
SEVONPEND
SLEEPDEEP SLEEPEXIT
CFGCTRL, type R/W, offset 0xD14, reset 0x0000.0200
STKALIGN BFHFNMIGN
DIV0
UNALIGNED
MAINPEND
BASETHR
SYSPRI1, type R/W, offset 0xD18, reset 0x0000.0000 USAGE BUS SYSPRI2, type R/W, offset 0xD1C, reset 0x0000.0000 SVC MEM
SYSPRI3, type R/W, offset 0xD20, reset 0x0000.0000 TICK PENDSV DEBUG SYSHNDCTRL, type R/W, offset 0xD24, reset 0x0000.0000 USAGE SVC BUSP MEMP USAGEP TICK PNDSV MON SVCA USGA BUS BUSA MEM MEMA
FAULTSTAT, type R/W1C, offset 0xD28, reset 0x0000.0000 DIV0 BFARV BLSPERR BSTKE BUSTKE IMPRE PRECISE UNALIGN IBUS MMARV MLSPERR MSTKE NOCP MUSTKE INVPC INVSTAT DERR UNDEF IERR
1187
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
HFAULTSTAT, type R/W1C, offset 0xD2C, reset 0x0000.0000 DBG FORCED VECT MMADDR, type R/W, offset 0xD34, reset ADDR ADDR FAULTADDR, type R/W, offset 0xD38, reset ADDR ADDR
Cortex-M4 Peripherals Memory Protection Unit (MPU) Registers

Base 0xE000.E000
MPUTYPE, type RO, offset 0xD90, reset 0x0000.0800 IREGION DREGION MPUCTRL, type R/W, offset 0xD94, reset 0x0000.0000
SEPARATE
PRIVDEFEN HFNMIENA
ENABLE
MPUNUMBER, type R/W, offset 0xD98, reset 0x0000.0000
NUMBER MPUBASE, type R/W, offset 0xD9C, reset 0x0000.0000 ADDR ADDR MPUBASE1, type R/W, offset 0xDA4, reset 0x0000.0000 ADDR ADDR MPUBASE2, type R/W, offset 0xDAC, reset 0x0000.0000 ADDR ADDR MPUBASE3, type R/W, offset 0xDB4, reset 0x0000.0000 ADDR ADDR MPUATTR, type R/W, offset 0xDA0, reset 0x0000.0000 XN SRD MPUATTR1, type R/W, offset 0xDA8, reset 0x0000.0000 XN SRD MPUATTR2, type R/W, offset 0xDB0, reset 0x0000.0000 XN SRD MPUATTR3, type R/W, offset 0xDB8, reset 0x0000.0000 XN SRD AP TEX SIZE S C B ENABLE AP TEX SIZE S C B ENABLE AP TEX SIZE S C B ENABLE AP TEX SIZE S C B ENABLE VALID REGION VALID REGION VALID REGION VALID REGION
Cortex-M4 Peripherals Floating-Point Unit (FPU) Registers

Base 0xE000.E000
CPAC, type R/W, offset 0xD88, reset 0x0000.0000 CP11 CP10
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
FPCC, type R/W, offset 0xF34, reset 0xC000.0000 ASPEN LSPEN MONRDY FPCA, type R/W, offset 0xF38, reset ADDRESS ADDRESS FPDSC, type R/W, offset 0xF3C, reset 0x0000.0000 AHP DN FZ RMODE BFRDY MMRDY HFRDY THREAD USER LSPACT
System Control System Control Registers

Base 0x400F.E000
DID0, type RO, offset 0x000, reset VER MAJOR DID1, type RO, offset 0x004, reset VER PINCOUNT PBORCTL, type R/W, offset 0x030, reset 0x0000.0000 FAM TEMP PARTNO PKG ROHS QUAL CLASS MINOR
BORIOR RIS, type RO, offset 0x050, reset 0x0000.0000
MOSCPUPRIS USBPLLLRIS
PLLLRIS
MOFRIS
BORRIS
IMC, type R/W, offset 0x054, reset 0x0000.0000
MOSCPUPIM USBPLLLIM
PLLLIM
MOFIM
BORIM
MISC, type R/W1C, offset 0x058, reset 0x0000.0000
MOSCPUPMIS USBPLLLMIS
PLLLMIS
MOFMIS
BORMIS
RESC, type R/W, offset 0x05C, reset MOSCFAIL
WDT1 RCC, type R/W, offset 0x060, reset 0x0780.3D51 ACG PWRDN BYPASS SYSDIV XTAL
USESYSDIV
SW
WDT0
BOR
POR
EXT
OSCSRC
IOSCDIS MOSCDIS
GPIOHBCTL, type R/W, offset 0x06C, reset 0x0000.7E00
PORTF RCC2, type R/W, offset 0x070, reset 0x07C0.6810 USERCC2 DIV400
USBPWRDN
PORTE
PORTD
PORTC
PORTB
PORTA
SYSDIV2 PWRDN2 BYPASS2
SYSDIV2LSB
OSCSRC2
MOSCCTL, type R/W, offset 0x07C, reset 0x0000.0000
NOXTAL DSLPCLKCFG, type R/W, offset 0x144, reset 0x0780.0000 DSDIVORIDE DSOSCSRC SYSPROP, type RO, offset 0x14C, reset 0x0000.1D31
MOSCIM
CVAL
FPU
1189
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PIOSCCAL, type R/W, offset 0x150, reset 0x0000.0000 UTEN CAL PIOSCSTAT, type RO, offset 0x154, reset 0x0000.0040 DT RESULT PLLFREQ0, type RO, offset 0x160, reset 0x0000.0032 MFRAC MFRAC PLLFREQ1, type RO, offset 0x164, reset 0x0000.0001 MINT CT UPDATE UT
Q PLLSTAT, type RO, offset 0x168, reset 0x0000.0000
LOCK PPWD, type RO, offset 0x300, reset 0x0000.0003
P1 PPTIMER, type RO, offset 0x304, reset 0x0000.003F
P0
P5 PPGPIO, type RO, offset 0x308, reset 0x0000.003F
P4
P3
P2
P1
P0
P14
P13
P12
P11
P10
P9
P8
P7
P6
P5
P4
P3
P2
P1
P0
PPDMA, type RO, offset 0x30C, reset 0x0000.0001
P0 PPHIB, type RO, offset 0x314, reset 0x0000.0001
P0 PPUART, type RO, offset 0x318, reset 0x0000.00FF
P7 PPSSI, type RO, offset 0x31C, reset 0x0000.000F
P6
P5
P4
P3
P2
P1
P0
P3 PPI2C, type RO, offset 0x320, reset 0x0000.000F
P2
P1
P0
P5 PPUSB, type RO, offset 0x328, reset 0x0000.0001
P4
P3
P2
P1
P0
P0 PPCAN, type RO, offset 0x334, reset 0x0000.0001
P1 PPADC, type RO, offset 0x338, reset 0x0000.0003
P0
P1 PPACMP, type RO, offset 0x33C, reset 0x0000.0001
P0
P0
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PPPWM, type RO, offset 0x340, reset 0x0000.0000
P1 PPQEI, type RO, offset 0x344, reset 0x0000.0000
P0
P1 PPEEPROM, type RO, offset 0x358, reset 0x0000.0001
P0
P0 PPWTIMER, type RO, offset 0x35C, reset 0x0000.003F
P5 SRWD, type R/W, offset 0x500, reset 0x0000.0000
P4
P3
P2
P1
P0
R1 SRTIMER, type R/W, offset 0x504, reset 0x0000.0000
R0
R5 SRGPIO, type R/W, offset 0x508, reset 0x0000.0000
R4
R3
R2
R1
R0
R5 SRDMA, type R/W, offset 0x50C, reset 0x0000.0000
R4
R3
R2
R1
R0
R0 SRHIB, type R/W, offset 0x514, reset 0x0000.0000
R0 SRUART, type R/W, offset 0x518, reset 0x0000.0000
R7 SRSSI, type R/W, offset 0x51C, reset 0x0000.0000
R6
R5
R4
R3
R2
R1
R0
R3 SRI2C, type R/W, offset 0x520, reset 0x0000.0000
R2
R1
R0
R3 SRUSB, type R/W, offset 0x528, reset 0x0000.0000
R2
R1
R0
R0 SRCAN, type R/W, offset 0x534, reset 0x0000.0000
R0 SRADC, type R/W, offset 0x538, reset 0x0000.0000
R1 SRACMP, type R/W, offset 0x53C, reset 0x0000.0000
R0
R0 SREEPROM, type R/W, offset 0x558, reset 0x0000.0000
R0
1191
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
SRWTIMER, type R/W, offset 0x55C, reset 0x0000.0000
R5 RCGCWD, type R/W, offset 0x600, reset 0x0000.0000
R4
R3
R2
R1
R0
R1 RCGCTIMER, type R/W, offset 0x604, reset 0x0000.0000
R0
R5 RCGCGPIO, type R/W, offset 0x608, reset 0x0000.0000
R4
R3
R2
R1
R0
R5 RCGCDMA, type R/W, offset 0x60C, reset 0x0000.0000
R4
R3
R2
R1
R0
R0 RCGCHIB, type R/W, offset 0x614, reset 0x0000.0001
R0 RCGCUART, type R/W, offset 0x618, reset 0x0000.0000
R7 RCGCSSI, type R/W, offset 0x61C, reset 0x0000.0000
R6
R5
R4
R3
R2
R1
R0
R3 RCGCI2C, type R/W, offset 0x620, reset 0x0000.0000
R2
R1
R0
R3 RCGCUSB, type R/W, offset 0x628, reset 0x0000.0000
R2
R1
R0
R0 RCGCCAN, type R/W, offset 0x634, reset 0x0000.0000
R0 RCGCADC, type R/W, offset 0x638, reset 0x0000.0000
R1 RCGCACMP, type R/W, offset 0x63C, reset 0x0000.0000
R0
R0 RCGCEEPROM, type R/W, offset 0x658, reset 0x0000.0000
R0 RCGCWTIMER, type R/W, offset 0x65C, reset 0x0000.0000
R5 SCGCWD, type R/W, offset 0x700, reset 0x0000.0000
R4
R3
R2
R1
R0
S1 SCGCTIMER, type R/W, offset 0x704, reset 0x0000.0000
S0
S5
S4
S3
S2
S1
S0
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
SCGCGPIO, type R/W, offset 0x708, reset 0x0000.0000
S5 SCGCDMA, type R/W, offset 0x70C, reset 0x0000.0000
S4
S3
S2
S1
S0
S0 SCGCHIB, type R/W, offset 0x714, reset 0x0000.0001
S0 SCGCUART, type R/W, offset 0x718, reset 0x0000.0000
S7 SCGCSSI, type R/W, offset 0x71C, reset 0x0000.0000
S6
S5
S4
S3
S2
S1
S0
S3 SCGCI2C, type R/W, offset 0x720, reset 0x0000.0000
S2
S1
S0
S3 SCGCUSB, type R/W, offset 0x728, reset 0x0000.0000
S2
S1
S0
S0 SCGCCAN, type R/W, offset 0x734, reset 0x0000.0000
S0 SCGCADC, type R/W, offset 0x738, reset 0x0000.0000
S1 SCGCACMP, type R/W, offset 0x73C, reset 0x0000.0000
S0
S0 SCGCEEPROM, type R/W, offset 0x758, reset 0x0000.0000
S0 SCGCWTIMER, type R/W, offset 0x75C, reset 0x0000.0000
S5 DCGCWD, type R/W, offset 0x800, reset 0x0000.0000
S4
S3
S2
S1
S0
D1 DCGCTIMER, type R/W, offset 0x804, reset 0x0000.0000
D0
D5 DCGCGPIO, type R/W, offset 0x808, reset 0x0000.0000
D4
D3
D2
D1
D0
D5 DCGCDMA, type R/W, offset 0x80C, reset 0x0000.0000
D4
D3
D2
D1
D0
D0 DCGCHIB, type R/W, offset 0x814, reset 0x0000.0001
D0
1193
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
DCGCUART, type R/W, offset 0x818, reset 0x0000.0000
D7 DCGCSSI, type R/W, offset 0x81C, reset 0x0000.0000
D6
D5
D4
D3
D2
D1
D0
D3 DCGCI2C, type R/W, offset 0x820, reset 0x0000.0000
D2
D1
D0
D3 DCGCUSB, type R/W, offset 0x828, reset 0x0000.0000
D2
D1
D0
D0 DCGCCAN, type R/W, offset 0x834, reset 0x0000.0000
D0 DCGCADC, type R/W, offset 0x838, reset 0x0000.0000
D1 DCGCACMP, type R/W, offset 0x83C, reset 0x0000.0000
D0
D0 DCGCEEPROM, type R/W, offset 0x858, reset 0x0000.0000
D0 DCGCWTIMER, type R/W, offset 0x85C, reset 0x0000.0000
D5 PCWD, type R/W, offset 0x900, reset 0x0000.0003
D4
D3
D2
D1
D0
P1 PCTIMER, type R/W, offset 0x904, reset 0x0000.003F
P0
P5 PCGPIO, type R/W, offset 0x908, reset 0x0000.7FFF
P4
P3
P2
P1
P0
P5 PCDMA, type R/W, offset 0x90C, reset 0x0000.0001
P4
P3
P2
P1
P0
P0 PCHIB, type R/W, offset 0x914, reset 0x0000.0001
P0 PCUART, type R/W, offset 0x918, reset 0x0000.00FF
P7 PCSSI, type R/W, offset 0x91C, reset 0x0000.000F
P6
P5
P4
P3
P2
P1
P0
P3 PCI2C, type R/W, offset 0x920, reset 0x0000.003F
P2
P1
P0
P3
P2
P1
P0
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PCUSB, type R/W, offset 0x928, reset 0x0000.0001
P0 PCCAN, type R/W, offset 0x934, reset 0x0000.0003
P0 PCADC, type R/W, offset 0x938, reset 0x0000.0003
P1 PCACMP, type R/W, offset 0x93C, reset 0x0000.0001
P0
P0 PCEEPROM, type R/W, offset 0x958, reset 0x0000.0001
P0 PCWTIMER, type R/W, offset 0x95C, reset 0x0000.0000
P5 PRWD, type R/W, offset 0xA00, reset 0x0000.0000
P4
P3
P2
P1
P0
R1 PRTIMER, type R/W, offset 0xA04, reset 0x0000.0000
R0
R5 PRGPIO, type R/W, offset 0xA08, reset 0x0000.0000
R4
R3
R2
R1
R0
R5 PRDMA, type R/W, offset 0xA0C, reset 0x0000.0000
R4
R3
R2
R1
R0
R0 PRHIB, type R/W, offset 0xA14, reset 0x0000.0001
R0 PRUART, type R/W, offset 0xA18, reset 0x0000.0000
R7 PRSSI, type R/W, offset 0xA1C, reset 0x0000.0000
R6
R5
R4
R3
R2
R1
R0
R3 PRI2C, type R/W, offset 0xA20, reset 0x0000.0000
R2
R1
R0
R3 PRUSB, type R/W, offset 0xA28, reset 0x0000.0000
R2
R1
R0
R0 PRCAN, type R/W, offset 0xA34, reset 0x0000.0000
R0 PRADC, type R/W, offset 0xA38, reset 0x0000.0000
R1
R0
1195
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
PRACMP, type R/W, offset 0xA3C, reset 0x0000.0000
R0 PREEPROM, type R/W, offset 0xA58, reset 0x0000.0000
R0 PRWTIMER, type R/W, offset 0xA5C, reset 0x0000.0000
R5
R4
R3
R2
R1
R0
System Control System Control Legacy Registers

Base 0x400F.E000
DC0, type RO, offset 0x008, reset 0x007F.007F SRAMSZ FLASHSZ DC1, type RO, offset 0x010, reset 0x1103.2FFF WDT1 MINSYSDIV MAXADC1SPD CAN1 CAN0 MPU HIB PWM1 TEMPSNS PWM0 PLL WDT0 SWO ADC1 SWD ADC0 JTAG
MAXADC0SPD
DC2, type RO, offset 0x014, reset 0x030F.F037 EPI0 I2C1HS I2C1 I2C0HS I2S0 I2C0 COMP2 COMP1 QEI1 COMP0 QEI0 SSI1 SSI0 TIMER3 TIMER2 UART2 TIMER1 UART1 TIMER0 UART0
DC3, type RO, offset 0x018, reset 0xBFFF.0FC0 32KHZ

PWMFAULT
CCP5 C2O
CCP4
CCP3 C1O
CCP2
CCP1
CCP0 C0O
ADC0AIN7
ADC0AIN6
ADC0AIN5
ADC0AIN4
ADC0AIN3
ADC0AIN2
ADC0AIN1
ADC0AIN0
C2PLUS C2MINUS
C1PLUS C1MINUS
C0PLUS C0MINUS
PWM5
PWM4
PWM3
PWM2
PWM1
PWM0
DC4, type RO, offset 0x01C, reset 0x0004.F03F EPHY0 CCP7 CCP6 UDMA EMAC0 ROM E1588 GPIOJ GPIOH GPIOG GPIOF GPIOE GPIOD PICAL GPIOC GPIOB GPIOA
DC5, type RO, offset 0x020, reset 0x0000.0000

PWMFAULT3 PWMFAULT2 PWMFAULT1 PWMFAULT0
PWMEFLT PWMESYNC PWM7 PWM6 PWM5 PWM4 PWM3 PWM2 PWM1 PWM0
DC6, type RO, offset 0x024, reset 0x0000.0011
USB0PHY DC7, type RO, offset 0x028, reset 0xFFFF.FFFF
USB0
DMACH30 DMACH29 DMACH28 DMACH27 DMACH26 DMACH25 DMACH24 DMACH23 DMACH22 DMACH21 DMACH20 DMACH19 DMACH18 DMACH17 DMACH16 DMACH15 DMACH14 DMACH13 DMACH12 DMACH11 DMACH10 DMACH9 DMACH8 DMACH7 DMACH6 DMACH5 DMACH4 DMACH3 DMACH2 DMACH1 DMACH0 DC8, type RO, offset 0x02C, reset 0x0FFF.0FFF
ADC1AIN15 ADC1AIN14 ADC1AIN13 ADC1AIN12 ADC1AIN11 ADC1AIN10 ADC1AIN9 ADC0AIN15 ADC0AIN14 ADC0AIN13 ADC0AIN12 ADC0AIN11 ADC0AIN10 ADC0AIN9 ADC1AIN8 ADC0AIN8 ADC1AIN7 ADC0AIN7 ADC1AIN6 ADC0AIN6 ADC1AIN5 ADC0AIN5 ADC1AIN4 ADC0AIN4 ADC1AIN3 ADC0AIN3 ADC1AIN2 ADC0AIN2 ADC1AIN1 ADC0AIN1 ADC1AIN0 ADC0AIN0
SRCR0, type RO, offset 0x040, reset 0x0000.0000 WDT1 CAN0 HIB SRCR1, type RO, offset 0x044, reset 0x0000.0000 COMP1 I2C1 I2C0 COMP0 SSI1 SSI0 TIMER3 TIMER2 UART2 TIMER1 UART1 TIMER0 UART0 WDT0 ADC1 ADC0
SRCR2, type RO, offset 0x048, reset 0x0000.0000 USB0 UDMA RCGC0, type RO, offset 0x100, reset 0x0000.0040 WDT1 MAXADC1SPD CAN0 MAXADC0SPD HIB WDT0 ADC1 ADC0 GPIOF GPIOE GPIOD GPIOC GPIOB GPIOA
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
RCGC1, type RO, offset 0x104, reset 0x0000.0000 COMP1 I2C1 I2C0 COMP0 SSI1 SSI0 TIMER3 TIMER2 UART2 TIMER1 UART1 TIMER0 UART0
RCGC2, type RO, offset 0x108, reset 0x0000.0000 USB0 UDMA SCGC0, type RO, offset 0x110, reset 0x0000.0040 WDT1 CAN0 HIB SCGC1, type RO, offset 0x114, reset 0x0000.0000 COMP1 I2C1 I2C0 COMP0 SSI1 SSI0 TIMER3 TIMER2 UART2 TIMER1 UART1 TIMER0 UART0 WDT0 ADC1 ADC0 GPIOF GPIOE GPIOD GPIOC GPIOB GPIOA
SCGC2, type RO, offset 0x118, reset 0x0000.0000 USB0 UDMA DCGC0, type RO, offset 0x120, reset 0x0000.0040 WDT1 CAN0 HIB DCGC1, type RO, offset 0x124, reset 0x0000.0000 COMP1 I2C1 I2C0 COMP0 SSI1 SSI0 TIMER3 TIMER2 UART2 TIMER1 UART1 TIMER0 UART0 WDT0 ADC1 ADC0 GPIOF GPIOE GPIOD GPIOC GPIOB GPIOA
DCGC2, type RO, offset 0x128, reset 0x0000.0000 USB0 UDMA DC9, type RO, offset 0x190, reset 0x00FF.00FF ADC1DC7 ADC1DC6 ADC1DC5 ADC1DC4 ADC1DC3 ADC1DC2 ADC1DC1 ADC1DC0 ADC0DC7 ADC0DC6 ADC0DC5 ADC0DC4 ADC0DC3 ADC0DC2 ADC0DC1 ADC0DC0 NVMSTAT, type RO, offset 0x1A0, reset 0x0000.0001 GPIOF GPIOE GPIOD GPIOC GPIOB GPIOA
FWB

Base 0x400F.9000
SYSEXCRIS, type RO, offset 0x000, reset 0x0000.0000 (see page 473)
FPIXCRIS
FPOFCRIS
FPUFCRIS
FPIOCRIS
FPDZCRIS
FPIDCRIS
SYSEXCIM, type R/W, offset 0x004, reset 0x0000.0000 (see page 475)
FPIXCIM FPOFCIM FPUFCIM FPIOCIM FPDZCIM FPIDCIM SYSEXCMIS, type RO, offset 0x008, reset 0x0000.0000 (see page 477)
FPIXCMIS
FPOFCMIS FPUFCMIS
FPIOCMIS
FPDZCMIS
FPIDCMIS
SYSEXCIC, type W1C, offset 0x00C, reset 0x0000.0000 (see page 479)
FPIXCIC FPOFCIC FPUFCIC FPIOCIC FPDZCIC FPIDCIC
Hibernation Module
Base 0x400F.C000
HIBRTCC, type RO, offset 0x000, reset 0x0000.0000 (see page 493) RTCC RTCC HIBRTCM0, type R/W, offset 0x004, reset 0xFFFF.FFFF (see page 494) RTCM0 RTCM0
1197
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
HIBRTCLD, type R/W, offset 0x00C, reset 0x0000.0000 (see page 495) RTCLD RTCLD HIBCTL, type R/W, offset 0x010, reset 0x8000.2000 (see page 496) WRC VBATSEL BATCHK BATWKEN VDD3ON VABORT CLK32EN PINWEN RTCWEN OSCHYS OSCDRV OSCBYP HIBREQ RTCEN
HIBIM, type R/W, offset 0x014, reset 0x0000.0000 (see page 500)
WC HIBRIS, type RO, offset 0x018, reset 0x0000.0000 (see page 502)
EXTW
LOWBAT
RTCALT0
WC HIBMIS, type RO, offset 0x01C, reset 0x0000.0000 (see page 504)
EXTW
LOWBAT
RTCALT0
WC HIBIC, type R/W1C, offset 0x020, reset 0x0000.0000 (see page 506)
EXTW
LOWBAT
RTCALT0
WC HIBRTCT, type R/W, offset 0x024, reset 0x0000.7FFF (see page 507)
EXTW
LOWBAT
RTCALT0
TRIM HIBRTCSS, type R/W, offset 0x028, reset 0x0000.0000 (see page 508) RTCSSM RTCSSC HIBDATA, type R/W, offset 0x030-0x06F, reset - (see page 509) RTD RTD
Internal Memory Flash Memory Registers (Flash Control Offset)

Base 0x400F.D000
FMA, type R/W, offset 0x000, reset 0x0000.0000 OFFSET OFFSET FMD, type R/W, offset 0x004, reset 0x0000.0000 DATA DATA FMC, type R/W, offset 0x008, reset 0x0000.0000 WRKEY COMT FCRIS, type RO, offset 0x00C, reset 0x0000.0000 MERASE ERASE WRITE
PROGRIS
ERRIS
INVDRIS VOLTRIS
ERIS
PRIS
ARIS
FCIM, type R/W, offset 0x010, reset 0x0000.0000
PROGMASK
ERMASK INVDMASK VOLTMASK
EMASK
PMASK
AMASK
FCMISC, type R/W1C, offset 0x014, reset 0x0000.0000
PROGMISC
ERMISC
INVDMISC
VOLTMISC
EMISC
PMISC
AMISC
FMC2, type R/W, offset 0x020, reset 0x0000.0000 WRKEY WRBUF
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
FWBVAL, type R/W, offset 0x030, reset 0x0000.0000 FWB[n] FWB[n] FWBn, type R/W, offset 0x100 - 0x17C, reset 0x0000.0000 DATA DATA FSIZE, type RO, offset 0xFC0, reset 0x0000.007F
SIZE SSIZE, type RO, offset 0xFC4, reset 0x0000.007F
SIZE ROMSWMAP, type RO, offset 0xFCC, reset 0x0000.0000
SAFERTOS
Internal Memory EEPROM Registers (EEPROM Control Offset)

Base 0x400A.F000
EESIZE, type RO, offset 0x000, reset 0x0020.0200 BLKCNT WORDCNT EEBLOCK, type R/W, offset 0x004, reset 0x0000.0000
BLOCK EEOFFSET, type R/W, offset 0x008, reset 0x0000.0000
OFFSET EERDWR, type R/W, offset 0x010, reset VALUE VALUE EERDWRINC, type R/W, offset 0x014, reset VALUE VALUE EEDONE, type RO, offset 0x018, reset 0x0000.0000
INVPL EESUPP, type R/W, offset 0x01C, reset -
WRBUSY NOPERM WKCOPY WKERASE
WORKING
PRETRY EEUNLOCK, type R/W, offset 0x020, reset UNLOCK UNLOCK EEPROT, type R/W, offset 0x030, reset 0x0000.0000
ERETRY
EREQ
START
ACC EEPASS0, type R/W, offset 0x034, reset PASS PASS EEPASS1, type R/W, offset 0x038, reset PASS PASS
PROT
1199
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
EEPASS2, type R/W, offset 0x03C, reset PASS PASS EEINT, type R/W, offset 0x040, reset 0x0000.0000
INT EEHIDE, type R/W, offset 0x050, reset 0x0000.0000 Hn Hn EEDBGME, type R/W, offset 0x080, reset 0x0000.0000 KEY ME EEPROMPP, type RO, offset 0xFC0, reset 0x0000.001F
SIZE
Internal Memory Memory Registers (System Control Offset)

Base 0x400F.E000
RMCTL, type R/W1C, offset 0x0F0, reset -
BA FMPRE0, type R/W, offset 0x130 and 0x200, reset 0xFFFF.FFFF READ_ENABLE READ_ENABLE FMPRE1, type R/W, offset 0x204, reset 0xFFFF.FFFF READ_ENABLE READ_ENABLE FMPRE2, type R/W, offset 0x208, reset 0xFFFF.FFFF READ_ENABLE READ_ENABLE FMPRE3, type R/W, offset 0x20C, reset 0xFFFF.FFFF READ_ENABLE READ_ENABLE FMPPE0, type R/W, offset 0x134 and 0x400, reset 0xFFFF.FFFF PROG_ENABLE PROG_ENABLE FMPPE1, type R/W, offset 0x404, reset 0xFFFF.FFFF PROG_ENABLE PROG_ENABLE FMPPE2, type R/W, offset 0x408, reset 0xFFFF.FFFF PROG_ENABLE PROG_ENABLE FMPPE3, type R/W, offset 0x40C, reset 0xFFFF.FFFF PROG_ENABLE PROG_ENABLE BOOTCFG, type RO, offset 0x1D0, reset 0xFFFF.FFFE NW PORT PIN POL EN DBG1 DBG0
USER_REG0, type R/W, offset 0x1E0, reset 0xFFFF.FFFF DATA DATA
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
USER_REG1, type R/W, offset 0x1E4, reset 0xFFFF.FFFF DATA DATA USER_REG2, type R/W, offset 0x1E8, reset 0xFFFF.FFFF DATA DATA USER_REG3, type R/W, offset 0x1EC, reset 0xFFFF.FFFF DATA DATA
Micro Direct Memory Access (DMA) DMA Channel Control Structure (Offset from Channel Control Table Base)
Base n/a
DMASRCENDP, type R/W, offset 0x000, reset ADDR ADDR DMADSTENDP, type R/W, offset 0x004, reset ADDR ADDR DMACHCTL, type R/W, offset 0x008, reset DSTINC ARBSIZE DSTSIZE SRCINC SRCSIZE XFERSIZE
NXTUSEBURST
ARBSIZE XFERMODE
Micro Direct Memory Access (DMA) DMA Registers (Offset from DMA Base Address)
Base 0x400F.F000
DMASTAT, type RO, offset 0x000, reset 0x001F.0000 DMACHANS STATE DMACFG, type WO, offset 0x004, reset MASTEN
MASTEN DMACTLBASE, type R/W, offset 0x008, reset 0x0000.0000 ADDR ADDR DMAALTBASE, type RO, offset 0x00C, reset 0x0000.0200 ADDR ADDR DMAWAITSTAT, type RO, offset 0x010, reset 0xFFFF.FFC0 WAITREQ[n] WAITREQ[n] DMASWREQ, type WO, offset 0x014, reset SWREQ[n] SWREQ[n] DMAUSEBURSTSET, type R/W, offset 0x018, reset 0x0000.0000 SET[n] SET[n] DMAUSEBURSTCLR, type WO, offset 0x01C, reset CLR[n] CLR[n] DMAREQMASKSET, type R/W, offset 0x020, reset 0x0000.0000 SET[n] SET[n]
1201
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
DMAREQMASKCLR, type WO, offset 0x024, reset CLR[n] CLR[n] DMAENASET, type R/W, offset 0x028, reset 0x0000.0000 SET[n] SET[n] DMAENACLR, type WO, offset 0x02C, reset CLR[n] CLR[n] DMAALTSET, type R/W, offset 0x030, reset 0x0000.0000 SET[n] SET[n] DMAALTCLR, type WO, offset 0x034, reset CLR[n] CLR[n] DMAPRIOSET, type R/W, offset 0x038, reset 0x0000.0000 SET[n] SET[n] DMAPRIOCLR, type WO, offset 0x03C, reset CLR[n] CLR[n] DMAERRCLR, type R/W, offset 0x04C, reset 0x0000.0000
ERRCLR DMACHASGN, type R/W, offset 0x500, reset 0x0000.0000 CHASGN[n] CHASGN[n] DMACHIS, type R/W1C, offset 0x504, reset 0x0000.0000 CHIS[n] CHIS[n] DMACHMAP0, type R/W, offset 0x510, reset 0x0000.0000 CH7SEL CH3SEL DMACHMAP1, type R/W, offset 0x514, reset 0x0000.0000 CH15SEL CH11SEL DMACHMAP2, type R/W, offset 0x518, reset 0x0000.0000 CH23SEL CH19SEL DMACHMAP3, type R/W, offset 0x51C, reset 0x0000.0000 CH31SEL CH27SEL DMAPeriphID0, type RO, offset 0xFE0, reset 0x0000.0030 CH30SEL CH26SEL CH29SEL CH25SEL CH28SEL CH24SEL CH22SEL CH18SEL CH21SEL CH17SEL CH20SEL CH16SEL CH14SEL CH10SEL CH13SEL CH9SEL CH12SEL CH8SEL CH6SEL CH2SEL CH5SEL CH1SEL CH4SEL CH0SEL
PID0 DMAPeriphID1, type RO, offset 0xFE4, reset 0x0000.00B2
PID1 DMAPeriphID2, type RO, offset 0xFE8, reset 0x0000.000B
PID2
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
DMAPeriphID3, type RO, offset 0xFEC, reset 0x0000.0000
PID3 DMAPeriphID4, type RO, offset 0xFD0, reset 0x0000.0004
PID4 DMAPCellID0, type RO, offset 0xFF0, reset 0x0000.000D
CID0 DMAPCellID1, type RO, offset 0xFF4, reset 0x0000.00F0
CID1 DMAPCellID2, type RO, offset 0xFF8, reset 0x0000.0005
CID2 DMAPCellID3, type RO, offset 0xFFC, reset 0x0000.00B1
CID3

GPIO Port A (APB) base: 0x4000.4000 GPIO Port A (AHB) base: 0x4005.8000 GPIO Port B (APB) base: 0x4000.5000 GPIO Port B (AHB) base: 0x4005.9000 GPIO Port C (APB) base: 0x4000.6000 GPIO Port C (AHB) base: 0x4005.A000 GPIO Port D (APB) base: 0x4000.7000 GPIO Port D (AHB) base: 0x4005.B000 GPIO Port E (APB) base: 0x4002.4000 GPIO Port E (AHB) base: 0x4005.C000 GPIO Port F (APB) base: 0x4002.5000 GPIO Port F (AHB) base: 0x4005.D000
GPIODATA, type R/W, offset 0x000, reset 0x0000.0000 (see page 644)
DATA GPIODIR, type R/W, offset 0x400, reset 0x0000.0000 (see page 645)
DIR GPIOIS, type R/W, offset 0x404, reset 0x0000.0000 (see page 646)
IS GPIOIBE, type R/W, offset 0x408, reset 0x0000.0000 (see page 647)
IBE GPIOIEV, type R/W, offset 0x40C, reset 0x0000.0000 (see page 648)
IEV GPIOIM, type R/W, offset 0x410, reset 0x0000.0000 (see page 649)
IME GPIORIS, type RO, offset 0x414, reset 0x0000.0000 (see page 650)
RIS GPIOMIS, type RO, offset 0x418, reset 0x0000.0000 (see page 651)
MIS
1203
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
GPIOICR, type W1C, offset 0x41C, reset 0x0000.0000 (see page 652)
IC GPIOAFSEL, type R/W, offset 0x420, reset - (see page 653)
AFSEL GPIODR2R, type R/W, offset 0x500, reset 0x0000.00FF (see page 655)
DRV2 GPIODR4R, type R/W, offset 0x504, reset 0x0000.0000 (see page 656)
DRV4 GPIODR8R, type R/W, offset 0x508, reset 0x0000.0000 (see page 657)
DRV8 GPIOODR, type R/W, offset 0x50C, reset 0x0000.0000 (see page 658)
ODE GPIOPUR, type R/W, offset 0x510, reset - (see page 659)
PUE GPIOPDR, type R/W, offset 0x514, reset 0x0000.0000 (see page 661)
PDE GPIOSLR, type R/W, offset 0x518, reset 0x0000.0000 (see page 663)
SRL GPIODEN, type R/W, offset 0x51C, reset - (see page 664)
DEN GPIOLOCK, type R/W, offset 0x520, reset 0x0000.0001 (see page 666) LOCK LOCK GPIOCR, type -, offset 0x524, reset - (see page 667)
CR GPIOAMSEL, type R/W, offset 0x528, reset 0x0000.0000 (see page 669)
GPIOAMSEL GPIOPCTL, type R/W, offset 0x52C, reset - (see page 670) PMC7 PMC3 PMC6 PMC2 PMC5 PMC1 PMC4 PMC0
GPIOADCCTL, type R/W, offset 0x530, reset 0x0000.0000 (see page 672)
ADCEN GPIODMACTL, type R/W, offset 0x534, reset 0x0000.0000 (see page 673)
DMAEN GPIOPeriphID4, type RO, offset 0xFD0, reset 0x0000.0000 (see page 674)
PID4
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
GPIOPeriphID5, type RO, offset 0xFD4, reset 0x0000.0000 (see page 675)
PID5 GPIOPeriphID6, type RO, offset 0xFD8, reset 0x0000.0000 (see page 676)
PID6 GPIOPeriphID7, type RO, offset 0xFDC, reset 0x0000.0000 (see page 677)
PID7 GPIOPeriphID0, type RO, offset 0xFE0, reset 0x0000.0061 (see page 678)
PID2 GPIOPeriphID3, type RO, offset 0xFEC, reset 0x0000.0001 (see page 681)
PID3 GPIOPCellID0, type RO, offset 0xFF0, reset 0x0000.000D (see page 682)
CID0 GPIOPCellID1, type RO, offset 0xFF4, reset 0x0000.00F0 (see page 683)
CID1 GPIOPCellID2, type RO, offset 0xFF8, reset 0x0000.0005 (see page 684)
CID2 GPIOPCellID3, type RO, offset 0xFFC, reset 0x0000.00B1 (see page 685)
CID3
16/32-bit Timer 0 base: 0x4003.0000 16/32-bit Timer 1 base: 0x4003.1000 16/32-bit Timer 2 base: 0x4003.2000 16/32-bit Timer 3 base: 0x4003.3000 16/32-bit Timer 4 base: 0x4003.4000 16/32-bit Timer 5 base: 0x4003.5000 32/64-bit Wide Timer 0 base: 0x4003.6000 32/64-bit Wide Timer 1 base: 0x4003.7000 32/64-bit Wide Timer 2 base: 0x4004.C000 32/64-bit Wide Timer 3 base: 0x4004.D000 32/64-bit Wide Timer 4 base: 0x4004.E000 32/64-bit Wide Timer 5 base: 0x4004.F000
GPTMCFG, type R/W, offset 0x000, reset 0x0000.0000 (see page 709)
GPTMCFG GPTMTAMR, type R/W, offset 0x004, reset 0x0000.0000 (see page 711)
TAPLO
TAMRSU TAPWMIE
TAILD
TASNAPS
TAWOT
TAMIE
TACDIR
TAAMS
TACMR
TAMR
GPTMTBMR, type R/W, offset 0x008, reset 0x0000.0000 (see page 715)
TBPLO
TBMRSU TBPWMIE
TBILD
TBSNAPS
TBWOT
TBMIE
TBCDIR
TBAMS
TBCMR
TBMR
1205
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
GPTMCTL, type R/W, offset 0x00C, reset 0x0000.0000 (see page 719)
TBPWML
TBOTE
TBEVENT
TBSTALL
TBEN
TAPWML
TAOTE
RTCEN
TAEVENT
TASTALL
TAEN
GPTMSYNC, type R/W, offset 0x010, reset 0x0000.0000 (see page 723) SYNCWT5 SYNCWT1 SYNCWT0 SYNCT5 SYNCT4 SYNCT3 SYNCWT4 SYNCT2 SYNCWT3 SYNCT1 SYNCWT2 SYNCT0
GPTMIMR, type R/W, offset 0x018, reset 0x0000.0000 (see page 727) WUEIM TBMIM CBEIM CBMIM TBTOIM TAMIM RTCIM CAEIM CAMIM TATOIM
GPTMRIS, type RO, offset 0x01C, reset 0x0000.0000 (see page 730) WUERIS TBMRIS CBERIS CBMRIS TBTORIS TAMRIS RTCRIS CAERIS CAMRIS TATORIS
GPTMMIS, type RO, offset 0x020, reset 0x0000.0000 (see page 733) WUEMIS TBMMIS CBEMIS CBMMIS TBTOMIS TAMMIS RTCMIS CAEMIS CAMMIS TATOMIS
GPTMICR, type W1C, offset 0x024, reset 0x0000.0000 (see page 736) WUECINT TBMCINT CBECINT CBMCINT TBTOCINT GPTMTAILR, type R/W, offset 0x028, reset 0xFFFF.FFFF (see page 738) TAILR TAILR GPTMTBILR, type R/W, offset 0x02C, reset - (see page 739) TBILR TBILR GPTMTAMATCHR, type R/W, offset 0x030, reset 0xFFFF.FFFF (see page 740) TAMR TAMR GPTMTBMATCHR, type R/W, offset 0x034, reset - (see page 741) TBMR TBMR GPTMTAPR, type R/W, offset 0x038, reset 0x0000.0000 (see page 742) TAMCINT RTCCINT CAECINT CAMCINT TATOCINT
TAPSRH GPTMTBPR, type R/W, offset 0x03C, reset 0x0000.0000 (see page 743)
TAPSR
TBPSRH GPTMTAPMR, type R/W, offset 0x040, reset 0x0000.0000 (see page 744)
TBPSR
TAPSMRH GPTMTBPMR, type R/W, offset 0x044, reset 0x0000.0000 (see page 745)
TAPSMR
TBPSMRH GPTMTAR, type RO, offset 0x048, reset 0xFFFF.FFFF (see page 746) TAR TAR GPTMTBR, type RO, offset 0x04C, reset - (see page 747) TBR TBR GPTMTAV, type RW, offset 0x050, reset 0xFFFF.FFFF (see page 748) TAV TAV
TBPSMR
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
GPTMTBV, type RW, offset 0x054, reset - (see page 749) TBV TBV GPTMRTCPD, type RO, offset 0x058, reset 0x0000.7FFF (see page 750)
RTCPD GPTMTAPS, type RO, offset 0x05C, reset 0x0000.0000 (see page 751)
PSS GPTMTBPS, type RO, offset 0x060, reset 0x0000.0000 (see page 752)
PSS GPTMTAPV, type RO, offset 0x064, reset 0x0000.0000 (see page 753)
PSV GPTMTBPV, type RO, offset 0x068, reset 0x0000.0000 (see page 754)
PSV GPTMPP, type RO, offset 0xFC0, reset 0x0000.0000 (see page 755)
SIZE
Watchdog Timers
WDT0 base: 0x4000.0000 WDT1 base: 0x4000.1000
WDTLOAD, type R/W, offset 0x000, reset 0xFFFF.FFFF (see page 760) WDTLOAD WDTLOAD WDTVALUE, type RO, offset 0x004, reset 0xFFFF.FFFF (see page 761) WDTVALUE WDTVALUE WDTCTL, type R/W, offset 0x008, reset 0x0000.0000 (WDT0) and 0x8000.0000 (WDT1) (see page 762) WRC INTTYPE WDTICR, type WO, offset 0x00C, reset - (see page 764) WDTINTCLR WDTINTCLR WDTRIS, type RO, offset 0x010, reset 0x0000.0000 (see page 765) RESEN INTEN
WDTRIS WDTMIS, type RO, offset 0x014, reset 0x0000.0000 (see page 766)
WDTMIS WDTTEST, type R/W, offset 0x418, reset 0x0000.0000 (see page 767)
STALL WDTLOCK, type R/W, offset 0xC00, reset 0x0000.0000 (see page 768) WDTLOCK WDTLOCK WDTPeriphID4, type RO, offset 0xFD0, reset 0x0000.0000 (see page 769)
PID4
1207
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
WDTPeriphID5, type RO, offset 0xFD4, reset 0x0000.0000 (see page 770)
PID5 WDTPeriphID6, type RO, offset 0xFD8, reset 0x0000.0000 (see page 771)
PID6 WDTPeriphID7, type RO, offset 0xFDC, reset 0x0000.0000 (see page 772)
PID7 WDTPeriphID0, type RO, offset 0xFE0, reset 0x0000.0005 (see page 773)
PID2 WDTPeriphID3, type RO, offset 0xFEC, reset 0x0000.0001 (see page 776)
PID3 WDTPCellID0, type RO, offset 0xFF0, reset 0x0000.000D (see page 777)
CID0 WDTPCellID1, type RO, offset 0xFF4, reset 0x0000.00F0 (see page 778)
CID1 WDTPCellID2, type RO, offset 0xFF8, reset 0x0000.0006 (see page 779)
CID2 WDTPCellID3, type RO, offset 0xFFC, reset 0x0000.00B1 (see page 780)
CID3

ADC0 base: 0x4003.8000 ADC1 base: 0x4003.9000
ADCACTSS, type R/W, offset 0x000, reset 0x0000.0000 (see page 802)
ASEN3 ADCRIS, type RO, offset 0x004, reset 0x0000.0000 (see page 803)
ASEN2
ASEN1
ASEN0
INRDC INR3 ADCIM, type R/W, offset 0x008, reset 0x0000.0000 (see page 805) DCONSS3 DCONSS2 DCONSS1 DCONSS0 MASK3 ADCISC, type R/W1C, offset 0x00C, reset 0x0000.0000 (see page 807) DCINSS3 DCINSS2 DCINSS1 DCINSS0 IN3 ADCOSTAT, type R/W1C, offset 0x010, reset 0x0000.0000 (see page 810) IN2 IN1 IN0 MASK2 MASK1 MASK0 INR2 INR1 INR0
OV3
OV2
OV1
OV0
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
ADCEMUX, type R/W, offset 0x014, reset 0x0000.0000 (see page 812)
EM3
EM2
EM1
EM0
ADCUSTAT, type R/W1C, offset 0x018, reset 0x0000.0000 (see page 817)
UV3 ADCSSPRI, type R/W, offset 0x020, reset 0x0000.3210 (see page 818)
UV2
UV1
UV0
SS3 ADCSPC, type R/W, offset 0x024, reset 0x0000.0000 (see page 820)
SS2
SS1
SS0
PHASE ADCPSSI, type R/W, offset 0x028, reset - (see page 822) GSYNC
SYNCWAIT
SS3 ADCSAC, type R/W, offset 0x030, reset 0x0000.0000 (see page 824)
SS2
SS1
SS0
AVG ADCDCISC, type R/W1C, offset 0x034, reset 0x0000.0000 (see page 825)
DCINT7 ADCSSMUX0, type R/W, offset 0x040, reset 0x0000.0000 (see page 827) MUX7 MUX3 MUX6 MUX2
DCINT6
DCINT5
DCINT4
DCINT3
DCINT2
DCINT1
DCINT0
MUX5 MUX1
MUX4 MUX0
ADCSSCTL0, type R/W, offset 0x044, reset 0x0000.0000 (see page 829) TS7 TS3 IE7 IE3 END7 END3 D7 D3 TS6 TS2 IE6 IE2 END6 END2 D6 D2 TS5 TS1 IE5 IE1 END5 END1 D5 D1 TS4 TS0 IE4 IE0 END4 END0 D4 D0
ADCSSFIFO0, type RO, offset 0x048, reset - (see page 832)
DATA ADCSSFIFO1, type RO, offset 0x068, reset - (see page 832)
DATA ADCSSFIFO2, type RO, offset 0x088, reset - (see page 832)
DATA ADCSSFIFO3, type RO, offset 0x0A8, reset - (see page 832)
DATA ADCSSFSTAT0, type RO, offset 0x04C, reset 0x0000.0100 (see page 833)
FULL ADCSSFSTAT1, type RO, offset 0x06C, reset 0x0000.0100 (see page 833)
EMPTY
HPTR
TPTR
FULL ADCSSFSTAT2, type RO, offset 0x08C, reset 0x0000.0100 (see page 833)
EMPTY
HPTR
TPTR
FULL ADCSSFSTAT3, type RO, offset 0x0AC, reset 0x0000.0100 (see page 833)
EMPTY
HPTR
TPTR
FULL
EMPTY
HPTR
TPTR
1209
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
ADCSSOP0, type R/W, offset 0x050, reset 0x0000.0000 (see page 835) S7DCOP S3DCOP ADCSSDC0, type R/W, offset 0x054, reset 0x0000.0000 (see page 837) S7DCSEL S3DCSEL S6DCSEL S2DCSEL S5DCSEL S1DCSEL S4DCSEL S0DCSEL S6DCOP S2DCOP S5DCOP S1DCOP S4DCOP S0DCOP
ADCSSMUX1, type R/W, offset 0x060, reset 0x0000.0000 (see page 839)
MUX3
MUX2
MUX1
MUX0
ADCSSMUX2, type R/W, offset 0x080, reset 0x0000.0000 (see page 839)
MUX3
MUX2
MUX1
MUX0
ADCSSCTL1, type R/W, offset 0x064, reset 0x0000.0000 (see page 840)
TS3
IE3
END3
D3
TS2
IE2
END2
D2
TS1
IE1
END1
D1
TS0
IE0
END0
D0
ADCSSCTL2, type R/W, offset 0x084, reset 0x0000.0000 (see page 840)
TS3
IE3
END3
D3
TS2
IE2
END2
D2
TS1
IE1
END1
D1
TS0
IE0
END0
D0
ADCSSOP1, type R/W, offset 0x070, reset 0x0000.0000 (see page 842)
S3DCOP ADCSSOP2, type R/W, offset 0x090, reset 0x0000.0000 (see page 842)
S2DCOP
S1DCOP
S0DCOP
S3DCOP ADCSSDC1, type R/W, offset 0x074, reset 0x0000.0000 (see page 843)
S2DCOP
S1DCOP
S0DCOP
S3DCSEL
S2DCSEL
S1DCSEL
S0DCSEL
ADCSSDC2, type R/W, offset 0x094, reset 0x0000.0000 (see page 843)
S3DCSEL
S2DCSEL
S1DCSEL
S0DCSEL
ADCSSMUX3, type R/W, offset 0x0A0, reset 0x0000.0000 (see page 845)
MUX0 ADCSSCTL3, type R/W, offset 0x0A4, reset 0x0000.0000 (see page 846)
TS0 ADCSSOP3, type R/W, offset 0x0B0, reset 0x0000.0000 (see page 847)
IE0
END0
D0
S0DCOP ADCSSDC3, type R/W, offset 0x0B4, reset 0x0000.0000 (see page 848)
S0DCSEL ADCDCRIC, type WO, offset 0xD00, reset 0x0000.0000 (see page 849) DCTRIG7 DCTRIG6 DCTRIG5 DCTRIG4 DCTRIG3 DCTRIG2 DCTRIG1 DCTRIG0 DCINT7 ADCDCCTL0, type R/W, offset 0xE00, reset 0x0000.0000 (see page 854) DCINT6 DCINT5 DCINT4 DCINT3 DCINT2 DCINT1 DCINT0
CIE ADCDCCTL1, type R/W, offset 0xE04, reset 0x0000.0000 (see page 854)
CIC
CIM
CIE
CIC
CIM
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
ADCDCCTL2, type R/W, offset 0xE08, reset 0x0000.0000 (see page 854)
CIE ADCDCCTL3, type R/W, offset 0xE0C, reset 0x0000.0000 (see page 854)
CIC
CIM
CIC
CIM
CIC
CIM
CIC
CIM
CIE ADCDCCTL7, type R/W, offset 0xE1C, reset 0x0000.0000 (see page 854)
CIC
CIM
CIE ADCDCCMP0, type R/W, offset 0xE40, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP1, type R/W, offset 0xE44, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP2, type R/W, offset 0xE48, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP3, type R/W, offset 0xE4C, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP4, type R/W, offset 0xE50, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP5, type R/W, offset 0xE54, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP6, type R/W, offset 0xE58, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCDCCMP7, type R/W, offset 0xE5C, reset 0x0000.0000 (see page 856) COMP1 COMP0 ADCPP, type RO, offset 0xFC0, reset 0x00B0.20C7 (see page 857) TS DC ADCPC, type R/W, offset 0xFC4, reset 0x0000.0007 (see page 859) CH RSL
CIC
CIM
TYPE MSR
SR ADCCC, type R/W, offset 0xFC8, reset 0x0000.0000 (see page 860)
CS
1211
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0

UART0 base: 0x4000.C000 UART1 base: 0x4000.D000 UART2 base: 0x4000.E000 UART3 base: 0x4000.F000 UART4 base: 0x4001.0000 UART5 base: 0x4001.1000 UART6 base: 0x4001.2000 UART7 base: 0x4001.3000
UARTDR, type R/W, offset 0x000, reset 0x0000.0000 (see page 875)
OE
BE
PE
FE
DATA
UARTRSR/UARTECR, type RO, offset 0x004, reset 0x0000.0000 (Read-Only Status Register) (see page 877)
OE UARTRSR/UARTECR, type WO, offset 0x004, reset 0x0000.0000 (Write-Only Error Clear Register) (see page 877)
BE
PE
FE
DATA UARTFR, type RO, offset 0x018, reset 0x0000.0090 (see page 880)
TXFE UARTILPR, type R/W, offset 0x020, reset 0x0000.0000 (see page 882)
RXFF
TXFF
RXFE
BUSY
CTS
ILPDVSR UARTIBRD, type R/W, offset 0x024, reset 0x0000.0000 (see page 883)
DIVINT UARTFBRD, type R/W, offset 0x028, reset 0x0000.0000 (see page 884)
DIVFRAC UARTLCRH, type R/W, offset 0x02C, reset 0x0000.0000 (see page 885)
SPS UARTCTL, type R/W, offset 0x030, reset 0x0000.0300 (see page 887)
WLEN
FEN
STP2
EPS
PEN
BRK
RXE UARTIFLS, type R/W, offset 0x034, reset 0x0000.0012 (see page 891)
TXE
LBE
LIN
HSE
EOT
SMART
SIRLP
SIREN
UARTEN
RXIFLSEL UARTIM, type R/W, offset 0x038, reset 0x0000.0000 (see page 893)
TXIFLSEL
LME5IM
LME1IM
LMSBIM
9BITIM
OEIM
BEIM
PEIM
FEIM
RTIM
TXIM
RXIM
CTSIM
UARTRIS, type RO, offset 0x03C, reset 0x0000.000F (see page 896)
LME5RIS LME1RIS LMSBRIS 9BITRIS
OERIS
BERIS
PERIS
FERIS
RTRIS
TXRIS
RXRIS
CTSRIS
UARTMIS, type RO, offset 0x040, reset 0x0000.0000 (see page 899)
LME5MIS LME1MIS LMSBMIS 9BITMIS
OEMIS
BEMIS
PEMIS
FEMIS
RTMIS
TXMIS
RXMIS
CTSMIS
UARTICR, type W1C, offset 0x044, reset 0x0000.0000 (see page 902)
LME5IC
LME1IC
LMSBIC
9BITIC
OEIC
BEIC
PEIC
FEIC
RTIC
TXIC
RXIC
CTSMIC
UARTDMACTL, type R/W, offset 0x048, reset 0x0000.0000 (see page 904)
DMAERR TXDMAE RXDMAE
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
UARTLCTL, type R/W, offset 0x090, reset 0x0000.0000 (see page 905)
BLEN UARTLSS, type RO, offset 0x094, reset 0x0000.0000 (see page 906)
MASTER
TSS UARTLTIM, type RO, offset 0x098, reset 0x0000.0000 (see page 907)
TIMER UART9BITADDR, type R/W, offset 0x0A4, reset 0x0000.0000 (see page 908)
9BITEN UART9BITAMASK, type R/W, offset 0x0A8, reset 0x0000.00FF (see page 909)
ADDR
MASK UARTPP, type RO, offset 0xFC0, reset 0x0000.0003 (see page 910)
NB UARTCC, type R/W, offset 0xFC8, reset 0x0000.0000 (see page 911)
SC
CS UARTPeriphID4, type RO, offset 0xFD0, reset 0x0000.0000 (see page 912)
PID4 UARTPeriphID5, type RO, offset 0xFD4, reset 0x0000.0000 (see page 913)
PID5 UARTPeriphID6, type RO, offset 0xFD8, reset 0x0000.0000 (see page 914)
PID6 UARTPeriphID7, type RO, offset 0xFDC, reset 0x0000.0000 (see page 915)
PID7 UARTPeriphID0, type RO, offset 0xFE0, reset 0x0000.0060 (see page 916)
PID2 UARTPeriphID3, type RO, offset 0xFEC, reset 0x0000.0001 (see page 919)
PID3 UARTPCellID0, type RO, offset 0xFF0, reset 0x0000.000D (see page 920)
CID0 UARTPCellID1, type RO, offset 0xFF4, reset 0x0000.00F0 (see page 921)
CID1
1213
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
UARTPCellID2, type RO, offset 0xFF8, reset 0x0000.0005 (see page 922)
CID2 UARTPCellID3, type RO, offset 0xFFC, reset 0x0000.00B1 (see page 923)
CID3

SSI0 base: 0x4000.8000 SSI1 base: 0x4000.9000 SSI2 base: 0x4000.A000 SSI3 base: 0x4000.B000
SSICR0, type R/W, offset 0x000, reset 0x0000.0000 (see page 939)
SCR SSICR1, type R/W, offset 0x004, reset 0x0000.0000 (see page 941)
SPH
SPO
FRF
DSS
SLBY6 SSIDR, type R/W, offset 0x008, reset 0x0000.0000 (see page 943)
EOT
SOD
MS
SSE
LBM
DATA SSISR, type RO, offset 0x00C, reset 0x0000.0003 (see page 944)
BSY SSICPSR, type R/W, offset 0x010, reset 0x0000.0000 (see page 946)
RFF
RNE
TNF
TFE
CPSDVSR SSIIM, type R/W, offset 0x014, reset 0x0000.0000 (see page 947)
TXIM SSIRIS, type RO, offset 0x018, reset 0x0000.0008 (see page 948)
RXIM
RTIM
RORIM
TXRIS SSIMIS, type RO, offset 0x01C, reset 0x0000.0000 (see page 950)
RXRIS
RTRIS
RORRIS
TXMIS SSIICR, type W1C, offset 0x020, reset 0x0000.0000 (see page 952)
RXMIS
RTMIS
RORMIS
RTIC SSIDMACTL, type R/W, offset 0x024, reset 0x0000.0000 (see page 953)
RORIC
TXDMAE RXDMAE SSICC, type R/W, offset 0xFC8, reset 0x0000.0000 (see page 954)
CS SSIPeriphID4, type RO, offset 0xFD0, reset 0x0000.0000 (see page 955)
PID4 SSIPeriphID5, type RO, offset 0xFD4, reset 0x0000.0000 (see page 956)
PID5 SSIPeriphID6, type RO, offset 0xFD8, reset 0x0000.0000 (see page 957)
PID6
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
SSIPeriphID7, type RO, offset 0xFDC, reset 0x0000.0000 (see page 958)
PID7 SSIPeriphID0, type RO, offset 0xFE0, reset 0x0000.0022 (see page 959)
PID2 SSIPeriphID3, type RO, offset 0xFEC, reset 0x0000.0001 (see page 962)
PID3 SSIPCellID0, type RO, offset 0xFF0, reset 0x0000.000D (see page 963)
CID0 SSIPCellID1, type RO, offset 0xFF4, reset 0x0000.00F0 (see page 964)
CID1 SSIPCellID2, type RO, offset 0xFF8, reset 0x0000.0005 (see page 965)
CID2 SSIPCellID3, type RO, offset 0xFFC, reset 0x0000.00B1 (see page 966)
CID3
Inter-Integrated Circuit (I2C) Interface I2C Master

I2C 0 base: 0x4002.0000 I2C 1 base: 0x4002.1000 I2C 2 base: 0x4002.2000 I2C 3 base: 0x4002.3000
I2CMSA, type R/W, offset 0x000, reset 0x0000.0000
SA I2CMCS, type RO, offset 0x004, reset 0x0000.0020 (Read-Only Status Register)
R/S
CLKTO I2CMCS, type WO, offset 0x004, reset 0x0000.0020 (Write-Only Control Register)
BUSBSY
IDLE
ARBLST
DATACK
ADRACK
ERROR
BUSY
HS I2CMDR, type R/W, offset 0x008, reset 0x0000.0000
ACK
STOP
START
RUN
DATA I2CMTPR, type R/W, offset 0x00C, reset 0x0000.0001
HS I2CMIMR, type R/W, offset 0x010, reset 0x0000.0000
TPR
CLKIM
IM
1215
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
I2CMRIS, type RO, offset 0x014, reset 0x0000.0000
CLKRIS I2CMMIS, type RO, offset 0x018, reset 0x0000.0000
RIS
CLKMIS I2CMICR, type WO, offset 0x01C, reset 0x0000.0000
MIS
CLKIC I2CMCR, type R/W, offset 0x020, reset 0x0000.0000
IC
SFE I2CMCLKOCNT, type R/W, offset 0x024, reset 0x0000.0000
MFE
LPBK
CNTL I2CMBMON, type RO, offset 0x02C, reset 0x0000.0003
SDA
SCL
Inter-Integrated Circuit (I2C) Interface I2C Slave

I2CSOAR, type R/W, offset 0x800, reset 0x0000.0000
OAR I2CSCSR, type RO, offset 0x804, reset 0x0000.0000 (Read-Only Status Register)
OAR2SEL I2CSCSR, type WO, offset 0x804, reset 0x0000.0000 (Write-Only Control Register)
FBR
TREQ
RREQ
DA I2CSDR, type R/W, offset 0x808, reset 0x0000.0000
DATA I2CSIMR, type R/W, offset 0x80C, reset 0x0000.0000
STOPIM I2CSRIS, type RO, offset 0x810, reset 0x0000.0000
STARTIM
DATAIM
STOPRIS STARTRIS DATARIS I2CSMIS, type RO, offset 0x814, reset 0x0000.0000
STOPMIS STARTMIS DATAMIS I2CSICR, type WO, offset 0x818, reset 0x0000.0000
STOPIC I2CSOAR2, type R/W, offset 0x81C, reset 0x0000.0000
STARTIC
DATAIC
OAR2EN
OAR2
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
I2CSACKCTL, type R/W, offset 0x820, reset 0x0000.0000
ACKOVAL ACKOEN
Inter-Integrated Circuit (I2C) Interface I2C Status and Control

I2CPP, type RO, offset 0xFC0, reset 0x0000.0001
HS I2CPC, type RO, offset 0xFC4, reset 0x0000.0001
HS

CAN0 base: 0x4004.0000
CANCTL, type R/W, offset 0x000, reset 0x0000.0001 (see page 1035)
TEST CANSTS, type R/W, offset 0x004, reset 0x0000.0000 (see page 1037)
CCE
DAR
EIE
SIE
IE
INIT
BOFF CANERR, type RO, offset 0x008, reset 0x0000.0000 (see page 1040)
EWARN
EPASS
RXOK
TXOK
LEC
RP
REC
TEC
CANBIT, type R/W, offset 0x00C, reset 0x0000.2301 (see page 1041)
TSEG2
TSEG1
SJW
BRP
CANINT, type RO, offset 0x010, reset 0x0000.0000 (see page 1042)
INTID CANTST, type R/W, offset 0x014, reset 0x0000.0000 (see page 1043)
RX CANBRPE, type R/W, offset 0x018, reset 0x0000.0000 (see page 1045)
TX
LBACK
SILENT
BASIC
BRPE CANIF1CRQ, type R/W, offset 0x020, reset 0x0000.0001 (see page 1046)
BUSY CANIF2CRQ, type R/W, offset 0x080, reset 0x0000.0001 (see page 1046)
MNUM
BUSY CANIF1CMSK, type R/W, offset 0x024, reset 0x0000.0000 (see page 1047)
MNUM
WRNRD CANIF2CMSK, type R/W, offset 0x084, reset 0x0000.0000 (see page 1047)
MASK
ARB
CONTROL CLRINTPND
NEWDAT / TXRQST
DATAA
DATAB
WRNRD
MASK
ARB
CONTROL CLRINTPND
NEWDAT / TXRQST
DATAA
DATAB
1217
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
CANIF1MSK1, type R/W, offset 0x028, reset 0x0000.FFFF (see page 1050)
MSK CANIF2MSK1, type R/W, offset 0x088, reset 0x0000.FFFF (see page 1050)
MSK CANIF1MSK2, type R/W, offset 0x02C, reset 0x0000.FFFF (see page 1051)
MXTD
MDIR
MSK
CANIF2MSK2, type R/W, offset 0x08C, reset 0x0000.FFFF (see page 1051)
MXTD
MDIR
MSK
CANIF1ARB1, type R/W, offset 0x030, reset 0x0000.0000 (see page 1053)
ID CANIF2ARB1, type R/W, offset 0x090, reset 0x0000.0000 (see page 1053)
ID CANIF1ARB2, type R/W, offset 0x034, reset 0x0000.0000 (see page 1054)
MSGVAL
XTD
DIR
ID
CANIF2ARB2, type R/W, offset 0x094, reset 0x0000.0000 (see page 1054)
MSGVAL
XTD
DIR
ID
CANIF1MCTL, type R/W, offset 0x038, reset 0x0000.0000 (see page 1056)
NEWDAT MSGLST
INTPND
UMASK
TXIE
RXIE
RMTEN
TXRQST
EOB
DLC
CANIF2MCTL, type R/W, offset 0x098, reset 0x0000.0000 (see page 1056)
NEWDAT MSGLST
INTPND
UMASK
TXIE
RXIE
RMTEN
TXRQST
EOB
DLC
CANIF1DA1, type R/W, offset 0x03C, reset 0x0000.0000 (see page 1059)
DATA CANIF1DA2, type R/W, offset 0x040, reset 0x0000.0000 (see page 1059)
DATA CANIF1DB1, type R/W, offset 0x044, reset 0x0000.0000 (see page 1059)
DATA CANIF1DB2, type R/W, offset 0x048, reset 0x0000.0000 (see page 1059)
DATA CANIF2DA1, type R/W, offset 0x09C, reset 0x0000.0000 (see page 1059)
DATA CANIF2DA2, type R/W, offset 0x0A0, reset 0x0000.0000 (see page 1059)
DATA CANIF2DB1, type R/W, offset 0x0A4, reset 0x0000.0000 (see page 1059)
DATA
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
CANIF2DB2, type R/W, offset 0x0A8, reset 0x0000.0000 (see page 1059)
DATA CANTXRQ1, type RO, offset 0x100, reset 0x0000.0000 (see page 1060)
TXRQST CANTXRQ2, type RO, offset 0x104, reset 0x0000.0000 (see page 1060)
TXRQST CANNWDA1, type RO, offset 0x120, reset 0x0000.0000 (see page 1061)
NEWDAT CANNWDA2, type RO, offset 0x124, reset 0x0000.0000 (see page 1061)
NEWDAT CANMSG1INT, type RO, offset 0x140, reset 0x0000.0000 (see page 1062)
INTPND CANMSG2INT, type RO, offset 0x144, reset 0x0000.0000 (see page 1062)
INTPND CANMSG1VAL, type RO, offset 0x160, reset 0x0000.0000 (see page 1063)
MSGVAL CANMSG2VAL, type RO, offset 0x164, reset 0x0000.0000 (see page 1063)
MSGVAL

Base 0x4005.0000
USBFADDR, type R/W, offset 0x000, reset 0x00 (see page 1076) FUNCADDR USBPOWER, type R/W, offset 0x001, reset 0x20 (see page 1077) ISOUP USBTXIS, type RO, offset 0x002, reset 0x0000 (see page 1079) EP7 USBRXIS, type RO, offset 0x004, reset 0x0000 (see page 1081) EP7 USBTXIE, type R/W, offset 0x006, reset 0xFFFF (see page 1082) EP7 USBRXIE, type R/W, offset 0x008, reset 0xFFFE (see page 1084) EP7 USBIS, type RO, offset 0x00A, reset 0x00 (see page 1085) SOF USBIE, type R/W, offset 0x00B, reset 0x06 (see page 1086) DISCON USBFRAME, type RO, offset 0x00C, reset 0x0000 (see page 1088) FRAME USBEPIDX, type R/W, offset 0x00E, reset 0x00 (see page 1089) EPIDX USBTEST, type R/W, offset 0x00F, reset 0x00 (see page 1090) FIFOACC FORCEFS SOF RESET RESUME SUSPEND RESET RESUME SUSPEND EP6 EP5 EP4 EP3 EP2 EP1 EP6 EP5 EP4 EP3 EP2 EP1 EP0 EP6 EP5 EP4 EP3 EP2 EP1 EP6 EP5 EP4 EP3 EP2 EP1 EP0
SOFTCONN
RESET
RESUME SUSPEND PWRDNPHY
1219
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
USBFIFO0, type R/W, offset 0x020, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO1, type R/W, offset 0x024, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO2, type R/W, offset 0x028, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO3, type R/W, offset 0x02C, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO4, type R/W, offset 0x030, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO5, type R/W, offset 0x034, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO6, type R/W, offset 0x038, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBFIFO7, type R/W, offset 0x03C, reset 0x0000.0000 (see page 1091) EPDATA EPDATA USBTXFIFOSZ, type R/W, offset 0x062, reset 0x00 (see page 1092) DPB USBRXFIFOSZ, type R/W, offset 0x063, reset 0x00 (see page 1092) DPB USBTXFIFOADD, type R/W, offset 0x064, reset 0x0000 (see page 1093) ADDR USBRXFIFOADD, type R/W, offset 0x066, reset 0x0000 (see page 1093) ADDR USBCONTIM, type R/W, offset 0x07A, reset 0x5C (see page 1094) WTCON USBFSEOF, type R/W, offset 0x07D, reset 0x77 (see page 1095) FSEOFG USBLSEOF, type R/W, offset 0x07E, reset 0x72 (see page 1096) LSEOFG USBTXMAXP1, type R/W, offset 0x110, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP2, type R/W, offset 0x120, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP3, type R/W, offset 0x130, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP4, type R/W, offset 0x140, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP5, type R/W, offset 0x150, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP6, type R/W, offset 0x160, reset 0x0000 (see page 1097) MAXLOAD USBTXMAXP7, type R/W, offset 0x170, reset 0x0000 (see page 1097) MAXLOAD WTID SIZE SIZE
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
USBCSRL0, type W1C, offset 0x102, reset 0x00 (see page 1098) SETENDC RXRDYC USBCSRH0, type W1C, offset 0x103, reset 0x00 (see page 1100) FLUSH USBCOUNT0, type RO, offset 0x108, reset 0x00 (see page 1101) COUNT USBTXCSRL1, type R/W, offset 0x112, reset 0x00 (see page 1102) CLRDT USBTXCSRL2, type R/W, offset 0x122, reset 0x00 (see page 1102) CLRDT USBTXCSRL3, type R/W, offset 0x132, reset 0x00 (see page 1102) CLRDT USBTXCSRL4, type R/W, offset 0x142, reset 0x00 (see page 1102) CLRDT USBTXCSRL5, type R/W, offset 0x152, reset 0x00 (see page 1102) CLRDT USBTXCSRL6, type R/W, offset 0x162, reset 0x00 (see page 1102) CLRDT USBTXCSRL7, type R/W, offset 0x172, reset 0x00 (see page 1102) CLRDT USBTXCSRH1, type R/W, offset 0x113, reset 0x00 (see page 1104) AUTOSET USBTXCSRH2, type R/W, offset 0x123, reset 0x00 (see page 1104) AUTOSET USBTXCSRH3, type R/W, offset 0x133, reset 0x00 (see page 1104) AUTOSET USBTXCSRH4, type R/W, offset 0x143, reset 0x00 (see page 1104) AUTOSET USBTXCSRH5, type R/W, offset 0x153, reset 0x00 (see page 1104) AUTOSET USBTXCSRH6, type R/W, offset 0x163, reset 0x00 (see page 1104) AUTOSET USBTXCSRH7, type R/W, offset 0x173, reset 0x00 (see page 1104) AUTOSET USBRXMAXP1, type R/W, offset 0x114, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP2, type R/W, offset 0x124, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP3, type R/W, offset 0x134, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP4, type R/W, offset 0x144, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP5, type R/W, offset 0x154, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP6, type R/W, offset 0x164, reset 0x0000 (see page 1106) MAXLOAD USBRXMAXP7, type R/W, offset 0x174, reset 0x0000 (see page 1106) MAXLOAD USBRXCSRL1, type R/W, offset 0x116, reset 0x00 (see page 1107) CLRDT USBRXCSRL2, type R/W, offset 0x126, reset 0x00 (see page 1107) CLRDT STALLED STALL FLUSH DATAERR OVER FULL RXRDY STALLED STALL FLUSH DATAERR OVER FULL RXRDY ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD ISO MODE DMAEN FDT DMAMOD STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALLED STALL FLUSH UNDRN FIFONE TXRDY STALL SETEND DATAEND STALLED TXRDY RXRDY
1221
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
USBRXCSRL3, type R/W, offset 0x136, reset 0x00 (see page 1107) CLRDT USBRXCSRL4, type R/W, offset 0x146, reset 0x00 (see page 1107) CLRDT USBRXCSRL5, type R/W, offset 0x156, reset 0x00 (see page 1107) CLRDT USBRXCSRL6, type R/W, offset 0x166, reset 0x00 (see page 1107) CLRDT USBRXCSRL7, type R/W, offset 0x176, reset 0x00 (see page 1107) CLRDT USBRXCSRH1, type R/W, offset 0x117, reset 0x00 (see page 1110) AUTOCL USBRXCSRH2, type R/W, offset 0x127, reset 0x00 (see page 1110) AUTOCL USBRXCSRH3, type R/W, offset 0x137, reset 0x00 (see page 1110) AUTOCL USBRXCSRH4, type R/W, offset 0x147, reset 0x00 (see page 1110) AUTOCL USBRXCSRH5, type R/W, offset 0x157, reset 0x00 (see page 1110) AUTOCL USBRXCSRH6, type R/W, offset 0x167, reset 0x00 (see page 1110) AUTOCL USBRXCSRH7, type R/W, offset 0x177, reset 0x00 (see page 1110) AUTOCL USBRXCOUNT1, type RO, offset 0x118, reset 0x0000 (see page 1112) COUNT USBRXCOUNT2, type RO, offset 0x128, reset 0x0000 (see page 1112) COUNT USBRXCOUNT3, type RO, offset 0x138, reset 0x0000 (see page 1112) COUNT USBRXCOUNT4, type RO, offset 0x148, reset 0x0000 (see page 1112) COUNT USBRXCOUNT5, type RO, offset 0x158, reset 0x0000 (see page 1112) COUNT USBRXCOUNT6, type RO, offset 0x168, reset 0x0000 (see page 1112) COUNT USBRXCOUNT7, type RO, offset 0x178, reset 0x0000 (see page 1112) COUNT USBRXDPKTBUFDIS, type R/W, offset 0x340, reset 0x0000 (see page 1113) EP7 USBTXDPKTBUFDIS, type R/W, offset 0x342, reset 0x0000 (see page 1114) EP7 USBDRRIS, type RO, offset 0x410, reset 0x0000.0000 (see page 1115) EP6 EP5 EP4 EP3 EP2 EP1 EP6 EP5 EP4 EP3 EP2 EP1 ISO DMAEN
DISNYET / PIDERR
STALLED
STALL
FLUSH
DATAERR
OVER
FULL
RXRDY
STALLED
STALL
FLUSH
DATAERR
OVER
FULL
RXRDY
STALLED
STALL
FLUSH
DATAERR
OVER
FULL
RXRDY
STALLED
STALL
FLUSH
DATAERR
OVER
FULL
RXRDY
STALLED
STALL
FLUSH
DATAERR
OVER
FULL
RXRDY
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
ISO
DMAEN
DISNYET / PIDERR
DMAMOD
DMAMOD
RESUME USBDRIM, type R/W, offset 0x414, reset 0x0000.0000 (see page 1116)
RESUME
April 25, 2012
31 15
30 14
29 13
28 12
27 11
26 10
25 9
24 8
23 7
22 6
21 5
20 4
19 3
18 2
17 1
16 0
USBDRISC, type W1C, offset 0x418, reset 0x0000.0000 (see page 1117)
RESUME USBDMASEL, type R/W, offset 0x450, reset 0x0033.2211 (see page 1118) DMACTX DMABTX DMABRX DMAATX DMACRX DMAARX
USBPP, type RO, offset 0xFC0, reset 0x0000.1050 (see page 1120)
ECNT
USB
PHY
TYPE
Analog Comparators
Base 0x4003.C000
ACMIS, type R/W1C, offset 0x000, reset 0x0000.0000 (see page 1128)
IN1 ACRIS, type RO, offset 0x004, reset 0x0000.0000 (see page 1129)
IN0
IN1 ACINTEN, type R/W, offset 0x008, reset 0x0000.0000 (see page 1130)
IN0
IN1 ACREFCTL, type R/W, offset 0x010, reset 0x0000.0000 (see page 1131)
IN0
EN ACSTAT0, type RO, offset 0x020, reset 0x0000.0000 (see page 1132)
RNG
VREF
OVAL ACSTAT1, type RO, offset 0x040, reset 0x0000.0000 (see page 1132)
OVAL ACCTL0, type R/W, offset 0x024, reset 0x0000.0000 (see page 1133)
TOEN
ASRCP
TSLVAL
TSEN
ISLVAL
ISEN
CINV
ACCTL1, type R/W, offset 0x044, reset 0x0000.0000 (see page 1133)
TOEN
ASRCP
TSLVAL
TSEN
ISLVAL
ISEN
CINV
ACMPPP, type RO, offset 0xFC0, reset 0x0003.0003 (see page 1135) C1O CMP1 C0O CMP0
1223
Ordering and Contact Information
B
B.1
Ordering and Contact Information

Ordering Information
LM CCNNN XY PPS I GR
Core 4F = ARM Cortex-M4F Part Number NNN = Series part number Flash Size B = 32 KB C = 64 KB E = 128 KB H = 256 KB SRAM Size 2 = 12 KB 4 = 24 KB 5 = 32 KB Shipping Medium R = Tape-and-reel Omitted = Default shipping (tray or tube) Internal Use Only Temperature I = 40C to +85C Speed F = 80 MHz Package QC = 100-pin LQFP QD = 144-pin LQFP QR = 64-pin LQFP
Table B-1. Part Ordering Information

Orderable Part Number LM4F120H5QRFIG LM4F120H5QRFIGR Description Stellaris LM4F120H5QR Microcontroller Industrial Temperature 64-pin LQFP Stellaris LM4F120H5QR Microcontroller Industrial Temperature 64-pin LQFP Tape-and-reel
B.2
Part Markings
The Stellaris microcontrollers are marked with an identifying number. This code contains the following information: The first and second lines indicate the part number, for example, LM4F232H5QDFIGA0. The second letter in the part number indicates the product status. An M indicates the part is fully qualified and released to production. An X, for example, LX4F232H5QDFIGA0, indicates the part is experimental and requires a waiver The third line contains internal tracking numbers.
B.3
Kits
The Stellaris Family provides the hardware and software tools that engineers need to begin development quickly. Reference Design Kits accelerate product development by providing ready-to-run hardware and comprehensive documentation including hardware design files Evaluation Kits provide a low-cost and effective means of evaluating Stellaris microcontrollers before purchase Development Kits provide you with all the tools you need to develop and prototype embedded applications right out of the box
April 25, 2012
See the website at www.ti.com/stellaris for the latest tools available, or ask your distributor.
B.4
Support Information
For support on Stellaris products, contact the TI Worldwide Product Information Center nearest you: http://www-k.ext.ti.com/sc/technical-support/product-information-centers.htm.
1225
Package Information
C
C.1
C.1.1
Package Information
64-Pin LQFP Package
Package Dimensions
MECHANICAL DATA
MTQF008A JANUARY 1995 REVISED DECEMBER 1996
Figure C-1. Stellaris LM4F120H5QR 64-Pin LQFP Package
PM (S-PQFP-G64)
0,27 0,17 48 33
PLASTIC QUAD FLATPACK
0,50
0,08 M
49
32
64
17 0,13 NOM
1 7,50 TYP 10,20 SQ 9,80 12,20 SQ 11,80 1,45 1,35
16 Gage Plane
0,25 0,05 MIN 0 7
0,75 0,45
Seating Plane 1,60 MAX 0,08 4040152 / C 11/96 NOTES: A. B. C. D. All linear dimensions are in millimeters. This drawing is subject to change without notice. Falls within JEDEC MS-026 May also be thermally enhanced plastic with leads connected to the die pads.
April 25, 2012
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other changes to its semiconductor products and services per JESD46C and to discontinue any product or service per JESD48B. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All semiconductor products (also referred to herein as components) are sold subject to TIs terms and conditions of sale supplied at the time of order acknowledgment. TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TIs terms and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily performed. TI assumes no liability for applications assistance or the design of Buyers products. Buyers are responsible for their products and applications using TI components. To minimize the risks associated with Buyers products and applications, Buyers should provide adequate design and operating safeguards. TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI. Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altered documentation. Information of third parties may be subject to additional restrictions. Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use of any TI components in safety-critical applications. In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TIs goal is to help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and requirements. Nonetheless, such components are subject to these terms. No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties have executed a special agreement specifically governing such use. Only those TI components which TI has specifically designated as military grade or enhanced plastic are designed and intended for use in military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and regulatory requirements in connection with such use. TI has specifically designated certain components which meet ISO/TS16949 requirements, mainly for automotive use. Components which have not been so designated are neither designed nor intended for automotive use; and TI will not be responsible for any failure of such components to meet such requirements. Products Audio Amplifiers Data Converters DLP Products DSP Clocks and Timers Interface Logic Power Mgmt Microcontrollers RFID OMAP Mobile Processors Wireless Connectivity www.ti.com/audio amplifier.ti.com dataconverter.ti.com www.dlp.com dsp.ti.com www.ti.com/clocks interface.ti.com logic.ti.com power.ti.com microcontroller.ti.com www.ti-rfid.com www.ti.com/omap www.ti.com/wirelessconnectivity Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265 Copyright 2012, Texas Instruments Incorporated TI E2E Community e2e.ti.com Applications Automotive and Transportation www.ti.com/automotive Communications and Telecom www.ti.com/communications Computers and Peripherals Consumer Electronics Energy and Lighting Industrial Medical Security Space, Avionics and Defense Video and Imaging www.ti.com/computers www.ti.com/consumer-apps www.ti.com/energy www.ti.com/industrial www.ti.com/medical www.ti.com/security www.ti.com/space-avionics-defense www.ti.com/video

Stellaris® LM4F120H5QR Microcontroller Data Sheet

Uploaded by

Copyright:

Available Formats

Stellaris® LM4F120H5QR Microcontroller Data Sheet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stellaris® LM4F120H5QR Microcontroller Data Sheet

Uploaded by

Copyright:

Available Formats

TE X AS INS TRUM E NTS - ADVANCE INFO R MAT ION

Stellaris LM4F120H5QR Microcontroller

C o p yri g h t 2 0 07-2012 Te xa s In stru me n ts In co rporated

2 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

Architectural Overview .......................................................................................... 41

The Cortex-M4F Processor ................................................................................... 65

April 25, 2012 Texas Instruments-Advance Information

Cortex-M4 Peripherals ......................................................................................... 118

JTAG Interface ...................................................................................................... 196

System Control ..................................................................................................... 208

4 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

5.4 5.5 5.6

System Exception Module ................................................................................... 472

Hibernation Module .............................................................................................. 480

Internal Memory ................................................................................................... 510

Micro Direct Memory Access (DMA) ................................................................ 568

April 25, 2012 Texas Instruments-Advance Information

General-Purpose Input/Outputs (GPIOs) ........................................................... 632

General-Purpose Timers ...................................................................................... 686

6 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

Watchdog Timers ................................................................................................. 756

Analog-to-Digital Converter (ADC) ..................................................................... 781

Universal Asynchronous Receivers/Transmitters (UARTs) ............................. 861

Synchronous Serial Interface (SSI) .................................................................... 924

April 25, 2012 Texas Instruments-Advance Information

15.3.3 15.3.4 15.3.5 15.4 15.5 15.6

927 928 935 936 937 938

Inter-Integrated Circuit (I2C) Interface ................................................................ 967

Controller Area Network (CAN) Module ........................................................... 1014

Universal Serial Bus (USB) Controller ............................................................. 1064

8 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

18.3.2 18.4 18.4.1 18.5 18.6

Analog Comparators .......................................................................................... 1121

Pin Diagram ........................................................................................................ 1136 Signal Tables ...................................................................................................... 1137

Operating Characteristics ................................................................................. 1157 Electrical Characteristics .................................................................................. 1158

April 25, 2012 Texas Instruments-Advance Information

B.1 B.2 B.3 B.4

1224 1224 1224 1225

Package Information .......................................................................................... 1226

10 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

April 25, 2012 Texas Instruments-Advance Information

12 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

April 25, 2012 Texas Instruments-Advance Information

14 Texas Instruments-Advance Information

April 25, 2012

Stellaris LM4F120H5QR Microcontroller

April 25, 2012 Texas Instruments-Advance Information

16 Texas Instruments-Advance Information