Build Error when configuring the AOA example on nrf52833dk_nrf52833 dk

[Zephyr]

I am trying to build the code for AOA example for nrf52833dk_nrf52833 dk from the example code avaliable on the sample called direction_finding_central. i have nrf connect sdk version of 3.1.0. When i try to just build the code using this build configuration

With sysbuild being default i got the following  build errors:

```

C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/src/main.c:283:10: error: 'const struct bt_conn_cb' has no member named 'cte_report_cb'
283 | .cte_report_cb = cte_recv_cb,
| ^~~~~~~~~~~~~
C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/src/main.c:283:26: warning: initialization of 'void (*)(void)' from incompatible pointer type 'void (*)(struct bt_conn *, const struct bt_df
_conn_iq_samples_report *)' [-Wincompatible-pointer-types]
283 | .cte_report_cb = cte_recv_cb,
| ^~~~~~~~~~~
C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/src/main.c:283:26: note: (near initialization for 'bt_conn_cb_conn_callbacks.recycled')
[74/264] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_packaged.c.obj
ninja: build stopped: subcommand failed.
FAILED: _sysbuild/sysbuild/images/direction_finding_central-prefix/src/direction_finding_central-stamp/direction_finding_central-build C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/build
/_sysbuild/sysbuild/images/direction_finding_central-prefix/src/direction_finding_central-stamp/direction_finding_central-build
cmd.exe /C "cd /D C:\Users\hp\Desktop\Projects\RE96\direction_finding_central\build\direction_finding_central && C:\ncs\toolchains\b8b84efebd\opt\bin\cmake.exe --build ."
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b8b84efebd\opt\bin\cmake.EXE' --build C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/build

```

I also get this as well which is strange

```

warning: BT_DF_CONNECTION_CTE_RX (defined at C:/ncs/v3.1.0/zephyr/subsys/bluetooth/host/Kconfig:948,
subsys/bluetooth\host/Kconfig:948) was assigned the value 'y' but got the value 'n'. Check these
unsatisfied dependencies: (((!HAS_BT_CTLR || BT_CTLR_DF_CTE_RX_SUPPORT) && BT_DF && BT_HCI_HOST &&
BT_RPC_STACK) || ((!HAS_BT_CTLR || BT_CTLR_DF_CTE_RX_SUPPORT) && BT_DF && BT_HCI_HOST && BT_HCI &&
BT)) (=n). See docs.zephyrproject.org/.../kconfig.html
and/or look up BT_DF_CONNECTION_CTE_RX in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.

warning: BT_DF_CONNECTION_CTE_REQ (defined at
C:/ncs/v3.1.0/zephyr/subsys/bluetooth/host/Kconfig:962, subsys/bluetooth\host/Kconfig:962) was
assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
((BT_DF_CONNECTION_CTE_RX && BT_DF && BT_HCI_HOST && BT_RPC_STACK) || (BT_DF_CONNECTION_CTE_RX &&
BT_DF && BT_HCI_HOST && BT_HCI && BT)) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_DF_CONNECTION_CTE_REQ in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BT_LL_SW_SPLIT (defined at subsys/bluetooth\controller/Kconfig:145) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies:
DT_HAS_ZEPHYR_BT_HCI_LL_SW_SPLIT_ENABLED (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_LL_SW_SPLIT in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

warning: BT_CTLR_DF_ANT_SWITCH_RX (defined at subsys/bluetooth\controller\Kconfig.df:83) was
assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
BT_CTLR_DF_CTE_RX (=n), BT_CTLR_DF_ANT_SWITCH_2US_SUPPORT (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DF_ANT_SWITCH_RX in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BT_CTLR_DF_CTE_RX (defined at subsys/bluetooth\controller\Kconfig.df:91) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DF_CTE_RX_SUPPORT
(=n). See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DF_CTE_RX in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

warning: BT_CTLR_DF_CONN_CTE_REQ (defined at subsys/bluetooth\controller\Kconfig.df:99) was assigned
the value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DF_CONN_CTE_RX
(=n). See docs.zephyrproject.org/.../kconfig.html and/or
look up BT_CTLR_DF_CONN_CTE_REQ in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

warning: BT_CTLR_DF_CONN_CTE_RX (defined at subsys/bluetooth\controller\Kconfig.df:138) was assigned
the value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DF_CTE_RX (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DF_CONN_CTE_RX in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BT_CTLR_ADVANCED_FEATURES (defined at subsys/bluetooth\controller\Kconfig.ll_sw_split:314)
was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
BT_LL_SW_SPLIT (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_ADVANCED_FEATURES in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BT_CTLR_LLCP_LOCAL_PROC_CTX_BUF_NUM (defined at
subsys/bluetooth\controller\Kconfig.ll_sw_split:1050) was assigned the value '6' but got the value
''. Check these unsatisfied dependencies: BT_LL_SW_SPLIT (=n). See
docs.zephyrproject.org/.../kconfig.html and/or
look up BT_CTLR_LLCP_LOCAL_PROC_CTX_BUF_NUM in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.

warning: Experimental symbol BT_DF is enabled.

```

Can anyone explain the reason. Thanks.

[tesc]

Hi,

I am afraid I am unable to reproduce. Is this the unmodified nRF Connect SDK v3.1.0, and the unmodified direction_finding_central sample?

I have tried to build that one with the same configuration settings, and I am not able to reproduce. In my end, everything builds.

Please note however that when you have already chosen the Board target of nrf52833dk/nrf52833, it is not necessary to choose any of the fragments or overlays. I don't think that is the cause of the build errors, though, since my testing here do not reproduce the errors even for a build configuration with those added.

Can you please double check that you do have the latest version of VS Code, the latest version of the nRF Connect for VS Code extension, and a fresh install of nRF Connect SDK?

Might it be that the sample, which I see is located at C:/Users/hp/Desktop/Projects/RE96/direction_finding_central/, is from a different (older) version of the SDK?

Does the unmodified sample at <sdk location>\nrf\samples\bluetooth\direction_finding_central\ build directly, when not copied to a separate folder?

Regards,
Terje

[Zephyr]

`<sdk location>\nrf\samples\bluetooth\direction_finding_central\`

It seems to work at this directory,  i was choosing the sample from zephyr\samples\bluetooth\direction_finding_central\  first can that be an issue ?

[tesc]

Hi,

I have now tested the sample from the zephyr part of the SDK, and can confirm the build fails.

Please use the sample from the nrf part of the SDK, as that sample is the one which is tested on and intended for the nRF52833 DK. In general the recommendation is to use samples from the nrf part of the SDK.

Regards,
Terje