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

3.4 Code Generation

The C2000 SysConfig auto-generates code and other debug or visualization artifacts to simplify the user's development process. The auto-generated content can be viewed inside SysConfig by clicking the Show Generated Files button at the top right corner.

Figure 3-11 Auto-Generated Content

The content generated by the CLB Tool is removed when all instances of TILE used in the CLB Tool are removed from SysConfig. Similar to the CLB Tool, if the DCSM Tool to their design is added, new files generated by the DCSM tool will appear in the Generated Files panel.

To view a generated file and a live view of the updates made to the file as the configurable options are changed in the GUI, click on the file name in the Generated Files panel.

  • Click on the board.c file in the Generated Files panel
  • In the CLB module, check the Enable CLB box
  • The board.c file should be updated with the changes made in the code marked with RED and GREEN
  • You can pick the DIFF mode by clicking on the three dots at the top right corner of the GUI
Figure 3-12 Changed Configurable Code Generation DIFF

C2000 SysConfig generates two code files:

  • board.c: This file contains the initialization code for each module including PinMux. An all inclusive function named Board_init is available which initializes all module. You can choose to call the individual Module_init functions in their application, or you can use the Board_init function to use all modules. You can also choose to add PinMux_init to your application code to use only the PinMux initialization feature of the tool.
    Note: Board_init does not call DC_DC_init. DC_DC_init must be called before Board_init.
  • board.h: This file contains the prototypes for all generated functions in the board.c file, along with the re-namings of the modules for their specific application. Also, the GPIO number assigned for each PinMux option along with more information on each peripherals configuration.
Figure 3-13 board.h File