<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zigbee &amp;amp; Thread forum - Recent Threads</title><link>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 Jun 2026 12:52:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum" /><item><title>CC2652P: Zigbee Fragment can't receive the fragment packet with 0xFF DstEndPoint. In SDK 8.30</title><link>https://e2e.ti.com/thread/1654773?ContentTypeID=0</link><pubDate>Fri, 12 Jun 2026 03:37:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4a720cb3-143b-4f9c-8c0b-34083ae322ef</guid><dc:creator>Aries Lord</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1654773?ContentTypeID=0</comments><wfw:commentRss>https://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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2652P&lt;/p&gt;&lt;p&gt;&amp;nbsp; &amp;nbsp;A CC2652P send a fragment packet(aps data is 90 byte) to another CC2652P and DstEndPoint is 0xFF, the other CC2652P can&amp;#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.&lt;/p&gt;</description></item><item><title>RE: CC2652P: Zigbee Fragment can't receive the fragment packet with 0xFF DstEndPoint. In SDK 8.30</title><link>https://e2e.ti.com/thread/6380948?ContentTypeID=1</link><pubDate>Fri, 12 Jun 2026 12:52:29 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:68815925-036e-4473-874a-b17249c1062d</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6380948?ContentTypeID=1</comments><wfw:commentRss>https://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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi Aries,&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp; 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.&amp;nbsp; I have not further looked into what would happen if the 0xFF endpoint were attempted to be registered by the application.&amp;nbsp; 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)&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/1653445?ContentTypeID=0</link><pubDate>Tue, 09 Jun 2026 04:24:41 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1672e2c1-7f1f-42fa-99ea-ff4dd3271e52</guid><dc:creator>baosong xie</dc:creator><slash:comments>5</slash:comments><comments>https://e2e.ti.com/thread/1653445?ContentTypeID=0</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2340R5&lt;/p&gt;&lt;p&gt;SDK version: &amp;nbsp;simplelink_lowpower_f3_sdk_9_14_02_16&lt;/p&gt;
&lt;p&gt;Reference: zboss-user-guide&amp;nbsp;&lt;/p&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;Configuration file&lt;/th&gt;
&lt;th&gt;Usage&lt;/th&gt;
&lt;th&gt;Maximum number of nodes&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;zb_mem_config_min.h&lt;/td&gt;
&lt;td&gt;Simple applications and small networks.&lt;/td&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;zb_mem_config_med.h&lt;/td&gt;
&lt;td&gt;Applications without huge demands on Zigbee features,&lt;br /&gt;for example broadcast transmissions, binding and group membership entries.&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;zb_mem_config_max.h&lt;/td&gt;
&lt;td&gt;Complex applications and huge networks.&lt;/td&gt;
&lt;td&gt;128&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;A large-scale network should be capable of accommodating 128 nodes.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>RE: CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/6379331?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2026 13:11:29 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:367ca601-1a92-42d9-9766-e137b9650799</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6379331?ContentTypeID=1</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Do you have any sniffer logs or debugging stack return statuses of additional devices failing to join when the maximum 31 devices has been reached?&amp;nbsp; How does the Zigbee network behave at this point?&amp;nbsp; Are more devices allowed if ZR were introduced into the network?&amp;nbsp; Although not your target device, have you tried a CC2745R10-Q1 LaunchPad to determine if the results are similar?&amp;nbsp; Have you considered evaluating the latest F3 SDK v9.20 to determine whether the results are similar?&lt;/p&gt;
[quote userid="655090" url="~/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"]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]
&lt;p&gt;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?&lt;/p&gt;
&lt;p&gt;Zigbee R&amp;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.&amp;nbsp; They have suggested potentially fixing this by&amp;nbsp;calling zb_set_max_children(MAX_CHILDREN) in the ZC application after ZB_INIT() and before zboss_start_no_autostart().&amp;nbsp; Can you please implement this workaround and give feedback on its efficacy?&amp;nbsp; And could you also provide a debug print of gc_neighbor_table_size at runtime after stack initialization?&amp;nbsp; This would provide further evidence.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/6378552?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2026 02:34:59 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8a289110-6f5f-486b-9686-21c90273e29d</guid><dc:creator>baosong xie</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6378552?ContentTypeID=1</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://e2e.ti.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/158/pastedimage1781145202090v3.png" alt=" " /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://e2e.ti.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/158/pastedimage1781145281484v4.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Only the SYSCFG configuration file was changed, but the zb_mem_config_lprf3.h file was not modified.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/6377539?ContentTypeID=1</link><pubDate>Wed, 10 Jun 2026 13:56:01 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:407b9c20-bcc6-490c-8e90-aa8a61aa971f</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6377539?ContentTypeID=1</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;I do not think the NVS memory is the issue in your current setup.&amp;nbsp; I would like to further understand your changes to the zb_mem_config_* implementation inside of the TI Zigbee example projects.&amp;nbsp; Can you please provide your application .c file, Sysconfig, and any changes to&amp;nbsp;zb_mem_config_lprf3.h for review?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/6376709?ContentTypeID=1</link><pubDate>Wed, 10 Jun 2026 01:38:27 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c7871e10-d15e-4053-bfa0-5a4a005ec327</guid><dc:creator>baosong xie</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6376709?ContentTypeID=1</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;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.The &amp;quot;Network Maximum Children&amp;quot; parameter in syscfg is set to 128.&amp;nbsp;&amp;nbsp;I found that when the coordinator uses the default NVS value 0x1000 of the SYSCFG ,&amp;nbsp;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.&amp;nbsp; &amp;nbsp;&amp;nbsp;I know that the NV of the coordinator will store the link keys and IEEE address information of each joined node,&amp;nbsp;&amp;nbsp;So I&amp;#39;m wondering if the NVS space is what limits the network size of the coordinator?&amp;nbsp; &amp;nbsp;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2340R5: The CC2350R53 ZBOSS zigbee how to achieve a network scale of 128 nodes</title><link>https://e2e.ti.com/thread/6375779?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2026 13:23:43 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ce047500-6913-4311-8409-377ede2415c0</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6375779?ContentTypeID=1</comments><wfw:commentRss>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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi baosong,&lt;/p&gt;
&lt;p&gt;Here is additional information on the &lt;a href="https://dev.ti.com/tirex/content/simplelink_lowpower_f3_sdk_9_20_00_81/docs/third_party/zboss_r23/doxygen/html/zigbee_mem_cfg_feature_ram.html"&gt;Zigbee stack RAM usage configuration&lt;/a&gt;&lt;span&gt;.&amp;nbsp; As SimpleLink F3 SDK Zigbee projects have&amp;nbsp;&lt;/span&gt;ZB_CONFIGURABLE_MEM defined in zb_vendor_lpf3_sdk.h,&amp;nbsp;zb_mem_config_lprf3.h is referenced and uses&amp;nbsp;ZB_CONFIG_LIGHT_TRAFFIC,&amp;nbsp;ZB_CONFIG_APPLICATION_MODERATE, and&amp;nbsp;MAX_CHILDREN (from&amp;nbsp;ti_zigbee_config.h generated by SysConfig) which configure the definitions inside of the zb_mem_config_common.h file.&amp;nbsp; 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.&lt;/p&gt;
&lt;p&gt;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).&amp;nbsp; 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.&amp;nbsp; Are you using a mesh network (i.e. routers) or do you have all ZED connecting directly to the ZC?&amp;nbsp; Can you please share all changes you&amp;#39;ve applied to the baseline TI out-of-box example?&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2652R: Zigbee Range issue</title><link>https://e2e.ti.com/thread/6354064?ContentTypeID=1</link><pubDate>Thu, 21 May 2026 09:06:40 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:70464ced-5a19-4f87-8528-12b57b7ed016</guid><dc:creator>srinivas muniswami</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6354064?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi Team,&lt;br /&gt;&lt;br /&gt;Thanks, I have submitted my files for review to the following ID&amp;nbsp;&lt;span&gt;&lt;a id="" href="mailto:connectivity-24ghz-hw-review@list.ti.com"&gt;connectivity-24ghz-hw-review@list.ti.com&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;But there is no acknowledgement or response&lt;br /&gt;&lt;br /&gt;Regards&lt;br /&gt;Srinivas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC2652R: Zigbee Range issue</title><link>https://e2e.ti.com/thread/1647540?ContentTypeID=0</link><pubDate>Wed, 20 May 2026 05:25:25 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c40cd4e6-d879-4c6d-bac2-60389981deb8</guid><dc:creator>srinivas muniswami</dc:creator><slash:comments>3</slash:comments><comments>https://e2e.ti.com/thread/1647540?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2652R&lt;/p&gt;&lt;p&gt;Hi Team,&lt;br /&gt;&lt;br /&gt;Continuing the discussion, As suggested we have tested the results. Kinldy find the attached test results in the document&lt;br /&gt;&lt;br /&gt;&lt;a href="https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/Home_5F00_automation_5F00_Range_5F00_test_5F00_report.pdf" target="_blank" rel="noopener" data-temp-id="Home_automation_Range_test_report.pdf-969350"&gt;Home_automation_Range_test_report.pdf&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kinldy check and share us your feedback to overcome the issues&lt;/p&gt;
&lt;p&gt;Regards&lt;br /&gt;Srinivas&lt;/p&gt;</description></item><item><title>RE: CC2652R: Zigbee Range issue</title><link>https://e2e.ti.com/thread/6352678?ContentTypeID=1</link><pubDate>Wed, 20 May 2026 14:08:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:44c0bc93-a1f5-4d6e-adc9-559ae55aaf00</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6352678?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi srinivas,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;You would need to submit your schematic and layout design files to&amp;nbsp;&lt;/span&gt;&lt;a id="" href="https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS"&gt;SIMPLELINK-2-4GHZ-DESIGN-REVIEWS&lt;/a&gt;&lt;span&gt;&amp;nbsp;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.&amp;nbsp; Unfortunately this means that the PCB antenna design could be suboptimal which is resulting in poorer performance than expected.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2652R: Zigbee Range issue</title><link>https://e2e.ti.com/thread/6352496?ContentTypeID=1</link><pubDate>Wed, 20 May 2026 11:43:37 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:24872d93-503c-49df-9dca-c8c5f2f6f32e</guid><dc:creator>ZC</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6352496?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1647540/cc2652r-zigbee-range-issue/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi Srinivas,&lt;/p&gt;
&lt;p&gt;I took a quick look at your PCB layout in the previous thread you linked.&lt;/p&gt;
&lt;p&gt;My initial impression is that the TI reference design layout hasn&amp;#39;t been as closely followed as we would recommend. I would strongly advise submitting your design files for review using&amp;nbsp;&lt;strong&gt;2.4 GHz Design Review Submission:&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a class="external-link" href="https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS" rel="nofollow"&gt;https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can then get more targeted feedback and implement the changes. I&amp;#39;m not sure if that has been done yet, but should be as the first step if it hasn&amp;#39;t.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Regards,&lt;/p&gt;
&lt;p&gt;Zack&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2538-CC2592EMK: Electronic Door Lock - ZigBee Development Project</title><link>https://e2e.ti.com/thread/6350557?ContentTypeID=1</link><pubDate>Tue, 19 May 2026 12:31:10 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6c56e81b-39ad-4763-8c21-5957540247f8</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6350557?ContentTypeID=1</comments><wfw:commentRss>https://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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi Prince,&lt;/p&gt;
&lt;p&gt;You should certainly be evaluating the CC23XX / CC27XX device family using the &lt;a href="https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F3-SDK/9.20.00.81"&gt;SimpleLink Low Power F3 SDK&lt;/a&gt;.&amp;nbsp; 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.&amp;nbsp; You can reference the Datasheet and Technical Reference Manual (TRM) of each device for more information.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.ti.com/product/CC2340R5"&gt;CC2340R5&lt;/a&gt;, &lt;a href="https://www.ti.com/tool/LP-EM-CC2340R5"&gt;LP-EM-CC2340R5&lt;/a&gt;&lt;br /&gt;&lt;a href="https://www.ti.com/product/CC2755R10"&gt;CC2755R10&lt;/a&gt;,&amp;nbsp;&lt;a id="" href="https://www.ti.com/tool/LP-EM-CC2745R10-Q1"&gt;LP-EM-CC2745R10-Q1&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="https://www.ti.com/product/CC2755P10"&gt;CC2755P10&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://dev.ti.com/tirex/explore/node?isTheia=false&amp;amp;node=A__AGj9KtA6tkgMIEwNI7zxZA__com.ti.SIMPLELINK_LOWPOWER_F3_SDK__58mgN04__LATEST"&gt;Zigbee User&amp;#39;s Guide&lt;/a&gt;&lt;br /&gt;&lt;a href="https://dev.ti.com/tirex/explore/node?isTheia=false&amp;amp;node=A__AI3LCfHTOpMIB.0xf4CRXg__SIMPLELINK-ACADEMY-CC23XX__gsUPh5j__LATEST"&gt;Zigbee SimpleLink Academy Labs&lt;/a&gt;&lt;br /&gt;&lt;a href="https://dev.ti.com/tirex/content/simplelink_lowpower_f3_sdk_9_20_00_81/docs/third_party/zboss_r23/doxygen/html/group__ha__door__lock.html"&gt;Zigbee DoorLock ZCL APIs&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://csa-iot.org/csa_product/ti-zigbee-core/"&gt;CC2340R5 CSA compliancy&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="https://csa-iot.org/csa_product/ti-zigbee-core-2/"&gt;CC27xx CSA compliancy&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC2538-CC2592EMK: Electronic Door Lock - ZigBee Development Project</title><link>https://e2e.ti.com/thread/1647247?ContentTypeID=0</link><pubDate>Tue, 19 May 2026 09:53:50 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:33d1a106-d1b5-47fd-94b0-e50ccb040814</guid><dc:creator>Prince Tero</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1647247?ContentTypeID=0</comments><wfw:commentRss>https://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/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2538-CC2592EMK&lt;/p&gt;&lt;div data-olk-copy-source="MessageBody"&gt;Hi TI Team,&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;I am reaching out on behalf of our engineering team as we are currently in the process of integrating a Zigbee antenna/module into our access control door lock system. We are exploring suitable Zigbee chip or module solutions and would like to request your support and proposal.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Below are our initial requirements:&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;A Zigbee chip or module compatible with integration into an electronic door lock system&lt;/div&gt;
&lt;ul style="list-style-type:disc;"&gt;
&lt;li&gt;
&lt;div&gt;Latest available Zigbee version and supported protocols&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Electrical and mechanical specifications, including interface, pinout, power consumption, and antenna options&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Security features, OTA capability, and certification compliance&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Recommended development tools, SDKs, and documentation&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Estimated pricing for samples and bulk orders&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Lead time for samples and mass production&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;Technical support availability during development and coordination with our factory engineering team&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;We would appreciate it if you could provide your recommended solution along with the full technical specifications, datasheets, and commercial details. Our team is ready to coordinate further to ensure compatibility with our existing lock hardware.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Thank you in advance for your assistance. We look forward to your proposal and to the possibility of working together.&lt;/div&gt;</description></item><item><title>CC2755R10: Radio frequency plan</title><link>https://e2e.ti.com/thread/1641416?ContentTypeID=0</link><pubDate>Wed, 29 Apr 2026 08:56:05 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f85947f4-d726-4495-af0d-8126989335e1</guid><dc:creator>Flemming Noerskov Larsen</dc:creator><slash:comments>2</slash:comments><comments>https://e2e.ti.com/thread/1641416?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1641416/cc2755r10-radio-frequency-plan/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2755R10&lt;/p&gt;&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Are currently running a FCC approval, got a question on the radio frequency plan LO osc, IF freq. I guess frequencies are about the same as stipulated in &amp;quot;How to certify your Bluetooth Product&amp;quot;. Please elaborate on this.&lt;/p&gt;
&lt;p&gt;B.R.&lt;/p&gt;
&lt;p&gt;Flemming Larsen&lt;/p&gt;</description></item><item><title>RE: CC2755R10: Radio frequency plan</title><link>https://e2e.ti.com/thread/6329345?ContentTypeID=1</link><pubDate>Thu, 30 Apr 2026 06:53:05 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0c432ca0-2c27-4f80-8293-10d7a8ca5231</guid><dc:creator>Flemming Noerskov Larsen</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6329345?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1641416/cc2755r10-radio-frequency-plan/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello Alex&lt;/p&gt;
&lt;p&gt;Reading the&amp;nbsp;&lt;a href="https://www.ti.com/lit/an/swra601n/swra601n.pdf?ts=1777392577670"&gt;How to Certify Your Bluetooth Product (Rev. N)&lt;/a&gt;&amp;nbsp;one more time I see the CC27XX products are covered&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Flemming&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2755R10: Radio frequency plan</title><link>https://e2e.ti.com/thread/6328708?ContentTypeID=1</link><pubDate>Wed, 29 Apr 2026 20:14:37 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5b962c3b-cb53-4e62-b048-079793167869</guid><dc:creator>Alex Fager</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6328708?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1641416/cc2755r10-radio-frequency-plan/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hello Flemming Larsen,&lt;/p&gt;
&lt;p&gt;Can you possibly provide the specific question or field for more context?&amp;nbsp;The&amp;nbsp;&lt;span&gt;How to certify your Bluetooth Product should be a good document to reference for FCC certification.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks,&lt;br /&gt;Alex F&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2755R10: SW package with aliro standards</title><link>https://e2e.ti.com/thread/6326338?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2026 12:36:04 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:576b1dd9-43b1-4122-84f0-1002a841fb1d</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6326338?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1640899/cc2755r10-sw-package-with-aliro-standards/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Hi robin,&lt;/p&gt;
&lt;p&gt;There are currently no plans to support Aliro, however I have informed the Systems Team of this request so that it may be considered for the software roadmap.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC2755R10: SW package with aliro standards</title><link>https://e2e.ti.com/thread/1640899?ContentTypeID=0</link><pubDate>Tue, 28 Apr 2026 04:28:49 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:655ce4b3-f823-4d91-9161-434c0b9e06d9</guid><dc:creator>robin Moon</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/1640899?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1640899/cc2755r10-sw-package-with-aliro-standards/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2755R10&lt;/p&gt;&lt;p&gt;Hi experts,&lt;/p&gt;
&lt;p&gt;My customer is looking for a device that meets the Aliro(CSA Standard).&lt;/p&gt;
&lt;p&gt;&lt;a href="https://csa-iot.org/all-solutions/aliro/"&gt;https://csa-iot.org/all-solutions/aliro/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;do you have any plans to provide aliro standard library among cc2755 or cc2340R5?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;</description></item><item><title>CC2530: After interference on the CC2530 P0_2/P1_0 pins, the power consumption becomes extremely high.</title><link>https://e2e.ti.com/thread/1639057?ContentTypeID=0</link><pubDate>Wed, 22 Apr 2026 03:38:54 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5753c3e3-7376-4c06-9385-d68ad88693b6</guid><dc:creator>lu zheng</dc:creator><slash:comments>9</slash:comments><comments>https://e2e.ti.com/thread/1639057?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639057/cc2530-after-interference-on-the-cc2530-p0_2-p1_0-pins-the-power-consumption-becomes-extremely-high/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2530&lt;/p&gt;&lt;p&gt;Hello!&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; We encountered the same configuration in a project where both P0_2 and P0_3 are configured as output low. Neither of these IOs is connected to any external device. When P0_2 is touched with tweezers, the power consumption increases dramatically. At this point, the measured voltage on this pin is around 0.63V. Touching P0_3 in the same way does not cause this issue. When this problem occurs, it can only be restored to normal by power cycling. Could you please help analyze what might be causing this and how to resolve it? We look forward to your reply.&lt;/p&gt;
&lt;p&gt;Thank you!&amp;nbsp;&lt;/p&gt;</description></item><item><title>RE: CC2530: After interference on the CC2530 P0_2/P1_0 pins, the power consumption becomes extremely high.</title><link>https://e2e.ti.com/thread/6322697?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 13:23:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d3560a44-9fb1-4238-9302-0b506ce20117</guid><dc:creator>lu zheng</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6322697?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639057/cc2530-after-interference-on-the-cc2530-p0_2-p1_0-pins-the-power-consumption-becomes-extremely-high/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span&gt;Thank you for your help. Unfortunately, we do not currently have a TI official evaluation board (EVM) on hand, so we are unable to perform this test. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2530: After interference on the CC2530 P0_2/P1_0 pins, the power consumption becomes extremely high.</title><link>https://e2e.ti.com/thread/6322664?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 13:02:40 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d85b0188-a124-4915-899d-dd366be455f6</guid><dc:creator>Ryan Brown1</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6322664?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639057/cc2530-after-interference-on-the-cc2530-p0_2-p1_0-pins-the-power-consumption-becomes-extremely-high/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;You can submit your design to&amp;nbsp;&lt;a id="" href="https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS"&gt;SIMPLELINK-2-4GHZ-DESIGN-REVIEWS&lt;/a&gt;&amp;nbsp;for further review.&amp;nbsp; Have you replicated the issue with a TI EVM?&amp;nbsp; I have no concerns with implementing a 10 nF capacitor on an unused IO if it resolves the issue for your system.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: CC2530: After interference on the CC2530 P0_2/P1_0 pins, the power consumption becomes extremely high.</title><link>https://e2e.ti.com/thread/6322088?ContentTypeID=1</link><pubDate>Fri, 24 Apr 2026 05:48:21 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d4898c89-998f-4f4b-b515-5f4c75375452</guid><dc:creator>lu zheng</dc:creator><slash:comments>1</slash:comments><comments>https://e2e.ti.com/thread/6322088?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639057/cc2530-after-interference-on-the-cc2530-p0_2-p1_0-pins-the-power-consumption-becomes-extremely-high/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;span&gt;Do you have any better solutions to resolve this issue?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt; Thanks&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>CC2652PSIP: Maximum total internal capacitance for ATEX certification</title><link>https://e2e.ti.com/thread/1639071?ContentTypeID=0</link><pubDate>Wed, 22 Apr 2026 04:16:39 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:48741d16-742e-4926-9241-a43145a1402c</guid><dc:creator>robin Moon</dc:creator><slash:comments>2</slash:comments><comments>https://e2e.ti.com/thread/1639071?ContentTypeID=0</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639071/cc2652psip-maximum-total-internal-capacitance-for-atex-certification/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;&lt;b&gt;Part Number:&lt;/b&gt; CC2652PSIP&lt;/p&gt;&lt;p&gt;Hi experts,&lt;/p&gt;
&lt;p&gt;My customer requested Maximum total internal capacitance of CC2652PSIP for ATEX certification.&lt;/p&gt;
&lt;p&gt;Also, could you please provide us with a guide document for ATEX certification?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description></item><item><title>RE: CC2652PSIP: Maximum total internal capacitance for ATEX certification</title><link>https://e2e.ti.com/thread/6321713?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 22:57:26 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3b65d8c8-460d-4720-835a-8e6460d77140</guid><dc:creator>robin Moon</dc:creator><slash:comments>0</slash:comments><comments>https://e2e.ti.com/thread/6321713?ContentTypeID=1</comments><wfw:commentRss>https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1639071/cc2652psip-maximum-total-internal-capacitance-for-atex-certification/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;hi FI&lt;/p&gt;
&lt;p&gt;&lt;span&gt;They need the value of ATEX parameter as below for ATEX certification.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://e2e.ti.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/158/ATEX-parameter.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Please let me know the value for each parameter of CC2652PSIP.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;thanks.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>