低于 1GHz 论坛 - 最近的话题

CC1312R: an updated Audio Plugin for CC1312R1 supporting SysConfig

zili fl — Wed, 03 Jun 2026 02:29:49 GMT

Part Number: CC1312R

CC1312R: Where can I set the frequency of the audio SDK's radio frequency？ - 低于 1GHz 论坛 - 低于 1GHz - E2E™ 设计支持

I noticed you mentioned the latest audio development SDK plug-in. Could you please send it to me? We have already signed the NDA.

CC1310: CC1310低频晶振在系统中的作用

ancient frog — Wed, 20 May 2026 09:26:23 GMT

Part Number: CC1310

你好，

我的测试板误装了REV A 的CC1310，同时没有放置外部低频晶振，所以我想咨询下，外部低频晶振（32.768kHz）主要会影响系统的哪一部分？换言之就是他会为系统的哪部分提供时钟？这些部分的功能是什么？（e.g.休眠定时？or射频定时器？）

谢谢！

CC1310: REV A版本通信问题

ancient frog — Tue, 19 May 2026 01:44:29 GMT

Part Number: CC1310

你好，

我在使用SmartRF Studio对测试板1进行测试。测试板1的发射性能（868MHz）与其余测试板相同，RX性能（868MHz）低于其余测试板2~5db。

备注：其余测试板包括LAUNCHXL-CC1310和旧版本的自制测试板，其中的CC1310均为REV B。测试板1为最新自制测试板，误装了REV A 的CC1310。所有自制测试板均按照TI最新参考设计进行设计，且省略了外部LF 晶振。

我的问题：

1.CC1310的版本问题（REV A），是导致TX性能正常，RX性能异常的原因吗？

2.TI何时在中国进行了REV A至REV B的迭代？我在2026年购买的CC1310为REV A版本，是供应商的库存料还是fake芯片？

谢谢。

CC1200: 關於新的安規認證

yang ch — Mon, 04 May 2026 06:19:35 GMT

Part Number: CC1200

新版安規法條EN300220測試規定有下圖1要求

需提供在地震盪(LO, Local Oscillator)及中頻(IF, Intermediate Frequency)二項資訊

程式中的RF參數為圖2,如何知道"中頻"及"在地震盪"二者資訊呢?

(圖1)

(圖2)

TI-15-4-STACK-GATEWAY-LINUX-SDK: TI_ucc5881qdfcrq1电气仿真SPICE模型咨询

hu xianke — Tue, 14 Apr 2026 06:14:18 GMT

Part Number: TI-15-4-STACK-GATEWAY-LINUX-SDK

请问哪里可以下载到这个芯片的spice仿真模型，谢谢

CC1101: CC1101的RSSI读取数值异常

Lott Yu — Thu, 02 Apr 2026 10:17:54 GMT

Part Number: CC1101

测试了5个CC1101模块，其中2个存在RSSI读取异常；433MH的频率，在1.2k空速，5.2K频偏、58k带宽下进行GFSK调制通信测试，使用信号源进行CC1101的接收数据包的RSSI数据读取测试和灵敏度测试。

测试结果现出异常模块的RSSI接收数据包RSSI读取始终偏差较大且灵敏度也较差。同时使用另一个模块在固定位置进行发送，在同一块测试底板上，固定位置固定天线实际测试模块间的通信，异常模块的RSSI数据仍表现异常。

将正常模块和异常模块的CC1101芯片进行交换，异常模块恢复正常，而正常模块出现RSSI异常的问题，可以看出异常跟随CC1101芯片变动，和模块的PCB以及外围器件无关。请问这是什么原因导致的异常。表格是记录的测试数据，其中1号和2号模块是异常模块，2、4和5号模块为正常模块，原始值是从CC1101的接收数据包中获取的RSSI，计算值是根据CC1101手册提供的计算方式得出的数据。

疑问：

1、是否CC1101芯片生产工艺有变化，导致数据包RSSI读取变动，有批次差异？

2、是否有其它异常导致该问题？

3、综上是否有解决方案

CC1312R: 大核应用程序中如果使用ADC功能，小核（SENSOR传感器控制器是否就不能初始化通过），两者不能同时使用么？

