Working with ESP-IDF

This chapter includes the following sections:

• ESP-IDF Getting Started
• Setting Up the ESP-IDF Development Environment
• ESP32-P4-WIFI6-DB Example
  • Quick Run
  • LCD Panel Selection
  • Recommended Validation Order
  • ESP-IDF Example Index
  • Pre‑run Checks

ESP-IDF Getting Started

New to ESP32 ESP-IDF development and looking to get started quickly? We have prepared a general Getting Started Tutorial for you.

• Section 1: Environment Setup
• Section 2: Running Examples
• Section 3: Creating a Project
• Section 4: Using Components
• Section 5: Debugging
• Section 6: FreeRTOS
• Section 7: Peripherals
• Section 8: Wi-Fi Programming
• Section 9: BLE Programming

Please Note: This tutorial uses the ESP32-S3-Zero as a teaching example, and all hardware code is based on its pinout. Before you start, it is recommended that you check the pinout of your development board to ensure the pin configuration is correct.

Setting Up the ESP-IDF Development Environment

info

The ESP-IDF BSP and brookesia_test in the ESP32-P4-WIFI6-DB repository require ESP-IDF >=5.5, and 10_wifi_antenna_tesat requires ESP-IDF >=6.0. These are the version constraints declared in the component manifest. Dependent components may impose additional requirements. For the component and configuration requirements of specific examples, refer to the README in the corresponding example directory.

note

The following guide uses Windows as an example, demonstrating development using VS Code + the ESP-IDF extension. macOS and Linux users should refer to the official documentation.

Version Selection

The screenshots in this section use ESP-IDF V5.5.2 as an example. When installing, please select the ESP-IDF version that matches your board's example.

Install the ESP-IDF Development Environment

1. Download the installation manager from the ESP-IDF Installation Manager page. This is Espressif's latest cross-platform installer. The following steps demonstrate how to use its offline installation feature.

   Click the Offline Installer tab on the page, then select Windows as the operating system and the ESP-IDF version you need (the version shown in the screenshot is for reference only — choose the version that fits your actual needs).

   

   After confirming your selection, click the download button. The browser will automatically download two files: the ESP-IDF Offline Package (.zst) and the ESP-IDF Installer (.exe).

   

   Please wait for both files to finish downloading.

2. Once the download is complete, double-click to run the ESP-IDF Installer (eim-gui-windows-x64.exe).

   The installer will automatically detect if the offline package exists in the same directory. Click Install from archive.

   

   Next, select the installation path. We recommend using the default path. If you need to customize it, ensure the path does not contain Chinese characters or spaces. Click Start installation to proceed.

   

3. When you see the following screen, the ESP-IDF installation is successful.

   

4. We recommend installing the drivers as well. Click Finish installation, then select Install driver.

   

Install Visual Studio Code and the ESP-IDF Extension

1. Download and install Visual Studio Code.

2. During installation, it is recommended to check Add "Open with Code" action to Windows Explorer file context menu to facilitate opening project folders quickly.

3. In VS Code, click the Extensions icon in the Activity Bar on the side (or use the shortcut Ctrl + Shift + X) to open the Extensions view.

4. Enter ESP-IDF in the search box, locate the ESP-IDF extension, and click Install.

   

5. For ESP-IDF extension versions ≥ 2.0, the extension will automatically detect and recognize the ESP-IDF environment installed in the previous steps, requiring no manual configuration.

ESP32-P4-WIFI6-DB Example

The ESP-IDF BSP and example programs for the ESP32-P4-WIFI6-DB are maintained in the ESP32-P4-WIFI6-DB Example. You can obtain the board‑level code and example programs from this repository.

The relevant directories in the repository are:

• firmware/esp32_p4_wifi6_db/: ESP-IDF BSP, header files, Kconfig, and component manifest.
• examples/esp_idf/: Peripheral examples and Brookesia applications.
• firmware/factory-firmware/: ESP32-P4 firmware for 5, 7, 8, and 10.1inch panels, as well as ESP32-C5 slave firmware.
• ESP32-P4-WIFI6-DB Schematic.

The target chip for the example projects is esp32p4.

Quick Run

