Note that if this is an eMMC model, then there are security fuses you can burn with a key. Once you do that though much of the content can only be flashed with that key (this is not encryption). I don’t think there is such an ability with SD card models.
When flashing the dev kit, I am flashing to an external eMMC SSD, which has an image of various scripts and content.
The dev kit I am working on was originally flashed this way by my predecessor. He has set me the challenge of recreating his method, but I was having difficulty until he briefly explained that there is a UUID file in the “bootloader” folder of the NVIDIA filesystem used for flashing (I am not using the SDK Manager).
I am trying to understand;
• Was the UUID (file) created when flashing, or was it created manually?
◦ (Where does the UUID come from?)
• Can it be changed?
◦ (IF the UUID is created when flashing (not created manually), is it created randomly each time and is it possible to make the UUID the same if I were to flash a number of devices?)
• How is the UUID used?
◦ (Would I be correct to believe that there is a script on the external eMMC SSD that verifies the presents of the UUID when the dev kit starts up?)
Are you aware of any documentation that could give me a better understanding of a UUID?
typically, you can find the UUID of all the disk partitions by running blkid commands.
this UUID doesn’t change unless you format/delete the disk, it’ll generate a new UUID for the new filesystem.