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


Using Build Variables in debug Initialization Commands

Hi,
I’m not so sure that I understand what you really want to achieve, so I may not have the right answer.
By my understanding, the build variables like ${ProjDirPath} etc. are provided by Eclipse and then passing to shell level command invoking. If your debugging is through OpenOCD, and the debug initialization commands means of commands within OpenOCD context, then the OpenOCD has no knowledge about build variables like ${ProjDirPath}.
There may some ways to replicate those macro definitions into OpenOCD in the shell level when invoking OpenOCD, but I’m not an expert in OpenOCD and I can’t tell.
If you describe more detail about what you want, it would be helping people to understand, and so better answer your question.