[gboy]

Interesting.  Thanks for the clarification!

[gboy]

Note to the community:  I am able to achieve my objective by putting my system commands into a batch file (e.g. my_bat.bat) placed in the $(BuildDir) and then calling it as a pre build command using the command:

.\my_bat.bat

 

[gboy]

I tried to implement ‘Before building’ custom build step using the following command setup:

However, when I went to build the project, I got this set of messages:

Run "del /F my_file.c.obj " in directory "C:/my_proj/build/VisualGDB/Debug/CMakeFiles/my_proj.dir" on local computer 

Command-line action failed

Do you know why this command to delete one of the object files is not succeeding?

Attachments:

You must be logged in to view attached files.

[gboy]

Thanks for the tip.  Where exactly are pre-build steps like that added in VisualGDB?  (and what’s the format of the command to regenerate such a header file?)

 

[gboy]

Thanks @support.  I was able to fix my issue.  Turns out I had to set ‘Debug’ to ‘Serial Wire’ in the SYS tab of the CubeMX interface.  This properly assigns the PA13 & PA14 pins to the TMS and TCK signals necessary for debugging with the ST-Link / V2 adapter.

I can now step through my code in Visual Studio.

Thanks again.

[gboy]

Ok – what is the later/more effective version:  VisualGDB-5.2r9-trial.msi or VisualGDB-5.3.7.1769.msi?  I’m guessing the latter?

Thank you.

[Author]

Posts