white paper

Are you safe yet? Safety mechanism insertion and validation

Introduce correct safety mechanisms using safety synthesis

Are you safe yet? Safety mechanism insertion and validation

As functional safety becomes increasingly important in today's industrial and automotive designs, many legacy designs have to be “upgraded” to meet the safety goal of the system. An efficient approach is to use safety synthesis and formal verification to incorporate a safety architecture into the design.

The flow can consist of these major steps:

1. Explore areas of the design where better fault detections are required

2. Introduce the right safety mechanisms into the design with safety synthesis

3. Validate the design changes with formal verification, and

4. Perform formal fault injection to measure the diagnostic coverage

FMEDA (Failure Mode Effect and Diagnostic Analysis) evaluates the safety architecture with its collection of safety mechanisms and calculates the safety performance of the system. In Part 5 of the ISO 262621 specification, a hardware architecture needs to be evaluated against the requirements for fault handling. It requires that the probabilities of random hardware failures are rigorously analyzed and quantified via a set of objective metrics. If any of the architectural metrics fail to meet the criteria defined for the product’s Automotive Safety Integrity Level (ASIL), design teams will be mandated to re-evaluate the component’s safety concept, improve the existing safety mechanisms, and if necessary introduce new safety mechanisms.

To improve diagnostic coverage, a practical approach is to incorporate a collection of safety mechanisms into the design so that the number and types of faults detected can be improved. This is best to be done at the register transfer level, where functional verification can be performed efficiently.

Share

Related resources

It’s not my fault! How to run a better fault campaign using formal
White Paper

It’s not my fault! How to run a better fault campaign using formal

This paper describes how to run a better ISO 26262 fault campaign using formal verification. The ISO 26262

How formal reduces fault analysis for ISO 26262
White Paper

How formal reduces fault analysis for ISO 26262

The ISO 26262 standard defines straightforward metrics for evaluating the “safeness” of a design by defining safety goals, safety mechanisms, and fault metrics. However, determining those metrics is difficult.

Achieving functional safety for autonomous vehicle SoC designs
White Paper

Achieving functional safety for autonomous vehicle SoC designs

This paper details the fundamental functional safety concepts for companies delivering silicon and systems into a rapidly evolving automotive ecosystem