ST-LINK Cannot Detect Target – NUCLEO-F072RB – “Unable to get core ID” / “No STM32 target found”

[Visu]

Hi,

I am facing an issue while connecting to my board using STM32CubeProgrammer and ST-LINK. I would appreciate any help.

Board: NUCLEO-F072RB
Programmer: ST-LINK (Onboard)
Software: STM32CubeProgrammer
Connection: SWD
ST-LINK Firmware: V2J46M31

Issue Description:
STM32CubeProgrammer is unable to detect the target MCU. It shows errors like:

• Unable to get core ID

• No STM32 target found

• ST-LINK error (DEV_CONNECT_ERR)

Observed Details:

• Target voltage showing around 0.29V

• Connection mode tried: Normal (SWD)

• Reset mode: Software reset

• Speed: Reliable

• Frequency: 4000 kHz

Log Messages (Important Parts):

• Error: Unable to get core ID

• Error: No STM32 target found!

• ST-LINK error (DEV_CONNECT_ERR)

• Error: Problem occurred while trying to connect

What I Already Checked:

• USB cable and port

• Reinstalled STM32CubeProgrammer

• ST-LINK firmware upgrade option checked

• Tried reconnecting multiple times

Questions:

1. Is the low target voltage (0.29V) the reason ST-LINK cannot detect the MCU?

2. Could this be a power supply or hardware issue on the board?

3. Should I try different reset modes (Hardware reset / Connect under reset)?

4. Any recommended debugging steps for this case?

Thanks in advance for your support.

[TDK]

> Target voltage showing around 0.29V

This is not enough voltage to run the chip. Changing the reset mode won't fix this.

Recheck your power settings. These are the defaults to power from USB:

If you haven't changed any settings and the board no longer works, it probably got damaged.

[Imen.D]

Hello @Visu 

I recommend the following article describes tips to fix such errors encountered:

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

Hope that helps!

[Andrew Neil]

---

@Visu wrote:

1. Is the low target voltage (0.29V) the reason ST-LINK cannot detect the MCU?

---

Yes.

As @TDK said, the MCU cannot run at that voltage - therefore the ST-Link cannot communicate with it.

---

@Visu wrote:

2. Could this be a power supply or hardware issue on the board?

---

Yes.

---

@Visu wrote:

4. Any recommended debugging steps for this case?

Check the board's User Manual and schematics:

• make sure you have the board configured correctly
• measure voltages at appropriate points

The fact that CubeProgrammer has the serial number & firmware version shows that it is communicating with the ST-Link.

Therefore power must be reaching the ST-Link.

So something is wrong between the ST-Link/USB and the MCU ...