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/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, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656365/cc2340r5-add-drive-strength-control-to-zephyr-gpio-driver/6388113Thu, 18 Jun 2026 17:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4fc55a4c-b03b-4cde-9e33-29e9b5a826abJanHi Munan, Thank you for reaching out. I am looping in a Zephyr expert to comment. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1653768/cc2745p10-q1-modifying-dts-file-to-enable-interal-low-frequency-osc-when-using-zephyr-for-mesh-applications/6387858Thu, 18 Jun 2026 15:16:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7bc01fb6-29c6-4fd1-a6fc-39588384ed0bMike CroweWhile not very elegant, using PowerLPF3_selectLFOSC() works as a patch against a faulty .dts Thanks for your help in the regard Cheers Mikehttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status/6387785Thu, 18 Jun 2026 14:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0f5fe4d7-01f4-4c78-b63b-1bfaa0fff093Tarek DHey Mike, [quote userid=&quot;402811&quot; url=&quot;~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status&quot;]Is it correct that CC2340R5 does not support Channel Sounding [/quote] This is correct, unfortunately the CC2340R52 does not support Channel Sounding [quote userid=&quot;402811&quot; url=&quot;~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status&quot;]For R53-based devices , is Channel Sounding:[/quote] For R53 devices, the reflector role of channel sounding is supported, however, the initiator role is not currently supported [quote userid=&quot;402811&quot; url=&quot;~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status&quot;]For the lack of CS support on R5, is this mainly due to[/quote] The lack of CS support on the R52 is mainly due to RAM constraints. The R53 variant has more RAM space which enabled the CS support [quote userid=&quot;402811&quot; url=&quot;~/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status&quot;]Is there any plan or possibility for[/quote] As of right now, there aren&#39;t any plans for enabling CS support on R52. Currently, for evaluating Channel Sounding, I would recommend using the car_node and key_node examples found in the latest SDK (9.20). For instructions on how to use these examples, and for more information regarding channel sounding, the user&#39;s guide channel sounding section discusses this. I hope this answers your questions! Best Regards, Tarek Dhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656626/cc2745p10-q1-how-to-set-irk-and-static-random-address-stored-in-flash-at-startupThu, 18 Jun 2026 12:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ea39d424-e1fd-4f11-9588-8a7fd042cf3bKoki TsushimaPart Number: CC2745P10-Q1 Customer is porting the CC2642 code to CC2745. The SDK version is simplelink_lowpower_f3_sdk_9_14_01_16. The IRK and Random Static Address are set via an external interface and are configured at startup. In the CC2642, I used osal_snv_write() and osal_read_snv_read() for this setting. Then, by writing the IRK and Random Static Address read by osal_read_snv_read() at startup, the STACK was correctly configured, and the RPA was also created correctly. However, with CC2745, osal_read_snv_read() and osal_write_snv_write() cannot be used unless they are called after BLEAppUtil_init(). Also, it seems that the IRK and Random Static Address need to be set before BLEAppUtil_init(). Please tell me the specific method for retrieving information previously saved in Flash and registering it on the Stack at startup. Note that the information needed simultaneously at startup, including the IRK and Static Random Address, is approximately 40 bytes.Body Electronics &amp; LightingCC2745P10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656607/cc2340r5-cc2340r5-module-is-not-visible-in-laptop-scanThu, 18 Jun 2026 10:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bc0acf11-c7c3-46cd-b5cb-35af4c470030Himanishu KaradbhajnePart Number: CC2340R5 CC2340R5 module is power on in I.MX93 linux. In mobile bluetooth scan device is visible, able to connect and pair. But CC2340R5 module is not visible in windows laptop bluetooth scan.CC2340R5Connected peripherals &amp; printershttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656477/cc2745r10-q1-car_node-example-will-enter-hardfault-with-commenting-app_extctrlinitThu, 18 Jun 2026 06:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3f5d8a17-338e-44f1-9ac1-a9271fdafca2ConnorPart Number: CC2745R10-Q1 Hi team, I found something wired. When I comment the App_extCtrlInit() to test Standby on Car Node, sometimes it will enter Hardfault with no specific time(30s ~ several minutes). SDK version: simplelink_lowpower_f3_sdk_9_20_00_81 HW: LP-EM-CC2745R10-A SW: Car_Node example. Could the team reproduce the issue and debug this? Thanks, Best Regards, ConnorBody Electronics &amp; LightingCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656181/cc2340r5-clarification-request-cc2340r5-vs-r53-bluetooth-channel-sounding-cs-support-sig-status/6387007Thu, 18 Jun 2026 02:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:389bed88-58e5-46aa-a3d1-2b0a4ab5dd64JanHi Mike, Thank you for reaching out. We will look into your questions and get back to you as soon as possible. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1655345/cc2642r-capture-rssi-based-on-cc2642/6387006Thu, 18 Jun 2026 02:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4bb89022-e543-4a50-a20a-16e722a0f695JanHi Deng, It should be possible for the CM to track the complete connection, but it will need to capture the connection establishment fully. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1656261/cc2652r7-cc2652r7-erratum-advisory-sys_05-elevated-por-solutions/6386630Wed, 17 Jun 2026 20:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:61f7c9f1-6646-4630-a53e-e7dcead226c9desouzaHi, if you are able to hold the reset line low until the VDDS stabilizes, then you will achieve what you intend. You don&#39;t need to bounce the RESET_N. Voltage supervisors are indeed a good way to hold the reset line waiting for the voltage to stabilize. Although the MAX6897 can be used, working for TI I can&#39;t help myself from recommending our own TPS3842 as a candidate that might be suitable for your design - it has adjustable threshold and programmable delay. Hope this helps, Rafael