problem with binding: ZDP_TABLE_FULL

Luca Tavanti

Other Parts Discussed in Thread: CC2531, CC2650STK, Z-STACK, CC2650

Hi,

I'm trying to bind the sample switch on the SensorTag with a ZTool + cc2531 based coordinator.

I followed the instructions in: here and also in the TI forum, but until now I never succeeded, and I really can't figure it out why.

Here is my setup:

SensorTag with sample application, disabled HOLD_AUTO_START, ZCL_EZMODE, and NV_RESTORE.

ZStack version 1.2.2a.

The SensorTag associates and can manually send data, but cant' bind.

I have attached the log of ZTool.

The really strange thing is that when I send the binding command, the SensorTag seems to reply ZDP_TABLE_FULL, even though the table is (or should be) empty. In fact, I have erased the tag and reprogrammed it, and if try to unbind it, the sensortag replies "entry not found".

Also, if I issue the ZDO_MGMT_BIND_REQ, the reply is ZDP_NOT_PERMITTED...

Did I miss something?

Any help would really be appreciated :)

Fullscreen ztool-nobind.txt Download

<RX>12:20:26.79 COM10 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
    SrcAddr: 0x10B3
    NwkAddr: 0x10B3
    IEEEAddr: 0x00124B00079ED581
    Capabilities: 0x80

<TX>12:21:03.36 COM10 ZDO_BIND_REQ (0x2521)
    DstAddr: 0x10B3
    SrcAddress: 0x00124B00079ED581
    SrcEndpoint: 0x08
    ClusterID: 0x0006
    BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
    BindAddr: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
    BindEndpoint: 0x07

<RX>12:21:03.38 COM10 ZDO_BIND_REQ_SRSP (0x6521)
    Status: afStatus_SUCCESS (0x0)

<RX>12:21:12.15 COM10 ZDO_BIND_RSP (0x45A1)
    SrcAddr: 0x10B3
    Status: 140 (0x8C)

<TX>12:23:16.76 COM10 ZDO_BIND_REQ (0x2521)
    DstAddr: 0x10B3
    SrcAddress: 0x00124B00079ED581
    SrcEndpoint: 0x09
    ClusterID: 0x0420
    BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
    BindAddr: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
    BindEndpoint: 0x07

<RX>12:23:16.77 COM10 ZDO_BIND_REQ_SRSP (0x6521)
    Status: afStatus_SUCCESS (0x0)

<RX>12:23:22.37 COM10 ZDO_BIND_RSP (0x45A1)
    SrcAddr: 0x10B3
    Status: 140 (0x8C)

<TX>12:25:20.4 COM10 ZDO_MGMT_BIND_REQ (0x2533)
    DstAddr: 0x10B3
    StartIndex: 0x00

<RX>12:25:20.41 COM10 ZDO_MGMT_BIND_REQ_SRSP (0x6533)
    Status: SUCCESS (0x0)

<RX>12:25:22.59 COM10 ZDO_MGMT_BIND_RSP (0x45B3)
    SrcAddr: 0x10B3
    Status: 139 (0x8B)
    BindingTableEntries: 0x00
    StartIndex: 0x00
    BindingTableListCount: 0x00
    BindingTableList: 

<TX>12:27:25.81 COM10 ZDO_UNBIND_REQ (0x2522)
    DstAddr: 0x10B3
    SrcAddress: 0x00124B00079ED581
    SrcEndpoint: 0x09
    ClusterID: 0x0420
    DstAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
    DstAddress: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
    DstEndpoint: 0x07

<RX>12:27:29.53 COM10 ZDO_UNBIND_RSP (0x45A2)
    SrcAddr: 0x10B3
    Status: ZDP_NO_ENTRY (0x88)

over 10 years ago

0 YiKai Chen over 10 years ago

Guru 735695 points

I think the problem is your clusterID.

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

Uhm... are you sure?
I used 0x0006, which is ZCL_CLUSTER_ID_GEN_ON_OFF.
And the exactly same problem occurs with the ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT cluster as well.

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

Yes, I am sure. If endpoint is 0x09, the cluster ID should be 0x0402 not 0x0420.

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

I've just checked, still same problem.
(sorry for the 0x0420, it was a typo)

<TX>03:47:29.41 COM10 ZDO_BIND_REQ (0x2521)
DstAddr: 0x9CB9
SrcAddress: 0x00124B00079ED581
SrcEndpoint: 0x09
ClusterID: 0x0402
BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
BindAddr: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
BindEndpoint: 0x07

<RX>03:47:29.43 COM10 ZDO_BIND_REQ_SRSP (0x6521)
Status: afStatus_SUCCESS (0x0)

