Safe and Seamless Integration of Tegra into the In-Vehicle Network Stefaan Sonck Thiebaut, OpenSynergy

Transcription

1 Safe and Seamless Integration of Tegra into the In-Vehicle Network Stefaan Sonck Thiebaut, OpenSynergy

2 OpenSynergy OpenSynergy is a global provider of software solutions for embedded automotive systems. OpenSynergy s core product portfolio consists of the key software components necessary to create efficient automotive solutions in the areas of: Infotainment onnectivity Driver Information Driver Assistance 2

3 OpenSynergy Product Portfolio Products Engineering OQOS SDK The standards-based OQOS software platform is the basic technology underpinning all OpenSynergy solutions ar2infrastructure Model-based telematics stack Backend system simulation End-to-end security solutions Blue SDK Leading independent Bluetooth stack Voice SDK Voice band audio processing Development and Integration AUTOSAR software systems Architecture and software design Implementation and integration Board support packages Update SDK Versatile software update mechanism for embedded devices Support Standard support for OpenSynergy s products Access to product updates 3

4 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 4

5 Automotive Trends & hallenges onvergence onnected ar Instrument luster Head Unit ADAS onnectivity Integration on a few EUs / SOs Safety & Security Standardization 5 Towards autonomous driving

6 Possible Software Architecture of Future Automotive EUs SW Update System State Driver Assistance System Resource Management Shared drivers Infotainment Applications OEM-controlled Applications, e.g Instrument luster Real-time Applications Virtualization / Hypervisor GPU Hardware Typically: Multi-ore ARM ORTEX with powerful GPU 6 cloud Other Vehicle Systems

7 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 7

8 Development Partnership AUTOSAR ( Defines the software architecture and development methodology for automotive EUs. AUTOSAR Partners (March 2014) 8 from Up-to-date Global status Automotive see: E/E Standard, Rick Flores, General Motors, presented at Open Architecture Summit, Nov 4, 2014

9 AUTOSAR Defines 1. software architecture of automotive devices 2. methodology to configure automotive devices 3. application interfaces. 9

10 AUTOSAR Software Architecture mages/media_pictures/autosarcomponents-and-inte.jpg 10

11 11

12 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 12

13 Targets of the project Facilitate integration of Tegra into the in-vehicle AN network (through MU) Allow use of AUTOSAR methodology to configure the integration in the vehicle bus ontrol information flow between non-autosar and AUTOSAR partitions Integrate the configuration & build process into the Vibrante SDK Make it possible to run AUTOSAR Software-omponents (applications) on Tegra Allow the integration of OEM-specific AUTOSAR variants on Tegra Take advantage of virtualization/hypervisor technology 13

14 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 14

15 High-Level oncept AF AF OS Inter-Processor ommunication So AUTOSAR AUTOSAR SW- MU AUTOSAR BSW AN ommunication Additional I/O Power Management Hypervisor MAL Nano AUTOSAR Framework NVIDIA Tegra K1 MU 15 AF = Automotive ommunication Framework BSW = Basic-Software (AUTOSAR Infrastructure Software) SW- = Software omponent (AUTOSAR Application Software) MAL = Microcontroller Abstraction Layer (Drivers) OS = Operating System AN I/O

16 Use ase 1: ommunication to Vehicle Bus AF AF OS Inter-Processor ommunication So AUTOSAR MU Application AN Gateway AN ommunication Additional I/O Power Management Hypervisor MAL Nano AUTOSAR Framework NVIDIA Tegra K1 MU 16 AN I/O

17 Inter-Processor ommunication AF AF OS Use ase 2: Integration of OEM Applications So AUTOSAR MU Application AUTOSAR SW- RTE AUTOSAR BSW with OEM Specifics AN communication Additional I/O Power Management Hypervisor MAL Nano AUTOSAR Framework NVIDIA Tegra K1 MU 17 AN I/O

18 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 18

19 Overall Process AUTOSAR System Information TEGRA image onfigure onfiguration Generate ode Build Flash Run Other Applications MU image Other Vibrante SDK Elements 19

20 Overall Process AUTOSAR System Information TEGRA image onfigure onfiguration Generate ode Build Flash Run Other Applications MU image Other Vibrante SDK Elements 20

21 onfiguration and ode Generation OpenSynergy ode Generators onfigure AN Generate AN AN ode (So and MU) ARXML AUTOSAR Editor onfigure OS onfigure AF EU onfiguration Generate OS Generate AF OS ode (So) AF ode (AUTOSAR and Linux) onfigure AN Gateway Generate AN Gateway AN Gateway ode 21

22 Examples of configuration items onfigure AN AN system (including MU) AN speed hardware filtering OpenSynergy ode Generators Generate AN AN ode (So and MU) AUTOSAR Editor onfigure OS onfigure AF Scheduling behavior ARXML on the TEGRA EU onfiguration Generate OS Availability of signals in other partitions (like Linux) Generate AF OS ode (So) AF ode (AUTOSAR and Linux) onversion of AN frames to/from logical signals Timing behavior of outgoing AN frames onfigure AN Gateway Generate AN Gateway AN Gateway ode 22

23 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & Tools Demonstration Summary 23

24 Demonstration 24

25 Development Scenario Example AR ARXML arxml Add new AN MSG and Signal Updated onfigurations arxml Generate (command Line) /H Files /H Build Flash Image MOVIE 25

26 Agenda Background on automotive trends & challenges Background on AUTOSAR Targets of the project Architecture Process & tools Demonstration Summary 26

27 Summary Future versions of Vibrante SDK will include support for AUTOSAR and AN-integration. Solution consists of: MU running nano-autosar handling AN, IO, power management AUTOSAR partition on Tegra handling AN processing, AUTOSAR basic-software functionality and applications Automotive ommunication Framework for communication to non-autosar operating systems Tooling integrated in Vibrante. 27

28 ontact OpenSynergy GmbH Rotherstraße 20 D Berlin Germany Phone Web OpenSynergy GmbH Starnberger Str. 22 D Gauting / Munich Germany Phone bluetooth@opensynergy.com OpenSynergy, Inc. (USA) 765 East 340 South Suite 106 American Fork, Utah Phone bluetooth@opensynergy.com OpenSynergy, OQOS SDK, Blue SDK, IrDA SDK, Voice SDK, Update SDK, Qonformat, and other OpenSynergy products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of OpenSynergy GmbH in Germany and in other countries around the world. All other product and service names in this document are the trademarks of their respective companies. These materials are subject to change without notice. These materials are provided by OpenSynergy GmbH for informational purposes only, without representation or warranty of any kind and OpenSynergy GmbH shall not be liable for errors or omissions with respect to the materials. OpenSynergy GmbH