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
Hot Topic (More than 8 Replies) Debug using ST LINK V2 (Read 27326 times)
cdia
Newbies
*
Offline


Posts: 3
Joined: Dec 20th, 2016
Re: Debug using ST LINK V2
Reply #20 - Dec 20th, 2016 at 5:48pm
Print Post  
Could You please help me with this. I've tried attaching the project zip but I'm not allowed to do so.

The funny thing is that once the board.txt file is added to project dir, no log will be written in dir BlinkStm32\Debug\logs\gdb\. But it will write logs with no board.txt file added to project.

Thanks.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12076
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Debug using ST LINK V2
Reply #21 - Dec 20th, 2016 at 6:56pm
Print Post  
please attach again thanks
  
Back to top
WWW  
IP Logged
 
cdia
Newbies
*
Offline


Posts: 3
Joined: Dec 20th, 2016
Re: Debug using ST LINK V2
Reply #22 - Dec 21st, 2016 at 5:48am
Print Post  
To summarize what I have done so far:
All files are UTF-8 encoded, Windows EOL carriages

1) I have added file 
...\VisualStudio\...\tools\openocd-0.9.0\scripts\board\stm32f103c8t6mini.cfg
with content from your post in this thread

2) I have added the board.txt file in project dir with content which can be found in attachment

3) I have tried to hard-code all the paths inside board.txt file with no success

4) Without the board.txt file odb creates log file inside Debug dir but with board.txt file it will not create any log

5) I've verified that openocd runs with the created config file:
in a cmd:
Code
Select All
bin\openocd.exe -f scripts\board\stm32f103c8t6mini.cfg 

and device connected

than in another cmd:
Code
Select All
telnet localhost 4444
> reset halt
> flash probe 0
> stm32f1x mass_erase 0
> reset halt
 

and everything went smoothly

I think this should be the short version of attempts I have done so far.

Thanks.
« Last Edit: Dec 21st, 2016 at 8:03am by cdia »  

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


Posts: 12076
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Debug using ST LINK V2
Reply #23 - Jan 6th, 2020 at 11:26am
Print Post  
« Last Edit: Jan 6th, 2020 at 11:27am by Tim@Visual Micro »  
Back to top
WWW  
IP Logged
 
Page Index Toggle Pages: 1 [2] 
Send TopicPrint