zjj12138 — Thu, 26 Mar 2026 06:10:30 GMT

Part Number: CC1312R

原本运行正常的应用程序：ADC数据采集功能放在小核里面采集数据，大核里面没有ADC采集小核运行正常，大核运行正常；

因为一直采集上的原因，想要把小核里面的ADC采集放在大核里面去做，把小核ADC采集功能关闭并删除，遇到的问题是程序在ADC初始化完成后，对RF初始化，再对小核初始化，初始化小核运行到 scifInit(&scifDriverSetup);就进行不下去了。是大核ADC启用后不能再启动小核了么？还是RF的初始化影响了小核初始化？

CC1310: CC1310 GPIO控制问题

TX dong — Sat, 21 Mar 2026 03:09:32 GMT

Part Number: CC1310

最讨厌的没有基础库的器件让我遇到了！控制GPIO竟然这么久了还没办法实现。

目的：让LED闪亮

现象：点亮LED时，DOUT寄存器变化正常，DOE位正常，但DIN位没变化，所以LED就不会变化。

程序： while(1) {
uint32_t t = PIN_getOutputValue(Board_PIN_LED0);
t = 1^t;
t = t & 1;
t = PIN_setOutputValue(ledPinHandle, Board_PIN_LED0, t);
//sleep(1000);
CPUdelay(8000*50);
}

CC1312R7: 2GFSK通信时，CRC检测错误

chun dong — Wed, 18 Mar 2026 08:08:56 GMT

Part Number: CC1312R7

我们在尝试使用两块LP-CC1312R7来测试2GFSK的收发，我们在TX/RX端都已经关闭了CRC检测，但是通过smartRF studio接收的数据总是报CRC error. 请问下怎么解决？

Tx端的配置为：

Rx端配置为：

CC1312R: CC1312在空中升级例程中加入SENSOR小核程序，但是小核唤醒大核时间不正常

zjj12138 — Mon, 09 Mar 2026 01:26:17 GMT

Part Number: CC1312R

在CC1312例程的基础上做了修改，在程序没有进入升级模式时不启动OAD部分程序，运行一部分功能性应用程序，根据存储标志识别。

应用程序的功能：sensor定时唤醒大核进行数据发送，但是在唤醒过程中发现定时的时间异常，无论设置几秒唤醒一次，都会很快被唤醒（根据观察不到一秒的时间）

目目前设置了10秒唤醒一次

CC1312R7: CC1312R的无线音频开发插件demo中的RX和TX两端的I2S时钟频偏问题时如何处理的

zili fl — Sat, 07 Mar 2026 08:31:18 GMT

Part Number: CC1312R7
Other Parts Discussed in Thread: CC1312R,

CC1312R的rfAudioTX和rfAudioRX端的I2S时钟都是采用的本地时钟，两边的时钟不可避免存在频偏问题，那TX端发送到RX端的数据，写缓冲区或者读缓冲区，就会有溢出或者读空的情况出现（这种情况的出现会导致有噪音或者爆音的出现），这个demo里是否有做特殊处理，避免这个问题。

CC1352P: CC1352P1 LaunchPad 进入standby后无法用按键唤醒

ea skk — Fri, 27 Feb 2026 02:16:53 GMT

Part Number: CC1352P

代码仅做最简进入standby后按键唤醒，测试用外部供电仅能进入休眠，无法唤醒，调试器供电也一样，有没有大佬知道怎么解决

#include <stdint.h>
#include <stdbool.h>
#include <ti/drivers/Power.h>
#include <ti/drivers/power/PowerCC26XX.h>
#include <ti/drivers/GPIO.h>
#include "ti_drivers_config.h"



volatile bool isKeyWakeup = false;
#define AON_WAKEUP_PIN 14  
#define LED_PIN 6       


void keyWakeupCallback(uint_least8_t index)
{
    isKeyWakeup = true;
    GPIO_clearInt(index);
}


