Config Target Guidance - Cloud Build
The cloud build carries boards that the Betaflight team has reviewed and accepted. What it accepts, what it warns against, and what is eligible for Betaflight Supported is set out in the Hardware Policy. A design that is not accepted can still be distributed by its manufacturer, see Two Routes to Pilots. The notes below explain the guidance behind the most common questions.
New flight controller designs using STM32 F4 and F7 microcontrollers with more than four motor outputs are not accepted for new designs in the cloud build.
-
We strive to be the best flight experience available on the widest range of hardware. These older microcontrollers have limited timer and DMA resources, and more than four motors exhausts them.
-
They remain a good choice for budget freestyle and racing designs, and for AIOs with four motor outputs. For high performance, high motor output and high IO designs, where an STM microcontroller is preferred, we recommend the STM32H743, which is now very close in price to the F405.
-
Existing designs are not affected, although some future features may not fit within their resources.
New STM32 F411 designs and SPI receivers are not accepted for new designs, and the BMI270 gyro is not recommended:
-
The STM32 F411 has been a stable option for smaller flight controllers, and the cloud build has extended its useful life despite its limited flash. Its limited IO makes it a poor choice for new designs, and we recommend AT32, PICO or G4 options instead. Existing F411 targets continue to be built.
-
Serial receivers are preferred to SPI receivers, in line with the direction of the ExpressLRS project. Existing SPI receiver targets continue to be built.
-
The BMI270 IMU is no longer recommended due to calibration issues (drift), and is accepted only as a second source on an ICM-42688-P footprint. Where a PCB is second-sourced between a BMI270 and an ICM-42688-P on the same footprint, see the
ENABLE_BMI270_ALIGN_AS_ICMdefine.
For the full list of MCU platforms and target names the firmware supports, and which are recommended for new designs, see Supported MCU Platforms and Targets. For the sensor and peripheral defines a config may use, see Definitions for Targets.
Betaflight is free software, and will continue to be free, however the automated build and delivery system is not free and comes with operational costs. Supporting the costs of running the cloud build system is optional. You are free to distribute your own hex files however you choose, and your customers can flash them with the "Load Local" function of the Betaflight App.
We recommend starting a dialogue with the Betaflight team at [email protected] before you move to making prototypes. The Betaflight team will endeavour to create a reference library to assist manufacturers as early as possible in the process.