There are a lot of boot related partitions which won’t matter to you, and there will be the root filesystem (“rootfs”). It is this latter you can easily clone and use during a flash, but the JetPack/L4T/SDK Manager release used to flash will need to be from the same release as the rootfs clone. All of your content goes in the rootfs, and the only reason you’d ever care about the other partitions is if you had some sort of modified boot, e.g., encryption or signing. Exact instructions depend on which L4T release you are using.
Depending on which release you have, one of these will tell you your current release:
head -n 1 /etc/nv_tegra_release
dpkg -l | grep 'nvidia-l4t-core'
Which release are you working with, and are you concerned only with the running operating system rootfs, or are you customizing something in the boot environment?
We can add more details later, but basically if you were to flash a unit on command line and not using a clone, then this would fully flash with a brand new stock rootfs (executed from the “
sudo ./flash.sh jetson-txt2 mmcblk0p1
As soon as you add the “
-r” option the rootfs image is no longer generated fresh, and you reuse whatever is there (which can conveniently be a clone of your “golden image”):
sudo ./flash.sh -r jetson-tx2 mmcblk0p1
The clone is a very big file though, so you have to prepare. This is also where different releases may differ in instructions to clone.