https://e2echina.ti.com/support/wireless-connectivity/other-wireless/zh-CNTelligent Community 13https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3868642Thu, 21 May 2026 20:05:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:c3dcff6e-812c-45de-8087-acfa319048c8Tarek D你好， 您如何验证有效载荷是否完整？ 此致， 塔雷克·DECTEhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead/3868180Wed, 20 May 2026 08:26:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:a09c576b-245a-43c1-a42f-4d8d35fcdfccQingtian Yang是否可以这样理解，在 SimpleLink LowPower F3 SDK 当中还未有完善的可用的DMP应用？https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3868179Wed, 20 May 2026 08:24:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:822bc9b5-94c2-418d-b001-49261456aabcQingtian Yang您好： 我已经能够成功发出了ble的广播包了，但是我的sniffer提示我：crc错误，但payload完整无误。但是我找不到在sysconfig当中设置他的地方，这些配置都被隐藏了吗。另外我使用的simplelink-lowpower-f3-sdk 8.10，我使用类似的代码在SDK 9.20上面是正确的，我找不到调试的方向，能否提供关于sysconfig配置Generic BLE的更多信息https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead/3867982Mon, 18 May 2026 19:01:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:327bc5a2-13fc-4c20-83b9-d012b605be58Alex ***你好， [quote userid="675191" url="~/support/wireless-connectivity/other-wireless-group/other-wireless---internal/f/other-wireless---internal-forum/1646716/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead"] 基本控制： 我只需要执行一些基本操作，例如更改频率/信道以及发送/接收原始数据包，同时保持基本的 BLE 连接以进行配置。[/quote] 在 BLE 协议栈运行时，或许可以使用简单/简短的 proprf 命令；目前还没有相关的示例或支持；但是，如果您要自行实现，则需要非常小心地发送 proprf 命令，因为如果 RCL/无线电在 BLE 需要使用时处于活动状态，则会导致错误。 [quote userid="675191" url="~/support/wireless-connectivity/other-wireless-group/other-wireless---internal/f/other-wireless---internal-forum/1646716/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead"]请问如何在 CC2340 上使用 DMM 实现这种“裸机式”多协议切换？或者，是否有推荐的架构可以在不增加完整协议栈 RAM 开销的情况下实现低级射频并发？[/quote] 我之前修改过 MCUboot，使其使用镜像插槽来保存不同的项目，并在它们之间切换，但是这样无法与 BLE 保持活动连接，尽管一旦 BLE 项目重新启动并使用保存的设置，它就可以恢复。 谢谢， 亚历克斯·FECTEhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3866802Fri, 15 May 2026 14:48:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:45e1f60b-5562-4cf8-84d4-a732333e961bRyan Brown1你好， 您应该查阅 RCL API 指南 中的 BLE 命令处理程序 （例如 广播命令处理程序 ）和 BLE5 文件参考 。请注意，这需要使用自定义的 ti_radio_config.c/h 文件，因为 SysConfig 目前不支持自定义使用这些 RCL 命令。本质上，rfPacketTx 使用 BLE PHY，但并未公开所有 RCL 命令。您需要进一步研究文档，并尝试调整项目配置及其广播数据包结构，才能获得预期的输出。 问候， 瑞安ECTEhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead/3865942Fri, 15 May 2026 03:54:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:17668124-afee-4bd0-b31b-758953121f49AliceHello, We have received your post and the investigation will take some time. Thanks for your patience.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overheadFri, 15 May 2026 02:13:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:d9ae8855-5d6f-45b9-bb21-e8037a7c4690Qingtian YangPart Number: CC2340R5 Hello TI , I am excited to see the DMM (Dynamic Multi-protocol Manager) solution implemented in the latest SimpleLink LowPower F3 SDK (v9.20.00.81) . I am currently working with the CC2340 series for an IoT project. Currently, I do not see any ready-to-use DMM examples specifically for the CC2340. Given this lack of reference, I am considering the following approach to implement a lightweight multi-protocol solution that fits within the 36KB/64KB RAM limit My specific requirements and pain points: Lightweight Coexistence: I do not necessarily need full-stack features (like a complete Zigbee mesh or high-level BLE profiles). My goal is to achieve basic packet transceiver (RX/TX) functionality across different protocols. Protocol Switching: Is it feasible to use DMM on CC2340 to switch between BLE (Low Level) , 802.15.4 (MAC layer only) , and Proprietary 2.4G (RF Driver/RAIL level) ? Basic Control: I only need to perform basic operations like changing frequencies/channels and sending/receiving raw data packets while maintaining a basic BLE connection for configuration. Demo Availability: Are there any "Lightweight DMM" or "DMM + RF Driver" demos available for the CC2340? Could you please provide guidance on how to implement such a "bare-metal style" multi-protocol switching using DMM on the CC2340? Or is there a recommended architecture for achieving low-level RF concurrency without the RAM overhead of full-featured stacks? Looking forward to your expert advice. Best regards!CC2340R5https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3865359Thu, 14 May 2026 02:30:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:86657ebd-3468-4127-8df6-fbeb3ed0e34aQingtian Yangstatic void ble_build_adv_pdu(void) { // --- PDU Header --- ble_pdu_raw[0] = 0x42; // ADV_NONCONN_IND (0x02) | TxAdd=1 (0x40) ble_pdu_raw[1] = 15; // Length: 6 (AdvA) + 3 (Flags) + 6 (Name) = 15 // --- AdvA: Random Static Address CC:66:55:44:33:22 (LSByte first) --- ble_pdu_raw[2] = 0x22; ble_pdu_raw[3] = 0x33; ble_pdu_raw[4] = 0x44; ble_pdu_raw[5] = 0x55; ble_pdu_raw[6] = 0x66; ble_pdu_raw[7] = 0xCC; // MSByte: bits 7:6 = '11' (Random Static).You can edit any byte of address except this bits 7:6! // --- AD Structure 1: Flags --- ble_pdu_raw[8] = 0x02; // AD Length ble_pdu_raw[9] = 0x01; // AD Type: Flags ble_pdu_raw[10] = 0x06; // LE General Discoverable | BR/EDR Not Supported // --- AD Structure 2: Complete Local Name "FG22" --- ble_pdu_raw[11] = 0x05; // AD Length ble_pdu_raw[12] = 0x09; // AD Type: Complete Local Name ble_pdu_raw[13] = '2'; ble_pdu_raw[14] = '3'; ble_pdu_raw[15] = '4'; ble_pdu_raw[16] = '0'; memcpy(ble_pdu_send+1,ble_pdu_raw,17); ble_pdu_send[0]=17; } /***** Callback Functions *****/ void defaultCallback(RCL_Command *cmd, LRF_Events lrfEvents, RCL_Events rclEvents) { if (rclEvents.lastCmdDone) { gCmdDone += 1; GPIO_toggle(CONFIG_GPIO_GLED); } } /***** Function definitions *****/ void *mainThread(void *arg0) { /* Initialize and open RCL */ RCL_init(); RCL_Handle rclHandle = RCL_open(&rclClient, &LRF_config); /* Set RF frequency */ rclPacketTxCmdGenericTx.rfFrequency = FREQUENCY; /* Start command as soon as possible */ rclPacketTxCmdGenericTx.common.scheduling = RCL_Schedule_Now; rclPacketTxCmdGenericTx.common.status = RCL_CommandStatus_Idle; rclPacketTxCmdGenericTx.config.fsOff = FS_OFF; // Turn off FS /* Callback triggers on last command done */ rclPacketTxCmdGenericTx.common.runtime.callback = defaultCallback; rclPacketTxCmdGenericTx.common.runtime.rclCallbackMask.value = RCL_EventLastCmdDone.value; /* Set RCL TX buffer packet to be packet buffer */ RCL_Buffer_TxBuffer *txPacket = (RCL_Buffer_TxBuffer *)&packet; GPIO_setConfig(CONFIG_GPIO_GLED, GPIO_CFG_OUT_STD | GPIO_CFG_OUT_LOW); GPIO_write(CONFIG_GPIO_GLED, CONFIG_GPIO_LED_OFF); ble_build_adv_pdu(); while(1) { /* Create packet with random payload */ uint8_t *txData; txData = RCL_TxBuffer_init(txPacket, NUM_PAD_BYTES, HDR_LEN, MAX_LENGTH); /* Zero out data in header before the length field */ // for (int s = 0; s < LEN_INDEX; s++) // { // txData[s] = 0U; // } /* Set the packet length */ // txData[LEN_INDEX] = ble_pdu_send[0]; memcpy(txData, ble_pdu_send, 17+1); /* Generate a random payload */ // for (int i = HDR_LEN; i < MAX_LENGTH; i++) // { // txData[i] = rand(); // } /* Set packet to transmit */ RCL_TxBuffer_put(&rclPacketTxCmdGenericTx.txBuffers, txPacket); rclPacketTxCmdGenericTx.common.status = RCL_CommandStatus_Idle; /* Submit command */ RCL_Command_submit(rclHandle, &rclPacketTxCmdGenericTx); /* Pend on command completion */ RCL_Command_pend(&rclPacketTxCmdGenericTx); usleep(PACKET_INTERVAL); } } This is part of my test code, based on the original rfPacketTx example. I only made some simple packet construction changes and modified: #define FREQUENCY (2402000000U) // set to BLE channel 37 I hope this helps clarify the issue I am trying to understand.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3865358Thu, 14 May 2026 02:25:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:0f0a816e-fb15-4f79-b4c5-ae568b6895a6LydiaHello, we have received your case and the investigation will take some time. Thank you for your patience.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettxThu, 14 May 2026 02:22:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:de3985fb-5de5-4fee-a904-c98374eaa12bQingtian YangPart Number: CC2340R5 Other Parts Discussed in Thread: SYSCONFIG Hi, I am trying to use the CC2340R5 with the LP_EM_CC2340R5/prop_rf/rfPacketTx example as a starting point. My goal is: Use the Custom RF stack configuration with BLE PHY selected ( Generic 1 Mbps / 2 Mbps / Coded ) Transmit a fixed custom BLE advertising PDU Do not use the full BLE stack (GAP/GATT/LL) Later switch dynamically between BLE PHY and other PHYs for a multi-protocol application Currently I can run with the prop_rf example, but I cannot make a valid BLE advertising packet that can be detected by a phone or nRF Connect. I would like to understand: When using Custom -> BLE PHY in SysConfig, does the radio automatically handle: BLE Access Address (0x8E89BED6) CRC24 Data whitening BLE bit ordering Is it sufficient to provide only the BLE advertising PDU payload: Header AdvA AdvData or do I need to manually construct the full BLE over-the-air packet? Does the rfPacketTx example use a proprietary packet formatter that prepends packet length or uses a non-BLE packet structure? Is there an official example for transmitting raw/custom BLE advertising packets without using the BLE stack? My current intention is to transmit only on advertising channel 37 (2402 MHz) first. Thank you.SYSCONFIGCC2340R5https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camds/3852187Thu, 23 Apr 2026 03:28:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:33966f9c-9f5d-45f4-b986-46d7eced8730Taylor您这个问题需要提到客服的质量组进行处理，请在下面链接选择相应项 联系我们 | 技术支持 | 德州仪器 TI.com.cnhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camds/3852186Thu, 23 Apr 2026 03:23:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:6a94dec0-cfd5-43c5-8446-530a139bff87Taylor您好， 已经收到了您的案例，调查需要些时间，感谢您的耐心等待。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camdsThu, 23 Apr 2026 03:18:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:1f799eb1-977e-40e2-b50e-076f6f6430b5Shibing WuPart Number: SN74LVC1G66-Q1 贵司之前提交的CAMDS已经失效了，请重新提交 MNN.04R0A.0089 IC SWITCH SPST SN74LVC1G66QDCKRQ1 CAR TI SN74LVC1G66QDCKRQ1 CAMDS失效的ID:CA_5_69980954/2SN74LVC1G66-Q1https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1033061/trf7970a-trf7970arhbr/3708207Tue, 21 Oct 2025 03:00:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:afb2a3de-0e36-437a-a240-b96c52d98bcbKevin ChenI just want to know what material is used for THERMAL PAD and is this normal？https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1033061/trf7970a-trf7970arhbr/3708205Tue, 21 Oct 2025 02:44:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:5200eb47-363b-4d1b-a6f2-62b515c43e0dDaniel您好 TI 论坛旨在解决客户在使用TI产品过程中遇到的技术问题。 建议您请按照以下方式联系客户支持部门，会有客服为您提供帮助。 打开链接 https://ticsc.service-now.com/csm 点击“申请新的支持”下面的“提交申请”按钮 在新打开的窗口中点击“质量，可靠性和环境信息”下面的“创建案例”按钮 在打开的表格中您可以使用中文描述您的问题并且递交。 关于质量问题，请您查阅客户退货流程： https://www.ti.com.cn/zh-cn/support-quality/additional-information/customer-returns.htmlhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1033061/trf7970a-trf7970arhbrTue, 21 Oct 2025 02:26:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:69d52019-fffe-42fc-a89e-ff8fc058531bKevin ChenPart Number: TRF7970A 你好， TRF7970ARHBR 拆开编带发现THERMAL PAD划痕明显，受影响区域超过镀铅面积的50% 请问THERMAL PAD用的是什么材料，这种情况正常吗TRF7970Ahttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1032812/cc2590-cc2500-cc2590/3707205Fri, 17 Oct 2025 07:45:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:ce916f6a-22d0-48b0-bd7d-7c42d636ba7eTaylor以下是一些类似的资源供参考 https://www.ti.com/lit/swra375 https://www.ti.com/lit/swra422 还可以在 SIMPLELINK-2-4GHZ-DESIGN-REVIEWS . 上审查硬件设计。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1032812/cc2590-cc2500-cc2590/3707197Fri, 17 Oct 2025 06:12:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:415743a3-57b9-4ebb-8a3d-bd674058ea9bTaylor您好， 已经收到了您的案例，调查需要些时间，感谢您的耐心等待。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1032812/cc2590-cc2500-cc2590Fri, 17 Oct 2025 06:10:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:f5718400-e1d3-4f3f-9def-42ec76e113fbZ.Cheng CPart Number: CC2590 Other Parts Discussed in Thread: CC2500 , 在CC2590数据手册中，有关CC2500+CC2590的电路设计的前级电路并没有相关元件参数，应如何确定相关元件参数？另外数据手册中对于AVDD_PA2和AVDD_LNA引脚的连接线做出了要求，是否只要这部分PCB线路短而粗即可，还是必须满足一定的长度和宽度要求，如果是的话应该为多少？ 好CC2590cc2500SIMPLELINK-2-4GHZ-DESIGN-REVIEWShttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1024722/cc2500/3688948Mon, 22 Sep 2025 23:49:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:6833d0a5-e4e6-4522-ba0a-77c162f0c9a9Daniel您好 Is it possible to test the sensitivity of the device in the hardware? See section 7 of this for details: https://www.ti.com/lit/pdf/swra370