Error initializing I2C #5
-
|
Hi, I've been working on my code for a couple of weeks (using ES8388 as an ADC for ESP32 S3). Most of the time, I didn't get anything from StreamCopy and I kind of figured why. There is some error in the I2C communication, but I'm not exactly sure what it could be. Info: output_device: 0 I attached my code below: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Since the ES8388 is working perfectly with the AudioKit, it can only be the initialization of I2C. Are you doing this via the pin definitions or yourself ? Both options are explained in the Wiki |
Beta Was this translation helpful? Give feedback.
-
|
I'm using the pin definitions. (This is the line) my_pins.addI2C(audio_driver::PinFunction::CODEC, 4, 3, 0x10, 100000, Wire); |
Beta Was this translation helpful? Give feedback.
-
|
Did you try with some other pins ? The default (recommended?) pins would be
|
Beta Was this translation helpful? Give feedback.
-
|
You can try to set the log mode to debug to see in detail what's going on. |
Beta Was this translation helpful? Give feedback.
-
|
I used the scan sketch to verify the I2C connection, and I showed that the codec had the 0x10 address. Should I change it to 0x20 anyways? Scanning for I2C devices ... |
Beta Was this translation helpful? Give feedback.
-
|
Set the log level to debug and you can also try to reduce the I2C speed. |
Beta Was this translation helpful? Give feedback.
-
|
With the latest commits, I changed the I2C address logic to use Arduino Conventions: This should be less confusing, since it the log you will see the values that you expect. |
Beta Was this translation helpful? Give feedback.
-
|
endTransmission returns: byte , which indicates the status of the transmission: |
Beta Was this translation helpful? Give feedback.
Since the ES8388 is working perfectly with the AudioKit, it can only be the initialization of I2C. Are you doing this via the pin definitions or yourself ? Both options are explained in the Wiki