-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W (1852) i2s_common: GPIO 33 is not usable, maybe conflict with othe (BSP-541) #377
Comments
if i change the bsp_espbox_disp_example.c in a Way that i change from: /* Initialize audio */
app_audio_init(); to /* Initialize audio */
//app_audio_init(); then the Example runs but no Sound. |
The GPIO reservation feature is a rather new one in ESP-IDF so this can be red herring. @L-KAYA Could you please check why this warning is displayed when GPIOs 33 and 34 are exclusively used by I2S in this example? Also the error message is very confusing... @diplfranzhoepfinger Audio playback works OK on my board without any changes in the code. The recording path is distorted, I'll have a look soon |
This warning I still need to check the recording path distortion |
I have been working with another ESP32-S3 board and have just been wrangling my own GPIO33 issue. The problem is that with large PSRAM's (8MB), the S3 uses a wide data path. GPIO33 is one of the lines needed (D4 I think). So either you use PSRAM and avoid the alternate use, or you disable PSRAM and use the alternative function. One or the other. |
Correct, for Octal PSRAM, GPIO33 is reserved for D4 signal to PSRAM. M5Stack CoreS3 has Quad PSRAM, so the pin is usable |
Excellent! Thanks. |
Board
M5Stack CoreS3
Hardware Description
M5Stack CoreS3
IDE Name
Espressif-IDE
Operating System
Linux
Description
https://github.com/espressif/esp-bsp/tree/master/examples/display_audio_photo
the Display blinks up a short moment, then goes dark.
Log:
Sketch
Other Steps to Reproduce
I have checked existing issues, README.md and ESP32 Forum
The text was updated successfully, but these errors were encountered: