• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 2785 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-TM4C123GXL: Stellaris ICDI Driver - Device Descriptor Failed

user5319984
Prodigy 50 points
Part Number: EK-TM4C123GXL

I received the launchpad last week from Mouser Electronics. I first installed the Keil IDE and connected the device's debug USB port to my Windows 10 laptop, but I received the following notification:

Moving to Windows Device Manager, I notice that the device is not recognized (device descriptor failed).

I installed the Stellaris drivers manually from TI's website, but that did not change the situation.

I then tried with the other ports of my laptop, with the same result. I tried with my desktop computer (also a Windows 10 system) and had the same result.

I then resorted to more advanced solutions, such as found on this website: 

But none of these attempts could remove the error. The Keil IDE doesn't find the device either when I attempt to download code.

I am coming down to the conclusion that the drivers are broken, rendering useless the TI T4MC123G device I purchased.

Do you have any solution for this problem I may have overlooked?

  • 0
    TI__Guru*** 135355 points

    Hello,

    I think you just need to install the correct drivers from TI website.

    The Stellaris ICDI drivers can be downloaded and installed from: http://www.ti.com/tool/STELLARIS_ICDI_DRIVERS

    And our latest USB drivers for USB applications on TM4C are: http://software-dl.ti.com/tiva-c/SW-TM4C/latest/exports/SW-TM4C-2.1.4.178.PATCH-1.0.zip

    See if the use of these solves your issue.

  • 0 in reply to Ralph Jacobi
    Prodigy 50 points
    First link is what I've been working with so far, and the basis of my first post.

    Latest driver from the second link displays the same behavior. If I update the unknown device from Windows Device Manager and load the new driver, Windows says that the best available driver for this device is already installed. Manually installing the driver from boot_usb.inf doesn't change anything either.

    Anything I may have overlooked? Otherwise, is TI willing to fix its broken Stellaris driver?
  • 0 in reply to user5319984
    TI__Guru*** 135355 points

    Hello,

    The latest drivers are not broken for Windows 10, we have hundreds of Win 10 users using them without issue (there was some signing problem a while back when it first came out, but those have long been resolved. I myself have a Windows 10 laptop and I have not had any issues with the latest drivers. Either the LaunchPad is the issue (occasional DOA happens) or there is a missing step.

    When you install the drivers, are you doing a manual installation by browsing for driver software directing Windows the download folder for the driver?

    Can you try to uninstall the driver that Windows automatically downloaded for it, and then try with a manual process?

    Lastly, you mention you plugged the USB cable into the debug port, have you

    1) Ensured the switch next to the port is set to "Debug"

    2) Tried a new USB Cable?

    I ask #2 because you'd be surprised how many times issues like this end up being due to the USB cable... so please do give that a try as well.

  • 0 in reply to Ralph Jacobi
    Prodigy 50 points

    The small USB adapter packaged with my Launch Pad causes this issue. Switching to a USB adapter of my own, I immediately noticed the appearance of the 3 USB devices (ICDI JTAG and such) in the Device Manager.

    Using the latest drivers (second link) to update the drivers would not do it, leaving them with the warning. However, the website drivers worked and I could debug the device with Keil.

    EDIT: I should probably thank you, this is not Stack Overflow after all. Your help was very valuable in troubleshooting this issue.

  • 0 in reply to user5319984
    Guru 117855 points

    user5319984 said:
    The small USB adapter packaged with my Launch Pad causes this issue.

    Pardon - do you (really) mean,  "USB Adapter?"     Are those "Adapters" not usually "Converters of some sort" - often (bi-directionally) converting UART CMOS/TTL Level Signals - to USB?

    Ralph advised you to, Switch USB Cables - which are (rarely) described as Adapters.      Would you be so good as to confirm that it was this CABLE REPLACEMENT (not Adapter) which resolved your issue?

  • 0 in reply to cb1_mobile
    Prodigy 50 points
    Hello cb1_mobile,

    I confirm it was question of a micro USB to USB type A adapter. This is the adapter packaged with the TM4C123GXL and one you would typically use for JTAG with this board.
  • 0 in reply to user5319984
    Guru 117855 points
    OK - good that - might you agree that a 'blend' of (both) our views describes a, 'Micro USB' to 'USB type A Adapter CABLE' best describes your solution?
  • 0 in reply to user5319984
    Guru 117855 points
    C'est bien - mercî. It would likely prove of Great Interest to Vendor here - if you'd be good enough to, "Ohm out" that failed cable - to try & determine which (assumed data lines) had: Opened, Shorted, Presented high resistance. (it is suspected that power DID reach your LPad...)