https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1671295/cc2745r7-q1-inquiry-about-abnormal-upgrade-of-cc27xxx10_hsm_fw_v3-4-5-bin-via-hsmfwupdateFri, 07 Aug 2026 03:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9a9beb30-fb26-4eba-b64b-4311c2c54294xing luPart Number: CC2745R7-Q1 hsmFwUpdate.c Hi Team, We would like to seek advice on a scenario concerning HSM firmware upgrades. The firmware in question is cc27xxx10_hsm_fw_v3.x.x.bin . Is there any possibility that, during the upgrade process using the hsmFwUpdate tool, an unexpected failure (e.g., interruption, checksum mismatch, or communication error) could render the HSM permanently unable to be upgraded again via any software-based method? This concern arises because we are currently considering deploying HSM firmware upgrades over OTA (Over‑The‑Air), and we are worried about potential irreversible consequences in case of an abnormal event.CC2745R7-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670028/cc2745r10-q1-how-to-choose-uart-interrupt-nvic-priority-relative-to-ble-stack-and-rtos-tasks/6443253Fri, 07 Aug 2026 01:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c638bf7e-ea24-4881-9ca2-ab5640fb6d7esnail leoHi TI team, gentle bump on this one as it&#39;s been a few days. I&#39;m still blocked on the NVIC described above. If there&#39;s any additional debug info (sniffer logs, peripheral register dumps, etc.) that would help speed up the investigation, please let me know. Thanks for your time.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1658913/cc2652p-does-it-back-off-from-20db-to-14db-sometimes/6442685Thu, 06 Aug 2026 16:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a70fe25d-768b-4a3a-a225-465a07fec53dJanHi Raphael, Apologies for the delay again. Looking into this with the HW team, I believe this is done to meet FCC requirements regarding PSD. I believe we need to update our documentation as that table does not mention this. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666457/cc2745r10-q1-guidance-on-adding-oad-support-to-channel-sounding-car_node-and-key_node-examples/6442574Thu, 06 Aug 2026 15:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ff9daac6-faac-4e9e-b3bf-4520c16f27d1Eshaan TibrewalaHello Vaibhav, Yes OAD is supported, but as Evan mentioned earlier, we usually see it with they key_node side. I have attached a guide that walks through how to integrate OAD with CC2745xx device into a basic_ble project, but the process should also work on car_node project. Please let me know if this works for you. Thank you. e2e.ti.com/.../Simplelink-F3-CC2745-OAD-Step-by-Step-Guide_2D00_v2_2D00_20260806_5F00_101536.pdfhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670582/cc2745r10-q1-cc2745r10-q1-the-primary-app-image-is-erased-after-a-dual-image-oad-update-with-xip-revert-enabled/6442403Thu, 06 Aug 2026 13:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:956f8eab-600a-48c1-95e9-1c5584d58e6bKevin QiuHi Weiting, This is related to downgrade prevention. Downgrade prevention is a feature which enforces that the new image must have a higher version/security counter number than the image it is replacing, thus preventing the malicious downgrading of the device to an older and possibly vulnerable version of its firmware. If alternate image security counter is greater than previous image, previous image will be erased. You can set the same security counter if hope to retain previous image in flash. Regards, Kevinhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670949/cc2340r5-follow-up-question-on-low-power-operation-with-48-mhz-crystal/6442350Thu, 06 Aug 2026 13:00:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a8e8449f-04d7-4239-8d60-bbe08ead0465ZCHi, Yes it is suitable but the specifics depend on your requirements. The crystal is used for operation of the radio, not the MCU. You can review Section 7.9 and Section 7.10 of the CC2340R5 datasheet for the power consumption figures: CC2340R5 Datasheet: https://www.ti.com/lit/SWRS272 Regards, Zackhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670949/cc2340r5-follow-up-question-on-low-power-operation-with-48-mhz-crystalThu, 06 Aug 2026 06:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bc612bf9-ab5e-4ec0-9dff-125609337a39AnkushPart Number: CC2340R5 Dear Team, Thank you for your clarification that the 48 MHz crystal is mandatory for BLE/radio operation and cannot be removed. I have one additional question regarding power consumption. Since the 48 MHz crystal is required, can I still use this hardware design for a low-power BLE application? Specifically, during sleep or standby modes, does the presence of the external 48 MHz crystal significantly increase the device&#39;s power consumption, or is it disabled when not required? I would appreciate your clarification on whether this design is suitable for achieving low-power operation.CC2340R5Connected peripherals &amp; printershttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1667963/cc2652r7-period-advertising-cmd_ble5_adv_per-never-fires-rf_eventlastcmddone/6441396Wed, 05 Aug 2026 20:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6bb27e6b-dd00-4132-b18a-e4ec943c333bKent HauserI have followed the guidelines in debugging-rf-output. But unfortunately, the PA/LNA is not exposed in the R7 part. I recently extracted the &quot;tester&quot; image from the SimpleLink 8.30 distribution and successfully tested periodic transmission and reception using the HCI commands exposed by that image. So I can say with certainty that the part is able to transmit and receive SYNC PDUs with arbitrary AA/CRC. I suspect that the SimpleLink implementation uses the ADV_AUX variants and somehow overrides the AA/CRC from the default &quot;Advertising&quot; values by utilizing the CMD_WRITE_FWPAR command described in TRM &#167;25.8.4. If you could provide the parameter addresses to modify or point me to the &quot;related documentation&quot; described in &#167;25.8.4, I would be glad to try that solution.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1669864/cc2744r7-q1-advertising-and-scanning-is-not-starting-channel-sounding/6441319Wed, 05 Aug 2026 19:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:648af853-0498-4347-a27f-34fb0746fb2eIsaac LarsonHello Vaibhav, Understood. The 6th question was to verify that advertising/scanning was not seen through the radio layer. Have you tested this on the newer SDKs (9.20 or 9.20.01)? I will work on replicating the problem you are seeing. Thanks, Isaachttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1668846/cc2662rq1-csu-evm-ble-terminated-due-to-unknown-reason-0x3e/6441106Wed, 05 Aug 2026 16:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c9adc921-8f35-43e8-a488-df0a0c744d7eTarek DHello Srivamsi, I couldn&#39;t find anything in the known issues or release notes that would indicate that this would be an issue, therefore I would like to replicate this on my end. Can you provide any replication steps? Should i just flash a simple_peripheral project onto the launchpad, connect to it, and monitor whether or not it disconnects due to a supervision timeout throughout the day? Please let me know if that&#39;s the case or if there are specific steps i need to follow to see this issue. Best Regards, Tarek Dhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1667963/cc2652r7-period-advertising-cmd_ble5_adv_per-never-fires-rf_eventlastcmddone/6440571Wed, 05 Aug 2026 09:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:af1f2a2d-cafb-4bf2-bdbf-0c70c2eac969LeaHi, After looking at the code for the SDK and the RF Core, the way periodic advertisement is done is that the CMD_BLE5_ADV_PER is chained to a CMD_COUNT command that points back to the original CMD_BLE5_ADV_PER command. Could you try if when set up like this you get callbacks, status updates and/or if the packets do send correctly over the air ? You could also try to enable the PA/LNA pins to see if anything is sent over the air when you send this command. You can see how to enable this here : https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_8_32_00_07/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#debugging-rf-output Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670582/cc2745r10-q1-cc2745r10-q1-the-primary-app-image-is-erased-after-a-dual-image-oad-update-with-xip-revert-enabledWed, 05 Aug 2026 08:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:23fb3cbd-d9b8-4fcc-ad54-79dd766125aaWeiting LiaoPart Number: CC2745R10-Q1 Other Parts Discussed in Thread: UNIFLASH Hi TI support team, Thank you for your support on my previous question . According to the information in the referenced post, I modified the settings for both the primary app and the secondary app projects. https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1635233/cc2745r10-q1-questions-about-oad-dual-image-project I was able to successfully perform a dual-image OAD using the SimpleLink Connect mobile app. After that, I checked the flash content using UniFlash. At that point, the primary app image was still present in flash. But I observed that the primary app image was erased after reboot. ( After OAD: The primary application image still exists in flash. ) ( After reboot: The primary application image is erased ) My syscfg settings are as follows. (Primary app) (Secondary app) Could you please explain why the primary application is erased after reboot when the update mode is set to XIP Revert Enabled ? Could you also advise how to resolve this issue? Thank you for your support. Best regards, WTUniFlashWireless InfrastructureCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1667963/cc2652r7-period-advertising-cmd_ble5_adv_per-never-fires-rf_eventlastcmddone/6440333Wed, 05 Aug 2026 06:17:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f0d9084e-fef9-43e9-b188-b2c335a39f73LeaHi, after asking around there is no documentation on the radio core, neither internal or external. I am still going through the code to try to find some indications, but this code is internal only so I cannot share it with you.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670488/cc2745r10-q1-guidance-required-for-aes-cmac-and-aes-ccm-on-cc2745r10Wed, 05 Aug 2026 04:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5077fa42-8ffc-4544-942d-6a11ada21cdcBalaji WankhedePart Number: CC2745R10-Q1 Other Parts Discussed in Thread: SYSCONFIG Hi Team, I am currently working with the CC2745R10 MCU using the following environment: SDK: simplelink_lowpower_f3_sdk_9_14_02_16 Code Composer Studio: 20.2.0 I am trying to implement AES-CMAC and AES-CCM encryption using the TI Secure Drivers. AES-CMAC I am able to initialize the driver successfully, but AESCMAC_oneStepSign() returns the following status: AESCMAC_STATUS_UNALIGNED_IO_NOT_SUPPORTED (-8) This corresponds to: /*! * @brief The operation does not support non-word-aligned input. * * AESCMAC driver implementations may have restrictions on the alignment of * input data due to performance limitations of the hardware. */ #define AESCMAC_STATUS_UNALIGNED_IO_NOT_SUPPORTED \ AES_STATUS_UNALIGNED_IO_NOT_SUPPORTED I have already aligned the key, input, and output buffers to 4-byte boundaries, but I am still unsure about the complete initialization sequence and whether there are any additional requirements for CC2745R10 when using AES-CMAC. AES-CCM I was able to get the SDK AES-CCM example working successfully. I noticed that the example for CC27xx devices uses: CryptoKeyPlaintextHSM_initKey() instead of: CryptoKeyPlaintext_initKey() which appears to use the HSM hardware accelerator. Could you please provide the recommended procedure for implementing AES-CMAC and AES-CCM on the CC2745R10? Specifically, I would appreciate guidance on: The correct initialization sequence for AES-CMAC. Whether CryptoKeyPlaintextHSM_initKey() should be used for AES-CMAC on CC27xx devices. Any mandatory buffer alignment or memory requirements. Whether there are any HSM-specific configuration or SysConfig settings required. A minimal working example for both AES-CMAC and AES-CCM on the CC2745R10. I have referred to the Secure Drivers documentation and examples, but I would appreciate confirmation of the recommended implementation flow for this device. Thank you for your support. Thanks &amp; regards Balaji WankhedeSYSCONFIGCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1669864/cc2744r7-q1-advertising-and-scanning-is-not-starting-channel-sounding/6440225Wed, 05 Aug 2026 04:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8fa29e85-4d51-48ff-a6dc-8d6bd94a3249Vaibhav PatilHi Isaac, Yes, I verified that the command is being received correctly, and the corresponding API is executed with a return status of 0x00 (SUCCESS). I have implemented a wrapper function outside app_car_node.c , which eventually transfers the control flow to the functions in app_car_node.c . When I issue the command to start advertising, the API returns 0x00 (SUCCESS). However, advertising does not actually start. If I issue the same command again, the API returns 0x11 . I don&#39;t believe the initial API call is unsuccessful, since it returns 0x00 (SUCCESS). I verify advertising using the nRF Connect Android application. For scanning, I verify that advertising reports are received by the application. Could you clarify the relevance of this check? Since advertising and scanning work correctly in some scenarios and only fail when triggered through my external UART commands, it seems the radio itself is functioning correctly. Wouldn&#39;t that indicate the issue lies elsewhere? Regards Vaibhavhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670454/cc2745r10-q1-cc2745r10-and-vivo-x300-cs-range-measurement-abnormal-interruption/6440147Wed, 05 Aug 2026 02:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:35b75e5e-12da-4b17-ab06-1dfc133c0cddUnderwood Frank[ 2026-07-07 18:52:28.067 ] [ 258930330 ] Count: 320 , Success: 320 , Fail: 0 , Confidence= 0 : 94 , Distance: 124 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:28.067 ] [ 2026-07-07 18:52:28.532 ] [ 259395713 ] Count: 321 , Success: 321 , Fail: 0 , Confidence= 0 : 95 , Distance: 134 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:28.532 ] [ 2026-07-07 18:52:29.069 ] [ 259932091 ] Count: 322 , Success: 322 , Fail: 0 , Confidence= 0 : 96 , Distance: 151 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:29.069 ] [ 2026-07-07 18:52:29.481 ] [ 260344067 ] Count: 323 , Success: 323 , Fail: 0 , Confidence= 0 : 97 , Distance: 168 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:29.481 ] [ 2026-07-07 18:52:29.995 ] [ 260858493 ] Count: 324 , Success: 324 , Fail: 0 , Confidence= 0 : 97 , Distance: 82 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:29.995 ] [ 2026-07-07 18:52:30.457 ] [ 261320187 ] Count: 325 , Success: 325 , Fail: 0 , Confidence= 0 : 98 , Distance: 14 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:30.457 ] [ 2026-07-07 18:52:30.994 ] [ 261856513 ] Count: 326 , Success: 326 , Fail: 0 , Confidence= 0 : 99 , Distance: 14 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:30.994 ] [ 2026-07-07 18:52:31.505 ] [ 262368883 ] Count: 327 , Success: 327 , Fail: 0 , Confidence= 0 : 100 , Distance: 125 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:31.505 ] [ 2026-07-07 18:52:31.919 ] [ 262781646 ] Count: 328 , Success: 328 , Fail: 0 , Confidence= 0 : 101 , Distance: 167 , Quality: 0 , Vel: 0 . 000000 , Confidence: 0 [ 2026-07-07 18:52:31.919 ] [ 2026-07-07 18:52:32.063 ] [ 262928064 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:32.063 ] [ 2026-07-07 18:52:32.551 ] [ 263415568 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:32.551 ] [ 2026-07-07 18:52:32.699 ] [ 263550229 ] 263550228 : CS_Failed, status: 22 [ 2026-07-07 18:52:32.699 ] [ 263550890 ] Procedure ended: 22 [ 2026-07-07 18:52:32.699 ] [ 263551374 ] Ready Procedure Restart: 22 [ 2026-07-07 18:52:32.699 ] [ 263552292 ] 263552292 : CS_procedureStart, status: 0 [ 2026-07-07 18:52:32.699 ] [ 263553032 ] Call Procedure Restart: 0 [ 2026-07-07 18:52:32.699 ] [ 2026-07-07 18:52:33.039 ] [ 263903073 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:33.039 ] [ 2026-07-07 18:52:33.272 ] [ 264136589 ] Failed status: 13 [ 2026-07-07 18:52:33.272 ] [ 2026-07-07 18:52:33.526 ] [ 264390581 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:33.526 ] [ 2026-07-07 18:52:33.683 ] [ 264525243 ] 264525243 : CS_Failed, status: 22 [ 2026-07-07 18:52:33.683 ] [ 264525904 ] Procedure ended: 22 [ 2026-07-07 18:52:33.683 ] [ 264526389 ] Ready Procedure Restart: 22 [ 2026-07-07 18:52:33.683 ] [ 264527309 ] 264527308 : CS_procedureStart, status: 0 [ 2026-07-07 18:52:33.683 ] [ 264528048 ] Call Procedure Restart: 0 [ 2026-07-07 18:52:33.683 ] [ 2026-07-07 18:52:34.743 ] [ 264878083 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:34.743 ] [ 265365587 ] subevent: procedure abort reason: 32 [ 2026-07-07 18:52:34.743 ] [ 265502292 ] 265502292 : CS_Failed, status: 22 [ 2026-07-07 18:52:34.743 ] [ 265502954 ] Procedure ended: 22 [ 2026-07-07 18:52:34.743 ] [ 265503500 ] Ready Procedure Restart: 22 [ 2026-07-07 18:52:34.743 ] [ 265504506 ] 265504506 : CS_procedureStart, status: 0 [ 2026-07-07 18:52:34.743 ] [ 265505552 ] Call Procedure Restart: 0 [ 2026-07-07 18:52:34.743 ] [ 265599118 ] Failed status: 13https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670454/cc2745r10-q1-cc2745r10-and-vivo-x300-cs-range-measurement-abnormal-interruptionWed, 05 Aug 2026 02:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:25bf8d07-9913-4857-9e83-3930e17ea4f7Underwood FrankPart Number: CC2745R10-Q1 TI technical support, Hello! I recently used the latest lopower f3 SDK 9.20.1.21 on the CC2745R10 chip to perform CS ranging with the Vivo X300 phone, and found that the ranging would terminate abnormally after a period of time. Specifically manifested as: The normal ranging operation lasted for about 1 minute, but the CS process was suddenly terminated abnormally. Before the termination, there were two procedure abort situations, and the abort reason was 0x20. I checked the description of 0x20 and it was no CS_SYNC received. This problem is inevitable. I want to know if the reason for this problem is due to the strategy of the handheld device or an abnormal situation?Software-defined vehicleCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1670038/cc2640r2f-q1-how-can-i-get-access-to-sdk/6440120Wed, 05 Aug 2026 02:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:df50ecda-9656-4681-b13b-238cd6a783a2Island WeiEvan, yes I tried to download SDK with this link, after log-in and get access to the files, the page shows 404. Me and customer both have this issue. could you please check the link?https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1669864/cc2744r7-q1-advertising-and-scanning-is-not-starting-channel-sounding/6439882Tue, 04 Aug 2026 21:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2924c191-8a4b-4f49-a3e4-558d54e6db80Isaac LarsonHello Vaibhav, 1. Have you verified the UART commands are being received properly? 2. Also, can you let me know where you are calling the adv/scan start API from? 3. What do you mean by issue the command again? 4. Do you mean you unsuccessfully call adv/scan start, then try to start adv/scan again? 5. How are you verifying that adv/scan is not working? 6. Can you output the PA/LNA and send a waveform capture of this when the problem occurs? You can do this within RCL -&gt; RCL Observables -&gt; Use Case -&gt; Select PA/LNA Pins. Please provide a response to these comments. I will look into testing when I receive these answers. Thanks, Isaachttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1664235/cc2340r5moda-unexpected-configuration-appears-cpuirq0sel/6439815Tue, 04 Aug 2026 20:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f797a15a-6109-4e31-81f5-4abd6e7452e0Alex FagerHello Roeland Benoot, Thank you for your update and feedback. Using your own user bootloader (user bootloader setting in sysconfig) here should work as it should not call the serial bootloader when you configure it correctly in sysconfig. Thanks, Alex F