# FAQ / Betaflight - no gyro, no blackbox, no baro

Betaflight 4.4 and later introduces "cloud-build" as presented in 4.4 release notes here: https://betaflight.com/docs/wiki/release/Betaflight-4-4-Release-Notes#1-cloud-build

For cloud-builds, the 3 typical things that a target's definition might lack is the acc/gyro, baro, & flash-chips.

Although it is the manufacturers' responsibility to keep targets updated, Betaflight developers can easily fix these issues upon reports of missing defines. Note: Manufacturer of Clones should create their own target.

Recommended: use latest Configurator https://app.betaflight.com (currently in development).
- [Out of date] ~~Recommend using a nightly Configurator as there are some worthy bug-fixes: https://github.com/betaflight/betaflight-configurator-nightlies/releases~~
- (Note: release 10.9 has a bug where you are ***required*** to enable expert-mode on the flashing tab; otherwise the UI will ignore any custom defines requested.)

Two proper routes to take is :
option 1) iterate through all the defines and report exactly which one works for specifically what flight-controller.
option 2) use the integrated support-system along with discord comment as per documenation https://betaflight.com/docs/wiki/configurator/firmware-flasher-tab#board-defines

i.e.

* **option 1**) Enable **`Expert-mode`** on `Firmware Flasher` tab (***required*** in 10.9, or prefer to use a nightly configurator). Then use the baro/flash/etc defines as reported by 4.4 release notes.
Prefer to cloud-build & flash `4.4-dev` or `4.5-dev` rather than "release". (at this time until things settle as "stable")

* **option 2**)
- 1. Flash your board with the **Core-Only** toggle enabled.
- 2. Use **`Submit Support Data`** button on CLI tab.
- 3. Post support IDs to Betaflight discord's `#cloud-build-issues`, explaining what you need.
- 4. Optionally, Include info from CLI status command.
- Devs will add the define(s) to source-code.
- Note: devs will not add defines for FC's that are actually clones, but prefer the clones to have their own target. Please check if your clone already has a specific target.
### Custon Defines:
* Any defines as listed on https://betaflight.com/docs/development/manufacturer/manufacturer-design-guidelines#42-definitions-for-targets but user may exclude the `USE_` prefix.

Blackbox flash chipsets:

FLASH
FLASH_M25P16
FLASH_W25N01G
FLASH_W25M
FLASH_W25M512
FLASH_W25M02G
FLASH_W25Q128FV

SDcard logging:

SDCARD

Serial loggers:

BLACKBOX

Gyros:

ACCGYRO_BMI270
ACCGYRO_BMI160
GYRO_SPI_MPU6000
ACC_SPI_MPU6000
GYRO_SPI_MPU6500
ACC_SPI_MPU6500
GYRO_SPI_MPU9250
ACC_SPI_MPU9250
GYRO_SPI_ICM20602
ACC_SPI_ICM20602
GYRO_SPI_ICM20689
ACC_SPI_ICM20689
GYRO_SPI_ICM42605
ACC_SPI_ICM42605
GYRO_SPI_ICM42688P
ACC_SPI_ICM42688P

Barometers: (Baro may *require* battery)

BARO
BARO_MS5611
BARO_SPI_MS5611
BARO_BMP280
BARO_SPI_BMP280
BARO_BMP388
BARO_SPI_BMP388
BARO_LPS
BARO_SPI_LPS
BARO_QMP6988
BARO_SPI_QMP6988
BARO_DPS310
BARO_SPI_DPS310
BARO_BMP085
BARO_2SMBP_02B
BARO_SPI_2SMBP_02B

Magnotometers:

MAG
MAG_AK8963
MAG_AK8975
MAG_DATA_READY_SIGNAL
MAG_HMC5883
MAG_LIS3MDL
MAG_MPU925X_AK8963
MAG_QMC5883
MAG_SPI_AK8963
MAG_SPI_HMC5883

* Example for external baro/mag of specified type: `BARO BARO_BMP280 MAG MAG_QMC5883 `

* Note that if a define is already existent, an error will be reported. Simply remove the specified define and try again.

* Complete list of defines: https://hackmd.io/@nerdCopter/H11rvS8Lh

* This video is well explained: https://www.youtube.com/watch?v=ksxONEal7yo

* Pilot may also define values with PARAMETER=VALUE. e.g. `GYRO_1_ALIGN=CW180_DEG`