• Ti Cc2540 Usb Driver
• Usb Cc2540 Hid Driver
• Ti Cc2540 Usb Cdc

• BLE-STACK (Support for CC2540/CC2541) - Modified the PID in the driver.inf to match the PID of the dongle. Driver in C:Texas InstrumentsBLE-CC254x-1.4.2.2ComponentshaltargetCC2540USBusbdriver. Changed PID to 16B3 - Then did driver reinstall, pointing to above directory, got msg about unsigned drivers and it installed.
• TIDC-CC2540-BLE-USB — The CC2540 USB Dongle is a complete example of how to use the USB enabled Bluetooth Low Energy (BLE) Wireless MCU. The reference design can be used to enable Bluetooth Smart and Internet of Things applications on any system that contains a USB host.

DESCCC1111 = 'TI CC1111 USB CDC Serial Port' DESCCC2511 = 'TI CC2511 USB CDC Serial Port' DESCCC2531 = 'TI CC2531 USB CDC Serial Port' DESCCC2538 = 'TI CC2538 USB CDC Serial Port' DESCCC2540 = 'TI CC2540 USB CDC Serial Port' DESCCC2544 = 'TI CC2544 USB CDC Serial Port' DESCCCXXXXBL = 'TI CCxxxx Generic USB CDC Boot Loader' DESCREMOTINP.

• 3Analysis
• 4Protocol
  • 4.2Reading BLE frames

Status

At this point (2017-05-09), the status is:

• it is pretty clear which commands the default sniffer firmware understands
• I wrote a little test program to dump raw BLE frames
• there is no plugin for WireShark yet

Introduction

This page is about the CC2540 bluetooth low-energy sniffer dongle and getting it to work with Linux.A nice end result could be that it becomes possible to sniff directly in WireShark with this dongle.

I have such a 'WeBee' dongle that can be found for about E15,- on websites like Aliexpress.

It's supposedly a CC2540 (or compatible) dongle, the USB id is 0451:16b3.

Interesting links:

Analysis

USB descriptor

When plugging this stick into a Linux machine, you can see it uses only one bulk endpoint.

Reading the identification from the stick with the 0xC0 command, results in the following 8-byte response

You can recognise the 2540 type number in there.

USB logs from Windows

This USB device does actually work with Windows:

I've captured a log of the communication over USB while the BLE is capturing bluetooth traffic from some iBeacon, using USB pcap.

In the logs, I cannot see any firmware blobs being downloaded to the stick.Probably the stick comes with a pre-loaded firmware of itself to do the BLE sniffing.

The USB control transfer request codes seem to match up with the code in https://github.com/christianpanton/ccsniffer/blob/master/ccsniffer.py

• 0xC0, GET_IDENT: returns some kind of identifier
• 0xC5, SET_POWER
• 0xC6, GET_POWER
• 0xC9, no idea, this appears in my USB logs but I can't find it in the python code
• 0xD0, START
• 0xD1, STOP
• 0xD2, SET CHAN

Protocol

In the windows sniffer software, it seems there are only two things communicated:

• towards the stick: which radio channel to sniff, and some other radio settings
• from the stick: raw sniffed BLE frames

Configuring the radio

This appears to be done using USB control transfers.

The following requests are sent:

Request type 0x40 is a vendor-specific device request from host-to-device.Request type 0xC0 is a vendor-specific device request from device-to-host.

Reading BLE frames

This appears to be done using USB bulk input transfers.

I can see a lot of similarities between the USB log and the BLE sniffer log.

Each frame starts with a byte indicating the type of frame, following by two bytes indicating the length of the rest of the frame (encoded as little endian).

data frames

The bulk USB data starts off with two bytes indicating the length of the rest of the data.

In the example image on the right:

• 00: 0 means this is a data frame
• 31 00: length of rest of frame encoded in little endian = 49 bytes decimal
• 39 04 29 54: part of the time stamp
• 2c d6 be ..: data frame contents

unknown frames (tick or 'alive'?)

The stick also returns 4-byte frames, alternating between

and

Interpretation:

• 01: 1 means this is a frame of type 1
• 01 00: length of the rest of the frame encoded in little endian = 1 byte
• 40 or C0: unknown data byte

Software

Preliminary code can be found athttps://github.com/bertrik/cc2540

Ti Cc2540 Usb Driver

It connects to the dongle and dumps raw USB packets to stdout.

Usb Cc2540 Hid Driver

This software requires libusb-1.0-dev

Ti Cc2540 Usb Cdc