NRF-{BT,802154}-SNIFFER NRFUTIL nRF52840 DONGLE HEX TO DFU ZIP --SD-REQ

[CeDeROM]

Hello world :-)

I would like to use Bluetooth Low Energy Sniffer [1] and 802.15.4 Sniffer [2] on nRF52840 DONGLE using my FreeBSD workstation.  I did manage to build the`nrfutil` (no nRF Connect and other closed source utilities). DFU mode reuires ZIP package not HEX files that are provided with these project releases.

I have noticed that using `--debug-mode` allows me to skip the cryptography part which is not important here.

I have noticed that `--hw-version` should be `52` for the nRF52 family.

I am not sure what parameter should I use with `--sd-req`. Using `0` generates the DFU ZIP package and it gets flashed, but I can only work with 802.154 Sniffer (it shows as umodem device and I can talk to it over minicom serial terminal) while BLE Sniffer does not work (it shows as umodem device but I cannot talk to it over minicom serial terminal).

What is the in depth purpose of this `--sd-req` switch? Does it filter all available options for the hardware that DFU ZIP will be flashed in order to avoid flashing into incompatible hardware? Does it perform some soft of selection and/or glue of the provided HEX with selected SoftDevice and it really matters to provide valid numbers for 802.15.4 and different nubers for BLE?

My observstions:

* NRF-BT-SNIFFER Firmware 3.0.0 and 3.1.0 works with nRF52840DK + Wireshark, using DEBUG VCP not the nRF USB port.

* NRF-BT-SNIFFER Firmware 3.0.0 works with nRF52DK_nRF52832 + Wireshark.

* NRF-BT-SNIFFER Firmware 3.1.0 does NOT seem to work with nRF52DK_nRF52832, as above it sends something over DEBUG VCP as this device does not have its own USB port.. and although I can see and read from the umodem /dev/cuaU0 port the script does not recognise it and so it is not visible in Wireshark.

* NRF-BT-SNIFFER adds support for nRF52840 DONGLE in 3.1.0 Firmware version. After conversion from HEX to DFU ZIP this firmware flashes into DONGLE, it shows up as umodem, but it remains silent and no Wireshark/script finds it.

My questions:

* Are problems with NRF-BT-SNIFFER that common?

* Why there is no dedicated repository for NRF-BT-SNIFFER on GitHub while NRF-SNIFFER-802154 has its own repo?

* Why those Sniffers are not Open-Souce?

* Is this DONGLE problem related with NRFUTIL DFU ZIP conversion using invalid SD-REQ parameter or the Firmware itself?

Host OS: `FreeBSD 0xCFMX4 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC  amd64`

Any hints welcome :-)

Tomek

[1] www.nordicsemi.com/.../nRF-Sniffer-for-Bluetooth-LE

[2] github.com/.../nRF-Sniffer-for-802.15.4

[Simonr]

Hi

I made it to the office today and tested the BLE nRFSniffer (v3.1.0) on a new nRF52840 Dongle and did not have any trouble adding the BLE sniffer profile to Wireshark nor finding the Dongle as an available sniffer. Please see the screenshots below. I found one step that's easy to miss during setup that might cause you to not see the sniffer device. After the necessary modifications to Wireshark is done, please make sure to enable the nRF Sniffer capture tool in Wireshark by:

1. Refresh the interfaces in Wireshark by selecting Capture > Refresh Interfaces or pressing F5. You should see that nRF Sniffer is displayed as one of the interfaces on the start page.

2. Select View > Interface Toolbars > nRF Sniffer for Bluetooth LE to enable the Sniffer interface.

For reference, I flashed the sniffer firmware onto the Dongle using the nRFConnect for Desktop Programmer application with the sniffer_nrf52840dongle_nrf52840_7cc811f.hex file.

Best regards,

Simon

[CeDeROM]

Thank you Simonr for your time effort and confirmations!! This means something needs a fix on my end :-)

Merry Christmas to You and the Team :-)

[Simonr]

Merry Christmas to you to! I hope you find out what's wrong soon. Don't hesitate to ask if you need assistance!

Best regards,

Simon