I want to use libuarte.
Target is nRF52832 and SDK17.0.0.2.
Do I need to take workaround against Errata109 when using libuarte?
And,
I done backport libuarte to SDK15.3.
It's seem success.
Similarly, Do I need to take workaround?
I want to use libuarte.
Target is nRF52832 and SDK17.0.0.2.
Do I need to take workaround against Errata109 when using libuarte?
And,
I done backport libuarte to SDK15.3.
It's seem success.
Similarly, Do I need to take workaround?
Hi Syuji,
Errata [109] affects the peripherals PWM, SPIS, SPIM, TWIS, UARTE, and TWIM. If you don't use those peripherals, you don't need the workaround.
With those peripherals, you could set NRF52_ANOMALY_109_WORKAROUND_ENABLED in sdk_config.h to Enables nRF52 anomaly 109 workarounds for them.
Please note that due to the Easter holiday, we're low on staff, so somewhat lower response times must be expected until April 6th. Sorry about the inconvenience.
-Amanda H.
I know that.
However, nrfx_uarte doesn't seem to have any countermeasures.
Also, libuarte doesn't seem to have any countermeasures.
Since libuarte uses UARTE and PPI, I would like to know if the user needs to implement a workaround.
In fact, there is no protection on the TX side. PPI is used to start TX if long packets are sent (over 255 bytes), so it needs to implement a workaround.
-Amanda H.
OK. Thanks.