I am trying to flash a Jetson Orin AGX in a way that it will have a user after flash. To do this I am manually flashing through the command line. I am getting an error that the general flash has failed. I have confirmed through lsusb that the device is in forced recovery mode. Any suggestions on what I should do? I have attached the output of the flash.
out.txt (55.7 KB)
Hello @lamblily90,
According to NVIDIA’s Documentation you should try a couple of things:
- First try using a different USB port on your Host PC.
- Try disabling USB Port auto-suspend:
sudo bash -c 'echo -1 > /sys/module/usbcore/parameters/autosuspend'
Please note that after disabling auto suspend you should reboot your board into recovery mode again and unplug then plug the usb cable into your host pc.
Please give that a try and let us know how it goes.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
Had to switch computers and when we set up everything (and turned off auto suspend) this is the new log.
out (1).txt (17.0 KB)
Hello @lamblily90,
That is an interesting new issue.
Can you please share the command you are using to flash the device?
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I am using this and I have confirmed my device is in forced recovery mode through lsusb:
sudo ./flash jetson-orin-agx-devkit mmcblk0p1
Thanks @lamblily90,
That command looks good.
The error is very estrange. Never seen it before. The weirdest part is that it really doesn’t show what is actually breaking.
Can you try flashing with SDK manager just to make sure that it works that way on your new host setup?
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I actually tried that as well and it failed at the same point.
Please try sdkmanager with some old version like rel-35.5 first and see if it can flash your module.
And please do share the full sdkmanager log by clicking the “export logs” button on the GUI.
I tried to flash it with the latest version I could (Jetpack 6.1) Here are the logs.
SDKM_logs_JetPack_6.1_(rev._1)Linux_for_Jetson_AGX_Orin[64GB_developer_kit_version]_2025-07-09_10-25-40.zip|attachment (810.1 KB)
I saw the same weird behavior too.
There is actually no specific error log from it and it just failed.
Could you share the result of command df -T on your host PC?
Looking at one of the logs it shows sdkmanager download failures. Recently there have been some intermittent outages reported of nvidia apt download server
This might help. Close sdkmanager. then delete the directory that’s named similar to JetPack_6.1_Linux_JETSON_AGX_ORIN_TARGETS
or your JetPack_5.1.5_Linux_JETSON_AGX_ORIN_TARGETS
Then run sdkmanager and it will recreate the directory.
If it still fails then you could try
cd …/Linux_for_Tegra
Then run
sudo ./apply_binaries.sh
The original error (which is the same error from the sdk manager) is from the command line method where I ran applies binaries. I just tried it and it failed in the same place, here are the new logs
SDKM_logs_JetPack_6.2.1_Linux_for_Jetson_AGX_Orin_[64GB_developer_kit_version]_2025-07-10_08-35-59.zip (784.0 KB)
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 3252472 2888 3249584 1% /run
/dev/nvme0n1p2 ext4 982862268 117727036 815134900 13% /
tmpfs tmpfs 16262344 0 16262344 0% /dev/shm
tmpfs tmpfs 5120 4 5116 1% /run/lock
tmpfs tmpfs 16262344 0 16262344 0% /run/qemu
/dev/nvme0n1p1 vfat 523248 6232 517016 2% /boot/efi
tmpfs tmpfs 3252468 108 3252360 1% /run/user/1003
Is it possible to just try old Jetpack5 first? I saw all the things you tried here are all Jetpack6.
I know you may want Jetpack6 only, but this is just a quick check.
Unfortunately the device I am flashing from is Ubuntu 22 and sdk manager will not allow me to go below jetpack 6
What is your exact command line when flashing on command line?
and I am flashing a jetson orin agx 64
You setup your user account with this command or something like it?
cd Linux_for_Tegra
sudo ./tools/l4t_create_default_user.sh -u “username” -p “apassword” -n “nameAgxOrin” --accept-license
If so you could try this just as a different way to start flash.
sudo sdkmanager --cli --action install --login-type devzone --product Jetson --version 6.2.1 --target-os Linux --host --target JETSON_AGX_ORIN_TARGETS --flash
Lots of good advice here, and the flash command seems valid, so I’m going to ask something slightly different. I’ve seen flash logs using L4T R35.x (JetPack 5.x if using JetPack) and L4T R36.x (JetPack 6.x if using JetPack). Did you switch directories on the host PC for the two? If JetPack/SDK Manager installed this, then it definitely (automatically) uses different directories and would download sufficient content by the time of the first use. If everything on the host PC (or part of) is installed manually, then there is a possibility of mixing software that should not be mixed. I know you are flashing on command line, and your command looks valid, but how was your content added to the host PC, and was the addition to different locations?
In the case of manual setup (I don’t know yet if you manually set this up, so this might not even apply, ignore it if not applicable) can you delete that content and install again via JetPack/SDK Manager? Some information you might be interested in if you do this is that a newer JetPack/SDK Manager can be started like this to see older releases:
sdkmanager --archived-versions
A list of L4T releases is here, and this is what actually gets flashed (there is a similar JetPack/SDKM release URL, and eventually it will lead to an L4T URL…they are “sort of” equivalent and interchangeable):
https://developer.nvidia.com/linux-tegra
The JetPack/SDKM URL is here (and would eventually lead to the L4T URL, but it isn’t quite as obvious and I think the L4T URL is more useful):
https://developer.nvidia.com/embedded/jetpack-archive
Someone else mentioned some network issues, which is a good catch. Normally JetPack/SDKM (SDK Manager is the “smart network” layer) would tell you about issues. If you were to do this manually though, and just for flash, then you’d go to the L4T release URL and download the “driver package” and the “sample root filesystem”. You’d unpack the driver package as a regular user (go to any empty directory, specific location not important if not using JetPack), and then unpack the sample rootfs in the “Linux_for_Tegra/rootfs/” subdirectory created by the driver package unpack. I think I saw you already did this, but to be thorough, you’d then run (once and only once) “sudo ./apply_binaries.sh” from the “Linux_for_Tegra/” location. Optionally, if you want to pre-create the login information, you could run the “sudo ./l4t_create_default_user.sh” script. After that you could attempt flash with the creation of a log on command line like this:
sudo ./flash jetson-orin-agx-devkit mmcblk0p1 2>&1 | tee log_flash.txt
# Then attach log_flash.txt to the forum.
I’m going through this because everyone has given good advice (e.g., turning off USB autosuspend) and it might be a good idea to check procedure. Do note that a purely command line approach would allow you to flash any of the L4T R35.x or R36.x on an Ubuntu 22 host. It isn’t recommended, mostly because you won’t have JetPack/SDKM checking on requirements. The trick is that if the flash requirements are met, then it will work even on different distributions and not just the particular Ubuntu release for host. Note that JetPack/SDKM 6.x is normally tied to L4T R36.x, and that R36.x should work with an Ubuntu 22.04 host PC. Try to stick with that. If you want to manually install L4T R35.x to a different location without deleting the other content, then you can do this on command line (just don’t expect help from JetPack/SDKM).
You can actually perform a manual attempt with L4T R36.x in a new location separate from what JetPack/SDKM uses if you go entirely manual with unpack into a new empty location.
Any time you flash on command line always log it similar to what I named above. Whatever release or target Jetson is, you can append this to the end to log a flash:
" 2>&1 | tee log_flash.txt"
(always name the exact command line used to flash when you post that log)
Looking through your most recent logs. sdkmanager failed when running this file. Can you upload it here as a text file?
/home/IntegerRadar/.nvsdkm/replays/scripts/JetPack_6.2.1_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh
Here’s the error.
08:38:24.614 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_AGX_ORIN_TARGETS: [exec_command]: /bin/bash -c /home/IntegerRadar/.nvsdkm/replays/scripts/JetPack_6.2.1_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: *** ERROR: flashing failed.