Other Parts Discussed in Thread: Z-STACK
I have the Z-Stack_Linux_Gateway-1.0.1 running on BBB with CC2531USB. I have CC2530EB+SmartRF05 devices programmed as a ZLL light (ZllLight-EB.hex) and ZLL remote (ZllRemote-EB.hex). I can use classical commissioning to add the ZLL devices to the network and in the sample app (TI Gateway Demo App v1.00) they show up and I can use the on/off actions to turn the Zll light's LED on/off. Everything appears to be OK there.
If I bind the Zll-Remote (Color Dimmer) to a Gateway endpoint (Color Dimmable Light), the bind appears to be successful. I can then use the joystick on the CC2530EB+SmartRF05 to "turn on" the Gateway endpoint. What I see in the app is this:
received from GATEWAY: len=38, cmd_id=24, subsystem=83
Raw=26:00:53:18:08:18:10:01:1A:0D:08:00:11:E6:6D:C2:01:00:4B:12:00:28:0B:20:84:02:28:06:30:06:38:01:40:00:50:00:58:00:60:01:6A:00
system_process_zcl_frame_receive_indication: Received GW_ZCL_FRAME_RECEIVE_IND
profileid = 0x0104
endpointiddest = 0x0006
endpointidsrc = 0x000B
clusterid = 0x0006
frametype = 1
manufacturerspecificflag = 0
manufacturercode = (none)
clientserverdirection = 0
commandid = 1
payload = 0x09C518B8
If I use the joystick again to send an "Off" message or another "On" message, the NWKMGR server crashes:
*** glibc detected *** ./NWKMGR_SRVR_arm: corrupted double-linked list: 0x0007ce00 ***
./zigbeeHAgw: line 1049: 18894 Aborted $NWKMGR_CMD $NWKMGR_RESTART_FLAG
NETWORK MANAGER exited with code 134
Here is the full output starting from the launch of the servers if it is helpful:
running zigbeegw.scr on an ARM
resetting beaglebone black
sleeping 6 seconds after reset... Using serial port: /dev/ttyACM0
zbSocProcessRpc: CMD0:41, CMD1:80, not handled
Received System version.
Transport Protocol Version: 2
Product ID: 0
Software Release: 2.6.1
Software Revision: 38724
done
Starting the ZigBee gateway subsystem
deviceKey = 0 (0 )
devPath = '/dev/ttyACM0'
logPath = './NpiLnxLog.txt'
... freeing memory (ret 0)
Port: 2533
Following IP addresses are available:
IPv4: interface: lo IP Address 127.0.0.1
IPv4: interface: eth0 IP Address 192.168.1.201
IPv4: interface: usb0 IP Address 192.168.7.2
IPv6: interface: lo IP Address ::1
IPv6: interface: eth0 IP Address fe80::caa0:30ff:fec3:cd7d
The socket will listen on the following IP addresses:
IPv4: 0.0.0.0
IPv6: ::
0.0.0.0 means it will listen to all available IP address
waiting for first connection on #3...
NPI started (pid 18882) at Sat May 17 21:46:51 UTC 2014
Connected to #5.(127.0.0.1 / ::88e8:e0be:d0e8:e0be)
ZLSZNP started (pid 18887) at Sat May 17 21:46:55 UTC 2014
[NWK_MGR/MAIN] : there are 2 args
[NWK_MGR/MAIN] : argv[0] = ./NWKMGR_SRVR_arm
[NWK_MGR/MAIN] : argv[1] = 127.0.0.1:2536
[NWK_MGR/MAIN] : ************************************************
[NWK_MGR/MAIN] : * Network Manager Server v1.0.1 *
[NWK_MGR/MAIN] : * The following are the avaible key commands: *
[NWK_MGR/MAIN] : * Exit Program. - q *
[NWK_MGR/MAIN] : ************************************************
NETWORK MANAGER started (pid 18894) at Sat May 17 21:46:56 UTC 2014
[GATEWAY/MAIN] :
[GATEWAY/MAIN] : ************************************************
[GATEWAY/MAIN] : * Gateway Server v1.0.1 *
[GATEWAY/MAIN] : * The following are the avaible key commands: *
[GATEWAY/MAIN] : * Exit Program. - q *
[GATEWAY/MAIN] : ************************************************
GATEWAY SERVER started (pid 18900) at Sat May 17 21:46:58 UTC 2014
[OTASRVR/MAIN] :
[OTASRVR/MAIN] : ************************************************
[OTASRVR/MAIN] : * OTA Upgrade Server 1.0.1 *
[OTASRVR/MAIN] : * The following are the avaible key commands: *
[OTASRVR/MAIN] : * Exit Program. - q *
[OTASRVR/MAIN] : ************************************************
OTA SERVER started (pid 18909) at Sat May 17 21:47:00 UTC 2014
starting tracker with our pid ./zigbeeHAgw and pid list 18882 18887 18900 18909
===================================================
tracking 4 pids, 18882 18887 18900 18909
when we see something missing we will send a SIGUSR2 to pid 18817
*** glibc detected *** ./NWKMGR_SRVR_arm: corrupted double-linked list: 0x0007ce00 ***
./zigbeeHAgw: line 1049: 18894 Aborted $NWKMGR_CMD $NWKMGR_RESTART_FLAG
NETWORK MANAGER exited with code 134 at Sat May 17 21:49:48 UTC 2014
./zigbeeHAgw: line 482: 18921 Killed ./track_servers $$ "$pids"
Removing connection #5
unexpected exit code (134) from netmgr!
Eventually I have to do a hard reset of the servers to get back to a stable environment. Any insight or suggestions are welcome. Thanks.
