CC2652R: GATT client, handle storage

Tomáš L.

Part Number: CC2652R

Hello,

Could someone explain to me how handles are stored in the GATT client (central device)?
I have one central device and three identical peripherals. All peripherals have the same GATT characteristics database.

The response to GATT_DiscCharsByUUID (for SIMPLEPROFILE_CHAR1_UUID) returns the same charHandle value for all peripherals.

I would expect handles to be stored separately for each peripheral (connection).
Even if I change the characteristic properties in one peripheral, it still returns the same handle.

I also found that the handle value is valid even after reconnecting the device.
Can you confirm that the handle remains in memory even after disconnecting the peripheral?

Thanks,
Thomas

over 1 year ago

0 Tomáš L. over 1 year ago

Prodigy 40 points

The Central device is able to send GATT_WriteNoRsp on charHandle even if GATT_DiscCharsByUUID was never called.
It seems that the charHandle is not a handle to the GATT client, but to the GATT server database.

This will probably be the reason why the handle is the same for all peripherals and works even after reconnecting.

0 David over 1 year ago in reply to Tomáš L.

TI__Genius 15535 points

Hello Tomas,

Each peripheral will be addressed by its own connHandle (found inside gattMsgEvent_t).

For instance, when using api calls as GATTServApp_ProcessCCCWriteReq() or GATTServApp_ReadRsp() you need to pass the connHandle as well as the attribute handle, which is also defined as the offset.

Are you using any out of the box example I can use as reference?

BR,

David.

Bluetooth®︎

Bluetooth forum

CC2652R: GATT client, handle storage