As the power of semiconductor chips, or System on Chips (SOCs) grows, software designers are mixing more functions to be supported on these SOCs. This saves cost. To accomplish this, designers use a hypervisor, which can support multiple domains (sub-systems) each isolated from the other on the same SOC. In industrial robotics, medical and automotive systems, such as in digital cockpits and advanced driver assistance systems (ADAS), functional safety requirements are becoming increasingly required. Mission-critical systems that demand high reliability, deterministic response times, security and functional safety can be supported by a safety-certified hypervisor.
Join Randy Martin, senior product manager, and Jonah Caplan, functional safety manager from BlackBerry QNX, for an in-depth discussion of how automotive and other mission-critical systems are using safety-certified hypervisors to address issues such as:
- Freedom from interference in hardware (spatial), freedom from interference in time (temporal). What is unique about a safety-certified hypervisor? How is it used?
- The separation and isolation of safety-certified software components and non-certified software components running on a single SoC. How can this be securely managed?
- What restrictions exist for the guest operating system? For applications running in the guest?
- What SoC and hardware restrictions exist? What should you be asking your hardware vendor?
- An example implementation: Running an Android operating system on a safety-certified hypervisor
Randy Martin, Senior Product Manager, BlackBerry QNX
Jonah Caplan, Functional Safety Manager, BlackBerry QNX
Brandon Lewis, OpenSystems Media