TMS320F28379D: Supported Static code analysis tools

AK,

The link you are looking at is a very old press release where LDRA is announcing that they now support integrating with Code Composer Studio. The CCS version at that time was v6 but that does not mean that it is the last version they support. LDRA can provide more information on what versions they support but I would expect that the v12 that you are using is supported.

There are other solutions as well such as:

ParaSoft C/C++ test https://www.parasoft.com/solutions/static-code-analysis/

vectorCAST https://www.vector.com/us/en/products/products-a-z/software/vectorcast/

Klocwork https://www.perforce.com/p/kw/try-klocwork-static-code-analyzer

There are cheaper solutions as well such as PC Lint

https://pclintplus.com/wp-content/uploads/2023/04/getting-started-pclp-generic-ccs-eval.pdf

Regards,

John

Thanks , What tools does TI generally use? Maybe we can follow something similar if its tested with the CCS v12 and on C2000 MCUs.

AK,

I will loop in the C2000 team.

Regards,

John

Hi AK--Most of our software teams, including those doing C2000 software development, are using Klocwork.

Whitney

Hello Whitney,

Thanks for the information , I am just looking at the Perforce web page they have 2 STA tools , Klocwork and Helix QAC

Is only Klocwork used? How do you comply with MISRA standards?

Also do you generally use it as a standalone tool or is it integrated with code composer? I am trying to understand the interface for performing the code complience checks , report generation that kind of thing so that we could replicate a similar work flow in our project.

Yes, we're using Klocwork for MISRA, and then supplementing the Klocwork analysis with code inspection to cover the rules that the tool isn't capable of checking.

I think most folks do use it standalone, although I have used an Eclipse plugin for it in CCS the past. I think there is also Visual Studio/VS Code plugins although I haven't tried those.

Whitney

Do you have a mock/dummy report for checking MISRA complience.?

For example , considering the  C2000ware motor control SDK , could you share the MISRA complience report . It would help get some ideas and standard practices.

I'm not aware of any public versions of reports that I could link to, but our MISRA report template is basically

• Klocwork build configuration information (build name, creation date, enabled checkers, KW version used, etc...)
• Issue summary showing how many issues of each severity and status there are
• List of all issues found in the code (columns for rule code, location, severity, status, comment, etc...)
• List of all the rules we've enabled in the checkers (MISRA C 2012, C and C++, HIS metrics, etc...)
• List of deviation permits (records of the use cases where it is acceptable to set the issue status to "Ignore" or "Not a Problem")

We use Jira to track deviation records, so for example, if in a project we want to say that you're allowed to cast an integer to a pointer when you're doing so to access a memory mapped register, we'd file a deviation for R.11.4 describing that use case. Then in Klocwork whenever an issue is reported for that use case, we can set its status to Ignore and in the comment field provide a Jira ID of the deviation record that explains the justification.

Hopefully that gives you some ideas?

Whitney