The target is in a bad state. "NVIDIA USB Device was removed (APX)" immediately after flash starting. Jetson AGX Orin 64GB

I’m working on WSL2 with Ubuntu 18.04 and attempting to flash JetPack 5.1.3. Everything seems to be going well until the flashing process starts, as the Jetson AGX Orin 64GB device is in recovery mode.
I do everything like attached: Windows Subsystem for Linux (WSL) — SDK Manager 2.1.0 documentation
I’m using a USB 3.0 5Gb/s connection on my host device with a suitable cable connecting to the Jetson

On Windows PowerShell, I perform the following steps:
PS C:\Windows\system32> usbipd list
Connected:
BUSID VID:PID DEVICE STATE
1-1 0955:7023 APX Shared
1-5 27c6:639c Goodix MOC Fingerprint Not shared
1-6 0bda:5556 Integrated Webcam, Camera DFU Device Not shared
1-10 0bda:c829 Realtek Bluetooth Adapter Not shared

PS C:\Windows\system32> usbipd attach --wsl --busid 1-1
usbipd: info: Using WSL distribution ‘Ubuntu-18.04’ to attach; the device will be available in all WSL 2 distributions.
usbipd: info: Using IP address 172.20.0.1 to reach the host.
PS C:\Windows\system32>

In my WSL2 Ubuntu environment, I verify that the device is recognized:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 031: ID 0955:7023 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I downloaded everything without problems.
When it is time for flashing, I set 1.Runtime 2.EMMC (default). I tried many things and configurations, but the same problem occured. It also didn’t worked on Ubuntu 20.04 with the same issue.


Hello @lsisoftware.ai,

Can you try using the flash script on ~/nvidia//Linux_For_Tegra/ ?

./flash.sh jetson-agx-orin-devkit mmcblk0p1

Also, if possible. Connect to the board through UART, so you can see what happens during the flash procedure.

Please let us know how it goes.

Andrew,
Embedded Software Engineer
ContactUs: support@proventusnova.com
www.proventusnova.com

I tried this mentioned command, but made this in other way right now. When I run that script, jetson disconneted as always. When it disconnected I run on powershell:
usbipd attach --wsl --busid .

Jetson connected and the flashing process went correctly.
Is it a hardware problem with my jetson?

Hello @lsisoftware.ai,

It might not be a problem with the Jetson, but maybe with the host machine.

You are using windows, correct?

Also, when you say that the flashing procedure went correctly, do you mean that it completed successfully?

regards,
Andrew
Embedded Software Engineer
ContactUs: support@proventusnova.com
www.proventusnova.com

Yes, it completed successfully. I have my jetson working as I wanted

@lsisoftware.ai,

Sounds great!

Then yes, it seems more like an issue with the host machine than with your Jetson.

Hope we were able to help a bit.

Please do not hesitate to reach out if you require further assistance, we would love to help.

regards,
Andrew
Embedded Software Engineer

1 Like