SysConfig 1.19.0_3426 Release Notes
Table of Contents
Overview
- Release Date: Jan 15, 2024
- Build Version: 1.19.0+3426
What’s new for v1.19.0
v1.19.0 is an update to v1.18.1 which includes:
- New devices: AM62SIP, AWR2544, CC2340R22RKP, CC2340R53RKP,J722S_TDA4VEN_TDA4AEN_AM67, MSPM0L122X, MSPM0L222X
- Various minor updates to existing device data
- Miscellaneous tool bug fixes and updates
Device Specific Notes for v1.19.0
AM64
- Added MMC0_CALPAD to MMC0 use cases
- USBx_DRVBUS RX disabled.
- Added DDR0_CAL0 to DDRSS use cases
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.
AM62
- Added missing padconfig control for SYSTEM - AUDIO_EXT_REFCLK0 and AUDIO_EXT_REFCLK1
- Adjusted RX and Pull options for SYSTEM
- Adjusted RX and pull options for MCU_SYSTEM, MCU_OBSCLKOUT0 now de-selected by default.
- Removed pull and RX options from USB signals that have no padconfig control.
- USBx_DRVBUS RX disabled.
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
AM62A
- Adjusted RX and Pull options for SYSTEM
- Adjusted RX and pull options for MCU_SYSTEM, MCU_OBSCLKOUT0 now de-selected by default.
- Removed pull and RX options from USB signals that have no padconfig control.
- USBx_DRVBUS RX disabled.
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
AM62P
- Added missing padconfig control for SYSTEM - AUDIO_EXT_REFCLK0, AUDIO_EXT_REFCLK1, and MAIN_ERRORn
- Adjusted RX and Pull options for SYSTEM
- Adjusted RX and pull options for MCU_SYSTEM, MCU_OBSCLKOUT0 now de-selected by default.
- Removed pull and RX options from USB signals that have no padconfig control.
- Corrected typo select descriptions.
- Added MMC0_CALPAD to MMC0 use cases
- Fixed GPMC0_IOSet_2. GPMC0_FCLK_MUX was incorrectly specified.
Known Issues
- Not all PADCONFIG bits are supported by the tool
- GPIO0_31 incorrectly shows no pull available
AM62SIP
- Initial Release
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
66AK2Gx/AM65x/AM335x/AM437x/AM438x/AMIC110/AMIC120
- No Changes
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.