SPRACX3 October   2021 TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P550SJ , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DK-Q1

 

  1.   Trademarks
  2. 1 Introduction
  3. 2 Getting Started With C2000 SysConfig
    1. 2.1 Example C2000 SysConfig in CCS
    2. 2.2 Other SysConfig Tools
  4. 3 C2000 SysConfig Overview
    1. 3.1 Modules
    2. 3.2 PinMux
    3. 3.3 Peripheral Initialization
    4. 3.4 Code Generation
    5. 3.5 Error Detection
    6. 3.6 SysConfig Script File
  5. 4 SysConfig Generated Files After the Project is Built
  6. 5 Application Code Based on C2000 SysConfig Initialization
  7. 6 Interrupt Support
  8. 7 Device-Specific Code Generation
  9. 8 Adding C2000 SysConfig Support to Existing Projects
  10. 9 Remove C2000 SysConfig Support from Projects
  11. 10Standalone SysConfig Tool
  12. 11Summary
  13. 12References

8 Adding C2000 SysConfig Support to Existing Projects

Most driverlib based examples in C2000Ware are delivered with built-in support for C2000 SysConfig. Even if the example does not have a syscfg configuration file, the project properties for C2000 SysConfig are most likely already configured.

Follow these steps to check if the C2000 project properties are set up for C2000 SysConfig development:

  1. Right-click on the project and select Properties.
  2. In the left panel of the project properties, under the Build category, check to see if the SysConfig options are available.
  3. If the SysConfig option is available under Build, SysConfig is enabled for your project.

If the SysConfig module is not enabled in your project, follow these steps to enable it:

  1. Add an empty file of the syscfg file named empty.syscfg to the project by copying the file into the project or creating a new file in the project.
  2. CCS will ask whether or not to enable SysConfig. Accept and select Yes.
    GUID-CE952D36-69B5-42E1-BF48-B022E9FB6A7A-low.png Figure 8-1 Enable SysConfig in the CCS Project

After the SysConfig feature has been enabled, you can change the settings inside the project properties to select C2000 SysConfig and choose your specific device package/part.

Detailed descriptions on how to configure the SysConfig project properties can be found at: How to configure CCS Project Properties for C2000 SysConfig.

Note: C2000 SysConfig is built on top of C2000 driverlib software layer.