Automated Identification of Application-Dependent Safe Faults in Automotive Systems-on-a-Chips

ISO 26262 requires classifying random hardware faults based on their effects (safe, detected, or undetected) within integrated circuits used in automobiles. In general, this classification is addressed using expert judgment and a combination of tools. However, the growth of integrated circuit comple...

Full description

Saved in:
Bibliographic Details
Published inElectronics (Basel) Vol. 11; no. 3; p. 319
Main Authors Bagbaba, Ahmet Cagri, Augusto da Silva, Felipe, Sonza Reorda, Matteo, Hamdioui, Said, Jenihhin, Maksim, Sauer, Christian
Format Journal Article
LanguageEnglish
Published Basel MDPI AG 01.02.2022
Subjects
Automation
Automobile industry
Case studies
Central processing units
Classification
Controller area network
CPUs
Cruise control
Electrostatic discharges
Embedded systems
Fault detection
Hardware
Integrated circuits
Pessimism
Simulation
Software
Software testing
System on chip
Online AccessGet full text

Cover

More Information
Summary:ISO 26262 requires classifying random hardware faults based on their effects (safe, detected, or undetected) within integrated circuits used in automobiles. In general, this classification is addressed using expert judgment and a combination of tools. However, the growth of integrated circuit complexity creates a huge fault space; hence, this form of fault classification is error prone and time consuming. Therefore, an automated and systematic approach is needed to target hardware fault classification in automotive systems on chips (SoCs), considering the application software. This work focuses on identifying safe faults: the proposed approach utilizes coverage analysis to identify candidate safe faults considering all the constraints coming from the application. Then, the behavior of the application software is modeled so that we can resort to a formal analysis tool. The proposed technique is evaluated on the AutoSoC benchmark running a cruise control application. Resorting to our approach, we could classify 20%, 11%, and 13% of all faults in the central processing unit (CPU), universal asynchronous receiver–transmitter (UART), and controller area network (CAN) as safe faults, respectively. We also show that this classification can increase the diagnostic coverage of software test libraries targeting the CPU and CAN modules by 4% to 6%, increasing the achieved testable fault coverage.
ISSN:2079-9292
2079-9292
DOI:10.3390/electronics11030319