The official demo of AoA/AoD shows an error about cte_report_cb

[Zihao]

I got an error while building the direction finding demo In nRF Connect:

../src/main.c:254:10: error: 'const struct bt_conn_cb' has no member named 'cte_report_cb'
254 | .cte_report_cb = cte_recv_cb,
| ^~~~~~~~~~~~~
../src/main.c:254:26: warning: initialization of '_Bool (*)(struct bt_conn *, struct bt_le_conn_param *)' from incompatible pointer type 'void (*)(struct bt_conn *, const struct bt_df_conn_iq_samples_report *)' [-Wincompatible-pointer-types]
254 | .cte_report_cb = cte_recv_cb,
| ^~~~~~~~~~~
../src/main.c:254:26: note: (near initialization for 'bt_conn_cb_conn_callbacks.le_param_req')
[27/118] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_core.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'd:\AoAAoD\direction_finding_central\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

In VSCode:

I found two similar problems in Nordic DevZone, but it doesn't seem to be solved:

Direction_finding_central test

Problems building Direction_finding_central sample

Other than that, I didn't find any helpful posts using Google.

I am a beginner in BLE and just finished the basic Bluetooth course in Nordic a few days ago. So, I don't think I had any problems with my environment, In that I was able to run all the demos In Bluetooth Low Energy Fundamentals.

I directly built the demo named direction finding central without any modification, because I did not see any information in the document that necessary to be changed to build successfully. Note that I just built it, it doesn't involve flash, so I don't think it's hardware related.

In contrast, the associated demo called direction finding peripheral was build successfully without any modification.

My operating system is Windows 10.
My nRF Connect SDK is v2.5.1.in VSCode.
My Zephyr version: 3.4.99
I don't know if this is an official Sample Bug, because I'm just getting started with embedded development. Is there any information that can help me?

[Simonr]

Hi

Can you try moving the project to the C: disk (the same as where NCS is located on your computer, as I think the fact that you're trying to build the sample on a different disk than where you have NCS stored might be what is causing this. The west build is not great at jumping between disks to find functions/references if I recall correctly.

Best regards,

Simon

[Zihao]

Hi,
I once tried to copy this project to the same disk, but it didn't work [sad]. 
Actually, when I was learning the Nordic Bluetooth course, all the new projects on the D disk were built very well. 

So I still think there is something wrong (at least something not very universal) in this sample.

Now I'm testing the connectionless sample which can be built properly at least. But since it doesn't meet all my needs, I'm still following this error on the connection-based example.
I hope this problem can attract the attention of your direction finding engineers. There are three people have already encountered this problem as I mentioned earlier, but none of them have been solved yet.

Best regards,

Zihao

[Zihao]

I strongly believe that this issue is related to the version or configuration of Zephyr. Is there anything specific I should know about configuring Zephyr?

My Zephyr installation was automated by the Toolchain during the installation of the nRF Connect SDK, and it is currently at version 3.5.99. I wrote 3.4.99 in this post, but as I later tried to update to nRF Connect SDK v2.6.0, it was changed to 3.5.99.

I would greatly appreciate any possible clues you could provide. Thank you!

Yours,

Zihao