void initWakeupSystem(void)
{
    Power_init();
    Power_releaseConstraint(PowerCC26XX_DISALLOW_STANDBY);
    Power_setPolicy(PowerCC26XX_standbyPolicy);
    GPIO_init();
    GPIO_PinConfig wakeupConfig = GPIO_CFG_IN_PU | GPIO_CFG_IN_INT_FALLING | GPIO_CFG_INT_ENABLE | GPIO_CFG_SHUTDOWN_WAKE_LOW;
    GPIO_setConfig(AON_WAKEUP_PIN, wakeupConfig);
    GPIO_setCallback(AON_WAKEUP_PIN, keyWakeupCallback);   
    GPIO_setConfig(LED_PIN, GPIO_CFG_OUT_STD | GPIO_CFG_OUT_LOW);
}


void *mainThread(void *arg0)
{
    initWakeupSystem();

    while(1)
    {
        isKeyWakeup = false;
       
        Power_sleep(PowerCC26XX_STANDBY);
        
       
        if (isKeyWakeup)
        {
            GPIO_toggle(LED_PIN);
          
            for (volatile uint32_t i=0; i<200000; i++);
        }
    }
}

CC1310: CC1310器件库

TX dong — Tue, 24 Feb 2026 10:31:07 GMT

Part Number: CC1310

最近需要使用cc1310做项目，初次使用，看了器件库后，一头雾水。

我是从C2000走来，感觉CCS的编辑风格和功能，比其它编译优点特别突出。C2000的底层库文件一目了然，控制起来非常容易。

然而，CC1310的器件库封装在LIB文件中，象端口控制和简单过程，也只能通过库来完成。很不习惯！且例程又较少。

现在做的项目，需要用到比较器、定时器、ADC，等，没找到它的例程。

我希望的是：能不能提供像C2000那样的库文件？可以直接对寄存器操作达到初始化及运行的目的。

CC1354P10: MAP_GapInit_cancelConnect() in SDK 8.31 resolves to trap (E7FE) and causes infinite loop when canceling initiating (CC1354P10_6)

liu yi_zheng — Fri, 13 Feb 2026 02:21:21 GMT

Part Number: CC1354P10
Other Parts Discussed in Thread: BLE-STACK

MAP_GapInit_cancelConnect() resolves to trap (E7FE) in SDK 8.31 causing infinite loop during initiating cancel

Environment

SDK Version: SimpleLink CC13xx/CC26xx SDK 8.31.00.11
Device: CC1354P10
Stack Variant: ble5stack_flash / cc1354p10_6
Base Example: multi_role
Toolchain: TI ARM compiler (CCS)

Problem Description

When operating as Central and performing connection initiation, our application implements a timeout mechanism. Upon timeout, we call the cancel connection procedure (initiator cancel).

However, when this path executes, the system enters an infinite loop inside:

MAP_GapInit_cancelConnect()

The device halts and never returns.

Disassembly Evidence

The function resolves to:

E7FE    b .

This corresponds to a 2-byte infinite branch instruction (trap stub).

Map File Evidence

From the generated .map file:

00060382    00000002     rom_init.o (.text.MAP_GapInit_cancelConnect)

This confirms:

MAP_GapInit_cancelConnect is linked from rom_init.o
Function size is 2 bytes
It matches the trap stub (E7FE)

Expected Behavior

The official examples and stack references indicate that the correct implementation path should call:

GapInit_cancelConnect()

To verify this, we modified rom_init.c as follows:

extern uint8 GapInit_cancelConnect(void);

uint8 MAP_GapInit_cancelConnect(void)
{
#if (HOST_CONFIG & CENTRAL_CFG)
    return GapInit_cancelConnect();
#else
    return bleIncorrectMode;
#endif
}

After this change:

The project builds without errors
The .map file now shows:

0008262f    GapInit_cancelConnect

Cancel connect executes correctly
The infinite loop no longer occurs

Observations

GapInit_cancelConnect() exists and links successfully (presumably from OneLib.a).
The default rom_init.c implementation of MAP_GapInit_cancelConnect() appears to be a trap stub.
This trap is reached during a valid central initiating timeout → cancel scenario.

Questions

Why does SDK 8.31 provide a trap implementation for MAP_GapInit_cancelConnect()?
Is this behavior expected only under certain configuration variants?
Is there a required glue-layer variant that should override this stub?
Should this be considered a defect in the cc1354p10_6 ble5stack_flash configuration?

