https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1655520/cc3501e-flash-less-mcu-with-mask-boot-rom/6394270Wed, 24 Jun 2026 21:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9f76cfa9-49f7-4a29-8184-360e276cc810BLiuHi Slava, The first stage bootloader is stored in ROM of the CC35XX. The external flash mainly stores Wi-Fi firmware, second stage bootloader, and vendor images; the SPI interface used with our external flash is QSPI / OSPI. This is used by our OTFDE to communicate with the external flash, and we provide a programmer binary (and CLI commands) to clean, debug, or flash the device. Let me know if you still have questions.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1658284/cc3220moda-cc3220modasm2mon---conducted-rf-testing-sample-custom-test-fixture-guide-for-regulatory-certification-anatel/6394214Wed, 24 Jun 2026 20:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:efa170b3-b90c-4221-b433-c3b0e7b54823Dylan HubbardHi Allan, 1. We do not. 2. There is no official guide - this may be something not commonly done or no guidance needed. However, my suggestion is as follows: Cut the trace around the circled area to isolate the PCB antenna from the RF path. THen you can solder the signal pin of the coax to the trace on the shield side. The ground area to the right of the circled point can be the mounting point for the coax shielding - just scrape the solder mask to expose enough copper for a strong connection.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/6394190Wed, 24 Jun 2026 19:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:61beea2b-2ebb-4136-8eeb-dd815b25a65eDylan HubbardHi Sri, Nothing special really, most critical thing is ESD safety so you aren&#39;t damaging parts.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/6394173Wed, 24 Jun 2026 19:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fe8a4fb9-7515-4dca-8eec-99bfa620372cJosh PrushingHi Aniruth, One more thing to try, can you try reconfiguring the DTS to use inband IRQ? You can comment out the following lines to do this: interrupt-parent = ; interrupts = ; You can reference this thread for more information: https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1508195/cc3351-wi-fi-locking-up-while-downloading-atmds62levm-m2-cc3351-linux-ti-staging-6-12/5811150#5811150 Best Regards, Josh Prushinghttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1658284/cc3220moda-cc3220modasm2mon---conducted-rf-testing-sample-custom-test-fixture-guide-for-regulatory-certification-anatelWed, 24 Jun 2026 19:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4e0ccd98-a689-4675-b6cb-c9cc487e2a77Allan DiasPart Number: CC3220MODA Hello, I am currently going through the ANATEL (Brazil) regulatory certification process for an end-product that utilizes the CC3220MODASM2MON module (the variant with the integrated chip antenna). To perform the mandatory conducted RF tests at the certification laboratory, we need an RF conducted path (coaxial connection) from the module&#39;s RF output. I have two questions regarding this: Does Texas Instruments provide or sell pre-conditioned/pre-convectorized samples or specific test fixtures for this module variant to assist with conducted regulatory testing? If TI does not supply these hardware samples, is there an official application note, layout guide, or reference procedure detailing the best practice to physically modify/bypass the integrated chip antenna on the module to solder a 50-Ohm coaxial pigtail for lab equipment connection? Thank you in advance for your support. Best regards,CC3220MODAhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6393952Wed, 24 Jun 2026 16:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:38aa24d6-40e7-4786-a9d9-d913b17f158cJosh PrushingHi Yogesh, Can you please provide the source code? From logs it seems to be initializing correctly. I am wondering if the AP Callback function is not functioning as expected. Feel free to send this through email if you do not wish to send here. Best Regards, Josh Prushinghttps://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/6393876Wed, 24 Jun 2026 15:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:247303dc-9c6d-4912-b9f9-da9df3a32d6cSabeeh Khan1Hi Lavanya, Let me see what I can do, but I think it would be easiest to test the m2-cc3351 on a board such as the am62x-sk (not the LP version) or the AM62P, AM62L, or AM62A boards. The prebuilt SDK images already have m2-cc3351 support for these boards. Unfortunately am62-lp-sk was not included.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/6393869Wed, 24 Jun 2026 15:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:afe125f6-e803-41cf-a336-ab78a45bf95fLavanya SundararajanHi Sabeeh Khan, Thank you. This helps, I wonder would you get me the right SD Card image so that I can quickly validate the WiFi Module, in parallel I can setup the Kernel sources and follow the steps given in the user guide? Thanks,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/6393851Wed, 24 Jun 2026 15:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b4348702-938b-4caf-b423-43d7cc68eb03Sabeeh Khan1Hi Lavanya, The link shared is correct. You can download and install the &#39;ti-processor-sdk-linux-am62xx-evm-12.00.00.07.04-Linux-x86-Install.bin&#39;. This is the processor SDK which contains the linux kernel sources. You can then follow documentation process as described here for modifying and compiling the new DTB: https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/12_00_00_07_04/exports/docs/linux/Foundational_Components_Kernel_Users_Guide.html#https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651593/cc3351-cc33xx-rtos-mcu-package-bundled-third-party-components-modified/6393808Wed, 24 Jun 2026 15:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:eb214e8b-4c91-4c06-a0ec-41f42abf1777ABHello, use TCP_NODELAY when you need low‑latency, immediate delivery of small writes and are willing to accept the extra packet overhead. If you’re bulk‑transferring data where throughput matters more than per‑byte latency, leave it disabled (the default) to let Nagle coalesce writes into full‑sized segments. In short, it should not be mandatory. NimBLE: We pulled from v1.7.0 and added patches on top. some were pulled from mainline and others were developed by us and are already pushed to mainline. LwIP: is using version  2.1.3https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1658026/bp-cc3301mod-cc33xx-kernel-patch-for-kernel-version-4-9Wed, 24 Jun 2026 07:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c9a1284d-2530-4b49-a53d-5028c5f40205Rahul ShahPart Number: BP-CC3301MOD Other Parts Discussed in Thread: CC3350 , Hello TI team, We are currently evaluating the CC3350 Wi-Fi module for a Linux-based platform. We have BP-CC3301MOD EVK Kit and trying to interface with SOC which have kernel version 4.9. I referred thread https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1616067/cc3351-cc3351-linux-driver-support-for-kernel-4-19-x and follow steps as below: 1. First apply the kernel patches from 1.0.2.10 CC33xx SDK. (https://www.ti.com/tool/download/CC33XX-LINUX-MPU/1.0.2.10) 2. Then apply patch from following path. I need patch for kernel 4.9 but as it is not available i have used 4.19 patch. https://github.com/TexasInstruments-Sandbox/cc33xx-linux-mpu-ports/blob/main/4.19.y/backport-1.0.2.10-to-4.19.y.patch After this still i see build issues as below : patch -p 0 dev); ^ drivers/net/wireless/ti/cc33xx/main.c: In function ‘eth_addr_inc’: drivers/net/wireless/ti/cc33xx/main.c:5145:2: error: implicit declaration of function ‘ether_addr_to_u64’ [-Werror=implicit-function-declaration] u64 u = ether_addr_to_u64(addr); ^ drivers/net/wireless/ti/cc33xx/main.c:5148:2: error: implicit declaration of function ‘u64_to_ether_addr’ [-Werror=implicit-function-declaration] u64_to_ether_addr(u, addr); ^ drivers/net/wireless/ti/cc33xx/main.c: In function ‘cc33xx_init_ieee80211’: drivers/net/wireless/ti/cc33xx/main.c:5347:15: error: ‘struct wiphy’ has no member named ‘max_sched_scan_reqs’ wl-&gt;hw-&gt;wiphy-&gt;max_sched_scan_reqs = 1; ^ drivers/net/wireless/ti/cc33xx/rx.c: In function ‘cc33xx_rx_status’: drivers/net/wireless/ti/cc33xx/rx.c:42:9: error: ‘struct ieee80211_rx_status’ has no member named ‘encoding’ status-&gt;encoding = RX_ENC_VHT; ^ drivers/net/wireless/ti/cc33xx/rx.c:42:22: error: ‘RX_ENC_VHT’ undeclared (first use in this function) status-&gt;encoding = RX_ENC_VHT; ^ drivers/net/wireless/ti/cc33xx/rx.c:42:22: note: each undeclared identifier is reported only once for each function it appears in drivers/net/wireless/ti/cc33xx/rx.c:45:9: error: ‘struct ieee80211_rx_status’ has no member named ‘encoding’ status-&gt;encoding = RX_ENC_HT; ^ drivers/net/wireless/ti/cc33xx/rx.c:45:22: error: ‘RX_ENC_HT’ undeclared (first use in this function) status-&gt;encoding = RX_ENC_HT; ^ drivers/net/wireless/ti/cc33xx/rx.c:49:9: error: ‘struct ieee80211_rx_status’ has no member named ‘encoding’ status-&gt;encoding = RX_ENC_LEGACY; ^ drivers/net/wireless/ti/cc33xx/rx.c:49:22: error: ‘RX_ENC_LEGACY’ undeclared (first use in this function) status-&gt;encoding = RX_ENC_LEGACY; ^ drivers/net/wireless/ti/cc33xx/rx.c:51:9: error: ‘struct ieee80211_rx_status’ has no member named ‘encoding’ status-&gt;encoding = 0; ^ drivers/net/wireless/ti/cc33xx/rx.c:98:8: error: ‘struct ieee80211_rx_status’ has no member named ‘nss’ status-&gt;nss = 1; ^ drivers/net/wireless/ti/cc33xx/rx.c: In function ‘wlcore_rx_getPacketData’: drivers/net/wireless/ti/cc33xx/rx.c:200:2: error: implicit declaration of function ‘skb_put_data’ [-Werror=implicit-function-declaration] skb_put_data(wl-&gt;partial_rx.skb, raw_buffer_ptr, available_data_bytes); once i fixed above errors , then i get another error like sdio_irq_work is not member of struct mmc_host: file : sdio.c , function : cc33xx_sdio_sync_irq , flush_delayed_work(&amp;host-&gt;sdio_irq_work); static void cc33xx_sdio_sync_irq(struct device *child) { struct cc33xx_sdio_glue *glue = dev_get_drvdata(child-&gt;parent); struct sdio_func *func = dev_to_sdio_func(glue-&gt;dev); struct mmc_host *host = func-&gt;card-&gt;host; if (mmc_inband_polling_host(func)) flush_work(&amp;glue-&gt;inband_irq_work); else flush_delayed_work(&amp;host-&gt;sdio_irq_work); } so if i fix this errors by disabling code , then when i try to load cc33xx driver on device it gets error as below : # insmod /mnt/flash/cc33xx.ko # insmod /mnt/flash/cc33xx_sdio.ko mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) vienna_set_mmc_clock: clk name vpl_mshc0_clk, set bus_hz 100000000, div 00000000 val 00000000 mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 25000000Hz, actual 25000000HZ div = 2) cc33xx_sdio mmc0:0001:2: Using SDIO in-band IRQ # vienna_set_mmc_clock: clk name vpl_mshc0_clk, set bus_hz 50000000, div 00000008 val c2c4d780 mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) vienna_set_mmc_clock: clk name vpl_mshc0_clk, set bus_hz 100000000, div 00000000 val 00000000 mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 25000000Hz, actual 25000000HZ div = 2) random: crng init done random: 7 urandom warning(s) missed due to ratelimiting wlcore: ERROR boot IRQ timeout vienna_set_mmc_clock: clk name vpl_mshc0_clk, set bus_hz 50000000, div 00000000 val c2c8f180 wlcore: ERROR FW download failed I doubt like driver is still not compatible with 4.9 kernel. can you please check and provide me updated patch with kernel 4.9 version. Here is dts changes : &amp;mmc0 { status = &quot;okay&quot;; bus-width = ; max-frequency = ; non-removable; cap-sdio-irq; no-sd; no-mmc; cap-power-off-card; disable-wp; keep-power-in-suspend; no-1-8-v; mmc-pwrseq = ; wifi@2 { compatible = &quot;ti,cc33xx&quot;; reg = ; }; }; Regards, Rahul ShahCC3350BP-CC3301MODhttps://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/6393027Wed, 24 Jun 2026 05:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d43b66c4-e527-411a-ad04-3c971d83c7b8Lavanya SundararajanHi Sabeeh Khan, We used the SD card image tisdk-default-image-am62xx-lp-evm-12.00.00.07.04.rootfs.wic from https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM62X/12.00.00.07.04 and rootfs has only dtbo file. Kindly share the right sdk which has the correct dts file and the procedure for bring up the wlan interfacehttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1649926/cc3351-cc3351-ble-tx-in-calibration-mode-for-certification/6393006Wed, 24 Jun 2026 04:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:20c837fd-d7b1-4e9d-9a85-2ea5362f26c8Romain CazalisHi Josh, we tried different things but never managed to get BLE TX running. As mentioned in another ticket, we will use XDS110 board and SimpleLink tool to get BLE TX running. This works fine. I will consider this ticket closed. Thanks for your support. Romainhttps://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/6393003Wed, 24 Jun 2026 04:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:32335c69-de3a-413e-a360-e3aca47953e8Aniruth KumarHi Dean Ramsier Thank you for the clarification. Josh Prushing We are currently on Processor SDK Android AM62P 11.00.01 . Could you let us know which upcoming Processor SDK Android release will include this cc33xx fix (1.2.0.10+), and the expected timeline for that release?https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1654547/cc3351-configuration-file/6393002Wed, 24 Jun 2026 04:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:818599dd-c6e4-49c9-8870-394980024c68Romain CazalisHi Josh, unfortunately, as we run Zephyr with our own ported driver, my direct commands will not be identical to yours. We got a newly released CC3351 Zephyr driver from TI and we&#39;ll switch to it once we have a bit more time. We may get a better behaviour. I am in China now and spent some time with our certification lab. I manage to get correct TX power when I use an XDS110 board (and SimpleLink tool) wired to the SWD interface on our module. It is still not the case when I run our firmware implementing the manufacturing commands. So I have decided to use XDS110 boards. This solves my issue and I shall be able to pass certification. I will stop trying to get normal TX power with our own implementation of manufacturing commands firmware, we have spent too much time already. This also solves another ticket ( CC3351: CC3351 BLE TX in calibration mode for certification ). We are still unable to get BLE TX with our firmware. It works with XDS110. Two birds with same stone. I will consider both issues closed. Thanks again for your support.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/6392820Wed, 24 Jun 2026 01:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:53640c68-1b89-4ab0-99db-ed48ff168f95ShengYi WangThank you.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1657811/cc2564c-automotive-grade/6392523Tue, 23 Jun 2026 19:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c18ec254-8cf1-4167-9bff-241b0bf82e5fDylan HubbardHi Yousif, This device is not Automotive grade - you can browse TI&#39;s automotive portfolio here to find a device to suit your needs.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/6392495Tue, 23 Jun 2026 19:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:48dd2783-0c52-4c22-8194-0fc7c341cd24Dean RamsierI think you&#39;re thinking of the firmware file. cc33xx-nvs.bin is not firmware, and not used. That message can be ignored. It generally isn&#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.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1651997/cc3300mod-require-information-on-validating-ti-sdk-api/6392446Tue, 23 Jun 2026 18:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8b92c9ce-c6df-48b6-9f71-bcc4cd7f4f73YogeshGHi Josh Prushing This is very good information. We parsed log using logger.bin and found all checkpoint in log which indicate CC3300 fw initialize correctly. We are testing following sequence and AP point is not visible. int ret = cmdWlanStartCallback(&quot;NULL&quot;);//Wlan_Start(WlanStackEventHandler); osi_Sleep(10); ret = cmdWlanRoleUpApCallback(&quot;-s \&quot;TISDKAPYOG\&quot; -t OPEN -r \&quot;00\&quot;&quot;); Then we take out all signal form our board and connected TI eval board and executed our code and still AP is not visible. This indicates something missing in our host side implementation. Attached is parsed log from our side. Our queries: Do you see something in log for which AP is not showing. Once host send command to cc3300 for RoleUpAp, what is the role of Host so that AP visible on mobile. What is possible missing thing at Host side, for which AP not visible on mobile. e2e.ti.com/.../CC3300Log18JuneWlanInitWlanRoleUPOpen.csv Thanks... Yogeshhttps://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/6392432Tue, 23 Jun 2026 18:33:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:60e63baf-f123-41d5-bf9c-02ef2455eea0Sabeeh Khan1Hi 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