Can't configure 2 gpio pins with opposite pull state

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Mon, 21 Sep 2020 08:39:14 GMT

Great, I am happy to hear that the application now works as intended!

[quote user="Serhio"]Thank you for your help.[/quote]

It is no problem at all, Serhio! I am happy to help.

Please do not hesitate to open a new ticket if you should encounter any issues or questions in the future.

Best regards,
Karl

RE: Can't configure 2 gpio pins with opposite pull state

Serhio — Sun, 20 Sep 2020 12:33:11 GMT

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/269293"]Is the application now working as you had intended?[/quote]

Yes, Karl, I'm satisfied how the application works now. Thank you for your help.

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Mon, 14 Sep 2020 07:32:02 GMT

Hello,

[quote user="Serhio"]I`m very sorry for my late reply. I was on vacation.[/quote]

No worries at all, I hope you had a great vacation!

[quote user="Serhio"]NRF52832_xxAA_REV2, SoftDevice S132 v5.0.0[/quote]

Thank you for letting me know.

[quote user="Serhio"]I tried. And it works![/quote][quote user="Serhio"]I use GPIOTE_CONFIG_IN_SENSE_TOGGLE only for one button and now... works both buttons..[/quote]

I am glad to hear that! Then I would think the problem was caused due to the PORT event already being generated when the second one came in.
Is the application now working as you had intended?
If you are using TOGGLE on both, you can keep track of which direction it has transitioned since the last event.

Best regards,
Karl

RE: Can't configure 2 gpio pins with opposite pull state

Serhio — Sat, 12 Sep 2020 15:29:41 GMT

Hello! I`m very sorry for my late reply. I was on vacation.

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/266241"]So, what you are saying is that both GPIOs in questions are connected with a button, sensing a change in the level, correct?[/quote]

Yes

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/266241"]What was the results of these trails, were you able to confirm the callback behavior using the LED?[/quote]

Yes, the LED state did not change

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/266241"]Which SoC version and variant are you working with?[/quote]

NRF52832_xxAA_REV2, SoftDevice S132 v5.0.0

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/266650"]Could you also try to use GPIOTE_CONFIG_IN_SENSE_TOGGLE() instead of _LOTOHI for your buttons?[/quote]

I tried. And it works! Code:

{    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(false);
    in_config.pull = NRF_GPIO_PIN_PULLUP;
    err_code = nrf_drv_gpiote_in_init(PIN_BUTTON, &in_config, button_handler);
    APP_ERROR_CHECK(err_code);
    nrf_drv_gpiote_in_event_enable(PIN_BUTTON, true);}/**/


    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
    in_config.pull = NRF_GPIO_PIN_PULLDOWN;
    err_code = nrf_drv_gpiote_in_init(PIN_IMPULSE, &in_config, impulse_handler);
    APP_ERROR_CHECK(err_code);
    nrf_drv_gpiote_in_event_enable(PIN_IMPULSE, true);

I use GPIOTE_CONFIG_IN_SENSE_TOGGLE only for one button and now... works both buttons..

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/266241"]Could you share with me a stripped down project in which you are seeing this behavior?
I will then attempt to replicate the behavior on my end, so that I may better debug it.[/quote]

For reproduce issue, just use code from my first message. And connect one button to "+" and other to "-"

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Thu, 27 Aug 2020 08:36:38 GMT

Hello again,

Could you also try to use GPIOTE_CONFIG_IN_SENSE_TOGGLE() instead of _LOTOHI for your buttons?

I believe that if a port event is triggered on a low to high transition on a pin, a new port event can’t be triggered before that pin has gone low again or the pin is configured to sense low (which will trigger a new event on high to low transition). See the answers to this and this post.

The results of this test will also tell us more about what might be causing the unexpected behavior you are seeing.

Best regards,
Karl

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Tue, 25 Aug 2020 13:02:11 GMT

Hello again,

I am terribly sorry for the late reply.

[quote user="Serhio"]For testing purposes, I`m connecting it with a plus. Thus, it is like a button. In release, a phototransistor will be connected there.[/quote]

Thank you for clarifying. So, what you are saying is that both GPIOs in questions are connected with a button, sensing a change in the level, correct?

[quote user="Serhio"]I like your holistic approach) I've tried using nrf_gpio_pin_toggle(PIN_LED)[/quote]

Great! What was the results of these trails, were you able to confirm the callback behavior using the LED?

[quote user="Serhio"]I am aware of this define. But thank you for not forgetting about that. It`s equal 4[/quote]

Thank you for verifying this. It is indeed quickly overlooked, and so I just had to make sure this was not the case right now.

[quote user="Serhio"]Now for the good news. As you suggested. I setup pin with hi-accuracy is true and now it works.[/quote]

That is good news indeed!

[quote user="Serhio"]But does this cause increased power consumption? The device under development is powered by a CR2032 battery and the issue of power consumption is very important.[/quote]

Yes, high-accuracy GPIOTE IN_EVENTS does increase power consumption compared to the low-accuracy PORT event. The GPIOTE IN will enable the HFCLK source to run when a edge is triggered, then start sampling using the HFCLK.
There is also some Erratas present for the GPIOTE on the nRF52832. Which SoC version and variant are you working with?

