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


custom MCU project " OpenOCD Script not found "

Hello to everyone,

First of all thank you again for that forum, and by advance to all those how take a bit of their time trying to help me ! My previous requests here were really helpfull. Hope I can help myself someday when I get skilled enough.

I have been using stm32 workbench for industrial purspose, I wich to replace licenced IDE ( keil, attolic etc ...) systems by opensource one in my company promoting opensource and not only for pricing policy but for code transparency, maintainability and also to be able to contribute in sharing my drivers with open soruce community.

I have been using STM32 workbench for few months, I only used to focus on stm32f407 drivers developpement, I have been using a lot of drivers from I2C to usart to CAN normal and loopback mode

Now I focus on using stm32workbenck for a custom industrial project.

So far I wonder if i am doing the right things :

I’ve been testing drivers with an stm32f4 discovery board with stm32f407VGt6 MCU.

I am actually using the stm32f4 discovery integrated swd stlinkv2 for flashing and debugging.
I also purchased an standalone stlink V2 kit.

I have been trying to used stm32workbench file -> new -> c project -> AC6 stm32 MCU project to generate a custom MCU board project.

When this is done I get a new workspace generated, I can compile but once trying to start debbug I get the following error message from eclipse IDE :

“launching trialstm32f4customboard.elf” has encountered a problem

OpenOCD Script not found

I’ve been going threw the web to look for a solution but couldn’t find any so far.

Has any of you had this error so far ?

What is the best way to generate a project for a custom board ? should i use stm32cube MX for startup file genretation ?

I am beeing really humble here I am an experienced electronics engineer more used to assembly language and feel a bit lost with this issue.


Thank you all by advance.

Hi,

Custom board on System Workbench is a quick but not really precise way to create and test a project for your board. CubeMX provided a complete interface to configure your chip then to generate a project with configuration and drivers code (Make sure, you’re using the latest version of CubeMX ! There are known issues in the generated project for SW).

About your issue :
The OpenOCD script is a configuration file (*.cfg) use by OpenOCD (On-chip debbuger) to identify your debug device and chip. With custom board, a *.cfg file should be generated into your project directory. Is this file existing in your project directory ?

1/ It it exists, go to Run > Debug configuration..., then select your debug configuration and go to the “Debugger” tab. In “Script” section, select “use local script” and browse the *.cfg file.

2/ If not, make sure you’re using the latest version of the SW, then try to create a new project again with your newly created board selected (It should be listed in STM32F4 series). The OpenOCD script should be generated this time. You can copy the *.cfg file into your first project then do as how I describe in 1/.

As I cannot reproduce your issue, I don’t if what I’m suggesting will solve your problem...
Hope it helps you.

PS : Find my OpenOCD script for STM32F4DISCOVERY in attachement if needed.


Hi,

Just a small addition.

Attached is a screen-shoot: with red is highlighted the OpenOCD script (added by System Workbench) - down in picture and the AC6 debug configuration left upper.
Check if you have something similar (except the script name - should be the name that tang give you)

Even if you use CubeMX to generate the project you will have to create the Debug Configuration - check section Setting up your project for debug on below link (if you follow this steps be sure to choose correct ST Link version v2 OR v2.1):
http://www.openstm32.org/Importing+a+STCubeMX+generated+projectQuestion


Hi,

thank you all for those fast answers !!! I really really appreciate it a lot here !


first to tang  :

thank you I added your .cfg file and my debugger is running back again :-) !!!

But then I am wondering if defining custom board project with stm32 workbench wizzard using file -> new -> c project -> AC6 stm32 MCU project to generate a custom MCU board project is supposed to produce an OpenOCDscript .cfg file why isn’t working on my SW ? I will then try to set up the last release to see if ti fixes the problems!

or maybe SW is generating the OpenOCDscript .cfg but i could’nt find it ? i tried browsing and searching from workspace directory root ./workspace.

When Sw is generating this file where is it generated by default please ?

Then too both of you : I started using stm32cubeMX and if working great generating startup files but I it supposed to generated a OpenOCDscript .cfg script when specifying an SW project target aswell ? If it is were is it supposed to be stored in result directory ?


Once again thank you a lot for your support !

For custom boards, the OpenOCD script should be generated when the project is created. The file is in the project root directory and should be automatically found by the IDE.
I don’t know why it was not generated for you. Maybe the update will fix this.

STM32CubeMX does not create the OpenOCD script. After imported and built the generated project from CubeMX to SW, when you launch the debug, a window should pop up to ask you to choose the debug device like when you’ve created a custom board. After this step, a OpenOCD script is generated into the project root directory.

Kevin.