<RX>03:47:34.7 COM10 ZDO_BIND_RSP (0x45A1)
SrcAddr: 0x9CB9
Status: 140 (0x8C)

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

Do you have sniffer log?

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

I attach the sniffer log.

The sensor tag address is 0xA182.

binding-failure.psd

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

Yes, the sniffer log also shows table full. I would suggest you to do a mass erase to your CC2650STK and program it to test again.

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

I mass erased, rebuilt and programmed both zstack and app, but the error is still there.

I also tried with another sensortag. Same result.

It's really puzzling...

2705.binding-failure2.psd

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

It's not the same. There is no binding response in your 2705.binding-failure2.psd.

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

Probably the sniffer did not catch the frame.

The ZTool log is essentially the same:

<TX>12:59:45.67 COM10 ZDO_BIND_REQ (0x2521)
DstAddr: 0x2844
SrcAddress: 0x00124B00079EDE85
SrcEndpoint: 0x08
ClusterID: 0x0006
BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
BindAddr: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
BindEndpoint: 0x07

<RX>12:59:45.67 COM10 ZDO_BIND_REQ_SRSP (0x6521)
Status: afStatus_SUCCESS (0x0)

<RX>12:59:51.02 COM10 ZDO_BIND_RSP (0x45A1)
SrcAddr: 0x2844
Status: 140 (0x8C)

<TX>01:01:15.79 COM10 ZDO_BIND_REQ (0x2521)
DstAddr: 0x2844
SrcAddress: 0x00124B00079EDE85
SrcEndpoint: 0x09
ClusterID: 0x0402
BindAddrMode: 0x03 (ADDRESS_64_BIT) (0x3)
BindAddr: ..K..Zf. (0x00, 0x12, 0x4B, 0x00, 0x01, 0x5A, 0x66, 0xE6)
BindEndpoint: 0x07

<RX>01:01:15.8 COM10 ZDO_BIND_REQ_SRSP (0x6521)
Status: afStatus_SUCCESS (0x0)

<RX>01:01:25.12 COM10 ZDO_BIND_RSP (0x45A1)
SrcAddr: 0x2844
Status: 140 (0x8C)

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

I run out of idea. I suggest you to debug and trace into SenaorTag example to see if you can find any clue.

0 Luca Tavanti over 10 years ago in reply to YiKai Chen

Prodigy 210 points

I'm afraid tha's the only option left.
By the way, do you know if it's possible to debug the zstack too?
And how?

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

You can only debug ZStack application for CC26xx.

0 Joshua Bijak over 10 years ago in reply to Luca Tavanti

Intellectual 790 points

Your bind address is not little endian
you must input it this way

e6 66 5a 01 00 4b 12 00 ( this also has to be the coordinator address)

srcaddress must be the SensorTag address

Also make sure you bind within 10 seconds of association otherwise for whatever reason the SensorTag sends a pseudo SendTemp and locks the whole thing. Dont ask me why I am currently trying to figure it out.

Guaranteed steps to work.
Change the bind address to little endian.
Reflash sensortag.
Wait for association
AS SOON AS it associates send bind request.
Youll see messages as AF incoming msg for temperature.

0 YiKai Chen over 10 years ago in reply to Joshua Bijak

Guru 735695 points

Yes, Joshua is correct. BindAddr should be in reverse endian. However, I don't see the limit that have to do binding in 10 seconds right after association.

0 Luca Tavanti over 10 years ago in reply to Joshua Bijak

Prodigy 210 points

Hi Joshua,

That worked!

Thanks a lot.

I also confirm what Yikai said: no need to do binding within 10 seconds.

BTW, I really can't understand why all fields in the ZTool are big endian but this one must be little endian... just to have developers go out crazy...

Also: I don't see why the device replies "ZDP_TABLE_FULL".... it's totally misleading...

0 YiKai Chen over 10 years ago in reply to Luca Tavanti

Guru 735695 points

Yes, this is very weird behavior in Z-Stack about little endian. I think this might be a bug but to keep all Z-Stack backward compatible so TI doesn't want to change it. As for device replies "ZDP_TABLE_FULL", don't have any idea.

0 Joshua Bijak over 10 years ago in reply to Luca Tavanti

Intellectual 790 points

Maybe it is just my version of SensorTag. I have no idea how to solve it.

Yikai. Is there a function that you can call in SensorTag App that lets you see the binding table entries?

0 YiKai Chen over 10 years ago in reply to Joshua Bijak

Guru 735695 points

I am afraid you cannot do this on CC2650. It's in ZStackCore and not open to application. If you are interested in the binding related function, you can refer to BindingTable.c and BindingTable.h under \Components\stack\nwk

Zigbee & Thread

Zigbee & Thread forum

problem with binding: ZDP_TABLE_FULL