Pixhawk 1 v2.4

Paparazzi on Pixhawk

The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the PIXHAWK project. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM).

It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.

An step-by-step example on flying Paparazzi with a Pixhawk can be found on the Iris page.

Intro

This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the Pixhawk site. Details on how to flash the board with Paparazzi can be found below. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the Iris drone. A list of features that are currently (not) supported in Paparazzi can be found here.

The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --> USB -> PX4FMU --> internal UART --> PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.

Getting started

In short, the steps you'll need to run through are roughly the following:

1. Define your aircraft and settings for the Pixhawk (e.g. see the Iris airframe )
2. Connect the Pixhawk via USB to your computer, and upload the AP firmware
3. Replug the USB, and upload the FBW code. Replug USB again.

Details on steps 2 and 3 can be found in Flashing. Details on step 1 can be found in further below.

Flashing

Figure 2; building the AP

Figure 3; flashing the AP

Figure 4; building the FBW

Figure 5; flashing the FBW

In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU) and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.

To flash the AP (See figure 2 and 3):
- Select your aircraft (1).
- Select the AP (2).
- Click the build button (3).
- After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.
- After 5 seconds click upload (5).
- You should see "upload successful" (6).

To flash the FBW (See figure 4 and 5):
- Select FBW (7).
- Click the build button (8).
- After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.
- After 5 seconds click upload (10).
- You should see "upload successful" (11).

Notes:

After flashing the FBW, it is required to re-power the Pixhawk.
The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time.
Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.
In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.

Figure 6; upload problems

Airframe config

In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required.

Define seperate <firmware>'s for both the fbw and the ap: