Skip to main content
Visitor II
June 3, 2025
Question

Cannot Connect to STM32G0B0CET6

  • June 3, 2025
  • 3 replies
  • 264 views

Hello, 

I am trying to flash a STM32G0B0CET6 and keep getting "Error: No STM32 target found!" When trying to connect. 

Through the power supply I can see that the device properly resets. The voltage target also goes to 0 when the device turns off. I am using an ST-Link V2 with a Tag-connect TC2050-ARM2010 and TC2050-IDC cable to program. 

 

    This topic has been closed for replies.

    3 replies

    Super User
    June 3, 2025

    Has it ever worked?

    Does correct voltage get detected by STM32CubeProgrammer?

    Consider showing the schematic.

    ST Employee
    June 4, 2025

    Hello @ra345j 

    Ensure all connections between the ST-Link and the STM32 board are secure, and also check that the jumpers are set correctly. Update the ST-Link firmware using STM32CubeProgrammer if needed. If the issue persists, try the "Connect Under Reset" mode. For more help, refer to the FAQ: "How to Solve Debugger Connection Issues."

    Br

    Super User
    June 4, 2025

    Welcome to the forum.

    Please see How to write your question to maximize your chances to find a solution for best results; in particular, please give full details of your development host and  target hardware setup.

     


    @ra345j wrote:

    getting "Error: No STM32 target found!" When trying to connect. 


    Where, exactly, are you getting that?  what tool(s) & versions are you using?

    Please show the full logs & messages you get.

     


    @ra345j wrote:

    I am using an ST-Link V2 with a Tag-connect TC2050-ARM2010 and TC2050-IDC cable 


    Is it a genuine ST-Link?

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

    Are you sure the cable wiring is correct?

    As @TDK said, please show a schematic.

    Some good, clear photos may also help

     

    See also:

    How to solve connection errors when connecting and programming the STM32 target board.

    How to solve debugger connection issues.