Your SlideShare is downloading. ×
0
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System

605

Published on

Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System – Andrew Patterson …

Simultaneously Leveraging Linux and Android in a GENIVI compliant IVI System – Andrew Patterson

It is widely accepted that Linux is the operating system of choice when building a complex, in-vehicle infotainment (IVI) system. The ability to support and quickly integrate device drivers for features such as CAN, MOST, graphics accelerators, networking interfaces, and Bluetooth can result in key differentiators for any GENIVI compliant IVI-based system. But what if Android was introduced as a second operating system? This session multiple implementations integrating both Android and Linux on multicore SoCs sharing audio and video resources across both domains while maintaining GENIVI compliance. Implementations with and without hypervisor technology will also be presented.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
605
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
49
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Infotainment systems are become key decision points by customers, more and more influenced by the SmartPhone lifecycle. Users no longer wish to maintain multiple user-interfaces, and contact lists. OEMs and Tier 1s are under pressure to reduce development costs, so this has driven the formation of industry standards and alliances in the area of IVI and Instrument Clusters
  • Many OEMs and TIer1s have recognized that they cannot stay on a proprietary or first generation platform. The QNX operating system has been widely used in the past, but does not offer the open-source path and GENIVI compliance needed to keep future cost base low. Other proprietary solutions for IVI, such as Microsoft or Google, are risky because of potential future license restrictions
  • Agenda for this presentation.
  • Automotive OEMs and Tier 1s are facing a wide range of new challenges demanded by customers, increasingly influenced by Smart Phone technology. A second generation, linux-based platform capable of handling the complexity is needed
  • Many OEMs and TIer1s have recognized that they cannot stay on a proprietary or first generation platform. The QNX operating system has been widely used in the past, but does not offer the open-source path and GENIVI compliance needed to keep future cost base low. Other proprietary solutions for IVI, such as Microsoft or Google, are risky because of potential future license restrictions
  • Many OEMs and TIer1s have recognized that they cannot stay on a proprietary or first generation platform. The QNX operating system has been widely used in the past, but does not offer the open-source path and GENIVI compliance needed to keep future cost base low. Other proprietary solutions for IVI, such as Microsoft or Google, are risky because of potential future license restrictions
  • Many OEMs and TIer1s have recognized that they cannot stay on a proprietary or first generation platform. The QNX operating system has been widely used in the past, but does not offer the open-source path and GENIVI compliance needed to keep future cost base low. Other proprietary solutions for IVI, such as Microsoft or Google, are risky because of potential future license restrictions
  • Because of the success of Android in the SmartPhone market, many IVI users expect similar apps in their cars. There are several ways to include Android in an IVI solution, and one increasingly popular solution is the Linux Container. Here Android sits as a Guest OS on top if the Linux Kernel. Priveliges and permissions may be tightly controlled
  • An alternative way to implement Android is by using a Hypervisor, provided by specialist partners. Mentor has close relationships with Hypervisor providers, such as Open Kernel Labs and SysGo
  • Users often worry that a Hypervisor will be a performance overhead, but this is not typically the case. As platforms get more and more powerful, a Hypervisor is a good way to offer support for multiple operating systems and functions in IVI and Instrument Cluster
  • This slide shows the four key elements to Mentor’s IVI strategy
  • Transcript

    • 1. Embedded World Session 22 Simultaneously Leveraging Linux and Android in Automotive IVIAndrew PattersonBusiness Development Director mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions.Mentor Graphics Ltd Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
    • 2. What goes into an IVI system? Applications Middleware/Libraries / Services Proprietary OS DeviceDrivers
    • 3. Technology EvolutionBring in the New, Exit the Old Hi-Fi Stereo 8-Track Tapes Circa 1970 • 300,000 new cars and trucks would be sold in the United States this year with no CD player Paired Device 2013 • Expected to grow to 15.9 million in 2019. • Large population of older people who don’t want to give up their CD players : Change takes time John Canali - senior analyst at Strategy Analytics,
    • 4. Where are the influences ?• Android : Dominant in consumer electronics mobile devices• Automotive Standardization : Reduce costs, share non- differentiating technology• Technology & Value : More innovation for less moneyIn the first 6 months of 2012Android downloaded onto681,900 separate devices in195 different countries
    • 5. IVI Trends in Telematics : Need Linux & Android Collision Notification Insurance Stolen Vehicle In-car services, concierge, streaming Eco-driving services Real-time Cloud data : Traffic, Weather, Road ahead Car-Car communication Driverless car Diagnostics and servicing
    • 6. Consumer Electronics Influence …■ The SmartPhone Revolution ■ 3 out of 4 Smart Phones sold are Android ■ Apple & Samsung account for 83% of market ■ Platform Refresh every 6 months■ The Car is becoming a Consumer Electronic Product■ Lifecycles — Consumer Electronics : 6 months — Automotive : 10 years?
    • 7. Choices and Design OptionsConsumers demand choice..Infotainment Design Choices :• Hardware Platform• Operating System• Architecture• Applications and App management• Phone / Internet Connectivity
    • 8. Linux to Obtain 30% IVI Market Share in 2018 60 50 40 QNX Microsoft % 30 Genivi Android 20 Others Others include 10 other Linux platforms 0 2010 2012 2014 2016 2018 Copyright © 2012 IHS Inc. All Rights Reserved.
    • 9. Operating Systems OS For Against Win CE widely License cost ? Established Many open source Development effort variants / GENIVI / flexible platform Widely accepted in Managed by Google, Mobile / CE, open source adaptation effort Highly tuned / good Cost of development and Proprietary OS control over functions by run-time, maintenance, Commercial OEM/Tier 1 development cycle
    • 10. Platform Options / GENIVI OS Choices Silicon Available : • Multi core CPUS • High performance GPU • Peripherals : USB, WiFi, etc GENIVI 3.0 GENIVI 2.0 GENIVI 1.0Accenture ARM Cortex-A9 (TI OMAP 4460) (Intel® Atom™ ) (Intel® Atom™ ) Intel® Atom™MontaVista Renesas R-car H1 reference board Renesas R-Car H1 (Marzen) Renesas R-Car M1(Mentor) Freescale i.MX6q Sabre-lite Freescale SABRE i.MX53 Boundary Devices Freescale i.MX53 Sabre Freescale i.MX6q Sabre-lite Sabre-lite board Freescale i.MX53 QSB Texas Instruments Jacinto Intel Atom Crossville Intel Atom CrossvilleWind River (i.MX6 Sabre Lite) Renesas R car M1A BOCK-W (Intel® Atom™ ), (ARM Texas Instruments Jacinto 5 EVM Cortex-A8) Freescale i.MX6 Sabre Lite Renesas R car E1 – SilverstoneMentor (i.MX6 Sabre Lite) Intel Atom Crossville Intel Atom Crossville (i.MX6 Sabre Lite) Freescale i.MX6q Courtesy : GENIVI 2012
    • 11. Driver and Passenger needs Driver Passengers • Navigation • Social Media • Radio / Media Player • Streamed Services • Concierge Services • Web Browsing • Phone • Android Apps • Real-time travel informationCourtesy : Volvo Car
    • 12. The case for Linux in Infotainment mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
    • 13. Why Move to Linux ? Proprietary 1st generation automotive IVI operating systems are getting expensive to maintain and scale up Linux is an Industry standard  Facebook, Amazon, Twitter all Linux servers  Android has a Linux Kernel Wide choice of hardware platforms (SoC)  SoC vendors increasingly ―do Linux first‖ Several Automotive Linux options  GENIVI well established  AGL (Automotive Grade Linux) ?
    • 14. Linux in numbersPopularity rankings for Linux (by community access) 2010 2011 2012 1 Ubuntu Linux MINT Linux MINT 2 Fedora Ubuntu Mageia 3 Linux MINT Fedora Ubuntu 4 openSUSE openSUSE Fedora 5 PCLinuxOS Debian openSUSE 6 Debian Arch Linux Debian 7 Mandriva PCLinuxOS Arch Linux 8 Sabayon CentOS PCLinuxOS 9 Arch Linux Puppy Linux CentOS
    • 15. Where does GENIVI fit ? • Open Source Linux software platform for Infotainment Systems Developers • Goals : – Reduce Costs – Make Tier 1 development more transparent – Contributions from many expert sources • 170 Corporate Members • Many projects underway
    • 16. GENIVI is a partial solution for OEMs Migration to Linux Open Source Powerful SoC Connected HMI Car Performance Function Android Multi-Mode Consolidation Support User InputsPicture : Courtesy GENIVI org
    • 17. Mentor GENIVI 3.0 Linux Audio Graphics Multimedia Speech • ALSA • X.Org • GStreamer • festival • PulseAudio • GENIVI Layer • GStreamer good, • pocketsphinx • AudioManager Management base plugins • Chromium / Webkit • tracker CE-device External Connectivity Positioning Access • gypsy • wireless tools • cedevicemanager • lighttpd • Wpa-supplicant Personal Information • lighttpd-mod-webdav • ConnMan Management • BlueZ • SyncEvolution Package Networking Security System Infrastructure Management • d-bus • • dhcp • ecryptfs-utils quota • sqlite • udev • opkg • libcurl • gnupg2 • qt-core • usb-utils • nfs-utils • openssl • fuse • libmtp • ntp • gettext • ... OS kernel, drivers and libraries Linux Linux drivers ARM A9 Freescale Sabre, SabreLite GNU libc 17
    • 18. Android in IVI mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
    • 19. In-Vehicle AndroidOptions• Native • Android operating system on ―bare metal‖• Parallel Domain • Android running as a parallel operating system • Virtual Domain, Container• Tethered • Linked in via mobile phone
    • 20. Arguments For Android Acceptance in CE  850,000 new devices daily  Over 700,000 Apps (Oct 2012)  6 billion total downloads Car features  Android ―Car Mode‖ routes all audio to speaker  Hands-Free support Other selling points  Familiar UI for users  Development kits & community  Automotive apps peripheral support
    • 21. Top 6 Automotive Android AppsApp DescriptionRadaroid Radaroid shows you a map which will provide locations of places where there might be a speed camera installedGPS HUD provide you the exact location and the speed that you are travelling at. Also, the same will be reflected in the display which can be cleverly reflected on the windscreen. Thus giving you a feel of using an HUDCarr Matey In case you have forgotten the location where you have parked your car,Drive this app and it will read your messages and e-Carefully mails to you.Geo Keep yourself and others entertained by someReader general knowledge about that place by using this app.
    • 22. Android Challenges Roadmap managed by Google Updates to OS / App compatibility OS fragmentation and distribution MultiMedia IVI  Audio Routing  Video Layers Security ?
    • 23. Beyond Apps Security Concerns  Apps may provide gateway for hackers / attacks  May compromise / interfere with operation of other vehicle functions Management  Which Apps are authorized?  Some Auto OEMs will set up Apps Stores Renault R-Link Apps Store
    • 24. Renault R-Link
    • 25. Tethered Smart Phone ―Thin Client‖ on IVI head unit Approved Apps only Internet Speech Engine IVI Networking Connectivity Navigation Audio Stack Entertainment Telephony Quick Android Mobile Office Cloud Integration
    • 26. Car Connectivity Consortium Standard ―recipes‖ for Smart Phone tethering  Universal Plug and Play (UPnP™) is used for controlled access to applications  Virtual Network Computing (VNC™) replicatesofthe Only 34% consumers would phones display on the navigation screen and to pay be willing communicate user inputs back to the phone. in the car for Apps (IMS Jan 2013) 80 members  70% market share in vehicles  60% market share in smart phones. Built-in support  Samsung Galaxy III, Nokia, …
    • 27. IVI Architectures mentor.com/embedded Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
    • 28. Linux Container (LXC) Architecture Common HMI Graphics Layer Management Android Apps Networking Navigation IVI Android OS Entertainment Stack Mobile Office Linux Container Mentor IVI Linux OS / LXC Resource Management Hardware Layer Multi-Core CPU GPU
    • 29. Overview of LXC• OS-level virtualization method• Used to run multiple isolated Linux systems – Can be different distributions• A single kernel is shared• LXC does not provide a virtual machine – provides a virtual environment that has its own process and network space• The LXC project is hosted on SourceForge – http://sourceforge.net/projects/lxc/• Userspace control tools are provided for Linux containers• LXC has been integrated into Mentor ATP
    • 30. Overview of LXC (Cont…)Linux cgroups provide: • Resource limiting: groups can be set to not exceed a set memory limit • Prioritization: some groups may get a larger share of CPU or disk I/O throughput • Accounting: to measure how much resources certain systems use for e.g. billing purposes • Isolation: separate namespaces for groups, so they dont see each others processes, network connections or files • Control: freezing groups or checkpointing and restarting
    • 31. Android Guest OS via Hypervisor Common HMI Graphics Layer Management Networking Android Navigation IVI Apps. Stack Entertainment Mobile Office Linux OS Android OS HyperVisor Hypervisor Virtualization ARM Multi-core CPU SoC GPU, Peripherals
    • 32. Features of a Hypervisor solution ■ SoC Hardware resources shared between two or more operating systems ■ Multi-core CPU, GPU, Audio, Network, USB ■ Independent reboot / fast boot options ■ ADAS, system start-up ■ Low Overhead ( 1-4 % CPU) ■ Privileges Management / Security (General Dynamics) (Thales) (OpenSynergy)
    • 33. Virtualization or Containers? ■ Option Comparison : Hypervisor Virtualization Linux Container For - Scalable to multiple domains on - Available as part of Mentor a single hardware platform GENIVI Linux - Faster boot-up time - Lower Cost - HMI Integration easier to manage - Solutions in place for Android and AUTOSAR Against - Cost / proprietary licensed - Boot-up time : Need to wait for software solution Linux host - Substantial porting effort for - Less domain isolation device drivers
    • 34. AUTOSAR Co-Host ■ HostAUTOSAR environment on IVI or Cluster hardware ■ Mentor (or partner) AUTOSAR V4 Application Software (e.g. ABS Algorithm) IVI SWC 1 ECU 1 SWC 3 RTE Interface Cluster Application and HMI BSW RTE Communication Stack Communication IVI LIN, CAN, FR Microcontroller OS BSW Linux OS AVB/Ethernet Abstraction Layer (MCAL) MCAL Virtualization Layer SoC ECU 2 ECU nBus : CAN, LIN, FlexRay, AVB, MOST
    • 35. Summary : Integrated Solutions IVI Hardware Flexible architectures allowing co-existence of Android and Linux are needed

    ×