Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

Markus Proeller — Fri, 28 Mar 2025 10:44:27 GMT

I had the same issue with a custom board. I was missing the

config BT_CTLR
default BT

entry in Kconfig.<myboard> file

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

CktDesigner — Wed, 05 Feb 2025 18:43:24 GMT

OK, thanks. It sounds like I should get the Nordic version to build in my project.

Here is a link to the other case: (Missing Forum Thread)

I just asked there how to make that case private so I can share the entire project.

Thanks again!

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

Vidar Berg — Wed, 05 Feb 2025 10:13:39 GMT

We recommend using the Softdevice controller. We are contributing to the development of the open source Zephyr controller as well, but we are not doing the Bluetooth qualification (Bluetooth DNs and QDIDs) and SDK release testing for this controller as we are doing for the softdevice controller. I would be happy to investigate the build issue you're experiencing with the softdevice controller if you could create a private ticket and provide your board files (if you have defined your own SDK board) and project.

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

CktDesigner — Tue, 04 Feb 2025 22:11:59 GMT

Thanks... Changing to bt_hci_controller from bt_hci_sdc also allows my project to compile. My understanding is that this is selecting the Zephyr bluetooth solution vs the Nordic Soft Device. I'm looking for a comparison between the two solutions (pros/cons) so I can decide if it is worth pursuing getting this to compile with bt_hci_sdc.

Thanks again!

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

PuffinEgg — Tue, 04 Feb 2025 17:58:54 GMT

Thank you! I now see the node is disabled in nrf52832.dtsi. I was able to get my project to build successfully :).

Migrating from 2.7.0 to 2.9.0 turns out to be much simpler compared to the migration from 2.5.0 to 2.7.0 (sysbuild and hw model v2).

RE: Encounter device tree build error when building zephyr BLE peripheral example with zephyr LL software stack (NCS 2.7.0 -> NCS 2.9.0)

Vidar Berg — Tue, 04 Feb 2025 11:20:26 GMT

Hi,

The "bt_hci_controller" node is disabled by default: https://github.com/nrfconnect/sdk-zephyr/commit/e88198c09a18ebf8a12aa0674cf535433d105018. To select the Zephyr controller, please try using the following overlay:

/ {
	chosen {
        zephyr,bt-hci = &bt_hci_controller;
	};
};

&bt_hci_sdc {
    status = "disabled";
};

&bt_hci_controller {
    status = "okay";
};

Best regards,

Vidar