• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 32 subscribers
  • Views 1022 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR2944: SysConfig file cannot be opened on SysConfig tool

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

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.

[The SysConfig tool path]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\sysconfig_1.10.0

[The SysConfig file path]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\awr294x\mmw\mss\mss.syscfg

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, the SysConfig file included in the CCS project in the MMWAVE-MCUPLUS-SDK_04.02.00.02 can be opened on CCS, but not on the standalone and cloud versions of the SysConfig tool.

Best regards,

Daisuke

  • 0
    Guru 20215 points

    Hi,

    Another SysConfig file also cannot be opened on the standalone and cloud versions of the SysConfig tool.

    [The SysConfig file path]C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\awr294x\mmw\dss\dss.syscfg

    Each of the SysConfig files cannot be opened even when added to a new CCS project.

    [Path of each SysConfig file]
    C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\awr294x\mmw\
    dss\dss.syscfg
    mss\mss.syscfg

    How to open the SysConfig files included in the out-of-box mmWave demo on the SysConfig tool?

    Best regards,

    Daisuke

  • 0 in reply to Daisuke Maeda
    TI__Expert 8275 points

    Hi Mr. Daisuke,

                            To open the syscfg files of demo. I would request you to please select: TI SysConfig (shortcut) available at C:\ti\mmwave_mcuplus_sdk_04_02_00_02\sysconfig_1.10.0. This opens up a dialog box of SysConfig.

                              From this window select browse and select dss.syscfg available at C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\awr294x\mmw\dss\dss.syscfg. You should have been able to open dss.syscfg using this procedure. Let me know if you have faced any issues here (because its working fine for me).

                              For mss.syscfg I had faced some issues as mentioned by you. So there is a temporary fix you could follow for this. In mss.syscfg replace the file header comments as shown below in green colour:

                             Also, remove/delete the lines of code highlighted in red below:

                             Then you should follow the same procedure as mentioned (similar to dss.syscfg) for opening the mss.syscfg file.

                              Let me know if you still face issues or you have doubts regarding this.

    Thanks and Regards,

    Akshay.     

  • 0 in reply to Akshay Kumar Chandrasekaran
    Guru 20215 points

    Hi Akshay-san,

    Thank you for your reply.

    The dss.syscfg cannot be opened with the procedure you said.

    The mss.syscfg cannot be opened even with the changes you said.

    Attached is the modified mss.syscfg file:

    Fullscreen mss.syscfg.txt Download 
    /**
 * 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 "AWR294X" --package "ETS" --part "Default" --context "r5fss0-0" --product "MCU_PLUS_SDK_AWR2944@08.01.00"
 * @versions {"tool":"1.10.0+2163"}
 */

/**
 * Import the modules used in this configuration.
 */
const flash      = scripting.addModule("/board/flash/flash", {}, false);
const flash1     = flash.addInstance();
const adcbuf     = scripting.addModule("/drivers/adcbuf/adcbuf", {}, false);
const adcbuf1    = adcbuf.addInstance();
const cbuff      = scripting.addModule("/drivers/cbuff/cbuff", {}, false);
const cbuff1     = cbuff.addInstance();
const crc        = scripting.addModule("/drivers/crc/crc", {}, false);
const crc1       = crc.addInstance();
const edma       = scripting.addModule("/drivers/edma/edma", {}, false);
const edma1      = edma.addInstance();
const edma2      = edma.addInstance();
const ipc        = scripting.addModule("/drivers/ipc/ipc");
const uart       = scripting.addModule("/drivers/uart/uart", {}, false);
const uart1      = uart.addInstance();
const uart2      = uart.addInstance();
const clock      = scripting.addModule("/kernel/dpl/clock");
const debug_log  = scripting.addModule("/kernel/dpl/debug_log");
const mpu_armv7  = scripting.addModule("/kernel/dpl/mpu_armv7", {}, false);
const mpu_armv71 = mpu_armv7.addInstance();
const mpu_armv72 = mpu_armv7.addInstance();
const mpu_armv73 = mpu_armv7.addInstance();
const mpu_armv74 = mpu_armv7.addInstance();
const mpu_armv75 = mpu_armv7.addInstance();
const mpu_armv76 = mpu_armv7.addInstance();
const mpu_armv77 = mpu_armv7.addInstance();
const mpu_armv78 = mpu_armv7.addInstance();
const enet_cpsw  = scripting.addModule("/networking/enet_cpsw/enet_cpsw", {}, false);
const enet_cpsw1 = enet_cpsw.addInstance();

/**
 * Write custom configuration values to the imported modules.
 */
flash1.$name                  = "CONFIG_FLASH0";
flash1.peripheralDriver.$name = "CONFIG_QSPI0";

adcbuf1.$name = "CONFIG_ADCBUF0";

cbuff1.$name = "CONFIG_CBUFF0";

crc1.$name = "CONFIG_CRC0";

