<?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: CC2564C: Automotive Grade</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1657811/cc2564c-automotive-grade/6392523</link><pubDate>Tue, 23 Jun 2026 19:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c18ec254-8cf1-4167-9bff-241b0bf82e5f</guid><dc:creator>Dylan Hubbard</dc:creator><description>Hi Yousif, This device is not Automotive grade - you can browse TI&amp;#39;s automotive portfolio here to find a device to suit your needs.</description></item><item><title>Forum Post: RE: CC3301: CC3301 (M.2) WiFi driver crash with SDIO -110 timeout after sustained network activity on AM62P Android 16</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1652995/cc3301-cc3301-m-2-wifi-driver-crash-with-sdio--110-timeout-after-sustained-network-activity-on-am62p-android-16/6392495</link><pubDate>Tue, 23 Jun 2026 19:21:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:48dd2783-0c52-4c22-8194-0fc7c341cd24</guid><dc:creator>Dean Ramsier</dc:creator><description>I think you&amp;#39;re thinking of the firmware file. cc33xx-nvs.bin is not firmware, and not used. That message can be ignored. It generally isn&amp;#39;t sufficient to change just the driver, or the firmware or the conf.bin between releases. They are intrinsically tied together with shared data structures. A complete update to a new SDK is required, unless you know there are no incompatible changes between versions.</description></item><item><title>Forum Post: RE: CC3300MOD: Require information on validating TI SDK API</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6392446</link><pubDate>Tue, 23 Jun 2026 18:45:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8b92c9ce-c6df-48b6-9f71-bcc4cd7f4f73</guid><dc:creator>YogeshG</dc:creator><description>Hi Josh Prushing This is very good information. Tomorrow we will capture log with logger.bin and will compare result against your result, since laptop with tool is on office. The log which you shared is for cc3300 R8_1 SDK? It is for which device CC3301/CC3300? For CC3300 and CC3301 logger pin log will be same or different? Attached is the raw binary which we captured for our device for condition wlan_start, Wlan_role_UP_AP_Open. Please check once at your end by selecting logger.bin and let us know whether it is log as expected or not and AP functionality is working correctly or not? e2e.ti.com/.../2026_5F00_06_5F00_18_5F00_17_5F00_47_5F00_55_5F00_RoleUpAP.zip Thanks... Yogesh</description></item><item><title>Forum Post: RE: CC3351: CC3351 M2 card is not detected in SK-AM62-LP EVM</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1656381/cc3351-cc3351-m2-card-is-not-detected-in-sk-am62-lp-evm/6392432</link><pubDate>Tue, 23 Jun 2026 18:33:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:60e63baf-f123-41d5-bf9c-02ef2455eea0</guid><dc:creator>Sabeeh Khan1</dc:creator><description>Hi Lavanya, I would recommend to start from the DTS within the SDK rather than de-compiling the DTBO and DTB. exp2 is clearly defined here in k3-am62-lp-sk.dts: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts?h=ti-linux-6.18.y#n168</description></item><item><title>Forum Post: RE: CC3301: CC3301 (M.2) WiFi driver crash with SDIO -110 timeout after sustained network activity on AM62P Android 16</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1652995/cc3301-cc3301-m-2-wifi-driver-crash-with-sdio--110-timeout-after-sustained-network-activity-on-am62p-android-16/6392395</link><pubDate>Tue, 23 Jun 2026 18:00:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8592a646-696f-43d9-bae7-76ce5903fc84</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Aniruth, I&amp;#39;m not sure what version of the SDK is included in the Android release, but you can find the latest cc33xx SDK here, which also has a AM62P Yocto image: https://www.ti.com/tool/download/CC33XX-LINUX-MPU Find the cc33xx-nvs.bin and place this in /lib/firmware/ti-connectivity/. If there is already one there, replace it. Let me know if this resolves the issue. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: CC3300MOD: Require information on validating TI SDK API</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6392391</link><pubDate>Tue, 23 Jun 2026 17:55:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:eb598032-a1d9-491d-90a0-8fc92633511e</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Yogesh, Instead of choosing CC3300 in the &amp;quot;Device Part Number&amp;quot;, please select &amp;quot;Custom Parser File&amp;quot; as seen below. There will be a new option called &amp;quot;Parser Bin&amp;quot;, this is where you upload logger.bin file. All other steps are correct. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: CC3300MOD: Require information on validating TI SDK API</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6392382</link><pubDate>Tue, 23 Jun 2026 17:51:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:98d68ff4-7acd-44ed-82ff-43579fe208c1</guid><dc:creator>YogeshG</dc:creator><description>Hi Josh Prushing We are using logger tool as below. We are using &amp;quot;Online Parser&amp;quot; and started application using &amp;quot;Start&amp;quot; button Wireshark window opened. Once log captured, we used to copy log from Wireshark and shared with you. Not remembering that we have selected &amp;quot;logger.bin&amp;quot;. Attached &amp;quot;logger.bin&amp;quot; present in our SDK and all other binaries. e2e.ti.com/.../1882.wifi_5F00_fw.zip Please tell procedure to capture log using logger.bin and how it different from procedure which we followed above. Regards... Yogesh</description></item><item><title>Forum Post: CC3351: Query regarding any special precautions to be taken during the assembly process</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1657875/cc3351-query-regarding-any-special-precautions-to-be-taken-during-the-assembly-process</link><pubDate>Tue, 23 Jun 2026 17:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6fc4e847-7351-4fd4-b46c-e16d51458056</guid><dc:creator>Sri Vamsi V</dc:creator><description>Part Number: CC3351 Hi Everyone For this CC3351ENJARSBR Part Number any special precautions to be taken during the assembly process.</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC3351">CC3351</category></item><item><title>Forum Post: RE: CC3351: CC3351 M2 card is not detected in SK-AM62-LP EVM</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1656381/cc3351-cc3351-m2-card-is-not-detected-in-sk-am62-lp-evm/6392355</link><pubDate>Tue, 23 Jun 2026 17:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c5d4ab30-6c53-4f15-84ab-71f7e61091d2</guid><dc:creator>Lavanya Sundararajan</dc:creator><description>Hi, In the dts file I see only exp1 exp1 = &amp;quot;/fragment@0/__overlay__/regulator-30:gpios:0&amp;quot;, &amp;quot;/fragment@3:target:0&amp;quot;;</description></item><item><title>Forum Post: RE: CC3351: CC33xx Wi‑Fi/BT coexistence control configuration parameters in INI file?</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1656574/cc3351-cc33xx-wi-fi-bt-coexistence-control-configuration-parameters-in-ini-file/6392333</link><pubDate>Tue, 23 Jun 2026 17:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:52fd1de3-4c9b-4ed3-9deb-d15fb356a70e</guid><dc:creator>Josh Smith</dc:creator><description>Hi ShengYi Wang, To clarify more, are you referring to internal WiFi/BLE coexistence or external 3-Wire PTA WiFi BLE coexistence? If referring to internal, there are not any control parameters for you to configure. If referring to external COEX, the device supports 3-Wire PTA which can be configured in the INI CORE [COEX_CONFIGURATION] section. You can find more information about this in the CC33Conf Tool Guide tab of the Linux CC33xx User Guide Hopefully this helps. Josh</description></item><item><title>Forum Post: RE: CC3235MODAS: Plan for KC Certifications</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1653510/cc3235modas-plan-for-kc-certifications/6392307</link><pubDate>Tue, 23 Jun 2026 16:55:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:015df5ae-764b-478d-bdc0-1a5a6e2e2612</guid><dc:creator>Josh Smith</dc:creator><description>Hi Sun Young Ham, This report is also found on Simplelink-CC3xxx-Certification page under CC32xx-Reports. The file is found in the CE folder and is named CC3235MODS,SF LVD report-L092433L420_final.pdf Once Change in ID is complete, this also will apply to your system. Best, Josh</description></item><item><title>Forum Post: RE: CC3351: CC3351 M2 card is not detected in SK-AM62-LP EVM</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1656381/cc3351-cc3351-m2-card-is-not-detected-in-sk-am62-lp-evm/6392299</link><pubDate>Tue, 23 Jun 2026 16:50:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4a0599d5-5702-4e52-a766-8a83e9e22e55</guid><dc:creator>Sabeeh Khan1</dc:creator><description>Hi Lavanya, Yes, needs to be changed to .</description></item><item><title>Forum Post: RE: CC3300MOD: Require information on validating TI SDK API</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6392237</link><pubDate>Tue, 23 Jun 2026 16:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a124d1d0-891c-44f3-8262-dbf675bfe6ab</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Yogesh, The logs you sent for the CC3300 side do not make sense, can you confirm you are using the custom parser in the toolbox logger? This should be the logger.bin in the cc3300 R8_1 SDK. It does not make sense that you are receiving a TWT error right after invoking RAM bootloader. It should look something like this: e2e.ti.com/.../Custom_5F00_parser_5F00_logs_5F00_correct.csv Can you upload the logger.bin you are using when you collect logs through the toolbox or provide your steps to collect the 18 June logs? I am looking for the following lines to confirm proper initialization that are currently missing from your current logs: -------------Validation Start ------------- -------------Container Validation Success ----------------- -------------Invoking WSOC FW ----------------- Main Init finished successfully, Firmware version cc3xxx_rev_ .... Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: CC3351: CC3351 M2 card is not detected in SK-AM62-LP EVM</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1656381/cc3351-cc3351-m2-card-is-not-detected-in-sk-am62-lp-evm/6392205</link><pubDate>Tue, 23 Jun 2026 15:59:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:98073724-f2a9-450f-a0ae-09c7942b557a</guid><dc:creator>Lavanya Sundararajan</dc:creator><description>Hi Sabeeh Khan1 , I converted the k3-am625-sk-m2-cc3351.dtbo to readable k3-am625-sk-m2-cc3351.dts regulator-30 { compatible = &amp;quot;regulator-fixed&amp;quot;; regulator-name = &amp;quot;wlan_lten&amp;quot;; regulator-min-microvolt = ; regulator-max-microvolt = ; vin-supply = ; gpios = ; enable-active-high; phandle = ; }; should I change gpios = ; ?</description></item><item><title>Forum Post: RE: CC3351: Firmware doesn't reboot after crash</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1643864/cc3351-firmware-doesn-t-reboot-after-crash/6392017</link><pubDate>Tue, 23 Jun 2026 14:14:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8f783a02-7758-4d5a-b74a-c4bb6d6a5cd3</guid><dc:creator>Ga&amp;#233;tan Froissard</dc:creator><description>Hello Josh, We did update to MCU R9 but we didn&amp;#39;t do the switch from our Zephyr driver to TI&amp;#39;s. I close this ticket until we made it to reopen it if necessary. Thanks for your help, Ga&amp;#233;tan</description></item><item><title>Forum Post: RE: CC3351: MCU SDK preR9: BLE ready event</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1649245/cc3351-mcu-sdk-prer9-ble-ready-event/6392014</link><pubDate>Tue, 23 Jun 2026 14:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:748f417a-54b7-4f99-808d-955cfc012f70</guid><dc:creator>Ga&amp;#233;tan Froissard</dc:creator><description>Hello Josh, Sorry for the delay. I&amp;#39;ve seen in the SDK that there is a timeout on a semaphore. I think on Zephyr it wait for this timeout which is 1 seconds. For now, we will live with it but at the end we would like to avoid it. I&amp;#39;ve also checked on the code from https://github.com/TexasInstruments/simplelink-hal_ti/releases/tag/218d961-ti-9.22.00_ea and it use the same mechanism of waiting with semaphore. Thanks, Ga&amp;#233;tan</description></item><item><title>Forum Post: CC2564C: Automotive Grade</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1657811/cc2564c-automotive-grade</link><pubDate>Tue, 23 Jun 2026 13:50:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:079f8fcd-dc79-4e2d-9974-d901c18b5657</guid><dc:creator>Yousif Ibrahim</dc:creator><description>Part Number: CC2564C Hello TI Team, I was looking to find documation on if this component is Automotive Grade or not (AEC grade).</description><category domain="https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/tags/CC2564C">CC2564C</category></item><item><title>Forum Post: RE: CC3551E: Power consumption of the CC3551</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1654269/cc3551e-power-consumption-of-the-cc3551/6391771</link><pubDate>Tue, 23 Jun 2026 10:27:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:fc22aaf1-f8c4-419a-a9ee-be6c5c81aa13</guid><dc:creator>Aljaž Krašna</dc:creator><description>Hi, I tried re-enabling the AUTOIP and IGMP, settings corresponding timer intervals (AUTOIP_TMP_INTERVAL, IGMP_TMP_INTERVAL) to 250 ms and XTAL_SettlingTime to 0x2EE0 (12000), the consumption is comparable to tje default settings: AUTIP and IGMP disabled and XTAL_SettlingTime 1700. Due to the fact the AUTOIP and IGMP are not required in our use case (device has a static IP or it operates in networks with DHCP server + device does not use sharable address) I would stick to my initial configuration. Or, do you have second thoughts about such a configuration? Regarding the &amp;quot;ping issue&amp;quot;. I was able to re-produce the issue on several access points. You said that you tried to re-produce the behaviour on your side. Can you try to use the sources that I posted previously? Kind regards, Aljaz</description></item><item><title>Forum Post: RE: WL1837MOD: FCC / EMC testing, spurious emission, 2nd harmonics over limit</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1646884/wl1837mod-fcc-emc-testing-spurious-emission-2nd-harmonics-over-limit/6391632</link><pubDate>Tue, 23 Jun 2026 08:41:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:51c15dd4-e0be-4d69-ba79-8e4763760f63</guid><dc:creator>Jonathan Cohen</dc:creator><description>Hello Josef, Happy to hear that the 2nd harmonic has gone down to allow you to pass. This is the same method that we passed our own certification. The Tune channel command should be set to 40MHz for optimal 2nd harmonic, but you should still be transmitting at 20MHz when certifying. So the start_tx should be set to 20MHz, while tune_channel is set to 40MHz. Regards, Jonathan</description></item><item><title>Forum Post: RE: CC3135: Relation between MaxSleepTimeMs and Region on 5 GHz network</title><link>https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1647752/cc3135-relation-between-maxsleeptimems-and-region-on-5-ghz-network/6391619</link><pubDate>Tue, 23 Jun 2026 08:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:98217455-7928-4695-a5af-45ba14d97ccd</guid><dc:creator>Aljaž Krašna</dc:creator><description>Hi, ok, thank you for the info. Kind regards</description></item></channel></rss>