RE: Getting the following error message when working with Laird BL652 (nRF52832): NRF_FAULT: id=\01 pc=0x442dc info=323743.

Sigurd — Tue, 03 Mar 2020 12:36:20 GMT

Hi,

Is the code going into app_error_save_and_stop() ? If yes, then you should be able to look at the call stack to see where the error is coming from. If you set DEBUG as a preprocessor symbol, the error-code and where the error is coming from should also be printed by nrf_log (you can use either UART or Segger RTT as logger backend).

Since you have the PC value, and if you have the .elf file, you could use arm-none-eabi-addr2line to find where it is failing also.

// Example, pc=0x01BEEF

$ arm-none-eabi-addr2line 0x01BEEF -e app_beacon.elf

C:\folder\SDK\src\main.c:34