How can I ensure my CAN ISR completes processing quickly enough to avoid the interrupt WDT panic?
@Middleware & OS I'm using an MCP25625 CAN controller with an ESP32-S3 and esp-idf with RTOS. I'm encountering an interrupt WDT panic within my CAN interrupt service routine (ISR).
I know ISRs typically involve checking the interrupt cause, clearing the flag, and potentially deferring complex processing to a separate task using queues or semaphores. But in this case, I'm realizing that reading the MCP25625 registers within the ISR context might be causing the WDT panic.
How can I ensure my CAN ISR completes processing quickly enough to avoid the interrupt WDT panic? Are there specific techniques for handling CAN interrupts efficiently within the ESP-IDF RTOS environment?
Greetings Devs,l need your Kind Opinion(s)
I know ISRs typically involve checking the interrupt cause, clearing the flag, and potentially deferring complex processing to a separate task using queues or semaphores. But in this case, I'm realizing that reading the MCP25625 registers within the ISR context might be causing the WDT panic.
How can I ensure my CAN ISR completes processing quickly enough to avoid the interrupt WDT panic? Are there specific techniques for handling CAN interrupts efficiently within the ESP-IDF RTOS environment?
Greetings Devs,l need your Kind Opinion(s)
