Difference between revisions of "Zynthian Webconf debug with Visual Studio Code (VSC)"
| Line 52: | Line 52: | ||
[[File:Vsc-remote explorer password.png|thumb|center|800px]] | [[File:Vsc-remote explorer password.png|thumb|center|800px]] | ||
| − | Once VSC has established a connection, it will download the appropriate python components to the zynthian to allow debugging to take place remotely. | + | Once VSC has established a connection, it will download the appropriate python components to the zynthian to allow debugging to take place remotely. This make take some time and als o may complain about missing components, giv it some time it will get here if it possibly can.... |
[[File:Vsc setting up remote server.png|thumb|center|800px]] | [[File:Vsc setting up remote server.png|thumb|center|800px]] | ||
[[File:Vsc connected.png|thumb|center|800px]] | [[File:Vsc connected.png|thumb|center|800px]] | ||
| + | |||
| + | and as you can see the zynthian-orig.local machine is recognised by visual studio code. | ||
[[File:Vsc remote explorer connect to host.png|thumb|center|800px]] | [[File:Vsc remote explorer connect to host.png|thumb|center|800px]] | ||
Revision as of 17:17, 11 January 2022
Debugging Webconf with Visual Studio Code
This is presented as an example of how a Visual Studio Code can be used to examine a component of the zynthian sub system as it runs using the Visual studio Code extensions, python & remote-ssh. These are loaded using the cog dialog at the bottom of the vsc code page.
Once you have these components added you can attempt to log onto an existing Zynthian from your PC, MAC, or linux machine, just so long as it's capable of running Visual Studio Code. In my own case I have it running on a 64 bit Raspbian instance, and I had to build it from source to get it running which is a degree of proof of the overall flexibility of what is after all a Microsoft product!
I also tend to add the git-graph extension.
The ssh connection
The addition of the remote component adds the Remote Explorer element
I already have a couple of remote zynthians in the machine and VSC is pretty tenacious at hanging onto remote instances it knows about. But we will try to add a new machine.
I have a zynthian called zynthian-orig.local. It's actually a genuine zynthian product running a Pi3 and no membrane switches and some fairly simplistic interface. Indeed it has to be disassembled to change the ssd. Such were the early days.!
1 Visual Studio Code Configure.
Firstly we need to add the extensions.
activated by the cog in the bottom left hand corner of the Visual Studio Code interface This will give us a command line that will attempt to log on to the server we are pursuing.. . .
So lets make sure that it is actually running.
To access this we press on the + button against the appropriate machine. ( images a little awry here )
we enter the command we will use to access the remote zynthian which is ssh....
And login using the machines root password.
Once VSC has established a connection, it will download the appropriate python components to the zynthian to allow debugging to take place remotely. This make take some time and als o may complain about missing components, giv it some time it will get here if it possibly can....
and as you can see the zynthian-orig.local machine is recognised by visual studio code.
