ARINC 653 basics |
送交者: 2018年11月11日01:55:16 于 [世界军事论坛] 发送悄悄话 |
|
ARINC 653From Wikipedia, the free encyclopedia ARINC 653 (Avionics Application Standard Software Interface) is a software specification for space and time partitioning in safety-critical avionics real-time operating systems (RTOS). It allows the hosting of multiple applications of different software levels on the same hardware in the context of an Integrated Modular Avionics architecture.[1] It is part of ARINC 600-Series Standards for Digital Aircraft & Flight Simulators. ContentsOverview[edit]In order to decouple the real-time operating system platform from the application software, ARINC 653 defines an API called APplication EXecutive (APEX). Each application software is called a partition and has its own memory space. It also has a dedicated time slot allocated by the APEX API. Within each partition, multitasking is allowed. The APEX API provides services to manage partitions, processes and timing, as well as partition/process communication and error handling. The partitioning environment can be implemented by using a hypervisor[2] to map partitions to virtual machines, but this is not required. The current work of the AEEC APEX Subcommittee includes the enhancement of ARINC 653 for multicore processor architectures.[3] History[edit]Initial version[edit]The initial version of ARINC 653 was published on October 10, 1996. ARINC 653-1[edit]Supplement 1 was published on January 1997 and introduced the concepts of APEX and Time and Space partitioning. ARINC 653-2[edit]Supplement 2 was published in 3 parts between March 2006 and January 2007:[4]
Current Organization of Standard[edit]
Basic principles of partitioning[edit]ARINC 653 Platform[edit]An ARINC 653 platform contains:
Initialization[edit]Initialization of an ARINC 653 partition creates resources used by the partition. Resources creation (PROCESS, EVENT, SEMAPHORE...) is performed by calling API services named CREATE_xxxx. Error handling[edit]The process error handler is a preemptive process of the highest priority dedicated to handle partition exceptions. It is created by the service CREATE_ERROR_HANDLER during partition initialization. The API allows the error handler to stop a faulty process (STOP_SELF). In that case, the RTOS scheduler will elicit the next process with the highest priority. ARINC 653 does not specify how the scheduler should behave if the error handler does not stop a faulty process. In some (theoretical) cases, this could lead to an infinite loop between the faulty process and the error handler. The error handler can obtain information about the source and the context of the exception. Mode management[edit]Each partition can be in several activation modes:
The SET_PARTITION_MODE service allows to manage these states. It can be called by any process in the partition. Entering the IDLE state is irreversible for the partition. Only an external event (such as a platform restart) can change the state to another mode when the partition is in this state. The processes of a partition[edit]Each partition has at least one process. Process scheduling is preemptive. The scheduler is called either by a timer or by API services. API services[edit]The ARINC 653 APEX services are API calls belonging in six categories:
No ARINC 653 services are provided for the memory management of partitions. Each partition has to handle its own memory (still under the constraints of memory partitioning enforced by ARINC 653). Each service returns a RETURN_CODE value which indicates if the call has been successful:
Links to POSIX and ASAAC[edit]The field covered by ARINC 653 is similar to ASAAC Def Stan 00-74. However, there are differences between the two standards.[11] Some ARINC 653 (APEX) calls have a POSIX equivalent, but are different from how they are defined in POSIX.[11] For example, the following call defined in ASAAC: receiveBuffer would be translated in ARINC 653 by: RECEIVE_BUFFER() and also in POSIX by: recv() References[edit]
See also[edit] |
|
|
|
|
实用资讯 | |
|
|
一周点击热帖 | 更多>> |
|
|
一周回复热帖 |
|
历史上的今天:回复热帖 |
2017: | 加拿大最后一分钟提出反对并拒绝开会, | |
2017: | 讲述几个为空军“一年成军三年成名”呕 | |
2016: | 筑墙,推翻O8 Care,Job, 川普的三大优 | |
2016: | 習近平:中國共產黨是孫中山最忠實繼承 | |
2015: | 喜讯:中国研发经费支出已超欧盟日本 升 | |
2015: | 中国货再次抢占印度市场 “印度制造”仍 | |
2014: | 肥妞运20新大图 多有前所未见角度 zt | |
2014: | LOL, Star Trek Uniform | |
2013: | 《大国重器》 20131110 第五集 创新驱动 | |
2013: | 《大国重器》(6、5、4、3、2、1) | |
|