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.

[FAQ] TAS2563: What are the .ftcfg, .cfg, .h, .json, and .bin files used for in End System Integration?

Part Number: TAS2563

How can I use .ftcfg, .cfg, .h, .json, and .bin files for End System Integration and what data are stored in these files?

  • These files are exported from the PPC3 under the "End System Integration" panel. The functions of each files are listed below:

    File with .ftcfg extension is called the Factory Test and Calibration (FTC) Configuration file. It contains the Pass/Fail limits defined by the users in the "Pass/Fail" page under the "End System Integration" Panel of the PPC3. These limits are used to calibrate each speaker and flag any speakers that do not meet the design requirement. The FTC process will output the result of the test in tas2563_cal.txt and create a calibrated binary file.

    File with .cfg, .h, and .json extensions all contain the same I2C commands for tuning configuration but in different formats. cfg files can only be used by "Direct I2C" in PPC3, while header(.h) and .json files can be executed by any compatible platforms. They are used for debugging and program the tuning data to the device.

    File with .bin extension is the binary file the driver needs to program the Smart Amp after the device is integrated in the end product. It contains all of the tuning configurations, characterization data, and device settings. 

    For more information about End System Integration, please refer to the TAS2563 End System Integration Guide, and TAS2555, TAS2557, and TAS2559 Factory Test and Calibration Guide