Wireless MCU中的主题 Re: coordinator does not send network key

coordinator does not send network key

286520810 — Mon, 08 Jun 2020 09:32:16 GMT

I use jn5169 as coordinator and routing. When the gateway accesses more than 30 sub devices, the latter one has already initiated association request when entering the network, and the routing device has also replied successfully. After updating to the coordinator, the coordinator does not send out the network key, resulting in the sub device unable to enter the network.

The coordinator uses jn-an-1216-zigbee-3-0-iot-control bridge, and the SDK version is jn-sw-4170 v1840. Sub equipment SDK:JN-SW-4168 v1620.

The attachment is the capture log and coordinator zpscfg file.

Re: coordinator does not send network key

mario_castaneda — Tue, 09 Jun 2020 02:21:19 GMT

Hi Haorong,

Is it possible that you could provide your network key?

However, what is the table size that you have set?

Please look ZigBee 3.0 Stack User Guide

https://www.nxp.com/docs/en/user-guide/JN-UG-3113.pdf

B.5 Table Configuration Guidelines

100 Nodes Example

Neighbour Table: = 26

set to 26 - this is the minimum size required for a ZigBee-Compliant Platform

Address Map Table = 36

The Address Map table on a node is used to keep a record of the address-pairs of network nodes with which the local node needs to communicate directly

MAC Address Table = Neighbour Table + Address Map = 62

The entries in the MAC Address table are referenced from entries of both the Neighbour table and Address Map table

Routing Table (it could be equal to 100)

The default size of the Routing table is 70, which should be sufficient for most applications

Regards,

Mario

Re: coordinator does not send network key

286520810 — Tue, 09 Jun 2020 03:50:49 GMT

Hi Mario,

network key:BF:F8:9D:BE:2B:74:E9:9A:57:B0:F5:36:43:AC:C1:92

new question:Which one do I choose to compile?

Serial port appears these logs, how should I check them?

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

[11:40:12.536] ** Control Bridge Reset** pin 13, level Off

[11:40:12.614]

[11:40:12.614] !!! Trap error

[11:40:12.614] u32PICMR = 0 : u32PICSR = 8000

[11:40:12.614] u32PICMSR = 0 : u32IPMR = 0

[11:40:12.614] u32IHPR = f : u32AINT = 8000 u32PINT 0

[11:40:12.614] EPCR = b987a : EEAR = 0

[11:40:12.614] Stack dump:

[11:40:12.614] 4007f54 : 000003fc

[11:40:12.614] 4007f58 : 0008325f

[11:40:12.614] 4007f5c : 673a7ac3

[11:40:12.614] 4007f60 : 000b987a

[11:40:12.614] 4007f64 : 00000000

[11:40:12.614] 4007f68 : 00000000

[11:40:12.614] 4007f6c : 0000000f

[11:40:12.614] 4007f70 : 00000000

[11:40:12.614] 4007f74 : 00008000

[11:40:12.614] 4007f78 : 00000000

[11:40:12.614] 4007f7c : 00000000

[11:40:12.614] 4007f80 : 00008000

[11:40:12.614] 4007f84 : 04006570

[11:40:12.614] 4007f88 : 00083281

[11:40:12.614] 4007f8c : 00000001

[11:40:12.614] 4007f90 : 000b98d7

[11:40:12.614] 4007f94 : 00000005

[11:40:12.614] 4007f98 : 000b98d7

[11:40:12.614] 4007f9c : 04004d88

[11:40:12.614] 4007fa0 : 0009998d

[11:40:12.614] 4007fa4 : 000003fc

[11:40:12.614] 4007fa8 : 0008a363

[11:40:12.614] 4007fac : 81ca0020

[11:40:12.614] 4007fb0 : cb7bb6b5

[11:40:12.614] 4007fb4 : 69784dfe

[11:40:12.614] 4007fb8 : 100a85b9

[11:40:12.614] 4007fbc : 88400a18

[11:40:12.614] 4007fc0 : 02c77890

[11:40:12.614] 4007fc4 : 9f002be1

[11:40:12.614] 4007fc8 : d8ccaa5a

[11:40:12.614] 4007fcc : e4542562

[11:40:12.614] 4007fd0 : 56367f7e

[11:40:12.614] 4007fd4 : d3c73ff3

[11:40:12.614] 4007fd8 : cbffdb1e

[11:40:12.614] 4007fdc : 673a7ac3

[11:40:12.614] 4007fe0 : 7f87eee5

[11:40:12.614] 4007fe4 : 000003fc

[11:40:12.614] 4007fe8 : 00001ae8

[11:40:12.614] 4007fec : 00000000

[11:40:12.614] 4007ff0 : 00000000

[11:40:12.614] 4007ff4 : 0009a9a9

[11:40:12.614] 4007ff8 : 76543210

[11:40:12.614] 4007ffc : fedcba98

[11:40:12.614]

Best Regards

Re: coordinator does not send network key

mario_castaneda — Tue, 09 Jun 2020 04:50:42 GMT

Hi,

It will depend on the application that you want full functionality, the example could support coordinator, router, or end device, depending on the configuration that you make. The bin file will require more memory.

Did you modify the code? What are the changes that you did?

I am checking your sniffer log.

Regards,

Mario

Re: coordinator does not send network key

286520810 — Tue, 09 Jun 2020 06:15:50 GMT

Hi Mario,

I only need a coordinator for the gateway. Do you want to select "ZigbeeNodeControlBridge_Coordinator_1000000(JN5169)"?

I just follow your 100 nodes example to modify zpscfg，The following log will appear：

[14:00:07.109] EXB EXCEPTION @ 000b3fc8 (EA: 616e6365 SK: 04007f04 HP: 04005f9c)Stack dump:

[14:00:07.109] 4007f04 : 00000008

[14:00:07.109] 4007f08 : 616e6365

[14:00:07.109] 4007f0c : 000b3fc8

[14:00:07.109] 4007f10 : 00081347

[14:00:07.109] 4007f14 : 00000008

[14:00:07.109] 4007f18 : 0009b723

[14:00:07.109] 4007f1c : 0a04f005

[14:00:07.109] 4007f20 : 04003928

[14:00:07.109] 4007f24 : 00007f9a

[14:00:07.109] 4007f28 : 04007f5f

[14:00:07.109] 4007f2c : 04005a34

[14:00:07.109] 4007f30 : 000a44a0

[14:00:07.109] 4007f34 : f005020d

[14:00:07.109] 4007f38 : 00000005

[14:00:07.109] 4007f3c : 04003a2c

[14:00:07.109] 4007f40 : 000a44e3

[14:00:07.109] 4007f44 : 00045914

[14:00:07.109] 4007f48 : 04007f5f

[14:00:07.109] 4007f4c : 0005020d

[14:00:07.109] 4007f50 : 04005a34

[14:00:07.109] 4007f54 : 00000104

[14:00:07.109] 4007f58 : 000a335f

[14:00:07.109] 4007f5c : 04006814

[14:00:07.109] 4007f60 : 04005a4c

[14:00:07.109] 4007f64 : 00000024

[14:00:07.109] 4007f68 : 00000004

[14:00:07.109] 4007f6c : 04000150

[14:00:07.109] 4007f70 : 040002b0

[14:00:07.109] 4007f74 : 00000001

[14:00:07.109] 4007f78 : 000a33d5

[14:00:07.109] 4007f7c : 04007f9a

[14:00:07.109] 4007f80 : 00000118

[14:00:07.109] 4007f84 : 04003928

[14:00:07.109] 4007f88 : 0000f005

[14:00:07.109] 4007f8c : 00000000

[14:00:07.109] 4007f90 : 00000001

[14:00:07.109] 4007f94 : 00000024

[14:00:07.109] 4007f98 : 00000004

[14:00:07.109] 4007f9c : 04000150

[14:00:07.109] 4007fa0 : 040002b0

[14:00:07.109] 4007fa4 : 00000008

[14:00:07.109] 4007fa8 : 00089013

[14:00:07.109] 4007fac : 80ca0020

[14:00:07.109] 4007fb0 : cb7ba6f5

[14:00:07.109] 4007fb4 : 09284dfe

[14:00:07.109] 4007fb8 : 000285b9

[14:00:07.109] 4007fbc : 88000a18

[14:00:07.109] 4007fc0 : 06076990

[14:00:07.109] 4007fc4 : 9f002be0

[14:00:07.109] 4007fc8 : ccc8a84a

[14:00:07.109] 4007fcc : e4542563

[14:00:07.109] 4007fd0 : 00000001

[14:00:07.109] 4007fd4 : 00000024

[14:00:07.109] 4007fd8 : 00000004

[14:00:07.109] 4007fdc : 04000150

[14:00:07.109] 4007fe0 : 040002b0

[14:00:07.109] 4007fe4 : 00000008

[14:00:07.109] 4007fe8 : 00001ae8

[14:00:07.109] 4007fec : 00000000

[14:00:07.109] 4007ff0 : 00000000

[14:00:07.109] 4007ff4 : 00095ab1

[14:00:07.109] 4007ff8 : 76543210

[14:00:07.109] 4007ffc : fedcba98

[14:00:07.109]

Compile log

text data bss dec hex
199834 2548 27985 230367 383df

Is there any memory overflow?

Re: coordinator does not send network key

mario_castaneda — Tue, 09 Jun 2020 16:41:51 GMT

Hi,

Ii could be a memory overflow. Remember that increasing the memory size, it will require more memory, also I recommend to use the Coordinator example, not the full functionality.

Please look at the Please look ZigBee 3.0 Stack User Guide

https://www.nxp.com/docs/en/user-guide/JN-UG-3113.pdf

B.5 Table Configuration Guidelines

Also, please change the next define #define ZNC_MAX_TCLK_DEVICES in the app_common.h file

Regards,

Mario

Re: coordinator does not send network key

286520810 — Sat, 13 Jun 2020 02:25:30 GMT

Hi Mario

I can add 60 devices after I modify it according to your configuration. But I want to add more than 70.

Address Map Table = 36, Does this value mean that only 36 routes can be added?

100 Nodes Example
Neighbour Table: = 26
set to 26 - this is the minimum size required for a ZigBee-Compliant Platform
Address Map Table = 36
The Address Map table on a node is used to keep a record of the address-pairs of network nodes with which the local node needs to communicate directly
MAC Address Table = Neighbour Table + Address Map = 62
The entries in the MAC Address table are referenced from entries of both the Neighbour table and Address Map table
Routing Table (it could be equal to 100)
The default size of the Routing table is 70, which should be sufficient for most applications

I found that when I set "APS Key Table" value to 1, the program will crash. When I set it to 10, it will not run normally. I want to know how to set these two values.

Re: coordinator does not send network key

mario_castaneda — Mon, 15 Jun 2020 23:56:45 GMT

Hi Haorong,

Does this value mean that only 36 routes can be added?

No, exactly the routers could be end devices. The size is of the devices that are connected directly to the TC. The Address Map Table could be equal to the routing table.

I am not sure what are you trying to do. but you could change the APS key table, this will help you if you are working with install codes, for example.

Regards,

Mario

Re: coordinator does not send network key

LChll — Thu, 29 Oct 2020 10:15:03 GMT

Hi Mario,

I ran into the same problem. I cannot add more devices after more than 40 devices.
Change the Maximum Number of Nodes from 36 to 100, the Address Map Table Size from 10 to 36, the routing Table Size from 127 to 100, Mac Table Size = Neighbour Table + Address Map = 62.
The Device Table Size is still 36 and has not changed. Is this the problem?
Can't add devices yet, why is this? what should I do?

Re: coordinator does not send network key

LChll — Fri, 30 Oct 2020 09:51:14 GMT

How big can this Active Neighbour Table Size be changed? Has any influence on this?