SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
The ESC has one interrupt line that can be connected to the local host (CPU1 or CM) that is called PDI IRQ from the ESC. Besides this, there are other interrupt causes generated within the ESCSS. These are aggregated to a total of 4 interrupt lines that are connected to the local host core.
Table 31-8 summarizes these exceptions and their mapping. There are 4 interrupt lines provided for ESCSS which are: ECATSS_Intr, RESET_OUT_Intr, SYNC0_Intr and SYNC1_Intr. Each of these causes have an independent set of mask/clear/set controls and raw/masked interrupt status flags. This allows independent cause servicing on the exception event with flexibility to mask or service the desired set of causes. All these interrupts are mapped onto NVIC on CM and PIE on CPU1. Refer to the System Control and Interrupts chapter for details on the interrupt numbers.
In the event that the same exception is available to the multiple bus master cores of the local host CPU, the application software is expected to make sure that clearing of the RIS is a software synchronized event between those masters and there is no stale exceptions pending for one master while the other clears the RIS. In other words, there is no separate exception cause (RIS/MIS) copy per master but are common interrupt registers for the local host across masters.
Source | Description | Master | ||||
---|---|---|---|---|---|---|
CPU1 | CLA | CPU1 DMA | CM | µDMA | ||
EtherCAT IRQ | AL Event Request of the ESC | ECATSS_ intr |
ECATSS_ intr |
Not Available | ECATSS_ intr |
Not Available |
PDI Interface Timeout Error | PDI Interface WatchDog timeout error | ECATSS_ intr |
ECATSS_ intr |
Not Available | ECATSS_ intr |
Not Available |
µDMA Done(1) | This event indicates to CM or CPU1 that the µDMA transfer by earlier event is over | ECATSS_ intr |
Not Available | Not Available | ECATSS_ intr |
Not Available |
EtherCAT RESET_ OUT Event |
RESET_OUT can be programmed as interrupt to the CPU to either complete the reset sequence with required pre-steps if an or acknowledge the reset request in some other way. Given the high priority nature of the signal independent interrupt line is allocated | RESET_ OUT_Intr |
RESET_ OUT_Intr |
Not Available | RESET_ OUT_Intr |
Not Available |
SYNC0 Event | Precise time event 2, can be used to start routine SYNC1_Intron cores or data transfer using DMA. Given the precise time and priority of these interrupts a separate interrupt line is dedicated. | SYNC0_ Intr |
SYNC0_ Intr |
SYNC_ DMAReq |
SYNC0_ Intr |
SYNC_ DMAReq |
SYNC1 Event | Precise time event 1, can be used to start routine on cores or data transfer using DMA. Given the precise time and priority of these interrupts a separate interrupt line is dedicated. | SYNC1_ Intr |
SYNC1_ Intr |
SYNC_ DMAReq |
SYNC1_ Intr |
SYNC_ DMAReq |