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

View 4 firmware recipes · 2 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-goodread the caveat

    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.

    Caveat: Bruce publishes a dedicated `Bruce-esp32-c5.bin` in its official 1.16.1 release. The ESP32-C5-DevKitC-1 is the reference bare C5 devkit (no display), so the plain c5 build is its target; the `-tft` variant is for C5 boards with a screen. Verified on real hardware 2026-09-01: ESP32-C5-DevKitC-1, chip revision v1.2 (ROM esp32c5-eco3-20250704), ESP32-C5-WROOM-1 with 8 MB flash and no PSRAM. Bruce-esp32-c5.bin 1.16.1 (4,122,608 bytes, bootloader at 0x2000 inside the merged image) written at 0x0 with esptool 5.3.0 over the USB-to-UART port (CP2102N), hash verified, 211 s at 115200 (the C5 ROM does not support --baud changes). Boots cleanly: ROM -> second-stage -> app, no resets in a 10 s window; logs one 'MSPI Timing: Failed to allocate dummy cacheline for PSRAM memory barrier' error (module has no PSRAM - harmless) and one 'Invalid IO 255' pin warning. Headless board: Bruce runs on its serial CLI. CAVEAT: the in-browser flash of this same image through ESP Web Tools 10.4.0 fails on this silicon revision with 'Failed to initialize. Try resetting your device or holding the BOOT button while clicking INSTALL.' - esptool-js 0.6.1 does not know this chip's CHIP magic 0x30e1706f (espressif/esptool-js#262; chip-id detection merged upstream in #197, unreleased). Flash from a terminal until esptool-js ships a release and ESP Web Tools bumps.

  • ESPHomeKnown goodhomeweb flasher
    Flash ESPHomeweb flasherknown-goodread the caveat

    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.

    Caveat: ESPHome's `esp32:` component targets a standard Espressif devkit per chip variant by default; the ESP32-C5-DevKitC-1 is that reference board for `variant: esp32c5`, so any esphome YAML with that variant (or no board override) runs on it unmodified. Verified on real hardware 2026-09-01: ESPHome 2026.8.2 (`framework: esp-idf`, ESP-IDF 5.5.5) compiled for `variant: esp32c5`, flashed as the factory image at 0x0 with esptool 5.3.0 over the USB-to-UART port; boots and logs `ESP32 Chip: ESP32-C5 rev1.2`, and drives the onboard GPIO27 WS2812 through `esp32_rmt_led_strip`. Note: the same chip revision answers CHIP magic 0x30e1706f, which the in-browser flashers (esptool-js 0.6.1) do not recognise -- web.esphome.io could not detect it; the CLI + esptool path works.

Unverified

  • WLEDUnverifiedhome
    Flash WLEDguidedread the caveat

    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.

    Caveat: wled names this board as esp32-c5-devkitc-1 in its platformio.ini (env esp32c5dev); derived from the repo's own build files, not verified on hardware.

Broken

  • ESP32 MarauderBrokenpentestrelease .bin
    ESP32 Marauder — not installablebroken

    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.

    Why: ESP32 Marauder has a dedicated wiki page for the ESP32-C5-DevKitC-1 and ships a board-specific `...esp32c5devkitc1.bin` in its v1.15.1 release (a ~1.8 MB merged image, bootloader magic 0xE9 at byte 0, flashed at 0x0). Hardware test 2026-09-01 on an ESP32-C5-DevKitC-1 with chip revision v1.2 (ROM eco3-20250704, 8 MB flash, no PSRAM): flashed at 0x0 with esptool 5.3.0 over the USB-to-UART port, hash verified, the image boot-loops -- six `rst:0x7 (TG0_WDT_HPSYS)` resets then `invalid header` / `ets_flash_boot` assertion on UART0, and it never prints a second-stage bootloader line on UART0. Marked broken at v1.15.1 for this silicon revision; earlier revisions untested, and the maintainer wiki still lists the board -- retest on a newer release.

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.