![]() |
AVR SD Safety Framework 1.0.0
|
Contains Tasks that implement high-level logic, decision-making and error handling. More...
Topics | |
| Task Defines | |
| Defines types and macro constants used by Tasks. | |
| Error Handler | |
| Contains API prototypes for the Error Handler. | |
| Tasks Config | |
| Defines and declares configurations for Tasks. | |
| Interrupt Tasks | |
| Contains API prototypes for Interrupt Tasks. | |
| Pre-startup Tasks | |
| Contains API prototypes for Pre-startup Tasks. | |
| Scheduler Tasks | |
| Contains API prototypes for Scheduler Tasks. | |
| Shared Tasks | |
| Contains API prototypes for Tasks shared between several Task Managers. | |
| Shutdown Tasks | |
| Contains API prototypes for Shutdown Tasks. | |
| Startup Tasks | |
| Contains API prototypes for Startup Tasks. | |
Contains Tasks that implement high-level logic, decision-making and error handling.
The Safety Framework is fundamentally a Task-based Software Architecture. The Task Layer encompass the core functionalities and safety-related features of the Safety Framework. Tasks are the 'what' of the Application, focusing on high-level logic and decision-making. They are responsible for orchestrating the sequence of operations and executing the high-level objectives and safety-related operations of the Application.
Tasks, as decision-makers, are responsible for identifying and addressing errors within their operational domain, leveraging their contextual knowledge to make informed decisions. Middleware, while capable of detecting errors, lacks the broader context for decision-making and thus, serves mainly as a reporter of issues back to the Tasks, which will invoke the Error Handler. For this reason, the more specialized and central Error Handler is included in this layer.
The Task Layer is intended to be expanded upon by adding application-specific Tasks for Safety and Non-safety related application requirements, including application-specific Error IDs.