ARINC 653P0-1

This document introduces the concepts and principles specifiedwithin ARINC 653 to support the API, including vocabulary anddefinitions, and system architecture. Both the interface and thebehavior of the API services are specified in ARINC 653. Behavioris specified to the extent needed to describe functionalityrelevant to calling applications.

Where necessary, assumptions are made as to the support orbehavior provided by the CSW and hardware. This document should notbe construed as a specification for the CSW or hardware. However,where the CSW or hardware does not coincide with the statedassumptions, the API behaviors specified in ARINC 653 may not matchthe actual behavior.

ARINC 653 is intended for use in a partitioned softwareenvironment. In order to assure a high degree of portability,aspects of the partitioned environment are discussed and assumed.However, ARINC 653 does not define the complete system, hardware,and software requirements for partitioning nor does it provideguidance on proper implementation of partitioning, and inparticular, robust partitioning. It must not be construed thatcompliance to ARINC 653 assures robust partitioning.

Purpose

This document provides an overview of the entire set ofdocuments collectively referred to as ARINC 653. As this set ofdocuments evolves, supplements to Parts 1 through 5 will be mademore consistent with Part 0 in conjunction with the technicalchanges expected to be made in the evolution of ARINC 653. Asummary of the ARINC 653 documents follows:

• Part 0 – Overview of ARINC 653

• Part 1 – Required Services

• Part 2 – Extended Services

• Part 3A – Conformity Test Specification for ARINC 653 RequiredServices

• Part 3B – Conformity Test Specification for ARINC 653 ExtendedServices

• Part 4 – Subset Services

• Part 5 – Core Software Recommended Capabilities

The term “this document” refers to Part 0 only, while the term”ARINC 653″ or “the Specification” refers to the whole set of ARINC653 documents, currently Parts 0 to 5.

The primary objective of ARINC 653 is to define a generalpurpose APplication/EXecutive (APEX) interface Application ProgramInterface (API) between the Core Software (CSW) of an AvionicsComputer Resource (ACR) and the application software. Includedwithin ARINC 653 are the interface requirements between theapplication software and the CSW and the list of services whichallow the application software to control the scheduling,communication, and status information of its internal processingelements.

It should be noted that while ARINC 653 was developed for use inavionics systems, it is equally suitable for any system thatrequires API services, and partitioning mechanisms to enablemultiple hosted applications (of the same or differing safetylevels) to operate on platform hardware.

ARINC 653 defines the data exchanged statically (viaconfiguration) or dynamically (via services) as well as thebehavior of services provided by the CSW and used by theapplication. It is not the intent of the 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.

ARINC 653 Parts 1, 2, and 4 describe the runtime environment forembedded avionics software. This list of services identifies theminimum functionality provided to the application software and is,therefore, the industry standard interface. It is intended for thisinterface to be as generic as possible, since an interface with toomuch complexity or too many system specific features is normallynot accepted over a variety of systems. The software specificationsof this API are High Order Language (HOL) independent, allowingsystems using different compilers and languages to follow thisinterface.

ARINC 653 is intended to complement ARINC Report651: Design Guidance for Integrated ModularAvionics. It is expected that individual parts of ARINC 653will evolve to contain additional functionality and capability.Supplements to ARINC Specification 653 Parts 0 to 5 will beprepared and published independently as needed by the industry. Ineach case, the evolution of one part must consider the potentialimpact on the other ARINC 653 parts.

Edition:

15

Published:

08/03/2015

Number of Pages:

39

File Size:

1 file , 240 KB