Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

riz94107 — Sun, 02 Jul 2023 18:11:39 GMT

As I expected, the problem was in fact simple.

Setting up the device:

static const struct hakkei_power_config config = {.signal = GPIO_DT_SPEC_INST_GET(0, signal_gpios)};

static const struct hakkei_power_data data = {.str = "BLARGH"};

DEVICE_DT_INST_DEFINE(0, hakkei_power_init, NULL, &data, &config, APPLICATION, 1, NULL);

... the callback is in the "data" struct - which is marked `const`. This didn't trigger a compiler error, but apparently did get it stored in flash instead of RAM. 🤦

Changing to this:

static struct hakkei_power_data data = {.str = "BLARGH"};

made everything work! Thanks for your help.

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

riz94107 — Sat, 01 Jul 2023 00:30:45 GMT

I found the time to step through somewhat; I haven't figured it out yet, but it looks like the handler isn't actually getting set. I have no idea why just yet - Ozone is telling me some stuff is "out of scope" when I step through on the debugger for reasons I don't entirely understand, but clearly, when I step through here:

gpio_init_callback(&data->pwr_cb, button_pressed, BIT(config->signal.pin));

gpio_add_callback(config->signal.port, &data->pwr_cb);

... I don't see the "handler" field of &data->pwr_cb (which is `struct gpio_callback`) getting set (it remains 0)

So... I clearly am missing something simple. I bet it's staring me right in the face. 🙂

The fact that those are inline functions is making the debugging a bit hard.

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

riz94107 — Fri, 30 Jun 2023 21:14:42 GMT

OK, adding a breakpoint in nrfx_gpiote.c::nrfx_gpiote_irq_handler() is going to help - that's definitely triggering, and I step through the function. EVENTS_IN[7] shows "Generated" at that point.

I think at this point I just need to step through nrfx_gpiote.c::nrfx_gpiote_irq_handler() to figure out why the callback isn't being called - hopefully this gives me enough of a clue. I probably won't have time to get to it for a few days, unfortuately, but I'll reply here when I figure it out.

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

Vidar Berg — Fri, 30 Jun 2023 15:35:47 GMT

Good, you found the SVD file. However, it's strange that the same register configuration is not working in your project. Could you please check if the EVENTS_IN[6] register is being set when you toggle the input? You may also want to try placing a breakpoint in the nrfx_gpiote.c::nrfx_gpiote_irq_handler() function to see if it is invoked when the interrupt is triggered.

Besides not receiving the button callback, is your application performing other tasks as expected?

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

riz94107 — Wed, 28 Jun 2023 18:20:23 GMT

Sorry for the response delay - took me a bit to figure out I hadn't loaded the nrf52 SVD in Ozone :)

Anyway, no luck - pin configurations for the registers in question all seem to be the same in both apps:

P0->PIN_CNF[17] is 0000 0000

GPIOTE->INTENSET is 8000 0080

GPIOTE->CONFIG[7] is 0003 1101

(all other GPIOTE->CONFIG[0..6] are 0000 0000)

I'm really scratching my head at this point

RE: Help figuring out why my GPIO interrupt handler not being called - Zephyr 3.2

Vidar Berg — Tue, 27 Jun 2023 12:15:36 GMT

Hello,

Please use the peripheral viewer in Ozone to check if the GPIO (P0) and GPIOTE configurations are the same when you run the basic button sample and when you run your application. I'm not able to spot any errors in the code you posted, so I'm wondering if the input pin configuration may be overwritten by something else in your app.

Relevant registers fields:

P0->PIN_CNF[17]

GPIOTE->INTENSET

GPIOTE->CONFIG[n] (check all channels)

Thanks,

Vidar