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 , 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

2.1 Example C2000 SysConfig in CCS

To get started with C2000 SysConfig, let's import an existing example with C2000 SysConfig support.

  1. Launch CCS and import the example: clb_ex8_external_signal_AND_gate.projectspec
    1. Select Project → Import CCS Project
    2. Browse to C2000Ware_VERSION\driverlib\f2838x\examples\c28x\clb\CCS
    3. Select the clb_ex8_external_signal_AND_gate.projectspec project and import it
  2. Inside your CCS project you should be able to see the syscfg file along with the rest of the application files.
    Figure 2-1 C2000 SysConfig Example Project in CCS
  3. Double click on clb_ex8_external_signal_AND_gate.syscfg file and the C2000 SysConfig GUI will launch
    Note: You can also right-click on the syscfg file, then select Open With → SysConfig Editor.
    Figure 2-2 Launching SysConfig GUI
  4. The C2000 SysConfig GUI should be launched inside CCS and should look similar to one shown in Figure 2-3.
    Figure 2-3 C2000 SysConfig GUI
  5. Click the Device View button at the top right corner of the SysConfig GUI to see the device and package used for your project
    Figure 2-4 Device View

C2000 SysConfig support is added in the Project Properties. By default, this project was configured for F2838x family of devices and the selected device package is set to 337 BGA package. If the Project Properties for C2000 SysConfig support is not set up by default in your CCS project, the syscfg file will not launch the GUI succesfully. Most driverlib projects have the Project Properties set up by default for C2000 SysConfig. If Project Properties are not set up correctly, Section 8 describes how C2000 SysConfig can be added to a CCS project.