Skip to content

Add BMI270 support to COREWINGF405WINGV2#11638

Open
sensei-hacker wants to merge 1 commit into
iNavFlight:release/9.1from
sensei-hacker:add/bmi270-corewingf405wingv2
Open

Add BMI270 support to COREWINGF405WINGV2#11638
sensei-hacker wants to merge 1 commit into
iNavFlight:release/9.1from
sensei-hacker:add/bmi270-corewingf405wingv2

Conversation

@sensei-hacker

Copy link
Copy Markdown
Member

Summary

A new board revision of the CoreWing F405 Wing V2 ships with a BMI270 IMU instead of the ICM42688 (covered by USE_IMU_ICM42605). Users with the new revision have no working IMU with the current firmware.

Adding BMI270 defines on the same SPI1/CS pin (PA4) allows a single firmware image to serve both hardware revisions. INAV's boot-time auto-probe walks all USE_IMU_* defines and identifies the correct chip by its WHO_AM_I/CHIP_ID register — no conditional compilation required.

Changes

  • src/main/target/COREWINGF405WINGV2/target.h: Add USE_IMU_BMI270 block (SPI1, CS PA4, CW270_DEG) alongside the existing ICM42605 block

Testing

  • Target builds cleanly on release/9.1: 610 KB / 896 KB flash (68%), no errors or warnings
  • Pattern verified against DAKEFPVF722 which uses the identical dual ICM42605+BMI270 on SPI1/PA4 in production
  • Hardware testing required: a user with the new-revision board (BMI270 variant) should confirm IMU detection at boot. Existing ICM42688 boards are unaffected.

Notes

  • No changes to driver code — BMI270 driver already present in firmware
  • Existing ICM42688 boards: auto-probe finds ICM42605 match first, BMI270 probe returns false (different CHIP_ID register/value), no behaviour change

New board revision ships with BMI270 instead of ICM42688. Adding BMI270
defines on the same SPI1/PA4 allows a single firmware image to serve both
board revisions via INAV's auto-probe at boot.
@qodo-code-review

Copy link
Copy Markdown
Contributor

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

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

Test firmware build ready — commit 68f2797

Download firmware for PR #11638

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant