Tutorials Overview¶
This series turns a successful first flash into practical SF32 development skills. It is organized by engineering scope: first prove one peripheral, then combine subsystems, then build the evidence needed for a product. The tutorials use SiFli-SDK examples as starting points, but the habits—verify hardware, keep a known-good baseline, and measure the result—apply to every SF32 software path.
Tutorials are the second stage of Getting Started. Complete its first-run success criteria first. If you are choosing a chip, module, or development board, start with the SF32 Family before beginning the series.
What You Need¶
Use an SF32 development board with a working USB data connection and serial console. The examples most often assume an SF32LB52-DevKit-LCD-class board such as sf32lb52-lcd_n16r8; on another board, use its supported board name and verify pin, peripheral, display, audio, and storage details in the relevant schematic and board files.
| Item | Minimum readiness check |
|---|---|
| Toolchain | SiFli-SDK can build a known example for your board. |
| Flash flow | You can repeatedly program the board without changing the setup. |
| Serial console | You can see boot logs and access the FinSH msh> prompt. |
| Board information | You have the board schematic or support files before assigning pins or peripherals. |
| Measurement tools | Keep a multimeter or logic analyzer available; add current measurement before low-power work. |
Recommended Learning Path¶
| Outcome track | Start when | You will practice | Continue with |
|---|---|---|---|
| First Peripherals | hello_world, flash, and serial output work. |
GPIO, FinSH, ADC, PWM, RTC, and a small board-level project. | Move on when you can independently prove an input, output, and basic peripheral. |
| Connected Subsystems | Single peripherals work reliably. | I2C sensors, LVGL, BLE, audio, storage, and deliberate coexistence testing. | Move on when two real subsystems remain stable together. |
| Product Validation | You can integrate middleware and diagnose ordinary failures. | Measured power, OTA recovery, custom displays, crash analysis, multi-connection BLE, and reusable drivers. | Use the relevant Develop and Learn articles as ongoing implementation references. |
The order is deliberate. Do not start with a display, BLE service, or custom driver until the board, flash flow, serial console, and a simple GPIO test are known-good. When a later tutorial fails, return to the last stage whose success criterion you can still reproduce.
How to Use Each Tutorial¶
Each exercise identifies a close SDK example, a goal, a success criterion, and likely failure checks. Start from the named example rather than an empty project, change one behavior at a time, and preserve a known-good build before combining features. Record the board revision, SDK version, board name, and observed result for any configuration you expect to reuse.
The tutorials intentionally do not replace the reference material:
- Use Develop for platform workflows, tools, firmware topics, and the consolidated SDK example index.
- Use Learn for architecture and subsystem decisions, such as graphics flow, Bluetooth behavior, and power strategy.
- Use the SF32 Family for device selection, board information, hardware design guidance, and production checks.
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.