UART Service instant overflow

RE: UART Service instant overflow

Drewster — Thu, 21 Sep 2017 04:16:07 GMT

Found the answer - it's a little dumb..

in ble_evt_dispatch it looks like I forgot to add the NUS! Naturally, it was never getting into a "connected" state

RE: UART Service instant overflow

Drewster — Wed, 20 Sep 2017 13:44:46 GMT

@Martin I edited my post to account for most of your comment. The errors occur with UART connected, otherwise it seems to just hang out and connect to devices fine. I've added more detail on the errors and when they occur above.

"Initialize UART" was just bad structure - that's just on the list of successful things

RE: UART Service instant overflow

MartinBL — Wed, 20 Sep 2017 07:27:16 GMT

It is possible to disconnect the RX pin altogether if you need to test this.

RE: UART Service instant overflow

MartinBL — Wed, 20 Sep 2017 07:26:37 GMT

Hi,

Can you try to set NRF_LOG_DEFAULT_LEVEL to 'Debug' in sdk_config.h so that maybe we can get some more detailed logging.
If you leave the RX line on the nRF52 unconnected and floating in the wind it is pretty common to get UART errors because it picks up noise which registers as incoherent UART frames.
Do you at any point, with RX connected or not, get any error info out of the UART event handler? The parameter passed into the handler might contain some valuable info. You can find the info in p_event->data.error_communication and/or p_event->data.error_code
You say that "Debugging points to a UART overrun". Are there any specific clues that points to this?
In your list of bullet points you list "Initialize UART" after you get the APP:INFO:Disconnected message. Is this correct and as intended?