This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-J721S2: SysConfig fails to open a .syscfg

Part Number: PROCESSOR-SDK-J721S2
Other Parts Discussed in Thread: SYSCONFIG, TDA4VL

Tool/software:

Hello,

I'm using SysConfig

Version: 1.20.0.3587
Release date: 02 Apr 2024
When I`m trying to open the .syscfg file found by default in the SDK ti-processor-sdk-rtos-j721s2-evm-09_02_00_05 the tool throws an error which states that the file is not supported and I need a newer version to open that.
The SysConfig tool is the latest available for download and the "check for updates" option doesn`t find any new updates to install.
What do I need to do to get my hands on a newer version or how do i use my version to open the .syscfg file?
I`m attaching a picture with the error.
 
  • Hi Alexandru,

    I am assuming that you are talking about the following file for the PinMux,

    <ti-processor-sdk-rtos-j721s2-evm-09_02_00_05>/pdk_j721s2_09_02_00_30/packages/ti/board/src/j721s2_evm/j721s2_evm_baseboard_pinmux.syscfg

    I have taken a look at the contents of this file, and this file was created during the early releases of J721S2 using SysConfig 1.9.0, and was not updated.

    /**
    * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
    * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
    * @cliArgs --device "J721S2_beta" --package "ALZ" --part "Default"
    * @versions {"data":"20211013","tool":"1.9.0+2015","templates":"20210927"}
    */

    The device name used by SysConfig has changed since 1.9.0 and so the newer version doesn't recognize the device.

    Please replace the device name J721S2_beta with the actual device name used by SysConfig 1.20.0 for this SoC, J721S2_TDA4VE_TDA4AL_TDA4VL_AM68x

    You should then be able to open this file. I recommend saving the syscfg file once the tool is opened, and use that for future usage.

    regards

    Suman

  • This solved the issue.

    Thank you!

    BR

    Alexandru Dadu