current consumption issue in nrf52832

[Prajapati]

Dear all,

Good morning,

We are using nrf52832 as our main mcu. Our current consumption in system-off mode in custom board is around 3.2 mA which is very high and we want long battery life.

We have referred many posts and sample codes but did not get success.

My wake up pin configuration and stand by routine is as follow.

#define STAND_BY_BUTTON 5

static void gpio_init(void)
{
ret_code_t err_code;
err_code = nrf_drv_gpiote_init();
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(false); 
in_config.pull = NRF_GPIO_PIN_PULLUP;  
err_code = nrf_drv_gpiote_in_init(STAND_BY_BUTTON, &in_config, in_pin_handler);
APP_ERROR_CHECK(err_code); 
nrf_drv_gpiote_in_event_enable(STAND_BY_BUTTON, true);

}

void stand_by(void)
{
ret_code_t err_code;
NRF_SPI0->ENABLE = 0;
NRF_TWI0->ENABLE=0;
NRF_TWI1->ENABLE=0;
NRF_UART0->TASKS_STOPTX = 1;
NRF_UART0->TASKS_STOPRX = 1;
NRF_UART0->ENABLE =0;
sd_power_system_off();

}

One more question is that i am using one single button for wake up pin and for other gpio intterupt. So is it necessary to disable gpiote events before entering to system off mode.

My debug process is also not stopped after entering to system off mode.

So Kindly guide us on this.

Any help will be greatly appreciated..

Thank you.

[Einar Thorsrud]

Hi,

The nRF52832 will not actually enter system OFF mode when it is in a debug session. Instead, it will use emulated system OFF, which is essentially an eternal loop. So in this case the CPU will be active, consuming a lot of current. You should get the expected behaviour if you test without having a debugger connected.

[Prajapati]

hello  Einar Thorsrud.

Thank you for your kind response.

Currently i have doubt on ,how we can terminate the debug session before entering system off mode?

By disabling the RTT log ,will debug session be terminated?

Thank you.

[Einar Thorsrud]

Hi,

The simplest is to power cycle the board and not start a new debug session. You could event disconnect the debugger to be on the safe side. You could also disable logging in just in case, though RTT logging should not have a significant effect as long as you don't actually read it (by enabling the debug interface using for instance a RTT viewer).