C2000™ SysConfig is a graphical user interface (GUI) tool that allows you to configure your C2000 Real-Time Control MCUs. The following are the features supported in the tool:

• System initialization code generation: C2000 SysConfig generates initialization code for the C2000 device including peripheral initialization, interrupt initialization, PinMux initialization, and so forth.
• Device PinMux visualization: A visual representation of the device and all of its pins, a list of all possible PinMux options, your selected mode for each pin, and a summary PinMux CSV file is supported by the tool.
• Error detection: C2000 SysConfig is capable of catching configuration errors and notifying you of the incorrect setup.
• Device level dependency identification: C2000 SysConfig identifies the dependencies in the device and ensures that the dependent peripherals are all configured by you.
• Device level error detection: Device level configuration errors caused by dependent peripherals are caught and you are notified of the error.
• Portable device initialization: Device initialization settings are portable between device families and device packages.
  Note: The device families supported are:

  • F2807x, F2837xS, F2837xD
  • F28004x
  • F2838x
  • F28002x
  • F28003x
• Seamless support for other tools: Support for other SysConfig tools such as CLB Tool and the DCSM Tool.

C2000 SysConfig is available inside C2000Ware and requires the SysConfig Tool, which is delivered built-in with Code Composer Studio™ (CCS) IDE and is also delivered as a standalone tool for use with other IDEs.

Figure 1-1 C2000 SysConfig Overview

The C2000 SysConfig support is built on top of the C2000 driverlib software layer. To get started, either start from an existing C2000 SysConfig based driverlib project or add C2000 SysConfig and driverlib support to an existing project.

Most driverlib examples in C2000Ware have either an example.syscfg file or you can add a file with the .syscfg extension. Double clicking and opening the .syscfg file launches the C2000 SysConfig tool.

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.

Other SysConfig-based tools such as the CLB Tool and the Security (DCSM) Tool are seemlessly integrated with C2000 SysConfig. If these tools are supported by the device family selected by you, they will automatically show up as a new section under the modules panel of the SysConfig GUI.

The CLB Tool and DCSM Tool can be used as standalone tools. You can modify the CCS Project Properties to use only the CLB Tool or the DCSM Tool.

For more information on the DCSM Tool, visit:

• C2000™ DCSM Security Tool

For more information on the CLB Tool, visit:

• CLB Tool User's Guide
• Designing With the C2000™ Configurable Logic Block (CLB)

The available modules/peripherals for each device/package is listed in the left panel of the C2000 SysConfig GUI. The number of each peripheral available for the device is shown in Figure 3-4 as the modules are added to the application by you. This allows for a simple resource management by you.

Each module's description is shown in the middle panel (configurable options panels) and once the module is added, the description is minimized. The description can easily be expanded by clicking the question mark icon next to the name of the module (if available).

For each peripheral with PinMux options, there is a PinMux submodule available in the Configurable Options panel. Inside the PinMux submodule, there are configurable options for each pin of the peripheral along with the instance of the peripheral. The solution for the PinMux is shown as the selected option for each pin. You can LOCK the solution to ensure it does not change as more modules/peripherals are added.

Above the PinMux submodule, a configurable option named Use Case is also available to limit the available peripheral pins in the PinMux module. Selecting the Custom option for the Use Case adds a new configurable option named Pins Used, where you can select the peripheral pins for their specific custom use-case.

It is also possible to modify the PinMux submodule GUI to show not only the device pin names, but also the device GPIO number. To change the pin name representation:

• Click the three dots at the top right corner of the C2000 SysConfig GUI
• Select Preferences and Actions
• In the Device Pin Labels options, select the Device Pin Name option

The device PinMux summary is available inside the pinmux.csv auto-generated file.

Figure 3-8 PinMux Summary CSV Auto-Generated File

The pinmux.csv file contains not only the selected PinMux options, but it also contains ALL AVAILABLE PinMux options for each pin.

Figure 3-9 pinmux.csv Auto-Generated File

C2000 SysConfig initializes the C2000 Real-Time Control MCU. Each module has support for all possible supported configurations. Relevant options are made visible or hidden as needed by the tool. Some peripherals have dependency on other peripherals. These dependencies are identified by the tool and you are guided to configure all needed dependent peripherals.

Figure 3-10 shows the configurable options for the SCI peripheral. Placing the cursor on the configurable option shows the tool-tip for that option.