SFFS277 November 2023 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1
The CLA_STL implements the CLA2 - Software Test of CLA. The CLA_STL’s start-up tests are also destructive in nature and should be run during start-up operations. The CLA_STL’s run time tests comprise the bulk of the tests designed to run in conjunction with the host application. The CLA host application must allocate the time and space for the run time tests. To achieve the required DC, the CPU must run both the CLA_STL POST and PEST tests.
The system integrator must consult the CLA_STL user guides and understand all aspects of integrating the library into the host application.
The process of determining what kind of tests are required to achieve the DC with the optimal distribution and quality of coverage is a fairly thorough and rigorous process. It requires running a fault injection campaign using the right combination of test vectors and confirming the coverage. It is precisely these test vectors that are packaged into the CLA_STL. It is important to note that the CLA-STL source code delivered with the CLA_STL can be validated using the MD5 checksum provided for each source file. The MD5 checksums for all the relevant files are available in the SDF file provided in the release package.
The system integrator must consult the CLA_STL user guides and understand all aspects of integrating the library into the host application.