nrf52832-DK sniffer issue

RE: nrf52832-DK sniffer issue

Khodidas11 — Wed, 16 Sep 2026 05:25:25 GMT

Hi,
Finally done, We analyzed multiple packets and Found issues related toBLE audi over L2CAP and resolved. worked .

Thank you for Kind and timely support.

Regards

Khodidas Domadiya

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Tue, 15 Sep 2026 13:11:13 GMT

Hi Khodidas,

I am glad to hear that workd. L2CAP is fine, but as you mention audio plese note that ISO is not supported, and conversly not LE Audio. If you need to sniff that you would need another sniffer such as for instance Ellisys.

Regarding timing, note that you can use the delta time, but the absolute timestamp in the time field is not accurate as that is set on the PC side and affectec by the UART/USB transport between the sniffer HW and PC.

RE: nrf52832-DK sniffer issue

Khodidas11 — Tue, 15 Sep 2026 11:32:39 GMT

Hi,

Thanks for Highlighting.

It worked, It was observed that after changing firmware of segger Jlink. it helped.

This helps to sniff sniff data packet transmitted over GATT profile. Now we need to sniff audio data transmitted on L2CAP. Also want to measure time between two transmission.

Regards
Khodidas

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Tue, 15 Sep 2026 11:13:21 GMT

Hi,

I am sorry I did not spot this before in your previous screenshot, but you are filtering on advertisign address using normal wirehark filtering. So you will not see this in a connection. You need to select the device from the Device list dropdown where you currently have selevted "All advertising devices". That is a requierment in order to follow and sniff a connection.

RE: nrf52832-DK sniffer issue

Khodidas11 — Tue, 15 Sep 2026 10:36:13 GMT

Hi,

Still issue is as it is

Regards
Khodidas

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Fri, 11 Sep 2026 11:49:57 GMT

I see. I am not able to explain this, but the nRF52832 having no USB is a bit limited as it depends on UART and USB-CDC. In order to limit the potential proglems introduced by that, I suggest that you 1) Disable the mass storage device on the debugger (using the MSDDisable command as described here). It is also worth making sure that the J-Link firmware on the DK is up to date, which you can do with J-Link Configurator.

RE: nrf52832-DK sniffer issue

Khodidas11 — Fri, 11 Sep 2026 09:52:34 GMT

Hi,

After upgrade still facing saame issue

nrfutil-ble-sniffer 0.21.0 (9e8f626 2026-08-13)
commit-hash: 9e8f6262ef2d246a589fbfa8aa527656f14c6baa
commit-date: 2026-08-13
host: x86_64-unknown-linux-gnu
build-timestamp: 2026-08-14T09:02:26.515665353Z
classification: nrf-external

no data packet sniffin after CONNECT_IND

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Fri, 11 Sep 2026 08:56:48 GMT

Hi,

I see that the sniffer software is not updated, can you call "nrfutil upgrade" to get the latest version (0.21.0)? This includes fixes for an issue that might explain this, where packets would be lost between the sniffer HW and computer.

RE: nrf52832-DK sniffer issue

Khodidas11 — Fri, 11 Sep 2026 04:26:43 GMT

Hi,

Yes using 1M Phy only. and below is blr-sniffer version details

nrfutil-ble-sniffer 0.18.0 (e34a381 2026-02-10)
commit-hash: e34a381b8d88a550916c7383ec6344ea92285d37
commit-date: 2026-02-10
host: x86_64-unknown-linux-gnu
build-timestamp: 2026-02-12T10:29:55.170582366Z
classification: nrf-external

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Thu, 10 Sep 2026 13:22:16 GMT

I see. Is the BLE sniffer updated as well? ("nrfutil ble-sniffer --version")?

Also, can you confirm that connection happens on 1M PHY? If by any chance connection happens on Coded PHY you have to enable that in Wireshark, and also use a board that support it (nRF52832 does not).

Other than that I am not able to think of anything specific, so it would be interesting to see more details on your testing.

RE: nrf52832-DK sniffer issue

Khodidas11 — Thu, 10 Sep 2026 13:15:32 GMT

Hi,

nrfutil 8.2.1 (350d1fd 2026-08-11)
commit-hash: 350d1fdcdf82d30c115ebb08bdbb9717937f37ac
commit-date: 2026-08-11
host: x86_64-unknown-linux-gnu
build-timestamp: 2026-08-11T14:44:07.606388532Z
classification: nrf-external

this is installed in Ubuntu 22.04 Also for windows, downloaded latest and using. Yes we selected device from device list and then after established connection.

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Thu, 10 Sep 2026 13:08:13 GMT

Hi,

I see. But which version of the sniffer software do you use? Do you use the nrfutil variant (which you should)? If so, can you make sure it is updated? (You can update with "nrfutil self-upgrade" and then "nrfutil upgrad").

Also, can you confirm that you select the device in the device list before connection is established? That is a requierment for the sniffer to follow the connection.

RE: nrf52832-DK sniffer issue

Khodidas11 — Thu, 10 Sep 2026 12:50:33 GMT

Hi, Einar

I am using sniffer_nrf52dk_nrf52832_4.1.1.hex, which is proigrrammed if nrf52832-DK.
Also tried with wireshark version 4.6.8. Facing same issues.

RE: nrf52832-DK sniffer issue

Einar Thorsrud — Thu, 10 Sep 2026 10:50:01 GMT

Hi Khodidas,

In order to follow a connection you need to select the advertising device in the dropdown in Wirehark in the device list before the CONNECT_IND is sent. Do you do that? Note that even then the sniffer may loose the packet, and then you need to try again (disconnect and establish a new connection and see if the sniffer picks it up).

If that is not the probelm, we need to look deeper. I have questions about the sofware versions. Are you using 4.1.1 of the sniffer PC side software, or is that just the version of he hex file? The PC side software has moved to nrfutil and is now installed via nrfutil and there has been several important undates there. See documentation. I would also suggest updating Wireshark as that is quite old. The last nrfutil based version is 0.21.0 (see changelog).

If you stil see this issue with the latest versions, can you share a bit more detail about the configuration (type of advertisment, PHY used) as well as a description of how you test and logs?

There is currently no support for using nRF54L15 as a sniffer, but that is a request that we are looking into. I cannot promise or povide a timeline for this, though.

Regards,

Einar