• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 298 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM2732: SysConfig file cannot be opened on SysConfig tool

Daisuke Maeda
Guru 19835 points
Part Number: AM2732
Other Parts Discussed in Thread: SYSCONFIG, MMWAVE-MCUPLUS-SDK

The SysConfig file included in the out-of-box mmWave demo cannot be opened on the SysConfig tool in the MMWAVE-MCUPLUS-SDK_04.02.00.02.

[Path of the SysConfig file]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\am273x\mmw\dss\dss.syscfg

[Path of the SysConfig tool]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\sysconfig_1.10.0

The cloud version of SysConfig tool also cannot open the SysConfig file.

How to open the SysConfig file on the SysConfig tool?

By the way, Another SysConfig file can be opened on both the standalone and cloud versions of the SysConfig tool.

[Path of the SysConfig file]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\am273x\mmw\mss\mss.syscfg

Best regards,

Daisuke

  • 0
    TI__Mastermind 27743 points

    Hi Daisuke,

    Can you please try below?

    Delete the older sysconfig versions and only keep latest and use new workspace to build the project. 

    Regards, Prasad

  • 0 in reply to Prasad Jondhale
    Guru 19835 points

    Hi Prasad-san,

    Thank you for your reply.

    I installed the latest SysConfig tool (v1.11.0) and retried, but got the same error message.

    Should older versions of the SysConfig tool be uninstalled?

    Does the project you said indicate the CCS project?

    There is no CCS project for the out-of-box (OOB) mmWave demo.

    The OOB demo is built by gmake on the command prompt, but the build fails if the SysConfig file is not in the default path.

    Best regards,

    Daisuke

  • +1 in reply to Daisuke Maeda
    TI__Guru 68160 points

    Hi Daisuke,

    Please edit dss.syscfg file as marked below and reopen in sysconfig GUI.

    /**
    * 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 "AM273x" --package "ZCE" --part "Default" --context "c66ss0" --product "MCU_PLUS_SDK_AM273x.evmAM273x@08.01.01"
    * @versions {"tool":"1.10.0+2163"}
    */

  • 0 in reply to Jitendra Gupta
    Guru 19835 points

    Hi,

    Thank you for your reply.

    I understand that the argument for MCU+ SDK in the header part in the SysConfig file is required to contain the corresponding device name and software version.

    Best regards,

    Daisuke