https://devzone.nordicsemi.com/f/nordic-q-a/124276/timer-problemsCurrently, only the NRF5340 chip on the NRF5340 development board is powered. Now, we need to first test the Bluetooth performance of this chip. Open a standard example project in VSCODE, which is located in the directory: nrf\samples\bluetooth\peripheral_uarten-USTelligent Community 13Wed, 10 Sep 2025 07:23:32 GMThttps://devzone.nordicsemi.com/thread/548314?ContentTypeID=1Wed, 10 Sep 2025 07:23:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e458742f-3eeb-4d94-8a18-d58f99817479HHJ<p>thanks bro</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/548301?ContentTypeID=1Wed, 10 Sep 2025 04:41:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9136753d-a477-42d3-89dd-915461da4e2aTurbo J<p>The timer handler function runs in interrupt context, which does not allow <strong>a lot</strong> of things (mostly stuff that can&nbsp;<em>wait).</em></p> <p>Workaround with system work queue is in the timer documentation itself:<a href="https://docs.zephyrproject.org/latest/kernel/services/timing/timers.html#using-a-timer-expiry-function">Timer expiry function docs</a>. There are other methods but a work queue is by far the simplest.</p><div style="clear:both;"></div>