Bonding information is cleared over time

[Masa]

nRF52832 is used as Central to get data from nRF52820 (Peripheral).

There is no problem when you always communicate, but if you can not communicate due to running out of the Peripheral, etc., you can reconnect even if the connection is expired for several tens of minutes, but after about an hour, the connection from the advirtise again. It will return to (the same state as reset).

The time is irregular and the information is gone in a few tens of minutes, and it may be maintained even after an hour.
There is a possibility that the microcomputer is reset, but it does not occur in the debug state and the cause cannot be identified.

The SDK is created based on 17.1, Central's ble_app_uart_c.

[Vidar Berg]

Hello,

The original implementation of these SDK examples do not include support for bonding or pairing. Have you implemented support for this in your version of the project?

Peripheral, etc., you can reconnect even if the connection is expired for several tens of minutes, but after about an hour, the connection from the advirtise again. It will return to (the same state as reset).

I'm not sure I understand the difference between these two scenarios. The peripheral must start connectable advertising in order to allow a connection to be re-established.

Best regards,

Vidar

[Masa]

Hello,
The bonding function can be imported from other samples and can be connected.
The problem is that if the bonding connection is cut off and about an hour has passed, all the connection information on the Central side is cleared (the Central continues to be powered on and is not in standby).

For example, if the Peripheral side is turned off for about 10 minutes, when the Peripheral side is turned on again, bonding will be automatically established (communication-wise advertising → bonding connection).
If about an hour has passed, there will be no Central information, and although advertising can be received, bonding will not be automatically established. (Same state as a reset)

Best regards,

[Vidar Berg]

Hello,

There is clearly an issue with how bonding support was integrated if the bonding information is suddenly lost after some time. I suggest monitoring the PM_EVT_PEER_DELETE_SUCCEEDED and PM_EVT_PEERS_DELETE_SUCCEEDED events on both your peripheral and central devices to determine if any of these events are triggered. You may also call pm_peer_count() to check the number of bonds on the device.

Best regards,

Vidar