Porting applications to an ARINC 653 compliant IMA platform using Vxworks as an example

Kinnan, L.; Wlad, J.; Rogers, Pat

doi:10.1109/dasc.2004.1390800

Cited by 14 publications

(8 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An example for a partition management operating system is a time-triggered operating system based on Linux RealTime Application Interface (RTAI) (Huber et al 2005). Further examples of suitable operating systems, which fit into the proposed architecture, are LynxOS-178 (LynuxWorks 2006) and VxWorks (Kinnan et al 2004). These two operating systems are certified operating systems that support time partitioning through a fixed-cyclic timeslice scheduler.…”

Section: Physical System Structurementioning

confidence: 99%

An integrated architecture for future car generations

2007

View full text Add to dashboard Cite

The DECOS architecture is an integrated architecture that builds upon the validated services of a time-triggered network, which serves as a shared resource for the communication activities of more than one application subsystem. In addition, encapsulated partitions are used to share the computational resources of Electronic Control Units (ECUs) among software modules of multiple application subsystems. This paper investigates the benefits of the DECOS architecture as an electronic infrastructure for future car generations. The shift to an integrated architecture will result in quantifiable cost reductions in the areas of system hardware cost and system development. In the paper we present a current federated Fiat car E/E architecture and discuss a possible mapping to an integrated solution based on the DECOS architecture. The proposed architecture provides a foundation for mixed criticality integration with both safety-critical and non safety-critical subsystems. In particular, this architecture supports applications up to the highest criticality classes (10 −9 failures per hour), thereby taking into account the emerging dependability requirements of by-wire functionality in the automotive industry.

show abstract

Section: Physical System Structurementioning

confidence: 99%

An integrated architecture for future car generations

2007

View full text Add to dashboard Cite

show abstract

“…Traditionally, the partition scheduling problem has been addressed in an ad-hoc fashion based on interactions between the system designer and vendors who provide the partitions. Although many different ARINC-653 platforms exist (see [1], [2]), there is little work on automatic scheduling of partitions [15], [16], [21]. Kinnan et.…”

Section: System Model and Related Workmentioning

confidence: 99%

“…al. [15] only provide preliminary heuristic guidance, and the other studies [16], [21] use constraint-based approaches to look at combined network and processor scheduling. In contrast to this high-complexity holistic analysis, we present an efficient compositional analysis technique that also protects intellectual property through partition isolation.…”

Section: System Model and Related Workmentioning

confidence: 99%

A Compositional Scheduling Framework for Digital Avionics Systems

Easwaran

Lee

Sokolsky

et al. 2009

2009 15th IEEE International Conference on Embedded and Real-Time Computing Systems and Applications

View full text Add to dashboard Cite

Abstract-ARINC specification 653-2 describes the interface between application software and underlying middleware in a distributed real-time avionics system. The real-time workload in this system comprises of partitions, where each partition consists of one or more processes. Processes incur blocking and preemption overheads, and can communicate with other processes in the system. In this work, we develop compositional techniques for automated scheduling of such partitions and processes. At present, system designers manually schedule partitions based on interactions they have with the partition vendors. This approach is not only time consuming, but can also result in under utilization of resources.

show abstract

“…An example for a partition management operating system is Wind River's VxWorks AE653 [30]. In compliance with ARINC standard 653 [31] (also called APplication EXecutive (APEX)), this real-time operating system supports the execution of avionic jobs that would be implemented on dedicated Line Replaceable Units (LRUs) in non IMA systems.…”

Section: Model Of An Integrated Node Computermentioning

confidence: 99%

The Fault Assumptions in Distributed Integrated Architectures

Obermaisser¹,

Peti²

2007

SAE Technical Paper Series

View full text Add to dashboard Cite

Distributed integrated architectures in the automotive and avionic domain result in hardware cost reduction, dependability improvements, and improved coordination between application subsystems compared to federated systems. In order to support safety-critical application subsystems, a distributed integrated architecture needs to support fault-tolerance strategies that enable the continued operation of the system in the presence of failures. The basis for the implementation and validation of faulttolerance strategies are realistic fault assumptions, which are captured in a fault hypothesis. This paper describes a fault hypothesis for distributed integrated architectures, which takes into account the sharing of the communication and computational resources of a single distributed computer system among multiple application subsystems. Each node computer serves for the execution of multiple jobs. In analogy, the communication network interconnecting the node computers has to support message exchanges of more than one application subsystem. Using a generic system model of a distributed integrated architecture, we argue in favor of a differentiation of fault containment regions for hardware and software faults. Based on these fault containment regions, we discuss the failure modes, the failure rates, the maximum number of failures, and the recovery intervals. In particular, the fault hypothesis describes the assumptions concerning the respective frequencies of transient and permanent failures in consideration of recent semiconductor trends.

show abstract

Porting applications to an ARINC 653 compliant IMA platform using Vxworks as an example

Cited by 14 publications

References 1 publication

An integrated architecture for future car generations

An integrated architecture for future car generations

A Compositional Scheduling Framework for Digital Avionics Systems

The Fault Assumptions in Distributed Integrated Architectures

Contact Info

Product

Resources

About