Tool/software:
Dear support team,
I have some questions how to implement RF encryption between a pair of CC1352P chips, using simplelink_cc13x2_26x2_sdk_3_20_00_68 SDK.
On both devices, we have a 128-bit pre-shared key available that can or should be used for encryption, and both devices know the address/identity of the other.
With the TI 15.4 stack, I was able to verify an encyption by enabling FEATURE_MAC_SECURITY (in the Collector and Sensor examples), and putting the pre-shared key into the KEY_TABLE_DEFAULT_KEY variable. I did not need the Secure Manager/Secure Commissioning (Collector_SM, Sensor_SM examples) for this encryption to work.
Now I am investigating BLE with the TI BLE5 stack.
I see that in the BLE user configuration, "const drvTblPtr_t driverTable" contains also a "cryptoDrvTbl" that is valid and filled, pointing to AESCCM_* and AESECB_* functions.
Therefore I have the impression that the stack is already prepared for encryption.
The stack documentation says, that the GAPBondMgr is required for security, which can do pairing and bonding. I do not think that I require pairing at all. The question is, if the GAPBondMgr is the only means to set up an encrypted connection to another device, or if there is some simpler way to just activate encryption to a single other known device.
Also, is a full pairing required in order to enable encryption?
Thank you!
Harald