Add HGLRCH743 config.h file

[HGLRC-T]

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 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 HGLRCH743 flight controller, including accelerometer/gyroscope, DPS310 barometer, MAX7456 OSD, and on-board flash as the default Blackbox device.
  • Comprehensive pin mappings for 8 motors, 4 servos, beeper (inverted), LED strip, and status LEDs.
  • Extensive connectivity: UART1–8, I2C1–2, and SPI buses with device chip-selects.
  • ADC monitoring for VBAT, current, and RSSI, with default meter sources and scales.
  • Timer mappings and 8 MHz external clock configuration.

• Chores

  • Added a minor placeholder text file.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds a new STM32H743 board configuration for HGLRCH743, defining board identifiers, enabled peripherals, SPI/I2C/UART/ADC pin mappings, timer mappings, defaults (meters, blackbox), and clock. Introduces two config headers with largely overlapping content and a trivial text file containing “123”.

Changes

Cohort / File(s)	Summary
Board configuration: HGLRCH743 configs/HGLRCH743/config.h	New board config header for STM32H743-based HGLRCH743: defines MCU/board/manufacturer, enables ACC/GYRO (ICM42688P), BARO (DPS310), MAX7456, FLASH (W25Q128FV); maps SPI1/2/3 with CS lines; defines beeper, 8 motors, LED strip, 4 servos, UART1–8, I2C1–2, LEDs, ADCs; timer pin mapping; DMA opts; default meters/scales; blackbox to flash; 8 MHz HSE; beeper inverted.
Global/duplicate config header configs/config.h	Adds another config header with near-identical HGLRCH743 definitions and mappings as above, duplicating board-specific configuration in a different path.
Misc text teeeeeeeee.txt	New file containing “123”.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Add HAKRCH743 #757 — Adds a similar STM32H743 board config header with comparable macros, buses, and timer mappings.
• Add New Target DAKEFPVH743Pro #793 — Introduces another STM32H743 board config file defining the same categories of macros and peripherals.
• add new sensors to target for Hobbywing #838 — Adds identical sensor enable macros (ICM42688P, DPS310) in board configs.

Suggested reviewers

• haslinghuis
• ot0tot
• nerdCopter

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between df10848 and 645dbbf.

📒 Files selected for processing (3)

• configs/HGLRCH743/config.h (1 hunks)
• configs/config.h (1 hunks)
• teeeeeeeee.txt (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• 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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary or `` to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Auto-closing pull request because the source branch is named 'master'. Please create a feature branch instead. https://betaflight.com/docs/development#using-git-and-github