CC1352P: Problem configuring LAUNCHXL-1352P-2 for the TI Wi-SUN stack

Jose Ramón Serrano Pérez — Mon, 09 Feb 2026 05:48:26 GMT

Part Number: CC1352P
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I´m triying to configure a project for the LAUNCHXL-1352P-2 with TI Wi-SUN stack and when I try to select in the stack the LAUNCH 1352P-2, which is the same selected for the rfdesign, etc.

I got the error below:

I´ve tried everything, but with the same result. Tested in windows and Linux(Fedora)

I think is something related with the sdk, but i don´t know.

I would be grateful if someone could tell me how to solve this.

Thanks in advance.

empty-00.rar

CC1352P7: coordinator zigbee+bluetooh

Jesús Antonio Cardona Jaramillo — Fri, 06 Feb 2026 15:17:20 GMT

Part Number: CC1352P7
Other Parts Discussed in Thread: CC1354P10, CC1352P, CC2650

Greetings.

I am working on an application where I use a BeaglePlay (BeagleBoard) as a gateway. The BeaglePlay includes an internal CC1352P7 microcontroller. In addition, I am using two BeagleConnect Freedom boards, which also include a CC1352P7, and I also have two CC1352P1 LaunchPad boards.

My question is whether there is any example or reference project that could guide me. I need to install a Zigbee + Bluetooth coordinator firmware on the internal CC1352P7 inside the BeaglePlay. That would be ideal for me. I could use one of the LaunchPads, but I would like to have everything embedded in the BeaglePlay.

I am using Home Assistant as the platform for data capture. At the moment, I have the CC1352P7 running a Zigbee coordinator firmware, and I am using one BeagleConnect Freedom as a receiver for another BeagleConnect Freedom using upstream 6LoWPAN.

My need is that I want to measure acceleration, and for that I have a classic TI SensorTag, which (as I understand) connects via Bluetooth. It would be great for me to have Zigbee + Bluetooth on the BeaglePlay, or alternatively on the BeagleConnect Freedom that is acting as the upstream 6LoWPAN receiver (i.e., receiver + Bluetooth).

One additional concern: once I have a multiprotocol firmware (Zigbee + Bluetooth), how does Home Assistant recognize it? Normally I need to bind a mechanism or device such as a /dev/ttyS* interface. If the microcontroller runs Zigbee + Bluetooth at the same time, how would Home Assistant detect and handle each protocol separately?

Thank you very much.

Jesus

CC2650: Inquiry regarding BLE Security Implementation on SensorTag CC2650 (BLE-Stack 2.2.2)

Areebah Ali — Fri, 06 Feb 2026 08:34:23 GMT

Part Number: CC2650
Other Parts Discussed in Thread: CC2540, BLE-STACK

Dear TI Support Team / Technical Experts,

I am currently working on my Final Year Project involving the SensorTag CC2650. My objective is to implement and verify Bluetooth Low Energy (BLE) security/encryption to protect data transmission.

My Current Setup:

Hardware: SensorTag CC2650, USB Dongle CC2540 (for sniffing).
Software/IDE: Code Composer Studio (CCS) v7.4.0.
Stack: BLE-Stack Version 2.2.2.
Monitoring: SmartRF Packet Sniffer v2.18.1 running on Windows 7 (VMWare) and Simplelink SensorTag App on a Google Pixel 8.

Requirement: I have successfully captured unencrypted packets using the CC2540 sniffer. I now need to enable security (Pairing/Bonding and Encryption) so that the data packets appear encrypted in the sniffer for comparison.

Could you please provide guidance or documentation on the following:

Which specific files or parameters within the SimpleBLEPeripheral (or relevant sample project) in BLE-Stack 2.2.2 need to be modified to trigger the Pairing/Bonding process?
How to configure the GAP Bond Manager (gapbondmgr.c) to enforce encryption for specific characteristics.
Are there specific "Application Notes" or "Software Developer Guides" for BLE-Stack 2.2.2 that detail the transition from a non-secure link to an encrypted one?

