I tried using the C++ template doing a helloworld project. It had issues

Technical Support
, , , ,
6

Issue Analysis

You’re encountering a connection issue during the debug deployment process. The error ssh: connect to host 192.168.6.243 port 2230: Connection refused indicates that the debug container isn’t running or the SSH service isn’t accessible on port 2230.

Key Observations

Looking at your logs, I notice several important details:

  1. Build Process Completed Successfully: The container images were built and pushed successfully to the local registry
  2. Missing Application Build: The log shows make: Nothing to be done for 'debug' - this suggests the application wasn’t compiled
  3. Container Not Running: The SSH connection failure indicates the debug container isn’t started yet

Troubleshooting Steps

Step 1: Verify Debug Container Deployment

The debug process should automatically start the container with SSH access enabled (1). Check if the debug container is running on your target device:

docker ps

Step 2: Check Docker Compose Status

On your target device, verify the container orchestration:

docker compose -p torizon ps

Step 3: Manual Container Start

If the container isn’t running, you can manually start it using the docker-compose.yml file that was copied to your device (2):

docker compose -p torizon up -d helloworldcpp-debug

Step 4: Verify SSH Service

Once the container is running, check if the SSH service is accessible:

docker compose -p torizon logs helloworldcpp-debug

Common Causes and Solutions

Application Build Issue: The make: Nothing to be done for 'debug' suggests your Makefile might not have the correct debug target or the source files weren’t detected properly.

Port Forwarding: The debug container should automatically expose port 2230 for SSH access (1). This is typically configured in the docker-compose.yml file.

Torizon OS 7 Compatibility: Since you’re using TorizonOS 7 with extension version 3.2.5, ensure you’re using compatible templates. The pre-release support for TorizonOS 7 has been migrating from PowerShell to Python/Xonsh scripts (3), which might affect some workflows.

Recommended Actions

  1. Check your Makefile: Ensure it has a proper debug target
  2. Verify project structure: Make sure your source files are in the expected locations
  3. Try a fresh debug session: Stop any existing containers and restart the debug process
  4. Check VS Code extension settings: Ensure you’re using templates compatible with TorizonOS 7

The debug deployment process should automatically handle port forwarding and container startup (1). If the issue persists, try creating a fresh project from the template to isolate whether this is a project-specific issue.

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.