Hi Support,
I am testing current consumption of NRF_TIMER1, below is my code snippets, basically, I just start timer1 task and then stop it.
int main(void) { ... nrf_timer_task_trigger(NRF_TIMER1, NRF_TIMER_TASK_START); nrf_timer_task_trigger(NRF_TIMER1, NRF_TIMER_TASK_STOP); // Enter main loop. for (;;) { idle_state_handle(); } }
After the two code lines of START/STOP added, current spikes increases, please see below capture. (GREEN is the current after adding timer1 operation)
My questions is that is this a expected behavior? I mean, the current consumption increases even though we already stop the timer and aren't using it.
Really appreciate your support.
Best,
Desmond
Hey,
Maybe the High Frequency Clock(HFCLK) is still running? The Timer may have started the clock but didn't stop it?
You can check if clock is running or not using the functions from the clock HAL.
Thank you for response. I find errata already states this issue.
https://www.nordicsemi.com/DocLib/Content/Errata/nRF52840_Rev1/latest/ERR/nRF52840/Rev1/latest/anomaly_840_78#anomaly_840_78
So I have to use TASK_SHUTDOWN instead of TASK_STOP.