edma1.$name                             = "CONFIG_EDMA0";
edma1.instance                          = "EDMA_DSS_B";
edma1.regionId                          = 0;
edma1.edmaRmDmaCh[0].resourceType       = scripting.forceWrite("ownDmaCh");
edma1.edmaRmDmaCh[0].$name              = "CONFIG_EDMA_RM0";
edma1.edmaRmDmaCh[0].startIndex         = 0;
edma1.edmaRmDmaCh[0].endIndex           = 63;
edma1.edmaRmQdmaCh[0].$name             = "CONFIG_EDMA_RM1";
edma1.edmaRmTcc[0].$name                = "CONFIG_EDMA_RM2";
edma1.edmaRmTcc[0].startIndex           = 0;
edma1.edmaRmTcc[0].endIndex             = 63;
edma1.edmaRmParam[0].$name              = "CONFIG_EDMA_RM3";
edma1.edmaRmParam[0].startIndex         = 0;
edma1.edmaRmReservedDmaCh[0].$name      = "CONFIG_EDMA_RM4";
edma1.edmaRmReservedDmaCh[0].startIndex = 0;
edma1.edmaRmReservedDmaCh[0].endIndex   = 0;

ipc.r5fss0_1     = "NONE";
ipc.vringNumBuf  = 1;
ipc.vringMsgSize = 1152;

uart1.$name           = "CONFIG_UART1";
uart1.baudRate        = 852272;
uart1.intrEnable      = "DISABLE";
uart1.UART.$assign    = "UARTB";
uart1.UART.RX.$used   = false;
uart1.UART.TX.$assign = "ball.A14";

uart2.$name           = "CONFIG_UART0";
uart2.UART.$assign    = "UARTA";
uart2.UART.RX.$assign = "ball.B16";
uart2.UART.TX.$assign = "ball.C16";

edma2.$name                        = "CONFIG_EDMA1";
flash1.peripheralDriver.edmaConfig = edma2;
edma2.edmaRmDmaCh[0].$name         = "CONFIG_EDMA_RM5";
edma2.edmaRmQdmaCh[0].$name        = "CONFIG_EDMA_RM6";
edma2.edmaRmTcc[0].$name           = "CONFIG_EDMA_RM7";
edma2.edmaRmParam[0].$name         = "CONFIG_EDMA_RM8";
edma2.edmaRmReservedDmaCh[0].$name = "CONFIG_EDMA_RM9";

debug_log.enableLogZoneError   = false;
debug_log.enableLogZoneWarning = false;

mpu_armv71.$name        = "CONFIG_MPU_REGION0";
mpu_armv71.attributes   = "Device";
mpu_armv71.allowExecute = false;

mpu_armv72.$name = "CONFIG_MPU_REGION1";
mpu_armv72.size  = 14;

mpu_armv73.$name    = "CONFIG_MPU_REGION2";
mpu_armv73.baseAddr = 0x80000;
mpu_armv73.size     = 14;

mpu_armv74.$name    = "CONFIG_MPU_REGION3";
mpu_armv74.baseAddr = 0x10200000;
mpu_armv74.size     = 20;

mpu_armv75.$name        = "CONFIG_MPU_REGION4";
mpu_armv75.baseAddr     = 0x102E0000;
mpu_armv75.size         = 16;
mpu_armv75.attributes   = "NonCached";
mpu_armv75.allowExecute = false;

mpu_armv76.$name        = "CONFIG_MPU_REGION5";
mpu_armv76.baseAddr     = 0xC5000000;
mpu_armv76.size         = 13;
mpu_armv76.attributes   = "NonCached";
mpu_armv76.allowExecute = false;

mpu_armv77.$name        = "CONFIG_MPU_REGION6";
mpu_armv77.baseAddr     = 0xA4030000;
mpu_armv77.size         = 12;
mpu_armv77.attributes   = "NonCached";
mpu_armv77.allowExecute = false;

mpu_armv78.$name      = "CONFIG_MPU_REGION7";
mpu_armv78.baseAddr   = 0x88000000;
mpu_armv78.size       = 21;
mpu_armv78.attributes = "Cached+Sharable";

enet_cpsw1.$name                 = "CONFIG_ENET_CPSW0";
enet_cpsw1.phyToMacInterfaceMode = "RGMII";
enet_cpsw1.phyAddr1              = 0;

/**
 * Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
 * version of the tool will not impact the pinmux you originally saw.  These lines can be completely deleted in order to
 * re-solve from scratch.
 */
