← ClaudeAtlas

esp32-p4listed

Chip-level ESP-IDF capability reference for the ESP32-P4 SoC (dual-core RISC-V HP cores + a RISC-V LP core) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-P4 hardware — MIPI-CSI/DSI with the on-chip ISP, hardware JPEG encode/decode, hardware H.264 encode, PPA/2D-DMA image acceleration, the LP core and its own peripherals, USB HS OTG vs FS OTG vs USB-Serial-JTAG, TWAI/CAN, Ethernet MAC, SDIO host, in-package PSRAM up to 32MB, HP-core task pinning, and the PIE instruction extensions behind on-device AI/DSP. Trigger on MIPI-CSI/MIPI-DSI/camera/ISP/JPEG/H.264/PPA/LP-core/deep-sleep/PSRAM/USB-HS-OTG questions on an ESP32-P4, or any M5Stack P4 board (Tab5, Stamp-P4) needing depth beyond its own SKILL.md. For pinouts/wiring use that board's skill. Also relevant when a user asks why their ESP32-P4 board has no WiFi/Bluetooth and needs a companion radio chip.
iot-forge/m5stack-skills · ★ 2 · AI & Automation · score 73
Install: claude install-skill iot-forge/m5stack-skills
# ESP32-P4 chip capabilities This skill is the **chip layer**, not a board layer. A board skill (e.g. `m5stack-tab5`) tells you what's wired to what on one specific product; this skill tells you what the ESP32-P4 silicon itself can do — the peripherals, multimedia hardware, low-power modes, memory options, and concurrency model that are the same on every ESP32-P4 board regardless of vendor. Read a board's own skill first for pin numbers and I2C addresses, then come here when the user wants to go deeper on a capability than "call the vendor's high-level library and move on" — e.g. driving the MIPI camera pipeline, encoding H.264 in hardware, using the LP core while the main system sleeps, or getting real throughput out of USB HS OTG. ## The one thing every ESP32-P4 user needs to know: no radio, ever Unlike every other current ESP32 variant, **the P4 has zero wireless hardware** — no WiFi, no Bluetooth, no Thread/Zigbee/802.15.4. This isn't a stripped-down SKU; the chip was designed as a high-performance applications/HMI processor and pairs with a separate radio chip (an ESP32-C6 on M5Stack's Tab5 and Stamp-P4, most commonly) over SDIO or SPI when a project needs wireless. If a user asks "why won't `WiFi.begin()` compile/link" or "how do I get WiFi on my P4 board," the answer is always "it needs a companion radio chip and a host-side driver (ESP-Hosted or similar) talking to it" — not a missing library or wrong board setting. See that board's own skill (e.g. the `m5stack-tab