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


Cannot program or debug STM32VLDiscovery

Hello,

I compiled a small “Blinky” program for a STM32VLDiscovery board, I can program the kit with the ST-LINK utility but not from the Eclipse IDE.

I get an error:

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333

Error message from debugger back end:
localhost:3333: The system tried to join a drive to a directory on a joined drive.
localhost:3333: The system tried to join a drive to a directory on a joined drive.

(correct, the last line is repeated).

A similar program is downloaded and debugged without problems on an STM32F0Discovery board.

Regards and thanks,

Fernando

I ran into this problem as well when I started using SW4STM32.

The resoultion turned out to be related to the type of USB port you had your board/debugger plugged into. When I plugged my board into a USB 3-compatible port, I saw the same error message. When I plugged my board/debugger into a USB 2 port, I was able to (eventually, after some messing around) get debugging to work.

Try plugging your board into a different USB port and try again.

Same here, with Workbench Eclipse plugin on Debian Linux, with STM32F7 Discovery board.
Acutally it doesn’t seem to be a problem of USB 2 or 3: I had to switch between two USB 2 ports, one is working, the other gives a timeout error. Don’t know why.


On the proejct propertie c/c++ ac6 target make sure ther’s a board mcu device selected (it used to not be set on some cubemx generated project)
that is the final -f params to openocd if missing openocd will obvisouly fail to detect board and connect.

by the way how did you start debug on eclispe ide have you created a debug config ?

The openocd log may help here
you can get opencod log console fro hat click the arrow close to the console icon select openocd in teh drop down list open ocd , gdb etc ... )

if shoudl look like
Open On-Chip Debugger 0.9.0-dev-00416-gc6629a9-dirty (2015-08-03-16:31)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html

====> may stop stop here if no mcu/baord given

Info : auto-selecting first available session transport “hla_swd”. To override use ‘transport select ‘.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz

===> if no st link is detected it will stop here

Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v14 API v2 SWIM v0 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 2.882250
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting ‘gdb’ connection on tcp/3333
etc ....

if you have an ac6 target debug configruation (bug icon drop down) open the config check board etc there if all ok.

On window you may have a firewall alarm first time you start openocd that could delay or prevent it to start.

I remenber of some board not suported by official openocd (no cfg file) (l053 for instance) but ok on ac6 (extra cfg file added )
i don’t nwo how ac6 install on linux system bvtu if you use yoru own openocd doubek checkl teh cfg fiel is welel present as teh stm34f7 is recent i woudl nto be surprise thers’ not yet any cfg and support for it .

last it is true that openocd use libusb there’s few knwon issue with some usb host under win7
for nec usb 3.0 contoler be sure to update to a recent driver or it may not work.
for ti usb 3.0 controler it may not be dectect on all ports .

if you have the st utility use it it can connect to the baord then usb port or drivers is likely not the problem.