* feat(bl_update): pet the watchdog during erase and program CAN nodes start the IWDG in the bootloader, and nothing else pets it while bl_update holds the scheduler lock. Assisted-by: Claude:claude-opus-5-5 * feat(nuttx): emit canbootloader to board extras and build bootloader+app image canbootloader builds now write extras/<vendor>_<board>_bootloader.bin like FMU bootloader builds do, which plugs CAN nodes into the existing ROMFS / rc.board_bootloader_upgrade / jlink wiring. CAN node app builds with that file also emit <config>_with_bootloader.bin (bootloader padded to the app's ELF load address, followed by the CRC'd image) so a bare board is flashed in one SWD step instead of two. Assisted-by: Claude:claude-opus-5-5 * feat(cannode): run rc.board_bootloader_upgrade at startup The hook was only wired into the FMU rcS, so SYS_BL_UPDATE did nothing on CAN nodes even with bl_update built in. * feat(ark): enable bootloader update on CAN nodes Ships the CAN bootloader in the app ROMFS so a node can rewrite it via SYS_BL_UPDATE without SWD. Assisted-by: Claude:claude-opus-5-5 * docs(dronecan): bootloader update and combined image for CAN nodes Assisted-by: Claude:claude-opus-5-5 * build(ark): rebuild CAN node bootloaders from current main The committed binaries predated the F412 chip-selection and linker fixes and the NuttX 12.12 upgrade, so they no longer matched the source. Assisted-by: Claude:claude-opus-5-5 * feat(uavcannode): update the bootloader as soon as SYS_BL_UPDATE is set Same approach as AP_Periph. Running the update on the next boot needed two reboots and reported nothing over CAN: it ran before uavcannode started, and the boot script printed "done" even when bl_update failed. The node now flashes while running, skips an identical bootloader, and the result reaches the flight controller through the existing log message forwarding. A value left set from before boot is cleared rather than acted on. The flash routine moves into a library so uavcannode can call it. Assisted-by: Claude:claude-opus-5-5 * docs(dronecan): note that the combined CAN node image resets parameters Found on the bench: the padding between bootloader and app covers the parameter sectors, so every SWD flash of the combined image erases them. Assisted-by: Claude:claude-opus-5-5 * fix(nuttx): limit CAN bootloader extras and combined image to STM32 Every canbootloader build wrote its binary to the board's extras, so a later nxp_ucans32k146 default or cyphal configure picked it up and failed in prepend_bootloader.py: the S32K application loads at 0x6000, below the 0x08000000 base the script and bl_update assume. CI only passed because the canbootloader was built after both had configured. Assisted-by: Claude:claude-fable-5-1 * fix(bl_update): pad the image before erasing and warn on every flash failure The STM32F4 up_progmem_write() returns -EINVAL for an odd byte count, which was only found out after sector 0 had been erased. An erase or program failure also leaves the board without a bootloader, but only a verify failure told the user to retry before rebooting. Assisted-by: Claude:claude-fable-5-1 * fix(romfs): pack rc.board_bootloader_upgrade only where rcS runs it CAN nodes with bl_update carried the script in their ROMFS although the cannode rcS never sources it: uavcannode flashes the bootloader itself. Assisted-by: Claude:claude-fable-5-1 * refactor(bl_update): move the flash routine to src/lib The library lived under systemcmds, which is configured after drivers, so uavcannode could only link it through a forward reference. The watchdog is now selected by chip because the platform targets do not exist yet when src/lib is configured. Assisted-by: Claude:claude-fable-5-1 * docs(dronecan): the CAN bootloader is written to extras on STM32 only Assisted-by: Claude:claude-fable-5-1
The autopilot stack the industry builds on.
About
PX4 is an open-source autopilot stack for drones and unmanned vehicles. It supports multirotors, fixed-wing, VTOL, rovers, and many more experimental platforms from racing quads to industrial survey aircraft. It runs on NuttX, Linux, and macOS. Licensed under BSD 3-Clause.
Why PX4
Modular architecture. PX4 is built around uORB, a DDS-compatible publish/subscribe middleware. Modules are fully parallelized and thread safe. You can build custom configurations and trim what you don't need.
Wide hardware support. PX4 runs on a wide range of autopilot boards and supports an extensive set of sensors, telemetry radios, and actuators through the Pixhawk ecosystem.
Developer friendly. First-class support for MAVLink and DDS / ROS 2 integration. Comprehensive SITL simulation, hardware-in-the-loop testing, and log analysis tools. An active developer community on Discord and the weekly dev call.
Vendor neutral governance. PX4 is hosted under the Dronecode Foundation, part of the Linux Foundation. Business-friendly BSD-3 license. No single vendor controls the roadmap.
Supported Vehicles
|
Multicopter |
Fixed Wing |
VTOL |
Rover |
…and many more: helicopters, autogyros, airships, submarines, boats, and other experimental platforms. These frames have basic support but are not part of the regular flight-test program. See the full airframe reference.
Try PX4
Run PX4 in simulation with a single command. No build tools, no dependencies beyond Docker:
docker run --rm -it -p 14550:14550/udp px4io/px4-sitl:latest
Open QGroundControl and fly. See PX4 Simulation Quickstart for more options.
Build from Source
git clone https://github.com/PX4/PX4-Autopilot.git --recursive
cd PX4-Autopilot
make px4_sitl
Note
See the Development Guide for toolchain setup and build options.
Documentation & Resources
| Resource | Description |
|---|---|
| User Guide | Build, configure, and fly with PX4 |
| Developer Guide | Modify the flight stack, add peripherals, port to new hardware |
| Airframe Reference | Full list of supported frames |
| Autopilot Hardware | Compatible flight controllers |
| Release Notes | What's new in each release |
| Contribution Guide | How to contribute to PX4 |
Community
- Weekly Dev Call — open to all developers (Dronecode calendar)
- Discord — Join the Dronecode server
- Discussion Forum — PX4 Discuss
- Maintainers — see
MAINTAINERS.md - Contributor Stats — LFX Insights
Contributing
We welcome contributions of all kinds — bug reports, documentation, new features, and code reviews. Please read the Contribution Guide to get started.
Citation
If you use PX4 in academic work, please cite it. BibTeX:
@software{px4_autopilot,
author = {Meier, Lorenz and {The PX4 Contributors}},
title = {{PX4 Autopilot}},
publisher = {Zenodo},
doi = {10.5281/zenodo.595432},
url = {https://px4.io}
}
The DOI above is a Zenodo concept DOI that always resolves to the latest release. For a version-pinned citation, see the Zenodo record or our CITATION.cff.
Governance
The PX4 Autopilot project is hosted by the Dronecode Foundation, a Linux Foundation Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship — no single company owns the name or controls the roadmap. The source code is licensed under the BSD 3-Clause license, so you are free to use, modify, and distribute it in your own projects.