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 Send TopicPrint
Normal Topic VS2017 STM32 "Unable to start debugging... " (Read 1778 times)
Indrid kold
Junior Member
**
Offline


Posts: 18
Joined: May 15th, 2017
VS2017 STM32 "Unable to start debugging... "
Aug 9th, 2019 at 4:21pm
Print Post  
I'm working to get GDB working with an STM32F103C8 board. I can successfully program the board using an STLinkV2. My vMicro version is 1908.5.1. STLink upgraded to latest via STCubeProgrammer. When I attempt to start debug a dialog stating "...Unable to establish a link to GDB..." appears. Build text is attached, thanks for any assistance.
  

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


Posts: 12071
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VS2017 STM32 "Unable to start debugging... "
Reply #1 - Aug 10th, 2019 at 10:14am
Print Post  
Thanks for the info. Can you also please see if there are any .log files in 

Code
Select All
cSTM32F103C\Debug 

  
Back to top
WWW  
IP Logged
 
Indrid kold
Junior Member
**
Offline


Posts: 18
Joined: May 15th, 2017
Re: VS2017 STM32 "Unable to start debugging... "
Reply #2 - Aug 12th, 2019 at 1:32pm
Print Post  
Good morning and thanks for your response. The .log file is attached.
  

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


Posts: 2145
Joined: Feb 13th, 2019
Re: VS2017 STM32 "Unable to start debugging... "
Reply #3 - Aug 12th, 2019 at 7:08pm
Print Post  
Testing on my setup it currently reports as below in the output when its all connected correctly, but fails as yours does when either my USB Lead is bad, or when the VID/PID being searched for is incorrect (they normally prompt more clearly about this).

Code
Select All
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748 


A few more questions:-

1) Can you confirm what the source / instructions to update the STLink if possible?

2) Would you be able to confirm the successful upload was using the "STLinkv2 + OpenOCD (VMicro)" Menu option? 

3) If (2) = YES - does it still works since updating the STLink? (please attach output if this works)

4) Finally, what does it report as in Device Manager > USB devices > STM32 STLink > Details > Hardware IDsĀ  (something like USB\VID_0483&PID_3748)
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint