Hi Nikhil, the reason for this error is most likely the size and the complexity of the application.
I would like you to analyze your code using the Polyspace Bug Finder. Using the Bug Finder is much faster and by finding and eliminating possible bugs in the code the probability, that a timeout occurs using the Code Prover decreases. One possible workaround is to use a less precise mode. You can change this in Configuration>Code Prover Verification > Precision, where you choose a smaller "Precision level" then the current one.
Another possibility would be to verify the files independently(-unit-by-unit): https://de.mathworks.com/help/codeprover/ref/verifyfilesindependentlyunitbyunit.html?searchHighlight=unit-by-unit&s_tid=doc_srchtitle
You can also split up the verification manually in multiple modules and then perform the analysis.
At last you can also re-launch the verification with the following options: 1. -no-inactivity-monitoring (in "Other" of the Advanced Settings) 2. precision/level0 (in Code Prover Verification-> Precision -> Precision Level) 3. -k-limiting http://www.mathworks.com/help/codeprover/ref/depthofverificationinsidestructuresklimiting.html
If none of the suggestions mentioned above resolve the issue I would like you to contact the Technical Support.
Have a great day,
Lucas
