Reading jyiu book on Cortex-M4 and general information about usage of PendSV exception type.
One application highlighted is of context switching in the RTOS wherein on a Systick timer interrupt, instead of context switching, it will set the PendSV bit. This will then execute the context switching at the lowest priority after all other interrupts have been handled. Again this is because the priority of PendSV will be kept the lowest.
However, is the same not possible if we just lower down the priority of Systick timer exception? In that case, if any interrupt is active, the systick timer exception handler will get executed after all other interrupts are done with.
If that is possible, then what is the major benefit in using PendSV?
Am I missing something?
But isn't the priority of the systick timer unconfigurable? The manuals say that it is configured with a static priority -3(Highest).
SysTick exception's priority level is programmable. Could you let me know which document said it is fixed? It might be a documentation error. Thanks
Joseph