https://devzone.nordicsemi.com/f/nordic-q-a/77585/twi-consuming-extra-current-nrf52Hello, I am working on product based on the NRF52. It has an external EEPROME wired via I2C bus (no external pullups). I see an extra 300uA ish current consumption after performing an I2C transaction. I have init the peripheral in this way: nrf_gpio_cfg_inputen-USTelligent Community 13Thu, 22 Jul 2021 15:56:42 GMThttps://devzone.nordicsemi.com/thread/321418?ContentTypeID=1Thu, 22 Jul 2021 15:56:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7bc9afc2-539a-4d30-943e-796125ce478cAndrea<p>Hi Simon,</p> <p></p> <p>Thanks, That was it!</p> <p>Cheers,</p> <p><br />Andrea</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/320708?ContentTypeID=1Mon, 19 Jul 2021 13:19:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e854076d-4b0d-43d9-a870-92ca5945332dSimonr<p>Hi</p> <p>Due to the summer vacation period we are currently understaffed, so delayed replies must be expected. I am sorry about any inconvenience this might cause.</p> <p>What nRF52 device exactly are you seeing this current consumption on exactly? This could be linked to this erratum, where the TWI peripheral isn&#39;t disabled correctly by the nrf_drv_twi_disable() function, and it stays on. If so, please <a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_89.html">check out the workaround explained in here</a>, where you can turn the TWI instance you&#39;re using off and on again by power cycling the peripheral.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>