Skip to main content

ESP32-P4-NANO-WIFI6-DB

ESP32-P4-NANO-WIFI6-DB

ESP32-P4-NANO-WIFI6-DB is a development board based on the ESP32-P4NRW32X. The board features a dual-core high-performance processor and a single-core low-power processor, and includes an onboard ESP32-C5-MINI-1U wireless module that provides 2.4 GHz / 5 GHz dual-band Wi-Fi 6 and Bluetooth 5 (LE).

The board brings out MIPI-CSI, MIPI-DSI, USB 2.0 OTG, Ethernet, TF, audio, and GPIO interfaces, making it suitable for HMI, edge computing, and I/O expansion applications. Actual functionality is subject to the firmware and software resources provided with this model.

If you are looking for:

  • Coding with AI tools: Click Ask AI and select an AI tool to ask questions about this page, or choose Copy page to copy its content and paste it into an AI tool for coding assistance.
  • Schematics, datasheets, and example code: See Resources
  • Arduino development: See Working with Arduino
  • ESP-IDF development: See Working with ESP-IDF
  • Troubleshooting: See Product FAQ or contact Technical Support
SKUProduct
35554ESP32-P4-NANO-WIFI6-DB
35555ESP32-P4-NANO-WIFI6-DB-KIT-A
35556ESP32-P4-NANO-WIFI6-DB-KIT-B
35557ESP32-P4-NANO-WIFI6-DB-KIT-C
35559ESP32-P4-NANO-WIFI6-DB-KIT-D

The 10.1inch DSI touchscreen is included only in Kit D. For other kits, if you need a display, you must prepare a compatible display separately; whether the camera module and PoE module are included depends on the corresponding configuration list.

Onboard Resources​

ESP32-P4-NANO-WIFI6-DB Onboard Resources

  1. ESP32-P4NRW32X: Package-on-package with 32 MB PSRAM.
  2. ESP32-C5-MINI-1U: Provides dual-band Wi-Fi 6 and Bluetooth 5 (LE) via an external antenna.
  3. Display Interface: MIPI-DSI, 2-lane. Compatible with 5 / 7 / 8 / 10.1-inch DSI screens.
  4. Camera Interface: MIPI-CSI, 2-lane. Compatible with OV5647 camera.
  5. Type-C Port: For 5 V power, program flashing, and serial debugging.
  6. USER-LED: Power indicator.
  7. BOOT Button: Press during power-on or reset to enter download mode.
  8. RESET Button: Resets the board.
  9. PoE Module Power / External Power Input: For 5 V power input or compatible PoE module.
  10. RTC Battery Header: For a rechargeable RTC battery (only rechargeable RTC batteries supported).
  11. Microphone: Onboard audio capture.
  12. PoE Module Connector: For an optional compatible PoE expansion board.
  13. Type-A Port: USB 2.0 OTG High-Speed interface.
  14. 100 Mbps RJ45 Ethernet Port: 100 Mbps Ethernet interface.
  15. Speaker Header: MX1.25 2P, supports 8 Ω 2 W speakers.
  16. GPIO Headers: Two 2 × 13, 2.54 mm expansion pin headers.
  17. TF Card Slot: For local storage and media expansion.

Peripheral Quick Reference​

ModuleDevice / FunctionInterfaceAddress / ParametersGPIO / Signals
LCDMIPI-DSI displayMIPI-DSI2-lane; supports 5 / 7 / 8 / 10.1-inch panel configurationsLCD reset not connected; backlight controlled via shared I2C
TouchGT911 capacitive touchI2C7-bit address 0x5D / 0x14SDA=GPIO7, SCL=GPIO8; RST / INT not connected
LCD BacklightBacklight controllerI2C7-bit address 0x45; brightness register 0x96SDA=GPIO7, SCL=GPIO8
CameraMIPI-CSI camera interfaceMIPI-CSI + SCCB2-lane; camera model and address depend on module documentationSCCB shared on GPIO7 / GPIO8; XCLK / RESET not connected
AudioES8311 CodecI2C + I2S7-bit I2C address 0x18; 8-bit write address 0x30; single analog microphoneI2C: SDA=GPIO7, SCL=GPIO8; MCLK=GPIO13, SCLK=GPIO12, WS=GPIO10, DOUT=GPIO9, DIN=GPIO11
Amplifier ControlOnboard speaker amp enableGPIOHigh level to enableGPIO53
TF CardSDMMC 4-bitSDMMC4-bit modeCLK=GPIO43, CMD=GPIO44, D0=GPIO39, D1=GPIO40, D2=GPIO41, D3=GPIO42; power control=GPIO45
EthernetIP101GRI PHYRMII + SMIPHY address 1; 50 MHz REF_CLK external inputCRS_DV=GPIO28, RXD0=GPIO29, RXD1=GPIO30, MDC=GPIO31, TXD0=GPIO34, TXD1=GPIO35, TX_EN=GPIO49, REF_CLK=GPIO50, RESET=GPIO51, MDIO=GPIO52
ESP32-C5ESP-Hosted communicationSDIOWi-Fi 6 / Bluetooth 5 (LE) co-processorCLK=GPIO18, CMD=GPIO19, D0=GPIO14, D1=GPIO15, D2=GPIO16, D3=GPIO17, RESET=GPIO54

Pin Definitions​

When using the GPIO headers on the ESP32-P4-NANO-WIFI6-DB, note the multiplexed functions marked on the pin diagram. Some GPIOs are already connected to onboard peripherals; before using them as general-purpose I/O, confirm that the corresponding peripheral is not enabled.

ESP32-P4-NANO-WIFI6-DB Pinout

Expansion Interface​

TypeSignals
Power5V / 3V3 / GND
I2CSDA(GPIO7) / SCL(GPIO8)
UARTTX(GPIO37) / RX(GPIO38)
GPIOGPIO0 / GPIO1 / GPIO2 / GPIO3 / GPIO4 / GPIO5 / GPIO6 / GPIO20 / GPIO21 / GPIO22 / GPIO23 / GPIO24 / GPIO25 / GPIO26 / GPIO27 / GPIO32 / GPIO33 / GPIO36 / GPIO45 / GPIO46 / GPIO47 / GPIO48 / GPIO53 / GPIO54

GPIO Allocation​

The table below lists the GPIOs already occupied by onboard circuits and those brought out to expansion headers.

