-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
esp32-p4-function-ev-board 开发板运行i2s_es8311运行不正常 (IDFGH-13389) #14297
Comments
@666wsp have you checked this code? |
Hi, @suda-morris ,I think he was using this demo and I had the same problem using this routine |
@Y1hsiaochunnn Yes, you're right, this demo doesn't seem to be running correctly for esp32-p4 at the moment |
Swap the I2S DI and DO GPIO can help, thanks for reporting! |
@L-KAYA Thanks for the reply, I really didn't look closely at these pin definitions, I can run it successfully with my modifications |
Hi,@L-KAYA ,I'm running the above I2S demo with ESP32-P4 Fuction_EV_Board V1.4 but it doesn't work, I checked the pin definition and it seems to be right |
I just got in my ESP32-P4 board and I am having the same problem. The example builds and runs, but there is no audio coming from speaker in either of the two modes. |
Please refer to this comment in #15047 if you still fail to get the audio by speaker, but success by earphone. The P4 boards disable the PA by default. Please try to pull up the |
Answers checklist.
IDF version.
v5.3-beta2-281-g44f58ecb51
Espressif SoC revision.
ESP32-P4 chip revision: v0.1
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
esp32-p4-function-ev-board
Power Supply used.
USB
What is the expected behavior?
在运行I2S_ES8311实例时候使用功能没法正常运行,Example mode设置为music时喇叭也没发音,设置为echo时也没有捕获到外部音频在喇叭中播放
What is the actual behavior?
运行程序时喇叭会有发音
Steps to reproduce.
1、我使用自带的出厂固件运行测试喇叭能正常工作,证明ES8311和功放电路完全没有问题
2、在运行I2S_ES8311demo时候我使用逻辑分析I2C通讯正常
3、将功放芯片PA_CTRL引脚设置为高电平输出打开功放输出喇叭也没有正常发音
Debug Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered: