SysConfig 1.21.0 Release Notes

Table of Contents

Overview

• Release Date: August, 2024
• Build Version: 1.21.0

What’s new for v1.21.0

v1.21.0 is an update to v1.20.0 which includes:

• New Devices: AM275x, AM5716_SR1.0_beta, AM5718_SR1.0_beta, CC3500
• Device Data updates: 66AK2G12, AM3351, AM335x, AM437x, AM438x, AM62Ax, AM62Px, AM62SIP, AM62x, AM64x, AM65xx_SR1.0, AM65xx_SR2.0_beta, AMIC110, AMIC120, F28P55x, MSPM0C110X, MSPM0G110X, MSPM0G150X, MSPM0G310X, MSPM0G350X, MSPM0L110X, MSPM0L122X, MSPM0L130X, MSPM0L134X, MSPM0L222X, MSPS003FX
• Removed Devices: CC13x0F128RHB, CC13x0F128RSM, CC3200, CC3220S, CC3220SF, CC3230S, CC3230SF, CC3235S, CC3235SF, DRA80x_SR1.0, DRA80xM_SR2.0_beta

Notable changes

• Device/board selection is based on part numbers that are in synch with product names as their appear to www.ti.com. User may be asked to select specific part name that matches their device.
• Miscellaneous tool bug fixes and updates

Device Specific Notes for v1.21.0

Sitara AM243x

• Removed I2C2 as option for ALX package
• Updated optional pins in GPMC usecases (ALV)
• Removed CLKLB from MMC1. See Known Issues
• Removed CLKLB from GPMC (ALV). See Known Issues
• Added use cases for USB – enables selection of USB2 and/or USB3 and allows USB2 to be selected with SerDes (ALV)
• Added USB0 RCALIB which was not included in previous release (dedicated pin).
• All I2C interfaces have pull options disabled.
• 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.
• Renamed "USB 3.0" use case to "USB Superspeed" (ALV)
• Added DDR0_CAL0 to DDRSS use cases (ALV)
• Updated PCIe use cases (ALV)
• Resolved USB0_DRVVBUS/GPIO1_79 not being included in generated files.
• Corrected signal assignments for TMS (JTAG) and RESET_REQZ (SYSTEM) in *_pinmux.h files.
• 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.
• 1. 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.
• 2. 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.

AM243x Known Issues

• 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.
• 1. 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.
• 2. 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.

Sitara AM62Ax

• Removed DDR4 use case from DDRSS - was incorrectly included.

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

Sitara AM62x

• No updates

AM62x 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 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.

Sitara AM62Ax

• Removed DDR4 use case from DDRSS - was incorrectly included.

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

Sitara AM62P

• Added IOsets to CPSW CPTS signals.

AM62P Known Issues

• 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 available

Sitara AM62SIP

• No updates

AM62SIP Known issues

• 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.