SPRAD68 February 2023 TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1
One of the key benefits of using SysConfig is the auto-generated code. The right-hand side of the tool show-cases all of the files SysConfig generates based on the settings chosen. Upon changing a setting within the tool, the files that are modified change icons to signify a modification made. This provides an easy way to identify which files are modified for certain functionality. If you desire not to use one or all of the generated files, toggle the 'Include in build' switch to remove the generated files from being included in the build.
The ".genlibs" files generated by SysConfig includes all of the paths to any ".lib" files that the project requires. These files are automatically pulled in when the project is compiled to maintain proper linking and usage of the libraries. Below is an example entry located within the ".genlibs" file of the motor control sdk libraries file (mcsdk_libraries.cmd.genlibs).
-l"/libraries/observers/est_lib/lib/fast_full_lib.lib"
The ".opt" files includes all paths for any required header files. The content of these files is auto-generated based on the added motor control libraries. Below is an example extry located within the ".opt" file of the motor control sdk libraries file (mcsdk_libraries.opt).
-I"C:/ti/c2000/C2000Ware_MotorControl_SDK_4_01_00_00/libraries/control/pi/include"
Lastly, any reference files used are showcased within the 'Reference File' pane. These reference files are added to the project based on the settings selected. The image below shows the "fwc.c" file being added to the project when the "fwc" motor feature is added.