ARINC-653 and Virtualization Concepts for Safety- Critical Systems
ARINC-653 and Virtualization Concepts for Safety- Critical Systems
ARINC-653 and Virtualization Concepts for Safety- Critical Systems
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
SAVUNMA SANAYİİ MÜSTEŞARLIĞI<br />
Kalite – Test ve Sertifikasyon Daire Başkanlığı<br />
INTERAKTİF KOKPİT GÖRÜNTÜ SİSTEMLERİ ve<br />
SERTİFİKASYONU<br />
için YAZILIM YAKLAŞIMLARI<br />
<strong>ARINC</strong> <strong>653</strong> / DO-178C ve <strong>ARINC</strong> 661<br />
Konferansı<br />
30 Kasım 2012, Ankara<br />
<strong>ARINC</strong>-<strong>653</strong> <strong>and</strong><br />
<strong>Virtualization</strong><br />
<strong>Concepts</strong> <strong>for</strong> <strong>Safety</strong>-<br />
<strong>Critical</strong> <strong>Systems</strong><br />
Alex Wilson, Wind River, Director, EMEA Aerospace <strong>and</strong> Defence
SAVUNMA SANAYİİ MÜSTEŞARLIĞI<br />
Kalite – Test ve Sertifikasyon Daire Başkanlığı<br />
INTERAKTİF KOKPİT GÖRÜNTÜ<br />
SİSTEMLERİ ve SERTİFİKASYONU<br />
için YAZILIM YAKLAŞIMLARI<br />
<strong>ARINC</strong> <strong>653</strong> / DO-178C ve <strong>ARINC</strong> 661<br />
Tarih : 30 KASIM 2012<br />
Saat : 09:00-17:45<br />
Yer : SSM Sosyal Tesisleri<br />
PROGRAM :<br />
09:00 - 09:10 Açılış ve Konuşmalar<br />
09:10 - 09:30 Challenges Facing Aerospace <strong>and</strong> Defense Suppliers<br />
Alex Wilson, Wind River Director, Aerospace <strong>and</strong> Defence<br />
09:30 - 11:00 <strong>ARINC</strong>-<strong>653</strong> <strong>and</strong> <strong>Virtualization</strong> <strong>Concepts</strong> <strong>for</strong> <strong>Safety</strong>-<strong>Critical</strong> <strong>Systems</strong><br />
Alex Wilson, Wind River Director, Aerospace <strong>and</strong> Defence<br />
11:00 - 11:15 Çay-Kahve Molası<br />
11:15 - 13:00 Getting Ready <strong>for</strong> DO-178C<br />
Bernard Dion, Ph.D., Esterel Technologies Chief Technical Officer<br />
13:00 - 14:00 Yemek Arası<br />
14:00 - 15:00 Introduction to <strong>ARINC</strong> 661 St<strong>and</strong>ard<br />
Cockpit Display System Interfaces to User System<br />
Vincent Rossignol, Esterel Technologies Product Marketing<br />
Manager<br />
15:00 - 15:15 Çay-Kahve Molası<br />
15:15 - 17:30 An Implementation of <strong>ARINC</strong> 661 St<strong>and</strong>ard<br />
Vincent Rossignol, Esterel Technologies Product Marketing<br />
Manager<br />
17:30 - 17:45 Kapanış Konuşması – Soru ve Cevaplar<br />
Kayıt : event@tektronik.com.tr<br />
En iyisinin teminatı
<strong>ARINC</strong>-<strong>653</strong> <strong>and</strong><br />
<strong>Virtualization</strong> <strong>Concepts</strong> <strong>for</strong><br />
<strong>Safety</strong>-<strong>Critical</strong> System
Why virtualize?<br />
Consolidation<br />
(Merging or reducing several systems)<br />
Per<strong>for</strong>mance<br />
(Increase speed <strong>and</strong> functionality in existing system)<br />
Separation<br />
(Split existing functionality <strong>for</strong> safety <strong>and</strong>/or security)<br />
11<br />
| © 2012 Wind River. All Rights Reserved.
<strong>Virtualization</strong> <strong>and</strong> Partitioning<br />
Virtual Machine 1 Virtual Machine 2<br />
Application 1<br />
Application 2<br />
• Cores<br />
• Memory<br />
• Devices<br />
Guest Operating System 1<br />
Guest Operating System 2<br />
Virtual Machine Monitor (Hypervisor)<br />
Single or Multi-core Processor<br />
12<br />
| © 2012 Wind River. All Rights Reserved.
Avionics Consolidation Trend<br />
1980s 1990–2000 2010+<br />
Multicore Plat<strong>for</strong>m<br />
App<br />
App App App<br />
<strong>Virtualization</strong> Layer<br />
Core<br />
Core Core Core<br />
• One box<br />
• One function<br />
• One OS<br />
• One safety/security level<br />
• Federated systems<br />
• One board<br />
• Multiple functions<br />
• One OS<br />
• Multiple safety/security levels<br />
• Integrated Modular Avionics<br />
• One die<br />
• Multiple functions<br />
• Multiple OS<br />
• Multiple safety/security levels<br />
• Multi-core integration<br />
13<br />
| © 2012 Wind River. All Rights Reserved.
<strong>Virtualization</strong> <strong>and</strong> Avionics<br />
Avionics Bus:<br />
• <strong>ARINC</strong> 429/629<br />
• <strong>ARINC</strong> 664<br />
• MIL STD 1553<br />
• SAE AS6802<br />
Federated Avionics Computer:<br />
Inertial Reference System<br />
Integrated Modular Avionics (IMA) Computers:<br />
• Flight Management<br />
• Mission Computer<br />
• Displays (<strong>ARINC</strong> 661)<br />
• Navigation<br />
• Engine Monitoring<br />
• Fire Control<br />
• Stores Management<br />
• Targeting Computer<br />
Federated Avionics Computer:<br />
Flight Controls<br />
Federated Avionics Computer:<br />
Engine Controls<br />
Federated Avionics Computer:<br />
HUD/HDD (<strong>ARINC</strong> 661)<br />
Federated Avionics Computer:<br />
Weapons Controls<br />
Federated Avionics Computer:<br />
Sensor <strong>Systems</strong><br />
14<br />
| © 2012 Wind River. All Rights Reserved.
Federated <strong>and</strong> Integrated Modular Avionics<br />
Federated<br />
Advantages<br />
• High per<strong>for</strong>mance<br />
• Independence of design <strong>and</strong><br />
certification<br />
• Well-understood methodology<br />
• Established supply chain<br />
Challenges<br />
• Greater size, weight, <strong>and</strong> power<br />
(SWaP) requirements<br />
– Each function is separate LRU<br />
• Less software reuse<br />
• Less portability, less modularity<br />
• Cannot scale into larger plat<strong>for</strong>ms<br />
IMA<br />
Advantages<br />
• Lower SWaP requirements<br />
– Multiple functions on single LRU<br />
• Better software reuse, refresh<br />
• Better portability, modularity<br />
• More efficient plat<strong>for</strong>m certification<br />
Challenges<br />
• Greater complexity of system<br />
integration<br />
• Greater complexity of design <strong>and</strong><br />
certification<br />
• Less experienced supply chain<br />
Radar<br />
Flight<br />
Management<br />
Graphics<br />
Flight<br />
Management<br />
Radar<br />
Graphics<br />
Time <strong>and</strong> Space Partitioning<br />
<strong>ARINC</strong> <strong>653</strong> Operating System<br />
<strong>ARINC</strong> 429<br />
15<br />
| © 2012 Wind River. All Rights Reserved.
<strong>ARINC</strong> <strong>653</strong> <strong>for</strong> Integrated Modular Avionics<br />
• Goal: Reduce size, weight, <strong>and</strong> power (SWaP) requirements<br />
• <strong>ARINC</strong> <strong>653</strong>: Industry specification <strong>for</strong> Integrated Modular Avionics (IMA)<br />
• Includes API of 56 routines<br />
– Time <strong>and</strong> space partitioning<br />
– Inter- <strong>and</strong> intra-partition communications (IPC)<br />
– Health monitoring (error detection <strong>and</strong> reporting)<br />
• <strong>ARINC</strong> <strong>653</strong> OSs <strong>and</strong> applications are typically certified to DO-178C / ED-12C<br />
• RTCA/DO-297: Integrated Modular Avionics Development, Guidance <strong>and</strong> Certification,<br />
Shared set of flexible, reusable, <strong>and</strong> interoperable hardware <strong>and</strong> software resources<br />
Integrated Modular Avionics (IMA)<br />
Flight<br />
Management<br />
Radar<br />
Graphics<br />
Time <strong>and</strong> Space Partitioning<br />
<strong>ARINC</strong> <strong>653</strong> Operating System<br />
16<br />
| © 2012 Wind River. All Rights Reserved.
VxWorks <strong>653</strong> DO-178C <strong>and</strong> ED-12C<br />
Level A Certification Evidence Package<br />
• Plan <strong>for</strong> Software Aspects of Certification (PSAC)<br />
• Software Quality Assurance Plan<br />
• Software Configuration Management Plan (SCMP)<br />
• Software Development Plan (SDP)<br />
– Software requirements st<strong>and</strong>ards<br />
– Software design st<strong>and</strong>ards<br />
– Software coding st<strong>and</strong>ards<br />
• Software Verification Plan (SVP)<br />
• Software Requirements Specification (SRS) (7,000<br />
requirements)<br />
• Software Design Document (SDD)<br />
• Software Life Cycle Environment Configuration Index<br />
(SECI)<br />
• Traceability Matrix<br />
• Software Development Folder<br />
– Design reviews<br />
– VxWorks <strong>653</strong> source files <strong>and</strong> binary code<br />
– Code reviews (40,000 LOC)<br />
– Test reviews (7,500 tests)<br />
– Functional tests (270,000 LOC)<br />
– Coverage results (object level)<br />
• Software Accomplishment Summary (SAS)<br />
• Tools Qualification Documents (TQD)<br />
– Test Harness <strong>for</strong> VxWorks <strong>653</strong><br />
– VerOcode, VerOLink, VeroSource-A, VeroTrace<br />
– WindSH<br />
2.9GB sealed DVD with certification artifacts<br />
<strong>and</strong> more than 70,000 hyperlinked files<br />
17<br />
| © 2012 Wind River. All Rights Reserved.
VxWorks <strong>653</strong><br />
The Avionics Plat<strong>for</strong>m of the Future<br />
• First Flight: December 2010<br />
• FAA Certification: September 2011<br />
• GE Common Core certified to DO-178B Level A<br />
• Eliminated over 100 different LRUs<br />
• 17 Boeing suppliers, dozens of teams<br />
• DO-297 used <strong>for</strong> multi-vendor integration / re-use<br />
November 2012: VxWorks <strong>653</strong> leads the IMA industry with<br />
over 270 projects, used by over 150 customers in over 55 aircraft<br />
Photo by LongBachNguyen.com All Rights Reserved.<br />
18<br />
| © 2012 Wind River. All Rights Reserved.
The <strong>ARINC</strong> <strong>653</strong> st<strong>and</strong>ard<br />
• <strong>ARINC</strong> <strong>653</strong> Specification First Published <br />
• <strong>ARINC</strong> <strong>653</strong>P1-3 (Part 1 Supplement 3 Required Services) <br />
– <strong>ARINC</strong> <strong>653</strong> partition management<br />
– Cold start <strong>and</strong> warm start definition<br />
– Application software error h<strong>and</strong>ling<br />
– <strong>ARINC</strong> <strong>653</strong> compliance<br />
– Ada <strong>and</strong> C language bindings<br />
• <strong>ARINC</strong> <strong>653</strong>P2-2 (Part 2 Supplement 2 Extended Services) <br />
– Including File System, Logbook, Service Access points…<br />
• <strong>ARINC</strong> <strong>653</strong>P3 (Part 3 Con<strong>for</strong>mity Test Specification) <br />
– Supplement 1 in progress<br />
• Added <strong>ARINC</strong> <strong>653</strong> Part 4 (Subset Services) <br />
• New Proposal<br />
– Part 0 – Overview of APEX Services<br />
– Part 5 - Non-API Related O/S Capabilities (working title)<br />
19<br />
| © 2012 Wind River. All Rights Reserved.
<strong>ARINC</strong> <strong>653</strong> Scheduling<br />
• St<strong>and</strong>ards-based virtualization approach<br />
– "Virtual machine" approach as described in DOT/FAA/AR-99/58,<br />
Partitioning in Avionics Architectures: Requirements, Mechanisms <strong>and</strong><br />
Assurance, by John Rushby<br />
– <strong>Virtualization</strong> enables applications to run on partition OSs<br />
Partition 1 Partition 2<br />
Partition OS<br />
Partition OS<br />
Partition 1 Time Slice<br />
Partition 2 Time Slice<br />
Time<br />
20<br />
| © 2012 Wind River. All Rights Reserved.
IMA in the Real World - Lessons Learned<br />
• IMA systems can be extremely complex:<br />
– Large number of applications: 10+<br />
– Large application: 2,000,000+ lines of code, 4-8 MBytes<br />
– Large configuration data: 50,000+ configuration entries<br />
• Complexity must be managed to be successful<br />
– Roles <strong>and</strong> responsibilities have to be defined<br />
– Role activities have to be decoupled<br />
• Development cycles are shorter <strong>and</strong> shorter<br />
• Cost of change must be low<br />
– Introducing a change should have a low impact, even during the<br />
certification cycle<br />
– Must be scalable<br />
21<br />
| © 2012 Wind River. All Rights Reserved.
So what is DO-297 / ED-124?<br />
“Integrated Modular Avionics (IMA) Development<br />
Guidance <strong>and</strong> Certification Considerations”<br />
• Purpose:<br />
“..provides guidance <strong>for</strong> IMA developers, integrators, applicants, <strong>and</strong><br />
those involved in the approval <strong>and</strong> continued airworthiness of IMA<br />
systems. It provides specific guidance <strong>for</strong> the assurance of IMA<br />
systems as differentiated from traditional federated avionics”<br />
• Results of joint US/EU Study RTCA SC-200 <strong>and</strong> EUROCAE WG-60<br />
• Defines roles <strong>and</strong> responsibilities – Certification applicant, <strong>Systems</strong><br />
Integrator, Plat<strong>for</strong>m Provider, Application Developer<br />
• References RTCA DO-178B (EUROCAE ED-12B) <strong>and</strong> <strong>ARINC</strong> <strong>653</strong><br />
22 | © 2012 Wind River. All Rights Reserved.
Certification of IMA system<br />
From DO-297 :<br />
“Six tasks define the incremental acceptance of IMA systems in the certification process:”<br />
– Task 1: Module acceptance<br />
– Task 2: Application software or hardware acceptance<br />
– Task 3: IMA system acceptance<br />
– Task 4: Aircraft integration of IMA system – including Validation <strong>and</strong> Verification<br />
– Task 5: Change of modules or applications<br />
– Task 6: Reuse of modules or applications<br />
Key implementation <strong>and</strong> certification challenges:-<br />
• How to change application or configuration entities without affecting the entire<br />
system?<br />
– Without requiring re-testing or re-certification of other independent entities<br />
• How to reuse applications from one IMA project on the next IMA project?<br />
– Without having to re-write <strong>and</strong> re-test the entire application<br />
23 | © 2012 Wind River. All Rights Reserved.
Benefits of incremental certification<br />
• Development of applications independently<br />
• Ability to modify an application<br />
• Re-use of applications<br />
24 | © 2012 Wind River. All Rights Reserved.
DO-297/ED-124 certification stakeholders<br />
Certification Authority<br />
– Organization that grants approval on behalf of the state(s) responsible <strong>for</strong> the aircraft/engine<br />
certification<br />
Certification Applicant<br />
– Responsible <strong>for</strong> demonstrating compliance to applicable aviation regulations<br />
– Seeking TC, Amended TC, Supplemental TC or Amended STC<br />
System Integrator<br />
– Integrating the “plat<strong>for</strong>m” <strong>and</strong> “applications” to produce “IMA System”<br />
– System Configuration, Resource allocation, IMA V&V<br />
Plat<strong>for</strong>m Supplier<br />
– Provide processing hardware <strong>and</strong> software resources (including the core software)<br />
– Specify interfaces, shared resources, configuration tables<br />
– Plat<strong>for</strong>m V&V<br />
Application Supplier<br />
– Develops “Hosted” applications <strong>and</strong> verifies on “plat<strong>for</strong>m”<br />
– Specifies external interfaces <strong>and</strong> resource requirements of application<br />
25 | © 2012 Wind River. All Rights Reserved.
Independent software delivery / DO-297<br />
Supplier 1 Supplier 2 Supplier 3 Supplier 4<br />
IMA System<br />
Integrator<br />
User<br />
Mode<br />
Flight<br />
Management<br />
Application<br />
Level A<br />
Radar<br />
Application<br />
Level B<br />
Graphics<br />
Generator<br />
Application<br />
Level C<br />
Display<br />
Application<br />
Level D<br />
Application<br />
Suppliers<br />
<strong>ARINC</strong> <strong>653</strong><br />
Partition OS<br />
POSIX<br />
Partition OS<br />
VxWorks<br />
Partition OS<br />
Ada/Java<br />
Partition OS<br />
Plat<strong>for</strong>m<br />
Supplier<br />
VxWorks <strong>653</strong><br />
Application Executive<br />
Architecture Support<br />
Package (ASP)<br />
XML Configuration Data<br />
Board Support<br />
Package (BSP)<br />
Kernel<br />
Mode<br />
Hardware<br />
26<br />
| © 2012 Wind River. All Rights Reserved.
XML Table Generator <strong>for</strong><br />
Review of Configuration Data <strong>for</strong> Credit<br />
Plat<strong>for</strong>m<br />
Supplier<br />
XML Tables<br />
XML Config<br />
File<br />
System<br />
Integrator<br />
XML Tables<br />
XML Config<br />
File<br />
FMS<br />
XML Tables<br />
XML Config<br />
File<br />
Application<br />
Suppliers<br />
Nav<br />
XML Tables<br />
XML Config<br />
File<br />
Display<br />
XML Tables<br />
XML Config<br />
File<br />
XML Compiler/Checker<br />
DO-178 Qualified Development Tool<br />
XML Business<br />
Rules<br />
Plat<strong>for</strong>m<br />
Data<br />
Schedule<br />
Tables<br />
HM Table<br />
HM Table<br />
HM Table<br />
FMS<br />
Nav<br />
Display<br />
Reviewers, DERs <strong>and</strong> Certification Authorities<br />
27<br />
| © 2012 Wind River. All Rights Reserved.
New FAA Policy:<br />
Reusable IMA Components<br />
• Advisory Circular AC 20-170*, October, 2010<br />
– “Integrated Modular Avionics Development, Integration,<br />
Verification <strong>and</strong> Approval Using RTCA DO-297 <strong>and</strong> TSO C153”<br />
• Technical St<strong>and</strong>ard Order C153**: IMA Hardware Elements<br />
– Allows <strong>for</strong> reuse of previously “accepted” IMA components<br />
• Applications, OSs <strong>and</strong> hardware<br />
• Software accepted by the FAA as meeting DO-297<br />
objectives across IMA plat<strong>for</strong>ms<br />
– Allows <strong>for</strong> “portability” of certification ef<strong>for</strong>t to other products<br />
without full re-verification of unmodified software components<br />
* http://www.faa.gov/regulations_policies/<br />
** http://rgl.faa.gov/Regulatory_<strong>and</strong>_Guidance_Library/rgTSO.nsf/Frameset?OpenPage<br />
28<br />
| © 2012 Wind River. All Rights Reserved.
IMA Acceptance Supports Multiple<br />
Approvals by reducing time/ef<strong>for</strong>t<br />
IMA Cabinet with<br />
Applications, TSO<br />
C153 Hardware <strong>and</strong><br />
VxWorks <strong>653</strong><br />
Same Hardware <strong>and</strong><br />
OS reused in<br />
different<br />
configurations<br />
Certified applications<br />
approved in different<br />
configurations using<br />
VxWorks <strong>653</strong><br />
29<br />
| © 2012 Wind River. All Rights Reserved.
What is Multi-Core?<br />
• Architecture where a single physical<br />
processor contains the core logic of two<br />
or more processors<br />
• Packaged into a single integrated circuit<br />
(IC) called a die<br />
– Can also refer to multiple dies packaged<br />
together<br />
• Multi-core enables the system to<br />
per<strong>for</strong>m more tasks with a greater<br />
overall system per<strong>for</strong>mance<br />
30 | © 2012 Wind River. All Rights Reserved.
Why use Multi-core in Avionics?<br />
• Embrace the future!<br />
• Dem<strong>and</strong> <strong>for</strong> more power<br />
• Pervasiveness of multi-core silicon<br />
• <strong>Virtualization</strong> <strong>for</strong> Multi-OS designs<br />
• Ability to separate applications<br />
– Security <strong>and</strong> safety separated too<br />
31 | © 2012 Wind River. All Rights Reserved.
Multicore configurations<br />
Single Core<br />
“Traditional”<br />
OS<br />
Core<br />
Core <strong>Virtualization</strong><br />
OS OS<br />
Hypervisor<br />
Core<br />
SMP<br />
Unsupervised AMP<br />
Supervised AMP (sAMP)<br />
Multi-core<br />
OS<br />
Core 1 Core 2<br />
OS<br />
Core 1<br />
OS<br />
Core 2<br />
OS OS<br />
Hypervisor<br />
Core 1 Core 2<br />
32<br />
| © 2012 Wind River. All Rights Reserved.
<strong>Safety</strong> & multicore<br />
• Consolidation of safety-critical applications through IMA<br />
– <strong>ARINC</strong> <strong>653</strong> dominant<br />
• Consolidation of uni-processor systems onto multicore<br />
• Suitable approaches <strong>for</strong> safety-critical multicore systems<br />
– SMP:<br />
• Pros: attractive model<br />
• Cons: loss of determinism in multicore environment<br />
– AMP:<br />
• Pros: can be used with a Hypervisor to partition shared resources,<br />
support multiple applications at different levels of criticality<br />
• Cons: still need to prevent coupling through shared resources<br />
33 | © 2012 Wind River. All Rights Reserved.
Typical Single Core architecture<br />
- <strong>ARINC</strong> <strong>653</strong><br />
User<br />
Mode<br />
Flight<br />
Management<br />
Application<br />
Radar<br />
Application<br />
Graphics<br />
Generator<br />
Application<br />
Display<br />
Application<br />
Level A<br />
Level B<br />
Level C<br />
Level D<br />
<strong>ARINC</strong> <strong>653</strong><br />
Partition OS<br />
POSIX<br />
Partition OS<br />
VxWorks<br />
Partition OS<br />
Ada/Java<br />
Partition OS<br />
VxWorks <strong>653</strong><br />
Application Executive<br />
Architecture Support<br />
Package (ASP)<br />
XML Configuration Data<br />
Board Support<br />
Package (BSP)<br />
Kernel<br />
Mode<br />
CPU<br />
Ethernet<br />
GPU<br />
Memory, other I/O<br />
34<br />
| © 2012 Wind River. All Rights Reserved.
Multi-core:<br />
Electronic Flight Bag Use Case<br />
DO-178 Level A<br />
DO-178 Level C<br />
DO-178 Level E<br />
DO-178 Level E<br />
App 1<br />
Server App<br />
VxWorks<br />
App 2<br />
Server App<br />
Linux<br />
App 3<br />
Server App<br />
OS TBD<br />
App 4<br />
Server App<br />
Android<br />
Hypervisor<br />
Core 1 Core 2 Core 3<br />
Ethernet<br />
GPU<br />
Flash<br />
35 | © 2012 Wind River. All Rights Reserved.
Typical IMA Design:<br />
Hardware <strong>and</strong> Software<br />
Typical Hardware<br />
Modules<br />
Typical Software<br />
Modules<br />
Common<br />
Hardware<br />
Back Plane<br />
Power Supply<br />
CPU & Memory<br />
Real Time Executive<br />
Built-in Test<br />
On-board<br />
Maintenance<br />
System Protocol<br />
Common<br />
Software<br />
Data Bus<br />
I/O Processing<br />
Application<br />
Specific Software<br />
Application<br />
Specific Hardware<br />
I/O<br />
Application<br />
Shaded areas show potential shared resources<br />
36<br />
| © 2012 Wind River. All Rights Reserved.
<strong>Safety</strong> Considerations<br />
Some Challenges to Multiple <strong>Critical</strong>ities<br />
– No policies <strong>and</strong> guidance<br />
– Different multi-core implementations<br />
– Shared caches<br />
• Loss of determinism, cross channel coupling<br />
– Shared bus contention<br />
• Loss of determinism, cross channel coupling<br />
– Exception redirection<br />
• Exceptions may be directed to one core<br />
– Time management<br />
• Clock interrupt may be directed to one core<br />
37 | © 2012 Wind River. All Rights Reserved.
VxWorks Safe & Secure Plat<strong>for</strong>m<br />
Operating Environments<br />
Development<br />
Lifecycle Solutions<br />
Wind River Professional Services<br />
Wind River Global Support<br />
VxWorks<br />
Cert<br />
Incl APEX<br />
Real-Time<br />
Hypervisor<br />
Profile<br />
VxWorks<br />
Wind River<br />
Linux<br />
Separation Profiles<br />
<strong>Safety</strong><br />
v<br />
Separation<br />
Profile<br />
<strong>ARINC</strong> <strong>653</strong>, DO-178C, IEC 61508<br />
Other<br />
OS<br />
Security<br />
Separation<br />
Profile<br />
MLS/CDS<br />
Wind River<br />
Simics<br />
Wind River<br />
Test<br />
Management<br />
Wind River<br />
Workbench<br />
Architecture Support: Single <strong>and</strong> Multicore<br />
38<br />
| © 2012 Wind River. All Rights Reserved.
Summary<br />
• Trends<br />
– Consolidation<br />
– Interoperability<br />
– Regulatory<br />
• <strong>ARINC</strong> <strong>653</strong> St<strong>and</strong>ard<br />
• DO-297 / ED-124<br />
• Multicore<br />
• Safe <strong>and</strong> Secure Plat<strong>for</strong>m<br />
39<br />
| © 2012 Wind River. All Rights Reserved.
Change language