NRF52 doesn't work after a few days

[Ricardo Nunes]

I'm getting a weird behaviour on my first NRF52 custom board. It's a BLE with HR, battery and a custom service. After programming I can test it properly with/without debugger and powered either by FTDI + Regulator or a battery.

For 2 times now the system just stops working, not even with BLE detected by PC or Android phone (connection with both worked before). After reprogramming the exact same software, everything goes back to normal.

I was thinking about putting a software UART (the hardware one is already taken) to have some feedback, but maybe there are other alternatives. Can I create a debug session on a already running device, without reprogramming it?

Did you ever had such problem? What could be wrong to make this happen and what methods can I use to diagnose it?

[Otavio Borges]

I had a similar issue. If your problem is recurrent (undoubtedly the BLE will froze) you could let the board running connected to the debugger, with a breakpoint on app_error_handler_bare and first lines of main. If, for some reason, your firmware is glitched you would trap the code before it reboots and use stacktrace to check from where is coming the error.

I've done such using a custom board attached to the Nordic nrf52DK and eclipse as IDE. solved my problems.