I want to ensure the CC2540 sniffer correctly identifies the encrypted packets so I can document the difference for my project analysis. Any code snippets or walkthroughs would be highly appreciated.

Best regards,

CC1312R: 关于CC1312使用外部48M晶振的问题再CCS12.4中有相关设置，但是ccs20.1.1中找不到相关设置了

zjj12138 — Thu, 22 Jan 2026 07:29:52 GMT

Part Number: CC1312R

我在开发板上使用CCS2.1.1调试好的程序，在自己电路板上使用SUB1G发不出去了，但是使用CCS12.4调试的程序正常发送；目前猜测可能是晶振设置有问题，CCS12.4包含以下设置

但是CCS20.1.1中找不到相关设置

以下是我不分电路图使用了一个48M晶振

CC1312R: 想要在CC1312上使用BOOSTXL-SHARP128显示器模块有没有相关的驱动

zjj12138 — Tue, 20 Jan 2026 08:22:51 GMT

Part Number: CC1312R
Other Parts Discussed in Thread: BOOSTXL-SHARP128

想要在CC1312上使用BOOSTXL-SHARP128显示屏，但是查找了很多资料没有该屏的驱动例程，请问官方是否有提供相关例程

LMH13000RQEEVM: 我是用lmh13000评估版来点亮二极管，但输出电流为0，二极管没有压降，不亮

feng feng ling — Sat, 17 Jan 2026 05:47:29 GMT

Part Number: LMH13000RQEEVM

我采用了两款激光二极管但输出电流都为0二极管不亮.pptx

CC1190: CC1190的电路设计是否可行

Z.Cheng C — Wed, 14 Jan 2026 07:28:38 GMT

Part Number: CC1190
Other Parts Discussed in Thread: CC1101,

我想请教一下该原理图设计是否有问题，通过CC1101与CC1190实现915MHz频段的无线通信，其中电容电感参数以及滤波器选型是否合适，能否优化前级电路，下面两板Layout设计是否有哪里缺陷较为严重，需要优化的话应从哪些方面入手，RF/N 、RF/P信号走线是否需要按照差分走线？欢迎您提出任何想法建议...

CC1312R: 在一个工程中可以跳转频段么？

zjj12138 — Mon, 12 Jan 2026 08:49:26 GMT

Part Number: CC1312R
Other Parts Discussed in Thread: SYSCONFIG

需要实现的功能

1：OAD空中升级；（维护功能时程序使用）

2：采集数据并通过SUB1G将数据发送出去；（功能程序）

以上两个功能在不同的线程中，设备启动时会选择其中一个线程启动，不会同时运行两个线程。但是数据发送和OAD空中升级必须在不同的频段中；

根据ccs里面设置频段的入口只找到下图修改入口，如何在启动不同的线程时选择不同的频段参数呢？

我会在芯片里做一个数据存储区，掉电不丢失的保存一个标志用来判断需要进入哪一个线程的功能，进而选择不同的频段。

CC1312R: 提升发射功率方案需求

Hui Cao22 — Tue, 06 Jan 2026 02:43:34 GMT

CC1311P31T0RGZR，软件 15.4 协议栈在 433MHz 频段下，是否支持20dBm 的输出功率？

CC1310: CC1310串口接收

user6331972 — Wed, 24 Dec 2025 11:44:45 GMT

Part Number: CC1310

CC1310串口接收时，调用UART_read（）函数时，CPU停在这个函数上不动，一直等待串口接收到数据，没有办法查询其他函数，有没有其函数可以不一直在等串口接收到数据，串口接收到数据读取数据就可以，没有数据时能过去查询其他函数或者变量。或者判断那个标志能知道串口接收缓冲区已有接收数据，再调用UART_read（）函数。

CC1312R: 提升发射功率方案需求

Hui Cao22 — Tue, 23 Dec 2025 07:19:39 GMT

Part Number: CC1312R
Other Parts Discussed in Thread: CC1311P3, LP-CC1311P3

TI 基于 CC1312R 是否有提供，通过外置功率放大器将发射功率提升到 20dBm 或 22dBm 的方案？
如果没有 1 所述方案，是否有其他方案，当前 CC1312R 发射功率只有 14dBm，我们希望提高点。

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian