<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Wi-Fi</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/</link><description>&lt;p style="display:none;"&gt;blank&lt;/p&gt;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: CC3301: CC33xx Driver – RAM Usage Optimization Request</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693686/cc3301-cc33xx-driver-ram-usage-optimization-request/6545168</link><pubDate>Sun, 22 Nov 2026 14:50:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:173641ea-805b-47a1-9674-9728806d0ddb</guid><dc:creator>Shlomi Itzhak</dc:creator><description>Hi, Can you pin point where it is on the .map file? the wrapper itself is not that heavy but it points to freeRTOS implementations that are necessary if you are working with an OS (semaphore, tasks, queues, etc). Th library itself is under the am243 SDK (e.g. C:\ti\mcu_plus_sdk_am243x_09_02_01_05\source\kernel\freertos\lib). Regards, Shlomi</description></item><item><title>Forum Post: RE: CC3551E: FW Cash during Iperf test</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1690623/cc3551e-fw-cash-during-iperf-test/6545166</link><pubDate>Sun, 22 Nov 2026 14:38:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7988c761-d9a9-4c3c-b252-ef6484fca351</guid><dc:creator>Shlomi Itzhak</dc:creator><description>Hi, This would be good. I can either open a sharepoint for you to share (but need an Email address) or you can uploaded to somewhere that I can fetch. Regards, Shlomi</description></item><item><title>Forum Post: RE: CC3551E: CCStudio for VS Code Unable to Resovle Compiler Reference</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698837/cc3551e-ccstudio-for-vs-code-unable-to-resovle-compiler-reference/6544909</link><pubDate>Fri, 20 Nov 2026 20:47:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d7be623c-0243-4132-8e64-6c8d18f88d46</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Peter, Both the &amp;#39;Installation and Setup&amp;#39; and &amp;#39;Troubleshooting&amp;#39; pages have setup requirements to follow. To clarify, I am asking if you have done the following: 3.1.1 System Requirements (should be yes) 3.1.2 Installing CCStudio for VS Code (should be yes) Would be good to double check that the dependencies are installed, you can verify in C:\[USER]\.vscode\extensions 3.1.3 Install the XDS110 Debug Probe Drive r (could be root cause) 10.1.2.1 Project Debug Requires Manual Pre-Launch Setup (could be root cause) Please confirm at your earliest convenience. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: CC3551E: CCStudio for VS Code Unable to Resovle Compiler Reference</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698837/cc3551e-ccstudio-for-vs-code-unable-to-resovle-compiler-reference/6544746</link><pubDate>Fri, 20 Nov 2026 17:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d72a264d-4948-4f29-84f1-4d5fd61bbc80</guid><dc:creator>Peter Borenstein</dc:creator><description>Josh, You linked the troubleshooting section, but referenced a setup. Should I follow the setup section or troubleshooting sections? Thank you, Peter B</description></item><item><title>Forum Post: RE: CC3551E: CCStudio for VS Code Unable to Resovle Compiler Reference</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698837/cc3551e-ccstudio-for-vs-code-unable-to-resovle-compiler-reference/6544660</link><pubDate>Fri, 20 Nov 2026 16:26:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:95df5033-4104-4e26-be63-071e24f8710a</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Peter, Have you done the manual pre-launch setup described here: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccsvsc_1.0.2000/ccsvsc_troubleshooting.html#cc35x1e? Please let me know if you have any questions. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: LM25007: Material 52388 / LM25007MMX/NOPB</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1697688/lm25007-material-52388-lm25007mmx-nopb/6544624</link><pubDate>Fri, 20 Nov 2026 15:59:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2a171814-3b1a-4b86-ad85-051dae2ccdff</guid><dc:creator>Frank De Stasi</dc:creator><description>Hello Let me check. Thanks</description></item><item><title>Forum Post: RE: CC3351MOD: CC3351MOD: cc33xx linux driver crashing issue</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699058/cc3351mod-cc3351mod-cc33xx-linux-driver-crashing-issue/6544414</link><pubDate>Fri, 20 Nov 2026 10:41:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:60ea90e5-927b-49d7-8282-5e9e4553fe66</guid><dc:creator>Serhii Havrysh</dc:creator><description>Hi Sabeeh! Thank a lot for your response. As for the first question, I can&amp;#39;t switch to inband IRQ couse I have no stable work on SDIO-bus even on 25MHz. I had doubts about how the SoC vendor-provided interrupt controller driver configures the type of IRQ, but if you can see to oscilloscope screenshot diagram (yellow IRQ_WL, blue SDIO_CMD) - it works as specified, on rising edge, IRQ cleared after host issuing cmd. Time for processing interrupt is dependent from linux kernel scheduler. As for the second one, I&amp;#39;m agree with you, nRST should be under the full driver control and not userspace accesible. As for me It&amp;#39;s our task specific, so I will try to convince rework this moment. Generally i did tests with nRST in devicetree, of course it&amp;#39;s very simple to do this. The driver completely restore communication while this issue reproducing, all looks good, but i think It&amp;#39;s not the issue resolution and wireshark-log around &amp;quot; BEACON_TRACK_MODE_TRACKING_NORMAL --&amp;gt; BEACON_TRACK_MODE_TRACKING_AWAKE, beaconMissedCounter = 15, role id = 0 &amp;quot; need to be checked. Log with recovery in attachment. e2e.ti.com/.../cc33xx_5F00_wireshark_5F00_crash_5F00_log_5F00_with_5F00_recovery.txt</description></item><item><title>Forum Post: RE: CC3351MOD: CC3351MOD on custom AM625 board: ROM acknowledges the whole 2nd loader container but never boots it (no HINT 0x10)</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1696568/cc3351mod-cc3351mod-on-custom-am625-board-rom-acknowledges-the-whole-2nd-loader-container-but-never-boots-it-no-hint-0x10/6544392</link><pubDate>Fri, 20 Nov 2026 10:22:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:32ad21a2-28ec-4a20-8183-2fa0949c2c9b</guid><dc:creator>Rajender Reddy Suram</dc:creator><description>Hello TI team, This is an update specifically about question 6 (is the SDIO in-band interrupt usable during the ROM and 2nd-loader stages). We tested it on our board. In-band works for the ROM stage, but it does not fix the problem. Setup: For this test we removed the Host_IRQ_WL GPIO interrupt from the device tree, so the driver used the SDIO in-band interrupt (CCCR 0x16 async interrupt, then sdio_claim_irq ). The GPIO interrupt count stayed at 0. Result ROM stage works in-band. The ROM raised the in-band interrupt for all 110 chunk acknowledges. The driver read HINT=0x2 each time, with the rx_status sequence counter stepping 0x03, 0x43, 0x83, 0xc3, and so on. Each chunk took about 10 ms because the host polls DAT1. The failure is unchanged. After the last chunk&amp;#39;s HINT=0x2 , we polled the status for 2 s and read HINT=0x0 every time. rx_status stayed at 0x83ff0000 and pad0 at 0x55555555 . The wait for HINT 0x10 timed out after 2068 ms. The status word&amp;#39;s TSF kept advancing, so the chip is not reset. The host never sees HINT 0x10 . A device-info command after the timeout gets no answer. Conclusion: the problem is not the interrupt path. With a GPIO interrupt (rising or falling edge) and with the in-band interrupt, we get the same outcome: the 2nd loader is invoked by the ROM (logger shows Container Validation Success and Invoking RAM Bootloader ), but it never posts HINT 0x10 . Questions (additions to the earlier list) Is the in-band interrupt also supported once the 2nd loader is running, or only in the ROM? Since the status register itself stays at zero, what could keep the 2nd loader from posting HINT 0x10 ? Our logger-pin comparison shows SoP Mode = 0x3 (working BBB: 0x1) and an internal slow clock ( System Info 0x8 = 0 , BBB: external). Could either one stop the 2nd loader from starting? After the invoke, what should the host read at 0xBFFC and the surrounding mailbox words to tell that the 2nd loader is alive? Best regards, Rajender</description></item><item><title>Forum Post: RE: CC3551E: BLE link layer stops serving a connection and supervision timeout never fires</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699186/cc3551e-ble-link-layer-stops-serving-a-connection-and-supervision-timeout-never-fires/6544273</link><pubDate>Fri, 20 Nov 2026 08:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0159716d-d5da-44a3-ac86-9f8f4ee3b60b</guid><dc:creator>Jakob Krantz</dc:creator><description>We now also see the hang on the central. Setup as in the description, but 2M PHY and data in one direction only, central to peripheral: 251-byte Write Without Response with all 10 controller ACL buffers in use. The link stalled in 100% of the tests within 18–90 s, 3 times on the central and once on the peripheral. The central shows the same signature in the TI LOGGER: the next connection event is scheduled and CpeReset() runs, but no Coex_requestPTASignal ... granted, rfPUpCallback or llCentral_TaskEnd follows. It then gets no Number Of Completed Packets and no Disconnection Complete, while the peripheral gets Disconnection Complete with reason 0x08. It also happens at a 7.5 ms connection interval. Logs available on request.</description></item><item><title>Forum Post: RE: CC3351MOD: CC3351MOD on custom AM625 board: ROM acknowledges the whole 2nd loader container but never boots it (no HINT 0x10)</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1696568/cc3351mod-cc3351mod-on-custom-am625-board-rom-acknowledges-the-whole-2nd-loader-container-but-never-boots-it-no-hint-0x10/6544206</link><pubDate>Fri, 20 Nov 2026 07:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:05406f27-fc32-447f-89bc-0f1c9c9a450f</guid><dc:creator>Rajender Reddy Suram</dc:creator><description>Hello Sabeeh Khan1 , We are integrating the CC3351MOD (SDIO) on a custom AM625 board. The module boots correctly on a BeagleBone Black, but on our board it does not come up. We captured the logger pin on both systems and compared the ROM logs line by line. The comparison and our questions are below, so you can answer everything in one pass. 1. Setup Working reference (BBB) Failing system (custom board) Host BeagleBone Black (AM335x), carrier supplies the 32.768 kHz slow clock Custom board, PocketBeagle2-derived, AM6232 (AM625 family) Kernel 6.12.57-ti-arm64-r64 6.12.57-ti-arm64-r64 Host interface SDIO SDIO on MMC2, 4-bit, 50 MHz, I/O fixed at 1.8 V (no level shifter) Reset by the carrier WIFI_RESET = GPIO0_4/5 via a regulator-fixed switched by the MMC core (runtime PM), shared with the BT driver Host_IRQ_WL to the BBB straight to AM625 GPIO0_4 (no inverter), no external pull; AM62 GPIO supports edge triggers only Slow clock external 32.768 kHz SLOW_CLK_IN not connected, module&amp;#39;s own clock 2. Symptom on the custom board The ROM boots, accepts all 110 chunks (109 &amp;#215; 640 B + 452 B), validates the container ( Container Validation Success ) and logs Invoking RAM Bootloader . The host then never sees HINT 0x10 (2nd loader up). After the last chunk the status stays 0, the device-info command gets no response, and the chip&amp;#39;s TSF keeps counting (it never rebooted). On the BBB the same step works: HINT 0x10 within a few hundred ms, then the firmware boots. 3. Logger-pin comparison All System Info indices 0x4 to 0x1C were compared (BBB first, then custom board). Same on both: ROM BootMan 1.0.0.31, PG 0x2, metal 0x1, fuse ROM version 0x1, life cycle 3 (strong pattern 0xCA5B3A). Part number 0x0, package 0x0, reset cause PoR, PLL not bypassed and locked, fast clock XTAL 40 MHz. Disable flags: 5 GHz 0, 6 GHz 1, BLE/M0+/M33 0. Bypass level 0xF, expected/actual bypass bitmap 0x18/0x18, actual flow bitmap 0x3E7. The whole ROM sequence through container validation, with the same steps. Different: Item BBB (working) Keonn SoP Mode 0x1 (all 6 boots) 0x3 (all 6 boots) System Info 0x8 (SLOW_CLK_EXTERNAL_DETECTED) / ReadClockInfo 0x1 / external 0x0 / internal (0x9 = 0x1 on both) ROM Version 0x1 0x80 Expected flow bitmap 0x18 0x18 Fuse CRC / UDID / MAC chip specific chip specific Our custom boards capture ends at Invoking RAM Bootloader , so we have no logger output from the 2nd loader on the custom board 4. Other observations On the custom board the Host_IRQ_WL line idles high and goes low while the chip signals, the reverse of the active-high behaviour in swru612b &amp;#167;2.2.2. The schematic has no inverter on that net. The reference DTS for the SK-AM62A M.2 CC3351 uses PIN_INPUT_PULLUP and IRQ_TYPE_EDGE_FALLING on this signal. The TI migration guide uses PIN_INPUT_PULLDOWN and level-high, and warns against pulls. nRESET toggles several times within about 2 s before the download (MMC runtime PM). Each release gives a short ROM boot and HOST_IRQ_WL pulses. On the BBB with the ported 6.12 driver, the 1282-byte conf layout is rejected by FW 1.7.0.185 at the INI download (HINT 0x80000000). This is a separate issue we understand, but it shows the layout/firmware coupling. 5. Already tried, with no change to the 2nd-loader failure SDIO at 5 MHz 1-bit, 25 MHz and 50 MHz, and no-1-8-v . The kernel console and getty silenced and the BT driver unloaded The IRQ trigger as rising and falling edge (level was rejected by the SoC GPIO controller), with and without an internal pull-down on Host_IRQ_WL . 6. Questions SOP and strap What do the bits of SoP Mode mean? Which pin sets which bit, and what do 0x1 and 0x3 select? Does SoP Mode (or the level sensed on Host_IRQ_WL at reset) change anything after the ROM, such as 2nd-loader behaviour or the HOST_IRQ_WL polarity? Is the polarity selectable? When exactly are the SOP pins sampled relative to the nRESET rising edge, and what setup and hold times are required? What are the default pulls on Host_IRQ_WL and Logger inside the module? What external pull-down value do you recommend for Host_IRQ_WL , and is the SoC&amp;#39;s weak internal pull-down enough? HOST_IRQ_WL 5. Please confirm the polarity and clearing rules: high until the host reads the status? 6. Since the AM62 GPIO controller is edge-only, what is TI&amp;#39;s recommended configuration? Can the SDIO in-band interrupt be used during the ROM and 2nd-loader stages? Slow clock 7. Is the internal slow clock fully supported with the 2nd loader and firmware on the CC3351MOD? What do System Info 0x8 = 0 and 0x9 = 1 mean exactly, and does the internal-clock case need specific conf parameters? ROM and logger 8. What does ROM Version 0x80 versus 0x1 mean, and does it indicate a different ROM variant? 9. We read Device Part Number 0x0 and Package 0x0 on a CC3351MOD. Is that expected? 10. Can you provide a logger.bin that matches our 2nd loader and firmware build, so we can decode their logs? Does the 2nd loader log at all, and what should appear after Invoking RAM Bootloader ? 2nd-loader handoff 11. What does the 2nd loader do first, and what can make it hang before it raises HINT 0x10 (clocks, PLL, DCDC current spike, SDIO state)? 12. Which host accesses are allowed during validation and after the invoke? Can extra SDIO reads or a device-info command at that point break the boot? Does the 2nd loader reset the SDIO block (FBR2 block size, bus width)? Which block size is expected (1024 from the AM62 host versus 512)? Firmware and conf 13. What is the official compatibility matrix of driver, firmware, 2nd loader and conf layout (1129, 1282 and 1283 bytes) for kernel 6.12? Is there a TI-released driver for 6.12? Reset and power 14. What are the minimum nRESET low time and the minimum time between releases? 15. Is there any known erratum for PG2 metal 1, ROM 1.0.0.31 regarding the 2nd-loader start, SDIO at 1.8 V or SOP? 7. What would help most A confirmed driver, firmware and conf set for kernel 6.12. Thanks, Rajender</description></item><item><title>Forum Post: CC3351: BLE HCI Controller to Host data flow control issue</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699268/cc3351-ble-hci-controller-to-host-data-flow-control-issue</link><pubDate>Thu, 19 Nov 2026 22:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8e585d11-e286-4d11-80d0-5703ca99a049</guid><dc:creator>Liudmyla Mykytyn</dc:creator><description>Part Number: CC3351 Hi Team, We are currently trying to enable the BLE HCI Controller to Host data flow control, but the CC3351 responds with an error to the HCI_Host_Number_Of_Completed_Packets command. Below are more details: On startup, the NimBLE sends the commands when the MYNEWT_VAL_BLE_HS_FLOW_CTRL is enabled. HCI_Set_&amp;#173;Controller_&amp;#173;To_&amp;#173;Host_&amp;#173;Flow_&amp;#173;Control. Enable param value 0x01: Flow control is on for HCI ACL Data packets and off for HCI Synchronous Data packets in the direction from Controller to Host. HCI_Host_&amp;#173;Buffer_&amp;#173;Size. MYNEWT_VAL_BLE_TRANSPORT_ACL_SIZE 251 MYNEWT_VAL_BLE_TRANSPORT_ACL_COUNT 20 The Controller responds with status Success for both commands. As in our case, MYNEWT_VAL_BLE_HS_FLOW_CTRL_THRESH equals 18. After the 18th ACL DATA packet is received from the Controller, the Host sends the HCI_Host_Number_Of_Completed_Packets command: The Controller responds with the HCI Event with the error code 0x12: Per the BLE HCI spec, part 7.3.40. Host Number Of Completed Packets command: Normally, no event is generated after the HCI_Host_Number_Of_Completed_Packets command has completed. However, if the HCI_Host_Number_Of_Completed_Packets command contains one or more invalid parameters, the Controller shall return an HCI_Command_Complete event containing the error code Invalid HCI Command Parameters (0x12). The normal flow control for commands is not used for this command. According to the Read Local Supported Commands response from the CC3351: 20 00 80 00 00 C0 00 00 00 00 E4 00 00 00 28 22 00 00 00 00 00 00 04 00 00 F7 FF FF 7F 00 00 00 30 F0 FF FF FF E3 80 07 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The HCI_Set_Controller_To_Host_Flow_Control, HCI_Host_Buffer_Size and HCI_Host_Number_Of_Completed_Packets should be supported: bit 0 = 0 HCI_Read_Hold_Mode_Activity bit 1 = 0 HCI_Write_Hold_Mode_Activity bit 2 = 1 HCI_Read_Transmit_Power_Level bit 3 = 0 HCI_Read_Synchronous_Flow_Control_Enable bit 4 = 0 HCI_Write_Synchronous_Flow_Control_Enable bit 5 = 1 HCI_Set_Controller_To_Host_Flow_Control bit 6 = 1 HCI_Host_Buffer_Size bit 7 = 1 HCI_Host_Number_Of_Completed_Packets The connection handle equals the one that is sent in the ACL Data packets from the Controller, so we may assume that this parameter is correct: The CC33XX RTOS MCU SDK R9 is used for the STM32 host with the CC3351. The MYNEWT_VAL_BLE_HS_FLOW_CTRL flag is enabled. MYNEWT_VAL_BLE_HS_FLOW_CTRL_THRESH equals 18. From the CC3351 logs: - Firmware version cc3xxx_rev_1.7.2.348, - HW version 0x33000002, - Wifi lower mac version wifi_lmac_rev_1.0.0.294, - Wsoc version wsoc_rev_1.0.0.13, - Bootloader rom version bootman_rom_rev_1.0.0.31, - Bootloader ram version bootman_ram_rev_1.0.0.31, - BLE version ble_rev_1.0.0.52, - UpperMac version upper_mac_rev_2.0.0.11 Can you please let us know: 1. Does the CC3351 FW support the Controller-to-Host data flow control functionality? 2. If so, are there any steps to be taken, or any specific configuration in the cc33xx-conf.bin to be set to enable this functionality on the Controller? 3. As the CC3351 returns error code 0x12 - Invalid HCI Command Parameters, does this mean that the NimBLE host stack sends the incorrect parameters in the command? If so, can you please specify which parameters are incorrect in our case and what the correct values should be?</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/Portable%2bElectronics">Portable Electronics</category><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3351">CC3351</category></item><item><title>Forum Post: RE: CC3235SF: 5Ghz and 2.4 GHz operation selection from AP mode</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693589/cc3235sf-5ghz-and-2-4-ghz-operation-selection-from-ap-mode/6543735</link><pubDate>Thu, 19 Nov 2026 20:29:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1a846b12-133b-4fc4-814a-9df9fc615ccb</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Sundar, I believe that this is not working because the SL_WLAN_GENERAL_PARAM_OPT_SCAN_PARAMS parameter is only for station mode, it is not relevant for AP. If you want to set the operational channel for AP mode, you should use SL_WLAN_AP_OPT_CHANNEL instead. Please see this thread for more information. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: LM25007: Material 52388 / LM25007MMX/NOPB</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1697688/lm25007-material-52388-lm25007mmx-nopb/6543644</link><pubDate>Thu, 19 Nov 2026 18:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6a25e3ea-3f2b-4ce0-aa62-6d521fdc246e</guid><dc:creator>Jelena Krstic</dc:creator><description>Hi, I have checked with our technical team. However, although the component has the same specifications, it cannot be used due to the difference in packaging. Do you have LM25007MMX/NOPB? We need this material in January</description></item><item><title>Forum Post: RE: CC3351MOD: CC3351MOD: cc33xx linux driver crashing issue</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699058/cc3351mod-cc3351mod-cc33xx-linux-driver-crashing-issue/6543603</link><pubDate>Thu, 19 Nov 2026 17:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f584743d-b8cb-4c06-ae80-73b90dcddd3f</guid><dc:creator>Sabeeh Khan1</dc:creator><description>Hello Serhii, I see your interrupt is configured as &amp;#39; INT_PM_GPI_FIQ_PAD_PM_PSPI0_INT&amp;#39;. What interrupt type is this (level/edge, rising/falling)? Can you try switching to inband IRQ? Also why are you using GPIO from init.d to control the nRST? It is expected that the linux driver should have control over this pin. It should not be userspace accessible.</description></item><item><title>Forum Post: CC3551E: BLE link layer stops serving a connection and supervision timeout never fires</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699186/cc3551e-ble-link-layer-stops-serving-a-connection-and-supervision-timeout-never-fires</link><pubDate>Thu, 19 Nov 2026 14:34:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7ee307f7-4dc2-421a-8926-7e143361028e</guid><dc:creator>Jakob Krantz</dc:creator><description>Part Number: CC3551E Two boards; the host stack is NimBLE, sending HCI through the TI host driver. Wi-Fi is started but has no role or connection. CC3551 - SimpleLink Wi-Fi SDK 10.20.00.39 During a connection the controller stops serving one link. From then on that side gets no ACL RX, no Number Of Completed Packets and no Disconnection Complete, also long after the supervision timeout (2 s). The peer gets Disconnection Complete reason 0x08 after 2 s. HCI commands, including vendor commands, are still answered. In the TI LOGGER of the stalled side, the last connection event is scheduled ( llScheduleTask ) and CpeReset() runs, but no Coex_requestPTASignal ... granted , rfPUpCallback , CpeShutdown or ll*_TaskEnd follows. In every normal event the grant comes directly after CpeReset() . All 7 hangs we captured have this signature. The Setup One connection between two CC35XX boards: 1M PHY, connection interval 15 ms, latency 0, supervision timeout 2 s. LE Set Data Length 251 octets / 17040 &amp;#181;s on both sides. Continuous 251-byte ACL data in both directions: the central sends ATT Write Without Response and the peripheral sends notifications, keeping all 10 controller ACL buffers in use. The link stalls in 6 of 9 runs, after 5–160 s of data. It is always the peripheral. The same signature was also seen once on the central, with no data load (1 of 8 connections, case2_central_conn_update/ ). At connection event 2, an LL_LENGTH_REQ was pending and the host had just sent LE Connection Update (in answer to the peripheral&amp;#39;s L2CAP Connection Parameter Update Request). What we observed after the stall To look at the stalled link, we tried to send some send some vendor commands about about 10s after the last activity: 0xFC20 and 0xFC14 are answered within 3 ms. We do not know the layout of the responses, so key_lines.txt lists them raw, next to the responses to the same commands on a healthy link ( hci_vendor_cmds_healthy_link.btsnoop ). They may show you the state of the link. 0xFC13 ends the link: Disconnection Complete reason 0x16 and Number Of Completed Packets for all 10 buffers. The next LE command is also answered. The host then sends HCI Reset. It never gets a Command Complete. 5 s later the TI host driver reports GENERAL ERROR event received! FW is stuck and WLAN event: FW Crash . The LOGGER shows the HCI Reset entering the BLE stack ( icall_directAPI to BLE func=0x6aed9 ) and never returning, followed by handlerDebugMon() ASSERT ERROR at address 493ae and icall_directAPI() ASSERT ERROR 0 (main dump: PC 0x000493AE, LR 0x00051F0F, R5 0x0006AED9). Further HCI Resets are not answered either. This happened after all 6 stalls with data load. In normal operation the same HCI Reset ( func=0x6aed9 ) completes. To us this looks like the same stuck connection event, now blocking the reset. Where to see it key_lines.txt lists the relevant lines with frame and line numbers: hci_peripheral.btsnoop frame #2202 is the last activity on the link. Nothing follows until the host sends vendor commands at +10.56 s (#2203). 0xFC13 ends the link with reason 0x16 and returns all 10 buffers (#2209, #2210). The HCI Reset at #2213 and its retries are never answered. hci_central.btsnoop frame #2187: the peer gets Disconnection Complete 0x08 1.98 s after the last packet. logger_peripheral.txt line 33650: the last CpeReset() with no grant after it. Compare with the normal event at lines 33554–33556. The next line for this link is the termination at line 34026, 10.57 s later. Line 34084 is the HCI Reset, lines 34223–34224 the asserts, followed by the main dump. Questions What is the connection event waiting for after CpeReset() ? Is it a PTA request that is never granted or denied? Why does the supervision timeout not end the link on the stalled side? Attachments File Content key_lines.txt The key HCI frames and LOGGER lines, the vendor command responses, the HCI Reset with the main dump, and a table of the 5 other stalls hci_peripheral.btsnoop , hci_central.btsnoop HCI traces of both boards (Wireshark) logger_peripheral.bin , logger_peripheral.txt TI LOGGER of the stalled side, raw and decoded hci_vendor_cmds_healthy_link.btsnoop HCI trace of the same vendor commands on a healthy link, for comparison case2_central_conn_update/ The central case: HCI traces of both boards, central LOGGER, key_lines.txt ZIP with all files: A_link_stops_no_supervision_timeout.zip</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3551E">CC3551E</category></item><item><title>Forum Post: CC3351MOD: CC3351MOD: cc33xx linux driver crashing issue</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1699058/cc3351mod-cc3351mod-cc33xx-linux-driver-crashing-issue</link><pubDate>Thu, 19 Nov 2026 09:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:11b8aeb8-c4e8-4f99-9df9-635d4738dbc9</guid><dc:creator>Serhii Havrysh</dc:creator><description>Part Number: CC3351MOD Hello TI team. Related to the same another topic disscussed here https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1582807/cc3301-cc33xx-linux-driver-crashing-issue ?, I&amp;#39;m facing the same linux driver crash issue. Another input data are as follows: - Custom mpu board. - Linux Driver 1.00.02.17 integrated through linux-backports 6.1.97. - Kernel 5.10.117. - cc33xx-conf.bin file is default from package located at cc33xx_linux_package_1_0_2_17/cc33xx/cc33xx_rootfs/lib/firmware/ti-connectivity/cc33xx-conf.bin, threated as &amp;quot;unlimited&amp;quot; - connected to host ap 5GHz # iw wlan0 info Interface wlan0 ifindex 4 wdev 0x1 addr b2:de:ad:be:ef:01 type managed wiphy 0 channel 48 (5240 MHz), width: 20 MHz, center1: 5240 MHz txpower 21.00 dBm - wireshark logs through SimpleLink Wi-Fi Toolbox has been captured. - gpio-reset is controlled through init.d scripts, devicetree has no compatible &amp;quot;mmc-pwrseq-simple&amp;quot; or &amp;quot;regulator-fixed&amp;quot;, so driver can&amp;#39;t recover from from crash. DT: &amp;amp;ifs_sdmmc0 { /delete-property/ no-sdio; no-mmc; fake-cdz = /bits/ 8 ; sdio-use-1bit = /bits/ 8 ; support-runtime-pm = /bits/ 8 ; max-frequency = ; cap-sd-highspeed; /delete-property/ cap-sdio-irq; status = &amp;quot;ok&amp;quot;; #address-cells = ; #size-cells = ; wlcore: wlcore@2 { compatible = &amp;quot;ti,cc33xx&amp;quot;; reg = ; interrupt-parent = ; interrupts = ; }; }; It&amp;#39;s looks like I can&amp;#39;t face this problem working on 2.4GHz freq. So chip doesn&amp;#39;t respond to any SDIO cmd when it happens. Wireshark log messages to look into, i think, need to check all around &amp;quot;BEACON_TRACK_MODE_TRACKING_NORMAL --&amp;gt; BEACON_TRACK_MODE_TRACKING_AWAKE, beaconMissedCounter = 15, role id = 0&amp;quot;. Console dump with backtrace is as follows: [ 7][RX-C] 166.00-167.00 sec 1.82 MBytes 15.3 Mbits/sec [ 5][TX-C] 167.00-168.00 sec 2.25 MBytes 18.9 Mbits/sec 0 443 KBytes [ 7][RX-C] 167.00-168.00 sec 1.74 MBytes 14.7 Mbits/sec [ 5][TX-C] 168.00-169.00 sec 2.25 MBytes 18.8 Mbits/sec 0 447 KBytes [ 7][RX-C] 168.00-169.00 sec 1.83 MBytes 15.3 Mbits/sec [ 5][TX-C] 169.00-170.00 sec 2.25 MBytes 18.9 Mbits/sec 0 452 KBytes [ 7][RX-C] 169.00-170.00 sec 1.78 MBytes 15.0 Mbits/sec [ 5][TX-C] 170.00-171.00 sec 2.25 MBytes 18.9 Mbits/sec 0 458 KBytes [ 7][RX-C] 170.00-171.00 sec 1.81 MBytes 15.2 Mbits/sec [ 5][TX-C] 171.00-172.00 sec 2.00 MBytes 16.8 Mbits/sec 0 462 KBytes [ 7][RX-C] 171.00-172.00 sec 1.66 MBytes 13.9 Mbits/sec [ 5][TX-C] 172.00-173.00 sec 640 KBytes 5.24 Mbits/sec 1 1.41 KBytes [ 7][RX-C] 172.00-173.00 sec 641 KBytes 5.25 Mbits/sec [ 5][TX-C] 173.00-174.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 173.00-174.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 174.00-175.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 174.00-175.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 175.00-176.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 175.00-176.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 176.00-177.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 176.00-177.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 177.00-178.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 177.00-178.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 178.00-179.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 178.00-179.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 179.00-180.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 179.00-180.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 180.00-181.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 180.00-181.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 181.00-182.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 181.00-182.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 182.00-183.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 182.00-183.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 183.00-184.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 183.00-184.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 184.00-185.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 184.00-185.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 185.00-186.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 185.00-186.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 186.00-187.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 186.00-187.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 187.00-188.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 187.00-188.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 188.00-189.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 188.00-189.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 189.00-190.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 189.00-190.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 190.00-191.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 190.00-191.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 191.00-192.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 191.00-192.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 192.00-193.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 192.00-193.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 193.00-194.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 193.00-194.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 194.00-195.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 194.00-195.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 195.00-196.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 195.00-196.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 196.00-197.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 196.00-197.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 197.00-198.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 197.00-198.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 198.00-199.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 198.00-199.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 199.00-200.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 199.00-200.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 200.00-201.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 200.00-201.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 201.00-202.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 201.00-202.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 202.00-203.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 202.00-203.00 sec 0.00 Bytes 0.00 bits/sec cc33xx: ERROR INTERROGATE command failed cc33xx: WARNING acx roaming statistics failed: -5 cc33xx: Recovery work [ 5][TX-C] 203.00-204.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 203.00-204.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 204.00-205.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 204.00-205.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 205.00-206.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 205.00-206.00 sec 0.00 Bytes 0.00 bits/sec cc33xx: down cc33xx: down SDMMC1 &amp;gt;&amp;gt; [Hal_CARD_SetBustiming] LS mode. &amp;gt; [Hal_CARD_SetBustiming] DEFS mode. &amp;gt; [Hal_CARD_SetBustiming] LS mode. &amp;gt; [Hal_CARD_SetBustiming] HS mode. &amp;gt; [sdmmc_0] Err: #Cmd_53 (0x297FE048)=&amp;gt;(E: 0x0100)(S: 0x00000000)__(L:896)(B:72/72)(I:0/1) ------------[ cut here ]------------ WARNING: CPU: 1 PID: 360 at /home/hs/vms-firmware/output/build/linux-backports-custom-6.1.97-1/./drivers/net/wireless/ti/cc33xx/sdio.c:95 cc33xx_sdio_raw_read+0x53/0xdc [cc33xx_sdio] Modules linked in: ccm k351P_MIPI(PO) mi_debug(PO) mi_venc(PO) mi_scl(PO) mi_ai(PO) mi_ldc(PO) mi_isp(PO) mi_ipu(PO) mi_vif(PO) mi_ao(PO) mi_aio(PO) mi_rgn(PO) mi_sensor(PO) mi_sys(PO) mi_common(PO) sch_fq cc33xx_sdio(O) cc33xx(O) mac80211(O) cfg80211(O) firmware_class compat(O) libarc4 CPU: 1 PID: 360 Comm: kworker/u5:0 Tainted: P O 5.10.117 #4 Hardware name: IFS Soc (Flattened Device Tree) Workqueue: cc33xx_wq irq_deferred_work [cc33xx] [ ] (unwind_backtrace) from [ ] (show_stack+0xb/0xc) [ ] (show_stack) from [ ] (dump_stack_lvl+0x61/0x74) [ ] (dump_stack_lvl) from [ ] (__warn+0x63/0x84) [ ] (__warn) from [ ] (warn_slowpath_fmt+0x3b/0x74) [ ] (warn_slowpath_fmt) from [ ] (cc33xx_sdio_raw_read+0x53/0xdc [cc33xx_sdio]) [ ] (cc33xx_sdio_raw_read [cc33xx_sdio]) from [ ] (cc33xx_raw_read+0x3f/0x60 [cc33xx]) [ ] (cc33xx_raw_read [cc33xx]) from [ ] (cc33xx_irq_locked+0x6d/0x178 [cc33xx]) [ ] (cc33xx_irq_locked [cc33xx]) from [ ] (irq_deferred_work+0x35/0xa0 [cc33xx]) [ ] (irq_deferred_work [cc33xx]) from [ ] (process_one_work+0xf9/0x164) [ ] (process_one_work) from [ ] (worker_thread+0x16b/0x1e0) [ ] (worker_thread) from [ ] (kthread+0xe7/0xf0) [ ] (kthread) from [ ] (ret_from_fork+0x11/0x30) Exception stack(0xc0c31fb0 to 0xc0c31ff8) 1fa0: 00000000 00000000 00000000 00000000 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ---[ end trace 06950ab910a428c2 ]--- cc33xx_sdio mmc0:0001:2: sdio read failed (-110) SDMMC1 &amp;gt;&amp;gt; [Hal_CARD_SetBustiming] LS mode. &amp;gt; [Hal_CARD_SetBustiming] DEFS mode. ] (unwind_backtrace) from [ ] (show_stack+0xb/0xc) [ ] (show_stack) from [ ] (dump_stack_lvl+0x61/0x74) [ ] (dump_stack_lvl) from [ ] (__warn+0x63/0x84) [ ] (__warn) from [ ] (warn_slowpath_fmt+0x3b/0x74) [ ] (warn_slowpath_fmt) from [ ] (ieee80211_reconfig+0x315/0x83a [mac80211]) [ ] (ieee80211_reconfig [mac80211]) from [ ] (ieee80211_restart_work+0x7d/0xe0 [mac80211]) [ ] (ieee80211_restart_work [mac80211]) from [ ] (process_one_work+0xf9/0x164) [ ] (process_one_work) from [ ] (worker_thread+0x16b/0x1e0) [ ] (worker_thread) from [ ] (kthread+0xe7/0xf0) [ ] (kthread) from [ ] (ret_from_fork+0x11/0x30) Exception stack(0xc0897fb0 to 0xc0897ff8) 7fa0: 00000000 00000000 00000000 00000000 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ---[ end trace 06950ab910a428c3 ]--- ------------[ cut here ]------------ WARNING: CPU: 1 PID: 18 at /home/hs/vms-firmware/output/build/linux-backports-custom-6.1.97-1/./net/mac80211/driver-ops.c:98 drv_remove_interface+0x31/0x5c [mac80211] p2p-dev-wlan0: Failed check-sdata-in-driver check, flags: 0x0 Modules linked in: ccm k351P_MIPI(PO) mi_debug(PO) mi_venc(PO) mi_scl(PO) mi_ai(PO) mi_ldc(PO) mi_isp(PO) mi_ipu(PO) mi_vif(PO) mi_ao(PO) mi_aio(PO) mi_rgn(PO) mi_sensor(PO) mi_sys(PO) mi_common(PO) sch_fq cc33xx_sdio(O) cc33xx(O) mac80211(O) cfg80211(O) firmware_class compat(O) libarc4 CPU: 1 PID: 18 Comm: kworker/1:0 Tainted: P W O 5.10.117 #4 Hardware name: IFS Soc (Flattened Device Tree) Workqueue: events_freezable ieee80211_restart_work [mac80211] [ ] (unwind_backtrace) from [ ] (show_stack+0xb/0xc) [ ] (show_stack) from [ ] (dump_stack_lvl+0x61/0x74) [ ] (dump_stack_lvl) from [ ] (__warn+0x63/0x84) [ ] (__warn) from [ ] (warn_slowpath_fmt+0x3b/0x74) [ ] (warn_slowpath_fmt) from [ ] (drv_remove_interface+0x31/0x5c [mac80211]) [ ] (drv_remove_interface [mac80211]) from [ ] (ieee80211_do_stop+0x503/0x564 [mac80211]) [ ] (ieee80211_do_stop [mac80211]) from [ ] (cfg80211_stop_p2p_device+0x33/0x90 [cfg80211]) [ ] (cfg80211_stop_p2p_device [cfg80211]) from [ ] (cfg80211_shutdown_all_interfaces+0x71/0x88 [cfg80211]) [ ] (cfg80211_shutdown_all_interfaces [cfg80211]) from [ ] (ieee80211_restart_work+0x8d/0xe0 [mac80211]) [ ] (ieee80211_restart_work [mac80211]) from [ ] (process_one_work+0xf9/0x164) [ ] (process_one_work) from [ ] (worker_thread+0x16b/0x1e0) [ ] (worker_thread) from [ ] (kthread+0xe7/0xf0) [ ] (kthread) from [ ] (ret_from_fork+0x11/0x30) Exception stack(0xc0897fb0 to 0xc0897ff8) 7fa0: 00000000 00000000 00000000 00000000 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ---[ end trace 06950ab910a428c4 ]--- [ 5][TX-C] 221.00-222.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 221.00-222.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 222.00-223.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 222.00-223.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 223.00-224.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 223.00-224.00 sec 0.00 Bytes 0.00 bits/sec [ 5][TX-C] 224.00-225.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 224.00-225.00 sec 0.00 Bytes 0.00 bits/sec ^C[ 5][TX-C] 225.00-225.41 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 7][RX-C] 225.00-225.41 sec 0.00 Bytes 0.00 bits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-225.41 sec 308 MBytes 11.5 Mbits/sec 106 sender [ 5][TX-C] 0.00-225.41 sec 0.00 Bytes 0.00 bits/sec receiver [ 7][RX-C] 0.00-225.41 sec 0.00 Bytes 0.00 bits/sec sender [ 7][RX-C] 0.00-225.41 sec 308 MBytes 11.5 Mbits/sec receiver iperf3: interrupt - the client has terminated # # cc33xx_wireshark_crash_log.txt</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/Wireless%2bInfrastructure">Wireless Infrastructure</category><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3351MOD">CC3351MOD</category></item><item><title>Forum Post: RE: CC3301: How to use SWD interface to toggle some GPIO</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698711/cc3301-how-to-use-swd-interface-to-toggle-some-gpio/6542576</link><pubDate>Wed, 18 Nov 2026 17:24:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:80115b51-b06a-4720-9431-71d094e49318</guid><dc:creator>Sabeeh Khan1</dc:creator><description>Hello Jerry, Yes this is possible through the Radio Tool in simplelink wifi toolbox. You can click on &amp;#39;Addons&amp;#39; and control the pins directly.</description></item><item><title>Forum Post: CC3551E: CCStudio for VS Code Unable to Resovle Compiler Reference</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698837/cc3551e-ccstudio-for-vs-code-unable-to-resovle-compiler-reference</link><pubDate>Wed, 18 Nov 2026 14:53:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:be4db16c-d6ab-446d-a01d-a729cdb1c4bf</guid><dc:creator>Peter Borenstein</dc:creator><description>Part Number: CC3551E Other Parts Discussed in Thread: CCSTUDIO I am using CCStudio for VS Code v1.0.2000 to import a project from C:\ti\simplelink_wifi_sdk_10_20_00_39\examples\rtos\LP_EM_CC35X1ET\demos\at_commands There is an error when selecting the ti or GNU compiler: -- Creating project: at_commands_LP_EM_CC35X1ET_freertos_ticlang ... NOTE: project-type not specified - defaulting to &amp;#39;Executable&amp;#39; ERROR: unable to resolve compiler reference: com.ti.arm.clang v4.0.4.LTS -- Creating project: at_commands_LP_EM_CC35X1ET_freertos_gcc ... NOTE: project-type not specified - defaulting to &amp;#39;Executable&amp;#39; NOTE: tool-version not specified - defaulting to &amp;#39;0.0&amp;#39; ERROR: unable to resolve compiler reference: com.ti.arm.gnu v0.0 I have both installed. How can I make the extention understand where the compilers are?</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3551E">CC3551E</category><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CCSTUDIO">CCSTUDIO</category><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/Wireless%2bInfrastructure">Wireless Infrastructure</category></item><item><title>Forum Post: RE: CC3351MOD: CC3351MOD on custom AM625 board: ROM acknowledges the whole 2nd loader container but never boots it (no HINT 0x10)</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1696568/cc3351mod-cc3351mod-on-custom-am625-board-rom-acknowledges-the-whole-2nd-loader-container-but-never-boots-it-no-hint-0x10/6542144</link><pubDate>Wed, 18 Nov 2026 09:52:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6c548f7a-caca-46fd-b643-775c21f70bdb</guid><dc:creator>Rajender Reddy Suram</dc:creator><description>e2e.ti.com/.../keonn_5F00_loggerPin_5F00_logs_5F00_till_5F00_2nd_5F00_loader_5F00_1.zip Hi ,i managed to get FW logs using logger pin in my board. Please check and suggest what may be wrong.What should be the expected SOP Mode? Thanks, Rajender</description></item><item><title>Forum Post: CC3301: How to use SWD interface to toggle some GPIO</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1698711/cc3301-how-to-use-swd-interface-to-toggle-some-gpio</link><pubDate>Wed, 18 Nov 2026 09:43:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f0c3792f-6d82-42f3-94c9-9794bb02190e</guid><dc:creator>Jerry Kuo</dc:creator><description>Part Number: CC3301 Hi team, My customer would like to toggle some GPIO during manufacturing line test. Is it possible to use SWD interface to support this feature ? Thank you.</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/Wireless%2bInfrastructure">Wireless Infrastructure</category><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3301">CC3301</category></item></channel></rss>