Multiple GPIO interrupts

RE: Multiple GPIO interrupts

Jared — Mon, 13 Nov 2023 14:03:18 GMT

I see,

Thank you for sharing the solution!

Have a good day,

best regards

Jared

RE: Multiple GPIO interrupts

AndyM — Mon, 13 Nov 2023 13:55:30 GMT

Hi Jared

There were 2 bugs

1. The GPIO pin mask was wrong. It included the pin that the button is connected to. That caused the accelerometer interrupt callback to fire on button touch. That code is shared above an you suggested to check the value of the mask passed to gpio_init_callback() . When I did I realized that the mask was wrong and fixed it.

2. The second bug is in the code that configures the accelerometer by writing various values to its registers. It enabled the interrupt correctly but the next line of code disabled it by mistake.

Thank you so much for help!

RE: Multiple GPIO interrupts

Jared — Mon, 13 Nov 2023 09:25:51 GMT

HI,

What was the bug?

Was it related to any of the code that you've already shared?

regards
Jared

RE: Multiple GPIO interrupts

AndyM — Fri, 10 Nov 2023 18:15:31 GMT

Update

Turns there was a bug in my code that did not properly configure the part to generate interrupts. With that fixed the GPIO interrupt works perfectly. Thanks a lot for help!

RE: Multiple GPIO interrupts

Jared — Fri, 10 Nov 2023 14:33:15 GMT

[quote user="AndyM"]I believe this is done to avoid the limitation of 8 gpiote channels in the NRF52[/quote]

You might be into something here, what happens if you disable the other button interrupts completely by removing all code related to it. Both in the dts and main.c file. Only include the interrupt for the accelerometer.

This whole issue is a bit strange as setting up an interrupt for a button or an external slave should be exactly the same, effectively you should be able to replace the connection of one of the buttons to the pin with the accelerometer and see that it triggers the same interrupt.

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Thu, 09 Nov 2023 23:15:19 GMT

Jared

I checked the spec - by default the INT1 pin polarity is active-high

Also my gpio nodes are configured with sense-edge-mask i.e

&gpio0 {

status = "okay";

sense-edge-mask = <0xffffffff>;

};

I believe this is done to avoid the limitation of 8 gpiote channels in the NRF52

Not sure it matters, it does not work without that property either. Thought I'd bring it up just in case

Thank you

RE: Multiple GPIO interrupts

AndyM — Thu, 09 Nov 2023 19:07:24 GMT

Yes, in the code gpio_pin_interrupt_configure_dt is called before gpio_init_callback

Unfortunately did not work

Waiting on the results of the hardware analysis, will keep you posted

Anything else worth trying in the meantime?

Thank you

RE: Multiple GPIO interrupts

Jared — Thu, 09 Nov 2023 15:46:52 GMT

Hi,

[quote user="AndyM"]Did I miss anything?[/quote]

That looks correct, were you able to verify if the interrupt line is toggled by the slave and if so in what direction?

Another suggestion, can you try to move the gpio_pin_interrupt_configure_dt() call before gpio_init_callback() and see if that changes anything? Also try using

GPIO_INT_EDGE_TO_ACTIVE instead of GPIO_INT_LEVEL_ACTIVE as well.

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Wed, 08 Nov 2023 14:51:40 GMT

Jared, just to clarify, I made the following changes but it did not make a difference

acc_int1: acc_int1 {

gpios = <&gpio0 14 GPIO_ACTIVE_LOW>;

};

gpio_pin_configure_dt(&_int1_dt_spec, GPIO_INPUT|GPIO_ACTIVE_LOW);

gpio_pin_interrupt_configure_dt(&_int1_dt_spec,GPIO_INT_LEVEL_INACTIVE);

I also tried GPIO_INT_EDGE_TO_ACTIVE when configuring the interrupt - no luck

Did I miss anything?

Thank you

RE: Multiple GPIO interrupts

Jared — Wed, 08 Nov 2023 14:27:32 GMT

[quote user="AndyM"]I put in a request but it's out of my hands,l hopefully later this week.[/quote]

Got it,

[quote user="AndyM"]

GPIO_INPUT|GPIO_ACTIVE_HIGH so I expected to see a 1

Is my expectation correct?

[/quote]

