Ti Cc2540 Usb Driver
Tabby Vandermoon
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.
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?
Hi, I have the same issue. We just purchase and received a new Wireless Connectivity Development kit based on the CC2540 and CC2541 but nothing works. The driver keeps loading as a Cebal driver and no COM ports are available. BTool this does not find any devices. Any help would be much appreciated.
From what I read in this forum, the USB Dongle should appear as a Cebal controlled device. I just can't get Windows to detect it as anything other than a COM port. I have tried uninstalling the USB Dongle from Device Manager, and telling Windows to even remove the driver. But as soon as I plug it back in to a USB port., it reappears as a COM device. The CC Debugger does appear as a Cebal device.
If you need to flash a new CC2540 chip, you have to solder it on DFRobot BLE card correctly. Make sure there is no false welding! Here we skimmed some steps of installing softwares or the drivers for CC Debugger, please read related documents about how. CC Debugger usage, by TI
Ble-Nano can drive LCD1602 display screen through IIC, with less wiring and simple operation. Since there is a driver board on the module, cumbersome wiring is not needed, and only 4 wires are needed to control it
And last, but not least, are Iman's custom devices and drivers. Custom Zigbee devices that exceed the performance of similar mass produced products from well-established manufacturers. The problem here? Well, there is none, really. I mean, he built them from scratch to address some very specific uses. But if I were capable of doing it, I'd build a zigbee device that could match (or exceed) the capabilities of the ZEN17 and perhaps even add in an analog input/output.
That project looks promising, but I'm not really clear on what hardware one would need in order to use that firmware. And then there is the obvious driver issue. Do you have any other info on this project? Perhaps the "...for Dummies" version would be more up my alley.
You will also need a nodemcu with firmware from this site to flash the ti based board (using ccloader) with the Zigbee configurable firmware. It talks about the cc2540 chip (bluetooth) but the procedure is the same for the cc2530/cc2591 (cc2591 is an amp for the cc2530 zigbee chip)
b9b4d2437c