ADD NEW TARGET HUMMINGBIRD_FC305 #10954

LYNHQQ · 2025-07-08T01:58:08Z

User description

add target hummingbird fc305

PR Type

Enhancement

Description

Add complete target support for HUMMINGBIRD_FC305 flight controller
Configure ICM42605 IMU, SPL06 barometer, and MAX7456 OSD
Set up 6 UART ports with CRSF receiver on UART6
Enable SD card logging and LED strip support

Changes diagram

flowchart LR
  A["New Target"] --> B["Hardware Config"]
  B --> C["SPI Devices"]
  B --> D["I2C Sensors"]
  B --> E["UART Ports"]
  C --> F["ICM42605 IMU"]
  C --> G["MAX7456 OSD"]
  C --> H["SD Card"]
  D --> I["SPL06 Baro"]
  E --> J["CRSF RX"]

Changes walkthrough 📝

Relevant files

Configuration changes

target.h `Main target hardware configuration definitions` src/main/target/HUMMINGBIRD_FC305/target.h Define board identifier and USB product string Configure SPI buses for IMU, OSD, and SD card Set up I2C bus for barometer and magnetometer Define 6 UART ports with CRSF receiver configuration Enable LED strip, ADC channels, and default features	+163/-0
target.c `Hardware device registration and timer setup` src/main/target/HUMMINGBIRD_FC305/target.c Register SPI devices for ICM42605 IMU, SD card, MAX7456 OSD Register I2C device for SPL06 barometer Define timer hardware for 4 motor outputs and LED strip	+41/-0
config.c `Target-specific default configuration settings` src/main/target/HUMMINGBIRD_FC305/config.c Set SPL06 as default barometer hardware Configure UART4 for ESC serial communication Set up PINIO box for permanent user control	+33/-0
CMakeLists.txt `CMake build configuration` src/main/target/HUMMINGBIRD_FC305/CMakeLists.txt Add CMake target definition for STM32F722XE processor	+2/-0

Need help?
Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
Check out the documentation for more information.

qodo-merge-pro · 2025-07-08T01:58:41Z

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review Device Mismatch The ICM42605 device is registered with variable name `busdev_icm42688` which suggests ICM42688 hardware, but the device type is DEVHW_ICM42605. This naming inconsistency could lead to confusion during maintenance. BUSDEV_REGISTER_SPI_TAG(busdev_icm42688, DEVHW_ICM42605, ICM42605_SPI_BUS, ICM42605_CS_PIN, NONE, 0, DEVFLAGS_NONE, IMU_ICM42605_ALIGN); BUSDEV_REGISTER_SPI(busdev_sdcard_spi, DEVHW_SDCARD, SDCARD_SPI_BUS, SDCARD_CS_PIN, NONE, DEVFLAGS_SPI_MODE_0, 0); Duplicate Definition USE_OSD is defined twice in the file, once at line 81 and again at line 161. This redundant definition should be removed to avoid potential compilation issues. #define USE_OSD #define USE_DSHOT

