I used SDK Manager to flash an NVMe SSD on a Jetson AGX Orin Dev Kit 64GB.
Now, I would like to know if I can simply move this SSD to a Jetson AGX Orin Dev Kit 32GB and expect everything on the SSD (OS, rootfs, applications, etc.) to work normally without reflashing.
Since both models share the same SoC and flashing process, I assume it should be possible, but I’d like to confirm whether NVIDIA officially supports this kind of cross-usage between the 64GB and 32GB Dev Kit versions.
*** Please note that this reply is generated by LLM automatically ***
According to the provided context, the Jetson AGX Orin Dev Kit 64GB and 32GB share the same SoC (System on Chip) and flashing process. This suggests that the NVMe SSD flashed on the 64GB Dev Kit should be compatible with the 32GB Dev Kit.
However, to confirm whether NVIDIA officially supports this kind of cross-usage between the two Dev Kit versions, let’s examine the relevant information:
Hardware Compatibility: Both the Jetson AGX Orin Dev Kit 64GB and 32GB use the same SoC, which implies that the hardware architecture is identical. This increases the likelihood of compatibility between the two devices.
Flashing Process: The flashing process for both devices is the same, as indicated by the use of the same flash.sh script. This suggests that the software configuration and partition layout are also compatible.
Software Support: The context mentions that the Jetson AGX Orin series supports flashing to an external storage device, such as an NVMe SSD. However, it does not explicitly state that the SSD can be moved between different Dev Kit versions.
To provide a comprehensive answer, let’s consider the following points:
Root File System (rootfs): The rootfs is stored on the NVMe SSD, which contains the operating system, applications, and other data. Since the SSD is flashed with the same software configuration and partition layout, it is likely that the rootfs will work normally on the 32GB Dev Kit.
Device Tree: The device tree is a data structure that describes the hardware components of the system. Although the SoC is the same, there might be differences in the device tree between the 64GB and 32GB Dev Kit versions. However, this is unlikely to affect the compatibility of the NVMe SSD.
NVIDIA Official Support: Unfortunately, the provided context does not explicitly state that NVIDIA officially supports moving an NVMe SSD between different Dev Kit versions. However, based on the hardware and software compatibility, it is likely that the SSD will work normally on the 32GB Dev Kit.
In conclusion, while there is no explicit statement from NVIDIA regarding the official support for moving an NVMe SSD between different Dev Kit versions, the hardware and software compatibility suggest that it should work normally. However, it is always recommended to verify the compatibility and functionality of the SSD on the 32GB Dev Kit before using it in production.
To minimize potential risks, you may want to consider the following:
Verify the device tree and software configuration on both Dev Kit versions to ensure they are identical.
Test the NVMe SSD on the 32GB Dev Kit to ensure it works normally and all applications and data are accessible.
If you encounter any issues, consider reflashing the SSD with the 32GB Dev Kit’s software configuration to ensure optimal compatibility.
By taking these precautions, you can minimize potential risks and ensure a smooth transition of the NVMe SSD between the two Dev Kit versions.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
If I encounter the failure case (for example, the AGX Orin 64GB is using JetPack 6.2, but the AGX Orin 32GB is still on JetPack 5.x), what is the recommended way to resolve this?
Should I re-flash the 32GB module with the same JetPack version as the 64GB kit using SDK Manager?
Or is there a way to update the bootloader / JetPack version on the 32GB device without a full re-flash?
I would appreciate your guidance on the proper procedure to handle this case.