Customizing the Configuration File

Customize the mass storage partitions on the target by modifying the configuration file flashed to the target.

Configuration files (CFG files) consist of mass storage device declarations followed by partition declarations. The NVIDIA tools use the configuration file to create the images on the host and flash the target device on the specified memory locations.

The platform includes a default configuration file used by the flashing scripts. Use the default configuration file as a starting point for any customization, and backup the original file before attempting modifications.

For an example of the dual Linux OS partition configuration, see the Example Virtual Partition Configuration chapter in the NVIDIA DRIVE OS 6.0 Linux PDK Development Guide. For an example of a native OS (not virtual) partition configuration, see the Example Native OS Partition Configuration chapter in the NVIDIA DRIVE OS 6.0 Linux PDK Development Guide.

Note:

Two CFG versions are supported. The existing CFG format is identified as “legacy” or “v1,” while the 3-level CFG format is identified as “v2.”

The default configuration file for a platform is adequate for initial product development. However, consider creating a custom configuration file for these stages:

  • Finalizing production
  • Flashing updated images

There are several advantages to using a custom configuration file. It can specify:

  • Different kernel images for recovery and primary partitions
  • Temporary partition
  • RamDisk or other feature in recovery partition or vice-versa

If there is a need to repeatedly switch between NFS and MMC, it is recommended to create and use separate configuration files for each.