Power Consumption rises after I2C data transfer

RE: Power Consumption rises after I2C data transfer

Simonr — Wed, 10 Feb 2021 08:32:16 GMT

As the erratum states, only yhe TWIM should be affected by this current consumption issue. The TWI driver should not have this issue.

Best regards,

Simon

RE: Power Consumption rises after I2C data transfer

WJ-tech — Tue, 09 Feb 2021 09:14:28 GMT

Thanks. I will try this. I also wonder if i use the twi driver rather than the twim driver, the current consumption will still rising ?

RE: Power Consumption rises after I2C data transfer

Simonr — Tue, 09 Feb 2021 06:25:03 GMT

This seems to be the erratum 89 that is causing this excess current consumption, as the workaround has not been implemented in Zephyr, but rather in our nRFConnect SDK. After TWIM is finished operating it's necessary to power cycle the peripheral to disable it correctly. We recommend doing a full uninitializing of the module through Zephyr before you power cycle it though.

There is also a workaround that won't require a power cycling of the peripheral which enables TWIS for a short amount of time before enabling TWIM again.

temp = NRF_TWIMx->ENABLE 
NRF_TWIMx->ENABLE = 9 
NRF_TWIMx->ENABLE = temp

The official workaround should be sufficient as well which is described in the erratum link I provided at top.

Best regards,

Simon