Debug hardfault with MCUXpresso. Vectpc show less information than LPCXpresso?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debug hardfault with MCUXpresso. Vectpc show less information than LPCXpresso?

1,578 Views
tim99
Contributor III

When experiencing a hardfault when debugging with LPCXpresso, looking at vectpc would give you useful hints on what had happened. Screenshot below is from a hardfault in LPCXpresso

pastedImage_1.png

In MCUXpresso this information does not apare:

pastedImage_2.png

How do I find the same information in MCUXpresso?

Labels (1)
Tags (2)
0 Kudos
3 Replies

1,036 Views
lpcxpresso_supp
NXP Employee
NXP Employee

We'll be implementing a fix for issue with the (LinkServer-specific) "vectpc" functionality in the next IDE release.

In the meantime, and also if you try using a different probe type, then this blog article may be of interest...

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

Basically this mimics exactly what the IDE is doing with "vectpc".

Regards,

MCUXpresso IDE Support

0 Kudos

1,036 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Thank you for the report - you appear to be correct.  We'll investigate.

Regards,

MCUXpresso IDE Support

0 Kudos

1,036 Views
tomaszziajko
Contributor II

Any luck in finding the problem? Additional information would be very helpful in hardfault tracking, and moving whole project to legacy IDE does not seem reasonable....

0 Kudos