The CC2540 USB Evaluation Module Kit contains one CC2540 Bluetooth low energy USB Dongle. The dongle can be used to enable Bluetooth low energy on your PC. It can also be used as a packet sniffer for analyzing the BLE protocol and for software and system level debugging (use the free tool SmartRF Packet Sniffer). BLE-CC254x-1.3.2-Usb2Usb-(V1.0-20140817) BLE CC2540 Serial Port USB passthrough source code.

Yes, we actually do have signed CDC drivers (or really signed.inf files) for the CC2531 (and our other USB devices). We distribute the drivers (and install them as well) with SmartRF Studio (see C: Program Files (x86) Texas Instruments SmartRF Tools drivers vcp), but I've attached the required files here for your convenience. USB CDC virtual UART (CC2540 only) More information on the HostTestRelease project can be found in the CC254x BLE Software Developer's Guide (http://www.ti.com/lit/pdf/swru271). If you think you might be experiencing a problem with the TI driver, you might try first testing whether the device can be recognized by other bluetooth-compatible devices. If it turns out the driver is the problem, since it is created by TI, you might also try looking on the TI forums to see if a work-around is already available.

Description

The CC2540 USB Evaluation Module Kit contains one CC2540 Bluetooth low energy USB Dongle. The dongle can be used to enable Bluetooth low energy on your PC. It can also be used as a packet sniffer for analyzing the BLE protocol and for software and system level debugging (use the free tool SmartRF Packet Sniffer). The dongle comes preprogrammed as a BLE host device monitor. To program and debug software running on the dongle, you need the CC Debugger or SmartRF05EB board (not included in the kit).

Download

NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

• 3 Hardware Overview
• 4 Software Overview
• 5Driver Features List
• 6References

This section is a quick guide on how to start using usb ports on TI platform with supplied pre-built binaries. Please refer to USB Quick Start

The USB User's Guide provides information about

• Overview of USB hardware and software
• Supported linux driver features for USB host and device mode of operation
• The Linux USB configuration through menuconfig. Please refer to USB configuration

USBSS Overview[edit]

• The USB subsystem includes

• Two instances of USB (Mentor Graphic's USB2.0 OTG) controllers. Each MUSB controller supports USB 1.1 and USB 2.0 standard.
• CPPI 4.1 compliant DMA controller sub-module with 30 RX and 30 TX simultaneous DMA channels
• CPPI 4.1 DMA scheduler
• CPPI Queue Manager module with 92 queues for queuing/dequeuing packets

• Interfaces to the CPU via 3 OCP interfaces

• Master OCP HP interface for the DMA (for data transfers)
• Master OCP HP interface for the Queue manager (to manage CPPI descriptors)
• Slave OCP MMR interface (for CPU to access USBSS/MUSB registers)

• Signals the standard Charge Pump (part of EVM BOM) for VBUS 5V generation

MUSB Controller Overview[edit]

The salient features of the MUSB USB2.0 OTG controller are:

• High/full speed operation as USB peripheral.
• High/full/low speed operation as Host controller.
• Compliant with OTG spec.
• 15 Transmit and 15 Receive Endpoints other than the mandatory Control Endpoint 0.
• Double buffering support in FIFO.
• Support for high bandwidth Isochronous transfer
• 32 Kilobytes of Endpoint FIFO RAM for USB packet buffering.
• Interfaced with CPPI4.1 DMA controller with 15 Rx and 15 Tx channels (for each usb controller).
• Defer interrupt enable feature is supported for each packet descriptor of cppi-dma.

Mentor graphics controller driver (or MUSB driver) [edit]

The MUSB driver is implemented on top of Mentor controller IP which supports all the speeds (High, Full and Low). AM33XX USBOTG subsytem uses CPPI 4.1 DMA for all the transfers. The musb driver conforms to linux usb framework and supports both PIO and DMA mode of operation. The musb host controller driver (HCD) binds the controller hardware to linux usb core stack. The musb device or gadget controller driver binds the controller hardware and specific gadget driver (filestorage, cdc/rndis etc).

Linux USB Stack Architecture [edit]

As shown in the figure, linux usb stack is a layered architecture, with musb controller at the lowest layer, the musb host/device controller driver binds the musb controller hardware to linux usb stack framework. The CPPI4.1 DMA controller driver is responsible for transmit/receive of packets over the musb endpoints.

• The Mentor USB driver can be built as module or built-in to kernel
• Support both PIO and DMA mode (The DMA mode not applicable for control endpoint)
• Support two instances musb controller in otg mode (both usb0 and usb1 controller in otg mode. This will allow host or device operation on each port simultaneously.

The driver supports the following features for USB Host (AM33XX)[edit]

The driver supports the following features for USB Gadget (AM33XX)[edit]

The driver supports the following features for Dual host/gadget (AM33xx)[edit]

Not verified features of AM33xx[edit]

Ti Cc2540 Usb Cdc Driver Free Download

• For more details about EVM, please refer to EVM reference manual.

USB Configuration through menuconfig [edit]

Driver Ti Cc2540 Usb Cdc -

• The Mentor USB driver can be built as module or built into kernel. For more information refer to USB Configuration

Driver Ti Cc2540 Usb Cdc Driver