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

Best way to manage imported projects for different Stellaris dev kits and Launchpads?

Nolan Moore
Prodigy 40 points
Other Parts Discussed in Thread: LM3S3748

Hi everyone, I'm new to this particular forum, so apologies if I annoy/offend/screw up something :) 

I've assembled a small collection of TI dev kits, including the MSP430 Launchpad, the new Stellaris Launchpad, and a EKS-LM3S3748 Stellaris dev kit.

For the two Launchpads, I assume the best way to go is to use Code Composer Studio 5.2.1. The LM3S3748 came with CCS 4, but I think I can simply use the projects and examples that came with its Stellarisware in 5.2.1. 

Now my question is, what is the best way to manage and access all of these projects from within CCS? It seems like everything will be mixed up and jumbled if I simply import everything. Any thoughts on how to keep it clean and functional? Thanks much!

  • 0
    TI__Guru*** 130875 points

    Hi Nolan,

    first of all, welcome to the TI development world!

    how you organise is largely a personal question .   We all organise ourselves differently.  However some comments

    - ccs uses workspaces which can handle many project

    - you may want to start with a workspace for each kit as one way to organise 

    All the best with development.  Please let us know whether this helps.  As you start up also feel free to start a post for new questions or issues that arise.

    Best regards,

    Lisa

  • 0 in reply to Lisa TI
    Prodigy 40 points

    Ah, workspaces! I totally didn't think to use those. I'll give it a try.

    Thanks, Lisa :)