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.

RM48L952: Relation HALCoGen and SafeTI Diagnostic Library

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?

  • I'll be very interested in a reply to this great question since I have exactly the same question. Can a Guru or TI person please respond?

  • Hi,

    Sorry, this post went unanswered for so long.

    HALCoGen certainly generates the sequences for the diagnostic checks that meet the initialization requirements described in SPNA106. The Software Diagnostics Library provides a 1-to-1 mapping to the safety mechanisms and diagnostics described in the parts' safety manual. So an application designer can choose the necessary hardware and software safety mechanisms to be enabled in the application using the FMEDA and safety manual, and then enable the corresponding functions from the SDL to meet the requirements.

    For new developments, it is highly recommended to use the SDL for development.

    Regards,
    Sunil
  • Hi Sunil,


    Thanks for your response Sunil, I was hoping for a rationale why the SDL is recommended.
    Best regards,

    Karel
  • Hi,

    the Hercules safety diagnostic library (SDL) was developed to complement HALCoGen and to provide safety diagnostics functions which are inherent to the Hercules device. As such, the Hercules SDL is a more comprehensive diagnostic offering from TI and hence we recommend its use over similar APIs which have limited usage.

    Note that for the RM57x and TMS570LC43x devices, the Hercules SDL is the only available option from TI, HALCoGen doesn't offer these features.

    Thanks,

    Girish

  • Given what both the SafeTI Diagnostics Library CSP and the HALCoGen CSP provide I highly prefer using HALCoGen (and its CSP) over the SDL, at least for the RM48x.