• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 40 subscribers
  • Views 669 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.

TI UniFlash 7 now always fails with "Cannot read property 'DS' of undefined"

Christoph Schweers
Intellectual 475 points
Other Parts Discussed in Thread: UNIFLASH

I use TI UniFlash in a corporate network behind a proxy server to flash C2000 micro controller. In all UniFlash versions I've used, there is a bug that prevents this.

After pressing the "Load image" button, the error "Cannot read property 'DS' of undefined" occurs after a few seconds and the process is aborted. However, there is an annoying workaround. After all network connections have been switched off, the utility works as expected.

But this behaviour has now changed. With version 7 of UniFlash the error "Cannot read property 'DS' of undefined" always occurs, regardless of the state of the computer's network connection :-(

Is there any other tool available to flash TI micro controller via JTAG? Or may I hope that TI will try to fix this issue in the near future?

  • 0
    TI__Guru**** 161575 points

    Christoph,

    Can you try the workaround mentioned at the end of this thread to see if it helps in your case.

    https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1039804/uniflash-uniflash-cannot-read-property-ds-of-undefined/3848357?tisearch=e2e-sitesearch&keymatch=Cannot%2520read%2520property#3848357

    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.

    The file is in <UniFlash install dir>/TICloudAgentHostApp/src/

    I believe UniFlash 7.0 already increased this value from 1000 to 60000 but maybe it is not enough on this machine, or it could be that the connection is completely blocked.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 475 points

    Hi John,

    thank you for the answer. I changed the value from 60000 to 100000 and also 1000000 as recommended, but as soon as I press the "Load image" button, the error appears immediately again. 
    Best regards
    Christoph
  • 0 in reply to Christoph Schweers
    TI__Guru**** 161575 points

    Christoph,

    Can you try enabling the 2 types of logging shown here (GUI logging, Debug Server):

    http://software-dl.ti.com/ccs/esd/uniflash/docs/v5_0/quick_start_guide/uniflash_quick_start_guide.html#defect-reporting-and-logging

    Then attempt to flash again and attach the logs.  I will get these to our UniFlash expert to look at.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 475 points

    Hi John,

    attached you will find GUI Logging file. I'm unable to provide the Debug Server Logging file because every time I enable this feature it is automatically disabled and I cannot find a 'ds.log' file on my drive.

    uniflash_gui_debug_log.sql
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    16:33:15:689 log - NWAgentAPI: dinfraConfigue resolved successfully.
    16:33:16:188 error - {}
    16:33:16:232 error - {}
    16:33:16:261 error - {}
    16:33:16:266 error - {}
    16:33:16:311 error - {}
    16:33:16:321 error - {}
    16:33:16:374 error - {}
    16:33:16:376 error - {}
    16:33:16:435 error - {}
    16:33:16:452 error - {}
    16:33:16:471 error - {}
    16:33:16:475 error - {}
    16:33:16:699 error - {"message":"Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.\r\nSetting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this\r\ncheck, but Node.js might not execute correctly. Any issues encountered on\r\nunsupported platforms will not be fixed."}
    16:33:16:699 error - {}
    16:33:18:312 error - {}
    16:33:18:322 error - {}
    16:33:18:437 error - {}
    16:33:19:010 error - {}
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Best regards

    Christoph

  • 0 in reply to Christoph Schweers
    TI__Guru**** 161575 points

    Christoph,

    What version of windows are you running?

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 475 points

    Windows 7 Professional

  • 0 in reply to Christoph Schweers
    TI__Guru**** 161575 points

    Christoph,

    I don't believe Windows 7 is compatible with the version of node.js that UniFlash 7 is using.  I will find out what the latest version of UniFlash you can use is.  It is likely 6.4 but I will confirm.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 161575 points

    Christoph,

    UniFlash 6.4 will work on Windows 7 fine.  For UniFlash 7 it is possible to use it from the command line but the GUI will not work as it uses a version of node.js that is not compatible with Windows 7.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 161575 points

    We also going to test a workaround that may enable the GUI to work.

  • 0 in reply to JohnS
    Intellectual 475 points

    Hi John,

    in a test with UniFlash 6.4 on my Windows 7 computer, this also does not work:

     

    uniflash_gui_debug_log_6_4.sql
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    15:54:33:597 log - NWAgentAPI: dinfraConfigue resolved successfully.
    15:54:33:996 error - {}
    15:54:34:035 error - {}
    15:54:34:071 error - {}
    15:54:34:077 error - {}
    15:54:34:139 error - {}
    15:54:34:168 error - {}
    15:54:34:249 error - {}
    15:54:34:252 error - {}
    15:54:34:264 error - {}
    15:54:34:303 error - {}
    15:54:34:327 error - {}
    15:54:34:331 error - {}
    15:54:37:316 error - {}
    15:54:37:319 error - {}
    15:54:37:452 error - {}
    15:54:38:159 error - {}
    15:54:40:670 error - socket error
    15:54:40:670 error - {}
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    A colleague has installed UniFlash 7.0 on his Windows 10 computer and the error also occurs here:

    uniflash_gui_debug_log_7_0.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    13:46:26:270 log - NWAgentAPI: dinfraConfigue resolved successfully.
    13:46:26:638 error - {}
    13:46:26:672 error - {}
    13:46:26:691 error - {}
    13:46:26:695 error - {}
    13:46:26:726 error - {}
    13:46:26:729 error - {}
    13:46:26:746 debug - session service: load()
    13:46:26:778 error - {}
    13:46:26:781 error - {}
    13:46:26:789 error - {}
    13:46:26:796 error - {}
    13:46:26:821 error - {}
    13:46:26:835 error - {}
    13:46:26:852 error - {}
    13:46:26:857 error - {}
    13:46:27:010 error - {}
    13:46:27:015 error - {}
    13:46:27:086 error - {}
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    and another thing I noticed in this context is that the system requirements for UniFlash 7.0 list Windows 7 as a supported OS.

    Best regards

    Christoph

  • 0 in reply to Christoph Schweers
    TI__Guru**** 161575 points

    Christoph,

    Windows 7 was supposed to be supported with UniFlash 7 but that is not currently the case.

    The new errors on both your machine and your colleague's Win10 machine are socket errors.  On the windows 7 machine running 6.4 can you try the workaround from my first reply to see if it helps.  I am not convinced that it will but it is worth a try.  I think we are going to have to pull in our UniFlash expert..

    In your first post you mentioned that old versions worked when internet is off.  Is that the same for 6.4?

    John

  • 0 in reply to JohnS
    Intellectual 475 points

    Hi John,

    I have increased the timeout tenfold, but unfortunately the error still occurs.

    Since the command line version seems to be a good alternative for me, I will also give it a try. Unfortunately, the "Panda Active Defense Solution" installed on my computer currently thinks it has to quarantine the "libusb-1.0.dll", so I won't be able to take care of it until next week.

    Thank you for your efforts and have a nice weekend.

    Christoph

  • 0 in reply to Christoph Schweers
    TI__Guru**** 161575 points

    If you disable internet access on the computer does that stop Panda from quarantining that file?  You mentioned that in the past you had to disable internet access to get UF to work.

    Anyway we can continue Monday.  Have a great weekend.

    John

  • 0 in reply to JohnS
    Intellectual 475 points

    Hi John,

    sorry for mixing up the discussion a bit with my last post. My last comment on Panda and "libusb-1.0.dll" has nothing to do with the bug discussed here. The short summary:

    - UniFlash 6.3 works when the network is disabled.

    - UniFlash 6.4 and UinFlash 7.0 does not work regardless of the state of the network

    Best regards
    Christoph
  • +1 in reply to Christoph Schweers
    TI__Genius 12515 points

    Christoph,

    1. Can you clarify if your latest results (UniFlash is working on 6.3 with network disabled, but 6.4 and 7.0 is not working) was done on your Windows 7 machine, or your colleague's Windows 10 machine?

    Looking at the change log between UniFlash 6.3 and 6.4, I'm surprised that there would be difference in behaviour for this case (There was only minor bug fixes included in 6.4, as well as content alignment with CCS 10.4).

    --

    2. We did update the nodejs version included in UniFlash 7.0, which caused the incompatibility issue with Windows 7. We are looking at updating the release notes to note this, and document the workaround (set the required environment variable) for users that are on Windows 7.

    --

    3. As for the issue with UniFlash not working with your network enabled; UniFlash GUI starts up a local websocket to communicate between the GUI and the backup. This allows us to align the implementation between our desktop and cloud based DevTools. I'm assuming this might be causing the issue with your IT policies, but I'm just speculating at this point. It seems weird that it would start working with the network disabled, as UniFlash GUI does not required network access, except to check if updates are available (which can be turned off in the settings).

    As noted, UniFlash CLI does not require node or websockets, so this is the recommended workaround for now until we can figure out what is causing the various issues.

    Thanks,

    Ricky

  • 0 in reply to Ricky Lau
    Intellectual 475 points

    Hi Ricky,

    on topic 1,  the main difference in the behaviour of 6.3. and 6.4. is the following:
    If the button 'Load Image' is pressed in the dialogue 'Select and Load Images', the dialogue 'Load Program, Please Wait...' appears under 6.3 and after a few seconds the error 'Cannot read property 'DS' of undefined' occurs.
    Under 6.4 (and also 7.0), however, the error 'Cannot read property 'DS' of undefined' occurs immediately after pressing the 'Load Image' button.

    on topic 3, the error occurs independently of the 'Check for updates on application startup' setting and I can confirm that the command line version works. Therefore I would agree with your analysis that this error is related to the websocket communication between GUI and backend.

    Best regards
    Christoph