Unable to disable GPIOTE for nRF Connect SDK 2.6.1

[Christopher]

Hi, 

Recently I upgraded to nRF Connect SDK 2.6.1 and I was required to enable the GPIOTE in order to build properly. Doing this has significantly increased (nearly doubled) the total current consumption at runtime. How can I disable this peripheral now? I am unable to do so now using the overlay file.

Old: 

&gpiote {
    status = "disabled";
};

New:

&gpiote {
    status = "okay";
};

Thank you,

[Susheel Nuguru]

Christopher, Sorry for delayed response.

Have you done this power measurements on the DK aswell? And also what was your power measurement of your app on the older version of the SDK?

Christopher said:

but I am still drawing a lot more current (396uA vs. 199uA).

So you were expecting 199uA but getting 396uA on newer SDK or is it same on the older SDK?

[Christopher]

This project is on a custom board design so it might not run on an DK.

On the previous SDK (v2.4.2) I was reading 199uA. On the newer SDK (v2.6.1) I am getting 396uA. Both were measured with the same PPK2. I have tried the above suggestions, but the current consumption is still at 396uA. 

[Simonr]

Hi Christopher

Susheel asked me if I could take over this case, and indeed it seems like something is drawing a lot of power on your external board. In my opinion 199µA on the older SDK is also a bit high if your application is just doing GPIOTE, so I'm guessing your application does something else as well. 

First off, to try and achieve the same power consumption on NCS v2.6.1, can you go through the migration guides for NCS v2.5.0 and v2.6.0 to make sure you've made all the necessary changes to your project in order to make it running as it should on v2.6.1?

Next, if you use Visual Studio Code and the nRF Connect extensions for development, you can use the nRF DeviceTree visual editor to see what pins and peripherals exactly are enabled in your project and check for any discrepancies between the NCS 2.4.2 and 2.6.1 versions of your project.

Best regards,

Simon