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.

TMS570LC4357: SafeTI and MIRSA-2004 standards (not able to use strict ANSI)

Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN,

When compiling the SafeTI libraries from the website, I have to set the "Language Mode" to use "Relaxed parsing (non-strict ANSI) (--relaxed_ansi, -pr)" in order for it to compile without errors. 

This is true of the examples that come with the library as well for "non-OS" versions. 

It appears that it has to do with the assembly files including c file headers. 

Since we are trying to be MIRSA-2004 compliant in our code, do you have a SafeTI code update where Strict ANSI mode can be used? 

  • Hello,

    For Safety Diagnostic Library, we use LDRA tool for all our Static Analysis ( MISRA Metric is also used). Hercules Software Team follows a MISRA policy document across all our Safety Software products. Both HALCoGen and Safety Diagnostics Library come with Compliance Support Package( CSP). CSP is charged, since it packs the LDRA tool for running the tests. But there is a Demo verison which you can download.

    We don't have plan to update the Safety Diagnostic Library and AHLCoGen. 

  • Hello QJ, 

    Thank you for your fast response. 

    Since you mention this MISRA policy is followed, can you provide some guidance on how to remove a few of the larger MIRSA errors that occur in this example when compiling using Code Composer Studio and the required MISRA-2004 option? We unfortunately don't have the ability to even use the Demo version of CSP. 

    'I'm currently compiling: Hercules\SafeTI Diagnostic Library\2.4.0\demo_app\HALCoGen\TMS570LC4357_NoOS (attached in 2.4 version zip). 

    We're using  Version: 7.3.0.00019 of Code composer, and simply went to "advanced options", "MISRA-C:2004" and clicked "required."8688.zip




  • Hello,

    The SafeTI Diagnostic library code was evaluated against MISRA-C rules using LDRA tool. There are 2 aspects to consider:

    1) Different tools could lead to different findings

    2) There are some documented exceptions in the code (you can identify them with the label SAFETYMCUSW)