Loading...
 
Skip to main content

System Workbench for STM32


Workbench can't find stm32 board

Working with an stm32f469-discovery board and have not had any problems flashing it until yesterday. When I plug it in I get the window with the mbed.html file and the chirrup to tell me that it's been found by USB. However, when I try and Target->Program Chip I get:

16:00:12 **** Programming project passwd-469 on chip ****
"C:\\Ac6\\SystemWorkbench\\plugins\\fr.ac6.mcu.externaltools.openocd.win32_1.16.0.201708311556\\tools\\openocd\\bin\\openocd.exe" -f stm32.flash.3620796084820090593.cfg -s "D:\\passwd-469" -s "C:\\Ac6\\SystemWorkbench\\plugins\\fr.ac6.mcu.debug_2.1.1.201708311556\\resources\\openocd\\st_scripts" -c "program Debug/passwd-469.elf verify exit"
Open On-Chip Debugger 0.10.0-dev-00004-gcef2a8c-dirty (2017-08-31-14:07)
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: 1800 kHz
adapter_nsrst_delay: 100
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v28 API v2 M v18 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.235394
Error: init mode failed (unable to connect to the target)
in procedure 'program'
in procedure 'init' called at file "embedded:startup.tcl", line 473
in procedure 'ocd_bouncer'

    • OpenOCD init failed **

shutdown command invoked


16:00:12 Build Finished (took 676ms)

I've reinstalled the workbench and the stlink drivers/USB and double checked the jumper settings.

Anyone had anything similar and found a solution to this?

Small update:

if I take the command line and run it in a cmd session useing my own .cfg file I am able to program the chip.

Further update: after running from the command line the workbench option now works!