Adding AUTOSAR. Communications to GENIVI Linux. Ricardo Anguiano Technical Marketing Engineer. All Members Meeting. Burlingame October 19, 2016

Transcription

1 Adding All Members Meeting Communications to GENIVI Linux Burlingame October 19, 2016 Ricardo Anguiano Technical Marketing Engineer

2 Why should I care about? Q: A: I care about IVI. excludes IVI. Why should I care? Auto manufacturers are seeing the need to interface their complex ECUs, like IVI, into an environment. This presentation focuses on this need.

3 Automotive Industry Direction Electrification EV/PHEV Autonomous Driving 3 Domain Consolidation: Mature Functionality Moves to Powerful ECUs

4 Focal Areas Increase Productivity Time to Market Standardized Software Engineering Process Platform Reuse Methodology More Like Mobile Phones 4

5 Briefly What is? is a partnership, not unlike GENIVI: 202 members: core, premium, associate and development partners. addresses increasing complexity and R&D costs through well defined interfaces, abstractions and software reuse. Cooperate on standards, compete on implementation

6 Vehicle Design Engineering Process Methodology at OEMs Vehicle Functions ECU Extract System Database ECU Extract System Design ECU Extract Architecture Tooling 6

7 ECU Design Engineering Process Configuring an 4.2 ECU SW-Cs BSW ECU Generated API Diagnostics Communication ECU Extract OS / MCAL 7

8 on Linux Reuse Standardized Software Vehicle System API Access Enabler 8

9 Linux App A Linux SMP on SoC Linux AoL App Linux App B AoL ACL SW-C IPC Proxy SW-Cs Architecture VSTAR BSW Linux ACL MCAL Layer App B Linux drivers / System functions IPC Mechanisms Block Drivers Com Drivers App Runtime Automotive Ethernet 9

10 SoC LINUX µc LINUX SoC LINUX SoC Start Up Availability AoL Single SoC BOM Flexible Real Time Response Deployment LINUX LINUX Smaller BOM SoC SoC COM Buses in µc On Chip IPC µc Lower Engineering Effort No External IPC Delay 10

11 Splittable ECU Extract ECU Extract AoL Architecture Solutions Diagnostics Proxy Diagnostic Master and Proxy Diagnostic Client Routable Communication Buses ECU Extract ECU Extract AoL µc LINUX SoC 11 Ethernet CAN

12 OEM Benefits Inclusion of Linux nodes in methodology Standardized interface for inter-connecting ECUs Standard ECU definition and information exchange with Tier 1 suppliers Supplier Benefits Can cut BOM on SoC Standard software platform and methodology for ECU development 12

13 Demo: AoL with Diagnostics over IP (DoIP) on GENIVI Linux Ethernet diagnostics Linux Infotainment applications Type 1 Hypervisor Infotainment Linux Guest OS Linux Guest OS Mentor Embedded Hypervisor Intel x86 MinnowBoard MAX mentor.com/embedded-software/automotive 13

14 AoL: What is the point? Preserve investments in Reuse Software Components (SW-C) Ensure Consistent Behavior Augment Linux with functionality: diagnostics, vehicle system communication, mode management (Off, Accessory, Ignition) Expose standard interfaces between Linux and Increased design flexibility

15 Adaptive : Future Directions, Speculative 2017 Expected First Release of Adaptive Targeting V2X and AD Requires Functional Safety Runs on Computational Nodes Limited POSIX SOME/IP Service Oriented

16 Classic vs Adaptive Classic XML configuration of System and ECUs Detailed Software specifications Static configuration (once in car, functionality does not change) Adaptive XML configuration of System and ECUs Only interface specifications Will release Implementations Service oriented dynamic behavior

17 AoL Compliment to Classic and Adaptive Platforms Classic Platform Standard ECUs Real time Low Cost Adaptive Platform Computational nodes Ethernet/CAN Limited POSIX on Linux High end ECUs Full Linux/POSIX Rich Applications