Are IN events on the nrf5340 effectively usable?

[bearsh]

Hi

I'd like to use a gpiote in event to trigger a capture task of a timer (rtc timer). Now I realized that according to errata 153 in event may not always work. The suggested workaround is to either use the port event or disable low power mode. Both options are AFAIK not feasible because I also need other gpios as interrupts und the application should really be low power.

Am I right with my conclusion that in events are not really usable on the nrf5340? Or does task triggering still work in system on idle but it does not trigger a 'wakeup'?

[Susheel Nuguru]

I think there is a small misunderstanding here. The LATENCY register is only relevant for the GPIOTE peripheral and making the LATENCY=LowPower does not make the whole SoC into high power consumption mode, it only increases the power for GPIOTE peripheral. So yes, if you want to use GPIOTE peripheral for the in events, you can only use it with either PORT events or if you want high accuracy events, then with a bit of increased power consumption for the GPIOTE IN events with Latency=LowLatency. This is a limitation we have now with this chip.

[bearsh]

Thanks for your answer

Yes I know about the two latency option. I was only talking about the latency register of the gpiote peripheral.

Susheel Nuguru said:

then with a bit of increased power consumption for the GPIOTE IN events with Latency=LowLatency

if the application is designed to run at about 30uA, then this is more than just a bit... fortunately I know the time the event is expected to happen and so I can set LowLatency only for that small time window.