Other Parts Discussed in Thread: ADS1298
I have an MSP430 MAVRK development kit with a few plug-in modules and am trying to integrate multiple TI demo apps for these modules into a common single application as a prelude for developing an application for our target board design. I have 3 modules, including an ADS1298 module, plugged in and all working with the MAVRK AppMonitor as individual stand-alone demo apps from the mavrk_embedded repository. However, my debugging efforts are being hampered by some apparent limitations of the debugger in an interrupt loaded environment.
The problem I am having is that the single-step commands in the debugger, including both step-over and step-into functions, cannot be effectively used because the debugger jumps to the port 2 ISR with every attempt to execute the next line of code after a breakpoint has been reached. The interrupts are running at a high rate since the ADS1298 is continuously streaming data at 500 samples per second, so every time I attempt to single step, including step over, a port 2 interrupt is pending and the first line of the ISR is where program control jumps to and stops. This debugging handicap is further compounded by the apparent absence of a run-to-cursor debugger command that most quality debuggers have.
These limitations associated with debugging in an environment with a high rate of interrupts will profoundly hamper my product development as I continue to build a bigger and more complex application during the development cycle for my target board. Can you offer any help with facilitating my debugging efforts with CCS5 in this heavily interrupt loaded environment?
