• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 966 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.

TAS5756 I2C Issue

Jerry Chu
Genius 4915 points

Hi Expert,

Two questions for TAS5756. Thanks!

1. I log the initial code from PPC2, you can check "PPC2 Log Data.TXT". And also use the LA to log I2C bus command, you can check "LA Log Data.TXT. You can see many difference between the two I2C command. Which file is right? Or both are fine?

2. Customer MCU download the command to TAS5756 will fail, but use the AIC3254 CS tool, it always good. Does TAS5756 I2C need to follow any timing Spec?

PPC2 Log Data.TXT

PPC2 Log Data.TXT

LA Log Data.TXT

LA Log Data.TXT

TI AIC3254 GUI (the deltaT is 5.66mS)

Customer MCU (the deltaT is 648uS and 992uS)

  • 0
    TI__Mastermind 20085 points
    Hi Jerry,

    My colleague will be responding the next week with further information.

    Best Regards
    Jose Luis Figueroa
    Audio Applications Engineer
  • 0 in reply to José Luis
    TI__Guru 57800 points

    Hi, Jerry,

    I reviewed the log files you provided. It seems the address of the device is different, from the GUI perspective, the address of the slave device is 0x9C, while it is 0x98 in the LA log. Do you changed the target address for the device in PPC1?. Another thing to mention is that the LA data is capturing the MSB of some of the registers as '1'. This means that the data is being written using the Auto-increment mode. The timing parameters should match the specs from the I²C bus timing tables from the datasheet.

    Best Regards,

      -Diego Meléndez López
       Audio Applications Engineer

  • 0 in reply to Diego Melendez
    Genius 4915 points

    Hi Diego,

    Thanks for your review, 0x9C is customer's PCB, 0x98 is TI EVM. Local FAE already yo explain the register difference.

    Only one question is the I2C timing issue. Do you have it? Thanks!

  • 0 in reply to Jerry Chu
    TI__Guru 57800 points

    Hi, Jerry,

    Thanks for the feedback. Could you please gather more information about the I²C timing of customer's MCU?. from the waveforms you attached, it is no clear if I²C timing specs are compliant with the specs stated in the datasheet. If the timing is correct, then I would recommend to check if the communication with the slave device is correct by writing only basic commands like volume or mute. 

    Best Regards,

      -Diego Meléndez López
       Audio Applications Engineer