AV PCT Configuration

Partitions that are allocated to the QNX/Linux Virtual Machine(VM) and are physically managed by Virtual Storage Controller(VSC) server VM. These partitions are defined to be virtual partitions.

For more information, see the Storage Server / Virtualized Storage topic in the Virtualization Guide chapter.

These partitions are accessible to the VM(s) via inter VM communications channels called Inter-VM-Channel(IVC) which is a bidirectional short command oriented interface, and memory-pool which is a shared memory buffer. These are only accessible by the GOS(QNX or LINUX)/UPDATE VM and the VSC.

Add IVC/mempool number define to give notice those would be reserved:

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/platform_ivc_config.h

#define GOS0_VSC_Q_[Ivc Queue Num]   	 [Ivc Queue Num]

  NOTE: Allocate unused IVC number and define a new constant editing [Ivc Queue Num].
        IVC number can be added up to 255.
....

#define GOS0_VSC_M_[Mempool Num]   	 [Mempool Num]

  NOTE: Allocate an unused memory pool id, and define a new constant editing [Mempool Num].

Add IVC/mempool in platform_conf structure (Just place holder for HVRTOS VSC server to let user know these are using):

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/platform_config.h

#if defined(ENABLE_HVRTOS_VSC_EMMC_VIRT) || defined(ENABLE_HVRTOS_VSC_UFS_VIRT)
	//[GOS0_VSC_Q_[Ivc Queue Num]] /* <partition name> */
#endif

....

#if defined(ENABLE_HVRTOS_VSC_EMMC_VIRT) || defined(ENABLE_HVRTOS_VSC_UFS_VIRT)
	//[GOS0_VSC_M_[Mempool Num]] /* <partition name> */
#endif

    NOTE: None HVRTOS VSC server is deprecated. No need to add array in platform_conf structure.

Note:

• Adding Ivc/Memppol array in platform_config.h was only for none HVRTOS VSC server. If ENABLE_HVRTOS_VSC_* is set to y in profile makefile, HVRTOS VSC server uses ivc/mempool IDs parsed from virtual_storage_ivc_ch in storage config files.

The new IVC number added in previous step as \[Ivc Queue Num], and the new mempool number added in the previous step as [Mempool Num], must be added in two configurations files:

• In the storage configuration file where the new partition was added the following new attributes need to be added.

  • The last four string in virtual_storage_ivc_ch are the hexadecimal representation of the memory pool and IVC channel.

partition_attribute=<GID_GUEST0_VM+1>
virtual_storage_ivc_ch=0x8<GID_VSC_SERVER>20[Hex value of Mempool Num][Hex value of Ivc Queue Num]

• The 32-bit virtual_storage_ivc_ch value can be broken down as follows:

For QNX GOS0 VM, the presence of the partitions to be used by the QNX VM is defined in its device tree file:

<top>/<NV_SDK_NAME_QNX>/bsp/device-tree/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/storage/tegra234-common-driveav-storage-gos0.dtsi

    tegra_virt_storage[Number] {                                                       <<== required name, number is incrementing
    	compatible = "nvidia,tegra-hv-storage";                                   <<== required field, as is
    	status = "okay";                                                          <<== required field, as is
    	instance = <[Instance ID]>;                                               <<== [Instance ID] 0..n for each device type. This will determine node name in GOS File System
    	ivc = <&tegra_hv [Ivc Queue Num];                                         <<== ivc number used [Ivc Queue Num] in decimal
    	mempool = [Mempool Num];                                                  <<== mempool number used [Mempool Num] in decimal
    	device-type = "[vblk_type]";                                              <<== [vblk_type] is one of "vblk_mnand", "vblk_sifs", "vblk_ufs"
    	partition-name = "<partition name>";                                      <<== partition name as defined earlier in storage configuration files.
    	read-only;                                                                <<== optional token for read-only partition. omit if read/write
    	iommus = <&smmu_niso0 TEGRA_SID_NISO0_UFS_1>;                             <<== required field for UFS device node, to mapping smmu.
    	dma-coherent;                                                             <<== required field for UFS device node. only for QNX
    	memory-phandles = < &{/smmu-static-mapping/vscd0-smmu-static-mapping} >;  <<== required field for UFS device node, to mapping smmu. only for QNX
    };

