ARINC 653 hypervisor

We have developed an early prototype of an ARINC 653 implementation using the virtualization technology of the open source Xen hypervisor along with a Linux-based domain/partition OS. In this paper we share lessons learned from adding to our prototype both an ARINC 653 CPU scheduler and a simple ARINC 653 serial I/O driver. By using a common hypervisor technology on multiple platforms, early application development can be done in a PC environment with relatively good modeling of the final target's behavior. The paper covers three topics. First, we start with an overview of the ARINC 653 standard, which is important because it reduces development costs, reduces system weight, and lowers certification costs. The standard focuses on resource partitioning of time and space on an avionics computer, managing the three primary subsystems of the computer: Central Processing Unit (CPU), Memory, and Input/Output (I/O). Second, we will review virtualization technology, an established method of sharing a computing resource, considering it for adaptation to ARINC 653. Third, as a case study, we will examine our prototype implementation of the ARINC 653 standard using the Xen open source hypervisor. We conclude with a discussion of our plans for future work towards ARINC 653 simulation and development environments on both PC desktop and embedded targets.

[1]  K.R. Luecke,et al.  Device Drivers in Time and Space Partitioned Operating Systems , 2006, 2006 ieee/aiaa 25TH Digital Avionics Systems Conference.

[2]  Paul Clements,et al.  The U.S. Army's Common Avionics Architecture System (CAAS) Product Line: A Case Study , 2005 .

[3]  Robert P. Goldberg,et al.  Formal requirements for virtualizable third generation architectures , 1973, SOSP 1973.

[4]  Pierre Gaufillet,et al.  Linux: A multi-purpose executive support for civil avionics applications? , 2004, IFIP Congress Topical Sessions.

[5]  David Patterson The trouble with multi-core , 2010, IEEE Spectrum.

[6]  K.R. Luecke,et al.  Device drivers in Time and Space Partitioned operating systems , 2008, MILCOM 2008 - 2008 IEEE Military Communications Conference.

[7]  L. Kinnan,et al.  Porting applications to an ARINC 653 compliant IMA platform using Vxworks as an example , 2004, The 23rd Digital Avionics Systems Conference (IEEE Cat. No.04CH37576).

[8]  R.L. Alena,et al.  Communications for Integrated Modular Avionics , 2007, 2007 IEEE Aerospace Conference.

[9]  S. Santos,et al.  A portable ARINC 653 standard interface , 2008, 2008 IEEE/AIAA 27th Digital Avionics Systems Conference.

[10]  Lui Sha,et al.  Coscheduling of Real-Time Tasks and PCI Bus Transactions , 2008 .

[11]  Johan Akerberg On Security in Safety-Critical Process Control , 2009 .

[12]  Giuseppe Lipari,et al.  Resource Reservation in Real-Time Operating Systems - a joint industrial and academic position , 2003 .

[13]  J. Ventura,et al.  GASCA "Generic Avionics Scaleable Computing Architecture" , 1999 .

[14]  J. Littlefield-Lawwill,et al.  System considerations for robust time and space partitioning in Integrated Modular Avionics , 2008, 2008 IEEE/AIAA 27th Digital Avionics Systems Conference.

[15]  José Rufino,et al.  AMOBA - ARINC 653 Simulator for Modular Based Space Applications , 2008 .

[16]  John P. McDermott,et al.  A formal security policy for xenon , 2008, FMSE '08.

[17]  Rushby John,et al.  Partitioning in Avionics Architectures: Requirements, Mechanisms, and Assurance , 1999 .

[18]  P.J. Prisaznuk,et al.  ARINC 653 role in Integrated Modular Avionics (IMA) , 2008, 2008 IEEE/AIAA 27th Digital Avionics Systems Conference.

[19]  Thomas Novak,et al.  Safety- and Security-Critical Services in Building Automation and Control Systems , 2010, IEEE Transactions on Industrial Electronics.

[20]  Hoyt Lougee,et al.  SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION , 2001 .