• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 510 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TAS5760M: TAS5760 Amplifier internal clock error active for 3 hours

TAS5760MD: Clock error after updating PCB

Toon L
Prodigy 10 points
Part Number: TAS5760MD


I created a PCB with the TAS5760MD audio amplifier and this worked perfectly but when I created a second version with some added features unrelated to the amplifier and copied the previous schematic, this new version constantly gives a clock error, given by the fault register. I checked the different clock signals with an oscilloscope and compared these with the previous working version but they look the same. Even using the same software and microcontroller and making multiple PCBs to make sure there is no soldering error, I still get the same problem. The PCB traces are only a couple centimeters long and I tried adding capacitors but without success. Is there any special reason why this error could show up? 

  • 0
    TI__Guru 51860 points

    Hi Toon

        Could you please share your schematic of your new PCB? We would check it first.  

  • 0 in reply to Shadow He
    Prodigy 10 points

    This is the schematic used for the amplifier, it is just the schematic for software control given in the datasheet of the chip. The audio amplifier is controlled by an ESP32, which sends dual channel 16 bit audio at 44.1 kHz. The schematic stayed the same as for the version that works, only the PCB layout changed a bit by adding more components for other unrelated functionalities.

  • 0 in reply to Toon L
    TI__Guru 51860 points

    Hi Toon

       Can you use flying wire to send the MCLK/SCLK/SDIN directly from your old board to the new board, and cut out the trace on the new board. Let's quickly check if the problem is from I2S or not.