TAS2563: Mode to use when running 'factorytest'

Steve Darmadi

Part Number: TAS2563

Tool/software:

Hello,

I am working with TAS2563 and currently trying to design the production test sequence. After reading the end system integration guide (slaa954), our thought was to use ROM mode for running calibration (factorytest program). This results in getting failures due to the measured parameters showing wrong values:

TAS2563 calibration values:
DevA Re = -0.00 Ohm
DevA F0 = 1893.05
DevA Q = -0.00
DevA rms_pow = 0x00000000
DevA t_limit = 0x2EE00000
SPK A Calibration fail : Re is too low (limit: 2.00).
SPK A Calibration fail : F0 is too high (limit: 450.00).

Factorytest however, works fine with tuning mode. So my question is:
1. Is it expected that factorytest doesn't work when the smartamp runs on ROM mode?
2. Which mode is recommended to use when running factorytest? Is it tuning mode? Do we need to create a special snapshot where all the tunings (EQ, DRC, etc.) are turned off except the characterization?
3. When is it beneficial to use ROM mode?

1 month ago

0 Ivan Salazar 1 month ago

TI__Guru** 109395 points

Hi Steve,

I'll go through your issue description and get back to you by tomorrow end of the day.

Best regards,
-Ivan Salazar
Applications Engineer

0 Ivan Salazar 1 month ago in reply to Ivan Salazar

TI__Guru** 109395 points

Hi Steve,

Calibration should be run in tuning mode. PPC3 exported configuration files show calibration configuration as TuningMode.

Yes, this is expected.
You're correct the tuning mode configuration for calibration process should not have any special EQ, DRC, etc. You can use the .cfg or .h exported from PPC3 -> End System Intergration as reference.
ROM may be used if speaker protection and other processing features are not required. It may also be used for debugging purposes as it represents the simplest way to configure the device.

Best regards,
-Ivan Salazar
Applications Engineer

0 Vasishta Kanthi 1 month ago in reply to Ivan Salazar

Prodigy 20 points

Hi Ivan Salazar

I am a colleague of Steve, working on the same issue.

While testing the factorytest program on our DUTs, we found some discrepancies on the output. There seems to be some persistent value output from the program, even after running it several times

As a test, we ran the program with the speaker disconnected. We expect the output to be zeros, but instead it is returning the same measured value, that seems to be obtained from the ftcfg file. This is also true when rebooting the device.

It would be great if you could explain to us the procedure to properly execute this program. An explaination on the following would be great:

Can the factorytest program be run several times when testing, or just once after boot flash?
From the following output:
- TAS2563 calibration values:
      DevA Re = 3.63 Ohm
      DevA F0 = 320.98
      DevA Q = 1.10
      DevA rms_pow       = 0x01584F33
      DevA t_limit       = 0x2EE00000
- Are these values the measured values directly from the loudspeaker driver?
The above mentioned values are the repeated values we keep getting, even when there is no speaker connected, nor any .bin and .txt file saved in the device. Is it somehow obtained from the ftcgf file?

In addition to the above, could you indicate to us, as to how one should run this program, and what is to be expected from the output.

As you responded to Steve, we have the device on tuning mode and running on the default configuration. My assumption was that the measured values would change everytime. Maybe we are missing something here, and if so, knowing it would be crucial for us.

Awaiting Response,

With Regards,

Vasishta Kanthi