About μForge.io¶
Engineers evaluating a new microcontroller shouldn't have to piece together the full picture from a datasheet here, a wiki page there, and a forum thread somewhere else. μForge.io exists to close that gap.
We document SiFli's SF32 family of ultra-low-power microcontrollers — Bluetooth-connected, graphics-capable, AIoT-focused silicon for wearables, smart displays, and other battery-powered connected products — as one coherent, cross-linked path instead of scattered reference material. Chip and module selection, development boards, SDK workflows, hardware design guides, and production checklists all live here, organized around how a real product actually gets built: pick the part, prove it works, design it in, ship it. We check technical details against SiFli's official documentation where source material is available, and flag pages whose content still needs verification.
We picked SF32 for two reasons. It spans several core configurations and integrates graphics acceleration and hardware decompression, with the exact mix varying by family. And its SDK, hardware guides, and source are genuinely open, even though the ecosystem around it isn't nearly as well known yet as ESP32 or STM32. That combination of real openness and low visibility is exactly the gap this site is built to close.
Our goal is simple: help engineers make hardware and firmware decisions faster and with more confidence, so less time goes into re-deriving basics and more goes into building.
The name¶
μForge.io and uForge.io are the same project and are used interchangeably. The “μ” (Greek mu, for “micro”) is written as the ASCII “u” (also read as “you”) wherever Greek letters are inconvenient, so μForge = uForge and μForge.io = uForge.io (domain: uForge.io).
Have a question, a correction, or something you wish this site covered? Contact us.
Last updated: