Open Source Tools for Embedded Systems
Industrial Working Group
SAE AeroTech Congress September 24, 2013
About me
Tool Manager at Ericsson Telecom System • Open, standards-based common
platform • 99.99999% uptime standards • Broad range of support for both
infrastructure and value-added applications
• Network, multimedia, application processing capabilities
PolarSys Presentation Template 4
Toolkit in OPen Source for Critical Applications & SystEms Development
PolarSys Tool Landscape
Discipline Requirement System Engineering/Design SW/HW Development Quality Configura=on Management Test / Verifica=on & Valida=on Maintenance Process Field Engineering / Monitoring
Tool Type Modeling: DSL, UML, SysML Compiler, Debugger, Tracer Sta=c Analysis Simula=on/Emula=on Integrated Development Environment
SW Configura=on Management
Issue Tracker
Project Repor=ng, Documenta=on
8
SoNware Tools for Reliable Embedded Systems
PolarSys Tool Landscape
Tool Type Modeling: DSL, UML, SysML Compiler, Debugger, Tracer
Sta=c Analysis
Simula=on/Emula=on Integrated Development Environment
SW Configura=on Management
Issue Tracker
Project Repor=ng, Documenta=on
Tool Example Papyrus, Sirius GCC/Clang, GDB, LTTng LLVM Clang, Frama-‐C QEMU Eclipse CDT EGit, Gerrit
Tuleap
Sonar, Intent
9
SoNware Tools for Reliable Embedded Systems
Tool Example: System Modeling
10
CSDM 2010, Jean-‐Luc Voirin, "Model-‐driven Architecture building for constrained Systems"
Open source
Tool Example: Debugging
MI protocol
Target
Host
Open source
Open source applicable to all
target OS
Open source applicable to all
target OS
Simulator
Linux GDB Stub
Bare Metal / JTAG
Proprietary GDB Stubs
GDB Remote Protocol
GDB
Emulator
Proprietary code QEMU
11
• Open Innova=on • Commercial services around open source components
• Quality and maturity of tools • Fostering exchanges between academics and industrial partners
• Very Long Term Support
• Documents and qualifica=on kits required for cer=fica=on DO178, ISO26262, ECSS 40, etc.
PolarSys Ecosystem Eclipse Working Group
12
PolarSys Ecosystem Eclipse Working Group
• Legal agreement to share intellectual property rights
• Ability to pool resources to innovate on new technologies and standards
• Project governance and process to ensure a level playing field
• IT infrastructure to facilitate collabora=on between a distributed team
• A technology plaaorm
• Marke=ng & Communica=on 13
14
Value Added Resellers
Academics
Other Open Source
Contributors
Service Providers
End User Companies
Tool Vendors
Specifica=on Consor=um
PolarSys Ecosystem Eclipse Working Group
Closed Innovation Drawbacks
Adaptations are unsustainable with closed data format
Some innovations do not have a business case for tool vendors
Industrial users end up paying large amounts for improvements which can then be used by competitors who have a normal license cost
18
Mastering? Continuity?
Product strategy change, products may also vanish
Niche tool vendors may get acquired by larger companies, disappear or change their technical focus
19
Control and Secure your Destiny!
Typically less than 20% of Requests For Enhancement (RFE) get into the tool
Proprietary Tool Vendor Ecosystem
100 % of RFE are able to get into the tool e.g. 80% generic, 20% as user extensions
PolarSys Open Source Ecosystem
Tool Vendor
End User Requests
End User Requests
End User Requests
End User Requests
End User Requests
No lock-‐in! You or many third party can add features
Value Added Resellers
Academics
Other Open Source
Contributor
Service Providers
End User Companies
Tool Vendor
s
Specifica=on Consor=um
20
Open Source Software Facilitates
• Interoperability
• Creation of de facto standards
• Migration
• Extensibility
• Open Innovation
21
Better Features
Open Innova=on paradigm treats R&D as an open system
Mixing firms external ideas with internal ideas, e.g. IBM 500 US patents for Linux
Designing with experts from different companies equals be#er features
22
Internal Synergies
Protects investment in improvements projects
Synergies between development, services, research, etc.
The whole is greater than the sum of its parts
23
Open Source or Commercial?
PolarSys tools give you both!
Open Source with: • commercial support • commercial bug fixes • commercial contract to
add features
• etc.
24
Make or Buy?
25
PolarSys tools give you both!:
• In one project you buy a PolarSys tool from a supplier
• In the next project you can make your own very specialized feature in the same tool
Aeronautics Long Life Cycle AIRBUS A300 Life Cycle Program began in 1972, produc=on stopped in 2007 2007-‐1972 = 35 years... Support will last un=l 2050
2050-‐1972 = 78 years!
On board soVware development for very long lifecycle products
Embedded System Development Cost Structure
Help build it in open source, even with your direct compe=tors Infra
Value Focus on Value Compete on Products
Selling Features
Operating System Tools
Programming Language
etc.
Large costs can go to build and support infrastructure for which companies derive zero differen=a=ng product value.
27
Better Support
Direct access to developer and large open source community
Same people developing the adapta=ons are developing the main product and handling support.
Fast availability of bug fixes and workarounds
28
Accessibility, Learning Curve
Proprietary tools are some=mes too expensive for some R&D units and specially for service units
Using same tools across R&D and services for the same product speeds up the service area
De-‐facto in industries, universi=es: -‐ people already know how to use -‐ mandate transfer made easier -‐ acquiring companies made easier
29
FULL Speed Innovation
Controlling our own destiny
Learning Curve, Accessibility
↓Cost ↑Improvement Budget
Re-Use, faster development
Innovation, advanced feature
More Features, Empowerment
30
Open Source & Industry
Open
Source
Individual Driven Hackers (1980)
Tool Vendor Driven Framework (2000)
Industrial User Driven Feature Completeness, Speed
Long Term Availability, Quality (2010)
32
Speed Really Matters? In 2012, SpaceX Dragon spacecraN became the first privately developed vehicle in history to successfully akach to the Interna=onal Space Sta=on
33
SpaceX did not exist before 2002! Open source in avionics, naviga=on, control systems spacecraN
Open Source Rules • Openness Everyone can participate under the same rules
• Transparency Project discussions, minutes, deliberations, project plans, plans for new features, and other artifacts are open, public, and easily accessible.
• Meritocracy Becoming a committer or accepting your code depends on peer review and voting by your peers
37
Open Source Definition • Free Redistribution • Free Source Code • Free Derived Works • Integrity of The Author's Source Code • No Discrimination Against Persons or Groups • No Discrimination Against Fields of Endeavor • Distribution of License • License Must Not Be Specific to a Product • License Must Not Restrict Other Software • License Must Be Technology-Neutral
38