其他无线技术论坛 - 最近的话题

CC2340R5: CC2340R5-Q1: Can 48MHz XTAL pin (X48P/X48N) accept external CMOS clock (bypass mode)?

yuling Lu — Sun, 13 Sep 2026 12:29:42 GMT

Part Number: CC2340R5

Hi TI team,

I am designing a rotating telemetry system (thermocouple
acquisition on a rotor spinning up to 60000 rpm) using the
CC2340R5-Q1 as the rotor-side MCU + 2.4GHz radio.

Question about the 48 MHz high-frequency clock:

1) Does the CC2340R5 support an "external clock source"
(bypass / clock-input) mode on the 48 MHz XTAL pins
(X48P / X48N)?

The datasheet (SWRS292A, section "Clock Systems") states
that "Radio operation requires an external 48 MHz crystal",
and it clearly documents an "LFXT bypass mode" for the
32.768 kHz input. However I could NOT find any statement
about whether the 48 MHz HFXT input also supports bypass
mode / external single-ended clock injection.

2) If bypass mode IS supported, please advise:
- Which pin should be driven (X48P?), and what to do with
the other pin (X48N) -- float, or tie to GND?
- Required input amplitude (Vpp / Vih / Vil) and waveform
(sine vs. square/CMOS)?
- Allowed frequency tolerance (ppm)?
- Any register / SysConfig setting needed to enable it?

Background / why I am asking:

At 60000 rpm, the on-rotor electronics see ~80,000 g of
steady centrifugal acceleration. A quartz crystal cannot
survive this (typical quartz shock rating is only
1,000-3,000 g), so I want to drive X48P from a SiTime MEMS
oscillator (e.g. SiT8918BA-71-33N-48.000000, +/-20 ppm,
-40 to +125 C) which outputs a rail-to-rail 48 MHz CMOS
square wave.

3) If bypass mode is NOT supported: can a single-ended CMOS
oscillator be connected to X48P with X48N left floating,
and will the internal programmable load capacitance
(5-9 pF) cause any problem in that case?

4) Additional question: Is the 32.768 kHz LFXT required for
proprietary 2.4 GHz (non-BLE) operation? Can I reliably
use the internal LFOSC only, to save board space and
reduce component count on the rotor?

Thank you very much for your help.

Best regards,
[Lu]

RE: CC2340R5: CC2340R5-Q1: Can 48MHz XTAL pin (X48P/X48N) accept external CMOS clock (bypass mode)?

Alice — Mon, 14 Sep 2026 06:45:35 GMT

您好，

不支持外部48MHz时钟输入，只能使用48MHz晶振，不支持单端输入。

这是射频模块工作需要的，只有32.768 kHz不可以.

Crystal Oscillator and Crystal Selection for the CC13xx, CC26xx, and CC23xx Family of Wireless MCUs (Rev. L)

RE: CC2340R5: CC2340R5-Q1: Can 48MHz XTAL pin (X48P/X48N) accept external CMOS clock (bypass mode)?

Eirwen — Sun, 13 Sep 2026 22:51:41 GMT

Hello, we have received your case and the investigation will take some time. Thank you for your patience.

RE: TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

Alice — Fri, 07 Aug 2026 00:24:26 GMT

您好，

天线及输出功率都会影响读取距离，请参考链接文档了解天线设计

TMS3705: Methods to increase the read range of the receiver - Other wireless technologies forum - Other wireless - TI E2E support forums

[Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums

另外，这个导轨电源的85khz 800mv的干扰噪声是通过射频耦合的，那么可否从实施角度考虑给导轨电源外加屏蔽罩呢？

TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

bo yang — Wed, 05 Aug 2026 02:44:41 GMT

Part Number: TMS3705

尊敬的TI设计团队，您们好！

我们在设计使用TMS3705设计低频读卡器的时候，在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。我们在工业现场做过一下验证，在工业现场使用读取距离只有2cm，后面用在工业现场那个电源把我们的读卡器拿到机房外面测试，读取距离回复正常。我们初步判断不是我们24V输入电源的影响。后面经过多方面测试和观察我们发现是工业现场的一个导轨电源发出了85k波形被我们天线接收都了影响了我们的读取距离。如下图所示的导轨电源，后面我们用示波器探头在空气测试中发现距离导轨电源越近这个85k干扰波形在空间中电压越大大概在800mv左右。而且我们的读卡器距离导轨电源越近基本上读取不到，距离他远一点距离会长一点，但是也只能有2cm无法到达10cm。像这种情况我们在使用TMS3705的设计的时候应该做哪些相关抗干扰设计和防护。以及现场这种情况有没有比较的解决方案，非常感谢了！

TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

bo yang — Wed, 05 Aug 2026 02:49:32 GMT

Part Number: TMS3705

尊敬的TI设计团队，您们好！

RE: TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

FRANK1 — Wed, 05 Aug 2026 06:00:10 GMT

你看看调整下接收天线的角度和功率看看有没有改善。

(+) [Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums

另外，导轨电源能不能加上屏蔽罩，会有效阻止频率干扰。

RE: TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

Alice — Wed, 05 Aug 2026 05:41:20 GMT

您好，

天线及输出功率都会影响读取距离，请参考链接文档了解天线设计

TMS3705: Methods to increase the read range of the receiver - Other wireless technologies forum - Other wireless - TI E2E support forums

[Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums

另外，这个导轨电源的85khz 800mv的干扰噪声是通过射频耦合的，那么可否从实施角度考虑给导轨电源外加屏蔽罩呢？

RE: TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

Daniel — Wed, 05 Aug 2026 03:02:10 GMT

您好

已经收到了您的案例，调查需要些时间，感谢您的耐心等待

RE: TMS3705: TMS3705设计得低频读卡器在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。电磁干扰

FRANK1 — Wed, 05 Aug 2026 02:54:19 GMT

感谢您对TI产品的关注！
关于你的咨询，我们正在确认您的问题，感谢您的耐心等待。

RE: CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Tarek D — Thu, 21 May 2026 20:05:06 GMT

你好，

您如何验证有效载荷是否完整？

此致，

塔雷克·D

CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Qingtian Yang — Thu, 14 May 2026 02:22:00 GMT

Part Number: CC2340R5

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.

RE: CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Qingtian Yang — Wed, 20 May 2026 08:24:27 GMT

您好：

我已经能够成功发出了ble的广播包了，但是我的sniffer提示我：crc错误，但payload完整无误。但是我找不到在sysconfig当中设置他的地方，这些配置都被隐藏了吗。另外我使用的simplelink-lowpower-f3-sdk 8.10，我使用类似的代码在SDK 9.20上面是正确的，我找不到调试的方向，能否提供关于sysconfig配置Generic BLE的更多信息

RE: CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Ryan Brown1 — Fri, 15 May 2026 14:48:42 GMT

你好，

您应该查阅RCL API 指南中的BLE 命令处理程序（例如广播命令处理程序）和BLE5 文件参考。请注意，这需要使用自定义的 ti_radio_config.c/h 文件，因为 SysConfig 目前不支持自定义使用这些 RCL 命令。本质上，rfPacketTx 使用 BLE PHY，但并未公开所有 RCL 命令。您需要进一步研究文档，并尝试调整项目配置及其广播数据包结构，才能获得预期的输出。

问候，
瑞安

RE: CC2340R5: CC2340 DMM: Support for Lightweight Multi-protocol (BLE + 802.15.4 / Proprietary) without full-stack overhead

Alice — Fri, 15 May 2026 03:54:54 GMT

Hello,
We have received your post and the investigation will take some time.
Thanks for your patience.

CC2340R5: CC2340 DMM: Support for Lightweight Multi-protocol (BLE + 802.15.4 / Proprietary) without full-stack overhead

Qingtian Yang — Fri, 15 May 2026 02:13:47 GMT

Part 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!

RE: CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Qingtian Yang — Thu, 14 May 2026 02:30:06 GMT

static 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.

RE: CC2340R5: CC2340R5 Custom BLE PHY: How to transmit raw/custom BLE advertising PDUs without BLE stack using prop_rf/rfPacketTx?

Lydia — Thu, 14 May 2026 02:25:15 GMT

Hello, we have received your case and the investigation will take some time. Thank you for your patience.

RE: SN74LVC1G66-Q1: CAMDS失效

Taylor — Thu, 23 Apr 2026 03:28:20 GMT

您这个问题需要提到客服的质量组进行处理，请在下面链接选择相应项

联系我们 | 技术支持 | 德州仪器 TI.com.cn

SN74LVC1G66-Q1: CAMDS失效

Shibing Wu — Thu, 23 Apr 2026 03:18:52 GMT

Part Number: SN74LVC1G66-Q1

贵司之前提交的CAMDS已经失效了，请重新提交

MNN.04R0A.0089

IC SWITCH SPST SN74LVC1G66QDCKRQ1 CAR

SN74LVC1G66QDCKRQ1

CAMDS失效的ID:CA_5_69980954/2

RE: SN74LVC1G66-Q1: CAMDS失效

Taylor — Thu, 23 Apr 2026 03:23:44 GMT

您好，

已经收到了您的案例，调查需要些时间，感谢您的耐心等待。

RE: TRF7970A: TRF7970ARHBR 镀层层划伤脱落于铅单引线

Kevin Chen — Tue, 21 Oct 2025 03:00:12 GMT

I just want to know what material is used for THERMAL PAD and is this normal？

TRF7970A: TRF7970ARHBR 镀层层划伤脱落于铅单引线

Kevin Chen — Tue, 21 Oct 2025 02:26:41 GMT

Part Number: TRF7970A

你好，

TRF7970ARHBR 拆开编带发现THERMAL PAD划痕明显，受影响区域超过镀铅面积的50%

请问THERMAL PAD用的是什么材料，这种情况正常吗

RE: TRF7970A: TRF7970ARHBR 镀层层划伤脱落于铅单引线

Daniel — Tue, 21 Oct 2025 02:44:28 GMT

您好

TI 论坛旨在解决客户在使用TI产品过程中遇到的技术问题。建议您请按照以下方式联系客户支持部门，会有客服为您提供帮助。

打开链接https://ticsc.service-now.com/csm
点击“申请新的支持”下面的“提交申请”按钮
在新打开的窗口中点击“质量，可靠性和环境信息”下面的“创建案例”按钮
在打开的表格中您可以使用中文描述您的问题并且递交。

关于质量问题，请您查阅客户退货流程：https://www.ti.com.cn/zh-cn/support-quality/additional-information/customer-returns.html

CC2590: CC2500+CC2590的电路设计

Z.Cheng C — Fri, 17 Oct 2025 06:10:07 GMT

Part Number: CC2590

在CC2590数据手册中，有关CC2500+CC2590的电路设计的前级电路并没有相关元件参数，应如何确定相关元件参数？另外数据手册中对于AVDD_PA2和AVDD_LNA引脚的连接线做出了要求，是否只要这部分PCB线路短而粗即可，还是必须满足一定的长度和宽度要求，如果是的话应该为多少？
好