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/1647490/cc2652r7-zephyr-reboot-not-working/6364914Sun, 31 May 2026 09:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:956db717-6908-4b94-93cd-37e625c5a34bKent HauserPicking up on Mike and Ging&#39;s exchange — that answer is not helpful for the CC2652R7 LaunchPad. The XDS110 is hardwired to the chip&#39;s cJTAG pins on the board, so there is no free-running mode out of the box. I&#39;m using an external J-Link in place of the onboard XDS110, but the chip sees a cJTAG-initialized debug subsystem regardless of which probe drives it. I&#39;m trying to implement the `sys_reset(...)` reboot for zephyr. I have been trying various incantations in an override the cortex-M default (` NVIC_SystemReset()`) in &#39;soc&#39; for the part, but have had no success getting the &quot;reboot&quot; actually working. So after working the problem and have four followup questions: 1. Is the &quot;reset API only on a free-running device&quot; stance also the contract on CC2652R7? And where is it documented? I couldn&#39;t find it in the SimpleLink SDK docs, or SimpleLink Academy. 2. If it is the contract, what is the supported software sequence on a CC2652R7 LaunchPad — where the XDS110 is hardwired to the chip&#39;s cJTAG pins on the board — to put the chip into &quot;free running&quot; state from the application&#39;s own code before calling `sys_reboot`? Is there a driverlib call, a register write (`AON_PMCTL.JTAGCFG`?), or a debug-subsystem disable bit that the application can issue on-chip so ROM treats itself as &quot;no debugger present&quot;? 3. Is `TrimAfterColdReset` known to hang or busy-spin when entered from a software warm reset with debugger attached? That&#39;s what my trace points to; an errata reference or known-issue acknowledgment would close this out. 4. If there is no such on-chip API, knowing that would help. Still hoping for the Zephyr expert Jan mentioned at the top of the thread. Thanks for any pointers.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1645653/cc2755p10-step-by-step-how-to-measure-rssi-in-smart-rf-studio-8/6364642Fri, 29 May 2026 20:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:44c7b740-4528-47ad-9eb8-2c3b9eb2ebfaBailey Loopere2e.ti.com/.../RSSI-Measurement-Guide.docx Inserting this for anyone who finds this thread and needs the guide.https://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_8/6364557Fri, 29 May 2026 19:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:aa5ea941-c14f-4d83-9bd3-45fced938f4dEshaan Tibrewalae2e.ti.com/.../app_5F00_extctrl_5F00_cs.h e2e.ti.com/.../app_5F00_cs_5F00_process_5F00_api.h e2e.ti.com/.../app_5F00_cs_5F00_api.h e2e.ti.com/.../app_5F00_extctrl_5F00_cs.c e2e.ti.com/.../app_5F00_car_5F00_node.c e2e.ti.com/.../app_5F00_cs_5F00_process.c Hello Pallavi, I have attached 6 files above, please replace the ones in your workspace with these of the same name. This should fix the python issue and enable stepsIdxChnlMap on external side. I essentially had to connect the signal from the application side to the external control. 1. Yes, you are correct. stepsToChnlMap collects the local steps indices to the channel numbers. 2. I believe they are in order of acquisition order (so Mode 0 steps and then Mode 2 steps). Please let me know if you are able to configure the python script as expected now. Thanks.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643693/cc2745r10-q1-how-to-perform-cs-range-test/6364547Fri, 29 May 2026 19:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a5e0f36b-d09e-4548-a5af-3dcd1dcc8da9Isaac LarsonLinus, To setup the channel sounding demo you can follow the Channel Sounding Documentation . I am not sure what you are setting up. The car node project must&#39;ve been customized to automatically output the RSSI for each connection event. Additionally, I will assume then you have the car node and key node projects configured to 10dBm then. The distance that BLE can support depends on the txPower, the PHY, RX sensitivity, environment and the antenna. You can reference the range calculator from Bluetooth SIG to get an estimate on the expected range. Thanks, Isaachttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1629212/dlpc4420aevm-connection-issue-on-dlpc4420aevm-so-513588/6364337Fri, 29 May 2026 16:00:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5a94b15b-bb25-4308-8d65-a74065232170Bhavan LHi Lucas, We will try to setup a similar hardware on our side and try to reproduce this issue to debug this. Will give you an update and the latest firmware that you requested for by Monday. Regards. Bhavan Lhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650698/cc2745p10-q1-feature-request-add-generation-of-dtsi-in-sysconfig-tool-to-support-zephyr-designsFri, 29 May 2026 15:42:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7a297edd-2b2b-495e-b85a-18110d381558Mike CrowePart Number: CC2745P10-Q1 Other Parts Discussed in Thread: SYSCONFIG Hello Maybe this feature exists, but I was unable to exersise it. I am porting a Zephyr BLE mesh applictation to a new board. Part of this process requires a .dts and/or a .dtsi file based on the SOC configuration information found in the TI .sysconf file. I found that sysconfig tool generates a .dtsi file for some products/configurations but not others. Can this feature be added? If the feature already exists, I wasn&#39;t able to use it for the cc2745 with the online tool, or installed versions 1.18.0, 1.23.2 or 1.27.0. Alternativly, is there a stand alone command line tool that might suitable to migrate a .sysconf to a .dts(i)? Cheers MikeSYSCONFIGCC2745P10-Q1Test &amp; Measurementhttps://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_8/6364097Fri, 29 May 2026 12:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e2122311-86fa-482e-9942-3354a5c95840Pallavi ArageHi Eshaan, Yes, we need stepsIdxToChnlMap (1) Can you confirm my understanding regarding it. My understanding : it basically tells the order in which the channel appeared while executing CS procedures For example if stepsIdxToChnlMap is [44, 25, 4], then it means on step 0 channel 44 appeared , on step 1 ch 25 appeared and so on. (2) Second, regarding the local results and remote results in the function csProcess_CalcResults, ( gCsProcessDb . initPathsData ; gCsProcessDb . refPathsData ; ) are they arranged in channel order(ch0 iq data, ch1 iq data ch2 iq data ...) or as per acquisation order (that is mentioned in stepsIdxToChnlMap)https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650593/cc2340r5-cc2340r5-ble-mtu-size-300-bytes-support/6364004Fri, 29 May 2026 11:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5ad5e506-c79a-46b8-ac34-47f7b5b56d84LeaHi ! As you correctly mentionned, our BLE controller on the CC2340R53 has a max MTU size of 251. Unfortunately it is not possible to reach 300 bytes of MTU. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650593/cc2340r5-cc2340r5-ble-mtu-size-300-bytes-supportFri, 29 May 2026 10:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0e5a75a0-2c4e-40b2-8b21-8aadd191e3d8Akhil JosephPart Number: CC2340R5 Hi TI Team, I am working with the CC2340R5 BLE stack and would like to know whether it is possible to configure or negotiate an ATT MTU size more than 255 - L2CAP_HDR_SIZE bytes. Thanks.Infotainment &amp; ClusterCC2340R5https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1648351/cc2745r7-q1-feasibility-of-integrating-ota-ancs-ams-nordic-uart-service-channel-sounding-and-can-bus-on-ti-cc2745r7-q1/6363942Fri, 29 May 2026 10:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:efe82233-dfd7-441c-b2f0-741c583aa80aMike Wu1Hi Evan, Thanks for the recommendation. Currently, we are developing a project based on the CC2755R10-Q1 EVM (with the ultimate target being the CC2745R7-Q1), and we have already implemented the following features: Apple ANCS &amp; AMS Nordic UART Service Profile Dual-image OAD (Over-the-Air Download) CAN BUS / CAN-FD Communication&lt;---on-going Our plan is to have the customer run the full suite of functions on this EVM to precisely evaluate the actual Flash/RAM consumption, especially once they decide to use Channel Sounding. If we find that more memory is required, we will definitely reach out to our local sales or marketing team to discuss the upcoming roadmap offline. Thanks again for your support. Best regards, Mikehttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1648770/cc2642r-fw-write-fails-on-reset/6363848Fri, 29 May 2026 09:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5e373a99-a8fb-4f02-8c08-2970e18562ffLeaHi ! Just to clarify, when you say that you don&#39;t have a debugger, do you mean that the only way you&#39;ve been flashing firmware into the chip has been through the bootloader backdoor ? The command input you are sending in the 2nd image seems to be much larger than the one in the first image, especially considering the time scale. Can you zoom in and see what is it that you are sending on your CPU Rx line in both cases ? Because perhaps the data sent is invalid. I also see spikes on the CPU Tx line in the second image, are those measurement errors ? It looks like the chip does reply to your command input. It may reply with a useful error code, so it would be useful to zoom in right on the command input part. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650139/cc2340r5-ble-device-reconfigured-as-central-for-the-application/6363819Fri, 29 May 2026 08:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d5782ce8-7dfb-4855-a726-9645ced6707dLeaHi, According to the following thread : CC2340R2: Using LFOSC instead of an external 32k crystal we do not have any software workaround to have the central role when using LFOSC. I don&#39;t think that we have made any estimation of the percentage of occurrence of issue in the central role when using LFOSC, as TI officially does not support this and recommends to use the 32kHZ crystal. You can try this by yourself, run a basic_ble example in central role with LFOSC configured in SysConfig, start a connection on your phone, and run stability measurements like this. You can try to play around with values such as the connection timeout, peripheral latency and connection interval to see if you get to a point that is good enough for you. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650139/cc2340r5-ble-device-reconfigured-as-central-for-the-application/6363532Fri, 29 May 2026 04:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2b29bff8-9058-4cb7-a24f-95eeb8b27220Abhinav KumarHi Lea, Is there any other software workaround which I can implement to handle this, since I previously mentioned that I don&#39;t have the timeline or liberty to change the child card design. If not, I want to know the percentage of occurrence observed for random disconnections during your testing and validation. This data will help me to take an informed decision.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1648770/cc2642r-fw-write-fails-on-reset/6363476Fri, 29 May 2026 03:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:197afc85-8171-4f0b-adca-431f60bc76fcShuhei YamaguchiDear Lea-san, I don&#39;t have debugger. I&#39;ll consider to buy it. By the way, I measured UART waveform when FW was being updated. CC2642R on my board is connected to CPU by UART (level shifter is used). And FW update command is input via the CPU. Actually, there are 2 type of board. One succeeded in writing FW smoothly (1st time sample). Another failed to writing FW first, but succeeded in writing FW second time (2nd time sample) When FW update command was input, CPU on 1st time sample sometimes received CC2642R responces (CPU Rx=blue waveform). But CPU on 2nd time sample didn&#39;t receive CC2642R responses. HW design is same. So, I don&#39;t know why the result was different. Is there anything that comes to mind? Best regards, Yamaguchihttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1647490/cc2652r7-zephyr-reboot-not-working/6363121Thu, 28 May 2026 20:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7f86c9cc-bc9f-4f04-b08a-d00041b22cf6Ging GonzalezHi Mike, Thanks for reporting that back. The behavior that you see is expected. The reset API should only be done on a free running device (not in debug mode). Regards, Ginghttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1648647/cc2340r2-att_read_rsp-with-0-byte-payload/6362525Thu, 28 May 2026 13:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5d6a799e-cd60-4305-bcba-3da39334f9afLukeHey Jan, Good news. They realized there was an issue in building their code as we were debugging this issue – some of the updated files were not being built. Once fixed, they were able to see the BLE stack was passing the event with the payload length equal to their application. So adding code to check payload length fixed the issue. Thanks for the support, Lukehttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650139/cc2340r5-ble-device-reconfigured-as-central-for-the-application/6362389Thu, 28 May 2026 11:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:cf5ebd2d-f16a-4547-b2fa-d647c4705055LeaHi ! As the CLK_01 errata you shared mention, if you do not have an external low frequency crystal, you will face issues while using the central role, such as random disconnections due to devices missing the communication window. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1643145/cc2340r5-q1-scanning-with-empty-whitelist/6362341Thu, 28 May 2026 11:08:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:16f78b72-61b6-45f8-89e6-68ac6b414435Rahul Chowdary PinnakaHello Team, Can you please provide update on this query ?https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1650257/cc2340r5-q1-auto-connect-to-peripheral-in-central-roleThu, 28 May 2026 11:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6e9e8db1-0f3d-4498-8731-960e00ebbf30Rahul Chowdary PinnakaPart Number: CC2340R5-Q1 Hi Team, I am using CC2340R53 chip with simplelink_lowpower_f3_sdk_9_12_00_19, and I have a query related to automatic connection establishment with bonded peripheral device when my device is in central role. My research says it might be possible to achieve this by using the API GapInit_connect() by passing peer address parameter as NULL. I am looking for more details here. I don&#39;t see any such implementation in the app_central.c or app_menu.c files in the basic_ble example in the SDK. If possibility exists, please explain me clearly how to achieve auto connection using GapInit_connect() (or) other possiblity with a bonded device in central role. If possible to achieve auto connection using GapInit_connect(), would it be not needed to GapScan_Enable() beforehand ? If no, what default scan parameters would GapInit_connect() internally uses to scan for advertisement before initiating auto CONNECT_REQ to bonded devices ? Please provide detailed answers. Thanks a lot. Regards RahulCC2340R5-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1648770/cc2642r-fw-write-fails-on-reset/6362138Thu, 28 May 2026 08:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:cd9551aa-cccb-4bba-bbd0-35975e64d3b1LeaHi ! About detecting if the chip has woken up properly, you can try attaching a debugger to the chip while it is running. If you&#39;re able to attach and read registers, then you know that your chip is awake. Reading the PC address will also allow you to see if you are in the ROM or the Flash. Kind regards, Lea