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.

TDC1000-C2000EVM: EVM GUI does not find COM port

Part Number: TDC1000-C2000EVM
Other Parts Discussed in Thread: TUSB3410, , UNIFLASH, TDC1000

I believe that I am seeing pretty much exactly the same problem as posted by  in https://e2e.ti.com/support/sensors/f/1023/t/802806 , but after suggesting that the EVM firmware needed to be upgraded, that thread never included full instructions on how to actually do it.

In my particular case:

  • I am using a Windows 10 VM, but see the same behavior in Win7 and WinXP compatibility mode
  • I have installed the "Virtual COM Port Windows Driver" from here
  • All three of the expected LEDs on the EVM are lit up
  • I see the TUSB3410 show up in device manager with driver version 6.7.4.0
  • Device manager also shows a generic "Communications Port"
  • When I launch the EVM GUI, the "Serial Port" dropdown box includes the COM port corresponding to the generic "Communication Port" device, but not the COM port corresponding to the TUSB3410
  • I can re-assign the COM ports in device manager, and the EVM GUI continues to find only the port corresponding to the generic "Communication Port"

I'm very excited to try out the TDC1000-C2000EVM if I can ever connect to it!

Thanks

  • Neal,

    Let me look into this issue and get back with you by Monday.

  • , do you have any further guidance?

  • I think that I was able to update the firmware on the EVM via the following:

    * XDS110 Debug probe

    * TI cloud-hosted UniFlash utility

    * TDC1000_C2000_FW-v1.42-1MHz.hex (found under the "Firmware" subdirectory of the EVM GUI installation path)

    The UniFlash utility says that it successfully verified and loaded the firmware image. 

    However, I am still unable to connect to the EVM board from the GUI

  • I have installed everything on a Win7 VM and am seeing the same results as with Win10.  I am still unable to connect the GUI to the EVM.

  • Neal,

    Please do not run the GUI in compatible mode in Windows. And run it in WIndows 7 or XP.

    Let me know if the COM port does not see the USB port.

  • Bharat,

    I have tried this both in Windows 7 and Windows 10 with the same result.  

    In both cases, the TUSB3410 device shows up in the Device Manager, but the EVM GUI does not recognize the associated COM port.

    Neal

  • Neal,

    I am still looking into this issue, you seem to have followed all the instructions as in the TDC1000-C2000 User's Guide and still unable to launch the GUI.

    Please let me know if you connect the GUI to the communication port does it not communicate with the device ? Does the GUI say that you are unable to connect it ?

  • Neal,

    I too have a TDC1000-C2000EVM. It came fully programmed with the correct firmware and I did not have to reprogram the device useing and XDS110.

    That being said I was able to connect to the board using the GUI. My firmware version was 1.42 and my GUI revision was 1.2.0.83, what versions are you using? I am using a native Win 10 PC, no virtual machine.

    This might be a stupid question, but did you run the GUI after opening it? The first time I opened the GUI it did not automatically run. I had to click the Run arrow.

    Regards,
    Cody 

  • Cody and Bharat,

    When I connect the TDC1000-C2000EVM board to my windows 10 VM it shows up in Device Manager as shown below.  Note that the TUSB3410 is COM1 and some other generic device is COM4.

    When I first launch the EVM GUI, I immediately get the screen below telling me that the connection failed.

    What I find to be the most suspicious, is that when I go to the drop-down menu to select the desired serial port, COM1 does not show up at all.  The GUI is detecting that COM4 exists, but of course (since it's not the TI board at all) cannot connect to it either.

    Thanks

    Neal

  • I briefly hijacked my wife's work computer (I haven't owned a windows computer in nearly two decades) and was able to get the EVM GUI to connect to the EVM.  Her physical computer and my VM show the TUSB3410 exactly the same within Device Manager, but one works and the other doesn't.  Go figure....

    Cody, Thank you for your help confirming that the current version does indeed work on Win10 (when not virtualized).

    If either of you can point me towards documentation of the USB/serial protocol between the GUI and the C2000, I posted that as a separate question here.

  • I have procured a physical Win10 machine, but I am now getting the following error when I try to run the EVM GUI.

    "The VI is not executable. The full development version of LabVIEW is required to fix the errors."

  • Neal,

    Do you know the difference in the systems wherein you were able to install this GUI and the system wherein you get this error.

    The GUI was originally designed to work in Windows XP & 7 and it will require a full version of the LabVIew Run time engine.

  • Both machines are basic dell laptops with Windows10 installed.  In both cases, I installed the TUSB3410 driver and the TDC1000-C2000EVM GUI software with all default settings.

    I can re-steal my wife's laptop and do a more specific comparison of installed versions of things if anyone can tell me more specifically what I should be looking for.

  • I tried installing the EVM GUI on two other dell windows 10 laptops and it installed correctly on both.  

    I gave up on identifying what was wrong with the installation on the first laptop and switched to one of the other laptops.

    I am able to run the GUI and communicate with the EVM board now.  Thank you for your help.