Skip to main content
P
paraschivescue
Associate
May 15, 2026
Solved

CubeProgrammer + ST-LINK V2 doesn't work anymore

  • May 15, 2026
  • 3 replies
  • 224 views

I have created a firmware for a STM32L010F4Px microcontroller.
I was able to Connect and Download Firmware by using ST-LINK V2.

For some reason, I can't connect to the MCU at the moment by using CubeProgrammer + ST-LINK V2.

Instead, I can connect/debug my microcontroller by using a SEGGER J-Link Ultra+ + J-Flash tool.
The log from CubeProgrammer doesn't give me much details:


13:28:34 : UR connection mode is defined with the HWrst reset mode
13:28:34 : ST-LINK SN : 37FF71064E573436D2C11443
13:28:34 : ST-LINK FW : V2J47S7
13:28:34 : Board : --
13:28:34 : Voltage : 3.28V
13:28:34 : Error: Unable to get core ID
13:28:34 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

Best answer by paraschivescue

I have solved the mystery.
The problem was a wire that was no longer making good contact between ST-LINK v2 debugger and my development board on which the microcontroller is soldered.
Thank you all for your involvement and help! 
Have a good day!

3 replies

AScha.3
AScha.3
Super User
May 15, 2026

Try in CubeProgrammer with reset : software   setting.

"If you feel a post has answered your question, please click ""Accept as Solution""."
P
paraschivescueAuthor
Associate
May 18, 2026

I have tried all options including Software Reset but without any success:
13:26:09 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits
13:26:35 : UR connection mode is defined with the SWrst reset mode
13:26:35 : ST-LINK SN : 37FF71064E573436D2C11443
13:26:35 : ST-LINK FW : V2J47S7
13:26:35 : Board : --
13:26:35 : Voltage : 3.28V
13:26:35 : Error: Unable to get core ID
13:26:35 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

mƎALLEm
mƎALLEm
Technical Moderator
May 18, 2026

@paraschivescue ,

Any low power used in the application you've already uploaded?

Look at this post. Use "Power down" mode.

 

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
    Andrew Neil
    Andrew Neil
    Super User
    May 18, 2026
    @paraschivescue wrote:

    I was able to Connect and Download Firmware by using ST-LINK V2.

    For some reason, I can't connect to the MCU at the moment by using CubeProgrammer + ST-LINK V2.

    So what changed?

    • Something in your firmware ?
    • Something in your hardware setup ?
    • Tool update(s) ?
    • Other ?

     

    @paraschivescue wrote:

    Instead, I can connect/debug my microcontroller by using a SEGGER J-Link Ultra+ + J-Flash tool.
    The log from CubeProgrammer doesn't give me much details:

    Is that using the exact same cable & connections ?

     

    Is it a genuine ST-Link ?

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

    Can it connect to any other target(s) ?

    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.
    P
    paraschivescueAuthorAnswer
    Associate
    May 21, 2026

    I have solved the mystery.
    The problem was a wire that was no longer making good contact between ST-LINK v2 debugger and my development board on which the microcontroller is soldered.
    Thank you all for your involvement and help! 
    Have a good day!

      Terms & ConditionsAccessibility statement