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


not possible to debug - configuration of GDB fails

I think the problem is that OpenOCD is not running. Here is the console output with Kevins configuration file (ST-LINK_v2):

Open On-Chip Debugger 0.9.0-dev-00415-g2d4ae3f-dirty (2015-04-22-11:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Error: open failed
in procedure ‘init’
in procedure ‘ocd_bouncer’


If I include the ST-LINK_v1 the output is like this:

Open On-Chip Debugger 0.9.0-dev-00415-g2d4ae3f-dirty (2015-04-22-11:10)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: open failed
in procedure ‘init’
in procedure ‘ocd_bouncer’



So the call to libusb seems to work with ST-LINK-v2, but there is another problem to open the interface.

I’ve got exactly the same problem.

I am however able to flash my binary(s) using ST32 ST-Link tool (as admin on w8).

I’ve also updated my programmer’s firmware, so kinda lost aswell

Hi,

Just wanted to let you know what i did to fix this issue :-)


if added to my debug settings -> tab startup:


monitor reset
monitor halt
monitor flash protect 0 0 11 off

for your info:
i’m using a stlink v2 ebay programmer (updated via stlink util to latest version), not sure if this is mandatory, probably not...

a stm32 devboard (http://item.taobao.com/item.htm?spm=a1z10.1.w4004-386456545.4.3eifcC&id=22097803050), its stm32f103c8
both boot0 and boot1 are in 0 position.

hope this helps!

I found a different fix. The VID/PID pair in stlink-v2.cfg was wrong. They had this:

> hla_vid_pid 0x0483 0x3748

but it should be this:

> hla_vid_pid 0x0483 0x374B

letter “B”, not the digit “8”. I looked up the correct VID/PID using Windows Device Manager...

Be careful, the stlink-v2.cfg is not wrong :

VID/PID 0x0483 0x3748 for ST-Link/V2
VID/PID 0x0483 0x374b for ST-Link/V2-1

There is a stlink-v2-1.cfg if needed.