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/1640054/cc2745r10-q1-power-control-in-sysconfig/6338567Fri, 08 May 2026 19:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5f927b2e-838e-42de-b8f4-c2d8ebebc853Barbara WuHi Yasukane, For HCI_LE_EnhancedReadTransmitPowerLevelCmd and HCI_LE_SETTransmitPowerReportingEnabledCmd, the feedback is under HCI_COMMAND_COMPLETE_EVENT_CODE. Example looks like: // 1. Call it (e.g., after connection established) HCI_LE_EnhancedReadTransmitPowerLevelCmd(connHandle, HCI_PHY_1_MBPS); // 2. Handle result in your GAP event processor case HCI_COMMAND_COMPLETE_EVENT_CODE: { hciEvt_CmdComplete_t *pkt = (hciEvt_CmdComplete_t *)pMsg; if (pkt-&gt;cmdOpcode == HCI_LE_ENHANCED_READ_TRANSMIT_POWER_LEVEL) { uint8_t status = pkt-&gt;pReturnParam[0]; int8_t curPower = (int8_t)pkt-&gt;pReturnParam[4]; int8_t maxPower = (int8_t)pkt-&gt;pReturnParam[5]; } } For HCI_LE_ReadRemoteTransmitPowerLevelCmd and HCI_EXT_SendPowerControlRequestCmd, the feedback is under HCI_COMMAND_STATUS_EVENT_CODE. Example looks like: // 1. Call HCI_EXT_SendPowerControlRequestCmd(connHandle, HCI_PHY_1_MBPS, -5, 1); // 2. Only a CommandStatus comes back case HCI_COMMAND_STATUS_EVENT_CODE: { hciEvt_CommandStatus_t *pkt = (hciEvt_CommandStatus_t *)pMsg; if (pkt-&gt;cmdOpcode == HCI_EXT_SEND_POWER_CONTROL_REQUEST) // 0xFC7C { // pkt-&gt;cmdStatus } } Best Regards, Barbara Wuhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1633438/cc2340r5-q1-updating-notification-data/6338539Fri, 08 May 2026 19:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:626446da-a4eb-4b82-aa6e-39c8f7650eaaBarbara WuHi hrkunied, Seems here, keep sending 0x00, 0x01, 0x02, 0x03 in sequence. Then if only want to send 0x03, then only set the myCharValue as 0x03 could meet the requriement. Something like: // Set the value to 0x03 once myCharValue = 0x03; // For notifications: just call it on a timer or whenever needed GATTServApp_ProcessCharCfg(myCharCfgTable, &amp;myCharValue, FALSE, myAttrTable, numAttrs, taskId, myReadAttrCB); Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1639997/cc2745r10-q1-secure-boot-bootup-sequence/6338509Fri, 08 May 2026 18:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5f46bac6-0e14-4934-a9e0-9db43b04a34aBarbara WuHi Abhirami, MCUBoot is an open source project that supports hardware-independent secure bootloader for 32-bit MCUs. Please refer to MCUboot | mcuboot for document. Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1632947/cc2340r5-implementation-advice-for-intercepting-ble-pairing-request-on-ti-cc2340/6338345Fri, 08 May 2026 16:33:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6c250b6e-f15a-49d4-84d8-6232c9b57d3cMike Wu1Hi Jan, I would greatly appreciate any guidance or comment on this thread. Thank you so much for your time and continuous support! Best Regards, Mikehttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1642100/cc2745r10-q1-on-chip-oad-device-not-broadcasting-not-found-by-simplelink-connect/6338313Fri, 08 May 2026 16:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3ceff218-b1e5-4139-b060-626e6003ef33Mike Wu1Hi Josh, Thanks for your help. The dual-image OAD is now working correctly. We have also successfully updated the firmware using Simple Connect on an iOS device. My customer is currently integrating ANCS/AMS with the dual-image OAD example code. We will start to run our plan to check if anything goes wrong. Thanks again for your support!https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643007/cc2652p-what-is-sdaa-for-can-we-use-it-to-optimize-our-connection/6338257Fri, 08 May 2026 15:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ce0c4be4-7f12-46ea-9cfa-679b1ac78293Raphael FischerHi David, Thank you very much for your detailed answer! I have some more questions: - As long as we stay within the recommended ranges of the parameters, do we stay compliant with the regulations? - Is there any documentation on this feature and on the configuration possibilities? We didn&#39;t find anything - I imagine it roughly works like this: Before transmitting on a channel, it listens on it. If the received signal is above the SDAA_RSSI_THRESHOLD for enough samples, it will skip this channel for a while. If this is true, decreasing SDA_RSSI_THRESHOLD to -90 would actually make it more sensitive to noise and block channels quicker, right? Shouldn&#39;t we then rather increase it to -40 or so if we already increase the noisiness through coded-phy? - How can we even change those configurations? I guess we have to define ICALL_STACK0_ADDR and SDAA_ENABLE and then define the parameters we want to change...? But what are the other effects of defining ICALL_STACK0_ADDR? Thank you very much for your help! Kind regards, Raphaelhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643693/cc2745r10-q1-how-to-perform-cs-range-test/6338225Fri, 08 May 2026 15:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:abf087ed-1e6b-408b-b9f9-da9f6c4f9191Isaac LarsonHello Jerry, First, the video uses the CC2745R10-Q1 Launchpad with a multiple antenna booster pack. We are not providing boosterpacks in the future, and will switch to a channel sounding specific EVM, which is not fully released yet. Second, the customer should determine what their use case is. What location the car node is in, where they worry about the key fob being most, what distance they would want to unlock at, what the maximum distance they would like to range, and what situations the customer is most interested in testing. Third, make sure you are taking the step measurements from the car node. For instance, if the car node is on the rearview mirror, you will need to account for the ~1m before the front of the car. Fourth, I would recommend 1m steps, with 100 samples per step, but this is up to the customer. Let me know if this helps. Thanks, Isaachttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643923/cc2745r10-q1-unable-to-get-raw-data-from-ble-agent-in-new-cc2745-sdk-simplelink_lowpower_f3_sdk_9_20_00_8Fri, 08 May 2026 12:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:07ef3a08-86b5-41af-8133-276ba19a68e7Pallavi AragePart Number: CC2745R10-Q1 Hi TI Support Team, SDK Version: 9_20_00_81 Board Details: CC2745R10-Q1 LaunchPad CCS Version: 20.5.0.28__1.11.0 I am currently evaluating the newly released SDK for the CC2745R10-Q1 LaunchPad using the Car Node and Key Node examples along with the BLE Agent Python tools provided in the SDK. I have followed all requirements, setup steps, and configurations mentioned in the provided requirements text files for both the SDK examples and BLE Agent setup. The procedure configuration and enable sequence appear to execute successfully. However, I am unable to receive the expected raw distance/ranging data from the BLE Agent. Below is the observed console output during execution: Procedure Enable successful Waiting for NWP_CS_APP_DISTANCE_EXTENDED_RESULTS Message received: No NWP_CS_APP_DISTANCE_EXTENDED_RESULTS event received The procedure repeatedly starts again, but no extended distance results or raw measurement data are received. Could you please help clarify the following: Are there any additional configurations required to enable extended/raw ranging results? Has the event/data flow changed compared to previous SDK versions? Are there any known limitations or additional steps required in the current SDK release for accessing raw ranging data? Your guidance would be greatly appreciated. Thank you.CC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643792/cc2340r5-faultisr-on-cc234r5/6337981Fri, 08 May 2026 11:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:34b9da09-5af8-4cda-be5c-492e18cd6dbcRyan Brown1Hi Sandeep, Have you already reviewed the BLE5-Stack Debugging Guide ? Would you be able to add your central based application in increments to determine what part causes the faultISR? Please try to further quantify the instances/environment which causes the error to occur. It may also be worth further investigating your memory allocations to the heap/stack to make sure no overflows are taking place. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1616441/cc2340r5-mtu-and-pdu-size-issues-with-latest-f3-stack/6337933Fri, 08 May 2026 10:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6ec36357-6b0a-4018-9309-05e9d9fd5d09Robert WeeklyHi Lea, Okay, this is where I have managed to get to. Using the 9.12.00.19 SDK, I have managed to build a peripheral device that now achieves the long packets on Read and Write. However this only works with a PHONE running as the connecting central. When I use a Central Device running CC2340R5 Dev board, I continue to have the issue in one direction, so really unsure what is going on with that. The MTU updates and LL exchanges seem similar to when the PHONE is the central. From there, I&#39;ve managed to regenerate our APP based on the 9.12.00.19 SDK and again prove through the bigger transfers, so all good. Just spotted new release 9.20.00.81 has dropped. So I will be moving to that and checking its a final solution. Moving in house project work between stack on IAR is a real headache, I cannot just reference the new stack - and generally have to build up again from the BLE Demo app. Wondering if there any intention from TI&#39;s side to create BIN library files for the Stack instead of all the source files? Anyway, will rebuild with 9.20.00.81 and let you know how it goes. As for why my 9.12.00.19 Central still does fragmented Writes, I just don&#39;t know. All the best Robhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643007/cc2652p-what-is-sdaa-for-can-we-use-it-to-optimize-our-connection/6337786Fri, 08 May 2026 08:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b890fa4b-3979-4a75-89b3-70f69a0cfbe7DavidHello Raphael, SDAA (Selective Detect and Avoid) is a regulatory compliance mechanism, design to meet EN 300 328 (ETSI Standard for 2.4 GHz Wide band Transmitters), which requires that devices using non-FHSS modes implement adaptativity, meaning that busy channels must be detected to avoid transmitting on them excessively. I think for your long range coded PHY, it might hurt in the long run because this one uses effectively x8 more airtime than the others, overloading quicker the channels and therefore &quot;blocking&quot; them quicker for usage. Especially if you are using the default parameters. For example, with the SDAA_RSSI_THRESHOLD of -70 dB which in long range is expected to reach quickly, SDAA will interpret your own weak signal reflections or interference as channel noise and block the channels. You can try tuning the parameters and test with them. For example, reducing the SDAA_RSSI_THRESHOLD to -90 dBm, increasing SDAA_MAX_THRESHOLD to 10%-20%, increasing SDAA_MAX_ALLOWED_NOISY_SAMPLES to 3-5 and increasing SDAA_OBSERVATION_TIME to 500ms-1sec to have longer windows can be a good start to test. Hope it helps. David.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643792/cc2340r5-faultisr-on-cc234r5Fri, 08 May 2026 07:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b29f62de-2fcd-4234-8d46-6d61ed08d864Sandeep SinghPart Number: CC2340R5 Hi Team, SDK used: 9_20_00_81 Chipset: CC2340R53 We have taken CC2340R5 &#39;s basis_ble example code as a base and have written a central based application on to it. The application for the most part runs smoothly without any issues but under certain random instances we see that the device goes into faultISR Handler. I have checked the PC and LR as well but I am not able to extrpolate anything from it. PC points to the while(1) present in the faultISR and LR contains a junk address. Other than the above two registers, Can TI suggest what must we look at to figure out what the cause of the fault is? Unlike cortex M3 &amp; M4 we do not have a various registers to isolate the cause of the fault. Kindly help us understand how we can debug faultISR related issues. Thanks and regards, SandeepCC2340R5https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1639997/cc2745r10-q1-secure-boot-bootup-sequence/6337680Fri, 08 May 2026 07:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ef45d236-6e82-4c74-965d-804f3cf05ed7Abhirami KHello, While I can look into porting the code, is there an alternative method to do this? (For example, setting certain fields in ccfg or scfg)https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643226/cc2745r10-q1-is-there-a-way-to-set-the-transmission-output-level-for-each-channel/6337480Fri, 08 May 2026 04:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d426347e-98e5-4db7-aac9-bdeee6b3cfc2Yasukane YamanakaThank you for your reply. Since radiation may be having an effect, I’ll take another look at the measurement environment. By the way, (though this is similar to my very first question), am I correct in understanding that the BLE stack does not automatically adjust the transmission power for each channel?https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1641771/cc2745r10-q1-connect-monitor-sync-data-and-cfg/6337392Fri, 08 May 2026 03:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ed6dcf08-8275-44ec-9e18-9090cee3fecfsnail leosequential timing requirement is here： This must be done before advertising (for the Peripheral) or before initiating (for the Central). Channel Selection Algorithm #2 — SimpleLink ™ Low Power F3 SDK BLE5-Stack User&#39;s Guide 9.20.00 documentationhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643226/cc2745r10-q1-is-there-a-way-to-set-the-transmission-output-level-for-each-channel/6337352Fri, 08 May 2026 02:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d5c7a059-4bf8-4feb-9c04-76c798ba9963Evan WBest way to narrow that down is to run a test in a conducted manner versus radiated to eliminate variables of your environment.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643693/cc2745r10-q1-how-to-perform-cs-range-testFri, 08 May 2026 01:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2ae7b6fd-9428-4ff3-8268-15f434dfde42Jerry KuoPart Number: CC2745R10-Q1 Hi team, Customer want to do Channel Sounding range test like below. They ask for any SOP or suggestion about how to do such test. Thank you.Body Electronics &amp; LightingCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643226/cc2745r10-q1-is-there-a-way-to-set-the-transmission-output-level-for-each-channel/6337216Thu, 07 May 2026 23:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:40ad3ac0-aeb1-4ed8-8f5d-c4b7f3e251b6Yasukane YamanakaHi Evan, Thank you for your response. I understand that it is not available. &gt; What would be the purpose out of curiousity? We created a BLE board using the CC2745R10 and conducted measurements in an anechoic chamber, but we frequently observed a drop in the RSSI value on a specific channel. That is why we wanted to know if it is possible to adjust (or configure) the transmission power for each channel. It does not appear that the RSSI drop occurs on a specific channel every time. Furthermore, it does not seem to occur consistently. Therefore, we believe it is entirely possible that our testing environment is the cause.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1626007/launchxl-cc26x2r1-gapinit_connect-times-out-targeting-rpa-during-directed-advertising-with-addrmode_rp_with_random_id-oob-irk/6336935Thu, 07 May 2026 19:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0e9b014d-8526-4a79-9a70-d3f77509876bJosh AldersonHello Marco, I reviewed my last comment and I realized that the wording was confusing and incomplete. According the BLE spec directed advertising with privacy is possible: 6.2.2. Connectable directed event type 6.4. Privacy in the Initiating state The issue seems to stem more from RPA mismatch at the filter level of the code. Earlier you mentioned that you are using a whitelist and if the filtering policy is set to SCAN_FLT_POLICY_WL then it could have issues with the RPA and filter out the directed advertising. This filter policy will check that each RPA matches exactly, but it would fail due to the RPAs being generated with different random data as mentioned above. To allow the device to attempt to resolve the RPA (which should work) it would require the filter policy to be SCAN_FLT_POLICY_WL_RPA. Please check what whitelist filter policy you are using. For your situation it should be SCAN_FLT_POLICY_WL_RPA. If it is not please update it and try again. For more information regarding the filtering policies please look at TI BLE5-Stack API Documentation: GapScan Structures Please look into this and let me know what you find. Best, Josh Aldersonhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1641771/cc2745r10-q1-connect-monitor-sync-data-and-cfg/6336339Thu, 07 May 2026 12:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:930cebfc-e8bb-43bb-b97c-12f845e4aa17Isaac LarsonHello, Can you elaborate on what you mean by sequential timing requirement relating to the function? Yes, the features need to be set at chip start up. This is done already within the stack using SysConfig, but if you want to alter the feature set, you will need to do this during chip startup. Thanks, Isaac