• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 162 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.

SYSCONFIG: sysconfig dependencies

Daviel Almonte
Expert 3506 points

Part Number: SYSCONFIG

Hello, 

 

My customer cannot open any sysconfig version 1.24 or later. I assume that there may be some dependencies that are not up to date. What are the dependencies and versions needed to run sysconfig?

 

Thank you,

Daviel

  • 0
    TI__Guru**** 480731 points

    Hi Daviel,

    I assume the customer is referring to the standalone SysConfig GUI outside of CCS. What host OS are they using? And what device/SDK?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Expert 3506 points

    yes stand alone. 

    Windows and they are using it for the AM275 on SDK 11.1

  • 0 in reply to Daviel Almonte
    TI__Guru**** 480731 points

    Can you open a DOS command window and run:

    <SYSCONFIG INSTALL DIR>\nw\nw.exe "<SYSCONFIG INSTALL DIR>"

    Ex:

    > > C:\ti\sysconfig_1.24.0\nw\nw.exe "C:\ti\sysconfig_1.24.0"

    Does anything happen? Is there any output in the command window?

  • 0 in reply to Ki
    Prodigy 70 points

    Hi, thanks for the help.

    I tried this, there is no output and application does not launch.  Only version that launches is 1.23. I have 6 different versions in the ti directory.  Too many?

  • 0 in reply to Antoine Moarbes1
    TI__Guru**** 480731 points

    We have heard of similar issues in the past on some machines. One theory is that newer SysConfig versions come with a newer version of node that could be flagged by your security software for some reason.

    One thing to try:

    Take the node-webkit from a working version and drop it into the 1.24 version and see of that works. To do this, simply back up and copy the "nw" folders inside of the SysConfig installation and then try running SysConfig again (basically replace the nw folder in the non-working version like 1.24 with the one from 1.23.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    Thanks, this allows 1.24 to launch.

  • 0 in reply to Antoine Moarbes1
    TI__Guru**** 480731 points

    Thanks for trying. It seems to be related to another reported issue regarding the new version of node that is used by the newer sysconfig versions.

    One thing the customer can try is to see if disabling their security software will allow for the unmodified version 1.24 to run. If so, perhaps they can get an exemption for the node version with the issue. Otherwise they can continue to use the workaround of using the older node version.