I am attempting to perform static analysis of a project utilising C-STAT in IAR. As per: https://renesasrulz.com/synergy/b/weblog/posts/improving-software-quality-using-the-c-stat-static-code-analysis-tool
However I get the following error when analysing files:
Each file analysis fails with the following;
"synergy\ssp\src\framework\el\tx\tx_src\tx_thread.h",649 Fatal error[Pe035]:
#error "Secure builder required to compile this file"
Will C-STAT not work when ThreadX source has been selected in the SSP configuration?
Has anyone successfully used C-STAT with their Synergy project?
Any assistance is appreciated.
That looks like it can't decrypt the protected file. Assuming you have the IAR license set uo for Synergy set up, CSTAT may not be part of the free compiler deal. Even if you pay for IAR, CSTAT costs extra.
Hi, from my understanding (and I could be wrong) CSTAT is included as part of the Synergy package with IAR.
All the licensing is set and I can compile and view protected source just fine, it just seems the C-STAT feature doesn't have access to the protected source.
I will continue to prod and poke around with it, I have a suspicion it can't be used when compiling the ThreadX source, so I might remove all the source modules from the SSP configurator and try again.
Thanks for your reply. :)
I have been able to successfully run C-STAT on most of my source files.
It was required that I remove all source modules from the SSP configuration.
I still have an issue running C-STAT on files which include headers from network applications (such as mqtt, http, etc..).
Yes, I believe there is an option to not run C-STAT on specific files or folders. Have you tried that option?
Yes I am able to run C-STAT on specific files rather than the whole lot.
However I would still like to use it on my source files that are including some ThreadX and NetX headers.
I'm still working on a solution, however in the meantime I am at least able to run C-STAT on the majority of my source files.
FYI, I also found this forum thread which is a similar issue;
Thanx for cross posting this thread. It shows the following fix for a Trace-X related issue.
I was able to confirm that disabling TX_ENABLE_EVENT_TRACE avoided the need to include encrypted headers.