I am running an application on the simplelink evaluation board MSP-EXDP432E401Y with the XDS110 debugger that is integrated into the eval board. When I insert a breakpoint into an ISR the break happens but I am unable to do anything but hit run again. There is no single stepping capability. Single stepping works fine outside the ISR. Is there a compiler setting that should be set?
Googling your "MSP-EXDP432E401Y" board leads me back here, You mean this?
http://www.ti.com/tool/MSP-EXP432E401Y
Is there something else interrupting the interrupt you've stalled?
Perhaps try some instrumentation to understand how you own code works/flows under dynamic conditions. Do you really need to single step an interrupt to know what it should be doing? Apply basic static analysis methods, and augment those with instrumentation and sanity checking. Record stuff to a play-back/trace buffer so you can better understand the dynamics and interplay with other interrupts, etc.
groupalpha said:board MSP-EXDP432E401Y with the XDS110
So that's a TI board, with TI's own debugger.
What if you use TI's own tools ?
Is it any different in Keil if you use a uLink or J-Link ?
Westonsupermare Pier said:Do you really need to single step an interrupt
This is s good point: By nature, interrupts are generally time-critical - so breakpoints or single stepping inside an ISR are likely to disrupt things ...
I believe you have misunderstood my question. When the Keil IDE is set of a breakpoint in an ISR (it really doen't matter why) the breakpoint occurs and the execution is halted with the run point cursor at the breakpoint. However, none of the step functions (over, into, run to cursor) are enable and the keystrokes normally associated with those actions do not work. I am asking is this a problem with the IDE, or possibly the XDS110 debugger I am using.
.
groupalpha said: I am asking is this a problem with the IDE, or possibly the XDS110 debugger I am using.
Again, you could narrow that down by trying a different debugger and/or trying a different IDE.