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/1676776/cc2642r-tcan4550-rx-fifo-overflow-issue-on-cc2642/6465059Thu, 27 Aug 2026 15:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:16050396-2cfe-4a9a-8a47-2302edf54676Jonathan NergerHello Runfa, The RX FIFO will overflow when the CAN frames arrive faster than the MCU can read and acknowledge them through the SPI interface. There are no configuration settings to achieve a higher throughput. Reducing the SPI processing time per message by reducing idle time, increasing the SPI bit rate, using multi-word SPI read and write functions whenever possible will help create a higher throughput. Reducing the number of frames per second is the other option. The Software Optimization Tips section of the TCAN45xx Software User&#39;s Guide ( Link ) discusses this topic. Regards, Jonathanhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1677264/cc2640r2f-unable-to-read-ecg-and-ppg-data-in-tida01580-labview-applicationThu, 27 Aug 2026 14:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a57ff696-be7c-4ba1-a7ad-cc797fd7da81Ratul KarPart Number: CC2640R2F Other Parts Discussed in Thread: TIDA-01580 , Hi Everyone, Recently I was working on a custom CC2640R2F module where when we are trying check the data in TIDA-01580 Labview application we are getting some error. Few images has been shown below for your references - Also while checking inside CCS, when ever we build the project the .out is vanishing from the folder inside TIDA-01580_firmware_rx\Generated binaries and we can see below in the problem tab in ccs we get this type of output which i have given a screenshot below for your reference - Need your help to resolve these issues. If you need any additional information let me know. Thank you in advance for help us out for clearing this issue. Regards RatulTIDA-01580Medical &amp; healthcareCC2640R2Fhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1671770/cc2340r5-chip-antenna-recommendations/6464832Thu, 27 Aug 2026 11:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3798583b-716c-487e-b065-df4a583ade7fRGWHi Michael, I would expect roughly 25 % antenna efficiency with your dimensions. Regards, Richardhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1671770/cc2340r5-chip-antenna-recommendations/6464428Thu, 27 Aug 2026 05:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9a7fc7c9-d960-42c9-88cf-1d7420923a4aMichael VHi Richard, Regarding the CC2340R5MODA, can external antennas be used under the existing Japanese certification, or would additional certification be required? I noticed that the CC2651R3SIPA Japanese certification includes a list of 38 approved antennas. Does use of any antenna on that list remain covered by the existing certification? ( CC26XX-REPORTS Certification | TI.com ) Is there a similar certificate/annex available for the CC2340R5MODA, and if so, where can it be found? Thank you, Michaelhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1667284/am625-am62x-sk-evm-wl1837-bluetooth-on-uart1-fails-with-failed-to-get-cts-despite-correct-pinmux-gpio-routing-and-dt-node-need-wl1837-chip-enable-pin-reference/6464095Wed, 26 Aug 2026 22:06:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:22bf80d3-bf4f-48e5-ba9e-13e1dbd62dd6BLiuHi Krushna, Thanks for your patience. I looked into this and there is a BT_EN_SOC GPIO on the AM62 SK-EVM. The MCU_SPI0_CS0 either acts as the chip select line for SPI0 or as a GPIO. Can you make sure that the pin is muxed to MCU_GPIO0_1 and drive the BT_EN_SOC high?https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1674202/cc2642r-system-reset-immediately-upon-gapscan_enable-during-simultaneous-scanning-and-advertising-scan-duty-cycle-100---interval-50ms-window-30ms/6463908Wed, 26 Aug 2026 18:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f0c2c2bd-850e-49de-bc0f-2cd5a580cd33Barbara WuHi Marco, I setup the test and does not reproduce the issue from my side. I tried many times no reset issue observed on call GapScan_enable(0,0,0); . I attached one of my test&#39;s ellisys log here to showcase there is adv, connection and scan with 60% duty cycle as you mentioned. And it work properly. I tried many times, but don&#39;t see the issue. e2e.ti.com/.../Valeo.btt Some tips I found during my test setup: When call GapScan_disable, it does not mean SCAN stops immediately. The GAP_EVT_SCAN_DISABLED actual indicate the scan stops. There is cases that GAP_LINK_ESTABLISHED_EVENT come first than GAP_EVT_SCAN_DISABLED. Even though under ADV_REPORT we first call GapScan_disable then call GapInit_connect. So in this case, if only add GapScan_enable under link establish event, the scan will still stop after GAP_EVT_SCAN_DISABLED received. I think you need to check if there is conflict between the enable/terminate/delete logic. And else, if you do see a hard fault happen, is it possible to get callstack information? Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1676736/cc2652p7-access-to-low-link-layer-to-manage-control-channel-and-rf-power-using-zephyr-rtos-source-code/6463632Wed, 26 Aug 2026 15:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5ad28b4e-93a5-4db4-bd6c-c11349499671Ging GonzalezHi Farooq, Zephyr actually provides APIs to do these For the setting of channel frequency map, you can checkout the ` bt_le_set_chan_map` API: https://docs.zephyrproject.org/3.7.0/doxygen/html/group__bt__gap.html#gabc115fd3fff6d00ae878a31613bf70aa For changing the RF Power, there is an example in Zephyr that you can reference, called `hci_pwr_ctrl`: https://docs.zephyrproject.org/latest/samples/bluetooth/hci_pwr_ctrl/README.html However, you may need to do something like the following for RF Power and also add `CONFIG_BT_HCI_VS=y` to your prj.conf file: #define HCI_EXT_SET_TX_POWER_DBM BT_OP(BT_OGF_VS, 0x002F) /* 0xFC2F */ static void set_tx_power(int8_t tx_pwr_lvl) { struct net_buf *buf; int err; buf = bt_hci_cmd_create(HCI_EXT_SET_TX_POWER_DBM, 1); if (!buf) { printk(&quot;Failed to allocate TX power command buffer\n&quot;); return; } net_buf_add_u8(buf, tx_pwr_lvl); err = bt_hci_cmd_send(HCI_EXT_SET_TX_POWER_DBM, buf); if (err) { printk(&quot;TX power SET failed (err %d)\n&quot;, err); return; } printk(&quot;TX power SET to %d dBm\n&quot;, tx_pwr_lvl); } Regards, Ginghttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1676736/cc2652p7-access-to-low-link-layer-to-manage-control-channel-and-rf-power-using-zephyr-rtos-source-code/6463454Wed, 26 Aug 2026 13:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c2b49c65-dccc-45ac-93b6-31580bf38c86JanHi Farooq, Let me loop in a Zephyr expert to comment. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1676776/cc2642r-tcan4550-rx-fifo-overflow-issue-on-cc2642Wed, 26 Aug 2026 12:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2e2de52e-e7b3-4c57-a1d5-384600191e4arunfa huoPart Number: CC2642R Other Parts Discussed in Thread: TCAN4550 Hi, We are using TCAN4550 with CC2642 MCU and encountering a persistent RX FIFO overflow issue. The CAN_EVENT_RX_FIFO_MSG_LOST event keeps triggering continuously. Test Condition: CAN FD mode, nominal bit rate 500kbps, data bit rate 2Mbps Receiving about 1000 frames per second Hardware/Software Configuration: MCU: CC2642 SPI clock: 8MHz, Mode 0 TCAN4550 input clock: 40MHz Task priority: 5 Hardware RX FIFO size: 16 (rxFifoNum[0] = 16) Questions: Is the ~1000fps continuous reception beyond TCAN4550&#39;s capability under this SPI clock? Any register settings or application notes we should refer to for high-throughput CAN FD reception? Attached our configuration for reference. Appreciate your help. Best regardsSoftware-defined vehicleCC2642RTCAN4550https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1676736/cc2652p7-access-to-low-link-layer-to-manage-control-channel-and-rf-power-using-zephyr-rtos-source-codeWed, 26 Aug 2026 10:32:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fa9655dd-bbef-4ca9-8423-bb33b05eba41Farooq ShaikPart Number: CC2652P7 Hello, We wanted the access to Low Link Layer to manage/control Channel (Frequency) and RF Power using Zephyr RTOS source code. Where do we get the source source code. Kindly help provide the direction. -Farooq Shaik +91 9949161041CC2652P7https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463246Wed, 26 Aug 2026 10:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f4d0f17a-d5a8-45fb-9d3a-0497d1c67821Ramprasad GHi Lea, We don&#39;t have a clean working sample to hand over, but here&#39;s the configuration we used and what it takes to set it up, in case it&#39;s a useful starting point: CONFIG_BT_MESH=y, left unprovisioned — just the node&#39;s own idle PB-ADV beacon is enough, no mesh peer or provisioner needed. CONFIG_BT_MESH_ADV_EXT=y — important: the default is CONFIG_BT_MESH_ADV_LEGACY=y, which routes mesh&#39;s beacon through the same singleton bt_le_adv_start() a separate GATT peripheral also needs, so the two collide over one advertising slot. Extended advertising gives mesh its own independent set. CONFIG_BT_EXT_ADV_MAX_ADV_SET=2 — otherwise the second bt_le_adv_start() call fails with -ENOMEM. A second, separate bt_le_adv_start(BT_LE_ADV_CONN, ...) for a plain custom GATT peripheral service. CONFIG_BT_SETTINGS=y plus a settings_load() call before the first bt_le_adv_start() — without this, the BT host&#39;s identity address never resolves, and bt_le_adv_start() can report success while the controller never actually broadcasts anything. Even with all of that in place, we still hit connection-stability issues that we didn&#39;t get to fully isolate. We&#39;ve had to put this on hold for now — we&#39;re on a tight deadline on the main project and couldn&#39;t dedicate more time to building out a fully clean repro. Happy to pick it back up and share actual code if that would help once we have some breathing room. Thanks, Ramprasadhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463236Wed, 26 Aug 2026 10:08:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:00819373-b0b3-4981-ade3-8052f82436c5LeaHi, You mentioned yesterday that &quot;We started building a minimal standalone sample&quot; but ran into issues. Any chance you could share the code for this so I can have a starting point for a non-working firmware ? Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463234Wed, 26 Aug 2026 10:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:65d2a5ad-0508-45ae-a4b1-3a3d96ea64fcRamprasad GHi Lea, Thank you for looking into this further — really appreciate it. We&#39;ll be waiting for your valuable input on the proxy vs. regular GATT comparison. Happy to test anything you come up with on our end. Thanks, Ramprasadhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1674202/cc2642r-system-reset-immediately-upon-gapscan_enable-during-simultaneous-scanning-and-advertising-scan-duty-cycle-100---interval-50ms-window-30ms/6463231Wed, 26 Aug 2026 10:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3ab8d0f7-0c20-4da1-8836-6ac6ef8bb834Marco MagdyHi Barbara, Thank you for looking into this. Here is the additional information you requested: 1. Patch Versions For the BLE Stack, we are using the TI Rollup Patch up to v1.1.1 for simplelink_cc13xx_cc26xx_sdk_6_30_00_84 . To be specific, our environment includes all the fixes up to this release note: v1.1.1 (Test Patch LPRFAPPS-2922): Fix stale RPA being stored when unable to resolve RPA. v1.1.0 (Fix Patches BLE_AGAMA-5040, BLE_AGAMA-5085): Connection parameter update fixes. v1.0.1.1, v1.0.1, and v1.0: All previous fixes from the rollup included. 2. Clarification on the Reproduction Loop To clarify, we don&#39;t necessarily need an endless loop to trigger the crash; it often happens on the very first attempt to resume scanning after link establishment, specifically because Advertising is running. Here is the exact state machine flow that causes the crash: Initial State: Advertising is running in the background (no active connection). Scanning is enabled. Target Found: The exact device is found via scan. Disable Scan: Scanning is stopped ( GapScan_disable() ). Connect: A connection to the target device is successfully established when the event received from the SDK. Resume Scan: We call GapScan_enable() to resume scanning while the new connection is active AND Advertising is still running in the background. Crash: The system crashes right here during GapScan_enable() . Important Isolation Testing: We ran a test to isolate the variables. If we run a loop of GapScan_disable() and GapScan_enable() multiple times with NO active connection and with Advertising OFF , no crash occurs whatsoever. The crash is strictly tied to calling GapScan_enable() when Advertising is enabled and running in the background (especially right after a link has been established). Please let me know if you need any additional code snippets or register details to help reproduce this on your end. Best regards, Marco Magdyhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463228Wed, 26 Aug 2026 09:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8c55509f-197f-453d-b619-6c86c3c1fc6cLeaHi, As far as I&#39;m aware, no this has not been done. A colleague mentioned running OAD, but they ran OAD first and enabled mesh later, just like you&#39;re doing right now. So a third party non mesh GATT peripheral has not been validated, no. But if proxy is working, it must mean that there&#39;s at least a way to make it work. I could compare how proxy and mesh are interactive vs regular GATT and mesh, to figure out what the issue is and see if I can fix it. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463219Wed, 26 Aug 2026 09:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0b67dc28-f5ee-483d-ae0c-1d2ab6ac33c1Ramprasad GHi Lea, Thanks for pointing us to mesh_uart_bridge — good to know it&#39;s in our exact SDK tree. One clarifying question before we try adapting it: as far as we can tell, the GATT connection in that sample is mesh&#39;s own Proxy Service / PB-GATT provisioning bearer, not a separate, unrelated custom GATT peripheral service. Our actual scenario is the latter — a completely independent GATT service (our own UUIDs, our own connectable advertising set) running alongside mesh&#39;s PB-ADV beacon, with no relation to mesh&#39;s own provisioning/proxy mechanism. Has that specific combination — mesh&#39;s own advertising plus a third-party, non-mesh GATT peripheral connection — actually been validated on the CC23xx Zephyr downstream, or does mesh_uart_bridge only demonstrate the mesh-protocol-connection case? If it&#39;s the latter, we&#39;re not sure it transfers directly to our situation, even though the underlying radio-scheduling mechanics should be similar. Thanks, Ramprasadhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463123Wed, 26 Aug 2026 08:17:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a23ce333-20b1-44c8-85db-6b512888ed54LeaHi ! From what I discussed with other teams, the &quot;mesh_uart_bridge&quot; example in the Zephyr downstream has the proxy mode enabled by default, so it should be able to run BLE advertisment and connections while at the same time running BLE Mesh operations. Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1666686/cc2340r5-cc2340r53-bt-mesh-custom-connectable-gatt-peripheral-service-discovery-hangs-disconnects-relates-to-zephyr-peripheral-sample-not-connecting-thread/6463077Wed, 26 Aug 2026 07:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:dda7eb60-dbbc-4429-9840-4b58ac1d57bcRamprasad GHi, Thanks for the reply. We started building a minimal standalone sample to hand over, but ran into real trouble just getting BLE Mesh + a separate connectable GATT peripheral to behave reliably together on the CC2340R53 (Zephyr downstream) - not just the discovery-hang we originally reported, but issues even with basic advertising visibility and connections completing. Before we keep iterating on a from-scratch repro, it would help a lot if you could point us to: Any existing example/reference project (from TI or elsewhere) that demonstrates BLE Mesh and a separate GATT peripheral role running concurrently and working - even for a different chip family, e.g. the CC13x2/CC26x2 &quot;simple_mesh_node&quot; reference mentioned in TI&#39;s Bluetooth Mesh Software Product Brief (SWRA732). Whether anything like that exists specifically for the CC23xx Zephyr downstream, even as an unofficial/internal example. Having a known-working baseline to compare against (or adapt) would be much more useful to us right now than us continuing to guess at a minimal repro blind. Happy to still share whatever we build once we get it stable, but a working reference from your side would save a lot of back-and-forth. Thanks, Ramprasadhttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1675601/cc2640-cc2640-ble-stack-question-link-layer/6462619Wed, 26 Aug 2026 00:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d6d7d29e-5d81-4664-925d-c987648196c2Michael McCullyHi Jan, No apology necessary. When I first posted the question I was trying to decide on the way to most definitely identify my problem, hence the question about trapping it at the BLE Link Level of the TI stack. Since I posted the question, though, I did use a USB BLE sniffer, and it looks like the problem is on the Android side. I&#39;m 99.9% sure that&#39;s where the problem is, but 99.9 isn&#39;t as good as 100%. I&#39;m interacting with some who are looking at the Android code. The BLE SDK is 2.2.1.18, because that is what was used for the production model of the 2640 device. The two Android devices under test that I am having no trouble at all with are phones, one running Android 16 and the other Android 6.0. The client that is failing to connect is an Android watch running WearOS 6.0. I&#39;m not sure at this point if I&#39;ll need to go back to the TI Link Level code--it depends on what I hear from the others with whom I&#39;m working, but in case I need to it would be nice to know, if convenient, which message stack to look at to find the first appearance at the Link Level of a connect request from a central device. Thanks for your reply, Mikehttps://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1675645/cc2755p10-accurate-distance-measurement/6462259Tue, 25 Aug 2026 18:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c1bd8ba2-847c-45f2-99bb-f1f191f27800Arthur Shidlovskiy1. Does distance measurement work with just one antenna? 2. How can I contact a TI representative? 3. Can I use Bluetooth long range to maximize the measurement range? Regards, Artur