FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [December 2011 Threads] uxMissedTicks should saturatePosted by David Farrell on December 7, 2011 In tasks.c uxMissedTicks should probably saturate. In the case of long delays with the scheduler suspended the "feature" of uxMissedTicks is lost.
RE: uxMissedTicks should saturatePosted by Dave on December 7, 2011 What you are saying is technically possible.
uxMissedTicks is used when the scheduler is suspended. Assuming a 100 ms tick and a 32 bit uxMissedTicks value. 0xFFFFFFFF x 100ms = 0x63ffffff9c ms, which is 13.6 years. If you suspend the scheduler for 13.6 years then you don't really need a scheduler. I don't think I will worry about that one.
RE: uxMissedTicks should saturatePosted by David Farrell on December 7, 2011 True, but I use 1ms and 49 days is not inconceivable. I do not necessarily mean 2^32 saturation. There is probably some reasonable limit as to how many ticks to unroll when the scheduler is re-enabled. I would think the system would take quite some time to unroll 2^32. Thanks for your response.
RE: uxMissedTicks should saturatePosted by Richard on December 7, 2011 I think 49 days is inconceivable if the functionality is used in the way it is intended. The scheduler should only ever be suspended for very short periods indeed. The value should never reach double digits in practical applications. You are also correct, unrolling the value takes time, and any remotely high value is going to cause problems for that reason.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|