Support for Windows 7 ended on January 14, 2020

1. Cc2540 Driver Windows
2. Ti Cc2540
3. Cc2540 Driver Arduino
4. Cc2540 Driver Windows 7 64-bit
5. Cc2540 Driver Windows 7 32-bit

We recommend you move to a Windows 10 PC to continue to receive security updates from Microsoft.

Cc2uart - node-cc2540. Node.js support for the TI CC2540 UART service. The CC2540 is programmable so there is no guarantee this works with all boards with the CC2540 chip. This module is built on noble so it should work where ever noble works. See also nrfuart if using the nRF8001 or nRF51822 chip. Tested configurations. Where do I find the model number (SKU)? The model number starts with three letters, hyphen and then followed by 3-4 digits for example CTH-690. It uses a Texas Instruments CC2540 SoC. We’d love to see a follow-up that does away with the Arduino in lieu of code running on the TI chip. Windows VMs, And HTTPS Everywhere 3 Comments The. Welcome to the PC Matic Driver Library, the internet's most complete and comprehensive source for driver information. Drivers Library. To find the latest driver for your computer we recommend running our Free Driver Scan. TI CC2540 USB CDC Serial Port (COM3) - Driver Download. Vendor: Texas Instruments. Product: TI CC2540 USB CDC.

You can have Windows automatically download recommended drivers and detailed information for your hardware and devices. This is a good way to make sure all your hardware and devices work properly.

Drivers and information

Windows can find and download two kinds of updates for devices connected to your computer:

• Drivers. A driver is software that allows your computer to communicate with hardware devices. Without drivers, the devices you connect to your computer—for example, a mouse or external hard drive—won't work properly. Windows can automatically check if there are drivers available for new devices that you connect to your computer.
  For hardware that you've connected to your computer in the past, updated drivers might become available at a later date; but those drivers aren't installed automatically. To install these optional updates, go to Windows Update in Control Panel, check for updates, and then view and install driver updates that are available for your computer.

• Information. Windows can download high-resolution icons for many hardware devices that you connect to your computer, along with detailed information about them, such as product name, manufacturer, and model number—even detailed information about the sync capabilities of a device. These details can make it easier for you to distinguish between similar devices that are connected to your computer, such as different mobile phones.

To have Windows automatically download recommended drivers and icons

You can check Windows Update at any time to see if it found new drivers and icons for your hardware, especially if you recently installed a new device. If you want to have Windows Update automatically check for the latest drivers and icons, here's how:

1. Open Devices and Printers by clicking the Start button , and then, on the Start menu, clicking Devices and Printers.

2. Right-click the name of your computer, and then click Device installation settings.

3. Click Yes, do this automatically (recommended), and then click Save changes. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

If Yes is already selected, click Cancel to close the dialog box.

To turn on and configure Windows Update

To get all important and recommended updates for your computer and your devices, make sure that Windows Update is turned on and configured properly.

To install drivers and other optional updates from Windows Update

Even if you have Windows Update set to automatically download and install all important and recommended updates, you still might not be getting all of the updated drivers available for your devices. For instance, optional updates might include updated drivers that become available for hardware or devices you've already installed. Windows doesn't automatically download and install optional updates, but you will be notified when optional updates are available.

To get all the available updates for your devices, periodically check Windows Update for all available updates, including optional updates. You can review the available updates and then select them from the list of updates that Windows finds for your computer. Here's how to do this:

1. Open Windows Update by clicking the Start button . In the search box, type Update, and then, in the list of results, click Windows Update.

2. In the left pane, click Check for updates, and then wait while Windows looks for the latest updates for your computer.

3. If there are any available updates, click the link in the box under Windows Update to see more information about each update. Each type of update might include drivers.

4. On the Select the updates you want to install page, look for updates for your hardware devices, select the check box for each driver that you want to install, and then click OK. There might not be any driver updates available.

5. On the Windows Update page, click Install updates. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

Notes:

• Windows Update tells you if an update is important, recommended, or optional.

• Some updates require you to restart your computer.

