Solved

Hi all,This is my first embedded programming project and Blue Pill is my first board to work on. Since I've got some experience in C++, I wish to use that language to make a project for blinking the Blue Pill's LED. Amongst various IDEs out there I picked up STM32CubeIDE because I suppose they both are from a family and they're better to be used together.There are very many tutorials regarding Blinking Blue Pill's LED on the Web, but the problem with all I came across were two things: they all use the C language to program and also a pre-made code for the project. I want to use C++ and write the code myself.After installing the IDE, I created a new STM32 Project called "Blinking LED" and then selected C++ as the target language and I'm stopped there. What I need now is a guidance to conduct me from that point up to the IDE's code editor where I can put my own C++ code for the project to be run on the board.

Hello,i am working for now on a diy project.In this project i am interfacing LoRa SX1278 (SPI), MPU6050 (I2C) and NEO-6M (UART) with the STM32F103C8 (blue pill).All in all it is working but because all this sensors and modules are served in the loop, it is affecting the speed of the µC.I am thinking of using Free RTOS for that purpose.The goal is that every 10 - 15 seconds the STM32 reads  NEO-6M and packs the results in a Buffer to send it with LoRa to the receiver.Would free RTOS be a good idea?Any suggestion is appreciated.Thanks in advance

Hi AllToday I wanted to start working with Bluepill DAC that turn out in STM32CubeIDE there is no DAC peripheral and I was shocked. Does anyone know what the h... is that issue? and how to solve it? I don't like to configure it by myself.

When I try to program my Blue Pill over UART in the Stm32CubeProgrammer it give me this Error message:13:11:23 : Serial Port ttyUSB0 is successfully opened.13:11:23 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1,0, flow-control = off13:11:23 : Activating device: OK13:11:23 : Board : --13:11:23 : Chip ID: 0x41013:11:23 : BootLoader protocol version: 3.013:11:23 : UPLOADING OPTION BYTES DATA ...13:11:23 : Bank : 0x0013:11:23 : Address : 0x1ffff80013:11:23 : Size : 16 Bytes13:11:23 : UPLOADING ...13:11:23 : Size : 1024 Bytes13:11:23 : Address : 0x800000013:11:23 : Read progress:13:11:23 : Data read successfully13:11:23 : Time elapsed during the read operation is: 00:00:00.10613:11:54 : Memory Programming ...13:11:54 : Opening and parsing file: blinky-test-f1-1.5.hex13:11:54 : File : blinky-test-f1-1.5.hex13:11:54 : Size : 12,47 KB13:11:54 : Address : 0x0800000013:11:54 : Erasing memory corresponding to segment 0:13:11:54 : Erasing internal memory sector

HI!I recently purchased some ST products, attempting to program and debug.I initially purchased a STM32 Blue Pill (STM32f103) along with a Mini St-Link V2 (Clone). Then I purchased an STM32F3VE board.I was able to program both boards using ST-LINKV2 (clone) and CubeProgrammer but not to debug via CubeIde, as I understand ST no longer allows debugging via cloned STlink.Wanting to debug I purchased a STLINK-V3minie, but I can't even connect with the CubeProgrammer Software to both cards. I have checked the connections over and over again and they are correct.I changed the firmware version of the Minie, believe me I've tried them all. I checked with the oscilloscope whether the CLOCK/Data are present, and everything is OK.What do you think about it? Is it possible that the cards have cloned chips and therefore the minie doesn't connect? If, yes, how can I check from CubeProgrammer whether they are genuine ST or not? Looking at the ICs case/mark they look Genuine.Thanks in advance 

