Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev 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: 9799
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