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/1694261/cc3220moda-i-need-example-codes-for-wi-fi-direct-p2p-on-cc3220modaFri, 30 Oct 2026 15:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:388d324b-80d8-440a-ab9f-8534a14de0fdTim CruisePart Number: CC3220MODA Other Parts Discussed in Thread: CC3220S Dear TI Technical Support, I am designing a portable device using Wi-Fi data transfer without a router or internet. So, I think of &quot;Wi-Fi Direct&quot; P2P. Data sheet of CC3220MODA claims that it supports Wi-Fi Direct. Then, I installed the CCS Studio SDK for CC3220S Launchpad, but there is no example project on Wi-Fi Direct. Please advice. Yours faithfully, TimmyCC3220MODAcc3220sPortable Electronicshttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6526259Fri, 30 Oct 2026 13:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:06bac213-1d7d-4c43-963f-5d0e09cfa7fbDean RamsierYour device tree is configured for serdev (it has the bluetooth node in the uart node). If using serdev, there is no tty and btattach is not relevant. serdev, assuming you have that in your kernel config, handles creating the hci device automatically. Either remove the bluetooth node from the device tree and use btattach, or leave the bluetooth node and rely on serdev. But if using serdev, make sure that is also in your kernel config. If the above doesn&#39;t just work, then you need to put an oscilloscope on your UART pins and figure out if you have the hardware configured correctly (correct UART, correct pins, correct directions, DCE vs DTE etc).https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6525785Fri, 30 Oct 2026 04:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3d2d6d1f-fff4-4d67-a0a3-8aa4b2c05e12saurav pandyaHi sabeeh, We already use &#39;cc33xx-supply= ;&#39; in my change device tree. &amp;uart4 { pinctrl-names = &quot;default&quot;; pinctrl-0 = ; uart-has-rtscts; status = &quot;okay&quot;; bluetooth { compatible = &quot;ti,cc33xx-bt&quot;; cc33xx-supply = ; max-speed = ; host-wakeup-gpios = ; pinctrl-names = &quot;default&quot;; pinctrl-0 = ; interrupt-parent = ; interrupts = ; status = &quot;okay&quot;; }; }; also, we have checked below command * reboot * load drivers * echo 1 &gt; /sys/kernel/debug/ieee80211/phy0/cc33xx/ble_enable * btattach -B /dev/ttymxc0 -S 115200 -P h4 &amp; using this command we got below error: [ 274.334903] Bluetooth: hci0: Opcode 0x0c03 failed: -110 Alos I have checked if we are not using than we have to set the power save mode to 0. Please confirm on this. and please mention which command use to put BLE in active power mode. Thanks, Sauravhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1692734/cc3351mod-software-config-issues/6525602Thu, 29 Oct 2026 23:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d8a98906-cef4-422b-94b4-c14ea8d33767BLiuHi Blake, CC3351 supports enabling another advertisement while a peripheral connection is active. The following commands (I am using my own GATT server setup) should work: cd /usr/share/cc33xx/ ./set_power_mode.sh 0 ./ble_enable.sh hciconfig hci0 up cd wifible_provisioning_demo ./__cc33xx_adv_bluez_btmgmt_gatt_server.sh &amp; btmon &amp; bluetoothctl advertise peripheral &amp; hcitool -i hci0 cmd 0x08 0x0039 01 01 01 00 00 00 The BTMON shows successful enabling of another advertisement in the results. Results: root@am335x-evm:~# cd /usr/share/cc33xx/ root@am335x-evm:/usr/share/cc33xx# ./set_power_mode.sh 0 root@am335x-evm:/usr/share/cc33xx# ./ble_enable.sh root@am335x-evm:/usr/share/cc33xx# [ 107.971213] Bluetooth: MGMT ver 1.22 [ 108.003161] NET: Registered PF_ALG protocol family [ 108.080363] cryptd: max_cpu_qlen set to 1000 root@am335x-evm:/usr/share/cc33xx# hciconfig hci0 up root@am335x-evm:/usr/share/cc33xx# cd wifible_provisioning_demo root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# ./__cc33xx_adv_bluez_btmgmt_gatt_server.sh &amp; [1] 796 root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# *** io_capab: DisplayOnly *** spawn bluetoothctl --agent=DisplayOnly [bluetooth]# default-agent No agent is registered Agent registered [CHG] Controller F8:FB:90:12:1D:27 Pairable: yes [bluetooth]# hci0: Primary controller addr F8:FB:90:12:1D:27 version 13 manufacturer 13 class 0x000000 supported settings: powered connectable discoverable bondable le advertising secure-conn debug-keys privacy static-addr phy-configuration current settings: powered bondable le secure-conn name TEXAS short name [CHG] Controller F8:FB:90:12:1D:27 Powered: no [CHG] Controller F8:FB:90:12:1D:27 Discovering: no [bluetooth]# hci0 Set Powered complete, settings: bondable le secure-conn hci0 Set Low Energy complete, settings: bondable le secure-conn hci0 Set Connectable complete, settings: connectable bondable le secure-conn hci0 Set Debug Keys complete, settings: connectable bondable le secure-conn hci0 Set Secure Connections complete, settings: connectable bondable le secure-conn hci0 Set Bondable complete, settings: connectable bondable le secure-conn hci0 Set Bondable complete, settings: connectable bondable le secure-conn hci0 Set Privacy complete, settings: connectable bondable le secure-conn [CHG] Controller F8:FB:90:12:1D:27 Alias: cc33xxble [bluetooth]# hci0 Set Advertising complete, settings: connectable bondable le advertising secure-conn hci0 Set Powered complete, settings: powered connectable bondable le advertising secure-conn [CHG] Controller F8:FB:90:12:1D:27 Powered: yes [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000fff0-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000fff0-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller F8:FB:90:12:1D:27 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb [CHG] Device 90:DD:5D:6B:58:02 Connected: yes [WallSt30]# [ 165.568900] omap_intc_handle_irq: spurious irq! [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0006 00001801-0000-1000-8000-00805f9b34fb Generic Attribute Profile [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0006/char0007 00002a05-0000-1000-8000-00805f9b34fb Service Changed [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0006/char0007/desc0009 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000a 0000180a-0000-1000-8000-00805f9b34fb Device Information [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000a/char000b 00002a29-0000-1000-8000-00805f9b34fb Manufacturer Name String [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000a/char000d 00002a24-0000-1000-8000-00805f9b34fb Model Number String [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000f d0611e78-bbb4-4591-a5f8-487910ae4366 Vendor specific [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000f/char0010 8667556c-9a37-4c91-84ed-54ee27d90049 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000f/char0010/desc0012 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service000f/char0010/desc0013 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0014 9fa480e0-4967-4542-9390-d343dc5d04ae Vendor specific [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0014/char0015 af0badb1-5b99-43cd-917a-a77bc549e3cc Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0014/char0015/desc0017 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0014/char0015/desc0018 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service001e 0000180f-0000-1000-8000-00805f9b34fb Battery Service [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service001e/char001f 00002a19-0000-1000-8000-00805f9b34fb Battery Level [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service001e/char001f/desc0021 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0022 00001805-0000-1000-8000-00805f9b34fb Current Time Service [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0022/char0023 00002a2b-0000-1000-8000-00805f9b34fb Current Time [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0022/char0023/desc0025 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0022/char0026 00002a0f-0000-1000-8000-00805f9b34fb Local Time Information [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028 7905f431-b5ce-4e99-a40f-4b1e122d00d0 Vendor specific [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char0029 69d1d8f3-45e1-49a8-9821-9bbdfdaad9d9 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char0029/desc002b 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char002c 9fbf120d-6301-42d9-8c58-25e699a21dbd Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char002c/desc002e 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char002f 22eac6e9-24d6-4bb5-be44-b36ace7c7bfb Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0028/char002f/desc0031 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032 89d3502b-0f36-433a-8ef4-c502ad55f8dc Vendor specific [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0033 9b3c81d8-57b1-4a8a-b8df-0e56f7ca51c2 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0033/desc0035 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0033/desc0036 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0037 2f7cabce-808d-411f-9a0c-bb92ba96c102 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0037/desc0039 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char0037/desc003a 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char003b c6b2f38c-23ab-46d8-a6ab-a3a870bbd5d7 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service0032/char003b/desc003d 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Primary Service (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service003e e43a1c28-8b72-4646-84fa-192b8f345c3b Vendor specific [NEW] Characteristic (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service003e/char003f f7da4085-bbe7-42f4-9727-6ca60fe3a1a5 Vendor specific [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service003e/char003f/desc0041 00002900-0000-1000-8000-00805f9b34fb Characteristic Extended Properties [NEW] Descriptor (Handle 0x0000) /org/bluez/hci0/dev_90_DD_5D_6B_58_02/service003e/char003f/desc0042 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration [CHG] Device 90:DD:5D:6B:58:02 ServicesResolved: yes [CHG] Device 90:DD:5D:6B:58:02 Paired: yes [WallSt30]# [1]+ Done ./__cc33xx_adv_bluez_btmgmt_gatt_server.sh root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# btmon &amp; [1] 829 root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# Bluetooth monitor ver 5.65 = Note: Linux version 6.1.83-ti-gc1c2f1971fbf (armv7l) 0.804796 = Note: Bluetooth subsystem version 2.22 0.804816 = New Index: F8:FB:90:12:1D:27 (Primary,UART,hci0) [hci0] 0.804823 = Open Index: F8:FB:90:12:1D:27 [hci0] 0.804829 = Index Info: F8:FB:90:12:1D:27 (Texas Instruments Inc.) [hci0] 0.804832 @ MGMT Open: bluetoothd (privileged) version 1.22 {0x0001} 0.804839 root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# bluetoothctl advertise peripheral &amp; [2] 830 root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# @ MGMT Command: Add Extended Advertising Parameters (0x0054) plen 18 {0x0001} [hci0] 7.212607 Instance: 1 Flags: 0x00000001 Switch into Connectable mode Duration: 0 Timeout: 0 Min advertising interval: 0.000 msec (0x0000) Max advertising interval: 0.000 msec (0x0000) TX power: 0 dbm (0x00) HCI Event: Command Complete (0x0e) plen 5 #2 [hci0] 7.218143 LE Set Extended Advertising Parameters (0x08|0x0036) ncmd 1 Status: Success (0x00) TX power (selected): 10 dbm (0x0a) @ MGMT Event: Command Complete (0x0001) plen 7 {0x0001} [hci0] 7.218247 Add Extended Advertising Parameters (0x0054) plen 4 Status: Success (0x00) Instance: 1 TX power: 10 dbm (0x0a) Available adv data len: 251 Available scan rsp data len: 251 @ MGMT Command: Add Extended Advertising Data (0x0055) plen 14 {0x0001} [hci0] 7.221690 Instance: 1 Advertising data length: 3 Flags: 0x06 LE General Discoverable Mode BR/EDR Not Supported Scan response length: 0 @ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 7.222073 Add Extended Advertising Data (0x0055) plen 1 Status: Success (0x00) Instance: 1 [CHG] Controller F8:FB:90:12:1D:27 SupportedInstances: 0x13 (19) [CHG] Controller F8:FB:90:12:1D:27 ActiveInstances: 0x01 (1) [CHG] Controller F8:FB:90:12:1D:27 SupportedInstances: 0x13 (19) [CHG] Controller F8:FB:90:12:1D:27 ActiveInstances: 0x01 (1) [WallSt30]# Advertising object registered Tx Power: off Name: off Appearance: off Discoverable: on root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo# hcitool -i hci0 cmd 0x08 0x0039 01 01 01 00 00 00 @ RAW Open: hcitool (privileged) version 2.22 {0x0002} 19.550212 @ RAW Close: hcitool {0x0002} 19.550818 @ RAW Open: hcitool (privileged) version 2.22 {0x0002} 19.551178 @ RAW Close: hcitool {0x0002} 19.551435 @ RAW Open: hcitool (privileged) version 2.22 {0x0002} [hci0] 19.551802 HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 19.558292 LE Set Extended Advertising Enable (0x08|0x0039) ncmd 1 Status: Success (0x00) &gt; HCI Event: 0x0e plen 4 01 39 20 00 @ RAW Close: hcitool {0x0002} [hci0] 19.558836 root@am335x-evm:/usr/share/cc33xx/wifible_provisioning_demo#https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1685108/cc3351-ble-advertising-while-connected/6525437Thu, 29 Oct 2026 19:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:27371c27-daa0-4463-8477-f39ba9facd9cDean RamsierHi Brandon, I can see this is working for you, but it still fails for me. The call to LE Set Extended Advertising Enable is failing (rejected by radio firmware with error code 0x12) on my platform. I&#39;m still trying to figure out why. I know I&#39;m using a newer kernel version and newer BlueZ stack than you are (kernel v6.18, BlueZ stack v5.79 and BlueZ stack 5.87). There are a number of differences in the HCI commands going to the radio, but I haven&#39;t yet been able to figure out what the culprit is. Still working on it... Deanhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1692159/cc3551e-support-for-tpc/6525228Thu, 29 Oct 2026 16:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:37b41bbb-7b44-44d4-8f27-95676874eb18Dean RamsierFor what it&#39;s worth, there is no TPC &quot;protocol&quot; where the AP tells the client to reduce power based on TPC. The AP can implement a local regulatory maximum, but that is separate from TPC. TPC is implemented dynamically on the client. The client decides when to reduce power, and by how much. The regulations just say that it must be implemented in certain configurations, and the implementation must be able to reduce power by at least X amount. But it is silent on when exactly it must reduce power and by how much using its TPC mechanism. There are standards based mechanisms where the AP and client exchange information (link quality, TX power etc) that can be used by the TPC algorithm to determine optimal TX power. But the actual decision to reduce power, and by how much, remains with the client. Cisco CCX did have an explicit mechanism to do this, but that isn&#39;t TPC and is not standard.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693666/cc3351mod-clarification-on-missing-regulatory-db-and-cc33xx-nvs-bin-during-cc3351mod-boot/6525213Thu, 29 Oct 2026 16:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:36ec00bf-04a3-48a2-ac52-2e3c72f6af22Dean RamsierThe .nvs file is not used, you can ignore that message. Regulatory.db is the regulatory database and contains the country specific rules. You need to have that, but it isn&#39;t part of the TI deliverable. You need to provide that, typically from the upstream wireless-regdb project.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693325/cc3551e-mcu-stalls-for-hundreds-of-milliseconds-in-lpds-when-using-preferred-xtal_settlingtime-0x2ee0/6525158Thu, 29 Oct 2026 15:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f442b9ce-ef48-436b-b10d-71ca383a04e3Shlomi ItzhakHi, Thanks for the info. In general, the XTAL_SettlingTime is used to work around a bug that is opened and should be fixed so it is temporary. What was observed is that when the fast clock settling time is set to default (i.e. 1.7mSec), the m33 would wake up from LPDS, pend for 1.7mSec until the clock is stabilized, and then move to awake. the power subsystem also has a definition for how much to wake up prior to an event (PowerWFF3_WAKEDELAYSLEEP). this is set to 15mSec. It is observed that during this time, the m33 is on full power (~20mA) although it has nothing to do but pend. This is why the XTAL settling time was increased to these values so the m33 remains in low current. It may have some implications as you stated but need to explore why. Regards, Shlomihttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1692159/cc3551e-support-for-tpc/6525063Thu, 29 Oct 2026 14:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bfc96838-1f7f-4ed5-af7b-19abb693bd69Sabeeh Khan1Hello Phil, Sorry for the delay. TPC is supported on the cc3551E. I&#39;m not sure about that specific standard you have mentioned, but TPC is supported. So if the AP tells the cc3551 device to reduce its power (via TPC protocol) then the power will similarly reduce on the device. There is no need to implement it from customer-perspective as the firmware will handle it automatically.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693632/cc3351mod-wifi-bluetooth-module-ic-with-mpn-cc3351modeniamozr/6525053Thu, 29 Oct 2026 14:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2a935d7f-15af-44f2-aa75-553999338466Sabeeh Khan1Hello Tanveer, You can connect it directly to a floating testpoint. The logger pin can be connected to a USB-UART transceiver for collecting the firmware logs on the cc3351MOD from a PC. The logger pin is sensed during power-up as an SOP pin and must remain at a high logic level ; an optional pullup is recommended if anything connected to the pin could affect its level.https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6525042Thu, 29 Oct 2026 14:17:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c9452c89-27c0-456d-b868-c87116681224Sabeeh Khan1Hello Saurav, [quote userid=&quot;662917&quot; url=&quot;~/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6524920&quot;]Also, for testing purpose we have remove CTS and RTS Line. is it okay? or its required to communication with CC33xx module.[/quote] This is NOT okay. You must use CTS/RTS. Please add back in CTS/RTS and then use &#39;cc33xx-supply= ;&#39;https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6524920Thu, 29 Oct 2026 12:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:44182ca4-d68e-4b6a-acce-79ccd3ffbafbsaurav pandyaHi Sabeeh Khan1 Also, for testing purpose we have remove CTS and RTS Line. is it okay? or its required to communication with CC33xx module. Thanks, Sauravhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6524818Thu, 29 Oct 2026 10:24:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3722a740-8d82-4ce8-8068-cf71c5e5661csaurav pandyaHi Sabeeh Khan1 , I used the command directly: &quot;echo 1 &gt; /sys/kernel/debug/ieee80211/phy0/cc33xx/ble_enable&quot;https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693686/cc3301-cc33xx-driver-ram-usage-optimization-requestThu, 29 Oct 2026 07:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9e931889-7bbd-4957-a67b-b55d18b00388Julien bouillePart Number: CC3301 Hi TI team, We are currently integrating the CC33xx driver into an embedded system with limited RAM resources. We have noticed that the driver has a relatively large RAM footprint, which can be challenging for memory-constrained MCU applications. Would it be possible for TI to consider RAM usage optimization in future driver releases, particularly by reducing static memory allocation and buffer sizes where possible? Any improvements in this area would be greatly appreciated. Thanks!Connected peripherals &amp; printersCC3301https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693666/cc3351mod-clarification-on-missing-regulatory-db-and-cc33xx-nvs-bin-during-cc3351mod-bootThu, 29 Oct 2026 06:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a54f5383-8497-4407-958e-df0cb0076e91Parv PatelPart Number: CC3351MOD Hello Team, I am using the CC3351MOD module with an AM62Lx processor. During Linux kernel boot, I see messages indicating that the following firmware files are missing: regulatory.db cc33xx-nvs.bin However, the Wi-Fi driver loads successfully, and Wi-Fi functionality appears to be working correctly. From my understanding, the cc33xx-nvs.bin file is used for chip calibration. For our design, we have already performed module calibration using the SimpleLink Wi-Fi Toolbox INI Composer and generated a cc33xx-conf.bin file. This configuration file is being loaded by the driver during initialization. My questions are: Is it expected that cc33xx-nvs.bin is not required when cc33xx-conf.bin is generated and loaded from the INI Composer output? Are there any functionality, performance, or RF compliance impacts if cc33xx-nvs.bin and regulatory.db are not present but Wi-Fi operates normally? Any clarification regarding the role of these files and whether additional actions are required would be appreciated. Thanks, ParvIndustrial AutomationCC3351MODhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693418/cc3351-ble-is-not-working/6524548Thu, 29 Oct 2026 05:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ef623b70-740b-4832-9381-553984854100saurav pandyaHi, Please find below dts of wifi and wifi successfully working fine we able to scan and connect with router cc33xx_en_reg: regulator-usdhc3 { compatible = &quot;regulator-fixed&quot;; pinctrl-names = &quot;default&quot;; pinctrl-0 = ; regulator-name = &quot;cc33xx-en-regulator&quot;; regulator-min-microvolt = ; regulator-max-microvolt = ; /*startup-delay-us = ; */ /* HW init grace period */ gpio = ; enable-active-high; status = &quot;okay&quot;; /*regulator-always-on; *//* Keeps the reset pin de-asserted (high) if regulator is not in use */ } &amp;usdhc1 { pinctrl-names = &quot;default&quot;, &quot;state_100mhz&quot;, &quot;state_200mhz&quot;; pinctrl-0 = ; pinctrl-1 = ; pinctrl-2 = ; keep-power-in-suspend; non-removable; wakeup-source; bus-width = ; cap-power-off-card; vmmc-supply = ; status = &quot;okay&quot;; assigned-clock-rates = ;*/ #size-cells = ;*/ wlcore: wlcore@0 { compatible = &quot;ti,cc3300&quot;; reg = ; // TODO need to check gpio pinctrl-names = &quot;default&quot;; pinctrl-0 = ; interrupt-parent = ; interrupts = ; irq-gpio = ; status = &quot;okay&quot;; }; }; pinctrl_usdhc1: usdhc1grp { fsl,pins = ; }https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1693632/cc3351mod-wifi-bluetooth-module-ic-with-mpn-cc3351modeniamozrThu, 29 Oct 2026 04:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:54f8df54-7c12-46c6-a494-7935644246a5Tanveer AhmedPart Number: CC3351MOD Hi, For the Pin#9 LOGGER output pin, shall I connect it to a Floating Testpoint or this also need to be connected to a GPIO similar to HOST_IRQ_WL? Kindly confirm this part. NOTE: I want both WiFi and Bluetooth to be used with this IC MPN# CC3351MODENIAMOZRAerospace &amp; DefenseCC3351MODhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1692955/cc3551e-feasibility-assessment-of-using-external-flash-mx25u3235f-with-cc3551e/6524413Thu, 29 Oct 2026 01:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c16e4351-82b8-4374-b439-c28311812f51Jim DengThank you for your reply. We also want to know when the flash of these Experimental devices will be completed for the comprehensive test. We are planning to use the flash of this Experimental device when mass-producing the wireless module products. Awaiting your response.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-modeThu, 29 Oct 2026 00:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9f2118a0-d3e1-474f-b753-093a844565c5Sundaresan Thangeswaran1Part Number: CC3235SF Hi, I am using the code below to switch between 2.4 GHz and 5 GHz Wi-Fi connections in intermittent connection mode. Initially, after flashing the firmware, the band switching works correctly. However, after entering AP mode and attempting to switch between 2.4 GHz and 5 GHz, the device does not connect as expected. I initially suspected that the issue was related to the automatic connection policy. However, even after restarting the Network Processor (NWP) and disabling the automatic connection policy using the code below, the issue persists. I would appreciate your guidance on resolving this issue. int status = sl_WlanPolicySet( SL_WLAN_POLICY_CONNECTION, SL_WLAN_CONNECTION_POLICY(0, 0, 0, 0), NULL, 0 ); SlWlanScanParamCommand_t scan2G = {0}; SlWlanScanParam5GCommand_t scan5G = {0}; _u8 enable5G = 1; scan2G.RssiThreshold = -90; scan5G.RssiThreshold = -90; if (bandwidth[0] == &#39;2&#39;) { scan2G.ChannelsMask = 0x3FFF; scan5G.ChannelsMask = 0; enable5G = 0; UART_PRINT(&quot;Select 2.4 GHz\r\n&quot;); } else if(bandwidth[0] == &#39;5&#39;) { UART_PRINT(&quot;Select 5 GHz\r\n&quot;); scan2G.ChannelsMask = 0; scan5G.ChannelsMask = 0x3FFFFFFF; UART_PRINT(&quot;Select 5 GHz\r\n&quot;); } else { scan2G.ChannelsMask = 0x3FFF; scan5G.ChannelsMask = 0x3FFFFFFF; UART_PRINT(&quot;Select dual band (2.4 GHz + 5 GHz)\r\n&quot;); } status = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, SL_WLAN_GENERAL_PARAM_OPT_SCAN_PARAMS, sizeof(scan2G), (_u8 *)&amp;scan2G); ASSERT_ON_ERROR(status); status = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, SL_WLAN_GENERAL_PARAM_OPT_SCAN_PARAMS_5G, sizeof(scan5G), (_u8 *)&amp;scan5G); ASSERT_ON_ERROR(status); status = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, SL_WLAN_GENERAL_PARAM_OPT_ENABLE_5G, sizeof(enable5G), &amp;enable5G); ASSERT_ON_ERROR(status); Regards, SundarMedical &amp; healthcareCC3235SFhttps://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1692955/cc3551e-feasibility-assessment-of-using-external-flash-mx25u3235f-with-cc3551e/6524314Wed, 28 Oct 2026 22:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ef7e6652-6f86-4ee8-921d-147dd62f0829Sabeeh Khan1Hello Jim, Experimental simply means that we now have support for those flash types but those have not gone through TI test cycles. The flash should execute the development code just fine, but it issues may arise because those flash types have not gone through our full test cycles so we still claim &quot;your mileage may vary&quot;.