Increased Current Consumption after GPIO Interrupt

RE: Increased Current Consumption after GPIO Interrupt

Christian Braun — Fri, 20 Dec 2024 20:28:48 GMT

Hi Håkon. You are correct, data is being aliased due to the sampling rate in the previous recordings. Attached are a .ppk2 file of the recording of a test similar to those above at 100kS/s, as well as a screenshot showing the transition period before and after the interrupt event at approximately 22.7s.

No debounce is being applied to the manually triggered interrupt. The ~2mA current spikes for ~0.2s after the interrupt can be attributed to this as a GPIO attached to a level shifter with pullups is being driven to observe and confirm the interrupt is triggered. The ~1.5s period current spikes are another processor on the board waking up periodically. I also wrapped the nrf_pwr_mgmt_run() call in main() with a GPIO toggle to observe wake events, and did not observe a difference before and after the interrupt event.

devzone.nordicsemi.com/.../ppk2_2D00_20241220T201045.ppk2

RE: Increased Current Consumption after GPIO Interrupt

Håkon Alseth — Thu, 19 Dec 2024 08:34:52 GMT

Hi,

If I read your graphs correctly, you are going from approx. 20 uA -> 60 uA after the interrupt has occurred.

pin is configured with PORT, with emulated edge triggering, but you are also seeing similar behavior when using "hi_accuracy" (ie. GPIOTE.IN).

What is the sampling rate of your current profile? I fear that aliasing is causing the current consumption curve to be smoothed out, so that we loose potential wake-up events. Do you have access to a PPK2 or similar which has a higher sampling rate?

Kind regards,

Håkon

RE: Increased Current Consumption after GPIO Interrupt

Christian Braun — Wed, 18 Dec 2024 20:26:03 GMT

Thank you for your input. We are aware of Errata 89 and have implemented the fix per the documentation. In the tests above, the TWI peripheral was still enabled and I2C interactions occurred outside the interrupt service.

We disabled the TWI peripheral in the sdk_config.h file and commented out the instantiation and relevant application code. Additionally, BLE advertising and other pieces of proprietary application code were disabled to limit other possible interactions. Unfortunately the increase in current consumption after the interrupt event is still present even under these conditions.

RE: Increased Current Consumption after GPIO Interrupt

hmolesworth — Tue, 17 Dec 2024 00:32:47 GMT

We once hit a similar issue in SDK 15 related to Errata 89 "GPIOTE: Static 400 μA current while using GPIOTE" so the question is even though no TWI transactions occur within the interrupt does the TWI still get initialised or used at all outside the interrupt? If so maybe try not initialising TWI for the port pin test.