Device not advertising after disconnect

RE: Device not advertising after disconnect

brian fleming — Sun, 10 Feb 2019 20:51:40 GMT

Thanks! I have the same problem but different, but at least I have isolated the problem to my C code on the nRF, not the Java code in my APP.

RE: Device not advertising after disconnect

joe.ker — Wed, 19 Jul 2017 07:32:49 GMT

Hi, thanks for the suggestions. I managed to isolate the issue to a particular function of the code which deactivates a portion of my custom PCB (SPI connected ADC) by disabling a load switch and reactivates it when it is needed. If I leave the external ADC constantly powered, the issue does not appear. Since these parts of the code (Advertising and ADC reading over SPI) are in no way related, i imagine that the remaining charge after disabling the load switch has some kind of influence on the nRF pins... I will keep looking...

RE: Device not advertising after disconnect

endnode — Thu, 13 Jul 2017 21:49:39 GMT

It might be caused by any error/hard fault and its wrong handling in your code. The usual (and sometimes the only;) way is to run it in debug mode with UART or SEGGER RTT print-outs at such level that you can easily trace what your code is doing without disturbing the timing and APP/SD flow. With high probability you will then see some bad return (error) code from some sd_xxx function call or deadlock inside your own code...

Normally Nordic BLE Stack (SD) doesn't start advertising after GAP Peripheral link is terminated, it's always application which requests to start it through sd_ble_gap API. If you haven't been doing it before and you've anyway seen you board to start advertising after disconnection then you most probably use some thick library/module from SDK which does it for you (and then if not using correctly or if there is a bug it explains the failures you see).