close By using this website, you agree to the use of cookies. Detailed information on the use of cookies on this website can be obtained on OneSpin's Privacy Policy. At this point you may also object to the use of cookies and adjust the browser settings accordingly.

Why Safety-Critical Verification Is So Difficult

By Ann Steffora Mutschler, Semiconductor Engineering

Experts at the Table: Proprietary hardware makes software development more difficult; how to deal with over-the-air updates.

The inclusion of AI chips in automotive and increasingly in avionics has put a spotlight on advanced-node designs that can meet all of the ASIL-D requirements for temperature and stress. How should designers approach this task, particularly when these devices need to last longer than the applications? Semiconductor Engineering sat down to discuss these issues with Kurt Shuler, vice president of marketing at Arteris IP; Frank Schirrmeister, senior group director, solutions marketing at Cadence; Ted Miracco, CEO of Cylynt; Dean Drako, CEO of Drako Motors; Michael Haight, director of business management, Micros, Security & Software Business Unit at Maxim Integrated; Neil Hand, director of marketing for digital verification technologies at Mentor, a Siemens Business; Sergio Marchese, technical marketing manager at OneSpin Solutions; Marc Serughetti, senior director, verification group at Synopsys; and Hagai Arbel, CEO of Vtool. To read part one of this discussion, click here.


People have found exploits and ways to do things that are mind blowing. When you add in the complexity of modern safety critical systems, whether it be automotive, industrial, mil/aerospace, it’s a different mindset, and we can enable them with tools and we have to enable them with tools. It’s a mentality. It’s switching what you think. It’s going from the white hat hacker to a black hat hacker. It’s how do you go from, using it for good versus how to exploit it for evil.


Related Links