Loading...
 

STM32MP1 support available in SW4STM32

   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 download a short video showcasing this on the ac6-tools website (registration required).

System Workbench for STM32


absolute script path in debug/run launch configuration

In stored debug/run configuration file the openocd scipt file is stored as aboslute file path
that make the configuration machine/user/os instalation type dependant what is anoying.
Opencocd manage script relative path very well so relative path solution should be posible

In confguration the key is

stringAttribute key=”fr.ac6.mcu.ide.OPENOCD_SCRIPT”

and value are

“C:\Users\xxxx\AppData\Roaming\Ac6\SW4STM32\openocd\scripts\st_board\nucleo_f401re.cfg”
“lilkley a window package install” with all file in user directory


“K:\eclipse-luna\plugins\fr.ac6.mcu.debug_1.1.0.201503121115\resources\openocd\scripts\st_board\nucleo_f401re.cfg”/”
An eclipse install from update site

idealy it should bed one using internal pulgin install relative path like :

stringAttribute key=”....openocd.gdbServerOther” value=”-f board/stm32f4discovery.cfg”
stringAttribute key=”...openocd.gdbServerExecutable” value=”${openocd_path}/${openocd_executable}”

You can use the -s parameter to specify the scripts directory to OPENOCD the it will find the files when you put -f “interface/stlink-v2.cfg”.

Example: -s “C:\openocd\scripts”