SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
Figure 17-2 shows the relationship between the device INTCs and external interrupts.
Table 17-1 describes the signals that can be used by external devices to generate interrupts to the device INTCs.
Device Pin | I/O(1) | Description |
---|---|---|
sys_nirq1 | I | External devices can use these pins to generate a system wake-up interrupt event to any device INTC. The user must take care to configure the corresponding IRQ_CROSSBAR properly (via Control Module). |
sys_nirq2 | I | |
nmin_dsp | I | External device can use this pin to generate a non-maskable interrupt (NMI) event to the following device processors: |
- IPU1_C0, IPU1_C1. Upon enable (via Control Module), the NMI is routed directly to the NMI input of Cortex M4 core. Note that NMI can be enabled separately for IPU1_C0 and IPU1_C1. | ||
- IPU2_C0, IPU2_C1. Upon enable (via Control Module), the NMI is routed directly to the NMI input of Cortex M4 core. Note that NMI can be enabled separately for IPU2_C0 and IPU2_C1. | ||
- DSP1, DSP2. Upon enable (via Control Module), the NMI is routed directly to the NMI input of C66x CPU. | ||
The signal from the nmin_dsp pin can also be mapped to the MPU_INTC (MPU_IRQ_133 input) but it would be treated by Cortex-A15 as a general interrupt and not as a non-maskable interrupt. The Cortex-A15 processor does not provide NMI input. | ||
The Control Module registers CTRL_CORE_NMI_DESTINATION_1 and CTRL_CORE_NMI_DESTINATION_2 are used to route the NMI signal to the corresponding device processor subsystems as follows:
|
External devices can also use the GPIO modules to generate an interrupt to the device INTCs. For more information, see Chapter 27, General-Purpose Interface.