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

You are viewing a reply to Run without program?  

Run without program?

The Debug Configurations window is the full height of the screen - its just that it is empty to start with, all other tabs are fully populated.

I’ve done an update and I’m running on a 64bit Kubuntu 14.04.4 LTS. Java -version
java version “1.7.0_101”
OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-0ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

Selecting another config and then back to the GDB OpenOCD Debugging config initially populates the “Initialization Commands” area, subsequent random tab selections eventually causes the “Load Symbols and Executable”, “Runtime Options” and “Run/Restart Commands” sub-windows to appear and be populated.

My eventual aim would be to determine why some prototype boards program OK from GDB and other fail when they all program OK using st-flash (from the texane/stlink package) and using OpenOCD in telnet mode. That way I wouldn’t have to be concerned with NOT programming the target.



You talk of the “GDB OpenOCD Debugging” configuration. You should use the “Ac6 STM32 Debugging” configuration, not the “GDB Hardware Debugging” configuration. The Ac6 is based on the CDT GDB support, but it is an extended, tailored, configuration.

Bernard (Ac6)