![]() | NVIDIA DRIVE 5.0 Foundation SDK Development Guide 5.0.10.3 Release |
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. |
Early Boot Partition | Provides early display of video images. |
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 |