topic Re: Why PE_DEBUGHALT / CPU_Interrupt? in CodeWarrior for MCU

Why PE_DEBUGHALT / CPU_Interrupt?

dineshbabu — Sat, 28 Dec 2019 05:51:33 GMT

Hi,

I am using my own board of MKV10Z32VLC7 & MKE02Z32VLC4 which belongs to Cortex-M0+ Based Micro controller.

As we have a product already with MKV10Z32VLC7 and we planned to upgrade to low cost micro controller we choose MKE02Z32VLC4. And now we are migrating the code from MKV10Z32VLC7 to MKE02Z32VLC4, we are facing the PE_DEBUGHALT error after the AMCLIB_PMSMBemfObsrvAB_F16() function call.

I have attached the PE_DEBUGHALT capture file.

It will be helpful when we solve this issue to proceed further.

Is there any motor control library changes required?

Dinesh

Re: Why PE_DEBUGHALT / CPU_Interrupt?

Sabina_Bruce — Fri, 03 Jan 2020 16:25:03 GMT

Hello Dinesh,

Could you please confirm the IDE you are using and the version?

Also there is no attachment on your post, could you please reattach it.

Best Regards,

Sabina

Re: Why PE_DEBUGHALT / CPU_Interrupt?

dineshbabu — Sat, 04 Jan 2020 04:10:23 GMT

Hi Sabina Bruce,

IDE : Codewarrior Development Studio

Version : 10.6

Re: Why PE_DEBUGHALT / CPU_Interrupt?

Sabina_Bruce — Mon, 06 Jan 2020 22:01:09 GMT

Hello Dinesh,

Could you please follow the instructions in this article. So we can detect were the interrupt is coming from specifically.

Oh my! An Interrupt… | MCU on Eclipse

Once you have done that let me know which interrupt handler is used and we can then determine the root cause.

Best Regards,

Sabina

Re: Why PE_DEBUGHALT / CPU_Interrupt?

dineshbabu — Mon, 20 Jan 2020 04:41:07 GMT

Hello Sabina,

I have attached the cpu_interrupt captured file.

Best Regards,

Dinesh

Re: Why PE_DEBUGHALT / CPU_Interrupt?

Sabina_Bruce — Mon, 20 Jan 2020 20:22:06 GMT

Hello Dinesh,

In the case of your hardfault, it could be caused by a variety of situations. Ranging from illegal use of funcitons/pointers/variables, not initiating proper clocks, trying to access memory that is not accessable, etc.

You mention that it goes into hardfault after executing AMCLIB_PMSMBemfObsrvAB_F16(). If this is true, can you place a breakpoint on the line after and it will stop there. Or does it go into a hardfault during the execution of that function.

I would recommend to step through each step, to better locate where it actually goes into the hardfault.

For further reference in debugging hardfaults you can refer to Debugging Hard Faults on ARM Cortex-M | MCU on Eclipse.

Best Regards,

Sabina