| ??? 02/07/05 22:20 Read: times |
#86832 - Timing a Task Responding to: ???'s previous message |
Erik Malund said:
False statement in prev post:
A time triggered sheduler only runs one task per tick so this situation never occurs unlike interupt driven systems where you have no control over when things happen. because If a task that has to "complete in less than one tick time" has 47 if statements testing flags etc set by external evants, how are you to guarantee that the "task completes in less than one tick time". For example my thingy here that run with a powerful processor and a URTOS that has no such restrictions, test several random events (a simple example "key received") in many tasks. These tasks has a very large "completion time" variance. I assume there are not 247 responses to these 47 flags else it would rather hard fitting into an 8051. If a limited subset of values of these 47 flags each requires a different piece of code to run then it is easy to time each one and determine the worst case time. Ian |
