Global Sources
EE Times-Asia
Stay in touch with EE Times Asia
EE Times-Asia > Embedded

Designing GENIVI-based infotainment systems

Posted: 27 Nov 2013 ?? ?Print Version ?Bookmark and Share

Keywords:GENIVI 5.0? in-vehicle infotainment? HMI? audio-video processing? Linux?

The GENIVI 5.0 specification is slated to be published this latter part of 2013. With each new specification release, GENIVI's open source base platform becomes more functional and usable by implementers of in-vehicle infotainment (IVI) systems. However, the final performance of any GENIVI IVI system is dependent on the underlying hardware and the corresponding peripheral components available to the designer. To get the best possible performance the software needs to be specified with the hardware peripherals in mind. To this end, major semiconductor suppliers are now converging on the must-have range of features for vehicle infotainment systems.

This article looks at some of the technology areas where the marriage between hardware and software is essential to ensure the development of a top-performing GENIVI infotainment system at the right price.

Key requirements from the automotive OEM
The detailed content of GENIVI software releases is far removed from the real-world requirements of automotive OEMs and their tier one implementers. Paramount for the manufacturer are safety, cost, environmental issues, and usability considerations. These, in turn, are dependent on the hardware platform hosting the infotainment software stack. IVI requirements that correlate directly to the underlying hardware might include:

???A user interface (UI) complying with National Highway Traffic Safety Administration (NHTSA)driver distraction guidelines
???System start-up times (typically ???Hibernate/stand-by states, persistence, and memory
???Screen layout, access, and UI ease of use
???Domain consolidation, virtualisation; links to other automotive functions and data feeds
???ASIL classification; safety and ISO 26262 conformance
???Real-time data streams: camera, radar feeds, etc.
???Minimising cost by maximising use of multi-core system-on-chip (SoC) hardware
These high-level requirements map down to specific hardware peripherals, whether relating to connectivity, HMI, data-storage, or multimedia audio-video processing.

Table: Automotive hardware features and impact on the IVI system functionality.

Hardware-dependent performance
Almost every aspect of the infotainment end product requires a good hardware foundation. The table covers some of the necessary peripherals and the infotainment features that leverage each peripheral.

Typical vendor examples supporting many of the above features include platforms such as the Freescale i.MX6 family, Texas Instruments' Jacinto range of devices, Renesas R-Car H2/M2, and nVidia's Tegra family. These platforms are often supplied with software board support packages (BSPs) as a starting point, which often need modification or "hardening" to adapt them for use with the infotainment and GENIVI software components they are hosting.

Let's take a closer look at some of the more interesting technology areas and how GENIVI is working to align itself with these required hardware capabilities. Most semiconductor providers will advertise support for OpenGL /ES (Embedded Systems) with their silicon C a well-established standard for describing on-screen graphical objects. OpenGL ES technology is royalty-free and provides a cross-platform standard for 2D and 3D graphics on embedded systems, and as a result this standard has become widespread. OpenGL ES is a well-defined subset of the desktop OpenGL standard and provides the low-level interface between software and on-chip, hardware-based graphics acceleration.

1???2???3?Next Page?Last Page

Article Comments - Designing GENIVI-based infotainment ...
*? You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.

Back to Top