Main Content

Board

R2026b

ESP32-S3 development board variant for target hardware

Since R2026b

Model Configuration Pane: Hardware Implementation / Hardware board settings / Target hardware resources / Groups / ESP32-S3 board properties

Description

Select the specific ESP32-S3 development board used as the target hardware. The board selection determines the pin mapping, onboard peripherals, and USB bridge configuration. The list of available boards is filtered based on the selected Module.

Dependencies

To enable this parameter, set Hardware board to ESP32-S3 Series (Arduino Compatible).

This parameter is enabled only when a custom board definition is available for the selected Module. The available board entries are dynamically populated based on the module selection and any custom board files created using the Create Custom board button.

Settings

ESP32-S3-DevKitC-1 (when Module is ESP32-S3-WROOM-1/1U or ESP32-S3-WROOM-2/2U) (default) | ESP32-S3-DevKitM-1 (when Module is ESP32-S3-MINI-1/1U) | Custom: <board name> (user-defined custom boards)

Select the board from the drop-down list. The available boards depend on the selected Module:

ESP32-S3-WROOM-1/1U module

ESP32-S3-DevKitC-1 — Development board with USB-to-UART bridge (CP2102/CH340). Supports GPIO 1-21 and GPIO 38-48.

ESP32-S3-WROOM-2/2U module

ESP32-S3-DevKitC-1 — Development board with USB-to-UART bridge. Same pin availability as WROOM-1, with PSRAM support.

ESP32-S3-MINI-1/1U module

ESP32-S3-DevKitM-1 — Compact development board. Supports additional GPIO pins (GPIO 26, GPIO 33-37) compared to WROOM variants.

Additional custom boards appear in this list (prefixed with Custom:) after you create them using the Create Custom board button. Custom boards are matched to modules based on the ESP32Module property defined in the custom board class file.

Recommended Settings

Select the board that matches your physical hardware. If your board is not listed, use the Create Custom board button to define a custom board configuration.

Programmatic Use

No programmatic use is available.

Version History

Introduced in R2026b