UG Spruhx5g PDF
UG Spruhx5g PDF
UG Spruhx5g PDF
Preface....................................................................................................................................... 81
1 C2000 Software Support ...................................................................................................... 82
1.1 Introduction .................................................................................................................. 83
1.2 C2000Ware Structure ...................................................................................................... 83
1.3 Documentation .............................................................................................................. 83
1.4 Devices ...................................................................................................................... 83
1.5 Libraries ..................................................................................................................... 83
1.6 Code Composer Studio .................................................................................................... 83
1.7 PinMUX Tool ................................................................................................................ 84
2 C28x Processor .................................................................................................................. 85
2.1 Introduction .................................................................................................................. 86
2.2 Features ..................................................................................................................... 86
2.3 Floating-Point Unit ......................................................................................................... 86
2.4 Trigonometric Math Unit .................................................................................................. 86
2.5 Viterbi, Complex Math, and CRC Unit II (VCU-II) ..................................................................... 87
3 System Control .................................................................................................................. 88
3.1 Introduction .................................................................................................................. 89
3.2 System Control Functional Description .................................................................................. 89
3.2.1 Device Identification .............................................................................................. 89
3.2.2 Device Configuration Registers ................................................................................. 89
3.3 Resets ....................................................................................................................... 90
3.3.1 Reset Sources ..................................................................................................... 90
3.3.2 External Reset (XRS) ............................................................................................. 90
3.3.3 Power-On Reset (POR) .......................................................................................... 90
3.3.4 Debugger Reset (SYSRS) ....................................................................................... 91
3.3.5 Watchdog Reset (WDRS) ........................................................................................ 91
3.3.6 NMI Watchdog Reset (NMIWDRS) ............................................................................. 91
3.3.7 DCSM Safe Code Copy Reset (SCCRESET) ................................................................. 91
3.3.8 Hibernate Reset (HIBRESET) ................................................................................... 91
3.3.9 Hardware BIST Reset (HWBISTRS)............................................................................ 91
3.3.10 Test Reset (TRST) ............................................................................................... 92
3.4 Peripheral Interrupts ....................................................................................................... 92
3.4.1 Interrupt Concepts................................................................................................. 92
3.4.2 Interrupt Architecture.............................................................................................. 92
3.4.3 Interrupt Entry Sequence ......................................................................................... 93
3.4.4 Configuring and Using Interrupts ................................................................................ 94
3.4.5 PIE Channel Mapping ............................................................................................ 96
3.4.6 Vector Tables ...................................................................................................... 97
3.5 Exceptions and Non-Maskable Interrupts ............................................................................. 103
3.5.1 Configuring and Using NMIs ................................................................................... 103
3.5.2 Emulation Considerations ...................................................................................... 103
3.5.3 NMI Sources ...................................................................................................... 104
3.5.4 Illegal Instruction Trap (ITRAP) ................................................................................ 104
3.6 Safety Features ........................................................................................................... 104
3.6.1 Write Protection on Registers .................................................................................. 104
List of Figures
3-1. Device Interrupt Architecture ............................................................................................. 92
3-2. Interrupt Propagation Path ................................................................................................ 93
3-3. Missing Clock Detection Logic .......................................................................................... 106
3-4. ERRORSTS Pin Diagram ............................................................................................... 107
3-5. Clocking System .......................................................................................................... 108
3-6. Single-ended 3.3V External Clock ...................................................................................... 109
3-7. External Crystal ........................................................................................................... 109
3-8. External Resonator ....................................................................................................... 110
3-9. AUXCLKIN ................................................................................................................. 110
3-10. CPU-Timers ............................................................................................................... 117
3-11. CPU-Timer Interrupts Signals and Output Signal .................................................................... 118
3-12. CPU Watchdog Timer Module ......................................................................................... 119
3-13. Memory Architecture ..................................................................................................... 125
3-14. Arbitration Scheme on Global Shared Memories ..................................................................... 127
3-15. Arbitration Scheme on Local Shared Memories ...................................................................... 127
3-16. FMC Interface with Core, Bank and Pump ............................................................................ 134
3-17. Flash Prefetch Mode ..................................................................................................... 137
3-18. ECC Logic Inputs and Outputs.......................................................................................... 140
3-19. PUMP_OWNERSHIP Configuration ................................................................................... 144
3-20. Storage of Zone-Select Bits in OTP ................................................................................... 148
3-21. Location of Zone-Select Block Based on Link-Pointer ............................................................... 149
3-22. CSM Password Match Flow (PMF) ..................................................................................... 153
3-23. ECSL Password Match Flow (PMF) .................................................................................... 155
3-24. TIM Register ............................................................................................................... 160
3-25. PRD Register .............................................................................................................. 161
3-26. TCR Register .............................................................................................................. 162
3-27. TPR Register .............................................................................................................. 164
3-28. TPRH Register ............................................................................................................ 165
3-29. PIECTRL Register ........................................................................................................ 168
3-30. PIEACK Register.......................................................................................................... 169
3-31. PIEIER1 Register ......................................................................................................... 170
3-32. PIEIFR1 Register ......................................................................................................... 172
3-33. PIEIER2 Register ......................................................................................................... 174
3-34. PIEIFR2 Register ......................................................................................................... 176
3-35. PIEIER3 Register ......................................................................................................... 178
3-36. PIEIFR3 Register ......................................................................................................... 180
3-37. PIEIER4 Register ......................................................................................................... 182
3-38. PIEIFR4 Register ......................................................................................................... 184
3-39. PIEIER5 Register ......................................................................................................... 186
3-40. PIEIFR5 Register ......................................................................................................... 188
3-41. PIEIER6 Register ......................................................................................................... 190
3-42. PIEIFR6 Register ......................................................................................................... 192
3-43. PIEIER7 Register ......................................................................................................... 194
3-44. PIEIFR7 Register ......................................................................................................... 196
3-45. PIEIER8 Register ......................................................................................................... 198
3-46. PIEIFR8 Register ......................................................................................................... 200
3-47. PIEIER9 Register ......................................................................................................... 202
19-7. I2C Module Data Transfer (7-Bit Addressing with 8-bit Data Configuration Shown) ........................... 2184
19-8. I2C Module 7-Bit Addressing Format (FDF = 0, XA = 0 in I2CMDR) ............................................ 2184
19-9. I2C Module 10-Bit Addressing Format (FDF = 0, XA = 1 in I2CMDR) ........................................... 2184
19-10. I2C Module Free Data Format (FDF = 1 in I2CMDR) .............................................................. 2185
19-11. Repeated START Condition (in This Case, 7-Bit Addressing Format) ........................................... 2185
19-12. Synchronization of Two I2C Clock Generators During Arbitration ................................................ 2186
19-13. Arbitration Procedure Between Two Master-Transmitters ......................................................... 2187
19-14. Pin Diagram Showing the Effects of the Digital Loopback Mode (DLB) Bit ..................................... 2188
19-15. Enable Paths of the I2C Interrupt Requests ......................................................................... 2189
19-16. Backwards Compatibility Mode Bit, Slave Transmitter ............................................................. 2190
19-17. I2C_FIFO_interrupt...................................................................................................... 2191
19-18. I2COAR Register ........................................................................................................ 2194
19-19. I2CIER Register ......................................................................................................... 2195
19-20. I2CSTR Register ........................................................................................................ 2196
19-21. I2CCLKL Register ....................................................................................................... 2200
19-22. I2CCLKH Register....................................................................................................... 2201
19-23. I2CCNT Register ........................................................................................................ 2202
19-24. I2CDRR Register ........................................................................................................ 2203
19-25. I2CSAR Register ........................................................................................................ 2204
19-26. I2CDXR Register ........................................................................................................ 2205
19-27. I2CMDR Register........................................................................................................ 2206
19-28. I2CISRC Register ....................................................................................................... 2210
19-29. I2CEMDR Register ...................................................................................................... 2211
19-30. I2CPSC Register ........................................................................................................ 2212
19-31. I2CFFTX Register ....................................................................................................... 2213
19-32. I2CFFRX Register ....................................................................................................... 2215
20-1. Conceptual Block Diagram of the McBSP ........................................................................... 2222
20-2. McBSP Data Transfer Paths ........................................................................................... 2223
20-3. Companding Processes ................................................................................................ 2224
20-4. μ-Law Transmit Data Companding Format .......................................................................... 2224
20-5. A-Law Transmit Data Companding Format .......................................................................... 2224
20-6. Two Methods by Which the McBSP Can Compand Internal Data ................................................ 2225
20-7. Example - Clock Signal Control of Bit Transfer Timing ............................................................ 2225
20-8. McBSP Operating at Maximum Packet Frequency ................................................................. 2227
20-9. Single-Phase Frame for a McBSP Data Transfer ................................................................... 2228
20-10. Dual-Phase Frame for a McBSP Data Transfer ..................................................................... 2229
20-11. Implementing the AC97 Standard With a Dual-Phase Frame ..................................................... 2229
20-12. Timing of an AC97-Standard Data Transfer Near Frame Synchronization ...................................... 2230
20-13. McBSP Reception Physical Data Path ............................................................................... 2230
20-14. McBSP Reception Signal Activity ..................................................................................... 2230
20-15. McBSP Transmission Physical Data Path ........................................................................... 2231
20-16. McBSP Transmission Signal Activity ................................................................................. 2231
20-17. Conceptual Block Diagram of the Sample Rate Generator ........................................................ 2233
20-18. Possible Inputs to the Sample Rate Generator and the Polarity Bits ............................................ 2235
20-19. CLKG Synchronization and FSG Generation When GSYNC = 1 and CLKGDV = 1 ........................... 2237
20-20. CLKG Synchronization and FSG Generation When GSYNC = 1 and CLKGDV = 3 ........................... 2238
20-21. Overrun in the McBSP Receiver ...................................................................................... 2240
20-22. Overrun Prevented in the McBSP Receiver ......................................................................... 2241
20-23. Possible Responses to Receive Frame-Synchronization Pulses ................................................. 2241
22-30. USB Receive Functional Address Endpoint n Registers (USBFIFO[n]) ......................................... 2489
22-31. USB Receive Hub Address Endpoint n Registers (USBRXHUBADDR[n]) ...................................... 2490
22-32. USB Transmit Hub Port Endpoint n Registers (USBRXHUBPORT[n]) .......................................... 2491
22-33. USB Maximum Transmit Data Endpoint n Registers (USBTXMAXP[n]) ......................................... 2492
22-34. USB Control and Status Endpoint 0 Low Register (USBCSRL0) in Host Mode ................................ 2493
22-35. USB Control and Status Endpoint 0 Low Register (USBCSRL0) in Device Mode ............................. 2494
22-36. USB Control and Status Endpoint 0 High Register (USBCSRH0) in Host Mode ............................... 2495
22-37. USB Control and Status Endpoint 0 High Register (USBCSRH0) in Device Mode ............................ 2495
22-38. USB Receive Byte Count Endpoint 0 Register (USBCOUNT0)................................................... 2496
22-39. USB Type Endpoint 0 Register (USBTYPE0) ....................................................................... 2496
22-40. USB NAK Limit Register (USBNAKLMT) ............................................................................ 2497
22-41. USB Transmit Control and Status Endpoint n Low Register (USBTXCSRL[n]) in Host Mode ................ 2498
22-42. USB Transmit Control and Status Endpoint n Low Register (USBTXCSRL[n]) in Device Mode ............. 2499
22-43. USB Transmit Control and Status Endpoint n High Register (USBTXCSRH[n]) in Host Mode ............... 2501
22-44. USB Transmit Control and Status Endpoint n High Register (USBTXCSRH[n]) in Device Mode ............ 2502
22-45. USB Maximum Receive Data Endpoint n Registers (USBRXMAXP[n]) ......................................... 2503
22-46. USB Receive Control and Status Endpoint n Low Register (USBCSRL[n]) in Host Mode .................... 2504
22-47. USB Control and Status Endpoint n Low Register (USBCSRL[n]) in Device Mode ............................ 2505
22-48. USB Receive Control and Status Endpoint n High Register (USBCSRH[n]) in Host Mode ................... 2506
22-49. USB Control and Status Endpoint n High Register (USBCSRH[n]) in Device Mode ........................... 2507
22-50. USB Maximum Receive Data Endpoint n Registers (USBRXCOUNT[n]) ....................................... 2508
22-51. USB Host Transmit Configure Type Endpoint n Register (USBTXTYPE[n]) .................................... 2509
22-52. USB Host Transmit Interval Endpoint n Register (USBTXINTERVAL[n]) ....................................... 2510
22-53. USB Host Configure Receive Type Endpoint n Register (USBRXTYPE[n]) .................................... 2511
22-54. USB Host Receive Polling Interval Endpoint n Register (USBRXINTERVAL[n]) ............................... 2512
22-55. USB Request Packet Count in Block Transfer Endpoint n Registers (USBRQPKTCOUNT[n]) .............. 2513
22-56. USB Receive Double Packet Buffer Disable Register (USBRXDPKTBUFDIS) ................................. 2514
22-57. USB Transmit Double Packet Buffer Disable Register (USBTXDPKTBUFDIS) ................................ 2516
22-58. USB External Power Control Register (USBEPC) .................................................................. 2517
22-59. USB External Power Control Raw Interrupt Status Register (USBEPCRIS) .................................... 2519
22-60. USB External Power Control Interrupt Mask Register (USBEPCIM) ............................................. 2520
22-61. USB External Power Control Interrupt Status and Clear Register (USBEPCISC) .............................. 2521
22-62. USB Device RESUME Raw Interrupt Status Register (USBDRRIS) ............................................. 2522
22-63. USB Device RESUME Raw Interrupt Status Register (USBDRRIS) ............................................. 2523
22-64. USB Device RESUME Interrupt Status and Clear Register (USBDRISC)....................................... 2524
22-65. USB General-Purpose Control and Status Register (USBGPCS) ................................................ 2525
22-66. USB DMA Select Register (USBDMASEL) .......................................................................... 2526
23-1. uPP Integration .......................................................................................................... 2529
23-2. Functional Block Diagram .............................................................................................. 2530
23-3. RX in SDR or DDR (non-demux) Mode .............................................................................. 2531
23-4. RX in DDR (demux) Mode ............................................................................................. 2531
23-5. TX in SDR (non-interleave) or DDR (non-demux) Mode ........................................................... 2531
23-6. TX in SDR (interleave) or DDR (demux) Mode ..................................................................... 2531
23-7. IO Output Clock Generation for TX Mode............................................................................ 2532
23-8. IO Input clock for RX Mode ............................................................................................ 2532
23-9. Structure of DMA Window and Lines in Memory.................................................................... 2534
23-10. uPP Receive in SDR Mode ............................................................................................ 2536
23-11. uPP Transmit in SDR Mode ........................................................................................... 2537
23-12. uPP Transmit in SDR Mode – Interleaving .......................................................................... 2537
List of Tables
1-1. C2000Ware Root Directories ............................................................................................. 83
2-1. TMU Supported Instructions .............................................................................................. 86
2-2. Viterbi Decode Performance .............................................................................................. 87
2-3. Complex Math Performance .............................................................................................. 87
3-1. Reset Signals ............................................................................................................... 90
3-2. PIE Channel Mapping ..................................................................................................... 96
3-3. CPU Interrupt Vectors ..................................................................................................... 97
3-4. PIE Interrupt Vectors ....................................................................................................... 98
3-5. Access to EALLOW-Protected Registers .............................................................................. 104
3-6. Clock Connections Sorted by Clock Domain .......................................................................... 113
3-7. Clock Connections Sorted by Module Name .......................................................................... 114
3-8. Example Watchdog Key Sequences ................................................................................... 119
3-9. Local Shared RAM........................................................................................................ 126
3-10. Global Shared RAM ...................................................................................................... 126
3-11. Error Handling in Different Scenarios .................................................................................. 130
3-12. Mapping of ECC Bits in Read Data from ECC/Parity Address Map ............................................... 131
3-13. Mapping of Parity Bits in Read Data from ECC/Parity Address Map .............................................. 131
3-14. CLA Access Filter ......................................................................................................... 145
3-15. RAM Status ................................................................................................................ 145
3-16. Security Levels ............................................................................................................ 146
3-17. System Control Base Address Table................................................................................... 158
3-18. CPUTIMER_REGS Registers ........................................................................................... 159
3-19. CPUTIMER_REGS Access Type Codes .............................................................................. 159
3-20. TIM Register Field Descriptions ........................................................................................ 160
3-21. PRD Register Field Descriptions ....................................................................................... 161
3-22. TCR Register Field Descriptions........................................................................................ 162
3-23. TPR Register Field Descriptions ........................................................................................ 164
3-24. TPRH Register Field Descriptions ...................................................................................... 165
3-25. PIE_CTRL_REGS Registers ............................................................................................ 166
3-26. PIE_CTRL_REGS Access Type Codes ............................................................................... 166
3-27. PIECTRL Register Field Descriptions .................................................................................. 168
3-28. PIEACK Register Field Descriptions ................................................................................... 169
3-29. PIEIER1 Register Field Descriptions ................................................................................... 170
3-30. PIEIFR1 Register Field Descriptions ................................................................................... 172
3-31. PIEIER2 Register Field Descriptions ................................................................................... 174
3-32. PIEIFR2 Register Field Descriptions ................................................................................... 176
3-33. PIEIER3 Register Field Descriptions ................................................................................... 178
3-34. PIEIFR3 Register Field Descriptions ................................................................................... 180
3-35. PIEIER4 Register Field Descriptions ................................................................................... 182
3-36. PIEIFR4 Register Field Descriptions ................................................................................... 184
3-37. PIEIER5 Register Field Descriptions ................................................................................... 186
3-38. PIEIFR5 Register Field Descriptions ................................................................................... 188
3-39. PIEIER6 Register Field Descriptions ................................................................................... 190
3-40. PIEIFR6 Register Field Descriptions ................................................................................... 192
3-41. PIEIER7 Register Field Descriptions ................................................................................... 194
3-42. PIEIFR7 Register Field Descriptions ................................................................................... 196
3-43. PIEIER8 Register Field Descriptions ................................................................................... 198
20-17. Bit Values Required to Configure the McBSP as an SPI Slave ................................................... 2260
20-18. Register Bits Used to Reset or Enable the McBSP Receiver Field Descriptions ............................... 2262
20-19. Reset State of Each McBSP Pin ...................................................................................... 2262
20-20. Register Bit Used to Enable/Disable the Digital Loopback Mode ................................................. 2263
20-21. Receive Signals Connected to Transmit Signals in Digital Loopback Mode .................................... 2263
20-22. Register Bits Used to Enable/Disable the Clock Stop Mode ...................................................... 2263
20-23. Effects of CLKSTP, CLKXP, and CLKRP on the Clock Scheme ................................................. 2264
20-24. Register Bit Used to Enable/Disable the Receive Multichannel Selection Mode ............................... 2264
20-25. Register Bit Used to Choose One or Two Phases for the Receive Frame ...................................... 2264
20-26. Register Bits Used to Set the Receive Word Length(s) ............................................................ 2265
20-27. Register Bits Used to Set the Receive Frame Length .............................................................. 2265
20-28. How to Calculate the Length of the Receive Frame ................................................................ 2266
20-29. Register Bit Used to Enable/Disable the Receive Frame-Synchronization Ignore Function .................. 2266
20-30. Register Bits Used to Set the Receive Companding Mode ........................................................ 2267
20-31. Register Bits Used to Set the Receive Data Delay ................................................................. 2268
20-32. Register Bits Used to Set the Receive Sign-Extension and Justification Mode................................. 2270
20-33. Example: Use of RJUST Field With 12-Bit Data Value ABCh..................................................... 2270
20-34. Example: Use of RJUST Field With 20-Bit Data Value ABCDEh ................................................. 2270
20-35. Register Bits Used to Set the Receive Interrupt Mode ............................................................. 2271
20-36. Register Bits Used to Set the Receive Frame Synchronization Mode .......................................... 2271
20-37. Select Sources to Provide the Receive Frame-Synchronization Signal and the Effect on the FSR Pin..... 2272
20-38. Register Bit Used to Set Receive Frame-Synchronization Polarity ............................................... 2273
20-39. Register Bits Used to Set the SRG Frame-Synchronization Period and Pulse Width ......................... 2274
20-40. Register Bits Used to Set the Receive Clock Mode ............................................................... 2275
20-41. Receive Clock Signal Source Selection .............................................................................. 2276
20-42. Register Bit Used to Set Receive Clock Polarity .................................................................... 2276
20-43. Register Bits Used to Set the Sample Rate Generator (SRG) Clock Divide-Down Value ..................... 2278
20-44. Register Bit Used to Set the SRG Clock Synchronization Mode ................................................. 2278
20-45. Register Bits Used to Set the SRG Clock Mode (Choose an Input Clock) ...................................... 2279
20-46. Register Bits Used to Set the SRG Input Clock Polarity ........................................................... 2280
20-47. Register Bits Used to Place Transmitter in Reset Field Descriptions ............................................ 2281
20-48. Register Bit Used to Enable/Disable the Digital Loopback Mode ................................................. 2282
20-49. Receive Signals Connected to Transmit Signals in Digital Loopback Mode .................................... 2282
20-50. Register Bits Used to Enable/Disable the Clock Stop Mode ...................................................... 2282
20-51. Effects of CLKSTP, CLKXP, and CLKRP on the Clock Scheme ................................................. 2283
20-52. Register Bits Used to Enable/Disable Transmit Multichannel Selection ......................................... 2284
20-53. Use of the Transmit Channel Enable Registers .................................................................... 2284
20-54. Register Bit Used to Choose 1 or 2 Phases for the Transmit Frame ............................................ 2287
20-55. Register Bits Used to Set the Transmit Word Length(s) ........................................................... 2287
20-56. Register Bits Used to Set the Transmit Frame Length ............................................................. 2288
20-57. How to Calculate Frame Length ....................................................................................... 2288
20-58. Register Bit Used to Enable/Disable the Transmit Frame-Synchronization Ignore Function ................. 2289
20-59. Register Bits Used to Set the Transmit Companding Mode ....................................................... 2290
20-60. Register Bits Used to Set the Transmit Data Delay ................................................................ 2291
20-61. Register Bit Used to Set the Transmit DXENA (DX Delay Enabler) Mode ...................................... 2293
20-62. Register Bits Used to Set the Transmit Interrupt Mode ............................................................ 2293
20-63. Register Bits Used to Set the Transmit Frame-Synchronization Mode .......................................... 2294
20-64. How FSXM and FSGM Select the Source of Transmit Frame-Synchronization Pulses ....................... 2294
20-65. Register Bit Used to Set Transmit Frame-Synchronization Polarity .............................................. 2295
20-66. Register Bits Used to Set SRG Frame-Synchronization Period and Pulse Width .............................. 2296
20-67. Register Bit Used to Set the Transmit Clock Mode ................................................................. 2297
20-68. How the CLKXM Bit Selects the Transmit Clock and the Corresponding Status of the MCLKX pin ......... 2297
20-69. Register Bit Used to Set Transmit Clock Polarity ................................................................... 2297
20-70. McBSP Emulation Modes Selectable with FREE and SOFT Bits of SPCR2.................................... 2299
20-71. Reset State of Each McBSP Pin ...................................................................................... 2299
20-72. Receive Interrupt Sources and Signals .............................................................................. 2304
20-73. Transmit Interrupt Sources and Signals .............................................................................. 2304
20-74. Error Flags ............................................................................................................... 2305
20-75. McBSP Mode Selection ................................................................................................ 2305
20-76. McBSP Base Address Table........................................................................................... 2308
20-77. McBSP Register Summary............................................................................................. 2308
20-78. Serial Port Control 1 Register (SPCR1) Field Descriptions ....................................................... 2310
20-79. Serial Port Control 2 Register (SPCR2) Field Descriptions........................................................ 2313
20-80. Receive Control Register 1 (RCR1) Field Descriptions ............................................................ 2315
20-81. Frame Length Formula for Receive Control 1 Register (RCR1) .................................................. 2316
20-82. Receive Control Register 2 (RCR2) Field Descriptions ............................................................ 2316
20-83. Frame Length Formula for Receive Control 2 Register (RCR2) .................................................. 2317
20-84. Transmit Control 1 Register (XCR1) Field Descriptions ........................................................... 2318
20-85. Frame Length Formula for Transmit Control 1 Register (XCR1) ................................................. 2318
20-86. Transmit Control 2 Register (XCR2) Field Descriptions ........................................................... 2319
20-87. Frame Length Formula for Transmit Control 2 Register (XCR2) ................................................. 2320
20-88. Sample Rate Generator 1 Register (SRGR1) Field Descriptions ................................................. 2321
20-89. Sample Rate Generator 2 Register (SRGR2) Field Descriptions ................................................. 2322
20-90. Multichannel Control 1 Register (MCR1) Field Descriptions ...................................................... 2323
20-91. Multichannel Control 2 Register (MCR2) Field Descriptions ...................................................... 2325
20-92. Pin Control Register (PCR) Field Descriptions ...................................................................... 2327
20-93. Pin Configuration ....................................................................................................... 2329
20-94. Receive Channel Enable Registers (RCERA...RCERH) Field Descriptions..................................... 2329
20-95. Use of the Receive Channel Enable Registers ..................................................................... 2330
20-96. Transmit Channel Enable Registers (XCERA...XCERH) Field Descriptions .................................... 2331
20-97. Use of the Transmit Channel Enable Registers .................................................................... 2332
20-98. McBSP Interrupt Enable Register (MFFINT) Field Descriptions .................................................. 2333
20-99. MCBSP Registers to Driverlib Functions ............................................................................. 2334
21-1. CAN Register Access From Software ................................................................................ 2340
21-2. CAN Register Access From CCS ..................................................................................... 2341
21-3. PIE Nomenclature for Interrupts ....................................................................................... 2347
21-4. Programmable Ranges Required by CAN Protocol ................................................................ 2357
21-5. Message Object Field Descriptions ................................................................................... 2366
21-6. Message RAM Addressing in Debug Mode ......................................................................... 2368
21-7. CAN Base Address Table .............................................................................................. 2370
21-8. CAN_REGS Registers .................................................................................................. 2371
21-9. CAN_REGS Access Type Codes ..................................................................................... 2372
21-10. CAN_CTL Register Field Descriptions ............................................................................... 2373
21-11. CAN_ES Register Field Descriptions ................................................................................. 2376
21-12. CAN_ERRC Register Field Descriptions ............................................................................. 2378
21-13. CAN_BTR Register Field Descriptions ............................................................................... 2379
21-14. CAN_INT Register Field Descriptions ................................................................................ 2381
21-15. CAN_TEST Register Field Descriptions.............................................................................. 2382
22-15. USB Interrupt Enable Register (USBIE) in Device Mode Field Descriptions .................................... 2473
22-16. Frame Number Register (FRAME) Field Descriptions ............................................................. 2474
22-17. USB Endpoint Index Register (USBEPIDX) Field Descriptions ................................................... 2474
22-18. USB Test Mode Register (USBTEST) in Host Mode Field Descriptions......................................... 2475
22-19. USB Test Mode Register (USBTEST) in Device Mode Field Descriptions ...................................... 2475
22-20. USB FIFO Endpoint n Register (USBFIFO[n]) Field Descriptions ................................................ 2477
22-21. USB Device Control Register (USBDEVCTL) Field Descriptions ................................................. 2478
22-22. USB Transmit Dynamic FIFO Sizing Register (USBTXFIFOSZ) Field Descriptions ........................... 2480
22-23. USB Receive Dynamic FIFO Sizing Register (USBRXFIFOSZ) Field Descriptions ............................ 2481
22-24. USB Transmit FIFO Start Address Register (USBTXFIFOADDR) Field Descriptions ......................... 2482
22-25. USB Receive FIFO Start Address Register (USBRXFIFOADDR) Field Descriptions .......................... 2483
22-26. USB Connect Timing Register (USBCONTIM) Field Descriptions................................................ 2484
22-27. USB Full-Speed Last Transaction to End of Frame Timing Register (USBFSEOF) Field Descriptions ..... 2485
22-28. USB Low-Speed Last Transaction to End of Frame Timing Register (USBLSEOF) Field Descriptions..... 2485
22-29. USB Transmit Functional Address Endpoint n Registers (USBTXFUNCADDR[n]) Field Descriptions ...... 2486
22-30. USB Transmit Hub Address Endpoint n Registers(USBTXHUBADDR[n]) Field Descriptions ................ 2487
22-31. USB Transmit Hub Port Endpoint n Registers(USBTXHUBPORT[n]) Field Descriptions ..................... 2488
22-32. USB Recieve Functional Address Endpoint n Registers(USBFIFO[n]) Field Descriptions .................... 2489
22-33. USB Receive Hub Address Endpoint n Registers(USBRXHUBADDR[n]) Field Descriptions ................ 2490
22-34. USB Transmit Hub Port Endpoint n Registers(USBRXHUBPORT[n]) Field Descriptions ..................... 2491
22-35. USB Maximum Transmit Data Endpoint n Registers(USBTXMAXP[n]) Field Descriptions ................... 2492
22-36. USB Control and Status Endpoint 0 Low Register(USBCSRL0) in Host Mode Field Descriptions .......... 2493
22-37. USB Control and Status Endpoint 0 Low Register (USBCSRL0) in Device Mode Field Descriptions ....... 2494
22-38. USB Control and Status Endpoint 0 High Register (USBCSRH0) in Host Mode Field Descriptions......... 2495
22-39. USB Control and Status Endpoint 0 High Register (USBCSRH0) in Device Mode Field Descriptions ...... 2495
22-40. USB Receive Byte Count Endpoint 0 Register (USBCOUNT0) Field Descriptions ............................ 2496
22-41. USB Type Endpoint 0 Register (USBTYPE0) Field Descriptions ................................................. 2496
22-42. USB NAK Limit Register (USBNAKLMT) Field Descriptions ...................................................... 2497
22-43. USB Transmit Control and Status Endpoint n Low Register (USBTXCSRL[n]) in Host Mode Field
Descriptions .............................................................................................................. 2498
22-44. USB Transmit Control and Status Endpoint n Low Register (USBTXCSRL[n]) in Device Mode Field
Descriptions .............................................................................................................. 2499
22-45. USB Transmit Control and Status Endpoint n High Register (USBTXCSRH[n]) in Host Mode Field
Descriptions .............................................................................................................. 2501
22-46. USB Transmit Control and Status Endpoint n High Register (USBTXCSRH[n]) in Device Mode Field
Descriptions .............................................................................................................. 2502
22-47. USB Maximum Receive Data Endpoint n Registers (USBTXMAXP[n]) Field Descriptions ................... 2503
22-48. USB Control and Status Endpoint n Low Register(USBCSRL[n]) in Host Mode Field Descriptions ......... 2504
22-49. USB Control and Status Endpoint 0 Low Register(USBCSRL[n]) in Device Mode Field Descriptions ...... 2505
22-50. USB Control and Status Endpoint n High Register (USBCSRH[n]) in Host Mode Field Descriptions ....... 2506
22-51. USB Control and Status Endpoint 0 High Register(USBCSRH[n]) in Device Mode Field Descriptions ..... 2507
22-52. USB Maximum Receive Data Endpoint n Registers (USBRXCOUNT[n]) Field Descriptions ................. 2508
22-53. USB Host Transmit Configure Type Endpoint n Register(USBTXTYPE[n]) Field Descriptions .............. 2509
22-54. USBTXINTERVAL[n] Frame Numbers ............................................................................... 2510
22-55. USB Host Transmit Interval Endpoint n Register(USBTXINTERVAL[n]) Field Descriptions .................. 2510
22-56. USB Host Configure Receive Type Endpoint n Register(USBRXTYPE[n]) Field Descriptions ............... 2511
22-57. USBRXINTERVAL[n] Frame Numbers ............................................................................... 2512
22-58. USB Host Receive Polling Interval Endpoint n Register(USBRXINTERVAL[n]) Field Descriptions.......... 2512
22-59. USB Request Packet Count in Block Transfer Endpoint n Registers (USBRQPKTCOUNT[n]) Field
Descriptions .............................................................................................................. 2513
22-60. USB Receive Double Packet Buffer Disable Register (USBRXDPKTBUFDIS) Field Descriptions .......... 2514
22-61. USB Transmit Double Packet Buffer Disable Register (USBTXDPKTBUFDIS) Field Descriptions .......... 2516
22-62. USB External Power Control Register (USBEPC) Field Descriptions ............................................ 2517
22-63. USB External Power Control Raw Interrupt Status Register (USBEPCRIS) Field Descriptions .............. 2519
22-64. USB External Power Control Interrupt Mask Register (USBEPCIM) Field Descriptions....................... 2520
22-65. USB External Power Control Interrupt Status and Clear Register (USBEPCISC) Field Descriptions ....... 2521
22-66. USB Device RESUME Raw Interrupt Status Register (USBDRRIS) Field Descriptions....................... 2522
22-67. USB Device RESUME Raw Interrupt Status Register (USBDRRIS) Field Descriptions....................... 2523
22-68. USB Device RESUME Interrupt Status and Clear Register (USBDRISC) Field Descriptions ................ 2524
22-69. USB General-Purpose Control and Status Register (USBGPCS) Field Descriptions .......................... 2525
22-70. USB DMA Select Register (USBDMASEL) Field Descriptions .................................................... 2526
23-1. uPP Signal Description ................................................................................................. 2533
23-2. CPU/CLA/uPP-DMA Address Map.................................................................................... 2540
23-3. CPU/CLA/uPP-DMA Address Map.................................................................................... 2541
23-4. uPP Parameters Useful for System Tuning .......................................................................... 2542
23-5. UPP Base Address Table .............................................................................................. 2543
23-6. UPP_REGS Registers .................................................................................................. 2544
23-7. UPP_REGS Access Type Codes ..................................................................................... 2544
23-8. PID Register Field Descriptions ....................................................................................... 2546
23-9. PERCTL Register Field Descriptions ................................................................................. 2547
23-10. CHCTL Register Field Descriptions ................................................................................... 2549
23-11. IFCFG Register Field Descriptions.................................................................................... 2550
23-12. IFIVAL Register Field Descriptions ................................................................................... 2552
23-13. THCFG Register Field Descriptions .................................................................................. 2553
23-14. RAWINTST Register Field Descriptions.............................................................................. 2555
23-15. ENINTST Register Field Descriptions ................................................................................ 2557
23-16. INTENSET Register Field Descriptions .............................................................................. 2559
23-17. INTENCLR Register Field Descriptions .............................................................................. 2561
23-18. CHIDESC0 Register Field Descriptions .............................................................................. 2563
23-19. CHIDESC1 Register Field Descriptions .............................................................................. 2564
23-20. CHIDESC2 Register Field Descriptions .............................................................................. 2565
23-21. CHIST0 Register Field Descriptions .................................................................................. 2566
23-22. CHIST1 Register Field Descriptions .................................................................................. 2567
23-23. CHIST2 Register Field Descriptions .................................................................................. 2568
23-24. CHQDESC0 Register Field Descriptions ............................................................................. 2569
23-25. CHQDESC1 Register Field Descriptions ............................................................................. 2570
23-26. CHQDESC2 Register Field Descriptions ............................................................................. 2571
23-27. CHQST0 Register Field Descriptions ................................................................................. 2572
23-28. CHQST1 Register Field Descriptions ................................................................................. 2573
23-29. CHQST2 Register Field Descriptions ................................................................................. 2574
23-30. GINTEN Register Field Descriptions ................................................................................. 2575
23-31. GINTFLG Register Field Descriptions ................................................................................ 2576
23-32. GINTCLR Register Field Descriptions ................................................................................ 2577
23-33. DLYCTL Register Field Descriptions ................................................................................. 2578
24-1. Configuration for EMIF1 and EMIF2 Modules ....................................................................... 2580
24-2. EMIF Pins Used to Access Both SDRAM and Asynchronous Memories ........................................ 2583
24-3. EMIF Pins Specific to SDRAM ........................................................................................ 2583
24-4. EMIF Pins Specific to Asynchronous Memory ...................................................................... 2584
24-5. EMIF SDRAM Commands ............................................................................................. 2584
This Technical Reference Manual (TRM) details the integration, the environment, the functional
description, and the programming models for each peripheral and subsystem in the device.
The TRM should not be considered a substitute for the data manual, rather a companion guide that should
be used alongside the device-specific data manual to understand the details to program the device. The
primary purpose of the TRM is to abstract the programming details of the device from the data manual.
This allows the data manual to outline the high-level features of the device without unnecessary
information about register descriptions or programming models.
Notational Conventions
This document uses the following conventions.
• Hexadecimal numbers may be shown with the suffix h or the prefix 0x. For example, the following
number is 40 hexadecimal (decimal 64): 40h or 0x40.
• Registers in this document are shown in figures and described in tables.
– Each register figure shows a rectangle divided into fields that represent the fields of the register.
Each field is labeled with its bit name, its beginning and ending bit numbers above, and its
read/write properties with default reset value below. A legend explains the notation used for the
properties.
– Reserved bits in a register figure can have one of multiple meanings:
• Not implemented on the device
• Reserved for future device expansion
• Reserved for TI testing
• Reserved configurations of the device that are not supported
– Writing nondefault values to the Reserved bits could cause unexpected behavior and should be
avoided.
Glossary
TI Glossary — This glossary lists and explains terms, acronyms, and definitions.
C2000Ware for C2000™ Microcontrollers is a cohesive set of development software and documentation
designed to minimize software development time. From device-specific drivers and libraries to device
peripheral examples, C2000Ware provides a solid foundation to begin development and evaluation of your
product.
1.1 Introduction
C2000Ware for C2000™ Microcontrollers is a cohesive set of development software and documentation
designed to minimize software development time. From device-specific drivers and libraries to device
peripheral examples, C2000Ware provides a solid foundation to begin development and evaluation of your
product.
C2000Ware can be downloaded from: www.ti.com/tool/C2000WARE
1.3 Documentation
Within C2000Ware, there is an extensive amount of development documentation ranging from board
design documentation, to library user's guides, to driver API documentation. The "boards" directory
contains all the hardware design, BOM, gerber files, and more for controlCARDs. To assist with locating
the necessary documentation, an HTML page is provided that contains a full list of all the documents in
the C2000Ware package. Locate this page in the "docs" directory.
1.4 Devices
C2000Ware contains the necessary software and documentation to jumpstart development for C2000
microcontrollers. Each device includes device-specific common source files, peripheral example projects,
bit field headers, and if available, a device peripheral driver library. Additionally, documentation is provided
for each device on how to set up a CCS project, as well as give an overview of all the included example
projects and assist with troubleshooting. For devices with a driver library, documentation is also included
that details all the peripheral APIs available.
To learn more about C2000 microcontrollers, visit www.ti.com/c2000.
1.5 Libraries
The libraries included in C2000Ware range from fixed point and floating point math libraries, to specialized
DSP libraries, as well as calibration libraries. Each library includes documentation and examples, where
applicable. Additionally, the flash API files and boot ROM source code are located in the "libraries"
directory.
All projects and examples in C2000Ware are built for and tested with TI’s Code Composer Studio.
Although Code Composer Studio is not included with the C2000Ware installer, it is easily obtainable in a
variety of versions.
C28x Processor
This chapter contains a short description of the C28x Processor and extended instruction sets.
Further information can be found in the following document(s):
TMS320C28x CPU and Instruction Set Reference Guide
TMS320C28x Extended Instruction Sets Technical Reference Manual
Accelerators: Enhancing the Capabilities of the C2000 MCU Family Technical Brief
TMS320C28x FPU Primer
2.1 Introduction
The C28x CPU is a 32-bit fixed-point processor. This device draws from the best features of digital signal
processing, reduced instruction set computing (RISC), microcontroller architectures, firmware, and tool
sets.
For more information on CPU architecture and instruction set, see the TMS320C28x CPU and Instruction
Set Reference Guide.
2.2 Features
The CPU features include a modified Harvard architecture and circular addressing. The RISC features are
single-cycle instruction execution, register-to-register operations, and modified Harvard architecture. The
microcontroller features include ease of use through an intuitive instruction set, byte packing and
unpacking, and bit manipulation. The modified Harvard architecture of the CPU enables instruction and
data fetches to be performed in parallel. The CPU can read instructions and data while it writes data
simultaneously to maintain the single-cycle instruction operation across the pipeline.
No changes have been made to existing instructions, pipeline or memory bus architecture. All TMU
instructions use the existing FPU register set (R0H to R7H) to carry out their operations.
For more information, see the TMS320C28x Extended Instruction Sets Technical Reference Manual .
NOTE: Only the CRC-related VCU instructions will be supported in future devices. FFT algorithms
are available for the C28x+FPU.
For more information, see the TMS320C28x Extended Instruction Sets Technical Reference Manual .
System Control
This chapter explains system control and interrupts found on this MCU. The system control module
configures and manages the overall operation of the device and provides information about the device
status. Configurable features in system control include reset control, NMI operation, power control, clock
control, and low-power modes.
3.1 Introduction
The register space of the device system control module is divided into three categories and will be
explained further in this chapter. They are:
1. System Control Device Configuration Registers (DEV_CFG_REGS). The base address of these
registers begins at 0x5D000.
2. System Control Clock Configuration Registers (CLK_CFG_REGS). The base address of these
registers begins at 0x5D200.
3. System control CPU Subsystem Registers (CPU_SYS_REGS). The base address of these registers
begins at 0x5D300.
3.3 Resets
This section explains the types and effects of the different resets on this device.
After a POR, the POR and XRSn bits in RESC are set. These bits are then cleared by the boot ROM.
CPU1.TINT0
CPU1.TIMER0
CPU1
INPUTXBAR4 CPU1.XINT1 Control
GPIO0
GPIO1 INPUTXBAR5 CPU1.XINT2 Control INT1
...
Input CPU1.XINT3 Control
CPU1. to
INPUTXBAR6
... X-BAR CPU1.XINT4 Control
ePIE INT12
INPUTXBAR13
GPIOx
INPUTXBAR14 CPU1.XINT5 Control
CPU1.TINT1
CPU1.TIMER1 INT13
CPU1.TINT2
CPU1.TIMER2 INT14
Peripherals
PIEIERx.2
Peripheral 0 Set
PIEIFRx.2 1 PIEACK.x IER.x ST1.INTM
Interrupt
Latch 1 0 1
CPU
B 0 IFR.x 1 0
Interrupt
Latch
Logic
PIEIERx.16
0
Peripheral
PIEIFRx.16 1
Interrupt
Latch
P
When a peripheral generates an interrupt (on PIE group x, channel y), it triggers the following sequence of
events:
1. The interrupt is latched in PIEIFRx.y.
2. If PIEIERx.y is set, the interrupt propagates.
3. If PIEACK.x is clear, the interrupt propagates and PIEACK.x is set.
4. The interrupt is latched in IFR.x.
5. If IER.x is set, the interrupt propagates.
6. If INTM is clear, the CPU receives the interrupt.
7. Any instructions in the D2 or later stage of the pipeline are run to completion. Instructions in earlier
stages are flushed.
8. The CPU saves its context on the stack.
9. IFR.x and IER.x are cleared. INTM is set. EALLOW is cleared.
10. The CPU fetches the ISR vector from the PIE. PIEIFRx.y is cleared.
11. The CPU branches to the ISR.
The interrupt latency is the time between PIEIFRx.y latching the interrupt and the first ISR instruction
entering the execution stage of the CPU pipeline. The minimum interrupt latency is 14 SYSCLK cycles.
Wait states on the ISR or stack memories will add to the latency. External interrupts add a minimum of two
SYSCLK cycles for GPIO synchronization plus extra time for input qualification (if used). Loops created
using the C28x RPT instruction cannot be interrupted.
The PIEACK bit for the interrupt group must be cleared manually in user code. This is normally done at
the end of the ISR. If the PIEACK bit is not cleared, the CPU will not receive any further interrupts from
that group. This does not apply to the Timer1 and Timer2 interrupts, which do not go through the PIE.
CPU Suspended When the CPU is suspended, the NMI watchdog counter will
be suspended.
Run-Free Mode When the CPU is placed in run-free mode, the NMI watchdog
counter will resume operation as normal.
Real-Time Single-Step Mode When the CPU is in real-time single-step mode, the NMI
watchdog counter will be suspended. The counter remains
suspended even within real-time interrupts.
Real-Time Run-Free Mode When the CPU is in real-time run-free mode, the NMI
watchdog counter operates as normal.
NOTE: A RAM fetch access violation will trigger an ITRAP in addition to the normal peripheral
interrupt for RAM access violations. The CPU will handle the ITRAP first.
At reset, the EALLOW bit is cleared, enabling EALLOW protection. While protected, all writes to protected
registers by the CPU are ignored and only CPU reads, JTAG reads, and JTAG writes are allowed. If this
bit is set, by executing the EALLOW instruction, the CPU is allowed to write freely to protected registers.
After modifying registers, they can once again be protected by executing the EDIS instruction to clear the
EALLOW bit.
CLKSRCCTL1.OSCCLRSRCSEL /1,
Switch
SYSPLL /2,
Ckt
/4
Mux
PLLRAWCLK ..
(glitch- PLLSYSCLK
/124
PLL Locking free)
/126
Registers Control
Ckt
Clock Dividers
3.6.5 NMIWDs
CPU1 has a user-programmable NMIWD period register in which users can set a limit on how much time
they want to allocate for the device to acknowledge the NMI. If the NMI is not acknowledged, it will cause
a device reset.
CPU1.NMIWD.NMISHDFLG.Bit-0
CPU1.NMIWD.NMISHDFLG.Bit-1
ERROR
CPU1.NMIWD.NMISHDFLG.Bit-15
3.7 Clocking
This section explains the clock sources and clock domains on this device, and how to configure them for
application use. Figure 3-5 provides an overview of the device's clocking system.
To ePIEs, LS RAMs,
CPU1.SYSCLK CLA message RAMs,
and DCSMs
One per SYSCLK peripheral
PCLKCRx
PERx.SYSCLK To peripherals
EPWMCLKDIV PCLKCRx
HRPWM
PCLKCRx
HRPWMCLK To HRPWMs
CLKSRCCTL2
AUXCLK
AUXOSCCLK AUXPLLCLK To USB bit clock
Divider
Auxiliary PLL AUXPLLRAWCLK
Note that the default/2 divider for ePWMs and EMIFs is not shown.
VDDOSC X1 VSSOSC X2
3.3V NC
3.3V
Clk
VDD OUT
GND
3.3V Oscillator
• An external crystal. The crystal should be connected across X1 and X2 with its load capacitors
connected to VSSOSC as shown in Figure 3-7.
VDDOSC X1 VSSOSC X2
3.3V
Crystal
RD CL2 CL1
• An external resonator. The resonator should be connected across X1 and X2 with its ground
connected to VSSOSC as shown in Figure 3-8.
VDDOSC X1 VSSOSC X2
3.3V
Resonator
3.7.4 XCLKOUT
It is sometimes necessary to observe a clock directly for debug and testing purposes. The external clock
output (XCLKOUT) feature supports this by connecting a clock to an external pin, GPIO73. The available
clock sources are PLLSYSCLK, PLLRAWCLK, SYSCLK, AUXPLLRAWCLK, INTOSC1, and INTOSC2.
To use XCLKOUT, first select the clock source via the CLKSRCCTL3 register. Next, select the desired
output divider via the XCLKOUTDIVSEL register. Finally, connect GPIO73 to mux channel 3 using the
GPIO configuration registers.
NOTE: The system clock frequency (PLLSYSCLK) may not exceed the limit specified in the
datasheet. This limit does not allow for oscillator tolerance.
NOTE: If the AUXOSCCLK source is changed on the same AUXOSCCLK cycle as the multiplier, the
PLL will be disabled but the AUXPLLMULT register will show the written value. This can
happen when the system PLL is enabled before configuring the auxiliary PLL (CPUCLK >>
AUXOSCCLK). To avoid this issue, wait two AUXOSCCLK cycles between changing the
clock source and writing to AUXPLLMULT.
CLKSRCCTL1.OSCCLKSRCSEL = 0x1
SYSPLLMULT.IMULT = 26 (0x1A)
SYSPLLMULT.FMULT = .50 (0x2)
SYSCLKDIVSEL.PLLSYSCLKDIV = 4 (0x2)
SYSPLLCTL1.PLLCLKEN = 1
PERCLKDIVSEL.EPWMCLKDIV = 1 (0x0)
PERCLKDIVSEL.EMIF1CLKDIV = 1 (0x0)
PERCLKDIVSEL.EMIF2CLKDIV = 1 (0x0)
CLKSRCCTL2.AUXOSCCLKSRCSEL = 0x1
AUXPLLMULT.IMULT = 8 (0x08)
AUXPLLMULT.FMULT = .00 (0x0)
AUXCLKDIVSEL.AUXPLLDIV = 2 (0x1)
AUXPLLCTL1.PLLCLKEN = 1
This gives a PLLRAWCLK of 397.5 MHz and an AUXPLLRAWCLK of 120 MHz, both of which are in the
acceptable range. The CPU frequency is 99.375 MHz. Crystals have tight frequency tolerances, which
should keep the system clock from exceeding 100 MHz. The USB frequency is exactly 60 MHz. Since the
CPU frequency is less than 100 MHz, the ePWM and EMIF clock dividers can be set to /1.
Example 2: Using INTOSC2 (10 MHz) as a reference, generate a CPU frequency of 200 MHz - 3%:
CLKSRCCTL1.OSCCLKSRCSEL = 0x0
SYSPLLMULT.IMULT = 38 (0x26)
SYSPLLMULT.FMULT = .75 (0x3)
SYSCLKDIVSEL.PLLSYSCLKDIV = 2 (0x1)
SYSPLLCTL1.PLLCLKEN = 1
Reset
Timer reload
Borrow
TINT
INT1 TINT0
to PIE TIMER0
INT12
28x
CPU
TINT1
INT13 TIMER1
TINT2
INT14 TIMER2
A The timer registers are connected to the memory bus of the C28x processor.
B The CPU Timers are synchronized to SYSCLKOUT.
WDCR(WDPS(2:0)) WDCR(WDDIS)
WDCNTR(7:0)
WDWCR(MIN(7:0))
WDKEY(7:0) Watchdog
In Window
Watchdog Window
Good Key Out of Window
Key Detector Detector
Bad Key
55 + AA
WDRSTn
Generate
512-WDCLK
WDINTn Watchdog Timeout
Output Pulse
SCSR(WDENINT)
Step 3 in Table 3-8 is the first action that enables the WDCNTR to be reset. The WDCNTR is not actually
reset until step 6. Step 8 again re-enables the WDCNTR to be reset and step 9 resets the WDCNTR. Step
10 again re-enables the WDCNTR to be reset. Writing the wrong key value to the WDKEY in step 11
causes no action, however the WDCNTR is no longer enabled to be reset and the 0xAA in step 12 now
has no effect.
If the watchdog is configured to reset the device, then a WDCR overflow or writing the incorrect value to
the WDCR[WDCHK] bits will reset the device and set the watchdog flag (WDRSn) in the reset cause
register (RESC). After a reset, the program can read the state of this flag to determine whether the reset
was caused by the watchdog. After doing this, the program should clear WDRSn to allow subsequent
watchdog resets to be detected. Watchdog resets are not prevented when the flag is set.
CPU Suspended: When the CPU is suspended, the watchdog clock (WDCLK) is suspended
Run-Free Mode: When the CPU is placed in run-free mode, then the watchdog module
resumes operation as normal.
Real-Time Single-Step When the CPU is in real-time single-step mode, the watchdog clock
Mode: (WDCLK) is suspended. The watchdog remains suspended even within real-
time interrupts.
Real-Time Run-Free When the CPU is in real-time run-free mode, the watchdog operates as
Mode: normal.
3.10.1 IDLE
IDLE is a standard feature of the C28x CPU. In this mode, the CPU clock is gated while all peripheral
clocks are left running. IDLE can thus be used to conserve power while a CPU is waiting for peripheral
events.
Any enabled interrupt will wake the CPU up from IDLE mode.
To enter IDLE mode, set LPMCR.LPM to 0x0 and execute the IDLE instruction.
3.10.2 STANDBY
STANDBY is a more aggressive low-power mode that gates both the CPU clock and any peripheral clocks
derived from the CPU's SYSCLK. The watchdog however, is left active. STANDBY is best suited for an
application where the wake-up signal will come from an external system rather than a peripheral input.
An NMI (or optionally) a watchdog interrupt or a configured GPIO can wake the CPU from STANDBY
mode. Each GPIO from GPIO0-63 can be configured to wake the CPU when they are driven active low.
Upon wakeup, the CPU receives the WAKEINT interrupt if configured.
To enter STANDBY mode:
1. Set LPMCR.LPM to 0x1.
2. Enable the WAKEINT interrupt in the PIE.
3. For watchdog interrupt wakeup, set LPMCR.WDINTE to 1 and configure the watchdog to generate
interrupts.
4. For GPIO wakeup, set GPIOLPMSEL0 and GPIOLPMSEL1 to connect the chosen GPIOs to the LPM
module, and set LPMCR.QUALSTDBY to select the number of OSCCLK cycles for input qualification.
5. Execute the IDLE instruction to enter STANDBY.
To wake up from Standby mode:
1. Configure the desired GPIO to trigger the wakeup.
2. Drive the selected GPIO signal low; it must remain low for the number of OSCCLK cycles specified in
the QUALSTDBY bits in the LPMCR register. If the signal is sampled high during this period, the count
restarts.
At the end of the qualification period, the PLL enables the CLKIN to the CPU and the WAKEINT interrupt
is latched in the PIE block. The WAKEINT interrupt can also be triggered by a watchdog interrupt.
The CPU is now out of STANDBY mode and can resume normal execution.
3.10.3 HALT
HALT is a global low-power mode that gates almost all system clocks and allows for power-down of
oscillators and analog blocks. HALT can be used for additional power savings over putting the CPU in
STANDBY, although the options for wakeup are more limited.
Similar to STANDBY, any of GPIO0-63 can be configured to wake up the system from HALT. No other
wakeup option is available. However, CPU1's watchdog may still be clocked, and can be configured to
produce a watchdog reset if a timeout mechanism is needed. On wakeup, the CPU receives a WAKEINT
interrupt.
To enter HALT mode:
1. Disable all interrupts with the exception of the WAKEINT interrupt . The other interrupts can be
reenabled after the device is brought out of HALT mode.
2. Set LPMCR.LPM to 0x2. Set GPIOLPMSEL0 and GPIOLPMSEL1 to connect the chosen GPIOs to the
LPM module.
3. Set CLKSRCCTL1.WDHALTI to 1 to keep the CPU1 watchdog active and INTOSC1 and INTOSC2
powered up in HALT.
4. Set CLKSRCCTL1.WDHALTI to 0 to disable the CPU1 watchdog and power down INTOSC1 and
INTOSC2 in HALT.
5. Execute the IDLE instruction on CPU1 to enter HALT.
If an interrupt or NMI is received while the IDLE instruction is in the pipeline, the system will begin
executing the WAKEINT ISR. After HALT wakeup, ISR execution will resume where it left off.
NOTE: Before entering HALT mode, if the system PLL is locked (SYSPLL.LOCKS = 1), it must also be
connected to the system clock (PLLCTL1.PLLCLKEN = 1). Otherwise, the device will never wake up.
To wake up from HALT mode:
1. Drive the selected GPIO low for a minimum 5us. This will activate the CPU1.WAKEINT PIE interrupt.
2. Drive the wake-up GPIO high again to initiate the powering up of the SYSPLL and AUXPLL
3. Wait 16us plus 1024 OSCLK cycles to allow the PLLs to lock and the WAKEINT ISR to be latched.
4. Execute the WAKEINT ISR.
The device is now out of HALT mode and can resume normal execution.
3.10.4 HIB
Hibernate (HIB) is a global low-power mode that gates the supply voltages to most of the system. HIB is
essentially a controlled power-down with remote wakeup capability, and can be used to save power during
long periods of inactivity. Because gating the supply voltage corrupts the state of the logic, a reset is
required to exit HIB. To prevent external systems from being affected by the reset, HIB provides isolation
of the I/O pin states as well as low-power data retention via the M0 and M1 memories.
Unlike the clock-gating modes, HIB does not have a true wakeup. Instead, GPIO41 becomes HIBWAKE,
an asynchronous reset signal. When the boot ROM detects a HIB wakeup, it will avoid clearing M0 and
M1 and call a user-specified I/O restore function. To prevent glitches on internal and external signals, XRS
will also generate a HIBWAKE signal during HIB. The I/O restore function should set up the GPIO control
registers to match their pre-HIB state, then write a 1 to LPMCR.IOISODIS to deactivate I/O isolation. If the
restore function does not disable isolation, the boot ROM will do it.
To enter HIB mode:
1. Save any necessary state to the M0 and M1 memories.
2. Put all I/Os in the desired state for isolation and deactivate any analog modules in use.
3. Write the address of the I/O restore function for the CPU to its IORESTOREADDR register.
4. Bypass the PLL by setting PLLCLKEN to 0.
5. Set CPU1's LPMCR.LPM to 0x3 and execute the IDLE instruction.
Any debugger connection will be lost on HIB entry since the JTAG logic is powered down.
Due to the loss of system state on HIB entry, it is possible for error information to be lost if an NMI is
triggered while the IDLE instruction is in the pipeline. The ERRORSTS pin will be set and remain set until
I/O isolation is disabled, but there will be no way to tell what caused the error.
To wake the device from HIB mode:
1. Assert the dedicated GPIOHIBWAKE pin (GPIO41) low to enable the power-up of the device clock
sources.
2. Assert GPIOHIBWAKE pin high again. This triggers the power-up of the rest of the device.
3. Boot ROM code will execute on HIB wake-up. Boot ROM will read CPU1.RESC.HIBRESTn bit to
determine this is a wakeup from HIB.
4. Boot ROM calls the I/O context restore routine. This I/O restore function should reconfigure the I/O
configuration and do any other necessary application setup.
Since waking up from HIB mode is a type of reset, the device will enter the main function. The device is
now out of HIB mode and can normal execution.
NOTE: The bootROM uses locations 0x02-0x122 on CPU1’s M0 RAM. To prevent losing any data
during HIB wake-up, avoid saving any critical data to these locations.
NOTE: The application must bypass the PLL before executing the IDLE instruction to enter HIB. If
the PLL is not bypassed when entering HIB, there will be a brief current spike on the Vdd
supply that may cause the device to reset.
CPU1 TO
CPU1.CLA1 CPU1.CLA1
MSGRAM
CPU1.CLA1 TO
CPU1 MSGRAM
CPU1.DMA
CPU1
CPU1.M0 RAM
CPU1.M1 RAM
CPU1.Dx RAM
All these RAMs have the access protection (CPU write/CPU fetch) feature. Each type of access protection
for each RAM block can be enabled or disabled by configuring the specific bit in the local shared RAM
access protection registers. Table 3-9 shows the LSx RAM features.
Like other shared RAM, these RAMs also have a different levels of access protection which can be
enabled or disabled by configuring specific bits in the GSxACCPROT registers.
Master select and access protection configuration for each GSx RAM block can be individually locked by
the user to prevent further update to these bit fields. The user can also choose to permanently lock the
configuration to individual bit fields by setting the specific bit fields in the GSxCOMMIT register (refer to
the register description for more details). Once configuration is committed for a particular GSx RAM block,
it can not be changed further until CPU1.SYSRS is issued.
CPU1.DMA READ/WRITE
RR-CPU1.DMA
If a fetch protection violation occurs, it results in an ITRAP for CPU. A flag gets set into the appropriate
access violation flag register, and the memory address for which the access violation occurred, get
latched into the appropriate CPU fetch access violation address register.
If a write access is made to GSx memory by a non-master DMA, it is called a non-master write protection
violation. If a write access is made to a dedicated or shared memory by a master DMA, and
DMAWRPROTx is set to ‘1’ for that memory, it is called a master DMA write protection violation.
A flag gets set in the DMA access violation flag register, and the memory address where the violation
happened gets latched in the DMA fetch access violation address register. These are dedicated registers
for each subsystem.
Note 1: All access protections are ignored during debug accesses. Write access to a protected
memory will go through when it is done via the debugger, irrespective of the write protection
configuration for that memory.
Note 2: Access protection is not implemented for M0 and M1 memories.
Note 3: In the case of local shared RAM, if memory is shared between the CPU and its CLA, the
CPU will only have access if the memory is configured as data RAM for the CLA. If it is
programmed as program RAM, all the access from the CPU (including read) and data access
from the CLA will be blocked, and violation will be considered as a non-master access
violation. If the memory is configured as dedicated to the CPU, all access from the CLA will
be blocked and the violation will be considered a non-master access violation.
NOTE: ECC/Parity for address is calculated for address offset only (based on RAM block size) of
corresponding 32bit aligned address. E.g. in case of LSx RAM which are 4KB RAM block,
only 11 LSB of 32bit aligned address are used. So if address is 0x8F8F, address ECC (or
Parity) will be calculated for address 0x78E (11bit offset of 32bit aligned address). Similarly
for 8KB RAM block, 12bit address offset will be used.
NOTE: In the case of an uncorrectable error during fetch on the CPU, there is the possibility of
getting an ITRAP before an NMI exception, since garbage instructions enter into the CPU
pipeline before the NMI gets generated.
During debug accesses, correctable as well as uncorrectable errors are masked.
NOTE: The memory map for ECC/Parity bits and data bits are the same. The user must choose a
different test mode to access ECC/Parity bits.
Table 3-12 shows the bit mapping for the ECC/Parity bits when they are read in RAMTEST mode using
their respective addresses.
Table 3-12. Mapping of ECC Bits in Read Data from ECC/Parity Address Map
Data Bits Location in Read Data Content (ECC Memory)
6:0 ECC Code for lower 16 bits of data
7 Not Used
14:8 ECC Code for upper 16 bits of data
15 Not Used
22:16 ECC Code for address
31:23 Not Used
Table 3-13. Mapping of Parity Bits in Read Data from ECC/Parity Address Map
Data Bits Location in Read Data Content (Parity Memory)
0 Parity for lower 16 bits of data
7:1 Not Used
8 Parity for upper 16 bits of data
15:9 Not Used
16 Parity for address
31:17 Not Used
NOTE: None of the masters should access the memory while initialization is taking place. If memory
is accessed before RAMINITDONE is set, the memory read/write as well as initialization will
not happen correctly.
3.12.1 Features
Features of flash memory include:
• Two flash banks (Bank0 and Bank1) (refer to the device data manual for the size of the flash bank)
• Dedicated flash module controller (FMC) for each bank
• 128 bits (bank width) can be programmed at a time along with ECC
• Multiple sectors providing the option of leaving some sectors programmed and only erasing specific
sectors
• User-programmable OTP locations (in USER OTP0) for configuring security, OTP boot-mode and boot-
mode select pins (if the user is unable to use the factory-default boot-mode select pins)
• Flash pump shared by the two banks
• Hardware flash pump semaphore to control ownership of the pump between the two FMCs.
The semaphore mechanism is not applicable during reads or program execution. It is also transparent
when the CCS plugin/Uniflash is used tor Flash programming. However, the semaphore must be
managed when the API is used.
• Enhanced performance using the code-prefetch mechanism and data cache in FMC0 and FMC1
• Configurable wait states to give the best performance for a given execution speed
• Safety Features
– SECDED-single error correction and double error detection is supported in the FMC
– Address bits are included in ECC
– Test mode to check the health of ECC logic
• Supports low-power modes for flash bank and pump for power savings
• Built-in power mode control logic
• Integrated flash program/erase state machine (FSM) in the FMC
– Simple flash API algorithms
– Fast erase and program times (refer to the device data manual for details)
• Code Security Module (CSM) to prevent access to the flash by unauthorized persons (refer to
Section 3.13 for details)
• Extra wait-state is encountered when code is fetched (or data is read) from Bank1, even for prefetched
data
NOTE: Before initializing wait-states, turn off the pre-fetch and data caching in the FRD_INTF_CTRL
register.
Bank0
FMC0
Pump
CPU
FMC1
Pump Semaphore
CPU System Clock
Bank1
The CPU interfaces with FMC1 which in turn, interfaces with Bank1 and the shared pump to perform
erase or program operations as well as to read data and execute code from Bank1. Control signals to the
flash pump will be controlled by either FMC0 or FMC1, depending on who gains the flash pump
semaphore.
There is a state machine in both FMC0 and FMC1 which generates the erase/program sequences in
hardware. This simplifies the Flash API software which configures control registers in the FMC to perform
flash erase and program operations (see TMS320F2837xS Flash API Version 1.55 Reference Guide
SPNU630, for details on Flash API).
Section 3.12.6 through Section 3.12.10 describe FMC in detail.
The flash bank and pump consume a significant amount of power when active. The flash module provides
a mechanism to power-down flash banks and pump. Special timers automatically sequence the power-up
of Bank0 and Bank1 independently of each other. The shared charge pump module has its own
independent power-up timer as well.
The flash bank and OTP operate in three power modes: Sleep (lowest power), Standby, and Active
(highest power)
• Sleep State
This is the state after a device reset. In this state, a CPU data read or opcode fetch will automatically
initiate a change in power mode to the standby state and then to the active state. During this transition
time to the active state, the CPU will automatically be stalled.
• Standby State
This state uses more power than the sleep state, but takes a shorter time to transition to the active or
read state. In this state, a CPU data read or opcode fetch will automatically initiate a change in power
mode to the active state. During this transition time to the active state, the CPU will automatically be
stalled. Once the flash/OTP has reached the active state, the CPU access will complete as normal.
• Active or Read State
In this state, the bank and pump are in active power mode state (highest power)
The charge pump operates in two power modes:
• Sleep (lowest power)
• Active (highest power)
Any access to any flash bank/OTP causes the charge pump to go into active mode, if it is in sleep mode.
An erase or program command causes the charge pump and bank to become active. If any bank is in
active or in standby mode, the charge pump will be in active mode, independent of the pump power mode
control configuration (PMPPWR bit-field in FPAC1 register).
To power down the Flash pump, the CPU must power down the Flash Pump using below sequence
without any Flash accesses in between. The Flash Pump will not enter low-power mode if below sequence
is not followed.
1. Assign the Pump Semaphore for Bank 0.
2. Assign a value of 0x14 to FMC0 VREADST (refer to the FBAC register) to ensure the requisite delay
needed for the flash pump/bank to come out of low-power mode later: FBAC.VREADST = 0x14
3. Change the FMC0 Flash Bank Fall Back power mode to Sleep: FBFALLBACK.BNKPWR = 0.
4. Change the FMC0 Flash Charge Pump Fall Back power mode to Sleep: FPAC1.PMPPWR = 0.
5. Assign the Pump Semaphore for Bank 1.
6. Assign a value of 0x14 to FMC1 VREADST (refer to FBAC register) to ensure the requisite delay
needed for the flash pump/bank to come out of low-power mode later: FBAC.VREADST = 0x14.
7. Change the FMC1 Flash Bank Fall Back power mode to Sleep: FBFALLBACK.BNKPWR = 0.
8. Change the FMC1 Flash Charge Pump Fall Back power mode to Sleep: FPAC1.PMPPWR = 0.
The above listed procedure should be executed from RAM and not from Flash. Note that exclusive control
of the Flash pump should be assigned to a FMC (using PUMPREQUEST, Flash pump ownership control
register) before configuring the PMPPWR bit field of the FPAC1 register as shown in the above sequence.
As the charge pump is shared between FMC0 and FMC1, the effective PMPPWR value used when
powering down the pump will be of the FMC (out of FMC0 and FMC1) which owns the pump. The
application software can check the current power mode of flash bank by reading the FBPRDY register.
The PUMPRDY bit can be used by the application software to identify the current power mode status of
the pump. A value of 0 in the PUMPRDY bit in both FMC0 and FMC1 indicates that the charge pump is in
sleep mode. A value of 1 in PUMPRDY bit in either FMC0 or FMC1 or in both FMC0 and FMC1 indicates
that the charge pump is in active mode. Refer to the register descriptions, Section 3.15, for detailed
information.
While the pump is in sleep state, a charge pump sleep down counter holds a user configurable value
(PSLEEP bit field in the FPAC1 register) and when the charge pump exits sleep power mode, the down
counter delays from 0 to PSLEEP prescaled SYSCLK clock cycles (prescaled clock is SYSCLK/2) before
putting the charge pump into active power mode. Note that the configured PSLEEP value should yield at
least a delay of 20us for the pump to go to active mode. Refer to the register descriptions, Section 3.15,
for detailed information
Below are the number of cycles it will take for the Bank and pump to wake up from low power modes.
1. Pump sleep to active = PSLEEP * (SYSCLK/2) cycles
2. Bank sleep to standby = 425 Flash clock cycles
3. Bank standby to active = 90 Flash clock cycles
For a given system clock frequency, RWAIT has to be configured using below formula:
RWAIT = ceiling[(SYSCLK/FCLK)-1]
Flash prefetch
Instruction buffer
128-bit 128-bit
buffer buffer
Instruction fetch
128-bit
M Data cache
CPU 32-bit U
X
This prefetch mechanism does a look-ahead prefetch on linear address increments starting from the
address of the last instruction fetch. The flash prefetch mechanism is disabled by default. Setting the
PREFETCH_EN bit in the FRD_INTF_CTRL register enables this prefetch mode.
An instruction fetch from the flash or OTP reads out 128 bits per access. The starting address of the
access from flash is automatically aligned to a 128-bit boundary, such that the instruction location is within
the 128 bits to be fetched. With the flash prefetch mode enabled, the 128 bits read from the instruction
fetch are stored in a 128-bit wide by 2-level deep instruction prefetch buffer. The contents of this prefetch
buffer are then sent to the CPU for processing as required.
Up to four 32-bit or eight 16-bit instructions can reside within a single 128-bit access. The majority of C28x
instructions are 16 bits, so for every 128-bit instruction fetch from the flash bank, it is likely that there are
up to eight instructions in the prefetch buffer ready to process through the CPU. During the time it takes to
process these instructions, the flash prefetch mechanism automatically initiates another access to the
flash bank to prefetch the next 128 bits. In this manner, the flash prefetch mechanism works in the
background to keep the instruction prefetch buffers as full as possible. Using this technique, the overall
efficiency of sequential code execution from flash or OTP is improved significantly.
NOTE: If the prefetch mechanism is enabled, then the last two rows (16 16-bit words, 256 bits) of
the bank which does not have valid address beyond its boundary should not be used,
because the prefetch logic which does a look-ahead prefetch, will try to fetch from outside
the bank and would result in an ECC error.
The flash prefetch is aborted only on a PC discontinuity caused by executing an instruction such as a
branch, BANZ, call, or loop. When this occurs, the prefetch mechanism is aborted and the contents of the
prefetch buffer are flushed. There are two possible scenarios when this occurs:
1. If the destination address is within the flash or OTP, the prefetch aborts and then resumes at the
destination address.
2. If the destination address is outside of the flash and OTP, the prefetch is aborted and begins again
only when a branch is made back into the flash or OTP. The flash prefetch mechanism only applies to
SPRUHX5G – August 2014 – Revised September 2019 System Control 137
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Flash and OTP Memory www.ti.com
instruction fetches from program space. Data reads from data memory and from program memory do
not utilize the prefetch buffer capability and thus bypass the prefetch buffer. For example, instructions
such as MAC, DMAC, and PREAD read a data value from program memory. When this read happens,
the prefetch buffer is bypassed but the buffer is not flushed. If an instruction prefetch is already in
progress when a data read operation is initiated, then the data read will be stalled until the prefetch
completes.
Note that the prefetch mechanism gets bypassed when RWAIT is configured as zero.
NOTE: Flash contents are verified for ECC correctness before they enter prefetch buffer or data
cache and not inside the prefetch buffer or data cache itself.
3.12.9.1 Erase
When the target flash is erased, it reads as all 1's. This state is called 'blank.' The erase function must be
executed before programming. The user should NOT skip erase on sectors that read as 'blank' because
these sectors may require additional erasing due to marginally erased bits columns. The FSM provides an
“Erase Sector” command to erase the target sector. The erase function erases the data and the ECC
together. This command is implemented by the following Flash API function:
Fapi_issueAsyncCommandWithAddress();
The Flash API provides the following function to determine if the flash bank is 'blank':
Fapi_doBlankCheck();
3.12.9.2 Program
The FSM provides a command to program the USER OTP and Flash. This command is also used to
program ECC check bits.
This command is implemented by the following Flash API function:
Fapi_issueProgrammingCommand();
The Program function provides the options to program data without ECC, data along with user-provided
ECC data, data along with ECC calculated by API software , and to program ECC only.
3.12.9.3 Verify
After programming, the user must perform verify using API function Fapi_doVerify(). This function verifies
the flash contents against supplied data.
Application software typically perform a CRC check of the Flash memory contents during power-up and at
regular intervals during runtime (as needed). Apart from this, ECC logic, when enabled (enabled by
default), catches single-bit errors, double-bit errors, and address errors whenever the CPU reads/fetches
from a Flash address.
Data[127:64]
ECC[7:0]
During an instruction fetch or a data read operation, the 19 most significant address bits (three least
significant bits of address are not considered), together with the 64-bit data/8-bit ECC read-out of flash
banks/ECC memory map area, pass through the SECDED logic and the eight checkbits are produced in
FMC. These eight calculated ECC check bits are then XORed with the stored check bits (user
programmed check bits) associated with the address and the read data. The 8-bit output is decoded inside
the SECDED module to determine one of three conditions:
• No error occurred
• A correctable error (single bit data error) occurred
• A non-correctable error (double bit data error or address error) occurred
If the SECDED logic finds a single-bit error in the address field, then it is considered to be a non-
correctable error.
NOTE: TI recommends programming ECC while programming Flash to avoid any error. Since ECC
is calculated for an entire 64-bit data, a non 64-bit read such as a byte read or a half-word
read will still force the entire 64-bit data to be read and calculated, but only the byte or half-
word will be actually used by the CPU.
This ECC (SECDED) feature is enabled at reset. The ECC_ENABLE register can be used to configure(
enable/disable) the ECC feature. The ECC for the application code must be programmed.. There are two
SECDED modules in each FMC. Out of the 128-bit data (aligned on a 128-bit memory boundary) read
from the bank/OTP address, the lower 64-bits of data and corresponding 8 ECC bits (read from user
programmable ECC memory area) are fed as inputs to one SECDED module along with 128-bit aligned
19-bit address from where data has been read. The upper 64- bits of data and corresponding 8 ECC bits
are fed as inputs to another SECDED module in parallel, along with 128-bit aligned 19-bit address. Each
of the SECDED modules evaluate their inputs and determine if there is any single-bit data error or double-
bit data error/address error.
ECC logic will be bypassed when the 64 data bits and the associated ECC bits fetched from the bank are
either all ones or zeros.
When an uncorrectable error occurs, the UNC_ERR_INTFLG bit is set and an uncorrectable error interrupt
is fired. This uncorrectable error interrupt generates an NMI, if enabled. If an uncorrectable error interrupt
flag is not cleared using the corresponding error interrupt clear bit in the ERR_INTCLR register, an error
interrupt will not come again, as this is an edge based interrupt.
Although ECC is calculated on 64-bit basis, a read of any address location within a 128-bit aligned Flash
memory will cause the uncorrectable error flag to get set when there is a uncorrectable error in both or in
either one of the lower 64 and upper 64 bits (or corresponding ECC check bits) of that 128-bit data. NMI
will occur on the CPU for a read of any address location within a 128-bit aligned Flash memory, when
there is an uncorrectable error in both or in either one of the lower 64 and upper 64 bits (or corresponding
ECC check bits) of that 128-bit data.
Bank 0 is writable.
Bank 1 is writable
• RAM: All Dx and LSx RAMs can be secure RAM on this device. These RAMs can be allocated to
either zone by configuring the respective GRABRAM location in the USER OTP.
• Flash Sectors: Flash Sectors can be secure on this device. Each Flash sector can be allocated to
either zone by configuring the respective GRABSECT location in the USER OTP.
• Secure ROM: This device also has secure ROM which is EXEONLY-protected. This ROM contains
specific function for the user, provided by TI.
Table 3-15 shows the status of a RAM block based on the configuration in GRABRAM register.
The security of each zone is ensured by its own 128-bit (four 32-bit words) password (CSM password).
The password for each zone is stored in its dedicated OTP location based on a zone-specific link pointer.
A zone can be unsecured by executing the password match flow (PMF), described in Section 3.13.3.3.2.
There are three types of accesses: data/program reads, JTAG access, and instruction fetches (calls,
jumps, code executions, ISRs). Instruction fetches are never blocked. JTAG accesses are always blocked
when a memory is secure. Data reads to a secure memory are always blocked unless the program is
executing from a memory which belongs to the same zone. Data reads to unsecure memory are always
allowed. Table 3-16 shows the levels of security.
If the password locations of a zone have all 128 bits as ones, the zone is considered unsecure. Since new
Flash devices have erased Flash (all ones), only a read of the password locations is required to bring any
zone into unsecure mode. If the password locations of a zone have all 128 bits as zeros, the zone is
secure, regardless of the contents of the CSMKEY registers. This means the zone can’t be unlocked using
PMF, the password match flow described in Section 3.13.3.3.2. Therefore, the user should never use all
zeros as a password. A password of all zeros will prevent debug of secure code or reprogramming the
Flash.
CSMKEY registers are user-accessible registers that are used to unsecure the zones.
NOTE: Password unlock only makes password locations non-secure. All other secure memories and
other locations of Flash sectors, which contain a password, remains secure as per security
settings. But since passwords are non-secure, anyone can read the password and make the
zone non-secure by running through PMF.
• Zx-GRABSECT
• Zx-CSMPASSWORD
The location of the zone select region in OTP is decided based on the value of three 29-bit link pointers
(Zx-LINKPOINTERx) programmed in the OTP of each zone. All OTP locations except link pointer locations
are protected with ECC. Since the link pointer locations are not protected with ECC, three link pointers are
provided that need to be programmed with the same value. The final value of the link pointer is resolved in
hardware when a dummy read is done to all the link pointers by comparing all the three values (bit-wise
voting logic). Since in OTP, a ‘1’ can be flipped by the user to ‘0’ but ‘0’ can’t be flipped to ‘1’ (no erase
operation for OTP), the most significant bit position in the resolved link pointer which is ‘0’, defines the
valid base address for the zone select region. While generating the final link pointer value, if the bit
patterns is not one of those listed in Figure 3-20, the final link pointer value becomes All_1
(0xFFFF_FFFF) which selects the Zone-Select-Block1 (also known as the default zone select block).
NOTE: Address locations for other security settings (PSWDLOCK/CRCLOCK) that are not part of
Zone Select blocks) can be programmed only once; therefore, the user should program them
towards end of the development cycle.
NOTE: Since linkpointer location in USER OTP does not have ECC user should always define
separate structure and section for linkpointers.
3.13.1.5.1 C Code Example to get Zone Select Block Addr for Zone1
unsigned long LinkPointer;
unsigned long *Zone1SelBlockPtr;
int Bitpos = 28;
int ZeroFound = 0;
NOTE: If there is a loss of power or a reset of any nature during the flash programming operation,
there is high probability of some (or possibly all) of the 128 bits in the corresponding 128-bit
aligned address getting corrupted. If this happens while programming the password locations
in USER OTP, the passwords may get corrupted.
3.13.1.8 SafeCRC
Since reads from EXEONLY memories are not allowed, the user cannot calculate the CRC for content in
EXEONLY memories using the VCU-II. But in some safety-critical applications, the user may have to
calculate the CRC on these memories as well. To enable this without compromising on security, TI
provides specific “SafeCRC” library functions for each zone. These functions do the CRC calculation in
highly secure environment and allow a CRC calculation to be performed only when the following
conditions are met:
• The source address should be modulo the number of words (based on length_id) for which the CRC
needs to be calculated.
• The destination address should belong to the same zone as the source address.
For further usage of these library functions, see the device-specific Boot ROM documentation.
NOTE: The user must disable all the interrupts before calling the safe copy code and the safeCRC
function. If there is a vector fetch during copy code operation, the CPU gets reset
immediately.
Disclaimer: Code Security Module Disclaimer The Code Security Module (CSM) included on this device
was designed to password protect the data stored in the associated memory and is warranted by Texas
Instruments (TI), in accordance with its standard terms and conditions, to conform to TI's published
specifications for the warranty period applicable for this device. TI DOES NOT, HOWEVER, WARRANT
OR REPRESENT THAT THE CSM CANNOT BE COMPROMISED OR BREACHED OR THAT THE
DATA STORED IN THE ASSOCIATED MEMORY CANNOT BE ACCESSED THROUGH OTHER
MEANS. MOREOVER, EXCEPT AS SET FORTH ABOVE, TI MAKES NO WARRANTIES OR
REPRESENTATIONS CONCERNING THE CSM OR OPERATION OF THIS DEVICE, INCLUDING ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL TI BE LIABLE FOR ANY CONSEQUENTIAL, SPECIAL, INDIRECT, INCIDENTAL, OR
PUNITIVE DAMAGES, HOWEVER CAUSED, ARISING IN ANY WAY OUT OF YOUR USE OF THE CSM
OR THIS DEVICE, WHETHER OR NOT TI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. EXCLUDED DAMAGES INCLUDE, BUT ARE NOT LIMITED TO LOSS OF DATA, LOSS OF
GOODWILL, LOSS OF USE OR INTERRUPTION OF BUSINESS OR OTHER ECONOMIC LOSS.
NOTE: Security Initialization is done by BOOTROM code on all the resets which assert SYSRSn (as
part of device initialization). This will not be part of user application code
START
NO
NO Correct
Password?
YES
Zone Unsecure
3.13.3.3 Unsecuring Considerations for Zones With and Without Code Security
Case 1 and Case 2 provide unsecuring considerations for zones with and without code security.
• Case 1: Zone With Code Security
A zone with code security should have a predetermined password stored in the password locations of
that zone. The following are steps to unsecure any secure zone:
NOTE: Even if a zone is not protected with a password (all password locations all ones), the CSM
will lock at reset. Thus, a dummy read operation must still be performed on these zones prior
to reading, writing, or programming secure memory if the code performing the access is
executing from outside of the CSM protected memory region. The Boot ROM code does this
dummy read for convenience.
START
NO
NO Correct
Password?
YES
3.14 JTAG
Gel files perform certain initialization tasks. This helps the users in a debug environment. However, when
executed standalone (without the emulator connected) the application may not work as expected, since
there is no gel file to perform those initializations. For example, gel file disables watchdog. If user code
does not service the watchdog in the application (or fails to disable it), there will be a difference in how the
application behaves with the debugger and without.
Common tasks performed by the gel files (but not boot-ROM)
On Reset:
• Disable Flash ECC on some devices.
– Disabling ECC only when using Flash API functions, see the Flash API User Guide for details.
Otherwise, TI suggests to always program ECC and enable ECC-check.
• Disable Watchdog
• Enable CLA clock
• Select real-time mode or C28x mode
On Restart:
• Select real-time mode or C28x mode
• Clear IER and IFR
On Target Connect:
• Select real-time mode or C28x mode
Complex bit access types are encoded to fit into small table cells. Table 3-19 shows the codes that are
used for access types in this section.
TIF indicates whether a timer overflow has happened since TIF was
last cleared. TIF is not cleared automatically and does not need to
be cleared to enable the next timer interrupt.
Reset type: SYSRSn
0h (R/W) = The CPU-Timer has not decremented to zero.
Writes of 0 are ignored.
1h (R/W) = This flag gets set when the CPU-timer decrements to
zero.
Writing a 1 to this bit clears the flag.
14 TIE R/W 0h CPU-Timer Interrupt Enable.
Reset type: SYSRSn
0h (R/W) = The CPU-Timer interrupt is disabled.
1h (R/W) = The CPU-Timer interrupt is enabled. If the timer
decrements to zero, and TIE is set, the timer asserts its interrupt
request.
13-12 RESERVED R 0h Reserved
11 FREE R/W 0h If the FREE bit is set to 1, then, upon a software breakpoint, the
timer continues to run. If FREE is 0, then the SOFT bit controls the
emulation behavior.
Reset type: SYSRSn
0h (R/W) = Stop after the next decrement of the TIMH:TIM (hard
stop)
(SOFT bit controls the emulation behavior)
1h (R/W) = Free Run
(SOFT bit is don't care, counter is free running)
10 SOFT R/W 0h If the FREE bit is set to 1, then, upon a software breakpoint, the
timer continues to run (that is, free runs). In this case, SOFT is a
don't care. But if FREE is 0, then SOFT takes effect.
Reset type: SYSRSn
0h (R/W) = Stop after the next decrement of the TIMH:TIM (hard
stop).
(ONLY if FREE=0, if FREE=1 this bit is don't care)
1h (R/W) = Stop after the TIMH:TIM decrements to 0 (soft stop)
In the SOFT STOP mode, the timer generates an interrupt before
shutting down (since reaching 0 is the interrupt causing condition).
(ONLY if FREE=0, if FREE=1 this bit is don't care)
9-6 RESERVED R 0h Reserved
Complex bit access types are encoded to fit into small table cells. Table 3-26 shows the codes that are
used for access types in this section.
Note: When a NMI is serviced, the PIEVECT bit-field does not reflect
the vector as it does for other interrupts.
Reset type: SYSRSn
0 ENPIE R/W 0h Enable vector fetching from ePIE block. This bit must be set to 1 for
peripheral interrupts to work. All ePIE registers (PIEACK, PIEIFR,
PIEIER) can be accessed even when the ePIE block is disabled.
Reset type: SYSRSn
Complex bit access types are encoded to fit into small table cells. Table 3-54 shows the codes that are
used for access types in this section.
Notes:
[1] If MIN = 0, this bit is never set
[2] If MIN is changed back to 0x0 from a non-zero value, this bit is
auto-cleared
[3] This bit is added for debug purposes only
Reset type: IORSn
7-0 MIN R/W 0h These bits define the lower limt of the Windowed functionality
Reset type: IORSn
Complex bit access types are encoded to fit into small table cells. Table 3-61 shows the codes that are
used for access types in this section.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
10 RESERVED R-0/W1S 0h Reserved
9 RESERVED R-0/W1S 0h Reserved
8 CLBNMI R-0/W1S 0h Writing a 1 to the respective bit clears the corresponding flag bit in
the NMIFLG and NMISHDFLG registers. Writes of 0 are ignored.
Always reads back 0.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
7 RESERVED R-0/W1S 0h Reserved
6 RESERVED R-0/W1S 0h Reserved
5 RESERVED R-0/W1S 0h Reserved
4 CPU1HWBISTERR R-0/W1S 0h Writing a 1 to the respective bit clears the corresponding flag bit in
the NMIFLG and NMISHDFLG registers. Writes of 0 are ignored.
Always reads back 0.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
2 RAMUNCERR R-0/W1S 0h Writing a 1 to the respective bit clears the corresponding flag bit in
the NMIFLG and NMISHDFLG registers. Writes of 0 are ignored.
Always reads back 0.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
1 CLOCKFAIL R-0/W1S 0h Writing a 1 to the respective bit clears the corresponding flag bit in
the NMIFLG and NMISHDFLG registers. Writes of 0 are ignored.
Always reads back 0.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
0 NMIINT R-0/W1S 0h Writing a 1 to the respective bit clears the corresponding flag bit in
the NMIFLG and NMISHDFLG registers. Writes of 0 are ignored.
Always reads back 0.
Notes:
[1] If hardware is trying to set a bit to 1 while software is trying to
clear a bit to 0 on the same cycle, hardware has priority.
[2] Users should clear the pending FAIL flag first and then clear the
NMIINT flag.
Reset type: SYSRSn
If no enabled FAIL flag is set, then the counter will reset to zero and
remain at zero until an enabled FAIL flag is set.
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
10 RESERVED R 0h Reserved
9 RESERVED R 0h Reserved
8 CLBNMI R 0h Shadow NMI Flags: When an NMIFLG bit is set due to any of the
possible NMI source in the device, the corresponding bit in this
register is also set. Note that NMIFLGFRC and NMIFLGCLR register
also affects the bits of this register in the same way as they do for
the NMIFLG register. This register is only reset by a PORESETn
reset.
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
7 RESERVED R 0h Reserved
6 RESERVED R 0h Reserved
5 RESERVED R 0h Reserved
4 CPU1HWBISTERR R 0h Shadow NMI Flags: When an NMIFLG bit is set due to any of the
possible NMI source in the device, the corresponding bit in this
register is also set. Note that NMIFLGFRC and NMIFLGCLR register
also affects the bits of this register in the same way as they do for
the NMIFLG register. This register is only reset by a PORESETn
reset.
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
2 RAMUNCERR R 0h Shadow NMI Flags: When an NMIFLG bit is set due to any of the
possible NMI source in the device, the corresponding bit in this
register is also set. Note that NMIFLGFRC and NMIFLGCLR register
also affects the bits of this register in the same way as they do for
the NMIFLG register. This register is only reset by a PORESETn
reset.
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
1 CLOCKFAIL R 0h Shadow NMI Flags: When an NMIFLG bit is set due to any of the
possible NMI source in the device, the corresponding bit in this
register is also set. Note that NMIFLGFRC and NMIFLGCLR register
also affects the bits of this register in the same way as they do for
the NMIFLG register. This register is only reset by a PORESETn
reset.
Notes:
[1] This register is added to keep the definition of System Control
Reset Cause Register Clean.
Reset type: PORESETn
0 RESERVED R-0 0h Reserved
Complex bit access types are encoded to fit into small table cells. Table 3-70 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-80 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-88 shows the codes that are
used for access types in this section.
Note: This field shows flash size on CPU1 (see datasheet for flash
size available)
Reset type: XRSn
15 RESERVED R 0h Reserved
14-13 INSTASPIN R 0h 0 = Reserved for future
1 = Reserved for future
2 = Reserved for future
3 = NONE
Reset type: XRSn
12 RESERVED R 0h Reserved
11 RESERVED R 0h Reserved
10-8 PIN_COUNT R 0h 0 = reserved for future
1 = reserved for future
2 = reserved for future
3 = reserved for future
4 = reserved for future
5 = 100 pin
6 = 176 pin
7 = 337 pin
Reset type: XRSn
Complex bit access types are encoded to fit into small table cells. Table 3-128 shows the codes that are
used for access types in this section.
Notes:
[1] Clock to CPU2.WD clocks is always gated in the HALT mode.
Reset type: XRSn
4 XTALOFF R/W 0h Crystal (External) Oscillator Off Bit: This bit turns external oscillator
off:
0 = Crystal (External) Oscillator On (default on reset)
1 = Crystal (External) Oscillator Off
NOTE: Ensure no resources are using a clock source prior to
disabling it. For example OSCCLKSRCSEL (SYSPLL),
AUXOSCCLKSRCSEL (AUXPLL), CANxBCLKSEL (CAN Clock),
TMR2CLKSRCSEL (CPUTIMER2) and XCLKOUTSEL(XCLKOUT).
Reset type: XRSn
This bit could be used by the user to turn off the internal oscillator 2
if it is not used.
Notes:
[1] Reserved selection defaults to 00 configuration
[2] INTOSC1 is recommended to be used only after missing clock
detection. If user wants to re-lock the PLL with INTOSC1 (the back-
up clock source) after missing clock is detected, he can do a
MCLKCLR and lock the PLL.
Reset type: XRSn
Missing clock detect circuit doesnt have any impact on these bits.
Reset type: XRSn
3-2 CANABCLKSEL R/W 0h CANA Bit-Clock Source Select Bit:
00 = PERx.SYSCLK (default on reset)
01 = External Oscillator (XTAL)
10 = AUXCLKIN (from GPIO)
11 = Reserved
Missing clock detect circuit doesnt have any impact on these bits.
Reset type: XRSn
Whenever the user changes the clock source using these bits,
the AUXPLLMULT register will be forced to zero and the PLL will
be bypassed and powered down. This prevents potential PLL
overshoot. The user will then have to write to the AUXPLLMULT
register to configure the appropriate multiplier.
The missing clock detection circuit does not affect these bits.
Reset type: XRSn
1 = SYSPLL is enabled
0 = SYSPLL is powered off. Clock to system is direct feed from
OSCCLK
Reset type: XRSn
The SLIPS bit will only be set on a PLL slip condition after the PLL is
used as the SYSCLK source by seting the
SYSPLLCTL1[PLLCLKEN] bit. Disabling and re-enabling the PLL
with PLLEN is the only way to clear this bit.
Note:
[1] If SYSPLL out of lock condition is detected then interrupts are
fired to CPU1 and CPU2 through their respective ePIE modules.
Software can decide to relock the PLL or switch to PLL bypass mode
in the interrupt handler
Reset type: XRSn
0 LOCKS R 0h SYSPLL Lock Status Bit: This bit indicates whether the SYSPLL is
locked or not
1 = AUXPLL is enabled
0 = AUXPLL is powered off. Clock to system is direct feed from
AUXOSCCLK
Reset type: XRSn
The SLIPS bit will only be set on a PLL slip condition after the PLL is
used as the AUXPLLCLK source by seting the
AUXPLLCTL1[PLLCLKEN] bit. Disabling and re-enabling the PLL
with PLLEN is the only way to clear this bit.
Note:
[1] If AUXPLL out of lock condition is detected then interrupts are
fired to CPU1 and CPU2 through their respective ePIE modules.
Software can decide to relock the PLL or switch to PLL bypass mode
in the interrupt handler
Reset type: XRSn
0 LOCKS R 0h AUXPLL Lock Status Bit: This bit indicates whether the AUXPLL is
locked or not
000000 = /1
000001 = /2
000010 = /4 (default on reset)
000011 = /6
000100 = /8
......
111111 = /126
Reset type: XRSn
00 = /1
01 = /2 (default on reset)
10 = /4
11 = /8
Reset type: XRSn
0: /1 of CPU1.SYSCLK is selected
1: /2 of CPU1.SYSCLK is selected
Reset type: CPU1.SYSRSn
5 RESERVED R-0 0h Reserved
4 EMIF1CLKDIV R/W 1h EMIF1 Clock Divide Select: This bit selects whether the EMIF1
module run with a /1 or /2 clock.
x0 = /1 of PLLSYSCLK
x1 = /2 of PLLSYSLCK (default on reset)
00 = /1
01 = /2
10 = /4
11 = /8 (default on reset)
Reset type: CPU1.SYSRSn
Note:
[1] This clock is used as strobe for the SCI and SPI modules.
Reset type: CPU1.SYSRSn
Complex bit access types are encoded to fit into small table cells. Table 3-147 shows the codes that are
used for access types in this section.
Notes:
1. This bit from CPU1.PCLKCR0 or CPU2.PCLKCR0 is selected and
fed to the individual EPWM modules based on their respective
CPUSEL bit.
Reset type: SYSRSn
17 RESERVED R-0 0h Reserved
16 HRPWM R/W 0h HRPWM Clock Enable Bit: When set, this enables the clock to the
HRPWM module
1: HRPWM clock is enabled
0: HRPWM clock is disabled
Note:
[1] This bit is present only in CPU1.PCLKCR0. This bit is not used
(R/W) in CPU2.PCLKCR0
Reset type: SYSRSn
15-6 RESERVED R-0 0h Reserved
5 CPUTIMER2 R/W 1h CPUTIMER2 Clock Enable bit:
Notes:
[1] These bits are not used (R/W) in CPU2.PCLKCR1 register.
EMIF1 & EMIF2 clock enabled are controlled only from
CPU1.PCLKCR1 register.
Reset type: SYSRSn
0 EMIF1 R/W 0h EMIF1 Clock Enable bit:
Notes:
[1] These bits are not used (R/W) in CPU2.PCLKCR1 register.
EMIF1 & EMIF2 clock enabled are controlled only from
CPU1.PCLKCR1 register.
Reset type: SYSRSn
Notes:
[1] This bit is not used (R/W) in CPU2.PCLKCR11 register. USB_A
clock enabled is controlled only from CPU1.PCLKCR11 register
Reset type: SYSRSn
15-2 RESERVED R-0 0h Reserved
1 McBSP_B R/W 0h McBSP_B Clock Enable bit:
Notes:
[1]] This bit also affects the uPP message RAM wrapper associated
with the respective uPP module
[2] This bit is not used (R/W) in CPU2.PCLKCR12 register. UPP_A
clock enabled is controlled only from CPU1.PCLKCR12 register
Reset type: SYSRSn
Notes:
[1] This bit is reserved in the register mapped to CPU2
Reset type: raw-XRSn
30-18 RESERVED R-0 0h Reserved
17-16 M0M1MODE R/W 0h These bit control the state of CPU1's and CPU2's M0 & M1
memories when Device goes into HIB mode.
[2] These bits take effect only when device goes into HIB mode. If
the device is not in HIB mode, the value in this bit doesn't control the
state of CPU1's and CPU2's M0 & M1 memories
Reset type: POR
15 WDINTE R/W 0h When this bit is set to 1, it enables the watchdog interrupt signal to
wake the device from STANDBY mode.
Note:
[1] To use this signal, the user must also enable the WDINTn signal
using the WDENINT bit in the SCSR register. This signal will not
wake the device from HALT mode because the clock to watchdog
module is turned off
Reset type: SYSRSn
14-8 RESERVED R-0 0h Reserved
000000 = 2 OSCCLKs
000001 = 3 OSCCLKs
......
111111 = 65 OSCCLKs
Note:
[1] The CPU Timer2s Clock sync logic detects an input clock edge
when configured for any clock source other than SYSCLK and
generates an appropriate clock pulse to the CPU timer2. If SYSCLK
is approximately the same or less then the input clock source, then
the user would need to configure the pre-scale value such that
SYSCLK is at least twice as fast as the pre-scaled value.
[2] Pre-scaler is bypassed if SYSCLK is selected as the source of
CPU Timer 2 in TMR2CLKSRCSEL of TMR2CLKCTL.
Reset type: SYSRSn
To know the exact cause of NMI after the reset, software needs to
read CPU1/2.NMISHDFLG registers
Reset type: POR
2 WDRSn R/W1S 0h If this bit is set, indicates that the device was reset by WDRSn.
Complex bit access types are encoded to fit into small table cells. Table 3-174 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-177 shows the codes that are
used for access types in this section.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
29-28 RESERVED R 0h Reserved
27-26 STATUS_SECTN R 0h Reflects the status of flash sector N.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
25-24 STATUS_SECTM R 0h Reflects the status of flash sector M.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
21-20 STATUS_SECTK R 0h Reflects the status of flash sector K.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
19-18 STATUS_SECTJ R 0h Reflects the status of flash sector J.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
17-16 STATUS_SECTI R 0h Reflects the status of flash sector I.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
15-14 STATUS_SECTH R 0h Reflects the status of flash sector H.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
13-12 STATUS_SECTG R 0h Reflects the status of flash sector G.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
11-10 STATUS_SECTF R 0h Reflects the status of flash sector F.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
7-6 STATUS_SECTD R 0h Reflects the status of flash sector D.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
5-4 STATUS_SECTC R 0h Reflects the status of flash sector C.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
3-2 STATUS_SECTB R 0h Reflects the status of flash sector B.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
1-0 STATUS_SECTA R 0h Reflects the status of flash sector A.
00 : Sector is in-accessible
01 : Sector belongs to Zone1.
10 : Sector belongs to Zone2.
11: Sector is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
00 : CLA is in-accessible
01 : CLA belongs to Zone1.
10 : CLA belongs to Zone2.
11: CLA is un-secure and code running in both zone have full access
to it.
Reset type: SYSRSn
27-16 RESERVED R 0h Reserved
15-14 STATUS_RAM7 R 0h Reflects the status of D1 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
13-12 STATUS_RAM6 R 0h Reflects the status of D0 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
9-8 STATUS_RAM4 R 0h Reflects the status of LS4 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
7-6 STATUS_RAM3 R 0h Reflects the status of LS3 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
5-4 STATUS_RAM2 R 0h Reflects the status of LS2 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
3-2 STATUS_RAM1 R 0h Reflects the status of LS1 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
1-0 STATUS_RAM0 R 0h Reflects the status of LS0 RAM.
00 : RAM is in-accessible
01 : RAM belongs to Zone1.
10 : RAM belongs to Zone2.
11: RAM is un-secure and code running in both zone have full
access to it.
Reset type: SYSRSn
Complex bit access types are encoded to fit into small table cells. Table 3-182 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-190 shows the codes that are
used for access types in this section.
1111 : CSM password locations in OTP are not protected and can
be read from debugger as well as code running from anywhere.
Other Value : CSM password locations in OTP are protected and
can't be read without unlocking CSM of that zone.
Reset type: SYSRSn
3-0 RESERVED R Fh Reserved
Complex bit access types are encoded to fit into small table cells. Table 3-205 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-213 shows the codes that are
used for access types in this section.
1111 : CSM password locations in OTP are not protected and can
be read from debugger as well as code running from anywhere.
Other Value : CSM password locations in OTP are protected and
can't be read without unlocking CSM of that zone.
Reset type: SYSRSn
3-0 RESERVED R Fh Reserved
Complex bit access types are encoded to fit into small table cells. Table 3-228 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-257 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-277 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-295 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-298 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-307 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 3-329 shows the codes that are
used for access types in this section.
562 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Introduction
4.1 Introduction
This chapter explains the boot ROM code functionality including the boot procedure when executed, the
functions and features of the boot ROM code, and details the ROM memory map contents. On every
reset, the device executes a boot sequence in the ROM depending on the reset type and boot
configuration. This sequence will initialize the device to run application code. The boot ROM also contains
peripheral bootloaders which can be used to load an application into RAM. ROM Memory is shown in
Table 4-1.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 563
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Device Boot Modes www.ti.com
Table 4-4 shows the boot mode options available through selection by the default boot mode select pins.
The boot mode select pins’ GPIOs and realized boot mode for when Get boot mode is selected can be
customized through the BOOTCTRL register detailed in Section 4.5.
564 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Configuring Boot Mode Pins
NOTE: All the peripheral boot modes that are supported use the first instance of the peripheral
module (SCIA, SPIA, I2CA, CANA, and so forth). Whenever these boot modes are referred
to in this chapter, such as SCI boot, it is actually referring to the first module instance,
meaning the SCI boot on the SCIA port. The same applies to the other peripheral boots.
On this device, the DCSM has two zones. Each zone, Z1 and Z2, has its own copy of the BOOTCTRL
register. The boot ROM is designed to be able to read from either location and uses the procedure in
Figure 4-1 to identify which register to use. By default, if the Z1 BOOTCTRL is programmed, then that
register is given the priority. If the Z1 BOOTCTRL isn’t programmed, then the boot ROM will check if Z2
BOOTCTRL is programmed, if not, then the factory default options are used.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 565
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Configuring Get Boot Options www.ti.com
YES YES
566 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Configuring Emulation Boot Options
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 567
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Device Boot Flow Diagrams www.ti.com
Reset
XRSn or
POR or
No No Hibernate No Other Resets
WD or NMIWD
resets
M0M1
No Retention Yes
Initialize all ON
RAMs
Initialize all Initialize all RAMs
RAMs except for M0/M1
DCSM INIT
DCSM INIT
Valid
Boot as per
Hibernate Boot
Yes Hibernate Boot
Key == 0x5A
TRSTn == 1 Mode
Yes No
No
568 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Device Boot Flow Diagrams
WAIT BOOT MODE Bits 7:0 EMU_KEY ± Use 0x5A to indicate validity of this location
Emulation Boot Mode
> Init PIE values.
While(1)
> Install C2C1IPC Handler
No > Disable WatchDOG Bits 15:8 EMU_BMODE - Use this field to define upto 256 boot modes
Valid Valid
EMUBOOTCTRL. EMUBOOTPIN0 = EMUBOOTPIN1 =
Read EmuBoot pins NO EMUBOOTCTRL. No
EMUBOOTPIN0 GPIO84 GPIO72
EMUBOOTPIN1
No Yes
Yes
EMUBOOTCTRL.EMU
_BMODE == 0xFE
Yes EMUBOOTPIN0 = EMUBOOTPIN1 = BootMode =
EMUBOOTCTRL.EM EMUBOOTCTRL.EM (*EMUBOOTPIN1 << 1) |
UBOOTPIN0 UBOOTPIN1 (*EMUBOOTPIN0)
No
------------------------------------------------------------------------------------------------
EMU_BMODE Value | Realized Boot Mode
------------------------------------------------------------------------------------------------
0x00 Parallel Boot Boot Mode = 0 -> Parallel Boot Mode
0x01 SCIBOOT(0) Boot Mode = 1 -> SCIBOOT Mode
0x02 WAIT BOOT Boot Mode = 2 -> WAIT BOOT Mode
0x03 GET MODE (OTP) Is Get Mode Boot Mode = 3 -> GET MODE (read OTP Boot
0x04 SPIBOOT(0) Mode values)
0x05 I2CBOOT(0)
No Yes
0x07 CANBOOT(0)
0x0A RAMBOOT
0x0B FLASHBOOT
0x0C USB BOOT
0x81 SCIBOOT(1) ± Alternate IO
0x84 SPIBOOT(1)- Alternate IO
0x85 I2CBOOT(1) ± Alternate IO
0x87 CANBOOT(1) ± Alternate IO
Start Boot LOAD Get Mode
0x47 CANBOOT(TEST)(0) ± TESTMODE
0xC7 CANBOOT(TEST)(1) ± TEESTMODE, Alternate
IO
Other WAIT BOOT
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 569
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Device Reset and Exception Handling www.ti.com
Bits 7:0 OTP_KEY ± Use 0x5A to ind ica te validity of this locatio n
values.
Yes
Bits 15:8 OTP_BMODE - Use this field to d efin e u pto 256 boo t modes
BOO TP IN0 =
Bits 23:16 OTP_BOO TP IN 0
ZxB OOTCTRL.OTPBO O Yes
Zx- 0-> Pick the default boo t pin-0 (GPIO 84)
TPIN0
BOO TCTRL.OTP_BO 1 -> Pick GP IO0 as b oot pin-0
OTPIN0 is valid? 2 -> Pick GP IO1 as b oot pin-0
«.
255 -> Pick GP IO255 as b oot pin-0
No
Boo t Mode = 0 -> Par allel Boot Mod e
Boo tMode = Boo t Mode = 1 -> SCIBOOT Mo de
BOO TP IN0 = (*BOO TP IN1 << Boo t Mode = 2 -> WAIT BOO T Mode
GPIO72 1)|(*BOO TP IN0) Boo t Mode = 3 -> GET MODE (read OTP Boot
Mode values)
GET MODE (boo t Mode) ----- --------- ---------- --------- --------- --------- ---------- --------- --------- --------- --------
Boo tMode Va lue | Realized Boo t Mo de
----- --------- ---------- --------- --------- --------- ---------- --------- --------- --------- --------
0x00 Par allel Boot
0x01 SCIBOOT(0)
Zx- Boo tMode = Zx- 0x02 WAIT BOO T
BOO TCTRL.OTP Yes OTPBO OTCTRL.OT 0x04 SPIBO OT(0)
_KEY == 0x5A P_BMODE 0x05 I2CBOOT(0)
0x07 CANBOOT(0)
0x0A RAMBOOT
0x0B FLASHBO OT
No 0x0C USB BOO T
0x81 SCIBOOT(1) ± Alterna te IO
Is Get Mod e 0x84 SPIBO OT(1)- Alterna te IO
Ena ble Wa tchdog 0x85 I2CBOOT(1) ± Alterna te IO
Boo t to Flash 0x87 CANBOOT(1) ± Alterna te IO
0x47 CANBOOT(TEST)(0) ± TESTMODE
0xC7 CANBOOT(TEST)(1) ± TEESTMODE, Alterna te IO
No Other FLASHBO OT (if stand Alone) EMUBOOT (if CCS con nected)
570 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Device Reset and Exception Handling
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 571
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
572 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 573
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
574 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
• An error occurs during emulation boot and the boot mode pins are decoded with a value not
recognized as a valid boot mode
SCIRXDA
Control Host
Subsystem (Data and program
boot ROM SCITXDA source)
The device communicates with the external host by communication through the SCI-A peripheral. The
autobaud feature of the SCI port is used to lock baud rates with the host. For this reason the SCI loader is
very flexible and you can use a number of different baud rates to communicate with the device.
After each data transfer, the bootloader will echo back the 8-bit character received to the host. This allows
the host to check that each character was received by the bootloader.
At higher baud rates, the slew rate of the incoming data bits can be affected by transceiver and connector
performance. While normal serial communications may work well, this slew rate may limit reliable auto-
baud detection at higher baud rates (typically beyond 100kbaud) and cause the auto-baud lock feature to
fail. To avoid this, the following is recommended:
1. Achieve a baud-lock between the host and SCI bootloader using a lower baud rate.
2. Load the incoming application or custom loader at this lower baud rate.
3. The host may then handshake with the loaded application to set the SCI baud rate register to the
desired high baud rate.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 575
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
SCI_Boot
Valid No
Setup SCI-A for KeyValue Jump to Flash
1 stop, 8-bit character, (0x08AA)
no parity, use internal ?
SC clock, no loopback,
disable Rx/Tx interrupts
Yes
No Autobaud
lock
?
Return
Yes EntryPoint
Serial SPI
EEPROM
SPIA_SIMO
DIN
Control SPIA_SOMI
DOUT
subsystem SPIA_CLK CLK
SPIA_STE CS
The SPI boot ROM loader initializes the SPI module to interface to a serial SPI EEPROM or flash. Devices
of this type include, but are not limited to, the Xicor X25320 (4Kx8) and Xicor X25256 (32Kx8) SPI serial
SPI EEPROMs and the Atmel AT25F1024A serial flash.
576 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
The SPI boot ROM loader initializes the SPI with the following settings: FIFO enabled, 8-bit character,
internal SPICLK master mode and talk mode, clock phase = 1, polarity = 0, using the slowest baud rate.
If the download is to be performed from an SPI port on another device, then that device must be setup to
operate in the slave mode and mimic a serial SPI EEPROM. Immediately after entering the SPI_Boot
function, the pin functions for the SPI pins are set to primary and the SPI is initialized. The initialization is
done at the slowest speed possible. Once the SPI is initialized and the key value read, you could specify a
change in baud rate or low speed peripheral clock.
The data transfer is done in "burst" mode from the serial SPI EEPROM. The transfer is carried out entirely
in byte mode (SPI at 8 bits/character). A step-by-step description of the sequence follows:
Step 1. The SPI-A port is initialized
Step 2. The GPIO19 (SPISTE) pin is used as a chip-select for the serial SPI EEPROM or flash
Step 3. The SPI-A outputs a read command for the serial SPI EEPROM or flash
Step 4. The SPI-A sends the serial SPI EEPROM an address 0x0000; that is, the host requires that
the EEPROM or flash must have the downloadable packet starting at address 0x0000 in the
EEPROM or flash. The loader is compatible with both 16-bit addresses and 24-bit addresses.
Step 5. The next word fetched must match the key value for an 8-bit data stream (0x08AA). The least
significant byte of this word is the byte read first and the most significant byte is the next byte
fetched. This is true of all word transfers on the SPI. If the key value does not match, then the
load is aborted and the bootloader jumps to flash.
Step 6. The next 2 bytes fetched can be used to change the value of the low speed peripheral clock
register (LOSPCP) and the SPI baud rate register (SPIBRR). The first byte read is the
LOSPCP value and the second byte read is the SPIBRR value. The next 7 words are
reserved for future enhancements. The SPI bootloader reads these 7 words and discards
them.
Step 7. The next two words makeup the 32-bit entry point address where execution will continue after
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 577
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
the boot load process is complete. This is typically the entry point for the program being
downloaded through the SPI port.
Step 8. Multiple blocks of code and data are then copied into memory from the external serial SPI
EEPROM through the SPI port. The blocks of code are organized in the standard data stream
structure presented earlier. This is done until a block size of 0x0000 is encountered. At that
point in time the entry point address is returned to the calling routine that then exits the
bootloader and resumes execution at the address specified.
SPI_Boot
Enable EEPROM
Send read command and Read and discard 7
start at EEPROM address reserved words
0x0000
I2CA_SDA
Control
subsystem
I2CA_SCL
I2C
SDA EEPROM
578 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
If the download is to be performed from a device other than an EEPROM, then that device must be set up
to operate in the slave mode and mimic the I2C EEPROM. Immediately after entering the I2C boot
function, the GPIO pins are configured for I2C-A operation and the I2C is initialized. The following
requirements must be met when booting from the I2C module:
• The input frequency to the device must be in the appropriate range.
• The EEPROM must be at slave address 0x50.
NACK Yes
I2C_Boot
received Jump to Flash
?
Enable I2CA_SDA and
I2CA_SCL pins No
Enable pullups on
I2CA_SDA and I2CA_SCL Read KeyValue
Read EntryPoint
address
Return
EntryPoint
The bit-period prescalers (I2CCLKH and I2CCLKL) are configured by the bootloader to run the I2C at a 50
percent duty cycle at 100-kHz bit rate (standard I2C mode) when the system clock is 10 MHz. These
registers can be modified after receiving the first few bytes from the EEPROM. This allows the
communication to be increased up to a 400-kHz bit rate (fast I2C mode) during the remaining data reads.
Arbitration, bus busy, and slave signals are not checked. Therefore, no other master is allowed to control
the bus during this initialization phase. If the application requires another master during I2C boot mode,
that master must be configured to hold off sending any I2C messages until the application software
signals that it is past the bootloader portion of initialization.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 579
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
The non-acknowledgment bit is checked only during the first message sent to initialize the EEPROM base
address. This is to make sure that an EEPROM is present at address 0x50 before continuing. If an
EEPROM is not present, the non-acknowledgment bit is not checked during the address phase of the data
read messages (I2C_Get Word). If a non acknowledgment is received during the data read messages, the
I2C bus will hang. Table 14-1 shows the 8-bit data stream used by the I2C.
The I2C EEPROM protocol required by the I2C bootloader is shown in Figure 4-11 and Figure 4-12. The
first communication, which sets the EEPROM address pointer to 0x0000 and reads the KeyValue
(0x08AA) from it, is shown in Figure 4-11. All subsequent reads are shown in Figure 4-12 and are read
two bytes at a time.
NO ACK
START
WRITE
READ
STOP
MSB
MSB
ACK
ACK
ACK
ACK
ACK
LSB
LSB
SDA LINE
1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 1 01 0 0 0 0 1 0
580 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
NO ACK
START
READ
STOP
ACK
ACK
SDA LINE
1 01 0 0 0 0 1 0
The control subsystem communicates with the external host device by polling/driving the GPIO70 and
GPIO69 lines. The handshake protocol shown in Figure 4-14 must be used to successfully transfer each
word via GPIO [63-58,64,65]. This protocol is very robust and allows for a slower or faster host to
communicate with the master subsystem.
Two consecutive 8-bit words are read to form a single 16-bit word. The most significant byte (MSB) is read
first followed by the least significant byte (LSB). In this case, data is read from GPIO[63-58,64,65].
The 8-bit data stream is shown in Table 4-17.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 581
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
The device first signals the host that it is ready to begin data transfer by pulling the GPIO69 pin low. The
host load then initiates the data transfer by pulling the GPIO70 pin low. The complete protocol is shown in
Figure 4-14:
Host control
GPIO70
Device control
GPIO69
1. The device indicates it is ready to start receiving data by pulling the GPIO69 pin low.
2. The bootloader waits until the host puts data on GPIO [63-58,64,65]. The host signals to the device
that data is ready by pulling the GPIO70 pin low.
3. The device reads the data and signals the host that the read is complete by pulling GPIO69 high.
4. The bootloader waits until the host acknowledges the device by pulling GPIO70 high.
5. The device again indicates it is ready for more data by pulling the GPIO69 pin low.
This process is repeated for each data value to be sent.
Figure 4-15 shows an overview of the Parallel GPIO bootloader flow.
Parallel_Boot
Call
CopyData
Valid
No KeyValue
Return Flash EntryPoint (0x08AA)
?
Return
Yes EntryPoint
582 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
Figure 4-16 shows the transfer flow from the host side. The operating speed of the CPU and host are not
critical in this mode as the host will wait for the device and the device will in turn wait for the host. In this
manner the protocol will work with both a host running faster and a host running slower than the device.
Start transfer
No Device ready
(GPIO69=0)
?
Yes
Signal that data
is ready Acknowledge device
(GPIO70=0) (GPIO70=1)
More Yes
data
?
No
End transfer
Figure 4-17 shows the flow used to read a single word of data from the parallel port.
• 8-bit data stream
The 8-bit routine, shown in Figure 4-17, discards the upper 8 bits of the first read from the port and
treats the lower 8 bits masked with GPIO65 in bit position 7 and GPIO64 in bit position 6 as the least
significant byte (LSB) of the word to be fetched. The routine will then perform a second read to fetch
the most significant byte (MSB). The routine will then perform a second read to fetch the most
significant byte (MSB). It then combines the MSB and LSB into a single 16-bit value to be passed back
to the calling routine.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 583
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
Parallel_GetWordData A
8 bit
Data Data
ready No ready No
(GPIO70 = 0) (GPIO70 = 0)
? ?
Yes Yes
Host
ack No
(GPIO70 = 1)
? Host
ack No
Yes (GPIO70 = 1)
?
Yes
WordData = MSB:LSB
A
Return WordData
584 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
28x
CAN bus
CAN
host
28x
The bit timing registers are programmed in such a way that a 100 kbps bit rate is achieved with a 20 MHz
external oscillator, a shown in Table 4-18.
The SYSCLKOUT values shown are the reset values with the default PLL setting. The BRP and bit-time
values are hard-coded to 10 and 20, respectively.
Mailbox 1 is programmed with a standard MSGID of 0x1 for boot-loader communication. The CAN host
should transmit only 2 bytes at a time, LSB first and MSB next. For example, to transmit the word 0x08AA
to the device, transmit AA first, followed by 08. The program flow of the CAN bootloader is identical to the
SCI bootloader. The data sequence for the CAN bootloader is shown in Table 4-19:
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 585
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
Enumerate to host
PC with ID 1cbe:00ff Valid key
Jump to flash
(0x08AA)?
Host PC installs
drivers
MCU loads data into
RAM
MCU waits
for data MCU disconnects
from the USB bus
Return EntryPoint
586 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
Implementing PC-side USB software is not trivial. It is recommended to use the TI-provided tools and
drivers to load data in USB boot mode. Hex and binary files for loader tools can be generated from COFF
(.out) files using the hex2000 tool. To produce a plain binary file in the boot loader format, use the
following command line:
hex2000 -boot -b Program_to_Load.out -o Binary_Loader_Data.dat
For more information on hex2000, please see the TMS320C28x Assembly Language Tools User's Guide
(SPRU513).
NOTE: INTOSC2 must be enabled before invoking the USB boot loader. If INTOSC2 is not enabled,
the boot loader will hang. A debugger reset or SCC reset will not enable INTOSC2 if it has
been disabled by the application.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 587
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
The first 16-bit word in the data stream is known as the key value. The key value is used to tell the
bootloader the width of the incoming stream: 8 or 16 bits. Note that not all bootloaders will accept both 8
and 16-bit streams. Please refer to the detailed information on each loader for the valid data stream width.
For an 8-bit data stream, the key value is 0x08AA and for a 16-bit stream it is 0x10AA. If a bootloader
receives an invalid key value, then the load is aborted.
The next eight words are used to initialize register values or otherwise enhance the bootloader by passing
values to it. If a bootloader does not use these values then they are reserved for future use and the
bootloader simply reads the value and then discards it. Currently only the SPI and I2C and parallel
bootloaders use these words to initialize registers.
The tenth and eleventh words comprise the 22-bit entry point address. This address is used to initialize
the PC after the boot load is complete. This address is most likely the entry point of the program
downloaded by the bootloader.
The twelfth word in the data stream is the size of the first data block to be transferred. The size of the
block is defined as 8-bit data stream format. For example, to transfer a block of 20 8-bit data values from
an 8-bit data stream, the block size would be 0x000A to indicate 10 16-bit words.
The next two words tell the loader the destination address of the block of data. Following the size and
address will be the 16-bit words that makeup that block of data.
This pattern of block size/destination address repeats for each block of data to be transferred. Once all the
blocks have been transferred, a block size of 0x0000 signals to the loader that the transfer is complete. At
this point the loader will return the entry point address to the calling routine which in turn will cleanup and
exit. Execution will then continue at the entry point address as determined by the input data stream
contents.
588 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
After load has completed the following memory values will have been initialized as follows:
Location Value
0x3F9010 0x0001
0x3F9011 0x0002
0x3F9012 0x0003
0x3F9013 0x0004
0x3F9014 0x0005
0x3F8000 0x7700
0x3F8001 0x7625
PC Begins execution at 0x3F8000
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 589
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
590 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
NOTE: The application should disable interrupts before calling one of the EXEONLY function APIs.
If a vector fetch request is given by the CPU while its program counter (PC) is within the
EXEONLY function API code of the Secure ROM, a reset will fire. The consequence of this is
if an NMI or ITRAP occurs while the PC is executing one of the EXEONLY API functions, the
NMI/ITRAP cannot be serviced because a reset will be fired to that subsystem.
The safe copy code zone 1 and zone 2 functions allow EXEONLY Flash to be copied to EXEONLY
RAM in a secure manner. The source must be from EXEONLY Flash and the destination to EXEONLY
RAM. There is no support to copy EXEONLY ROM or EXEONLY RAM to RAM. Both Flash and RAM
must be set to EXEONLY and configured for the same zone. Additionally, the copy size must not cross
over the flash sector boundary. Any violations of these requirements will result in a failure status returned.
Upon successful copy of the data, the number of 16-bit words copied is returned.
Uint16 SafeCopyCodeZ1(Uint32 size : The number of 16-bit words to 0xXXXX : Returns the number of
size, Uint16 *dst, Uint16 *src) copy 16-bit words copied
The safe CRC calculation zone 1 and zone 2 functions allow a safety CRC check of EXEONLY
memory in a secure manner. The CRC length provided must be a value from 1 to 8 where 1 represents a
CRC size of 32 16-bit words and 8 represents a CRC size of 4096 16-bit words. The source address
specifies the starting address for the CRC and the destination address is the location that the resulting
CRC value will be stored. The source and destination memories must be configured for the same zone.
Additionally, the CRC length must not cross over the flash sector or RAM block boundary. Any violations
of these requirements will result in a failure status returned. Upon successful CRC, the number of 16-bit
words CRC'd is returned.
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 591
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Boot ROM Description www.ti.com
NOTE: If the PLL is used during the boot process, it will be bypassed by the boot ROM code before
branching to the user application.
592 ROM Code and Peripheral Booting SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Boot ROM Description
SPRUHX5G – August 2014 – Revised September 2019 ROM Code and Peripheral Booting 593
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Chapter 5
SPRUHX5G – August 2014 – Revised September 2019
The direct memory access (DMA) module provides a hardware method of transferring data between
peripherals and/or memory without intervention from the CPU, thereby freeing up bandwidth for other
system functions. Additionally, the DMA has the capability to orthogonally rearrange the data as it is
transferred as well as “ping-pong” data between buffers. These features are useful for structuring data into
blocks for optimal CPU processing.
594 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Introduction
5.1 Introduction
The strength of a controller is not measured purely in processor speed, but in total system capabilities. As
a part of the equation, any time the CPU bandwidth for a given function can be reduced, the greater the
system capabilities. Many times applications spend a significant amount of their bandwidth moving data,
whether it is from off-chip memory to on-chip memory, or from a peripheral such as an analog-to-digital
converter (ADC) to RAM, or even from one peripheral to another. Furthermore, many times this data
comes in a format that is not conducive to the optimum processing powers of the CPU. The DMA module
described in this reference guide has the ability to free up CPU bandwidth and rearrange the data into a
pattern for more streamlined processing.
The DMA module is an event-based machine, meaning it requires a peripheral or software trigger to start
a DMA transfer. Although it can be made into a periodic time-driven machine by configuring a timer as the
DMA trigger source, there is no mechanism within the module itself to start memory transfers periodically.
The DMA module has six independent DMA channels which can be configured separately and each
channel contains its own independent PIE interrupt to let the CPU know when a DMA transfer has either
started or completed. Five of the six channels are exactly the same, while Channel 1 has the ability to be
configured at a higher priority than the others. At the heart of the DMA is a state machine and tightly
coupled address control logic. It is this address control logic that allows for rearrangement of the block of
data during the transfer as well as the process of ping-ponging data between buffers. Each of these
features, along with others, will be discussed in detail in this document.
5.2 Features
DMA features include:
• Six channels with independent PIE interrupts
• Each DMA channel can be triggered from multiple peripheral trigger sources independently
• Word Size: 16-bit or 32-bit (SPI limited to 16-bit)
• Throughput: 3 cycles/word without arbitration
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 595
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Architecture www.ti.com
5.3 Architecture
C28x Bus
DMA Bus
TINT (0-2)
DMA_CHx (1-6)
XINT (1-5) DMA Trigger
Source Selection
ADC INT (A-D) (1-4), EVT (A-D) DMACHSRCSEL1.CHx DMA C28x
SDxFLTy (x = 1 to 2, y = 1 to 4) DMACHSRCSEL2.CHx
SOCA (1-12), SOCB (1-12) CHx.MODE.PERINTSEL
MXEVT (A-B), MREVT (A-B) (x = 1 to 6)
PIE
SPITX (A-C), SPIRX (A-C)
eQEP
eCAP
DAC
596 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Architecture
NOTE: If CPU and DMA make an access to the same peripheral frame in the same cycle, the DMA
has priority and the CPU is stalled.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 597
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Architecture www.ti.com
DMA
DMACHSRCSELx.CH1 CH1.MODE.PERINTSEL[4:0] = 1
256 X 1
Mux ‘1’ 0
1
All DMA Trigger
Sources 2
6
Trigger Source for CH1
7
(Active Low)
DMACHSRCSELx.CH2 31
256 X 1
Mux
CH2.MODE.PERINTSEL[4:0] = 2
0
1
31
DMACHSRCSELx.CH6
256 X 1
Mux
CH6.MODE.PERINTSEL[4:0] = 6
0
1
31
NOTE: To use the system level DMA Trigger source selection, the DMA internal trigger source
selection configuration for each channel should be done using the DMACHSRCSELx
register, and the CHx.MODE.PERINTSEL register as shown here. See Table 5-1 or the
DMACHSRCSELx register definition for a complete list of DMA trigger sources.
598 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Architecture
Regardless of the value of the MODE.CHx[PERINTSEL] bit field, software can always force a trigger by
using the CONTROL.CHx[PERINTFRC] bit. Likewise, software can always clear a pending DMA trigger
using the CONTROL.CHx[PERINTCLR] bit.
Once a particular peripheral trigger event sets a channel’s PERINTFLG bit, the bit remains pending until
the priority logic of the state machine starts the burst transfer for that channel. Once the burst transfer
starts, the flag is cleared. If a new peripheral trigger event is generated while a burst is in progress, the
burst will complete before responding to the new peripheral trigger event (after proper prioritization). If a
third peripheral trigger event occurs before the pending event is serviced, an error flag is set in the
CONTROL.CHx[OVRFLG] bit. If a peripheral trigger event occurs at the same time as the latched flag is
being cleared, the trigger event has priority and the PERINTFLG will remain set.
Figure 5-4 shows a diagram of the trigger select circuit. See the DMACHSRCSELx register description for
the complete list of peripheral trigger event sources.
PERINTSEL
Clear
PERINTCLR
Latch DMA Trigger Event
(DMACHSRCSELx) Peripheral DMA Trigger
Set MODE.CHx.PERINTE
Software Trigger
[PERINTFRC = 1]
Table 5-1 shows the peripheral trigger source options that are available for each channel.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 599
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Architecture www.ti.com
600 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Architecture
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 601
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Architecture www.ti.com
602 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Address Pointer and Transfer Control
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 603
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Address Pointer and Transfer Control www.ti.com
Source and Destination Transfer Size (TRANSFER_SIZE): — This specifies the number of bursts to be
transferred per CPU interrupt (if enabled).
Whether this interrupt is generated at the beginning or the end of the transfer is defined in the
CHINTMODE bit in the MODE register. Whether the channel remains enabled or not after the
transfer is completed is defined by the CONTINUOUS bit in the MODE register. The
TRANSFER_SIZE register is loaded into the TRANSFER_COUNT register at the beginning of each
transfer. The TRANSFER_COUNT register keeps track of how many bursts of data the channel has
transferred and when it reaches zero, the DMA transfer is complete.
Source/Destination Wrap Size (SRC/DST_WRAP_SIZE)— This specifies the number of bursts to be
transferred before the current address pointer wraps around to the beginning.
604 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Address Pointer and Transfer Control
This feature is used to implement a circular addressing type function. This value is loaded into the
appropriate SRC/DST_WRAP_COUNT register at the beginning of each transfer. The
SRC/DST_WRAP_COUNT registers keep track of how many bursts of data the channel has
transferred and when they reach zero, the wrap procedure is performed on the appropriate source
or destination address pointer. A separate size and count register is allocated for source and
destination pointers. To disable the wrap function, assign the value of these registers to be larger
than the TRANSFER_SIZE.
NOTE: The value written to the SIZE registers is one less than the intended size. So, to transfer
three 16-bit words, the value 2 should be placed in the SIZE register.
Regardless of the state of the DATASIZE bit, the value specified in the SIZE registers are for
16-bit addresses. So, to transfer three 32-bit words, the value 5 should be placed in the SIZE
register.
For each source/destination pointer, the address changes can be controlled with the following step values:
Source/Destination Burst Step (SRC/DST_BURST_STEP)— Within each burst transfer, the address
source and destination step sizes are specified by these registers.
This value is a signed 2's compliment number so that the address pointer can be incremented or
decremented as required. If no increment is desired, such as when accessing the data receive or
transmit registers in a communication peripheral, the value of these registers should be set to zero.
Source/Destination Transfer Step (SRC/DST_TRANSFER_STEP)— This specifies the address offset to
start the next burst transfer after completing the current burst transfer.
This is used in cases where registers or data memory locations are spaced at constant intervals.
This value is a signed 2's compliment number so that the address pointer can be incremented or
decremented as required.
Source/Destination Wrap Step (SRC/DST_WRAP_STEP): — When the wrap counter reaches zero, this
value specifies the number of words to add/subtract from the SRC/DST_BEG_ADDR pointer and
hence sets the new start address.
This implements a circular type of addressing mode, useful in many applications. This value is a
signed 2's compliment number so that the address pointer can be incremented or decremented as
required.
NOTE: Regardless of the state of the DATASIZE bit, the value specified in the STEP registers are
for 16-bit addresses. So, to increment one 32-bit address, a value of 2 should be placed in
these registers.
Channel Interrupt Mode (CHINTMODE)— This mode bit selects whether the DMA interrupt from the
respective channel is generated at the beginning of a new transfer or at the end of the transfer.
If implementing a ping-pong buffer scheme with continuous mode of operation, then the interrupt
would be generated at the beginning, just after the working registers are copied to the shadow set.
If the DMA does not operate in continuous mode, then the interrupt is typically generated at the end
when the transfer is complete.
All of the above features and modes are shown in Figure 5-5.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 605
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Address Pointer and Transfer Control www.ti.com
No
DMA trigger event?
Yes
Yes WRAP_COUNT !=
WRAP_COUNT = WRAP_SIZE
WRAP_SIZE
No
TRANSFER_COUNT = TRANSFER_SIZE
DMA Transfer in Progress (TRANSFER_STS = 1)
HALT
BURST_COUNT = BURST_SIZE
here
BURST in Progress (BURST_STS = 1)
*DST_ADDR_ACTIVE = *SRC_ADDR_ACTIVE
Yes
Yes
SRC_WRAP_COUNT -- SRC_WRAP_COUNT > 0 DST_WRAP_COUNT -- DST_WRAP_COUNT > 0
No
Points where No
state machine Wait for DMA Trigger Event
branches to next
channel No Another DMA trigger
event
Yes
606 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Pipeline Timing and Throughput
If instead the channel were configured to transfer the same amount of data 32 bits at a time (the word size
is configured to 32 bits) the transfer would take:
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 607
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Channel Priority www.ti.com
The DMA module consists of a 3-stage pipeline as shown in Figure 5-6 and Figure 5-7.
In the case above, after each channel has transferred a burst of words, the next channel is serviced. You
can specify the size of the burst for each channel. Once CH6 (or the last enabled channel) has been
serviced, and no other channels are pending, the round-robin state machine enters an idle state.
From the idle state, channel 1 (if enabled) is always serviced first. However, if the DMA is currently
processing another channel x, all other pending channels between x and the end of the round are serviced
before CH1. It is in this sense that all the channels are of equal priority. For instance, take an example
where CH1, CH4, and CH5 are enabled in round-robin mode and CH4 is currently being processed. Then
CH1 and CH5 both receive an interrupt trigger from their respective peripherals before CH4 completes.
CH1 and CH5 are now both pending. When CH4 completes its burst, CH5 will be serviced next. Only after
CH5 completes will CH1 be serviced. Upon completion of CH1, if there are no more channels pending, the
round-robin state machine will enter an idle state.
A more complicated example is shown below:
• Assume all channels are enabled, and the DMA is in an idle state,
• Initially a trigger occurs on CH1, CH3, and CH5 on the same cycle,
608 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Channel Priority
• When the CH1 burst transfer starts, requests from CH3 and CH5 are pending,
• Before completion of the CH1 burst, the DMA receives a request from CH2. Now the pending requests
are from CH2, CH3, and CH5,
• After completing the CH1 burst, CH2 will be serviced since it is next in the round-robin scheme after
CH1.
• After the burst from CH2 is finished, the CH3 burst will be serviced, followed by CH5 burst.
• Now while the CH5 burst is being serviced, the DMA receives a request from CH1, CH3, and CH6.
• The burst from CH6 will start after the completion of the CH5 burst since it is the next channel after
CH5 in the round-robin scheme.
• This will be followed by the CH1 burst and then the CH3 burst
• After the CH3 burst finishes, assuming no more triggers have occurred, the round-robin state machine
will enter an idle state.
The round-robin state machine may be reset to the idle state via the DMACTRL[PRIORITYRESET] bit.
Given an example where CH1, CH4 and CH5 are enabled in Channel 1 High Priority Mode and CH4 is
currently being processed. Then CH1 and CH5 both receive an interrupt trigger from their respective
peripherals before CH4 completes. CH1 and CH5 are now both pending. When the current CH4 word
transfer is completed, regardless of whether the DMA has completed the entire CH4 burst, CH4 execution
will be suspended and CH1 will be serviced. After the CH1 burst completes, CH4 will resume execution.
Upon completion of CH4, CH5 will be serviced. After CH5 completes, if there are no more channels
pending, the round-robin state machine will enter an idle state.
Typically Channel 1 would be used in this mode for the ADC, since its data rate is so high. However,
Channel 1 High Priority Mode may be used in conjunction with any peripheral.
NOTE: High-priority mode and ONESHOT mode may not be used at the same time on channel 1.
Other channels may use ONESHOT mode when channel 1 is in high-priority mode.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 609
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Overrun Detection Feature www.ti.com
DMA
channel interrupt DMACHx interrupt generated
PIE at beginning or end of transfer
CHx.MODE[CHINTE] CHx.CONTROL[OVRFLG]
CHx.CONTROL[PERINTFLG]
PERx_INT
Latch
CHx.CONTROL[ERRCLR]
CHx.MODE[OVERINTE]
610 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 611
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
Complex bit access types are encoded to fit into small table cells. Table 5-5 shows the codes that are
used for access types in this section.
612 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
If CH1 is high-priority, the state machine restarts from CH2 (or the
next highest enabled channel).
Reset type: SYSRSn
0 HARDRESET R-0/W1S 0h Writing a 1 to the hard reset bit resets the whole DMA and aborts
any current access (similar to applying a device reset). Writes of 0
are ignored and this bit always reads back a 0.
When writing to this bit, there is a one cycle delay before it takes
effect. Hence, a one-cycle delay (such as a NOP instruction) is
required in software before attempting to access any other DMA
register.
Reset type: SYSRSn
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 613
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
This bit specifies the action when an emulation halt event occurs.
Reset type: SYSRSn
0h (R/W) = The DMA completes the current read-write operation,
then halts.
1h (R/W) = The DMA continues running during an emulation halt.
14-0 RESERVED R 0h Reserved
614 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
This bit selects whether CH1 has high priority or not. The priority can
only be changed when all channels are disabled. A priority reset
should be performed before restarting channels after changing
priority
Reset type: SYSRSn
0h (R/W) = CH1 has the same priority as the other channels
1h (R/W) = CH1 has a higher priority than the other channels
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 615
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
616 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
Complex bit access types are encoded to fit into small table cells. Table 5-11 shows the codes that are
used for access types in this section.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 617
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
618 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
If this bit is set to 1, each peripheral event trigger causes the channel
to perform an entire transfer. Otherwise, the channel only performs
one burst per trigger.
Reset type: SYSRSn
9 CHINTMODE R/W 0h Channel Interrupt Generation Mode
This bit specifies when the DMA channel generates a CPU interrupt
for a transfer.
Reset type: SYSRSn
0h (R/W) = Generate interrupt at beginning of new transfer
1h (R/W) = Generate interrupt at end of transfer.
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 619
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
These are legacy bits and should be set to the channel number. The
actual source selection is done via the DMACHSRCSELn registers,
which are part of the DMA_CLA_SRC_SEL_REGS group.
Reset type: SYSRSn
620 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
This bit indicates that a peripheral event trigger was received while
PERINTFLG was already set. It can be cleared by writing to the
ERRCLR bit.
Reset type: SYSRSn
0h (R/W) = No overflow detected
1h (R/W) = Overflow detected
13 RUNSTS R 0h Run Status Flag
This bit is set when a DMA burst begins. The BURST_COUNT is set
to the BURST_SIZE. This bit is cleared when BURST_COUNT
reaches zero, or when the HARDRESET or SOFTRESET bit is set.
Reset type: SYSRSn
0h (R/W) = No burst activity
1h (R/W) = The DMA is currently servicing or suspending a burst
transfer from this channel
11 TRANSFERSTS R 0h Transfer Status Flag
This bit is set when a DMA transfer begins. The address registers
are copied to the shadow set and the TRANSFER_COUNT is set to
the TRANSFER_SIZE. This bit is cleared when
TRANSFER_COUNT reaches zero, or when the HARDRESET or
SOFTRESET bit is set.
Reset type: SYSRSn
0h (R/W) = No transfer activity
1h (R/W) = The channel is currently in the middle of a transfer
regardless of whether a burst of data is actively being transferred
or not
10 RESERVED R 0h Reserved
9 RESERVED R 0h Reserved
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 621
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
This bit indicates whether a peripheral event trigger has arrived. This
bit is automatically cleared when the first burst transfer begins.
Reset type: SYSRSn
0h (R/W) = Waiting for event trigger
1h (R/W) = Event trigger pending
7 ERRCLR R-0/W1S 0h Clear Error
Writing a 1 to this bit will clear the OVRFLG bit. This is normally
done when initializing the DMA module or if an overflow condition is
detected. If an overflow event occurs at the same time this bit is set,
the overrun has priority and the OVRFLG bit is set.
Reset type: SYSRSn
6 RESERVED R-0/W1S 0h Reserved
5 RESERVED R-0/W1S 0h Reserved
4 PERINTCLR R-0/W1S 0h Clear Peripheral Event Trigger
If the PERINTE bit of the MODE register is set, writing a 1 to this bit
sets PERINTFLG, which triggers a DMA burst. This bit can be used
to start a DMA transfer in software.
Reset type: SYSRSn
2 SOFTRESET R-0/W1S 0h Channel Soft Reset
Writing a 1 to this bit places the channel into its default state after
the current read/write access has completed:
RUNSTS = 0
TRANSFERSTS = 0
BURSTSTS = 0
BURST_COUNT = 0
TRANSFER_COUNT = 0
SRC_WRAP_COUNT = 0
DST_WRAP_COUNT = 0
When writing to this bit, there is a one cycle delay before it takes
effect. Hence, a one-cycle delay (such as a NOP instruction) is
required in software before attempting to access any other DMA
register.
Reset type: SYSRSn
1 HALT R-0/W1S 0h Halt Channel
Writing a 1 to this bit halts the DMA channel in its current state after
any ongoing read/write access has completed.
Reset type: SYSRSn
622 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
Writing a 1 to this bit enables the DMA channel and sets the
RUNSTS bit to 1. This bit is also used to resume after a channel
halt.
The RUN bit is typically used to start the DMA channel after
configuration. The channel will then wait for the first peripheral event
trigger (PERINTFLG == 1) to start a burst.
Reset type: SYSRSn
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 623
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
624 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 625
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
626 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 627
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
628 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 629
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
630 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 631
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
632 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 633
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
634 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 635
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
636 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 637
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
At the start of a transfer, the value in this register is loaded into the
SRC_BEG_ADDR_ACTIVE register and used as the beginning
value for the source address. This register can be safely updated
during a transfer.
Reset type: SYSRSn
638 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
At the start of a transfer, the value in this register is loaded into the
SRC_ADDR_ACTIVE register and used as the value of the source
address. This register can be safely updated during a transfer.
Reset type: SYSRSn
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 639
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
640 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 641
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
At the start of a transfer, the value in this register is loaded into the
DST_BEG_ADDR_ACTIVE register and used as the beginning value
for the destination address. This register can be safely updated
during a transfer.
Reset type: SYSRSn
642 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
At the start of a transfer, the value in this register is loaded into the
DST_ADDR_ACTIVE register and used as the value of the
destination address. This register can be safely updated during a
transfer.
Reset type: SYSRSn
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 643
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
644 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 645
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
DMA Registers www.ti.com
646 Direct Memory Access (DMA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com DMA Registers
SPRUHX5G – August 2014 – Revised September 2019 Direct Memory Access (DMA) 647
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Chapter 6
SPRUHX5G – August 2014 – Revised September 2019
The Control Law Accelerator (CLA) Type-1 is an independent, fully-programmable, 32-bit floating-point
math processor that brings concurrent control-loop execution to the C28x family. The low interrupt latency
of the CLA allows it to read ADC samples "just-in-time." This significantly reduces the ADC sample to
output delay to enable faster system response and higher MHz control loops. By using the CLA to service
time-critical control loops, the main CPU is free to perform other system tasks such as communications
and diagnostics. This chapter provides an overview of the architectural structure and components of the
control law accelerator.
648 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Introduction
6.1 Introduction
The Control Law Accelerator extends the capabilities of the C28x CPU by adding parallel processing.
Time-critical control loops serviced by the CLA can achieve low ADC sample to output delay. Thus, the
CLA enables faster system response and higher frequency control loops. Utilizing the CLA for time-critical
tasks frees up the main CPU to perform other system and communication functions concurrently.
6.2 Features
The following is a list of major features of the CLA:
• C compilers are available for CLA software development.
• Clocked at the same rate as the main CPU (SYSCLKOUT).
• An independent architecture allowing CLA algorithm execution independent of the main C28x CPU.
– Complete bus architecture:
• Program Address Bus (PAB) and Program Data Bus (PDB)
• Data Read Address Bus (DRAB), Data Read Data Bus (DRDB), Data Write Address Bus
(DWAB), and Data Write Data Bus (DWDB)
– Independent eight stage pipeline.
– 16-bit program counter (MPC)
– Four 32-bit result registers (MR0-MR3)
– Two 16-bit auxiliary registers (MAR0, MAR1)
– Status register (MSTF)
• Instruction set includes:
– IEEE single-precision (32-bit) floating point math operations
– Floating-point math with parallel load or store
– Floating-point multiply with parallel add or subtract
– 1/X and 1/sqrt(X) estimations
– Data type conversions.
– Conditional branch and call
– Data load/store operations
• The CLA program code can consist of up to eight tasks or interrupt service routines
– The start address of each task is specified by the MVECT registers.
– No limit on task size as long as the tasks fit within the configurable CLA program memory space.
– One task is serviced at a time until its completion. There is no nesting of tasks.
– Upon task completion a task-specific interrupt is flagged within the PIE.
– When a task finishes the next highest-priority pending task is automatically started.
• Task trigger mechanisms:
– C28x CPU via the IACK instruction
– Task1 to Task8: up to 256 possible trigger sources from peripherals connected to the shared bus
on which the CLA assumes secondary ownership.
• Memory and Shared Peripherals:
– Two dedicated message RAMs for communication between the CLA and the main CPU.
– The C28x CPU can map CLA program and data memory to the main CPU space or CLA space.
– The CLA, on reset, is the secondary master for all peripherals which can have either the CLA or
DMA as their secondary master.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 649
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Features www.ti.com
CLA Control
Register Set
MIFR(16) CLA_INT1
From MPERINT1 to
MIOVF(16)
Shared to MICLR(16) CLA_INT8
Peripherals MPERINT8 MICLROVF(16) INT11 C28x
PIE
MIFRC(16) INT12 CPU
MIER(16)
MIRUN(16)
LVF
LUF
MVECT1(16)
MVECT2(16)
MVECT3(16)
SYSCLK MVECT4(16)
CLA Clock Enable MVECT5(16)
SYSRSn CPU Read/Write Data Bus
MVECT6(16)
MVECT7(16)
MVECT8(16) CLA Program
CLA Program Bus Memory (LSx)
MCTL(16)
LSxMSEL[MSEL_LSx]
LSxCLAPGM[CLAPGM_LSx]
650 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Interface
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 651
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Interface www.ti.com
652 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Interface
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 653
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Interface www.ti.com
654 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Interface
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 655
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA and CPU Arbitration www.ti.com
These blocks are useful for passing data between the CLA and CPU. No opcode fetches, from either the
CLA or CPU, are allowed from the message RAMs. A write protection violation will not be generated if the
CLA attempts to write to the CPU to CLA message RAM but the write will be ignored. The arbitration
scheme for the message RAMs are the same as those for the shared memories described in the
Section 3.11.
The message RAMs have the following characteristics:
• CLA to CPU Message RAM:
The following accesses are allowed:
– CPU reads
– CLA data reads and writes
– CPU debug reads and writes
656 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Configuration and Debug
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 657
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Configuration and Debug www.ti.com
658 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Configuration and Debug
NOTE: A CLA fetch has higher priority than CPU debug reads. For this reason, it is possible for the
CLA to permanently block CPU debug accesses if the CLA is executing in a loop. This might
occur when initially developing CLA code due to a bug that causes an infinite loop. To avoid
locking up the main CPU, the program memory will return all 0x0000 for CPU debug reads
when the CLA is running. When the CLA is halted or idle then normal CPU debug read and
write access to CLA program memory can be performed.
If the CLA gets caught in an infinite loop, you can use a soft or hard reset to exit the
condition. A debugger reset will also exit the condition.
There are special cases that can occur when single-stepping a task such that the program counter,
MPC, reaches the MSTOP instruction at the end of the task.
• MPC halts at or after the MSTOP with a task already pending
If you are single-stepping or halted in "task A" and "task B" comes in before the MPC reaches the
MSTOP, then "task B" will start if you continue to step through the MSTOP instruction. Basically if
"task B" is pending before the MPC reaches MSTOP in "task A" then there is no issue in "task B"
starting and no special action is required.
• MPC halts at or after the MSTOP with no task pending
In this case you have single-stepped or halted in "task A" and the MPC has reached the MSTOP
with no tasks pending. If "task B" comes in at this point, it will be flagged in the MIFR register but it
may or may not start if you continue to single-step through the MSTOP instruction of "task A."
It depends on exactly when the new task comes in. To reliably start "task B" perform a soft reset
and reconfigure the MIER bits. Once this is done, you can start single-stepping "task B."
This case can be handled slightly differently if there is control over when "task B" comes in (for
example using the IACK instruction to start the task). In this case you have single-stepped or halted
in "task A" and the MPC has reached the MSTOP with no tasks pending. Before forcing "task B,"
run free to force the CLA out of the debug state. Once this is done you can force "task B" and
continue debugging.
5. Disable CLA breakpoints, if desired
In Code Composer Studio you can disable the CLA breakpoints by disconnecting the CLA core in the
debug perspective. Make sure to first issue a run or reset; otherwise, the CLA will be halted and no
other tasks will start.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 659
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Configuration and Debug www.ti.com
660 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Pipeline
6.6 Pipeline
This section describes the CLA pipeline stages and presents cases where pipeline alignment must be
considered.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 661
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Pipeline www.ti.com
662 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Pipeline
<Instruction 8> ; I8
<Instruction 9> ; I9
....
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 663
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Pipeline www.ti.com
664 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Pipeline
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 665
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
666 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Each instruction has a table that gives a list of the operands and a short description. Instructions always
have their destination operand(s) first followed by the source operand(s).
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 667
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Encoding for the shift fields in the MASR32, MLSR32 and MLSL32 instructions is shown in Table 6-8.
668 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Table 6-10 shows the condition field encoding for conditional instructions such as MNEGF, MSWAPF,
MBCNDD, MCCNDD, and MRCNDD.
For instructions that use MRx (where x could be 'a' through 'f') as operands, the trailing alphabet appears
in the opcode as a two-bit field. For example,
MMPYF32 MRa, MRb, MRc ||
MADDF32 MRd, MRe, MRf
The two-bit field specifies one of four working registers according to Table 6-9.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 669
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
6.7.3 Instructions
The instructions are listed alphabetically, preceded by a summary.
Table 6-11. General Instructions
Title ...................................................................................................................................... Page
670 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 671
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description The absolute value of MRb is loaded into MRa. Only the sign bit of the operand is
modified by the MMABSF32 instruction.
if (MRb < 0) {MRa = -MRb};
else {MRa = MRb};
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
672 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point destination register (MR0 to MR3)
MRc CLA floating-point destination register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; };
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 673
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
MRb CLA floating-point source register (MR0 to MR3)
Description Add MRb to the floating-point value represented by the immediate operand. Store the
result of the addition in MRa.
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. #16FHi is
most useful for representing constants where the lowest 16-bits of the mantissa are 0.
Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and -1.5
(0xBFC00000). The assembler will accept either a hex or float as the immediate value.
That is, the value -1.5 can be represented as #-1.5 or #0xBFC0.
MRa = MRb + #16FHi:0;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
674 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Add MRb to the floating-point value represented by the immediate operand. Store the
result of the addition in MRa.
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. #16FHi is
most useful for representing constants where the lowest 16-bits of the mantissa are 0.
Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and -1.5
(0xBFC00000). The assembler will accept either a hex or float as the immediate value.
That is, the value -1.5 can be represented as #-1.5 or #0xBFC0.
MRa = MRb + #16FHi:0;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 675
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
676 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
MRc CLA floating-point source register (MR0 to MR3)
Description Add the contents of MRc to the contents of MRb and load the result into MRa.
MRa = MRb + MRc;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 677
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MADDF32 MRd, MRe, MRf||MMOV32 mem32, MRa 32-Bit Floating-Point Addition with Parallel Move
Operands
MRd CLA floating-point destination register for the MADDF32 (MR0 to MR3)
MRe CLA floating-point source register for the MADDF32 (MR0 to MR3)
MRf CLA floating-point source register for the MADDF32 (MR0 to MR3)
mem32 32-bit memory location accessed using one of the available addressing modes. This
will be the destination of the MMOV32.
MRa CLA floating-point source register for the MMOV32 (MR0 to MR3)
Description Perform an MADDF32 and a MMOV32 in parallel. Add MRf to the contents of MRe and
store the result in MRd. In parallel move the contents of MRa to the 32-bit location
mem32.
MRd = MRe + MRf;
[mem32] = MRa;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
678 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MADDF32 MRd, MRe, MRf ||MMOV32 MRa, mem32 32-Bit Floating-Point Addition with Parallel Move
Operands
MRd CLA floating-point destination register for the MADDF32 (MR0 to MR3).
MRd cannot be the same register as MRa.
MRe CLA floating-point source register for the MADDF32 (MR0 to MR3)
MRf CLA floating-point source register for the MADDF32 (MR0 to MR3)
MRa CLA floating-point destination register for the MMOV32 (MR0 to MR3).
MRa cannot be the same register as MRd.
mem32 32-bit memory location accessed using one of the available addressing modes. This is
the source for the MMOV32.
Description Perform an MADDF32 and a MMOV32 operation in parallel. Add MRf to the contents of
MRe and store the result in MRd. In parallel move the contents of the 32-bit location
mem32 to MRa.
MRd = MRe + MRf;
MRa = [mem32];
Restrictions The destination register for the MADDF32 and the MMOV32 must be unique. That is,
MRa and MRd cannot be the same register.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes Yes Yes
Pipeline The MADDF32 and the MMOV32 both complete in a single cycle.
Example 1 ; Given A, B and C are 32-bit floating-point numbers
; Calculate Y1 = A + 4B
; Y2 = A + C
;
_Cla1Task1:
MMOV32 MR0, @A ; Load MR0 with A
MMOV32 MR1, @B ; Load MR1 with B
MMPYF32 MR1, MR1, #4.0 ; Multiply 4 * B
|| MMOV32 MR2, @C and in parallel load C
MADDF32 MR3, MR0, MR1 ; Add A + 4B
MADDF32 MR3, MR0, MR2 ; Add A + C
|| MMOV32 @Y1, MR3 ; and in parallel store A+4B
MMOV32 @Y2, MR3 ; store A + C MSTOP
; end of task
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 679
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
680 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
MRc CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; }
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 681
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
#SHIFT Number of bits to shift (1 to 32)
Description Arithmetic shift right of MRa by the number of bits indicated. The number of bits can be 1
to 32.
MARa(31:0) = Arithmetic Shift(MARa(31:0) by #SHIFT bits);
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; }
682 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
16BitDest 16-bit destination if condition is true
CNDF Optional condition tested
Description If the specified condition is true, then branch by adding the signed 16BitDest value to the
MPC value. Otherwise, continue without branching. If the address overflows, it wraps
around. Therefore a value of "0xFFFE" will put the MPC back to the MBCNDD
instruction.
Please refer to the pipeline section for important information regarding this instruction.
if (CNDF == TRUE) MPC += 16BitDest;
Restrictions The MBCNDD instruction is not allowed three instructions before or after a MBCNDD,
MCCNDD or MRCNDD instruction. Refer to the pipeline section for more information.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline The MBCNDD instruction by itself is a single-cycle instruction. As shown in Table 6-12
for each branch 6 instruction slots are executed; three before the branch instruction (I2-
I4) and three after the branch instruction (I5-I7). The total number of cycles for a branch
taken or not taken depends on the usage of these slots. That is, the number of cycles
depends on how many slots are filled with a MNOP as well as which slots are filled. The
effective number of cycles for a branch can, therefore, range from 1 to 7 cycles. The
number of cycles for a branch taken may not be the same as for a branch not taken.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 683
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Referring to Table 6-12 and Table 6-13, the instructions before and after MBCNDD have
the following properties:
• I1
– I1 is the last instruction that can effect the CNDF flags for the MBCNDD
instruction. The CNDF flags are tested in the D2 phase of the pipeline. That is, a
decision is made whether to branch or not when MBCNDD is in the D2 phase.
– There are no restrictions on the type of instruction for I1.
• I2, I3 and I4
– The three instructions proceeding MBCNDD can change MSTF flags but will have
no effect on whether the MBCNDD instruction branches or not. This is because
the flag modification will occur after the D2 phase of the MBCNDD instruction.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
• I5, I6 and I7
– The three instructions following MBCNDD are always executed irrespective of
whether the branch is taken or not.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
<Instruction 1> ; I1 Last instruction that can affect flags for
; the MBCNDD operation
<Instruction 2> ; I2 Cannot be stop, branch, call or return
<Instruction 3> ; I3 Cannot be stop, branch, call or return
<Instruction 4> ; I4 Cannot be stop, branch, call or return
MBCNDD _Skip, NEQ ; Branch to Skip if not eqal to zero
; Three instructions after MBCNDD are always
; executed whether the branch is taken or not
<Instruction 5> ; I5 Cannot be stop, branch, call or return
<Instruction 6> ; I6 Cannot be stop, branch, call or return
<Instruction 7> ; I7 Cannot be stop, branch, call or return
<Instruction 8> ; I8
<Instruction 9> ; I9
....
_Skip:
<Destination 1> ; d1 Can be any instruction
<Destination 2> ; d2
<Destination 3> ; d3
....
....
MSTOP
....
684 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 685
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
686 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Skip1:
MMOV32 MR3, @SteadyState
MMOVXI MR2, #STEADYMASK
MOR32 MR3, MR2
MBCNDD Skip2, NTF ; (B) if State != .01, go to Skip2
MMOV32 MR1, @CoastState ; Always executed
MMOVXI MR2, #COASTMASK ; Always executed
MOR32 MR1, MR2 ; Always executed
MMOV32 @CoastState, MR1 ; Execute if (B) branch not taken
MSTOP ; end of task if (B) branch not taken
Skip2:
MMOV32 @SteadyState, MR3 ; Executed if (B) branch taken
MSTOP
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 687
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
16BitDest 16-bit destination if condition is true
CNDF Optional condition to be tested
Description If the specified condition is true, then store the return address in the RPC field of MSTF
and make the call by adding the signed 16BitDest value to the MPC value. Otherwise,
continue code execution without making the call. If the address overflows, it wraps
around. Therefore a value of "0xFFFE" will put the MPC back to the MCCNDD
instruction.
Please refer to the pipeline section for important information regarding this instruction.
if (CNDF == TRUE)
{
RPC = return address;
MPC += 16BitDest;
};
Restrictions The MCCNDD instruction is not allowed three instructions before or after a MBCNDD,
MCCNDD, or MRCNDD instruction. Refer to the Pipeline section for more details.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
688 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Pipeline The MCCNDD instruction by itself is a single-cycle instruction. As shown in Table 6-14,
for each call 6 instruction slots are executed; three before the call instruction (I2-I4) and
three after the call instruction (I5-I7). The total number of cycles for a call taken or not
taken depends on the usage of these slots. That is, the number of cycles depends on
how many slots are filled with a MNOP as well as which slots are filled. The effective
number of cycles for a call can, therefore, range from 1 to 7 cycles. The number of
cycles for a call taken may not be the same as for a call not taken.
Referring to the following code fragment and the pipeline diagrams in Table 6-14 and
Table 6-15, the instructions before and after MCCNDD have the following properties:
• I1
– I1 is the last instruction that can effect the CNDF flags for the MCCNDD
instruction. The CNDF flags are tested in the D2 phase of the pipeline. That is, a
decision is made whether to branch or not when MCCNDD is in the D2 phase.
– There are no restrictions on the type of instruction for I1.
• I2, I3 and I4
– The three instructions proceeding MCCNDD can change MSTF flags but will have
no effect on whether the MCCNDD instruction makes the call or not. This is
because the flag modification will occur after the D2 phase of the MCCNDD
instruction.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
• I5, I6 and I7
– The three instructions following MBCNDD are always executed irrespective of
whether the branch is taken or not.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 689
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
690 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Example ;
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 691
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MCMP32 MRa, MRb 32-Bit Integer Compare for Equal, Less Than or Greater Than
Operands
MRa CLA floating-point source register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Set ZF and NF flags on the result of MRa - MRb where MRa and MRb are 32-bit
integers. For a floating point compare refer to MCMPF32.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
692 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MCMPF32 MRa, MRb 32-Bit Floating-Point Compare for Equal, Less Than or Greater Than
Operands
MRa CLA floating-point source register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Set ZF and NF flags on the result of MRa - MRb. The MCMPF32 instruction is performed
as a logical compare operation. This is possible because of the IEEE format offsetting
the exponent. Basically the bigger the binary number, the bigger the floating-point value.
Special cases for inputs:
• Negative zero will be treated as positive zero.
• A denormalized value will be treated as positive zero.
• Not-a-Number (NaN) will be treated as infinity.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 693
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MCMPF32 MRa, #16FHi 32-Bit Floating-Point Compare for Equal, Less Than or Greater Than
Operands
MRa CLA floating-point source register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Compare the value in MRa with the floating-point value represented by the immediate
operand. Set the ZF and NF flags on (MRa - #16FHi:0).
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. This
addressing mode is most useful for constants where the lowest 16-bits of the mantissa
are 0. Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and
-1.5 (0xBFC00000). The assembler will accept either a hex or float as the immediate
value. That is, -1.5 can be represented as #-1.5 or #0xBFC0.
The MCMPF32 instruction is performed as a logical compare operation. This is possible
because of the IEEE floating-point format offsets the exponent. Basically the bigger the
binary number, the bigger the floating-point value.
Special cases for inputs:
• Negative zero will be treated as positive zero.
• Denormalized value will be treated as positive zero.
• Not-a-Number (NaN) will be treated as infinity.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
694 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
LOOP
MMOV32 MR2, *MAR1[2]++ ; MR2 = next element
MCMPF32 MR2, MR1 ; Compare MR2 with MR1
MSWAPF MR1, MR2, GT ; MR1 = MAX(MR1, MR2)
MADDF32 MR0, MR0, #-1.0 ; Decrememt the counter
MCMPF32 MR0 #0.0 ; Set/clear flags for MBCNDD
MNOP
MNOP
MNOP
MBCNDD LOOP, NEQ ; Branch if not equal to zero
MMOV32 @_Result, MR1 ; Always executed
MNOP ; Always executed
MNOP ; Always executed
MSTOP ; End of task
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 695
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
none This instruction does not have any operands
Description When CLA breakpoints are enabled, the MDEBUGSTOP instruction is used to halt a
task so that it can be debugged. That is, MDEBUGSTOP is the CLA breakpoint. If CLA
breakpoints are not enabled, the MDEBUGSTOP instruction behaves like a MNOP.
Unlike the MSTOP, the MIRUN flag is not cleared and an interrupt is not issued. A
single-step or run operation will continue execution of the task.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
696 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
none This instruction does not have any operands
Description This instruction sets the MEALLOW bit in the CLA status register MSTF. When this bit is
set, the CLA is allowed write access to EALLOW protected registers. To again protect
against CLA writes to protected registers, use the MEDIS instruction.
MEALLOW and MEDIS only control CLA write access; reads are allowed even if
MEALLOW has not been executed. MEALLOW and MEDIS are also independent from
the main CPU's EALLOW/EDIS. This instruction does not modify the EALLOW bit in the
main CPU's status register. The MEALLOW bit in MSTF only controls access for the
CLA while the EALLOW bit in the ST1 register only controls access for the main CPU.
As with EALLOW, the MEALLOW bit is overridden via the JTAG port, allowing full control
of register accesses during debug from Code Composer Studio.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 697
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
none This instruction does not have any operands
Description This instruction clears the MEALLOW bit in the CLA status register MSTF. When this bit
is clear, the CLA is not allowed write access to EALLOW-protected registers. To enable
CLA writes to protected registers, use the MEALLOW instruction.
MEALLOW and MEDIS only control CLA write access; reads are allowed even if
MEALLOW has not been executed. MEALLOW and MEDIS are also independent from
the main CPU's EALLOW/EDIS. This instruction does not modify the EALLOW bit in the
main CPU's status register. The MEALLOW bit in MSTF only controls access for the
CLA while the EALLOW bit in the ST1 register only controls access for the main CPU.
As with EALLOW, the MEALLOW bit is overridden via the JTAG port, allowing full control
of register accesses during debug from Code Composer Studio.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
698 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description This operation generates an estimate of 1/X in 32-bit floating-point format accurate to
approximately 8 bits. This value can be used in a Newton-Raphson algorithm to get a
more accurate answer. That is:
Ye = Estimate(1/X);
Ye = Ye*(2.0 - Ye*X);
Ye = Ye*(2.0 - Ye*X);
After two iterations of the Newton-Raphson algorithm, you will get an exact answer
accurate to the 32-bit floating-point format. On each iteration the mantissa bit accuracy
approximately doubles. The MEINVF32 operation will not generate a negative zero,
DeNorm or NaN value.
MRa = Estimate of 1/MRb;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 699
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description This operation generates an estimate of 1/sqrt(X) in 32-bit floating-point format accurate
to approximately 8 bits. This value can be used in a Newton-Raphson algorithm to get a
more accurate answer. That is:
Ye = Estimate(1/sqrt(X));
Ye = Ye*(1.5 - Ye*Ye*X/2.0);
Ye = Ye*(1.5 - Ye*Ye*X/2.0);
After 2 iterations of the Newton-Raphson algorithm, you will get an exact answer
accurate to the 32-bit floating-point format. On each iteration the mantissa bit accuracy
approximately doubles. The MEISQRTF32 operation will not generate a negative zero,
DeNorm or NaN value.
MRa = Estimate of 1/sqrt (MRb);
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
700 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert a 32-bit floating point value in MRb to a 16-bit integer and truncate. The result
will be stored in MRa.
MRa(15:0) = F32TOI16(MRb);
MRa(31:16) = sign extension of MRa(15);
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 701
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MF32TOI16R MRa, MRb Convert 32-Bit Floating-Point Value to 16-Bit Integer and Round
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 32-bit floating point value in MRb to a 16-bit integer and round to the nearest
even value. The result is stored in MRa.
MRa(15:0) = F32TOI16round(MRb);
MRa(31:16) = sign extension of MRa(15);
702 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 32-bit floating-point value in MRb to a 32-bit integer value and truncate.
Store the result in MRa.
MRa = F32TOI32(MRb);
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 703
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MF32TOUI16 MRa, MRb Convert 32-Bit Floating-Point Value to 16-bit Unsigned Integer
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 32-bit floating point value in MRb to an unsigned 16-bit integer value and
truncate to zero. The result will be stored in MRa. To instead round the integer to the
nearest even value use the MF32TOUI16R instruction.
MRa(15:0) = F32TOUI16(MRb);
MRa(31:16) = 0x0000;
704 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MF32TOUI16R MRa, MRb Convert 32-Bit Floating-Point Value to 16-bit Unsigned Integer and Round
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 32-bit floating-point value in MRb to an unsigned 16-bit integer and round to
the closest even value. The result will be stored in MRa. To instead truncate the
converted value, use the MF32TOUI16 instruction.
MRa(15:0) = MF32TOUI16round(MRb);
MRa(31:16) = 0x0000;
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 705
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MF32TOUI32 MRa, MRb Convert 32-Bit Floating-Point Value to 32-Bit Unsigned Integer
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 32-bit floating-point value in MRb to an unsigned 32-bit integer and store the
result in MRa.
MRa = F32TOUI32(MRb);
706 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Returns in MRa the fractional portion of the 32-bit floating-point value in MRb
See also
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 707
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the 16-bit signed integer in MRb to a 32-bit floating point value and store the
result in MRa.
MRa = MI16TOF32(MRb);
708 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem16 16-bit source memory location to be converted
Description Convert the 16-bit signed integer indicated by the mem16 pointer to a 32-bit floating-
point value and store the result in MRa.
MRa = MI16TOF32[mem16];
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 709
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem32 32-bit memory source for the MMOV32 operation.
Description Convert the 32-bit signed integer indicated by mem32 to a 32-bit floating point value and
store the result in MRa.
MRa = MI32TOF32[mem32];
_Cla1Task3:
MI32TOF32 MR0, @_M ; MR0 = 0x4BC00000
MI32TOF32 MR1, @_X ; MR1 = 0x4C200000
MI32TOF32 MR2, @_B ; MR2 = 0xCB000000
MMPYF32 MR0, MR0, #0x3380 ; M = 1/(1*2^24) * iqm = 1.5 (0x3FC00000)
MMPYF32 MR1, MR1, #0x3380 ; X = 1/(1*2^24) * iqx = 2.5 (0x40200000)
MMPYF32 MR2, MR2, #0x3380 ; B = 1/(1*2^24) * iqb = -.5 (0xBF000000)
MMPYF32 MR3, MR0, MR1 ; M*X
MADDF32 MR2, MR2, MR3 ; Y=MX+B = 3.25 (0x40500000)
710 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert the signed 32-bit integer in MRb to a 32-bit floating-point value and store the
result in MRa.
MRa = MI32TOF32(MRb);
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 711
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
#SHIFT Number of bits to shift (1 to 32)
Description Logical shift left of MRa by the number of bits indicated. The number of bits can be 1 to
32.
MARa(31:0) = Logical Shift Left(MARa(31:0) by #SHIFT bits);
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; }
712 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
#SHIFT Number of bits to shift (1 to 32)
Description Logical shift right of MRa by the number of bits indicated. The number of bits can be 1 to
32. Unlike the arithmetic shift (MASR32), the logical shift does not preserve the number's
sign bit. Every bit in the operand is moved the specified number of bit positions, and the
vacant bit-positions are filled in with zeros
MARa(31:0) = Logical Shift Right(MARa(31:0) by #SHIFT bits);
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1;}
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 713
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMACF32 MR3, MR2, MRd, MRe, MRf ||MMOV32 MRa, mem32 32-Bit Floating-Point Multiply and
Accumulate with Parallel Move
Operands
MR3 floating-point destination/source register MR3 for the add operation
MR2 CLA floating-point source register MR2 for the add operation
MRd CLA floating-point destination register (MR0 to MR3) for the multiply operation
MRd cannot be the same register as MRa
MRe CLA floating-point source register (MR0 to MR3) for the multiply operation
MRf CLA floating-point source register (MR0 to MR3) for the multiply operation
MRa CLA floating-point destination register for the MMOV32 operation (MR0 to MR3).
MRa cannot be MR3 or the same register as MRd.
mem32 32-bit source for the MMOV32 operation
Description Multiply and accumulate the contents of floating-point registers and move from register
to memory. The destination register for the MMOV32 cannot be the same as the
destination registers for the MMACF32.
MR3 = MR3 + MR2;
MRd = MRe * MRf;
MRa = [mem32];
Restrictions The destination registers for the MMACF32 and the MMOV32 must be unique. That is,
MRa cannot be MR3 and MRa cannot be the same register as MRd.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes Yes Yes
714 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 715
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
See also MMPYF32 MRa, MRb, MRc || MADDF32 MRd, MRe, MRf
716 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The ZF and NF flags are configured on the result of the operation, not the result stored
in the destination register.
if(MRa == MRb) {ZF=1; NF=0;}
if(MRa > MRb) {ZF=0; NF=0;}
if(MRa < MRb) {ZF=0; NF=1;}
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 717
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
718 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Compare MRa with the floating-point value represented by the immediate operand. If the
immediate value is larger, then load it into MRa.
if(MRa < #16FHi:0) MRa = #16FHi:0;
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. This
addressing mode is most useful for constants where the lowest 16-bits of the mantissa
are 0. Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and
-1.5 (0xBFC00000). The assembler will accept either a hex or float as the immediate
value. That is, -1.5 can be represented as #-1.5 or #0xBFC0.
Special cases for the output from the MMAXF32 operation:
• NaN output will be converted to infinity
• A denormalized output will be converted to positive zero.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The ZF and NF flags are configured on the result of the operation, not the result stored
in the destination register.
if(MRa == #16FHi:0) {ZF=1; NF=0;}
if(MRa > #16FHi:0) {ZF=0; NF=0;}
if(MRa < #16FHi:0) {ZF=0; NF=1;}
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 719
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point source/destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The ZF and NF flags are configured on the result of the operation, not the result stored
in the destination register.
if(MRa == MRb) {ZF=1; NF=0;}
if(MRa > MRb) {ZF=0; NF=0;}
if(MRa < MRb) {ZF=0; NF=1;}
Example 2 ;
; X is an array of 32-bit floating-point values
; Find the minimum value in an array X
; and store it in Result
;
_Cla1Task1:
MMOVI16 MAR1,#_X ; Start address
MUI16TOF32 MR0, @_len ; Length of the array
MNOP ; delay for MAR1 load
MNOP ; delay for MAR1 load
MMOV32 MR1, *MAR1[2]++ ; MR1 = X0
LOOP
MMOV32 MR2, *MAR1[2]++ ; MR2 = next element
MMINF32 MR1, MR2 ; MR1 = MAX(MR1, MR2)
MADDF32 MR0, MR0, #-1.0 ; Decrememt the counter
MCMPF32 MR0 #0.0 ; Set/clear flags for MBCNDD
MNOP
MNOP
MNOP
MBCNDD LOOP, NEQ ; Branch if not equal to zero
MMOV32 @_Result, MR1 ; Always executed
MNOP ; Always executed
MNOP ; Always executed
MSTOP ; End of task
720 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 721
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa floating-point source/destination register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Compare MRa with the floating-point value represented by the immediate operand. If the
immediate value is smaller, then load it into MRa.
if(MRa > #16FHi:0) MRa = #16FHi:0;
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. This
addressing mode is most useful for constants where the lowest 16-bits of the mantissa
are 0. Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and
-1.5 (0xBFC00000). The assembler will accept either a hex or float as the immediate
value. That is, -1.5 can be represented as #-1.5 or #0xBFC0.
Special cases for the output from the MMINF32 operation:
• NaN output will be converted to infinity
• A denormalized output will be converted to positive zero.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The ZF and NF flags are configured on the result of the operation, not the result stored
in the destination register.
if(MRa == #16FHi:0) {ZF=1; NF=0;}
if(MRa > #16FHi:0) {ZF=0; NF=0;}
if(MRa < #16FHi:0) {ZF=0; NF=1;}
722 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MMOV16 MARx, MRa, #16I Load the Auxiliary Register with MRa + 16-bit Immediate Value
Operands
MARx Auxiliary register MAR0 or MAR1
MRa CLA Floating-point register (MR0 to MR3)
#16I 16-bit immediate value
Opcode LSW: IIII IIII IIII IIII (opcode of MMOV16 MAR0, MRa, #16I)
MSW: 0111 1111 1101 00AA
LSW: IIII IIII IIII IIII (opcode of MMOV16 MAR1, MRa, #16I)
MSW: 0111 1111 1111 00AA
Description Load the auxiliary register, MAR0 or MAR1, with MRa(15:0) + 16-bit immediate value.
Refer to the pipeline section for important information regarding this instruction.
MARx = MRa(15:0) + #16I;
Flags This instruction does not modify flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline This is a single-cycle instruction. The load of MAR0 or MAR1 will occur in the EXE
phase of the pipeline. Any post increment of MAR0 or MAR1 using indirect addressing
will occur in the D2 phase of the pipeline. Therefore the following applies when loading
the auxiliary registers:
• I1 and I2
The two instructions following MMOV16 will use MAR0/MAR1 before the update
occurs. Thus these two instructions will use the old value of MAR0 or MAR1.
• I3
Loading of an auxiliary register occurs in the EXE phase while updates due to post-
increment addressing occur in the D2 phase. Thus I3 cannot use the auxiliary
register or there will be a conflict. In the case of a conflict, the update due to address-
mode post increment will win and the auxiliary register will not be updated with #_X.
• I4
Starting with the 4th instruction MAR0 or MAR1 will be the new value loaded with
MMOVI16.
; Assume MAR0 is 50, MR0 is 10, and #_X is 20
MMOV16 MAR0, MR0, #_X ; Load MAR0 with address of X (20) + MR0 (10)
<Instruction 1> ; I1 Will use the old value of MAR0 (50)
<Instruction 2> ; I2 Will use the old value of MAR0 (50)
<Instruction 3> ; I3 Cannot use MAR0
<Instruction 4> ; I4 Will use the new value of MAR0 (30)
<Instruction 5> ; I5
Table 6-16. Pipeline Activity For MMOV16 MARx, MRa , #16I
Instruction F1 F2 D1 D2 R1 R2 E W
MMOV16 MAR0, MR0, #_X MMOV16
I1 I1 MMOV16
I2 I2 I1 MMOV16
I3 I3 I2 I1 MMOV16
I4 I4 I3 I2 I1 MMOV16
I5 I5 I4 I3 I2 I1 MMOV16
MMOV1
I6 I6 I5 I4 I3 I2 I1
6
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 723
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
724 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
_RestartCount
MMOV16 @_ConversionCount, MR1 ; If branch taken, restart count
MSTOP ; end of task
See also
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 725
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MARx CLA auxiliary register MAR0 or MAR1
mem16 16-bit destination memory accessed using one of the available addressing modes
Opcode LSW: mmmm mmmm mmmm mmmm (Opcode for MMOV16 MAR0, mem16)
MSW: 0111 0110 0000 addr
LSW: mmmm mmmm mmmm mmmm (Opcode for MMOV16 MAR1, mem16)
MSW: 0111 0110 0100 addr
Description Load MAR0 or MAR1 with the 16-bit value pointed to by mem16. Refer to the pipeline
section for important information regarding this instruction.
MAR1 = [mem16];
Pipeline This is a single-cycle instruction. The load of MAR0 or MAR1 will occur in the EXE
phase of the pipeline. Any post increment of MAR0 or MAR1 using indirect addressing
will occur in the D2 phase of the pipeline. Therefore the following applies when loading
the auxiliary registers:
• I1 and I2
The two instructions following MMOV16 will use MAR0/MAR1 before the update
occurs. Thus these two instructions will use the old value of MAR0 or MAR1.
• I3
Loading of an auxiliary register occurs in the EXE phase while updates due to post-
increment addressing occur in the D2 phase. Thus I3 cannot use the auxiliary
register or there will be a conflict. In the case of a conflict, the update due to address-
mode post increment will win send the auxiliary register will not be updated with #_X.
• I4
Starting with the 4th instruction MAR0 or MAR1 will be the new value loaded with
MMOV16.
; Assume MAR0 is 50 and @_X is 20
726 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
_RestartCount
MMOV16 @_ConversionCount, MR1 ; If branch taken, restart count
MSTOP ; end of task
See also
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 727
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
mem16 16-bit destination memory accessed using one of the available addressing modes
MARx CLA auxiliary register MAR0 or MAR1
Opcode LSW: mmmm mmmm mmmm mmmm (Opcode for MMOV16 mem16, MAR0)
MSW: 0111 0110 1000 addr
LSW: mmmm mmmm mmmm mmmm (Opcode for MMOV16 mem16, MAR1)
MSW: 0111 0110 1100 addr
Description Store the contents of MAR0 or MAR1 in the 16-bit memory location pointed to by
mem16.
[mem16] = MAR0;
Example
See also
728 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
mem16 16-bit destination memory accessed using one of the available addressing modes
MRa CLA floating-point source register (MR0 to MR3)
Description Move 16-bit value from the lower 16-bits of the floating-point register (MRa(15:0)) to the
location pointed to by mem16.
[mem16] = MRa(15:0);
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 729
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
_RestartCount
MMOV16 @_ConversionCount, MR1 ; If branch taken, restart count
MSTOP ; end of task
730 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa floating-point register (MR0 to MR3)
mem32 32-bit destination memory accessed using one of the available addressing modes
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
No flags affected.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 731
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MSTF floating-point status register
mem32 32-bit destination memory
Flags This instruction does not modify flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
Example The following example illustrates the pipeline flow for the context save (of the flags and
RPC) prior to a function call. The first column in the comments shows the pipeline stages
for the MMOV32 instruction while the second column pertains to the MCCNDD
instruction.
MMOV32 @_temp, MSTF ; D2| |
MNOP ; R1|F1| MCCNDD is fetched
MNOP ; R2|F2|
MNOP ; E |D1|
MCCNDD _bar, UNC ; W |D2| old RPC written to memory,
; | | RPC updated with MPC+1
MNOP ; |R1|
MNOP ; |R2|
MNOP ; |E | execution branches to _bar
732 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem32 32-bit memory location accessed using one of the available addressing modes
CNDF optional condition.
Description If the condition is true, then move the 32-bit value referenced by mem32 to the floating-
point register indicated by MRa.
if (CNDF == TRUE) MRa = [mem32];
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
if(CNDF == UNCF)
{
NF = MRa(31);
ZF = 0;
if(MRa(30:23) == 0) { ZF = 1; NF = 0; }
}
else No flags modified;
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 733
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
734 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
CNDF optional condition.
Description If the condition is true, then move the 32-bit value in MRb to the floating-point register
indicated by MRa.
if (CNDF == TRUE) MRa = MRb;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
if(CNDF == UNCF)
{
NF = MRa(31); ZF = 0;
if(MRa(30:23) == 0) {ZF = 1; NF = 0;}
}
else No flags modified;
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 735
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
736 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MMOV32 MSTF, mem32 Move 32-Bit Value from Memory to the MSTF Register
Operands
MSTF CLA status register
mem32 32-bit source memory location
Description Move from memory to the CLA's status register MSTF. This instruction is most useful
when nesting function calls (via MCCNDD).
MSTF = [mem32];
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified Yes Yes Yes Yes Yes
Loading the status register will overwrite all flags and the RPC field. The MEALLOW field
is not affected.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 737
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMOVD32 MRa, mem32 Move 32-Bit Value from Memory with Data Copy
Operands
MRa CLA floating-point register (MR0 to MR3)
mem32 32-bit memory location accessed using one of the available addressing modes
Description Move the 32-bit value referenced by mem32 to the floating-point register indicated by
MRa.
MRa = [mem32];
[mem32+2] = [mem32];
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
NF = MRa(31);
ZF = 0;
if(MRa(30:23) == 0){ ZF = 1; NF = 0; }
738 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands This instruction is an alias for MMOVIZ and MMOVXI instructions. The second operand
is translated by the assembler such that the instruction becomes:
MMOVIZ MRa, #16FHiHex MMOVXI MRa, #16FLoHex
MRa CLA floating-point destination register (MR0 to MR3)
#32F immediate float value represented in floating-point representation
Opcode LSW: IIII IIII IIII IIII (opcode of MMOVIZ MRa, #16FHiHex)
MSW: 0111 1000 0100 00aa
LSW: IIII IIII IIII IIII (opcode of MMOVXI MRa, #16FLoHex)
MSW: 0111 1000 1000 00aa
Description Note: This instruction accepts the immediate operand only in floating-point
representation. To specify the immediate value as a hex value (IEEE 32-bit floating-
point format) use the MOVI32 MRa, #32FHex instruction.
Load the 32-bits of MRa with the immediate float value represented by #32F.
#32F is a float value represented in floating-point representation. The assembler will only
accept a float value represented in floating-point representation. That is, 3.0 can only be
represented as #3.0. #0x40400000 will result in an error.
MRa = #32F;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline Depending on #32FH, this instruction takes one or two cycles. If all of the lower 16-bits
of the IEEE 32-bit floating-point format of #32F are zeros, then the assembler will
convert MMOVF32 into only MMOVIZ instruction. If the lower 16-bits of the IEEE 32-bit
floating-point format of #32F are not zeros, then the assembler will convert MMOVF32
into MMOVIZ and MMOVXI instructions.
Example MMOVF32 MR1, #3.0 ; MR1 = 3.0 (0x40400000)
; Assembler converts this instruction as
; MMOVIZ MR1, #0x4040
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 739
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMOVI16 MARx, #16I Load the Auxiliary Register with the 16-Bit Immediate Value
Operands
MARx Auxiliary register MAR0 or MAR1
#16I 16-bit immediate value
Opcode LSW: IIII IIII IIII IIII (opcode of MMOVI16 MAR0, #16I)
MSW: 0111 1111 1100 0000
Description Load the auxiliary register, MAR0 or MAR1, with a 16-bit immediate value. Refer to the
pipeline section for important information regarding this instruction.
MARx = #16I;
Flags This instruction does not modify flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline This is a single-cycle instruction. The immediate load of MAR0 or MAR1 will occur in the
EXE phase of the pipeline. Any post increment of MAR0 or MAR1 using indirect
addressing will occur in the D2 phase of the pipeline. Therefore the following applies
when loading the auxiliary registers:
• I1 and I2
The two instructions following MMOVI16 will use MAR0/MAR1 before the update
occurs. Thus these two instructions will use the old value of MAR0 or MAR1.
• I3
Loading of an auxiliary register occurs in the EXE phase while updates due to post-
increment addressing occur in the D2 phase. Thus I3 cannot use the auxiliary
register or there will be a conflict. In the case of a conflict, the update due to address-
mode post increment will win snd the auxiliary register will not be updated with #_X.
• I4
Starting with the 4th instruction MAR0 or MAR1 will be the new value loaded with
MMOVI16.
; Assume MAR0 is 50 and #_X is 20
740 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MMOVI32 MRa, #32FHex Load the 32-Bits of a 32-Bit Floating-Point Register with the Immediate
Operands
MRa floating-point register (MR0 to MR3)
#32FHex A 32-bit immediate value that represents an IEEE 32-bit floating-point value.
This instruction is an alias for MMOVIZ and MMOVXI instructions. The second operand
is translated by the assembler such that the instruction becomes:
MMOVIZ MRa, #16FHiHex
MMOVXI MRa, #16FLoHex
Opcode LSW: IIII IIII IIII IIII (opcode of MMOVIZ MRa, #16FHiHex)
MSW: 0111 1000 0100 00aa
Description Note: This instruction only accepts a hex value as the immediate operand. To specify the
immediate value with a floating-point representation use the MMOVF32 MRa, #32F
instruction.
Load the 32-bits of MRa with the immediate 32-bit hex value represented by #32Fhex.
#32Fhex is a 32-bit immediate hex value that represents the IEEE 32-bit floating-point
value of a floating-point number. The assembler will only accept a hex immediate value.
That is, 3.0 can only be represented as #0x40400000. #3.0 will result in an error.
MRa = #32FHex;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline Depending on #32FHex, this instruction takes one or two cycles. If all of the lower 16-
bits of #32FHex are zeros, then assembler will convert MOVI32 to the MMOVIZ
instruction. If the lower 16-bits of #32FHex are not zeros, then assembler will convert
MOVI32 to a MMOVIZ and a MMOVXI instruction.
Example MOVI32 MR1, #0x40400000 ; MR1 = 0x40400000
; Assembler converts this instruction as
; MMOVIZ MR1, #0x4040
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 741
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMOVIZ MRa, #16FHi Load the Upper 16-Bits of a 32-Bit Floating-Point Register
Operands
MRa floating-point register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Load the upper 16-bits of MRa with the immediate value #16FHi and clear the low 16-
bits of MRa.
#16FHiHex is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-
bit floating-point value. The low 16-bits of the mantissa are assumed to be all 0. The
assembler will only accept a decimal or hex immediate value. That is, -1.5 can be
represented as #-1.5 or #0xBFC0.
By itself, MMOVIZ is useful for loading a floating-point register with a constant in which
the lowest 16-bits of the mantissa are 0. Some examples are 2.0 (0x40000000), 4.0
(0x40800000), 0.5 (0x3F000000), and -1.5 (0xBFC00000). If a constant requires all 32-
bits of a floating-point register to be iniitalized, then use MMOVIZ along with the
MMOVXI instruction.
MRa(31:16) = #16FHi;
MRa(15:0) = 0;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
742 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem16 16-bit source memory location
Description Move the 16-bit value referenced by mem16 to the floating-point register indicated by
MRa.
MRa(31:16) = 0;
MRa(15:0) = [mem16];
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = 0;
if (MRa(31:0)== 0) { ZF = 1; }
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 743
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMOVXI MRa, #16FLoHex Move Immediate to the Low 16-Bits of a Floating-Point Register
Operands
MRa CLA floating-point register (MR0 to MR3)
#16FLoHex A 16-bit immediate hex value that represents the lower 16-bits of an IEEE 32-bit
floating-point value. The upper 16-bits will not be modified.
Description Load the low 16-bits of MRa with the immediate value #16FLoHex. #16FLoHex
represents the lower 16-bits of an IEEE 32-bit floating-point value. The upper 16-bits of
MRa will not be modified. MMOVXI can be combined with the MMOVIZ instruction to
initialize all 32-bits of a MRa register.
MRa(15:0) = #16FLoHex;
MRa(31:16) = Unchanged;
Flags
Flag TF ZF NF LUF LVF
Modified No No No No No
744 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
MRc CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 745
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
MRb CLA floating-point source register (MR0 to MR3)
Description Multiply MRb with the floating-point value represented by the immediate operand. Store
the result of the addition in MRa.
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. #16FHi is
most useful for representing constants where the lowest 16-bits of the mantissa are 0.
Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and -1.5
(0xBFC00000). The assembler will accept either a hex or float as the immediate value.
That is, the value -1.5 can be represented as #-1.5 or #0xBFC0.
MRa = MRb * #16FHi:0;
Flags This instruction modifies the following flags in the MSTF register:.
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
746 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 747
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
Description Multiply MRb with the floating-point value represented by the immediate operand. Store
the result of the addition in MRa.
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. #16FHi is
most useful for representing constants where the lowest 16-bits of the mantissa are 0.
Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and -1.5
(0xBFC00000). The assembler will accept either a hex or float as the immediate value.
That is, the value -1.5 can be represented as #-1.5 or #0xBFC0.
MRa = MRb * #16FHi:0;
Flags This instruction modifies the following flags in the MSTF register:.
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
748 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 749
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMPYF32 MRa, MRb, MRc||MADDF32 MRd, MRe, MRf 32-Bit Floating-Point Multiply with Parallel
Add
Operands
MRa CLA floating-point destination register for MMPYF32 (MR0 to MR3)
MRa cannot be the same register as MRd
MRb CLA floating-point source register for MMPYF32 (MR0 to MR3)
MRc CLA floating-point source register for MMPYF32 (MR0 to MR3)
MRd CLA floating-point destination register for MADDF32 (MR0 to MR3)
MRd cannot be the same register as MRa
MRe CLA floating-point source register for MADDF32 (MR0 to MR3)
MRf CLA floating-point source register for MADDF32 (MR0 to MR3)
Description Multiply the contents of two floating-point registers with parallel addition of two registers.
MRa = MRb * MRc;
MRd = MRe + MRf;
Restrictions The destination register for the MMPYF32 and the MADDF32 must be unique. That is,
MRa cannot be the same register as MRd.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
750 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
See also MMACF32 MR3, MR2, MRd, MRe, MRf || MMOV32 MRa, mem32
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 751
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMPYF32 MRd, MRe, MRf ||MMOV32 MRa, mem32 32-Bit Floating-Point Multiply with Parallel Move
Operands
MRd CLA floating-point destination register for the MMPYF32 (MR0 to MR3)
MRd cannot be the same register as MRa
MRe CLA floating-point source register for the MMPYF32 (MR0 to MR3)
MRf CLA floating-point source register for the MMPYF32 (MR0 to MR3)
MRa CLA floating-point destination register for the MMOV32 (MR0 to MR3)
MRa cannot be the same register as MRd
mem32 32-bit memory location accessed using one of the available addressing modes. This
will be the source of the MMOV32.
Description Multiply the contents of two floating-point registers and load another.
MRd = MRe * MRf;
MRa = [mem32];
Restrictions The destination register for the MMPYF32 and the MMOV32 must be unique. That is,
MRa cannot be the same register as MRd.
Flags This instruction modifies the following flags in the MSTF register:.
Flag TF ZF NF LUF LVF
Modified No Yes Yes Yes Yes
752 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 753
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MMPYF32 MRd, MRe, MRf ||MMOV32 mem32, MRa 32-Bit Floating-Point Multiply with Parallel Move
Operands
MRd CLA floating-point destination register for the MMPYF32 (MR0 to MR3)
MRe CLA floating-point source register for the MMPYF32 (MR0 to MR3)
MRf CLA floating-point source register for the MMPYF32 (MR0 to MR3)
mem32 32-bit memory location accessed using one of the available addressing modes. This
will be the destination of the MMOV32.
MRa CLA floating-point source register for the MMOV32 (MR0 to MR3)
Description Multiply the contents of two floating-point registers and move from memory to register.
MRd = MRe * MRf;
[mem32] = MRa;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
754 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MMPYF32 MRa, MRb, MRc ||MSUBF32 MRd, MRe, MRf 32-Bit Floating-Point Multiply with Parallel
Subtract
Operands
MRa CLA floating-point destination register for MMPYF32 (MR0 to MR3)
MRa cannot be the same register as MRd
MRb CLA floating-point source register for MMPYF32 (MR0 to MR3)
MRc CLA floating-point source register for MMPYF32 (MR0 to MR3)
MRd CLA floating-point destination register for MSUBF32 (MR0 to MR3)
MRd cannot be the same register as MRa
MRe CLA floating-point source register for MSUBF32 (MR0 to MR3)
MRf CLA floating-point source register for MSUBF32 (MR0 to MR3)
Description Multiply the contents of two floating-point registers with parallel subtraction of two
registers.
MRa = MRb * MRc;
MRd = MRe - MRf;
Restrictions The destination register for the MMPYF32 and the MSUBF32 must be unique. That is,
MRa cannot be the same register as MRd.
Flags This instruction modifies the following flags in the MSTF register:.
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 755
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
CNDF condition tested
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
756 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 757
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MNOP No Operation
Operands
none This instruction does not have any operands
Description Do nothing. This instruction is used to fill required pipeline delay slots when other
instructions are not available to fill the slots.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
See also
758 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
MRc CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; }
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 759
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
CNDF optional condition.
Description If the specified condition is true, then the RPC field of MSTF is loaded into MPC and
fetching continues from that location. Otherwise program fetches will continue without
the return.
Please refer to the pipeline section for important information regarding this instruction.
if (CNDF == TRUE) MPC = RPC;
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
760 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Pipeline The MRCNDD instruction by itself is a single-cycle instruction. As shown in Table 6-19,
for each return 6 instruction slots are executed; three before the return instruction (d5-
d7) and three after the return instruction (d8-d10). The total number of cycles for a return
taken or not taken depends on the usage of these slots. That is, the number of cycles
depends on how many slots are filled with a MNOP as well as which slots are filled. The
effective number of cycles for a return can, therefore, range from 1 to 7 cycles. The
number of cycles for a return taken may not be the same as for a return not taken.
Referring to the following code fragment and the pipeline diagrams in Table 6-19 and
Table 6-20, the instructions before and after MRCNDD have the following properties:
;
;
<Instruction 1> ; I1 Last instruction that can affect flags for
; the MCCNDD operation
<Instruction 2> ; I2 Cannot be stop, branch, call or return
<Instruction 3> ; I3 Cannot be stop, branch, call or return
<Instruction 4> ; I4 Cannot be stop, branch, call or return
because the flag modification will occur after the D2 phase of the MRCNDD
instruction.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
• d8, d9 and d10
– The three instructions following MRCNDD are always executed irrespective of
whether the return is taken or not.
– These instructions must not be the following: MSTOP, MDEBUGSTOP,
MBCNDD, MCCNDD or MRCNDD.
762 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Example ;
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 763
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
FLAG 8 bit mask indicating which floating-point status flags to change.
VALUE 8 bit mask indicating the flag value; 0 or 1.
Description The MSETFLG instruction is used to set or clear selected floating-point status flags in
the MSTF register. The FLAG field is an 11-bit value that indicates which flags will be
changed. That is, if a FLAG bit is set to 1 it indicates that flag will be changed; all other
flags will not be modified. The bit mapping of the FLAG field is shown below:
RNDF3 reserve reserve TF reserve reserved ZF NF LUF LVF
2 d d d
9 8 7 6 5 4 3 2 1 0
The VALUE field indicates the value the flag should be set to; 0 or 1.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified Yes Yes Yes Yes Yes
Any flag can be modified by this instruction. The MEALLOW and RPC fields cannot be
modified with this instruction.
Example To make it easier and legible, the assembler accepts a FLAG=VALUE syntax for the
MSTFLG operation as shown below:
MSETFLG RNDF32=0, TF=0, NF=1; FLAG = 11000100; VALUE = 00XXX1XX;
764 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
none This instruction does not have any operands
Description The MSTOP instruction must be placed to indicate the end of each task. In addition,
placing MSTOP in unused memory locations within the CLA program RAM can be useful
for debugging and preventing run away CLA code. When MSTOP enters the D2 phase
of the pipeline, the MIRUN flag for the task is cleared and the associated interrupt is
flagged in the PIE vector table.
There are three special cases that can occur when single-stepping a task such that the
MPC reaches the MSTOP instruction.
1. If you are single-stepping or halted in "task A" and "task B" comes in before the MPC
reaches the MSTOP, then "task B" will start if you continue to step through the
MSTOP instruction. Basically if "task B" is pending before the MPC reaches MSTOP
in "task A" then there is no issue in "task B" starting and no special action is required.
2. In this case you have single-stepped or halted in "task A" and the MPC has reached
the MSTOP with no tasks pending. If "task B" comes in at this point, it will be flagged
in the MIFR register but it may or may not start if you continue to single-step through
the MSTOP instruction of "task A". It depends on exactly when the new task comes
in. To reliably start "task B" perform a soft reset and reconfigure the MIER bits. Once
this is done, you can start single-stepping "task B".
3. Case 2 can be handled slightly differently if there is control over when "task B" comes
in (for example using the IACK instruction to start the task). In this case you have
single-stepped or halted in "task A" and the MPC has reached the MSTOP with no
tasks pending. Before forcing "task B", run free to force the CLA out of the debug
state. Once this is done you can force "task B" and continue debugging.
Restrictions The MSTOP instruction cannot be placed 3 instructions before or after a MBCNDD,
MCCNDD or MRCNDD instruction.
Flags This instruction does not modify flags in the MSTF register.
Flag TF ZF NF LUF LVF
Modified No No No No No
Pipeline This is a single-cycle instruction. Table 6-21 shows the pipeline behavior of the MSTOP
instruction. The MSTOP instruction cannot be placed with 3 instructions of a MBCNDD,
MCCNDD or MRCNDD instruction.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 765
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
766 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point destination register (MR0 to MR3)
MRc CLA floating-point destination register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 767
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to R1)
MRb CLA floating-point source register (MR0 to R1)
MRc CLA floating-point source register (MR0 to R1)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
768 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
Operands
MRa CLA floating-point destination register (MR0 to R1)
#16FHi A 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit floating-
point value. The low 16-bits of the mantissa are assumed to be all 0.
MRb CLA floating-point source register (MR0 to R1)
Description Subtract MRb from the floating-point value represented by the immediate operand. Store
the result of the addition in MRa.
#16FHi is a 16-bit immediate value that represents the upper 16-bits of an IEEE 32-bit
floating-point value. The low 16-bits of the mantissa are assumed to be all 0. #16FHi is
most useful for representing constants where the lowest 16-bits of the mantissa are 0.
Some examples are 2.0 (0x40000000), 4.0 (0x40800000), 0.5 (0x3F000000), and -1.5
(0xBFC00000). The assembler will accept either a hex or float as the immediate value.
That is, the value -1.5 can be represented as #-1.5 or #0xBFC0.
MRa = #16FHi:0 - MRb;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 769
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MSUBF32 MRd, MRe, MRf ||MMOV32 MRa, mem32 32-Bit Floating-Point Subtraction with Parallel
Move
Operands
MRd CLA floating-point destination register (MR0 to MR3) for the MSUBF32 operation
MRd cannot be the same register as MRa
MRe CLA floating-point source register (MR0 to MR3) for the MSUBF32 operation
MRf CLA floating-point source register (MR0 to MR3) for the MSUBF32 operation
MRa CLA floating-point destination register (MR0 to MR3) for the MMOV32 operation
MRa cannot be the same register as MRd
mem32 32-bit memory location accessed using one of the available addressing modes. Source
for the MMOV32 operation.
Description Subtract the contents of two floating-point registers and move from memory to a floating-
point register.
MRd = MRe - MRf;
MRa = [mem32];
Restrictions The destination register for the MSUBF32 and the MMOV32 must be unique. That is,
MRa cannot be the same register as MRd.
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes Yes Yes
770 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MSUBF32 MRd, MRe, MRf ||MMOV32 mem32, MRa 32-Bit Floating-Point Subtraction with Parallel
Move
Operands
MRd CLA floating-point destination register (MR0 to MR3) for the MSUBF32 operation
MRe CLA floating-point source register (MR0 to MR3) for the MSUBF32 operation
MRf CLA floating-point source register (MR0 to MR3) for the MSUBF32 operation
mem32 32-bit destination memory location for the MMOV32 operation
MRa CLA floating-point source register (MR0 to MR3) for the MMOV32 operation
Description Subtract the contents of two floating-point registers and move from a floating-point
register to memory.
MRd = MRe - MRf;
[mem32] = MRa;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No Yes Yes
Example
See also MSUBF32 MRa, MRb, MRc
MSUBF32 MRa, #16FHi, MRb
MSUBF32 MRd, MRe, MRf || MMOV32 MRa, mem32
MMPYF32 MRa, MRb, MRc || MSUBF32 MRd, MRe, MRf
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 771
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point register (MR0 to MR3)
MRb CLA floating-point register (MR0 to MR3)
CNDF Optional condition tested based on the MSTF flags
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No No No No No
No flags affected
772 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
See also
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 773
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
CNDF condition to test based on MSTF flags
Description Test the CLA floating-point condition and if true, set the MSTF[TF] flag. If the condition is
false, clear the MSTF[TF] flag. This is useful for temporarily storing a condition for later
use.
if (CNDF == true) TF = 1;
else TF = 0;
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified Yes No No No No
TF = 0;
if (CNDF == true) TF = 1;
774 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
_Skip1:
MMOV32 MR3, @_SteadyState
MMOVXI MR2, #STEADYMASK
MOR32 MR3, MR2
MBCNDD _Skip2, NTF ; (B) if State != .01, go to Skip2
MMOV32 MR1, @_CoastState ; Always executed
MMOVXI MR2, #COASTMASK ; Always executed
MOR32 MR1, MR2 ; Always executed
MMOV32 @_CoastState, MR1 ; Execute if (B) branch not taken
MSTOP ; end of task if (B) branch not taken
_Skip2:
MMOV32 @_SteadyState, MR3 ; Executed if (B) branch taken
MSTOP
See also
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 775
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MUI16TOF32 MRa, mem16 Convert Unsigned 16-Bit Integer to 32-Bit Floating-Point Value
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem16 16-bit source memory location
Description When converting F32 to I16/UI16 data format, the MF32TOI16/UI16 operation truncates
to zero while the MF32TOI16R/UI16R operation will round to nearest (even) value.
MRa = UI16TOF32[mem16];
Example
See also MF32TOI16 MRa, MRb
MF32TOI16R MRa, MRb
MF32TOUI16 MRa, MRb
MF32TOUI16R MRa, MRb
MI16TOF32 MRa, MRb
MI16TOF32 MRa, mem16
MUI16TOF32 MRa, MRb
776 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MUI16TOF32 MRa, MRb Convert Unsigned 16-Bit Integer to 32-Bit Floating-Point Value
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
Description Convert an unsigned 16-bit integer to a 32-bit floating-point value. When converting
float32 to I16/UI16 data format, the MF32TOI16/UI16 operation truncates to zero while
the MF32TOI16R/UI16R operation will round to nearest (even) value.
MRa = UI16TOF32[MRb];
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 777
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
MUI32TOF32 MRa, mem32 Convert Unsigned 32-Bit Integer to 32-Bit Floating-Point Value
Operands
MRa CLA floating-point destination register (MR0 to MR3)
mem32 32-bit memory location accessed using one of the available addressing modes
778 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Instruction Set
MUI32TOF32 MRa, MRb Convert Unsigned 32-Bit Integer to 32-Bit Floating-Point Value
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 779
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Instruction Set www.ti.com
Operands
MRa CLA floating-point destination register (MR0 to MR3)
MRb CLA floating-point source register (MR0 to MR3)
MRc CLA floating-point source register (MR0 to MR3)
Flags This instruction modifies the following flags in the MSTF register:
Flag TF ZF NF LUF LVF
Modified No Yes Yes No No
The MSTF register flags are modified based on the integer results of the operation.
NF = MRa(31);
ZF = 0;
if(MRa(31:0) == 0) { ZF = 1; }
780 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 781
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
Complex bit access types are encoded to fit into small table cells. Table 6-24 shows the codes that are
used for access types in this section.
782 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 783
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
784 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 785
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
786 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 787
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
788 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 789
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
790 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 791
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
792 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 793
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
794 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 795
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
796 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
The IFR flag bits can also be set and cleared by the MIFRC and
MICLR registers.
If the MIFRC register is trying to set the respective bit while a new
task tries to clear it, then the MIFRC event has priority.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 797
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 8 interrupt overflow has not occurred (default)
1h (R/W) = A task 8 interrupt overflow has occurred
6 INT7 R 0h These bits, when set to "1", indicate an interrupt overflow event
occurred. Such an event occurs when the IFR bit is already set.
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 7 interrupt overflow has not occurred (default)
1h (R/W) = A task 7 interrupt overflow has occurred
798 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 6 interrupt overflow has not occurred (default)
1h (R/W) = A task 6 interrupt overflow has occurred
4 INT5 R 0h These bits, when set to "1", indicate an interrupt overflow event
occurred. Such an event occurs when the IFR bit is already set.
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 5 interrupt overflow has not occurred (default)
1h (R/W) = A task 5 interrupt overflow has occurred
3 INT4 R 0h These bits, when set to "1", indicate an interrupt overflow event
occurred. Such an event occurs when the IFR bit is already set.
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 4 interrupt overflow has not occurred (default)
1h (R/W) = A task 4 interrupt overflow has occurred
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 799
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 3 interrupt overflow has not occurred (default)
1h (R/W) = A task 3 interrupt overflow has occurred
1 INT2 R 0h These bits, when set to "1", indicate an interrupt overflow event
occurred. Such an event occurs when the IFR bit is already set.
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 2 interrupt overflow has not occurred (default)
1h (R/W) = A task 2 interrupt overflow has occurred
0 INT1 R 0h These bits, when set to "1", indicate an interrupt overflow event
occurred. Such an event occurs when the IFR bit is already set.
If the MIFR bit is being cleared by a new task on the same cycle as
a new peripheral interrupt occurs, the overflow flag will not be
affected and the respective MIFR bit will be set.
Notes: [1] The MIOVF bits are only affected by peripheral interrupt
events. Forcing an interrupt using the MIFRC or IACK operation will
not set the overflow flag even if the MIFR bit is set.
Reset type: SYSRSn
0h (R/W) = A task 1 interrupt overflow has not occurred (default)
1h (R/W) = A task 1 interrupt overflow has occurred
800 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 801
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
802 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 803
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
804 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 805
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
806 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 807
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
808 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 809
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
810 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 811
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
812 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
The MPC register address 16-bits and not 32-bits. Hence the
address range of the CLA with a 16-bit MPC is 64Kx16 words or 32K
CLA instructions.
[2] After a STOP operation, and with no other task pending, the PC
will remain pointing to the STOP operation.
Reset type: SYSRSn
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 813
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
814 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 815
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
816 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 817
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
818 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 819
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
820 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 821
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
822 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
Complex bit access types are encoded to fit into small table cells. Table 6-50 shows the codes that are
used for access types in this section.
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 823
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
824 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com CLA Registers
SPRUHX5G – August 2014 – Revised September 2019 Control Law Accelerator (CLA) 825
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
CLA Registers www.ti.com
826 Control Law Accelerator (CLA) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Chapter 7
SPRUHX5G – August 2014 – Revised September 2019
The GPIO module controls the device's digital multiplexing, which uses shared pins to maximize
application flexibility. The pins are named by their general-purpose I/O name (for example, GPIO0,
GPIO25, GPIO58). These pins can be individually selected to operate as digital I/O (also called GPIO
mode), or connected to one of several peripheral I/O signals. The input signals can be qualified to remove
unwanted noise.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 827
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Introduction www.ti.com
7.1 Introduction
Up to twelve independent peripheral signals are multiplexed on a single GPIO-enabled pin in addition to
the CPU-controlled I/O capability. Each pin output can be controlled by either a peripheral or one of the
two CPU masters (CPU1, CPU1.CLA). There are two I/O ports:
• Port A consists of GPIO0-GPIO31
• Port B consists of GPIO32-GPIO63
• Port C consists of GPIO64-GPIO95
• Port D consists of GPIO96-GPIO127
• Port E consists of GPIO128-GPIO159
• Port F consists of GPIO160-GPIO168
Figure 7-1 shows the GPIO logic for a single pin.
CPU1 CPU1.CLA
GPyGMUX1-2 GPySET GPySET
GPyMUX1-2 GPyCLEAR GPyCLEAR
GPyDIR GPyTOGGLE GPyTOGGLE
Hibernate GPyCSEL1-4 GPyDAT (W) GPyDAT (W)
Isolation Latches
Direction 00
01
10 Reserved
11 Reserved
Data
00:00
00:01 Peripheral A
00:10 Peripheral B
Data 00:11 Peripheral C
NOTE: High-speed SPI and AUXCLKIN use a different signal path that do not support inversion or
qualification. For more details on high-speed SPI pins, see Section 7.6.
The USB PHY pin muxing is not shown in this diagram. For more details on USB pins, see
Section 7.5.
828 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Configuration Overview
There are two key features to note in this diagram. The first is that the input and output paths are entirely
separate, connecting only at the pin. The second is that peripheral muxing takes place far from the pin. As
a result, it is always possible for both CPUs and CLAs to read the physical state of the pin independent of
CPU mastering and peripheral muxing. Likewise, external interrupts can be generated from peripheral
activity. All pin options such as input qualification and open-drain output are valid for all masters and
peripherals. However, the peripheral muxing, CPU muxing, and pin options can only be configured by
CPU1.
A separate configuration is required for the USB signals. See Section 7.5 for details.
NOTE: JTAG uses a different signal path that does not support inversion or qualification.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 829
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Digital General-Purpose I/O Control www.ti.com
sets the corresponding output latch and if the pin is enabled as a general purpose output (GPIO
output) the pin will also be driven either low or high. If the pin is not configured as a GPIO output then
the value will be latched, but the pin will not be driven. Only if the pin is later configured as a GPIO
output, will the latched value be driven onto the pin.
When using the GPyDAT register to change the level of an output pin, you should be cautious not to
accidentally change the level of another pin. For example, if you mean to change the output latch level
of GPIOA1 by writing to the GPADAT register bit 0 using a read-modify-write instruction, a problem can
occur if another I/O port A signal changes level between the read and the write stage of the instruction.
Following is an analysis of why this happens:
The GPyDAT registers reflect the state of the pin, not the latch. This means the register reflects the
actual pin value. However, there is a lag between when the register is written to when the new pin
value is reflected back in the register. This may pose a problem when this register is used in
subsequent program statements to alter the state of GPIO pins. An example is shown below where two
program statements attempt to drive two different GPIO pins that are currently low to a high state.
If Read-Modify-Write operations are used on the GPyDAT registers, because of the delay between the
output and the input of the first instruction (I1), the second instruction (I2) will read the old value and
write it back.
GpioDataRegs.GPADAT.bit.GPIO1 = 1; //I1 performs read-modify-
write of GPADAT GpioDataRegs.GPADAT.bit.GPIO2 = 1; //I2 also a read-modify-
write of GPADAT. //GPADAT gets the old value of GPIO1 due to the delay
The second instruction will wait for the first to finish its write due to the write-followed-by-read
protection on this peripheral frame. There will be some lag, however, between the write of (I1) and the
GPyDAT bit reflecting the new value (1) on the pin. During this lag, the second instruction will read the
old value of GPIO1 (0) and write it back along with the new value of GPIO2 (1). Therefore, GPIO1 pin
stays low.
One solution is to put some NOPs between instructions. A better solution is to use the
GPySET/GPyCLEAR/GPyTOGGLE registers instead of the GPyDAT registers. These registers always
read back a 0 and writes of 0 have no effect. Only bits that need to be changed can be specified
without disturbing any other bit(s) that are currently in the process of changing.
• GPySET Registers
The set registers are used to drive specified GPIO pins high without disturbing other pins. Each I/O
port has one set register and each bit corresponds to one GPIO pin. The set registers always read
back 0. If the corresponding pin is configured as an output, then writing a 1 to that bit in the set register
will set the output latch high and the corresponding pin will be driven high. If the pin is not configured
as a GPIO output, then the value will be latched but the pin will not be driven. Only if the pin is later
configured as a GPIO output will the latched value be driven onto the pin. Writing a 0 to any bit in the
set registers has no effect.
• GPyCLEAR Registers
The clear registers are used to drive specified GPIO pins low without disturbing other pins. Each I/O
port has one clear register. The clear registers always read back 0. If the corresponding pin is
configured as a general purpose output, then writing a 1 to the corresponding bit in the clear register
will clear the output latch and the pin will be driven low. If the pin is not configured as a GPIO output,
then the value will be latched but the pin will not be driven. Only if the pin is later configured as a GPIO
output will the latched value be driven onto the pin. Writing a 0 to any bit in the clear registers has no
effect.
• GPyTOGGLE Registers
The toggle registers are used to drive specified GPIO pins to the opposite level without disturbing other
pins. Each I/O port has one toggle register. The toggle registers always read back 0. If the
corresponding pin is configured as an output, then writing a 1 to that bit in the toggle register flips the
output latch and pulls the corresponding pin in the opposite direction. That is, if the output pin is driven
low, then writing a 1 to the corresponding bit in the toggle register will pull the pin high. Likewise, if the
output pin is high, then writing a 1 to the corresponding bit in the toggle register will pull the pin low. If
the pin is not configured as a GPIO output, then the value will be latched but the pin will not be driven.
Only if the pin is later configured as a GPIO output will the latched value be driven onto the pin. Writing
a 0 to any bit in the toggle registers has no effect.
830 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Input Qualification
NOTE: Using input synchronization when the peripheral itself performs the synchronization may
cause unexpected results. The user should ensure that the GPIO pin is configured for
asynchronous in this case.
GPxCTRL Reg
GPxQSEL1/2
SYSCLKOUT
Number of Samples
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 831
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Input Qualification www.ti.com
To qualify the signal, the input signal is sampled at a regular period. The sampling period is specified by
the user and determines the time duration between samples, or how often the signal will be sampled,
relative to the CPU clock (SYSCLKOUT).
The sampling period is specified by the qualification period (QUALPRDn) bits in the GPxCTRL register.
The sampling period is configurable in groups of 8 input signals. For example, GPIO0 to GPIO7 use
GPACTRL[QUALPRD0] setting and GPIO8 to GPIO15 use GPACTRL[QUALPRD1]. Table 7-1 and
Table 7-2 show the relationship between the sampling period or sampling frequency and the
GPxCTRL[QUALPRDn] setting.
Sampling Period
If GPxCTRL[QUALPRDn] = 0 1 × TSYSCLKOUT
If GPxCTRL[QUALPRDn] ≠ 0 2 × GPxCTRL[QUALPRDn] × TSYSCLKOUT
Where TSYSCLKOUT is the period in time of SYSCLKOUT
Sampling Frequency
If GPxCTRL[QUALPRDn] = 0 fSYSCLKOUT
If GPxCTRL[QUALPRDn] ≠ 0 fSYSCLKOUT × 1 ÷ (2 × GPxCTRL[QUALPRDn])
Where fSYSCLKOUT is the frequency of SYSCLKOUT
From these equations, the minimum and maximum time between samples can be calculated for a given
SYSCLKOUT frequency:
Number of samples:
The number of times the signal is sampled is either three samples or six samples as specified in the
qualification selection (GPAQSEL1, GPAQSEL2, GPBQSEL1, and GPBQSEL2) registers. When three or
six consecutive cycles are the same, then the input change will be passed through to the MCU.
Total Sampling Window Width:
The sampling window is the time during which the input signal will be sampled as shown in Figure 7-3. By
using the equation for the sampling period along with the number of samples to be taken, the total width of
the window can be determined.
For the input qualifier to detect a change in the input, the level of the signal must be stable for the duration
of the sampling window width or longer.
The number of sampling periods within the window is always one less than the number of samples taken.
For a three-sample window, the sampling window width is two sampling periods wide where the sampling
period is defined in Table 7-1. Likewise, for a six-sample window, the sampling window width is five
sampling periods wide. Table 7-3 and Table 7-4 show the calculations that can be used to determine the
total sampling window width based on GPxCTRL[QUALPRDn] and the number of samples taken.
832 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com Input Qualification
NOTE: The external signal change is asynchronous with respect to both the sampling period and
SYSCLKOUT. Due to the asynchronous nature of the external signal, the input should be
held stable for a time greater than the sampling window width to make sure the logic detects
a change in the signal. The extra time required can be up to an additional sampling period +
TSYSCLKOUT.
The required duration for an input signal to be stable for the qualification logic to detect a
change is described in the device-specific data manual.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 833
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
USB Signals www.ti.com
1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 1 1 1 1 1 1
SYSCLKOUT
QUALPRD = 1
(SYSCLKOUT/2)
(D)
Output From
Qualifier
A. This glitch will be ignored by the input qualifier. The QUALPRD bit field specifies the qualification sampling period. It can vary from 00 to
0xFF. If QUALPRD = 00, then the sampling period is 1 SYSCLKOUT cycle. For any other value “n”, the qualification sampling period in 2n
SYSCLKOUT cycles (i.e., at every 2n SYSCLKOUT cycles, the GPIO pin will be sampled).
B. The qualification period selected via the GPxCTRL register applies to groups of 8 GPIO pins.
C. The qualification block can take either three or six samples. The GPxQSELn Register selects which sample mode is used.
D. In the example shown, for the qualifier to detect the change, the input should be stable for 10 SYSCLKOUT cycles or greater. In other words,
the inputs should be stable for (5 x QUALPRD x 2) SYSCLKOUT cycles. That would ensure 5 sampling periods for detection to occur. Since
external signals are driven asynchronously, an 13-SYSCLKOUT-wide pulse ensures reliable recognition.
834 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO and Peripheral Muxing
(1)
I = Input, O = Output, OD = Open Drain
(2)
GPIO Index settings of 9, 10, 11, 13, and 14 are reserved.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 835
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO and Peripheral Muxing www.ti.com
(3)
High-Speed SPI-enabled GPIO mux option. This pin mux option is required when using the SPI in High-Speed Mode
(HS_MODE = 1 in SPICCR). This mux option is still available when not using the SPI in High-Speed Mode (HS_MODE = 0 in
SPICCR).
836 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO and Peripheral Muxing
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 837
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO and Peripheral Muxing www.ti.com
838 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO and Peripheral Muxing
For example, the multiplexing for the GPIO 6 pin is controlled by writing toGPAGMUX[13:12] and
GPAMUX[13:12]. By writing to these bits, GPIO 6 can be configured as either ageneral-purpose digital I/O
or one of four different peripheral functions. The options are shown inTable 7-8.
The devices have different multiplexing schemes. If a peripheral is not available on a particular device,
that mux selection is reserved on that device and should not be used.
NOTE: If you select a reserved GPIO mux configuration that is not mapped to either a peripheral or
GPIO mode, the state of the pin will be undefined and the pin may be driven.
Unimplemented configurations are for future expansion and must not be selected. In the
device mux table (see datasheet), these options are indicated as Reserved or left blank.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 839
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Internal Pullup Configuration Requirements www.ti.com
Some peripherals can be assigned to more than one pin via the mux registers. For example,
OUTPUTXBAR1 can be assigned to GPIOs 2, 24, 34, or 58, depending on individual system
requirements. An example of this is shown in Table 7-9.
If none, or more then one, of the GPIO pins are configured as peripheral input pins, then that GPIO will be
set to a hard-wired default value.
840 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 841
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
842 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 843
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
Complex bit access types are encoded to fit into small table cells. Table 7-13 shows the codes that are
used for access types in this section.
844 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 845
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
846 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 847
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
848 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 849
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
850 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 851
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
852 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 853
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
854 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 855
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
856 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 857
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
858 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 859
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
860 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 861
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
862 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 863
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
864 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 865
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
866 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 867
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
868 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 869
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
870 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 871
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
872 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 873
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
874 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 875
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
876 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 877
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
878 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 879
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
880 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 881
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
882 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 883
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
884 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 885
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
886 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 887
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
888 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 889
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED GPIO43 GPIO42 RESERVED RESERVED
R/W-0h R/W-0h
7 6 5 4 3 2 1 0
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
890 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 891
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
892 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 893
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
894 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 895
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
896 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 897
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
898 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 899
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
900 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 901
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
902 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 903
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
904 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 905
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
906 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 907
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
908 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 909
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
910 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 911
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
912 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 913
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
914 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 915
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
916 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 917
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
918 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 919
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
920 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 921
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
922 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 923
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
924 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 925
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
926 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 927
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
928 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 929
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
930 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 931
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
932 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 933
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
934 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 935
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
936 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 937
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
938 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 939
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
940 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 941
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
942 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 943
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
944 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 945
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
946 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 947
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
948 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 949
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
950 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 951
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
952 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 953
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
954 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 955
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
956 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 957
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
958 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 959
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
960 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 961
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
962 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 963
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
964 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 965
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
966 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 967
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
968 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 969
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
970 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 971
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
972 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 973
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
974 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 975
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
976 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 977
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
978 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 979
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
980 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 981
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
982 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 983
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
984 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 985
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
986 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 987
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED GPIO168
R/W-0h
15 14 13 12 11 10 9 8
GPIO167 GPIO166 GPIO165 GPIO164
R/W-0h R/W-0h R/W-0h R/W-0h
7 6 5 4 3 2 1 0
GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h
988 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 989
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED GPIO168
R/W-0h
15 14 13 12 11 10 9 8
GPIO167 GPIO166 GPIO165 GPIO164
R/W-0h R/W-0h R/W-0h R/W-0h
7 6 5 4 3 2 1 0
GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h
990 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 991
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
992 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 993
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-1h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-1h R/W-1h R/W-1h R/W-1h R/W-1h R/W-1h R/W-1h R/W-1h
994 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 995
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
996 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 997
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
998 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 999
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED GPIO168
R/W-0h
15 14 13 12 11 10 9 8
GPIO167 GPIO166 GPIO165 GPIO164
R/W-0h R/W-0h R/W-0h R/W-0h
7 6 5 4 3 2 1 0
GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h
1000 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1001
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
RESERVED RESERVED RESERVED GPIO168
R/W-0h
1002 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1003
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1004 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/WOnce-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/WOnce-0h R/WOnce-0h R/WOnce-0h R/WOnce-0h R/WOnce-0h R/WOnce-0h R/WOnce-0h R/WOnce-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1005
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1006 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
Complex bit access types are encoded to fit into small table cells. Table 7-113 shows the codes that are
used for access types in this section.
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1007
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1008 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1009
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1010 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1011
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1012 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1013
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1014 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1015
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1016 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1017
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1018 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1020 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1021
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1022 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1023
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1024 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1025
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1026 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1027
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1028 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1029
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1030 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1031
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1032 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1033
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1034 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1035
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1036 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1037
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1038 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1039
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1040 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1041
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1042 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1043
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1044 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1045
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1046 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1047
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1048 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1049
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1050 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1051
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1052 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1053
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1054 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
23 22 21 20 19 18 17 16
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
15 14 13 12 11 10 9 8
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GPIO168
R/W-0h
7 6 5 4 3 2 1 0
GPIO167 GPIO166 GPIO165 GPIO164 GPIO163 GPIO162 GPIO161 GPIO160
R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h R/W-0h
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1055
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1056 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
www.ti.com GPIO Registers
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1057
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1059
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
SPRUHX5G – August 2014 – Revised September 2019 General-Purpose Input/Output (GPIO) 1061
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
GPIO Registers www.ti.com
1062 General-Purpose Input/Output (GPIO) SPRUHX5G – August 2014 – Revised September 2019
Submit Documentation Feedback
Copyright © 2014–2019, Texas Instruments Incorporated
Chapter 8
SPRUHX5G – August 2014 – Revised September 2019
Crossbar (X-BAR)
The crossbars (referred to as X-BAR throughout this document) provide flexibility to connect device inputs,
outputs, and internal resources in a variety of configurations.
The device contains a total of four X-BARs: the Input X-BAR, the Output X-BAR, the CLB X-BAR and the
ePWM X-BAR. Each of the X-BARs is named according to where they take signals. For example, the
Input X-BAR brings external signals “in” to the device. The Output X-BAR takes internal signals “out” of
the device to a GPIO. The CLB X-BAR and ePWM X-BAR take signals to the CLB and ePWM modules
respectively.
You can read more about each of these X-BARs in the following sections.
TZ1,TRIP1
XINT5 TZ2,TRIP2
XINT4 TZ3,TRIP3
CPU PIE
XINT3
CLA XINT2 TRIP4
XINT1 TRIP5
TRIP7 ePWM
ePWM TRIP8 Modules
X-BAR TRIP9
TRIP10
TRIP11
TRIP12
TRIP6
ADC ADCEXTSOC
EXTSYNCIN1 ePWM and eCAP
EXTSYNCIN2 Sync Chain
Output X-BAR
0.0
0.1 0
0.2
0.3
TRIPxMUXENABLE
(32 bits)
TRIPxMUX0TO15CFG.MUX0
1.0
1.1 1
1.2
1.3
TRIPxMUX0TO15CFG.MUX1
31.0
31.1 TRIPOUTINV
31 (1 bit)
31.2
31.3
TRIPxMUX16TO31CFG.MUX31
First, determine the signal(s) which should be passed to the ePWM by referencing Table 8-2. You may
select up to one signal per mux (32 total muxes) for each TRIPx output. Select the inputs to each mux via
the TRIPxMUX0TO15CFG and TRIPxMUX16TO31CFG registers. In order to pass any signal through to
the ePWM, you must also enable the mux in the TRIPxMUXENABLE register. All muxes which are
enabled will be logically OR’d before being passed on to the respective TRIPx signal on the ePWM. You
may also optionally invert the signal via the TRIPOUTINV register.
0.0
0.1 0
0.2
0.3 AUXSIGxMUXENABLE
(32 bits)
AUXSIGxMUX0TO15CFG.MUX0
1.0
1.1 1
1.2
1.3
AUXSIGxMUX0TO15CFG.MUX1
31.0
31.1 AUXIGOUTINV
31 (1 bits)
31.2
31.3
AUXSIGxMUX16TO31CFG.MUX31
First, determine the signal(s) which should be passed to the CLB. You may select up to one signal per
mux (31 total muxes) for each AUXSIGx output. Select the inputs to each mux via the
AUXSIGxMUX0TO15CFG and AUXSIGxMUX16TO31CFG registers. In order to pass any signal through
to the CLB, you must also enable the mux in the AUXSIGxMUXENABLE register. All muxes which are
enabled will be logically OR’d before being passed on to the respective AUXSIGx signal on the CLB. You
may also optionally invert the signal via the AUXSIGOUTINV register.
0.0
0.1 0
0.2
0.3
OUTPUTxMUXENABLE
(32 bits)
OUTPUTxMUX0TO15CFG.MUX0
1.0
1.1 1
1.2
1.3
OUTPUTx
OUTPUTxMUX0TO15CFG.MUX1
OUTPUTLATCHENABLE
31.0
D Q
31.1 31
31.2 OLAT OUTPUTINV
31.3
Q
First, determine the signal(s) which should be passed to the GPIO by referencing Table 8-4. You may
select up to one signal per mux (32 total muxes) for each OUTPUTXBARx output. Select the inputs to
each mux via the OUTPUTxMUX0TO15CFG and OUTPUTxMUX16TO31CFG registers.
In order to pass any signal through to the GPIO, you must also enable the mux in the
OUTPUTxMUXENABLE register. All muxes which are enabled will be logically OR’d before being passed
on to the respective OUTPUTx signal on the GPIO module. You may also optionally invert the signal via
the OUTPUTINV register. The signal will only be seen on the GPIO if the proper OUTPUTx muxing
options are selected via the GpioCtrlRegs.GPxMUX and GpioCtrlRegs.GPxGMUX registers.
CMPSSx
CTRIPH
CTRIPL
(ePWM X-BAR only)
eCAPx ECAPxOUT
EVT1
EVT2
ADCx EVT3 TRIP4
EVT4 TRIP5
TRIP7 All
INPUT1 ePWM TRIP8
ePWM
INPUT2 X-BAR TRIP9
TRIP10
Modules
INPUT3
INPUT4 TRIP11
Input X-Bar TRIP12
INPUT5
INPUT6
OTHER DESTINATIONS
(see Input X-BAR)
X-BAR Flags
FLT1.COMPH (shared)
FLT1.COMPL
SDFMx
FLT4.COMPH
FLT4.COMPL
Complex bit access types are encoded to fit into small table cells. Table 8-7 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 8-15 shows the codes that are
used for access types in this section.
Complex bit access types are encoded to fit into small table cells. Table 8-32 shows the codes that are
used for access types in this section.
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT1 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT1 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT1 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT1 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT1 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT1 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT1 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT1 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT1 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT1 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT1 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT1 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT1 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT1 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT1 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT1 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT1 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT1 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT1 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT1 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT1 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT1 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT1 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT1 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT1 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT1 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT2 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT2 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT2 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT2 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT2 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT2 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT2 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT2 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT2 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT2 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT2 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT2 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT2 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT2 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT2 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT2 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT2 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT2 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT2 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT2 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT2 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT2 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT2 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT2 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT2 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT2 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT3 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT3 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT3 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT3 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT3 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT3 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT3 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT3 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT3 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT3 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT3 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT3 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT3 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT3 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT3 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT3 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT3 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT3 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT3 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT3 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT3 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT3 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT3 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT3 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT3 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT3 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT4 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT4 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT4 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT4 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT4 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT4 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT4 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT4 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT4 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT4 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT4 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT4 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT4 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT4 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT4 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT4 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT4 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT4 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT4 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT4 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT4 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT4 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT4 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT4 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT4 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT4 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT5 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT5 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT5 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT5 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT5 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT5 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT5 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT5 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT5 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT5 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT5 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT5 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT5 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT5 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT5 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT5 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT5 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT5 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT5 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT5 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT5 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT5 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT5 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT5 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT5 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT5 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT6 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT6 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT6 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT6 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT6 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT6 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT6 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT6 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT6 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT6 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT6 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT6 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT6 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT6 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT6 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT6 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT6 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT6 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT6 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT6 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT6 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT6 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT6 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT6 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT6 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT6 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT7 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT7 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT7 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT7 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT7 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT7 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT7 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT7 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT7 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT7 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT7 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT7 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT7 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT7 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT7 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT7 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT7 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT7 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT7 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT7 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT7 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT7 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT7 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT7 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT7 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT7 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for OUTPUT8 Mux14:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for OUTPUT8 Mux13:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for OUTPUT8 Mux12:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for OUTPUT8 Mux10:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for OUTPUT8 Mux9:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for OUTPUT8 Mux8:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for OUTPUT8 Mux7:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for OUTPUT8 Mux6:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for OUTPUT8 Mux4:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for OUTPUT8 Mux3:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for OUTPUT8 Mux2:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for OUTPUT8 Mux1:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for OUTPUT8 Mux0:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for OUTPUT8 Mux30:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for OUTPUT8 Mux29:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for OUTPUT8 Mux28:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for OUTPUT8 Mux26:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for OUTPUT8 Mux25:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for OUTPUT8 Mux24:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for OUTPUT8 Mux23:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for OUTPUT8 Mux22:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for OUTPUT8 Mux20:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for OUTPUT8 Mux19:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for OUTPUT8 Mux18:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for OUTPUT8 Mux17:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for OUTPUT8 Mux16:
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT4 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive OUTPUT8 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
6 OUTPUT7 R 0h Records the OUTPUT7 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
5 OUTPUT6 R 0h Records the OUTPUT6 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
3 OUTPUT4 R 0h Records the OUTPUT4 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
2 OUTPUT3 R 0h Records the OUTPUT3 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
1 OUTPUT2 R 0h Records the OUTPUT2 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
0 OUTPUT1 R 0h Records the OUTPUT1 of OUTPUT-XBAR.
Refer to the Output X-BAR section of this chapter for more details.
Note:
[1] setting of this bit has priority over clear by software
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
6 OUTPUT7 R-0/W1S 0h Clears the Output-Latch for OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 OUTPUT6 R-0/W1S 0h Clears the Output-Latch for OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 OUTPUT5 R-0/W1S 0h Clears the Output-Latch for OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 OUTPUT3 R-0/W1S 0h Clears the Output-Latch for OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 OUTPUT2 R-0/W1S 0h Clears the Output-Latch for OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 OUTPUT1 R-0/W1S 0h Clears the Output-Latch for OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
6 OUTPUT7 R-0/W1S 0h Sets the Output-Latch for OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 OUTPUT6 R-0/W1S 0h Sets the Output-Latch for OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 OUTPUT5 R-0/W1S 0h Sets the Output-Latch for OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 OUTPUT3 R-0/W1S 0h Sets the Output-Latch for OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 OUTPUT2 R-0/W1S 0h Sets the Output-Latch for OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 OUTPUT1 R-0/W1S 0h Sets the Output-Latch for OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
6 OUTPUT7 R/W 0h Selects the output latch to drive OUTPUT7 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 OUTPUT6 R/W 0h Selects the output latch to drive OUTPUT6 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 OUTPUT5 R/W 0h Selects the output latch to drive OUTPUT5 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 OUTPUT3 R/W 0h Selects the output latch to drive OUTPUT3 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 OUTPUT2 R/W 0h Selects the output latch to drive OUTPUT2 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 OUTPUT1 R/W 0h Selects the output latch to drive OUTPUT1 for OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
6 OUTPUT7 R/W 0h Selects polarity for OUTPUT7 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 OUTPUT6 R/W 0h Selects polarity for OUTPUT6 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 OUTPUT5 R/W 0h Selects polarity for OUTPUT5 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 OUTPUT3 R/W 0h Selects polarity for OUTPUT3 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 OUTPUT2 R/W 0h Selects polarity for OUTPUT2 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 OUTPUT1 R/W 0h Selects polarity for OUTPUT1 of OUTPUT-XBAR
Refer to the Output X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Note:
[1] LOCK mechanism only apples to writes. Reads are never
blocked.
Reset type: CPU1.SYSRSn
Complex bit access types are encoded to fit into small table cells. Table 8-64 shows the codes that are
used for access types in this section.
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP4 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP5 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP7 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP8 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP9 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP10 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP11 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX14 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux14:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX13 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux13:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX12 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux12:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX10 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux10:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX9 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux9:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX8 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux8:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX7 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux7:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX6 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux6:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX4 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux4:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX3 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux3:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX2 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux2:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX1 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux1:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX0 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux0:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29-28 MUX30 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux30:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
27-26 MUX29 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux29:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25-24 MUX28 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux28:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21-20 MUX26 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux26:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19-18 MUX25 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux25:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17-16 MUX24 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux24:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15-14 MUX23 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux23:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
13-12 MUX22 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux22:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9-8 MUX20 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux20:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7-6 MUX19 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux19:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5-4 MUX18 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux18:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3-2 MUX17 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux17:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1-0 MUX16 R/W 0h Select Bits for EPWM-XBAR TRIP12 Mux16:
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of Mux0 to drive TRIP4 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive TRIP5 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive TRIP7 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive TRIP8 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive TRIP9 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
16 MUX16 R/W 0h Selects the output of Mux16 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
15 MUX15 R/W 0h Selects the output of Mux15 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
14 MUX14 R/W 0h Selects the output of Mux14 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
12 MUX12 R/W 0h Selects the output of Mux12 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
11 MUX11 R/W 0h Selects the output of Mux11 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
10 MUX10 R/W 0h Selects the output of Mux10 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
9 MUX9 R/W 0h Selects the output of Mux9 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
8 MUX8 R/W 0h Selects the output of Mux8 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
7 MUX7 R/W 0h Selects the output of Mux7 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
5 MUX5 R/W 0h Selects the output of Mux5 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
4 MUX4 R/W 0h Selects the output of Mux4 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
3 MUX3 R/W 0h Selects the output of Mux3 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
2 MUX2 R/W 0h Selects the output of Mux2 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
1 MUX1 R/W 0h Selects the output of Mux1 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
0 MUX0 R/W 0h Selects the output of mux0 to drive TRIP10 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
30 MUX30 R/W 0h Selects the output of Mux30 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
29 MUX29 R/W 0h Selects the output of Mux29 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
28 MUX28 R/W 0h Selects the output of Mux28 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
26 MUX26 R/W 0h Selects the output of Mux26 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
25 MUX25 R/W 0h Selects the output of Mux25 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
24 MUX24 R/W 0h Selects the output of Mux24 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
23 MUX23 R/W 0h Selects the output of Mux23 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
22 MUX22 R/W 0h Selects the output of Mux22 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
21 MUX21 R/W 0h Selects the output of Mux21 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
19 MUX19 R/W 0h Selects the output of Mux19 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
18 MUX18 R/W 0h Selects the output of Mux18 to drive TRIP11 of EPWM-XBAR
Refer to the EPWM X-BAR section of this chapter for more details.
Reset type: CPU1.SYSRSn
17 MUX17 R/W 0h Selects the output of Mux17 to drive TRIP11 of EPWM-XBAR