The receive interrupt handler and the timer interrupt
handler only determine whether the condition for transmitting the stored data is satisfied.
Therefore, the firmware of the node was based on the implementation of the timer interrupts
assuring execution of a certain event at a given frequency in the defined time intervals.
Modified Implementation Based On the Employment of "Sandwich Delay" and "Multiple Timer Interrupts
--interrupt_clock_resolution(): gives the expected minimal resolution (in Hz) at which the facility can schedule events and equals the frequency of the system's periodic timer interrupt
, which is used to "back up" soft timers.
In both preemptive and cooperative mode, the scheduler operates as a periodical timer interrupt
Each time when counter counts to upper limit, it starts timer interrupt
The implementation of periodic task is based on the timer interrupt
and the principle of the scheduling is the same using in non periodic task scheduler.
The possible sCPUi events are: timer interrupts
(TEvi), watchdog timer (WDEvi), two interrupts used for preventive signaling of the deadline (D1Evi and D2Evi), attached interrupts (IntEvi), mutexes used for handling shared resources (MutexEvi), synchronization and inter-task communication events between sCPUi (SynEvi), self-sustaining execution information for the current sCPUi (lr_run_sCPUi).