Hardfault analysis

[Igor]

I got the following hardfault:

hardfault_implementation.c,  108, HARD FAULT at 0xCFB3986B
hardfault_implementation.c,  109,   R0:  0x000692BC  R1:  0x2003E834  R2:  0x0000C779  R3:  0x0086DD77
hardfault_implementation.c,  111,   R12: 0x0006919D  LR:  0x2003E820  PSR: 0x2003E870
hardfault_implementation.c,  128, Cause: The processor attempted a load or store at a location that does not permit the operation.
hardfault_implementation.c,  128, Cause: Stacking for an exception entry has caused one or more access violations.
hardfault_implementation.c,  134, MemManage Fault Address: 0x2003E878

addr2line

%addr2line% -e program.elf -f 0x2003E820

returns:

__stack_start__
libvfprintf.c:?

Did I misinterpreted the hardfault message? Or is the hardfault source really in libvfprintf? How to find out the root cause for this error?

[nRF52840, nRF SDK 16.0, Mesh SDK 4.0, SD140 7.0.1]

[Turbo J]

Igor said:

is the hardfault source really in libvfprintf?

Most likely a  "%s" with the string pointer not properly initialized or otherwise overwritten.

Might be a simple mistake (using uninitalized memory) - or worse: a stack overflow. The latter can be really hard to debug properly.