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.

TAS5706 EVM2 + TAS5602 EVM2 : Problem transfering the I2C script

Other Parts Discussed in Thread: TAS5706, TAS5602, TAS5706B

Hello,

I'm currently trying to setup the TAS5706 EVM2 with the TAS5602 EVM2 for a 2.1 audio system.
After finding the correct values for all my biquad, channel volume, DRCs etc.. using GDE, I wrote the corresponding script and tried to transfer it via USB to the board using the I2C memory tool. I then acoustically measure my speaker in a anechoic room.

Problem is I never get the same frequency response everytime I send the file to the board :
 - sometimes satellites level is higher than the subwoofer, sometimes it's the inverse
 - Sometimes subwoofer is not working but it's seems to be solved by re-execute the script
 - Sometimes Subwoofer and satellites are out of phase
 - Sometimes biquads value are not correct.
 - Sometimes the response is correct

Another stange thing is that, everytime, after 10s, the global level decrease by 2dB SPL before stabilizing.

I use the 5706EVM2 board in BTL mode for the 2 satellites, and 5602EVM2 board in PBTL mode for the subwoofer.
I do a master reset, reconnect to the board with GDE and inject the script with I2C memory tool everytime. 

I've attached my script for your reference.0755.Script.ini 

Can anyone please help me?

Thanks, David.

  • FYI, I already try to replace the USB cable but with no results.

    After further testing, it seems that the global level decreasing during 10 first sec is due to DRC. Because when I remove DRC register lines in the script, the level stay stable. But no improvement regarding the other problems.

    Many thanks in advance for your help.

    David

  • Hi, David,

    The TAS5706B is a really old part, and it has some particular things you have to follow when programming the registers via I2C. Make sure you are not violating any of these. They are discussed in the data sheet in the section titled, "I2C SERIAL CONTROL COMMAND CHARACTERISTICS"

    -d2