Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

You are viewing a reply to not possible to debug - configuration of GDB fails  

not possible to debug - configuration of GDB fails

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

Reads: 3817
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