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/CC2650: Copying BLE-Stack Project to make changes without affecting original project files

Part Number: CC2650
Other Parts Discussed in Thread: BLE-STACK, ,

Tool/software: Code Composer Studio

Hi,

I am using the sensortag_cc2650stk app+stack example from the BLE-STACK folder and I made a copy of the root folder ble_sdk_2_02_01_18 which I renamend to ble_sdk_02_01_18_copy.

I created a new workspace and I did all the changes that I wanted and I was able to build and flash the code to the cc2650 sensortag.

Now I wanted to do other changes to that programm but to have a backup, I wanted to duplicate this project and do the changes their without affecting the previosu verison.

I followed the following instructions which says to copy the root folder and create new workspace and but I was not able to build the project because of gmake errors : http://processors.wiki.ti.com/index.php/Creating_copy_of_example_project

Now I went back to the previous version ble_sdk_02_01_18_copy and I tried to f´build it and even this is not running anymore. I did not change anything on that and now I am not able to run it anmore.

These are the following errors that I get in Code Composer Studio:

Is it possible to make it run again and how I can create a duplicate of this project otdo more changes withaout changing this project?

  • Hello,

    Based on the error messages, it looks like the project is dependent on some variables (linked resource variables and also build variables) which need to get adjusted. Can you provide the projects in your workspace? Just zip up the whole project folder and attach it to this thread.

    Thanks

    ki

  • Hi Ki,
    thank you for your response. But I did not change anything on the previous project, I only made up a copy and created a new Workspace. So I did not touch the other workspace, how this can happen? Actually it is not possible to upload the project, it is cofidental. Is there a way to solve it and how I can duplicate projects in future without having these problems in future? CCSv8 seems to be not user friendly like v7 for project duplication. In v7 I could copy and paste the project and rename to work on it without that the changes would affect the other version.

  • It is hard to say what the issue is without more details (examples). Please check the linked resource and build variables used by the project. See what they are defined to and check that the definition points to the correct path. That is the first thing to check.
  • Hi Ki,

    how can I check this, can you maybe give me a short introdcution, I am a little bit confused where to look?
  • Please see:

    http://software-dl.ti.com/ccs/esd/documents/ccs_portable-projects.html#variables

    For example, see how the below project uses the linked resource variable "SRC_EX". 

    Check the Path Variables tab and see if it defines to. In my example below, SRC_EX is based of ORG_PROJ_DIR, which is based of ORIGINAL_PROJECT_DIR

    Do this for all the variables. Make sure the variable is valid and defied to the correct path. Check your include search paths and other build properties

    Thanks

    ki

  • I checked the linked resoruces and build variables and it looks right, look? What I should do now so that the project is running again?

  • My problem is that I damaged my whole project and now I not even able to run the previous version. Is there a way to re-use the project or should I do everything from scratch? I need a guidline how to duplicate safely projects so that I can do changes with don't affects the previous version.
    Is there something available, I was searching and to be honest I did not found a clear guideline for that
  • sensortag_fan said:
    I checked the linked resoruces and build variables and it looks right, look?

    Actually, it doesn't. Your ORG_PROJ_DIR points to PROJECT_ROOT. This is because you made a copy of an imported project. ORG_PROJECT_DIR should point to the original location of the example project inside the SDK. Look at my screenshot - ORIG_PROJ_ROOT points to ORIGINAL_PROJECT_ROOT... which points to a directory inside the SDK.

  • sensortag_fan said:
    My problem is that I damaged my whole project and now I not even able to run the previous version. Is there a way to re-use the project or should I do everything from scratch? I need a guidline how to duplicate safely projects so that I can do changes with don't affects the previous version.
    Is there something available, I was searching and to be honest I did not found a clear guideline for that

    the old BLE projects are delicate and true portability can be an issue because of the way the project variables were used. You need to fix the variables in the project as I mentioned in my prior post. What you were doing regarding copying projects and importing to a new workspace is ok, you just need to understand how the variables work and adjust them as needed.

  • Thank you so much for the answer. Okay I was able to recover the project. I found a way how to create copies of imported projects. Everytime I need to have a duplicate I am copy the ble sdk root folder (make a copy of the in the same directory --> c:\ti\simplelink) and I create a new workspace for it. So the changes does not affect the other version of the project, like is stated here: processors.wiki.ti.com/.../Creating_copy_of_example_project

    Do you have another way how to do it?

    Thanks for your help

  • Yes that sounds about right. It is a bit of a messy workaround but because of the way the old BLE SDK projects were structured, there likely isn't a better alternative. The projects that come with the newer simplelink SDKs are structured better to make this easier but they don't support the CC2650 unfortunately.