gpio_keys: interrupt configuration failed: -134

[Tom]

I have a small demo, based on the hello world example, where I have also enabled gpio_keys. I can run this on the nRF52-DK, nRF54-DK but when I come to run it on my custom board I get the following:

[00:00:00.000,801] <err> gpio_keys: interrupt configuration failed: -134
[00:00:00.000,807] <err> gpio_keys: Pin 0 interrupt configuration failed: -134

I am having trouble working out how to address this issue. I am assuming it must be in my device tree, or defconfig, but haven't been able to isolate it any further.

Can you help me understand how I could further debug the issue?

[Hieu]

Hi Tom,

It seems that error log is only produced here: https://github.com/nrfconnect/sdk-zephyr/blob/ncs-v3.1.1/drivers/input/input_gpio_keys.c#L161.

Which ultimately should be originated from here: https://github.com/nrfconnect/sdk-zephyr/blob/ncs-v3.1.1/drivers/gpio/gpio_nrfx.c#L427-L493.

Are you using the nRF54L15? If so, could you be using a pin that doesn't support interrupt?

Refer to:
GPIO — General purpose input/output
Essential pin planning guidelines for the nRF54L Series

Hieu

[Tom]

Ah... yeah, that will be it. I hadn't spotted that in the nRF54L15 datasheet. Looking through the forum it looks like it's a fairly common oversight unfortunately.

 

Is there any way to shoehorn a different peripheral to the pin to get interrupt functionality?

[Hieu]

Unfortunately, there isn't any way to place a different peripheral in to get you a GPIO interrupt.

If you are working with a QFN package, then perhaps you can use a thin wire to short the pin with another from P0 or P1?

[Tom]

We're using a precertified module, rather than a package, but I can wire one of the interrupt lines to a test pad and run the GPIO keys inputs as polling for now.
Thanks for the help

[Hieu]

Just doing my job. I hope it works well enough for your test.