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


Debug Configuration no Target Information

I have imported my STM32 Project to System Workbench and I am trying to create the Debug Configuration.
I have added the Ac6 STM32 Configuration, and can configure everything except the Target Information Mcu / Baord.

I have looked at the project properties but am unable to find this, I don’t have any tabs for Target.
Any help/pointers appreciated.

France

Hello,

I confirm there’s no way to update target information relying on launch configuration.

Only way to setup a target is either at project creation (relying on CubeMx or System Workbench project creation wizard) or updating project C/C++ build settings. You can get build settings UI requiring for project properties C/C++ Build > Settings > Target tab. Once build configuration updated you can create a launch configuration in sync. with (be aware any existing launch configuration will not be updated).
Doing such please take care about C/C++ Build > Settings > Target tab warning notice ...

Br,


Hello, Smart people,

I am using sw4stm32 to debug a project created by Stm32cubeMX. MCU is stm32f103zet. Normal compile no issue. However, when I debug it with ST Link V2, the message came out like this:

Wrong device detected
Open On-Chip Debugger 0.10.0-dev-00004-gcef2a8c-dirty (2017-08-31-14:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 950 kHz
adapter_nsrst_delay: 100
Info : tcl server disabled
Info : telnet server disabled
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v23 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.236436
Error: init mode failed (unable to connect to the target)
in procedure ‘init’
in procedure ‘ocd_bouncer’

Can any one help me to explain the message and guide me what to do?

Thanks a lot!

Hi,

To enable SWD debug on STM32F1 devices, you need to configure in the cubeMx the “Pinout -> SYS -> Debug -> Serial Wire”.
Have you done that ?

As you have no more access to the target mcu with SW4STM32, you will need to program the controller once in a different way, for example with ST-LINK Utility.

If you haven’t the reset connected from the STLink, you will need to use the “software reset” in the debug configuration options.

Rgds,
Laurent