I would like to know whether the stm32f103c8t6(Blue pill) can be supplied using a 5v source through the regulator ( 5V pin); I've seen a lot of people indicate that it was possible but the datasheet clearly says that the maximum voltage the regulator can take is 4.0v. In addition, I've read that the regulator is disabled in stop mode, does that mean that I cannot use my external 5v source in while in stop mode? and is the onboard usb regulator the same one used on the 5v pin? ( I've only seen one regulator in the blue pill schematic) Image to see what portion of the datasheet I'm referring to :

Hello!I have Blue Pill board and ST-LINK/V2 programmer. When I open STM32CubeProgrammer on Windows 10, my ST-LINK is detected properly but nothing happens when clicking on connect. No error messages, nothing. I can click all day and nothing. At the same time if I connect my ST-LINK to an Linux machine, STM32CubeProgrammer connects to my Blue pill without any problems. I have found couple of threads on Google with similar issue, but they seem outdated and are not working for me. I have tried re-installing JRE multiple times, but nothing changes. I hope you guys could help me, as I am really willing to start learning STM32.

I'm not sure how I did it, but my Blue Pill STM32F103C8T6 doesn't respond to st-info --probe any more. This has happened twice in a row with identical devices. It seems that if I Ctrl-D out of GDB (an old bad habit) the device seems to brick itself and won't respond to programming or STLINK probes. I'm using an STLINK/V2 programmer attached to the SWIO/SWCLK pins. I can still set the BOOT0 pin to boot the system ROM bootloader and get proper responses from the STLINK/V2 programmer. So, I'm wondering where I can download the original flash bootloader and what address I'd need to use with st-flash to flash it back onto the device so that I can return to a nice wholesome flash bootloader.

..

So I've been trying for a while to get the I2C1 peripheral working for communicating with the AM2320 humidity/temperature sensor but for some reasons I have not yet broken down, it never seems to reach it. I used CubeMX to initialize the peripherals and the main.c code is as it follows:#include "main.h"I2C_HandleTypeDef hi2c1;void SystemClock_Config(void);static void MX_GPIO_Init(void);static void MX_I2C1_Init(void);int main(void){ HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_I2C1_Init(); HAL_GPIO_WritePin(LED_BUILTIN_GPIO_Port, LED_BUILTIN_Pin, 1); while (1) {  HAL_GPIO_WritePin(LED_BUILTIN_GPIO_Port, LED_BUILTIN_Pin, 1);  for(int i = 0; i < 255; i++)  {   if(HAL_I2C_IsDeviceReady(&hi2c1, i, 1, 10) == HAL_OK)   {    HAL_GPIO_WritePin(LED_BUILTIN_GPIO_Port, LED_BUILTIN_Pin, 0);   }  } }}void SystemClock_Config(void){ RCC_Os

Hello,I made a project using a blue pill. It works when is powered through st-link (3,3V).When I power this board from two AA batteries (~3V), the board does nothing until I press the reset button.An STM32F103 should work from 2 to 3,6 V, according to its datasheet, or I need to adjust something?

ST-Link V2, STM32F103C6T6A "blue pill", trivial program (version of blink LED), after pushing code to CPU (using STM32CubeIDE 1.9.0 and a current-firmware official ST-LINK V2), the board(s) appear "bricked" and don't respond to ST-LINK V2.I am in need of a way to determine if the boards are scrap, or can be recovered from this condition.Upon receipt (of the "blue pill" boards and the ST-LINK V2 programmer), I pre-tested the "blue pill" boards with both an official ST-Link V2 with a fresh from the package board (which comes with a blink-the-LED program). I can read out the 32768 bytes of flash memory, save to file, do a full erase, and rewrite the device with the previously saved (from the factory) 32768 byte image (which just blinks the LED on GPIOC bit 13.)This is where the problem began:Wrote my own version of "blink the LED" to verify I could complete the write-build-program cycle with STM32CubeIDE (using the official ST-Link V2 as the firmware in the clone ST-LINK can't be updated)

Hi all,after working with Arduinos for some time now, I am currently trying to get stuff to work using a blue pill (stm32f1). I've managed to get some code working that turnes on the builit-in LED when a button is pressed using the Arduino IDE.With that milestone achieved, I am now trying to get the STM32 to communicate with my 64bit win7 PC via serial / USB. When I plug in the STM, no connection is established. The win device manager shows an "unknown device" and under details error code 43 is given.I've searched the net for quite some time now but haven't found a solution to my problem. I've tried a couple of drivers from this website, but noting worked. I added a 1.8kOhm resistor between PA12 and 3V3 to compensate for the wrong resistor on most blue pills (10kOhm insted of 1.5kOhm)Maybe some of you can point me into the right direction. Should the blue pill connect automatically for serial communication via USB like other µ-controller / USB devices? If no: What do I have to do to m

