• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 21 subscribers
  • Views 388 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.

Original question:

LMX2594: USB connection

LMX2594EVM: TICS Pro Unable to Connect to EVM

Derek Fronek
Prodigy 10 points
Part Number: LMX2594EVM
Other Parts Discussed in Thread: USB2ANY

I have a LMX2594EVM that I know works with the reference pro and can connect to a laptop successfully. I have been trying to connect the same setup to another computer and it keeps throwing the following error when I connect the reference pro to the computer.

 

I am running TICS Pro version 1.7.7.1 and have been able to use the USB2ANY firmware flasher to reflash the reference pro from the same computer that is unable to connect with TICS Pro. It appears that TICS Pro detects the reference pro but throws and error. I have also tried the previous version of TICS Pro but this did not work either. The laptop that is able to connect to the reference pro using TICS Pro did update the reference pro to version 2.7 we I first plugged it in. 

Suggestions on further steps would be appreciated. 

  • 0
    TI__Mastermind 33340 points

    We recently had to change the backend USB detection code to use the WMI event system on Windows. For a variety of reasons (mostly antivirus software), WMI is susceptible to corruption. This looks like a corrupted WMI database is preventing event checking.

    There's a quick way to check:

    1. From Win + R run tool, run wmimgmt.msc
    2. In the leftmost pane, right click "WMI Control (Local)" and select "Properties". This spawns a new properties pane.
    3. Look for any error messages in the properties. An example of an uncorrupted WMI and a corrupted WMI are included below.
    4. If your WMI looks like the right with "Invalid class" errors, run the following commands in an admin console to force recompilation of the WMI namespace DLLs:
      cd C:\Windows\System32\Wbem
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
for %i in (*.dll) do regSvr32 -s %i
net stop winmgmt /y
net start winmgmt
gpupdate /force

    If this doesn't fix the problem, we can try some other debug steps.

  • 0
    Prodigy 10 points

    Thank you for the help, I will try this over the weekend and report back if this solved the issue

  • 0 in reply to Derek Payne
    Prodigy 10 points

    I tried the above steps but it does not appear I have any invalid class errors. I went through the steps to recompile just in case but this did not have any effect. 

  • 0 in reply to Derek Fronek
    TI__Mastermind 33340 points

    Hmm, okay. My next guess is there's something wrong with how the USB2ANY is being initialized, but without more insight into the error message it's hard to say exactly what's going on. I'm going to build a version of the binary that produces more comprehensive error messages and provide it to you later today, along with patching instructions.

  • 0 in reply to Derek Payne
    Prodigy 10 points

    Is there any update to this? I am able to get by with the laptop but would appreciate being able to connect this to the test computer desktop going forward. Thanks

  • 0 in reply to Derek Fronek
    TI__Mastermind 33340 points

    Hi, apologies for the delay - I finally managed to get time to build a new TICS Pro version (1.7.7.2) which should be available on the web within the next hour. I don't think it will resolve the issue yet, but it will give us more clues - it should now dump a stack trace to a file, C:\Program Files (x86)\Texas Instruments\TICS Pro\ErrorLog.txt (or something similar), whenever a traceable exception is thrown (such as the one you're encountering).

    Can you try installing 1.7.7.2, triggering the error, and sending me the corresponding stack trace in the errorlog file?