Posted by scrungy_doolittle on 2015-03-26 22:53

I went through these steps
Debug As >> Debug Configurations...
Create a Ac6 STM32 Debugging configuration
Choose your project and executable (if needed)

It filled in things for me. and created a debug script.
At the bottom of the debug configuration command, there is a debug button. I really should not have to do this each time, so will need to know how to select this without doing this.

I hit debug and get an error.
‘Lauching project name has encountered a problem.
OpenOCD Script not found.

There is NO use local script radio button.
NOW WHAT?

Select the Debugger tab
If there is a NO SCRIPT FOUND red error message (most surely currently) select the “Use local script” redio button
Provide a debug script by one of three means:
Browse to your System Workbench install directory, then plugins\fr.ac6.mcu.debug_1.1.0.201503121050\resources\openocd\scripts\board and look for the script for your board (you may find also some st-specific scripts in st_board)
This is usually the way to use for a standard ST board (eval, disco or nucleo)
Manually search for a close board in the directory above then manually copy it to your project main directory, then browse to it and select it
This is usually a good way to go for a custom board that is very close to an ST board (often an EVAL board), including the same debug interface
Get a custom board debug script created when creating a project using your custom board (may be a no-firmware project with an empty main program)
You just have to copy the System Workbench-generated debug script in your project and browse to it
This is usually convenient if you define your own board, create a custom board in a System Workbench-generated test project and want to reuse it in your CubeMX-generated project