Detecting Fake BluePills - BEWARE

[olivier.jan]

@PhilC Out of interest I tried that diagnostic software after @olivier.jan suggested it, and it didn't work at all for mine, again casting doubt on mine despite Blinky working.

It seemed to flash ok, but then didn't do what was suggested it should when I followed the instructions. I'm interested to see how others fare with it.

Last week, after the discussions here I tried flashing again and i managed to get the test software running on 2 out of 3 bluepill I had in stock. Just one thing as it took me a few minutes to get it to work: the software doesn’t display anything, not even the menu, before you press « Return » in the serial console.

[rubber_jonnie]

@PhilC Out of interest I tried that diagnostic software after @olivier.jan suggested it, and it didn't work at all for mine, again casting doubt on mine despite Blinky working.

It seemed to flash ok, but then didn't do what was suggested it should when I followed the instructions. I'm interested to see how others fare with it.

Last week, after the discussions here I tried flashing again and i managed to get the test software running on 2 out of 3 bluepill I had in stock. Just one thing as it took me a few minutes to get it to work: the software doesn’t display anything, not even the menu, before you press « Return » in the serial console.

I followed the instructions as per BluePill diagnostics, but had no results. I may try again today, if I get anything this time I'll post here.

[BrettRogersUK]

Hi All,

I've just tried this (https://mecrisp-stellaris-folkdoc.sourc ... 1.640.html) on my bluepill board that I sent to @rubber_jonnie to test. I've also tried it on the spare one that I have here.

The results of the bluepill I sent to @rubber_jonnie to test are below. I run a linux system and the blue pill was detected when plugged in via usb cable to the blue pill itself (No serial device or STlink in the middle just a straight connection from bluepill to laptop). Results are below:

===========================================
Bluepill Diagnostics V1.640 - GPL3 Licensed
===========================================
h - test for Hidden second 64kb flash block: 0x10000 - 0x1FFFF - PASSED

f - how much Flash is declared in the Flash Size Register ?
131072 flash is declared in the flash size register at 0x1FFFF7E0

d - Print DBGMCU_IDCODE
DBGMCU_IDCODE [@ 0xE0042000] = 0x20036410

a - STM32F103C8T6 Authenticity test, don't use with SWD/JTAG.
STM32F103C8 Authentication failed on one or more tests:______________________________
FAIL - Declared flash not 65536
FAIL - DBGMCU_IDCODE is readable with no SWD/JTAG Connected
PASS - Second 64KB flash block verified
PASS - JDEC Manufacturer id IS STMicroelectronics

j - Jdec manufacturer id
Jdec Contunation Code: 0x00
Jdec Identity Code: 0x20
Jdec Manufacturer id: STMicroelectronics

The spare blue pill I have here (the one I got from eBay) isn't recognised when plugging in the usb cable from the bluepill to the laptop so I am unable to test even though the BIN file was uploaded both with the ST Link v2 device and also through USB serial.

The blue pill I sent for testing shows up on my system as a STMicroelectronics Virtual COM port but I think the results above show that the chip is not a genuine STM32F103C8T6 but it is however a genuine STM chip according to the manufacturer ID test just not sure which one as it has clearly been rebadged/remarked.

Hopefully my two IC's I brought from RS Components will show up tomorrow and I can get the chips swapped and see what happens. I've got nothing to lose really if they don't end up working.

[rubber_jonnie]

Hi All,

I've just tried this (https://mecrisp-stellaris-folkdoc.sourc ... 1.640.html) on my bluepill board that I sent to @rubber_jonnie to test. I've also tried it on the spare one that I have here.

The results of the bluepill I sent to @rubber_jonnie to test are below. I run a linux system and the blue pill was detected when plugged in via usb cable to the blue pill itself (No serial device or STlink in the middle just a straight connection from bluepill to laptop). Results are below:

===========================================
Bluepill Diagnostics V1.640 - GPL3 Licensed
===========================================
h - test for Hidden second 64kb flash block: 0x10000 - 0x1FFFF - PASSED

f - how much Flash is declared in the Flash Size Register ?
131072 flash is declared in the flash size register at 0x1FFFF7E0

d - Print DBGMCU_IDCODE
DBGMCU_IDCODE [@ 0xE0042000] = 0x20036410

a - STM32F103C8T6 Authenticity test, don't use with SWD/JTAG.
STM32F103C8 Authentication failed on one or more tests:______________________________
FAIL - Declared flash not 65536
FAIL - DBGMCU_IDCODE is readable with no SWD/JTAG Connected
PASS - Second 64KB flash block verified
PASS - JDEC Manufacturer id IS STMicroelectronics

j - Jdec manufacturer id
Jdec Contunation Code: 0x00
Jdec Identity Code: 0x20
Jdec Manufacturer id: STMicroelectronics

The spare blue pill I have here (the one I got from eBay) isn't recognised when plugging in the usb cable from the bluepill to the laptop so I am unable to test even though the BIN file was uploaded both with the ST Link v2 device and also through USB serial.

The blue pill I sent for testing shows up on my system as a STMicroelectronics Virtual COM port but I think the results above show that the chip is not a genuine STM32F103C8T6 but it is however a genuine STM chip according to the manufacturer ID test just not sure which one as it has clearly been rebadged/remarked.

