Skip to main content

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.

Mission Control’s Flash Tool installs the ADOS agent on every supported companion computer. Pick your starting state below to find the right path.

Pick your starting point

I have a Luckfox Pico Zero

Browser flash. No terminal.

I have a board running stock OS

Copy a command. Paste over SSH.

I have a fresh SD card with no OS

Get the vendor OS running first.

Luckfox Pico Zero

The Luckfox Pico Zero ships without a usable stock OS for the agent, so the Flash Tool writes a complete ADOS image directly from your browser. No terminal, no SSH, no separate flashing tool.
1

Open Mission Control

Open Mission Control in a Chromium-family browser (Chrome, Edge, Brave, or Opera). Browser flash uses WebUSB, which Safari and Firefox do not support.
2

Open the Flash Tool

Go to Settings -> Flash Tool. Pick ADOS Drone Agent as the firmware stack, then pick Luckfox Pico Zero as the target board.
3

Put the board in bootrom mode

Unplug the board. Hold the BOOT button. Plug the USB-C cable in while still holding BOOT. Release the button after the board enumerates.
4

Pick the device

Click Flash via browser. The browser device picker lists the Luckfox in bootrom mode. Select it and click Connect.
5

Wait for the flash to complete

The Flash Tool writes the ADOS image and shows a progress bar. The board reboots when flashing finishes.
6

Pair from your phone or laptop

The board exposes a Wi-Fi network named ados-setup-<id>. Join it from any device, finish the captive portal wizard, and the board appears in Mission Control’s Fleet view as a pending pair.

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.
1

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.
2

Open the Flash Tool

In Mission Control, go to Settings -> Flash Tool. Pick ADOS Drone Agent (for the air-side) or ADOS Ground Agent (for the ground-side) as the firmware stack, then pick your board.
3

Copy the install command

The Flash Tool shows a single curl ... | sudo bash line. Click Copy.
4

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.
5

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.
This flow works in any browser that runs Mission Control. Browser flash is not required for stock-OS boards because the install command runs over SSH on the board itself. For the canonical curl walkthrough, see Drone Agent installation or 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 flow once it boots and you can SSH in.
Browser-based OS flashing is supported today only for boards where the agent owns the entire image. The Luckfox Pico Zero is the first such target. More boards will follow as their bringup matures.

Browser support

BrowserBrowser flashInstall command
Chrome (89+)YesYes
Edge (89+)YesYes
BraveYesYes
OperaYesYes
SafariNoYes
FirefoxNoYes
Browser flash needs WebUSB, which is a Chromium-family feature. The install command flow runs entirely on the board, so any browser that can copy text works.

What’s next

Flash Tool walkthrough

Full tour of the Flash Tool inside Mission Control.

Supported hardware

Boards and companion computers the agent runs on.

Drone Agent installation

The canonical curl install path.