ShiroFPV Flight Controller

ShiroFPV Flight Controller Collection

Open-source FPV flight controller hardware — schematic, PCB layout, symbols and firmware target, all published in full.

Designed in KiCad, targeted at Betaflight, and licensed so it stays open.

More at shirofpv.com/flight-controller

Boards

V1 — SFVPF435 (30.5 × 30.5)

Layout

V1_30x30_SFVPF435/
├─ Shematic/          hardware sources — CERN-OHL-S v2
│  ├─ ShiroFPV_Flight_Controller.kicad_sch    schematic
│  ├─ ShiroFPV_Flight_Controller.kicad_pcb    PCB layout
│  ├─ All_Own_Symbols.kicad_sym               custom symbols
│  ├─ All_Own_Symbols.pretty/                 custom footprints
│  └─ .glb                                    3D model
└─ Release/           firmware — GPL-3.0-or-later
   ├─ config.h                                Betaflight target config
   └─ SFPVF435V1.hex                          compiled firmware

Note: Shematic/ is a typo for Schematic/ kept as-is so existing links and clones don't break.

V2 — SFVPF435 (20 × 20) — coming soon

A smaller board for builds a 30.5 stack won't fit. Decided so far:

Dropping the analog OSD chip is what buys the space. Everything else — gyro, baro, blackbox, UART count, power stage — is still being worked out.

Details in V2_20x20_SFVPF435/.

Datasheets

Artery's documentation is not redistributed here — it is their copyright. Download it from the source:

• AT32F435 — product page (datasheet + reference manual)
• AT32F437 — product page

Building one

The design files are complete — schematic, layout, custom symbols and footprints. Open ShiroFPV_Flight_Controller.kicad_pro in KiCad 8 or newer, export gerbers, and send them to whichever fab you like.

Flash SFPVF435V1.hex with the Betaflight Configurator, or build from the Betaflight sources using config.h as the target definition.

It flies. Mostly.

Licence

Two licences, because there are two kinds of work here. Both copyleft.

Short version: use it, modify it, build it, sell it. If you distribute a modified version, publish your sources under the same licence. You can profit from this design — you just can't close it.

Full detail and reasoning in LICENSING.md.

Contributing

Issues and pull requests welcome — improvements, fixes, or a revision of your own. Contributions are accepted under the same licences as above.