GPIOSignal NameConnected ToRemarks
GPIO0GPIO0XTAL_32K_N / (reserved pad / pin header)To use as normal GPIO, consider removing R32 to disable XTAL_32K function
GPIO1GPIO1XTAL_32K_P / (reserved pad / pin header)To use as normal GPIO, consider removing R36 to disable XTAL_32K function
GPIO2GPIO2Reserved pad / pin headerExpansion header GPIO2
GPIO3GPIO3Reserved pad / pin headerExpansion header GPIO3
GPIO4GPIO4Reserved pad / pin headerExpansion header GPIO4
GPIO5GPIO5Reserved pad / pin headerExpansion header GPIO5
GPIO6GPIOExpansion header / ESP32-C5-MINI-1UC5 IO02
GPIO7I2C SDAES8311, GT911, LCD backlight, camera SCCB, expansion headerShared I2C SDA
GPIO8I2C SCLES8311, GT911, LCD backlight, camera SCCB, expansion headerShared I2C SCL
GPIO9I2S DOUTES8311 DSDINAudio playback data
GPIO10I2S WSES8311 LRCKAudio frame sync
GPIO11I2S DINES8311 ASDOUTAudio capture data
GPIO12I2S SCLKES8311 SCLKAudio bit clock
GPIO13I2S MCLKES8311 MCLKAudio master clock
GPIO14GPIO14ESP32-C5-MINI-1UC5 SDIO D0
GPIO15GPIO15ESP32-C5-MINI-1UC5 SDIO D1
GPIO16GPIO16ESP32-C5-MINI-1UC5 SDIO D2
GPIO17GPIO17ESP32-C5-MINI-1UC5 SDIO D3
GPIO18GPIO18ESP32-C5-MINI-1UC5 SDIO CLK
GPIO19GPIO19ESP32-C5-MINI-1UC5 SDIO CMD
GPIO20GPIO20Reserved pad / pin headerExpansion header GPIO20
GPIO21GPIO21Reserved pad / pin headerExpansion header GPIO21
GPIO22GPIO22Reserved pad / pin headerExpansion header GPIO22
GPIO23GPIO23Reserved pad / pin headerExpansion header GPIO23
GPIO24GPIO24Reserved pad / pin headerExpansion header GPIO24 / expansion header USB1P1_N0
GPIO25GPIO25Reserved pad / pin headerExpansion header GPIO25 / expansion header USB1P1_P0
GPIO26GPIO26Reserved pad / pin headerExpansion header GPIO26 / expansion header USB1P1_N1
GPIO27GPIO27Reserved pad / pin headerExpansion header GPIO27 / expansion header USB1P1_P1
GPIO28GPIO28IP101GRI RMII CRS_DVCarrier sense / receive data valid multiplexed signal, PHY → ESP32-P4 (input)
GPIO29GPIO29IP101GRI RMII RXD0Receive data bit 0, PHY → ESP32-P4 (input)
GPIO30GPIO30IP101GRI RMII RXD1Receive data bit 1, PHY → ESP32-P4 (input)
GPIO31GPIO31IP101GRI SMI MDCPHY management interface clock, ESP32-P4 → PHY (output)
GPIO32GPIO32Reserved pad / pin headerExpansion header GPIO32
GPIO33GPIO33Reserved pad / pin headerExpansion header GPIO33
GPIO34GPIO34IP101GRI RMII TXD0Transmit data bit 0, ESP32-P4 → PHY (output)
GPIO35GPIO35IP101GRI RMII TXD1 / BOOTStrapping pin; transmit data bit 1, ESP32-P4 → PHY (output)
GPIO36GPIO36Reserved pad / pin headerStrapping pin; external 3.3 V pull-up
GPIO37UART0_TXDExpansion header / serial interfaceUART0 TX; not recommended for general-purpose use
GPIO38UART0_RXDExpansion header / serial interfaceUART0 RX; not recommended for general-purpose use
GPIO39SD_D0TF cardSDMMC 4-bit data line
GPIO40SD_D1TF cardSDMMC 4-bit data line
GPIO41SD_D2TF cardSDMMC 4-bit data line
GPIO42SD_D3TF cardSDMMC 4-bit data line
GPIO43SD_CLKTF cardSDMMC clock line
GPIO44SD_CMDTF cardSDMMC command line
GPIO45SD_VDD_ENTF card power control / expansion headerLow to enable; not recommended for general-purpose use while TF function is active
GPIO46GPIO46Reserved pad / pin headerExpansion header GPIO46
GPIO47GPIO47Reserved pad / pin headerExpansion header GPIO47
GPIO48GPIO48Reserved pad / pin headerExpansion header GPIO48
GPIO49GPIO49IP101GRI RMII TX_ENTransmit enable, ESP32-P4 → PHY (output)
GPIO50GPIO50IP101GRI RMII REF_CLK50 MHz RMII reference clock, PHY → ESP32-P4 (input)
GPIO51GPIO51IP101GRI PHY RESETPHY hardware reset control, ESP32-P4 → PHY (GPIO output)
GPIO52GPIO52IP101GRI SMI MDIOPHY management interface data, bidirectional
GPIO53PA_CTRLNS4150B enable / expansion headerActive high; not recommended for general-purpose use while audio function is active
GPIO54C5_CHIP_PUESP32C5 enable / expansion headerHigh to enable, low to reset
LCD and Touch Pins
SignalGPIO / SignalDescription
MIPI-DSIMIPI interface2-lane display interface
LCD_RSTNot connectedNo dedicated GPIO for LCD reset
LCD_BLI2C 0x45Backlight controlled via register 0x96
TP_SCLGPIO8GT911 touch I2C SCL, shared bus
TP_SDAGPIO7GT911 touch I2C SDA, shared bus
TP_RSTNot connectedGT911 reset signal not connected
TP_INTNot connectedGT911 interrupt signal not connected; uses polling mode
Audio and TF Card
Signal / PeripheralGPIO / SignalDescription
I2S_MCLKGPIO13ES8311 master clock
I2S_SCLKGPIO12ES8311 bit clock
I2S_WSGPIO10ES8311 frame sync
I2S_DOUTGPIO9ESP32-P4 output to ES8311
I2S_DINGPIO11ES8311 output to ESP32-P4
Amplifier enableGPIO53Active high
SD_D0 / SD_D1GPIO39 / GPIO40SDMMC data lines
SD_D2 / SD_D3GPIO41 / GPIO42SDMMC data lines
SD_CLK / SD_CMDGPIO43 / GPIO44SDMMC clock and command lines
SD_VDD_ENGPIO45TF card power control, low to enable
Ethernet Pins
SignalGPIODirection / Description
RMII_CRS_DVGPIO28IP101GRI → ESP32-P4; carrier sense / receive data valid multiplexed signal
RMII_RXD0GPIO29IP101GRI → ESP32-P4; receive data bit 0
RMII_RXD1GPIO30IP101GRI → ESP32-P4; receive data bit 1
SMI_MDCGPIO31ESP32-P4 → IP101GRI; PHY management interface clock
RMII_TXD0GPIO34ESP32-P4 → IP101GRI; transmit data bit 0
RMII_TXD1GPIO35ESP32-P4 → IP101GRI; transmit data bit 1
RMII_TX_ENGPIO49ESP32-P4 → IP101GRI; transmit enable
RMII_REF_CLKGPIO50IP101GRI → ESP32-P4; 50 MHz RMII reference clock
PHY_RESETGPIO51ESP32-P4 → IP101GRI; PHY hardware reset control
SMI_MDIOGPIO52Bidirectional; PHY management interface data
I2C Device Summary
DeviceModel / FunctionI2C AddressI2C PinsNotes
Audio CodecES83117-bit 0x18; 8-bit write address 0x30GPIO7 / GPIO8Onboard audio capture and playback
TouchGT9110x5D / 0x14GPIO7 / GPIO8Both addresses are tried; RST / INT not connected
LCD BacklightBacklight controller0x45GPIO7 / GPIO8Brightness register is 0x96
Camera SCCBExternal camera moduleDepends on moduleGPIO7 / GPIO8Shares bus with onboard I2C devices

