ESP32-C5-DevKitC-1

Board
by Espressifesp32-c5-devkitc-1

Also known as: esp32-c5-devkitc1-n16r4, esp32-c5-devkitc1-n4, esp32-c5-devkitc1-n8r4

Flash this board — 4 firmware options · Known good
ESP32-C5-DevKitC-1 board
Board
ESP32-C5-DevKitC-1 pinout
Pinout

Specifications

Radiosinherited from ESP32-C5

Wi-Fi
Wi-Fi 6 · 2.4 / 5 GHz
Bluetooth LE
BLE 5
Bluetooth Classic
no
802.15.4
Thread 1.4, Zigbee 3.0

USB

Native USB
yes
Connector
usb-c

Board

Form factor
devkit

Display & extras

Extras
rgb-led
Built onESP32-C5-DevKitC-1 BoardESP32-C5 SoC

Entry-level ESP32-C5-WROOM-1(U) devkit with dual USB-C (UART bridge + native) and a GPIO27 addressable RGB LED. First Espressif devkit with 5 GHz Wi-Fi 6.

Firmware for this board

Known good

  • BruceKnown goodpentestrelease .bin
    Flash Brucein-browserknown-good

    Known good esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

  • ESPHomeKnown goodhomeweb flasher
    Flash ESPHomeweb flasherknown-good

    Known good esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

Unverified

  • WLEDUnverifiedhome
    Flash WLEDguided

    Unverified esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

Broken

  • ESP32 MarauderBrokenpentestrelease .bin
    Flash ESP32 Marauderrelease .binbroken

    Broken esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

Notes

Before you flash

  • J5 current-measurement header: its jumper must be fitted (factory default = jumper on). Without it, per the user guide, "power supply between the module and peripherals on the board is cut off" -- the USB-to-UART bridge still enumerates and the power LED still lights, but the ESP32-C5 itself is unpowered and answers on neither USB-C port. Observed 2026-09-01 on a unit that shipped with no jumper; fitting one fixed it.
  • Board version documented: v1.2
  • Carries an ESP32-C5-WROOM-1(U) module (module record not yet in the atlas); modeled via soc: esp32-c5 rather than module: per the current data model -- cpu/radio specs come straight from the ESP32-C5 chip record, not restated here
  • Two USB Type-C ports: a UART-bridge port and the native ESP32-C5 USB 2.0 full-speed port; USB-UART bridge chip not named on the page (just "single-chip USB-to-UART bridge")
  • Addressable RGB LED on GPIO27
  • J3 pin 6 is NC/GPIO15 depending on whether the module variant integrates SPI PSRAM (SPICS1 when PSRAM is present); excluded from gpio_pins/gpio_free as not guaranteed available
  • Flash/PSRAM size not stated on this user-guide page -- omitted rather than guessed
  • io.gpio_free=12 DERIVED, not quoted (SPEC-io-power.md §5.3). J1+J3 headers break out 21 definite GPIOs per the pin tables (J1: 0,1,2,3,6,7,8,9,10,25,26; J3: 4,5,11,12,13,14,23,24,27,28 -- GPIO15 excluded as conditional). Subtracting esp32-c5's soc.reserved_pins that are exposed -- strapping {2,3,7,25,26,27,28} (7) and usb_flash_tied {13,14} (2) -- gives 21 - 7 - 2 = 12. Math not vendor-stated; verify before treating as exact.

Verify my board

Reads the connected chip over USB and checks it against what esp-atlas cites for ESP32-C5-DevKitC-1 — over Web Serial, no backend, nothing leaves your browser.

In-browser verify needs Web Serial: Chrome or Edge on a desktop. Safari, Firefox and phones cannot do it.

Serial monitor

Not connected.