Search Results

Modern cars contain more and more safety-relevant features which require addressing safety aspects during all development phases: on the functional level, on the architectural level, during integration as well as throughout the verification. The workflow of designing safe and reliable automotive embedded systems start with appropriate requirements definitions. According to the automotive safety standard ISO 26262, functional as well as non-functional threats need to be addressed. Non-functional aspects of safe software include a sound and safe timing of the software. The right methods, tools and standards enable OEMs and suppliers developing and providing applications which meet their timing requirements and a high level of quality. We present with this paper some important aspects related to timing in automotive embedded systems as well as the major standards such as TIMMO and AUTOSAR.

Distributed Control Systems (DCS) are becoming widely used in several areas of application, including automotive embedded systems. Many of these applications have severe timing constraints and are considered safety-critical, requiring predictable behavior in relation to both logical result and timing even in presence of faults. In such cases, a graceful degradation of service delivery that fulfils safety requirements can be tolerated. Especially in the automotive area, which is considering the possibility of replacing the major part of mechanical and/or hydraulic systems for electronic systems, the importance of reliable communication services plays a key role. To cover automotive DCS requirements, it is necessary to explore fault-tolerant techniques. In this context, this work presents an analysis on communication requirements in the automotive embedded system domain. In addition, a simulated analysis comparing a CAN and a TTP/C DCS is presented.