Skip to content

Conversation

@HGLRC-T
Copy link
Contributor

@HGLRC-T HGLRC-T commented Aug 18, 2025

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

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 HGLRC H743 flight controller.
    • Enabled IMU (ICM42688P) and barometer (DPS310) with predefined I2C assignments.
    • Integrated on-screen display via MAX7456.
    • Enabled onboard flash logging with flash set as the default Blackbox target.
    • Preconfigured motor, servo, LED, beeper, and LED strip outputs.
    • Provided multiple UART and SPI/I2C ports for peripherals.
    • Set default current/voltage meters and scales for plug‑and‑play telemetry.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 18, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Adds new STM32H743 board configuration headers defining MCU/board identifiers, enabled sensors/peripherals, SPI/UART/I2C/ADC pin mappings, timer-to-pin map, DMA options, default blackbox/current/voltage settings, PINIO boxes, LEDs, motors/servos, beeper, and 8 MHz HSE clock. Includes commented optional features (e.g., SDIO, BMP280).

Changes

Cohort / File(s) Summary of changes
New board target: HGLRCH743
configs/HGLRCH743/config.h
Introduces HGLRCH743 board header with MCU/board IDs, USE_* feature flags (ICM42688P, DPS310, MAX7456, W25Q128FV), extensive pin mappings (SPI1–3, UART1–8, I2C1–2, ADCs, LEDs, motors/servos, beeper, PINIO), TIMER_PIN_MAPPING, DMA opts, meter defaults, blackbox to flash, 8 MHz HSE.
Global configs header addition
configs/config.h
Adds a configuration header mirroring H743 target settings: identifiers, sensor/peripheral enables, SPI/UART/I2C/power pins, TIMER_PIN_MAPPING, meter defaults, PINIO boxes, blackbox, and clock; includes commented optional peripherals.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

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

📒 Files selected for processing (2)
  • configs/HGLRCH743/config.h (1 hunks)
  • configs/config.h (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
🪧 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
Copy link

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

@github-actions github-actions bot closed this Aug 18, 2025
@haslinghuis
Copy link
Member

@HGLRC-T - kindly read comment above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants