SPRSP14E may 2019 – june 2023 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
PRODUCTION DATA
Refer to the PDF data sheet for device specific package drawings
The CM subsystem has the capability of detecting all serious errors that could occur in the entire system (including all the subsystems), and informing the main CPU core about the errors. An NMI exception to the Cortex-M4 CPU on the CM subsystem will be generated only when at least one or more of the below NMI error sources become active. For more details on each of the sources, see the CM Subsystem NMI Sources section of the TMS320F2838x Real-Time Microcontrollers Technical Reference Manual.
All these NMI sources are "OR-ed" to generate the NMI input to the Cortex-M4 NVIC. The NMI triggers a CMNMIWD counter running at the CM subsystem frequency. The CMNMIWD counter will stop counting only if all the pending NMIs are acknowledged by clearing the pending flags in the CMNMIFLG register. If the pending NMI is not acknowledged before the CMNMIWD counter reaches the value programmed in the NMI Watchdog period register (CMNMIWDPRD), an NMIWD reset is generated to the CM subsystem, which will reset the entire device.
Figure 8-12 shows different sources that can trigger an NMI to the Cortex-M4 on the CM subsystem and the registers associated with them.
All the NMI sources shown in Figure 8-12 are enabled by default on reset. CMNMICFG.NMIE is disabled on reset and needs to be enabled by setting it to 1.
For more information about the CMNMI, see the CM Subsystem Non-Maskable Interrupt (CMNMI) Module section of the TMS320F2838x Real-Time Microcontrollers Technical Reference Manual.