flash

Builds and flashes OTGW firmware/filesystem images to ESP8266 over USB automatically.

199|41|Updated Oct 25, 2020
One-click install
npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill flash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flash
Source: https://github.com/rvdbreemen/OTGW-firmware/tree/main/.claude/skills/flash
Command: npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill flash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive build-and-flash steps required to update the OTGW firmware on an ESP8266 device.

Core Features & Use Cases

  • Automated build pipeline: Builds firmware and the filesystem together using the repository’s build script.
  • Automated flashing workflow: Flashes both firmware and filesystem to the connected ESP via USB with serial port auto-detection.
  • Version-aware reporting: Helps you confirm what firmware version was flashed and provides build/flash sizing and status feedback.

Quick Start

Run the flash skill to build the OTGW firmware and filesystem and flash them to the ESP8266 connected over USB, with serial port detection and no user input needed.

Frequently Asked Questions about flash

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

FAQPage Schema
How do I automate building and flashing ESP8266 firmware over USB?

To automate building and flashing ESP8266 firmware over USB, you need a repeatable deployment workflow that compiles firmware and filesystem images together and writes them to the device via serial port auto-detection.

What is the best way to flash OTGW firmware to an ESP8266 after code changes?

The best way to flash OTGW firmware updates to an ESP8266 is using an automated build pipeline that builds both firmware and filesystem, flashes them over USB serial, and reports the flashed firmware version and build sizes.

How does serial port auto-detection work when flashing an ESP8266?

Serial port auto-detection works when flashing an ESP8266 by automatically identifying the connected USB serial port, allowing the flashing workflow to run non-interactively without requiring manual port configuration.

Can I run a non-interactive ESP8266 firmware update workflow?

Yes, you can run a non-interactive ESP8266 firmware update workflow by executing build and flash scripts with flags like --no-interactive and --build, ensuring deterministic execution without requiring user input during deployment.

Do I need to manually build the ESP8266 filesystem image separately from the firmware?

No, you do not need to manually build the ESP8266 filesystem image separately, because the automated build pipeline compiles both the OTGW firmware and the filesystem together in one continuous step before flashing.

Why does my ESP8266 flashing workflow need version-aware reporting?

Your ESP8266 flashing workflow needs version-aware reporting to confirm exactly what firmware version was flashed, providing build and flash sizing status feedback by reading the firmware version directly from version.h.