NRF52 doesn't work after a few days

RE: NRF52 doesn't work after a few days

Nguyen Hoan Hoang — Thu, 01 Feb 2018 23:58:19 GMT

Not working you mean not advertising ? If that is the case, check the advertising timeout. Set it to 0 for non stop advertising otherwise it will stop at timet out. The default was usually 180 seconds.

RE: NRF52 doesn't work after a few days

Otavio Borges — Thu, 01 Feb 2018 23:09:08 GMT

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.

RE: NRF52 doesn't work after a few days

RK — Thu, 10 Aug 2017 21:22:28 GMT

You can attach a debugger to a running chip, halt it and read the registers. Literally do exactly that, attach a debugger (JLink recommended), I'd use the command line to halt it and read the registers. Most IDEs will try hard to reset and reprogram so they won't work well. If you try Segger's excellent Ozone debugger I think you may be able to point it to the software image, attach it and get a full debugger at the point you've halted. Try it on a running chip, it's a nice tool.

Note that as soon as you do attach a debugger, you can't single step (well you can if you use the debugger to instantly disable all interrupts to stop the softdevice getting any). So you really just have a frozen 'moment in time' to work from, but that may be enough.