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.

HALCOGEN: Handling DO178 certification with HALCOGEN

Part Number: HALCOGEN


Hi Team,

A customer of mine is trying to implement the DO178 certification in the TMS570 with the libC code generated from the Halcogen. But there seems to be no certification kit available to achieve this implementation. However the Safe TI Diagonostic Library shows a lot of evidence that can help them in achieveing the DO178. Hence the following questions:

Isn't the libC generated code developed following the same process as the Safe TI library?

How can such certification be handled with the libC?

Thanks.

  • Hi Obinna,

    HALCoGen CSP can be used to generate the required coverage reports for code generated using HALCoGen.

    You can request HALCoGen CSP from here: http://www.ti.com/tool/SAFETI-HALCOGEN-CSP

  • Hello,

    We are analysing the possibility to use the TMS570 for our DO254 DO178 DAL C product

    The problem decribe by  is more related to the library that you provide with the TMS570. “SafeTI Diagnostic Library” and “HALCogen” developed in order to meet the ISO26262 up to ASIL-D and  and not the DO178.

    The library show a lot of evidence that help use to meet the DO178 via the CSP package that you mention nevertheless it seem that the “HALCoGen” generated code call libC related Code that don’t seem to have any Certification Kit nor being developed following the same process that the SafeTI libray .

    The typical example is the file HL_sys_startup.c generated via HALCoGen the fct void _c_int00(void) calling   __TI_auto_init() that is belonging to libC provide with the compiler. 

    How do you handle this in the certification ISO or IEC?

  • Hello,

    HALCoGen as well as the SafeTI Diagnostic Library come with their own Compliance Support Package (CSP). These CSPs are very similar in nature and allow you to perform unit tests and generate the coverage reports you need as evidence.

    You are correct about the libraries supplied with the compiler not being created using a certified development flow. I will check if the compiler qualification kit CQKit) provides a mechanism to verify this auto_init() routine.

    Regards, Sunil

  • Hello,

    do you have any more information about this issue ?

    Regards

    Sigefroid van Haelst

  • Hi Sunil, 

    Have you got updates on the compiler qualification kit yet?

    Thanks in advance. 

    Obinna. 

  • Obinna,

    The TI ARM compiler QKIT currently only addresses the tool qualification and does not include RTS library code qualification.

    We do run extensive validations that exercise the RTS library code, however, we do not currently have any reports mapping those validation results to RTS library lines of code.

    Regards,
    Greg