BLE Connection Sync - Uninitilize?

RE: BLE Connection Sync - Uninitilize?

Hung Bui — Mon, 28 Apr 2025 13:06:28 GMT

Hi Simon,
I was thinking the TIMER would take time to ramp up and start when the START TASK is triggered but it seems that if the oscillator already running it doesn't need that. At least it's deterministic latency. 1 or 2 clock cycles I think.

If you are testing and find it worked within your requirement then I think all good.

RE: BLE Connection Sync - Uninitilize?

SimonBursten — Mon, 28 Apr 2025 09:50:08 GMT

yes, i've taken this approach and it works. i'm able to disable and uninitialize the TIMER and EGU, and free up the ppi channels. when i need to use the sync again i reinitialize the TIMER, EGU and PPI and i'm able to sync again.

RE: BLE Connection Sync - Uninitilize?

Hung Bui — Fri, 25 Apr 2025 09:11:22 GMT

Hi Simon,

I haven't looked deep into the code of the sample but your idea is to disable TIMER and EGU and let the RTC to run. When the RTC CC event occur you will start the TIMER and the EGU to wait for the TIMER CC to match. correct ?

I am not so sure it would work because you will need to involve the CPU to set the EGU, right ? And the TIMER even though can be started with PPI (not sure if you have extra PPI for that) would need time to ramp up and start I am not so sure it would be able to give good accuracy.

Have you done any testing ?

RE: BLE Connection Sync - Uninitilize?

SimonBursten — Thu, 24 Apr 2025 12:36:25 GMT

One idea I had was to keep the RTC running but turn off the EGU and TIMER. is this a viable approach?