topic Re: How to trace PE_ISR() for MK60 MCU in Kinetis Microcontrollers

How to trace PE_ISR() for MK60 MCU

rabbitz — Thu, 03 Sep 2015 08:20:09 GMT

I have an CodeWarrior peoject with PE generated code, it some time trigger PE_ISR() and hang, I would like to trace the reason and fix it.

Is there suggestion how to trace it?

Regards

Sam

BlackNight — Thu, 03 Sep 2015 09:36:38 GMT

Hi Sam,

You can enable 'own handler for every interrupt', so you know which interrupt is firing.

I hope this helps,

Erich

rabbitz — Fri, 04 Sep 2015 00:05:48 GMT

Hi Erich,

It is Hard_Fault,

How many conditions can cause this fault?

Regards

Sam

BlackNight — Fri, 04 Sep 2015 05:36:15 GMT

Hi Sam,

most likely it is a misaligned access, an access to a NULL pointer or accessing a peripheral which is not clocked/powered.

Here are a few articles how to debug the reason for the hard fault:

For the last one with that Processor Expert component (this is what I use with my Processor Expert projects), you can find it on SourceForge:

I hope this helps,

Erich