Plain running list of useful references gathered while researching this project. Format: link, what it is, what they ran into / how they solved it (where known).
Last updated: 2026-09-22
SpeedyBee F405 V3 Betaflight unified target config The actual resource/pin mapping Betaflight uses to support the real SpeedyBee F405 V3 out of the box — the closest thing we have to a schematic reference without a teardown. Gives MCU (STM32F405, 8MHz HSE), gyro (BMI270 over I2C, CS/interrupt pins), all 6 UART pin assignments, 8 motor outputs with DMA/timer mapping, current sensor ADC pin + scale factor (386), OSD/SD card SPI wiring, beeper/LED pins. This is the direct starting template for cloning the board — copy the pin philosophy, adjust for your own MCU package/footprint choice.
SpeedyBee F405 V4 unified target config Same idea but the newer revision — notably switches the IMU to ICM42688P over SPI instead of the V3's I2C BMI270. Worth comparing against V3 since SPI IMUs are lower-latency, which matters for the "responsive" requirement. Useful to see what SpeedyBee itself changed between revisions and why (faster gyro interface).
Betaflight Custom Board Configuration docs Official docs on how to define a new target/board for Betaflight. Directly answers "how do I make my clone actually run Betaflight" — this is the path to avoid writing flight-control firmware from scratch.
Betaflight unified-targets repo The full collection of target config files (including the two above) for essentially every commercial FC Betaflight supports. Good for cross-referencing multiple existing F405 boards (Matek F405 AIO/STD/MINI/CTR, Diatone Mamba F405, BetaFPV F405, etc.) to see common pin-mapping conventions and what a "typical" STM32F405 board looks like across vendors, not just SpeedyBee.
Betaflight — ESC Firmware wiki page Explains DShot and the ESC firmware landscape. Their explicit recommendation: AM32 for 32-bit ESCs (open source, actively developed, full RPM filtering + bidirectional DShot telemetry, works across STM32/GD32/AT32) and BlueJay for 8-bit ESCs (open source equivalent to closed-source BLHeli_S). They flag BLHeli_32 versions 32.8+ as having reported communication/motor issues, and call out JazzMaverick as deprecated/unmaintained — i.e., steer toward the open firmware options both for cost (no per-unit licensing) and reliability.
AM32-MultiRotor-ESC-firmware The open source ESC firmware itself. If integrating ESC onto the FC (AIO route), this is what runs on the motor-driving MCU — no licensing fee, source available if something needs debugging on your custom hardware, which matters since you're not running stock reference hardware.
Open-4in1-AM32-ESC (Just4Stan) A fully open-source (KiCad, CERN-OHL-S-2.0 licensed) 4-in-1 ESC board: AT32F421 per channel (one MCU per motor), 40A continuous per channel, current sensing rated to 165A, 20x20mm mounting, 6-layer/2oz copper PCB, 2-6S input. Useful as a real, open reference design for the high-current side specifically — even if you go the AIO route instead of a separate ESC board, the layout/copper/current-sensing choices here are directly applicable to your power stage. They chose per-channel MCUs + heavy copper + 6 layers specifically to handle current and thermal load — a concrete data point for the "handle high currents" requirement.
OpenDrone_HW_AIO_FC_F405 An actual open-source AIO (flight controller + integrated ESC) board built around STM32F405RGT6 — this is the closest existing open project to exactly what you're building (integrated FC+ESC, STM32F405, USB). It uses a dual-MCU approach: STM32F405 for flight control, a separate small EFM8BB21 for ESC duties. Also uses MPU6000 IMU, BMP280 baro, INA186 current sensor (a dedicated current-sense IC rather than a raw shunt-to-ADC approach), AT7456 OSD, TPS5430 5V@5A + RT9013 3.3V@500mA regulators, jumper-selectable power rails. MIT licensed. Good reference for how someone else solved the "put an MCU-controlled ESC on the same board as the FC" problem — notably they used a separate small MCU for ESC control rather than driving DShot straight off the main STM32F405, which is worth considering as a design pattern.
Zbotic — Custom Flight Controller: STM32 Build Guide A step-by-step guide to building a custom FC from scratch on STM32F405. Recommends STM32F405RGT6 specifically as the best starting chip "for first-time builders" due to community support and Betaflight compatibility (vs. F722/H743 for more advanced/faster builds). Lays out the standard 30.5×30.5mm mounting pattern, minimum viable component list (MCU + IMU + 5V reg + USB-C + 4 motor outputs + 2 UARTs), and a sane bring-up order: power → USB → gyro → motors → RC receiver, tested in that order before ever installing props. Notably light on documented failures/pitfalls — read it as the "happy path" checklist, not a troubleshooting guide.
Industrial Monitor Direct — Custom STM32F405 Flight Controller Hardware Design More detailed hardware-design-level article: recommends a 4-layer stackup (signal / ground / power / signal), decoupling caps on every VDD pin (100nF + 10µF combo), analog ground plane isolation specifically for the ADC reference (relevant to current/voltage sensing accuracy), USB-C CC pull-down resistors for enumeration, and notes that ICM-42688-P is a well-supported native-Betaflight IMU choice. Also flags AT32F435 as a cheaper/faster alternative MCU but with weaker Betaflight support than STM32F405 — reinforces that F405 is still the safe default for compatibility even if not the cheapest/fastest silicon available.
The Devana Project — Hardware design for AM32 ESCs Deep-dive on the ESC power-stage side specifically: MOSFET selection (pick continuous current rating "at least double" your expected draw, since datasheet numbers assume lab conditions, not a cramped drone board), gate driver options (Fortior FD6288, TI DRV8300) with a specific warning about undervoltage protection thresholds conflicting with low gate voltage designs, gate resistor sizing (10-20Ω as a practical starting point), input capacitance guidance (250-500µF per motor, mix of MLCC + electrolytic, noting MLCC capacitance drops under DC bias so rate caps ~2x the actual voltage), and PCB layout guidance (minimum 4 layers, prefer 6-8 for higher current, ground plane paired with every signal layer, ground via near every signal via). This is the most detailed "how to actually not blow up your power stage" reference found.
TI INA240 datasheet + TIDA-00913 reference design A bidirectional, high-precision current-sense amplifier rated 4-80V, built for exactly this kind of high-current in-line/shunt sensing. Alternative to the "raw shunt straight into the STM32 ADC" approach the stock SpeedyBee target uses — costs a little more BOM but gives cleaner, more accurate current telemetry at high current, which may matter if your research needs reliable current/power data from the test flights, not just flight behavior.
AIO vs Stack Flight Controllers: Pros and Cons Explains the standard FPV-industry reasoning for why stacks (separate FC + ESC boards) are usually preferred over AIO: repairability (swap just the failed board instead of the whole thing) and thermal management (separate boards = separate heatsinking, AIO "can" overheat under sustained high current draw on 6S with aggressive flying). Concludes stacks are "the safer long-term choice" for most standard builds — this reasoning assumes you want to repair boards after a crash, which doesn't apply to a disposable research design, but the thermal warning is still worth taking seriously in the layout (see plan §3/§6).
Engineering a low-cost, expendable fixed-wing drone for search and rescue (EAVDAR paper) Academic paper on designing a genuinely expendable/disposable drone. Their cost-reduction approach: foam board + 3D-printed structure instead of custom-engineered airframe parts, off-the-shelf components wherever possible instead of custom avionics (they used a stock Pixhawk 2.4.8 rather than a custom FC), modular sections for quick assembly, and — notably — a semi-disposable philosophy where cheap structure (foam) is sacrificed but avionics are recovered where possible. Useful as an outside-the-FC-world data point on how other "designed to be destroyed" projects think about the cost/reliability/recoverability trade-off; also a reminder that most similar projects reach for an off-the-shelf FC rather than rolling their own, which is worth keeping in mind as a fallback if the custom-FC timeline slips.
Hack Club Forge and hackclub/forge GitHub repo
The funding platform itself — described as a Hack Club YSWS ("You Ship, We Ship") program for teens building hardware projects. The public docs available didn't spell out exact funding caps/reimbursement mechanics in what we could pull — check the live site directly (and the "contributing"/development.md docs in the repo if you want to understand the platform's own architecture) before finalizing a purchasing plan, since program details tend to evolve.
Notes on what wasn't found
- No public teardown or leaked schematic of the actual SpeedyBee F405 V3 PCB was found — the unified target config is a functional reference (which pins do what), not a full schematic (exact part numbers, regulator topology, decoupling values). Expect to make your own component-level choices even while following the pin-mapping philosophy.
- Didn't find a project that documents someone building an FC specifically for one-time-use/crash-test research (as opposed to disposable airframes with stock FCs, or normal FPV FCs designed for repair). If you find one later, it belongs at the top of this list — it would be the single most directly relevant reference.