Skip to main content
The Flash Tool flashes flight controller firmware, updates DroneCAN peripheral nodes and gives you the install command for the ADOS agents, all from one panel.
Flash Tool Firmware step with the ArduPilot stack, CubeOrangePlus board, ArduCopter Stable version and flash methods

Flash Tool on the Firmware step with the ArduPilot stack, a board and a Stable version selected.

​
Open the Flash Tool

  • Settings → Flash Tool (route /config/firmware)
  • The ⚡ Flash Tool button in the top bar
  • A node’s Setup tab → SYSTEM → Firmware
Links can preselect a stack and an AP_Periph node with /config/firmware?stack=<stack>&target=<node id>, for example ?stack=ap-periph&target=10.

​
Choose a stack

Mission Control does not flash iNav. Use iNav Configurator, then connect the board to Mission Control to configure it.
Flashing needs WebUSB (DFU) and Web Serial (bootloader paths): Chrome or Edge on desktop, or the desktop app. Firefox and Safari support neither. The agent install command works in any browser because it runs on the board.

​
Flight controller firmware

​
Flash methods

Pick a Flash Method, or leave it on Auto.

​
Flash ArduPilot

1

Connect the flight controller

Plug it in over USB. If it is connected in Mission Control, the panel shows FC Connected via MAVLink and the board details from AUTOPILOT_VERSION. A board already in bootloader mode shows DFU Device Connected.
2

Pick the firmware

Choose the Vehicle Type (ArduCopter, ArduPlane, ArduRover or ArduSub) and the Version: a stable release (marked Recommended), Latest Beta, Latest Build or Development (Unstable). Check that the board target matches your hardware.
3

Confirm the checklist

Tick the pre-flash checklist. Flash Firmware stays disabled until every item is ticked.
4

Flash

Click Flash Firmware. The board reboots into its bootloader and the progress bar tracks the write. Do not unplug the board.
5

Reconnect

The board reboots into the new firmware. Reconnect and check the version in the board details.
PX4 and Betaflight follow the same flow with their own target and version pickers. A Betaflight board that cannot reboot into DFU from software needs its boot button held while you plug in USB.
Flashing the wrong target can leave the flight controller unbootable until you reflash it in DFU mode. Always check the detected board against the target you pick.

​
Pre-flash checklist

​
DFU mode

​
AP_Periph CAN nodes

The AP_Periph (CAN nodes) stack flashes AP_Periph firmware to DroneCAN peripheral nodes such as GPS, compass and airspeed units on the CAN bus.
1

Choose the transport

Under Connection, pick SLCAN (needs a direct USB connection to the flight controller) or CAN_FORWARD (via agent), which routes CAN frames through the connected Drone Agent.
2

Pick the target node

Target node lists the DroneCAN nodes on the bus with their ID, name and software version. Select the node to update.
3

Confirm and flash

Tick the AP_Periph checklist and flash. The node reboots during the update.
The DroneCAN panel (Setup → DEBUG) shows the nodes on the bus and links a node straight to this stack.

​
Back up and restore parameters

Back up before every flash: a major firmware upgrade can reset parameters.
  • Backup Parameters in the Flash Tool saves the flight controller’s parameters to a file.
  • Restore Parameters loads a backup, compares it with the flight controller and writes the values you select with Restore. It is disabled while the aircraft is armed.
You can also export from the Parameters tab and load the file with Compare after the flash. Some parameters change name or meaning between firmware versions, so review the diff before writing.

​
Companion computers

The ADOS Drone Agent and ADOS Ground Agent stacks install the agent on a companion computer that already runs a stock OS (Raspberry Pi OS, Radxa OS, Ubuntu and similar).
Flash Tool ADOS Drone Agent stack showing the target board picker and the Install on a board running stock OS card

Flash Tool with the ADOS Drone Agent stack, a target board selected and the install command card.

1

Pick the stack and board

Choose ADOS Drone Agent or ADOS Ground Agent, then your board. The board list matches Supported hardware.
2

Copy the command

The Install on a board running stock OS card shows the install command for that stack. Click Copy.
3

Run it on the board

SSH into the board and paste the command. The installer detects the board, installs the agent and its services, and starts them.
4

Check the agent

Run ados status on the board.
The command for the Drone Agent is the standard installer. The Ground Agent command adds the ground-station profile. See Drone Agent installation and Ground Agent installation for the flags.

​
Add the board to your fleet

When the agent is running, open http://<board-ip>:8080 to finish its setup. Then in Mission Control click + at the top of the Fleet sidebar and add the board by hostname or IP in the Companion Computer column of the Connect dialog. See Pairing or, for a ground station, Set up a ground station.

​
Troubleshooting

Check that the flight controller is powered and connected with a data-capable USB cable. On Linux, your user needs serial port access (the dialout group).
Do not unplug the board. Try again. If the firmware no longer boots, enter DFU mode with the boot button and reflash. The bootloader is separate from the firmware and is not overwritten.
Restore your backup with Restore Parameters and review the diff.
Check that the board has internet access. Behind a proxy, set http_proxy and https_proxy before running the command. See Drone Agent troubleshooting.

​
Next steps

Sensor calibration

Calibrate after a fresh flash.

Choose what to install

Pick the install path for your hardware.
Last modified on October 11, 2026