Advancing automotive application development: Page 2 of 8

February 08, 2017 //By Alexander Herz, Tasking
Advancing automotive application development
Safety-critical software functions required in a car are traditionally placed in separate, single-core Electronic Control Unit (ECU). With this practice, it’s easy to ensure that different functions with potentially different functional safety requirements and Automotive Safety Integrity Level (ASIL) are physically insulated and protected against interference from each other.

First, we will look at the key features of the TASKING Safety Checker before we evaluate how you use the tool in a step-by-step walkthrough. Lastly, we will discuss how the TASKING Safety Checker helps reduce the risk of releasing code which triggers MPU traps by up to 95% while also saving 69% of your MPU related testing and bug fixing costs.

Overview of the tasking safety checker

The TASKING Safety Checker is the only automated analysis tool that enables developers to reduce dramatically the risk of MPU access violations generating in the field. The TASKING Safety Checker also significantly reduces the cost of testing for MPU traps and fixing the offending code.

The tool statically analyzes the component’s source code for access violations that would trigger MPU traps as if the code was executed with all possible inputs using an appropriately configured MPU. This differentiates the TASKING Safety Checker from other static analysis tools, which do not analyze MPU access violations and other information including reads from uninitialized memory and data overflows.

Notably, the TASKING Safety Checker does not require hardware, and without any running code. This allows for fast and early detection of common coding mistakes with a quick run of the TASKING Safety Checker after a code change. It also takes into account all possible executions of the provided source code, so that very high coverage, including odd corner cases, is achieved without the cost of creating test cases. Furthermore, a detailed root cause analysis for each identified memory access violation is displayed so that the cost of debugging MPU traps to find and fix the offending code is removed.

Design category: 

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.