ECU SW-Development grows up from small legacy solutions to Virtual Machines

Transcription

1 ECU SW-Development grows up from small legacy solutions to Virtual Machines ECU-Technology & Development discover Virtual Machines Theo Voss, Steffen Herz Stuttgart, November 2016 HF-7761EN_C ( )

2 Introduction ECU-Design from History to Future Microcontroller Generations Resource consumption growths System- / SW-Architecture demands Virtualization challenge and demand in future Introduction Motivation Implementation as challenge Summary 2

3 ECU-Design from History to Future Microcontroller Design in mirror of history What was first, user requirements or HW technology? Code / KB Bit Tricore 32-Bit Multicore ARM Performance increase with x-bit space Frequency increase with HW-Design structures (300 -> 28 nm) Bit Dualcore Single Core versus Multicore v 8/16-Bit 32-Bit RAM-Space increase with feature parameter Bit 16-Bit Application execution in ROM or RAM

4 ECU-Design from History to Future Evaluation Overview (Microcontroller Resources) 1) OSEK 2) No. ECUs increase 3) AUTOSAR is established ) Service (ETH) oriented architectures extend com. 5) ECU Domain Solutions in use 6) Virtual Machines Evolution in dependency of features, technology, cost and social demands 4

5 ECU-Design from History to Future System- / SW-Architecture - Generation 1 Appl. Appl. Appl. Appl. Appl. Appl. Appl. Services OSEK Communication Standards Abstraction Handler Low Level Driver Microcontroller Layered Architecture Standard Services Standard Communication 5

6 ECU-Design from History to Future System- / SW-Architecture - Generation 2 Appl. Appl. Appl. Appl. Appl. Appl. Appl. Application COM-Layer Services OSEK Communication Standards Abstraction Handler Low Level Driver Microcontroller Layered Architecture Standard Services Standard Communication Standardized Application Interfaces 6

7 ECU-Design from History to Future System- / SW-Architecture - Generation 3 Appl. Appl. Appl. Appl. Appl. Appl. Appl. RTE Services OSEK Mem Standards Com Standards Abstraction Handler Low Level Driver CD Microcontroller Layered Architecture Standard Services Standard Communication Standardized Application Interfaces Automotive Standards 7

8 Introduction ECU-Design from History to Future Microcontroller Generations Resource consumption growths System- / SW-Architecture demands Virtualization challenge and demand in future Introduction Motivation Implementation as challenge Summary 8

9 Virtualization challenge and demand in future Virtualization a future technology? Introduction Full Virtualization Virtual Machines with own OS e.g. AUTOSAR / LINUX Hypervisor OS is interface to HW 1-> n HW Cores possible VM 1 AUTOSAR VM 2 LINUX VM 3 xxx Interrupt Handling with Hypervisor OS only Time Slice Scheduling by HV Encapsulation via MMU Hypervisor Inter Process Communication Core 0 Core 1 Core n 9

10 Virtualization challenge and demand in future Motivation for Virtualization Innovation driven by software functionality Hosting of various Operating systems (e.g. AUTOSAR OS and LINUX) Feature updates in shorter cycles Isolation / Encapsulation of applications Feature extensions without new ECU-Design Dynamic allocation of memory EE-Architecture innovation by new communication technologies Master the complexity increasing 10

11 Virtualization challenge and demand in future Implementation as challenge with todays Real Time demands HW- (microcontroller) design is important for success, e.g. Microcontroller design with MPU / MMU Amount of microcontroller cores Peripheral IO-Design at microcontroller Interrupt and exception behavior RAM-Resources ROM-/Flash-Resources System cost Today, there is no final design in market; depends on use cases, several solutions are in evaluation 11

12 Virtualization challenge and demand in future Use Case 1: Hosting of various Operation Systems Reason, Infotainment System can use range of available SW in market Virtual Machines are complete independent from each other VM - use case dependent OS Applications for LINUX / Android OS on market can be used World of new SW products is available with short time to market 12

13 Virtualization challenge and demand in future Use Case 2: Isolation / Encapsulation of applications Isolation between secure and unsecure partitions Freedom of Interference between different ASIL partitions Virtual Machines are complete independent from each other Memory write only from ASIL -> QM, e.g. shared memory No read / write access to secure partitions, also for code 13

14 Virtualization challenge and demand in future Use Case 3: Feature updates / extension V2.0 Virtual Machines are complete independent from each other VM has own memory and time budget VM 1 VM 2 VM 3 V1.3 VM-new VM themselves is qualified and certificate New VM (new feature) with interface to Hypervisor is possible Hypervisor Core 0 Core 1 Core n 14

15 Virtualization challenge and demand in future Use Case 4: Feature allocation (for every Virtual Machine a core) Virtual Machines are complete independent from each other VM has own memory and time budget VMs contains AR-Stacks VMs with different AR-Versions VM is allocated to one core 15

16 Virtualization challenge and demand in future Use Case 5: Microcontroller cores optimized for feature implementation Virtual Machines are complete independent from each other VM has own memory and time budget VMs allocated on feature implementation (e.g. COM as board net interface) VM for IO-Design VMs for application 16

17 Virtualization challenge and demand in future Conclusion Virtualization (Hypervisor) is a technology for the future Isolation / Encapsulation offers independent development and certification streams for safety and security Feature update is more flexible Challenges HW-Design of Microcontroller for low end solution needs targets / standards Inter process communication (e.g. services oriented or shared memory) System Configuration Tooling is success key factor 17

18 HF-7761EN_C ( ) Thank You!