Choosing a WCH BLE MCU: CH583 vs CH585 vs CH592, and When to Step Up to CH32V

WCH's BLE lineup looks crowded from the outside: CH57x, CH582, CH583, CH584, CH585, CH591, CH592. The useful insight from a recent community selection guide is that they are not eight independent products - they are three tiers built on one core and one protocol stack, with a fourth family (the BLE-capable CH32V parts) covering industrial use cases the tiers do not.

Because the core and stack are common, switching between tiers costs very little. That changes the selection question from "which chip is best" to "which tier does my product actually need".

Ask four questions before opening a datasheet

Do you need USB, how many ports, and how fast? One full-speed port for programming and serial bridging is different from two ports, which is different again from 480 Mbps
Do you need a display? A segment LCD is a different requirement from an LED matrix
What is the power source? Coin cell, single-cell Li-ion, or mains. Year-scale standby is a hard requirement or it is not
Do you need NFC? Tap-to-pair, tap-to-start, or near-field read/write

Those four answers map almost exactly onto the differences between WCH's tiers: USB port count and speed, display driving, power and standby current, and NFC.

Tier 1 - balanced workhorse: CH583 and CH582

The general-purpose pair. Both carry dual full-speed USB, 40 GPIO, 14 ADC channels, 14 touch channels, four UARTs and two SPI controllers.

CH583 adds an extra SPI1 host controller and supports supplies down to 1.75 V
CH582 is the right pick when pin count and board area are tighter; it drops SPI1

This is the only tier with two USB ports. If your product must act as a USB host reading a peripheral and as a device reporting to a PC at the same time, this is the only option in the BLE range. The 1.75 V support combined with SRAM retention in sleep also makes the CH583M variant comfortable on a single Li-ion cell.

Tier 2 - human-machine interaction: CH585 and CH584

The display-and-touch tier, running up to 78 MHz.

CH585: 128 KB RAM, one full-speed USB plus one 480 Mbps high-speed USB, SPI1, 112-dot segment LCD, LED matrix interface (1/2/4/8 ways), NFC, 14 ADC and touch channels
CH584: 96 KB RAM, single full-speed USB, no NFC-adjacent extras beyond the common set, still 112-dot segment LCD

If the product has a matrix or seven-segment LED display at any meaningful size, only the CH585 exposes the LED matrix interface. If it needs tap-to-pair NFC, this tier is where NFC lives - the other two tiers do not have it. And if you need bulk transfer or a virtual network adapter over USB, the 480 Mbps port on the CH585 is the difference between viable and not.

Tier 3 - small battery terminals: CH592 and CH591

The volume tier. Both offer single full-speed USB with host and device support, an 80-dot segment LCD, 24 GPIO, 12 ADC channels plus a temperature sensor, supplies down to 1.75 V, sleep current of roughly 0.8 to 2.5 uA and power-down current of 0.3 to 1.3 uA.

CH592: 512 KB FlashROM, ADC with DMA, I2C, 12 capacitive touch keys, receive sensitivity around -95 dBm
CH591: 256 KB FlashROM, ADC without DMA, no I2C, no touch keys - the deliberately trimmed part

For a wristband, a portable detector or an electronic shelf label, this is the default answer. The microamp sleep floor is what makes a coin cell or a small Li-po viable across a year of standby.

The fourth family: BLE-capable CH32V

The CH32V wireless variants are not a fourth BLE tier, they are a different architectural answer: BLE 5.x on a QingKe RISC-V core running at 144 MHz zero-wait-state, alongside CAN, USB and Ethernet, with roughly 0.5 uA standby.

That combination is what a gateway needs, not what a sensor tag needs. A sensible wireless product architecture is often two-level: a Tier 3 part in each endpoint for radio and power, and a CH32V wireless part as the aggregator that bridges BLE to CAN or Ethernet backhaul. If you are weighing that split we have notes on the CH32V307/CH32V317 Ethernet path and on the CH32H417 for the high-bandwidth tiers.

Reducing within a tier

The pairs are deliberately close, so the choice inside each pair comes down to one or two features:

Pair	Choose the smaller part when	Choose the larger part when
CH582 vs CH583	pins and board area are tight	you need SPI1 host or 1.75 V operation
CH584 vs CH585	high-speed USB is not needed	you need 480 Mbps USB, SPI1, 128 KB RAM or LED matrix
CH591 vs CH592	cost is the driver and interaction is minimal	you need touch keys, I2C, 512 KB Flash or ADC DMA

Five recurring mistakes

Assuming more USB is better. Battery terminals usually cannot use a second port, and adding it costs both power and area. A single-port CH592 frequently beats a dual-port CH583 in a wearable
Forgetting SRAM retention in sleep. Long-standby products must verify the retention region, otherwise wake-up loses state and spends more energy rebuilding it
Treating display driving as an add-on. Choosing a part without an LCD or LED driver forces an external driver chip, which costs board area and quiescent current. Pick the driver up front
Underestimating RF and antenna work. Half of BLE range is silicon and half is board-level matching plus antenna. A -95 dBm receiver means nothing with a poor layout - start from the vendor reference design
Choosing on unit price alone. Confirm package availability and lead time before committing to volume; a well-specified part on allocation is worse than a slightly larger one you can actually buy

Practical evaluation advice

The tiers share a core and a protocol stack, which means prototypes can validate two tiers in parallel with little duplicated effort. Get the eval boards for all three tiers, then measure the three things datasheets cannot tell you: real RF range in your enclosure, real current in your actual sleep/wake duty cycle, and how the display actually looks.

The selection guide cites CH583/CH582 datasheet V1.9, CH585/CH584 V1.6, CH592/CH591 V1.9 and CH32V203 V3.0 as its sources; verify exact BLE version numbers, RAM/Flash totals and pricing against the current official datasheets before fixing a BOM.

Sources

Source thread: WCH BLE selection guide (21ic, 2026-10-24)

Compiled by Open RISC-V AI Assistant For product inquiries, contact contact@open-riscv.com or visit /forum/inquiry