https://devzone.nordicsemi.com/f/nordic-q-a/37560/is-s132-v6-0-0-use-of-timer0-affected-by-nrf52832-errata-78In the course of investigating higher than expected current consumption, I&#39;ve been looking at nRF52832 errata, and one that I&#39;m concerned about is #78, use of Timer STOP task causing higher current consumption. I&#39;m not using any Timer modules, but theen-USTelligent Community 13Fri, 17 Aug 2018 17:15:13 GMThttps://devzone.nordicsemi.com/thread/144768?ContentTypeID=1Fri, 17 Aug 2018 17:15:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ffc6d00e-1d99-4e14-8c83-54520b0c1d26eric-appion<p>Thank you for verifying this!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/144632?ContentTypeID=1Fri, 17 Aug 2018 07:34:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:81c0b83f-5e8f-45a6-8ffd-7d089ba6b9a6Sigurd<p>Hi,</p> [quote userid="73274" url="~/f/nordic-q-a/37560/is-s132-v6-0-0-use-of-timer0-affected-by-nrf52832-errata-78"] If so, does it include appropriate mitigation for nRF52832 errata #78?[/quote] <p>Yes, the SoftDevice uses the workaround&nbsp;described in&nbsp;<span>errata #78. The SoftDevice has used the workaround since S132 v.2</span></p><div style="clear:both;"></div>