DAKEFPVF722: add LSM6DXX IMU support

[tviktinho]

Boards shipping under the DAKEFPVF722 target use the LSM6DSV16X IMU, which this target does not currently enable. Without USE_IMU_LSM6DXX the gyro is not detected under INAV and the board cannot arm.

Hardware

The board in question is sold as "JIJIE FPV Mini F722" (a rebrand). Stock Betaflight 4.5.2 identifies it as this target and reports the IMU:

# status
board: manufacturer_id: DAKE, board_name: DAKEFPVF722
Betaflight / STM32F7X2 (S7X2) 4.5.2
GYRO=LSM6DSV16X, ACC=LSM6DSV16X, BARO=SPL06
OSD: MAX7456 (30 x 13)
FLASH: JEDEC ID=0x00ef4018 16M

# resource
resource GYRO_CS 1 A04
resource GYRO_EXTI 1 C04

The sensor sits on SPI1 with CS on PA4 — the same bus and pin as every other IMU already declared in this target, so only the driver selection was missing.

Change

Adds the USE_IMU_LSM6DXX block, mirroring the sibling DAKEFPVF405 target from the same manufacturer, which already declares it with the identical bus and CS pin. As the comment in that target notes, the LSM6DSV16X is handled by the shared USE_IMU_LSM6DXX driver via WHO_AM_I detection.

Testing

Built INAV 9.1.0 with this change and flashed the board. The gyro is now detected and initialises:

# status
INAV/DAKEFPVF722 9.1.0 Jul 21 2026
CPU Clock=216MHz, GYRO=LSM6DXX, ACC=LSM6DXX, BARO=SPL06
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK

Baro, OSD (MAX7456) and the 16MB blackbox flash are all detected correctly with the existing target definitions — no other changes were needed.

Related: #10979

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[Copilot]

Pull request overview

Adds missing IMU driver enablement for the DAKEFPVF722 target so boards shipping with an LSM6DSV16X (detected via the shared USE_IMU_LSM6DXX driver) can successfully initialize the gyro/accel and arm under INAV.

Changes:

• Enable USE_IMU_LSM6DXX for DAKEFPVF722.
• Define LSM6DXX SPI bus/pin and alignment (SPI1 / PA4, CW90_DEG) consistent with the target’s existing IMU wiring assumptions and the sibling DAKEFPVF405 target.
• Add an in-file note clarifying that LSM6DSV16X/LSM6DSK320X are covered via WHO_AM_I detection under the shared driver.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Test firmware build ready — commit 27a652a

Download firmware for PR #11743

1 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.

Development build for testing only. Use Full Chip Erase when flashing.