Overview[edit]

This is an early preview of an alternative graphical configuration tool called SysConfig, which can help to generate TI Driver and pin configuration code. The SysConfig tool is integrated with logic to help manage, expose and potentially solve conflicts visually to free up more time for developers to create differentiated applications. Use of this preview version of SysConfig is not required for developing on SimpleLink devices. However, we encourage you to try it out and to give us your feedback.

Note: This early preview only works with CCSv8.1 and the 2018/Q2 SimpleLink SDKs.

Video Demo[edit]

<embedvideo service="youtube">https://youtu.be/Z9ilZ1dMelE</embedvideo>

SysConfig v1.0 Feature Set[edit]

• Interactive & intuitive configuration tool allows developers to spend less time enabling, configuring & initializing pins & peripherals so they can spend more time creating differentiated applications.
• Interactive graphical tool for enabling, configuring & generating initialization code for pinmuxing & TI Drivers.
• Support for all SimpleLink MCUs & some TI LaunchPad Development Kits
• Real-time conflict management to ensure developers are creating a valid system configuration
• SysConfig is integrated with logic to help resolve potential conflicts by proposing valid pin & TI Driver configurations
• Board.c and Board.h files are automatically generated, fully-commented at build time based on GUI inputs
• Real-time code preview is available allowing developers to see what code is being generated based on GUI inputs
• Both device & board level views are available to visually show pin & peripheral configurations

SysConfig v1.0 Summary[edit]

The SysConfig preview objectives are:

• A vehicle for incremental feedback on the user interface and use case flow.
• Maintain meta-content compatibility for users creating plug-ins to SDKs

The content of this beta includes

• SysConfig tool integrated in CCSv8.1
• SDKs for CC3220, CC13xx, CC26x2 and MSP432.

Not included in this beta

• Full SDK integration

It is recommended that beta users subscribe to this page to receive notifications of changes to the preview release.

Installation[edit]

You will require two components:

• A CCS v8.1 Windows installation

  * Download the CCS installer here, extract and run the CCSv8.1 installer. Be sure to install support for all SimpleLink devices.

• SimpleLink Product SDKs

  * Download the SDKs for the families you will be working with. You only need the specific SDKs for the families you are using.
     * CC13xx/CC26xx Download  (Coming Soon)
     * CC32XX Download (Coming Soon)
     * MSP432E4 Download (http://www.ti.com/tool/download/SIMPLELINK-MSP432E4-SDK)
     * MSP432P4 Download (http://www.ti.com/tool/download/SIMPLELINK-MSP432-SDK)
  * Install the selected SDKs into the root folder of your CCS installation

Supported Boards and BoosterPacks[edit]

The following LaunchPads are supported by the related SDKs:

• CC26X2R1_LAUNCHXL
• CC1352R1_LAUNCHXL
• CC3220SF_LAUNCHXL
• MSP_EXP432E401Y
• MSP_EXP432P401R

The following BoosterPacks are supported (see the section below regarding adding BoosterPacks):

• 430BOOST-SHARP96
• BOOSTXL-SENSORS

Quick Start[edit]

The fastest way to get started with SysConfig is to import one of the examples from the SysConfig preview folder. For example:

• Start CCS
• In the project manager, select Import → CCS Project
• Browse in the selected SDK to examples/syscfg_preview/rtos/<board>/drivers
• Select and example CCS project and import it
• Build the project and load it on the target board
• Double-click the .syscfg file; the file will open in a few seconds

Adding BoosterPacks[edit]

This version does not automatically load the available BoosterPacks from the SDKs. There are two workarounds that can be used:

• Add the desired BoosterPack directly to the .syscfg script
• In your project view, find the .syscfg file. Right click, and select Open With→Text Editor
• Add this line near the top of the script: var boosterpack_1 = scripting.addHardware("/ti/boards/boosterpacks/<your_booster_pack_name>");
  • For example: var boosterpack_1 = scripting.addHardware("/ti/boards/boosterpacks/430BOOST-SHARP96.syscfg.json");

Add other boosterpacks you may want to use. The list of available boosterpacks can be found here.

• Save and closed the .syscfg file.
• Open the syscfg file again using Right-Click→ Open With → System Configuration Editor

Known Limitations, Bugs, Etc[edit]

• The SysConfig tool UI can take several seconds to appear after opening the .syscfg file.
• No UI support for migrating between device families.
• For the moment, we're only testing the Windows build. The Linux and OSX builds will come later.
• Some configuration options are enabled even though selecting them will, for a LaunchPad, always result in a pin conflict being reported by the GUI.
• Highlighting of used pins in the board view does not always work
• If you have multiple sysconfig projects, double-clicking on error/warnings reported in the console against the generated Board.c may open the wrong Board.c source file

Providing feedback[edit]

Please submit questions or feedback via the relevant product forum at http://e2e.ti.com/support/