Drivers Ss Telecoms USB Devices

If your system has a device-side USB port, used in the peripheral side of the USB protocol, see the 'USB Gadget' framework instead. After choosing your HCD, then select drivers for the USB peripherals you'll be using. You may want to check out the information provided in usb/ and especially the links given in usb/usb-help.txt. To compile this driver as a module, choose M here: the module will be called usbcore. Option: USBUSS720. If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. After the device-specific driver is installed, Windows 10 will select that driver instead of the standard USB audio 2.0 driver when you first connect the device.

-->

The set of identifiers generated for USB devices depends on whether the device is a single-interface device or a multiple-interface device.

Single-Interface USB Devices

When a new USB device is plugged in, the system-supplied USB hub driver composes the following device ID by using information extracted from the device's device descriptor:

USBVID_v(4)&PID_d(4)&REV_r(4)

Where:

  • v(4) is the 4-digit vendor code that the USB committee assigns to the vendor.

  • d(4) is the 4-digit product code that the vendor assigns to the device.

  • r(4) is the revision code.

Telecoms

The hub driver extracts the vendor and product codes from the idVendor and idProduct fields of the device descriptor, respectively.

An INF model section can also specify the following hardware ID:

USBVID_v(4)&PID_d(4)

and the following compatible IDs:

USBCLASS_c(2)&SUBCLASS_s(2)&PROT_p(2)

Unknown usb device driver download

USBCLASS_c(2)&SUBCLASS_s(2)

USBCLASS_c(2)

Where:

  • c(2) is the device class code taken from the device descriptor.

  • s(2) is the device subclass code.

  • p(2) is the protocol code.

The device class code, subclass code, and protocol code are determined by the bDeviceClass, bDeviceSubClass, and bDeviceProtocol fields of the device descriptor, respectively. These are 2-digit numbers.

Multiple-Interface USB Devices

Devices with multiple interfaces are called composite devices. Starting with Windows 2000, when a new USB composite device is plugged into a computer, the USB hub driver creates a physical device object (PDO) and notifies the operating system that its set of child devices has changed. After querying the hub driver for the hardware identifiers associated with the new PDO, the operating system searches the appropriate INF files to find a match for the identifiers. If it finds a match other than USBCOMPOSITE, it loads the driver indicated in the INF file. However, if no other match is found, the operating system uses the compatible ID USBCOMPOSITE, for which it loads the USB Generic Parent driver. The Generic Parent driver then creates a separate PDO and generates a separate set of hardware identifiers for each interface of the composite device.

Each interface has a device ID of the following form:

USB VID_v(4)&PID_d(4)&MI_z(2)

Where:

  • v(4) is the 4-digit vendor code that the USB committee assigns to the vendor.

  • d(4) is the 4-digit product code that the vendor assigns to the device.

  • z(2) is the interface number that is extracted from the bInterfaceNumber field of the interface descriptor.

An INF model section can also specify the following compatible IDs:

USBCLASS_d(2)&SUBCLASS_s(2)&PROT_p(2)

USBCLASS_d(2)&SUBCLASS_s(2)

USBCLASS_d(2)

USBCOMPOSITE

Where:

  • d(2) is the device class code taken from the device descriptor.

  • s(2) is the subclass code.

  • p(2) is the protocol code.

The device class code, subclass code, and protocol code are determined by the bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol fields of the interface descriptor, respectively. These are 2-digit numbers.

Symptoms

If you quickly and repeatedly insert and remove a USB device, the USB port may stop responding. When the port is in this state, it no longer recognizes any USB device, and the USB device will not work.
This article helps you fix the problem.

Prerequisites

You must use administrative credentials to log on to Windows to perform some of the troubleshooting methods that are listed in this article. If this is your personal computer, you are likely already logged on with an administrator account. If this is a computer that is part of a network at work, you might have to ask the system administrator for help.

Resolution

To fix this problem, use the following methods in the order in which they are listed. After each method, check the USB device to see whether the problem is fixed. If the problem is not fixed, try the next method.
This article also includes a workaround that you can try if these methods do not work.

Method 1: Use Device Manager to scan for hardware changes

