Blue Pill (STM32F103C8T6) – “No STM32 target found” in STM32CubeIDE & STM32CubeProgrammer

[Bharath_5]

Hi Everyone,

I am facing an issue where my Blue Pill development board (STM32F103C8T6) is not being detected by ST-LINK V2 when using either STM32CubeIDE or STM32CubeProgrammer.

Both tools consistently show the “No STM32 target found” error message. I have two Blue Pill boards and two ST-LINK V2 programmers, and I am facing the same issue on both setups, which makes me believe it’s not a wiring or hardware fault on a single unit.

My Hardware Setup:

• Boards tested: 2 × Blue Pill (STM32F103C8T6)

• Programmers tested: 2 × ST-LINK V2 (Firmware version: V2J34S7)

• Target voltage: ~3.1V (as detected by STM32CubeProgrammer)

• Connections:

  • 3.3V → VCC

  • GND → GND

  • SWDIO → SWDIO

  • SWCLK → SWCLK

Steps Tried:

1. Verified all SWD wiring and signal continuity using a multimeter.

2. Tested both “Hardware reset” and “Software reset” modes in STM32CubeProgrammer.

3. Updated ST-LINK firmware to the latest version (V2J34S7).

4. Switched between multiple USB ports and cables.

5. Verified target power (3.3V stable).

6. Ensured BOOT0 = 0 (Normal boot from Flash).

7. Tried connecting with and without NRST line connected.

8. Reinstalled all ST drivers and software tools.

Despite all these attempts, the target MCU is not detected in either CubeIDE or CubeProgrammer on both ST-LINKs and both Blue Pill boards.

I have tried the above steps then also I cannot resolve this issue, can anyone please help me to resolve this issue.
Thank You

[kaosad]

I suspect the jumper wires are the issue. Test for connectivity or change to another set of wires. Most low-quality jumper wires from China have this kind of problem. 

[AScha.3]

Hi,

>Is the Blue Pill and ST-Link I am using not original?

They are original Chinese products . Thats it.

Question is: are the chips still alive and are they genuine STM F103 ?

So if possible , show good pic of the cpus on blue pill boards.

+

link, where you ordered them (just to see, what they write)

[Andrew Neil]

---

@kaosad wrote:

I suspect the jumper wires are the issue. Test for connectivity or change to another set of wires. Most low-quality jumper wires from China have this kind of problem. 

---

@Bharath_5  It has been known; eg,

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693#:~:text=Be%20particularly%20wary%20of%20solderless%20breadboards%2C%20cheap%20%22dupont%22%20style%20headers%2C%20etc%3A

See also: 

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

How to solve debugger connection issues.

[Bharath_5]

Hello @AScha.3,
Thank you for your response. I really appreciate your time and support.

Close-up photo of the STM32F103C9T6 Micro-controller you said for and below is the purchase link from where I have purchased the Blue pill and ST-Link V2.
Blue Pill Link:  https://robu.in/product/stm32f103c8t6-minimum-system-board-microcomputer-stm32-arm-core-board/

ST-Link V2: https://robu.in/product/st-link-v2-programmer-for-stm8-and-stm32/

[Andrew Neil]

---

@Bharath_5 wrote:

ST-Link V2: https://robu.in/product/st-link-v2-programmer-for-stm8-and-stm32/

---

As already noted, that is not a genuine ST-Link - it's a clone.

And, as noted in that link, beware that the pinouts can vary.

[mfgkw]

> ST-Link V2: https://robu.in/product/st-link-v2-programmer-for-stm8-and-stm32/

This is not a ST-Link, even when labeled so. It is a commonly sold bad clone. You might use it if it works or forget about it if it does not work (which is obviously the case). You might use the housing for something or even reprogram the board for something useful (if you open it and connect to its SWDL pins using a real ST-Link).

(As far a s I know: Some time ago they worked because they where flashed with something like the ST firmware and got updated silently with latest ST firmware when used in CubeIDE. But at some point the automatic update did not happen anymore [maybe ST stopped it intentionally - who knows] and now the "mini" clones are useless. IIRC I have one in my drawer which got such an update a long time ago.)

A real ST-Link v2 looks like this: https://www.mouser.de/ProductDetail/STMicroelectronics/ST-LINK-V2?qs=H4BOwPtf9MC1sDQ8j3cy4w%3D%3D

Do yourself a favour and pay ~20 bucks for a ST-Link from ST and stop wasting your time.

Or I can offer you my old mini clone for only 10$...

[Andrew Neil]

---

@mfgkw wrote:

Do yourself a favour and pay ~20 bucks for a ST-Link from ST and stop wasting your time.

---

Or get an ST Nucleo-F103 board,  which gives you both a genuine STM32 and a genuine ST-LInk - all for  ~ 10 bucks!

At least, get yourself started with a Nucleo - then, when you're familiar with the product and the tools, you'll be better equipped to with issues from possible fakes & clones ...

[mfgkw]

> Or get an ST Nucleo-F103 board,  which gives you both a genuine STM32 and a genuine ST-LInk - all for  ~ 10 bucks!

Even better: the ST-Link on a NUCLEO board offers a virtual COM port, which the external ST-Link does not.

[Andrew Neil]

@Bharath_5  Another plus for the Nucleo is that its ST-Link is already connected to the target - so there's no risk of poor or incorrect wiring!

---

@mfgkw wrote:

Even better: the ST-Link on a NUCLEO board offers a virtual COM port, which the external ST-Link does not.

---

True - neither the genuine ST-Link V2 nor the clones offer a VCP.

The ST-Link V3MINIE does have VCP. It costs ~ 10 bucks.

The STLINK-V3MINI (without the 'E') also had VCP. It's now obsolete, but you might be able to find old stock.

Other ST-Link V3 models are available with advanced features;  obviously, they cost more. Full details of the whole range here:

https://www.st.com/en/development-tools/hardware-debugger-and-programmer-tools-for-stm32/products.html

[AScha.3]

Hi,

from the links -> board comment:

> This is a clone, so it wont work with debug mode in stm32CubeIDE. Otherwise working fine

> priyammascharak2002 – January 5, 2024

So we can assume: big chance, to have a cpu not by STM on the board.

But anyway , we should get a connection in CubeProgrammer, even if it might show "wrong" chip ID .

(Only debug mode  in IDE then not possible.)

You have a scope ? Then check, what happens on pill board at SWD + SWC lines, when click >connect< in CubeProgrammer.