Ignore MISRA checks for driverlib files

Hi Nigel,

Nigel Paine said:

Is there a way to filter out any warnings

Have you tried a working set that only includes the files you're interested in?

Or perhaps this works for you:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/942409/ccs-msp430f5419a-exclude-misra-checking-for-msp430-driverlib-files

Kier said:

Or perhaps this works for you:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/942409/ccs-msp430f5419a-exclude-misra-checking-for-msp430-driverlib-files

I would suggest the method here - using file/folder specific options to choose the files that have MISRA checking enabled (or disabled).

Unfortunately this doesn't completely work to only set MISRA rules for a specific folder. For example, if there are any static inline functions in the driverlib that are used or included in my source files, MISRA flags these files in addition to my source files, even though I've only set the MISRA checks for a specific file/folder in my source files excluding the driverlib.

Nigel Paine said:

For example, if there are any static inline functions in the driverlib that are used or included in my source files, MISRA flags these files in addition to my source files, even though I've only set the MISRA checks for a specific file/folder in my source files excluding the driverlib.

You raise a valid issue. the inlined functions whould be considered part of your source and hence the MISRA checking would be applied to them.

I think we will need to go back to your first thought of filtering out the warnings in the view. let me mull on this and see what i can think of...

Ki said:

let me mull on this and see what i can think of...

Doesn't the working set idea at the top of this issue fulfill this objective?

I've used working sets in the past to group projects together. I never did it to group files inside a single project. But the idea sounded promising. However I was not able to successfully filter the contents of the Problems view via working set. It could be that I am doing something wrong...

Using working sets will likely not work because the again the inlined function would be considered part of the source files where MISRA checking is enabled.

Yes, I see the difficulty. Most likely even the pro tools may not be able to separate inlined driverlib code from user code. Perhaps a #pragma around each driverlib call that temporarily suspends analysis is the way forward.