Update CTE params...failed (err -134) in 'direction_finding_connectionless_tx'

[Majoris]

Hi

I'm working with the sample 'ncs1.7.1\nrf\samples\bluetooth\direction_finding_connectionless_tx' on nRF5340,  I followed this page and built with AoA mode, then added content of overlay-aoa.conf file to child_image/hci_rpmsg.conf file, ran this code:

G:\ncs_v1.7.1\ncs1.7.1\nrf\samples\bluetooth\direction_finding_connectionless_tx>west build -b nrf5340dk_nrf5340_cpuapp -- -DCMAKE_BUILD_TYPE=overlay-aoa.conf

Build and flash seems correct,  but output in putty is wrong:

*** Booting Zephyr OS build v2.6.99-ncs1-1  ***
Starting Connectionless Beacon Demo
Bluetooth initialization...success
Advertising set create...success
Update CTE params...failed (err -134)

 I tried as Amanda said, erased the kit before flash, but it doesn't help. How to solve this problem? Thanks in advance.

Best regards,

Majoris

[Saleh]

Hi

As mentioned in this document:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/direction_finding_connectionless_tx/README.html

To build this sample for nRF5340 DK, with angle of arrival mode only, add content of overlay-aoa.conf file to child_image/hci_rpmsg.conf file.

So if only AoA feature is needed not AoD, you should append this code:

# Disable AoD Feature (antenna switching) in Tx mode
CONFIG_BT_CTLR_DF_ANT_SWITCH_TX=n

to this file:

https://github.com/nrfconnect/sdk-nrf/blob/main/samples/bluetooth/direction_finding_connectionless_tx/child_image/hci_rpmsg.conf

---------------------------------------------

Anyway, error -134 means ENOTSUP, as you can find here:

https://docs.zephyrproject.org/apidoc/latest/group__system__errno.html

So this problem comes from a bad configuration file or the source code you are using (maybe an old version), doesn't support nRF5340.

Hint: If you was confused by different configuration files, temporarily you can copy all needed configurations to the main .conf file:

https://github.com/nrfconnect/sdk-nrf/blob/main/samples/bluetooth/direction_finding_connectionless_tx/prj.conf

and remove other .conf files from your project folder.

BR,

Saleh

[Majoris]

Thanks very much! 

[Saleh]

You are welcome!

Also I noticed probably another configuration is needed which is not included in .conf files. Add this line to prj.conf file:

CONFIG_BT_CTLR_DF_ADV_CTE_TX=y

Then if it worked, it is better to move it to sub-project configuration files (because it is target dependent), child_image/hci_rpmsg.conf in your case or boards/nrf52833dk_nrf52833.conf or boards/nrf52833dk_nrf52820.conf if someone is using those boards.

[WilliamES]

We have followed all the steps in this thread but the problem remains. We are using the nRF5340 as both array and tag and flashing via VSCode. Everything works as intended up until:

PER_ADV_SYNC[X]: [DEVICE]: XX:XX:XX:XX:XX:XX, tx_power XXX, RSSI XX, CTE XXX, data length X, data: XXX 

Then  "Waiting for periodic sync lost..." is returned and the board reboots and the "CTE[X]" is not received:

 CTE[X]: samples count XX, cte type XXX, slot durations: X [us], packet status XXX, RSSI XXX

Is there any progress made regarding this problem?

Best regards,

William

[Saleh]

I suppose the Zephyr upstream is ahead of what has been used in NCS. Especially new updates for direction finding has introduced into the Zephyr recently.

My suggestion is to use Zephyr directly:

https://docs.zephyrproject.org/latest/getting_started/index.html

---

And then building its example for "direction finding":

https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/direction_finding_connectionless_rx

---

While you set the target board as nrf5340:

docs.zephyrproject.org/.../index.html

Note: in README file of the above example, it has mentioned to: "To run the application on nRF5340DK, a Bluetooth controller application must also run on the network core." please refer to that description for more details.

Regards,

Saleh