The “chatterbox”- application basically consists of 3 instances of the “chatterbox”-task. Every time the chatterbox-task is executed, it outputs a string (in this exercise the string is simply printed to the console output). The behavior of a task instance is defined at its creation by two values: a) the output string and an integer flag which can have either value 0 (infinite task instance executions) or 1 (task instance shall only be executed 5 times)
Emulating the behavior of a frame-based scheduler in FreeRTOS for the frame list
The scenario consists of the following components:
- There are three producer tasks (one for Sensor 1, one for Sensor 2A and one for Sensor 2B) which put sensor values into messages queues.
- There is one message queue per sensor task and each sensor task writes its sensor values only into its assigned queue.
- Also there are two consumer tasks which can take sensor values from messages queues (one for Controller 1 and one for Controller 2) and then proceed to do some computation with the sensor values.
