What's the delay from setting the Start / Stop task in an RTC module to when the RTC actually starts or stops? Is it less than 1 clock cycle on the CPU (15ns)? More than one clock cycle?
What's the delay from setting the Start / Stop task in an RTC module to when the RTC actually starts or stops? Is it less than 1 clock cycle on the CPU (15ns)? More than one clock cycle?
If the LFCLK is already running and RTC is already configured, then it will be just one clock cycle to start by TASKS_START or to stop it by by TASKS_STOP.
That's 1 HFCLK cycle, correct?
yes, you are right .. that was why we were able to generate 8Mhz clock using Timers, GPIO and PPI setup to prove that the tasks take just one hfclk cycle. This will be no different for RTC.
Hence the lack of "EVENTS_STARTED" and "EVENTS_STOPPED" for the RTC... that should have been a clue to me there...