Avoid risks and be compliant to security standards with on-target code coverage analysisDevelopers of embedded software are living with risks: functions implemented have often the potential to cause death, injury and financial damage if they do not operate correctly.In safety-critical systems like aircraft flight controls, car braking, railway control or medical devices no margin of error is tolerable. For this reason the industry standards DO-178C (aviation), Iso 26262 (automotive) and EN 50128 (railway) require extensive software tests and the proof of code coverage. In dependancy to the criticality, developers and testers have to apply different levels of code coverage. In order to proof that the software is sufficiently tested, the source code has to be instrumented by code coverage tools. This requires a greater memory usage and challenges arise as the available Ram and Rom memory of embedded systems is usually limited. Learn more about the requirements of the standards for safety-critical software and how to achieve them. We show how to address the challenge of small embedded targets by downsizing dramatically the need for additional Ram memory.
Slide Presentation
|
|