RE: GPIOTE example how can i modify to pulse once and why dont I get time event

bjorn-spockeli — Tue, 18 Feb 2020 08:58:35 GMT

Hi Robin,

in the GPIOTE example the Timer is configured in the extended compare mode using nrfx_timer_extended_compare. The last parameter passed to nrfx_timer_extended_compare is the boolean value enable_int, which dictates if the the interrupt for the compare channel is enabled or disabled.

In the example nrfx_timer_extended_compare is called with int_enable set to false

 nrf_drv_timer_extended_compare(&timer, (nrf_timer_cc_channel_t)0, 200 * 1000UL, NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK, false);

So If you want the TIMER IRQ, i.e. timer_dummy_handler to be called on every compare event, then you just need to alter the line to

nrf_drv_timer_extended_compare(&timer, (nrf_timer_cc_channel_t)0, 200 * 1000UL, NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK, true);

In order to have the GPIO go high and then low again, you will need to have two COMPARE0 event. In the GPIOTE context, toggleing a GPIO means that it will go from low to high if the pin is low or high to low if the pin is high. Hence, the TOGGLE task of the GPIO must be triggered twice for the GPIO to go back to the initial state.

Lastly, there is no event generated when a GPIO state is set, so if you want to verify that the pin went high or low, then you need to check this in the interrupt handler of the event that triggered the Toogle task, which in this case is the TIMER IRQ handler, i.e. timer_dummy_handler.

However, the whole point with the GPIO task and event system and PPI is that you're able to trigger task without any CPU execution.

Best regards

Bjørn