Question: How do I prevent the debugger from stopping in isr_default

[nijo]

Hey,

I am debugging some small code. My problem is that the debugger keeps getting stopped when it hits the isr_default.

PE_ISR(isr_default)
{
/* Write your interrupt code here ... */
}

Is there someway to understand where this interrupt comes from? (In the interrupt vector almost everything except PIT gets directed to this, so I cannot see the origin of the interrupt).

Is there anyway for me to "select" that the debugger should not stop here, just keep going?

I should mention that I am newbie.

Best regards

Niklas

[mjbcswitzerland · Accepted solution]

Niklas

I think that it may be possible to remove the default breakpoints in the error handling interrupts but I wouldn't recommend it.

If you are entering into an unexpected ISR it means that there is a (quite serious) error in the code, which should not be simply ignored.

If you step back out of the interrupt handler (best in assembler view) you may find that it then shows you the cause of the problem. You may find that the default handler is handling errors due to illegal HW accesses (the register or memory at fault can then be seen and the cause of it solved in preference to not seeing it happening). Once you have solved the problem you will not find the default ISR disturbing any more.

Regards

Mark

[nijo]

Thanks for you answer. I think I finally figure out my problem. I read up in the manual about the SIM and started fresh. I think I had plenty of errors in my .pe file, especially the clock gates. Now when I run, I do not get stuck in the default interrupt anymore. So you are correct, the debugger kept stopping in isr_default because my project/code was completely wrong.

Thank you very much for looking at my question.

[leccy]

nijo

i am having a similar problem with a default ISR running a project created mostly with PE.

can you be more specfic about the problems you found with the code created for SIM

thanks

leccy

[BlackNight]

Hello,

there is a setting in Processor Expert which allows you to generate a handler for each vector.

That way you will know what has caused that interrupt.

See http://mcuoneclipse.wordpress.com/2012/02/20/oh-my-an-interrupt/

BK

[leccy]

BK

thanks for that - should have seen it earlier

ISR now shows as Hard Fault...

will now see where that leads!

leccy