I am using the STM32F103C8 (blue Pill) and have been having lots of troubles with reading multiple channels on ADC1. Here is my init code using firmware 1.7: ADC_ChannelConfTypeDef sConfig = {0};   /* USER CODE BEGIN ADC1_Init 1 */   /* USER CODE END ADC1_Init 1 */ /**Common config */ hadc1.Instance = ADC1; hadc1.Init.ScanConvMode = ADC_SCAN_ENABLE; hadc1.Init.ContinuousConvMode = ENABLE; hadc1.Init.DiscontinuousConvMode = DISABLE; hadc1.Init.ExternalTrigConv = ADC_SOFTWARE_START; hadc1.Init.DataAlign = ADC_DATAALIGN_RIGHT; hadc1.Init.NbrOfConversion = 4; if (HAL_ADC_Init(&hadc1) != HAL_OK) { Error_Handler(); } /**Configure Regular Channel */ sConfig.Channel = ADC_CHANNEL_0; sConfig.Rank = ADC_REGULAR_RANK_1; sConfig.SamplingTime = ADC_SAMPLETIME_1CYCLE_5; if (HAL_ADC_ConfigChannel(&hadc1, &sConfig) != HAL_OK) { Error_Handler(); } /**Configure Regular Channel */ sConfig.Channel = ADC_CHANNEL_1; sConfig.Rank = ADC_REGULAR_RANK_2; if

Hi, I´m trying to communicate two blue pills between them using CAN bus, but when I try to run it, it doesn´t even finish the start up, because I tried to use a blink program selecting the CAN in the .ioc and not using it and doesn´t work.Does anyone knows why does this happen?

HelloI came across with this board (STM32 Blue Pills) and instantly got many questions.1) I couldn't find it on CubeMX and could you please confirm that it is not present on CubeMX or it is just clumsy me?2) It seems that MPU is STM32F103xx which I believe belongs to STM32F103 Nucleo64 board. Can I use CubeMX to generate templates for say Keil and then compile code and upload to MCU ?3) It seems to utilize general purpose USB. However on STM32F103 Nucleo board does not have it, it only has ST-Link JTAG usb for programming only that cannot be used or say HID or CDC or whatever. But folks there utilize USB functionality of the Blue Pill. What am I missing ?

Hi everyone,beginning the embedded systems journey has been fun, thanks to starting out with Nucleo board STM32L412RB-P. It's got an on board debugger (like any other nucleo board) which certainly abstracts the hardware nitty gritties required to setting up. Again, thanks to the rich ST community, one could find tonnes of resources and help readily available when stuck. I decided to take a little step further by purchasing a bluepill (original) and an STLink V3 SET (original). To my surprise, there hasn't been useful resources (in my opinion) on how to set these two up. Wherever the bluepill is mentioned, some stlink V2 (original or clone) follows. So I'm turning to this rich ST community, as trivial as this may seem, help me out of this quagmire. How do I do a simple debug, flash etc on my bluepill using STLink V3 SET using SWD. Thanks

Hello,I'm developing a USB bootloader for the STM32F103C8T6 Blue Pill (64KB / 128KB). I've seen many protocols and methods for doing this. Can you suggest the best method? I want to program the STM32F103C8T6 Blue Pill with STM Cube IDE software via USB.

I have an STM32F103C8T6 Blue Pill board, and I'm trying to get the RTC to function correctly when Vdd is removed. However, when I disconnect Vdd, the RTC doesn't operate as expected. Sometimes, when Vdd is supplied, the RTC starts counting from the time I disconnected Vdd, or it begins from an entirely different time. Additionally, I'm observing a voltage of 2.2V on Vdd when only Vbat is connected. Interestingly, the contents of the RTC backup registers are saved when only Vbat is supplied but the RTC doesn't work.  /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no

