Zephyr GPIO Interrupt

RE: Zephyr GPIO Interrupt

Andrea Verdecchia — Fri, 10 Jan 2025 08:08:56 GMT

I've the same problem. Did you solve it?

RE: Zephyr GPIO Interrupt

skim — Wed, 02 Nov 2022 22:28:26 GMT

At your code line 49:

gpio_pin_interrupt_configure_dt(&button, GPIO_INT_EDGE_BOTH);

Instead of GPIO_INT_EDGE_BOTH, try using others: e.g. GPIO_INT_EDGE_TO_ACTIVE, GPIO_INT_LEVEL_INACTIVE, or any other interrupt config flags.

You can find other interrupt config flags at Zephyr GPIO document page, under GPIO interrupt configuration flags. (GPIO-Zephyr)

RE: Zephyr GPIO Interrupt

Susheel Nuguru — Mon, 25 Jul 2022 11:56:12 GMT

I can reproduce this, but do not know why it behaves like this. I need to investigate the nrfx driver behaviour

RE: Zephyr GPIO Interrupt

akaun — Sun, 24 Jul 2022 18:42:06 GMT

OK here is log, first I press and release button, it goes to sleep. Then i press to wake up, it wakes up. Then I press and release again and you can see call back is fired twice. I added a time stamp inside callback before if statement printk("Button pressed at %" PRIu32 "\n", k_cycle_get_32());

*** Booting Zephyr OS build v3.0.99-ncs1 ***
Set up button at GPIO_0 pin 11
Button pressed at 176252
Button pressed...
Button pressed at 210136
Button released...
Preparing wake up
�*** Booting Zephyr OS build v3.0.99-ncs1 ***
Set up button at GPIO_0 pin 11
Button pressed at 246061
Button pressed...
Button pressed at 246189
Button pressed...
Button pressed at 283049
Button released...
Preparing wake up
Power down
Button pressed at 283276
Button released...
Preparing wake up
�ower down

RE: Zephyr GPIO Interrupt

Susheel Nuguru — Sun, 24 Jul 2022 17:42:25 GMT

Single press most likely is not firing the interrupt twice, it is the way you are printing the logs.

Can you add another log just after entereing button_pressed() but before the if condition and show me the logs again.

RE: Zephyr GPIO Interrupt

akaun — Fri, 22 Jul 2022 13:38:40 GMT

This is a simplified code, where in reality the button needs to be help for half a second for power down to begin. That shouldn't really solve the problem as to why the gpio callback gets fired twice on "SINGLE" press of the button and then release.

RE: Zephyr GPIO Interrupt

Susheel Nuguru — Fri, 22 Jul 2022 04:41:15 GMT

The logic in your code seems to have a bug.

static void button_pressed(const struct device *dev, struct gpio_callback *cb, uint32_t pins)
{
    if (gpio_pin_get(button.port, button.pin)) {
        printk("Button pressed...\r\n");
    } else {
        printk("Button released...\r\n");
        prepare_wake_up();
        power_down();
    }
}

Inside the button_pressed callback reading the gpio pin status after wakeup might read that the button is released if you pressed and released the button fast. Instead do something like below

static void button_interrupt(const struct device *dev,
			     struct gpio_callback *cb,
			     uint32_t pins)
{
static bool pressed = false;

	pressed = !pressed;
	printk("Button %s\n", pressed ? "pressed" : "released");

	if (pressed) {
        ...
	}
    else {
        ...
    }
    ...
}