nrf5340 - DFU WiFi - Facing BLE "Endpoint binding failed with -11" error

[Lavanya_Manohar]

Hi,
I checked DFU over Wi-Fi in a separate project (net/download) that only included DFU and Wi-Fi-related functionality. In which FOTA is working as expected.

In our custom board (nrf5340-nrf7002) and our application project includes BT-GATT, Wi-Fi, a timer counter for scheduled work, GPIO for hardware interrupts, I2C for an OLED display, and ADC functionality.

I’m now working on integrating BT - GATT to DFU working project. However, I’m encountering a BLE  issue. "<err> bt_hci_driver: Endpoint binding failed with -11"

Could you please assist with resolving this?

Here I share my project.

5824.my_fota_download.zip

[Einar Thorsrud]

Hi,

The assert indicate issues communicating with the HCI controller on the network core. Do you have a log from thet network core so that we can see what is going on there? Also, I assume BLE was working at some ponit? If so, how do you trigger this issue?

[Lavanya_Manohar]

Einar Thorsrud said:

I assume BLE was working at some ponit? If so, how do you trigger this issue?

Yes, Wifi and ble alone working fine in our board. When I try to include BLE into my (DFU + WIFI) working project facing issue.

[Einar Thorsrud]

I see, so you never had BLE working? Have you programmed the bluetooth host on the network core? Normally that will automatically be included when you build a Bluetooth sample for the application core.

[Lavanya_Manohar]

Einar Thorsrud said:

that will automatically be included when you build a Bluetooth sample for the application core.

Yes, it will be automatically included. Are there any configs or commands to verify this?

We are working with both BLE and Wi-Fi in our projects. Initially, we faced an issue, but we resolved(Case link) it by adding the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC configuration in the network core via the hci_ipc.conf file.

However, after including DFU, the same issue has resurfaced.

[Einar Thorsrud]

Hi,

Lavanya_Manohar said:

Yes, it will be automatically included. Are there any configs or commands to verify this?

To verify that it actually happens, observe that hci_ipc or hci_rpmsg (depending on SDK version) is being built when you build the projejct. As that is the end result you are looking for.

Regarding configuration, if you are using sysbuild (typically using SDK 2.7 or newer), you should set NRF_DEFAULT_IPC_RADIO and to NETCORE_IPC_RADIO_BT_HCI_IPC as you can see is done in Kconfig.sysbuild in the Bluetooth samples. If using an older SDK that does not use sysbuild, you get the hci_rpmsg child image automatically added if you build a Bluetooth projct for the application core (you can see that you get hci_rpmsg child image related configs in the generated .config).

Lavanya_Manohar said:

However, after including DFU, the same issue has resurfaced.

Then I suspect that you do not configure the same clock source in the bootloader? If the bootloader? As these are separate images, you need to configure the correct clock source in all. Also, clock configuration is handled by the applicaiton core, so you only need to specify the source there (but in all binaries that run there and use the LF clokc source, which typically means MCUboot and your application).

[Lavanya_Manohar]

Einar Thorsrud said:

If using an older SDK that does not use sysbuild, you get the hci_rpmsg child image automatically added if you build a Bluetooth projct for the application core (you can see that you get hci_rpmsg child image related configs in the generated .config).

I'm using 2.6.1 SDK. 

Are you suggesting us to try latest version? 

Here I share the mcuboot conf files, build logs and generated .config of network.

And I have already attached my project zip for your reference. Kindly check.

child_image/mcuboot.conf

CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y

child_image/mcuboot/nrf7002dk_nrf5340_cpuapp.conf

#
# Copyright (c) 2023 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# MCUboot configurations to host the secondary image slot on the mx25r64 external flash memory.

# General
CONFIG_FLASH=y
CONFIG_MULTITHREADING=y
CONFIG_MAIN_STACK_SIZE=4096

# Serial Peripheral Interface (SPI)
CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_SPI_NOR_SFDP_DEVICETREE=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096

# MCUBoot and Partition Manager
CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y
CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x20000
CONFIG_BOOT_MAX_IMG_SECTORS=256
CONFIG_BOOT_ERASE_PROGRESSIVELY=y
CONFIG_SOC_FLASH_NRF_EMULATE_ONE_BYTE_WRITE_ACCESS=y

# Use minimal C library instead of the Picolib
CONFIG_MINIMAL_LIBC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

Output config file of network core


build log file 
build_log.zip