ST-Link Utility Error: “Can not connect to target!” — Blue Pill; Clone ST-Link

[Visu]

Hello,

I'm facing an issue while trying to program my WeAct STM32F411CEU6 board using a genuine ST-Link/V2 programmer via SWD interface. The ST-Link firmware version is V2J38S7 and the target voltage is detected as 3.14V.

However, every time I attempt to upload code (via STM32CubeIDE or ST-Link Utility), I get the following error:

"No STM32 target found" or
"Cannot connect to target. Please select 'Connect Under Reset'..."

I’ve verified the following:

• SWDIO is connected to PA13, SWCLK to PA14, GND and 3.3V connected properly.

• NRST pin is also connected from ST-Link to MCU.

• BOOT0 is set to GND.

• Tried both normal and "Connect Under Reset" modes in ST-Link Utility.

• Reduced SWD frequency to as low as 4kHz.

• Tried pressing and holding RESET during connection attempts.

Despite all this, the debugger still fails to connect. The device is detected on PC and ST-Link firmware is up to date. Could this be a firmware protection (RDP), hardware lock, or some issue with the board itself?

Any help or suggestions would be highly appreciated.

Thank you!

 

 

 

 

 

 

[Peter BENSCH]

Welcome @Visu, to the community!

please insert legible pictures of your ST-LINK/V2, front and back.

Regards
/Peter

[Visu]

 

[Peter BENSCH]

@Visu

You inserted again a screenshot of the programme, but I meant photos of the hardware ST-LINK/V2, front and back.

[LysAn]

Hello, I am plagued by this problem since almost a year now, with Mac OS, even with different ST boards. 

What helped me, is to try to establish a connection via Minicom or via Putty (so independent from the ST software). Also you can try to look in your systems settings whether your PC recognizes the device in the first place: on Mac OS that would be commands ls /dev/*usb* and system_profiler SPUSBDataType. Also you can try different cables, different USB ports, even different PC's. Finally, you can try powering the μCU externally.

The bottom line is, ST-Link is not reliable since many other users are reporting this issue.  

[Peter BENSCH]

ST resources are dedicated to supporting genuine ST products. We are not committed to ensuring that clones/fakes work properly with the firmware we provide.

This thread will now be locked. However, if you face difficulties while using genuine ST products, we’re here to assist you. Please feel free to start a new thread, and our team, along with community members, will be ready to help you with any issues/ questions you encounter.

Best regards,
Peter