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 two short videos (registration required) highlighting:

System Workbench for STM32


STM32VLDISCOVERY no connect

Hi,
I’m working with a board STM32VLDISCOVERY on a chip STM32F100RBT6

When connect the board and press the RUN button, a message is displayed:
“OpenOCD child process termination
Reason:
Unplugged target or STLink USB driver not installed”

Detailed:
” Open On-Chip Debugger 0.10.0-dev-00007-g58350bc-dirty (2018-01-08-12:20)
Licensed under GNU GPL v2
For bug reports, read
http: //openocd.org/doc/doxygen/ bugs
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_nsrst_delay: 100
adapter speed: 950 kHz
Info : clock speed 950 kHz
Error: open failed (no matching adapter found)
in procedure ‘program’
in procedure ‘init’ called at file “embedded:startup.tcl”, line 485
in procedure ‘ocd_bouncer’
** OpenOCD init failed **
shutdown command invoked”

In the “ST-Link Utility” , the STM32VLDISCOVERY board is programmed fine.
The STM32F407G-DISCO1 board is working normally.
What could be the problem?
What do I need to do to make the board work?

Hi Kisoff,

When you press the run button, is the ST-Link Utility is still connected to the target?
If not, add the openocd option “-d” in the debugger tab of your run configuration to share more info on the pb.

Regards,
Elliot


Hello,

Sorry but STM32VLdisco is using an old STLink V1 and is not supported by SW4STM32.

Rgds,
Laurent


Another reason for this might be caused by the type of USB port the board is plugged into.
I have found that the ST-provided “ST-Link Utility” will work with Nucleo/Discovery ST-Link plugged into any type of USB port. However, the version of OpenOCD provided with SW4STM32 does not work with ST-Links that are plugged into USB3-capable ports.

Try plugging your board into a USB2-only host port and try again.