> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altnautica.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install paths

> Pick the right install flow for your hardware. Mission Control's Flash Tool drives every supported path.

Mission Control's Flash Tool installs the ADOS agent on every supported companion computer. For each supported board it hands you a one-line install command to paste over SSH. Pick your starting state below to find the right path.

## Pick your starting point

<CardGroup cols={2}>
  <Card title="I have a board running a stock OS" icon="terminal" href="#stock-os-board">
    Copy the install command. Paste it over SSH.
  </Card>

  <Card title="I have a fresh SD card with no OS" icon="sd-card" href="#fresh-sd-card">
    Get the vendor OS running first, then install.
  </Card>
</CardGroup>

## Stock OS board

If your board is a Raspberry Pi, Radxa, Jetson, or any other supported SBC running its standard vendor OS, the Flash Tool surfaces a `curl` install command. Paste it on the board over SSH and the install script does the rest. The supported boards today are the Raspberry Pi 4B and Pi Zero 2 W, the Radxa CM3, CM4, Rock 5C Lite, and Cubie A7Z, plus the other profiles listed in [Supported hardware](/drone-agent/supported-hardware).

<Steps>
  <Step title="Boot your board with stock OS">
    Boot the board with its standard vendor OS. SSH must be enabled and you must be able to reach the board over the network.
  </Step>

  <Step title="Open the Flash Tool">
    In Mission Control, go to **Settings, then Flash Tool**. Pick **ADOS Drone Agent** (for the air-side) or **ADOS Ground Agent** (for the ground-side) as the stack, then pick your board.
  </Step>

  <Step title="Copy the install command">
    The Flash Tool shows a single `curl ... | sudo bash` line. Click **Copy**.
  </Step>

  <Step title="Paste it on the board over SSH">
    SSH into the board. Paste the command. The install script detects the board, installs dependencies, configures the agent, and starts everything automatically.
  </Step>

  <Step title="Pair from Mission Control">
    The board exposes a setup webapp at `http://<board-ip>:8080`. Finish onboarding there. The board then shows up in Mission Control's Fleet view.
  </Step>
</Steps>

The install command runs over SSH on the board itself, so any browser that displays Mission Control can show you the command. For the canonical walkthrough, see [Drone Agent installation](/drone-agent/installation) or [Ground Agent installation](/ground-agent/installation).

## Fresh SD card

Bringing up a brand-new Raspberry Pi or Radxa board from a blank SD card is out of scope for the Flash Tool today. The vendor flashing tools handle the initial OS write.

Get the board running its standard vendor OS first, then come back here. The board falls into the [Stock OS board](#stock-os-board) flow once it boots and you can SSH in.

## Flashing flight controller firmware

The Flash Tool also flashes flight controller firmware (ArduPilot, PX4, Betaflight, iNav), which is a separate flow from installing the companion agent. That path runs in the browser and needs a Chromium-family browser (Chrome, Edge, Brave, Opera) because it uses WebUSB and WebSerial. See [Firmware Flashing](/mission-control/firmware-flashing) and the [Flash Tool walkthrough](/mission-control/flash-tool).

## What's next

<CardGroup cols={2}>
  <Card title="Flash Tool walkthrough" icon="wand-magic-sparkles" href="/mission-control/flash-tool">
    Full tour of the Flash Tool inside Mission Control.
  </Card>

  <Card title="Supported hardware" icon="microchip" href="/drone-agent/supported-hardware">
    Boards and companion computers the agent runs on.
  </Card>

  <Card title="Drone Agent installation" icon="download" href="/drone-agent/installation">
    The canonical curl install path.
  </Card>
</CardGroup>