SLAA954 August   2020  – MONTH  TAS2563

 

  1.   Abstract
  2.   Trademarks
  3. 1End System Integration
    1. 1.1 Step 1: Exporting Binary and Configuration Files
    2. 1.2 Step 2: Configuration Selection
    3. 1.3 Step 3: Snapshot Selection
  4. 2Factory Test and Calibration (FTC)
    1. 2.1 Step 4: Pass/Fail Limits
    2. 2.2 Step 5: Configuration Summary
  5. 3Device Driver Integration
    1. 3.1 Case 1 : Initialization
    2. 3.2 Case 2: Power up
    3. 3.3 Case 3: New Configuration
    4. 3.4 Case 4: New Configuration and PLL
    5. 3.5 Case 5: New Configuration and Program
  6. 4Summary

2.2 Step 5: Configuration Summary

This the summary page of the configuration. The binary, ftcfg, cfg, and header files should be available in the saved path. Select the highlighted text to open the file directory or “Finish” to exit the wizard.

GUID-20200721-CA0I-SVHW-ZP1V-S2TLLFHGP2QJ-low.pngFigure 2-3 Files Export Completion Page.

The folllowing figure shows the generated files from PPC3 end system integration dumping.

  • All of the tuning, configuration, and characteristic data are stored in the binary file with extension .bin (e.g. TAS2563_demo.bin). The binary file will be used by the driver to initialize the speaker.

  • The debug_cfg, json file, and headers folder contain the segmented tuning data in .cfg, .json, .h format, respectively, for necessary debugging purposes.

  • The factory test calibration file with extension .ftcfg contains the pass/fail limit for model calibration of each speaker during the factory test phase.

GUID-20200721-CA0I-14SV-TNKQ-F1LS7KFSTXWP-low.pngFigure 2-4 Generated Binary/Headers/CFG Files.

For more information on the End System Integration process, users can also reference to TAS2555 End-System Integration Guide or TAS2555, TAS2557, and TAS2559 Factory Test and Calibration Guide. This mark the final step of the implmentation flowchart described in the TAS2563 Quick Start Guide

Once this step is complete, users are ready to integrate the Smart Amp with the driver. Proceed to Section 3 for driver integration.