The following commands use the 00_board_check example. Switch the terminal's current directory to the example directory and run them, replacing COMx with the actual serial port of the ESP32-P4:

cd examples/esp_idf/00_board_check
idf.py set-target esp32p4
idf.py build
idf.py -p COMx flash monitor

Display, camera, and Wi-Fi related examples also require selecting the actually connected LCD panel and entering Wi-Fi credentials via idf.py menuconfig before building. The component manager resolves dependencies during the configuration phase.

LCD Panel Selection

The BSP selects the LCD panel via the following options:

BSP Option	Panel Controller	Resolution
CONFIG_BSP_LCD_TYPE_720_1280_5_INCH_A	HX8394, 5inch	720 × 1280
CONFIG_BSP_LCD_TYPE_720_1280_7_INCH_A	ILI9881C, 7inch	720 × 1280
CONFIG_BSP_LCD_TYPE_800_1280_8_INCH_A	JD9365, 8inch	800 × 1280
CONFIG_BSP_LCD_TYPE_800_1280_10_1_INCH_A	JD9365, 10.1inch	800 × 1280

The BSP Kconfig defaults to the 10.1inch JD9365, and the default configuration of brookesia_test selects the 8inch JD9365. Before building, select the panel that is actually connected. The default configuration does not override an existing sdkconfig; to confirm the options actually in effect, check the project configuration and the generated build/config/sdkconfig.h.

Recommended Validation Order

It is recommended to run the examples in the following order: first confirm the board‑level peripherals, then verify the display, networking, and other functions:

1. 00_board_check: Board‑level peripheral check.
2. 02_i2c_console_test: I2C bus check.
3. 03_sdmmc_test: SDMMC check.
4. 04_mipi_dsi_test: Display test.
5. 06_wifi_test: Wi-Fi Station test.

ESP-IDF Example Index

Example Directory	Example Content
00_board_check	Outputs chip, Flash, PSRAM, heap memory information, and periodic heartbeat
01_gpio_input_test	Displays GPIO input status on the LCD
02_i2c_console_test	Interactive I2C scan and register read/write console
03_sdmmc_test	TF file write, read, and rename test
04_mipi_dsi_test	LCD output test, currently displaying a solid white screen
05_mipi_csi_test	Uses PPA processing and previews the camera feed on the LCD
06_wifi_test	Wi-Fi Station networking and gateway ping
07_i2s_codec	ES8311 built-in audio playback or microphone loopback
08_usb_host_msc	USB mass storage file operations and sequential read/write speed test
09_bt_controller_mac_addr	Hosted Bluetooth MAC view/configuration and BLE GATT test
10_wifi_antenna_tesat	Wi-Fi scan, STA networking, band, and RSSI logging
brookesia_test	Comprehensive interface including calculator, drawing board, audio, camera, video, settings, Xiaozhi, and GPIO applications

10_wifi_antenna_tesat is the current directory spelling in the repository. For wiring and operation methods, refer to the README and configuration in each example directory.

Pre‑run Checks

• The board implements wireless functionality via the ESP32-C5 wireless co-processor and ESP-Hosted/SDIO. The ESP32-C5 requires compatible ESP-Hosted slave firmware; flashing an ESP32-P4 example will not update the ESP32-C5.
• The I2C bus uses GPIO7 (SDA) and GPIO8 (SCL), connecting to the ES8311, GT911, LCD backlight controller, and camera SCCB bus.
• The ES8311 I2S signals use GPIO13, GPIO12, GPIO10, GPIO9, and GPIO11, and amplifier enable uses GPIO53.
• The TF uses 4-bit SDMMC, card power enable is GPIO45 (active low), and SDMMC IO power uses LDO channel 4.
• The LCD backlight is controlled via the 0x45 device on the shared I2C bus, brightness register 0x96; GT911 uses polling mode.
• ESP-Hosted/SDIO uses GPIO18, GPIO19, GPIO14, GPIO15, GPIO16, GPIO17, and GPIO54.
• For component versions, configuration requirements, and hardware connection details of specific examples, please refer to the README in the corresponding example directory and the board hardware documentation. Build, flash, and run results must be confirmed separately for the selected example, ESP-IDF version, and actual panel.