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
This section provides the high level details related to what a system integrator must consider during the process of defining and building their F28003x based safety architecture.
The software support for the various safety mechanisms in the F28003x can be divided into the following categories:
A safe product built on the F28003x device hierarchically deploys each of the software solutions provided by TI. The first in the hierarchy is the HWBIST that has the ability to detect permanent faults inside the CPU by implementing the CPU Hardware Built-In Self-Test (HWBIST) safety mechanism. Drivers for using HWBIST are provided as part of the SDL. The second in the hierarchy is the rest of the tests in the SDL which provide a series of examples of safety mechanisms that are designed to detect permanent faults inside several key elements within the F28003x device. Lastly, the CLA_STL that implements the CLA2 - Software Test of CLA safety mechanism, can be deployed to detect permanent faults inside the CLA.
The CLA_STL makes use of, and depends on both the C28x CPU and the CLA to test the CLA. Therefore it is important to run the HWBIST first to make sure that the CPU is functioning properly and is capable of performing the required safety operations. The SDL supports safety mechanisms such as: CLK2 - Clock Integrity Check Using CPU Timer, CLK10 - Software Test of Watchdog (WD) Operation, CLK12 - Software Test of Missing Clock Detect Functionality, SRAM14 - Software Test of Parity Logic, SRAM13 - Software Test of ECC Logic, SRAM3 - Software Test of SRAM and several other key processing elements. The system integrator must study all the safety mechanisms supported by the SDL and determine their applicability into the safety system being designed. The safety system must be evaluated with respect to the start-up and runtime constraints and whether the software diagnostic tests can be run during POST, PEST or a combination of both.
The successful completion of the software diagnostics, selected by the system integrator, can be used as the qualifier to run the test vectors supported by the CLA_STL.