qodo-merge-pro · 2025-07-08T01:59:16Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Fix device name inconsistency The variable name `busdev_icm42688` doesn't match the device type `DEVHW_ICM42605`. This inconsistency could cause confusion and potential issues when referencing the device. src/main/target/HUMMINGBIRD_FC305/target.c [27] -BUSDEV_REGISTER_SPI_TAG(busdev_icm42688, DEVHW_ICM42605, ICM42605_SPI_BUS, ICM42605_CS_PIN, NONE, 0, DEVFLAGS_NONE, IMU_ICM42605_ALIGN); +BUSDEV_REGISTER_SPI_TAG(busdev_icm42605, DEVHW_ICM42605, ICM42605_SPI_BUS, ICM42605_CS_PIN, NONE, 0, DEVFLAGS_NONE, IMU_ICM42605_ALIGN); Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a naming inconsistency between the registered device `busdev_icm42688` and its type `DEVHW_ICM42605`, improving code clarity and preventing potential future bugs.	Medium
	✅ ~~Remove duplicate macro definition~~ Suggestion Impact: The commit removed the duplicate USE_OSD macro definition as suggested, eliminating the redundant definition code diff: -#define USE_OSD The `USE_OSD` macro is defined twice in the file. This duplication is unnecessary and could lead to preprocessor warnings or confusion during compilation. src/main/target/HUMMINGBIRD_FC305/target.h [81-161] #define USE_OSD #define USE_MAX7456 -MAX7456_SPI_BUS BUS_SPI3 +#define MAX7456_SPI_BUS BUS_SPI3 #define MAX7456_CS_PIN PC13 -... -#define USE_OSD `[To ensure code accuracy, apply this suggestion manually]` Suggestion importance[1-10]: 4 __ Why: The suggestion correctly identifies that the `USE_OSD` macro is defined twice (lines 81 and 161), and removing the redundant definition improves code quality.	Low
	Fix inconsistent indentation formatting The line contains mixed tabs and spaces for indentation, which can cause formatting inconsistencies. Use consistent spacing to match the surrounding code style. src/main/target/HUMMINGBIRD_FC305/target.h [83] -#define MAX7456_SPI_BUS BUS_SPI3 +#define MAX7456_SPI_BUS BUS_SPI3 Apply / Chat Suggestion importance[1-10]: 3 __ Why: The suggestion correctly points out inconsistent use of tabs and spaces for alignment on line 83, and fixing it improves code style and readability.	Low
Update

sensei-hacker · 2025-08-30T22:37:36Z

sensei-hacker · 2025-08-30T23:07:07Z

In testing, the OSD does not seem to function for me. I see the board does not have the standard MAX7456 chip?

sensei-hacker · 2025-08-31T01:24:13Z

For the motor order to match the silkscreen, please see:
newbeedrone#1

HUMMINGBIRD_FC305 motor order

LYNHQQ · 2025-09-22T01:51:46Z

在测试中，OSD 似乎对我不起作用。我看到电路板没有标准的MAX7456芯片？

Hi, please add:
BUSDEV_REGISTER_SPI(busdev_max7456, DEVHW_MAX7456, MAX7456_SPI_BUS, MAX7456_CS_PIN, NONE, DEVFLAGS_USE_RAW_REGISTERS, 0);

sensei-hacker · 2025-10-25T21:44:13Z

The one thing I can't confirm by testing is the external i2c. The sample may have had a fault before that test could be completed. @LYNHQQ can you please confirm you have tested the i2c pads with this target?

LYNHQQ · 2025-10-27T11:30:24Z

The one thing I can't confirm by testing is the external i2c. The sample may have had a fault before that test could be completed. @LYNHQQ can you please confirm you have tested the i2c pads with this target?

Hi @sensei-hacker , the sample is brand new. If it has any issues, could you please consider testing it with the Betaflight firmware? It has the barometer connected by default. If it doesn't work, please feel free to contact me, and I will arrange for a new sample to be sent to you for testing

sensei-hacker · 2025-10-28T04:32:54Z

The one thing I can't confirm by testing is the external i2c. The sample may have had a fault before that test could be completed. @LYNHQQ can you please confirm you have tested the i2c pads with this target?

Hi @sensei-hacker , the sample is brand new. If it has any issues, could you please consider testing it with the Betaflight firmware? It has the barometer connected by default. If it doesn't work, please feel free to contact me, and I will arrange for a new sample to be sent to you for testing

I understand it was new. I am hesitant to connect the faulted board to power again since it already burned up one of my testers.

Would you be able to simply test the external i2c pads with the INAV target to confirm it works for you?

LYNHQQ · 2025-10-28T09:13:20Z

The one thing I can't confirm by testing is the external i2c. The sample may have had a fault before that test could be completed. @LYNHQQ can you please confirm you have tested the i2c pads with this target?

Hi @sensei-hacker , the sample is brand new. If it has any issues, could you please consider testing it with the Betaflight firmware? It has the barometer connected by default. If it doesn't work, please feel free to contact me, and I will arrange for a new sample to be sent to you for testing

I understand it was new. I am hesitant to connect the faulted board to power again since it already burned up one of my testers.

Would you be able to simply test the external i2c pads with the INAV target to confirm it works for you?

