For this HADES fixed-wing flight-control board, the firmware options that could work are:
- ArduPilot Plane — best fit if the board is intended for autonomous fixed-wing aircraft with waypoint navigation, takeoff/landing logic, payload control, servos, GPS, barometer, IMU, and telemetry.
- PX4 — also viable, especially if you want a more modular professional autopilot stack, but board bring-up can be more demanding.
- Custom STM32/embedded firmware — appropriate if this is a learning or experimental controller and you want direct control over IMU fusion, PWM outputs, sensor drivers, and failsafe behavior.
The board appears to include flight-controller-relevant peripherals such as IMU sensing, PWM/servo expansion, EEPROM, USB protection, pressure sensing, status LEDs, and external connectors, so ArduPilot Plane is likely the most practical target firmware if the main MCU is compatible.
To confirm firmware compatibility, the key items to verify are:
- Main MCU part number and flash/RAM size
- IMU model and bus connection
- Barometer/airspeed/pressure sensor connection
- PWM/servo output mapping
- RC input method: PWM, PPM, SBUS, CRSF, etc.
- GPS/UART mapping
- USB/UART bootloader support
- Power sensing inputs, if any
- I2C/SPI bus assignments
Recommended path:
- If the MCU is an STM32 commonly supported by ArduPilot/PX4, create a custom ArduPilot hwdef for HADES.
- Start with ArduPilot Plane, bring up power, clock, USB/UART console, then IMU, then PWM outputs, then GPS/telemetry.
- Only move to PX4 if you specifically need PX4’s architecture or ecosystem.
I can’t inspect or modify the project further from here, but the next concrete step is to generate a firmware bring-up document with the exact pin map and an ArduPilot/PX4 compatibility checklist from the schematic.