• State
  • Locked Locked
  • Replies 27 replies
  • Subscribers 55 subscribers
  • Views 6568 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2531EMK: Unable to Form a Network using ZNP (Zstack 3.0 )

Karim Shaik
Intellectual 370 points
Part Number: CC2531EMK
Other Parts Discussed in Thread: CC2531, Z-STACK

Hi ,

I have uploaded ZNP from ZStack 3.0 on CC2531 USB Dongle . I am using ZTool to send and receive commands.

I have sent ZB_Permit_joining_request command to the dongle  and I have received a response from a end device as below

ZDO_END_DEVICE_ANNCE_IND (0x45C1)

scrAddr :0x6DEB

NwkAddr:0x6DEB

IEEEAddr:0x000D6F000B102449

Capabilities:0x80

After a few seconds i am receiving a another respose of device leaving

ZDO_LEAVE_IND (0x45C9)

srcAddr:0x6DEB

extAddr:0x000D6F000B102449

request:0x00

removeChildren:0x00

rejoin:0x00

I cant understand why the device joins and automatically disjoins. I have even tried network streering and procedure from the blog sunmaysky

Thanks,

Karim

  • 0
    Guru 735455 points
    You must allow legacy devices to join your Zigbee 3.0 network, they are being rejected because of the new Zigbee 3.0 security scheme. You can allow legacy devices to join by setting BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to FALSE in bdb_interface.h
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    Hi Chen,

    I have tried above option by sending APP_CNF_BDB_SET_TC_REQUIRE_KEY_EXCHANGE with value Flase, but the issue is still the same.

    Thanks,
    Karim
  • 0 in reply to Karim Shaik
    Guru 735455 points
    Which example do you use as Zigbee device to join Z-Stack 3.0 coordinator?
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    Hi,

    I have used the prebuilt firmware CC2531ZNP-with-SBL.hex from Texas Instruments/Z-Stack 3.0.1/Projects/zstack/ZNP/CC253x/dev/ folder

    Thanks
    karim
  • 0 in reply to Karim Shaik
    Guru 735455 points
    Is it coordinator or device?
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    my CC2531 is a coordinator . On sending UTIL_GET_DEVICE_INFO I am receiving the reponse as
    DEVICETYPE : COORDINATOR,Router,End_Device(0x7)
    DeviceState : DEV_ZB_COORD(0x9)

    I am connecting a door sensor (MCT-340 E) to it
  • 0 in reply to Karim Shaik
    Guru 735455 points
    How do you send APP_CNF_BDB_SET_TC_REQUIRE_KEY_EXCHANGE with value Flase?
  • 0 in reply to YiKai Chen
    Intellectual 370 points

    COM5_fnal.rtfI have attached the screenshot of my ztool and log. Please see.

  • 0 in reply to Karim Shaik
    Guru 735455 points
    I suggest you to use Ubiqua Protocol Analyzer to check what happens over the air.
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    Thanks, but I dont have sniffer right now as I have changed the firmware from sniffer to ZNP on cc2531.
  • 0 in reply to Karim Shaik
    Guru 735455 points
    Maybe try to use ZNP from Z-Stack Home 1.2.2a to test again.
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    I will try it and let you know tomorrow
  • 0 in reply to Karim Shaik
    Intellectual 370 points
    Can you share the link for ZNP from Z-Stack Home 1.2.2a
  • 0 in reply to Karim Shaik
    Guru 735455 points
    You can find Z-Stack Home 1.2.2a from www.ti.com/.../z-stack-archive
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    I have downloaded the Z-Stack Home 1.2.2a and flashed the cc2531 with ZNP pro hex file available at ZAP/ZNP-Hexfiles/ . On sending command UTIL_GET_DEVICE_INFO I am receiving the device state as DEV_HOLD(0x0) can you share the steps how to make the device as coordinator
  • 0 in reply to Karim Shaik
    Guru 735455 points
    There’s script in ZTool folder to do that.
  • 0 in reply to YiKai Chen
    Intellectual 370 points

    COM5_18_10.rtf

    I have run the script for bringing up the coordinator then after  Joining the network using network topology script I found two devices one is router and the other is an end device(Motion sensor).  

    But,  after the above  step when I try to permit join using ZB_PERMIT_JOIN_REQUEST I  get the response as SUCESS but the device has not joined the network. how can I make the device to join the  network.

    I have attached the trace log of steps I did, please go through them.

  • 0 in reply to Karim Shaik
    Guru 735455 points

    I cannot open your attach rtf file. You can try to download script ZNP_script_example.7z from TheDarkSide's reply at e2e.ti.com/.../1208179 to start coordinator from Ztool by script.

  • 0 in reply to YiKai Chen
    Intellectual 370 points

    0066.COM_18_10_2017.txt 
    Start Time: 10/18/2017 3:33:18 PM

<TX>03:33:27.3 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>03:33:27.3 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001DD847F
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_HOLD (0x0)
    NumAssocDevices: 0x01
    AssocDevicesList: 0xD2D5

<TX>03:33:44.1 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:44.92 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:45.73 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:46.6 COM5 ZB_SYSTEM_RESET (0x4609)

