What is it about?

Safety-critical electronic systems must behave safely even if hardware malfunctions. Often, embedded software is responsible to detect and correct hardware errors or establish a safe state if error correction is not possible. Our work aims to support software designers in considering this aspect already from the beginning of the design.

Featured Image

Why is it important?

Software behavior under the influence of hardware errors can be tested by fault injection. However, fault injection can take several hours or days. Thus, it is typically performed only once during system integration after hardware and software design has been completed. However, changing the software design at late development stages is very expensive and can delay release. This work provides techniques to speed up fault injection significantly such that it can be carried out already during design.

Read the Original

This page is a summary of: Fault Injection for Test-Driven Development of Robust SoC Firmware, ACM Transactions on Embedded Computing Systems, January 2018, ACM (Association for Computing Machinery),
DOI: 10.1145/3092943.
You can read the full text:

Read

Resources

Contributors

The following have contributed to this page