Board Profile
STM32 Blue Pill Practical Board Guide
The Blue Pill is a compact 3.3V development board built around the ARM Cortex-M3 STM32F103C8T6. It has no Wi-Fi, but it is strong for GPIO, ADC, UART, SPI, I2C, USB FS, and SWD debugging work.
Basic specifications
| MCU | STM32F103C8T6, ARM Cortex-M3, commonly operated up to 72MHz. |
|---|---|
| Power | Board input can come from USB 5V or the 5V pin, while the MCU and GPIO operate at 3.3V logic. |
| Memory | Commonly treated as 64KB Flash and 20KB SRAM. Some boards may differ from their printed marking. |
| I/O | GPIO, ADC, PWM timers, UART, SPI, I2C, CAN, USB FS, and SWD debugging are available. |
| Upload | USB DFU/serial bootloader paths or ST-LINK/SWD are used. For stable development, ST-LINK is the most reliable option. |
Pin usage notes
The Blue Pill exposes many pins, but some are tied to boot, USB, and debugging functions. Assign roles from the pin map before wiring a circuit.
- PA13 and PA14 are SWDIO/SWCLK debug pins. Avoid repurposing them during early development.
- PA11 and PA12 are USB D-/D+. Do not assign them as general GPIO if USB communication is planned.
- BOOT0 and PB2/BOOT1 determine the boot mode. Check these first when upload fails.
- PC13 is often connected to the onboard LED, but it is not a good choice for driving external loads.
- ADC inputs must not exceed 3.3V. Use a divider or level shifting for 5V sensors.
Some STM32F103 pins are described as 5V tolerant, but not all pins are. Treat ADC/analog and power-related pins as 3.3V-only unless the exact datasheet says otherwise.
Main interfaces
UART
Common pairs are PA9/PA10 for USART1, PA2/PA3 for USART2, and PB10/PB11 for USART3.
I2C
PB6/PB7 or PB8/PB9 are commonly used for sensors. Check pull-up resistors when designing I2C.
SPI
PA4-PA7 for SPI1 and PB12-PB15 for SPI2 are common. Useful for displays, flash, and high-speed sensors.
SWD
Connect PA13/SWDIO, PA14/SWCLK, 3V3, and GND to ST-LINK for stable debug and firmware download.
Best-fit projects
The STM32 Blue Pill fits projects where real-time control, multiple timers, fast GPIO, and reliable debugging matter more than wireless connectivity. ESP32 is easier when Wi-Fi is required; STM32 is better for motor control, serial equipment, multi-channel sensors, and low-level firmware practice.
Build and purchase cautions
- Blue Pill boards come from many vendors, so USB circuits, pull-up resistors, and bootloader state can differ.
- Some boards use clone MCUs. Before volume use, identify the chip and test ST-LINK programming.
- If USB upload fails, using ST-LINK is usually the fastest way to reduce variables.
Resources
ST STM32F103C8 product page
Check exact chip specifications, package details, and documentation links.
Open official pageSTM32F1 Reference Manual
Reference for timers, ADC, USART, SPI, I2C, USB, and other peripherals.
Open official PDFHow to choose this board in real builds
Do not choose a development board from the specification table alone. Power source, installation location, radio requirements, GPIO count, library support, and replacement availability matter in real deployments.
Checklist before wiring
- Confirm whether sensors and modules use 3.3V logic.
- Avoid using boot-sensitive pins for loads that change state during startup.
- Test with the final power adapter, not only USB power.
- Check flash and partition headroom if OTA or local logs are needed.
- Make sure the board can still be sourced if you need more units later.
When to avoid it
A popular board is not automatically the right board. Avoid a board when GPIO headroom, power behavior, radio support, or long-term replacement does not match the actual installation.