• State Resolved
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 69 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TAS5782M: DEQ and AGL functions don't track output level

Oliver Lieder
Prodigy 10 points
Part Number: TAS5782M

Tool/software:

We are trying to implement the DEQ and the AGL on the TAS5782M. When we drive our speaker using the TAS5782EVM and control it using the Purepath Console, everything works perfect. However, when we apply the register values to the amplifier in our End System (DUT), the DEQ and AGL are binary in operation regardless of the volume level. In other words, regardless of the output signal level, when the functions are toggled on, they always fully active.

We’ve also connected the Purepath Console to the I2C bus of our circuit and used the In-System Tuning of the End System Integration module to control the device. We have full control of the amplifier, but once again, as the volume level changes from very low to very high, these functions are always in full engagement. If the AGL is set to -10dB, it cuts the output 10dB regardless of volume. If the DEQ has a +8dB bass boost with a low level threshold of -40dB, the amp will apply +8dB boost at all output levels. Note: All these values work perfect in the EVM.

The bottom line is, it simply appears the amp in our End System isn’t detecting its output.

If I remember correctly, the amp is configured for 48k Standard Processing operation, but I can’t be certain about this.

Any thoughts on how to resolve this issue or things to check would be much appreciated.


Thank You!

Oliver

  • 0
    TI__Mastermind 34840 points

    Hi Oliver

      Using In-System Tuning is a good way to debug, let's continue doing this way.

      When debugging, make sure the jumper J2/J5 on the board is out, to avoid the device on the EVM give ACK.

      Better to cut out the I2C on the DUT, to avoid SOC send different I2C script.

      When you find the function not working correctly, could read back the related register value, to see if it is the same as configure. 

    Oliver Lieder said:
    If I remember correctly, the amp is configured for 48k Standard Processing operation, but I can’t be certain about this.

     PPC3 could choose 48KHz flow also 96KHz flow. Could give us the .ppc3 file, we can help check it.

  • 0 in reply to Shadow He
    Prodigy 10 points

    I was able to resolve the issue, and some of what you suggested was helpful in getting me on the right track. Here are some notes from my experience:

    I was not able to use the TAS5782EVM to connect to my DUT. When I tried, there was no communication, even with J2 and J5 removed. Historically, I have been connecting the GND, SDA, and SCL signals directly from the Pure Path Console Mother Board (PP-CMBEVM) to the I2C bus on the DUT. This has worked in the past and continues to work. 

    I did not cut the lines from the SOC, since I have only a single sample of the DUT to work with and I didn't want to damage it. However, this suggestion along with a suggestion from the factory that I control the volume directly within the TAS5782 gave me the thought that the DEQ and AGL states may have been rewritten by the system microcontroller when I used the App to raise and lower the volume. Once I began controlling the volume directly, the DEQ and AGL retained their programmed states at high and low volume levels. 

    I used the End-system tuning function and then dumped the registers into a file. Changing the modes and comparing the various changes allowed us to capture the necessary settings for our SOC firmware.

    The system is now working properly with full functionality using our App. 

    Thank you,

    Oliver