bt_enable() failed after bt_disable() in nrf5340

RE: bt_enable() failed after bt_disable() in nrf5340

Chao W — Mon, 04 Aug 2025 21:43:59 GMT

I removed the "CONFIG_SOC_NRF53_CPUNET_ENABLE=y" entry from my prj.conf file which let me turn the network core on and off using shell commands and bt_enable() and bt_disable().

This might not be a viable workaround if you need to use network core resources before calling bt_enable() though.

I've attached the modified extended advertising sample that I used for testing this. The sample fails to turn the network core back on after issuing the "ble disable" then "ble enable" commands. Comment out the "CONFIG_SOC_NRF53_CPUNET_ENABLE=y" entry in the prj.conf file and the "ble disable" "ble enable" commands should work as intended.

devzone.nordicsemi.com/.../advertiser.zip

RE: bt_enable() failed after bt_disable() in nrf5340

Rick T — Mon, 04 Aug 2025 16:16:38 GMT

And what was the solution?

RE: bt_enable() failed after bt_disable() in nrf5340

Chao W — Fri, 25 Jul 2025 17:30:01 GMT

Hi!

I ran into this issue on ncs3.1.0preview4 as well and found CONFIG_SOC_NRF53_CPUNET_ENABLE=y to be the cause of the endpoint binding failure for my project.

I was able to confirm using a modified extended advertising scanner sample with a slightly stripped down set of conf files from my project.

RE: bt_enable() failed after bt_disable() in nrf5340

Ben_Squar3d — Fri, 11 Jul 2025 13:37:39 GMT

Hi, sorry to hijack the post, with ncs3.0.2, it does not solve the issue.

RE: bt_enable() failed after bt_disable() in nrf5340

Einar Thorsrud — Thu, 19 Sep 2024 12:17:47 GMT

Hi,

I suspect that MPSL is still enabled. Does adding CONFIG_BT_UNINIT_MPSL_ON_DISABLE=y resolve it? See this post for more.