Does DriveOS Support Flashing Different targetfs.img for A/B chain?

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

DRIVE OS Version: 6.0.10

Issue Description: Based on my current validation results, the A/B chain partition sizes can be different (for example, configuring the UFS partitions as 90 GB for chain A and 10 GB for chain B). The rootfs sizes can also differ accordingly (e.g., 87 GB for chain A and 8 GB for chain B).

However, the targetfs.img specified for both slots must be the same. When I configure different targetfs.img files for chain A and chain B, the images can be generated and flashed successfully, but the system fails to boot.

I would like to confirm whether this usage is fundamentally unsupported by DriveOS from a design or technical perspective. If it is supported, could you advise which areas I should investigate to debug and locate the root cause (for example, bootloader configuration, chain metadata, filesystem layout, or integrity checks)?

5

This forum is exclusively for developers who are part of the NVIDIA DRIVE® AGX SDK Developer Program | NVIDIA Developer . To post in the forum, please use an account associated with your corporate or university email address. This helps us ensure that the forum remains a platform for verified members of the developer program.