• Windows Update will tell you if the updates were successfully installed.

If Windows can't find a driver for your device

It's best to let Windows install drivers automatically. Occasionally, Windows might not be able to find a driver for your device. If this happens, you might want to check the manufacturer's website for a driver or update for the device, or try installing any software that came with the device.

If Windows can't find information about your device in Device Stage

Device Stage is a new feature in this version of Windows that displays details about a device and tasks you can perform with that device. When you connect a device that's compatible with Device Stage to your computer, Device Stage will automatically open. Occasionally, Device Stage might open but not display any or all tasks and information about the device. Here are some reasons why that might happen, and what to do if it does:

Note: If you connect a device to your computer that reportedly supports Device Stage (but only AutoPlay opens), check with the manufacturer of the device. Find out if there are any software or firmware updates available that will make the device work with Device Stage, and confirm that the device actually supports Device Stage.

• Device Stage might need your permission to download information about your device. Check to see if there's a message in Device Stage telling you that updated information is available, and then follow the instructions.

• Your computer might not be connected to the Internet. Device Stage can't download information about your device if you're offline. Try connecting the device later when you're online.

• Device Stage might be trying to download information about your device. Wait a few minutes and see if Device Stage is able to find the information, especially if this is the first time you've connected the device to your computer. Device Stage will keep trying to download information about your device, even if the location where that information is stored is busy. If you don't want to wait, try connecting the device again later.

Starting with Windows 10, release 1703, a USB Audio 2.0 driver is shipped with Windows. It is designed to support the USB Audio 2.0 device class. The driver is a WaveRT audio port class miniport. For more information about the USB Audio 2.0 device class, see https://www.usb.org/documents?search=&type%5B0%5D=55&items_per_page=50.

The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.

The driver will identify in device manager as 'USB Audio Class 2 Device'. This name will be overwritten with a USB Product string, if it is available.

The driver is automatically enabled when a compatible device is attached to the system. However, if a third-party driver exists on the system or Windows Update, that driver will be installed and override the class driver.

Architecture

usbaudio2.sys fits within the wider architecture of Windows USB Audio as shown.

Related USB specifications

The following USB specifications define USB Audio and are referenced in this topic.

• USB-2 refers to the Universal Serial Bus Specification, Revision 2.0
• ADC-2 refers to the USB Device Class Definition for Audio Devices, Release 2.0.
• FMT-2 refers to the Audio Data Formats specification, Release 2.0.

The USB-IF is a special interest group that maintains the Official USB Specification, test specifications and tools.

Audio formats

The driver supports the formats listed below. An alternate setting which specifies another format defined in FMT-2, or an unknown format, will be ignored.

Type I formats (FMT-2 2.3.1):

• PCM Format with 8..32 bits per sample (FMT-2 2.3.1.7.1)
• PCM8 Format (FMT-2 2.3.1.7.2)
• IEEE_FLOAT Format (FMT-2 2.3.1.7.3)

Type III formats (FMT-2 2.3.3 and A.2.3):

• IEC61937_AC-3
• IEC61937_MPEG-2_AAC_ADTS
• IEC61937_DTS-I
• IEC61937_DTS-II
• IEC61937_DTS-III
• TYPE_III_WMA

Feature descriptions

This section describes the features of the USB Audio 2.0 driver.

Audio function topology

The driver supports all entity types defined in ADC-2 3.13.

Each Terminal Entity must have a valid clock connection in compatible USB Audio 2.0 hardware. The clock path may optionally include Clock Multiplier and Clock Selector units and must end in a Clock Source Entity.

The driver supports one single clock source only. If a device implements multiple clock source entities and a clock selector, then the driver will use the clock source that is selected by default and will not modify the clock selector’s position.

A Processing Unit (ADC-2 3.13.9) with more than one input pin is not supported.

An Extension Unit (ADC-2 3.13.10) with more than one input pin is not supported.

Cyclic paths in the topology are not allowed.

Audio streaming

The driver supports the following endpoint synchronization types (USB-2 5.12.4.1):

