Zigbee and BLE coex support using NCS v1.3.0

[Sridhar Jonnavittula]

Hi Team,

I am using nRF Connect SDK v1.3.0 tag for nRF52840 DK.

I am trying to integrate BLE HCI UART project files into Zigbee light switch project.

I have attached modified

app.overlay

/* Copyright (c) 2020 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: Apache-2.0
 */

/ {
	chosen {
		zephyr,entropy = &rng;
	};
};


&uart0 {
	compatible = "nordic,nrf-uart";
	current-speed = <1000000>;
	status = "okay";
};

prj.conf

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

CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_SERIAL=y
CONFIG_GPIO=y

# Make sure printk is not printing to the UART console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

CONFIG_HEAP_MEM_POOL_SIZE=2048

CONFIG_ZIGBEE=y
CONFIG_ZIGBEE_ROLE_END_DEVICE=y

# Enable bonding
CONFIG_NVS=y

# Enable DK LED and Buttons library
CONFIG_DK_LIBRARY=y

# This example requires more workqueue stack
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# Enable nRF ECB driver
CONFIG_CRYPTO=y
CONFIG_CRYPTO_NRF_ECB=y

# Cryptocell is not supported through CSPRNG driver API: NCSDK-4813
CONFIG_ENTROPY_CC310=n




CONFIG_UART_0_NRF_FLOW_CONTROL=y
CONFIG_MAIN_STACK_SIZE=512
CONFIG_BT_MAX_CONN=16
CONFIG_BT_TINYCRYPT_ECC=n
CONFIG_BT_CTLR_DTM_HCI=y
CONFIG_BT_CTLR_ASSERT_HANDLER=y
CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_H4=y
CONFIG_BT_HCI_RAW_H4_ENABLE=y
CONFIG_STDOUT_CONSOLE=n

files in Zigbee light switch project  with configuration from Zephyr BLE HCI UART.

Attached error while generating SES project.

Please point out the integration issue.

Please take a look at the attached Zigbee light switch modified project.

light_switch.rar

Thanks

Sridhar

[Marjeris Romero]

Hi Sridhar,

We don't currently have support for multiprotocol Zigbee/BLE in NCS, but our developers are working on it. My advice is to wait until this is available. In this case, as you can see in the SES error message, the issue is with the crypto libraries compatibility, but this will just be one of the many issues you will encounter. For example you need to think about how to solve the radio arbitration as well.

I recommend you wait until multiprotocol for Zigbee/BLE is added. You can talk to your regional sales manager if you have more questions regarding the scheduled timeline for this release.

Best regards,

Marjeris

[Sridhar Jonnavittula]

I know that below query may deviate this ticket but almost similar:

Is it the same case with Openthread and BLE coex like wait till included in SDK?

[Marjeris Romero]

Yes, I will recommend to wait until the nRF IEEE 802.15.4 radio driver is available for NCS: https://github.com/NordicSemiconductor/nRF-IEEE-802.15.4-radio-driver

Which will allow multiprotocol solutions between Thread/BLE and Zigbee/BLE as it does in the nRF5 SDK.

-Marjeris

[sjf]

Hi msromero,

Is BLE and Zigbee multiprotocol supported in NCS 1.4.2?

Regards

Santiago

[Marjeris Romero]

Hi,

Yes, Zigbee/BLE multiprotocol was added in NCS 1.4.0. You can take a look at the answer in this ticket for a walkthrough on how to add multiprotocol support to an sample.

Best regards,

Marjeris