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.

TAS2563: QFN package Latched Error =0x0400D188, DAC MOD error questions.

Part Number: TAS2563

Hi all,

My customer is using the QFN package of the 2563. We are debugging a sound issue and we read the error flag register 0x24-0x27 to be 0x0400D188.

 what might have caused the DAC MOD error flag to come up?

We find that 0x04005188 error flag doesn't really affect the sound performance so we are primarily concerned with the 0x26=D1 value.

thank you!

  • Hello Andy,

    Thank you for reaching out. I am doing some additional research and will let you know as soon as I find an answer.

    Thank you,

    Elizabeth Weichel

  • Hello Andy,

    It looks like in register 0x24, that bit 2 is flagged which indicates a TDM clock error. This means that there is some internal clock error that will also cause the DAC MOD to have a clock error. There are three ways that a TDM clock error might happen: 1) Invalid SBCLK to FSYNC ratio 2) Invalid FSYNC frequency or 3) halting of SBCLK or FSYNC clocks. The table above shows correct SBCLK to FSYNC ratios for a chosen sample rate. Please let me know if this helps you in determining the cause of the TDM clock error. It would also be good to check the SAMP_RATE[1:0] bits to ensure that your sample rate is correctly chosen.

    Thank you,

    Elizabeth Weichel

  • Hi Elizabeth,

    Thank you for the response.

    Correct me if I'm wrong but you're saying that the DAC MOD clock error is strictly a derivative of the TDM clock error? Are there any possibilities your can think of for this error flag to be raised?

    The latched errors registers read 0x04005188 which means the TDM clock error also exist on units that are running normally. The samples rates and ratio are correct we are sure. We will be checking the SBCK and FSYNC halt possibilities. 

    Much appreciated!

  • Hello Andy,

    Another potential problem could occur if you try to stop the clocks when the audio stops. If the input data and clocks are stopped then the device will go into software shutdown. Once the clocks are enabled again the device can go back to active mode.

    The other note I would add is to make sure you're using the QFN version of PPC3 to generate the bin/header file. The WCSP version is incompatible here.

    Thank you,

    Elizabeth Weichel