在调试模式下，ISR消耗单步

亲爱的论坛读者，
在调试模式下运行时，我一直在PSoC5和5LP系列部件上出现问题。我的问题是，当我有一个tiC ISR系统，每秒100000万次更新计数器。我想调试一个单独的不相关的代码段。所以我会设置一个断点，然后尝试单步通过我要检查的代码。我需要打开的中断才能进入这段代码。计数器计数，然后在计数器达到特定值后执行特定代码。所以我需要调试的代码。我将设置一个断点，代码执行停止。现在我想单步执行下一行代码，单击单步按钮，然后我在ISR中，而不是我想去的地方。好的，我会点击跳出按钮，然后我又回到ISR的开始。回到断点的唯一方法是点击播放按钮。在这一点上，我回到那里，我点击单步按钮，我在ISR再次。我希望部分/调试器有一种方式允许我在中断启用时使用单步模式。当我遇到一个断点时，内部时钟似乎并没有停止，调试器没有在我通过每一行代码时向处理器添加一个固定数量的时钟。C代码的每一条独特代码行都必须与X .ASM指令的Y系统时钟相等，而C是C的特定行中的指令。相反，我得到一个断点，调试器停止并显示我在哪里，但是处理器上的内部时钟继续运行时钟。时钟是从CyOnCH出来的示意区，这是绑在一个ISR。它与主控有同步。我应该使用另一种时钟吗？我知道我也可以关闭我的断点后，手动中断我的断点和重新启用它们，一旦我通过调试，但必须有一个更好的更清洁的方式来工作。
谢谢你的帮助！！
马特



     以下为原文
  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!!
    Matt