Error: nrfx_gpiote_input_configure() failed, errCode=0xbad0002

[snowuyl]

The first calling nrfx_gpiote_input_configure() in afe4900.c is successful. But the second calling nrfx_gpiote_input_configure() in button.c is failed. 

What is meaning of errCode=0xbad0002? How can I fix this issue?

00> *** Booting Zephyr OS build v3.2.99-ncs2 ***

00> Starting button Test example
00> configure AFE4900_RDY pin as input
00> configure AFE4900_RESET pin as output
00> configure POWER_UP pin as output
00> configure LED_G pin as output
00> set POWER_UP pin
00> clear AFE4900_RESET pin, 0
00> set AFE4900_RESET pin
00> I2C: Device is ready.
00> 0x39 0x35 0x50
00> Starting button Test example
00> device_is_ready() ok
00> btInit() e
00> bt_passkey_set(123456)
00> _btReady(0) e
00> Bluetooth initialized
00> _btReady(0) x
00> btInit() x
00> device_is_ready() ok
00> Error: nrfx_gpiote_input_configure() failed for button, errCode=0xbad0002

[Jared]

Hi,

I have some questions:

1. Can you specify which line and in what file it asserts when you call nrfx_gpiote_input_configure() for the second time? Use the debugger and take a screenshot of the call stack when it asserts. Can you share this screenshot?
2. If you change the pins that you use, does it still return this error?
3. It looks like you're getting NRFX_ERROR_NO_MEM, which indicates that there isn't any GPIOTE channels left for you to use. 

regards

Jared 

[snowuyl]

1. line number 117 of button.c. I don't use debugger and I just use printk() to print error message.

2. It still return this error.

3. Why I got NRFX_ERROR_NO_MEM error with CONFIG_DEBUG=y but no NRFX_ERROR_NO_MEM error with CONFIG_DEBUG=n?   The source code are same for CONFIG_DEBUG=y and CONFIG_DEBUG=n.

[Jared]

Hi,

I'm able to reproduce the issue, and it seems that setting CONFIG_NRFX_GPIOTE_NUM_OF_EVT_HANDLERS to more than 1 in the prj.conf should mitigate the issue, even with CONFIG_DEBUG=y.

I'm not quite sure exactly how but setting CONFIG_DEBUG=y will disable optimization which results in NRFX_ERROR_NO_MEM.

Have you been able to reproduce it using the normal nRF52832 board not your custom nRF52832 board file?,

regards

Jared 

[snowuyl]

Thanks for your reply! I have not used normal nRF52832 board.

[Jared]

Ok, did the workaround fix the issue for you?

snowuyl said:

I have not used normal nRF52832 board.

But if you use the normal nRF52832 board file and not your custom, are you able to reproduce the issue?

regards

Jared

[snowuyl]

I am sorry that I don't have normal nRF52832 board so I don't use normal nRF52832 board file.

[Jared]

Ok, but did the workaround fix the issue for you?