RE: GPIOTE IRQ loss when too fast....how to use latch?

lbe — Fri, 14 Feb 2020 14:51:19 GMT

Hello Hakon, thanks for your answer.

I am using nrfx_gpiote and SDK 15.0, but it turned out that the problem I had was not related to the latch but to an error somewhere else in the code (wrong timings).

Thanks in any case for your suggestions.

RE: GPIOTE IRQ loss when too fast....how to use latch?

Håkon Alseth — Wed, 12 Feb 2020 14:38:18 GMT

Hi,

Are you using nrfx_gpiote or nrf_gpiote? Which SDK are you using?

nrfx_gpiote.c was recently updated with LATCH support:

https://github.com/NordicSemiconductor/nrfx/blob/master/drivers/src/nrfx_gpiote.c#L655

I suspect the easiest way is to update to the latest nrfx version, unless you want to use a GPIOTE IN channel instead (by setting .hi_accuracy = true in your nrf_drv_gpiote_in_config_t my_button variable).

This is how you update nrfx to v2.1 in SDK v16:

1. Go to sdk_16\modules and rename "nrfx" to "nrfx_old"

2. Clone the repo (https://github.com/NordicSemiconductor/nrfx) to the same directory

3. The API introduced a interrupt level as an input to nrfx_gpiote_init, where you have to pass a interrupt level (between 0 and 7) to the init, for instance: nrf_drv_gpiote_init(APP_IRQ_PRIORITY_LOWEST);

Kind regards,

Håkon