I'm doing some CCSv4.2.00033 development on a TMS320C2384x MCU and I'm trying to use the debugger to figure out what's going on with my code.
Unfortunately, the debugger has started acting flakey over the past few days and has steadily gotten worse.
For starters optimization is turned off (Level 0), and full symbolic debugging is turned on.
Breakpoints within ISRs and the initial setup seem to work, but within Main once I finish my initialization and enter my infinite loop none of the breakpoints seem to catch.
All breakpoints have the little circle and check and are in color so they seem to be active. But if I press the little "run" button it just free runs and never catches.
So if I press the "pause" button it'll stop, sometimes in main, sometimes in one of the ISRs. I can go step by step from then until I reach a printf or another function from code I've added to my project.
In addition, I have a few test printf routines and the text never shows up.
Also, if I try to "step over" a printf the debugger acts like it's freerunning again (i.e. the play button greys out, the cursor indicating we're stopped goes away) and it doesn't stop until I press the "pause" button again.
The debugger does exactly the same thing on another function from code that I've added to my project. I can't "step over" this function, but I can "step through" it.
Has anybody seen this issue before? Is it as simple as some setting and/or checkbox I've neglected to set up?
The printfs were working a few days ago and I haven't messed with compiler or debugger settings since then.
