FreeRTOS tick count invalid when using tickless idle

RE: FreeRTOS tick count invalid when using tickless idle

WestCoastDaz — Fri, 28 Oct 2016 18:27:18 GMT

Aryan, we switched back to tick based mode since we were experiencing unexplained high current consumption in tickless idle see devzone.nordicsemi.com/.../

RE: FreeRTOS tick count invalid when using tickless idle

Susheel Nuguru — Thu, 27 Oct 2016 18:43:31 GMT

Darren, I know that this is late response. If you were seeing this in tickless mode Can you follow this thread and see if these fixes help you.

RE: FreeRTOS tick count invalid when using tickless idle

Radoslaw Koppel — Mon, 08 Aug 2016 12:24:20 GMT

What do you mean by missing ticks? Single ticks are lost or there is still the problem when calling xTaskGetTickCount() early after wakeup?

RE: FreeRTOS tick count invalid when using tickless idle

WestCoastDaz — Thu, 26 May 2016 04:04:58 GMT

Anders,

We are using your implementation of you posted in this thread devzone.nordicsemi.com/.../ and I am still seeing missing ticks. I reviewed some of the FreeRtos demo port implementations and they all seem to call vTaskStepDiff() unconditionally. Is there a way to debug the tick count?

Thanks

RE: FreeRTOS tick count invalid when using tickless idle

Anders Strand — Fri, 20 May 2016 13:01:36 GMT

This is now a know bug, see this thread.

RE: FreeRTOS tick count invalid when using tickless idle

Michael Dierks — Tue, 26 Apr 2016 19:03:47 GMT

Is there any further information regarding this? I am having issues with the xNextTaskUnblockTime syncing with the xTickCount. Sometimes the tickcount is jumping ahead of the unblocktime in places it seems it should not be moving, which results in odd behavior. Trying to isolate a problem when I came across this post. Just thinking it may be related.

RE: FreeRTOS tick count invalid when using tickless idle

Anders Strand — Mon, 04 Apr 2016 13:04:27 GMT

Hello.

As you say, this is caused by how the tickless mode is implemented. The issue has been reported internally, and will probably be changed in an upcoming release. Thanks for reporting this.

-Anders