Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 [2]  Send TopicPrint
Very Hot Topic (More than 25 Replies) Unexpected GDB output from "-exec-run" (Read 3624 times)
romeo
Junior Member
**
Offline


Posts: 48
Joined: Aug 3rd, 2024
Re: Unexpected GDB output from "-exec-run"
Reply #20 - May 6th, 2026 at 1:56pm
Print Post  
Simon,
Here is the output of the fuse list you asked for.

Roman
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: Unexpected GDB output from "-exec-run"
Reply #21 - May 6th, 2026 at 2:11pm
Print Post  
Thanks Roman, that all looks correct for the default settings and USB Debugging.

Can you try putting the board into download mode manually and then connecting the debugger (or running the command we had in notepad on your PC)?

ie.
1) Hold BOOT
2) Tap RESET
3) Release BOOT
4) Check Task Manager shows no openocd.exe programs running, and no xtensa-esp32s3-elf-gdb.exe programs running on the Details Tab (kill if they are by pressing delete when highlighted).
4) Try the command via CMD or try again in Visual Studio
  
Back to top
IP Logged
 
romeo
Junior Member
**
Offline


Posts: 48
Joined: Aug 3rd, 2024
Re: Unexpected GDB output from "-exec-run"
Reply #22 - May 7th, 2026 at 2:10am
Print Post  
I did the BOOT/RESET thing. The flasher stops running at this point. There were no openocd tasks running, or any xtensa tasks but I don't see a "Details" tab on Task Manager. I also checked Zadig.

I then opened VS (unfortunately I lost the Notepad entry when I cleaned up after your session) and the blinker .sln, and did "Attach..". A couple of xtensa tasks then started (I had a Task Manager search window open), but after a couple of seconds, the same GDB error. When I closed the error, the xtensa tasks disappeared.
Just for fun I restarted the blinker and tried again - same result.

I also tried a second identical module (same batch, same supplier). Same result.

And here I sat assuming that I had just made some simple rookie error! Frustrating!
  
Back to top
 
IP Logged
 
romeo
Junior Member
**
Offline


Posts: 48
Joined: Aug 3rd, 2024
Re: Unexpected GDB output from "-exec-run"
Reply #23 - May 8th, 2026 at 8:49am
Print Post  
Simon,
Have you had any more thoughts? 
I installed VS2026 yesterday just to test the water; is VMicro debugger likely to behave differently in that environment?
Is that worth trying?
(Obviously, I don't have VMicro installed on VS2026).
Roman
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: Unexpected GDB output from "-exec-run"
Reply #24 - May 8th, 2026 at 8:59am
Print Post  
VS2026 will behave in the same way to my knowledge as this is failing at the bottom of the stack of software as it failed in the command line on your machine.

Could you run the attached driver script, and post or email back the output it generates (see the *Instructions.txt file for how to run the script)?

If you have another PC you could try on this would be useful as I suspect it is stale driver related currently as everything else seems correct.
  

Please Register or Login to the Forum to see File Attachments
Back to top
IP Logged
 
romeo
Junior Member
**
Offline


Posts: 48
Joined: Aug 3rd, 2024
Re: Unexpected GDB output from "-exec-run"
Reply #25 - May 8th, 2026 at 10:55am
Print Post  
I have the output but cannot see where is there an "Attach File" on this reply screen ;-(
I'll send it by email.
(Posting this here simply to maintain continuity on the forum)

Was I supposed to have had the ESP board plugged into its USB socket when I ran this? It wasn't!
« Last Edit: May 8th, 2026 at 10:59am by romeo »  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: Unexpected GDB output from "-exec-run"
Reply #26 - May 12th, 2026 at 12:21pm
Print Post  
Just to summarise the findings after a lot of exchanges and investigation via Email:-

What was Wrong?
The default driver installed by Windows for the "USB JTAG/Serial Debug Unit (Interface 2)" on the ESP32S3 is a Microsoft v10.x WinUSB Driver.  This appears to not work with the OpenOCD debugging tools, and needs to be replaced with the correct v6.x version using Zadig.

Further Findings
The Adapter Speed is not taking effect in the debugging pattern as it is overridden by the ESP32S3.cfg file.  This will be fixed in the next release.

Documentation Updates
The below pages have been updated to clarify the Zadig Driver Installation IS required, and to amend the board.txt overrides to resolve the adapter speed in the interim for the S3:
GDB and ESP32S3 via USB
GDB and ESP32C3 via USB
GDB and ESP32C6 via USB
GDB and ESP32H2 via USB

The below page has been updated to highlight the Windows USB Driver Issue:
Zadig Driver Installation Guide
  
Back to top
IP Logged
 
romeo
Junior Member
**
Offline


Posts: 48
Joined: Aug 3rd, 2024
Re: Unexpected GDB output from "-exec-run"
Reply #27 - May 12th, 2026 at 11:51pm
Print Post  
I would like to express my thanks to Simon for the effort he put into solving this issue. I have always found the level of support from Simon to be nothing short of amazing!
Roman
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1 [2] 
Send TopicPrint