Keil Logo

PCLINT: µVISION ignores MISRA configuration file for PC-Lint


Information in this knowledgebase article applies to:

  • MDK-ARM version 5.23

SYMPTOM

µVision Version 5.23 introduced a new PC-Lint configuration dialog which offers a selection of different MISRA rules.

After selecting one of the MISRA rules and after pressing the Setup button, the corresponding configuration file MISRA_C_xxxx_Config.lnt is copied into the project folder. By pressing the button Edit, this configuration file is opened in µVision and can be modified in Configuration Wizard mode.

Unfortunately, the copied and possibly adapted MISRA_C_xxxx_Config.lnt configuration file is not used by PC-Lint and any changes in this file are ignored.

CAUSE

µVision correctly copies the file MISRA_C_xxxx_Config.lnt into the project folder, but because of a wrong PC-Lint command file search order, the default configuration file in path C:\Keil_v5\UV4\Lint\MISRA_C_xxxx_Config.lnt is used by mistake.

RESOLUTION

Extract the attached ZIP file into the folder C:\Keil_v5\UV4 to replace the UV4.exe file. If you have installed MDK-ARM into a different folder, you need to adapt the path accordingly.

STATUS

This problem was fixed in MDK version 5.24 and later. That version also includes a MISRA-C++ 2008 template for C++ projects, and a new warning level avoids conflicts of MISRA rules and CLANG diagnostic messages.

MORE INFORMATION

ATTACHED FILES

Request the files attached to this knowledgebase article.

FORUM THREADS

The following Discussion Forum threads may provide information related to this topic.

Last Reviewed: Wednesday, March 14, 2018


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

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.