Add ORBITH743v2 target

[orbittechnologyx]

Summary

This PR adds support for the ORBITH743v2 flight controller board.

ORBITH743v2 is a revised version of the ORBITH743 board and is based on the STM32H743VIT6 MCU.

Changes compared to ORBITH743:

• Replaced dual ICM42688P configuration with ICM42688P + ICM40609D
• Replaced DPS310 barometer with SPL06
• Replaced 256 MByte FRAM with 16 MByte FRAM
• Added dedicated external connectors for GPS and UART peripherals

The board has been tested successfully on hardware and all functions are operating as expected.

[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.

[github-actions]

Test firmware build ready — commit a725524

Download firmware for PR #11701

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.

[sensei-hacker]

Just an FYI for contributors: The tentative schedule for INAV 10 is to have a full release in mid December. That means RC2 needs to be in early to mid November, which places INAV 10.0RC1 at September 1. Please plan to have any new features for INAV 10.0 ready for RC1 no later than September 1. After that, 10.1 will follow about six to seven months later.