[peted]

Hi just to follow up, the firewall issue was not related to VisualGDB.  For some reason adding the inbound rules did not work for me, so I disabled the firewall for public access on the WSL vEthernet only and then it works.  So now I can easily set the necessary toolchain files on WSL2, but still have the other issues I reported.

[peted]

Hi

Thanks for the reply.  I have attempted to do as you suggest, but I have hit a few issues.

First, VisualGDB hangs trying to access the filesystem on the WSL2 machine unless I disable my windows defender firewall (both private and public networks).  I have applied the firewall rule from https://visualgdb.com/documentation/wsl2/ ok.  It is strange because if I select the WSL2 distro then VisualGDB can list toolchains there (e.g it finds an install of GCC) but if I select to choose my own toolchain it hangs because of the firewall issue.
– Is there a log file so I can see exactly how visualGDB is trying to access WSL2, e.g which TCP ports to allow?

Secondly, the test of the toolchain fails which is kind of expected.  Is there any way to instruct VisualGDB not to run the checks after you select a toolchain and click “next” in the wizard?

Thirdly, what I want to do is to build on WSL2 but deploy to windows 10, i.e locally where visual studio is running.  I will then run gdb locally on windows 10 along with openocd in order to debug on HW (some of the ISA won’t be supported but it should still allow downloading of applications).
If I choose separate build & deploy machines, VisualGDB seems to want me to choose some Linux machine – I cannot seem to choose the local windows 10 machine.
Is this possible with VisualGDB (with the non-custom version of the product), or is there something I am missing?

Thanks
Pete

[Author]

Posts