CC2540EMK-USB: Driver for Windows 10 for CC2540 USB doesn't install/work

I tried a couple of things:

- Enabled unsigned driver install (my system is x86

- I downloaded the BLE-STACK:II. BLE-STACK (Support for CC2540/CC2541)

- Modified the PID in the driver .inf to match the PID of the dongle

  Driver in C:\Texas Instruments\BLE-CC254x-1.4.2.2\Components\hal\target\CC2540USB\usb\driver

Changed PID to 16B3

- Then did driver reinstall, pointing to above directory, got msg about unsigned drivers and it installed.

- The driver tried to start but failed, couldn't start

This device cannot start. (Code 10)

A device which does not exist was specified.

 

Device is listed at TI CC2540 USB CDC Serial Port COM3

????????????????????

I note that the CEBAL driver with the Smart RF Packet Sniffer install is only x86, my system is x64

Do you download sniffer FW to your CC2540 USB dongle?

I downloaded and installed the SmartRF Packet Sniffer at .

The driver in that package is only x86.

I did not install anything the to the dongle.itsself.

I have found a "workaround"!

I dug up an x86 (16 bit) (slow) box running Windows 10 and was able to get that to work.

Surely there is a a x64 version of the driver somewhere though ??

I downloaded the Packet Sniffer software from that link above and installed it, however no driver gets installed, I am on Windows 10 x64.

The file that gets downloaded is called swrc045z.zip and inside are the following 2 versions (?) of the packet sniffer install, tried both, both don't result in a working driver being installed. 

Setup_SmartRF_Packet_Sniffer_2.18.0.exe

Setup_SmartRF_Packet_Sniffer_2.18.1.exe

I notice that during install the following error occurs regarding driver install:

Output folder: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\Drivers
Extract: dpinst32.exe... 100%
Extract: dpinst64.exe... 100%
Output folder: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\Drivers\cebal\win_32bit_x86
Extract: cebal2.cat... 100%
Extract: cebal2.inf... 100%
Extract: cebal2.sys... 100%
    Installing Cebal driver...
Execute: "C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\drivers\dpinst32.exe" /c /sa /sw /PATH "C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\drivers\cebal\win_32bit_x86"
    Driver installation failed with return code -2147483648.
Delete file: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\Drivers\dpinst64.exe
Delete file: C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\..\Drivers\dpinst32.exe
Completed

There is a driver file in C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Drivers\cebal\win_32bit_x86 after the installation.

However trying to manually install the .inf in there results in no error message, but still no driver being installed.

How to get this working on Windows 10 x64? I have the same problem as mentioned above in that the CC2540 dongle shows up in device manager with no driver installed and is therefore not showing up in the Packet Sniffer. The dongle is untouched as received from TI, which I understand should mean that its flashed with the packet sniffer firmware by default. 

Are you sure you already download sniffer FW sniffer_fw_cc2540_usb.hex into your CC2540 USB dongle?

I don't have a programmer, I just ordered a CC2540 USB dongle from TI and it says on TI' product page that by default the CC2540 USB dongle is flashed with the sniffer FW.

So, you have tried to use cebal2_x64.inf under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\drivers\cebal\win_64bit_x64 and it doesn't work on your Windows 10?

there is no directory "win_64bit_x64", there is only win_32bit_x86

thanks for the hint though, I found another post from you here with the x64 driver attached, after installing it it all works now! e2e.ti.com/.../538263

problem is just that the official packet sniffer install did not install this x64 driver on my system

It's good to know you find my attachment and make it work.

Hello,

My situation is similar to one described by the guys above, but with some difference: when I first installed SmartRF Studio + Packet Sniffer + SmartRF Flash Programmer, everything worked just fine: I was able to use cc2540 dongle with sniffer, read and write firmware from/to cc2540 chips through SmartRF05EB.

Yesterday I tried to read the firmware from cc2531 chip and found out that now neither Packet Sniffer nor Flash Programmer nor Studio don't see any of the chips! It seems that the main big thing that happened in between is the automatic Win 10 upgrade to ver 1703 (build 15063.413 as it says now; don't remember, which one was before). It's x64.

I removed Studio, Programmer and Sniffer applications, reinstalled them, but with no effect. Versions that I use are:

SmartRF Studio 7 - 2.6.0

Packet Sniffer - 2.18.1

Flash Programmer - 1.12.8

As everything worked before, I didn't look to Windows' device manager. Now I looked there and under "Other devices" I have CC2540USB Dongle with error 28, driver not installed, like mentioned in above messages. It's pretty surprising to see that, but at least it correlates to the fact that things are broken now.

I installed the same toolset to Windows 7 machine and Pack Sniffer sees cc2540 pretty well there, meaning that hw is working.

Further, I don't see any "cebal2_x64.inf under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\drivers\cebal\win_64bit_x64". Under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\drivers\cebal there are only 2 dirs: \not_certified and \win_32bit_x86, no mentioning of 64bit version at all. So, as far as I see, I have latest versions of all tools and neither one has installed 64bit version. Where can I find it?

But the strangest thing here is that I definitely remember that about 1-2 weeks ago everything worked!

Has anyone faced this kind of problem?

Vladimir

Sorry, I didn't realize that this topic had the second page! Now I found your attachment too, installed the drivers and it works. Thanks a lot!

Still, I think TI guys should recheck the distributions that place x86 drivers in Win 10 x64. In my Win 7 installation the Cebal dir contains just previous version (relative to yours) of win_64bit_x64. So, it seems to be a problem of Win 10x64 installations.