boxlang-runtime-esp32

Flash firmware and deploy bytecode to ESP32 devices with MatchBox tooling.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-esp32-ortus-boxlang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boxlang-runtime-esp32
Source: https://github.com/ortus-boxlang/skills/tree/main/boxlang-developer/runtime-esp32
Command: npx skills add https://github.com/ortus-boxlang/skills --skill boxlang-runtime-esp32-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy BoxLang to ESP32 microcontrollers efficiently by managing firmware flashing, bytecode deployment, and hardware access, enabling rapid iteration and reliable deployment in embedded environments.

Core Features & Use Cases

  • ESP32 target support with various chips (ESP32-S3, ESP32-C3, ESP32, ESP32-S2) for BoxLang runtime
  • Full firmware flash on first deployment and fast bytecode updates thereafter
  • Watch mode for automatic recompile and reflash during development
  • Runtime detection and basic hardware interfacing via BoxLang BIFs
  • Clear development workflow with serial monitor support

Quick Start

Run a full firmware flash for the first deployment with matchbox app.bxs --target esp32 --chip esp32s3 --full-flash and then iterate with matchbox app.bxs --target esp32 --chip esp32s3 --flash --watch.

Frequently Asked Questions about boxlang-runtime-esp32

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

FAQPage Schema
How do I flash BoxLang firmware to an ESP32 microcontroller?

To flash BoxLang firmware to an ESP32, use MatchBox tooling to run a full firmware flash on first deployment with the --full-flash flag, specifying your target chip like ESP32-S3 or ESP32-C3.

Can I use watch mode to automatically reflash bytecode to an ESP32 during development?

Yes, watch mode automatically recompiles and reflashes BoxLang bytecode to the ESP32 during development. Use the --flash and --watch flags with your matchbox command for rapid incremental updates after the initial full flash.

What is the deployment workflow for running BoxLang on embedded ESP32 devices?

The BoxLang ESP32 deployment workflow involves an initial full firmware flash followed by fast incremental bytecode updates. It includes runtime environment detection, serial monitor output for debugging, and hardware interfacing via BoxLang BIFs.

Does BoxLang runtime support various ESP32 chips like ESP32-S2 and ESP32-C3?

Yes, the BoxLang runtime supports various ESP32 chips including ESP32, ESP32-S2, ESP32-S3, and ESP32-C3. It handles runtime detection across these variants while operating within FreeRTOS task constraints.

Why do I need a full firmware flash before deploying bytecode to an ESP32?

A full firmware flash is required on first deployment to establish the BoxLang runtime environment on the ESP32. Subsequent updates use fast bytecode-only flashes, significantly reducing iteration time during embedded development.

What are the FreeRTOS task constraints when running BoxLang on an ESP32?

When running BoxLang on an ESP32, the runtime operates within FreeRTOS task constraints, requiring coordination between bytecode deployment and hardware access to ensure reliable execution in the embedded environment.