nRF52840 BLE UART re-connect fail

RE: nRF52840 BLE UART re-connect fail

Hung Bui — Mon, 15 Jan 2018 14:37:42 GMT

Most likely the UART buffer was overflowed. Have you really debug ? Put a break point in the app error handler ?

There could be a chance that it was the issue with the segger chip (USB-> UART) crashed. I would suggest to test using better UART-UART solution or reduce the baudrate or use HWFC in your case.

RE: nRF52840 BLE UART re-connect fail

miki_h — Mon, 15 Jan 2018 14:17:04 GMT

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...

RE: nRF52840 BLE UART re-connect fail

Hung Bui — Mon, 15 Jan 2018 12:16:53 GMT

When something doesn't work as it should, you should debug. To debug, follow this guide.