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.
| Area | Responsibility | Evidence |
|---|---|---|
| BUILD | Integrated ESP-IDF build and flash output | PHYSICALLY PROVEN on ESP32-P4 |
| MONITOR | Authoritative raw serial output | PHYSICALLY PROVEN on ESP32-P4 / COM5 / 115200 |
| I/O | Read-only interpretation of recognised monitor data | IMPLEMENTED / TESTED |
Opening the Device Console
- 01Use Console in the Studio toolbar to open or collapse the dock.
- 02Drag the divider at its upper edge to resize it.
- 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.
MONITOR
- 01Open MONITOR and choose Refresh if the port is absent.
- 02Select the intended Windows COM port.
- 03Keep 115200 baud unless the device uses another rate.
- 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.
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.
Architecture
Studio UI
│
Device Console
│
Local ForgeUI Backend
├── ESP-IDF Build / Flash
└── Serial Monitor Service
├── Raw MONITOR (authoritative)
└── Read-only I/O parserMONITOR 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
| Problem | What to check |
|---|---|
| Port does not appear | Refresh, check USB and the Windows driver, and confirm the COM port is enumerated. |
| Port busy / access denied | Close other serial terminals holding the port, then retry. |
| No monitor output | Verify port and baud; reset the device if appropriate. |
| Wrong baud | Use the device's configured rate; ForgeUI defaults to 115200. |
| I/O empty | Confirm MONITOR has data. I/O ignores unknown patterns and never guesses. |
| Reconnect after flash fails | The flash may still have succeeded. Refresh ports, select the port and reconnect manually. |
