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.

CCS/TM4C129XNCZAD: TM4C129 device USB is not working

Part Number: TM4C129XNCZAD

Tool/software: Code Composer Studio

Hi,

We are using a Hub from microchip USB2512B. The Hub has one upstream to connected to PC and two downstream one used to the Cam and the other one is connected to TM4C129.

The cam is detected when we plug the USB cable to PC, and TM4C129 it is detected but not working (no data is going out/in)??

Please help, we need to re-spin the board asap. Thanks

Kind regards,

Mourad

  • Hello Mourad,

    I would like to help as fast as I can but you need to provide me a lot more detail to work with here.

    From your topic title, it sounds like the TM4C is in Device mode, is this correct?

    What mode is it in? CDC? Bulk? HID?

    What software is running on the device? If you started from a TI example project, tell me which one.

    Is this your first test with the system? Did you ever validate functionality with your BoosterPack?

    When you say detected, does it enumerate the USB port? Have you looked at the communication exchange to ensure the device has enumerated correctly? If it enumerates, have you seen what commands are sent back to request further comms?

    That may not be all the details I need to help, but those are the big ones I can think of to start, and further info you provide would be appreciated.
  • Hi Ralph,

    The TM4C is in device mode. The driver library function USBStackModeSet() has been tried with both eUSBModeForceDevice and eUSBModeDevice,.

     

    Our software implements a vendor specific HID device. It was originally based loosely on the TI example code in usbdhidkeyb.c but heavily modified.

    Our HID code works on an existing product developed with driver library version 2.0.1.11577.

    For this new product we have tried upgrading the Tiva driver library to 2.1.4.178 but have dropped back to developing with 2.0.1.11577 as we know

    our code definitely works with that version on the existing product.

     

    The device seems to enumerate OK with the correct device descriptor and string descriptors displaying on the PC using Microsoft’s usbview utility.

    The lower driver layers send three messages to our receive callback handler during enumeration: USB_EVENT_SUSPEND then USB_EVENT_CONNECTED then another USB_EVENT_SUSPEND.

     

    The host PC is running Windows 10 Pro.

    Regards,

    Mourad

  • Hello Mourad,

    That is a pretty old TivaWare and I have not worked with it before so that may result in some challenges. I would recommend using the latest version, what prompted the switch back? Did something else not work?

    Also that TivaWare was never tested on Windows 10, so that could be part of the issue.

    That the device enumerates okay makes me think the drivers are probably okay, but to be fully sure there isn't a driver problem, can you install the latest TivaWare USB drivers which were patched for WIndows 10? The download link is: software-dl.ti.com/.../SW-TM4C-2.1.4.178.PATCH-1.0.zip