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

Forum List Topic List

[ prev topic ]  

not possible to debug - configuration of GDB fails

Posted by vrd on 2015-05-05 10:42

i try to get the IDE running but fail to debug my application on the STM32 Value Line Disco Board.

i created a new project, compiled it successfully and tried to debug it.

i chose the OpenOCD script (local script) stm32vldicovery.cfg under: C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.debug_1.0.0.201412011131\resources\openocd\scripts\board

when i run debugging it always ends up in the step: configure GDB and shows afterwards the error message. (see attached image.)

i read a lot of hints and helps and forum entries but still not able to get it work. i have no idea what to do to get it work.
has anybod the same problem and a solution?

best regards

Dominik

Untitled.png (186.17 Kb)
Reads: 25616
Link
Posted by tang on 2015-05-05 11:11

Hi Dominik,

I think this board is not supported on System Workbench due to the Embedded ST-Link/V1.

I’m afraid that there is a conflict between ST-Link/V1 and ST-Link/V2-1 drivers .

Sorry not to be more helpful.
Kevin.

Link
Posted by vrd on 2015-05-05 19:13

Hello Kevin

Thank you for information

i tried 2 days to get it run... i’m glad i finally did my post in the forum...
i tried the sw4stm32 with the f0 disco board and it worked out of the box...

is it just the stlink version which is the problem. so can i bridge the stlinkv2 from the f0 disco board to my f1 disco board and it should work also? (i have no cables right now so i can’t test it here...)

thank you

Link
Posted by tang on 2015-05-07 12:07

Hi Dominik,

I’ve just tried to bridge the ST-Link/V2 from an F0Discovery on the VLDiscovery as you suggested. You only need is to modify the OpenOCD configuration script (to use the ST-Link/V2 instead of the ST-Link/V1) and it will work.

You can find my OpenOCD script in attachement.

Best regards.
Kevin.

CUSTOM_STM32VLDISCO.cfg (337 b)
Link
Posted by bluenow on 2017-06-21 22:06

Hi Tang,
Could you provide a little more details on how you bridge the ST-Link/V2 from an F0Discovery on the VLDiscovery?

Regars,
Andy

Link

Posted by niieg on 2015-06-03 21:53

Hi Dominik and Kevin,

I have the exact same problem as you Dominik.

I use a STM32VLDiscovery-Board and try to debug it ... without success.

I also included Kevins configuration file, and tried that with the stlink-v2 as well as the stlink-v2-1 configuration. Always the same error message you posted.

Do you have any hint for me to debug the problem. Right now I can’t see where to start.

I downloaded the Atollic TrueStudio LiteVersion and here I can debug without problems.

Best regards
Stefan

Link
Posted by niieg on 2015-06-03 23:28

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.

Link
Posted by vinietje on 2015-06-25 22:24

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

Link
Posted by vinietje on 2015-06-25 23:00

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!

startup-addition.png (40.21 Kb)
Link
Posted by clovett on 2016-04-08 00:49

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...

Link
Posted by tang on 2016-04-08 16:17

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.

Link