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.

CPU self test Demo

Other Parts Discussed in Thread: HALCOGEN, TMS570LS3137

Hello, I am using your official development board, TMS570LS3173 series. Use HALCOGen to generate the diagnostic library. I don't know how to use this. Can I refer to it for routine reference or engineering? Thank you.

  • Hi Xiaohong,

    To use the Safety Diagnostic Library (SDL), please refer to the example for TMS570LS3137 device in the SDL installation folder:

  • Thanks your reply.

    1. I used the CCS software to open the project according to the path you provided, but the following problems occurred during compilation, suggesting that the path could not be found during compilation. I tried several methods: (1) Add header files, add the header files of the compilation environment, library header files, etc., and the compilation still reports an error; (2) Creating a new folder and copying the project to a different path for compilation is still the same problem.

    2. There is another problem. I looked at the interface of the diagnostic library provided in this demo program, but did not find the interface function related to CPU diagnosis. There is a SL_SelfTest_STC(...). This should be a test of the internal logic of the STC. but for the CPU. What is the diagnostic calling interface? thank you very much.

  • Hi Xiaohong,

    1. There is no problem in my test. Why are the following files are built for your project? 

        How do you import the project to CCS? Did you change the project property and compile/link options?

    2. SL_SelfTest_STC(...) is used for STC self-check and for CPU self-test. If the argument testType=STC_COMPARE_SELFCHECK, it is to perform STC self-check. If the argument testType=STC_RUN, it is to perform CPU self-check.

  • Thanks your reply. I re-imported the project and it can be compiled. It may be that the previous method of importing is wrong.