If by this you mean that you configure the pin as GPIO_ACTIVE_HIGH in the dts and as an INPUT in the application with for example gpio_pin_configure_dt() then that is OK. But you still need to configure what interrupt that should trigger the callback handler which you have already done in gpio_pin_interrupt_configure_dt().

I therefore wonder, does the accelerometer pull the signal to a logical 1 or a logical 0 when it enables the interrupt? Have you tried switching it to a GPIO_ACTIVE_LOW and see if that fixes the issue?

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Tue, 07 Nov 2023 19:08:09 GMT

[quote userid="73165" url="~/f/nordic-q-a/105392/multiple-gpio-interrupts/454531"]Can you double check it by probing the interrupt line either with an oscilloscope or logic analyzer and confirm that the pin is asserted by the accelerometer? [/quote]

I put in a request but it's out of my hands,l hopefully later this week.

One peculiar thing is that gpio_pin_get_dt() always returns 0 but the pin is configured as

GPIO_INPUT|GPIO_ACTIVE_HIGH so I expected to see a 1

Is my expectation correct? And if it is wouldn't this point to hardware?

Thanks

RE: Multiple GPIO interrupts

Jared — Tue, 07 Nov 2023 15:30:31 GMT

[quote user="AndyM"]Your hunch was correct. I was including a header which redefined the BIT macro so the pin used for the button was added to the pin mask for the accelerometer interrupt and that' caused the accelerometer gpio callback to be called on a button press. I fixed that and now the button press works fine and does not trigger the accelerometer gpio callback. .Thank you![/quote]

Good,

[quote user="AndyM"]However the accelerometer interrup callback still is not called on a movement event, as expected. I'm certain that the part generates the interrupt - if I poll the control register of the accelerometer in a loop I see the interrupt bit set when the event occurs. I tried using GPIO_INT_EDGE_TO_ACTIVE and GPIO_INT_LEVEL_ACTIVE flags in gpio_pin_interrupt_configure_dt() function - makes no difference[/quote]

Can you double check it by probing the interrupt line either with an oscilloscope or logic analyzer and confirm that the pin is asserted by the accelerometer?

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Tue, 07 Nov 2023 15:22:55 GMT

Jared

Your hunch was correct. I was including a header which redefined the BIT macro so the pin used for the button was added to the pin mask for the accelerometer interrupt and that' caused the accelerometer gpio callback to be called on a button press. I fixed that and now the button press works fine and does not trigger the accelerometer gpio callback. .Thank you!

However the accelerometer interrup callback still is not called on a movement event, as expected. I'm certain that the part generates the interrupt - if I poll the control register of the accelerometer in a loop I see the interrupt bit set when the event occurs. I tried using GPIO_INT_EDGE_TO_ACTIVE and GPIO_INT_LEVEL_ACTIVE flags in gpio_pin_interrupt_configure_dt() function - makes no difference

Any ideas ?

RE: Multiple GPIO interrupts

Jared — Tue, 07 Nov 2023 13:46:34 GMT

Hi Andy,

Can you set a breakpoint at line : gpio_init_callback(&_gpio_int1_cb,gpio_int1_callback, BIT(_int1_dt_spec.pin));

And see what the third parameter BIT(_int1_dt_spec.pin) is when you run the program with the debugger?

Can you share a screenshot of the variable from debug view?

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Mon, 06 Nov 2023 13:58:18 GMT

[quote userid="73165" url="~/f/nordic-q-a/105392/multiple-gpio-interrupts/454219"]Just to be clear, are you saying that _gpio_int1_cb() is called when you press the GPIO button, but it's not called when accint1 is toggled by the accelerometer? [/quote]

Yes, that's the behavior I see

RE: Multiple GPIO interrupts

Jared — Mon, 06 Nov 2023 13:37:19 GMT

Hi,

Just to be clear, are you saying that _gpio_int1_cb() is called when you press the GPIO button, but it's not called when accint1 is toggled by the accelerometer?

[quote user="AndyM"]Question, Is it OK for the accelerometer int1 pin to be under "gpio-keys" binding? The documentation says this is for buttons[/quote]

Yes, this should be fine,

regards

Jared

RE: Multiple GPIO interrupts

AndyM — Sun, 05 Nov 2023 23:17:10 GMT

Question, Is it OK for the accelerometer int1 pin to be under "gpio-keys" binding? The documentation says this is for buttons

If no - what binding should be under ?

Thanks