WSL instance pre setup failed: Bind USB port failed

[cmckenna]

We’ve been using Jetson AGX Orin with JetPack 6.0 rev1 for about a year now and just started having trouble with it today. At first it wouldn’t boot, but now I can’t even get the BIOS or any text to show up on the screen when it is powered on (light).

I tried using the SDK manager to reinstall Jetpack, but even though I was able to detect the device I got an error.

“WSL instance pre setup failed: Bind port failed.”

At the top of your install doc it says,

”For Windows users: JetPack installation is now supported on Windows for Jetson AGX Orin and Jetson AGX Thor devices. This new method, available starting with JetPack 6.2.1, uses Windows Subsystem for Linux (WSL) to flash your Jetson device.”

So I didn’t think I had to mess with attaching the USB to WSL. Any idea what’s going on?

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues with your Jetson AGX Orin device, specifically with booting and displaying the BIOS or text on the screen. You have also tried reinstalling JetPack using the SDK manager, but encountered an error related to WSL instance setup.

Firstly, let’s address the WSL-related error. The documentation mentions that JetPack installation is supported on Windows for Jetson AGX Orin and Jetson AGX Thor devices using WSL. However, it’s possible that the issue lies in the fact that you didn’t attach the USB to WSL. To resolve this, you can try the following:

1. Connect your Jetson AGX Orin device to the USB port on your Windows host computer.
2. Open the Windows Subsystem for Linux (WSL) and ensure that it’s running.
3. Attach the USB device to WSL using the wsl --attach command.
4. Try reinstalling JetPack using the SDK manager.

Regarding the boot issue, it’s possible that the problem lies in the boot flow or partition configuration. The Jetson AGX Orin Boot Flow consists of the following stages:

1. BootROM
2. PSCROM
3. MB1
4. MB2 (including MB2 Applet)
5. UEFI

You can try to troubleshoot the issue by checking the boot flow and partition configuration. Here are some steps to follow:

1. Check the partition configuration files to ensure that they are correct and not corrupted.
2. Verify that the boot flow is correct and that the device is booting from the correct partition.
3. Try to boot the device in recovery mode by pressing the recovery button during boot.

Additionally, you can try to debug the issue using the Register Trace Buffers (RTB) feature, which allows you to capture and analyze the boot flow and system activity.

In comparison to other Jetson devices, the Jetson AGX Orin has a similar boot flow and partition configuration. However, the specific stages and components may vary depending on the device. For example, the Jetson Xavier NX and Jetson AGX Xavier have a different boot flow that includes the following stages:

1. BootROM
2. Bootloader Components (including Common Driver Framework and Microboot1)
3. TegraBoot (including TegraBoot-BPMP and TegraBoot-CPU)
4. UEFI

It’s possible that the issue is specific to the Jetson AGX Orin device or the JetPack version you are using. You may want to try updating to a newer version of JetPack or seeking further assistance from the NVIDIA support team.

In summary, to resolve the issue, you can try the following:

1. Attach the USB device to WSL and reinstall JetPack using the SDK manager.
2. Check the partition configuration files and boot flow to ensure that they are correct.
3. Try to boot the device in recovery mode.
4. Use the Register Trace Buffers (RTB) feature to debug the issue.
5. Update to a newer version of JetPack or seek further assistance from the NVIDIA support team.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

[dongbox]

Could you please provide the SDK Manager log files located at:
C:\ProgramData\NVIDIA Corporation\SDK Manager?

In the meantime, please try the following on your host machine:

• Reboot the system.

• Open NVIDIA SDK Manager.

• Uninstall all previously installed SDK components.

• Run the installation process again.

Let me know if you still encounter the issue and share the logs so further analysis can be done.

[cmckenna]

Is this the log your looking for?

I’ll try a reboot and try an install on a ‘fresh’ windows machine that doesn’t already have WSL on it.

sdkm-2026-01-13-16-23-04.log (176.8 KB)

[cmckenna]

No luck on reboot. I tried on a ‘fresh’ machine and got passed that problem, but got a message that said,

“The target is in a bad state.”

I tried power cycling as suggested with no luck. Logs are attached below.

JetsonLog.txt (7.5 KB)

[cmckenna]

I’m still looking for solutions for both:

• How to fix the “WSL instance pre setup failed: Bind port failed.” on my main computer.
• If there is anything I can do about the “bad state” problem,

Thanks,

Chris

[dongbox]

Hi,

We have reviewed the logs.

For the first one, it seems like Bind issue may related to CsDeviceControl that is on your host device conflicts the usbipd. We will need further investigation.

The second “bad state” problem, please follow the instructions in SDK Manager to manually power cycle the device, change use port, etc. It may take serveral tries.

If it’s still not working, you may need to try to flash it with an Ubuntu Host or use some other flashing methods. Or consider if it’s a hardware issue.