Problem after Update Torizon IDE Extension Version 3.2.0

Technical Support
, ,
1

Hello,
after Update IDE to new Version, I can not debug anymore. (WSL, VSCODE, IMX8)

Task “validate-arch-arm64” failed:

Terminal:

Executing task: bash -c [[ "arm64" == "aarch64" ]] && true || false 


 *  The terminal process "bash '-c', '[[ "arm64" == "aarch64" ]] && true || false'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

Console:

WARNING :: The default device architecture is arm64 but you are trying to deploy for arm64

Before updating, I removed my device, after update I did a fresh connect. Debugger is set to ARM64.

I had to downgrade to IDE Version 3.1.1. Hope this helps to fix problems with the update.

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.

Architecture Validation Error After IDE Update

The error you’re encountering appears to be related to architecture validation in the updated Torizon IDE Extension. The task validate-arch-arm64 is failing because it’s comparing “arm64” with “aarch64”, which are different naming conventions for the same ARM 64-bit architecture.

Troubleshooting Steps

  1. Verify Debug Configuration
    When debugging, ensure you select the correct architecture option that matches your target device (1):

    • Torizon ARMv8 for ARM 64-bit devices (iMX8)
    • Torizon ARMv7 for ARM 32-bit devices

  2. Check Device Connection Settings
    Since you’ve already reconnected your device, verify that the device architecture is properly detected in your VS Code settings. The architecture should be consistently recognized throughout the debugging process (1).

  3. Launch Configuration Review
    Check your .vscode/launch.json file to ensure the debug configuration matches your target architecture. The configuration should specify the correct architecture for your iMX8 device (2).

Architecture Selection in Debug Sessions

The debugging process requires selecting the appropriate architecture option before starting (1). For your iMX8 device, you should use the Torizon ARMv8 option, which corresponds to ARM 64-bit architecture.

Known Issues with IDE Updates

Based on community reports, IDE updates can sometimes cause architecture validation issues (3) (4) (5). The fact that downgrading to IDE version 3.1.1 resolved your issue suggests this may be a regression in the newer version.

Recommended Actions

  1. Ensure your project’s debug configuration explicitly targets ARM64/ARMv8
  2. Verify that your device connection settings are correct after the fresh connection
  3. If the issue persists with the latest IDE version, consider staying with version 3.1.1 until the architecture validation issue is resolved

The architecture mismatch between “arm64” and “aarch64” terminology appears to be the root cause of the validation failure in the updated IDE extension.

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.

3

Hello,

I can confirm the issue reported by @Lars.ceta. I think that Torizon IDE extension now uses “arm64” instead of “aarch64” in its settings. The latest Torizon IDE extension templates are likely already updated to reflect this change (at least the CMake console template is, based on my tests). You can use the try-update-template Torizon IDE VS Code task to apply the update. I hope it helps.

@toradex I’d also like to point out that, in the case of the CMake console template (I haven’t checked the others), the new script spin-up-down-registry.xsh
(https://github.com/torizon/vscode-torizon-templates/blob/bookworm-7/scripts/spin-up-down-registry.xsh) is not added by the updater script. I had to include it manually.

Furthermore, since updating to Torizon IDE Extension v3.2.0, I’m seeing some errors in the terminal when opening the workspace:

Executing task in folder Myproject: /home/user/.local/bin/xonsh /home/user/path/to/Myproject/.conf/run-container-if-not-exists.xsh --container-runtime docker --run-arguments “-d -p 5002:5000 --restart=always registry:2” --container-name registry

The terminal process failed to launch: Cannot launch a terminal process in an untrusted workspace with cwd /home/user/path/to/Myproject and userHome \home\user.
Container Runtime: docker
Run Arguments: -d -p 5002:5000 --restart=always registry:2
Container Name: registry
Container registry already created
Checking if container registry is running…
Container registry is already running.

And similar issues for:

  • run-torizon-binfmt task
  • run-share-wsl-port task

Is this some left-over task after extension update?

PS: My project is trusted by VS Code and all tasks seem to work just fine when launched manually.

4

Updating to Torizon IDE 3.2.3 solved my problems. Thanks.

1 Like
5

Now there is another issue.
The docker daemon.json on the device is not updated with a new docker host ip-address (“insecure-registries”), if I change the network.
I did a fresh “remove-device”, “connect-device”, “set-default”, but the ip is not updated.