Can not to start Zigbee 3.0

I test ZNP in Z-Stack 3.0 ProdHex and Debug projects. All work fine. I use attached script coordinator_light.zip in to do the test for your reference.

I think I made a little change to make ProdHex work. You should select f8w2530.xcl (under \Z-Stack 3.0.0\Projects\zstack\Tools\CC2530DB) instead of znp-prod.xcl (under \Z-Stack 3.0.0\Projects\zstack\ZNP\CC253x\tools) as "Linker configuration file".

I use IAR 9.20. But i can to try 9.30

Please use the attached script znp-bringupR.zjs to run ZR using ZNP. You can revise it to run as ZED. znp-bringupC.zjs is for ZC.

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/ZNP_5F00_script_5F00_example.7z

I try your scripts.  But nothing! The ZC  starts ok and ZR don't starts  it send Beacon request (I can see it in Sniffer)  Coordinator sen SuperFrame and it is all.  The Router Script infinity send Start_request  and get  ZDO_STATE_CHANGE_IND 

It is all. 

I do undestand right the algoritm of forming network with security:
The first - I tune my netowrk paremetr (PANID,ROLE, CHANNEL) on my ZC and ZR(ZED)

Reset devices with CLEAR_STATE_NETWORK flag.
Start ZC.
Send command ZDO_MGMT_PERMIT_JOIN_REQ (fe 05 25 36 02 00 00 ff(fe) 00) on ZC

Start ZR(ZED)
I must send ZDO_MGMT_PERMIT_JOIN_REQ (fe 05 25 36 02 00 00 ff 00) on ZR(ZED)??
If yes -What is the parametr I must set in this command? Type of AddrMode? DstAddr

YiKai Chen said:

According to Zigbee 3.0 spec, you shouldn't enable permit join all the time.

In this case how can i provide join new device to my network? If the time limit only 4 minutes?

YiKai Chen said:

No, you don't have to send ZDO_MGMT_PERMIT_JOIN_REQ on ZR or ZED

And DstAddr in this request  must be set Addres of Coordinator or Router which want to be TC??

Luis Luna said:

Luis Luna!

Thank you! I saw Your messege onlu now.  And I try  today late. thank you!

Yesterday I build  prevision version of Stack with  security options  and try to join by YiKai Chen's script. The ZC and ZR strat well. But I didn't  send any messege. The sender return AF_DATA_CONFIRM with status Success. But I don't  get it on recipient (receiver). But I can see on receiver the AF_DATA_CONFIRM too. It is very strange.. 

Sorry for this question but I never work with security n Z-Stac. 

Hi Luis!

Your post help me solve same problem, and i can join to network.

But stay same question abot scenario to join.

When I start network first time (the coordinator) I must send APP_CNF_BDB_START_COMMISSIONING  with Formation enabled (0x04) and after APP_CNF_BDB_START_COMMISSIONING  with Steering enabled (0x02).  And for Router  APP_CNF_BDB_START_COMMISSIONING  with Steering enabled (0x02), It is right??  What is the type of  APP_CNF_BDB_START_COMMISSIONING  for ED?

If I restart my device  I must to send only APP_CNF_BDB_START_COMMISSIONING  with Steering for EC and ER??

The second question.

When I start my devices (ZC and ZR) the first time (or both CLEAR_STATE bit) The device up fine.  If I restart and again up device all fine again.

BUT! If I restart my ZR with CLEAR_STATE bit in this case I get same problem - the device try to join to network but couldn't.  I get 

ZDO_STATE_CHANGE_IND 02, 03, 05... And Again 02,03,05.  On the ZC-side I get ZDO_TC_DEV_IND but ZR not join..  

It is strange.. If I once or twice times restart ZR with CLEAR_STATE bit I join to network.  

And where can i find information about type of  APP_CNF_BDB_START_COMMISSIONING?

Thank You!

Thanks for usefull help.
What does ZDO_state = 0x08 means? where should i see what does each number means? i read znp developing document some numbers are there like 0x02,0x05,0x07 and 0x09 but i got 0x08 that i don't know what does it mean!!

It is DEV_COORD_STARTING .

You can find it at source (Find this impression) or in MT Manual ZDO_STATE_CHANGE_IND

t

typedef enum
{
  DEV_HOLD,                                // Initialized - not started automatically
  DEV_INIT,                                // Initialized - not connected to anything
  DEV_NWK_DISC,                            // Discovering PAN's to join
  DEV_NWK_JOINING,                         // Joining a PAN
  DEV_NWK_SEC_REJOIN_CURR_CHANNEL,         // ReJoining a PAN in secure mode scanning in current channel, only for end devices
  DEV_END_DEVICE_UNAUTH,                   // Joined but not yet authenticated by trust center
  DEV_END_DEVICE,                          // Started as device after authentication
  DEV_ROUTER,                              // Device joined, authenticated and is a router
  DEV_COORD_STARTING,                      // Started as Zigbee Coordinator
  DEV_ZB_COORD,                            // Started as Zigbee Coordinator
  DEV_NWK_ORPHAN,                          // Device has lost information about its parent..
  DEV_NWK_KA,                              // Device is sending KeepAlive message to its parent
  DEV_NWK_BACKOFF,                         // Device is waiting before trying to rejoin
  DEV_NWK_SEC_REJOIN_ALL_CHANNEL,          // ReJoining a PAN in secure mode scanning in all channels, only for end devices
  DEV_NWK_TC_REJOIN_CURR_CHANNEL,          // ReJoining a PAN in Trust center mode scanning in current channel, only for end devices
  DEV_NWK_TC_REJOIN_ALL_CHANNEL            // ReJoining a PAN in Trust center mode scanning in all channels, only for end devices
} devStates_t;

File ZDApp.h