Due to the U.S. Thanksgiving holiday, please expect delayed responses during the week of 11/22.

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.

SafeTI Diag Lib vs het1ParityCheck()

Other Parts Discussed in Thread: HALCOGEN, TMS570LC4357


In reference to SafeTI Diagnostic Library and code generated by HalCoGen, in safety applications should we use het1ParityCheck() or SL_SelfTest_HET(HET_SRAM_PARITY_TEST,SL_HET1,0U,0U); ?
In the example of usage SafeTI diagnostic library in boot time (sys_startup.c) het1ParityCheck() is being called but in main() SL_SelfTest_HET() is being used. 
The question also applies to other peripheries where the situation is the same.

  • Hello,

    The SDL can be used independent of the driver code generated by HALCoGen. The demo application that is included along with the SDL installation demonstrates the use of the API functions included in the SDL.

    For most devices (all except TMS570LC4357 and RM57), the start-up code and routines for safety diagnostic checks are also generated by HALCoGen. In this case you can choose to use either the HCG routines or those from the SDL. They should be very similar if not completely identical.

    Hope this helps.