I am currently in production stage and use the backup and restore script option to make sure all my new targets (Orin NX 16GB modules) have the same OS version running with all necessary tools.
This worked fine for my previous production batch but my newly ordered Orin NX modules cant be flashed using this method, the backup restore script tells me i am flashing a different module version.
I scanned the barcode on the old and new modules and they both contain the same HW revision (this is where my previous setup failed)
barcode content for both modules is:
699-13767-0000-303,161-0546-10X
Can somebody explain to me why if i buy the same module again (same MPN order code) and the PN on the barcode is also the same, the same method of flashing does not work a second time?
Update, after some digging i found that the nvrestore_partitions.sh script fails due to a mismatch in the board match data, after some googling this turns to a mismatch in the TNSPEC.
Old modules: 3767-303-0000-F.1-1-1-jetson-orin-nano-devkit
New modules: 3767-303-0000-B.1-1-1-jetson-orin-nano-devkit
Can somebody tell me if this change in spec requires SW changes to be made, or can i alter the script to ignore this?
Hi kayccc,
According to that PCN note that only applies to the Orin NX 8GB version and not the 16GB.
Is there an overview as to what the changes are in the TNSPEC code, e.g. can you tell me what the changes are between version B and version F.
They are both PN number 699-13767-0000-303 so i dont know what the change from B to F implies.
B and F are the internal using revision and follow the same specification.
Please modify nvpartitionmap.txt to fit the .B module and verify whether it works successfully.
According to the update from operation team, they’re no HW/SW change on both modules.
They are all buiilt with the same HW for PCN209760, and just internal using revision.
You may ignore this TNSPEC code form the script to confirm whether the backup process work successfully.