RE: About Bond Manager

Petter Myhre — Fri, 09 Jan 2015 10:02:21 GMT

The purpose of bonding is described in Vol 3, Part H, Section 6.5.1, in the Bluetooth Core Specification 4.2:

The purpose of bonding is to create a relation between two Bluetooth devices based on a common link key (a bond). The link key is created and exchanged (pairing) during the bonding procedure and is expected to be stored by both Bluetooth devices, to be used for future authentication. In addition to pairing, the bonding procedure can involve higher-layer initialization procedures.

The bond manager (and the device manager) is just a library we offer for persistently storing the bonding information (in flash). You don't have to use it, you can store the bonding information however you want to, or if you don't need bonding, you can just skip it all together.

You can find information about the bond manager in SDK 5.2.0 documentation, and information about the device manager in SDK 7.1.0 documentation.

If the list is full you will not be able to store more bonds, but you can increase the number of bonds you can have in the list, and you can delete bonds from the list.

If you reset your device and you lose the bonding information, it is not working as it should. If you delete the bonding information from Master Control Panel you are no longer bonded.

RE: About Bond Manager

Elena — Fri, 17 Oct 2014 09:26:45 GMT

Thanks you. I'll start right now to include the bond manager to my design

Thanks again

RE: About Bond Manager

wlgrd — Tue, 14 Oct 2014 22:14:25 GMT

The bond manager, or Device Manager (see SDK6.0 docs) stores information about the bonds in flash so it is persistent through a power cycle. When the list is full, I think the application needs to tell the DM which bond to erase to make room for a new bond.