Detailed method of using pc-lint in Keil MDK

keil MDK version: V4.03

PC-lint version: V8.0

There are many articles on the Internet about the powerful role of PC-Lint. I don't want to repeat them here. I will just say one thing: a program that can pass the PC-Lint test is not necessarily without problems, but the improvement in quality of a program that has passed the PC-Lint test is self-evident. 

First install Keil MDK and PC-lint. Most PC-lint on the Internet is installed in a compressed package, which can be directly unzipped to the C drive. Please support genuine products! ! (Ahem, guilty conscience...) 

The method is very simple, because keil MDK has already provided the configuration file of pc-lint corresponding to the keil ARM compiler: CO-KCARM.LNT. 

First open mdk, select Tools – Setup PC Lint, and the PC-lint configuration interface shown in Figure 1 will pop up.

                        Figure 1 PC-lint configuration interface

Click the area marked with red 1 in Figure 1 and select the lint tool; then click the area marked with red 2 in Figure 1 and locate the CO-KCARM.LNT file under the /ARM/bin file in the keil installation directory. This file is the PC-lint check configuration file for the corresponding keil ARM compiler. Finally, click 'OK' to exit and the settings are complete. 

Run PC-lint to check the source code in the project: Tools – Lint … is used to check the current C source file opened in the editor, and Tools – Lint All C Source Files is used to check all C source files in the project. The information obtained by PC-Lint will be relocated to the Build – Output window for display. Double-clicking the Lint information line will position the editor to the corresponding source code line.

My program originally had 0 errors and 1 warning () in the compiler. After checking with pc-lint, there were hundreds of errors, warnings, and other information. I was sweating...