Why the RTOS Path From ISR to Task Must Be Designed
In RTOS devices, many peripheral issues are not about whether an interrupt entered. They are about whether the task handled it correctly and soon enough after the ISR.
Common symptoms include:
- ISR logs appear, but the business task receives no data
- queues fill up when interrupt rate increases
- ISR does too much work and system response gets worse
- a high-priority task is woken but runs late
- normal APIs are called from ISR and cause assertions or deadlocks
- one notification is sent while the hardware FIFO already contains many events
Do not look only at the ISR function. The full path is:
Read More