Part Number: RM48L952
Other Parts Discussed in Thread: HALCOGEN
Hi,
I was interested in the related post, but I do not think the question is answered completely. The answer of Girish Gajwani which suggests to use the SafeTI Diagnostic Library does not contain an explanation why the SDL should be used over HALCoGen.
HALCoGen and the SafeTI Diagnostic Library are still both available and both have a Compliance Support Package available, which suggests that both options are fit for compliance.
It seems to me that using the safety_init tab of HALCoGen I can generate most of the self-tests that have to be performed at startup. This also nicely follows the "Standard Initialization Sequence for Hercules Microcontrollers" (SPNA106D). This covers steps 1-43 of SPNA106D. Steps 44-56 have to be added by the user, this can be done either with the SafeTI Diagnostic Library or HALCoGen functions depending on the application.
The code for initializing the core registers or running the PBIST for example is functionally identical between the 2 libraries, so functionally they do the same thing,
HALCoGen automatically generates the startup code and fills in the parameters depending on the safety_init tab which is nice.
Is there any advantage in changing the HALCoGen generated initialization code with the initialization functions of the SafeTI Diagnostic Library?