GuideFirmware

Choosing a Low-Cost MCU: CH32V003 vs STM32 vs ESP32 for Price-Sensitive Products

How to pick a microcontroller when every rupee of BOM counts: what ultra-low-cost RISC-V parts can do, when STM32 is worth it, and when you need the wireless of an ESP32.

Short answer

Simple sensing, display, lowest cost
WCH CH32V003
More peripherals, long-term ecosystem
STM32 (C0, G0 families)
Wi-Fi or Bluetooth needed
ESP32 family

For high-volume, price-sensitive products the microcontroller is often the single biggest lever on cost. The right answer depends less on raw performance and more on how much memory, which peripherals and what connectivity your product truly needs.

Start with a requirements list

  • Flash and RAM, with room to grow (including a bootloader if you want updates).
  • ADC channels, resolution and sample rate.
  • Timers, PWM channels and communication buses (UART, I²C, SPI, USB).
  • Wireless: none, Bluetooth, Wi-Fi, or both.
  • Supply availability and second sources over the product's lifetime.

The three options compared

Typical positioning (check current datasheets and distributor pricing for your volumes)
OptionStrengthsWatch out for
WCH CH32V00332-bit RISC-V at 48 MHz, 16 KB flash, 2 KB SRAM, 10-bit ADC, reported pricing around ten US cents in volumeVery little memory, so firmware must be designed for it from the start
STM32 (entry families)Huge ecosystem, mature tools, many package and memory optionsHigher unit cost than the cheapest RISC-V parts
ESP32 familyIntegrated Wi-Fi and Bluetooth, plenty of memoryHigher power and cost if you do not need wireless

Five questions to decide

  1. Does it need wireless?

    If yes, an ESP32-class part is usually cheaper than an MCU plus a separate radio module.

  2. How big is the firmware really?

    Estimate flash and RAM, including a bootloader and future features. Leave at least 30% headroom.

  3. What volume and price target?

    At high volume, a few rupees per unit justifies extra firmware effort on a smaller chip.

  4. What does your team know?

    Toolchain familiarity shortens development, but should not override a large BOM saving.

  5. Can you get it for five years?

    Check distributor stock, lifecycle status and pin-compatible alternatives.

Frequently asked questions

Is the CH32V003 reliable enough for products?

It is used in many low-cost products. As with any part, validate it against your temperature, ESD and supply requirements before committing.

Can a tiny MCU support firmware updates?

Yes, with a small bootloader and careful flash layout. My USB power meter story shows how.

Should I always pick the cheapest part?

No. Pick the cheapest part that meets every requirement with headroom. A respin costs more than years of savings.

Sources

  1. CNX Software: 10-cent CH32V003 RISC-V MCU with 2 KB SRAM and 16 KB flash
See it in a real projectA USB Power Meter on a Sub-₹200 BOM: Choosing the MCU and Display, Then Fitting OTA and Power Monitoring Into a Tiny Chip
Nikhil Robinson

Embedded systems consultant at TechProgeny, Bengaluru. 7+ years and 29+ shipped products across firmware, embedded Linux, edge AI, apps and IoT servers.