AnsweredAssumed Answered

Run/Debug problem in SW4STM32 using ST-Link/V2 SWD

Question asked by mostafanfs on Oct 31, 2015
Latest reply on Feb 6, 2016 by toss.piotr
I've just started using SW4STM32 and wrote a sample project to check it out but after setting up my board and its connection and a Run/Debug configuration I got this error when I want to deploy my program using ST-Link/V2 SWD:

Open On-Chip Debugger 0.9.0-dev-00415-g2d4ae3f-dirty (2015-06-12-17:54) 
Licensed under GNU GPL v2 
For bug reports, read 
http://openocd.org/doc/doxygen/bugs.html 
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD 
adapter speed: 1000 kHz 
adapter_nsrst_delay: 100 
none separate 
srst_only separate srst_nogate srst_open_drain connect_deassert_srst 
Info : Unable to match requested speed 1000 kHz, using 950 kHz 
Info : Unable to match requested speed 1000 kHz, using 950 kHz 
Info : clock speed 950 kHz 
Info : STLINK v2 JTAG v23 API v2 SWIM v4 VID 0x0483 PID 0x3748 
Info : using stlink api v2 
Info : Target voltage: 3.261335 
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints 
Error: timed out while waiting for target halted 
TARGET: stm32f1x.cpu - Not halted 
in procedure 'program' 
in procedure 'reset' called at file "embedded:startup.tcl", line 478 
in procedure 'ocd_bouncer'

Unable to reset target **
shutdown command invoked

Isn't this supposed to work without problems?

I can program and debug the chip using every other tools I have on my computer like Keil, Atollic TrueSTUDIO and STM32 ST-LINK Utility pretty easy and I wasn't expecting any problems at this stage!
ST-LINK has the latest firmware and I have installed the latest ST-LINK USB driver so I sort of blame SW4STM32 or maybe STM32CubeMX because the project was created using STM32CubeMX.
Any thoughts?

Outcomes