SPRUIQ5 May 2019 TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S
The procedure given here is a basic guideline to develop software using this kit regardless of the C2000 MCU being used. The description in this guide is based on F28379D and the same will apply to all MCUs that TI may use this kit for in future. Any deviation to this will be appropriately addressed when required.
NOTE
When Code Composer Studio opens, the workspace launcher may appear that requests the selection of a workspace location on the hard drive where all the settings for the IDE, that is, which projects are open, what configuration is selected, and so forth. are saved. This can be anywhere on the disk. The location mentioned in the following steps is for reference. If this is not your first time to run Code Composer, the dialog in the following steps may not appear).
NOTE
A Getting Started tab opens with links to tasks for creating a new project, importing an existing project, and watching a tutorial on CCS.
NOTE
You must set up the Target Configuration to configure Code Composer Studio to recognize the MCU to which it must connect. The target configurations are already set up in TMS320F28379D.ccxml in the project files.
NOTE
If Use shared location is checked, store this configuration file in a common location by CCS for use by other projects.
NOTE
A new tab opens. (See Figure 3-2.)
NOTE
Alternatively, to use the Target Configuration file in the SDK project at any time, proceed to step 22 or skip to step 28.