RE: How to handle the crash about APP_UART_COMMUNICATION_ERROR

Yong.Xie — Sun, 24 Mar 2019 17:03:26 GMT

Hi awneil， Your are right there is no reason to re-initialise the UART after framing error.

If clear the ERROR REG, the RX task will still running.

Pull up RX pin is a good idea for RX stable.

I think maybe I have found the reason why UART “crash” after error.

See the picture below. The SDK will stop the UART when ERROR occured. So I delete those code and test my product.

Now it's stable...

awneil — Sat, 23 Mar 2019 16:28:46 GMT

A framing error just means that the UART thought it saw a start bit, but then couldn't recognise a valid frame (byte, character) following it.

Most likely due to noise on the line.

I can't see any reason to re-initialise the UART after a Framing error.

It's up to your application how to handle the situation.

None of this has anything specifically to do with Nordic.

But the way (some of) Nordic's examples handle framing errors is particularly daft: