SysConfig 1.17.0+3128 Release Notes

Table of Contents

Overview

• Release Date: July 10, 2023
• Build Version: 1.17.0+3128

What’s new for v1.17.0

v1.17.0 is an update to v1.16.2 which includes:

• PinMux Data updates for AM62, AM62A, AM64, J7, AM5718
• Ability to copy a module
• miscellaneous tool bug fixes and updates

Device Specific Notes for v1.17.0

AM64

• Removed CLKLB from MMC1. Saved files that include MMC1_CLKLB will may fail to load. This can be resolved by editing the .syscfg file and removing any lines that include "iMMC11.CLKLB".
• Updated use cases for MMC1. MMC1 operation is mutually exclusive with muxed GPIO functions.
• Updated use cases for ADC. ADC operation is mutually exclusive with muxed GPIO functions.

Known Issues

• GPMC0_FCLK_MUX is included in the SYSTEM group rather than GPMC.
• Saved files that include GPMC0_CLKLB will may fail to load. This can be resolved by editing the .syscfg file and removing any lines that include "iGPMC1.CLKLB".
• GPIO0_64,GPIO0_65, and GPIO0_70 pull select option is disabled despite having a pull available.
• GPI01_80,81,82,83,84,85,86,87 Are shown as IO, these are General Purpose Inputs only, no output function is supported.
• VDDSHV1 is incorrectly named PRG1. This should be PRG0
• VDDSHV2 is incorrectly named PRG2. This should be PRG1
• Signals a grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflict warnings with some peripherals.

AM62x

• Updated use cases for MMC0.
• Updated use cases for MMC1 & MMC2. MMC1 operation is mutually exclusive with muxed GPIO functions.

Known issues

• The PRUSS interfaces are listed as PRU_ICSSM0.
• Not all PADCONFIG bits are supported by the tool
• MMC use cases may have duplicates. This is to maintain compatibility with previous save files.
• GPIO1 only has 52 signals but tool shows 92 when GPIO1 is the selected peripheral instance.
• Signals a grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflict warnings with some peripherals.
• GPIO1_31 is missing "pull" option

AM62Ax

• Updated use cases for MMC0.
• Updated use cases for MMC1 & MMC2. MMC1 operation is mutually exclusive with muxed GPIO functions.

Known issues

• Not all PADCONFIG bits are supported by the tool
• MMC use cases may have duplicates. This is to maintain compatibility with previous save files.
• GPIO1 only has 52 signals but tool shows 92 when GPIO1 is the selected peripheral instance.
• Signals a grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflict warnings with some peripherals.
• GPIO1_31 is missing "pull" option

System Requirements

• Free Disk Space - 500MB
• Memory - 4GB
• OS - Windows 8/10/11 (64-bit), 64-bit Linux Distribution based on CCS requirements here, MacOS

Installation Instructions

The update can be applied to Code Composer Studion using the “Check for Updates” menu item. The standalone version of SysConfig can be updated by downloading and running the new installer.

Users of the cloud-based tool can browse to https://dev.ti.com and select the SysConfig tile on the portal page.

Getting Started

Software configuration with the SysConfig tool works in conjunction with a TI SDK. To see how this works, it is easiest to start with a CCS installation and an SDK for the device family you are using. Please refer to the device specific documentation included in the SDK for your device family. In general, you would start by importing an example from the SDK and open the the .syscfg file within CCS.

SysConfig may also be used as a low-level pinmux configuration tool. In this use case, you can start with the standalone SysConfig installer. Start the tool, please select the device, part, and package you are working with. You do not need to select a software product (IE SDK) unless you are using the tool for software configuration.

Importing TI PinMux Tool Projects

The SysConfig tool can open existing TI PinMux tool projects and convert these projects to the new .syscfg file format. Once converted, the project can only be saved in the new .syscfg file format.

Previous releases

All released versions and download links are available HERE.