• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 903 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.

LAUNCHXL-F28377S: F28377S bulk device driver no longer works on windows 10 (x64)

Mario Hiti
Prodigy 110 points

Part Number: LAUNCHXL-F28377S

Hello!

I have created a USB interface that is derived form the example usb_dev_bulk which was working fine since march on windows 7,8 and 10. However ~4 weeks ago USB support stopped working on both of my devices that run on windows 10. 

I have disabled driver signature enforcement and reinstalled the drivers provided by controlSUITE and the newer c2000-ware-package. Neither seem to work.

What makes things even stranger is that the device is not even showing up as an unrecognized device in the windows 10 device manager. 

The XDS100 debug port and the USB serial port show up just fine.

  • 0
    TI__Mastermind 32995 points

    Hi,

    Please try the patch contained in this ZIP file provided by Lori Heustess.

    Let us know if this works and fixes the USB recognition and enumeration issue.

    Here it is as well...

    SW-TM4C-2.1.4.178.PATCH-1.0.zip

    sal

  • 0 in reply to Sal Pezzino
    Prodigy 110 points

    Hi Sal!

    Thank you for the signed driver. This one makes it easier for me to install the device on Windows 8 machines since is no longer have to disable driver signature enforcement.

    Unfortunately it does not resolve my issue for Windows 10...
    As mentioned above the device does not appear in the device manager. therefore i cannot install the driver by clicking on one of the devices. I can however install it using hdwwiz.exe. This leads to a device being listed but with error 10.
    I dug a little deeper into the problem by debugging the usb_dev_bulk example that comes with the c2000 ware package. Without any modifications to the example I am facing the same issues as in my project. Here are some odd things that I found out:
    - on windows 8 no USB device gets added until the device calls the function to initialize the USB system. Once called the OS acoustically indicates that something has been found and lists it in the device manager.
    - on win8 i can create an invalid device i.e. changing the clock speed. this leads to an unrecognized device bein listed in the manager
    - on win10 neither of those things happen. The USBDBulkInit() is called but nothing visible happens on the host side.
    - in example usb_dev_serial RxHandler() handles all incoming data. shortly after the init process is complete RxHandler() actually gets called which implies that the OS found something. However the event passed to the handler is always USB_EVENT_SUSPEND. This happen twice after a restart but at no other time.
    - I have also the same issue when using the usb_dev_serial amd the usb_dev_keyboard example

     


    Update: It turned out that the issue was hardware related.. We are using a custom breakout board in the lab for the devce and incidentally all devices there are running windows 8. For my desk PC i am using a modified cable to connect which turned out to be faulty. When I tried using the PCs of my colleagues (who  are also using win8) it obviously didnt work either..

  • 0 in reply to Mario Hiti
    TI__Mastermind 32995 points
    Mario,

    Thanks for the update. This happens sometimes. In the past we have run some electrical tests on our devices communicating USB, and we were failing the tests. Once we swapped the cable, everything was passing.

    A faulty cable may cause some serious issues. Throw that cable out!

    sal