This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error checking in CCS5

Is there a way to make error checking less strict in CCS5?

  • Hi Robert,
    For which feature are you talking about? The build tools (compiler/linker)? The static code analysis tool (Codan)?

    Thanks
    ki
  • The build tools. After converting a project from CCS3.1 to CCS5 the project has a lot of new errors when I try to build it. I also noticed that it is including more files in the build.
  • There are some compiler options to suppress warnings (-pdw) or suppress a specific diagnostic (-pds). However I have a feeling that your new error messages you see from moving to v5 is because of the new project format in v5 vs v3, which is leading to additional files being built that you did not originally intend to. In v5, any file that is inside the project folder is considered part of the build. This is different from CCSv3. See slides 26&27 of: software-dl.ti.com/ccs/esd/training/CCSv5-FromCCSv3.pdf

    Thanks
    ki
  • Thanks. Many errors went away after I removed unused files from the build. However, I still have many warnings of the type: "#225-D function declared implicity" after converting from CCS3.1 to 5. Is there a way to surpress these warnings?
  • In the Diagnostics Options of the project properties, there are all sorts of options to elevate/deprecate/suppress various compiler errors/warnings/remarks.

    You would need to know the ID of the message (in your example, it is 225). A full list is here.


    Thanks

    ki