STM32F103C8T6 Bluepill Issue with CubeIDE

kiranraj_k_r · ‎2025-12-30

Hi Team,

I was working on STM32F103C8T6 Bluepill board. I was using this board with ST-LinkV2 to connect with CubeIDE. When i tried to flash a sample LED blink program via CubeIDE, it gave an error saying 'Target not found'. But at the same time i was able to connect this board via cube programmer using same ST-Link and write sample LED code into the board.
I have also tried to put the board into DFU mode by changing BOOT0 to 1 and connected with a usb cable to my linux machine. when i tried 'lsusb' it didnt show DFU mode status of the board. Please help me to resolve this issue.

Andrew Neil · ‎2025-12-31

welcome to the forum.

Please see How to write your question to maximize your chances to find a solution for best results.

Note that "Blue Pill" is not an ST product, and likely contains a fake STM32.

Also, are you using a genuine ST-Link, or a clone/fake?

How to recognize a genuine ST-LINK/V2 versus a cloned one. TL;DR: if it looks like a USB memory stick, it's a clone.

@kiranraj_k_r wrote:
When i tried to flash a sample LED blink program via CubeIDE, it gave an error saying 'Target not found'.

Please show the full error message, and log.

It is common that CubeIDE will refuse to work with clone chips & ST-Links; CubeProgrammer may be more forgiving.

What versions of IDE & Programmer are you using, and on what Host?

PS:

ST's NUCLEO-F103RB gives you:

A genuine STM32
A genuine ST-Link
Actual support
Ready-to-go examples
etc, etc, ...

I would certainly recommend this as a better option for a beginner and, by the time you've bought a Blue Pill plus separate ST-Link, it may not even be any (or much) more expensive!

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

AScha.3 · ‎2025-12-31

Hi,

In addition to what @Andrew Neil wrote :

1. was the board + st-link working before, or is this first test ?

2. IDE checking for "fake" target, thats almost just other manufacturer of F103-similar chip, CubeProgrammer more "forgiving" , also works with F103-similar chip.

3. show good pic of F103 on bluepill board, if possible .

4. show link, where /what you buyed as bluepill + st-link .

If you feel a post has answered your question, please click "Accept as Solution".

kiranraj_k_r · ‎2025-12-31

I am using genuine ST-Link(photo attached).

Error message from CubeIDE and photo of Bluepill board attached.

I am using CubeIDE Version: 2.0.0 and CubeMX Version 6.16.1 on Linux 22.04.
product I am using : https://robu.in/product/stm32f103c8t6-minimum-system-board-microcomputer-stm32-arm-core-board/issue facing while trying to debug - GDB issue

I am also facing a GBD error while trying to debug

kiranraj_k_r · ‎2025-12-31

I have replied in @Andrew Neil comment with details you have requested for.

Andrew Neil · ‎2025-12-31

@kiranraj_k_r wrote:
I am using genuine ST-Link(photo attached).

Your photo does not match the How to recognize a genuine ST-LINK/V2 versus a cloned one article:

@kiranraj_k_r wrote:

I think that is to be expected with a fake STM32 and/or clone ST-Link.

Again, I would strongly recommend that you at least start with a genuine ST board, so that you can gain familiarity with the product & tools using known-good hardware - without having to worry about all the extra unknowns with fakes/clones.

The forum is littered with people struggling due to the issues of fakes/clones - save yourself the grief!

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Andrew Neil · ‎2025-12-31

@kiranraj_k_r wrote:
I have replied in @Andrew Neil comment with details you have requested for.

Everyone can see all replies - no need for a separate reply.

You didn't answer @AScha.3's question: "1. was the board + st-link working before, or is this first test ?"

Also, "3. show good pic of F103 on bluepill board" means a good closeup of the MCU chip so that we can see exactly what's written on it.

This diagnostic may also help to see what MCU is actually on your board:

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

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

MGogr.1 · ‎2025-12-31

Why do I feel your ST-Link connections are wrong?!
Could you please verify that once.

Andrew Neil · ‎2025-12-31

@Andrew Neil wrote:
@kiranraj_k_r wrote:
I am using genuine ST-Link (photo attached).
Your photo does not match the How to recognize a genuine ST-LINK/V2 versus a cloned one article

@kiranraj_k_r Confirmed here (by @mƎALLEm) that it's not genuine.

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

AScha.3 · ‎2025-12-31

Ok,

so from link to robu .... read the comments, before buy (next time.) :

So its probably a real fake : STM32F103 written on it , but other chip inside.

And your Chinese st-link probably also, thats why IDE telling: could not verfy ST device.

What you could do now:

- for simple test and learning you can make programs with IDE , but flash the clone with CubeProgrammer.

- no debug possible , no connect in IDE

- for better behaviour, debug in IDE etc. , buy a cheap nucleo board (genuine from STM) , like this:

https://robu.in/product/nucleo-f303re/

+ here also the st-link attached, can separate even.

If you feel a post has answered your question, please click "Accept as Solution".