GPIOTE driver/peripheral power consumption

RE: GPIOTE driver/peripheral power consumption

markopa — Fri, 12 Oct 2018 12:02:16 GMT

Ok, I've been able to figure it out. After I exit the nrf_pwr_mgmt_run() function I check the status of my wake-up pin manually by checking the NRF_GPIO->IN register. If the wake-up reason is asserted I just trigger other actions.

I'm measuring a CPU consumption on 2.3uA which is oscillating to 6~7uA upon a RTC tick. I'm fine with that.

RE: GPIOTE driver/peripheral power consumption

markopa — Fri, 12 Oct 2018 10:34:44 GMT

"Uninit" output pins makes no sense if they don't maintain the state as a pin change will trigger other parts of the board that will in turn consume more power. I'm sorry I can't even try this.

Instead, I've tried to nrf_drv_gpiote_in_uninit() the two input pins and this drops the CPU consumption to ~2uA+.

That being said is there an SDK api or a register which I can check to distinguish if the CPU was waken up by RTC or by the GPIO ?

RE: GPIOTE driver/peripheral power consumption

Edvin — Fri, 12 Oct 2018 09:35:05 GMT

Sorry, I was a bit quick on the trigger.

The pins will not maintain the state while they are disabled, but they will be remembered until you init them again, since the state is written in a different register.

If you need to keep them in a certain state while you are in system ON, this will draw some current. That is how electronics work.

But to check whether that is actually the part drawing current here, can you check whether the current consumption drops if you try to uninit the pins before going to sleep?

Try to use the nrf_drv_gpiote_in_uninit() on the pins that are used for output pins.

BR,

Edvin

RE: GPIOTE driver/peripheral power consumption

Edvin — Fri, 12 Oct 2018 09:19:16 GMT

It is probably the output pins that draw the current. Can you try to disable them?

BR,

Edvin

RE: GPIOTE driver/peripheral power consumption

markopa — Fri, 12 Oct 2018 09:07:40 GMT

Hi, thanks for your input.

I have other pins configured as well. I have some output pins which are not actively being used. They are used at startup to enable other devices on the board. Does disabling the pins preserve their output state?

As for input pins I have two and they are configured as follows:

static nrf_drv_gpiote_in_config_t irq1_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
irq1_config.pull = NRF_GPIO_PIN_NOPULL;
APP_ERROR_CHECK(nrf_drv_gpiote_in_init(LIS2DH_IRQ1, &irq1_config, irq1_handler)); 

static nrf_drv_gpiote_in_config_t irq2_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(true);
irq2_config.pull = NRF_GPIO_PIN_NOPULL;
APP_ERROR_CHECK(nrf_drv_gpiote_in_init(LIS2DH_IRQ2, &irq2_config, irq2_handler)); 
				
nrf_drv_gpiote_in_event_enable(LIS2DH_IRQ1, true);	
nrf_drv_gpiote_in_event_enable(LIS2DH_IRQ2, true);	
				
nrf_gpio_cfg_sense_input(LIS2DH_IRQ2, NRF_GPIO_PIN_NOPULL/*NRF_GPIO_PIN_PULLUP*/, NRF_GPIO_PIN_SENSE_LOW);

IRQ1 pin is used as a regular IRQ and I can disable it when going into "system ON" sleep and later enable i only prior I need it.

As fro IRQ2 that one is used as a wake-up and as shut-down as well. I can reconfigure even that one to uses it just as a sense pin for wakeup without having the irq handler functionality. I just need to find a way to know why I was waken up. Was this the RTC (1 second) event or was it the IRQ2 pin? Any hints there like reading a status register or similar?

RE: GPIOTE driver/peripheral power consumption

Edvin — Fri, 12 Oct 2018 08:50:54 GMT

And what pin do you use as wakeup pin? Is it P0.09 or P0.10? Or any of the others?

RE: GPIOTE driver/peripheral power consumption

Edvin — Fri, 12 Oct 2018 08:49:25 GMT

Hello,

Do you have any other GPIOs configured than the one used for wakeup? And how have you configured that pin? obviously as an input, but how is the rest of the configuration?

If there are any others, especially if any are used as output pins, you should disable these pins before going to "System ON" mode.

Best regards,

Edvin