CC2530: Z-Stack 3.0.1 UART communication stops after sending 20-30 frames

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

Hello YK,

Its not the OSRAM which stops working. I have to reboot CC2530 running Z-Stack 3.0.1 which stops responding on UART. I sniff the network and use Wireshark and dont see any packets coming out of CC2530. The only way I get Z-Stack to work again is to reboot it. This same behavior occurs with any Zigbee device, I have tested Cree bulb, OSRAM lightify products, Viconics thermostats etc.

Thanks,

Can you attach your sniffer log?

Hello,

This is the device OSRAM CLM which onboards on CC2530 running Z-Stack 3.0.1. I am using znp host-framework to talk to Z-Stack over UART. (enclosed osram-onboarding.pcap)

Endpoint: 0x01
ProfileID: 0x0104
DeviceID: 0x0101
DeviceVersion: 0x00
NumInClusters: 9
InClusterList[0]: 0x0000
InClusterList[1]: 0x0003
InClusterList[2]: 0x0004
InClusterList[3]: 0x0005
InClusterList[4]: 0x0006
InClusterList[5]: 0x0008
InClusterList[6]: 0x0015
InClusterList[7]: 0xFC01
InClusterList[8]: 0xFC30
NumOutClusters: 1
OutClusterList[0]: 0x0019

Device joined network:
0 0x2042 0x01 0x0101

and then I send on, off commands at the rate of 500msec and after I while I keep getting these. 

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
rpcSendFrame: waiting for SRSP [04]
rpcSendFrame: SRSP Error - CMD0: 0x24 CMD1: 0x02

At this point I do not see device- OSRAM CLM toggling and no packet is going out of CC2530 (shown in wireshark capture: osram-on-off-stops.pcap) 

Why does Z-Stack locks up after hammering it continuously with packets? 

osram-on-off-stops.pcap-   drive.google.com/.../view
osram-onboarding.pcap-    drive.google.com/.../view

Thanks,

1. I cannot decrypt osram-on-off-stops.pcap since there is no association process included and no network key is available.
2. I don't see you do binding to OSRAM CLM so I don't think the device would work.

This is the network key used- 6a:64:6d:4b:6e:f7:ae:e6:fe:8a:02:a7:83:ba:20:b3, Trust link key- 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39

You can add these in Wireshark by going to Edit-->Preferences-->Protocols-->ZigBee Nwk--> Pre-configured key Edit

You can see that there is a two way communication between CC2530 and OSRAM CLM (NwkAddr- 0x2042) and also my eyes confirms that device is turning on and off. This stops when I get this error on serial line. If I reboot CC2530 I can again control the OSRAM light. 

rpcSendFrame: Blocking on RPC sem
rpcSendFrame: Sending RPC
rpcSendFrame: waiting for SRSP [04]
rpcSendFrame: SRSP Error - CMD0: 0x24 CMD1: 0x02

I see this OSRAM device keep sending lots of route record and make network very busy. I think this might be the root cause of your issue.

So this means a busy network can lock up Z-Stack and stop UART communication? If that's the case this will never work for anyone. I have had same experience with Viconics Thermostat, OSRAM Lightify, Cree, GE light link etc.

I had integrate/test Cree bulb into CC2530 coordinator but don't see similar issue. I cannot judge this. I only know it is weird to see so many route records.