Whats the alternative to GPIOTE In Event ?

RE: Whats the alternative to GPIOTE In Event ?

Roger Clark — Thu, 12 Jan 2017 09:22:44 GMT

Thanks

Setting the argument to false solved the problem

RE: Whats the alternative to GPIOTE In Event ?

Vidar Berg — Thu, 12 Jan 2017 07:56:31 GMT

The button module used in our Bluetooth examples uses PORT events to detect button press. The implementation is quite abstracted, and I think it is easier to follow the instructions given in the driver documentation to enable it. Just make sure to set .hi_accuracy to false in the nrf_drv_gpiote_in_config_t structure used for initialization:

nrf_drv_gpiote_in_config_t config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(false);

RE: Whats the alternative to GPIOTE In Event ?

Roger Clark — Thu, 12 Jan 2017 07:38:05 GMT

Thanks Vidar

Are there any official examples of how to use the PORT method?

As far as I could see the documentation only has code for the "IN event".

I think someone posted a question about the PORT method which included their own code, but I hoped these would be official documentation / example code for how to use the PORT method, as I think its completely different from the IN event method (isnt it ?)

RE: Whats the alternative to GPIOTE In Event ?

Vidar Berg — Thu, 12 Jan 2017 07:29:05 GMT

IN events requires the HF clock to be held active, hence the higher current consumption. The difference between PORT and IN events are explained in the driver documentation here.