https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6387070Thu, 18 Jun 2026 04:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d1eaab5e-d818-4187-af6b-39336feb6aa0baosong xiee2e.ti.com/.../C.txt e2e.ti.com/.../R.txthttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6387046Thu, 18 Jun 2026 04:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:348b31b2-9eb6-427b-8d0c-54b636304be6baosong xieWe obtained the total capacity of the network through the interface &quot;zb_nwk_get_total_capacity()&quot;, and it is exactly 100 the value set by SYSCFG.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6387044Thu, 18 Jun 2026 03:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f86772aa-400f-4720-b5b5-bbb640b059a1baosong xieWe conducted tests on version V9.20（simplelink_lowpower_f3_sdk_9_20_00_81），The &quot;Network Maximum Children&quot; parameter in SYSCFG is configured as 100 and The &quot;Network Maximum End Device Capacity&quot; parameter in SYSCFG is configured as 50. Build a Zigbee R23 network consisting of 50 routers,the routing nodes are connected to the network one by one, When the 44th router node is connected to the network, it cannot join the network. Then we powered off the 43 previously connected router nodes and focused solely on the network connection process of the 44th router node. We obtained the log files of the Zigbee frames in the air，and obtained the serial port logs of the coordinator and the 44th router node.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1656024/cc26xx-resources-matter-v-1-5---not-able-to-find-support-for-cc2652r7/6386031Wed, 17 Jun 2026 13:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:220e0fa2-4bf0-46da-ace9-c48c1ba9f75bRyan Brown1Hi Adesh, TI is currently in the process of certifying our Thread 1.4 and Matter 1.5 solution by September 2026. However, this will be performed for CC2755xx platform and all variants. In truth the CC2652R7 does not have enough flash memory to act as a Matter end device but could perform the task of a Thread RCP for a Matter fabric controller. TI has enabled an evaluation ready software support via down-stream forks of Open Thread and Matter . Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1656024/cc26xx-resources-matter-v-1-5---not-able-to-find-support-for-cc2652r7Wed, 17 Jun 2026 03:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d3374213-ad53-4837-97f8-6a81358f0124Adesh AgarwalPart Number: CC26XX-RESOURCES Other Parts Discussed in Thread: LP-CC2652R7 , CC2652R7 Hi Team, I am unable to find Matter 1.5 support documentation or software support for the LP-CC2652R7 LaunchPad. Could you please provide the relevant link or documentation for Matter 1.5 support on the LP-CC2652R7 platform? Any guidance regarding the required SDK version, example projects, or migration steps would also be appreciated.LP-CC2652R7CC26XX-RESOURCESCC2652R7https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1654773/cc2652p-zigbee-fragment-can-t-receive-the-fragment-packet-with-0xff-dstendpoint-in-sdk-8-30/6384384Tue, 16 Jun 2026 13:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:59a50c5d-4134-48bc-903c-1dc6b764607bRyan Brown1We are aligned and I&#39;ve sent you a direct message. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1654773/cc2652p-zigbee-fragment-can-t-receive-the-fragment-packet-with-0xff-dstendpoint-in-sdk-8-30/6383647Tue, 16 Jun 2026 03:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5d23b7f5-9a85-4d42-bba4-762c2e1bb19eAries Lordfragmented packets with 0xFF broadcast endpoint is useful in Zigbee Application. I have tried to fix this issue in &quot;aps_frag.c&quot; of Z-stack 3.0.2. But I have no this source file of SDK 8.30. e2e.ti.com/.../aps_5F00_frag.chttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1654773/cc2652p-zigbee-fragment-can-t-receive-the-fragment-packet-with-0xff-dstendpoint-in-sdk-8-30/6380948Fri, 12 Jun 2026 12:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:68815925-036e-4473-874a-b17249c1062dRyan Brown1Hi Aries, The APS fragmentation layer of the Z-Stack source libraries will discard fragmented packets if the endpoint is not registered into the endpoint description list, which applies to the 0xFF broadcast endpoint. To work around this limitation you can send the fragmented packets to a direct registered endpoint or break up the large APS packet outside of the packet fragmentation feature context. I have not further looked into what would happen if the 0xFF endpoint were attempted to be registered by the application. The delay for AF_DATA_CONFIRM failure will depend on whether APS ACK is enabled and Packet Sending parameters set in SysConfig (like NWK Data Retries, APS Retries, and APC ACK Wait Duration) Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1654773/cc2652p-zigbee-fragment-can-t-receive-the-fragment-packet-with-0xff-dstendpoint-in-sdk-8-30Fri, 12 Jun 2026 03:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4a720cb3-143b-4f9c-8c0b-34083ae322efAries LordPart Number: CC2652P Other Parts Discussed in Thread: SYSCONFIG , Z-STACK A CC2652P send a fragment packet(aps data is 90 byte) to another CC2652P and DstEndPoint is 0xFF, the other CC2652P can&#39;t receive this packet. And the sender CC2652P will wait for long time(more than 15s) and trigger AF_DATA_CONFIRM with failure status.CC2652PZ-StackSYSCONFIGhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6379331Thu, 11 Jun 2026 13:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:367ca601-1a92-42d9-9766-e137b9650799Ryan Brown1Do you have any sniffer logs or debugging stack return statuses of additional devices failing to join when the maximum 31 devices has been reached? How does the Zigbee network behave at this point? Are more devices allowed if ZR were introduced into the network? Although not your target device, have you tried a CC2745R10-Q1 LaunchPad to determine if the results are similar? Have you considered evaluating the latest F3 SDK v9.20 to determine whether the results are similar? [quote userid=&quot;655090&quot; url=&quot;~/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6376709&quot;]I have tested that the coordinator can connect to a maximum of 31 routers.I have also tested that the coordinator can connect a maximum of only 31 end device nodes.[/quote] Is it only 31 maximum withany given combination of ZR and ZED, and are all ZR/ZED directly neighboring/associating with the ZC or for example can ZED join through other ZR? Zigbee R&amp;D has suggested that ZB_DEFAULT_MAX_CHILDREN might be hardcoded to 32U in zb_config_common.h from the pre-built libraries of this SDK. They have suggested potentially fixing this by calling zb_set_max_children(MAX_CHILDREN) in the ZC application after ZB_INIT() and before zboss_start_no_autostart(). Can you please implement this workaround and give feedback on its efficacy? And could you also provide a debug print of gc_neighbor_table_size at runtime after stack initialization? This would provide further evidence. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6378552Thu, 11 Jun 2026 02:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8a289110-6f5f-486b-9686-21c90273e29dbaosong xieOnly the SYSCFG configuration file was changed, but the zb_mem_config_lprf3.h file was not modified.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6377539Wed, 10 Jun 2026 13:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:407b9c20-bcc6-490c-8e90-aa8a61aa971fRyan Brown1I do not think the NVS memory is the issue in your current setup. I would like to further understand your changes to the zb_mem_config_* implementation inside of the TI Zigbee example projects. Can you please provide your application .c file, Sysconfig, and any changes to zb_mem_config_lprf3.h for review? Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6376709Wed, 10 Jun 2026 01:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c7871e10-d15e-4053-bfa0-5a4a005ec327baosong xieI have tested that the coordinator can connect to a maximum of 31 routers.I have also tested that the coordinator can connect a maximum of only 31 end device nodes.The &quot;Network Maximum Children&quot; parameter in syscfg is set to 128. I found that when the coordinator uses the default NVS value 0x1000 of the SYSCFG , The coordinator can connect to a maximum of only a few dozen nodes,If the size of NVS is changed to 0x2000, the coordinator can connect up to 31 nodes, But continuing to increase the size of NVS does not change the number of nodes joined the coordinator. I know that the NV of the coordinator will store the link keys and IEEE address information of each joined node, So I&#39;m wondering if the NVS space is what limits the network size of the coordinator? I am using the CC2340R53. Its RAM has a capacity of 64K, so it should not be the RAM space limitation that restricts the network scale of the coordinator.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodes/6375779Tue, 09 Jun 2026 13:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ce047500-6913-4311-8409-377ede2415c0Ryan Brown1Hi baosong, Here is additional information on the Zigbee stack RAM usage configuration . As SimpleLink F3 SDK Zigbee projects have ZB_CONFIGURABLE_MEM defined in zb_vendor_lpf3_sdk.h, zb_mem_config_lprf3.h is referenced and uses ZB_CONFIG_LIGHT_TRAFFIC, ZB_CONFIG_APPLICATION_MODERATE, and MAX_CHILDREN (from ti_zigbee_config.h generated by SysConfig) which configure the definitions inside of the zb_mem_config_common.h file. Please make sure you are changing the appropriate locations of these definitions and confirm in a debug setting that these values are as you expect. Currently it appears that the stack is configured to support a maximum of 32 nodes which produces the stop at 31 (plus local device itself). There should not be a NVRAM limitation which hinders the number of devices which can join, and the CC2340R53 is capable of supporting more than 32 Zigbee devices. Are you using a mesh network (i.e. routers) or do you have all ZED connecting directly to the ZC? Can you please share all changes you&#39;ve applied to the baseline TI out-of-box example? Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1653445/cc2340r5-the-cc2350r53-zboss-zigbee-how-to-achieve-a-network-scale-of-128-nodesTue, 09 Jun 2026 04:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1672e2c1-7f1f-42fa-99ea-ff4dd3271e52baosong xiePart Number: CC2340R5 Other Parts Discussed in Thread: SYSCONFIG , CC2745R10-Q1 SDK version: simplelink_lowpower_f3_sdk_9_14_02_16 Reference: zboss-user-guide Configuration file Usage Maximum number of nodes zb_mem_config_min.h Simple applications and small networks. 16 zb_mem_config_med.h Applications without huge demands on Zigbee features, for example broadcast transmissions, binding and group membership entries. 32 zb_mem_config_max.h Complex applications and huge networks. 128 A large-scale network should be capable of accommodating 128 nodes. However, using the configuration in zb_mem_config_max.h. The actual test ,the maximum number of nodes that the coordinator can connect to is only 31. Increasing the NVRAM did not improve anything either,In the ZBOSS protocol stack, is it true that NV (Non-Volatile Memory) is limited to a maximum size of 8K? This results in the maximum network size being limited to 32.CC2340R5SYSCONFIGCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/6354064Thu, 21 May 2026 09:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:70464ced-5a19-4f87-8528-12b57b7ed016srinivas muniswamiHi Team, Thanks, I have submitted my files for review to the following ID connectivity-24ghz-hw-review@list.ti.com But there is no acknowledgement or response Regards Srinivashttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/6352678Wed, 20 May 2026 14:08:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:44c0bc93-a1f5-4d6e-adc9-559ae55aaf00Ryan Brown1Hi srinivas, You would need to submit your schematic and layout design files to SIMPLELINK-2-4GHZ-DESIGN-REVIEWS for further review since it is apparent with the range you are now observing that the external CC2592 power amplifier must be connected and controlled correctly since you are able realize up to 50 feet of range. Unfortunately this means that the PCB antenna design could be suboptimal which is resulting in poorer performance than expected. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/6352496Wed, 20 May 2026 11:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:24872d93-503c-49df-9dca-c8c5f2f6f32eZCHi Srinivas, I took a quick look at your PCB layout in the previous thread you linked. My initial impression is that the TI reference design layout hasn&#39;t been as closely followed as we would recommend. I would strongly advise submitting your design files for review using 2.4 GHz Design Review Submission: https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS You can then get more targeted feedback and implement the changes. I&#39;m not sure if that has been done yet, but should be as the first step if it hasn&#39;t. Regards, Zackhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issueWed, 20 May 2026 05:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c40cd4e6-d879-4c6d-bac2-60389981deb8srinivas muniswamiPart Number: CC2652R Other Parts Discussed in Thread: CC2592 Hi Team, Continuing the discussion, As suggested we have tested the results. Kinldy find the attached test results in the document Home_automation_Range_test_report.pdf Kinldy check and share us your feedback to overcome the issues Regards Srinivasbuilding automationSIMPLELINK-2-4GHZ-DESIGN-REVIEWSCC2652RCC2592https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647247/cc2538-cc2592emk-electronic-door-lock---zigbee-development-project/6350557Tue, 19 May 2026 12:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6c56e81b-39ad-4763-8c21-5957540247f8Ryan Brown1Hi Prince, You should certainly be evaluating the CC23XX / CC27XX device family using the SimpleLink Low Power F3 SDK . Further device selection depends on whether a module is needed (coming later this year), output power (PA enabled devices for up to +20 dBm instead of +8 or +10 dBm maximum on non-PA devices), flash memory requirements (CC2340R5 has 512 kB whereas the CC2755x10 is , RAM restrictions (CC2340R5 is 36/64 kB whereas CC2755x10 is 162 kB), etc. You can reference the Datasheet and Technical Reference Manual (TRM) of each device for more information. CC2340R5 , LP-EM-CC2340R5 CC2755R10 , LP-EM-CC2745R10-Q1 CC2755P10 Zigbee User&#39;s Guide Zigbee SimpleLink Academy Labs Zigbee DoorLock ZCL APIs CC2340R5 CSA compliancy CC27xx CSA compliancy Regards, Ryan