Flight Controller Config for AOCODARCF722V2

[OfficialNilabh]

Pull-Request requirements

Mandatory Review for All New Flight Controllers

• All new flight controllers must undergo the Betaflight review process, regardless of whether they use an existing target.
• Manufacturers may reuse the same target for multiple designs, but each new hardware release must be reviewed before approval.

Hardware Compliance Requirements

• All hardware must adhere to the Manufacturer Design Guidelines.
• Poor hardware designs will not be accepted, as outlined in the Requirements for the Submission of New and Updated Targets.
• Adhere to the [Config Target Guidance] https://betaflight.com/docs/development/manufacturer/config-target-guidance
• To avoid costly issues and delays, we strongly encourage consulting with Betaflight developers early in your design process and providing schematics for review before producing hardware.

These measures help maintain high standards and ensure compatibility within the Betaflight ecosystem.

If you have any questions or need guidance, feel free to reach out to the Betaflight development team.

Housekeeping

• Pull-Request only from a custom branch, not master.
• Replace this text with details of your own.

Checklist (✓/✕, or y/n)

• passed Betaflight team's schematics review
• passed hardware samples testing
• follows guidelines
• follows connector standards
• flight tested
• comments/issues resolved

Summary by CodeRabbit

• New Features
  • Added support for the AOCODARCF722V2 flight controller board with complete hardware configuration, including motor control, motion sensors (accelerometer and gyroscope), barometric pressure sensor, OSD display, and onboard storage capabilities.

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

Introduces a new configuration header for the AOCODARCF722V2 flight controller board targeting STM32F7X2 MCU. Defines hardware mappings including pin assignments for motors, UART/I2C/SPI peripherals, ADC channels, sensor interfaces, and timer configurations. Enables support for accelerometers, gyroscopes, flash memory, barometer, and OSD features.

Changes

Cohort / File(s)

Summary

AOCODARCF722V2 Board Configuration configs/AOCODARCF722V2/config.h

New board configuration header with MCU identification (STM32F7X2), manufacturer/board naming, and feature enablement macros for IMU sensors (MPU6500/6000, ICM42688P), flash (W25Q128FV), barometer (BMP280, DPS310), and MAX7456 OSD. Establishes comprehensive pin mappings for motors (8), UARTs (5), SPI (3), I2C, ADC inputs, and timer configurations. Configures peripheral instances (SPI, I2C, DMA) and default device sources for blackbox, DSHOT, and power metering.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• RADIOLINKF722 add W25Q128FV FLASH #1005: Adds the same W25Q128FV flash support macro across related board configurations, indicating coordinated flash peripheral enablement.
• Add new target DAKEFPVH743_SLIM. #926: Introduces similar comprehensive pin/macro mappings and peripheral instance configurations for other flight controller boards.

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes only the template text without any actual details about the submission. The author did not replace placeholder text with specifics about their hardware, testing, or compliance status as instructed.	Replace the template text with details about the AOCODARCF722V2 hardware, provide manufacturer information, confirm compliance with design guidelines, and check off applicable items in the checklist based on actual review and testing completion.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: adding a flight controller configuration for the AOCODARCF722V2 target, which matches the new config.h file introduced in this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

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

---

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

[ot0tot]

Does not follow manufacturer design guidelines.