Software Architecture Methods and Mechanisms for Timing Error and Failure Detection According to ISO 26262: Deadline vs. Execution Time Monitoring 2013-01-0174
More electronic vehicle functions lead to an exponentially growing degree of software integration in automotive ECUs. We are seeing an increasing number of ECUs with mixed criticality software. ISO26262 describes different safety requirements, including freedom from interference and absence from error propagation for the software. These requirements mandate particular attention for mixed-criticality ECUs. In this paper we investigate the ability to guarantee that these safety requirements will be fulfilled by using established (deadline monitoring) and new error detection mechanisms (execution time monitoring). We also show how these methods can be used to build up safe and efficient schedules for today's and future automotive embedded real time systems with mixed criticality software.
Citation: Ficek, C., Sebastian, M., Feiertag, N., Richter, K. et al., "Software Architecture Methods and Mechanisms for Timing Error and Failure Detection According to ISO 26262: Deadline vs. Execution Time Monitoring," SAE Technical Paper 2013-01-0174, 2013, https://doi.org/10.4271/2013-01-0174. Download Citation
Christoph Ficek, Maurice Sebastian, Nico Feiertag, Kai Richter, Marek Jersak, Karsten Schmidt