ESP-WROVER-KIT
BoardSpecifications
Radiosinherited from ESP32
- Wi-Fi
- Wi-Fi 4 · 2.4 GHz
- Bluetooth LE
- BLE 4.2
- Bluetooth Classic
- yes
- 802.15.4
- no
USB
- Native USB
- no
- Connector
- micro-usb
- Bridge chip
- ft2232hl
Board
- Form factor
- devkit
Display & extras
- Extras
- rgb-led
ESP32-WROVER-E development/debug board with a built-in FT2232HL JTAG debugger and an onboard RGB LED.
Firmware for this board
No firmware recipes yet — help add one.
Notes
- USB 2.0 A-to-Micro-B cable; FT2232HL provides both the UART bridge and on-board JTAG debugging
- Carries an ESP32-WROVER-E module with 64-Mbit (8 MB) PSRAM
- Four diagnostic red LEDs on FT2232HL GPIOs, plus a red 5V Power-On LED and an RGB LED (GPIO0/GPIO2/GPIO4)
- Dimensions not provided in the user guide (omitted)
- io.gpio_free=13 DERIVED, not quoted (SPEC-io-power.md §5.3). Main I/O connector JP1 lists 24 pads in its table, but the user guide states "GPIO16 and GPIO17 ... are not broken out to the board's pin headers" (reserved for PSRAM CS/CLK on the WROVER module) -- excluding those 2 leaves 22 usable exposed pads (GPIO 0,2,4,5,12-15,18,19,21-23,25-27,32-36,39). Subtracting esp32's soc.reserved_pins that are exposed -- strapping {0,2,5,12,15} (5) and input_only {34,35,36,39} (4); usb_flash_tied {6-11} none exposed -- gives 22 - 5 - 4 = 13. 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 ESP-WROVER-KIT — 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.
