I am able to program my ESP32S3 through an external JTAG (ESP-Prog) in command line. And I can program it in Visual Studio if I run OpenOCD separately concurrently in command line, but VS cannot tund OpenOCD on its own (I would like to also debug). Looks like VS is not using the proper .cfg file. How can I specify what should it be? When I press F1 and enter OpenOCD Tools options "Choose CFG" and "Choose SVG" end up with a message:
"The "path" argument must be of type string or an instance of Buffer or URL. Received undefined"
Specifying the correct .CFG file for Visual Studio Code
Re: Specifying the correct .CFG file for Visual Studio Code
Ah ok I see that we have also internal command line terminal in VS. Just with Powershell. Thanks to this youtuber: https://www.youtube.com/watch?v=uq93H7T7cOQ. Power of the video media.
But still there is a problem with error:
Esp Unable to start debugging. Unexpected GDB output from command "-interpreter-exec console "target remote 127.0.0.1:3333"". Remote connection closed
But still there is a problem with error:
Esp Unable to start debugging. Unexpected GDB output from command "-interpreter-exec console "target remote 127.0.0.1:3333"". Remote connection closed
Re: Specifying the correct .CFG file for Visual Studio Code
Ah ok after the weekend this somehow resolved itself..
Who is online
Users browsing this forum: No registered users and 29 guests