Electronic components
STM32 MCU Selection Guide: Industrial Control vs IoT Applications
If you are picking an STM32 for a new design, the first question is not "which one is best" — it is "what does this board actually have to survive." Industrial control and IoT look nearly identical on a datasheet and behave nothing alike in the field. Get that distinction right and the rest of the selection is mostly arithmetic.
What STM32 is, in one paragraph
STM32 is STMicroelectronics' 32-bit microcontroller family built on ARM Cortex-M cores. It is not a single chip — it is a sprawling lineup of sub-families, each tuned for a different set of trade-offs: raw compute, power draw, wireless, or cost. That range is exactly why it is the default choice for so many embedded products, and exactly why picking the wrong variant is so easy.
Industrial control: what the board has to survive
On a factory floor or inside a motor drive, the MCU is not the star of the show — it is the thing that has to keep running when everything around it is hostile.
· Temperature: many industrial designs spec -40 to +85 C, and some go wider. Check the grade before you fall in love with a part.
· Real-time response: missed interrupt = damaged equipment. Timer precision and interrupt latency matter more than clock headline.
· Comms that exist in machinery: CAN, RS-485, sometimes EtherCAT or Profinet. A part with only UART and I2C will not fit here.
· Long availability: industrial products ship for 10+ years. Pick a series ST has committed to, not a "new and exciting" part that could go NRND in two.
We have watched teams prototype on a cheap mainstream line, then discover it cannot hold timing under the electrical noise of a real VFD cabinet. The board did not fail in the lab. It failed at the customer.
IoT: where the priorities flip
In a battery-powered sensor or a connected node, the board spends most of its life asleep. The job is different.
· Sleep current: this is the spec that decides battery life, not the active draw. Look at stop/standby modes in microamps.
· Wireless where it belongs: BLE, Zigbee, LoRa, or NB-IoT. If the product is wireless, let the MCU carry the radio instead of bolting on a separate module.
· Security: a node on a network needs a secure boot and key storage. Treat this as mandatory, not a nice-to-have.
· Footprint and BOM cost: IoT runs at volume, so every cent and every square millimeter compounds.
Which series fits which job
Series | Where it fits | Why |
STM32H7 | Industrial HMI, motion control | Highest performance Cortex-M7, handles demanding real-time + UI |
STM32G4 | Motor control, digital power | Fast analog + timers tuned for control loops |
STM32F4 / F7 | Mainstream industrial & IoT | The workhorses — broad ecosystem, still widely available |
STM32L4 / L5 | Battery IoT, portable | Low-power focus, L5 adds hardware crypto |
STM32U5 | Ultra-low-power IoT | Newest efficiency, security built in |
STM32WB / WL | Wireless IoT | WB = BLE/Zigbee, WL = LoRa — radio on-chip |
The selection checklist we actually use
· Core + frequency: enough headroom for the real-time loop, not the marketing number.
· Flash/RAM: size for the firmware plus a buffer for field updates — do not run it to the edge.
· Peripherals: list the exact interfaces (CAN, Ethernet, ADC count, timers) before browsing parts.
· Package: can your assembly house place it? A 0.4 mm pitch BGA changes your whole PCB cost.
· Availability: check ST's longevity commitment and current lead time before design-in.
· Ecosystem: does the part have working HAL/LL libs and a dev board you can prototype on this week?
At QIXINWEI (Shenzhen Qixinwei Technology Co., Ltd.), we have spent 13 years supplying STM32 and the broader ST lineup alongside full PCBA assembly. When a customer sends us a BOM, the conversation usually starts with "is this part actually available, and is it the right one for the job" — not with a quote. If you are mid-selection and want a second pair of eyes on the MCU and the supporting components, send the spec or the BOM and we will flag the risks before you commit.
FAQ
Q: STM32F4 or STM32G4 — which should I pick?
A: For general industrial and IoT work, STM32F4 is the safe, widely-available mainstream choice. Pick STM32G4 when the design is motor control or digital power, where its fast analog and control-centric timers earn their keep.
Q: Which STM32 is best for low-power IoT?
A: STM32L4/L5 cover most battery devices; STM32U5 pushes efficiency and security further for the newest designs. If the node is wireless, STM32WB (BLE/Zigbee) or STM32WL (LoRa) put the radio on-chip.
Q: Can STM32 handle industrial temperature ranges?
A: Yes — many STM32 parts are rated -40 to +85 C, and some go wider. The key is to select the correct temperature grade for your environment and verify it on the specific ordering code, not the family name.
Q: Is STM32 good for real-time control?
A: For hard real-time industrial control, the STM32H7 (Cortex-M7) and G4 families are strong. Timer precision, interrupt latency, and deterministic behavior matter more than peak clock — check those against your loop requirements.
Q: Where can I buy genuine STM32 with reliable supply?
A: Buy from authorized channels. QIXINWEI supplies genuine STMicroelectronics parts with original-component sourcing and global delivery from Shenzhen, and we can build a dual-source BOM so a single-line shortage does not stall your production.
0users like this.
