How to handle GPIO interrupts while it is configures to SENSE low

RE: How to handle GPIO interrupts while it is configures to SENSE low

sachin.singh — Sat, 19 Jan 2019 05:36:18 GMT

Hi Mikhail,

You can try this :

void in_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
      if(pin == INT1)
        {
            // Function or tast to be done here ...
        }
HAL_GPIO_EXTI_Callback();
}

All the BEST

RE: How to handle GPIO interrupts while it is configures to SENSE low

Mikhail — Tue, 14 Nov 2017 13:31:42 GMT

I try to use external interrupt from pin.

Use example \examples\peripheral\pin_change_int

but doesn't work. I can't receive handler in_pin_handler()

my code:

void in_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
HAL_GPIO_EXTI_Callback();
}

static void gpio_init2(void)

{
ret_code_t err_code;

err_code = nrf_drv_gpiote_init();
APP_ERROR_CHECK(err_code);

//    nrf_drv_gpiote_out_config_t out_config = GPIOTE_CONFIG_OUT_SIMPLE(false);

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
in_config.pull = NRF_GPIO_PIN_NOPULL;

err_code = nrf_drv_gpiote_in_init(INT1, &in_config, in_pin_handler);
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(INT1, true);
}

where is my wrong?

RE: How to handle GPIO interrupts while it is configures to SENSE low

Kenneth — Fri, 29 Apr 2016 14:46:31 GMT

Hi, there are two example projects in the SDK that show usage of the gpiote module:

\examples\peripheral\pin_change_int
\examples\peripheral\gpiote

Typically you initialize the gpiote module with nrf_drv_gpiote_init(), and then for each input pin you want to generate an interrupt you add nrf_drv_gpiote_in_init(), with a parameter to the event handler that should execute on pin change.

You will notice that the gpiote driver is using the SENSE mechanism only, and not any of the IN events. Main reason for this is that the current consumption is much lower by using SENSE detect, and you are not limited to only 4 pins (there are only 4 configurable IN events).

Typically the 4 OUT tasks and 4 IN events are used to control something directly through PPI without CPU interaction. For instance one of the examples show how a compare0 event from a timer can toggle an output pin directly.