claudeDroneteam-docs
documentation · reference
Docs reference

Architecture, simulation, RL framework, hardware and guides. Browse the tree on the left.

Embedded firmware (ESP32)

Sensor harness firmware: ESP32 + Arduino / ESP-IDF, lidar/ToF/optical-flow drivers, host-testable C++ patterns.

stablefirmwareupdated 2026-05-11T00:00:00.000ZClaudeDroneFirmwareEmbeddedESP32

The claudeDrone sensor harness lives on an ESP32 — a separate MCU alongside the Pixhawk-class flight controller. The ESP32 polls peripherals (TF-Luna UART, VL53L0X×6 via I2C-mux, PMW3901 SPI, servos via PWM), aggregates the data, and sends UDP frames to the companion PC.

Which ESP32, exactly. Early notes assumed an ESP32-S3. Reading the chip ID off the bench board (esptool chip-id, July 2026) settled it: ESP32-D0WD-V3, rev 3.1 — the classic dual-core Xtensa LX6 at 240 MHz, 520 KB SRAM, no PSRAM, Bluetooth 4.2/BLE. There is no native USB: the board always shows up as /dev/ttyUSB* through a CP2102 bridge, never as /dev/ttyACM*. We follow the hardware, so the firmware builds for the esp32dev target and the sensor pin map was redone for the classic chip. A binary built for the S3 won’t boot on this board at all.

Subhubs

Section What
Datasheet pitfalls 5 common surprises when building a knowledge bank from datasheets
Host-testable Arduino pattern Pure C++ + #if defined(ARDUINO) — unit tests on the host without mocks
TF-Luna driver See /drone/firmware/sensors/lidar/tf-luna/driver

Related nodes

  • Firmware agent → firmware-agent-logs
  • ESP32 ↔ companion PC: UDP spec (in progress, separate doc)

The category expands as modules are added: I2C-mux, PWM-servo, SPI-PMW, UART-timing — these become subfolders in boards/esp32dev/ of the firmware repo.

© 2026 claudeDrone Team Docs