CC2652P: how to start coordinator for cc2652P in Z tool ?

Hi Praveen,

Make sure to start by loading the LAUNCHXL-CC1352P-2 ZNP project.  UART settings should be 115200 baud with no flow control.

Regards,
Ryan

Hi,

 I follow the above link steps but i could not add my devices in coordinator. please help me out I could not find the error

Start Time: 8/18/2022 11:12:35 AM

<RX>11:13:01.42 COM4 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>11:13:01.41 COM4 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0003
Offset: 0x00
Len: 0x01
Value: . (0x03)

<TX>11:13:06.2 COM4 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>11:13:08.45 COM4 SYS_RESET_RESPONSE (0x4180)
Reason: 0x00
TransportRev: 0x02
Product: 0x01
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x01

<TX>11:13:37 COM4 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0087
Offset: 0x00
Len: 0x01
Value: . (0x00)

<RX>11:13:37.01 COM4 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>11:14:03.42 COM4 APP_CNF_BDB_SET_CHANNEL (0x2F08)
isPrimary: TRUE (0x1)
Channel: CHNL_0x00002000 (0x2000)

<RX>11:14:03.42 COM4 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
Status: SUCCESS (0x0)

<TX>11:14:11.13 COM4 APP_CNF_BDB_SET_CHANNEL (0x2F08)
isPrimary: FALSE (0x0)
Channel: NONE (0x0)

<RX>11:14:11.13 COM4 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
Status: SUCCESS (0x0)

<TX>11:14:31.99 COM4 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x04) Network Formation (0x4)

<RX>11:14:34.95 COM4 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>11:14:34.95 COM4 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 1 (0x1)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 0x04 (Network Formation) (0x4)

<RX>11:14:35.16 COM4 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>11:14:35.73 COM4 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>11:14:35.73 COM4 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 0 (0x0)

<TX>11:15:22.55 COM4 UTIL_GET_DEVICE_INFO (0x2700)

<RX>11:15:22.55 COM4 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B0025791D78
ShortAddress: 0x0000
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ZB_COORD (0x9)
NumAssocDevices: 0x00
AssocDevicesList

<TX>11:15:44.36 COM4 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x008F
Offset: 0x00
Len: 0x01
Value: . (0x01)

<RX>11:15:44.37 COM4 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>11:16:36.66 COM4 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>11:16:36.66 COM4 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>11:16:36.67 COM4 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
SrcAddr: 0x0000
Status: ZDP_SUCCESS (0x0)

<RX>11:16:36.67 COM4 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 0 (0x0)

<RX>11:16:36.67 COM4 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x02 (No Network) (0x2)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 0 (0x0)

Do you use second device to act as end device or router to join coordinator?

second device act as end device

I don't see you do channel setup for end device in your log. Do you set channel on your end device?

where the place of end device channel setup in above log?

I just follow the  steps in Page sunmaysky.blogspot.com/.../use-ztool-z-stack-30-znp-to-set-up.html

Read the post carefully and you will see.

Devices are added but couldn't control from the AF Data Request in Ztool . It display Invalid parameter

<TX>02:25:00.1 COM4 AF_DATA_REQUEST (0x2401)
DstAddr: 0x2B98
DestEndpoint: 0x01
SrcEndpoint: 0x07
ClusterID: 0x0006
TransID: 0x01
Options: 0x02
Radius: 0x07
Len: 0x03
Data: ... (0x01, 0x01, 0x00)

<RX>02:25:00.11 COM4 AF_DATA_REQUEST_SRSP (0x6401)
Status: afStatus_INVALID_PARAMETER (0x2) 

Try to use AF_DATA_REQUEST_EXT instead of AF_DATA_REQUEST.

How to get DstPanID from end devices

You can use UTIL_GET_NV_INFO to get PANID

Added device (on/off module)

<RX>02:58:39.08 COM4 ZDO_MGMT_LQI_RSP (0x45B1)
SrcAddr: 0x0000
Status: ZDP_SUCCESS (0x0)
NeighborTableEntries: 0x02
StartIndex: 0x00
NeighborLqiListCount: 0x02
NeighborLqiList:
ExtendedPanID: 0x00124B0025791D78
ExtendedAddress: 0x086BD7FFFE5B6851
NetworkAddress: 0x2B98
Reserved_7_Relationship_6_4_RxOnWhenIdle_3_2_DeviceType_1_0: 0x15
Reserved_7_2_PermitJoining_1_0: 0x02
Depth: 0x01
RxLQI: 0xF3

i sent the request from AF_DATA_REQUEST_EXT its also invalid parameter

<TX>02:59:05.81 COM4 AF_DATA_REQUEST_EXT (0x2402)
DstAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
DstAddr: Qh[...k. (0x51, 0x68, 0x5B, 0xFE, 0xFF, 0xD7, 0x6B, 0x08)
DstEndPoint: 0x01
DstPanId: 0x0000
SrcEndpoint: 0x07
ClusterID: 0x0006
TransID: 0x01
Options: 0x02
Radius: 0x07
Len: 0x0003
Data: ... (0x01, 0x01, 0x01)

<RX>02:59:05.82 COM4 AF_DATA_REQUEST_EXT_SRSP (0x6402)
Status: afStatus_INVALID_PARAMETER (0x2)

Do you use AF_REGISTER to register endpoint on your coordinator and device?

devices are controlled but couldn't get feedback from device .so, I manually bind with coordinator using ZDO_BIND_REQ option no feedback from the device