nRF SDK 2.9.2: BT_CTLR_RX_BUFFERS unsatisfied dependencies: BT_LL_SW_SPLIT (=n)

[Leiser]

I need help with this issue. I'm updating the code from SDK 2.4.2 to SDK 2.9.2. I had change the device tree to HWM2 and I'm using sysbuild.

The build log is showing this warning:

warning: BT_CTLR_RX_BUFFERS (defined at subsys/bluetooth\controller/Kconfig:225) was assigned the
value '10' 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_RX_BUFFERS 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.

After I had set CONFIG_BT_LL_SW_SPLIT in HCI_IPC_CONF I got more errors:

After a day trying to figure out what I'm missing I decided to use the hello world sample with nrf5340dk and I got the same error. Below I copied the log.

./cfs-file/__key/communityserver-discussions-components-files/4/compilation-log.txt

Here my test code using the hello_world sample.

/cfs-file/__key/communityserver-discussions-components-files/4/0005.hello_5F00_world.zip

[Susheel Nuguru]

Hi, 

This looks like very similar issue like the one that is mentioned and discussed here. Can you try the --no-sysbuild with the build command and see if that helps?

[Leiser]

Thanks for the advice, but It did not work. 

FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/b620d30767/opt/bin/python.exe '-Bc:\Work\nrf-samples\hello_world\app\build' -GNinja -DBOARD=nrf5340dk/nrf5340/cpuapp -DNCS_TOOLCHAIN_VERSION=NONE -DCONF_FILE=prj.conf -DBOARD_ROOT=c:/work/nrf-samples/hello_world '-Sc:\Work\nrf-samples\hello_world\app'
-- Found partition manager static configuration: C:/Work/nrf-samples/hello_world/app/pm_static.yml
-- Configuring incomplete, errors occurred!
See also "C:/Work/nrf-samples/hello_world/app/build/CMakeFiles/CMakeOutput.log".
See also "C:/Work/nrf-samples/hello_world/app/build/CMakeFiles/CMakeError.log".

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

In the link you will find the complete log.

/cfs-file/__key/communityserver-discussions-components-files/4/compilation-log_2D00_20250714_2D00_0909.txt

As fair I understood, we should use sysbuild because the samples were converted to sysbuild.

From the SDK 2.7.0 relase notes:

"

Highlights

This release introduces significant, potentially breaking, changes to the SDK:

• The previous method to define a board (hardware model) is deprecated and being replaced by a new method (hardware model v2).

• The previous method to define multi-image builds (parent-child images) is deprecated and being replaced by Sysbuild (System build).

All samples and applications in the SDK have been migrated. Consult respective documentation as additional or changed parameters might be needed to build them successfully. Applications that are outside of the SDK and use custom-defined boards should not be affected by these changes. However, modifications might still be required as per the migration procedure described in Migration guide for nRF Connect SDK v2.7.0. nRF Connect for VS Code users migrating to the latest version of the SDK might be affected.

All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

"