Issue with Polyspace Code Prover Autosar software component Analysis, How can I resolve it?

I am facing issue with Polyspace code prover analysis of Autosare components, It is not considering the given 'Rte_Type.h' as it contains variable declarations and tool is creating its own 'Rte_Type.h' in the folder 'AUTOSR' it does not have anything . So How can I give my own Rte_Type.h because I am including this header files in other header files, I do not want to use the Polyspace generated file.

Answer 1

[Anirban]

Please contact MathWorks Technical Support for a solution. The generated Rte_Type.h file should not be empty. If your generated file does not contain anything, you probably ran into a bug (or there is some other issue with the setup).

Having said that, you can provide the full path to your own Rte_Type.h using the option:

-include path\to\Rte_Type.h

to the polyspace-autosar command.

This workaround can normally cause other problems such as conflicts with declarations in the generated Rte_Type.h file. But, in your case, since the generated file seems to not contain anything (the variable declarations were not generated), this workaround might work. But really, the best thing would be to contact MathWorks Technical Support for additional help with the setup.