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 debug using ST-Link/V2

Running on Windows 10, SWSTM32/Eclipse 4.6.3. This is a new computer / new installation and unfortunately the old one is gone.

I am using STM32F469II, and can program using ST-LInk program with no issue.

I am utterly unable to debug using AC6/SWSTM32 IDE. I find no end of error reports, but none seem to match. I do have a reset line connected, so that meme does not apply.

Using a debug configuration “AC6 STM32 Debugging”, I get a variety of errors, usually something like:

“Open OCD child process termination. Reason: Unplugged target or STLink already in use or STLink USB Driver not installed”.
(all of which are not true).

Further detail:
Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)
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: 12000 kHz
adapter_nsrst_delay: 100
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 12000 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: open failed (no matching adapter found)
in procedure ‘init’
in procedure ‘ocd_bouncer’


I have installed the latest firmware / St-link drivers and utilities, I reinstalled the l&g SWSTM32, no change.

I also note in the debugger settings that I do not have an SWD option, and that is how I am connected. This is the ST-Link output when connecting to the same target:
23:27:57 : ST-LINK SN : 37FF6C064D4E383542330343
23:27:57 : ST-LINK Firmware version : V2J34S7
23:27:57 : Connected via SWD.
23:27:57 : SWD Frequency = 1,8 MHz.
23:27:57 : Connection mode : Normal.
23:27:57 : Debug in Low Power mode enabled.
23:27:57 : Device ID:0x434
23:27:57 : Device flash Size : 2MBytes
23:27:57 : Device family :-STM32F469x/F479x


I used ST Cube MX to create the frame work for this project, and selected the correct debug connection.

Any suggestions on fixing this?