Hard fault documentation

[Roei]

Hi,

I would like to document the error reason and program counter on every hard fault.

I added it to my application, in HardFault_c_handler(). I save p_stack->pc and cfsr.

The problem is that the program counter always saves as 0, so I can't know where the hard fault occurred.

What is the reason for that 0? What can I do?

Thanks!

[Susheel Nuguru]

most likely it is invalid or garbage value popped for a corrupted stack. First thing i would check to see if there was enough RAM space for the application to run.

[ilyasbsran]

Hi, Can you explain how you log the error reason and program counter? Do you log them into the flash? If the answer is yes, Which flash did you use?

[Susheel Nuguru]

Normally in the HardFault_c_handler default implementation you should have this deducible when debugging or are thrown out to the selected logger backend.

[ilyasbsran]

I don't have a connection to the device all the time so I need to save this info in flash. But when I use fds library in HardFault_c_handler I am not able to save them. But when I use the fds library, I don't get any errors either.

[Susheel Nuguru]

you cannot use fds in hardfault handler. Hardfault is higher priority exception than the SWI interrupts (BLE event handling) which is needed for the fds to work properly when using softdevice.