Blue Pill STM32F103C8T6 not detected via ST-Link – connection/programming issue

[DanielDSouza]

Hello everyone,

I’m working with an STM32F103C8T6 (Blue Pill) development board and facing an issue while trying to program/debug the MCU using ST-Link V2.

Board used:
https://robocraze.com/products/stm32f103c8t6-arm-development-board

Issue details:

STM32CubeProgrammer / STM32CubeIDE does not consistently detect the target

Sometimes shows “No target connected” or fails during connection

Tried SWD mode with NRST connected

BOOT0 is set to 0 (Flash mode)

Power supplied via USB (5V) and also tested with external 3.3V

Checked SWDIO, SWCLK, GND continuity

I’m not sure if this is related to board configuration, clock settings, or ST-Link connection parameters. I’d appreciate guidance on:

Recommended ST-Link connection settings for STM32F103C8T6

Any known issues with Blue Pill boards (pull-ups, reset circuit, USB power, etc.)

Whether enabling connect under reset is mandatory for this MCU

I’m still getting familiar with the forum and STM32 ecosystem, so apologies if I’ve missed something obvious. Looking forward to learning from the community and thanks in advance for any help.

[mƎALLEm]

Hello @DanielDSouza and welcome to the ST community,

Please bear in mind that STM32F103 blue Pill most probably contains a counterfeit chip.

Also, you need to check your STLINK. It could be not a genuine product:

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

[mfgkw]

Hi Daniel,

Welcome here!

The known issue with blue pill is that nearly all of them (or really all?) are faked meanwhile and are not equipped with an original STM MCU.

Use a more reputable board from a more trustworthy dealer than Ali* or temu or something like that. You probably have more fun with NUCLEO board or something like that.

Don't waste your time...

[Andrew Neil]

As the others have said, Blue Pill is not an ST product, and most likely does not contain a genuine STM32.

Therefore it (probably) is not supported by STM32CubeIDE - see:

https://community.st.com/t5/others-hardware-and-software/stm32programmer-is-not-connecting-with-blue-pill-device/m-p/874208#M33304

You will find many, many threads here with people suffering issues due to using Blue Pills; eg,

• https://community.st.com/t5/others-hardware-and-software/configuring-uart-on-stm32f103c8t6-bluepill-kills-connection-to/m-p/668641/highlight/true#M32234 
• https://community.st.com/t5/stm32-mcus-boards-and-hardware/error-in-initializing-st-link-device-reason-18-could-not-verify/m-p/314096#:~:text=It%20was%20100%25%20due%20to%20there%20being%20a%20counterfeit%20chip%20on%20my%20blue%20pill%20board

Do yourself a favour and at least start on a genuine ST board - such as a Nucleo-F103RB.

That way you get:

• Known-good hardware, with a genuine STM32F103
• A genuine ST-Link, all connected and ready to go
• Support
• Documentation
• Loads of ready-to-go examples
• etc, etc

That will let you get familiar with the tools and the product in a reliable, supported environment.

After that, armed with that understanding &experience, you will be better equipped to venture into the "Wild West" of Blue Pill land...

PS:

Here's a tool to identify what chip you do actually have:

https://mecrisp-stellaris-folkdoc.sourceforge.io/bluepill-diags-v1.640.html#diags-1-640

See also: https://hackaday.com/2021/06/23/test-your-blue-pill-board-for-a-genuine-stm32f103c8-mcu/

And: https://hackaday.com/2020/10/22/stm32-clones-the-good-the-bad-and-the-ugly/ 

And: https://github.com/keirf/Greaseweazle/wiki/STM32-Fakes#rogues-gallery

#BluePillFakeSTM32

[gbm]

Try connecting with BOOT0 set to 1. If it doesn't connect - it's very likely the chip is not 100% STM32F103 compatible.