zephyr indication registration & enable

RE: zephyr indication registration & enable

Håkon Alseth — Fri, 15 Feb 2019 14:32:06 GMT

Notification and indication is more or less the same, just that indication is ACKed on a application level (and on the link-layer for that matter).

It looks like it uses the same members etc, just that the .value member has a different value. Here from the shell application:

https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/shell/gatt.c#L442

If you still have issues handling the CCCDs, I'd recommend that you reach out in one of the zephyr channels.

Cheers,

Håkon

RE: zephyr indication registration & enable

mrowe — Thu, 14 Feb 2019 19:41:43 GMT

Yep .. did the discover and know the handle of the CCCD ...but ...

The "struct bt_gatt_subscribe_params" structure does not have a .indicate member ?? so I was thinking it was incorrect to subscribe with BT_GATT_CCC_INDICATE in the notify member ... don't know about that .. but it seems wrong.

The warning appears directly after I subscribe.

RE: zephyr indication registration & enable

Håkon Alseth — Thu, 14 Feb 2019 18:26:11 GMT

Hi,

We recommend that you contact the zephyr community regarding the applications in their code base: https://www.zephyrproject.org/developers/how-to-contribute/

[quote user=""][00:00:25.559,112] <wrn> bt_ctlr_hci: handle: 0x0000, CSA: 0.[/quote]

CSA stands for "channel selection algorithm", and I assume that this is a generic warning stating that your link is using the older algorithm. This is likely not related to the crash.

[quote user=""]How do I register and enable a discovered characteristic's indication?[/quote]

The sequence in this example (https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/bluetooth/central_hr/src/main.c#L43) is that you discover the UUIDs you want, then if you have found them all; you subscribe for CCCD.

Kind regards,

Håkon