New association request on second Central connection

[Armando]

Hi,

I'm encountering a strange problem with the nRF52832 when it works as Central with two bonded Peripherals connection.

In particular I'm able to secure the connection with the first Peripherals by calling the pm_handler_secure_on_connection() function as soon as the BLE_GAP_EVT_CONNECTED event is sent by the softdevice.

When I establish the connection with the second one Peripheral (a smartphone) I receive a new association request on the smartphone display, please consider that the device was previously bonded.

If I accept the new pairing with the device (by pressing “OK” on the smartphone display, I use the Just Works method) a new bonding occurs and the connection is secured, after a disconnection I have to pair again.

I use the scan with policy WHITELIST and I call the  sd_ble_gap_connect() function when the NRF_BLE_SCAN_EVT_WHITELIST_ADV_REPORT occurs.

Any idea about the problem?

[Edvin]

Hello,

Are all devices' bonding information deleted when you start your test, so that you are 100% sure that one device doesn't have old bonding information and the connected device still tries to use some bonding information?

What are the peripherals in the connection? Are they nRF DKs running your application? Or are both peripherals phones? Does it only happen if the phone is the peripheral? Does it happen if you try to bond with the ble_app_gls example as the peripheral, and the phone as a central using nRF Connect?

I am afraid you will have to capture a sniffer trace of the packets when you try to connect to the bonded device. You can use the nRF Sniffer.

Please take one sniffer trace when you delete the bonding information on both devices first, and one where you don't delete the bonding information before you connect.