flash1.peripheralDriver.QSPI["0"].$suggestSolution = "ball.U11";
flash1.peripheralDriver.QSPI["1"].$suggestSolution = "ball.V11";
flash1.peripheralDriver.QSPI["2"].$suggestSolution = "ball.T11";
flash1.peripheralDriver.QSPI["3"].$suggestSolution = "ball.R12";
flash1.peripheralDriver.QSPI.$suggestSolution      = "QSPI0";
flash1.peripheralDriver.QSPI.CLK.$suggestSolution  = "ball.R10";
flash1.peripheralDriver.QSPI.CS.$suggestSolution   = "ball.U12";
enet_cpsw1.MDIO.$suggestSolution                   = "MDIO0";
enet_cpsw1.MDIO.DATA.$suggestSolution              = "ball.T5";
enet_cpsw1.MDIO.CLK.$suggestSolution               = "ball.R4";
enet_cpsw1.RGMII.$suggestSolution                  = "RGMII0";
enet_cpsw1.RGMII.RD0.$suggestSolution              = "ball.V6";
enet_cpsw1.RGMII.RD1.$suggestSolution              = "ball.V4";
enet_cpsw1.RGMII.RD2.$suggestSolution              = "ball.V5";
enet_cpsw1.RGMII.RD3.$suggestSolution              = "ball.U10";
enet_cpsw1.RGMII.RCTL.$suggestSolution             = "ball.T7";
enet_cpsw1.RGMII.RCLK.$suggestSolution             = "ball.T9";
enet_cpsw1.RGMII.TD0.$suggestSolution              = "ball.U7";
enet_cpsw1.RGMII.TD1.$suggestSolution              = "ball.U5";
enet_cpsw1.RGMII.TD2.$suggestSolution              = "ball.U6";
enet_cpsw1.RGMII.TD3.$suggestSolution              = "ball.U4";
enet_cpsw1.RGMII.TCTL.$suggestSolution             = "ball.R6";
enet_cpsw1.RGMII.TCLK.$suggestSolution             = "ball.V3";

    Best regards,

    Daisuke

  • +1 in reply to Daisuke Maeda
    TI__Genius 15046 points

    Hi Daisuke-san,

    I could open the mss.syscfg you had shared on my end. Could you post a screenshot of the home page dropdown menu in sysconfig? It should look something like this:

    As a workaround, there is also an alternative way to open up syscfg files from the GUI by using the following CLI command:

    C:/ti/sysconfig_1.10.0/nw/nw C:/ti/sysconfig_1.10.0 --product C:/ti/mmwave_mcuplus_sdk_04_02_00_01/mcu_plus_sdk_awr294x_08_01_00_34/.metadata/product.json --device AWR294X --context r5fss0-0 --part Default --package ETS --output generated/  <syscfg_file_path_name.syscfg>

    Could you try using this and see it it works?

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Guru 20215 points

    Hi Aayush-san,

    Thank you for your reply.

    Attached is a screenshot of the dropdown menu in the SysConfig tool.

    The workaround you indicated worked fine.

    C:/ti/mmwave_mcuplus_sdk_04_02_00_02/sysconfig_1.10.0/nw/nw C:/ti/mmwave_mcuplus_sdk_04_02_00_02/sysconfig_1.10.0 --product C:/ti/mmwave_mcuplus_sdk_04_02_00_02/mcu_plus_sdk_awr294x_08_01_01_06/.metadata/product.json --device AWR294X --context r5fss0-0 --part Default --package ETS --output generated/ C:/ti/mmwave_mcuplus_sdk_04_02_00_02/mmwave_mcuplus_sdk_04_02_00_02/ti/demo/awr294x/mmw/mss/mss.syscfg

    C:/ti/mmwave_mcuplus_sdk_04_02_00_02/sysconfig_1.10.0/nw/nw C:/ti/mmwave_mcuplus_sdk_04_02_00_02/sysconfig_1.10.0 --product C:/ti/mmwave_mcuplus_sdk_04_02_00_02/mcu_plus_sdk_awr294x_08_01_01_06/.metadata/product.json --device AWR294X --context c66ss0 --part Default --package ETS --output generated/ C:/ti/mmwave_mcuplus_sdk_04_02_00_02/mmwave_mcuplus_sdk_04_02_00_02/ti/demo/awr294x/mmw/dss/dss.syscfg

    Best regards,

    Daisuke

  • +1 in reply to Daisuke Maeda
    TI__Expert 8275 points

    Hi Daisuke-san,

                            Thanks for confirmation that workaround suggested by Aayush worked. Can you please let me know if this ticket can be closed if your query is resolved?

    Regards,

    Akshay.

  • 0 in reply to Akshay Kumar Chandrasekaran
    Guru 20215 points

    Hi Akshay-san,

    Thank you for your reply.

    It would be preferable to open the SysConfig files on the GUI of the SysConfig tool, but that was also resolved by another thread suggestion for AM2732.

    e2e.ti.com/.../am2732-sysconfig-file-cannot-be-opened-on-sysconfig-tool

    It seems 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.

    For mss.syscfg:
    * @cliArgs --device "AWR294X" --package "ETS" --part "Default" --context "r5fss0-0" --product "MCU_PLUS_SDK_AWR2944@08.01.01"

    For dss.syscfg
    * @cliArgs --device "AWR294X" --package "ETS" --part "Default" --context "c66ss0" --product "MCU_PLUS_SDK_AWR2944@08.01.01"

    Best regards,

    Daisuke

  • +1 in reply to Daisuke Maeda
    TI__Genius 15046 points

    Hi Daisuke-san,

    I noticed in your sysconfig dropdown screenshot that the version of MCU+ SDK installed on your machine is 8.01.01 instead of 8.01.0. Could you retry Akshay's suggestion in the earlier post and use --product "MCU_PLUS_SDK_AWR2944@08.01.01" instead?

    Edit: I just noticed that you have already tried this and it solved the issue.

    Regards,

    Aayush