Projects Overview¶
Projects are application-grounded references that you can duplicate, adapt, and use to explore an SF32 product direction. Rather than trying to demonstrate every feature in isolation, each project shows a focused combination of SF32 capabilities in something a person might actually build and use.
What Projects Are For¶
Each project should be:
- Grounded in an application. It starts with a recognizable product behavior or use case, not an abstract feature demonstration.
- Complete enough to follow. It connects the selected hardware, software baseline, dependencies, integration milestones, validation evidence, and an adaptation path, so you can experience a substantial portion of the development flow.
- Meant to be duplicated. It provides a practical baseline to reproduce first, then modify for your own hardware, interaction model, or product requirements.
- Fun to make. A project should invite experimentation and make visible what SF32 capabilities enable; usefulness and enjoyment belong together here.
Use a project after completing the relevant Getting Started baseline. Use Reference Designs for the reusable hardware/software baseline that a project adopts and adapts; a project must link to that baseline where one exists, rather than recreate its design-file, bring-up, or production material.
SiFli-SDK Projects¶
Third-party project ownership
LilyGO T-Display-SF32 is maintained by Xinyuan-LilyGO/LilyGO, not by SiFli. Use LilyGO's repository for board-specific hardware and firmware support, and SiFli sources for the underlying SF32 device and SiFli-SDK.
| Project | Outcome | Hardware and software baseline | Best for |
|---|---|---|---|
| SF32 Xiaozhi Voice Assistant | A connected voice-and-display assistant based on the open-source Xiaozhi SF32 implementation. | Supported SF32LB52 boards, Xiaozhi SF32 source, Bluetooth PAN, and Xiaozhi cloud services. | Evaluating an AI voice-interaction product flow and adapting its hardware or application behavior. |
| SF32 BLE Talkback Intercom | A multi-device BLE push-to-talk room with role selection, Opus speech, Slave reconnect, state indication, and low-power behavior. | Two or more SF32LB52-DevKit-ULP boards, pinned Talkback source, a pinned SiFli-SDK 2.4-compatible revision, and talk_back/1.2@sifli. |
Qualifying portable group intercom behavior, acoustics, RF recovery, and power before custom hardware. |
| SF32 E-Paper EPUB Reader | A local EPUB reader with library/contents flow, key and touch input, dynamic fonts, full/partial refresh, storage, and low-power states. | SF32-OED-EPD V1.1, YZC085 V1.05 e-paper, pinned EPD Reader and SDK commits, TF storage, and qualified content/fonts. | Evaluating an e-paper reading terminal, EPUB/rendering limits, panel waveforms, storage recovery, and power behavior. |
| SuperKey Multifunction Macro Keyboard | A three-display USB HID/CDC desktop controller with keys, encoder, sensing, telemetry, and a companion application. | Open sf32-keyboard hardware, the sf32lb52-superkey firmware target, and SuperKeyHub. |
Evaluating a desktop HMI, macro keyboard, status panel, or host-connected control surface. |
| Radiation Monitor | A portable 79-point 2.4 GHz signal-strength viewer with smoothing and history playback. | SF32LB52 RF test path, LVGL display, KEY2 control, and a controlled RF comparison setup. | Exploring relative interference trends and deciding whether a calibrated RF instrument path is justified. |
| Pocket Pi SF32 Handheld Game Console | A local NES-emulation handheld with game browser, input, audio, save states, and built-in/TF-card storage. | SF32LB52-DevKit-ULP target, PocketPi/Nofrendo source, AW9523 controls, and legally usable NES content. | Testing a game-oriented graphics, input, audio, storage, and power workload before custom hardware. |
| LilyGO T-Display-SF32 | A third-party display-led SF32 development platform with touch, motion, storage, audio, LoRa, and power-management paths. | LilyGO T-Display-SF32 hardware, fixed board-repository and LilyGO SDK-fork commits, and the t-display-sf32_hcpu target. |
Evaluating a LilyGO-maintained wearable, handheld, sensor-terminal, or HMI baseline without mistaking it for an official SiFli project. |
Zephyr Projects¶
This group includes projects built on Zephyr directly or on a documented Zephyr-derived layer, such as OpenSiFli's ArduinoCore-zephyr.
| Project | Outcome | Hardware and software baseline | Best for |
|---|---|---|---|
| Arduboy2 on SiFli | A reproducible path for evaluating an Arduboy2-style game or interactive demo on SF32. | OpenSiFli Arduboy2-SiFli source, ArduinoCore-zephyr, and the selected SF32 display/input/audio path. | Testing local game interaction, graphics, input, audio, and the limits of a portable Arduino-oriented application layer. |
| ZMK Keyboard Firmware on SF32 | A reproducible SF32LB52 split-keyboard baseline with matrix scanning, layers, USB HID, BLE split/host links, settings, and ZMK Studio. | OpenSiFli/zmk, the SF32LB52-DevKit-LCD ZMK board variant, and the urchin_sf32lb52_left/right shields with pinned manifest dependencies. |
Evaluating ZMK-based wireless keyboards, macro pads, or custom HID products while measuring the maturity of the downstream SF32 port. |
What Every Project Includes¶
Each μForge project should document its target outcome, intended reader, supported hardware and software versions, prerequisites, source repository, milestone-based build steps, validation criteria, measurements, and product-adaptation handoff. A project is a starting point for engineering work, not a substitute for production validation of the final hardware, service integration, security, privacy, or regulatory requirements.
Auto-generated content
This page was compiled/drafted without an existing source document. Verify technical claims against SiFli's official documentation before relying on them.