AEDROXH7 - Update config.h

[Aedrox-UAx]

config file updated (some 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

Release Notes

• New Features

  • Added On-Screen Display (OSD) support for enhanced flight information visualization.
  • Enabled barometer sensor support for improved altitude readings.
  • Added magnetometer support for better navigation.
  • Introduced camera switch control for convenient camera management.

• Chores

  • Updated hardware configuration and peripheral mappings.

[coderabbitai]

Caution

Review failed

Failed to post review comments

Walkthrough

Updated AEDROXH7 board configuration file with pin reassignments, OSD support via MAX7456, changed flash memory driver to W25N01G, added DPS368 barometer and magnetometer support, and introduced new camera switch control mapping.

Changes

Cohort / File(s)	Summary
Board Configuration configs/AEDROXH7/config.h	Remapped LED1_PIN (PE4→PC13), GYRO_1_CS_PIN (PA4→PB12), PINIO3_PIN (PB12→PB1); added MAX7456 OSD with SPI1 pins (PB3/PB4/PB5 for SCK/SDI/SDO, PE4 for CS); replaced flash driver (W25Q128FV+M25P16→W25N01G); added barometer DPS368 and magnetometer support; introduced PINIO4 with camera switch user control.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Add SPEDIXH743 #791: Adds MAX7456 OSD support and SPI1 pin mappings to a different board configuration with similar hardware enablement changes.

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 fails to provide meaningful details about the changes, stating only 'some minor changes' while the template is minimally filled with mostly boilerplate text and an uncompleted checklist.	Replace the boilerplate text with specific details about hardware changes, component updates, and a completed checklist confirming the required reviews and compliance measures have been addressed.
Title check	❓ Inconclusive	The title is generic and vague, using non-descriptive phrasing ('Update config.h') that doesn't convey the specific hardware changes made to the configuration file.	Consider a more specific title that highlights the main changes, such as 'AEDROXH7: Add OSD and DPS368 baro support, update pinouts' to better communicate the changeset's purpose.

✅ 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

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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