3.2.0 Updated...now issues with device connection, etc

Technical Support
,
2

Hi, I’m the Toradex AI Assistant.

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

Torizon IDE Extension Device Detection Issues

Based on your startup log and the issues you’re experiencing, there are several potential causes for the extension not detecting your Toradex devices after the update to version 3.2.106.

Troubleshooting Steps

1. Check Auto-Scan Settings

The extension has an auto-scan feature that can be disabled(1). Verify that automatic scanning is enabled:

  • Open VS Code settings and search for torizon.autoScan(1)
  • Ensure this boolean setting is set to true(1) (this is the default)
  • If set to false, the extension won’t automatically scan for devices when opening workspace folders(1)

2. Manual Device Addition

If automatic scanning isn’t working, you can manually add devices(2):

  • Click the Torizon icon in the left menu bar(2)
  • Click the + icon to manually add devices(2)
  • Input your device’s IP address(2)

3. Network and Port Requirements

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

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

4. Host IP Configuration Issues

Similar to the community reports, there may be an issue with host IP detection(4). Try setting the host IP manually:

  • Open VS Code global settings
  • Search for torizon.overwriteHostIp(1)
  • Set it explicitly to your host machine’s IP address(1)
  • This setting overwrites the automatically detected IP address and can resolve issues when the automatic detection gets the wrong interface(1)

5. Check Internal VS Code Logs

To get more detailed information about what’s happening during startup(3):

  1. Open the VS Code command palette and select Developer: Toggle Developer Tools(3)
  2. Click on the Console tab and check the logs(3)
  3. Look for any error messages related to device scanning or network detection

6. Verify Network Connectivity

Test basic connectivity to your device:

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

If this fails with “Operation not permitted”, you may need to set ping capabilities(3):

sudo setcap cap_net_raw+ep /bin/ping

Extension Configuration

Your startup log shows the extension is using the dev branch for templates, which may indicate you’re using experimental features(1). Consider checking if the torizon.experimental setting is affecting device detection(1).

The missing port forwarding you mentioned could be related to the local Docker registry not starting properly, which would affect device communication.

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.