Synchonisation in Trustzone secure world by callbacks to non-secure world

[aggarg (Gaurav Aggarwal)]

@jefftenney

EDIT: I think I’ve answered my own question. Passing &xWasHigherPriorityTaskWoken to the FreeRTOS API function wouldn’t work because it would refer to memory on the secure main stack. That memory should be marked as secure access only, thus preventing the non-secure API function from writing to it. I think I’m ready to give up on the secureportEND_SWITCHING_ISR() idea because it really cannot fit the existing usage pattern for portEND_SWITCHING_ISR().

Yup, that is the reason!

@aggarg

If secureportEND_SWITCHING_ISR only validates interrupt priorities, then all is good.

What do you think about the above? In other words, have asecureportVALIDATE_INTERRUPT_PRIORITY which people can optionally call from secure ISR to incorrect secure interrupt priority configurations.