Skip to content

Add AXISFLYINGH7MINI #822

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

haslinghuis
Copy link
Member

@haslinghuis haslinghuis commented Jun 23, 2025

Summary by CodeRabbit

  • New Features
    • Added support for the AXISFLYINGH7MINI flight controller board, including configuration of sensors, peripherals, motor outputs, LEDs, UARTs, I2C, SPI, ADC inputs, and OSD device.
    • Enabled features such as blackbox logging, battery voltage and current monitoring, and beeper control for this board.

Copy link

coderabbitai bot commented Jun 23, 2025

Walkthrough

A new configuration header file for the AXISFLYINGH7MINI flight controller board has been introduced. This file defines the target MCU, board identifiers, sensor and peripheral enables, pin assignments, timer mappings, DMA options, UART/I2C/SPI assignments, default device settings, beeper configuration, and pin IO settings, centralizing all hardware-specific definitions.

Changes

File(s) Change Summary
configs/AXISFLYINGH7MINI/config.h New configuration header for AXISFLYINGH7MINI: sets MCU, board ID, enables sensors/peripherals, assigns pins, timers, DMA, UART/I2C/SPI, default device settings, beeper, and pin IO configs.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Firmware
    participant config.h

    User->>Firmware: Select AXISFLYINGH7MINI target
    Firmware->>config.h: Include board-specific config
    config.h-->>Firmware: Provide MCU, sensors, pin mappings, peripherals
    Firmware-->>User: Initializes board using provided configuration
Loading

Possibly related PRs

Suggested reviewers

  • ot0tot
  • nerdCopter
✨ Finishing Touches
  • 📝 Generate Docstrings

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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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.

Documentation and Community

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

@haslinghuis haslinghuis marked this pull request as draft June 23, 2025 18:35
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (3)
configs/AXISFLYINGH7MINI/config.h (3)

68-71: Document I2C bus usage.

Add inline comments indicating which sensors use I2C1 vs. I2C2 (e.g., barometer vs. external magnetometer) to aid future maintainers.


130-133: Reconsider default DSHOT implementation.

Hardware DSHOT support is available on STM32H7—using bitbang by default may underutilize built-in timers. Consider defaulting to hardware DSHOT or document why bitbang is preferred.


143-143: Add trailing newline.

Ensure the file ends with a newline to comply with POSIX text file conventions.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 96eebb9 and 4d5afcd.

📒 Files selected for processing (1)
  • configs/AXISFLYINGH7MINI/config.h (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
configs/AXISFLYINGH7MINI/config.h (1)
Learnt from: haslinghuis
PR: betaflight/config#0
File: :0-0
Timestamp: 2025-06-02T16:16:20.197Z
Learning: In STM32F405-based flight controller configurations, timer pin mappings must be carefully analyzed for DMA stream conflicts, especially between motor timers, LED strip timers, and SPI DMA assignments. Changes to TIMER_PIN_MAPPING should include verification that all required peripherals (motors, LED strip, blackbox SPI) can coexist without DMA conflicts.
🔇 Additional comments (8)
configs/AXISFLYINGH7MINI/config.h (8)

1-20: Skip license header review.

Standard GPL header appears consistent with other Betaflight configs.


22-28: Verify BOARD_NAME and MANUFACTURER_ID formatting.

Ensure these macros use the same literal style (e.g., quoted strings) as existing board configs for consistency in build scripts and UI display.


39-50: Validate motor & LED pin mappings against schematic.

Double-check that MOTOR1_PINMOTOR8_PIN and LED_STRIP_PIN assignments match the physical PCB silk-screen and that no GPIO remapping conflicts exist.


52-67: Missing UART5 pin assignments?

You specify TX/RX for USART1–4 and UART6–8 but skip USART5. Verify if USART5 is unavailable on STM32H743 or if its pins were overlooked.


103-112: Validate timer pin mapping against DMA streams.

Per retrieved learnings, confirm that the timers for motors (channels 0–7) and the LED strip (channel 8) do not share DMA streams used by SPI (flash, gyros, OSD) to avoid runtime collisions.


114-117: Confirm ADC DMA channel selections.

Ensure ADC1_DMA_OPT = 9, ADC2_DMA_OPT = 10, and ADC3_DMA_OPT = 11 correspond to the correct stream/channel mapping on STM32H743 so ADC sampling isn’t lost.


135-138: Verify PINIO box IDs.

Confirm that PINIO1_BOX = 40 and PINIO2_BOX = 41 align with the Betaflight UI/config schema for these configurable pins.


139-142: SPI instance assignments look correct.

GYRO_1_SPI_INSTANCE = SPI1 (PA5), GYRO_2_SPI_INSTANCE = SPI4 (PE12), FLASH_SPI_INSTANCE = SPI3 (PB3), and MAX7456_SPI_INSTANCE = SPI2 (PB13) align with the SCK pin definitions.

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.

1 participant