Tasking in Germany has launched its third generation of its static software analysis tool focused on proving Freedom from Interference (FFI).
Safety Checker v3.00 improves usability with a new graphical user interface (GUI) and simplifies the process of ensuring functional safety for automotive software projects.
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 and thus enables 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, for example for performance reasons.
- Tasking buys iSystem to create German end-to-end tool supplier
- New CTO at Tasking looks to Rust and RISC-V
- Tasking’s VX-Toolset sees TÜV safety certifications
Also in MPU-based system, the tool supports software developers by generating a list of memory violations and reducing tedious debugging. It also monitors compliance with guidelines such as MISRA-C or CERT-C.
The tool is compiler and hardware architecture independent and can be integrated into Continuous Integration Build environments such as Jenkins.
The new GUI provides the ability to define security classes and access rights and assign files/functions to security classes while the ability to import AUTOSAR configuration files (.arxml) makes it easy to create configuration files and keep them synchronized 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.
The Tasking Safety Checker v3.0 is available immediately.
Leave a comment