Subscribe to Safety Checker
November 2016
Nov 10, 2016Gerard Vink
Safety standard ISO 26262 specifies that freedom from interference between software elements shall be ensured. The current safety mechanisms to address memory interferences have severe restrictions. Read on if you want to understand the weaknesses in today’s solutions to prevent corruption of memory content and illegal access to memory allocated to other software components.
September 2016
Sep 23, 2016Harrold
To achieve freedom from interference as defined by ISO 26262 would be rather simple if all C modules were completely self-contained, i.e. only calling functions and referring variables within in the same module. But reality is different. Addresses of objects, passed as parameters, flow through the whole application. How to keep track of access violation in such a labyrinth of code?
Sep 16, 2016Harrold
Critical to static analysis is whether a tool is capable of building a complete and correct call-graph. This is easy for direct calls, but becomes far more complicated if indirect calls are involved. See how this works for TASKING Safety Checker for ISO 26262 related applications.
Sep 07, 2016Harrold
TASKING wants employees to be creative, you get your best ideas when you’re under the shower, so build a couple of showers at the TASKING office. This wonderful idea arose under the shower, so I quickly wiped myself dry and went to the office to tell my boss about it. Unfortunately he was not excited at all. Read how this relates to my experience when developing our Safety Checker, initially targeted for ISO 26262 related applications.
August 2016
Aug 31, 2016Harrold
Mixed criticality in embedded software development is the concept of allowing software at different levels of criticality to interact and coexist in the same Electronic Control Unit (ECU). Certification of such systems is rather complex, because you have to prove that software elements with a lower safety level cannot interfere with elements with a higher safety level. You have to ensure what ISO 26262 calls ‘Freedom from Interference’. Read how to address this topic.