Use Device Manager to scan for hardware changes. After your computer scans for hardware changes, it might recognize the USB device that is connected to the USB port so that you can use the device.
To scan for hardware changes, follow these steps:

  1. Click Start, and then click Run.
    Note If you are running Windows Vista, click Start, and then use the Start Search box.

  2. Type devmgmt.msc, and then click OK. Device Manager opens.

  3. In Device Manager, click your computer so that it is highlighted.

  4. Click Action, and then click Scan for hardware changes.

  5. Check the USB device to see whether it is working.

If scanning for hardware changes fixed the problem, you are finished. If this method did not fix the problem, go to Method 2.

Method 2: Restart the computer

If scanning for new hardware did not fix the problem, try restarting the computer. After the computer has restarted, check the USB device to see whether it is working.
If restarting the computer fixed the problem, you are finished. If this method did not fix the problem, go to Method 3.

Method 3: Disable and re-enable the USB controller

Use Device Manager to disable and re-enable all the USB controllers. This lets the controllers recover the USB port from its unresponsive condition. The USB controllers represent the USB ports in Device Manager. If you are not comfortable with advanced troubleshooting, try the steps in the 'Workaround' section.
To disable and re-enable the USB controllers, follow these steps:

  1. Click Start, and then click Run.
    Note If you are running Windows Vista, click Start, and then use the Start Search box.

  2. Type devmgmt.msc, and then click OK. Device Manager opens.

  3. Expand Universal Serial Bus controllers.
    Note You might have to scroll down the list to find this item.

  4. Right-click the first USB controller under Universal Serial Bus controllers, and then click Uninstall to remove it.

  5. Repeat step 4 for each USB controller that is listed under Universal Serial Bus controllers.

  6. Restart the computer. After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB controllers that you uninstalled.

  7. Check the USB device to see whether it is working.

Drivers Ss Telecoms Usb Devices Download

If the USB port recognizes the device and if you can use the device, you are finished.
If this method fixed the problem, you are finished. If this method did not fix the problem, go to the 'Workaround' section.

Drivers Ss Telecoms USB Devices

Workaround

If none of these methods worked for you, you can disable the Selective Suspend feature. However, be aware that when the Selective Suspend feature is disabled, all USB host controller drivers (and therefore all USB ports and connected USB devices) in the system are affected. Therefore, your computer cannot suspend any USB devices that are connected to it, and the USB devices can continue to use power while connected to the computer. Additionally, the Allow the computer to turn off this device to save power check box does not appear on the Power Management tab for the USB Root Hub.
This section is intended for an advanced computer user.
You can disable the USB Selective Suspend feature as a workaround by editing the registry. The USB device may become unresponsive because of a race condition in the Selective Suspend feature. The Selective Suspend feature suspends the USB device to efficiently maintain battery power by enabling the computer to turn off the USB device. However, sometimes this feature may not correctly wake up the USB device. Therefore, the USB device is unresponsive when you try to use it.
You might want to disable this feature for server products where power management is not important or required.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

Drivers Ss Telecoms Usb Devices Wireless Adapter

322756 How to back up and restore the registry in WindowsTo disable the Selective Suspend feature, follow these steps:

Drivers Ss Telecoms Usb Devices Adapters

  1. Click Start, and then click Run.
    Note If you are running Windows Vista, click Start, and then use the Start Search box.

  2. Type regedit, and then click OK. Registry Editor opens.

  3. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESystemCurrentControlSetServicesUSB

  4. If the DisableSelectiveSuspend registry entry is present, double-click it. If it is not present, create the entry. To create the entry, follow these steps:

    1. On the Edit menu, point to New, and then click DWORD.

    2. Type DisableSelectiveSuspend, and then press ENTER.

    3. On the Edit menu, click Modify.

  5. In the Value data field, type 1 to disable the Selective Suspend feature, and then click OK.

Now go to the 'Did this fix the problem?' section.

Cause

This problem may occur because of a timing issue that prevents the computer from detecting the USB device.
Microsoft and the hardware vendors that manufacture the chips that are used for USB have investigated the problem. However, the results were inconclusive because of the intermittent nature of the problem.

Status

Microsoft is researching this problem and will post more information in this article when the information becomes available.