Skip to content

Add HUMMINGBIRD_200RS #805

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

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

LYNHQQ
Copy link

@LYNHQQ LYNHQQ commented Jun 4, 2025

Add HUMMINGBIRD_200RS target

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features
    • Added support for the HUMMINGBIRD_200RS flight controller board, including sensor, flash memory, and on-screen display compatibility.
    • Configured motor, LED, UART, I2C, SPI, ADC, and other hardware pin assignments.
    • Enabled features such as DSHOT, ESC sensor, serial RX, blackbox logging to flash, and current/voltage monitoring.

Copy link

coderabbitai bot commented Jun 4, 2025

"""

Walkthrough

A new configuration header file for the HUMMINGBIRD_200RS flight controller board has been added. This file defines board-specific hardware settings, including MCU type, sensor and peripheral usage, pin assignments, timer mappings, default feature flags, and hardware resource allocations.

Changes

File(s) Change Summary
configs/HUMMINGBIRD_200RS/config.h Added configuration header for HUMMINGBIRD_200RS, specifying MCU, sensors, pins, peripherals, timer mappings, ADC/DMA settings, and default features.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Board_Config
    participant MCU
    participant Sensors
    participant Peripherals

    User->>Board_Config: Load HUMMINGBIRD_200RS/config.h
    Board_Config->>MCU: Define AT32F435G as target MCU
    Board_Config->>Sensors: Enable ICM42688P (gyro/accel) via SPI
    Board_Config->>Peripherals: Configure flash (M25P16, W25Q128FV, W25N01G), MAX7456 OSD, UART, I2C, SPI, ADC
    Board_Config->>Board_Config: Set pin assignments and timer mappings
    Board_Config->>Board_Config: Enable default features (DSHOT, serial RX, blackbox, etc.)
Loading

Possibly related PRs

  • Add New Target DAKEFPVH743Pro #793: Introduces a configuration header for another board, defining MCU, sensors, pins, and features.
  • add HDZERO_AIO15 #784: Adds a board config with ICM42688P gyro/accelerometer and similar hardware mapping for a different board.
  • Add AIKONF4V3 #715: Adds a new board configuration header with similar structure for a different flight controller board.

Suggested reviewers

  • haslinghuis
  • ot0tot
    """

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5b37452 and 90ca073.

