• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 754 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler: ARM v5.2.8 Code Analysis throws numerous symbol resolve errors after migrating from ARM 5.2.7.

Genatco
Guru 56033 points


Tool/software: TI C/C++ Compiler

Migrating and importing existing project CCS5.4 ARM compiler v5.2.7 into CCS7 and lowest version ARM compiler v5.2.8 the code analysis (CA) reports numerous symbol errors. 

Both CCS5.4/CCS7 CA configured at the project level and CA properties set for launching (run with build), throws hundreds of symbol resolve errors in the imported project to CCS7.

Building with ARM 5.2.8 in both CCS5.4/CCS7 with CA (run with build) disabled and importing project CC7 symbol errors go away. If we again enable CA run with build, the imported project CCS7 throws 100's of symbol errors shortly after importing project. 

The difference is building project in CCS5.4 with same version ARM (5.2.8) and CCS7 project CA set to (Run as you type) the symbol errors are gone after the import. Otherwise there seems to be something wrong in the CA in ARM 5.2.8 when set to run with build it still throws numerous and seemingly unfounded failed to resolve symbol errors.

I say unfound errors as the build appears to run without any bus faulting on the EK-TM4C1294NCPDT-XL launch pad. The latest ARM compiler V16.9.0 LTS seems to cause project symbol resolve errors either way CA is configured.

Is TI aware of these symbol resolve errors seemingly occurring after ARM compiler 5.2.7 build?  

  • 0
    TI__Guru**** 173310 points

    The rules defined in the Eclipse static analysis tool are somewhat different than what is defined by the TI tools, so the analysis tool could trigger errors where the TI tools do not. Due to this, code analysis is disabled by default in CCS projects, and that is the recommended setting.
    Please see this wiki section: http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Code_Analysis

    Also a general recommendation (which you already may be doing) is to always use a new workspace with each new version of CCS, as we have seen some odd errors to be triggered by the indexer and other features when using old workspaces in new versions of CCS.

  • 0 in reply to AartiG
    Guru 56033 points
    Hi Arti

    I am always using CCS workspace CA settings indicated in wiki but also include in the project build properties C/C++General/Code Analysis/launch/ (run on build) check box. Which works great for ARM 5.2.7 but seems to fail in ARM 5.2.8 with the import of the lower level compiler.

    The ARM 5.2.7 CA found several syntax errors not indicated as problems to fix for very long time when project CA workspace setting set with no (run at launch) checked. Workspace only CA seems mostly check syntax when typing only and missed an incorrectly placed return set on an IF statement been there over a year or so and made several suggestions for adding parentheses when (( )&&( )) exists between two sets of directives.

    Once the problems have been identified and or fixed then disable project level CA but leave launch run with build enabled. Even ARM 5.2.8 that way works ok and simply edit workspace CA individual problems that are design relative. The Wiki is not telling the entire truth about the functionality of CA!


    Did include a new workspace setting for CCS7.