Sysprogs forums › Forums › VisualGDB › esp32 s3 jtag
Tagged: esp32s3 debug
- This topic has 8 replies, 4 voices, and was last updated 1 year, 4 months ago by support.
-
AuthorPosts
-
July 19, 2022 at 01:11 #32832engineering-spiritParticipant
Is there support for the buildin usb JTAG of the esp32-s3 ?
July 19, 2022 at 01:35 #32833engineering-spiritParticipantC:\Users\pvisser\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 64499” -c “telnet_port 64497” -f interface/esp_usb_jtag.cfg -c “adapter_khz 3000” -f target/esp32s3.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2022-05-03)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect ‘jtag’
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
adapter speed: 40000 kHzDEPRECATED! use ‘adapter speed’ not ‘adapter_khz’
adapter speed: 3000 kHzWarn : Transport “jtag” was already selected
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 64497 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: esp_usb_jtag: could not find or open device!Error: No JTAG interface configured yet. Issue ‘init’ command in startup scripts before communicating with targets.
Error: Failed to clear OCDDCR_ENABLEOCD!
Error: No JTAG interface configured yet. Issue ‘init’ command in startup scripts before communicating with targets.
Error: Failed to clear OCDDCR_ENABLEOCD!July 21, 2022 at 04:43 #32852engineering-spiritParticipantso the buildin jtag is not supported?
Or is there a way to use it.I cant vind any option to use it in the debug configuration.
July 21, 2022 at 09:27 #32854supportKeymasterHi,
We have just retested it with the ESP32-S3-BOX and it worked just fine. Please make sure you actually install the WinUSB driver for the “USB Composite device” as VisualGDB suggests (you need to select “USB Devices” in the “Debug Using” field for VisualGDB to check the drivers).
The default driver layout (separate serial port & debug nodes) appears to be incompatible with the current version of OpenOCD.
November 29, 2022 at 21:57 #33478AshvajitPParticipantHi,
I am getting the issue, not able to use debug my ESP32-S3 in custom board. I have already flashed my code in S3, but I am not able to debug using built-in USB debug of ESP32-S3.
I am getting this exception message:
VisualGDB version: 5.6.104.4534
—————— System.Exception ——————
System.Exception: esp_usb_jtag: could not find or open device!
at VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.ThrowTestFailedException()
at VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.TestThreadBody()
trace=[VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.ThrowTestFailedException:56, VisualGDB.Common_GUI.WPF.DebugMethodTestWindow.TestThreadBody:356]Test settings
C:\Users\APRASAD\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 60858” -c “telnet_port 60856” -f interface/esp_usb_jtag.cfg -c “adapter_khz 3000” -f target/esp32s3.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2022-05-03)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect ‘jtag’
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
adapter speed: 40000 kHzDEPRECATED! use ‘adapter speed’ not ‘adapter_khz’
adapter speed: 3000 kHzWarn : Transport “jtag” was already selected
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 60856 for telnet connections
Error: esp_usb_jtag: could not find or open device!Error: No JTAG interface configured yet. Issue ‘init’ command in startup scripts before communicating with targets.
Error: Failed to clear OCDDCR_ENABLEOCD!
Error: No JTAG interface configured yet. Issue ‘init’ command in startup scripts before communicating with targets.
Error: Failed to clear OCDDCR_ENABLEOCD!- This reply was modified 1 year, 11 months ago by AshvajitP. Reason: To add more details
Attachments:
You must be logged in to view attached files.November 29, 2022 at 22:13 #33481supportKeymasterHi,
This is something to check with Espressif, the maintainers of the ESP32 OpenOCD port. All VisualGDB does in this case is launch OpenOCD with the parameters you select.
November 30, 2022 at 02:43 #33485AshvajitPParticipantHi,
I have found the issue and I am able to debug my ESP32-S3 now. It turns out that visual GDB was not able to change the driver of USB device. I had to do it manually using USB Driver Tool and is working now with earlier given commands.
Attachments:
You must be logged in to view attached files.June 30, 2023 at 07:48 #34395orbitcomsParticipantI am also interested how to get the debugging working for the S3.
Can the dual USB version modules be debugged in Visual Studio with Visual gdb? The board works with openocd and flash programming ok in VS Code.
I notice in the “New Espressif sdk project” dialog there is only option to select ESP32C3 built-in jtag. Is this to be selected to set up S3 debugging as attached?
Attachments:
You must be logged in to view attached files.July 3, 2023 at 09:32 #34410supportKeymasterHi,
The built-in debugging interface was originally introduced in ESP32C3, hence VisualGDB calls it “ESP32C3 debug interface”. If it was auto-detected by the USB ID as shown on the screenshot, it should work just fine.
-
AuthorPosts
- You must be logged in to reply to this topic.