2 months ago it went, mosr unfortunately didn't go to programming and so debug either.
I can't program the chip with ST-Link v2, I always get the following messages:


Debugger: STLink v2 (External)
Compiling 'Grill6ServoSTM' for 'Generic STM32F1 series'
Program size: 22,340 bytes (used 34% of a maximum of 65,536 bytes) (160.42 secs)
Minimum Memory Usage: 1000 bytes (5% of a maximum of 20480 bytes)
 
Uploading 'Grill6ServoSTM' to 'Generic STM32F1 series' using 'COM5'
Uploader started for board Generic STM32F1 series
The upload method will be: bootloader
Uploading via Bootloader
C: \ ProgramData \ vmicro \ tools \ openocd-0.10.0.20200213 \ bin \ openocd.exe -d2 -s "C: \ ProgramData \ vmicro \ tools \ openocd-0.10.0.20200213 / scripts /" -f "interface / stlink. cfg "-c CPUTAPID 0x2ba01477 -f" target / stm32f1x.cfg "set -c" echo -n {**** [vMicro] **** Uploading ELF:} "-c" reset_config; telnet_port disabled; program {C: \ Users \ Cnc \ AppData \ Local \ Temp \ VMBuilds \ GRILL6 ~ 1 \ STMICR ~ 1 \ Debug / Grill6ServoSTM.ino.elf} reset; reset_config; shutdown "
The uploader returned an error
Open On-Chip Debugger 0.10.0 + dev-01058-g853a05287 (2020-02-13-16: 41)
Licensed under the GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
Unexpected command line argument: 0x2ba01477


Board.txt :

tools.stlinkv2.server.targetCmd=-c CPUTAPID 0x2ba01477 -f "{tools.openocd.debug.build.openocdscript}" 
tools.stlinkv2.upload.targetCmd=-c CPUTAPID 0x2ba01477 -f "{tools.openocd.upload.openocdscript}"


Do you also need a serial port for programming with ST-Link v2?
What have I done wrong ?

safi

I will also attach the Debug log.

I tried, unfortunately it doesn't work that way.

safi

Thanks for the tip !

I tried it, unfortunately it doesn't work:

safi

Thanks for the update.

Can you enable the options shown at the top of the page, as well as enabling vMicro > Uploader > Verbose.

Then perform a full build, and try attaching the debugger, and attach the full output as a text file.

Please also attach the OpenOCD.log file from the build folder which should reveal more information about the issue (How to Find OpenOCD Log File)