STM32F0，ST-link v2，OpenOCD 0.9.0:打开失败 [英] STM32F0, ST-link v2, OpenOCD 0.9.0: open failed

问题描述

我正在使用 Launchpad的 gcc-arm-none-eabi 4.9-2015q2编译为STM32F0，现在我想使用该集合中的arm-none-eabi-gdb进行调试.我的ST-Link v2是Nucleo F411RE板的一部分，并连接了外部硬件(STM32F0目标).闪烁F0可以正常工作，因此我得出结论，我的SWD连接良好.

I'm using Launchpad's gcc-arm-none-eabi 4.9-2015q2 to compile for an STM32F0, and now I'd like to debug using arm-none-eabi-gdb from that collection. My ST-Link v2 is part of a Nucleo F411RE board, with external hardware (the STM32F0 target) attached. Flashing the F0 works fine, so I conclude that my SWD connections are good.

现在，我要启动 OpenOCD ，但失败:

Now I want to start OpenOCD, but it fails:

$ openocd -f interface/stlink-v2.cfg -f target/stm32f0x.cfg
Open On-Chip Debugger 0.9.0 (2015-07-26-16:02)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
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
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'

这可能是什么问题?

我也无法使用st-util建立连接，该连接报告了超时，最后总是因

I also couldn't establish a connection using st-util, which reported timeouts and in the end always crashed with a segmentation fault.

推荐答案

Nucleo F411RE嵌入了stlink v2-1而不是stlink v2

Nucleo F411RE embedded a stlink v2-1 not stlink v2

这样更改脚本文件:

source [find interface/stlink-v2-1.cfg]

transport select hla_swd

source [find target/stm32f4x.cfg]

reset_config srst_only

这篇关于STM32F0，ST-link v2，OpenOCD 0.9.0:打开失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！