• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 710 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: "usb_dev_cserial" Example Troubleshooting

EricScott18
Prodigy 60 points
Part Number: EK-TM4C1294XL


Hello all,

I am trying to get the example program "usb_dev_cserial" for the TM4C1294XL up and going. The program builds and runs successfully, I can see that the program makes it to the main while loop when I step through it. Though I am not seeing any output to the Stellaris Virtual Serial Port. I only see one virtual com port appear in my device manager, instead of the multiple com ports that are described in the project comments. I have applied the driver patch for Windows 10 already with out any change in behavior. Does any one know what behavior I should expect to see when running this application? Please let me know what information I can help provide to expedite troubleshooting. 

Thanks for your time,

Eric

  • 0
    TI__Guru*** 135355 points

    Hello Eric,

    This is a known issue with that specific TivaWare example when used on Windows 10. The belief is that the USB descriptors for the composite device is not recognized by Windows 10 (and possibly 8.1) properly compared to previous versions of Windows. It is an open issue still and will be addressed in the future.

    One solution that has worked for a minority of users 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: https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/463167/2268171#2268171

    If you need a CDC example without the Composite device portion, I can provide a working example for that in the meantime.

  • 0 in reply to Ralph Jacobi
    Prodigy 60 points
    Hi Ralph,
    Thanks for the additional information. I saw posts referencing that issue but I wasn't sure if I was running into the same problem. I tried that fix but it does not appear to have worked for me. I still only see one comm port come up, and the USB composite device associated with my board still has a yellow triangle over it in the device manager.

    If you wouldn't mind sharing your CDC example without the composite device, that would be much appreciated! What behavior should I expect from your example to confirm it is working properly?

    Best regards,
    Eric
  • 0 in reply to EricScott18
    TI__Guru*** 135355 points

    Hello Eric,

    Here is the CCS project (built in CCS v7): 0525.usb_dev_cdcserial.zip

    As far as behavior goes, the naming may vary depending how your Windows 10 enumerates the CDC port. For mine, it is named just 'USB Serial Device' under Ports (COM & LPT) in Device Manager. The main thing to look for is that a USB device is detected or installed when plugging in a cable to the Target USB side (not the debug side, which usually shows up as a Stellaris Virtual Port).

  • 0 in reply to Ralph Jacobi
    Prodigy 60 points
    Hi Ralph,
    Thanks for the help! The example project works! I was able to confirm that I saw a new COM port pop up when I plugged in my board. I then opened a serial connection through tera-term and was able to trip a break point within the interrupt when I sent data back to the board.

    Best regards,
    Eric