• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 953 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.

[TAS5713EVM] Wrong ACK from I2C communication

Han Hui Chan
Prodigy 70 points
Other Parts Discussed in Thread: TAS5713

Dear Ti developers,

I faced the I2C communication when I fly-wire I2C pins to the TAS5713EVM.

The default I2C device address for TAS5713EVM is set to 0x36, using the TAS5713 GDE tool to read out the device address, by read out from register address 0xF9.

When i send the wrong device address (for example, 0x32)  to the TAS5713EVM, the signal shown on the oscilloscope telling me that i received a 'LOW' from the SDA line, which indicates received ACK from TAS5713.

I believe the I2C clock communication speed is not the cause of it, as it is below 100kHz.

Please advice.

Thanks

Regards,

Chan

  • 0
    TI__Mastermind 22965 points

    Hi Chan,

    The start-up I2C address of the device is set by the status of Pin-14 (ASEL). A pull-up on this pin sets the address to 0x36, and a pull-down sets it to 0x34.

    After the start-up, the I2C address can be set to any value, by using the register 0xF8, as described in the data-sheet.

    Two questions:-

    1.) Was the I2C address updated using register 0xF8?

    2.) Is the Ack received for both 0x32 & 0x36? and are the register's readable using either of these I2C address?

    - Ravi

  • 0 in reply to Ravi Singh
    Prodigy 70 points

    Dear Ravi,

    Thanks for your reply.

    Below is my answer from your questions.

    1.) Was the I2C address updated using register 0xF8?

    >> No, I only use 0xF9 to read the I2C address using TAS5713 GDE I2C Memory Tools.

    2.) Is the Ack received for both 0x32 & 0x36? and are the register's readable using either of these I2C address?

    >> Yes, It was. And only 0x36 is readable, set to 0x37 for I2C address.

     

    I am still checking my microcontroller see if there is some problem with port.

    Will update the status once I found the problem.

     

    Thans for your support.

    Regards,

    Chan

     

     

  • 0 in reply to Han Hui Chan
    Prodigy 70 points

    Dear Ravi,

     

    After troublesome one round on Hardware side, I found out that the internal pull up resistors for SDA and SCL are the main cause. After change to external pull-up 4.7k, the ack can response correctly, (0x32, no ack; 0x36, ack)

    Thanks.

    Regards,

    Chan