Add ATOMRCF405NAVI target

[Mick51]

New target for the AtomRC F405 NAVI (STM32F405, BMI270, MAX7456, SD card). Ported from the INAV ATOMRCF405NAVI target definition.

Tested on real hardware: builds and flashes cleanly, gyro/acc/baro/mag detected, SD card blackbox working, fixed-wing mixer running 2 motors (S1/S2) and 3 servos (S3/S4/S5).

Submitted under COMM as AtomRC is not a registered manufacturer ID.

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 ATOMRCF405NAVI flight controller target.
  • Enabled wing and servo functionality, including motor, servo, LED, and receiver support.
  • Added support for onboard sensors, barometers, magnetometers, OSD, SD cards, and flash storage.
  • Configured communication interfaces, telemetry, voltage/current monitoring, and DShot operation.

[coderabbitai]

Walkthrough

Adds the ATOMRCF405NAVI Betaflight target configuration for an STM32F405 board. The configuration defines board metadata, enabled hardware features, GPIO and timer mappings, sensor and storage interfaces, receiver and meter defaults, DShot behavior, and the system clock.

Changes

ATOMRCF405NAVI target

Layer / File(s)	Summary
Board target definition configs/COMM/ATOMRCF405NAVI/config.h	Adds the complete STM32F405 target configuration, including feature flags, pin assignments, timers, ADC/DMA settings, sensors, communication buses, storage, OSD, receiver, DShot, voltage/current meters, and the 8 MHz system clock.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• betaflight/config#1150: Adds another board-specific Betaflight target configuration with peripheral, pin, timer, and feature macros.
• betaflight/config#1160: Adds another target configuration with board-specific hardware and feature definitions.
• betaflight/config#1172: Adds another target configuration with MCU, peripheral, pin, timer, and feature macros.

Suggested reviewers: nerdcopter, vitroidfpv, sugaark

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the addition of the ATOMRCF405NAVI target.
Description check	✅ Passed	The description explains the target, hardware, testing results, submission rationale, and checklist status.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Warning

CodeRabbit couldn't request changes on this pull request because it doesn't have sufficient GitHub permissions.

Please grant CodeRabbit Pull requests: Read and write permission and re-run the review.

👉 Steps to fix this

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@configs/COMM/ATOMRCF405NAVI/config.h`:
- Around line 50-52: Remove the conflicting USE_FLASH and USE_FLASH_W25Q128FV
definitions alongside USE_SDCARD if this board has no separate flash chip;
otherwise configure the flash with its actual SPI instance and a chip-select pin
distinct from SDCARD_SPI_CS_PIN/PB6.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5b1d7cdd-e8dc-4513-b964-1920de69a24f

📥 Commits

Reviewing files that changed from the base of the PR and between 749fff1 and c69b9b9.

📒 Files selected for processing (1)

• configs/COMM/ATOMRCF405NAVI/config.h