always automatic wakeup after entering SYSTEM OFF mode

RE: always automatic wakeup after entering SYSTEM OFF mode

yoyou — Sat, 30 Oct 2021 01:15:56 GMT

thank you very much,According to your guidance，The problem is solved。as follows：

App:

#define _BT_PIN_NUMBER NRF_GPIO_PIN_MAP(1,1)

static void sleep_mode_enter(void)
{
indication_set(BSP_INDICATE_IDLE);
APP_ERROR_CHECK(err_code);
nrf_gpio_cfg_sense_input(_BT_PIN_NUMBER,BUTTON_PULL,NRF_GPIO_PIN_SENSE_LOW);
// nrf_gpio_cfg_sense_set(_BT_PIN_NUMBER, GPIO_PIN_CNF_SENSE_Low);
err_code = sd_power_system_off();
APP_ERROR_CHECK(err_code);
}

bootloader：

#define NRF_BL_DFU_ENTER_METHOD_BUTTON 0

Thanks for your help

RE: always automatic wakeup after entering SYSTEM OFF mode

Einar Thorsrud — Fri, 29 Oct 2021 13:16:23 GMT

Hi,

There is a potential problem with the bootloader. If you built the bootloader with NRF_BL_DFU_ENTER_METHOD_BUTTON set to 1, then the pin you have specified with NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN is configured as an input with sense like this:

    nrf_gpio_cfg_sense_input(NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN,
                             BUTTON_PULL,
                             NRF_GPIO_PIN_SENSE_LOW);

Unfortunately the bootloader does revert this configuration back to the default values before starting the application, so this will still be active when the application starts. If you use the same pin as wakeup source in your application as you use to signal that the bootloader should enter DFU mode that is OK, but if not, this can cause problems as you suddenly have a wakeup source you were not aware of.

If this is the problem you could fix this by modifying the bootloader either by simply setting NRF_BL_DFU_ENTER_METHOD_BUTTON to 0 if it is not needed, or alternatively call nrf_gpio_cfg_default(NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN); for instance in the end of dfu_enter_check() in components\libraries\bootloader\nrf_bootloader.c.

RE: always automatic wakeup after entering SYSTEM OFF mode

yoyou — Fri, 29 Oct 2021 09:20:42 GMT

nrf_gpio_cfg_sense_set(_BT_PIN_NUMBER, GPIO_PIN_CNF_SENSE_Low);

err_code = sd_power_system_off();
APP_ERROR_CHECK(err_code);

S140 SDK17 52840, only one button that connect to P1.1.

when no bootloader everything's fine.

app+bootloader ,always automatic wakeup after entering SYSTEM OFF mode.

Does anyone know how to solve it？

Thanks for your help

RE: always automatic wakeup after entering SYSTEM OFF mode

Einar Thorsrud — Tue, 19 Oct 2021 06:43:13 GMT

Hi,

[quote user="Yuank"]sd_power_system_off() and NRF_POWER->SYSTEMOFF = 1, I guess it's not emulated off?[/quote]

As long as you are not debugging, then both these methods will enter system OFF mode.

[quote user="Yuank"]I'm not sure about WDT, if it's not set by default, I have no code for that.[/quote]

Then you are not using the WDT.

[quote user="Yuank"]everything is fine, no auto reset and wake up on button, RESETREAS shows wakeup on GPIO DETECT[/quote]

Ah, I see. I did not think to ask what you did in configure_gpio_wakeup(), but that is interesting. The call to nrf_gpio_cfg_sense_set() is also done by bsp_wakeup_button_enable(), but this does not clear the latch state of that pin. If for some reason there is a latched interrupt this will cause problems without it. I cannot see why this is, though.

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Mon, 18 Oct 2021 23:27:17 GMT

The sum up is right.

The custom pcb runs separately and the DK is used to receive the BLE data and show it on DC serial port, is that considered as debugging mode? And I tried both sd_power_system_off() and NRF_POWER->SYSTEMOFF = 1, I guess it's not emulated off? I'm not sure about WDT, if it's not set by default, I have no code for that.

As I mentioned below, if I use

void configure_gpio_wakeup(uint32_t pin_number, nrf_gpio_pin_sense_t sense)

{

nrf_gpio_pin_latch_clear(pin_number);

nrf_gpio_cfg_watcher(pin_number);

nrf_gpio_cfg_sense_set(pin_number, sense);

}

configure_gpio_wakeup(BUTTON_5, NRF_GPIO_PIN_SENSE_LOW);

everything is fine, no auto reset and wake up on button, RESETREAS shows wakeup on GPIO DETECT

RE: always automatic wakeup after entering SYSTEM OFF mode

Einar Thorsrud — Mon, 18 Oct 2021 08:48:16 GMT

Hi,

I don't see anything obviously wrong here. Just to sum up:

The device always wakes up after 4-5 seconds in system off, but only if you have called bsp_wakeup_button_enable(BUTTON_5); before entering system OFF.
And you cannot wake up before this from system of by pressing the button.
If wakeup button was not configured, device stays in system off forever.

Is that correct?

