This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52840 NUS application: communication lost with nRF UART APP

Hello everybody.
Using the nRF52840-DK board and the Nordic example ble_app_uart_pca10056_s140 I am sending 200 bytes, repeatedly, to the Nordic UART APP.
Everything works correctly, only after a few minutes, I randomly lose communication with my smartphone.
Am I getting some configuration wrong?

Appearance vs suggestions.
Thank you.
Francesco

  • Hello Francesco,

    Using the nRF52840-DK board and the Nordic example ble_app_uart_pca10056_s140 I am sending 200 bytes, repeatedly, to the Nordic UART APP.
    Everything works correctly, only after a few minutes, I randomly lose communication with my smartphone.
    Am I getting some configuration wrong?

    Have you made any changes to the examples, on either side?
    Or, could it be that one of the devices are resetting when this happens?
    I suspect that you could be getting a buffer overflow, leading to a device reset and broken connection.

    Please make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image:
    This will make your logger print a detailed error message if a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.
    Please mind that the Nordic UART examples use the RTT backend for their logging, so you will need to use an RTT compatible serial monitor to see the logs (like the SES debug terminal or the standalone Segger RTT Viewer desktop application).

    In case you are not getting any error messages printed to your logger: Are you familiar with the nRF Sniffer tool? It would be very helpful if you could capture a sniffer trace of the on-air BLE communication between the devices when this happens.

    Best regards,
    Karl

Related