I use ApolloX extension with my Verdin iMX8M-Plus SoM under WSL.
After I connected to my SoM (manually added), I noticed that when I click on Set Default
the file .vscode/settings.json is modified automatically.
As far as I understand this is “by design”, so that settings.json is filled with the info of the “default” device.
But I noticed that the following two fields are misconfigured (i.e., they’re changed to wrong values, and I must change them back):
host_ip is set to the first network interface, and so I need to chage it back (as described in this workaround). Maybe the next release of the extension (2.1.0) will fix this.
Moreover, is it possible that “Set Default” changes the content of /etc/docker/daemon.json on the SoM?
I see that it contains
{
"insecure-registries" : ["10.1.2.50:5002"]
}
and th ip is those of the first network interface of my PC. And so I need to change it to the proper one, followed by sudo systemctl restart docker
torizon_gpu is set to an empty string, but for my Plus module I need "-vivante"
Regarding the first point, yes this seems related to ApolloX not correctly handling setups with multiple network interfaces as you have seen.
Moreover, is it possible that “Set Default” changes the content of /etc/docker/daemon.json on the SoM?
I believe so, this is so the device knows which registry IP to pull containers from. In general this is a known issue by our team and they’re working on possible fixes and improvements to this behavior.
Now about your second point regarding torizon_gpu. I believe I saw you discuss this on another thread as well. Though it’s strange this field doesn’t auto-fill for you since it does for us. What version of ApolloX is this exactly? Maybe this behavior is bugged on a certain version.
What version of ApolloX is this exactly? Maybe this behavior is bugged on a certain version.
It’s the pre-release version 2.0.7 used in WSL.
I know that I could find bugs in a pre-release; I’m not complaining about this.
I’ve been testing to help to develop a better extension.
As a test I tried the following on the same pre-release version:
Create new project
Add my Verdin i.MX8M Plus SoM to ApolloX
Click “Set Default” for this device
After doing this torizon_gpu in .vscode/settings.json was automatically updated with "-vivante". It seems like this automatically fills correctly, I’m still not sure why it doesn’t get set properly in your case.
Edit: Actually wait maybe the issue is that you have multiple network interfaces. Since ApolloX doesn’t default to the right network interface which has your device it can’t connect to the module initially and determine what value should be filled in torizon_gpu.
Just to chime in, we have the same issues regarding the different networks, and I think I also raised that point some time ago. I guess this is sadly the standard in most company networks. VPN, multiple devices, …
