Cc2540 Usb Dongle Driver
Taneka Tarring
I'm trying to use the CC2540 USB Dongle as a packet sniffer. It was pre-programmed with the corresponding firmware, but I don't manage to install it on my PC and use it as a sniffer tool. I have already tested with the 2 packet sniffer applications from TI, but it keeps saying there is no driver for it. I found an x86 driver in the sniffer installation folder, but not x64. Installing the BLE stack there are x86 and x64 drivers available but not for this VID/PID (VID_0451&PID_16B3). Is there a 64bit driver for Win 10? Where can I find it?
I can run the CC2540 USB dongle PACKET-SNIFFER v2.18.1 firmware on my Win10 x64 machine. Note that you must install this package since the CEBAL driver used by the packet sniffer is not bundled with the BLE-Stack.
Hi, in the PACKET-SNIFFER v2.18.1 the driver is only for x86 architecture, this is why I have asked here for the x64 driver version. In the meantime there is another answer to my question with the x64 driver version attached, that solved my problem :-)
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.
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.
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.
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?
Apparently, there has been a change in Windows 8 related to signing of drivers. Win 8 now enforces that all drivers (related .inf files) have a digital signature. Without the signature, the driver will not be installed. On win 7, you could ignore the error and install anyway, but not so for Win 8. The driver (or really, the .inf file) for the dongle has not been certified by TI yet.
However that clearly isn't the case, at least for me. I get the signature problem that everyone else is having on Windows 8 machines. This driver you provided however works fine! It would probably help a lot of people out if you guys updated that package or at least made a note on the TI BLE stack download page. Thanks again.
Thanks for noticing! The BLE stack installer is actually missing the .cat file (it only includes the new .inf file). So for now, please continue to use the one I posted in this thread, and we will update the installer.
Maybe I'm just doing something wrong but after downloading and extracting the driver folder I can't seem to get it to work. I've tried directing the device manager to the extracted folder only to have it tell me that it can't find any driver files, then I tried picking from the list of drivers on my computer as shown in the pictures below only to have download errors. Can anyone fill me in as to what I'm doing wrong?
I have installed the RFStudio 7 which includes all necessary drivers as suggested on some of the post. I have noticed one thing when adding device manually. I can see the Texas Instrument in standard Serial port devices.But no device like TI CC45XXXX CDC?
I have noticed one more thing with RFStudio 7 that when I connect the SensorTag on serial port RFStudio detects the CC2541 but unable to detect the usb dongle when connected on CC debugger's serial port.
Not sure if I understand your second question. Do you connect the CC debugger to the CC2540 USB dongle, but can't see the device in SmartRF Studio? Have you applied any power to the dongle (it needs to get power from a USB port)?
Have you checked the CC Debugger cable? In a very few cases, we've seen that the cable might be broken or that there's something wrong with the small adapter board between the debugger and the small cable.
what is terrible is i saw it passed to green one time and unconnected it to make sure i could reproduce it again, and since then , no green anymore on any of all the deive i have : keyfob, dongle, sensor tag
I would not be amazed this is a cable issue coming from the jtag cable... as i just see the led passed to green again (and then rf studio indicate CC1201 instead of nochip) and then when i pressed again it turn to red, very strange..
Are you sure that winXP recognized the CC2540USB Dongle as a CDC device? You can check this in Device Manager where it should state "TI CC2540 Low-Power RF to USB CDC Serial Port (COM##)". This is completely independent of BTool and should indicate if it's a problem with the USB driver. Let me know.
on the other hand, I am using another notebook PC, winXP, install BTool by runing "BLE-CC254x-1.3.exe" first,no USB driver can be install when CC2540USB is plug-in. Then I install SmartRF Packer Sniffer_2.16.3, then it can recognize the CC2540USB device as "Cebal controlled devices".
I have flashed the dongle with CC2540_USBdongle_HostTestRelease_All.hex. Upon plugging the dongle into the USB port, the LED is showing red. And nothing is shown in the device manager.
I also tried to use CC2540_SmartRF_HostTestRelease_All.hex. I flashed this file to the CC2540 EM module on the SmartRF05 evaluation board. It's shown up under "Cebal controlled devices".
1. If I right click on usb_cdc_driver_cc2540.inf and choose "Install", a "Install Error" dialog would pop up and says "The INF file you selected does not support this method of installation"
When I update drivers and point to this folder, it tells me the driver is uptodate. I've tried pointing to the specific file not folder and this results in the same error as right click install having navigated to the file.
I've tried have disk and the error this time is potentially more helpful, as it says the folder doesn't contain a compatible driver, followed by if it does make sure it is designed to work with Windows for x64-based systems. I'm using Windows 7 64 bit.
I have tried the method mentioned by William14730 but still recognizing devices as a "Cable Connector Devices" and I couldn't see "unknown USB device with warning icon". Also It could not find the driver when tried to add device manually and installed driver from "c:\Texas Instrument\BLE-CC254x-1.4\Accesso..\Drivers".
I am not able to install the btool driver on either an XP or window7 machine. When I plug in the CC2540 central board's USB cable the PC's device manager populates with Cebral controlled devices->SmartRF05EB and I am not able to update this driver with the .inf file in the btool accessories folder.
I have the same issue with windows 7.. But I am not able to find a COM port "TI CC2540 Low-Power RF to USB CDC Serial Port (COM##)".. I tried many things...but everything is unsuccessful..Can you guide me through this?
I have no such thing as "Accessories\Drivers\usb_cdc_driver_cc2540.inf" in the BLE folder. It is version 1.4 though. Only ccxxxx_usb_cdc.inf I have which will install Cebal driver but not the COM port. So, could you please suggest what to do next?
I have installed the BLE 1.4 multiple times, last about a minute ago. The Drivers folder contains only ccxxxx_usb_cdc.inf and ccxxxx_usb_cdc.cat, nothing else. That installs my CC2540 USB dongle as Cebal controlled device but does not install any COM ports.
The packet sniffer actually shows some packet flow and I am quite not sure if that is correct or not. The Flash Programmer tool, neither version 1.27 nor version 1.4 shows the CC2540 dongle.
no, I have not flashed it with the CC debugger. Actually, I do not even have a CC debugger. I just want to use the CC2540 dongle to deliver measurements from CC2541 SensorTag to my PC-hosted C++ program. Do I need the CC debugger to start using the CC2540+CC2541...? Or am I still missing something?
I fabricated a board.
I am using a CC debugger.
I am able to upload a bootloader by following a 3rd party site.
It was successful but not sure how to check if it was successful or not except the flash programmer says verify OK.
I need some ports to choose from in the Flash software to upload the firmware. I can't choose a port because these ports are not associated with the CC debugger. I need to bring a port somehow so I can select it and upload the firmware. The light is green on debugger, it shows up in the device manager as a CC debugger but I don't know why not any port.
Thanks
I didn't try it but i am not sure what settings i should change to upload firmware in flash programmer.
Do i need to choose secondary location for firmware?
Also, How the port will appear?
Hi Ali, In the guide you are following the programming of the CC2540 happens through an FTDI device or another MCU (Arduino something). The COM port you are looking for is thus not associated with the CCDebugger.
TI have provided you a way to upload FW to the CC2540. Since you have successfully uploaded the boot loader through the CCDebugger, you know that that interface works. This is in fact the default way provided by TI to program the device. Of course TI cannot help you with some third party serial interface boot loader system. How would they know how that is designed and supposed to work?
ff7609af8f