• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 2619 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.

CC2540EMK-USB: How to use CC2540 USB dongle as a common USB device?

yi xia
Prodigy 20 points
Part Number: CC2540EMK-USB
Other Parts Discussed in Thread: CC2540, , BLE-STACK

Recently I bought a CC2540 USB dongle from TI official website: http://www.ti.com/tool/cc2540emk-usb.

We need to use this device to connect to PC and then communicate with my company’s device (which already has a CC2540 module inside).

When the new USB dongle is inserted into the PC, and driver (SWRC212a.zip) is installed, we can see the device is identified as

Cebal controlled devices

CC2540 USB dongle

 

Problem is we need the Windows 10 (64bit) assign a COMM port number, because our own PC application needs a port number to point the dongle device to transmit/receive data.

 

My guess is the driver maybe wrong although it works when we use an older version dongle (Rev1.0.1). By the way, the new dongle version is Rev1.1.2.

  • 0
    TI__Guru** 105180 points
    Hello,

    The default firmware on the CC2540USB dongle is for the TI Packet Sniffer tool. To reprogram the firmware with the Host Test network processor, you need to download the BLE-Stack SDK v1.4.2.2 and follow the steps from the "CC2540 USB Evaluation Kit Quick Start Guide" available on the CC2540EMK-USB link above.

    Please note that this dongle is not a BLE Controller, and must be interfaced with SW developed to the TI Vendor Specific HCI Guide, included in the BLE-Stack SDK.

    Best wishes
  • 0 in reply to JXS
    Prodigy 20 points

    Hi JXS,

    Thanks for your reply at first.

    As you said, the default firmware on the CC2540 USB dongle is for the TI Packet Sniffer tool, I tried this process too, but there is still not a COMM port number, and the device is still shown as Cebal Controlled devices in the device manager. Is it correct?

  • 0 in reply to yi xia
    TI__Guru** 105180 points
    Hi,

    The packet sniffer firmware does not enumerate as a COM (CDC) port, it uses the CEBAL interface. You need to program the dongle with the Host Test firmware using the CC Debugger in order to enumerate as a COM port.

    Best wishes