UART0->ERROSRC value 0x09

RE: UART0->ERROSRC value 0x09

awneil — Wed, 13 Feb 2019 12:33:21 GMT

The examples don't just "stop receiving" - they do a Fatal Error & crash!

It's easy enough to just handle the case of a UART error appropriately; eg, ignore the byte.

I did post an example of doing that in one of the past threads on this - but can't now find it.

😞

[quote userid="2111" url="~/f/nordic-q-a/43627/uart0--errosrc-value-0x09/170864"]you will avoid the error by adding an pull-up resistor[/quote]

Maybe - but that just masks the symptom.

Your code really needs to properly handle UART errors.

RE: UART0->ERROSRC value 0x09

Kenneth — Wed, 13 Feb 2019 12:27:14 GMT

Unfortunately the examples and libraries have been setup to stop receiving data on error, so you would need to reinit() for instance the serial driver on error. Alternatively in this case I suspect you will avoid the error by adding an pull-up resistor on the UART_RX input pins on both DK.

RE: UART0->ERROSRC value 0x09

awneil — Tue, 12 Feb 2019 18:48:24 GMT

[quote userid="25598" url="~/f/nordic-q-a/43627/uart0--errosrc-value-0x09"]When we pressed the reset button on the slave end, we get a "NRF_SERIAL_EVENT_DRV_ERR" event [/quote]

It is very common - to the extent that applications should expect it - to get a "junk" character or two at startup. Often with framing and/or parity errors.

This is probably what you're seeing.

The Nordic examples do not handle this sensibly:

https://devzone.nordicsemi.com/f/nordic-q-a/41480/multiperipheral-nus-crashes/161714#161714