SF32 FAQ¶
1. Choosing a Product¶
1.1. Which SF32 family should I choose?¶
Start with these critical selection factors:
- Display resolution: Required pixel count, display interface, refresh rate and framebuffer memory.
- Bluetooth mode: BLE-only or dual-mode BLE and Classic Bluetooth.
- GPIO count: Usable pins after accounting for interface and memory assignments.
- Package size: Footprint, pin pitch and PCB assembly requirements.
- Power supply: Battery or regulated supply, operating voltage range and I/O levels.
- Audio functions: ADC/DAC, I2S and PDM requirements, including microphone channels.
Compare exact parts rather than choosing by family number alone: a higher number is not automatically the best fit. Every one of these factors is a filter in the Product selector: set them there to shortlist exact parts.
Family comparison · Product selector
1.2. Should I use a chip, module, or development board?¶
Use a development board to evaluate the platform and prove the firmware. Use a module to reduce RF, crystal and memory-routing work on a product carrier board. It can also lower overall development cost. For lower-volume products, a module outsources the supply chain of the components inside it, and its RF certification can prove very useful in some parts of the world. Choose chip-down when cost, size or hardware flexibility justifies owning the schematic, layout and RF work. Neither route removes finished-product validation. More modules will be listed as they become available.
1.3. Which development board should I start with?¶
Start with the display-focused LCD board for your chip family: SF32LB52-DevKit-LCD, SF32LB56-DevKit-LCD, SF32LB57-DevKit-LCD (N32R16 memory variant) or SF32LB58-DevKit-LCD (N16R32N1 variant). For SF32LB52x there are also compact boards: SF32LB52-DevKit-Core-3p3, SF32LB52-DevKit-Nano and SF32LB52-DevKit-ULP (wearable low-power evaluation). Check that the board's memory variant matches your target part; SiFli's official board-model guide lists all boards.
Product selector · Official board-model guide
1.4. How do I read chip and module part numbers?¶
Read the complete order code, not just the family prefix. Chip codes distinguish device, package and memory configuration; module suffixes describe fitted storage and memory options. Use the naming guide's examples and legacy exceptions, then confirm the exact orderable configuration with its supplier.
2. Memory and Specifications¶
2.1. What is the difference between SRAM, PSRAM, and Flash?¶
SRAM and PSRAM hold runtime data and lose it when their supply is removed; supported retention modes are device-dependent. On-chip SRAM and external or co-packaged PSRAM differ in access path, bandwidth and power. Flash is nonvolatile storage for firmware and assets. More Flash does not replace a shortage of working RAM.
2.2. How much memory does my application need?¶
Budget working RAM for the OS, stacks, heap, graphics buffers, audio and other concurrent tasks. A basic framebuffer needs width × height × bytes per pixel × buffer count; allow for stride alignment and additional rendering buffers. Separately budget nonvolatile storage for firmware, fonts, images, audio, files and OTA images. Measure peak usage on the intended workload.
Graphics overview · Plan a Product
2.3. When should I choose NOR, NAND, or eMMC?¶
Choose from the required boot path, capacity, access pattern and software support, not capacity alone. NOR commonly supports code and random reads; NAND needs suitable management for erase blocks, ECC and bad blocks; eMMC includes a managed storage controller. In these module descriptions, SPI-NAND and QSPI-NAND refer to the same storage option, not a discrepancy between products. Confirm bootloader, driver and filesystem support for the exact device.
Memory types · Module suffix codes
2.4. Does every part support all features listed for its family?¶
No. A family summary may combine capabilities from several parts. Memory, supply requirements, usable pins and exposed interfaces can depend on the exact SKU, package and multiplexing. A peripheral present in the chip may not be exposed by a module or development board. Check the part's variant table, datasheet and pinout, plus the SDK support for the required function.
Family comparison · Product selector
3. Application Fit¶
3.1. How do I choose a device for my display?¶
Match the panel's electrical interface and timing first, then check resolution, pixel format, refresh target, framebuffer memory and bandwidth. A maximum-resolution figure alone does not guarantee smooth performance. Confirm the required graphics acceleration and panel driver, then test representative screens and animations on the intended memory configuration.
Per-Device Interface Matrix · Display controller · Graphics overview
3.2. How do I check audio and microphone support?¶
Check ADC and DAC channels for analog paths, I2S for digital audio devices, and PDM for digital microphones. One PDM interface can carry up to two microphone channels; interface count is not microphone count. Usable channels still depend on pin exposure, multiplexing, driver support and board routing. Confirm the intended configuration rather than adding interface counts together.
3.3. Which products support BLE, Classic Bluetooth, or both?¶
SF32LB55x is BLE-only; the SF32LB52x, SF32LB56x, SF32LB57x and SF32LB58x families offer dual-mode Bluetooth. Radio capability does not guarantee every profile, codec or feature in every SDK configuration. Check the required application profile and its tested example; BLE support alone does not establish support for Classic Bluetooth audio or BLE Audio.
Family comparison · Bluetooth overview
3.4. Does my design need an external Wi-Fi device?¶
The SF32 products catalogued here do not provide an integrated Wi-Fi radio. The selector's Wi-Fi option identifies an external SDIO-based path, not built-in Wi-Fi. An external device also needs compatible power, pins, drivers and networking software; the presence of SDIO alone is not proof of a working solution.
3.5. How many GPIOs are actually available?¶
Use the exact package and memory configuration, then subtract pins committed to your required interfaces and board functions. A module exposes only part of the chip's pin set. On SF32LB57x BGA112, any additional MPI3/static-output pins are restricted-function pins, not freely assignable GPIOs. Do not treat a headline pin count as a guaranteed application GPIO budget.
Family GPIO notes · SF32LB57x variants
4. Availability and Product Planning¶
4.1. What do module regulatory markings mean for my product?¶
Use the module page's label summary to identify the marked variants and request the applicable approval documents and integration conditions. A printed FCC identifier or CE mark is not, by itself, evidence that your finished product is covered. Changes to the antenna, carrier or enclosure require review against the applicable conditions.
52 module markings · 56 module markings · 58 module markings
4.2. Can I request another memory or module configuration?¶
Contact μForge.io with the desired chip or module, storage and PSRAM capacities, interfaces, antenna requirements, expected volume and schedule. Confirm feasibility, SDK support, minimum order quantity and lead time before committing the design. A configuration shown in an older document is not a guarantee of current availability; SF32LB58-MOD-E4R32N1 is no longer available due to memory-chip supply shortages.
Contact μForge.io · 58 module availability
4.3. How do I confirm availability and obtain samples?¶
Use the selected product page's purchasing and documentation links, and specify the complete order code and required revision when contacting the supplier. Confirm current availability, memory configuration, antenna option and lead time. Start from a supported evaluation board where possible, and use the exact part's official documentation rather than a family summary as the final design reference.
Contact μForge.io · Product selector
Last updated: