Some details on manually working with the “driver package” and “sample root filesystem” might help here. JetPack/SDKM is itself only a front end to this, and for adding optional extra packages. I’m not sure how JetPack/SDKM deals with alternate install locations (never tried), but this is how you would work with manual command line install.
Wherever you are at when you unpack the “driver package” you will end up with the “
Linux_for_Tegra/” subdirectory. Whenever JetPack/SDKM runs, this directory exists only because it unpacked the driver package there. The driver package itself should not be unpacked with
sudo and should only be unpacked as your regular user.
Once you have the driver package installed there will be an empty (other than a README) directory at “
Linux_for_Tegra/rootfs/”. This is where you unpack the sample rootfs. You must be careful to use
sudo in unpacking the sample rootfs since file permissions and ownerships must be preserved. This puts a lot of purely Ubuntu content into the “
When NVIDIA drivers are added to the purely Ubuntu rootfs this can be called “Linux for Tegra” (or “L4T”). This is the actual content which is going to end up being used for generating an image and flashing with that image. The method of adding those drivers is to use
sudo and run the command “
sudo ./apply_binaries.sh” from the “
Linux_for_Tegra/” directory. Once this is done you are ready to flash however many times you want without having to repeat any of those above steps again.
If your Jetson is in recovery mode and attached to the host with the micro-B USB cable, then this should flash:
sudo ./flash.sh jetson-tx2 mmcblk0p1
Keep in mind that while flashing is going on it will create images the size of the entire TX2 eMMC, and so this is going to consume a lot of space on the host PC. If you have 16GB of eMMC, then over 16GB will be used the first time flashing. If you have a Jetson with 32GB of eMMC, then over 32GB will be consumed from the host PC file space if it is the first flash. Additional flashes do generate the same size content, but it overwrites the current temporary content rather than saving the old generated content.
If you want to flash on command line, then you can log the flash like this:
sudo ./flash.sh jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt
(text logs can be attached to the forum and are far easier to work with than images)