Porting applications to an ARINC 653 compliant IMA platform using Vxworks as an example

With the advent of ARINC 653-1 and the availability of ARINC 653 complaint partitioned systems, most avionics manufacturers are now faced with migrating or porting their existing legacy applications from a single address space system widely used in federated avionics systems to an ARINC-653 system. This work discusses the issues of scheduling and latency effects of the partitions as well as issues of different operating modes (flight, ground maintenance, etc.) and considerations needed when moving these applications to the new system using Wind River's VxWorks RTOS as the example environment.