bt_hci_driver: Endpoint binding failed with -11 [00:00:02.273,956]

[lara]

Hi,

I’m using the nRF5340 for a beacon development project in VS Code with nRF Connect SDK v3.1.1.

However, I’m facing the following error during initialization:

Starting Beacon Demo
[00:00:02.273,956] <err> bt_hci_driver: Endpoint binding failed with -11
[00:00:02.273,956] <err> bt_hci_core: HCI driver open failed (-11)
Bluetooth init failed (err -11)

I’ve gone through several threads discussing the same issue, but none of the suggested solutions have worked for me.

Any guidance or suggestions would be greatly appreciated, as I’m new to working with this dual-core controller.

[Susheel Nuguru]

There are multiple reasons that this could happen and this has been discussed very well in this forum, please try to see if you have flashed both cores properly with proper firmware.

[lara]

 https://devzone.nordicsemi.com/f/nordic-q-a/122957/bt_hci_core-hci-driver-open-failed--11-on-nrf5340-custom-board 

here "Solved. Just wasn't clicking on the build itself when flashing so it was not flashing both cores." marked as answer

 https://devzone.nordicsemi.com/f/nordic-q-a/90145/ncs-hci-driver-open-failed--11 

here i cannot find the build\hci_rpmsg\zephyr\merged_CPUNET.hex file to flash to net core.

 https://devzone.nordicsemi.com/f/nordic-q-a/112127/nrf5340---bt_hci_core-bt_enable-no-hci-driver-registered-bluetooth-init-failed-err--19 

here they are using the cudtom board

 https://devzone.nordicsemi.com/f/nordic-q-a/90305/booting-zephyr-os-build-zephyr-v3-1-0-2256-gdddb5dd6b0de-starting-beacon-demo-bluetooth-init-failed-err--11-00-00-01-262-176-bt_hci_driver-endpoint-binding-failed-with--11-00-00-01-262-207-bt_hci_core-hci-driver-open-failed-- 

here i cannot find the proper solution

non of these threads give me proper solution and still not able to figure out what causes the issue while using nrf5340dk.

all solved their problem by themselves and most of them using custom board.

can u guide me whats the exact step i need to follow

[lara]

I have now compiled the same firmware for both the NetCore and the AppCore, and flashed them separately.

My DK is advertising correctly, but on another COM port I’m getting the following error:

Starting Beacon Demo
[00:00:02.272,308] <err> bt_hci_driver: Endpoint binding failed with -11
[00:00:02.272,308] <err> bt_hci_core: HCI driver open failed (-11)
Bluetooth init failed (err -11)

Is it okay to keep it like this, or does this indicate a problem?

[Susheel Nuguru]

This is not okay as the application core and the network core wont be able to communicate if HCI did not open properly.

lara said:

I have now compiled the same firmware for both the NetCore and the AppCore, and flashed them separately.

What do you mean by this? You should not flash the same image onto both cores. The child image that needs to be flashed onto the Netcore for bluetooth samples to work on APP core is samples/bluetooth/hci_rpmsg.

Please read this documentation properly to understand how these cores communciate and what you need to flash to each core.

[lara]

Susheel Nuguru said:

samples/bluetooth/hci_rpmsg.

i cannot find any file in this name hci_rpmsg,should i create it

[Susheel Nuguru]

I am sorry lara, 

I was pointing you to the old documentation, that is my bad.

According to this migration notes

The HCI implementation for both the Host and the Controller sides has been renamed for the IPC transport. The CONFIG_BT_RPMSG Kconfig option is now CONFIG_BT_HCI_IPC, and the zephyr,bt-hci-rpmsg-ipc Devicetree chosen is now zephyr,bt-hci-ipc. The existing sample has also been renamed, from samples/bluetooth/hci_rpmsg to samples/bluetooth/hci_ipc. (GitHub #64391)

hci_rpmsg has been moved to hci_ipc