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


openocd - wrong paths on win x64

My mistake. Following the exact steps described on User Guide - “Importing an STM32CubeMX generated project under System Workbench for STM32” it was possible to compile and debug the project (STM32F3 Discovery board).

I use a Win 8.1 64 bit machine

It turns out that the System Workbench set few paths (correct paths) when it is invoked by pressing the Debug icon on the Eclipse:

Open On-Chip Debugger 0.9.0-dev-00415-g2d4ae3f-dirty (2015-04-22-11:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
User : 13 15 command.c:546 command_print(): debug_level: 3
Debug: 14 15 configuration.c:44 add_script_search_dir(): adding C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.2.0.201506021103\resources\openocd\scripts\st_board
Debug: 15 15 configuration.c:44 add_script_search_dir(): adding C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.2.0.201506021103\resources\openocd\scripts

and then configuration files could be found

Debug: 22 15 configuration.c:84 find_file(): found stm32f3discovery.cfg
Debug: 23 15 configuration.c:84 find_file(): found C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.2.0.201506021103\resources\openocd\scripts/interface/stlink-v2.cfg


To activate debug output for openocd I have added “-d3” under “OpenOCD Command:” entry in “Debug Configuration” window under “Debugger” tab, the comand looks like:
”${openstm32_openocd_path}\openocd.exe” -d3
The output is printed in Console window when debug is started

Attached is the complet file log.