gpiote interrupt cannot wake sd_app_evt_wait?

RE: gpiote interrupt cannot wake sd_app_evt_wait?

Haruki Kawakami — Mon, 21 Aug 2017 14:01:50 GMT

I tried volatile, and it works well!! Still it is strange why __WFE() works well without volatile. I cannot understand compiler behavior. Can you explain? Anyway, thank you for your answer!

RE: gpiote interrupt cannot wake sd_app_evt_wait?

Turbo J — Mon, 21 Aug 2017 13:13:24 GMT

You forgot the C optimizer:

volatile int s_is_resp_ready;

Without the volatile, the optimizer will replace the

while(!s_is_resp_ready)

with an unconditional loop. Look at the disassembly if you can.

RE: gpiote interrupt cannot wake sd_app_evt_wait?

ovrebekk — Mon, 21 Aug 2017 11:10:55 GMT

Hi Haruki

I tested the code with the ble_app_uart example, and I had no issues getting the GPIOTE interrupt to work, also when using sd_app_evt_wait().

I made some minor changes to the code, to use the button 4 input for testing, but otherwise it is pretty much the same:

static void sf_gpiote_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    printf("gpiote interrupt\r\n");
     //s_is_resp_ready = true;
}


static void gpiote_init()
{
     /* config interrupt */
    nrf_drv_gpiote_in_config_t config = GPIOTE_CONFIG_IN_SENSE_HITOLO(false);
    config.pull = NRF_GPIO_PIN_PULLUP;

    if(!nrf_drv_gpiote_is_init())
        nrf_drv_gpiote_init();

    nrf_drv_gpiote_in_init(BSP_BUTTON_3, &config, sf_gpiote_handler);
    nrf_drv_gpiote_in_event_enable(BSP_BUTTON_3, true);
}

If the log is delayed it could be because you are using the log library in deferred mode? In this mode the printing will be delayed until NRF_LOG_PROCESS() is called.

Do you have a scope available?
Then you could try to toggle an output pin in the interrupt instead, and look on the scope if the pin is toggled after the input changes.

Best regards
Torbjørn

RE: gpiote interrupt cannot wake sd_app_evt_wait?

Haruki Kawakami — Wed, 16 Aug 2017 01:20:41 GMT

code is like below.

    /* config interrupt */
    nrf_drv_gpiote_in_config_t config = GPIOTE_CONFIG_IN_SENSE_HITOLO(false);

    if(!nrf_drv_gpiote_is_init())
        nrf_drv_gpiote_init();

    nrf_drv_gpiote_in_init(INT_N, &config, sf_gpiote_handler);
    nrf_drv_gpiote_in_event_enable(INT_N, true);

is this collect?

RE: gpiote interrupt cannot wake sd_app_evt_wait?

ovrebekk — Fri, 04 Aug 2017 09:02:06 GMT

Can you show me the code used to initialize the GPIOTE channel?

sd_app_evt_wait() is using WFE under the hood, so there shouldn't be a big difference between the two, except sd_app_evt_wait() is running the recommended sleep sequence:

__WFE();
__SEV();
__WFE();

If you only run __WFE(); once then you might not go to sleep at all, if there is already an event pending.

Best regards