If new UFS virtual partitinon need to be added in QNX PCT, edit NUM_UFS_PARTITIONS to set total number of partitions. NUM_UFS_PARTITIONS number is using for offset/size of UFS SMMU.

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/storage/tegra234-common-driveav-storage-gos1.dts

#ifndef DISABLE_UFS
	/*
	 * NUM_UFS_PARTITIONS should be matched with unmber of UFS partitions.
	 * UFS partition node has device-type=vblk_ufs.
	 * Exceptionally UFS partition could have device-type=vblk_sifs in case Sencondary IFS
	 * exist in UFS device.
	 */
	#ifdef NDAS_STORAGE_CONFIG
		#define NUM_UFS_PARTITIONS 5
	#else
		#ifdef ENABLE_ECO_UFS_SEC_BOOT
			#ifdef ENABLE_GOS0_SIFS_1
				/* ECO QSPI+UFS case, secondary IFS exist in UFS */
				#define NUM_UFS_PARTITIONS 9
			#else
				#define NUM_UFS_PARTITIONS 8
			#endif
		#else
			#define NUM_UFS_PARTITIONS 2
		#endif
	#endif
#endif

For qnx GOS0 VM, nvhvblk_[Ivc Queue Num] must be added in nvsciipc table entry in the following file:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-nvsciipc-gos0.dtsi

    "INTER_VM",      "nvhvblk_[Ivc Queue Num]",          "[Ivc Queue Num]",  "0",    /* nvhvblk_guest */

Note:

• For linux GOS VM in linux PCT, this step is not needed.

• For 2nd qnx GOS VM in dual-qnx PCT, refer /<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-nvsciipc-gos1.dtsi

For qnx GOS0 VM, nvhvblk_[Ivc Queue Num] must be added in the list after nvhvblk_orin_gos: in the following file:

    <top>/<NV_SDK_NAME_QNX>/nvidia-bsp/aarch64le/sbin/nvsciipc_secpolicy.cfg

        nvhvblk_orin_gos:nvhvblk_[Ivc Queue Num],<already existing nvhvblk_* list>

Note:

• For linux GOS VM in linux PCT, this step is not needed. For the second qnx GOS VM in dual-qnx PCT, see "nvhvblk_orin_gos1:" in the same nvsciipc_secpolicy.cfg file.

Constraints

1. QNX OS expects the partition layout in a specific order. Refer to the Mass Storage Partitions Configuration chapter.

2. Partition sizes should be 256 K aligned.

3. IVC queue number should be smaller than 256.

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:

Note:

• For mandatory partition, only size of partition is customizable. For nonmandatory partition, all partition-attributes is customizable or it can be removed/split.

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:

Note:

• Chain B (same as Chain A) partitions are not included in the above table.

• QSPI Chain-C Layout

• emmc-part eMMC and UFS partitions

The eMMC/UFS device connected to NVIDIA 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:

Note:

