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,

[Edvin]

Hello,

What happens when you try to disable the gpiote? What worked in the older SDKs? Disabling GPIOTE while still receiving interrupts from other peripherals?

What was the current consumption in the old application, and what is the current consumption in the new one? Apart from enabling GPIOTE, are there any other changes to the application?

Do you have an application showing that it doesn't work in the new SDKs?

Best regards,

Edvin

[Christopher]

This is all rather strange to me too. In the older SDK everything works just fine and all GPIOs interrupt correctly as the should. When I build the code, I reviewed the DTS files and observed I have GPIOTE disabled in all child images (e.g. mcuboot, b0, b0n, application, network). However, I am unable to disable the GPIOTEs in my child images and thus I am assuming that is the reason why I have about a ~200uA increase in current consumption.

I need to take a step back and just do a simple test with a single GPIO input trigger. I can then compare the two SDKs to ensure it isn't another peripheral running. 

I should also point out I am using the nRF5340DK board files.

Thank you,

[Christopher]

Would you be able to show me an example of how to configure a GPIOTE interrupt which will consume the least amount of current on a nRF53? I cannot seem to get it work properly. 

Thank you,

[Edvin]

Hello Christopher,

This ticket is getting quite old, so I am not sure what your current status is. What do you observe when setting up the GPIOTE interrupt?

Does it work?

What is your current consumption?

What is your expected current consumption?

Best regards,

Edvin

[Christopher]

So, after investigating a little further. It appears like it was a new configuration required for using the NFC pins on the nRF53. I needed to add the following to my .dts file. 

&uicr {

nfct-pins-as-gpios;

};

My assumption was this was always triggering a read of my ADC which was causing some extra current draw.

Thank you for the assistance. We can close this now.