Unable to Get Core ID - No STM32 Target Found - ST-LINK V2 Issue

[Visu]

Hello ST Community,

I am facing an issue while trying to connect to my STM32 MCU using STM32CubeProgrammer and ST-LINK V2.

Here are the details:

• ST-LINK SN: 50FF73064977875712192367

• ST-LINK Firmware Version: V2J45S7

• Error Message:

  Error: Unable to get core ID
  Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

• Voltage Detected: ~0.48V

• Target Board: [Please mention your MCU and board name here, e.g., STM32F103C8T6, custom board]

What I have already tried:

• Verified SWD wiring (SWDIO, SWCLK, GND, NRST)

• Verified power supply to MCU (currently measured at 0.48V, which is quite low)

• Tried "Connect Under Reset" option

• Ensured BOOT0 is low

• Firmware of ST-LINK is updated

• MCU is externally powered (attempted both self-powered and ST-LINK powered)

My Doubts:

• Is the low voltage (0.48V) the reason ST-LINK cannot detect the MCU?

• Could this be a Debug Authentication lock issue? (Although my MCU is [mention family, e.g., STM32F1] which I believe doesn't use Debug Authentication.)

• Is it possible that the MCU is in a protected or corrupted state? How can I recover it?

Request: Please guide me on how to recover or reprogram my STM32 MCU.
If any additional settings or hardware tweaks are required, kindly suggest.

My connection is 

Thank you!

VISHWJEET SINGH

[Andrew Neil · Accepted solution]

---

@Visu wrote:

• Voltage Detected: ~0.48V

---

So there is no power on your target board!

You need to separately supply power - the ST-Link does not supply power.

Also, the board you're using appears to be a "Blue Pill" - this is not an ST product and will (almost) certainly not have a genuine STM-32 on it.

[Visu]

@Andrew Neil 

Thank you for your quick response!

Yes, I understand — and I have already tried supplying separate 3.3V power to the board.
Unfortunately, even with external power, the issue remains the same.

Regarding the point that this "Blue Pill" may not have a genuine STM32, I appreciate your clarification.
It seems that if the chip is not genuine, then there may not be any reliable way to recover or connect to it.

I will consider sourcing a verified genuine STM32 board for future projects.

Thanks again for your support!

[Peter BENSCH]

As @Andrew Neil mentioned, Blue Pills are not products of STMicroelectronics and also use faked STM32. ST resources are only dedicated to supporting genuine ST products. We are not committed to ensuring that clones/fakes products work properly with the firmware we provide.

This thread will now be locked. However, if you face difficulties while using genuine ST products, we’re here to assist you. Please feel free to start a new thread, and our team, along with community members, will be ready to help you with any issues/questions you encounter.

Regards
/Peter