Docs menu

Studio Workflow

Device Console

Build and flash with ESP-IDF, monitor authoritative raw ESP32-P4 serial output, and inspect recognised runtime state in a read-only view.

Overview

The Studio-wide Device Console brings DESIGN → BUILD → FLASH → MONITOR → INSPECT HARDWARE into the visual workspace. It is a collapsible, resizable dock below the Studio; it is never part of the Canvas or exported interface.

AreaResponsibilityEvidence
BUILDIntegrated ESP-IDF build and flash outputPHYSICALLY PROVEN on ESP32-P4
MONITORAuthoritative raw serial outputPHYSICALLY PROVEN on ESP32-P4 / COM5 / 115200
I/ORead-only interpretation of recognised monitor dataIMPLEMENTED / TESTED
The complete Studio workspace with its collapsible Device Console dock.

Opening the Device Console

  1. 01Use Console in the Studio toolbar to open or collapse the dock.
  2. 02Drag the divider at its upper edge to resize it.
  3. 03Start Build & Flash or Clean Build & Flash to open the console automatically with BUILD selected.

BUILD

BUILD shows live ESP-IDF compilation and flash output, progress and completion state. It provides Build & Flash, Clean Build & Flash, Clear, Stop and auto-scroll. Existing ESP-IDF commands, board configuration, export validation and firmware generation remain authoritative underneath.

Genuine BUILD console output from the current Studio workflow.

MONITOR

  1. 01Open MONITOR and choose Refresh if the port is absent.
  2. 02Select the intended Windows COM port.
  3. 03Keep 115200 baud unless the device uses another rate.
  4. 04Choose Connect; use Disconnect, Clear and auto-scroll as needed.

MONITOR displays raw ESP32 serial text without interpreting or filtering it. It uses the local ForgeUI backend, not browser Web Serial.

The authoritative raw MONITOR connected to ESP32-P4.

Safe Build/Flash Handoff

ForgeUI prevents the monitor and flash process from fighting over the same serial port. Before flashing it records the connection, closes and releases the port, then runs ESP-IDF. After a successful flash it attempts to reconnect the previous port and baud. A reconnect failure is separate and does not change a successful flash result.

I/O

I/O is a read-only interpretation of explicit patterns already present in MONITOR. Recognised categories can include System and memory, Network / Wi-Fi / IP / RSSI, Storage / SD, GPIO, GPS, I2C, UART and CAN.

I/O derives compact state only from recognised raw monitor patterns.

Architecture

text
Studio UI
  │
Device Console
  │
Local ForgeUI Backend
  ├── ESP-IDF Build / Flash
  └── Serial Monitor Service
        ├── Raw MONITOR (authoritative)
        └── Read-only I/O parser

MONITOR and I/O share one authoritative serial source. I/O never becomes a second serial owner. ForgeUI integrates these tools; it does not replace ESP-IDF, VS Code, a general-purpose IDE or a full debugger.

Troubleshooting

ProblemWhat to check
Port does not appearRefresh, check USB and the Windows driver, and confirm the COM port is enumerated.
Port busy / access deniedClose other serial terminals holding the port, then retry.
No monitor outputVerify port and baud; reset the device if appropriate.
Wrong baudUse the device's configured rate; ForgeUI defaults to 115200.
I/O emptyConfirm MONITOR has data. I/O ignores unknown patterns and never guesses.
Reconnect after flash failsThe flash may still have succeeded. Refresh ports, select the port and reconnect manually.

Future telemetry