Build, flash, and provision an ESP32-S3/C6 CSI node for RuView — firmware variant choice, ESP-IDF Windows-subprocess flow, NVS/WiFi/channel/MAC-filter overrides.
69
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Bring an ESP32 sensing node online.
Prebuilt binaries: GitHub release v0.8.1-esp32 (hardware-validated on S3 QFN56 rev v0.2).
ESP-IDF v5.4 on Windows is subprocess-only (Git Bash/MSYS is unsupported — strip
MSYSTEM* env vars). Offsets for the S3 image:
esptool --chip esp32s3 -p <PORT> -b 460800 write_flash \
0x0 bootloader.bin 0x8000 partition-table.bin \
0xf000 ota_data_initial.bin 0x20000 esp32-csi-node-s3-8mb.bin(ruview_node_flash returns the exact pinned command rather than running an
unattended flash.)
python firmware/esp32-csi-node/provision.py --port <PORT> \
--ssid "<SSID>" --password "<secret>" --target-ip <server-ip> --target-port 5005
# optional ADR-060 overrides:
python firmware/esp32-csi-node/provision.py --port <PORT> --channel 6 --filter-mac AA:BB:CC:DD:EE:FFNever echo or commit the WiFi password.
ruview_node_monitor {port} — PASS criteria: serial shows CSI cb #... callbacks and
(on a bare board) CSI filter upgraded to MGMT+DATA. No callbacks → the node isn't
capturing; do not proceed to calibration.
d9dfea2
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.