Disable SysConfig

This section will describe the steps necessary to disable SysConfig, either entirely or just a few selected files. Disabling SysConfig may be necessary when freezing source code for production or when you are satisfied with the output.

This example will use the basic_ble project from the BLE5-Stack, but the steps can be adopted for other project.

A summarization of the steps can be found below:

1. Build the project at least once so that SysConfig can generate output

2. Locate the generated files

3. Copy generated files from build directory

4. Modify compiler/linker files to point to moved files

5. Exclude generated files from building.

Tip

Check if configuring SysConfig to Reserve Peripheral(s) could help.

Locating Generated Files

After building the basic_ble project using default settings, the first step to disabling SysConfig is to determine which files it has generated.

Click the <> button in SysConfig to see which files it is currently generating. See SysConfig generated files - Command files are marked with yellow for an example of which files are generated by SysConfig for the basic_ble project.

In CCS these files are placed in <build_config>/syscfg

• <build_config> is the build configuration of the project. (e.g. Debug)

In IAR these files are placed in the project folder (e.g. ~/<proj_import>/)

• <proj_import> is the location selected when importing the project in IAR

• In the IDE the SysConfig files reside in a virtual folder called SysConfig Generated Files. You can find their location by right clicking any of the files in this folder and selecting Open Containing folder…

Figure 157. SysConfig generated files - Command files are marked with yellow

Copy Generated Files

IAR Users may skip this step

In CCS the build directory is cleaned every time the project is rebuilt, so it is necessary to copy the generated files to a permanent location before the project is rebuilt. Follow the steps below to do so. We will place the files in the application in a folder called syscfg but it can be called anything.

1. Right click on the project -> New -> Folder

2. Copy the files from <build_config>/syscfg to the new folder.

• See Generated Files to see which files to copy

Attention

When debugging using ROV, be sure to place syscfg_c.rov.xs in the root directory of the project. This way, the ROV tool can pull in the appropriate debug tools as selected by SysConfig initially.

Modifying Compiler/Linker Settings

IAR Users may skip this step as the SysConfig output is already in a non destructive location. However, if you moved the SysConfig generated content to a new location elsewhere in the file system, you may need to change the project settings.

The .c, .h, and .opt files generated by SysConfig are consumed by the compiler and linker as part of the build process. Moving the files to a new location means that we need to modify the project settings to find them. For the case of basic_ble this means:

1. Change include paths (Project > Properties > ARM Compiler > Include Options)

• Add ${PROJECT_ROOT}/syscfg

2. Change location of .opt files (Project > Properties > ARM Compiler > Advanced Options > Command Files)

• Change the location of the ti_build_config.opt and ti_ble_app_config.opt to be in ${PROJECT_ROOT}/syscfg

3. Modify linker include paths (Project > Properties > ARM Linker > File Search Path)

• Change the location of ti_utils_build_linker.cmd.genlibs from ${PROJECT_BUILD_DIR}/syscfg/ to be in ${PROJECT_ROOT}/syscfg/

Exclude Generated Files from Building

In order to do this, click the <> button in SysConfig and deselect the Include in Build button of files you no longer want generated by SysConfig. Make sure that these files are the only ones which have been copied into your custom syscfg application folder.

Figure 158. SysConfig generated files, excluded ones of which have been deselected.