Dear Forum readers,
I have been having an issue on the Psoc5, and 5lp series parts when running in debug mode. My problem is when I have a system tic isr that goes off at 1000-10000 times per second to update counters. I am wanting to debug a separate unrelated section of code. So ill set a break point and then attempt to single step through the code I want to inspect. I need the interrupts turned on to get into this section of code. Counter counts up and then executes specific code once counters reach a specific value. So I'm in the code I need to debug. I'll set a break point and the code execution stops. Now I want to single step to the next line of code, Click the single step button and then I am in the ISR and not where I want to be. Ok, I'll click the jump out button and then I'm at the beginning of the isr again. The only way to get back to the break point is to click the play button. At this point I'm back where I started and I click the single step button and I'm in the isr again. I am hoping the part/debugger has a way of allowing me to use the single step mode while the interrupts are enabled. It seems like the internal clocks are not stopping when I have hit a break point and the debugger is not adding a fixed number clocks to the processor as I step thru each line of code. Each unique line of c code with x .asm instructions should equal y system clocks based upon the instruction in that specific line of c. Instead I get to a break point and the debugger stops and shows me where I am but the internal clocks on the processor keep running the clocks. The clock is coming from the cy_clock out of the schematic area which is tied to a isr. It does have the sync with master checked. Should I be using another kind of clock? I know I can also turn off the global interrupts manually after I hit my break point and reenable them once I am through debugging, but there has got to be a better cleaner way for this to work.
Thanks for the help!!