SysConfig 1.26.0_4407 Release Notes

Overview

Release Date: December 1, 2025
Build Version: **1.26.0

What's new for v1.26.0

v1.26.0 is an update to v1.25.0 which includes:

New devices: AM13E230x, TPLD1202,
Updated device data for AM5766, AM5768, AM243x, AM275, AM62x, AM64x, MSPM33C321X
Enhancements and bug fixes

Device Specific Notes for v1.26.0

AM243

Added IOSets for I2C2
Added initial support for drive strength

AM275

Added IOSets for I2C3, I2C6, SPI1, and SPI2
Added initial support for drive strength selection on LVCMOS IOs

AM62

Added initial support for drive strength selection on LVCMOS IOs

AM62A

Added initial support for drive strength selection on LVCMOS IOs

AM62D

Added initial support for drive strength selection on LVCMOS IOs
Corrected address offset for USB0_DRVVBUS (PADCONFIG149) and USB1_DRVVBUS (PADCONFIG150)

AM62L

Added initial support for drive strength selection on LVCMOS IOs
Generated dtsi file updated from AM62LX_MCU_IOPAD to AM62LX_WKUP_IOPAD

AM62P

Added initial support for drive strength selection on LVCMOS IOs

AM625SIP

Added initial support for drive strength selection on LVCMOS IOs
Removed 1.2v option for VDDS_DDR.

AM64

Added initial support for drive strength selection on LVCMOS IOs
Added IOSets for I2C2

Known Issues

AM243x

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".
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".
GPMC0_FCLK_MUX is included in the SYSTEM group rather than GPMC.
GPIO0_18, GPIO0_19,GPIO1_64,GPIO1_65, and GPIO1_70 pull select option is invalid. These GPIOs are implemented by I2C buffers. No pull option.
GPI01_80,81,82,83,84,85,86,87 Are shown as IO, these are General Purpose Inputs only, no output function or pull options are supported.
VDDSHV1 is incorrectly named PRG1. This should be PRG0
VDDSHV2 is incorrectly named PRG2. This should be PRG1
Signals are grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflicts with some peripherals.
The RGMII and RMII interfaces have been merged into CPSW. This is to correct a bug that allowed both RMII1 and RGMII1 to be simultaneously selected. Note that this will break previously saved syscfg files that implemented RGMII and/or RMII . There are two options to resolved this.

Use the previous tool release to remove all RGMII and RMII interfaces and re-save. The updated syscfg file should now successfully load in the new release. Re-add the RGMII/RMII interfaces using the CPSW peripheral and the appropriate use case.
Directly edit the saved syscfg file and remove all lines containing iRGMII or iRMII. The updated syscfg file should now successfully load in the new release. Re-add the RGMII/RMII interfaces using the CPSW peripheral and the appropriate use case.

AM62x

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 conflicts with some peripherals.
GPIO1_31 is missing "pull" option
AUDIO_EXT_REFCLK0/1 pins cannot be set as input. Workaround is to edit the generated files.

AM62Ax

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 conflicts with some peripherals.
GPIO1_31 is missing "pull" option

AM62Dx

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 conflicts with some peripherals.
GPIO1_31 is missing "pull" option

AM62Lx

Not all PADCONFIG bits are supported by the tool
Support for changing Slew rate on 1.8V-LVCMOS IOs is currently disabled.
Drive Strength support for LVCMOS IOs is limited to peripherals that have all instances/signals on LVCMOS IO buffers
Signals a grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflicts with some peripherals.

AM62P Signals are grouped by function/domain, not power domain. It is therefore possible to encounter voltage conflicts with some peripherals.

Not all PADCONFIG bits are supported by the tool
GPIO0_31 incorrectly shows no pull or DRV_STR available.

AM62SIP

The PRUSS interfaces are listed as PRU_ICSSM0.
Not all PADCONFIG bits are supported by the tool
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 conflicts with some peripherals.
GPIO1_31 is missing "pull" option
AUDIO_EXT_REFCLK0/1 pins cannot be set as input. Workaround is to edit the generated files.

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.