cannot connect with ORIN 64 after flashing with 5.1.1
cannot flash now to 5.1.2
Hello and welcome to the forums. This topic belongs in the Jetson category, I have moved it over for you.
Tom
What does this mean? Can’t boot well or?
How did you flash the device? With SDKM on a Ubuntu 20.20 host PC?
Please provide more description of your issue, then we can know how to help.
You can also check Getting Started with Jetson AGX Orin Developer Kit | NVIDIA Developer to see if can ehlp.
At least post some log here…
I flash it with SDKManager on a UBuntu 18.04
Neither of your two comments in this post provides any useful information…
Do you know what I mean with log?
Can you help me how to get logs from …… sdkmanager ??? Orin ???
This particular Orin device was updated from an older version to Jetpack 5.1.1 with this same equipment ( UBuntu)
Same equipment is and has been used to flash multiple NX, AGX and other Orin devices multiple times with successful results
And it is the only use for this particular device only SDKManager.
In particular, we have only one Orin 64 GB.
And this device, once was flashed to 5.1.1, cannot connect to SDKManager through USB Cable, making impossible to flash it again.
Either downgrade to 5.1 or upgrade to 5.1.2
Hope this help to understand the actual issue
Gustavo
+56 9 9827 2748
What do you mean with cannot connect to SDKManager through USB Cable?
Have you put it into force recovery mode? Was it detected with lsusb?
Was it detected with lsusb?
NO
here is the output from lsusb before and after plugging USB
gossando@udesktop4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gossando@udesktop4:~$
gossando@udesktop4:~$
gossando@udesktop4:~$
gossando@udesktop4:~$
gossando@udesktop4:~$
gossando@udesktop4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gossando@udesktop4:~$
gossando@udesktop4:~$
and this is same command after plugging a Jetson NX Xavier
gossando@udesktop4:~$
gossando@udesktop4:~$
gossando@udesktop4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 006: ID 0955:7020 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gossando@udesktop4:~$
gossando@udesktop4:~$
where you can see NVIDIA device shows immediately
recovery mode usually did not work … will try again
gus
Check this :
Ensure that the developer kit is powered off.
Press and hold down the Force Recovery button.
Press, then release the Power button.
Release the Force Recovery button.
, and run lsusb again.
Impossible to use USB-C because ORIN module do not have USB-C ( like AGX for example )
Already tried changing microUSB cable with similar results
Gus
+56 9 9827 2748
Are you using a third-party carrier board here?
AGX Orin Developer Kit by NVIDIA uses a USB-C port for flashing.
Please contact the vendor for help or maybe RMAing the device.
This does not mean anything. 7020 is the code for USB device mode, but not for force recovery mode.
You should get 0955:7e19 with a Xavier NX that is in force recovery mode.
Similarly, 0955:7023 for AGX Orin 64GB.
https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/IN/QuickStart.html#to-determine-whether-the-developer-kit-is-in-force-recovery-mode
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.