I noticed another thing from one of your earlier posts. There you wrote that "RESETREAS register always shows reset by soft reset". That is not expected. You should see that it had woken up from system-off mode. Could it be that you are not testing system off mode, but rather emulated system off? Do you have a debugger attached when doing this test? I ask because system off does not work while debugging.

Other questions: have you tested that this button works as expected when not using it to wake up from system off mode, so that the HW is good? Do you have a WDT running? If yes, have you tested without it?

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Fri, 15 Oct 2021 18:12:18 GMT

Still can't get why "bsp_wakeup_button_enable(BUTTON_5);" will cause the auto wakeup, but if I use "configure_gpio_wakeup(BUTTON_5, NRF_GPIO_PIN_SENSE_LOW);", everything's fine.

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Fri, 15 Oct 2021 16:50:05 GMT

It's already pullup in bsp.c when I #define BSP_BUTTON_4 BUTTON_5

And during the 4-5 seconds before it automatic wakeup, the button doesn't work(won't wakeup the chip on press) and after the wakeup, pressing the button will enter the bsp_event

Following is all the code about this button

// in pca10040.h
#define BUTTONS_NUMBER 5   //4------>5
#define BUTTON_5  NRF_GPIO_PIN_MAP(0,24)
#define BUTTONS_LIST { BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4, BUTTON_5 }
#define BSP_BUTTON_4   BUTTON_5

// in sdk_config.h
#define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS 5   //4--->5

// in bsp.c
#ifdef BSP_BUTTON_4
    {BSP_BUTTON_4, false, BUTTON_PULL, bsp_button_event_handler},
    #endif
    
// in main.c
// in bsp_event_handler
case BSP_EVENT_KEY_4:  //BUTTON_5
            sprintf(bletext,"button_pcb detected\r\n");BLE_TEXT(bletext);
            break;
// in ble_nus_event_handler
case 29:  // SYSTEM OFF mode
            nrf_delay_ms(500);
            sprintf(bletext,"SYSTEM OFF......\r\n"); BLE_TEXT(bletext);
            sprintf(bletext,"SYSTEM OFF......\r\n"); BLE_TEXT(bletext);
            sprintf(bletext,"SYSTEM OFF......\r\n"); BLE_TEXT(bletext);
            nrf_delay_ms(500);

            err_code = bsp_wakeup_button_enable(BUTTON_5);
            APP_ERROR_CHECK(err_code);
                                 
            nrf_delay_ms(500);
            /*err_code = sd_power_system_off();
            APP_ERROR_CHECK(err_code);*/
            NRF_POWER->SYSTEMOFF = 1;

RE: always automatic wakeup after entering SYSTEM OFF mode

Einar Thorsrud — Fri, 15 Oct 2021 16:38:41 GMT

Hi,

Is it so that pin 29 is connected to ground when pushed, and that you do not have a pull-up? If so it will be floating when the button is not pressed, so yes, you need a pull-up. Note that there are internal pull resistors for every GPIO, so there is no need for an external pull-up - just enable the internal pull-up.

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Fri, 15 Oct 2021 16:31:45 GMT

It's connected to PIN29 (p0.24) using #define BUTTON_5 NRF_GPIO_PIN_MAP(0,24). On HW it connects PIN29 and GND (already pullup in bsp.c, and active_state = 0)

I have a bsp event for that button and I only enter that event when I press the button, is that enough to prove that it's not floating

Thanks for your help

RE: always automatic wakeup after entering SYSTEM OFF mode

Einar Thorsrud — Fri, 15 Oct 2021 09:41:25 GMT

Which pin does BUTTON_5 map to in your code? And how is this pin connected on your HW? When you configure that as an input and as a wakeup source, a change on the state of that pin can wake up the device. If that is controlled by something else and/or is floating, you will not have any control over what happens. Generally it is essential to have control over your inputs and to ensure that you hever have floating digital inputs.

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Fri, 15 Oct 2021 01:09:15 GMT

The system will stay in OFF mode if I comment out

err_code = bsp_wakeup_button_enable(BUTTON_5);
APP_ERROR_CHECK(err_code);

We use a custom PCB and there's no bsp_buttons on it, but we have a button connected to P0.24, and I added it in pca10040.h and sdk_config.h as following:

// in pca10040.h
#define BUTTONS_NUMBER 5   //4------>5
#define BUTTON_5  NRF_GPIO_PIN_MAP(0,24)
#define BUTTONS_LIST { BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4, BUTTON_5 }

// in sdk_config.h
#define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS 5   //4--->5

And in main bsp_event_handler, we do enter the case BSP_EVENT_KEY_4 when the button is pressed, so I guess it should work the same as those buttons on the DK. But after I set that button for wakeup as "bsp_wakeup_button_enable(BUTTON_5);", it will automatically wakeup without being pressed, what might be wrong?

RE: always automatic wakeup after entering SYSTEM OFF mode

Yuank — Fri, 15 Oct 2021 00:10:28 GMT

Actually automatic restart after 4-5 seconds. I'm not sure if anything else (timers etc.)wakes it up, but the RESETREAS register always shows reset by soft reset. Did I set it to OFF mode correctly or is there anything else I need to set other than sd_power_system_off() or NRF_POWER->SYSTEMOFF = 1? If it really entered the OFF mode, what can trigger a soft reset?