RE: nrf52810 BLE examples only run in debug mode

lifeglug — Tue, 09 Mar 2021 09:19:04 GMT

Hi Edvin,

thanks for your suggestion. I am not using UART for my application, and I have tried disabling everything relating to UART in the example app but this doesn't make any difference.

I have tried other examples without Bluetooth and they work perfectly (I can run the code normally with no debugger connected). So there must be something in the Bluetooth code - or some config setting in Segger Embedded Studio - which causes this.

I am going to try incrementally adding Bluetooth bits to a working example to see which component causes it to stop working.

RE: nrf52810 BLE examples only run in debug mode

Edvin — Thu, 25 Feb 2021 14:58:28 GMT

Hello,

I am not sure whether this is the issue, but it was the first thing that came to mind. What HW are you running this on? And what debugger are you using? Are you using a DK with the on board DK, or a custom setup?

Are you using UART in your application? A common mistake is that people who use the DK and UART struggles when the debugger is not connected, because this is also the device keeping the UART RX pin grounded. When this pin is floating, you may receive some APP_UART_COMMUNICATION_ERROR events, causing your device to reset.

Do you have any way to monitor the log when the debugger is not connected? If possible, you can use UART with an external UART to USB device.

BR,

Edvin