• Asynchronous IN and OUT
• Synchronous IN and OUT
• Adaptive IN and OUT

For the asynchronous OUT case the driver supports explicit feedback only. A feedback endpoint must be implemented in the respective alternate setting of the AS interface. The driver does not support implicit feedback.

There is currently limited support for devices using a shared clock for multiple endpoints.

For the Adaptive IN case the driver does not support a feedforward endpoint. If such an endpoint is present in the alternate setting, it will be ignored. The driver handles the Adaptive IN stream in the same way as an Asynchronous IN stream.

The size of isochronous packets created by the device must be within the limits specified in FMT-2.0 section 2.3.1.1. This means that the deviation of actual packet size from nominal size must not exceed +/- one audio slot (audio slot = channel count samples).

Descriptors

An audio function must implement exactly one AudioControl Interface Descriptor (ADC-2 4.7) and one or more AudioStreaming Interface Descriptors (ADC-2 4.9). A function with an audio control interface but no streaming interface is not supported.

The driver supports all descriptor types defined in ADC-2, section 4. The following subsections provide comments on some specific descriptor types.

Class-Specific AS interface descriptor

For details on this specification, refer to ADC-2 4.9.2.

An AS interface descriptor must start with alternate setting zero with no endpoint (no bandwidth consumption) and further alternate settings must be specified in ascending order in compatible USB Audio 2.0 hardware.

An alternate setting with a format that is not supported by the driver will be ignored.

Each non-zero alternate setting must specify an isochronous data endpoint, and optionally a feedback endpoint. A non-zero alternate setting without any endpoint is not supported.

The bTerminalLink field must refer to a Terminal Entity in the topology and its value must be identical in all alternate settings of an AS interface.

The bFormatType field in the AS interface descriptor must be identical to bFormatType specified in the Format Type Descriptor (FMT-2 2.3.1.6).

For Type I formats, exactly one bit must be set to one in the bmFormats field of the AS interface descriptor. Otherwise, the format will be ignored by the driver.

To save bus bandwidth, one AS interface can implement multiple alternate settings with the same format (in terms of bNrChannels and AS Format Type Descriptor) but different wMaxPacketSize values in the isochronous data endpoint descriptor. For a given sample rate, the driver selects the alternate setting with the smallest wMaxPacketSize that can fulfill the data rate requirements.

Type I format type descriptor

For details on this specification, refer to FMT-2 2.3.1.6.

The following restrictions apply:

Class-Specific AS isochronous audio data endpoint descriptor

For details on this specification, refer to ADC-2 4.10.1.2.

The MaxPacketsOnly flag in the bmAttributes field is not supported and will be ignored.

The fields bmControls, bLockDelayUnits and wLockDelay will be ignored.

Class requests and interrupt data messages

The driver supports a subset of the control requests defined in ADC-2, section 5.2, and supports interrupt data messages (ADC-2 6.1) for some controls. The following table shows the subset that is implemented in the driver.

Cc2540 Driver Windows

Additional information on the controls and requests is available in the following subsections.

Ti Cc2540

Clock source entity

For details on this specification, refer to ADC-2 5.2.5.1.

At a minimum, a Clock Source Entity must implement Sampling Frequency Control GET RANGE and GET CUR requests (ADC-2 5.2.5.1.1) in compatible USB Audio 2.0 hardware.

The Sampling Frequency Control GET RANGE request returns a list of subranges (ADC-2 5.2.1). Each subrange describes a discrete frequency, or a frequency range. A discrete sampling frequency must be expressed by setting MIN and MAX fields to the respective frequency and RES to zero. Individual subranges must not overlap. If a subrange overlaps a previous one, it will be ignored by the driver.

A Clock Source Entity which implements one single fixed frequency only does not need to implement Sampling Frequency Control SET CUR. It implements GET CUR which returns the fixed frequency, and it implements GET RANGE which reports one single discrete frequency.

Clock selector entity

For details on this specification, refer to ADC-2 5.2.5.2

