Torizon IDE Extension 3.4.0 doesn't connect to device

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I’d be glad to help with your Torizon IDE Extension connection issue! To provide the most accurate guidance, could you let me know:

  1. Which OS and version are you running on your device? (e.g., Torizon OS 6.8.2, Torizon OS 7.2.0-build.13)
  2. What hardware are you using? (e.g., Verdin i.MX8M Plus, Verdin AM62, Apalis i.MX8QP, Colibri i.MX8X)

You can get this information by running the tdx-info command on your device. For more details on this command, see: Getting Device Information with Tdx-Info | Toradex Developer Center

Common Troubleshooting Steps

While waiting for your platform details, here are some general troubleshooting steps based on the documentation:

Port Forwarding Check

Ensure the following ports are accessible between your machine and the development board(1):

  • 22 (Dev Board SSH Connection)
  • 2375 (Docker API)
  • 5002 (Local Docker Registry)
  • 2222 (Container SSH Connection)

Device Connectivity

Try executing this command in a terminal to verify basic connectivity(1):

$ ping -W 1 -c 1 <ip-address>

If you get “ping: socket: Operation not permitted”, set the capability with(1):

$ sudo setcap cap_net_raw+ep /bin/ping

VS Code Internal Logs

Check the internal VS Code logs to identify the root cause(1):

  1. Open the VS Code command palette
  2. Select Developer: Toggle Developer Tools
  3. Click on the Console tab and check the logs

WSL-Specific Issues

Since you mentioned WSL, ensure you’re launching VS Code from a WSL terminal using code . and verify the bottom left corner shows the WSL distribution name(2).

Once you provide the platform information, I can give you more specific guidance for your setup.

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.