Real-time scheduling in a generic fault-tolerant architecture

Wellings, Andy; Beus-Dukic, Ljerka; Powell, David

doi:10.1109/real.1998.739772

Cited by 9 publications

(4 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3) Actuating: The output actor balances the actuation effort among the (redundant) actuators that issue commands to the electronics (A/D converters or pulsewidth-modulation drivers) to set the motor torque. The actuator updates are applied to the plant at the period end to reduce jitter, a well-known technique in real-time control [24], [25].…”

Section: Proposed Methodology and Design Flowmentioning

confidence: 99%

Fault-Tolerant Distributed Deployment of Embedded Control Software

Pinello

Carloni

Sangiovanni-Vincentelli

2008

IEEE Trans. Comput.-Aided Des. Integr. Circuits Syst.

View full text Add to dashboard Cite

Abstract-Safety-critical feedback-control applications may suffer faults in the controlled plant as well as in the execution platform, i.e., the controller. Control theorists design the control laws to be robust with respect to the former kind of faults while assuming an idealized scenario for the latter. The execution platforms supporting modern real-time embedded systems, however, are distributed architectures made of heterogeneous components that may incur transient or permanent faults. Making the platform fault tolerant involves the introduction of design redundancy with obvious impact on the final cost. We present a design flow that enables the efficient exploration of redundancy/cost tradeoffs. After providing a system-level specification of the target platform and the fault model, designers can rely on the synthesis of the low-level fault-tolerance mechanisms. This is performed automatically as part of the embedded software deployment through the combination of the following three steps: replication, mapping, and scheduling. Our approach has a sound foundation in faulttolerant data flow, a novel model of computation that simplifies the integration of formal validation techniques. Finally, we report on the application of our design flow to two case studies from the automotive industry: a steer-by-wire system from General Motors and a drive-by-wire system from BMW.

show abstract

Section: Proposed Methodology and Design Flowmentioning

confidence: 99%

Fault-Tolerant Distributed Deployment of Embedded Control Software

Pinello

Carloni

Sangiovanni-Vincentelli

2008

IEEE Trans. Comput.-Aided Des. Integr. Circuits Syst.

View full text Add to dashboard Cite

show abstract

“…The control system repeats the following sequence at each period T max : (1) sensors are sampled, (2) software routines are executed, and (3) actuators are updated with the newlyprocessed data. The actuator updates are applied to the plant at the end of the period to help minimize jitter, a well known technique in the real-time control community [17,32]. In order to guarantee correct operation, the worstcase execution time among all possible iterations, i.e.…”

Section: Fault-tolerant Design Methodologymentioning

confidence: 99%

Platform-Based Design for Embedded Systems

Sgroi¹,

Sangiovanni‐Vincentelli²,

Bernardinis³

et al. 2005

Embedded Systems Handbook

View full text Add to dashboard Cite

A platform is an abstraction layer that hides the details of several possible implementation refinements of the underlying layers. It is a library of elements characterized by models that represent their functionalities and offer an estimation of (physical) quantities that are of importance for the designer. The library contains interconnects and rules that define what are the legal composition of the elements. A legal composition of elements and interconnects is called a platform instance. Platform-based design is a meet-in-the-middle process, where successive refinements of specifications meet with abstractions of potential implementations that are captured in the models of the elements of the platform. It is this characteristic that makes platform-based design a novel design method.We argue for the importance of structuring precisely the platform layers and we discuss how to define formally the transitions from one platform to the next. In particular, we emphasize the interplay of top-down constraint propagation and bottomup performance estimation while illustrating the notion of articulation point in the design process. In this context, we study the key role played by the API platform together with the micro-architecture platform in embedded system design. Also, we report on three applications of platform-based design: at the system-level, we discuss network platforms for communication protocol design and fault-tolerant platforms for the design of safety-critical applications; at the implementation level, we present analog platforms for mixed-signal integrated circuit design.

show abstract

“…If precedence relations exist between tasks, the communication mechanisms can be simplified, since these precedence relations guarantee de:erministic execution (Wellings et al, 1998). If the receiving task is sporadic and is released by a sending task, it is guaranteed that, in all replicated components, the replicas of the task will execute with the same data.…”

Section: Hrts Replica Managermentioning

confidence: 99%