The USB Audio 2.0 driver does not support clock selection. The driver uses the Clock Source Entity which is selected by default and never issues a Clock Selector Control SET CUR request. The Clock Selector Control GET CUR request (ADC-2 5.2.5.2.1) must be implemented in compatible USB Audio 2.0 hardware.

Feature unit

For details on this specification, refer to ADC-2 5.2.5.7.

The driver supports one single volume range only. If the Volume Control GET RANGE request returns more than one range, then subsequent ranges will be ignored.

The volume interval expressed by the MIN and MAX fields should be an integer multiple of the step size specified in the RES field.

If a feature unit implements single channel controls as well as a master control for Mute or Volume, then the driver uses the single channel controls and ignores the master control.

Additional Information for OEM and IHVs

OEMs and IHVs should test their existing and new devices against the supplied in-box driver.

There is not any specific partner customization that is associated with the in-box USB Audio 2.0 driver.

This INF file entry (provided in a update to Windows Release 1703), is used to identify that the in-box driver is a generic device driver.

The in-box driver registers for the following compatible IDs with usbaudio2.inf.

See the USB audio 2.0 specification for subclass types.

USB Audio 2.0 Devices with MIDI (subclass 0x03 above) will enumerate the MIDI function as a separate multi-function device with usbaudio.sys (USB Audio 1.0 driver) loaded.

The USB Audio 1.0 class driver registers this compatible ID with wdma_usb.inf.

And has these exclusions:

An arbitrary number of channels (greater than eight) are not supported in shared mode due to a limitation of the Windows audio stack.

IHV USB Audio 2.0 drivers and updates

For IHV provided third party driver USB Audio 2.0 drivers, those drivers will continue to be preferred for their devices over our in-box driver unless they update their driver to explicitly override this behavior and use the in-box driver.

Audio Jack Registry Descriptions

Starting in Windows 10 release 1703, IHVs that create USB Audio Class 2.0 devices having one or more jacks have the capability to describe these jacks to the in-box Audio Class 2.0 driver. The in-box driver uses the supplied jack information when handling the KSPROPERTY_JACK_DESCRIPTION for this device.

Jack information is stored in the registry in the device instance key (HW key).

The following describes the audio jack information settings in the registry:

<tid> = terminal ID (As defined in the descriptor)

<n> = Jack number (1 ~ n).

Convention for <tid> and <n> is:

• Base 10 (8, 9, 10 rather than 8, 9, a)
• No leading zeros
• n is 1-based (first jack is jack 1 rather than jack 0)

For example:

T1_NrJacks, T1_J2_ChannelMapping, T1_J2_ConnectorType

For additional audio jack information, see KSJACK_DESCRIPTION structure.

These registry values can be set in various ways:

• By using custom INFs which wrap the in-box INF for the purpose to set these values.

• Directly by the h/w device via a Microsoft OS Descriptors for USB devices (see example below). For more information about creating these descriptors, see Microsoft OS Descriptors for USB Devices.

Microsoft OS Descriptors for USB Example

Cc2540 Driver Arduino

The following Microsoft OS Descriptors for USB example contains the channel mapping and color for one jack. The example is for a non-composite device with single feature descriptor.

The IHV vendor should extend it to contain any other information for the jack description.

Troubleshooting

If the driver does not start, the system event log should be checked. The driver logs events which indicate the reason for the failure. Similarly, audio logs can be manually collected following the steps described in this blog entry. If the failure may indicate a driver problem, please report it using the Feedback Hub described below, and include the logs.

For information on how to read logs for the USB Audio 2.0 class driver using supplemental TMF files, see this blog entry. For general information on working with TMF files, see Displaying a Trace Log with a TMF File.

For information on 'Audio services not responding' error and USB audio device does not work in Windows 10 version 1703 see, USB Audio Not Playing

Feedback Hub

If you run into a problem with this driver, collect audio logs and then follow steps outlined in this blog entry to bring it to our attention via the Feedback Hub.

Driver development

Cc2540 Driver Windows 7 64-bit

This USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft.

Cc2540 Driver Windows 7 32-bit

See also