NVIDIA DRIVE AV Storage Configuration

Three-Level Partitioning

The following diagram shows an example of a three-level partition layout and three-level partition tables.

To enable data updates in eMMC and UFS partitions through Over-The-Air(OTA), the partitions on eMMC are categorized as follows:

• The eMMC A chain: It consists of all eMMC partitions assigned to all virtual machines in the Partition Configuration Table (PCT). All content in this chain can be overwritten by the OTA application.

• The eMMC B chain: This is the recovery chain. The target boots in this chain when the OTA application is about to update other boot chains.

• The QSPI C chain: This is the recovery chain to boot with only QSPI. The target boots in this chain when the OTA application is about to update other boot chains.

• Persistent partitions for all virtual machines: The data partitions that are not updated by the OTA application. Data over these partitions remain consistent over multiple OTA cycles.

When inspecting the global_storage.cfg (level-1), you will notice it refers to boot_chain_storage.cfg as a sub_config file. This elevates the boot_chain_storage_qspi.cfg to be level-2.

...
[partition]
name=A_qspi_chain
...
sub_cfg_file=boot_chain_storage.cfg

[partition]
name=B_qspi_chain
...
sub_cfg_file=boot_chain_storage.cfg

[partition]
name=C_qspi_chain
...
sub_cfg_file=boot_chain_c_storage.cfg

Similarly, when inspecting the boot_chain_storage.cfg (level-2), you will notice it refers to the OS storage configuration file. This elevates the OS storage configuration file to be level-3.

[partition]
name=qnx-gos0
...
sub_cfg_file=qnx_gos0_storage.cfg

Since level-3 is derived from level-2, its content will be duplicated in each of the boot chains (A and B).

DRIVE AV Storage Layout

First-Level Partition Table (L1PT) Layout

The global_storage.cfg file defines the total size of storage devices, boot chain container partitions and persistent partitions of guest VMs.

The first-level configuration has the following layout for the ECO QSPI+eMMC use case:

The first-level configuration has the following layout for the ECO QSPI+UFS use case:

The first-level configuration has the following layout for the NDAS use case:

Second-Level Partition Table (L2PT) Layout

• QSPI Chain-A/B Layout

QSPI partitions include bct files, bootloaders, and firmware binaries.

The storage layout for QSPI is as follows:

• eMMC and UFS partitions

The eMMC/UFS device connected to Orin is partitioned logically to enable each VM to have its own root file system or to store user data. Each VM is assigned a dedicated user partition on eMMC/UFS and might have secondary user partitions for storing additional data. The eMMC/UFS device on board is shared between the VMs.

The eMMC/UFS storage chain A/B for QNX PCT ECO use case:

Where:

• /dev/vblk_* denotes the enumeration for a given partition from guest OS or service VM. The partitions must be formatted before use.

• IFS: Early boot partition with minimal file system that contains the kernel.

• EFS: QNX root file system, additional file system demonstration bits, sample applications, and data.

• All partitions present in boot_chain_storage.cfg are part of the OTA update.

• All sub-configuration files that are in the boot_chain_storage.cfg are also part of the OTA update.

The eMMC/UFS storage chain A/B for Linux PCT ECO use case:

The eMMC/UFS storage chain A/B for QNX (qnx/dual-qnx) PCT NDAS use case:

The eMMC/UFS storage chain A/B for Linux PCT NDAS use case:

NV Pre-Allocated Stream IDs

The following table describes the NV pre-allocated stream IDs.