Hi NXP Team,
I have a debugger usability problem:
Environment: Code Warrior 10.7, P&E debugger, TRK-USB-MPC5643L, Embedded Qorivva OSBDM/OSJTAG Device
I'm writing exception handlers and have to inject a lot of arbitrary errors for testing it. This leads to a lot of se_illegal instructions, which is expected, wanted and natural because of the simple binary pattern zero of the instruction. My problem is that the frequent appearance of this instruction in the software error paths makes debugging of my software virtually impossible since the debugger understands the instruction as a break point. Instead of getting into the debugger, I would like the software to continue to see if the fault is safely caught by the program interrupt handler.
My question: Is it possible to instruct/configure the debugger to not break at an se_illegal instruction?