Ten tutorials · one careful path
Learn PyBLE
Start with the exact firmware for your board, prove the BLE coding loop without hardware, then add files, reviewed source, Blocks, and physical components one boundary at a time.
Beginner progression
Follow the path in order.
Lessons are complete static pages: no sign-in, analytics, remote media, or client-side tutorial fetch is required. Allow about two hours for the full path, plus time for careful wiring reviews.
Read claims precisely
Compatibility and evidence are separate.
- Qualified firmware
- A firmware-release state backed by the project's release and hardware gates. Confirm it on the current installer.
- Designed for this profile
- The lesson or example was authored for that profile. This is not evidence that a physical run passed.
- Exact board only
- A documented carrier-board surface is required; a matching chip family is not enough.
- Development example — physical validation not recorded
- Source exists in the reviewed development snapshot, but no HIL record or examples release promotes it.
- Not applicable
- The lesson intentionally does not target that profile.
Immutable review points
Know what these pages were checked against.
Five firmware profiles
The lessons preserve this order and never infer a carrier pin map from a generic chip profile.
esp32-4mb · esp32-s3-n16r8 · waveshare-esp32-s3-lcd-147b · esp32-c3-4mb · rpi-pico2-wExamples development snapshot
All 32 entries are reviewed at one exact commit. They remain development-only, unreleased, and not HIL-validated.
Open examples snapshot 8f4529b3cd0d…A step does not match your screen?
Stop before writing or wiring anything else. Record the exact board profile and versions, then use the support and recovery checklist.