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/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6481440Fri, 11 Sep 2026 20:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5f88a4d5-5c0d-42c0-82a6-2edc920e7c81Alex FagerHello jun cao, Thanks for confirming with the pictures, on my end after compiling a ZNP example and flashing it to a CC2674P10 device the following is what I see in the PuTTY window: I also tested the z-tool to see if it can find and control the device and it unfortunately did not. From what I can conclude here the ZNP project for the CC2674P10 does not currently work, at least when attempting to open the project with z-tool (what was recommended in the readme). Though it&#39;s interesting that zigbee2mqtt can seem to work with it from what you report. We currently do not recommend developers to develop on (or go to production) with the F2 devices (such as the CC2674P10) and instead recommend the F3 (CC23, CC27) devices. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679992/cc2652psip-having-antenna-range-issues-with-custom-cc2652psip-board/6481224Fri, 11 Sep 2026 16:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c352e7cc-a16e-4c26-b653-6e94a3cca41aKatherine OgreanHi, From the information you have provided I think the issue might be a manufacturing / assembly issue. This could be due to the antenna or the assembly of the RF path. I suggest looking at the 2.4-GHz Inverted F Antenna (Rev. D) application note to ensure the implementation of the inverted F antenna is correct. Additionally, make sure all layout recommendations are followed in section 10 of CC2652PSIP SimpleLink ™ Multiprotocol 2.4-GHz Wireless System-in-Package With Integrated Power Amplifier datasheet (Rev. B) . I would also recommend testing the custom board Tx to see if you are seeing the same performance degradation as in Rx. Best, Katyhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-error/6480662Fri, 11 Sep 2026 08:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fac9598f-3031-4247-9814-d8b5ea7803a9Ohata ReijiHi Alex, Thank you supporting.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1677452/cc2755p10-cc2755p10-availability-roadmap-of-zboss-ncp-sncp-device-side-build-for-cc23xx-cc27xx/6480520Fri, 11 Sep 2026 06:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:463aa738-c918-4077-a2a2-514ebb238488Levent SagirogluHi Ging, hi Jan, Thank you both — understood on NCP not being supported today, and I appreciate you taking this to R&amp;D. We will wait for your update next week. One note in case it helps them scope the answer: of the questions in my original post, the one that actually unblocks our design is item 5 — whether a customer-implemented serial coprocessor on top of the supported SoC-mode ZC role is a viable and supportable approach on CC2755P10. Thanks, Leventhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6480351Fri, 11 Sep 2026 02:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ec2a345f-c317-4468-9987-f9a76415e26cjun caoHi Alex Fager : I have configured the settings based on the screenshot you provided, as shown below: However, zigbee2mqtt is reporting the same error as before, as shown below: [quote userid=&quot;567427&quot; url=&quot;~/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6479918&quot;]As a separate question do you plan to go to production with the CC2674P10 with zstack? [/quote] Yes, but during our testing, we found that when the CC2674P10 is used as the coordinator, only 40 devices can be added to the Zigbee network. This number is too low, so we submitted the issue to E2E to see if a solution could be provided.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6480307Fri, 11 Sep 2026 01:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b5e0691c-b527-43b3-9dd9-7092c961163bjun caoHi Alex Fager : 1. Where should the code be added—in the OTBR app or in OT-TI? 2. What kind of code should be added? I look forward to your reply.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6480110Thu, 10 Sep 2026 21:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1f7759fd-83ca-4c4a-a009-3daffd5e0fafAlex FagerHello jun cao, [quote userid=&quot;716594&quot; url=&quot;~/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6478929&quot;]is it a known bug or something else?[/quote] I do not see any bug referencing this issue in the github. [quote userid=&quot;716594&quot; url=&quot;~/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6478929&quot;]How can I check if &quot;d679ce2673019647&quot; is in the RCPs table?[/quote] We may need to add some direct logging code to the actual software to export the current RCP table. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1677452/cc2755p10-cc2755p10-availability-roadmap-of-zboss-ncp-sncp-device-side-build-for-cc23xx-cc27xx/6480087Thu, 10 Sep 2026 20:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2e14d3b4-e173-4a45-8d32-40c3a5f2f4d6Ging GonzalezHi Levent, Thank you for looking into this and reaching out! We currently do not support NCP and I cannot commit to a timeline or target SDK release, but let me reach out to our R&amp;D teams and get more details for your questions. Give me until next week to get back to you. Thanks! Regards, Ginghttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-error/6479973Thu, 10 Sep 2026 18:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3c01b434-2182-487a-9963-7695076ee063Alex FagerHello Ohata Reiji, Going off of the diagram below the signals for Priority and Grant seem to be working correctly, and the Zigbee device should be allowed to perform the TX/RX operations so the code setup seems ok. I am not aware of how exactly the setup on the CC33 side would work, as you want the CC33 to also do BLE I am not sure how its own Priority/Grants would work. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6479918Thu, 10 Sep 2026 18:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c1c05013-ab0d-41c0-b78c-fb15db91f622Alex FagerHello jun cao, To confirm your setup is similar to the below pictures: As a separate question do you plan to go to production with the CC2674P10 with zstack? Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-error/6479259Thu, 10 Sep 2026 10:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:73b9953a-16b9-4cab-b891-a334681620acOhata ReijiI found that COEX_PRIORITY becomes HIGH and COEX_GRANT becomes LOW when cc2755r10 sends ACK. Therefore, I think 3 wire-PTA works well. Could you tell me below code is correct or not. rcl_stub_dmm.c DMM_WEAK_FUNC RCL_CommandStatus OVRDE_RCL_Command_submit(RCL_Handle h, RCL_Command_Handle c) { ((RCL_CmdIeeeRxTx*)c)-&gt;coexControl.grantEnable = 1; ((RCL_CmdIeeeRxTx*)c)-&gt;coexControl.requestPriorityEnable = 1; return RCL_Command_submit(h, c); }https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6478929Thu, 10 Sep 2026 05:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f58b3a41-83c1-4e34-b8f2-908298bc3b33jun caoHi Alex Fager : I could try using the latest OT-TI (tag: thread-v1.4-ti-2.1), but I would still like to know why this error occurs with OT-TI (tag: thread-ti-v1.3-1.0)—is it a known bug or something else? How can I check if &quot;d679ce2673019647&quot; is in the RCPs table?https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6478803Thu, 10 Sep 2026 03:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7fdad0f1-9efd-45fd-a702-5edf67647965jun caoHi Alex Fager : I have tried setting HEAPMGR_SIZE to 8192 or 16384, but the zigbee2mqtt error remains the same. The HEAPMGR_SIZE configuration is as follows: --stack_size=0x600 /* C stack is also used for ISR stack */ HEAPSIZE = 0x4000; /* Size of heap buffer used by HeapMem */ /* Retain interrupt vector table variable */ --retain=g_pfnVectors /* Allow main() to take args */ --args 0x8 /* Suppress warnings and errors: */ /* - 10063: Warning about entry point not being _c_int00 */ /* - 16011, 16012: 8-byte alignment errors. Observed when linking in object */ /* files compiled using Keil (ARM compiler) */ --diag_suppress=10063,16011,16012 /* The following command line options are set as part of the CCS project. */ /* If you are building using the command line, or for some reason want to */ /* define them here, you can uncomment and modify these lines as needed. */ /* If you are using CCS for building, it is probably better to make any such */ /* modifications in your CCS project and leave this file alone. */ /* */ /* --heap_size=0 */ // --stack_size=1024 --stack_size=16384 /* --library=rtsv7M3_T_le_eabi.lib */ // #define NVOCMP_NVPAGES 5 #define NVOCMP_NVPAGES 0xA /* The starting address of the application. Normally the interrupt vectors */ /* must be located at the beginning of the application. */ #define FLASH_PAGE_SIZE 0x800 /* 2 KB per TRM */ #define FLASH_BASE 0x0 #define FLASH_SIZE (0x100000 - (NVOCMP_NVPAGES * FLASH_PAGE_SIZE)) #define FLASH_NV_BASE (0x100000 - (NVOCMP_NVPAGES * FLASH_PAGE_SIZE)) #define FLASH_NV_SIZE (NVOCMP_NVPAGES * FLASH_PAGE_SIZE) #define RAM_BASE 0x20000000 #define RAM_SIZE 0x40000 #define GPRAM_BASE 0x11000000 #define GPRAM_SIZE 0x2000 #define CCFG_BASE 0x50000000 #define CCFG_SIZE 0x800 Is there an issue with this configuration?https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-error/6478685Thu, 10 Sep 2026 01:16:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b4b5a866-6224-4084-933b-fae39eac3371Ohata ReijiHi Alex, Our developing device use CC2755R10 as a Zigbee module, and CC3301 as a BLE/WiFi module. This architecture cannot change. I want to know how to solve this problem with this architecture.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-error/6478488Wed, 09 Sep 2026 21:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5d70dcc0-d4dd-4c59-b1f7-ff7822b3ce86Alex FagerHello, Coex here should use the CC27 with BLE/Zigbee and have the CC3301 chip only do wi-fi as the CC3301 would be the PTA master. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6478441Wed, 09 Sep 2026 20:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f5960ab0-fe04-4729-b9e2-759c735ed225Alex FagerHello jun cao, Can you possibly try the latest ot-ti (1.4) if possible, and report back if you have the same issue. Given the log above the RCP seems to be crashing and then recovering but not able to continue (likely via watchdog). Is the &quot;d679ce2673019647&quot; within the RCPs table when it requests its removal? Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6478044Wed, 09 Sep 2026 15:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6ec06cbf-9196-42a0-bb30-43f074bf04e0Alex FagerHello jun cao, Since we are trying to set the device max to 200 devices, lets try at least 8192 or 16384 bytes for the HEAPMGR_SIZE. Current thought is that during the Network Information base it runs out of space in the heap. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680685/cc2755r10-coex_req-errorWed, 09 Sep 2026 08:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b27dc434-13b0-4d8c-9ff7-cbe9a7b6d40cOhata ReijiPart Number: CC2755R10 Other Parts Discussed in Thread: CC3301 , Hi, Our developing device uses CC2755R10 with CC3301 to use Zigbee and BLE/WiFi. Therefore I edited syscfg like below. However, COEX_REQ and COEX_PRIORITY are not work. When it receives some packets, these 2 line are still Low. To solve this problem, I edited rcl_stub_dmm.c like below. DMM_WEAK_FUNC RCL_CommandStatus OVRDE_RCL_Command_submit(RCL_Handle h, RCL_Command_Handle c) { ((RCL_CmdIeeeRxTx*)c)-&gt;coexControl.grantEnable = 1; ((RCL_CmdIeeeRxTx*)c)-&gt;coexControl.requestPriorityEnable = 1; return RCL_Command_submit(h, c); } By this change, COEX_REQ is become HIGH and COEX_PRIORITY is still Low when it receives some packets. [Question] 1. Is this change correct? If no, could you tell me how to fix it? 2. Does COEX_PRIORITY not become High, when receive?CC2755R10tabletsCC3301https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1679526/cc2674p10-cc2674p10-openthread-rcp-wait-for-response-timeout/6477125Wed, 09 Sep 2026 02:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5e56c7e8-05e5-43f0-8b75-fde45b6a33a5jun caoHi Alex Fager : This is my log file. e2e.ti.com/.../core_5F00_openthread_5F00_border_5F00_router_5F00_2026_2D00_08_2D00_28T12_2D00_07_2D00_48.884Z.log In the ot-ti project, I manually set the baud rate to 460800. I also set the OTBR app&#39;s baud rate to 460800. The logs indicate that data communication is taking place between the OTBR app and the OpenThread RCP; the error only occurs at the very end: 00:01:10.851 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:3, cmd:PROP_VALUE_REMOVE, key:MAC_SRC_MATCH_EXTENDED_ADDRESSES, extaddr:d679ce2673019647 00:01:10.851 [D] P-RadioSpinel-: Wait response: tid=3 key=4869 00:01:12.854 [W] P-RadioSpinel-: Wait for response timeout 00:01:12.864 [W] P-RadioSpinel-: RCP failure detected 00:01:12.871 [W] P-RadioSpinel-: Trying to recover (1/2) 00:01:12.871 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET 00:01:12.871 [D] P-SpinelDrive-: Waiting response: key=0 00:01:14.874 [W] P-SpinelDrive-: Wait for response timeout 00:01:14.874 [I] P-SpinelDrive-: co-processor self reset successfully 00:01:14.874 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_SET, key:PHY_ENABLED, enabled:1 00:01:14.874 [D] P-RadioSpinel-: Wait response: tid=1 key=32 00:01:16.877 [W] P-RadioSpinel-: Wait for response timeout 00:01:16.888 [W] P-RadioSpinel-: RCP failure detected 00:01:16.896 [W] P-RadioSpinel-: Trying to recover (2/2) 00:01:16.896 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET 00:01:16.896 [D] P-SpinelDrive-: Waiting response: key=0 00:01:18.897 [W] P-SpinelDrive-: Wait for response timeout 00:01:18.897 [I] P-SpinelDrive-: co-processor self reset successfully 00:01:18.897 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_SET, key:PHY_ENABLED, enabled:1 00:01:18.897 [D] P-RadioSpinel-: Wait response: tid=1 key=32 00:01:20.898 [W] P-RadioSpinel-: Wait for response timeout 00:01:20.909 [W] P-RadioSpinel-: RCP failure detected 00:01:20.915 [C] P-RadioSpinel-: Too many rcp failures, exiting I am unable to determine the cause of this error.https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1680390/cc2674p10-cc2674p10-zdsecmgr_tc_device_max-upper-limit/6477109Wed, 09 Sep 2026 02:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:af8e979d-3147-48aa-9017-e9f78331bae5jun caoHi Alex Fager : Thank you for you reply. I can provide the logs from the zigbee2mqtt startup failure, as follows: Starting Zigbee2MQTT without watchdog. [2026-09-09 10:16:32] info: z2m: Logging to console, file (filename: log.log) [2026-09-09 10:16:32] info: z2m: External JS (converters/extensions) is disabled [2026-09-09 10:16:32] info: z2m: Starting Zigbee2MQTT version 2.12.1 (commit #aa909a8a) [2026-09-09 10:16:32] info: z2m: Starting zigbee-herdsman (10.6.1) [2026-09-09 10:16:33] info: zh:adapter:discovery: Matched adapter: {&quot;path&quot;:&quot;/dev/ttyUSB1&quot;,&quot;manufacturer&quot;:&quot;SONOFF&quot;,&quot;serialNumber&quot;:&quot;d0c758260312f0118fd40314773d9da9&quot;,&quot;pnpId&quot;:&quot;usb-SONOFF_SONOFF_Dongle_Plus_CC2674P10_d0c758260312f0118fd40314773d9da9-if00-port0&quot;,&quot;vendorId&quot;:&quot;10c4&quot;,&quot;productId&quot;:&quot;ea60&quot;} =&gt; zstack: 4 [2026-09-09 10:16:33] info: zh:zstack:znp: Opening SerialPort with {&quot;path&quot;:&quot;/dev/ttyUSB1&quot;,&quot;baudRate&quot;:115200,&quot;rtscts&quot;:false,&quot;autoOpen&quot;:false} [2026-09-09 10:16:33] info: zh:zstack:znp: Serialport opened [2026-09-09 10:17:07] error: z2m: Error while starting zigbee-herdsman [2026-09-09 10:17:07] error: z2m: Failed to start zigbee-herdsman [2026-09-09 10:17:07] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2026-09-09 10:17:07] error: z2m: Exiting... [2026-09-09 10:17:07] error: z2m: Error: network commissioning failed - timed out waiting for nib to settle Note: When I change ZDSECMGR_TC_DEVICE_MAX to 100, zigbee2mqtt does not produce this error log and starts up normally. I perform a &quot;rebuild&quot; operation every time I compile the project. Therefore, the project is definitely cleaned first and then built.