STLINK-V3 not detected by STM32CubeIDE but works with STM32CubeProgrammer

[pepsipower]

Hello,

I am experiencing a consistent connection issue with my development setup:

Hardware/Software Configuration:

• MCU: STM32 (exact model: STM32G474VET6)

• Debugger: STLINK-V3

• IDE: STM32CubeIDE

• Programmer: STM32CubeProgrammer

• Operating System: Window

• Target board : Custom board
  • art of custom board schematics : 
    

Problem Description:

• When connecting my STLINK-V3 to STM32CubeIDE, the IDE fails to detect or connect to the target device. It typically shows error messages like “No ST-LINK detected” or “No target found.”

• However, when I use STM32CubeProgrammer, the STLINK-V3 is detected and connects to my target MCU without any issues. All programming and memory read functions work perfectly.

• While many boards face connection issues with STLINK-V3 in STM32CubeIDE, some boards succeed to be connected.

Questions:

• Has anyone experienced similar issues where STM32CubeIDE fails but CubeProgrammer succeeds with STLINK-V3?

• Are there recent changes in CubeIDE or driver packages that could explain this?

• Any additional steps or patches recommended for resolving this mismatch?

• Are there any configuration that i can try on CubeIDE? (eg data rate)

[Andrew Neil]

Please show the logs from CubeIDE, and screenshots of the errors.

PS:

Also, what versions, and on what Host?

How to write your question to maximize your chances to find a solution

[AScha.3]

Hi,

>  While many boards face connection issues with STLINK-V3 in STM32CubeIDE, some boards succeed to be connected.

The IDE checking the cpu is "genuine STM" , so it refuses connect on all cpus that might be not from STM.

CubeProgrammer connects -if possible- also to other ARM cpus.

But here , on (i assume) genuine STM32G474VET6 , it should connect also in IDE .

Maybe try: set debug to using openOCD  (i had some strange "no target.." , but switching the debug to OCD - it works.  And even switching back the debug setting, it works. This happened also on boards, working before....and then also working again. So dont ask me "why" .)

so try: (and adjust the settings...see:)

 

[pepsipower]

Thanks all,

I'm out of the office right now. Here i attach the log i get from failure cases....

 

STMicroelectronics ST-LINK GDB server. Version 7.11.0

Copyright (c) 2025, STMicroelectronics. All rights reserved.

 

Starting server with the following options:

        Persistent Mode            : Disabled

        Logging Level              : 1

        Listen Port Number         : 61234

        Status Refresh Delay       : 15s

        Verbose Mode               : Disabled

        SWD Debug                  : Enabled

        InitWhile                  : Enabled

 

Target unknown error 19

 

Error in initializing ST-LINK device.

Reason: Unknown. Please check power and cabling to target.

-----

Let me update other properties like host version, Stlink F/W version very soon...