OpenOCD "open failed" error

Support
1

Does anyone know what this error means?

openocd -f interface/stlink.cfg  -f target/stm32f4x.cfg
GNU MCU Eclipse OpenOCD, 64-bitOpen On-Chip Debugger 0.10.0+dev-00593-g23ad80df4 (2019-04-22-20:25)
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: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 2000 kHz
Error: open failed


make: *** [Makefile:17: flash] Error 1

What I have tried:
1)

OPENOCD := openocd -f interface/stlink.cfg \
		$(if $(value PROGRAMMER),-c 'hla_serial $(PROGRAMMER)',) \
		-f target/stm32f4x.cfg

OPENOCD := openocd -f interface/stlink-v2.cfg \
		$(if $(value PROGRAMMER),-c 'hla_serial $(PROGRAMMER)',) \
		-f target/stm32f4x.cfg

OPENOCD := openocd -f interface/stlink-v2-1.cfg \
		$(if $(value PROGRAMMER),-c 'hla_serial $(PROGRAMMER)',) \
		-f target/stm32f4x.cfg
  1. reinstalling OPENOCD
  2. running make flash while the odrive is powered and plugged in
  3. reading through the link that is provided in the error here

I can’t seem to figure out what is going on.

Is running make flash required in order to flash a new firmware to the board? Or can I just compile the firmware and then flash the resulting .hex file?

2

You can just compile the firmware then flash the .hex with DFU

I’m not entirely sure what the problem would be there. Perhaps your STLink isn’t working properly, or it’s not setup correctly?

3

Hi,

Just to rule out a hardware problem, Is the stlink showing up cleanly in the device manager? (assuming windows here)

Cheers
Simon