Hi,

Yes, you should be able to get it working by running OpenOCD on the customer’s machine and setting up TCP port forwarding so that you can connect to it from your lab.

You would need to find out the following parameters used in a regular debug session and replicate them manually with a 2-machine setup:

1. The OpenOCD command line. You can find it in the OpenOCD window in Visual Studio (or in the connection testing window when you press the “Test” button in the VisualGDB Project Properties).
2. The GDB command line. Is is typically gdb –interpreter mi $(TargetPath).
3. The startup gdb commands involved in a regular session (e.g. target remote host:port, load, etc). You can find them out by switching the GDB Session window to “All GDB Interaction” mode.

Once you find out those parameters and can successfully launch OpenOCD remotely, you can use the Debug Settings page of VisualGDB Project Properties to switch the debug method to the “Custom” mode. This will allow entering the gdb command line and startup commands manually, so you can connect to the remote OpenOCD instance.

We would also advise trying to manually launch OpenOCD locally and connect to it using the custom mode first. This should help decouple the manual setup problems from potential network problems.