1. © 2015 Wind River. All Rights Reserved. Integrating FACE™ Aligned Componentry Larry Kinnan Principal Technologist, Wind River

2. 2 © 2015 Wind River. All Rights Reserved. Establishing the requirements  In order to establish a list of requirements a final “product” goal was needed –The “product” in this case was a reusable demonstration platform  The following platform requirements were then established –Use of multiple memory spaces using ARINC 653 partition scheduling –Graphical display that is externally controllable –Use of a Transport Services Segment using both DDS and ARINC ports –Must be portable to multiple hardware architectures –Must be extensible with the goal of showing a path to DO-178 certification

3. 3 © 2015 Wind River. All Rights Reserved. Operating System Segment (OSS)  The OSS serves as the basis for the platform providing: –Architecture Support Package (ASP) and Board Support Package (BSP) for the hardware platform that enable partitioning and device support framework –Provides the C and C++ runtimes –Provides the libraries for the ARINC 653 and POSIX which comprise the FACE Safety Base Profile –Provides HMFM APIs and a subset of the TS and IO Segments for use by portable graphical component  This OSS is based on VxWorks 653 version 2.5.0.1

4. 4 © 2015 Wind River. All Rights Reserved. Graphical Portable Component (GUI and OpenGL) Ansys tools created the Portable Application (GUI), CoreAVI provides OpenGL ES stack and device driver  Device Driver –Installed by OSS primitives –Adapter provides for device discovery in the IO Services –Second adaptor performs configuration from the PCS  Graphic Services –OpenGL ES stack is a linkable library provides direct path access  Portable Graphics Application –Generated via modeling tools –Data source manually added to read from TSS using ARINC port –Mapping of frame buffer done via configuration to application space

5. 5 © 2015 Wind River. All Rights Reserved. Data Distribution Services (DDS) and TSS RTI Connext provides DDS services and reference TSS  DDS is used as the underlying mechanism to send data from an external source to the FACE aligned platform –Industry standard using a publish subscribe model –Hardware/Architecture agnostic  Reference TSS –Supports communication between any PCS and PSSS UoPs –Not hard coded to a specific instantiation of the data model –Uses an IDL expression of a UoP Supplied Model compiled to C++ type-specific Transport Services (TS) interface (in this case the generic Shapes object) –Linked to the corresponding PCS

6. 6 © 2015 Wind River. All Rights Reserved. Implemented Platform and Control Tablet Overview

7. 7 © 2015 Wind River. All Rights Reserved. Partition Level Details Graphics Partition  Portable Graphics Application  OpenGL ES Stack  Framebuffer mapped via Configuration accessed using Memory Block DDS Partition  Data Distribution Services  Receives data from external source (tablet)  Send to Graphics Application via ARINC port Reference TSS Supplied by OSS library ARINC port Reference TSS Supplied by DDS library ARINC port Socket

8. 8 © 2015 Wind River. All Rights Reserved. Summary Use of FACE aligned components was the key goal  FACE uses industry standards to create profiles of APIs facilitating ease of integration  Multiple components easily integrate using these APIs  Platform is reusable and extensible Based upon the requirements provided the platform met and exceeded its goal and has been operation for multiple years and is now being extended to incorporate additional technologies

9. 9 © 2015 Wind River. All Rights Reserved. Thank You Questions and Comments, please contact: Larry Kinnan Principal Technologist for Avionics and Safety Critical Systems Wind River larry.kinnan@windriver.com Booth #13