I'm programming stm32f103 using CUBEIDE. I'm having this error "Could not verify ST device! Please verify that the latest version of the GDB-server is used for the connection."

[H.Ahmed]

I have selected the debug prob to ST-LINK OpenOCD.

[Tesla DeLorean · Accepted solution]

Has it worked before?

Is this a Blue Pill board with a fake STM32?

What's connected to the probe? You have NRST? Does connect under reset work?

Does STM32 Cube Programmer, the stand-alone app, work with this board/part?

[Tesla DeLorean]

Duplicate thread https://community.st.com/s/question/0D53W00001tMmEDSA0/can-anyone-help-me-solve-the-failed-to-start-gdb-server-error

[mattias norlander]

Yes - seems like duplicate post. Difference is that here it is OpenOCD which is reporting fake device. In the other thread it is ST-LINK GDB server...

Based on the discussion in the previous thread I think we can "close" this one too...

[Neolithic]

AOA Ahmed, I am facing a similar issue with STM32F407. My OpenOCD (gdb-server) is running remotely on Raspberry pi. Until STMCube IDE version 1.6 everything was fine. I updated it today to version 1.14 and it started giving this error. I have seen most of the posts in the context of bluepill. On OpenOCD side, i have these messages:

Can you please tell me how did you solve it?

Regards,

Junaid