AedroxH7. - Update config.h

[Aedrox-UAx]

Config file update (minor changes)

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

  • On-Screen Display (OSD) support is now available for displaying flight information in real-time
  • Camera switch functionality has been added for convenient control

• Improvements

  • Flash memory configuration updated for enhanced reliability
  • Hardware sensor compatibility refreshed

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

Configuration updates for the AEDROXH7 board including LED pin reassignment, SPI1 interface definition, gyro chip select pin change, flash memory chip replacement from W25Q128FV/M25P16 to W25N01G, MAX7456 OSD support with dedicated pins, barometer sensor addition, and PINIO adjustments with camera switch functionality.

Changes

Cohort / File(s)	Summary
AEDROXH7 Board Configuration configs/AEDROXH7/config.h	Updated hardware pin assignments: LED1_PIN (PE4→PC13), GYRO_1_CS_PIN (PA4→PB12), added SPI1 pins (SCK/SDI/SDO on PB3/PB4/PB5). Replaced flash memory support (W25Q128FV/M25P16→W25N01G). Added MAX7456 OSD with SPI1 instance and PE4 CS pin. Added DPS368 barometer. Modified PINIO3_PIN (PB12→PB1), added PINIO4_PIN (PD15) with box assignment 43 for camera switch.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add New Target DAKEFPVH743Pro #793: Updates board configuration to add/adjust SPI, MAX7456 OSD, flash, barometer, and PINIO macro definitions.
• Fix the config file of HAKRCF405V2 #828: Modifies board configuration headers to add BOX_USER and PINIO-related macro definitions.
• Add PrincipIoT H7 Pi target #1002: Updates board configuration macros including LED, SPI, GYRO CS, and sensor/flash/PIO settings across multiple boards.

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description contains only a placeholder statement 'Config file update (minor changes)' followed by boilerplate template text that was not replaced with actual PR details as instructed.	Replace the placeholder text with specific details about the hardware changes (SPI1 pins, OSD support, flash memory updates, etc.) and complete the checklist items to indicate review status.
Title check	❓ Inconclusive	The title is vague and generic—'Update config.h' does not specify which config or what changes were made, making it unclear to reviewers scanning history.	Replace with a more specific title like 'AedroxH7: Update config with SPI1, OSD, and barometer support' to clearly describe the main changes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
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.}

[ot0tot]

These changes are invalid. Please read and follow the Betaflight manufacturer design guidelines (https://www.betaflight.com/docs/development/manufacturer/manufacturer-design-guidelines).