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

nRF52840 BLE UART re-connect fail

Hi, I'm working on the nRF52840 DK and running the ble_app_uart example. I'm connecting to the BLE using the nRF UART V2.0 app and open a terminal. In the terminal I'm sending a large amount of non-stop data which the nRF52840 forwards in BLE to the app. Sometimes when I disconnect and trying to reconnect again is success and sometimes fails, it seems the program which is running on the nRF52840 doesn't reapond: the LED doesn't blinks and you can't see the advertising name. When it happens the only way to be able to reconnect is by disconnecting and connecting the USB cable from the PC. Any ideas what to do?

Thanks, Miki

Parents
  • Hi Hung,

    When I debug it the UART port is not flooded with data vs working in real time so everything works perfect... Moreover, I added a software reset procedure to the case when BLE is disconnected and still same same... Its getting even more complicated to understand when the reset button (hardware reset) sometimes doesn't solve it either! (if this was the solution it was very disappointing) I thought it maybe because the USB to UART is done in the Segger MCU on the DK but in such case the reset for the nRF52840 should make the LED at least blink again and the BLE should be discoverable. It's like the UART channel somehow interfere the whole process in a way that only by disconnecting the USB hardware and connecting it back again can solve it.

    So unfortunately I don't know a better way for debugging it when the problem happens only in real time when the UART is flooded with data...

Reply
  • Hi Hung,

    When I debug it the UART port is not flooded with data vs working in real time so everything works perfect... Moreover, I added a software reset procedure to the case when BLE is disconnected and still same same... Its getting even more complicated to understand when the reset button (hardware reset) sometimes doesn't solve it either! (if this was the solution it was very disappointing) I thought it maybe because the USB to UART is done in the Segger MCU on the DK but in such case the reset for the nRF52840 should make the LED at least blink again and the BLE should be discoverable. It's like the UART channel somehow interfere the whole process in a way that only by disconnecting the USB hardware and connecting it back again can solve it.

    So unfortunately I don't know a better way for debugging it when the problem happens only in real time when the UART is flooded with data...

Children
No Data
Related