I'm getting an occasional NRF_LIBUARTE_ASYNC_EVT_OVERRUN_ERROR, it often takes over 24 hours to reproduce, and the libuarte appears to be generating garbage after the error happens.
We're using SDK 16, SoftDevice 132 v7.0.1, and the device is sitting on an RS485 token bus.
The issue is pretty much identical to this one: https://devzone.nordicsemi.com/f/nordic-q-a/74726/getting-nrf_libuarte_async_evt_overrun_error-after-long-time-of-use I saw no cause or resolution to it.
NRF_LIBUARTE_ASYNC_EVT_OVERRUN_ERROR is for the hardware FIFO, correct? Or does this also occur when DMA is full?
I'm guessing that DMA is not doing its job, so it must be some kind of timer conflict. I'm using Timer1 and Timer2 for libuarte.
Our DMA is using 8 buffers with a size of 255. Our interrupt routine simply moves any incoming bytes into an internal software buffer, so these buffers appear to be way overkill. It would have to be a pretty serious interrupt latency for this to be a problem.
There appears to be some correlation with a lot of Bluetooth devices advertising nearby; when Bluetooth is turned off, we do not see this issue.
Not sure where to go from here.
