RE: GPIO interrupt(s) not running unless connected to RTT logger

Einar Thorsrud — Fri, 09 Aug 2024 10:19:47 GMT

Hi,

Using RTT logging should not affec the scheduler in any direct way. But it can change timing etc, as you found in the second issue. This change in timing may not only be related to logging and RTT itself, but also to the debugger being attached and keeping clocks and regulators running. This may also be why you don't see the issue if you use a while loop with a short delay as that wakes the device up regularily (depending on the delay).

Is the issue also worked around by enabling constant latency mode (NRF_POWER->TASKS_CONSTLAT = 1;) but not having the loop in your main thread? I would not thing so, but it would be intersting to see.

RE: GPIO interrupt(s) not running unless connected to RTT logger

luckyyorange — Wed, 07 Aug 2024 16:16:31 GMT

Occasion 2 has been resolved. Occasion 2 was relying on a delay from the RTT logger being open and had been indeed correctly running the GPIO ISR and work submission the whole time. Apologies for any misleading as I had very little ability to debug because of limited use of the logger in this scenario.

However, still looking into occasion 1. After learning the resolution for occasion 2, I may be left to believe that occasion 1 may be due to needing a delay as well rather than a ISR or scheduling not running