Bind Partitions#

A bind process creates a hypervisor image that combines DTB/KERNEL of HVRTOS-servers, Hypervisor kernel, and PCT. This process also builds Guest-OS DTB and BPMP-DTB.

Syntax of bind_partitions#

Enter the drive-foundation folder:

# for NSR package
$ cd drive-foundation/

Use the bind_partitions command by issuing the following syntax:

$ ./make/bind_partitions -b <board_name> <domain>.<pct> -p <pct_variant> [additional options]

Example of development non-safety related (NSR) AV+L PCT use case on NVIDIA DRIVE AGX Thor™ Devkit:

For generic Linux PCT:

bind_partitions -b p3960-10-sw01 linux

Note

When the -p <pct_variant> option is omitted, the default PCT variant is dev_nsr.

Note

The default <domain> is drive_av, so drive_av can be omitted for the drive_av domain. Also note that drive_av has alias_name av and linux has alias name l. All the following commands are equivalent with upper command.

Example of ECO UFS boot configuration bind for development non-safety related build:

bind_partitions -b p3960-10-sw01 drive_av.linux -p dev_nsr

Example specifying the drive_av domain for Linux:

bind_partitions -b p3960-10-sw01 av.l

Example using the alias l for Linux in bind call:

bind_partitions -b p3960-10-sw01 l

Note

The default value and alias_name can be found in /virtualization/pct/make/t264/pct_configuration_v2.yaml file.

The following tables list the supported bind options.

Supported Bind Options for Thor™#

Example of development NSR Linux PCT with QSPI+UFS use case on NVIDIA DRIVE AGX Thor™ Devkit:

bind_partitions -b p3960-10-sw01 linux

Board name list#

<board_name> need to be passed after -b.

Platform

<board_name>

SKU-REV

p3960

p3960-10-sw01

940-63960-0010-TS1

p3960-10-sw02

940-63960-0010-TS2

Domain, Pct, Pct variant and Memory size list#

<pct_variant> need to be passed after -p.

<memory_size> need to be passed after -m.

<domain>.<pct>

<pct_variant>

<memory_size>

drive_av.linux

  • dev_nsr (Default)

  • test_nsr

  • prod_nsr

  • 64g (Default)

  • 32g (for 32GB DRAM)

Note

The memory size option -m <memory_size> determines the DRAM configuration for your system:

  • 64g: Configures the system for boards with 64GB DRAM capacity (8x 8GB DIMMs)

  • 32g: Configures the system for boards with 32GB DRAM capacity (8x 4GB DIMMs)

Choose the option that matches your board’s physical DRAM configuration.

An additional option for Thor-U#

  • Thor-X

By default, Thor-X SoC is selected.

  • Thor-U

Thor-U needs the following extra options:

The ENABLE_THOR_U=y option during bind_partitions.

The --board_config <path>/<board_name>_thor_u.json option during bootburn.py.

Example:

bind_partitions -b p3960-10-sw01 linux ENABLE_THOR_U=y

sudo ${NV_WORKSPACE}/drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3960-10-sw01 -D --board_config ${NV_WORKSPACE}/drive-foundation/platform-config/hardware/nvidia/platform/t264/automotive/flashing/board_configs/p3960-10-sw01_thor_u.json

For more detail of using bootburn.py, refer to the Flashing section.

On this page