Could not verify ST device when attempting to debug

jean_bonneau · ‎2026-01-29

SOMETIMES (not always), when i try to debug (and only when i try to debug, run does its job well) with STM32CubeIDE my Riverdi board, i encounter the "Could not verify ST device! Please verify that the last version of the GDB-server is used for the connection" error. It happens right after

Loading RTOS driver... ThreadX

Connecting to GDB server 127.0.0.1 on port 61234 ... Connected

Listen for GDB connection on port: 60000 ... Connected

.if this helps.
Downloading code with run is always fine, and sometimes the debug option works, but not always. It is really annoying to rely on luck to make the *** thing work. I tried unplug-replug. The board is definitly not counterfeited, same goes for the ST-Link.

mƎALLEm · ‎2026-01-29

Hello,

What STLINK device are you using? a genuine ST link? it could be a counterfeit ..

See How to recognize a genuine ST-LINK/V2 versus a cloned one

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

jean_bonneau · ‎2026-01-29

It looks like a geniune ST-Link/V2

Andrew Neil · ‎2026-01-29

Similar: "Could not verify ST device" when Debugging with RTOS Proxy; OK without ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

mƎALLEm · ‎2026-01-29

Could you please share real pictures of your ST-LINK?

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

jean_bonneau · ‎2026-01-29

Here you are
If you want images of the inside too, tell me if popping the cover with a flat screw driver seems ok for you

mƎALLEm · ‎2026-01-29

It seems OK.

You need also to check the wiring/connections. Are they stable and well fixed? I mean the connection between ST-LINK and the board connectors..

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

jean_bonneau · ‎2026-01-29

The ribbon cable doesn't seem damaged, the JST connector is properly connected, the ribbon cable is properly connected to the JST and the ST-Link connector (at least it seems so), and i use the same usb cable/port all the time with a Microchip debugging probe without encountering issue. Unless there is a specific pin i can further investigate on, i don't know where it fails. However wouldn't i encounter a "No target detected" error if this was the issue?