RE: How to determine the context of a callback

benjamin.forest — Mon, 30 Mar 2020 06:39:41 GMT

Thanks a lot, I will use this solution nex time :). Have a nice day,

RE: How to determine the context of a callback

Vidar Berg — Fri, 27 Mar 2020 10:16:46 GMT

Hi,

The app uart library does not include support for the app scheduler so the callback is reported in the UART interrupt context. Generally, I think the easiest way to find this out by debugging the application in an IDE. Below is a screenshot I took from Segger Embedded studio when I have hit a breakpoint in the UART callback. As you can see from the call stack, the UART IRQ handler is called first followed by some event handling before notifying the app directly through the registered callback. The ISR number shown in the xPSR register on the right would have been zero if the callback was invoked in main context through the app scheduler, etc.

It's also possible to use the current_int_priority_get() function in your code if you want to check if you are in an interrupt context or not programmatically.