Altium adds software integrity analysis for automotive safety

November 13, 2015 // By Graham Prophet
Altium has announced software integrity analysis to provide embedded developers with effective processes to analyse their code for automotive safety integrity levels; the tool set will be made available as a stand-alone solution for safety-related code analysis in automotive applications.

The Tasking Integrity Checker is currently part of the Tasking VX-toolset for TriCore/AURIX that is available on the Tasking website.

“Having to balance the needs between transitioning from single-core to multi-core architectures while still maintaining industry-standard safety integrity levels, e.g. for ISO 26262 certification, is making it harder than ever to manage the software in today's vehicles,” said Harm-André Verhoef, Tasking Product Manager at Altium. “...we introduced the Tasking Integrity Checker to help to identify and remove safety critical interference within automotive applications in the most efficient way possible for embedded software developers.”

Developers, Altium says, constantly struggle with the need to partition their applications and reduce the interference between software components while still maintaining the highest safety levels possible. One way to achieve this goal in mixed criticality systems is to prove that low-level safety functions, such as audio related applications, do not interfere with high-level safety functions, such as braking systems. This so called “Freedom from Interference” is the goal, but not an easy one to achieve in new multi-core architectures where more functions are being combined into one control unit.

The Tasking Integrity Checker provides embedded software developers with the tools needed to accomplish this task, including:

- The ability to work at the compiler level so that developers do not have to change the source code in an application.

- Information about memory allocated is already included, with unique ways to identify memory write/read access.

- Information about the safety classes of functions are built into the application, allowing developers to easily address the implementation of safety requirements with ASIL aware static analysis.

By making the Tasking Integrity Checker available as a stand-alone application, embedded developers will be able to create safe and reliable automotive applications, regardless of what architecture they are working on.