This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TAS3204 I2C wait states required?

Other Parts Discussed in Thread: TAS3204

I now have the TAS3204 up and running on my own PWB using a PIC micro to control the run time properties of the DAP using the i2c bus. However, I am experiencing unpredictable and intermittent problems with the DAP. It will be playing audio just fine. When the micro sends an i2c command to one of the volume components or one of the equalizers, it sometimes works and sometimes the audio will abruptly cut off. Sometimes it comes back with a subsequent i2c command but mostly it requires a DAP reset. I'm running the i2c bus at 100KHz and a message that causes the audio to cut off looks perfectly good on the oscilloscope.

In the older TAS3004 DAP, i2c wait states were required after volume, tone, and some other i2c commands. I don't see any mention of i2c wait states in the TAS3204 data sheet. Are there limits on how fast commands can be sent to the TAS3204 DAP when the DAP is in slave mode?