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.
HMI and Display-Centric Design
The ESP32-P4 is Espressif's first SoC with a native MIPI-DSI display interface, and this positions it squarely against STM32 chips that have dominated the touchscreen HMI market for years. Previous ESP32 variants drove displays over SPI — functional for small screens, but bandwidth-limited. An SPI bus at 80 MHz feeding a 320x240 TFT is fine. An SPI bus trying to push pixels to a 7-inch 800x480 panel stutters visibly during LVGL animations and scroll operations. MIPI-DSI eliminates this bottleneck with dedicated display lanes that DMA framebuffer data directly to the panel controller.
The 2-lane MIPI-DSI output on the P4 drives panels up to 1080p at 60 Hz. Combined with 32MB PSRAM on the Function EV Board, the P4 can double-buffer a full 1080p framebuffer (approximately 6MB per frame at RGB888) with room to spare for application logic, fonts, and image assets. This is the territory of industrial HMI panels — think factory dashboards, point-of-sale terminals, smart thermostats with rich UIs, and home automation wall panels.
The hardware JPEG codec accelerates image decompression without loading the CPU, which matters for UIs with photographic backgrounds or product images. The H.264 hardware codec handles video playback for digital signage or tutorial displays. These are dedicated silicon blocks, not software decoders competing for CPU cycles.
For developers coming from the STM32 ecosystem, the P4 offers a compelling alternative. STM32H7 boards with LTDC display controllers and external SDRAM achieve similar HMI performance, but the P4 adds WiFi (via the C6 co-processor), a richer peripheral set for IoT integration, and the familiar ESP-IDF toolchain. The trade-off is ecosystem maturity — STM32 has a decade of LVGL optimizations, TouchGFX support, and industrial-grade BSPs. The P4's LVGL port is functional but still accumulating the performance tuning and driver coverage that STM32 enjoys.
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.
400MHz RISC-V: Performance Positioning
The P4's dual-core RISC-V at 400MHz sits in a performance tier that did not previously exist in the ESP32 lineup. The ESP32-S3's dual-core Xtensa at 240MHz has been the ceiling for five years — fast enough for basic camera and display work, but visibly struggling with complex LVGL animations on large panels, real-time audio processing at CD quality, or ML inference on models larger than a few hundred kilobytes. The P4 delivers roughly 1.6x the clock speed with a more modern RISC-V pipeline that achieves higher instructions-per-clock, putting effective compute gain closer to 2x for typical workloads.
This positions the P4 between the S3 and entry-level application processors like the Allwinner H616 (quad-core Cortex-A53 at 1.5GHz) used in the BTT CB1. The P4 cannot run Linux — it lacks an MMU and the memory subsystem Linux requires. But for bare-metal and RTOS workloads, the P4 handles tasks that previously required stepping up to a Linux SBC: rendering complex UIs at 60fps on 720p displays, processing 1080p camera feeds for object detection, running keyword spotting and voice command models with sub-100ms latency, and driving USB host peripherals while simultaneously managing display and network traffic.
The 32MB PSRAM on the Function EV Board is equally important to the performance story. A 720p RGB888 framebuffer consumes approximately 2.7MB. Double-buffering for tear-free rendering requires 5.4MB. Add LVGL's working buffers, font caches, and image assets for a moderately complex UI, and you easily reach 10-15MB. The S3's maximum 8MB PSRAM makes double-buffered 720p impractical — you must compromise on color depth (RGB565 instead of RGB888) or resolution. The P4's 32MB PSRAM eliminates this constraint entirely, with headroom for ML model weights, audio buffers, and application data alongside the display stack.
When to choose the P4 over the S3: any project involving displays larger than 3.5 inches, camera resolutions above VGA, real-time audio or video processing, or ML models that exceed 2MB. When to choose a Linux SBC instead: web servers, general-purpose computing, anything requiring a package manager or Python runtime, or projects where development speed matters more than power consumption and boot time.
Full Specifications
Processor
| Specification | Value |
|---|---|
| Architecture | RISC-V dual-core (HP) + RISC-V single-core (LP) [1] |
| CPU Cores | 2 [1] |
| Clock Speed | 400 MHz [1] |
| Low-Power Core | RISC-V LP core @ 40MHz [1] |
| AI Acceleration | AI instruction extensions (vector + DSP) [1] |
Memory
| Specification | Value |
|---|---|
| Flash | 16 MB [1] |
| SRAM | 768 KB [1] |
| PSRAM | 32 MB [1] |
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) [2] |
I/O & Interfaces
| Specification | Value |
|---|---|
| GPIO Pins | 54 [2] |
| mipi_csi | 2-lane MIPI-CSI (up to 1080p30 camera) [2] |
| mipi_dsi | 2-lane MIPI-DSI (up to 1080p60 display) [2] |
| USB | USB 2.0 HS (OTG) + USB-UART [2] |
| sdmmc | 2x SDIO 3.0 (eMMC/SD 4-bit) [2] |
| ethernet | 10/100 RMII MAC (external PHY required) [2] |
| SPI | 3 [2] |
| I2C | 2 [2] |
| UART | 5 [2] |
| ADC Channels | 12 [2] |
Power
| Specification | Value |
|---|---|
| Input Voltage | 5 V [1] |
Physical
| Specification | Value |
|---|---|
| Dimensions | 110 x 60 mm [2] |
| Form Factor | Dev kit with dual USB-C, MIPI connectors [2] |
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
Ecosystem & Community
The ESP32-P4 is very new (2025-2026) with a growing but still small ecosystem — primarily ESP-IDF first-party examples for MIPI camera, display, and AI inference workloads.
Compatible Software
What to Build First
Connect a 1080p MIPI-CSI camera and a MIPI-DSI touchscreen display to build a smart doorbell or object detection system. The P4's 400MHz RISC-V cores with AI vector extensions handle on-device inference that the ESP32-S3 cannot.
View tutorial →Must-Have Accessories
Tutorials & Resources
- ESP32-P4 Getting Started GuideOfficial ESP-IDF setup and first project guide for the ESP32-P4 Function EV Boarddocs
- ESP32-P4 Technical Reference ManualComplete hardware reference covering MIPI-CSI, MIPI-DSI, AI extensions, and all peripheralsdocs
- ESP-WHO (AI Vision Examples)Face detection, recognition, and object detection examples optimized for ESP32 AI capabilitiesgithub
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.