CC2530: Coordinator does not receive data sent from EndDevice with AF_DATA_REQUEST

Yevhenii Tsiura

Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

Hi! I try to send data from EndDevice to Coordinator with AF_DATA_REQUEST message via my custom cc2530 ZNP board. But Coordinator does not trigger AF_INCOMING_MSG callback.
I have 3 ZNP devices (cc2530) connected via SPI to my STM32F103ZET6 board. One of device is Coordinator, the second is Router and the EndDevice. After start Coordinator successfully creates network, then Router successfully joined as a router, and after that EndDevice also successfully joined the network. After ED join i try to send data to Coordinator, i send AF_DATA_REQUEST to EndDevice ZNP, it respond me with status=0 (success), after that i receive MT_AF_DATA_CONFIRM from EndDevice. But there is no AF_INCOMING_MSG at Coordinator device.

Should i create binding between ED and Coordinator before send messages? As i see in example in swra444.pdf binding is not required to send data between devices?

Also i tried allow bind at coordinator and send bind request to ED, but AF_DATA_REQUEST still not gave any succes ((

What im doing wrong?

Also this is my simple prinf log from IAR terminal )

ID:1 - Coordinator, ID:2 - Router, ID:3 - EndDevice

TaskCoordBegin
[ID:1] Reset: [0]
[ID:1] Reset: [1]
[ID:1][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [01:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:1][mtSysResetIndCb] Reason: [1], ZNP Version: 2.6.3
[ID:1][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:03]
[ID:1][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:1] NV Write Startup Option cmd sent[0]...
[ID:1][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [02:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:1][mtSysResetIndCb] Reason: [2], ZNP Version: 2.6.3
[ID:1][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:00]
[ID:1][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:1] NV Write Startup Option cmd sent[0]...
[ID:1][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [8F:00:00:01:01]
[ID:1][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:1] NV Write direct callback cmd sent[0]...
[ID:1][SREQ][ZDO]Length[2], cmd0[25], cmd1[3E], payload [06:00]
[ID:1][SRSP][ZDO]Length[1], cmd0[65], cmd1[3E], payload [00]
 MT_ZDO_SIMPLE_DESC_REQ
[ID:1][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [87:00:00:01:00]
[ID:1][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:1] NV Write Device Type cmd sent... [0]
[ID:1][SREQ][SYS]Length[6], cmd0[21], cmd1[09], payload [83:00:00:02:FF:FF]
[ID:1][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:1] NV Write PAN ID cmd sent...[0]
[ID:1][SREQ][AF]Length[11], cmd0[24], cmd1[00], payload [01:04:01:00:01:01:02:01:06:00:00]
[ID:1][SRSP][AF]Length[1], cmd0[64], cmd1[00], payload [00]
 MT_AF_REGISTER
[ID:1][SREQ][ZDO]Length[2], cmd0[25], cmd1[40], payload [00:00]
[ID:1][SRSP][ZDO]Length[1], cmd0[65], cmd1[40], payload [01]
 MT_ZDO_STARTUP_FROM_APP
[zdoStartupFromApp] NEW_NETWORK
[ID:1][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [08]
 MT_ZDO_STATE_CHANGE_IND
[ID:1][mtZdoStateChangeIndCb] Starting as Zigbee Coordinator
[ID:1][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [08]
 MT_ZDO_STATE_CHANGE_IND
[ID:1][mtZdoStateChangeIndCb] Starting as Zigbee Coordinator
[ID:1][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [09]
 MT_ZDO_STATE_CHANGE_IND
[ID:1][mtZdoStateChangeIndCb] Started as Zigbee Coordinator
[ID:1][AREQ][SYS]Length[0], cmd0[41], cmd1[04]
[ID:1][SREQ][SAPI]Length[3], cmd0[26], cmd1[08], payload [FC:FF:78]
[ID:1][SRSP][SAPI]Length[1], cmd0[66], cmd1[08], payload [00]
 MT_SAPI_PERMIT_JOINING_REQ
[ID:1][SREQ][SAPI]Length[1], cmd0[26], cmd1[02], payload [FF]
[ID:1][SRSP][SAPI]Length[0], cmd0[66], cmd1[02]
[ID:1] unhandled
[ID:1][AREQ][ZDO]Length[3], cmd0[45], cmd1[B6], payload [00:00:00]
 MT_ZDO_MGMT_PERMIT_JOIN_RSP
TaskRouterBegin
[ID:2] Reset: [0]
[ID:2] Reset: [1]
[ID:2][POLL][ERR]Length[0], cmd0[00], cmd1[00]
[ID:2][mtProcess]: CMD0:0, CMD1:0, not handled
[ID:2][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [01:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:2][mtSysResetIndCb] Reason: [1], ZNP Version: 2.6.3
[ID:2][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:03]
[ID:2][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:2] NV Write Startup Option cmd sent[0]...
[ID:2][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [02:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:2][mtSysResetIndCb] Reason: [2], ZNP Version: 2.6.3
[ID:2][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:00]
[ID:2][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:2] NV Write Startup Option cmd sent[0]...
[ID:2][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [8F:00:00:01:01]
[ID:2][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:2] NV Write direct callback cmd sent[0]...
[ID:2][SREQ][ZDO]Length[2], cmd0[25], cmd1[3E], payload [06:00]
[ID:2][SRSP][ZDO]Length[1], cmd0[65], cmd1[3E], payload [00]
 MT_ZDO_SIMPLE_DESC_REQ
[ID:2][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [87:00:00:01:01]
[ID:2][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:2] NV Write Device Type cmd sent... [0]
[ID:2][SREQ][SYS]Length[6], cmd0[21], cmd1[09], payload [83:00:00:02:FF:FF]
[ID:2][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:2] NV Write PAN ID cmd sent...[0]
[ID:2][SREQ][AF]Length[11], cmd0[24], cmd1[00], payload [01:04:01:01:01:01:02:00:01:06:00]
[ID:2][SRSP][AF]Length[1], cmd0[64], cmd1[00], payload [00]
 MT_AF_REGISTER
[ID:2][SREQ][ZDO]Length[2], cmd0[25], cmd1[40], payload [00:00]
[ID:2][SRSP][ZDO]Length[1], cmd0[65], cmd1[40], payload [01]
 MT_ZDO_STARTUP_FROM_APP
[zdoStartupFromApp] NEW_NETWORK
[ID:2][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [02]
 MT_ZDO_STATE_CHANGE_IND
[ID:2][mtZdoStateChangeIndCb] Discovering PAN's to join
[ID:2][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [03]
 MT_ZDO_STATE_CHANGE_IND
[ID:2][mtZdoStateChangeIndCb] Joining a PAN
[ID:2][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [07]
 MT_ZDO_STATE_CHANGE_IND
[ID:2][mtZdoStateChangeIndCb] Device joined, authenticated and is a router
[ID:1][AREQ][ZDO]Length[13], cmd0[45], cmd1[C1], payload [84:D1:84:D1:00:08:01:10:00:4B:12:00:8E]
 MT_ZDO_END_DEVICE_ANNCE_IND
[ID:1][mtZdoEndDeviceAnnceIndCb] SrcAddr [D184], NwkAddr [D184], Capabilities[8E]
[ID:1][AREQ][ZDO]Length[12], cmd0[45], cmd1[CA], payload [84:D1:00:08:01:10:00:4B:12:00:00:00]
 MT_ZDO_TC_DEVICE_IND
[ID:1][mtZdoTcDeviceIndCb] NwkAddr [84D1], ParentAddr [00]
[ID:1][SREQ][ZDO]Length[16], cmd0[25], cmd1[21], payload [D1:84:00:08:01:10:00:4B:12:00:01:06:00:00:FF:FF]
[ID:1][SRSP][ZDO]Length[1], cmd0[65], cmd1[21], payload [00]
 MT_ZDO_BIND_REQ
TaskEndDeviceBegin
[ID:3] Reset: [0]
[ID:3] Reset: [1]
[ID:3][POLL][ERR]Length[0], cmd0[00], cmd1[00]
[ID:3][mtProcess]: CMD0:0, CMD1:0, not handled
[ID:3][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [01:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:3][mtSysResetIndCb] Reason: [1], ZNP Version: 2.6.3
[ID:3][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:03]
[ID:3][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:3] NV Write Startup Option cmd sent[0]...
[ID:3][AREQ][SYS]Length[6], cmd0[41], cmd1[80], payload [02:02:00:02:06:03]
 MT_SYS_RESET_IND
[ID:3][mtSysResetIndCb] Reason: [2], ZNP Version: 2.6.3
[ID:3][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [03:00:00:01:00]
[ID:3][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:3] NV Write Startup Option cmd sent[0]...
[ID:3][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [8F:00:00:01:01]
[ID:3][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:3] NV Write direct callback cmd sent[0]...
[ID:3][SREQ][ZDO]Length[2], cmd0[25], cmd1[3E], payload [06:00]
[ID:3][SRSP][ZDO]Length[1], cmd0[65], cmd1[3E], payload [00]
 MT_ZDO_SIMPLE_DESC_REQ
[ID:3][SREQ][SYS]Length[5], cmd0[21], cmd1[09], payload [87:00:00:01:02]
[ID:3][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:3] NV Write Device Type cmd sent... [0]
[ID:3][SREQ][SYS]Length[6], cmd0[21], cmd1[09], payload [83:00:00:02:FF:FF]
[ID:3][SRSP][SYS]Length[1], cmd0[61], cmd1[09], payload [00]
 MT_SYS_OSAL_NV_WRITE
[ID:3] NV Write PAN ID cmd sent...[0]
[ID:3][SREQ][AF]Length[11], cmd0[24], cmd1[00], payload [01:04:01:02:01:01:02:00:01:06:00]
[ID:3][SRSP][AF]Length[1], cmd0[64], cmd1[00], payload [00]
 MT_AF_REGISTER
[ID:3][SREQ][ZDO]Length[2], cmd0[25], cmd1[40], payload [00:00]
[ID:3][SRSP][ZDO]Length[1], cmd0[65], cmd1[40], payload [01]
 MT_ZDO_STARTUP_FROM_APP
[zdoStartupFromApp] NEW_NETWORK
[ID:3][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [02]
 MT_ZDO_STATE_CHANGE_IND
[ID:3][mtZdoStateChangeIndCb] Discovering PAN's to join
[ID:3][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [03]
 MT_ZDO_STATE_CHANGE_IND
[ID:3][mtZdoStateChangeIndCb] Joining a PAN
[ID:3][AREQ][ZDO]Length[1], cmd0[45], cmd1[C0], payload [06]
 MT_ZDO_STATE_CHANGE_IND
[ID:3][mtZdoStateChangeIndCb] Started as device after authentication
[ID:2][AREQ][ZDO]Length[13], cmd0[45], cmd1[C1], payload [1B:44:1B:44:21:08:01:10:00:4B:12:00:80]
 MT_ZDO_END_DEVICE_ANNCE_IND
[ID:1][AREQ][ZDO]Length[13], cmd0[45], cmd1[C1], payload [1B:44:1B:44:21:08:01:10:00:4B:12:00:80]
 MT_ZDO_END_DEVICE_ANNCE_IND
[ID:1][mtZdoEndDeviceAnnceIndCb] SrcAddr [441B], NwkAddr [441B], Capabilities[80]
[ID:1][AREQ][ZDO]Length[12], cmd0[45], cmd1[CA], payload [1B:44:21:08:01:10:00:4B:12:00:00:00]
 MT_ZDO_TC_DEVICE_IND
[ID:1][mtZdoTcDeviceIndCb] NwkAddr [1B44], ParentAddr [00]
[ID:1][SREQ][ZDO]Length[16], cmd0[25], cmd1[21], payload [44:1B:21:08:01:10:00:4B:12:00:01:06:00:00:FF:FF]
[ID:1][SRSP][ZDO]Length[1], cmd0[65], cmd1[21], payload [00]
 MT_ZDO_BIND_REQ
[ID:3][SREQ][AF]Length[14], cmd0[24], cmd1[01], payload [00:00:01:01:06:00:00:00:EE:04:0A:0B:0C:0D]
[ID:3][SRSP][AF]Length[1], cmd0[64], cmd1[01], payload [00]
 MT_AF_DATA_REQUEST
[ID:3][AREQ][AF]Length[3], cmd0[44], cmd1[80], payload [00:01:00]
afProcess: MT_AF_DATA_CONFIRM
[ID:3][mtAfDataConfirmCb] Status [00], Endpoint [01], TransId [00]
[ID:3][SREQ][AF]Length[14], cmd0[24], cmd1[01], payload [00:00:01:01:06:00:01:00:EE:04:0A:0B:0C:0D]
[ID:3][SRSP][AF]Length[1], cmd0[64], cmd1[01], payload [00]
 MT_AF_DATA_REQUEST
[ID:3][AREQ][AF]Length[3], cmd0[44], cmd1[80], payload [00:01:01]
afProcess: MT_AF_DATA_CONFIRM
[ID:3][mtAfDataConfirmCb] Status [00], Endpoint [01], TransId [01]

over 7 years ago

0 YiKai Chen over 7 years ago

Guru 735695 points

I suggest you to use Ubiqua Protocol Analyzer to check what happens over the air.

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

6644.capture.zip

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

I think NO-25 (highlighted) is my message that i sent from ED to Coordinator.

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

I left devices working for few hours, after i'm back i found that coordinator receiving data (it triggers AF_INCOMING_MSG). Then i restarted system, and again AF_DATA_REQUEST did not give any success result (

I attached my system startup log from Ubiqua, maybe it will help to find the problem

7183.startup.zip

0 YiKai Chen over 7 years ago in reply to Yevhenii Tsiura

Guru 735695 points

I see you use AF_DATA_REQUEST to send message to destination endpoint 1. Does your ZNP coordinator register endpoint 1?

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

Yes, i use such parameters in AF_REGISTER at Cordinator:

    .EndPoint = 1,
    .AppProfId = 0x0104,
    .AppDeviceId = 0x0100,
    .AppDevVer = 1,
    .Reserved = 0x00,
    .AppNumInClusters = 1,
    .pAppInClusterList[0] = 0x0006,
    .AppNumOutClusters = 1,
    .pAppOutClusterList[0] = 0x0006

This is AF_REGISTER for EndDevice

    .EndPoint = 1,
    .AppProfId = 0x0104,
    .AppDeviceId = 0x0102,
    .AppDevVer = 1,
    .Reserved = 0x00,
    .AppNumInClusters = 1,
    .pAppInClusterList[0] = 0x0006,
    .AppNumOutClusters = 1,
    .pAppOutClusterList[0] = 0x0006

And then i try to send data with AF_DATA_REQUEST with such parameters:

  dataReq.ClusterID = 0x0006;
  dataReq.DstAddr = 0x0000;
  dataReq.DstEndpoint = 1;
  dataReq.Radius = 0xEE;
  dataReq.SrcEndpoint = 1;
  dataReq.Len = 4;
  dataReq.Options = 0x80;
  dataReq.Data[0] = 0x0A;
  dataReq.Data[1] = 0x0B;
  dataReq.Data[2] = 0x0C;
  dataReq.Data[3] = 0x0D;

And again i left devices worked for a night, and in the morning i found that messages delivered successfully to Coordinator again! But after restart again nothing ...

Also after sending AF_DATA_REQUEST my ED received AF_DATA_CONFIRM with success status, but Coordinator does not received message

0 Yevhenii Tsiura over 7 years ago in reply to Yevhenii Tsiura

Intellectual 260 points

UPD:
Also when i try to use 0xFFFF as DstAddr my Router starts receiving messages from the beginning, but not the coordinator (

0 YiKai Chen over 7 years ago in reply to Yevhenii Tsiura

Guru 735695 points

I suggest you to do some debug on coordinator ZNP to see why it doesn't pops AF_INCOMING_MSG.

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

Problem exists only with prebuild CC2530ZNP-Pro-Secure_Standard.hex firmware from Z-Stack Home 1.2, i tried to flash devices with CC2530ZNP-Pro.hex and all works fine now. Is it firmware bug?

0 YiKai Chen over 7 years ago in reply to Yevhenii Tsiura

Guru 735695 points

I suppose you are using ON/OFF ZCL cluster so it might be filtered by zcl layer.

0 Yevhenii Tsiura over 7 years ago in reply to YiKai Chen

Intellectual 260 points

Is ZCL layer built in to ZNP device?

I did not change anything in my code, just change firmware. Now i build new ZNP firmware in IAR from HA 1.2.2a with -DSECURE=1, set up precfg key and enabled it, and all works fine! Messages successfully delivered from ED to Coordinator. I think it was actually a firmware problem.

By the way, can you tell me what is this "Data Request" every 500ms from End Device?

And one more (i hope the last) question is - why periodicaly i received 0xFF messages by SPI from End Device? Is it sleep mode?

0 YiKai Chen over 7 years ago in reply to Yevhenii Tsiura

Guru 735695 points

1. No, ZCL layer is not built in to ZNP. Maybe you can try to build ZNP with TC link key security by yourself to verify if it is prebuilt hex problem.
2. "Data Request" is device does polling to its parent node to receive messages.
3. If you configure it to end device, it should be in sleep mode. You can try to measure power consumption of end device ZNP to confirm this.

Zigbee & Thread

Zigbee & Thread forum

CC2530: Coordinator does not receive data sent from EndDevice with AF_DATA_REQUEST