• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 2137 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/cc1350: Best way to update shared project to new SDK version

David Bartle
Intellectual 585 points

Part Number: CC1350

Tool/software: Code Composer Studio

What is the best way to update the Code Composer project to the most recent version of the SDK? We have a few developers using a Git project and I find that we each have to download the new SDK, update our environment variables, etc. to utilize the new version (e.g moving from simplelink_cc13x0_sdk_1_40_00_10 to simplelink_cc13x0_sdk_1_50_00_08). For example, under the project properties, I find the Build Variables "COM_TI_SIMPLE_LINK_CC13X0_SDK_INSTALL_DIR"  and "COM_TI_SIMPLE_LINK_CC13X0_SDK_INSTALL_DIR_REPOS" must be modified in everyone's CCS. Is there a way to create a project makefile that specifies the environment variables for CCS? Is this problem solved with other development environments like IAR?

  • 0
    TI__Guru**** 163095 points

    David,

    The article at the link below shows how to change the version of the SDK used by a project.  

    The build variables are automatically populated by CCS, you should not have to change those.  But in order for CCS to populate them with the current values it has to be aware of the installations of the SDK.  Basically the shared project can be set to use 1.50 but if CCS has not discovered that version then it will use the closest version it is aware of which in your case would be 1.40.

    The article above assumes that CCS is aware of both the version you are currently using as well as the one you are switching to.  By default this would be the case if the SDK were installed via resource explorer or installed in one of the default paths that CCS looks for software products.  However in your case the SDK is in GIt and likely located on each users machine in a location CCS doesn't automatically search.  However you can tell CCS where to look for products.

    I am not sure what your setup is but lets say that when you get the latest content from Git it pulls the sdk and it looks something like this:

    C:\Git\SDK\1.40

                           1.50

    In this case if we were to add C:\Git\SDK to the list of locations that CCS searches for software products then both the 1.40 and 1.50 versions of the SDK would be discovered by CCS and would be available for use.

    In CCS if you go to Window -> preferences (if on Windows or Linux), on Mac it is under the main application menu.  Then expand Code Composer Studio -> Projects in the tree.  Then at the top of the dialog you can specify the locations to search for products and at the bottom it will show you the products that CCS has discovered.  In my case most of the products are not actually in the 2 locations specified but were still discovered as I installed them via Resource Explorer.

    These settings are not something that is shared and would have to be setup by each user.

    Regards,

    John