The current sniffer FW (the hex files that is flashed on the dongles/DKs) does not support sniffing 2MBPS or CODED_PHY, unfortunately. I believe this is a work in progress, but I don't have any input on when this will come.
Right now, this is not possible using our sniffers. If you want to sniff the communication, then you need to stay on 1MBPS (during the development). When you are satisfied with the application, you can implement the request for 2MBPS.
May I ask whether there are any specific reason for why you need to sniff on 2MBPS? Do you just want to check that the link switch to 2MBPS? Or do you see any issues with the application after switching to 2MBPS? Do you suspect that this issue is related to the PHY? Or is it possible to reproduce it on 1MBPS?
It's a good idea.But it means that sniffer does not support the features of ble 5.0. In the process of Wireshark being used by me, it is found that extend adv cannot be recognized.
Posting on this thread to keep information collected rather than making a new one. By "extended adv" I think Ming meant the extended advertising feature of Bluetooth 5 where the advertiser tells the listeners to go to a data channel and receive up to 255 bytes of data, which is completely unrelated to 2Mbps or CODED_PHY. I'm assuming this feature is currently unsupported as well, based on my own testing. I'm trying to debug why a Samsung phone is giving me Error 133 when I try to connect to my device, while a OnePlus phone works just fine, and sniffing the over the air data would be helpful. And yes I need extended advertising, the device I'm working on requires broadcasting more data than can fit in a traditional advertisement + scan response. And the bug seems to be specifically related to use of the extended advertising feature where the phone can see the advertising data fine, but the connection process fails.
Specifically, is support for the extended advertising feature also planned for a future release? Again this is not related to the 2Mbps or CODED_PHY feature from the comment I'm replying to.
