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 ]  

Please update OpenOCD

Posted by khockuba on 2017-03-10 17:39
I noticed I can’t connect to my custom board with L476. ST-Link utility on the other hand could succesfully connect to the board under all conditions and program it. After I downloading final release of openocd (0.10), I could also succefully debug the board. Solution please update SW4STM32 from unstable development version to current one.
Reads: 7712
Link
Posted by dellamorte on 2017-03-13 22:58
Same problem! I’m running it on Manjaro linux machine. I downgraded it to older version, now it works again.
Link
Posted by LaurentL on 2017-03-15 11:29

For Dellamorte,

On which STM32 device ?

Is it a custom board ?

Reset line connected ?

Can you send the openocd log file ?

Thanks,
Laurent

Link
Posted by Bettemand on 2017-03-16 12:34

How do you downgrade it? tried to do it via the eclipse addon installer, but wont work.

openocd just terminates instead of running my program on STM32L100C-discovery

Link
Posted by LaurentL on 2017-03-16 13:13

On which OS ?

What do you mean by running your program ?
Are you using the menu Target => Program chip... ?

Or the Debug isn’t programming your appli code ?
Can you add -d in openocd options in debugger tab in debug configuration and attach the result log file ?

The previous version was working fine on the L100C disco ?
On which plugin version are you now ?

Can you try a fresh SW4STM32 install ? Installer exe have been updated.

Rgds,
Laurent

Link

Posted by LaurentL on 2017-03-15 11:28

Hello,
On which OS are you working, Linux ?

Can you try to send the openocd log text file (with -d option) please ?

Do you connect the STLink reset line on your custom board.

Thanks,
Laurent

Link

Posted by khockuba on 2017-03-16 19:32

Look my config file is working correctly I’m using OS X. To test my assumption there is something wrong with openocd I used two different openocd binaries one which is most recent openocd 0.10 release, this worked correctly with connection under hardware reset. Then with pretty much the same config file openocd provided with s24stm32 fails when asserting rst and throws an error. This is obviously related to openocd version since newer works fine under the same conditions.

For temporary fix you can simply replace all the binaries and scripts under openocd plugin folder in Eclipse with new ones on openocd website.

Link
Posted by LaurentL on 2017-03-17 11:13

Hello Khockuba,

Did you just install SW4STM32 now and see the issue or it was working fine with a previous version ?
If yes, on which version it was working and are you using now the 1.14.0 version?

Can you attach the openocd log file with the error you got (add -d to openocd options in debugger tab of debug config window) ?
To know if it is a cfg file problem or if it is an openocd binary issue.

For the moment, SW4STM32 forces to use “Connect under reset” mode in the cfg files so your custom board should connect the STLink reset line to STM32 Reset input pin.
For info, all the STM32 ST boards (Nucleo, Disco or Eval) have the STLink reset line connected.

Rgds,
Laurent

Link
Posted by LaurentL on 2017-03-22 16:56

Hi Khockuba,

It seems there is an issue on SW4STM32 latest version (1.14.0) for “use local script” cfg file.
The openocd binary is ok, it is the cfg files that have issues.
If the board cfg is in project workspace, it won’t be executed. That is the case for custom board created during a new project.
The workaround is either to copy the cfg elsewhere and to reselect it by browse button or to use the “manual spec” mode for the cfg.

And for the boards that don’t have reset line connected from STlink, you can add the -c “reset_config none” in openocd options in debug config launch (debugger tab).

Rgds,
Laurent

Link
Posted by grublu on 2017-03-25 20:06

Bonjour Laurent
Thank you, that did the trick. Had the same issue with my F401 custom board. Copied the x.cfg to another location outside the project workspace and reselected it. Now it works.
Best regards
Ludwig

Link
Posted by khockuba on 2017-03-25 23:03
Perhaps you are correct though I can’t even upgrade to 1.14 as it doesnt show up as update in Eclipse latest version that show up are 1.12 something
Link
Posted by LaurentL on 2017-03-27 11:01

Hello Khockuba,

When i say 1.14.0, it is SW4STM32 version, so the “mcu.ide” plugin version.
mcu.debug plugin is indeed 1.12.1
openocd.win32 is 1.13.1

Rgds,
Laurent

Link