STM32 STM32F103C6T6A Bug report

[khatus]

I am trying to program STM32 blue-pill board with STM32F103C6T6A  microcontroller and using STM32CUBE IDE. But nothing is able to upload the program to the microcontroller. When trying to upload the program, the following error messages are showing. Is there anyone in this forum? Who has done blue-pill board programming using STM32F103C6T6A  and STM32CUBE IDE before? What is the problem here? How to resolve this problem?

Here is my bug report
*******************(*)********************************************

[STTwo-32]

Hello @khatus and welcome to the ST Community :smiling_face_with_smiling_eyes:.

The Blue Pill is not an ST product, and the chip on it will (almost) certainly not be genuine. So, can you please switch to one of our STM32 official boards.

Best Regards.

STTwo-32 

[Tesla DeLorean]

Not sure this is a "Bug Report" as much as an "Inability to Use Report"

ST doesn't support boot-leg ST-LINK equipment.

You'd do better with a NUCLEO-F103 board at a first excursion.

The ST-LINK might also generally want a connection to NRST so it can gain control of the part.

You could perhaps try STM32 Cube Programmer to check / erase the part, removing any loader or existing code that may be running on the board.

For LINUX you might have to free-climb your technical support.

It looks to get initial connectivity so you might look at the BOOTx jumpers, or keeping the speed of the connection down, say 1 or 2 MHz rather than 8 MHz

You don't show your ST-LINK/V2 nor it's connectivity to your board. DuPont jumper wires can be very lose and intermittent.

[Karl Yamashita]

Since you're using OpenOCD, you should be contacting them for support on their software.

In the mean time just use ST-LINK GDB Server as the debug probe