Access Official Technical PDF

Share Summary:LinkedInEmail

Automotive software virtualization was a prominent theme at the GENIVI Alliance’s 2018 All Member Meeting and Open Community Days in Munich. Demonstrations showed how Linux, real-time operating systems (RTOSs), graphics applications and safety-related functions could coexist on shared computing platforms. Although the showcased systems were designed for vehicles, their engineering challenges—integrating software, partitioning resources, maintaining safety and coordinating updates—are relevant to teams working with complex embedded systems across industrial automation.

The event also illustrated a broader point: system integration depends on more than selecting capable hardware. It requires clear boundaries between functions, dependable communication paths and development practices that allow organizations to build on shared technologies.

Automotive software virtualization and cockpit consolidation

Several demonstrations explored consolidating functions that might otherwise run on separate hardware. One combined infotainment and driver-information systems using two GENIVI-compatible Linux operating systems on Intel ApolloLake hardware. An automotive-grade hypervisor allocated shared hardware resources to the two environments, supporting a digital instrument display and center-stack infotainment system.

Other demonstrations used virtualization to host multiple operating systems or functions on a common platform. Green Hills Software and Renesas presented a design combining Linux infotainment with safety-critical instrument-cluster and head-up-display functions. OpenSynergy and Rightware demonstrated a Linux-based instrument cluster in a virtual machine alongside a separate subsystem that checked safety-critical graphical elements. In the described architecture, a guard mechanism could initiate recovery if the instrument-cluster virtual machine experienced a software failure.

These examples highlight an important design task for any consolidated embedded system: determine which functions may share resources, how they are isolated, and how failures are detected and handled. Virtualization provides a way to organize multiple software environments on shared hardware, but the system architecture must still address the requirements of each function.

Integrating graphics, audio and safety functions

The showcase included digital-cluster demonstrations that combined rich graphics with safety-related display content. One architecture paired complex graphics with safety-certifiable ASIL B graphics. Another used separate virtual machines and a verification mechanism for safety-critical telltales, such as warnings associated with braking or airbags. These demonstrations focused on making different classes of display content coexist while preserving a defined approach to safety.

Audio integration offered another example of system-level design. A Mentor demonstration used non-intrusive monitoring based on Analog Devices’ A2B technology. The described approach used lightweight, unshielded twisted-pair cabling in place of conventional in-vehicle cables and connected audio technology with infotainment and noise-cancellation applications.

For automation engineers and integrators, the transferable lesson is not that vehicle architectures can simply be copied into a plant. It is that graphics, audio, control and safety functions have distinct requirements, and their interfaces and shared resources need to be deliberately engineered.

Connected systems expand the integration boundary

Many exhibits extended beyond the individual computing platform to consider connections between vehicles, cloud services and other devices. HARMAN presented a cloud platform for connectivity, device management, applications, analytics and managed services, alongside a remote vehicle updating service covering software components such as applications, firmware, settings and maps. Wind River’s connected-car framework included an over-the-air update capability in its demonstration.

Other projects focused on moving data and media between systems. Demonstrations included streaming content to rear-seat or personal devices, sharing graphics and media between driver and passenger infotainment systems, and collecting vehicle data for use by software components and off-board servers. These use cases make the interfaces between in-vehicle and external systems part of the overall architecture—not an afterthought.

Security was also represented. An HMI demonstration showed a brute-force attack against a keyless entry system, together with detection and theft-prevention features. Another exhibit presented a tool for analyzing security properties during automotive development. The examples underscore the need to consider security as a system concern spanning devices, software and connections.

Open-source development and ecosystem collaboration

GENIVI’s event brought automakers, suppliers and software organizations together around shared platforms and development topics. The displayed technologies included GENIVI-compatible Linux systems, the Yocto Project, WebKit and Chromium-based browser technologies, interface-definition tools, and software for modeling event-driven systems. GitHub’s presentation focused on collaboration and reuse in automotive software development, while the GENIVI Development Platform provided a target system and development environment.

The alliance’s wider collaboration extended beyond the traditional automotive supply chain. The event material described work with organizations and ecosystems involved in broadcasting, smart homes, smart cities and advanced mobility. This reflects a practical integration challenge: connected products increasingly exchange information with services and technologies developed by different organizations.

For technical decision-makers, shared development environments and well-defined interfaces can support collaboration across teams. They do not remove the need for requirements management, security analysis, traceability or validation. The showcase’s tooling examples included security analysis, interface definition and traceability tools associated with standards such as ISO 26262 and Automotive SPICE.

Practical takeaways for embedded-system teams

  • Plan consolidation around function boundaries. Shared hardware can host multiple software environments, but the architecture must account for isolation, resource sharing and recovery.
  • Keep safety requirements visible. Demonstrations distinguished safety-critical display elements from other graphics and showed mechanisms for checking or recovering those functions.
  • Design for system-to-system communication. Data, media and services crossed boundaries between applications, devices and cloud platforms, making interface choices central to integration.
  • Include security and lifecycle needs. The exhibits addressed attack detection, security analysis and remote software updates as parts of connected-system development.
  • Use collaboration deliberately. Open technologies and shared development practices can bring organizations together, while engineering processes remain essential for managing quality and traceability.

Conclusion

GENIVI’s Munich showcase presented a varied set of automotive demonstrations, but recurring engineering concerns connected them: consolidating functions, managing mixed software environments, protecting safety-related behavior and integrating connected services. Industrial automation teams can use these examples as prompts for evaluating their own embedded architectures. The practical focus is on making boundaries, interfaces, failure responses and software lifecycle responsibilities explicit as systems become more integrated.

Access Official Technical PDF

About The Author