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 again

The COVID situation escalated again in this weekend, so I won't be able to test the sniffer firmware on the Dongle today I'm afraid, but I should be able to during the week. I did however test with an nRF52832 DK as well, and did not have any problems with installing the latest nRFSniffer firmware (v3.1.0) or flashing it onto the DK. You can see the screenshot below for reference.

I also asked around internally, and none of my colleagues have seen any issues with the latest nRFSniffer firmware and the nRF52840 Dongle. A suggestion as to what might be going on:

• Have you removed the v3.0.0 Wireshark profile from Wireshark and added the latest Wireshark profile according to "Adding a Wireshark profile"?
• Have you added the nRF Sniffer capture tool according to the "installation guide" here?
• Please make sure that you program the correct sniffer firmware .hex file onto the Dongle. sniffer_nrf52840dongle_nrf52840_7cc811f.hex is the correct .hex file for the nRF52840 Dongle.

As far as suggestions to other sniffer solutions, I don't have any real suggestions as we generally use the nRFSniffer or Ellisys sniffer to do sniffing, neither being open-source I'm afraid.

Best regards,

Simon