Docker info Architecture in the vscode terminal

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Based on the context provided, it seems that the issue with sourcing the tcb-env-setup.sh script in the VS Code terminal when connected via SSH to the Ubuntu host is likely due to misconfigurations in the terminal setup or the activation of the Torizon IDE extension. Here are some steps you can take to resolve the issue:

  1. Check Terminal Settings: Ensure that the VS Code terminal is configured to use the correct shell. You may need to adjust the terminal profile settings in VS Code to ensure that it sources the tcb-env-setup.sh script upon startup.

  2. Activate Torizon IDE Extension in Workspace: Since the Torizon IDE extension is not activated in the current workspace, activate it to ensure that all necessary tools and configurations are available. This might help in setting up the environment correctly.

  3. Manual Sourcing: As a temporary workaround, manually source the tcb-env-setup.sh script in the terminal after connecting via SSH by executing the command source ~/Toradex/tcb/tcb-env-setup.sh. This should help in setting up the environment for the current session.

  4. Verify SSH Configuration: Check the SSH connection settings to ensure that the terminal environment is correctly loading the necessary scripts and configurations. This might involve checking any SSH configuration files or settings that could affect the terminal environment.

By following these recommendations, you should be able to resolve the issue and ensure that the TorizonCore Builder environment is set up correctly in your VS Code terminal.

Please, also check if these links can help you solve your problem:

Cannot run and debug C code in VS Code to my iMX6.