Same codes and project file, but hardfault on other PCs

RE: Same codes and project file, but hardfault on other PCs

it0406 — Tue, 28 Sep 2021 12:43:03 GMT

It is just my example project, but based on a SDK example. I just added some lines for my work.

I didn't try it with default SDK examples.

Best regards,

it0406

RE: Same codes and project file, but hardfault on other PCs

Simonr — Tue, 28 Sep 2021 12:23:40 GMT

I agree with Turbo J. If the stack is indeed okay, adding a hardfault handler of your own should help debugging here. Does default SDK examples also hardfault on this one computer or is it just your specific example project?

Best regards,

Simon

RE: Same codes and project file, but hardfault on other PCs

it0406 — Mon, 27 Sep 2021 18:59:47 GMT

Thank you for the reply.

[quote userid="18935" url="~/f/nordic-q-a/80043/same-codes-and-project-file-but-hardfault-on-other-pcs/331362#331362"]Add your own HardFault_Handler() to your code. This way the code won't end up in the default Handler. Can help debugging if - and only if - the stack was still OK.[/quote]

As I know, hardfault means unrecoverable system failures.

Can I ignore it just with a hardfault handler? Or do you mean some hardfault cases in the handler and should the debug be stopped in this handler?

[quote userid="18935" url="~/f/nordic-q-a/80043/same-codes-and-project-file-but-hardfault-on-other-pcs/331362#331362"]The default handler for faults (and undefined interrupts) resides in thumb_crt0.s source file IIRC.[/quote]

Should I modify something in the file?

RE: Same codes and project file, but hardfault on other PCs

Turbo J — Mon, 27 Sep 2021 14:53:57 GMT

Add your own HardFault_Handler() to your code. This way the code won't end up in the default Handler. Can help debugging if - and only if - the stack was still OK.

The default handler for faults (and undefined interrupts) resides in thumb_crt0.s source file IIRC.