# RuView Hardware Setup

Builds, flashes and monitors ESP32 RuView sensing nodes and fixes ones not streaming.

- Repository: https://github.com/ruvnet/RuView (101983 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ruvnet/RuView --skill ruview-hardware-setup -g -a claude-code -y`
Codex: `npx skills add ruvnet/RuView --skill ruview-hardware-setup -g -a codex -y`
Cursor: `npx skills add ruvnet/RuView --skill ruview-hardware-setup -g -a cursor -y`
Gemini CLI: `npx skills add ruvnet/RuView --skill ruview-hardware-setup -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ruvnet/RuView`

## Description

ESP32-S3 / ESP32-C6 firmware build, flash, WiFi provisioning, and serial monitoring for RuView CSI sensing nodes. Use when setting up physical hardware, reflashing a node, or debugging a device that isn't streaming CSI.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# RuView Hardware Setup

Bring a RuView sensing node online: build firmware → flash → provision WiFi → confirm CSI stream.

## Supported devices

| Device | Flash | Chip | Role |
|--------|-------|------|------|
| ESP32-S3 (8MB) | 8 MB | Xtensa dual-core | WiFi CSI sensing node (default) |
| ESP32-S3 SuperMini | 4 MB | Xtensa dual-core | Compact CSI node, use `sdkconfig.defaults.4mb` |
| ESP32-C6 + Seeed MR60BHA2 |, | RISC-V + 60 GHz FMCW | mmWave HR/BR/presence |

**Not supported:** original ESP32, ESP32-C3 (single-core).

**⚠️ Ask about board form factor before flashing.** If the user's board is a coin-sized clone (ESP32-S3-Zero, SuperMini, or similar, not a full DevKitC/XIAO-style board with a real USB connector and visible regulator), warn them before they walk away from it: this firmware runs the WiFi radio continuously (`WIFI_PS_NONE`) plus a full DSP pipeline (`edge_tier=2`), which is sustained high current draw that full-size dev boards handle fine but tiny clones with minimal copper/budget regulators may not. At least one field report: boards ran hot during a normal session and failed to power on again afterward (regulator damage suspected). Tell them to give the board airflow (don't stack/enclose it) and check it by touch during the first several minutes of any new deployment.

## 1. Build firmware (Windows, Python subprocess, NOT bash directly)

ESP-IDF v5.4 does not support MSYS2/Git Bash. Use the Espressif Python venv as a subprocess with `MSYSTEM*` env vars stripped. The proven command lives in `CLAUDE.local.md`, reproduce it:

The rest: https://github.com/ruvnet/RuView/blob/HEAD/plugins/ruview/skills/ruview-hardware-setup/SKILL.md