Hi @all, I am using the FreeRTOS with an NXP LPC2290 and my code creates abort-interrupts but I don’t know where the bad code is, so one solution is to print the actual register-contents before the interrupt is caused in order to detect the bad code. Does someone have a solution who to do get the register contents in order to print it out during abort-isr or does someone have a better solution to find the bad code ? regards Joe

First – the most common cause of an abort is a stack overflow.  Check the size of the stacks allocated to the tasks and in particular check the stack of the task pointed to by pxCurrentTCB after the abort has occurred. If you cannot work it out then when the abort occurs you can look at the saved link register, subtract 8 from the value, then this will be the instruction that was executing.  It would be a bit tricky without a debugger.

Ok i will do that, thank you regards Joe