TI CC2540 support / BLE support

[shirriff]

Your csniffpiper was very helpful to me. I've figured out a few changes to make ccsniffpiper work with the CC2540 and generate BLE traces that Wireshark can handle. What's the best way to make this available to other people? Should I fork your code? Attach a patch file?

[andrewdodd]

To be honest, I'm not really sure. If you send me a patch/pull request I'll happily include it (I don't really use this tool much anymore).

[bertrik]

Very interesting. I've done some investigation on a "webee" CC2540 dongle, including USB sniffing. It seems indeed that the protocol to talk to the CC2540 dongle is very similar (if not identical). My reverse engineering page is at: https://revspace.nl/CC2540

[nickls]

@shirriff Did you ever make a patch or PR for the CC2540 changes?

[shirriff]

@nickls Here's a patch file that has my CC2540 changes, in case it's useful. I haven't looked at this code since 2014, so I can't provide much help if it doesn't work.

ccsniffpiper.txt

[sh123]

@shirriff, thank you, your patch still works fine with CS2540, would be nice to merge it.

[subhanshus-optimus]

@sh123 Can you provide updated code for using CC2540 as BLE sniffer and directly view packets via Wireshark?

[sh123]

@subhanshus-optimus, you can just apply patch provided by shiriff above.

[subhanshus-optimus]

@sh123 I tried after updating ccsniffpiper.py (please refer to attached updated file) and executed following steps:

• Connected CC2540 usb dongle to ubuntu machine

• Exectuted pipe2wireshark.sh file.

Results: No BLE packets were displayed in wireshark. ccsniffpiper_patchAdded.txt

[sh123]

@subhanshus-optimus, try to run it separately (without using .sh script) to see if it works. In my case, I also had to change CHANNEL in pipe2wireshark.sh and update range in arguments as

-                          choices = range(11, 27),
+                          choices = range(36, 39),