![]() The following requests are sent: Request type This appears to be done using USB control transfers. towards the stick: which radio channel to sniff, and some other radio settings.In the windows sniffer software, it seems there are only two things communicated: 0xC9, no idea, this appears in my USB logs but I can’t find it in the python code.0xC0, GET_IDENT: returns some kind of identifier.The USB control transfer request codes seem to match up with the code in In the logs, I cannot see any firmware blobs being downloaded to the stick.Probably the stick comes with a pre-loaded firmware of itself to do the BLE sniffing. I’ve captured a log of the communication over USB while the BLE is capturing bluetooth traffic from some iBeacon, using USB pcap. This USB device does actually work with Windows: You can recognise the 2540 type number in there. Reading the identification from the stick with the 0xC0 command, results in the following 8-byte response When plugging this stick into a Linux machine, you can see it uses only one bulk endpoint. Interesting links: Analysis Usb Cc2540 Hid USB descriptor It’s supposedly a CC2540 (or compatible) dongle, the USB id is 0451:16b3. I have such a ‘WeBee’ dongle that can be found for about E15,- on websites like Aliexpress. This page is about the CC2540 bluetooth low-energy sniffer dongle and getting it to work with Linux.A nice end result could be that it becomes possible to sniff directly in WireShark with this dongle. I wrote a little test program to dump raw BLE framesīusiness in a box pricing.it is pretty clear which commands the default sniffer firmware understands.Reverse engineering the CC2540 BLE sniffer dongle Some highlights: USB controller 2 hardware UART. This chip has all major peripherals and hardware capability of modern microcontrollers, as you can see from the functional diagram below. ![]() The only different between the two is the flash space as the name indicates. We distribute the drivers (and install them as well) with SmartRF Studio (see C: Program Files (x86) Texas Instruments SmartRF Tools drivers vcp), but I’ve attached the required files here for your convenience. Yes, we actually do have signed CDC drivers (or really signed.inf files) for the CC2531 (and our other USB devices). The kit contains ESD sensitive components. Kit Contents 1 x CC2540 USB Dongle 1 x Quick Start Guide The CC2540 USB Dongle in this kit is FCC and IC certified and tested to comply with ETSI/R&TTE over temperature from 0 to +35☌. Most Android-based phones also do not require third-party programs.įor those who have problems, we recommend a program for reading QR codes Privacy Friendly QR Scanner (we are not affiliated with this software, but tested this application and it performs the necessary functions).ĬC2540 USB Evaluation Kit Quick Start Guide 1. For Apple phones, no additional software is required (just point the camera at the QR code and follow the instructions). In order to be able to scan the code, use the camera of your phone. You need to scan the QR code shown on the site using your mobile phone (or tablet) and perform the required actions on your device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |