TAS5825M: TAS5825M startup and the PPC3 settings when generated eq.h

Hi 

1. If I can't provide the I2S signal before writing the I2C signal, is there a way to properly start the TAS5825M?

-> if there is no I2s signal, the clk error and no output will happen. so that the initial register value may not be able to write rightly.

2. If the I2S signal must be provided at the start-up sequence, must the I2S signal be continuously provided?

-> No, after you start up successfully, you doesn't need provide i2s continuously. if i2s halt during operation, the clk error and no output will happen. but if you reopen i2s, amp will recovery automatically.

3. What is the difference between the current state-cold boot of ppc3 and the EQ.h generated by default? Why can the EQ.h file generated by current state-cold boot get the correct AP data but the eq.h generated by default cannot? Can the EQ.h file generated by current state-cold boot be used directly?

-> Here, the "by default" you mean "Current State"? Originally, the current state-cold is developed when no i2s signal been input. but it is not recommend to use it for this function seems not work very well at sometime, so we recommend you still need to input i2s at start-up.

I am afraid that because you don't input the i2s signal, so that the clock error happen and EQ parameter haven't been input rightly.

if using current-state cold, the clock detect will be disabled, so that error doesn't happen and EQ parameter been write rightly.

Although current-state cold work right at your situation, but we still recommend you should follow the start-up sequence on the datasheet.

thanks.

jesse

Hi jesse,

Thank you for your kindly reply.

My customer has some additional questions as follows:

1. Does disabling clock detection mean the 5825M uses the internal clock? The rate at which we write I2C during initialization is not high, so can it be considered basically reliable? (It seems that there is no failure to write EQ during the experiment)

2. We want to initialize the power amplifier before the bluetooth master outputs the I2S signal. So if there is no way to provide a stable I2S signal when the amplifier boots up, is it common practice to use the eq generated by current state -cold boot(or disable detect clock by write 29h)? Is there any other better way?

Best Regards,
Yuki Liu