[quote user="Serhio"]Thus, low-accuracy don't work for pins with opposite pull state?[/quote]

I have never heard of this behavior before, and neither has my colleagues that I have conferred with. I would not expect this either.

Could you share with me a stripped down project in which you are seeing this behavior?
I will then attempt to replicate the behavior on my end, so that I may better debug it.

Looking forward to getting to the bottom of this!

Best regards,
Karl

RE: Can't configure 2 gpio pins with opposite pull state

Serhio — Wed, 19 Aug 2020 19:31:46 GMT

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/265255"]Could you also tell me what this pin is connected to?[/quote]

For testing purposes, I`m connecting it with a plus. Thus, it is like a button. In release, a phototransistor will be connected there.

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/265255"]Instead, I would suggest using a LED or sending a message to verify that you have entered into one of the callbacks.[/quote]

I like your holistic approach) I've tried using nrf_gpio_pin_toggle(PIN_LED)

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/265255"]Could you tell me what your GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS is defined as in your sdk_config?[/quote]

I am aware of this define. But thank you for not forgetting about that. It`s equal 4

[quote userid="87869" url="~/f/nordic-q-a/64839/can-t-configure-2-gpio-pins-with-opposite-pull-state/265255"]Furthermore, I would alert you to the difference between PORT event and IN_EVENT, since you are currently using low-accuracy configuration which means that both pins will generate the same PORT event, as opposed to high-accuracy configuration which has a dedicated IN_EVENT per pin.[/quote]

Now for the good news. As you suggested. I setup pin with hi-accuracy is true and now it works.

But does this cause increased power consumption? The device under development is powered by a CR2032 battery and the issue of power consumption is very important.

Thus, low-accuracy don't work for pins with opposite pull state?

Thanks for your answers.

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Wed, 19 Aug 2020 09:05:50 GMT

Hello,

Sorry for my late reply.

Thank you for clarifying.

[quote user="Serhio"]PIN_IMPULSE - 9 (I use CONFIG_NFCT_PINS_AS_GPIOS define)[/quote]

Could you also tell me what this pin is connected to?

[quote user="Serhio"]callback called(log is displayed).[/quote]

Are you using deferred logging, by the way?
If you are, it is not a definite way to see the flow of your program using logs, since they will be written only when the CPU have no other task.
Instead, I would suggest using a LED or sending a message to verify that you have entered into one of the callbacks.

[quote user="Serhio"]

And then use nrf_gpio_pin_read(PIN_BUTTON)

But that doesn't suit me..

[/quote]

No, I would not recommend this, this is far from ideal.
I see now that you are configuring both your inputs as low-accuracy.
Could you tell me what your GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS is defined as in your sdk_config? I suspect it might be set to 1, in which case you should try increasing it to 2. Please try this, and let me know if this resolves your issue.

Furthermore, I would alert you to the difference between PORT event and IN_EVENT, since you are currently using low-accuracy configuration which means that both pins will generate the same PORT event, as opposed to high-accuracy configuration which has a dedicated IN_EVENT per pin.

Looking forward to resolving this issue together,

Best regards,
Karl

RE: Can't configure 2 gpio pins with opposite pull state

Serhio — Mon, 17 Aug 2020 21:35:28 GMT

In same time, I can use this code:

    nrf_gpio_cfg_input(PIN_BUTTON, NRF_GPIO_PIN_PULLUP);

    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
    in_config.pull = NRF_GPIO_PIN_PULLDOWN;
    err_code = nrf_drv_gpiote_in_init(PIN_IMPULSE, &in_config, impulse_handler);
    APP_ERROR_CHECK(err_code);
    nrf_drv_gpiote_in_event_enable(PIN_IMPULSE, true);

And then use nrf_gpio_pin_read(PIN_BUTTON)

But that doesn't suit me..

RE: Can't configure 2 gpio pins with opposite pull state

Serhio — Mon, 17 Aug 2020 21:30:50 GMT

Hello, Karl!

Callback code, for example:

void button_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
   NRF_LOG_INFO("button_handler %d %d", pin, action);
   nrf_gpio_pin_toggle(PIN_LED);
}

void impulse_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
   NRF_LOG_INFO("impulse_handler %d %d", pin, action);
}

If I configure 1(any) gpio pin then corresponding callback called(log is displayed).

PIN_BUTTON - 25

PIN_IMPULSE - 9 (I use CONFIG_NFCT_PINS_AS_GPIOS define)

I use custom board:

RE: Can't configure 2 gpio pins with opposite pull state

Karl Ylvisaker — Mon, 17 Aug 2020 08:01:58 GMT

Hello,

That sounds strange.
Could you detail your issue some more:

[quote user=""]But, callback don`t called.[/quote]

How are you testing this, and how does it behave differently than expected? I just want to make sure that I have understood you correctly.
Could you also share the callback code, which is / is not being called?

[quote user=""]Why is this occurs? How to set up pins with diffrent pull state?[/quote]

Which pins on the nRF52832 are you using, and what are they connected to?
Are you working with a nRF52 DK, or a custom board?

Looking forward to resolving this issue together!

Best regards,
Karl