2020-05-14 12:18 PM - last edited on 2025-01-29 09:23 AM by Andrew Neil
When "ST-LINK: Could not verify ST device!" error appears and what the mentioned verification process consists of? Can I influence verification process in STM32CubeIDE and how?
I have STM32 MCU, which gives me "ST-LINK: Could not verify ST device!" in STM32CubeIDE whatever i do (trust me, i did a lot). ST-LINK Utility can connect to this MCU without any problem, so I wanted to ask for more information about the famous verification, which doesn't let me to debug the MCU. Thank you.
2025-01-29 09:16 AM
Mostly this is to protect against counterfeit devices.
I've seen the ST-LINK DLL in Keil throw this on STM32G031 devices, but it may be reflective of an initial probing/capture of SWD connectivity. And if the MCU is in a cooperative state.
Perhaps make sure NRST is connected, and "Connect Under Reset" is used. Or the bus speed is dropped, especially for CM0(+) devices, which often work a lower speeds.
You've provided little actual context to understand your specific situation. Elaborate.