nRF52-DK stops following a BLE connection after a small amount of time passes.

[tjhasan]

I am currently using a nRF52-DK to follow the connection between two external devices. I run the sniffer and start/stop the sniffing via Wireshark.

When I start sniffing, I can see the advertisement packets of the two devices. Then, I select to follow one of the devices. Once that device is followed, I connect the two external devices together. For a small amount of time, Empty PDU and Encrypted packets are shown in the window, but after a small amount of time (roughly around 3 to 5 seconds), the sniffer stops printing packets or packet data.

I'm assuming this is because of the hopping mechanism of BLE devices, but I was under the assumption that the nRF52-DK had the ability to follow a connection through the hopping sequence.

Any help would be appreciated.

[daviddedwin]

I had linked to the case where using the debug key for secure connections are described, but I see that the debug key setting is not so straight forward.

You can look at peer manager init (I checked on SDK 17.0.2 for the HID Mouse example) and set the LE Secure parameter to off, this should switch the pairing process to legacy.

static void peer_manager_init(void)
....

    sec_param.lesc=SEC_PARAM_LESC;