📒 Files selected for processing (1)
  • configs/HUMMINGBIRD_200RS/config.h (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • configs/HUMMINGBIRD_200RS/config.h
✨ 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.

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: 0

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

43-56: Pin assignments are accurate but could be clearer.
All motor, LED, and UART pins appear correct. For maintainability, group related definitions under comments (e.g. // Motor pins, // LED pins, // UART pins) to improve readability.


59-67: SPI pin definitions are consistent.
Each SPI bus has its SCK/SDI/SDO mapping defined. Consider grouping or adding section headers per SPI instance for easier navigation.


103-105: User box configuration could use inline documentation.
PINIO1_BOX, PINIO1_CONFIG, and BOX_USER1_NAME are defined correctly, but adding a brief comment explaining their roles and valid value ranges would aid future maintainers.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7970f07 and 2154eb6.

📒 Files selected for processing (1)
  • configs/HUMMINGBIRD_200RS_AT32F435/config.h (1 hunks)
🔇 Additional comments (7)
configs/HUMMINGBIRD_200RS_AT32F435/config.h (7)

22-28: Target MCU and board identifiers look correct.
Values for FC_TARGET_MCU, BOARD_NAME, and MANUFACTURER_ID follow existing conventions and align with the hardware naming scheme.


29-42: Sensor and peripheral enable flags are properly defined.
All required USE_* macros for accelerometer, gyroscope, GPS, magnetometer, barometer, flash, and OSD (MAX7456) are present and correctly spelled.


69-76: ADC and chip-select pins appear correct.
Verify that PINIO1_PIN used for the “VTX 10V” feature matches the schematic and board silkscreen.


77-83: Timer pin mapping macro is well-formed.
The multi-line TIMER_PIN_MAPPING macro correctly omits a trailing backslash on the last entry to close the definition.


84-86: ADC instance and DMA option are valid.
ADC_INSTANCE = ADC1 with ADC1_DMA_OPT = 12 aligns with other STM32F4 configurations.


87-96: Clock and peripheral instances need verification.
Ensure SYSTEM_HSE_MHZ = 8 matches the external crystal on the board, and confirm that SPI1, SPI2, SPI4, I2CDEV_2, SERIAL_PORT_USART1, and USART2 assignments correspond to the actual hardware wiring.


97-103: Default features and meter scales require calibration.
The DEFAULT_VOLTAGE_METER_SCALE (110) and DEFAULT_CURRENT_METER_SCALE (307) should reflect the ADC divider and shunt resistor on this board—please verify these values with a test bench.

@osirisinferi
Copy link

osirisinferi commented Jun 5, 2025

I'm still afraid this looks like a duplicate of the NBD_HUMMINGBIRD200RS board added in #692, at least in name.

It has the same board name ("HummingBird 200 RS"), the same processor (AT32F435G) and seems to be made by the same manufacturer (NewBeeDrone). Just other pinouts.

Is the board you're adding now a "v2" version of the board added back in february perhaps?

Also, if this board is also made by NewBeeDrone (the pull request is coming from the newbeedrone Github fork), why not use the NEBD manufacturer ID? @LYNHQQ seems to indicate above that the manufacturer has changed, apparently to "HummingBird". That said, the only thing I can find is NewBeeDrone results when searching for HummingBird.. There's no "HummingBird" manufacturer website to be found. And Manufacturers.md would need to be updated.

@LYNHQQ
Copy link
Author

LYNHQQ commented Jun 5, 2025

我仍然担心这看起来像是 #692 中添加的板子的重复,至少在名称上是这样。NBD_HUMMINGBIRD200RS

它具有相同的板名(“HummingBird 200 RS”),相同的处理器 (AT32F435G),并且似乎由同一制造商 (NewBeeDrone) 制造。只是其他引脚。

您现在添加的板子是 2 月份添加的板子的“v2”版本吗?

另外,如果这个板子也是由 NewBeeDrone 制作的(拉取请求来自 Github 分叉),为什么不使用制造商 ID? 似乎在上面表明制造商已经改变,显然是 “HummingBird”。也就是说,我唯一能找到的就是在搜索HummingBird时得到的NewBeeDrone结果。没有找到“HummingBird”制造商网站。并且需要更新。Manufacturers.md

I'm still afraid this looks like a duplicate of the NBD_HUMMINGBIRD200RS board added in #692, at least in name.

It has the same board name ("HummingBird 200 RS"), the same processor (AT32F435G) and seems to be made by the same manufacturer (NewBeeDrone). Just other pinouts.

Is the board you're adding now a "v2" version of the board added back in february perhaps?

Also, if this board is also made by NewBeeDrone (the pull request is coming from the newbeedrone Github fork), why not use the NEBD manufacturer ID? @LYNHQQ seems to indicate above that the manufacturer has changed, apparently to "HummingBird". That said, the only thing I can find is NewBeeDrone results when searching for HummingBird.. There's no "HummingBird" manufacturer website to be found. And Manufacturers.md would need to be updated.

Please remove the NBD_HUMMINGBIRD 200 RS; it's deprecated and replaced by this current version. I apologize for not having specified this earlier – that was my error. Thanks for the reminder, @osirisinferi !

@LYNHQQ LYNHQQ closed this Jun 5, 2025
@LYNHQQ LYNHQQ reopened this Jun 5, 2025
@LYNHQQ LYNHQQ changed the title Add HUMMINGBIRD_200RS_ATF435 Add HUMMINGBIRD_200RS Jun 5, 2025
haslinghuis
haslinghuis previously approved these changes Jun 9, 2025
@haslinghuis haslinghuis dismissed their stale review June 9, 2025 15:07

Suggest renaming board to not conflict with existing board.

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.

4 participants