MUTEX: Interrupts and Mutex
Tasks run normally, the first execution of the task just takes the mutex semaphore, prints the parameter function of each task and gives the mutex. When the button is pressed, an ISR is
Tasks run normally, the first execution of the task just takes the mutex semaphore, prints the parameter function of each task and gives the mutex. When the button is pressed, an ISR is
Observe in the timeline the execution of Task, put attention to the start time of the "Task_LP", the task take the mutex blocking a part of the code, after a
At the init, Tasks are executed. Notice that first Task 1 is executed taking the mutex 1, after, Task 2 is executed to take the mutex 2. Tasks are now in block state
Embedded real-time systems have to take actions in response to events that originate from the environment. Non-trivial systems will have to service events that originate from multiple sources, all of which will have
A software timer (or just a 'timer') allows a function to be executed at a set time in the future. The function executed by the timer is called the timer’s