Linux Software Stack

Component	Description
NVIDIA DRIVE™ Hypervisor	Privileged software component optimized to run on the ARM® based Cortex-A57 MPCore. Hypervisor separates system resources between multiple VM partitions. Each partition can run an operating system or a bare-metal application. The Hypervisor manages: • Guest OS partitions and the run-time isolation between them • Partitions’ virtual views of the CPU and memory resources • I/O resource allocation and sharing between partitions
Boot Loader	Responsible for loading Foundation images. Based on NVIDIA Quickboot technology.
Flashing tools	Allows flashing and updating Foundation components and Guest OS partitions. Based on NVIDIA Bootburn technology.
I2C Server	A Bare metal partition that manages I/O device sharing between partitions.
OS Loader	Responsible for loading OS images. Implements OS specific boot protocol for NVIDIA DRIVE™ platforms. Based on NVIDIA Quickboot technology.
Partition Configuration Tool	Allows configuring partition parameters and resource allocation
Partition Loader	Responsible for loading Guest OS boot image into partition container. Additionally: • Plays a key role in restarting individual Guest partitions. • Dynamically loads/unloads partitions and virtual memory allocations. Based on NVIDIA Quickboot technology.
Monitor Partition	Monitors partitions, including: • Starts/stops Guest OSs. • Coordinates Guest OS restarts. • Performs watchdog services for Guest OSs. • Logs partition use.
RM Server	Manages isolated hardware services for: • Graphics and computation (GPU) • Codecs (MM) • Display and video capture I/O
System Memory Management Unit (SMMU) Server	Bare metal partition responsible for Tegra SMMU management for I/O device memory access protection between partitions
Virtualization Storage Client Server (VSC)	Controls access to a single eMMC device and virtualizes this device so that VMs see the device as a set of individual disks. VSC also controls and secures access to partitions on the eMMC device from multiple guests

Component	Description
OS Drivers	OS driver support for enabling OEM applications to establish standard I/O interfaces. These drivers support Linux file systems (such as ext3, ext4, and NFS), networking (such as TCP, IP, and UDP), USB 3.0 mass storage file systems (ext3, ext4, fat32 with vfat), and USB 2.0 host (such as HID, Com, and Mass Storage).
Linux Kernel 4.9	Widely used open-source POSIX compatible operating system.
Board Support Package (BSP) Drivers	NVIDIA drivers and applications that support communication, configuration, and flashing from a host computer.
NVIDIA® CUDA®	An NVIDIA parallel computing platform and programming model. It enables dramatic increases in computing performance by harnessing the power of the graphics processing unit (GPU).
OpenGL 4.5	NVIDIA implementation of the OpenGL ES standard accelerated 3D graphics rendering library. This NVIDIA library includes implementations of NVIDIA and multi-vendor OpenGL ES extensions. In many cases, these extensions use platform-specific features to provide efficient implementations. OpenGL 4.5 is backward compatible with GLES 3.2. For more information, see OpenGL ES 2/3 Specs and Extensions in API Modules, Graphics APIs.
EGL 1.5	NVIDIA implementation of the EGL interface library for use between rendering libraries (like OpenGL ES) and the underlying native platform window system. This library includes NVIDIA enhancements specific to the Tegra platform. For more information, see EGL Specifications Extensions in API Modules, Graphics APIs.
Applies to: NVIDIA DRIVE™ Linux Vulkan 1.0	NVIDIA supports the Vulkan 1.0.35 specification for instance and device extensions. For more information, see Vulkan Specs and Extensions in API Modules, Graphics APIs.
NvMedia	NVIDIA API that provides a complete solution for decoding, post-processing, compositing, and displaying compressed or uncompressed video streams.
RM Driver Note: Available with Hypervisor features.	Resource Manager that provides inter-process communication (IPC) and data transfer between the guest operating system and the hypervisor. IPC includes processing requests and hardware settings.

Integration with the AURIX microcontroller enables high, real-time processing performance with enhanced embedded safety and security features for use in ADAS applications. The EB tresos software integrates the capability of Linux and AUTOSAR applications with NVIDIA DRIVE™ PX 2 functionality for monitoring and redundancy processing. It enables a safe and reliable, cross-CPU-communication execution environment in compliance with the ISO 26262 standard at the highest automotive safety integrity level (ASIL D).

NVIDIA DRIVE™ PX 2 provides hypervisor functionality through virtualization capabilities of the Cortex-A15 processor. Hypervisor (also known as a Virtual Machine Monitor or VMM) is a small layer of full-privilege software. Hypervisors can be hosted and run on the host operating system, or they can be run directly on the hardware. They enable running multiple guest operating systems (or baremetal software) on the same chipset, and each guest OS stack has its own security and safety requirements. The partitions run as if they own the hardware exclusively, but they run in a multiplexed manner, sharing memory, CPU resources, and devices.

Fast booting features in hypervisor enable safety-critical operations and multiple OS’s to run reliably. CANBUS related software can run next to Android, for example, without being affected by software bugs in the Android partition. With realtime capabilities, drivers can be ported to a partition running on a realtime OS or a bare metal partition, and then provide realtime response. Any partition using that driver can then receive that benefit.