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/1652445/cc2652r-ble-cc2652r1-sdk-8-30-8-31-8-32-all-report-version-0-2-43-555/6390331Mon, 22 Jun 2026 12:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:db91555a-8e14-466c-83c7-c9763c8399cfRyan Brown1Hi Sen, Since I believe this version is maintained in source libraries, developers are not able to access them and thus the best course of action is to create a custom version which is maintained inside your modified BLE application code. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1646142/cc2652p7-on-chip-oad-does-not-success-device-reset-on-our-custom-pcb/6390306Mon, 22 Jun 2026 12:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4b7a65e9-4670-40ef-aa5e-4d76f4d70556Ryan Brown1Hi Bank, I&#39;d ask for you to ensure that the Frequency Make Tolerance (FL) is equal to or less than +/- 20 ppm. Otherwise both crystal options appear to adhere to the datasheet specs, with option B being closer to the recommended CL. See Section 6 of swra640 for tuning recommendations. Regards, Ryanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1655133/cc2642r-q1-ble-secure-connections-issue/6390207Mon, 22 Jun 2026 10:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5081b6e9-750d-4fe0-86d8-f25f5d874ab8Faruk D.Yes, we performed an ABA swap test. We swapped the chip with one from a known-good board, and the failure followed the chip to the working board.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1654686/cc2340r5-changing-tx-power-in-zephyr/6390102Mon, 22 Jun 2026 08:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f5cc4aee-4599-4d4b-a8e3-e1611365ad7cLeaHi ! Unlike setting the TX power, reading the TX power is not a vendor-specific HCI command. This is a regular Bluetooth HCI command. This means that you can send an HCI command with the value BT_HCI_OP_READ_TX_POWER_LEVEL, in the same way that you are sending the VS HCI command. You can see the format of the request and response struct in &quot;zephyr\include\zephyr\bluetooth\hci_types.h&quot; : #define BT_HCI_OP_READ_TX_POWER_LEVEL BT_OP(BT_OGF_BASEBAND, 0x002d) /* 0x0c2d */ struct bt_hci_cp_read_tx_power_level { uint16_t handle; uint8_t type; } __packed; struct bt_hci_rp_read_tx_power_level { uint8_t status; uint16_t handle; int8_t tx_power_level; } __packed; You will then be able to read the TX power from the rsp struct, filled out by bt_hci_cmd_send_sync. You will need to cast rsp to the bt_hci_rp_read_tx_power_level struct by adding &quot;rp = (void *)rsp-&gt;data;&quot;. You can see the example linked below to see how it&#39;s done. As for your memory allocation question, the Zephyr example for using Vendor-specific HCI command does not free the buf pointer, but it does free the rsp pointer after using it by calling &quot;net_buf_unref(rsp);&quot;. I assume that the buf pointer is freed by bt_hci_cmd_send_sync. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1657111/cc2642r-memory-issues-of-cc2642/6390013Mon, 22 Jun 2026 07:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a2add475-010e-41eb-a6c8-ad193ff95132LeaHi ! When building the rtls_coordinator project for the CC2642, I see that I am using only 16% of RAM (12536 bytes out of 77857). Could you re-build your project and run &quot;View &gt; Memory Allocation&quot; to see what is your memory usage ? Another thing might be that you are not allocating enough memory for your heap. Do you know what heap strategy you are using and what is your heap size ? Can you share your map file ? If you want to optimize the memory of your application, removing unused modules like UART in SysConfig will cut down memory consumption. I don&#39;t recommend removing threads, as they are all necessary for the application. You can try to look at this chapter of the user guide if you think the issue is that you do not have enough heap (which I don&#39;t think is the issue). Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1646856/am625-cc3300-ble-not-functioning-properly-on-am62xx-custom-board/6389999Mon, 22 Jun 2026 07:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7931325b-bf22-4c49-bb49-d7868b1694aeNavami GSHi Josh After following the steps you shared these are the logs, root@am62xx-lp-evm:~# bluetoothctl hci0 new_settings: bondable le secure-conn Agent registered [CHG] Controller 34:68:B5:88:3E:80 Pairable: yes [bluetooth]# power on hci0 new_settings: powered bondable le secure-conn Changing power on succeeded [CHG] Controller 34:68:B5:88:3E:80 Powered: yes [bluetooth]# [ 1319.892457] audit: type=1334 audit(1781947457.929:22): prog-id=20 op=UNLOAD [ 1319.900901] audit: type=1334 audit(1781947457.933:23): prog-id=22 op=UNLOAD [ 1319.908312] audit: type=1334 audit(1781947457.933:24): prog-id=21 op=UNLOAD advertise on hci0 advertising_added: instance 1 [CHG] Controller 34:68:B5:88:3E:80 SupportedInstances: 0x13 (19) [CHG] Controller 34:68:B5:88:3E:80 ActiveInstances: 0x01 (1) Advertising object registered Tx Power: off Name: offh]# Appearance: off Discoverable: on RSI: onoth]# [bluetooth]# scan on SetDiscoveryFilter success hci0 type 6 discovering on Discovery started but this am62xx is not displaying/showing in the simple link app scan. Also from stating im asking you whay this hciconfig -a is giving this error root@am62xx-lp-evm:~# hciconfig -a hci0: Type: Primary Bus: UART BD Address: 34:68:B5:88:3E:80 ACL MT[ 1807.288875] Bluetooth: hci0: unexpected cc 0x0c14 length: 1 &lt; 249 U: 255:10 SCO MTU: 0:0 UP RUNNING RX bytes:35893 acl:0 sco:0 events:836 errors:0 TX bytes:1486 acl:0 sco:0 commands:142 errors:0 Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: PERIPHERAL ACCEPT Can&#39;t read local name on hci0: Input/output error (5) Thanks Navamihttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1646142/cc2652p7-on-chip-oad-does-not-success-device-reset-on-our-custom-pcb/6389978Mon, 22 Jun 2026 06:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8a48c152-f998-489e-979a-f0716aa34c56BankHi Tarek, Could you please explain the differences between crystal A and crystal B, including any impact on oscillator startup margin, frequency stability, load capacitance requirements, and overall system performance? Parameter TZ3158EA6053 (TI Ref) A B Frequency 32.768 kHz 32.768 kHz 32.768 kHz 32.768 kHz CL 6–12 pF 7 pF 12.5 pF 7 pF ESR 30–100 kΩ 80 kΩ max 90 kΩ max 70 kΩ max Drive Level n/a 0.1 &#181;W typical, 1 &#181;W max 0.5 &#181;W max 0.5 &#181;W max Regards, Bankhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1657111/cc2642r-memory-issues-of-cc2642Mon, 22 Jun 2026 01:42:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f6e0fa0c-60a6-4c30-9c62-1c508cb927b8junjie DengPart Number: CC2642R Other Parts Discussed in Thread: SYSCONFIG Dear TI Support Engineer, I am currently working with the rtls_coordinator project. I need to implement passive connections and RSSI value collection via BLE advertising, alongside several custom application tasks. To reduce memory footprint, I would like to check if unused tasks inside the project can be disabled. The application currently crashes during runtime with a memory allocation failure in the execution path: ICall_createRemoteTasks → Task_create → Memory_alloc. Could I disable unused modules via SysConfig to cut down memory consumption? Best regards, Deng JunjieCC2642RSYSCONFIGBody Electronics &amp; Lightinghttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1651719/lp-em-cc2340r5-issue-on-cc2340r5-flash-programming-and-chip-erase-become-impossible-due-to-error--615-swd-communication-error/6389648Sun, 21 Jun 2026 23:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:19ad4ee4-12d8-4645-b92b-61a6b910720bHONDA SHOGOHello Alex, Thank you for your response. Your explanation clarified the points we wanted to confirm, and we now have a clear understanding of the situation. We will mark this thread as resolved. Thank you very much for your support. Best regards,https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1654539/cc2745r10-q1-channel-sounding-function-not-returning-value/6389567Sat, 20 Jun 2026 06:42:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2541b9bd-0284-4206-8364-5d0a64f4358dPrafulla SalunkeHello Evan, With above mentioned clock settings &amp; disabling Low power mode, Channel sounding is working file. For key side, where I am 3V coin cell CR2450 battery, strangely whenever battery voltage dips below 2.9V, channel sounding distance measurement is getting stuck. One more thing is, Motion sensor AIS2DW is integrated over SPI . DIO11, 12, 15, 16 are used as MOSI, MISO, SCLK &amp; CS. DIO18_A7 is configured as interrupt from motion sensor. We measured the current consumption during sleep mode, consumed current is ~2.5mA. How this can be reduced further ? Motion sensor is consuming ~200uA as of now. I am working on reducing it further. From BLE side, how this can be further reduced ? Regards, Prafulla S.https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656361/cc2340r5-high-drive-io-configuration/6389304Fri, 19 Jun 2026 18:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c7c53214-62e0-4330-839f-f1f9cc28fb1eAlex FagerHello, The actual file that has the sysconfig related defines is GPIOLPF3.h, in this find: #define GPIO_CFG_DRVSTR_LOW_INTERNAL ( IOC_CONFIG_DRIVE_STRENGTH_2MA ) #define GPIO_CFG_DRVSTR_MED_INTERNAL ( IOC_CONFIG_DRIVE_STRENGTH_4MA ) #define GPIO_CFG_DRVSTR_HIGH_INTERNAL ( IOC_CONFIG_DRIVE_STRENGTH_8MA ) Sysconfig abstracts it: Setting sysconfig GPIO to strength to medium sets the ti_drivers_config.c GPIO to GPIO_CFG_OUT_STR_MED which then is abstracted to #define GPIO_CFG_OUT_STR_LOW GPIO_CFG_DRVSTR_LOW_INTERNAL then you can find in the ioc.h file this: //! \hideinitializer Manual mode, 8 mA drive strength #define IOC_CONFIG_DRIVE_STRENGTH_8MA ( IOC_IOC12_IOCURR_CUR_8MA ) //! \hideinitializer Manual mode, 4 mA drive strength #define IOC_CONFIG_DRIVE_STRENGTH_4MA ( IOC_IOC12_IOCURR_CUR_4MA ) //! \hideinitializer Manual mode, 2 mA drive strength #define IOC_CONFIG_DRIVE_STRENGTH_2MA ( IOC_IOC12_IOCURR_CUR_2MA ) // Automatic mode is not supported on this device #undef IOC_CONFIG_DRIVE_STRENGTH_AUTO The above shows our four modes (including automatic) which means this should be IOSTR which also happens sets the current (IOCURR), so yes sysconfig does set the drive strength. You can likely also set the register directly using: //***************************************************************************** // // API Functions and prototypes // //***************************************************************************** //***************************************************************************** // //! \brief Set the configuration and mux option for a specific DIO. //! //! \param dioNumber specifies the DIO to configure (0-25). //! //! \param config The configuration to apply. This is a bitwise OR of //! - One of the \ref ioc_config_drive_strength_options //! &quot;IOC Config drive strength options&quot; //! - One of the \ref ioc_config_slew_rate_options //! &quot;IOC Config slew rate options&quot; //! - One of the \ref ioc_config_pull_control_options //! &quot;IOC Config pull control options&quot; //! - One of the \ref ioc_config_edge_detection_options //! &quot;IOC Config edge detection options&quot; //! - One of the \ref ioc_config_standby_wakeup_options //! &quot;IOC Config standby wakeup options&quot; //! - One of the \ref ioc_config_shutdown_wakeup_options //! &quot;IOC Config shutdown wakeup options&quot; //! - One of the \ref ioc_config_io_invert_options //! &quot;IOC Config IO invert options&quot; //! - One of the \ref ioc_config_io_mode_options &quot;IOC Config IO mode options&quot; //! - One of the \ref ioc_config_input_buffer_options //! &quot;IOC Config input buffer options&quot; //! - And one of the \ref ioc_config_hysteresis_options //! &quot;IOC Config hysteresis options&quot; //! //! \param mux Selects the function of the DIO. It must be one of the following: //! - \ref IOC_MUX_GPIO //! - \ref IOC_MUX_DTB //! - \ref IOC_MUX_ANALOG //! - \ref IOC_MUX_PERIPH_FUNC1 //! - \ref IOC_MUX_PERIPH_FUNC2 //! - \ref IOC_MUX_PERIPH_FUNC3 //! - \ref IOC_MUX_PERIPH_FUNC4 //! - \ref IOC_MUX_PERIPH_FUNC5 // //***************************************************************************** __STATIC_INLINE void IOCSetConfigAndMux(uint32_t dioNumber, uint32_t config, uint32_t mux) { // Check the arguments. ASSERT(dioNumberLegal(dioNumber)); ASSERT((config &amp; IOC_CONFIG_ALL_M) == config); ASSERT((mux &amp; IOC_IOC0_PORTCFG_M) == mux); // Set the config and mux option for the specified DIO. HWREG(IOC_BASE + IOC_O_IOC0 + dioNumber * IOC_REG_SPACING) = config | mux; } Best, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656744/cc2745p10-q1-programming-cc2745-with-cmsis-dap-interface/6389271Fri, 19 Jun 2026 17:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9608b56a-4183-4b90-a4e2-82267c23521bAlex FagerHello Mike Crowe, Can you revert down to ti-v1.1.0 or ti-v1.1.1 as these two were the versions that initially added support for the CC27 devices. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656361/cc2340r5-high-drive-io-configuration/6389270Fri, 19 Jun 2026 17:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2ec52359-3d72-48ec-8ac9-7fe947d62449Munan XuAlso I just realized further down that list there is yet another field for slew control, so I don&#39;t think the sysconfig tool ever touches drive strength, just drive current. So then the question really is just what is the difference between the two bitfields IOSTR and IOCURR Munanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656607/cc2340r5-cc2340r5-module-is-not-visible-in-laptop-scan/6389182Fri, 19 Jun 2026 16:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:87129849-2f1b-4697-8e3f-ca2ca33c0821Himanishu KaradbhajneHi Yes CC2340R5 is in advertising. Yes device in visible in simplelink connect mobile app. want to check the file transfer from mobile app or windows laptop app to CC2340R5 module (linux terminal) Is it possible to transfer the file instated of data from Mobile Application to CC2340R5https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656361/cc2340r5-high-drive-io-configuration/6389082Fri, 19 Jun 2026 14:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f8873cdd-ca31-4c4b-ba82-d2d67adc7e77Munan XuHi Alex, Yes this is possible to configure a pin with drive strength using sysconfig, but it is also important to actually write out what the recommended settings are for this since not every customer is using sysconfig, and then it requires everyone who looks at this post now to go into sysconfig and configure a GPIO to see what it spits out. For what it&#39;s worth, Sysconfig seems to leave IOSTR on &quot;auto&quot; as a default unless you ask it to reduce the slew rate: Which also if you look at the TRM description of this feature: It&#39;s not really clear which one ends up controlling the current sourcing or sinking capability of the pin. Sysconfig seems to imply that IOSTR is just controlling the slew rate, but the TRM seems to imply that to actually get 8-10 mA out of a high drive pin across any supply voltage situation (whether or not that is advised is up to the user to decide) you would need to override the auto setting for IOSTR and set it to maximum. Or is the TRM saying that somehow the auto setting automagically does this for you? Thoughts? Munanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1655159/cc2652r-how-to-evaluate-channel-quality/6388748Fri, 19 Jun 2026 07:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:11e0bed1-ef5e-4d34-b54c-9a13ab3df743Yasukane YamanakaHello, Thank you for your response. I’ll review the sample code and consider it. Kind regards,https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656361/cc2340r5-high-drive-io-configuration/6388369Thu, 18 Jun 2026 22:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a93aed66-d5c8-4358-aa8a-24379ef5a506Alex FagerHello Munan Xu, We should be able to set this in sysconfig in the GPIO section under output strength. Thanks, Alex Fhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656744/cc2745p10-q1-programming-cc2745-with-cmsis-dap-interface/6388219Thu, 18 Jun 2026 19:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:30b726a2-7412-45a4-a768-486dd91ff701Mike CroweHere are some additional diagnostics when the TI openocd is run with --debug sudo ./bin/openocd -f gcdc1483-program.cfg ... Debug: 83 5 target.c:1588 handle_target_init_command(): Initializing targets... Debug: 84 5 semihosting_common.c:107 semihosting_common_init(): Debug: 85 36 cmsis_dap_usb_bulk.c:170 cmsis_dap_usb_open(): found product string of 0x0d28:0x0204 &#39;DAPLink CMSIS-DAP&#39; Debug: 86 36 cmsis_dap_usb_bulk.c:190 cmsis_dap_usb_open(): enumerating interfaces of 0x0d28:0x0204 Debug: 87 37 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 0, has only 1 endpoints Debug: 88 37 cmsis_dap_usb_bulk.c:300 cmsis_dap_usb_open(): skipping interface 1, class 10 subclass 0 protocol 0 Debug: 89 38 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 2 string &#39;QYF-CMSIS-DAP&#39; Debug: 90 38 cmsis_dap_usb_bulk.c:257 cmsis_dap_usb_open(): skipping interface 2, endpoint[0] is not bulk out Debug: 91 39 cmsis_dap_usb_bulk.c:237 cmsis_dap_usb_open(): found interface 3 string &#39;WebUSB: CMSIS-DAP&#39; Debug: 92 39 cmsis_dap_usb_bulk.c:250 cmsis_dap_usb_open(): skipping interface 3, has only 0 endpoints Error: 93 40 cmsis_dap.c:287 cmsis_dap_open(): unable to find a matching CMSIS-DAP device Debug: 94 40 command.c:529 exec_command(): Command &#39;init&#39; failed with error code -4https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656744/cc2745p10-q1-programming-cc2745-with-cmsis-dap-interfaceThu, 18 Jun 2026 19:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b2246895-50a2-4dd4-ac4b-8df50b5f70deMike CrowePart Number: CC2745P10-Q1 I have been devloping wiht the lp_em_cc2745r10_q1 evaluation board using the TI branch of openocd (openocd_1_3.1.50). Our production programming environment uses CMSIS-DAP interfaces. When we adjust interface to the cmsis-dap e.g. #source [find interface/xds110.cfg] source [find interface/cmsis-dap.cfg] we get the following error: Open On-Chip Debugger 0.12.0+dev-00006-g98b4ef45b (2026-03-10-10:04) Licensed under GNU GPL v2. For bug reports, read http://openocd.org/doc/doxygen/bugs.html * init Error: unable to find a matching CMSIS-DAP device To validate the hardware, when the stock openocd application was used, the interface was found and even was able to reset the cc2745 before failing (we had to select a differnt chip to get things to go) The stock openocd fails when encountering &quot;-switch-thru-dormant&quot; in target/cc27xx.cfg We tried to remove it, but it still faild Any ideas of how to proceed would be useful. Cheers MikeCC2745P10-Q1Test &amp; Measurementhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656607/cc2340r5-cc2340r5-module-is-not-visible-in-laptop-scan/6388115Thu, 18 Jun 2026 17:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b8f35436-e2c8-4ce6-bbb1-56ab9839b25cJanHi, Thank you for reaching out. I have a couple of questions to help figure out what is going on. 1. Is the CC2340R5 advertising? Are you able to see it advertising using the simplelink connect mobile app? 2. What kind of devices are you seeing in the scan device feature of your laptop? Some desktop OSs restrict the types of advertised devices that show up in the scan results. I don&#39;t know if your version of Linux does this, but Windows and MacOs do. Best Regards, Jan