bt_enable fails when net core has Multiprotocol RPMSG or IPC Radio configured for Bluetooth and IEEE802.15.4

Hi, I recently upgraded our ncs SDK version from 2.6.0 to 2.9.0 for a custom matter application development using an nRF5340. We also support a smaller debug app that is BLE only. I noticed that on 2.6.0 we could flash the multiprotocol rpmsg child image to the net core for both the BLE builds that use bt_enable to start the stack, and the matter application. In 2.9.0 it seems like if a multiprotocol net core image is loaded, either ipc radio or multiprotocol rpmsg, bt_enable always fails with: 

<err> bt_hci_core: HCI driver open failed (-11)

Digging through the source code it looks like we time out waiting on a response from the net core. Is there a reason bt_enable wouldn't be expected to work if the net core is configured for multiprotocol operation?

Parents Reply Children
  • I am currently porting some applications for custom boards from 2.6.0 to 2.9.0 so I did integrate sysbuild and hardware model v2. The application I'm having problems with isn't a matter application, its just a bluetooth application with ble/802154 ipc_radio running on the netcore. Perhaps I'll start by programming a ble shell sample on the nrf5340dk app core and multiprotocol ipc radio on the nrf5340dk net core. Is that configuration expected to work?

Related