• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 43 subscribers
  • Views 577 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**** 161130 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**** 161130 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 
    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 - {}
16:33:21:158 error - {}
16:33:21:207 error - {}
16:33:21:228 error - {}
16:33:21:288 error - {}
16:33:21:295 error - {}
16:33:21:308 error - {}
16:33:21:346 error - {}
16:33:21:372 error - {}
16:33:21:447 error - {}
16:33:21:494 error - {}
16:33:21:522 error - {}
16:33:21:543 error - {}
16:33:21:574 error - {}
16:33:21:594 error - {}
16:33:21:626 error - {}
16:33:21:647 error - {}
16:33:21:680 error - {}
16:33:21:724 error - {}
16:33:21:754 error - {}
16:33:24:762 error - {}
16:33:24:799 error - {}
16:33:24:924 error - {}
16:33:24:955 error - {}
16:33:25:748 error - {}
16:33:25:789 error - {}
16:33:25:814 error - {}
16:33:25:837 error - {}
16:33:26:981 error - {}
16:33:27:007 error - {}
16:33:28:234 error - {}
16:33:28:258 error - {}
16:33:28:283 error - {}
16:33:44:460 error - {}
16:33:44:515 error - {}
16:33:45:563 error - {}
16:33:45:588 error - {}
16:33:49:546 error - {}
16:33:49:569 error - {}
16:33:50:260 error - {}
16:33:50:282 error - {}
16:33:51:362 error - {}
16:33:51:498 error - {}
16:33:51:522 error - {}
16:33:55:548 error - {}
16:33:55:569 error - {}
16:33:57:779 error - {}
16:33:57:802 error - {}
16:34:00:849 error - {}
16:34:00:892 error - {}
16:34:00:914 error - {}
16:34:00:964 error - {}
16:34:01:042 error - {}
16:34:01:932 error - {}
16:34:01:952 error - {}
16:34:04:622 error - {}
16:34:04:645 error - {}
16:34:05:713 error - {}
16:34:06:012 error - {}
16:34:06:033 error - {}
16:34:06:266 error - {}
16:34:06:379 error - {}
16:34:06:383 error - {}
16:34:06:497 error - {}
16:34:06:519 error - {}
16:34:06:525 error - {}
16:34:06:583 error - {}
16:34:06:598 error - {}
16:34:06:599 error - {}
16:34:06:749 error - {}
16:34:06:754 error - {}
16:34:06:756 error - {}
16:34:06:999 error - {}
16:34:07:006 error - {}
16:34:08:594 error - {}
16:35:30:348 error - {}
16:35:30:350 error - {}
16:36:25:050 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:36:34:962 debug - Target Configuration. Device: f280049, Connection: TIXDS2XXUSB_Connection, LP: false
16:36:35:330 debug - ufDS, session.configured, partnum of current session = tms320f280049
16:36:35:401 debug - addTargetStateListener on C28xx_CPU1
16:36:35:518 error - {}
16:40:27:993 debug - AddQuickSetting. id: Flash Bank 0, type: category, core: C28xx_CPU1
16:40:34:354 debug - AddQuickSetting. id: FlashC28Bank0Sector8, type: property, core: C28xx_CPU1
16:41:04:706 debug - session service: save()
16:46:06:528 error - {}
16:46:10:274 debug - returning new configure
16:46:10:274 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:46:10:279 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:46:10:279 error - {}
16:46:10:279 error - Cannot read property 'DS' of undefined
16:46:16:778 error - {}
16:46:16:780 error - {}
16:46:21:770 debug - returning new configure
16:46:21:770 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:46:21:771 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:46:21:771 error - {}
16:46:27:378 error - {}
16:46:27:380 error - {}
16:46:30:770 debug - returning new configure
16:46:30:770 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:46:30:771 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:46:30:771 error - {}
16:46:33:699 debug - returning new configure
16:46:33: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:46:33:701 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:46:33:701 error - {}
16:46:33:701 error - Cannot read property 'DS' of undefined
16:46:39:921 error - {}
16:46:39:923 error - {}
16:48:09:242 debug - returning new configure
16:48:09:242 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:48:09:242 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:48:09:242 error - {}
16:48:09:906 debug - returning new configure
16:48:09:906 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:48:09:906 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:48:09:906 error - {}
16:48:10:675 debug - returning new configure
16:48:10:676 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:48:10:676 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:48:10:676 error - {}
16:48:11:634 debug - returning new configure
16:48:11:634 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:48:11:634 error - configure failed: Node.js is only supported on Windows 8.1, Windows Server 2012 R2, or higher.
Setting the NODE_SKIP_PLATFORM_CHECK environment variable to 1 skips this
check, but Node.js might not execute correctly. Any issues encountered on
unsupported platforms will not be fixed.
16:48:11:634 error - {}

    Best regards

    Christoph

  • 0 in reply to Christoph Schweers
    TI__Guru**** 161130 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**** 161130 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**** 161130 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**** 161130 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 
    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 - {}