I bought Bluepill devboards from two different sellers, paying extra to hopefully receive genuine STM chips. When I use the Bluepill Diagnostics Tool written by Terry Porter, the tool reports passing on all counts except for one:Declared flash not 65536Does that definitely mean it isn't genuine? Thinking I could get a second opinion, I launched STM32 CubeIDE. I've barely ventured outside the world of Arduino so I have no idea what I am doing. I tried to follow instructions I got off Bing LLM AI which advised me to try to start debugging in the CubeIDE. Can anyone tell me whether the following can be used to infer whether the chip is genuine or not? Sorry if that's a stupid question. I heard that the Cube softwares don't work with fake chips so I was thinking this would be a way to get a second opinion on the providence of the chips. ST-LINK SN : 16004A002933353739303541 ST-LINK FW : V2J41S7 Board : -- Voltage : 3.17V SWD freq : 4000 KHz Connect mode: Under Reset Reset mode : Hardw

Hello, I'm using stm32 blue pill and my code communicates with several sensor using UART and displays it on LCD using i2c. My code works perfectly fine on debug. But when i power it again, it doesn't start execution. Although power LED is ON but code execution doesn't start. It only starts after i press reset button.I read some other solutions saying changing capacitor next to reset button, or connecting BOOT0 to GND. but I'm not sure how to do it.Can someone explain how can i do it through software.Similar - https://community.st.com/s/question/0D50X0000ArSX5ISQW/why-my-mcu-doesnt-work-when-powerup-it-only-starts-code-if-i-do-a-reset

I have recently bought 3 BluePills (STM32F103C8T6) and 1 ST-LINK V2 from ebay. I have been succesfully testing some old codes with Coocox Studio, but I decided to try out STM32CUBEIDE. Once I set up STM32CUBEIDE and built the program, I noticed that there's debugging option so I went with it. Unfortunately I wasn't able to debug the program - the chip would not be flashed successfully because the device would not be found or disconnected. I was/am receiving these messagesError in final launch sequence:Failed to execute MI command:-exec-runError message from debugger back end:Error creating process C:/Users/zdrav/Google Drive/STM32CUBEIDE/PWM/Debug/PWM.elf, (error 193).Failed to execute MI command:-exec-runError message from debugger back end:Error creating process C:/Users/zdrav/Google Drive/STM32CUBEIDE/PWM/Debug/PWM.elf, (error 193).Error creating process C:/Users/zdrav/Google Drive/STM32CUBEIDE/PWM/Debug/PWM.elf, (error 193).I also can't run the programError starting process.Cannot

Hi there, I am using STM32F103c8t6 blue pill. there is a problem: when I use ST-LINK programmer to download the code to it, the PC13 LED is turned ON, without being ON in the program! why is that? One assumption is that the board is driving too much current, is that so?

Hi all,Total newbie here.I am seeing this error in Windows 11 Device Manager: "Device Descriptor Request Failed", when I plug the Bluepill to a PC using Bluepill's onboard micro-USB PortAlthough the Bluepill looks like it is running OK with the previously flashed program (Blink PC13) with power supplied via the Bluepill's onboard micro-USB, Windows is giving this error. Being a "perferctionist", I would like to see the Windows error eliminated.I have check few "solutions" on youtube and none of them seems to apply to STM32, and thus not working. Can any kindly soul please help. Sorry if this has been asked before, but being a newbie to this site, I can't find anything suitable.

  Hello everyone,     I’m experiencing an issue with communication between two STM32WL33CC1 devices. I’m using one for LPAWUL wakeup receiver and the other for MRSUBG transmitter, but I noticed that beyond 10 meters, the communication starts failing.     Setup Details: SB1 resistor: 0Ω   -C3 resistor: 0Ω -Configured for +20 dBm PA   -Test environment: tested indoors in a hallway   The communication works fine up to 10 meters, but beyond that, wakeup packets are not received reliably.    Can everone help me solve this problem and get +/-30 stable meters?   Code LPAWUR: https://github.com/STMicroelectronics/STM32CubeWL3/tree/main/Projects/NUCLEO-WL33CC/Demonstrations/LPAWUR/LPAWUR_WakeupRadio_Rx   Code MRSUBG: https://github.com/STMicroelectronics/STM32CubeWL3/tree/main/Projects/NUCLEO-WL33CC/Demonstrations/MRSUBG/MRSUBG_WakeupRadio_Tx