https://devzone.nordicsemi.com/f/nordic-q-a/56619/timing-behaviour-with-and-without-debugger-connectedWe have a problem that we are struggling to solve. We have written an application for the Nordic Semiconductor nRF52832 which uses a proprietory radio protocol. This protocol is based on the concept of a time frame, during which a message is passed fromen-USTelligent Community 13Fri, 17 Jan 2020 10:00:44 GMThttps://devzone.nordicsemi.com/thread/229564?ContentTypeID=1Fri, 17 Jan 2020 10:00:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:44675d6f-adf1-4d26-b8b9-b436738639c3Hung Bui<p>Hi Dave,&nbsp;<br /><br />Could you give more detail of the change in the timing ? If you can capture a logic analyzer trace showing how much off the timing it would be nice.&nbsp;</p> <p>The only reason why enabling the debugger can cause the change in the timing I can think of is that the debugger when active will keep the CPU and the HFCLK running.&nbsp;<br /><br />What do you use to keep the timing ? with the TIMER or with the RTC ? Please make sure that you initialized the clock source properly.&nbsp;<br /><br />Do you put the CPU to sleep between the communication event ?</p> <p>You can test by disable the radio activity and only keep a timer running and check if the timer timeout drift off when you disable the debugger.&nbsp;</p><div style="clear:both;"></div>