• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 1345 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.

EK-TM4C1294XL: Virtual COM Port Not Installed for Device Port

Thomas Jacobson
Intellectual 310 points
Part Number: EK-TM4C1294XL

Hello community!

I'm using the EK-TM4C129XL eval board, trying to run the USB-dev-cserial example code. I'm able to load the code through the debug port without any trouble, and under the Device Manager, I can see the "Stellaris Virtual Serial Port" for the debug port. When I plug in the device USB port, however, I see the install window attempting to install the "Virtual COM Port." When it appears to have finished and I look in Device Manager, I don't see a new COM port. Instead, under "Universal Serial Bus controllers," I see a new "USB Composite Device" with the yellow warning symbol in the lower right corner.

I've tried installing the various .inf drivers under the "windows_drivers" folder, but it doesn't seem to help. I do get different results when I try to install using different versions of TivaWare_C_Series:

Version 2.1.0.12573 appears to install the drivers without any problems.

Version 2.1.1.71 fails to install with the message, "A problem was encountered while attempting to add the driver to the store."

Version 2.1.3.156 fails to install with the message, "The has for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering."

I'm hoping someone has an idea as to why I'm not getting the virtual COM port when I plug in to the device port on my eval board. I'm running Windows 8.1, with CCS 7.1.

Thanks for your time.

- Tom

  • 0
    TI__Guru*** 135355 points
    Hello Thomas,

    Have you tried with the latest drivers available here: software-dl.ti.com/.../SW-TM4C-2.1.4.178.PATCH-1.0.zip

    The issue with the composite example is known for Windows 10 and is being looked into actively, but this is the first I've heard of the issue occurring on Windows 8.1. Please let me know if the latest drivers are demonstrating the same problem for you on Windows 8.1.
  • 0 in reply to Ralph Jacobi
    Intellectual 310 points
    Hi Ralph,

    I was able to install the drivers you linked without any problems. However, I'm still getting the same USB Composite Device issue, where I get the yellow warning symbol and no COM port listed under the Ports section.

    If it helps, under the Problem status property for the Composite Device, it lists:

    {Operation Failed}The requested operation was unsuccessful.
    C0000001

    I usually associate the C0000001 with a null pointer, if that helps at all.

    Thanks for responding as quickly as you did!

    - Tom
  • 0 in reply to Thomas Jacobson
    TI__Guru*** 135355 points

    Hello Thomas,

    Thanks for confirming the issue exists with the latest driver as well. As mentioned, we are actively looking into this.

    One solution that has worked for some but not all is using an updated .c file as described in the following E2E post, I think it would be worth a try for you at least: e2e.ti.com/.../2268171

    Additionally, I have your post logged for follow-up when we find a final solution. Right now as all other reports came for Win 10, that is the current focus but as soon as we have that resolved I will provide you the latest update and we'll see if it also resolves the issue for Win 8.1.

  • 0 in reply to Ralph Jacobi
    Intellectual 310 points

    Hi Ralph,

    Thanks for the suggestion in the other forum post. I tried downloading the latest TivaWare C Series package (2.1.4.178), and I added the usbdcomp.c file (I didn't need to replace the file; there wasn't one there originally). Unfortunately, I got the same result as before, with the "USB Composite Device" with a warning symbol, and no new COM ports available.

    I appreciate the work your team has been doing to resolve this. Hopefully a Windows 10 fix will work for my machine as well

    - Thomas