Settings from (C)

R2026b

(To be removed) Settings to use for the Polyspace analysis of C code

Model Configuration Pane: Polyspace

This option will be removed in a future release. In R2026b, it moved into the Advanced parameters section.

Description

The Settings from parameter determines Polyspace^® analysis settings for C code. You can choose to add C coding rules to your analysis using this parameter.

Dependencies

This setting overrides custom configuration settings in Project configuration and Use custom project file. If you want to use your custom coding rule settings, specify them in the Project configuration or in a custom project file.

Settings

Project configuration (default) |

Project configuration and MISRA AC AGC
                checking

Project configuration and MISRA C 2004
                checking

Project configuration and MISRA C 2012
                checking

| MISRA AC AGC checking | MISRA C 2004 checking | MISRA C 2012 checking

Project configuration

Run Polyspace with the options specified in Project configuration or Use custom project file.

Polyspace does not check for coding rule violations unless you select a rule set in the configuration.

Project configuration and MISRA AC AGC checking

(Errors) Run Polyspace with the options specified in Project configuration and check for violations of MISRA™ AC-AGC obligatory and recommended rules. This option is deprecated. If you select this option and run an analysis, you will get an error in the MATLAB^® Command Window.

Project configuration and MISRA C 2004 checking

(Errors) Run Polyspace with the options specified in Project configuration and check for violations of MISRA C 2004 rules. This option is deprecated. If you select this option and run an analysis, you will get an error in the MATLAB Command Window.

Project configuration and MISRA C 2012 checking

Run Polyspace with the options specified in Project configuration and check for violations of MISRA C 2012 rules. This option automatically applies the rule categories for generated code. See Use generated code requirements for MISRA standards (-misra-agc-mode).

MISRA AC AGC checking

(Errors) Check for violations of MISRA AC-AGC obligatory and recommended rules. This option is deprecated. If you select this option and run an analysis, you will get an error in the MATLAB Command Window.

MISRA C 2004 checking

(Errors) Check for violations of MISRA C 2004 rules. This option is deprecated. If you select this option and run an analysis, you will get an error in the MATLAB Command Window.

MISRA C 2012 checking

Check for violations of all MISRA C 2012 rules. This option automatically applies the rule categories for generated code. See Use generated code requirements for MISRA standards (-misra-agc-mode).

Recommended Settings

Application	Setting
Debugging	No Impact
Traceability	No Impact
Efficiency	No Impact
Safety precaution	No Impact

Programmatic Use

Parameter: VerificationSettings for use with pslinkoptions

Parameter: PSVerificationSettings for use with set_param()

Values:

'PrjConfig' | 'PrjConfigAndMisraAGC' | 'PrjConfigAndMisra' |
                    'PrjConfigAndMisraC2012' | 'MisraAGC' | 'Misra' |
                'MisraC2012'

Default: 'PrjConfig'

Example:

opt = pslinkoptions(modelname); opt.VerificationSettings =
                    'PrjConfigAndMisraC2012'

Version History

Introduced in R2016b

expand all

R2026b: Support for MISRA C:2004 and MISRA AC AGC standards is removed

Support for the MISRA C:2004 and MISRA AC AGC standards is removed. Running an analysis with any of these options will produce an error:

MISRA AC AGC checking
Project configuration and MISRA AC AGC checking
MISRA C 2004 checking
Project configuration and MISRA C 2004 checking

Use the newer MISRA C standards instead. When analyzing generated code, use a newer MISRA C standard with the option Use generated code requirements for MISRA standards (-misra-agc-mode) enabled in the Polyspace configuration.

R2026b: Settings from parameter will be removed

The Settings from parameter will be removed in a future release. In R2026b, this parameter moved into the Advanced parameters section of the Configuration Parameters dialog box.

Instead of using this option to configure your Polyspace Bug Finder™ analysis settings:

Specify the defect checkers and coding rules to enable in the Checkers Selection window by clicking Checkers Selection on the Polyspace tab of the Simulink^® toolstrip. Save these settings in the checkers activation (.xml) file. For more information, see Checkers activation file (-checkers-activation-file).
Specify additional and more advanced analysis options in the Polyspace Platform configuration. To open the Polyspace configuration, click Polyspace Settings on the Polyspace tab of the Simulink toolstrip.
For example, to use generated code requirements for MISRA C™:2012 and later standards, set Settings from to Project configuration. Then:
- On the Polyspace toolstrip tab, click Checkers Selection. In the Checkers Selection window, enable all rules for the MISRA C standard you want to use.
- On the Polyspace toolstrip tab, click Polyspace Settings. In the Polyspace configuration, navigate to the Static Analysis tab, select the Defects and Coding Standards node, and enable the option Use generated code requirements for MISRA standards (-misra-agc-mode).