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.

How to create CC3200 project based on one of the example projects?

Other Parts Discussed in Thread: CC3200, CC3200SDK

I'm still attempting to work through the CC3200 Getting Started Guide and hopefully after uninstalling and re-installing CCSv6 from scratch (yet again), I might be able to build the wlan_station example and run it.

Looking forward to creating my own custom project, I'm presuming it will be much easier to simply "duplicate" one of the example projects and modify/add code to that. Is there a guide to this process anywhere? One of the main issues/problems I see with the process:

I want to copy an example project from C:\ti\cc3200-sdk\examples\ to my own project directory - what is the easiest way to resolve the reference issues?

Anyone have a cheat sheet on how to do this?

Thanks,

Craig

  • Hi Craig,

         Do a search at CCS forum regarding "copy project'. There are several posts at CCS forum regarding copying projects that you can learn from.

    - kel

  • Hi Craig,

    CC3200 Programmer's Guide (<cc3200-sdk>\docs\CC3200-Programmers_Guide.pdf : section 5.3.2.3 onwards) gives details about CCS project creation, please folow the steps given there.

    Regards,

    Jitendra

  • Jitendra Gupta said:

    Hi Craig,

    CC3200 Programmer's Guide (<cc3200-sdk>\docs\CC3200-Programmers_Guide.pdf : section 5.3.2.3 onwards) gives details about CCS project creation, please folow the steps given there.

    Regards,

    Jitendra

    Thanks Jitendra, I must have missed that section when scanning the documentation. While that info is useful in explaining how to set up a new project, it's not explicitly about copying and modifying an existing project. This thread over in the Code Composer Studio forum has several good suggestions: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/37410.aspx.

    Note that I did not try any of these suggestions yet as I'm having trouble even getting the example in the Getting Started Guide to build (addressed in a separate post).

    Thanks,

    Craig

  • Yeah, you have to follow the instructions line by line.  And don't forget to upgrade to the latest Service Pack. 

    Honestly, I don't recommend using a different directory.  I copied a project and just let it live by reference in the same C:/ti/ directory.  Messing with project settings is usually something I avoid like the plague.

    If you really want to, this is the best guide I've seen on the material.  You don't have a Tiva device, but Chapter 2 is all about CCS and working with Path variables and build variables.  It explains it in a very step by step, easy to understand way.  It will cover everything you need to know if you want to move your project directory.

    This is a link to the workbook.  The CCS chapter is chapter 2.

    http://software-dl.ti.com/trainingTTO/trainingTTO_public_sw/GSW-TM4C123G-LaunchPad/TM4C123G_LaunchPad_Workshop_Workbook.pdf

    This is a link to the wiki.  You'll find a link to the workbook at the bottom of the page.  There's also a link to a  video for Chapter 2.  I prefer the workbook because I can work at my own speed.

    http://processors.wiki.ti.com/index.php/Getting_Started_with_the_TIVA%E2%84%A2_C_Series_TM4C123G_LaunchPad

  • Hi Craig,

    Do you still having issues with getting started? Also CC3200 SDK 1.0 default CCS settings allow user to copy project into workspace leaving the original always in c:/ti.

    I hope that helps in copying and modifying existing SDK examples. 

  • Hi Kaushal,

    I'm considering two options and was going to experiment with them today:

    (1) Duplicate the entire cc3200-sdk over into my main project directory (e.g. C:\projects\client\src\cc3200-sdk) then create a new workspace one level above (e.g. C:\projects\client\src\workspace). I would then adjust the example project settings (e.g. paths, etc.) so that they build in that location. I would duplicate one of the example projects in the same directory and then modify it for my application.

    (2) Create a new workspace in my project directory (e.g. C:\projects\client\src\workspace) then import some of the example SDK projects into the workspace using the copy project into workspace option. Not sure how I would then duplicate one of those imported/copied projects for use as the basis of my application. I did find out that you can't simply duplicate an example project directory, change the name, then import it - got an error to the effect that you can't have two projects with the same name in a workspace.

    Questions:

    - What the pros and cons of the two approaches above?

    - One the key things is that I need to get all src/libraries into my project directory for version control (git). Does either approach above work better for that?

    - If a new version of the SDK comes out, which approach above would make it easier to selectively update portions of my application code?

    Thanks,

    Craig

  • Hi Craig,

         I just copy the project and paste it in the same workspace. 

    - kel

  • You're copying the project while in CCS or you're copying the project out in Windows Explorer?

    I just tried creating a new workspace in my client project directory and then importing example projects from two locations (a) C:\projects\client\src\cc3200-sdk (I installed another copy of the SDK at this location) and (b) C:\ti\CC3200SDK_1.0.0 (this is the normal install location). For some reason, as soon as I check one of the example projects to import, CCS automatically checks "Copy projects into workspace" and then grays it out so you can't uncheck it!!! Why is that? If I already duplicated the entire cc3200-sdk directory under my client directory, why won't it let me import those projects without checking "Copy projects…"?

    I'm getting the impression that CCS is going to force me to use "Copy projects into workspace" no matter what. I'm fine with that as long as that really works properly (there seems to be many messages on this forum stating that it doesn't).

  • Craig Heilman said:
    CCS automatically checks "Copy projects into workspace" and then grays it out so you can't uncheck it!!! Why is that?

    This is normal for importing to CCS, CC3200 SDK 1.0.0 example projects.

    - kel

  • Ok, so I imported "blinky" into my new workspace with "Copy projects into workspace" checked. That project builds and runs. Next I imported wlan_station, again with "Copy projects…" checked. I then imported the associated projects (ti_rtos_config, driver lib, oslib, simplelink) and unchecked the "Copy projects…" box (CCS let me) because the Getting Started Guide states "For any library import, do not check the 'Copy projects into workspace' option. This would break the links the libraries have to their dependencies." Now we have a problem - the libraries are not copied to my project directory and are therefore not under source code control (git).

    Another problem is that the Getting Started Guide instructs you (section 3.1.3, steps 9-10) to open and edit common.h located at C:\ti\CC3200SDK_1.0.0\cc3200-sdk\example\common\. Same issue - I'm editing a file that is not under my client project directory and therefore is NOT under version control!

    If I go back to my option 1 above (i.e. duplicate the entire cc3200-sdk directory into my client project directory), will I even be able to import the libraries required for wlan_station or are those libraries hard-wired to only work from the C:\ti\CC3200SDK_1.0.0 directory?

  • Hi Craig,

        Just use the latest SDK version 1.0.0.

         Regarding building your example projects outside SDK, see details in this post below.

         macros.ini added at CCS6 project view?

    - kel

  • You can stop CCS from forcing the project to copy to the workspace by deleting the .ccsimportspec file.
    So simply copy one of the examples, remove this file, import to a workspace and you're ready to go. All references are relative so as long as you keep the code together it will work.

    See here:
    www.argenox.com/.../cc3200-example-code-imports