Connecting to BluePill via Serial Port

[xq1xq1xq1]

I am a newborn to this whole side of tech

I am running Windows 11

I have bluepill that I am trying to run the bluepill diagnostics from

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

I am using a STLINKv2 USB clone and flashed the bluepill diagnostics to the bluepill

I am now attempting to connect to the bluepill to run the diagnostics

Initially I tried to use the connection via the STLinkv2 adapter but do not see a new COM port for it (Intel Active MGMT is COM3)

I then thought the mini-usb may be where I need to connect to but also with no joy in connecting or seeing a new COM port

Any idea what I am missing

[Tesla DeLorean]

It looks like that software should present as a USB CDC device, provided the BOOT jumpers are set to run the FLASH software

Should present in Device Manager as "Mecrisp STM32F10x Forth Serial Port" instead of "STM32 BOOT DEVICE" from the System Boot Loader. Check if it finds a device, or needs drivers

[Karl Yamashita]

Maybe you have a Chinese knockoff of the BluePill? 

[xq1xq1xq1]

I was wondering if it is fake 

When I looked at the board in the stmprogrammer I got this:

Device ID: The Device ID 0x410 corresponds to the STM32F103C8T6, which is the chip used in the BluePill board.

Flash Size: The reported flash size is 128k, which matches the expected flash size for the STM32F103C8T6.

CPU: The Cortex-M3 core is correct for the STM32F103C8T6

Is there something else that I can do to verify if it's genuine or not? 

[xq1xq1xq1]

I left the boot0 and boot1 jumpers on 0.

Do I need to make a change on the board?

Thx

[Techn]

First you have to load the new firmware using st-link v2. Then select main flash memory option and plug the board into usb. Check device manager and let us know what does your windows device manager shows. Once the device manager is showing the board, using any serial monitor app to connect to that device as serial. Follow the steps given in the pdf file which is got in the zip folder.

[xq1xq1xq1]

If I understood you correctly, I left Boot0 and Boot1 on 0 to run flash memory.

I flashed the 

I disconnected the STLinkv2 USB Adapter and I connected the bluepill mini-usb to the computer and the power LED lights up.

I still only see the Intel COM Port in Device Manager

I apologize if I am being dense, any ideas?

[Tesla DeLorean]

Would need bluepill-diagnostics-v1.6xx.bin successfully written to the STM32F103

You would expect the Windows ding-dong sounds if the device registers as a USB Device, and then would appear as something in Device Manager, either what you want, or as an "Unknown Device"

The functionality of the third-party software would be under the purview of the developer, not ST

[Techn]

I too tried the diagnostics on my bluepill and there is no output either on usb or uart1, since the source code is not published, we are unable to identify the reason, please ask the owner of the program.

[xq1xq1xq1]

Thanks so much for confirming your experience with the diagnostic firmware. I will table my work with the diagnostic firmware for now. The author suggested using SWDCOM instead of a serial connection. I had trouble compiling and getting SWDCOM to execute on debian. 

I'm trying confirm whether or not my bluepill board is genuine or fake as my project is not behaving as I expect. 

Do you have any suggestions on how to confirm if my chip is genuine or not?