RoboHub

This page was generated from the source of RoboHub. Edit the source, not this page.

RoboHub Linux Platform

The Linux platform for the RoboHub ecosystem: the interfaces declared by
robohub-common, implemented on Linux hosts, with board support packages
for the Linux-based boards.

The platform

A Rho program on this platform runs on a Linux host. The platform provides
the interfaces, the HAL, and the board support package that registers the
board's peripherals. The console is a file descriptor, the clock is
CLOCK_MONOTONIC, and a serial port is a tty.

Building

cd examples/c/hello_world
rho build -target uno-q .

Deploying

rho deploy -target uno-q -run build/output/hello_world

The examples

examples/c/hello_world and examples/rho/hello_world are the smallest
programs that run on real hardware: they say hello and write a line to the
console every second.

System dependencies

  • ssh — for deploying to the board
  • rsync — for copying the program to the board
  • aarch64-linux-gnu-gcc — for cross-compiling

Deployment metadata

The boards this platform carries say what a deployment may make of them and how
the keeper reaches them:

capabilities:
  gateway: true
  relay: true
  node: false
  host: true
  wireless: true
  links: "uart console usb wifi socket"
  buses: "uart usb"

deployment:
  method: "adb"
  arch: "arm64"
  kconfig: "CONFIG_RH_BOARD_ARDUINO_UNO_Q=y"
  apps_dir: "/home/arduino/apps"

native is the machine running the build or the keeper; it is a host with UART,
USB, Ethernet, WiFi and socket links. The UNO Q is a host gateway with WiFi and
USB; its Ethernet is added by the USB-C dongle the board doesn't carry yet. The
keeper prefers ADB for the UNO Q when it is connected over USB, and SSH for a
board reached over the network.

Arduino UNO Q

The UNO Q is two machines on one board: a Linux side that is deployed to, and a
microcontroller that is flashed. The bring-up runbook takes it from
the box to a running program: reaching the board over USB (ADB) or the network
(SSH), deploying a program or a container to its Linux side, and flashing its
MCU.

The device keystore

On a Linux host the rotated device key (robohub/keystore.h) is one file, mode
0600, holding the two A/B records of robohub/keystore_core.h. A write never
changes it in place: the new contents go to <file>.tmp (created 0600 and
fsync'd), which is renamed over the file before the directory is fsync'd, so a
crash leaves the old file or the new one. The file is, first that is set:

VariableFile
RH_KEYSTORE_FILEthat file
RH_STATE_DIR<dir>/keystore.bin
RH_SECURE_KEY_FILE<key file>.keystore, beside the key it supersedes

With none set there is no store, the same answer as the weak default.

Release history

All notable changes to this module are recorded here, one section per release.

[0.2.0] - 2026-11-01

The UNO Q manifest declares the host gateway role, WiFi and UART/USB links, and an ADB/arm64 deployment to /home/arduino/apps; the documentation explains the keeper's ADB deployment and that Ethernet is added with the USB-C dongle.

[0.3.0] - 2026-11-14

The board key is kept in a 0600 file replaced atomically. Linux hosts have no production mode.