Kinetis MicrocontrollersのトピックK64 ivINT Hard Fault

K64 ivINT Hard Fault

vnguyen — Sat, 14 Mar 2020 00:24:13 GMT

Hi everyone,

Once in a while my program would crash and end up in the below function that belongs to the "Vectors.c" file. Under what situation would cause a program to crash and trigger it to go to the below function.

PE_ISR(Unhandled_ivINT_Hard_Fault);
PE_ISR(Unhandled_ivINT_Hard_Fault)
{
PE_DEBUGHALT();
}

Debugging ARM Cortex-M Hard Faults with GDB Custom Command | MCU on Eclipse

armex
EXEC_RETURN (LR):
lr                      0xffffffe9             4294967273
Uses MSP 0x2002ff38 return.
xPSR                0x5923
ReturnAddress 0xa
LR (R14)           0x0
R12                   0x20
R3                     0x2002ffbe
R2                     0x0
R1 0x2002ffbe
R0                     0x2002ff40
Return instruction:
0xa <__vect_table+10>: movs r0, r0
LR instruction:
0x0 <__vect_table>: movs r0, r0

Best Regards,

Re: K64 ivINT Hard Fault

kerryzhou — Tue, 17 Mar 2020 04:50:53 GMT

Hi Vu Nguyen ，

What's the kinets chip you are using? Tell me the chip partnumber.

What's the IDE you are using?

We highly suggest you use the SDK with the newest MCUXPresso IDE, or IAR, MDK. PE in the old IDE will be not supported now.

Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: K64 ivINT Hard Fault

vnguyen — Tue, 17 Mar 2020 18:33:40 GMT

Hi Kerry,

I'm using KDS version 3.2.0. The chip part number is MK64FN1M0VLL12.

Re: K64 ivINT Hard Fault

kerryzhou — Wed, 18 Mar 2020 04:24:46 GMT

Hi Vu Nguyen,

What's the detail code you have added to cause the hardfault problems.

As I know, if you access the module register which doesn't enable the module clock will cause the hardfault problems.

You also can refer to the link which you already mentioned to check more details:

Debugging ARM Cortex-M Hard Faults with GDB Custom Command | MCU on Eclipse

Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!