ESP32-P4 Function EV Board
The ESP32-P4 is Espressif's flagship RISC-V SoC — a dual-core 400MHz HP CPU plus a 40MHz LP core, 768KB on-chip SRAM, and up to 32MB PSRAM on the Function EV Board. It targets HD camera and display applications with 2-lane MIPI-CSI input (1080p30) and 2-lane MIPI-DSI output (1080p60). The ESP32-P4 SoC has no integrated radio, but the Function EV Board includes an onboard ESP32-C6-MINI-1 co-processor over SDIO that provides 2.4 GHz WiFi 6 and Bluetooth 5 (LE).
Best for HD camera, display, and on-device AI projects that need serious compute; skip if you want wireless out of the box or the lowest possible cost.
Where to Buy
Pros
- Dual-core 400MHz RISC-V HP CPU with AI/DSP vector extensions — ~1.6x higher clock than the ESP32-S3
- 32MB PSRAM on the Function EV Board unlocks HD framebuffers and on-device ML workloads
- Native 2-lane MIPI-CSI camera input (up to 1080p30) — no OV2640 bottleneck
- Native 2-lane MIPI-DSI display output (up to 1080p60) for UI-heavy projects
- Dedicated 40MHz RISC-V LP core runs while HP cores sleep for true low-power standby
Cons
- ESP32-P4 SoC has no integrated radio — Function EV Board solves this with an onboard ESP32-C6-MINI-1 over SDIO; a custom P4 design needs its own wireless co-processor
- Larger footprint (110x60mm dev kit) than classic ESP32 dev boards
- Newer chip — Arduino core and ecosystem libraries still maturing as of 2026
Why the P4 exists
Espressif's previous flagship, the ESP32-S3, tops out at 240MHz dual-core Xtensa with 8MB PSRAM. For camera and display projects, that ceiling shows up fast: the DVP parallel camera bus and SPI displays force you to compromise on resolution or frame rate. The P4 is Espressif's answer — 400MHz RISC-V dual-core with proper MIPI-CSI and MIPI-DSI lanes and up to 32MB PSRAM.
The trade-off is that Espressif chose to split wireless out of the package. The ESP32-P4 SoC itself has no integrated radio. The Function EV Board solves this with an onboard ESP32-C6-MINI-1 co-processor over SDIO, which provides 2.4 GHz WiFi 6 and Bluetooth 5 (LE). A custom P4-based design would need to integrate its own wireless co-processor. For camera streamers that only talk to Ethernet or USB, the wireless path is optional.
MIPI camera and display
The 2-lane MIPI-CSI interface is the headline feature for camera projects. It accepts 1080p30 sensors like the OV5640 or IMX415 directly, without the parallel-bus bottleneck that caps ESP32-S3 boards at VGA or 720p in practice. Combined with 32MB PSRAM, you can buffer several HD frames for motion detection, pre-processing, or on-device inference before streaming.
The 2-lane MIPI-DSI output handles 1080p60 panels natively. This matters for HMI and smart-display projects: ESP32-S3 driving an SPI TFT is throughput-limited by the SPI clock and CPU bit-banging overhead, so LVGL animations on larger panels stutter. A MIPI-DSI link sidesteps that bottleneck — framebuffer writes are DMA'd to the display without riding the CPU. Actual frame rates depend on panel resolution and LVGL scene complexity; refer to Espressif's MIPI example benchmarks in the ESP-IDF repo.
Power architecture
The P4 has three cores: two 400MHz RISC-V HP cores and one 40MHz RISC-V LP core. The LP core survives when the HP cores enter deep sleep, running housekeeping tasks, BLE/GPIO wake logic, or sensor polling. This is the same pattern as the ESP32-C6 but scaled up — you get real compute when you need it and a low-power watchdog when you don't.
For always-on devices like smart displays that wake on motion or voice, this matters. You can keep the LP core monitoring an I2S microphone or PIR sensor at milliwatt draw, and only spin up the HP cores for inference or UI.
Full Specifications
Processor
| Specification | Value |
|---|---|
| Architecture | RISC-V dual-core (HP) + RISC-V single-core (LP) |
| CPU Cores | 2 |
| Clock Speed | 400 MHz |
| Low-Power Core | RISC-V LP core @ 40MHz |
| AI Acceleration | AI instruction extensions (vector + DSP) |
Memory
| Specification | Value |
|---|---|
| Flash | 16 MB |
| SRAM | 768 KB |
| PSRAM | 32 MB |
Connectivity
| Specification | Value |
|---|---|
| wireless_note | Onboard ESP32-C6-MINI-1 co-processor provides 2.4 GHz WiFi 6 + Bluetooth 5 (LE) over SDIO (the ESP32-P4 SoC itself has no integrated radio) |
I/O & Interfaces
| Specification | Value |
|---|---|
| GPIO Pins | 54 |
| mipi_csi | 2-lane MIPI-CSI (up to 1080p30 camera) |
| mipi_dsi | 2-lane MIPI-DSI (up to 1080p60 display) |
| USB | USB 2.0 HS (OTG) + USB-UART |
| sdmmc | 2x SDIO 3.0 (eMMC/SD 4-bit) |
| ethernet | 10/100 RMII MAC (external PHY required) |
| SPI | 3 |
| I2C | 2 |
| UART | 5 |
| ADC Channels | 12 |
Power
| Specification | Value |
|---|---|
| Input Voltage | 5 V |
Physical
| Specification | Value |
|---|---|
| Dimensions | 110 x 60 mm |
| Form Factor | Dev kit with dual USB-C, MIPI connectors |
Who Should Buy This
The 2-lane MIPI-CSI interface accepts 1080p30 sensors directly, bypassing the parallel-DVP bandwidth limits that cap ESP32-S3 cameras at lower resolutions. 32MB PSRAM holds multiple HD framebuffers.
MIPI-DSI drives 1080p60 panels natively. With 32MB PSRAM you can run LVGL or a small React-style UI framework without the draw-call stutter that plagues SPI displays on ESP32-S3.
AI vector instructions plus 32MB PSRAM allow models that won't fit on ESP32-S3's 8MB PSRAM. Not a Jetson replacement, but fills the gap between S3 and a Pi.
The EV Board's onboard C6 co-processor works but uses more power than a single-chip design. For a simple battery sensor the ESP32-C6 or C3 on its own is cheaper and lower-power.
Better alternative: ESP32-C6-DevKitC-1
The P4 assumes you are comfortable with ESP-IDF and multi-chip topologies. Start on an ESP32-S3 DevKit where Arduino core and tutorials are mature.
Better alternative: ESP32-S3-DevKitC-1
Frequently Asked Questions
Does the ESP32-P4 have WiFi or Bluetooth?
The ESP32-P4 SoC has no integrated radio. The Function EV Board includes an onboard ESP32-C6-MINI-1 co-processor over SDIO that provides 2.4 GHz WiFi 6 and Bluetooth 5 (LE). A custom P4-based design would need its own wireless co-processor. For Ethernet-only or USB-only devices, wireless is optional.
ESP32-P4 vs Raspberry Pi 5: which should I choose?
The Pi 5 runs Linux with a GPU and gigabytes of RAM — it's a general-purpose computer. The P4 is a microcontroller-class SoC: faster than ESP32-S3 but slower than a Pi, with deterministic real-time behavior, lower idle power, and direct hardware peripherals. Pick the P4 when you need MCU-style I/O and sub-second boot; pick the Pi 5 when you need Linux apps or a desktop stack.
Can the ESP32-P4 run ESPHome or Home Assistant firmware?
Yes — the Function EV Board's onboard C6 co-processor handles wireless for ESPHome and Home Assistant. You flash the P4 as the host and the C6 as the transceiver. Verify current ESPHome P4 component status before relying on specific peripherals; some components still mature across releases. If you only need WiFi on a single chip, an ESP32-S3 or C6 is simpler.
What camera sensors work with the ESP32-P4?
Any 2-lane MIPI-CSI sensor up to 1080p30 is supported at the hardware level. Espressif's reference examples use OV5640 and SC2336; third-party drivers exist for IMX415, GC2145, and OV2640 (via parallel DVP). Driver availability is still growing as of 2026.
How much does the ESP32-P4 Function EV Board cost compared to ESP32-S3?
The Function EV Board is positioned as a premium dev kit and is significantly more expensive than the ESP32-S3-DevKitC-1. For production you'd design a custom board around the raw ESP32-P4 module, which narrows the cost gap significantly.
Does the ESP32-P4 support USB host mode?
Yes. The P4 has USB 2.0 HS with OTG, so it can act as a USB host for storage, HID peripherals, audio class devices, or camera-class devices. The dev kit also exposes a second USB-C port for UART bridging during development.