Posted by mahmudzero on 2017-11-06 01:22

Well that changed some stuff for me. Now I’m getting the following:

Open On-Chip Debugger 0.10.0-dev-00005-g4030e1c-dirty (2017-10-24-07:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 950 kHz
adapter_nsrst_delay: 100
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.261782
Info : Stlink adapter speed set to 950 kHz
Info : STM32F030R8Tx.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : Stlink adapter speed set to 950 kHz
adapter speed: 950 kHz
STM32F030R8Tx.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
in procedure ‘program’
in procedure ‘reset’ called at file “embedded:startup.tcl”, line 478
in procedure ‘ocd_bouncer’
in procedure ‘ocd_process_reset’
in procedure ‘ocd_process_reset_inner’ called at file “embedded:startup.tcl”, line 248
in procedure ‘STM32F030R8Tx.cpu’ called at file “embedded:startup.tcl”, line 370
in procedure ‘ocd_bouncer’

• Programming Started **

auto erase enabled
Error: Cannot identify target as a stm32x
Error: auto_probe failed

• Programming Failed **

shutdown command invoked