Warnings during configuration stage of build for nrf/samples/bluetooth/hci_lpuart in v3.0.2 and v3.1.1 and other levels

[Burt]

Hello,

I started off doing a v3.1.1 build and got this serious warning message

warning: BT_CTLR_DTM_HCI (defined at subsys/bluetooth/controller/Kconfig.dtm:14) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DTM_HCI_SUPPORT (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DTM_HCI 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.

Because my colleague is using nRF SDK v3.0.2, I switched to that and found even more warnings: the one mentioned above is preceded by

warning: UART_1_NRF_HW_ASYNC (defined at drivers/serial/Kconfig.nrfx_uart_instance:51) was assigned
the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
(!UART_NRFX_UARTE_ENHANCED_RX) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
UART_1_NRF_HW_ASYNC 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: UART_1_NRF_HW_ASYNC_TIMER (defined at drivers/serial/Kconfig.nrfx_uart_instance:83) was
assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
UART_1_NRF_HW_ASYNC (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
UART_1_NRF_HW_ASYNC_TIMER 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.

I have to take all these warnings seriously. Past experience is 1) they usually happen only if I modify off the shelf prj.conf (no mods being done here) 2) I won't end up with what I asked for if I ignore the warnings.

Aside, it took me a few tries to convince my colleague that they exist--he assumed that they would be colored. So I would say that it would be a big help for everybody if they <were> colored yellow or something similar.

Please help me proceed! Thanks.

Burt Silverman

[Sigurd Hellesvik]

Hi,

Did you change anything in the sample?

What build configurations are you using?

Regards,
Sigurd Hellesvik

[Burt]

I did not change anything in the sample--and the problem was seen by a colleague in addition to myself.

I use the SDK versions that I mentioned above.

The commands I use are

$ rm -rf build

$ west build -b nrf9160dk/nrf52840.

Thank you, Sigurd.

Burt Silverman

[Sigurd Hellesvik]

I started off doing a v3.1.1 build and got this serious warning message

warning: BT_CTLR_DTM_HCI (defined at subsys/bluetooth/controller/Kconfig.dtm:14) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DTM_HCI_SUPPORT (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DTM_HCI 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.

Im checking this with the codeowner of the sample.

Because my colleague is using nRF SDK v3.0.2, I switched to that and found even more warnings: the one mentioned above is preceded by

warning: UART_1_NRF_HW_ASYNC (defined at drivers/serial/Kconfig.nrfx_uart_instance:51) was assigned
the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
(!UART_NRFX_UARTE_ENHANCED_RX) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
UART_1_NRF_HW_ASYNC 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: UART_1_NRF_HW_ASYNC_TIMER (defined at drivers/serial/Kconfig.nrfx_uart_instance:83) was
assigned the value '2' but got the value ''. Check these unsatisfied dependencies:
UART_1_NRF_HW_ASYNC (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
UART_1_NRF_HW_ASYNC_TIMER 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.

This failed in v3.0.2 due to the Deprecation of CONFIG_UART_x_NRF_HW_ASYNC. From what I can see UART_NRFX_UARTE_ENHANCED_RX was used instead, causing the warnings. 

However, in v3.1.1 this deprecation has been reverted. 

Aside, it took me a few tries to convince my colleague that they exist--he assumed that they would be colored. So I would say that it would be a big help for everybody if they <were> colored yellow or something similar.

The warnings are from the Zephyr build system, so if you want to make a feature request for this, I suggest that you make it to the Zephyr project.

[Sigurd Hellesvik]

I started off doing a v3.1.1 build and got this serious warning message

warning: BT_CTLR_DTM_HCI (defined at subsys/bluetooth/controller/Kconfig.dtm:14) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DTM_HCI_SUPPORT (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DTM_HCI 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.

This configuration is for the possiblility to use Direct Test Mode over HCI. This is for specific testing, and not a generic Bluetooth feature.

If you do not need this feature, you can safely ignore this warning.

[Burt]

Thank you very much, Sigurd. I will close the ticket.

Burt