CC2538: Coordinator Not NwkAddrRsp

SL Cho

Prodigy 90 points

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK,

The End device is transmitting nwk address request.

I am testing the coordinator on existing router & end device.

Although the end device is sending a nwk address request, coordinator does not nwk address respond.

The attached file questionFor_NwkAddrRsp.cubx.(Ubiqua tool)

questionFor_NwkAddrRsp.zip

Stack : Z-Stack Home 1.2.2a.44539

Project : TI SampleThermostat(Coordinator), Silicon labs(Router, End device)

PAN Configuration and Test Procedure :

1. Coordinator On & Pan configuration

2. Router On & binding to Coordinator

3. End device On & binding to Coordinator

4. The End device sends the Temp & Humidity data to the Coordinator at 10 seconds intervals.

5. Coordinator Off

6. The End device is intended to send sensor data to the Coordinator via Router.(Coordinator Off)

7. End device is sending a nwk address request

8. Coordinator On(NV_RESTORE defined)

9. The code is sending the response.(attached file : QuestionFor_NwkAddrRsp.png)

10. However, the packet on ubquia appears to be broadcast by the Coordinator.

What should I add to the project for response?

over 8 years ago

0 YiKai Chen over 8 years ago

Guru 735695 points

If you intend to do network address request, you can use API ZDP_NwkAddrReq to do it. However, the network address of coordinator is fixed to 0x0000 so there is no need to request it.

0 SL Cho over 8 years ago in reply to YiKai Chen

Prodigy 90 points

coordinator does not nwk address request.

When the coordinator power is off -> on, it is not reconnected.
End device or router nwk address request -> coordinator

I don't know why I can't reconnect.

0 YiKai Chen over 8 years ago in reply to SL Cho

Guru 735695 points

Do you enable NV_RESTORE?

0 SL Cho over 8 years ago in reply to YiKai Chen

Prodigy 90 points

yes NV_RESTORE ok

0 YiKai Chen over 8 years ago in reply to SL Cho

Guru 735695 points

What do you mean "yes NV_RESTORE ok?"

0 SL Cho over 8 years ago in reply to YiKai Chen

Prodigy 90 points

I'm sorry.
It was created in a different way to PC trouble.
NV_RESTORE is defined.

ewarm
CC2538_USE_ALTERNATE_INTERRUPT_MAP=1
FEATURE_RESET_MACRO
SECURE=1
TC_LINKKEY_JOIN
NV_INIT
NV_RESTORE
xHOLD_AUTO_START
ZTOOL_P1
MT_TASK
MT_APP_FUNC
MT_SYS_FUNC
MT_ZDO_FUNC
LCD_SUPPORTED=DEBUG
MULTICAST_ENABLED=FALSE
ZCL_READ
ZCL_WRITE
ZCL_REPORT
ZCL_EZMODE
ZCL_BASIC
ZCL_IDENTIFY
ZCL_ON_OFF
ZCL_HVAC_CLUSTER

0 YiKai Chen over 8 years ago in reply to SL Cho

Guru 735695 points

I am confused by your descriptions. Do you intend to send network address request from ZC to ZED or ZED to ZC? Can you elaborate?

0 Jose Maria Alvarez over 8 years ago

Genius 3415 points

Hi SL Cho,

I tried this myself by using:

ZDP_NwkAddrReq( ieeeAddr, ZDP_ADDR_REQTYPE_SINGLE, 0, 1 );

I'm using a few nodes and each one of them is sending the NWK Address Response. Can you try to repeat your test with a fresh installation of the zstack?

I hope this helps.

Jose Maria

0 Luis Luna over 8 years ago

Expert 1620 points

Hi SL Cho,

Coordinator might not be sending the frame to child device because it is waiting for child to poll (send data request), as shown at the begging of the capture, ZED was child of coordinator and after power cycle coordinator might think that it is still his child. Can you confirm this by retrieving the assoc table from coordinator?

If this is your issue, then you will need to consider how to clean up you assoc table to avoid this cases, or you can migrate to Z3.0 which implements the child management feature that actually addresses this kind of scenarios by using parent annce command

Hope this helps!

Zigbee & Thread

Zigbee & Thread forum

CC2538: Coordinator Not NwkAddrRsp