• (*) is a partition only for dual-qnx PCT, and (#) is a partition only for HIGH storage configuration.

The eMMC/UFS Storage Chain A/B for Linux PCT NDAS use case:

Note:

• (#) is a partition only for HIGH storage configuration.

Note:

• For mandatory partition, only size of partition is customizable. For non-mandatory partition, all partition-attributes is customizable or it can be removed/split.

GUID based partition table(GPT) support is added for GOS at L3 level. With this feature, the partitions in L3 under GPT can be independently updated including the partition table.

To add a GPT partition at third level(L3), a container partition needs to be added at second level(L2). Level 2 container partition holds the GPT primary and backup partition layout along with the actual partition contents.

The diagram below shows the organization of L2 container partition for GPT.

In the example above, the “custom” partition is the container partition. In order for the flashing tools to create GPT partition layout the first partition must be of type “GP1” and the last partition must be of type “GPT”. Flashing tools would create GPT primary and back up partitions when such an arrangement exists.

Multiple GPT partitions can be added for the same guest. The GPT primary and secondary are generated by using the container partition name as prefix.

Example Changes for Both Linux and QNX GOS VM

Configuration files are in the following folder:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>

    NOTE:
        <PCT> is qnx or dual-qnx or linux.

"ENABLE_TEST_GPT_L3PT :=" in "profile.mk" file is knob to adding GPT custom partition. "ENABLE_TEST_GPT_L3PT" is defined by default in standard package and safety pacakge prod_debug_extra PCT variant for sample of adding GPT partitions.

The following example snippet shows changes to add custom partition in L2:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/boot_chain_storage.cfg

    [device]
    type=sdmmc
    instance=3
    linux_name=/dev/block/3460000.sdhci
    size=EMMC_BOOTCHAIN_SIZE

    ...

    #ifdef ENABLE_TEST_GPT_L3PT
    [partition]
    name=custom
    allocation_policy=sequential
    size=0x380000
    partition_attribute=0x1000000<GID_GUEST0_VM+1>
    sub_cfg_file=custom_storage_emmc.cfg
    virtual_storage_ivc_ch=0x8<GID_VSC_SERVER>964631
    #endif   

Note:

• IVC Channel(0x31=49) and Mempool(0x46=70) used in virtual_storage_ivc_ch are subject to availability.

Note:

• For information about partition_attribute, see Mass Storage Partition Configuration > Customizing the Configuration File > Setting Attributes > Partition Attributes Table in the NVIDIA DRIVE OS 6.0 Linux SDK Developer Guide or see Storage > Mass Storage Partition Configuration > Customizing the Configuration File > Setting Attributes > Partition Attributes Table in the NVIDIA DRIVE OS 6.0 QNX SDK Developer Guide.

Add IVC/mempool for custom partition(Just place holder for HVRTOS VSC server):

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/platform_ivc_config.h

#define GOS0_VSC_Q_49   	 49

....

#define GOS0_VSC_M_70   	 70

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/platform_config.h
	
#ifdef ENABLE_TEST_GPT_L3PT
	#ifdef ENABLE_HVRTOS_VSC_EMMC_VIRT
			//[GOS0_VSC_Q_49] /* custom */
	#elif defined(ENABLE_VSC_EMMC_VIRT)
			/* custom */
			[GOS0_VSC_Q_49] = { .peers = {GID_GUEST0_VM, GID_VSC_SERVER}, .nframes = 16, .frame_size = 128 },
	#endif
#endif

#if defined(ENABLE_TEST_GPT_L3PT)
	#ifdef ENABLE_HVRTOS_VSC_EMMC_VIRT
			// [GOS0_VSC_M_70] /* custom */
	#elif defined(ENABLE_VSC_EMMC_VIRT)
			/* custom */
			[GOS0_VSC_M_70] = { .peers = {GID_GUEST0_VM, GID_VSC_SERVER}, .size = (SZ_1MB * 8), .align = (SZ_1MB * 2) },
	#endif
#endif

    NOTE: None HVRTOS VSC server is deprecated. The codes inside of ENABLE_VSC_EMMC_VIRT define are not used anymore.

More custom partitions can be added with the same guest ID in the partition_attribute. The container partition name is used to differentiate between multiple GPT partition tables for the same guest.

For the example above the GPT is defined within the sub config file "custom_storage_emmc.cfg".

The following shows an example of how to define GPT L3 partitions.

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/custom_storage_emmc.cfg

    [meta]
    version=2

    [device]
    type=sdmmc
    instance=3
    linux_name=/dev/block/3460000.sdhci
    size=0x380000

    [partition]
    name=sample-gp1
    type=GP1
    allocation_policy=sequential
    filesystem_type=basic
    size=0x40000
    partition_attribute=0

    [partition]
    name=samplep1
    allocation_policy=sequential
    filesystem_type=basic
    size=0x100000
    partition_attribute=1

    [partition]
    name=samplep2
    allocation_policy=sequential
    filesystem_type=basic
    size=0x100000
    partition_attribute=1

    [partition]
    name=samplep3
    allocation_policy=sequential
    filesystem_type=basic
    size=0x100000
    partition_attribute=1

    [partition]
    name=sample-gpt
    type=GPT
    allocation_policy=sequential
    filesystem_type=basic
    size=0x40000
    

Example Changes for QNX GOS VM

Add device tree entry to let QNX enumerate each of the partitions inside the container as virtual block devices, as in the following example:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/storage/tegra234-common-driveav-storage-gos0.dtsi

    #ifdef ENABLE_TEST_GPT_L3PT
    	/* custom */
    	tegra_virt_storage50 {
    		compatible = "nvidia,tegra-hv-storage";
    		status = "okay";
    		instance = <15>;
    		ivc = <&tegra_hv 49>;
    		mempool = <70>;
    		icache = <10485760>;
    		device-type = "vblk_mnand";
    		partition-name = "custom";
    	};
    #endif

    NOTE: Ensure the tegra_virt_storage50 node name is unique in the above mentioned dtsi file.
        Also pick a different instance number in new added node(tegra_virt_storage50 in the example above),
        if that instance number is already in use in other node having same device-type.

The nvsciipc table entry in GOS-DTB:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-nvsciipc-gos0.dtsi

    #ifdef ENABLE_TEST_GPT_L3PT
    		/* GPT container partition */
                    "INTER_VM",      "nvhvblk_49",          "49",  "0",     /* nvhvblk_guest */
    #endif

nvhvblk node(nvhvblk_49 in this example) is added in nvhvblk_orin_gos for this feature:

        <top>/<NV_SDK_NAME_QNX>/nvidia-bsp/aarch64le/sbin/nvsciipc_secpolicy.cfg

        nvhvblk_orin_gos:....,nvhvblk_49,

In case nvsciipc_secpolicy.cfg is modified, QNX-IFS of Guest OS need to be rebuilt.

Example Changes for Linux GOS VM

Add device tree entry to let Linux enumerate each of the partitions inside the container as virtual block devices, as in the following example:

    <top>/<NV_SDK_NAME_LINUX>/kernel/source/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/linux/storage/tegra234-common-storage-linux-gos.dtsi

    #ifdef ENABLE_TEST_GPT_L3PT
    	/* custom */
    	tegra_virt_storage50 {
    		compatible = "nvidia,tegra-hv-storage";
    		status = "okay";
    		instance = <15>;
    		ivc = <&tegra_hv 49>;
    		mempool = <70>;
    	};
    #endif

    NOTE: Ensure the tegra_virt_storage50 node name is unique in the above mentioned dtsi file.
        Also pick a different instance number in new added node(tegra_virt_storage50 in the example above),
        if that instance number is already in use in other node having same device-type.

Bind/Bootburn steps are needed after upper changes.

Caution and Verification

The size of the device at L3 matches the size of the extended custom partition at L2:

The custom container has three partitions each of 1 MB. Note that the filename is not specified above. If file is not specified, flash tools will not create any images for these partitions but the space is allocated and will be formatted if specified. If an image is required, update the partition within the custom cfg file accordingly to add the filename field and point it to the file you want to flash.

Once booted with upper changes, the GPT partitions are enumerated as virtual block devices in each Guest OS(QNX or Linux).

For QNX, for example, if the container block device is enumerated as /dev/vblk_mnandf0, then the individual partitions are /dev/vblk_mnandf0.ms.0, /dev/vblk_mnandf0.ms.1, and /dev/vblk_mnandf0.ms.2.

For Linux, if the container block device is enumerated as /dev/vblkdev15, then the individual partitions are /dev/vblkdev15p1, /dev/vblkdev15p2, and /dev/vblkdev15p3.

Creating Custom QNX Filesystem Image

The GPT partitions added above do not have a file image associated, so create_bsp_images does not generate images for these partitions.

Follow the below steps to create a qnx6 dummy filesystem image with some contents.

1.Create an empty folder mkdir custom_fs.

2.Create some text files using touch, and add some content to the custom_fs folder.

3.Create the qnx_rootfs_build file with the contents and save as qnx_rootfs_build:

	[num_sectors=2048]
	[-followlink]
	[type=link]/tmp=/dev/shmem

4.Make sure that QNX_TARGET and QNX_HOST paths are set correctly.

	$QNX_HOST/usr/bin/mkxfs -t qnx6fsimg qnx_rootfs_build custom_qnxfs.img

QNX (qnx/dual-qnx) PCT NDAS use case provide one more Secondary Image Filesystem (SIFS) by default. With this feature, one of SIFS having latency critical binaries can be loaded first and another SIFS having large number of binaries can be loaded after.

Example Code of adding Second SIFS

"ENABLE_GOS0_SIFS_1 :=" in "profile.mk" file is knob to add another Secondary Image Filesystem (SIFS). "ENABLE_GOS0_SIFS_1" is defined by default in QNX (qnx/dual-qnx) PCT NDAS use case.

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/common_profile.mk

ifeq ($(NDAS_STORAGE_CONFIG),y)
    # Add SIFS_1 by default for NDAS use case
    ENABLE_GOS0_SIFS_1 := y

The following example snippet shows changes required to divide 500MiB "gos0-ifs2"(SIFS0) partition into 250MiB "gos0-ifs2"(SIFS0) and 250MiB "gos0-ifs2_1"(SIFS1) in case "ENABLE_GOS0_SIFS_1" is defined:

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/boot_chain_storage.cfg

    #ifdef NDAS_STORAGE_CONFIG

....

    [partition]
    name=gos0-ifs2
    allocation_policy=sequential
    filesystem_type=basic
    #ifdef ENABLE_GOS0_SIFS_1
        size=0xFA00000
    #else
        size=0x1F400000
    #endif
    partition_attribute=<GID_GUEST0_VM+1>
    type=sec_ifs
    decompression_algorithm=lz4
    stream_validation=yes
    #ifdef ENABLE_SAFETY_HV
        filename=<PDK_TOP>/<NV_SDK_NAME_QNX>/bsp/images/ifs-nvidia-t18x-vcm31t186-guest_vm_safety_secondary.bin
    #else
        filename=<PDK_TOP>/<NV_SDK_NAME_QNX>/bsp/images/ifs-nvidia-t18x-vcm31t186-guest_vm_secondary.bin
    #endif
    virtual_storage_ivc_ch=0x809732E9

    #ifdef ENABLE_GOS0_SIFS_1
    [partition]
    name=gos0-ifs2_1
    allocation_policy=sequential
    filesystem_type=basic
    size=0xFA00000
    partition_attribute=<GID_GUEST0_VM+1>
    type=sec_ifs
    decompression_algorithm=lz4
    stream_validation=yes
    #ifdef ENABLE_SAFETY_HV
        filename=<PDK_TOP>/<NV_SDK_NAME_QNX>/bsp/images/ifs-nvidia-t18x-vcm31t186-guest_vm_safety_secondary.bin
    #else
        filename=<PDK_TOP>/<NV_SDK_NAME_QNX>/bsp/images/ifs-nvidia-t18x-vcm31t186-guest_vm_secondary.bin
    #endif
    virtual_storage_ivc_ch=0x80974732
    #endif

....

#else /* NDAS_STORAGE_CONFIG */
....
    NOTE: Same codes are here for ECO use case.
....
#endif /* NDAS_STORAGE_CONFIG */

    NOTE: Current code using same "filename" for gos0-ifs2 (SIFS0) and gos0-ifs2_1 (SIFS1) due to example code.

The following example snippet shows changes required to add storage node in GOS-DTB:

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/boot_chain_storage.cfg

    #ifdef NDAS_STORAGE_CONFIG

....

#ifdef ENABLE_GOS0_SIFS_1
	tegra_virt_storage60 {
		compatible = "nvidia,tegra-hv-storage";
		status = "okay";
		instance = <1>;
		ivc = <&tegra_hv 50>;
		mempool = <71>;
		icache = <10485760>;
		device-type = "vblk_sifs";
		partition-name = "gos0-ifs2_1";
		no_vblk_enumeration;
		read-only;
	};
#endif

....

    #elif defined(ENABLE_ECO_UFS_SEC_BOOT)
....
         NOTE: Similar codes are here for ECO QSPI+UFS use case. But QSPI+UFS add SIFS1 partition in UFS storage.
....
    #else

         NOTE: Same codes are here for ECO  QSPI+eMMC use case.

    #endif /* NDAS_STORAGE_CONFIG */

The nvsciipc table entry in GOS-DTB:

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-nvsciipc-gos0.dtsi

    #ifdef ENABLE_GOS0_SIFS_1
                "INTER_VM",      "nvhvblk_50",          "50",   "0",    /* nvhvblk_guest */
    #endif

nvhvblk node(nvhvblk_50 in this example) is added in nvhvblk_orin_gos for this feature:

        <top>/<NV_SDK_NAME_QNX>/nvidia-bsp/aarch64le/sbin/nvsciipc_secpolicy.cfg

        nvhvblk_orin_gos:....,nvhvblk_50,

QNX GOS0 startup script to mount SIFS1 after boot in GOS-DTB by automount:

• For Standard package

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-startupcmds-gos0.dtsi

#ifdef ENABLE_GOS0_SIFS_1
			// mount sifs1 after sifs0 mounting is done. "automount -s" should not be executed parallelly.
			<&automount_sifs1>,
			<&nop_sifs1_done>,
#endif
....

#ifdef ENABLE_GOS0_SIFS_1
		// Mount secondary IFS1
		automount_sifs1: automount_sifs1 {
			cmd = "iolauncher automount -s 1 -U 2410:2410";
			sc7 = "nop";
			critical_process = "no";
			heartbeat = "no";
			oneshot = "yes";
		};

		nop_sifs1_done: nop_sifs1_done {
			cmd = "iolauncher --wait --prewait /tmp/secondary_ifs1_mount.done -i nop";
			sc7 = "nop";
			critical_process = "no";
			heartbeat = "no";
			oneshot = "yes";
		};
#endif

• For Safety package

    <top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/common/qnx/tegra234-startupcmds-gos0-safety.dtsi

#ifdef ENABLE_GOS0_SIFS_1
			// mount sifs1 after sifs0 mounting is done. "automount -s" should not be executed parallelly.
			// Add sifs1 mount here not to give impact to boot KPI.
			<&automount_sifs1>,
			<&nop_sifs1_done>,
#endif
....

#ifdef ENABLE_GOS0_SIFS_1
		// Mount secondary IFS1
		automount_sifs1: automount_sifs1 {
			cmd = "iolauncher --secpol-type automount_sifs_t automount -s 1 -U 2410:2410";
			sc7 = "nop";
			critical_process = "no";
			heartbeat = "no";
			oneshot = "yes";
		};

		nop_sifs1_done: nop_sifs1_done {
			cmd = "iolauncher --wait --prewait /tmp/secondary_ifs1_mount.done -i nop";
			sc7 = "nop";
			critical_process = "no";
			heartbeat = "no";
			oneshot = "yes";
		};
#endif

NOTE: the number "1" in "-s" option is to find device node of SIFS that is passed number "1" in "secondary_ifs1" thourgh GOS-DTB "/chosen/bootargs/".

Pass argument to GOS VM through GOS-DTB "/chosen/bootargs/" to make automount parse device node and mount on /:

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/common_profile.mk

ifeq ($(ENABLE_GOS0_SIFS_1),y)
    OS_ARGS_QNX_GOS0_SIFS_1 :=secondary_ifs1=/dev/vblk_sifs10:/
else
    OS_ARGS_QNX_GOS0_SIFS_1 :=
endif

NOTE: the number "1" in "secondary_ifs1" should be matched the number which is passed with "-s" in startup script.

<top>/<NV_SDK_NAME_FOUNDATION>/platform-config/hardware/nvidia/platform/t23x/automotive/pct/drive_av/<PCT>/qnx_gos0_storage.cfg

#define GOS0_OS_ARG         "gpt gpt_sector=0x13001 <OS_ARGS_QNX_ROOTFS> secondary_ifs0=/dev/vblk_sifs00:/ <OS_ARGS_QNX_USER_FS> <OS_ARGS_QNX_UFS_FS> <DBG_OVERLAY_OS_ARGS> <OS_ARGS_QNX_GOS0_SIFS_1>"

NOTE: <OS_ARGS_QNX_GOS0_SIFS_1> will be replaced to "OS_ARGS_QNX_GOS0_SIFS_1" in common_profile.mk after bind_partitions.

Verification to Check Two SIFSs

    # df -hP | grep ifs
    ifs 17M 17M 0 100% /
    ifs 17M 17M 0 100% /
    ifs 53M 53M 0 100% /

    NOTE: Three "ifs"s exist, one is a primary IFS and rest of two "ifs"s are econdary IFSs.
          FYI, displayed size is not parition size, is actual size of included contents.

    # mount
    ifs on / type ifs
    ifs on / type ifs
    /dev/vblk_ufs00 on / type qnx6
    /dev/vblk_mnand00 on / type qnx6
    ifs on / type ifs

    # ls /dev/vblk_sifs*
    /dev/vblk_sifs00 /dev/vblk_sifs10

    NOTE: vblk_sifs00 is SIFS0 having "instance = <0>;" in storage node in GOS-DTB.
          vblk_sifs10 is SIFS1 having "instance = <1>;" in storage node in GOS-DTB.

    # ls /tmp/secondary_ifs*.done
    /tmp/secondary_ifs0_mount.done /tmp/secondary_ifs1_mount.done

    NOTE: /tmp/secondary_ifs0_mount.done is created after SIFS0 is mounted by automount.
          /tmp/secondary_ifs1_mount.done is created after SIFS1 is mounted by automount.

=====================================