Meeting ISO 26262 standards for automotive safety means applying a consistent approach throughout the design process. Here's how to start.
A look at how DDR DRAM is being adapted for use in automotive systems, and the demands its use puts upon interface IP for SoCs.
Considering the issue of functional safety verification in automotive systems design, within the context of ISO26262
Engineers developing an SoC for the automotive market have to show that it doesn’t have functional safety issues - even if the SoC enters an unexpected state. Here's how to tackle the safety verification task.
How fault mode and effect analysis (FMEA) can be performed on a virtual prototype of an automotive system containing mechanical, electrical, analog and digital models, including the microcontroller running the same software as will be used in the car.
Behind the drivers for memory BIST innovation in areas such as power-on self-test, destructive and non-destructive techniques, and faster memory repair.
A look at some of the quality and safety requirements that must be met when developing and applying semiconductor IP to the automotive sector.
The increasing complexity of automative software is challenging the ability of established software testing strategies to demonstrate its functional safety. Here's how virtual prototyping can help.
Designers will have to update development processes to achieve the rigorous safety certifications required in automotive, rail, avionics and similar markets
The ISO 26262 safety standard lays out a number of best practices for the automotive industry and for suppliers. Formal verification provides a way of streamlining the verification of SoCs that need to conform to the standard.