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: Unable to install USB driver for TI CC2540 USB dongle sniffer under Windows 10 64-bit

Part Number: CC2540EMK-USB
Other Parts Discussed in Thread: CC2540

I am unable to install the driver for the CC2540 USB dongle running the sniffer software under Window 10, 64bit.   

Windows  itself correctly identifies the USB dongle as a "CC2540 USB Dongle" but the driver in Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cabal\win_32bit_x86 fails to install.   The documentation I have found on TI.com mentions Windows through 8, and specifically 32-bit.   However, I  *am* able to load the driver and run the SmartRF sniffer in a 64-bit Windows 7 VM, which is being hosted by Windows 10 64-bit.

So is there, or will there be, a 64-bit Windows 10 driver?   I really hope so because we've been recommending this USB sniffer to our clients...

-- Neal

  • Hi,

    I am using windows 10 64 bit system, and I have no problem using CC2540 usb dongle with packet sniffer.

    Can you download BLE stack 1.4.2 and see if the usb driver is installed successfully.
    BLE stack 1.4.2 can be download here :
    http://www.ti.com/ble-stack
  • I have this dongle and it works OK out of the box as a packet sniffer on windows 10 but the serial driver doesn't work (so you can't program it with different firmware). I was hoping to be able to use it with btool but because it can't be programmed, you can't. The packet sniffer is very useful though.
  • No joy with Btool, which doesn't seem to have a driver included, but I tried it anyway.
  • Here's Windows' device driver install error log. The exact error is near the bottom (Error 0xe0000228: There are no compatible drivers for this device.):

    [Device Install (DiInstallDriver) - C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf]
    >>> Section start 2017/01/02 10:32:12.545
    cmd: "C:\WINDOWS\System32\InfDefaultInstall.exe" "C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf"
    ndv: Flags: 0x00000000
    ndv: INF path: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf
    inf: {SetupCopyOEMInf: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf} 10:32:12.563
    inf: Copy style: 0x00000000
    ! inf: Driver package is already in driver store
    sto: {Setup Import Driver Package: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf} 10:32:12.579
    sto: Driver package already imported as 'oem56.inf'.
    sto: {Setup Import Driver Package - exit (0x00000000)} 10:32:12.584
    inf: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\cebal2.inf_amd64_c808c532a09ae409\cebal2.inf
    inf: Published Inf Path: C:\WINDOWS\INF\oem56.inf
    inf: {SetupCopyOEMInf exit (0x00000000)} 10:32:12.600
    ndv: {Update Device Driver - USB\VID_0451&PID_16B3\5&16B1AE89&0&1}
    ndv: Search options: 0x00000081
    ndv: Searching single INF 'C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86\cebal2.inf'
    dvi: {Build Driver List} 10:32:12.631
    dvi: Searching for hardware ID(s):
    dvi: usb\vid_0451&pid_16b3&rev_2110
    dvi: usb\vid_0451&pid_16b3
    dvi: Searching for compatible ID(s):
    dvi: usb\class_ff&subclass_ff&prot_ff
    dvi: usb\class_ff&subclass_ff
    dvi: usb\class_ff
    dvi: {Build Driver List - exit(0x00000000)} 10:32:12.679
    ! ndv: No matching drivers found in single INF
    ndv: Searching currently installed INF
    dvi: {Build Driver List} 10:32:12.679
    dvi: Searching for hardware ID(s):
    dvi: usb\vid_0451&pid_16b3&rev_2110
    dvi: usb\vid_0451&pid_16b3
    dvi: Searching for compatible ID(s):
    dvi: usb\class_ff&subclass_ff&prot_ff
    dvi: usb\class_ff&subclass_ff
    dvi: usb\class_ff
    dvi: {Build Driver List - exit(0x00000000)} 10:32:12.726
    dvi: {DIF_SELECTBESTCOMPATDRV} 10:32:12.726
    dvi: Default installer: Enter 10:32:12.726
    dvi: {Select Best Driver}
    ! dvi: Selecting driver failed(0xe0000228)
    dvi: {Select Best Driver - exit(0xe0000228)}
    ! dvi: Default installer: failed!
    ! dvi: Error 0xe0000228: There are no compatible drivers for this device.
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 10:32:12.763
    ! ndv: Unable to select best compatible driver. Error = 0xe0000228
    ndv: No drivers found for device.
    ndv: {Update Device Driver - exit(00000103)}
    <<< Section end 2017/01/02 10:32:12.779
    <<< [Exit status: FAILURE(0x00000103)]
  • Hi David - are you running Windows 10 32-bit or 64-bit ?

    I agree the packet sniffer is very useful, but it would be even more useful if I could run it on my portable Surface Pro 3 rather than a VM on my desktop.

    - Neal
  • I have no problem to use CC2540EMK on my windows 10 64 bits system for your reference.

  • 64 bit Neal - the system shows the cc2540 serial driver on COM9 but has the above error.  As I said it works fine as a packet sniffer.

  • Hmmph. OK, so there's something goofy with Windows on that PC. A real bummer because I can run other dongles and sniffers on it.
  • Maybe try to download sniffer FW to previous CC2540EMK to see if it will work.