Skip to content
Snippets Groups Projects
Select Git revision
  • heading_hold
  • stable default protected
  • yaw_damper
  • fw_controller_mod
  • master
  • holybro-s500-airframe
  • pr-update_src/modules/micrortps_bridge/micro-CDR
  • pr-update_src/drivers/uavcan/libuavcan
  • nuttx_master
  • beta
  • release/1.9
  • col_prev_dist_sensor
  • safe_landing_1.9
  • feature/sim-battery-parameter
  • ecl_master
  • pr-jenkins
  • pr-jenkins_asan
  • pr-assisted_land_speed
  • slp_ci
  • pr-new-vision-mav-mode
  • v1.9.1-rc0
  • v1.9.0
  • v1.9.0-rc2
  • v1.9.0-rc1
  • v1.9.0-rc0
  • v1.9.0-beta3
  • v1.9.0-beta2
  • v1.9.0-beta1
  • v1.9.0-alpha
  • v1.8.2
  • v1.8.1
  • v1.8.0
  • v1.8.0-rc0
  • v1.8.0-beta2
  • v1.8.0-beta1
  • v1.7.4beta
  • v1.7.3
  • v1.7.3beta
  • v1.7.2
  • v1.7.1
40 results
Compare
user avatar
px4fmu-v4 nsh: Disable ARCH_IRQPRIO & ARCH_HIPRI_INTERRUP
David Sidrane authored 
   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.
dfc390bb
History
user avatar dfc390bb
History
Name Last commit Last update
.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

Releases DOI

Build Status Coverity Scan

Slack

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.

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

See also About Us (px4.io) and the contributors list (Github).

Supported Hardware

This repository contains code supporting these boards:

Additional information about supported hardware can be found in PX4 user Guide > Autopilot Hardware.

Project Roadmap

A high level project roadmap is available here.