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 ]  

Solving OpenOCD Debugging/Uploading problem

Posted by bugmenot on 2015-06-11 10:15

Hi, I just want to share a solution to a possible problem. I created a custom board based on STM32F407 MCU. When trying to upload firmware or debug there was OpenOCD error. I solved it by changing this configuration file include in the ProjectName.cfg file:

interface/stlink-v2-1.cfg

to this:

interface/stlink-v2.cfg

because my ST-Link device on STM32F4-Discovery is v2. Newer Nucleo boards have ST-Link v2.1 in which case no correction is needed.

I would suggest OpenSTM32 developers to have a setting in the GUI to select the ST-Link version.

Thanks.

Reads: 11480
Link
Posted by dautrevaux on 2015-06-11 12:06 France

Hello,

The setting is available in the dialog whan you create your custom board; the default is STlink-v2-1, but you should select the right debugging device at this time. If you make a mistake, just delete then re-create your board.

Bernard

Link
Posted by catacluj on 2015-09-21 22:25

How do I do this once the project is underway?
I don’t want to start from scratch again.
I’m not sure I have the same problem but I can’t program/debug my custom board at all although I can if I use the ST-Link utility outside System Workbench.

Thanks,

Cat

Link

Posted by bugmenot on 2015-06-11 13:32
Oops, my bad then, I missed it when creating the board, sorry for the noise.
Link