Hopefully my two IC's I brought from RS Components will show up tomorrow and I can get the chips swapped and see what happens. I've got nothing to lose really if they don't end up working.

When flashed with the diagnostics mine were not recognised either on Windows or Mac (Same machine, dual OS, intel based). I did try on another Windows machine, but still the USB serial port wasn't recognised at all, and I simply had no way of running the diags. I may try again for a 3rd (Maybe 4th time), see if I missed something.

[PhilC]

@rubber_jonnie @BrettRogersUK the USB serial port is not particularly reliable, I use a program called serial tools on my iMac and it works most of the time with that

[rubber_jonnie]

@rubber_jonnie @BrettRogersUK the USB serial port is not particularly reliable, I use a program called serial tools on my iMac and it works most of the time with that

I have that on my Macs, the USB device does not appear in the list of ports and while detected on Windows it is unrecognised. I haven't tried on my M1 Macbook Pro yet so will try.

EDIT: I tried on my M1 Mac, and a Windows 7 machine. I get no USB serial detection on the Mac, Windows 7 is like Windows 10, the device is detected but is not recognised.

I don't have a Linux machine I can test on at the moment, but I can probably sort that out, but I'm not hopeful.

I suspect my boards are probably fake, but visually pretty good, and good enough to run Blinky, but the USB ports don't work, even with downloaded virtual com port drivers from ST.

[BrettRogersUK]

Well I'm pleased to announce that the blue pill boards I ordered from America turned up today and I loaded one of them with the bluepill diagnostics software as in my last post and it turns out that these pass all the tests including STM32F103C8T6 authentication.

I had no problems connecting to it with ST link and STCubeProgrammer software and it downloaded the software without problems.

Looking at the markings on the chip on these boards they appear to be almost in exactly the same format as the chips I got from RS components with the F being at the end of the first line printed STM32F instead of starting on the second line.

These are the boards I got:
HiLetgo 2pcs STM32F103C8T6 ARM STM32 Minimum System Development Board Module STM32F103C8T6 Core Learning Board for Arduino https://amzn.eu/d/8k3vSZk

[BrettRogersUK]

Just a quick update.

The hiletgo boards that I got from America (link in my previous post) work flawlessly.

They pass all the diagnostics and the blinky as well.

I also swapped a chip on one of the boards that didn't work in my project. I bought some genuine chips from RS components and desoldered one if the suspect ones from one of my BluePill boards and soldered the genuine one on.

To my surprise it worked a treat. The board that didn't work before now works flawlessly in my project. So the chip that was on my board before was definitely NOT an STM32F103C8T6 or it was and was a defective chip.

So just thought I'd post this along just for more info on these so called fakes and clones.

[rubber_jonnie]

Just a quick update.

The hiletgo boards that I got from America (link in my previous post) work flawlessly.

They pass all the diagnostics and the blinky as well.

I also swapped a chip on one of the boards that didn't work in my project. I bought some genuine chips from RS components and desoldered one if the suspect ones from one of my BluePill boards and soldered the genuine one on.

To my surprise it worked a treat. The board that didn't work before now works flawlessly in my project. So the chip that was on my board before was definitely NOT an STM32F103C8T6 or it was and was a defective chip.

So just thought I'd post this along just for more info on these so called fakes and clones.

Nice to know, thanks Brett. I may order a couple from the link you shared and see if it fixes my BlueSCSI issues.

[elterwater]

In the end, I ended up taking a punt on an AliExpress seller who seems to openly offer the CH chip variant, "Original" STM32 chip and a "China copy" variant of the boards.

I ordered a couple of the "Original chip" boards out of curiosity and they have arrived with STM32F103C8T6 chips seemingly on board.
Amusingly, they're called the "All goods are freeshipping Store" but neglect to mention it's only free shipping over £8...

They also all seemed to be pre-flashed with a blinky test as the LED was flashing when I first plugged it in. I was able to flash these with both ST32cubeIDE with my own blinky test using 2 second delays, and then flashed the bluepill diagnostics onto it using the ST-LINK utility.

Code: Select all

===========================================
Bluepill Diagnostics V1.640 - GPL3 Licensed
===========================================
h - test for Hidden second 64kb flash block: 0x10000 - 0x1FFFF:  PASSED
f - how much Flash is declared in the Flash Size Register ?
d - Print DBGMCU_IDCODE
a - STM32F103C8T6 Authenticity test, don't use with SWD/JTAG.
j - Jdec manufacturer id
e - Extra menu
q - Quit menu, enter the Forth command line
m - Main menu


Please wait, testing Flash ......

65536 flash is declared in the Flash size register at 0x1FFFF7E0

DBGMCU_IDCODE [@ 0xE0042000] = 0x00000000

STM32F103C8 authentication PASSED all these tests:
----------------------------------------------------
PASS - Declared flash = 65536 Bytes
PASS - DBGMCU_IDCODE is NOT readable without SWD/Jtag connected
PASS - Second 64KB flash block verified
PASS - JDEC manufacturer id IS STMicroelectronics


Jdec Continuation Code: 0x00
Jdec Identity Code: 0x20
JDEC manufacturer id: STMicroelectronics

Apologies for the moire pattern, couldn't be bothered to rustle up a micro sd from anywhere.

I think this all means that they're all ok?

IMG20230821160211.jpg

IMG20230821160254.jpg