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.

Porting projects from Cloud CCS to eclipse desktop CCS?

Other Parts Discussed in Thread: CCSTUDIO

I have the Cloud CCS up and running with the SensorTag and SensorTagStack.  Compile and debug OK -- except the web bandwidth locally (Saipan, a tiny island far, far away) cause many session disconnects.

I woud like to shift development/debugging of these T.I. examples to the eclipse based Ccstudio ( Version: 6.1.3.00033 ) on my mac (OS 10.11.5 -- El Capitan) and develop locally.

I have read and followed all of the obvious suggestions in the forums and lit, but all methods for import fail (usually in different ways)

Are there any guidelines for the specific question of moving a project from the cloud to the Eclipse based Ccstudio?

  • Hi Jim,
    Can you provide more details about the failures you are experiencing?

    Thanks
    ki
  • Step 1- import SensorTag App and SensorTag Stack into CCS
    Step 2- Compile OK. Run OK (This is good up to here. Nice.)
    Step 3- Share project via dropbox -- Dropbox gets lots of files

    Result: Specific failure -- Several files are corrupt and truncated. (run ID 1465420337863_00000719)
    EXAMPLE: file ICallBLE/bleUserConfig.h has 373 lines and has line 372 as:
    #endif /* BLE_USER_CONFIG_H */

    When exported to dropbox, line 373 is gone, and line 372 has been changed to:
    #endif /* BLE_USER_CONFIG_H

    The comment terminator has been lost by the TI export to dropbox process.
  • Just to clarify some of the steps:

    1 - import the projects into CCS CLOUD, correct?
    2 - compile/run was successful on CCS CLOUD, correct?

    Also do you have the BLE STACK installed on your desktop?
  • 1) and 2) are correct.

    I have not been able to use the desktop development system at all.  I will be able to use the Cloud development system if I can get the project over to github.

    One of the first methods I used to get the project into the desktop development system was via "export to dropbox."  The export step was corrupt as shown above.  Other files were missing, also: the Makefile, for one.

    The "Export to Dropbox" functionality is likely missing a "close" on the stream to dropbox.  Events, events, events... aways more events,