<RX>03:33:46.63 COM5 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x06
    HwRev: 0x03

<TX>03:33:47.43 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x03
    Len: 0x01
    Value: . (0x03)

<TX>03:33:47.9 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x03
    Len: 0x01
    Value: . (0x03)

<RX>03:33:47.92 COM5 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x06
    HwRev: 0x03

<RX>03:33:47.92 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<RX>03:33:47.92 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:33:48.1 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:48.92 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:49.73 COM5 ZB_SYSTEM_RESET (0x4609)

<TX>03:33:50.95 COM5 ZB_SYSTEM_RESET (0x4609)

<RX>03:33:50.96 COM5 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x06
    HwRev: 0x03

<TX>03:33:51.76 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x87
    Len: 0x01
    Value: . (0x00)

<TX>03:33:52.28 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x87
    Len: 0x01
    Value: . (0x00)

<RX>03:33:52.29 COM5 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x06
    HwRev: 0x03

<RX>03:33:52.29 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<RX>03:33:52.31 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:33:52.49 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x83
    Len: 0x02
    Value: .. (0xFF, 0xFF)

<RX>03:33:52.49 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:33:52.7 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x84
    Len: 0x04
    Value: .... (0x00, 0x00, 0x08, 0x00)

<RX>03:33:52.7 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:33:52.92 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x01)

<RX>03:33:52.92 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:33:53.14 COM5 AF_REGISTER (0x2400)
    EndPoint: 0x07
    AppProfID: 0x0104
    AppDeviceId: 0x0100
    AppDevVer: 0x00
    LatencyReq: NO_LATENCY_REQS (0x0)
    AppNumInClusters: 0x05
    AppInClusterList: 0x0000, 0x0003, 0x0004, 0x0005, 0x0006
    AppNumOutClusters: 0x01
    AppOutClusterList: 0x0000

<RX>03:33:53.14 COM5 AF_REGISTER_SRSP (0x6400)
    Status: afStatus_SUCCESS (0x0)

<TX>03:33:53.35 COM5 ZB_START_REQUEST (0x2600)

<RX>03:33:54.12 COM5 ZB_START_REQUEST_RSP (0x6600)

<RX>03:33:54.12 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>03:33:54.64 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>03:33:55.15 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>03:33:56.17 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<TX>03:34:09.62 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>03:34:09.64 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001DD847F
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

<TX>03:35:51.76 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x00)

<RX>03:35:51.76 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:35:51.98 COM5 ZDO_MGMT_LQI_REQ (0x2531)
    DstAddr: 0x0000
    StartIndex: 0x00

<RX>03:35:51.98 COM5 ZDO_MGMT_LQI_REQ_SRSP (0x6531)
    Status: afStatus_SUCCESS (0x0)

<RX>03:35:52 COM5 ZDO_MGMT_LQI_RSP (0x45B1)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NeighborTableEntries: 0x00
    StartIndex: 0x00
    NeighborLqiListCount: 0x00
    NeighborLqiList: 

<TX>03:40:41.57 COM5 UTIL_GET_NV_INFO (0x2701)

<RX>03:40:41.6 COM5 UTIL_GET_NV_INFO_RESPONSE (0x6701)
    Status: ZMAC_UNSUPPORTED (0x18)
    IEEEAddress: 0x00124B0001DD847F
    ScanChannels: NONE (0x0)
    PanID: 0x0800
    SecurityLevel: 0x00
    PreConfigKey: ................ (0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF)

<TX>03:40:50.86 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>03:40:50.86 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001DD847F
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

<TX>03:41:15.9 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x00)

<RX>03:41:15.91 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:41:16.12 COM5 ZDO_MGMT_LQI_REQ (0x2531)
    DstAddr: 0x0000
    StartIndex: 0x00

<RX>03:41:16.12 COM5 ZDO_MGMT_LQI_REQ_SRSP (0x6531)
    Status: afStatus_SUCCESS (0x0)

<RX>03:41:16.12 COM5 ZDO_MGMT_LQI_RSP (0x45B1)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NeighborTableEntries: 0x00
    StartIndex: 0x00
    NeighborLqiListCount: 0x00
    NeighborLqiList: 

<TX>03:42:32.01 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x00)

<RX>03:42:32.03 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)

<TX>03:42:32.23 COM5 ZDO_MGMT_LQI_REQ (0x2531)
    DstAddr: 0x0000
    StartIndex: 0x00

<RX>03:42:32.23 COM5 ZDO_MGMT_LQI_REQ_SRSP (0x6531)
    Status: afStatus_SUCCESS (0x0)

