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

TAS5707EVM GDE Driver Error - Win10

Markus Krautter
Intellectual 440 points
Other Parts Discussed in Thread: TAS5707, TAS5707A, TAS5731

Hello,

i'm using the TAS5707 Evaluation Module. Was working without any problems so far.

Since yesterday i get an error in the output window of the GDE (using TAS5707 GUI v2.0.1 Build 14 Rev. D). See the attached picture below for the exact entry in the output window.

I haven't changed anything on my system (Windows 10 - 64 bit). A reinstall of the GDE didn't fix the issue. Has that problem already come up with other matters ?

I suspect maybe the Windows Updates caused the driver problem.

Best regards,

Markus.

  • 0
    Intellectual 440 points
    Hello again,

    i just tested the Software on Windows XP (SP3, 32bit). The same error message occured.
    As a result i think it's an issue which belongs to the hardware.
    Is that a known problem ?

    Thanks,
    Markus.
  • 0 in reply to Markus Krautter
    TI__Mastermind 25845 points
    Hi Markus,

    I actually had this error working with a TAS5731 EVM a couple weeks ago, but I have not heard of this being a hardware problem. The error is usually caused by an incorrect I2C device address. Could you please verify your environment variable setting (refer to section 2.3 I2C Address Setup of the EVM users guide for details on this). The address should be "36" for TAS5707/09 and "3A" for TAS5707A/09A. I am wondering if it somehow got reset on your system.

    Regards,

    Alex
  • 0 in reply to Alex Bhandari-Young
    Intellectual 440 points

    Hi Alex,

    I checked the configuration of the I²C-Port and address. The address is set to "3A" as mentioned for the TAS5707A. When I installed the GDE software on an other computer i also did the setup correctly.

    Actually the configuration worked fine for a while. But one day, without (knowingly) changing anything, I became the described error.

    I testet it on 3 different computers (2x Win 10, 1x Win XP SP3) with the correct setup and always became the same error. Due to this fact i was thinking of a problem of the Eval-Board or the programmer.

    Regards,

    Markus.

  • 0 in reply to Markus Krautter
    TI__Mastermind 25845 points

    Hi Markus,

    That sounds like a possibility although I have not seen this issue before. Do you happen to have another EVM you could try with the software to verify this is a problem with the board? Are you able to use an oscilloscope to check the i2c lines on the EVM? I am interested in what the waveform looks like on the SCL and SDA pins of the device.

    Regards,

    Alex

  • 0 in reply to Alex Bhandari-Young
    Intellectual 440 points

    Hi Alex,

    i found the solution for my problem: I had a bypass in the 3.3 V Vdd, which caused a damage of the chip. So this driver error means, that no device was found for communication on the I²C-bus. A message like "No hardware found for communication" would have been a better solution for the Error-Report of the TAS570X GDE.

    I have another question: The datasheet of the TAS5707 says that the chip doesn't implicitly need a Master clock, because the PLL can generate the internal system clock from LRCLK and SCLK. Do i have to configure the mode for using no masterclock e.g. setting a value in a register via I²C or does the PLL automatically recognise whether there is a MCLK present or not ?

    Thanks for your help.

    Regards, Markus.

  • 0 in reply to Markus Krautter
    TI__Mastermind 25845 points
    Hi Markus,

    Glad you got to the bottom of it!

    Only the i2c is active with no MCLK for this device so you will need to provide an MCLK to play audio. The best you will be able to do is configure the timing such that SCLK=MCLK at 44.1 and 48 kHz. This allows you to tie the MCLK and SCLK lines together.

    Regards,

    Alex