The prj CONFIGs gets a 'n' in build although they are y

RE: The prj CONFIGs gets a 'n' in build although they are y

Zihao — Fri, 12 Apr 2024 09:43:56 GMT

Yes I did.

But I have not solved it till now so I just look around and find a similar case here.

My case is

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

Zihao

RE: The prj CONFIGs gets a 'n' in build although they are y

Hieu — Fri, 12 Apr 2024 09:37:49 GMT

Hi Zihao,

This is a different Kconfig, so the root cause might be different. You are also noting that this happens with a sample unmodified. Therefore, I would like to ask you to open a new case for this.

You also mentioned both that a sample doesn't run, and some samples run very well. It would be great to include the details on what sample failed, and what work, in the new case.

Please also included compiled Kconfig and pristine build log in the new case.

Hieu

RE: The prj CONFIGs gets a 'n' in build although they are y

Zihao — Fri, 12 Apr 2024 08:09:49 GMT

Hi, I got something wrong like that.

The Warning:

warning: BT_DF_CONNECTIONLESS_CTE_RX (defined at
D:/ncs/v2.6.0/zephyr/subsys/bluetooth/host/Kconfig:849, subsys/bluetooth\host/Kconfig:849) was
assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: (((!BT_CTLR ||
BT_CTLR_DF_CTE_RX_SUPPORT) && BT_DF && BT_HCI_HOST && BT_RPC_STACK) || ((!BT_CTLR ||
BT_CTLR_DF_CTE_RX_SUPPORT) && BT_DF && BT_HCI_HOST && BT_HCI && BT)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BT_DF_CONNECTIONLESS_CTE_RX and/or look up
BT_DF_CONNECTIONLESS_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.

And BT_DF_CONNECTIONLESS_CTE_RX is not defined that prevents all code snippets wrapped in #if defined(CONFIG_BT_DF_CONNECTIONLESS_CTE_RX) from being compiled. So that I saw an error:

D:/AoAoD2/direction_finding_connectionless_rx/src/main.c:249: undefined reference to `bt_df_per_adv_sync_cte_rx_enable'
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'D:\ncs\toolchains\cf2149caf2\opt\bin\cmake.EXE' --build 'd:\AoAoD2\direction_finding_connectionless_rx\build'

The `bt_df_per_adv_sync_cte_rx_enable' is defined in the #if defined(CONFIG_BT_DF_CONNECTIONLESS_CTE_RX) snippets.

I know that there are some Missing dependencies. But I am confused and don't know what to do because it occurred when I build the sample named "direction finding connectionless rx" in nRF Connect SDK without any modification.

As far as I'm concerned, it should not occurred in an official demo, right?

Meanwhile, I can run other samples involved without direction finding function very well. And I installed the nRF Connect SDK on another PC, then I met the same error which proves that there is nothing wrong with my OS. And I tried change my SDK version, but it didn;t work.

Anything helpful will be appreciated! Thanks!

RE: The prj CONFIGs gets a 'n' in build although they are y

Hieu — Tue, 21 Nov 2023 13:37:07 GMT

Hi Ibrahim_Augury,

Could you please elaborate how mdell's answer didn't help? I actually found that it is in the right direction.

Could you please also share the compiled Kconfig file and your pristine build log here?

Hieu

RE: The prj CONFIGs gets a 'n' in build although they are y

Ibrahim_Augury — Mon, 20 Nov 2023 14:05:43 GMT

This answer didnt help

RE: The prj CONFIGs gets a 'n' in build although they are y

Ibrahim_Augury — Mon, 20 Nov 2023 12:47:27 GMT

Ok I will check that
Thanks for the tip

RE: The prj CONFIGs gets a 'n' in build although they are y

mdell — Mon, 20 Nov 2023 12:43:26 GMT

But in the build logs you might see the reason why BT got deselected, something like "warning: BT (defined at X) was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: ..."

RE: The prj CONFIGs gets a 'n' in build although they are y

Ibrahim_Augury — Mon, 20 Nov 2023 12:39:20 GMT

I post the CONFIG_BT as example because it needs no dependencies

RE: The prj CONFIGs gets a 'n' in build although they are y

mdell — Mon, 20 Nov 2023 12:37:19 GMT

Can you check or post your build logs? Almost always there should be an explanation in there why the config value got deselected, most of the time missing dependencies...