• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1843 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.

CCS/CC2640: Release configuration does not build after project and referenced file name change

Dale Kramer
Expert 2615 points
Part Number: CC2640
Other Parts Discussed in Thread: CC2650

Tool/software: Code Composer Studio

I renamed my project name and a referenced file name over a month ago and have been happily building in debug configuration ever since.

Here is the refactoring (2nd change was from HaloLogger221Stack to Quyak221Stack):

Today, I tried for the first time since then, to build in the release configuration and have had no luck.

So far have tracked it down to the fact that it does not look like my renaming I did a month ago made it into the release configuration.

See this:

I have tried:

1. 'Edit Flags' but I cannot edit the incorrect HaloLogger221Stack directory to Quyak221Stack.

2. I can not figure out how to make a new clean release configuration (options to do so are disabled):

How can I fix this?

Thanks,

Dale.

  • 0
    Expert 2615 points

    I was able to edit the incorrect HaloLogger221Stack directory to Quyak221Stack with 'Advanced' options ON, in CSS Build>ARM Compiler>Advanced Options>Command Files.

    BUT, I still can't compile the Release Configuration due to reporting that 'program will not fit into available memory' even though I am using the same optimization parameters as the debug Configuration (I am probably starting a new post on this).

    SO, I still want to try a new 'clean' Release configuration.

    Can someone tell me why my ability to create a new default release configuration is disabled (I may even do a new post on this)?

    Even though I have marked this as resolved, I think TI should look into why my refactoring failed to update the Release configuration.


    Dale

  • 0 in reply to Dale Kramer
    TI__Guru**** 173310 points

    Dale Kramer said:
    Even though I have marked this as resolved, I think TI should look into why my refactoring failed to update the Release configuration.

    Was the --cmd_file option initially set to use a hard-coded path or a path variable like PROJECT_ROOT or PROJECT_LOC? If it was the latter, I would expect it to be automatically updated after the rename. But if it was the former, then it would not update automatically. 

  • 0 in reply to AartiG
    Expert 2615 points
    I believe I never changed the --cmd_file options since I started with the original ProjectZero, so I believe the above image shows the --cmd_file options, does it not?

    Not sure how they were hardcoded but the Debug configuration was hard coded too and they were updated on the refactoring in the Debug config..
  • 0 in reply to Dale Kramer
    TI__Guru**** 173310 points

    Dale,

    If I look at the ProjectZero example for CC2650, the --cmd_file option is set as below.


    As you can see the project name is explicitly specified in the path. The app project reads these option files that are within the dependent stack project.

    After renaming both the stack and app projects, the option remains the same (see below).  This option will not get updated automatically after a rename . I don't see how this could have worked with your Debug configuration either. As I see it, this path would need to be manually updated if you rename the dependent stack project. 

     

  • 0 in reply to AartiG
    Expert 2615 points

    Thank-you for that effort!

    It is definitely a possibility that I was smarter last month and was able to figure out how to get the Debug Configuration working again after the rename, and then i just forgot that I did it and how to do it.

    The joys of getting old!

    But if i were writing the refactoring code I thinkIi would have look through the whole build parameters for changes that needed to be made :)



    Thanks,
    Dale