Skip to content
On this page

ESP32-DevKitC V4 — first connection and flash

Applies to: ESP32-DevKitC V4 (current revision). The older V2 has its own user guide; see the revision selector on the board page.

Before you plug in

The official guide opens Start Application Development with a condition, not a step: make sure the board is in good condition with no obvious signs of damage. Then it hands you to the ESP-IDF Get Started guide — that, not this page, is the authoritative toolchain walkthrough.

The one USB port

Unlike the S3 generation (ESP32-S3-DevKitC-1 has two ports), DevKitC V4 has exactly one micro-USB port, wired through an on-board USB-to-UART bridge. Everything — power, flashing, serial — happens through it. A charge-only USB cable powers the board and then flashing silently fails; use a known data cable.

Boot mode

The classic ESP32 does not need manual download mode for normal flashing — the tool resets the chip itself. If auto-sync fails: hold BOOT, tap EN (reset), release BOOT. The board is now in Firmware Download mode for serial flashing.

The LED trap: there is no LED to blink

The DevKitC V4 component list contains no user LED of any kind — only the 5 V power-on LED, which is not programmable. Tutorials that blink “the onboard LED” on a DevKitC are written for other boards. Wire an LED (with resistor) to a spare GPIO and blink that. Which GPIOs are spare matters: see Pins to avoid on the board page — GPIO6–11 are flash lines on every variant, and GPIO16/17 depend on whether your board carries a WROOM or a WROVER module.

Power: three mutually exclusive paths

Official wording: micro USB port (default), 5V+GND header pins, or 3V3+GND header pins — mutually exclusive, with a warning that combining supply paths can damage the board and/or the supply.

The V4-specific trap: C15

On earlier V4 boards, component C15 can cause spurious boots into download mode and clock disturbance on GPIO0; the documented remedy is to remove the component. If your board enters download mode by itself, check the C15 note (with the fixed source) in the revision summary on the board page.

Expected, and failure exits

StepExpectedIf it fails
USB connected5 V power LED lightscharge-only cable / dead port — USB board not detected
Serial port on the computerbridge’s serial device appearscharge-only cable again, or missing bridge drivers — ESP-IDF Get Started
First flash (IDF example)tool resets chip, flashes, runs“Failed to connect” → manual BOOT+EN download mode above
Blink exampleexternal LED blinksno onboard LED exists on this board — see the LED trap

What this page cannot tell you

  • We did not flash a DevKitC V4 here — this page transcribes the pinned official guide; no MCUID hardware receipt exists for it. (The compiled-and-not-flashed lab we do have targets the S3 board: blink the DevKitC-1 RGB LED.)
  • OS-specific driver steps — maintained in ESP-IDF Get Started, not in the board guide.

Sources