Since upgrading from MDK 4.7.0 to 4.7.0A I'm seeing strange behaviour in the debugger. Running on LPC4330 and without any changes to the code, code which compiled and was debuggable with the old version still compiles and runs perfectly but crashes when debugged.
The issue seems to be related to having the call stack / locals displayed. I can single step and display variables without a problem, but if I enable the call stack window the debugger is causing a memory exception on the chip and crashing, requiring a HW reset to recover.
It's not possible from the error messages to see what address it was trying to access to cause this problem, is there a way to limit the call stack depth.
Since the code runs fine until single stepping I'm confident that this is a debugger issue and not caused by any issues in the compiled code.
And since the debugger was working with the previous version I tried to revert to that but now I see the same problem, so I assume that the installer has updated the FW in the uLink devices and / or the DLL used to handle them.
so how do I revert the debugger to the previous state?.