Dreamstime_Wrightstudio_240359563
dreamstime_wrightstudio_240359563
Dreamstime_Jamesteohart_161233010
dreamstime_andjamesteohart_161233010_promo
ID 211678764 © Andrey Sayfutdinov | Dreamstime.com
Lithium_Ion_Batteries_Stock_1_Dreamstime_
ID 21506016 © Cherkas | Dreamstime.com
_cable_dreamstime_l_21506016
Toshiba (generated with AI)
ednp_toshibaautobrushedmotordriver_eyecandy
Dreamstime_Nahid-Hasan-Masud_332026927
dreamstime_nahidhasanmasud_332026927
Dreamstime_jan-dzacovsky_206876437
dreamstime_jandzacovsky_206876437

Three Steps to an Automated ISO 26262 Random-Fault Flow (.PDF Download)

Aug. 8, 2019
Three Steps to an Automated ISO 26262 Random-Fault Flow (.PDF)

The complexity of automotive integrated circuits (ICs) has grown exponentially with the introduction of advanced driver-assistance systems and autonomous drive technologies. Directly correlated to this hike in complexity is the increased burden of ensuring an IC is protected from random hardware faults—functional failures that occur unpredictably. Random-fault mitigation continues to be one of the primary challenges and pain points across the industry.

To ensure random faults don’t affect silicon functionality and place humans at risk of injury, designs must be enhanced by implementing safety mechanisms to identify and control these faults. ISO 26262 requires that development teams instrument and prove the effectiveness of each safety mechanism.