|
|||||||||||||||||||||||||||||||||
Technical Support On-Line Manuals µVision User's Guide About µVision User Interface Creating Applications Utilities Configuration Wizard Searching for Text Find Replace Find in Files Incremental Find Source Browser Run External Programs Using the SVCS Menu Key Sequence for Tool Parameters PC-lint and MISRA Validation Installation of PC-lint Configure PC-lint Using PC-lint Debugging Debug Commands Debug Functions Simulation Flash Programming Dialogs Example Programs Command Line Appendix |
Configure PC-lintThis section shows the configuration of PC-Lint for validation and MISRA checking. General setupOpen Tools – Set-up PC-lint and enter the path to the PC-lint executable. It is recommended to enable Add Compiler Conifg, as the relevant PC-lint configuration files are automatically selected. You may include other project information as shown below. For details refer to Setup PC-lint.
Setup for MISRA ValidationTo setup PC-Lint for MISRA validation, choose the relevant Rules configuration, for example MISRA_C_2012_Config. Then click on Setup to copy the rules configuration file to your project.
Click on Edit to configure the MISRA rules. This opens the configuration file where you may disable certain MISRA rules.
Additional PC-lint CommandsYou may enter Additional Lint Commands that are added to the PC-Lint configuration.
For example, to suppress the info 714 message from the PC-lint output, you may enter –e714 into this dialog.
For complex PC-lint setups, you may use additional PC-lint
configuration files, using the command
Additional InformationThe folder ..\UV4\Lint contains the PC-lint template setup files.
Compiler PC-lint Setup Files
MISRA Template Configuration Files
MISRA Setup Files
During configuration with the PC-Lint Options dialog, the related MISRA configuration is copied to the project folder into the sub-folder .\Lint. The MISRA configuration is therefore only relevant for a single project, however, you may copy existing configuration files to other projects. PC-Lint Command File StructureThe command files for PC-Lint are generated in the project folder and have the name target_A.lnt (for single file invocation) or target_G.lnt (for multi-file invocation). The PC-lint command file is generated based on the settings in the PC-lint Options dialog. An example is shown below:
Example content of single file target_A.lnt
// PC-Lint invocation file generated by uVision // -------------------------------------------- -i.\Lint // Lint specific command path: -iC:\Keil_v5\UV4\Lint // Compiler Include path: -iC:\Keil_v5\C51\Inc // ARM Compiler Lint configuration: ..\..\..\Keil_v5\UV4\Lint\co-kc51.lnt // Disable messages for Compiler header file directories: -wlib(4) -wlib(1) +libdir(C:\Keil_v5\C51\Inc) // Format Output to uVision: -hsfb^3 -format="*** LINT: %(%f(%l) %)%t %n: %m" -width(160,4) // Source file(s) for verification: Blinky.c | ||||||||||||||||||||||||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.