sometimes connection not bonding

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable
Step 1: Central connects to and bonds with peripheral-1, writes request, gets notification, disconnects.

Step 2: Central then connects to and bonds with peripheral-2, etc.

Step 3: Central then tries again with peripheral-1; central and peripheral-1 both get ConnUp callback, but neither gets bond result callback (lesmp_regSMPResultCb).
0 Likes
1 Solution
Anonymous
Not applicable

Hello Jason,

Here is what we believe the behavior of your use case:

1.  The Central and Peripheral are already bonded.
2.  Therefore, the bonding will not occur again.
3.  If security was enabled, you will get an encryption complete call back as a result.

Hope this helps,
JT

View solution in original post

0 Likes
3 Replies
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog
Are you using the BCM920732 Tag board?

Which of the included ROM/RAM based profiles are you using for your testing?

Are you enabling anything within BLE_PROFILE_CFG to enable Pairing/Bonding?

I will check with the developers.
0 Likes
Anonymous
Not applicable

I'm getting this behaviour, was it ever established what was going on?

0 Likes
Anonymous
Not applicable

Hello Jason,

Here is what we believe the behavior of your use case:

1.  The Central and Peripheral are already bonded.
2.  Therefore, the bonding will not occur again.
3.  If security was enabled, you will get an encryption complete call back as a result.

Hope this helps,
JT

0 Likes