SPRUJ17I March 2022 – August 2025 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1
An Interrupt can be generated on capture events (CEVT1-CEVT4, CNTOVF) or APWM events (CTR = PRD, CTR = CMP). See Interrupts in PRU-ICSS eCAP Module.
A counter overflow event (FFFF FFFFh->0000 0000h) is also provided as an interrupt source (CNTOVF).
The capture events are edge and sequencer qualified (that is, ordered in time) by the polarity select and Mod4 gating, respectively.
One of these events can be selected as the interrupt source of the PRU-ICSS eCAP module "pr1_ecap_intr_req" aggregated IRQ mapped on the PRU-ICSS1_IRQ_15 input line of the local PRU-ICSS1_INTC. See also Table 7-59.
Seven interrupt events (CEVT1, CEVT2, CEVT3, CEVT4, CNTOVF, CTR = PRD, CTR = CMP) can be generated. The interrupt enable register (PRU-ICSS_ECAP_ECEINT) is used to enable/disable individual interrupt event sources. The interrupt flag register (PRU-ICSS_ECAP_ECFLG) indicates if any interrupt event has been latched and contains the global interrupt flag bit (INT). An interrupt pulse is generated to the PRU-ICSS1_INTC local interrupt controller only if any of the interrupt events are enabled, the flag bit is 1, and the INT flag bit is 0. The interrupt service routine must clear the global interrupt flag bit and the serviced event via the interrupt clear register (PRU-ICSS_ECAP_ECCLR) before any other interrupt pulses are generated. You can force an interrupt event via the interrupt force register (PRU-ICSS_ECAP_ECFRC). This is useful for test purposes.