Image of Board

ESP32-S3-DevKitC-1-N32R16 by Espressif

The ESP32-S3-DevKitC-1 is an entry-level development board equipped with ESP32-S3-WROOM-2, a general-purpose Wi-Fi + Bluetooth LE MCU module that integrates complete Wi-Fi and Bluetooth LE functions. This version is equipped with the ESP32-S3-WROOM-2 (PCB antenna) with 32MB Flash and 16MB PSRAM.

Most of the I/O pins on the module are broken out to the pin headers on both sides of this board for easy interfacing. Developers can either connect peripherals with jumper wires or mount ESP32-S3-DevKitC-1 on a breadboard. We particularly like that there’s a debug UART/USB port and a separate native USB port, so you can upload/debug/USB all at once.

At the core of the module is an ESP32-S3R16V, an Xtensa® 32-bit LX7 CPU that operates at up to 240 MHz. You can power off the CPU and make use of the low-power co-processor to constantly monitor the peripherals for changes or crossing of thresholds. ESP32-S3 integrates a rich set of peripherals including SPI, LCD, Camera interface, UART, I2C, I2S, remote control, pulse counter, LED PWM, USB Serial/JTAG controller, MCPWM, SDIO host, GDMA, TWAI® controller (compatible with ISO 11898-1), ADC, touch sensor, temperature sensor, timers, and watchdogs, as well as up to 45 GPIOs. It also includes a full-speed USB 1.1 On-The-Go (OTG) interface to enable USB communication

There are three mutually exclusive ways to provide power to the board:

  • USB-to-UART Port and ESP32-S3 USB Port (either one or both), default power supply (recommended)
  • 5V and G (GND) pins
  • 3v3 and G (GND) pins

Components:

  • ESP32-S3-WROOM-2: ESP32-S3-WROOM-2 is a powerful, generic Wi-Fi + Bluetooth LE MCU module that has a rich set of peripherals. It provides acceleration for neural network computing and signal processing workloads. ESP32-S3-WROOM-2 comes with a PCB antenna.
  • 5V to 3.3V LDO: Power regulator that converts a 5V supply into a 3.3V output.
  • Pin Headers: All available GPIO pins (except for the SPI bus for flash and PSRAM) are broken out to the pin headers on the board for easy interfacing and programming. For details, please see Header Block. Note that GPIO35, GPIO36 and GPIO37 are used internally for the octal SPI flash and PSRAM and are not available for external use.
  • USB-to-UART Port: A Micro-USB port used for power supply to the board, for flashing applications to the chip, as well as for communication with the chip via the on-board USB-to-UART bridge.
  • Native ESP32-S3 USB Port: ESP32-S3 full-speed USB OTG interface, compliant with the USB 1.1 specification. The interface is used for power supply to the board, for flashing applications to the chip, for communication with the chip using USB 1.1 protocols, as well as for JTAG debugging.
  • Boot Button: Download button. Holding down Boot and then pressing Reset initiates Firmware Download mode for downloading firmware through the serial port.
  • Reset Button
  • USB-to-UART Bridge: Single USB-to-UART bridge chip provides transfer rates up to 3 Mbps.
  • RGB LED: Addressable RGB LED, driven by GPIO38. This board is a v1.1 revision of the ESP32-S3-DevKitC-1; the initial v1.0 revision drove the RGB LED from GPIO48 instead.
  • 3.3V Power On LED: Turns on when the USB power is connected to the board.

Purchase

Contribute

Have some info to add for this board? Edit the source for this page here.

Absolute Newest

Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. These releases are even newer than the development release listed above. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.

Previous Versions of CircuitPython

All previous releases of CircuitPython are available for download from Amazon S3 through the button below. For very old releases, look in the OLD/ folder for each board. Release notes for each release are available at GitHub button below.

Older releases are useful for testing if you something appears to be broken in a newer release but used to work, or if you have older code that depends on features only available in an older release. Otherwise we recommend using the latest stable release.