Skip to content

Add target HGLRC_F405_WING#11416

Open
HGLRC-T wants to merge 2 commits intoiNavFlight:maintenance-9.xfrom
HGLRC-T:add-HGLRC_F405_WING
Open

Add target HGLRC_F405_WING#11416
HGLRC-T wants to merge 2 commits intoiNavFlight:maintenance-9.xfrom
HGLRC-T:add-HGLRC_F405_WING

Conversation

@HGLRC-T
Copy link
Contributor

@HGLRC-T HGLRC-T commented Mar 10, 2026

This PR adds a new target for the HGLRC F405 Wing flight controller, a popular board for fixed-wing aircraft.

Hardware Overview

  • MCU: STM32F405RG
  • IMU: ICM42605 (SPI1, CS PA4, orientation CW270°)
  • Barometer: DPS310/SPL06 (I2C1)
  • Magnetometer: external I2C (all common types supported)
  • OSD: MAX7456 (SPI2, CS PB12)
  • SDCard: SPI3 (CS PC14) – blackbox logging enabled by default
  • Serial ports: VCP, UART1 (PA9/PA10), UART2 (PA2/PA3), UART3 (PC10/PC11), UART4 (PA0/PA1), UART5 (PC12/PD2)
  • PWM outputs: 11 channels (DShot capable, see target.c for timer mapping)
  • LED strip: PA8
  • ADC: VBAT (PC0), Current (PC1), RSSI (PC4), Airspeed (PC5)
  • Beeper: PC15 (inverted)
  • PINIO: CAM switcher (PC13), BEC switcher (PC6)

Configuration Highlights

  • Default receiver: CRSF on UART2
  • Default features: OSD, current meter, VBAT, telemetry, blackbox, airmode
  • PinIO boxes assigned to USER1 and USER2 for camera and BEC switching

Testing

  • Compiled successfully with current master
  • Verified pin mappings against board schematic
  • Basic functionality tested (UARTs, IMU, OSD, ADC) on actual hardware (if applicable, otherwise state that testing is pending)

Please review and merge. Thanks!

@github-actions
Copy link

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

  • maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

  • maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.


This is an automated suggestion to help route contributions to the appropriate branch.

@github-actions
Copy link

Test firmware build ready — commit d0bbb53

Download firmware for PR #11416

226 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.

Development build for testing only. Use Full Chip Erase when flashing.

@sensei-hacker sensei-hacker changed the base branch from master to maintenance-9.x March 10, 2026 03:33
@sensei-hacker
Copy link
Member

  • Samples received
  • Flash firmware
  • Calibrate
  • Orientation matches
  • Gyro working
  • Accel working
  • Baro working
  • Blackbox
  • UART1
  • UART2
  • UART3
  • UART4
  • UART6
  • UART7
  • UART8
  • Buzzer working
  • DShot support on m1-4
  • Additional motor / servo outputs
  • Voltage sensor
  • Current sensor
  • I2C Bus
  • Analog Camera working
  • Video Out working
  • OSD working
  • LEDs working
  • PINIO1
  • PINIO2

@sensei-hacker sensei-hacker added the New target This PR adds a new target label Mar 10, 2026
@HGLRC-T
Copy link
Contributor Author

HGLRC-T commented Mar 11, 2026

  • Samples received
  • Flash firmware
  • Calibrate
  • Orientation matches
  • Gyro working
  • Accel working
  • Baro working
  • Blackbox
  • UART1
  • UART2
  • UART3
  • UART4
  • UART6
  • UART7
  • UART8
  • Buzzer working
  • DShot support on m1-4
  • Additional motor / servo outputs
  • Voltage sensor
  • Current sensor
  • I2C Bus
  • Analog Camera working
  • Video Out working
  • OSD working
  • LEDs working
  • PINIO1
  • PINIO2

OK. Connect you with discord.

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

Labels

New target This PR adds a new target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants