CC2530EM: ZNP developing problem!!

Navid Torabi

Part Number: CC2530EM
Other Parts Discussed in Thread: Z-STACK, CC2530, CC2531EMK

Hi friends

I'm using CC2530 z-stack 3.0 firmware. I try to setup coordinator by means of znp uart, i use "znp developing" document values but there are some problem. can somebody tell me whats wrong on my work? does it need more settings or something wrong? or maybe something wrong on my compiler defined symbols?

----------------

data from pc to znp (send) and znp answers (Receive):

Send:FE03260503010220
Receive:FE0166050062
Send:FE0141000040
Receive:FE064180020200020700C2
Send:FE0426058302FFFFA6
Receive:FE0166050062
Send:FE0A26052D08DDDDDDDDDDDDDDDD0C
Receive:FE0166050062
Send:FE062605840403FFF800A1
Receive:FE0166050062
Send:FE032605870100A6
Receive:FE0166050062
Send:FE12260562100000000000000000000000000000000043
Receive:FE0166050062
Send:FE03260563010143
Receive:FE0166050062
Send:FE24210901010020FFFFFFFFFFFFFFFF0123456789ABCDEF0123456789ABCDEF00000000000000002C
Receive:FE016109026B
Send:FE112400080DBF01050100040000150002070000009E
Receive:FE0164000065
Send:FE022540000067
Receive:FE0165400125FE0145C0088C

------------------------------

my compiler defined symbols:

BDB_FINDING_BINDING_CAPABILITY_ENABLED=0
TC_LINKKEY_JOIN
NWK_MAX_DEVICE_LIST=10
ZDSECMGR_TC_DEVICE_MAX=30
ZNP_ENABLED
POWER_SAVING
FEATURE_SYSTEM_STATS
MT_GP_CB_FUNC
MT_SYS_FUNC
MT_UTIL_FUNC
MT_ZDO_FUNC
xHAL_SPI=FALSE
HAL_UART=TRUE
NV_RESTORE

------------------

Regards

over 8 years ago

0 Navid Torabi over 8 years ago

Intellectual 850 points

Is somebody here?
This is another try to make coordinator node:
---------------
1/30/2017 20:45:38.609 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
1/30/2017 20:45:41.485 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
1/30/2017 20:45:42.333 [TX] - FE 03 26 05 03 01 02 20 //ZCD_NV_STARTUP_OPTION
1/30/2017 20:45:42.346 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:43.418 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
1/30/2017 20:45:46.260 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
1/30/2017 20:45:48.128 [TX] - FE 04 26 05 83 02 FF FF A6 //ZCD_NV_PANID
1/30/2017 20:45:48.145 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:50.101 [TX] - FE 0A 26 05 2D 08 DD DD DD DD DD DD DD DD 0C //ZCD_NV_EXTPANID
1/30/2017 20:45:50.123 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:52.134 [TX] - FE 06 26 05 84 04 03 FF F8 00 A1 //ZCD_NV_CHANLIST
1/30/2017 20:45:52.143 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:53.836 [TX] - FE 03 26 05 87 01 00 A6 //ZCD_NV_LOGICAL_TYPE
1/30/2017 20:45:53.844 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:56.268 [TX] - FE 12 26 05 62 10 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 43 //ZCD_NV_PRECFGKEY
1/30/2017 20:45:56.278 [RX] - FE 01 66 05 00 62
1/30/2017 20:45:58.810 [TX] - FE 03 26 05 63 01 01 43 //ZCD_NV_PRECFGKEYS_ENABLE
1/30/2017 20:45:58.818 [RX] - FE 01 66 05 00 62
1/30/2017 20:46:01.198 [TX] - FE 24 21 09 01 01 00 20 FF FF FF FF FF FF FF FF 54 45 58 41 53 49 4E 53 54 52 55 4D 45 4E 54 53 00 00 00 00 00 00 00 00 31 //ZCD_NV_TC_LINK_KEY
1/30/2017 20:46:01.220 [RX] - FE 01 61 09 02 6B
1/30/2017 20:46:03.093 [TX] - FE 0F 24 00 08 0D BF 01 05 01 00 03 00 00 15 00 02 07 00 87 //AF_REGISTER
1/30/2017 20:46:03.103 [RX] - FE 01 64 00 00 65
1/30/2017 20:46:04.967 [TX] - FE 02 25 40 00 00 67 //ZDO_STARTUP_FROM_APP
1/30/2017 20:46:06.298 [RX] - FE 01 65 40 01 25 00
1/30/2017 20:46:22.313 [TX] - FE 02 25 40 00 00 67 //ZDO_STARTUP_FROM_APP
1/30/2017 20:46:22.562 [RX] - 00 3F
1/30/2017 20:46:31.238 [TX] - FE 02 25 40 00 00 67 //ZDO_STARTUP_FROM_APP
1/30/2017 20:46:31.475 [RX] - 00 3F
1/30/2017 20:46:34.550 [TX] - FE 02 25 40 00 00 67
1/30/2017 20:46:34.785 [RX] - 00
--------------------------------------------------
Why i get "FE 01 65 40 01 25 00 " after ZDO_STARTUP_FROM_APP? as documents say it should be "FE 01 45 C0 09 86" for coordinator!! what does "FE 01 65 40 01 25 00 " mean? where should i look to find what does responses mean?
Ragards

0 JasonB over 8 years ago in reply to Navid Torabi

TI__Expert 8950 points

Hi Navid,

With Z-Stack 3.0, you should be using the BDB commissioning methods to start a ZNP network.

Please see this guide:

e2e.ti.com/.../2056927

0 Navid Torabi over 8 years ago in reply to JasonB

Intellectual 850 points

Thanks a lot JasonB
What about my compiler defines? should i change them and get new hex too? are there ok to use BDB commissioning?

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Those APIs are supported by default ZNP and you don't have to add any compile option.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks friends good help
Is there anywhere complete minimum scenario to set ZC and ZR and ZED and connect them together by ZNP? something like "znp developing" document that shows what should be send to znp in what sequence in z-stack 3.0!! actually I'm a little confused about which commands are madatory like "APP_CNF_BDB_START_COMMISSIONING" and which commands are not neccessary to set simple zigbee network by znp!! which one should send first? and ...
I know finaly I'll find the right way to do this by reading different documents and community posts but it needs much time!! we need some reference code or figure or flowchart to understand whole scenario!! i'm not so lazy but i don't have much time to read all documents that i don't know which one should be usefull or not!!
Regards

0 Navid Torabi over 8 years ago in reply to JasonB

Intellectual 850 points

when should i send "APP_CNF_BDB_START_COMMISSIONING" ? I still want to set a ZC device without anything more and this is what i do:
-----------
1- FE 01 41 00 00 40 //SYS_RESET_REQ
2- FE 03 26 05 03 01 02 20 //ZCD_NV_STARTUP_OPTION
3- FE 01 41 00 00 40 //SYS_RESET_REQ
4- FE 04 26 05 83 02 FF FF A6 //ZCD_NV_PANID
5- FE 06 26 05 84 04 03 FF F8 00 A1 //ZCD_NV_CHANLIST
6- FE 03 26 05 87 01 00 A6 //ZCD_NV_LOGICAL_TYPE ( COORDINATOR)
7- FE 12 26 05 62 10 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 43 //ZCD_NV_PRECFGKEY
8- FE 03 26 05 63 01 01 43 //ZCD_NV_PRECFGKEYS_ENABLE
9- FE 24 21 09 01 01 00 20 FF FF FF FF FF FF FF FF 54 45 58 41 53 49 4E 53 54 52 55 4D 45 4E 54 53 00 00 00 00 00 00 00 00 31 //ZCD_NV_TC_LINK_KEY
10- FE 01 2F 05 04 2F //APP_CNF_BDB_START_COMMISSIONING
-------
after sending "APP_CNF_BDB_START_COMMISSIONING" i just receive:
-----
FE 01 6F 05 00 6B
sometimes I receive some 00 3F after that!
-----

whats wrong here? what else should i add? is there any problem with security key numbers?
Regards

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

You can refer to znp-bringup.zjs under Z-Tool\Scripts which shows you steps to setup ZC.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai Chen
Understanding this scrpit is another problem itself :)
I have run this file on z-tool and this is the resault, nothing received after AF_REGISTER!!
-----------------
*** SCRIPT STARTED : znp-bringup.zjs ***
ZB_SYSTEM_RESET to COM5

<TX>03:26:57.03 COM5 ZB_SYSTEM_RESET (0x4609)
ZB_SYSTEM_RESET to COM5

<TX>03:26:57.83 COM5 ZB_SYSTEM_RESET (0x4609)
ZB_SYSTEM_RESET to COM5

<TX>03:26:58.64 COM5 ZB_SYSTEM_RESET (0x4609)

<RX>03:26:59.06 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x00
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00
ZB_WRITE_CONFIGURATION to COM5

<TX>03:26:59.44 COM5 ZB_WRITE_CONFIGURATION (0x2605)
ConfigId: 0x03
Len: 0x01
Value: . (0x03)

<RX>03:26:59.46 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
Status: SUCCESS (0x0)
ZB_SYSTEM_RESET to COM5

<TX>03:26:59.65 COM5 ZB_SYSTEM_RESET (0x4609)
ZB_SYSTEM_RESET to COM5

<TX>03:27:00.45 COM5 ZB_SYSTEM_RESET (0x4609)
ZB_SYSTEM_RESET to COM5

<TX>03:27:01.26 COM5 ZB_SYSTEM_RESET (0x4609)
ZB_SYSTEM_RESET to COM5

<TX>03:27:02.06 COM5 ZB_SYSTEM_RESET (0x4609)

<RX>03:27:02.11 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x00
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00
ZB_WRITE_CONFIGURATION to COM5

<TX>03:27:02.87 COM5 ZB_WRITE_CONFIGURATION (0x2605)
ConfigId: 0x87
Len: 0x01
Value: . (0x00)

<RX>03:27:02.89 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
Status: SUCCESS (0x0)
ZB_WRITE_CONFIGURATION to COM5

<TX>03:27:03.08 COM5 ZB_WRITE_CONFIGURATION (0x2605)
ConfigId: 0x83
Len: 0x02
Value: .. (0xFF, 0xFF)

<RX>03:27:03.09 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
Status: SUCCESS (0x0)
ZB_WRITE_CONFIGURATION to COM5

<TX>03:27:03.28 COM5 ZB_WRITE_CONFIGURATION (0x2605)
ConfigId: 0x84
Len: 0x04
Value: .... (0x00, 0x00, 0x08, 0x00)

<RX>03:27:03.31 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
Status: SUCCESS (0x0)
ZB_WRITE_CONFIGURATION to COM5

<TX>03:27:03.48 COM5 ZB_WRITE_CONFIGURATION (0x2605)
ConfigId: 0x8F
Len: 0x01
Value: . (0x01)

<RX>03:27:03.51 COM5 ZB_WRITE_CONFIGURATION_RSP (0x6605)
Status: SUCCESS (0x0)
ZB_AF_REGISTER_REQUEST to COM5

<TX>03:27:03.69 COM5 AF_REGISTER (0x2400)
EndPoint: 0x07
AppProfID: 0x0104
AppDeviceId: 0x0100
AppDevVer: 0x00
LatencyReq: NO_LATENCY_REQS (0x0)
AppNumInClusters: 0x05
AppInClusterList: 0x0000, 0x0003, 0x0004, 0x0005, 0x0006
AppNumOutClusters: 0x01
AppOutClusterList: 0x0000

<RX>03:27:03.7 COM5 AF_REGISTER_SRSP (0x6400)
Status: afStatus_SUCCESS (0x0)
ZB_START_REQUEST to COM5

<TX>03:27:03.9 COM5 ZB_START_REQUEST (0x2600)
ZB_START_REQUEST to COM5

<TX>03:27:04.9 COM5 ZB_START_REQUEST (0x2600)

<RX>03:27:05.84 COM5 ZB_START_REQUEST_RSP (0x6600)
ZB_START_REQUEST to COM5

<TX>03:27:10.91 COM5 ZB_START_REQUEST (0x2600)
ZB_START_REQUEST to COM5

<TX>03:27:11.91 COM5 ZB_START_REQUEST (0x2600)
ZB_START_REQUEST to COM5

<TX>03:27:12.91 COM5 ZB_START_REQUEST (0x2600)
ZB_START_REQUEST to COM5

<TX>03:27:13.92 COM5 ZB_START_REQUEST (0x2600)
ZB_START_REQUEST to COM5

------------------------------------------------------------------------------------

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Try to refer to e2e.ti.com/.../3286.CC2530ZNP-Interface-Specification.pdf

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

I think my problem is common problem, everybody work with cc2530 znp should make a coordinator first of all!! how other people do this? as I understand there are a minimum specific steps to setup a device as coordinator in znp, I have read znp documents and i did it that doesn't work, just reading the documents will not solve my problem! how you and other peoples setup coordinator in znp? if my steps are wrong then what other steps should i use? if my steps are enough and true please tell me it's true then i check other things like firmware and etc.

0 Luis Luna over 8 years ago in reply to Navid Torabi

Expert 1620 points

Hi Navid,

I see that you are trying to take the ZNP as older versions of ZNP which might not work (Ej. the keys are not longer configurable that way because of the requirements of Z3.0).

Please state your requirements and needs, so we can suggest how to achieve this.

In the mid time, as an proof of concept, you can try to create a simple network using Z-Tool:

1.- Erase the memory of 3 devices, then flash 3 ZNP devices.

2.- Set the logical devices (Ej. 1 coordinator, 2 routers). Use SYS_OSAL_NV_WRITE to write the index 0x87, offset 0, len 1, value = [0 coordinator, 1 router, 2 end device]

3.- Reset the devices by sending SYS_RESET

4.- Optionally, but suggested, you can set the channel with APP_CNF_BDB_SET_CHANNEL, as proof of concept pick only one channel by setting isPrimary=TRUE and channel=the channel of your choise, then send the same command but with isPrimary=FALSE and channel=0 (Z3.0 support two channel masks and you do not want the devices to start commissioning in the second channel mask).

5.- Commission the devices. On Coordinator, send APP_CNF_BDB_START_COMMISSIONING with Formation, once the Coordinator has created the network (wait until you see nwk commands encrypted, which would be link status).

6.- Open the network, on the coordinator send APP_CNF_BDB_START_COMMISSIONING with NetworkSteering as parameter, this will cause the coordinator to open the network. You must see a nwk data frame (which is a ZDO permit joining), then join the other devices by using the same command (APP_CNF_BDB_START_COMMISSIONING with NetworkSteering).

7.- At this point you should have the devices in the network.

If you have any issues replicating this, please share a log so we can take a look in the steps you are getting troubles.

Hope this helps!

0 Navid Torabi over 8 years ago in reply to Luis Luna

Intellectual 850 points

Thanks a lot Luis, Certainly it'll help

what different if i use ZCD_NV_LOGICAL_TYPE instead of SYS_OSAL_NV_WRITE?

and the other question: in Z-STACK Monitor and Test API document I see 2 bytes for id, as you said it should be 0x87 for logical type, should i send 0x00 0x87 or 0x87 0x00? and where can i see what does each id mean for this command?

I'm a little not clear about channels too, first i should set a channel with Primary=TRUE and then set channel zero with Primary=FALSE?!! I don't understand why should i set to channel but I think it's not important now! :)

Regards

0 Navid Torabi over 8 years ago in reply to Navid Torabi

Intellectual 850 points

This is what i did:
------------------------
<TX>02:59:52.35 COM5 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>02:59:54.3 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x02
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<RX>03:00:40.91 COM5 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>03:00:40.9 COM5 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0087
Offset: 0x00
Len: 0x01
Value: . (0x00)

<TX>03:00:50.42 COM5 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>03:00:52.63 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x02
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<TX>03:01:08.77 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x04) Network Formation (0x4)

<RX>03:01:10.84 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>03:01:10.9 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>03:01:10.92 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x0D (Network Restored) (0xD)
Commissioning Mode: 0x00 (Initialization) (0x0)
Commissioning Mode: 0x01 (Initiator TL), 0x08 (Finding and Binding), 0x10 (Initialization) (0x19)

<RX>03:01:11.04 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x08 (Formation Failure) (0x8)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 0 (0x0)

<TX>03:01:20.56 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>03:01:20.58 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>03:01:20.59 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 227 (0xE3)
-----------------------------------------------------
why formation is fail? and how can i understand what does this notification numbers means if i don't use Z-TOOL and i send hex frame by means of mcu?
Thanks again

0 Navid Torabi over 8 years ago in reply to Navid Torabi

Intellectual 850 points

Hi again :)
lets take another look at what i did for coordinator and router to connect them at final:
first i set coordinator with these steps:

======================================== Coordinator ============================
2/1/2017 20:43:59.738 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
2/1/2017 20:44:01.926 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/1/2017 20:44:07.086 [TX] - FE 03 26 05 03 01 02 20 //ZCD_NV_STARTUP_OPTION
2/1/2017 20:44:07.095 [RX] - FE 01 66 05 00 62
2/1/2017 20:44:09.408 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
2/1/2017 20:44:12.202 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/1/2017 20:44:17.585 [TX] - FE 03 26 05 87 01 00 A6 //ZCD_NV_LOGICAL_TYPE ( COORDINATOR )
2/1/2017 20:44:17.596 [RX] - FE 01 66 05 00 62
2/1/2017 20:44:23.887 [TX] - FE 01 2F 05 04 2F // APP_CNF_BDB_START_COMMISSIONING ( FORMATION )
2/1/2017 20:44:25.542 [RX] - FE 01 6F 05 00 6B FE 01 45 C0 08 8C FE 03 4F 80 00 00 00 CC FE 01 45 C0 08 8C FE 01 45 C0 09 8D FE 03 4F 80 0D 00 19 D8
------------------------------ [TX] - FE 01 2F 05 02 29 // APP_CNF_BDB_START_COMMISSIONING ( STEERING )
------------------------------ [RX] - FE 01 6F 05 00 6B FE 03 4F 80 00 01 E3 2E
===============================================================================

after that i do these steps for router to connect them:
========================================== Router ===============================
2/1/2017 22:13:29.581 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
2/1/2017 22:13:31.521 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/1/2017 22:13:35.014 [TX] - FE 03 26 05 03 01 02 20 //ZCD_NV_STARTUP_OPTION
2/1/2017 22:13:35.036 [RX] - FE 01 66 05 00 62
2/1/2017 22:13:36.722 [TX] - FE 01 41 00 00 40 //SYS_RESET_REQ
2/1/2017 22:13:38.783 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/1/2017 22:13:40.233 [TX] - FE 03 26 05 87 01 01 A7 //ZCD_NV_LOGICAL_TYPE ( ROUTER )
2/1/2017 22:13:40.244 [RX] - FE 01 66 05 00 62
2/1/2017 22:13:43.484 [TX] - FE 01 2F 05 04 2F // APP_CNF_BDB_START_COMMISSIONING ( FORMATION )
2/1/2017 22:13:44.626 [RX] - FE 01 6F 05 00 6B FE 01 45 C0 02 86 FE 03 4F 80 00 00 00 CC FE 01 45 C0 02 86
=================================================================================

I think coordinator starts PAN and router are trying to join some coordinator but noting happens!!
what other steps should i do to connect them? or whats wrong on my way?
+ if they connect successfully than should i use AF_DATA_REQUEST and AF_DATA_INCOMING to transfer data between them?
with best Regards

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

I suggest you to use Ubiqua Packet Analyzer to check over the air messages and attach it so we can know exactly what happens.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YkKai, what hardware does it need? cc2530 debugger? or it can use znp uart too?!! or other stuff?!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

You need to use CC2531EMK as HW to work with Ubiqua Packet Analyzer.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Is there a way to use CC Debugger or CC2530 itself instead of CC2531EMK? it's not personal project and i can't buy anything more, it's my company order to me so i have just CC Debugger and some CC2530 soldered to board to make ZigBee network!! :(

0 Navid Torabi over 8 years ago in reply to Navid Torabi

Intellectual 850 points

i have connected CC Debugger and ubiqua found it!!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Cool!

0 Luis Luna over 8 years ago in reply to Navid Torabi

Expert 1620 points

Hi Navid,

SYS_OSAL_NV_WRITE is the name of the command to write in any Nv ID in the device, while ZCD_NV_LOGICAL_TYPE is the Nv ID that defines the logical device to be selected, in this sence, SYS_OSAL_NV_WRITE uses as part of its parameters Nv IDs such as ZCD_NV_LOGICAL_TYPE.

From the MCU you have to send 0x87 0x00 to specify the 0x0087 ID which is ZCD_NV_LOGICAL_TYPE.

In Z3.0 there is two channel mask, with Primary = TRUE, you set the channel mask 1, with Primary = FALSE you set the channel mask 2. Z3.0 commissioning methods uses both masks. If you have not set properly your networks, you may find your devices joining other networks that are not intended to do so. Setting the secondary channel to 0 helps to avoid this.

0 Luis Luna over 8 years ago in reply to Navid Torabi

Expert 1620 points

Hi Navid,

What you mean that you have a CC Debugger found by Ubiqua?
Can you capture OTA traffic?

0 Navid Torabi over 8 years ago in reply to Luis Luna

Intellectual 850 points

Hi Luis, thanks for your attention
I have connected my CC2530 debugger to my cc2530 through laptop usb port and after clicking add device button, it was on device list, I have added it but it was always idle or not found anything, I think ubiqua needs just cc2531EMK and doesn't work that way i tried :)
I think finally I have connected coordinator and router, because of getting 0x09 from coordinator and 0x07 from Router! but how can i check if they are connected or not? can coordinator sends simple data or ping to see if there is any Router connected? is there some instruction like "ping" to check connections?
Regards

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

As I remember, SmartRF05EB-CC2530EM can act as sniffer HW. I suggest you to setup sniffer to capture over the air messages to know what happens exactly.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai, I try this way too.
how can i understand if my coordinator and router are connected together or not? I need something like ping in TCP/IP that shows me if they can find each other!! my coordinator and router short address and IEEE address are available now but i don't know which command should i use to send data between them or just check if they are in same network!!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

There is not enough information from your ZNP output to judge anything. I still need sniffer log to know what happens. Try to download attached sniffer_fw_cc2530.hex to your CC2530DK and connect RS-232 cable to the RS-232 port on SmartRF05 to your PC. Then, you can start Ubiqua Packet Analyzer to open the COM port to see if it can sniff over the air messages.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai, I don't know why usually i think i need simple thing on my next step but your answers open new window to zigbee world for me!! :) i'm confuesed with some simple basic concepts of zigbee and znp but you think i understand what's sniffer and packet analyzer and how to use them and ...?!! :) I don't know maybe i can!! anyway it's nice to mee that some people like you try to help and i'm sure finally it helps!

this is what i did again: com5 is my coordinator and com3 is router, nothing happens between them and i'm just looking for a way to see reaction from one of them to make sure it's 2 devices network!!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

When you start coordinator (COM5) and router (COM3), do you see ZDO_END_DEVICE_ANNCE on COM5?

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

no I don't see!!
Should i use APP_CNF_BDB_START_COMMISSIONING (steering) for Router too? I do this, on Router when i send APP_CNF_BDB_START_COMMISSIONING ( formation) my ZDO_STATE_CHANGE_IND answer is 0x06 but after that i send ZDO_STATE_CHANGE_IND (steering) and now it changes to 0x07!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Yes, you have to use APP_CNF_BDB_START_COMMISSIONING on both coordinator and router. ZDO_STATE_CHANGE_IND changing to 0x07 should mean it joins coordinator as a router. However, you say you don't see ZDO_END_DEVICE_ANNCE on COM5. I think it's better to use sniffer to check and confirm it.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai.
Should i see ZDO_END_DEVICE_ANNCE on com5 automatically after Router confgs finish? if Yes i don't see any thing on com5 automatically that depends on Com3 changes!!
ok I try to do what you said about sniffer and packet monitoring but i'm not sure i can do those steps you said because of it's proccess! :/

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

If router or end device joins Zigbee network, they would broadcast ZDO_END_DEVICE_ANNCE and coordinator should receive it which you should see it on COM5.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Finally I got a response on coordinator after Router trying to join!! This is the response of coordinator:
ZC RX: 0C 45 CA F2 EE 8F 9E 4B 09 00 4B 12 00 00 00
I found it is "ZDO_TC_DEV_IND" the addresse are right ( IEEE and short address of Router which trying to join ), but I don't know what does this mean!! i see coordinator knows router addresses that trying to join but is it ok or it's s kind of errors?
-----------
another question:
when i flash my CC2530 and start to setup a coordinator after sending APP_CNF_BDB_START_COMMISSIONNG anything is ok, but after power off and next power on i see formation failure status 0x08! and it'll be on next tries to, until i flash my CC2530 and start again!! i have this problem in both case i use NV_RESTORE and i don't use it!! you see this failure here:
------------------
<TX>11:30:21.37 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x04) Network Formation (0x4)

<RX>11:30:21.89 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>11:30:21.91 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>11:30:21.91 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x0D (Network Restored) (0xD)
Commissioning Mode: 0x00 (Initialization) (0x0)
Commissioning Mode: 0x01 (Initiator TL), 0x08 (Finding and Binding), 0x10 (Initialization) (0x19)

<RX>11:30:22.09 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x08 (Formation Failure) (0x8)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 0 (0x0)
-----------------------
I think i know what's your answer YiKai: " use packet sniffer and ubiqua!! " ;) ( i'm joking YiKai but I have tried but unsuccessfully, because i just have CC Debugger and CC2530 chips soldered on board not any other Ti development kit or usb dongle!! )
Best Regards

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

I use my CC2530DK running ZNP 3.0 to act as coordinator and another CC2538DK running SampleSwitch to join coordinator. Everything works fine and the followings are my Ztool log for your reference.

<TX>05:00:39.35 COM1 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x00)

<RX>05:00:39.37 COM1 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>05:00:57.33 COM1 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00000800 (0x800)

<RX>05:00:57.33 COM1 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

<TX>05:03:32.85 COM1 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x04) Network Formation (0x4)

<RX>05:03:38.32 COM1 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>05:03:38.32 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:38.33 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 254 (0xFE)

<RX>05:03:38.59 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:38.85 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:39.12 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:39.38 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:39.64 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:39.9 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:40.17 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>05:03:40.71 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<RX>05:03:40.75 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 69 (0x45)

<TX>05:07:29.07 COM1 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

<RX>05:07:29.09 COM1 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>05:07:29.1 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 67 (0x43)

*** WARNING ***
    Unsupported or unformatted message received. Raw data: --> this is end node announcement.
    0C 45 CA AA B9 27 01 E5 00 00 4B 12 00 00 00

<TX>05:08:13.01 COM1 UTIL_GET_DEVICE_INFO (0x2700)

<RX>05:08:13.02 COM1 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001025822
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x01
    AssocDevicesList: 0xB9AA

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai, that was great.
All of my steps and responses are like you except two final lines on Device_info, I got NumAssocDevices: 0x00 and no device list!!
My bigger problem is that they work well just after i write hex file to my CC2530, if i power down it and power on again it'll not work and i get Formation_failure after sending "APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)". if i write hex file again it'll work again like yours but just for one time, the next try will be formation failure again!! I think it's something depends on NV_RESTORE!!
actually coordinator formation is ok just for first try after writing hex to flash, next tries will be fail until i write hex file again!!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Since you NumAssocDevices: 0x00 and no device list, I suspect the device doesn't join coordinator and that's why I keep asking you to use sniffer to check it. I see the same issue when I power recycle my ZNP and am still trying to find what happens.

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

I find the correct step to start ZNP after power recycle. You have to call APP_CNF_BDB_START_COMMISSIONING with Network Steering as input parameter again to start ZNP correctly.

<RX>09:53:00.33 COM1 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x01
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x00

<TX>09:53:04.43 COM1 UTIL_GET_DEVICE_INFO (0x2700)

<RX>09:53:04.46 COM1 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001025822
    ShortAddress: 0xFFFE
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_HOLD (0x0)
    NumAssocDevices: 0x00
    AssocDevicesList

<TX>09:53:11.35 COM1 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

<RX>09:53:12.8 COM1 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>09:53:12.82 COM1 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<RX>09:53:12.82 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x0D (Network Restored) (0xD)
    Commissioning Mode: 0x00 (Initialization) (0x0)
    Commissioning Mode: 0x01 (Initiator TL), 0x02 (Network Steering), 0x04 (Network Formation), 0x08 (Finding and Binding), 0x10 (Initialization) (0x1F)

<RX>09:53:13.03 COM1 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 67 (0x43)

<TX>09:53:18.96 COM1 UTIL_GET_DEVICE_INFO (0x2700)

<RX>09:53:18.99 COM1 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B0001025822
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Great Yikai, Thanks a lot. I'm going to check it and i should get requirments to use packet sniffer and analyzer at last!! ( if my company try to buy something more than a debugger and a chip :) )

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

You are welcome.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Hi again :)
I have tried as you said for recycling power problem, I just send network steering as input and i think no problem on coordinator but this time it didn't get anything from Router!! i mean coordinator didn't see the unsupported frame of Router address and..
what did you do for Router after recycling power? did you find Router after recycling power too? this is what I did for coordinator and Router:
============================================== Coordinator =====================================
Start Time: 2/7/2017 11:28:27 AM

<RX>11:28:44.86 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x01
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<TX>11:28:58.59 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>11:28:58.6 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9AAF
ShortAddress: 0xFFFE
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_HOLD (0x0)
NumAssocDevices: 0x00
AssocDevicesList

<TX>11:29:21.01 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>11:29:22.26 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>11:29:22.27 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>11:29:22.28 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x0D (Network Restored) (0xD)
Commissioning Mode: 0x00 (Initialization) (0x0)
Commissioning Mode: 0x01 (Initiator TL), 0x08 (Finding and Binding), 0x10 (Initialization) (0x19)

<RX>11:29:22.48 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 227 (0xE3)

<TX>11:30:49.67 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>11:30:49.68 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9AAF
ShortAddress: 0x0000
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ZB_COORD (0x9)
NumAssocDevices: 0x00
AssocDevicesList
==================================================== Router =======================================
Start Time: 2/7/2017 11:28:28 AM

<TX>11:29:43.4 COM3 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>11:29:45.64 COM3 SYS_RESET_RESPONSE (0x4180)
Reason: 0x02
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<TX>11:30:01 COM3 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0087
Offset: 0x00
Len: 0x01
Value: . (0x01)

<RX>11:30:01.02 COM3 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>11:30:04.86 COM3 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>11:30:06.9 COM3 SYS_RESET_RESPONSE (0x4180)
Reason: 0x02
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<RX>11:30:19.1 COM3 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9E8F
ShortAddress: 0xFFFE
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_HOLD (0x0)
NumAssocDevices: 0x00
AssocDevicesList

<TX>11:30:19.08 COM3 UTIL_GET_DEVICE_INFO (0x2700)

<TX>11:30:34.61 COM3 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>11:30:36.6 COM3 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>11:30:36.63 COM3 ZDO_STATE_CHANGE_IND (0x45C0)
State: 7 (0x7)

<RX>11:30:36.64 COM3 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x0D (Network Restored) (0xD)
Commissioning Mode: 0x00 (Initialization) (0x0)
Commissioning Mode: 89 (0x59)

<RX>11:30:36.82 COM3 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 227 (0xE3)

<TX>11:30:55.97 COM3 UTIL_GET_DEVICE_INFO (0x2700)

<RX>11:30:55.99 COM3 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9E8F
ShortAddress: 0x3EBA
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ROUTER (0x7)
NumAssocDevices: 0x00
AssocDevicesList
=========================================================================================================

I think we should do something different on Router after power recycling too, because i write flash again just to Router and your method on coordinator and it was ok, but on next try of Router it was unsuccessful connect again!! ( sorry my english is not so good i try to say what i mean!! )

How can i set TC Link key for coordinator and Router? maybe my joining problem is because of TC LINK KEY, isee different PRECFGKEY on my Coordinator and Router which try to join!!
+ I have a personal question!! Are you ti dependence or ti employee? or just a free person like me that tries freely to solve others problem ? :)

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

1. What do you mean "coordinator didn't see the unsupported frame of Router address?"
2. I am not ti dependence or ti employee. I am not free too. I work for living.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

1- I mean when it's first time after flashing it, I see coordinator reaction against Router on that frame which is Router IEEE and short address, also it's not join yet but coordinator and Router act again each other and i know half of my way is ok. but when nothing happens after Router tries to join it means something is wrong, now on that way you explained for coordinator it's ok after recycling power only if it was first power on Router, if I recycle the Router power, again i'll not get any reaction from Router on Coordinator!! I mean for next powerons on Router I think there is a little different scenario too!!
2- you are so nice that give your times to solve other people problems! I should find someway to compensate your help ;)
Regards

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

Guru 735695 points

For your reference, I do the same test on ZNP router, power recycle ZNP router and call APP_CNF_BDB_START_COMMISSIONING to start ZNP. I can see my ZNP router response to coordinator as usual from sniffer.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai
And finally may i see your IAR compiler Defined symbols too? it's mine!
---------
BDB_FINDING_BINDING_CAPABILITY_ENABLED=0
TC_LINKKEY_JOIN
NWK_MAX_DEVICE_LIST=10
ZDSECMGR_TC_DEVICE_MAX=30
ZNP_ENABLED
POWER_SAVING
FEATURE_SYSTEM_STATS
MT_GP_CB_FUNC
MT_SYS_FUNC
MT_UTIL_FUNC
MT_ZDO_FUNC
xHAL_SPI=FALSE
HAL_UART=TRUE
NV_RESTORE
---------------------------

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

I cannot access to my desktop now but I use default ZNP project without modification.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Hi again YiKai, i hope good times for you :)
I have disabled NV_RESTORE and instead of ZC and ZR, i use ZC and ED! The good news is that unlike Router, End Device joined successfully and coordinator shows number of associated devices = 1 !! but i have to problem in this case too! here is my frame sequences:
------------------------------------------- Coordinator --------------------------------------------------------------
2/9/2017 12:39:42.087 [TX] - FE 00 27 00 27
2/9/2017 12:39:42.095 [RX] - FE 0E 67 00 00 AF 9A 4B 09 00 4B 12 00 FE FF 07 00 00 41
2/9/2017 12:39:47.407 [TX] - FE 03 26 05 03 01 02 20
2/9/2017 12:39:47.424 [RX] - FE 01 66 05 00 62
2/9/2017 12:39:50.911 [TX] - FE 03 26 05 87 01 00 A6
2/9/2017 12:39:50.920 [RX] - FE 01 66 05 00 62
2/9/2017 12:39:57.277 [TX] - FE 01 41 00 00 40
2/9/2017 12:39:58.643 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/9/2017 12:40:01.295 [TX] - FE 01 2F 05 04 2F
2/9/2017 12:40:02.515 [RX] - FE 01 6F 05 00 6B FE 01 45 C0 08 8C FE 03 4F 80 00 00 00 CC FE 01 45 C0 08 8C FE 01 45 C0 08 8C FE 01 45 C0 09 8D FE 03 4F 80 0D 00 19 D8
2/9/2017 12:40:06.815 [TX] - FE 01 2F 05 02 29
2/9/2017 12:40:06.827 [RX] - FE 01 6F 05 00 6B FE 03 4F 80 00 01 E3 2E FE 0C 45 CA 1B 5C 8F 9E 4B 09 00 4B 12 00 00 00 CE
2/9/2017 12:40:52.148 [TX] - FE 00 27 00 27
2/9/2017 12:40:52.157 [RX] - FE 10 67 00 00 AF 9A 4B 09 00 4B 12 00 00 00 07 09 01 1B 5C 11
---------------------------------------------------------------- End Device ---------------------------------------------------------
2/9/2017 12:40:11.151 [TX] - FE 00 27 00 27
2/9/2017 12:40:11.158 [RX] - FE 0E 67 00 00 8F 9E 4B 09 00 4B 12 00 FE FF 07 00 00 65
2/9/2017 12:40:14.452 [TX] - FE 03 26 05 03 01 02 20
2/9/2017 12:40:14.470 [RX] - FE 01 66 05 00 62
2/9/2017 12:40:15.917 [TX] - FE 03 26 05 87 01 02 A4
2/9/2017 12:40:15.933 [RX] - FE 01 66 05 00 62
2/9/2017 12:40:18.219 [TX] - FE 01 2F 05 04 2F
2/9/2017 12:40:19.126 [RX] - FE 01 6F 05 00 6B FE 01 45 C0 02 86 FE 03 4F 80 01 02 65 AA
2/9/2017 12:40:21.628 [TX] - FE 01 41 00 00 40
2/9/2017 12:40:23.147 [RX] - FE 06 41 80 02 02 00 02 07 00 C2
2/9/2017 12:40:25.689 [TX] - FE 01 2F 05 02 29
2/9/2017 12:40:26.384 [RX] - FE 01 6F 05 00 6B FE 01 45 C0 02 86 FE 03 4F 80 01 01 65 A9 FE 01 45 C0 03 87 FE 01 45 C0 05 81 FE 01 45 C0 06 82 FE 03 4F 80 00 01 E3 2E
2/9/2017 12:40:37.089 [TX] - FE 00 27 00 27
2/9/2017 12:43:16.564 [TX] - FE 00 27 00 27
2/9/2017 12:43:19.745 [TX] - FE 01 41 00 00 40
no answer after joined network!!
========================================================
- The first problem is after checking UTIL_GET_DEVICE_INFO Response! I think the short address of associated device on coordinator is not same as End Device short address how ever i don't have any other device but IEEE address is correct on both of them!! ( just a coordinator and end device ) maybe coordinator changes address of ED?
- The seconde problem is this: As you say on ED, after in joins the netwrok i have tried to get device info but no response on it!! and no response for any other commands too ( on ED ). I have tried this for many times but all times ED had no response to my znp commands after it joins the network!!
Regards

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

1. Where do you see the device short address is changed?
2. You have to write NV item ZCD_NV_ZDO_DIRECT_CB to 1 to enable receiving ZDO response.

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks YiKai
1- before starting to join i have checked ED short address by sending "UTIL_GET_DEVICE_INFO" but it's not here. i'll check again later about this, maybe i'm wrong!
2- sorry I didn't understand what you mean!! where and how should i do this?! can you give me hex frame for it?! or it's compiler option?!! when should i do this? for ED or ZC?!

0 YiKai Chen over 8 years ago in reply to Navid Torabi

Guru 735695 points

Try to refer to sunmaysky.blogspot.tw/.../use-ztool-z-stack-30-znp-to-set-up.html

0 Navid Torabi over 8 years ago in reply to YiKai Chen

Intellectual 850 points

Thanks again YiKai
It's strange that all steps are like and I got :ZDO_END_DEVICE_ANNCE_IND" too but still Coordinator shows NumAssocDevices : 0x00!!!! My coordinator likes to live alone forever!!
This is my Z-TOOL commands sequence:
----------------------------------------------------- Coordinator ----------------------------------------------------------
Start Time: 2/10/2017 10:38:48 AM

<RX>10:39:25.06 COM5 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>10:39:25.05 COM5 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0003
Offset: 0x00
Len: 0x01
Value: . (0x03)

<TX>10:39:33.36 COM5 SYS_RESET (0x4100)
Type: 0x00 (HARD RESET) (0x0)

<RX>10:39:35.09 COM5 SYS_RESET_RESPONSE (0x4180)
Reason: 0x02
TransportRev: 0x02
Product: 0x00
MajorRel: 0x02
MinorRel: 0x07
HwRev: 0x00

<TX>10:39:55.14 COM5 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0087
Offset: 0x00
Len: 0x01
Value: . (0x00)

<RX>10:39:55.15 COM5 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>10:40:37.92 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x04) Network Formation (0x4)

<RX>10:40:38.55 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>10:40:38.55 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>10:40:38.56 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 1 (0x1)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 101 (0x65)

<RX>10:40:38.82 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>10:40:39.08 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>10:40:39.34 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>10:40:39.61 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 8 (0x8)

<RX>10:40:40.16 COM5 ZDO_STATE_CHANGE_IND (0x45C0)
State: 9 (0x9)

<RX>10:40:40.16 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x02 (Formation) (0x2)
Commissioning Mode: 0x01 (Initiator TL), 0x04 (Network Formation), 0x08 (Finding and Binding), 0x20 (Parent Lost) (0x2D)

<TX>10:41:09.07 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:41:09.08 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9AAF
ShortAddress: 0x0000
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ZB_COORD (0x9)
NumAssocDevices: 0x00
AssocDevicesList

<TX>10:41:50.12 COM5 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x008F
Offset: 0x00
Len: 0x01
Value: . (0x01)

<RX>10:41:50.14 COM5 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>10:42:53.36 COM5 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>10:42:53.38 COM5 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>10:42:53.39 COM5 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
SrcAddr: 0x0000
Status: ZDP_SUCCESS (0x0)

<RX>10:42:53.39 COM5 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 227 (0xE3)

*** WARNING ***
Unsupported or unformatted message received. Raw data:
0C 45 CA 0F 30 8F 9E 4B 09 00 4B 12 00 00 00

<RX>10:43:09.3 COM5 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
SrcAddr: 0x300F
NwkAddr: 0x300F
IEEEAddr: 0x00124B00094B9E8F
Capabilities: 0x8E

<TX>10:43:49.35 COM5 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:43:49.36 COM5 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9AAF
ShortAddress: 0x0000
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ZB_COORD (0x9)
NumAssocDevices: 0x00
AssocDevicesList
--------------------------------- Router ---------------------------------
Start Time: 2/10/2017 10:38:49 AM

<TX>10:42:34.55 COM3 SYS_OSAL_NV_WRITE (0x2109)
Id: 0x0087
Offset: 0x00
Len: 0x01
Value: . (0x01)

<RX>10:42:34.58 COM3 SYS_OSAL_NV_WRITE_SRSP (0x6109)
Status: SUCCESS (0x0)

<TX>10:43:05.5 COM3 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
CommissioningMode: (0x02) Network Steering (0x2)

<RX>10:43:06.48 COM3 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
Status: SUCCESS (0x0)

<RX>10:43:06.51 COM3 ZDO_STATE_CHANGE_IND (0x45C0)
State: INVALID_PARAMETER (0x2)

<RX>10:43:06.54 COM3 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 1 (0x1)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 101 (0x65)

<RX>10:43:06.75 COM3 ZDO_STATE_CHANGE_IND (0x45C0)
State: 3 (0x3)

<RX>10:43:07.28 COM3 ZDO_STATE_CHANGE_IND (0x45C0)
State: 5 (0x5)

<RX>10:43:09.28 COM3 ZDO_STATE_CHANGE_IND (0x45C0)
State: 7 (0x7)

<RX>10:43:09.8 COM3 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
Status: 0x00 (Success) (0x0)
Commissioning Mode: 0x01 (Network Steering) (0x1)
Commissioning Mode: 227 (0xE3)

<TX>10:43:43.06 COM3 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:43:43.07 COM3 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
Status: SUCCESS (0x0)
IEEEAddr: 0x00124B00094B9E8F
ShortAddress: 0x300F
DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
DeviceState: DEV_ROUTER (0x7)
NumAssocDevices: 0x00
AssocDevicesList
===================================================================================================================

Zigbee & Thread

Zigbee & Thread forum

CC2530EM: ZNP developing problem!!