This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Unexpected indicated connection security with connectivity firmware

Hi

I've implemented a BLE peripheral based on the SDK11. For bonding i'm using the new peer manager. If the code runs on a nRF51 DK the bonding works properly. After the connection has been established a pin code may be inserted on the smart device. Afterwards the connection security reaches mode 1/level 3 with encryption key size of 16. On reconnect the connection security reaches again the Mode 1/Level 3 level without entering a pin. So far so good.

If the BLE peripheral code runs on a host system and uses serialization to communicate with a nRF51 DK with connectivity firmware the behavior is different.

The bonding still works properly, but after a reconnect the security level indicated by the BLE_GAP_EVT_CONN_SEC_UPDATE is Mode 1/Level 2 with Keysize 8. The strange thing is, that accessing a characteristic with security level Mode 1/ Level 3 works properly. I assume that the connection security is in the correct mode/level, but the indicated mode/level is wrong.

Any idea what can cause an invalid indicated connection security mode?

Regards Adrian

Related