• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 840 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.

CC2640: Renaming a BLE project fails.

Dale Kramer
Expert 2615 points
Part Number: CC2640

It was suggested that I repost this here as it may be related to referencing the BLE stack as a second project or there are more experts here ;)

I am unable to rename my project that started out as a SimpleLink Academy ProjectZero.

There is no preview available when I right-click rename it (ccs 7.0.0.00042):

So, I continue with an 'OK' and get a 'nil argument' exception:

And when I click OK, the workspace is completely screwed up and I get this:

I click OK, and nothing works until I delete all three projects from workspace (including from disk) and re-import the project from my zipped archive.

Any ideas on this rename issue?

Thanks,

Dale

  • 0
    TI__Guru** 105180 points
    Hi Dale,

    Please see this post from a few days ago: e2e.ti.com/.../2109000

    Best wishes
  • 0 in reply to JXS
    Expert 2615 points
    Hi JXS,

    Thanks, but to me Marie's answer of 'Please do not rename your project in CCS/IAR, but change the name in the .projectpec or .ewp or .project file.' was simply not enough. I had no idea what a .projectspec was (doesn't help that she misspelled it) and using those instructions would not even get the project folder renamed. Besides there is more to do if your project is a reference of another project.

    I was able to eventually rename enough things to make mine work and I could not even explain it all again.

    Someone need to write a book on how to rename all the folders, . files and references in them. To me I even had a question about whether I needed to rename in places where I ultimately decided not to because it was referencing what the actual source of the code was (I think).

    So, until I see that book, I will leave this unanswered ;)

    Dale