With Ozone we have encountered a rather strange display artifact.
Every time an software interrupt call ends, the whole stack does not drop down one bar, instead one main() gets filled in immediately after the terminated interrupt handler, resulting an ever stacking up main(), see below.
Is there any way to alleviate the problem?
Edit: I later found out that this stacking up would only happen during a software interrupt ending, normal interrupt are handled correctly
And it seems rather bizarre that the sw interrupt ended without PE coming back from the call stack to end it, it just suddenly ended on its own.
The chip we are tracing is nRF52833 from Nordic, it's a cortex M-4 processor. Is there any explanation as why a sw interrupt would end on its own?
Thanks.
Every time an software interrupt call ends, the whole stack does not drop down one bar, instead one main() gets filled in immediately after the terminated interrupt handler, resulting an ever stacking up main(), see below.
Is there any way to alleviate the problem?
Edit: I later found out that this stacking up would only happen during a software interrupt ending, normal interrupt are handled correctly
And it seems rather bizarre that the sw interrupt ended without PE coming back from the call stack to end it, it just suddenly ended on its own.
The chip we are tracing is nRF52833 from Nordic, it's a cortex M-4 processor. Is there any explanation as why a sw interrupt would end on its own?
Thanks.