*** Update see end ***
Orin AGX 32GB dev kit will boot to Ubuntu login screen. Using nvidia/nvida user:pass the screen briefly goes black but then returns to the login screen. Other user/password combinations show an error saying “wrong password”
Tried to reflash with SDKManager. The device is recognised by SDKManager but when going to do the flash it gives an error
" The connected Jetson device is not ready for flash.**
The issue is likely related to a non-optimal USB connection."
I have tried different USB cables / USB hub / No Hub / Different ports. These all give the same error.
Also tried this command on the host PC “echo -1 > /sys/module/usbcore/parameters/autosuspend” to avoid timeout in connections.
*** Update 1***
- I have tried to enter the UEFI setup menu screen but when pressing escape on boot the device doesn’t output anything to a monitor. Rebooting the device does allow it to go to the Ubuntu login screen but I can’t seem to get to the UEFI menu.
- Using UART Serial login method and command “minicom -D /dev/ttyACM0 -8 -b 115200” I do get to a login request within the terminal. Using the user/password I get the following info
"tegra-ubuntu login: nvidia
Password:
Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.10.120-tegra aarch64)
This system has been minimized by removing packages and content that are
not required on a system that users do not log into.
To restore this content, you can run the ‘unminimize’ command.
Expanded Security Maintenance for Infrastructure is not enabled.
48 updates can be applied immediately.
40 of these updates are standard security updates.
To see these additional updates run: apt list --upgradable
46 additional security updates can be applied with ESM Infra.
Learn more about enabling ESM Infra service for Ubuntu 20.04 at
XXX
Last login: Fri Jul 25 16:03:27 UTC 2025 on ttyGS0
This account is currently not available.
Ubuntu 20.04.6 LTS tegra-ubuntu ttyGS0"
I’m unsure why it says “This account is currently not available”.
*** Update 2 ***
Using a different laptop / OS (Ubuntu 24.04) I was able to get the SDKManager to flash the OS but when getting to SDK component install I received an error about IP address not being available. I skipped this stage and the SDKManager finished. When booting the Orin now I no output from HDMI. Returning to recovery mode and SDKManager the Orin is detected again. Any thoughts on how to get this fixed?
Any tips?
Regarding the flash, if this is your first time flashing a Jetson, then please make sure you put the board into recovery mode before your attempt to flash.
*** Please note that this reply is generated by LLM automatically ***
The issue you’re experiencing with the Jetson AGX Orin 32GB dev kit seems to be related to a combination of factors, including USB connection issues and potential problems with the device’s state. Here are some tips and potential solutions to help you resolve the issue:
- USB Connection Issues: The error message “The connected Jetson device is not ready for flash” suggests that the device is not properly connected or recognized by the SDKManager. You’ve already tried different USB cables, hubs, and ports, which is a good troubleshooting step. However, you can also try:
- Using a high-quality USB cable that is specifically designed for data transfer.
- Ensuring that the USB port on the host PC is not a USB 3.0 port, as some users have reported issues with USB 3.0 ports.
- Trying a different host PC or a different USB controller on the same PC.
- Device State Issues: The fact that the device boots to the Ubuntu login screen and then returns to the login screen after entering the correct username and password suggests that there might be an issue with the device’s state. You can try:
- Performing a force recovery mode reset on the device. This will reset the device to its default state and may resolve any issues related to the device’s state.
- Reflashing the device using the SDKManager, but this time, try using the “Force Flash” option. This will reflash the device even if it’s not in a optimal state.
- SDKManager Issues: The SDKManager error message “The connected Jetson device is not ready for flash” might be related to a issue with the SDKManager itself. You can try:
- Updating the SDKManager to the latest version.
- Trying a different version of the SDKManager.
- Checking the SDKManager logs for any error messages that might indicate the cause of the issue.
- Timeout Issues: The command
echo 1 > /sys/module/usbcore/parameters/autosuspend is used to avoid timeout issues in connections. However, you can also try:
- Increasing the timeout value in the SDKManager settings.
- Disabling the autosuspend feature on the host PC.
In comparison to other Jetson devices, the Jetson AGX Orin 32GB dev kit is a relatively new device, and it’s possible that there are some teething issues with the SDKManager and the device’s firmware. However, the steps outlined above should help you resolve the issue.
It’s also worth noting that the Jetson Orin NX and Nano devices have similar issues with USB connections and device state, and the solutions outlined above might also be applicable to those devices.
In terms of the specific error messages you’re seeing, the “wrong password” error message is likely related to the device’s state, and the “The connected Jetson device is not ready for flash” error message is likely related to the USB connection issues.
I hope this helps! Let me know if you have any further questions or if there’s anything else I can help you with.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
I press and hold the middle button on the side when booting. Within the SDK Manager Software when you look at the connected device is says its status is Recovery.
“force recovery mode reset” - > This is the step of pressing the middle button on the side and power cycling the device? This does show that it is in “Recovery” mode in the SDKManager but nothing will show on the screen with HDMI connected to the device if you enter this mode.
Hi
Is your host machine a VM or native Ubuntu host?
Are you sure that type C cable really can flash the device? For example, not some cheap cable which could only do charge.
I have now tested using SDKManager on a different host PC with Ubuntu 20.04 and have tried to install JetPak 5.1.5 instead of 6.2.1 to see if that completes and allows the device to boot. But I get an error within SDRManager for the OS install part. I have the logs from the install and can attach here.
SDKM_logs_JetPack_5.1.5_Linux_for_Jetson_AGX_Orin_32GB_2025-07-29_16-35-02.zip (496.3 KB)
Previous issues on 20.04 Ubuntu SDKManager install was due to apt update repositories. Fixed this Ubuntu issue and re-ran SDKManager install. Also failed and new error states:
17:10:46 ERROR: [ 0.0421 ] ERROR: failed to read rcm_state
17:10:46 ERROR: [ 0.3585 ] Error: Skip generating mem_bct because sdram_config is not defined
17:10:43 INFO: [host] [ Disk Avail on Partition /dev/nvme0n1p6: 62.30 GB ]
17:10:46 ERROR: [ 0.3585 ] Error: Skip generating mem_bct because sdram_config is not defined
17:10:43 INFO: Installing component ‘Flash Jetson Linux’ (NV_L4T_FLASH_JETSON_LINUX_COMP)
17:10:51 ERROR: [ 0.4381 ] ERROR: might be timeout in USB write.
17:10:43 INFO: change working directory to /home/sdrlaptop1/nvidia/nvidia_sdk/JetPack_5.1.5_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra
17:10:51 ERROR: Error: Return value 3
17:10:43 INFO: [ Component Install Started ]
17:10:43 INFO: current working directory is /home/sdrlaptop1/nvidia/nvidia_sdk/JetPack_5.1.5_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra
17:10:51 ERROR: — Error: Reading board information failed.
17:10:43 INFO: exec_command [host]:
17:10:51 ERROR: command error code: 11
17:10:43 INFO: **********************
17:10:51 ERROR: command terminated with error
17:10:43 INFO: set -e
17:10:51 SUMMARY: Installation failed.
SDKM_logs_JetPack_5.1.5_Linux_for_Jetson_AGX_Orin_32GB_2025-07-29_17-05-20.zip (1.0 MB)
The log you attached is not same as what I saw from the zip file. I don’t know which one is correct.
From the zip file, I saw this log
17:10:46.297 - Info: [ 0.3663 ] BR_CID: 0x80012344705DF1083000000013FE0100
17:10:46.340 - Info: [ 0.3947 ] Sending bct_br
17:10:51.376 - Info: [ 0.4381 ] ERROR: might be timeout in USB write.
If the timeout error happens right after the bct_br case, then it is related to usb auto suspend.
Please disable auto suspend and then replug the usb cable again and also put the board into recovery mode again.