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)

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

Summary by CodeRabbit

• New Features
  • Added support for the AKINGF405HD flight controller board featuring STM32F405 MCU with integrated 6-axis IMU, barometer, flash storage, and OSD support. Includes multiple communication interfaces (UART, I2C, SPI) with preset default configurations for optimal operation.

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

A new Betaflight target configuration file is added for the AKINGF405HD flight controller board. The file contains hardware definitions including MCU type (STM32F405), manufacturer identifier, sensor and peripheral configurations, pin mappings for motors/servos/UARTs/I2C/SPI interfaces, timer assignments, and default operating parameters.

Changes

Cohort / File(s)	Summary
New Board Configuration configs/AKINGF405HD	Adds complete hardware configuration for STM32F405-based AKINGF405HD flight controller, including MCU type, sensor definitions (ICM42688P gyro/accel, BMP280 barometer, W25Q128FV flash, MAX7456 OSD), pin mappings for motors/servos/UARTs/I2C/SPI, timer-to-pin associations via TIMER_PIN_MAPPING, and default parameters (current meter scale, DSHOT modes, blackbox device).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related issues

• Verify and add missing HSE defines to these targets #1008: This PR adds SYSTEM_HSE_MHZ = 8 to the new AKINGF405HD configuration, directly addressing the missing HSE define requirement for STM32F4/G4 target configs.

Possibly related PRs

• Create Add AKIN as a new manufacturer #1000: Related through shared manufacturer identifier AKIN; PR #1000 defines the manufacturer entry while this PR uses it in the new board configuration.
• Add AXISFLYING ARGUS ECO F4 #780: Both PRs add STM32F405-based board configuration headers with nearly identical macro patterns (sensor definitions, pin mappings, TIMER_PIN_MAPPING, SPI/I2C instances, HSE settings, and default values).
• Add AIRBRAINH743 #924: Related through overlapping board configuration macro definitions such as USE_GYRO_SPI_ICM42688P, TIMER_PIN_MAPPING, and GYRO_1_SPI_INSTANCE.

Suggested labels

Schematics Approved

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes the template requirements and checklist items are marked as completed, but lacks specific details about the hardware implementation, design rationale, and actual changes made.	Replace template boilerplate with concrete details: describe the specific hardware configuration, explain why these design choices were made, and summarize what was changed in this PR beyond the checklist confirmation.

✅ Passed checks (2 passed)

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