15:54:41:105 debug - session service: load()
15:54:41:106 error - {}
15:54:41:133 error - {}
15:54:41:155 error - {}
15:54:41:190 error - {}
15:54:41:245 error - {}
15:54:41:302 error - {}
15:54:41:373 debug - ufDS, session.configured, partnum of current session = tms320f280049
15:54:41:373 debug - ufDS, session.configured, partnum of current session = tms320f280049
15:54:41:378 error - {}
15:54:41:402 error - {}
15:54:41:639 debug - addTargetStateListener on C28xx_CPU1
15:54:41:716 error - {}
15:54:47:268 error - {}
15:54:47:275 error - {}
15:54:50:375 debug - returning new configure
15:54:50:375 error - socket error
15:54:50:376 error - configure failed: undefined
15:54:50:376 error - {}
16:11:39:620 debug - returning new configure
16:11:39:623 error - socket error
16:11:39:630 error - configure failed: undefined
16:11:39:631 error - {}
16:11:39:631 error - Cannot read property 'DS' of undefined
16:11:45:715 error - {}
16:11:45:718 error - {}
16:11:48:559 debug - returning new configure
16:11:48:559 error - socket error
16:11:48:560 error - configure failed: undefined
16:11:48:560 error - {}
16:11:51:061 debug - returning new configure
16:11:51:061 error - socket error
16:11:51:064 error - configure failed: undefined
16:11:51:064 error - {}
16:11:51:064 error - Cannot read property 'DS' of undefined
16:12:04:943 error - {}
16:12:04:945 error - {}

    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 
    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 - {}
13:46:28:109 error - {}
13:46:28:110 error - {}
13:46:28:229 error - {}
13:46:28:771 error - {}
13:46:30:479 debug - ufDS, session.configured, partnum of current session = tm4c123gh6pz
13:46:30:480 debug - ufDS, session.configured, partnum of current session = tm4c123gh6pz
13:46:30:484 error - {}
13:46:30:527 error - {}
13:46:30:696 error - socket error
13:46:30:743 debug - addTargetStateListener on CORTEX_M4_0
13:46:30:808 error - {}
13:46:50:672 debug - session service: load()
13:47:04:751 debug - session service: new()
13:47:04:844 error - socket error
13:47:04:852 error - {}
13:47:05:026 error - {}
13:47:05:229 error - {}
13:47:05:244 error - {}
13:47:05:274 error - {}
13:47:05:291 error - {}
13:47:05:307 error - {}
13:47:05:326 error - {}
13:47:05:788 error - {}
13:47:05:824 error - {}
13:47:07:832 debug - session service: load()
13:47:07:834 error - {}
13:47:07:858 error - {}
13:47:07:881 error - {}
13:47:07:907 error - {}
13:47:07:959 error - {}
13:47:08:033 debug - ufDS, session.configured, partnum of current session = tms320f280048
13:47:08:033 debug - ufDS, session.configured, partnum of current session = tms320f280048
13:47:08:154 debug - addTargetStateListener on C28xx_CPU1
13:47:08:180 error - {}
13:47:25:297 debug - returning new configure
13:47:25:297 error - socket error
13:47:25:300 error - configure failed: undefined
13:47:25:300 error - {}
13:47:25:300 error - Cannot read property 'DS' of undefined
13:47:30:973 error - {}
13:47:30:977 error - {}
13:47:40:233 debug - returning new configure
13:47:40:235 error - socket error
13:47:40:235 error - configure failed: undefined
13:47:40:235 error - {}
13:47:47:552 debug - returning new configure
13:47:47:553 error - socket error
13:47:47:554 error - configure failed: undefined
13:47:47:554 error - {}
13:47:47:554 error - Cannot read property 'DS' of undefined
13:47:54:555 error - {}
13:47:54:557 error - {}

    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**** 161130 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**** 161130 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 12045 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