ES8388 board and ESP32 #8
-
I saw a few folks posting about ES8388 having issues with I2C. This issue is real as I can find the device using Arduino Example Wire/WireScan at address 0x10 but audio driver does not communicate on correct I2C settings. I enabled DEBUG mode in the Example audio-driver/audiotools/audiotools-custom-max and followed the source code. I believe there is an issue with DriverPins.h at
This is not executing
function because I do not set any debug information regarding I2C SDA, SCL and setclock. I added a function to check for the presence of a device on the i2c bus with I call this function right at the beginning of es8388_init with:
My output looks like the following (there is no I2C debug info, that is why I believe the I2C setup is not called):
I do not think I should add
I will continue trying to find the issue. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Initially the API used ESP32 I2C port naming conventions which is Arduino Port << 1. Since this is confusing, I have changed the logic to use Arduino logic as well, so that the respult from the portscan can be used w/o any changes |
Beta Was this translation helpful? Give feedback.
Initially the API used ESP32 I2C port naming conventions which is Arduino Port << 1. Since this is confusing, I have changed the logic to use Arduino logic as well, so that the respult from the portscan can be used w/o any changes
#6