nRF52832 hardfault with all provided example

[kurta999]

Hi,

My problem in shortly is when I have debugger connected to nRF5282, I always get hardfault after some time.

https://i.ibb.co/hZ3bZ1b/optionbytes-1.png

I tried VisualGDB & Segger Embedded Studio, the result is same. For development board I'm using Laird BL652 development kit (https://www.lairdconnect.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl652-series-bluetooth-v5-nfc-module) and I have one custom PCB. On custom PCB I'm even unable to  see the bluetooth, but on laird one I can. 

I already wasted days on this and still no results, mostly on when softdevice_enable didn't worked so I've disabled the crystal and using internal RC.

Any ideas please?

[jing]

My guess is that the sample application tries to go to system off and is expecting a NRF_SUCCESS from sd_power_system_off().

sd_power_system_off() with debugger connection will result to (NRF_ERROR_SOC_BASE_NUM | NRF_ERROR_NOT_SUPPORTED).

Can either add the above result as valid or disable power save temporarily when debugging.

jing