Add configuration file for AKINGF405HD

[haicheng0515-star]

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 AKINGF405HD flight controller board with integrated gyro, accelerometer, barometer, flash storage, and comprehensive peripheral connectivity including UARTs, I2C, SPI, and servo outputs.

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

This pull request adds a new board configuration file for the AKINGF405HD flight controller, defining the MCU (STM32F405), manufacturer (AKIN), and comprehensive hardware mappings for sensors, peripherals, pins, and communication interfaces.

Changes

Cohort / File(s)	Summary
AKINGF405HD Board Configuration configs/AKINGF405HD	Added complete hardware configuration with 131 lines defining MCU, board identity, sensor support (ICM42688P gyro/accel, BMP280 barometer, W25Q128FV flash, MAX7456 OSD), pin mappings for motors, servos, UARTs, I2C/SPI buses, and default peripheral/communication settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Create Add AKIN as a new manufacturer #1000 — Adds AKIN manufacturer to the public manufacturer list, directly complementing this new AKIN board configuration.
• Add GEPRC_TAKER_F405AIO config.h #951 — Introduces another STM32F405 board configuration with identical MCU, sensor types (ICM42688P, BMP280), and similar pin mapping/peripheral macros.
• Add AXISFLYING ARGUS ECO F4 #780 — Adds a new STM32F405 board with the same sensor support (ICM42688P, BMP280, W25Q128FV flash, MAX7456) and comparable configuration patterns.

Suggested labels

Awaiting prototype samples

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The pull request description follows the template structure but does not replace the template text with specific project details as instructed. The checklist is partially completed but lacks substantive information about the submission.	Replace the template instructions with specific details about the AKINGF405HD submission, including rationale, hardware specifications, and clear answers to all checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly summarizes the main change: adding a configuration file for the AKINGF405HD flight controller board.
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 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.}