UUID compare in CCC function (Zephyr)

RE: UUID compare in CCC function (Zephyr)

run_ar — Wed, 22 Dec 2021 14:45:03 GMT

Hi,
Sorry for the late reply. I took a closer look at one of our example applications, i.e. the RCSC example. and it seems you should register the CCCD with different handles like this:
BT_GATT_CCC(rsc_meas_ccc_cfg_changed, BT_GATT_PERM_READ | BT_GATT_PERM_WRITE),
BT_GATT_CCC(ctrl_point_ccc_cfg_changed, BT_GATT_PERM_READ | BT_GATT_PERM_WRITE),

RE: UUID compare in CCC function (Zephyr)

Christoffer Brask — Wed, 08 Dec 2021 14:15:45 GMT

Strange thing is that type = 0 which is BT_UUID_TYPE_16 and not 2 = BT_UUID_TYPE_128

RE: UUID compare in CCC function (Zephyr)

run_ar — Wed, 08 Dec 2021 14:10:07 GMT

Hi,

Sorry, not to familiar with zephyr yet, but trying to answer anyway. When the peer enables notification it writes to the attribute handle for the cccd. This means some where in the stack this must be linked to the rest of the bt_gatt_attr struct. I would guess that is happening in the application layer, so you will likely have to linke this in the application yourself. As a check, what information does this struct contain if you halt the code and check?