Software Version
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
1.9.10816
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Hello;
We are encountering an error while flashing AGX Orin with SDK Manager. We ran into similar issues even though we tried it many times on two different development kit.
Although we searched the forums for solutions, tried suggested solutions for similar problems but we could not get any result.
Some of suggestions we tried;
Rebooting many times both target and host.
Flashing DRIVE OS 6.0.4.
Removing all files downloaded (and even SDK manager), reinstalling all and starting a clean setup.
Changing USB ports and USB cables we connected target to host.
Starting target in recovery mode manually (with button).
Changing target mode to recovery mode by MCU console tegrarecovery command
Disabling USB suspend in Ubuntu.
Running bootburn.py in console without SDK Manager. After the command executed succesfully we tried to flash target over SDK manager again but we got same issue.
Additionally we are having the issue on different installation percentage on all tries. But all executions are finishing with same error codes showed in screenshot below.
If you still have the issue, please provide the host dmesg log and the target flashing kernel log with the below description:
For the host dmesg log, on the x86 host where you are running SDKM, open a terminal window and enter the command “dmesg -T”
For the target flashing kernel logs, in another terminal window on the host you need to open a minicom connection to the Tegra (“sudo minicom -w -D /dev/ttyACM0”), redo the flashing, and copy paste the output to a file.
Yes, We are sure that we used USB 3.0 port on the host PC with micro USB cable for host PC connection and we used USB 2.0 port on the host PC with USB type-C cable for flashing.
We are still seeing USB 3.0 in your log. Please use a USB 2.0 cable to avoid negotiation as 3.0 speed.
[Sal Ara 13 14:10:48 2022] usb 1-2: Manufacturer: NVIDIA Corp.
[Sal Ara 13 14:13:29 2022] usb 1-2: USB disconnect, device number 13
[Sal Ara 13 14:13:29 2022] usb 1-2: new high-speed USB device number 14 using xhci_hcd
[Sal Ara 13 14:13:29 2022] usb 1-2: New USB device found, idVendor=0955, idProduct=7023, bcdDevice= 4.01
[Sal Ara 13 14:13:29 2022] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Sal Ara 13 14:13:29 2022] usb 1-2: Product: APX
[Sal Ara 13 14:13:29 2022] usb 1-2: Manufacturer: NVIDIA Corp.
[Sal Ara 13 14:13:32 2022] usb 1-2: USB disconnect, device number 14
[Sal Ara 13 14:13:39 2022] usb 2-8.3: new SuperSpeed USB device number 5 using xhci_hcd
[Sal Ara 13 14:13:39 2022] usb 2-8.3: New USB device found, idVendor=0955, idProduct=7100, bcdDevice= 5.10
[Sal Ara 13 14:13:39 2022] usb 2-8.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sal Ara 13 14:13:39 2022] usb 2-8.3: Product: FunctionFS gadget (adb)
[Sal Ara 13 14:13:39 2022] usb 2-8.3: Manufacturer: NVIDIA
[Sal Ara 13 14:13:39 2022] usb 2-8.3: SerialNumber: 8S2TQACM8000002G50A0
[Sal Ara 13 14:15:14 2022] usb 2-8.3: Disable of device-initiated U1 failed.
[Sal Ara 13 14:15:14 2022] usb 2-8.3: Disable of device-initiated U2 failed.
[Sal Ara 13 14:15:14 2022] usb 2-8.3: reset SuperSpeed USB device number 5 using xhci_hcd