Zephyr and SDK5 coded phy compability

RE: Zephyr and SDK5 coded phy compability

qwertynoon — Thu, 10 Jun 2021 11:33:29 GMT

Reason

att_internal.h -

Attribute protocol handling

BT_ATT_DEFAULT_LE_MTU 23 ---

BT_ATT_DEFAULT_LE_MTU 30 +++

RE: Zephyr and SDK5 coded phy compability

qwertynoon — Wed, 09 Jun 2021 12:42:07 GMT

Thanks for reply

CONFIG_BT_LL_SW_SPLIT=n cause BT_CTLR_ADVANCED_FEATURES = n and nothing changed else

If I change BT_LE_ADV_OPT_CONNECTABLE to BT_LE_ADV_OPT_SCANNABLE then Central scan Peripheral but with wrong address and not connected

[00:06:42.515,106] [0m<inf> central_uart: Filters matched. 10:c7:d3:7d:47:ec[0m
[00:06:42.516,815] [0m<inf> central_uart: Connection pending[0m
[0m
[00:06:45.516,784] [0m<inf> central_uart: Failed to connect to 10:C7:D3:7D:47:EC (random) (2)[0m
[00:06:45.622,497] [0m<inf> central_uart: Filters matched. 10:c7:d3:7d:47:ec[0m
[00:06:45.624,206] [0m<inf> central_uart: Connection pending[0m

10:C7:D3:7D:47:EC - this is wrong address of Peripheral

RE: Zephyr and SDK5 coded phy compability

Sigurd — Wed, 09 Jun 2021 12:26:25 GMT

I see you have

CONFIG_BT_LL_SW_SPLIT=y

on the peripheral, do you see any changes if you set

CONFIG_BT_LL_SW_SPLIT=n

RE: Zephyr and SDK5 coded phy compability

qwertynoon — Wed, 09 Jun 2021 09:02:28 GMT

I think the reason is here

BT_LE_ADV_PARAM_INIT(
                     BT_LE_ADV_OPT_CONNECTABLE |
                     BT_LE_ADV_OPT_SCANNABLE |
				     BT_LE_ADV_OPT_EXT_ADV |
				     BT_LE_ADV_OPT_CODED,
				     100,
				     100,
				     NULL);

When I put BT_LE_ADV_OPT_CONNECTABLE and BT_LE_ADV_OPT_SCANNABLE together then I get an error

[1;33m<wrn> bt_hci_core: opcode 0x2036 status 0x12

Without BT_LE_ADV_OPT_CONNECTABLE Central receive advertising but with error