Implement a feasibility check for task-to-hardware allocation tables
Description
- This feature shall allow task-to-hardware allocations to be checked for feasibility using a fixed set of constraints:
- Basic (Deployment)
- Memory (Flash & RAM)
- Safety (ASIL / SIL)
- Before checking, it must be ensured that the allocation is fully specified (i.e., all tasks have been assigned to an execution unit). If this is not the case, an error message shall be displayed.
Implementation
- The check can be implemented by creating instantiating a (headless) DSE with a rule set including the necessary constraints as well as an allocation constraint for each allocation table entry.
- The check can be triggered, e.g., by a new entry in the context menu of task-to-hardware allocation tables.
Testing
- Import the test project.
- Note that it contains two allocation table collections, one titles "SATISFIES", the other "VIOLATES": The former shall pass the feasibility check, the latter shall fail it.
- Also note that the FlashMemory annotations are not set in the platform architecture. The feasibility check shall be able to handle this lack of information without a failure.
Edited by Tiziano Munaro