This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2538EMK: How to Configure CC2538EM devices as a Coordinator and End Devices?

Part Number: CC2538EMK
Other Parts Discussed in Thread: Z-STACK, CC2531, LAUNCHXL-CC2650, CC2538

Hello,

I  am new to this Zigbee environment. I know little bit knowledge about it. 

I have a two CC2538EM devices. I want to make them as a one coordinator and another one End device. I am using  Z-Stack 3.0.0 and Z-Tool 2.0.

Yes I successfully configured one device as a Coordinator . I followed this  link .But i am unable to configured another device as a End device.

Please help me anyone.

Thanks in Advance,

Amar.

  • You can write ZCD_NV_LOGICAL_TYPE to 2 which means end device.
  • Thanks for reply YK Chen,

    I didn't find anywhere ZCD_NV_LOGICAL_TYPE in Z-Tool. My Device Configurations like this.

  • You still have to do all other steps like assign primary/secondary channels and start commissioning to make it start sending beacon requests to join Zigbee network.
  •  I followed below steps. 

    3. You can run the following MT commands to setup Zigbee 3.0 router.
    
    10:43:43.75 COM99 SYS_OSAL_NV_WRITE (0x2109) --> Write ZCD_NV_LOGICAL_TYPE to 1 which means router
        Id: 0x0087
        Offset: 0x00
        Len: 0x01
        Value: . (0x01)
    
    10:43:59.35 COM1 APP_CNF_BDB_SET_CHANNEL (0x2F08) --> Set Primary channel mask to channel 13 only
        isPrimary: TRUE (0x1)
        Channel: CHNL_0x00002000 (0x2000)
    10:43:59.35 COM1 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
        Status: SUCCESS (0x0)
    
    10:44:11.43 COM1 APP_CNF_BDB_SET_CHANNEL (0x2F08) --> Set Secondary channel to 0x0 to disable secondary channel mask
        isPrimary: FALSE (0x0)
        Channel: NONE (0x0)
    10:44:11.45 COM1 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
        Status: SUCCESS (0x0)
    
    10:44:26.46 COM99 APP_CNF_BDB_START_COMMISSIONING (0x2F05) --> Start commissioning using network steering as parameter to make device to start scan Zigbee network to join
        CommissioningMode: (0x02) Network Steering (0x2)
    
    10:44:26.46 COM99 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
        Status: SUCCESS (0x0)
    
    10:44:26.56 COM99 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
        Status: 1 (0x1)
        Commissioning Mode: 0x01 (Network Steering) (0x1)
        Commissioning Mode: 0 (0x0)
    
    10:44:26.8 COM99 ZDO_STATE_CHANGE_IND (0x45C0)
        State: INVALID_PARAMETER (0x2)
    
    10:44:27.11 COM99 ZDO_STATE_CHANGE_IND (0x45C0)
        State: INVALID_PARAMETER (0x2)
    
    10:44:27.37 COM99 ZDO_STATE_CHANGE_IND (0x45C0)
        State: 3 (0x3)
    
    10:44:27.88 COM99 ZDO_STATE_CHANGE_IND (0x45C0)
        State: 5 (0x5)
    
    10:44:28.24 COM99 ZDO_STATE_CHANGE_IND (0x45C0)
        State: 7 (0x7)
    
    10:44:28.9 COM99 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
        Status: 0x00 (Success) (0x0) --> Router joins coordinator successfully
        Commissioning Mode: 0x01 (Network Steering) (0x1)
        Commissioning Mode: 0 (0x0)
    
    11:03:22.81 COM99 UTIL_GET_DEVICE_INFO (0x2700)--> Get device info to confirm router is setup correctly
    
    11:03:22.81 COM99 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
        Status: SUCCESS (0x0)
        IEEEAddr: 0x00124B0000E50127
        ShortAddress: 0x4EE6
        DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
        DeviceState: DEV_ROUTER (0x7)
        NumAssocDevices: 0x00
        AssocDevicesList
     
    4. On Ztool of coordinator, you should see ZDO_END_DEVICE_ANNCE_IND pops when router joins coordinator.
    
    10:44:28.84 COM1 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
        SrcAddr: 0x4EE6
        NwkAddr: 0x4EE6
        IEEEAddr: 0x00124B0000E50127
        Capabilities: 0x8E

    Successfully configured Coordinator and Router. But didn't get this info

    4. On Ztool of coordinator, you should see ZDO_END_DEVICE_ANNCE_IND pops when router joins coordinator.

    10:44:28.84 COM1 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
        SrcAddr: 0x4EE6
        NwkAddr: 0x4EE6
        IEEEAddr: 0x00124B0000E50127
        Capabilities: 0x8E

    in coordinator.

    Here got little bit confused. To send data from coordinator,which one is required (Router or End Device). Here pan id is required for coordinator and end device join the network?

    Can you please tell about Router and End device.

  • Both router and end device can receive data from coordinator. Router is a Zigbee device with routing capability which means it can help to forward messages for others in Zigbee network and its receiver is always turned on so it would consume more power. End device usually is under sleeping and use polling to receive data, which is more power saving but might have latency when receiving data due to longer polling rate.
  • Thanks for YK chen,

    In my case don't want use router. Later I will use router.

    Initially i  want to communicate with end device without using router. But when i followed that document. 

    The device has configured as a router.How to configure end device. The same pan id should required for both devices?.

    Thanks and regards,

    Amar.

  • As I already replied, do SYS_OSAL_NV_WRITE (0x2109) ZCD_NV_LOGICAL_TYPE to 2 in 1st step of3 and keep all other steps the same .
  • Thanks YK chen,

    I had been set  SYS_OSAL_NV_WRITE (0x2109)  to 2 for configuring End device. When I see the  UTIL_GET_DEVICE_INFO. 

    The device has showing below info.

    <TX>10:14:32.08 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>10:14:32.08 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_INIT (0x1)
    NumAssocDevices: 0x00
    AssocDevicesList

    I didn't get a End device.

    Thanks in Advance,

    Amar.

  • You have to enable permit join on coordinator to allow end device to join and DeviceState will turn to END_DEVICE after it joins a Zigbee network.
  • Where I have to enable permit join on a Coordinator. I saw ZB_PERMIT_JOINING_REQUEST. Is this correct?.
  • Yes, you can use ZB_PERMIT_JOINING_REQUEST to enable permit join.
  • Thanks YK Chen,

    I tried with Destination =1 and Duration = 60 in ZB_PERMIT_JOINING_REQUEST at Simple API. 

    But the device will not turn into End Device. 

    <TX>12:00:20.56 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>12:00:20.56 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_INIT (0x1)
    NumAssocDevices: 0x00
    AssocDevicesList

    Coordinator:

    End Device:

    The  device still being in DEV_INIT.

    What was correct values to enable permit join request in coordinator?

    Thanks,

    Amar.

  • I suggest you to use sniffer to check what happens over the air first.
  • What values(Destination and Timeout) I have to give to enable permit join in ZB_PERMIT_JOINING_REQUEST in Coordinator.

  • Destination should be set to 0x0000 which is coordinator's short address and timeout can be set to 180 which means enable permit join for 180 seconds.
  • Thanks  YK Chen ,

    I had set Destination set to 0x0000  and Timeout set to 180 in ZD_PERMIT_JOIN_REQUEST at Coordinator.

    And I had been wait upto 5 mins. Then when I choose UTIL_GET_DEVICE_INFO from End Device. It will showing same info.

  • I can only suggest you to use sniffer to check what happens over the air.
  • When I set the  device as a router. The  device has turn to  DEV_ROUTER . Immediately device will change to router. 

    But When I set the device as end device. The device will not turn to DEV_END_DEVICE. I have been wait couple of minutes for end device.But finally didn't get result.

    Thanks,

    Amar.

  • You need to use sniffer to check if your end device sends beacon requests to join coordinator first. Without sniffer log, I cannot judge anything further.
  • Amar,

    If you're still having issues, could you try to use Z-Stack 3.0.1 and also provide a sniffer log if possible.

    Best,
    Sean
  • Thanks Sean,

    I had test with  Z-Stack 3.0.1. There is no result. 

    Still getting the same info like DeviceState: DEV_INIT (0x1).

    <TX>11:39:55.37 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>11:39:55.37 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_INIT (0x1)
    NumAssocDevices: 0x00
    AssocDevicesList

    I have been set ZB_PERMIT_JOINING_REQUEST Destination = 0x0000 and Timeout = 180  in Coordinator side.

    After setting the ZB_PERMIT_JOINING_REQUEST in Coordinator side, we have to wait  or  the device will automatically turn to End Device.

    Thanks in Advance,

    Amar.

  • After setting the ZB_PERMIT_JOINING_REQUEST in Coordinator side, you have to do start commissioning on end device side to make it send beacon requests to join coordinator.
  • Thanks for reply YK chen,

    I did what you saying. After setting the ZB_PERMIT_JOINING_REQUEST in Coordinator side. I had start commissioning with Network Steering (0x2) on end device side. Only one time is enough for start

    commissioning on end device.Then what to do? I have to wait for device will turn to end device?

  • I strongly suggest you to setup sniffer to check what happens over the air and attach sniffer log so I can also know where the problem is.
  • Amar,

    Testing default ZNP examples with one being a ZC and one being a ZED, following YK's guide which you referenced, I was able to successfully associate the devices and you can see that the ZED shows the DeviceState as 'DEV_END_DEVICE (0x6)'

    Below are both attached logs for setting up the ZC/ZED.COM18_ZC.rtf

    COM40_ZED.rtf

    If you still need assistance, please post a sniffer log to be able to further debug your issue.

    Best,

    Sean

  • Hi Sean,

    Thanks for response,

    Now I  will go through your configurations files for setup devices as a coordinator and end device. If I still getting issues and I will use sniffer and send to you log files.

    Best Regards,

    Amar.

  • Hi Sean,

    I just gone through your configuration files.

    Coordinator  log files:

    <TX>11:18:57.9 COM6 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

    <RX>11:18:57.9 COM6 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>11:18:57.9 COM6 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

    <RX>11:18:57.9 COM6 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    *** WARNING ***
    Unsupported or unformatted message received. Raw data:
    0C 45 CA 36 E4 00 4B 12 00 54 3F 3A 06 00 00

    <RX>11:21:33.89 COM6 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
    SrcAddr: 0xE436
    NwkAddr: 0xE436
    IEEEAddr: 0x063A3F5400124B00
    Capabilities: 0x80

     

    End Device log files:

    <TX>11:21:32.24 COM7 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

    <RX>11:21:32.24 COM7 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>11:21:32.36 COM7 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    <RX>11:21:32.65 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

    <RX>11:21:32.92 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 3 (0x3)

    <RX>11:21:33.35 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 5 (0x5)

    <RX>11:21:33.87 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 6 (0x6)

    <RX>11:21:49.25 COM7 ZDO_LEAVE_IND (0x45C9)
    srcAddr: 0x0000
    extAddr: 0x063A3F5400124B00
    request: 0x01
    removeChildren: 0x00
    rejoin: 0x00

    <RX>11:21:54.15 COM7 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x07 (TC Link Key Exchange Failure) (0x7)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    <RX>11:21:54.63 COM7 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x00

    <TX>11:22:59.42 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>11:22:59.42 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_HOLD (0x0)
    NumAssocDevices: 0x00
    AssocDevicesList

    But device didn't  changed from DeviceState: DEV_HOLD (0x0) to  DeviceState: DEV_END_DEVICE (0x6).

    Device still being in DeviceState: DEV_HOLD (0x0).

    Thanks in Advance,

    Amar.

  • Please refer to the following ZED ZTool log which is from my test to join a ZNP based ZED into ZC.

    Start Time: 2018/10/4 下午 02:19:25

    <TX>02:20:24.25 COM1 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x02)

    <RX>02:20:24.26 COM1 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

    <TX>02:20:52.92 COM1 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00002000 (0x2000)

    <RX>02:20:52.93 COM1 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>02:21:01.13 COM1 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

    <RX>02:21:01.14 COM1 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>02:23:51.07 COM1 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

    <RX>02:23:55.7 COM1 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>02:23:55.71 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

    <RX>02:23:55.71 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0x02 (Network Steering) (0x2)

    <RX>02:23:55.98 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 3 (0x3)

    <RX>02:23:56.44 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 5 (0x5)

    <RX>02:23:57.64 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 6 (0x6)

    <RX>02:23:57.9 COM1 ZDO_NODE_DESC_RSP (0x4582)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x0000
    LogicalType_ComplexDescAvailable_UserDescAvailable: 0x00
    APSFlags_FrequencyBand: 0x40
    MACCapabilityFlags: ALTER_PAN_COORD, DEVICE_TYPE, POWER_SOURCE, RECEIVER_ON_WHEN_IDLE, ALLOCATE_ADDRESS (0x8F)
    ManufacturerCode: 0x0000
    MaxBufferSize: 0x50
    MaxInTransferSize: 0x00A0
    ServerMask: 10753 (0x2A01)
    MaxOutTransferSize: 0x00A0
    DescriptorCapabilities: 0x00

    <RX>02:23:58.37 COM1 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0xBB26
    Status: ZDP_SUCCESS (0x0)

    <RX>02:23:58.37 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    <TX>02:25:23.97 COM1 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>02:25:23.98 COM1 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B00011436F6
    ShortAddress: 0xBB26
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_END_DEVICE (0x6)
    NumAssocDevices: 0x00
    AssocDevicesList
  • Thanks for reply YK Chen,

    I just followed your configuration file for setup end device. I didn't enable ZB_PERMIT_JOINING_REQUEST in coordinator. Is it required to enable ZB_PERMIT_JOINING_REQUEST in coordinator.

    If it is required,when i have to enable ZB_PERMIT_JOINING_REQUEST in coordinator.

    Coordinator side:

    Start Time: 10/4/2018 12:38:23 PM

    <RX>12:38:45.91 COM6 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

    <TX>12:38:45.91 COM6 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0003
    Offset: 0x00
    Len: 0x01
    Value: . (0x03)

    <TX>12:39:10.18 COM6 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x00)

    <RX>12:39:10.19 COM6 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

    <TX>12:39:31.82 COM6 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00002000 (0x2000)

    <RX>12:39:31.83 COM6 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <RX>12:39:44.93 COM6 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>12:39:44.93 COM6 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

    <TX>12:39:49.87 COM6 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

    <RX>12:39:49.87 COM6 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>12:40:12.87 COM6 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x04) Network Formation (0x4)

    <RX>12:40:12.87 COM6 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>12:40:13 COM6 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 0 (0x0)

    <RX>12:40:13.27 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

    <RX>12:40:13.53 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

    <RX>12:40:13.8 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

    <RX>12:40:14.06 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

    <RX>12:40:14.32 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

    <RX>12:40:14.85 COM6 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

    <RX>12:40:14.85 COM6 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 0 (0x0)

    <TX>12:40:31.75 COM6 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>12:40:31.76 COM6 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A490C00124B00
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

    <TX>12:41:18.85 COM6 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x008F
    Offset: 0x00
    Len: 0x01
    Value: . (0x01)

    <RX>12:41:18.85 COM6 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

    <TX>12:41:38.97 COM6 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

    <RX>12:41:38.97 COM6 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>12:41:38.97 COM6 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

    <RX>12:41:38.97 COM6 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    *** WARNING ***
    Unsupported or unformatted message received. Raw data:
    0C 45 CA A7 1E 00 4B 12 00 54 3F 3A 06 00 00

    <RX>12:43:25.57 COM6 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
    SrcAddr: 0x1EA7
    NwkAddr: 0x1EA7
    IEEEAddr: 0x063A3F5400124B00
    Capabilities: 0x80

    End Device Side:

    Start Time: 10/4/2018 12:38:23 PM

    <TX>12:42:25.8 COM7 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x02)

    <RX>12:42:25.8 COM7 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

    <TX>12:42:49.17 COM7 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00002000 (0x2000)

    <RX>12:42:49.17 COM7 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>12:43:03.26 COM7 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

    <RX>12:43:03.26 COM7 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

    <TX>12:43:23.79 COM7 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

    <RX>12:43:23.79 COM7 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

    <RX>12:43:24.04 COM7 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    <RX>12:43:24.31 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

    <RX>12:43:24.58 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 3 (0x3)

    <RX>12:43:25.03 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 5 (0x5)

    <RX>12:43:25.57 COM7 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 6 (0x6)

    <RX>12:43:40.95 COM7 ZDO_LEAVE_IND (0x45C9)
    srcAddr: 0x0000
    extAddr: 0x063A3F5400124B00
    request: 0x01
    removeChildren: 0x00
    rejoin: 0x00

    <RX>12:43:45.84 COM7 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x07 (TC Link Key Exchange Failure) (0x7)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

    <RX>12:43:46.37 COM7 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x00

    <TX>12:44:46.14 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>12:44:46.14 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_HOLD (0x0)
    NumAssocDevices: 0x00
    AssocDevicesList


    Can you please share coordinator configuration file also.

    Best regards,

    Amar.

  • On coordinator, you can use APP_CNF_BDB_START_COMMISSIONING (0x2F05) with Network Steering (0x2) as CommissioningMode: (0x02). The coordinator log for enable commision is like the followings:

    Start Time: 2018/10/4 下午 02:23:00

    <TX>02:23:41.29 COM8 APP_CNF_BDB_START_COMMISSIONING (0x2F05)

       CommissioningMode: (0x02) Network Steering (0x2)

    <RX>02:23:41.3 COM8 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)

       Status: SUCCESS (0x0)

    <RX>02:23:41.3 COM8 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)

       SrcAddr: 0x0000

       Status: ZDP_SUCCESS (0x0)

    <RX>02:23:41.3 COM8 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)

       Status: 0x00 (Success) (0x0)

       Commissioning Mode: 0x01 (Network Steering) (0x1)

       Commissioning Mode: 0 (0x0)

    *** WARNING ***

       Unsupported or unformatted message received.  Raw data:

       0C 45 CA 26 BB F6 36 14 01 00 4B 12 00 00 00

    <RX>02:23:57.61 COM8 ZDO_END_DEVICE_ANNCE_IND (0x45C1)

       SrcAddr: 0xBB26

       NwkAddr: 0xBB26

       IEEEAddr: 0x00124B00011436F6

       Capabilities: 0x80

  • I had used APP_CNF_BDB_START_COMMISSIONING (0x2F05) with Network Steering (0x2) as CommissioningMode: (0x02) in coordinator. I got coordinator log files as you shared with me.

    My log files in coordinator.

    <TX>02:14:27.74 COM6 ZB_PERMIT_JOINING_REQUEST (0x2608)
    Destination: 0x0000
    Timeout: 0xB4

    <RX>02:14:27.74 COM6 ZB_PERMIT_JOINING_REQUEST_RSP (0x6608)
    Status: SUCCESS (0x0)

    <RX>02:14:27.75 COM6 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

    *** WARNING ***
    Unsupported or unformatted message received. Raw data:
    0C 45 CA 05 CC 00 4B 12 00 54 3F 3A 06 00 00

    <RX>02:14:45.36 COM6 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
    SrcAddr: 0xCC05
    NwkAddr: 0xCC05
    IEEEAddr: 0x063A3F5400124B00
    Capabilities: 0x80


    In my scenario the another one device(End device) still being in hold state. I have shared below log files belongs to end device side.

    <TX>02:17:02.5 COM7 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>02:17:02.5 COM7 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x063A3F5400124B00
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_HOLD (0x0)
    NumAssocDevices: 0x00
    AssocDevicesList


    When the hold state device will turn into end device.

    Thanks,

    Amar.

  • I don't know why you cannot make it so I already suggest you to setup sniffer to check your issue.
  • Okay YK chen,

    I will start to use Smart RF sniffer agent. Here how to capture a packet log files.

    The software didn't recognize my devices. It has showing Sniffer Devices not found.

  • What is your sniffer device?
  • I have CC2538EM devices.
  • You need to use either CC2531 USB dongle or LAUNCHXL-CC2650 as sniffer device.
  • Thanks for response YK Chen,

    I will test and get back to you.

    Best Regards,

    Amar.
  • Hey Amar,

    Were you able to solve your problem? Or get a sniffer log?
  • Hi YKChen,

    Sorry for late response.

    Just I got CC2531 USB Dongles.Here Can I follow the steps for configuring coordinator and end device. I had been flashed CC2531ZNP-Pro-Secure_Standard.hex file into CC2531 USB Dongles from Z-Stack

    Home 1.2.2a which is given in TI. But here got the configuration file below shown.

    CC2531 device:

    But here didn't get GP and AppConfig capabities in CC2531. which shown in below.

    CC2538 device:

    Which ZNP have to use for getting above configuration options.

    Thanks and regards,

    Amar.

  • Using CC2531ZNP-Pro-Secure_Standard.hex from Z-Stack Home 1.2.2a running on CC2531 USB Dongle, you have to follow the steps in sunmaysky.blogspot.com/.../setup-zigbee-ha-coordinator-with-ti.html
  • Thanks you for suggestion Chen.

    I have two CC2531 USB Dongles. I want  to setup one is coordinator and another one is end device. Coordinator setup is fine. I want to setup another device as a end device.

    How to setup end device.

  • Try to refer to TheDarkSide’s script at e2e.ti.com/.../1208179 to revise it for end device.
  • Chen,

    I tried TheDarkSide's script file for make as a end devices. I enabled ZDO_MGMT_PERMIT_JOIN_REQUEST with the value of AddrMode=0x02, DstAddr=0, and Duration=255 in the Coordinator side. I just changed

    COM PORT in the DarkSide's script file.I had wait upto 5min. I didn't get ZDO_END_DEVICE_ANNCE_IND at coordinator side. I have to share log files below.

    2388.coordinator.rtf

    end_device.rtf

  • I suggest you to setup sniffer to check what happens over the air.
  • Okay Chen,

    I will setup sniffer and check what happens over air. I will share sniffer log files.

    Here when i send UTIL_GET_DEV_INFO  from end device side. Got response below shown.

    <TX>05:53:10.19 COM15 UTIL_GET_DEVICE_INFO (0x2700)

    <RX>05:53:10.2 COM15 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0006272A09
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_NWK_DISC (0x2)
    NumAssocDevices: 0x00
    AssocDevicesList


    At end device side continuously showing.

    <RX>05:53:11.02 COM15 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

    <RX>05:53:11.77 COM15 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

     Thanks and Regards,

    Amar.

  • According to the ZTool log, your end device is searching network to join but can not make it. Do you enable permit join on coordinator to allow end device to join?
  • Yeah Chen,

    I had been enabled ZDO_MGMT_PERMIT_JOIN_REQUEST with AddrMode=0x02, DstAddr=0, and Duration=255 in coordinator, After script file running at End device side. Is this process is correct.

    or which is correct process.

    Thanks and Regards,

    Amar.

  • Are you sure Coordinator and end device are on the same channel?
  • Here how to see channels in devices. Because i ran script files into devices.
  • You have to set it in script file.