<RX>03:42:32.23 COM5 ZDO_MGMT_LQI_RSP (0x45B1)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NeighborTableEntries: 0x02
    StartIndex: 0x00
    NeighborLqiListCount: 0x02
    NeighborLqiList: 
    ExtendedPanID: 0x00124B0001DD847F
    ExtendedAddress: 0x000D6F0004482F75
    NetworkAddress: 0x15B4
    Reserved_7_Relationship_6_4_RxOnWhenIdle_3_2_DeviceType_1_0: 0x15
    Reserved_7_2_PermitJoining_1_0: 0x02
    Depth: 0x01
    RxLQI: 0xAA
    ExtendedPanID: 0x00124B0001DD847F
    ExtendedAddress: 0x000D6F000D695AB8
    NetworkAddress: 0x0E98
    Reserved_7_Relationship_6_4_RxOnWhenIdle_3_2_DeviceType_1_0: 0x12
    Reserved_7_2_PermitJoining_1_0: 0x02
    Depth: 0x01
    RxLQI: 0xAA

<TX>03:49:20.03 COM5 ZB_PERMIT_JOINING_REQUEST (0x2608)
    Destination: 0xFFFC
    Timeout: 0x19

<RX>03:49:20.05 COM5 ZB_PERMIT_JOINING_REQUEST_RSP (0x6608)
    Status: SUCCESS (0x0)

<RX>03:49:20.05 COM5 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 00 

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 00 

<TX>04:01:51.93 COM5 ZB_WRITE_CONFIGURATION (0x2605)
    ConfigId: 0x8F
    Len: 0x01
    Value: . (0x00)

<RX>04:01:51.95 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
    Status: SUCCESS (0x0)


<TX>04:01:52.21 COM5 ZDO_MGMT_LQI_REQ (0x2531)
    DstAddr: 0x15B4
    StartIndex: 0x00

<RX>04:01:52.21 COM5 ZDO_MGMT_LQI_REQ_SRSP (0x6531)
    Status: afStatus_SUCCESS (0x0)

<TX>04:04:34.17 COM5 ZB_PERMIT_JOINING_REQUEST (0x2608)
    Destination: 0xFFFC
    Timeout: 0x19

<RX>04:04:34.17 COM5 ZB_PERMIT_JOINING_REQUEST_RSP (0x6608)
    Status: SUCCESS (0x0)

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 19 

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 19 

<RX>04:04:34.19 COM5 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 00 

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    01 45 CB 00

    I started the coordinator by script  but the device did not join the network. I am attaching the trace file in text format now.

  • 0 in reply to Karim Shaik
    Guru 735455 points
    I cannot judge anything from attached log. Please set up Ubiqua Protocol Analyzer to check what happens over the air.
  • 0 in reply to YiKai Chen
    Intellectual 370 points

    hi, I have received below response from the script

    <TX>03:42:32.23 COM5 ZDO_MGMT_LQI_REQ (0x2531)
        DstAddr: 0x0000
        StartIndex: 0x00
     
    <RX>03:42:32.23 COM5 ZDO_MGMT_LQI_REQ_SRSP (0x6531)
        Status: afStatus_SUCCESS (0x0)
     
    <RX>03:42:32.23 COM5 ZDO_MGMT_LQI_RSP (0x45B1)
        SrcAddr: 0x0000
        Status: ZDP_SUCCESS (0x0)
        NeighborTableEntries: 0x02
        StartIndex: 0x00
        NeighborLqiListCount: 0x02
        NeighborLqiList:  
        ExtendedPanID: 0x00124B0001DD847F
        ExtendedAddress: 0x000D6F0004482F75
        NetworkAddress: 0x15B4
        Reserved_7_Relationship_6_4_RxOnWhenIdle_3_2_DeviceType_1_0: 0x15
        Reserved_7_2_PermitJoining_1_0: 0x02
        Depth: 0x01
        RxLQI: 0xAA
        ExtendedPanID: 0x00124B0001DD847F
        ExtendedAddress: 0x000D6F000D695AB8
        NetworkAddress: 0x0E98
        Reserved_7_Relationship_6_4_RxOnWhenIdle_3_2_DeviceType_1_0: 0x12
        Reserved_7_2_PermitJoining_1_0: 0x02
        Depth: 0x01
        RxLQI: 0xAA

    Coordinator MAC add : 0x00124B0001DD847F

    End devices : 0x000D6F0004482F75, 0x000D6F000D695AB8

    Does this mean that the device has joined the network ? . I have setup the ubiqua protocol analyzer and I will share the log soon .

  • 0 in reply to Karim Shaik
    Guru 735455 points
    I cannot judge this from ZTool response. I need Ubiqua log to know it.
  • 0 in reply to YiKai Chen
    Intellectual 370 points

    Zstack3.0 log.zipHI Chen,

    PFA, Ubiqua log and ztool log for ZStack 3.0 on CC2531 and NYCE motion sensor . I could see that the device is being configured for few seconds but finally could not join the network. I will soon share the log for HA 1.2 as well.

  • 0 in reply to Karim Shaik
    Intellectual 370 points

    PFA the latset one for ZStack 3.0Zigbee.zip

  • 0 in reply to Karim Shaik
    Guru 735455 points
    In your sniffer log, coordinator only enable permit join for a very short time.
  • 0 in reply to YiKai Chen
    Intellectual 370 points
    I have even tried with 255 (0xff) the result is the same, one of the above two attachments has it.
  • 0 in reply to Karim Shaik
    Guru 735455 points
    You can set it to 254 at most in Zigbee 3.0