• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1307 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320F28379D: CCS 9 - Changing the connection in the Project Properties->General tab causes errors

Ed Sanders
Genius 3860 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

I am upgrading my project from CCS 8.0.0 to CCS 9.1.0.  I imported the project and was able to build successfully.  However, when I tried to change the debugger, it gives me a Warning dialog box which states, "Problems encountered while initializing build-configuration 'Debug' of project 'blah'.  Please see the 'project.lgo' file, in the root of the project for details."  Looking at the log file, I see many lines such as the following:

!WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C2000_18.1.compilerID.LARGE_MEMORY_MODEL

Any idea why this is happening?  Should I be importing these things separately, or entering them by hand?

Thank you,

Ed

  • 0
    Genius 3860 points

    Another symptom/clue.  After doing this, I can no longer build the main project because all of the Include Options were deleted and replaced with:

    ${INHERITED_INCLUDE_PATH}

    This is empty.

    Ed

  • 0
    TI__Guru**** 173310 points

    Ed Sanders said:
    However, when I tried to change the debugger, it gives me a Warning dialog box which states, "Problems encountered while initializing build-configuration 'Debug' of project 'blah'.

    When you imported your project into CCS 9.1.0, did the Compiler version field look something like this, with a message about "Compiler version xxx is not currently installed. A compatible version zzz will be used during build"?

    And then you tried changing the Connection field, is that correct?

    If so, I am able to reproduce the error. This appears to a bug that is triggered somehow when the original project is set for an older version of the compiler. And I also observed that the Include Options are deleted after the error. I will file a bug report for this.

    If the Compiler version is explicitly set to use the newer version prior to changing the Connection, then the error does not occur. In my example, I click on the Compiler version drop-down and select 18.1.4.LTS before changing the Connection, then there is no error. You would need to delete your current (broken) project from the workspace, import it again and then try the workaround. Let us know if that helps. 

  • 0 in reply to AartiG
    Genius 3860 points

    Yes!  That is what I am seeing, but with different versions.  If it helps, I saw:


    TI V18.1.1.LTS [TI V18.12.2.LTS]

    I manually selected "TI V18.12.3.LTS", change the connection, built the code, and was able to use the debugger normally.  So the workaround works!!

    Thanks for your help,

    Ed

  • 0 in reply to Ed Sanders
    TI__Guru**** 173310 points

    Ed,

    FYI, the tracking ID for this bug is CCSIDE-3670. Feel free to track its status using the SDOWP link in my signature.

  • 0 in reply to AartiG
    Intellectual 680 points

    Hi,

    I am also facing the same bug. 1 more bug I have found that on the same window, when I am trying to change the xxxxx.cmd file, I am not able to change the xxxxxx.cmd file. Please check this also. First I was using this .cmd file from ccs directory. Now I am trying to use it from project directory. I am also inporting project from ccs 5.6 to ccs 9. 

  • 0 in reply to AKhilesh Gangwar
    TI__Guru**** 173310 points

    AKhilesh Gangwar said:
    1 more bug I have found that on the same window, when I am trying to change the xxxxx.cmd file, I am not able to change the xxxxxx.cmd file.

    Yes, changing other fields in the General Properties also seems to trigger the bug. I will add that information to the bug report. 

    In the meantime, please use the workaround suggested in an earlier post - (ie) Change the Compiler version field to explicitly set it to use the newer version of compiler prior to changing any other field.