ARINC 653P1-4

This document specifies both the interface and the behavior ofthe API services. Behavior is specified to the extent needed todescribe functionality relevant to interfacing applications.

Where necessary, assumptions are made as to the support orbehavior provided by the operating system and hardware. This shouldnot be construed as a specification for the O/S or hardware.However, where the O/S or hardware does not coincide with thestated assumptions, the API behaviors specified herein may notmatch the actual behavior.

ARINC 653 is intended for use in a partitioned environment. Inorder to assure a high degree of portability, aspects of thepartitioned environment are discussed and assumed. However, thisspecification does not define the complete system, hardware, andsoftware requirements for partitioning nor does it provide guidanceon proper implementation of partitioning, and in particular, robustpartitioning. It must not be construed that compliance to ARINC 653assures robust partitioning.

Purpose

This document specifies the basic operating environment forapplication software used within Integrated Modular Avionics (IMA)and traditional ARINC 700-series avionics.

The primary objective of this specification is to define ageneral-purpose APEX (APplication/EXecutive) interface between theOperating System (O/S) of an avionics computer resource and theapplication software. Included within this specification are theinterface requirements between the application software and the O/Sand the list of services which allow the application software tocontrol the scheduling, communication, and status information ofits internal processing elements.

This specification defines the data exchanged statically (viaconfiguration) or dynamically (via services) as well as thebehavior of services provided by the O/S and used by theapplication. It is not the intent of this specification to dictateimplementation requirements on either the hardware or software ofthe system, nor is it intended to drive certain system-levelrequirements within the system which follows this standard.

The majority of this document describes the runtime environmentfor embedded avionics software. This list of services identifiesthe minimum functionality provided to the application software andis, therefore, the industry standard interface. It is intended forthis interface to be as generic as possible, since an interfacewith too much complexity or too many system-specific features isnormally not accepted over a variety of systems. The softwarespecifications of the APEX interface are High-Order Language (HOL)independent, allowing systems using different compilers andlanguages to follow this interface.

This document is intended to complement ARINC Report651: Design Guidance for Integrated ModularAvionics. It is expected that this document will evolve tocontain additional functionality and capability. Supplements tothis document will be prepared as needed by the industry.

Edition:

15

Published:

08/21/2015

Number of Pages:

285

File Size:

1 file , 910 KB