Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

[ prev topic | next topic ]  

Changing debugger/programmer for project

Posted by samf48 on 2016-12-21 03:58

How does one go about changing the debugger/programmer from the original settings in a build to a new settings. My issue is that I had started a project using a discovery board with the build-in ST-Link V2.1 to a custom board with a stand-alone ST-Link V2.

I’ve tried so many a “Manual Spec” under debugger settings and a custom script. No matter what though, in my console it always comes up with this message: “”C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.externaltools.openocd.win32_1.10.0.201607261143\tools\openocd\bin\openocd.exe” -f stm32l476g_disco.cfg”

I am no longer using that board and yet System Workbench defaults to it. What do I have to change?

Reads: 5868
Link
Posted by samf48 on 2016-12-21 18:48
Follow up to this, I ended up getting this working with the attached script and selecting a “local script” in the debug options. One thing that I had to figure out, which I couldn’t find anywhere, was that I had to keep unplugging and re-pluggin the ST-Link V2. in order to get that “read error” to go away.
FMC2.cfg (313 b)
Link