Testing direction finding beacon in nRF Connect SDK v1.5.0

[choehyunho]

Hi, teams.

I am testing nRFConnect 1.5.0 with nRF52833DK.

Recently, I noticed "Direction finding connectionless beacon" example in latest repository, and copied it to my 1.5.0 tree.

With slight modification, I managed to build the sample, but when I  executed, bt_df_set_adv_cte_tx_param() call returns error -35, which means not supported.

Is it limitation of current SDK version, or any way to fix it?

[Simonr]

Hi

Can you provide some information on what these "slight modifications" are that you did to the sample? Do you get the EINVAL error if you try building and programming the unmodified project? 

BT_FEAT_LE_CONNECTIONLESS_CTE_TX() is defined in the hci.h header file, have you included this in your project?

Best regards,

Simon

[choehyunho]

First, I already mentioned that I "backported" the sample from latest (not released) repository to SDK 1.5.0.

Please notice.

During backporting, I changed "dfe-antenna-num" to "dfe-ant-num", and removed dfe-pdu-antenna property in devicetree.

And applied AOA configuration by default, for testing.

And about BT_FEAT_LE_CONNECTIONLESS_CTE_TX(), I know it is defined in hci.h

But, it is evaluated in directions.c as below.

int bt_df_set_adv_cte_tx_param(struct bt_le_ext_adv *adv,
				const struct bt_df_adv_cte_tx_param *params)
{
	__ASSERT_NO_MSG(adv);
	__ASSERT_NO_MSG(params);

	int err;

	if (!BT_FEAT_LE_CONNECTIONLESS_CTE_TX(bt_dev.le.features)) {
		return -ENOTSUP;
	}
...

I want to know how to enable this feature.