Stm32F103C8T6 (Blue Pill)

[Asifur]

I have tried to programme and reset stm32F103C8T6 (Blue Pill) via different st-links, uart serial bridge via arduino uno with switching the bootloaders boot0 to 1 and also boot1 to 0. But still it cannot connect the the stm32cubprogrammer gives an error "activating device Ko”. Is it a driver issue like the esp8266 has, that worked with the previous version of driver that I hads to install manually. Is it the problem with blue pill or something else?

Can anyone suggest me the solution ?

[AScha.3]

Did it work already?

Or is this your first attempt to get it working?

So try to connect in CubeProgrammer, st-link and blue pill, Boot 0 +1 lo.

Connection mode: normal, software reset.

Try.

[Asifur]

I have made projects with the same blue pill. It worked properly but one problem I faced that the stm32 had been locking with the previous code agian abnd again. So i had to reset the chip each time through cubeprogrammer then upload a new code. But this time it is not connecting anyways.

 

”CubeProgrammer, st-link and blue pill, Boot 0 +1 lo.

Connection mode: normal, software reset."  done but no improvement.

[AScha.3]

Ahhh ok, so it was working before.

So you damaged it?

Or wrote something in your program, that stops SWD debug access from working.

You could try:

Set CubeProgrammer to hardware reset and connect: under reset, maybe set reset on Blue pill board, if your st-link doesn't work with setting reset in hardware.

Or: set Boot 0 high, try to connect in CubeProgrammer with dfu mode, but need USB to serial adapter for this, connect to Rx TX of Blue pill STM 32f103 . 

[Asifur]

Yeah I tried it also. But no expected result. Blue pill cannot be connected. I think the board is damaged somehow because na matter how many ways I try, it dessapoints me.

[mƎALLEm]

Hello ​@Asifur and welcome to the ST community,

The product you are using (Blue Pill) is a clone of a genuine ST product. ST resources are only dedicated to supporting genuine ST products including the community. We are not committed to ensuring that clones/fakes products work properly with the firmware and tools we provide.

To get the support you need, please contact the third party you purchased this product from.  

For assurance of buying authentic ST products, we recommend purchasing exclusively through our official distributors, which you can find listed here: ST Official Distributors.  

Thank you for your understanding.

[Andrew Neil]

As already noted, the Blue Pill is not an ST product. And, most likely, it  does not have a genuine STM32.

Also, are your “different st-links” genuine ?

 

ST tools are not guaranteed to work properly - or even at all - with fake/clone chips and/or ST-Links.

 

 

[AScha.3]

Ok, now we know: surprisingly not all boards on earth are produced by STM. 

But still here in STM forum we try to help people with -probably- STM chips, that dont work as they should.

On demo-boards by STM and also on custom boards - right ?

And the OP wrote: It worked properly… 

It therefore seems more like an excuse to avoid helping, as long as it hasn't been conclusively proven that an STM chip isn't the one causing the problems here.

Here, in this case, it (It worked properly… , but now no response at all)  might indicate, the hardware is damaged now. 

So ​@Asifur , you should try another (new) blue pill or if no more pills around, buy a cheap nucleo board and you know, this can work as long as you dont damage the hardware. (usually by overvoltage or static discharge, so handle with some care.)

[mƎALLEm]

BluePills may contains (unlikely) a genuine ST chips but most probably they don’t. As we are not sure they are genuine chips we assume they are fake/clone. This community is a ST resource that should be used for ST products. Sorry, this is our policy for these “colorfull” boards especially for BluePill containing that STM32F103C8T6 part number.