Hi,
A system event (memory violation) generates us a HWI (as we can not afford exceptions in our system) ending up in an ISR. We would like to know what was the context (all registers and active stack pointer) that lead to violation. Is there a way to know the task before HWI ISR?
We are using BIOS 6_33_06_50 on EVM c6678.
Assuming we know the task (task handle) that was active before ISR is known to us, can we use Task_stat to get task information?
Does the statbuf->sp points to the top of the active stack? statbuf->used appears to be computing the maximum stack used so far.
if statbuf->sp is not the stack pointer, is there a way to figure out the task's stack pointer?
Best Regards
Judah
