Sniffing BLE 5.0 packets (nRF52)

RE: Sniffing BLE 5.0 packets (nRF52)

Amanda Hsieh — Tue, 24 Nov 2020 07:08:09 GMT

Hi,

Is it possible for you to test the nRF52840 DK as the target? If so, run the ATT_MTU Throughput Example.

-Amanda H.

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Mon, 23 Nov 2020 19:50:08 GMT

Hi,
I already did it but it is not the problem.

RE: Sniffing BLE 5.0 packets (nRF52)

Amanda Hsieh — Thu, 19 Nov 2020 14:21:02 GMT

Hi,

Could you try to select the target in the device after restarting the nRF52 DK (as the sniffer) and the Wireshark?

-Amanda H.

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Wed, 18 Nov 2020 09:46:06 GMT

yes, I am using v3.0.
no, it doesn't happen. it works fine with all the v4.2 application and I can sniff all the packets but the problem only when I use BLE v5 and send using 2Mbit PHY

RE: Sniffing BLE 5.0 packets (nRF52)

Amanda Hsieh — Wed, 18 Nov 2020 09:21:03 GMT

Do you use nRF-Sniffer-for-Bluetooth-LE v3.0? If not, please try it.

Does it also happen while sniffer for other applications?

-Amanda H.

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Mon, 16 Nov 2020 11:03:30 GMT

Hi, Amanda, I tried Wireshark Version 3.4.0. but the problem still as it is. I cant sniff any packets after the "connect_req".
I am using nRF52 DK (PCA10040) as a sniffer.

RE: Sniffing BLE 5.0 packets (nRF52)

Amanda Hsieh — Tue, 10 Nov 2020 08:43:24 GMT

Hi Dmitry,

Try the later version of Wireshark like Version 3.4.0.

Which board do you run as the sniffer?

-Amanda H.

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Mon, 09 Nov 2020 13:25:27 GMT

it was the only device in the range but I did it in another test and choose the device and the same result. the"connect_req" is the last packet it can trace

RE: Sniffing BLE 5.0 packets (nRF52)

Dmitry — Mon, 09 Nov 2020 13:19:46 GMT

Did you choose your device in sniffer interface?

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Mon, 09 Nov 2020 12:29:19 GMT

Hi,Dmitry, yes it is the last one sniffer can trace.
in your opinion why it cant trace these three more packets and stopped at the "connect_req"? because I can't understand this behavior and if you have any resource explaining this point please mention it will help

RE: Sniffing BLE 5.0 packets (nRF52)

Dmitry — Mon, 09 Nov 2020 12:15:27 GMT

Hi,

is packet #1710 the last one you see in the sniffer trace? There should be at least three more packets at 1M PHY before switching to 2M.

RE: Sniffing BLE 5.0 packets (nRF52)

ahmed fathy — Mon, 09 Nov 2020 11:53:12 GMT

HI, Amanda, I know that Sniffer does not support tracing Coded PHY but in the example, I sent data only with PHY 2M so according to the sniffer's docs it should trace it.

RE: Sniffing BLE 5.0 packets (nRF52)

Amanda Hsieh — Mon, 09 Nov 2020 09:07:31 GMT

Hi,

Unfortunately, the nRF Sniffer does not support tracing Coded PHY packets at the moment.

-Amanda H.