SFFS339 December   2022 TLIN1431-Q1

 

  1.   Trademarks
  2. 1Introduction
  3. 2Hardware Component Failure Modes Effects and Diagnostics Analysis (FMEDA)
    1. 2.1 Random Fault Estimation
      1. 2.1.1 Fault Rate Estimation Theory for Packaging
      2. 2.1.2 Fault Estimation Theory for Silicon Permanent Faults
      3. 2.1.3 Fault Estimation Theory for Silicon Transient Faults
      4. 2.1.4 The Classification of Failure Categories and Calculation
  4. 3Using the FMEDA Spreadsheet Tool
    1. 3.1 Mission Profile Tailoring Tab
      1. 3.1.1 Geographical Location
      2. 3.1.2 Life Cycle
      3. 3.1.3 Use Case Thermal Management Control (Theta-Ja) and Use Case Power
      4. 3.1.4 Safe vs Non-Safe (Safe Fail Fraction) for Each Component Type
      5. 3.1.5 Analog FIT Distribution Method
      6. 3.1.6 Operational Profile
    2. 3.2 Pin Level Tailoring Tab
    3. 3.3 Function and Diag Tailoring Tab
    4. 3.4 Diagnostic Coverage Tab
    5. 3.5 Customer Defined Diagnostics Tab
    6. 3.6 Totals - ISO26262 Tab
    7. 3.7 Details - ISO26262 Tab
    8. 3.8 Example Calculation of Metrics
      1. 3.8.1 Assumptions of Use for Calculation of Safety Metrics
      2. 3.8.2 Summary of ISO 26262 Safety Metrics at Device Level

3.4 Diagnostic Coverage Tab

This tab is informational only. There are no selections the user can make in this tab.

The 'Diagnostic Coverage' tab is the source for the diagnostic groupings that are selected in the 'Pin Level Tailoring' tab and 'Function and Diag Tailoring' tab. Each design block (Part Level) has one or more diagnostic options (which appear as the drop-down options in those tabs). The FMA values field represents all of the unique diagnostics that are applied when that diagnostic option is selected. The diagnostic detection, diagnostic coverage, and latent coverage fields indicate the diagnostic coverage claimed for each diagnostic option that is populated into the 'Function and Diag Tailoring' tab when that option is selected.

For each failure mode of a fundamental design element, a diagnostic may be allocated in the safety architecture to detect failures. Often a single diagnostic is able to detect multiple failure modes. Diagnostics may take the form of software-based tests, hardware test structures, or additional logical channels, amongst other possible implementations. Diagnostics may have continuous, periodic, or one time execution. The frequency of necessary diagnostic application should be determined by the system integrator based on relevant safety constraints (such as fault tolerant time interval, desired detection rate, and so forth), which are necessary to support the targeted safety function or safety goal.