https://devzone.nordicsemi.com/f/nordic-q-a/22627/timer-1-and-ble-softdevice-interferingHi, To decrease the load on the system I would like to periodically send some BT data (and do some SD card writing). Since Timer 0 is used by the soft device, I am using Timer 1 as follows: const nrf_drv_timer_t timer = NRF_DRV_TIMER_INSTANCEen-USTelligent Community 13Thu, 01 Mar 2018 11:12:39 GMThttps://devzone.nordicsemi.com/thread/122436?ContentTypeID=1Thu, 01 Mar 2018 11:12:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1c902255-8302-4f34-b45c-e10dde6f9dc7Pepijn<p>I just saw I didn&#39;t close this ticket, although the issue has been resolved. However, I&#39;m not sure what the exact cause was, I believe it was because I did &quot;very&quot; time consuming actions, such as writing/read to and from an SD card. This wouldn&#39;t be completed before the next timer callback, leading to strange behavior.<br /><br />I solved it by only setting flags in the onTimer callback, such as &quot;_action_write = true&quot;. In the main() loop I checked whether this flag was set, performed the action there, and cleared the flag. Now I&#39;m also sure I&#39;m not trying to write to the same file at the same time (which would happen if the onTimer callbacks overlapped in duration time).</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/89008?ContentTypeID=1Fri, 09 Jun 2017 12:23:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b6e93d09-9d4b-43ff-a910-cd6da2a7dd9aFormerMember<p>When TIMER1 starts to behave strange, could you use <code>nrf_drv_timer_capture()</code> to capture the timer value?</p><div style="clear:both;"></div>