Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 1320 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.

TAS5086 and I2C - Not getting the ack

DJH
Intellectual 985 points
Other Parts Discussed in Thread: TAS5086

We are addressing the TAS5086 with 0x36 and not getting the ACK from the device.  There are several other devices on the I2C bus and they do respond just fine.  We're running the bus at 400KHz.

Is there anything unique about the I2C communication and the TAS5086?

Thank you,

David

  • 0
    TI__Mastermind 33420 points

    Hi David:

    There is nothing unique with I2C bus on TAS5086.  (a) Can you slow down the I2C clock to ~100kHz and see if that works?  It should work at 400kHz ... just want to check and see if the signal is getting through @ lower rate.  Please try a simple read 0x00; it should return 6C. (b)  I assume that PDNz (pin 10) is de-asserted?

    Best regards,

    Tuan

  • 0 in reply to Tuan
    Intellectual 985 points

    Hello Tuan,

    Yes, we will turn down the clock to 100KHz and see if that helps.  Can you confirm for me that this power up sequence is correct?

    Reset low for 500 ms
    Reset high, wait 100 ms
    Powerdown high
    Mute low
    Backend Error high

    I will be trying the clock rate change here shortly.

    Thanks for your help Tuan.


    David

  • 0 in reply to DJH
    TI__Mastermind 33420 points

    Hello David:

    Please do the following for start up, just a bit different from what you have:

    PDNz - high (and keep this signal high for the entire operation - the device has issue when this signal is asserted)

    Reset low for 500mS

    Reset high, wait 100mS

    Mute low

    Backend Error high

    Best regards,

    Tuan

  • 0 in reply to Tuan
    TI__Guru**** 189399 points

    David,

    What voltage are your I2C lines pulled up to? What value pull-up resistors are you using?

    -d2

  • 0 in reply to Don Dapkus
    Intellectual 985 points

    Well, I think we will need to decrease our pullup values to make that pull a little bit harder.  The waveforms show a little rounding on the rising edge.  We slowed the clock rate to 100KHz and it seems to work fine.

    Thanks for the pointers everyone.

    David