I am using visual studio code. This was all working on Friday in terms of connection to the development board. But this morning I was adding some additional commands to the torizon extension, but now I can’t connect to the board. I backed out the changes I made, but still wouldn’t connect. So, I started a new makefile project. And the problem continues. I can ssh into the board just fine, I can open the terminal window in VScode just fine. I’ve restarted docker, and the dev board as well as VScode, but nothing seems to help.
Here is the output:
[02-06 17:32:04.242] Initializing Torizon Extension
[02-06 17:32:04.255] Checking system setup…
[02-06 17:32:04.256] Checking Moses …
[02-06 17:32:04.303] Starting backend local instance running on port 5001
[02-06 17:32:11.463] Torizon Backend version 1.0.0 API version: 1.1.7
[02-06 17:32:11.464] Torizon IDE backend started
[02-06 17:32:11.464] Checking Docker …
[02-06 17:32:11.488] Docker version 20.10.22 build 42c8b31
[02-06 17:32:11.532] Trying connect to Toradex Verdin iMX8M Plus WB on Verdin Development Board(14762705)
[02-06 17:32:12.193] Active configuration has been selected 844dec2f-62f4-497b-aac6-531fcc30a3ec, updating it.
[02-06 17:32:12.194] Initializing Torizon C/C++ application.
[02-06 17:32:12.500] SDK-related features are enabled for this project.
[02-06 17:32:12.520] Torizon: debian arm64v8 bullseye - Gimbal - 844dec2f-62f4-497b-aac6-531fcc30a3ec
[02-06 17:32:12.521] Torizon Extension Initialized
[02-06 17:32:12.548] LA_OPT_NXP_Software_License v5 January 2019 EULA accepted
[02-06 17:36:06.508] Toradex Verdin iMX8M Plus WB on Verdin Development Board(14762705) not reached
[02-06 17:36:06.509] Unreachable devices:
Toradex Verdin iMX8M Plus WB on Verdin Development Board(14762705)
Make sure the devices are turned on and connected to the network.
I get this in the terminal:
NFO:root:REST → /api/devices/14762705/images
INFO:root:SSH - Creating tunnel to 14762705
2023-03-06 17:34:55,145| ERROR | Could not open connection to gateway
ERROR:sshtunnel.SSHTunnelForwarder:Could not open connection to gateway
ERROR:root:Error: 539 SSH tunnel error. SSH tunnel error: Could not establish session to SSH gateway
ERROR:root:Exception: SSH tunnel error: Could not establish session to SSH gateway
ERROR:root:Could not establish session to SSH gateway
INFO:root:REST ← /api/devices/14762705/images - 539
Nothing was touched over the weekend.
Any help would be appreciated.
I am running on a Dell Windows 10 host machine. I have a version 1.1A of the Toradex iMx8m Plus on a Verdin dev board. I just downloaded and installed things last week, so I believe I’m using the latest version of the extension as well as VSCode. I upgraded my Docker to see if that might make any difference, but it doesn’t. I can connect via ssh to the board with no issues.
id 14762705 (isn’t this supposed to be the serial number? If not, where does this number come from?)
name: Toradex Verdin iMX8M Plus WB on Verdin Development Board(14762705)
model 0058
Kernel Version #1-TorizonCore SMP PREEMPT Fri Feb 17 12:53:14 UTC 2023
kernelrelease 5.15.77-6.2.0-devel+git.5ee7b429cf75
distroVersion TorizonCore 6.2.0-devel-20230223+build.190 (kirkstone)
Modeldescription Verdin iMX8M Plus Quad 4GB WB IT
I don’t have any other Toradex SoMs to test connections on.
I don’t know if this matters, but sometimes I’ve seen authentication failed. I actually got a your “password” has expired, change your password immediately! (this is for user torizon) I don’t see where in the torizon extension where I can set the password if I change it.
I have created a new project using torizon create and a makefile project. It creates all the things locally, but can’t connect to the dev board. It compiles the files and for the install I see the “deploy” task with a checkmark, but I get the error window showing up saying could not establish an ssh connection to the board.
Here is the terminal output:
Executing task: make
make: ‘Gimbal3’ is up to date.
Terminal will be reused by tasks, press any key to close it.
Executing task: make WORKDIR=/workspaces/Gimbal3/appconfig_0/work/Gimbal3 install
That’s strange. The extension team suggested reinstalling the extension or installing the early access version of the extension. Can you try it and see if it makes any difference?
I think I know what is going on. I uninstalled the extension and reinstalled it. But this time I just tried to detect the device. I put in the username torizon and password torizon but now I am seeing password is required for C:\Users(me)/.ssh(id_key_filename).
I had to do this for our internal security, but it’s only for git ssh. For some reason it is triggering that mechanism and wanting my .ssh public key password. It doesn’t appear that I have a way to enter that. Is there a way around this? Maybe the options you are using to create the tunnel?
It would be helpful it you could provide me with the exact options that are being used to create the tunnel connection.
I managed to do a work around. I had to disable the system from using my 25519 key system (by renaming my .ssh folder) and then everything went back to normal. I don’t know why it started trying to use that when the tunneling was taking place, but that is the work around. If there is a way to provide the options you use in the code, maybe there is a default way to have it not use that “feature” of ssh when creating a tunnel. Otherwise you’d have to put a way for the user to put in a password to connect in your process. I was only using that when I access our git repository.
@lucas_a.tx
I am having trouble again not being able to connect using the tunnel, but this time it isn’t the .ssh mechanism. I had to reload the Torizon version I was using, but Version 6.2 gave me the same issue as not being able to log in, and when I went back to 5.72 build 20, it doesn’t boot all the way.
I am completely stuck. I tried to find an earlier version of the Toradex build with containers, but the version I had was built in December I think, and when I looked for it, the last build was in June, so I’m pretty sure that’s not it.
I have tried both the latest 5.xx and 6.1x versions with no luck.
6.1 seems to have this error: The terminal process "tail’ --port: 5001 terminated with exit code 1, but I think this is just because it can’t connect.
