Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Satish Varma,
Director of Technology and New Business, U.S.
September 26, 2013
Separation Using Type-1 Virtualization
Pres...
Red Bend Software Background
• Founded in 1999 with a novel approach to remote software updating
• Entered Mobile industry...
• Run multiple OSs on the same platform
• The challenges:
– Enable some, or all OSs to use the
device’s peripherals
– Supp...
• The pressure to consolidate car ECUs and head units drives
the need to use virtualization on future embedded platforms
•...
Virtualization Potential
5
RTOS
Digital Cluster, ADAS
IVI
Rear-seat
entertainment
• Modern head-units have ~10s of
peripherals
• Hardware peripherals and software
drivers are not designed to be shared
• T...
Architecture Overview
Apps
Apps
vOGL
FE
vEGL
FE
vAlloc
FE
vDisp
FE
WS
vOGL
BE
vEGL
BE
vAlloc
BE
vDisp
BE
WSAllocEGL
Displa...
Configuration with Two Displays
Apps
vOGL
BE
vEGL
BE
vAlloc
BE
vDisp
BE
WSAllocEGLOGL
Off screen memory rendering
Physical...
Considerations
• An excellent solution for reducing hardware costs
– Separate OSs for each functional area
– Separate CPU ...
Cluster+Infotainment Graphics
Use Case demo
• TI hardware
– OMAP5432 uEVM
• QNX Platform Software
– QNX CAR 2.1 for OMAP5,...
Satish.Varma@redbend.com
12
Upcoming SlideShare
Loading in …5
×

Red Bend Software: Separation Using Type-1 Virtualization in Vehicles and Automotive Devices

3,108 views

Published on

Satish Varma from Red Bend Software presents at TI Tech Day Detroit 2013 on how to use Type-1 virtualization to consolidate hardware in automotive ECUs. Panelists included QNX Software Systems and Crank Software.

Published in: Technology, Business
  • Be the first to comment

Red Bend Software: Separation Using Type-1 Virtualization in Vehicles and Automotive Devices

  1. 1. Satish Varma, Director of Technology and New Business, U.S. September 26, 2013 Separation Using Type-1 Virtualization Presented at TI Tech Day Detroit Session: “Accelerated Graphics in virtualized and non-virtualized environments on Jacinto 6 and OMAP5 SoC” 1 Presenters:
  2. 2. Red Bend Software Background • Founded in 1999 with a novel approach to remote software updating • Entered Mobile industry in 2003 to solve complex problem of over- the-air software management, expanded to M2M and Automotive in 2007 • Innovated with smallest delta file size, fastest updates, instant fail- safe and background updates, making Red Bend the most trusted mobile software management company • In Sept. 2010, acquired VirtualLogix, the leader in Mobile Virtualization, to bring greater security to the next generation of smart devices • Today, 1.75 Billion smartphones, tablets, M2M devices and connected vehicles are Red Bend-Enabled™ 2
  3. 3. • Run multiple OSs on the same platform • The challenges: – Enable some, or all OSs to use the device’s peripherals – Support close-to-native performance – Securely separate the OSs – Minimize the disruption on the customer development process What is Virtualization? 3 Hardware Hardware OS1 App OS2 App vLogix Mobile® (vLM) vLogix Mobile® acts like an OS scheduler
  4. 4. • The pressure to consolidate car ECUs and head units drives the need to use virtualization on future embedded platforms • Embedded systems are optimized for a Type 1 virtualization solution • Red Bend Type 1 hypervisor provides: – Swift integration with current Cortex A9 – OOTB integration with Cortex A15 – Minimal performance degradation – Security & Separation Why Use Virtualization in Automotive? 4
  5. 5. Virtualization Potential 5 RTOS Digital Cluster, ADAS IVI Rear-seat entertainment
  6. 6. • Modern head-units have ~10s of peripherals • Hardware peripherals and software drivers are not designed to be shared • The solution: – One OS physically responsible for the HW – Enable virtual drivers to access the peripherals through back-end / front-end architecture Device Sharing is Key to the Success 6 Hardware OS1 App OS2 App vLogix Mobile (vLM) Disk Network LCD Hardware Disk Network LCD vLM product comprises of hypervisor and virtual drivers in multiple configuration addressing various use-cases
  7. 7. Architecture Overview Apps Apps vOGL FE vEGL FE vAlloc FE vDisp FE WS vOGL BE vEGL BE vAlloc BE vDisp BE WSAllocEGL Display OGL Off screen memory rendering Display memory rendering Frame buffer Virtual sidePhysical side Off screen memory rendering Display memory rendering Frame buffer(s) Off screen memory rendering Display memory rendering Virtual Frame buffer 8
  8. 8. Configuration with Two Displays Apps vOGL BE vEGL BE vAlloc BE vDisp BE WSAllocEGLOGL Off screen memory rendering Physical side Off screen memory rendering Display memory rendering Frame buffer 2 FB1 display WS is configured as follow:  Frame Buffer 1 dedicated to one display for the physical VM  Frame Buffer 2 dedicated to second display of the virtual VM Frame buffer 1 Frame buffer 2 FB2display 9
  9. 9. Considerations • An excellent solution for reducing hardware costs – Separate OSs for each functional area – Separate CPU cores to guarantee compute resources • Things to consider… – Performance impact of the hypervisor: Real or FUD? • True Type 1 hypervisors’ performance impact is negligible – TI OMAP5 and Jacinto 6 processors have hardware-support for virtualization: less code running in the hypervisor – Board-level device assignment: complicated? • Devices can be directly assigned to individual guest OSes without the need for sharing – Licensing • BOM savings more than offsets the increase in runtime costs • OS runtimes remain the same as two SoCs 10
  10. 10. Cluster+Infotainment Graphics Use Case demo • TI hardware – OMAP5432 uEVM • QNX Platform Software – QNX CAR 2.1 for OMAP5, Crank Software HMI – Accelerated OpenGL cluster • Red Bend Virtualization – Virtualized Graphics Driver 11 • Challenge: – Maintain a constant cluster frame rate during heavy rendering on the IVI display • Solutions – (1) QNX Scheduler – adaptive partitioning – (2) Virtualization + 2 QNX guest OS’s • Other ideas? Tweet out to #TItechday !
  11. 11. Satish.Varma@redbend.com 12

×