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


Unable to single-step application code

I am using a Win10-64bit PC on which I have installed System Workbench V1.8 and I have NOT applied any updates to it via Help|Check for Updates. The project itself uses an STM32F411RET device and the project was generated using STM32CubeMX V4.18.

I have a debug and release build configuation. For the debug configuration I am using Optimization -Og and Debugging option -g3. The code builds OK. The board I am developing for is not yet available so I am using a Nucleo-F411RE for now.

The debug configuration has been set to use an ST-LINK V2-1 probe and SWD interface.

When I start a debug session the code is loaded to the target but the code executes without stopping at the breakpoint in main(). The code appears to function as expected (LED light flashing etc.).

I have attached the text written to the Console.

Any help would be appreciated.

Regards
FarmerJo

As an exercise I un-installed System Workbench and the ST-LINK drivers. I then re-installed it and re-imported the original CubeMX project. I then rebuilt it and created a build configuration. I was able to start the debugger and single-step the code as expected. However, when I exited System Workbench and restarted it again I was again no longer to single-step.

Any ideas?

I have also found that I can get single-stepping back when I goto Debug Confugurations then goto the Debugger settings select Use local script|Apply and then Manual Spec|Apply. Note that the local script does not even exit for this custom board design.

If I do not get this the Console window ends with the following every time.
...
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
adapter speed: 1800 kHz
shutdown command invoked

What is System Workbench do when I switch between the script types that allows the debugger to single-step?

Also do I get System Workbench to generate a local script for a custom board?

Regards
FarmerJo

This issue has finally been resolved. As pointed out by robertkendrick in a recent post it requires enabling in the SYS block of STM32CubeMX.

Regards
FarmerJo