5148d2d94f
This insures the common exception handler will not be re-entered. The handler does not support nested interrupts and the interrupt stack pointer and context will be overwritten resulting in hard to debug hardfaults. If all the priorities are equal the NVIC prevents the preemption. The startup code defaults all the priorities to the same value 128. This change safeguards in 2 ways 1) By disabling CONFIG_ ARCH_IRQPRIO: up_prioritize_irq cannot be called. This will insure that all HW interrupts are at the same priority. 2) By disabling CONFIG_ARCH_HIPRI_INTERRUP, the common exception will disable any interrupts during interrupt processing. |
||
---|---|---|
.ci | ||
.github | ||
Documentation | ||
ROMFS | ||
Tools | ||
cmake | ||
integrationtests/python_src/px4_it | ||
launch | ||
mavlink/include/mavlink | ||
msg | ||
platforms | ||
posix-configs | ||
src | ||
test | ||
test_data | ||
validation | ||
.ackrc | ||
.clang-tidy | ||
.github_changelog_generator | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
.ycm_extra_conf.py | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
CTestConfig.cmake | ||
Firmware.sublime-project | ||
Jenkinsfile | ||
LICENSE | ||
Makefile | ||
PULL_REQUEST_TEMPLATE.md | ||
README.md | ||
appveyor.yml | ||
eclipse.cproject | ||
eclipse.project | ||
package.xml |
README.md
PX4 Drone Autopilot
This repository holds the PX4 flight control solution for drones, with the main applications located in the src/modules directory. It also contains the PX4 Drone Middleware Platform, which provides drivers and middleware to run drones.
- Official Website: http://px4.io (License: BSD 3-clause, LICENSE)
- Supported airframes (portfolio):
- Multicopters
- Fixed wing
- VTOL
- many more experimental types (Rovers, Blimps, Boats, Submarines, etc)
- Releases: Downloads
PX4 Users
The PX4 User Guide explains how to assemble supported vehicles and fly drones with PX4. See the forum and chat if you need help!
PX4 Developers
This Developer Guide is for software developers who want to modify the flight stack and middleware (e.g. to add new flight modes), hardware integrators who want to support new flight controller boards and peripherals, and anyone who wants to get PX4 working on a new (unsupported) airframe/vehicle.
Developers should read the Guide for Contributions. See the forum and chat if you need help!
Weekly Dev Call
The PX4 Dev Team syncs up on a weekly dev call.
Note The dev call is open to all interested developers (not just the core dev team). This is a great opportunity to meet the team and contribute to the ongoing development of the platform. It includes a QA session for newcomers. All regular calls are listed in the Dronecode calendar.
Maintenance Team
- Project: Founder - Lorenz Meier, Architecture: Daniel Agar
- Communication Architecture
- UI / UX
- Multicopter Flight Control
- VTOL Flight Control
- Fixed Wing Flight Control
- Racers - Matthias Grob
- OS / drivers - David Sidrane
- UAVCAN / Industrial - Pavel Kirienko
- State Estimation - James Goppert, Paul Riseborough
- Vision based navigation
- Obstacle Avoidance - Martina Rivizzigno
- Snapdragon
- Intel Aero
- Raspberry Pi / Navio - Beat Kueng
- Airmind MindPX / MindRacer - Henry Zhang
- RTPS/ROS2 Interface - Vicente Monge
See also About Us (px4.io) and the contributors list (Github).
Supported Hardware
This repository contains code supporting these boards:
- Snapdragon Flight
- Intel Aero
- Raspberry PI with Navio 2
- Parrot Bebop 2
- FMUv2.x
- FMUv3.x Pixhawk 2
- FMUv4.x
- FMUv5.x (ARM Cortex M7, future Pixhawk)
- Gumstix AeroCore (only v2)
- Airmind MindPX V2.8
- Airmind MindRacer V1.2
- Bitcraze Crazyflie 2.0
Additional information about supported hardware can be found in PX4 user Guide > Autopilot Hardware.
Project Roadmap
A high level project roadmap is available here.