TAS2505: (Random) no sound issue; need explanation on driver code changes

The attached are customer's logs during no-sound event (tas2505_reg_all_fault.log) and normal operation(tas2505_reg_all_ok.log).

The two register dumps look identical though, you could double check it with BeyondCompare, etc.https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/6/tas2505_5F00_reg_5F00_all.7z

Any idea on the values here?

Thanks,

Mingrui

Hi Mingrui,

Can you let me know if the latest driver can fix their issue ?

This commit is aimed to correct the power up sequence,  we should power up DAC first, then power up SPK.

You can refer to this note, https://e2e.ti.com/support/audio-group/audio-internal/f/audio---internal-forum/1166194/tas2505-q1-tas2505-q1-tas2505-software-timing?tisearch=e2e-sitesearch&keymatch=Xiaoxiang%252525252520tas2505#

Thanks

Kevin

Hi Kevin,

Changing the order of power-up sequence helps resolving their problem. They were originally doing SPK-DAC order, and now switching to the DAC-SPK order works.

Now they want to know the root cause of this problem, i.e. why powering up SPK first might result in random no-sound issue. Only after obtaining a detailed explanation, the end customer's code would switch onto the new power-up sequence.

They are also confused by the difference in the order said in the application note.

In the most recent app note (SLAU762B, revised in July 2023), in Chap 3.4.12 (DAC Setup), it says that power up SPK first and then DAC.

But in the example section 5.1, it says powerup DAC first and then DAC.

Is it merely typo? Or my explanation/interpretation here is wrong?

Thanks,

Mingrui