Supported boards

Project creation shows the targets enabled by your installation. The catalog and runtime do not promise identical capabilities for every board.

Framework / target	Browser execution	Local simulation tests / browser debug	Physical Flash
Arduino UNO R3	Yes, AVR adapter	Yes / Yes	Unavailable
Arduino ESP32	Yes, original ESP32 engine	No / No	Supported
Arduino ESP32-C3	Yes, C3 engine	Yes / Yes	Supported
Arduino ESP32-S3	Yes, S3 engine	No / No	Supported
ESP-IDF ESP32	Runtime path available	No / No	Unavailable
ESP-IDF ESP32-C3	Runtime path available	No / No	Unavailable
ESP-IDF ESP32-S3	Build/runtime unavailable	No / No	Unavailable
Java 21	Process runtime; no board	Project JUnit is separate	Not applicable

These are implementation capabilities, not a claim that every row was executed during this documentation capture. The current screenshots verify creation/editor access for Arduino C3, Java and ESP-IDF C3; actual hardware flashing needs a physical device.

The Project board selector changes boards within the existing framework. Source/libraries stay; connections to pins absent on the new board are dropped. ESP-IDF target changes also update sdkconfig.defaults and preserve an existing sdkconfig as sdkconfig.old.

The canvas is a logical view rather than physical header order. S3 GPIO35–37 are reserved conservatively for memory variants; onboard addressable RGB pins differ across board revisions. Check the real board before wiring.

Before physical writing, the Flash flow identifies the connected chip and rejects a mismatch. Chip detection and exact development-board identification are separate. See Flash a device and Simulator limitations.