Analysis of Functional Safety software facilitated

November 12, 2015 // By Christoph Hammerschmidt
Developing electronic systems that must meet functional safety requirements can be a rather demanding task. Electronic Design Automation software vendor Altium Ltd. now facilitates this endeavour by providing an integrity analysis tool that previously was only available as part of a suite.

Automotive safety integrity levels are an absolute must to guarantee safe and reliable execution of applications in the real-time environment of an automobile. Yet developers constantly struggle with the need to partition their applications and reduce the interference between software components while still maintaining the highest safety levels possible.

Having to balance the needs between transitioning from single-core to multi-core architectures while still maintaining industry-standard safety integrity levels, for example for ISO 26262 certification, is making it harder than ever to manage the software in today’s vehicles. “This is why 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,” says Harm-André Verhoef, Tasking Product Manager at Altium.

One way to achieve this goal in mixed criticality systems is to prove that low-level safety functions, like audio related applications, do not interfere with high-level safety functions, like braking systems. This so called ‘Freedom from Interference’ is not an easy goal to achieve in new multi-core architectures where more functions are being combined into one control unit.

The Tasking Integrity Checker, previously part of Altium’s Tasking VX-toolset for TriCore/AURIX, provides embedded software developers with the needed tools 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.
  1. Information about memory allocated is already included, with unique ways to identify memory write/read access.
  2. 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.
  3. 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.

Additional information: