TAS2563: Regarding the issue of audio not being output from the TAS2563 on the mounting board

Hi Fumiya,

1. ROM mode is the simplest configuration option, this can be used for playback tests where speaker protection, EQ and the rest of the digital processing features are not required.
   Tuning mode enables all the digital processing features.
   The device operates in ROM mode by default, the transition from ROM to Tuning mode is unfortunately not a simple bit toggle, it implicates many different registers.
   In order to understand what the issue with a playback test might be, you can read the latched interrupts located in registers 0x24 to 0x27.
2. That is correct, the device is set to Software Shutdown after every power cycle, this is so that the proper register configuration is completed before playing audio.

There are DSBGA and QFN package versions of TAS2563, can you confirm which one are you using? Perhaps you used the incorrect software to generate the DSP program. You must use the matching version of hardware and software.

During your test, make sure to enable the clocks going from your host processor to the TAS2563 before setting register 0x02. If the device is set to Active mode on register 0x02 while the input clocks are not present, it will change to SW shutdown automatically due to clock error.

For general understanding, I'd like to know which files from the end system integration tool are you using? Are these .h or .bin files? And what driver are you using on your host processor? Is it something from TI or developed on your side?

Best regards,
-Ivan Salazar
Applications Engineer

Hi, Ivan.
Thanks for your answer.
I will respond to each one.

1. I understand. So for playback related errors it is better to read the interrupt register.

2. I understand. After all the settings are complete, I need to update Addr0x02 and set Operational Mode to Active before playing audio.

3. The package mounted on the product board is a QFN package. The EVM is a BGA package, right? Does this mean that the firmware content may differ depending on the package? If so, I was not aware of this.

4. I understood. I'll check the clock error later.

5. The files used are .h files, and the drivers were created in-house. There was no equivalent to PLL Data in the .h files.

That's all for the answer.
Here, I will share the output file for discussion purposes.
Please confirm.

Regards,
Fumiya.

20250408.zip

Hi Fumiya,

For Q3, if the device on your board is QFN, you must use the TAS2563QFN EVM PPC3 application, if you don't have access to that one you can request it here: https://www.ti.com/drr/opn/TAS2563QFN-SW 
The EVM for this package is TAS2X63EVM Evaluation board | TI.com

The device usually works in auto-detect clock settings, so any PLL related settings are either not applied or handled by the device after SBCLK and FSYNC are enabled.

Best regards,
-Ivan Salazar
Applications Engineer

Hi, Ivan.

When incorporating and using the TAS2563RPP, does this mean that it is necessary to use the TAS2563QFN application and the TAS2563QFN EVM?
The descriptions of each evaluation board seem to distinguish between mono and stereo devices rather than differences in the packaging.
Is there any way to correctly write to the QFN on the board using a YBG evaluation board?
Also, in the first place, is the difference between EVM and the app related to the current AUDIO issue?

Ultimately, all that matters is that the sound comes out correctly from the TAS2563RPP on the board.

I look forward to your reply.

Regards,

Fumiya.

Hi Fumiya,

All the compatibility issues are related to Tuning mode. ROM mode should work the same across both variants.

Specifically talking about Tuning mode:

• You must use the QFN version of PPC3 to generate the bin file for the QFN device on the final board.
• You cannot use QFN version of PPC3 with WCSP version of EVM, and vice versa.

If you generated the bin file from PPC3 using the DSBGA version of PPC3, and you selected Tuning mode when generating these files, then it would not work for QFN on the final board.

In order to simplify things, you may try generating the files in PPC3 using ROM mode instead.

Also, I mentioned you can read the interrupt registers, have you tried that?

Best regards,
-Ivan Salazar
Applications Engineer

Hi, Ivan.

I tried two things.

I tried reading 0x24~0x29 "Latched Interrupt Readback".
The value of 0x24 was 0x04, the value of 0x27 was 0x80, and the value of 0x29 was 0x80.
The three events that may occur are TDM clock error, Device power down flag hold, and Clock halt flag.

I installed the app for the QFN package and output a binary file in its default state without changing the sound quality or speaker characteristic information.
When I wrote that file to the TAS2563 on the board, sound started coming out normally.

I have a question. Is it possible to use the app for the QFN package to adjust the sound quality of the YBGEVM, determine protection characteristics, evaluate speaker characteristics, etc.? Or, after performing these tasks using the app for the YBGEVM, can that information be transferred to the app for the QFN?

I look forward to your reply.

Regards,

Fumiya.