Hi @sensei-hacker , I'm aware of the situation and will be running some tests on it. This will take some time

LYNHQQ · 2025-10-30T02:44:30Z

我无法通过测试确认的一件事是外部 i2c。在完成测试之前，样品可能出现了故障。您能否确认您已经使用此目标测试了 I2C 焊盘？

嗨，样品是全新的。如果有任何问题，您能考虑使用 Betaflight 固件进行测试吗？它默认连接了气压计。如果不起作用，请随时与我联系，我会安排将新样品发送给您进行测试

我知道这是新的。我犹豫是否要再次将有故障的电路板连接到电源，因为它已经烧毁了我的一个测试仪。

您是否可以简单地使用 INAV 目标测试外部 i2c 焊盘，以确认它适合您？

Hi @sensei-hacker , I've re-tested it, and it seems to be working correctly now. I have registered the I2C bus to the MAG, and everything looks good. Please feel free to contact me if you have any new questions or need new samples.

sensei-hacker · 2025-10-30T02:52:24Z

Thank you very much.

LYNHQQ · 2025-10-30T02:54:20Z

谢谢。

Hold on, I need to add it to target.h.

sensei-hacker · 2025-10-30T03:00:41Z

Oh, I didn't realize a change was needed. Sorry about that.
Since I already merged this PR, we'll have a new very small PR for whatever needs to change.

LYNHQQ · 2025-10-30T03:35:33Z

哦，我没有意识到需要改变。对不起。由于我已经合并了这个 PR，我们将有一个新的非常小的 PR 来处理任何需要更改的内容。

Thanks a lot for your help. I will open a new PR to address this.

Add target HUMMINGBIRD_FC305

599f414

qodo-merge-pro bot added the Review effort 2/5 label Jul 8, 2025

sensei-hacker added the New target This PR adds a new target label Jul 8, 2025

Remove duplicate definitions of USEr OSD and USE_RANGEFINDER

0df216f

HUMMINGBIRD_FC305 motor order

8bda6f0

Merge pull request #1 from sensei-hacker/target/hummingbird_fc305

5fa112a

HUMMINGBIRD_FC305 motor order

sensei-hacker self-assigned this Oct 30, 2025

sensei-hacker added this to the 9.0 milestone Oct 30, 2025

sensei-hacker merged commit af0765d into iNavFlight:master Oct 30, 2025
21 checks passed

ADD NEW TARGET HUMMINGBIRD_FC305 #10954

ADD NEW TARGET HUMMINGBIRD_FC305 #10954

Uh oh!

Conversation

LYNHQQ commented Jul 8, 2025 • edited by qodo-merge-pro bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

PR Type

Description

Changes diagram

Changes walkthrough 📝

Uh oh!

qodo-merge-pro bot commented Jul 8, 2025

PR Reviewer Guide 🔍

Uh oh!

qodo-merge-pro bot commented Jul 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Code Suggestions ✨

Uh oh!

sensei-hacker commented Aug 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sensei-hacker commented Aug 30, 2025

Uh oh!

sensei-hacker commented Aug 31, 2025

Uh oh!

LYNHQQ commented Sep 22, 2025

Uh oh!

sensei-hacker commented Oct 25, 2025

Uh oh!

LYNHQQ commented Oct 27, 2025

Uh oh!

sensei-hacker commented Oct 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LYNHQQ commented Oct 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LYNHQQ commented Oct 30, 2025

Uh oh!

sensei-hacker commented Oct 30, 2025

Uh oh!

Uh oh!

LYNHQQ commented Oct 30, 2025

Uh oh!

sensei-hacker commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LYNHQQ commented Oct 30, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

LYNHQQ commented Jul 8, 2025 •

edited by qodo-merge-pro bot

Loading

qodo-merge-pro bot commented Jul 8, 2025 •

edited

Loading

sensei-hacker commented Aug 30, 2025 •

edited

Loading

sensei-hacker commented Oct 28, 2025 •

edited

Loading

LYNHQQ commented Oct 28, 2025 •

edited

Loading

sensei-hacker commented Oct 30, 2025 •

edited

Loading