boxlang-runtime-esp32

Deploy BoxLang to ESP32 microcontrollers using MatchBox with --target esp32.

16|78|Updated Nov 28, 2014
One-click install
npx skills add https://github.com/ortus-docs/coldbox-docs --skill boxlang-runtime-esp32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boxlang-runtime-esp32
Source: https://github.com/ortus-docs/coldbox-docs/tree/main/.agents/skills/boxlang-runtime-esp32
Command: npx skills add https://github.com/ortus-docs/coldbox-docs --skill boxlang-runtime-esp32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines deploying BoxLang to ESP32 microcontrollers, enabling firmware flashing, bytecode updates, and rapid hardware iteration using MatchBox tooling.

Core Features & Use Cases

  • Deploy BoxLang to ESP32 with --target esp32 and optional --full-flash or --flash for incremental updates.
  • Use --watch for automatic recompile and reflash during development, and access serial output with espflash monitor.
  • Runtime detection and FreeRTOS task constraints support multiple ESP32 variants (S3, C3, etc) and predictable hardware behavior.

Quick Start

Run matchbox app.bxs --target esp32 --chip esp32s3 --full-flash to install firmware, then continue with matchbox app.bxs --target esp32 --chip esp32s3 --flash --watch for iterative updates.

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?

Streamline ESP32 development iterations using MatchBox watch mode with the --watch and --flash flags to automatically recompile BoxLang bytecode and reflash incremental updates to the microcontroller on every file change.

What prerequisites do I need to deploy BoxLang to ESP32?

BoxLang supports multiple ESP32 variants including S3 and C3 models, with runtime detection via server.os.arch and FreeRTOS task constraints ensuring predictable hardware behavior across different microcontroller specifications.

Why do I need to use --full-flash versus --flash when deploying to ESP32?

Use --full-flash for the initial firmware installation to deploy the complete BoxLang runtime, then use --flash for subsequent bytecode updates to push only incremental changes, significantly reducing deployment time during development.

How do I view serial output from my BoxLang application running on ESP32?

View serial output from a BoxLang application on ESP32 by running espflash monitor, which connects to the microcontroller's serial port and displays real-time logs and debugging information from the deployed bytecode.