• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 567 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.

PROCESSOR-SDK-J784S4: SysConfig file error opening

Scott Brown
Prodigy 190 points
Part Number: PROCESSOR-SDK-J784S4
Other Parts Discussed in Thread: SYSCONFIG, TDA4VH

Tool/software:

Hi. I'm trying to open the sysconfig file located in the latest SDK (ti-processor-sdk-rtos-j784s4-evm-09_02_00_05/pdk_j784s4_09_02_00_30/packages/ti/board/src/j784s4_evm/j784s4_evm_pinmux.syscfg) however I get an error when opening the file in SysConfig 1.14, 1.17 and 1.20.

Are you able to tell me the correct SysConfig version or how to correctly open the config file?

Thanks,

Scott

  • 0
    Prodigy 190 points

    Selecting "Yes" then just raises another error that can't be dismissed:

  • 0 in reply to Scott Brown
    TI__Guru** 116625 points

    Hi Scott,

    What SDK version are you trying to use - 9.2 SDK or 8.6 SDK? Your text describes 9.2 SDK path, but your picture demonstrates 8.6 SDK.

    The comments header at the top of the file gives the details on the device name and the SysConfig Tool version used.

    /**
    * 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 "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH" --package "ALY" --part "Default"
    * @versions {"tool":"1.12.1+2446"}
    */

    The newer SysConfig versions have adjusted the device name, so you need to modify the file to just match the device name. The device name can be seen by dropping down on the Device List on a New design in the SysConfig tool.

    Please make adjustments as mentioned in a related thread for J721S2, PROCESSOR-SDK-J721S2: SysConfig fails to open a .syscfg 

    regards

    Suman

  • 0 in reply to Suman Anna
    Prodigy 190 points

    Hi Suman,

    Apologies, I tried multiple SDK versions just to be sure. It's v9.2 we are using.

    The public version of SysConfig 1.12 throws a different error that the device "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH" was not found (similar to the thread) and I can't see anything related to the J784s4 in the device list.

    The newer versions of SysConfig don't throw this error, instead they throw:
    "TypeError: Cannot set properties of undefined (setting '$assign')" and also "Error: Exception occurred calling scripting.suppress(): Unknown member: RGMII1_RXC" like in the screenshots, which suggests they are getting further into processing the config?

    Thanks,
    Scott

  • 0 in reply to Scott Brown
    TI__Guru** 116625 points

    Hi Scott,

    Scott Brown said:
    "TypeError: Cannot set properties of undefined (setting '$assign')" and also "Error: Exception occurred calling scripting.suppress(): Unknown member: RGMII1_RXC" like in the screenshots, which suggests they are getting further into processing the config?

    Yes, I am able to reproduce the error. There seems to be some mismatch in the data around the MCU CPSW2G. Commenting out this entry will allow you to open it with SysConfig 1.20.

    --- a/packages/ti/board/src/j784s4_evm/j784s4_evm_pinmux.syscfg
+++ b/packages/ti/board/src/j784s4_evm/j784s4_evm_pinmux.syscfg
@@ -1,7 +1,7 @@
 /**
  * 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 "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH" --package "ALY" --part "Default"
+ * @cliArgs --device "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH_AM69x" --package "ALY" --part "Default"
  * @versions {"tool":"1.12.1+2446"}
  */

@@ -531,6 +531,7 @@ iMCU_ADC1.AIN4.$assign                            = "ball.P34";
 iMCU_ADC1.AIN5.$assign                            = "ball.R37";
 iMCU_ADC1.AIN6.$assign                            = "ball.R33";
 iMCU_ADC1.AIN7.$assign                            = "ball.V38";
+/*
 const iMCU_CPSW2G1                                = scripting.addPeripheral("MCU_CPSW2G");
 iMCU_CPSW2G1.$name                                = "MyMCU_CPSW2G";
 iMCU_CPSW2G1.RGMII1_RD0.$assign                   = "ball.A35";
@@ -546,6 +547,7 @@ iMCU_CPSW2G1.RGMII1_TD3.$assign                   = "ball.E38";
 iMCU_CPSW2G1.RGMII1_TXC.$assign                   = "ball.E36";
 iMCU_CPSW2G1.RGMII1_TX_CTL.$assign                = "ball.C38";
 scripting.suppress("Solution may have changed,No suggested solution was provided, so this value may differ from the last time this tool was run", iMCU_CPSW2G1, "RGMII1_RXC");
+*/
 const iMCU_I2C1                                   = scripting.addPeripheral("MCU_I2C");
 iMCU_I2C1.$name                                   = "MyMCU_I2C0";
 iMCU_I2C1.$assign                                 = "MCU_I2C_0";
@@ -966,7 +968,7 @@ iGPIO_VDDSHV21.$suggestSolution          = "GPIO_0_VDDSHV2";
 iI2C5.$suggestSolution                   = "I2C_0";
 iJTAG_VDDSHV01.$suggestSolution          = "JTAG_VDDSHV0";
 iMCU_ADC1.$suggestSolution               = "MCU_ADC_0";
-iMCU_CPSW2G1.$suggestSolution            = "MCU_CPSW2G_0";
+/*iMCU_CPSW2G1.$suggestSolution            = "MCU_CPSW2G_0";*/
 iMCU_MDIO1.$suggestSolution              = "MCU_MDIO_0";
 iMCU_OSPI1.$suggestSolution              = "MCU_OSPI_0";
 iPCIE1.REFCLK_P_OUT.$suggestSolution     = "ball.AN9";

    You can then save back the file, after adding in the MCU_CPSW2G node back from SysConfig tool.

    regards

    Suman

  • +1 in reply to Suman Anna
    TI__Guru** 116625 points

    Hi Scott,

    Try the following simpler change, and you can open the file with SysConfig 1.20. You can then save the config file to update the syscfg file format.

    --- a/packages/ti/board/src/j784s4_evm/j784s4_evm_pinmux.syscfg
+++ b/packages/ti/board/src/j784s4_evm/j784s4_evm_pinmux.syscfg
@@ -1,7 +1,7 @@
 /**
  * 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 "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH" --package "ALY" --part "Default"
+ * @cliArgs --device "J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH_AM69x" --package "ALY" --part "Default"
  * @versions {"tool":"1.12.1+2446"}
  */

@@ -532,6 +532,7 @@ iMCU_ADC1.AIN5.$assign                            = "ball.R37";
 iMCU_ADC1.AIN6.$assign                            = "ball.R33";
 iMCU_ADC1.AIN7.$assign                            = "ball.V38";
 const iMCU_CPSW2G1                                = scripting.addPeripheral("MCU_CPSW2G");
+iMCU_CPSW2G1.$useCase                             = "RGMII";
 iMCU_CPSW2G1.$name                                = "MyMCU_CPSW2G";
 iMCU_CPSW2G1.RGMII1_RD0.$assign                   = "ball.A35";
 iMCU_CPSW2G1.RGMII1_RD1.$assign                   = "ball.B36";

    regards

    Suman

  • 0 in reply to Suman Anna
    Prodigy 190 points

    Hi Suman,

    This worked - thank you!

    Kind regards,
    Scott