CC2651P3: ZNP, Not posible to start coordinator with Ztool

Make sure you setup primary and secondary channels properly. I also suggest you to use sniffer to check what exactly happens over the air

The chanels are well set. Sniffering, i can see the beacon from coordinator and the beacon response from coordinator, but nothing more hapends.

And in the Ztool of the router apears this:

<TX>01:45:23.42 COM8 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

<RX>01:45:23.87 COM8 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>01:45:23.87 COM8 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0x02 (Network Steering) (0x2)

<RX>01:45:24.13 COM8 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

<RX>01:45:24.39 COM8 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x02 (No Network) (0x2)                                                                            -----> I think here is the problem
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

<RX>01:45:24.39 COM8 ZDO_STATE_CHANGE_IND (0x45C0)
    State: SUCCESS (0x0)

Can you attach your sniffer log?

No.     Time           Source                Destination           Protocol Length Info
   6718 949.568855     N/A                   Broadcast             IEEE 802.15.4 74     Beacon Request

Frame 6718: 74 bytes on wire (592 bits), 74 bytes captured (592 bits) on interface \Device\NPF_Loopback, id 0
Null/Loopback
Internet Protocol Version 4, Src: 172.30.111.106, Dst: 172.30.111.106
User Datagram Protocol, Src Port: 51981, Dst Port: 17754
ZigBee Encapsulation Protocol, Channel: 13, Length: 10
    Protocol ID String: EX
    Protocol Version: 2
    Type: Data (1)
    Channel ID: 13
    Device ID: 0
    LQI/CRC Mode: LQI
    Link Quality Indication: 0
    Timestamp: Jun  6, 2023 13:45:24.131478999 Hora de verano romance
    Sequence Number: 24
    .000 1010 = Length: 10 bytes
IEEE 802.15.4 Command, Dst: Broadcast
    Frame Control Field: 0x0803, Frame Type: Command, Destination Addressing Mode: Short/16-bit, Frame Version: IEEE Std 802.15.4-2003, Source Addressing Mode: None
    Sequence Number: 194
    Destination PAN: 0xffff
    Destination: 0xffff
    Command Identifier: Beacon Request (0x07)
    TI CC24xx-format metadata: FCS OK
        FCS Valid: True
        RSSI: 29 dB
        LQI Correlation Value: 0

No.     Time           Source                Destination           Protocol Length Info
   6720 949.575863     0x0000                N/A                   ZigBee   92     Beacon, Src: 0x0000, EPID: TexasIns_00:14:fb:86:dd

Frame 6720: 92 bytes on wire (736 bits), 92 bytes captured (736 bits) on interface \Device\NPF_Loopback, id 0
Null/Loopback
Internet Protocol Version 4, Src: 172.30.111.106, Dst: 172.30.111.106
User Datagram Protocol, Src Port: 51981, Dst Port: 17754
ZigBee Encapsulation Protocol, Channel: 13, Length: 28
    Protocol ID String: EX
    Protocol Version: 2
    Type: Data (1)
    Channel ID: 13
    Device ID: 0
    LQI/CRC Mode: LQI
    Link Quality Indication: 0
    Timestamp: Jun  6, 2023 13:45:24.131478999 Hora de verano romance
    Sequence Number: 25
    .001 1100 = Length: 28 bytes
IEEE 802.15.4 Beacon, Src: 0x0000
    Frame Control Field: 0x8000, Frame Type: Beacon, Destination Addressing Mode: None, Frame Version: IEEE Std 802.15.4-2003, Source Addressing Mode: Short/16-bit
    Sequence Number: 152
    Source PAN: 0xfeab
    Source: 0x0000
    Superframe Specification: PAN Coordinator
        .... .... .... 1111 = Beacon Interval: 15
        .... .... 1111 .... = Superframe Interval: 15
        .... 1111 .... .... = Final CAP Slot: 15
        ...0 .... .... .... = Battery Extension: False
        .1.. .... .... .... = PAN Coordinator: True
        0... .... .... .... = Association Permit: False
    GTS
        GTS Descriptor Count: 0
        GTS Permit: False
    Pending Addresses: 0 Short and 0 Long
    TI CC24xx-format metadata: FCS OK
        FCS Valid: True
        RSSI: 22 dB
        LQI Correlation Value: 0
ZigBee Beacon, ZigBee PRO, EPID: TexasIns_00:14:fb:86:dd
    Protocol ID: 0
    Beacon: Stack Profile: ZigBee PRO, Router Capacity, End Device Capacity
    Extended PAN ID: TexasIns_00:14:fb:86:dd (00:12:4b:00:14:fb:86:dd)
    Tx Offset: 16777215
    Update ID: 0

Can you save sniffer log as .pncap file to attach it 

https://we.tl/t-UdMBwGnWIb

I unfortunately cannot access the website due to privacy errors.  You should be able to drag-and-drop the *.pcapng (or some other file extension) into the response window.

The Beacon Payload screenshot shows that the Association Permit flag is False, which means the network is not open for joining.  Please make sure to form the Zigbee network on your ZC before steering, which will enable/permit joining for 180 seconds.  If you continue to experience issues then consider erasing all device memory and re-programming both devices, and be sure to follow all instructions from the blog post.

Regards,
Ryan

Download Ztool_Sniffer.pcapng shows TCP protocol in my wireshark. Which Wireshark version do you use?

According to this log, your coordinator is not enable permit join. Please make sure you enable it to join your device.

My Wireshark version is 4.0.5.

How can I enable that falg, or wich comand do I have to send to permit joining. I've been looking in to MT API, but I didn't found anything.

APP_CNF_BDB_START_COMMISSIONING (0x2F05) would enable permit join for 180 seconds by default and you have to join your device in this 180 seconds period.

Okay, now the permit flag is enable.

But the joining doesn't finish.

Router device info response this:

<TX>09:19:46.34 COM8 UTIL_GET_DEVICE_INFO (0x2700)

<RX>09:19:46.34 COM8 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0014FB8404
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_NWK_DISC (0x2)
    NumAssocDevices: 0x00
    AssocDevicesList

Finally, It was nesesary to erease the entire flash, and then load de FW.

Thanks for everything.

This forum has a very good customer services.