Interrupt from two input pins for the same handler

[Nell]

Hi everyone,

I am trying to use the Port interrupts on the nRF52840. I started from the example "pin-change-int" and it works fine when I use one input pin.

But when I try to get my callback from 2 input pins, with 2 interrupts, only one of the 2 handled. In my application I want to use the PORT interrupt, not the IN_EVENT, so using “low accuracy” mode.

I also tried with the high accuracy mode, just to see if it worked, and the management of the 2 inputs worked fine.

Also, I did set the #define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS in sdk_config.h from to 2 (or even higher).

You will find my code below, if any of you has an idea, that would be wonderful.

 

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

static void gpio_init(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);
    err_code = nrf_drv_gpiote_out_init(GPIO_OUT_PIN, &out_config);
    APP_ERROR_CHECK(err_code);
        
    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);

    err_code = nrf_drv_gpiote_in_init(GPIO_IN_PIN, &in_config, in_pin_handler);
    APP_ERROR_CHECK(err_code);
        
    err_code = nrf_drv_gpiote_in_init(GPIO_IN_PIN2, &in_config, in_pin_handler);
    APP_ERROR_CHECK(err_code);

    nrf_drv_gpiote_in_event_enable(GPIO_IN_PIN, true);
    nrf_drv_gpiote_in_event_enable(GPIO_IN_PIN2, true);
}

Thank you

[haakonsh]

You need to read the IN registers to check for what pin or pins have changed state in the event handler. If both port events happen at the same time or close together they will register as one event. Only when the EVENTS_PORT has been cleared by the GPIOTE driver can it fire another interrupt. 

If you used both Port0 and Port1 you will have to read both port's IN registers.

[Nell]

hello and thank you already for your help.

In my application, no matter which pin is changing state, the task executed is the same.
On the other hand, I added the EVENTS_PORT registry reset but it does not work.
Would there be errors in the configuration of my entries?

[Nell]

ok... sorry

so  : GPIO_IN_PIN is P0.13 and GPIO_IN_PIN2 is P1.00

[haakonsh]

Try using the NRF_GPIO_PIN_MAP macro when using port1 for configuring pins. 

What is the exact value of GPIO_IN_PIN2?

Also, what is the value of the GPIO and GPIOTE registers after you've configured the pins?

[Nell]

Hello,

I modified my configuration like this :

#define GPIO_IN_PIN    NRF_GPIO_PIN_MAP(0,13)
#define GPIO_IN_PIN2   NRF_GPIO_PIN_MAP(1,00)

At the end onf my system initialisation, registers are  :

And only the interrupt on GPIO_IN_PIN2 works well!

[haakonsh]

Are you using the DK by any chance? 
If so, see Connector interface for available GPIOs.

[Nell]

No, I developed my own board

[haakonsh]

Does it work if you only use p0.13?

Can you scope GPIO_OUT_PIN, GPIO_IN_PIN, and GPIO_IN_PIN2 with a logic analyzer when you're triggering the pins?

[Nell]

Does it work if you only use p0.13? : YES

[haakonsh]

Hmm. 
I suggest you change:
void in_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    nrf_drv_gpiote_out_set(GPIO_OUT_PIN);
}

to 
void in_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    nrf_gpio_pin_toggle(GPIO_OUT_PIN);
}

And then scope the three signals.

[Nell]

In first time, I made a few measurements on a scope and I realized that I was making a mistake from the beginning:
in fact, IN_PIN is well active at the high level but IN_PIN2 is active at the low level. My output switches when IN_PIN2 resumes its idle level.
anyway, my output does not switch on the state change of IN_PIN.

In a second time, i tried your suggest and now, only IN_PIN works.
I don't understand what's happen...

I will try to finish my application without sleep mode in my module - so in high accuracy....
If you have others ideas, I take...

[haakonsh]

Nell said:

In a second time, i tried your suggest and now, only IN_PIN works.
I don't understand what's happen...

 Can you show me the scope?