how do I eliminate auto breakpoints in interrupt functions?

[checkers]

I want to debug my code, not the interrupts. I set a breakpoint in the C code and press f5. The program executes to the breakpoint.

When I press f10 to step to the next C code statement, it jumps to the latest interrupt function and stops there. I cannot get to the next C statement.

Is there a setting somewhere to tell CW debugger  to ignore the interrupts?

[CrasyCat]

Hello

Which microcontroller are you targeting (HCS08, Coldfire, kinetis, ....)?

Which version of CodeWarrior are you using?

  To retrieve that info:

    - Start CodeWarrior

    - Select Help -> About Freescale CodeWarrior or About CodeWarrior Development Studio

CrasyCat

[checkers]

Thanks for the reply. I am new to CodeWarrior and don't really know how to find the answers on my own yet.

Using the latest CodeWarrior updates with PE 3.04

MC9S12P32CFT micro

P&E multilink universal

Installed Products:

    CodeWarrior Development Studio for Freescale HC12 v5.1 HCS12 G240 Service Pack, build 110228.

    CodeWarrior Development Studio for Freescale HC12 v5.1 HCS12 G64 Service Pack, build 110727.

    CodeWarrior Development Studio for Freescale HC12 v5.1 HCS12 VR64 Service Pack, build 120113.

    CodeWarrior Development Studio for the S12(X) Version 5.1, build 10221.

    CodeWarrior Development Studio for Freescale HCS12(x) v5.1, PE V3.03 Service Pack, build 110331.

    CodeWarrior Development Studio for Freescale HCS12(x) v5.1, PE V3.04 Service Pack, build 120116.

IDE Version: 5.9.0 Build 5294

[CrasyCat · Accepted solution]

Hello

Per default when you are stepping the debugger will stop at the next instruction executed. If an interrupt arises, it will stop inside of the interrupt function.

You can disable that behavior in the following way:

• Start the debugger the usual way
• Select "Multilink/CyclonePro" > "Connect". The Connection dialog is opened.
• Switch to the "Special Setup" tab
• Check the box "Disable maskable ISR's when stepping"
• Click OK to close the dialog.

  Now PC should not enter interrupt function when you are stepping. Only non-maskable interrupts might interrupt the execution.

CrasyCat