AnsweredAssumed Answered

Corrupted metadata and hardfaults

Question asked by Catosh on Jun 14, 2019
Latest reply on Jun 20, 2019 by Jiri Kral

Hi all; 

I noticed a fancy behavior using S32ds and segger jlink. 

I have a fully working project, sometimes I need to make some edits and reload the project.  Out of the blue, I get an hard fault on the MCU where it should generally execute the systick handler. 

Exploring the bin, I can see that the address of the systick ISR is the one I expect, where I expect it. 

Flashing the MCU using the binary and segger jlink everything works fine.

Flashing the MCU inside Design studio using segger in debug mode it gets the hard fault. 

 

Many possible fault paths here, but what I found out is that erasing Eclipse metadata and re-importing the project WITHOUT any change fixes the issue. 

 

Any hint on this point? IT took almost a work week to figure out what was wrong (omitting some verbose detail here) and I think it would be beneficial to have some insight on this point for other developers facing similar issues. 

 

K.R..

 

 

Outcomes