Coordinator dont send Match Descriptor Respond

Shinryu

Other Parts Discussed in Thread: CC2531, CC2530

Hi everyone,

I'm using CC2531 as coordinator and CC2530 as end device. I created my FW based on GenericApp.

Sometime my end device cannot binding to coordinator. Although End Device send Match Descriptor Request many time but Coordinator dont respond Match Descriptor Respond. (please check the log)log.pcapng.zip

Could you tell me the reason and how to fix it?

Thank in advance

over 9 years ago

0 YiKai Chen over 9 years ago

Guru 735685 points

I see your device sends out match request with 0x0006 as cluster ID. Does your coordinator support cluster ID 0x0006? If not, it doesn't respond to match request.

0 Shinryu over 9 years ago in reply to YiKai Chen

Intellectual 570 points

HI YiKai,

Thank for your answer,

It's strange. In my source code, It's defined as 1. But when I try to re-flash the same software it will be OK.
The reason is related to NV memory or initialization ....???

My Preprocessor for ED as below:
NWK_AUTO_POLL
xPOWER_SAVING
HAL_PA_LNA
HAL_UART=TRUE
HAL_UART_DMA=1
HAL_KEY
NV_INIT

Thank in advance,

0 YiKai Chen over 9 years ago in reply to Shinryu

Guru 735685 points

Sorry, it's my fault to make it wrong. you are correct that your cluster ID in match request is 0x0001. But, why does your device keep sending match requests so fast?

0 Shinryu over 9 years ago in reply to YiKai Chen

Intellectual 570 points

HI Yikai,

My ED will send match request with timer 100ms until receive match respond from ZC.
This timer starts when init and stop after binding success.

Thank in advance.

0 YiKai Chen over 9 years ago in reply to Shinryu

Guru 735685 points

I think broadcast match request every 100 ms is too much for Zigbee network. You should enlarge the period to 3 or 5 seconds to test again.

Zigbee & Thread

Zigbee & Thread forum

Coordinator dont send Match Descriptor Respond