bt_dev.drv->open(); fails with bt_hci_driver: bt_rpmsg_open: Endpoint binding failed with -11 error

[PoloMetyos]

Hi everyone,

I am trying to transfer a code that is working on nRF5340 DK to a custom board also using a nRF5340.

I don't know if it matters, but the custom board has the nRF5340-CLAA (WLCP package) version and I didn't do any changes regarding this package change.

The software crashes when bt_enable(NULL) is called with the following errors, pointing to bt_dev.drv->open() failing:

[00:00:01.016,784] <err> bt_hci_driver: bt_rpmsg_open: Endpoint binding failed with -11
[00:00:01.025,756] <err> bt_hci_core: bt_enable: HCI driver open failed (-11)
[00:00:01.033,813] <err> ble: ble_init: BLE enable failed (err -11)
[00:00:01.040,985] <err> main: main: Failed to init BLE

I flash the device with VSCode and nRF Connect so normally net cpu and app cpu should be flashed at the same time.

Reading memory with nrfConnect Programmer shows that the netcpu has indeed something flashed.

I also manually programmed the net cpu with nrfjprog with merged_CPUNET.hex but it didn't help.

Do you have any leads for me to look at to try to solve this ? Thank you !

[Sigurd]

Hi,

Could you try to fully erase the nRF5340 and flash it again?

 

# recover network core
nrfjprog --recover -f nrf53 --coprocessor CP_NETWORK
# recover app core
nrfjprog --recover -f nrf53

If that does not work, check your clock configs

 nRF5340 Peripheral BLE connections always fail with reason 0x3e (62) 

[PoloMetyos]

Hi,

It was a clock config issue, I have no external LF quartz and only configured the internal RC clock for app core on not network core. So if it can help other people, the LF quartz must be activated in prj.conf of both app cpu and net cpu with :

CONFIG_SOC_ENABLE_LFXO=n

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

Thank you for your help !