esp32-workbench-serial-flashing

Automate remote ESP32 flashing and device management via RFC2217 proxies.

161|53|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/SensorsIot/Universal-ESP32-Workbench --skill esp32-workbench-serial-flashing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: esp32-workbench-serial-flashing
Source: https://github.com/SensorsIot/Universal-ESP32-Workbench/tree/main/.claude/skills/esp32-workbench-serial-flashing
Command: npx skills add https://github.com/SensorsIot/Universal-ESP32-Workbench --skill esp32-workbench-serial-flashing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ESP32 flashing across multi-slot ESP32 workbenches requires coordinating device discovery, slot management, and reliable remote flashing via RFC2217, including recovery flows when boot issues arise.

Core Features & Use Cases

  • Remote device discovery and slot management for ESP32 workbenches, including single- and dual-slot hubs.
  • Remote flashing, reset, and GPIO-based boot mode control via RFC2217 proxies, with crash-loop and flapping recovery.
  • Automatic and manual recovery workflows to bring devices back from download mode or bricking scenarios.

Quick Start

Discover available slots with the /api/devices endpoint and flash a device using esptool via the RFC2217 URL.

Frequently Asked Questions about esp32-workbench-serial-flashing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I flash an ESP32 remotely using esptool and RFC2217?

Remote ESP32 flashing via RFC2217 is automated by discovering available slots with the /api/devices endpoint and then flashing the device using esptool pointed at the RFC2217 URL. This handles slot management and the remote serial connection automatically.

What is the best way to control ESP32 GPIO boot mode pins over a remote serial connection?

Controlling ESP32 GPIO boot mode pins remotely is handled through RFC2217 proxies that provide GPIO-based boot mode control. The Skill triggers reset and boot pin state changes via dedicated endpoints to force devices into or out of download mode.

Can I recover an ESP32 stuck in a crash loop or bricking scenario over a network connection?

Yes, crash-loop and flapping recovery for ESP32 boards is supported over the network. The Skill implements automatic and manual recovery workflows to bring devices back from download mode or bricking scenarios using the remote RFC2217 serial connection.

Does this remote flashing workflow support multi-slot USB hubs for ESP32 workbenches?

Yes, remote device discovery and slot management for ESP32 workbenches fully supports both single-slot and dual-slot USB hub scenarios. It coordinates which device is flashed and managed across the available hardware slots.

Why does my remote ESP32 flashing fail to enter download mode when using an RFC2217 proxy?

Remote ESP32 flashing fails to enter download mode when GPIO boot-mode control is not properly triggered before flashing. The Skill applies dedicated reset and GPIO workflows via the RFC2217 proxy to ensure the device enters the correct boot mode before esptool runs.