Automotive ECUs integrate multiple functions with different safety requirements in the same package. The TASKING Safety Checker ensures Freedom from Interference to support safety argumentation according to ISO 26262. Through statistical code analysis based on compiler technology, the Safety Checker detects critical memory violations so enabling the integration of software components with different safety requirements in a memory area, even if no MPU (Memory Protection Unit) is available or the MPU cannot be used, e.g., for performance reasons.
Also, in MPU-based systems, Safety Checker supports software developers by generating a list of memory violations and reducing tedious debugging.
In addition, the Safety Checker monitors compliance with guidelines such as MISRA-C or CERT-C. The Safety Checker is compiler and hardware architecture independent and can be integrated into Continuous Integration Build environments such as Jenkins.
Some significant new features in the third version of Safety Checker include:
- A new graphical user interface that improves usability and provides the ability to define security classes and access rights and assign files/functions to security classes.
- The ability to import AUTOSAR configuration files (.arxml) makes it simpler to create configuration files and keep them synchronised with the ECU project.
- Reports can now be generated in HTML, XML or PDF format and include information such as the access violation log, function call graph, MISRA/CERT C violations and code metrics.
