STM32F0, ST-link v2, OpenOCD 0.9.0: open failed

Question

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

Answer 1

In my case I also got Error: open failed but all the configuration was OK. Then I did dmesg | grep usb to see why it cannot connect via USB (on Ubuntu). The dmesg told me that there are power issues and perhaps the cable is faulty. As I had used the same cable earlier the same day and some LEDs still flashed on the board, I first ignored the message. But then I finally decided to try, bought another cable and lo and behold! It was a faulty cable - with the new one everything works. So, not always a software problem after all.

Though if you do lsusb (or use device manager in Windows) and the board is nicely listed, it will probably not be a cable issue. If it is missing, it might be.