Precautions​

  • GPIO7 / GPIO8 are the onboard shared I2C bus. When connecting external I2C devices, confirm that the addresses do not conflict.
  • GPIO45 is used for TF card power control, GPIO53 for the audio amplifier, and GPIO54 for ESP32-C5 communication reset; it is not recommended to use these as general-purpose GPIO while the corresponding peripherals are active.
  • GPIO28–GPIO31, GPIO34–GPIO35, and GPIO49–GPIO52 are used for Ethernet RMII / SMI and PHY reset; it is not recommended to use them as general-purpose GPIO.
  • The LCD reset, GT911 reset, and interrupt signals are not connected; the corresponding control is handled through software in the display or touch drivers.

Dimensions​

ESP32-P4-NANO-WIFI6-DB Product Dimensions

Development Methods​

Arduino is generally easier to get started with and more beginner-friendly for hobbyists. ESP-IDF offers a more complete development toolchain and finer-grained system control, making it suitable for complex projects or applications with higher performance requirements.

warning

ESP32-P4 currently has limited adaptation on the Arduino platform. To ensure development stability, it is recommended to use ESP-IDF for development at this stage.

  • ESP-IDF, short for Espressif IoT Development Framework, is Espressif's development framework for the ESP series of chips. It is developed using the C language, including a compiler, debugger, and flashing tool, etc., and can be developed via the command lines or through an integrated development environment (such as Visual Studio Code with the Espressif IDF plugin). The plugin offers features such as code navigation, project management, and debugging, etc. We recommend using VS Code for development. For detailed configuration steps, refer to the ESP-IDF (VS Code) Development Environment Setup Guide, which also provides relevant example programs for reference.