Periodic thread isBestEffort
RTOS for Secure, Safe and Real-Time Systems
Brought to you by:
rtospharos
In some cases, the periodic thread does not meet the period. That is, a job of a thread may take longer than its period. The current Pharos behavior is to trigger a health handler (even if the thread does not have a deadline).
In this ticket it is proposed for periodic threads to have a "isBestEffort" boolean flag which, if set to TRUE (the default is FALSE), the health handler will not be invoked and the thread will just be rescheduled to awake at the next release instant (release + N*period)
Anonymous
Implemented in threadperiodic.c:
Tested in Test3200.