Hi,
We have a board populated with TAS2505 and have the I2C analyzer to generate and capture the command and responses respectively but look like the amplifier is not responding. How to confirm its working?
BR,
Vageesh
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.
Hi Vageesh,
Are you saying that the I2C is not ACKing any writes or it is ACKing and just not doing what you expect?
Do you have any scope shots of an I2C transaction? The schematic looks ok to me.
Do you have an I2C sniffer?
Best Regards,
dave
Hi Dave,
We have I2C signal generator and analyser from http://www.totalphase.com/products/beagle-i2cspi/
when we send the data 0x18+write+0x00 +0x00+0x00 from the generator to the device we are not seeing the ack in
the analyser. We can send the analyzer log file. Also please let us know how to confirm the device is working?
Thanks in advance.
If the device is not ACKing, it sounds like there must be a very fundamental problem. Have you tried looking at each pin to verify that the correct voltages are present? Assuming that the device is powered properly, it should be ACKing I2C commands.
Hi Vageesh,
From this screen shot, it is not clear that any data is being sent or that the device is NACKing?
Best Regards,
dave
Hi Dave,
The update is we are able to communicate with TAS2505 over I2C.
We have interfaced CC2564 with TAS2505 over I2S and when we are playing the audio we are able to see the pulses on these pins generated from CC2564.Initially we have configured the TAS2505 with configuration settings as in the attachment. But we are observed as soon as we switch on the Speaker, the TAS2505 stops communicating over I2C and not receives any further commands. if you see the command list we are switching on the speaker first and then the DAC so if I2C doesn't responds after we switch on speaker cant enable DAC ,
so please let us what configuration we are missing and help us in getting the correct configuration.
One more concern is that in the reference guide if we see the scripts, the I2C address given as 0x30[0011000] but if we use this same address the device not communicates instead we are using the address 0x18 for which device responding.