Hi JesseBeeker,
I looked over this issue, but i do not think i related with our toolbox.
The files that are reported as not being able to be found can be added in the MATLAB path by:
- adding the generated folder (model_name_rtw) in the MATLAB path
- adding the ...NXP_MBDToolbox_S32K1xx\code\tools folder in the path
These files are GCC or SDK related include files that exists on the host PC (otherwise the build would fail)
After doing so, the edit command in MATLAB can successfully open any of the files reported as fail by the Static Code Metric Report.
I suspect an issue with the Simulink Code Metric itself - most likely it expect to find all the files in the root folder of the generated code. Also, i see that others are reporting similar issues on the Mathworks site: https://www.mathworks.com/matlabcentral/answers/263910-static-code-metrics-report-cannot-be-created-...
brianmckay,
Is MW aware of such limitations ?
Thank you!
Daniel