Automotive has evolved into one the fastest growing parts of the worldwide semiconductor industry, and automotive semiconductor content is exploding, driven by many advanced SoCs powering autonomous drive, infotainment, and vehicle communication systems. The “traditional” automotive electronics are not standing still either, with advanced drivetrains and sophisticated safety and ADAS systems creating demand for even-larger and more integrated SoCs.
As automotive electronic systems become ever more complex, the potential impact on the safety of vehicles' occupants and bystanders becomes a critical consideration for these systems. ISO 26262, the functional safety standard for road vehicles was created to guide the development of electrical and electronic systems for automobiles, and was recently released in a 2nd edition. For IP and SoC companies, ISO 26262 product development at the hardware level guidelines are particularly important—from a verification perspective, it lays out a set of requirements for functional safety that need to be understood and followed, and which are in addition to best-practice functional verification methodologies.
State-of-the-art functional safety verification must be performed, with the objective of determining the product’s ability to safely manage random faults that may arise during its lifecycle. This is a different verification objective compared to functional verification. To achieve the needed qualification in shortest amount of time, various technologies like static, formal, simulation and emulation must be combined in a unified functional safety platform.
This tutorial will provide a practical, hands-on overview of the following:
• ISO 26262 considerations for SoC and IP design verification, customer insights and today’s challenges
• Unique challenges for automotive SoC and IP verification engineering teams
• Best practice methodologies for functional safety verification
• Unified functional safety platform with
• FMEA (Failure Mode Effect Analysis) planning to FMED (Diagnostic) A management
• Static methods to estimate fault and diagnostic coverage
• Formal methods to prune the fault set and guide coverage closure
• Fault injection testing with simulation and emulation
• Annotation of diagnostic data
• Conclusions and QA
Thank you to our Sponsor