Static code metrics report not created for ezdspF28335 project

I am working with the ezdspF28335 development board and embedded coder with version R2013a. The project uses Code Composer 5.5 with the 'generate makefile' configuration. When I build the model the code is generated and built with the target tools. It downloads using CCS and runs fine on the target board. If I ask for a code generation report to be produced this also works fine apart from the static code metrics part of the report. Here I see the following error messages and the report cannot be viewed. If there was a genuine code error then presumably the code would not build at all. I do not see any messages at all from the code build action so either they are not being displayed or there aren't any messages to display (I suspect the latter).

If the code compiles and runs without error then why does the code metrics report seem to think there are errors? Is there a fix or workaround for this problem that would allow the code metrics report to be produced?

Thanks.

Static Code Metrics Report

Error Report

Static code metrics report was not successfully generated because of the following errors.

File Line Description C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_Device.h 36 expected a ";" C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_Device.h 37 expected a ";" C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 28 expected a ";" C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 37 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 38 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 39 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 40 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 41 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 42 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 43 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 44 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 45 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 46 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 47 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 48 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 49 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 52 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 53 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 54 identifier "PINT" is undefined C:\Program Files\MATLAB\R2013a\toolbox\idelink\extensions\ticcs\inc\DSP2833x_PieVect.h 55 identifier "PINT" is undefined

Answer 1

[Anusha B]

Hi Mike,

The static code metrics tool accepts many dialects of C/C++ (gnu, msvc, upc). However, the TI keywords are not recognized by it. Hence the error occurs.

Hope this helps.

[Jiaqaun Hu]

How to solve it? can you tell me?

[Sam]

It would be very nice if MATLAB could fix this issue. I encounter the same error message for the TI C2000, 28379D. C:\ti\controlSUITE\device_support\F2837xD\v190\F2837xD_headers\include\F2837xD_pievect.h

[seynaser]

Hi

me too...

did you find any solution?

thank you

[Gaurav Ahuja]

try this

https://in.mathworks.com/matlabcentral/answers/478247-static-code-metrics-report-was-not-successfully-generated-because-of-the-following-errors

https://in.mathworks.com/help/ecoder/ug/analyze-static-code-metrics-of-the-generated-code.html

Static Code Metrics Report Limitations

• Static code metrics are not available if the target configuration for a model results in generated code that:
• Includes a header file that is not generated by the model hierarchy and is not a system header file
• Uses a macro that is not recognized
• On a Windows machine, static code metrics can be generated for a model only if it is configured with MinGW compiler. For information about changing default compiler, see To Change Default on Windows Systems.