Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

How is initialization of an arinc 653 partition performed?


Asked by Angie Thomas on Dec 05, 2021 FAQ



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 . The process error handler is a preemptive process of the highest priority dedicated to handle partition exceptions.
Similarly,
ARINC 653 partitions are analogous to Windows/Unix processes and ARINC 653 processes are analogous to Windows/Unix threads. Process Management Module provides process scheduling. Each process can be in Waiting, Ready or Running State. Time Manager Module: Time is unique and independent of partition execution.
Also Know, It is part of ARINC 600-Series Standards for Digital Aircraft & Flight Simulators. 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.
Indeed,
The initial version of ARINC 653 was published on October 10, 1996. Supplement 1 was published on January 1997 and introduced the concepts of APEX and Time and Space partitioning. Supplement 2 was published in 3 parts between March 2006 and January 2007:
Additionally,
However, there are differences between the two standards. Some ARINC 653 (APEX) calls have a POSIX equivalent, but are different from how they are defined in POSIX. For example, the following call defined in ASAAC: