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.

UNIFLASH: Uniflash Cannot read property "DS" of undefined

Part Number: UNIFLASH
Other Parts Discussed in Thread: MSP432E401Y

Hi,

I started getting this error in all versions of Uniflash whenever is needs to use the debugger.  Do you have a debug version that can show what's wrong?

Regards,

-Mike

13:38:24:273 log - NWAgentAPI: dinfraConfigue resolved successfully.
13:38:25:009 debug - session service: load()
13:38:25:051 error - {}
13:38:25:074 error - {}
13:38:25:094 error - {}
13:38:25:097 error - {}
13:38:25:133 error - {}
13:38:25:138 error - {}
13:38:25:175 error - {}
13:38:25:187 error - {}
13:38:25:190 error - {}
13:38:25:201 error - {}
13:38:25:204 error - {}
13:38:25:208 error - {}
13:38:25:211 error - {}
13:38:26:065 error - {}
13:38:26:073 error - {}
13:38:26:081 error - {}
13:38:26:140 error - {}
13:38:26:422 error - {}
13:38:27:514 error - {}
13:38:27:537 debug - ufDS, session.configured, partnum of current session = msp432e401y
13:38:27:537 debug - ufDS, session.configured, partnum of current session = msp432e401y
13:38:27:540 error - {}
13:38:27:561 error - {}
13:38:27:684 debug - addTargetStateListener on CORTEX_M4_0
13:38:27:737 error - {}
13:38:39:727 debug - returning new configure
13:39:11:372 error - socket error
13:39:11:373 error - configure failed: undefined
13:39:11:373 error - {}
13:39:11:373 error - Cannot read property 'DS' of undefined
13:42:32:665 error - {}
13:42:32:668 error - {}
13:42:38:949 debug - returning new configure
13:42:38:949 error - socket error
13:42:38:949 error - configure failed: undefined
13:42:38:949 error - {}
13:43:00:160 debug - returning new configure
13:43:00:160 error - socket error
13:43:00:161 error - configure failed: undefined
13:43:00:161 error - {}
13:43:00:161 error - Cannot read property 'DS' of undefined
13:43:20:142 debug - returning new configure
13:43:20:142 error - socket error
13:43:20:143 error - configure failed: undefined
13:43:20:143 error - {}
13:43:20:143 debug - returning new configure
13:43:20:143 error - socket error
13:43:20:143 error - Cannot read property 'DS' of undefined
13:43:20:144 error - configure failed: undefined
13:43:20:145 error - {}
13:45:11:713 error - {}
13:45:11:715 error - {}

  • Hello Mike,

    Which processor are you using Uniflash to program?

    Regards,

    Nick

  • Hi Nick,

    I have an MSP432E401Y and an XDS110 Debug Probe.  I can't get a ds.log file from it.

    Regards,

    -Mike

  • Hello Mike,

    I am sending your thread to the MSP team. Please ping the thread if they do not reply in a day or so.

    Regards,

    Nick

  • Hi Mike,

    Have you tried running Uniflash in Administrator mode or tried other connection methods? This seems to be a UniFlash issue as it spans other devices, here is a similar thread that could help with different debugging issues. Cannot read property 'DS' of undefined. Also making sure that UniFlash is the most updated version could help.

    Regards,

    Luke

  • Hi Luke,

    I've tried your suggestions without resolve.  Is DS some kind of background server task?  If so can we run it from a command line with some kind of verbose output?

    -Regards,

    -Mike

  • Mike,

    Let's see if we can get to the bottom of what is going on.

    Based on your initial post am I correct to understand that this was working fine before and then stopped working?

    Which version of UniFlash are you running?

    Do you also happen to have Code Composer Studio installed?  If so is it able to connect and load the program ok?

    Regards,

    John

  • Hi John,

    It was working before.  I've tried going back to older revisions with the same result.  I'm currently running uniflash_sl.6.4.0.3394.  Code Composer CCS10.4.0.00006_win64 still works. Also the Standalone Command Line utility is working.

    Regards,

    -Mike

  • Mike,

    Those are the latest versions.  It seems like something is blocking the UniFlash browser-based GUI from communicating with the backend.  The command-line utility uses the backend directly.  I will see if I can loop in our UniFlash expert to dig into more.

    Regards,

    John

  • In talking with our UniFlash expert that "socket error" is concerning and likely means that something is blocking communication between the GUI and debug server.

    Could you give the cloud version a quick try to see if it has the same problem.

    It can be accessed here: https://dev.ti.com/uniflash

    The GUI looks the same.

    Do you know what security software you have installed?  Maybe it logs what it is blocking and we can try to tell it that the processes used by UniFlash are trusted.

    Regards,

    John

  • John,

    I tried the cloud version yesterday and it had the same result.  Is the socket local ,outbound or both?  Will a blocked outbound connection cause this issue?  Just need to know what to focus on.

    Regards,

    -Mike

  • Mike,

    It is a local socket.  ws://127.0.0.1

    Could there have been an IT change that started blocking unsecure sockets?

    Regards,

    John

  • John,

    I see no activity in the security software logs.  I have a feeling the server is failing to start. Can I run it manually as a test?  The dslite.bat utility works that's in the Uniflash folder.

    Regards,

    -Mike

  • Mike,

    Let me try to pull in some others to debug further.

    John

  • Mike,

    We have a couple of things to try.

    First let's see if the cloudagent can start up the server.

    Open a command prompt.

    Then go to <uniflash install dir>/TICloudAgentHostApp

    run ticloudagent.bat

    What does it output?  It should show a port, version and buildversion.

    Next we can edit the ticloudagent.bat to enable some logging.  Remove the comment from lines 3 and 4 to enable logging.  THis should generate a my_ticld.log in your temporary directory.  Could you attach that?

    Regards,

    John

  • Hi John,

    Here are the results.

    C:\ti\uniflash_6.4.0\TICloudAgentHostApp>ticloudagent.bat
    4{"port":1138,"version":"4.11","buildVersion":"3394"}

    Regards,

    -Mike

    2021-10-07T18:09:04.938Z: main_chrome: Staring directory = C:\ti\uniflash_6.4.0\TICloudAgentHostApp\src
    2021-10-07T18:09:04.990Z: Starting Agent!
    2021-10-07T18:09:05.003Z: Module( Agent )->Web socket server started!
    2021-10-07T18:09:25.373Z: Overridden Proxy = 
    2021-10-07T18:09:26.013Z: Discovered Module : DeviceDetector
    2021-10-07T18:09:26.074Z: Discovered Module : DS
    2021-10-07T18:09:26.139Z: Discovered Module : EventBroker
    2021-10-07T18:09:26.248Z: Discovered Module : File
    2021-10-07T18:09:26.309Z: Failed to load module : rex_redirect.js : Error: Cannot find module '../../../../tirex4/ti-rex-core/cloud-agent-module'
        at Function.Module._resolveFilename (module.js:547:15)
        at Function.Module._load (module.js:474:25)
        at Module.require (module.js:596:17)
        at require (internal/module.js:11:18)
        at Object.<anonymous> (C:\ti\uniflash_6.4.0\TICloudAgentHostApp\src\modules\rex_redirect.js:3:19)
        at Module._compile (module.js:652:30)
        at Object.Module._extensions..js (module.js:663:10)
        at Module.load (module.js:565:32)
        at tryModuleLoad (module.js:505:12)
        at Function.Module._load (module.js:497:3)
    2021-10-07T18:09:26.373Z: rov_server_redirect: looking in: C:\ti\eclipse\dropins
    2021-10-07T18:09:26.379Z: rov_server_redirect: looking in: C:\ti\eclipse\plugins
    2021-10-07T18:09:26.384Z: rov_server_redirect: looking in: C:\ti\eclipse\Eclipse.app\Contents\Eclipse\dropins
    2021-10-07T18:09:26.391Z: rov_server_redirect: looking in: C:\ti\eclipse\Eclipse.app\Contents\Eclipse\plugins
    2021-10-07T18:09:26.397Z: Failed to load module : rov_server_redirect.js : Error: rov_server.js was not found (this is expected in cloud)
        at Object.<anonymous> (C:\ti\uniflash_6.4.0\TICloudAgentHostApp\src\modules\rov_server_redirect.js:65:11)
        at Module._compile (module.js:652:30)
        at Object.Module._extensions..js (module.js:663:10)
        at Module.load (module.js:565:32)
        at tryModuleLoad (module.js:505:12)
        at Function.Module._load (module.js:497:3)
        at Module.require (module.js:596:17)
        at require (internal/module.js:11:18)
        at module_1.createModule.then (C:\ti\uniflash_6.4.0\TICloudAgentHostApp\src\host_agent.js:23:42)
        at <anonymous>
    2021-10-07T18:09:27.853Z: Discovered Module : Serial
    2021-10-07T18:09:27.914Z: Discovered Module : TargetSupport
    2021-10-07T18:09:27.981Z: Discovered Module : USB
    2021-10-07T18:09:28.228Z: Discovered Module : USB-HID
    2021-10-07T18:09:28.235Z: Agent main module running on port 21047
    2021-10-07T18:09:28.240Z: len=
    2021-10-07T18:09:28.246Z: 5
    2021-10-07T18:09:28.252Z: buf=
    2021-10-07T18:09:28.257Z: {"port":21047,"version":"4.11","buildVersion":"3394"}
    

  • It is starting up ok from what I can tell.  The rex_redirect and rov_server errors are fine as we are running from UniFlash and not CCS.

    Odd that the port number is different in the log than the console.  Maybe those were from different runs?

  • It was different runs. One before the batch file change and then after the change. I'm starting to wonder if it is a java issue. IT has been scrubbing computers because of the license change with java, though other java dependent tools continue to work. Another thought is configuration settings. I noticed Uniflash picks up old settings after uninstalling all the Uniflash installs then re-installing.  How do we purge out anything related to Uniflash?  Registry settings, temp files etc...  The thought here is that it uses some corrupted settings value.

  • Are you open to doing a webex?  We could try to setup something for tomorrow.

    Regards,

    John

  • Anytime after 12PM EST.

  • Doesn't look like we were able to get something that works for today.  Hopefully the time Ruben booked for Tuesday works.  Monday is a holiday for us as we are in Canada.

    John

  • For anyone else following this thread we were able to work around this issue by adjusting the timeout for connecting to the server in module.js.  In the setTimeout increase the value at the end to 100000

    We believe the underlying issue is that security software is causing a delay in the server starting up.  The GUI would them timeout in trying to connect.

    Regards,

    John