https://e2e.ti.com/support/wireless-connectivity/Products covered in this section are low power RF ICs and connectivity protocols such as ZigBee, RF4CE, Bluetooth & Bluetooth Low Energy, ANT, WLAN, SimpliciTI, ISO 15693/14443, and NFC.en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475917Tue, 08 Sep 2026 11:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:cf59028e-206f-4d8a-8d76-089b5bf7fa96Ratul KarHi Lea, As you have mentioned, I will answer them one by one - [quote userid="646004" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475868"]What are you using to read this in CCS directly ?[/quote] In the TIDA_01580_TX.c file I have added a display function to display the device Id over serial console in CCS but unable to see the devID. So for this I have the CC2640R2F Dev kit and TMP117EVM connected over I2C while no TIDA-01580 interface connected to the CC2640R2F dev kit. If there is a easy to read out the temperature, device id please let me know. [quote userid="646004" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475868"]You mention that you're able to run all the other parts fine but adding the TMP117 breaks the data reading. Are you able to run and read the TMP117 measurements independently without the other parts (ECG/PPG/SPo2) ?[/quote] We were able to run the TIDA firmware and checked the data in Tida01580 Labview application thanks to the TI forum since we were struggling at the starting. As you have mentioned I have not tried yet to measure the TMP117 data independently while interfacing with CC2640R2F dev kit but while using stand alone TMP117EVM the we can see the data over the TI cloud tool. If you can help me to interface the TMP117 from the TMP117EVM breakout board with CC2640R2F dev kit independently then it would be a great help. [quote userid="646004" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475868"]How are you connecting the other parts to the CC2640R2F ?[/quote] Currently only the TMP117EVM breakout board is connected with the CC2640R2F dev kit over I2C. [quote userid="646004" url="~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475868"] Are they all using I2C ?[/quote] No, The TIda-01580 including the AFE4900 is connected over SPI to CC2640R2FRGZR MCU. Also I have these question as i have highlighted over the post - " Can i run all the applications as TIDA-01580 sensors over SPI and TMP117 sensor over I2C together in CC2640R2FRGZR MCU for data capturing, processing and finally transmission over BLE". Please give a confirmation over above mentioned statement that weather it is possible or not. If it is not possible then both of our times can be saved from endless debugging. Since while searching over the forum and internet i have found that adding temp sensor such as TMP117 can cause Memory Crash, Flash Depletion,SRAM Buffer Starvation. I have also mentioned this issues over a different thread where you can find all of my concerns - https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1679248/tmp117evm-unable-to-see-the-tmp117-sensor-out-data-over-i2c-when-connected-to-cc2640r2f-for-body-temperature-measurement To solve our issue if you need anymore information let me know. Regards, Ratulhttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1680356/cc1312r-inquiry-for-sub-ghz-and-dual-band-wireless-mcus-and-modulesTue, 08 Sep 2026 10:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d90ac459-d825-4ee5-86b2-2ce62b000012Tirthal PatelPart Number: CC1312R We are currently evaluating wireless connectivity solutions for an upcoming low-power wireless device and are looking for suitable Wireless MCUs and ready-to-use wireless modules . We are primarily looking for: 1. Sub-GHz Wireless MCUs & Modules Support for the 868 MHz band Low power consumption Long-range communication Suitable for IoT applications 2. Dual-Band Wireless MCUs & Modules Support for 868 MHz Sub-GHz Additional support for 2.4 GHz Low power consumption Compact size Long-range communication Suitable for IoT applications Could you please recommend suitable products from your current portfolio and provide the following information? Complete part number Datasheet/product information Package/module dimensions and antenna options Development kit availability Product lifecycle and minimum 5-year availability/EOL support MOQ and lead time Unit pricing at 10K and 100K quantities We would appreciate your recommendations for suitable Sub-GHz and dual-band Wireless MCUs and modules , along with the above technical and commercial information. Thank you, and we look forward to your response.CC1312Rhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680353/cc3351-reset-to-irq_wl-assertion-timing-rom-bootloader-startup-timeTue, 08 Sep 2026 10:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ee068714-ec13-461e-9771-5ded036769d1Mike Wu1Part Number: CC3351 Hi TI team, I'm helping a customer evaluate the CC3351 startup sequence and have a question regarding the boot timing. Could you help clarify the timing from RESET release to IRQ_WL assertion? Specifically, we would like to understand: 1. Typical RESET → IRQ_WL timing 2. Worst-case timing, if available 3. Whether the timing depends on: - XTAL startup - Power-up conditions - Firmware version 4. Is there any official documentation or characterization data available? I checked the CC3351 datasheet but could not find a specification for the RESET-to-IRQ_WL timing. Any guidance would be appreciated. Thanks, MikeIndustrial AutomationCC3351https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475872Tue, 08 Sep 2026 10:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ae7645cb-c0a1-45d3-9c09-93a22cc0dabaGURUKUMAR YADAV BAIRAGANIWe did not generate the CC2755P20 firmware ourselves from a SysConfig example. We are implementing the programming algorithm, and the CCFG/SCFG configuration values were taken from the TI documentation/example structure available to us and incorporated into the programming algorithm for manufacturing/test. We would like to confirm the correct approach with TI. If the CCFG/SCFG C files must be generated through SysConfig for a CC2755P20 example , could you please provide the recommended example/project and the exact SysConfig configuration used to generate them? We can then use the generated hw_ccfg.h / hw_scfg.h definitions or generated configuration image in our programmer algorithm. In particular, we need the official CC2755P20 SysConfig-generated CCFG/SCFG configuration for a manufacturing/test configuration with debug authorization 0x5A .https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-output/6475868Tue, 08 Sep 2026 10:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f33086f1-7d3d-4381-82da-eb2fc0fdc6ecLeaHi, I'm struggling to understand what exactly do you mean by "unable to check the data of the body temp measurement unity in CCS itself". What are you using to read this in CCS directly ? You mention that you're able to run all the other parts fine but adding the TMP117 breaks the data reading. Are you able to run and read the TMP117 measurements independently without the other parts (ECG/PPG/SPo2) ? How are you connecting the other parts to the CC2640R2F ? Are they all using I2C ? Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1680271/cc2755p20-cc2755p207e0wrhar-programming-specifications/6475869Tue, 08 Sep 2026 10:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3b61285b-ca68-4fec-aa34-1ae3df31b672GURUKUMAR YADAV BAIRAGANIWe need clarification on the expected debug transition after programming: After MAIN/CCFG/SCFG programming, what is the required SACI command/sequence to exit SACI and enable the AHB-AP for normal SWD memory access? With Ccfg.debugCfg.authorization = 0x5A , is the AHB-AP guaranteed to become accessible after device reset , assuming CCFG and SCFG CRCs are valid? Is an additional DEBUG_EXIT_SACI_HALT (0x07) or BLDR_APP_EXIT_SACI_RUN (0x15) required before reconnecting through SWD? Are there any restrictions when CCFG was programmed during the same SACI session that affect the subsequent SWD/AHB connection? Please provide the recommended sequence for: Program → Reset → SWD reconnect → AHB-AP flash read . If AHB-AP access is still blocked after reset, what TI-documented condition/configuration should be checked in CCFG/SCFG?https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1680349/cc1312r-inquiry-for-sub-ghz-and-dual-band-wireless-mcus-and-modulesTue, 08 Sep 2026 10:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b2abdb97-7e70-45f7-b4b1-18f8a0b3da8dTirthal PatelPart Number: CC1312R We are currently evaluating wireless connectivity solutions for an upcoming low-power wireless device and are looking for suitable Wireless MCUs and ready-to-use wireless modules from Murata. We are primarily looking for: 1. Sub-GHz Wireless MCUs & Modules Support for the 868 MHz band Low power consumption Long-range communication Suitable for IoT applications 2. Dual-Band Wireless MCUs & Modules Support for 868 MHz Sub-GHz Additional support for 2.4 GHz Low power consumption Compact size Long-range communication Suitable for IoT applications Could you please recommend suitable products from your current portfolio and provide the following information? Complete part number Datasheet/product information Package/module dimensions and antenna options Development kit availability Product lifecycle and minimum 5-year availability/EOL support MOQ and lead time Unit pricing at 10K and 100K quantities We would appreciate your recommendations for suitable Sub-GHz and dual-band Wireless MCUs and modules , along with the above technical and commercial information. Thank you, and we look forward to your response. Best regards, Tirthal Patel Senior Hardware EngineerCC1312Rhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680350/cc2745r10-q1-question-about-rssi-availability-in-ble-channel-sounding-mode-3Tue, 08 Sep 2026 10:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:31641b41-9a99-491d-ad6a-d4ec19c31718Mike Wu1Part Number: CC2745R10-Q1 Other Parts Discussed in Thread: SYSCONFIG Hi Team, I am supporting a customer who is evaluating the BLE Channel Sounding example (car_node/key_node) on CC2745 and would like to obtain both Distance and RSSI measurements simultaneously. According to a previous TI E2E discussion, we suggested the following configuration to the customer: Set Channel Sounding Results Mode to Distance + Raw Results in SysConfig. Set wait_for_raw_events = true in the provided Python example script. The customer has tested the above settings and can see additional raw event messages. However, they still cannot find any RSSI-related information in the output. Could you please help clarify the following questions? Does the current Channel Sounding implementation provide RSSI information through raw events? If RSSI is available, which event or field contains the RSSI data? Are there any additional configurations, code modifications, or patches required to enable RSSI output? Is simultaneous Distance and RSSI reporting officially supported in the current SDK release? Are there any example projects or documentation that demonstrate how to retrieve RSSI during Channel Sounding measurements? The customer would like to compare traditional RSSI-based ranging with Channel Sounding distance measurements, so access to RSSI data is important for their evaluation. Any guidance would be greatly appreciated. Best regards, Mike WuSoftware-defined vehicleSYSCONFIGCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475860Tue, 08 Sep 2026 10:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:315fc4ef-5b02-428a-8dad-93a2fd6e3d52LeaThese C files are generated through SysConfig when building an example. How did you get your firmware ?https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1680271/cc2755p20-cc2755p207e0wrhar-programming-specifications/6475861Tue, 08 Sep 2026 10:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d894a495-22c4-4eb8-9736-c22c0ee5ffd8LeaHi, What exactly is it that you're trying to do ? What is your situation/flashing hardware at your disposal ? If you're using a XDS110, you can flash the HSM using UniFlash following this guide : https://dev.ti.com/tirex/content/simplelink_lowpower_f3_sdk_9_20_00_81/docs/ble5stack/ble_user_guide/html/cc23xx/hsm-programming-guide-cc27xx.html?highlight=hsm#the-hardware-security-module-hsm Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475857Tue, 08 Sep 2026 10:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d27bf65a-2095-41cb-a247-ba38953e85b2GURUKUMAR YADAV BAIRAGANICan you please share us the link where we can find that .c fileshttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680210/cc2340r5-does-the-fcfg-of-cc2340-can-be-erase/6475856Tue, 08 Sep 2026 10:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1fd3f4b4-c5ce-41d8-adae-032d1c5f2fecLeaHi ! Even if the customer tried really really hard, they could not erase the FCFG. It is programmed in the factory and is not editable in any way. Therefore there's 0 risk of the customer possibly erasing this part of flash, it will always be proctected. The technical reason behind it is because the register that holds the protection bits for the FCFG are sticky bits, which mean once set to 1/"protected", they can't be unprotected. The boot ROM will always set these bits to 1, therefore theres no way to unprotect and erase/modify the FCFG. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475854Tue, 08 Sep 2026 10:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4211639d-1375-4a8d-bb8d-b2026dad2e5cLeaHi ! The CCFG, SCFG and HSM are different regions of flash that are meant for different things : - The HSM is the Hardware Security Module Firmware. It's independent from your actual firmware. The firmware can be found in your SDK at C:\ti\simplelink_lowpower_f3_source_sdk_9_21_00_36_LTS\bin\hsm and can be flashed using UniFlash or using the hsmfwupdate example in the SDK. You can read more about the HSM here . - The CCFG and SCFG are configurations that are part of your customer's firmware. It contains information like boot configuration, permissions, etc .. You can read some of the fields of the CCFG and SCFG here . It's surprising that your CCFG and SCFG ranges are completely 0, how did you build your firmware ? If you're building with CCS, you'll be able to view the content of the ti_devices_config.c to see what is written to the CCFG and SCFG : Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1677838/cc1352p7-cc1352p7-sub-1g-proprietary-866-mhz-zigbee-2-4g-coordinator-in-one-binary-using-dmmsch-is-a-combined-rf-patch-available/6475812Tue, 08 Sep 2026 09:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2a67e650-196f-4abf-946e-d4d9bbeaf548nitish kareliyaHi Arthur Can you please guide us on this as our POC is getting delayed ? Regards, Nitishhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680307/cc2640r2f-unable-to-see-tmp117-data-outputTue, 08 Sep 2026 09:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:68cf410c-4c82-4784-aa31-25c1a5eb973bRatul KarPart Number: CC2640R2F Other Parts Discussed in Thread: TMP117 , , TIDA-01624 , TIDA-01580 , TMP117EVM , AFE4900 Hi Everyone, Recently I was working with the body temperature measurement sensor TMP117 and was trying to check the output while interfacing with CC2640R2F over I2C. It has been a few week i am trying to debug the issue where my ECG/PPG/SPo2 part are running well but while adding the body temp measurement unit we are unable to check the data in CCS itself. Can anyone confirm me that is CC2640R2F is compatible for working ECG/PPG/SPo2 and Body temp measurement all together where it will capture the data, process it and finally transmit it through BLE? Also if you have any references of the CCS project files that contain TMP117 implementation over I2C code it would be a great help. Please first confirm the question that i have highlighted above. This information is critical to me. Also Please do not say that TMP117 can be implemented with CC2640R2F kind of stuff because we know that beforehand through the TIDA-01624 and i have to write this question again because on my last thread over this forum the person told he will revert it to the CC2640R2F product support team but it has been 5 days and no replies. Thank you in advance for help me out to solve this issue. Regards, RatulTIDA-01580AFE4900TMP117EVMTMP117TIDA-01624CC2640R2FTest & Measurementhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1680302/cc3551e-ble-rx-le-1m-test-fail-on-the-ti-evm-lp-em-cc35x1-with-the-cc3551eTue, 08 Sep 2026 09:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4be78b3b-16f9-414f-b6b7-7e6f724d63b4Jesse WangPart Number: CC3551E Other Parts Discussed in Thread: LP-EM-CC35X1 Hi TI expert, We followed the "Simplified RF Testing Guide for CC33xx/CC35xxE" recommendations and performed the BLE RX LE 1M test with the CC3551E EVM board and the equipment LitePoint VSG. Test setup and results: (1). Open TI Radio Tool and configure the LP-EM-CC35X1 EVM for BLE RX testing. (2). In TI Radio Tool, click Calibration, and then click RX Start to start BLE RX mode. (3). We adjusted some parameters and gave tries as below: (a). Infinite Packet Receive is enabled on the TI Radio Tool. We start RX on the CC3551E first, and then start transmitting packets from the LitePoint VSG. (b). We aligned the Access Address between the TI Radio Tool and LitePoint VSG: *** If set TI Access Address = 8E89BED6, and LitePoint Sync Word = 8E89BED6 → The CC3551E can detect the packets, but they are counted as Received Not OK (nRxOk = 0, nRxNok > 0) packets. *** If set TI Access Address = 71764129, and LitePoint Sync Word = 71764129 → The CC3551E does not receive any packets (Received OK = 0, Received Not OK = 0). (c). Whitening is disabled on both the TI Radio Tool and LitePoint VSG. (d). We increased the LitePoint Repeat Time from 1 slot to 100 slots, but the result is still the same. We could not find a separate Packet Interval setting on the VSG WaveGen page. (e). We also used a lower VSG output level to make sure the CC3551E RX input was not saturated. The LitePoint waveform is based on 1LE_PRBS9.iqvsg. We generated 1LE_TEST.iqvsg by modifying the Sync Word/Access Address. From the LitePoint waveform configuration, we currently have: - Packet Type: LE - Sync Word: 0x8E89BED6 - PDU Type: ADV - CRC Init: 0x555555 - Whitening: OFF Could you please provide some advice on this issue? why the LE 1M can't be tested ok? 1. If 0x71764129 should be used for BLE_TEST packets, could you please provide the recommended LitePoint VSG packet settings or a reference waveform configuration? 2. Since 0x8E89BED6 allows the CC3551E to detect the packets, but all packets are reported as Received Not OK, could you please help confirm this issue? Thanks for your help. BR, Jesse.CC3551Ebuilding automationLP-EM-CC35X1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1680293/cc2745r10-q1-bluetooth-le-channel-sounding-supportTue, 08 Sep 2026 09:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:93529416-d130-4811-a8f5-efa0b2d58bbaBertram FONSECAPart Number: CC2745R10-Q1 Hello, For the CC27xx series, what level of support is currently available for Bluetooth LE Channel Sounding? Does TI provide a complete reference implementation, including the Channel Sounding procedure, PHY configuration, antenna switching, phase measurement, and distance calculation? Thankyou, BertramCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1680271/cc2755p20-cc2755p207e0wrhar-programming-specificationsTue, 08 Sep 2026 08:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:58dedc2a-868a-49f0-9758-f6ba4a29aa37GURUKUMAR YADAV BAIRAGANIPart Number: CC2755P20 Other Parts Discussed in Thread: UNIFLASH Hi Team, can you please provide us the programming sepcification for HSM range for CC2755P20 device and provide inputs on how to program the hsm range. Thanks! Gurukumar BUniFlashSoftware-defined vehicleCC2755P20https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676302/cc2755p20-cc2755p207e0wrhar/6475724Tue, 08 Sep 2026 08:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8abaa4ef-4594-4198-8ac4-18b531915dbfGURUKUMAR YADAV BAIRAGANIHello, Can you please provide inputs on how to program 96kb hsm range ?? does it same as main flash or its different ? Thanks!https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1677770/cc2745r10-cs-evm-syscfg-migration-fails-from-cc2745r10-to-cc2745r7-in-sdk-9_21_00_36_lts/6475707Tue, 08 Sep 2026 08:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:916466a4-ba3b-437c-b323-235c9bffce61Haiatullah GholamiHi, We have identified that the current SDK does not yet include the necessary support for migrating from CC27xxR10 to CC27xxR7. We are working to include this in a future release. In the meantime, you can enable this migration by replacing the four attached files within your existing SDK: source/ti/common/.meta/mcuboot/mcubootTemplate.syscfg.js source/ti/common/.meta/lprf_common.js source/ti/common/.meta/mcuboot_application.syscfg.js source/ti/common/.meta/mcuboot.syscfg.js Important Configuration Step : After replacing the files, you must import the example again and update the NVS Region Base to 0xBD000 in SysConfig (NVS -> Internal Flash -> Region Base). Best regards, HG e2e.ti.com/.../cc27xx_5F00_migration.zip