2026-05-15 3:30 AM
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
Solved! Go to Solution.
2026-05-21 12:48 AM
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!
2026-05-15 4:00 AM
Try in CubeProgrammer with reset : software setting.
2026-05-18 3:28 AM
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
2026-05-18 3:39 AM
@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?
@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) ?
2026-05-18 4:06 AM
Any low power used in the application you've already uploaded?
Look at this post. Use "Power down" mode.
2026-05-21 12:48 AM
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!
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.