UAC exemple for ESP 32 P4 does not run on ESP32 P4 EV board (AEGHB-1102)

[digitalLumberjack]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

5.3, 5.4, master

Espressif SoC revision.

ESP34 S4 EV Board

Operating System used.

Linux

How did you build your project?

Command line with CMake

If you are using Windows, please specify command line type.

None

Development Kit.

ESP34 S4 EV Board

Power Supply used.

USB

What is the expected behavior?

I excpeted it to run as an UAS USB device.

What is the actual behavior?

i2c driver seems to be mixed with old driver

Steps to reproduce.

1. Clone this repository
2. cd to esp-iot-solution/examples/usb/device/usb_uac/
3. make and flash

Debug Logs.

I (4059) cpu_start: Pro cpu start user code
I (4059) cpu_start: cpu freq: 360000000 Hz
I (4059) app_init: Application information:
I (4062) app_init: Project name:     usb_uac
I (4067) app_init: App version:      6f25eba1
I (4072) app_init: Compile time:     Jun  3 2025 17:25:22
I (4078) app_init: ELF file SHA256:  23e9fbf7a...
I (4084) app_init: ESP-IDF:          v5.3.3-dirty
I (4089) efuse_init: Min chip rev:     v0.1
I (4094) efuse_init: Max chip rev:     v1.99 
I (4099) efuse_init: Chip rev:         v0.1
I (4104) heap_init: Initializing. RAM available for dynamic allocation:
I (4111) heap_init: At 4FF174F0 len 00023AD0 (142 KiB): RAM
I (4117) heap_init: At 4FF3AFC0 len 00004BF0 (18 KiB): RAM
I (4124) heap_init: At 4FF40000 len 00060000 (384 KiB): RAM
I (4130) heap_init: At 50108080 len 00007F80 (31 KiB): RTCRAM
I (4136) heap_init: At 3010005C len 00001FA4 (7 KiB): TCM
I (4143) esp_psram: Adding pool of 32768K of PSRAM memory to heap allocator
I (4151) spi_flash: detected chip: generic
I (4155) spi_flash: flash io: dio
W (4159) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
E (4172) i2c: CONFLICT! driver_ng is not allowed to be used with this old driver

More Information.

No response

[leeebo]

@digitalLumberjack The USB Type-C interface of the P4 EV Board cannot supply power externally, so it cannot directly support Type-C headphones. You can use a Type-A to Type-C adapter to connect from the Type-A interface.

[digitalLumberjack]

Hello thank you @leeebo for your answer.

I'm trying to run this example : https://github.com/espressif/esp-iot-solution/tree/master/examples/usb/device/usb_uac, to create a PC -> ESPP4 -> CODEC -> SPEAKER

The example project specify the compatibility with the p4 ev board, but does not work because E (4172) i2c: CONFLICT! driver_ng is not allowed to be used with this old driver. I made no modifications.

I have used the example code to make it work on ESP32 custom board and it works with a bug i'll talk about in an other issue.

[leeebo]

@digitalLumberjack Oh, sorry for the mistake, I thought you were running USB Host UAC.

For the error message in USB Device UAC example, It seems to be caused by the new version of the IDF I2C driver. You can temporarily switch to IDF 5.2 version to use this example. For support of the new version of IDF, we will fix it as soon as possible.

[digitalLumberjack]

Hello @leeebo thank you :)

Sadly there are dependencies on idf >= 5.3 on transitive dependencies.

I was trying to make the project run on esp32-p4 to compare to my main issue when i run the project on ESP32-S3 that I tried to explain here:
#525

[leeebo]

Hi @digitalLumberjack , please set CONFIG_CODEC_I2C_BACKWARD_COMPATIBLE=n to build with idf >= 5.3

[digitalLumberjack]

Hi @leeebo, thank you for the support :)
It worked and I'm currently running the example on the esp32p4 ev board.
I have the exact same issue as in #525, so I'll continue ton investigate there, maybe you can join if you think you can have any clues I can check to understand what is happening.

[14790897]

How to set CONFIG_CODEC_I2C_BACKWARD_COMPATIBLE=n?
I don't find it