• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 455 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TAS2770: TAS2770 WAS ALWAYS SHUTDOWN MODE DUE TO TDM CLOCK ERROR

thumu ramakrishna
Prodigy 30 points
Part Number: TAS2770

Hi,

we have interfaced the tas2770 using eval kit with mtk processor.

we are changing the regs using i2c-tools

for dump:

i2cdump -f -y 2 0x41

for setting:

i2cset -f -y 2 0x41 0x00 0x00 (PAGE SET)

i2cset -f -y 2 0x41 0x02 0x0c (PWR_CTRL REG)

but if I read now the i2c dump values it is 0x02 reg is ox02 which is software shutdown

NOTE: the same thing is worked a few days back

OBSERVATIONS:

ALL the value are at reset state only except below

When we are setting the i2cset -f -y 2 0x41 0x00 0x00 then i observed that 0X24(INT_LTCH0) IS 0x04 which is --INT DUE TO TDM ERROR 

please, any idea why this happening ? and how to overcome it

  • 0
    TI__Guru* 95175 points

    Hi Thumu,

    Could you share the configuration you're loading into the device? What are your processor clock frequencies and format?

    Is there anything that could have changed from your previous test, like device configuration, jumper settings, data source, difference in IOVDD voltage etc?

    One last question: Is your device working fine when using the onboard audio source?

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • 0 in reply to Ivan Salazar
    Prodigy 30 points

    hi Ivan,

    1. Is there anything that could have changed from your previous test, like device configuration, jumper settings, data source, the difference in IOVDD voltage etc?

    --->using external jumper settings and no changes 

    2. Could you share the configuration you're loading into the device? What are your processor clock frequencies and format?

    sh-3.2#  aplay /usr/share/sounds/alsa/Rear_Right.wav
    Playing WAVE '/usr/share/sounds/alsa/Rear_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono

    processor clock is 1.3 ghz .

    3.One last question: Is your device working fine when using the onboard audio source? 

    when we are using windows tool for configuring  feeding audio  as input  eval kit it is working fine

    Testing procedure following:

    1.using i2c commands for configuring the power-on status for that i am using only two regs

    i2cset -f -y 2 0x41 0x00 0x00 (PAGE SET)

    i2cset -f -y 2 0x41 0x02 0x0c (PWR_CTRL REG)

    Q.I am using only these two configurations for others are in reset state is there some more reg we need to configure?

    2. Now in working case PWR_CTRL REG is 0x0c means codec is in normal mode and then now i am feeding the i2s input from a laptop and it is playing audio

    Please find the reg dump in the attached file.

  • 0 in reply to thumu ramakrishna
    TI__Guru* 95175 points

    Hi Thumu,

    Is there a chance you can send an initialization script to the device via your processor?
    If you use the default values, the device is not initialized, and there are several things that should be configured, like input clock source, internal clock dividers for sample rate, gain settings and class-D driver configuration.

    You can use the same initialization that the EVM sends to the device, the I2C monitor within PPC3 can be used to capture I2C transactions.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • 0 in reply to Ivan Salazar
    TI__Guru* 95175 points

    Hi Thumu,

    Were you able to try the suggestion above?
    Is there an update on your application status?

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators