https://devzone.nordicsemi.com/f/nordic-q-a/62318/wakeup-interrupt-controllerHi, we are seeing subtle timing differences in code execution between when we have a debugger attached or not (same build of code). Does the nRF52832 implement the optional wakeup interrupt controller https://developer.arm.com/docs/dui0553/a/the-cortexen-USTelligent Community 13Mon, 08 Jun 2020 18:37:40 GMThttps://devzone.nordicsemi.com/thread/253886?ContentTypeID=1Mon, 08 Jun 2020 18:37:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c40a7bff-457b-4405-ad1c-0d78fa90a80aTurbo J<p>The debugger actually disables &quot;deep sleep&quot; entirely when connecting.</p> <p>Without the debugger, HFINT (or HFCLK) is stopped during sleep (WFE/WFI) and thus must be restarted before wakeup. With a debugger connected, HFINT (or HFCLK) runs all the time.</p> <p>Since Systick is fed from the HF clock, it can be used to &quot;measure&quot; how long the HF oscillator actually runs. Just configure it for 100 ints/sec, count the actual occuring interrupts and you have a &quot;usage percent&quot; value once per second. And yes, with a debugger you&#39;d get full 100ints/sec.</p><div style="clear:both;"></div>