With JetPack 7, users are now able to flash their Jetson modules from a Ubuntu 24.04 host machine. The host requirements remain the same as in previous releases: Ubuntu must be installed natively on the system. Flashing from virtual machines or bootable USB environments is not officially supported and may cause issues.
Along with this requirement, there are also dependencies that must be installed on the Ubuntu 24.04 host device in order to flash. To follow our flashing guide, kdb373, please first install the following packages:
$ sudo apt-get install net-tools bzip2 qemu-user-static xmlstarlet abootimg libxml2-utils binutils -yIf you are running the flashing commands from an ssh connection you may also need to install the following:
$ sudo apt-get install openssh-server sshpass
With these dependencies installed, you should now be able to follow kdb373 to flash your Jetson device.
If you have difficulties flashing after installing these dependencies to your native Ubuntu 24.04 Host, please see the diagnostic steps below to the most common issues found related to flashing.
1. Ensure the correct port of the CTI carrier is being used to flash
Ensure you are connected to the OTG port of your CTI carrier. This port will be referenced in the relevant CTI carrier manual.
2. Try different cables/ports on the Host device
This is by far the most common cause of a flash attempt failing. Please try different cables and different ports on the Host device.
3. Verify the power supply
Information on the appropriate power for the system can be found in the relevant CTI carrier manual.
4. Ensure the CTI system is in recovery mode
Instructions on how to put the system into forced recovery can be found in the relevant CTI carrier manual. To confirm it has been successfully put into force recovery mode run $ watch lsusb from a terminal prior to following the Force Recovery instructions and confirm a NVIDIA Corp. device enumerates during the process.
5. Restart your Host device
Our team has found that restarting your Host device may resolve certain flashing issues.
6. Try using CTI's alternate flashing method
An alternate method to flash is through CLI, this procedure is as follows:
$ sudo su $ mkdir <L4T Directory> && cd <L4T Dir> $ wget https://developer.nvidia.com/downloads/embedded/l4t/<RELEASE VERSION>/release/<DRIVER PACKAGE (BSP)> $ wget https://developer.nvidia.com/downloads/embedded/l4t/<RELEASE VERSION>/release/<SAMPLE ROOT FILESYSTEM> $ wget https://connecttech.com/ftp/Drivers/<CTI L4T BSP> $ tar -xvf <DRIVER PACKAGE (BSP)> $ tar -xvf <SAMPLE ROOT FILESYSTEM> -C Linux_for_Tegra/rootfs $ tar -xvf <CTI L4T BSP> -C Linux_for_Tegra $ cd Linux_for_Tegra/CTI-L4T $ ./install.sh 2>&1 | tee install.txt $ cd .. $ ./cti-flash.sh 2>&1 | tee flash.txt
Note, the wget & tar lines will need to be changed based on what L4T version is being built.
NVIDIA downloads can be found here: https://developer.nvidia.com/embedded/downloads & CTI downloads here: https://connecttech.com/resource-center/l4t-board-support-packages/
If you are still having trouble flashing your device after going through this guide, please reach out to CTI support and provide the install.txt and flash.txt files generated in diagnostic step 6.