Add MicoAir743v2 board

[khoazero123]

Add MicoAir743v2 Flight Controller Support

This PR adds support for the MicoAir743v2 flight controller from MicoAir Tech.

Board Information

The MicoAir743v2 is a high-performance H7-based flight controller featuring:

• MCU: STM32H743VIT6 (480MHz, 2MB Flash)
• IMU: BMI270 (SPI3)
• Barometer: SPL06 (I2C2)
• Magnetometer: QMC5883L (I2C2, internal)
• OSD: AT7456E (SPI1)
• Storage: MicroSD card slot (SDIO)
• Connectivity: 8x UART, 1x I2C, Bluetooth telemetry (UART8)
• PWM Outputs: Up to 8 motor outputs
• Power: 5V 3A BEC, 12V 3A BEC
• Battery: 2-6S LiPo support (6-27V)

Board Variants

Three board configurations are provided:

1. MICOAIR743V2_INTMAG - Internal magnetometer variant (QMC5883L on I2C2)
2. MICOAIR743V2_EXTMAG - External magnetometer variant (for use with external I2C compass)

Pin Mapping

• Motors: PE14, PE13, PE11, PE9, PB1, PB0, PD12, PD13
• UARTs: All 8 UARTs properly mapped with TX/RX pins
• I2C: I2C1 (PB8/PB9) and I2C2 (PB10/PB11)
• SPI: SPI1 (OSD), SPI3 (Gyro)
• ADC: PC0 (VBAT), PC1 (Current)

Source

Configuration files are based on the official MicoAir743v2 repository:

• Board specifications: https://micoair.com/flightcontroller_micoair743v2/
• Source reference: https://github.com/micoair/MicoAir743v2

Summary by CodeRabbit

Release Notes

• New Features
  • Added support for MICOAIR743V2 flight controller with external magnetometer configuration
  • Added support for MICOAIR743V2 flight controller with internal magnetometer configuration

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

Two new target-specific configuration headers for Betaflight flight controller boards MICOAIR743V2 (STM32H743), with external magnetometer (EXTMAG) and internal magnetometer (INTMAG) variants, defining MCU identity, peripheral enablement, pin mappings, timer configurations, and UART port assignments.

Changes

Cohort / File(s)

Summary

MICOAIR743V2 Board Configuration configs/MICOAIR743V2_EXTMAG/config.h, configs/MICOAIR743V2_INTMAG/config.h

New target-specific configuration headers for STM32H743-based flight controller boards with full hardware abstraction layer setup including MCU/board identity, accelerometer/gyroscope BMI270, SD card, MAX7456, and magnetometer (external or internal). Extensive pin mappings for motors M1–M8, UARTs 1–8 (TX/RX pairs), I2C (SCL/SDA), SPI instances (SPI1, SPI3 with SCK/SDI/SDO), and SDIO signals. Defines LED, beeper, gyro CS/EXTI, MAX7456 CS, and IO pins with corresponding TIMER_PIN_MAPPING entries. Configures DMA options, peripheral instances (GYRO via SPI3, MAX7456 via SPI1, SDIO 4-bit), magnetometer I2C configuration, beeper polarity, and default measurement sources/scales for current and voltage meters. Assigns MSP, GPS, SERIALRX, ESC sensor, and UART ports to specific SERIAL_PORT entries.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–25 minutes

• Pin mapping verification across multiple categories (motors, UARTs, I2C, SPI, SDIO, LED, beeper, gyro CS/EXTI)
• Timer channel assignments for motors and LED/beeper
• Peripheral instance selections and DMA configuration
• Detailed comparison between EXTMAG and INTMAG variants to verify expected differences (especially magnetometer configuration)
• Default measurement sources, scale factors, and UART port assignments

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provides comprehensive board information, hardware specifications, and pin mappings, but does not address the mandatory checklist items required by the template (schematics review, hardware testing, compliance verification).	Complete the mandatory checklist from the template, explicitly confirming schematics review, hardware testing, guideline compliance, connector standards adherence, and flight testing status.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add MicoAir743v2 board' directly and clearly describes the main change—introducing support for a new flight controller board.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sugaarK]

all new targets require schematic approval by the bf team

as outlined in the online documentation

https://www.betaflight.com/docs/development/manufacturer/config-target-guidance