issue about gpio_nrfx_pin_configurationl() function of NCS

[Hannibalhz]

Dear Nordic Engineers

I encounter a issue about gpiote channel() function of NCS 2.0.0.

I use gpio_nrfx_pin_configurationl() to judg gpiote channel is be occupied.

It return the relative pin number not is the absolute pin number.

for example: I would like get the P1.05 working states, it return 5, not is 37.

[SwRa]

Hello,

I would like get the P1.05 working states, it return 5, not is 3

This is how it usually works.. You could perhaps try parsing it through nrf_gpio.h helper functions.. You could try using NRF_GPIO_PIN_MAP: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfx/drivers/gpio/hal.html#c.NRF_GPIO_PIN_MAP'

Best Regards,

Swathy

[Hannibalhz]

Dear Swathy

Sorry, maybe my description has some problems.

I encountered a problem when I use gpio_nrfx_pin_configurationl() to judge the gpiote channel to be occupied.

For example P1.05 is be occupied, the gpio_nrfx_pin_configurationl() returns relative pin number 5, not the absolute pin number 37.

Then my program starts initializing GPIO, and the initialization function will use this pin number.

So, it will free P0.05, not P1.05.​ It will cause other GPIO appear issues.

I would like the gpio_nrfx_pin_configurationl() function to return the absolute pin number.

Please give me some good suggestions.

Best regards,

[SwRa]

Hi wang,

Sorry for the delayed response.. There is indeed a bug as you mentioned.. It has been fixed and the bugfix will be included in thenext nRF Connect SDK release, v2.1.0, that will be released in a couple of days.. The fix can be found here: https://github.com/nrfconnect/sdk-zephyr/commit/4b3fe99b83e393777dedc4200c7209fcdf31a77f

Best Regards,

Swathy