• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 90 subscribers
  • Views 986 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 315939
Options

Zigbee device binding fails when using Softdevice S140 but works with only Zigbee library (i,e without Softdevice)

anusha_14

Hello Nordic Team,

The issue mentioned here is same as in  Unable to bind Zigbee end devices when using softdevice . I have created the new ticket as suggested by Nordic support team as the previous question was asked several months ago.

Here is a brief summary of the issue:

My application is based on nRF5 SDK for Thread and Zigbee v4.1.0.. I have a Nordic Zigbee application that uses libzboss.a and nrf_radio_driver_softdevice.a , with Nordic working as a coordinator. With this application, I was able to bind Zigbee end devices such as motion sensor, window sensor etc and able to receive data from them.

Later, I added softdevice s140 to my application as I wanted my application to be able to operate in either BLE mode or Zigbee mode. After adding softdevice, I had to change the radio driver to nrf_radio_driver_softdevice.a. In this new application, there is no change in code with respect to Zigbee functionality. However, I am no longer able to bind Zigbee end devices.

Some details about my application: 

Nordic can either start in BLE mode or Zigbee mode and once it starts running, it will stay in that protocol mode only. To switch protocols, I perform a restart of Nordic. 

In BLE mode, the functionality works fine as I can see that bonding to a device works fine, able to perform GATT read and write, perform scanning and advertising. But in Zigbee mode, the functionality seems to have changed as I can no longer bind a Zigbee end device.

Also, note that: 

1. It can boot up as Zigbee coordinator device and can respond to joining request from ZED but cannot bind.

2. It can boot up as BLE device, perform GATT operation, scan and after power cycle also, BLE operations work as expected.

If it helps to debug, I can share Zigbee sniffer logs from two cases that I tried.

Case 1: Nordic as Zigbee coordinator with only Zigbee support (using libzboss.a and nrf_radio_driver.a) without SoftDevice. I commissioned a ZED (window contact) and the binding was successful. This is the sniffer log. Note: Extended PAN Id of the Zigbee coordinator is F4:CE:36:48:5A:C4:22:82 and the Extended PAN Id of ZED is 00:15:BC:00:1E:01:1E:F0
 
BindSuccessNoSD.pcapng

Case 2: Nordic as Zigbee coordinator with SoftDevice (using libzboss.a and nrf_radio_driver_softdevice.a). I tried to commission a ZED (window contact) and the binding failed. This is the sniffer log.  Note: Extended PAN Id of the Zigbee coordinator is F4:CE:36:48:5A:C4:22:82 and the Extended PAN Id of ZED is 00:15:BC:00:1E:01:1E:F0

ZigbeeLogBindFail.pcapng


Please let me know if you need any other information to help in debugging this issue.

Thanks,

Anusha

Parents
  • 0

    I would like to add some info that I found going through the Zigbee sniffer log:

    For the log where binding is successful (i.e without Softdevice), it is seen that Nordic acknowledges the data request from ZED after association response is sent.



    However, in the log where the binding fails (i.e with Softdevice), it is seen that Nordic does not acknowledge the data request from ZED after association response:


    Regards,

    Anusha

Reply
  • 0

    I would like to add some info that I found going through the Zigbee sniffer log:

    For the log where binding is successful (i.e without Softdevice), it is seen that Nordic acknowledges the data request from ZED after association response is sent.



    However, in the log where the binding fails (i.e with Softdevice), it is seen that Nordic does not acknowledge the data request from ZED after association response:


    Regards,

    Anusha

Children
No Data
Related
Terms of service