GPIO IN_EVENT to GPIO PORT Event

RE: GPIO IN_EVENT to GPIO PORT Event

Enzo — Wed, 23 May 2018 02:44:02 GMT

sure

RE: GPIO IN_EVENT to GPIO PORT Event

Sigurd — Tue, 22 May 2018 10:42:47 GMT

Hi Enzo,

Please create a new question/ticket for your issue:

https://devzone.nordicsemi.com/support/add

RE: GPIO IN_EVENT to GPIO PORT Event

Enzo — Tue, 22 May 2018 01:59:16 GMT

Hi,

I use custom 51822 board with sdk 12.3 and running nrf_nus sevice. I use port event to start uart peripheral so can lower power consumption. could you tell me the Exact power consumption of port event. When i measure current consumption it will be different when connect the configed port event pin to usb to ttl module or dsconnect it. i can't get it

RE: GPIO IN_EVENT to GPIO PORT Event

michael — Tue, 03 Oct 2017 07:07:52 GMT

Thank you. This change is working :-)

RE: GPIO IN_EVENT to GPIO PORT Event

Sigurd — Wed, 27 Sep 2017 17:17:47 GMT

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.

You could try to use the GPIOTE_CONFIG_IN_SENSE_TOGGLE() instead.

RE: GPIO IN_EVENT to GPIO PORT Event

michael — Tue, 26 Sep 2017 14:36:38 GMT

First function is the one mentioned in the initial question. It's also called first. Next three init functions are following:

void init_gpio_acc()
{
  ret_code_t err_code;
  nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
  in_config.pull = NRF_GPIO_PIN_NOPULL;
  
  err_code = nrf_drv_gpiote_in_init(GPIO_AINT1, &in_config, pin_handler);
  APP_ERROR_CHECK(err_code);
  nrf_drv_gpiote_in_event_enable(GPIO_AINT1, false);  
}

void int_gpio_gyro()
{
  ret_code_t err_code;
  nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
  in_config.pull = NRF_GPIO_PIN_NOPULL;
  
  err_code = nrf_drv_gpiote_in_init(GPIO_GINT1, &in_config, pin_handler);
  APP_ERROR_CHECK(err_code);
  nrf_drv_gpiote_in_event_enable(GPIO_GINT1, false);
}

void int_gpio_comm()
{
  ret_code_t err_code;
  nrf_drv_gpiote_in_config_t dio0 = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);
  dio0.pull = NRF_GPIO_PIN_NOPULL;
  
  nrf_drv_gpiote_in_uninit(GPIO_DIO0);
  err_code = nrf_drv_gpiote_in_init(GPIO_DIO0, &dio0, dio_handler_isr);
  APP_ERROR_CHECK(err_code);
  nrf_drv_gpiote_in_event_enable(GPIO_DIO0, true);
}

If I use .hi_accuracy set to true the functionality is fine. When I change it to false I receive just one interrupt and that's all.

Thank you for comment.

RE: GPIO IN_EVENT to GPIO PORT Event

Sigurd — Tue, 26 Sep 2017 09:24:27 GMT

You should not need to clear any interrupt flag yourself, the GPIOTE driver should take care of that for you.

Could you post your init_gpio_button() function where you use 4 inputs GPIOs ?

RE: GPIO IN_EVENT to GPIO PORT Event

michael — Mon, 25 Sep 2017 10:51:01 GMT

Thank you I will have a look on the post.

I have one more question. In case I have more than one input GPIOs, how the interrupt handling must be changed? In our implementation we have 4 input GPIOs and if change .hi_accuracy to false for all four GPIOs after I receive first interrupt, I don't receive any else. Do I need to clear any interrupt flag?

Thank you very much.

RE: GPIO IN_EVENT to GPIO PORT Event

Sigurd — Mon, 25 Sep 2017 09:05:26 GMT

PS: If you need to decrease power consumption, take a look at this post.

RE: GPIO IN_EVENT to GPIO PORT Event

Sigurd — Mon, 25 Sep 2017 09:01:05 GMT

Hi,

Yes, if you set the .hi_accuracy flag to true, then the GPIOTE will use IN event(consumes more current), but if you set the flag to false, the GPIOTE will use the PORT event (low accuracy mode, uses less current.) You don't need to configure anything more than that, the GPIOTE driver takes care of the rest.