Code Prover Analysis of AUTOSAR Code
If you use the AUTOSAR methodology for software development, you can reuse the AUTOSAR specifications (ARXML files) to set up your Polyspace® analysis and verify code implementation of AUTOSAR Software Components. Alternatively, you can run an AUTOSAR-aware integration analysis.
The verification checks for AUTOSAR-specific issues and other run-time errors such as overflow and division-by-zero.
Polyspace Options
Libraries used
(-library) | Specify libraries that you use in your program (Since R2021a) |
Functions
polyspaceAutosar | Run Polyspace Code Prover on code implementation of AUTOSAR software components using MATLAB scripts |
DOS/UNIX Command
polyspace-autosar | (DOS/UNIX) Run Polyspace Code Prover on code implementation of AUTOSAR software components |
Polyspace Results
AUTOSAR runnable not
implemented | Function implementing AUTOSAR runnable is not found |
Invalid result of
AUTOSAR runnable implementation | Return value or output arguments violate AUTOSAR specifications |
Invalid use of
AUTOSAR runtime environment function | RTE function argument violates AUTOSAR specifications |
Non-compliance with
AUTOSAR specification | RTE API function is used with arguments that violate the AUTOSAR standard specification (Since R2021a) |
Topics
- Using Polyspace in AUTOSAR Software Development
Learn about the various workflows for using Polyspace in AUTOSAR software development.
- Benefits of Polyspace for AUTOSAR
Polyspace modularizes code based on AUTOSAR software components and checks for run-time errors or violation of ARXML data constraints.
- Run Polyspace on AUTOSAR Code
Check code implementation of AUTOSAR software components for run-time errors or violation of ARXML data constraints.
- Review Polyspace Results on AUTOSAR Code
Interpret Polyspace results that highlight violation of ARXML data constraints.
Troubleshooting
Troubleshoot Polyspace Analysis of AUTOSAR Code
Diagnose issues running Polyspace on code implementation of AUTOSAR software components.