Connecting to BluePill via Serial Port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-11 12:09 PM - last edited on ‎2024-12-17 1:45 PM by Tesla DeLorean
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
Solved! Go to Solution.
- Labels:
-
STM32F1 Series
-
USB
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-19 3:37 AM
Thanks for your guidance. I'll work towards that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-11 12:16 PM
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
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-11 12:22 PM
Maybe you have a Chinese knockoff of the BluePill?
TimerCallback tutorial! | UART and DMA Idle tutorial!
If you find my solution useful, please click the Accept as Solution so others see the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-11 1:46 PM
I was wondering if it is fake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-11 1:47 PM
I left the boot0 and boot1 jumpers on 0.
Do I need to make a change on the board?
Thx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-12 5:58 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-16 11:32 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-16 12:29 PM - edited ‎2024-12-17 1:32 PM
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
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-16 5:27 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-16 5:43 PM
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?
