CC2340R5-Q1: How does CC2340 use the bonding process?

Hi Preston, 

Sorry for the delay. 

I can test this on my side, but do you mind sending me your pairing handler code?

Additionally, I see that the device should be the one initiating pairing. Are they already bonded by any chance? To make sure, do a full chip erase on both devices and conduct the test again.

Best,

Nima Behmanesh

Hi Nima,

test_basic_ble_LP_EM_CC2340R5_freertos_ticlang.zip

This is my pairing handler code.（scan role. In the syscfg file, broadcast role use the same BLE pairing configuration）

Actually, I didn't see the report for the BLEAPPUTIL_PAIRING_STATE_BOND_SAVED event, so I don't know if it was bonded. But I can't see the code of the internal implementation, is there any way to confirm this. Is there a function like querying a bond list?

Nima said:

To make sure, do a full chip erase on both devices and conduct the test again.

I did a sector erase when I loaded the program. I restarted after the log showed that pairing was complete and still needed to be repaired.

Preston

Best regards

Hi Nima

Is there a switch that enables the nv storage function?

Preston

Best regards

Hi Preston,

Sorry for the delay, I can take a look at your test project and see what's going on.

Peisheng Yang said:

Is there a function like querying a bond list?

You can use this function to see if the device is in the bond list: TI BLE5-Stack API Documentation: GAPBondMgr

I'll provide an update this Friday.

Best,

Nima Behmanesh

Hi Preston,

the OSAL_SNV driver wraps around the NV driver so there's no switch:

https://dev.ti.com/tirex/content/simplelink_lowpower_f3_sdk_8_10_01_02/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory-cc23xx.html?highlight=osal#osal-simple-nv-osal-snv

Has more information about OSAL_SNV.

Best,

Nima Behmanesh

Hi Preston,

When doing the initial bonding, are you receiving the encryption complete event?

Best,

Nima Behmanesh