sd_app_evt_wait() and hardware interrupts

RE: sd_app_evt_wait() and hardware interrupts

Jonathan — Mon, 25 May 2015 14:16:50 GMT

You are the best! Thumbs up!

RE: sd_app_evt_wait() and hardware interrupts

RK — Mon, 25 May 2015 14:14:00 GMT

added the code from bsp.c which sets up buttons ready for wakeup just before sleeping. Sense is one of the things you can set the GPIO to do, ie it senses when the level changes and causes a GPIO event which causes the chip to wake.

RE: sd_app_evt_wait() and hardware interrupts

Jonathan — Mon, 25 May 2015 14:09:26 GMT

Great advise. Could you explain in short what "sense" does mean. I knew that you could configure the inputs with sense, but couldn't find out what the difference is to no sense.

RE: sd_app_evt_wait() and hardware interrupts

RK — Mon, 25 May 2015 13:30:11 GMT

No it doesn't use a timer - not the one I'm looking at. As long as you enable the GPIO to 'sense' they will wake up the chip. That works just as well from an external source, as long as it toggles the value on a pin set to sense, the chip will wake.

Added in the code from bsp.c which sets the buttons up for sensing for wake

uint32_t bsp_wakeup_buttons_set(uint32_t wakeup_buttons)
{
#if (BUTTONS_NUMBER > 0) && !defined(BSP_SIMPLE)
    for (uint32_t i = 0; i < BUTTONS_NUMBER; i++)
    {
        uint32_t new_cnf = NRF_GPIO->PIN_CNF[m_buttons_list[i]];
        uint32_t new_sense = ((1 << i) & wakeup_buttons) ? GPIO_PIN_CNF_SENSE_Low : GPIO_PIN_CNF_SENSE_Disabled;
        new_cnf &= ~GPIO_PIN_CNF_SENSE_Msk;
        new_cnf |= (new_sense << GPIO_PIN_CNF_SENSE_Pos);
        NRF_GPIO->PIN_CNF[m_buttons_list[i]] = new_cnf;
    }
    return NRF_SUCCESS;
#else
    return NRF_ERROR_NOT_SUPPORTED;  
#endif
}